Command 'Create new jupyter notebook' resulted in an error

Testing microsoft/vscode-jupyter#11963
This is familiar, there might be an issue for this, but I'm not sure and can't find it
I just ran the command and closed the  new untitled notebook over and over then got this

2022-11-30 15:50:58.937 [error] NO notebook document for 'untitled:Untitled-2.ipynb?jupyter-notebook': Error: NO notebook document for 'untitled:Untitled-2.ipynb?jupyter-notebook'
    at f.getNotebookDocument (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:96:78756)
    at k.$acceptDirtyStateChanged (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:86:107708)
    at u.N (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:11208)
    at u.M (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:10926)
    at u.H (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:10019)
    at u.G (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:9000)
    at /home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:104:7788
    at d.invoke (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at v.deliver (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at g.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at h.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:14314)
    at /home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:120:15804
    at d.invoke (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at v.deliver (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at g.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at h.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:14314)
    at c.y (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:17324)
    at /home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:15795
    at d.invoke (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at v.deliver (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at g.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at g.acceptChunk (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:12045)
    at /home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:11332
    at d.invoke (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at v.deliver (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at g.fire (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at g.t (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:72:25895)

From the log it seems related to our model syncing
at f.getNotebookDocument (/home/roblou/.vscode-server-insiders/bin/9908b3d5ae12691da5adc2f18e21a100ee8eeb58/out/vs/workbench/api/node/extensionHostProcess.js:96:78756)
    at k.$acceptDirtyStateChanged

A dup of https://github.com/microsoft/vscode/issues/148368


Add docs for the "Explain enforcement" feature

Issue: https://github.com/casbin/casbin/issues/355
PR: https://github.com/casbin/casbin/pull/425

@nodece @GopherJ @hackerchai @DivyPatel9881 @kingiw can anyone work on it?


feat($location/$route): support changing location without side effects/route reloading

There seem to be several issues that requests/discuss/implement the ability to make changes to the current location (URL/history API), without Angular "reacting" to the change. Below is a list of such issues I gathered from a very quick search that seem (more or less) related:
PRs:
#5860: feat(ngRoute): add method $route.silent(path) for change location path without triggering route controller
Issues:
#1699: Option on $location to allow hash/path change w/o reloading the route
#3789: Directly modifying the URL path & search without any side effects
#7925: Something along the lines of reloadOnPathParams in ngRoute
#11075: Changing the location outside of $location causes infdig and/or resets the original url
#12719: Do not force a reload when navigating out of the app base

I see two main categories/features:

Change the location to something that is either outside of the Angular app (e.g. at a different base) or would map to a different route (assuming client-side routing is used).
Change the location to something that would map to the same route (but with different route params).

While I think it would be possible to support both usecases, I haven't seen any (reasonably common) usecase for (1). Furthermore, if we implemented (1), it would make it too easy for people to unknowingly break their client-side routing/deep-linking. Based on that and the fact that it would further complicate what is one of the most complex services, I am not too keen on adding support for (1) - but can be convinced other wise :smiley:
In contrary, having the ability to update the route params (and having the change reflect back to the URL, so deep-linking continues to work as expected), but without having to reload the same route, re-compile the same template, re-instantiate the same controller, re-resolve all resolve values etc, sounds pretty reasonable and common.
It is essentially a variation of the reloadOnSearch configuration option, but for path segments. I.e. if the path changes, but the new path maps to the same route (with different route params) and that route is configured to not reload on path change, then we just emit a $routeUpdate event (the same we do for query param/hash changes on routes configured with reloadOnSearch: false) and not load the same route all over.
For routes configured to reload on path changes (probably the default), the behavior will be the same as it is today.

Also note that the Angular 2 router will support a similar feature (although there can't be a 1-to-1 match with ngRoute, since the former is hierarchical.

Usecase (2) addressed by #15002 and we do not intend to support usecase (1) atm.
Closing.


Is there a way to revoke a token?

I have searched through the code for "revoke" but could not find anything, not sure where the complete documentation for this is, the only documentation I found covers getting started but no complete documentation of the methods.
So the question is: can I revoke a token with the sdk? I'm asking because the sdk is used on a stateless server and this token is only used for the duration of the request.

The SDK didn't implement a revoke token mechanism yet.
The revocation typically happens out of band and was not in scope of the SDK. Same applies btw for the introspection.

@jenschude Can you advice how I should use the sdk on a stateless server? I don't think it's a good idea to create a new session (associated with token) on every request only to never use that token again.

There are different ways possible.
One could be using a cache instance for storing the tokens and using the existing tokens middleware.
Another one can be to give the token to the serverless function using an environment variable. You would have to have a service/library regularly updating the environment variable.
When using AWS Lambda you could also use SSM or similar functionality.
Another option for AWS Lambda is to use the init phase of the lambda function to create the client instance and fetching the token. The lambda instance should stay alive for some time (~15min) before being killed.


Prisma query engine panic in making relation query

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v14.15.1

OS
windows

Prisma Client
2.15.0

Query Engine
query-engine e51dc3b5a9ee790a07104bec1c9477d51740fe54

Database
undefined

Query
query {
  findManyIssue(where: {
    resolved: false
    message: null
    request: {
      evidence: {
        isNot: null
      }
    }
  }) {
    id
    resolved
    approved
    reason
    request {
      id
      timecreated
      email
      issue
      orderid
      cashcode
      translink
      repreq
      otherissue
      evidence {
        id
        timeupload
        origname
        ETag
        key
        Location
        originid
      }
    }
  }
}

Logs
ransform.js:193:12)
  engine     at writeOrBuffer (_stream_writable.js:352:12)
  engine     at LineStream.Writable.write (_stream_writable.js:303:10)
  engine     at Socket.ondata (_stream_readable.js:719:22)
  engine     at Socket.emit (events.js:315:20)  {"timestamp":"Feb 01 12:15:54.500","level":"ERROR","fields":{"message":"PANIC","reason":"index out of bounds: the len is 1 but the index is 1","file":"C:\\Users\\runneradmin\\.cargo\\git\\checkouts\\quaint-9f01e008b9a89c14\\2d8c9c7\\src\\connector\\postgres\\error.rs","line":138,"column":29},"target":"query_engine"}
  engine {
  engine   error: Error: read ECONNRESET
  engine       at TCP.onStreamRead (internal/stream_base_commons.js:209:20) {
  engine     errno: -4077,
  engine     code: 'ECONNRESET',
  engine     syscall: 'read'
  engine   }
  engine }
  engine {
  engine   error: Error: connect ECONNREFUSED <IP_ADDRESS>:59118
  engine       at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
  engine     errno: -4078,
  engine     code: 'ECONNREFUSED',
  engine     syscall: 'connect',
  engine     address: '<IP_ADDRESS>',
  engine     port: 59118
  engine   }
  engine }
  engine There is a child that still runs and we want to start again
  engine { cwd: 'C:\\Users\\arifa\\Desktop\\Projects\\supplied-form\\prisma' }
  engine Search for Query Engine in C:\Users\arifa\Desktop\Projects\supplied-form\node_modules\.prisma\client
  engine { flags: [ '--enable-raw-queries' ] }
  engine port: 59122
  engine stdout  Starting a postgresql pool with 17 connections.
  engine stdout  Started http server on http://<IP_ADDRESS>:59122
  engine Search for Query Engine in C:\Users\arifa\Desktop\Projects\supplied-form\node_modules\.prisma\client
  engine Client Version: 2.15.0
  engine Engine Version: query-engine e51dc3b5a9ee790a07104bec1c9477d51740fe54
  engine Active provider: postgresql
  engine stdout  PANIC in C:\Users\runneradmin\.cargo\git\checkouts\quaint-9f01e008b9a89c14\2d8c9c7\src\connector\postgres\error.rs:138:29
index out of bounds: the len is 1 but the index is 1
  engine TypeError: this.currentRequestPromise.cancel is not a function
  engine     at NodeEngine.handlePanic (C:\Users\arifa\Desktop\Projects\supplied-form\node_modules\@prisma\client\runtime\index.js:26519:36)
  engine     at NodeEngine.setError (C:\Users\arifa\Desktop\Projects\supplied-form\node_modules\@prisma\client\runtime\index.js:26465:16)
  engine     at LineStream.<anonymous> (C:\Users\arifa\Desktop\Projects\supplied-form\node_modules\@prisma\client\runtime\index.js:26760:24)
  engine     at LineStream.emit (events.js:315:20)
  engine     at addChunk (_stream_readable.js:309:12)
  engine     at readableAddChunk (_stream_readable.js:284:9)
  engine     at LineStream.Readable.push (_stream_readable.js:223:10)
  engine     at LineStream.Transform.push (_stream_transform.js:166:32)
  engine     at LineStream._pushBuffer (C:\Users\arifa\Desktop\Projects\supplied-form\node_modules\@prisma\client\runtime\index.js:23721:19)
  engine     at LineStream._transform (C:\Users\arifa\Desktop\Projects\supplied-form\node_modules\@prisma\client\runtime\index.js:23715:10)
  engine     at LineStream.Transform._read (_stream_transform.js:205:10)
  engine     at LineStream.Transform._write (_stream_transform.js:193:12)
  engine     at writeOrBuffer (_stream_writable.js:352:12)
  engine     at LineStream.Writable.write (_stream_writable.js:303:10)
  engine     at Socket.ondata (_stream_readable.js:719:22)
  engine     at Socket.emit (events.js:315:20)  {"timestamp":"Feb 01 12:15:55.278","level":"ERROR","fields":{"message":"PANIC","reason":"index out of bounds: the len is 1 but the index is 1","file":"C:\\Users\\runneradmin\\.cargo\\git\\checkouts\\quaint-9f01e008b9a89c14\\2d8c9c7\\src\\connector\\postgres\\error.rs","line":138,"column":29},"target":"query_engine"}
  engine {
  engine   error: Error: read ECONNRESET
  engine       at TCP.onStreamRead (internal/stream_base_commons.js:209:20) {
  engine     errno: -4077,
  engine     code: 'ECONNRESET',
  engine     syscall: 'read'
  engine   }
  engine }

Client Snippet
const issues = await prisma.issue.findMany({
    where: {
      resolved: false,
      message: null,
      request: { evidence: { isNot: null } },
    },
    include: { request: { include: { evidence: true } } },
  });

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

generator client {
  provider = "prisma-client-js"
}

model Request {
  id          String   @id @default(uuid())
  timecreated DateTime @default(now())
  email       String
  issue       String
  orderid     String
  cashcode    String?
  translink   String?
  repreq      Int?
  otherissue  String?
  evidence    File?
  Issue       Issue?

  @@map(name: "REQUESTS")
}

model File {
  id         String   @id
  timeupload DateTime @default(now())
  origname   String
  ETag       String
  key        String
  Location   String
  origin     Request  @relation(fields: [originid], references: [id])
  originid   String

  @@map(name: "FILES")
}

model Issue {
  id       String   @id
  resolved Boolean
  approved Boolean?
  reason   String?
  message  Message?
  request  Request  @relation(fields: [id], references: [id])

  @@map(name: "ISSUES")
}

model Message {
  id       String   @id
  timesent DateTime
  issueid  String
  issue    Issue    @relation(fields: [issueid], references: [id])

  @@map(name: "MESSAGES")
}

Hey @arifali123
Can you please try this with the 2.16 release and tell us if this is already fixed? We did some recent fixes on that area so this might be already addressed.

I am going to close this as its been 3 months now and there is no activity here.
Please reply if you want us to take another look.


HBASE-23828 - Remove unused hadoop.guava.version from pom.xml

<hadoop.guava.version>11.0.2</hadoop.guava.version> is not used anywhere. It was added in https://github.com/apache/hbase/commit/0e95a8a0ae24b0d19b391d49794d6716a8e86bcd , when hbase-backup was using it. When it got removed in hbase-backup, this was forgotten. Static analyzers is now flagging hbase as there is a CVE for guava older versions.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  6s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+1 :green_heart:
mvninstall
6m  2s
master passed

+1 :green_heart:
compile
3m 20s
master passed

+1 :green_heart:
shadedjars
5m  8s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 58s
master passed

_ Patch Compile Tests _

-1 :x:
mvninstall
0m  8s
root in the patch failed.

-1 :x:
compile
0m  7s
root in the patch failed.

-1 :x:
javac
0m  7s
root in the patch failed.

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

-1 :x:
shadedjars
0m  5s
patch has 12 errors when building our shaded downstream artifacts.

-1 :x:
hadoopcheck
0m  5s
The patch causes 12 errors with Hadoop v2.8.5.

-1 :x:
hadoopcheck
0m 11s
The patch causes 12 errors with Hadoop v2.9.2.

-1 :x:
javadoc
0m 10s
root in the patch failed.

_ Other Tests _

-1 :x:
unit
0m 10s
root in the patch failed.

+0 :ok:
asflicense
0m 11s
ASF License check generated no output?

26m 50s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1163

Optional Tests
dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile

uname
Linux 9aacac1e2af9 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1163/out/precommit/personality/provided.sh

git revision
master / 12f98bc50e

Default Java
1.8.0_181

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/patch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/patch-compile-root.txt

javac
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/patch-compile-root.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/patch-shadedjars.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/patch-javac-2.8.5.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/patch-javac-2.9.2.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/patch-javadoc-root.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/testReport/

Max. process+thread count
86 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1163/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

It seems that this property is still used in the hadoop-2.0 profile of hbase-backup.

Yes, that's a big mis on my part, sorry, I'm looking into it...


Multilanguage support docs

New Multilanguage support section added to the main Readme.
Lokalise sponsorship added to the translation Readme.

All of this looks good to me, thanks a lot !


[WEB] Images loaded into UI from network doesn't apply EXIF rotation

I've seen several issues from the past that were addressing similar issues for iOS and Android - they were already fixed.
Sample data
An image file took on an iPhone that contains EXIF rotation 180 value. Full EXIF:
Camera make : Apple
Camera model : iPhone 7
Date/Time :2018/08/24 08:25:22
Resolution : 4032 x 3024
Orientation : rotate 180
Flash used : No
Focal length : 4.0mm (35mm equivalent 28mm)
Exposure time : 0.0004 s (1/2283)
Aperture : f/1.8ISO equiv. : 4000
Whitebalance : Auto
Metering Mode : pattern
Exposure : program (auto)
GPS Latitude :N 43º 0' 34.15"GPS
Longitude :E 17º 16' 4.81"GPS
Altitude : 5.26m

Steps to reproduce

Create an empty Flutter Web project
Create one widget Image.network('URL to the image');

Observed

Image is displayed without EXIF rotation being applied

Expected

Image is rotated according to the stored rotation value

Other

The same file, reproduction scenario in Flutter Android behaves correctly - image is rotated.

Thanks for reporting. Unfortunately this is only possible by decoding image file. Due to cross-origin restrictions on the web, it is not possible unless browsers provide support or the image is an asset (non-network). We will forward request to Fugu/Chrome team to prioritize. See https://developer.mozilla.org/en-US/docs/Web/CSS/image-orientation. I'll leave issue open for now.

On iOS 14, by default images are HEIC, which isn't supported yet https://github.com/flutter/flutter/issues/20522 hence i can't test this

Was able to reproduce on master channel, following the steps in Rotated image on Flutter web with CanvasKit #70620.
flutter doctor -v
[✓] Flutter (Channel master, 1.24.0-8.0.pre.267, on Mac OS X 10.15.7 19H2
    darwin-x64, locale en)
    • Flutter version 1.24.0-8.0.pre.267 at
      /Users/pedromassango/dev/SDKs/flutter_master
    • Framework revision 22e576fa26 (11 hours ago), 2020-11-16 18:48:03 -0500
    • Engine revision f0e80100f7
    • Dart version 2.12.0 (build 2.12.0-49.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • 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
      1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 51.0.3
    • Dart plugin version 202.8070

[✓] VS Code (version 1.51.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (4 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86    • Android 11
      (API 30) (emulator)
    • macOS (desktop)             • macos         • darwin-x64     • Mac OS X
      10.15.7 19H2 darwin-x64
    • Web Server (web)            • web-server    • web-javascript • Flutter
      Tools
    • Chrome (web)                • chrome        • web-javascript • Google
      Chrome 86.0.4240.198

• No issues found!

Remove labels based on https://github.com/flutter/flutter/issues/70620#issuecomment-730379278

duplicate of https://github.com/flutter/flutter/issues/53820


feedback for ci/cd pipeline using azure devops

[Enter feedback here]
nice

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

ID: 507afae4-129d-4da3-b559-fbd5f93c2a06
Version Independent ID: 507afae4-129d-4da3-b559-fbd5f93c2a06
Content: CI/CD baseline architecture with Azure Pipelines - Azure Example Scenarios
Content Source: docs/example-scenario/apps/devops-dotnet-baseline.yml
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @RobBagby
Microsoft Alias: robbag

Thank you @yakkantisravs for the positive feedback.  Hope you have a wonderful week.
#please-close

Resolved


update dmtet vertices

multiplying the vertices of DMTet by -1.0 to rectify the results

Thanks for the contribution!


Undocumented change to workspaces?

I followed the workspaces documentation with versions 0.4.3 and 0.4.4, and it seems that importing modules from the same workspace is broken (perhaps only for certain directory structures?) in recent versions, whereas 0.3.5 worked exactly as expected.
- rootdir/
    - pyproject.toml (has tool.uv.workspace.members which contains 'common' and 'thing')
    - libs/
        - common/
            - pyproject.toml
            - src/
                - common/
                    - __init__.py etc
    - services/
        - thing/
            - pyproject.toml (has tool.uv.sources with common = {workspace = true})
            - some_script.py

some_script.py:
import foo from common

command: uv run --refresh --package=thing services/thing/some_script.py

v0.4.x: Module common not found
v0.3.5: works

I've been clearing the cache at every step of the investigation, deleting uv.lock, re-running uv sync, and also using the --refresh flag when calling uv run.
One last interesting tidbit.  When I switch from 0.3.5 back up to 0.4.4, clean the cache, delete the lockfile, and then run uv sync --package=thing, it deletes the common dependency.  So for some reason, it's not even recognizing it as a dependency despite it being in the dependencies array, and also having a tool.uv.sources callout.
It looks like there were significant changes at 0.4.0, so maybe something fundamental regressed there.  I read through changelogs and docs and couldn't get to the bottom of it, though.

Is common declared as a dependency in rootdir/services/thing/pyproject.toml? Or only at the root?

If you can help put together a small reproducible example I'm happy to help.

It's declared a dependency only on the leaf, not the root.  Would making it one at the root help?  And sure, I can try to put together a reproducible example.

Yeah I would only expect it to be declared as a dependency in rootdir/services/thing/pyproject.toml, and not in the root -- so that sounds right. Was just a guess. A small reproducible example would help a ton, thanks.


Error Updating Stack referencing inline Lambda and Node v10 runtime

Description:
Seeing CREATE_FAILED error when template defines an inline lambda function against the nodejs10.x runtime
Steps to reproduce the issue:

Lauch a cloud formation stack referencing a template with an inline lambda function against the nodejs.x runtime. (example attached)

Observed result:
CREATE_FAILED error along with this error:  ZipFile can only be used when Runtime is set to either of nodejs, nodejs4.3, nodejs6.10, nodejs8.10, python2.7, python3.6, python3.7.
Seems similar to https://forums.aws.amazon.com/thread.jspa?messageID=841075&tstart=0
Expected result:
An updated stack and associated lambda function running against nodejs10.x runtime

This is an issue with the CloudFormation resource. I brought this up internally with the CloudFormation team.
The only workaround that I can suggest in the meantime is to deploy a function using NodeJS 8 then switch the runtime to 10 via the console or AWS CLI.
Closing as we can't do anything more about this; this feature will work once CFN releases support for the new runtime.

Thank you, @keetonian for the explanation. Do you know where I might be able to track this issue with the CloudFormation team and/or get an ETA?

@mattmar10 I would recommend opening a case with AWS Support; they should be able to notify you when the feature is released.


Enable sharing of schema.json in published android maven packages

Is your feature request related to a problem? Please describe.
Ideally we would like to be able to share our schema.json and other apollo metadata across our maven published android libraries.
Describe the solution you'd like
Currently using the apolloMetadata configuration such as:
implementation "com.example.mypublishedlibrary:0.0.1"
apolloMetadata "com.example.mypublishedlibrary:0.0.1"

With a local or remote maven published android library results in the following error:
Execution failed for task ':app:generateDebugServiceApolloSources'.
> Failed to calculate the value of task ':app:generateDebugServiceApolloSources' property 'generateMetadata'.
   > Could not resolve all files for configuration ':app:apolloDebugServiceConsumer'.
      > Could not resolve com.example.mypublishedlibrary:0.0.1.
        Required by:
            project :app
         > No matching variant of com.example.mypublishedlibrary was found. The consumer was configured to find a usage of 'apollo-metadata' of a component, as well as attribute 'com.apollographql.variant' with value 'debug', attribute 'com.apollographql.service' with value 'service' but:
             - Variant 'compile' capability com.example.mypublishedlibrary:
                 - Incompatible because this component declares an API of a component and the consumer needed a usage of 'apollo-metadata' of a component
                 - Other compatible attributes:
                     - Doesn't say anything about com.apollographql.service (required 'service')
                     - Doesn't say anything about com.apollographql.variant (required 'debug')
             - Variant 'enforced-platform-compile' capability com.example.mypublishedlibrary-derived-enforced-platform:0.0.1:
                 - Incompatible because this component declares an API of a component and the consumer needed a usage of 'apollo-metadata' of a component
                 - Other compatible attributes:
                     - Doesn't say anything about com.apollographql.service (required 'service')
                     - Doesn't say anything about com.apollographql.variant (required 'debug')
             - Variant 'enforced-platform-runtime' capability com.example.mypublishedlibrary-derived-enforced-platform:0.0.1:
                 - Incompatible because this component declares a runtime of a component and the consumer needed a usage of 'apollo-metadata' of a component
                 - Other compatible attributes:
                     - Doesn't say anything about com.apollographql.service (required 'service')
                     - Doesn't say anything about com.apollographql.variant (required 'debug')
             - Variant 'platform-compile' capability com.example.mypublishedlibrary-derived-platform:0.0.1:
                 - Incompatible because this component declares an API of a component and the consumer needed a usage of 'apollo-metadata' of a component
                 - Other compatible attributes:
                     - Doesn't say anything about com.apollographql.service (required 'service')
                     - Doesn't say anything about com.apollographql.variant (required 'debug')
             - Variant 'platform-runtime' capability com.example.mypublishedlibrary-derived-platform:0.0.1:
                 - Incompatible because this component declares a runtime of a component and the consumer needed a usage of 'apollo-metadata' of a component
                 - Other compatible attributes:
                     - Doesn't say anything about com.apollographql.service (required 'service')
                     - Doesn't say anything about com.apollographql.variant (required 'debug')
             - Variant 'runtime' capability com.example.mypublishedlibrary:0.0.1:
                 - Incompatible because this component declares a runtime of a component and the consumer needed a usage of 'apollo-metadata' of a component
                 - Other compatible attributes:
                     - Doesn't say anything about com.apollographql.service (required 'service')
                     - Doesn't say anything about com.apollographql.variant (required 'debug')

Using the module directly such as:
implementation project(":mylibrary")
apolloMetadata project(":mylibrary")

Works as intended with the exact same code.
Is there a way get apolloMetadata working with a maven published android library? Is there a recommended maven publishing configuration that allows for this use case?
We do have an alternative solution using gradle tasks to copy and delete the schema.json from the published dependency during build when generating apollo sources. Ideally we would like to use apolloMetadata if possible! Thank you!

Hi 👋
Indeed, Apollo metadata publication isn't handled at the moment. Doing so will open a whole new class of interesting questions such as binary compatibility, matching schemas, Gradle variant selection, etc...

We do have an alternative solution using gradle tasks to copy and delete the schema.json from the published dependency during build when generating apollo sources.

Interesting, does that mean you actually publish a apollo-metadata.jar where you get the schema from ? Is that repository public by any chance ? Maybe adding support for publication could be added without changing too many things if we enforce the same plugin versions everywhere...

Hello 👋

Interesting, does that mean you actually publish a apollo-metadata.jar

We're not currently doing this but instead are including the schema.json in the published artifact by adding the graphql directory to the resources source set.
sourceSets {
    main.resources.srcDirs += 'src/main/graphql/com/example/mypublishedlibrary'
}

Then in the consumer build gradle we pull in the schema during any ApolloSources task:
task copySchema(type: Copy) {
    from { getSchemaFile() }
    into project.file('src/main/graphql')
}
task deleteSchema(type: Delete) {
    delete project.file('src/main/graphql/schema.json')
}
this.afterEvaluate { Project project ->
    def apolloSourcesTaskNames = project.tasks.getNames().findAll { it.contains("ApolloSources") }
    apolloSourcesTaskNames.each { String taskName ->
        def generateApolloSourcesTask = project.tasks.getByName(taskName)
        generateApolloSourcesTask.dependsOn(copySchema)
        generateApolloSourcesTask.finalizedBy(deleteSchema)
    }
}

Is that repository public by any chance

It is not public unfortunately, but the steps described above are more or less the approach.

@martinbonnin
We are facing the same issue and I wonder if there Is any update or alternative solution?

If you're familiar with Gradle APIs, the solution to this would be to add the metadata.json to the publication. This might or might not be an easy thing to do, not sure at this point.
If that's not easy, a workaround would be to distribute the schema "out of band", like @chrisr-ifit is doing and generate classes in each module with a separate package name. It's sub optimal because it will generate duplicate classes but that might be good enough until proper maven publication is handled

First drop there: https://github.com/apollographql/apollo-kotlin/pull/3904
Let me know what you think. If everything goes well, it should hit the SNAPSHOTS later this week.


fix(site-detection): ignore domains

Please ensure your pull request adheres to the following guidelines:

[ ] make sure to link the related issues in this description. Or if there's no issue created, make sure you
describe here the problem you're solving.
[ ] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

If the PR is changing the API specification:

[ ] make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready
yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
[ ] make sure you add at least one example of the request and response.

If the PR is changing the API implementation or an entity exposed through the API:

[ ] make sure you update the API specification and the examples to reflect the changes.

If the PR is introducing a new audit type:

[ ] make sure you update the API specification with the type, schema of the audit result and an example

Related Issues
Thanks for contributing!

:tada: This issue has been resolved in version 1.63.3 :tada:
The release is available on:

v1.63.3
GitHub release

Your semantic-release bot :package::rocket:


Feature request: Do not attempt to reconnect

I've put some authorization logic inside protoo server. When auth fails, client still tries to connect again, which isn't what I want.
At the same time, once client gets connected and connection is lost, I want it to try to reconnect.

Sorry for the delay.

That's not true. Websocket has a close method that accepts a code, where one can specify 4000 https://developer.mozilla.org/en-US/docs/Web/API/WebSocket#close()

Yes, but you can just use it in an already established WS connection. Here we were talking about rejecting a WS handshake request, which is just a HTTP GET request. And it does not matter how the server rejects it (which status code or HTTP headers) since the browser does not expose a JS API to inspect the HTTP rejection response.

Alternatively, it is possible to use X-WebSocket-Reject-Reason for specifying reason.

I don't think such a header is a standard nor that browsers implement it:
https://stackoverflow.com/questions/10560591/nodejs-websockets-reject-the-connection-with-a-message


Bug: android-chrome-manifest.json vs. manifest.json

Hello,
you are generating the file manifest.json but in the generated HTML you reference android-chrome-manifest.json guess one of this two names is wrong? :)

Hey @di5abled, yes that was a recent change, we must have missed updating the HTML reference - nice find! I see you've forked and fixed it, how about a PR? Thanks :+1:

Fixed in<EMAIL_ADDRESS>


prepare release 2.2.3

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.2@7d9c974). Click here to learn what that means.
The diff coverage is 100%.

@@          Coverage Diff           @@
##             2.2    #6528   +/-   ##
======================================
  Coverage       ?   83.21%
  Complexity     ?    12821
======================================
  Files          ?     1483
  Lines          ?    48581
  Branches       ?     5915
======================================
  Hits           ?    40426
  Misses         ?     5397
  Partials       ?     2758

Impacted Files
Coverage Δ
Complexity Δ

core/src/main/java/io/crate/Version.java
71.42% <100%> (ø)
12 <0> (?)

Continue to review full report at Codecov.

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


docs: s/1.6/1.7/g

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


Possible to enter iDRAC username and password on the web?

Hi,
first of all, its a great work. Thanks for this tool!
Is it possible to store iDRAC username and password NOT in the Docker file (because of security reasons)?
I would prefer to enter it on demand on the guacamole web interface. Is this possible or planned?
Regards

It's not possible but you could use Docker secrets instead: https://docs.docker.com/compose/use-secrets/


Use Websockets to connect to TMI

Is your feature request related to a problem? Please describe.
In the recent weeks IRC endpoints of TMI have been really unstable for EU. While the websocket connections stayed stable. Webchat worked as usual and bots using websockets were more reliable.
Describe the solution you'd like
Either make it an option to use websockets instead of IRC or use websockets permanently everywhere since that is what webchat uses and IMO less people complain about chatterino when webchat also won't work.
Describe alternatives you've considered
Use webchat

Closing since chat over EventSub will be an alternative instead, which would use websockets rather than IRC.
https://github.com/Chatterino/chatterino2/pull/4962
https://github.com/Chatterino/chatterino2/issues/5128


fix for offset check when month or year changes

If the local time is at the start of the day but the universal time is the previous day a month or year check is required.
Fix for https://github.com/massivefermion/birl/issues/16

Thanks!


Update docs for new version

@alexander0042 Just getting ahead of the curve and create a branch where you can document the changes coming in the next release. The only thing changed so far is the version number in the OpenAPI spec.
This release should

Fix #266 .
Fix #283
Fix #284
It also should address the issues seen in #229

Things to update before this can be merged in:

[x] Changelog
[x] API documentation (if needed)
[x] OpenAPI spec (if needed)
[x] Recent updates section on the homepage
[x] Roadmap (if needed)

Great idea to start pulling this together! Just released v2.1 live on the dev endpoint, and I want to see how it does for a few days, but so long as it's stable it should be ready for prime time

Feel free to update the docs on that branch for the new update.
I just did a quick test on the dev endpoint and I noticed that pressure and apparent temperature are the same as the production endpoint. Are you still working on those fixes or they just get missed?

@alexander0042 Feel free to update the docs for anything related to the update. I also added a v2.1 section to the changelog so you can start adding the changes there.
When I was testing the development server there were some issues which I thought were going to be fixed in this version but don't seem to be fixed. Namely these issues:

#269
#268
#265
#246

Is it just the case of the version on dev currently doesn't have these fixes or are they not going to be included in v2.1 and will come afterwards?

I noticed there were a few things in the repo which weren't in the roadmap so I went and added them. You can always remove if you don't want them there are re-order things if needed.

@alexander0042 This PR should be good to review now as everything has been updated. In the changelog I had initially marked #269, #268, #265 and #246 as being fixed but considering the issues that have popped up today I think 2.1 can be launched and the other issues be fixed in a 2.1.1 version.
The release date of 2.1 still needs to be added.

Thanks for the ping! I'm always tempted to try to get everything in one big release, but you make a great point and it's better just to push this out to fix the data stability issues and then go from there. Data ingest has been a whole can of worms, but I really think this approach will scale for the future, and will also make it much easier for people to eventually run it on their own!

Thanks for the ping! I'm always tempted to try to get everything in one big release, but you make a great point and it's better just to push this out to fix the data stability issues and then go from there. Data ingest has been a whole can of worms, but I really think this approach will scale for the future, and will also make it much easier for people to eventually run it on their own!

As much as a big release would be nice imo any stability issues should get pushed out as soon as their ready. For those other issues it would be nice if they were fixed I'd rather the stability issues be fixed first and have those other issues be fixed afterwards.


fix(TDI-39525): Missing properties for Wizard

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-39525
What is the new behavior?
Please check if the PR fulfills these requirements

[X] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:
Sonar results


<EMAIL_ADDRESS>

<EMAIL_ADDRESS>
Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[x] I have added the 'writer impact' label
[x] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@saechintha

https://github.com/saechintha/docs/pull/1#issue-841341121


iOS, macOS support based on vger

Some time ago I stumbled upon https://github.com/audulus/vger and seeing you missing support for Apple ecosystem I thought you might give it a try (or not).
Or maybe even some broader cooperation might be feasible...

vger seems to be a graphics library gust like this. So I highly doubt it can be used for Mac and iOS support in this project. Also, Mac support was moved to the attic in November 2020, so I doubt it would be readded anytime soon.

I'm a ok with bringing mac support in, but I don't know anything about the ecosystem and don't have a mac.

I am going to close this issue, for now, but I'll keep my eyes open for anything new.

@cnlohr yep, that is a pragmatic decision. I still think vger could be a good choice as sort of a "backend" (or even the two project could merge into one...) but does not have enough time to make a PR :cry:.
@audulus thoughts?


Document tag edge-cases

Specifically I'm wondering:
Will adding tags replace existing tags on an image?
Will adding an existing tag fail?

@bdelavega-maralytix Hi Bill, thank you for your interest in the action.
The intention of this action was to provide a way to add a new tag to an image in a registry in a way that does not modify the image or create a new image: it should add a new tag only.
Q: Will adding tags replace existing tags on an image?
A: No, existing tags will remain as-is
Q: Will adding an existing tag fail?
A: That depends on the behaviour of the registry. Some registries support immutable tags which would block any attempt to re-use a tag, however, most registries (including Docker's and GitHub's) allow for a tag to be re-used. Therefore, an attempt to use a tag for a second time, will "move" the tag.
What's your use case: are you hoping to prevent a tag from being re-assigned? I could add an option to guard against that, however, I suspect that's something you'd typically want to happen at the registry level (due to the potential for race conditions when interacting with the registry API, which is what this action does).

Actually, it might be helpful for me to describe how a Docker registry works. An image is represented by a manifest: a manifest is stored in a repository at one or more locations. The manifest can be accessed using the digest hash (e.g: sha256:7ea108539c53d2e601b17c23d9f3b0aacd627c3873eb1ef52187dd71a41ba061) and by one or more tags (e.g: latest v1.0.0).
This action uses the Docker registry API to create one or more tags using the target image's manifest. Therefore, unless you specify tags that already exist in your image's repository there will only be the creation of new tags. The logic of the action is:

Download a copy of the target image manifest
Push a copy of the image manifest to each of the specified tags

Thanks a ton for answering so quickly!
My use case is this: our build process puts images into a private GitHub registry with some tags.  Later on, if some tests pass, the image is deployed to a staging environment. Later it may or may not go to production. I want to tag the images when they're deployed (e.g. with stage), so that I can identify old, unused images to delete. We plan to keep a few older images in case we need to rollback.
Your answers fit the need well.
I still need to find a way to remove tags, but that's less sensitive because it will be a separate process from the build/test/deploy scripts. Probably a daily cron job.

@bdelavega-maralytix You might find snok/container-retention-policy helpful. I haven't used it personally, however, after a brief look around the documentation, it looks ideal for cleaning up stale images. The untagged option would probably work well alongside your use of the stage tag.


[Event Request] Reminder Header - procedure InsertLines - before insert additional fee line

We would like to have a new event OnBeforeInsertReminderAdditionalFeeLine in procedure InsertLines in table Reminder Header.
The existing event OnBeforeInsertReminderLine does not work because this event is called in multiple places. We need an event specifically for additional fee, which includes the current Reminder Header record.
The event OnBeforeInsertReminderTextLine does not work either. This seems to be a bug, see also issue #14381
    procedure InsertLines()
    ........
                ReminderLine.Validate(Amount, AdditionalFee);
                ReminderLine."Line Type" := ReminderLine."Line Type"::"Additional Fee";
                OnBeforeInsertReminderTextLine(ReminderLine, ReminderText, ReminderHeader); // <-- incorrect event? ReminderHeader parameter will be empty
                OnBeforeInsertReminderAdditionalFeeLine(ReminderLine, Rec); // <-- NEW EVENT
                OnBeforeInsertReminderLine(ReminderLine);
                ReminderLine.Insert();
                if TransferExtendedText.ReminderCheckIfAnyExtText(ReminderLine, false) then
                    TransferExtendedText.InsertReminderExtText(ReminderLine);
                ........

    [IntegrationEvent(false, false)]
    local procedure OnBeforeInsertReminderAdditionalFeeLine(var ReminderLine: Record "Reminder Line"; var ReminderHeader: Record "Reminder Header")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Localized Docs Link

Related Issue: #239

@micahalcorn @sparrowDom Ok if we merge this PR in?

@franckc sure, it looks good at a glance. I would recommend pushing a branch in the future rather than forking so that it's easier for us to pull and run locally. 🙂

@micahalcorn
Thanks, I don't have the access to push. I think someone has to add me as a contributor.

@ZaHuPro I think I added you, so just let me know if you don't find the email. 📬

Nice job @ZaHuPro, looks good to me. And congrats on the first PR 👍

@micahalcorn Thanks, I got the mail upcoming fix I will push into a branch to a folk branch

@sparrowDom  Thanks


no modules named "torch_dwconv"

i've seen the following code in file "model.py",but i can't see where is the "torch_dwconv"
from torch_dwconv import depthwise_conv2d, DepthwiseConv2d
so could please tell me where can i see the file "torch_dwconv"?

麻烦问一下你现在解决了吗我也被torch_dwconv难住了

are you finding this one: https://github.com/rosinality/depthwise-conv-pytorch

For people who are not willing to install the dependency, go check this thread about depth-wise conv


Terria doesn't show the legend

I installed Terria with the purpose of showing my data managed by OpenDataCube (via OWS) and the result is as follows:

My probleml, as you can see, is that I can't see the legend on the left (which I once saw).
Who can help me?

The problem was with OWS and, in particular, with the configuration file called "ows_cfg.py".


ZIO-inspired error handling

Review Abort, Result, and related kyo-combinators methods to follow a naming pattern similar to ZIO's since it's quite mature and it would be helpful to people coming from ZIO. We should also review whether the APIs provide similar semantics to ZIO. Context: https://github.com/getkyo/kyo/pull/644#discussion_r1749345497

I believe the ZIO model for errors is brilliant and kyo would greatly benefit from it:

typed channel for recoverable/expected errors
untyped channel for unrecoverable/unexpected failures

Btw, have you @fwbrasil considered constraining Result errors only to Exception? Like
opaque type Result[+E <: Exception, +A] >: (Success[A] | Failure[E]) = Success[A] | Failure[E]

E stands for those typed, recoverable/expected errors, right, but in my experience they should still always be subclasses of Exception for good interoperability with the JVM and ecosystem around it.

Btw, have you @fwbrasil considered constraining Result errors only to Exception?

I think @hearnadam also suggested that some time ago. The intent was make Result have the features of both Either and Try and allow Abort for any value like in ZIO. I haven't much benefit in the approach yet, though. There's only the swap method that might not make sense if we add this restriction. @johnhungerford can you share you thoughts? I added swap inspired in the equivalent combinator method.

I believe the ZIO model for errors is brilliant and kyo would greatly benefit from it:

typed channel for recoverable/expected errors
untyped channel for unrecoverable/unexpected failures

I think that's what have already given that Result and Abort handle both typed (Result.fail) and untyped failures (Result.panic).

I definitely would not want to restrict errors to Exception in kyo.  For instance, we should be able to use Abort as an Option-like effect by aborting with Maybe.Empty (or whatever it's called), which is not an exception.

I don't find Abort[Maybe.Empty] very useful. In most cases, I prefer returning a regular Maybe so the caller has to handle the effect immediately and, in cases like a missing config, a specific exception seems better since it can communicate the cause of the abort more clearly. @johnhungerford do you mind sharing more on why you feel that's a useful pattern? (to be honest, I'm still struggling to see the value of Abort[Throwable] as well 🙃)

A < (S & Abort[Maybe.Empty]) is equivalent to OptionT[S, A]: it combines the Option monad with other effects. I find this very useful in any case where I need to abstract over the composition of optional values while also abstracting over other effects. For instance, say you are writing a function to generate a result from multiple functions that return optional values asynchronously. In this case, you may want to lift those values to < Abort[Maybe.Empty] and let any empty value short-circuit the logic.
I agree in this case you probably want to then convert the A < (Abort[Maybe.Empty] & Async) back to an Option[A] < Async at the end of your function, but you still need to use Abort within the function. I also agree than in more cases you will want to preserve some information along with the missing value, but I have definitely encountered plenty of situations where I'm dealing with straightforwardly optional values. I've used this pattern plenty in ZIO.

That seems like an abuse of Abort, whose purpose is to track typed, recoverable/expected errors. It's not that I'm morally condemning writing code like that, it will "work", but maybe it is a symptom of a lack of an OptionT-like effect in Kyo?
Obviously you have to do it like that in ZIO, because that's just how ZIO is, you don't have much choise. But isn't the point of Kyo to be more flexible, making it easy to add such an effect, which would be analogous to OptionT?

If Abort were simply for errors, it would be called Error. Abort is for "aborting," or short-circuiting a computation. Why would it matter whether this is for errors or empty values? There used to be a separate Option effect in Kyo, but it was removed, since was basically just an alias for Abort[None].
A < Abort[B], represents a computation that may complete with a value of type A or abort with a value of type B. This way of thinking about aborts is consistent with both errors and options.
Again, in most cases I would probably handle A < Abort[Maybe.Empty] to Maybe[A] < Any at the end of a function, but I think it makes perfect sense to use Abort to abstract over short-circuiting missing values.

If Abort were simply for errors, it would be called Error.

Fair enough. @fwbrasil do you think kyo would benefit from an effect dedicated purely to typed recoverable/expected errors?

Fair enough. @fwbrasil do you think kyo would benefit from an effect dedicated purely to typed recoverable/expected errors?

Sorry I missed your question at the time. I also wasn't sure about this design decision but I feel we've reached good level of usability in Abort and Result without having to restrict failures to Throwable. I'm not sure if I understood your suggestion correctly but I'd prefer to avoid having two effects for error handling. Kyo's primitives are designed to be canonical and keeping the pending effect set compact is an important aspect for usability.
Anyone against closing this? We've made good progress in error handling and the scope of this issue seems too broad. Smaller issues for specific improvements would probably be more effective.

Anyone against closing this? We've made good progress in error handling and the scope of this issue seems too broad. Smaller issues for specific improvements would probably be more effective.

One final ask is an orDie style operator for Abort. This will enable translating APIs (Console comes to mind) where you may not care about failures: https://github.com/zio/zio/blob/series/2.x/core/shared/src/main/scala/zio/ZIO.scala#L1175-L1183

How about catchAll, catchSome, mapError, orElse? Was reaching for it the other day. It seems currently you have to runtheAbort` and handle every case which is quite verbose.

@ghostdogpr we have some methods in kyo-combinators for that:
val effect: String < Abort[Int | String | Throwable] = ???

val handled: Result[Int | String | Throwable, String] < Any = effect.handleAbort // I think this doesn't actually work yet
val handledString : Result[String, Unit] < Abort[Int | Throwable] = effect.handleSome[String]()
val caught: String < Any = effect.catchAbort(_.toString) // I think this doesn't work yet either
val caughtString: String < Abort[Int | Throwable] = effect.catchSome[String](v => v)

I elected not to include a mapAbort or mapSomeAbort simply because it's easy to use catchAbort
effect.catchSomeAbort[Int](i => Kyo.fail(i.toString))

@hearnadam I was just thinking we need orDie -- I can add that one


Api/sponsors implementation

I did it I think... I may have missed some good error handling and may have left a todo in there somewhere but I'll let you guys tell me if things still need to change

Unless I'm reading this wrong (which I definitely could be) the only travis errors I'm getting are for naming enum cases with a lowercase letter, which I do to match up with the variable name in the structs and the name of the api fields for decodable to work. Can we add a thing to ignore the rule for enums? I'm hoping that would be the easiest fix.


fix(install docs): consistency, grammar

Signed-off-by: Alex C-G<EMAIL_ADDRESS>Goals:

Consistency

Grammar

[x] check and update documentation, if required. See guide

Codecov Report
Base: 87.76% // Head: 85.16% // Decreases project coverage by -2.61% :warning:

Coverage data is based on head (be2141c) compared to base (26e072c).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1028      +/-   ##
==========================================
- Coverage   87.76%   85.16%   -2.61%
==========================================
  Files         155      155
  Lines        8061     8061
==========================================
- Hits         7075     6865     -210
- Misses        986     1196     +210

Flag
Coverage Δ

docarray
85.16% <100.00%> (-2.61%)
:arrow_down:

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

Impacted Files
Coverage Δ

docarray/__init__.py
77.77% <100.00%> (ø)

docarray/array/mixins/embed.py
9.89% <0.00%> (-82.42%)
:arrow_down:

docarray/array/mixins/evaluation.py
8.86% <0.00%> (-80.38%)
:arrow_down:

docarray/array/storage/memory/find.py
54.68% <0.00%> (-40.63%)
:arrow_down:

docarray/document/mixins/sugar.py
60.00% <0.00%> (-20.00%)
:arrow_down:

docarray/array/mixins/group.py
71.05% <0.00%> (-18.43%)
:arrow_down:

docarray/math/helper.py
67.64% <0.00%> (-17.65%)
:arrow_down:

docarray/math/distance/__init__.py
77.77% <0.00%> (-17.47%)
:arrow_down:

docarray/array/mixins/match.py
83.33% <0.00%> (-8.34%)
:arrow_down:

docarray/score/data.py
95.65% <0.00%> (-4.35%)
:arrow_down:

... and 17 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Search engine user agents (e.g. Googlebot)

https://techpatterns.com/forums/about304.html has a decent list of such user agents. (Thanks Rotxer)

I can take care of this. PR will be opened in a day or two.


Thaunomicon's progress is not working in Mc Eternal modpack

I am advanced in the Mc Eternal but it turns out that when I want to start with thaumcraft my progress is not marked, I got the book that comes out when you collect a crystal from the mod and sleep, but when I do the salismundis and make the book. I open the thaunomicon and it doesn't mark anything (not even the first lessons). Can someone help me??

Is the Thaumcraft 6


Support for Inbound emails by Amazon SES

+1! Amazon SES is quite widely used...I'd love to be able to use this package with it.

I think SES includes the MIME message (see https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-notifications-contents.html , so you should be able to use that with InboundEmail::fromMessage($mimeContent);

Confused. So no need for a ses driver?

Hi All,
I just submitted a PR to introduce SES support.

@ziming did you manage to solve this one?

+1


Profile pictures have incorrect hover state

Title line template: [Title]: Brief description
What package(s) are you using?

[x] Carbon for IBM Products (or Carbon for IBM Cloud & Cognitive)
[ ] Legacy/CDAI
[ ] Legacy/Security

Detailed description

Describe in detail the issue you're having.

Profile pictures should have no inherent hover state change on icons inside them. Doing so may become inaccessible and look visually incorrect.

Is this issue related to a specific component?

Profile pictures

What did you expect to happen? What happened instead? What would you like to see changed?

Nothing except a tooltip should appear when hovering.

What browser are you working in?

Firefox, Safari, Google Chrome

What version of the @carbon/ibm-products (or @carbon/ibm-cloud-cognitive)
package are you using?

Latest?

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

Additional information

Thanks for opening this issue @mitchellbernstein, it will be fixed with https://github.com/carbon-design-system/ibm-cloud-cognitive/pull/1745


[KYUUBI #1204] Enhance zookeeper authentication and acls

Why are the changes needed?

Please see #1204 for details.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

cc @zhouyifan279 can you help review this too

thanks, merged to master


[gha] split code gen unit tests out, bump unit test timeout by 10 minutes

Motivation
Prevent unit test timeouts, that will block prs from landing on CI.
Have you read the [Contributing Guidelines on pull requests]
Yes
Test Plan
CI, hopefully.
Related PRs
All of 'em you might want to land.
If targetting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

/priority high

/land


path_to_config_file.yaml

hello，Where can I see a reference example

Hi @DarylLei, thank you so much for reaching out. Today, we are going to release a more stable version of ChatLLaMA, with more detailed documentation. Thank you for your feedback, let us know if after the release there is still something missing or unclear.

Closing the issue since examples have been provided in the new readme #204.


Plugin Template: mutex not initialized correctly

I have written a Webworks plugin based off your excellent plugin template, in the course of that I found a bug: template_ndk.hpp defines two private member variables cond and mutex (see here).
In the corresponding constructor in template_ndk.cpp, these two are supposed to get initialized, but they aren't. Instead, new variables, which are local to the constructor, are declared (see here), which for me meant that the mutex was never correctly initialized, my thread synchronization acted weirdly and my app froze.
Long story short: in template_ndk.cpp, this:
		pthread_cond_t cond  = PTHREAD_COND_INITIALIZER;
		pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER;

should become this:
		cond  = PTHREAD_COND_INITIALIZER;
		mutex = PTHREAD_MUTEX_INITIALIZER;

Thanks for this (otherwise ;-) ) great template.

Yes I see that. We seem to have missed that in our tweaks to the template. Thanks for pointing it out.


Feature request: Improve performance for segmentation maps

Hi.
First, I would like to thank you for the great library. Very user-friendly and full of features. :)
I've noticed the overall process (augmentation of images, bounding boxes and segmentation maps) is spending most of its time on the segmentation maps.
In particular whichever augmenter is used, there is some significant overhead in transforming the seg map into a heat map, and then back to the seg map. Am wondering if it could be improved by doing it only when necessary, as some augmenters have no effect on the seg map (e.g. Add brightness) or could work directly on the seg map (e.g. Flip, Translate) ?
Thanks a lot !

Thanks for the praise!
Segmentation map augmentation is currently not exactly the fastest process. It uses heatmap augmentation as a proxy as that method was already implemented and tested. Usually it should convert the segmentation maps to heatmaps exactly once at the start of the pipeline and then convert back once at the end. So if you combine multiple augmenters (e.g. via Sequential) the conversion should only happens once (per augmentation run). Augmenters that don't affect segmentation maps should then not change these heatmaps in any way and not cost noteworthy performance.
Many augmenters could directly operate on the (integer-based) segmentation maps. It is planned to change that in the future, but it will be a rather big change, so it hasn't happened yet (SegmentationMapOnImage needs to be rewritten, various augmenters need new segmentation-map specific augmentation functions, all of these changes then have to be tested and the documentation will have to be updated for some methods).

Thanks. I look forward to it.
I leave the issue open until then ?

OK.

Thanks a lot for implementing it ! Much appreciated. :)


Couldn't load default plugin 'jpegtran

that's my gulpfile code :
gulp.task('img',function(){
gulp.src('img/**/*')
.pipe(imagemin())
.pipe(gulp.dest('dist/img'))
})
when i run the task ,it show me gulp-imagemin:Couldn't load default plugin 'jpegtran'
what's the problem is ?

What's your problem ?

sorry,i forget to confirm edit button

Should be reported on https://github.com/sindresorhus/gulp-imagemin/issues instead.


lto build

Description of the requested feature
lto is a obvious binary characteristic which works fine here on gentoo
Proposed configuration syntax
By adding:
-Clto=fat
Cembed-bitcode=yes
-Zdylib-lto
Additional context
No response

Given that there is currently no "official" package of eww anywhere, I'm unsure what exactly you're asking for here. Wouldn't enabling LTO and stuff like that optimally be a thing that the package declares, rather than the project itself?

Despite gentoo package has options (X , debug, wayland),  they could only be there to only constraint execution environment, not the binary generation itself.
No problem pushing at packaging level.


Handle empty hook files

Address code review comments of #729 and use @pytest.skipif.
⬆ @michaeljoseph @jcarbaugh
Resolves #632

Current coverage is 100% (diff: 100%)

Merging #862 into master will not change coverage

@@           master   #862   diff @@
====================================
  Files          16     16
  Lines         661    667     +6
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
+ Hits          661    667     +6
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 03dc984...457dc72


Button of the selected view isn't underlined.

How the button of the selected view looks like upon loading the page:

How the selected button should look like. Currently works only after you click it.

custom_header:
  hidden_tab_redirect: false
  shadow: false
  editor_warnings: false
  compact_mode: true
  button_text:
    options: '{{ time }}'
resources:
  - type: module
    url: /community_plugin/mini-media-player/mini-media-player-bundle.js
  - type: module
    url: /hacsfiles/mini-graph-card/mini-graph-card-bundle.js
  - type: js
    url: /local/synthwave-hass-extras.js
  - url: /community_plugin/custom-header/custom-header.js
    type: module
title: ''
views:
  - icon: 'mdi:home'
    panel: false
    path: default_view
    theme: Backend-selected
    title: Home
    badges: []
    cards:
      - entity: light.bedroom_lights
        theme: Backend-selected
        type: light
      - entities:
          - entity: light.bedside
          - entity: light.desk
          - entity: light.ceiling
        show_header_toggle: false
        title: Lights
        type: entities
      - entities:
          - entity: media_player.bedroom
            group: true
            type: 'custom:mini-media-player'
        type: entities
      - entity: weather.home
        theme: Backend-selected
        type: weather-forecast
      - entities:
          - entity: scene.chores
          - entity: scene.everyday
          - entity: scene.computer_time
        show_header_toggle: false
        title: Scene Selector
        type: entities
      - entities:
          - entity: sensor.czech_republic_coronavirus_confirmed
            icon: 'mdi:emoticon-neutral-outline'
            name: Confirmed
          - entity: sensor.czech_republic_coronavirus_current
            icon: 'mdi:emoticon-frown-outline'
            name: Current
          - entity: sensor.czech_republic_coronavirus_recovered
            icon: 'mdi:emoticon-happy-outline'
            name: Recovered
          - entity: sensor.czech_republic_coronavirus_deaths
            icon: 'mdi:emoticon-dead-outline'
            name: Deaths
        show_icon: true
        show_name: true
        show_state: true
        type: glance
        title: COVID-19
  - title: Lights
    path: lights
    icon: 'mdi:lightbulb'
    theme: synthwave
    badges: []
    cards: []

Using Home Assistant 0.106.4
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
Tried disabling the plugin and the issue doesn't persist, so perhaps it must be bug of the plugin.
Thank you very much for this plugin.

Please try the latest version and report back:
https://community.home-assistant.io/t/custom-header/155399/636

Fixed now. Thanks so much!


Feature request: add options to hide one/both scrollbars but still allow scrolling (no supress)

Feature request: add options to hide one/both scrollbars but still allow scrolling (no supress)

You can do this with just CSS. Please add following lines in any of your CSS files.
.ps-container > .ps-scrollbar-x-rail {
  visibility: hidden;
}
.ps-container > .ps-scrollbar-y-rail {
  visibility: hidden;
}

You can surely choose which scrollbar to hide by adding only one of them.
Thanks!


Custom type fixes

Appends the Value macro directly instead of calling .value and re-extracting the type spec.
For consistency, hoist maybe to the DSL as well so it can be used inside of blocks, just like filled.
Incorporates a variant of @ADStrovers repro spec from #423.
Resolves #419.
Resolves #423.

Thanks for taking care of this. I'm gonna release it today/tomorrow.


Regression with version 2.10.2

I get the following error :-(
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2332, in resolve
    return functools.reduce(getattr, self.attrs, module)
AttributeError: module 'jinja2.ext' has no attribute 'bable_extract'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/pot-create", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/dist-packages/lingua/extract.py", line 308, in main
    register_babel_plugins()
  File "/usr/local/lib/python3.7/dist-packages/lingua/extractors/babel.py", line 51, in register_babel_plugins
    extractor = entry_point.load(require=True)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2334, in resolve
    raise ImportError(str(exc))
ImportError: module 'jinja2.ext' has no attribute 'bable_extract'

It's babel_extract, not bable_extract.

oh, it's a typo in our setup.py ;/

oops, hold on

Fixed in 218e77d77da08f045672a2e2abb521ba5c73d2a1, we'll make a new release soon

2.10.3 released

Thanks :-)


Add recurring cards to billing agreement of magento

You need to enable Recurring Contract Notifications on your account contact<EMAIL_ADDRESS>for this


bash on windows ERROR in Missing binding

npm install & npm rebuild node-sass   Did not solve the problem
ERROR in Missing binding /mnt/d/Gits/pepper/node_modules/node-sass/vendor/linux-x64-48/binding.node
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 6.x
Found bindings for the following environments:

Windows 64-bit with Node.js 4.x

This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass to build the binding for your current environment.
@ ./src/pages/cinema/bonus.scss 4:14-365 13:2-17:4 14:20-371

Looks like you ran npm install on Windows 64-bit with Node.js 4, but you're trying run node-sass on Linux 64-bit with Node.js 6. This can happen when doing mounting files into a docker container or vm for instance.
You need to fetch the correct binary for your environment with npm rebuild node-sass.

The rebuild needs to be run inside the Linux environment.

Looks like we got a right OS during the download time, but we get it wrong when it comes to running it, maybe bash is a bit too much unixlike here for us?


Replace calls to xorm UseBool with Where

Filter with Where instead of by struct values with UseBool.
Since new boolean fields can be added to a struct at any time in the future, filtering by struct with UseBool() is dangerous, as it considers as part of the filter all bools in the struct.
Coders shouldnt have to think about the impact new fields have on existing database queries.

LGTM

LGTM


got errors, when using long_callback

app = DashProxy(external_stylesheets=external_stylesheets,meta_tags=[{
                        "name": "viewport",
                        "content": "width=device-width, initial-scale=1, maximum-scale=1"
                    }])
@app.long_callback(
    output=Output('raw_data_cleaning_state', 'children'),
    inputs=[Input('clean_raw_data_button', 'n_clicks'),
            State('username', 'data'),
            State('file_list_completedata', 'value')
            ],

    running=[(Output('clean_raw_data_button', 'disabled'), True, False),
             (Output('clean_raw_data_button', 'children'), 'wait for processing', 'Clean the selected data')],
    prevent_initial_call=True,
    manager=long_callback_manager
)

When use the dash.Dash, it works fine
app = dash.Dash(__name__,
                #suppress_callback_exceptions=True,
                external_stylesheets=external_stylesheets,
                #long_callback_manager=long_callback_manager,
                # prevent_initial_callbacks=True,
                # routes_pathname_prefix='/dash/',
                # It's what make the app be responsive;

                meta_tags=[{
                        "name": "viewport",
                        "content": "width=device-width, initial-scale=1, maximum-scale=1"
                    }])

The transform system was implemented prior to Dash 2.0, so it doesn't apply to Dash 2.0 callbacks (i.e. long callbacks and callbacks "directly on the dash module"). I have updated the documentation accordingly.

Thanks for your work on this project, @emilhe! Are you planning on adding support for long_callback? Is there something that makes it hard to support it?

I don't see any immediate blockers, but as the structure is different from other callbacks, it will probably require a bit of work.
The main reasons I haven't prioritized (looking into) support yet is that not many people seem to use the feature, myself included.

is there still a way to call the original Dash long_callback within the same app if that particular callback doesn't require any of the DashProxy enrich transforms?

No, you'll have to use the new syntax.


Fixes Router.GoUp/GoBack crash

fixes https://github.com/fusetools/fuselibs-public/issues/1066
This PR contains:

[x] Changelog
[ ] ~Documentation~
[x] Tests

Travis status is actually green, even though github doesn't seem to be aware. Merging anyways.


Frontend: unpredictable gas limit error

System information
Discord User:
For some reason, I had multiple "UNPREDICTABLE_GAS_LIMIT" errors when I tried to use MetaMask extension (tried to bridge from Arb to OP and vise-versa); for testing purposes, I checked & transfered with MetaMask bridge and it was successfully; then I switched to Zerion Wallet and finally I was able to bridge with Beamer. maybe the issue is related to low asset allowance, and if so, maybe it worth to add some friendly explanation to user in UI in general, keep going, team, the product looks well!

I had a look at this again. The issue is that the user approved less tokens than needed. Meaning that they did not use the Use default button for approval inside MetaMask. When creating the request transaction, we should again check if the right amount is approved. This would at least allow for showing an understandable error message or let us trigger another approval.
In the best case, we make MetaMask to prefill the field with our default amount, but I couldn't find an option for this yet.


Add property to DragTarget to change appearance when a Draggable is dragged but not necessarily near the DragTarget

Use case

Right now, the DragTarget class has the relevant properties:

onMove: Called when a Draggable moves within this DragTarget.

onWillAccept: Called to determine whether this widget is interested in receiving a given piece of data being dragged over this drag target.

However, these two only get initiated when a Draggable moves "within" or "over" the drag target. This is okay, but it is somewhat mobile focused, where there is not much room for a lot of drag targets. On desktop and in certain applications, one might imagine there being several DragTargets for a given Draggable.
For example, consider a board game where a player picks up, i.e. drags, a pawn represented by a Draggable. In such a case, the application might want to highlight the various options on the board, represented by DragTargets, where the pawn can be placed, before the pawn is moved within or over the acceptable places.
Right now, this has to be handled implicitly outside of the Draggable and DragTarget classes, as far as I can tell.
An image to hopefully communicate a potential use case:

The user initiates a drag on the red checker that gets highlighted with green, and then the various acceptable drop locations get highlighted in blue, before the checker is placed over the acceptable squares.
Proposal

The proposal is to either modify the existing properties to be more generic, passing through both the draggable type and a flag whether the draggable is within or over the drag target or coordinates, or add a new property (the more backwards compatible way) to configure the behavior for any draggable being dragged anywhere within the window or application (in the case of a multi-window application).
It isn't entirely clear to me what the name should be because the names are actually already relevant. I think onWillAccept is the perfect name, but unfortunately the current implementation only triggers when the data is dragged over the drag target. Maybe onWillAcceptDraggable or onWillAcceptGlobal or onWillAcceptAny?
(Apologies for perhaps imprecise language. I am new to Flutter and Dart, so I probably am abusing some nomenclature surrounding properties.)

@bmitc Thanks for the report.
Can you check this issue and see if it resembles your case ?

Hi @darshankawar. Thank you for the response, but unfortunately, no it doesn't. That issue is specifically discussing when onMove and onLeave get triggered. Right now, the cursor position entering and leaving the DragTarget's widget boundary is what triggers the behavior. That issue is asking for the option of using the Draggable's widget boundary. I have added a video and example code to that issue to demonstrate. (Note that onMove is poorly named. It should probably be named onEnter.)
The issue I filed here is much more generic. There should be an easy way for DragTarget's to be notified of any drag happening (maybe with some settable filters) such that they may change their appearance accordingly. This is shown in the image, and note that I do mention several times that there should be an event even when the DragTarget and Draggable are not near each other.
An example video of the behavior to complete my original image description:
https://user-images.githubusercontent.com/65685447/215430044-2b63685d-4366-4661-a0db-ff22c416f0a8.mp4
This can be accomplished right now by using, in this case, onDragStarted and onDraggableCanceled inside the Draggable, but it is done implicitly and ad-hoc. The appearance change of the DragTarget should be handled by the DragTarget and not the by the Draggable.
There are three main scenarios that a DragTarget should be notified of and be able to handle:

A drag started anywhere in the application
A Draggable's widget boundary has intersected the DragTarget's widget boundary
The cursor dragging a Draggable has intersected the DragTarget's widget boundary

(3) is the only one explicitly supported right now. (2) is requested by the issue you linked. (1) is what I am requesting in this issue.
And please note that by "anywhere in the application" I mean even in another window. Flutter has been adding multi-window support, and thus, DragTarget's in one window should be able to be notified (via some new property as proposed here) that a Draggable has started to be dragged, even if that starts in another window within the same application.

Thanks for the detailed update.


Partial Load Bitmap Entry List

Currently, BitmapIndex loads the all bitmap entries into a whole fiber.
Baidu @songzhan01 proposed to have a partial loading for this entry fiber.
The design is: 1 entry -> 1 fiber
@songzhan01  will test the bitmap index size in their production environment to decide if this is needed.

Use a parquet file to test.
file size:<PHONE_NUMBER> bytes
record number: 425400
unique key (cmatch): 77
The result:
the size of index file using Baidu internal version: 4099602 bytes
the size of index file using  oap master: 429801 bytes

thanks @songzhan01
BTW, btree index is 2M on the same column


Refactor registry plugin and simplify its usage

Purpose of the pull request
This pull request refactors the registry plugin mechanism and simplifies its usage and registry plugin development.
Brief change log

Split the registry plugin from DolphinScheduler's plugin system and use Java SPI directly.
Minimize the interface of registry so contributors can easily develop a new registry plugin.

@CalvinKirs can you please take a look?

Codecov Report

Merging #6712 (2590829) into dev (1144360) will increase coverage by 0.20%.
The diff coverage is 13.91%.

@@             Coverage Diff              @@
##                dev    #6712      +/-   ##
============================================
+ Coverage     37.69%   37.90%   +0.20%
+ Complexity     3236     3233       -3
============================================
  Files           650      642       -8
  Lines         26546    26379     -167
  Branches       2876     2859      -17
============================================
- Hits          10006     9998       -8
+ Misses        15621    15463     -158
+ Partials        919      918       -1

Impacted Files
Coverage Δ

...scheduler/api/service/impl/MonitorServiceImpl.java
13.95% <0.00%> (-0.34%)
:arrow_down:

.../org/apache/dolphinscheduler/common/Constants.java
79.16% <ø> (ø)

...apache/dolphinscheduler/common/enums/NodeType.java
0.00% <0.00%> (ø)

...gin/registry/zookeeper/ZookeeperConfiguration.java
100.00% <ø> (ø)

...ry/zookeeper/ZookeeperConnectionStateListener.java
0.00% <0.00%> (ø)

...n/registry/zookeeper/ZookeeperRegistryFactory.java
0.00% <0.00%> (ø)

...er/master/registry/MasterRegistryDataListener.java
0.00% <0.00%> (ø)

...uler/server/master/registry/ServerNodeManager.java
1.29% <0.00%> (-0.04%)
:arrow_down:

...nscheduler/server/monitor/RegistryMonitorImpl.java
0.00% <0.00%> (ø)

...olphinscheduler/server/registry/HeartBeatTask.java
27.58% <0.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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


light sensor returns empty value

Hi, I have created new react native app and installed this package, I am using the example code from the readme file.
When I run the code light sensor returns empty value. I am currently testing on the physical device.
Do I need to configure anything else?

@chiragparekh this module works only for android platform, iOS code is missing, maybe that's your issue.

@Mladen1kus I was testing with android device I wasn't able to make it work.

@chiragparekh Try changing the LIGHT_SENSOR event name to LightSensor, it won't work without that change(example code is wrong)

@Mladen1kus thanks for pointing out. Yes the event name should be LightSensor. I will make the change in readme.
@chiragparekh check if you are receiving the value after making the above change. After that we can close this.

@Cshayan do you happen to know if this is possible to do on iOS side?

@Mladen1kus I am not so much into iOS ecosystem. But I believe it can be done using Sensorkit framework.
https://developer.apple.com/documentation/sensorkit
Feel free to raise a PR for iOS functonality if you want to contribute.


Create www.bbwpornv.com

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Proposed Changes

...
...
...

Relevant issues
Closes #...
Closes #...
Closes #...
Related #...

Кпошлои нол

Hi, this seems a personal project. Hence closing this.


add travis CI

Use travis CI to check the links in README, and show the build status.
May need to open CI in travis

Awesome 😄 👍


fix: Updated dependencies

Description
Updated package without unnecesary dependencies
Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[x] 🗑 Chore

okay ;)


Fix StatusBar extension API

Make sure that items are still on right side if no items are
registered on left side

Make more injectable

Switch the naming to StatusBar to be more consistent within the code base

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>

Fixed styling issues, @jim-docker ptal once more.

Fixed styling issues, @jim-docker ptal once more.

Were you trying to fix the minor issue I mentioned? It's still there but I don't think it is a big deal. Looks good otherwise


added the editions funciton

What is this
An amalgamation of a few minor cards. The goal here is to standardise the patterns for the api ready to hit the ground running nest week. From here the rest of the (stub store powered) iteration of the api should be repeating said patterns.
This pr consist of and closes:

https://app.zenhub.com/workspaces/cogs-dd-cms-61e83b63053eb70011d37b4f/issues/gh/gss-cogs/idpd-api-poc/36, swtich to dependency injeciton (simplifies development)
https://app.zenhub.com/workspaces/cogs-dd-cms-61e83b63053eb70011d37b4f/issues/gh/gss-cogs/idpd-api-poc/34 /editions/{id} endpoint.
https://app.zenhub.com/workspaces/cogs-dd-cms-61e83b63053eb70011d37b4f/issues/gh/gss-cogs/idpd-api-poc/20 /editions endpoint.

Have also gone through and swtiched to everything to use fastapi.Depends and updated the tests. Also filled out the type hints and abstract methods.
It should all follow one nice neat centralised pattern from now.
How to review
Sanity check please. Also make test after you pipenv sync --dev should pass and coverage should be 100%.

need to reopen for github bug


[FEATURE] Enable linux/arm64 and linux/arm/7 architectures

Use case
As a raspberry-pi owner, I want to set up iCloud Drive on raspberry-pi so that I can keep the cost of HW lower.
Describe the solution you'd like

iCloud-drive-docker runs on ARM64 architectures.

Describe alternatives you've considered
None available
Additional context
ARM64 based systems are now increasingly popular due to lower TCO and power consumption.

Available on main branch.


Fix proxy when it path contains query string

We using Respond together with Symfony2 and generated url looks like ``//assets.site.com/js/respond/respond-proxy.html?_assets_version=123`. So library doesn't work properly without this patch.

ping @scottjehl @jefflembeck


Feature/migration new context api

change legacy context api to new context api
ralated plotly#776
Because my first PR of oss, it may not follow the rules, so please comment me if I made a mistake

I think it is v 16.3.0

I confirmed the result of percy, but I can cure it because I have not been able to migrate perfectly yet


Modal style fixes

Settings

Added placeholder values to inputs
Added helper copy under labels
Added Save button to top right
Added missing shadow to inputs and buttons
Added Highlight Color and Highlight Text Color inputs
Reduced width on some of the inputs (they were abnormally long)
Made the about textarea wider (removed the double label)
Reordered sections in Settings > Page
Added a contentBox around the cover photo and avatar settings
Added helper links
I attempted to switch the About textarea to the WYSIWYG editor (not working, but I think I'm close)

Create / Edit Listing

Added placeholder values to inputs
Added helper copy under labels
Added Save button to top right
Added missing shadow to inputs and buttons

Misc

Made trumbowyg theme friendly (the .trumbowyg-button-pane needed to be set to $primary)
Changed the Modal shadow style a bit
Disabled scroll on textareas when they're not focused (this prevents the textareas from randomly scrolling when you're attempting to scroll the Settings / Edit listing modals)

@tenthhuman would it be possible to change the About textarea within Settings to include the WYSIWYG editor?

@jjeffryes I'm attempting to center the header text (Page in the screenshot below) while keeping the Save button fixed to the right. Are there some classes you have in place that I can reuse to achieve this?

@morebrownies to center the header exactly, I would leave it like it is now in master, and put a .cornerTR class on the save button. That would let the save button overlap the title container, which is currently centered with flexHCent on the parent (putting a txtCtr on the h2 would work too).

@jjeffryes this one is ready for review.
There are 2 things to look at if you have time:

WYSIWYG editor is not working in the About section. I attempted to set it up, but I must be missing something.
select2 inputs are 12px taller than non select2 inputs. Spent 30m looking at this and couldn't figure it out :(

@morebrownies I'll take a look at the trumbowyg editor and the select 2 inputs. Select2 is kind of a beast.

I'm working in a few smaller changes right now. Should be finished with them in 10-15m.

Ok, all set on my end.

@morebrownies for the select2 inputs, it looked like they were 40px tall vs 42px for everything else, is that what you meant? I couldn't find examples that were 12 px different.

This is what I see in Edit Listing @jjeffryes
Tags and Categories are where I see the size issue.

@jjeffryes all changes should be ready for review

This looks good to me. @rmisio when you approve your review, you can merge it.


Pull request to test the "Build docker image" circle ci step

Hi @pdedumast ,
It is indeed what I would have done... 🤔
Let you know if I get another idea!

I just tried to remove some conda channels that might be problematic, not sure if there are needed thought. Let's see


TASK: Improve ADRs and Contributing Guidelines

Summary
Make it easier for folks to contribute to the project by improving the ADR documentation and adding other open source documentation.
To Do

[x] Create CONTRIBUTING.md with guidelines for contributing
[x] Create CODE_OF_CONDUCT.md based on this template
[x] Add better description to docs/adrs/README.md
[x] Create ISSUE_TEMPLATE/adr.md for ADR issues

Definition of Done

[x] When a new project is created from this template, it includes the following Open Source related files:

[x] CONTRIBUTING.md
[x] CODE_OF_CONDUCT.md
[x] README.md
[x] LICENSE

[x] When new decisions need to be made, contributors/maintainers can create a corresponding issue with the ADR issue template
[x] Contributors can reference the docs/adr/README.md for guidance on how and why we create ADRs

A few more changes needed:

[ ] Add the following steps to the Installation section in the README.md:

[ ] Forking
[ ] Changing into the current directory

[ ] Add Vision and Roadmap section to README.md with the following components:

[ ] Vision statement
[ ] Link to project boards
[ ] Link to issues

[ ] Remove 3.6 from testing suite
[ ] Fix ADR template and 0001-architecture-decision-records.md


Added InsertionSort algorithm..!

Well done but having description would have been much better. Consider adding problem description.


Bluetooth reconnection issue

When bluetooth is turned off and back on, the app gets disconnected and is unable to reconnect again without restarting.
When this happens the console output has these kinds of log messages:
 [CoreBluetooth] XPC connection invalid

Thanks for your work on this – I just merged your work in.


feat: attempt for some storage stuff (WIP)

@linuxbandit do you still want to work on this?

depends on cd's needs

I talked about it with Diederik and there are no plans to start using this in the short term, so I'm closing this.