Error: Cannot find module 'express'

Installed on PI-1. getting the following error when running "node serveronly"
pi@raspberrypi:~/MagicMirror $ node serveronly
module.js:340
throw err;
^
Error: Cannot find module 'express'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/home/pi/MagicMirror/js/server.js:8:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

Sorry, Pi 1 is not supported.

Is there a basic version I can install...I have come a long way with
setting up all the hardware and to stop because I have the wrong version of
pi is sad....
Any work around??
On Jun 21, 2016 10:12 AM, "Michael Teeuw"<EMAIL_ADDRESS>wrote:

Closed #364 https://github.com/MichMich/MagicMirror/issues/364.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MichMich/MagicMirror/issues/364#event-699373548, or mute
the thread
https://github.com/notifications/unsubscribe/ATJDEhw9OX65Tw9U3k5s_AZzl5Zo3poKks5qOBtugaJpZM4I67sV
.

You might be able to find some workarounds on http://forum.magicmirror.builders - But unfortunately I can't give you any support.

just to confirm, I am using Raspberry Pi Model B 512MB RAM. can you confirm
is this not supported?
On Tue, Jun 21, 2016 at 10:16 AM, Michael Teeuw<EMAIL_ADDRESS>wrote:

You might be able to find some workarounds on
http://forum.magicmirror.builders - But unfortunately I can't give you
any support.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MichMich/MagicMirror/issues/364#issuecomment-227508743,
or mute the thread
https://github.com/notifications/unsubscribe/ATJDEovHL_EUyl8o6vjUu0aVlVnUW-8bks5qOByGgaJpZM4I67sV
.

--
Naveen Patlola
http://www.marchforbabies.org/march/personal_page.asp?w=6930219&u=naveenpatlola&bt=5

Exactly. Officially only the Pi 2 & 3 are supported.

Thank you for your assistance...
On Tue, Jun 21, 2016 at 11:16 AM, Michael Teeuw<EMAIL_ADDRESS>wrote:

Exactly. Officially only the Pi 2 & 3 are supported.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MichMich/MagicMirror/issues/364#issuecomment-227525883,
or mute the thread
https://github.com/notifications/unsubscribe/ATJDEseQqg0cn3Y7lRngGbhQgtb8YzTOks5qOCqRgaJpZM4I67sV
.

--
Naveen Patlola
http://www.marchforbabies.org/march/personal_page.asp?w=6930219&u=naveenpatlola&bt=5

Officially, Pi 1 supported. I was able to get it running on my Pi 1 though on serveronly. The challenge was getting the layout right in the browser. I've since had to reformat my RPi so I can't tell you much more but it is possible.
There's another thread discussing how to run on Pi1:
https://github.com/MichMich/MagicMirror/issues/354
I haven't gotten this method to work yet though

*is not supported. Sorry

Thank you for you help. I was able to build my own magic mirror...Additionally I add a sensor to control the monitor, which will save power and also not overheat the system...
much appreciated..attached are some pictures


Test fails

Test fails with a simple npm i && vows:
  ✗ Errored » Asynchronous Error
      in protocol imports
      in test/protocol-imports-test.js
✗ Errored » callback not fired
      in of a proxied resource
      in protocol imports
      in test/protocol-imports-test.js✗ Errored » 2822 honored ∙ 1 errored ∙ 3 dropped

Failure is not related to a test (same error without test/protocol-imports-test.js)
Environment

clean-css version - npm ls clean-css: 4.2.2
node.js version - node -v: v10.17.0
operating system: Linux

Test are OK using node.js ≥ 12

Looks good now


[Bug] Settings crashing

With the new unc0ver jailbreak, I was able to jailbreak my iPhone 11 14.2 and install secret shot. The issue once it is installed is, going to the tweak settings causes a crash to the home screen. Without being able to get to the setting you can’t enable the tweak.

I have this same issue, bump


NodeJS doesnt stop using port after killing process

The node process is killed but I see port 1337 (the currently configured port) still being used and it gives an error. The only current fix is to manually run sudo netstat -tulpn and kill the PID using the port.
I noticed that it only remains listening on the IPv6 interface...so maybe we should disabled IPv6? Or check to see the if the port is in use then kill the process using the port? (this could cause problems if the port was changed to something like 80 though)

After switching to babel I havent seen this error happen, so I will close it for now. Will reopen if this error happens again.


Hide controller manager and scheduler for AKS cluster

What kind of request is this (question/bug/enhancement/feature request):
enhancement
Due to an upstream bug in K8s, the AKS cluster shows the controller manager and scheduler unhealthy forever. But the AKS cluster still works without problems, so it will be great if we can hide those two items from UI.

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):  v2.0+

related issues:
https://github.com/rancher/rancher/issues/11496
https://github.com/Azure/AKS/issues/173

+1 for this issue

We will probably drop them soon

We don't need to hide, but maybe grey out so that at least it's not looking like a bug when it's just expected due to the AKS issues.

The bug fix is validated on Rancher: master 5d74988c
The Controller Manager and Scheduler are grayed out and no error messages showing in the UI anymore.

The bug fix is validated on Rancher: master 5d74988
The Controller Manager and Scheduler are grayed out and no error messages showing in the UI anymore.

@jiaqiluo , How to hide warnings and  gray out? Any steps or documentation available?

I'm running rancher on a linux host as docker container, latest version image, I'm still facing this issue after importing AKS cluster. Are you using some specific docker image where it was set to be grayed-out or what is your implementation?


Calling dir.getallfiles with no "pattern" returns an empty List

This bug was introduced today with the new 1.4.0 version. Not providing a pattern to dir.getallfiles results in the file mask ^$ being used, which looks for files whose name is empty-string (not all files regardless of name, like the doc implies.) This results in dir.getallfiles() returning an empty List instead of all of the files in the directory, as intended.

As this breaks busted, I think it's a good idea to release a bugfix version (1.4.1) as soon as possible. @stevedonovan what do you think? I'll update the changelog in the meantime. (and sorry for introducing this bug)

Cool, let's do that...


Add in classiclink properties to autoscaling configuration

Classic Link Properties

@stevenjack bump

@kornypoet sorry, I'll push it out this evening

Thanks


Keep an eye on alchemist-server/ElixirSense

I'm just opening this issue because the @mat-mcloughlin mention didn't work. @msaraiva plans to do a refactoring/rewrite of the alchemist-server and I think we should really keep an eye out for this.
Read more here

Tracked in #60


Image cannot open when cursor is 'release' outside preview image

looks like it becomes preview image of default obsidian when cursor is release outside preview image.
https://github.com/sissilab/obsidian-image-toolkit/assets/39915562/2487cb12-8ded-4439-b17d-350b99c68f75

looks like it becomes preview image of default obsidian when cursor is release outside preview image.
It seems influenced by your theme. So what's your theme?
If it really matters with your theme, you can try to close image zooming function of the theme  by Style Settings plugin.

looks like it becomes preview image of default obsidian when cursor is release outside preview image.

It seems influenced by your theme. So what's your theme? If it really matters with your theme, you can try to close image zooming function of the theme by Style Settings plugin.

Wow, it's really affect by theme.
I use Minimal theme, and it's works normally after I toggle the Disable image zoom via Style Settings plugin.
Thank you! @sissilab


Invalid UTF-8 character when lang is set to fr-FR

Hi,
I am writing a document in French using Pandoc to convert my markdown document to PDF.
As I am writing in French, I am using lang: fr-FR in the YAML header to have \usepackage[francais]{babel} in my rendered file.
However, it fails with the bibliography generated by pandoc-citeproc.
Indeed, in my bibliography, I have lines such as
	pages = {1169--1174},

(dash is standard ASCII dash)
and the dashes get somehow converted to UTF-8 dashes (U+2011), which gives the following error when compiling:
! Package inputenc Error: Unicode char ‑ (U+2011)
(inputenc)                not set up for use with LaTeX.

See the inputenc package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.1048 ... for the Advancement of Science: 1169‑

Try running pandoc with --latex-engine=xelatex.
pandoc: Error producing PDF

Thanks

pandoc-citeproc is cross-platform; it produces output that
should work with any format.  Keeping the -- as it
is would only work with LaTeX.
I suppose we could have the LaTeX writer escape the en-dash
as --, and similarly with quotes and em-dashes, but I'm
not sure everyone would want this behavior.  Why not just
use --latex-engine=xelatex as suggested?
+++ Lucas Verney [Apr 22 16 07:23 ]:

Hi,
I am writing a document in French using Pandoc to convert my markdown
document to PDF.
As I am writing in French, I am using lang: fr-FR in the YAML header to
have \usepackage[francais]{babel} in my rendered file.
However, it fails with the bibliography generated by pandoc-citeproc.
Indeed, in my bibliography, I have lines such as
pages = {1169--1174},
(dash is standard ASCII dash)
and the dashes get somehow converted to UTF-8 dashes (U+2011), which
gives the following error when compiling:
! Package inputenc Error: Unicode char ‑ (U+2011)
(inputenc)                not set up for use with LaTeX.
See the inputenc package documentation for explanation.
Type  H   for immediate help.
...
l.1048 ... for the Advancement of Science: 1169‑
Try running pandoc with --latex-engine=xelatex.
pandoc: Error producing PDF
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or [1]view it on GitHub
References

https://github.com/jgm/pandoc-citeproc/issues/223

Ok for the reason, still I think it would be better if pandoc-citeproc could be used with LaTeX directly, without having to switch to xelatex.
Concerning the suggestion about xelatex, I am using:
header-includes:
    - \usepackage{mathtools}

in the header of my markdown file, which gives:
! Package mathspec Error: `amsmath' must be loaded earlier than `mathspec'.

See the mathspec package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.116 \RequirePackage{amsmath}

When running Pandoc using xelatex on the file.
I removed the header line, and still got another issue later:
! Improper alphabetic constant.
<to be read again>
                   \varphi
l.971 ...ta \varphi_X^2 + \varphi_Y^2 + C" \varphi

I have no issues compiling the file if I use standard LaTeX engine and disable the pandoc-citeproc filter.
P.S.: My issues with xelatex may not be pandoc-related, but rather xelatex-specific. But this option is not as straightforward as the warning message might say in my case.

Pandoc doesn't normally use unicode curly quotes for Quoted
inlines.  The issue is that pandoc-citeproc does localization.  The
quotation mark style is affected by the locale.  Many of the
quote mark styles don't even have LaTeX ligatures defined,
so we really need to use unicode characters rather than
Quoted inlines.
I suppose one could change the pandoc Quoted type to take
a more fine grained parameter than SingleQuoted or
DoubleQuoted, with the specific open and close quote
characters given.  This might be helpful for other reasons,
too.  And then the LaTeX writer could produce ascii
ligatures when possible.
However, this would be a big change, since it affects
pandoc-types and requires changes in virtually every
module in the pandoc ecosystem.  As I say, it might be
worth making for other reasons (allowing localization
of quote styles, see #2620).  Perhaps another issue
should be opened about this.
+++ Lucas Verney [Apr 26 16 08:32 ]:

Ok for the reason, still I think it would be better if pandoc-citeproc
could be used with LaTeX directly, without having to switch to xelatex.
Concerning the suggestion about xelatex, I am using:
header-includes:

\usepackage{mathtools}

in the header of my markdown file, which gives:
! Package mathspec Error: amsmath' must be loaded earlier than mathspec'.
See the mathspec package documentation for explanation.
Type  H   for immediate help.
...
l.116 \RequirePackage{amsmath}
When running Pandoc using xelatex on the file.
I removed the header line, and still got another issue later:
! Improper alphabetic constant.

\varphi
l.971 ...ta \varphi_X^2 + \varphi_Y^2 + C" \varphi
I have no issues compiling the file if I use standard LaTeX engine and
disable the pandoc-citeproc filter.
P.S.: My issues with xelatex may not be pandoc-related, but rather
xelatex-specific. But this option is not as straightforward as the
warning message might say in my case.
—
You are receiving this because you commented.
Reply to this email directly or [1]view it on GitHub
References

https://github.com/jgm/pandoc-citeproc/issues/223#issuecomment-214784705

@jgm Ah, you mean the issue with xelatex is due to the C" text which is converted to C“ when using pandoc-citeproc, and which gives the issue because “ is not a valid constant name?
Is there an easy way to workaround at the moment?
Thanks!

No, you can see from the xelatex error message that the " is not made curly in the LaTeX source (pandoc wouldn't mess with quotes in math mode).  I wasn't giving you a solution to the xelatex issue, but see the last comment in http://tex.stackexchange.com/questions/64900/improper-alphabetic-constant which may help diagnose that.

Ok, thanks. I got it working with xelatex, after removing my mathtools include, this does not seem to be Pandoc-related.
I am not sure whether this issue should stay open as it would be better if we could compile such texts using the plain LaTeX engine. At least it is non blocking if switching to xelatex. Feel free to close if you think it should not be fixed. :)

By the way, I am just thinking about it, is there a specific reason for pandoc not to switch to xelatex engine automatically if available? I am tempted to do it in my own wrapper on top of pandoc, but fear to miss some major downside.

The main reason is that it's better (more efficient) for
people to find about the need to use xelatex and change
their build command, rather than having pandoc
unsuccessfully try pdflatex  every time they build
the document...
+++ Lucas Verney [May 01 16 11:50 ]:

By the way, I am just thinking about it, is there a specific reason for
pandoc not to switch to xelatex engine automatically if available? I am
tempted to do it in my own wrapper on top of pandoc, but fear to miss
some major downside.
—
You are receiving this because you were mentioned.
Reply to this email directly or [1]view it on GitHub
References

https://github.com/jgm/pandoc-citeproc/issues/223#issuecomment-216063775

OK, thanks! :)


Angular is deprecated - please migrate to React

Hello :wave: from Grafana Labs
We have detected that your plugin might still be using AngularJS and recommend migrating it to React, so that it may continue to operate successfully in future versions of Grafana.
You can read more on why and how by visiting our documentation: https://grafana.com/docs/grafana/latest/developers/angular_deprecation/
You can reach out to us with any questions via slack: slack.grafana.com - channel #plugins or our plugin development community forum

@tolzhabayev we submitted to grafana.com
new release, https://github.com/Altinity/clickhouse-grafana/releases/tag/v3.0.0
Which is not contained any angular dependencies, why grafana still show Angular warning for plugin?
Is the Angular mark is manual from Grafana Labs side?

@Slach can you specify which one of the messages you mean / where you see it? We have a lot of different places where we flag plugins as angular and some are based on code detection and some on fetching data from our APIs that have a list of plugin versions that we update.
Generally - great news and thank you for doing the work and migrating!

@tolzhabayev
just open my local plugin installation
http://localhost:3000/plugins/vertamedia-clickhouse-datasource
3.0.0 have no angular dependencies and created from scratch with React

@Slach it is interesting as I don't see this banner if I just checkout your latest master, build and run the npm run server

@tolzhabayev 3.0.0 was released yesterday, and now clickhouse-grafana altinity plugin just not marked as angular

awesome! thanks for doing the work


Issue: Create 'Version' Endpoint in Nachet Backend

Description
To ensure consistency and compatibility between our frontend and backend services, we need to implement a 'version' endpoint in the Nachet Backend. This endpoint will provide version information, including the application version, name, Git commit hash, and long Git version, similar to what is currently available in the Nachet frontend.
Requirements

The endpoint should be accessible via a simple GET request (e.g., /api/version).
It should return a JSON object containing:

applicationVersion: The current version of the application (from package.json).
applicationName: The name of the application (from package.json).
gitCommitHash: The short Git commit hash of the current deployment.
longGitVersion: A combined string of the application version and commit hash (e.g., 0.1.0-f0db6e8).

Purpose
This endpoint will allow the frontend to display the backend version information, ensuring that both frontend and backend are running compatible versions. It will be particularly useful for troubleshooting and verifying deployments.
Implementation Notes

The backend should dynamically retrieve version and Git information during runtime, rather than hardcoding these values.
Consider using build scripts or CI/CD pipelines to inject the Git commit hash and other relevant information into the backend environment.

Acceptance Criteria

A new endpoint /api/version is implemented in the Nachet Backend.
The endpoint returns accurate and up-to-date version information.
The frontend can successfully retrieve and display this information to verify compatibility with the backend.

also:
https://flask-rebar.readthedocs.io/en/latest/quickstart/api_versioning.html

@k-allagbe should comment on the design choices here

@k-allagbe should comment on the design choices here

I haven't explored the API versioning topic very well yet. My first reaction would be to use blueprints to implement versions. But maintaining features across the blueprints could become cumbersome.
I'm not too sure about flask_version. The last commit on it dates 2020 and it doesn't seem to be maintained by a lot of people.
I like the flask-rebar extension not only for the versioning, but also because it integrates swagger already.
Quick comparison: blueprints vs. flask-rebar
Blueprints
Pros:

Flexibility: Blueprints are highly flexible and seamlessly integrate with Flask.
Simplicity: Easy to set up for versioning, using version prefixes in URLs.
Organizational Clarity: Ideal for structuring large applications into distinct sections.

Cons:

Manual Management: Requires handling request validation, serialization, and documentation manually.
Less Feature-Rich for APIs: Blueprints alone don’t offer specific RESTful API development features like automatic schema validation or documentation.

Flask-Rebar
Pros:

Built for APIs: Specifically designed for RESTful API development, offering features like API versioning, marshalling, validation, and auto documentation (Swagger).
Schema Validation: Integrated request and response schema validation using Marshmallow.

Cons:

Additional Dependency: Introduces an external dependency to the project.
Less Flexibility in Routing: Might offer less flexibility than Blueprints for certain routing requirements.

My Opinion:
I'm not sure if flask-rebar works with quart. But if this backend will grow a lot, we should probably consider flask-rebar. Otherwise, blueprints can satisfy our needs for versioning for now.

@k-allagbe good review, thanks.
For now I'd lean towards the simpler solution, which is just using blueprints to give us time to carefully consider major changes such as switching .
This example demonstrates what we want I think:
https://gist.github.com/berend/fb8fd98be235aec7c6d12782805d7bff
My concern was mainly making sure that if version 1.1.0 is basically the same as version 1.2 except for a few, non-API breaking additions to the API that we are able to reuse these changes.
in the case of breaking changes (a major version bump, such as going from 1.2 to 2.0.0) we can clearly have label for the function that changes.
It is perhaps "cumbersome" but it may also be the cost of change management.


Allow build windows exe under linux

It would be great to build windows exe under linux

I believe this has been asked before, however this is impossible (to my knowledge). You'd need Visual Studio in order to do this and is really to much of a hassle. If there is a method of doing so for node, I could perhaps look into it, but until it won't be!
Thanks for the suggestion!

Maybe this is relevant : https://github.com/maxogden/electron-packager#building-windows-apps-from-non-windows-platforms
However I don't really know how it's done

Thank you, tried that but resulting file is too big :dancer:


BIE-V2支持纯粹的YAML

Codecov Report

Merging #469 (b9c1066) into master (2c43fa0) will increase coverage by 0.08%.
The diff coverage is 80.95%.

@@            Coverage Diff             @@
##           master     #469      +/-   ##
==========================================
+ Coverage   62.62%   62.70%   +0.08%
==========================================
  Files          92       92
  Lines        7614     7631      +17
==========================================
+ Hits         4768     4785      +17
+ Misses       2077     2076       -1
- Partials      769      770       +1

Impacted Files
Coverage Δ

api/yaml.go
53.93% <80.95%> (+0.56%)
:arrow_up:

api/config.go
85.25% <0.00%> (+2.56%)
:arrow_up:

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 2c43fa0...b9c1066. Read the comment docs.


[LIVY-688] Error message of BypassJobStatus should contains cause information of Exception

What changes were proposed in this pull request?
Change the implement of org.apache.livy.rsc.Utils.stackTraceAsString to guava Throwables.getStackTraceAsString, so that user can receive details of error message by calling org.apache.livy.client.http.JobHandleImpl.get.
https://issues.apache.org/jira/browse/LIVY-688

Codecov Report

Merging #237 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #237      +/-   ##
============================================
- Coverage     68.37%   68.34%   -0.03%
  Complexity      921      921
============================================
  Files           100      100
  Lines          5729     5724       -5
  Branches        871      870       -1
============================================
- Hits           3917     3912       -5
- Misses         1247     1248       +1
+ Partials        565      564       -1

Impacted Files
Coverage Δ
Complexity Δ

rsc/src/main/java/org/apache/livy/rsc/Utils.java
80.55% <100%> (-2.38%)
14 <1> (-1)

...ain/scala/org/apache/livy/utils/SparkYarnApp.scala
66.01% <0%> (-1.31%)
40% <0%> (ø)

...c/src/main/java/org/apache/livy/rsc/RSCClient.java
72.28% <0%> (-1.21%)
20% <0%> (ø)

...ain/java/org/apache/livy/rsc/driver/RSCDriver.java
79.23% <0%> (+1.27%)
42% <0%> (+1%)
:arrow_up:

...cala/org/apache/livy/scalaapi/ScalaJobHandle.scala
55.88% <0%> (+2.94%)
7% <0%> (ø)
:arrow_down:

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 b8251eb...1791e1c. Read the comment docs.


Online Updater for DoCM

@acoffman I pushed a commit to implement most of your suggested changes/fixes. See my comments above for the remaining suggestions.

 Finish DGIdb PRs


Understanding the "process is not defined" error

As I bumped a few times in this issue and did not find out a solution could you explain me how should I fix this.
Context
I am coding a LitElement based web application using es-dev-server to serve my app during development phase.
Here is my es-dev-server.config.js :
const proxy = require('koa-proxies')

module.exports = {
  port: 3000,
  hostname: "<IP_ADDRESS>",
  watch: true,
  nodeResolve: true,
  appIndex: './index.html',
  middlewares: [
    proxy('/api', {
      target: 'http://server:8000',
    })
  ],
  debug: true
}

I want to use (for example) the history package :
...
import { createBrowserHistory } from 'history'
...

What is happening
tiny-warning.esm.js:1 Uncaught (in promise) ReferenceError: process is not defined
    at tiny-warning.esm.js:1

What is expected
The history package is imported without issues and I can use it.
Also
I tried to import the history/esm/history.js file as the workaround is proposed in the open-wc website FAQ to fix redux import but I get the same error.
What do I miss ? Should I build my code before serving it ? Should I use babel to compile my code and if so what settings should I use ?

It's likely one of your dependencies is using process.environment, which doesn't exist in the browser.
I'd file an issue on the project, since they're publishing code that doesn't work.
You can probably hack it in your project by setting window.process = {} before you load your application. Other option is to use a responseTransformer and rewrite this piece of code in that project, that is essentially what build tools like webpack do.

@LarsDenBakker Thx !
I thought of that but wasn't sure as history is itself a dependency of redux-first-router which is recommended in open-wc website among other routers.

Fair point, we may not have checked if all the routers listed there work correctly with es-dev-server...

That's alright !
Still open-wc is very helpfull and you've done great work !
By the way history is not the only package that is not supported by es-dev-server :
query-string is using CommonJS syntax and does not provide es6 build

Es dev server just supports what the browser supports :)

Closing this, as there is no actionable item for us.


UploadedFileFactory - Failing to create a readable UploadedFile from string

While I was updating Mika Tuupola's tuupola/http-factory to support this package, I stumbled upon this bug. The tests won't pass for slim/psr7 as can be seen here https://github.com/tuupola/http-factory/pull/10, while they do pass for the other PSR-7 implementations.
I was trying to solve it for a couple of hours, but failed, so for now I'm just providing the failing test and a temporary comparison to nyholm/psr7 that does not fail.
The code of the test is taken from Interop\Http\Factory\UploadedFileFactoryTestCase (http-interop/http-factory-tests package).
I will try a bit later again, but I suspect the authors will have much better insight into the matter.

The problem might be, that the temp stream created, fails to be readable in \Slim\Psr7\Factory\UploadedFileFactory::createUploadedFile():
https://github.com/slimphp/Slim-Psr7/blob/6e3292963548c6a4c29402fc105b19a1edf6577b/src/Factory/UploadedFileFactory.php#L32
A var_dump() of the $stream variable right before that line mentioned above, gave the following:
class Slim\Psr7\Stream#8517 (7) {
  protected $stream =>
  resource(1089) of type (stream)
  protected $meta =>
  array(6) {
    'wrapper_type' =>
    string(3) "PHP"
    'stream_type' =>
    string(4) "TEMP"
    'mode' =>
    string(3) "w+b"
    'unread_bytes' =>
    int(0)
    'seekable' =>
    bool(true)
    'uri' =>
    string(10) "php://temp"
  }
  protected $readable =>
  NULL
  protected $writable =>
  NULL
  protected $seekable =>
  NULL
  protected $size =>
  NULL
  protected $isPipe =>
  NULL
}

While is_readable($file) returns false, $stream->isReadable() returns true.
@l0gicgate Do you have any idea why this happens?

I just changed https://github.com/slimphp/Slim-Psr7/blob/6e3292963548c6a4c29402fc105b19a1edf6577b/src/Factory/UploadedFileFactory.php#L32-L34
into
       if (!is_string($file)) {
            throw new InvalidArgumentException('File is not readable.');
        }

        if ($stream instanceof Stream) {
            if (!$stream->isReadable()) {
                throw new InvalidArgumentException('File is not readable.');
            }
        } elseif (!is_readable($file)) {
            throw new InvalidArgumentException('File is not readable.');
        }

See https://github.com/adriansuter/Slim-Psr7/commit/9c7f060dc444ddb8300dc59bed19d2a9cbbaad65
Now, the contents of the uploaded file seems to be empty.

In
https://github.com/slimphp/Slim-Psr7/blob/6e3292963548c6a4c29402fc105b19a1edf6577b/src/Factory/UploadedFileFactory.php#L40
we would actually pass php://temp as $file to the constructor.
But later on, in \Slim\Psr7\UploadedFile::getStream(), the stream would be recreated from the given file, which is php://temp:
https://github.com/slimphp/Slim-Psr7/blob/6e3292963548c6a4c29402fc105b19a1edf6577b/src/UploadedFile.php#L106
Maybe that's the issue?

Sorry, I forgot to provide those details: Yes, the file is not readable at the moment of the check, but even if you fix the check the stream content will be empty, that is what I found out. Anyway the same happens in the nyholm implementation (file is not readable in the constructor), but the stream content returns as expected. Tough I have not investigated further.

So I managed to fix this particular issue by allowing to create an instance of UploadedFile from a stream directly (no recreation of the stream). But this breaks the other tests, obviously, and is most probably a BC break.
The issue is this:
UploadedFileFactory will extract the filename of the stream, pass it down to the UploadedFile and then the UploadedFile recreates the stream when getStream method is invoked. This IMHO fails for temporary streams though:

php://memory and php://temp are not reusable, i.e. after the streams have been closed there is no way to refer to them again.

PHP php:// documentation, scroll to the bottom of the page

Exactly.

My opinion? I'd prefer to modify the UploadedFile::__construct as it is in this draft PR (that is, remove the type constraint from the $file argument) and possibly rename it to $fileOrStream, to keep the interface simple. This is IMHO much better than adding an optional $stream parameter, because then there would be confusion as to whether the filename comes from $file parameter or $stream->getMetadata('uri)... Or how to solve case where these two would not match.
P.S.: I was wrong with the BC break - the classes that extend UploadedFile and overload the constructor should keep working without problems even if the superclass's type constraint is removed (I tried with PHP 7.2 and 7.3).
The tests that this modification breaks are in fact only those that expect an exception being thrown:
1) Slim\Tests\Psr7\Factory\UploadedFileFactoryTest::testCreateUploadedFileWithInvalidUri
Failed asserting that exception of type "InvalidArgumentException" is thrown.
2) Slim\Tests\Psr7\Factory\UploadedFileFactoryTest::testCreateUploadedFileWithNonReadableFile
Failed asserting that exception of type "InvalidArgumentException" is thrown.
3) Slim\Tests\Psr7\Integration\UploadedFileTest::testGetSize
Failed asserting that 0 is null.

(except for the last one with file size, i'll investigate that one)
So if you're asking me, I'd go down this way and finish this PR, possibly altering the tests that expect the exception and/or move the "is readable" check elsewhere (e.g. to the getStream method).

Hi @dakujem
I agree. Probably we should use $fileOrStream or even $fileNameOrStream as variable name in the constructor.
Regarding the "get size" test case: It seems that the slim integration of \Http\Psr7Test\Tests\Slim\UploadedFileTest::createSubject() does not write the created temporary file to disk.
https://github.com/slimphp/Slim-Psr7/blob/6e3292963548c6a4c29402fc105b19a1edf6577b/tests/Integration/UploadedFileTest.php#L23-L28
I changed that in my branch addressing this subject https://github.com/adriansuter/Slim-Psr7/commit/c40aebf605ce4711b28456bb127f2d05ceea2478

@adriansuter Shoul I continue to solve this issue? I'd most probably need to update the tests so that they do not expect exception at the time of calling UploadedFileFactory::createUploadedFile (because of the postponed check).

@dakujem
You can if you like and if you have time.
Why do you postpone those checks? Couldn't we leave them in \Slim\Psr7\Factory\UploadedFileFactory::createUploadedFile()?
If you don't like to continue to work on this issue, I could PR my branch https://github.com/adriansuter/Slim-Psr7/tree/patch-uploaded-file-temp-stream instead

I can continue, I just was not sure you liked the changes... would not want to waste time.
For reason I have yet to discover, the "is readable" check will always fail for php://temp streams that have just been created.
This makes the test sequence used in the http-interop tests fail. I have compared this to the nyholm implementation and they do not check for file being readable and thus make the factory work as expected.
This is why I tried to postpone the test to the moment the stream is actually used.

See https://github.com/slimphp/Slim-Psr7/pull/100#issuecomment-508842887 for infos about the "is readable" check.
In the end, the composer.json should be removed from the PR (set back to what it was before).

Okay, I will try to work it out with your version of the factory. Of course I plan to squash and polish everything before marking the PR ready, obviously no need for nyholm nor the related test case :-)

So I prepared this, but I have one question before I mark this ready:
in the UploadedFileFactory as you have written above, the code goes like this:
        if ($stream instanceof Stream) {
            if (!$stream->isReadable()) {
                throw new InvalidArgumentException('File is not readable.');
            }
        } elseif (!is_readable($file)) {
            throw new InvalidArgumentException('File is not readable.');
        }

... well should we care about the implementation? I believe passing StreamInterface instance as the $stream argument is enough, as the isReadable method is declared by the interface. I believe the above code can be reduced into:
        if (!$stream->isReadable()) {
            throw new InvalidArgumentException('File is not readable.');
        }

However, with this one test (UploadedFileFactoryTest::testCreateUploadedFileWithNonReadableFile) fails, due to the mock object not implementing the isReadable method. I will play with this, though I am not familiar with the prophecy package used for mocking.

I managed to update the test "prophecy" so the test does not fail. IMHO this is the way the factory should be implemented (independent of the particular implementation of the StreamInterface being passed in).
@adriansuter any thoughts?

Coverage decreased (-0.3%) to 99.464% when pulling 2f0752b9e787e90cff3cb3cade975c7632888ed2 on dakujem:patch-uploaded-file-temp-stream into 6e3292963548c6a4c29402fc105b19a1edf6577b on slimphp:master.

This may be due to loosening the UploadedFile parameter type restriction. How can I/we improve the coverage? I believe both cases when a stream and a filename is used are tested. Maybe the case where the exception is thrown is not. Let me see...

@dakujem Yes, we should add a test case for when the $filenameOrStream is neither a stream nor a file name (string). Then we should expect an exception to be thrown.

Done.

42 - nerd 😄.
At a first glance, your PR looks goot to me. Although I have to check it in more detail. Thanks already for your work.

Got a towel with me all the time...
You're welcome. Glad to help.

I may have messed up, I'm not sure how to mark the changes "done".


[fix] add methodOverride to default configs

Fixes #3385
The svelte.config.js files in the templates were not being used and were overridden by the configs in /shared/+typescript and /shared/-typescript. This PR adds configs for the four cases (outlined below) and makes a note in the template configs that they are overridden.

default + typescript: config with methodOverrides
default - typescript: config with preprocess and methodOverrides
skeleton + typescript: config with preprocess
skeleton - typescript: default config

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

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

Tests

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

Changesets

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

whoops! good catch


[Proposal] Adding phpstan checks.

This PR introduces phpstan/phpstan dependency.
More info on what phpstan is https://github.com/phpstan/phpstan.
For now I've enabled level 4 checks on src/ dir.
Performing checks on tests/ dir would probably require phpstan-phpunit, though this package requires phpunit/phpunit which conflicts with simple-phpunit :(
There are more extensions that we could use eg. Doctrine, but for now I wanted to keep it simple and see if You like this idea.

Closing this for now, since getting phpstan to work here, would mean writing some boilerplate code and complicating things.


Fetch youngest flutter/flutter older than flutter/engine for integration tests

Directly fetching flutter/flutter from engine is risky since it can create circular dependency and circular breakage.
Yet we still need flutter/flutter on the engine for running in the pre-submit tests. To solve this we will  Fetch youngest flutter/flutter older than flutter/engine.

This is completed: https://github.com/flutter/engine/pull/16818


Fix dead link

I was going through the README when I stumbled upon a dead link. I think this is the new URL.

Codecov Report
Base: 56.94% // Head: 59.13% // Increases project coverage by +2.18% :tada:

Coverage data is based on head (3f2e381) compared to base (1f0ca16).
Patch coverage: 63.77% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #581      +/-   ##
==========================================
+ Coverage   56.94%   59.13%   +2.18%
==========================================
  Files          30       30
  Lines        2590     2736     +146
==========================================
+ Hits         1475     1618     +143
- Misses       1115     1118       +3

Impacted Files
Coverage Δ

src/file_config.rs
30.46% <0.00%> (-0.41%)
:arrow_down:

src/source.rs
83.82% <ø> (ø)

src/pmtiles/mod.rs
25.92% <6.66%> (-2.46%)
:arrow_down:

src/mbtiles/mod.rs
42.00% <18.18%> (+42.00%)
:arrow_up:

martin-mbtiles/src/lib.rs
76.31% <65.85%> (+3.94%)
:arrow_up:

martin-tile-utils/src/lib.rs
71.42% <65.88%> (-2.26%)
:arrow_down:

src/srv/server.rs
78.66% <86.36%> (+2.25%)
:arrow_up:

src/lib.rs
32.96% <100.00%> (+0.55%)
:arrow_up:

src/pg/pg_source.rs
72.46% <100.00%> (+0.40%)
:arrow_up:

src/utils/utilities.rs
65.27% <100.00%> (+15.27%)
:arrow_up:

... and 6 more

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

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


Set graphql endpoint with env variable

How can I set the graphql endpoint from an env variable so I don’t have to build several versions to run the codebase with several backends:
For example, I’d like to be able to run
ENDPOINT=endpoint1 PORT=4001 node dist/server.js
ENDPOINT=endpoint2 PORT=4002 node dist/server.js

So I can run two instances with different graphql servers without having to build two different dist’s
Is a setup like this possible?

Apologies for the generic response, but I've released a new v3.0 kit, which has been re-written from the ground up.
It bumps the ReactQL stack to Webpack 4, React 16.4, Apollo Client 2.0, and adds Styled Components, full SSR (even in development), and has been re-written in Typescript. It's leaner, faster and has been brought completely up-to-date.
If you're still using ReactQL (and I appreciate you may not be, given the time lag in my response), I'd recommend checking out the new kit to see if your issue has been answered. If not, please feel free to post a new issue at https://github.com/leebenson/reactql


store search pagination state in URL

Related to #829 and #896
We want to store which page the user is on for the pagination in the URL, similar to how we store the search query and which tab is active.

Relates to #896

https://github.com/equinor/energyvision/tree/PADMS-915-store-search-pagination-state

Hi @padms, I've noticed some errors on the console.
When in /news the server throws:

[InstantSearch] renderToString should be passed to getServerState(, { renderToString })

And the client:

when in search and magazine, a few warnings are shown to both client and server console:

You should also remove this from package.json since the dep was upgraded:
  "pnpm": {
    "patchedDependencies": {
<EMAIL_ADDRESS><EMAIL_ADDRESS>    }
  }

@fernandolucchesi Warnings are removed for the newsroom, magazine index pages.. Its getting hard to remove the warnings for search

Also tried to remove it but no luck. Let's leave it like this then, approved ✅ there was still an error on /news, fixed on #1622

@fernandolucchesi I added few more commits here b344994cc7bcd0f4520623e2334a83a28a3237b9 , removed useDebounce

looks to me that although you removed it we still have the debounced value for the search field correct? bc that prevents unnecessary api calls... if that is the case then review is ok ✅

@fernandolucchesi Pushed some commits to fix the language toggle issue and this fix also stops urls from being added  to the history ( which is also another issue). Let me know if the commits are confusing ...

@fernandolucchesi This is now ready for final review

Hi @padms, works for most of the cases, however when navigating on the browser back and forth, sometimes I land in the _next pages... probably happening only in dev for some weird algolia reason? Does it happen to you?

@fernandolucchesi  No I don't see it

@fernandolucchesi No I don't see it

Hmm... I can't replicate and doesn't seem to be happening on prod.. let's move this to acceptance then ✅

@NickHaggerty1 can you review this one?

@fernandolucchesi Seems to work on Magazine and Newsroom. So Approved


fix: modulo op with negative zero divisor produces Nan

Which issue does this PR close?

Closes #521 .
Rationale for this change

What changes are included in this PR?

Improves compatibility with apache spark.
How are these changes tested?

Added a relevant test case.

Filed https://github.com/apache/datafusion/issues/11051 lets see

imho it has to be fixed on DataFusion side. I can see it returns NaN
> select 1 % -0.0;
+------------------------+
| Int64(1) % Float64(-0) |
+------------------------+
| NaN                    |
+------------------------+

PG, Trino fails on such query, DuckDB, Spark returns NULL
I'll start a ticket in DF, if community supports to go with NULL, so no action needed for this ticket, if they decide to fail the query we might need some custom handling

Make sense. I will keep my PR as it then until we get some resolution on the datafusion ticket.
Thank you @comphead

The direct reason why NaN is produced by dividing by -0.0 is that EqualTo condition is failing in nullIfWhenPrimitive() of QueryPlanSerde
DataFusion changed their behavior several versions ago, to fail for dividing by zero. The DataFusion community recommendation to keep old behavior was to put if condition such as nullIfWhenPrimitive().
I would say we should do something like
if (expression.dataType == DoubleType) {
    If(Or(EqualTo(expression, zero), EqualTo(expression, negZero)), Literal.create(null, expression.dataType), expression)
} else {
    If(EqualTo(expression, zero), Literal.create(null, expression.dataType), expression)
}

If is also supported natively, so it won't be too much overhead (at least that was the case last time I tried).

The direct reason why NaN is produced by dividing by -0.0 is that EqualTo condition is failing in nullIfWhenPrimitive() of QueryPlanSerde
DataFusion changed their behavior several versions ago, to fail for dividing by zero. The DataFusion community recommendation to keep old behavior was to put if condition such as nullIfWhenPrimitive().
I would say we should do something like
if (expression.dataType == DoubleType) {
    If(Or(EqualTo(expression, zero), EqualTo(expression, negZero)), Literal.create(null, expression.dataType), expression)
} else {
    If(EqualTo(expression, zero), Literal.create(null, expression.dataType), expression)
}

If is also supported natively, so it won't be too much overhead (at least that was the case last time I tried). I would hesitate to re-implement whole operator only for negative zero case. I feel we should reuse DataFusion as much as possible

makes a lot of sense. I have mad a fix as per your comments.
please review @kazuyukitanimura

can someone please re-run the CI? It seems like a task failed because of network error.
cc @kazuyukitanimura @comphead

@kazuyukitanimura ready for review

@kazuyukitanimura ready for review.

Codecov Report
Attention: Patch coverage is 52.08333% with 23 lines in your changes missing coverage. Please review.

Project coverage is 53.59%. Comparing base (2fc45a2) to head (6e843da).
Report is 20 commits behind head on main.

Files
Patch %
Lines

.../scala/org/apache/comet/serde/QueryPlanSerde.scala
52.08%
9 Missing and 14 partials :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##               main     #585       +/-   ##
=============================================
+ Coverage     34.13%   53.59%   +19.45%
+ Complexity      809      792       -17
=============================================
  Files           106      105        -1
  Lines         38586     9940    -28646
  Branches       8566     1880     -6686
=============================================
- Hits          13172     5327     -7845
+ Misses        22674     3648    -19026
+ Partials       2740      965     -1775

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@kazuyukitanimura could you please review once? CI passed.

@vaibhawvipul Sorry, I got busy with something else. I may be unable to review or work on OSS a week or two.

@andygrove @viirya can i get a review please?

@andygrove / @kazuyukitanimura can we please get CI triggered? and also a review?

The main issue was fixed by https://github.com/apache/datafusion-comet/pull/953
The test cases from this PR would be still helpful

Please never mind my comment above, I will post a workaroud PR

@kazuyukitanimura can we close it?

Yes @comphead @vaibhawvipul


Update README.md

This is only for Hackertobest competition.

Please help me to win the competition.


Crash when creating anonymous function.

So I was thinking this was a node REPL, but i guess it's not, because when I tried a simple JS thing:
(function(){return 5})()

But then it crashed on me:
/root/lib/node_modules/bin-nsh/node_modules/lib-cmdparse/index.js:15
    if (env && item[0] != '-' && item.indexOf('=') > 0) {
                                      ^
TypeError: Object #<Object> has no method 'indexOf'
    at /root/lib/node_modules/bin-nsh/node_modules/lib-cmdparse/index.js:15:39
    at Array.forEach (native)
    at parse (/root/lib/node_modules/bin-nsh/node_modules/lib-cmdparse/index.js:13:9)
    at run (/root/lib/node_modules/bin-nsh/nsh.js:123:16)
    at readline (/root/lib/node_modules/bin-nsh/nsh.js:93:7)
    at /root/lib/node_modules/bin-nsh/nsh.js:176:5
    at Interface._onLine (readline.js:200:5)
    at Interface._line (readline.js:531:8)
    at Interface._ttyWrite (readline.js:760:14)
    at ReadStream.onkeypress (readline.js:99:10)
<---- first runner exited
<---- stopping init because BOOT=0 (set BOOT=1 to override)
docker@boot2docker:~$

I have a feeling this isn't intended behaviour.
Uhh, bug report?

status?


Could not setup from Integration UI

無法從整合加入設定
Logger: homeassistant.config_entries
Source: config_entries.py:720
First occurred: 23:23:43 (2 occurrences)
Last logged: 23:25:30

Error occurred loading configuration flow for integration Hitachi_smart_app: cannot import name 'HTTP_OK' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)

碰到同樣的問題, HA版本是2022.3.3

Same here.

跟樓上大大們遇到一樣的問題

Open Code Editor
Open custom_components/Hitachi_smart_app/smarthome/init.py
line 6
#from homeassistant.const import HTTP_OK
line 692
if response.status == HTTP_OK => if response.status == 200
it's work for me.


⚠ Bofrost.lu has degraded performance

In 141bbf0, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 981 ms

Resolved: Bofrost.lu performance has improved in 938aebb.


Add blog post

#59
Link to overlay in blog post goes to GitHub and has redirect to overlay in the documentation. So directly added the document overlay link
At the end of the blog, removed the content about kubecon conference. Please let me know if that to be included as well

Hi @kayvee83 thank you for your contribution! We will only add unique-to-carvel.dev blog posts to the website, not posts that are posted elsewhere. If you are interested in writing a brand new blog post to add to the website, please reach out to us in #carvel: https://kubernetes.slack.com/archives/CH8KCCKA5
Thanks, again!


ruby highlighting in readme

simply add the ruby tag to the code block for syntax highlighting

:+1:

Is it the only place where highlight is not rubyish?

Yes


VScode extensions manager not working

Type: Bug
I just installed latest vscode version (1.92.1) on my linux OS (ubuntu distrubition) and I got the below error while searching for any plugin:
Error while fetching extensions.
Failed to fetch
VS Code version: Code 1.92.1 (eaa41d57266683296de7d118f574d0c2652e1fc4, 2024-08-07T20:16:39.455Z)
OS version: Linux x64 6.5.0-45-generic
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (16 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_offwebnn: disabled_off

Load (avg)
0, 1, 1

Memory (System)
31.08GB (24.67GB free)

Process Argv
--crash-reporter-id 919787b6-c724-450e-ac32-1c44ca0eed45

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
wayland

Extensions: none
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
impr_priority:31102340
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31111718

I am facing the same issue. It was working fine few days ago no settings were changed.

@sandy081
any update on this issue ?

he firewall I was using was blocking VSCode’s internet access, so I had to manually grant permission

@sandy081 any update on this issue ?

Was caused by kaspersky, had same issue on windows update and for some magical reasons it started also causing it on chrome this morning

I am facing the same issue. It was working fine few days ago no settings were changed.

Can you please open the network tab in dev tools and check the extensionquery requests to Marketplace and share the error with us

F1 > Developer: Toggle Developer Tools

I share the general view with the console output below.
From the 4 extensionquery shown 2 are identical, I attach the details of the headers.

I share the general view of the Network tab, with the console output below
Every extension search throws 4 extensionquery, 2 are identical so I share the headers in the 2 below images.

Seems proxy related.


Record attempted trades

In MarketAdapter, we log trades, whether they were filled or killed. This data could be valuable, and we should probably save them to a DB (or at least have an option to do this).

We no longer use InfluxDB, so the log statements we use now are a little funny (since they're still in the Influx schema). We should use the logger to create some logs on filled/killed attempts, something that could be plausibly read by machine. Then we can close this issue I reckon.

@adamrothman attempted trades are logged at the debug level, right? So this issue is resolved?

I answered my own question. Proposed trades are logged, noted as either filled or killed. They appear to be Python dicts, so I am confident the log statements would be machine-parseable if someone wanted to record them and use them (e.g. to create more realistic backtests).


bugfix: fix when TC returns RollbackFailed FailureHandler not executed

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
fixes :https://github.com/seata/seata/issues/5231

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #5362 (40e14bc) into 2.x (1400743) will decrease coverage by 0.03%.
The diff coverage is 22.22%.

:exclamation: Current head 40e14bc differs from pull request most recent head 1330765. Consider uploading reports for the commit 1330765 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@             Coverage Diff              @@
##                2.x    #5362      +/-   ##
============================================
- Coverage     48.54%   48.52%   -0.03%
+ Complexity     4300     4299       -1
============================================
  Files           771      771
  Lines         27350    27358       +8
  Branches       3410     3410
============================================
- Hits          13277    13275       -2
- Misses        12669    12676       +7
- Partials       1404     1407       +3

Impacted Files
Coverage Δ

...in/java/io/seata/tm/api/TransactionalTemplate.java
58.90% <22.22%> (-1.97%)
:arrow_down:

...rage/redis/store/RedisTransactionStoreManager.java
75.83% <0.00%> (-0.78%)
:arrow_down:

...very/registry/zk/ZookeeperRegisterServiceImpl.java
61.02% <0.00%> (-0.74%)
:arrow_down:

...o/seata/server/coordinator/DefaultCoordinator.java
45.45% <0.00%> (-0.42%)
:arrow_down:

...er/src/main/java/io/seata/server/ServerRunner.java
50.00% <0.00%> (ø)

...erver/storage/file/session/FileSessionManager.java
61.78% <0.00%> (+0.63%)
:arrow_up:


chore: simplify utxo apis

Codecov Report
Patch coverage: 50.00% and project coverage change: +0.44 :tada:

Comparison is base (a02dc49) 62.83% compared to head (7e54b79) 63.27%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #113      +/-   ##
===========================================
+ Coverage    62.83%   63.27%   +0.44%
===========================================
  Files           17       16       -1
  Lines          444      433      -11
  Branches       167      166       -1
===========================================
- Hits           279      274       -5
+ Misses         165      159       -6

Flag
Coverage Δ

unittests
63.27% <50.00%> (+0.44%)
:arrow_up:

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

Impacted Files
Coverage Δ

...ages/swapkit/swapkit-entities/src/helpers/asset.ts
100.00% <ø> (ø)

...kages/swapkit/swapkit-entities/src/helpers/memo.ts
85.71% <ø> (ø)

...es/swapkit/swapkit-entities/src/helpers/network.ts
100.00% <ø> (ø)

...s/swapkit/swapkit-entities/src/helpers/thorname.ts
100.00% <ø> (ø)

packages/swapkit/swapkit-explorers/src/index.ts
90.00% <ø> (ø)

...ckages/toolboxes/toolbox-evm/src/networkHelpers.ts
27.27% <ø> (ø)

packages/toolboxes/toolbox-evm/src/provider.ts
100.00% <ø> (ø)

...oolboxes/toolbox-evm/src/toolbox/BaseEVMToolbox.ts
56.38% <ø> (ø)

packages/toolboxes/toolbox-evm/src/toolbox/bsc.ts
20.00% <0.00%> (-5.00%)
:arrow_down:

...ges/toolboxes/toolbox-evm/src/types/clientTypes.ts
100.00% <ø> (ø)

... and 4 more

... and 2 files with indirect coverage changes

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


[feat]: Add a clock displaying system time (UTC) (visible while looking at logs!)

Prerequisites

[X] I have searched for existing issues that already suggest this feature, without success.

Describe the Feature Request
Please consider adding a clock displaying the Embassy OS time.
I was initially thinking on the left hand side, but anywhere so it is visible while looking at logs would be helpful
This could be more useful for some folks than even the snake game.
Describe the Use Case
A problem occurs at 10am local time and I open up the logs to see what the issue might be.  I see errors in the logs starting at 10am.  Did the errors occur just now, 4 hours ago? 1 hour ago?  It depends on my time zone vs. UTC.  Would be nice if I could just see the current system time in the same browser window that I see the log entries.
Describe Preferred Solution
Add a clock in the left sidebar - perhaps between Snek and LogOut? or between Start9 and Services?  don't really care where...
Describe Alternatives
Maybe just add it to the title bar on all Logs screens?
replace "<-  Logs                                                                   "
with      "<-  Logs             Current Embassy time is: 18:43:05"
I can look up the time difference manually every time - but I don't spend a lot of time looking at logs or dealing with UTC and I do change locations / time zones from time to time, so it's a bit of a pain.
Anything else?
Not very important, but it would be nice to have for me - so I thought particularly for less technical folks, it might be nice for them too.

@dr-bonez BE component: add endpoint to get server time

@JesseMarkowitz Thanks for the request! I totally see how this could be annoying 😅 Adding to our next milestone

@elvece for a proper clock, we don't want to be spamming the backend. You can probably show the current UTC time pretty easily without any request to the backend, and let that update live. Only use case of the endpoint IMO is because it could show an issue with NTP, if it's too far off of what it should be.

@elvece for a proper clock, we don't want to be spamming the backend. You can probably show the current UTC time pretty easily without any request to the backend, and let that update live. Only use case of the endpoint IMO is because it could show an issue with NTP, if it's too far off of what it should be.

Cool maybe we just call the endpoint on refresh or something, to make sure we're in sync? Perhaps that doesn't matter. Thanks for the insight.

Even lighter: just use the client clock and just sync the backend timezone?

backend timezone is always UTC

Maybe a clock showing UTC and local time 🤔 ? @chrisguida are the log timestamps the same for every service (same format) from the BE endpoint?


PEP 004 - Labels and Namespaces

Organize and isolate porter documents using labels and namespaces.
This lays storage foundation that PEP003 relies upon.
New PEP Checklist

[x] Is your pull request named: PEP NNN - <TITLE>?
[x] Have you posted your proposal in the forum?
[x] Have you gotten approval and a PEP number from a maintainer?
[x] Did you use the PEP Template?

Forum Suggestion Link
Originally proposed as part of PEP 003: Dependency Namespaces and Labels. https://github.com/getporter/proposals/pull/8

@vdice I have addressed your feedback and synced this with the open PR to the cnab-spec. If you think this is good enough to start iterating on the PEP design, let's merge it. The goal with the PEPs is that merging the first PR as "provisional" means that we want to do the work but haven't finalized the design. I'm going to start relying on that more so that we can get initial proposals out for people to see without requiring it to be complete before merging the provisional PEP.
Once we finish design and are ready to implement, I'll update the PEP to say "implementable".


Function to revoke role

 Issue by thisisommore
Wednesday Feb 02, 2022 at 11:15 GMT
Originally opened as https://github.com/TheLazarusNetwork/marketplace-contracts/issues/17

None

https://mumbai.polygonscan.com/address/0x013EFF13a04b7882eAd886D78F4FdB9D02502300#writeContract#F8


Add and Delete tasks testing

In this checkpoint we installed jest and added mock tests for the addTask function and for the deleteTasks function.
We used babel to translate ES6 so it was compatible with jest.

Thank you All for your review.


[packages] Switch from submit-queue to flutter-luci for PR tree state

Currently flutter/packages uses submit-queue as the "test" in PRs that reflects current tree status (i.e., whether the latest commit's post-submits are all green) to prevent PRs landing into a closed tree. This mostly works, but sometimes it becomes stale in some PRs (e.g., showing red forever even once the tree is green again) for reasons we don't understand. Ideally we would move to the same tooling that flutter/flutter and flutter/engine use, which is flutter-luci (managed by Cocoon, IIUC), so that:

flutter/packages is more consistent with our other repos, making it easier for engineers who move between repos, and
we can debug and fix issues like the staleness problem, since we control the logic.

My understanding that check will only get LUCI post-submit statuses, which means this is blocked on https://github.com/flutter/flutter/issues/114373 since currently about half of our post-submits are on Cirrus.

We no longer have any Cirrus post-submit tests (only one pre-submit)

(Closing was a mis-click)
We no longer have any Cirrus post-submit tests (only one pre-submit), so this is unblocked. We've been having a lot of issues with staleness with this check recently, so now that we're unblocked I would very much like to have the packages repo moved over to the check used by the engine and framework repos.
@yusuf-goog Please re-assign if you're not the right owner for this.

@keyonghan is this done? I recall you did some work around this.

Ah gotcha. Thank you for clarifying!

All cirrus tasks are in LUCI, remaining work

[ ] Enable tree status in packages repo
[ ] Disable submit-queue (uninstall the app) from packages repo
[ ] Stop creating/updating post-submit checkruns to packages repo

https://github.com/flutter/cocoon/pull/3232 landed. A manual push to enable the cronjob works:

@stuartmorgan could you try uninstalling the submit-queue app from the repo?

@stuartmorgan could you try uninstalling the submit-queue app from the repo?

I'm not an admin for the repo, so if it's something you don't have the ability to do, I almost certainly don't either.

@godofredoc Is this something you can help with?

[ ]  Stop creating/updating post-submit checkruns to packages repo

We cannot remove the post-submit checkruns from packages repo considering the auto-publish GitHub action waits for all post-submit tests to pass before publishing. Created https://github.com/flutter/flutter/issues/138092 to track this. (removing this action item from this bug)

Submit-queue was uninstalled, and now packages repo is consistent with other repos with tree-status. Closing here with https://github.com/flutter/flutter/issues/138092 to track a general post-submit tests passing event.


deploy: make csi.sock work on OpenShift 4.5 + SELinux

For some (unknown) reason SELinux got in the way when using
/var/lib/pmem-csi.intel.com/csi.sock. The symptoms were that
node-driver-registrar was unable to connect and thus the CSI driver
never got registered. Disabling SELinux "fixed" this.
When using the more traditional
/var/lib/kubelet/plugins/pmem-csi.intel.com/csi.sock, it worked with
SELinux enabled, so that is what we are using now.
It makes changing the driver name a bit more complicated, though, in
particular when trying to do it via kustomize.

@avalluri: please take another look. I had to rebase and fix one issue (socat paths not updated, which broke sanity testing).
Originally had one commit that would have been back-portable and another commit which updated it for "devel", but during rebasing I lost that, so now the commit no longer applies cleanly to "release-0.7" - won't be hard to solve, so let's go ahead with just one commit for "devel".


feature: ability to use emmet and tailwind-language-server in HEEX and elixir files

Did you check the docs?

[x] I have read all the LazyVim docs
[x] This is not a request for a new or existing extra (see above)

Is your feature request related to a problem? Please describe.
I want the same experience I get when writing svelte code using the lazyvim.plugins.extras.lang.svelte in elixir using lazyvim.plugins.extras.lang.elixir
Describe the solution you'd like
https://github.com/user-attachments/assets/39b0c051-e0d5-4877-b5e8-81a711fc7bb7
That is:

Emmet abbreviation
TailwindCSS language server

Describe alternatives you've considered
Writing html/css by hand 🥲
Additional context
No response

Nevermind 🙃
When I clone and build the live_beats project, the tailwindcss lsp works as expected with the starter repo.
Thank you for all your hard work!


Door interaction  breaks Manual Toolchange at G59.3

Hey Terje,
i hope your Holiday was relaxing! :)
I have added some doorswitches to my enclosure, when i now run a gcode with a toolchange, then everything works until the first toolchange is requested...
a small step by step:
the toolchange is requested : the spindel rises and goes over G59.3 and waits...
then i open the door, the "DOOR:1" appears and i start to change the endmill...
now the endmill is changed, i closed the door... "DOOR:0" appears and now evrything is broken...
i can´t press start -  in the Console comes: "First do a "$TPW" for probing... ", i have a Macro with "$TPW", also not working... i can´t do anything, except "STOP", when i press "STOP" the running Gcode and offsets are useless ...
So what can i do?
Today i broke an endmill, thinking that a reprobing and restarting at a specific line... the spindle went down with G0...
If you have further questions, just ask...
greeting from Germany :)
Einar

here a small video of it...
https://foto-shoot.de/nextcloud/index.php/s/o2SERe3QZjLTdFK
sorry for my bad english and my voice... i´m speaking without voicebox :)
Thx for watching

Hmm, I guess the door signal should be suppressed while changing tools. I did not think of that earlier.
It is a bit like the option to suppress it when in IDLE state, I enable that so I can position my CO2 laser with the lid (door) open.

maybe just add the "TOOL" state to the section where the "IDLE" state is ignored..

maybe just add the "TOOL" state to the section where the "IDLE" state is ignored..

Yes, and also add a check for door open after the tool change has been completed. So best to close the door before ending it with Cycle start.

is this ioSender related or controller based?

Controller. I'll commit a fix soon.

thank you very much!

Fix committed and Web Builder updated. Please report back if it works as intended.

Hey Terje...
you are really awesome...
in the webbuilder i get this message...
Command failed: pio run -etest -cjob.ini
src/grbl/ngc_flowctrl.c: In function 'ngc_flowctrl':
src/grbl/ngc_flowctrl.c:694:23: warning: 'sub' may be used uninitialized in this function [-Wmaybe-uninitialized]
if(sub == NULL)
^
.pio/libdeps/test/grblhal-rgb-plugin/status_light.c:207:21: error: static declaration of 'bit_count' follows non-static declaration
static uint_fast8_t bit_count (uint32_t n)
^
In file included from src/grbl/config.h:112:0,
from src/grbl/grbl.h:37,
from src/grbl/hal.h:31,
from src/grbl/driver_opts.h:30,
from src/driver.h:48,
from .pio/libdeps/test/grblhal-rgb-plugin/status_light.c:36:
src/grbl/nuts_bolts.h:233:14: note: previous declaration of 'bit_count' was here
uint_fast8_t bit_count (uint32_t bits);
^
.pio/libdeps/test/grblhal-rgb-plugin/status_light.c: In function 'rgb_state_changed':
.pio/libdeps/test/grblhal-rgb-plugin/status_light.c:427:76: warning: implicit declaration of function 'ffsl' [-Wimplicit-function-declaration]
if(bit_count(hard_limits.mask) == 1 && (axis = ffsl(hard_limits.mask)) != -1)
^
*** [.pio/build/test/libf0e/grblhal-rgb-plugin/status_light.c.o] Error 1
========================= [FAILED] Took 30.63 seconds =========================
its related to the RGB plugin...
Thx for looking!
And please take it easy!
Einar... :)

Try again now

Firmware was created successfully!
thank you very much!!
what a great support!!
Terje Io @.***> schrieb am Sa., 14. Dez. 2024, 21:45:

Try again now
—
Reply to this email directly, view it on GitHub
https://github.com/terjeio/ioSender/issues/425#issuecomment-2543339868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXI5ITNKP2AI52HFYQMZBTD2FSKIDAVCNFSM6AAAAABTSR4LBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGMZTSOBWHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

so firmware flashed and initial test done (rerun the program from yesterday...)
the Door system is ignored by the TOOL state so that works now!
Only the RGB Pins are different after rebuilding the Firmware.
the assignment has changed so the Colors are messed up... :)
the Pins are assign as follows.
PIN0: 0
PIN1: R
PIN2: G
PIN3: B
but thats another thing... the main important thing was solved in just 24h... amazing!!!
Thank you!
Cheers
Einar


Please add a download counter to the GitHub readme

Is your feature request related to a problem? Please describe.
Not a problem, but an opportunity
Describe the solution you'd like
A clear and concise description of what you want to happen.
Add download shield to Readme.
Describe alternatives you've considered
N/A
Additional context
N/A

Josh asked me about this  and I found a source for PyPI and conda-forge.
Here are examples from each:
PyPI Downloads:
conda-forge Downloads:
I'd also suggest tabularizing these shields to organize them like pandas does. This would help the uninitiated to be clear about what each of these might mean. Certain people will be primarily concerned with code quality while others might be interested in publications or impact based on raw download counts.
I can make a PR for this as an example if there's no objections.

Sounds great, thanks!


Asynchronous load of getTileUrl

Hi,
Opening an issue for a follow up on this discussion.
I'm trying to implement reading DZIs from the filesystem, and my current bottleneck is the synchronous function call of getTileUrl in OSD 3.0.0.
Here's some relevant code of what I'm trying to do (forgive the unorganized thoughts, this is a very rough idea)
  // Function to get a handler to the DZI file, and populate a tileSource state with the base dzi data (width, height, tileSize, tileOverlap)
  const fileAccessHandler = async () => {
    try {
      const [fileHandle] = await window.showOpenFilePicker({
        types: [
          {
            description: "DZI File",
            accept: {
              "application/xml": [".dzi"],
              "application/json": [".dzi"],
            },
          },
        ],
        multiple: false,
        excludeAcceptAllOption: true,
      });

      // Reset folder handle if file handle changes
      if (fileHandle !== dziFileHandle) {
        setDziFolderHandle(null);
      }
      setDziFileHandle(fileHandle);

      const file = await fileHandle.getFile();
      const dziData = await parseDzi(fileHandle);

      // Set the TileSource with the height, width, tileSize, tileOverlap
      setTileSource({
        ...dziData,
      });
    } catch (e) {
      console.log(e);
      setDziFileHandle(null);
    }
  };

  const directoryAccessHandler = async () => {
    try {
      const directoryHandle = await window.showDirectoryPicker();

      setDziFolderHandle(directoryHandle);

      // Add the getTileUrl handler to the existing tileSource state
      setTileSource((prev) => ({
        ...prev,
        getTileUrl: async (level, x, y) => {
          // Utility function that handles getting a nested file from a given root directory handle
          const fileHandle = await getNestedFileHandle(directoryHandle, `${level}/${x}_${y}.png`);
          const file = await fileHandle.getFile();

          // Since a URL is required, create a blob URL that can be read for the image data
          const fileUrl = URL.createObjectURL(file);
          return fileUrl;
        },
      }));
    } catch (e) {
      console.log(e);

      setDziFolderHandle(null);
    }
  };

This currently fails as filesystem api calls are async. I found some similar discussions (1672, 1699, 1707), but wasn't able to get much traction on how to proceed.

I implemented something similar to what you're trying to do in the GeoTiffTileSource plugin.
The gist of it is to let getTileUrl remain synchronous, and just define the async method to actually get the data - but don't do the asynchronous data loading there. Then, override downloadTileStart to perform the load asynchronously.
https://github.com/pearcetm/GeoTIFFTileSource/blob/a66e0e6376a708da6a55772f30751e6eb13c4ed0/GeoTIFFTileSource.js#L169-L196

Thanks!! This gives me a better idea, but I'll have to revisit this to wrap my head around it. This looks like an implementation that works purely as a plugin without having to maintain a forked OSD?
I came across another great repository towa that maintains a fork of OSD with an ImageLoader that can accept a fileHandle.
The geoTIFF plugin looks great btw, I'll have to play around with it!

Closing this as @pearcetm and @pandaxtc 's approaches have clarified my questions here.


GEP: Complete Backend mTLS Configuration

What would you like to be added:
I'd like to bundle three related changes together as part of a broader effort to enable Backend mTLS configuration:

Configuration for the client certificate Gateways should use when connecting to Backends
Ability to specify SANs on BackendTLSPolicy
Add TLS options to BackendTLSPolicy to mirror TLS config on Gateways

Of those, 2 may not seem quite as obvious as the rest. The rationale is that SPIFFE is very commonly used as part of mTLS, and is not compatible with our current requirement that the cert served by the backend must match the SNI used to connect to the backend. Adding the option to separately specify SANs would also enable the use of SPIFFE IDs with BackendTLSPolicy.
All of Envoy, HAProxy, and NGINX should be able to support these capabilities, but there will be some nuance in terms of where the configuration lives.
Why this is needed:
One of the core goals for Gateway API is to provide more secure capabilities than Ingress. This feature would finally allow backend mTLS to be configured natively within Kubernetes APIs, and would likely provide opportunities for closer integration between ingress-focused implementations of this API and mesh-focused implementations.

/remove-lifecycle stale
The changes described here are heading in to Experimental in v1.2.

See #3180 and #3304 for more.


In dot-prod kernel, a typo or intended?

According to the definition of bmm, this line outputs bx1x1 tensor; however, Eqn. 12 in the paper seems to be for NC x NC.
Could you clarify my observation?

The computing order is reversed to reduce time complexity. Self-resolved.


Windows Log Rotation catch-22: cannot rename old file because it is locked

[X] Defect
[ ] Feature Request or Change Proposal

Defects
Make sure that these boxes are checked before submitting your issue -- thank you!

[ ] Included gnatsd -DV output
[X] Included a [Minimal, Complete, and Verifiable example] (http://stackoverflow.com/help/mcve)

Versions of gnatsd and affected client libraries used:
nats-server 1.0.4
OS/Container environment:
Windows Server 2008R2
Steps or code to reproduce the issue:
(1) Configure gnatsd as a Windows service, log to a file [WINDOWS ONLY]
(2) Attempt to rotate the log: ren (cmd.exe) or Move-Item (PowerShell) fails because log file is in active use.
Expected result:
Rename or Move allowed; then gnatsd.exe -sl reload should restart logging to the (now empty) log file
Actual result:
No way to rotate the existing log file out of the way.
Feature Requests
Use Case:
Proposed Change:
Possibility 1: Close log file through gnatsd.exe -sl command
Possibility 2: Include FILE_SHARE_DELETE flag when calling CreateFile. This might allow renaming of the file. See URL below.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa363858(v=vs.85).aspx
Who Benefits From The Change(s)?
Anyone running gnatsd.exe on Windows logging to file
Alternative Approaches
Log to syslog (syslog:true in .cfg or --syslog on gnatsd.exe command line)

Just making a note that I'm aware of this, and will try to take a look in next few days.


Fix: Remove extra empty line

This pull request

[x] removes an extra empty line

Thank you, @ashnazg, @drupol, and @Jean85!


[QUESTION] Why is ring mode fixed to All2All in src/all_gather/ths_op/all_gather_types.h?

This prevents the --ring_mode option in AG tests from working as expected.
By changing the function get_ring_mode() to simply returning its input, the ring_mode option can work as expected, greatly improving the performance for 8xGPUs w/o NVLink.

ring mode is for PCI-e machines. and there are some codes for PCI-e that are not fully tested, especially for GemmRS, and so they are not released (or open sourced).

@lucifer1004 We haven't yet release PCI-E support officially. We will keep you updated. For now I will close the issue.


”Lunca Cernii de Jos” is listed in the drop-down menu

Description:
"Lunca Cernii de Jos" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Lunca Cernii de Jos" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Lunca Cernii de Jos, HUNEDOARA".


[release-4.10] OCPBUGS-14279: Updates to use Java 11 by default

@apoorvajagtap Comments addressed, ptal

/lgtm

/retest-required

/retest-required
level=error msg=Error: Error launching source instance: InsufficientInstanceCapacity: We currently do not have sufficient m6i.xlarge capacity in the Availability Zone you requested (us-west-1b). Our system will be working on provisioning additional capacity. You can currently get m6i.xlarge capacity by not specifying an Availability Zone in your request or choosing us-west-1a.

/retest-required

/label backport-risk-assessed
/label cherry-pick-approved


Facial emotion recognition using deep learning

Description:
Facial emotion recognition using deep learning
Dependencies:
Python 3, OpenCV, Tensorflow
let me know if there's a chance to work on it.
Thank you

I would like to work on this.

are u a dwoc participant?

I'm a participant of Cross WoC

assigning you.

Hi, @akshitagupta15june
I opened this issue hoping that you could assign this to me. I request you to assign this to me.
Thank you

I am sorry @gopichandpuli9 this issue will be assigned to @smriti1313 as she opened it.
You can search for new issues and let me know.

@smriti1313 what label should i add swoc or dwoc?

First of all thank you so much for helping out everytime. I am sorry for being a trouble :).
I am dwoc participant.
Thank you

ok great!

But you first assigned it to me.
I started doing too


Adds project makefile (specially for install job)

Hello,
I add a makefile with an install and Debian package building tasks. I Hope you find this usefull.
Best regards,
Thomas Pérennou

Hi,
Thanks for the contribution. I'm just coming back from holidays, I'll for sure look at it the next few days/weeks!

I already merged the commit concerning git aliases (8298fc664f572a8d2761423daa989b17d518e92f). Nice catch!
The makefile is mostly Debian specific right? If yes, is it possible to move it to the debian folder – or at least to rename it to debian-makefile – without breaking its purpose? (I don't know anything about Debian build system :confused: ) I want to avoid people trying to call make on non-Debian systems, or thinking there is something to build for using it.
Btw: The tests folder and its Makefile is a little bit misleading here. No tests are made, this is just building a workspace with different states, to test gws manually later. There is no interest of running it as default target.

Here is it.
I have kept the makefile in place but deactivated the debian task when required tools are not available.
Tell me if you really move the debian part into its own makefile, I will do it.

Seems better to me, thanks. Let starts with this Makefile and I'll update or move it later if needed.

This is now merged into master, but I moved the Debian files into the packaging/debian directory and updated the file paths as best as I could (see dc91278). Does that still work? Feel free to reopen this if there's anything that needs fixing.


Implement utility method for cleaning up temp dirs

To be used by jobtype implementors

Looks good to me, one comment to consider first though I think.

lgtm, merging.


BLEU on a scale of 0 to 100

I can't think of any good reason to have BLEU on the 0 to 1 scale. Instead of making the code more complicated by adding an option, I propose we make 0-100 BLEU the default.

Thanks. I think we should at least

be consistent across the various evaluation metrics, such as BLEU, chrF, and METEOR
maybe have a "score_scale" variable somewhere, even if it's a pre-defined constant. That way if we (or a user) want to change it later we can

OK I extended this to BLEU, chrF, WER and METEOR. I am less familiar with the other scorers so I don't know the standard, let me know if I should extend to RIBES, ROUGE and the length ratio.
This also adds a --scorer_scale option

Thanks! I think RIBES and ROUGE should also be scaled. Length ratio maybe not?

Should be done (and bug free) now


pipeline for testing on the CMU-Seasons dataset

Excellent tool. Are you going to release the pipeline for the CMU-Seasons dataset?

Any update?

hloc v1.1 now has a pipeline for the Extended CMU Seasons dataset in hloc.pipelines.CMU. It does not yet support sequence or multi-camera localization but this will be added at a later point.


HARP-8201: Avoid glitches when rendering transparent lines

This change should avoid seeing circles when
rendering adjacent segments of solid lines.
Use the stencil buffer and prefer boxstep to smoothstep
when rendering solid-lines with opacity less than 0.98.
Note that we are using 0.98 instead of 1.0 to avoid possible
issues when interpolations give values close to 1.0 instead
of 1.0.

@harpgl-bot retest this please

@harpgl-bot retest this please

@harpgl-bot retest this please


Make a pattern of Geometric Stardust

hey admin of the repo , can you assign this issue to me, and can you also add tag of hacktoberfest , hackaccepted to this issue so that this issue can be considered for hacktoberfest


Well, dear friends, when will you add pictures, forms, comments and directories

Upload pictures
base64 or online upload, or local upload, or ctrl+v upload
Add Table
Slide the mouse into rendering n rows and n columns, select and merge cells, add and delete columns and rows, and drag the mouse to adjust the height of rows
Add a comment
You can select one or more words for a paragraph of text, or add comments to it by overlapping it
Implementation document directory
Document directory similar to Word
Add Referenced Paragraph
Click the pop-up window and select a paragraph of text to render to the last out of focus position of the editor

Hello
You definitely have great ideas, unfortunately I won't develop it because I don't need it.
I'm sorry.
Don't hesitate to fork the project and hack it with your own code. If you are pretty proud of your work, you can then make a pull request so I can merge it to the main project. It's how open-source works.
Good luck!

yes,i do


Big problem

So i m using subliminal 2.0, trying to install the nautilus integration .
But i have the following error;
 Could not find a version that satisfies the requirement subliminal>=2.0 (from -r requirements.txt (line 1)) (from versions: 0.1, 0.2, 0.3, 0.4, 0.5, 0.5.1, 0.6.0, 0.6.1, 0.6.2, 0.6.3, 0.6.4, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.7.5, 1.0, 1.0.1, 1.1, 1.1.1, 2.0rc1) No matching distribution found for subliminal>=2.0 (from -r requirements.txt (line 1))

See #650


bemoji: init at 0.3.0

Description of changes
https://github.com/marty-oehme/bemoji/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 261852 run on aarch64-darwin 1

1 package built:

bemoji


hydrate: memory leak, somewhere

After (only) 135,313 messages ubuntu's OOM killer came and took out hte processes:
[Sa Apr 22 00:20:52 2023] Out of memory: Killed process 18967 (tegracli) total-vm:532276kB, anon-rss:291708kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:872kB oom_score_adj:0

And it seems it's here.

Sounds sensible to me for now.


Prometheus-proxy not able to start - Permission Denied

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
From the Rancher web UI, navigate to a cluster > Tools > Monitoring.  Enable Monitoring.  (we have tried with Prometheus and Grafana persistent storage marked as True as well as False with no difference)
Result:
Cattle-prometheus namespace is created within the System project however the prometheus-proxy container within the prometheus-cluster-monitoring pod / stateful set fails to launch.  The error reported is "/bin/sh: /var/cache/nginx/nginx-start.sh: Permission Denied"
Other details that may be helpful:
I have reviewed ticket #23573 which links to a merge request that suggested a change of storage to EmptyDir and user ID to 101 would solve the problem.  I verified the loaded configuration matches these storage and user semantics.  The container in question is pulling image rancher/nginx:1.17.4-alpine.
This cluster is primarily offline / disconnected from the internet.  System images are manually pulled and imported into the private system registry.  Cluster images are pulled through an Artifactory instance from external sources.
We are enabling monitoring so that we can then enable Istio to make use of some of the additional features that tool provides.
Environment information
Rancher version 2.4.5, deployed in HA configuration.  The clusters on which we are enabling monitoring have at least three hosts each.
Host OS: CentOS 7
Cluster information
Cluster type: Local Custom
Machine Type: VM (in vSphere-managed environment)
Kubernetes version: 1.17.2 (server), 1.17.6 (client)

Docker version (use docker version): 1.13.1, api version 1.26 (as provided by CentOS via RPM)

I am going to try to reproduce this bug this week. We haven't had any other customers reporting this. Can you confirm that you are installing Istio without first enabling the monitoring stack from Tools -> Monitoring?

The Istio component (under Tools -> Istio) will not enable / install without first enabling Monitoring.  We have enabled Monitoring at the cluster level.  We can then enable Istio and the istio-system namespace shows up in the System project and all of its (Istio) pods appear to start successfully.
While the Prometheus monitoring does report as "Enabled" allowing the Istio tool to then be enabled, the Rancher UI now shows a "Monitoring API is not ready" on the cluster dashboard.
And now, because these things report as "Enabled" we are able to begin looking at Istio panels on the project levels, too.  The additional tools (Kiali, Grafana, Jaeger, etc) do come up and attempt to display data but there is no data to display because Prometheus is still down.  In fact, Kiali reports that many other pods are up but that Prometheus is down.
Hope that helps.

I ran into the same issue when trying to enable monitoring on our cluster. prometheus-proxy container under prometheus-cluster-monitoring fails to come up because it fails to start Nginx due to a permission issue.
/bin/sh: /var/cache/nginx/nginx-start.sh: Permission denied

Environment information

Rancher version: v2.4.8
Installation option (single install/HA): single install
Host OS: CentOS 7

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom (kubeadm)
Machine type (cloud/VM/metal) and specifications (CPU/memory): 5x VM - CentOS 7 2vCPU 8GB ram (1 master, 4 worker)
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-13T18:06:54Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:07:13Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version): 19.03.6, API version 1.40

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Importing a custom cluster. 7 hosts, 2 workers, 2cps, 3etcds. Running in vSphere. Air-gapped installation with a private registry.
Result:
All's good except for the prometheus-proxy. The container doesn't start because of a permission problem.
/bin/sh: /var/cache/nginx/nginx-start.sh: Permission denied
Other details that may be helpful:
/bin/sh: /var/cache/nginx/nginx-start.sh: Permission denied
Environment information

Rancher version: v2.4.8
Installation option: HA, with a supplemental cluster. The cluster that has the prometheus pod is in a seperate cluster from rancher itself.

Cluster information

Cluster type: Custom. Pre-created OEL7 VMs.
Machine type (cloud/VM/metal) and specifications (CPU/memory): VMs in vSphere, 5 ESXis, E5-2690 v2 x2 per ESXi host, ~384GB RAM per host
Kubernetes version (use kubectl version): v.1.18.6

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.6", GitCommit:"d32e40e20d167e103faf894261614c5b45c44198", GitTreeState:"clean", BuildDate:"2020-05-20T13:16:24Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:51:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client: Docker Engine - Community
 Version:           19.03.11-ol
 API version:       1.40
 Go version:        go1.14.7
 Git commit:        78418d7
 Built:             Tue Aug 18 22:46:21 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.11-ol
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.14.7
  Git commit:       78418d7
  Built:            Tue Aug 18 22:44:38 2020
  OS/Arch:          linux/amd64
  Experimental:     false
  Default Registry: docker.io
 containerd:
  Version:          1.2.4
  GitCommit:
 runc:
  Version:          1.0.0-rc5+dev
  GitCommit:        4bb1fe4ace1a32d3676bb98f5d3b6a4e32bf6c58
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Okay, a classic case of reporting and then immediately solving the problem.
In my case, the host has the /var mountpoint mounted with the noexec flag.
Removing that, solves the problem. Now why the container executes something in /var, is beyond me.

Unfortunately, the environments we work in will not allow disabling the "noexec" flag on a mount to /var for our hosts.  It kind of goes to your question about why the container is trying to execute something from /var.  Security means a lot to my organization.
Anyone have alternative ideas?

~solved for us
An alternate solution that my lead sys admin found is to create separate mount points under /var/lib{docker,kubectl} where those mount points may be mounted with the exec flag while the base system maintains the noexec flag.
It still does not absolve the issue of executing from the /var/* mount but is a workable solution for us to enable Istio in our Rancher environments.


Javascript callback Question

Hello,
in the documentation of your JavaScript callbacks you write the following:
DCrmEgGridRowOnload Fires for every row to be rendered. Allows setting a field (cell) to readonly and change the background and forground colors.
Is there a special reason why the field have to be set to readonly before the colors can be be changed ?

Hi,
The field doesn't need to be set to readonly to change the colors. Each option can be set desperately without the need to set the others.
Hope this answered your question.
Mehrdad

Thank you for the Clarification :-)


Add some explicit captures for this

Scope & Purpose
Implicit this captures are deprecated as of c++20, so better remove them before things break.
Testing & Verification

[ ] This change is a trivial rework / code cleanup without any test coverage.
[ ] The behavior in this PR was manually tested
[x] This change is already covered by existing tests, such as all of them.
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

Rebased on devel, maybe the tests now pass, too!

Wee, tests pass.


No function calling support currently implemented.

OpenAI just released gpt-4-0613, gpt-4-32k-0613, and gpt-3.5-turbo-0613 which allow "function calling" from the model.
See: New function calling docs, and blog update.

I've opened a draft PR (#60) for this. Let me know your thoughts 😊


Test for Discord Server

Describe the Issue
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

dfsa

fdasfsd

dfasfsa

Hi This is John


Hi I liked, thank you!

I I have an error with the links that start with
"https://us02web.zoom.us/rec/share/K5...
I delete the subdomine and its working
"https://zoom.us/rec/share/K5....
Thank you

Fixed in https://github.com/hyunbinseo/zoom-rec-dl/commit/f9517df2f65601fd4b078200172c6814c00abad6. Can you re-download the script and check if it works?


Ingest democube Landsat 5 sample set to EPSG:3577

#67
For testing non geographic projections on the THREDDS test instance

Test data in Albers EPSG:3577 is available at http://dapds00.nci.org.au/thredds/catalog/uc0/rs0_dev/alberscube/catalog.html
Looks good to me!


Update SecurityStatus.json

Fixes #
Proposed Changes

Fixing code to align to Sentinel info @  https://github.com/Azure/Azure-Sentinel/blob/master/Workbooks/README.md