[SAGE-352] Grid add fixed column width

Description

[x] add ability for the Grid to have a fixed width column. The parent grid should allow for the natural width of the children to determine the width

Screenshots

Testing in sage-lib

Go the Grid views and resize the browser to verify that Variable Width variation works as expected:

Rails
React

Testing in kajabi-products

(LOW) Adds new Grid property. Has no affect in the app

Related

Closes SAGE-352

Closing in favor of this PR, #1375


Password is not present

Password input is not present

Sir we not need of password it sends OTP to authenticate the user


Ingress proxy / service mesh guid:x-request-id not compatible with Jaeger UI

Hey,
I am trying to trace requests from our monitoring system through Jaeger, after following the instructions on installation.  In my monitoring system, I am setting x-request-id on the request, which appears to be being reflected in Jaeger as guid:x-request-id:

However you're unable to search for guid:x-request-id in the Jaeger gui due to the colon, therefore you cannot filter by request id.  As you can see from the Jaeger gui code, they can't handle colons.
https://github.com/jaegertracing/jaeger/blob/master/cmd/query/app/query_parser.go#L190

@objectiser ^^^

This is a Jaeger issue, so could close this - although you might want to keep it open until fixed in case other users find the same problem?

I think it makes sense to keep it open, I came here first looking for answers before I spoke with the jaeger devs!

Unless there is something we can do in Istio to help with this issue, let's close this.

Some work has been done in Jaeger to address this:

jaegertracing/jaeger#550
jaegertracing/jaeger-ui#145

The change is to use logfmt for tag matching in the search form.
The changes are done, but not yet released.
cc @yurishkuro, @objectiser


Fix race condition in allocator fuzz-test

Introduce a flag 'block' to prevent an address from being freed during re-test.
Fixes #802

LGTM


Add low poly hands with arms

Pull Request Templates
Switch template by going to preview and clicking the link - note it not work if you've made any changes to the description.

default.md - for contributions to stable packages.
lightweight.md - for contributions to pre-release/preview packages use the lightweight merge request template. The quality threshold for reviewing is lower - it prioritizes a lean review process.
release.md - for release merge requests.

You are currently using: default.md
Note: these links work by overwriting query parameters of the current url. If the current url contains any you may want to amend the url with &template=name.md instead of using the link. See query parameter docs for more information.
Summary
Adding low poly hands with arms and adding them to the standard rigged hands example scene
Contributor Tasks
These tasks are for the merge request creator to tick off when creating a merge request.

[ ] Pair review with a member of the QA team.
[ ] Add any release testing considerations to the MR for the next release.
[ ] Check any relevant CHANGELOG files have been updated.
[ ] Ensure documentation requirements are met e.g., public API is commented.
[ ] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
[ ] Add any relevant labels such as breaking to this MR.
[ ] If this MR closes a Jira issue, make sure the fix version on the JIRA issue is set to the correct one.

Reviewer Tasks
Add any instructions or tasks for the reviewer such as specific test considerations before this can be merged.
Use emojis in review threads to communicate intent and help contributors.

[ ] Code reviewed.
[ ] Non-code assets e.g. Unity assets/scenes reviewed.
[ ] Documentation has been reviewed. Includes checking documentation requirements are met and not missing e.g., public API is commented.
[ ] Checked and agree with release testing considerations added to MR for the next release.

Closes JIRA Issue
If this MR closes any JIRA issues list them below in the form Closes PROJECT-#

Lack of a face on the end of the arm feels wrong?

mesh scaling doesn't seem to be working for them - my finger tips are quite far apart when I touch them together
https://user-images.githubusercontent.com/17143693/179464181-7e2bee10-2f11-4103-9331-d20bf0086ef2.mp4

The material assigned to the mesh is a different one to Low Poly Hands

URP & HDRP scenes should be fine with the old low poly materials :)

Testing that I have done:

new hands work

elbow follows elbow tracking data
the hand model looks right from all sides and in different poses

hands are part of the example scenes and work there

all three rigged hands example scenes include the new hands
hands look good in URP and HDRP

hand scaling works

the standard tests we do for hand scaling pass (eg. changing the scale offset, changing fingertip offsets, enabling / disabling scale)

@Greg-UL  Is there anything else that you think needs to be tested before this is merged?

Testing that I have done:

new hands work

elbow follows elbow tracking data
the hand model looks right from all sides and in different poses

hands are part of the example scenes and work there

all three rigged hands example scenes include the new hands
hands look good in URP and HDRP

hand scaling works

the standard tests we do for hand scaling pass (eg. changing the scale offset, changing fingertip offsets, enabling / disabling scale)

@Greg-UL Is there anything else that you think needs to be tested before this is merged?

Is this working alright across Unity versions too?
Can we activate deactivate the elbow tracking whilst using the arm models?
What's the interaction like for switching showArm like? Pre editor preview mode switch on/off, during editor preview mode on/off.
How does the model react to losing elbow tracking?
Model in different positions - Elbows close to the face, outstretched arms, arms close to body.

@Greg-UL

Is this working alright across Unity versions too?

tested on Unity 2020 and Unity 2021

Can we activate deactivate the elbow tracking whilst using the arm models?

You can toggle showArm while using the model, and the arm will disappear / reappear

What's the interaction like for switching showArm like? Pre editor preview mode switch on/off, during editor preview mode on/off.

Video here: https://ultrahaptics.box.com/s/okldmyjl9k633sjx5aumqtgzhdeav5rw

How does the model react to losing elbow tracking?

I don't think it's possible to lose elbow tracking? The elbow will be tracked if the hand is tracked. And if the hand isn't tracked anymore, the HandEnableDisable script will disable the hand model

Model in different positions - Elbows close to the face, outstretched arms, arms close to body.

Can also be seen on video here: https://ultrahaptics.box.com/s/okldmyjl9k633sjx5aumqtgzhdeav5rw

@Greg-UL

Is this working alright across Unity versions too?

tested on Unity 2020 and Unity 2021

Can we activate deactivate the elbow tracking whilst using the arm models?

You can toggle showArm while using the model, and the arm will disappear / reappear

What's the interaction like for switching showArm like? Pre editor preview mode switch on/off, during editor preview mode on/off.

Video here: https://ultrahaptics.box.com/s/okldmyjl9k633sjx5aumqtgzhdeav5rw

How does the model react to losing elbow tracking?

I don't think it's possible to lose elbow tracking? The elbow will be tracked if the hand is tracked. And if the hand isn't tracked anymore, the HandEnableDisable script will disable the hand model

Model in different positions - Elbows close to the face, outstretched arms, arms close to body.

Can also be seen on video here: https://ultrahaptics.box.com/s/okldmyjl9k633sjx5aumqtgzhdeav5rw

Thanks Julia - that's brilliant.
All good from my perspective.


Use JSDOM document as input and output to avoid reserialization

This is similar to #7, but the fix in there doesn't cover my use case. I have a long chain of processing that passes around a JSDOM document. Before mathjax-node-page, I serialize to a string to pass it to JSDOM, then after, I parse the mathjax-node-page output to get a JSDOM document. This seems a bit silly considering mathjax-node-page is operating on a JSDOM document.
I want to be able to provide a complete JSDOM document as input, and receive a JSDOM document as output. Ideally, just modified in place for best performance.

Definitely a good idea but I don't plan to work on this any time soon.
Happy to review a PR.

Also, if this ideas comes from your work on arxiv-vanity, then I suspect it might be easier to write your own wrapper around mathjax-node -- just picking up LaTeXML-specific markup etc.


Show return type on hover

It would be nice if you could hover over return types that are too long to be shown, or otherwise see the information. See, e.g. the variables "rules" on the page at  http://jacobr.sea.corp.google.com:8000/web/out/index.html#!{"id":"serialization/Reader"}

return type is visible in new dartdoc


Prisma Client/Query Engine is giving me this error "Cannot create property 'clientVersion' on boolean 'true'"

Bug description
Hello. The prisma client/query engine is giving the following error. If anyone has encountered this issue before then please help me out. Thanks in advance.
{
  "level": 50,
  "time":<PHONE_NUMBER>709,
  "pid": 6,
  "stack": "TypeError: Cannot create property 'clientVersion' on boolean 'true'\n    at cb (/app/node_modules/@prisma/client/runtime/index.js:35953:25)\n    at processTicksAndRejections (internal/process/task_queues.js:95:5)",
  "type": "Error",
  "msg": "Cannot create property 'clientVersion' on boolean 'true'",
  "correlationId": "e676c591-889c-41b4-a1db-5b3d8b32d139"
}

How to reproduce

My application is an express.js application. One of the endpoints has the following code block.

    const count = await prisma.content.count({
      where: {
          tags: {
            hasSome: ['Women],
          },
        publishedAt: { gt: "2021-04-12T00:00:00-0400", lt: "2021-08-13T03:16:05-04:00" },
      },
    });

When I hit the above endpoint, I'm getting an error with the following logs.

2021-08-14T22: 45: 44.703Z prisma:client Prisma Client call: 2021-08-14T22: 45: 44.705Z prisma:client prisma.content.aggregate({
 where: {
   tags: {
     hasSome: [
       'Women'
     ]
   },
   publishedAt: {
     gt: '2021-04-12T00: 00: 00-0400',
     lt: '2021-08-13T03: 16: 05-04: 00'
   }
 },
 select: {
   _count: {
     select: {
       _all: true
     }
   }
 }
})
2021-08-14T22: 45: 44.705Z prisma:client Generated request: 2021-08-14T22: 45: 44.705Z prisma:client query {
 aggregateContent(where: {
   tags: {
     hasSome: [
       "Women"
     ]
   }
   publishedAt: {
     gt: "2021-04-12T00:00:00-0400"
     lt: "2021-08-13T03:16:05-04:00"
   }
 }) {
   _count {
     _all
   }
 }
}

2021-08-14T22: 45: 44.708Z prisma:engine { cwd: '/app/node_modules/.prisma/client'}
2021-08-14T22: 45: 44.709Z prisma:client:fetcher true
{
 "level": 50,
 "time":<PHONE_NUMBER>709,
 "pid": 6,
 "errorMessage": "Cannot create property 'clientVersion' on boolean 'true'",
 "correlationId": "e676c591-889c-41b4-a1db-5b3d8b32d139"
}
{
 "level": 50,
 "time":<PHONE_NUMBER>709,
 "pid": 6,
 "stack": "TypeError: Cannot create property 'clientVersion' on boolean 'true'\n    at cb (/app/node_modules/@prisma/client/runtime/index.js:35953:25)\n    at processTicksAndRejections (internal/process/task_queues.js:95:5)",
 "type": "Error",
 "msg": "Cannot create property 'clientVersion' on boolean 'true'",
 "correlationId": "e676c591-889c-41b4-a1db-5b3d8b32d139"
}

Expected behavior
The Prisma client/query engine should work without any issues.
Prisma information
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Content {
  id           Int          @id
  title        String
  url          String
  thumbnailUrl String?      @map("thumbnail_url")
  publishedAt  String       @map("published_at") @db.VarChar(36)
  type         ContentType?
  tags         String[]

  @@map("content")
}

enum ContentType {
  blogs     @map("BLOGS")
  videos    @map("VIDEOS")
  docs      @map("DOCS")
  social    @map("SOCIAL")
  custom    @map("CUSTOM")
  targeted  @map("TARGETED")

  @@map("content_type")
}

Environment & setup

OS: Debian
Database: PostgreSQL
Node.js version: v14.16.0

Prisma Version
prisma               : 2.29.0
@prisma/client       : 2.29.0
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine 1be4cd60b89afa04b192acb1ef47758a39810f3a (at<EMAIL_ADDRESS>Migration Engine     : migration-engine-cli 1be4cd60b89afa04b192acb1ef47758a39810f3a (at<EMAIL_ADDRESS>Introspection Engine : introspection-core 1be4cd60b89afa04b192acb1ef47758a39810f3a (at<EMAIL_ADDRESS>Format Binary        : prisma-fmt 1be4cd60b89afa04b192acb1ef47758a39810f3a (at<EMAIL_ADDRESS>Default Engines Hash : 1be4cd60b89afa04b192acb1ef47758a39810f3a
Studio               : 0.419.0

clientVersion should only be read or filled when you actually have an error, so this might be an error while creating an error message - something will try to reproduce with the code you provided.

Thanks for the reply @janpio. Now I'm facing a different issue after I started using napi preview feature in prisma.schema file.
2021-08-15T20:19:38.960Z prisma:client:libraryEngine sending request, this.libraryStarted: false
2021-08-15T20:19:38.962Z prisma:client:fetcher TypeError: Cannot read property 'message' of undefined
    at LibraryEngine.request (/app/node_modules/@prisma/client/runtime/index.js:24476:101)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async cb (/app/node_modules/@prisma/client/runtime/index.js:35913:26)

@pantharshit00 Did you get a chance to look into this issue? I'm kind of blocked with this issue. It would really be helpful for me if you can look into this issue.

Is this still reproducible in a recent version of Prisma @provHarshaKommanaboyina?

@provHarshaKommanaboyina this error should be resolved with our later versions of Prisma client. I'm going to close it but please open again if you are still getting the error.


Document not reflecting AAD management page

I am trying to put together an Web-App that uses SSO following this document,
However I cannot find the Manage tab in AAD Admin to add the API
Help please!

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

ID: 52221dd3-95ec-96b9-1da8-9478527c2602
Version Independent ID: 32e9c2d8-733d-0865-2ea3-727d8684a10d
Content: Single Sign-On - Teams
Content Source: msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
Product: msteams
GitHub Login: @laujan
Microsoft Alias: lajanuar

@eilmrein You could see the Manage tab on the overview page after you have created the AAD app.


OSX desktop app's TE details window is cut off

osx_native_app/7.2.150
I try to update the project and client fields, but now the desktop client looks like the attached screenshot OS X Yosemite. The Project field is cut off.

Desk case #176583

cannot reproduce on OS X Yosemite (10.10.5)


Error in build while taking release APK

flutter --version
Flutter 3.13.9 • channel [user-branch] • unknown source
Framework • revision d211f42860 (6 months ago) • 2023-10-25 13:42:25 -0700
Engine • revision 0545f8705d
Tools • Dart 3.1.5 • DevTools 2.25.0

flutter doctor -v
[!] Flutter (Channel [user-branch], 3.13.9, on Microsoft Windows [版本 10.0.22631.2792], locale zh-Hans-HK)
    ! Flutter version 3.13.9 on channel [user-branch] at D:\flutter_windows_3.13.9-stable\flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at
      https://flutter.dev/docs/get-started/install.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
    • Framework revision d211f42860 (6 months ago), 2023-10-25 13:42:25 -0700
    • Engine revision 0545f8705d
    • Dart version 3.1.5
    • DevTools version 2.25.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly
      to perform update checks and upgrades.

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\Administrator\AppData\Local\Android\sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-10027231)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop Windows apps (Visual Studio Build Tools 2019 16.11.31)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
    • Visual Studio Build Tools 2019 version 16.11.34114.132
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 2022.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-10027231)

[✓] Connected device (4 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 12 (API 31) (emulator)
    • Windows (desktop)            • windows       • windows-x64    • Microsoft Windows [版本 10.0.22631.2792]
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 123.0.6312.107
    • Edge (web)                   • edge          • web-javascript • Microsoft Edge 123.0.2420.97

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

flutter build apk --release (Error section)
Task :app:compileFlutterBuildRelease FAILED
[   +1 ms] :app:compileFlutterBuildRelease (Thread[Execution worker Thread 5,5,main]) completed. Took 7.799 secs.
[        ] FAILURE: Build failed with an exception.
[        ] * What went wrong:
[        ] Execution failed for task ':app:compileFlutterBuildRelease'.
[        ] > Process 'command 'D:\flutter_windows_3.13.9-stable\flutter\bin\flutter.bat'' finished with non-zero exit
value 1
[        ] * Try:
[        ] > Run with --debug option to get more log output.
[        ] > Run with --scan to get full insights.
[        ] * Exception is:
[        ] org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:compileFlutterBuildRelease'.
[        ]      at
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.ja
va:142)
[        ]      at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282)
[        ]      at
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:140)
[        ]      at
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:128)
[        ]      at
org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
[        ]      at
org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
[   +1 ms]      at
org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:5
1)
[   +1 ms]      at
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
[        ]      at
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
[        ]      at
org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
[        ]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
[        ]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
[        ]      at
org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRun
ner.java:204)
[        ]      at
org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRun
ner.java:199)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
[        ]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
[        ]      at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:69)
[        ]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.jav
a:327)
[        ]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.jav
a:314)
[        ]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecution
Graph.java:307)
[        ]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecution
Graph.java:293)
[        ]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:417)
[        ]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:339)
[        ]      at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
[        ]      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
[        ]      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[        ]      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[        ]      at java.base/java.lang.Thread.run(Thread.java:833)
[        ] Caused by: org.gradle.process.internal.ExecException: Process 'command
'D:\flutter_windows_3.13.9-stable\flutter\bin\flutter.bat'' finished with non-zero exit value 1
[        ]      at
org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:415)
[        ]      at org.gradle.process.internal.DefaultExecAction.execute(DefaultExecAction.java:38)
[        ]      at org.gradle.process.internal.DefaultExecActionFactory.exec(DefaultExecActionFactory.java:202)
[        ]      at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1171)
[        ]      at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1166)
[        ]      at org.gradle.api.Project$exec$9.call(Unknown Source)
[        ]      at BaseFlutterTask.buildBundle(flutter.groovy:1297)
[        ]      at BaseFlutterTask$buildBundle.callCurrent(Unknown Source)
[        ]      at FlutterTask.build(flutter.groovy:1422)
[        ]      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[        ]      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
[        ]      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[        ]      at java.base/java.lang.reflect.Method.invoke(Method.java:568)
[        ]      at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:125)
[        ]      at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
[        ]      at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
[        ]      at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
[        ]      at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:236)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68)
[        ]      at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:221)
[        ]      at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:204)
[        ]      at
org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:187)
[        ]      at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:165)
[        ]      at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:89)
[        ]      at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:40)
[        ]      at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:53)
[        ]      at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:50)
[        ]      at
org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRun
ner.java:204)
[        ]      at
org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRun
ner.java:199)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
[        ]      at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:50)
[        ]      at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:40)
[        ]      at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:68)
[        ]      at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:38)
[        ]      at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:41)
[        ]      at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:74)
[        ]      at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)
[        ]      at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:51)
[        ]      at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:29)
[        ]      at
org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.executeDelegateBroadcastingChanges(CaptureStateAfterE
xecutionStep.java:124)
[        ]      at
org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:80)
[        ]      at
org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:58)
[        ]      at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:48)
[        ]      at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:36)
[        ]      at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:181)
[        ]      at org.gradle.internal.execution.steps.BuildCacheStep.lambda$execute$1(BuildCacheStep.java:71)
[        ]      at org.gradle.internal.Either$Right.fold(Either.java:175)
[        ]      at org.gradle.internal.execution.caching.CachingState.fold(CachingState.java:59)
[        ]      at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:69)
[        ]      at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:47)
[        ]      at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:36)
[        ]      at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:25)
[        ]      at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:36)
[        ]      at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:22)
[        ]      at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:110)
[        ]      at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:56)
[        ]      at java.base/java.util.Optional.orElseGet(Optional.java:364)
[        ]      at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:56)
[        ]      at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:38)
[        ]      at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:73)
[        ]      at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:44)
[        ]      at
org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep
.java:37)
[        ]      at
org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep
.java:27)
[        ]      at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:89)
[        ]      at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:50)
[        ]      at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:114)
[        ]      at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:57)
[        ]      at
org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:76)
[        ]      at
org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:50)
[        ]      at
org.gradle.internal.execution.steps.SkipEmptyWorkStep.executeWithNoEmptySources(SkipEmptyWorkStep.java:254)
[        ]      at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:91)
[        ]      at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:56)
[        ]      at
org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:32)
[        ]      at
org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:21)
[        ]      at
org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.j
ava:38)
[        ]      at
org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:43)
[        ]      at
org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:31)
[        ]      at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:40)
[        ]      at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:281)
[        ]      at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:40)
[        ]      at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:30)
[        ]      at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:37)
[        ]      at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:27)
[        ]      at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:44)
[        ]      at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:33)
[        ]      at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:76)
[        ]      at
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:139)
[        ]      at
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:128)
[        ]      at
org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
[        ]      at
org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
[        ]      at
org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:5
1)
[        ]      at
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
[        ]      at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
[        ]      at
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
[        ]      at
org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
[        ]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
[        ]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
[        ]      at
org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRun
ner.java:204)
[        ]      at
org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRun
ner.java:199)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
[        ]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
[        ]      at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:69)
[        ]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.jav
a:327)
[        ]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.jav
a:314)
[        ]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecution
Graph.java:307)
[        ]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecution
Graph.java:293)
[        ]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:417)
[        ]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:339)
[        ]      at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
[        ]      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
[        ]      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[        ]      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[        ]      at java.base/java.lang.Thread.run(Thread.java:833)
[        ] * Get more help at https://help.gradle.org
[        ] BUILD FAILED in 11s

Hi @JuYiYang, you are using an older version of flutter. Kindly upgrade to the latest version of flutter stable (3.19.5) to see if you still experience this issue. You might need to modify your build.gradle file. See https://docs.flutter.dev/release/breaking-changes/flutter-gradle-plugin-apply
If you still experience this issue after the upgrade, kindly provide the full crash log in a .log or .txt file along with your android/build.gradle, android/app/build.gradle & settings.gradle files.
Thank you

Is there a way to not upgrade the SDK? Since I am maintaining this project, I am not sure what will cause the upgrade, as it is normal for the project to be packaged under another employee's computer (macbook).

We will need the full out of flutter build apk -v to determine where the issue is coming from, maybe then we could offer a solution.
Please provide the full output of flutter build apk -v in a .txt or .log file and not only the error, it is likely something is going wrong before the error you posted above.

I replaced a computer to re-package the project, and found that it could be normally packaged, but it would report some kotlin errors

The kotlin warnings are largely harmless, you can see how to fix similar issues by following https://stackoverflow.com/questions/67448034/module-was-compiled-with-an-incompatible-version-of-kotlin-the-binary-version.
If you are able to build the apk successfully on a different issue, that suggests that there might be something wrong with the gradle cache on the laptop you were using initially, without further logs, we can't do much to assist.

Now I can't find any complete log, I suspect it is the problem of flutte downgrade version, I downgraded from 3.19.3 to 3.13.9 on the original computer, may be cached after the downgrade?

You can always get the logs by running the flutter build apk -v command. You can also try clearing your .pub-cache and your .gradle caches to see if it helps

emm,How do I know which version of kotlin my project needs when my console keeps reporting kotlin errors

You can always get the logs by running the flutter build apk -v command. You can also try clearing your .pub-cache and your .gradle caches to see if it helps


Fancy box not render image correctly when image resolution is too large

I'm using Redmine version 3.1.1
The preview is okay but not for popup. look like it's not render correctly.
http://i.imgur.com/cKHDU9U.png

What is the size of the image?

It's 2160 × 1176

Unfortuantely, I cannot reproduce with Redmine 3.1.3 and plugin version 0.2.4.
Neither in Chrome nor in Firefox on a Retina MacBook.
This is how it looks in Chrome: Resized as it should be...

Which plugin version do you use? Are you running the latest v0.2.4? Can you upgrade your Redmine to at least 3.1.3?

I upgrade it to latest version. and it's work just fine. Thank you ;-)


Stop mangling duplicate columns. Fix #736

This makes it so pandas no longer mangles duplicate columns, allowing for proper duplicate column checks.

ping @squirrelo


Could it be possible to take control of the user's own browser instead?

Some websites have a CAPTCHA mechanism that is repeated, while Playwright already has a feature to take control of the user's own browser (e.g., by launching the Chrome browser through the command line in CMD terminal as follows:
cd C:\Program Files\Google\Chrome\Application && chrome.exe \
--remote-debugging-port=9222 \
--user-data-dir=“C:\playwright\user_data”

Can crawl4ai support this? This would significantly reduce the need to write code to handle CAPTCHAs, and it would be great if this functionality could be implemented!

Hi @BZBY thank you so much for the suggestion, I really appreciate it. I've implemented the changes - see the code below. There's a new flag that allows the Chromium browser to run in control of the user's own browser, similar to your suggestion. It also accepts a specific user data directory, offering a lot of possibilities. For example, you can copy and paste part of your current user data into this folder and then pass it. I've tested this on a few websites that were previously challenging to crawl, and it's now easier.
This makes sense, as it's the user's own browser. Additionally, you can set the browser type, and the printing system automatically detects whether you're running on a Mac, Windows, or Linux. Since I'm on a Mac, I haven't tested on Windows yet - maybe you can try that.
These changes are in the 0.3.73 branch, and I'll push them to the new version soon. Thanks again for the suggestion. I wouldn't have thought of it. If you'd like, I'd love to invite you to our Discord to work with us and suggest more improvements for the engine.
import asyncio
from crawl4ai import AsyncWebCrawler

async def main():
    async with AsyncWebCrawler(
        headless=True, # Set to False to see what is happening
        use_managed_browser=True,
        browser_type="chromium",
    ) as crawler:
        result = await crawler.arun(
            url="https://crawl4ai.com",
            bypass_cache=True,
        )
        print(result.markdown)

if __name__ == "__main__":
    asyncio.run(main())

@BZBY You are most welcome, and please share your email address then I send the invitation link, perhaps you can start to help by testing this new features.

@unclecode OK,I’m already testing the new features. my email<EMAIL_ADDRESS>

@BZBY already sent, welcome :)

hey this is on the docker / rest api version?
meaning if im running that can i connedt to my ip via chrome debug mode websocker or puppeteer ?

Hi @rdvo! Yes, you absolutely can connect to your local Chrome browser from the Docker container. We're adding remote browser support in version 0.3.743 (releasing very soon) which will make this even easier.
Here's how you can do it:
request = {
    "urls": "your-url-here",
    "priority": 8,
    "crawler_params": {
        "use_managed_browser": True,
        "browser_kwargs": {
            "host": "host.docker.internal",  # This resolves to your host machine from Docker
            "debugging_port": 9222  # Your Chrome debug port
        }
    }
}

# Submit to the API
response = requests.post("http://localhost:11235/crawl", json=request)

Just make sure to:

Start Chrome with remote debugging enabled:google-chrome --remote-debugging-port=9222

If you're on Linux, you may need to add --add-host=host.docker.internal:host-gateway to your Docker run command

This way you can keep your browser running locally while letting the containerized crawler connect to it. Let me know if you need any help setting this up!
Note: If you don't see these options in the current version, they'll be available in 0.3.743 which is landing very soon.


Revert NULL_HASH, NULL_PUBLIC_KEY, NULL_SECRET_KEY

Fix https://github.com/qwertycoin-org/qwertycoin/issues/117
exiting without message

@exploshot please try this Fork on your System.


Add PodAnnotations feature

Proposed changes
Pod annotations are not available for all deployment with splunk-connect, I added the possibility to set a pod annotations for all daemon set and deployment. This is very usefull if you have for instance istio and you want to disable the istio side-car injection.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[X ] I have read the CONTRIBUTING doc
[X] I have read the CLA
[X] I have added necessary documentation (if appropriate)
[X] Any dependent changes have been merged and published in downstream modules

Anyone can re-run the build_test, it's not related to my changes.

re-running. I had to enable sharing environment variable. I recently added it for ruby version.


Polyline is not rendered on android

Summary
My APP must draw a polyline while the user moves. However, nothing is drawn (Android only. iOS works as expected).
This is the code snippet where I add new coordinates to the latLongs vector every 5 seconds:
    //Tracking GPS
    useEffect(() => {
        if (timer - lastUpdate > 5 || latLongs.length <= 0) {
            Geolocation.getCurrentPosition(
                position => {
                    if (position && position.coords) {
                        let locationCoordinates = {
                            latitude: position.coords.latitude,
                            longitude: position.coords.longitude,
                            altitude: position.coords.altitude,
                            timestamp: +new Date(),
                        }
                        setLatLongs([...latLongs, locationCoordinates]);
                        MonitorStorage.saveLocationCoordinates(locationCoordinates);
                        lastUpdate = timer;
                    }
                },
                error => console.log(error),
                { enableHighAccuracy: Platform.OS == "ios" ? true : false, timeout: 5000 }
            );
        }
    }, [timer]);

The components are arranged in this way:
             <MapView
                    provider={PROVIDER_GOOGLE}
                    showsUserLocation={true}
                    region={{
                        latitude: (latLongs[latLongs.length - 1] || {}).latitude || 0,
                        longitude: (latLongs[latLongs.length - 1] || {}).longitude || 0,
                        latitudeDelta: 0.0043,
                        longitudeDelta: 0.0043,
                    }}
                    style={activityStyles.map}
                >
                   <Polyline coordinates={latLongs} strokeWidth={7} strokeColor="rgba(36, 110, 246, 0.7)" />
                </MapView>

Environment info
    "react-native-maps": "0.27.1"

react-native info output:
System:
    OS: macOS 10.15.6
    CPU: (4) x64 Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz
    Memory: 72.38 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.22.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.7 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 14.2, DriverKit 20.0, macOS 11.0, tvOS 14.2, watchOS 7.1
    Android SDK:
      API Levels: 23, 25, 26, 27, 28, 29, 30
      Build Tools: 26.0.2, 27.0.0, 28.0.3, 29.0.0, 29.0.2, 29.0.3, 30.0.2
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>58069
    Xcode: 12.2/12B45b - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5
  npmGlobalPackages:
    react-native-cli: 2.0.1

Steps to reproduce
1 - Add a map and a polyline;
2 - Update the coordinate vector at run time.
##Expected behavior:
The polyline is rendered normally while the user is moving.
iOS example:

##Currently happening:
Android example:

Only one dot is drawn at the user's home position.
Is there something wrong with my code that prevents it from working?
Why does it work on iOS and Android not?
I really need to fix this as it is a bug in production.

My problem was in the high accuracy of the gps that was set only for iOS. It appears that Polyline does not render if high precision is not enabled or is rendered incorrectly.
I replaced: { enableHighAccuracy: Platform.OS == "ios" ? true : false, timeout: 5000 }
By: { enableHighAccuracy: true, timeout: 5000 }
Defining calls with promises also helped me to improve behavior.

My problem was in the high accuracy of the gps that was set only for iOS. It appears that Polyline does not render if high precision is not enabled or is rendered incorrectly.
I replaced: { enableHighAccuracy: Platform.OS == "ios" ? true : false, timeout: 5000 }
By: { enableHighAccuracy: true, timeout: 5000 }
Defining calls with promises also helped me to improve behavior.


[Manage Public Key] Upload Key and Fail/Success message

Problem statement
The sender emails us two separate public keys. These keys are stored in the database under sender settings. Then we send them an email that they can start testing (authentication) and includes the API endpoint to point to and link them to API Programmer's guide.
This happens on almost every new sender and is a manual process.
What you need to know
https://www.figma.com/file/6mwI5ac6rprACKDzDo4Ady/ReportStream-Workspace-|-2023?node-id=2167-21742&t=hrkPPWw0VtqV0v9V-0
API - https://github.com/CDCgov/prime-reportstream/pull/8678
Acceptance criteria

[x]  Senders key saves on Submit
[x]  Display success message when successful submit of a senders public key
[x]  Display fail message when error of a senders public key
[x]  Try again button returns the user back to the Manage Public Key page
[ ] QA with Design/Content before merging

To do

[x]  Add endpoint hook and save Senders key
[x]  Display success message when successful submit of a senders public key
[x]  Display fail message and 'Try again' button when error of a senders public key
[x]  Loading step while request is pending
[x] Unit tests

@stephenkao and @jpandersen87 to review it EoD 4/18

ghp_ X8wYT2ZsNhemb9D4FyDyV5hlmxZUw72FtrGi


Add waterway=tidal_channel preset

The feature waterway=tidal_channel has been around for a year now, and usage is up to 2 325 ways. It is documented at https://wiki.openstreetmap.org/wiki/Tag:waterway%3Dtidal_channel -
"A natural intertidal waterway in mangroves, salt marshes and tidal flats with water flow in the direction of the tide"
These features are also know as a "tidal creek", "pill" or "tidal inlet"
JOSM already supports this feature with a preset.

@jeisenbe Thanks 👍


Introduce GitHub Usage for NuGet packages

Today, users depend on a package's download counts to understand its popularity. However, this isn't always sufficient. For example, some System.* packages' downloads are high even though they are not referenced directly very often. To alleviate this, we will add to the "Display Package" page a list of the top GitHub repositories that depend on the package.

(I tried to comment on the blog but it seemed to get swallowed up)
This is great! If I could make one suggestion: change the wording in the "info" sidebar from "Dependent repositories (223+)" to "Github Usage: 223+ repositories".
Even for native speakers, I feel pretty confident that a lot of people are going to read "Dependent repositories" and think it means how many dependencies the nuget package has, which is exactly the opposite of what you want to communicate, and may scare people away.
Sticking with "Github usage" is more consistent with the other new section on the page, too.

Interesting feature. Maybe it will be interesting one day. But now very popular F# libs having no github usages, which is definitely not true. And e.g. Paket, maybe the most popular one, has no GitHub section at all. Correct your heuristics :)

Thanks for the feedback @vilinski! At this time, we only index C# repositories. Adding support for F# projects is a low hanging fruit, I've opened an issue to track that here: https://github.com/NuGet/NuGetGallery/issues/7370

As of today, this feature isn't even working on the package showcased in the article announcing the feature:

As of today, this feature isn't even working on the package showcased in the article announcing the feature:

@kzu , the UX was updated, you can find GitHub usage in the 'Used By' section:

@kzu , the UX was updated, you can find GitHub usage in the 'Used By' section:

You mean nothing uses this? https://www.nuget.org/packages/Microsoft.Extensions.Logging
I'm not seeing any such sections in that page...

You mean nothing uses this? https://www.nuget.org/packages/Microsoft.Extensions.Logging
I'm not seeing any such sections in that page...

Here's a screenshot of the page you linked:

Here's a screenshot of the page you linked:

Ahhh, so it's under Used by, all the way to the bottom! Quite hard to discover if you've been in nuget.org for a while.
I'd suggest adding a second collapsible level under Used By, so that both NuGet Packages and GitHub Repositories become collapsible too and therefore easy to spot when first expanding Used By.
Thanks

Ahhh, so it's under Used by, all the way to the bottom! Quite hard to discover if you've been in nuget.org for a while.
I'd suggest adding a second collapsible level under Used By, so that both NuGet Packages and GitHub Repositories become collapsible too and therefore easy to spot when first expanding Used By.
Thanks


Enhancement/1440 django file form

Ticket: #1440
Rebased from master and added support for S3 temporary storage using a slightly modified django-file-form.
There are some hints in local.py.exmaple for setting up S3 locally if you want to try that first.

@balazs-endresz I have sent you an invite to the Hypha repo now, sorry for not noticing this before!
Now you can commit directly to the 1440-django-file-form branch in this repo.


[pkg/networkpath] Skip Test_createRawTCPSyn and Test_createRawTCPSynBuffer on macOS

What does this PR do?
Skips the Test_createRawTCPSyn and Test_createRawTCPSynBuffer tests on macOS (#incident-32860).
Motivation
Remove broken tests while they are investigated.
Describe how to test/QA your changes
macOS unit test jobs in CI should pass.
Possible Drawbacks / Trade-offs
n/a
Additional Notes

n/a

Force-merging the PR to fix main.


Incompatibility between Python 2.7.11 and Vim 64 bits on Windows

Description
I am using my own built version of Vim 64 bits for Windows with python2 support and I am getting the following error when running python2 inside Vim
E887: Sorry, this command is disabled, the Python's site module could not be loaded.

with python 2.7.11 64 bits. I don't have this issue with the previous version (2.7.10) of Python.
How to reproduce
Install Vim 7.4.972 64 bits for Windows and python 2.7.11 64 bits on Windows 7 64 bits.
Start Vim:
vim -N -u NONE

and run the command:
:py 1

Configuration details
In a shell:
$ python
Python 2.7.11 (v2.7.11:6d1b6a68f775, Dec  5 2015, 20:40:30) [MSC v.1500 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>

$ vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 13 2015 17:01:30)
MS-Windows 64-bit console version
Included patches: 1-972
Compiled by micbou<EMAIL_ADDRESS>Huge version without GUI.  Features included (+) or not (-):
+acl             +eval            +mouse           +syntax
+arabic          +ex_extra        -mouseshape      +tag_binary
+autocmd         +extra_search    +multi_byte      +tag_old_static
-balloon_eval    +farsi           +multi_lang      -tag_any_white
-browse          +file_in_path    -mzscheme        -tcl
++builtin_terms  +find_in_path    -netbeans_intg   -tgetent
+byte_offset     +float           +path_extra      -termresponse
+cindent         +folding         -perl            +textobjects
+clientserver    -footer          +persistent_undo +title
+clipboard       +gettext/dyn     -postscript      -toolbar
+cmdline_compl   -hangul_input    +printer         +user_commands
+cmdline_hist    +iconv/dyn       +profile         +vertsplit
+cmdline_info    +insert_expand   +python/dyn      +virtualedit
+comments        +jumplist        +python3/dyn     +visual
+conceal         +keymap          +quickfix        +visualextra
+cryptv          +langmap         +reltime         +viminfo
+cscope          +libcall         +rightleft       +vreplace
+cursorbind      +linebreak       -ruby            +wildignore
+cursorshape     +lispindent      +scrollbind      +wildmenu
+dialog_con      +listcmds        +signs           +windows
+diff            +localmap        +smartindent     +writebackup
+digraphs        -lua             -sniff           -xfontset
-dnd             +menu            +startuptime     -xim
-ebcdic          +mksession       +statusline      -xterm_save
+emacs_tags      +modify_fname    -sun_workshop    -xpm_w32
   system vimrc file: "$VIM\vimrc"
     user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$HOME\vimfiles\vimrc"
 3rd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
Compilation: cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32   -DFEAT_CSCOPE       -DWINVER=0x0500 -D_WIN32_WINNT=0x0500  /Fo.\ObjCYHAMD64/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_MBYTE -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON  -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python34.dll\" -DFEAT_HUGE /Fd.\ObjCYHAMD64/ /Zi
Linking: link /RELEASE /nologo /subsystem:console /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib uuid.lib /machine:AMD64  /nodefaultlib libcmt.lib  user32.lib      /nodefaultlib:python27.lib /nodefaultlib:python34.lib      /PDB:vim.pdb -debug

In Vim:
:echo has('python')
1

I can confirm that this is specific to the python 64 bits version. It works fine with Vim 32 bits and python 2.7.11 32 bits. Maybe it should be reported to the python folks?

Maybe same as #526?

closing as duplicate of #526


clean_figure() not working

Hi all,
I just discovered the clean_figure() command in tikzplotlib, and it looked like exactly what I need at the moment. Unfortunately, it seems to work only when a figure doesn't contain any points that are outside the axis limits. Example to reproduce the error (adapted from the tikzplotlib example on PyPI):
import matplotlib.pyplot as plt
import numpy as np

plt.style.use("ggplot")

t = np.arange(0.0, 2.0, 0.1)
s = np.sin(2 * np.pi * t)
s2 = np.cos(2 * np.pi * t)
plt.plot(t, s, "o-", lw=4.1)
plt.plot(t, s2, "o-", lw=4.1)
plt.xlabel("time (s)")
plt.ylabel("Voltage (mV)")
plt.title("Simple plot $\\frac{\\alpha}{2}$")
plt.grid(True)

import tikzplotlib

tikzplotlib.clean_figure()
tikzplotlib.save("test.tex")

does work without errors, whereas this (changing ylim):
import matplotlib.pyplot as plt
import numpy as np

plt.style.use("ggplot")

t = np.arange(0.0, 2.0, 0.1)
s = np.sin(2 * np.pi * t)
s2 = np.cos(2 * np.pi * t)
plt.plot(t, s, "o-", lw=4.1)
plt.plot(t, s2, "o-", lw=4.1)
plt.xlabel("time (s)")
plt.ylabel("Voltage (mV)")
plt.title("Simple plot $\\frac{\\alpha}{2}$")
plt.grid(True)
plt.ylim([-0.5, 0.5])

import tikzplotlib

tikzplotlib.clean_figure()
tikzplotlib.save("test.tex")

returns a NotImplementedError.
If it helps, I'm using tikzplotlib 0.9.1. Is there anything I can do to get this to work?
Many thanks,
Sita

Is there anything I can do to get this to work?

Sure! Submit a PR.

By PR, do you mean pull request? I'm not much of a GitHub expert, how does a pull request work?

@sitadrost Check here. :wink:

Alright, so by PR you did indeed meant pull request, good. Perhaps I should have phrased my question differently: of course I looked up "pull request" in the GitHub help before asking you, the explanation just didn't make much sense to me in this context. The help says:
Pull requests let you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.
So how is this supposed to help me to get clean_figure() to work? I installed tikzplotlib through conda, so my local version is not a git repository. For which branch do you want me to submit a pull request?

You can of course also make your changes locally and attach them to this bug report. It's usually easier to discuss changes in PRs though, so I'd recommend you make yourself familar with GitHub. I can understand if this is quite tall of an order for you, but it is my experience with software that is in "maintenance mode" like tikzplotlib that if you don't do it yourself, no one else will do it for you.

Thanks, but I didn't make any changes, so I still don't quite see what you want me to do.

I'm saying: If you want this to work sometime soon, you'll probably have to implement it yourself.

Grand, thanks for nothing, why not just say so straight off?
Never mind, I'll use some workaround.

I didnt fix the issue, but improved the error message, so that people dont need to dig to deep to fix the issue manually(i.e setting ylim/xlim appropriately)
Here is the PR
https://github.com/nschloe/tikzplotlib/pull/514


slice_input_producer output tensor of wrong shape under certain conditions

From the verison
tensorflow-0.12.0rc0-cp27-cp27mu-manylinux1_x86_64.whl
When using  tf.train.slice_input_producer with a tensor_list containing only a single tensor, the output from the tf.train.batch has incorrect dimension.
Code to reproduce it
import tensorflow as tf

data=tf.random_uniform(shape=(50, 50))
labels=tf.ones(50)
sample, _=tf.train.slice_input_producer([data, labels])
batch=tf.train.batch([sample], batch_size=8)

print batch

sample=tf.train.slice_input_producer([data])
batch=tf.train.batch([sample], batch_size=8)

print batch

the output is
Tensor("batch:0", shape=(8, 50), dtype=float32)
Tensor("batch_1:0", shape=(8, 1, 50), dtype=float32)

I think the two output should be the same? Simple workaround like reshaping the batch data is feasible. However, I think this is a bug.

@ebrevdo is this WAI?

Good question. I'm ooo for 2 weeks.  Ispir may know better.

slice_input_producer returns a list.
First call expands the list due to double assignment.
Second call doesn't expand it.
second call of batch should be as follow:
batch=tf.train.batch(sample, batch_size=8)


Module extension definition question.

Given the following modules how can I import/export the functions in the modulea namespace as functions in module b IAllFunctions interface?
My problem stems from trying to create rethinkdbdash definitions that are easy to maintain.
I've created the following retinkdbdash definition that duplicates all functions into the RDash interface that exists in the rethinkdb defition namespace.
Is there a way to declare my rethinkdbdash definition in a more maintainable way?
declare module 'modulea' {
namespace modulea  {
      function abc() : xyz
   }

export = modulea;
}

declare module 'moduleb' {
import * as moda from 'modulea';
namespace moduleb  {
      export interface IAllFunctions {
         EXPORT modulea.abc() here....???
      }
   }
 export = moduleb;
}

Are you trying to augment an interface with functions declared in a namespace?

@aluanhaddad It would seem so.

Roger. I was asking because I find the following pseudocode very confusing
export interface IAllFunctions {
         EXPORT modulea.abc() here....???
      }

What is your goal? Is it to have modulea appear as though it exposes the augmentations introduced by moduleb or is to merge modulea into moduleb and expose the augmented module from the latter?

I've included a snippet of code usage so that you can see the differences in usage. The rethinkdbdash driver basically wraps the rethinkdb driver and exposes all the methods of the rethinkdb namespace on the variable that you get back from calling rethinkdbDash({db:'devDB'});
Thus I have to re-declare all rethinkdb.Func..XYZ on the RDash interface that is returned. So now I'm asking if there is a better way than having to re-declare all the exposed functions. Maybe some clever import/export that can reduce all the copy and pasting.
import * as rethinkdbDash from 'rethinkdbdash';
import * as rethinkDb from 'rethinkdb';

async function printDateRethinkDb(){
	let conn = await rethinkDb.connect('localhost'); //Note how we are accessing namespace functions.
	let date = await rethinkDb.now().run(conn);
	console.log(`Rethink DB Date: ${date}`);
}

async function printDateRethinkDbDash(){
	let r = rethinkdbDash({db:'devDB'}); //Here we call the default namespace function to get back an interface.
	let date = await r.now();
	console.log(`Rethink DB Dash Date: ${date}`);
}

printDateRethinkDb();
printDateRethinkDbDash();


Wallaby not finding wallabyTest.js

Facing this weird issue that Wallaby is still complaining about not finding wallabyTest.js file even tough I have it saved as attached.
Unable to move ahead with Wallaby due to this. Also I can't seem to see the Wallaby toolbar I used to have in my previous company using phpStorm,

Sorry that was by mistake, had wrong window open.


New version: Telegram.TelegramDesktop version 5.2.1

Pull request has been created with WinGet Releaser main :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:
(Automated response - build 886.)

Close with reason: Duplicate of #160999;


Automate CLI documentation task

Adding toolkit to automate documentation tasks moving forward.

Thanks @vdice - I just did a pretty major update on all of these and tested it out.
It should be good to go.
Thanks for the review feedback and new ideas; greatly appreciated.

Edited these files (squashed the commits) and tested it out locally again this afternoon (with the new updates).
Thanks for the suggestions and review @vdice - hopefully this is good to go now.

Thanks @vdice


Can you help my with matrix parameters?

Please, add example path and rule for matrix parameters, can't understand that

You can look at the tests: https://github.com/troch/path-parser/blob/master/test/main.js#L122-L129
Matrix parameters is something very obscure though, do you have the capabilities to support them with your backend? I am not sure to support them very well. I don't make them optional like query parameters.
They are like regular URL parameters but look more like query parameters (but placed anywhere before ?). You can define a matrix param by using ;key instead of :key and it will parse them from your URL expecting ;key=value.

Thanks!

I thought, that matrix parameters can resolve my problem. I have object like
  {setiD: 2, variations: "12-13-4", elements="2-3"},
  {setiD: 4, variations: "11-12-6", elements="2"},
  {setiD: 5, variations: "18-13-8", elements="1"}
]```

And don't know how I can put it to hash with clear structure

best idea was /;set;variations;elements/ , but I can't repeat that pattern multiple times


Fix compilation warning. Added Wall and Wextra flags and fix warnings.

I just hided an unused parameter warning : is_random_access_iterator(Iterator /* begin */, Iterator /* end */ )
I have added some compile flags that are used in the projects I work on and hide them in CPR so that they do not show anymore.

Ok I will remove the extra flag on Windows which does not recognize it...

Looks good, thanks @coin-au-carre!


tests: drivers: Extend coverage for SPI MEMORY driver

Cover more SPI flash memeory driver api methods
Extend testing for nrf54l15

Please review

Coverage should be a goal for a test, not a user-facing code sample https://docs.zephyrproject.org/latest/samples/sample_definition_and_criteria.html
Thanks

Agree.
I need to wait until upmerge finishes on our side before modifying the test case.


how to train on custom dataset?

I have a .vtp 3d mesh model, and 2d rendered images in different views. Is it possible to train the real fusion based on such data?
Thank you :-)

I suppose it would be possible, yes. You could modify the code to load multiple conditioning images and their corresponding camera positions. That being said, if you already have a mesh model, what is the motivation for wanting to do RealFusion?


pio: add initial config and instructions

This build tool involves less manual steps and use a modern editor anyways.
I am also considering converting the ino to cpp, but it will drop support for arduino ide.

Thanks!


Sniff for HTML in translatable strings

Avoid HTML in strings if possible

Ref: https://make.wordpress.org/core/handbook/best-practices/internationalization/
HTML in translatable strings should be avoided as it puts an extra burden on translators in that they'd have to know HTML.
It also makes output escaping translatable strings much easier if there is no HTML in the string.
The HTML should be moved out of the translatable string and placeholders should be used instead.
// Bad:
echo wp_kses( __( 'This is a bold text', 'text-domain' ) );

// Good:
printf (
    /* translators: 1:  open tag 2: close tag. */
    esc_html__( 'This is a %1$sbold%2$s text', 'text-domain' ),
    '',
    ''
);

I think this should be quite easily sniffable and could be a good addition to the existing WP.I18n sniff.
I propose for this to be a warning.
I also propose not to include an auto-fixer. While for a simple example as the above, this could be auto-fixed, in general, it will need the critical look of a human being to determine the best course of action.

Just a question out of curiosity
// Good:
printf (
    /* translators: 1:  open tag 2: close tag. */
    esc_html__( 'This is a %1$sbold%2$s text', 'text-domain' ),
    '',
    ''
);

Would this not be better like this since it's easier for translators?
// Good:
printf (
    /* translators: The "bold" string, wrapped in  tags. */
    esc_html__( 'This is a %s text', 'text-domain' ),
    '' . esc_html__( 'bold', 'text-domain' ) . '',
);

Strings like %1$sbold%2$s are something that I've seen confuse lots of people and over the years I've spotted many wrong translations because of strings like that

@aristath No. You should always avoid fragmenting a sentence as the sentence build up may be (very) different in different languages.
See: https://make.wordpress.org/core/handbook/best-practices/internationalization/#avoid-fragmented-or-patchwork-messages

Ah I don't know how I missed that... Thanks! I learned something new today. 👍

I'm -1 for this.
The best practices say to move unusual markup out of the string, but it also says about leaving URLs (typically, as part of an  tag) in if they are likely to have a locale-specific version.
It then also refers to the gettext manual, which includes:

HTML markup, however, is common enough that it’s probably ok to use in translatable strings.

So a string with basic markup is fine. It's static markup - translators can cope with it, as they have done for the last X years.
The Handbook page to which you reference is clearly incomplete, so I wouldn't put too much weight behind those 6 words to feel it implies that all HTML should be removed.
The Theme Handbook clarifies it as:

Do not put unnecessary HTML markup into the translated string.
(my emphasis)

rather than do not put any markup in the string.
The Plugin Handbook even gives an example with HTML in it:
/* translators: 1: WordPress version number, 2: plural number of bugs. */
_n_noop( 'Version %1$s addressed %2$s bug.',
         'Version %1$s addressed %2$s bugs.' );

Examples where the markup should be removed from inside of the string would be:
<?php __( '
Settings Page
', 'text-domain ); ?>
should be

<?php __( 'Settings Page', 'text-domain' ); ?>

because the markup only wraps the string.

<?php _e( 'Adds rel="noopener noreferer" to links', 'text-domain' ); ?>
would move the code and the `<code>` elements into a placeholder, because they should not change during translation:
<?php
printf(
    esc_html__( 'Adds %s to links', 'text-domain' ),
    'rel="noopener noreferer"'
); ?>

The first example might be detectable - matching tags as first and last items in the string, with no other markup, but it would be trivial to come up with close-but-not-quite right examples where a check like this would miss.

@GaryJones Good points. I think the second example would be quite easy to sniff for as well as  is a very specific tag.
Let's see if we can collect some more typical examples where HTML should be moved out of the translatable string.
We could then just throw a warning for those specific situations.

I fully agree with @GaryJones's statements above; %1$sbold%2$s is definitely not good.

Let's see if we can collect some more typical examples where HTML should be moved out of the translatable string.

See https://core.trac.wordpress.org/search?q="Avoid+using+HTML"&noquickjump=1&changeset=on&ticket=on for some examples.

Thanks @ocean90 for that link, very useful!

There doesn't seem to be consensus on this, so closing this issue as wont-fix.


Renamed layer types, classes, values and keys from nso to admin-level-data

[x] Rename all layer types with nso to admin-level-data
[x] Rename NSOLayer and NSOLayerProps to AdminLevelDataLayer and AdminLevelDataLayerProps respectively
[x] Test is changes didn't affect the application

Looks good from my side @erwagasore. You'll need to get the latest from master again. Let's also wait for technical review from @JorgeMartinezG . Let's please aim to get this merged onto master early next week


Player transitions from left of screen

Current Behavior

Hey, I'm using your great video player but encountered one problem which I could not fix. The player "enters" the screen from the left.
Expected Behavior

I would like it to keep centered and no transition.
Steps to Reproduce

All I did was to add the video player to the page.
Environment

URL attempting to play:
Browser: Chrome, Safari
Operating system: macOS
Framework: Next.js version 10.2.0
codeSandbox example: https://codesandbox.io/s/reactplayervimeoissue-281zo

Other Information

Things I'v tried:

Wrapping it in a <div>,

Using the wrapper attribute

Passing style={{transition: 'none'}}

Creating .css selectors for
.vp-video-wrapper
.vp-overlay-wrapper
.vp-overlay-bg
and even
.vp-overlay-cell
.vp-overlay-icon-wrapper
.vp-overlay-icon
.vp-overlay-logo
.vp-alert
.logo
.hidden
.player
with { transition: none }
in globals.css

I ran into this issues as well. Ended up using the onReady() callback to toggle the visibility.
Something like this:
https://codesandbox.io/s/reactplayervimeoissue-forked-loclh?file=/src/App.js

Thanks a lot @yoheioka, this hack handle the issue perfectly!


Add cypress e2e-testing for react, angular, vue apps

Checklist

[x] create react app
[x] create vue app
[x] create angular app
[x] add scripts to run apps

@jmestxr wrong branch yoz. merge your e2e stuff branch to master directly.


Breaking API change to support base type comparison.

Equals made protected and IEquatable made explicit for classes. This should sort out the last issue with comparing derived types cast as base-type.
Solves #43

@christianrondeau are you happy with this fix?

I'm looking at the branch, is that the eventual 3.0? And FYI I got this when referencing directly from source, it's annoying when you don't have VS installed :D

You could check for an environment variable, or a precompiler directive other than DEBUG.
So, I had this that you may find interesting:

@christianrondeau I have fixed the private/protected modifier and added extra tests. On the <generated/> comment I could not find any guidelines or docs for use -- I am not entirely sure this does anything that's not already accomplished by the GeneratedCodeAttribute.
If you have any pointers to it, let me know.

These changes are available on 3.0.0-beta001 if you want to give that a go!

You may be right, anyway I also got it wrong, it's actually <auto-generated />
https://learn.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/source-generators-overview does it but doesn't explain why... I guess it's just to make it clear. But I guess it doesn't really matters.
I'll pull and try it when I have some time :)


ICS Functionality for Juno (tracking issue for discussion)

Do we want to pursue this?
I know how to give Juno ICS functionality but it does seem to at this time restrict us to using SDK 45.

I'm not sure ICS is on the cards. My money is probably on smart contract based mesh security. Thoughts @JakeHartnell / @dimiandre ?

Is this in regards to Interchain security v1/v2/v3? If so we are going the mesh way - this issue can be closed if so

I'm not sure ICS is on the cards. My money is probably on smart contract based mesh security. Thoughts @JakeHartnell / @dimiandre ?

Mesh Security > Replicated Security.


Add missing configuration option to plex

Related issue (if applicable): fixes part of #21254
Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Great!


Not sure where and how to set the Workflow Environment Variables

Hi,
First I'd like to thank you because I've been looking for a workflow like yours for several months. Can't wait to set it up properly.
I may ask beginner questions, apologies, but I already searched in existing open and closed issues without success.
About your mention "The Workflow Environment Variables have defaults which will work for most. You only have to mess with them if you have an atypical setup.
google_drive_path: The location of Google Drive on your file system. Can take multiple paths separated by commas."

I don't know exactly where I'm suppose to edit them? I think I'm having an atypical setup, with 2 Google drive accounts, one with Shared drive. When trying to use the basic settings and following the cache building instructions, no file is being found.
Thanks a lot for your help.

Documentation with screenshot.


Improving feedback to the user when updating templates

Adresses #788.
Implements

When you do not have internet connection, you receive some feedback about it.
When adapting templates, you receive feedback that the templates are being imported
Fixed an issue that forced to download the latest templates each time you clicked on generate.

Attention: This PR also includes PR #785 and PR #787
@devonfw/cobigen

I am not sure, how this relates to #787 as it contains the same commits, please have a look at the review of #787.
Even #781 seems to be the same. Which PR now contains the latest changes? Please close the others.

@maybeec with the last two commits, I have fixed all your change requests but this one, which I think should be discussed.


Fix phase 2 and 3 audit logging in case of internal redirect

Pull request #241 attempted to fix the problem where the log handler was not called in case of internal redirects (e.g. when using error_page). The problem was that the log handler was registered at Nginx log phase, however processing never reached that Nginx phase in case of an internal redirect (the Nginx context of the original request was cleared and a new one was created for the internal redirect). The pull request tackled the issue by introducing the concept of “early logging”, where the process intervention function would manually call the log handler.
However, this early logging mechanism was only enabled for ModSecurity’s phase 1 (request headers). As a result, the original issue was fixed only for that phase but not for ModSecurity’s phases 2 (request body) and 3 (response headers). It did not apply to ModSecurity’s phase 4 (response body), as at this phase it not possible to perform a redirection due to Nginx limitations (see this comment for more information).
This pull request unconditionally enables early logging in the process intervention function for all ModSecurity phases, by removing the respective control flag (what it does is similar to pull request #90, on which pull request #241 is based on). The log handler should always be called in both the process intervention function and the Nginx log phase. The former is the only place in which the log handler is guaranteed to be called in case of an intervention (as demonstrated by this issue) and the latter is required so that it is called when an intervention is not triggered. The "logged" context flag ensures that logging takes place only once.
Finally, the custom error page test case has been updated to include rules of all ModSecurity phases. The tests for ModSecurity phases 2 and 3 fail with the current upstream code and succeed after the proposed fix is applied.

Any update on this?

@kolotouros : No

@kolotouros This will duplicate log entry, and no extra response header, nor response body.
For error_page, current implementations:

request, no response, no log
second request, got response, log with response headers and body

In this patch:

request, no response, log without headers
second request, got response, log without headers

This pull request is more of a fix to the existing workaround ("early logging") than a proper solution to the issue caused by internal redirects.
Pull request #273 is in the correct direction, it recovers the original request's context which can then be used to log the transaction properly. However in its current state it does not properly mitigate the issue described in this pull request. Specifically, if ModSecurity is not enabled in the internal redirect's location conf, the log handler will not run at all. This is demonstrated by the updated test case included in this pull request.
If pull request #273 is merged (along with the extra changes discussed in the respective thread), this pull request can be closed.

Is there any news please?
It seems that those commits helps my need.
Thanks to the author for your contribution. :)

+1, we need to fix error_page redirect still with this code base.

Hi guys,
it seems like there are some conflicts that must be resolved, so @mlevogiannis please:

pick up and merge the modifications
resolve the conflicts
push the new commits

Then the new CI will start and we can see the tests results too.
It would be nice to do these in next few days, I would like to release a new version, and - perhaps - many user would be happy whit this.
Thanks!

@airween In my opinion, this branch (mentioned in #273) should be merged instead of this PR (the reasoning is described here. It fixes the issue described in the first post and includes the same test cases. We may create a new PR for it, if that will help.
However, if you insist on merging this PR, I will update it to resolve the conflicts.

@airween In my opinion, this branch (mentioned in #273)

you mean the PR #273 instead of this, right?

should be merged instead of this PR (the reasoning is described here. It fixes the issue described in the first post and includes the same test cases. We may create a new PR for it, if that will help.
However, if you insist on merging this PR, I will update it to resolve the conflicts.

No, I'm not insist. But that PR must be updated too.
Thanks.

@airween In my opinion, this branch (mentioned in #273)

you mean the PR #273 instead of this, right?

No, I mean this branch, which is based on the PR you mention. I have not created a separate PR for it (yet, but I will do so should this be requested) as I hoped that the original author would include the extra commits in their branch, but they only copied part of our changes in a new commit.

should be merged instead of this PR (the reasoning is described here. It fixes the issue described in the first post and includes the same test cases. We may create a new PR for it, if that will help.
However, if you insist on merging this PR, I will update it to resolve the conflicts.

No, I'm not insist. But that PR must be updated too.

Updated.


Update install-lookyloo-docker.adoc

Port used by container was not correct
Pull requests should be opened against the main branch. For more information on contributing to Lookyloo documentation, see the Contributor Guidelines.
Type of change
Description:
Select the type of change(s) made in this pull request:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Documentation (change or fix to documentation)

Fixes #issue-number
Proposed changes

Thanks!


[Learn Rebrand/Metadata Publish]

We need to verify the commits that are mixed in with the Learn Rebrand work

Learn Build status updates of commit 165591d:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

project-rome-docs/devicerelay/how-to-guide-for-android.md
:bulb:Suggestion

Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

CONTRIBUTING.md
:white_check_mark:Succeeded

project-rome-docs/devicerelay/how-to-guide-for-windows.md
:white_check_mark:Succeeded

project-rome-docs/includes/android/notifications-notification-init.md
:white_check_mark:Succeeded

project-rome-docs/includes/android/notifications-platfrom-init.md
:white_check_mark:Succeeded

project-rome-docs/includes/auth-scopes.md
:white_check_mark:Succeeded

project-rome-docs/includes/auth-scopesiOS.md
:white_check_mark:Succeeded

project-rome-docs/notifications/api-reference-for-android.md
:white_check_mark:Succeeded

project-rome-docs/remote-sessions/how-to-guide-for-windows.md
:white_check_mark:Succeeded

project-rome-docs/user-activities/how-to-guide-for-android.md
:white_check_mark:Succeeded

project-rome-docs/user-activities/how-to-guide-for-windows.md
:white_check_mark:Succeeded

README.md
:white_check_mark:Succeeded

project-rome-docs/devicerelay/how-to-guide-for-android.md

Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'This guide will show how to discover remote devices and apps and then launch apps or interact with app services.' is duplicated in 'devicerelay/how-to-guide-for-android.md(3,14)', 'devicerelay/how-to-guide-for-ios.md(3,14)'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Can't mount specific file type via Azure extension

I tried to mount Azure blob storage as a file system in order to read one specific file from AzureBlobStorage.
I used another extension, "spatial," which can read and open the ".gdbtable" format for reading files.
con = duckdb.connect(
            database="/tmp/quack.db",
            config={
                "threads": 8,
                "memory_limit": "4GB",
                "temp_directory": "/tmp/",
                "preserve_insertion_order": False,
                "extension_directory": "/tmp/"
            }
        )

con.install_extension("spatial")
con.execute("LOAD spatial;")
con.install_extension("azure")
con.execute("LOAD azure;")
con.execute("""CREATE SECRET secret (
    TYPE AZURE,
    CONNECTION_STRING 'DefaultEndpointsProtocol=https;AccountName=redacted;AccountKey=redacted'
);""")

Here, I want to read this file directly to avoid downloading it to the worker and just put all the data into a duckdb table
con.sql(query='CREATE OR REPLACE TABLE GPKG_FILE AS SELECT * FROM ST_Read("abfss://redacted/dat-redacted/raw_data/v55/a00000007.gdbtable")')

The error traceback
Traceback (most recent call last):
  File "/Users/redacted/Library/Caches/pypoetry/virtualenvs/com-ing-connector-XVl8hQFI-py3.11/lib/python3.11/site-packages/IPython/core/interactiveshell.py", line 3577, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-29-c75b6f8e2a1a>", line 1, in <module>
    con.sql(query='CREATE OR REPLACE TABLE GPKG_FILE AS SELECT * FROM ST_Read("abfss://redacted/dat-redacted/raw_data/v55/a00000007.gdbtable")')
duckdb.duckdb.NotImplementedException: Not implemented Error: AzureDfsStorageFileSystem: FileExists is not implemented!

Also, I have the same with
con.sql(query='CREATE OR REPLACE TABLE GPKG_FILE AS SELECT * FROM ST_Read("az://dat-nexiga/raw_data/nexiga_v55/a00000007.gdbtable")')

The error traceback
Traceback (most recent call last):
  File "/Users/redacted/Library/Caches/pypoetry/virtualenvs/com-ing-connector-XVl8hQFI-py3.11/lib/python3.11/site-packages/IPython/core/interactiveshell.py", line 3577, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-28-6b82186ab390>", line 1, in <module>
    con.sql(query='CREATE OR REPLACE TABLE GPKG_FILE AS SELECT * FROM ST_Read("az://dat-redacted/raw_data/v55/a00000007.gdbtable")')
duckdb.duckdb.NotImplementedException: Not implemented Error: AzureBlobStorageFileSystem: DirectoryExists is not implemented!

Also, I have the same with
con.sql(query='CREATE OR REPLACE TABLE GPKG_FILE AS SELECT * FROM ST_Read("az://dat-nexiga/raw_data/nexiga_v55/a00000007.gdbtable")')

The error traceback
Traceback (most recent call last):
  File "/Users/redacted/Library/Caches/pypoetry/virtualenvs/com-ing-connector-XVl8hQFI-py3.11/lib/python3.11/site-packages/IPython/core/interactiveshell.py", line 3577, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-28-6b82186ab390>", line 1, in <module>
    con.sql(query='CREATE OR REPLACE TABLE GPKG_FILE AS SELECT * FROM ST_Read("az://dat-redacted/raw_data/v55/a00000007.gdbtable")')
duckdb.duckdb.NotImplementedException: Not implemented Error: AzureBlobStorageFileSystem: DirectoryExists is not implemented!

Thanks for reporting @andreypanchenko! This seems like it should be relatively simple fix


mulit_commits__20150509

Moves folder Experiemntal out of old source and just adjusts the
Readme no other change

What I do is to rename the experimental to Docile and use it just normal.
ulia> Pkg.test("Docile")
INFO: Computing test dependencies for Docile...
INFO: No packages to install, update or remove
INFO: Testing Docile
ExampleMeta1.
     - Check getparsed metadata replacement.
INFO: Updating cached package list...
INFO: Initialising cache for 'ExampleMeta1' and related modules...
 ExampleMeta1 ✓
INFO: Succcessfully initialised package cache.
14 facts verified.
INFO: Docile tests passed
INFO: No packages to install, update or remove

julia>

Thanks.


reorder rules in front of selectors

Sort rules to the start of selector blocks.


Button not visible properly

When logged in to the application as an admin and while creating a new appointment, it is confusing to understand the add button. The visibility is poor due to color selection.
I am viewing this in chrome on mac. The button color is greenish.

@csawai the button is that way because it is disabled until all of the required fields have been filled in. Once all the required fields are filled in the button changes color:

Def agree that it's crappy as is, though. It's awaiting some long overdue design cleanup. I've been meaning to give those buttons a better disabled style, like some type of gray or something. :+1:

Partly addressed in #355.

As @jkleinsc said the color on the buttons after filling up the appointment forms is confusing.I am going to  change the disabled,active and hover buttons color states to a more understandable manner . Please review my pull request #971


Allow extra user fields

Allow extra user fields for specific deployments. This will allow gathering additional data about users such as their email address, definable on a per instance basis.

Closing this as we have decided to make email registrations optional and unrelated to the authentication flow. This changes the approach significantly, will open a new PR.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

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


wip

User-facing:

fix #43
report: add special fork/star sections when no data is available.
report: fix a typo.

For CI/dev changes see commit msgs.

Great, there are two test cases here that cover https://github.com/jgehrcke/github-repo-stats/issues/43 -- here is how it's exposed:
not ok 2 analyze.py: snapshots: some, vcagg: yes, stars: none, forks: some
# (in test file tests/analyze.bats, line 18)
#   `[ "$status" -eq 0 ]' failed
# Last output:
# 211202-14:45:11.859 INFO: Remove output directory: 2021-12-02_report
# 211202-14:45:11.859 INFO: Create output directory: 2021-12-02_report
# 211202-14:45:12.848 INFO: stargazer_ts_inpath not provided, return emtpy df
# 211202-14:45:12.849 INFO: Parse fork time series (raw) CSV: tests/data/A/forks.csv
# 211202-14:45:12.852 INFO: forks_cumulative, raw data: time
...
# 211202-14:45:12.884 INFO: df[views_total]: use symlog scale, because range > 100
# 211202-14:45:12.932 INFO: time window for stargazer/fork data: ('2020-12-01', '2021-11-30')
# Traceback (most recent call last):
#   File "/cwd/analyze.py", line 1589, in <module>
#     main()
#   File "/cwd/analyze.py", line 126, in main
#     add_stargazers_section(
#   File "/cwd/analyze.py", line 1153, in add_stargazers_section
#     assert starts_earlier_than_vc_data is None
# AssertionError

Gave the updated @main a try:

This repository has no forks yet.

👍


Mismatch pad_ix in utils week 8.

Resolved mismatch pad_ix in utils week 8. Also rearranged clear_output position and added total value for tqdm training loop (now remaining time is showing).

Thank you so much!


Add @available attribute to testAsyncMethods fixture

This fixes a compilation problem when running tests under SPM.
Motivation:
If running unit tests with SPM like so:
swift test --sanitize=thread --filter FunctionalTests.TestDiscoveryTests/testAsyncMethods
The test fails with these errors:
/private/var/folders/s3/556s8dsd7y9272mxm7rydmsr00056_/T/Miscellaneous_TestDiscovery_Async.Guycrz/Miscellaneous_TestDiscovery_Async/Tests/AsyncTests/SwiftTests.swift:6:22: error: concurrency is only available in macOS 12.0.0 or newer
    func testAsync() async {
                     ^

This change fixes the problem.
Modifications:
Add @available attribute to the AsyncTests class in the test fixture.
Result:
Test now passes when run under SPM.

@swift-ci please smoke test


Keep stake DB updated and avoid rewind on startup

Addresses https://github.com/dcrdata/dcrdata/issues/26
This adds package stakedb to manage the dcrd/database.DB used to track the live ticket pool.  It simplifies startup sync and it has a notification handler to stay updated as blocks come in after the sync.
The dependencies are also updated to Decred 1.0.1 versions.

Looks like this panics on reorgs (makes sense).
05:12:07.46 2017-05-11 [INF] DCRD: Block height 132248 connected
05:12:07.56 2017-05-11 [DBG] MEMP: Vote in new block triggering mempool data collection
05:12:07.66 2017-05-11 [DBG] MEMP: mempoolDataCollector.Collect() completed in 0s
05:12:07.76 2017-05-11 [INF] DSQL: Connected block 132248 to stake DB.
05:12:08.19 2017-05-11 [DBG] DCRD: blockDataCollector.Collect() completed in 830.9989ms
05:12:14.97 2017-05-11 [DBG] DATD: Winning tickets: 7f095fb29750110e62084a3f2a611789dab0530d1f6f212a0615593fe536319e, 66390f5d1d7d216081c5c2a89974ed530b224e1e38b272200dcd508a6b905d74, a4b3028e07c9ee03582569258aa0d48bed661f73e5c582833ef57b3b6b75ec63, 9aa37c672a06adb6bdc787a8e479301823a29f20a62fe02461cd596942781517, 9f9d1b0981f5c164322f88ac6ca5bd10af1df443f5b2ac9fb43cafc0e9207490
05:20:33.77 2017-05-11 [INF] DCRD: Block height 132248 connected
panic: trying to connect the wrong next block: 132248, 132248

goroutine 99 [running]:
github.com/dcrdata/dcrdata/stakedb.(*StakeDatabase).ConnectBlock(0xc04256ca80, 0xc044dd3c00, 0xc044dd3c00, 0x0)
        C:/Users/jon/go/src/github.com/dcrdata/dcrdata/stakedb/stakedb.go:116 +0x3ab
github.com/dcrdata/dcrdata/stakedb.(*StakeDatabase).ConnectBlockHash(0xc04256ca80, 0xc04378a480, 0x0, 0xc04456ff06, 0x1)
        C:/Users/jon/go/src/github.com/dcrdata/dcrdata/stakedb/stakedb.go:90 +0x8d
github.com/dcrdata/dcrdata/stakedb.(*ChainMonitor).BlockConnectedHandler(0xc042ec0ca0)
        C:/Users/jon/go/src/github.com/dcrdata/dcrdata/stakedb/chainmonitor.go:41 +0x13a
created by main.mainCore
        C:/Users/jon/go/src/github.com/dcrdata/dcrdata/main.go:214 +0x1720

Looks like this is on the table now: https://github.com/dcrdata/dcrdata/issues/15