bug: erzak yardım ve teyitlide Son 3 gün ve Tüm zamanlar dışında veri gelmemesi

Error Description
Teyitli ve erzak yardım seçimlerinde son 24 saat ve öncesindeki veriler gelmiyor. Şu an aktif veri mi yok, kontrol eder misiniz?
-- Add this info:
discord username: cccececcc#4824
Error Environment
afetharita.com
Describe how you got the error step by step
Bildirimler/Erzak Yardım & Teyitli
bildirimler/Son 24  ve öncesi
Expected Behaviour
Haritada verilerin gelmesi
Screenshots

Desktop Environment

Operating System: Windows 11
Browser Chrome
Version 109.0.5414.120

Hi, now all our content is in English. I will activate it again when you make the translation.

think about this

hi
i think the major problem with this issue is not related with the code itself but database records. for "live aid" filter sends reason key as "erzak" value. but as far i see, these record timestamp values somehow have been set to a fixed value to<PHONE_NUMBER> which is equal to  February 9, 2023 9:12:32, as of 2/12/2023 3:23 AM (right now) means "2 days ago"

that means these records gets only when you supply timestamp value older than  February 9, 2023 9:12:32.  if you supply newer date timestamp for example last 24 hours, it won't work. that explains why these records can be seen on "all the times" or last 3 days conditions. actually "all the times" simply sets a year ago from now. so any timestamp value older than Feb 9 meets epoch >= timestamp condition.
above all also valid for "confirmed" section. i didn't check but probably these fields somehow left as its default value or something.
thanks for your hard work.

My account was hacked and I lost almost everything $520,000 I have saved over the years until I found a legit hacker who helped me recover a lot of money in 3 days it was a surprise to me because I do not believe that one can hack money from account just with the bank and front picture of the credit or debit card without holding the card or asking for more details
this was the best experience ever if you have a credit of debit card with good funds and you are ready to transfer the money to your personal account without any trace and you can invest in any business of your choice and enjoy life to the fullest here is the contact of the best hacker in the world I call him GURU
contact him here AT  expertrecovery @ gomail com,


Android tools version.

This change is

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


[Feature request] Add Webex Teams (Cisco Spark) channel

Can we get Webex Teams Channel anytime soon?

Is there any update on this Issue??

@vviswadeep BotKit, built on the Bot Framework, has a WebEx Adapter: https://botkit.ai/docs/v4/platforms/webex.html

We do have this on our overall backlog, but as Eric mentions, the BotKit adapter hopefully will be useful for your needs.  Thanks!


you need to checking IPermissions

I could not get the solution to build because the IPermissions class doesnt exist in git

Restore the nuget packages :P
Secondly, if you want a reply in the future, please use the issue template


ci(release): update types array

Pull Request Test Coverage Report for Build 674686824

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 674669656:
0.0%

Covered Lines:
699

Relevant Lines:
699

💛  - Coveralls


Small group see leader

Fixes #258

do you know what's up with these commits being funky and including stuff already on master?

No, other than its undoubtably a mistake of mine in the endless mysteries of git. I asked Seve about it and he said to put it up so he could take a look and see if anything needed to be done about it.

Sounds good. If he can't figure it out I'll take a look too

Why add a need fixing? there is no known problem that needs to be fixed, or a trace of one other than a fluke test which has passed the same code on a subsequent run.

Its due to the odd commits included

might we merge this before new conflicts arise?

@seveibar  while there are the weird commits, the merges from master show no problems. and you assessment of the visual was roughly thats looks good, ready to get merged so...

thanks for the follow up Alex, I think it's okay to get merged


Provide api for mapping implementation to interface

Currently for creating implementation and providing it everywhere by it's interface we need to do something like that:
class ImplDep : BaseDep
interface BaseDep
class Target(dep: BaseDep)

class Module {
    @Create fun target(): Target

    @Create private fun impl(): ImplDep
    private fun baseDep(): BaseDep = impl()
}

or
    @UseConstructors(ImplDep::class)
    @Create private fun dep(): BaseDep
    private fun baseDep(impl: ImplDep): BaseDep = impl

Seems too boilerplate either way. Need to find an api that would allow to do that in one line while supporting different cases: 1. implementation is provided by property or function and 2. implementation is created using constructor

When implementation is provided somewhere it seems fairly simple to use this:
fun baseDep(): BaseDep = impl()

But when we want to use constructor and implementation isn't used anywhere directly it might be a good idea to add a parameter to @Create and @CreateSingle like this
@Create(ImplDep::class) fun dep(): BaseDep

Not sure if this api looks straitforward enough

With new API it's easier to map implementations using fun something(): Base = resolve<Impl>()


.Net: Add changes to the values of the plan parameters while the  HandlebarsPlan  is running

Env: RC4 .NET Core 7
Here is my code
string handlbar_plan = "{{!-- Step 1: Set the generate_analysis_report variable --}}\n" +
"{{set "generate_analysis_report" "$generate_analysis_report"}}" +
"\n\n" +
"{{!-- Step 2: Create a file name for the report --}}\n" +
"{{set "file_name" (concat "generate_analysis_report_" ".txt")}}" +
"\n\n" +
"{{!-- Step 3: Save the generate_analysis_report content to a local file --}}" +
"\n" +
"{{ExtenedFilePlugin-WriteFileContent content=(get "generate_analysis_report") path=(get "file_name")}}" +
"\n\n" +
"{{!-- Step 4: Upload the local file to OneDrive --}}" +
"\n" +
"{{OneDrive-UploadFile filePath=(get "file_name") destinationPath=(concat "/OneDriveFolder/" (get "file_name"))}}" +
"\n\n" +
"{{!-- Step 5: Output the result --}}" +
"\n" +
"{{json "The analysis report has been saved to OneDrive."}}";
HandlebarsPlan reloadedPlan = new HandlebarsPlan(handlbar_plan, "");
var reloadedPlan_re  = await reloadedPlan.InvokeAsync(sk._SK_Kernel, new KernelArguments()
{
["$generate_analysis_report"]="1111"
["generate_analysis_report"]="1111"
});
The plan has a parameter named "generate_analysis_report" .I haven't found any way to change this value at runtime

Hey @strikene, what are you using as the goal for the plan?
Either way, you can load the variables into the KernelArgs using this syntax:
        HandlebarsPlan reloadedPlan = new HandlebarsPlan(handlebars_plan, "");
        var reloadedPlan_re = await reloadedPlan.InvokeAsync(sk._SK_Kernel, new KernelArguments()
        {
            { "generate_analysis_report", "1111" }
        });

Note:

When referencing a variable, you don't need to prefix it with $. It can just be generate_analysis_report, so the first step would be: "{{set "generate_analysis_report" "$generate_analysis_report"}}"
The variables referenced in the Handlebars prompt template must match with the keys defined in the KernelArguments dictionary, so if you want to keep the $, the KernelArguments entry would be { "$generate_analysis_report", "1111" }

Hey @strikene, what are you using as the goal for the plan?
Either way, you can load the variables into the KernelArgs using this syntax:
        HandlebarsPlan reloadedPlan = new HandlebarsPlan(handlebars_plan, "");
        var reloadedPlan_re = await reloadedPlan.InvokeAsync(sk._SK_Kernel, new KernelArguments()
        {
            { "generate_analysis_report", "1111" }
        });

Note:

When referencing a variable, you don't need to prefix it with . It can just be , so the first step would be: $``generate_analysis_report``"{{set "generate_analysis_report" "$generate_analysis_report"}}"
The variables referenced in the Handlebars prompt template must match with the keys defined in the KernelArguments dictionary, so if you want to keep the , the KernelArguments entry would be $``{ "$generate_analysis_report", "1111" }

Thanks for the help, I'll try it later~
In my case, goal is a single step after a complex step decomposition, and we try to break down the complex action into simpler, atomic-level steps through the prompt word, so as to ensure that the planner chooses the function as little as possible without "illusion"
The variable $generate_analysis_report is the result of the previous step referenced by the current step, and this method works reliably. In the previous sequence planner we could easily pass it on.

Hey @strikene, what are you using as the goal for the plan?
Either way, you can load the variables into the KernelArgs using this syntax:
        HandlebarsPlan reloadedPlan = new HandlebarsPlan(handlebars_plan, "");
        var reloadedPlan_re = await reloadedPlan.InvokeAsync(sk._SK_Kernel, new KernelArguments()
        {
            { "generate_analysis_report", "1111" }
        });

Note:

When referencing a variable, you don't need to prefix it with . It can just be , so the first step would be: $``generate_analysis_report``"{{set "generate_analysis_report" "$generate_analysis_report"}}"
The variables referenced in the Handlebars prompt template must match with the keys defined in the KernelArguments dictionary, so if you want to keep the , the KernelArguments entry would be $``{ "$generate_analysis_report", "1111" }

I have come up with the test results
1."{{set "generate_analysis_report" "XXXXXX"}}"      No matter which way I use it in the arguments, I can't change the value of this variable at runtime (in my case, generate_analysis_report writes the contents as a file to the local file, so it's good to judge)
2."{{set "$generate_analysis_report" "XXXXXX"}}"
using  KernelArguments saved_handlbar_plan_arguments = new()
{
{ "generate_analysis_report", "1111" }
};  it works . but  ‘{{set "generate_analysis_report" "XXXXXX"}}’ it create by planner . I can't interfere with the planner generating variables with the '$' prefix, so I can't change their values

Hey @strikene, what are you using as the goal for the plan?
Either way, you can load the variables into the KernelArgs using this syntax:
        HandlebarsPlan reloadedPlan = new HandlebarsPlan(handlebars_plan, "");
        var reloadedPlan_re = await reloadedPlan.InvokeAsync(sk._SK_Kernel, new KernelArguments()
        {
            { "generate_analysis_report", "1111" }
        });

Note:

When referencing a variable, you don't need to prefix it with . It can just be , so the first step would be:  $generate_analysis_report"{{set "generate_analysis_report" "$generate_analysis_report"}}"
The variables referenced in the Handlebars prompt template must match with the keys defined in the KernelArguments dictionary, so if you want to keep the , the KernelArguments entry would be  ${ "$generate_analysis_report", "1111" } ``

@teresaqhoang

I have come up with the test results 1."{{set "generate_analysis_report" "XXXXXX"}}" No matter which way I use it in the arguments, I can't change the value of this variable at runtime (in my case, generate_analysis_report writes the contents as a file to the local file, so it's good to judge)
2."{{set "$generate_analysis_report" "XXXXXX"}}" using KernelArguments saved_handlbar_plan_arguments = new() { { "generate_analysis_report", "1111" } }; it works . but ‘{{set "generate_analysis_report" "XXXXXX"}}’ it create by planner . I can't interfere with the planner generating variables with the '$' prefix, so I can't change their values

Hey @strikene, what are you using as the goal for the plan?
Either way, you can load the variables into the KernelArgs using this syntax:
        HandlebarsPlan reloadedPlan = new HandlebarsPlan(handlebars_plan, "");
        var reloadedPlan_re = await reloadedPlan.InvokeAsync(sk._SK_Kernel, new KernelArguments()
        {
            { "generate_analysis_report", "1111" }
        });

Note:

When referencing a variable, you don't need to prefix it with . It can just be , so the first step would be: $``generate_analysis_report``"{{set "generate_analysis_report" "$generate_analysis_report"}}"
The variables referenced in the Handlebars prompt template must match with the keys defined in the KernelArguments dictionary, so if you want to keep the , the KernelArguments entry would be $``{ "$generate_analysis_report", "1111" }

@teresaqhoang
I have come up with the test results
1."{{set "generate_analysis_report" "XXXXXX"}}" No matter which way I use it in the arguments, I can't change the value of this variable at runtime (in my case, generate_analysis_report writes the contents as a file to the local file, so it's good to judge)
2."{{set "$generate_analysis_report" "XXXXXX"}}"
using KernelArguments saved_handlbar_plan_arguments = new()
{
{ "generate_analysis_report", "1111" }
}; it works . but ‘{{set "generate_analysis_report" "XXXXXX"}}’ it create by planner . I can't interfere with the planner generating variables with the '$' prefix, so I can't change their values

Related to https://github.com/microsoft/semantic-kernel/issues/4072, @matthewbolanos we should consider if and how to expose initial variables to the planner.
Added variable access testing to this issue here: https://github.com/microsoft/semantic-kernel/issues/4252

Closing as a dupe of #4422


Determine completed status without downloading videos?

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.02.10. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

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

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] 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

How can I determine from bash if youtube-dl still has work to do for a particular playlist WITHOUT downloading videos?  For example, if youtube-dl is used to CONTINUE downloading an existing playlist (for example, a Pluralsight course, a Youtube channel, etc.), youtube-dl loads the manifest and determines one-by-one if a video has already been downloaded.  I would like to use youtube-dl to determine if all of the videos have already been downloaded WITHOUT doing the actual download.  The goal is to mark the Pluralsight course or Youtube channel as "complete" so I may continue with other automated processing.

Store video ids in --download-archive per playlist. List ids for a playlist with -o '%(extractor)s %(id)s' --get-filename and match against the archive file. If all of them present in the archive file then it's finished.


test: improve import tests

Add respawn_lxd() and shutdown_lxd() to allow stopping and restarting an
already running LXD daemon in the test-suite.
Stop the daemon before calling sqlite3 to avoid db locked errors in the
test-suite.

Signed-off-by: Christian Brauner<EMAIL_ADDRESS>

Can you split this in 3 commits:

Add the new helpers
Port the existing use case for this (lxd shutdown test) over to it
Change the "lxd import" tests to use this?

That will let me cherry-pick the first two to stable-2.0 and keep the 3rd only for master.

@stgraber, sure.

@stgraber, done.

@stgraber, should be good to merge. db locked errors are gone.

@brauner any idea where that "not found" error comes from? it was there before this fix too

Anyway, merging this one as it's not making things worse.

Likely storage that is accidentally unmounted.

or not mounted


Improve DQ Resolution Flow

Context and Abstract
In 1.1.0 we introduce a resolution flow allowing user to understand the status of a data quality failure. In of 1.1.0 and 1.2.0 users are able to set 3 status:

New: denote a newly failed data quality test
Ack: denote an acknowledge failure (i.e. we are working on solving it)
Resolved: denote a solved data quality failure

in 1.3.0 we will introduce an enhanced flow adding 2 additional status:

assign: allows to assign the resolution to someone else

assignee

review: we'll be introducing a new policy tests resolution approval, users without this policy will not be able to mark issue as resolved. They will need to set a reviewer. It should include the following fields

reviewer
resolution summary

assigning an assignee or a reviewer should open a task for the user of concern. Closing a task for an assignee result in a review or a resolution (depending on the permission). Closing a reviewer task should result in a resolution. When a task is marked as resolved, a user should be able to choose if they want to mark all the previously failed tests as resolved as well.
We will also prevent users from changing the status of a resolved test case failure.
User Stories

As a user I want to be able to track what DQ issues do I need to solve
As a user I want to be able to control who can mark a DQ issue as resolved

Resolution flow approval diagram

Below are the lists of all the permutation for the task status
combination ('New', 'Ack')
-------
New -> Ack
Ack -> New

combination ('New', 'Assigned')
-------
New -> Assigned
Assigned -> New

combination ('New', 'InReview')
-------
New -> InReview
InReview -> New

combination ('New', 'Resolved')
-------
New -> Resolved

combination ('Ack', 'Assigned')
-------
Ack -> Assigned
Assigned -> Ack

combination ('Ack', 'InReview')
-------
Ack -> InReview
InReview -> Ack

combination ('Ack', 'Resolved')
-------
Ack  -> Resolved

combination ('Assigned', 'InReview')
-------
Assigned -> InReview
InReview -> Assigned

combination ('Assigned', 'Resolved')
-------
Assigned -> Resolved

combination ('InReview', 'Resolved')
-------
Resolved -> InReview

combination ('New', 'Ack', 'Assigned')
-------
New -> Ack -> Assigned
New -> Assigned -> Ack
Ack -> New -> Assigned
Ack -> Assigned -> New
Assigned -> New -> Ack
Assigned -> Ack -> New

combination ('New', 'Ack', 'InReview')
-------
New -> Ack -> InReview
New -> InReview -> Ack
Ack -> New -> InReview
Ack -> InReview -> New
InReview -> New -> Ack
InReview -> Ack -> New

combination ('New', 'Ack', 'Resolved')
-------
New -> Ack -> Resolved
Ack -> New -> Resolved

combination ('New', 'Assigned', 'InReview')
-------
New -> Assigned -> InReview
New -> InReview -> Assigned
Assigned -> New -> InReview
Assigned -> InReview -> New
InReview -> New -> Assigned
InReview -> Assigned -> New

combination ('New', 'Assigned', 'Resolved')
-------
New -> Assigned -> Resolved
Assigned -> New -> Resolved

combination ('New', 'InReview', 'Resolved')
-------
New -> InReview -> Resolved
InReview -> New -> Resolved

combination ('Ack', 'Assigned', 'InReview')
-------
Ack -> Assigned -> InReview
Ack -> InReview -> Assigned
Assigned -> Ack -> InReview
Assigned -> InReview -> Ack
InReview -> Ack -> Assigned
InReview -> Assigned -> Ack

combination ('Ack', 'Assigned', 'Resolved')
-------
Ack -> Assigned -> Resolved
Assigned -> Ack -> Resolved

combination ('Ack', 'InReview', 'Resolved')
-------
Ack -> InReview -> Resolved
InReview -> Ack -> Resolved

combination ('Assigned', 'InReview', 'Resolved')
-------
Assigned -> InReview -> Resolved
InReview -> Assigned -> Resolved

combination ('New', 'Ack', 'Assigned', 'InReview')
-------
New -> Ack -> Assigned -> InReview
New -> Ack -> InReview -> Assigned
New -> Assigned -> Ack -> InReview
New -> Assigned -> InReview -> Ack
New -> InReview -> Ack -> Assigned
New -> InReview -> Assigned -> Ack
Ack -> New -> Assigned -> InReview
Ack -> New -> InReview -> Assigned
Ack -> Assigned -> New -> InReview
Ack -> Assigned -> InReview -> New
Ack -> InReview -> New -> Assigned
Ack -> InReview -> Assigned -> New
Assigned -> New -> Ack -> InReview
Assigned -> New -> InReview -> Ack
Assigned -> Ack -> New -> InReview
Assigned -> Ack -> InReview -> New
Assigned -> InReview -> New -> Ack
Assigned -> InReview -> Ack -> New
InReview -> New -> Ack -> Assigned
InReview -> New -> Assigned -> Ack
InReview -> Ack -> New -> Assigned
InReview -> Ack -> Assigned -> New
InReview -> Assigned -> New -> Ack
InReview -> Assigned -> Ack -> New

combination ('New', 'Ack', 'Assigned', 'Resolved')
-------
New -> Ack -> Assigned -> Resolved
New -> Assigned -> Ack -> Resolved
Ack -> New -> Assigned -> Resolved
Ack -> Assigned -> New -> Resolved
Assigned -> New -> Ack -> Resolved
Assigned -> Ack -> New -> Resolved

combination ('New', 'Ack', 'InReview', 'Resolved')
-------
New -> Ack -> InReview -> Resolved
New -> InReview -> Ack -> Resolved
Ack -> New -> InReview -> Resolved
Ack -> InReview -> New -> Resolved
InReview -> New -> Ack -> Resolved
InReview -> Ack -> New -> Resolved

combination ('New', 'Assigned', 'InReview', 'Resolved')
-------
New -> Assigned -> InReview -> Resolved
New -> InReview -> Assigned -> Resolved
Assigned -> New -> InReview -> Resolved
Assigned -> InReview -> New -> Resolved
InReview -> New -> Assigned -> Resolved
InReview -> Assigned -> New -> Resolved

combination ('Ack', 'Assigned', 'InReview', 'Resolved')
-------
Ack -> Assigned -> InReview -> Resolved
Ack -> InReview -> Assigned -> Resolved
Assigned -> Ack -> InReview -> Resolved
Assigned -> InReview -> Ack -> Resolved
InReview -> Ack -> Assigned -> Resolved
InReview -> Assigned -> Ack -> Resolved

combination ('New', 'Ack', 'Assigned', 'InReview', 'Resolved')
-------
New -> Ack -> Assigned -> InReview -> Resolved
New -> Ack -> InReview -> Assigned -> Resolved
New -> Assigned -> Ack -> InReview -> Resolved
New -> Assigned -> InReview -> Ack -> Resolved
New -> InReview -> Ack -> Assigned -> Resolved
New -> InReview -> Assigned -> Ack -> Resolved
New -> Resolved -> Ack -> Assigned -> InReview
New -> Resolved -> Ack -> InReview -> Assigned
New -> Resolved -> Assigned -> Ack -> InReview
New -> Resolved -> Assigned -> InReview -> Ack
New -> Resolved -> InReview -> Ack -> Assigned
New -> Resolved -> InReview -> Assigned -> Ack
Ack -> New -> Assigned -> InReview -> Resolved
Ack -> New -> InReview -> Assigned -> Resolved
Ack -> Assigned -> New -> InReview -> Resolved
Ack -> Assigned -> InReview -> New -> Resolved
Ack -> InReview -> New -> Assigned -> Resolved
Ack -> InReview -> Assigned -> New -> Resolved
Ack -> Resolved -> New -> Assigned -> InReview
Ack -> Resolved -> New -> InReview -> Assigned
Ack -> Resolved -> Assigned -> New -> InReview
Ack -> Resolved -> Assigned -> InReview -> New
Ack -> Resolved -> InReview -> New -> Assigned
Ack -> Resolved -> InReview -> Assigned -> New
Assigned -> New -> Ack -> InReview -> Resolved
Assigned -> New -> InReview -> Ack -> Resolved
Assigned -> Ack -> New -> InReview -> Resolved
Assigned -> Ack -> InReview -> New -> Resolved
Assigned -> InReview -> New -> Ack -> Resolved
Assigned -> InReview -> Ack -> New -> Resolved
InReview -> New -> Ack -> Assigned -> Resolved
InReview -> New -> Assigned -> Ack -> Resolved
InReview -> Ack -> New -> Assigned -> Resolved
InReview -> Ack -> Assigned -> New -> Resolved
InReview -> Assigned -> New -> Ack -> Resolved
InReview -> Assigned -> Ack -> New -> Resolved

Tasks
Backend

[x] #14049
[x] Add assign status.
[ ] Create "resolution approval" permission
[x] #14248
[x] Make test case resolution status with status "resolved" immutable
[x] #14331
[ ] Implement severity failure inference

Ingestion

[ ] Update logic to post in the new flow

UI

[ ] Implement Resolution center as per mock

Scenario 1 - Incident Details Page

Create Test Case
Run Test that fails

The backend will automatically a NEW incident will be created

We can get the incidentId from the testCase
From the DQ page, we see Incidents column with NEW
Clicking on NEW will send us to the Incident page
We will see Issues (1 Open)
We click on Issues
We add a comment on the issue
We click on Reassign

The UI will send a POST request to /api/v1/dataQuality/testCases/testCaseIncidentStatus with the "testCaseResolutionStatusType": "Assigned"
The backend will reassign the task under the hood (The UI does not need to "talk" to the task directly)

The new user, clicks on Resolve

The UI will send a POST request to /api/v1/dataQuality/testCases/testCaseIncidentStatus with the "testCaseResolutionStatusType": "Resolved"
The backend will automatically resolve and close the task. The UI does not need to talk to the task directly

We can validate that the incident is indeed Resolved and that the task is closed.

Scenario 2 - Resolving task from the Incident List Page

Create Test Case
Run Test that fails

The backend will automatically a NEW incident will be created

We can get the incidentId from the testCase
We go to the Incident Manager list page
We see our incident with status NEW
We click on Reassign

The UI will send a POST request to /api/v1/dataQuality/testCases/testCaseIncidentStatus with the "testCaseResolutionStatusType": "Assigned"
The backend will reassign the task under the hood (The UI does not need to "talk" to the task directly)

We click on Resolve

The UI will send a POST request to /api/v1/dataQuality/testCases/testCaseIncidentStatus with the "testCaseResolutionStatusType": "Resolved"
The backend will automatically resolve and close the task. The UI does not need to talk to the task directly

We can validate that the incident is indeed Resolved and that the task is closed.

Scenario 3 - Resolving & Rerunning

Create Test Case
Run Test that fails

The backend will automatically a NEW incident will be created

We can get the incidentId from the testCase
We go to the Incident Manager list page
We click on Resolve
We can validate that the incident is indeed Resolved and that the task is closed.
We trigger the test failure again
A NEW task is created
We should have 1 open incident

1 open task
1 closed task

We Resolve the open incident
It will close the open task

Scenario 4 - Rerunning an open incident

Create Test Case
Run Test that fails

The backend will automatically a NEW incident will be created

We can get the incidentId from the testCase
The DQ page shows a NEW incident
If we click, we see that we have only 1 ongoing incident and 1 open task
Rerunning the test case again to trigger another failure won't open another task

NEW
ACK

Open a task with the selected assignee

ASSIGNED

Open a task with the selected assignee if no task was created in ACK
If we go from ACK -> ASSIGNED, we update the task

RESOLVED

must be manually closed
we won't automatically close after the test passes
only one unresolved incident alive at a time per each test case

We'll force the flow:

NEW -> (ACK | ASSIGNED) -> ASSIGNED -> RESOLVED

NEW

ACK

Open a task with the selected assignee

ASSIGNED

Open a task with the selected assignee if no task was created in ACK
If we go from ACK -> ASSIGNED, we update the task

RESOLVED

must be manually closed
we won't automatically close after the test passes
only one unresolved incident alive at a time per each test case

We'll force the flow:

NEW -> (ACK | ASSIGNED) -> ASSIGNED -> RESOLVED

Do we need any change from UI side?


Dynamic icon added

Issue no. #518
Added a common favicon to the site and a separate favicon to 404 page.
For All pages:

For 404 page:

The change is not reflecting for 404. Check the deploy preview
Please make sure that the assets are loaded from the local folder of the project itself and not from CDN

Ok, @smaranjitghose, I will resolve this issue, and do another PR, and closing this one.


Invalid name for a Snapshot build asset

Hi,
I'm trying to use this plugin for publishing package and everything works good beside of publishing SNAPHSOT versions. DO anyone had issue like this? Or could help me with it?

Would you mind sharing your build file? I would be happy to take a look and try to reproduce the problem.

I will add it shortly today

Hi,
I was also recently trying to publish some SNAPSHOT version of Maven package to CodeArtifact using sbt-codeartifact. I came across the same issue. I did some debugging and here's what I found. As far as I understand this plugin doesn't support publishing SNAPSHOT versions.

First of all the names of published assets are wrong in case of snapshots. They should be published in the following format: <package_name>-<version_without_snapshot>-<timestamp(yyyyMMdd.HHmmss)>-<buildNumber>-<optional_classifier>.<extension (pom/jar)>. Secondly the format of maven-metadata.xml is completely wrong for SNAPSHOT versions.

The second example of maven-metadata.xml file under this link: example of maven-metadata.xml shows a correct form of this file for SNAPSHOT version.

Here's a screenshot from my debugging session showing that CodeArtifact returned 400 because of wrong asset name for SNAPSHOT version of a package.

Thanks for the details. I'll take a look at this tonight after work.

Quick update: I haven't solved this yet. I've made some progress, but work/life has been busy. I'll keep at it as time allows.

Is there any update on this issue? It is really an important feature.

I'm sorry, my new job has kept me very busy, and I don't foresee having time to address this. Please feel free to submit a PR. I will be happy to review it.

when publishing, i am getting my Scala version appended to the package name example: myRepository:myPackageName_myScalaVersion how to remove the _myScalaVersion


Update manifests/m/Microsoft/VCRedist/2015+/arm64/14.40.33816.0/Microsoft.VCRedist.2015+.arm64.locale.en-US.yaml

Fixes an issue where this package has multiple different monikers
Microsoft Reviewers: Open in CodeFlow

[Policy] Needs-Attention

@wingetbot run

@wingetbot run


⚠ Bofrost.nl has degraded performance

In 3c45d72, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1312 ms

Resolved: Bofrost.nl performance has improved in 15722db.


azure acs-engine

Codecov Report

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

@@          Coverage Diff           @@
##           master    #172   +/-   ##
======================================
  Coverage    3.56%   3.56%
======================================
  Files          15      15
  Lines         673     673
======================================
  Hits           24      24
  Misses        649     649

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 e79711f...03b6532. Read the comment docs.

Always create your branch from master, unless there is a good reason not to do so. :) @tahsinrahman


Repos, Azure DevOps and AAD control access policy, Denie Access while cloning repro

Problem: If Databricks is configured to use Azure DevOps with AAD authentication and the customer has enabled control access policy in Azure DevOps and has a AAD control access policy enabled a user could get a "Denied Access" error message trying to clone a repro. The error message that comes back to the Databricks control plane from AAD is not bubbled up to the UI so you do not know you are hitting this issue. CAP=Control Access Policy, https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-policies
Resolution: You can add an exclusion to the CAP in AAD for IP address or users of Databricks.
Ask is to document REPOS/Azure DevOps/AAD CAP issue and feature request to bubble up the error message to UI so users know they are hitting CAP.

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

ID: 8b98be98-e0dc-e08c-8a0d-b87571cc77b9
Version Independent ID: 8b98be98-e0dc-e08c-8a0d-b87571cc77b9
Content: Repos for Git integration - Azure Databricks
Content Source: databricks/repos/index.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@wpcarroll  Thanks for the feedback! I have assigned the issue to the content author to evaluate and add the details.

Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7111) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close


Merge master into develop

Closes https://github.com/lvgl/lvgl_esp32_drivers/issues/146

@C47D This PR resolves conflicts between master and develop. It can be successfully build (check GH actions)
I'll have to test in on HW before merging, though

Update: tested and working with ESP32S2 + ST7789 + LVGL v8.
I understand that the other drivers were not updated to LVGL v8 yet.

Hi @tore-espressif, I think that particular driver should work with both LVGL v7 and v8, I will need to check the latest merged pull requests. I'm getting older and can't remember from the top of my head.
Thanks for taking the time to solve this issue, I know is not very fun to do :)

Well, I caused the whole problem, it's shame that it took me so long.
If this gets merged into develop, do you want to merge develop to master ASAP? As far as I understand it, there will be inconsistencies between drivers.
(Related discussion https://github.com/lvgl/lvgl_esp32_drivers/pull/188)

Hi, don't worry. We could merge develop into master and firstly fix compilation errors. Then update drivers gradually. What do you think?

Fair enough 👍


HIVE-21678

There are three commits, each commit message explains what's contained in it and why they are separate. Finally all these commits should be squashed into a single commit.

Issue resolved in JIRA:
https://issues.apache.org/jira/browse/HIVE-21678


More recent version of LibGD

Is there a technical reason to not add LibGD 2.3.3 to the package?
Especially for WebP and AVIF support in PHP 8.2.

Right. Note even LibDG can be updated, the PHP 8.2.0 included a GD bundled and the version is 2.1.0. Contributions to the project are welcome!

GD Version => bundled (2.1.0 compatible)


Update zmq.hpp

This fixes issues like https://github.com/zeromq/cppzmq/issues/40

@jonnydee Does fix compile issues on Ubuntu 16.04.

Another fix for size_t - int conversions.

@jonnydee When will you merge my changes?

Hi, I'm sorry. I merged your changes. Thanks a lot :-)
Diese EMail ist digital signiert.
This email is digitally signed
----- Original Message -----
From: "Matthias Dieter Wallnöfer"<EMAIL_ADDRESS>Sent: 08.05.2017 - 09:37
To: jonnydee/nzmqt<EMAIL_ADDRESS>Subject: Re: [jonnydee/nzmqt] Update zmq.hpp (#35)

@jonnydee When will you merge my changes?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/jonnydee/nzmqt/pull/35#issuecomment-299795030


'tomorrow + 1 day' vs. 'tomorow + 1 day'  (rr vs. r); problem only when in >1 lines

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
This does not work as expected, because I wrote 'tomorrow' correct in both lines. ;-)
not done
due after tomorrow + 1 day
due before tomorrow + 3 days
explain

This works, because there is one bug 'r' in the second line. ;-)
not done
due after tomorrow + 1 day
due before tomorow + 3 days
explain

This one does not works, because I wrote it once correct: ;-)
not done
due after tomorow + 1 day
due before tomorrow + 3 days
explain

This one works, because there are 2 bugs 'r' in it. ;-)
not done
due after tomorow + 1 days
due before tomorow + 3 days

explain

If you try 'tomorrow' or 'tomorow' without the addition, the plugin recognizes the 'rr' error.
Can you please solve it till tomorrow? ;-)
Current behaviour
see before
Steps to reproduce
see before
Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[ ] macOS
[X] Windows

Obsidian Version
1.1.16
Tasks Plugin Version
3.0.0
Checks

[ ] I have tried it with all other plugins disabled and the error still occurs

Possible solution
No response

Could you please explain what you are wanting the search to do?

In Germany, we have a word for the day after tomorrow: "übermorgen".
I want to have the dates from "übermorgen".
Today we have 2023-04-08, tomorrow is 2023-04-09, "übermorgen" is 2023-04-10.

What is happening ... (there is no bug)
Just to note that the interpreting of text in queries is done by the chrono library, as explained near the start of this page in the Tasks docs:
Filters - Tasks User Guide - Obsidian Publish
So filters need to be written in vocabulary that chrono understands.

not done
due after tomorrow + 1 day
due before tomorrow + 3 days
explain

It's good that you used the explain instruction, as it does demonstrate what is happening.
Today is 8th April. The above explanation is is:
Explanation of this Tasks code block query:

not done

due after tomorrow + 1 day =>
  due date is after 2023-04-09 (Sunday 9th April 2023)

due before tomorrow + 3 days =>
  due date is before 2023-04-09 (Sunday 9th April 2023)

Tomorrow is spelled correctly, so the due lines are interpreted as due before tomorrow and due after tomorrow - as shown in the explanation.. and which of course can never find any tasks, as they are all either due before, or after, the date, but cannot be both.

This one works, because there are 2 bugs 'r' in it. ;-)
not done
due after tomorow + 1 days
due before tomorow + 3 days

explain

Here, the explanation is:
Explanation of this Tasks code block query:

not done

due after tomorow + 1 days =>
  due date is after 2023-04-09 (Sunday 9th April 2023)

due before tomorow + 3 days =>
  due date is before 2023-04-11 (Tuesday 11th April 2023)

Because you mis-spelled tomorrow, chrono ignores that, and instead goes on the read the remaining text + 1 days and + 3 days.
In fact, it does not read + as any conventional date pattern, so it is reading 1 day and 3 days.
So your misspelling of the tomorrow is causing chrono to read the actual valid text later in the line.
Correcting your filters
I don't know where the search phrase tomorrow + 1 days came from, but it is not something in the Tasks docs, and is the source of the confusion.
If you change your filter to this, you will get the intended results:
not done

# These two are equivalent - whichever you prefer:
due after tomorrow
due after 1 day

due before 3 days
explain

which explains as:
Explanation of this Tasks code block query:

not done

due after tomorrow =>
  due date is after 2023-04-09 (Sunday 9th April 2023)

due after 1 day =>
  due date is after 2023-04-09 (Sunday 9th April 2023)

due before 3 days =>
  due date is before 2023-04-11 (Tuesday 11th April 2023)

Simpler still
Since you are wanting tasks done on a particular day, this can be done like this:
due in 2 days
explain

Explanation is:
Explanation of this Tasks code block query:

due in 2 days =>
  due date is on 2023-04-10 (Monday 10th April 2023)

I trust this explanation is clear.
I'm going to close the ticket as no action is needed on Tasks, but if anything is still not clear to you on this topic, we can continue the conversation here.

Ahh, I cannot add numbers to date-expressions. Thank you very much for clearification and advice!


changed the borken link Velero on Azure with the right link

Fixing Velero on Azure broken link.

@kmoussa : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified the broken-link fix.
@kmoussa Thanks for submitting the fix.


Has package been renamed from dart_nostr to nostr?

Has this package been renamed?
Installation now says nostr: any
What is the diff between nostr package and dart_nostr?
Do they depend on each other, just been renames, which is best to use?

Yes, it is renamed


Inherited placeholders

This is a continuation of #5780
It will have to wait due to the changes that are currently ongoing on 3.5

Would be great to have:

[ ] differentiation of the top level inherit placeholder vs the ones that actually inherit so we can add better tooltips
[ ] show non-editable inherited plugins in the content mode vs showing nothing

Coverage remained the same at 82.826% when pulling 911f44cf8e899233685df1e1a76523d794d20750 on vxsx:feature/inherited-placeholders into 98405e85ac4fa808f5aa875b6d4b24570fb4af3e on divio:develop.

@vxsx bump for merging :)

@FinalAngel this is missing BE

closing this for now


Animation on Scrolling back too

The demo (aka scrollRevealjs.org animates on scroll down, and then when scrolling back up, it animates too! Is that using this same library, and if yes, how?

https://github.com/jlmakes/scrollReveal.js/wiki/Configuration#reset

Just as @mikerockett has referenced, the reset property (set to false by default) controls whether or not revealed elements will reset when scrolled out of view.
This will override the defaults, and reset all animations (as seen on the demo):
var config = {
  reset: true,
}

var sr = new scrollReveal( config );

This will use (or disable) reset for specific elements:

 Foo

 Foo

Thanks. It works.

Hello,
Thanks for your enquiry!
I'm now out of the office until Tuesday 30th June.
For urgent web hosting support, please call 0113 3185277, otherwise I will get back to you on my return.
Warm regards,
James
Lux Digital Ltd
e<EMAIL_ADDRESS>m: 07734 467977
w: www.madebylux.com
t: 0113 318 5277
a: Tower Works, Globe Road, Leeds LS11 5QG


Screenshot shows manager node's IP address instead of worker node's

File: engine/getstarted-voting-app/test-drive.md
On the second screen shot (ie. the result web page), the ip address on the picture is <IP_ADDRESS> which is the worker's ip in this tutorial instead of the manager's ip. Please check and update.

dibs for hackathon

This topic no longer exists. Don't worry, you'll still get the points for the fix, @bdwill.

Points to @bdwill


Proposal: Change how justifications & hypothesis changes are done (not sure this is a good idea)

This is a UI proposal, it doesn't change functionality. Do with it as you will, it's not critical, but maybe you'll find it interesting.
Currently there's a little "P" that toggles display of a justification on the next line. But often I want to see all justifications or none, and having each one on its line wastes a tremendous amount of space when I'm using a larger display.
I proposal instead having a toggle at the top that turns on/off displays of justifications; when on, it displays in the same line the justification or something that indicates it's a hypotheses (maybe HYP). When off, this becomes a tiny minimized column that shows H or P (if it's a justified provable statement) or "-" (if it's supposed to be provable but is not yet justified).  Hovering over it shows a tooltip: "Hypothesis NUMBER" if a hypothesis, the justification if it's justified along with "Press Alt- to generate proof", or "This is not yet proven". You could change a statement between H and P by selecting it and then selecting a new button at the top "H<>P" (this would make the ability to change a statement type more obvious).

Hmm, after using this further, I realize that the "next line" is nice on narrow screens like those on smart phones... and that this system is quite usable on a smart phone. I don't know if my proposal would work so well on a smart phone.

Probably I can implement different behavior depending on a screen width. I will check.

I'm sure you can change how things look depending on the width, since simple CSS can do that.
However, I don't think you want to change too much about behavior - instead, provide multiple mechanisms that all work (if they work at all). I expect some users to use both a smartphone and a big screen (e.g., laptop). If it's possible to do the same action it should work the same way. I may be reading too much into your word "behavior" :-).

More thoughts...
I think it really would be nice to be able to see, on one line, the justification refs and hyp steps. But whether or not the user wants that will vary by person as well as by screen size.
So instead of making that based on width, how about making two on/off in settings, for "show refs in editor" and "show hyp steps in editor"? Then the user can turn each on or off. If on, that extra info will be available on that line. Extra points if you can click on the ref (opening a dynamic tab on it) and the step used (jumping to it).

So instead of making that based on width, how about making two on/off in settings, for "show refs in editor" and "show hyp steps in editor"? Then the user can turn each on or off.

Yes, I think this is a good approach. I actually was going to implement it. But I also include more options to show/hide other UI elements: checkboxes, labels, H/P/G indicators. I am going to place these options in the editor for not to switch to the settings tab.

Extra points if you can click on the ref (opening a dynamic tab on it) and the step used (jumping to it).

In that case long-click to edit and short click to jump?

Yes, I think this is a good approach. I actually was going to implement it. But I also include more options to show/hide other UI elements: checkboxes, labels, H/P/G indicators. I am going to place these options in the editor for not to switch to the settings tab.

Sure!

Extra points if you can click on the ref (opening a dynamic tab on it) and the step used (jumping to it).

In that case long-click to edit and short click to jump?

This is regarding the steps and justification, right? The goal of course is consistency.
Hmm, that sounds right, I guess the rule is: "on a link, normal click always jumps to it, long click might do something else". In that case all hyperlinks (like the step id or ref) to jump to something should be made to look like a hyperlink. That would help discoverability too, if in the explorer the name of the theorem/axiom looked like a hyperlink. By "looks like a hyperlink" I mean "underlined and in blue" or some similar visual indicator.

BTW, your v11 list is ambitious! Can't wait to see it released.

@david-a-wheeler
Currently I am concentrating on implementation of the features you listed as required or highly wanted for the video tutorial. The features in v11 list are those which I estimated as relatively easy to implement (I was in rush, so I could miss some or include something by mistake). The problem is that it is difficult to predict how much time I need to complete everything. I planed to finish the features you listed and then ask you if you want to wait until I am done with everything else in v11 list, or you want to start creating the video tutorial as soon as possible. Since you already noticed this list, could you please review it and let me know if you are ok to wait for everything in it (with undefined due date)? Or you may select only what is valuable for the video tutorial, and everything else will be moved to v12. Another option is to select most wanted features and set up a hard deadline (say 2-3 weeks after I finish the features you've listed for the tutorial) and whatever is ready until then gets published to the latest version and everything else is moved to v12.
It is not required to come up with a decision right now, we may discuss this when I finish the features you've listed for the tutorial.
We also may move this discussion to the tutorial related issue in the guide repo.

Thanks for offering to discuss v11. That is its own issue, so in the hope of making things easier to understand, I created a separate issue to discuss that: https://github.com/expln/metamath-lamp/issues/83

@david-a-wheeler
There is a bug on dev (which I've just noticed) - justifications are shown for hypotheses too. I am going to implement the following  (in v11, because that should be easy):

The content of justification for hypotheses will always be HYP.
If you add a new step and want it to be a hypothesis then you may set its justification to hyp and it will be automatically converted to a hypothesis. So you don't need to use the step type indicator and you may even hide it.

Please let me know if you think this is wrong or you have a better idea.

justifications are shown for hypotheses too. I am going to implement the following (in v11, because that should be easy)

I like that! I'm guessing there will be no ":", so a database with label "HYP" would not be confused with that being an axiom or theorem. Presumably we don't want local labels named HYP.

BTW, I think showing the justifications by default is wise. It certainly makes the tool easler to explain, and even on a smartphone I do want to see them.

I'm guessing there will be no ":", so a database with label "HYP" would not be confused with that being an axiom or theorem.

Yes, : will be used to distinguish these cases visually. However, internally, mm-lamp checks if a step is H or P. If the step is H then mm-lamp doesn't even attempt to interpret its justification.
Also, internally there is no G type, only H and P; G = {type:P, isGoal:true}

Presumably we don't want local labels named HYP.

Currently I don't want to restrict users by this rule. If it is not forbidden by Metamath, then let them do whatever they want ( in the scope of what mm-lamp can do :) )

This is implemented on dev. Here is a brief description of what was changed:

It is possible to select what to show on same line with each step.
Use "main menu" in the editor to open "view options" dialog. This dialog allows to select what to show and what to hide.
If justifications are not shown to the left of statements, then clicking on either green checkmark, or the label or the step type will reveal the justification.
If justifications are shown to the left of statements, then clicking on either green checkmark, or the label or the step type will reveal the visualization.
for hypotheses, a justification is also shown, but it is always HYP.
Setting hyp (case insensitive) as a justification for a provable step will automatically change its type to H.
Setting a justification to anything other than hyp (case insensitive) for a hypothesis step will automatically change its type to P.


Object don't created while using create block

For example if using:
User.create do |user|
  user.name = "test"
  user.email =<EMAIL_ADDRESS>end

It's returns an empty object:
#<User _id: BSON::ObjectId('4eccb6ecb145b16c3e000001')>
In User model keys are defined:
key :name, String, :required => true
key :email, String

MongoMapper doesn't support the block syntax on new/create. Patches are welcome if you'd like to add support for it.


package name not resolved

Maybe I'm just too stupid, but I cannot get PackageCompilerX installed.
(Windows 10, Julia 1.3)
(v1.3) pkg> add PackageCompilerX
  Updating registry at `C:\Users\joach\.julia\registries\General`
  Updating git-repo `https://github.com/JuliaRegistries/General.git`
ERROR: The following package names could not be resolved:
 * PackageCompilerX (not found in project, manifest or registry)
Please specify by known `name=uuid`.

Am I missing something?

Currently not registered so need to do add https://github.com/JuliaComputing/PackageCompilerX.jl

awesome. Thanks.


table name is dynamic alert error

i want dynamic change table name
for example
@Query('select * from bk_info_:id order by num asc')
Future<List> findAllbkInfos(String id);
but alert error
DB Error: 1 "near "?": syntax error"
DB Query: select * from bk_info_?1 order by num asc
What do I need to do？

i want dynamic change table name for example @query('select * from bk_info_:id order by num asc') Future findAllbkInfos(String id);
but alert error DB Error: 1 "near "?": syntax error" DB Query: select * from bk_info_?1 order by num asc What do I need to do？

I think you need to add a space between bk_info_ and :id, if the table name is bk_info_

@query('select * from bk_info_:id order by num asc')
Future findAllbkInfos(String id);
if id = '123'
i hope table name is bk_info_123

@query('select * from bk_info_:id order by num asc') Future findAllbkInfos(String id); if id = '123' i hope table name is bk_info_123

No, floor does not support dynamic table names, as an option, you can use a raw query.


How to run shaka player at custom domain for testing

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
If the question is related to FairPlay, have you read the tutorial?

What version of Shaka Player are you using?
4.6.3
What browser and OS are you using?

Browser: Chrome  124.0.6367.119
OS: Window 11 Pro, 64 bit

Please ask your question
I am developing my app for testing stream url using framework nuxt v2.
Due to security reason, localhost is not allowed to run stream.
In dev mode, stream link can be only played at http://abc.mycompany.com. In which abc.mycompany.com is our custom hostname for localhost, configured in host file:
<IP_ADDRESS> abc.mycompany.com.
I know shaka player require https or localhost to run. But is there any way in this case?
I already tried to run https but no luck: https://abc.mycompany.com.
Hope to here from you soon

Sorry, the requirement to use https or localhost ("secure contexts") comes from the web platform and the browser, not the player.
For specific browsers, you can work around this with command-line flags.  For example, in Chrome, you can use this:

--unsafely-treat-insecure-origin-as-secure
Treat given (insecure) origins as secure origins. Multiple origins can be supplied as a comma-separated list.
Example: --unsafely-treat-insecure-origin-as-secure=http://a.test,http://b.test

There are probably flags available for Firefox testing as well.  Edge and Safari tend not to have flags for these sorts of things.
Does this help?

  To create a new session, use something like --user-data-dir=/path/to/blank-user-data-dir in addition to your other testing flags.

thanks @joeyparrish , it works.
just a small wonder, when i use videojs, this issue not happen. I can play at my custom domain without having to setup --unsafely-treat-insecure-origin-as-secure.
anyway now it works.


Make Galley configuration metadata dynamically loadable

Galley currently loads configuration resource metadata from a hardcoded list. Galley must be re-built and re-started to change per-resource metadata, e.g. group, version, kind. Instead of hardcoding this metadata, Galley can load it from a local file to allow for fine adjustments to Group/Version/Kind.

CRD installation is conditional on presence of Pilot, Security, and Mixer being enabled (see below). Galley's dynamic config metadata may need to be similarly conditional on feature APIs.
https://github.com/istio/istio/blob/3378c01f98d1b5b284b022483ac0cd83f6f3eb0f/install/kubernetes/helm/istio/templates/crds.yaml#L3
https://github.com/istio/istio/blob/3378c01f98d1b5b284b022483ac0cd83f6f3eb0f/install/kubernetes/helm/istio/templates/crds.yaml#L149
https://github.com/istio/istio/blob/3378c01f98d1b5b284b022483ac0cd83f6f3eb0f/install/kubernetes/helm/istio/templates/crds.yaml#L199

Currently, the metadata is an embedded metadata.yaml file. It is relatively straightforward to make this an external config file now.

Given galley is removed I think  this is no longer relevant


Tweak to not squish wide images in story headers

Remove the copied CSS and replace with just object-fit: cover, the image sizing's already taken care of and anything that overflows will automatically be cropped.

We have <0.5% IE users. As this will only have a minor effect on a couple of pages where wider story pictures might be served in the wrong aspect ratio I'll merge. All the pages will still be usable.


1587 add regularizer demo

Fixes #1587.
Description
As mentioned in #1587, the notebook should contain

[x] Formula for bending energy and diffusion,
[x] Demonstration that bending energy is not scale invariant while diffusion is not scale invariant in some cases (maybe display examples of these cases), and
[x] How both losses are made invariant by specifying normalize=True.

Checks

[x] Avoid including large-size files in the PR.
[x] Clean up long text outputs from code cells in the notebook.
[x] For security purposes, please check the contents and remove any sensitive info such as user names and private key.
[ ] Ensure (1) hyperlinks and markdown anchors are working (2) use relative paths for tutorial repo files (3) put figure and graphs in the ./figure folder
[x] Notebook runs automatically ./runner.sh -t <path to .ipynb file>

Hi @ebrahimebrahim, would you mind taking a look at this? I'm also wondering if I should mention your notebook somewhere in here. But anyways let me know what you think :)

Yes, happy to look it over! Can someone add me as a reviewer? I will try to look at it this week.
No need to mention the earlier notebook I think. One thing you could do is to add
Co-authored-by: Ebrahim Ebrahim<EMAIL_ADDRESS>to the body of the commit message that says add regularizer demo
but it is not too important

@kvttt Added my suggestions. It looks great; thank you for putting this together!!
I really like the separation between unequal and equal scaling of images. Everything is very clear and nicely organized.


incorrect power calculation

Hello!
mpmath.power() fails with negative numbers. Initially I expect to have something like -8**(1./3)=-2. In reality there are 3 roots for 1./3 power and ok, let it be some other answer. But why I didn't get exact 1.0 as a real part and exact sqrt(3) as imaginary part?
$ python3
Python 3.8.5 (default, Jan 27 2021, 15:41:15)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import mpmath
mpmath.mp.dps=50
mpmath.power(-8.0,1./3)
mpc(real='1.0000000000000000622086928455818618679774324989807018', imag='1.7320508075688771687514964885913910681346917057935831')
mpmath.sqrt(3)
mpf('1.732050807568877293527446341505872366942805253810381')

@metelev-sv, it seems, mpmath uses principal value of exp(y*log(x)) for power(x, y), just like Mathematica does:
$ wolframscript
Wolfram Language 12.2.0 Engine for Linux x86 (64-bit)
Copyright 1988-2021 Wolfram Research, Inc.

In[1]:= Power[-8, 1/3]

              1/3
Out[1]= 2 (-1)

In[2]:= ComplexExpand[%1]

Out[2]= 1 + I Sqrt[3]

In[3]:= %1 // N

Out[3]= 1. + 1.73205 I

I doubt there is something incorrect.  Yet, maybe it's a documentation bug.

BTW, you can get an "expected" answer with
>>> mpmath.root(-8, 3, 1)
mpf('-2.0')

Thank you for answer!
Principal value should have real part exact 1., but it contains some digits after 16 position, though mp.dps=50. And the same for imaginary part, it should be exact sqrt(3) and it is equal for sqrt(3) only for first 15 digits.
By the way, mathematica has similar problem. It gives exact 1. for real part, but not exact Sqrt[3] for imaginary part. I did write to them also.

The problem is you are using 1./3, which creates the Python float 0.3333333333333333. This only approximates 1/3 to 15 digits, the number of digits of a Python machine float. If you want more digits than that, you have to use a function that allows mpmath to see the exact 1/3 when it evaluates, such as root.
This is a general gotcha with mpmath if you are working with dps higher than the default 15. You have to avoid implicitly computing things with Python floats, which always round to 15 digits.

Yeah, or could use mpmath's rationals (or builtin Fraction's), for example:
>>> import mpmath
>>> mpmath.mp.dps = 50
>>> mpmath.root(-8, 3, 0)
mpc(real='1.0', imag='1.7320508075688772935274463415058723669428052538103806')
>>> mpmath.power(-8, mpmath.mp.mpq(1, 3))
mpc(real='1.0', imag='1.7320508075688772935274463415058723669428052538103783')

c.f. Mathematica:
Wolfram Language 12.2.0 Engine for Linux x86 (64-bit)
Copyright 1988-2021 Wolfram Research, Inc.

In[1]:= N[Power[-8, 1/3], 50]

Out[1]= 1.0000000000000000000000000000000000000000000000000 +
1.7320508075688772935274463415058723669428052538104 I

It gives exact 1. for real part, but not exact Sqrt[3] for imaginary part. I did write to them also.

Hmm, so far, I can't see something wrong with the last answer.  It seems to be correct for 50 digits (up to 3810).

btw, float's issue seems to be documented: https://mpmath.org/doc/current/basics.html#providing-correct-input
You can also create exponent from the string:
>>> mpmath.power(-8, mpmath.mpf('1/3'))
mpc(real='1.0', imag='1.7320508075688772935274463415058723669428052538103783')

Thank you for answers!
In mathematica I use WolframAlpha, call
SetPrecision[Exp[Log[-8]/3.], 50] and get
1.0000000000000000000000000000000000000000000000000 + 1.7320508075688769711319991984055377542972564697266 I
which is differ from your answer. Now I understand, that it is because of -8 without point.

Ok, then #588 should fix this issue.  Let me know if you do think that https://mpmath.org/doc/current/basics.html#providing-correct-input should be rewritten/expanded.


Add imu support and vesc udev enumeration tools (rebase upstream ros2)

added tool to enumerate vescs based on their uuid (/dev/vesc/XXXX-XXXX-XXXX)
added support to read imu data

@anscipione The copyright check failed on at least one of your files. Can you please run colcon test --packages-select vesc && colcon test-result --verbose and fix the issues provided?

the checks do not pass because the code on which I have based the rebase lacks the copyright.
in particular it is missing on the new launch file.  it is not code written by me so I would not want to put an incorrect copyright.  can you tell me what kind of copyright to put

Closing as the branch for this PR no longer exists. @anscipione The formatting issues on the ros2 branch have been corrected. Please provide a new PR and I'll make sure to get it in this time.

Ok i'lo asap


ensure *nix platforms add an initial / rooted drive

This is certainly an edge case but I am working in a docker container that has no / mount point:
[181][default:/src:0]# cat /proc/mounts
tmpfs /dev tmpfs rw,nosuid,mode=755 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /run tmpfs rw,relatime 0 0
tmpfs /var/run/docker.sock tmpfs rw,nodev,relatime,size=201160k,mode=755 0 0
//<IP_ADDRESS>/C /src cifs rw,relatime,vers=3.02,sec=ntlmssp,cache=strict,username=matt,domain=ULTRAWROCK,uid=0,noforceuid,gid=0,noforcegid,addr=<IP_ADDRESS>,file_mode=0755,dir_mode=0755,iocharset=utf8,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=1048576,wsize=1048576,actimeo=1 0 0

This results in an "automounted" PS Drive named / but with a Root of /dev which causes Get-Location, $pwd and auto module loading to fail.
This ensures that a / dirive is added during the file system provider drive initialization and rooted to /.

To further clarify this, without this change, a PSDrive is still created for / but that happens later in AutoMountFileSystemDrive. However the root is not adjusted so in the above case it points to /dev but in any case it would point to the first mount in proc/mounts and on *nix, VolumeSeparatedByColon is not set to false which results in malformed path resolution and a Get-Location looking like /:/.

Sure thing @vors. Done!

Looks like the Travis CI queue filled up. I canceled some irrelevant jobs, this should run soon.


fix: let custom icons override builtins

fixes #6

This will cause another issue, Consider this situation:
builtinIcons = {
   'vite': 'vscode-icons:file-type-vite',
}

customIcons = {
  'vitepress': '<svg>...<svg>'
}

mergedIcons = {
   'vite': 'vscode-icons:file-type-vite',
   'vitepress': '<svg>...<svg>'
}

Because the icon matching logic：
https://github.com/yuyinws/vitepress-plugin-group-icons/blob/main/src/codegen.ts#L65
In this case the vitepress will always match the vite icon.
I think we should find a better solution about the icon matching logic.


Feature Request: Custom Breakpoints For Extensions

Hi:
I am currently exploring the options of using VS Code to build a debugger for an actor-based language.
One of the things that are key for the project are custom and often complex types of breakpoints.
In our current prototype, we support for instance the following types of breakpoints:

On the asynchronous message send operator, we can set a sender side or a receiver side breakpoint.

On method definitions, we can set breakpoints that are only triggered when that method is activated via an asynchronous message (but not when it is called synchronously).
Since this is probably far from a common requirement, I would also be more than happy with some recommendations of how I could prototype this myself.
While we have popovers in our prototype, the context menu might do (however, the 'when' clause in package.json does not seem to be taking callbacks for custom predicates?). A custom indicator/handle to interact with the breakpoint might still be nice (I think the decorator-sample comes with code that I can probably adapt).
And when the breakpoint is set, it needs to be communicated to the process that's debugged, but I'll probably be able to extend the debugging protocol to my needs.
So, I think, it should be possible for me to prototype something, but I'd be very grateful for guidelines and perhaps pointers to the most relevant elements that I should be aware of.
Thanks
Stefan

One element for the custom breakpoints that would be very useful is to have support for context menus that are specific to a token for instance: https://github.com/Microsoft/vscode/pull/11405


Added script for stopping Cassandra and Cqlsh for linux

We have added script for stopping CQLSH and Cassandra for linux.

Added the patch for the same here
https://issues.apache.org/jira/browse/CASSANDRA-13901


Bug: Icons are not displaying properly.

icon name does not seem to match icon display.

Duplicate. issue already addressed in PR https://github.com/SAP/techne/pull/1012


consider vite instead of tsc for packages?

ref #20, this will make working with vitest unit tests easier

using Vite for apps, moved back to TypeScript ESM for libraries


TF 2.13.0-rc0 fails to compile on Ubuntu 22.04/MacOS

Click to expand!
Issue Type
Build/Install
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
2.13.0-rc0
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 22.04 / MacOS 13.3
Mobile device
No response
Python version
3.10.6
Bazel version
5.3.0
GCC/Compiler version
gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
CUDA/cuDNN version
11.8
GPU model and memory
Quadro RTX 6000
Current Behaviour?
When compiling TF 2.13.0-rc0 from source with default bazel parameters (see attached log) compilation fails.
Standalone code to reproduce the issue
Use version of TF 2.13.0-rc0. Follow the default bazel ./configure parameters. The issues happens regardless of compilation with or without CUDA.

Please input the desired Python library path to use.  Default is [/usr/lib/python3/dist-packages]

Do you wish to build TensorFlow with ROCm support? [y/N]:
No ROCm support will be enabled for TensorFlow.

Do you wish to build TensorFlow with CUDA support? [y/N]:
No CUDA support will be enabled for TensorFlow.

Do you wish to download a fresh release of clang? (Experimental) [y/N]:
Clang will not be downloaded.

Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -Wno-sign-compare]: -Wno-sign-compare

Would you like to interactively configure ./WORKSPACE for Android builds? [y/N]:
Not configuring the WORKSPACE for Android builds.

Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
	--config=mkl         	# Build with MKL support.
	--config=mkl_aarch64 	# Build with oneDNN and Compute Library for the Arm Architecture (ACL).
	--config=monolithic  	# Config for mostly static monolithic build.
	--config=numa        	# Build with NUMA support.
	--config=dynamic_kernels	# (Experimental) Build kernels into separate shared objects.
	--config=v1          	# Build with TensorFlow 1 API instead of TF 2 API.
Preconfigured Bazel build configs to DISABLE default on features:
	--config=nogcp       	# Disable GCP support.
	--config=nonccl      	# Disable NVIDIA NCCL support.
Configuration finished

Relevant log output
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=100
INFO: Reading rc options for 'build' from /home/nicola/Software/tensorflow/gpu/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/nicola/Software/tensorflow/gpu/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --define tsl_protobuf_header_only=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library --experimental_link_static_libraries_once=false --incompatible_enforce_config_setting_visibility
INFO: Reading rc options for 'build' from /home/nicola/Software/tensorflow/gpu/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/usr/bin/python3 --action_env PYTHON_LIB_PATH=/usr/lib/python3/dist-packages --python_path=/usr/bin/python3
INFO: Reading rc options for 'build' from /home/nicola/Software/tensorflow/gpu/tensorflow/.bazelrc:
  'build' options: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/ir,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_jitrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/tfrt/eager,tensorflow/core/tfrt/eager/backends/cpu,tensorflow/core/tfrt/eager/backends/gpu,tensorflow/core/tfrt/eager/core_runtime,tensorflow/core/tfrt/eager/cpp_tests/core_runtime,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/graph_executor,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils,tensorflow/core/tfrt/utils/debug
INFO: Found applicable config definition build:short_logs in file /home/nicola/Software/tensorflow/gpu/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/nicola/Software/tensorflow/gpu/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:opt in file /home/nicola/Software/tensorflow/gpu/tensorflow/.tf_configure.bazelrc: --copt=-Wno-sign-compare --host_copt=-Wno-sign-compare
INFO: Found applicable config definition build:linux in file /home/nicola/Software/tensorflow/gpu/tensorflow/.bazelrc: --define=build_with_onednn_v2=true --host_copt=-w --copt=-Wno-all --copt=-Wno-extra --copt=-Wno-deprecated --copt=-Wno-deprecated-declarations --copt=-Wno-ignored-attributes --copt=-Wno-array-bounds --copt=-Wunused-result --copt=-Werror=unused-result --copt=-Wswitch --copt=-Werror=switch --copt=-Wno-error=unused-but-set-variable --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++17 --host_cxxopt=-std=c++17 --config=dynamic_kernels --experimental_guard_against_concurrent_changes
INFO: Found applicable config definition build:dynamic_kernels in file /home/nicola/Software/tensorflow/gpu/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/7d879c8b161085a4374ea481b93a52adb19c0529.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/llvm/llvm-project/archive/dc275fd03254d67d29cc70a5a0569acf24d2280d.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/benchmark/archive/f7547e29ccaed7b64ef4f7495ecfff1c9f6f3d03.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://mirror.bazel.build/github.com/bazelbuild/rules_cc/archive/081771d4a0e9d7d3aa0eed2ef389fa4700dfb23e.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/flatbuffers/archive/v23.1.21.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/abseil/abseil-cpp/archive/b971ac5250ea8de900eae9f95e06548d14cd95fe.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/glennrp/libpng/archive/v1.6.39.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/XNNPACK/archive/b9d4073a6913891ce9cbd8965c8d506075d2a45a.zip failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/openxla/stablehlo/archive/43d81c6883ade82052920bd367c61f9e52f09954.zip failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/boringssl/archive/c00d7ca810e93780bd0c8ee4eea28f4f2ea4bcdc.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/pybind/pybind11_abseil/archive/2c4932ed6f6204f1656e245838f4f5eae69d2e29.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
ERROR: /home/nicola/.cache/bazel/_bazel_nicola/c53ed0be17816f9e0970b1ba234e403c/external/local_config_python/BUILD:78:8: in outs attribute of genrule rule @local_config_python//:python_include: Genrules without outputs don't make sense
ERROR: /home/nicola/.cache/bazel/_bazel_nicola/c53ed0be17816f9e0970b1ba234e403c/external/local_config_python/BUILD:78:8: Analysis of target '@local_config_python//:python_include' failed
INFO: Repository cython instantiated at:
  /home/nicola/Software/tensorflow/gpu/tensorflow/WORKSPACE:15:14: in <toplevel>
  /home/nicola/Software/tensorflow/gpu/tensorflow/tensorflow/workspace2.bzl:972:21: in workspace
  /home/nicola/Software/tensorflow/gpu/tensorflow/tensorflow/workspace2.bzl:706:20: in _tf_repositories
  /home/nicola/Software/tensorflow/gpu/tensorflow/third_party/repo.bzl:136:21: in tf_http_archive
Repository rule _tf_http_archive defined at:
  /home/nicola/Software/tensorflow/gpu/tensorflow/third_party/repo.bzl:89:35: in <toplevel>
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted:
INFO: Elapsed time: 87.858s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (389 packages loaded, 6975 targets configured)
    Fetching https://storage.googleapis.com/.../github.com/cython/cython/archive/3.0.0a11.tar.gz

Log when compiling using CUDA:
mochi_O3.txt

So far the issue is limited to linux. MacOS 13.3 with python 3.11 seems to be compiling just fine.

A similar issue is present for MacOS 13.3 using python 3.10. Log attached.
MacOS.txt

Trying to reproduce in Ubuntu 22.04 with all of the above conditions.  I'll let you know if I'm able to.

I was not able to reproduce the error, my build succeeded.  What is your system arch?

@SuryanarayanaY,
Notes: I tried to replicate the issue using tf v2.13.0-rc0 and CUDA 12.0 and was facing the below error when trying to configure the setup using ./configure.

In both cases it's x86_64.
The issue here seem to point to a configuration issue:
ERROR:
/home/nicola/.cache/bazel/_bazel_nicola/c53ed0be17816f9e0970b1ba234e403c/external/local_config_python/BUILD:78:8:
in outs attribute of genrule rule @local_config_python//:python_include:
Genrules without outputs don't make sense
ERROR:
/home/nicola/.cache/bazel/_bazel_nicola/c53ed0be17816f9e0970b1ba234e403c/external/local_config_python/BUILD:78:8:
Analysis of target @.***_config_python//:python_include' failed
INFO: Repository cython instantiated at:
  /home/nicola/Software/tensorflow/gpu/tensorflow/WORKSPACE:15:14: in

/home/nicola/Software/tensorflow/gpu/tensorflow/tensorflow/workspace2.bzl:972:21:
in workspace
/home/nicola/Software/tensorflow/gpu/tensorflow/tensorflow/workspace2.bzl:706:20:
in _tf_repositories
/home/nicola/Software/tensorflow/gpu/tensorflow/third_party/repo.bzl:136:21:
in tf_http_archive
Repository rule _tf_http_archive defined at:
/home/nicola/Software/tensorflow/gpu/tensorflow/third_party/repo.bzl:89:35:
in
ERROR: Analysis of target
'//tensorflow/tools/pip_package:build_pip_package' failed; build aborted:
INFO: Elapsed time: 88.076s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (388 packages loaded, 6429
targets configured)
On 5/16/23 9:11 AM, Yeison Rodriguez wrote:

I was not able to reproduce the error, my build succeeded. What is
your system arch?
—
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/60581#issuecomment-1549112759,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAIY7Y24PVXJBBXVXRPIVDXGMSATANCNFSM6AAAAAAX7IC5YE.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi, Thanks for reporting the bug, Since we are trying to figure out if this is regression issue.
Could you please help us with the below analysis and let us know if you see change in behavior.
Please test against the 2.12.0 version with below configurations.
GPU

Version
Python version
Compiler
Build tools
cuDNN
CUDA

tensorflow-2.12.0
3.8-3.11
GCC 9.3.1
Bazel 5.3.0
8.6
11.8

On MacOS, the error is related but slightly different:
ERROR: /Users/feranick/Desktop/tensorflow/tensorflow/BUILD:1134:21: declared output 'tensorflow/libtensorflow_framework.2.dylib' was not created by genrule. This is probably because the genrule actually didn't create this output, or because the output was a directory and the genrule was run remotely (note that only the contents of declared file outputs are copied from genrules run remotely)
ERROR: /Users/feranick/Desktop/tensorflow/tensorflow/BUILD:1134:21: Executing genrule //tensorflow:libtensorflow_framework.2.dylib_sym failed: not all outputs were created or valid
realpath: illegal option -- -
usage: realpath [-q] [path ...]
Target //tensorflow/tools/pip_package:build_pip_package failed to build

Hi, Thanks for reporting the bug, Since we are trying to figure out if this is regression issue. Could you please help us with the below analysis and let us know if you see change in behavior.
Please test against the 2.12.0 version with below configurations.
GPU
Version	Python version	Compiler	Build tools	cuDNN	CUDA
tensorflow-2.12.0	3.8-3.11	GCC 9.3.1	Bazel 5.3.0	8.6	11.8

On Ubuntu 22.04. TF 2.12.0 fails just as well (using the parameters above). Weirdly enough, it compiled just fine when released. I am not sure what changed, suggestions welcome.
I am testing MacOS, will report shortly.

I'm trying to reproduce in Ubuntu 22.04 with all of the above conditions. I'll let you know if I'm able to.

If you are successful, can you please list your system configuration (including your list of python packages and version)?

I was not able to reproduce it in a fresh docker environment.

On MacOS 13.3.1, TF 2.12.0 compiles just fine.
tensorflow-2.12.0
python: 3.10.11
Apple clang version 14.0.3 (clang-14<IP_ADDRESS>.1)
Bazel 5.3.0

[UPDATE] I finally figured out the issue with Ubuntu. Compilation fails when Cython is newer than 0.29.28 is installed (currently the latest is 0.29.32). Cython needs to be v0.29.28, which is also that provided by Ubuntu via apt. Maybe this should be listed  in the recommended list of required software.
I am still trying to identifying the issue with MacOS, which seems to be  related (and yet compilation fails also with Cytin 0.29.28).

For Ubuntu the issue is not a duplicate, but again, documentation needs to be updated with information on the correct version number for Cython.

Action is on Google here. I suggested a solution above.

@feranick ,
From Tf2.13 onwards TF uses Clang 16.0.0 as compiler instead of GCC as per updated documentation. I will also test the build with Clang and update you results.

Hi @feranick , Could you please try to compile it in the 2.13.0 or 2.13.0-rc2 and let us know if that works for you. Thanks!

Yes, it compiles fine with 2.13.0. But that is not because of this specific release (compared to earlier rcs), but because, as mentioned above the use of the correct libraries. The issue is in the lack of any documentation of what version of cython is needed for compilation. Such info should be listed in the required libraries.

Hi,
Would it be possible for you to create a PR with the specific version of cython which worked for you.Thanks!

As described above there is no change needed in TF, just making sure that Cython is in the correct version:
Compilation fails when Cython is newer than 0.29.28 is installed (currently the latest is 0.29.32). Cython needs to be v0.29.28, which is also that provided by Ubuntu via apt.
I am not sure what I should push as PR. Rather, this should be listed within the set of requirements for compilation...

Don't use clang when asked. Should work.
On 9/12/23 9:43 AM, cuchio wrote:

I have also not been able to build on lubuntu 22.04.3 using docker.io.
I follow the instructions on
https://www.tensorflow.org/install/source#linux
The following appears to work OK
docker pull tensorflow/tensorflow:devel
docker run -it -w /tensorflow_src -v $PWD:/mnt -e HOST_PERMS="$(id
-u):$(id -g)"
tensorflow/tensorflow:devel bash
git pull
However, when running ./configure it fails to see the clang directories
@.***:/tensorflow_src# ./configure
You have bazel 6.1.0 installed.
Please specify the location of python. [Default is /usr/bin/python3]:
Found possible Python library paths:
/usr/lib/python3/dist-packages
/usr/local/lib/python3.8/dist-packages
Please input the desired Python library path to use. Default is
[/usr/lib/python3/dist-packages]
Do you wish to build TensorFlow with ROCm support? [y/N]:
No ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]:
No CUDA support will be enabled for TensorFlow.
Do you want to use Clang to build TensorFlow? [Y/n]: Y
Clang will be used to compile TensorFlow.
Please specify the path to clang executable. [Default is ]:
If I try to compile not using clang it does download and start to
compile but fails at many points.
Bazel command used is either:
bazel build --config=opt --config=v2
//tensorflow/tools/pip_package:build_pip_package
or
bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package
When it starts is tells me python 3.9 chosen.
I am compiling this on an old pre avx system.
—
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/60581#issuecomment-1715753213,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAIY76YGMCL6OPMGTQL6HLX2BRHLANCNFSM6AAAAAAX7IC5YE.
You are receiving this because you were mentioned.Message ID:
@.***>

--------------uhVVUHL7PrMAlHCnksw33Bcd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

    Don't use clang when asked. Should work.

On 9/12/23 9:43 AM, cuchio wrote:

I have also not been able to build on lubuntu
    22.04.3 using docker.io.

I follow the instructions on https://www.tensorflow.org/install/source#linux

The following appears to work OK

docker pull tensorflow/tensorflow:devel

    docker run -it -w /tensorflow_src -v <math-renderer class="js-inline-math" style="display: inline" data-static-url="https://github.githubassets.com/static" data-run-id="b0d76be046d4ad734683225467a7b462">$PWD:/mnt -e
      HOST_PERMS="$</math-renderer>(id -u):$(id -g)"

    tensorflow/tensorflow:devel bash

git pull

However, when running ./configure it fails to see
    the clang directories

  <p ***@***.***:/tensorflow_src# ./configure

    You have bazel 6.1.0 installed.

    Please specify the location of python. [Default is
    /usr/bin/python3]:

Found possible Python library paths:

    /usr/lib/python3/dist-packages

    /usr/local/lib/python3.8/dist-packages

    Please input the desired Python library path to use. Default is
    [/usr/lib/python3/dist-packages]

Do you wish to build TensorFlow with ROCm support?
    [y/N]:

    No ROCm support will be enabled for TensorFlow.

Do you wish to build TensorFlow with CUDA support?
    [y/N]:

    No CUDA support will be enabled for TensorFlow.

Do you want to use Clang to build TensorFlow? [Y/n]:
    Y

    Clang will be used to compile TensorFlow.

Please specify the path to clang executable.
    [Default is ]:

If I try to compile not using clang it does download
    and start to compile but fails at many points.

Bazel command used is either:

bazel build --config=opt --config=v2
    //tensorflow/tools/pip_package:build_pip_package

or

bazel build --config=opt
    //tensorflow/tools/pip_package:build_pip_package

When it starts is tells me python 3.9 chosen.

I am compiling this on an old pre avx system.

—

    Reply to this email directly, view it on GitHub, or unsubscribe.

    You are receiving this because you were mentioned.Message
      ID: <tensorflow/tensorflow/issues/60581/1715753213@github.com>


0.4.1 has breaking changes

0.4.1 is a patch release, but it includes the breaking changes from #66. This has caused Quicksilver and Tetra to stop building for new projects without a lock file.
Could this release be yanked?
Related issue: https://github.com/ryanisaacg/golem/issues/32

Oops, sorry about that! 0.4.1 is yanked now.

Thank you for the quick fix :)


Multiple LG AC units only shows 1 unit inside homekit

LG Air Conditioner Model
Please provide your A/C model here. If the unit successfully paired to Homekit, please also include the "Model" listed in the accessory's settings.
LW1517IVSM
LP1419IVSM
The LW1517IVSM shows up inside homekit, perhaps coincidentally I set that one up first and it is the first one listed inside the ThinQ app. The model number inside homekit is: WIN_056905_WW
Describe the bug
I have two LG ac units inside thinq, only one shows up inside homekit
Symptom check

Does your unit appear in the Home app? Yes/No - Both, only one of the two is visible
Is the current on/off state, temperature, and mode being reported? Yes/No - Yes for the one that is available
Does your unit respond to the controls? Yes/No - Yes for the one that is available

Hi @SausCode -- Could you restart Homebridge and check the Homebridge logs to see if there's a note about one of them not being supported?

Hi @sman591, thanks for the reply.
[LgThinqAirConditioner] "Portable" (model POT_056905_WW) uses the thinq1 platform, which is not supported. Please see https://github.com/sman591/homebridge-lg-thinq-ac/issues/4 for updates.
Sorry for the noise, new to homebridge and HOOBS and didn't realize there was output I could actually see.

Also, perhaps a separate issue is more appropriate, but seeing a good amount of spam in the logs with the functioning A/C:
...
10/2/2020, 1:57:45 PM [LgThinqAirConditioner] TargetHeaterCoolerStateCharacteristic: Error parsing state Error: Unsupported API value: 8
10/2/2020, 1:58:45 PM [LgThinqAirConditioner] TargetHeaterCoolerStateCharacteristic: Error parsing state Error: Unsupported API value: 8
...

Also, perhaps a separate issue is more appropriate, but seeing a good amount of spam in the logs with the functioning A/C:
...
10/2/2020, 1:57:45 PM [LgThinqAirConditioner] TargetHeaterCoolerStateCharacteristic: Error parsing state Error: Unsupported API value: 8
10/2/2020, 1:58:45 PM [LgThinqAirConditioner] TargetHeaterCoolerStateCharacteristic: Error parsing state Error: Unsupported API value: 8
...

I think this is due to the A/C being on Energy Saver Mode, with it off I no longer see the messages in the logs.

Gotcha! Yeah looks like one of them isn't supported right now. #4 will be updated once support is added.
As for the energy saver mode -- this is a known bug that I believe should have a fix available later with a toggle for this support


alembic: wrongly naming the foreign key constraint fk_transaction_accounts_user_id

Problem:
The alembic recipe 9848d0149abd_create_accounts_tables.py creates a foreign key named fk_transaction_accounts_user_id  between the SQLAlchemy-Continuum's transaction table and the invenio-accounts'  accounts_user table.
The problem is that

SQLAlchemy-Continuum does not name the corresponding foreign key constraint in its model.
invenio-db has a recipe 35c1075e6360_force_naming_convention.py enforcing a naming convention and renaming forcefully any constraint.
the recipe 9848d0149abd_create_accounts_tables.py does not depend on recipe 35c1075e6360_force_naming_convention.py but on a previous recipe.

Thus 9848d0149abd_create_accounts_tables.py and 35c1075e6360_force_naming_convention.py run in random order and force either the foreign key constraint name fk_transaction_accounts_user_id or fk_transaction_user_id_accounts_user (as generated by the naming convention). Thus It is not possible to know which name the constraint will have after running alembic upgrade.
Solution.
We should not name the constraint in 9848d0149abd_create_accounts_tables.py. That way the resulting name will always be the one from the naming convention, i.e. fk_transaction_user_id_accounts_user, once the recipe 35c1075e6360_force_naming_convention.py has ran. However it also means that as long as 35c1075e6360_force_naming_convention.py is not called the name can vary. This should not be a problem as the module is still in beta and alembic upgrades are not yet officially supported.
cc: @lnielsen, @egabancho, @tiborsimko, @remileduc, @PXke, @kaplun

cc @jmartinm

Note: for B2SHARE we are currently working on having our own upgrade scripts doing all the hacks needed like renaming + using alembic. We are planning a presentation on how we proceed.

cc @dinosk


Notification - copy address on multiple shares

....should (be renamed? and) bring the app to foreground instead of putting the first address in clipboard.
1.6 self build

That's a good point.. not sure how to handle this cleanly. Perhaps a popup window prompting which link to copy? I'll need to research what's possible.

Yes or just plain show the app...

Tapping the body of the notification itself will already open the app

I know, then you could just remove the copy button and let the user figureit oute


Fix conversion warnings

NuttX and artik053 build - compiling with strict Werror=conversion - fail when jerry-debugger option is enabled.
This patch based on #2007, because most of them are fixed earlier within that PR, but it was closed before the land.
Credit: Piotr Marcinkiewicz<EMAIL_ADDRESS>JerryScript-DCO-1.0-Signed-off-by: Robert Sipka<EMAIL_ADDRESS>

Good point, I've updated it accordingly, thanks.

@LaszloLango , @zherczeg  : Thanks for the review, I've updated the PR.

LGTM


Make it easy to return something else from a cascade macro

Looking at the method chaining example from basic_example.rs:
let method_chain_example = cascade! {
    ch: Chain::blank();
    ..add(5).add(6).add(7);
    | let ch = ();
  };

| let ch = (); is ugly and unintuitive. Instead, if the last expression has no semicolon, we should simply return that value instead of the value being cascaded. For example:
cascade! {
  ch: Chain::blank();
  ..add(5).add(6).add(7);
  ()
}

I think you might be misunderstanding the change. Usually, the value returned in a block expression is the last expression in the block. But right now, that throws an error in cascade. All this change does is allow an expression at the end of the cascade, which acts as the return value. It makes the cascade macro more closely represent block syntax. Previously, you would have to shadow the variable (re-declare the named value being cascaded as something else), which isn't intuitive.
Here's another example of where this might become useful (note: this takes into account the other changes I plan on making):
fn main() {
  // Run application
  cascade! {
    Application::new();
    ..setup(Window::new(600,800));
    loop {
      ..tick();
    }
    ()
  }
}

Ah, you're completely right!


fix: improved exception handling

…kers

Codecov Report

Merging #70 (b23f38f) into master (4508e9c) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master      #70      +/-   ##
============================================
+ Coverage     81.22%   81.28%   +0.06%
- Complexity      286      287       +1
============================================
  Files            53       53
  Lines           932      935       +3
  Branches         94       95       +1
============================================
+ Hits            757      760       +3
  Misses          143      143
  Partials         32       32

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/com/gojek/beast/worker/Worker.java
100.00% <100.00%> (ø)
8.00 <1.00> (+1.00)

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 4508e9c...b23f38f. Read the comment docs.


migrate bank account info to Zipmark

Looks like we're going to go with Zipmark for ACH: #3491. This ticket is for migrating bank account info.
To: Balanced
Cc: Zipmark

Well, it looks like Gratipay is going to be one of the last ones out the door. After trying to pull off our own ACH partnership with a bank, we're now turning to plan B (discovered last week): Zipmark. The Zipmark team is copied here. Can we please start the process of migrating Gratipay's users' bank account info to them? Let me know what you need from me. Thanks! :-)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/20487257-migrate-bank-account-info-to-zipmark?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Private convo in Slack. Upshot:

other point on the migration file is we need you to supplement some data customer_name,customer_type,tax_id,street,street2,city,state,zip_code,contact_first_name,contact_last_name,contact_email
so, if you can provide that w/ the customer_id, ill merge the two data sets for import
customer_type can be either 'organization', or 'individual'

We can complete the migration without name and address, though we'll need to collect that info (either ourselves or with a Zipmark iframe) before we can process payments. However, we need to collect tax id numbers (cf. https://github.com/gratipay/gratipay.com/issues/3289#issuecomment-107100341) before we can complete the migration, so we're blocking on https://github.com/gratipay/gratipay.com/issues/3289 here.
We

We can probably pull some name/address info out of Balanced.

tax ID and email are necessary

We do require emails for team owners, so we're covered there.

To: Zipmark

Our best option may be to scrap the Balanced migration data and sign up all users from scratch (we only have 16 users that we've already onboarded on the new Gratipay w/ bank payouts). Can we schedule a call or chat to discuss what that would look like?

How about tomorrow (Thursday) at 11am or 2pm?
h/t @kaguillera @dmk246

#3491 isn't happening, closing.


Add  formatTimestamp64

Add  formatTimestamp64

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Add formatTimestamp64

Thanks for the pull request. It seems you're trying to address your issue but the solution is not generic. For example: DateTime64 supports nano seconds but you're using yyyy-MM-dd HH:mm:ss.SSS. Moreover, it's probably better to merge the two PRs into.
Lastly, I hope you understand that ru.yandex is deprecated and will be removed in 0.4.0. You probably should try the new JDBC driver com.clickhouse.jdbc.ClickHouseDriver which supports both time zone and DateTime64.

Got it. I'll go down and look into it


People listing should show first start date for a given role

Leah should have collaborator listed as 2012 and not 2017

Related to https://github.com/jonfroehlich/makeabilitylabwebsite/issues/688. Should be fixed now (though needs testing).


get_transaction_result() failing while parsing storefrontv2 events

get_transaction_result() function in client.py failing if the transaction is liting nft on storefrontv2 ,
It is observe that, "type" in the events must be string , however listingAvailable event has a some "type" field as dict and it is getting failed to parse.

adding these lines
if type(obj[c.typeKey])!=str or not obj[c.typeKey]:         return obj
in flow_py_sdk/cadence/decode.py in decode function can solve this problem


MWPW-137805 - Update samplerum.js

samplerum.js updated from the latest version
Resolves: MWPW-137805
Test URLs:

Before: https://main--milo--joaquinrivero.hlx.page/?martech=off
After: https://mwpw-137805--milo--joaquinrivero.hlx.page/?martech=off

Adressed with https://github.com/adobecom/milo/pull/1465