Key sequence M-j starts with non-prefix key ESC (on M-x and some SPC prefixes)

Observed behavior
After commit 1f23eecdc877d3ece2330fb8ac4fbbe30c00e5a0, I keep getting this error, for example when issuing SPC f r, SPC p p or M-x.
For now, I just apply the following:
diff --git a/modules/config/default/+evil-bindings.el b/modules/config/default/+evil-bindings.el
index ae0f578a..6bbb90eb 100644
--- a/modules/config/default/+evil-bindings.el
+++ b/modules/config/default/+evil-bindings.el
@@ -278,7 +278,7 @@
             "C-j"     #'company-select-next-or-abort
             "C-k"     #'company-select-previous-or-abort
             "C-s"     (λ! (company-search-abort) (company-filter-candidates))
-            "ESC"     #'company-search-abort)
+            [escape]     #'company-search-abort)
           ;; TAB auto-completion in term buffers
           :map comint-mode-map "TAB" #'company-complete))

and it seems that it's working fine.
Expected behavior
Not get the error.
Steps to reproduce
After a new git clone, follow the appropriate steps and issue SPC f r or M-x.
System information

OpenBSD 6.5 GENERIC.MP#760 amd64
- OS: berkeley-unix (x86_64-unknown-openbsd)
- Emacs: 26.1 (Mar 01, 2019)
- Doom: 2.0.9 (develop a669406cad46f96ac842906f150391d5a5886ebf)
- Graphic display: t (daemon: nil)
- System features: XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK DBUS GSETTINGS NOTIFY GNUTLS LIBXML2 FREETYPE XFT ZLIB TOOLKIT_SCROLL_BARS GTK2 X11 THREADS LCMS2
- Details:
  ```elisp
  elc count: 0
  uname -a:  OpenBSD morgoth.lan 6.5 GENERIC.MP#760 amd64
  modules:   (:feature eval (evil +everywhere) file-templates (lookup +docsets) snippets workspaces :completion company (helm +fuzzy) :ui doom doom-dashboard doom-quit evil-goggles hl-todo indent-guides modeline nav-flash treemacs (popup +all +defaults) unicode vc-gutter vi-tilde-fringe window-select :editor fold multiple-cursors parinfer rotate-text :emacs dired electric eshell imenu vc :tools editorconfig flycheck flyspell magit password-store pdf :lang clojure data emacs-lisp latex markdown (org +attach +babel +capture +export +present +publish) perl (sh +fish) :app email irc :config default)
  packages:  ((geiser :modules ((:private))) (paredit :modules ((:private))) (pretty-mode :modules ((:private))) (w3m :modules ((:private))) (wttrin :modules ((:private))) (evil-leader :modules ((:private))) (nov :modules ((:private))) (chicken-scheme :modules ((:private))) (scheme-complete :modules ((:private))) (vlf :modules ((:private))) (ranger :modules ((:private) (:emacs . dired))) (transmission :modules ((:private))) (mu4e-alert :modules ((:private))) (helm-lobsters :modules ((:private))) (poet-theme :modules ((:private))) (tao-theme :modules ((:private))) (restclient :modules ((:private))) (request-deferred :modules ((:private))) (spacemacs-theme :modules ((:private))) (nyan-mode :modules ((:private))))
  exec-path: (~/bin /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /usr/local/bin /usr/local/sbin /usr/games /usr/local/plan9/bin ~/.local/bin ~/go/bin ~/.emacs.d-doom/bin /usr/local/jdk-1.8.0/bin /usr/local/libexec/emacs/26.1/amd64-unknown-openbsd)

p.s. As I have the opportunity, thank you for this truly amazing setup.
While I'm getting into scheme, I still don't have the knowledge to hack elisp code (yet). I suspect somehow the issue is PEBCAC.
[edit]: fix code block

I had a similar issue that made emacs unusable but the cause was not the same. It was because of some tweaks I had in place for evil-collections. It did happen in the company package though, guessing some change in evil-collections made my key translations screw things up.

I had a similar issue that made emacs unusable but the cause was not the same. It was because of some tweaks I had in place for evil-collections. It did happen in the company package though, guessing some change in evil-collections made my key translations screw things up.
This only happened on macos though, no issues in linux.

Thank you for pointing me to the right direction. It was indeed something in my config related to evil-collection. I managed to pinpoint the problem when I was calling (evil-collection-init).
Confirming that when commenting the above, I get no errors.
Once more, thank you so much and sorry for the noise.


POC data source view/create page with data loaded from/to OSD

Signed-off-by: Kristen Tian<EMAIL_ADDRESS>Description
POC data source view/create page with data loaded from/to OSD
Issues Resolved
tba

There are some comments mentioned in #3 and https://github.com/opensearch-project/OpenSearch-Dashboards/pull/1806. Let's resolve them in the next PR.


Load crate components on node startup again

This commit makes it possible to again start Crate from within Intellij.
But there are still some TODOs:
- BlobPlugin loads the HttpModule which causes guice errors
- plugins (admin-ui, aws, hdfs) are missing the plugin-descriptor
  files
- There are errors due to the SecurityManager

ack


SAK-32350 Don’t fail attachments in peer review mode.

When an assignment is in peer review student review mode there is an option for the student to provide attachments for their review, however we were attempting to check these with content-review which isn’t correct (and was failing). So this check has been disabled when in peer review mode.

I'd like to get this merged, anyone able to check it over?

I'm not following the comment string on line 17414 ... will defer

This is basically a addition of a check for peer review mode on line line 17375 but I extracted a variable to "make the code more readable", but I think it makes the change harder to understand. Maybe having done this as 2 commits would have been clearer.


(Minor Documentation Issue) magick: 2x is not supported

In the Filters section of the documentation, magick: 2x is included as an example, but this is not actually a supported value!

Yes it is: https://github.com/jekyll/jekyll-assets/blob/master/lib/jekyll/assets/proxies/magick.rb#L9 https://github.com/jekyll/jekyll-assets/blob/master/spec/tests/lib/jekyll/assets/addons/proxies/magick_spec.rb#L77.  we do not support spaces between key and value because we part like your CLI does so "magick:" and "2x" are each their own so you'll end up with "2x=true" on your HTML tag (or an error sometimes.) It needs to be "magic:2x" for it to work.

If you continue to have problems, do please let me know and I'll happily investigate further.


Edge function segfaults when served by CLI - but not in prod or with deno run

Describe the bug
I have an edge function that uses the node-onesignal package to send an email.
If I run it with supabase functions serve it starts fine, but when it's triggered (by curl for my testing) serve reports a segfault and exits.
The function works as expected when:

run with deno run --allow-net <path> and triggered by navigating to localhost:8000
deployed, then triggered by a webhook

It segfaults on await onesignal.createNotification(notification). If I comment that line out everything else works as expected.
To Reproduce

Create a new function

supabase functions new my-function

Replace my-function/index.ts with

import * as OneSignal from "https://esm.sh/<EMAIL_ADDRESS>
console.log("Hello from Functions!");

const _OnesignalAppId_ = "my_onesignal_app_id";
const _OnesignalUserAuthKey_ = "my_onesignal_userauth_key";
const _OnesignalRestApiKey_ = "my_onesignal_rest_api_key";

const onesignal = new OneSignal.DefaultApi(OneSignal.createConfiguration({
  userKey: _OnesignalUserAuthKey_,
  appKey: _OnesignalRestApiKey_,
}));

Deno.serve(async () => {
  const notification = new OneSignal.Notification();

  notification.app_id = _OnesignalAppId_;
  notification.include_email_tokens =<EMAIL_ADDRESS>  notification.email_body = "Body";
  notification.email_subject = "Subject";

  console.log("Sending");
  await onesignal.createNotification(notification);  // <-- This triggers the segfault
  console.log("Sent");

  return new Response();
});

Serve with

supabase functions serve --debug

Trigger with

curl --request POST 'http://localhost:54321/functions/v1/my-function' \
  --header 'Authorization: Bearer my_anon_key' \
  --header 'Content-Type: application/json'

See the following printed to console:

[Info] Sending

Segmentation fault (core dumped)
2023/11/08 19:01:16 Sent Header: Host [api.moby.localhost]
2023/11/08 19:01:16 Sent Header: User-Agent [Docker-Client/unknown-version (linux)]
2023/11/08 19:01:16 Send Done
2023/11/08 19:01:16 Recv First Byte
error running container: exit 139

Expected behavior
I would expect:

The function to execute successfully without hitting a segfault
The behaviour locally to match the behaviour in production (it works in production, the email is sent)

Desktop (please complete the following information):

OS: Ubuntu 22.04.3 LTS
Version of CLI: 1.111.2
Local Deno version: 1.38.0

Transferring because it sounds like an issue with edge runtime container.

Similar problem here. For me, it worked fine with the CLI version 1.106.1 but when I tried to upgrade it always lead to me getting the segfault. I am not using a third party package, though. Just making fetch calls to some APIs.


Can't access dapp from specific link when search on browser

Describe the bug
To reproduce the bug
Steps:

Go to the Browser tab
Input search = https://snapshot.org/#/moonbeam-foundation.eth/proposal/0xd054fc5486475ff01a1c2d7a5b7aa5a560e7f8e17860c1b0fe1707e1d30b2ab7
Observe the displayed screen
Actual: Do not show the correct link

https://github.com/Koniverse/SubWallet-Mobile/assets/117999489/7195bca7-8ead-448e-bf9b-47acf799c44f

Version test: v1.0.11(203)
Devices test: IP 11
@nguyenduythuc Please re-check this issue


build(deps): bump intl from 0.18.1 to 0.19.0

Connection with issue(s)

Close #92
Close #91
Close #90
Solution description
Upgrades the intl package to 0.19.0 so that Flutter SDK v3.22.0 is supported.
Screenshots or Videos

To Do

[x] Read contributing guide
[x] Check the original issue to confirm it is fully satisfied
[x] Add solution description to help guide reviewers
[ ] Add unit test to verify new or fixed behaviour
[ ] If apply, add documentation to code properties and package readme

How soon can this be merged please? @deandreamatias

Had some error that isn't related to the intl dependency but with increase flutter version (I guess).
https://github.com/flutter-form-builder-ecosystem/form_builder_validators/actions/runs/9104136037/job/25067818196?pr=93
Take a look if can solve

@deandreamatias It seems the project is using gradle 6.7. When running a flotter create xxx with the current Flutter 3.22, it uses gradle 7.6.3.
Possibly upgrading the gradle included in the project fixes this. You can try the instructions at Android Java Gradle migration guide which would come down to:
cd android
./gradlew wrapper --gradle-version=7.6.3

My personal experience with upgrading gradle in an existing Flutter project has been sketchy. What eventually fixed it for me was to
cd /tmp
flutter create form_builder_validators

and then just copy the /tmp/form_builder_validators/android folder over the existing project's android folder. If you previously modified any files in the project's android folder (e.g. adding properties), you will need to repeat these modifications.


Tune PID controller for UR5 Gazebo

Right now the arm controllers are unstable / have steady state error. PID values need tuning (in file marimbabot_ur5_moveit_config/config/arm_controller_ur5.yaml)

TODO: Norman suggested that we should try just adding the mallet to his setup (tams_ur5_gazebo) and see if the default PID values work in that case

UPD: The default PID values cause shaking for smaller movements (e.g. move pan by 0.1 rad) while being stable for long-range movements (e.g. from one predefined position to another). Thanks @normanhendrich for testing this with default UR5 setup.
Sensible next step is to test the motion planning scripts in Gazebo and tune the PID values based on that. I will get on that as soon as #80 is merged.

What is the current status?
@ateRstones  and I wondered

I think they were tuned some time ago. If there are still issues open another ticket.


Meross outdoor plug dimmer MPD100

Hello,
can you assist me to properly configure your plugin? I wrote my credential properly but no device detect in ''cache''
What I did wrong?
Please
jDaniel

Sorry same as issue 551


[Numpy] FFI: random.shuffle, equal, not_equal, less_equal, greater_equal, less, maximum and minimum

Description
Add FFI support of

random.shuffle

equal, not_equal, less_equal, greater_equal, less

maximum, minimum

| Old FFI (ctypes) (us) | New FFI (cython) (us)
-- | -- | --
random.shuffle | 16.7 | 4.74
equal | 26.41 | 9.65
not_equal | 25.88 | 9.22
less_equal | 25.9 | 9.23
greater_equal | 61.6 | 29.95
less | 26.03 | 9.27
maximum | 24.61 | 8.17
minimum | 24.5 | 8.02
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

LGTM

@mxnet-bot run ci [windows-gpu]

@mxnet-bot run ci [unix-gpu]


Azure Maps control code samples - comments regarding clientId are misleading

Several of the code samples throughout the docs contain this comment for clientId:
//Your Azure Active Directory client id for accessing your Azure Maps account

This is incorrect. Anyone looking at this will try to place a clientId from an AAD app registration here, which would not work. This is the Azure Maps client ID that is retrieved from the following location, and as far as I can tell, it has nothing to do with AAD.

Please correct this in all code samples to // azure map account client id like in this code sample: https://docs.microsoft.com/en-us/azure/azure-maps/how-to-secure-spa-app#create-an-azure-function

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

ID: 4dbd1c7c-f712-ae16-529c-645da8646f2a
Version Independent ID: 15786e93-71fa-80b4-4436-e0c1f7e024a9
Content: Create a map with Azure Maps
Content Source: articles/azure-maps/map-create.md
Service: azure-maps
GitHub Login: @anastasia-ms
Microsoft Alias: v-stharr

Thanks for taking time to share your valuable feedback! We are taking a look into this and will get back to you soon.

Hello @anthonychu Sorry for the delay, we are working internally with the team on this issue, we will keep u posted.

Hello @stevemunk Thanks for helping in this matter.

@anthonychu That comment is technically accurate, The Azure Active Directory client id is the same value as the Azure Maps account client id. I went ahead and changed these anyway.

@stevemunk Thanks for updating it.
@anthonychu We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[stable/prometheus] added additional ports option for server & headless service

Signed-off-by: 하광일/TC_Core Engineering<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

i need to add grpc (10901) & http (10902) port for thanos sidecar


Invalid HTTP response can crash Guzzle-Event-Loop

Guzzle version(s) affected: 6.5.1
Description
If a (broken) server responds with a "HTTP/1.1 404: Not Found" header (note the wrong colon!) after being redirected, the promise is not normally rejected, but the $promise->wait(); call throws an Exception ("Status code must be an integer value.") - and exits the event-loop completely (very bad when having concurrent requests).
How to reproduce
Start two "HTTP test servers" ...
... one on port 18000 that redirects to port 18001:
cat <<EOF | nc -N -l -p 18000
HTTP/1.1 301 Moved Permanently
Connection: close
Location: http://localhost:18001/

EOF

... and one on port 18001 that sends the broken header with the colon after "404":
cat <<EOF | nc -N -l -p 18001
HTTP/1.1 404: Not Found
Connection: close

EOF

... then execute this script:
$url = 'http://localhost:18000/';

try {
    $client = new \GuzzleHttp\Client();
    $client->requestAsync('GET', $url)->then(function ($response) {
        echo 'Response Status-Code: ' . $response->getStatusCode() . PHP_EOL;
    }, function ($e) {
        echo 'Normal Error: ' . $e->getMessage() . PHP_EOL;
    })->wait();
} catch (\Exception $e) {
    echo 'Unexpected Error (should never happen): ' . $e->getMessage() . PHP_EOL;
}

It will run into the "Unexpected Error"-catch.
Possible Solution
The problem is, that $easy->createResponse(); in https://github.com/guzzle/guzzle/blob/master/src/Handler/CurlFactory.php#L569 can throw exceptions, but is not inside a try-catch.
Maybe it is the best, to just expand the try-catch for "$onHeaders"-callback so that the $easy->createResponse(); is covered, too?

Also seeing this issue

@not-implemented have you found a workaround for this?
Even if I try/catch the exception the code still exits
try{
	$results = GuzzlePromise\settle($requestPromises)->wait();
}
catch(Exception $e){
	$msg = __METHOD__ . ' : exception for sites: ' . var_export( $sitesToCheck, true ) . ' exception: ' .
	get_class($e) . ' code: ' . $e->getCode() . ' message: ' . $e->getMessage() . ' trace: ' .
	$e->getTraceAsString();

	$this->logger->err( $msg );
}

Output
  [InvalidArgumentException]
  Status code must be an integer value between 1xx and 5xx.

Exception trace:
 () at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/psr7/src/Response.php:151
 GuzzleHttp\Psr7\Response->assertStatusCodeRange() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/psr7/src/Response.php:98
 GuzzleHttp\Psr7\Response->__construct() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/guzzle/src/Handler/EasyHandle.php:81
 GuzzleHttp\Handler\EasyHandle->createResponse() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:560
 GuzzleHttp\Handler\CurlFactory->GuzzleHttp\Handler\{closure}() at n/a:n/a
 curl_multi_exec() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php:114
 GuzzleHttp\Handler\CurlMultiHandler->tick() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php:131
 GuzzleHttp\Handler\CurlMultiHandler->execute() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:246
 GuzzleHttp\Promise\Promise->invokeWaitFn() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:223
 GuzzleHttp\Promise\Promise->waitIfPending() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:267
 GuzzleHttp\Promise\Promise->invokeWaitList() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:225
 GuzzleHttp\Promise\Promise->waitIfPending() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:62
 GuzzleHttp\Promise\Promise->wait() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/EachPromise.php:101
 GuzzleHttp\Promise\EachPromise->GuzzleHttp\Promise\{closure}() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:246
 GuzzleHttp\Promise\Promise->invokeWaitFn() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:223
 GuzzleHttp\Promise\Promise->waitIfPending() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:267
 GuzzleHttp\Promise\Promise->invokeWaitList() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:225
 GuzzleHttp\Promise\Promise->waitIfPending() at /var/www/sitecrawler/symfony3/vendor/guzzlehttp/promises/src/Promise.php:62

and $this->logger->err( $msg ); is never called

Another quick update on this, i see the problem when a standard 303 response is received. I guess guzzle does not handle it well?
Curl call returns a standard 303 as shown below. I wonder why Guzzle just panics on this.
curl -v bandwidth-infr******re.com
* Rebuilt URL to: bandwidth-infr******re.com/
*   Trying 64.***.30...
* TCP_NODELAY set
* Connected to bandwidth-infr******re.com (64.***.30) port 80 (#0)
> GET / HTTP/1.1
> Host: bandwidth-infr******re.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 303 See Other
< Content-Type: text/html; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Status: 303 See Other
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< Location: http://www.linkedin.com/in/e******a
< Cache-Control: no-cache
< X-Request-Id: 71b5c939-55fe-4416-8987-ce20f77a74ff
< X-Runtime: 0.004081
< X-Powered-By: Phusion Passenger 4.0.53
< Date: Thu, 05 Dec 2019 12:03:39 GMT
< Server: nginx/1.6.2 + Phusion Passenger 4.0.53
< P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
<
* Connection #0 to host bandwidth-infrastructure.com left intact
You are being redirected.

@bizmate No I do not have a workaround for this :-(

#2591 may fix this

This is fixed in 7.2.0


GIF color issues

I'm seeing some really bad color palette issues when trying to use this, possibly because I'm trying to push it too far. Here's what I'm seeing:

Generated with this code:
var numFrames = 50;
var width = 300;
var height = 300;

var canvas = document.querySelector("canvas");
canvas.width = width;
canvas.height = height;

var gif = new GIF({
  workers: 4,
  workerScript: "gif.worker.js",
});

gif.on("finished", function(blob) {
  var img = document.querySelector("img");
  img.src = URL.createObjectURL(blob);
});

var ctx = canvas.getContext("2d");
ctx.textAlign = "center";
ctx.textBaseline = "middle";
ctx.font = "bold 30px Helvetica";

var i = 0;
function renderFrame() {
  var p = (i + 1) / numFrames;

  var grad = ctx.createLinearGradient(0, 0, 0, p*height);
  grad.addColorStop(0, "#d4e5f6");
  grad.addColorStop(1, "#5183c8");
  ctx.fillStyle = grad;
  ctx.fillRect(0, 0, width, height);

  ctx.fillStyle = "black"
  ctx.fillText("😀", width/2, height/2);

  gif.addFrame(canvas, {
    copy: true,
    delay: 200,
  });

  i++;
  if (i < numFrames) {
    setTimeout(renderFrame, 0);
  } else {
    gif.render();
  }
}
renderFrame();

Link to codepen.
Now, I know that gifs aren't going to encode gradients well, due to the limited color depth. My problem is that the emoji in the center is so unstable, changing drastically from frame to frame. In fact, if I remove the gradient and just use a moving 2 color background, I still see issues with the emoji, although not as bad:

Codepen for this gif.
Am I trying to push gif.js too far, or is this the result of a bug?

You've hit a limitation of the color quantization algorithm, what you can do is increase the sample frequency to make it more accurate, options.quality or use the (undocumented because buggy) globalPalette option


UnicodeDecodeError: 'utf-8' codec can't decode byte 0xbb in position 438: invalid start byte

diff-cover generate diff report with --src-roots, the follwing exception occured due to differrent source code encoding format in projects:
Traceback (most recent call last):
File "/usr/local/python3/bin/diff-cover", line 8, in
sys.exit(main())
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/diff_cover_tool.py", line 232, in main
percent_covered = generate_coverage_report(
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/diff_cover_tool.py", line 195, in generate_coverage_report
reporter.generate_report(output_file)
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 251, in generate_report
report = template.render(self._context())
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 300, in _context
context = super().report_dict()
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 183, in report_dict
src_stats = {src: self._src_path_stats(src) for src in self.src_paths()}
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 183, in
src_stats = {src: self._src_path_stats(src) for src in self.src_paths()}
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 343, in _src_path_stats
formatted_snippets = Snippet.load_formatted_snippets(
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/snippets.py", line 175, in load_formatted_snippets
snippet_list = cls.load_snippets(src_path, violation_lines)
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/snippets.py", line 198, in load_snippets
contents = src_file.read()
File "/usr/local/python3/lib/python3.9/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xbb in position 438: invalid start byte.

Can you give me a bit more info to reproduce? What encoding is your source files?

Can you give me a bit more info to reproduce? What encoding is your source files?

currently, in a project,  some source files are "fileencoding=utf-8", and others are "fileencoding=latin1".

currently, in a project,  some source files are "fileencoding=utf-8", and others are "fileencoding=latin1".

Hmm, multiple encodings.
Kk, I'll do some thinking. I got a couple ideas.
On Tue, Jan 19, 2021, 10:41 PM realhac<EMAIL_ADDRESS>wrote:

currently, in a project, some source files are "fileencoding=utf-8", and
others are "fileencoding=latin1".
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Bachmann1234/diff_cover/issues/167#issuecomment-763308180,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALTLRJYBIDITMHWCAT7EN3S2ZGHVANCNFSM4WKARMBA
.

Hmm, multiple encodings.
Kk, I'll do some thinking. I got a couple ideas.
On Tue, Jan 19, 2021, 10:41 PM realhac<EMAIL_ADDRESS>wrote:

currently, in a project, some source files are "fileencoding=utf-8", and
others are "fileencoding=latin1".
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Bachmann1234/diff_cover/issues/167#issuecomment-763308180,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALTLRJYBIDITMHWCAT7EN3S2ZGHVANCNFSM4WKARMBA
.

@realhac I took a stab at fixing this in a way that would require no change on your side. Let me know if 4.2.0 https://pypi.org/project/diff-cover/4.2.0/ works for you.
If not I think I will have to go in and allow users to specify what encodings I should be expecting.

@realhac I took a stab at fixing this in a way that would require no change on your side. Let me know if 4.2.0 https://pypi.org/project/diff-cover/4.2.0/ works for you.
If not I think I will have to go in and allow users to specify what encodings I should be expecting.

sorry for late. It seems not well.
Traceback (most recent call last):
File "/usr/local/python3/bin/diff-cover", line 8, in
sys.exit(main())
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/diff_cover_tool.py", line 232, in main
percent_covered = generate_coverage_report(
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/diff_cover_tool.py", line 195, in generate_coverage_report
reporter.generate_report(output_file)
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 251, in generate_report
report = template.render(self._context())
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 300, in _context
context = super().report_dict()
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 183, in report_dict
src_stats = {src: self._src_path_stats(src) for src in self.src_paths()}
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 183, in
src_stats = {src: self._src_path_stats(src) for src in self.src_paths()}
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 343, in _src_path_stats
formatted_snippets = Snippet.load_formatted_snippets(
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/snippets.py", line 176, in load_formatted_snippets
snippet_list = cls.load_snippets(src_path, violation_lines)
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/snippets.py", line 206, in load_snippets
contents = src_file.read()
File "/usr/local/python3/lib/python3.9/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc9 in position 2936: invalid continuation byte

sorry for late. It seems not well.
Traceback (most recent call last):
File "/usr/local/python3/bin/diff-cover", line 8, in
sys.exit(main())
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/diff_cover_tool.py", line 232, in main
percent_covered = generate_coverage_report(
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/diff_cover_tool.py", line 195, in generate_coverage_report
reporter.generate_report(output_file)
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 251, in generate_report
report = template.render(self._context())
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 300, in _context
context = super().report_dict()
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 183, in report_dict
src_stats = {src: self._src_path_stats(src) for src in self.src_paths()}
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 183, in
src_stats = {src: self._src_path_stats(src) for src in self.src_paths()}
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/report_generator.py", line 343, in _src_path_stats
formatted_snippets = Snippet.load_formatted_snippets(
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/snippets.py", line 176, in load_formatted_snippets
snippet_list = cls.load_snippets(src_path, violation_lines)
File "/usr/local/python3/lib/python3.9/site-packages/diff_cover/snippets.py", line 206, in load_snippets
contents = src_file.read()
File "/usr/local/python3/lib/python3.9/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc9 in position 2936: invalid continuation byte

Alrighty, I'll take another stab at this over the weekend.

Alrighty, I'll take another stab at this over the weekend.

Ok, I think I got at least this issue with https://pypi.org/project/diff-cover/4.2.1/
I was a bit lazy last time and did not reproduce with a test.
I am not 100% sure if I have solved this entirely. An example project to try would verify that. But how about you give 4.2.1 a shot and see if it works

Ok, I think I got at least this issue with https://pypi.org/project/diff-cover/4.2.1/
I was a bit lazy last time and did not reproduce with a test.
I am not 100% sure if I have solved this entirely. An example project to try would verify that. But how about you give 4.2.1 a shot and see if it works

It looks like you have resolved this issue, thanks.
Total:   12 lines
Missing: 10 lines
Coverage: 16%

woot!


BasicDrawer-BasicForm-ApiTreeSelect只有第一次执行fetch，没办法每次打开Drawer，ApiTreeSelect请求一次数据

⚠ IMPORTANT ⚠ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

[ ] Read the docs.
[ ] Make sure the code is up to date. (Some bugs have been fixed in the latest code)
[ ] This is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Describe the bug
A clear and concise description of what the bug is..
Reproduction
Please describe the steps of the problem in detail to ensure that we can restore the correct problem
System Info

Operating System:
Node version:
Package manager (npm/yarn/pnpm) and version:

请问问题解决了么，我现在也碰到了这样的问题

请参考 drawer 属性 destroyOnClose


[#43] Testing Travis Ci and Static Analysis integration

Implementation of a Static Analysis Coverage during a PR to allow Users see the quality of their implemented code

All good.


Sloppy (1px-off) visuals of Slider knobs, grooves etc.

A regression after I tried silencing the warnings of the int -> float conversion chain in the ctor by starting out with floats...
If I leave the original ints, it all looks fine, but there're 10 warnings to tame. :)
It was the int size basically, so going for short instead did the trick. :)
Note that I (mostly) ended up with unsigned short, as that's a better abstraction there.
Also changed the API from int to float, to

be more flexible (preparing to arbitrary ranges later: #49), and to
get rid of the nasty inconsistency causing int/float conv. warnings for pbarScale->setValue(sliderScale->getValue()) in the demo (see #4, #3).

BTW, also changed its confusing m_box member to m_groove.

Dammit... -> #104!

I had to add floor() to updateHandlePosition:
void Slider::updateHandlePosition()
{
    if (m_orientation == Horizontal)
    {
        float max = getSize().x - m_handle.getSize().x - Theme::borderSize * 2;
        float x = floor(max * m_value / 100 + Theme::borderSize);
        m_handle.setPosition(x, 0);
        m_progression[2].position.x = x;
        m_progression[3].position.x = x;
    }
    else
    {
        float max = getSize().y - m_handle.getSize().y - Theme::borderSize * 2;
        float reverse_value = 100.f - m_value;
        float y = floor(max * reverse_value / 100 + (float)Theme::borderSize);
        m_handle.setPosition(0, y);
        m_progression[0].position.y = y;
        m_progression[2].position.y = y;
    }
}


Fail to open capture device

My system is
Ubuntu 14.04.5 LTS
Python 3.5

I have a virtual environment with
$ pip freeze
numpy==1.11.1
opencv-python==<IP_ADDRESS>

Any try on opening a VideoCapture fails... Any of the following always return False when I test with cap.isOpened()
cap = cv2.VideoCapture(full_path_to_video_file)
cap = cv2.VideoCapture(0)
cap = cv2.VideoCapture(-1)

I have ffmpeg installed and other OpenCV installations from source on my system work fine.
I was now giving a try with your package but it is not working. What am I missing? Do I need to link ffmpeg in some way?

The Linux builds have been built without ffmpeg. I can enable it (and I'm looking into #6), but there remains the GPL/LGPL licensing issue. Statically linking the ffmpeg to the cv2.so is a no go (I don't know if this is even possible). Shipping the shared ffmpeg lib with the package might be possible. Another solution is to build the package with ffmpeg support and then users manually install ffmpeg on their systems.

The Linux wheel built this way is useless to me then. A shame, for this could be an easy way to get OpenCV rolling in my environments. I have gstreamer also installed but it looks like it is of no help.
The lack of ffmpeg codecs could be the reason why I can not read my videos, but what about the camera? Any hints on how I can work through this?
Anyone using this on Linux with success? Can anyone cv2.VideoCapture(0) even without ffmpeg enabled?

Using the wheels built here, I cannot get capture devices to work on either OS X or Linux (Ubuntu).

It looks like windows support was added: https://github.com/skvark/opencv-python/pull/15

Haven't found yet enough time to enable ffmpeg on Linux/OS X. Yes, Windows support was a lot easier to add than for example Linux because precompiled ffmpeg shared libs are provided within OpenCV.

https://github.com/opencv/opencv/tree/master/3rdparty/ffmpeg talks about various options around ffmpeg, etc and dealing with licenses. It seems that at least on OS X, oepncv should link against AVFoundation.
It might also be worth looking at how brew builds opencv3: https://github.com/Homebrew/homebrew-science/blob/master/opencv3.rb

There is also some flag: WITH_AVFOUNDATION.

I might have figured out a way to include FFmpeg support to the Linux (and maybe MacOS too) builds without actually shipping the library itself within the package. This will of course require a proof of concept first, but this is roughly the idea:

Find somewhere a fresh dev build of FFmpeg for Cent OS 5 or compile it manually
Compile OpenCV against it
Patch the resulting binary with PatchELF which comes pre-installed in the manylinux containers

this means that any needed link time dependencies (DT_NEEDED) related to FFmpeg will be removed

Users can install the opencv-python as before and it will import without any issues, BUT:

video I/O is supported given that FFmpeg has been separately installed in the system and it is API/ABI compatible with the one that OpenCV was compiled against
trying to use video related functions without FFmpeg will most likely result in undefined symbol / some other error and terminate the program

It will take some time to test this, so do not except video support any time soon. I haven't forgotten this or the other issues :)

@skvark is it in progress? are there any rc with it already? Thanks m8

I'm waiting for pull request for macOS support, see https://github.com/skvark/opencv-python/issues/49. For Linux builds FFmpeg will be added hopefully during this year.

How is V4L2 (using VideoCapture with webcams) related to FFmpeg in any way? The two are orthogonal (except maybe to support h264 webcams, which are somewhat rare anyway).
Is there a problem building with V4L2 support with the manylinux setup?

I haven't tried, but I hope it works. I'm just trying to provide consistent and comprehensive packages across different platforms given that Windows builds already use FFmpeg for video I/O and macOS builds will have FFmpeg support hopefully soon.

Closing in favor of #50 and #56.

As @kerio92  mentioned. We could have webcam video capture enabled without FFMPEG.
Its a totally separate flag and dependency to enable V4L2 support in OpenCV.

FFmpeg will be supported in the next release. I will try to enable V4L2 also.

Once it's released I can help testing it.


3.1.1 easeui integration cocoapods

Please specify the 3rd party dependency in the podfile so that we can resolve the duplicate problem


Test deserializing TagContext with all duplicate keys that is over size limit.

TagContextBinarySerializer.fromByteArray should throw an exception, even though
the input represents a relatively small TagContext.

See https://github.com/census-instrumentation/opencensus-specs/issues/12#issuecomment-345353825.

Coverage remained the same at 81.252% when pulling b9a69dc944c75483a39827618b3457b8839f91b3 on sebright:test-deserializing-duplicate-keys-over-size-limit into 4c36f49f34fe0127d2c59a78ec0d9211113cf2ca on census-instrumentation:master.


New untitiled file not saved on exit

OS Version: I see it both on el capitan and linux

Steps to Reproduce:

file > new file > write some simple content
exit vscode - you get a prompt if you want to save, click 'Save' > name the file and sav it inside the repo
no changes are visible in repository - vscode is still open, and there is no file that I just saved. I still see the untitiled file open and there is no way for me to save it's content

Looks good with latest build


how this can field cardview

cardview can input field?

Do you mean that using UITextField for like cardBrandName UILabels ? If you do, I can upgrade the iCard with using this place using UITextField. Also you can easily change the UILabels automatically.


Referenced Microsoft.ML preview package not accessible

The machine learning notebooks reference Microsoft.ML version 2.0.0-preview.22356.1 from a private Azure DevOps server. This preview version of the Microsoft.ML package is not available from nuget.org making it hard to run the notebooks.

PackageManagement Error 3217 Invalid URI: The format of the URI could not be determined.

@wldevries they’re all public feeds.
Can you share a screenshot of what you’re seeing?
sharing the notebook would be helpful too!

This is what I'm seeing. Note that I'm using Notebook Editor in Visual Studio Pro 2022.

That's so strange ..
What happens when you visit https://pkgs.dev.azure.com/dnceng/public/_packaging/MachineLearning/nuget/v3/index.json in your browser?

@michaelgsharp is there any reason why this feed might be having issues?

That url returns a json, but most of the links in there return "The resource cannot be found."

@wldevries - can you check your NuGet configs to see what other feeds are in there?
They're usually at these locations:
%appdata%\NuGet\NuGet.Config
%ProgramFiles(x86)%\NuGet\Config

I have some local directories, a local server and the following official source declared:
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />

Can you try removing any local directories and servers temporarily?
I think this is a bug on our end but I want to try to understand what the problem is.

@wldevries - are there any special characters in the path that didn't work?
It might be related to: https://github.com/dotnet/fsharp/issues/12401

It's not only local Nuget that is the problem:

My Azure Dev-Ops hosted nuget feed throws a 401.
Had to uncheck it and restart VS 2022 before I could run the 1st couple of steps in the notebook


Add options to choose JSX file extension .js or .jsx

I want to keep jsx in the file content, so I choose:
        "jsx": "preserve"

but the generated file has jsx extension and ReactNative refuse to recognize this extension.
So there needs an option to let JSX format file using js extension.

Yeah I met the same problem.
I would like to see the compiled file with jsx expression because that's clear but I do not want the .jsx extension. React Native just does not recognize them.

I'd propose an option preserveJs that retains JSX expressions but computes the filename as .js. This should be a fairly easy change if someone wants to send a PR for it

@RyanCavanaugh I'd love to take this! Can you give me any other direction?

Actually it looks like https://github.com/Microsoft/TypeScript/pull/9864/files targets this?

I'm a big fan of keeping jsx out of .js files :) but thats just my opinion and I haven't done react native :rose:

I think this can be closed, implemented in #13636.


Unwanted Permission Exception

While playing youtube video through this library it is throwing unwanted permission exceptions E.g
"W/CameraBase: An error occurred while connecting to camera 1: Status(-8): '1: validateClientPermissionsLocked:913: Caller "com.my_packagename" (PID 10380, UID 13672) cannot open camera "1" without camera permission' "
An error like failed to connect to camera service and all. Why this permission needed when it's had nothing to do with camera or all. I am using core library not even that chromecast so why these all exceptions occurring?

I doubt that message is coming from the library.


adhoc filter generate wrong sql

Describe the bug
ad hoc filter generated wrong sql ( missing quote ? )  when the column type is String and the value is a numeric string.
Versions
Grafana and Plugin versions.
Grafana version: 8.2.7
plugin version: 1.1.2
Query
please look at the screenshot below
Expected behavior
always generate correct sql
Screenshots

table description:

please forgive my poor english

I believe changes to Grafana core will need to be made to solve this issue. Right now we try to parse the ad hoc query
results into a number. If the results do not parse into a number we assume it's a string.
You could work around this issue by using a template variable for app_id and add a where clause to your query using the template variable.

I believe changes to Grafana core will need to be made to solve this issue. Right now we try to parse the ad hoc query results into a number. If the results do not parse into a number we assume it's a string.
You could work around this issue by using a template variable for app_id and add a where clause to your query using the template variable.

thanks for the reply; BTW, does the Grafana team know about this issue, or  have a plan to fix it? thanks again.

I've made the team aware of this issue. I am not sure how/when this will be fixed. I'll update this ticket when I learn more 🙂

I've made the team aware of this issue. I am not sure how/when this will be fixed. I'll update this issue when I learn more 🙂

thanks！！

This should no longer be as of the 2.0 release. Please reopen if this is not fixed.


vite-plugin-top-level-await breaks source map generation in Vite

So, we've noticed that our source maps were broken since switching to Vite. Most of the generated bundles were missing the //# sourceMappingURL=... annotation.
We ended up having to deactivate all our Vite plugins one by one, and this one turned out to be the culprit. Unfortunately, I have not done any further digging so I cannot offer any further insight, but I still thought it prudent to open this issue so others who run across the same problem might find it.
Is this a known issue in general or does this work for everyone else?

Yes. I'm sorry it's broken. I didn't handle source-map.

I had the same problem. I need to produce source-map in my production code and this plugin messed with the sourcemap creation .

Is there a fix to be expected for this any time soon?

But I have no idea of how to implement this...


Improve these docs links should open in new tab

For anyone looking to take a stab at this:
The denalijs.org website is built from the docs branch of this repo, specifically the src/ folder. The templates in src/layouts/ and src/templates are probably the best place to get started. A quick search through the source should show all the anchor tags that need updating. Check the Readme for that branch for details on how to preview the site locally.


Fix typo around CTFontManagerRegisterGraphicsFont.

Hey @sapzildj,
The guard statement is correct as-is, since the code after the statement handles any errors in the CTFontManagerRegisterGraphicsFont function. We only report an error if the function fails.
guard !CTFontManagerRegisterGraphicsFont(font, &error) else {
   // Font registered successfully
}
// Error occurred while registering font

The code could probably be improved to make it a little more clear, but the functionality is correct. Thanks for reaching out though!
FYI, active development on this framework has been moved to jlandon/alexandria, so if you like to get the latest releases and/or contribute in the future, check out that repo.


set month and year same time

How to change month and year in the same time?
I am currently using
calendar.setYear(year);
calendar.setMonth(month);

But i have an ajax event on doneRendering. When I change the days with above codes it loads ajax data two times.
I want a function similiar to setYearAndMonth

Hello @mikegioia ,
I have one small question.
How can I setMonth() and setYear() without rendering ?
Thanks in advance.

@jaydeept4f The calls to setMonth() and setYear() both call render() from within them. There's no real way to do that unfortunately.


Inlining in jitted loop bodies

This PR enables script function inlining in jitted loop bodies.

Small changes in the stack walker to support this scenario.
Tweaks to inlining heuristics so that we don't inline as aggressively in loop bodies as we do in functions.

This change is

@LouisLaf please review
FYI, @pleath @abchatra

:shipit:


Hello, could you share your dataset? This download link is unuseful

Hello, could you share your dataset ?  I read this paper, the download link is unuseful, so your script can not download this dataset also. I need your help....thx a lot.....

Its working for me, I trained the model on google colab and ran the script there itself, even i dont have the dataset on local machine
ftp://smartengines.com/midv-500/dataset/
please check this link
If the problem stills exists, I will need to download all the dataset and share it with you on drive

I am also able to download the dataset in colab. But, i want it in my local machine. How can i download it? Can someone help me.

I am also able to download the dataset in colab. But, i want it in my local machine. How can i download it? Can someone help me.

It will be a quite long process...

Download the dataset in colab.
Link your google drive with colab.
Copy the dataset to your google drive.
Download the data from google drive.

How can i copy the dataset to drive. Can you share the command.

Or else, Is there any other way to get the dataset in my local machine?

How can i copy the dataset to drive. Can you share the command.

First mount the content of drive to colab
from google.colab import drive
drive.mount('/content/drive')

after running this code you will get a link, click on that link and sign in with your gmail account.
Now you get a authorization code, copy the code and place it in the input field of colab.
After this you can see the folder 'drive' in your file tab
then run the following command on each folder or you can write a script to do this.
!cp "folder_name" "drive/My Drive/path/to/save"

Hi, would you be able to update download_dataset.py to include the new ftp://smartengines.com/midv-500/extra/midv-2019/ dataset, including the unzipping > .npy automation.
I've tried by find/replace
ftp://smartengines.com/midv-500/dataset/
ftp://smartengines.com/midv-500/extra/midv-2019/dataset/
but it keeps failing after 1st .zip is downloaded and unzipped.
Thanks!

This url has a googledrive link if midv https://zhuanlan.zhihu.com/p/56336225

You can try this repo for automatic midv500 dataset download/unzip/coco format conversion operations on Linux and Windows:
https://github.com/fcakyon/midv500-to-coco

Its working for me, I trained the model on google colab and ran the script there itself, even i dont have the dataset on local machine
ftp://smartengines.com/midv-500/dataset/ please check this link If the problem stills exists, I will need to download all the dataset and share it with you on drive

Hi, I am unable to download the dataset. Could you share it on drive with me?

@phungo-hub you can use https://github.com/fcakyon/midv500 for easy midv500 download/unzip/coco format conversion!


Add context information when making signature help requests

This is the other half of https://github.com/Microsoft/vscode/issues/752

Is there any timeline on this? We could use this to fix some bugs in the Haxe extension / language server.

Duplicate of #54972


Feedback issue when Talk back is one in Accessibility Settings Google TV 4K for Media 1.4.1-alpha GitHub (Exoplayer) Wh

Version
Media3 main branch
More version details
Feedback for Media 1.4.1-alpha GitHub (Exoplayer)
Issue: Talkback incompatibility in media demo app on Google TV 4K Chromecast with collapsed categories
Steps to reproduce:

On Google TV 4K Chrome-cast, navigate to Settings > Accessibility.
Enable Talkback.
Launch the media demo app.
In the media.exolist.json file, collapse a main category.
Expand the collapsed category again.
Expected behavior:

Talkback should announce the expanded category and maintain the cursor's highlighted position within the channel list.
Observed behavior:
After expanding the category, Talkback loses track of the previously highlighted item, and the cursor position is reset.
Additional information:
The issue only occurs with Talkback enabled. Disabling Talkback allows collapsing and expanding categories without problems.
Developer mode within Talkback settings ([Settings > Accessibility > Talkback > Advanced]) can be used for debugging.
Impact:
This incompatibility hinders accessibility for users who rely on Talkback to navigate the media demo app.
Recommendation:
Investigate the cause of the cursor position being lost when expanding collapsed categories with Talkback enabled.
Implement a fix to ensure Talkback maintains focus and announces content changes appropriately.
Thank you,
Pooya M
Note:
I've replaced the bracketed text with a more descriptive explanation of the developer mode option.
I hope this formatted feedback is helpful for you to forward to the media 1.4.1-alpha GitHub repository.

Devices that reproduce the issue
Google TV 4K Chrome-cast (and also Android TV probably)
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
Steps to reproduce:
On Google TV 4K Chromecast, navigate to Settings > Accessibility.
Enable Talkback.
Launch the media demo app.
In the media.exolist.json file, collapse a main category.
Expand the collapsed category again.
Expected result
Talkback should announce the expanded category and maintain the cursor's highlighted position within the channel list.
Actual result
After expanding the category, Talkback loses track of the previously highlighted item, and the cursor position is reset.
Media
Media 1.4.1-alpha GitHub (Exoplayer)
Bug Report

[X] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

Thanks for reporting!
Is this problem specific to a TV device or can you repro the same on a mobile device?

After expanding the category, Talkback loses track of the previously highlighted item, and the cursor position is reset.

When trying this on a mobile phone with a Pixel 6 on Android 14 this seems to work. The selected and collapsed/expanded item is kept selected.
When I double tap the header of a category, it reads the category name and says that the category is collapsed. If I double tap it gives an audio feedback that the section is open. When (single) tapping on the item again it announces that it is expanded. So it looks like Talkback is aware of the state of the UI.

Talkback should announce the expanded category and maintain the cursor's highlighted position within the channel list.

As mentioned above, for what I see Talkback is aware of the UI state and I'd assume that it reacts in a standard way that Talkback users are used to.
How did you come to the conclusion that Talkback is expected to announce the expanded category any further than it currently does? Can you give us a hint how to enhance the UI element to work like you describe?
For now I think that the UI/Talkback integration works in a standard way. Or can you give us an example app that has such a UI element that behaves as you expect. If you can educate us that way we would be happy to change this accordingly.


Pullout bug

First, Thank you for your help.
It has been helpful to you using your project.
By the way I find a bug.
When I choose pullout mode, Leaving a space on the back of the list .
I found out that SwipeLayout.java/layoutPullOut() have a problem.
But your library operate well, I tried it decompile.
====
void layoutPullOut() {
// origin code
View surfaceView = getSurfaceView();
Rect surfaceRect = mViewBoundCache.get(surfaceView);
if (surfaceRect == null) surfaceRect = computeSurfaceLayoutArea(false);
if (surfaceView != null) {
surfaceView.layout(surfaceRect.left, surfaceRect.top, surfaceRect.right, surfaceRect.bottom);
bringChildToFront(surfaceView);
}
View currentBottomView = getCurrentBottomView();
Rect bottomViewRect = mViewBoundCache.get(currentBottomView);
if (bottomViewRect == null)
bottomViewRect = computeBottomLayoutAreaViaSurface(ShowMode.PullOut, surfaceRect);
if (currentBottomView != null) {
currentBottomView.layout(bottomViewRect.left, bottomViewRect.top, bottomViewRect.right, bottomViewRect.bottom);
}
}
void layoutPullOut() {
    // decompile code
    Rect rect = computeSurfaceLayoutArea(false);
    View surfaceView = getSurfaceView();
    if(surfaceView != null)
    {
        surfaceView.layout(rect.left, rect.top, rect.right, rect.bottom);
        bringChildToFront(surfaceView);
    }
    rect = computeBottomLayoutAreaViaSurface(ShowMode.PullOut, rect);
    View currentBottomView = getCurrentBottomView();
    if(currentBottomView != null)
        currentBottomView.layout(rect.left, rect.top, rect.right, rect.bottom);
}

====
Can I do merge request?
If not, please edit this code.
Many people use your code.

Thanks Kim. You solved my problem. I replaced the code with decompiled and works.

Your project is very nice. It is very helpful for me. Thank you again:)


add OSGi compatibility

Let's create a manifest, so that we can use the Chromecast API in an OSGi environment (e.g. in some IoT context).

Generally, it's ok. But I don't like changing of 'packaging'. Maybe it's worth to implement this as a submodule.

done

Merged. Thank you.


Consider discarding < 4 upper-bound on Requires-Python

See: https://github.com/astral-sh/uv/pull/4021#discussion_r1626581939

It's awkward but perhaps a pragmatic decision to treat >=3.7 as compatible with >=3.7,<4.

Thanks for opening a tracking issue.
Here's some relevant discussion:

https://github.com/python-poetry/poetry/issues/3747
https://github.com/pypa/packaging.python.org/pull/850
https://github.com/python-poetry/poetry/issues/8616

Probably more out there too.

It's awkward but perhaps a pragmatic decision to treat >=3.7 as compatible with >=3.7,<4.

Seems pretty reasonable until Python 4 is like... a real thing that might happen. If they switch to CalVer <4 is going to be a problem anyway :)

Haha. But if Python 4 is a thing, then users could set <4. I was more thinking we'd throw this out on declared metadata.

A broader thing you could do is ignore all upper bounds for Requires-Python. https://discuss.python.org/t/requires-python-upper-limits/12663 has much longer discussion but while standards say require python works for lower bounds, for upper bounds it's less clear.

Henry's comment there is interesting:

It really should have two settings, one for Requires-Python, and one for solving.

In Poetry, the published Requires-Python is coupled to the Requires-Python used for solving.

cc @henryiii :)

That suggests we shouldn't use Requires-Python but a separate setting for this hah.

Requires-Python can't be use for upper bounds. The field currently is used to back-solve, and backsolving is the wrong thing to do for an upper bounds. Libraries that have added an upper bound here (numba, numpy, etc) have had to remove it as it provides a worse experience to have the solver just permanently install a really old and broken package instead of the latest broken package. :)
https://iscinumpy.dev/post/bound-version-constraints/ talks about it some, and I've proposed some solutions in https://discuss.python.org/t/requires-python-upper-limits/12663 - though it got a bit stuck because packaging.tags should have a way to compute unions on SpecifierSets to help libraries detect an upper bound reliably, and I don't think we fully settled on a preferred solution.

What would you suggest we do? We can compute unions on specifier sets.

For now, ignoring <4 when making a lock file is safe. IMO ignoring upper bounds when making a lock file is safe, as you can't guarantee the upper solution is in fact compatible regardless (for example, https://pypi.org/project/rembg/#data says <3.13 but it's because a dependency states that, and poetry forces them to too. But when the dependency updates, that fixes the package depending on it, a package should state what they support!), but it's not as surprising to respect it as it is to respect <4.
If you want to have a lock file range, you can default to requires-python, but make sure there's a way to specify it without affecting the public metadata, please!

this has come up a few times in poetry, I think https://github.com/python-poetry/poetry/issues/6884 contains the most useful discussion.  fwiw I continue to hold the view that I expressed there: that it would be better to get the rules changed - presumably by an updated PEP - than to have solvers guess that folk meant something different than what they wrote.
Incidentally re

for example, https://pypi.org/project/rembg/#data says <3.13 but it's because a dependency states that, and poetry forces them to too.

While I think it's true that poetry's choice to default requires-python as capped has proved somewhat infectious, this particular project is a very curious example to choose to make that point - as rembg does not use poetry.

Poetry would force this though, and it's just the most recent thing I'd seen with the cap.
Currently, no one knowns what Python 4 will be like, other than it will be "less disruptive" than Python 3, and that it will come after 3.33. So I think it's perfectly fine to ignore "<4" as it only purely incorrect for anyone to use it now. Certainly don't make it infectious.
This Python limit is special, though, unless you can also solve for the Python version, which Poetry, PDM, etc. can't do. If you can't ever fix a solve by using this, what is the point of potentially breaking working solves?
And in general, if any solver starts going back to older versions of a package with an upper cap (which they all do), they not going to arrive a better solve with an older package just because they find one without a cap.
I feel most solvers go for mathematical correctness here when practically backsolving is only useful for lower bounds, and is at best expensive (for perfect metadata) and at worst wrong (for un-editable metadata).
Do keep in mind, though, I work on a total of 0 solvers. :)

Poetry would force this though, and it's just the most recent thing I'd seen with the cap.

sure, it's not that you're wrong about poetry - but you are wrong to assume that everything is poetry's fault!
I agree that most solvers go for correctness, I agree that it's plausible that if the folk writing the spec had understood the consequences of that then they might have written it differently.  But perhaps we disagree about the right resolution to that:

you're willing to just ignore the part of the rules that you don't like
I say: if the spec is wrong then first get the spec fixed

if everyone agrees that the spec is wrong then that should be easy, if not then perhaps it shouldn't be done...

Maybe it would be interesting to have a solver take the other path and see what happens.

This Python limit is special, though, unless you can also solve for the Python version, which Poetry, PDM, etc. can't do.

What does this mean @henryiii?

assume that everything is poetry's fault!

Sorry, didn't mean everything is Poetry's fault! I'll settle for "almost everything". :P
Poetry and PDM solve for a range - that's why this is infectious. Say you have one dependency: numpy. But this is during the few weeks where they had >=3.9,<3.13. Now Poetry will force you to set your Requires-Python to >=3.9,<3.13 (or narrower), since it can't find a lockfile that will be declared to support 3.13. However, as a python library, that's wrong, since your library just depends on numpy, and when numpy updates for 3.13 (or drops this silly cap, which they did), then your library now supports Python 3.13. It's only your lockfile that doesn't. So yes, you need to update your lockfile, but you shouldn't have to update your metadata and make a new release of your library, because you should't have been forced to modify your library metadata in the first place.

if the spec is wrong then first get the spec fixed

What would you suggest fixing? I have three options, I don't think we ever picked one though. And IMO it's still pretty squarely on the solvers to fix; an official statement that the upper bound is ignored or disallowed would help, of course. If I don't wan't to put a limit on my usage of Python, a solver should not force me to because my dependency does. I'm fine if it forces me to acknowledge that with tool.something, but not my project metadata.

What does this mean

Just that numpy<2 is not the same as requires-python<3.11. You can select numpy<2, but you can't pick the Python you are running on (in the mentioned tools). So a limit only serves to either cause backsolving on packages to look for a higher or missing upper cap (which is wrong for an upper limit) or to cause the solve to error, which turns a non-zero chance of failure into a guaranteed failure. The NumPy cap might cause a working solve by selecting an older NumPy. If a tool does solve for Python, like conda does, then it is much more like a normal package cap, and could cause a working solve by lowering Python rather than backsolving for older libraries without caps.
Conda lockfiles have a pinned version of Python. Poetry, PDM, etc. have a range of Pythons.
(TL;DR: the solution here may be affected by uv's Python installation plans ;) )

Regarding updating Requires-Python to be narrower than your dependents see https://github.com/astral-sh/uv/issues/4071 which proposes only narrowing the lockfile value and #4021 where we require users to narrow the pyproject.toml value. I find narrowing just the lockfile relatively compelling.
I'm also quite intrigued by the idea of "solving" for Python versions but haven't fully grasped what that would look like in practice.

What would you suggest fixing?

depends what exactly you think is broken!  eg I think I have seen you assert that requires-python was never intended / should not be used for upper bounds at all (apologies if this is misrepresenting you, or you now think something different).  In that case, one might propose something like: introduce min-python, deprecate requires-python.

If I don't wan't to put a limit on my usage of Python, a solver should not force me to because my dependency does

While related, I think this is a separate question from whether or not upper bounds and consequent backsolving were a good idea.  eg per zanieb the published range and the locked range do not have to be identical, this is something that could - at least in principle - be addressed today without changes to specs.

Yes, I said both, though the former is not correct, the designers assumed it could be used for anything, it just turned out that it doesn't "just work" when you design solvers. Adding a cap (remember when it was designed nothing had it, so it was always "added") just causes backsolving to before the cap existed.
requires-python originally supported dropping Python 3.x versions while keeping 2.7, which is why it needed to be a specifier set. Changing it to a new field would be a monumental task compared to just disallowing an upper cap. And if there was a situation like that in the future, it could also be determintal to handicap ourselves now. I have three suggestions in the linked Python discussion, but I don't think the churn of replacing the whole thing is acceptable.

But anyway, I am curious to see what's chosen here, and eventually will try to restart the Python discussions.

I find narrowing just the lockfile relatively compelling.

I think there's something to this but it doesn't quite work as-is. We include your own project in the lockfile, so that sets an upper limit on the Requires-Python that we could infer -- like, it can't get any wider than your own project's requirement.

But anyway, I am curious to see what's chosen here, and eventually will try to restart the Python discussions.

My guess right now is that we'll ignore upper bounds on declared Requires-Python from dependencies.

I'm also quite intrigued by the idea of "solving" for Python versions but haven't fully grasped what that would look like in practice.

This I take to mean treat python as another dependency and install it. uv pip install python==3.11 for example. And that user could specify,
python>=3.10
numpy>=1.24
...

and then treat requires-python same as adding a dependency constraint on python itself and be able to install/upgrade/downgrade python like any other library. That's what makes conda special. Conda can install python packages, but it can also install non-python packages and even interpreter itself.

👍 Yeah, "solving" for Python would mean you end up solving for a specific Python version (as opposed to solving for a range, I guess).

I wonder whether it would be good to emit a warning if the ignored upper bound is a bit unusual, i.e. anything other than <4.


Regenerate ToC

Using https://github.com/jonschlinkert/markdown-toc
markdown-toc -i --maxdepth 3 --bullets='-'  README.md
This is merely a proposition because I saw it was out of date and incomplete ("chapter" 9 was missing completely) and wanted to find a method that can semi-automate the job for you. No worries if you'd rather do it manually, then I'll apply the changes you want. Or just close this PR if you don't want it.

Thanks Anton. It's a good idea to automate the ToC, because it can be a pain to maintain.
This doesn't change any URLs, right? I often reference specific parts of the ToC from a StackOverflow answers.
Otherwise, I'm kind of ambivalent about this. I wish it didn't include the sections at the end like "Inspirations", but I can live with it.

This doesn't change any URLs, right? I often reference specific parts of the ToC from a StackOverflow answers.

I think it doesn't as long as the headlines stay the same. Once you want something like [Foo](#bar) where the #anchor is not the same as the headline, automation becomes a problem.
For this I'd recommend using either a specific revision, tag or branch to link to, so they kinda stay the same, for example for 7.1.3 https://github.com/airblade/paper_trail/blob/v7.1.3/README.md#5-activerecord, which might not exist in, i.e. paper_trail 10.
That way links should stay valid and relevant to the SO answer.

Otherwise, I'm kind of ambivalent about this. I wish it didn't include the sections at the end like "Inspirations", but I can live with it.

Yeah, I can understand that. But I was actually looking for the Problems part in the ToC, didn't find it and thus led me to open this PR, heh.

This doesn't change any URLs, right?

I think it doesn't as long as the headlines stay the same.

Cool, then I'm fine with merging this.

For this I'd recommend using either a specific revision, tag or branch to link to ..

Good point, I'll try to remember that for future SO answers.
Thanks for your continued contributions to PT!


Update VGS iOS documentation

Looks like the iOS documentation is not updated.
I did everything mentioned in the document but still some how it wasn't showing the card number nor the expiry date later I figured out that content path mentioned in documentation was the reason it was't working I had to change the path and it worked.
As per the documentation
cardNumberLabel.contentPath = "cardData.cardNumber" // didn't work not showing any data
expDateLabel.contentPath = "cardData.expDate" // didn't work not showing any data

Instead I had to change path to this.
cardNumberLabel.contentPath = "id" // working
expDateLabel.contentPath = ""expiry_mm_yyyy"" //  working

Thanks

Hello @anas-iqbal
Thank you for reaching us out and sorry for the confusion.
contentPath is not supposed to be hardcoded property just for card data, it depends on your setup and use case, contentPath works as an identifier for reveal operations on inbound routes.


Review Mod register(), startup(), shutdown() and unregister() behavior

There are some timing and behavior issues with the four Mod methods register(), startup(), shutdown() and unregister(). Current practice is that resources are registered and unregistered in the register() and unregister() methods. However, when enabling and disabling a Mod from the product page, only startup() and shutdown() are called, which leaves resources in an unexpected state. Consider removing startup() and shutdown() in deference to register() and unregister() or move resource registration and unregistration to startup() and shutdown() and call as needed before restoring the UI at program start.

Chose to move resource registration and unregistration to startup() and shutdown() and call as needed before restoring the UI at program start.


Fix deprecation in code climate config

See https://docs.codeclimate.com/docs/advanced-configuration#section-analysis-configuration-versions

LGTM


add pre-commit hooks

https://dev.to/haydenbleasel/adding-a-basic-pre-commit-check-to-a-next-js-app-a96 This may be a decent article to add pre-commit hook for

@mjubilee1 this works most of the way. Basically if it fails your commit and you fix the eslint error... make sure you rerun git add . before attempting to commit again. Or it will pass the linter b/c you fixed it but push up the old commit that was failing.


fix: ImageCard caption sizes

Pull Request Test Coverage Report for Build 466208587

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 74.136%

Totals

Change from base Build 463112087:
0.04%

Covered Lines:
1665

Relevant Lines:
2049

💛  - Coveralls

Pull Request Test Coverage Report for Build 466208587

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 74.136%

Totals

Change from base Build 463112087:
0.04%

Covered Lines:
1665

Relevant Lines:
2049

💛  - Coveralls


Replace all the *Repeated nonsense with a one-liner

Instead of having the whole *Repeated nonsense, if you want different hashes for otherwise identical proposals, you can just append a different timelock.salt(x) call to each proposal.

Just removed the lot and left a simple message.


Host function generic_hash() with blake2b/blake3 support.

In order to support Zero Knowledge software, cryptography related utils should be implemented as a host functions, otherwise execution cost would be too unacceptable. For example running Risc0 VM proof verification for simple sum of squares takes more than 6000 CSPR. The underlying hash used: sha256.
This PR adds host function called generic_hash(input, type) with support for the following types:

HashAlgoType::Blake2b - used existing blake2b implementation,
HashAlgoType::Blake3b - blake3 library was introduced.

We expect to add more algorithms, i.e. sha256, keccak, poseidon.
Example usage
Smart contract:
#![no_std]
#![no_main]

extern crate alloc;

use alloc::format;
use casper_contract::contract_api::{crypto, runtime};
use casper_types::HashAlgoType;

#[no_mangle]
pub extern "C" fn call() {
    let input = "casper".as_bytes();
    runtime::print(&format!("Input: {:?}", input));

    let blake2b = crypto::generic_hash(input, HashAlgoType::Blake2b);
    runtime::print(&format!("Blake2b hash: {:?}", blake2b));

    let blake3 = crypto::generic_hash(input, HashAlgoType::Blake3);
    runtime::print(&format!("Blake3 hash: {:?}", blake3));
}

Node output:
Input: [99, 97, 115, 112, 101, 114]
Blake2b hash: [163, 40, 63, 203, 149, 170, 125, 252, 231, 127, 90, 198, 44, 250, 234, 42, 1, 199, 20, 158, 150, 188, 25, 205, 21, 106, 255, 40, 204, 65, 45, 196]
Blake3 hash: [122, 158, 116, 51, 175, 213, 20, 50, 237, 63, 251, 230, 53, 2, 233, 86, 36, 159, 195, 109, 254, 108, 189, 210, 233, 1, 93, 219, 226, 1, 50, 217]

Considerations
1. AssemblyScript support
Is AssemblyScript binding required? I am pretty sure no one uses it.
Update: AssemblyScript is broken since a long time. I see no reason to include bindings for something that does not work.
2. Gas cost
For now, I used the same cost for generic_hash() as defined for blake2() - default fixed value 200. I can do benchmarks for WASM bytecode execution, but is there any conversion ratio between CPU time and execution cost?
Update: There will be new execution engine that will affect (lower) gas usage. It will be the better to make benchmarks then.
3. Place for core hashes implementation
Blake2b is implemented in types package, which does not seem to be reasonable. I added blake3 to new module crypto in execution engine, but I am open to discussing its location.
4. Single vs multiple host function
Do we want to introduce separate host functions for each hash algorithm?
5. Place for generic_hash() in contract API
I was thinking of using runtime, but finally decided to create new crypto module.

I just confirmed that host function is still working correctly after all changes and fixes.

Michal's approval is sufficient for you to move forward with this at the functional level. As far as inclusion into 1.6, @marc-casperlabs is the principal engineer on that rel; I've had no direct involvement with it.

@mpapierski should this be repointed to feat-2.0 ?

@mpapierski should this be repointed to feat-2.0 ?

I talked to @asladeofgreen and @jonas089 and for now, there's no concrete use case for generic hash functions, but we can revisit this once we use it internally or externally from the community. My understanding is that this PR was done as part of research.

Related issue (created to take this forward) #4892


getTextSelection not working

Hi there!
Not sure what I might be doing wrong, but I installed the example and it seems like getTextSelection doesn't select anything. Any help would be appreciated.
https://user-images.githubusercontent.com/2568736/153981077-8f7597f6-7929-40e4-858f-d48852d47d25.mov

I am also getting this behaviour (macOS app 2.1.6), getTextSelection succeeds but returns the empty string.
const selection = async () => {
	const response = await craft.editorApi.getTextSelection();
	if (response.status !== "success") throw new Error(response.message);

	let selectedText = response.data;
	if (selectedText.length === 0) selectedText = "Text selection is of len 0.";

	const block = craft.blockFactory.textBlock({
		content: selectedText
	});

	craft.dataApi.addBlocks([block]);
}

Consistently creates a block with Text selection is of len 0., regardless of I have text selected (which I would assume would give me the selected text) or if I don't have any selection (which apparently still flags success, kind of a strange API decision as a "success" implies something was selected and fetched).
I wanted to build a small capitalisation utility, but I don't see how you can do that without getTextSelection.


Mixed content warning when overview page is served over HTTPS

django-request always uses an HTTP URL for Google Charts, which leads to the browser marking the page as insecure due to mixed content.
Fixing this ought to be a simple as changing
'http://chart.apis.google.com/chart?cht=p3&chd=t:%s&chs=%sx%s&chl=%s'
to
'//chart.apis.google.com/chart?cht=p3&chd=t:%s&chs=%sx%s&chl=%s'
in request_admin.py.
However, the google.com certificate doesn't include that sub-domain. To get around that, you can use the following instead:
'//chart.googleapis.com/chart?cht=p3&chd=t:%s&chs=%sx%s&chl=%s'

@dwdyer I fixed your issue with PR #98 .
Can you try ?


Refactor ZHA

Refactor the core of ZHA so that it can be extended without causing issues with things like circular imports.
This PR:

splits the helper functions out into their own file
splits the entities into their own files
corrects a situation where zha_const.populate_data() was called for every device initialization

I think we need to update .coveragerc with the new files.

I think we need to update .coveragerc with the new files.

@MartinHjelmare I’m out with family for a while. I can do it when I get home or you can do it if you don’t want to wait.

Thanks for the assist @MartinHjelmare!


Ember server: Empty shutdown timeout causes "connection reset by peer" on all requests

Expectation: withShutdownTimeout(0) is only used when the server is shutting down
Reality: the value of 0 seems to have a special effect in which all client requests get rejected.
To reproduce, start the Server app here (scala-cli):
//> using scala "2.13.10"
//> using lib "org.typelevel::cats-effect:3.3.4"
//> using lib "org.http4s::http4s-ember-server:0.23.16"
//> using lib "org.http4s::http4s-ember-client:0.23.16"
import cats.effect.IOApp
import cats.effect.IO
import cats.effect.std.Console
import com.comcast.ip4s._
import org.http4s.ember.server.EmberServerBuilder
import org.http4s.HttpApp
import org.http4s.ember.client.EmberClientBuilder
import org.http4s.client.dsl.io._
import org.http4s.Method
import org.http4s.implicits._
import scala.concurrent.duration.Duration

object Server extends IOApp.Simple {

  def run: IO[Unit] =
    EmberServerBuilder
      .default[IO]
      .withHttpApp(HttpApp.notFound)
      .withPort(port"4000")
      .withHost(host"<IP_ADDRESS>")
      .withShutdownTimeout(Duration.Zero)
      .build
      .useForever

}

object Client extends IOApp.Simple {

  def run: IO[Unit] = EmberClientBuilder
    .default[IO]
    .build
    .use { client =>
      client.run(Method.GET.apply(uri"http://localhost:4000")).use(_.bodyText.compile.string)
    }
    .flatMap(IO.println(_))

}

For clients, you can use anything (curl, httpie, the Client app above all surface the issue).

I got as far as Shutdown.immediateShutdown which seems to very much be a special case, but I didn't dig deeper.


Issue1319 add block sig part4

This just adds the Schnorr multi signing of the blocks but without block validation requiring it yet. Part of Issue #1319

Think I addressed all comments.


Stuck at - rails g rails_admin:install

When i type in rails g rails_admin:install in git and after it ask me this it gets stuck.
I just press enter.

What is the reason?

Dup of #2334.


Change file import suggestion fail

When I change import or file name whatever from search bar. The suggestion appear woud you like to change file import etc.
and its turn the fallow line
import React, { Component } from '../../../../../../../Library/Caches/typescript/2.9/node_modules/@types/react';
normal form as fallow
import React, { Component } from 'react';

Duplicate of #53597
Fixed in VS Code insiders and if you upgrade to to use TypeScript 3.0 in your workspace (or downgrade to use TS 2.9.1)


The number of “Organs” in the Census with >= 70 donors is increased by 10 organs to 16 organs total

Data acquisition in collaboration with other members of SCB are finalizing a "Tissue General" list that will act as our roadmap to comprehensive tissue coverage:
-At current this list has 83 tissues.
-7 of these tissues already meet the > 70 donor criteria
-In H2 we are targeting 10 more tissues to meet the > 70 donor criteria

After evaluation of available data for the top ten tissue targets, i.e., those closest to the 70 threshold, the target of 10 is looking beyond reach for this half. I currently estimate we can cross the threshold for 5-6.

Missed this particular target. Will reopen for H1


improve the spacing between the cards in home page

hey , Please Assign This Task to me.

hey, can I take this up?

according to fcfs assigning this issue to @Mustafa-Azad025
@DugarRishab you can look at other issues

Will This Contribution Adds In Hacktoberfest 2022

If you give the pr after 1st oct then it will count

Ok So I Will Raise PR Again By Adding Screenshot Of The Changes .

Hey @akshitagupta15june ,
I have raised PR please merge it.

hey @akshitagupta15june ,
please approved this as a quality contribution for hacktober fest.

I already did merge it

Ok but i haven't receive any message from hacktoberfest as approved.
For earlier contribution I received message that why i am asking

You will not receive notifications on Every contribution
Only in first and fourth pr

Oh ok 😊


[Bug] [data develop] when task submit fail, the state is running

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
when task submit fail, the state is runing, and always running, can not stop and resubmit
and return error the cluster is not exists
What you expected to happen
1、submit fail, state should be stop
2、cluster not exists, set state to stop
How to reproduce
when task submit fail, the state is runing, and always running, can not stop and resubmit
and return error the cluster is not exists
Anything else
No response
Version
0.6.4
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

1.0 has solved


Need to rationalise the names of the Input and Field classes

As of today:
InputField is not an Input and is not a FormField. It contains a RawInput.
InputContainer is not an Input and is not a Container.
Input builds an InputContainer containing an InputField.
InputFormField extends FormField and builds an Input.
This is very confusing. We should rationalise these names.
See also https://github.com/flutter/flutter/issues/7017 about documenting all this better.
cc @HansMuller, @mpcomplete, @abarth

Also, per https://github.com/flutter/flutter/pull/6733#discussion_r86873884, in the Material spec and in many GUI toolkits, Input is called TextField.

Proposal:
Input => TextField (to match Material spec)
InputContainer => TextFieldDecorator
InputField => TextFieldEditable
InputFormField => TextFormField
Let's decide on this soon. The longer we wait, the more people we will break.

InputContainer/TextFieldDecorator isn't just about Inputs/TextFields. How about something like ControlLabel or something for that one?
Form uses FormFields. TextField and FormField sound like they'd be related, but aren't in this model.
I like that today InputFormField is a FormField.
I do like the TextField name, that makes sense to me. We could find another term for FormField, maybe FormControl? then you can have TextFieldControl for the version of TextField that is a Control. Or TextFieldFormControl but that's a bit long.
RawInput could be RawTextField. Today's InputField is between TextField and RawInput, maybe PlainTextField? But that suggests it's a "plain-text field", as opposed to a "plain text-field". Maybe UndecoratedTextField?
What does TextField add? Could we drop it and require that people either use TextFieldControl or ControlLabel+PlainTextField? In which case we could rename that latter one to just TextField? But then it's weird that TextFieldControl does more than just add the FormControl to the TextField, it also adds the ControlLabel...
In general, if Foo is a class, then BarFoo should be a subclass of Foo that adds bar-related functionality, and FooBaz should be a helper class for Foos that handles baz-related logic.

I like UndecoratedTextField. It's the most accurate description. I suspect most people won't use it anyway.
TextField is the Material-spec implementation and should be most common, so I think we should keep that.
I also like the Foo => BarFoo naming convention. I was trying to avoid the repetition of "Field", but maybe that's not worth it.
Something about "FormControl" seems wrong to me. Maybe it's just me.
New proposal:
RawInput => RawTextField
Input => TextField
InputContainer => TextFieldDecorator
InputField => UndecoratedTextField
InputFormField => TextFieldFormField or TextFieldFormControl (these options are my least favorite)

InputContainer is for any kind of form control, right? Not just text fields.
In general I would avoid a name FooBar if both Foo and Bar are classes because that's confusing (is it a subclass of Bar, or a utility class for Foo?).

RawTextField/UndecoratedTextField/TextField seems good to me.
I think we should broaden the scope of renames to include Form, FormField, and FormState (which by the way has no documentation). (Not saying we need to rename all of these, just that including them in the list is good for noticing if your names are consistent.)

Oops you're right, I glossed over InputContainer for some reason. That one's hard to name, because it's such a weird grab bag of stuff. WidgetThatAddsSomeTextFieldLikeDecorationsToChild would be accurate...

Maybe InputFieldDecorator or something like that?

Here's a slate:

Form
FormState
FormAssociatedWidget
RawEditableText
EditableText
InputFieldDecorator
TextField
TextFormField

What is FormAssociatedWidget?

Yes.  It's a base class for other widgets, which with tend to name either with a "Widget" suffix (e.g., AnimatedWidget) or with an "able" suffix (e.g., Pageable).

One thing is that EditableText is material-specific (it uses material UI for its popup menu). It's weird that we'd have a RawEditableText in widgets/ an EditableText + TextField in material/. I think Matt's UndecoratedTextField/TextField might be better.

Ah, I missed that UndecoratedTextField was material-specific.  It's usually a bad pattern to name something after what it isn't.  Maybe RawTextField?

FormAssociatedWidget is a mouthful. It's not just a base class. It ends up getting used for most other widgets that are more complicated than Input. (e.g. for sliders, you may want to use the field value as part of the label and maybe the color, like the expansion panels demo does, so you can't use a premade widget).

New slate:

Form

FormState

FormField

RawTextInput

TextInput

TextField

InputDecorator

(In this slate, Input disappears an becomes an implementation detail of TextField)

TextField has one limitation (though it's easily addressed). We don't expose the onChanged handler, so you can't respond to each individual keypress (e.g. if you want to update an autocomplete search field). This is https://github.com/flutter/flutter/issues/7210

InputFormField (proposed TextField) now has feature parity with Input, so we could merge the two.

New slate from latest in-person discussion:

Form
FormState
FormField
EditableText (the widgets version)
MaterialEditableText (the material version)
TextField (same as old InputFormField, which Input is now an impl detail of)
InputDecorator

SGTM. Let's do it.

So many merges! Did we address this, or more to come?

More to come. :-(

This issue is going to slip unto next quarter.

New proposal:

Form
FormState
FormField
EditableText (the widgets version)
TextField

all-sing, all-dance text field control
input decoration is optional, but enabled by default
not a form field

TextFormField

All the dancing and singing of TextField but also a FormField

InputDecorator

Also, InputDecoration, which bundles up all the consty parameters to InputDecorator to make them easier to deal with.

SGTM


Support for admin popup windows

@jsocol can you check this?

I haven't had a problem with pop-ups and adminplus. Can you give a little more details about what the problem is? Affected Django versions? Maybe a screenshot of the unpatched and patched versions?

this patch hides breadcrumb when is_popup is True, lick it's done in django, see https://github.com/django/django/blob/master/django/contrib/admin/templates/admin/base.html#L20-L60

I'd love to see a screenshot of the change, because in that template, the entire breadcrumb block is already inside a if not_popup block: https://github.com/django/django/blob/master/django/contrib/admin/templates/admin/base.html#L54-L59


Fix goreportcard errors

Happy to do this work in the next month or so.
Reference: https://goreportcard.com/report/github.com/vbatts/tar-split
I have a pretty cool script for this, icecrime/poule is using it now too:
https://github.com/box-builder/box/blob/master/checks.sh
This could be added to your test suite to ensure it doesn't go down again. It will put the report card at 100% when it passes.
Since the gocyclo & golint errors in particular will probably require some refactors, if you're willing to accept this request, we should probably discuss how the code should be reorganized first.
Hope this is useful, thanks.

Oh cool. That seems helpful for sure
On Tue, May 9, 2017, 00:12 Erik Hollensbe<EMAIL_ADDRESS>wrote:

Happy to do this work in the next month or so.
Reference: https://goreportcard.com/report/github.com/vbatts/tar-split
I have a pretty cool script for this, icecrime/poule is using it now too:
https://github.com/box-builder/box/blob/master/checks.sh
This could be added to your test suite to ensure it doesn't go down again.
It will put the report card at 100% when it passes.
Since the gocyclo & golint errors in particular will probably require some
refactors, if you're willing to accept this request, we should probably
discuss how the code should be reorganized first.
Hope this is useful, thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vbatts/tar-split/issues/39, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEF6Ua8bnjU1eKs4talRd07KMaM-0xXks5r3_WjgaJpZM4NU08T
.


Add build for arm6

Codecov Report

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

@@           Coverage Diff           @@
##           master     #101   +/-   ##
=======================================
  Coverage   78.19%   78.19%
=======================================
  Files          11       11
  Lines         642      642
=======================================
  Hits          502      502
  Misses         93       93
  Partials       47       47

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 0ce6344...3628813. Read the comment docs.


Audit policy metadata-only rule should include serviceaccounts/token resource

The following files reference a metadata-only audit policy in order to prevent logging request/response contents for sensitive resources:

https://github.com/cla-assistant/cla-assistant/blob/master/.actions/gardener/ansible-playbook/roles/gardener/defaults/audit_policy.yaml

A recent Kubernetes bugfix means that audit-logging of subresource requests which previously failed will now log successfully. The serviceaccounts/token subresource responds to TokenRequest API calls with a newly minted service account token.
The serviceaccounts/token resource should also be included in the metadata-only audit policy if credentials are not intended to appear in the audit log:
- group: "" # core
  resources: ["secrets", "configmaps", "serviceaccounts/token"]

Hi @liggitt,
thanks a lot for pointing that out.
We will in an iteration remove the whole kubernetes part of the project. So far as well only some staging services where running it. I'm going ahead and close this and again thanks for pointing this out.


Fix somes compilation warnings

I thought about the idea of moving TIMEOUT_IN_MS and other definitions to rmw/rmw.h, but noticed that it is not always equal to 1000. Also this way the value could be modified locally without affecting all files.

Thanks @acassis, let us review these changes, please don't remove your branch. We may take some time to review it.


"Content is not allowed in prolog." error in Azure DevOps when specifying an xml file

I have added an xml file to our source control and it looks like a legit xml file ot me, however the build fails because Dependency checker cannot parse the xml file. Here is the contents of the xml file:
<?xml version="1.0" encoding="UTF-8"?>
<suppressions xmlns="https://jeremylong.github.io/DependencyCheck/dependency-suppression.1.3.xsd">
   <suppress>
      <notes><![CDATA[
      file name: Microsoft.VisualStudio.Web.CodeGeneration.Design:2.2.4
      ]]></notes>
      <packageUrl<EMAIL_ADDRESS>      <cpe>cpe:/a:microsoft:visual_studio_code</cpe>
   </suppress>
</suppressions>

I have tried to parse the file with and without the xml tag in the first line but I get the same error both the times. Please help!

For anyone else who comes across this, if you are using Visual Studio to create an xml, then the default encoding is utf-8-BOM. I had to open the file in Notepad++ and change the encoding to utf-8. Once I checked it in, the dependency checker task ran successfully.

Correct handling of the BOM was just implemented for both reading the suppression files and hint files. This will be included in the next release.


have an interactive fabric8:run mode?

something like:
$ mvn fabric8:run-interactive
....
deploying app foo
...
waiting for pod foo-1234 to be ready.....

pod foo-1234 is now ready!

Please press Ctrl-C to terminate the app!

log of pod is now tailed to the console....

....
[Ctrl-C pressed]
scaling down deployment foo.....
pods all terminated

so that to java developers it looks and feels like you just did mvn spring-boot:run and to stop it you just ctrl-C it.

@jstrachan, shall we also add option to fabric8:run to expose the service as well ?

FWIW its the fabric8:resource that does that. I've raised a separate issue for improving the UX of exposing services:  https://github.com/fabric8io/fabric8-maven-plugin/issues/341

I've been prefixing the log output with the pod name then using a colour to highlight the log coming from the pod.
I wonder if this is a bit too wide? Maybe we just use "Pod >" as the prefix and have the first line list the pod name?

I think this is a bit easier to grok, particularly on smaller screens:

Here's an example of pressing Ctrl-C which then undeploys the app:
I've made it the default; we can disable the deleteOnExit via -Dfabric8.deleteOnExit=false

all sorted! we've mvn fabric8:log too for similar stuff when folks use mvn fabric8:deploy


Solving "Access Violation" on Linux

Bug
Northstar not launching properly with standard proton
Steps to reproduce

Be on linux
Start Northstar Titanfall with proton
Errors like 'Acces Violation' or crashes or other...

Specifications

Northstar version: 1.4
Platform: Origin/Steam/Linux

Solution
installing and using this proton fork Solves this problem and allows linux users to use this great Mod :)) I would be very thankful If you could add this information into the Linux part in the wiki.
https://github.com/GloriousEggroll/proton-ge-custom/

Oh, sorry, didnt know there was a page for the wiki. Thanks :3

Since you've found the solution can you add this to the Linux section of the wiki?

Done with #37