fix(hmr): client pinging behind a proxy on websocket disconnect (fix #4501)

Description
When running the Vite dev server behind a proxy, the fetch request results in a 502 status code. This 502 does not throw an error, triggering the catch statement. Instead, the loop breaks (because of the break statement on the next line).  When it breaks, the page reloads, but it cannot load because the proxy server is down. This causes those of us working behind proxies to lose frontend application state whenever the proxy restarts.
Additional context
https://github.com/vitejs/vite/issues/4501
For my team, this occurs frequently because the proxy is a part of our API code - so whenever we are doing backend work and we need to restart our local API server, our frontend application loses state because the window reloads and can't connect to the proxy.

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

Our team experienced the same issue, we are running our vite development environment on k8s with using devspace. When we are replacing our common JS dependencies for development we are automatically restarting the whole node/vite process since the required optimizeDeps is not working without restarting vite.
During the restart the k8s load balancer returns status code 502 for a few seconds but the browser reloads already the page even if the vite process isn't up and running. A few more retries / waiting time would result in a better development experience inclusive checking the return code.

In our last meeting we discussed that someone (hopefully from the community) with a matching environment should test this and report if everything worked.
If so, it is okay to get merged.

@mwarnerdotme would you run pnpm run format? thanks

@mwarnerdotme would you run pnpm run format? thanks

done!

@wuxiaolin1949 @BirknerAlex could you confirm that this PR works for your setup, we can merge it if this is the case

@wuxiaolin1949 @BirknerAlex could you confirm that this PR works for your setup? We can merge it if this is the case

Yes


Downport issue: CL_OO_CLASS_SECTION_SOURCE constructor parameters

System NW 7.30 SP12
abapGit 1.67.0
CL_OO_CLASS_SECTION_SOURCE constructor is called with
>>>>>	    CREATE OBJECT lo_update TYPE ('CL_OO_CLASS_SECTION_SOURCE')
27949	      EXPORTING
27950	        clskey                        = ls_clskey
27951	        exposure                      = iv_exposure
27952	        state                         = 'A'
27953	        source                        = it_source
27954	        suppress_constrctr_generation = seox_true
27955	      EXCEPTIONS
27956	        class_not_existing            = 1
27957	        read_source_error             = 2
27958	        OTHERS                        = 3.

In 7.30 it only has parameters
CLSKEY
EXPOSURE
STATE

and exceptions
CLASS_NOT_EXISTING
READ_SOURCE_ERROR

so
source
suppress_constrctr_generation

are a problem.
When importing a zip into an offline project with a modified source path to / the import starts, but then hits the following issue and dumps.
The zip file is here: https://open.sap.com/files/f94c899c-62ae-4c79-81ff-c05d3b44c390
Category	              	ABAP Programming Error
Runtime Errors	         	DYN_CALL_METH_PARAM_NOT_FOUND
Except. 	               	CX_SY_DYN_CALL_PARAM_NOT_FOUND
ABAP Program 	          	ZABAPGIT
Application Component  	Not Assigned
Date and Time 	         	24.05.2018	 	08:58:16

Short text
    	In a dynamic method call the formal parameter could not be found.

What happened?
    	Error in the ABAP application program.

    	The current ABAP program "ZABAPGIT" had to be interrupted because it contains
    	a statement that cannot be executed.

Error analysis
    	An exception occurred that is explained in detail below.
    	The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
    	 not caught in
    	procedure "UPDATE_META" "(METHOD)", nor was it propagated by a RAISING clause.
    	Since the caller of the procedure could not have anticipated that the
    	exception would occur, the current program is terminated.
    	The reason for the exception is:
    	The formal parameter "SOURCE" could not be found in method "CONSTRUCTOR" of
    	 class "CL_OO_CLASS_SECTION_SOURCE".

Missing RAISING Clause in Interface
    	Program                                 	ZABAPGIT
    	Include                                 	ZABAPGIT
    	Row                                     	27.940
    	Module type                             	(METHOD)
    	Module Name                             	UPDATE_META

27940	  METHOD update_meta.
27941
27942	    DATA: lo_update     TYPE REF TO cl_oo_class_section_source,
27943	          ls_clskey     TYPE seoclskey,
27944	          lv_scan_error TYPE seox_boolean.
27945	    ls_clskey-clsname = iv_name.
27946
27947	* todo, downport to 702, see https://github.com/larshp/abapGit/issues/933
>>>>>	    CREATE OBJECT lo_update TYPE ('CL_OO_CLASS_SECTION_SOURCE')
27949	      EXPORTING
27950	        clskey                        = ls_clskey
27951	        exposure                      = iv_exposure
27952	        state                         = 'A'
27953	        source                        = it_source
27954	        suppress_constrctr_generation = seox_true
27955	      EXCEPTIONS
27956	        class_not_existing            = 1
27957	        read_source_error             = 2
27958	        OTHERS                        = 3.
27959	    IF sy-subrc <> 0.
27960	      zcx_abapgit_exception=>raise( 'error instantiating CL_OO_CLASS_SECTION_SOURCE' ).
27961	    ENDIF.
27962
27963	    lo_update->set_dark_mode( seox_true ).
27964	    TRY.
27965	        CALL METHOD lo_update->('SET_AMDP_SUPPORT')
27966	          EXPORTING
27967	            enabled = abap_true.

Is this duplicate? https://github.com/larshp/abapGit/issues/1366

duplicate, closing


Update transmission-remote-gui to 5.0.1

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 5a2fe8eedb5e620f87313d6e142aee1653788b6e. Your contribution is still credited to you.


Runtime error with ApolloClient.Utilities.getOperationDefinition function

Hello
Once again many thanks for your great bindings. 👏🥳
I am currently experiencing a bug in the use of the ApolloClient.Utilities.getOperationDefinition function.
let terminatingLink = ApolloClient.Link.split(~test=({query}) =>
  switch ApolloClient.Utilities.getOperationDefinition(query) {
  | Some({kind, operation, name: {value}}) =>
    kind === "OperationDefinition" &&
    operation === "query" &&
    value->Js.String2.startsWith("Analytics")
  | _ => false
  }
, ~whenTrue=httpAnalyticsLink, ~whenFalse=httpGatewayLink)

It creates an error if I have a graphql query that takes this form (no operation name).
query ($id: ID!) {
  user(id: $id) { ... }
}

In this cas, the name property is undefined. So it is not possible to access value property.
So I applied this patch ⬇
diff --git a/node_modules/rescript-apollo-client/src/graphql/language/ApolloClient__Graphql_Language_Ast.res b/node_modules/rescript-apollo-client/src/graphql/language/ApolloClient__Graphql_Language_Ast.res
index 1c007fa..80f26c6 100644
--- a/node_modules/rescript-apollo-client/src/graphql/language/ApolloClient__Graphql_Language_Ast.res
+++ b/node_modules/rescript-apollo-client/src/graphql/language/ApolloClient__Graphql_Language_Ast.res
@@ -172,7 +172,7 @@ module OperationDefinitionNode = {
   type t = {
     kind: string,
     loc: option<Location.t>,
-    name: NameNode.t,
+    name: option<NameNode.t>,
     operation: OperationTypeNode.t,
     variableDefinitions: option<array<VariableDefinitionNode.t>>,
     directives: option<array<DirectiveNode.t>>,

And change that ⬇
let terminatingLink = ApolloClient.Link.split(~test=({query}) =>
  switch ApolloClient.Utilities.getOperationDefinition(query) {
-  | Some({kind, operation, name: {value}}) =>
+  | Some({kind, operation, name: Some({value})}) =>
    kind === "OperationDefinition" &&
    operation === "query" &&
    value->Js.String2.startsWith("Analytics")
  | _ => false
  }
, ~whenTrue=httpAnalyticsLink, ~whenFalse=httpGatewayLink)

Do you need a pull request?
Greetings from France 🇫🇷
Léo

Thanks! I checked the types and clearly just an oversight on my part. I'm going to make a PR here shortly anyway, so I'll include this.

Resolved in #136

Thanks !! 🎅:evergreen_tree:


Font module breaks build: "cannot find zipfile directory" for google fonts

I've been having this issue pop up intermittedly on my personal builds (see https://github.com/michaelhaaf/bluebuild-custom/actions/runs/8462707712/job/23184496580). I also saw someone on the Discord with the same issue, which I'll paste the log from:
Installation of google-fonts started
Downloading Roboto Open Sans.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1642    0  1642    0     0  13197      0 --:--:-- --:--:-- --:--:-- 13136
100  1642    0  1642    0     0  13185      0 --:--:-- --:--:-- --:--:-- 13136
Warning: Got more output options than URLs
Archive:  Roboto Open Sans.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of Roboto Open Sans.zip or
        Roboto Open Sans.zip.zip, and cannot find Roboto Open Sans.zip.ZIP, period.
Error: building at STEP "RUN --mount=type=tmpfs,target=/tmp --mount=type=tmpfs,target=/var --mount=type=bind,from=docker.io/mikefarah/yq,src=/usr/bin/yq,dst=/usr/bin/yq --mount=type=bind,from=stage-config,src=/config,dst=/tmp/config,rw --mount=type=bind,from=stage-modules,src=/modules,dst=/tmp/modules,rw --mount=type=bind,from=stage-exports,src=/exports.sh,dst=/tmp/exports.sh --mount=type=cache,dst=/var/cache/rpm-ostree,id=rpm-ostree-cache-os-image-39,sharing=locked chmod +x /tmp/modules/fonts/fonts.sh   && source /tmp/exports.sh && /tmp/modules/fonts/fonts.sh '{"type":"fonts","fonts":{"nerd-fonts":["FiraCode","NerdFontsSymbolsOnly"],"google-fonts":["Roboto","Open Sans"]}}'": while running runtime: exit status 9

Not sure why the issue doesn't happen all time, which makes it tricky to reproduce (though: I haven't actually set up the local bluebuild-cli properly yet, which doesn't help, lol).
I can't see an obvious problem with the google font module code, though it has some differences from the nerd font module code.
I hope to have time in the near future to set up a local build process and investigate this myself, but thought I'd raise the issue in the meantime in case anyone already knows why this might be happening.

The font module is due to be refactored. Let us just hope that the refactor will not repeat these bugs...

I think that this bug is related to the usage of older BlueBuild GitHub action.

Thanks for the help everyone.
Seems unrelated, but since updating to github action 1.2 I'm getting a different blocking error.
I had thought it may be module order (something like, modules that depend on the existence of /usr/ weren't working since my files module wasn't running first) but I've ruled that out
#33 [stage-4  6/15] COPY ./config/files/usr /usr
#33 ERROR: cannot copy to non-directory: /var/lib/docker/overlay2/yggvj9u0in8wk3ivzrfnhfk2y/merged/usr/local
------
> [stage-4  6/15] COPY ./config/files/usr /usr:
------
Containerfile:41
--------------------
  39 |     COPY --from=docker.io/mikefarah/yq /usr/bin/yq /usr/bin/yq
  40 |     COPY --from=ghcr.io/blue-build/cli:latest-installer /out/bluebuild /usr/bin/bluebuild
  41 | >>> COPY ./config/files/usr /usr
  42 |     RUN \
  43 |       --mount=type=tmpfs,target=/tmp \
--------------------
ERROR: failed to solve: cannot copy to non-directory: /var/lib/docker/overlay2/yggvj9u0in8wk3ivzrfnhfk2y/merged/usr/local
[2024-03-28T15:28:51Z ERROR blue_build::commands] Failed to build ghcr.io/michaelhaaf/sway:39

I think that this bug is related to the usage of older BlueBuild GitHub action.

I had this same issue with the fonts module happen in my builds today, on the latest version of the Github action.

When you were previously a fork & then you detached it when migrating to BlueBuild, you would still need to manually enable Dependabot to notify for Action updates, as Dependabot is not automatically enabled for forks.

How do you do that?

I had this same issue with the fonts module happen in my builds today, on the latest version of the Github action.

I'm on 1.2 and it's happening for me as well

It looks like the download url changed on Google's side.
Module url: https://fonts.google.com/download?family=
New url: https://fonts.google.com/download/list?family=

Commented on the PR. I am now getting the same error too. Not available for long today, but will be back tomorrow.
https://github.com/xynydev/linuXYZ/actions/runs/8471125178/job/23210416658

Commented on the PR. I am now getting the same error too. Not available for long today, but will be back tomorrow.
https://github.com/xynydev/linuXYZ/actions/runs/8471125178/job/23210416658

@xynydev you're right, my proposed URL fix is incorrect. It does seem like something changed on my end though. I'll try to investigate further later on.

How do you do that?

@m0ngr31 Go to your repo, Dependencies tab, Dependabot tab, Recent update jobs
Then it should ask you to enable Dependabot or not.


stdenv unpacking: Preserve timestamps when copying files breaks zipfiles

Eelco reverted a fix for <1980 dates issue in zip files. See https://github.com/NixOS/nixpkgs/commit/f4553d721972e6a437c9f367af2bb0967b773998
Example package: pythonPackages.gyp
Possible fix: https://github.com/triton/triton/commit/52f9121ffbe37f405d9f41a9d5dc4ae884fc652a

Maybe we can fix zip?

Canonicalising to 2000 seems confusing to me since we're already canonicalising to 1970 in other places.

The supported range seems from 1980 for 128 years. Theoretically, we could change the semantics, e.g. "wrap" the last 10 years into the 1970-80 period, preserving compatibility on the overlapping 118 years.

This seems to cause thousands of broken builds on staging, mainly because of python tests failing. @domenkozar: do you know what the tests are trying to achieve? Zipping up the build directory?

@vcunat tests are due to setuptools bump, which forces tests to be ran even if they don't exist. This is an issue on Python 3.x.
The failures with this change are related to our installation method using wheels. Basically we create a wheel (zip file) and then install it. That's the preferred Python way of doing binary installs. As an example see http://hydra.nixos.org/build/31373731/nixlog/1/raw

I really wouldn't go and fix zip. Guix folks are doing a very similar thing: https://lists.gnu.org/archive/html/guix-commits/2015-07/msg00462.html

Yeah, probably some similar solution.

Any arguments against this solution: d7b59519f6? (@edolstra mainly, I suppose)


Fix: Preserve signature in PNG palette images during transformation

Before this change, when transforming PNG palette images (with transparency), the signature would be lost, and the resulting image would become fully transparent. This PR ensures that the signature is preserved during transformations, keeping it visible while maintaining the transparency of the image.
Screenshots:

Original Image (before transformation):

Image Before Fix (signature lost after transformation):

Image After Fix (signature preserved):

Thank you! It seems that the tests are failing. Could you take a look?

Thank you for bringing this up!
All tests pass locally with my Lando config:
name: spatieimage
recipe: lamp
config:
  webroot: .
  php: "8.2"
services:
  appserver:
    build_as_root:
      - apt-get update

      # Install NodeJS
      - curl -sL https://deb.nodesource.com/setup_20.x | bash -
      - apt-get install -y nodejs

      # Install dependencies needed for optimizers and PHP extensions
      - apt-get install -y jpegoptim pngquant gifsicle optipng libjpeg-progs webp libavif-bin

It seems that my local environment is not generating the same snapshots as required by GitHub Actions.
@freekmurze, could you help me investigate this? I haven’t been able to pinpoint the issue.


Something wrong with example 37

Maybe something wrong with Example 37 in my PC (Windows 10 64bit/ GeForce GTX 1050 Ti)

And Segmentation fault when I close the window, the traceback is
Thread 1 received signal SIGSEGV, Segmentation fault.
0x00007fff3f255e8a in d3d11!D3D11CoreRegisterLayers () from /c/WINDOWS/SYSTEM32/d3d11.dll
(gdb) bt
#0  0x00007fff3f255e8a in d3d11!D3D11CoreRegisterLayers () from /c/WINDOWS/SYSTEM32/d3d11.dll
#1  0x00007fff3f2254f9 in d3d11!D3D11On12CreateDevice () from /c/WINDOWS/SYSTEM32/d3d11.dll
#2  0x00007fff3f236979 in d3d11!D3D11On12CreateDevice () from /c/WINDOWS/SYSTEM32/d3d11.dll
#3  0x00007fff3f2535c8 in d3d11!D3D11CoreRegisterLayers () from /c/WINDOWS/SYSTEM32/d3d11.dll
#4  0x00007fff3f236958 in d3d11!D3D11On12CreateDevice () from /c/WINDOWS/SYSTEM32/d3d11.dll
#5  0x00007fff3f2368f9 in d3d11!D3D11On12CreateDevice () from /c/WINDOWS/SYSTEM32/d3d11.dll
#6  0x00007fff3f2535b2 in d3d11!D3D11CoreRegisterLayers () from /c/WINDOWS/SYSTEM32/d3d11.dll
#7  0x00007fff3f23b434 in d3d11!D3D11On12CreateDevice () from /c/WINDOWS/SYSTEM32/d3d11.dll
#8  0x00007fff3f23b364 in d3d11!D3D11On12CreateDevice () from /c/WINDOWS/SYSTEM32/d3d11.dll
#9  0x00007fff3f23b200 in d3d11!D3D11On12CreateDevice () from /c/WINDOWS/SYSTEM32/d3d11.dll
#10 0x000000000060f0ec in bgfx::d3d11::RendererContextD3D11::shutdown (this=0x20e9e040)
    at ../../../src/renderer_d3d11.cpp:1970
#11 0x00000000005fe053 in bgfx::d3d11::rendererDestroy () at ../../../src/renderer_d3d11.cpp:3976
#12 0x00000000005961ed in bgfx::rendererDestroy (_renderCtx=0x20e9e040) at ../../../src/bgfx.cpp:2165
#13 0x0000000000633989 in bgfx::Context::rendererExecCommands (this=0x1ca5b080, _cmdbuf=...)
    at ../../../src/bgfx.cpp:2236
#14 0x000000000062e24b in bgfx::Context::renderFrame (this=0x1ca5b080, _msecs=5000)
    at ../../../src/bgfx.cpp:1861
#15 0x000000000058c0df in bgfx::renderFrame (_msecs=-1) at ../../../src/bgfx.cpp:1088
#16 0x000000000069a4a4 in entry::Context::run (this=0x88d3e0 <entry::s_ctx>, _argc=1, _argv=0x1c1db0)
    at ../../../examples/common/entry/entry_windows.cpp:531
#17 0x00000000007ae82a in main (_argc=1, _argv=0x1c1db0)
    at ../../../examples/common/entry/entry_windows.cpp:1148

+1
https://youtu.be/G6UYqtOACIk

I still need to reproduce this, but in mean time to eliminate driver issue, check your drivers, and update to the latest.

@bkaradzic you didn't get this issue? Will look into upgrading the driver when I get home

I update my nvidia driver from 387.95 to 391.01 (latest version) today, but the issue still exists :(


gx publish 0.0.19

Coverage increased (+4.1%) to 91.781% when pulling 39a79707fd205f45975b3d9fd0d5a3785613fa58 on gx/update-libp2p into 9e734e5b4c602a626fcbab4c3e071a05f88fe7c0 on master.


how get docker registry2.0 source code?

how get docker registry2.0 source code?

@blackfader just look here https://github.com/docker/distribution

Correct, the registry 2.0 source code is in the https://github.com/docker/distribution repository.

thinks

and registry2.0 now support proxy or cache model？


updated to work with new versions of kafka

will now work with any version that has a compatible api, uber jar excludes kafka so it wont conflict with the classpath when added to the lib dir.

Sorry i totally missed this one.


Use the delete key to remove history items

I propose the delete key as a shortcut to delete the selected history item.

Delete key is required for mini-editor .

I think you are confusing the delete key with backspace. Probably you are using a Mac and as I see from a google image search they don't have a delete key and sometimes they label backspace key as delete. So yeah, I meant "the other" delete key.
I'm not familiar with atom internals, can I map delete item action to a key in keymap.cson? If yes then I will do that if not then I would like to reopen this ticket.
Cheers.


Fix building AWS SDK for C++  with CMake 3.22.0

Describe the pull request

What does your PR fix?
Fixes https://github.com/aws/aws-sdk-cpp/pull/1810

Which triplets are supported/not supported?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Can you please also report this bug to the upstream?
Thanks.

~Can you please also report this bug to the upstream?~ Ah already have a upstream PR.
Thanks.

I even created a ticket https://github.com/aws/aws-sdk-cpp/issues/1820

Please remember that port aws-sdk-cpp needs an update (1.9.96 -> 1.9.152).

@dg0yt We can accept this then remove the fix patch in the next release.

Thanks for the patch!

(And for following up with upstream!

Please remember that port aws-sdk-cpp needs an update (1.9.96 -> 1.9.152).

Amazon rarely, if ever, merges user contributions. I have a couple of PR's hanging there for more than a year already!

Amazon rarely, if ever, merges user contributions. I have a couple of PR's hanging there for more than a year already!

That's a good reason to apply patches. We still usually want upstream to have a first say on any changes since anything we patch looks like it comes from upstream; this is the source of most of our guidelines regarding patches (e.g. the ban on implementing features).
If they've had an opportunity to look at a build fix for a while and haven't responded as long as the thing has actually been filed with them and they've had the opportunity, that's fine.


YARN-11298. Improve Yarn Router Junit Test Close MockRM.

JIRA: YARN-11298. Improve Yarn Router Junit Test Close MockRM.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m 18s

trunk passed

+1 :green_heart:
compile
0m 48s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 39s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 44s

trunk passed

+1 :green_heart:
mvnsite
0m 51s

trunk passed

+1 :green_heart:
javadoc
0m 56s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 36s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 16s

trunk passed

+1 :green_heart:
shadedclient
20m 33s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 27s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
compile
0m 27s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 27s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 23s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-router.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router: The patch generated 3 new + 0 unchanged - 0 fixed = 3 total (was 0)

+1 :green_heart:
mvnsite
0m 28s

the patch passed

+1 :green_heart:
javadoc
0m 24s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 27s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
0m 56s

the patch passed

+1 :green_heart:
shadedclient
20m  9s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 40s

hadoop-yarn-server-router in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

96m 43s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4870/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4870

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 7193681d9c05 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 575e3aaf85feb9810d59bad574e9682ffb3d8403

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4870/1/testReport/

Max. process+thread count
727 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4870/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

@goiri Please help to review the code, thank you very much!

@goiri Thank you very much for your help reviewing the code!


Unable to run format due to missing flag

When trying to format some documents the extension provides two error boxes:

SQLFluff templating/parsing errors found
Fix aborted due to unparseable template variables. Use --FIX-EVEN-UNPARSABLE' to attempt to fix the SQL anyway

I am currently using it with the dialect redshift and Linter:Run onType, I think that's all the changes I have in the config.
Is there a way to add the flag in the settings json? I haven't found any in the docs.

You could try setting the sqlfluff.ignoreParsing setting to true. If that doesn't work, try setting the sqlfluff.executablePath to include that flag. For example, sqlfluff.executablePath = "sqlfluff --FIX-EVEN-UNPARSABLE".
Let me know if either of those options works for you, if not I can add a setting to allow you to pass in arguments manually.

I've just tried both, restarting vscode after each change just to be on the safe side.
The sqlfluff.ignoreParsing lead to the same result, changing the executable path to add the flag resulted in the following error The sqlfluff executable was not found. Use the 'Executable Path' setting to configure the location of the executable, or add it to your PATH..  I've tried running the path without the flag and it seems to be ok.

I've updated to v0.1.4 and set the option in the settings.json as "sqlfluff.format.arguments": ["--FIX-EVEN-UNPARSABLE"], . However I am still getting the same error box (Fix aborted due to unparseable template variables. Use --FIX-EVEN-UNPARSABLE' to attempt to fix the SQL anyway). Maybe I have something else not properly set?
My other sqlfluff related config is:
    "sqlfluff.rules": [

    ],
    "sqlfluff.executablePath": "/Users/pau/miniconda3/bin/sqlfluff",
    "sqlfluff.excludeRules": [

    ],
    "files.associations": {
        "*.sql": "jinja-sql"
    },
    "sqlfluff.dialect": "redshift",
    "sqlfluff.ignoreParsing" : true,
    "sqlfluff.format.arguments": ["--FIX-EVEN-UNPARSABLE"],
    ```

Can you check the output tab and look at the SQLFluff channel. This will tell you the exact command it is executing when the formatting is taking place. Copy that command and try running it in the terminal and see if the output is the same. If the "--FIX-EVEN-UNPARSABLE flag is not there add it and see if that works on the terminal.

The output tab does have the flag, it does not have the path to the file it's trying to format (although the file content is in the output tab) and the command finishes with a - :

--------------------Executing Command--------------------

/Users/pau/miniconda3/bin/sqlfluff fix --force --FIX-EVEN-UNPARSABLE --dialect redshift --ignore parsing -

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

However I tried running /Users/pau/miniconda3/bin/sqlfluff fix path_to_file.sql  --force --FIX-EVEN-UNPARSABLE --dialect redshift --ignore parsing and it did work, formatting the file (with some unfixable stuff showing a WARNING    One fix for L005 not applied, it would re-cause the same error.                                                                                in the terminal output)

The command finished with - because I am letting sqlfluff know that it needs to format using stdin content, which I pass in after executing that command. I wonder if it won't work because of the warnings? I'm not sure. I can try to look into this more when I have some time, but that might be a while.
For now, could you try setting "sqlfluff.experimental.format.executeInTerminal": true,. That forces the extension to pass in the file path instead of using stdin, but can come with some drawbacks as editing the file while the formatting is taking place causes an issue, but that is not too big of a deal. I'm hopeful that this would at least do the formatting though.


Update farsi quotes

Fixed minor typos, added more quotes.

Current coverage is 98.41% (diff: 100%)

Merging #59 into master will not change coverage

@@             master        #59   diff @@
==========================================
  Files            26         26
  Lines          1448       1448
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1425       1425
  Misses           23         23
  Partials          0          0

Powered by Codecov. Last update 7a2ebfd...d6157cb

@lk-geimfari If you could please merge it before we run into conflicts again, that'd be great.

@aminalaee Thank you!


[WFLY-11390] Removal of custom getContent methods

Removal of custom getContent methods for MP related tests
https://issues.jboss.org/browse/WFLY-11390
Please make sure your PR meets the following requirements:

[x] Pull Request title is properly formatted: [WFLY-XYZ] Subject or WFLY-XYZ Subject
[x] Pull Request contains link to the JIRA issue(s)
[x] Pull Request contains description of the issue(s)
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Attached commits represent units of work and are properly formatted

Linux - elytron: unrelated clustering test fail (that test has 94.5% success ratio)


Adds compileReadonly function

This PR adds compileReadonly function

Hmm - I wonder how many more HTML attributes we would possibly add directives for 😨  I'm worried we will get too many.

@if($condition) readonly @endif.
If there is minimal keystrokes saved without tackling verbosity, I reject.
At this point, I think is just better to create a package to handle forms separately.

@taylorotwell maybe you are right but actually, not all HTML attributes will be rendered to directives because the attributes that must be rendered must have a common use like @readonly which is similar to @disabled it's common to check about something to apply these attributes So, it'll be nice to render these attributes to directives in Laravel because Laravel tries to make everything awesome and easier.

@DarkGhostHunter the same thing can be applied to @disabled and @selected because we can use @if($condition) disabled @endif also the same thing with @selected but I see that it'll be nice if we use minimal keystrokes to handle these scenarios.

I looked over the attributes - looks like there isn't much of anything remaining after this.


IDENTITY-5213 - Solving Error occurred when creating a new user

https://wso2.org/jira/browse/IDENTITY-5213

https://wso2.org/jira/browse/CARBON-16060


Converting a PlainDateTime to a ZonedDateTime with disambiguation earlier when wall clock is moved forwards

Hello,
there seems to be an issue when converting a PlainDateTime to a ZonedDateTime with disambiguation earlier when the clock is moved forwards (e.g. time change from winter to summer time).
// Wall clock is moved forwards by an hour on 2024-03-31 at 02:00 in Europe/Berlin time zone.
// CET (+01:00) -> CEST (+02:00)
const plain = Temporal.PlainDateTime.from("2024-03-31T02:00")

// ambiguous, either 2024-03-31T02:00:00+01:00 (CET) or 2024-03-31T03:00:00+02:00 (CEST)
const zoned = plain.toZonedDateTime("Europe/Berlin", { disambiguation: "earlier" })

expect(zoned.toString()).toBe("2024-03-31T02:00:00+01:00[Europe/Berlin]")
// actually 2024-03-31T01:00:00+01:00[Europe/Berlin], so an hour earlier in UTC

I am not sure if that's the expected result, but it seem unintuitive to me.
Kind regards,
Felix Schorer

Hi @felixschorer. Here's why the results are the way they are:

In the Europe/Berlin time zone, on 2024-03-31, there's a nonexistent wallclock hour from 02:00 -> 02:59
The PlainDate your provided (2024-03-31T02:00) has a wallclock time of 02:00, which falls within this hour
When toZonedDateTime is called with a non-reject disambiguation setting, it must return a ZonedDateTime

When earlier, the wallclock time of the result will end up being -1 hour than requested in order to push it in-bounds
When later, the wallclock time of the result will end up being +1 hour than requested in order to push it in-bounds

Your earlier setting causes the resulting ZonedDateTime have a wallclock time of 02:00 - 1 hour = 01:00, which will have the timezone offset that the side BEFORE the transition has, which is +01:00. Thus, 2024-03-31T01:00:00+01:00[Europe/Berlin] is correct

@arshaw Thank you for clearing up my misunderstanding. I apprechiate the detailed explanation.


Selecting account in Send window changes back to original account

In the Send window, when you select a different account than the one that was displayed when you first entered the window, the original account will be restored after about 30-60 seconds.

This issue is bigger then explained and also releted to receive account as well.
How qt wallet should handle that:

Receive account should be stored per wallet. When user start qt wallet, it should setup receive account as it was done last time.
Current account should be used for all pages that using account: send, transactions and outputs. And also it should be stored per wallet.

Testing scenarios:

Open qt wallet, wallet 1. Setup receive account,  at pages send, transactions and outputs select current account and check if selection is correct.
restart qt wallet and check that receive account and current accounts are restored.
Open another wallet 2 and check that receive account and current accounts are different and they stored and restored correctly.
Do some account transfers. Check if account transfer affect  receive and current accounts.

OS tested: OSX
How to reproduce: Have a wallet with multiple accounts open.  Go to the outputs tab and change to a non default account.  Switch to the receive tab.
Behavior: The receive field does not get updated.
Expected Behavior: The receive field should be updated.

Tested as instructed.  The receive tab doesn't change, but Chris said that is expected.  Closing unless I hear anything from Konstantin conflicting.

@jbyrer , Receive is different, it shouldn't change.  There you define account that accept the coins.  This account should not be changed when you checking your transactions or sending coins.
So it is feature, it is expected that way

closed as K agreed that receive should be different (as it is)


Add link to Releases on GitHub in header navigation

There's no easy or obvious way to get to the GitHub repo or see what the latest release is from the docs. Can we add a "Releases" link like we're now doing for https://primer.style/css from the main nav?
This might tie in with upcoming navigation updates for primer.style.

Moving this to gatsby-theme-primer


feat: Add loggers to manifest for dynamic debug logging

https://github.com/home-assistant/architecture/discussions/715

Thanks. When did this feature go live? Does it support custom components? And should it include both Tesla and teslajsonpy?

It does support custom components, I made the modification directly in the custom_conponents folder for tesla_custom to confirm and it worked for me.
Not sure exactly when it was added, but loggers keys were added a while back: https://github.com/home-assistant/core/pull/65083
It only needs the keys of requirements, not the actual integration itself as HA can determine that one.
https://developers.home-assistant.io/docs/creating_integration_manifest/#loggers


Add unable to toggle Register network in the Packet Broker page in the Packet Broker troubleshooting guide

Summary

Add the information about I'm unable to toggle **Register network** in the Packet Broker. What should I do? in the Packet Broker troubleshooting guide.
Why do we need this ?
To help users to understand the reason for behaviour and resolution to solve it.
What is already there? What do you see now?
https://www.thethingsindustries.com/docs/getting-started/packet-broker/troubleshooting/
What is missing? What do you want to see?
Add I'm unable to toggle **Register network** in the Packet Broker. What should I do? into the Packet Broker troubleshooting guide.
How do you propose to document this?

Insights:
Generally, to enable Packet Broker peering, The Things Stack Cloud users can enable it by toggling the Register network button via Console using Admin Account. It is not possible for users to enable packet broker peering if the tenant is not registered in the Packet Broker.
So, The Things Stack Cloud users can contact the TTI Support team via the<EMAIL_ADDRESS>email to register the tenant in the Packet Broker.
Can you do this yourself and submit a Pull Request?

No, @nejraselimovic

I'm confused about this. Who does this apply to? Because here it says:

To register it (tenant), toggle the Register network switch ...

So basically, if you're unable to toggle the switch, you're unable to register the tenant. But why are you unable to register the tenant? Why does TTI need to do it for you? @adriansmares can you pls explain?

Hey - there are two issues here that make things a bit more complicated that they should be.
Fundamentally in order to receive traffic from Packet Broker, a network needs to have a set of device addresses allocated to them. We call these addresses blocks, and they are automatically allocated when people register via the normal onboarding flow (i.e. when they self register with their credit card).
Some tenants are manually created or are simply very old and do not have a device address block allocated to them. In such cases, we need to allocate them a device address block in order to allow them to receive traffic from Packet Broker. This is a manual operation.

There was a bug which has been fixed for version v3.25.1 which always stopped the Register network switch from working for tenants which have no tenant settings whatsoever. I have fixed it in https://github.com/TheThingsIndustries/lorawan-stack/pull/3641 .
I think what we need to inform customers about is the possibility that they may need device address blocks allocated to their tenants - something like 'I have registered my network but I still do not receive traffic', which indeed should guide them towards CyberEye.


Support for Bootstrap 4

Hi,
Do you think support Bootstrap 4?
http://blog.getbootstrap.com/2015/08/19/bootstrap-4-alpha/

Closing as a duplicate of #4234

Closing as a duplicate of #4234.  @elesdoar, please take a moment to search both open and closed issues for your topic before opening a new one.  When you don't, you create unnecessary busy work for us.  Thanks.


Navigation Back Functionality Issue during Email Verification on Enatega Multivendor Customer Website.

Issue: Navigation Back Functionality Issue during Email Verification on Enatega Multivendor Customer Website
Description:
There is a navigation issue on the Enatega Multivendor Customer Website during the email verification process. The "navigation back" function does not work properly, impacting the user's ability to return to the previous page or step.
Impact:
User Experience: The malfunctioning navigation back feature can frustrate users and affect their overall experience on the website.
Process Flow: The issue disrupts the expected flow of the email verification process, potentially causing confusion.
Steps to Reproduce:

Access the Enatega Multivendor Customer Website.
Proceed to the email verification process.
Attempt to use the "navigation back" function to return to the previous step.
Observe that the function does not work as expected.

Expected Resolution:
The navigation back functionality during email verification should be addressed and fixed to ensure that users can navigate smoothly and return to the previous step when needed. This will enhance the user experience and maintain a logical process flow.

Issue Resolved: This issue has been successfully fixed.


Add support for Convection using libCEED

This PR adds support using libcEED for:

[x] ConvectionIntegrator,
[x] VectorConvectionNLFIntegrator,
[x] VectorCoefficient,
This should be reviewed after #1719

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#1766
@YohannDudouit
@v-dobrev
@barker29 + @pazner
10/29/20
⌛due 11/12/20
⌛due 11/19/20

@barker29 This PR adds support for ConvectionIntegrator if you want to try your libCEED based solver on it.

@jandrej This PR adds support for VectorConvectionNLFIntegrator if you want to try it in your Navier-Stokes miniapp.

I've caught some bugs, I was making a mistake for the tests of non-linear forms, I put this back in WIP.

@barker29 I think I have addressed your remarks.

I still have the problem with ex9p.

@YohannDudouit can merge master and resolve conflicts?

@tzanio I will merge master, I found the bugs but I didn't fix it in a clean way, I want to clean this, and I'll merge master.

@barker29 @pazner ex9 is working now, my fix is not the cleanest, currently Convection only works with alpha = -1 (this value is hardcoded on the libCEED side). I have to redesign the way BuildContext are handled to make this cleaner but this is not a small change so I prefer to postpone this refactor.

@barker29 @pazner ex9 is working now, my fix is not the cleanest, currently Convection only works with alpha = -1 (this value is hardcoded on the libCEED side). I have to redesign the way BuildContext are handled to make this cleaner but this is not a small change so I prefer to postpone this refactor.

Maybe for now a compromise would be to have CeedScalar coeff[4] in the BuildContext, and use coeff[3] as the alpha for convection?
I agree this is an ugly fix, but this could be revamped when you do a redesign of BuildContext.
I'd prefer not to have alpha=-1 hard-coded. It makes sense for ex9, since the convection term is moved to the RHS for time integration, but wouldn't make sense for steady problems in residual formulation.

@barker29 @pazner I merge the libCEED refactor branch, besides this I only moved the MFEMCeedOperator into NonlinearFormIntegrator to avoid having to duplicate code inside each Integrator that supports libCEED.
@tzanio I lowered the order of test to only order 1, now the libCEED tests take about 6 sec in debug an 1 sec in release version.

@barker29 @pazner I merge the libCEED refactor branch, besides this I only moved the MFEMCeedOperator into NonlinearFormIntegrator to avoid having to duplicate code inside each Integrator that supports libCEED.
@tzanio I lowered the order of test to only order 1, now the libCEED tests take about 6 sec in debug an 1 sec in release version.

This PR has grown quite a bit -- it changes a lot of files (45). The scope has probably also grown far beyond what the title says. Should we consider breaking it into smaller pieces?

This PR has grown quite a bit -- it changes a lot of files (45). The scope has probably also grown far beyond what the title says. Should we consider breaking it into smaller pieces?

@v-dobrev This is correct that the title is not relevant any more, different branches have been merged and already reviewed, because this PR is a refactor of the libCEED integration. I think it would only be disruptive to restart the review process since I believe we're seeing the end of it.

@v-dobrev This is correct that the title is not relevant any more, different branches have been merged and already reviewed, because this PR is a refactor of the libCEED integration. I think it would only be disruptive to restart the review process since I believe we're seeing the end of it.

One very minor comment: perhaps we should rename the libceed subdirectory to ceed in order to match the name of the namespace.

I will also prefer ceed

Merged in next for testing...

Re-merged in next.

LGTM


Fix the crash when an endpoint without a UTF8 name is discovered

Summary

How did you test this change?

Granted


Confirmed button showing on claim stakes and fee modal before claiming the reporting stake: See images

Opened from notification:
Confirmed button already showing

Clicking it makes it go away:

I had a winning position on the same market that I had winning REP. I claimed proceeds first
This is my bell history:

Note: maybe claiming on proceeds indirectly causes claiming stake and fees to show confirmed

pulling out marketIds is incorrect. Look at getUserAccountData method in Users.ts

it could also be from switching accounts

not seeing this....closing


[Chi nhánh EVN] Warning in Log File

Log files
2024-09-01 06:44:55.687 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open with args ('/config/custom_components/nestup_evn/evn_branches.json',) inside the event loop by custom integration 'nestup_evn' at custom_components/nestup_evn/nestup_evn.py, line 1030: with open(file_path) as f: (offender: /config/custom_components/nestup_evn/nestup_evn.py, line 1030: with open(file_path) as f:), please create a bug report at https://github.com/trvqhuy/nestup_evn/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#open

OS: Debian aarch64

HA platform: Core

HA Version: 2024.8.1

Installation method: HACS

Version: 2.4.1

Mình đã fix ở phiên bản mới nhất nhé bạn.


No keyboard characters

Microsoft PowerToys version
0.73.0
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
Mouse Without Borders
Steps to reproduce
When writing Polish characters, not all of them want to work
✔ Expected Behavior
Possibility to write Polish characters
❌ Actual Behavior
No possibility to write Polish characters
Other Software
No response

/dup #29342


Setbrightness

Fixing spelling issue

@abchatra,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


[Parse][SR-510] emit error for closures outside of a func

When there is no local context, we should emit an error rather than
silently eating the closure. This code used to be silent to avoid
double-reporting an error for fixed-size array types, but those
no longer exist.
Resolves https://bugs.swift.org/browse/SR-510

Passes build-script -RT.
(except for the existing failing test on master at the moment, not related to this PR.)

Thanks, @dduan!

The error message isn't really correct for a user:

Accessors, initializers, and deinitializers are not considered "functions". (Nor exactly are closures.)
I think you mean "initial value expression" instead of "initializer", since an "initializer" is "the thing you declare with init" in Swift.
Script-mode files allow top-level code, including closures.

Stepping back, both of the other test changes aren't really adding any value. Admittedly those are just a mess of tokens and therefore a mess of error messages, but a user who ends up in that situation is probably not thinking of those braced-blocks as closures.
Why isn't this being caught by the normal enum case expression validation already?

@jrose-apple For enum rawValue, the enum expression parser simply gives Parser::parseExpr an diagnoses and defer the error handling to the latter. Which is why, I believe, @jder handled it here (where parseExpr eventually calls).

@jrose-apple for comparison, I attempted to catch the error at the enum error but ultimately decided solution here is better. https://github.com/apple/swift/pull/931
Part of this bug is when rawValue parsing fails, the case expression code simply quit silently. That's probably worth addressing too.

@jrose-apple Thanks for the feedback. I agree that the error message is not great, but had missed some of your points.
I believe the way the current logic for parsing the raw values works is that parseExpr will always print an error message when it fails, falling back to the generic "expected raw case value" error if it is completely confused. If parseExpr succeeds parsing an expression, then the case parseDeclEnumCase validates that it is a literal, etc (which I think you're referring to about the case validation). In this case the expression was failing to parse at all, but parseExpr was not producing an error.
So, it seems like we could:

Improve the error message.
Fall back to the generic "expected raw case value" error rather than producing a specific diagnostic for this case. This would mean having parseExpr pass the "fallback" diagnostic along to parseExprClosure.
Allow parseExprClosure to succeed without a local context (returning an ErrorExpr?) and let it get caught by the parseDeclEnumCase checks.

I personally think that the second option is probably the most reasonable, but it is currently unprecedented (the "fallback" diagnostic is only emitted in a single place right now) which is why I didn't do it in the first place. What do you think?

Hm. What about just making a local context? I haven't looked at this code recently so I don't know how hard that is, but it seems like just parsing case values the same way as property initial values would be reasonable.

Sure, I can look into that.

@dduan If you'd like to take a look at that yourself, feel free to grab the bug from me.


fixed bugs when 'osInfo' like 'iOS-12-1'

macOS Mojave 10.14.3
Xcode 10.1 (10B61)

@ChengLuffy thanks for your contributions. :smile:


The Basics of SEO For Your Website

Most of my day job involves building in-house web-based software and commercial client portals, SEO wasn't much applicable until 2007, I have found some fun projects to do for my then employer Boston MedFlight. Along with its company site, I built several websites for its consortia, CCTCORE and NEAA. At the time CCTCORE conducted an international airway study to collect the airway management variables data from US and Canadian transport programs. SEO was desired.
The meta tags, where the meta data are stored
<head>
<title>Services | Web Design and Development Services - emAmazed.com</title>
<meta name="description" content="Here is a description of the services we provide">
<meta name="keywords" content="web design, Wordpress, Joomla, Drupal, SEO, web development, MA">
</head>

Description can be any length, but normally got truncated after 160 characters.
Don't let your keywords exceed 10 phrases and limit your page title within 70 characters. When you structure your title tags, includes your target keyword phrase separated by the "|".
Make search engine robots Index your pages ... or not
Search engine robots look for your site "meta data" that are stored in your site "meta tags". It reads and interprets them, then uses to index your site.
If you don't wish your site to be indexed, 301 redirect and .htaccess can prevent SSL https version of your site from getting indexed.
Bring RESTful design to the site
Post and Get variables on your sites can utilize your SEO results. REST, "representational state transfer", consists of distinct URLs linking directly to content or content states in a web-based application. The content is accessible via one unique URL and one unique URL only.
For example,
- http://www.emAmazed.com/services/web-design
- http://www.emAmazed.com/services/analytics
- http://www.emAmazed.com/services/?page=analytics

robots.txt makes your site SEO more robust
A robots file is what search engine and other information gathering companies use to find your site, analyze it and then decide ignore it, ban it or index it.
Robots is a catch-all, it "crawl" through the web and collect data from websites.
User-agent: *
Disallow: /my-folder/
The "User-agent: *" means this section applies to all robots,
The "Disallow: /folder/" tells the robot that it should not visit any pages under /my-folder on the site.
Google Analytics is your best friend
It is an easy and handy tool to see who is visiting your site and reports the traffic flow on your site.

Step by Step to set up your SEO:

How to check website current meta tags. Right click on the webpage, select "Inspect".

When you hover your mouse over the source code in the "Elements" tab, the corresponding page section associated with that code will be highlighted.

xx


want to leak non-env_prefix'd values from dotenv?

Hi,
I'd like to inquire about the intentionality of this dotenv loading behavior when env_prefix is set. Namely, even with an env_prefix set in the model config, it looks like we happily read values whose name matches the field names even when they are not prefixed:
def test_with_prefix_with_dotenv(tmp_path):
    p = tmp_path / '.env'
    p.write_text('apple=incorrect')

    class Settings(BaseSettings):
        apple: str

        model_config = SettingsConfigDict(env_file=p, env_prefix='foobar_')

    s = Settings()
    assert s.apple == 'correct'

I see per the documentation:

Pydantic settings loads all the values from dotenv file and passes it to the model, regardless of the model's env_prefix. So if you provide extra values in a dotenv file, whether they start with env_prefix or not, a ValidationError will be raised.

Respectfully, reading such unprefixed value seems like a footgun to me (imagine e.g. DEBUG vs SOME_OTHER_THING__DEBUG), especially since the env-sourced variables do not exhibit this behavior. Intuitively, I'd expect overall similar behavior for both sources.
But, even if this load-all behavior is desired, should there at least be an effort to prefer the dotenv value whose prefix matches over that with no prefix? Without having looked at the actual parsing code, it appears the last entry currently wins, which can be seen by modifying the previous test:
...
    p.write_text('foobar_apple=correct')
    p.write_text('apple=incorrect')
...

Thanks in advance.

Thanks @mknaw for reporting this.
It is because Dotenv source parses extra values(apple=incorrect in your case) at the end and it will override the old value(foobar_apple=correct).
I think we can change it to don't override the value but I am afraid it will break some user code that depends on this.


Markdown on Interactive Messaging

Hi team,
When rendering a ListPicker InteractiveMessage or ChatMessage, how can we insert a link as such?
I've tried various methods, i.e.
https://codesandbox.io/s/snowy-field-r8d3c?file=/src/App.js:481-560
https://github.com/remarkjs/react-markdown/issues/12
https://docs.aws.amazon.com/connect/latest/adminguide/enable-text-formatting-chat.html

Currently we don't support text formatting in interactive messages. For chat messages you need to call StartChatContact API with the SupportedMessagingContentTypes set to [ "text/plain", "text/markdown" ], then send a message with content type text/markdown. It should be successfully sent through and you can have your own implementation to render it correctly.
To insert a link, just follow the common markdown syntax for links - https://www.markdownguide.org/basic-syntax/#links.
Does this answer your question?

Closing, no response from the issue creator.


Ports take up by certbot

Both the init script and docker-compose up fail. As much I can tell nginx container can't start because the certbot container already uses ports 80 and 443.
Output of init script
### Downloading recommended TLS parameters ...

### Creating dummy certificate for dicedraw.me ...
Generating a RSA private key
........................+++++
............+++++
writing new private key to '/etc/letsencrypt/live/dicedraw.me/privkey.pem'
-----

### Starting nginx ...
Building nginx
Step 1/4 : FROM nginx:alpine
 ---> 0476319fbdad
Step 2/4 : COPY /build /usr/share/nginx/html
 ---> 46e1e3ae3428
Step 3/4 : COPY /compose/nginx.conf /etc/nginx/conf.d/default.conf
 ---> ac6ab3e5a67f
Step 4/4 : CMD ["nginx", "-g", "daemon off;"]
 ---> Running in 0c5af44c0668
Removing intermediate container 0c5af44c0668
 ---> e0dbfc383fb9
Successfully built e0dbfc383fb9
Successfully tagged server_nginx:latest
WARNING: Image for service nginx was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating server_nginx_1 ... error

ERROR: for server_nginx_1  Cannot start service nginx: driver failed programming external connectivity on endpoint server_nginx_1 (4df10f029d22d1d37ec45f74ead73e1d83b63ee0c433fd2a0342ae39f8789e83): Error starting userland proxy: listen tcp <IP_ADDRESS>:80: bind: address already in use

ERROR: for nginx  Cannot start service nginx: driver failed programming external connectivity on endpoint server_nginx_1 (4df10f029d22d1d37ec45f74ead73e1d83b63ee0c433fd2a0342ae39f8789e83): Error starting userland proxy: listen tcp <IP_ADDRESS>:80: bind: address already in use
ERROR: Encountered errors while bringing up the project.

### Deleting dummy certificate for dicedraw.me ...

Output of docker-compose up
Creating server_certbot_1 ...
Starting server_nginx_1   ... error

Creating server_certbot_1 ... done
rting userland proxy: listen tcp <IP_ADDRESS>:80: bind: address already in use

ERROR: for nginx  Cannot start service nginx: driver failed programming external connectivity on endpoint server_nginx_1 (60bec82974a55f55ffefe5adeeb6c0a2a64b9b0b3b488dca1977f2bed813be95): Error starting userland proxy: listen tcp <IP_ADDRESS>:80: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Running on ubuntu 18.04
Docker version 18.09.4, build d14af54266
docker-compose version 1.21.2, build a133471

same here

Issue was with my config.

there was an issue with nginx starting because it had a dependence on another service
I had port 80 used by apache. It can be stoped with sudo /etc/init.d/apache2 stop

For the dependence issue the fix was the modified init script provided in another issue https://github.com/wmnnd/nginx-certbot/issues/11#issuecomment-478324876

Glad to hear it worked out!


Update Installation-Troubleshooting.rst

added fix for "Receiver node cannot receive messages from the talker [ARM64]"

No response to my comment for a while, so I'm going to close this.  If you'd like to continue with this PR, please feel free to respond and reopen.


WIP: Learning mode

continuation of #2
Progress so far (will be updated)
bash edition

you can toggle learning mode on and off in runtime, simply run aptpac --learning-mode=on to turn it on and aptpac --learning-mode=off to turn it off.

C-edition
There are 2 ways to enable/disable learning mode in the C edition:

using the --config flag. the setting is saved in ~/.aptpac/aptpac.config

to enable learning mode: aptpac --config set learn.
to disable learning mode: aptpac --config unset learn

You can use the environment variable APTPAC_LEARN to turn it on and off in runtime without having to recompile.

run aptpac like this: APTPAC_LEARN=1 aptpac <command>
add this: export APTPAC_LEARN=1 to your bashrc or equivalent and source it or restart your terminal to have learning mode on until you remove that line or change the value of the variable.

- you need to recompile to toggle it. to turn it on, add -DLEARN=1 to the cmake line. to turn it off (only needed if you are recompiling the same build without re-generating the build files from scratch), add -DLEARN=0.

Learning mode is done! this means I will close this issue once I move the config file to ~/.config and release aptpac 3.0!

v3.0 has been released!


[GEP-20] Adjust Control Plane Status Dashboard

How to categorize this PR?

/area monitoring
/area high-availability
/kind enhancement
What this PR does / why we need it:
This PR adjust the Kubenetes Control Plane Status dashboard to correctly show CPU and Memory usage for kube-controller-manager and kube-scheduler if they are deployed with multiple replicas.
Which issue(s) this PR fixes:
Fixes partly #6529
Special notes for your reviewer:
I also checked the dashboard for other components that will run with multiple replicas in the future, the configuration should already be sufficient.
Release note:

The `Kubernetes Control Plane Status` dashboard has been updated to show correct values for `kube-controller-manager` and `kube-scheduler` once they are deployed with multiple replicas for HA shoots.

/approve


Application does not create a new directory for my new bot account

I made a new bot account to replace the "phoenixcouncilbot" one out of fear that you (banshee) would lock me out of the account or make it so I can't use it for the bot and when I went to use my new bot account in the application, I got this: https://gyazo.com/1e75fd4177bfdd09991d34707c115238
And here is the directory where the new folder for the new account should be: https://gyazo.com/d76b7d574b4973953c2db0183457d3be

No one replied...


B 21115

INT PR
Summary
Remove Conus Or Not Page

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

  Generated by :no_entry_sign: dangerJS against d0ee44124c2bed5bdf69b51faabe5ab62bb0c82d


fix: 2146 - compliance ration reduction calculation

Same code as in https://github.com/bcgov/zeva/pull/2147, which was approved


CreditCardFraudDetection.Trainer load data file error

For project BinaryClassification_CreditCardFraudDetection\CreditCardFraudDetection.Trainer\ModelBuilder.vb file line number 37 is
_dataSetFile = assetsPath
Change this line to
_dataSetFile = Path.Combine(_assetsPath, "input\creditcard.csv")
This will solve the AuthorizationException error.

@rrvenki If commit https://github.com/Nukepayload2/machinelearning-samples/commit/d73d8eee7447b3dc6d2b65289bbbafe7576f9296 has solved your problem, please close this issue.


Fixing to_dict() issue in editMessageReplyMarkup.

This error wasted my time. and i realized its from client.
by the way. it fixed now :)

No need, v0.9.0 will be released soon which it will make Pytdbot well-typed.


dev tools screenshot tests

~(work in progress)~ pretty happy with how these came out

Dang, unable to find the devtools UI window on CircleCI. Not sure what's going wrong here.
======================================================================
ERROR: test_devtools_python_errors (tests.test_render.Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/circleci/repo/tests/test_render.py", line 2289, in test_devtools_python_errors
    self.wait_for_element_by_css_selector('.test-devtools-error-toggle').click()
  File "/home/circleci/repo/tests/test_render.py", line 60, in wait_for_element_by_css_selector
    'Could not find element with selector "{}"'.format(selector)
  File "/home/circleci/repo/venv/lib/python3.6/site-packages/selenium/webdriver/support/wait.py", line 80, in until
    raise TimeoutException(message, screen, stacktrace)
selenium.common.exceptions.TimeoutException: Message: Could not find element with selector ".test-devtools-error-toggle"

This does work locally.

Hm, devtools UI is there but the error messages aren't popping up

Perhaps it's an issue with the build systems / branches, like some other uncaught exception. I'll try a fresh build tomorrow.

Re-built everything locally using same instructions in circle/config.yml and was able to reproduce the error locally 👍

Selenium screenshot artifact looks (mostly) good now:

hooray we have percy snapshots 🎉

I suspect the missing CSS is from werkzeug's JS - it adds some dynamic CSS to the nodes. It might be doing that in a way that is un-capturable (i.e. in memory)

:dancer:  nice solution with percy swapping,


Default profile headings

Closes #1246
The headings in #410 seems a bit outdated? I chose the ones that made the most sense for the sections we got now.
This is what it looks like if the "Who I am" / "What I do in my free time" fields are empty:

Frontend checklist

[x] Formatted my code with yarn format && yarn lint --fix
[x] There are no warnings from yarn lint
[x] There are no console warnings when running the app
[x] Added tests where relevant
[x] All tests pass
[x] Clicked around my changes running locally and it works
[x] Checked Desktop, Mobile and Tablet screen sizes

@lucaslcode Have another look and see what you think. The rendering of paragraphs seem to differ between the input and the read only view - in the input, the paragraphs are rendered as
s whereas they are actually shown as
s in the read only view.


Use custom template by url

Hey Pete,
I wrote some custom templates, that I want to reuse over several projects.
Therefore I added them to a public github repository.
Allowing to provide the template by url, would help a lot. e.g. https://raw.githubusercontent.com/...
Otherwise I would have to 1st save the template locally by using wget / curl or so, then generating the changelog and finally deleting the template again.
Or do you have another approach?

fyi - i just stumble over that notice in the nodejs fs api
https://nodejs.org/api/fs.html#fs_fs_access_path_mode_callback

Using fs.access() to check for the accessibility of a file before calling fs.open(), fs.readFile() or fs.writeFile() is not recommended. Doing so introduces a race condition, since other processes may change the file's state between the two calls. Instead, user code should open/read/write the file directly and handle the error raised if the file is not accessible.

It might work for your case - no question, just wanted to forward this to you in addition.


Is it possible to add a behavior to an existing custom element?

I know hat extending custom elements like in 0.5 isn't possible in 1.0, but what about adding just additional behaviors?

Sure, s what behavbehaviors are for. https://www.polymer-project.org/1.0/docs/devguide/behaviors.html

Hmm, then I fear I don't fully understand the Docs ;)
I will try to explain a bit further what I'm trying to do:
I created a Behavior that does some publishing to a mqtt broker when the checked attribute of the element changes. How can I add this behavior to f.e. paper-checkbox?
Right now I worked around the Problem (of not knowing how to add the behavior to an existing element) by encapsulating paper-checkbox in my own custom element, but I think that isn't a real good solution, so I'd like to add my behaviors/properties to e.g. paper-checkbox directly.

The short answer is no, you can't add a behavior to an existing element, and your best course of action is to use composition as you are now.
The elements folks have tried to factor out as much code into behaviors as possible, so it's easier to reuse that code in your own elements. But in this case, I think you want all of paper-checkbox, so that doesn't really help you.
The ability to extend an element is still on the roadmap, but it's a complicated one. You can follow that bug: https://github.com/Polymer/polymer/issues/2280.

Thanks for the Information!


tokenizer in demo_vid2seq.py

hello, as i want to use demo_vid2seq.py to get video captioning, there are many questions which i don't understand, first, when i run demo_vid2seq.py, there is an error:
load Vid2Seq model
Traceback (most recent call last):
File "demo_vid2seq.py", line 55, in
tokenizer = _get_tokenizer(args.model_name, args.num_bins)
File "/root/tzp/codes/VidChapters-main/model/vid2seq.py", line 12, in _get_tokenizer
tokenizer = T5Tokenizer.from_pretrained(tokenizer_path, local_files_only=True)
File "/root/.local/conda/envs/vidchapter/lib/python3.7/site-packages/transformers/tokenization_utils_base.py", line 1796, in from_pretrained
f"Can't load tokenizer for '{pretrained_model_name_or_path}'. If you were trying to load it from "
OSError: Can't load tokenizer for 't5-base'. If you were trying to load it from 'https://huggingface.co/models', make sure you don't have a local directory with the same name. Otherwise, make sure 't5-base' is the correct path to a directory containing all relevant files for a T5Tokenizer tokenizer.
i don't know how to set and get the tokenizer,  can you help me?

This error happens when you do not load the tokenizer properly, so make sure you have it downloaded and that the TRANSFORMERS_CACHE environment variable is set accordingly.

I'm getting a similar error when I try to run demo_vid2seq.py:
OSError: t5-base does not appear to have a file named pytorch_model.bin but there is a file for TensorFlow weights. Use from_tf=True to load this model from those weights.
@tickm did you manage to solve your error

@tickm do you know how to set and get the tokenizer yet? I also have this problem

@tickm
I successfully ran the code!
First, your need comment this line.
Then, create a new file named download_t5.py and write the following content:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("translation", model="t5-base")
run python download_t5.py , transformers will download t5 into /user/.cache/huggingface/models/models--t5-base
Finally, run demo_vid2seq.py and transformers will use cached t5.


Added Universidad Internacional de La Rioja

url: https://en.unir.net/
Example course longer than 1 year (4 years):  https://www.unir.net/educacion/grado-maestro-primaria/549200001487/#-plan-de-estudios

@Luz84 I am sorry, I have to close this request without merging, because you requested to add a non-existent domain to this repository:
$ host comunidadunir.es
Host comunidadunir.es not found: 3(NXDOMAIN)

Please ensure you are familiar with this repository rules located at the bottom of this page and submit a new request with correct information. Thank you for the understanding!


Spaces and parentheses in columns cause "not a valid scope name"

If Dataframe column names have spaces or parentheses, the fit() function raises an exception:
import pandas
import keras_pandas.Automater

data_good = pandas.DataFrame({'length': [1.0]})
data_bad = pandas.DataFrame({'length (cm)': [1.0]})

auto_good = keras_pandas.Automater.Automater(numerical_vars=['length'])
auto_bad = keras_pandas.Automater.Automater(numerical_vars=['length (cm)'])

auto_good.fit(data_good)
auto_bad.fit(data_bad)

Full traceback:
>>> auto_bad.fit(data_bad)
/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/keras_pandas/constants.py:33: FutureWarning: Method .as_matrix will be removed in a future version. Use .values instead.
  transformed = input_dataframe[variable].as_matrix()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/keras_pandas/Automater.py", line 92, in fit
    input_layers, input_nub = self._create_input_nub(self._variable_type_dict, input_variables_df)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/keras_pandas/Automater.py", line 272, in _create_input_nub
    variable_input, variable_input_nub_tip = variable_type_handler(variable, input_dataframe)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/keras_pandas/constants.py", line 42, in input_nub_numeric_handler
    input_layer = keras.Input(shape=(input_sequence_length,), dtype='float32', name='input_{}'.format(variable))
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/keras/engine/input_layer.py", line 178, in Input
    input_tensor=tensor)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/keras/legacy/interfaces.py", line 91, in wrapper
    return func(*args, **kwargs)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/keras/engine/input_layer.py", line 87, in __init__
    name=self.name)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/keras/backend/tensorflow_backend.py", line 517, in placeholder
    x = tf.placeholder(dtype, shape=shape, name=name)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/tensorflow/python/ops/array_ops.py", line 1745, in placeholder
    return gen_array_ops.placeholder(dtype=dtype, shape=shape, name=name)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/tensorflow/python/ops/gen_array_ops.py", line 5020, in placeholder
    "Placeholder", dtype=dtype, shape=shape, name=name)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 394, in _apply_op_helper
    with g.as_default(), ops.name_scope(name) as scope:
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 6040, in __enter__
    return self._name_scope.__enter__()
  File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
    return next(self.gen)
  File "/home/me/.virtualenvs/p3ml/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 4004, in name_scope
    raise ValueError("'%s' is not a valid scope name" % name)
ValueError: 'input_length (cm)' is not a valid scope name

I just fell over this using the Iris dataset from Sklearn. If it's an intended constraint it should be documented, but I suspect it's not.
This is using Python 3.6.5, keras-pandas 2.2.0, pandas 0.23.4.

Great catch! The 3.0 version is in the final days of development, so I’ll address this issue in a patch to the 3.0 version, rather than the current 2.X line.
As an aside, this is a tensorflow restriction in layer names, which can’t be removed. We can, however, internally format variable names to be consistent with tensorflow naming rules. The user wouldn’t know the difference, unless they are poking around in tensorflow objects.

Addressed in #92

@detly Addressed, by converting the 'natural' user provided names into names w/ non-alphanumeric (and underscores) characters removed

Is this in 3.0.0? I'll work out of master for now if not.

@detly This is currently in master, but is not in the release version yet. Working out of master should resolve this issue.
Long story, but travis is having deploy issues, and I can't (shouldn't?) release new versions until they get their ish together or I move to another CI platform.

@detly JK, variable name formatting is now in 3.0.1, released this morning.


Search for latitude and longitude

A user may have a column with locations of the form 1846 19th street, 9500 Gilman Drive, etc and may want to create latitude and longitude columns from this information.

@ackermag also requested the ability to convert lat/lon in DD MM SS to decimal degrees, and to support GPS coordinate conversions.
Adding this here since these features are all related. It may make sense to add these features after the SRGD.csv format (#51) is implemented, as that is a spatial-aware format.


Typescript > Add type definition on all remaining variable using any

Just reenable the eslint rules related to @typescript-eslint/no-unsafe-*

@jerome-benoit Perferct!


Update json-path to 2.9.0

About this PR
📦 Updates com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.jayway.jsonpath", artifactId = "json-path" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.jayway.jsonpath", artifactId = "json-path" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

scala steward update done on PR https://github.com/nationalarchives/da-tre-fn-court-document-pre-parser/pull/40


Arceuus essence mine doesn’t have “mining/not mining” panel

Hi! This is my first suggestion and I couldn’t find anything specifically about it while searching so forgive me if I missed it.
Would it be possible for mining dense essence blocks for blood/soul crafting to have the “mining/not mining” panel that also houses the counter for how many actions you’ve completed? Thank you for reading!

Added in 5a524471f8358e75405f787964391c986e529029


remove the ScopeWrapper workaround

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I formatted the code using mvn -Pformat,fastinstall install && mvn -Psourcecheck

As https://github.com/open-telemetry/opentelemetry-java/issues/5055 seems to be fixed.

@lmolkova would you mind to review this please?


Task/integrate into a runnable project

Integrate the engine and the UI into a runnable application.

Updated yellow color.


The program seems to be stucked.

System OS
Windows
Python Version
3.11 (CPython)
Install Source
pip / PyPi
Install version / commit hash
4.2.4
Expected Behavior vs Actual Behavior

The first one: Always display 'converting' but still moving on with a very slow rate.
The second one: take too much time to download the song
Steps to reproduce - Ensure to include actual links!
spotdl sync https://open.spotify.com/playlist/3q2y6gtt1mjVKKYty40p6V --save-file "MyLove.spotdl"
Traceback
Empty

Other details
No response

I'm experiancing the same behavior as well. Whan conversion starts it's just barely moving the progress.
spotdl version: 4.2.4
Win 11 Pro
Python 3.12.1
ffmpeg version 2024-01-11-git-5e751dabc5-full_build-www.gyan.dev

Sorry, if this isn't the correct place but I'm encountering a similar issue as mentioned above. While spotdl isn't completely stalled, its performance seems to have degraded compared to the latter part of last year. Despite running on the same distribution, I had to re-install recently. Previously, I could download over 300 songs within hours, but now it's taking days to complete, even when running continuously 24/7. Specifically, I'm trying to download this playlist: https://open.spotify.com/playlist/1TNg7JCxifAjwrnQARimex.
For reference, here's a link to my config.json: https://pastebin.com/5LVHnzTS
spotdl version: 4.2.4. (installed through pipx)
Arch (Garuda) Linux
Python version: 3.11.8
Pipx version: 1.4.3
ffmpeg version: n6.1.1

youtube might be throttling the downloads. make sure you are using the latest version of yt-dlp


[BUG] : Toast appears after saving a page with no changes

Bug Description
A success toast pops up after saving a page, even though nothing has changed.
To Reproduce
Steps to reproduce the behavior:

Go to a note
Click on edit
Save without changing anything
See toast pop up

Expected behavior
If nothing is changed, it shouldn't show the modal or any time of feedback, as there is nothing to update. :)

I'm currently rewriting the app with next.js, it'll be fixed once finished :)

Cool! Just thought I'd point it out. :)


Task Inputs and Outputs are not fully Configured in plugin requiring Daemon restart on change

Expected Behavior
If I change a parameter in the profiles block, for example if I add or change the filter block I should be able to re-run the task and be running with these new inputs.
detekt {
    version = "1.0.0.RC7"

    subprojects
        .forEach {
            profile(it.name, Action {
                input = "${it.projectDir}/src/main/kotlin"
                config = "${rootProject.projectDir}/config/detekt/detekt.yml"
                outputName = "detekt-report"
                output = "${project.buildDir}/reports/detekt"
            })
    }
}

Current Behavior
If you change configuration without killing the the Gradle daemon (with ./gradew --stop) your code ends up re-running with the same inputs and you will end up with confusing errors.
Context
This causes issues during the initial configuration phase of this plugin where you are rapidly changing configuration to be very confusing. Changing some code should result in a behavior change which does not occur.
Your Environment
------------------------------------------------------------
Gradle 4.7
------------------------------------------------------------
Build time:   2018-04-18 09:09:12 UTC
Revision:     b9a962bf70638332300e7f810689cb2febbd4a6c
Groovy:       2.4.12
Ant:          Apache Ant(TM) version 1.9.9 compiled on February 2 2017
JVM:          1.8.0_162 (Oracle Corporation 25.162-b12)
OS:           Mac OS X 10.13.4 x86_64

Thanks for reporting, there is an ongoing effort to rework the gradle plugin and hopefully this will be fixed then too!

This should be fixed for RC9.2 and higher.


Nether Coal

2x burn time.
Not sure how to make this just yet...

Thoughts on this was to have Nether Growth spread to a Nether Coal Ore and turn it into Nether Coal Ore..... Which is better.

This might need some tweaks to the Nether Growth spread logic to keep it somewhat sane as I want to add more things to how it can spread to other things.

This could use some rework, as it's weird how the Coal Ore block drops 2 Coal, but Nether Coal Ore drops only one, thus making it pretty useless to farm Nether Coal Ore, as 2x heat time is the same as 2x drops. Maybe increase the droprate of Nether Coal Ore to 2x also, ale increase the heat time to 3x?


Native Notebooks - .ipynb does not respect auto save on focus change

Environment data
Version: 1.55.0-insider
Commit: 5d80c30e5b6ce8b2f5336ed55ad043490b0b818f
Date: 2021-03-08T05:24:34.127Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.3.0
jupyter: v2021.4.637168989
python: v2021.3.636328865-dev
Expected behaviour

.ipynb file is saved whenever cursor select somewhere out of the notebook window frame.

Actual behaviour

.ipynb is NOT saved, must manually save file with cmd+s.

@jaymegordo Yeah, at a minimum I repro some inconsistent behavior regarding this. I believe that we might need to transfer to vscode core to get this fixed. If so, I'll link the issue.

@IanMatthewHuff Please could you file an issue with VS Code with the details, seems like you managed to repro this at your end.

https://github.com/microsoft/vscode/issues/119026 @DonJayamanne

Should be addressed already.


Uniswap/token-list

0xA7A72E26b76dd899b5A77045Dd190BeE36D5748F

Transfer

0xA7A72E26b76dd899b5A77045Dd190BeE36D5748F

How do I claim my money Sent from my iPhoneOn Apr 28, 2023, at 8:58 PM, Mewjaden @.***> wrote:
0xA7A72E26b76dd899b5A77045Dd190BeE36D5748F
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


[Help wanted]To use Toggle and Swipe together.

Hi i am trying to use toggle and swipe option. Can you help me how to initialize?

Duplicate of #145. Please subscribe over there—thanks!


Sha1 runtime insecure

Attempt to solve issue #656
Fallback from bogus to insecure, if crypto library returned specific error during verification.

Any comments for this change?

As I understand this is also related to FIPS. Why not just do something similar as #671 with detecting FIPS mode for the digest? Then we won't have to rely on the openssl error code for detection (which I cannot find proper documentation for its actual meaning and the stability of its use).

The reason for it is simple. It does happen on CentOS 9 Stream and RHEL 9 in default installation. Unlike PR #671 this does not fail only when FIPS mode is enabled. It fails also when DEFAULT crypto-policy is set. Which is preselected policy on mentioned distributions.
Of course it would fail in FIPS mode too. But it is more general, because it has to be. There's a note about that in Considerations in adopting RHEL 9. And related release note mention that unbound package build currently disables all SHA-1 validation in all cases. This change would allow secure resolution of SHA-1 base name in legacy policies, but at least insecure resolution in default policy or FIPS mode.
There is pull request to enable simple check to openssl, but until that is present in openssl, it is not that simple.
Also it is good to note, it would affect both our official packages and also unofficial builds, as long as they link to openssl.


Implement metacom version 3 specs

Refs: https://github.com/metarhia/Contracts/blob/master/doc/Metacom.md

Landed in https://github.com/metatech-university/NodeJS-Pure/commit/fd50d0512b4df88e62bcd5da940dd99cbc248a80 and https://github.com/metatech-university/NodeJS-Pure/commit/f98d28b09aff13e52e7ee5c0715eb42bd6989182


Timeout is not taken into account when using Datadriver concept.

While using data-driven approach as well as templates the timeout configured in the testcase is not taken into account.
taking this example, the testcases will be passed as if i didn't set a timeout despite that i'm configuring it for 5 seconds.
*** Settings ***

Library    DataDriver    file=data.csv
Variables    dynamic_test_naming.py    ${SUITE_NAME}
Test Template   TTM25_LCE_355_keyword

# Test Timeout    5 seconds

*** Test Cases ***
TTM25_LCE_355
    [Setup]   Sleep    1
    [Teardown]    Sleep    1
    [Timeout]    5
    ${szl}

*** Keywords ***
TTM25_LCE_355_keyword
    [Arguments]    ${szl}
    Sleep    10

@Eya-Mh
Which version do you have of DataDriver?
There was this issue in 1.6.1 but that is fixed.
Please update to 1.7.0
Regards

@Snooz82 Thank you, i have upgraded to the last version and the problem is solved.


feat: test native tracer

Resolves #414

Blocking issue to resolve first https://github.com/0xPolygonZero/zk_evm/issues/448


Download

Steps to reproduce
Not able to download any anime or movie
Expected behavior
Download should start
Actual behavior
Download starts and stick to 0 Percent
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 11
Device
Phone Vivo v15
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

I'm facing the same issue.. Videos are downloading when download location is Internal storage but fails when storage is set to external sd card.


Airspeed sensor  ( MS5611 ) reading varies up to 3m/s in a closed room

Hi,
I use a holybro speed sensor MS5611 and notice very large fluctuations of the airspeed measurements in idle mode (closed room). I have recalibrated this sensor several times. The result is always the same. Unfortunately there is no second sensor available for comparison. A comparison with a SDP3 from drotek shows a better behaviour. But I also see artefacts in this log.
Question: Is the sensor defective or were there changes in 1.9beta that cause this? I see that the MS5611 was added after the 1.8.2 release.
Software: Px4 version 1.9beta
Hardware: Holybro Pixhawk 4
https://review.px4.io/plot_app?log=5a97e051-a43a-455d-bbf9-1dfba47c2bc9
https://review.px4.io/plot_app?log=b072ef9c-2f10-4b69-a17f-5b6c906364e4

Negative Airspeed, never saw this with SDP3.

These sensors work completely differently - the MS5611 measures differential pressure while the SDP3 measures the cooling of a CMOS element by passing air molecules (the pitot in the case of the SDP3 is "leaking" for this purpose, which also explains why it needs a matched / calibrated pitot).
That also means they have completely different noise characteristics. What you are seeing is the effect of the square root in the airspeed formula:
https://en.wikipedia.org/wiki/True_airspeed#Calculating_true_airspeed
It means that with increasing speed, your relative noise level and steady state error goes down, as the same pressure offset and noise (absolute) translates to an ever-decreasing velocity error. And for the same reason negative airspeed makes sense: The sensor is oscillating around zero (the calibrated value). The filter will reject these measurements though.

@LorenzMeier, Thank you Lorenz for the detailed explanation. The reason I raised this was on the fact that I did some trials with a bungee start of a Phantom Wing, which was not successful. To reduce the damage I did tests just "shooting" the plane in the air without the motor. The launch trigger was detected, but the Wing-wing (px4)  did not try to give any pitch in the starting phase. Thomas Stastney looked at the log and he raised the suspicion, the airspeed sensor could be the culprit. So I looked at this sensor and compared it with SDP3.

We see negative airspeed all the time on the sdp3 units and the interesting thing is that while Lorenz is completely correct about their low speed performance, from a practical standpoint one can tolerate more of an error at higher speeds since in fixed wing we won’t fall out of the sky if going x percentage faster or slower when at cruise speed but at min or stall speed, we need to be on the mark. That’s the benefit we’ve seen with the sdp3 units but they are a pain to work with initially.

I am unsure about the matched/calibrated pitot though. So long as the tube length is entered and kept at 1.5mm I.D. and the pitots are kept the same, when next to each other, we get the same readings when testing but I gather that’s what @lorenz meant about calibrated pitots (correct me if I’m wrong please so I can ask for some different types of testing to be done).

@ryanjAA In theory it also depends on the type of pitot tube, yes, the ID should be 1.5mm and you need to set up CAL_AIR_TUBELEN as precisely as possible.

I would be willing to do a test without a pitot. Would this mean just take a tube which a entry hole of (lets say 1mm diameter? and do a calibration.

Thanks @lorenzmeier makes sense. @jstrebel Lorenz can better answer that since there is some black box magic (ie a pressure drop model implemented for the sensor). I believe this is more of a flow sensor, not differential pressure sensor but I’m not sure if the model works without the difference between the readings from the static and dynamic ports from the pitot. Just get a steady wind source (fan or otherwise) and do some basic bench testing first (although I’m sure Lorenz, reading through the model if it’s available or whomever wrote the model may know quite quickly. Compare the non pitot with readings from with a pitot or from another sensor. Would be interested to know.

Minor correction for anyone that stumbles across this later. The Holybro sensor is an MS4525 differential pressure sensor, not an MS5611 (a barometric pressure sensor).


[To rel/0.11] Add max direct memory size parameter to env.sh

Description
Currently the non-heap memory is out of our control. We add a java runtime parameter to get some control of it.

This PR has:

[ ] been self-reviewed.

[ ] concurrent read
[ ] concurrent write
[ ] concurrent read and write

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods.
[ ] added or updated version, license, or notice information
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious
for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold
for code coverage.
[ ] added integration tests.
[ ] been tested in a test IoTDB cluster.

Key changed/added classes (or packages if there are too many classes) in this PR
Startup script

Windows bat fixed~


[Discussion] Could not find a version that satisfies the requirement tensorflow==2.3.0 (from spleeter)

I've been trying to install spleeter obviously the native version and when I try to install with cmd "pip3 install spleeter"
I get this error message.
ERROR: Could not find a version that satisfies the requirement tensorflow==2.3.0 (from spleeter)
ERROR: No matching distribution found for tensorflow==2.3.0
Not sure what to do to fix this

Hi @Gseasoning,
I cannot reproduce your issue. What OS are you using ? What version of python ?

I ran into the same issue when using Python 3.9. Tensorflow 2.3.0 only supports Python 3.8, so I downgraded to Python 3.8 and was able to install everything.

Indeed spleeter is only compatible with python 3.6 to 3.8, mainly for dependancies such as tensorflow not compatible with later versions.


2.7.1 release

What is the purpose of the change
XXXXX
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #3683 into master will decrease coverage by 0.07%.
The diff coverage is 31.12%.

@@             Coverage Diff              @@
##             master    #3683      +/-   ##
============================================
- Coverage     63.44%   63.37%   -0.08%
  Complexity       71       71
============================================
  Files           703      704       +1
  Lines         31000    31069      +69
  Branches       5024     5039      +15
============================================
+ Hits          19669    19690      +21
- Misses         9066     9103      +37
- Partials       2265     2276      +11

Impacted Files
Coverage Δ
Complexity Δ

.../apache/dubbo/remoting/etcd/jetcd/JEtcdClient.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...gcenter/support/etcd/EtcdDynamicConfiguration.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...onfigcenter/consul/ConsulDynamicConfiguration.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../support/etcd/EtcdDynamicConfigurationFactory.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...a/org/apache/dubbo/registry/etcd/EtcdRegistry.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ubbo/remoting/etcd/support/AbstractEtcdClient.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../dubbo/remoting/etcd/jetcd/JEtcdClientWrapper.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...annotation/ServiceAnnotationBeanPostProcessor.java
82.48% <100%> (+1.18%)
0 <0> (ø)
:arrow_down:

...ontext/annotation/DubboConfigBindingRegistrar.java
93.1% <100%> (+0.37%)
0 <0> (ø)
:arrow_down:

.../annotation/DubboConfigConfigurationRegistrar.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

... and 20 more

Continue to review full report at Codecov.

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

Please do not do things like this. After the 2.7.1-release is released, the release manager will merge it into master branch.  I am closing this pull request for now.