OSX arm errors

M1 macs give error clang: error: the clang compiler does not support '-march=native' if makefile contains ARM_FLAGS = -march=native.
Compiling gives a warning:
In file included from ../src/sqlite3mc.c:91:
../src/sqlite3patched.c:15677:22: warning: redefinition of typedef 'PgHdr' is a C11 feature [-Wtypedef-redefinition]
typedef struct PgHdr PgHdr;
                     ^
../src/sqlite3patched.c:10384:22: note: previous definition is here
typedef struct PgHdr PgHdr;

I created xmake file to compile the shared library, no errors with this.
-- xmake -rv -F sqlitemc-xmake.lua
-- build files are in: build/macosx/arm64/release/libsqlite3mc.dylib (build/{{os}}/{{arch}}/release)
-- NOTE: 'SQLITE_USE_URI' will cause shared database not to work, tempfile is not created
--
add_rules("mode.release")
	target("sqlite3mc")
	add_ldflags("-lpthread", "-ldl", "-lm")
	add_shflags("-lpthread", "-ldl", "-lm")
	set_kind("shared")
	add_files("src/sqlite3mc.c")
	set_languages("c99")
	set_optimize("fastest")
	add_defines('SQLITE_ENABLE_RTREE', 'SQLITE_ENABLE_GEOPOLY', 'SQLITE_ENABLE_FTS4', 'SQLITE_ENABLE_FTS5', 'SQLITE_ENABLE_EXPLAIN_COMMENTS',
							'SQLITE_ENABLE_DBPAGE_VTAB', 'SQLITE_ENABLE_STMTVTAB', 'SQLITE_ENABLE_DBSTAT_VTAB', 'SQLITE_ENABLE_SESSION',
							'SQLITE_ENABLE_JSON1', 'SQLITE_ENABLE_MATH_FUNCTIONS')
	add_defines('SQLITE_SOUNDEX', 'SQLITE_ENABLE_COLUMN_METADATA', 'SQLITE_ENABLE_DESERIALIZE', 'SQLITE_ENABLE_EXTFUNC', 'SQLITE_ENABLE_CARRAY')
	add_defines('SQLITE_ENABLE_CARRAY', 'SQLITE_ENABLE_FILEIO', 'SQLITE_ENABLE_SERIES', 'SQLITE_ENABLE_UUID', 'SQLITE_ENABLE_REGEXP')
	add_defines('SQLITE_DQS=0', 'SQLITE_MAX_ATTACHED=10', 'SQLITE_ENABLE_FTS3', 'SQLITE_ENABLE_FTS3_PARENTHESIS', 'SQLITE_CORE',
							'SQLITE_ENABLE_CSV')
	add_defines('SQLITE_TEMP_STORE=2', 'SQLITE_ENABLE_SHA3', 'SQLITE_USER_AUTHENTICATION')
	-- add_defines('SQLITE_THREADSAFE=0', 'SQLITE_SECURE_DELETE=0') -- disabled for performance
	-- add_defines('SQLITE_ENABLE_PREUPDATE_HOOK')

M1 macs give error clang: error: the clang compiler does not support '-march=native' if makefile contains ARM_FLAGS = -march=native.

Unfortunately, I don't have access to a M1 mac system. Under Linux it is necessary to specify -march=native, so that the compiler actually compiles the code for AES hardware support without error messages. Maybe clang simply doesn't need this flag.

Compiling gives a warning:
In file included from ../src/sqlite3mc.c:91:
../src/sqlite3patched.c:15677:22: warning: redefinition of typedef 'PgHdr' is a C11 feature [-Wtypedef-redefinition]
typedef struct PgHdr PgHdr;
                     ^
../src/sqlite3patched.c:10384:22: note: previous definition is here
typedef struct PgHdr PgHdr;

Thanks for reporting. I will fix this warning for the next release.

Adding -march=native is not a good solution when the program should run on customers' computers also. After testing in windows using msys2 I found that adding the following defines were enough to make it compile.
	add_cflags("-msse4.2", "-maes")

I created a windows make build. I copied sqlite3mc.def to main level and modified it because I had added SQLITE_THREADSAFE=0 and it caused errors on missing mutex functions to be exported.
-- xmake f -p mingw -F sqlitemc-xmake.lua
-- xmake -rv -F sqlitemc-xmake.lua
-- build files are in: build/mingw/x86_64/release/libsqlite3mc.dylib

add_rules("mode.release")
	target("sqlite3mc")
	add_cflags("-msse4.2", "-maes") -- add_cflags("-march=native")
	add_ldflags("-lpthread", "-lm")
	add_shflags("-lpthread", "-lm")
	add_shflags("sqlite3mc.def", {force = true})
	set_kind("shared")
	add_files("src/sqlite3mc.c", "src/sqlite3mc.rc")
	set_languages("c99")
	set_optimize("fastest")
	add_defines('SQLITE_ENABLE_RTREE', 'SQLITE_ENABLE_GEOPOLY', 'SQLITE_ENABLE_FTS4', 'SQLITE_ENABLE_FTS5', 'SQLITE_ENABLE_EXPLAIN_COMMENTS',
	            'SQLITE_ENABLE_DBPAGE_VTAB', 'SQLITE_ENABLE_STMTVTAB', 'SQLITE_ENABLE_DBSTAT_VTAB', 'SQLITE_ENABLE_STAT4',
	            'SQLITE_OMIT_AUTOINIT', 'SQLITE_DEFAULT_MEMSTATUS=0', 'SQLITE_ENABLE_UNLOCK_NOTIFY', 'SQLITE_ENABLE_SESSION',
	            'SQLITE_ENABLE_JSON1', 'SQLITE_ENABLE_MATH_FUNCTIONS', 'SQLITE_SOUNDEX', 'SQLITE_ENABLE_COLUMN_METADATA',
	            'SQLITE_ENABLE_DESERIALIZE', 'SQLITE_ENABLE_EXTFUNC', 'SQLITE_ENABLE_CARRAY', 'SQLITE_ENABLE_FILEIO', 'SQLITE_ENABLE_SERIES',
	            'SQLITE_ENABLE_UUID', 'SQLITE_ENABLE_REGEXP', 'SQLITE_DQS=0', 'SQLITE_CORE', 'SQLITE_ENABLE_CSV', 'SQLITE_TEMP_STORE=2',
	            'SQLITE_USE_URI')
	-- add_defines('SQLITE_THREADSAFE=0', 'SQLITE_SECURE_DELETE=0') -- disable for performance
	add_defines('SQLITE_ENABLE_SHA3', 'SQLITE_USER_AUTHENTICATION') -- encrypted database
	-- add_defines('SQLITE_ENABLE_PREUPDATE_HOOK', 'SQLITE_ENABLE_FTS3', 'SQLITE_ENABLE_FTS3_PARENTHESIS')

Adding -march=native is not a good solution when the program should run on customers' computers also. After testing in windows using msys2 I found that adding the following defines were enough to make it compile.
	add_cflags("-msse4.2", "-maes")

Actually, the build files coming with SQLite3 Multiple Ciphers use exactly these flages, when the platform is a x86 one.
Only for ARM platforms the flag -march=native is used.
At least for gcc the flags -maes and -msse4.2 are listed as i86 options - and they are required to enable the compiler to properly compile AES hardware support.
For ARM targets however, I'm not sure whether any specific flags are required to enable NEON support which includes AES hardware support.


Allow --link name to start with a number

It would be nice to run docker run -it codercom/code-server:latest --link and not have to specify an argument to link. However this will fail most of the time with Name must conform to regex ^[a-z][a-z0-9_]{0,50}$ because --link defaults to host name (I think), and docker host names start with a number more often than they start with a letter.

cc @sreya

We can strip leading numbers before passing to the cloud agent but I agree, I don't see a good reason why leading numbers shouldn't be allowed.

This has already been fixed server-side, should be fixed in the next release for code-server

Awesome!

Marking this as fixed then, just need to mention it in the release notes.


SSL support

I've had WatsonWebserver running for a while without SSL. It's pretty common to run webservices (even simple ones) under SSL nowadays. I've set the boolean in the constructor to true but I have no way to specify a certificate. Is there any how-to on this specific topic?
Thanks.

Hi Malalicious, thanks for filing this.  SSL certificates must be bound in the operating system beneath the server.  For Windows, use netsh http (see https://msdn.microsoft.com/en-us/library/ms733791(v=vs.110).aspx), and for Mono, use certmgr and mozroots (see http://www.mono-project.com/docs/faq/security/).
Which OS are you using?
Cheers,
Joel

Hi Malalicious, please let me know if this is helpful.  Closing the issue but if you feel I need to add more, let me know and I'll reopen it!  Thanks!   https://github.com/jchristn/WatsonWebserver/wiki/Using-SSL-on-Windows


Buffer initdb.tar.zst to a temporary file before upload

I'm not really sure it is needed but in https://github.com/neondatabase/neon/pull/5912#pullrequestreview-1749982732 , Christian liked the idea of using files instead of buffering the archive to RAM for the download path. This is for the upload path, which is probably a very similar situation.

This PR has lower priority as it doesn't deliver a feature, and the load in terms of memory is pretty low anyways. Any pageserver equipped with >4 GiB can do thousands of initdb upload requests in parallel.


PowerManager.EnergySaverStatusChanged throws InvalidCastException

Describe the bug
Attaching a event handler to the PowerManager.EnergySaverStatusChanged-event throws an InvalidCastException:
0:013> !clrstack
OS Thread Id: 0x3fe0 (13)
        Child SP               IP Call Site
000000722D83C988 00007fff53c3466c [HelperMethodFrame: 000000722d83c988]
000000722D83CA80 00007ffe5d084044 WinRT.ExceptionHelpers.ThrowExceptionForHR(Int32)
000000722D83CAC0 00007ffe5d08181f WinRT.IWinRTObject.IsInterfaceImplementedFallback(System.RuntimeTypeHandle, Boolean)
000000722D83CE20 00007ffe5d080cd6 WinRT.IWinRTObject.System.Runtime.InteropServices.IDynamicInterfaceCastable.IsInterfaceImplemented(System.RuntimeTypeHandle, Boolean)
000000722D83CE50 00007ffebaf66f08 System.Runtime.InteropServices.DynamicInterfaceCastableHelpers.IsInterfaceImplemented(System.Runtime.InteropServices.IDynamicInterfaceCastable, System.RuntimeType, Boolean) [/_/src/coreclr/src/System.Private.CoreLib/src/System/Runtime/InteropServices/DynamicInterfaceCastableHelpers.cs @ 16]
000000722D83D128 00007ffebc43a7a3 [HelperMethodFrame_1OBJ: 000000722d83d128]
000000722D83D230 00007ffebaf744dc System.Runtime.CompilerServices.CastHelpers.ChkCast_Helper(Void*, System.Object) [/_/src/coreclr/src/System.Private.CoreLib/src/System/Runtime/CompilerServices/CastHelpers.cs @ 374]
000000722D83D270 00007ffebaf74550 System.Runtime.CompilerServices.CastHelpers.ChkCastInterface(Void*, System.Object) [/_/src/coreclr/src/System.Private.CoreLib/src/System/Runtime/CompilerServices/CastHelpers.cs @ 417]
000000722D83D2A0 00007ffe5d77c5e3 WinRT.EventSource`1+Cache[[System.__Canon, System.Private.CoreLib]].Create(WinRT.IObjectReference, Int32, System.WeakReference`1<State<System.__Canon>>)
000000722D83D340 00007ffe5d77c0c0 WinRT.EventSource`1[[System.__Canon, System.Private.CoreLib]].Subscribe(System.__Canon)
000000722D83D410 00007ffe5d9b0e58 ABI.Windows.System.Power.IPowerManagerStatics.global::Windows.System.Power.IPowerManagerStatics.add_EnergySaverStatusChanged(System.EventHandler`1<System.Object>)
000000722D83D450 00007ffe5d9b09b5 Windows.System.Power.PowerManager.add_EnergySaverStatusChanged(System.EventHandler`1<System.Object>)

To Reproduce

Open VS 2019 and create a new console app-solution.
Add a Packaging Project-project to the solution and reference the console app.
Set TFM to 19041: <TargetFramework>net5.0-windows10.0.19041.0</TargetFramework>
In Program.cs, add an event handler: PowerManager.EnergySaverStatusChanged += PowerManager_EnergySaverStatusChanged;
Run and break on InvalidCastException. You may have to disable Just My Code.

Expected behavior
The delegate should be added to PowerManager.EnergySaverStatusChanged, without throwing any exceptions.
Version Info
Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22000
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.100-rc.2.21505.57\

Host (useful for support):
  Version: 6.0.0-rc.2.21480.5
  Commit:  6b11d64e7e

.NET SDKs installed:
  3.1.401 [C:\Program Files\dotnet\sdk]
  5.0.402 [C:\Program Files\dotnet\sdk]
  6.0.100-rc.2.21505.57 [C:\Program Files\dotnet\sdk]

Additional context
Repro: ConsoleApp5.zip
Affects all Microsoft.Windows.SDK.NET.Ref builds after 10.0.x.20, from 17763 to 22000. SDK 10.0.x.19 runs without issues:
<ItemGroup>
  <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref"
                      RuntimeFrameworkVersion="10.0.19041.19" />
  <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref"
                      TargetingPackVersion="10.0.19041.19" />
</ItemGroup>

Are there any workarounds for this? I'm unable to set FrameworkReference for transient deps targetting the windows SDK.

@trympet Can you confirm whether this is a first chance exception and that you able to click continue and observe it doesn't actually crash (the exception is caught) and the event it still registered?  If that is the case, then I believe this is from our IWeakReference cast and we have a change that would address this in an upcoming release.  In the meantime, if this exception is noisy, you might be able to disable first chance exceptions for InvalidCastException in exception settings.

Fixed as part of https://github.com/microsoft/CsWinRT/pull/997


a required input field with focus should not show an error on click of cancel btn

Cancel button definition used:
<button class="btn btn-primary" type="button" style="margin-left: 10px;">Cancel</button>

When you click Cancel, the required input is losing focus which triggers the error display. It will show an error no matter where else you click if you leave the input empty.

I know. But that is not what you want, you don't want to push the cancel button two times. It is user-unfriendly. My javascript knowledge is not yet enough to point you to a solution, it should be something like on blur: if (last event == cancel button click) {thisevent.preventdefault}

Sounds like you're running into the same issue as #443 where the error appears and pushes the button out from underneath your mouse cursor.

Is your suggestion "Make your .help-blocks take up space even when they're empty."? Does this mean inserting f.e. a space in the div, like below?

I tried that, but it does not work. The issue still exists.

I mean something like using min-height: 1.2em on your help-block or position: absolute to remove it from the layout flow so that the on-screen position of your buttons isn't affected by errors appearing.

Thanks a lot! I tried min-height: 1.2em, that works.


version 4.1.1 error - undefined object

Undefined symbols for architecture i386:
"_CACurrentMediaTime", referenced from:
___42-[Base64ToGallery saveImageDataToLibrary:]_block_invoke in Base64ToGallery.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)

After updated to 4.1.1, I found this error. Hope someone could look into this, thank you.

@kby799 do you have additional information from log?

** BUILD FAILED **
The following build commands failed:
Ld /volumes/helloWorld/ionic/final/working\ version/simple-login/platforms/ios/build/emulator/HelloWorld.app/HelloWorld normal i386
(1 failure)
Error code 65 for command: xcodebuild with args: -xcconfig,/volumes/helloWolrd/ionic/final/working version/simple-login/platforms/ios/cordova/build-debug.xcconfig,-project,HelloWorld.xcodeproj,ARCHS=i386,-target,HelloWorld,-configuration,Debug,-sdk,iphonesimulator,build,VALID_ARCHS=i386,CONFIGURATION_BUILD_DIR=/volumes/helloWorld/ionic/final/working version/simple-login/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/volumes/helloWorld/ionic/final/working version/simple-login/platforms/ios/build/sharedpch
Error: /volumes/helloWorld/ionic/final/working version/simple-login/platforms/ios/cordova/build: Command failed with exit code 2

This is all I have

@kby799 You can try to update or re-add cordova-ios with version 4.0.0:
cordova platform add<EMAIL_ADDRESS>and try to remove platform and re-add or run ionic build ios.
Thanks


Dev/alha

I'm a little concerned about port being a string (not an int) and the validation that we do. Could you please test some common error scenarios and make sure that the logs reflect the user error.

Added error handling to ensure that the value is a parseable integer. If it is not, an error is shown and the default port of 8883 is used. Values like "shark" or "8883a" will be caught and result in the warning message and default port usage.


[Bug Report]: farm watch doesn't copy /public contents to /dist

Steps to reproduce
Put in any item in the public directory and see that it does get copied over when running farm build but not when running farm watch
Reproduce link
No response
What is actually happening?
I need to have files on disk for my web extension, I have a manifest.json in the public directory. This doesn't get copied over so the extension crashes when using farm watch. Using the farm build -w command does work for now.
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (6) x64 AMD Ryzen 5 4500U with Radeon Graphics
    Memory: 4.94 GB / 15.37 GB
  Binaries:
    Node: 22.5.1 - ~\scoop\apps\nodejs\current\node.EXE
    Yarn: 1.22.22 - ~\scoop\apps\yarn\current\bin\yarn.CMD
    npm: 10.8.2 - ~\scoop\apps\nodejs\current\npm.CMD
    pnpm: 9.6.0 - ~\scoop\shims\pnpm.EXE
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @farmfe/core: ^1.3.0 => 1.3.12

we will support copy public when running farm watch


Support for AuraFlow

Can you add any support for AuraFlow? (Preferably SD LoRas to AuraFlow checkpoint at least)

Doesn't this also just use the SDXL VAE? Selecting XL should make it work.
https://huggingface.co/fal/AuraFlow/blob/main/vae/diffusion_pytorch_model.fp16.safetensors
https://huggingface.co/stabilityai/stable-diffusion-xl-base-1.0/blob/main/vae/diffusion_pytorch_model.fp16.safetensors

This repo is only for converting the latents between models for doing img2img on the output of one model with a second model that uses a different latent space.
What you're thinking of is X-Adapter but I have no clue if it exists for AuraFlow.


Have apply return single column array when cols is a single column name

The non-mutating apply in transformers.jl always returns a vector of the transformed columns specified in cols. cols is assumed to be a collection.
For convenience, we could add that if cols is a single column name (e.g. a String or Symbol rather than a collection of them), we return the single column vector, rather than wrapping it in a 1-element vector.

To avoid confusion can you elaborate on the issue description? maybe add a MWE of what you intend to implement?

I added a MWE of what I'm advocating for.


Json11 fails to build with clang 4.0.0

json11 fails to build with clang 4.0 likely due to llvm-mirror/clang@4b6ad14
% /usr/bin/clang -v
FreeBSD clang version 4.0.0 (branches/release_40 292009) (based on LLVM 4.0.0)
Target: x86_64-unknown-freebsd12.0
Thread model: posix
InstalledDir: /usr/bin

ext/json11/json11.cpp:153:24: error: invalid operands to binary expression
      ('nullptr_t' and 'nullptr_t')
        return m_value < static_cast<const Value<tag, T> *>(other)->m_value;
               ~~~~~~~ ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ext/json11/json11.cpp:209:5: note: in instantiation of member function
      'json11::Value<json11::Json::Type::NUL, nullptr_t>::less' requested here
    JsonNull() : Value(nullptr) {}
    ^

Also reported here: https://github.com/PowerDNS/pdns/issues/4913

You're right that this seems to have been an intentional compiler change.  I think the relevant commit is actually llvm-mirror/libcxx@e577a4c6 which removes operator< from nullptr_t.  Seems like this was changed intentionally in the standard, at the same time as the broader comparison change you referenced.  My digging found DR 583 which was resolved along with issue 1512 which was resolved by this wording in the standard.  At the end, nullptr_t is being specifically redefined to have fewer built-in operators.
That's a bit inconvenient since it breaks the nice symmetry of the use of nullptr_t in JsonValue, but it doesn't affect anything public so it shouldn't be impossible to hack around.  I haven't thought about it in detail, but you could likely do it by defining NullValue without using the Value template.  Or you might make Value work by replacing nullptr_t with a helper struct which is comparable and castable to nullptr_t.  Or there might be a more clever option.  @j4cbo any thoughts?
@cpu82 do you want to take a stab at this an send a PR, or are you looking for someone else to do it?

I like the helper struct idea. It doesn't need to be castable to nullptr_t, just comparable with itself.

It builds fine after replace nullptr_t with the new empty struct.
@j4cbo thanks for the patch.


Bump grunt version to 1.4.1

@AidasK: I created this patch that i think could work like a charm but actually i see that tests seems to not start.
Probably its due to the fact that we still need to migrate from travis-ci.org to travis-ci.com.
Will try to check on this later.

Okay the builds are now working again but actually the pull requires some adjustments.
Just by curiosity i wanna try to bump all the dependencies and see if it works or which library will fail.


[MB-7404] As the job runner, I need to call the EDI response processor service

Description
In PR #6163 we created a service in pkg/services/invoice/syncada_sftp_reader.go to read files from an SFTP directory, process them, and delete files that were successfully processed. In that PR, a CLI utility was also added for manual testing. The CLI used a generic processor, but now uses the specific NewEDI997Processor and NewEDI824Processor processors.
Reviewer Notes
Suggestions for more robust logging.
Setup
make db_dev_fresh

make server_run

# in another terminal
make client_run

Create a move with a payment request, and approve the payment request as a TIO.
Send EDIs for all reviewed payment requests to Syncada with:
{
  "body": {
    "sendToSyncada": true
  }
}

prime-api-client --insecure support-reviewed-payment-requests --filename sendtosyncada.json

Download files from Syncada
go run ./cmd/fetch-from-syncada-via-sftp  --directory /CSFTP866/Pickup/

You should see some EDI files logged.
If you delete the files with:
go run ./cmd/fetch-from-syncada-via-sftp  --directory /CSFTP866/Pickup/ --delete-after-processing

and then run again, you shouldn't see any more files logged.
References

Jira story for this change

Messages

:book:
:link: MB-7404

  Generated by :no_entry_sign: dangerJS against 8b7ca2601712ef44e6ae5c3bdc3b73b584773b2d


Toolkit Reports not showing up

When I click on Toolkit Reports it flashes real quick on my screen and then disappears.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. OSX, Windows]
Browser [e.g. chrome, firefox]
Toolkit Version [e.g. 2.22.0]

Setting Export
Please replace the text 'REPLACE_ME_WITH_SETTINGS' below with your exported Toolkit settings. You can export these by going to the Toolkit Options page, click the Import/Export Settings button at the top right and copying the text in the modal which appears.
Note! DO NOT replace the leading and trailing ``` characters as they are required formatting characters.
REPLACE_ME_WITH_SETTINGS

Same thing happening here

Same here. I get this in the dev console (Firefox) when I click on Toolkit Reports:
TypeError: expenseMonthData is undefined
    _normalizeNetIncomes moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:62905
    _normalizeNetIncomes moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:62901
    _calculateData moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:62765
    componentDidUpdate moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:62707
    lk moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1712
    jk moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1711
    ik moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1710
    Xk moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1734
    Qk moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1732

I also have this issue

Having this same exact problem after filtering out a category and changing the months covered. Here are the errors that are raised in the browser console.
TypeError: Cannot read properties of undefined (reading 'total')
    at ynab-toolkit.js:62905:65
    at Array.map (<anonymous>)
    at IncomeVsExpenseComponent._normalizeNetIncomes (ynab-toolkit.js:62901:37)
    at IncomeVsExpenseComponent._calculateData (ynab-toolkit.js:62765:42)
    at IncomeVsExpenseComponent.componentDidUpdate (ynab-toolkit.js:62707:18)
    at lk (ynab-toolkit.js:1712:316)
    at jk (ynab-toolkit.js:1711:446)
    at ik (ynab-toolkit.js:1710:431)
    at Xk (ynab-toolkit.js:1734:96)
    at Qk (ynab-toolkit.js:1732:398)

Toolkit Error:
  - Feature: unknown
  - Feature Setting: unknown
  - Function: global
  - Message: Cannot read properties of undefined (reading 'total') TypeError: Cannot read properties of undefined (reading 'total')
    at chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:62905:65
    at Array.map (<anonymous>)
    at IncomeVsExpenseComponent._normalizeNetIncomes (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:62901:37)
    at IncomeVsExpenseComponent._calculateData (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:62765:42)
    at IncomeVsExpenseComponent.componentDidUpdate (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:62707:18)
    at lk (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1712:316)
    at jk (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1711:446)
    at ik (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1710:431)
    at Xk (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1734:96)
    at Qk (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1732:398)

ynab-toolkit.js:62905 Uncaught TypeError: Cannot read properties of undefined (reading 'total')
    at ynab-toolkit.js:62905:65
    at Array.map (<anonymous>)
    at IncomeVsExpenseComponent._normalizeNetIncomes (ynab-toolkit.js:62901:37)
    at IncomeVsExpenseComponent._calculateData (ynab-toolkit.js:62765:42)
    at IncomeVsExpenseComponent.componentDidUpdate (ynab-toolkit.js:62707:18)
    at lk (ynab-toolkit.js:1712:316)
    at jk (ynab-toolkit.js:1711:446)
    at ik (ynab-toolkit.js:1710:431)
    at Xk (ynab-toolkit.js:1734:96)
    at Qk (ynab-toolkit.js:1732:398)

Found a way to recover:
On Chrome navigate to the developer toolkit -> Application -> Local Storage and search for: ynab-toolkit-active-report.
Delete this entry and you should be able to see the Toolkit again.

Thanks @erebks the same works in Firefox using the dev console there as well.

Thanks @erebks the same works in Firefox using the dev console there as well.

Until we click on Income vs Expense again.

Yes that worked momentarily, but when I click on the "Income vs. Expense" icon it causes the screen to go blank again.

I'm getting the same error here. Fixable in the console, happens again when clicking Income vs. Expense.

Juts throwing out there same thing, fixes with @erebks suggestion, but breaks again when you go to income and expense

Same issue

Commenting to add mine as well.
I did remember that I was messing around in my data view and selected "none" either in the categories or accounts selector options, not sure which but hopefully that might help narrow it down.

in addition to what @erebks suggested, also delete the record found when searching "income-vs-expense-category-filters" this allows you to go back into the income and expenses

This fixes clicking on Income v Expense messing the reports up again. Thanks!

Similar to @Bilbyj, I can't find any of these entries by filtering within Local Storage. Deleting the entire http://app.ynab.com entry in Local Storage works to access Toolkit Reports again, but does not reset Income v. Expense.

I just reported the same issue today for these reports appearing for a second or less and then disappearing...Help

After adding my findings about #3425, I skimmed through a few other reported issues. It appears that #3414, #3430, and #3425 are all reporting the same issue where the Toolkit Reports stop working after the user clicks on the Income and Expenses tab. So, I'm going to post this comment on all 3 so that everyone looking at them knows they're related.

I'm having the same issue.

I believe this problem was fixed and released in v3.13.1, so I'm going to close this issue.
If problem still persist, please feel free to reply and I'll reopen the issue


Deploying Vistio-API fails with 'PersistentVolumeClaim is not bound: "vistio-db-vistio-api-0" (repeated 4 times)'

The PVC claim just sits in a pending state and at API doesn't come up successfully, the Web UI just sits there "Loading".
kubectl version shows:
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:17:28Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Where is your Kubernetes cluster deployed? Vistio by default assumes that you have a Kubernetes StorageClass named standard
Example of mine
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: standard
parameters:
  type: gp2
provisioner: kubernetes.io/aws-ebs

In AWS, we will eventually move to EKS, but the current cluster was spun up using kops.

From: Nick<EMAIL_ADDRESS>Sent: Monday, July 16, 2018 5:53 PM
To: nmnellis/vistio
Cc: Gary Sumner; Author
Subject: Re: [nmnellis/vistio] Deploying Vistio-API fails with 'PersistentVolumeClaim is not bound: "vistio-db-vistio-api-0" (repeated 4 times)' (#8)
Where is your Kubernetes cluster deployed? Vistio by default assumes that you have a Kubernetes StorageClass named standard
Example of mine
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: standard
parameters:
type: gp2
provisioner: kubernetes.io/aws-ebs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/nmnellis/vistio/issues/8#issuecomment-405424906, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABzuQ537SxVCqg9qi8SGFDIeTLtioF2Vks5uHTWHgaJpZM4VGfQd.

Looks like that might be the issue…here is what my storage classes look like:
<EMAIL_ADDRESS>From: Nick<EMAIL_ADDRESS>Sent: Monday, July 16, 2018 5:53 PM
To: nmnellis/vistio<EMAIL_ADDRESS>Cc: Gary Sumner<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [nmnellis/vistio] Deploying Vistio-API fails with 'PersistentVolumeClaim is not bound: "vistio-db-vistio-api-0" (repeated 4 times)' (#8)
Where is your Kubernetes cluster deployed? Vistio by default assumes that you have a Kubernetes StorageClass named standard
Example of mine
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: standard
parameters:
type: gp2
provisioner: kubernetes.io/aws-ebs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/nmnellis/vistio/issues/8#issuecomment-405424906, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABzuQ537SxVCqg9qi8SGFDIeTLtioF2Vks5uHTWHgaJpZM4VGfQd.

Same error here. K8s deployed with kubeadm.
`kubectl describe pod -n istio-system vistio-api-0
Type     Reason            Age                From               Message

Warning  FailedScheduling  17s (x3 over 33s)  default-scheduler  pod has unbound PersistentVolumeClaims

kubectl get storageclass -n istio-system local-storage -oyaml          ⎈ isobox:tethering
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
creationTimestamp: 2018-07-03T15:48:22Z
name: local-storage
resourceVersion: "601"
selfLink: /apis/storage.k8s.io/v1/storageclasses/local-storage
uid: 841bab8a-7ed8-11e8-ac4d-005056950510
provisioner: kubernetes.io/no-provisioner
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
`

this is more of an issue with statefulsets and pvcs than with vistio. Upgrading your kubernetes version to >=1.9 might help fix this issue

My kube version is v1.10.2

maybe follow this? https://github.com/helm/charts/issues/5188#issuecomment-406447501

Same issue for me, but I'm using NFS so I don't have any StorageClass.

AKS also does not have 'standard', it has 'default'.
$ kubectl get sc
NAME                PROVISIONER                AGE
default (default)   kubernetes.io/azure-disk   5d
managed-premium     kubernetes.io/azure-disk   38d

Works well with rook.
helm install helm/vistio -f helm/vistio/values-with-ingress.yaml --set api.storage.class=rook-ceph-block --name vistio --namespace default

kubectl -n default get pods,svc,pvc -l app=vistio-api,app=vistio-api -o wide

NAME               READY   STATUS    RESTARTS   AGE   IP           NODE     NOMINATED NODE
pod/vistio-api-0   3/3     Running   0          18m   <IP_ADDRESS>   node03   <none>

NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)    AGE   SELECTOR
service/vistio-api   ClusterIP   <IP_ADDRESS>    <none>        9091/TCP   18m   app=vistio-api,release=vistio

NAME                                           STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
persistentvolumeclaim/vistio-db-vistio-api-0   Bound    pvc-b220c7ea-f3ff-11e8-9102-960000143fe3   5Gi        RWO            rook-ceph-block   4h59m

I suggest to not enforce the name of the storageclass.
If left empty ("") PVC will automatically select the (default) storage class.


Add support for type Decimal128.

Add support for new BSON type Decimal128.
Includes a new version of mongodb-driver (3.4.1)

Current coverage is 15.18% (diff: 18.91%)

Merging #137 into devel will decrease coverage by <.01%

@@              devel       #137   diff @@
==========================================
  Files           733        736     +3
  Lines         26311      26345    +34
  Methods           0          0
  Messages          0          0
  Branches       2800       2801     +1
==========================================
+ Hits           3996       4001     +5
- Misses        22042      22071    +29
  Partials        273        273

Powered by Codecov. Last update 861e91c...148ba89


How to inverse transform the regression predicted labels

Hi,
I have tried using numerical_transformer_method (str, optional) : box_cox and quantile_normal.
I get the predictions in a different scale as the original.
How to inverse transform the predictions to original labels?

All numerical transformer methods use scikit-learn under the hood. You should be able to inverse transform by running the inverse_transform function. Refer the Sklearn documentation for more information.
Note that you'll likely have to create another instance of the transformer since iirc it isn't saved anywhere when loading the data.


Text ellipsis for sApp description

What it solves
Resolves #2478
How this PR fixes it
By adding an ellipsis to the description. We show 3 lines (max) and add a ellipsis at the end.
How to test it

Go to the admin panel -> safe apps
add a new app with a very long description

Screenshots

Note to QA: in Chrome/Safari there'll be ... if the text is too long, in Firefox it will just cut the text.


[Layout] component design & spec

Problem

Website guidelines on layout https://www.ibm.com/standards/web/carbon-for-ibm-dotcom/guidelines/layout
VS our current layout component in Web component & React are very different.
This means adopters who are reading the site, would think they can achieve layout xyz, but lack have specific guidance & example on how to achieve it.
We need to enable adopters to do layout successfully on their own
This is part of the initiative to encourage adopter assembling their own layout components, & self serve

Also exist is Wonil's previous content on Layout for Dotcom
https://ibm.ent.box.com/notes/734766657395?s=1lm1zs6zcof4epd5k9i7wbk00o82glsj

Audit Layout guideline page

how to differentiate between Layout guideline and Layout component
identifying outdated content
Identify which layouts are provided in Layout component vs what is "ok" from grid usage perspective
Link to Figma Jam

Meeting scheduled for June 16 with Jeff, Shixie and James (optional)

Two types of Layout
4:12

used in the content section components

8:4

intended to be nested within the 12 of the 4:12 column

It's possible they are making the layouts as they build components, rather than using the layout component

Can we demo the correct layout we want:

Create 4:12 and 8:4
Need to create more modifier classes to use that
Not just making visual adjustments to storybook but we are aligning the component to how the spec is set up
Can deprecate (not remove but not document) the modifiers that we don't want people to use (1–3 : 2–3)

Then we can make the components that need to use layout use it correctly

How do we align the two frameworks and how it's developed?

Get WC straight first: documentation update as a utility
React define that it is a utility, we can not advertise that it is a component.

Let's discuss next steps during huddle

Talked about Layout component in DDS Team Huddle 6/22:

Provide grid code snippet to accompany the content components (in plain carbon grid language)
Layout component is not super useful.
Discuss getting rid of the layout components in both react web comp

Follow up issue has been created #1082, we can consider this done.


[Traefik Plugin Catalog] Plugin Analyzer has detected a problem.

The plugin was not imported into Traefik Plugin Catalog.
Cause:
failed to get the latest tag: invalid tag: 1.0.1 (this tag must be removed, see https://semver.org)

Traefik Plugin Analyzer will restart when you will close this issue.
If you believe there is a problem with the Analyzer or this issue is the result of a false positive, please fill an issue on piceus repository.

tag: 1.0.1 is removed


Add job for running spark funcional testing on native k8s cluster

Closes: # theopenlab/openlab#188

@kiwik @h00130372 what do you think about adding a openlab-dummy empty project for triggering such jobs, which don't need a real project to trigger ?

replace by https://github.com/theopenlab/openlab-zuul-jobs/pull/435


firefox: updates

Motivation for this change
Upstream release day was yesterday.
NSS 3.52.1 instead of 3.53, because it fails to compile with:
In file included from blapi.h:11,
                 from loader.h:11,
                 from loader.c:8:
blapit.h:11:10: fatal error: seccomon.h: No such file or directory
   11 | #include "seccomon.h"
      |          ^~~~~~~~~~~~
compilation terminated.
make[2]: *** [../../coreconf/rules.mk:292: Linux5.4_x86_64_gcc_glibc_PTH_64_OPT.OBJ/loader.o] Error 1
make[2]: Leaving directory '/build/nss-3.53/nss/lib/freebl'
make[1]: *** [../coreconf/rules.mk:44: freebl] Error 2
make[1]: Leaving directory '/build/nss-3.53/nss/lib'
make: *** [coreconf/rules.mk:44: lib] Error 2

cc @andir
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Usually we have that NSS update as part of a staging/staging-next cycle to reduce the amounts of rebuilds on master. Given the severity of some of the issues and it being a dependency of Firefox it might be fine to just land this on master as is. If someone disagrees we can also do it the "normal" way.
I'll spent the afternoon on the backports of this. As of a few days we are only support 20.03 and master IIRC so I'll skip 19.09 but it would probably not be that hard (famous last words).

I expect tomorrow around noon we can start a new staging-next cycle so this can be included then.

I'm not that familiar with the whole staging/staging-next workflow. Is there anything I need to do once the new cycle has been started?

I pushed the nss bump to staging now.  This still does not prevent us from skipping the wait in case the staging-next cycle gets stuck on some hard-to-solve problem.  (I pushed with non-SRI hash, although that change perhaps wasn't really required.)  Actually, this time I see no "critical" security problems, so it seems to be less important than usual :-)

Uh, I forgot to mention it here... and forgot this PR for a while: most of the commits don't need any large rebuild and they can go directly to master.  I pushed those now (better late than later).

I see these commit hashes are linked from 20.03 already, so we merge this PR as-is into current staging-next?

I don't know why @edolstra merged the backport, before this was merged. Since the commits are already referenced on release-20.03, this should probably merged as is.

I think it's good that 20.03 merge to wasn't delayed this long, but we could have merged this whole PR to staging long ago – at the first moment I only took what was necessary (nss).

So I'll just close this then, right?

Won't firefox on master fail because nss is still on staging-next?

firefox would fail, but I didn't push that.  I tested running all those I pushed.


Support for voice messages

Using the OpenAI Whisper model to transcribe voice messages into a request for the bot.

I've thought about it but haven't found a real use case. Would you actually use this feature? Can you describe your use case?

Request on the run, without the ability or desire to use text (for example, during a conversation with another person or on the subway)

But would you really use it that way?

Sometimes during meals - yes)

also useful during holding your kid :D +1

also, forward voice message from another chat to transcript and do something


Update organization-news-site.md

Corrected the maximum number of org news sites a tenant can have from 250 -> 100.

@MikePlumleyMSFT
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Pull out FindPNETCDF CMake module

This also fixes an issue where MPI was not linked when using pnetcdf with a serial HDF5

Pull out all the PnetCDF CMake stuff into a separate module
Make it a configure-time error if ENABLE_PNETCDF is true but PnetCDF not found
Replace include_directories with target_link_libraries for PnetCDF

I noticed that there are three CMake variables that are now always set to the same values as each other: ENABLE/USE/STATUS_PNETCDF. ENABLE is the user configure option, and USE is the internal preprocessor feature macro, so STATUS_PNETCDF could be replaced entirely by ENABLE_PNETCDF

Thanks for the comments @LecrisUT, I think these are all sorted now. Merge conflicts also sorted

I think the failing test here is just a flaky remote test


When a container fails the test result still show it as a passing test.

SMTestRunner doesn't support container failures, we can't do anything for now.

Duplicate of #29


fixfix case of drop index

Proposed changes
Issue Number: close #xxx
before drop index , need wait table NORMAL
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


The initialization the f_template network

Thanks for your awesome work. I noticed that"Once you have an object mesh and the corresponding sphere mesh, use the pre-processing script to initialize the f_template network" Why does it need to initialize the f_template network instead of using the original object mesh as the input?

Hi, f_template is initialized to have the same shape as the mesh. The shape model still needs to learn a mapping from sphere to your initial mesh shape.


Fix bugs introduced mainly to docker-machine driver when we added TLS proxy

:bell: @marcosnils

LGTM!. Minor comment regarding regex. Should we merge as is and improve later?


Explicit GenerateSW or InjectManifest webpack modes

R: @goldhand @prateekbh @gauntface
Fixes #1136
Fixes #1144
There's a lot of refactoring in this PR to move some of the internal methods in workbox-webpack-plugin around, and share logic between the two plugins.
As part of this PR it also made sense for me to change the global default value for globPatterns (defined in workbox-build) from ['**/*.{js,css,html}'] to []. We had introduced a number of overrides to that global default previously, and would have to introduce additional ones here, and it got to the point that defaulting everything to [] seemed cleaner. (Developers going through the workbox wizard onboarding flow won't be affected by this change, since they're explicitly asked which file extensions to precache.)
Assuming this PR is merged, I will put together a follow-up PR to reflect the changes that are needed to the relevant sections of the docs:
https://github.com/google/WebFundamentals/tree/master/src/content/en/tools/workbox/guides/_shared
https://github.com/google/WebFundamentals/blob/master/src/content/en/tools/workbox/modules/workbox-webpack-plugin.md

Coverage increased (+0.8%) to 85.787% when pulling 1aed68d707661ef4f96564f973ce94e26d85876f on explicit-webpack-mode-toggling into d391a0cb51b3e89121c5274fb15f05988233b57e on v3.

I've filed https://github.com/google/WebFundamentals/issues/5567 as a reminder to update the module docs to reflect this new interface and config options.

Coverage increased (+0.8%) to 85.808% when pulling 5adce9a8fb3bd8f017445636d1803d495cf79099 on explicit-webpack-mode-toggling into d391a0cb51b3e89121c5274fb15f05988233b57e on v3.


Added ability for live classification

Still need to fine-tune the accuracy, but the pipeline is in place

Files look large because I duplicated the dataset to tinker with it etc. without disrupting the primary dataset

To run the code, pull everything and then run python3 live_demo.py to view the integrated code. live_demo.py loads the model and runs it against the filtered results of a live opencv window.


The main navigation bar is not navigable using a keyboard

Description
As an attendee, I want the navigation to be logically traversable, so that I only need a keyboard for navigation.
Acceptance criteria
A user should be able to navigate through the entirety of the navigation bar with a keyboard alone.
Within the context of the navigation bar, this means that the tab order should go left to right, then top to bottom.
Additional information
WCAG 1.3.2 Meaningful Sequence

I phrased this ticket in a keyboard-centric way since it's what I tested it with, but the tab order is also used by adaptive switches.
This is the current tab order:

Skip to main link
Homepage
Code of conduct
Tickets

The next three links are Volunteers, Tickets and Sponsors as part of the actual page content "under the fold". It looks as though the entire navigation menu is completely avoided.

Done in #703, I'll leave this open in case there's something wrong 😊


Broken build due to contracts added via PR #251

PR #251 Adds some contracts which are not part of our Silverlight reference assemblies.
According to documentation they are correct, but the CRASanitizer fails because they are not part of the Silverlight 5.0 reference assemblies.

Good catch, thank you for fixing it.

@SergeyTeplyakov @sharwell I think I remember that Sam has setup AppVeyor for continuous integration. Does this run? I thought it would catch broken builds.

@tom-englert I thought it should. I'll merge the PR right now.

Merged.

@tom-englert The AppVeyor build runs against my fork of the project, not against the reference repository. I don't think we'll be able to enable the automated build on the main repository until it moves to the dotnet organization.

I see, so hopefully that will happen soon :smile:

Can this issue be closed?

Yes - just checked out master, got no build errors.


If path is not the current directory then correct it.

When debugging it's helpful to launch bedrock from different folder paths. Specifically when using Cloud9 IDE. Bedrock will fail to reference the correct paths if it is launched elsewhere. This fixes the issue.

Which paths does Bedrock fail to reference? Looking through Bedrock's code (which is basically just application.php), all references that I see use absolute paths. Am I missing something?

Which paths does Bedrock fail to reference?
@QWp6t anything under the /wp/<path. For example /wp/themes.php.

Additional info.
http://stackoverflow.com/questions/5254000/php-how-to-set-current-working-directory-to-be-same-as-directory-executing-the

@jumbojett I realize this solves a problem you're having but it seems a little specific to your development environment in Cloud9 and I don't want to add this by default for everyone when I'm not sure what other side-effects it could have.


Bind client to specific cluster name

This PR makes client check the node's ClusterName before using it to sniff nodes and/or marking it as healthy.
Currently it's possible that one node might go down and get up as a node from different cluster, respond to the sniffer faster than everyone else and effectively take over the client, making it query different cluster. Same can happen on startup if one of seed nodes had been moved to the different cluster.

I'll need your help writing tests for this - I haven't found any mention of cluster name used in Jenkins setup.

Does the SniffingCallback already solve this problem?

Oh, didn't notice it. Neat!
It won't solve the problem completely though, since previously healthy node can became node from foreign cluster, bypassing the new-node process in sniffer; plus, node roster would be ruined if we'll sniff a node from foreign cluster - yielding only foreign cluster's nodes.

since previously healthy node can became node from foreign cluster

You mean existing nodes switch clusters? That'd indeed be very bad.

node roster would be ruined if we'll sniff a node from foreign cluster

If SnifferCallback returns true, it shouldn't become a node in Elastic and shouldn't receive any requests. How SnifferCallback determines that is up to the callback.
I still struggle to see why nodes should/would switch clusters? I mean, it could happen, but only if I've not done my homework on the infrastructure level (i.e. separate nodes of clusters). Can you give an example of why that would be beneficial?

Well, we've hit this on prod when switching to new major version of Elastic. Since it had to be zero-downtime op we were using same physical nodes (nA) to build up a new cluster (cB) that is identical to current setup (cA) power-wise, gradually switch load to the new cluster cB while moving old machines from cA to new cluster as load moves to cB and then removing stand-in nodes nA to do the same later with remaining clusters running old version of Elastic.
While nodes nA were down for ~2min before forming new cluster after transition was completed - client still picked them up somehow and sniffed nodes of completely foreign cluster.
Besides, it's possible that someone somewhere would want to juggle nodes between clusters if there's high load expected for one of them.
This PR doesn't make the cluster binding mandatory, but it would create an additional safeguard for those who want it.

Hmm... a node can only join a cluster if it shares its cluster name (docs). So I'm still a bit surprise how you could end up with a node joining two different clusters other than the clusters shared the same name.
Anyway, I guess the requirement of isolating the nodes suitable for sniffing could be satisfied by something like this:
package main

import (
	"context"
	"log"

	elastic "gopkg.in/olivere/elastic.v5"
)

func main() {
	client, err := elastic.NewClient(
		elastic.SetSnifferCallback(EnforceVersion("5.5.2")),
	)
	if err != nil {
		log.Fatalf("Connect failed: %v", err)
	}
	log.Print("Connected")

	_, err = client.IndexExists("twitter").Do(context.Background())
	if err != nil {
		log.Fatalf("IndexExists failed: %v", err)
	}
	log.Print("Done")
}

func EnforceVersion(version string) elastic.SnifferCallback {
	return func(node *elastic.NodesInfoNode) bool {
		// log.Printf("%#v", node)
		return node.Version == version
	}
}

Notice that the cluster name is not available in elastic.NodesInfoNode. As a workaround, you could annotate the nodes accordingly and use the Attributes property to figure out what to do.

Hi! Sorry for the long response.
This solution wouldn't help - bad IndexExists response would require us to recreate client on failure w/ downtime, since roster is already poisoned and there's no way back.
EnforceVersion would wipe all nodes from the roster if foreign node is being sniffed.
I'm not exactly sure of exact sequence of events, but I suspect that node left the cluster and joined another cluster between the sniffing rounds, and then sniffer sniffed foreign nodes from it.
The node didn't join two different clusters, it just left one cluster and joined another one fast.

@utrack I still don't see how a node might decide to leave cluster A and then join a totally different cluster B--with a different cluster name and, as you state, a different major version.
If you want to enforce Elastic to only use specific nodes/node configurations you might turn off sniffing altogether and e.g. label the nodes with annotations like specified in the Wiki.
If that isn't feasible and your original solution solves the problem you should probably use your version until you completed the migration to the new cluster. Quite frankly I don't see a way to integrate it into the client because I think it solves a problem that shouldn't exist in the first place.

It did not "decide" to move, it was reprovisioned fast enough that client wasn't able to catch up with the changes.
Official Java client explicitly requires cluster name binding as well, see https://www.elastic.co/guide/en/elasticsearch/client/java-api/5.5/transport-client.html

@utrack You are refering to the TransportClient. The TransportClient works by being part of the cluster, is native Java, uses a binary protocol to talk to cluster nodes (not the REST API), and requires the cluster name for connecting to the cluster. AFAIK it's being retired and should be replaced by the official REST client for Java.
Elastic is a HTTP client, built in a similar fashion as the official clients for Ruby, Python, and now Java.
I'm trying to keep Elastic in line with the official clients. Until now, I haven't seen any configuration setting or code snippet that enforces cluster name affinity (see e.g. client.go or sniffer.rb). Can you point me to a code snippet or thread that discusses cluster name affinity?


Flamingo tenant structure not mapping to Flux tenant structure

Hi,
Hopefully a quick question if someone knows.
In the Flamingo source at:
https://github.com/flux-subsystem-argo/flamingo/blob/ef02f00f17000b5a95bee67abcd6387819e942be/cmd/flamingo/install_templates.go#L110
it suggests that the label to identify a tenant is limited to the namespace name:
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    toolkit.fluxcd.io/tenant: %s
  name: flamingo-reconciler
  namespace: %s
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: argocd-application-controller
  namespace: %s

However, Flux multi-tenancy doesn't limit a tenant to a single namespace:
https://fluxcd.io/flux/cmd/flux_create_tenant/
e.g. as per the doc, you can define --with-namespace multiple times which makes sense to me where a team may be allocated more than one namespace in a k8s (shared) cluster:
 # Generate tenant namespaces and role bindings in YAML format
 flux create tenant dev-team \
   --with-namespace=frontend \
   --with-namespace=backend \
   --export > dev-team.yaml

Is this difference between Flamingo tenancy and Flux intended? i..e would I have to work with a tenant = namespace if I wanted to use the Flux subsystem?

Hi @tommyreilly
Thank you for bringing this up.
Our aim is to make Flamingo 100% compatible with Flux tenants.
So yes, we would definitely support the model you suggested.

Thank you @chanwit


5442 - implement method HEAD in ApiListener

@Yale96, can you check (or perhaps add a check) that no real content data is received if the HEAD method is used? Maybe we need to add something to prevent that (or that it is used to by pass security etc).

@Yale96, can you check (or perhaps add a check) that no real content data is received if the HEAD method is used? Maybe we need to add something to prevent that (or that it is used to by pass security etc).

Indeed please add a test for this. I see nothing in code now to prevent data from being returned.


Email Delivery Failure

I have tried all of the various SMTP options for mail delivery, however, the server fails to properly send mail regardless of the method I use. It recognizes the method it is attempting to send with, but always fails with an error stating that there is no appropriate protocol.
org.simplejavamail.mailer.internal.MailerException: Third party error
	at org.simplejavamail.mailer.internal.SendMailClosure.executeClosure(SendMailClosure.java:91)
	at org.simplejavamail.mailer.internal.AbstractProxyServerSyncingClosure.run(AbstractProxyServerSyncingClosure.java:56)
	at org.simplejavamail.internal.util.concurrent.AsyncOperationHelper$1.run(AsyncOperationHelper.java:75)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: javax.mail.MessagingException: Could not convert socket to TLS
	at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1907)
	at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:666)
	at javax.mail.Service.connect(Service.java:317)
	at javax.mail.Service.connect(Service.java:176)
	at javax.mail.Service.connect(Service.java:125)
	at org.simplejavamail.mailer.internal.util.TransportRunner.runOnSessionTransport(TransportRunner.java:75)
	at org.simplejavamail.mailer.internal.util.TransportRunner.sendMessage(TransportRunner.java:48)
	at org.simplejavamail.mailer.internal.SendMailClosure.executeClosure(SendMailClosure.java:82)
	... 7 common frames omitted
Caused by: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
	at java.base/sun.security.ssl.HandshakeContext.<init>(HandshakeContext.java:170)
	at java.base/sun.security.ssl.ClientHandshakeContext.<init>(ClientHandshakeContext.java:98)
	at java.base/sun.security.ssl.TransportContext.kickstart(TransportContext.java:221)
	at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:443)
	at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
	at com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:549)
	at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:486)
	at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1902)
	... 14 common frames omitted
05:17:06.349 [pool-24-thread-1] WARN  c.s.c.c.p.provider.EmailServiceImpl - Email cannot be delivered

It, however, properly reflects the options as I change them in the config.
DEBUG o.s.m.internal.util.SessionLogger - starting async mail with session (host: smtp.<REDACTED>.com, port: 587, username: <REDACTED>, authenticate: true, transport: SMTP)

DEBUG o.s.m.internal.util.SessionLogger - starting async mail with session (host: smtp.<REDACTED>.com, port: 587, username: <REDACTED>, authenticate: true, transport: SMTPS)

DEBUG o.s.m.internal.util.SessionLogger - starting async mail with session (host: smtp.<REDACTED>.com, port: 587, username: <REDACTED>, authenticate: true, transport: SMTP_TLS)

Which TLS/SSL protocols does your SMTP allow? You can use nmap for this:
nmap --script ssl-enum-ciphers -p 443 smtp.<YOUR_SERVER>.com

Java11 only supports TLSv1.2+ so most likely your SMTP server only uses an older version.

Which TLS/SSL protocols does your SMTP allow? You can use nmap for this:
nmap --script ssl-enum-ciphers -p 443 smtp.<YOUR_SERVER>.com

Java11 only supports TLSv1.2+ so most likely your SMTP server only uses an older version.

Seems it supports TLSv1.2:
PORT    STATE SERVICE
587/tcp open  submission
| ssl-enum-ciphers:
|   TLSv1.0:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_DHE_RSA_WITH_AES_256_CBC_SHA (dh 2048) - A
|       TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|   TLSv1.1:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_DHE_RSA_WITH_AES_256_CBC_SHA (dh 2048) - A
|       TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|       TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (dh 2048) - A
|       TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (dh 2048) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_DHE_RSA_WITH_AES_256_CBC_SHA (dh 2048) - A
|       TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 2048) - A
|       TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server

Hmm, the docker container has this under $JAVA_HOME/conf/security/java.security:
jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, \
    DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
    include jdk.disabled.namedCurves

So it seems to be fine unless I'm misreading it.
Can you modify your docker-compose.yml file to include the following JAVA_OPTS:
  clearflask-server:
    ...
    environment:
      - ...
      - JAVA_OPTS="-Djavax.net.debug=ssl"

Then restart and look at the extra logs. You should see logs similar to the following:
Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
...

Please post the output including anything interesting around it.
The alternate option you have is to modify the docker container to comment out the jdk.tls.disabledAlgorithms in $JAVA_HOME/conf/security/java.security line and try it out. If it works, just keep using that modified container.

This is what I've got so far from it:
05-May-2022 06:01:38.106 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djavax.net.debug=ssl
javax.net.ssl|DEBUG|12|localhost-startStop-1|2022-05-05 06:01:50.599 UTC|SSLCipher.java:438|jdk.tls.keyLimits:  entry = AES/GCM/NoPadding KeyUpdate 2^37. AES/GCM/NOPADDING:KEYUPDATE =<PHONE_NUMBER>72

Oh you should try to send an email with this extra logging and see what gets printed

So a few things. There should be an option to let us specify the sending domain. The issue may have something to do with the fact that it's trying to send from @help.zandercraft.ca and not @zandercraft.ca. There should also be an option to change the email sending name to allow for more clearly specifying where the email is coming from. Most people won't understand what ClearFlask is who use the site, so it would be helpful to be able to set it to something like "Help Centre".  Would also be helpful if
More related to the issue itself, here's a full log of it sending an email: https://pastebin.com/gyWbp1PP

Try the different options for smtpStrategy config, options are SMTP, SMTP_TLS, SMTPS. This may be misconfigured.
com.smotana.clearflask.core.push.provider.EmailServiceImpl$Config.smtpStrategy=<SMTP, SMTP_TLS, SMTPS>

I am adding a config property for overriding the domain name, in a few hours check for version 1.5.9. Also you will be able to modify the local part as well (ie noreply@...).
com.smotana.clearflask.core.push.provider.EmailServiceImpl$Config.fromEmailLocalPart=noreply
com.smotana.clearflask.core.push.provider.EmailServiceImpl$Config.fromEmailDomainOverride=zandercraft.ca

There already is a config for overriding email sending name:
com.smotana.clearflask.core.push.provider.EmailServiceImpl$Config.emailDisplayName=ZanderCraft

All available configs for 1.5.8 are listed here:
https://github.com/clearflask/clearflask/blob/1.5.8/clearflask-server/src/main/java/com/smotana/clearflask/core/push/provider/EmailServiceImpl.java

Assuming this is resolved

Apologies. I've been busy for the past few days. The issue still persists.

No problem, whenever you have time you can post an update to my suggestions and re-open this issue and I'll help you out.


[FEAT]: Image generation

What would you like to see?
In addition to text generation, is it possible to allow anythingLLM to generate images?
Via the image generation API of OpenAI, or Gemini, etc.?
PS: i mean text to image and not image to text

I'm also interested in this, specifically around the way images can be "retrieved" from existing documentation rather than generated from scratch using something like DALL-E. Embedding images is currently possible with some LLMs but some things can only be communicated through the original image. So, retrieving that image in its original form would help a lot.

Hi, regarding the function that supports text generation for images, do you have an estimate of when or which version it will be supported for?
Thx


removed ratelimiter, synchronized hdfs stuff

I clearly do not know how to use github

What requires xml-apis? There is a version 2.0.2 which has an older timestamp than the version 1.4.01. Please confirm which is the latest version (all versions are really old, which makes me doubly doubt the need for it)

yuesong - xml-apis is required for the hdfs output writer, otherwise we get an org/w3c/.../ NoClassDefFoundError in prod when trying to instantiate the hdfs output sink. Version 1.4.01 is what Irene used as her solution. Our internal repo has a dependency on 1.3.x xml-apis and I'm not sure 2.0.2 is binary compatible since it's a different major version (and it's six years older).


Side Panel Navigation Parameters of Static Content Page Component not used by PWA

Is your feature request related to a problem? If yes, please describe it.
The configuration parameters for the side panel navigation of 'Static Content Page Component' are not being used by PWA component 'CMSStaticPageComponent'

Describe the desired solution.
CMSStaticPageComponent is rendering navigation menu as configured via CMS component 'Static Content Page Component'

Initially the CMS REST API did not provide the information to construct the page hierarchy for the static content pages navigation. But with the now available /cms/pagetree/{pagesKey} REST resource (https://support.intershop.com/kb/index.php/Display/2956B7#193cfc9be3b995831c6af2fea6650e60) it would be possible to implement this navigation. With this the configuration parameters for the Static Content Page Component would become meaningful again.


No spans field on Rich Text fields

Hi @antonbehaeghe, sorry for the late reply. Could you describe the issue?

I believe i have the same issue:
When spans gives back an empty array, it's not possible to query it

data

type: "StructuredText" --value: [ --{ type: "paragraph" text: "some text" spans: [ ] } ] }

you can do

team_content {               type               text             }

you can't do:

team_content {               type               text               spans {                 start                 end                 type               }             }
But this should be possible

I finally understand what this issue is. In the Prismic API V2 response, a RichText field contains data like the following:
{
  // ...
  data: {
    myRichTextField: [
    ]
  }
  // ...
}

I've opened an issue for prismic-richtext regarding this: https://github.com/prismicio/prismic-richtext/issues/10

Hi @angeloashmore, So it's more like an issue on Gatsby I guess. It doesn't feel right to just remove data from the API Response. I don't think that should be fix in the prismic library.

Closing in favor or #24 (providing HTML and text fields as part of the plugin).


Feature/packet

Codecov Report

Merging #18 (97d43cc) into main (bfbde4b) will increase coverage by 0.06%.
The diff coverage is 95.78%.

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
+ Coverage   95.58%   95.64%   +0.06%
==========================================
  Files          19       22       +3
  Lines         996     1079      +83
==========================================
+ Hits          952     1032      +80
- Misses         32       34       +2
- Partials       12       13       +1

Impacted Files
Coverage Δ

cores/entitys/module.go
100.00% <ø> (ø)

cores/nets/tcpconnect.go
100.00% <ø> (ø)

cores/nets/tcplisten.go
82.35% <ø> (ø)

cores/nets/netmgr.go
91.48% <66.66%> (ø)

cores/nets/tcpsession.go
77.14% <83.33%> (ø)

cores/msgs/stringmsg.go
93.75% <93.75%> (ø)

cores/entitys/entity.go
100.00% <100.00%> (ø)

cores/entitys/entitymgr.go
100.00% <100.00%> (ø)

cores/logs/empty.go
100.00% <100.00%> (ø)

cores/msgs/msgmgr.go
100.00% <100.00%> (ø)

... and 4 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Footer on all pages

Instead of adding NewFooter component on each page, add it to the root.
Check App.jsx or Layout

Hey can i work on it

Hey @Night3y3, Thanks for wanting to contribute. To begin, try setting it up on your computer. If you run into any issues or have questions, feel free to join us on Discord. We're here to assist!

Hey @pranshugupta54 pls check it.. if it is alright.

Hey I'd love to work on this

@ayann07 @mhgarry, this is still open. We're having some more changes in the main branch soon, so make sure to join us on discord.

@ayann07 just put up a pull request


Fix anr issue

This issue is a workaround that fixes ANR by moving blocking operations to a background threads.

Moves sendMessageToFlutterApplication to a background thread

In respect of @ikbalkaya opening comment:

Checks for intent.getExtras() not being null. I know this is not directly related to this task but I felt that this is an important thing to quickly fix as this is essentially a very small PR

I'm concerned about the nature of this change, or more specifically what conclusion or assumption led to it being added to this PR.
First, given that intent is what's passed to sendMessageToFlutterApplication, then I would have expected it would be the responsibility of that method's implementation to check intent.getExtras() isn't null. Checking it in this method feels inappropriate, in that it assumes the implementation of the method being called needs the extras.
But, secondly, this additional check doesn't appear to solve anything described in the opening issue. I think this pull request should have a narrow scope, focussed on fixing only the problem described. I've not seen anything (e.g. in #290) that describes null being encountered here being a cause of issues. 🤔

When comparing this with the official Firebase plugin, I realised they did that check before processing message. I tried sending an intent without any extras and that caused a crash. I just then struggled to prevent my urge to fix it 😄 but I agree, it's out of scope of this PR. So I removed it here https://github.com/ably/ably-flutter/pull/291/commits/6087a907e7ce84fb0254b4ba6a8f3956827ef0ce. I will open another issue to fix that


Adds validation that the service account specified in 'runAsUser' has …

…WRITE permission to application
@jtk54 @duftler @cfieber @ajordens PTAL.

LGTM, thanks @ttomsu!


Updated KerbalSpacePonies and Added BurgerMod!

Whew, after several busy days I can finally sit down and get this pushed!
Doesn't look like there are any problems with this push ^_^
Not sure if I wrote the BurgerMod's netkan file correctly, if there are any mistakes I'll quickly push it again XP
Thanks for being patient with me, with my last derp up ^^"

Looks good, merging with my thanks.


JarBuilder still runs the bnd Builder even though it is up to date

We have a large subproject of our build that applies the gradle-bundle-plugin.  We found that the plugin will run the aQute.bnd.osgi.Builder, and in the end mark the task as up to date.  Being a large subproject with a large amount of classes, this eats up over a minute of build time for an 'up-to-date' task.  I think the up to date check should prevent the Builder from being run, to save on build time.

A clipping of a debug log if it helps, with some things taken our for brevity.

09:28:30.229 [LIFECYCLE] [class org.gradle.TaskExecutionLogger] :someProject:jar
09:28:30.229 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Starting to execute task ':someProject:jar'
09:28:30.229 [DEBUG] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Determining if task ':someProject:jar' is up-to-date
09:28:30.245 [DEBUG] [org.gradle.api.internal.changedetection.state.CachingTreeVisitor] Cache hit directory 'C:\someProject\build\classes\main'
09:28:30.245 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting base C:\someProject
09:28:30.245 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting properties { ... stuff ... }
...
09:28:30.276 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting classpath ...classpath...
09:28:30.276 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting source path C:\someProject\src\main\java
09:28:30.955 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting resources C:\someProject\build\classes\main
09:28:30.956 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting version 1.0.0.SNAPSHOT
09:28:30.956 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting name someProject
09:28:30.956 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting trace false
09:28:30.956 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting fail on error false
09:28:31.369 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] The Builder is about to generate a jar using classpath: [... classpath ...]
09:28:31.369 [DEBUG] [aQute.bnd.osgi.Builder] build
... 106 seconds of Builder spam ...
09:30:17.145 [INFO] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Skipping task ':someProject:jar' as it is up-to-date (took 1 mins 46.916 secs).
09:30:17.145 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Finished executing task ':someProject:jar'
09:30:17.145 [LIFECYCLE] [class org.gradle.TaskExecutionLogger] :someProject:jar UP-TO-DATE

The Gradle 4.2-rc-2 log is slightly more interesting as it gives details for why it appears up to date:

13:29:14.898 [LIFECYCLE] [class org.gradle.internal.buildevents.TaskExecutionLogger] :someProject:jar
13:29:14.898 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Starting to execute task ':someProject:jar'
13:29:14.898 [INFO] [org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter] Putting task artifact state for task ':someProject:jar' into context took 0.0 secs.
13:29:14.901 [DEBUG] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Determining if task ':someProject:jar' is up-to-date
13:29:14.901 [DEBUG] [org.gradle.api.internal.changedetection.state.CacheBackedTaskHistoryRepository] Implementation for task ':someProject:jar': org.gradle.api.tasks.bundling.Jar_Decorated@ce97d6e0384e5ecf293e6ab33b4580e6
13:29:14.901 [DEBUG] [org.gradle.api.internal.changedetection.state.CacheBackedTaskHistoryRepository] Action implementations for task ':someProject:jar': [org.dm.gradle.plugins.bundle.BundleGenerator@1ad1926e8ebbe6bd82e5b20b8a1568cb]
13:29:14.902 [DEBUG] [org.gradle.api.internal.changedetection.state.CacheBackedTaskHistoryRepository] Snapshotting property rootSpec$1 (RELATIVE) for task ':someProject:jar'
13:29:14.903 [DEBUG] [org.gradle.execution.taskgraph.DefaultTaskPlanExecutor] Task worker [Thread[Task worker for ':' Thread 3,5,main]] finished, busy: 0.0 secs, idle: 0.695 secs
13:29:14.905 [DEBUG] [org.gradle.execution.taskgraph.DefaultTaskPlanExecutor] Task worker [Thread[Task worker for ':',5,main]] finished, busy: 0.0 secs, idle: 0.7 secs
13:29:14.906 [DEBUG] [org.gradle.execution.taskgraph.DefaultTaskPlanExecutor] Task worker [Thread[Daemon worker,5,main]] finished, busy: 0.0 secs, idle: 0.7 secs
13:29:14.912 [DEBUG] [org.gradle.api.internal.changedetection.state.CacheBackedTaskHistoryRepository] Snapshotting property rootSpec$2 (RELATIVE) for task ':someProject:jar'
13:29:14.912 [DEBUG] [org.gradle.api.internal.changedetection.state.CacheBackedTaskHistoryRepository] Snapshotting property rootSpec$2$1 (RELATIVE) for task ':someProject:jar'
13:29:14.914 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] Setting base C:\someProject
... stuff ...
13:29:15.710 [DEBUG] [org.dm.gradle.plugins.bundle.JarBuilder] The Builder is about to generate a jar using classpath: [ ... classpath ... ]
13:29:15.710 [DEBUG] [aQute.bnd.osgi.Builder] build13:31:23.270 [DEBUG] [org.gradle.api.internal.changedetection.state.CacheBackedTaskHistoryRepository] Snapshotting property archivePath (OUTPUT) for task ':someProject:jar'
13:31:23.272 [DEBUG] [org.gradle.api.internal.changedetection.state.CacheBackedTaskHistoryRepository] No discovered inputs for task ':someProject:jar'
13:31:23.284 [INFO] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Skipping task ':someProject:jar' as it is up-to-date (took 2 mins 8.379 secs).

I think this might have to do with the manifest being generated.  From a clean state, it seems to run the JarBuilder.build method once while generating the manifest in the writeManifestTo method, and again while generating the jar in the writeJarTo method.
void writeManifestTo(OutputStream outputStream, @Nullable Closure c) {
    def builder = build()

    def manifest = builder.jar.manifest.clone() as Manifest
    if (c != null) {
        c manifest
    }
    try {
        Jar.writeManifest manifest, outputStream
    } finally {
        outputStream.close()
        closeBuilder(builder)
    }
}

void writeJarTo(File output) {
    def builder = null
    try {
        builder = build()

        output.getParentFile().mkdirs()
        builder.jar.write output
    } finally {
        closeBuilder(builder)
    }
}

So the issue on a repeated build I assume has to do with the manifest generation calling the build method.  Is that avoidable on an up-to-date build?

With further digging I realize that the builder is run to generate the manifest to determine if it is up to date.    Getting around this might be tricky.


Error message missing name of the failed taskrun

Expected Behavior
Get a error message that provides the name of the task to better troubleshooting purpose.
Actual Behavior
status:
completionTime: '2019-07-31T19:54:11Z'
conditions:
- lastTransitionTime: '2019-07-31T19:54:11Z'
message: >-
invalid output resources: TaskRun's declared resources didn't match
usage in Task: Didn't provide required values: [source]
reason: PipelineValidationFailed
status: 'False'
type: Succeeded
startTime: '2019-07-31T19:54:11Z'
Steps to Reproduce the Problem
Good point, If I knew what Task is failing I could give steps to reproduce.

Could you provide the contents of the pipeline/pipelinerun and task/taskrun YAMLs that trigger this?
Looks like one of the tasks is expecting a resource named source and it isn't being wired in.
Taking a wild guess, is the error manifesting from the tutorial pipeline?

Source for the pipeline and tasks are here: https://github.com/samueltauil/openshift-cd-demo/tree/ocp-4.1-tekton
I don't remember from top of my head a resource called source there but will double check.
I'm starting the pipeline with tkn pipeline start deploy-pipeline --resource tasks-git=tasks-git --resource tasks-image=tasks-image-internal -s pipeline
tkn version: 0.2.0

I found some references to the source reference in my yaml files but still relevant the issue as the errors doesn't show what Task is throwing the error.

Just add more to the thread, I more concerned about messages like this that doesn't bring the actual Task name that generated that error:
message: >-         invalid output resources: TaskRun's declared resources didn't match         usage in Task: Provided extra values: [tasks-git]message: >-

Yeah, agreed, it would be helpful to include the name of the Task and TaskRun that caused the mismatch in the error message.

Looked into this briefly. This isn't an easy fix because those error messages are produced via ValidateResolvedTaskResources(). That validation method is reused for TaskRuns and PipelineRuns, both of which drop the particular Task name, if it exists (remember they can be directly embedded).

Additional points:

You can find the TaskRun/PipelineRun name right? I'm assuming that error is attached to one of them. It's still not as easy as it could be, but with that name and the missing parameter's name it's doable to find the source of the error
We allow embedded taskSpec definitions, so in some situations it will be impossible to give the task's name that has a resource validation issue. With the change suggested here we will have 2 different errors, determined by whether the user has embedded tasks or not. I'd say this is a feature at this point rather than a bug

@EliZucker Yes I do can see a list of TaskRun and PipelineRun but when you have many tasks it is kind of hard to understand where that error came from and looking to the future I'm assuming pipelines are gonna grow either in complexity and size so having this would be a key feature for troubleshooting purposes.

ValidateResolvedTaskResources() has a parameter of type ResolvedTaskResouces which has a TaskName. Can we not add that to the error message here?
(We'd have to figure out something for embedded tasks but I don't think they are supported in pipelines/pipelineruns at the moment just in taskruns)

Duplicate issue: https://github.com/tektoncd/pipeline/issues/2894
Fixed in https://github.com/tektoncd/pipeline/pull/2899
/close


Set Agent Host on Query Deployment

Requirement - what kind of business use case are you trying to solve?
After deploying the Jaeger Agents as daemonset, the collector as deployment and the query as separate deployment, the query service prints such log lines:
{"level":"error","ts":1558691285.7870169,"caller":"zap/logger.go:33","msg":"error when flushing the buffer: write udp <IP_ADDRESS>:57618-><IP_ADDRESS>:6831: write: connection refused","stacktrace":"github.com/jaegertracing/jaeger/vendor/github.com/uber/jaeger-client-go/log/zap.(*Logger).Error\n\t/home/travis/gopath/src/github.com/jaegertracing/jaeger/vendor/github.com/uber/jaeger-client-go/log/zap/logger.go:33\ngithub.com/jaegertracing/jaeger/vendor/github.com/uber/jaeger-client-go.(*remoteReporter).processQueue.func1\n\t/home/travis/gopath/src/github.com/jaegertracing/jaeger/vendor/github.com/uber/jaeger-client-go/reporter.go:257\ngithub.com/jaegertracing/jaeger/vendor/github.com/uber/jaeger-client-go.(*remoteReporter).processQueue\n\t/home/travis/gopath/src/github.com/jaegertracing/jaeger/vendor/github.com/uber/jaeger-client-go/reporter.go:267"}

Problem - what in Jaeger blocks you from solving the requirement?
I understand that it tries to send it's own tracing spans to localhost and since I don't have an agent running there it cannot send the spans. Obviously I could deploy an agent as sidecar container but I'd prefer sending them to the agents I run on that Kubernetes node - that's why I created the agents as daemonset in the first place right?

Proposal - what do you suggest to solve the problem or improve the existing situation?
I expected that there is an environment variable / argument where I could set the host for the jaeger agent.

Any open questions to address

Duplicates #1044


Dls 7003

Initial PR change requests addressed.  Changes from main also merged in.  Ready for 2nd review.


No mention of ApplicationDiscriminator

The page does not mention ApplicationDiscriminator and how to set/configure that value. We were unable to get our tokens working across multiple instances unless we gave a consistent value to ApplicationDiscriminator.

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

ID: b63ab082-ad30-b00d-ecd1-ca88eee1659e
Version Independent ID: 69818122-e47a-3fed-ea37-8009f66e2a5c
Content: Configure ASP.NET Core Data Protection
Content Source: aspnetcore/security/data-protection/configuration/overview.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hello @Cybrosys ... When the app name is set, the discriminator is set ...
https://github.com/dotnet/aspnetcore/blob/main/src/DataProtection/DataProtection/src/DataProtectionBuilderExtensions.cs#L39-L52
... but unfortunately, the section on setting the name doesn't connect the idea to earlier remarks in the topic about the discriminator ... and the lines that speak to the discriminator don't specifically mention the API property (ApplicationDiscriminator) and don't cross-link the API doc for it.

https://learn.microsoft.com/aspnet/core/security/data-protection/configuration/overview#setapplicationname
https://learn.microsoft.com/dotnet/api/microsoft.aspnetcore.dataprotection.dataprotectionoptions.applicationdiscriminator

Rick, here's a cut-'n-paste for that API ...
<xref:Microsoft.AspNetCore.DataProtection.DataProtectionOptions.ApplicationDiscriminator?displayProperty=nameWithType>

Thank you @guardrex!
Just read through the SetApplicationName chapter and forwarded the information internally. What I found was interesting and also confusing, is that it says we should not have to use SetApplicationName as long as the APIs have the same content root path. For us, we have dentical VMs behind a load balancer (shared secrets etc), yet, the only thing that made it work was setting the ApplicationDiscriminator (SetApplicationName).
Either I am not understand the root path or we're somehow doing something that results in it being unique per VM instance.
@Rick-Anderson I feel I am not the right person to update the documentation considering I have barely begun scraping the surface on the topic. As @guardrex pointed out, the important part we missed was the SetApplicationName (which according to the doc we should not have to use...).

That's an absolute path tho, so I think it is unique per VM. I think if you read the value of ApplicationDiscriminator without setting it ... read the value on each VM after deployment ... you'll probably see different paths reported by each.
@Rick-Anderson ... I'll do an update on this one in the morning. I'm awaiting feedback on a few Blazor things and have a few minutes to knock it out. I'll ping u for review tomorrow.

A quick one-liner can go like ...
app.Logger.LogInformation($"ApplicationDiscriminator: {app.Services.GetRequiredService<IOptions<DataProtectionOptions>>().Value.ApplicationDiscriminator}");

... right after the app is built in Program.cs.


[NEW] Auth deep link

Add support for auth deeplink
[https://rocket.chat/docs/developer-guides/deeplink/]
Supports both rocketchat://auth and https://go.rocket.chat/auth urls

Looking great! 👍


Cant get TXT Record of some Domains

Hey,
in short term, im trying to use fastdig as an alternative for "dig". When im using "dig" everything works expected, but on fastdig the result is missing. 						IN	TXT

;; AUTHORITY SECTION:

;; Query time: 7 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Wed Mar 20 15:40:36 EDT 2024
;; MSG SIZE  rcvd: 24

Im using the master, maybe its a bug?
//edit:
i downgraded till v0.6.0. looks like a basic problem

should be fine in 0.9.5, please try https://go.dev/play/p/UDJOz1Neh92
let me look why is broken in fastdig cli

fixed by using DoH in v0.9.6
So the root cause maybe related with UDP and possible no need to fix?


Random Blood Sugar - Update to Fasting Question [4h]

Issue
The term "fasting" is not used in Rwanda so we need to rephrase the fasting question on the random blood sugar test to be more appropriate.
The team has decided to change this question to "Was this test performed before a meal"
This should be changed across all Random Blood Sugar tests in E-Heza.
To Do

Update the question across e-eheza

https://nutrition-ihangane.pantheonsite.io/
QA Review
Checked and approved:

The question is updated as requested.


Eng nov patch notes

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit d9c7c3216f26bf80737887ee0efe03cd232bd32f
https://deploy-preview-9867--docsdocker.netlify.com


changed order of  prob and logit at line 84 and 87 to fixed the typo

I think it should be a typo. I fixed it. Please merge this commit to fix it.

Fix #42


Implement Tensor Product model

Todo:

[ ] Rename unbind because it is already a PyTorch method.
[ ] Can we still use bind(x, y.inverse()) to perform unbinding, if not, how do we deal with this breaking change?
[ ] Implement multibind.
[ ] Update examples and documentation.
[ ] How to perform permute?

Since this feature would break some of the standards in the library and the demand for this feature is not clear, we will opt to not include it in the library for now. If demand arises we will reconsider adding it.


Add example

I have finished writing some of the examples, and you can see the specific code in the example directory

1.You can change the connection configuration of gorm here

2.The example uses the Mysql database by default, which uses the users table, and you need to execute the sql statement in the zz_script script


Update build-constraints.yaml

Please update tasty-tap to allow the newest tasty and we should be good to go.

@bergmark 0.0.3 should do the trick.


[FEATURE] Create an enum for Resources

Is your feature request related to a problem?
To support the deprovisioning workflow we need a consistent set of Strings associated with resource types (e.g. connector_id).
Currently many of these are constant strings in the common package which is a good first step.  Some of them are hardcoded in the workflow steps which is not a good practice.
What solution would you like?
Create an enum associated with Resources created where the enum name can be used (lowercased) for the JSON string key.

Adding to this issue that we should have more consistent step names as well. for example for  /_plugins/_ml/model_groups/_register we just have model_group  but for /_plugins/_ml/models/_register we have register_remote_model and etc.
registerRemoteModel and registerLocalModel are a little more unique and there are also edge cases like like create_index where that name isn't anywhere in api path since its just PUT <index_name>

Fixed in #231


[AIRFLOW-2538] Update faq doc on how to reduce airflow scheduler latency

Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2538
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Update the faq doc on how to reduce airflow scheduler latency. This comes from our internal production setting which also aligns with Maxime's email(https://lists.apache.org/thread.html/<CAHEEp7WFAivyMJZ0N+0Zd1T3nvfyCJRudL3XSRLM4utSigR3dQ@mail.gmail.com>).

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[ ] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

PTAL @mistercrunch

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3434   +/-   ##
=======================================
  Coverage   76.71%   76.71%
=======================================
  Files         203      203
  Lines       15056    15056
=======================================
  Hits        11550    11550
  Misses       3506     3506

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 7c34354...8ae97fd. Read the comment docs.

PTAL @Fokko


Response UI

When admin/officer wants to give any response to a complaint, show the details of complaint. Like, separates the section (Kronologi [up] and Tanggapan [down]) and in the end of Tanggapan section, show all (or 3 latest) responses.
If the UI just like this, then it looks ruined I guess.

Closed as bb95795


ENH: Add get_range to BenchmarkSource

Add method to get a range of benchmark data

Coverage decreased (-0.4%) to 87.222% when pulling 655bf0f4cb28de9a4bf931ad8b8908b450419306 on get-array-benchmark-source into 0a481d4d6caf1bb185e68826cb8c4ac155c03069 on master.

Coverage decreased (-0.4%) to 87.222% when pulling 655bf0f4cb28de9a4bf931ad8b8908b450419306 on get-array-benchmark-source into 0a481d4d6caf1bb185e68826cb8c4ac155c03069 on master.


Provide step-by-step instructions for Carrenza VPN access

Having just been through this process and had to ask a lot of questions and figure things out, I thought I'd write up the steps which I took. This corrects several inaccuracies and ambiguities in the previous instructions.
It should now be possible to more or less copy and paste the commands step by step to complete the process of setting up VPN access, at least for Mac/AnyConnect users.

Only 2 minor comments, happy with approving once those are addressed 👍

Thanks for the reviews!


Alignment change to save memory in cluster info

Additional Description: Moving around a couple of variables to save a small amount of memory in Cluster Info.
Sizeof before changes: 2632
Sizeof after changes: 2624
Risk Level: Low

I've pushed a change like this in the same file just a few weeks ago. I don't see why it would cause issues.
https://github.com/envoyproxy/envoy/pull/25265


feat: add decimal type

I'm a bit sceptical about this type, as the result can be easily mapped from float type. I think they are similar in possible errors. and Decimal doesn't bring anything new.


Bloom Effect on transparent background

Hey there long time no see, glad to start playing with your library again, so far no real issues everything works great. Ran into something the other day I got stumped on...
Three 105, Postprocessing 6.5.0
How do I create a Bloom Effect on a scene drawn over a transparent canvas and background?
The closest I've gotten is with ALPHA blend mode which adds a blackish glow, similar in volume and shape as a bright glow you would expect to see with the scene rendered with a non transparent background.
this.bloomEffect = new POSTPROCESSING.BloomEffect({
  blendFunction: POSTPROCESSING.BlendFunction.ALPHA
})

A possibly related and current issue:
https://github.com/mrdoob/three.js/issues/14104

Hi, sorry for the late reply!
I tried some things, but couldn't find a way to remove the black halos. It seems that the bloom effect requires some form of alpha multiplication feature to produce the desired results. Unfortunately, I'm currently busy and can't look deeper into this.
Also thanks for pointing to the related issue. That might help when I get back to this.

Hey no worries life happens. I'm sure it's an easy fix when you get around to it 🙂

I finally found some time to look deeper into this. It turns out that the BloomEffect doesn't need any changes. It uses the right render target format, and the convolution shader already respects alpha values. The material blending also doesn't need to be changed.
The real issue lies with the luminance extraction pass. When I created that shader, I didn't pay much attention to the alpha channel. The same can be said about most of the effect blend functions. For example, the ADD blend function takes the new alpha and simply discards the input alpha value. These are the two main reasons for the blackish glow.
In summary, the LuminanceMaterial needs to reduce the alpha value of dark colors and blend functions need to blend alpha values.
Fixing the blend functions seems easy enough, but the luminance shader needs some more testing. These fixes will probably be included in the next release.

Luminance filtering and alpha blending have been improved in<EMAIL_ADDRESS>Here's an updated example of bloom over a transparent canvas: https://jsfiddle.net/of4b27nk/
If you find any other issues please let me know!

Oh wow you absolutely solved it. Thanks so much for this update!


Add webserver-py and webserver-py-old examples

webserver-py is a Python example that uses the new input/output classes. webserver-py-old uses dicts instead of the input/output classes, to ensure the old way of setting/getting nested data continues to work as expected.
Also, some minor cleanup while making changes to these test files: switched to using filepath.Join, rather than path.Join.

error: Error waiting to create Network: Error waiting for Creating Network: Quota 'SUBNETWORKS' exceeded.  Limit: 175.0 globally.