desktop ruined

So my desktop is now showing the users/Public desktop?? How can I revert this to the old desktop for MY account which is location in users/callu/OneDrive/Desktop

The script doesn't provide feature to show Public desktop. What functions did you run? Also did you uninstall OneDrive?

https://www.reddit.com/r/PowerShell/comments/go2n5v/powershell_script_setup_windows_10/g2cutiu/
// closed. 👍


Optimize MeshRuleAddressListenerInterceptor code#8151

What is the purpose of the change
see #8151
Brief changelog
Change ConcurrentHashMap to org.apache.dubbo.common.utils.ConcurrentHashSet
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[X] Each commit in the pull request should have a meaningful subject line and body.
[X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[X] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[X] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8152 (6efb708) into 3.0 (c263172) will decrease coverage by 0.21%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                3.0    #8152      +/-   ##
============================================
- Coverage     61.74%   61.52%   -0.22%
- Complexity      312      313       +1
============================================
  Files          1073     1073
  Lines         45119    45118       -1
  Branches       6778     6757      -21
============================================
- Hits          27857    27761      -96
- Misses        14184    14260      +76
- Partials       3078     3097      +19

Impacted Files
Coverage Δ

...mesh/route/MeshRuleAddressListenerInterceptor.java
80.00% <100.00%> (-1.82%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
37.50% <0.00%> (-37.50%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0.00%> (-20.69%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
46.15% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

.../remoting/transport/netty4/NettyServerHandler.java
56.81% <0.00%> (-13.64%)
:arrow_down:

.../remoting/transport/netty4/NettyClientHandler.java
57.62% <0.00%> (-10.17%)
:arrow_down:

.../apache/dubbo/remoting/transport/AbstractPeer.java
63.04% <0.00%> (-6.53%)
:arrow_down:

...pache/dubbo/remoting/transport/AbstractServer.java
57.14% <0.00%> (-5.72%)
:arrow_down:

.../org/apache/dubbo/remoting/ExecutionException.java
15.78% <0.00%> (-5.27%)
:arrow_down:

... and 27 more

Continue to review full report at Codecov.

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


Precompiled script plugin named build.gradle.kts without package name causes NoSuchMethodError

If I have a precompiled script, let's say build.gradle.kts, in the root source folder then I get problems
Expected Behavior
It should compile fine
Current Behavior
It fires

'void Build_gradle.(org.gradle.plugin.use.PluginDependenciesSpec)'

Context
Steps to Reproduce
I wanted to start writing some precompiled plugin for lwjgl, I started easy with the following:
this was my buildSrc/build.gradle.kts
plugins {
    `kotlin-dsl`
}
repositories {
    jcenter()
}

and this buildSrc/src/main/kotlin/lwjgl/build.gradle.kts (just a sketch)
plugins {
    `java-library`
}
val ciao = 3

It turned out that adding
package lwjgl fixed the problem, however I was recommended on the gradle slack to open an issue here to investigate further if this is a limitation or a bug
Your Environment
Gradle 6.6
Windows 10 Pro N, 20H2

I can confirm this happening on 6.8 too

I can confirm this happening on 6.8 too

Relates to

#11952


Page revision timeline rework

Overview
This pull request re-implements the revision timeline feature. Originally targeting the issue described in #830, the project scope expanded to include a comprehensive refactor. The new implementation improves code readability and functionality by utilizing flex-layout and replacing datalist and option elements with click listeners for item selection.
In response to feedback from @osmers and @JoeyStk, the timeline has been made scrollable. Users can now navigate through the timeline using the previous and next buttons, the left and right arrow keys, or horizontal scrolling.
You can find a screencast that demonstrates the new behaviuor here: https://github.com/user-attachments/assets/418389df-3168-431f-a2c9-894acbdbb0b8.
Key Changes

Enhanced accessibility by increasing contrast for revision numbers.
Improved layout by centering the timeline behind items for a more balanced and visually appealing design.
Enhanced user interaction with an updated cursor to a pointer to indicate clickable items.
Refined tooltips by adjusting positioning to ensure they consistently appear directly below the selected item.
Fixed alignment issues to address any previous misplacement of items.
Implemented fixed tooltip overflow management to ensure tooltips render on the left if they would exceed the container boundary.
Enabled horizontal scrolling to accommodate numerous revisions without crowding.
Added multiple navigation options for a comprehensive overview of the changes.

Side Effects

Scrolling Behavior: Scrolling events are only triggered when the content exceeds the container size. This means users cannot scroll through items if the timeline is not scrollable or is scrolled to the end.
Feature Behavior Change: Users may notice changes in feature behavior. A tooltip introducing the new controls could be considered to assist those familiarizing themselves with the updated feature.

Visual Comparison
Before:

After:

Related Issue

Fixes: #830

Pull Request Review Guidelines

From what I've seen in the short video, I like it a lot :)

Hey @JoeyStk, the browser compatibility looks good to me. How about we review it together during our co-working slot on Friday? 😊

I had a look at this with @osmers and we are both very happy with the new implementation!
Currently we don't think it needs a popup or tooltip to explain this further, as we assume that this is self-explanatory enough. This might become necessary once more testing has been done, but for now this is good to go :rocket:

Maybe we need here a release note? :)


Development: Fix Warnings about unnecessary optional chaining

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I followed the coding and design guidelines and ensured that the layout is responsive.

Motivation and Context

When starting the client in IntelliJ, multiple warnings about unnecessary optional chaining are shown.
Description

This PR removes unnecessary optional chaining.
This might be problematic, since some objects sent by the server might be null even if the type would not allow it.
Steps for Testing

Prerequisites:

Check the changes
Think about if they might be null and they should be handled differently, e.g with an additional *ngIf

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

I think in the dev meeting last week we agreed to keep it as-is and ignore the warning. Did you replace all occurrences or only selected ones?

Yes, we don't want to fix those warnings because they can be false and removing the optional chains can lead to runtime issues.
In a merged PR yesterday, those warnings were deactivated and I encourage everybody to program as defensive as possible in the client code


Modify "Blog Resource" to "Xeta"

Hello,
I want to modify the name, because now it's not only a blog. I have also developed a forum and some others features. ^^

It look like my editor love to remove white space. lol
I need to fix it or it's good ?

No please revert it.

Alphabetical order please :)

Thanks !


AzFilesHybrid parameters changed.

SamAccountName is not a valid parameter on the <IP_ADDRESS> AzFilesHybrid.   This page need to updated to match the new parameters
Join-AzStorageAccount : A parameter cannot be found that matches parameter name 'SamAccountName'.
At line:4 char:9

    -SamAccountName $SamAccountName `

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

CategoryInfo          : InvalidArgument: (:) [Join-AzStorageAccount], ParameterBindingException
FullyQualifiedErrorId : NamedParameterNotFound,Join-AzStorageAccount

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

ID: 7a1a9f3d-5733-012a-a0d7-c00ec21b9232
Version Independent ID: 1e70ab95-9488-5aa3-b8ef-e58b3e0067bb
Content: Enable AD DS authentication to Azure file shares
Content Source: articles/storage/files/storage-files-identity-ad-ds-enable.md
Service: storage
Sub-service: files
GitHub Login: @khdownie
Microsoft Alias: kendownie

@garetjax67
Thanks for your feedback! We will investigate and update as appropriate.

@khdownie
Can you please check and add your comments on this doc update request as applicable.

@garetjax67 please download the latest release and try again:
https://github.com/Azure-Samples/azure-files-samples/releases/tag/v0.2.4
There was an old 0.2.4 package before the latest release due to some versioning issue. The old package doesn’t support the new parameter SamAccountName. Likely you got the old package. The latest link should have the support for SamAccountName.

#please-close


POL-293 Add paging to the history of a single policy

Signed-off-by: Heiko W. Rupp<EMAIL_ADDRESS>

Something else to note, is that the UI would still need all the elements in the page for exporting (json/csv), should the UI consume all the pages to build this report?

Some test, not sure if i'm wrongly fetching the second page
curl 'https://ci.foo.redhat.com:1337/api/policies/v1.0/policies/3f421b5c-babc-4cf4-9026-0b9083d5b1df/history/trigger?limit=50&offset=0' | jq ". | length"
50

curl 'https://ci.foo.redhat.com:1337/api/policies/v1.0/policies/3f421b5c-babc-4cf4-9026-0b9083d5b1df/history/trigger?limit=200&offset=0' | jq ". | length"
200

but
curl 'https://ci.foo.redhat.com:1337/api/policies/v1.0/policies/3f421b5c-babc-4cf4-9026-0b9083d5b1df/history/trigger?limit=50&offset=50' | jq ". | length"
0

@burmanm maybe a bug from the engine?
I see that the following arguments are being sent to the engine:
@GET
  @Consumes("application/json")
  String findLastTriggered(@QueryParam("triggerIds") String triggerIds,
                                @QueryParam("thin") boolean thin,
                                @QueryParam("page") int page,
                                @QueryParam("per_page") int per_page,
                                @HeaderParam("Hawkular-Tenant") String customerId);

engine.findLastTriggered("the-id", false, 1, 50, "the-account")

and the engine returns []

I updated the engine, and now I'm getting [] always, but I can see "Last Triggered" date,maybe related to https://github.com/RedHatInsights/policies-engine/pull/80 ?

I don't see that [] in the master for all queries. Thin alerts shouldn't make a difference to this, but I'll have to investigate the apparent bug (maybe there's a double filtering done - so Infinispan + code and that causes the offsets to go wrong).

Debugging the backend code, it looks like something changed on the engine, it is returning (for first page of 2 elements):
[
   {
      "eventType":"ALERT",
      "tenantId":"940527",
      "id":"fe5a82ed-129c-4ce0-8e3b-63ab4aac045e-1591732136644-2243f530-f544-410b-bb4c-3d6090f65cc4",
      "ctime":1591732136644,
      "dataSource":"_none_",
      "dataId":"fe5a82ed-129c-4ce0-8e3b-63ab4aac045e",
      "category":"ALERT",
      "text":"Fail if we are running on a x86_64 - We should be using arm.",
      "trigger":{
         "tenantId":"940527",
         "id":"fe5a82ed-129c-4ce0-8e3b-63ab4aac045e",
         "name":"Copy of Not arch x86_64",
         "description":"Fail if we are running on a x86_64 - We should be using arm.",
         "type":"STANDARD",
         "eventType":"ALERT",
         "eventCategory":null,
         "eventText":null,
         "severity":"MEDIUM",
         "actions":[
            {
               "tenantId":"940527",
               "actionPlugin":"email",
               "actionId":"_managed-instance-email-35e48b6487d9568e"
            }
         ],
         "autoDisable":false,
         "autoEnable":false,
         "autoResolve":false,
         "autoResolveAlerts":false,
         "autoResolveMatch":"ALL",
         "enabled":true,
         "firingMatch":"ALL",
         "source":"_none_"
      },
      "severity":"MEDIUM",
      "status":"OPEN",
      "lifecycle":[
         {
            "status":"OPEN",
            "stime":1591732136644
         }
      ]
   },
   {
      "eventType":"ALERT",
      "tenantId":"940527",
      "id":"fe5a82ed-129c-4ce0-8e3b-63ab4aac045e-1591732136583-20d4a793-fa41-4321-9f6d-006e4d062cfc",
      "ctime":1591732136583,
      "dataSource":"_none_",
      "dataId":"fe5a82ed-129c-4ce0-8e3b-63ab4aac045e",
      "category":"ALERT",
      "text":"Fail if we are running on a x86_64 - We should be using arm.",
      "trigger":{
         "tenantId":"940527",
         "id":"fe5a82ed-129c-4ce0-8e3b-63ab4aac045e",
         "name":"Copy of Not arch x86_64",
         "description":"Fail if we are running on a x86_64 - We should be using arm.",
         "type":"STANDARD",
         "eventType":"ALERT",
         "eventCategory":null,
         "eventText":null,
         "severity":"MEDIUM",
         "actions":[
            {
               "tenantId":"940527",
               "actionPlugin":"email",
               "actionId":"_managed-instance-email-35e48b6487d9568e"
            }
         ],
         "autoDisable":false,
         "autoEnable":false,
         "autoResolve":false,
         "autoResolveAlerts":false,
         "autoResolveMatch":"ALL",
         "enabled":true,
         "firingMatch":"ALL",
         "source":"_none_"
      },
      "severity":"MEDIUM",
      "status":"OPEN",
      "lifecycle":[
         {
            "status":"OPEN",
            "stime":1591732136583
         }
      ]
   }
]

and the backend query "$.[*].evalSets..value" is the one returning [] after update.

Well, the backend is now removing evalsets from alerts storage if that is set (in the application.properties), so searching them would be impossible.

Ok, when setting engine.backend.ispn.alerts-thin to false it returns the evalSet as did before.

What i said above (https://github.com/RedHatInsights/policies-ui-backend/pull/119#issuecomment-641486265) is still an issue.
Using pages of 50 elements:

If I have 99 elements, page 1 and page 2 show correctly.
When I have 100 elements, the page 2 yields no elements.
Having 102 elements page 1 shows OK, page 2 empty and page 3 shows 2 elements.

Something else to note, is that the UI would still need all the elements in the page for exporting (json/csv), should the UI consume all the pages to build this report?

I think the UI would need to iterate over the pages. Sending with unlimited could be much too much data that is dealt with in one go.

Something else to note, is that the UI would still need all the elements in the page for exporting (json/csv), should the UI consume all the pages to build this report?

If there's export functionality, then it should probably just stream the data from engine? No point keeping any of this in memory elsewhere.

This depends now on https://github.com/RedHatInsights/policies-engine/pull/82

Tested this PR, is working fine.

Openapi has the types for the paged policy and paged triggers.
Paginated response is good

Already iterating over the pages when exporting.


Image and Audio support

In ChatGPT app, they added a support to image uploading and vocal messages.
Actually i don't know if the endpoints that allows image and audio messages uploading but is it a good idea to add two new methods to the client that allows the user to enjoy these ChatGPT features?

Adding image and audio support will be definitively great. Unfortunately, in this moment I haven't the time to implement these new features.
I'm happy to accept PR for this.


Automated cherry pick of #9690: fix(region): optimized secgroup rule sync

Cherry pick of #9690 on release/3.7.
#9690: fix(region): optimized secgroup rule sync

Codecov Report

Merging #9854 (6eec828) into release/3.7 (0ff3997) will increase coverage by 2.07%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.7   #9854       +/-   ##
===============================================
+ Coverage         5.98%   8.05%    +2.07%
===============================================
  Files              848     107      -741
  Lines           131795   12991   -118804
===============================================
- Hits              7887    1047     -6840
+ Misses          123206   11824   -111382
+ Partials           702     120      -582

Flag
Coverage Δ

aFlag
8.05% <0.00%> (+2.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/hostman/diskutils/nbd/driver.go
0.74% <0.00%> (-0.01%)
:arrow_down:

pkg/hostman/diskutils/nbd/lvmutils.go
4.70% <0.00%> (-0.24%)
:arrow_down:

pkg/monitor/alerting/eval_context.go
34.25% <0.00%> (-2.75%)
:arrow_down:

pkg/keystone/models/identitybase.go

pkg/compute/guestdrivers/esxi.go

... and 716 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #9854 (6eec828) into release/3.7 (0ff3997) will increase coverage by 2.07%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.7   #9854       +/-   ##
===============================================
+ Coverage         5.98%   8.05%    +2.07%
===============================================
  Files              848     107      -741
  Lines           131795   12991   -118804
===============================================
- Hits              7887    1047     -6840
+ Misses          123206   11824   -111382
+ Partials           702     120      -582

Flag
Coverage Δ

aFlag
8.05% <0.00%> (+2.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/hostman/diskutils/nbd/driver.go
0.74% <0.00%> (-0.01%)
:arrow_down:

pkg/hostman/diskutils/nbd/lvmutils.go
4.70% <0.00%> (-0.24%)
:arrow_down:

pkg/monitor/alerting/eval_context.go
34.25% <0.00%> (-2.75%)
:arrow_down:

pkg/keystone/models/identitybase.go

pkg/compute/guestdrivers/esxi.go

... and 716 more

Continue to review full report at Codecov.

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


Add files via upload

I am a part of my school's Comp Sci club and I would like to be able to run Intellij even though I am unable to pay. Thank you for your time.

@nrosen015 I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host student.marbleheadschools.org not found: 2(SERVFAIL) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Overlapping packages

Here's a list of packages that overlap with this and might influence the design:
https://github.com/JuliaGeometry/GeometryTypes.jl
https://github.com/zenna/AbstractDomains.jl
https://github.com/tpapp/ContinuousTransformations.jl/blob/master/README.md
https://github.com/JuliaReach/LazySets.jl

There is indeed some overlap with all of these packages, perhaps most with GeometryTypes, yet they are all rather distinct in their purpose too. It begs the question what exactly the purpose of this package is. We are mostly concerned with approximating functions defined on a domain. Clearly, Domains.jl is too general a name for us to register this package.

They each have their own distinct purpose, but also are representing the same objects, and for simple things this is silly.
Here's a proposal:

Make a super package called, say, InfiniteSets.jl that encodes the interface for infinite sets and defines

abstract type InfiniteSet{T} end

but little else.
2. Make a PR to IntervalSets.jl so that Interval <: InfiniteSet, and move over the open interval code from here to that package.
3. Make a PR to GeometryTypes.jl, and merge the relevant types from here
4. What's left over here would mostly be maps and spaces.
@SimonDanisch any thoughts on this?

(What type would the Cartesian product of a CountableSet and an UncountableSet be? They are interesting properties, but perhaps not ideal supertypes.)
Looking at GeometryTypes.jl, the AbstractGeometry{N, T} type is just like our EuclideanDomain{N,T} and indeed all it takes is one supertype that could be InfiniteSet{SVector{N,T}}.
The eltype of that would be SVector{N,T}, which clashes with the eltype of AbstractGeometry{N, T} which is T. That can easily be fixed on either end. Still, I'd feel uneasy about enforcing a joint supertype on different packages, when integration in Julia can be done less intrusively by respecting a similar interface without sharing an inheritance tree. (It does look like the simplest option and I'd like to use the meshes.)

IntervalSets.jl is more crucial, as the whole point of that package was to avoid having multiple definitions of interval.
Having a single abstract type can be very useful, e.g. AbstractArray is a type, not just an interface.
I think I’ll put in a PR moving the more versatile interval defined here to IntervalSets.jl. I’ll include an abstract type InfiniteSet in the PR to initiate the conversation.

Okay, thanks!

I'm starting to think you are right about not needing an abstract type at all. There's tons of types floating around that cat may be useful as a domain but are never going to be <: InfiniteSet:
julia> 1 in 1
true

julia> 1 in Set([1,2,3])
true

What if instead of trying to make everything <: InfiniteSet, I rewrite ApproxFun so domains can be any type? For example, I could have domain(DiracDelta()) === 0,  domain(DiracDelta(0)+DiracDelta(2.3)) === Set([0,2.3]), domain(SequenceSpace()) === countfrom(1), etc. This removes the extra layer of wrapping an object in a Domain.

I'm behind anything, that makes these packages more coherent :) I wouldn't mind depending on a lightweight math package, if that's what needed. But of course, if you figured it out without changing any packages, that does sound simpler!

I've made the PR
https://github.com/JuliaMath/IntervalSets.jl/pull/26

Here’s another one
https://github.com/tpapp/ContinuousTransformations.jl/blob/master/README.md

Here’s another one: https://github.com/JuliaReach/LazySets.jl

it seems JuliaGeometry is settling on https://github.com/JuliaGeometry/Meshes.jl. There is quite a bit of overlap, but also some similarities.


no license

Hello Ricardo. This project does not have a license. Is this intentional? In this case, it seems that people are not allowed to modify the code and publish these modifications.
In case having no license is not intentional, I would like to you to consider adding one.
Thanks.

Thanks for pointing this out. It was an omission. I've licensed the code under the terms of the CC0 license.


Exception when compiling QICoreCommon-2.0.000

Describe the bug
info: Hl7.Cql.Compiler.ExpressionBuilder[0]       Building expressions for QICoreCommon-2.0.000 Unhandled exception. System.InvalidOperationException: Duplicate code detected: billing from Diagnosis Role (http://terminology.hl7.org/CodeSystem/diagnosis-role)    at Hl7.Cql.Compiler.ExpressionBuilder.Build() in /Users/alex/Dev/Firely/SDK/firely-cql-sdk/Cql/Cql.Compiler/ExpressionBuilder.cs:line 169    at Hl7.Cql.Packaging.LibraryPackager.PackageResources(DirectoryInfo elmDirectory, DirectoryInfo cqlDirectory, DirectedGraph packageGraph, TypeResolver typeResolver, OperatorBinding operatorBinding, TypeManager typeManager, Func`2 canon, ILoggerFactory logFactory) in /Users/alex/Dev/Firely/SDK/firely-cql-sdk/Cql/Cql.Packaging/LibraryPackager.cs:line 157    at Hl7.Cql.Packaging.ResourcePackager.Package(DirectoryInfo elmDir, DirectoryInfo cqlDir, Action`1 afterPackageMutator) in /Users/alex/Dev/Firely/SDK/firely-cql-sdk/Cql/Cql.Packaging/ResourcePackager.cs:line 42    at Hl7.Cql.Packager.Program.Package(DirectoryInfo elmDir, DirectoryInfo cqlDir, DirectoryInfo csDir, DirectoryInfo fhirDir) in /Users/alex/Dev/Firely/SDK/firely-cql-sdk/Cql/PackagerCLI/Program.cs:line 109    at Hl7.Cql.Packager.Program.Main(String[] args) in /Users/alex/Dev/Firely/SDK/firely-cql-sdk/Cql/PackagerCLI/Program.cs:line 77
To Reproduce
Measures are committed to branch inspect-cms-measures. Executing the PackagerCli in that branch will trigger the error.
Version used:
Current develop version of the PackagerCli

The code "billing" appears twice:
Once on line 35:
code "Billing": 'billing' from "Diagnosis Role" display 'Billing'
and once on line 93:
code "billing": 'billing' from "Diagnosis Role" display 'billing diagnosis'
Note that the display differs, but also the local name of the code, once Billing and once billing, so they differ in case.
The problem surfaces because in the ELM, the identifier for a code is actually its code, which is the same, so the ELM contains two "codes" with the same id - I think it's not unreasonable we catch this  - certainly since the introduced local name differ only in case, and there are inconsistent displays. It seems this is a human oversight.
So, what to do?  Looking at the CQL spec, it says:

1.9. Case-Sensitivity
To encourage consistency and reduce potential confusion, CQL is a case-sensitive language. This means that case is considered when matching keywords and identifiers in the language

It seems we need to take "billing" and "Billing" as separate codes, and so use the introduced local name, not the id as the unique key. Changing the dictionary lookup to do so is easy, but we should allow some time to find downstream bugs that maybe count on "id" being unique and/or the local name not being case-sensitive.


does useSendTransaction support pay modal for react native ?

I am using useSendTransaction but nothing happened .

@ngocan3897 pay transaction modal is not currently supported it in react native.
curious how do you intend to use it? is it to pay with another wallet? or for fiat onramp?

For native mobile apps there is a bit more complexity around fiat onramp due to app store restrictions. But we'll be working on enabling cross chain / pay from another wallet functionality soon.Btw open to contributions!


Shaka can read the Start TimeCode embedded into video mp4 h264?

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
Please ask your question
If the video Start  TimeCode is for example 03:00:00:00 the player can read this value?

If you're playing a single mp4, the timestamps in the file are what will show in the UI for the current time.  This will be true whether you're using our UI or the browser's native controls.

But i need to see the timecode of the video not the current time.
Maybe the video tc start is 02:00:00:00
When playing 10 seconds i need to see
02:00:10:24 and not 0.10
it's possible?
Thanks!
On Fri, 31 Jan 2020 at 21:57 Joey Parrish<EMAIL_ADDRESS>wrote:

If you're playing a single mp4, the timestamps in the file are what will
show in the UI for the current time. This will be true whether you're using
our UI or the browser's native controls.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/shaka-player/issues/2369?email_source=notifications&email_token=AILPD7WXBOL63Y2DRILSB63RATCGDA5CNFSM4KOJX432YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKQOYDA#issuecomment-580971532,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AILPD7UHFLPCCTNWU5WAHOLRATCGDANCNFSM4KOJX43Q
.

I think the "current time" of the video is what you're looking for.  In JavaScript, that's videoElement.currentTime.  It's not the "wall clock time", as in "8:32 pm".  It's a timestamp in seconds.  Just try it out and see.

When you have a Master film for example.
You need to Edit and cut it into chapters from 1 to 6 For example.
The chapter 1 start at time 0 hours 0 minutes 0 seconds 0 frames. But
chapter 4 Start at 1 hour 23 minutes 12 seconds 29 frames.
That information is embedded into the video.
So if I play the chapter 4 from The begining I want to see 01:23:12:29 not
0.0 seconds
The request will be:
I want to see the timecode embedded into the video hh:mm:ss:ff not the
current time.
On Mon, 3 Feb 2020 at 21:40 Joey Parrish<EMAIL_ADDRESS>wrote:

I think the "current time" of the video is what you're looking for. In
JavaScript, that's videoElement.currentTime. It's not the "wall clock
time", as in "8:32 pm". It's a timestamp in seconds. Just try it out and
see.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/shaka-player/issues/2369?email_source=notifications&email_token=AILPD7XWLQHDUN2KNZ2WVODRBC2QTA5CNFSM4KOJX432YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKV5XNA#issuecomment-581688244,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AILPD7RFLOF4PDDBP4MS5D3RBC2QTANCNFSM4KOJX43Q
.

It sounds like what you want is a timestamp embedded in some format in the mp4.  I don't know what format that is, but if it's chapter metadata from an editor, I'm sure that's not being read by the browser and that there's no API in a browser to get that for you.
I'm sorry that we aren't able to help you with this.


Fully migrate to pyproject.toml

Split from #474

Thanks for your contribution. I ended up doing equivalent changes as part of migrating the build system from setuptools to hatch (as is now recommended by the Python publishing guide).


Failed capture at frame 1995: Uncapped Map()/Unmap()

Description

Environment

RenderDoc version: 1.8
Operating System: MIUI 11.0.6
Graphics API: OpenGLES

Hi there, your issue has been closed due to not correctly following the issue template. Please read the documentation about filing issues and open a new issue which does follow the issue template. Do not reply to this issue with more information or with a correctly formatted issue, as that will only lead to confusion.
I try to address all github issues and fix bugs quickly, but badly formatted issues or poorly described bug reports especially are a significant drain on project resources. Taking a few minutes to file a good issue makes a huge difference and will get it addressed faster - everybody wins!
In github when you first create a new issue the form is pre-populated with a template which you should read over and follow. As linked above there is documentation going into more detail about what makes a good issue.


⚠ Bofrost.fr has degraded performance

In a93345d, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 941 ms

Resolved: Bofrost.fr performance has improved in 884602c.


Prometheus: Add SERVFAIL metrics

This basically duplicates the NXDOMAIN metrics logic.

thank for this contribution :)

Planning more but that one I could do without learning the language :-)


Initial commit for new website

Landing banner Download button leads to 404 error

In step 6 - Build an installer, the commands are incorrect.
for linux, it should be:
cmake -DCMAKE_BUILD_TYPE=Release  -DDIST_INSTALLER=ON <path to source> && make && make installer


Alamofire not working in Xcode 8 GM and Swift 3

So I've used AlamoFire for years and getting ready for the new Swift3 Xcode8 update.  I've installed Xcode8 GM and then used the instructions to pull the Swift3 branch:
`source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '9.0'
use_frameworks!
target 'MySwift3Test' do
pod 'Alamofire', '~> 3.4'
end
`
However when I open up the newly created workspace (brand new project), Xcode is telling me that AlamoFire has not been converted and attempts to update the code?
What am I missing?

You're missing the necessity to use the master branch for Swift 3 compatibility or 3.5.0 for Swift 2.3, and update to CocoaPods 1.1.0.beta.2 to properly support Xcode 8 (mostly).

Turns out that needed to change it to
pod 'Alamofire', :git => 'git@github.com:Alamofire/Alamofire.git', :branch => 'swift3'
and then let xCode "attempt to update to Swift 3" which when it gets done it says no updates however has some 800 "warnings" which are bogus.  If you then do a CLEAN and BUILD, it appears to work just fine.  However... it can't find
print(UIDevice.deviceModel()) // x86_64 / iPhone7,2

@jshier it would probably help to update the README to make this clearer.  Currently, the README lists Swift 3.0+ as a requirement, but then in the installation instructions, it says to use v3.5, which is not Swift 3...


Multiply path scale problem

Hi, I have a vector image (vector_img.xml):
<?xml version="1.0" encoding="utf-8"?>
<vector xmlns:android="http://schemas.android.com/apk/res/android"
    android:width="22dp"
    android:height="22dp"
    android:viewportWidth="300"
    android:viewportHeight="300">

    <path
        android:fillColor="#FF000000"
        android:pathData="M 150 0 C<PHONE_NUMBER>75 0 300 67.1572875254 300 150 C<PHONE_NUMBER>12475<PHONE_NUMBER>75 300 150 300 C 67.1572875254 300 0<PHONE_NUMBER>75 0 150 C 0 67.1572875254 67.1572875254 0 150 0 Z" />

    <path
        android:fillColor="#FFFFFFFF"
        android:pathData="M 150 30 C<PHONE_NUMBER>8 30 270 83.7258300203 270 150 C<PHONE_NUMBER>6998<PHONE_NUMBER>8 270 150 270 C 83.7258300203 270 30<PHONE_NUMBER>8 30 150 C 30 83.7258300203 83.7258300203 30 150 30 Z" />

    <path
        android:fillColor="#FF000000"
        android:pathData="M 150 60 C<PHONE_NUMBER>85 60<PHONE_NUMBER>72515 240 150 C<PHONE_NUMBER>27485<PHONE_NUMBER>85 240 150 240 C<PHONE_NUMBER>15 240 60<PHONE_NUMBER>85 60 150 C 60<PHONE_NUMBER>15<PHONE_NUMBER>15 60 150 60 Z" />

</vector>

I'm trying to scale vector programmatically like this:
VectorMasterDrawable vectorDrawable = new VectorMasterDrawable(context, R.drawable.vector_img);
vectorDrawable.setScaleX(1.5f);
vectorDrawable.setScaleY(1.5f);

The result is not happy:

Perhaps the problem is that when we scale vector we can't set pivot points? Or am I doing something wrong?)
Thanks

Yes, the problem is with the pivot points being at the top left corner by default.
I will implement another scale method which takes pivot points as arguments along with the scale factor.
Thanks for opening the issue.


Add el-offline to syncing api response

PR Description
Add an el_offline to the /eth/v1/node/syncing syncing API response
Fixed Issue(s)

https://github.com/ConsenSys/teku/issues/6655
Documentation

[ ] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[ ] I thought about adding a changelog entry, and added one if I deemed necessary.

@rolfyone I ended up making the SyncStateTracker listening to the ExecutionClientEventsChannel, removed the logic from the API and added an acceptance test

Will be reopened/refactored once https://github.com/ethereum/beacon-APIs/pull/290 is done

Replaced by https://github.com/ConsenSys/teku/pull/6770


Prevent crash on  Quality and Signal level functions

Some interfaces cards when run "scan" might return values
like these:
Quality:0  Signal level:0  Noise level:0
Quality=0/100  Signal level=4/100

@roramirez Thanks! I hadn't encountered that before, but it appears to work in that situation.
Appreciate the contribution [=


tcpServersManager and tests

@tobybrad Appveyor says that tests aren't passing. Please resolve. If you click on the appveyor link you'll see that the failures are relevant to this code.
Also, the Javascript code was written without running JSCS or JSHINT so it contains a lot of style violations. I'll fix them later but in the future please use an IDE that enforces JSCS and JSHINT rules.

Reviewed 3 of 5 files at r1.
Review status: 3 of 5 files reviewed at latest revision, 23 unresolved discussions, some commit checks failed.

thali/NextGeneration/tcpServersManager.js, line 11 [r1] (raw file):
Why don't you use thalilogger?

thali/NextGeneration/tcpServersManager.js, line 158 [r1] (raw file):
It's true that if you tried to add an object directly as a property member then you would have a problem because it's name has to be represented as a string and the issue you bring up causes a problem.
But you should never have to assign an ID yourself because Javascript is required to be able to distinguish different instances of the same object. Please see https://gist.github.com/yaronyg/dea38f150015ab62c5c7
So please remove this method and the id properties in general, we don't need them. We can instead just use '===' comparisons to determine membership.
(As a side note, if we were going to use _id then wouldn't it have made more sense to just put the IDs as properties on objects like mux._streams and that way we could at least do lookups in O(1) and removals (using delete) in O(1)? But IDs are like ref counting, it's just something to get wrong so let's keep the structure of your existing code using an array and get rid of the IDs)

thali/NextGeneration/tcpServersManager.js, line 349 [r1] (raw file):
A 164 line Javascript function? I'm fairly certain that constitutes cruel and depraved behavior in most jurisdictions. Perhaps it should be refactored into something slightly more digestible?

thali/NextGeneration/tcpServersManager.js, line 383 [r1] (raw file):
The function's actual name is 'makeIntoCloseAllServer'. I'd appreciate it if you would use the full name only because every time I see "CloseAllServer" I think the server is being closed and wonder why that's happening at this point!

thali/NextGeneration/tcpServersManager.js, line 396 [r1] (raw file):
Isn't this code doing exactly what makeIntoCloseAllServer is doing except it uses end (which leaves behind half opened connections) rather than destroy (which closes everything)?

thali/NextGeneration/tcpServersManager.js, line 419 [r1] (raw file):
As the docs say, http://jxcore.com/docs/net.html#socketsettimeouttimeout-callback, a timeout doesn't close the connection. In fact, it doesn't actually do anything. So how can we safely remove the connection from _incoming? Don't we have to wait until close? Also, shouldn't we call destroy on ourselves so we can clean up this connection?
More generally, how do we ever manage to generate this event? It should only be generated in response to socket.setTimeout but I can't find us ever calling that method although I do believe it is required by the spec for what I suspect are reasonably obvious reasons.

thali/NextGeneration/tcpServersManager.js, line 462 [r1] (raw file):
I couldn't find an 'end' event anywhere, did you mean 'close'?

thali/NextGeneration/tcpServersManager.js, line 470 [r1] (raw file):
Per http://jxcore.com/docs/net.html#event-error any time error is called you are guaranteed there will be a subsequent call to close. So we should be able to skip the call to removeArrayEelement and instead wait for the close event to trigger it.

thali/NextGeneration/tcpServersManager.js, line 489 [r1] (raw file):
Where was mux._incoming defined?

thali/NextGeneration/tcpServersManager.js, line 490 [r1] (raw file):
I think this line is an error. Isn't this already handled in the close handler for the incoming connection?

thali/NextGeneration/tcpServersManager.js, line 505 [r1] (raw file):
If listen fails shouldn't we reject(err) the result so it propagates to start and gets returned to the caller? Otherwise aren't we just black holing this error outside of the log?

thali/NextGeneration/tcpServersManager.js, line 704 [r1] (raw file):
313 lines long? A little refactoring, maybe even into different files, could really help with readability.

thali/NextGeneration/tcpServersManager.js, line 728 [r1] (raw file):
Shouldn't this call resolve with the port of the peerServer per the spec's requirement that if createPeerListener is called on a peer we are already listening for then we will return the port we are using?

thali/NextGeneration/tcpServersManager.js, line 868 [r1] (raw file):
Isn't firstConnection always going to be true at this point because it was set at the start of onNewConnection and nothing will have run between then and now to have changed its value? In which case, why is it in the if statement
I think the real issue is that there seems to be an assumption in the code that somehow firstConnection is going to stick around since it gets set in various subfunctions but it will disappear as soon as we exit the parent method. It isn't defined on any object and while we write to it 3 different places we only check it once and that once is here before anything else could have happened. So what firstConnection was meant to do it can't be doing it. Something isn't quite right.

thali/NextGeneration/tcpServersManager.js, line 880 [r1] (raw file):
Shouldn't this be hooked into the promise so that we only get resolve to the parent promise if we successfully were able to connect to the peer?

thali/NextGeneration/tcpServersManager.js, line 922 [r1] (raw file):
In the spec we didn't just say the oldest server but rather the oldest inactive server. So I would have expected that anytime a server has active content being sent through it that we would update the [0] date value. That way the server to be closed is the one that was used in the most distant past. We don't care when it was originally created, only when it was last used.

thali/NextGeneration/tcpServersManager.js, line 943 [r1] (raw file):
This is an asynchronous callback so how do we ever end up calling reject? I can see the code below that will call reject if server is null but this error handle won't cause server to be null nor can it cause server to be null because it won't be called until after we have returned from createServer. It seems like there is a connection missing here between this error state and cleaning up a failed peerServers entry and removing it.
Personally I would go farther and say that createPeerListener MUST NOT resolve() until it knows that listen succeeded. When combined with pleaseConnect I suspect we will have to potentially track two promises in an array and use Promise.all to only return when both have been resolved.

thali/NextGeneration/tcpServersManager.js, line 948 [r1] (raw file):
Please have some pity for the future folks who have to maintain this file. Wouldn't it have been nicer to have had a value like { lastUsedDate: Date.now(), serverInstance: sever } rather than what we have now which is contextless references to _peerServers[peerIdentifier][0] and _peerServers[peerIdentifiery][1] everywhere?
Also I believe it is considered more correct to use Date.now() than new Date() since this lets us skip creating a new object.

thali/NextGeneration/tcpServersManager.js, line 955 [r1] (raw file):
In the createServer code we add an entry to _peerServers but if we are in this code then that entry is 'bad'. Shouldn't it be removed?

thali/NextGeneration/tcpServersManager.js, line 997 [r1] (raw file):
The error could happen at just about any time, including far in the future, long after a response to the promise has been sent. Now the good news is that trying to resolve/reject the same promise more than once is not, I believe, an error. I think after the first call to promise/reject any subsequent calls are ignored. But this whole thing feels kind of like a race condition. If we are lucky and the error happens early enough then we get the reject otherwise it is invisible. But maybe that is o.k.?

thali/NextGeneration/tcpServersManager.js, line 1000 [r1] (raw file):
Where did the call to outgoing.setTimeout happen to cause this event to fire?

thali/NextGeneration/tcpServersManager.js, line 1004 [r1] (raw file):
I thought we cannot rely on the output of address() until we got the listen callback? So don't we have to wait until there before we can resolve?

thali/NextGeneration/tcpServersManager.js, line 1008 [r1] (raw file):
I thought we cannot rely on the output of address() until we got the listen callback? So don't we have to wait until there before we can resolve?

Comments from the review on Reviewable.io

PR is added to the queue for testing as 1. task. (7fe97b0)

Test (Fail) 60124347 build is completed (7fe97b0)
See https://github.com/ThaliTester/TestResults/tree/601243477fe97b0_tcpServersManager_and_tests_tobybrad/ for the logs

thali/NextGeneration/tcpServersManager.js, line 885 [r5] (raw file):
After quite a bit of debugging, I realized why this (and some following code) does not work on devices.
That is, because both iOS and Android return the connection object as string. If one checks testThaliMobileNative.js, it can be seen that the callbacks to connect have something like connection = JSON.parse(connection);, which would be needed here as well.

Comments from the review on Reviewable.io

PR is added to the queue for testing as 1. task. (6e0f5f5)

Review status: 2 of 8 files reviewed at latest revision, 24 unresolved discussions.

thali/NextGeneration/tcpServersManager.js, line 349 [r1] (raw file):
Will get to...

thali/NextGeneration/tcpServersManager.js, line 419 [r1] (raw file):
we didn't create incoming, the native layer did. Should we really be setting timeouts on and closing socket we didn't originate ?? Nonetheless.. I've set it to 30s.

thali/NextGeneration/tcpServersManager.js, line 462 [r1] (raw file):
https://nodejs.org/api/net.html#net_event_end

thali/NextGeneration/tcpServersManager.js, line 704 [r1] (raw file):
Will get to...

thali/NextGeneration/tcpServersManager.js, line 885 [r5] (raw file):
Yeah. so this is a limitation of JXCore. You can either return JSON or a list of params. You can't return a mix of the two.

Comments from the review on Reviewable.io

PR is added to the queue for testing as 2. task. (0083d9b)

PR is added to the queue for testing as 3. task. (c8c8bd4)

Test (Fail) 60124347 build is completed (6e0f5f5)
See https://github.com/ThaliTester/TestResults/tree/601243476e0f5f5_tcpServersManager_and_tests_tobybrad/ for the logs

Test (Fail) 60124347 build is completed (6e0f5f5)
See https://github.com/ThaliTester/TestResults/tree/601243476e0f5f5_tcpServersManager_and_tests_tobybrad/ for the logs

Test (Fail) 60124347 build is completed (0083d9b)
See https://github.com/ThaliTester/TestResults/tree/601243470083d9b_tcpServersManager_and_tests_tobybrad/ for the logs

Test (Fail) 60124347 build is completed (0083d9b)
See https://github.com/ThaliTester/TestResults/tree/601243470083d9b_tcpServersManager_and_tests_tobybrad/ for the logs

Test (Fail) 60124347 build is completed (c8c8bd4)
See https://github.com/ThaliTester/TestResults/tree/60124347c8c8bd4_tcpServersManager_and_tests_tobybrad/ for the logs

Test (Fail) 60124347 build is completed (c8c8bd4)
See https://github.com/ThaliTester/TestResults/tree/60124347c8c8bd4_tcpServersManager_and_tests_tobybrad/ for the logs

PR is added to the queue for testing as 2. task. (97f7ca7)

Test<PHONE_NUMBER>f7ca7(97f7ca7) has failed
See https://github.com/ThaliTester/TestResults/tree/6012434797f7ca7_tcpServersManager_and_tests_tobybrad/ for the fail logs

PR is added to the queue for testing as 1. task. (e9830ee)

Test (Fail) 60124347 build is completed (e9830ee)
See https://github.com/ThaliTester/TestResults/tree/60124347e9830ee_tcpServersManager_and_tests_tobybrad/ for the logs

PR is added to the queue for testing as 1. task. (d4f5b03)

Test (Success) 60124347 build is completed (d4f5b03)
See https://github.com/ThaliTester/TestResults/tree/60124347d4f5b03_tcpServersManager_and_tests_tobybrad/ for the logs

Test 60124347d4f5b03(d4f5b03) has failed
See https://github.com/ThaliTester/TestResults/tree/60124347d4f5b03_tcpServersManager_and_tests_tobybrad/ for the fail logs

PR is added to the queue for testing as 1. task. (64ab483)

Test (Success) 60124347 build is completed (64ab483)
See https://github.com/ThaliTester/TestResults/tree/6012434764ab483_tcpServersManager_and_tests_tobybrad/ for the logs

Test<PHONE_NUMBER>ab483(64ab483) has failed
See https://github.com/ThaliTester/TestResults/tree/6012434764ab483_tcpServersManager_and_tests_tobybrad/ for the fail logs

PR is added to the queue for testing as 1. task. (40c277f)

Test (Fail) 60124347 build is completed (40c277f)
See https://github.com/ThaliTester/TestResults/tree/6012434740c277f_tcpServersManager_and_tests_tobybrad/ for the logs

PR is added to the queue for testing as 1. task. (1b7fae3)

Test (Fail) 60124347 build is completed (1b7fae3)
See https://github.com/ThaliTester/TestResults/tree/601243471b7fae3_tcpServersManager_and_tests_tobybrad/ for the logs

Test (Fail) 60124347 build is completed (1b7fae3)
See https://github.com/ThaliTester/TestResults/tree/601243471b7fae3_tcpServersManager_and_tests_tobybrad/ for the logs

Reviewed 1 of 5 files at r2, 2 of 5 files at r3, 1 of 4 files at r5, 10 of 14 files at r8, 2 of 4 files at r10, 3 of 5 files at r11, 2 of 2 files at r12, 1 of 1 files at r13.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from the review on Reviewable.io

PR is added to the queue for testing as 1. task. (13fea37)

Test (Success) 60124347 build is completed (13fea37)
See https://github.com/ThaliTester/TestResults/tree/6012434713fea37_tcpServersManager_and_tests_tobybrad/ for the logs

Reviewed 1 of 1 files at r14.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from the review on Reviewable.io

Test<PHONE_NUMBER>fea37(13fea37) has failed
See https://github.com/ThaliTester/TestResults/tree/6012434713fea37_tcpServersManager_and_tests_tobybrad/ for the fail logs

PR is added to the queue for testing as 1. task. (d1a8dac)

PR is added to the queue for testing as 2. task. (d1a8dac)

Test (Success) 60124347 build is completed (d1a8dac)
See https://github.com/ThaliTester/TestResults/tree/60124347d1a8dac_tcpServersManager_and_tests_tobybrad/ for the logs

Test 60124347d1a8dac(d1a8dac) has failed
See https://github.com/ThaliTester/TestResults/tree/60124347d1a8dac_tcpServersManager_and_tests_tobybrad/ for the fail logs

Test (Success) 60124347 build is completed (d1a8dac)
See https://github.com/ThaliTester/TestResults/tree/60124347d1a8dac_tcpServersManager_and_tests_tobybrad/ for the logs

Test (Success) 60124347 build is completed (e678b8e)
See https://github.com/ThaliTester/TestResults/tree/60124347e678b8e_tcpServersManager_and_tests_tobybrad/ for the logs

Test 60124347e678b8e(e678b8e) has failed
See https://github.com/ThaliTester/TestResults/tree/60124347e678b8e_tcpServersManager_and_tests_tobybrad/ for the fail logs


Improve refreshing the refresh token scenario

Right now when the refresh token becomes invalid for whatever reason ( e.g. is expired or is revoked )
the only way to do that is to create a new authorizer, assign it to the client and retrying the call.
We should look if we can automate a retry logic on TokenRefreshErrror or at least expose a way to retrigger the auth flow without having to create a new authorizer.

@joshgav  can you consult with AAD team what they recommend to do when the refresh token is expired ? Should we automatically try to get a new one or leave it to the consumers of the SDK to explicitly obtain a new one ?

This has been implemented for track 2 in azidentity, we won't be back-porting it to track 1.


AP-ALB v0.8.x documentation migration to dedicated place

The README.md have a lot of content [1536 lines (1262 sloc)] and we're running out of how many heading levels HTML/Markdown could support.
This issue is about improve this situation. And also start to care about be able to be found on search results outside GitHub (something that start to make sense when eventually we get out of alphas and betas releases).

Already implemented at https://ap-application-load-balancer.etica.ai/


[@urql/exchange-execute] Async Context Provider

Some context value needs to be provided in async. currently, exchange execute only support sync context. it should be apollo SchemaLink equivalent.
apollo client (works perfect)
const schemaLink = new SchemaLink({
        schema,
        context: async () => {
         const value = await readConfig()
         return {
             value: value
         }
        },
      })

urql
executeExchange({
        schema,
        // failed for async
        context: async () => {
         const value = await readConfig()
         return {
             value: value
         }
        },
      }),

Duplicate of #2406


JMX doc

mention setting and use of isRegisterMbeans, set/isRegisterMbeans(boolean register) in https://github.com/brettwooldridge/HikariCP/wiki/MBean-(JMX)-Monitoring-and-Management

also, In description for leakDetectionThreshold
It would be better to clearly state that setting this property does NOT close connection reported as leak. as its name suggests it is connection leak 'detection' only.

Just fell there and wasted 30 minutes. It's 10 seconds edit of the wiki page - if there was a way of suggesting pull request of wiki pages I would my self

Fixed.


DRAFT: Update "Setting Access .." section in Studio documentation

Please don't merge it yet, this MR should be reviewed by Maria first.

 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.Anna Vyakhireva seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@annavernidub , I've made some changes. Shall I merge this PR?

@MariaShaposhnikova Yes, please!


Register

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/96184
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 17d83ed13f669e1c3e6e770fd825f1e70adc81be
git push origin v0.1.0


Annotations: Fix issue where dashboard annotations weren't rendering

Fixes an issue where dashboard-wide annotations (ones created via API without a defined panelId, which are given the panelId 0 when stored in the database) would not render on existing panels. (Newly created panels rendered the annotations correctly).
Not super familiar with the code so please let me know if there's a better way to fix this that I've missed. :)
Fixes the following issue: https://github.com/grafana/support-escalations/issues/13356

📦 Published PR as canary version: 5.23.4--canary.964.11745806385.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>

Hello Team! Any update? Thank you in advance

Hi @grbevi ! Just trying to get someone to review the PR, apologies for the wait.


Impl/from geo types

[x] I agree to follow the project's code of conduct.
[x] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.
[x] I ran cargo fmt

addresses #73 and #48.
This adds impls of From for every type and the Geometry enum in geo_types. It makes it unnecessary to bring to scope the ToWkt trait which gets deleted because it was not being used actually. Of course this is a breaking change.
Additionally I added some docs on the most relevant cases for this crate: parsing a wkt and getting a geometry and having a geometry and getting its WKT string. This is what actually motivates most of the PRs I've been doing, I just wanted to do that .-.
Some opinions
What if Wkt was instead a trait itself, implemented for every type in geo_types that provided a single method: wkt(&self) -> String?
being georust an environment for building geo applications it makes sense that things are integrated to work well within the environment, and maybe providing some LineString etc. traits which, if implemented on foreign types would give automatically a Wkt impl that allows to get its WKT string. And perhaps a WktGeometry enum with inner types refering to those in the geo_types crate just for the purposes of having something to parse a string into. Although it probably makes more sense to just have FromStr impls for the geo_types themselves...
Just an idea, I think it would simplify a lot how work with this crate happens.

it also addresses #55

I'm curious what you though of my proposal in #89 @categulario

With Display implemented for Wkt<T> I don't tink it is necessary because people using ToWkt are already getting a Wkt out of it, which can be to_string()ed

Just pushed some commits and rebased main.
ToWkt is restored but deprecated. The doc tests are fixed.

Closing this since it no longer reflects my ideas, mostly laid out in #73


Clear NodeRefs when nodes are unmounted

Description
Fixes #968
Checklist:

[ ] I have run ./ci/run_stable_checks.sh
[x] I have reviewed my own code
[x] I have added tests

@jstarry Does this fix look right?
If I'm on the right track, I'll probably need some help with writing tests for VComp. I couldn't figure that out.

@jatinderjit definitely on the right track! VComp will be very similar to the VTag test you wrote but you'll need a test Component that renders something in its view method. Feel free to modify the existing Comp component in the VComp tests module and have it return a div or something.

@jstarry I'm done with the changes.
The tests fail, if the node_ref isn't set to None. And they pass after the fix is added.

Looks great, thank you!


Update query.md

Overwrite with new ones_zh

Hey, @arthuo , I am glad that you're back. Did you go for your vacation?
I've made a few comments to your contribution.

Hey, @arthuo , I am glad that you're back. Did you go for your vacation?
I've made a few comments to your contribution.

Hello, it's been a long time. Recently, I have focused on the research of vision transformer, which has benefited me a lot.I'm glad we can fight shoulder to shoulder again.

Hey, @arthuo , I am glad that you're back. Did you go for your vacation?
I've made a few comments to your contribution.

Hello, it's been a long time. Recently, I have focused on the research of vision transformer, which has benefited me a lot.I'm glad we can fight shoulder to shoulder again.

That's really cool, mate. I wish I could learn some more about computer science myself, haha.
Merging the PR.


RFP - rpcs3

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL :https://rpcs3.net/download
Direct download URL for the software / installer : https://github.com/RPCS3/rpcs3-binaries-win/releases/download/build-770a607ba5a528338723ebf031bedf85d1f8b61c/rpcs3-v0.0.17-12437-770a607b_win64.7z
Software summary / short description:
Playstation 3 emulator

Package already exists:
https://community.chocolatey.org/packages/rpcs3


bump version to 16.1

Please merge your v16.0 branch into your source branch to get ahead of the merge conflict before completing this PR.


Avoid undefined behaviour with the <ctype.h> functions.

As defined in the C standard:

In all cases the argument is an int, the value of which shall be representable as an unsigned char or shall equal the value of the macro EOF.  If the argument has any other value, the behavior is undefined.

This is because they're designed to work with the int values returned by getc or fgetc; they need extra work to handle a char value.
If EOF is -1 (as it almost always is), with 8-bit bytes, the allowed inputs to the ctype.h functions are:
{-1, 0, 1, 2, 3, ..., 255}.

However, on platforms where char is signed, such as x86 with the usual ABI, code like
char *p = ...;
... isspace(*p) ...

may pass in values in the range:
{-128, -127, -126, ..., -2, -1, 0, 1, ..., 127}.

This has two problems:

Inputs in the set {-128, -127, -126, ..., -2} are forbidden.

The non-EOF byte 0xff is conflated with the value EOF = -1, so even though the input is not forbidden, it may give the wrong answer.

Casting char inputs to unsigned char first works around this, by mapping the (non-EOF character) range {-128, -127, ..., -1} to {128, 129, ..., 255}, leaving no collisions with EOF.  So the above fragment needs to be:
char *p = ...;
... isspace((unsigned char)*p) ...

This patch inserts unsigned char casts where necessary.  Most of the cases I changed, I compile-tested using -Wchar-subscripts -Werror on NetBSD, which defines the ctype.h functions as macros so that they trigger the warning when the argument has type char.  The exceptions are under #ifdef __VMS or #ifdef _WIN32.  I left alone calls where the input is int where the cast would obviously be wrong; and I left alone calls where the input is already unsigned char so the cast is unnecessary.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Although the patch is probably legally not copyrightable we usually do not accept patches of such size with CLA: trivial. Could you please sign a regular CLA?

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

This PR is waiting for the creator to make requested changes but it has not been updated for 30 days.  If you have made changes or commented to the reviewer please make sure you re-request a review (see icon in the 'reviewers' section).

This PR is waiting for the creator to make requested changes but it has not been updated for 61 days.  If you have made changes or commented to the reviewer please make sure you re-request a review (see icon in the 'reviewers' section).

This PR has been closed.  It was waiting for the creator to make requested changes but it has not been updated for 90 days.


Add ability to use transclusion

With this pull request you can use transclusion to make the number editable.

Hi there,
Any chances to get that merged?
Best,
Markus

Looks good, thanks


docs: add new screenshot for jam moonbami

Portfolio Author
MoonbamiOfficial
Portfolio Link?
https://moonbamiofficial.vercel.app/
GitHub Link:
https://github.com/MoonbamiOfficial/dev-portfolio
Tech Stack
Next.js, Node.js, React, Tailwind CSS, MongoDB, Vercel

Thanks for the update @MoonbamiOfficial However, the screenshot is quite large (~600kb). Kindly compress it using compressnow or tinypng.
We like to have screenshots as low in size as possible because of the number of images in the repo. Thanks for understanding :)

I forgot about the compressing part, will do a pr again with a compressed one, thanks!


Repair All

/repair all fixes all your items in your inventory

https://github.com/GamerMJay/BetterRepair/issues/4


chore: Update dependencies

Signed-off-by: Michael Gasch<EMAIL_ADDRESS>

Codecov Report

Merging #101 (0ef3679) into main (8486f1d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #101   +/-   ##
=======================================
  Coverage   36.23%   36.23%
=======================================
  Files           1        1
  Lines          69       69
=======================================
  Hits           25       25
  Misses         42       42
  Partials        2        2

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 8486f1d...0ef3679. Read the comment docs.


Release github-action for Node.js node20

This is an enhancement request for Cypress github-action.
GitHub has now provided support for node20 in their JavaScript Actions environment. See https://github.com/actions/runner/discussions/2704.
What would you like?
A new major version of the Cypress github-action should be released using GitHub's support for Node.js 20 in GitHub JavaScript Actions.
Why is this needed?
Cypress needs to be able to run using Node.js 20 and not be restricted to Node.js 16.
Node.js 16 reaches end-of-life on Sep 11, 2023.
From within github-action, the full functionality of Cypress together with Cypress Cloud integration and test summaries is only available when Cypress is called by github-action using the Cypress Module API. This is the default way that the github-action calls Cypress since the release of github-action@v2. Cypress is called in the context of GitHub's runs.using for JavaScript Actions currently available only as node16.
Other
This enhancement request has a critical dependency on an update to the runs.using for JavaScript Actions environment being provided by GitHub through their actions/runner.
See https://github.com/actions/runner/discussions/2704 for announcement on the availability of node20  support:

From here, we plan to skip over node 18 and hop on the node 20 LTS release. We are currently working on a date to rollout node 20 and have work in-flight to accomplish this. We will update this discussion in the coming weeks with our plans once we finalize them.

Workarounds

The Custom test command option command of github-action can be used to call Cypress from the context of the Node.js version set up in the GitHub runner, for instance using actions/setup-node setting Node.js to 18 or 20, however this usage bypasses many other functions of github-action. It causes many of the other github-action options to be ignored and prevents return of detailed results information from the Cypress run, such as the test summary and resultsUrl. Using command is therefore not a good long-term option.

An alternative to using the Cypress JavaScript Action github-action is to call Cypress from a GitHub workflow directly using run, with the same disadvantage as above.

A further alternative is to call the Cypress Module API from a custom script written in JavaScript and called from a custom GitHub Actions workflow. This can be used in a simple way or the full results can be used and processed as needed.

Edit: Above text edited based on information in https://github.com/actions/runner/discussions/2704 Jul 19, 2023.
Updated again on Aug 15, 2023 based on https://github.com/actions/runner/issues/2619#issuecomment-1679003443.
Further update Aug 17, 2023.

I asked GitHub for their plans some time ago. The latest request is in https://github.com/orgs/community/discussions/58226.

GitHub has announced that GitHub runner release v2.308.0 includes support for node20 and that roll-out has started. This should allow the implementation of this feature request once the rollout has completed.

This feature request is planned for implementation through PR #995. This repo is now using GitHub runner release v2.308.0 which includes node20 support.

@MikeMcC399 looks like it worked!


Support to RGBA with background-color rule

Description

Currently, the rules for applying a background color do not support rgba, only rgb.

@Andres6936 The documentation missed the feature, but it works.

Thx for reporting. 👍🏻

Thanks @1Aron


⚠ Bofrost.es has degraded performance

In 27474cf, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1968 ms

Resolved: Bofrost.es performance has improved in 410de69 after 6 minutes.


Forbid hibernating the Shoot during credential rotation and triggering rotation when the Shoot is waking up

How to categorize this PR?

/area quality ops-productivity
/kind bug
What this PR does / why we need it:
It is not possible to support etcd-encryption key rotation and ServiceAccount signing key rotation for hibernated/hibernating Shoots as shared in https://github.com/gardener/gardener/issues/8155#issuecomment-1607066937.
If the shoot is in waking up and the rotation is triggered, and if the reconciliation is retried, this is also a problem.
This PR adds validation to:

Forbid hibernating a shoot if ETCD encryption key rotation or ServiceAccount signing key rotation is in progress, ie; in Preparing or Completing phase.
Forbid triggering a rotation operation on Shoots which are waking up, ie; status.IsHibernated=true.

Which issue(s) this PR fixes:
Fixes #8155
Special notes for your reviewer:
Release note:

A bug causing the gardenlet to panic when a ETCD encryption key rotation operation is triggered for a hibernated Shoot is now fixed. Now, triggering ETCD encryption key rotation or ServiceAccount signing key rotation is forbidden when the Shoot is in waking up phase.

/cc @ialidzhikov

/lgtm
/approve


Add the possibility to keep the code on the server encrypted at rest to avoid intellectual property leaks to VPS operators

Doesn’t seem to be available atm.
Sockets are encrypted on transmission but the code files sit on the disk unencrypted.
A curious VPS operator can read the disk and have all of my intellectual property.
No bueno.

Use encrypted file system such as fscrypt/eCryptfs/EncFS. I think this is not vs-code's jobs.

Sounds reasonable. Thanks for the advice!


Custom non-letsencrypt certificate

I'd like to have an easy way to use my own certificate (that already contains the key and is the only file needed) which is signed by a real CA and is a non-letsencrypt certificate.

Untested, but this should do the trick:
https://github.com/tomav/docker-mailserver/pull/90

Hi @emazzotta, I'll merge as soon you can confirme it works as expected.
Also, if there are integration can may check everything is working correctly, please add them.
We have currently 45+ tests.
Thank you.

I was able to verify, that the code within my if-statement works as expected.
However, I'm having issues exercising the flow that uses the DMS_SSL variable. This issue persists for "cutom" as well as for your "self-signed" option. Meaning, inside the container I can verify that the DMS_SSL variable is set correctly, but the operations are not executed (I don't even see echo "Adding $(hostname) SSL certificate" in the logs).
Any ideas what the issue could be?

echo "Adding $(hostname) SSL certificate"

This part is inside a if statement, so you probably don't match your requirements.
Try to put another echo just after line 142

Yes, I figured the same :)
I do see echo's before and after the switch cases for DMS_SSL so I probably really don't match the if-statement. However when I open bash inside the docker container and run:
[ -e "/tmp/postfix/ssl/$(hostname)-full.pem" ]; echo $?
I get 0
Any advice?

I suppose you got 0 because /tmp/postfix/ssl/FQDN-full.pem exists :-)
I don't have it and it returns 1.
Tried on an existing file I get 0.
root@mail:/# ls -la /tmp/postfix/ssl/
total 36
drwxr-xr-x 3 1000 1000 4096 Nov  9 14:08 .
drwxr-xr-x 3 1000 1000 4096 Feb 27 16:24 ..
drwxr-xr-x 4 1000 1000 4096 Nov  9 14:08 demoCA
-rw-r--r-- 1 1000 1000 4562 Nov  9 14:08 FQDN-cert.pem
-rw-r--r-- 1 1000 1000 6266 Nov  9 14:08 FQDN-combined.pem
-rw-r--r-- 1 1000 1000 1704 Nov  9 14:08 FQDN-key.pem
-rw-r--r-- 1 1000 1000 1009 Nov  9 14:08 FQDN-req.pem

root@mail:/# [ -e "/tmp/postfix/ssl/$(hostname)-full.pem" ]; echo $?
1

root@mail:/# [ -e "/tmp/postfix/ssl/$(hostname)-req.pem" ]; echo $?
0

That's exactly my point! :)
I have the file: /tmp/postfix/ssl/$(hostname)-full.pem
Therefore the if-statement if [ -e "/tmp/postfix/ssl/$(hostname)-full.pem" ]; then
Should be true and I should have Adding $(hostname) SSL certificate in the logs.
See: https://github.com/emazzotta/docker-mailserver/commit/6bd5c5015af895f98ef38c50778b0519074dd9d4
This is not happening though.

Could you paste here all the things you see between your docker start command and the last line of log (start it in foreground). Thank you.

Nevermind, my mistake, I thought if I built my fork of your repo with my change on dockerhub, I'd have my change integrated, but for some reason, dockerhub built your repo instead of my own (with my dockerhub account). If you accept the pull request it should be all good :)

Good new!
Bt why can't you test before I merge on master. Not really safe, no? ;-)
You can add your fork on your docker hub account or just test locally with an email client.
Think about integration tests.
Thanks.

Yes, you're obviously right, something weird happened, I opened a pull request, but the code change was not reflected in my fork. My bad. That's why my docker build didn't contain the change and I had issues testing it. Will test as soon as docker finished building.

Thanks @emazzotta

Tested and works flawlessly!

Merged.

Thank you @emazzotta.
If you find a way to ass integration test or this part of the code, feel free to PR.


[PE-D][Tester B] No Constraints for tags

Screenshot 2022-10-28 at 4.21.20 PM
Users can input #/compulsory4 as a tag which probably do not make any sense. Can implement a proper regex for tags.

Labels: severity.Low type.FeatureFlaw
original: dr-arrgghh/ped#4

Add regex to filter out unicode characters. Not going to implement magic AI to ensure tags makes sense.

Fixed in #230


[locale] id: Sunday changed to first day of week

Fixes #5370
Sunday changed to first day of week for Indonesia locale.
Fixes done assuming that doy should be changed to 06, as that is the case for most locales where dow is 0.

Coverage remained the same at 88.48% when pulling 4d00676a175f8444eda99af49be7c5feb27d2549 on mantinone:indonesia-sunday into 2259e43cfefe3a4a306ef25f4db37e0824d32d43 on moment:develop.

Thanks!


Expose damage tracking in the API

This adds two new functions to the public API, glfwGetBufferAge() and glfwSwapBuffersWithDamage(), mirroring the EGL extensions EGL_EXT_buffer_age and EGL_KHR_swap_buffers_with_damage, as well as a new GLFWrect struct used by the latter.
These two functions can help efficiency tremendously, especially due to a lower memory bandwidth usage, especially on embedded GPUs:

glfwGetBufferAge() lets the application know when the current buffer was last written to, so that it can avoid a clear and redraw of areas which haven’t changed.
glfwSwapBuffersWithDamage() lets the compositor know which areas it should redraw, so that it can avoid compositing areas which haven’t changed, if it itself tracks the buffer age of its buffers.

Here is a video of PyTouhou patched to use this new API: touhou-damage
I also modified tests/msaa.c to use damage to swap buffers, so that you can test this feature.
Other context APIs might have similar extensions, but I don’t have any way to test them and this can be left for a future changeset.
Another future extension to consider is EGL_KHR_partial_update, which lets the application tell the driver ahead of time which regions it will update, thus avoiding an expensive read back of the entire buffer, especially on tiling GPUs.

Hello linkmauve. Thank you for your contribution, Im super interested in this feature (performance implications for the immediate mode GUIs).  I manage to compile this branch and tested msaa example on two maschines (integrated intel gpu -mesa and nvidia gtx 770 - nvidia drivers) on two different linux distros. They both have necessary extensions but I don't see any differences with thoes spinning white rectangles. I see msaa working but no visual implications of this functions running. I even try to visual myself 8 areas that you compose.

I assumed (x, y, w, h) and now Im even more confused. what i'm doing wrong ? :(


Add support for charging station sockets and authentication tags

Description
Would be great to add support for charging station sockets and authentication methods input.
You can find the whole details about sockets types and properties on the wiki page
Screenshots
No response

Best to open an issue here: https://github.com/openstreetmap/id-tagging-schema/issues 👍

For the issue at hand, how would you think those socket types could be presented in iD? MapComplete has a dedicated theme for this topic and still I find all those values hard to use and understand (example https://mapcomplete.osm.be/charging_stations.html?z=18&lat=45.61047&lon=13.73213&language=en&background=osm#node/9134221645). And the List in MapComplete is quite long and complex https://github.com/pietervdvn/MapComplete/blob/master/assets/layers/charging_station/charging_station.json#L165

Another thing to consider is, that I think I remember from previous discussions in this Repo (when the tagging topics where not split of, yet), that those something:term:something schemas are not supported by the preset system yet / well(?). AFAIK a custom form element would be required for this to work.

Description
Would be great to add support for charging station sockets and authentication methods input.
You can find the whole details about sockets types and properties on the wiki page
Screenshots
No response

<EMAIL_ADDRESS>


Add backup service dashboard

Since the backup service was released it has produced metrics for number of tasks run, task duration, backup size etc. This adds a dashboard visualising these metrics.

Thanks Matt!


Create main.c

MinGW version of NTP Client project by David Lettier
sys/socket.h, netinet/in.h, and netdb.h exchanged with winsock2.h
bzero() exchanged with memset()
bcopy() exchanged with memmove()
write() exchanged with send()
read() exchanged with recv()

Merge from MinGW branch


DateTimePicker disabledDates assign String Array

Hello All,
I'm using bootstrap datetimepicker with my ASP.net MVC5 application.
I'm trying to fetch the dates from DB, create an Array of disabled dates and then pass that array in jquery:-
C#
public String[] disabledDates { get; set; } // This model property gets set from database.
e.g. disabledDates = ["2017-08-29","2017-11-22"];
<script type="text/javascript">     $(function () { var disabledDatesAr =<EMAIL_ADDRESS>$('#scheduleDate').datetimepicker({ useCurrent: false, minDate: new Date(), format: 'DD-MM-YYYY hh:mm A', showTodayButton: true, sideBySide: true, showClose: true,  showClear: true,  toolbarPlacement: 'top', disabledDates: disabledDatesAr }); }); </script>
But the above code doesn't work and DateTimePicker popup getting disabled.
Can anyone please guide me on how to assign this array value to disabled dates?
Thanks in advance.

Hi, I think you should populate the array of JS from the one of your MVC first bacause maybe of the way you're currently doing it is not working, so let's comfirng 2 things first:

does appear a console error?
if you do a console.log to disabledDatesAr what appears?

but for now populate the JS array of this old way and try it:
<script type="text/javascript">
    var myArray = [];
    @foreach (var d in Model.data)
    {
        @:myArray.push("@d");
    }
    alert(myArray);
</script>

Hello William-H-M,
Thanks for your response. I've resolved it using the suggestion provided in following link:-
https://stackoverflow.com/questions/45502237/unable-to-assign-string-array-to-bootstrap-datetimepicker-disableddates


Pagination per_page gets wrong value after calling next()

When using the Pagination and:

setting the max_per_page to a value greater than 100,
setting the per_page to a value greater than 100,
after calling next(), the per_page value gets set to 100 because the max_per_page is not carried into the next page.
e.g.

p = Todo.query.paginate(per_page=110, max_per_page=200)
assert len(p.items) == 110 # it works here
p2 = p.next()
assert len(p.items) == 110 # failed, it brings 100 records only.

Expected behavior: the next page result set should bring the per_page records requested and should not be fixed to 100 records after using the next() function.
Environment:

Python version: 3.7
Flask-SQLAlchemy version: 3.0.3
SQLAlchemy version: 1.4.47

Happy to review a PR.


Service hooks

Is there a feature that allows to configure hooks?
We used hooks on CoreOS to prepare storage environments for some services.
It would be great if we could at least have those:

BeforeStart
AfterStart
OnFailure
BeforeStop
AfterStop

Any word on these very useful hooks?  Looks like it's been planned for quite some time.
I need to de-provision an allocated resource per-container on stop/fail of the container.  Importantly, before it's restarted so that the resource is available for the new container.  Is there a another (or maybe better) way to do this?

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Spelling

Generated by https://github.com/jsoref/spelling f; to maintain your repo, please consider fchurn

After fixing the issue caught by the linter, the tests all pass. Just a couple comments inline

I'll try to get to this sometime this week...

Thanks! Great little tool you have there for fixing up simple spelling mistakes!

@ross looks good to me. Do you think it’s worth squashing down to 1 commit for all the changes?

FWIW, I leave them as individual commits while developing because it makes addressing errors, dropping things which people want to keep, and dealing w/ merge conflicts during rebase much easier.

@ross looks good to me. Do you think it’s worth squashing down to 1 commit for all the changes?

Yeah. The history will remain here if anyone is interested in it and that'll avoid a load of small commits in git log etc.
If you're both happy with the state of it. I'll merge.

Note that I tend to delete my branches, so the individual commits won't last. If you need me not to, I can...

Note that I tend to delete my branches, so the individual commits won't last. If you need me not to, I can...

Pretty sure they'll stick around anyway (thanks to behind the scenes GH magic) so it should be fine to delete.

Loooks good to me!


Icon - MessageCircle color prop

MessageCircle is black no matter what color i pass to it

@BillyG83
MessageCircle seems to be working as expected, i have identified some other icons with this problem (most likely a problem with svg).

@AbhinavMV you are correct it is MessageSquare

I will also fix CheckCircle

and finally i had no idea the color there was there, thats amazing DX dude!

look at my hacked preview, poor input lol


foreign calls should be imported interruptible

https://downloads.haskell.org/~ghc/8.4.1/docs/html/users_guide/ffi-chap.html#interruptible-foreign-calls
But to do so requires interruptible to be added to c2hs, which is this as yet unmerged PR: https://github.com/haskell/c2hs/pull/177

This PR is now merged. Thanks for your patience.


Can't use multiple configs on one page

Describe the bug
I have multiple configs for one page (to be more detailed on a Swagger page). The first one will be executed automatically when the page is loaded to authorize me. The second one will be executed with a hotkey (Ctrl + Shift + X if necessary) and enter data to test REST requests. The automated one will be executed but I can't use the one with the hotkey. If I deactivate the automated one, the other one works. The config order doesn't seem to have an impact.
To Reproduce
Steps to reproduce the behavior:

Create a config to login and let it execute when the page is loaded
Create a config that will be executed with a hotkey
Load the page
the automated config will be executed
Try to execute the hotkey one
No data will be entered in the fields

Expected behavior
I want to have multiple configs with different hotkeys for the page to test with different data.
Desktop (please complete the following information):

OS: Win10
Browser: Chrome
Version 94.0.4606.71 (64-Bit)

EDIT:
The config order has an impact: The one on top/above the other one works.

Can you share some demo configuration

Can you share some demo configuration

login config: https://pastebin.com/EvmkR6bA
data config: https://pastebin.com/KZkhEjM3
I use http://swagger.*.paradise.bsz-rancher.hup.intern/swaggerui/swagger-ui/* in the automated login config as I need the login informations on multiple Swagger with this URL scheme, this URL woks fine. Full URL is http://swagger.p5sdzt1.paradise.bsz-rancher.hup.intern/swaggerui/swagger-ui/index.html?configUrl=/swaggerui/swagger-config.json&urls=&url=http://censored-ip/logistic/calendar/v3/api-docs
The IP is in both configs the same.

not sure understand how i can use same config in another tab ?

nderstand how i can use same config in another tab ?

You can use regular expressions in URLs to match multiple configurations at once. https://getautoclicker.com/docs/3.x/configuration/url/


Working with the bindKnex() cache for multiple versions of same model

This is going to be a tricky one to explain, so bear with me!  At surface value the issue I'm having is that bindKnex() caches models based upon their name and tableName, which means I can't use two separate models with the same instance of knex that have identical name and tableName.
How did I generate this issue?  Well, as you can imagine, if I had this issue in a standalone application I would probably be doing something wrong.  But I'm actually building tooling for others to use via schwifty and the hapi pal ecosystem, with an emphasis on flexible application structure.  To keep it brief: independent areas of an application can define their own models, and we would like to allow for a case where one area of an application might be very generic, while another area more specific.  The generic area uses very minimal models, and the more specific area might extend those models to define its own further validation, lifecycle hooks, relation mappings, etc.  So there may be two models in the application with the same name and tableName, where one is essentially more specific than the other.
I have dug into this problem and have a pretty good understanding of how this is handled inside objection, and it makes perfect sense to me that it works the way it does.  I'm soliciting feedback/thoughts about how to either work with the current behavior, alter the current behavior (I would offer to work on this), or really any other solution I haven't thought of.
I have started working on this by extending the base model to have a more involved uniqueTag().  You can see a draft of this approach here: https://github.com/hapipal/schwifty/commit/c7f0f9381eed2389063ed97afb92045b269cbd8f#diff-a140b60b6a99a8c69f4b5d0d1f1f2bfaR15
This approach is a little tricky—it's never fun to introduce state to keep track of, although of course I can live with it— and I'm not positive if uniqueTag() is fair game to extend, as it's not in documentation (although I see it has been in place for a long while).  The other downside is that this approach doesn't work with plain objection models (rather than the schwifty base class), which I would like to support equally well.
If moving away from uniqueTag() for bindKnex() caching is an option, I have an idea about how that could work, taking advantage of the fact that the unique tag is primarily being used to protect bindKnex() from itself (or, inheritModel()).  But I would like to get some thoughts before jumping there.  For anyone who made it this far, thanks for reading!

Short answer before I have time to read this thoroughly: uniqueTag id fair game! I've just forgotten to document it.

Thanks @koskimas.  I wasn't able to support my "sandboxing" feature for all objection models, but i was able to support it for the schwifty base class, which is good enough for me.  The relevant PR is here for those interested https://github.com/hapipal/schwifty/pull/88


Return itself if an object is an instance of subclass

According to LSP from SOLID, subclasses should preserve the same interface as superclass.
Thus, it's needed to Dry::Struct to return an original subclass instance, not an instance coerced to a superclass.

We need another method for this, returning a subclass instance is not an expected behavior of .new in Ruby.

Then we need to split new method away from [] and call.
[] and call should behave as they behave right now, but new should have previous behaviour.
Do you want me to make that?

would be great :)

@flash-gordon please =)

@flash-gordon any chance to merge?

yes! thank you!


Master reload state

Master now reload the state as any other nodes. This allows the master to pick up changes done by hand to the zookeeper state, as well as the change of roles.

OCD build https://ocd.appscale.com:8080/job/Daily Build/5665/


Backport from 1.20.1 branch

This is backport from 1.20.1 branch (almost same as pull request #48)

Thanks


Issue found on page 'Relational API on Pandas'

Please describe the problem you encountered in the DuckDB documentation and include the "Page URL" link shown below.
Note: only create an issue if you wish to report a problem with the DuckDB documentation. For questions about DuckDB or the use of certain DuckDB features, use GitHub Discussions, Stack Overflow, or Discord.

Page URL: https://duckdb.org/docs/guides/python/relational_api_pandas.html
On the page documentation below, I believe the code references a filter of 'i >=2' which does not exist on the commented out query
# chain together relational operators (this is a lazy operation, so the operations are not yet executed)
# equivalent to: SELECT i, j, i*2 AS two_i FROM input_df ORDER BY i DESC LIMIT 2
transformed_rel = rel.filter('i >= 2').project('i, j, i*2 as two_i').order('i desc').limit(2)

I think it should read as
# chain together relational operators (this is a lazy operation, so the operations are not yet executed)
# equivalent to:SELECT i, j, i*2 AS two_i FROM input_df WHERE i >= 2 ORDER BY i DESC LIMIT 2
transformed_rel = rel.filter('i >= 2').project('i, j, i*2 as two_i').order('i desc').limit(2)

@chandy indeed. Thanks for reporting, I've submitted a PR to fix this.


Reworking category annotation access to avoid issues with some JUnit …

…extensions e.g. JUnitParams

Hi @JorgePCDV please could you add some details around what problem you are trying to solve with this PR?

Hi Anurag,
We are trying to migrate our tests to Atam4j, and we currenlty use listeners to set test identifiers in thread local storage, which we use to improve logging and traceability of the requests that the acceptance tests make.
We tried to implement this using Rules, but for certain tests e.g. JUnitParams tests, this approach does not work. Therefore, our current best option is to use test listeners.
Test listeners are a standard feature of JUnit and it seems like a useful addition to Atam4j.

In some cases Description.getMethodName() does not return a valid Java method name e.g. in a JUnitParams test. In this case, the exception was being caught but the Category annotation was not being successfully read.

Thanks. Merging..


Difference of fit_to_window between python and opset

fit_to_window for opset is resize_image_with_aspect and it has pad as well.
https://github.com/openvinotoolkit/model_api/blob/41c20267122bed9fe9b21631166d15818f669379/model_api/python/model_api/adapters/utils.py#L358-L367
But, fit_to_window for python is resize_image_with_aspect_ocv and it doesn't have pad. It just does resize keeping aspect ratio.
https://github.com/openvinotoolkit/model_api/blob/41c20267122bed9fe9b21631166d15818f669379/model_api/python/model_api/adapters/utils.py#L427-L430
I'd like to know if it is intended.

Not intended. But OpenCV version isn't used anywhere. It was left as a reference implementation. Apparently it diverged. Feel free to submit a fix and optionally a test. The test could create a dummy model without weights which does resize only.


Is there a way to backup and restore the configuration

After spending some time to put in everything I'm wondering if I'm missing a away to back up the configuration so that in case something crashes I can restore it.
If someone could point me in the right direction I would appreciate it.
Thanks

Currently there's no such way provided by the extension itself.
However, considering the extension can be installed from an unpacked directory, the default config is located in that directory.
So you can make changes to that config directly and try reloading the page, I think startpage would pick up the changes.
That just means you can basically backup the config from the directory where you unpacked the extension and then put it in any other device (where the extension is unpacked) and it will work like the way you want it to.

Thanks.. I'll try that. If I had to reconfigure this after setting it up it would definitely promote me to find something else. So far I'm really liking it.

@JoshFink The import/export button support is added in this commit: 0f6573f. You can try it out if you want.
The feature will be live soon in the next release along with some other useful new features!

@JoshFink The feature is now live at: https://github.com/deepjyoti30/startpage/releases/tag/1.1


Emitting errors through the browserify transform

So this might be a long shot and may not be related to Vueify, BUT I usually get errors in the console for the rest of the stack so here it goes.
I'm using a gulp task with browserify:
gulp.task('js', () => {
  return browserify(paths.app)
    .transform('babelify')
    .transform('vueify')
    .bundle()
    .pipe(source('app.js'))
    .pipe(convertStream())
    .pipe(sourcemaps.init())
    .pipe(sourcemaps.write())
    // When not in dev minify the JS (also removes source maps)
    .pipe(gulpif(!envIsDev, uglify()))
    .pipe(gulp.dest(paths.dist))
    .pipe(browserSync.stream())
})

This works really well with your example on how to run Vueify + Browserify + Node (in this case gulp). However, I made a dumb and funny mistake in my app.vue. I had put exports {} not export {}. I would expect some build/compile error, but instead the task sits at Starting 'js'... and never finishes.

Hmm, maybe this has to do with gulp, because vueify does emit compilation errors (and it's working fine when used with watchify).

Will dig further into the gulp tasks. Thanks for the confirmation - will reopen if I find evidence of it relating to Vueify specifically.

So if anyone else ever lands here, this is my current - albeit not amazing solution:

Grab gulp-util
use .on('error', gutil.log) on any plugin, or pipe in your task:

    .transform('babelify').on('error', gutil.log)
    .transform(vueify).on('error', gutil.log)
    .bundle().on('error', gutil.log)
    .pipe(source('app.js').on('error', gutil.log))

Once I got my error into the terminal, I fixed the issue and removed them and added a comment above the task in case it happens again. My specific error was due to:
[Error: Cannot find module 'node-sass' while parsing file: **redacted**/src/components/autocomplete.vue]
  code: 'MODULE_NOT_FOUND',

node-sass was grabbed by Vueify, but I found that explicitly installing it with --save-dev fixed the issue as well.


Remove Decentraland Library step from Editor

When adding a dependency via the Decentraland Editor SDK7, you're asked if "is this a Decentraland library"
the distinction made sense on SDK6 and is still needed there, but it's not needed on SDK7. We should not install libraries as bundle dependencies anymore
We should remove that step from the process, as it can cause confusion

Closed by https://github.com/decentraland/editor-sdk7/pull/72


require(...*.graphql) doesn't work in angular cli generated project

Hey,
I am trying to apply your tutproial with a project that I created using the angular cli.
Most of it is fine but I have 2 problems.
Here is nr. 1 I will add nr. 2 in a second issue.
const UsersQueryNode: DocumentNode = require('graphql-tag/loader!../graphql/Users.graphql');

does not work for me, the TS compiler says:

Cannot find name 'require'.

Not sure what the problem here is, I added the @types/node to the tsconfig.

hi,
seems you don't have require typings. try installing @types/node.
anyway, I am working with angular CLI project and I haven't encountered any problem.

@eitanfr I had already added @types/node to the package.json. Do I need to import the "require" somewhere else?

Maybe you have a wrong tsconfig settings ,
Try adding "types": ["node"] to the compilerOptions in the tsconfig.app.json

@eitanfr thanks, that solved the issue.

This works fine, but the webpack (Angular CLI) still logs the error on console. Any suggestions to fix that?


Stringify request body fix for #154

This PR is to fix #154 by stringifying everything rather than just objects.
NB. I can't create a valid test as Karma only accepts strict JSON objects and not lone JSON strings.

This change is

None of this will work if the type isn't an object. For that reason I don't think this PR solves anything. What was the idea?

@RWOverdijk see issue above

not really. the PR JSON.stringify when the body isn.t an Object which makes no sense

a string is not a valid JSON http://www.json.org/


Implement custom resampling command line args

This change implements -resample X Y command line support in addition to
-resample_factor, when a more sophisticated algorithm is needed to
compute the desired image size.
For example, these can be used to round the image to a multiple of 4 or
to a power of 2 for improved compatibility with various graphics APIs.
Fixes #224.

Got it, thank you!