python3Packages.anyio: 3.3.2 -> 3.3.4

Motivation for this change
https://anyio.readthedocs.io/en/stable/versionhistory.html
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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 146367 run on x86_64-linux 1

4 packages marked as broken and skipped:

python38Packages.hug
python38Packages.pytest-sanic
python39Packages.hug
python39Packages.pytest-sanic

4 packages failed to build and already failed to build on hydra master:

home-assistant: log was empty
python38Packages.httpx-socks: log was empty
python39Packages.httpx-socks: log was empty
wapiti: log was empty

35 packages failed to build and are new build failures:

esphome: log was empty
platformio: log was empty
python38Packages.asyncclick: log was empty
python38Packages.authcaptureproxy: log was empty
python38Packages.cirq: log was empty
python38Packages.cirq-rigetti: log was empty
python38Packages.dependency-injector: log was empty
python38Packages.envoy-reader: log was empty
python38Packages.fastapi: log was empty
python38Packages.ha-philipsjs: log was empty
python38Packages.ismartgate: log was empty
python38Packages.json-logging: log was empty
python38Packages.jupyter-server-mathjax: log was empty
python38Packages.jupyter_server: log was empty
python38Packages.jupyterlab: log was empty
python38Packages.jupyterlab-git: log was empty
python38Packages.jupyterlab_server: log was empty
python38Packages.jupytext: log was empty
python38Packages.nbclassic: log was empty
python38Packages.nbdime: log was empty
python38Packages.pyquil: log was empty
python38Packages.python-kasa: log was empty
python38Packages.respx: log was empty
python38Packages.slowapi: log was empty
python38Packages.starlette: log was empty
python38Packages.teslajsonpy: log was empty
python39Packages.cirq: log was empty
python39Packages.jupyter-server-mathjax: log was empty
python39Packages.jupyter_server: log was empty
python39Packages.jupyterlab: log was empty
python39Packages.jupyterlab-git: log was empty
python39Packages.jupyterlab_server: log was empty
python39Packages.jupytext: log was empty
python39Packages.nbclassic: log was empty
python39Packages.nbdime: log was empty

98 packages built:

apache-airflow (python39Packages.apache-airflow)
datasette (python39Packages.datasette)
dyndnsc
faraday-cli
gigalixir (python39Packages.gigalixir)
lexicon
mailman
odoo
pylode
python38Packages.amcrest
python38Packages.anyio
python38Packages.apache-airflow
python38Packages.asyncwhois
python38Packages.axis
python38Packages.datasette
python38Packages.datasette-template-sql
python38Packages.denonavr
python38Packages.elmax
python38Packages.entrance
python38Packages.entrance-with-router-features
python38Packages.falcon
python38Packages.gigalixir
python38Packages.httpcore
python38Packages.httpx
python38Packages.httpx-ntlm
python38Packages.iotawattpy
python38Packages.ipfshttpclient
python38Packages.ircrobots
python38Packages.mailman (python39Packages.mailman)
python38Packages.openapi-core
python38Packages.pylitterbot
python38Packages.pypoint
python38Packages.pyrmvtransport
python38Packages.pytest-httpx
python38Packages.qcs-api-client
python38Packages.rollbar
python38Packages.sanic
python38Packages.sanic-auth
python38Packages.sanic-testing
python38Packages.simple-rest-client
python38Packages.sunpy
python38Packages.total-connect-client
python38Packages.webargs
python38Packages.whodap
python38Packages.youtube-search-python
python38Packages.zeep
python39Packages.amcrest
python39Packages.anyio
python39Packages.asyncclick
python39Packages.asyncwhois
python39Packages.authcaptureproxy
python39Packages.axis
python39Packages.cirq-rigetti
python39Packages.datasette-template-sql
python39Packages.denonavr
python39Packages.dependency-injector
python39Packages.elmax
python39Packages.entrance
python39Packages.entrance-with-router-features
python39Packages.envoy-reader
python39Packages.falcon
python39Packages.fastapi
python39Packages.ha-philipsjs
python39Packages.httpcore
python39Packages.httpx
python39Packages.httpx-ntlm
python39Packages.iotawattpy
python39Packages.ipfshttpclient
python39Packages.ircrobots
python39Packages.ismartgate
python39Packages.json-logging
python39Packages.mailman-hyperkitty
python39Packages.openapi-core
python39Packages.pylitterbot
python39Packages.pypoint
python39Packages.pyquil
python39Packages.pyrmvtransport
python39Packages.pytest-httpx
python39Packages.python-kasa
python39Packages.qcs-api-client
python39Packages.respx
python39Packages.rollbar
python39Packages.sanic
python39Packages.sanic-auth
python39Packages.sanic-testing
python39Packages.simple-rest-client
python39Packages.slowapi
python39Packages.starlette
python39Packages.sunpy
python39Packages.teslajsonpy
python39Packages.total-connect-client
python39Packages.webargs
python39Packages.whodap
python39Packages.youtube-search-python
python39Packages.zeep
soco-cli
theharvester
ytmdl

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

odoo:

error: build log of '/nix/store/319jzwp6jdcnb5ydvbfw9zjky3mm8dll-odoo-15.0.20211029' is not available
When evaluating attribute ‘odoo’:
warning: unused-argument
Unused argument: stdenv.
Near pkgs/applications/finance/odoo/default.nix:1:3:
  |
1 | { stdenv
  |   ^

warning: unused-argument
Unused argument: python3.
Near pkgs/applications/finance/odoo/default.nix:4:3:
  |
4 | , python3
  |   ^

python38Packages.entrance:

error: build log of '/nix/store/irpz9zppfpc9q95q2qffvxlrwh53pv8p-python3.8-entrance-1.1.17' is not available
When evaluating attribute ‘python38Packages.entrance’:
warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/entrance/default.nix:39:
   |
39 |     description = "A server framework for web apps with an Elm frontend";
   | ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python38Packages.entrance-with-router-features:

error: build log of '/nix/store/4chkjaj4y40nr1j3iwzd24y9r38d071n-python3.8-entrance-1.1.17' is not available
When evaluating attribute ‘python38Packages.entrance-with-router-features’:
warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/entrance/default.nix:39:
   |
39 |     description = "A server framework for web apps with an Elm frontend";
   | ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python38Packages.respx:

warning: duplicate-check-inputs
Dependencies listed in propagatedBuildInputs should not be repeated in checkInputs.
Detected duplicates:

python3.8-httpx-0.19.0

Near pkgs/development/python-modules/respx/default.nix:28:3:
   |
28 |   checkInputs = [
   |   ^

Near pkgs/development/python-modules/respx/default.nix:24:3:
   |
24 |   propagatedBuildInputs = [
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/duplicate-check-inputs.md

python38Packages.rollbar:

error: build log of '/nix/store/pqpj7xwhakj34abq38220w7pcmd61chw-python3.8-rollbar-0.16.2' is not available
When evaluating attribute ‘python38Packages.rollbar’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/rollbar/default.nix:45:5:
   |
45 |     maintainers = with maintainers; [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python39Packages.entrance:

error: build log of '/nix/store/c7ip39qscqbs5sy6i2zc0g1nbmq34ink-python3.9-entrance-1.1.17' is not available
When evaluating attribute ‘python39Packages.entrance’:
warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/entrance/default.nix:39:
   |
39 |     description = "A server framework for web apps with an Elm frontend";
   | ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python39Packages.entrance-with-router-features:

error: build log of '/nix/store/595wj8w7bzfb01fgx95zhy78igqp5c5v-python3.9-entrance-1.1.17' is not available
When evaluating attribute ‘python39Packages.entrance-with-router-features’:
warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/entrance/default.nix:39:
   |
39 |     description = "A server framework for web apps with an Elm frontend";
   | ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python39Packages.respx:

error: build log of '/nix/store/hlyjrkk5nwm4zwmh7wjib9j3gwjz3pba-python3.9-respx-0.17.1' is not available
When evaluating attribute ‘python39Packages.respx’:
warning: duplicate-check-inputs
Dependencies listed in propagatedBuildInputs should not be repeated in checkInputs.
Detected duplicates:

python3.9-httpx-0.19.0

Near pkgs/development/python-modules/respx/default.nix:28:3:
   |
28 |   checkInputs = [
   |   ^

Near pkgs/development/python-modules/respx/default.nix:24:3:
   |
24 |   propagatedBuildInputs = [
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/duplicate-check-inputs.md

python39Packages.rollbar:

error: build log of '/nix/store/4alx2za32bj69qrabfhcwincszxk0vrx-python3.9-rollbar-0.16.2' is not available
When evaluating attribute ‘python39Packages.rollbar’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/rollbar/default.nix:45:5:
   |
45 |     maintainers = with maintainers; [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md


Void elements (input, img, br, etc.) html output not self-closing

Example:
import karax / [vdom, karaxdsl]
echo build_html input(class="foo")
echo build_html br()

# Expected:
<input class="foo" />

# Got:
<input class="foo"></input>

In practice, browsers are lenient enough to ignore the closing tag except for br where it's actually treated as 2
 tags (at least on Firefox). This can be sidestepped by just using verbatim("
"), but imo karax should output correct HTML in the first place.
I think this can be fixed by defining a list of all void elements then adding another conditional in vdom.nim right above here, something like elif n.kind in VOID_ELEMENTS: result.add(" />").
I can make a pull request if all this sounds reasonable.

Please go ahead and exuse my slow reply. What you said makes perfect sense to me.

Cool! I've made my PR here https://github.com/pragmagic/karax/pull/134


Tooltip blinking when target has children nodes

The target button has the following HTML:

where icon has a background image with an icon. Icon div is smaller that the button itself.
When pointer passes over the button into the icon, tooltip dissappears. After pointer is moved a little bit again over the icon, tooltip appears again.

Hey @batcer this is interesting, I think I know why, but will need to tinker a bit more to confirm.  Will address this ASAP

Similar issue here, but in my case the target element is a button and it seems to cause an additional problem. Only the icon inside it triggers the tooltip.
<Tooltip content='cant delete because'> <button disabled><FontAwesomeIcon icon='trash-alt' /></button> </Tooltip>

@batcer and @FIIFE this issue should be fixed now with v1.9.2

Closing this now as I believe it's been fixed.


Unused declaration in Iteration/Format cause TS build error

🐞 Bug Report
Describe the bug

The original issue is https://github.com/selfrefactor/rambda/issues/511
I am using ts-toolbelt but I ship part of its code within my library, so users receive full TS support out-of-the-box. The unused part IMap extends Map = NumberMap causes TS build error with following TS config:
"compilerOptions": {
        "noUnusedLocals": true,
        "noUnusedParameters": true
 },

Reproduce the bug
Repo: https://github.com/selfrefactor/rambda-tree-shaking
Folder: packages/rambda
Command: yarn build
Expected behavior

Build process completes with no errors.
Possible Solution

Remove the unused code.
Screenshots

Additional context

Thanks for reporting this @selfrefactor. It's fixed!

So again, there are unused variables that causes problems for me. Is there a way to add such check, so I don't have to trouble you every time?

no stale

not stale!


[OASIS-63] Add an OTelStatsdModule

What does this PR do?
Add a statsd implementation that delegates all operations to the encompassed statsd client. This is only expected to be used in OTel agent.
Motivation
This is a workaround to fix the statsd client initialization in OTel agent. See https://github.com/DataDog/datadog-agent/pull/25759#discussion_r1642996487

/merge


[Core reorg] Organize source files per area.

Signed-off-by: David Navarro<EMAIL_ADDRESS>

internals.h now has declarations for .c files that were moved to different directories. It should probably be broken up to keep the declarations near the definitions.

This can be closed now. Replaced by #528 .

This can be closed now. Replaced by #528 .


MINIXCompat_File_Open should return an error if the file can't be opened

(el)vi(s)  now works, kind of.

Good catch, thanks!


SMS All Helpline Volunteers

Describe the solution you'd like
It would be really great if we could send an SMS messages using the YAP Admin interface to:

all helpline volunteers for a service body
all helpline volunteers for an entire region
single helpline volunteer

Describe alternatives you've considered
Haven't really considered any other options - I'm sure there could be something configured in Twilio but I'd like to leverage the YAP admin interface as a communication tool for helpline volunteers as it's already got all the information.

Are you thinking of this an internal notification tool?

Yes :-)
Regards
Bruce

From: Danny Gershman<EMAIL_ADDRESS>Sent: Tuesday, August 7, 2018 10:28:39 PM
To: radius314/yap
Cc: brustar64; Author
Subject: Re: [radius314/yap] SMS All Helpline Volunteers (#121)
Are you thinking of this an internal notification tool?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/radius314/yap/issues/121#issuecomment-411038806, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbqjryR5QLhF9u7PZMEZG0LcldJgkmHVks5uOYf3gaJpZM4Vx_mV.

After much thought, this feature will not be implemented.  It's not core to phonelines and would like to keep the bloat down.

I understand and respect your decision.  Thanks Danny.
I'll try to be more discerning in relation to future feature requests that they are features that go directly to fulfilling our primary purpose.


Make it a manual plugin

Currently sbt-mu-srcgen is automatically enabled on all projects. But it prints an annoying message when it runs on projects where it has not been configured properly.
It would make more sense to ask users to enable it manually where it's needed, using .enablePlugins(SrcGenPlugin).

Chatted with Chris about this and I'm going to take this cc @rafaparadela

Sounds great to me @dmarticus go ahead. Thanks

I'm gonna keep this open until I can merge all the PRs related to it.

Everything got merged in so I'm closing this issue out.


Make default jobs log size depend on heap size

Looking at the base memory footprint of a CrateDB instance, the sys.jobs_log can use up a big chunk depending on what kind of SQL statements are used.
Entries are currently kept in memory via
Items in the jobs log are current kept in memory via JobContextLog and JobContext. That's about ~80 bytes of overhead, but it includes the statement. That can be anything from SELECT 1 (8 bytes, excluding some headers) to large statements that span several hundreds of lines. There are use-cases where statements that take up 1-3 kB is not uncommon.
Based on that, the jobs log can take up anything from 1MB to 30MB or more.

JobContextLog & JobContext structure
***** 64-bit VM, compressed references enabled: ***************************
io.crate.expression.reference.sys.job.JobContextLog object internals:
 OFFSET  SIZE                                               TYPE DESCRIPTION                               VALUE
      0    12                                                    (object header)                           N/A
     12     4   io.crate.expression.reference.sys.job.JobContext JobContextLog.jobContext                  N/A
     16     8                                               long JobContextLog.ended                       N/A
     24     4                                   java.lang.String JobContextLog.errorMessage                N/A
     28     4                                                    (loss due to the next object alignment)
Instance size: 32 bytes
Space losses: 0 bytes internal + 4 bytes external = 4 bytes total

***** 64-bit VM, compressed references enabled: ***************************
io.crate.expression.reference.sys.job.JobContext object internals:
 OFFSET  SIZE                                                            TYPE DESCRIPTION                               VALUE
      0    12                                                                 (object header)                           N/A
     12     4                                                  java.util.UUID JobContext.id                             N/A
     16     8                                                            long JobContext.started                        N/A
     24     4                                                java.lang.String JobContext.username                       N/A
     28     4                                                java.lang.String JobContext.stmt                           N/A
     32     4   io.crate.planner.operators.StatementClassifier.Classification JobContext.classification                 N/A
     36     4                                                                 (loss due to the next object alignment)
Instance size: 40 bytes
Space losses: 0 bytes internal + 4 bytes external = 4 bytes total

For nodes with a small heap, that could actually be a significant portion.
Users can currently change the default size manually, or also set an expiration to have entries expire after a certain amount of time. The jobs log is integrated with the circuit breaker, so if it uses up too much heap the entries are wiped.
So things are not too bad, but we could consider changing some of the defaults based on the available heap. That could improve the experience of trying out CrateDB on a node with low specs.
Or we could consider more radical changes. Like dropping the size and expiration feature, but instead have a fixed memory limit and utilize some kind of ring-buffer internally. That could also reduce the overhead a bit. To make up for the loss of functionality, we could explore options to improve the "log shipping" story into other systems - or have built-in persisted query logging as well.

Closing this as wontfix for now. Probably not enough of an issue to warrant spending time on it.


Docs: Update avamar.md

Fix typo in key.

I have read the Code of Conduct and I hereby accept the Terms

I have read the CLA Document and I hereby sign the CLA


0.95.2 .card-reveal div not being hidden?

Has anything changed to .card, especially .card-reveal?
I'm having a strange bug where the card-reveal div is NOT hidden. It's covering other content.
See here how it is not hidden (appears under card title):
https://www.dropbox.com/s/hr29zp5mux2rb8o/Screenshot 2015-02-20 19.08.30.png?dl=0
There was no issue in 0.95.1 . I see no issue when I use plain HTML, the error happens in my Meteor templates.

@Dogfalo
Just FYI,  the only way to fix this was to override with a new selector and overflow setting.
Something has changed from 0.95.1 to 0.95.2 , can you point me to that change? I would like to use the new and correct implementation.

Fixed in 91d4c19691b41584438781f6ee58e9ab52047294


Ensure exception_retries is always treated as an integer

By default, Thor gives you back a string, so the program
crashes with an ArgumentError if this is actually used.
comparison of Fixnum with String failed (ArgumentError)
There is a separate issue which is that neither this, the batch size, or settings overrides arguments are reported in the CLI (but it somehow still accepts them).
A cleaner of doing this could be to convert this to a named option, as documented in the Thor getting started guide here: https://github.com/erikhuda/thor/wiki/Getting-Started#options-for-a-task
I haven't done this here because I'm not familiar with how Thor works, plus everything uses positional arguments at the moment, and it doesn't make sense to change the API just for one of them.

Good catch, thanks for the fix!  This is now released as version 2.2.2.


[SPARK-5379][Streaming] Add awaitTerminationOrTimeout

Added awaitTerminationOrTimeout to return if the waiting time elapsed:

true if it's stopped.
false if the waiting time elapsed before returning from the method.
throw the reported error if it's thrown during the execution.

Also deprecated awaitTermination(timeout: Long).

cc @tdas, @JoshRosen

Test build #26002 has started for   PR 4171 at commit cdc820b.

This patch merges cleanly.

Test build #26002 has finished for   PR 4171 at commit cdc820b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  case class Rating(userId: Int, movieId: Int, rating: Float, timestamp: Long)
  case class Movie(movieId: Int, title: String, genres: Seq[String])
  case class Params(
class ALS extends Estimator[ALSModel] with ALSParams
 case class RatingBlock(srcIds: Array[Int], dstIds: Array[Int], ratings: Array[Float])

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

Yeah, it seems good to propagate the Boolean return value from waiter here, or else there's no way to distinguish timeout from non-timeout. And yes it seems like it requires a new method.

Please add unit tests for this behavior! It should be in StreamingContextSuite.

Also could could update the python API as well?

Test build #26726 has started for   PR 4171 at commit c9e660b.

This patch merges cleanly.

LGTM, will merge when tests pass.

Test build #26726 has finished for   PR 4171 at commit c9e660b.

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

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

Thanks! I have merged this.
On Tue, Feb 3, 2015 at 11:30 PM, UCB AMPLab<EMAIL_ADDRESS>wrote:

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26726/
Test PASSed.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/4171#issuecomment-72803099.


HDFS-17307. docker-compose.yaml sets namenode directory wrong causing datanode failures on restart

Restarting existing services using the docker-compose.yaml, causes the datanode to crash after a few seconds.
How to reproduce:
$ docker-compose up -d # everything starts ok
$ docker-compose stop  # stop services without removing containers
$ docker-compose up -d # everything starts, but datanode crashes after a few seconds

The log produced by the datanode suggests the issue is due to a mismatch in the clusterIDs of the namenode and the datanode:
datanode_1         | 2023-12-28 11:17:15 WARN  Storage:420 - Failed to add storage directory [DISK]file:/tmp/hadoop-hadoop/dfs/data
datanode_1         | java.io.IOException: Incompatible clusterIDs in /tmp/hadoop-hadoop/dfs/data: namenode clusterID = CID-250bae07-6a8a-45ce-84bb-8828b37b10b7; datanode clusterID = CID-2c1c7105-7fdf-4a19-8ef8-7cb763e5b701

After some troubleshooting I found out the namenode is not reusing the clusterID of the previous run because it cannot find it in the directory set by ENSURE_NAMENODE_DIR=/tmp/hadoop-root/dfs/name. This is due to a change of the default user of the namenode, which is now "hadoop",  so the namenode is actually writing these information to /tmp/hadoop-hadoop/dfs/name.
See https://issues.apache.org/jira/browse/HDFS-17307

Following this change, it would be nice if also the documentation located at https://hub.docker.com/r/apache/hadoop undergoes the same update.

do you know which commit broke this?

This is what I've found diving into the project history:

docker-compose.yaml was always configured with ENSURE_NAMENODE_DIR: "/tmp/hadoop-root/dfs/name"
the namenode base image always specified the use of the hadoop user (so my initial assumption about the previous use of the root user was wrong)
the default configurations of Hadoop and HDFS are the ones determining the use of the /tmp/hadoop-${user.name}/dfs/name directory,  but they date back before the creation of the docker-compose.yaml

So, it looks like the issue has always been there.


Update to remove smimesign from Linux instructions

Why:
#31465 was rejected because it added docs for gpgsm (X509 signing that works on Linux) - this at least clears up the fact smimesign does not work on Linux.
Closes:
https://github.com/github/smimesign/issues/45
Related to:
https://github.com/github/smimesign/issues/30
What's being changed (if available, include any code snippets, screenshots, or gifs):
Remove smimesign from Linux docs
Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@jc-clark PR as requested

@N6UDP Thanks so much for opening a PR with this fix! I'll get this merged 🍏


Feature Request : Implement 12hr/24hr time / battery percentage / wifi strength on main emulationstation view

One of the quality of life things I really like about 351 elec is its ability to show time, battery percentage and wifi on the top of the screen. Knowing those values has been a bit more informative than waiting for the little light on the front to switch to yellow/red, or drilling through settings to check. This would of course require theme support, but it would be super nice to have :)

Time is something that is possible already by changing the theme to one that supports it and enabling show time in the start menu.  The rest is something that’s already possible with the header version of ES for all devices except the 351v.  This is not something I will look to implement for the 351v at this time.


License?

Hi! I'm interested in playing with what seems to be a really cool new tool, but noticed you don't currently seem to have a license applied to your project. According to https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository#choosing-the-right-license, this technically means that legally nobody is allowed to do much with your code other than read it. Would you consider adding an explicit license to the repo to make your intentions clear?

Sorry about that! Added MIT license.

Awesome, thank you! Looking forward to giving it a proper workout!
On Thu, 11 May 2023 at 01:07, Yanay1 @.***> wrote:

Sorry about that! Added MIT license.
—
Reply to this email directly, view it on GitHub
https://github.com/snap-stanford/SATURN/issues/18#issuecomment-1542956182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFM54YB7RZDJYLHAXZMAO4LXFQUSRANCNFSM6AAAAAAX45BSYE
.
You are receiving this because you authored the thread.Message ID:
@.***>


bind property is undefined

Hi @Dipesh1Thakur,
Could you give us more context on the error that you've discovered? E.g. error log, steps to reproduce, version of create-react-app, node.js, npm etc.
Thanks & have a good weekend

Sure but later
On Fri, Sep 11, 2020, 9:43 PM Tobias Büschel<EMAIL_ADDRESS>wrote:

Hi @Dipesh1Thakur https://github.com/Dipesh1Thakur,
Could you give us more context on the error that you've discovered? E.g.
error log, steps to reproduce, version of create-react-app, node.js, npm
etc.
Thanks & have a good weekend
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/9620#issuecomment-691178512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIL7V65KSN43CSI35ZSAT6LSFJCLDANCNFSM4REUGSHA
.


Updated hyper-rusttls to native-tls

To avoid the ring dependency updated hyper-rusttls to native-tls
Fixes: #521

Closing this PR, As it is duplicate of #513


Update dev program messaging

Q
A

Bug fix?
no

New feature?
no

New sample?
no

Related issues?
none

What's in this Pull Request?
Updates messaging re: the Microsoft 365 Developer Program.

I think the FAQ link (qualify section) is not working. It is currently showing as "office/developer-program/microsoft-365-developer-program-faq#who-qualifies-for-a-microsoft-365-e5-developer-subscription-"
Will this resolve in a later stage or does it need the https://... prefix?
FAQ

I think the FAQ link (qualify section) is not working. It is currently showing as "office/developer-program/microsoft-365-developer-program-faq#who-qualifies-for-a-microsoft-365-e5-developer-subscription-" Will this resolve in a later stage or does it need the https://... prefix?
FAQ

Thanks. Yes, it's missing the domain. I'll add that in here.


specs-go/v1: remove stutter in name of index

We are already working with images, so we don't need to repeat
ourselves. Changing ImageIndex to `Index.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

ping @opencontainers/image-spec-maintainers

LGTM

LGTM


Implement Minimax

TODO - implement minimax and alpha-beta pruning algorithms!

For some reason this is based on the deleted branch - no worries, this won't break anything since the deleted branch was already merged into master.


[Feature]: support get_account, get_accounts and get_account_count method from social DB contract

What is your idea or feature suggestion?
Support account methods from social DB contract.
Here is the relevant snippet of code.
Benefits
No response
Where can we find information about this?
No response
Are you willing to provide a PR to address this?
None

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Quick-add of bootstrap in codepen adds bootstrap V4

Challenge Build a Tribute Page has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
As shown in the video, I added bootstrap to my codepen project for the tribute page. By default codepen (currently) uses the following version:
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.0.0-alpha.6/css/bootstrap.min.css
As documented here and as discussed here, img-responsive was replaced by img-fluid. I tried to use img-responsive in the tribute page, but of course, that didn't work. It took me a while to figure out that I had to use img-fluid with bootstrap version 4.
A little hint on the challenge page might be nice to either use bootstrap version 3 or check what has changed in V4 compared to V3.

@RichardHerzog Thanks for reporting this issue!
A hint on the webpage would be helpful, but I'm not sure where to add it so that as many as possible would see it.
Another option could be to update the challenge about responsive images (and probably the other Bootstrap challenges as well) once Bootstrap 5 is released.

@Greenheart I'd put a hint right below the video, since it shows the quick-add feature. Alternatively, or even in addtion, one could put a hint in the precedent challenge (slide 6/7), where the quick-add feature is also shown.

@RichardHerzog What video?
The slides would be a great place to add this tip, since it already has related information :+1:
Since you reported this, maybe you would like to fix this? Me and other contributors would be happy to guide you through the process :blush:
This is the introduction challenge on the beta site (where development of the new curriculum happens). To add this improvement, this line is what becomes the text of slide 6/7
To help you get started, CONTRIBUTING.md walks you through how to set up your local environment all the way to how to submit a pull request.
If you have any questions, please come chat with us in the Contributors Chat Room.
Happy Coding! :smile:

@RichardHerzog
Hello,
you know how to solve your problem is very simple. Just do as I do. Bearing in mind that Bootsrap version 4 is not completely stable, I do not use it.
All you have to do is go to the Settings  of Codepen css tab you delete the cdn of bootstrap 4 set by default and copy / paste the last stable version. this one : https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
Idem for bootstrap javascript
Sorry for my bad english ;)

@Parad0xJ
Yeah, I know. I'm just raising this issue in order to prevent that other students get stuck with this issue, too. I guess that I'm not the only one who is using the quick-add feature 'blindly' and then wondering why some bootstrap classes won't work although I'm doing it like in the challenges before.
@Greenheart
I somehow brought FCC to work on my machine, changed the mentioned line and commited the change to my fork of FCC. But I'm hesitating to create a PR because the current structure of the challenges (in branch staging) changed so that the bootstrap challenges are now way after the tribute page challenge, which makes mentioning the quick-add feature to add bootstrap obsolete in the tribute page challenge. You get what I'm trying to say? 😄

ok, I think you don't know that no problem

@RichardHerzog Great job, but I'm sorry for not mentioning the new curriculum we're working on over at https://beta.freecodecamp.com.
I guess we don't need this change anymore :confused:
As a side note, I'd recommend anyone to learn CSS and create a few projects with it before trying anything else like Sass, Bootstrap etc (which are based on CSS). The foundations of the web will give better knowledge in the long run.

@Greenheart
Ok. Shouldn't the slide itself be deleted then?
Regarding your side note: I totally agree on learning basics before utilizing higher level stuff. But on the other hand, sometimes it's easier to learn with a top-down approach (or system approach). It keeps you motivated because you get results really fast :)

@I think we still need to show how to use CodePen but I'm not sure. It's definitely a good thought!
That's true, it depends on what kind of learner one are. Some learn best by getting results, while others only learn how to use tools while not understanding the theory behind them :blush:

@Greenheart Yeah that makes sense. I guess that with the new order of challenges people won't be using bootstrap at this point anyway. Therefore closing the issue.

Hi, I lost the whole day with that bootstrap 4 bug.
I would kindly suggest that meanwhile the beta is not released, complete the solution, a hint, whatever, to make it go smooth for students.
Cheers,
Diego

Thanks @Parad0xJ
It worked like a charm


Add new IO type and providers and interface  Sensor

This add support into the pi4j-core.  It is a new IO type  Sensor. also defines an interface Sensor, Config/builder and provider.
There exist https://github.com/taartspi/Pi4J_V2-TemperatureSensor      This implements an I2C device that uses a BMP280 sensor, requiring this branch.  This branch also documents connecting an Adafruit BMP280 to a Pi.

@FDelporte       Good day.   I don't see the proper way to connect this pull request to the issue 197.   You have a quick pointer on doing this ?        thanks Tom

I'm not really sure about this PR. It brings in a specific use-case/device, something that we removed when moving from V1 to V2 to improve maintainability. What do you think @eitch @savageautomate ?

Relates to #197

Determined this code change is too specific to only two sensor types.  Suggested this implementation could define only the generic interfaces of possible  sensor types. Suggested ENUM be used.


swift-doc doesn't seem to detect protocol extension methods

We have a library that centers around a single protocol that is extended with methods (similar to how Combine has a Publisher protocol and extends it with map and other operations), but these methods don't appear to get picked up by swift-doc
Here's documentation for the protocol: https://pointfreeco.github.io/swift-parsing/Parser/
And here's an example extension method: https://github.com/pointfreeco/swift-parsing/blob/6443f30e5766c2319b58412e7c2687e363b54ff1/Sources/Parsing/Parsers/Map.swift#L1-L15

We have the same situation. For protocols, only the methods/properties requirements are generated. All the public methods in the protocol extension are not detected.

We have the same situation. For protocols, only the methods/properties requirements are generated. All the public methods in the protocol extension are not detected.

A fix for this problem was just merged and will be included in the next release. If you want to use it today (or even test the fix), you can compile it from source using the instructions in the README.


Should we allow implementations to add to the escaped set?

While researching Perl today we've found an interesting issue:

As an interesting point, RegExp grammar can add flags (like /x in the future) but RegExp.escape will not be able to react to these changes.

In both cases - this means that RegExp.escape can't guarantee the length of the returned string between versions of ECMAScript that make extensions to the grammar.

To me, this is a huge deal. I'm wondering - if implementations are allowed to extend the regular expressions grammar - should they be allowed to escape additional characters and we should make it clear that there is no length guarantee on the returned string?
(No other language has a length guarantee but some have a fixed character set which implies a length guarantee)

To me, RegExp.escape's only guarantee is that the string is safe to pass into RegExp. The length of the returned string is basically irrelevant to me.
Would not any additions to the RegExp grammar simply require corresponding changes to the RegExp.escape implementation? (assuming it's worded correctly)

Would not any additions to the RegExp grammar simply require
corresponding changes to the RegExp.escapeimplementation? (assuming it's
worded correctly)

What concerns me is that flags like /x could be added in the future which
would, for example, add comments (with a # syntax).
Moreover from what I understand implementations may choose to extend the
RegularExpression syntax. Maybe allowing them to escape additional
characters and suggesting that an implementation must ensure that the
return result is  possible to pass to a RegExp constructor?
On Fri, Jun 19, 2015 at 10:02 PM, Jordan Harband<EMAIL_ADDRESS>wrote:

To me, RegExp.escape's only guarantee is that the string is safe to pass
into RegExp. The length of the returned string is basically irrelevant to
me.
Would not any additions to the RegExp grammar simply require
corresponding changes to the RegExp.escape implementation? (assuming it's
worded correctly)
—
Reply to this email directly or view it on GitHub
https://github.com/benjamingr/RegExp.escape/issues/27#issuecomment-113607312
.

That's exactly the kind of wording I'm thinking of. With that requirement in place, a builtin RegExp.escape would always (theoretically) be safe, and a polyfilled one could feature-detect these new forms easily.

So something like?

Note: a valid implementation must ensure that the return result does not result in an abrupt completion when passed as the first and only argument to the RegExp constructor. An implementation may choose to escape additional characters in order to maintain this guarantee.

That's good, but the concern isn't just an abrupt completion, it's also about semantics changing as a new flag is added, right?

@ljharb what do you mean?

NOTEs are non-normative, just remove that prefix.

Thanks, what about the actual content?

Since your text says "first and only" argument, and since I can't imagine anyone making any changes to regexes without requiring a new flag, I think that text is definitely sufficient. However, if someone were to make an existing flag do something different (which would also be a breaking change) then this wouldn't cover it - but that's probably not much of a real concern.

Yes, maybe it should say "any flag passed as a second argument". I want to
be safe against a future /x mode for comments.
On Sat, Jun 20, 2015 at 8:49 PM, Jordan Harband<EMAIL_ADDRESS>wrote:

Since your text says "first and only" argument, and since I can't imagine
anyone making any changes to regexes without requiring a new flag, I think
that text is definitely sufficient. However, if someone were to make an
existing flag do something different (which would also be a breaking
change) then this wouldn't cover it - but that's probably not much of a
real concern.
—
Reply to this email directly or view it on GitHub
https://github.com/benjamingr/RegExp.escape/issues/27#issuecomment-113793095
.

I agree with @ljharb that it's not just about abrupt completions but also about semantic equivalence. IIRC Ruby had something like new RegExp(RegExp.escape(s)) ~= s as the invariant, which seems more interesting.

Yes, I agree. What about:

A valid escape implementation must ensure that the return result holds the invariant that when passed as the first and only argument to the RegExp constructor the resulting regular expression will test true against the input string. That is new RegExp(RegExp.escape(s)).test(s) === true for any string s. An implementation may choose to escape additional characters in order to maintain this guarantee.

Do you see any downside to allowing implementations to escape additional characters? Are we sure we're ok with not giving any length guarantee?

I guess I'm not clear when the normative spec text as-is would not already guarantee that.

I guess I'm not clear when the normative spec text as-is would not already guarantee that.

Regarding implementations and regular expressions:

An implementation may extend the ECMAScript Regular Expression grammar defined in 21.2.1, but it must not extend the RegularExpressionBody and RegularExpressionFlags productions defined below or the productions used by these productions.

Now I'm not 100% sure either, but I think it means that regular expression syntax can be extended to a point where other implementations would need to escape more characters.

I guess specifically tie it to that clause then. Or maybe we should just remove that clause; it seems bad for the web in theory, and unused in practice, as far as I know.

I've sent a mail to esdiscuss, to be fair I'm not sure why this is the case either.

I suspect the loose spec around RegExp flags is pre-ES6.  Now that we can extend built-ins, I'd expect that any engine which wants to add new RegExp syntax would do so as a subclass (and then extend RegExpSubclass.escape appropriately).

@cscott ES3 specifies:

An implementation may extend the regular expression constructor's grammar, but it should not extend the RegularExpressionBody and RegularExpressionFlags productions or the productions used by these
productions.

Earlier versions of the spec did not have regular expressions. I wonder if any engines still in use in 2015 use this capability.

I've sent an email about extensions to esdiscuss: https://esdiscuss.org/topic/forbid-implementations-from-extending-the-regexp-grammar
If we can forbid implementations from extending the implementation on their own and not through the standard then this addition will not be required and the proposal will be simplified.

We should include some note about this in the TC39 presentation. I think it should be part of the proposal to eliminate that language.
As such, I would update the spec document with an appropriate <del>.

@domenic good idea, I want to make sure that I didn't miss anything first (like an implementation that utilizes it. I'm not sure how else I can verify that - I checked current and older engines and asked around.
If this is indeed safe to remove - I agree that it's a good idea to tie it to this proposal and add an appropriate <del> clause (and a slide in the presentation).

Yep. And we can drop it if TC39 objects; it's a separable part of the proposal to delete that. But I hope nobody will.

I'd rather put in language limiting extensions to the de facto (?...)
extension mechanism (and flags).  That also guarantees that RegExp.escape
remains safe (since all proposals escape both ( and ?).
Is there any syntax in perlre which gets past our current proposals for
RegExp.escape?  If so, it may be worthwhile to future-proof escape`.
--scott

This isn't really about RegExp.escape as an issue. We can always extend
RegExp.escape when we make additions to the RegExp grammar as a standard
that would not be a problematic issue since we can keep both parts in sync
relatively easily.
On the other hand currently implementations are allowed to diverge in their
regular expressions which means there is no guarantee that they'll behave
the same in some cases. This is really risky for standard behavior and if
an implementation decides to use the clause it could create a big pain
point for developers while keeping it compliant.
Luckily, implementors are insightful people and implementations don't do
that because of precisely those usability implications for end developers.
What I'm suggesting is that we forbid implementations from extending the
regular expressions grammar beyond the language specification and outside
the process. Basically, we take the ECMAScript regular expression object
as specified (minus allowing extensions) as our base line :)
Cheers,
Benji
On Mon, Jul 6, 2015 at 5:03 PM, C. Scott Ananian<EMAIL_ADDRESS>wrote:

I think it would be more worthwhile of we tried to draw a compatibility
boundary.  Taking perlre as a baseline, for example, are there additional
characters we should escape in RegExp.escape so that implementations (and
the language itself) could add more perlre features without breaking
compatibility?  The (?...) syntax (and flags) seems to be the de facto
extension point, can we protect that more narrowly?
--scott
On Jul 6, 2015 1:56 AM, "Benjamin Gruenbaum"<EMAIL_ADDRESS>wrote:

So, following work on RegExp.escape [1] I found out that implementations
may extend the regular expression grammar in JavaScript [2]. However, when
asking esdiscuss and Stack Overflow about it [2][3] it doesn't look like
any implementations currently do so (*).
Can we please forbid implementations from extending the regular
expression syntax? It seems like this could cause compatibility issues
between implementations anyway. We have subclassable RegExp with hooks and
symbols in place and implementations that want to provide an extended
RegExp can subclass RegExp or propose an extension to the language itself.
[1] https://github.com/benjamingr/RegExp.escape
[2]
https://esdiscuss.org/topic/why-are-implementations-allowed-to-extend-the-regular-expressions-syntax
[3]
http://stackoverflow.com/questions/30958288/what-ecmascript-implementations-extend-the-regexp-syntax
(*) some did it to implement ES2015 features before ES2015.

es-discuss mailing list
<EMAIL_ADDRESS>https://mail.mozilla.org/listinfo/es-discuss

Benji -- but you've just specifically mentioned that implementations
are already using the flexibility provided by the spec to experiment
with and implement ES6 features.  Why are you going to foreclose that
possibility for ES2016+?
The perl community has managed to compatibly extend their regex engine
to an almost absurd degree.  There are plenty of ways to add features
to your regexp that don't break "standard-compliant" regexps.  I think
that's the spirit of the existing language in the spec, and it
should be honored.  I'm fine with narrowing the scope, so we know that
new flags and characters after (? are "reserved", for example, but I
don't see why we have to ban future change outright.
--scott
On Mon, Jul 6, 2015 at 10:13 AM, Benjamin Gruenbaum
<EMAIL_ADDRESS>wrote:

This isn't really about RegExp.escape as an issue. We can always extend
RegExp.escape when we make additions to the RegExp grammar as a standard
that would not be a problematic issue since we can keep both parts in sync
relatively easily.
On the other hand currently implementations are allowed to diverge in their
regular expressions which means there is no guarantee that they'll behave
the same in some cases. This is really risky for standard behavior and if an
implementation decides to use the clause it could create a big pain point
for developers while keeping it compliant.
Luckily, implementors are insightful people and implementations don't do
that because of precisely those usability implications for end developers.
What I'm suggesting is that we forbid implementations from extending the
regular expressions grammar beyond the language specification and outside
the process. Basically, we take the ECMAScript regular expression object as
specified (minus allowing extensions) as our base line :)
Cheers,
Benji
On Mon, Jul 6, 2015 at 5:03 PM, C. Scott Ananian<EMAIL_ADDRESS>wrote:

I think it would be more worthwhile of we tried to draw a compatibility
boundary.  Taking perlre as a baseline, for example, are there additional
characters we should escape in RegExp.escape so that implementations (and
the language itself) could add more perlre features without breaking
compatibility?  The (?...) syntax (and flags) seems to be the de facto
extension point, can we protect that more narrowly?
--scott
On Jul 6, 2015 1:56 AM, "Benjamin Gruenbaum"<EMAIL_ADDRESS>wrote:

So, following work on RegExp.escape [1] I found out that implementations
may extend the regular expression grammar in JavaScript [2]. However, when
asking esdiscuss and Stack Overflow about it [2][3] it doesn't look like any
implementations currently do so (*).
Can we please forbid implementations from extending the regular
expression syntax? It seems like this could cause compatibility issues
between implementations anyway. We have subclassable RegExp with hooks and
symbols in place and implementations that want to provide an extended RegExp
can subclass RegExp or propose an extension to the language itself.
[1] https://github.com/benjamingr/RegExp.escape
[2]
https://esdiscuss.org/topic/why-are-implementations-allowed-to-extend-the-regular-expressions-syntax
[3]
http://stackoverflow.com/questions/30958288/what-ecmascript-implementations-extend-the-regexp-syntax
(*) some did it to implement ES2015 features before ES2015.

es-discuss mailing list
<EMAIL_ADDRESS>https://mail.mozilla.org/listinfo/es-discuss

This doesn't look like a big deal. It seemed like I wasn't able to get the point (forbid 'allowed extension' and ask implementations to go through the spec after they extend RegExp or do it in a subclass) across. A shame but not a big issue for this proposal - we probably shouldn't tie this proposal to it.


Formatting doesn't work when string is read from a file

Node.js version: 14.13.1
Chalk version: 4.1.0
It's entirely possible that I am missing something obvious here, but I haven't been able to figure out what it is. I have a Node.js app that reads text strings from files and outputs them to a connected client. When I output hard-coded strings, Chalk's formatting makes it through to the client just fine, but when the exact same strings are read from the file system, the raw string (including Chalk's format syntax) is displayed instead.
I have reproduced the issue with a minimal repo here.
Here is a screenshot showing what I mean.

I have done some more digging, and I am wondering if tagged templates work differently than what I'd expect. With further testing, I have verified that the following example also fails to output ansi-colored text:
const someString = 'This is a {red.bold string} with {blue.bold some color}';

console.log(chalk`${someString}`);

Is this a limitation of JS itself? Is there an alternative or workaround to be able to use chalk in this manner?

Yes, tagged templates work differently than you expected. I wouldn't call that behavior a "limitation" though. When you call a template literal such as foo`bar${baz}qux`, this is translated internally into a function call similar to foo(['bar', 'qux'], [baz]) (not exactly this, but enough for you to get an idea). Therefore, when you do chalk`${someString}`, it becomes something like chalk(['', ''], [someString]) (again, not exactly this), and by design (which I think is a correct decision) chalk only interprets "chalk commands" from within the first array (i.e. only from literal strings, not variables).

Is there an alternative or workaround to be able to use chalk in this manner?

Good question. I don't know of any, but perhaps the Chalk team would be willing to accept a feature request for an option such as { dynamicParsing: true } which would also take commands from the variables instead of literals.

We use .raw string literals, so you have to do a bit of juggling first. This is unlikely to change, but note that it's not officially supported. You're on your own with this :)
const chalk = require('chalk');
const chalkTemplate = msg => { const a = []; a.raw = [msg]; return chalk(a); };

console.log(chalkTemplate('{red hello}')); //-> '\x1b[31mhello\x1b[0m'

@Qix- is your sample code an example of what it would take to provide a purely functional API that behaves similarly to the tagged template? If so, I can add a utility to my app that does what I need.
That said, I would obviously prefer if the chalk library itself provided a functional form, but I understand if that's a direction the maintainers prefer not to go. It's one of those cases where "it's trivial to implement yourself" and "it's trivial to simply add to the library" are both valid and understandable.

I'd like to note that it isn't just strings that come from files in my case, but that is where I originally hit the issue. All of the communication between my app and the client is funneled through a socket, so I was trying to apply the tagged template inside the call to socket.write(...). I was hoping to be able to write code like client.send('some {blue.bold colorized} string') instead of client.send(chalk\some {blue.bold colorized} string`)`. The latter isn't difficult, but I expect to have a minimum of hundreds of individually colorized strings throughout my app, and it would have been nice to only need one call to chalk at the actual point where the data is sent to the client.
I'm fine adding my own wrapper for this particular use case, but wanted to point out that strings coming from files is an edge case for me as well. The primary desire was simply to allow passing raw strings around within my app and applying chalk only at the exit point.
Thanks again for your help!


PRODUCT_PATCH_VERSION=null for jdk-11.0.10+1

Windows installer failing as PRODUCT_PATCH_VERSION=null for jdk-11.0.10+1
https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_windows/9573/console

Fixed by https://github.com/AdoptOpenJDK/openjdk-build/pull/2234


Added code for Counting Sort

For short term contributors: we understand that getting your commits well
defined like we require is a hard task and takes some learning. If you
look to help without wanting to contribute long term there's no need
for you to learn this. Just drop us a message and we'll take care of brushing
up your stuff for merge!
Fixes #{299}
By submitting this pull request I confirm I've read and complied with the
below declarations.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the commit guidelines for this project.
[x] My code follows the standard code structure.
[x] This pull request has a descriptive title. For example, {Tag}: Add {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.
[x] This pull request shall only be reviewed and merged once all the checks passes. No maintainer or supporter shall be obliged to review it before this condition is met.
[x] I have mentioned the issue number correctly (with hyperlink) in this pull request description.

After you submit your pull request, DO NOT click the 'Update Branch' button.

Comment on 5e1b24b81fe312f2785bbf90aa75509108010feb, file counting_sort/cpp/Counting_sort.cpp, line 9.
Do not use variable-length arrays.  Use an appropriately named ('k' followed by CamelCase) compile-time constant for the size.  [runtime/arrays] [1]
Origin: CPPLintBear, Section: all.cpplint.

Comment on 5e1b24b81fe312f2785bbf90aa75509108010feb, file counting_sort/cpp/Counting_sort.cpp, line 24.
Redundant blank line at the end of a code block should be deleted.  [whitespace/blank_line] [3]
Origin: CPPLintBear, Section: all.cpplint.


intermittent topology update error

sometimes a topology version importing the latest changes on startup ends up being completely empty
this empty topo gets saved as the valid latest version and immediately a bunch of stuff breaks
on a subsequent startup with the latest-valid being empty, the update works ok

resolved with 1.0.5


Command display instead of execution.

Sometimes (but not always),  hstr after selecting the command and pressing Enter, it displays it (instead of running it).

@Achaean possible duplicate of #519

I also encountered this, but just generating new config into .bashrc solved it.

For me it does just nothing anymore, not even display the command. I am using zsh and made sure my config is up-to-date


Add PWA Functionality

Description
Integrate PWA functionality with Vite-PWA, which includes a service worker, is installable across platforms such as Windows, iOS, and Android, implements caching with automatic updates, cleans up outdated caches, and features automatic switching of the status bar between light and dark modes.
Necessary service worker, workbox and web manifest files are generated in build folder at build time.
Related Issue(s)
Closes #88
Checklist

[x] I have read the contribution guidelines
[ ] Suitable unit/system level tests have been added and they pass --No tests added-minimal changes
[ ] Documentation has been updated

[ ] Upgrade instructions
[ ] Configuration details
[ ] Concepts

[ ] Changes flowforge.yml?

[ ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
[ ] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

[ ] Backport needed? -> add the backport label
[ ] Includes a DB migration? -> add the area:migration label

Hi @cgjgh,
Thanks for this PR!
Recently I wanted to create a shortcut to my flowforge dashboard D2 on my Android smartphone, but there was no "Add to home screen" menu option available in Chrome.  After some searching the reason seemed to be that dashboard D2 was not a PWA...
Very useful PR!
Bart

I believe the Add to Homescreen capability was added a few weeks ago. It certainly now works for me.

Add to Home Screen option was available on iOS at least, but seemed to only make a web shortcut which ran in a full screen browser. No caching or background worker which could now be used to receive push notifications for instance.
Also I’ve frequently gotten blank white screens on launch which lasted until Safari browser cache was cleared. This pull request fixes issue.
Also Dashboard logo did not appear on installed app icon,  now present in iOS, Windows and Android.

background worker which could now be used to receive push notifications for instance

@cgjgh
Thanks for the clarification!
Don't want to go off-topic, but I am not really familiar with PWA.
I would appreciate if you could add some feedback about push notifications to this issue.  I have about 99% of my web-push ui node completed (also by registering a service worker in my own custom ui node).  But now I am a bit confused whether you mean (native) push notifications or web push notifications, why you need pwa for a service worker, and so on.  Would love to hear your thoughts in that other issue.
Thanks!!!

@bartbutenaers

But now I am a bit confused whether you mean (native) push notifications or web push notifications,

To clarify, notifications from a PWA will show up as native device push notifications, originating from and linking to PWA app, which will have its own icon and window instead of browser’s.

why you need pwa for a service worker,

As I understand service workers are not exclusive to PWAs, but rather PWAs build on top of them. PWA can also work offline, not relevant in the case of Node Red, but can help with caching to improve launch speed, providing a more native app feel. As such, they support various native functionality such as push notifications, badges on PWA icon, geolocation, biometric authentication, etc, features that are more heavily restricted on iOS requiring web app to be installed as a PWA.
Example PWA - test notifications
References
Making PWAs Installable
Caching
Notifications and Push API Example
Example Notification on lock screen

Badges on home screen icon

PWA notification settings in iOS settings

Thanks!!
Features like Geolocation, ... are of course very useful features for home automation.
I will mention you in the other issue focussed on push notifications, because I don't want to hijack your PR discussion.

I will look into the above errors later today, think some updated files were not added to commit.

The E2E Tests are now failing here in line with how they failed when I run locally. Cypress required an on load event to be fired from the page to determine that the UI has updated after a page navigation, something in these changes is preventing that event from firing.

is there a plan when this will be released? looking forward for this functionality.

is there a plan when this will be released? looking forward for this functionality.

One the E2E tests pass - waiting on @cgjgh to take a look. The service worker introduced is preventing the onLoad event firing from the browser currently.

Load event not firing seems to be an ongoing issue with service workers and Cypress as can be seen here: https://github.com/cypress-io/cypress/issues/27501.
For now the only solution seems to be to disable service worker while testing in Cypress, which I've done by intercepting request for sw.js and returning empty object preventing it from registering:
 cy.intercept('/dashboard/sw.js', {         body: undefined     })
Let me know whether you approve of this fix .

Thanks @cgjgh - re running the tests action now, I'm away on vacation until Tuesday 16th, so can do a full and proper review then.
Unless @Steve-Mcl or @sherbastian can take a look in the mean time - but no pressure to, as I'd still need to cut a release to make this available for all anyway

@joepavitt Fixed, please try again.
Sorry for all the inconveniences caused by all this back and forth.

@cgjgh Nice work, it's a lot more resilient than 'Add to Home Screen'.
Thanks for submitting.

@Paul-Reed Thanks for the feedback! May I ask what platform you're using? Haven't done any much testing on Android, just iOS and Windows. Wondering what the experience is there.

@cgjgh
I am not sure if you are following the Discourse forum, so mentioning you here.  There is a PWA related question.  Maybe it let ring some bells in your head...

@bartbutenaers it might be possible to add the pages as shortcuts in the manifest.
Here is a good article: https://medium.com/going-fullstack/adding-shortcuts-to-progressive-web-apps-53e249b06aaf

it might be possible to add the pages as shortcuts in the manifest

For me the biggest problem is that it appears not to be possible in Android to rename the shortcut on the home page.  The result is, I presume, that I will not be able tell which shortcut is for which system.  Perhaps the app name could be provided via settings. js.  It might be good to be able to change the icon too.

@Paul-Reed May I ask what platform you're using? Haven't done any much testing on Android,  Wondering what the experience is there.

Android 14 on a Pixel 6.
The Node-RED server is Oracle cloud running Ubuntu 22.04.4.
It seems much more solid than the 'web shortcut', the data is up to date as soon as it's opened, and it is framed very nicely to fit the screen.
Don't know if the 'Server disconnected' popup is part of PWA, but it's a really useful addition, and gives me greater confidence to view my data.
Don't know it it's possible, but the NR icon does not look good (especially on a dark theme), can we use our own icons?

Which version of Android are you on @colinl ? And which browser?
When I click "Add to Home Screen" I get presented with the option to name the shortcut

Don't know if the 'Server disconnected' popup is part of PWA, but it's a really useful addition

Separate addition that we put into 1.8.0
For the icon, it's not configurable at the moment, but that's partly my fault as I asked @cgjgh to change it to white background as per other icons used, we can change the default

When I click "Add to Home Screen" I get presented with the option to name the shortcut

Joe that looks as though you are creating a web shortcut & not installing the app??
In fact, just to check, I deleted my 'app', cleared the phone cache, and tried to re add it, but the option to install the app is now missing from the context menu. Something has changed...

Which version of Android are you on @colinl ? And which browser?

Android version 14. Brave and Chrome browsers.  You should not be getting the Add to Home Screen any more, as @Paul-Reed says.  However, there seems to be something odd going on. I removed all my shortcuts and the installed web app and restarted the phone. Now, when I try to open the dashboard in either browser it just appears to hang with a blank screen. I do get the Install App option on the dropdown menu though.

I do get the Install App option on the dropdown menu though.

Unfortunately the app doesn't seem to work, I just get the blank screen! So for the moment I have no access at all.

Hmm, not sure what is going on here. I think it may be to do with the fact that I am using Cloudflare ZeroTrust with Google Oauth access control. I think the reason that I was getting the blank page was that it was waiting for the authorisation. I have managed to get it working again, it will be interesting to see what happens the next time the auth times out and I need to login again with google acct.

Still working ok here.
I add the app by selecting 'add to home screen' from the context menu, that then presents the 'install app' (like the screenshot above), and then get a confirmation pop-up that the app was successfully installed.
I've just repeated the process again.

Still working ok here.

On the home screen do you see the icon with the white surround, I was getting that, but now I am not, and although it says it is installing the app I am not conviced it is, it looks just like a shortcut.  If you hold down on the icon what options do you see?  The first time I installed it I had different options, but having cleared everything and starting again I just get the App Info and Remove options like a regular shortcut.

On the home screen do you see the icon with the white surround

Yes

If you hold down on the icon what options do you see?

Joe that looks as though you are creating a web shortcut & not installing the app??
I believe that you should see this instead...

You're right, I am on 1.8.0 though, but accessing via local network - so maybe Chrome doesn't let me "install" it

Joe that looks as though you are creating a web shortcut & not installing the app??
I believe that you should see this instead...

You're right, I am on 1.8.0 though, but accessing via local network - so maybe Chrome doesn't let me "install" it

I believe it needs to be HTTPS.
If you try from a FF instance, you should see "install app" for v1.8.0 and the add shortcut is no longer offered.
That's why I suggested we could/should serve dynamic manifest with the pages offered as shortcuts. See previous comment.
As well as shortcuts, the app name should be set by the base name or some other property in the users flows. That is because if you "install" more than one dashboard site as an app, all of your application names installed on your device will all be exactly the same.

Unfortunately no, there is no option for either the name or icon.

Unfortunately no, there is no option for either the name or icon.

I asked because, at some point, I did see such an option, but I have since removed the app and now can't get it to install again. It asks if I want to install it and I say yes, but then it just comes up with the Add to Home screen options. I guess that the install is failing for some reason and it is dropping back to Add to Home Screen.  I am using https.

Have you cleared your browser cache?
On Sun, 28 Apr 2024, 13:45 Colin Law, @.***> wrote:

Unfortunately no, there is no option for either the name or icon.
I asked because, at some point, I did see such an option, but I have since
removed the app and now can't get it to install again. It asks if I want to
install it and I say yes, but then it just comes up with the Add to Home
screen options. I guess that the install is failing for some reason and it
is dropping back to Add to Home Screen. I am using https.
—
Reply to this email directly, view it on GitHub
https://github.com/FlowFuse/node-red-dashboard/pull/708#issuecomment-2081473270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHNWDGHZFUAIPC72ZH7DTDY7TVM7AVCNFSM6AAAAABFGGTG7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGQ3TGMRXGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes, it didn't seem to help. I will have to steal one of the family's phones to see if it will install there.

Not sure if this will help, but I had some strange behaviors with  version 1.8.0 as well, blank screens, etc. I updated to 1.8.1 and after uninstalling and clearing website data and cache seems to work well.
Also I tried installing Dashboard on two different Android 14 device emulators, Android 14 and 15 using both Chrome and Brave. All scenarios installed and didn't get any blank screens or anything, although I did notice that Install App option was not always immediately available, and showed instead Add to home screen which would just add a web shortcut.
Also, I noticed that it had the Chrome icon as well on app icon which is inconsistent with PWA app icon behavior.

Chrome and Android versions:

As for setting shortcut for which webpage to open, that's predetermined in the generated manifest file with "start_url":"./" ,  so can not be changed when installing.
The option @Steve-Mcl mentioned could be a workaround for now, but if PWA functionality is to be retained, I'd suggest solving this in the future by changing path in ui-base config of Dashboard 2.0, which is currently in development I understand.

I think I have worked out what is going on with the blank screen I have been getting sometimes.
As I said earlier I use Google Oauth to authenticate and Cloudflare ZeroTrust.
Before the PWA capability, if re-authentication was required, reloading the page (by swiping down in Android) attempted to reload the dashboard and I was redirected to the Google login screen by Cloudflare so I could login and then the dashboard loaded.
Now, with the PWA version, if the authentication has expired then I just get a blank screen and there does not seem to be a way of forcing a reload so I am stuck.
To recover the situation I have to browse to the node-red root url (not the dashboard) and then I get the login screen before the editor opens. Then if I go back to the dashboard application it opens ok.

It sounds like the client code needs to have something that picks up a 401 response code from a client request and triggers a standard redirect to an endpoint defined in the D2 config.

I have added issue #817 to track this problem

Is there a logic to which dashboard page is initially opened, when the 'app' is opened?
I thought it may be the page which is listed topmost in the dashboard layout config, but doesn't appear to be.

Does it open the same one as if you open it in a PC browser window?  It does for me.  There is an issue #728 (not PWA related) saying that it does not necessarily open the one at the top of the list, but I have not confirmed that myself.

Does it open the same one as if you open it in a PC browser window?

Yes, maybe just a coincidence, but the page that it always opens by default is the first page that I created after installing DB2.


dynamodb: read_items support for ScanIndexForward

Is your idea related to a problem? Please describe.
Thanks for the great resource! It'd be great if the dynamodb.read_items method could be enhanced slightly to support changing the ScanIndexForward option on the DynamoDB query call.
https://aws-sdk-pandas.readthedocs.io/en/3.7.2/stubs/awswrangler.dynamodb.read_items.html
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/dynamodb/client/query.html
Describe the solution you'd like
I'd suggest exposing a scan_index_forward boolean kwarg on the method and explicitly propagating that down into the boto3 call, but potentially you could expose boto3_additional_kwargs similar to the existing pyarrow_additional_kwargs to allow for arbitrary additional kwargs.

Adding ScanIndexForward as an argument would be relatively simple here. My concern here is that the dynamodb.read_items API is not specific to Query. It abstracts all of GetItem, Query and Scan operations. If we are to support every individual arguments, the API would quickly become overloaded. A dynamodb_kwargs argument would help but then it would require a complex logic to filter the right arguments for each underlying operation


Automate IPAM for CAPV

Now, we have parameters in cluster-vsphere for k8s API and load balancer IPs. We should automate IP management to prevent conflicts between WCs. We may implement a validation webhook with kyverno.

@jkremser after your IPAM implementation. I think we can close this ticket here?

correct, closing

for the record, it was tracked here: https://github.com/giantswarm/giantswarm/issues/27164#issuecomment-1634557687


[pt run] - System.IO.FileNotFoundException failure

ℹ Computer information

PowerToys version:
PowerToy Utility:
Running PowerToys as Admin:
Windows build number: [run "winver"]

📝 Provide detailed reproduction steps (if any)
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19041.0
IntPtr Length: 8
x64: True
Date: 09/15/2020 14:06:44
Exception:
System.IO.FileNotFoundException: C:\Users\xwg\Desktop\scrt-x<IP_ADDRESS>.2279.exe
at System.Diagnostics.FileVersionInfo.GetVersionInfo(String fileName)
at Wox.Infrastructure.FileSystemHelper.FileVersionInfoWrapper.GetVersionInfo(String path)
at Microsoft.Plugin.Program.Programs.Win32Program.ExeProgram(String path)
at Microsoft.Plugin.Program.Programs.Win32Program.GetAppFromPath(String path)
at Microsoft.Plugin.Program.Storage.Win32ProgramRepository.OnAppCreated(Object sender, FileSystemEventArgs e)
at System.IO.FileSystemWatcher.NotifyFileSystemEventArgs(WatcherChangeTypes changeType, ReadOnlySpan`1 name)
at System.IO.FileSystemWatcher.ParseEventBufferAndNotifyForEach(Byte[] buffer)
at System.IO.FileSystemWatcher.ReadDirectoryChangesCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* overlappedPointer)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pNativeOverlapped)
✔ Expected result
What is the expected result of the above steps?
❌ Actual result
What is the actual result of the above steps?
📷 Screenshots
Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

duplicate of #6425.  We already have a fix and will be rolled out in 0.23 at the end of this month


Incorrect results while using lights that don't have direct lighting baked

I have two different scenes in my project. The same scene with Day and Night modes. Now, I have placed static geometry in a Scene and created two Lighting scenes.
Lighting Scene 1:  It has the below properties
Light Type : Baked
SkyBox : Skybox_Day
Lightmap Parameters: Day_Params
Lighting Scene 2:  It has the below properties
Light Type : Mixed
SkyBox : Skybox_Night
Lightmap Parameters: Night_Params
These two scenes look different when playing them using lightmap switching tool when compared to playing them individually. Baked Light Scene looks almost similar in both cases, but Mixed Light Scene is completely different. I tried loading the Lighting Scenes in both the cases to be on the safe side, but issue persists.
I have followed the exact same procedure in ReadMe. What I am doing wrong here?

Hi,
I'm sorry that's not clear at all in the readme but the tools is made to handle only baked lighting.
It was actually made before the new mixed modes were introduced in unity and never added.
However, if you use baked indirect mixed mode, it is very simple to handle : when calling the LightingScenarioSwitcher, you need to also call the SceneManager and additively load the corresponding Lighting scene, and then when you switch lighting scenario again you need to unload that Lighting scene.
If you need shadowMask mode support you can look at :
https://github.com/laurenth-unity/lightmap-switching-tool/pull/10
This doesn't load the lighting scene either so you need to do the same thing explained above.
I hope this helps and let me know if you managed to do what you want. I'd really like to add support for this in the tool in the future but if I want to make it easy to use it'll take me some time.

Hi,
I am using Unity 5.5.4 to run my project. I have loaded and unloaded the scene while switching the scenes. But still, it is more brighter than the scene which is played normally. I guess it is due to the Indirect light bounce. There is a bit of glossiness on the ground and this really kills the view of the ambience.
I would really love to see the example of scenario mentioned in TODO - "Include an example of lighting switching with lights that have baked GI but realtime direct lighting"
Would you provide this anytime soon?  Looking forward for the same..

I think several things can still be causing different looking lighting, like the ambient probe maybe.
I have done this loading unloading once already and I know there are a lot of things that can go wrong that's why I know it'll take some time to provide an example. I don't want to promise a date I cannot hold, I can try to do an example for next week, let's see if I manage to make something usable in that time.

you can take a look at the improvements branch, I've updated it today, it's being worked on using 2017.1.2f1

and updated today again to have shadowmask mixed mode support and simplified code.

You should now be able to use realtime / mixed lighting workflows with master branch and unity 2017.x
Please let me know if you find more issues


Postgres: Sorting on localized fields returns wrong count

Link to reproduction
https://github.com/Janisvb/payload-reproduction/tree/sort-localized
Describe the Bug
When sorting on localized fields with postgres, the number of docs returned is not correct.
To Reproduce
yarn dev:postgres _community

Sort by id (correct)
http://localhost:3000/api/posts?locale=en&depth=0&limit=10&sort=id
{..., totalDocs: 100}

Sort by localized text field
http://localhost:3000/api/posts?locale=en&depth=0&limit=10&sort=text
{..., totalDocs: 200}

Sort by localized date field
http://localhost:3000/api/posts?locale=en&depth=0&limit=10&sort=date
{..., totalDocs: 5} (and only 5 docs returned)

It works as expected with MongoDB.
Payload Version
2.8.2
Adapters and Plugins
db-postgres

@Janisvb Another great bug report with recreation 🙌
This fix will be in the next release.


liborc: 0.4.16 -> 0.4.26

Motivation for this change
Upgrade to latest
Things done

[ ] Tested using sandboxing
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@FRidh: this package was a mistake, I believe. We do have this called orc, at version 0.4.26 (it's been there for years).


Windows x64 Executable Installer Creates Firewall Rules That Block Inbound TCP/UDP

Are the installer scripts available so this can be verified?

see doc/gitian-building.md for how to build Bitcoin.
I don't think this issue is a bug in the bitcoin client. When I started it I just got a request for creating such a rule. Which is normal for any (internet enabled) software running the first time on Windows.

Retried a clean install after removing all existing bitcoin related firewall rules.
No issue this time.
Not client installer related.


[fix] fix hash table insert() may be failed but not handle this error

Proposed changes
Issue Number: close #8206
Problem Summary:
fix hash table insert() may be failed but not handle this error
Checklist(Required)

Does it affect the original behavior: (No)
Has unit tests been added: (No Need)
Has document been added or modified: (No Need)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

LGTM, and please rebase to solve the conflict

Done


 is deprecated internationally.

I don't agree that the tag should be supported by the library. Instead it'd be better that  will be used to color elements.

I went with <font color="..."> to match what Html.fromHtml() and Html.toHtml() use. You can also replace that conversion with your own rule.

thx


Feat: add sequential ordering and initial backoff

This PR adds the ability to process requests in sequence and fixes issues with results not being persisted.

[x] Test sequential ordering

[ ] Decide on linkExceptionHandler logic

[ ] Add example

Update: Exponential back off has been descoped to a future PR

@smkhalsa I'm getting some naming clashes with the existing offline link, should I remove that one or namespace things inside of the new client package?

@akinsho it's actually already re(moved).
The issue is probably that since ferry is a dependency of the new package, you're not seeing the version of ferry from the PR.
I use multipack to handle this and ensure that the dependencies are all overridden.
Just activate it with:
pub global activate multipack
Then from the monorepo root directory, you can run multipack pubspec override then multipack pub get to override all the local dependencies.
 Why not create a separate link for retrying, similar to Apollo?
I presume some users will want retry logic for their Queries as well as Mutations.

@smkhalsa it's primarily because this is how I implemented it for my own project based on our needs and my PR is basically just moving that logic across. They don't have to be coupled although I don't how to split it out into a separate link i.e. how to create separate links in ferry and how one like this would work 🤔 .
It also seems like it would expand the scope of this a bit, since that would need it's own set of set of tests and examples? could that be done separately?

@smkhalsa where should the example go? atm the only example in the repo is the pokemon one which is in it's on directory. Should I just create an example flutter project within the ferry_offline_client directory?

I'd suggest putting it in the examples directory

With respect and gratitude for all the work that has been put into ferry and this PR, and acknowledging that you are busy people: Are there any plans for further work on this PR?
(I am afraid my skills and knowledge isn't at the level required to contribute with code to this PR, at least atm)

@eivihnd this is not high on my priority list, but you should be able to incorporate the ideas into your own custom link pretty easily.


how do i add a warning screen on main menu like vs tinky winky?????

What is your question?
how??????

what's VS. tinky winky? I doubt Shadow Mario has played that, let alone anyone else I know. Warning screens are already in base psych engine, in what state do you want it? (MainMenuState, PlayState, e.t.c)

what's VS. tinky winky? I doubt Shadow Mario has played that, let alone anyone else I know. Warning screens are already in base psych engine, in what state do you want it? (MainMenuState, PlayState, e.t.c)

the vs tinky winky mod made by bonespook https://gamebanana.com/mods/309180
the mod uses kade. i want to know how to add the loading screen to psych engine..

Simple. before compiling, locate Project.xml, and delete this on line 65: <define name="PRELOAD_ALL" unless="web" />.
When deleting this line, the game will compile without "preloading" defined; it will use loadingState.hx that's usually specific to web.

Simple. before compiling, locate Project.xml, and delete this on line 65: <define name="PRELOAD_ALL" unless="web" />. When deleting this line, the game will compile without "preloading" defined; it will use loadingState.hx that's usually specific to web.

will it show the warning screen image i made?

I was on campus for a bit. You either have to replace funkay.png with your image of choice, or change what filename it should look for.


Typing inline_script does not show autocomplete

Could be useful to have an autocomplete snippet for it to easily write it, since most type you have to type inline_script manually, speeding up the insertion of inline scripts in most other places.

So the question is 'What are the all available places', should it can be autocompleted everywhere in script files (in game/mod directory) when typing a proeprty key, or be limited?

It's originally designed not to complete 'inline_script = ...', yet it may be coonfigured to complete.

Will be implemented in 1.3.5


Fix bug in font-loader where woff2 is not matched

Fixes a bug in the font-loader configuration where woff2 is never matched.

Coverage remained the same at 100.0% when pulling 88ddeba9759963ff9e440e8a162d45bf9ed13bcd on daveish:fixFontLoaderConfig into d54858f1dcb3cb61b719c7521c3151fcf0ec9cc1 on react-boilerplate:dev.

Never mind, sorry.


fix profiler

Fix using add_pathlist_to_PYTHONPATH in profilergui.py
This function was moved to utils/misc in commit 252c9adc49

Thanks a lot @Qlogin!!


WebAssembly.Table.get(): invalid index 584944 into funcref table of size 1000

I updated all my npm dependencies and encountered this issue, I can't tell why it happens
Uncaught (in promise) RangeError: WebAssembly.Table.get(): invalid index 584944 into funcref table of size 1000
    at ie (jassub-worker.js:2:9156)
    at Wr (jassub-worker.js:15:9810)
    at jassub-worker.wasm:0xa18b4
    at jassub-worker.wasm:0xa68eb
    at jassub-worker.wasm:0xea152
    at Dr (jassub-worker.js:15:10018)
    at jassub-worker.js:15:10373

Here is the context, since the stack trace is probably not that helpful:
	function xt(t, r, n) {
        f.hasOwnProperty(t) || ge("Replacing nonexistant public symbol"),
        f[t].overloadTable !== void 0 && n !== void 0 ? f[t].overloadTable[n] = r : (f[t] = r,
        f[t].argCount = n)
    }
    function Lt(t, r, n) {
        var i = dynCalls[t];
        return n && n.length ? i.apply(null, [r].concat(n)) : i.call(null, r)
    }
    var be = [];
    function ie(t) {
        var r = be[t];
        return r || (t >= be.length && (be.length = t + 1),
        be[t] = r = ue.get(t)), // Here
        r
    }
    function Ht(t, r, n) {
        if (t.includes("j"))
            return Lt(t, r, n);
        var i = ie(r).apply(null, n);
        return i
    }
    function Bt(t, r) {
        var n = [];
        return function() {
            return n.length = 0,
            Object.assign(n, arguments),
            Ht(t, r, n)
        }
    }

After searching a bit, it seems that the error is really similar to this one: https://github.com/jellyfin/jellyfin-web/issues/4794 but on a modern version of chrome/firefox:
Chrome version: Version 117.0.5938.149
Firefox version: Version 118.0.1
If you need more context for this, you can take a look at this branch where I updated packages: https://github.com/zoriya/Kyoo/compare/master...fix/things

I have no clue, that's compiled code that's throwing the error, reproduction steps would be better

Turns out this happens for any next 14 application, I don't know if I bundle jassub wrong or what they changed between version 13 and 14 to make this bug appears but here is a minimal reproduction repo: https://codesandbox.io/p/sandbox/elastic-antonelli-qrjfj8
That's simply a next-js template with a jassub component in index.tsx and it is bundled via a copy-weback-plugin (since import.meta.url is not available on next nor are import "file?url")

I'm fairly sure next is gonna be to blame here?
Try reproducing this statically without NextJS

I am totally sure that Next is to blame but it's not like I can remove it so I would like to make this work. Do you have an idea how to proceed to debug this? I don't think I did anything wrong with how jassub is served or initialized.
Do you have some debugging steps I could take to pinpoint the issue?

man you'll be happy to hear this: try 1.7.11

fixed in 1.7.11, thanks for the report, I have no clue how I overlooked this!!!

I think we were both waiting for the CI x) Thanks for the quick fix!


PostChanges()  timeout  not  occur

postChanges()  call does never return, seems to hang forever  even the timeout duration is reached.
I have following function in my  client code to run  postChanges() in an endless loop

function setupFollow(seq) {
 try {
     db.postChanges({"db":self.databaseName  "feed":"longpoll","timeout": 60000,"since": seq,"includeDocs" : true })
     .then(response => {
          logger.info(method,  numOfChangesDetected + " changes records received from configDB with last seq : ", lastSeq);
          ........
          setupFollow(lastSeq)
     .catch( (err) => {
                logger.error(method, "Failed to read trigger config info in configDB with  error : ",err);
                //** Continue to try to read from configDB after a retry wait time  with initial seq_nr
                setTimeout( () => {setupFollow( seq );}, retryDelay );
                logger.error(method, ": Error while read on provider DB : " + err , "will retry to read in ", retryDelay, " seconds");
     })
 } catch (err) {
    logger.error(method, ": Error in setting up change listener on provider DB : " + err , "will retry to read in 3 seconds");
    //** Continue to try to read from configDB after a retry wait time  with initial seq_nr
    setTimeout( () => {setupFollow( seq );}, 1000 );
 }
}

Error situation:  The logs over days show, that the setupFollow() is called in a loop. But then it  stopped  at one single call:
logline:
Dec 18 12:06:15 alarmstrigger-01-worker-76f44f7cc9-4dllr alarmstrigger-01-worker INFO [??] [alarmsTrigger] [setupFollow] Next trigger configDB read sequence starts on : [ 1520029-g1AAAAObeJzLYWBg4MhgTmFQTklKzi9KdUhJMtZLytUtz8gszjYwNNJLzskvTUnMK9HLSy3JASpmSmRIkv___39WBnMSA9Mjs1ygGHtqWpKhaXIycaaQZFuSApBMsodbeF8bbKGZgVlKmoUJLSx0AFkYD7fwwzqwhRYmhmkWaea0sDABZGE9wocPwBYam5ilJial0MDCPBYgydAApIB2zodY-rYabKmJpamZRWoizSxdALF0P8TSF1fBlqZYGBgYpSbRzNIDEEvvQyx9ehliqUmyqaWRGc0sfQCxFBqnj7shwWtumJiUbECcYVkABNIoEQ ]
Investigtion  on cloudant DB server side showed that the  HTTP reqeust for   SeqNr:  1520029-  did not reached server.
Dec 18 12:06:14 lb2.bm-whisk012 haproxy[26686]: <IP_ADDRESS>:36817 -> since=1520027-g1AAAAObe
Dec 18 12:06:15 lb2.bm-whisk012 haproxy[26686]: <IP_ADDRESS>:36817 -> since=1520028-g1AAAAObe

Question:  Is there a known  or possible error case in the  postChanges() call that is suppressing the timeout

This repository is a container for documentation that is common to IBM Cloud client SDKs produced with the IBM Cloud SDK Generator.
This issue seems like you are encountering an issue with a specific service and/or operation.  Please open an issue against the specific SDK that you are using.

Sorry, wrong repo


add part 16. Build the hive modules for QAT in docs

@ZJie1 could you change the format to MD file extension instead of PDF? It's not able to be updated.

Ok, I will change the format.

Thanks @ZJie1 . We only need to update README section https://github.com/Intel-bigdata/IntelQATCodec/blob/master/README.md about how-to-use. For design doc, it's optional.


Cool, but

I couldn't find docs on something as simple as defining what an app's name will be for make command. In contrast, electron-builder make it obvious right away, and I don't have to dig through source code.

At least for v6 the packager config options are documented in the "Configuration" section of the docs
https://v6.electronforge.io/configuration
Is there a lead in missing there that would point you in that direction?

For electron-packager, for example, first thing in the usage section:

electron-packager <sourcedir> <appname> --platform=<platform> --arch=<arch> [optional flags...]

and further down in the README:

electron-packager will do the following:

Use the current directory for the sourcedir
Infer the appname from the productName in package.json

So, just wanted to let you know that even though this looked cool, I chose not to use forge because it purveyed a more difficult experience due to missing some details that are probably very easy to document.

Ah, well, I clicked on https://electronforge.io on the GitHub page! That may be the cause!
Anywho, this looks awesome, just needed better docs, which I didn't find at first (thanks for showing the new link, you should definitely publish it).

@trusktr Ah I see, we're going through a pretty hefty rewrite at the moment which massively addresses things like documentation and getting started even quicker.
If you check out the v6 site you should find it a whole bunch better (and find some cool new features we added in 6)

We're going to publish the v6 site when Forge v6 is out of beta.
@MarshallOfSound I wonder if it would be worth adding a small "preview" link to the v6 site from the v5 site.

for anyone landing here in 2024 and beyond:
Forge uses electron-packager so the "For electron-packager," example that @trusktr shared is the answer here.


bump Go vertion to 1.22

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (9a3483d) 97.26% compared to head (7ab47b8) 83.21%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #130       +/-   ##
===========================================
- Coverage   97.26%   83.21%   -14.05%
===========================================
  Files          35       48       +13
  Lines        1315     1537      +222
===========================================
  Hits         1279     1279
- Misses         24      246      +222
  Partials       12       12

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


Data for Examples

Determine how best to help users get the data for the examples. Also include better instructions.
Include background and region file.

I've also changed the data :D It now is only 860 MB and requires a simple copy and paste into the terminal. Can we close this? @jgcovi

yayyy let me look at how it works, but if the data is smaller and more easily available (ie. example data) then yeah, I think that constitutes as closed