macOS 10.14 make: *** [transliterator.o] Error

sudo gem install charlock_holmes -- --with-icu-dir=/usr/local/opt/icu4c --with-cxxflags=-std=c++11
I've also tried adding the version parameters range from "0.7.3" to "0.7.6", none of them worked.
Error log:
Building native extensions with: '--with-icu-dir=/usr/local/opt/icu4c --with-cxxflags=-std=c++11'
This could take a while...
ERROR:  Error installing charlock_holmes:
	ERROR: Failed to build gem native extension.

    current directory: /Library/Ruby/Gems/2.3.0/gems/charlock_holmes-0.7.6/ext/charlock_holmes
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby -I /Library/Ruby/Site/2.3.0 -r ./siteconf20190530-29974-sl3ox1.rb extconf.rb --with-icu-dir\=/usr/local/opt/icu4c --with-cxxflags\=-std\=c\+\+11
checking for main() in -licui18n... yes
checking for main() in -licui18n... yes
checking for unicode/ucnv.h... yes
checking for main() in -lz... yes
checking for main() in -licuuc... yes
checking for main() in -licudata... yes
creating Makefile

current directory: /Library/Ruby/Gems/2.3.0/gems/charlock_holmes-0.7.6/ext/charlock_holmes
make "DESTDIR=" clean

current directory: /Library/Ruby/Gems/2.3.0/gems/charlock_holmes-0.7.6/ext/charlock_holmes
make "DESTDIR="
compiling converter.c
compiling encoding_detector.c
compiling ext.c
compiling transliterator.cpp
In file included from transliterator.cpp:1:
In file included from ./common.h:9:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/ruby.h:33:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/ruby/ruby.h:24:
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/universal-darwin18/ruby/config.h:365:31: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_ARCH "universal-"RUBY_PLATFORM_OS
                              ^

/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/universal-darwin18/ruby/config.h:366:35: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
                                  ^

/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/universal-darwin18/ruby/config.h:366:55: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
                                                      ^

In file included from transliterator.cpp:1:
In file included from ./common.h:9:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/ruby.h:33:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/ruby/ruby.h:1988:
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/ruby/intern.h:47:19: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
                  ^~~~~~~~~
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/ruby/intern.h:47:36: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
                                   ^~~~~~~~~
2 warnings and 3 errors generated.
make: *** [transliterator.o] Error 1

make failed, exit code 2

Gem files will remain installed in /Library/Ruby/Gems/2.3.0/gems/charlock_holmes-0.7.6 for inspection.
Results logged to /Library/Ruby/Gems/2.3.0/extensions/universal-darwin-18/2.3.0/charlock_holmes-0.7.6/gem_make.ou

same problem here.

I managed to fix this problem by editing
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/universal-darwin18/ruby/config.h

There are errors on line 365 and 366 - I added spaces between the literals and identifiers (like the error says).
I then ran the following, which worked correctly
sudo gem install charlock_holmes -- --with-icu-dir=/usr/local/opt/icu4c --with-cxxflags='-Wno-reserved-user-defined-literal -std=c++11'

I'm not sure if it's relevant, but this was with<EMAIL_ADDRESS>

I managed to fix this problem by editing
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/include/ruby-2.3.0/universal-darwin18/ruby/config.h

There are errors on line 365 and 366 - I added spaces between the literals and identifiers (like the error says).
I then ran the following, which worked correctly
sudo gem install charlock_holmes -- --with-icu-dir=/usr/local/opt/icu4c --with-cxxflags='-Wno-reserved-user-defined-literal -std=c++11'

I'm not sure if it's relevant, but this was with<EMAIL_ADDRESS>
The same issue applies to MacOS 10.13, which is the latest that some Macs can run.
For these, there's some extra complexity about turning off csr first, and the file is System/Library/[...] rather than /Library.
But it would be nice if Charlock Holmes could fix this "upstream."

I working on MacOS Big Sur, Ruby version is 2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin20]. When running the following:
gem install charlock_holmes -v '0.7.7' --source 'https://rubygems.org/',
and I got errors:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:415:31: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_ARCH "universal-"RUBY_PLATFORM_OS
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:416:35: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:416:55: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
^
In file included from transliterator.cpp:1:
In file included from ./common.h:9:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby.h:33:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:2111:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/intern.h:56:19: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
^~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/intern.h:56:36: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
^~~~~~~~~
2 warnings and 3 errors generated.
make: *** [transliterator.o] Error 1
make failed, exit code 2

I working on MacOS Big Sur, Ruby version is 2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin20]. When running the following:
gem install charlock_holmes -v '0.7.7' --source 'https://rubygems.org/',
and I got errors:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:415:31: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_ARCH "universal-"RUBY_PLATFORM_OS
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:416:35: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:416:55: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
^
In file included from transliterator.cpp:1:
In file included from ./common.h:9:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby.h:33:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:2111:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/intern.h:56:19: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
^~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/intern.h:56:36: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
^~~~~~~~~
2 warnings and 3 errors generated.
make: *** [transliterator.o] Error 1
make failed, exit code 2

Did you ever get this figured out?

Had the same problem. Solved by adding space in file /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h on lines 415 and 416
Before:
#define RUBY_ARCH "universal-"RUBY_PLATFORM_OS
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS

After:
#define RUBY_ARCH "universal-" RUBY_PLATFORM_OS
#define RUBY_PLATFORM "universal." RUBY_PLATFORM_CPU "-" RUBY_PLATFORM_OS

I working on MacOS Big Sur, Ruby version is 2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin20]. When running the following:
gem install charlock_holmes -v '0.7.7' --source 'https://rubygems.org/',
and I got errors:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:415:31: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_ARCH "universal-"RUBY_PLATFORM_OS
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:416:35: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:416:55: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
^
In file included from transliterator.cpp:1:
In file included from ./common.h:9:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby.h:33:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:2111:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/intern.h:56:19: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
^~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/intern.h:56:36: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
^~~~~~~~~
2 warnings and 3 errors generated.
make: *** [transliterator.o] Error 1
make failed, exit code 2

Did you ever get this figured out?

Had the same problem. Solved by adding space in file /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h on lines 415 and 416
Before:
#define RUBY_ARCH "universal-"RUBY_PLATFORM_OS
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS

After:
#define RUBY_ARCH "universal-" RUBY_PLATFORM_OS
#define RUBY_PLATFORM "universal." RUBY_PLATFORM_CPU "-" RUBY_PLATFORM_OS

I working on MacOS Big Sur, Ruby version is 2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin20]. When running the following:
gem install charlock_holmes -v '0.7.7' --source 'https://rubygems.org/',
and I got errors:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:415:31: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_ARCH "universal-"RUBY_PLATFORM_OS
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:416:35: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h:416:55: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS
^
In file included from transliterator.cpp:1:
In file included from ./common.h:9:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby.h:33:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:2111:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/intern.h:56:19: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
^~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/intern.h:56:36: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
^~~~~~~~~
2 warnings and 3 errors generated.
make: *** [transliterator.o] Error 1
make failed, exit code 2

Did you ever get this figured out?

Had the same problem. Solved by adding space in file /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h on lines 415 and 416
Before:
#define RUBY_ARCH "universal-"RUBY_PLATFORM_OS
#define RUBY_PLATFORM "universal."RUBY_PLATFORM_CPU"-"RUBY_PLATFORM_OS

After:
#define RUBY_ARCH "universal-" RUBY_PLATFORM_OS
#define RUBY_PLATFORM "universal." RUBY_PLATFORM_CPU "-" RUBY_PLATFORM_OS

Thanks, it worked awesome.
I was having XCode, so just the path of config file got changed
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin20/ruby/config.h


Remove JSONTimeString

The Slack API docs explicitly states that their funny timestamps are to be treated as a sort of message IDs and are guaranteed to be unique in the channel. In update and delete calls it is necessary to know the timestamp-string or the call will fail. Client code will use these timestamp-strings for things like checking for duplicate messages.
Instead of casting incoming timestamp-strings to (english speaking) human-readable strings like "Sun Jan 31" I think it's wise to let the client do its own formatting and leave the timestamp-strings be.
Slack docs:
All messages within a single channel are guaranteed to have a unique timestamp which is
ASCII sortable. Given the precision of the timestamp, clients should treat these timestamps
as strings, not floats/doubles.

Let me take a closer look at this soon™

+1

Gentle poke: any news on this? :)

Haven't forgotten about this, just been pretty busy. Apologies!

Thank you!


Provide logits or logprobs in the API

Feature request:
How can i get logits (probabilites of each next token), during generation, just like I can do it in Open AI API (logprobs)? This feature will be helpfull for apps, that use logprobs to measure model avareness and confidence.

Hello! Seems like a really good feature for more complex usage of Ollama.
Is this feature already WIP, or contribution would be fine?

I would also like to have this, I'm interested in having both echo + logprobs, so I can get information about the prompt too, instead of just the completion. Right now I'm using very small models with pytorch to compute logits directly, but that's really slow.

Any updates?

Any updates?

https://github.com/ollama/ollama/pull/1640#issuecomment-2043381653

Any updates?

Are there any updates on this very important issue? To not implement logits is not a valid solution. Anyone (including me) who needs logits will move from Ollama to a different solution! Please be aware of that.

support, would be very nice

I'm surprised this is not one of the first things implemented 🤔

Hi there,
any progress on integrating this feature request?

Hi, is there a timeline available for integration?

Hi, is there a timeline available for integration?

We are going to get AGI before this, 100%!

[laugh]         Mridul Sharma reacted to your message:

From: Tom Soru @.>
Sent: Thursday, September 19, 2024 12:53:37 PM
To: ollama/ollama @.>
Cc: Mridul Sharma @.>; Comment @.>
Subject: Re: [ollama/ollama] Provide logits or logprobs in the API (Issue #2415)
Hi, is there a timeline available for integration?
We are going to get AGI before this, 100%!
—
Reply to this email directly, view it on GitHubhttps://github.com/ollama/ollama/issues/2415#issuecomment-2360907875, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6MENUUYCRVXZP6V33UKE4LZXLCNDAVCNFSM6AAAAABDANSBIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQHEYDOOBXGU.
You are receiving this because you commented.Message ID: @.***>

We are going to get GTA 6 before this.

man, I really need this for to implement an CoT-Decoding pipeline. I guess I'll go back to playing Sparking Zero.

I've given up hope and switched back to llama.cpp for production inference.
Using it with ramalama which can pull from the ollama model library.
Really disappointed that the maintainers here show such disregard for such
a huge community request.
Makes me want to make sure I don't use the project in any way. If an
obvious thing like this is being totally ignored by the maintainers, then
it shows they don't really care much about what the community is asking
for.
On Tue, Oct 15, 2024, 11:39 PM Lino Valdovinos @.***>
wrote:

man, I really need this for to implement an CoT-Decoding pipeline for the
open-webui. I guess I'll go back to playing Sparking Zero.
—
Reply to this email directly, view it on GitHub
https://github.com/ollama/ollama/issues/2415#issuecomment-2415716327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEZELGRV4XP267QL3XM4ODZ3XUZLAVCNFSM6AAAAABDANSBIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJVG4YTMMZSG4
.
You are receiving this because you commented.Message ID:
@.***>

@jmorganca @bmizerany Has the team given up on implementing this feature?

 What about this though? This seems like less than 1/10th the effort - why are you ignoring everyone asking for input here? Why don't you at least provide a timeline?

insane that this not given as an option? maybe better to switch to pure huggingface models

man, I really need this for to implement an CoT-Decoding pipeline for the open-webui. I guess I'll go back to playing Sparking Zero.

Cot decoding and entropy decoding are available in optillm - https://github.com/codelion/optillm

Ollama will stop being an option for us if crucial features like this are not beeing implemented...

For such a simple but important feature, the team demonstrates unexpected arrogance and ignorance. I think this is a red flag for us to give up using Ollama as LLM backend since they cannot go far.

I have implemented it in PyTorch if anyone is looking for it they can use the following colab - https://colab.research.google.com/drive/1zPv47_tog2_KOFJY-WJxwPYR6mgoxKlK?usp=sharing
Here is the discussion on optillm where it was brought up as well - https://github.com/codelion/optillm/discussions/82

Logprobs are now directly supported in our local inference server - https://github.com/codelion/optillm?tab=readme-ov-file#local-inference-server we use the OpenAI compatible API so you can get them using the same code.

This would be very useful for enforcing the structure of output (output_cls with langchain, that currently works with llama.cpp and hugging face).
It can reject tokens that would break the output structure. Very useful for tool calling as well.

Logprobs are now directly supported in our local inference server - https://github.com/codelion/optillm?tab=readme-ov-file#local-inference-server we use the OpenAI compatible API so you can get them using the same code.

Great to hear that we have a cool alternative to ollama as those guys are not doing what needs to be done!

I would suggest you being more kind. Ollama is an open source project, they are not working for you. Feel free to offer a bounty to implement this, or create a pull request.
I would really like to see this implemented, but that does not mean I have to be mean to authors of a software I get for free.

Hey everyone! Sorry for the delay and no updates here - going to be picking this up soon and hopefully getting it in early Jan. There's been a ton of changes on the API even more so coming on the inference engine layer so just need to be a bit careful as it would be an API addition but it is something we want to support!

Hey folks would like to get your thoughts:
Would you care if it was logits vs logprobs? Would you prefer one over the other? If so why?
Working on designing the API and getting the functionality right along with that :) Appreciate your patience!

Personally would prefer log probs, just because all my tooling is setup for
that and used to thinking in logorobs haha
On Thu, Dec 12, 2024, 7:00 PM Parth Sareen @.***> wrote:

Hey folks would like to get your thoughts:
Would you care if it was logits vs logprobs? Would you prefer one over the
other? If so why?
Working on designing the API and getting the functionality right along
with that :) Appreciate your patience!
—
Reply to this email directly, view it on GitHub
https://github.com/ollama/ollama/issues/2415#issuecomment-2540310646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEZELA4VG6OFOCJ6QPM7TT2FIWTJAVCNFSM6AAAAABDANSBIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQGMYTANRUGY
.
You are receiving this because you commented.Message ID:
@.***>

But if you want to calculate the probability of the LLM generating "yes" or "no" for example you would either have to use constrained generation with logprobs, where only those 2 tokens will be non 0. Or you can directly use logits and do the constraining yourself.

Would you care if it was logits vs logprobs? Would you prefer one over the other? If so why?

Definitely logprobs so that it doesn't deviate from the OpenAI standards (see examples here) and the following can be supported:
for token in response.choices[0].logprobs.content:
    for top_logprob in token.top_logprobs:
        print((top_logprob.token, np.exp(top_logprob.logprob)))

Thanks @josiahbryan, @martinkozle, @mommi84. I also think it makes more sense to have logprobs for now and then happy to re-evaluate when doing the new engine. Have some fun plans for sampling :)

Hey folks would like to get your thoughts:
Would you care if it was logits vs logprobs? Would you prefer one over the other? If so why?
Working on designing the API and getting the functionality right along with that :) Appreciate your patience!

Personally I prefer logits because we can obtain ourselves a kind of logprobs if we have logits. Plus when trying tasks such as distillation or uncertainty observation, logits are more interesting to have. So please add logits 🙏, we can do the logprobs calculations by ourselves

To be more precise : Logprobs can be derived directly from logits through a softmax followed by a logarithmic transformation. This kind of operation is neither the most difficult nor the most time consuming. It's easy to get logprobs from logits but not that easy to get logits from logprobs except if you add a scale constant to get an approximation of the logits value.

Sorry for writing 3 successive message. This one should probably be another feature request. I'll definitely open one. Is it possible to add dropout layer to the models (like Monte Carlo dropout for example) ? Plus access the neural network layer information of models.

I disagree with @Elimane0800 , to get logprobs from logits, one need to compute logsoftmax on logits of the complete vocabulary, which is an expensive operation and is already done in the model for the inference of the next token.
Moreover, it is often only necessary to get the N most probable tokens (with N of the order of a few dozen). In this case, logprobs (or probs) are relevant, logits are not.

I disagree with @Elimane0800 , to get logprobs from logits, one need to compute logsoftmax on logits of the complete vocabulary, which is an expensive operation and is already done in the model for the inference of the next token.
Moreover, it is often only necessary to get the N most probable tokens (with N of the order of a few dozen). In this case, logprobs (or probs) are relevant, logits are not.

For having already tried to calculate logprobs from logits with cpu i can say that it is definitely not the type of task that will run during 24h. So if the only matter is a question of time and cost of the operation I can tell that it is nor the most time consuming neither the most expensive operation.

There are two use cases:

we want to know the probabilities of the N most probable tokens
we want to know the probabilities or the logits of all the tokens in the vocabulary.

I think the first use case is the most requested today. To answer it effectively, the API has no choice but to give the logprobs (or probs) of the N most probable tokens. Indeed, if the API only provides the logits, then it must provide them for the entire vocabulary if we want to deduce the logprobs. With vocabulary sizes sometimes approaching 100k, this overloads the API's JSON response enormously.


Birthday format needs to be consistent

The birthday field in the profile is populated straight form what comes from Facebook.
In this case it's formatted mm/dd/yyyy.
I propose we re-format this to ISO standard format, e.g. YYYY-MM-DD
Can use the following code to achieve this transformation:
if (json.birthday) {
  const parts = json.birthday.split('/');
  profile.birthday = [parts[2], parts[0], parts[1]].join('-');
}

Agreed, YYYY-MM-DD is far less ambiguous than MM-DD-YYYY (which where I come from would be interpreted as DD-MM-YYYY).

Yes same here, great I'll go ahead and implement this, but as it could be a breaking change for some it'll likely need a major version bump. So might want to hold off until it's clear what's happening in terms of unification of the profiles?

Agreed. I'll hopefully get time next week to have a good think on things. I also need to lint all the repos before we go making too many changes.

@rwky do you still maintain this package?

Yep, not worked on unifying profiles lately, promise support has been a higher priority though if you want to add a PR I'll take a look :)

I suppose either way
Considering same form to understand


Object type 'User' is not managed by the Realm.

The app is crashing on startup and we are not able to reproduce the problem on the test environment. Very critical, happened more than 400 times.
Actual Results

The exception:
Object type 'User' is not managed by the Realm. If using a custom `objectClasses` / `objectTypes` array in your configuration, add `User` to the list of `objectClasses` / `objectTypes`.

Issued by Fabric:
Fatal Exception: RLMException
0  CoreFoundation                 0x18113ed8c __exceptionPreprocess
1  libobjc.A.dylib                0x1802f85ec objc_exception_throw
2  Realm                          0x10546a254 RLMSchemaInfo::operator[](NSString*) (RLMClassInfo.mm:94)
3  Realm                          0x1054839e0 RLMGetObjects (RLMObjectStore.mm:215)
4  RealmSwift                     0x10594f880 Realm.objects<A where ...> (A.Type) -> Results<A> (Realm.swift:477)
5  My_App                         0x104a14fdc MyPresenterImpl.sync(onStart : Bool) -> () (MyPresenterImpl.swift:17)
6  My_App                         0x10495b78c MyViewController.viewDidAppear(Bool) -> () (MyViewController.swift:361)
7  My_App                         0x10495bb74 @objc MyViewController.viewDidAppear(Bool) -> () (MyViewController.swift)
8  UIKit                          0x18ad9a7b8 -[UIViewController _setViewAppearState:isAnimating:]
9  UIKit                          0x18adf0b8c -[UINavigationController viewDidAppear:]
10 UIKit                          0x18ad9a7b8 -[UIViewController _setViewAppearState:isAnimating:]
11 UIKit                          0x18afeb47c __64-[UIViewController viewDidMoveToWindow:shouldAppearOrDisappear:]_block_invoke
12 UIKit                          0x18adf0814 -[UIViewController _executeAfterAppearanceBlock]
13 UIKit                          0x18b0f69c4 _runAfterCACommitDeferredBlocks
14 UIKit                          0x18b0ec98c _cleanUpAfterCAFlushAndRunDeferredBlocks
15 UIKit                          0x18b0fd6c0 __34-[UIApplication _firstCommitBlock]_block_invoke_2
16 CoreFoundation                 0x1810e72bc __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__
17 CoreFoundation                 0x1810e6a7c __CFRunLoopDoBlocks
18 CoreFoundation                 0x1810e47b0 __CFRunLoopRun
19 CoreFoundation                 0x181004da8 CFRunLoopRunSpecific
20 GraphicsServices               0x182fe7020 GSEventRunModal
21 UIKit                          0x18afe578c UIApplicationMain
22 My_App                         0x104887a60 main (MigrationBlock.swift:16)
23 libdyld.dylib                  0x180a95fc0 start

Crashed: com.twitter.crashlytics.ios.exception
0  My_App                         0x104a48238 CLSProcessRecordAllThreads (CLSProcess.c:376)
1  My_App                         0x104a48238 CLSProcessRecordAllThreads (CLSProcess.c:376)
2  My_App                         0x104a486ac CLSProcessRecordAllThreads (CLSProcess.c:407)
3  My_App                         0x104a37cec CLSHandler (CLSHandler.m:26)
4  My_App                         0x104a467a4 __CLSExceptionRecord_block_invoke (CLSException.mm:199)
5  libdispatch.dylib              0x180a30ae4 _dispatch_client_callout + 16
6  libdispatch.dylib              0x180a39640 _dispatch_queue_barrier_sync_invoke_and_complete + 56
7  My_App                         0x104a46220 CLSExceptionRecord (CLSException.mm:206)
8  My_App                         0x104a46050 CLSExceptionRecordNSException (CLSException.mm:102)
9  My_App                         0x104a45c50 CLSTerminateHandler() (CLSException.mm:259)
10 libc++abi.dylib                0x1802e937c std::__terminate(void (*)()) + 16
11 libc++abi.dylib                0x1802e8f78 __cxa_rethrow + 144
12 libobjc.A.dylib                0x1802f87ac objc_exception_rethrow + 44
13 CoreFoundation                 0x181004e18 CFRunLoopRunSpecific + 664
14 GraphicsServices               0x182fe7020 GSEventRunModal + 100
15 UIKit                          0x18afe578c UIApplicationMain + 236
16 My_App                         0x104887a60 main (MigrationBlock.swift:16)
17 libdyld.dylib                  0x180a95fc0 start + 4

Steps to Reproduce

Probably crashing during migration, the migration is working ok but Realm hangs on this exception.
Code Sample

Do a query using Realm.objects<A where ...> (A.Type) -> Results<A>. The crash is very generic.
Version of Realm and Tooling

Realm framework version: 3.5.0
Realm Object Server version: No
Xcode version: 9.3
iOS/OSX version: ?
Dependency manager + version: CocoaPods : 1.5.0
Sorry if it is not enough information, but this is everything I have.

@tgoyne What it means, currently my code does:
func loadUser(_ realm: Realm?) -> User? {
  return realm?.objects(User.self).filter("someInfo != ''").first
}

import ObjectMapper
import RealmSwift

class User: Object, Mappable {

  @objc dynamic var id: Int = 0
  @objc dynamic var name: String = ""
  @objc dynamic var anotherValue: String = ""
  @objc dynamic var someValue: String = ""
  @objc dynamic var someInfo: String = ""
  @objc dynamic var anotherRealmObject: AnotherRealmObject? //extends Object
  @objc dynamic var defaultValue: Int = 1
  @objc dynamic var defaultRealmObjectTwo: RealmObjectTwo? //extends Object
  @objc dynamic var defaultRealmObjectThree: RealmObjectThree? //extends Object
  let somethingList: List<Something> = List<Something>() //Something  extends Object

  /**
   Initialization of ObjectMapper.
   */
  required convenience init?(map: Map) {
    self.init()
  }

  /**
   This method will map every field to be used with
   the ObjectMapper.
   */
  func mapping(map: Map) {
    id <- map["id"]
    name <- map["name"]
    anotherValue <- map["anotherValue"]
    someInfo <- map["someInfo"]
  }

  override static func primaryKey() -> String? {
    return "id"
  }

}

It was working ok two builds ago, I need to check the exactly version but it started happening after a update of realm-cocoa dependency.

Still crashing and I don't know what to do.

@bmunkholm Send more logs to<EMAIL_ADDRESS>Thanks.

@bmunkholm Can this be the cause?
0  libsystem_kernel.dylib         0x184b2c34c kevent + 8
1  Realm                          0x102f33584 realm::_impl::ExternalCommitHelper::listen() (external_commit_helper.cpp:203)
2  Realm                          0x102f34704 std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0>::operator()() (future:2323)
3  Realm                          0x102f3468c std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >::__execute() (future:1041)
4  Realm                          0x102f3483c std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >::*)(), std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >*> >(void*, void*) (memory:2549)
5  libsystem_pthread.dylib        0x184ce9220 _pthread_body + 272
6  libsystem_pthread.dylib        0x184ce9110 _pthread_body + 290
7  libsystem_pthread.dylib        0x184ce7b10 thread_start + 4

@vsridharan6 Is this happening to you too?

@vsridharan6 I don't think this is the same issue.

I was able to simulate this issue calling on the methods viewWillAppear(happened on iPad on this method on my test device) or viewDidAppear. Seems that Realm is not fully loaded when I try to use the objects. Very strange.
Wrapping the functionviewWillAppear with DispatchQueue.main.async seems to solve the issue, need to check if also solves on viewDidAppear.

I confirm that wrapping the code with DispatchQueue.main.async solves the issue. Should not.

@vsridharan6 The problem is still happening on version 3.7.6. It's so ugly to wrap everything with DispatchQueue.main.async to solve this issue introduced by Realm on my project.

@vsridharan6 This crash is still happening, even wrapping the query on  a DispatchQueue.main.async. Any idea?

I have run into the same issue, any updates?

@ppamorim Are you creating more than one Realm file in the application?

@gvardikos No, I am not.

@ppamorim Hope this can help you:
RLMRealmConfiguration *config = [RLMRealmConfiguration defaultConfiguration];
config.schemaVersion = 1;
config.migrationBlock = ^(RLMMigration *migration, uint64_t oldSchemaVersion) {
    // Never migration, oldSchemaVersion == 0
    if (oldSchemaVersion < 1) {
        [migration deleteDataForClassName:@"User"];
    }
 };
[RLMRealmConfiguration setDefaultConfiguration:config];

@kinarob Why deleting my user model will change something, it doesn't make sense.

@ppamorim You should delete Class that you wouldn't use in the future from the Realm.

I use it...

@realm-admin This error is happening all the time and I don't know how to fix. We had 27 users experiencing it with no reason. I will do a workaround to keep trying to load the user. This issue happens on the very moment when the app starts. Our users are getting stuck and the only way to solve this is reinstalling the app.

@realm-admin I was able to fetch the database from one of our testers in house with this issue, looks like the realm file is corrupted because the app was working fine for a months and suddenly the app started crashing. I've fetch the encryption key (and I am 100% sure that the encryption key is the same since the beginning) from the Keychain and converted it using this script:
So it generated this key:
1709dca07b4026d5b91a7a968ea3038cff5779caa2b6cf3bf263e752d7435f53a73c6b5180e6223f690a6e969bf82b2cea99c8e655d86ce6150c71a38c4647e7

Here is the corrupted .realm file + the raw data from the keychain .raw.
corrupted_realm.zip

You need to add Realm but not RealmSwift.

Without RealmSwift I get this compile error
RealmTestTests.swift:15:27: Cannot call value of non-function type 'module<Realm>

@andreamazz is there a sample repo you can send our way?

@andreamazz is there a sample repo you can send our way?

It's attached to my message above.
Worth noting that I ended up moving back to CocoaPods for the time being, since I had some other issues with SwiftPM and the production build.
Anyway, thanks for the support!

Closing - See @tgoyne comment's on using User and package management.


FzfPreviewDirectoryFiles is slower than fzf.vim's Files command

Hello, FzfPreviewDirectoryFiles is slower than fzf.vim's Files command.
I want to find a file at my user home(~/), if I use FzfPreviewDirectoryFiles ~/,  the preview window will be showed after a long time.

In fzf.vim, the result of the command is piped as it is, so it's fast.
In fzf-preview, fzf receives the result of the command and processes the data in Node (for various functions) before running fzf.
So if you need to input a lot of data at once, fzf may be slow to start.


godep restore + godep save changes revisions

I just did a godep restore on kubernetes followed by godep save ./... - I expected this to be a no-op, but I wanted to verify.  Instead, I find that ONE particular library has had it's version changed to the current tip of the master branch.
I can't figure out why.  godep restore -v is failing (#374 here)
Specifically:
                {
                        "ImportPath": "github.com/coreos/go-systemd/dbus",
-                       "Comment": "v2-27-g97e243d",
-                       "Rev": "97e243d21a8e232e9d8af38ba2366dfcfceebeba"
+                       "Comment": "v4-15-ga831f36",
+                       "Rev": "a831f36d09de8f095c28eeee839df52e9de5031f"
                },

Any clues would be great?  Godep is kind of inscrutable.

What version of godep? (godep version)
Sent from my iPhone

On Dec 20, 2015, at 22:16, Tim Hockin<EMAIL_ADDRESS>wrote:
I just did a godep restore on kubernetes followed by godep save ./... - I expected this to be a no-op, but I wanted to verify. Instead, I find that ONE particular library has had it's version changed to the current tip of the master branch.
I can't figure out why. godep restore -v is failing (#374 here)
Specifically:
            {
                    "ImportPath": "github.com/coreos/go-systemd/dbus",

                  "Comment": "v2-27-g97e243d",

                  "Rev": "97e243d21a8e232e9d8af38ba2366dfcfceebeba"

                  "Comment": "v4-15-ga831f36",

                  "Rev": "a831f36d09de8f095c28eeee839df52e9de5031f"
          },

Any clues would be great? Godep is kind of inscrutable.
—
Reply to this email directly or view it on GitHub.

I did a 'go get -u' yesterday
On Dec 20, 2015 11:54 PM, "Edward Muller"<EMAIL_ADDRESS>wrote:

What version of godep? (godep version)
Sent from my iPhone

On Dec 20, 2015, at 22:16, Tim Hockin<EMAIL_ADDRESS>wrote:
I just did a godep restore on kubernetes followed by godep save ./... -
I expected this to be a no-op, but I wanted to verify. Instead, I find that
ONE particular library has had it's version changed to the current tip of
the master branch.
I can't figure out why. godep restore -v is failing (#374 here)
Specifically:
{
"ImportPath": "github.com/coreos/go-systemd/dbus",

"Comment": "v2-27-g97e243d",
"Rev": "97e243d21a8e232e9d8af38ba2366dfcfceebeba"

"Comment": "v4-15-ga831f36",
"Rev": "a831f36d09de8f095c28eeee839df52e9de5031f"
},
Any clues would be great? Godep is kind of inscrutable.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/tools/godep/issues/375#issuecomment-166227059.

I did a 'go get -u' yesterday

Ok, but what version do you have? It would be helpful if you can run godep version and paste the output here so we know exactly what you have.

It's good to have assumptions challenged.  It turns out I was not running at head, despite go get -u.  v41 seems to work but for a different issue, which I will file it if is not open already


operator vfunction-server-operator (v3.3.1267)

New operator bundle
Name: vfunction-server-operator
Version: v3.3.1267
Certification project: 5f64dc1e0a4d06443d2818ad
Test result URL: https://catalog.redhat.com/api/containers/v1/projects/certification/test-results/id/65b00928211528930fa674d3
Test logs URL: https://catalog.redhat.com/api/containers/v1/projects/certification/artifacts/id/65b00925ca65c8b13b2ba574

/pipeline restart operator-release-pipeline


Release 5.1.0-alpha05

It looks like just this test is failing
org.mobilenativefoundation.store.store5.StoreWithInMemoryCacheTests.storeDeadlock[js, browser, ChromeHeadless<IP_ADDRESS>, Linuxx86_64] FAILED

#665


Add Reverse Proxy

Clear and concise description of the problem
Replace caddy dependency
Suggested solution

[x] Implement dependency-free Bun native reverse proxy

[ ] Ensure it compiles as a binary

[x] bun-reverse-proxy

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide
[X] Check that there isn't already an issue that requests the same feature (to avoid creating a duplicate)

relates to https://github.com/stacksjs/stacks/issues/1039

It's what became rpx:
https://rpx.netlify.app/
https://github.com/stacksjs/rpx


Need option to disable animation for specific overlay (e.g. of mat-select)

Bug, feature request, or proposal:
Feature request
What is the expected behavior?
It would be nice to have option to disable animation for a specific overlay. In our case we need to disable animation of overlay of mat-select growing wider.
What is the current behavior?
Nothing can stop thins animation normally, there is no way to prevent it with css and using @.disabled on overlayContainer through renderer disables animations of everything.
What is the use-case or motivation for changing an existing behavior?
We need to mat-select according to spec, where dropdown list has to be as wide as input itself, but animation always glitches it for a moment.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
@angular-devkit/architect         0.7.5
@angular-devkit/build-angular     0.7.5
@angular-devkit/build-optimizer   0.7.5
@angular-devkit/build-webpack     0.7.5
@angular-devkit/core              0.7.5
@angular-devkit/schematics        0.7.5
@angular/cdk                      6.4.7
@angular/cli                      6.1.5
@angular/material                 6.4.7
@ngtools/webpack                  6.1.5
@schematics/angular               0.7.5
@schematics/update                0.7.5
rxjs                              6.3.1
typescript                        2.9.2
webpack                           4.9.2

+1

any update on this?


[BUG] Adding Knowledge Graph Setup

Describe the bug
When I put in any type of API Provider and the API Key I then go down and click on the Yes radio button and I do not see a Robot Name section, also further more, when I click save literally nothing happens. It does not save. I tried all three different API Providers and nothing saves. When you click on the save button it does nothing. I have tried the web interface I have even tried to manually go in to apiConfig.json and input the information still does not work, when you try to ask Vector a question his respose is only "knowlegde graph is not enabled, this can be enabled in the web interface."
Device you are running wire-pod on (please complete the following information):

OS: [Windows]

I have a similar if not the same issue on a few install on a PI. OpenAI And Together won't save, but None and Houndify will

The latest release should work fine now;

What method did you use for installation and what method are you using to update? My guess is that you did a git pull, but didn't rebuild the chipper binary - so the older code is still running

I did this to update, and Guide 2 to install
sudo systemctl stop wire-pod cd ~/wire-pod sudo ./update.sh sudo ./setup.sh daemon-enable sudo systemctl start wire-pod

Got it working by running this again. Thanks for your help
cd ~/wire-pod
sudo STT=vosk ./setup.sh


JWT plugin cannot be assigned to an Ingress object

NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.

Summary
Error in kong ingress controller while assigning a JWT plugin to a route. Error shown says "expecting a set"
Kong Ingress controller version 0.9.1
Kong or Kong Enterprise version 2.1.0
Kubernetes version
**Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:37:52Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
**
Environment

Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release): CentOS 7
Kernel (e.g. uname -a): Linux 4.4.188-1.el7.elrepo.x86_64
Install tools: Helm 3
Others:

What happened
We have been experimenting with Kong in dbless mode on our kubernetes environment.
We got to the point of setting up some custom plugins on routes using the KongPlugin kubernetes custom resource type (these plugins work).
We created a KongPlugin JWT and associated it to an ingress rule using the annotation tag.
The plugin doesn't get assigned to the route because it is expecting a set, instead it blocks the ingress controller queue and routes are unusable.
Expected behavior
Plugin should be assigned to the route
Steps To Reproduce
We are having an issue creating a JWT plugin passing it the following config:

apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: kong-jwt
  namespace: ingress
config:
  claims_to_verify:
    exp: null
    nbf: null
  key_claim_name: realm
plugin: jwt

Creating the plugin seems to work, we don't see any error logs in the ingress controller
The issue comes up when we create an Ingress object that uses the plugin:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: kong-foo-route
  namespace: ingress
  annotations:
    kubernetes.io/ingress.class: "kong"
    konghq.com/plugins: kong-jwt,kong-rate-limiting
spec:
  rules:
  - http:
      paths:
      - path: /foo
        backend:
          serviceName: aService
          servicePort: 8080

After applying these rules to kubernetes, we get the following log in the Ingress controller

E0807 18:58:05.115303       1 controller.go:128] unexpected failure updating Kong configuration:
posting new config to /config: 400 Bad Request {"fields":{"plugins":[null,null,null,null,null,null,null,null,null,null,null,null,null,{"config":{"claims_to_verify":"expected a set"}},{"config":{"claims_to_verify":"expected a set"}}]},"name":"invalid declarative configuration","code":14,"message":"declarative config is invalid: {plugins={[14]={config={claims_to_verify=\"expected a set\"}},[15]={config={claims_to_verify=\"expected a set\"}}}}"}
W0807 18:58:05.115389       1 queue.go:112] requeuing kong/aRoute, err posting new config to /config: 400 Bad Request {"fields":{"plugins":[null,null,null,null,null,null,null,null,null,null,null,null,null,{"config":{"claims_to_verify":"expected a set"}},{"config":{"claims_to_verify":"expected a set"}}]},"name":"invalid declarative configuration","code":14,"message":"declarative config is invalid: {plugins={[14]={config={claims_to_verify=\"expected a set\"}},[15]={config={claims_to_verify=\"expected a set\"}}}}"}

Seems like we are writing a set, but we are still getting that error. Is this a bug, or do I have an incorrect way of writing a set?

You are providing wrong input.
Please do:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: kong-jwt
  namespace: ingress
config:
  claims_to_verify:
  - exp
  - nbf
  key_claim_name: realm
plugin: jwt

As per the documentation, claims_to_verify must be an array.

@hbagdi That worked. Thank you, not getting the error anymore.


actualizacion-documentacion: agrego diagrama de secuencia, modifico pdf

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@dd08ef1). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop       #6   +/-   ##
==========================================
  Coverage           ?   77.38%
  Complexity         ?       36
==========================================
  Files              ?       12
  Lines              ?       84
  Branches           ?        4
==========================================
  Hits               ?       65
  Misses             ?       16
  Partials           ?        3

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 dd08ef1...2ba4461. Read the comment docs.


feat: add in-memory storage as a fallback for disabled LocalStorage

Hello @mrousavy ✋
I am submitting this pull request to propose the addition of a new feature webFallbackStorage. The purpose of this enhancement is to provide a more resilient storage option for web environments, particularly when users disable localStorage in their browsers.
The webFallbackStorage is designed as an optional property that conforms to the Storage type. It allows the application to handle disabled localStorage situations gracefully by offering eg. in-memory storage as an alternative. This ensures smooth functioning of the application despite any user-imposed limitations.
Right now, react-native-mmkv throws an error and there is no way to run the monorepo with disabled localStorage.
Here's a brief overview of the changes introduced with this feature:

The webFallbackStorage property has been added as an optional attribute, maintaining backward compatibility with existing implementations.
When a user disables localStorage, the application will seamlessly transition to using webFallbackStorage, ensuring no disruption in the user experience.
If the webFallbackStorage property is not provided, the default behavior remains unchanged, and an error will be thrown in case localStorage is disabled.

I believe this enhancement will significantly improve the robustness and flexibility of the react-native-mmkv library.
Later we can add default in-memory storage to the lib.
Please feel free to reach out to me with any questions or suggestions.

This is default behaviour:
White screen + such error message in the console:

Ready to be checked @mrousavy

We have a single warning and my app is up and running 🪄

Hey - for some reason the linter failed. I'll fix that, your PR looks good!
I'm thinking if we should also use the in-memory Map fallback for when JSI is unavailable, e.g. when running in a Chrome debugger?

Hey - for some reason the linter failed. I'll fix that, your PR looks good!
I'm thinking if we should also use the in-memory Map fallback for when JSI is unavailable, e.g. when running in a Chrome debugger?

If it causes a crash then yes, it's still better to have limited experience, yet let the user debug the app.

I think the console.log should only be printed if typeof window !== "undefined"


aws-c-io: 0.9.1 -> 0.9.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/awslabs/aws-c-io/releases.
meta.description for aws-c-io is: "AWS SDK for C module for IO and TLS"
meta.homepage for aws-c-io is: "https://github.com/awslabs/aws-c-io"
meta.changelog for aws-c-io is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.9.2 with grep in /nix/store/izaln6lmkf070pbqsadnvdv9nb3lj79a-aws-c-io-0.9.2

found 0.9.2 in filename of file in /nix/store/izaln6lmkf070pbqsadnvdv9nb3lj79a-aws-c-io-0.9.2

directory tree listing: https://gist.github.com/d68c14b5b859558cb26f95103f5c49eb

du listing: https://gist.github.com/40d282b6b9eb356669c269ff6d00bf76

Rebuild report (if merged into master) (click to expand)

237 total rebuild path(s)

66 package rebuild(s)

65 x86_64-linux rebuild(s)
58 i686-linux rebuild(s)
57 x86_64-darwin rebuild(s)
57 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
aws-c-event-stream
aws-c-io
aws-sdk-cpp
bundix
cabal2nix
cachix
common-updater-scripts
crate2nix
crystal2nix
dep2nix
disnix
disnixos
dydisnix
fusionInventory
go2nix
haskellPackages.cachix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cnix-expr
haskellPackages.hercules-ci-cnix-store
haskellPackages.nix-paths
haskellPackages.update-nix-fetchgit
hercules-ci-agent
hydra-unstable
libnixxml
lispPackages.quicklisp-to-nix
lispPackages.quicklisp-to-nix-system-info
nix
nix-bundle
nix-direnv
nix-doc
nix-du
nix-exec
nix-index
nix-pin
nix-plugins
nix-prefetch
nix-prefetch-bzr
nix-prefetch-cvs
nix-prefetch-docker
nix-prefetch-git
nix-prefetch-hg
nix-prefetch-scripts
nix-prefetch-svn
nix-serve
nix-update
nix-update-source
nixFlakes
nixStable
nixStatic
nixUnstable

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/izaln6lmkf070pbqsadnvdv9nb3lj79a-aws-c-io-0.9.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A aws-c-io https://github.com/r-ryantm/nixpkgs/archive/cbbf036a07d3c3443d502119d78ad6d97b40b25c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/izaln6lmkf070pbqsadnvdv9nb3lj79a-aws-c-io-0.9.2
ls -la /nix/store/izaln6lmkf070pbqsadnvdv9nb3lj79a-aws-c-io-0.9.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @orivej for testing.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 118958 run on x86_64-linux 1

1 package marked as broken and skipped:

nix-exec

2 packages blacklisted:

tests.nixos-functions.nixos-test
tests.nixos-functions.nixosTest-test

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

dydisnix: log was empty
libnixxml: log was empty

58 packages built:

aws-c-event-stream
aws-c-io
aws-sdk-cpp
bundix
cabal2nix
cachix
common-updater-scripts
crate2nix
crystal2nix
dep2nix
disnix
disnixos
fusionInventory
go2nix
haskellPackages.cachix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cnix-expr
haskellPackages.hercules-ci-cnix-store
haskellPackages.nix-paths
haskellPackages.update-nix-fetchgit
hercules-ci-agent
hydra-unstable
lispPackages.quicklisp-to-nix
lispPackages.quicklisp-to-nix-system-info
nix (nixStable)
nix-bundle
nix-direnv
nix-doc
nix-du
nix-index
nix-pin
nix-plugins
nix-prefetch
nix-prefetch-bzr
nix-prefetch-cvs
nix-prefetch-docker
nix-prefetch-git
nix-prefetch-hg
nix-prefetch-scripts
nix-prefetch-svn
nix-serve
nix-update
nix-update-source
nixFlakes (nixUnstable)
nixos-generators
nixos-rebuild
nixos-shell
nixpkgs-review
nixui
python38Packages.nix-kernel
python38Packages.nixpkgs
python38Packages.pythonix
python39Packages.nix-kernel
python39Packages.nixpkgs
python39Packages.pythonix
update-nix-fetchgit
vgo2nix
vulnix

Closing as version 0.10.5 already in master.


Feature: Public/Private insights badge

Type of feature
🍕 Feature
Current behavior
There is no badge identifying if a dashboard is public or private
Suggested solution
Add a badge that checks and displays if a hub page is public or private
https://www.figma.com/file/OpVX6WT7dmWqnwRuEvADMF/OpenSauced-—-Insights-(insights.opensauced.pizza)?node-id=5176%3A6423&t=jZIlELgoFGnOMY8Y-0

Additional context
No response
Code of Conduct

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

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

@bdougie can I work on this?

I went ahead and added you to the @open-sauced/triage team. If you are able to assist in triaging and fixing future bugs, I would love your assistance.
For this feature, please ensure to leverage the design system and ask questions. I have assigned you to the issue.

Alright i'll be sure to ask questions on anything I'm not clear on, thanks.

Can you also me a message in the discord, so I can coordinate your roles there?

Can you also me a message in the discord, so I can coordinate your roles there?

Hi @bdougie, i've opened a pr for this issue and sent a message on discord.


fp16 compatibility

Thanks for the great repo!
Can you point me to what needs to be done to enable fp16 compatibility? I suppose it will need some rewriting in the CUDA kernels. Is it just changing the types in the function declarations or more work that needs to go into it?

Hi @kampelmuehler
I think it is just changing the types, that's a great idea.
You're welcome to make a PR for this.
Cheers,
Thibault

Though now looking at the data of your issue, you may bot be interested in this feature anymore

Thanks, you're right - my interest has dwindled meanwhile


[KIECLOUD-542] Conscious Language on KieCloud repos

Signed-off-by: desmax74<EMAIL_ADDRESS>see: https://issues.redhat.com/browse/KIECLOUD-542
Thanks for submitting your Pull Request!
Please make sure your PR meets the following requirements:

[x] Pull Request title is properly formatted: [RHDM-XYZ] Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Attached commits represent units of work and are properly formatted
[x] You have read and agreed to the Developer Certificate of Origin (DCO) (see CONTRIBUTING.md)
[x] Every commit contains Signed-off-by: Your Name<EMAIL_ADDRESS>- use git commit -s

/retest


refactor(rules): minor refactor to PR #438

:tada: This PR is included in version 1.4.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


DeepMind AlphaMissense

Description of feature
DeepMind AlphaMissense is expected and welcome, better than previous though perhaps a little underwhelmingly so:
https://www.science.org/doi/10.1126/science.adg7492
Download for all missense SNVs:
https://console.cloud.google.com/storage/browser/dm_alphamissense

Now available as a plugin in VEP https://github.com/Ensembl/VEP_plugins/blob/release/112/AlphaMissense.pm. Should make it rather easier to implement. 😸


Brazillian Portuguese Localization

Here is the JSON File with updated pt-BR localization strings
pt-BR.zip

Thanks a lot for the contribution!


 Y'all probably know all about this because you know JavaScript well, but I've seen people blindly copy and paste this code without realizing that var pymChild sets a variable on window. I suggest either explicitly setting it to window.pymChild =  (so it's more clear) or just pym.Child({ renderCallback: myFunc });.

I don't agree that it's useless. I don't want to sidetrack the docs having to explain how top-level variable declarations work in JavaScript, or encouraging people to assign to the window object unthinkingly if they're already copy/pasting code.
We could revise it to let, which does not add properties to the global object. But since Pym is generally on its way out in favor of Sidechain anyway, I'm not particularly driven to spend a lot of time fixing all the old-school flavor of the docs--particularly since that would mean I should probably fix the old-school flavor of the code, and I have no intention of making changes to Pym itself if I can help it.

I don't agree that it's useless. I don't want to sidetrack the docs having to explain how top-level variable declarations work in JavaScript, or encouraging people to assign to the window object unthinkingly if they're already copy/pasting code.
We could revise it to let, which does not add properties to the global object. But since Pym is generally on its way out in favor of Sidechain anyway, I'm not particularly driven to spend a lot of time fixing all the old-school flavor of the docs--particularly since that would mean I should probably fix the old-school flavor of the code, and I have no intention of making changes to Pym itself if I can help it.

I don't agree that it's useless. I don't want to sidetrack the docs having to explain how top-level variable declarations work in JavaScript, or encouraging people to assign to the window object unthinkingly if they're already copy/pasting code.
We could revise it to let, which does not add properties to the global object. But since Pym is generally on its way out in favor of Sidechain anyway, I'm not particularly driven to spend a lot of time fixing all the old-school flavor of the docs--particularly since that would mean I should probably fix the old-school flavor of the code, and I have no intention of making changes to Pym itself if I can help it.

It is useless in the literal sense that these three snippets are absolutely identical:
A)
<script>
    var pymChild = pym.Child({ renderCallback: myFunc });
</script>

B)
<script>
    pymChild = pym.Child({ renderCallback: myFunc });
</script>

C)
<script>
    window.pymChild = pym.Child({ renderCallback: myFunc });
</script>

I think C is the most clear to readers, but B is also fine. A is bad because it is misleading and makes pymChild look like a local variable.

encouraging people to assign to the window object unthinkingly if they're already copy/pasting code

The docs are already doing that though?

No, it encourages them to create a local variable. That has the side effect, at a top-level scope, of assigning to the global object. It may seem like a distinction without a difference, but I think showing people who are relatively inexperienced at JS (which is the kind of person you're talking about here) that they should define values by either leaving off the var keyword or explicitly assign to the global object is a bad practice, especially if they take that lesson and start using Pym inside of an init function or something similar.
Yes, in this particular case of a bare script tag on the window, using var has side effects. But that's not a bug in Pym, it's a bug in JS. I think the alternatives are worse. And unless you're worried that there's going to be a window.pymChild value that would be shadowed or overwritten by the assignment, I don't understand what the harm is. In the context of a normal page (particularly an iframed child page--and thus sandboxed/isolated JS context), this is a perfectly reasonable thing to do.

I don't think we're going to agree, so I'll let this be my last comment, but I think that many casual users of JavaScript have no idea what var does, and seeing a code sample which creates a global using var just adds to their confusion. For most use of Pym, there's nothing wrong with window.pymChild, but it's better to be explicit rather than implicit when using it.


log failed tasks

Please describe the problem you're trying to solve
I am trying to implement the suggested solution https://github.com/sxyazi/yazi/discussions/1103 so I updated to nightly yazi, doing so I noticed the "28 tasks" in taskbar. Typing w prompted the task list with this result:

Typing "Enter" on one of the entry I got:
Preload task failed:
error converting Lua nil to function

Would you be willing to contribute this feature?

[ ] Yes, I'll give it a shot

Describe the solution you'd like
I tried to get more context via less /home/teto/.local/state/yazi/yazi.log but the file remains empty  (I had previously removed it).
I believe failed tasks should be logged in the log file. And maybe the UI could be improved to show more info:

the tasklist could show if the task is running or failed ?
I am not sure how the task name Run preloader 'mime' is supposed to help me.

Here is the excerpt from my config:
[plugin]
# https://yazi-rs.github.io/docs/configuration/yazi/#plugin
preloaders = [
	{ name = "*", cond = "!mime", run = "mime", multi = true, prio = "high" },
	# Image
	{ mime = "image/vnd.djvu", run = "noop" },
	{ mime = "image/*",        run = "image" },
	# Video
	{ mime = "video/*", run = "video" },
	# PDF
	{ mime = "application/pdf", run = "pdf" },
]

prepend_previewers = [
  # sync = true
  { name = "*.chunks", run = "chunks" },
  { name = "*.jsonzlib", run = "jsonzlib" },
  { mime = "audio/*", run = "zaz" },
]

is mime the name of a builtin preloader ?
Additional context
once again thanks a lot for this amazing software that never ceases to amaze me

Hi, this is a breaking change for the upcoming Yazi v0.3 release. Please remove the mime plugin from your preloaders. See https://github.com/sxyazi/yazi/issues/1046 for details.

thanks it helped. I will let you close or let open depending on what you think of this part of my message

I believe failed tasks should be logged in the log file. And maybe the UI could be improved to show more info:
the tasklist could show if the task is running or failed ?
I am not sure how the task name Run preloader 'mime' is supposed to help me.

Do you mean to move the errors from the task manager to the log file for async tasks, or to keep the errors in the task manager and also copy them to the log file?
The reason I didn't add them to the error log before is that async tasks are often concurrent, making it hard to track their order in the log. But in the task manager, we can inspect and view errors in the list for each task individually.

And maybe the UI could be improved to show more info:
the tasklist could show if the task is running or failed ?

Added to the Feature Requests as Group tasks in Task Manager by "Running"/"Failed"

Added some error notifications for the mime plugin, hoping to make the transition to v0.3 smoother :)


Radiology insights GA

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure:azure-health-insights-radiologyinsights

There is FhirR4## classes that likely would be duplicated in future module from healthinsights. And it would be very hard to move them to shared lib, after GA.
Do we have a decision on this?

There is FhirR4## classes that could be duplicated in future module from healthinsights (e.g. cancerprofiling, clinicalmatching, etc.). And it would be very hard to move them to shared lib, after GA.
Do we have a decision on this?

That has been discussed and the current decision was not to have a shared lib.

There is discussion of the method signature of the LRO API in apiview
https://apiview.dev/Assemblies/Conversation/c48b47bd12a6493aa27b2cec58f9e54e#46f262e257de451485c82b43abb61bb5
Please reach a decision (if possible in SDK review meeting). I can help you customize this API whatever the decision be (the customize on method parameter should be very simple; the customize on method return would need some knowledge). Ping me when you need my help.

/azp run java - healthinsights - ci

/azp run java - healthinsights - ci

The branch seems having problem. There's 2516 files

The branch seems having problem. There's 2516 files
There's also over 1200 Checks which pretty much amounts to the build storm that's happening.
@koen-mertens I think the base way to sort this out is to rebase you branch on top of main.


[modify] check descendants' checkbox on tree ui

Coverage decreased (-0.04%) to 84.835% when pulling 456c5764625aa89099d6b8d2765664fce3b83301 on pr-check-descendants into 1cab9199668d445e17cf6a1de853e208070bdbff on master.


Fixed local test suite by syncing MySQL and MariaDB versions from CircleCI config

Goal
MySQL and MariaDB versions are not the same between .circleci/config.yml and tests/docker-compose.yaml, and as such, the local test suite fails on the master branch whereas it passes in CircleCI.
I've synced versions of MySQL and MariaDB databases so that local tests work correctly.
Please see Issue #423 for more context.

Thanks. Looks good.


[WIP] slashing interface

What does this PR/Draft:
It tries to introduce a few traits (Misconduct, Slashing wrapper, OnSlashing) to introduce a generic interface to slash misbehavior(s)
Roughly those have the following functionality:

Slashing: A wrapper trait that takes AccountID and misconduct as input which doesn't
handle balance.
Assumed to implemented on top of a module that implements the system::Trait

Misconduct: Trait that defines a type that handles severity level

OnSlashing: A trait to handles balance and concrete slashing, i.e, need to both call T::Currency::free_balance() and T::Currency::slash() based on severity_level estimated by the Misconduct
Assumed to implemented on top of a module that handles Currency a.ka BalanceOf<T>

Example use case
// MyModule is type that implements `system::Trait`
use crate::MyModule;

let misbehaved = vec![1, 2, 3, 4, 5, 6];
let num_validators = 100;
let era_len = get_era_len();
let severity_level = Slashing:<MyModule>::slash(&misbehaved, num_validators, era_len, &misconduct::Unresponsive);
// use severity_level to determine whether to kick out the validator or not

Additional types
Fraction type that handle fractions
Misconduct types, the GRANDPA types are just to check if the interface works and should be moved somewhere else or removed. In addition, I'm not sure which types should be defined in substrate vs polkadot but I guess Unresponsiveness makes sense and Parachain doesn't not make sense.
Unresolved issues/questions:

[ ] Where to put default misconduct types (currently slashing/src/misconduct.rs)
[ ] Remove hack Misconduct::Severity -> u128 -> BalanceOf<T>

References
https://research.web3.foundation/en/latest/polkadot/slashing/

A fair/good observation grumble from Rob is: if we slash on the end_on_era is you can get slashed logarithmically less by splitting your misbehavior on either side of the era
After removing ContinuousMisconduct the on_signal doesn't make sense anymore and we want to support slashing after a certain window too, such as era_len * k
The interface would look something like for a window of era_len * 2:
// first era
// severity is not returned only era_len has passed
let s = slash(&misbehaved, num_validators, era_len, &misconduct::Unresponsive);
// window has expired
let s = slash(&misbehaved, num_validators, era_len, &misconduct::Unresponsive);

take_action_based_on_severity(s);

A solution could be to require the Misconduct implementer to keep track window_length and current_length
However, it would require reporters to report via slash even if number of misbehaved is zero otherwise we won't know how to close a window

assert_eq(0, severity, "only one era reported, need at least 2");

OK, so I talked through this with Alfonso...
I think rather than having a rolling window of misbehavior that has happened in the last few eras, we keep a rolling window of misbehavior that happened in the last N sessions (with that being a parameter of the slashing system). These last N sessions may cover the boundaries of more than one era.
Also, to shed a bit of clarity on another point: we discussed the possibility of going back and slashing again for prior offences when another offence of the same type has been committed and was mapped onto a higher slashing value on the exponential curve. At the moment, we decided that this is not something we want in the initial system.

I think rather than having a rolling window of misbehavior that has happened in the last few eras, we keep a rolling window of misbehavior that happened in the last N (>=1, includes current) sessions (with that being a parameter of the slashing system). These last N sessions may be part of more than one era. Typically N should be > 2.

Ahhh, nice. Do you think we can have an associated const for N in the Misconduct trait then? Or does it have to be configurable at runtime?

Need significant amount refactoring


Split up utils.generic module

The generic module has accumulated many unrelated functions. These should be split up into more specific modules.

Done in #207.


Add allowIDFA to react native GA

Checklist

[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added all necessary documentation (if appropriate)

What was done
Added functionality to allow IDFA collection for the react-native Google Analytics package. This signals to GA whether the app is allowed to use the advertiser identifier for the device to deliver adds or collect ad click attribution.
Not sure how to go about adding a test for this, we've been using this change in production for a while now.

Going to move this to a separate branch as have a few other changes to add


Fix logic for _run_test in frames_test.py

Came across this while trying to debug other things, but if a series has a non-unique index run_test would fail because ser.columns doesn't exist.
I guess none of our existing tests have non-unique indices for series.

something is not right with test infra

asked in https://github.com/apache/beam/pull/28539

Checked: Dataframe precommit, formatter and lint GHA tasks, noted BUILD successful in the logs, failure is during teardown and unrelated to the PR.


updated for velero 1.14

Why the changes were made
go.mod changes for Velero 1.14 (including golang 1.22)
velero CRD changes for 1.14
some oadp operator code changes to cope with controller-runtime upgrade to 0.17.2
How to test the changes made

/test all

README links can also be updated
Example https://github.com/openshift/oadp-operator/blob/oadp-1.4/README.md?plain=1#L9

retest when https://github.com/openshift/release/pull/52511 goes in

/retest

# github.com/openshift/oadp-operator/pkg/leaderelection
pkg/leaderelection/leaderelection.go:41:4: k8s.io/klog/v2.Warning call has possible Printf formatting directive %v how much

error

/retest

/retest ci/prow/4.14-e2e-test-aws

/test 4.14-e2e-test-aws

/cherry-pick master


parseInt(new_scratch_preset)

looks good locally (and on Vercel)... the initial preset state is "Custom" but as soon as a platform is selected, the Preset works (for all platforms) - I dont know whether we care enough about that?
Fixes #907.

We should probably handle the initial case where parseInt returns NaN

bleurgh.

I give up :)

nah this change is junk.

Right. am finally happy with this. I dont know if there is a better way that would replace the need for the ready var?


Request a track icon

@iHiD I thought the Wren bird looked a little small in the icon you showed me before... didn't seem proportional with the other languages, perhaps... should someone perhaps have a second look at that?

(cc @taiyab)

@joshgoebel Yea, I'll sort it out.


Liquid Exception: GET 404 Not Found

If I don't set noscript: false in _config.yml, a Liquid exception is raised at build time:
/Users/frank/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/jekyll-gist-1.4.0/lib/jekyll-gist/gist_tag.rb:86: warning: constant Jekyll::Gist::GistTag::TimeoutError is deprecated
  Liquid Exception: GET https://api.github.com/gists/DirtyF/24cb9c96b64173ecd85578f38bcc940d: 404 - Not Found // See: https://developer.github.com/v3 in /Users/frank/code/jekyll-fr.org/_posts/2016-09-18-utiliser-des-plugins-jekyll-avec-github-pages.markdown
jekyll 3.2.1 | Error:  GET https://api.github.com/gists/DirtyF/24cb9c96b64173ecd85578f38bcc940d: 404 - Not Found // See: https://developer.github.com/v3

I don't know if it's related, but even if I add a JEKYLL_GITHUB_TOKEN with Gist, our tiny blog takes more than a minute to build 🐢  , with just two embedded Gists, whereas without gists it takes a few seconds. 🐎
At this point, I might as well remove the gists and insert code snippets 😥

@DirtyF It sounds like the timeouts we're using to fetch the gists are fairly high (30s to create connection, 30s to read, etc). Getting a 404 means the URL it's trying to hit doesn't exist – did you confirm that the gist still exists? Maybe our URL needs to be updated.

Thanks @parkr for the reply ❤
I re-checked and the issue is still present if I remove gist.no-scriptoption from config.
/Users/frank/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/jekyll-gist-1.4.0/lib/jekyll-gist/gist_tag.rb:86: warning: constant ::TimeoutError is deprecated
  Liquid Exception: GET https://api.github.com/gists/DirtyF/24cb9c96b64173ecd85578f38bcc940d: 404 - Not Found // See: https://developer.github.com/v3 in /Users/frank/code/jamstatic.fr/_posts/2016-09-18-utiliser-des-plugins-jekyll-avec-github-pages.markdown
jekyll 3.3.1 | Error:  GET https://api.github.com/gists/DirtyF/24cb9c96b64173ecd85578f38bcc940d: 404 - Not Found // See: https://developer.github.com/v3

What I don't get is that https://gist.github.com/DirtyF/24cb9c96b64173ecd85578f38bcc940d exists. 🤔

Gists are referenced by their ID alone, no need to put a username in front.
- {% gist DirtyF/24cb9c96b64173ecd85578f38bcc940d %}
+ {% gist 24cb9c96b64173ecd85578f38bcc940d %}

Indeed, it works if I remove the GitHub username. 💭
Thanks!  @pathawks
FYI I just followed blindly the example usage given in the README

We should simply strip the username from the gist ID when noscript: false.

Can someone please reopen this issue as it is still a thing. Just ran into this myself. And yes, the gist being referered to does exist.
C:/path-to/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-gist-1.4.1/lib/jekyll-gist/gist_tag.rb:96: warning: constant ::TimeoutError is deprecated
  Liquid Exception: GET https://api.github.com/gists/jrfnl/e5af95370fdb834ad7d696b4112c8d0c: 404 - Not Found // See: https://developer.github.com/v3/gists/#get-a-specific-revision-of-a-gist in gisttest.md
jekyll 3.6.2 | Error:  GET https://api.github.com/gists/jrfnl/e5af95370fdb834ad7d696b4112c8d0c: 404 - Not Found // See: https://developer.github.com/v3/gists/#get-a-specific-revision-of-a-gist


functorch.jvp doesn't work with AOTAutograd

def f(x):
  return x.cos()

def g(x, y):
  return functorch.jvp(f, (x,), (y,))

def t(x,_):
  print(x.code)
  return x

print(g(torch.ones(1), torch.ones(1)))
print(aot_function(g, t)(torch.ones(1), torch.ones(1)))

Not totally sure why.

Today I learned: autograd.Function turns off forward-mode AD computation. We probably just want to turn it back on like how grad/vjp turn reverse-mode AD computation back on. This might actually be the same thing as https://github.com/pytorch/functorch/issues/436

@Chillee I'm not sure how to read the output. This is how it is after https://github.com/pytorch/functorch/pull/607 went in. Is this fixed?

Yeah, sorry, I should have put the original error.
Previously it just crashed lol. The second graph is just just the "backwards pass" - since you're just running forward-mode AD with no backwards pass it works fine now.


Under subject settings page, allow subject to update sheets, or lock existing sheets

@mcailler can you add more information here? Thanks!

Not hearing anything for 9 months, we are closing the issue.


ContextException: Starting the process failed

Lately I'm getting this error when using amphp/parallel. When I check the previous exception it is
Amp\Parallel\Context\ContextException: Starting the process timed out.

Any idea what could be wrong here and how to fix it?

I tried to wrap the yield enqueue($task); call in a loop, catching the exception and retry on failure. With that I'm getting this:
User Warning: Worker in pool crashed with exception on shutdown: User Warning: Worker in pool exited unexpectedly with code -1

I tried with both uv and native driver, same result.

The issue disappeared when I removed xdebug. :thinking:

It appears that you're starting a worker from within another worker, is that the case?
How many workers total are you spawning?

Issue can be solved by modifying Amp\Parallel\Context\Internal\ProcessHub::PROCESS_START_TIMEOUT. It would be cool to have this configurable instead of hardcoded.

It appears that you're starting a worker from within another worker, is that the case?

No. Worker was started from the main loop process.

How many workers total are you spawning?

The error appeared with the first worker already.

Issue can be solved by modifying Amp\Parallel\Context\Internal\ProcessHub::PROCESS_START_TIMEOUT. It would be cool to have this configurable instead of hardcoded.
EDIT: I'm using grumphp and it's spawning multiple xdebug instances. After increasing said constant the issue went away.

How far did you increase it? I remember trying that as well to no avail.

@enumag I just added zero at the end.

Yeah, I tried even higher to no avail. It's simply not working for me with xdebug active.

Hi,
I have this problem too.
I have no xdebug install, and i try to increase PROCESS_START_TIMEOUT with no success.
I just try to execute the code on this link https://amphp.org/parallel/
My environnement :
centos 7
apache 2.4.6
php 7.2
the error :
500
Amp\Parallel\Context\ContextException
Starting the process failed
.../vendor/amphp/parallel/lib/Context/Process.php
202
Thank for your help

Closing this issue, since this has been completely refactored in v2 to allow full customization of context IPC.


[nginx] fix metrics metadata

What does this PR do?
Fixes https://github.com/DataDog/integrations-core/issues/797
Versioning
Changes only affect the backend, no need to bump the version.

The metadata is actually correct here:

the metric type in the metadata files describes the in-app metric type (also known as API metric type)
that metric type is not necessarily the same as the name of the method used in the checks

When a metric is submitted with AgentCheck.rate, it's actually sent with the gauge API metric type. So the metadata is correct.
See https://docs.datadoghq.com/metrictypes/ for more details


chore(master): release 2.0.0-rc.135

:robot: I have created a release beep boop
2.0.0-rc.135 (2024-12-13)
Features

add ConsumerInactiveThreshold to NatsStreamConfiguration (#1014) (7d66579)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v2.0.0-rc.135
:sunflower:


[Icon Request] Support Jest

[x] I'm sure this issue is not a duplicate?
[x] I want to create an icon request:
- Type: extension
- Icon Name: jest
- Sample original Icon:
- Extensions: 'jest.config.json'

as soon as you had published the steps to edit svgs in Inkscape, let me know ^^

@jens1o I already have the logo in SVG. Will make a PR tomorrow.


Add native qcow2 boot test

Add an end-to-end qcow2 test that follows a customer's steps with
composer-cli. The image is booted with libvirt to allow the best
virtualization options to be chosen by libvirt. It also uses libvirt's
default network.
Signed-off-by: Major Hayden<EMAIL_ADDRESS>

Two benefits here:

Our qcow2/openstack tests now use composer-cli like a customer would.
We can run these tests on systems without nested virt, like ec2.

Hm, by dropping the other tests we are no longer doing the image-info tests and this is doing the tests against update repos which are changing under us, right?
I think it is very nice test to have, but could we do it in addition? And maybe not make it blocking? @larskarlitski

@teg Sure, we can set this up however we want. We can run these entirely separately too, if we want.

I think it is very nice test to have, but could we do it in addition? And maybe not make it blocking? @larskarlitski

Agreed.

Thanks, @teg!


Allowing support for initializing multiple nocs and customizing command buffer configuration when creating kernels

Currently, user can specify a single noc to KernelConfig, which is used to initialize the default noc_index used in kernels. Our command buffers are defined in noc_nonblocking_api.h, and the specific ones used are hardcoded in dataflow_api.h.
There are use cases for both fast dispatch and user kernels where we want customized implementations for this.
Ex.
brisc (use noc 0 and 1): use cmd_buf 0 and 1
ncrisc (use noc 0 and 1): use cmd_buf 2 and 3
where for a risc, one command buffer is for reads, the rest is for regular, small, and atomic writes.
@pgkeller @yugaoTT

@tt-aho I added the support in yugao/noc
Basically I replaced one of the pad field with noc_mode.
Please let me know if the impl is okay or not

@tt-aho I added the support in yugao/noc Basically I replaced one of the pad field with noc_mode. Please let me know if the impl is okay or not

We're planning for more generic support where we have the current default config or user can manually configure the cmd buf distribution themselves, as for example our configuration for FD is not the same as what's in yugao/noc.

@yugaoTT @tt-aho this is handled w/ the new flexible noc changes, right?  close?

yeah I belive so, we can have other NoC configs for FD


OpenSearch cluster/domain provisioning support

Build support to provision Amazon OpenSearch Service domains. This should be built as a plugin allowing users to selectively use plugins of their choice.

Since OSB is an open-source project, provisioning clusters based off a specific cloud provider would not be part of its charter.  This could be implemented via a generic plugin-type mechanism that could be applied to various services, and would be tackled as a separate issue.


Don't mess with Windows line endings

Summary
During some rc releases we have seen the file gradlew.bat get diffs from release to release, and sometimes the diff is nothing, except some script messing with the line endings of that file.
According to this and my own experiments using unix2dos and dos2unix to swap the line endings of that file, this change fixes this problem.
We specify all the .bat files should have the Windows line endings.

Changelog

[General] [Fixed] - Specify line endings of .bat files for Windows in .gitattributes
Test Plan

To assist with the test, you can use brew install unix2dos.

Init a new project or use an existing one.

Make sure in your .gitattributes of the project and of the user (home dir or .config/git/attributes don't have anything about .bat files, or * text=auto.

Run unix2dos ./android/gradlew.bat.

Check git status.

Run dos2unix ./android/gradlew.bat.

Check git status.

You will notice that the changes when swapping around are the whole file changed.

Using the changes in this PR, and doing the above, the git status will be no changes, as it should be. The line changes stay Windows-style.

Thanks, I’m excited to have this not be a problem anymore. However, this change will still require a change to everyone’s project to add this. Could we avoid that? Could we make this change in React Native core to make sure that PRs modifying the gradle file don’t change the line endings? Once people init a project I don’t care so much if they cause the file’s line endings to be swapped.

I guess we could, but to be honest I think this change is the better way.
I haven't found where and when this broke (I haven't looked too hard though), but I think this could happen again by just having some formatter or linter that is a tiny more too zealous.
I also don't know if Windows is fine with that file having unix line endings, no matter if the change came from a new project, an upgrade, or a change in a user's computer.
As an extra, I have this rule on some of my machines at my user dir git config, when I know I might touch files like that there. This is a good/sensible default that is not there on many dev machines, unfortunately.
So based on these reasons, I think adding it here is the better choice. But if you think we should find where this broke (rn or cli or elsewhere) and add it there, I would be ok to add it there too, not only there. Does that make sense?

The bumps look like they were made as part of a Facebook employee doing a codemod across the internal repo: https://github.com/facebook/react-native/commits/master/template/android/gradlew.bat
When people upgrade and see this change to the gitattributes in their project they'll wonder why it matters. I'd rather avoid changes to the template that we can avoid.
I'd feel more comfortable adding it to here to cover the existing use case and punt on the decision to add it to the template in the case we run into problems later.

Alright, as you think it's best. 👍
I can make a PR to change it for the rn repo and not the template. Let's close this one then?

Do you want to change this PR to modify the other file?
I think it's reasonable from our side to make the case that they are suggestions not requirements, but I'm not sure if that's how other people see them. Personally, I would think I should make all the changes in the upgrade helper because if I don't future upgrades will be less clear, or I'll realize I actually need a step that I skipped a couple releases back and now have problems with my project. I'm not sure how we fix that or communicate the intent better which is why I'm trying to be fairly protective of the template.
I don't actually know much about these line endings and don't frequently work on open source projects with React Native, so it is possible that putting it in the template is the right choice and I'm happy to be overruled with some more voices. In the mean time though, it's definitely reasonable to add it to the core .gitattributes so we should at least do that and revisit adding it to the template if we hear more opinions. Does that sound okay?

Fair, I'll edit the PR here to change the other file, and I will revert the current changes. Then we either tag some people that could give opinions, or we leave it and revisit if this comes up again.


Add ColorImage::from_gray_iter

Add an alternative method for creating a [ColorImage] that accepts Iterator as the argument. It can be useful when &[u8] is not available but the iterator is.

please fix the compilation if you want this merged


Improve error message when running multiple main programs at once

When running multiple main programs at once in a package,  following error message is printed:
ballerina: <filename>:<lineNo>: redeclared symbol 'main'
Error message can be improved to log a proper message.

In semantic analyzer, the main function is also treated in the same way as other functions. hence the error message is printed to be consistent with the other functions.


feat: add deploy alias

@raaymax any ideas on why the CI might be failing?

No idea, it's failing the same way also in the other PR..

Found this https://github.com/microsoft/playwright/issues/30368
Seems to be related to ubuntu 24 🤔

It does, so how do we fix? cc @FabienArcellier

Looks like it run this time though?

You have no idea how much time I spent in click docs searching for exactly something like this...
Shout out to @FabienArcellier :D


Proposed remove step 1

Proposed remove Step 1 which is not necessary. That can cause confusion as this certificate is a Public Commercial Certificate (DigiCert Global Root CA) and is not related for native Azure certificate authentication which requires only self sign PFX and Root CA certificates.

@dmauser : Thanks for your contribution to the Azure documentation! The author, @cherylmc, has been notified to review your proposed change.

Thanks @dmauser. I will send this over to Aanand, as he is working on the updates for this. I'll go ahead and close this PR and incorp this change in Aanand's PR. Thanks again!

@aanandr  - I'm going to close this PR, but we'll want to make sure the updates you are working on incorp this feedback. #please-close


Return an error if multiplex message is empty

Right now if the message is empty, this
https://github.com/paradigmxyz/reth/blob/66c9403ea1d3d03938eafc099e64e789aadc3616/crates/net/eth-wire/src/multiplex.rs#L169
and this
https://github.com/paradigmxyz/reth/blob/66c9403ea1d3d03938eafc099e64e789aadc3616/crates/net/eth-wire/src/multiplex.rs#L512
will panic. We should use .get(0) here and return an error if the call returns None.

Let me do this :)

Hey, I'd like this one