Fix Razor VSCode C# completions at beginning of the line.

Looks like VSCode misbehaves in re-execution of completion scenarios. They've been experimenting with new completion range APIs and it seems that it translates O#'s non-new range based completion request into a new type of range completion request (range2).
We now fallback to using a range2 property on completion items if it exists and properly re-map.

https://github.com/aspnet/AspNetCore-ManualTests/issues/52
@jrieken I imagine this is not intended is it?

@dougbu or @wtgodbe would you mind merging this for me?

@NTaylorMullen So you are saying that you run the API command and don't get an item with a range back? What should happen is that when a provider produces a range than it is kept and when no range is provided than the default is the new range...

@NTaylorMullen So you are saying that you run the API command and don't get an item with a range back? What should happen is that when a provider produces a range than it is kept and when no range is provided than the default is the new range...

I'm not sure if O# provides ranges or not (@JoeRobich ?). However, even if they didn't I wouldn't imagine that a non-public property would then be used in the absence of a previously public one after calling vscode.executeCompletionItemProvider. Shouldn't that range -> range2 piece happen after our code returns it to you? I ask because there's no way for us to do anything to range (part of the public API) without casting this thing to any and grabbing the less reliable range2 property.

The plan is to make this public, e.g to change the signature like so: range?: Range | {inserting: Range, replacing: Range}. Things should be less confusing once that has happened. Today's lack of a default value for range is mostly because I didn't know which of inserting or replacing to use.


PNG version of Icons

HI there,
While I do appreciate the fact that these icons are available it would be GREAT if you could supply them as PNG as well as SVG. Seeing as there are a lot of Devs and Architects on Mac and the SVG support there is so-so it's a bit of a pain every 6 months when you go back and need a new set of icons. The previews looks like shit in Finder and you always end up needing to figure out whatever script and tool you need to loop through the folders and convert each file to png. Then you need remember to escape the paths cause you included + signs in the paths and what not if you use "find".
On top that something like Google Drawing doesn't support svg, which isn't your fault but still.
This seems to be the smoothest on Mac
brew install librsvg
cd to Icons in the downloaded svg folder
for i in */*.svg ; do rsvg-convert -h 512 "$i"> "$i".png ; done

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

ID: 6624d44c-f9f6-02f8-2c67-0f0637fed62e
Version Independent ID: 9346a8ff-bab5-be2c-9dc1-d546fda1efa9
Content: Azure Icons - Azure Architecture Center
Content Source: docs/icons/index.md
Service: architecture-center
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 363588

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 363588

@douglas-isaksson thanks for the request, delivering these Icons in PNG is in the near roadmap.  Unfortunately not able to provide timeline. IN the mean time, you can use Inkscape to batch convert SVG to PNG.  https://gallery.technet.microsoft.com/scriptcenter/Convert-SVG-to-PNG-e759387c

@douglas-isaksson thanks for the request, delivering these Icons in PNG is in the near roadmap.  Unfortunately not able to provide timeline. IN the mean time, you can use Inkscape to batch convert SVG to PNG.  https://gallery.technet.microsoft.com/scriptcenter/Convert-SVG-to-PNG-e759387c


[Enhancement] Refine the error message when creating a mv for iceberg catalog

Why I'm doing:
I tried to create a asynchronous materialized view in Starrocks, but the following error occurs.
SET CATALOG baikal;
USE assistant;
CREATE MATERIALIZED VIEW  `wap_meeting_summary_daily_mv`
PARTITION BY `day`
DISTRIBUTED BY hash(hgssiteid)
REFRESH MANUAL
PROPERTIES (
"force_external_table_query_rewrite" = "true"
)
AS
SELECT `day`, hgssiteid
FROM `baikal`.`assistant`.`wap_meeting_summary_daily`;
Detail message: Can not find database:assistant.

The error message is not clear, which may mislead users to investigate if the assistant exists in baikal or not.
What I'm doing:
refactor the error message body.
What type of PR is this:

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

Does this PR entail a change in behavior?

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

If yes, please specify the type of change:

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

Checklist:

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

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

[ ] This is a backport pr

Bugfix cherry-pick branch check:

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

[x] 3.4
[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0

@Youngwb @stephen-shelby plz help review the code

@zhaohehuhu commit conflict

@zhaohehuhu commit conflict

Fixed. Plz help review again.


Verifying firmware sha256

The releases' sha256sum files do not include the hash for the respective firmware-nk3-*.zip (I looked at releases >=1.5). At the same time this archive is what nitropy nk3 validate-update expects as input-file. While the zip file itself contains a separate sha256sum file for its content, it should still be listed for the release so that users can verify the download prior to validating it with the tool.

Adding it to sha256sum is not trivial because this one is generated by the CI before the images are signed and zipped into the container.  But we could maybe add a separate file that only has the checksum for the container.

Yes, I understand the zip creation has to trail the release of the firmware(s) and is a service to pick the correct image. A separate hash file would be ok, of course.
I realize a hash might seem superfluous for a zip with signed files, but keep in mind the tools signature validation outputs versions followed by "signed by: Nitrokey" only (e.g. no key ID). A lot of users will download but perform updates later and offline, hence, may want to double-check the firmware-zip to use at that moment.

For v1.5.0-test.20231030, I’ve manually added a firmware-nk3-v1.5.0-test.20231030.zip.sha256sum file.  It is to be discussed whether we want to do that for all releases.  If yes, it should be automated, documented and used in pynitrokey.

Thanks, having it available for a manual hash-check works fine for me. Once it's decided how to handle it in the future, I can make a suggestion perhaps.
As far as I've now seen in my test, pynitrokey already does check for the sha256sum inside the zip with the validate-update action. While the problem with the sha256sum in the zip is that users cannot use it to easily do a consistency check of the download (or firmware file) themselves, it suffices for validate-update itself. Of course this would change, if it's decided to drop the sha inside the zip, but then users would always have to download two files - not worthwhile in my opinion. So, aside for a couple more sentences in its user guidance and/or output, pynitrokey validation already is done and dusted™.(?)

I would keep the checksum inside of the container.  validate-update would not have to use the additional checksum file, but it could make sense to use it when downloading the update in nk3 fetch-update or nk3 update.  But I agree that it’s not important or required.


misalignment problem in the dataset

A question in the test_Sony.py is that, the scipy.io is really slow and cv2.imwrite is really fast. In the 8-bit saving way, do this two methods inference the finnaly PSNR & SSIM?

You can use any method you like. I evaluate the PSNR and SSIM using MATLAB.

I mean that the image saving code:
scipy.misc.toimage(temp * 255, high=255, low=0, cmin=0, cmax=255).save(
                result_dir + '%04d/%05d_00_train_%d.jpg' % (epoch, train_id, ratio))

It's really slow and the cv2.imwrite is much faster.
By the way, I found in your testset, some images are miss aligned, which affects the PSNR & SSIM a lot.
For example the 10034 gt_id, the phenomenon is so obvious.

Yes, I found the problem on 10034. Maybe you can exclude this image when evaluating.

When evaluating, this certain one image can be removed easily. But the PSNR will increase, right?
With your pretrained model, the results before and after removing the 10034 pairs are show as follow:

PSNR
SSIM

before
28.87
0.8879

after
29.03
0.8888

Hmm, the SSIM seems strange, same image used to calculate PSNR & SSIM.
Q1: Are there other misaligned pairs you know?
Q2: Finally, what do you think before publishing the amazing work? The misaligned image pairs hurt the results and your pipeline seems to have nothing to do with the latent misaligned factor.

I do not know how this misalignment happened. If I knew this image before, it should be removed already.

Oh, then I think we should fix the misalignment problems on some images in the dataset. @cchen156 @

@CQFIO @cchen156
would you provide the solved dataset if you solved this problem?
By the way,  what's your following schedule? Is there some following paper published, considering the open problems in the conclusion section in the paper?

Hi I checked each test image manually. I found misalignment in 10034, 10045 and 10172. Please remove these images for quantitative evaluations. But you can still use them for qualitative evaluations.

Thanks for your check. Besides, did you check the train & val datasets?

We also found that there are many misalignment data in the training sets, such as 00183.

@TerryYiDa you could simply use difference graph.

Hello, could you explain more on it? What is 'difference graph'? Thanks!


React native image picker works on emulator but gives an error message on real device "an error has occurred "

Hey everyone, I am having an issue with react native image picker library.
I am trying to upload the images from mobile which I take at that instance through "launchCamera" function to my database, doing so through an Android emulator works fine without any issues and even the response shows as status code 200 and data is saved in database table. But the issue occurs when doing the same through real device, whether it be Debug or Release.
Please shed some light if anyone has any idea how to solve this issue.
Thank you in advance
this is my submit button code which is pressed after the images are taken
const SubmitData = async () => {
        // debugger;
        if (frontImage != '' && frontImage != undefined) {
            DataForm.append('fileFront', {
                name: frontImage.name,
                type: frontImage.type,
                uri: frontImage.uri,
            });
        }
        if (backImage != '' && backImage != undefined) {
            DataForm.append('fileBack', {
                name: backImage.name,
                type: backImage.type,
                uri: backImage.uri,
            });
            // DataForm.append('json_body', JSON.stringify(JsonData));
        }

        DataForm.append('json_body', JSON.stringify(JsonData));
        // console.log(JsonData);
        // debugger;
        fetch('http://<IP_ADDRESS>:831/api/Data/DataCollection', {
            method: 'POST',
            headers: {
                'Content-Type': 'multipart/form-data',
            },
            body: DataForm,
        })
            .then(response => {
                debugger;
                response.json();
            })
            .then(json => {
                // debugger;
            })
            .catch(err => {
                debugger;
           });}

and this is how am using the launchCamera function
launchCamera({mediaType: 'photo'}, imageresponse => {
                                if (imageresponse.didCancel != true) {
                                    setFrontImage({
                                        name: imageresponse.assets[0].fileName,
                                        type: imageresponse.assets[0].type,
                                        uri:
                                            Platform.OS === 'android'
                                                ? imageresponse.assets[0].uri
                                                : imageresponse.assets[0].uri.replace('file://', ''),
                                        // direction: 'Front',
                                    });
                                }

                                // setPickerResponse(imageresponse);
                            });

Any help would be appreciated

How did you fix this?


fix issue 16:some items in deviceProperties do not have value

What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #16
/assign @qclc
Does this PR introduce a user-facing change?
NONE

/approve


docs: Various documentation updates

These are some changes that didn't get merged when PR #3335 was closed.

Nice, merged, thanks @synicalsyntax!


Upgrade Service Bus Package to use V7 SDK

The Service Bus V5 SDK is now deprecated, and the recommendation is to use V7. The Azure team published guidance on migrating to the new version.
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/MigrationGuide.md
For the most part, it was a fairly simple migration. The notable changes are:

Disable Cross-Entity Transactions - It was difficult to see how MassTransit should be configured when the recommendation is to do a receive first. It felt safer to turn it off.
Exposed new authentication mechanisms since there is no longer a single ITokenProvider.

Verification Steps:

Configured Service Bus tests to point to a private Service Bus. Most tests were successful, but there were some flaky ones that failed.
Created a separate Console app to send/receive messages using the .NET core generic host
Created a separate Function app to send/receive messages

Open Question: What should the versioning look like? I replaced the V5 SDK with V7 and the interfaces did change, so this would be a breaking change. It looks like the versioning is to keep all MassTransit packages at the same version; should this be another package?

So AF is now released using v7 of the SDK? That's great if so.

Looking good, I'll review it in the next day and see about getting it merged.

Once I get v7.2.4 released, I plan to pull this in as a squashed since commit, and update the version to v7.3.0.

This has been rebased/squashed/merged. Thank you!

@stainlessfawn  Any thoughts on this question? https://stackoverflow.com/questions/70850335/is-it-possible-to-use-hybrid-identity-with-masstransit-and-azure-identity

@phatboyg I don't have enough reputation on stack overflow to leave comments. I left an answer over there that focused on the differences I was aware of in the auth libraries. I honestly don't know anything about Hybrid Identity, so my answer is solely based on the differences.

No worries, I saw your answer. I'm not sure either how Hybrid is supposed to work.

Is there any value is setting DefaultAzureCredential if none is specified? Or would it conflict with credentials present in the connection string?


Download users button gives a proxy error

An admin user reported that they got a Proxy Error when downloading users for their institution.

I think this one is fixed. Can you verify @mariapraetzellis


alignchecker: require binary.Size and unsafe.Sizeof of all types to match

With the recent switch to ebpf-go's native map k/v (un)marshaling code,
a few MapKey and MapValue types came up that were lacking trailing padding.
These will be fixed in a follow-up commit, but to avoid future regressions,
the alignchecker needed to be improved to catch these errors during agent
startup, to guarantee catching it in CI instead of randomly during runtime.

ebpf-go uses binary.Read and binary.Write to convert values exchanged with the
kernel APIs to and from Go types. However, package 'binary' ignores all padding
in the given type. When calling binary.Write on a struct, all data will be
nicely packed into the resulting byte slice.

Since the Cilium agent was previously passing unsafe.Pointers to MapKeys and
MapValues to ebpf-go's Map APIs, it uses the reflect.Value().Size() (equivalent
of unsafe.Sizeof()) to populate Map.KeySize and .ValueSize. This value _does_
account for all padding, unlike binary.Size used by binary.Read() and .Write().

This blows up when interacting with the Map, since ebpf-go checks the amount
of bytes produced by binary.Write against the configured KeySize value of the
Map.

This commit modifies the alignchecker so it receives the actual Go types instead
of a reflect.Type, since we cannot call binary.Size on the latter. It also fixes
a logic bug in TestAlignChecker where the test returned after checking the first
test with an expected error.

Fixes: https://github.com/cilium/cilium/issues/26287
Require binary.Size and unsafe.Sizeof of all types to match

/test


Time coordinates are sometimes integers, not datetime64

Noticed this in https://gist.github.com/rmg55/b144cb273d9ccfdf979e9843fdf5e651, and I've had it happen before myself:
Coordinates:
  * time            (time) object<PHONE_NUMBER>627000000 ...<PHONE_NUMBER>393000000

Pretty sure stackstac is correctly making it into a pandas DatetimeIndex: https://github.com/gjoseph92/stackstac/blob/b652a07f9b2ae27235aea4db4ef0f1f594fd8941/stackstac/prepare.py#L354-L358
but something is going weird when xarray receives that, and it reinterprets it as an object array.

@gjoseph92 I believe you're running into https://github.com/pydata/xarray/issues/3291
I'm finally trying out stackstac and just ran into this. basically xarray doesn't like timezones, and since the ite spec has times always is UTC my strategy has been to either 1. rstrip('Z') on datestrings, or 2. use .tz_localize(None) on your pandas datetime index. If you'd like I can put in PR, should be an easy fix!
import numpy as np
import xarray as xr
print(xr.__version__) #0.17.0

np.random.seed(0)
temperature = 15 + 8 * np.random.randn(2, 2, 3)
precipitation = 10 * np.random.rand(2, 2, 3)
lon = [[-99.83, -99.32], [-99.79, -99.23]]
lat = [[42.25, 42.21], [42.63, 42.59]]

# https://github.com/radiantearth/stac-spec/blob/master/item-spec/item-spec.md#properties-object
# STAC ITEMS have datetime as UTC strings like this:
dates = ['2019-12-30T00:00:01.000Z', '2020-01-05T00:00:01.000Z', '2020-01-11T00:00:01.000Z']
times = pd.to_datetime(dates)

da = xr.DataArray(
    data=temperature,
    dims=["x", "y", "time"],
    coords=dict(
        lon=(["x", "y"], lon),
        lat=(["x", "y"], lat),
        #time=times, #results in dtype 'object'
        time = times.tz_localize(None), #results in dype 'datetime64[ns]'
    )
)
da

So, after I looked into this a bit, I couldn't understand why your example with S2 cogs does work as expected. It looks to me like there is an issue in pd.to_datetime() with infer_datetime_format=True if timestamps do not have decimal seconds:
# NASA CMR-STAC Dates
dates = ['2019-12-30T00:00:01.000Z', '2020-01-05T00:00:01.000Z', '2020-01-11T00:00:01.000Z']
pd.to_datetime(dates, infer_datetime_format=True, errors="coerce")

DatetimeIndex(['2019-12-30 00:00:01+00:00', '2020-01-05 00:00:01+00:00',
'2020-01-11 00:00:01+00:00'],
dtype='datetime64[ns, UTC]', freq=None)

# S2 dates
dates = ['2020-05-01T18:04:03Z', '2020-04-28T17:54:06Z', '2020-04-26T18:04:09Z']
pd.to_datetime(dates, infer_datetime_format=True, errors="coerce")

DatetimeIndex(['2020-05-01 18:04:03', '2020-04-28 17:54:06',
'2020-04-26 18:04:09'],
dtype='datetime64[ns]', freq=None)

the UTC time zone info is there as expected if you don't use infer_datetime_format (default is False)
# S2 dates
dates = ['2020-05-01T18:04:03Z', '2020-04-28T17:54:06Z', '2020-04-26T18:04:09Z']
pd.to_datetime(dates, infer_datetime_format=False, errors="coerce")

DatetimeIndex(['2020-05-01 18:04:03+00:00', '2020-04-28 17:54:06+00:00',
'2020-04-26 18:04:09+00:00'],
dtype='datetime64[ns, UTC]', freq=None)

Seems like a pandas bug? cc @TomAugspurger. Should stackstac expose infer_datetime_format as a keyword? not sure how much of a speedup that gets. In any case, adding a .tz_localize(None) gives you datetime64 in xarray coords, so that solution i suggested would still be a viable fix.

It's probably a bug. My understanding of infer_datetime_format is that it should be purely an optimization.

@scottyhq thanks a ton for looking into this!
Based on https://github.com/pydata/xarray/issues/3291#issuecomment-531522690, it sounds like dropping timezone information before going to xarray is currently the only option.
I don't see anything in the STAC spec that explicitly requires UTC; it just says datetimes must follow RFC 3339, which does include time-offset     = "Z" / time-numoffset. So I think we should handle other timezones, even if they're not commonly used.
How about we add a tz="UTC" parameter to stackstac.stack, so you can optionally set the timezone that stackstac converts to? And then do .tz_convert(tz).tz_localize(None) (maybe with a fastpath for tz=="UTC" to just do tz_convert(None)).
As for the infer_datetime_format problem, since you've looked into it a bit, @scottyhq could you open an issue on pandas? Then I'd say:

If the bug only applies when time-offset == "Z", then why don't we say that stackstac assumes any tz-naive dates are in UTC, and call tz_localize("UTC") appropriately (or, if tz == "UTC" already, then do nothing).
If the bug would cause us to lose timezone information from non-UTC dates, then let's set infer_datetime_format=False until it's fixed.

https://github.com/radiantearth/stac-spec/blob/master/item-spec/item-spec.md#properties-object states that datetime requires UTC:

REQUIRED. The searchable date and time of the assets, in UTC.

@matthewhanson or @m-mohr would greatly appreciate if you could clarify if that is a typo. I'm used to seeing UTC times in metadata, but it's also convenient to have the timezone information somewhere to easily convert to local time without relying on location-based lookups.

As for the infer_datetime_format problem, since you've looked into it a bit, @scottyhq could you open an issue on pandas?

yep, I'll open this now. also might rekindle discussion in xarray for handling timezones since I know there is current effort that is relevant to refactoring for more flexible indexing, and i feel like passing a pandas index with timezone information should work. cc @dcherian if you have pointers to relevant discussion here.

I'm not sure myself. I'd suggest opening an issue in stac-spec and discuss there. I could imagine that this is a legacy thing that we still want to change...

states that datetime requires UTC

Duh! Totally missed that, thanks for the careful read.
Let's see what comes up on https://github.com/radiantearth/stac-spec/issues/1095, but for now I'd vote for not assuming dates are always UTC, and doing the .tz_convert(tz).tz_localize(None) approach in stackstac. Do you think you'll get to a PR for that? If not, I can probably do it next week.

for not assuming dates are always UTC, and doing the .tz_convert(tz).tz_localize(None) approach in stackstac. Do you think you'll get to a PR for that? If not, I can probably do it next week.

Sounds good. I can start a PR. What's your preference for tests @gjoseph92 ?, It'd be nice to put in a simple framework, if you're ok for it I could copy what we've been using over in intake-stac https://github.com/intake/intake-stac/blob/main/.github/workflows/main.yaml

Tests are my biggest to-do right now, since IMO it's the main thing blocking contribution. I have a lot of thoughts on how I'd like this to look in https://github.com/gjoseph92/stackstac/issues/26.
I'd prefer to not copy in the intake-stac yaml, since it seems to be conda-oriented to me, and I'd like to keep this only using poetry. I'd say, if you want to write a pytest-friendly test for this case and put it in //stackstac/tests/test_prepare.py, go for it and we'll set up CI in the near future, otherwise don't worry about it.


Some new README text

https://issues.apache.org/jira/browse/SOLR-12345
Description
Please provide a short description of the changes you're making with this pull request.
Solution
Please provide a short description of the approach taken to implement your solution.
Tests
Please describe the tests you've developed or run to confirm this patch implements the feature or solves the problem.
Checklist
Please review the following and check all that apply:

[ ] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[ ] I have created a Jira issue and added the issue ID to my pull request title.
[ ] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[ ] I have developed this patch against the main branch.
[ ] I have run ./gradlew check.
[ ] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

(This was an example that I created in showing a Allejando how to create PRs, during our Community over Code "Solr Hackathon", please ignore.)


See raw request passed to API

Describe the solution you'd like
I want to see what exactly Instructor sends to OpenAI. I don't fully understand how the docstring, examples and descriptions of fields are passed to the LLM and want to gain more transparency into that.

https://useinstructor.com/concepts/logging/?h=logging


Unclear statement on how to achieve failover group upgrades

It recommends to upgrade the secondary database first, and then upgrade the primary. How can you upgrade the secondary under failover groups if it is in readonly mode? Can someone clarify what it means and how to achieve this as what the document claims?
We are designing a high availability application with almost zero downtime in combination of traffic manager using this design and approach but instead of just geo-replication we want it be included in failover group.

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

ID: 2476aace-c2ac-4084-93d5-8bd4edbc0ea0
Version Independent ID: fa098bb4-5c9e-0f58-cfc7-5d40eb1ce89b
Content: Failover groups and active geo-replication - Azure SQL Database
Content Source: articles/sql-database/sql-database-geo-replication-overview.md
Service: sql-database
GitHub Login: @anosov1960
Microsoft Alias: sashan

The section of the document you are referring is in regard to performance level:
Upgrading or downgrading a primary database

You can upgrade or downgrade a primary database to a different performance level (within the same service tier) without disconnecting any secondary databases. When upgrading, we recommend that you upgrade the secondary database first, and then upgrade the primary. When downgrading, reverse the order: downgrade the primary first, and then downgrade the secondary. When you upgrade or downgrade the database to a different service tier, this recommendation is enforced.

If your secondary is a lower tier in performance than the primary, and a fail-over event were to take place, there is a potential issue with the secondary having to manage workloads that are greater than what it can potentially handle.
Please let me know if you have additional questions.
Regards,
Mike

@Mike
Oh, I thought the "Upgrading or downgrading a primary database" is about rolling out new migration in the database. Thank you for clarification.
Warm regards,
Jr

@jrtabuloc No worries, and happy to make things clear. I am going to close this issue but if you still would like to discuss this further please feel free to reopen, and we can continue.
Regards,
Mike


Lynx compatibility

The Lynx browser seems unable to connect to the website. It gives the error "Unable to make secure connection to remote host".

Based on a report from SSLLabs, the SSL cert on the site only supports an ECDHE cipher, which Lynx isn't too happy with.
The best way to fix this would probably be to get a whole new certificate. Right now judging that to be too expensive to be worth it.


Need more publicity for Town Hall

We need to think more about how and where to publicise

Town Hall itself
requests for info from working groups and special interest groups
requests for people to run an ATH

and try to make publicity regular and co-ordinated

Channels:

Intersect newsletter

Discord

Twitter

Cardano forum?

Ask Intersect team to include an item reminding people of the date of TH and the link to it in subsequesnt newsletters.We could include a graphic about the agenda - could be taken direct from the slides, for example https://docs.google.com/presentation/d/1kczrgQ0tnQcrVN0g8k9Sqpgz0x6BzEzCo3GgD4zZZY8/edit?usp=sharing

we can also post this slide in Discord, and Tweet it

Need to create a workflow to ensure newsletter text is written and sent each week after planning WG or internal team meeting

Here is the task that runs across the entire project and includes different tools and methods we have been using to publicise information
https://github.com/orgs/Catalyst-Swarm/projects/1/views/1?pane=issue&itemId=62973624&issue=Catalyst-Swarm|Intersect-Town-Hall|8


multiple opbi

for ticket: https://github.ibm.com/IBMPrivateCloud/roadmap/issues/59166
allow multiple operandBindInfo in different namespaces mounting the same secret.

/retest


Firefox md-input placeholder text doesn't appear above user input

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Run the demo app in Firefox, or go to https://material2-app.firebaseapp.com/ . Click on a text field with placeholder text. The placeholder text will turn blue but remain in the same place. Start typing and the placeholder text will disappear entirely.

What is the expected behavior?
Chrome behaves correctly; when the text field becomes focused, the placeholder text should animate above the entered text.

Which version of Angular and Material, and which browser and OS does this issue affect?
Behavior is identical in Firefox 45 on Mac OS X 10.11, Windows 10, and Android. Running against material2 head.

Other information
Commenting out the "input:-webkit-autofill + .md-input-placeholder" selector in input.scss (https://github.com/angular/material2/blob/master/src/components/input/input.scss#L140) makes Firefox work as expected. Apparently Firefox believes "input:-webkit-autofill" is invalid CSS and won't apply any selectors that contain it.

One option is to split webkit-autofill and other selectors from each other. This will duplicate several lines of css, but will work for firefox, without affectine chrome/safary autofill behavior.
e.g. rendered css which works as expected
`[_nghost-dxv-12] .md-input-placeholder.md-float:not(.md-empty), [_nghost-dxv-12] .md-input-placeholder.md-float.md-focused, [_nghost-dxv-12] .md-input-placeholder {
visibility: visible;
padding-bottom: 5px;
-webkit-transform: translateY(-100%) scale(0.75);
transform: translateY(-100%) scale(0.75); }
[_nghost-dxv-12] .md-input-placeholder.md-float:not(.md-empty) .md-placeholder-required, [_nghost-dxv-12] .md-input-placeholder.md-float.md-focused .md-placeholder-required, [_nghost-dxv-12] .md-input-placeholder .md-placeholder-required {
color: #9c27b0; }
[_nghost-dxv-12] input:-webkit-autofill + .md-input-placeholder {
visibility: visible;
padding-bottom: 5px;
-webkit-transform: translateY(-100%) scale(0.75);
transform: translateY(-100%) scale(0.75); }
[_nghost-dxv-12] input:-webkit-autofill + .md-input-placeholder .md-placeholder-required {
color: #9c27b0; }`


TM-87: Update vocabs

Closes TM-87.

[x] Checked with insomnia that PUT vocabs works
[x] Checked in FE that PUT is used and that it works in FE too


Update Travis to run on latest stable and LTS Node.js

With this configuration, Travis will always run a build on both the latest stable and LTS Node.js versions.
This is also required to fix the block from Dependabot, husky 7.0.0 requires Node.js 12 or higher and Travis runs Node.js 10, so CI is failing on the PR to update husky.

#837 can be merged after this is merged.


APEXMALHAR-2517 - Shaded 3.7.0 release with legacy packages

The resulting artifact will contain the old com.datatorrent packages as of release 3.7 and will become a dependency of malhar-library with the upcoming release to provide these classes for backward compatibility (classes removed in #662).
To be merged after #662

What would be the benefit of doing this? Won't the malhar version 3.7 that is on maven central already have the 3.7 com.datatorrent classes. Is it to simulatenously use the older classes alongside new versions? What I am missing is how the apps written against 3.7 will benefit from newer versions without code changes. I thought we were going to create an alternate shaded version of the operators relocated to com.datatorrent so existing apps would work with newer versions.

That question was already answered during the mailing list discussion: The operators from old packages are deprecated and frozen as of 3.7, they are no longer developed (same as if you put @deprecated on a class and never touch it again). The only reason and goal for doing this is backward compatibility.
To take advantage of fixes and new features, the user will switch to the new packages. This will be mentioned in the release notes.

I don't think there was an agreement to this on the mailing list discussion from any of the folks involved in the discussion. I like the shading idea in general but would like to see it used to support the existing package names without things being frozen to a specific release or go the old fashioned approach of creating deprecated extensions. The old names can be dropped when we go to the next major version.

There was no consensus on the mailing list. Urgency of this big change was not explained. We do need to keep end user's convenience in mind. This change needs to be done in 4.0, not in 3.8.

@sandeshh I suggest you review the original email thread as that may address most of your concerns. Specifically I find it inappropriate to loop back on "urgency" when this is a two year old topic that was discussed many months before now finally action is taken. The other point that was already addressed is whether or not 4.0 is required to make this change. There are several options to satisfy backward compatibility (which this PR and related discussion actually is about.) I will appreciate your constructive input and suggestions that help move things forward.

@PramodSSImmaneni I think what you are asking for is not backward compatibility but forward compatibility :) However, both of the approaches you mention (extending new classes and offering new classes under old name) may not provide the same level of backward compatibility, as they would be intermingled and not isolated. I will look at it a bit more.

@tweise I am not looping back on urgency, I am saying this looking forward. We have already waited for 2 years, why not wait for few more months and do this change with 4.0? I am not against this change. What's the benefit to end users? To get simple bug fixes they have to change all the namespaces? rather than just changing the version number in POM.
FYI
I have also done similar(name) changes, like https://issues.apache.org/jira/browse/APEXCORE-475

The change is overdue like many others. There is the tendency to wait for the next great opportunity and that is why we are having this conversation after 2 years. When you look around you will find more examples where things are discussed and never taken up. Instead, you need to break things down in achievable units and tackle them on an ongoing basis. A major version change is not just a label on the package but signifies more than that. I don't see any reason to declare a new major version unless there is either real progress in operator maturity or other breaking changes are due.
IMO the discussion made clear that package cleanup can be done without major version change, now we need to decide which of the available options to pick for backward compatibility. To me it would be quite normal to change the import statements to pick up the change I'm interested in after upgrade (or do nothing if I don't care). If that's not agreeable then we have other options to move forward.

Please see my comments on #662


AVAudioFile crashes instead of throwing error when loading an invalid file

Hi I have the following code:
do {
    let audioFile = try AKAudioFile(forReading: url)
    soundfont.append(audioFile)
} catch {
    Crashlytics.sharedInstance().recordError(error, withAdditionalUserInfo: [
        "instrument": self.id,
        "file": file,
        "path": url,
    ])
}

I get a EXC_BAD_ACCESS error instead of having my catch execute.
I've attached the corrupt file if need be, but clearly this is an automatically generated file that shouldn't be there in the first place. Still :)
corrupt.zip

So I think what's happening here is that soundfont.append cannot be in the do try catch cycle. audioFile should be declared outside of the do and try'ed inside.  Let me know if that fixes things.


chore: fix getting started button link to not require redirect

/assign @RFMVasconcelos

The get started button requires a redirect, when testing locally I noticed redirection do not work, so it's not very convenient.
Also, the links should better use current real urls without redirection to improve browsing experience.
Therefore, I'm sending this PR to fix this.


Java: Generate builders for panels

Contributes to https://github.com/grafana/cog/issues/360
It generates panel's builders for Panels.
It adds a bit "hacky" things to make it works assuming that if there is a builder called "Panel" under a package, it needs a builder. Dashboard one is skipped since it already has a "Panel" builder and we could have file conflicts if we generate it twice.
Most of the changes in the template is to able to do cast to generic objects to be able to set the values. Also the functions that do the stuff have comments to be able to understand what they are doing if we need to re-check them in the future.

The error is fixed in the other PR.


Animate shadow?

Is it possible to animate this shadow? This has been such an amazing module, can't thank you enough for it.

Whan kind of animation? Can you give some examples/reference?

Thank you very much @Kishanjvaghela for being so supportive as always. My hope was to use it with the Animated API, example:
Render:
const anim = new Animated.value(0)

....
render() {
    const interpolated = anim.interpolate({ inputRange:[0,1], outputRange:[0,10] });
    return<Animated.Card cardElevation={interpolated} cardMaxElevation={interpolated} />
}

....

Animated.timing(anim, { toValue:1, duration:300 }).start();

This is the typical way Animated API is used, for instance the Blur view from Expo:
https://docs.expo.io/versions/latest/sdk/blur-view.html

A user just implemented an animation, this might help, I'm not familiar with the native side of things, so I'm hoping this share helps you out :)
https://github.com/react-native-community/react-native-blur/issues/152#issuecomment-353714361
Diff of changes made - https://github.com/AlpacaDB/react-native-blur/compare/b415e7774e046bdccc351da8e56581534777266e...1f0303a5c66179e3f9c84c9bf306968a2d453f19

Use Animated as per suggested by @Noitidart


Solver Mosek in Ubuntu 20.04 error - Process finished with exit code 132 (interrupted by signal 4: SIGILL)

Describe the bug
Running cvxpy code in a Ubuntu 20.04 VM with the mosek solver results in an error
Process finished with exit code 132 (interrupted by signal 4: SIGILL)
Exactly the same conde runs in Windows without problems.
Do you have any recommendations how to debug, the verbose output is not very helpfull, it fails at solve
problem.solve(verbose=True)
Any results for this error are mostly related to Apple hardware or Tensorflow (which does not apply in this case)
(CVXPY) Feb 09 02:51:29 PM: Your problem has 348 variables, 3 constraints, and 0 parameters.
(CVXPY) Feb 09 02:51:29 PM: It is compliant with the following grammars: DCP, DQCP
(CVXPY) Feb 09 02:51:29 PM: (If you need to solve this problem multiple times, but with different data, consider using parameters.)
(CVXPY) Feb 09 02:51:29 PM: CVXPY will first compile your problem; then, it will invoke a numerical solver to obtain a solution.
(CVXPY) Feb 09 02:51:29 PM: Compiling problem (target solver=MOSEK).
(CVXPY) Feb 09 02:51:29 PM: Reduction chain: Dcp2Cone -> CvxAttr2Constr -> ConeMatrixStuffing -> MOSEK
(CVXPY) Feb 09 02:51:29 PM: Applying reduction Dcp2Cone
(CVXPY) Feb 09 02:51:29 PM: Applying reduction CvxAttr2Constr
(CVXPY) Feb 09 02:51:29 PM: Applying reduction ConeMatrixStuffing
PyDev console: starting.

===============================================================================
                                     CVXPY
                                     v1.2.2
===============================================================================
-------------------------------------------------------------------------------
                                  Compilation
-------------------------------------------------------------------------------
(CVXPY) Feb 09 02:51:29 PM: Applying reduction MOSEK
(CVXPY) Feb 09 02:51:29 PM: Finished problem compilation (took 7.127e-03 seconds).
(CVXPY) Feb 09 02:51:29 PM: Invoking solver MOSEK  to obtain a solution.
-------------------------------------------------------------------------------
                                Numerical solver
-------------------------------------------------------------------------------

(CVXPY) Feb 09 02:51:29 PM: Problem
(CVXPY) Feb 09 02:51:29 PM:   Name                   :
(CVXPY) Feb 09 02:51:29 PM:   Objective sense        : maximize
(CVXPY) Feb 09 02:51:29 PM:   Type                   : LO (linear optimization problem)
(CVXPY) Feb 09 02:51:29 PM:   Constraints            : 348
(CVXPY) Feb 09 02:51:29 PM:   Affine conic cons.     : 0
(CVXPY) Feb 09 02:51:29 PM:   Disjunctive cons.      : 0
(CVXPY) Feb 09 02:51:29 PM:   Cones                  : 0
(CVXPY) Feb 09 02:51:29 PM:   Scalar variables       : 687
(CVXPY) Feb 09 02:51:29 PM:   Matrix variables       : 0
(CVXPY) Feb 09 02:51:29 PM:   Integer variables      : 0
(CVXPY) Feb 09 02:51:29 PM:
(CVXPY) Feb 09 02:51:29 PM: Optimizer started.
(CVXPY) Feb 09 02:51:29 PM: Presolve started.
(CVXPY) Feb 09 02:51:29 PM: Eliminator started.
(CVXPY) Feb 09 02:51:29 PM: Freed constraints in eliminator : 75
(CVXPY) Feb 09 02:51:29 PM: Eliminator terminated.
(CVXPY) Feb 09 02:51:29 PM: Linear dependency checker started.
(CVXPY) Feb 09 02:51:29 PM: Linear dependency checker terminated.
(CVXPY) Feb 09 02:51:29 PM: Eliminator started.
(CVXPY) Feb 09 02:51:29 PM: Freed constraints in eliminator : 0
(CVXPY) Feb 09 02:51:29 PM: Eliminator terminated.
(CVXPY) Feb 09 02:51:29 PM: Eliminator - tries                  : 2                 time                   : 0.00
(CVXPY) Feb 09 02:51:29 PM: Lin. dep.  - tries                  : 1                 time                   : 0.00
(CVXPY) Feb 09 02:51:29 PM: Lin. dep.  - number                 : 0
(CVXPY) Feb 09 02:51:29 PM: Presolve terminated. Time: 0.00

Process finished with exit code 132 (interrupted by signal 4: SIGILL)

Please dump the offending problem to a task file (prob.solve(solver=MOSEK, save_file="dump.task.gz")) and send the resulting dump file to Mosek support for debugging. https://docs.mosek.com/latest/faq/faq.html#how-do-i-dump-the-problem-to-a-file-to-attach-with-my-support-question

Closing because it seems this is off-topic for the CVXPY repo. Sending one last ping to @aszekMosek: you may want to follow up with @EmJay276 if you haven't heard back from them yet.


soft clipping primers from BAM files using sequences

Hello
Is it possible to  soft-clips gene-specific primers from BAM  files based on  primer sequences in fasta format instead of using genomic coordinates

Additionally I only want to soft clip an aligned read if the primer sequence shows up on the read edges

Currently BAMClipper soft-clips primer sequences at read edges based on BEDPE locations, which are usually derived from primer sequences in FASTA. Do you mean you have difficulties in preparing a BEDPE file from your primer sequences FASTA?

Many thanks for your response.
1)How do you derive the BEDPE locations from primer sequences in FASTA ?
2) Why use BEDPE locations instead of the sequences ?

Primer sequences can be mapped to genomic locations using these in silico PCR tools:

MFEPrimer 2.0
UCSC In-Silico PCR
NCBI Primer-BLAST
Please let me know if you have difficulties in preparing the BEDPE file. And do you think it will be handy if BAMClipper includes some kind of conversion tool to convert primer sequences to BEDPE for you?

Regarding your second question, BEDPE location is preferred for performance reason. Since aligner (e.g. BWA-MEM) matches primer sequence(s) in the NGS reads to reference genome already, BAMClipper soft-clips the primers accordingly without doing the matching again (NGS read versus primer sequences).


Group migration stuck in a loop

We are preparing for migrating all of our on prem distribution groups. On the third pilot set of groups one of them failed because we had a conflicting contact address in O365. I removed the contact and ran the migration again. It seemed to be proceeding fine and even moved the distro to the unsynced OU, deleted the synced distro from O365, and created the new distro with what looks like all of the correct attributes. Below is the log from the running process and it starts with where I think the issue started and ends with what it is now looping over and over again with:
[9/24/2024 1:16:45 PM] - Email address to remove after resetting attributes. [9/24/2024 1:16:45 PM] -<EMAIL_ADDRESS>[9/24/2024 1:16:45 PM] - Max retry attempt: 0 [9/24/2024 1:16:45 PM] - Error bulk updating email addresses on distribution group. Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=bfdc5f69-a3c8-d8c2-af03-0a9e16afaf8a,TimeStamp=Tue, 24 Sep 2024 19:16:45 GMT],Write-ErrorMessage

[9/24/2024 1:16:45 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:16:55 PM] - Max retry attempt: 1
[9/24/2024 1:16:56 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=670ed8bc-9d06-2a03-ebb6-48bce4092c30,TimeStamp=Tue, 24 Sep 2024 19:16:55 GMT],Write-ErrorMessage

[9/24/2024 1:16:56 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:17:06 PM] - Max retry attempt: 2
[9/24/2024 1:17:06 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=104d2060-c049-c65b-5a1c-9b7e6c2f7243,TimeStamp=Tue, 24 Sep 2024 19:17:06 GMT],Write-ErrorMessage

[9/24/2024 1:17:06 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:17:16 PM] - Max retry attempt: 3
[9/24/2024 1:17:16 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=35fb6e56-1be4-0ade-b136-734f463466b5,TimeStamp=Tue, 24 Sep 2024 19:17:16 GMT],Write-ErrorMessage

[9/24/2024 1:17:16 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:17:26 PM] - Max retry attempt: 4
[9/24/2024 1:17:26 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=d9feddce-6d3a-74a2-3c1d-49ab21e37536,TimeStamp=Tue, 24 Sep 2024 19:17:26 GMT],Write-ErrorMessage

[9/24/2024 1:17:26 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:17:36 PM] - Max retry attempt: 5
[9/24/2024 1:17:36 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=a6843d2d-d773-6f01-fe2e-68108d7a0d5c,TimeStamp=Tue, 24 Sep 2024 19:17:36 GMT],Write-ErrorMessage

[9/24/2024 1:17:36 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:17:46 PM] - Max retry attempt: 6
[9/24/2024 1:17:47 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=40a2fab0-5f78-da9d-c393-fb1aac372117,TimeStamp=Tue, 24 Sep 2024 19:17:46 GMT],Write-ErrorMessage

[9/24/2024 1:17:47 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:17:57 PM] - Max retry attempt: 7
[9/24/2024 1:17:57 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=5e12acaa-e515-3a22-98ad-24b833ab1fab,TimeStamp=Tue, 24 Sep 2024 19:17:57 GMT],Write-ErrorMessage

[9/24/2024 1:17:57 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:18:07 PM] - Max retry attempt: 8
[9/24/2024 1:18:07 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=61bca454-0390-cf36-e547-73e0f5da8a6a,TimeStamp=Tue, 24 Sep 2024 19:18:07 GMT],Write-ErrorMessage

[9/24/2024 1:18:07 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:18:17 PM] - Max retry attempt: 9
[9/24/2024 1:18:17 PM] - Error bulk updating email addresses on distribution group.
Write-ErrorMessage : Cannot process argument transformation on parameter 'EmailAddresses'. Cannot convert value "System.Collections.Generic.List`1[System.String]" to type "Microsoft.Exchange.Data.ProxyAddressCollection". Error: "The value
<EMAIL_ADDRESS>is already present in the collection."
At C:\Users\kbloomquist\AppData\Local\Temp\tmpEXO_kw5t2yv1.xwr\tmpEXO_kw5t2yv1.xwr.psm1:1205 char:13

        Write-ErrorMessage $ErrorObject

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Set-DistributionGroup], ParameterTransformationException
FullyQualifiedErrorId : [Server=DM6PR07MB8111,RequestId=00862c3b-e0f5-71b6-58e2-576237c4e372,TimeStamp=Tue, 24 Sep 2024 19:18:17 GMT],Write-ErrorMessage

[9/24/2024 1:18:17 PM] - Starting 10 second sleep before trying bulk update.
[9/24/2024 1:18:27 PM] - Bulk email address updating should be successful - test primary SMTP address
[9/24/2024 1:18:27 PM] - An error was detected during bulk updates - proceed with normal logic.
[9/24/2024 1:18:27 PM] - Attempting SMTP address updates per address.
[9/24/2024 1:18:27 PM] - Establishing group primary SMTP Address.
[9/24/2024 1:18:28 PM] - Processing address: x500:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=e64fb37947804c1aa69fda69aee0adf8-d81adc7a-ef
[9/24/2024 1:18:29 PM] - Processing address<EMAIL_ADDRESS>[9/24/2024 1:18:30 PM] - Processing address: X400:C=US;A= ;P=MBC;O=Exchange;S=ALLLCommittee;
[9/24/2024 1:18:31 PM] - Processing address: x400:C=US;A= ;P=MBC;O=Exchange;S=ALLL Committee;
[9/24/2024 1:18:31 PM] - Processing address: RFAX:ALLL Committee@
[9/24/2024 1:18:32 PM] - Processing address: CCMAIL:ALLL Committee at SLC
[9/24/2024 1:18:33 PM] - Processing address: MS:CMS/SLC/ALLLCOMMIT
[9/24/2024 1:18:33 PM] - Processing address<EMAIL_ADDRESS>[9/24/2024 1:18:34 PM] - Processing address<EMAIL_ADDRESS>[9/24/2024 1:18:34 PM] - Processing address<EMAIL_ADDRESS>[9/24/2024 1:18:35 PM] - Processing address<EMAIL_ADDRESS>[9/24/2024 1:18:36 PM] - Processing address: X500:/o=MBC/ou=UT/cn=Recipients/cn=ALLL Committee
[9/24/2024 1:18:37 PM] - Testing to ensure that new group primary SMTP address matches original group primary smtp address - loop until this is true.
[9/24/2024 1:18:37 PM] - Final test of primary SMTP address.
[9/24/2024 1:18:37 PM] - ********************************************************************************
ParameterName       Bound ParameterValue

groupSMTPAddress     True b1b93a1e-d01c-4a92-b56e-3d713dda27ca
groupTypeOverride   False
isUnifiedGroup      False False
isFirstPass         False False
Verbose             False
Debug               False
ErrorAction          True Stop
WarningAction       False
InformationAction   False
ErrorVariable       False
WarningVariable     False
InformationVariable False
OutVariable         False
OutBuffer           False
PipelineVariable    False
[9/24/2024 1:18:37 PM] - ********************************************************************************
[9/24/2024 1:18:37 PM] - ********************************************************************************
[9/24/2024 1:18:37 PM] - BEGIN GET-O365DLCONFIGURATION
[9/24/2024 1:18:37 PM] - ********************************************************************************
[9/24/2024 1:18:37 PM] - Obtaining Office 365 DL Configuration for evaluation.
[9/24/2024 1:18:37 PM] - Successfully obtained the Office 365 DL Configuration.
Name                         RecipientType

20240924T1306270341853995799 MailUniversalDistributionGroup
[9/24/2024 1:18:38 PM] - Testing if this is the first pass for DL validation.
[9/24/2024 1:18:38 PM] - This is not the first pass.
[9/24/2024 1:18:38 PM] - Group is not unified use standard DL commands.
[9/24/2024 1:18:38 PM] - Using Exchange Online to capture the distribution group.
[9/24/2024 1:18:38 PM] - Original DL configuration found and recorded.
[9/24/2024 1:18:38 PM] - END GET-O365DLCONFIGURATION
[9/24/2024 1:18:38 PM] - ********************************************************************************
[9/24/2024 1:18:38 PM] - Current primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:18:38 PM] - Office 365 prior primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:18:38 PM] - Although previously though successful - primary SMTP address still not updated.
[9/24/2024 1:18:38 PM] - ********************************************************************************
ParameterName       Bound ParameterValue

sleepString          True Primary SMTP address updates successful but not yet present - sleeping.
sleepSeconds         True 120
sleepParentID       False 0
sleepID             False 0
Verbose             False
Debug               False
ErrorAction         False
WarningAction       False
InformationAction   False
ErrorVariable       False
WarningVariable     False
InformationVariable False
OutVariable         False
OutBuffer           False
PipelineVariable    False
[9/24/2024 1:18:38 PM] - ********************************************************************************
[9/24/2024 1:18:38 PM] - ********************************************************************************
[9/24/2024 1:18:38 PM] - BEGIN  start-sleepProgess
[9/24/2024 1:18:38 PM] - ********************************************************************************
[9/24/2024 1:20:40 PM] - END start-sleepProgess
[9/24/2024 1:20:40 PM] - ********************************************************************************
[9/24/2024 1:20:40 PM] - Final test of primary SMTP address.
[9/24/2024 1:20:40 PM] - ********************************************************************************
ParameterName       Bound ParameterValue

groupSMTPAddress     True b1b93a1e-d01c-4a92-b56e-3d713dda27ca
groupTypeOverride   False
isUnifiedGroup      False False
isFirstPass         False False
Verbose             False
Debug               False
ErrorAction          True Stop
WarningAction       False
InformationAction   False
ErrorVariable       False
WarningVariable     False
InformationVariable False
OutVariable         False
OutBuffer           False
PipelineVariable    False
[9/24/2024 1:20:40 PM] - ********************************************************************************
[9/24/2024 1:20:40 PM] - ********************************************************************************
[9/24/2024 1:20:40 PM] - BEGIN GET-O365DLCONFIGURATION
[9/24/2024 1:20:40 PM] - ********************************************************************************
[9/24/2024 1:20:40 PM] - Obtaining Office 365 DL Configuration for evaluation.
[9/24/2024 1:20:40 PM] - Successfully obtained the Office 365 DL Configuration.
Name                         RecipientType

20240924T1306270341853995799 MailUniversalDistributionGroup
[9/24/2024 1:20:40 PM] - Testing if this is the first pass for DL validation.
[9/24/2024 1:20:40 PM] - This is not the first pass.
[9/24/2024 1:20:40 PM] - Group is not unified use standard DL commands.
[9/24/2024 1:20:40 PM] - Using Exchange Online to capture the distribution group.
[9/24/2024 1:20:41 PM] - Original DL configuration found and recorded.
[9/24/2024 1:20:41 PM] - END GET-O365DLCONFIGURATION
[9/24/2024 1:20:41 PM] - ********************************************************************************
[9/24/2024 1:20:41 PM] - Current primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:20:41 PM] - Office 365 prior primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:20:41 PM] - Although previously though successful - primary SMTP address still not updated.
[9/24/2024 1:20:41 PM] - ********************************************************************************
ParameterName       Bound ParameterValue

sleepString          True Primary SMTP address updates successful but not yet present - sleeping.
sleepSeconds         True 120
sleepParentID       False 0
sleepID             False 0
Verbose             False
Debug               False
ErrorAction         False
WarningAction       False
InformationAction   False
ErrorVariable       False
WarningVariable     False
InformationVariable False
OutVariable         False
OutBuffer           False
PipelineVariable    False
[9/24/2024 1:20:41 PM] - ********************************************************************************
[9/24/2024 1:20:41 PM] - ********************************************************************************
[9/24/2024 1:20:41 PM] - BEGIN  start-sleepProgess
[9/24/2024 1:20:41 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - END start-sleepProgess
[9/24/2024 1:22:42 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - Final test of primary SMTP address.
[9/24/2024 1:22:42 PM] - ********************************************************************************
ParameterName       Bound ParameterValue

groupSMTPAddress     True b1b93a1e-d01c-4a92-b56e-3d713dda27ca
groupTypeOverride   False
isUnifiedGroup      False False
isFirstPass         False False
Verbose             False
Debug               False
ErrorAction          True Stop
WarningAction       False
InformationAction   False
ErrorVariable       False
WarningVariable     False
InformationVariable False
OutVariable         False
OutBuffer           False
PipelineVariable    False
[9/24/2024 1:22:42 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - BEGIN GET-O365DLCONFIGURATION
[9/24/2024 1:22:42 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - Obtaining Office 365 DL Configuration for evaluation.
[9/24/2024 1:22:43 PM] - Successfully obtained the Office 365 DL Configuration.
Name                         RecipientType

20240924T1306270341853995799 MailUniversalDistributionGroup
[9/24/2024 1:22:43 PM] - Testing if this is the first pass for DL validation.
[9/24/2024 1:22:43 PM] - This is not the first pass.
[9/24/2024 1:22:43 PM] - Group is not unified use standard DL commands.
[9/24/2024 1:22:43 PM] - Using Exchange Online to capture the distribution group.
[9/24/2024 1:22:44 PM] - Original DL configuration found and recorded.
[9/24/2024 1:22:44 PM] - END GET-O365DLCONFIGURATION
[9/24/2024 1:22:44 PM] - ********************************************************************************
[9/24/2024 1:22:44 PM] - Current primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:22:44 PM] - Office 365 prior primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:22:44 PM] - Although previously though successful - primary SMTP address still not updated.
[9/24/2024 1:22:44 PM] - ********************************************************************************
ParameterName       Bound ParameterValue

sleepString          True Primary SMTP address updates successful but not yet present - sleeping.
sleepSeconds         True 120
sleepParentID       False 0
sleepID             False 0
Verbose            `
I have confirmed that the Primary SMTP address is populated in the O365 distro and it is correct. I even tried entering it again manually to see if it would then see that it was updated. The original distro is still sitting in the non synced OU. It has been looping since yesterday. I would like to understand what caused it so we can prevent it, and also how to best recover from this state. Like I said I think the new distro in 365 is configured correctly. The only difference I know of with this group is that it had a contact in O365 to allow external emails in to it as we are in a hybrid environment and our external mail flow goes directly to O365 instead of through on prem Exchange. Below are the parameters we are running with:
`ParameterName                           Bound ParameterValue

groupSMTPAddress                         True<EMAIL_ADDRESS>globalCatalogServer                      True dc.somedomain.com
activeDirectoryCredential                True System.Management.Automation.PSCredential
activeDirectoryAuthenticationMethod      True Negotiate
aadConnectServer                         True
aadConnectCredential                     True
aadConnectAuthenticationMethod           True Kerberos
exchangeServer                           True exchange.somedomain.com
exchangeCredential                       True System.Management.Automation.PSCredential
exchangeAuthenticationMethod             True Kerberos
exchangeOnlineCredential                 True
exchangeOnlineCertificateThumbPrint      True xxxxx
exchangeOnlineOrganizationName           True somedomaininc.onmicrosoft.com
exchangeOnlineEnvironmentName            True O365Default
exchangeOnlineAppID                      True xxxx
msGraphEnvironmentName                   True Global
msGraphTenantID                          True xxxx
msGraphCertificateThumbprint             True xxxx
msGraphApplicationID                     True xxxx
removeGroupViaGraph                      True False
logFolderPath                            True d:\Scripts\Azure AD\Distro Migrations\Logs
dnNoSyncOU                               True OU=do not sync dsn
retainOriginalGroup                      True True
enableHybridMailflow                     True True
groupTypeOverride                        True distribution
triggerUpgradeToOffice365Group           True False
overrideCentralizedMailTransportEnabled  True False
allowNonSyncedGroup                     False False
customRoutingDomain                      True
skipNestedGroupCheck                    False False
useCollectedFullMailboxAccessOnPrem      True False
useCollectedFullMailboxAccessOffice365   True True
useCollectedSendAsOnPrem                 True False
useCollectedFolderPermissionsOnPrem      True False
useCollectedFolderPermissionsOffice365   True False
dlNamePrefix                             True
dlNameSuffix                             True
threadNumberAssigned                     True 1
totalThreadCount                         True 1
isMultiMachine                           True False
remoteDriveLetter                        True
allowTelemetryCollection                 True True
allowDetailedTelemetryCollection         True True
isHealthCheck                           False False
Verbose                                 False
Debug                                   False
ErrorAction                             False
WarningAction                           False
InformationAction                       False
ErrorVariable                           False
WarningVariable                         False
InformationVariable                     False
OutVariable                             False
OutBuffer                               False
PipelineVariable                        False  `

This was new code put in to track when set calls are failing against the service.  Whats odd is that it's looking for the mail.onmicrosoft.com address to be primary.  You may have to abend it at this point.
Tim
From: mudsnowh2o @.>
Sent: Wednesday, September 25, 2024 5:33 PM
To: timmcmic/DLConversionV2 @.>
Cc: Subscribed @.***>
Subject: [timmcmic/DLConversionV2] Group migration stuck in a loop (Issue #184)
We are preparing for migrating all of our on prem distribution groups. On the third pilot set of groups one of them failed because we had a conflicting contact address in O365. I removed the contact and ran the migration again. It seemed to be proceeding fine and even moved the distro to the unsynced OU, deleted the synced distro from O365, and created the new distro with what looks like all of the correct attributes. The powershell job is stuck in a running state and I am seeing the following over and over again in the log:
`[9/24/2024 1:20:40 PM] - Testing if this is the first pass for DL validation.
[9/24/2024 1:20:40 PM] - This is not the first pass.
[9/24/2024 1:20:40 PM] - Group is not unified use standard DL commands.
[9/24/2024 1:20:40 PM] - Using Exchange Online to capture the distribution group.
[9/24/2024 1:20:41 PM] - Original DL configuration found and recorded.
[9/24/2024 1:20:41 PM] - END GET-O365DLCONFIGURATION
[9/24/2024 1:20:41 PM] - ********************************************************************************
[9/24/2024 1:20:41 PM] - Current primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:20:41 PM] - Office 365 prior primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:20:41 PM] - Although previously though successful - primary SMTP address still not updated.
[9/24/2024 1:20:41 PM] - ********************************************************************************
ParameterName Bound ParameterValue

sleepString True Primary SMTP address updates successful but not yet present - sleeping.
sleepSeconds True 120
sleepParentID False 0
sleepID False 0
Verbose False
Debug False
ErrorAction False
WarningAction False
InformationAction False
ErrorVariable False
WarningVariable False
InformationVariable False
OutVariable False
OutBuffer False
PipelineVariable False
[9/24/2024 1:20:41 PM] - ********************************************************************************
[9/24/2024 1:20:41 PM] - ********************************************************************************
[9/24/2024 1:20:41 PM] - BEGIN start-sleepProgess
[9/24/2024 1:20:41 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - END start-sleepProgess
[9/24/2024 1:22:42 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - Final test of primary SMTP address.
[9/24/2024 1:22:42 PM] - ********************************************************************************
ParameterName Bound ParameterValue

groupSMTPAddress True b1b93a1e-d01c-4a92-b56e-3d713dda27ca
groupTypeOverride False
isUnifiedGroup False False
isFirstPass False False
Verbose False
Debug False
ErrorAction True Stop
WarningAction False
InformationAction False
ErrorVariable False
WarningVariable False
InformationVariable False
OutVariable False
OutBuffer False
PipelineVariable False
[9/24/2024 1:22:42 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - BEGIN GET-O365DLCONFIGURATION
[9/24/2024 1:22:42 PM] - ********************************************************************************
[9/24/2024 1:22:42 PM] - Obtaining Office 365 DL Configuration for evaluation.
[9/24/2024 1:22:43 PM] - Successfully obtained the Office 365 DL Configuration.
Name RecipientType

20240924T1306270341853995799 MailUniversalDistributionGroup
[9/24/2024 1:22:43 PM] - Testing if this is the first pass for DL validation.
[9/24/2024 1:22:43 PM] - This is not the first pass.
[9/24/2024 1:22:43 PM] - Group is not unified use standard DL commands.
[9/24/2024 1:22:43 PM] - Using Exchange Online to capture the distribution group.
[9/24/2024 1:22:44 PM] - Original DL configuration found and recorded.
[9/24/2024 1:22:44 PM] - END GET-O365DLCONFIGURATION
[9/24/2024 1:22:44 PM] - ********************************************************************************
[9/24/2024 1:22:44 PM] - Current primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:22:44 PM] - Office 365 prior primary SMTP address<EMAIL_ADDRESS>[9/24/2024 1:22:44 PM] - Although previously though successful - primary SMTP address still not updated.
[9/24/2024 1:22:44 PM] - ********************************************************************************
I have confirmed that the Primary SMTP address is populated in the O365 distro and it is correct. I even tried entering it again manually to see if it would then see that it was updated. The original distro is still sitting in the non synced OU. It has been looping since yesterday. I would like to understand what caused it so we can prevent it, and also how to best recover from this state. Like I said I think the new distro in 365 is configured correctly. The only difference I know of with this group is that it had a contact in O365 to allow external emails in to it as we are in a hybrid environment and our external mail flow goes directly to O365 instead of through on prem Exchange. Below the parameters we are running with:
`ParameterName Bound ParameterValue

groupSMTPAddress True<EMAIL_ADDRESS>globalCatalogServer True dc.somedomain.com
activeDirectoryCredential True System.Management.Automation.PSCredential
activeDirectoryAuthenticationMethod True Negotiate
aadConnectServer True
aadConnectCredential True
aadConnectAuthenticationMethod True Kerberos
exchangeServer True exchange.somedomain.com
exchangeCredential True System.Management.Automation.PSCredential
exchangeAuthenticationMethod True Kerberos
exchangeOnlineCredential True
exchangeOnlineCertificateThumbPrint True xxxxx
exchangeOnlineOrganizationName True cardworksinc.onmicrosoft.com
exchangeOnlineEnvironmentName True O365Default
exchangeOnlineAppID True xxxx
msGraphEnvironmentName True Global
msGraphTenantID True xxxx
msGraphCertificateThumbprint True xxxx
msGraphApplicationID True xxxx
removeGroupViaGraph True False
logFolderPath True d:\Scripts\Azure AD\Distro Migrations\Logs
dnNoSyncOU True OU=do not sync dsn
retainOriginalGroup True True
enableHybridMailflow True True
groupTypeOverride True distribution
triggerUpgradeToOffice365Group True False
overrideCentralizedMailTransportEnabled True False
allowNonSyncedGroup False False
customRoutingDomain True
skipNestedGroupCheck False False
useCollectedFullMailboxAccessOnPrem True False
useCollectedFullMailboxAccessOffice365 True True
useCollectedSendAsOnPrem True False
useCollectedFolderPermissionsOnPrem True False
useCollectedFolderPermissionsOffice365 True False
dlNamePrefix True
dlNameSuffix True
threadNumberAssigned True 1
totalThreadCount True 1
isMultiMachine True False
remoteDriveLetter True
allowTelemetryCollection True True
allowDetailedTelemetryCollection True True
isHealthCheck False False
Verbose False
Debug False
ErrorAction False
WarningAction False
InformationAction False
ErrorVariable False
WarningVariable False
InformationVariable False
OutVariable False
OutBuffer False
PipelineVariable False `

Reply to this email directly, view it on GitHubhttps://github.com/timmcmic/DLConversionV2/issues/184, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKGTN6LCOPVMANOVUGY3VOLZYMT2JAVCNFSM6AAAAABO3OVMICVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2DSMBTG4YDQNQ.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>

If it is expecting the onmicrosoft address to be primary, what do you think it would do if I set that address to primary, just to see if it allows the script to gracefully finish, then I can set the proper address back to primary when it is done.

Actually that's a great idea!
From: mudsnowh2o @.>
Sent: Thursday, September 26, 2024 10:28 AM
To: timmcmic/DLConversionV2 @.>
Cc: Tim McMichael @.>; Comment @.>
Subject: Re: [timmcmic/DLConversionV2] Group migration stuck in a loop (Issue #184)
If it is expecting the onmicrosoft address to be primary, what do you think it would do if I set that address to primary, just to see if it allows the script to gracefully finish, then I can set the proper address back to primary when it is done.

Reply to this email directly, view it on GitHubhttps://github.com/timmcmic/DLConversionV2/issues/184#issuecomment-2377136337, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKGTN6PF6ISIKBJITUY3WV3ZYQKWXAVCNFSM6AAAAABO3OVMICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGEZTMMZTG4.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

That did it, migration successful. Thank you so much for your quick response. I did have one other question, after a migration is successful, should we be leaving the 3 new objects created on prem (dyn distro, renamed distro, contact) in a synced OU, or should we move them to an unsynced OU?

It is fine to have it all in the sycn OU - the contact is synced in case you need to nest DLs -> that's how we make sure mail flow works.
Tim
From: mudsnowh2o @.>
Sent: Thursday, September 26, 2024 12:35 PM
To: timmcmic/DLConversionV2 @.>
Cc: Tim McMichael @.>; Comment @.>
Subject: Re: [timmcmic/DLConversionV2] Group migration stuck in a loop (Issue #184)
That did it, migration successful. Thank you so much for your quick response. I did have one other question, after a migration is successful, should we be leaving the 3 new objects created on prem (dyn distro, renamed distro, contact) in a synced OU, or should we move them to an unsynced OU?

Reply to this email directly, view it on GitHubhttps://github.com/timmcmic/DLConversionV2/issues/184#issuecomment-2377437424, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKGTN6PZ37QP3CR42RKEPN3ZYQZR3AVCNFSM6AAAAABO3OVMICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGQZTONBSGQ.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

Thanks again. Just so you know, I didn't even have to change the 365 distro back to the proper final primary address, it set it correctly once I change the primary address to what you said it was expecting it to be.

Excellent!  I included this new logic and this is the first time it's failed - there have been some interesting issues in the service where powershell calls are failing and I'm still tracking it down.
From: mudsnowh2o @.>
Sent: Thursday, September 26, 2024 12:40 PM
To: timmcmic/DLConversionV2 @.>
Cc: Tim McMichael @.>; Comment @.>
Subject: Re: [timmcmic/DLConversionV2] Group migration stuck in a loop (Issue #184)
Thanks again. Just so you know, I didn't even have to change the 365 distro back to the proper final primary address, it set it correctly once I change the primary address to what you said it was expecting it to be.

Reply to this email directly, view it on GitHubhttps://github.com/timmcmic/DLConversionV2/issues/184#issuecomment-2377447530, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKGTN6K56GQPD4PUK7H6U73ZYQ2GHAVCNFSM6AAAAABO3OVMICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGQ2DONJTGA.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

If you need any more of the logs or information from me to help, just let me know.


Preference to always show the date, do not show Yesterday or Today

I use Vienna to check RSS sites, but to archive interesting articles I transfer to other application, but the date is show as Today or Yesterday the mayority of the time, so I need to change to the "real" date.
I think a new preference is needed for this problem, I suppose I am not the only one who wants this.

That would mean to change some date formatters, which should be no big deal. Feel free to ask for an update for this if nothing happens a month from now, or try the implementation yourself (or ask a friend) :)


SF: Usage of Paratext approved books only for training

See Issue 18 here: https://docs.google.com/spreadsheets/d/13Y8d3z3JajAoR2B1zDbsjb0q_GLVQaB6iX9rZPM9it4/edit#gid=0

See https://jira.sil.org/browse/SF-2626


Upgrade to CXF 3.1.9

Requires a new fabric8 release
https://github.com/fabric8io/fabric8/pull/6642


Cannot find module 'protractor-console'

This is how I used the plugin and it shows can not find the module?
plugins: [{
    package: 'protractor-console',
    logLevels: ['severe']
}]

Hi @harryyuanfeng.Try using require.resolve:
plugins: [{
  path: require.resolve('protractor-console'),
  logLevels: ['severe'] ,
}],

Closing due to inactivity


Evaluate: numerical metric can result in logging e.g. "Average Metric: 49 / 10"

Description
When using a metric that can be higher than 1, evaluate can produce logs like "Average Metric: 49 / 10"
This is due to the score being added to the count of correct answers, without normalising:
https://github.com/stanfordnlp/dspy/blob/4323844ccae2289d7505a8f2922183140ed289fa/dspy/evaluate/evaluate.py#L120
Maybe for now the docs should mention that scores should be normalised between 0 and 1?

Thanks @raphaelmerx ! I don't see a problem here. The score can exceed 1.0 and it's OK.


Event reminder is not updating in iOS.

Hi team,
I have created an event with reminder duration as 0 minutes (which is at the time of event).  And later on when i tried to change it from 0 to XX minutes.  It not updating in device calendar.  This issue occurs only in iOS devices.
Code snippet:
Event _event = new Event(writableCalendarId,
eventId: shift.localShiftId != "0" ? shift.localShiftId : null);
_event.title = AppStrings.REMINDER_TITLE;
_event.start = shift.startDate;
_event.end = shift.endDate;
_event.description =
"Help message";
_event.reminders = [
new Reminder(minutes: ConfigUtil.getReminderTime())
];
_event.location = shift.storeName;
_event.allDay = false;
      var result = await _deviceCalendarPlugin.createOrUpdateEvent(_event);

Please let me know the work around for this.

Hi,
Yes.  All other properties are getting reflected in Device calendar reminder.
Only with the above scenario, my device calendar reminder is not reflecting reminder time properly.

@nickrandolph Any update on this?

There is something fishy going on with the loading of reminders. I use iOS 15.4. An event saved in iOS Calendar with a reminder, then accessed with device_calendar like  print('Reminders: ' + event.reminders.toString()); returns Reminders: [], but all other data in the event is loading ok. Saving a reminder using device_calendar works fine and is visible in the iOS Calendar, but accessing it using device_calendar returns [].

This might be a bug but I'm not sure
Are you using the latest version?

If the question was directed at me so yes, 4.2.0.

Same error with saved reminders not getting loaded into flutter app using device_calendar on android emulator.  So both iOS and Android affected it seems. I have had a quick look at the flutter code loading events, but no obvious errors that I can see (but I am no expert...).

Did some further digging, and the error was on my side. Removing my above comments in order not to cause confusion. I apologise. (I am indeed not an expert...)


Automated cherry pick of #9785: guest_deploy_task: log other deploy details with i18n

Cherry pick of #9785 on release/3.7.
#9785: guest_deploy_task: log other deploy details with i18n

Codecov Report

Merging #9786 (827c298) into release/3.7 (56d583e) will increase coverage by 2.06%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.7   #9786       +/-   ##
===============================================
+ Coverage         6.00%   8.06%    +2.06%
===============================================
  Files              845     107      -738
  Lines           131245   12978   -118267
===============================================
- Hits              7879    1047     -6832
+ Misses          122665   11811   -110854
+ Partials           701     120      -581

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/esxi/host.go
0.77% <0.00%> (ø)

pkg/multicloud/esxi/image.go
0.00% <ø> (ø)

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/snapshot.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storage.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storagecache.go
0.00% <ø> (ø)

pkg/multicloud/esxi/template.go
0.00% <ø> (ø)

pkg/multicloud/esxi/vdisk.go
0.00% <ø> (ø)

pkg/multicloud/esxi/virtualmachine.go
0.00% <0.00%> (ø)

pkg/compute/models/loadbalancerlisteners.go

... and 662 more

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 77227ca...827c298. Read the comment docs.

Codecov Report

Merging #9786 (827c298) into release/3.7 (56d583e) will increase coverage by 2.06%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.7   #9786       +/-   ##
===============================================
+ Coverage         6.00%   8.06%    +2.06%
===============================================
  Files              845     107      -738
  Lines           131245   12978   -118267
===============================================
- Hits              7879    1047     -6832
+ Misses          122665   11811   -110854
+ Partials           701     120      -581

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/esxi/host.go
0.77% <0.00%> (ø)

pkg/multicloud/esxi/image.go
0.00% <ø> (ø)

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/snapshot.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storage.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storagecache.go
0.00% <ø> (ø)

pkg/multicloud/esxi/template.go
0.00% <ø> (ø)

pkg/multicloud/esxi/vdisk.go
0.00% <ø> (ø)

pkg/multicloud/esxi/virtualmachine.go
0.00% <0.00%> (ø)

pkg/compute/models/loadbalancerlisteners.go

... and 662 more

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 77227ca...827c298. Read the comment docs.


Alarm clock

Alarm Clock
Project Details: We use the alarm in our day to day life that gives an audio or visual reminder about a certain condition. Using Python you need to build an alarm software that allows users to set time for a certain condition and when the condition is met it should give an audio signal. This tool will work from the user’s laptop or desktop device.

I am interested to work on this issue can u assign me to this?

Ma'am can I work on this?

I am interested to work on this issue.Can I work on it?

I sent a pull request. Can you check it out?


not working

i tried to use this in my project as you mentioned. but its not working

Please refer to the example codepen. If you follow the exact same steps it will work for sure.


Need to add multiple menus with different content types

For some reason when i add a second menu item with different content type other than api::page.page it wont show up when i create a new menu in admin. It only ever shows "Pages", where as it should also now show "HelpForms"
for example i have created a new content type called "api::help-form.help-form" and it wont show in the dropdown? any ideas why?
My config is below::
module.exports = ({ env }) => ({
navigation: {
enabled: true,
config: {
additionalFields: ["audience"],
contentTypes: ["api::page.page", "api::help-form.help-form"],
contentTypesNameFields: {
"api::page.page": ["title"],
"api::help-form.help-form": ["title"],
},
allowedLevels: 2,
gql: {},
},
},
});

Its ok I solved this. maybe worth putting in documentation that you need to rebuild admin "yarn build" for the Navigation Plugin to show-up in settings  otherwise this don't work as they should :)

Since v2.0.2 config file is only a store for restoring configuration. If you changed it you have to restore config through the Settings Page for the file to be synchronized with the working configuration.
Creating your own configuration through the plugins.js file is very error-prone. Please try to avoid it and use the plugin's new Settings Page to avoid all possible problems with configuration.

Closing as answered.


Strange scroll after new data loads

I was wondering is someone could help. This is not an issue with the plugin but with my code I expect.
I have inherited development of this site and one thing they asked is for an infinite scroll feature.
It all works fine (to an extent). But when the new data loads the page does this strange scroll, which can be annoying when you are trying to add products to the cart, as suddenly your mouse is hovering over the wrong product..
The dev page is here
http://doorstep.vegemitetoast.com/index.php?route=product/category&path=1
If you scroll down a bit you'll see what happens. I'm probably missing something really obvious.
Thanks in advance for any help.

You should try setting the animate option to false. This isn't really an error with the code at all, so I'm going to close this issue.


Google translate

ability to use the spotlight function to translate the webpage to another language of choice

built into Chrome! will show folks how to use it 👍


build-node-package.nix takes excessive amount of time

Issue description
A profile of NIX_COUNT_CALLS=1 nix-env -qa --drv-path on Nixpkgs master shows that build-node-package.nix is the most dominant function during evaluation:
calls to 9295 functions:
    210846 anonymous function at /home/eelco/Dev/nixpkgs-stable/pkgs/development/web/nodejs/build-node-package.nix:314:33
    201017 anonymous function at /home/eelco/Dev/nixpkgs-stable/pkgs/tools/typesetting/tex/texlive-new/combine.nix:31:36
    201017 anonymous function at /home/eelco/Dev/nixpkgs-stable/pkgs/tools/typesetting/tex/texlive-new/combine.nix:31:39
     93926 ‘optional’ at /home/eelco/Dev/nixpkgs-stable/lib/lists.nix:175:14
     93926 ‘optional’ at /home/eelco/Dev/nixpkgs-stable/lib/lists.nix:175:20
...

In fact about 23% of Nixpkgs evaluation time is spent in nodejs stuff.
This is strange because hardly any nodejs packages are included in the output:
$ nix-env -f ~/Dev/nixpkgs -qa --drv-path | grep nodejs | wc -l
14

So it looks like there is some opportunity for optimisation here...
Steps to reproduce
Technical details

System: 16.03.git.7a41a40M
Nix version: 1.11.2
Nixpkgs version: 8a84fc0217344990b646cbfbf01037b935407a40

I wonder, how do you know 23% of time is spent on nodejs stuff?

Just by disabling node-packages.nix:
diff --git a/pkgs/top-level/node-packages.nix b/pkgs/top-level/node-packages.nix
index d8eb668..3d9cf8d 100644
--- a/pkgs/top-level/node-packages.nix
+++ b/pkgs/top-level/node-packages.nix
@@ -15,7 +15,7 @@
 , ...
 } @ args:

-with stdenv.lib;
+with stdenv.lib; assert false;

 let
   removeDeps = remove: deps: filterAttrs (n: d: all (r: r != d.pkgName) remove) deps;

There is some deep magic in pkgs/development/web/nodejs/build-node-package.nix.
So hopefully https://github.com/NixOS/nixpkgs/pull/16886 will yield https://github.com/NixOS/nixpkgs/issues/14532

@svanderburg how is the new code performance comparing to previous?

This seems to be fixed (texlive is now at the top of that listing).

Yep, looks fine


Ruby 2.7 warning

Ruby 2.7 warning is shown when using dry-validation with option when options are added without **

Affects my production application: YES
Ruby version: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
Reproducing script:

require 'bundler/inline'

gemfile do
  source 'https://rubygems.org'
  gem 'dry-validation', require: false
end

require 'dry-validation'

class CustomForm < Dry::Validation::Contract
  option :foo
  params {}
end

options = { foo: 'foo' }
CustomForm.new(**options) # no warning
CustomForm.new(options) # shows warning
# /.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/dry-initializer-3.0.4/lib/dry/initializer/mixin/root.rb:7: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
# (eval):2: warning: The called method `__dry_initializer_initialize__' is defined here

Options supposed to be passed as keyword arguments so this warning is correct. CustomForm.new(options) will stop working in future ruby versions. Ruby used to do some non-trivial trickery in earlier versions but it never worked perfectly, so they decided to separate keywords completely.

That's very cool that you answer so quickly)
But it was not trivial to find how to reproduce this warning in my app, so I think you rush a little bit to close issue.
Warning says __dry_initializer_initialize__ should send keyword args and nothing about application context. Its totally possible it is raised in other situations.
So I think  fix should be added to __dry_initializer_initialize__

Unfortunately, this cannot be "fixed" on the dry-initializer side. The warning is issued by ruby and it contains only one line of the call stack.
You can use https://github.com/jeremyevans/ruby-warning to raise these warnings to errors turning them into hard errors. This way you'll see the full backtrace.
require 'warning'

Warning.process { raise _1 if _1.match?(/keyword parameters is deprecated/) }


feat(publick8s) install geoipdata chart

Related to https://github.com/jenkins-infra/helpdesk/issues/4240
This PR installs the new chart geoipupdates in a new namespace geoipdata.
Requires:

https://github.com/jenkins-infra/azure/pull/803 to have a provisioned PVC in the namespace geoipdata
https://github.com/jenkins-infra/helm-charts/releases/tag/geoipupdates-0.0.1 (first release of the chart)
https://github.com/jenkins-infra/charts-secrets/commit/78d89c557a9863219d087023abf4fd180ed7add6 for the secrets

Tested locally once with success
Helmfile diff looks good


feat(core): reset password

What/Why?
This PR adds functionality to reset password for Customer and includes 2 steps:

reset password email,
change password

it's based on PR with mutations.
Testing
locally

Needs changeset 🦋

Looks good but we do need to know if we want to have a different path to reset passwords other than reusing /login 🤔

Yeah, it's a good point, Jorge. Now, when RequestResetPasswordInput can deal with path, I've added it to submit function also. I believe it should be done explicitly since if we skip this argument on calling submit fn we get next result - https://your-store/login.php?c=XX&t=XXX. In this way it inherits || reproduces current stencil behaviour, if we miss completely path in arguments, we get smth like https://your-store?c=XX&t=XXX.
So to receive https://your-store?login?c=XX&t=XXX I'm providing  it as an argument:
submitResetPasswordForm({ formData, reCaptchaToken, path: '/login' });


chore(deps): add OTEL tracing and span logging for GRPC server

TL;DR
Removed trace.WithNewRoot() from OpenTelemetry span creation and added tracing to GRPC requests.
What changed?

Removed trace.WithNewRoot() parameter from all otel.Tracer(TracerName).Start() calls across multiple files.
Added OpenTelemetry tracing to GRPC requests in the logGRPC function.
Updated the context in logGRPC to include trace and span IDs.

How to test?

Run the CSI driver with OpenTelemetry tracing enabled.
Perform various CSI operations (e.g., CreateVolume, DeleteVolume, NodePublishVolume).
Verify that the traces are correctly propagated and that GRPC requests are now included in the trace.
Ensure that removing trace.WithNewRoot() doesn't negatively impact the existing tracing functionality.

Why make this change?
This change improves the tracing capabilities of the CSI driver:

Removing trace.WithNewRoot() allows for better trace continuity across operations, potentially providing more context in distributed tracing scenarios.
Adding tracing to GRPC requests provides more granular insights into the communication between components, helping with debugging and performance analysis.

These improvements will enhance observability and make it easier to diagnose issues in production environments.

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

#361  👈
#358 : 2 other dependent PRs (#359 , #360 )
dev

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

Join @sergeyberezansky and the rest of your teammates on  Graphite

Merge activity

Oct 10, 12:13 PM EDT: A user started a stack merge that includes this pull request via Graphite.