CIP-0069: alternative approach

I had a conversation about this CIP several weeks ago with a few others, including @lehins from the ledger team. This seems desirable to do, easy to implement (on both the Plutus and the ledger side), and if we want it in Plutus V3 then it must be done soon.
I'm opening this issue to discuss an alternative approach: the problem with the proposed approach is that it adds a ScriptArgs argument, which leads to the "ugly unchecked dependence" problem as pointed out in https://github.com/cardano-foundation/CIPs/pull/321#issuecomment-1250053504. But this doesn't seem necessary: we can simply use two different types for scriptContextPurpose, and the key of txInfoRedeemers. E.g., Alexey suggested that we can create a ScriptPurposeWithDatum type for scriptContextPurpose, while keeping the txInfoRedeemers key type as it is, which would avoid the problem.
If we can agree and settle on the design soon, it should have a good chance to be done in time for Plutus V3. @KtorZ @michaelpj @zygomeb

I don't find the unchecked dependence problem to be that bad, but I also don't desperately hate the combined thing. Perhaps we could give it a different name. ScriptInfo? IDK.
I was going to say that the unchecked approach would make it easier if we decided to allow the spending of script outputs without datums. But if we did that we would probably need to tie it to a new ledger language anyway, in which case we could change the ScriptInfo type just as easily.

I made some updates to CIP 69 to mention the no datum case, but looks like the typing for ScriptInfo is better since you don't end up with an impossible type combination of ScriptArgs DatumAndRedeemer with a ScriptPurpose of Mint, Withdraw, etc.

@rphair has this been discussed and what was the outcome?

@zliu41 The outdone was to discuss with the Plutus Core team next CIP meeting to get the path forward that everyone is most comfortable implementing.
It sounds like the approach talked about in this issue is a more wholistic approach for typing validators.
We can also continue the discussion here in the comments. I can update the pr to reflect any changes decided on and finalized here.

I would love to see this implemented.
It is a prerequisite for smart wallets if we want them to have a smooth and intuitive UX .
I will also be implementing the Plutus-wallet connector soon and hopefully we can get this section of the market going, so having it in Plutus V3 will help everything accelerate .
Lots of innovation waiting to be unlocked.

If we are going to incorporate making the datum optional, then I think we should also propose the corresponding change to the ledger rules to make it legal to spend outputs without datums.

propose the corresponding change to the ledger rules to make it legal to spend outputs without datums.

We can continue the discussion of that in CIP-87. The only reason it is related to CIP-69 is because the original ScriptArg proposal accidentally did what CIP-87 wants. If we go with the ScriptInfo approach then these two CIPs are completely orthogonal.

I don't think they're orthogonal, since you have to decide here if you're going to have Datum or Maybe Datum in the spending purpose. It's weird to have Maybe Datum if we're not going to make that legal. So they are coupled!


Enum returning caption instead of value

Describe the bug
When trying to use an enum and send it to an API, it is sending the caption instead of the value.
To Reproduce
Have an enum :
enum 50000 TestEnum
{
    Extensible = true;

    value(0; "")
    {
        Caption = '';

    }
    value(1; "AF")
    {
        Caption = 'AF - Actualité financière';
    }
    value(2; "CN")
    {
        Caption = 'CN - Sinistres';
    }

Use this enum in a table :

table 50000 CompanyTheme
{
    Caption = 'CompanyTheme';
    DataClassification = ToBeClassified;

    fields
    {
        field(1; ID; Integer)
        {
            Caption = 'ID';
            DataClassification = CustomerContent;
            AutoIncrement = true;
            Editable = false;
        }
        field(2; "Thème"; Enum TestEnum)
        {
            Caption = 'Thème';
            DataClassification = CustomerContent;
        }

In a codeunit,
`var
CompanyTheme : Record CompanyTheme

this line is the issue :

payload := '&DateDebut=' + dateDebut + '&DateFin=' + DateFin + '&Theme=' + FORMAT(CompanyTheme."Thème");`

Expected behavior*
I think CompanyTheme."Thème" should return AF and not "AF - Actualités financières" because I need to send to my API only the AF and I don't think just cutting the first 2 string of Theme is the right idea...
5. Versions:

AL Language: 4.0.209944
Business Central: 15.1 (and 15.2)

This is by design. The Format works the same way as for Option fields to ensure backwards compatibility.
The scenario is perfectly valid though. Unfortunately we don't have an ideal way of doing this right now. From Version 4.0 of AL you can do something like
    procedure GetEnumValueName(e: enum TestEnum): Text;
    var
        index: Integer;
        name: Text;
    begin
        index := e.Ordinals.IndexOf(e.AsInteger());
        e.Names.Get(index, name);
        exit(name);
    end;

    procedure GetEnumValueName(fref: FieldRef): Text;
    begin
        exit(fref.GetEnumValueNameFromOrdinalValue(fref.Value));
    end;

Thanks for the response,
That seems to be a long way to do something that should be easily done but it works for now! thanks for the tips 👍


Error when Running Module 3: Obfuscating existing file

Whenever I try to run python3 main.py > module 3 I always get the following error:
    obfuscator.MainMenu(name)```

This is for any file that I choose and any format. I am trying to encode meterpreter payloads.

 File "/Users/thejman/Documents/malware/OSRipper/main.py", line 405, in postgen
    obfuscator.MainMenu(name)
NameError: name 'name' is not defined

I am pushing the fix right now. Thanks for letting me know about this

No problem! I fixed this on my own instance. This program is fantastic! I have another issue but I can submit it separately if you would like.

No problem! I fixed this on my own instance. This program is fantastic! I have another issue but I can submit it separately if you would like.

Sorry i haven't been very attentive lately so I didn't see that u had another issue. Please create it. Sorry again

You absolutely don’t need to apologize haha. You have made an amazing
program that will be pivotal to my red teaming work.
In fact, I’m not the greatest programmer in the world but I’m getting there
and my debugging skills are getting better. If you are open to some
collaboration/help then I’d love to help with this project.
I will recreate it sometime this weekend!
Regards,
Jeff
On Fri, Oct 21, 2022 at 6:54 PM subs @.***> wrote:

No problem! I fixed this on my own instance. This program is fantastic! I
have another issue but I can submit it separately if you would like.
Sorry i haven't been very attentive lately so I didn't see that u had
another issue. Please create it. Sorry again
—
Reply to this email directly, view it on GitHub
https://github.com/SubGlitch1/OSRipper/issues/15#issuecomment-1287511634,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOB4IZSAVIOC7L7SRIC6ALDWEMNI5ANCNFSM6AAAAAAQYF7R3E
.
You are receiving this because you authored the thread.Message ID:
@.***>

You absolutely don’t need to apologize haha. You have made an amazing
program that will be pivotal to my red teaming work.
In fact, I’m not the greatest programmer in the world but I’m getting there
and my debugging skills are getting better. If you are open to some
collaboration/help then I’d love to help with this project.
I will recreate it sometime this weekend!
Regards,
Jeff
On Fri, Oct 21, 2022 at 6:54 PM subs @.***> wrote:

No problem! I fixed this on my own instance. This program is fantastic! I
have another issue but I can submit it separately if you would like.
Sorry i haven't been very attentive lately so I didn't see that u had
another issue. Please create it. Sorry again
—
Reply to this email directly, view it on GitHub
https://github.com/SubGlitch1/OSRipper/issues/15#issuecomment-1287511634,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOB4IZSAVIOC7L7SRIC6ALDWEMNI5ANCNFSM6AAAAAAQYF7R3E
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sure you are more than welcome to open a pull request


WIP - Separate job runner logic from operations

Based on https://github.com/huggingface/datasets-server/pull/1142, this is a proposal to start separating operation logic like compute, pre-compute and post-compute from Job Runner so that, it will be easier to switch to an orchestrator some day.
I introduce "operators" concept which can be defined as a class that only compute (pre and post) a result and then it is managed in job runner.
An operator do not need to know about other actions like store cache, validate if there already exist a parallel cache, validate if it has to skip the compute or other actions different than "compute" the response.
I also introduce parent classes dataset_job_operator, config_job_operator and split_job_operator (They are different in the attributes needed by each operator, it will close https://github.com/huggingface/datasets-server/issues/1074).
I think this way we could extend in the future more levels of granularity (Like partitions for example for https://github.com/huggingface/datasets-server/issues/1087
This is just a POC and might need more teaks.
So far, it is pending:

[ ] Fix unittests
[ ] Refactor in some classes

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


abap2xlsx - Workbook protect

hi,
is it still not possible to have the workbook protect?
I've read in SCN that its not possible, and also tried to edit ZDEMO_EXCEL18 but still no luck.
Thank you.

If you want to block the access to the excel with a password, it is not possible, because it is not a OOXML standard but a functionality implemented by Microsoft (binary).
If you want to lock (with or without password) the workbook and/or the worksheet by changes you can using the proper methods.
Ivan


Update stratagem cli wording

replace the word configure with interval.
Signed-off-by: Joe Grund<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1162   +/-   ##
=======================================
  Coverage   95.39%   95.39%
=======================================
  Files           2        2
  Lines         152      152
=======================================
  Hits          145      145
  Misses          7        7

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 51e9586...5170058. Read the comment docs.


Double click to enter Operator only works when Parameters window open

close parameter window
double click on an operator

expected behaviour: Operator is opened
actual behaviour: popup with parameters, empty frame when op has no parameter
Not sure if it is by design, but it is a bit confusing IMO
version 3.5.0

It's a bug that is sadly hard to fix.
A workaround is to click an operator while holding the Shift key.


from_encoding does not work

I get - Imported file has a wrong encoding: 'utf-8' codec can't decode byte 0xb9 in position 254: invalid start byte.
Despite using from_encoding set to iso-8859-2, iso-8859-1, iso-8859.

I get:
Imported file has a wrong encoding: 'ascii' codec can't decode byte 0xc3 in position 31: ordinal not in range(128)

Even though I only get this problem in deploy and not in development.
From_encoding is set to utf-8 and I have installed:
django-import-export==2.1.0
tablib==2.0.0

Duplicate of #1141


Add setupbase.py to MANIFEST.in

To package nbclassic for conda: https://github.com/conda-forge/staged-recipes/pull/12722

Looks like an alternative would be to switch to jupyter_packaging instead: https://github.com/jupyterlab/nbclassic/pull/25


July 2019 guest OS patches list appears to have a broken link

This section https://docs.microsoft.com/en-us/azure/cloud-services/cloud-services-guestos-msrc-releases#july-2019-guest-os (for July 2019 image) contains the following line:
Rel 19-07 | 4506621 | Windows Security | 2.88, 3.75, 4.68 | July 9, 2019
The link under the KB number is https://support.microsoft.com/kb/4506621 which when it's followed redirects to https://support.microsoft.com/af-za/help/4506621 where I see a page which looks like a 404 "not found" page which says
Jammer, bladsy nie gevind nie
Probeer Microsoft-ondersteuning deursoek om ’n oplossing te vind

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

ID: 3a8cc2c5-eb5f-edaf-f155-98e5ff1b252c
Version Independent ID: 8e1a1933-e037-d682-5ba0-50d0f85f12e8
Content: List of updates applied to the Azure Guest OS
Content Source: articles/cloud-services/cloud-services-guestos-msrc-releases.md
Service: cloud-services
GitHub Login: @raiye
Microsoft Alias: raiye

Thanks for the feedback! We are currently investigating and will update you shortly.

@Erik Swart (TEKsystems<EMAIL_ADDRESS>to assist
Get Outlook for Androidhttps://aka.ms/ghei36

From: Micah<EMAIL_ADDRESS>Sent: Friday, August 2, 2019 9:14:43 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Rashmi Iyer<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
Thanks for the feedback! We are currently investigating and will update you shortly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F36386%3Femail_source%3Dnotifications%26email_token%3DAE64IMJUZAOHJRICHVPBOITQCRMPHA5CNFSM4II3XLVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OGFWQ%23issuecomment-517759706&data=02|01|raiye%40microsoft.com|f28cc040d36c437ea61a08d7176487d0|72f988bf86f141af91ab2d7cd011db47|1|0|637003592909980159&sdata=rXg1ZMuAl1RqQT3x2mDaghtJZyhjVUJ7ICpXjw4QpHQ%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE64IMJ3CRPYC5EZAE7HNUTQCRMPHANCNFSM4II3XLVA&data=02|01|raiye%40microsoft.com|f28cc040d36c437ea61a08d7176487d0|72f988bf86f141af91ab2d7cd011db47|1|0|637003592909990148&sdata=ZCcVS5ft7Lz1%2BJMp9nnlnozrjP07gxOEbFplZB7tg10%3D&reserved=0.

FYI:  Looking into it now.
-Erik Swart
Program Manager | Azure Compute | v-erswar<EMAIL_ADDRESS>[Microsoft Logo]
From: Rashmi Iyer<EMAIL_ADDRESS>Sent: Friday, August 2, 2019 9:51 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Erik Swart (TEKsystems Inc<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
@Erik Swart (TEKsystems<EMAIL_ADDRESS>to assist
Get Outlook for Androidhttps://aka.ms/ghei36

From: Micah <notifications<EMAIL_ADDRESS>Sent: Friday, August 2, 2019 9:14:43 AM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Rashmi Iyer <raiye<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
Thanks for the feedback! We are currently investigating and will update you shortly.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F36386%3Femail_source%3Dnotifications%26email_token%3DAE64IMJUZAOHJRICHVPBOITQCRMPHA5CNFSM4II3XLVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OGFWQ%23issuecomment-517759706&data=02|01|v-erswar%40microsoft.com|32bc3ca99e70413cf8e108d71769a515|72f988bf86f141af91ab2d7cd011db47|1|0|637003614819403552&sdata=CfYA81Zr3ssjaSs5QS31B6UWIXXbZi6EqImn6S5FS%2Bw%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE64IMJ3CRPYC5EZAE7HNUTQCRMPHANCNFSM4II3XLVA&data=02|01|v-erswar%40microsoft.com|32bc3ca99e70413cf8e108d71769a515|72f988bf86f141af91ab2d7cd011db47|1|0|637003614819413549&sdata=TP5X1jWWlGKQUAcDCAgiBzzYrLrc9fRFwntxM%2BYuUrA%3D&reserved=0.

@raiye looks like there is nothing related to that KB anymore. I submitted a PR to remove it from the list. I will wait on sign off to ensure that is what you want to do. Let me know and I can merge it.

@Erik Swart (TEKsystems<EMAIL_ADDRESS>to have the final say
-Rashmi Iyer
From: Micah<EMAIL_ADDRESS>Sent: Friday, August 2, 2019 12:48 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Rashmi Iyer<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
@raiyehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fraiye&data=02|01|raiye%40microsoft.com|aa81ff77b33f4026f8fe08d7178262d7|72f988bf86f141af91ab2d7cd011db47|1|0|637003721134113557&sdata=UxP7bTfYixc%2BcT9sbTPUhrn4nn2pWfccns717ZxHZcs%3D&reserved=0 looks like there is nothing related to that KB anymore. I submitted a PR to remove it from the list. I will wait on sign off to ensure that is what you want to do. Let me know and I can merge it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F36386%3Femail_source%3Dnotifications%26email_token%3DAE64IMPQQEAUIUFZRHRC46LQCSFQVA5CNFSM4II3XLVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OVYII%23issuecomment-517823521&data=02|01|raiye%40microsoft.com|aa81ff77b33f4026f8fe08d7178262d7|72f988bf86f141af91ab2d7cd011db47|1|0|637003721134118552&sdata=uatc0IzQ86e5N5hSU6GtLTvEKJ0N8DH%2BCgv5SGjAWyM%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE64IMJAN52VAR762DYW4FTQCSFQVANCNFSM4II3XLVA&data=02|01|raiye%40microsoft.com|aa81ff77b33f4026f8fe08d7178262d7|72f988bf86f141af91ab2d7cd011db47|1|0|637003721134123538&sdata=7LRswRA4%2BNo9nOg5jvZyvwvmHkIPfrPcduJ4OIg61x4%3D&reserved=0.

FYI:  I'm in process of verifying.  Looks like the original KB listed was removed (It was there previously).  I appears that it may have been replace with a Roll-Up KB.  But in process of confirming specific details of what was actually put into the build so that we can have accurate details on the site.  Expect to be able to have it resolved by EOD.  Else I'll remove that link from the Patch list and will update (if needed) once I get final confirmation from Build & Release teams.
-Erik Swart
Program Manager | Azure Compute | v-erswar<EMAIL_ADDRESS>[Microsoft Logo]
From: Rashmi Iyer<EMAIL_ADDRESS>Sent: Friday, August 2, 2019 12:50 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Erik Swart (TEKsystems Inc<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
@Erik Swart (TEKsystems<EMAIL_ADDRESS>to have the final say
-Rashmi Iyer
From: Micah <notifications<EMAIL_ADDRESS>Sent: Friday, August 2, 2019 12:48 PM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Rashmi Iyer <raiye<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
@raiyehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fraiye&data=02|01|v-erswar%40microsoft.com|893beabe04fe479926bd08d7178290c9|72f988bf86f141af91ab2d7cd011db47|1|0|637003721846360464&sdata=oPW4F2Lew1c9WATP6SFpSEhpN5S6iQ29ZNTUxilCG3M%3D&reserved=0 looks like there is nothing related to that KB anymore. I submitted a PR to remove it from the list. I will wait on sign off to ensure that is what you want to do. Let me know and I can merge it.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F36386%3Femail_source%3Dnotifications%26email_token%3DAE64IMPQQEAUIUFZRHRC46LQCSFQVA5CNFSM4II3XLVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OVYII%23issuecomment-517823521&data=02|01|v-erswar%40microsoft.com|893beabe04fe479926bd08d7178290c9|72f988bf86f141af91ab2d7cd011db47|1|0|637003721846370461&sdata=j%2BLCNTV6UtNFDisEQFVJBzjMyc93ngJgwz1DJKITaPA%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE64IMJAN52VAR762DYW4FTQCSFQVANCNFSM4II3XLVA&data=02|01|v-erswar%40microsoft.com|893beabe04fe479926bd08d7178290c9|72f988bf86f141af91ab2d7cd011db47|1|0|637003721846370461&sdata=M3bCLy%2FTTMG6VdjedvabGxQwszylycIA7Nib0quLOzw%3D&reserved=0.

Thanks. Sounds good. If you opt to remove, the PR I submitted is ready to merge. Else, I will close it and let you update as needed.

OK.  Got the finalized answer and I have committed the update PR to the GuestOS patch list, so should be posted live here in a little bit after all the publishing processes finish.
Summary:
The reference to KB4506621 was indeed correct and I did get multiple confirmations that the associated patches were actually applied in the July Release and the references were accurate.  However, reference to that KB# turns out is a rollup reference number for CVE-2019-1006https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1006 that isn't officially published.  I cross-checked with the release notes and the individual KB#'s within that CVE-2019-1006 list for the server versions in GuestOS and confirmed that the associated KB# for each are already included within the release notes and GuestOS Patch list on other lines.  As such, the reference line for KB4506621 is redundant, and has been removed.
Thanks!
-Erik Swart
Program Manager | Azure Compute | v-erswar<EMAIL_ADDRESS>[Microsoft Logo]
From: Erik Swart (TEKsystems Inc)
Sent: Friday, August 2, 2019 1:20 PM
To: Rashmi Iyer<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
FYI:  I'm in process of verifying.  Looks like the original KB listed was removed (It was there previously).  I appears that it may have been replace with a Roll-Up KB.  But in process of confirming specific details of what was actually put into the build so that we can have accurate details on the site.  Expect to be able to have it resolved by EOD.  Else I'll remove that link from the Patch list and will update (if needed) once I get final confirmation from Build & Release teams.
-Erik Swart
Program Manager | Azure Compute | v-erswar<EMAIL_ADDRESS>[Microsoft Logo]
From: Rashmi Iyer <raiye<EMAIL_ADDRESS>Sent: Friday, August 2, 2019 12:50 PM
To: MicrosoftDocs/azure-docs <reply<EMAIL_ADDRESS>MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Erik Swart (TEKsystems Inc) <v-erswar<EMAIL_ADDRESS>Cc: Mention <mention<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
@Erik Swart (TEKsystems<EMAIL_ADDRESS>to have the final say
-Rashmi Iyer
From: Micah <notifications<EMAIL_ADDRESS>Sent: Friday, August 2, 2019 12:48 PM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Rashmi Iyer <raiye<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] July 2019 guest OS patches list appears to have a broken link (#36386)
@raiyehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fraiye&data=02|01|v-erswar%40microsoft.com|893beabe04fe479926bd08d7178290c9|72f988bf86f141af91ab2d7cd011db47|1|0|637003721846360464&sdata=oPW4F2Lew1c9WATP6SFpSEhpN5S6iQ29ZNTUxilCG3M%3D&reserved=0 looks like there is nothing related to that KB anymore. I submitted a PR to remove it from the list. I will wait on sign off to ensure that is what you want to do. Let me know and I can merge it.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F36386%3Femail_source%3Dnotifications%26email_token%3DAE64IMPQQEAUIUFZRHRC46LQCSFQVA5CNFSM4II3XLVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OVYII%23issuecomment-517823521&data=02|01|v-erswar%40microsoft.com|893beabe04fe479926bd08d7178290c9|72f988bf86f141af91ab2d7cd011db47|1|0|637003721846370461&sdata=j%2BLCNTV6UtNFDisEQFVJBzjMyc93ngJgwz1DJKITaPA%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE64IMJAN52VAR762DYW4FTQCSFQVANCNFSM4II3XLVA&data=02|01|v-erswar%40microsoft.com|893beabe04fe479926bd08d7178290c9|72f988bf86f141af91ab2d7cd011db47|1|0|637003721846370461&sdata=M3bCLy%2FTTMG6VdjedvabGxQwszylycIA7Nib0quLOzw%3D&reserved=0.


appdome-build-2secure-android 3.2.0

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[ ] I will not move an already shared step version's tag to another commit
[ ] I read the Step Development Guideline
[ ] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[ ] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[ ] I read and accept the Abandoned Step policy

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Eli seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Added Review Aggregator Extension

Description
Added Review Aggregator Extension
Fixes:  #(issue no.)
Fixes #2525 issue

Type of change

d)

[x] This change requires a documentation update

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@Sulagna-Dutta-Roy, view this PR

Updated this PR @Sulagna-Dutta-Roy, once view this


Add is_disabled field on the table apps

Create a field is_disabled on the table apps with FALSE as default. When an app has TRUE assume all tokens with the app client_id are invalid so:

Broadcast should not be working for that app
Login (endpoint api/me) should not be working aswell

Fixed in #247


IP per service

Is it possible to define which IP should use an specific service?
use case: I want to use an specific public IP in my app to connect to azure postgres DB service

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

ID: 10de2de7-9d5a-b791-1e28-a399634993d6
Version Independent ID: a92015a1-4f3a-8b1b-1794-5566af729d16
Content: Whitelist Egress Traffic from Azure Kubernetes Service (AKS) cluster
Content Source: articles/aks/egress.md
Service: container-service
GitHub Login: @neilpeterson
Microsoft Alias: nepeters

https://docs.microsoft.com/en-us/azure/aks/static-ip
Also, totally not feedback :P

Thanks for the question! We are investigating and will update you shortly.

Thanks for your help!
so the only way is to expose individual services, and maybe use a NSG to
block IN traffic.
Is feedback in the sense current doc doesn't mention it :)
On Tue, 26 Jun 2018 at 21:59, Micah<EMAIL_ADDRESS>wrote:

Thanks for the question! We are investigating and will update you shortly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/10816#issuecomment-400442389,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGGV6nz01t4VT_FN8Ptw65gBHHz5aQeks5uApKEgaJpZM4U4Zxq
.

@jalberto thanks!
@neilpeterson can you take a look and see if we should add more information to this doc?

@jalberto currently, the first public IP address created is used for egress traffic. From the doc.
Once a Kubernetes service of type LoadBalancer is created, agent nodes are added to an Azure Load Balancer pool. For outbound flow, Azure translates it to the first public IP address configured on the load balancer.

There may be some way to hack together a deterministic solution, such as you have describe, however I am unsure of the superscribe steps / reliability etc..
My best advice would be to raise a product issue, which can be done here.

@jalberto - I am going to close this doc issue. If there is anything else, please let us know.
#please-close


Training problems

Which training document should I perform from scratch?

We will release the training code and related guidance in the future. Or you can intern in our group to access the training code earlier.

Which training document should I perform from scratch?

We will release the training code and related guidance in the future. Or you can intern in our group to access the training code earlier.


GN-4625: Move to Playwright E2E

Overview
Migrate to using Playwright instead of Cypress.
connected issues and PRs:
???
Setup

Checkout
npm install

How to test/reproduce
Available commands

e2e:open - opens Playwright UI locally
e2e:open:docker - opens Playwright UI in Docker and attempts to connect to your XServer
e2e:run - runs Playwright tests locally, skipping tests tagged with @vrt
e2e:run:docker - runs all Playwright tests in Docker
e2e:run:vrt - runs visual regression tests in Docker
e2e:run:vrt:update - updates visual regression tests after running them in Docker
e2e:show-report - shows the report of the last run

Visual regression tests (VRT)
To run visual regression tests locally you need to run npm run e2e:run:vrt.
Afterwards if you need to update the snapshots you can run npm run e2e:run:vrt:update.

[!IMPORTANT]
Playwright is run in Docker to ensure consistent snapshot comparison results, as it guarantees the same environment for each run.

Challenges/uncertainties
Not sure about behaviour on other host systems, e.g. Linux or Windows.
@abeforgit I am interested to see if you are able to run Dockerized version on your machine with XServer, if you have time to check 🤔
Checks PR readiness

[x] UI: works on smaller screen sizes
[x] UI: feedback for any loading/error states
[x] Check cancel/go-back flows
[x] Check database state correct when deleting/updating (especially regarding relationships)
[x] changelog
[x] npm lint
[x] no new deprecations

I justed tried the x11 forwarding setup. I doesn't seem to work on wayland (as expected, maybe it could be possible with xwayland), but it also does not seem to work on x11.
I'm now looking into running playwright locally, which also has some caveats it seems.

Update: got it to work on fedora wayland natively (not yet using the x11 forwarding). Was confused on ubuntu being the only 'officially' supported distro, but it also works fine on other distros.

@elpoelma good to merge?

Good to merge for me. I can run it locally as expected, and the docker set-up works (albeit without x11 forwarding, but not super crucial IMO).
One final question: doesn't the fact that playwright uses its own custom browser binaries make the vrt tests also run on the 'same' environment every time. That should be reliable enough no?

One final question: doesn't the fact that playwright uses its own custom browser binaries make the vrt tests also run on the 'same' environment every time. That should be reliable enough no?

The rendering is still going to be different between different OS

true, true.


Laravel 6 ( Swift_TransportException (530) Expected response code 250 but got code "530", with message "530 5.7.1 Authentication required ")

How to solve this issue? mailtrap  mailgun

My guess is that there is a problem with your mailtrap / mailgun account credentials; it could be that they are not working or possibly they have been miss-configured.  I would recommend trying to verify those credentials first and then make sure that the credentials are available to the framework via a .ENV file.  (Remember that Laravel may be caching config values - that might be part of the problem.)

I am going to close this for now.

same error received
.env file is correct but not resolved yet


Remove unknown if use_best in label transfer

When scs.tl.label_transfer is issued with use_best=True, unknown label is present in transferred annotations, although it won't be used. It could be better to remove it.

Addressed in 138fd3bd5438ff977ba208ba5ff75de84395d9ff


fix the judgement of clusterChanged

the judgement of clusterChanged is wrong

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

I signed it

I signed it

Thanks for this! I'd really appreciate a unit test for this - noticing how the logic is changing but tests don't need to be updated for this indicates lack of coverage. Would you be able to add a test for this logic please?
/assign @jimmidyson


Explorer not showing any workloads

Extension Name: vscode-kubernetes-tools
Extension Version: 0.1.3
OS Version: Windows_NT x64 10.0.16299
VSCode version: 1.19.3

We have written the needed data into your clipboard. Please paste:
{
	"activationTimes": {
		"startup": false,
		"codeLoadingTime": 798,
		"activateCallTime": 36,
		"activateResolvedTime": 0,
		"activationEvent": "onView:extension.vsKubernetesExplorer"
	}
}

The node is shown and the connection seems to work, but no workloads or pods are listed.
Kubernetes Version is:
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:34:11Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.0+coreos.0", GitCommit:"8031716957d697332f9234ddf85febb07ac6c3e3", GitTreeState:"clean", BuildDate:"2017-03-29T04:33:09Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

Thanks for reporting this Kevin.  Just to check the obvious, if you run kubectl at the command line then there are workloads or pods?  (Asking in particular because I've sometimes seen errors when the client and server versions are out by more than 1.)  Are there any namespaces in play that could affect what's displayed?  @testforstephen any other ideas?

Not sure what's the reason. @kwiesmueller  Any error logs at the Console of Help -> Toggle Developer Tools?

Yeah, kubectl works fine and there are no errors in the console.

@kwiesmueller Could you post the output you see from, say, kubectl get pods?  I'm just wondering if there's something in the way the output is formatted that's throwing the extension into confusion.
Also, could you try viewing Services and Nodes in the tree, and let us know if those are also unexpectedly empty?

kubectl get pods -n bot
NAME                                         READY     STATUS    RESTARTS   AGE
bot-agent-auth-239868889-2vdrh               2/2       Running   0          1d
bot-agent-bamboo-2261777643-pl49j            2/2       Running   0          1d
bot-agent-hello-golang-325248333-2kxxk       2/2       Running   0          1d
bot-agent-hello-java-4087186702-pq2vh        2/2       Running   0          1d
bot-agent-hello-python-837773870-dbxlw       2/2       Running   0          1d
bot-agent-highrise-1686754091-jqj85          2/2       Running   0          1d
bot-agent-lunch-2573429343-445rs             2/2       Running   0          1d
bot-agent-lunch-java-960343055-prjbh         2/2       Running   0          1d
bot-agent-mail-verify-1652137681-2r4zn       3/3       Running   0          1d
bot-agent-merge-bot-3792659608-kkr8s         2/2       Running   0          1d
bot-agent-news-1202067307-9j9xh              2/2       Running   0          1d
bot-agent-storage-1960611899-dp9jq           2/2       Running   0          8h
bot-agent-weather-1413410728-sxz2c           2/2       Running   0          1d
bot-connector-hipchat-3781426684-zf9qt       1/1       Running   0          1d
bot-connector-hipchat-db-4162098681-xzjbp    3/3       Running   2          1d
bot-connector-telegram-hq-66275053-hgjh9     1/1       Running   0          1d
bot-connector-telegram-sm-1202564322-8lsts   1/1       Running   0          1d
bot-master-847527999-rhr7z                   2/2       Running   0          1d

I have the problem on all my clusters. GCE, SingleNode Selfhosted, no matter what.
Also in all cases and on all devices I get the nodes correctly and for the services only the kubernetes service.

Also, if the extension might get confused, shouldn't there be some kind of logging?
I am not really into the extensions stuff yet, but would expect some ways to debug this.

@kwiesmueller I would encourage you to debug this issue by using the source code. And PR is welcome.
Here is a simple wiki about setup the extension development environment. https://github.com/Azure/vscode-kubernetes-tools/wiki/Setup-development-environment
After that, you could add some breakpoints at the explorer source code https://github.com/Azure/vscode-kubernetes-tools/blob/master/src/explorer.ts

@kwiesmueller We're not aware of any way the extension could get confused by kubectl output, which is why we don't log it; I asked because I wondered if perhaps there was a way it could get confused that we hadn't anticipated!
It looks like the issue is namespaces.  I notice that when you do kubectl get pods you're passing -n bot.  The current version of the extension doesn't support non-default namespaces.  This is fixed in https://github.com/Azure/vscode-kubernetes-tools/pull/36, which is merged but not yet shipped to the Marketplace.  I'll try to get a release out tomorrow; if not, it will be a couple of days more.  I think you can work around it by doing a kubectl config set-context <your-current-context-name> --namespace=bot.
Thanks for reporting this and for your patience in providing the diagnostic information.  Please do let us know if you still see problems once we ship the update and you switch to the bot namespace!

@kwiesmueller 0.1.4 is now in the VS Code Marketplace.  Could you try installing it and try the following:

Go to the tree view and expand your cluster
Expand the Namespaces node
Right-click the bot namespace node and select Set as Current Namespace

The tree view should refresh, and when you expand the workloads you should see things in the bot namespace.  Note this will have the side-effect of setting bot as the default namespace for kubectl in this context, even on the command line.
Please let us know if you still see problems!  And we would value your feedback on this feature -- whether it works for your scenario and ways that might work better for you.

That worked great. Thanks a lot.
I am already looking my way into vscode extensions and might provide some
contributions soon. Probably see you soon ;-)
On Wed, Feb 7, 2018 at 12:42 AM itowlson<EMAIL_ADDRESS>wrote:

@kwiesmueller https://github.com/kwiesmueller 0.1.4 is now in the VS
Code Marketplace. Could you try installing it and try the following:

Go to the tree view and expand your cluster
Expand the Namespaces node
Right-click the bot namespace node and select Set as Current
Namespace

The tree view should refresh, and when you expand the workloads you should
see things in the bot namespace. Note this will have the side-effect of
setting bot as the default namespace for kubectl in this context, even on
the command line.
Please let us know if you still see problems! And we would value your
feedback on this feature -- whether it works for your scenario and ways
that might work better for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/vscode-kubernetes-tools/issues/44#issuecomment-363604652,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATxF_Re8oTcn-cfG6AetYtBrXhij439Aks5tSONsgaJpZM4R00xD
.

--
Kevin Wiesmüller
Team Infinity
Tel.: +49-611-20570-138
Mobile: +49-172-297-2662
_
//SEIBERT/MEDIA GmbH / LuisenForum
Kirchgasse 6 / 65185 Wiesbaden
GF: J.Seibert und M.Seibert / AG Wiesbaden: HRB11502

Great!  I'll close the issue then - do reopen if necessary.


Update readme #6

Update readme #6

Hi @ValchanOficial I'm happy to accept PRs improving the Readme, but yours is not adding value. It's removing the formatting. I didn't understand what is your idea

Hi @ValchanOficial I'm happy to accept PRs improving the Readme, but yours is not adding value. It's removing the formatting. I didn't understand what is your idea

I changed the formatting and added the contributors

I see but the formatting was right, and I like the raw go-skeleton as the name. With your changes the formatting would be broken.

Closing due age, besides seems the branch/fork was deleted


[Feature request] Option to change 'openApp' transition

Currently the app opened with openApp method slides in. It will be great to provide functionality to customize this transition somehow - for example, make opened app scale up.

Also trying to figure out how to do that..
Normally overridePendingTransition is used on Android, but I dont know yet how it applies to flutter.

@cgestes
I've also tried to implement this solution, but it didn't work either...

I did use overridePendingTransition with success.
Opening: I call it just after startActivity
Coming back from the launched app: I call it in onResume
Took me a long time to figure it out!

@cgestes
And what animation did you passed there? And where it was stored?

I did:
overridePendingTransition(android.R.anim.fade_in, android.R.anim.fade_out);

@cgestes
Sounds great!
But in my case console complains that it can't resolve method overridePendingTransition. Maybe I miss some imports?

It seems to be a method of the Activity android java class.

@cgestes
Well, I already had this imported in the file..

@cgestes Well, seems I already had this imported in the file..
Maybe you forgot to mention some extra steps that you did to make it work?

Little bit late with a reply to this, but I did the following and the animations changed as per the overridePendingTransitions value.
Import the following
import android.app.Activity;
import android.app.ActivityOptions;

Amend the openApp to the following
private boolean openApp(@NonNull String packageName) {
        if (!isAppInstalled(packageName)) {
            Log.w(LOG_TAG, "Application with package name \"" + packageName + "\" is not installed on this device");
            return false;
        }

        Intent launchIntent = context.getPackageManager().getLaunchIntentForPackage(packageName);

        if (IntentUtils.isIntentOpenable(launchIntent, context)) {

            ActivityOptions options =
                    ActivityOptions.makeCustomAnimation(context, android.R.anim.fade_in, android.R.anim.fade_out);

            context.startActivity(launchIntent, options.toBundle());

            return true;
        }

        return false;
    }

When testing the animation now fades in on launching another application.
I've found a bit of a hack to be able to get the clipRevealAnimation to work, by passing the data of the scale, height and width down to the function, it works with the animation, but the offset on the screen doesn't always match up to where the onPress is being generated (in my case below I always want it to render from the middle of the screen, but the Y axis offset sometimes is a bit off when passing down the renderBox offset.
 private boolean openApp(@NonNull String packageName, int startX, int startY, int height, int width) {
        if (!isAppInstalled(packageName)) {
            Log.w(LOG_TAG, "Application with package name \"" + packageName + "\" is not installed on this device");
            return false;
        }

        Intent launchIntent = context.getPackageManager().getLaunchIntentForPackage(packageName);

        if (IntentUtils.isIntentOpenable(launchIntent, context)) {

            View view = new View(context);
            view.setLayoutParams(new LayoutParams(height, width));

            int startingX = width / 2;
            int startingY = startY;

            ActivityOptions options = ActivityOptions.makeClipRevealAnimation(view, startingX, startingY, 0, 0);

            context.startActivity(launchIntent, options.toBundle());

            return true;
        }

        return false;
    }

Will see if I can improve this to get it to work as intended, and also as mentioned before getting the reverse animation to work when calling onResume


Loss function

I could not understand how do you compute the loss function? Especially the computation of prior_ll part.
It would be great if you could explain what you are doing there

This line computes the log-likelihood of the output z assuming a unit-norm Gaussian prior (PDF can be found here:
prior_ll = -0.5 * (z ** 2 + np.log(2 * np.pi))


Adds dist and fixes typo

Hi, this is a fix to help publish the npm package with a compiled dist.
Certain apps do not like running babel on node modules, so we cannot create a build as it fails on the minification and get errors such as:
Failed to compile.

Failed to minify the code from this file:

 	./node_modules/styled-grid-component/src/grid.js:4

I also found a small typo. Thanks for the library otherwise, its working great 😃
Cheers.

Hi, thanks for the help !!


Fix backup depots

Change MiqSchedule to leverage file_depot relationship rather than "resource_id" and "resource_type" on the FileDepot, allowing the UI to build an associated file_depot when building or editing a MiqSchedule.
https://bugzilla.redhat.com/show_bug.cgi?id=1205898

@miq-bot remove_label WIP

@miq-bot add_label bug

@Fryguy @dclarizio Please review.

Tested creating a new schedule for both NFS and SMB (the two allowed types)

Editing an existing schedule doesn't work, screen doesn't fully render, url shows "http://<IP_ADDRESS>:3000/ops/explorer/new?escape=false&load_edit_err=true" (unrelated, not fixing that here)

Tested submitting a database backup for both NFS and SMB (the two allowed types)

Both verify buttons return an error saying something like "Edit aborted! CFME does not support the browsers back button" (unrelated, not fixing that here)

cc @AparnaKarve @gmcculloug

@brandondunne The BZ specified here is identical to this BZ -
https://bugzilla.redhat.com/show_bug.cgi?id=1210089.
In my opinion, the bug was on the controller side and has been fixed in this PR - https://github.com/ManageIQ/manageiq/pull/2643.
Therefore I'm not sure if we need this particular PR anymore since the DB backup issue has already been addressed.

@AparnaKarve I agree that the problem was on the controller side and PR #2643 appears to solve the problem.  But I still want to migrate to using a direct relationship to the FileDepot.

@brandondunne Testing this PR for adding/editing database schedules did not go so well.
I see that depot_hash is deprecated...can you make the necessary adjustments in schedules.rb and diagnostics.rb where depot_hash is being called ?
Thanks.

@Fryguy @dclarizio Please review.

@AparnaKarve I updated the remaining callers of depot_hash

@AparnaKarve Updated based on your comments.  Thanks for the review! :icecream:

@brandondunne Retested the changes in the UI, File Depot records are now getting created correctly :+1:

@Fryguy Any concerns?


Better handling of git merge conflict markers

When a user tries to deploy metadata that has git merge conflict markets in it, we simply return an error like:

Because this is a known format of strings and we are encoraging users to use source tracking, we could do a much better job of handling this special case.

We should do something similar and show a better error. "You are trying to deploy metadata to your org that has unresolved git conflicts. Please resolve the conflicts before you deploy."

Yes, an error message like that would be really helpful. Thanks.


ValueError: invalid literal for int() with base 10 when trying to get trace.csv

Hi, when I am trying to get CSV with trace, I get next error:
from RsInstrument import *

instr = RsInstrument('TCPIP::<IP_ADDRESS>::5555::SOCKET', True, False, "SelectVisa='socket'")
print(instr.query('MMEM:FILE? "PR100/Trace_000.csv"'))

ValueError: invalid literal for int() with base 10: '.4\r\n86705000,4.6\r\n86710000,6.1\r\n86715000,5.8\r\n86720000,5.0\r\n86725000,6.3\r\n86730000,6.1\r\n86735000,5.4\r\n86740000,6.1\r\n86745000,6.6\r\n86750000,5.0\r\n86755000,4.8\r\n86760000,4.9\r\n8

All OK, while using telnet

Hi banderlog,
is the instrument PR100? Can you post the csv file here? It seems the content has the termination characters used for the message control. Do you need to explicitly use the SOCKET connection?
BR
Milo

I see the problem... the payload contains the CRLF combinations, but the termination character for transmission is set to LF. The transfer is interrupted by the first LF occurrence, the rest of the payload stays in output buffer and is returned in further command queries. I'm affraid there is no solution to get this working correctly in with the RsInstrument.
I wonder, how do you get this to work in TELNET? You also have to specify the termination character, or wait for a timeout...

I wonder, how do you get this to work in TELNET?

Just run the command MMEM:FILE? "PR100/Trace_000.csv"


download speed of url youtube-dl returns is very slow

[x] I've verified and I assure that I'm running youtube-dl 2018.03.14

[x] At least skimmed through the README, most notably the FAQ and BUGS sections

[x] Searched the bugtracker for similar issues including closed ones

[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'--extract-audio', u'-g', u'https://www.youtube.com/watch?v=dQw4w9WgXcQ']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.03.14
[debug] Python version 2.7.14 (CPython) - Darwin-17.4.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.4.2, ffprobe 3.4.2
[debug] Proxy map: {}
https://r6---sn-3pm7sn7d.googlevideo.com/videoplayback?expire=1521469765&gcr=jp&ei=5XSvWrLAKou3gQOh04qoAw&requiressl=yes&itag=251&keepalive=yes&initcwndbps=1402500&source=youtube&clen=3438483&dur=212.061&ipbits=0&sparams=clen%2Cdur%2Cei%2Cgcr%2Cgir%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Ckeepalive%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Crequiressl%2Csource%2Cexpire&lmt=1518413814901302&mv=m&mt=1521448063&mm=31%2C26&fvip=4&ms=au%2Conr&pl=19&id=o-ANc6M-7es1U_ybk77INpHx-UBPu29oeLBUdfu508psBU&mime=audio%2Fwebm&gir=yes&c=WEB&mn=sn-3pm7sn7d%2Csn-oguelnle&ip=<IP_ADDRESS>&key=yt6&signature=3C110F464F336275AAB37309E69EB97DE5962E94.916C77A7815EE4CBF4AA43011AB023A58ADA7453&ratebypass=yes

I want to create API server that responses youtube audio URL to let client download youtube audio file directly.
So I get youtube audio file URL using the following command.
youtube-dl --extract-audio -g "https://www.youtube.com/watch?v=dQw4w9WgXcQ"

And I got following audio url.
https://r6---sn-3pm7sn7d.googlevideo.com/videoplayback?gcr=jp&requiressl=yes&fvip=4&ei=smqvWqbHL8fkqQGgrKOQBg&lmt=1518413814901302&mime=audio%2Fwebm&mv=m&c=WEB&expire=1521467154&source=youtube&keepalive=yes&pl=19&itag=251&dur=212.061&initcwndbps=1396250&clen=3438483&ipbits=0&mn=sn-3pm7sn7d%2Csn-3pm76n76&mm=31%2C29&id=o-APcnop1e4uRZDEsrYtj_pmV3lsMsCTO4a0lmk4srZ4gm&gir=yes&mt=1521445365&ms=au%2Crdu&key=yt6&ip=<IP_ADDRESS>&sparams=clen%2Cdur%2Cei%2Cgcr%2Cgir%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Ckeepalive%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Crequiressl%2Csource%2Cexpire&signature=E2078C6E348D3263DCDBF824190BC1BF2A938533.51541F2E85AFC8F3A6C0A142B37774DE16071692&ratebypass=yes

And I opened this url in chrome and download it, but it takes about fifty seconds, about 60 kb/s speed.
Using wget command, results are same.
videoplayback?gcr=j 100%[===================>]   3.28M  64.7KB/s    in 52s

But for some reason, Without -g option, Download can be done immediately.
It takes about 1-2 seconds.
youtube-dl --extract-audio "https://www.youtube.com/watch?v=dQw4w9WgXcQ"

Why is there a difference in speed like this?
Both download url are same?

Expected.
youtube-dl uses downloading based on separate chunks to work around the rate limitation imposed by YouTube.


[Decompiler] Always picks float type for qmfc2

Most of the time, qmfc2 is used to get the x component of a vector as a float.  But sometimes it's used to get the entire 128-bit vector value for use with MMI (pxxx) instructions.  Right now the decompiler will always pick type float.
This causes two issues:

Compile error because the compiler won't let you use pw.sll or similar on a float.
Silent loss of data because the compiler treats the value as 32/64 bits, but it is actually 128 bits

The second issue is probably very rare, but worth worrying about.  For now, we should be careful in any code that uses qmfc2.  Already we should be careful with all 128-bit variable stuff because they work slightly differently in GOAL vs. OpenGOAL.

Some examples of this

vector-rad<-vector-deg!
vector-rad<-vector-deg/2!
vector-degf
vector-degmod
vector-deg-diff
vector-degi

ocean-transition - function unknown atm

This was fixed for 128-bit values, but is still an issue for 64.


"System.ArgumentNullException: Value cannot be null" in WorkerInstanceManager.RegisterEvent

Originally posted by @Tewr in https://github.com/Tewr/BlazorWorker/issues/28#issuecomment-757541286:

@andersson09 I dont think this is related, more likely is that the worker process does not have the type TEvent (as in EventHandler<TEvent>)  loaded in memory. Please open a new issue if you want to discuss this further. I think an error message might be missing here in any case.

I'm running into the same problem when I use a custom event argument type (an enum I've defined). I suspect the cause is here:
https://github.com/Tewr/BlazorWorker/blob/c971af1af3259a564e783c8a305b6aa06e8e1a53/src/BlazorWorker.ServiceFactory/WorkerBackgroundServiceProxy.cs#L223
Type.GetType requires an assembly-qualified name when the type is defined anywhere except mscorlib or the current assembly (i.e., BlazorWorker.WorkerBackgroundService.dll), but EventHandlerTypeArg doesn't include the assembly name.

I was able to reproduce, fixed in master, available in upcoming release.

I was able to reproduce, fixed in master, available in upcoming release.


Update screenshots in UG

The screenshots look almost identical to the ones in the DG, just that the UI is updated.

Codecov Report

Merging #226 (ca9fe9e) into master (1abc2e7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #226   +/-   ##
=========================================
  Coverage     76.61%   76.61%
  Complexity      806      806
=========================================
  Files           115      115
  Lines          2266     2266
  Branches        262      262
=========================================
  Hits           1736     1736
  Misses          455      455
  Partials         75       75

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 1abc2e7...ca9fe9e. Read the comment docs.


Find the vimrc path in case of calling nvim with -u

This solves #99 and probably #74

Looks solid :+1:
Not sure about #74, that looked more like something went wrong with packer or neovim.


Amplify.Auth.getCurrentAuthUser() called from init() causes Preview to crash in XCode

Describe the bug
Hello,
Amplify.Auth.getCurrentAuthUser() called from init() causes Preview to crash in XCode.
Github repo indicating this error: https://github.com/Eumag/app4.
AWS video link (2year old now) indicates the use of this api from init(). At 24:20, sessionManager.getCurrentAuthUser() is added AuthenticatedApp.init(). This statement is needed to ensure app lands into proper state on first run.
The code builds and gets executed fine on real device but causes Preview to crash. This crash indicates a problem in launching process. With this statement commented out there is no crash observed. This api works fine from other places (as shown/used in video). Can you check upon it.
Thanks
Steps To Reproduce
Steps to reproduce the behavior:
1. Call Amplify.Auth.getCurrentAuthUser() from init() in file app4App.swift under function app4App.init(). This line is presently commented out in codebase.
2. Click on any View (say loginBySMSView)
2. Click on Resume for Previews on right side panel of any view

Expected behavior
No crash should happen during Preview of View screen when Amplify.Auth.getCurrentAuthUser()  is called from init().
Amplify Framework Version
1.28.0
Amplify Categories
Auth
Dependency manager
Cocoapods
Swift version
5.0
CLI version
9.2.1
Xcode version
13.4 (13F17a)
Relevant log output
<details>
<summary>Log Messages</summary>

MessageSendFailure: Message send failure for relaunch
|  RemoteHumanReadableError: The operation couldn’t be completed. Transaction failed. Process failed to launch. (process launch failed)

```
Is this a regression?
Yes
Regression additional context
Reason I say this is regression, is because this did not show any problem in the video. If there is an option of "Don't Know", I would prefer that because I have not been using this Amplify.Auth.getCurrentAuthUser() for a long time.
6. Device (Model and whether it is Simulator or real device) with IOS version: IPhone-11 , iOS 15.6.1, ModelNo: MHDD3HN/A, RealDevice
Device
iPhone11 - Real Device (ModelNo: MHDD3HN/A)
iOS Version
iOS 15.6.1
Specific to simulators
No response
Additional context
No response

Duplicate of https://github.com/aws-amplify/amplify-ios/issues/2308 and https://github.com/aws-amplify/amplify-ios/issues/1874. Linking for reference.

Awesome atierian! Did a quick check and Amplify 1.28.2-unstable.2 did seem to solve the issue at hand. Though, to avoid dependency problem between Amplify and AWSCognitoAuthPlugin, I had to change versions for AmplifyPlugins/AWSCognitoAuthPlugin and AmplifyPlugins/AWSAPIPlugin as well. I am sure dependency issues will taken care of at release time.

We released this as 1.28.2, closing this issue. Feel free to reach us if you have more questions.


Restructure vs2008_express_vc_python_patch to include source.

Include the x64 directory of reg files from staged-recipes history.
Include setup_x64.bat script from staged-recipes history.
Remove post-link.bat and incorporate relevant pieces.
Update meta.yaml to handle current installation structure.
Drop bld.bat as the script is included in meta.yaml to be compact.
Revert changes made to appveyor.yml as they are not needed.

xref: https://github.com/conda-forge/staged-recipes/pull/251

Thanks!


How to add JPLSnapshot to http://localhost:7876/test?requestTag=ADDONS

Hi, how can add the API JPLSnapshot in the _**http://localhost:7876/test?requestTag=ADDONS**_ url ?
By default, the JPLSnapshot don't appear
Can you help me ? Thanks :+1:

Found solution myself. I'am close :)


Release Google.Cloud.Firestore.Admin.V1 version 3.11.0

Changes in this release:
New features

Add Database.SourceInfo and Database.source_info (information about database provenance, specifically for restored databases) (commit 330fe6a)
Add Database.CmekConfig and Database.cmek_config (information about CMEK enablement) (commit 330fe6a)
Allow specifying an encryption_config when restoring a database (commit 330fe6a)
Add Database.delete_time (the time a database was deleted, if it ever was) (commit 330fe6a)
Add Database.previous_id (if a database was deleted, what ID it was using beforehand) (commit 330fe6a)

Documentation improvements

Fix assorted capitalization issues with the word "ID" (commit 330fe6a)
Clarify restore details (commit 330fe6a)
Clarify maximum retention of backups (max 14 weeks) (commit 48c7024)
Remove note about backups running at a specific time (commit 48c7024)
Standardize on the capitalization of "ID" (commit 48c7024)

Created release for Google.Cloud.Firestore.Admin.V1-3.11.0


KAFKA-12283: disable flaky testMultipleWorkersRejoining to stabilize build

Will address the root cause in this PR: https://github.com/apache/kafka/pull/10367, and added this test back in that PR, too.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ableegoldman , I agree to ignore this test first, and added back after the root cause fixed, to stabilize build.

Per our discussion in KAFKA-12283 (https://issues.apache.org/jira/browse/KAFKA-12283?focusedCommentId=17313560&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17313560):

We can disable the test in the meantime. It used to fail once in a while but I understand that this occurs more often now.

@ableegoldman , could you help merge this PR? Thanks.


Wrong subsection name(rsyslog)

Describe the Issue
wrong sub-section name
Expected Behavior
- name: "SECTION | 4.2.1 | Configure rsyslog"
  ansible.builtin.import_tasks:
      file: cis_4.2.1.x.yml
  when: rhel9cis_syslog == 'rsyslog'

- name: "SECTION | 4.2.2 | Configure journald"
  ansible.builtin.import_tasks:
      file: cis_4.2.2.x.yml
  when: rhel9cis_syslog == 'journald'

Actual Behavior
- name: "SECTION | 4.2 | Configure Logging"           # wrong name(should be "SECTION | 4.2.1 | Configure rsyslog")
  ansible.builtin.import_tasks:
      file: cis_4.2.1.x.yml
  when: rhel9cis_syslog == 'rsyslog'

- name: "SECTION | 4.2.2 | Configure journald"
  ansible.builtin.import_tasks:
      file: cis_4.2.2.x.yml
  when: rhel9cis_syslog == 'journald'

Control(s) Affected
4.2.1.*
Environment (please complete the following information):

branch being used: [e.g. devel]

Possible Solution
PR.

hi @ipruteanu-sie
This Issue has been merged to devel and into main branch. I will therefore close this issue.
Please feel free to reopen if you feel its not as expected.
Many thanks again for your time
uk-bolly


add dynamic dns support with dhcp for apiserver vip

When dynamic DNS is available, the input ‘address’ can be a fqdn without binding to a IP, then kube-vip will use dhclient to get an IP for the hostname of fqdn, then ipUpdater will kick in.

This looks good to me!
Two things though:

Can we move the destination merge from master to 0.2.1
It could do with some documentation? I've merged the /docs (from kube-vip.io) into the 0.2.1 branch so feel free to make a branch from there and add in a few lines of usage 👍

Ah, you may need to rebase... I can't imagine the merge conflicts are too bad :-)

Rebase done. will add more docs in a separate PR. Curious to know, for the doc, do you use some tools to generate the static website from markdown? I'm also looking for something like this.

https://github.com/mixu/markdown-styles
Then
generate-md --layout github --input . --output /var/www/kube-vip/

Thanks a lot!


Remove unused metavar

Changes proposed in this pull request:

It appears the mockmode metavar is unused in code. Please correct me if I am wrong.
The problem it causes by being there is it overrides the default --helpstring fromconnexion run --helpso that it is difficult to understand what the possible arguments are for--mock. From reading the click` docs & code, it seems that if we leave the metavar out, it will correctly populate the available options.

This metavar is not "unused" per se, but I think the help text is clearer without it.
The difference is shown below:
connexion run --help
with:
  --mock MOCKMODE                 Returns example data for all endpoints or
                                  for which handlers are not found.

without:
  --mock [all|notimplemented]     Returns example data for all endpoints or
                                  for which handlers are not found.

( ^ kicking Travis )

:+1:


Exclude cross-driver sessions from reverse lookup

What does this Pull Request accomplish?
Exclude cross-driver sessions from reverse lookup.
Fixes AB#1807465
Why should this Pull Request be merged?
If cross-driver sessions can be added to the reverse lookup, it can introduce ambiguity about which session should be returned from reverse lookup methods if there are multiple sessions with the same resource handle. If we exclude cross-driver sessions from reverse lookup, only primary sessions can be returned.
Methods that reverse lookup sessions are very rare. In RFSA, for example, there is a GetAttributeViSession method, but no actual public ViSession attributes. We could attempt more complicated features that make it possible to access cross-driver sessions under some conditions. But this provides little value. By restricting reverse lookups completely, we have more options to change/add behavior in the future.
What testing has been done?
Ran and passed all RFmx and RFSA test.


chore: run pyupgrade

use {...} instead of set([...])
do not use class Foo(object):, just use class Foo:
do not specify default flags ("r") for open()

You don't know how much I love your PRs.


fix(test):updated mailer copyright text properly

Fixes #
Fixed the mailer copy right text by adding some elements and removing some texts as stated in the issue
Describe the changes you have made in this PR -
Previously, mailer copyright text was like this "Copyright © 2021 CircuitVerse. All rights reserved. For any issues, reach out to us<EMAIL_ADDRESS>which was replaced by new correct text as stated in the issue "Copyright © %{time_current_year} CircuitVerse, All rights reserved."
Screenshots of the changes (If any) -

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage remained the same at 82.022% when pulling a8c0eb87ea921398dbb7d9301cb2a5bbcb8b6255 on me-aashish:update-mailer-copyright-text#3008 into d732e51bb07498627c7066d92af1aa3199ca5987 on CircuitVerse:master.

Have you verified this changes by sending an email ?

On it sir!
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Aboobacker MK @.>
Sent: Monday, June 27, 2022 1:08:33 PM
To: CircuitVerse/CircuitVerse @.>
Cc: Aashish Kumar Jha @.>; Author @.>
Subject: Re: [CircuitVerse/CircuitVerse] fix(test):updated mailer copyright text properly (PR #3216)
Have you verified this changes by sending an email ?
—
Reply to this email directly, view it on GitHubhttps://github.com/CircuitVerse/CircuitVerse/pull/3216#issuecomment-1166994556, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS274UVKGZIKLRG6Q45LUE3VRFK7TANCNFSM5Z4UU4JA.
You are receiving this because you authored the thread.Message ID: @.***>

@me-aashish any updates?
have you done with the testing it ?


Unresponsive component for mobile

Hey, I notice there's some component goes absurd in mobile, can you guys please check it out too, some brains is better than one you know

#14 For the navbar it should be responsive now


Don't return all of the snapshots in the sync view

This eventually exceeds the amount of memory available to the server and fails. Witnessed on trellisdemo.net after over 100k snapshots were created.

While this should probably happen, the underlying issue is just keeping too many snapshots in the database. These records should just be removed when the files are removed as part of #214.


Rewrite getNextViableDate, and related timex functions tests

getNextViableDate, getNextViableTime, getPreviousViableDate, getPreviousViableTime
The tests for these 4 timex functions are rewrote based on the mocked Date.Now method in #2596.
I changed the mocked Date.Now  to 2020-08-01T00:12:20.000Z and modified the corresponding expected values.
Also, 2 bugs in getPreviousViableDate, getPreviousViableTime is fixed.

Pull Request Test Coverage Report for Build 157591

4 of 7 (57.14%)  changed or added relevant lines in 3 files are covered.
9397 unchanged lines in 475 files lost coverage.
Overall coverage decreased (-57.4%) to 25.488%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/adaptive-expressions/src/builtinFunctions/getNextViableTime.ts
0
1
0.0%

libraries/adaptive-expressions/src/builtinFunctions/getPreviousViableTime.ts
3
5
60.0%

Files with Coverage Reduction
New Missed Lines
%

libraries/adaptive-expressions/src/builtinFunctions/average.ts
1
87.5%

libraries/adaptive-expressions/src/builtinFunctions/bool.ts
1
83.33%

libraries/adaptive-expressions/src/builtinFunctions/ceiling.ts
1
80.0%

libraries/adaptive-expressions/src/builtinFunctions/dataFunc.ts
1
88.89%

libraries/adaptive-expressions/src/builtinFunctions/dayOfMonth.ts
1
87.5%

libraries/adaptive-expressions/src/builtinFunctions/dayOfWeek.ts
1
87.5%

libraries/adaptive-expressions/src/builtinFunctions/dayOfYear.ts
1
88.89%

libraries/adaptive-expressions/src/builtinFunctions/endsWith.ts
1
87.5%

libraries/adaptive-expressions/src/builtinFunctions/exists.ts
1
62.5%

libraries/adaptive-expressions/src/builtinFunctions/floor.ts
1
80.0%

Totals

Change from base Build 157202:
-57.4%

Covered Lines:
5751

Relevant Lines:
17392

💛  - Coveralls


Fix typo in runtime_cache.go

@pmorie I've noticed that most of the RedHat folks aren't getting the CLA bot warning any longer but you still seem to be. Any ideas why you aren't passing the automated checks?

Code LGTM. Will merge on green.

@roberthbailey I believe it's because I hadn't switched my public email on my gh account over to my redhat.com email address.  Let's see what happens now.

@pmorie that would explain it.

@roberthbailey Fixed

Thanks! (now just waiting for a green dot...)

@roberthbailey Presumably the travis build will run at some point.

I think it's actually next in line!

I should have gotten a low number from the scalper


fix search bar

fixes #230
Up until now, ajax_search_bar used .isalpha() as a negative test to determine whether or not the search term might be a Cantus ID. But .isalpha returns False as soon as there is a space in the search term, and that seems to break things. Switching the test to use .isdigit()  as a positive test causes the search box to behave as expected.

I just did some testing and one thing came to mind. Cantus ID may not necessarily be all digits. Some Cantus IDs have letters in them. Incipit must be pure letters, but Cantus ID may not be pure digits.

most recent commit changes logic so that, if there is at least one digit in the search term, it will search for a Cantus ID rather than for an incipit.
It might make sense to search both by cantus ID and by incipit right off the bat, since there are a number of chants with a Cantus ID that begins with "Lamen2:". But OldCantus seems to use the same logic that this commit uses: it shows a bunch of chants whose incipits contain "lamen" before the "2" is added, and only shows chants with "Lamen2:" cantus IDs once the "2" has been added.


Allow the user to supply root cert store

I happen to stumble upon here:
https://github.com/seanmonstar/reqwest/blob/3ad6e02cdb4ba840f1663273ec77c9bb9cc83569/src/async_impl/client.rs#L508-L511
I'm using a custom Rustls provider with RustCrypto which is in pure Rust, and I'm not using ring and do not want ring in the dependency chain.
However, I cannot control this at the moment, so I have to improvise like this:
pub fn make_client() -> Result<Client, Error> {
    let mut builder = Client::builder();
    for cert in webpki_root_certs::TLS_SERVER_ROOT_CERTS {
        builder = builder.add_root_certificate(Certificate::from_der(cert).unwrap())
    }
    builder.build()
}

Which is pretty annoying.

maybe this solution will solve your problem click

Partially solved by #2447 but it is limited to webpki roots. If you want other roots there is no luck atm


tutorial reported broken

https://twitter.com/orrinxu/status/656350773698170880
hello world works fine but when i go to incorporation or seed round it comes up with this problem

reproduced successfully using a fresh copy of the demo master spreadsheet.
execution log:
[15-10-19 23:41:03:569 PDT] include(inc_dr_start) complete```

execution transcript:
```<Story_Main>
<centered>Frog Porridge Pte. Ltd.</centered>
<centered>UEN <span_ucnum>201500000A</span_ucnum></centered>
<centered>(Incorporated in the Republic of Singapore)</centered>
<centered>(the "Company")</centered>
<centered></centered>
<resolution_title>Directors' resolutions in writing
passed pursuant to Article 90 of the Company's Articles of Association</resolution_title>
]) [0 seconds]
[15-10-19 23:41:03:875 PDT] Execution failed: TypeError: Cannot call method "getActiveRound" of undefined. (line 2128, file "Code", project "legaleseMain") [9.359 seconds total runtime]```

the tutorial was loading an old version of the legaleseMain library. i have snapshotted version 12 and updated the tutorial to load that by default.

have sent remedy instructions to original bug reporter
https://twitter.com/mengwong/status/656366942060716032


fix(multiselect): remove + button beside the filter box

Proposed Changes
As the ( + ) icon beside the filter box doesn't seem to add a value for the end-user experience,
this item is remove of the code + the tests relevant to the latter.
Potential Breaking Changes

Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Have you checked with @oliviertaillon  that there are no plans to expand this feature?

@j-mcgregor,
Based on this comment: https://github.com/coveo/react-vapor/pull/1577#issuecomment-639581989,
it would seems that this feature is not needed.


Using dotenv to avoid env variables nightmare

It seems to be complicated to deal with env variables in electron and particularly in this boilerplate.
Maybe we can simplify with dotenv (or dotenv-safe).
NODE_ENV and HOT keys could be set in .env (and .env.example) and not on each command line.
It's possible to use different .env or override a particular key in code (for example set NODE_ENV=test in test helper).
Seems good idea?

There's also env-cmd which uses a similar interface to cross-env.

Setting them in package.json is a more idiomatic solution so I think it should be preferred. Also in my opinion, I think we already have enough dependencies for this project. If anything, we should be trying to get rid of some.

Closing this, as it seems extraneous. Don't think most people will be messing around with .env variables initially. Users can easily add dotenv themselves.


DLMBL 2023 excercise

@ziw-liu I've tested the whole exercise on dlmbl1 node. In addition to prototyping 3 solutions above, can you suggest how to log all validation samples? At this point, the subsample of validation set comes out empty in multiple runs.

With solutions in hand, I'll write the exercise prompt. Earlier exercise prompts are commented out so that you can just run the script by clicking Run Above in the last cell.

can you suggest how to log all validation samples? At this point, the subsample of validation set comes out empty in multiple runs.

I think I know what's happening here. The validation samples are the first sample of the first log_num_samples batches. So if total validation steps is 1 it will only have 1 sample. I can modify the behavior to only use the first batch in the epoch, with the caveat that log_num_samples will then have to be smaller than batch size.

@ziw-liu the conflicts in engine.py seem to be related to how you are logging the loss in two branches. Once you resolve them. Feel free to merge this branch into #37. I can start a smaller PR with updates from the course.
<<<<<<< dlmbl2023
        self.log("loss/validate", loss, batch_size=self.batch_size, sync_dist=True)
        if batch_idx == 0:
            self.validation_step_outputs.extend(
=======
        self.log("loss/validate", loss, sync_dist=True)
        if batch_idx < self.log_num_samples:
            self.validation_step_outputs.append(
>>>>>>> 21d-upscale-decoder
                self._detach_sample((source, target, pred))
            )


How about add "private": true to package.json?

How about add "private": true to package.json?
This will avoid the following warnings on npm install:
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.

and of course avoid publishing, as web projects tend to be private.

Great idea - would you be willing to submit a pull request? Thanks!

Yup


Cypress configuration

Changes Proposed

Check List

[x] The title of my pull request is a short description of the changes
[ ] This PR relates to some issue:
[x] I have documented the changes made (if applicable)
[x] I have covered the changes with unit tests

Codecov Report
Patch coverage has no change and project coverage change: -0.19% :warning:

Comparison is base (9dee9a4) 30.04% compared to head (e4efb33) 29.85%.
Report is 22 commits behind head on helm-dashboard-v2.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                  Coverage Diff                  @@
##           helm-dashboard-v2     #469      +/-   ##
=====================================================
- Coverage              30.04%   29.85%   -0.19%
=====================================================
  Files                     10       10
  Lines                   1348     1323      -25
=====================================================
- Hits                     405      395      -10
+ Misses                   902      887      -15
  Partials                  41       41

see 3 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@Tamir198 Can you restore this PR based on main branch?

@undera Sure, from now on all pr should go into main ?

Yes, we have merged into main, now working from there


Move mouse outside of the pinned box and it disappears

I'd assumed that if I pinned the hover ediitor box it would stay where i put it when I moved the mouse outside of the box.  I am on Windows, using the latest insider build and the pinned box disappears when i move the cursor outside the box,
EDIT:  This happens if when the hover box first appears I drag and move it and then pin it.  If I pin first I can then move the cursor outside and get another hover and then pin and move it.

Hmm, moving the popover auto pins it. So, if you move the popover and then click the pin, you're unpinning it.
Tilted indicated unpinned

And straight up and down indicates pinned

Are you seeing different behavior than that?

Now that you point it out I can see it BUT it isn't at all obvious.  I'm using Blue Topaz theme, but I think if you are new this is very easy to miss.  I see the pin and assume I need to click, since I didn't pin it and.

That's fair. The UX around pinning/dragging/resizing is still a work in progress and certainly has room for improvement. Is there something that you could recommend that would make the pinning behavior more intuitive/obvious?

When I move the hover box, after I get to thr right place on the title bar that left me drag, I am no longer looking at the box but at my target area.  That means I miss the icon change.  Perhaps if not just the icon but it its background "square" also change color that contrasted with the background of the title bar, it would be VERY noticeable and draw a user's eye.

Thanks for the feedback. See what you think about the pin effect in 0.4.3

I'm not sure the animation is actually all that helpful -- the problem may more be that both pin symbols are kind of ambiguous as to whether they're pinned or not.  You can imagine both the straight and angled pins as being either partly inserted or awaiting insertion.  They need something like a solid fill when pinned and a shorter or missing "metal" part, and this would be a more obvious contrast than just changing the angle.  I still have to think every time I look and manually remind myself that the vertical pin means it's pinned.
Another alternative would be to use a padlock and speak of locking or unlocking the pane, which has the additional advantage of not being confused with pinning a file to a pane.  (What's more, the idea of a pin for a hover popup gives the impression it will pin the pane to a fixed spot vs. keeping it open.)  An outline or filled bookmark icon might also work, in that it implies "keep my place" or "keep this open".
(I do like the ability to resize from all sides now, though it feels like the resize targets are still only a pixel or two wide?  Very hard still to grab hold of casually, vs. needing to carefully and precisely target the mouse.  But still a big improvement and much less awkward than only being able to use the corners.)

For me, lock indicates that it can't be moved as well or maybe can't be resized... or can't be edited... but I get your point.
Maybe we should consider if we even need the pin icon. Its current intention is to convey whether or not a popover is persistent or ephemeral. It is clickable so that you can manually pin/unpin but how often is that actually happening?
The only use case for clicking the button manually to unpin is to close the entire popover but there's already a leaf close button for that. In the case of multiple leafs, when we enable that, there will likely be a popover close button that would serve that purpose.
The only use case for clicking the button manually to pin is to mark the popover as persistent without first moving or resizing it. That's a valid use case but perhaps it could be replaced with logic that auto pins the popover on additional criteria.
Assuming those two use cases are no longer needed, the only thing left is visual indication.
If a popover is on the screen and you didn't just invoke it, it's pretty clear that it's a persistent popover so I'm not sure existing popovers need any indication.
So we're down to what to do to indicate the transition from an ephemeral popover to a persistent one at the time when the popover is first opened.

I'd actually like to have a keyboard command to "keep open" (pin in current terminology) available as well as the option to click something.  As I use the plugin I'm mostly finding I like auto-focus but not auto-pinning, and moving-to-pin is a pain.
I don't think that "you didn't just invoke it" is enough of an indicator, since you could get up and go away from your desk and come back and not be sure which one you invoked last.  I think the existence of this issue in the first place indicates that better visual feedback is needed, that's unequivocal as to the state, or else it's always possible to think a popup will persist and then have it vanish on you.
(Also, when you consider the keyboard commands for opening popups (frames?  windows?) and the possibility of API-created ones, a visual indicator seems a necessity.)
I once thought that typing or clicking in the main area should be enough to trigger the "keep open" state, but I soon found that with auto-focus I was often taking advantage of the fact that a popup was temporary even after I did things in it, saving me the trouble of the extra clicks to pin and close it.
I've been thinking about terminology a bit, trying to pin down (no pun intended) how to describe these things in the first place.  I'm currently leaning towards "auto-close" and "keep open" to describe the states, because e.g. "persistent" implies they would stay there past a restart of Obsidian or the plugin.  (And if at some point there is that option, that will probably need an indicator as well!)  I also lean towards open bookmark/filled bookmark as the visual indicator for whether you're keeping a window (frame? popup?) open, even if I agree that there's almost never a reason to switch it back to auto-close.
Other possible visual indicators: a "keep open" checkbox, some random symbol intended to suggest the window is temporary or transient (and disappears once clicked, becoming untoggle-able thereafter except in code), and...  well that's all my ideas, pretty much.  :)
Some advantages to the checkbox include the fact it's easy to theme, and it's easy to talk about a "keep open" checkbox vs. trying to talk about the opposite state.  The auto-pin setting then becomes "Automatically keep popups open (when moved or resized / always)", and the checkbox itself can have a hover-title of "Keep this popup open".

For me, lock indicates that it can't be moved as well or maybe can't be resized... or can't be edited... but I get your point.
Maybe we should consider if we even need the pin icon. Its current intention is to convey whether or not a popover is persistent or ephemeral. It is clickable so that you can manually pin/unpin but how often is that actually happening?
The only use case for clicking the button manually to unpin is to close the entire popover but there's already a leaf close button for that. In the case of multiple leafs, when we enable that, there will likely be a popover close button that would serve that purpose.
The only use case for clicking the button manually to pin is to mark the popover as persistent without first moving or resizing it. That's a valid use case but perhaps it could be replaced with logic that auto pins the popover on additional criteria.
Assuming those two use cases are no longer needed, the only thing left is visual indication.
If a popover is on the screen and you didn't just invoke it, it's pretty clear that it's a persistent popover so I'm not sure existing popovers need any indication.
So we're down to what to do to visually indicate the transition from an ephemeral popover to a persistent one at the time when the popover is first opened.

I like the idea of getting rid of pin.  Always pin it if it moves and the X at top tight for closing is enough to get rid of the hover box

https://github.com/nothingislost/obsidian-hover-editor/releases/tag/0.5.1 adds a class to popovers indicating whether or not they are pinned. This allows you to style the popover more easily based on the pinned state.
For example, to put a border around popovers that will auto close:
.popover.hover-popover:not(.is-pinned) {
  border: 3px solid var(--interactive-accent);
}

This will hide the pin icon for auto close popovers until you mouse over the popover
.popover.hover-popover:not(.is-pinned) .mod-pin-popover {
  display: none;
}

.popover.hover-popover:not(.is-pinned):hover .mod-pin-popover {
  display: block;
}


Add Polyp Histology to biospecimen template

Information
Proposed change:
Vanderbilt submitted a custom column, Polyp Histology, to their Biospecimen manifest, and requested it be made available on the data portal. Suggest we add this attribute to the data model so that it is displayed on the portal web.
Values submitted by Vanderbilt in the Polyp Histology column include: (seems to be normals and premalignant only)

Adenoma - tubular
Adenoma - tubulovillous
Normal
Serrated - hyperplastic
Serrated - hyperplastic - goblet cell-rich
Serrated - hyperplastic - microvesicular mucin-rich
Serrated - sessile serrated polyp
Serrated - traditional serrated adenoma
Unknown

Similar attributes exist in the data model under the Colorectal Tier 3 template: Colorectal Polyp Type and Colorectal Polyp Adenoma Type. These are not currently used in HTAN, and do not work for Vanderbilt as their designations are at the biospecimen level, not participant. Possibly rework Colorectal Polyp Type and Colorectal Polyp Adenoma Type to be optional Biospecimen elements?

Dicussion link:
Discussed on March 28, 2023 ops call
https://docs.google.com/document/d/18Krq5x-5dGcPxC9X_B24S5JMv0iXILF5_qwpvpUk4_U/edit#heading=h.fn0m8y7n5gab

How important is this feature?
Select from the options below

🌗 Medium - can do work without it; but it's important (e.g. to save time or for convenience)

Additional context
Implementation checklist

[ ] Branch created
[ ] HTAN.model.csv editied and pushed
[ ] HTAN.model.jsonld validated and created by Github action
[ ] PR opened
[ ] PR approved
[ ] PR merged into main
[ ] New Component added to ncihtan/HTAN-data-curator (if required)
[ ] DCA update requested
[ ] DCA updated

Review how centers have been using existing attributes, and for those that are required in CRC

Relevant notes: https://docs.google.com/document/d/1t8xPGKe5SFsWFqjjl4ukz0pqkldvewsnG6-Dszd63XM/edit#heading=h.gedw5u38si1z

Following discussion with @vthorsson, we think that the current set up where the portal displays only data model attributes, but the downloadable manifest contains all attributes submitted by the center (including Polyp Histology for Vanderbilt) is sufficient.
To avoid requiring an overhaul of templates and relevant attributes, we will not be adding Polyp Histology to the data model at this time. We can revisit should this become an issue in the future.


The links to copyright etc are taken from a resource file

From the code:
        <a href="<%= LocalizeString("Imprint.Url") %>" title="<%= LocalizeString("Imprint.Text") %>"><%= LocalizeString("Imprint.Text") %> |
        <a href="<%= LocalizeString("Privacy.Url") %>" title="<%= LocalizeString("Privacy.Text") %>"><%= LocalizeString("Privacy.Text") %>

The href values are taken from the resource file which I'm sure is in error. There are DNN controls that get the correct urls.

@donker your input sounds valid, @ropalko could you check / fix?

Created a new release v5.0.1


Update dependencies

Upgrade zwavejs2mqtt to v6.9.1
https://github.com/zwave-js/zwavejs2mqtt/releases/tag/v6.9.1

This isn't an issue, the relevant dependencies will be upgraded on the next maintenance cycle.


Typo in for loop

Is:
for fruit in fruits
  puts fruit
end

Should be:
for fruit in fruits do
  puts fruit
end

:+1:


Create 3 sum.cpp

Adding 3 sum

@jahnvisrivastava100 add only one solution and also mention the issue number


download files from list

we have a usecase where we want to download multiple files from artifactory, that live in paths which are not easily expressible by wildcards. Therefore we want to specify a list of files that should be downloaded, so that we can use the parallel downloading capabilities of the jfrog client
E.g.:
# the following entries in list.txt
npm/tweetnacl/-/tweetnacl-0.13.3.tgz
npm/ua-parser-js/-/ua-parser-js-0.7.10.tgz
npm/uc.micro/-/uc.micro-1.0.2.tgz
npm/underscore/-/underscore-1.8.3.tgz
npm/urijs/-/urijs-1.18.1.tgz

command which downloads all items listed in list.txt:
jfrog rt dl --from-list ./list.txt

Thank you for sharing this use case @leipert.
We are planning to start supporting a spec file, which defines the uploads or downloads to and from Artifactory. To allow maximum flexibility, the spec may include more information than just the list of files to be downloaded.

@leipert ,
JFrog CLI 1.5.0 includes the capability of using a spec file.
For more details about the spec option please refer to our documentation.

That looks promising. I am going to close this issue 👍


Invalid dependency resolution

Just pulled down the latest of the owf-framework and it cannot resolve the smack.jar 3.3.1 as it points to a repository that has since been shutdown:
Error |
Resolve error obtaining dependencies: The following artifacts could not be resolved: org.igniterealtime.smack:smack:jar:3.3.1, org.igniterealtime.smack:smackx:jar:3.3.1: Could not transfer artifact org.igniterealtime.smack:smack:jar:3.3.1 from/to repository_opencastproject_org_nexus_content_repositories_public (http://repository.opencastproject.org/nexus/content/repositories/public): Service Unavailable (503) (Use --stacktrace to see the full trace)
See:  https://groups.google.com/a/opencast.org/forum/#!topic/matterhorn/sGpkKQNwiMY

I have just pushed a commit to master that adds the missing dependencies directly to the lib directory, since I can't find them on any currently-running public maven instance.  If you are trying to build a prior release, cherry-pick commit 4720c5e before building in order to get the fix.


Shell opener fails on Trusnas core (FreeBSD) (sh)

io.xpipe.core.process.ProcessOutputException: Shell opener command was unsuccessful:
Illegal option -l
at io.xpipe.core.process.ProcessOutputException.withPrefix(ProcessOutputException.java:14)
at io.xpipe.ext.proc.util.c.a(SourceFile:145)
at io.xpipe.ext.proc.m.x(SourceFile:249)
at io.xpipe.ext.proc.m.start(SourceFile:196)
at io.xpipe.core.store.ShellStore.validate(ShellStore.java:31)
at io.xpipe.app.storage.DataStoreEntry.validateOrThrow(DataStoreEntry.java:398)
at io.xpipe.app.storage.DataStoreEntry.validate(DataStoreEntry.java:387)
at io.xpipe.ext.proc.env.l.a(SourceFile:37)
at io.xpipe.app.util.ScanAlert$1.lambda$finish$1(ScanAlert.java:158)
at io.xpipe.app.util.BooleanScope.execute(BooleanScope.java:11)
at io.xpipe.app.util.ScanAlert$1.lambda$finish$2(ScanAlert.java:146)
at io.xpipe.app.util.ThreadHelper.lambda$wrap$0(ThreadHelper.java:19)
at java.lang.VirtualThread.run(VirtualThread.java:309)

What kind of sh is that? Some kind of busybox?

Standard original FreeBSD /bin/sh, not busybox. Man page is here (note no -l):
https://man.freebsd.org/cgi/man.cgi?sh
Source code here: https://github.com/freebsd/freebsd-src/tree/main/bin/sh

Hmm I see. Usually most sh implementations at least allow the -l switch even if I does not do anything to provide some compatibility.
I will see what I can do to fix it

I think -l is a bash thing, rather than an sh thing, it's just a lot of linux distro's use bash as sh, ie:
$ ls -la /usr/bin/sh
lrwxrwxrwx 1 root root 4 Apr 25  2023 /usr/bin/sh -> bash
Pure sh even on linux doesn't seem to have an -l option: https://www.man7.org/linux/man-pages/man1/sh.1p.html

Can you try whether the latest PTB works for you: https://github.com/xpipe-io/xpipe-ptb ? Implemented a fix but did not have the time yet to properly test it everywhere.

Certainly! Unfortunately I see the same thing:
io.xpipe.core.process.ProcessOutputException: Shell opener command was unsuccessful:
Illegal option -l
at io.xpipe.core.process.ProcessOutputException.withPrefix(ProcessOutputException.java:20)
at io.xpipe.ext.proc.util.c.a(SourceFile:145)
at io.xpipe.ext.proc.m.x(SourceFile:249)
at io.xpipe.ext.proc.m.start(SourceFile:196)
at io.xpipe.core.store.ShellStore.validate(ShellStore.java:31)
at io.xpipe.app.storage.DataStoreEntry.validateOrThrow(DataStoreEntry.java:398)
at io.xpipe.app.storage.DataStoreEntry.validate(DataStoreEntry.java:387)
at io.xpipe.ext.proc.env.l.a(SourceFile:37)
at io.xpipe.app.util.ScanAlert$1.lambda$finish$1(ScanAlert.java:158)
at io.xpipe.app.util.BooleanScope.execute(BooleanScope.java:11)
at io.xpipe.app.util.ScanAlert$1.lambda$finish$2(ScanAlert.java:146)
at io.xpipe.app.util.ThreadHelper.lambda$wrap$0(ThreadHelper.java:19)
at java.lang.VirtualThread.run(VirtualThread.java:309)

Oh well, seems like I need to set up a BSD vm then.

It's easy enough to do! But if you need me to test, I'm happy to test.

Alright, I set up a BSD VM and properly fixed the issue. It was actually getting detected properly but it still added the normal sh dialect.
You can try it out in the latest PTB. (The missing sh icon can be ignored)

Nice, I can confirm it works for me now! Thanks!

This fix is now included in the latest release


Add AWS Command Line Tools (CLI)

Add AWS CLI and get rid of some stuff nobody is using.

were we ever planning on using redis? or is that just there by default?

:+1:

Redis was left over from the company we forked this from. We are not currently using it. When we do start to use things like Redis we should get them from docker instead of installing them straight on our macs.

LGTM


initialize correct curves when signing without an instance

What current issue(s) does this address, or what feature is it adding?
Addresses https://github.com/CityOfZion/neo-python-core/issues/176
How did you solve this problem?
Now the code initializes the correct curve parameters even if a CryptoInstance is not in use.
How did you make sure your solution works?
Wrote a test based on the code from https://github.com/CityOfZion/neo-python-core/issues/176
and make test
Did you add any tests?
Yes
Did you run make lint and make coverage?
Yes
Are there any special changes in the code that we should be aware of?
No
NOTE: I did search for other places where a private key is input and found none that are in use.

Thank you! I will keep working.

@ixje okay the tests are valid now. I am not sure what happened with my last rebasing but I didn't change anything with the initial commit. I made the changes in the "update..." commit.

setUp is called before every test case (whereas setupClass is called once for the whole TestCase class). This means tearDown didn't add anything

100 points seagrave

setUp is called before every test case (whereas setupClass is called once for the whole TestCase class). This means tearDown didn't add anything

@ixje thank you for clarifying! I misunderstood explanation when I was researching the functions.

https://neoscan.io/transaction/d5ae4a22ffe49912a2a3dc698d39ac63a8fcf2cef63ae136850d039c312591d8


Implement async iterator

🚀 Feature Proposal
A clear and concise description of what the feature is.
Motivation
To allow native for await usage
Example
const navigations = appHistory
  .filter(isNavigateEvent)
  .map(e => e.destination.url)

for await (const url of navigations) {
  console.log({ url });
}

Out of scope


Adding vim to Docker image

Purpose/implementation Section
What changes are being implemented in this Pull Request?
Addresses the first point in #232

This works! Merging!