flutter text rendering not display

Dear all:
I was in the development process and encountered a very strange problem. When I use the release package, the flutter text rendering does not display. Many of my users seem to have encountered this problem. This is a bad day. I checked a lot of information, but I still haven't solved it. Hope to get your help.  The flutter I currently use is stable version 1.22.6 .Thank you.

please share reproducible code

@KnightOneAdmin
Can you provide flutter doctor -v and a complete minimal reproducible code sample that shows the issue ?
Can you also mention the devices on which you are seeing the issue ?  What do you mean by release package ?

@KnightOneAdmin
Can you provide flutter doctor -v and a complete minimal reproducible code sample that shows the issue ?
Can you also mention the devices on which you are seeing the issue ? What do you mean by release package ?

Thank you for your reply
Mainly for vivo mobile phone users, the release package refers to the signed release environment, not the debug environment.

@KnightOneAdmin
Can you provide flutter doctor -v and a complete minimal reproducible code sample that shows the issue ?
Can you also mention the devices on which you are seeing the issue ? What do you mean by release package ?

Thank you for your reply
Mainly for vivo mobile phone users, the release package refers to the signed release environment, not the debug environment.

please share reproducible code

Thank you for your reply
Mainly for vivo mobile phone users, the release package refers to the signed release environment, not the debug environment.

@KnightOneAdmin
Can you provide flutter doctor -v and a complete minimal reproducible code sample that shows the issue ?
Can you also mention the devices on which you are seeing the issue ? What do you mean by release package ?

[✓] Flutter (Channel stable, 1.22.6, on Mac OS X 10.15.7 19H2 darwin-x64, locale zh-Hans-CN)
• Flutter version 1.22.6 at /Users/knight/MyResources/FileInstall/Installfile/flutter
• Framework revision 9b2d32b605 (6 weeks ago), 2021-01-22 14:36:39 -0800
• Engine revision 2f0af37152
• Dart version 2.10.5
• Pub download mirror https://pub.flutter-io.cn
• Flutter download mirror https://storage.flutter-io.cn
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/knight/MyResources/FileInstall/Installfile/android-sdk-macosx
• Platform android-30, build-tools 30.0.3
• 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)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 12.4)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.1
[!] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[!] IntelliJ IDEA Ultimate Edition (version 2020.3)
• IntelliJ at /Applications/IntelliJ IDEA.app
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• For information about installing plugins, see
https://flutter.dev/intellij-setup/#installing-the-plugins
[✓] Connected device (1 available)
• vivo NEX A (mobile) • 4d4e5f99 • android-arm64 • Android 10 (API 29)
! Doctor found issues in 3 categories.

@KnightOneAdmin
As requested earlier, we would need a complete minimal reproducible code sample that we can use to verify the issue you are seeing. Without a code sample we can't help you.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Possible bug... or incorrect docs code.

related to (https://github.com/pocketbase/pocketbase/issues/3149)
I tried making test file test.pb.js.txt
after checking console I see

so i fought it might be bug... as I assume that it should printout a string... and not [object Object]
at least for httpContext

The console.log in the examples are there just to show what fields are available, but that doesn't necessary mean that those fields have a public safe string representation.
For more details about the fields and their supported methods you can either "JSON.stringify" them or check the JSVM types reference - https://pocketbase.io/jsvm/index.html.

Side-note: you can also enable code intellisense and autocompletion if you reference the types.d.ts declarations - https://pocketbase.io/docs/js-overview/#typescript-declarations-and-code-completion

Side-note2: For examples how to use httpContext you can also check https://pocketbase.io/docs/js-routing/ (c in the examples in the same as e.httpContext)

ok, thank you


96boards: Add Hikey960 board support

Add 96Boards Hikey960 board support. Hikey960 is based on Huawei Kirin 960 octa-core ARM® big.LITTLE™ processor with four ARM Cortex®-A73 and four Cortex-A53 cores with 3GB of LPDDR4 SDRAM memory, 32GB of UFS 2.0 flash storage, and the latest generation Mali™ G71 MP8 GPU.
More information can be found in 96Boards product page: https://www.96boards.org/product/hikey960/
Signed-off-by: Manivannan Sadhasivam<EMAIL_ADDRESS>

@malikabhi05 Rebased the PR!

Merged, Thanks!


[Jupyter Widget] Allow easier configuration of height and width in a pydeck visualization

For #2929

Background

Change List

Coverage increased (+2.9%) to 82.773% when pulling d4dd68d52acc3cdc74e0d16fc587ad9ad2066bed on ajd/new-configure-height-and-width into 2bed9ca532511f73a821a9ab972ba901ae672ad4 on ajd/configure-height-and-width.


Remove unnecessary .collect() from _floyd_warshall()

This commit removes an unnecessary .collect() on the node indices from
being used in _floyd_warshall(). To build the output container the
function was looping over the node indices. Previously it was building a
Vec by iterating over the contents of graph.node_indices() and then
proceeding to iterate over the vec. Instead we can remove the
intermediate Vec and directly iterate over the NodeIndices iterator
returned by graph.node_indices().
This was caught by clippy on rust nightly which will save us from having
to fix this at a future date when a new rust version is released.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
9 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 95.408%

Files with Coverage Reduction
New Missed Lines
%

src/astar.rs
9
91.74%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
5734

Relevant Lines:
6010

💛  - Coveralls


Improve shoot secret rewriting after etcd encryption config changed

What this PR does / why we need it:

The whole RewriteShootSecretsIfEncryptionConfigurationChanged task is now retried. Also, it is no longer a dependent for the DeployGardenerResourceManager task.
When an issue happens during a PATCH of one secret then the error is no longer immediately returned but collected. At the end, an error list is returned.
The label we add to the shoot secrets is now removed again (we should not modify the secret of end-users (only if it's needed temporarily to rewrite them in the etcd store)).

Special notes for your reviewer:
/cc @vlerenc @michael-engler @adracus
Release note:

The shoot secret rewriting process (after the etcd encryption config has been changed) has been improved. It is now retried, and errors are collected and returned at the end (instead of immediately returned).

Thx!


Can't resolve dynamic import when target is 'webworker' and set dynamicImportMode: "eager"

System Info
System:
OS: macOS 13.6.3
CPU: (10) arm64 Apple M1 Pro
Memory: 3.19 GB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Yarn: 1.22.21 - ~/Library/Application Support/fnm/node-versions/v18.19.0/installation/bin/yarn
npm: 10.2.3 - ~/Library/Application Support/fnm/node-versions/v18.19.0/installation/bin/npm
pnpm: 8.14.3 - ~/Library/Application Support/fnm/node-versions/v18.19.0/installation/bin/pnpm
Browsers:
Chrome: 121.0.6167.85
Safari: 16.6
npmPackages:
@rspack/cli: latest => 0.5.3
@rspack/core: latest => 0.5.3
Details
Rspack build gets Can't resolve dynamic import error when target is 'webworker' and set dynamicImportMode: "eager".
const config = {
  mode: "production",
  target: "webworker",
  module: {
    parser: {
      javascript: {
        dynamicImportMode: "eager",
      },
    },
  },
};

Error (webpack is ok):

Reproduce link
https://github.com/chenjiahan/rsbuild-repro-worker-dynamic-import
Reproduce Steps

pnpm i
pnpm build:rspack
pnpm build:webpack

newTreeshaking will fix this:
module.exports = {
  //.....
  experiments: {
    rspackFuture: {
      newTreeshaking: true
    }
  }
}


app: Master isn't loading due to sound error

Currently, master isn't loading and throwing this error. Its just a blank white screen.

Added here: https://github.com/webaverse/app/commit/412c858a7eb2a6c736689ad3b4750383aa4f6f63

Working fine now


Idea for type to convert all children of an object to be a particular type

I'm starting to use this a fair bit for example when getting data from a datastore where all the values are strings. They don't necessarily fit the nicely typed structure I have for my model, but I don't want to have to explicitly write out a new type just for the version which is all strings coming back from the data store:
export type Monotype<T, U> = {[K in keyof T] : U}

This looks like something you already do in terms of Record:
export type Monotype<T, U> = Record<keyof T, U>;

Yeah, this doesn't seem like it saves much.


Fix plugin on latest versions of Gatsby

On latest versions of Gatsby, createNode is undefined because it's being unpacked from the wrong place. This fixes it, tested it locally with my own portfolio

I'm really sorry I missed the original notification when you opened the PR! I just saw the notification that it was closed. Thank you for the fix and sorry that thanks is three years late and no longer relevant.


replace usages of algo::generate with iter::successors from std

1.34 is out, so we no longer need to copy-paste generate everywhere!
https://github.com/rust-analyzer/rust-analyzer/blob/e6e2571bdf780d304c792d4317bbaf1d6f5d7a0a/crates/ra_syntax/src/algo.rs#L50-L51

Probably closed by #1143.

indeed, thanks!

oh, btw we have a similar generate in rowan, it should be replaced as well: https://github.com/rust-analyzer/rowan


Add a due date option to each task

Use DatePickerDialog

Also gonna have to construct a view model!

TaskData model constructed in the latest commit

Will have to add separate strings for both in the TaskData model class

Done.


⚠ Bofrost.de has degraded performance

In ee38ced, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 898 ms

Resolved: Bofrost.de performance has improved in 8f37c58 after 6 minutes.


Reverseproxy for docker registry not working anymore

1. What version of Caddy are you running (caddy -version)?
0.9.5
2. What are you trying to do?
I try to use caddy as reverse proxy for a docker container gitlab/gitlab-ce:8.16.6-ce.0
with docker registry enabled which is included in gitlab.
3. What is your entire Caddyfile?
https://git.<fqdn> https://registry.<fqdn> {
  tls on
  tls <email for acme>
  log / /data/logs/services.log "[gitlab] - {proto} {method} {path} - {status} {size}"
  proxy / http://gitlab {
    websocket
    transparent
  }
}

4.
My caddy is running in a docker container with caddy -type http -port 80 -http2=false -conf /data/conf/caddyfile and published ports 80 and 443. The git part of the gitlab container is working. And with caddy 0.9.4 pushing to the registry worked too.
5. What did you expect to see?
docker push to registry should work.
6. What did you see instead (give full error messages and/or log)?
When pushing layers > ~55 MB the transmission is interrupted.
This is the caddy log_
[gitlab] - HTTP/1.1 GET /jwt/auth - 200 926
[gitlab] - HTTP/1.1 POST /v2/root/example/blobs/uploads/ - 202 0
[gitlab] - HTTP/1.1 POST /v2/root/example/blobs/uploads/ - 202 0
[gitlab] - HTTP/1.1 PATCH /v2/root/example/blobs/uploads/f673486c-5e61-4d50-a2c3-0b483d385acf - 502 16
[gitlab] - HTTP/1.1 PATCH /v2/root/example/blobs/uploads/e8630147-4be3-4199-87d1-b37f41e59f8c - 502 16

7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?
The caddyfile is located at ./caddy/caddyfile and mounted into the caddy container.
The gitlab config is located at ./config/gitlab.rb and needs modification:
external_url 'https://git.<fqdn'
registry_external_url 'https://registry.<fqdn>'
need to be set like the domains in the caddyfile.
Use this docker-compose file to start both container:
version: "2"
networks:
  backend:

services:
  caddy:
    image: firecyberice/caddy:latest
    cap_add:
      - NET_BIND_SERVICE
    ports:
      - "80:80"
      - "443:443"
    networks:
      backend:
    command: -type http -port 80 -http2=false -conf /data/caddyfile
    working_dir: /data
    environment:
      - CADDYPATH=/data
    volumes:
      - ./caddy:/data:rw

  gitlab:
    networks:
      - backend
    image: gitlab/gitlab-ce:8.16.6-ce.0
    volumes:
      - ./config:/etc/gitlab
      - ./logs:/var/log/gitlab
      - ./data:/var/opt/gitlab

This may be related to default timeouts.
https://caddyserver.com/docs/timeouts
If you set to 0 it turns timeouts off.

Thank you setting timeouts to 0 solved this. Just to understand have the timeouts been changed between version 0.9.4 and 0.9.5?

Oh timeouts is a new directive just found it.

Yes, always read release notes before upgrading to a new version, especially before 1.0. :wink:

@mholt This change has caught quite a few people out, who have raised issues here and on forums.  Obviously this is will pass as people fix their issues, but it got me wondering whether a timeout is something that should be logged.  If it was was logged and people were having issues with closed connections it would help people to diagnose their issues a little easier.
Do you think it would be useful to log when a timeout occurs?

I see logs when a timeout happens. Do you not? The standard library emits a log entry.

oops.  That's perfect then. 😳

I'm thinking about making changes, but I don't know what to do. The new defaults mitigate attacks. Other than put it in the docs, I'm not sure what to do.


[SPARK-31756][WEBUI][test-maven] Add real headless browser support for UI test

What changes were proposed in this pull request?

This PR mainly adds two things.

Real headless browser support for UI test
A test suite using headless Chrome as one instance of  those browsers.

Also, for environment where Chrome and Chrome driver is not installed, ChromeUITest tag is added to filter out the test suite.
By default, test suites with ChromeUITest is disabled.
Why are the changes needed?

In the current master, there are two problems for UI test.

Lots of tests especially JavaScript related ones are done manually.
Appearance is better to be confirmed by our eyes but logic should be tested by test cases ideally.

Compared to the real web browsers, HtmlUnit doesn't seem to support JavaScript enough.
I added a JavaScript related test before for SPARK-31534 using HtmlUnit which is simple library based headless browser for test.
The test I added works somehow but some JavaScript related error is shown in unit-tests.log.

======= EXCEPTION START ========
Exception class=[net.sourceforge.htmlunit.corejs.javascript.JavaScriptException]
com.gargoylesoftware.htmlunit.ScriptException: Error: TOOLTIP: Option "sanitizeFn" provided type "window" but expected type "(null|function)". (http://<IP_ADDRESS>:60724/static/jquery-3.4.1.min.js#2)
        at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$HtmlUnitContextAction.run(JavaScriptEngine.java:904)
        at net.sourceforge.htmlunit.corejs.javascript.Context.call(Context.java:628)
        at net.sourceforge.htmlunit.corejs.javascript.ContextFactory.call(ContextFactory.java:515)
        at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine.callFunction(JavaScriptEngine.java:835)
        at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine.callFunction(JavaScriptEngine.java:807)
        at com.gargoylesoftware.htmlunit.InteractivePage.executeJavaScriptFunctionIfPossible(InteractivePage.java:216)
        at com.gargoylesoftware.htmlunit.javascript.background.JavaScriptFunctionJob.runJavaScript(JavaScriptFunctionJob.java:52)
        at com.gargoylesoftware.htmlunit.javascript.background.JavaScriptExecutionJob.run(JavaScriptExecutionJob.java:102)
        at com.gargoylesoftware.htmlunit.javascript.background.JavaScriptJobManagerImpl.runSingleJob(JavaScriptJobManagerImpl.java:426)
        at com.gargoylesoftware.htmlunit.javascript.background.DefaultJavaScriptExecutor.run(DefaultJavaScriptExecutor.java:157)
        at java.lang.Thread.run(Thread.java:748)
Caused by: net.sourceforge.htmlunit.corejs.javascript.JavaScriptException: Error: TOOLTIP: Option "sanitizeFn" provided type "window" but expected type "(null|function)". (http://<IP_ADDRESS>:60724/static/jquery-3.4.1.min.js#2)
        at net.sourceforge.htmlunit.corejs.javascript.Interpreter.interpretLoop(Interpreter.java:1009)
        at net.sourceforge.htmlunit.corejs.javascript.Interpreter.interpret(Interpreter.java:800)
        at net.sourceforge.htmlunit.corejs.javascript.InterpretedFunction.call(InterpretedFunction.java:105)
        at net.sourceforge.htmlunit.corejs.javascript.ContextFactory.doTopCall(ContextFactory.java:413)
        at com.gargoylesoftware.htmlunit.javascript.HtmlUnitContextFactory.doTopCall(HtmlUnitContextFactory.java:252)
        at net.sourceforge.htmlunit.corejs.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3264)
        at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$4.doRun(JavaScriptEngine.java:828)
        at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$HtmlUnitContextAction.run(JavaScriptEngine.java:889)
        ... 10 more
JavaScriptException value = Error: TOOLTIP: Option "sanitizeFn" provided type "window" but expected type "(null|function)".
== CALLING JAVASCRIPT ==
  function () {
      throw e;
  }
======= EXCEPTION END ========

I tried to upgrade HtmlUnit to 2.40.0 but what is worse, the test become not working even though it works on real browsers like Chrome, Safari and Firefox without error.
[info] UISeleniumSuite:
[info] - SPARK-31534: text for tooltip should be escaped *** FAILED *** (17 seconds, 745 milliseconds)
[info]   The code passed to eventually never returned normally. Attempted 2 times over 12.910785232 seconds. Last failure message: com.gargoylesoftware.htmlunit.ScriptException: ReferenceError: Assignment to undefined "regeneratorRuntime" in strict mode (http://<IP_ADDRESS>:62132/static/vis-timeline-graph2d.min.js#52(Function)#1)

To resolve those problems, it's better to support headless browser for UI test.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

I tested with following patterns. Both Chrome and Chrome driver should be installed to test.

sbt / with default excluded tags (expect to be skipped)
build/sbt -Dspark.test.webdriver.chrome.driver=/path/to/chromedriver "testOnly org.apache.spark.ui.ChromeUISeleniumSuite"

sbt / overwrite excluded tags as org.apache.spark.tags.ChromeUITest (expect to be skipped)
build/sbt -Dtest.exclude.tags="org.apache.spark.tags.ChromeUITest" -Dspark.test.webdriver.chrome.driver=/path/to/chromedriver "testOnly org.apache.spark.ui.ChromeUISeleniumSuite"

sbt / overwrite excluded tags as empty string (expect to succeed)
build/sbt -Dtest.exclude.tags= -Dspark.test.webdriver.chrome.driver=/path/to/chromedriver "testOnly org.apache.spark.ui.ChromeUISeleniumSuite"

mvn / with default excluded tags (expect to be skipped)
build/mvn -Dspark.test.webdriver.chrome.driver=/path/to/chromedriver83 -Dtest=none -DwildcardSuites=org.apache.spark.ui.ChromeUISeleniumSuite test

mvn / overwrite excluded tags as org.apache.spark.tags.ChromeUITest (expect to be skipped)
build/mvn -Dtest.exclude.tags=org.apache.spark.tags.ChromeUITest -Dspark.test.webdriver.chrome.driver=/path/to/chromedriver83 -Dtest=none -DwildcardSuites=org.apache.spark.ui.ChromeUISeleniumSuite test

mvn / overwrite excluded tags as empty string (expect to succeed)
build/mvn -Dtest.exclude.tags= -Dspark.test.webdriver.chrome.driver=/path/to/chromedriver -Dtest=none -DwildcardSuites=org.apache.spark.ui.ChromeUISeleniumSuite test

Test build #123042 has started for PR 28627 at commit 6b47fe8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27685/
Test PASSed.

Test build #123042 has finished for PR 28627 at commit 6b47fe8.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123042/
Test FAILed.

retest this please.

Test build #123052 has started for PR 28627 at commit 6b47fe8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27692/
Test PASSed.

Test build #123052 has finished for PR 28627 at commit 6b47fe8.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123052/
Test FAILed.

Jenkins retest this please

Test build #123060 has started for PR 28627 at commit 6b47fe8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27699/
Test PASSed.

Test build #123060 has finished for PR 28627 at commit 6b47fe8.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123060/
Test FAILed.

Test patterns are updated in the description.

Test build #123071 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27708/
Test PASSed.

Test build #123071 has finished for PR 28627 at commit 70d07a3.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123071/
Test FAILed.

retest this please.

Test build #123076 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27713/
Test PASSed.

Test build #123076 has finished for PR 28627 at commit 70d07a3.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123076/
Test FAILed.

retest this please.

Test build #123087 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27722/
Test PASSed.

Test build #123087 has finished for PR 28627 at commit 70d07a3.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123087/
Test FAILed.

retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27733/
Test PASSed.

Test build #123099 has started for PR 28627 at commit 70d07a3.

Test build #123099 has finished for PR 28627 at commit 70d07a3.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123099/
Test FAILed.

Can those tests finish within 400m with Maven?

retest this please.

Test build #123104 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27738/
Test PASSed.

Test build #123104 has finished for PR 28627 at commit 70d07a3.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123104/
Test FAILed.

retest this please.

Test build #123115 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27749/
Test PASSed.

Test build #123115 has finished for PR 28627 at commit 70d07a3.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123115/
Test FAILed.

retest this please.

Test build #123130 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27762/
Test PASSed.

Test build #123130 has finished for PR 28627 at commit 70d07a3.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123130/
Test FAILed.

retest this please.

Test build #123151 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27781/
Test PASSed.

@dongjoon-hyun Is it possible to finish tests within 400m with Maven?
I see #28640 also fails tests with Maven because of time out.
Can we extend the time for tests with Maven somehow?

Test build #123151 has finished for PR 28627 at commit 70d07a3.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123151/
Test FAILed.

retest this please.

Test build #123202 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27828/
Test PASSed.

Test build #123202 has finished for PR 28627 at commit 70d07a3.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123202/
Test FAILed.

@HyukjinKwon @shaneknapp
The time limit for CI seems to be too short with Maven.
Tests for this PR has failed 9 times due to the limit.
I see another PR fails with the same reason.
Can we expand the limit for Maven or do you have better idea?

retest this please

The problem is that it's getting too long to finish each PR build .. so last time it was pretty arguable when it increased the build time IIRC. Maybe it's time to profile and reduce the testing time again .. adding @cloud-fan too FYI. Shall we increase a bit more for now since it blocks Maven testing as can be seen above?

Test build #123224 has started for PR 28627 at commit 70d07a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27847/
Test PASSed.

Test build #123224 has finished for PR 28627 at commit 70d07a3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123224/
Test FAILed.

Test build #123247 has started for PR 28627 at commit 2e805ec.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27869/
Test PASSed.

Test build #123247 has finished for PR 28627 at commit 2e805ec.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123247/
Test FAILed.

Couldn't finish within 500m...

retest this please.

Test build #123265 has started for PR 28627 at commit 2e805ec.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27887/
Test PASSed.

Test build #123265 has finished for PR 28627 at commit 2e805ec.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123265/
Test FAILed.

retest this please.

Test build #123268 has started for PR 28627 at commit 2e805ec.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27890/
Test PASSed.

Test build #123268 has finished for PR 28627 at commit 2e805ec.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123268/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27904/
Test PASSed.

Test build #123282 has started for PR 28627 at commit 2e805ec.

It seems that we are hitting time-out still in some cases.
BTW, @sarutak . Is the following a successful run?

https://github.com/apache/spark/pull/28627#issuecomment-635776114

BTW, @sarutak . Is the following a successful run?

Actually, It's not.
According to the console log, it's almost finished but aborted...
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/123247/console

Oh. Got it, @sarutak .

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123282/
Test PASSed.

Thanks all for the review and expanding the timeout!

sorry, i don't watch github for @mentions...  if this is still a problem,
file a build/infra jira and assign it to me.  :)
On Thu, May 28, 2020 at 11:00 PM Kousuke Saruta<EMAIL_ADDRESS>wrote:

Couldn't finish within 500m...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/28627#issuecomment-635777121, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMIHLDX32JFW75S7HT5DQ3RT5FPBANCNFSM4NIXL3ZA
.


mp4 could not be loaded with cv

D:\comfyui\ComfyUI\output\deepfuze\faceswap_1723104173818295.mp4 could not be loaded with cv.
File "D:\comfyui\ComfyUI\execution.py", line 152, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\comfyui\ComfyUI\execution.py", line 82, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\comfyui\ComfyUI\execution.py", line 75, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\comfyui\ComfyUI\custom_nodes\ComfyUI-DeepFuze\nodes.py", line 928, in faceswampgenerate
return load_video_cv(faceswap_filename,0,'Disabled',512,512,0,0,1)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\comfyui\ComfyUI\custom_nodes\ComfyUI-DeepFuze\nodes.py", line 446, in load_video_cv
(width, height, fps, duration, total_frames, target_frame_time) = next(gen)
^^^^^^^^^
File "D:\comfyui\ComfyUI\custom_nodes\ComfyUI-DeepFuze\nodes.py", line 365, in cv_frame_generator
raise ValueError(f"{video} could not be loaded with cv.")

Same here.
It looks like this error occurs because the video is not saved to the correct folder or is saved with a different name.
The solution with reinstalling onnxruntime does not work. onnxruntime is definitely installed correctly.

In my case, i have reinstalling onnxruntime-gpu to spesific version, not new version. try install onnxruntime-gpu version 1.18.0, in my case this version work fine. maybe this node not supported new version of onnxruntime-gpu

thanks, but am not tech-savvy enough to try that. I might (probably) end with nothing working anymore.
I hope we get an update soon...

I installed onnxruntime-gpu==1.18.0 but the error is still here

Seems like the mp4 is not being createdd or saved correctly, @SamKhoze any ideas what needs to be altered i the script of
ComfyUI-DeepFuze\nodes.py

It didn't help me(

I reinstalled onnxruntime-gpu - It kinda works BUT it runs as fast as CPU.  I now get this error, but it still words.
Analysing: 100%|=============================| 241/241 [00:02<00:00, 82.39frame/s, rate=0]
[DEEPFUZE.CORE] Extracting frames with a resolution of 1080x1080 and 25.0 frames per second
[DEEPFUZE.PROCESSORS.FRAME.MODULES.LIP_SYNCER] Processing
2024-09-25 20:30:39.2715166 [E:onnxruntime:Default, provider_bridge_ort.cc:1992 onnxruntime::TryGetProviderInfo_CUDA] D:\a\_work\1\s\onnxruntime\core\session\provider_bridge_ort.cc:1637 onnxruntime::ProviderLibrary::Get [ONNXRuntimeError] : 1 : FAIL : LoadLibrary failed with error 126 "" when trying to load "D:\apps\Python\Python310\lib\site-packages\onnxruntime\capi\onnxruntime_providers_cuda.dll"

...maybe this doesn't work with onnxruntime-gpu 1.19?

and today - with no changes - it doesn't work again and I'm back to :
!!! Exception during processing !!! D:\apps\SD-WebUI\ComfyUI\output\deepfuze\enhanced_17273456893845851.mp4 could not be loaded with cv

This is crazy, I've never had a node so randomly unstable.
I have tried:
onnx 1.16 <-> 1.16.2
onnxruntime-gpu 1.18 <-> 1.19.2
opencv-python <IP_ADDRESS> <-> <IP_ADDRESS>
(<-> means "and everything in-between")
I've even uninstalled everything in the requirements file and re-installed from the requirements file.
It seems to decide to work when it wants to.
What do you need from us to get this node stable and working?


Strange png rendering behavior

Hi! First of all, thank you for creating this useful drawing tool!
I have stubbed upon one very strange issue. I am trying to draw a contour map by using polylines. The issue appears when I am trying to draw non-filled contours with non-zero stroke width. When I use "polyline.ToPath()" the code works well. When I attempt to smoothen the line by using "polyline.Smoothen()" I see unexpected filled rectangles in the resulting PNG file. And the rectangles have purely random sizes and positions at each next run. At the same time SVG files are correct in both the cases.
Here I attach two PNGs and zipped code. To reproduce the issue you may go to the line 259 in the file "main.go". The code is relatively simple and may be straightforwardly unzipped and built.

Best regards,
Dmitry

Hello again! I had a similar idea about the problems with colormaps, but it seems that the problem is different. May you try to start the code with smoothing several times in a row. Sometimes, when I change something in the code and recompile it I get correct PNGs. However, next starts results in those PNGs with glitches. At the same time, when I start the code without smoothing (i.e. with "polyline.ToPath()") all subsequent PNGs are correct.
We are now trying to launch the code under a different OS to check if there is some OS-dependency. I normally use MacOS 10.15.5. I will let you know about the results. I hope you've downloaded the code, since my colleague offers to remove the archive from the initial post.

I've downloaded your package. I just ran it again and the black rectangles appeared for me as well. This is very peculiar, as that means that rendering is not deterministic. It is possible that this is some numerical error, but it is strange nonetheless. I will investigate the problem and report back to you.

Thank you! We've just tested the code under Linux and got absolutely the same behavior, correct PNGs with no smoothing and glitched PNGs with smoothed contours.

I'm working on it, but I'm pretty busy the coming week so can't promise anything. In the mean time, some paths generated by the contours cause problems for the renderer, it is unclear what causes them. I've singled one out for further analysis.

I think there is no rush. I would be great to find the bug even if it takes some time.

The problem seems to appear in this seemingly innocent looking path:
package main

import (
	"fmt"

	"github.com/tdewolff/canvas"
	"github.com/tdewolff/canvas/renderers/rasterizer"
)

var path = `M985.9649808268126 1161.232756459878C986.2869285054657 1169.0146015445034<PHONE_NUMBER>725696 1177.257811327677 989 1183C990.8157448727096 1190.5799522811838<PHONE_NUMBER>624343 1193.8018226924364 995 1200C997.3023614375657 1206.1981773075636 1000.0251906229716 1215.372661511437 1003 1222`

func main() {
	w := 2000
	h := 2000

	p, err := canvas.ParseSVG(path)
	if err != nil {
		panic(err)
	}

	c := canvas.New(float64(w), float64(h))
	ctx := canvas.NewContext(c)
	ctx.DrawPath(0, 0, p.Stroke(5.0, canvas.ButtCap, canvas.BevelJoin))
	c.Fit(10.0)
	c.WriteFile(fmt.Sprintf("out.png"), rasterizer.PNGWriter(1.0))
}

which is the same as drawing the following path:
M988.4628440538675 1161.1294157664051L988.610054058531 1163.7754403202387L988.8428179248218 1166.5885882674277L989.1629593974355 1169.536693089536L989.5685310648431 1172.5704913532093L990.0521022467683 1175.6192489516043L990.5987964886564 1178.5878553687285L991.1846827052713 1181.3587105716074L991.4312186816342 1182.4176120519164L992.0195726132725 1184.7155993684296L992.6242177002957 1186.7869907330999L993.2683460703637 1188.7392926900234L993.9967490336006 1190.7224557084155L994.371112411036 1191.6802649643378L996.3664803999383 1196.5943384892403L997.3435408053143 1199.1294734387586L998.3815444308493 1202.0250491425195L998.5094049668467 1202.3927116629825L1001.3438081219083 1210.6981368136203L1003.0876242708475 1215.5683936908567L1004.2784836473611 1218.6269358026539L1005.2806742959069 1220.9760249953038L1005.2807677421221 1220.9762331776742L1000.7192322579441 1223.0237668224734M1000.7192322578779 1223.0237668223258L1000.7191309811094 1223.023541194806L999.6481897498684 1220.5138323082529L998.4044630092462 1217.3199645851787L996.6187894548352 1212.3334345222383L993.7855926222417 1204.031490761262L993.660264991707 1203.6711112487392L992.6564591946857 1200.8705265612414L991.7211186426406 1198.4438287281537L989.7238398434346 1193.5249485909844L989.3293081752578 1192.5154966543705L988.5476409747881 1190.3870012202578L987.8496807830154 1188.2715099231166L987.1970414367564 1186.035899732563L986.5687813183658 1183.5823879480836L986.3080755830066 1182.4626593815965L985.6935926177597 1179.5568625848732L985.1238510642015 1176.463251488051L984.6210596963064 1173.2933516837777L984.1992588041444 1170.138088483732L983.8655746882158 1167.0650856584587L983.6220162163052 1164.1210969193714L983.4671175997578 1161.3360971533507L988.4628440538675 1161.1294157664051z

Changing any of the stroke width or changing the path numbers seem to fix the problem, suggesting it is probably a fairly exotic / unstable type of error. My suspicion is that this is a problem in the (external) rasterizer, possible due to precision errors.

Well as always, most time is spent on the smallest bugs. There was a numerical precision error in joining paths while stroking. This seems to fix it, please let me know how it goes!


Target Android 15 (SDK 35)

Task/Issue URL: https://app.asana.com/0/1207908166761516/1206705314358009/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5204  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @mikescamell and the rest of your teammates on  Graphite


Improving / Updating how some hooks work

Background
When we started using pre-commit-dbt (the original project) we found that some hooks did not exhibit what we believe is the "correct" behavior. We made updates to the way some hooks worked and merged those changes. Now that we have moved to dbt-checkpoint and officially updated the version, some people are running into issues due to the new behavior.
What were we trying to solve for?
We noticed that a hook we were using check_model_has_all_columns was not always catching issues. The root cause was that it only checked that a property (yml) file contained all the columns in a model (sql) file if the model was changed. However, if the property file was the only file changed then it was not compared to the model file. This would allow someone to delete or add a column to the property file even though it did not match the model file. We felt this check should assure that these two files are always in sync and as such it should check if either file is changed.
How was this issue addressed?
We "fill in" the missing files so that if the yml file is changed we find the corresponding sql file so we can make sure we do the proper check.
Side effects
@followingell reported an issue with check-model-has-tests where excluded files were being included in the check. @karabulute found what we had implemented and submitted a PR that removed the functionality we added.
Our Opinion
We don't believe we should remove get_missing_file_paths from all the hooks because without this we are indirectly not complying with the spirit of the hook.
Proposal
We propose we add a parameter to the hooks that have this behavior so that files can be excluded, but we cannot use the pre-commit exclude parameter because we don't have that information in dbt-checkpoint.
Instead of doing this
- id: check-model-has-tests
  description: "Ensures that the model has a number of tests"
  args: ["--test-cnt", "1", "--"]
  exclude: |
    (?x)(
      models/demo
    )

We propose this
- id: check-model-has-tests
  description: "Ensures that the model has a number of tests"
  args: ["--test-cnt", "1", "--exclude","models/demo", "--"]

Which hooks are Impacted
Hooks that implement yml/sql file discovery:

Discover SQL:

check_column_name_contract https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-column-name-contract
check_model_has_all_columns https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-has-all-columns
check_model_has_tests https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-has-tests
check_model_has_tests_by_group https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-has-tests-by-group
check_model_has_tests_by_name https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-has-tests-by-name
check_model_has_tests_by_type https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-has-tests-by-type
check_model_name_contract https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-name-contract
check_model_parents_database https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-parents-database
check_model_tags https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-tags

Discover YML:

check_model_has_description https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-model-has-description

Discover both:

check_macro_has_description https://github.com/dbt-checkpoint/dbt-checkpoint/blob/main/HOOKS.md#check-macro-has-description

@JFrackson pre-commit's exclude works in a previous stage before reaching dbt-checkpoint hooks. What we receive in dbt-checkpoint are the results of pre-commit configurations, and we have no access to what the user specified in exclude, be it at repo or hook level.

Thanks for clarifying @BAntonellini . So without a more significant change it wouldn't be possible. That seems fine to me then to merge this as is! Let's merge this and then push a v1.2 so that there's a new stable release with this patch and the others recently.
Also, just in case users would find it useful: we can create an issue for making exclusions easier so that users can leave comments or reactions on what they would like to see (i.e. to keep conversation in one place). Would you mind creating that issue after you merge?


Price

That makes sense. My current mockup for the shop now also has a color different from $color-brand.

Alright, I updated the design, added colors and more tests. Also deployed to github pages.

Looks good to me - feel free to merge as you please :)


[PS-27296] Updated docs with TLS configuration info, updated logging implementat…

…ion, updated server_sdk.jar

Switched SLF4j backend from simple-logger to logback to make for cleaner log output

2020-09-18 | 13:54:34.633 | main     |  INFO | com.skillz.server.Server  | Starting Skillz Server 1.0...
2020-09-18 | 13:54:34.967 | main     |  INFO | com.skillz.server.World   | Loading ExampleSkillzGame 1.0...
2020-09-18 | 13:54:34.986 | main     |  INFO | com.skillz.server.World   | Using custom TickRate of 150ms
2020-09-18 | 13:54:35.601 | main     |  INFO | c.s.server.ContentLoader  | Loaded 1 MessageHandlers
2020-09-18 | 13:54:35.823 | main     |  INFO | com.skillz.server.Server  | Server started successfully on port 10140!
2020-09-18 | 13:54:40.292 | roup-2-2 |  INFO | com.skillz.server.World   | Socket connected from: /<IP_ADDRESS>:58893

Added TLS configuration instructions to the documentation
Added backticks around variables, functions, and paths to make for easier reading

🧹


bigint: Break out into multiple files

If the tests can be compiled outside altogether, then make the tests/ directory a sibling of src/.  Cargo will pick up each one automatically.  This isn't always possible though, if a test uses private items.

They do use private items
On Jul 15, 2016 5:33 PM, "Josh Stone"<EMAIL_ADDRESS>wrote:

If the tests can be compiled outside altogether, then make the tests/
directory a sibling of src/. Cargo will pick up each one automatically.
This isn't always possible though, if a test uses private items.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-num/num/pull/207#issuecomment-233101277, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB5r7hNrZ8ZQUMIVMW_t6fPSWQZcfjoaks5qWDTcgaJpZM4JNNnq
.

The best would be splitting it into 2 kinds of tests:

unit tests that checks simple methods
integration tests that checks interface as a whole

Wiadomość napisana przez koverstreet<EMAIL_ADDRESS>w dniu 16.07.2016, o godz. 03:53:
They do use private items
On Jul 15, 2016 5:33 PM, "Josh Stone"<EMAIL_ADDRESS>wrote:

If the tests can be compiled outside altogether, then make the tests/
directory a sibling of src/. Cargo will pick up each one automatically.
This isn't always possible though, if a test uses private items.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-num/num/pull/207#issuecomment-233101277, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB5r7hNrZ8ZQUMIVMW_t6fPSWQZcfjoaks5qWDTcgaJpZM4JNNnq
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/rust-num/num/pull/207#issuecomment-233102221, or mute the thread https://github.com/notifications/unsubscribe-auth/AARzN11LAddQVBQWbBDr8ezFq4kVjkZZks5qWDmrgaJpZM4JNNnq.

Perhaps, but let's leave that sort of thing off for future patches. I want
to keep this patch at just simple rearranging of code.
On Jul 15, 2016 11:57 PM, "Łukasz Jan Niemier"<EMAIL_ADDRESS>wrote:

The best would be splitting it into 2 kinds of tests:

unit tests that checks simple methods
integration tests that checks interface as a whole

Wiadomość napisana przez koverstreet<EMAIL_ADDRESS>w dniu
16.07.2016, o godz. 03:53:
They do use private items
On Jul 15, 2016 5:33 PM, "Josh Stone"<EMAIL_ADDRESS>wrote:

If the tests can be compiled outside altogether, then make the tests/
directory a sibling of src/. Cargo will pick up each one automatically.
This isn't always possible though, if a test uses private items.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-num/num/pull/207#issuecomment-233101277, or
mute
the thread
<
https://github.com/notifications/unsubscribe-auth/AB5r7hNrZ8ZQUMIVMW_t6fPSWQZcfjoaks5qWDTcgaJpZM4JNNnq

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <
https://github.com/rust-num/num/pull/207#issuecomment-233102221>, or mute
the thread <
https://github.com/notifications/unsubscribe-auth/AARzN11LAddQVBQWbBDr8ezFq4kVjkZZks5qWDmrgaJpZM4JNNnq
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-num/num/pull/207#issuecomment-233118605, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB5r7jUB-pCZTlmJN88831EK4KI3TP7Wks5qWI7ZgaJpZM4JNNnq
.

@homu r+ 2795223

:zap: Test exempted - status


fix: actions using node12 which is deprecated

closes #424.

thank you!


[FEATURE] added function to OrderMananger to get orders by user and status id, …

…fixed bug in Repository

ack


night-mode: Fix invite_user_form overlap bug.

Adding the element for the invite link would cause the modal footer to
shift upwards, in nightmode this caused the stream list to appear
beneath the footer as the footer background was transparent. This commit
replaces that styling with a solid equivalent color.

Follow up to https://github.com/zulip/zulip/pull/11471.
GIFs or Screenshots:

side note: (the hsl replacement gives #1a232e instead of #1a242f)

@timabbott This was a small bug fix that you might have missed. This is slightly hacky because it makes the modal completely opaque.

Nice, merged, thanks @YashRE42!  I had indeed lost track of this.

I realized I may have misread this; do you think we should try to figure out a less hacky solution?

I don't think it matters because it works fine and the transparent property didn't serve any use there.

in fact it avoids bugs like this:

that said if we want to change we could change it so the scroll is only on the stream list and not the whole modal. And adjust to account for the bump when the link is generated.... but it would probably take a lot of time for a low priority thing.

OK let's declare victory here :)


Meshing queries refactoring, improved error handling and doc updates

---------------------------------------------------------------

---------------------------------------------------------------

---------------------------------------------------------------

@hpohekar this is an observation rather than a criticism. The summary of each of these "service" objects focuses on the implementation: "wrapper over ... gRPC" rather than telling the reader what the "service" can offer them. This is bewildering for te average reader.

@hpohekar this is an observation rather than a criticism. The summary of each of these "service" objects focuses on the implementation: "wrapper over ... gRPC" rather than telling the reader what the "service" can offer them. This is bewildering for te average reader. #1586

Right.

@seanpearsonuk regarding following mesh utility function,

We have useful supporting  function to guide user about allowed arguments to above function.

---------------------------------------

@seanpearsonuk regarding following mesh utility function,

We have useful supporting function to guide user about allowed arguments to above function.

---------------------------------------

I believe that we should use enums for such things.

@seanpearsonuk
This PR is now ready and consistent with what we are offering in 23R2.
It contains all required meshing queries utility functions, tests and documentation.
We will implement new changes in next PR as per our  latest discussion.
Thanks.


Update cats-effect to 2.0.0

Updates org.typelevel:cats-effect from 2.0.0-M1 to 2.0.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, semver-pre-release

Codecov Report

Merging #61 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #61   +/-   ##
=======================================
  Coverage   42.30%   42.30%
=======================================
  Files          11       11
  Lines         208      208
  Branches        4        4
=======================================
  Hits           88       88
  Misses        120      120

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 e408e7f...d368626. Read the comment docs.


Is this like the Essential Mod?

If you are refering to this, no. This is a completely different mod.


Update test-helper doc for the easiest installation instruction

Hi - the easiest way of installation now is using this command from the Command Palette in VSCode:

I believe it can greatly help new contributors.

Nice, thanks!


"org.freedesktop.secrets was not provided by any .service files" when doing GistFS: New Gist for the first time

After successfully installed GistFS from the market place, when the "GistFS: New Gist" command was run for the first time, VSCode prompted me with the following error message:
org.freedesktop.secrets was not provided by any .service files
After some googling, install the following package on my system solved it:
gnome-keyring
Perhaps it would help to include some pointer in the Getting Started section of the document / webpage that gnome-keyring is a dependency?

Ah yeah this is good feedback. I’m using “keytar” to securely read and write the GH token, and I suppose that requires Gnome key ring to be installed on Linux. Thanks for reporting this!

@lichiku I just updated the readme to call out the need for gnome-keyring and libsecret.

@lostintangent  Thank you for the ultra-fast response. The readme looks great and helpful now. I really like the idea and hope to see this great extension growing and shining. Thank you for your great job!


CD: Include component tests coverage in codecov code coverage report.

What this PR changes/adds
Include ComponentTests to code coverage report.
In the current state, only unit tests are included in the code coverage report. This PR also includes the Component Tests to the report.

Publish jacoco reports for each run-tests action. jacoco reports will be a published artifact. The report will be present only for unit tests and component tests because the jacocoTestReport task is only running for unit tests and component tests.
Run jacocoTestReport task for ComponentTest
Created a job to publish the code coverage report (downloading the artifacts containing the jacoco reports first).

We can see that test coverage increased after including the ComponentTests:
https://codecov.io/github/agera-edc/DataSpaceConnector/commit/93f09d5d7c8dbbd1af763ce26300af0b611f37d4
Linked Issue(s)
#230
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[ ] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

:exclamation: No coverage uploaded for pull request base (feature/1217-include-component-tests-in-report@9282a7d). Click here to learn what that means.
The diff coverage is n/a.

@@                                Coverage Diff                                @@
##             feature/1217-include-component-tests-in-report     #245   +/-   ##
=================================================================================
  Coverage                                                  ?   66.75%
=================================================================================
  Files                                                     ?      699
  Lines                                                     ?    15480
  Branches                                                  ?     1045
=================================================================================
  Hits                                                      ?    10334
  Misses                                                    ?     4663
  Partials                                                  ?      483

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 9282a7d...de54bbd. Read the comment docs.


Range slider in Chrome for Android broken

The slider does not show the value on my Nexus 5 (Android 5.0). At most, the background for the label shows for a second if you tap (doesn't have the correct shape however):

It does not show at all if you swipe.

Yes, the range slider is not exactly the best. We are still planning on either improving this one heavily or just making a new one from scratch

Duplicate of #436


Object destructuring issue: Initializer on shorthand should not throw syntax error

Following should parse
var x = 10;
({x = 10} = {});

Actual: Syntax error
Refer OS bug [3887967] (https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7564&id=3887967)

these sorts of frontend fixes are probably good first bugs, if you want to attract volunteer contributors to work on actual language features.
I'm hoping I can encourage some local youth to tackle some of these bugs.

Hey, I'm a newbie.
Can I work on this bug and also get some help on how to tackle thing bug ?

@kepta absolutely. Tracing from the parser is the easiest thing to do. Add breakpoint at Parser::Parse. Also look at the call sites of IsES6DestructuringEnabled. That code amounts to destructuring related.
See this for building instructions. Let me know if you have more questions.

@kepta also take a read through test/runtests.cmd to learn how to run tests.  Of particular note, consider providing the options -dirs es6 -variant interpreter to reduce the number of tests run to those surrounding the new language features and running them against front end, so you can have quicker code, build, test, debug loops.
So for example, after building x64 debug in VS, cd to the test directory and execute runtests.cmd -x64debug -dirs es6 -variant interpreter to run tests appropriate for this bug.
Of course once you're satisfied with your change you'll want to run all tests to make sure nothing broke by accident (run all tests by only specifying the build flavor, e.g. runtests.cmd -x64debug).

This is fixed.


Step 10 commented code mislabeled

Lines 41 and 49 of DeepLinkAppWidgetProvider.kt should say Step 10. Simple edit :)
app/src/main/java/com/example/android/codelabs/navigation/DeepLinkAppWidgetProvider.kt

Good catch, updating now and thank you!


Fix looking up 'XDG_CONFIG_HOME' envvar

README says that 'era' lookups "$XDG_CONFIG_HOME" as a configuration directory, but it used to just lookup "$HOME/.config". I guess this doesn't make sense. So 'era' first lookups "$XDG_CONFIG_HOME", and if not found the variable, 'era' assumes the value is ~/.config/era now. This behavior probably is familiar in CLI application configurations.
And this patch fixes misc trivial stuffs.
Thank you for your cool CLI application.

Thank you! Agreed.


dev: remove precommit test all

Remove cargo test --all from pre-commit hooks via Husky
Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Testing
[ ] Other (please describe):

What is the current behavior?
the pre-commit hook generated by Husky will no longer generate lines for cargo test --all
Issue Number: N/A
What is the new behavior?

Husky would generate a pre-commit hook for cargo test --all

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information
In order to stop testing all for each commit you will need to manually edit the .git/hooks/pre-commit file and remove the lines pertaining to testing.

Codecov Report
Base: 84.43% // Head: 84.43% // No change to project coverage :thumbsup:

Coverage data is based on head (de7b0d9) compared to base (2cfd26d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #122   +/-   ##
=======================================
  Coverage   84.43%   84.43%
=======================================
  Files          21       21
  Lines         938      938
=======================================
  Hits          792      792
  Misses        146      146

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.


[fix] service-worker builder constant replacement

Closes https://github.com/sveltejs/kit/issues/6329 and https://github.com/sveltejs/kit/issues/5682.
Implements Option 1 proposed by @Rich-Harris in https://github.com/sveltejs/kit/issues/6329#issuecomment-1229207997
Vite constant replacement using define only applies to service-worker builder.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[X] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[X] This message body should clearly illustrate what problems it solves.
[X] Ideally, include a test that fails without this PR but passes with it.

Tests

[X] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

thank you!


Any chance to get ES6 module build for the browser?

I want to use this lib in my front-end project, but the mainstream tooling has long dropped support of UMD. Latest Babel/Webpack can't digest UMD anymore.
Can you make an ES6 build?

@sergiucaraian

Sure. I'll fix it up during this week.


feature/restructure_libvectormap

Status
PRODUCTION
Description
#1653 libvectormap has been restructured in line with the other libs in common

@sgermanserrano Do you plan to update this PR?

@gbiggs we can tackle package restructuring in the new repos


Obsolete Incubator release directory tree

The following directory tree no longer appears to be needed, and should be removed please:
https://dist.apache.org/repos/dist/release/incubator/singa/

It has been removed. Thanks for the reminder.

Thanks!


fix: Invalid comparator semver error when using tag versions

Hey, great job with the project!
Small fix to cover the case when you're using tag versions.
Let's say you publish snapshots on npm with our bulbosaur example from docs :)
You have examples in monorepo which can be fired from web container like stackblitz or codesandbox, but we don't want (and should not) commit snapshot releases with versions back to repo. Tags are solutions to that problem, yet they're not a valid semver ranges, so we have for example (my case is canary tag):

which breaks whole release. I'll be very grateful for quickly releasing this fix if all looks good for you here. Cheers!

hey @Andarist!
Would you mind taking a look at this PR? It'd be super helpful to have this fix released :)

Hmm, the goal of the change looks OK to me. if you are using a tag - that's your choice and Changesets should leave this alone. However, I wonder if your use case is correct - snapshot releases were not designed to be committed. Whatever changes they make to package.json/CHANGELOG.md/etc files should be treated as disposable.

@Andarist thank you for your response. Maybe I wasn't clear but definitely we're not committing snapshots, but on the other hand we have stackblitz templates which should work with current master branch (so snapshot) published on npm, that's why templates are using snapshot tag, but on local envs it resolves to packages from monorepo.
Quick real life case:
https://github.com/shopware/frontends/blob/main/templates/vue-demo-store/package.json#L15 template package file, which on stackblitz takes tag version from npm and locally from package.
But having this setup it crasches during changelog version and that's why I creates this PR :)

Could you take a look at my other comment? I feel like I'm missing something about the nature of this bug (or your setup) - and I would like to commit this change only after understanding the full picture.

Great, I appreciate you taking the time to dive deeper into that to understand my issue. I'm aware this setup is not a common one, but I have good reasons for that, which I hope are also making sense to you :)

hey @Andarist, can I ask you to re-review this one? :)

hello @Andarist, you're probably busy, it there anyone else I could ping to make this go forward?

Hey @Andarist, as a patch it's working for 5 months now. Is there anything blocking you from merging that? Just to refresh memory - it's just making sure the whole process is not failing when we have an npm tag version instead of semver.

@patzick could you resolve conflicts here? Sorry for not getting back to you earlier here

@Andarist, no problem, thanks for getting back at this!
The conflict was caused by this: https://github.com/changesets/changesets/pull/1176/files#diff-73bc94618d4ce1bc263e6ecb9e90dee49072a5d789137c6b530dccd1f99fbcabL91-R95
all resolved now and my import also changed in the same tree-shake convention. Test passing locally

Hey @Andarist, can you merge it? After the new release, I needed to patch it once again in our code and I see new merge movements so probably new release is coming soon :)

@Andarist, all changes applied to suggestions and tests are passing

LGTM, it only needs some minor code shuffling related to the added test case.

Woah, I somehow missed that there was another question here. As I thought LGTM covered all changes and it's merged already :)
@Andarist do you think we can merge it so I won't have to patch it again when new version will be released? :)

Hey @Andarist - is there anything else keeping you from merging this PR?
Unfortunately, with every new release, I need to patch it with that fix to avoid crashes in the process :(
Let me know if I can assist somehow more to go through with that!

hey @Andarist!
I'm coming back with the question if we could merge this fix, it has been tested (as patches) in our project for over a year and the only thing is doing is preventing crashes by additional checks; nothing fancy, very useful though :)

Hello, @Andarist, I see some movements in the repo.
Could you please go back to this fix and merge it?

Respect! 💙


Images not working again?

Thanks so much for this plugin. I am working on a skeleton for using Grav to host open educational resources and this is a great little plugin to find!
I can't seem to get any images to work though for showing the licenses. A text-only license works fine, but all other options seem to produce empty rectangles. I am using Grav 1.1.12 and also am trying it out with the Gantry 5 plugin.
Thanks very much,
Paul

Hey Paul,
sorry for the late reply, I've been on vacation the last days.
There has been a problem with multi-language setup in the past, do you have multilanguage enabled?
Are the image-paths on the frontend correct?
I'll have a look at this when I get home from work.

Thanks very much for taking a look. No, I am not working with a multi-language setup.
Please let me know if you find anything, and I'd be happy to test any possible fixes.

Hi Paul,
I've just fiddled around a little bit on a fresh install but can't reproduce the missing images.
May be there is a conflicting plugin or a configuration I didn't have.
Could you provide some more information or a copy of your user folder?

Sure thing, here is my user folder.
user.zip
Thanks again,
Paul

There has to be something broken somewere else.
The images are working on my test-install: https://ccbuttons.bughunter2k.de/blog/open-blogging-1-2-3
But I've no idea where to look.

Thanks so much for taking the time to look into it, I will continue to try things on my end and see. I assume you are running latest version of Grav etc.?

It seems the installation in a subdirectory causes the bug.
I'm using the grav-locator to determine the path of the images
                $locator = GravTrait::getGrav()['locator'];                 $path = "/".$locator->findResource('plugin://cclinker/images/', false)."/";
Actually I'm not sure what has to be changed. I'm still trying to figure out.

Hi Paul,
found the bug and made a patch, Could you test the patch-branch on your site, please?
https://github.com/BugHunter2k/grav-plugin-cclinker/tree/BugHunter2k-patch-1

Excellent! The patch appears to fix things 🙂
http://test.hibbittsdesign.org/grav-skeleton-open-blog-site/
Thanks very much for addressing this issue!
Paul


How to parse multiple emails in vCard?

I tried out your example but it only reads one email address. There's vCards that have multiple email addresses (and phone numbers etc.) saved. i.e.
TEL;:+81-80-4116-1790
TEL;:+41786128748
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>EMAIL;X-Sonstiges:othermailyahoo.com
I only see one method to get one email address:
VCard vCard = VCardParser.parse(vCardString);
vCard.getEmail();
How to get the other email addresses and other fields?

Thanks for the report, now I will check the problem!

Hi ;-)
Thanks for your report, I have now updated the library.
Please update your version!
dependencies {
compile 'it.auron:mecard-parser:1.0.9'
}
https://github.com/RurioLuca/QrCardParsing
Let me know how you look ;-)
Best regards
Rurio Luca
2017-04-23 18:29 GMT+02:00 Dominik<EMAIL_ADDRESS>
I tried out your example but it only reads one email address. There's
vCards that have multiple email addresses (and phone numbers etc.) saved.
i.e.
TEL;:+81-80-4116-1790 <+81%2080-4116-1790>
TEL;:+41786128748 <+41%2078%20612%2087%2048>
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>EMAIL;X-Sonstiges:othermailyahoo.com
I only see one method to get one email address:
VCard vCard = VCardParser.parse(vCardString);
vCard.getEmail();
How to get the other email addresses and other fields?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/RurioLuca/QrCardParsing/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/APfVfO2rYZat_319JC3thDoKFIRfMmo6ks5ry3yFgaJpZM4NFdXD
.

The bug should be fixed, I've released version 1.0.9 now

Thanks for the quick reaction. I will try it out tonight.


Add Stars In the Sky by Kid Cudi

Song Name
Stars In the Sky
Artist Name
Kid Cudi
Source
Youtube
Youtube Link
efiLdiBk1f8
Direct File Link
No response
Song ID
7208
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 95118613
Downloaded: No

aceptar

accept

Thanks for contributing! Someone will soon review your request.
Here is the JSON result for the reviewer:
{
  "name": "Stars In the Sky",
  "artist": "Kid Cudi",
  "source": "youtube",
  "startOffset": 0,
  "yt-id": "efiLdiBk1f8",
  "songs": [
    7208
  ]
}

To accept the request, a reviewer needs to write "accept".

accept

accept
El dom, 10 nov 2024 a la(s) 4:58 p.m., auto-nong[bot] (
@.***) escribió:

Thanks for contributing!
Someone will soon review your request.
Here is the JSON result for the reviewer:
{
"name": "Stars In the Sky",
"artist": "Kid Cudi",
"source": "youtube",
"startOffset": 0,
"yt-id": "efiLdiBk1f8",
"songs": [
7208
]
}
To accept the request, a reviewer needs to write "accept".
—
Reply to this email directly, view it on GitHub
https://github.com/FlafyDev/auto-nong-indexes/issues/6203#issuecomment-2466975450,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BM2J2AMLUTX2MJBEIBFN6JLZ77QJDAVCNFSM6AAAAABRQVLBYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWHE3TKNBVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


(minor) URL parse regexp not allow "http://localhost:8080" (url without domain)

testit-importer-allure/src/configurator.py:242 - wont allow url without domain
testit -u http://localhost:8080 fails with "Wrong URL"
workaround use: http://<IP_ADDRESS>:8080

Good afternoon!
This bug has been fixed in the package version 1.2.4 https://github.com/testit-tms/importers/pull/23.
Thank you for contacting us!


Food Detection

💥 Proposal
I would like to make a food detector using Pytorch which takes in an image of a food and gives its name.

@karthikbhandary2 - please provide the dataset.

https://www.kaggle.com/datasets/dansbecker/food-101

@karthikbhandary2 - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.


feat: show multiple checkbox instead of button, default is show one

Remove button that toggles between show multiple and show one. Default is now show one, checkbox is added to show multiple
How-to-demo

start the backend using the frank-runner on master branch
start the frontend on branch: feat/show-one-show-multiple-checkbox
switch the white box drop down to database storage
click on a row in the table
see that only one record can be shown in the debug file tree below the table
open the setting popup from the button iun the top left corner under the debug tab
click the setting: Show multiple files in debug file-tree to enable the checkbox
click on multiple rows in the table and see that they open in the debug tree below the table

Notes

Setting value is saved to local storage

The  debug file tree keeps having multiple when I disable Show multiple files in debug file-tree again, this should probably clear the file tree so it reflects the changed setting

The debug file tree keeps having multiple when I disable Show multiple files in debug file-tree again, this should probably clear the file tree so it reflects the changed setting

Fixed!


Capture and ship log output

As metrics and logs belong together I suggest an option to capture stout and stderr of node apps and ship logs to Logsene without additional configuration of any log shipper.
Example to hook into stdout/stderr stream: https://gist.github.com/pguillory/729616

+1.  But how often are logs written to stdout/stderr?

Any updates on this one? I am using a morgan for logging the requests and I can't figure it out how to ship those logs to Logsene.

@istratievladut I see morgan can log to files.  Is that what you are doing with morgan by any chance?  If yes, you can use any log shipper, like e.g. https://github.com/sematext/logagent-js to ship logs.  If you are logging to stdout/stderr, then I think https://github.com/sematext/spm-agent-nodejs doesn't have anything for that yet and the above was just @megastef showing how it could be done.

I find this feature still interesting because it would not need any log shipper and would not require any code change for logging (see examples below).
@istratievladut  Using @sematext/logagent you could run node myapp.js | logagent -i YOUR_LOGSENE_TOKEN.
And I see that morgan accepts writeable streams, and you could use winston-stream if you use already winston-logsene you could provide the write function to wrap the winston-logsene logger :
var winston = require('winston')
var logsene = require('winston-logsene')
var logger = new winston.Logger()
logger.add (logsene, {
  token: process.env.LOGSENE_TOKEN,
  type: 'test_logs',
  url: 'https://logsene-receiver.sematext.com/_bulk'
})
var logseneStream = {
	write: (message) => {
		logger.info(message)
	}
}
// for Express app ...
app.use(morgan('combined', {stream: logseneStream}))

If you use upstart or systemd your logs would be captured by those Linux services and could be shipped with Logagent or any other log shipper.
If you run your node app on docker stdout/stderr could be captured by Sematext Docker Agent
So there are several options until we find the time to implement Capture and ship log output

the problem with winston-logsene though is that it is out of date in how to use it. the code you provided does not work.

winston-logsene will get updated to work with Winston 3.x in https://github.com/sematext/winston-logsene/issues/15

We will not add log shipping. You can always collect logs from stdout with Logagent and run e.g. run node myapp.js | logagent -i logs_token -e https://logsene-receiver.sematext.com
In case you use upstart or systemd, this blog post might be helpful:
https://www.nearform.com/blog/pino-the-fastest-node-js-logger-for-production/
If you run your app i containers, you can simply use Logagent for Docker: https://sematext.com/docs/logagent/installation-docker/


Errors not being handled correctly

Output from the task
Starting: Update JIRA status
==============================================================================
Task         : PowerShell
Description  : Run a PowerShell script on Linux, macOS, or Windows
Version      : 2.194.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
==============================================================================
Generating script.
========================== Starting Command Output ===========================
/usr/bin/pwsh -NoLogo -NoProfile -NonInteractive -Command . '/home/vsts/work/_temp/c8c03347-497e-4f0b-b5fa-9d587c92c8dc.ps1'
VERBOSE: Exporting function 'Add-JiraDeploymentInformation'.
VERBOSE: Exporting function 'Update-AzureDeploymentInformation'.

acceptedDeployments rejectedDeployments               unknownIssueKeys unknownA
                                                                       ssociati
                                                                       ons
------------------- -------------------               ---------------- --------
{}                  {@{key=; errors=System.Object[]}} {}               {}

Finishing: Update JIRA status

Background info about our pipeline setup

Using multi-stage, one stage per environment (Development, Staging, Production, etc)
Using multiple deploy jobs per stage

API
UI
Automated test suites

For each deploy job we use the task to update Jira with the deployment status of 'InProgress' (if successful) until we reach the last deploy job where we set the status as 'Successful' or 'Failed'

Please let me know if you need any info.

You can set $DebugPreference="Continue" in DeploymentScript.ps1 to display the entire response.

Enabling debug works, I'll open a separate ticket for the underlying issue.


Removed deplyment of  seperate folder for InterstellarHybridRocketry

What's the background here? Was this incorrect? Is it changing? Etc.

It has become obsolete, there now is much better support for aluminum propulsion integrated in KSPIE

OK, good luck! It may be a day or two before this takes effect as the NetKAN bot is currently experiencing some downtime.


Job variable type annotation / hinting confusion with 2.x style job API

Taking the current example at https://docs.nautobot.com/projects/core/en/latest/development/jobs/#variables
from nautobot.extras.jobs import Job, StringVar, IntegerVar, ObjectVar

class CreateDevices(Job):
    var1 = StringVar(...)
    var2 = IntegerVar(...)
    var3 = ObjectVar(...)

    def run(self, var1, var2, var3):
        ...

The style used here are PEP484 style type annotations (#3243 is about adding type hints) which ultimately confuses any IDE that respects PEP484 style annotations. In this case the value of var1 should be of type StringVar but instead it will be called with the actual user supplied value.

Are you able to post a screenshot of the IDE that is showing this behavior? We aren't subclassing typing.TypeVar so these shouldn't be mistaken for type hints.

You don't need to be subclassing TypeVar. The style used is type annotation syntax so when using the nautobot-ssot plugin which in every example involves saving those parameters to self.themselves then it causes a conflict.
So I guess okay Nautobot core is fine but it leads to a bad example / case in one of the major plugins.
Overall it's an awkward experience for a newcomer to the project trying to follow the docs and examples from the nautobot-ssot plugin.

@gsnider2195 https://github.com/nautobot/nautobot-plugin-ssot/blob/35803947ddd8f5c44bf9bbf0df2a91398e9c5539/nautobot_ssot/integrations/infoblox/jobs.py#L60-L65 that's an example of what I'm talking about. And that's the plugin that's up to date with the current 2.x and best practices.
You then have the Job object itself passed down into the adapters like in https://github.com/nautobot/nautobot-plugin-ssot/blob/35803947ddd8f5c44bf9bbf0df2a91398e9c5539/nautobot_ssot/integrations/infoblox/jobs.py#L49
This ultimately makes it not possible to fully type hint the SSoT code due to the circular references as well (ref #3243).
So can we agree it's a code smell then?

Thanks for opening the issue in the ssot repository. It may be more appropriate to put these variables in an inner meta class instead of as properties on the class itself.

Perhaps something like:
class MyJob(Job):
    inputs = {
        "var1": ObjectVar(...),
        "boolean_var": BooleanVar(...),
    }

    def run(self, var1, boolean_var):
        ...

or even:
class MyJob(Job):
    class Meta:
        inputs = {
            "var1": ObjectVar(...),
            "boolean_var": BooleanVar(...),
        }

    def run(self, var1, boolean_var):
        ...


"Our purpose" text in home page footer adjustment

Replacing the text in "Our Purpose"
The Dark Patterns Tip Line is a platform people can use to submit deceptive designs they encounter in everyday digital products and services. Through crowdsourcing human stories of digital manipulation and amplifying people’s voices, we will raise awareness of the real-life harms that result from deceptive design.
The submissions reflect the views of the people who submitted them, and not necessarily those of Consumer Reports. They have not been checked by Consumer Reports for accuracy.

@benrito this has been updated on the site

Looks good!


Filters on equipment on Crews page

On the Crews page, the filter for crews equips should be an AND, not an OR. If you select "Unique" and "Epic" on rarity for instance, then it'd show all the crews that satisfy any of those. For equips on the other hand you'd want the list that satifies both condition (having a head and a body item for example)

Yes, I'm still thinking about this feature because there are use case where the OR can be useful, for example you have an Heavy Assault Armor and a Lucky Red Lantern and you want to filter crew with Rush command that can fit this Body OR this Accessory and sort them by WPN stat, that will be impossible.
But in other side, if you want to get crew with this Body AND this Accessory, that's impossible now.

All other the conditions are mutually exclusive (you can't be Epic and Hero, or have Poison Gas and Freeze, etc), so it definitely has to be an OR. For equips, I still think that the great majority of test scenarios will involved having an AND (both slots), rather than an OR (any of the slots). There might be a few counter examples, like the one you listed, but in that case if you programmed it as an AND, the user could always just check first the crews with Body and Rush, and then lookup those with Accessory and Rush. If you used and OR on the other hand, there'd be no way to have the conjunction, you'd have to go through the whole list and try identifying who has both.
Ideally you could implement an option for both, adding "AND" and "OR" keywords in the filters for instance. But since of all the pages (crews, ships, items, etc) this field (equipment) is the only one in that case, I'm not sure it's worth the effort. Just using AND would be enough in my opinion.

Done in v2 😉


Remove unsafe impl of Add<usize> for &'a Relocatable

The impl of Add<usize> for  Relocatable should be used instead, which uses checked_add and handles potential overflows

I think the unwrap_or_default calls in the relocation functions becomes a silent failure. Maybe they should bubble up an error instead.


TypeScript Support for Generic SgNode

We could add more variants of SgNode, like SgNode<CallExpression>, SgNode<StringLiterial>
@babel/types is a good example for reference.

I found tree-sitter supports a node-types json metadata from which we can produce TypeScript definition.

See also:

https://github.com/tree-sitter/tree-sitter-typescript

TypeScript grammar for tree-sitter

Fixed by #1661


684ad23 breaks installation on Arch Linux

Arch Linux ships pynvim as-is, so pkg_resources failed to find the distribution called neovim.
Traceback (most recent call last):
  File "/usr/bin/nvr", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3252, in <module>
    def _initialize_master_working_set():
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3235, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3264, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 583, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'neovim' distribution was not found and is required by neovim-remote

I guess we talk about this package?
The issue is that this won't be good enough:
diff --git i/nvr/nvr.py w/nvr/nvr.py
index 20605b7..748c5b8 100644
--- i/nvr/nvr.py
+++ w/nvr/nvr.py
@@ -24,0 +25,5 @@ THE SOFTWARE.
+try:
+    import pynvim as neovim
+except ModuleNotFoundError:
+    import neovim
+
@@ -26 +30,0 @@ import argparse
-import neovim
@@ -35 +38,0 @@ import traceback
-

The problem is the neovim here. Unfortunately I don't see a good way to specify either one or the other, but some systems only provide neovim and others only pynvim.
In the best case, the aur package would just depend on the neovim package for now (in case there is a package for that).
I'll see if I can find a better way in the meanwhile.
@jamessan Any thoughts on this?

I guess we talk about this package?

Yes :)

The issue is that this won't be good enough:
diff --git i/nvr/nvr.py w/nvr/nvr.py
index 20605b7..748c5b8 100644
--- i/nvr/nvr.py
+++ w/nvr/nvr.py
@@ -24,0 +25,5 @@ THE SOFTWARE.
+try:
+    import pynvim as neovim
+except ModuleNotFoundError:
+    import neovim
+
@@ -26 +30,0 @@ import argparse
-import neovim
@@ -35 +38,0 @@ import traceback
-

The problem is the neovim here. Unfortunately I don't see a good way to specify either one or the other, but some systems only provide neovim (Debian stable) and others only pynvim (Arch).
In the best case, the aur package would just depend on the neovim package for now (in case there is a package for that).

Unfortunately no, in the official repository the name python-neovim is provided by python-pynvim, so there is only one pynvim (egg name, not import name) available in site-packages.
Currently, I'm just modifying setup.py to change the name back.

I'll see if I can find a better way in the meanwhile.
@jamessan Any thoughts on this?

I would actually prefer us to ignore issues that are hard (if not impossible) to solve cleanly due to old dependency versions. At least we should not break in a sane condition.

Right, if there's a choice between breaking outdated and up-to-date systems, we should probably go for the former. I'm about to just change it back to require pynvim instead.
Systems who only provide the old neovim as package, must fall back to using pip3 directly in that case. Should be no problem, since Debian/Ubuntu doesn't seem to package neovim-remote anyway.

@hexchain
After some more thinking about it, I'm pretty sure this way is the Right Thing To Do.
Thanks for bringing this up! :sparkles:


Question: How to use validate silent? Still results to wrong result

Versions

vee-validate: 2.1.3
vue: 2.#.#

Describe the bug
Adding silent to the validate option does not work. It returns false instead of true.
My main goal is to validate fields without adding errors to the error bag. I just want to know if it is valid or not. (I cannot use this.fields.myfield.valid because sometimes it is still set to undefined)
To reproduce
console.log(field)
console.log(await this.$validator.validate(field))
console.log(await this.$validator.validate(field, null, {silent: true}))
if(! await this.$validator.validate(field, null, {silent: true})) filled = false;

//results to:
//cuisines
//true (that is correct)
//false (that is incorrect)

Expected behavior
the last bool should be true!
Demo link
If applicable, add a minimal demo link to help explain your problem. You can use JSFiddle or Codesandbox.
Desktop (please complete the following information):

OS: [osx]
Browser Chrome

Fk me... It's not null it should be undefined...
console.log(await this.$validator.validate(field, undefined, {silent: true}))

sorry about the issue


/v1/log/entries/retrieve needs systematic test coverage.

Description
/v1/log/entries/retrieve is one of the more complicated APIs but lacks systematic test coverage and some code paths, like query by proposed entry, appear to have any test cases at all. There continue to be edge case bugs filed against this API. A systematic approach to testing would help harden the API for positive and negative cases.
Would adding this API to rekor-cli help? A lot of the e2e tests use the cli. The API is currently only used in a constrained way in verify.

I've always been curious why the rekor-cli get did not support getting by propsed entry.
I assumed that get should use SearchLogQuery which can handle the UUID, log index, and propsed entry. Meanwhile, get uses GetLogEntryByIndex or GetLogEntryByUUID.
IMO we should remove the redundancy here... if you have the index or entry UUID then use the v1/log/entries or v1/log/entries/UUID

IMO we should remove the redundancy here... if you have the index or entry UUID then use the v1/log/entries or v1/log/entries/UUID. I think log/retrieve should not re-implement those. But that's a pretty major breaking change, and I can understand why clients may want a handle-all endpoint.
The main benefit would be to fetch multiple log entries in the context of a single HTTP request.

The main benefit would be to fetch multiple log entries in the context of a single HTTP request.

OH I see. That was probably the entire intent of the separate endpoint? In that case I change my opinion. Fetching a range is good.

some notes I took while working #1144:
the API takes array of entryUUIDs, logIndices, and/or entries; for each of these three:

empty (expect empty array & HTTP 200)
one validly formed, and in log (expect success)
valid formed, but not in log (expect empty array & HTTP 200)
mix of validly formed (some correct, some incorrect) (expect only correct ones, HTTP 200)
malformed input (expect HTTP 400)
mix of validly formed and malformed (expect HTTP 400)
more than 10 total requested lookups (expect HTTP 429)

Also should consider searching entries that span multiple shards


Predicting on real test set gives only very high probability for 1 for a very unbalanced data

Hi guys,
Excuse me for this question without much details, because I'm bound with time in order to post my results on a challenge platform, anyway I try to sum up as much as I can. I have a multivariate time-series, that I trained using an RNN, there are periods and repeating time indexes, from 2013-01 to 2016-09, steps are months, by repeating, I mean various subsets ordered from January to December, many times for the same year, for hundreds of times, and I am predicting the next year knowing other features. I trained using LSTM, on 3 years, and trying to predict also repeating time-series for the year 2017. I used fixed batch size, and one last layer for binary target value so I used such a basic neural network:
model = Sequential()
model.add(LSTM(10, batch_input_shape=(12, train_X.shape[1], train_X.shape[2]), return_sequences=True, stateful=True, activation='sigmoid', inner_activation='hard_sigmoid'))
model.add(Dropout(0.2))
# model.add(LSTM(70))
# model.add(Dropout(0.3))
model.add(Flatten())
model.add(Dense(1, activation='sigmoid'))
model.compile(loss='binary_crossentropy',
optimizer='rmsprop',
metrics=['accuracy'])

The batch size is 12 ( I chose) for 12 months, the target in train is very unbalanced with
pd.value_counts(test_y)
1.0 163781
0.0 5551
dtype: int64

the problem is that predicting on test like
res = model.predict(t_e_s_t, batch_size=12)

res
array([[0.9633749 ],
[0.79078996],
[0.99266464],
...,
[0.9891131 ],
[0.7582535 ],
[0.95778626]], dtype=float32)

is very frustrating before posting my results as all values of probability are above 0.5 and near 1 that means no probability for any entry to be zero.
what could be wrong !!?
Many thanks !!
Hope to hear from you as soon as possible in order to tweak my model and get more coherent outputs ! :) :)

I added
from sklearn.utils import class_weight
class_weights = class_weight.compute_class_weight('balanced',
                                                 np.unique(train_y),
                                                 train_y)

and passed class_weights to fit method, still zero probability values are under 0.5.

I also have similar problem with very unbalanced data, want to hear the solution


Marker active color

Hi everybody;
How can I disable or remove marker outline color? It actives when marker mouse over and take low opacity of marker color? I dont want? My marker range is 4.5

SOLVED Myself
  marker: {
       ...
          states: {
            hover: {
              enabled: false
            }
          }
        }

Refer to:

https://github.com/AAChartModel/AAChartKit/issues/1345