Other VDMs

Hi @visionMaze @Zhen-Dong ,
thanks for the interesting work! May I ask if there is any plan to apply this method to other VDMs, such as VideoCrafter?

Thank you for your interest.
Our framework is suitable for any LDM-based models, including VideoCrafter. The efforts differ based on the compatibility of the open-sourced implementation of models. Our near-term plan is to integrate SD-XL, and if there are more requirements to integrate with other LDM models such as VideoCrafter after that, we would like to work on that.

Thank you for your interest.
Our framework is suitable for most LDM models. The integration efforts differ based on the compatibility of open-sourced implementation. Our near-term plan is to integrate SD-XL first. If there are more requirements/rationales to integrate other LDM models such as VideoCraft, we would like to work on that.


Encoding::UndefinedConversionError - "\xD7" from ASCII-8BIT to UTF-8:

Starting MailCatcher
==> smtp://<IP_ADDRESS>:1025
==> http://<IP_ADDRESS>:1080
==> SMTP: Received message from<EMAIL_ADDRESS>(909 bytes)
*** Error sending message through websocket: {"id"=>1, "sender"=>"<noreply@examp
le.com>"<EMAIL_ADDRESS>"subject"=>"\xD7\x94\xD7\
xA8\xD7\xA9\xD7 \xD7\x94 \xD7\x91\xD7 \xD7\xAA\xD7\xA8 sugar10.local"
, "source"=>"To<EMAIL_ADDRESS>\xD7\x94\xD7\xA8\xD7\xA9\xD
7 \xD7\x94 \xD7\x91\xD7 \xD7\xAA\xD7\xA8 sugar10.local\r\nX-PHP-Origi
nating-Script: 0:Email.php\r\nUser-Agent: CodeIgniter\r\nDate: Thu, 11 May 2017
13:17:14 +0300\r\nFrom: \"test\"<EMAIL_ADDRESS><noreply@
example.com>\r\nReply-To<EMAIL_ADDRESS><EMAIL_ADDRESS>der<EMAIL_ADDRESS>xampp\r\nX-Priority: 3 (Normal)\r\nMessage
-ID<EMAIL_ADDRESS>1.0\r\nContent-Type: text/plai
n; charset=utf-8\r\nContent-Transfer-Encoding: 8bit\r\n\r\n\xD7\xA9\xD7\x9C\xD7\
x95\xD7\x9D sadasdas,\r\n\r\n\xD7\xAA\xD7\x95\xD7\x93\xD7\x94 \xD7\xA9\xD7\xA0\x
D7\xA8\xD7\xA9\xD7\x9E\xD7\xAA \xD7\x91\xD7\x90\xD7\xAA\xD7\xA8 sugar
10.local!\r\n\r\n\r\n\xD7\xA2\xD7\x9C \xD7\x9E\xD7\xA0\xD7\xAA \xD7\x9C\xD7\x94\
xD7\xA9\xD7\x9C\xD7\x99\xD7\x9D \xD7\x90\xD7\xAA \xD7\xAA\xD7\x94\xD7\x9C\xD7\x9
9\xD7\x9A \xD7\x94\xD7\x94\xD7\xA8\xD7\xA9\xD7\x9E\xD7\x94, \xD7\xA2\xD7\x9C\xD7
\x99\xD7\x9A \xD7\x9C\xD7\x90\xD7\x9E\xD7\xAA\r\n\xD7\x90\xD7\xAA \xD7\x94\xD7\x
93\xD7\x95\xD7\x90\"\xD7\x9C \xD7\xA9\xD7\x9C\xD7\x9A \xD7\x91\xD7\x9C\xD7\x97\x
D7\x99\xD7\xA6\xD7\x94 \xD7\xA2\xD7\x9C \xD7\x94\xD7\xA7\xD7\x99\xD7\xA9\xD7\x95
\xD7\xA8 \xD7\x94\xD7\x91\xD7\x90:\r\n\r\nPlease follow the link to confirm your
 registration\r\nhttp://sugar10.local/users/confirm/ca2c2c7034\r\n\r\
n\r\n\xD7\x91\xD7\x91\xD7\xA8\xD7\x9B\xD7\x94,\r\n\xD7\xA6\xD7\x95\xD7\x95\xD7\x
AA \xD7\x90\xD7\xAA\xD7\xA8 \xD7\xA9\xD7\x95\xD7\x92\xD7\xA8 \xD7\x93\xD7\x93\xD
7\x99\r\n\r\n", "size"=>"909", "type"=>"text/plain", "created_at"=>#<DateTime: 2
017-05-11T10:17:17+00:00 ((2457885j,37037s,0n),+0s,2299161j)>}
    Exception: "\xD7" from ASCII-8BIT to UTF-8
    Backtrace:
       C:/Ruby23-x64/lib/ruby/2.3.0/json/common.rb:224:in `encode'
       C:/Ruby23-x64/lib/ruby/2.3.0/json/common.rb:224:in `generate'
       C:/Ruby23-x64/lib/ruby/2.3.0/json/common.rb:224:in `generate'
       mailcatcher (0.6.5) lib/mail_catcher/web/application.rb:69:in `block (3 l
evels) in <class:Application>'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block (3 levels) in push'

       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `each'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block (2 levels) in push'

       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `each'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block in push'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:256:in `schedule'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `push'
       mailcatcher (0.6.5) lib/mail_catcher/mail.rb:57:in `block in add_message'

       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:981:in `block in run_deferred_
callbacks'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:978:in `times'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:978:in `run_deferred_callbacks
'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:193:in `run_machine'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:193:in `run'
       mailcatcher (0.6.5) lib/mail_catcher.rb:173:in `run!'
       mailcatcher (0.6.5) bin/mailcatcher:5:in `<top (required)>'
       C:/Ruby23-x64/bin/mailcatcher:22:in `load'
       C:/Ruby23-x64/bin/mailcatcher:22:in `'
    Please submit this as an issue at http://github.com/sj26/mailcatcher/issues
2017-05-11 13:17:21 - Encoding::UndefinedConversionError - "\xD7" from ASCII-8BI
T to UTF-8:
        C:/Ruby23-x64/lib/ruby/2.3.0/json/common.rb:224:in `encode'
        C:/Ruby23-x64/lib/ruby/2.3.0/json/common.rb:224:in `generate'
        C:/Ruby23-x64/lib/ruby/2.3.0/json/common.rb:224:in `generate'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/mailcatcher-0.6.5/lib/mail_catche
r/web/application.rb:81:in `block in <class:Application>'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1611:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1611:in `block in compile!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:975:in `block (3 levels) in route!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:994:in `route_eval'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:975:in `block (2 levels) in route!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1015:in `block in process_route'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1013:in `catch'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1013:in `process_route'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:973:in `block in route!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:972:in `each'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:972:in `route!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1085:in `block in dispatch!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1067:in `block in invoke'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1067:in `catch'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1067:in `invoke'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1082:in `dispatch!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:907:in `block in call!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1067:in `block in invoke'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1067:in `catch'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1067:in `invoke'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:907:in `call!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:895:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-protection-1.5.3/lib/rack/pr
otection/xss_header.rb:18:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-protection-1.5.3/lib/rack/pr
otection/path_traversal.rb:16:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-protection-1.5.3/lib/rack/pr
otection/json_csrf.rb:18:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-protection-1.5.3/lib/rack/pr
otection/base.rb:49:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-protection-1.5.3/lib/rack/pr
otection/base.rb:49:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-protection-1.5.3/lib/rack/pr
otection/frame_options.rb:31:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-1.6.6/lib/rack/nulllogger.rb
:9:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-1.6.6/lib/rack/head.rb:13:in
 `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:182:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:2013:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1487:in `block in call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1787:in `synchronize'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb
:1487:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-1.6.6/lib/rack/urlmap.rb:66:
in `block in call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-1.6.6/lib/rack/urlmap.rb:50:
in `each'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-1.6.6/lib/rack/urlmap.rb:50:
in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rack-1.6.6/lib/rack/builder.rb:15
3:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/mailcatcher-0.6.5/lib/mail_catche
r/web.rb:19:in `call'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/thin-1.5.1/lib/thin/connection.rb
:81:in `block in pre_process'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/thin-1.5.1/lib/thin/connection.rb
:79:in `catch'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/thin-1.5.1/lib/thin/connection.rb
:79:in `pre_process'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/thin-1.5.1/lib/thin/connection.rb
:54:in `process'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/thin-1.5.1/lib/thin/connection.rb
:39:in `receive_data'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmac
hine.rb:193:in `run_machine'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmac
hine.rb:193:in `run'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/mailcatcher-0.6.5/lib/mail_catche
r.rb:173:in `run!'
        C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/mailcatcher-0.6.5/bin/mailcatcher
:5:in `<top (required)>'
        C:/Ruby23-x64/bin/mailcatcher:22:in `load'
        C:/Ruby23-x64/bin/mailcatcher:22:in `'

Yup. I am having the same issue.

Similar issue here, running mailcatcher using Ruby 2.3.3 (x64) on Windows 10:
    Exception: "\xC3" from ASCII-8BIT to UTF-8
    Backtrace:
       json (2.1.0) lib/json/common.rb:224:in `encode'
       json (2.1.0) lib/json/common.rb:224:in `generate'
       json (2.1.0) lib/json/common.rb:224:in `generate'
       mailcatcher (0.6.5) lib/mail_catcher/web/application.rb:69:in `block (3 levels) in <class:Application>'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block (3 levels) in push'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `each'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block (2 levels) in push'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `each'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block in push'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:256:in `schedule'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `push'
       mailcatcher (0.6.5) lib/mail_catcher/mail.rb:57:in `block in add_message'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:981:in `block in run_deferred_callbacks'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:978:in `times'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:978:in `run_deferred_callbacks'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:193:in `run_machine'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:193:in `run'
       mailcatcher (0.6.5) lib/mail_catcher.rb:173:in `run!'
       mailcatcher (0.6.5) bin/mailcatcher:5:in `<top (required)>'
       C:/Ruby23-x64/bin/mailcatcher:22:in `load'
       C:/Ruby23-x64/bin/mailcatcher:22:in `'

Same here on ruby 2.1.5p273 (2014-11-13) [x86_64-linux-gnu]
Exception: "\xC5" from ASCII-8BIT to UTF-8
    Backtrace:
       /usr/lib/ruby/2.1.0/json/common.rb:223:in `encode'
       /usr/lib/ruby/2.1.0/json/common.rb:223:in `generate'
       /usr/lib/ruby/2.1.0/json/common.rb:223:in `generate'
       mailcatcher (0.6.5) lib/mail_catcher/web/application.rb:69:in `block (3 levels) in <class:Application>'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `call'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block (3 levels) in push'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `each'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block (2 levels) in push'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `each'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `block in push'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:256:in `call'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:256:in `schedule'
       eventmachine (<IP_ADDRESS>) lib/em/channel.rb:43:in `push'
       mailcatcher (0.6.5) lib/mail_catcher/mail.rb:57:in `block in add_message'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:981:in `call'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:981:in `block in run_deferred_callbacks'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:978:in `times'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:978:in `run_deferred_callbacks'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:193:in `run_machine'
       eventmachine (<IP_ADDRESS>) lib/eventmachine.rb:193:in `run'
       mailcatcher (0.6.5) lib/mail_catcher.rb:173:in `run!'
       mailcatcher (0.6.5) bin/mailcatcher:5:in `<top (required)>'
       /usr/local/bin/mailcatcher:23:in `load'
       /usr/local/bin/mailcatcher:23:in `'
    Please submit this as an issue at http://github.com/sj26/mailcatcher/issues```

I think it is bug of mail sender, not mailcatcher.
see https://github.com/sj26/mailcatcher/issues/322

I use UTF-8 in from, like the following code in ActionMailer::Base:
default from: 'leão - my latin america brand<EMAIL_ADDRESS>
I did the following commit only to show a possible fix https://github.com/cerdiogenes/mailcatcher/commit/b2520fff2f2e53079818847877a2227f924a1c19
What do you think about it @sj26? If you think it's acceptable I can prepare a PR.
Best regards!

@znz my email body is encoded with 7bit (I don't do anything special to have it, ActionMailer already send it ok), but the from header field keeps giving error, this is my from header:
From: =?UTF-8?Q?AlfaCon_-_AlfaCon_Concursos_P=C3=BAblicos_<no-reply@alf?=
 =?UTF-8?Q?a-dev.com.br:3000>?=

The body is proper have the proper charset and encoding:
Content-Type: multipart/mixed;
 boundary="--==_mimepart_5b61a61b9d9a5_159c2b07c5d3d950208f3";
 charset=UTF-8
Content-Transfer-Encoding: 7bit

----==_mimepart_5b61a61b9d9a5_159c2b07c5d3d950208f3
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

And in the body I have this string
Obrigado por comprar no AlfaCon Concursos P=C3=BAblicos

If I remove the accent from the from header I get no exception and mailcatcher show the email properly.
So, my question is basically how I can use accents in from field?

I'm not a ruby dev, but I believe this is related. Using mailcatcher in a vagrant box that serves as a magento development server. If email contains some non-ascii characters (german umlauts, euro symbol), it doesn't get sent. Apache error log:
/var/lib/gems/2.5.0/gems/mail-2.7.1/lib/mail/message.rb:2032:in `match': invalid byte sequence in US-ASCII (ArgumentError)
	from /var/lib/gems/2.5.0/gems/mail-2.7.1/lib/mail/message.rb:2032:in `match'
	from /var/lib/gems/2.5.0/gems/mail-2.7.1/lib/mail/message.rb:2032:in `set_envelope_header'
	from /var/lib/gems/2.5.0/gems/mail-2.7.1/lib/mail/message.rb:2132:in `init_with_string'
	from /var/lib/gems/2.5.0/gems/mail-2.7.1/lib/mail/message.rb:137:in `initialize'
	from /var/lib/gems/2.5.0/gems/mail-2.7.1/lib/mail/mail.rb:51:in `new'
	from /var/lib/gems/2.5.0/gems/mail-2.7.1/lib/mail/mail.rb:51:in `new'
	from /var/lib/gems/2.5.0/gems/mailcatcher-0.7.1/bin/catchmail:59:in `<top (required)>'
	from /usr/local/bin/catchmail:23:in `load'
	from /usr/local/bin/catchmail:23:in `

So match function's argument is US-ASCII encoded, which is weird. Ruby / encoding related stuff:
vagrant@syone:~$ ruby -v
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]
vagrant@syone:~$ ruby -e 'p Encoding.default_external'
#<Encoding:UTF-8>
vagrant@syone:~$ locale
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC=C.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="C.UTF-8"
LC_MONETARY=C.UTF-8
LC_MESSAGES="C.UTF-8"
LC_PAPER=C.UTF-8
LC_NAME=C.UTF-8
LC_ADDRESS=C.UTF-8
LC_TELEPHONE=C.UTF-8
LC_MEASUREMENT=C.UTF-8
LC_IDENTIFICATION=C.UTF-8
LC_ALL=

But if I print out Encoding.default_external from catchmail , it really uses US-ASCII. Setting Encoding.default_external = en_US.UTF-8 within catchmail solves the problem, also changing line 59 within catchmail to message = Mail.new($stdin.read.force_encoding('UTF-8')) solves it.
So I ended up changing sendmail_path within php.ini to:
sendmail_path = "LANG=en_US.UTF-8 /usr/bin/env catchmail -f vagrant@syone"
That works, but I still don't understand why catchmail thinks external encoding is US-ASCII.

MailCatcher does not advertise itself as 8-bit capable, and so mail clients should be sending mail in ascii compatible encodings. A feature request for 8 bit transfer encodings is now here, please follow if you're interested: #445


BUG 🐞: Getting window size too small, in fullscreen mode

Describe the bug
When running the binary with my terminal (Alacritty) in fullscreen mode, I'm getting an error stating 'Window too small 43 x 158, Consider going fullscreen for optimal experience'. I have tried restarting multiple times, and tried resizing manually to fit screen (14" Macbook Pro)
To Reproduce

Set Alacritty terminal to fullscreen
Run binary with gomanagedocker

Expected behavior
To not get error, or at least not be blocked completely
Screenshots

Desktop (please complete the following information):

OS: MacOS Sonoma 14.5
gmd Version: V1.3 (latest as of July 18, 2024)

Additional context
I can't escape out of it to get into the main view or anything, I have to just Ctrl-C to exit and can't use :(
I'd love to take on this issue if you don't have the time!

Hey,
This is not a bug it's a feature 🤡.  Initially while developing this I had to set height and width constraints to make sure the TUI doesn't break. For now, the minimum height and width needed are 33 and 169 respectively. Since, your setup doesn't meet those requirements, you will have to decrease the fontsize to meet the requirements.
However, I plan on removing this constraint in the near future (probably next release 😁). In v1.3, I've updated the lists and infobox to update dynamically depending on the width of the window. And next setup would be adjust the height and hide/unhide infobox depending on the window height.
But yeah, unfortunately you will have to decrease your font size a bit (try decreasing just by 1 unit initially). If you prefer, you can do it in a different terminal if you don't want to change your font size of your main terminal.
let me know if you have any other questions. I'm happy to help!

Haha no worries lad, I'll just decrease my font-size and play around with it, I plan on using it for work over the next couple weeks, it's a really great idea, love the project!

Thanks! I'm working on relaxing the window size constraints as we speak. I'm thinking of doing a v1.3.1 patch soon that will handle yours and a couple of other issues.
Let me know how it is working out for you. I'd image there are a few bugs in circulation that need to be ironed out.

Hey @justinbather!
I've pushed a patch that great improves how resizing is handled. You shouldn't have any issues now. Just get the new release using any of the methods.

Ahh good stuff. I’ll pull down latest, thanks!

From: Ajay D. @.>
Sent: Sunday, July 21, 2024 12:31:10 AM
To: ajayd-san/gomanagedocker @.>
Cc: Justin Bather @.>; Mention @.>
Subject: Re: [ajayd-san/gomanagedocker] BUG 🐞: Getting window size too small, in fullscreen mode (Issue #21)
Hey @justinbatherhttps://github.com/justinbather!
I've pushed a patch that great improves how resizing is handled. You shouldn't have any issues now. Just get the new release using any of the methods.

—
Reply to this email directly, view it on GitHubhttps://github.com/ajayd-san/gomanagedocker/issues/21#issuecomment-2241333261, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4JBCZQP44NQX5QUVIUSVSTZNLXL5AVCNFSM6AAAAABLDL774OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGMZTGMRWGE.
You are receiving this because you were mentioned.Message ID: @.***>


Multiple security groups don't work

Following on from #55, we have confirmation that an endpoint being in multiple security groups does not correctly function.

Pre-etcd: closing.


Cannot build xdpinstaller

When building the installer from an administrative "Developer Command Prompt for VS 2019" window, I get the following error:
"N:\repos\xdp-for-windows\src\xdpinstaller\xdpinstaller.sln" (default target) (1) ->
"N:\repos\xdp-for-windows\src\xdpinstaller\xdpinstaller.wixproj" (default target) (2) ->
(Link target) ->
light.exe : error LGHT1105: Validation could not run due to system policy. To eliminate this warning, run the process as admin or suppress ICE validation. [N:\repos\xdp-for-windows\src\xdpinstaller\xdpinstaller.wixproj]
Is this the result of an invalid build environment on my end or is this a known issue (w/ or w/o workaround)?

Does this repro with VS2022? I believe our build environment for XDP itself requires VS2022; we support VS2019 for native driver developers. I've built without admin, but we might have suppressed the ICE validation warning there - I don't recall.

I don't have VS2022 installed so I can't say. Interesting, I can confirm running create-installer as non-admin seems to work on my setup. Although building as non-admin I start running into errors related to signing bpf stuff.
"Visual Studio 2022 is recommended; Visual Studio 2019 or newer is required."
Since I'm not running the recommended VS2022, I'll close out this issue.


Enable to specify how relative paths of the extended file are resolved by extends keyword

Feature Request
Use Case:
First of all, thank you for creating such a great tool!
Recently, process-compose introduced the extends keyword which makes it easier to merge multiple configuration files.
I'm trying to apply this feature to monorepo, which has multiple packages and dependencies.
Assume we have the following monorepo:
.
├── db
│   ├── db-start.sh
│   └── process-compose.yaml
└── server
    ├── process-compose.yaml
    └── server-start.sh

process-compose.yaml in db package:
processes:
  # starts DB process
  db-start:
    command: ./db-start.sh

process-compose.yaml in server package:
extends: ../db/process-compose.yaml

processes:
  # starts server process, which depends on `db-start` process of the `db` package:
  start:
    command: ./server-start.sh
    depends_on:
      db-start:
        condition: process_healthy

Currently, the relative paths in the extended file (process-compose.yaml in db package) are resolved relative to the extending file (process-compose.yaml in server package). So running process-compose up in server directory results in the following error, because we don't have db-start.sh in server directory.
bash: line 1: ./db-start.sh: No such file or directory

It would be helpful if we have a way to specify how relative paths of the extended file are resolved (the file they originated in or the extending file).
Proposed Change:
Maybe something like this?
extends:
  file: ../db/process-compose.yaml
  path_resolution: extended # or extending

Available values are:

extended: The relative paths in extended configuration file are resolved relative to the file they originated
extending: The relative paths in extended configuration file are resolved relative to the file having extends keyword

I think we can come up with more obvious word.
Who Benefits From The Change(s)?
Users using extends keywords, especially working with monorepos.
Alternative Approaches

Syntax like Go Task's includes might be preferable.

I agree with this. Personally, I wouldn't go for making it configurable, but IMO, relative paths should be relative to the file they're defined in. The resolution of a path shouldn't change based on from where it's extended.
If one needs to adjust the path, they can override it in the extending file.

Hi @kota65535,
I think it's a good proposal. I think it will make more sense to keep it simple and to set the working_dir (for each process, but only if empty)  to be the location that contains the extended process-compose.yaml.
What do you think?

Hi @F1bonacc1, thank you for taking a look. Let me sort this out a bit.
Assume we have the following monorepo:
/
├── db
│   ├── db-start.sh
│   └── process-compose.yaml
└── server
    ├── process-compose.yaml
    └── server-start.sh

process-compose.yaml in server package:
extends:
  file: ../db/process-compose.yaml
  working_dir: # empty, relative path or absolute path

... (omitted)

And working_dir and actual working directory look like this, right?

working_dir
example
actual working directory

empty
N/A
/db

relative path
foo/bar
/server/foo/bar

absolute path
/another
/another

I think this is more flexible and intuitive than my first idea!

A few comments:

Adding nested extends.working_dir will break backward compatibility.
Processes also have working_dir today. Figuring out the combination of extends.working_dir and some_process.working_dir will be doable, but not intuitive.

Do you see any major disadvantages in the proposal I outlined above? Here it is again:

If empty - set it to be the location that contains the extended process-compose.yaml
If not empty and absolute dir - no change.
If not empty and relative dir - join extended process-compose.yaml location with the defined working_dir.

Added in v1.46.0
Please let me know if everything is as expected.


Enable flatten and merge functions in Eval.

To enable use on lists for packer modules

Enable flatten and merge functions in Eval;
Remove special handling of packer module labels.

Tested on blueprint from #1510
# expanded.yaml
      - source: modules/packer/custom-image
        ...
        settings:
          ...
          labels: |-
            ((merge(var.labels, {
              ghpc_role = "packer"
            })))
          ...
          windows_startup_ps1: ((flatten([module.windows_startup.windows_startup_ps1])))

# test-winimage/packer/image/defaults.auto.pkrvars.hcl
...
labels = {
  ghpc_blueprint  = "test-winimage"
  ghpc_deployment = "test-winimage"
  ghpc_role       = "packer"
}
...

# test-winimage/packer/image/image_inputs.auto.pkrvars.hcl
...
windows_startup_ps1 = ["#Requires -RunAsAdministrato...tall-Driver\n"]

Though ./ghpc deploy test-winimage failed with unrelated error:
--> test-winimage.googlecompute.toolkit_image: retry count exhausted. Last err: Tunnel start: ERROR: (gcloud.compute.start-iap-tunnel) While checking if a connection can be made: Error while connecting [4003: 'failed to connect to backend']. (Failed to connect to port 5986)

Though ./ghpc deploy test-winimage failed with unrelated error:
--> test-winimage.googlecompute.toolkit_image: retry count exhausted. Last err: Tunnel start: ERROR: (gcloud.compute.start-iap-tunnel) While checking if a connection can be made: Error while connecting [4003: 'failed to connect to backend']. (Failed to connect to port 5986)

This is a red herring. I have my default network manually setup to allow IAP tunneling of WinRM connections. A production blueprint will include this as a new VPC setting. I'll make sure #1510 is modified accordingly, though.


Report for Default Dashboard: Google Analytics - unique web traffic by month

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1768
Originally created by @dmor on 2020-02-20 15:24:35

chart type: line graph
x-axis: time (by month)
y-axis: unique website visitors

View 10 previous comments from the original issue on GitLab


Note in docs to add allauth urls if account email verification is mandatory

To solve this issue: https://github.com/Tivix/django-rest-auth/issues/576

Coverage remained the same at 96.044% when pulling b6c26ce1b080905fe56953741ae14abd05ab084f on brunomichetti:docs/note-if-account-verification-is-mandatory into 624ad01afbc86fa15b4e652406f3bdcd01f36e00 on Tivix:master.

Hi,
as a user of rest-auth, thanks for the contribution!
This repo is not maintained anymore, so the development moved to dj-rest-auth. (reference: https://github.com/Tivix/django-rest-auth/issues/568)
It may be best, if you move this PR there. (and upgrade to using dj_rest_auth)
new repo link: https://github.com/jazzband/dj-rest-auth (I'm not the upkeeper of that repo, it just makes sense for me to help you merge your PR)
Many Thanks,
Barney


CAP Java 2.0

Both services are created with Java version set to Java 17
The manifest.yaml is changed so it is now specifies Java 17, disables Spring Boot Auto Configuration (buildpack is quite loud about it being deprecated) and explicitly sets the cloud profile for Spring Boot.
xs-security.json is updated with "oauth2-configuration". In default data center offered for trial accounts it is mandatory.

Side note: the link we offer as a guide to create SAP HANA is a little newer than we need. I followed it https://developers.sap.com/tutorials/hana-cloud-mission-trial-2.html and got an error at the step where we need to deploy the database there. It seems either we need to do something in addition.
I tried simpler way to create SAP HANA via hana plan, but that causes an issue when the application is deployed. I am looking into it.
Side note #2: The link

Congratulations, you have added the SAP HANA Cloud entitlements and subscribed to the multi-environment tools. You now have the ability to provision your trial instance of SAP HANA Cloud and start your journey.
seems to be broken.

The new guide for HANA Cloud creation is a little more complex, but everything worked in the end.

Side note: the link we offer as a guide to create SAP HANA is a little newer than we need. I followed it https://developers.sap.com/tutorials/hana-cloud-mission-trial-2.html and got an error at the step where we need to deploy the database there. It seems either we need to do something in addition with this new tools plan.
I tried simpler way to create SAP HANA via hana plan. This is working, one must to allow access to all IPs.
Side note #2: The link

Congratulations, you have added the SAP HANA Cloud entitlements and subscribed to the multi-environment tools. You now have the ability to provision your trial instance of SAP HANA Cloud and start your journey.

seems to be broken.

Meanwhile the link seems fixed. It essentially is the same link as in your first sentence.

...

Yes. Maybe it is better to add direct references to our tutorial. The procedure is scattered across three different tutorials and is rather hard to figure out unless you know what to do.

Sure let's try to do it. Do you still have the places and information in mind and can write it up?
Anyway, we can do that in another branch and merge this one to publish it, right?


In display documentation: reference orientation of co-ordinate system to pysical board.

In the documentation for Display::blocking, it would be useful to mention the orientation of the display relative to the rest of the board. In the given example, will the 'point' of the heart be pointing to the usb port, or the edge connector?
(I know its easy enough to try it out, but it would also be nice to get it right first try/and or not have to question whether its your rotation logic code that's backwards or your display code)

That sounds like a great idea and might be a good first contribution. Want to give it a try?

was just waiting to make sure it was wanted!


Add new elmEndpointRequestInfo function

This involved a fairly big change to refactor out the code from endEndpointDefinition that could be used by both functions.
Addesses https://github.com/folq/servant-to-elm/issues/9 (and https://github.com/folq/servant-to-elm/issues/4)

Definitely a big change, let me know what you think!

For clarity, does this address #4 since you can now prepend a new URL base at runtime to the request info record?

It does!

Another question: Is there any reason not to exactly match the record type that Http.request accepts? It seems like that would make this easier to use.

I thought about this some, it's a classic "do what's expected/convenient" vs. "do what's principled" tradeoff.
As you say, the convenient thing to do would be to match Http.request exactly. However, since the tracker and timeout fields will always be Nothing, it's more principled to leave them out, thus making our codomain more tightly fit our range.
(If we leave them in the type signature becomes less useful, because the reader of the function can't tell that tracker will never be Just without examining the function body, etc etc.)
An additional consideration was what purpose this function serves in the library. If it was the primary function we expected people to use we'd want it to be convenient for sure. But it's meant to be the more "advanced" function for special use cases, so convenience is less of a priority than it would be otherwise.
What do you think?

For clarity, does this address #4 since you can now prepend a new URL base at runtime to the request info record?

It does!

Another question: Is there any reason not to exactly match the record type that Http.request accepts? It seems like that would make this easier to use.

I thought about this some, it's a classic "do what's expected/convenient" vs. "do what's principled" tradeoff.
As you say, the convenient thing to do would be to match Http.request exactly. However, since the tracker and timeout fields will always be Nothing, it's more principled to leave them out, thus making our codomain more tightly fit our range.
(If we leave them in the type signature becomes less useful, because the reader of the function can't tell that tracker will never be Just without examining the function body, etc etc.)
An additional consideration was what purpose this function serves in the library. If it was the primary function we expected people to use we'd want it to be convenient for sure. But it's meant to be the more "advanced" function for special use cases, so convenience is less of a priority than it would be otherwise.
What do you think?

That makes sense. Thanks for the answer.
Perhaps the URL can be represented just by url : String to match the Http interface at least, or is there any good reason to split it into a path and query parameters? Using just an url means that the record matches Http's interface apart from excluding tracker and timeout, as far as I can tell.

That makes sense. Thanks for the answer.
Perhaps the URL can be represented just by url : String to match the Http interface at least, or is there any good reason to split it into a path and query parameters? Using just an url means that the record matches Http's interface apart from excluding tracker and timeout, as far as I can tell.

Agreed it's tempting to have url : String, but then we'd no longer get to close https://github.com/folq/servant-to-elm/issues/4 for free. This way the user is just one call to a Url.Builder function away from having exactly the URL they want.
I also think this makes sense from the perspective of thinking of this new function as the low-level one that gives primitive building blocks, as opposed to elmEndpointDefinition with its emphasis on convenience.

Agreed it's tempting to have url : String, but then we'd no longer get to close https://github.com/folq/servant-to-elm/issues/4 for free. This way the user is just one call to a Url.Builder function away from having exactly the URL they want.
I also think this makes sense from the perspective of thinking of this new function as the low-level one that gives primitive building blocks, as opposed to elmEndpointDefinition with its emphasis on convenience.

Alright, I'm convinced!

Alright, I'm convinced!

Thanks!

Thanks!

You're very welcome, thanks for the great library:)

You're very welcome, thanks for the great library:)


dev: add missing CoreDns k8s descriptor files

Fixes: d83bc8d7c9e5 ("contrib/vagrant: deploy CoreDNS in development cluster")
Signed-off-by: André Martins<EMAIL_ADDRESS>Fixes #5802
Doesn't require a CI run as these files are only used in dev environment.
@ianvernon can you try it on your side and merge it if it fixes the issue?

This change is

Looks fine, will double check that it works locally when I get some cycles.

Thank you for providing a fix so quickly!


Import project in Label Studio

I would like to know if it is possible to re-upload a project in Label Studio? I imported a project onto my computer which was then deleted from my Label Studio projects. Is it possible to re-upload it with the downloaded data?

Hello Chaouabti,
Yes, you can import the exported project.  Follow these steps:

Make sure you have the exported JSON file containing tasks and annotations from the deleted project. If you don't have it, you'll need to obtain it from a backup or another source.

Set up Label Studio on your computer, if not already installed.

Create a new project in your Label Studio instance:
3.1. Use the labeling configuration from the deleted project. If you don't have it, you'll need to recreate it manually.

Import the previously exported JSON file into the new project:
4.1. Go to Project => Data manager page, click the Import button, and select the JSON file.

If the deleted project had images, audio, video, or other resources uploaded via the GUI, follow these steps:
5.1. Make sure you have the resources on your computer.
5.2. If necessary, update the paths in the imported JSON file to match the paths on your computer.

By following these steps, you can re-upload a deleted Label Studio project using the downloaded data.


[BEAM-9026] Clean up RuntimeValueProvider.runtime_options

before and after each test.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @chamikaramj

R: @TheNeuralBit


[AutoPR compute/resource-manager] Add missing Gallery Application API in 2019-07-01 version

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6745

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/6461


Test performance information (xus, cost, size)

Hi,
As we're migrating more and more tests to use Plutip we are discovering a lot of performance issues in our Plutus programs. To that point it would be great to have Plutip return performance information for each transaction submitted during a test execution.
Concretely, for each transaction we'd like to have information about all the Plutus scripts (validators, minting policies) that ran, how much execution units (mem, time) and associated ADA cost, overall transaction size with and without datums/redeemers etc.
We could then use this information to manage benchmarking and performance tracking.
However, I'm not yet sure what kind of information is possible to get from the backend tools Plutip relies on

Getting the execution units is possible, but needs a bit of tinkering with bot-plutus-interface.
Script size is also acquireable.
From a UX perspective, I think it would be a good idea, to

create assertions for these (maxExUnits, maxScriptSize, etc.)
add an optional verbose mode, that prints these for all test cases

Part of functionality (execution budgets assertions and their verbose printing) covered in #65


allow WKWebView to work with one password extension in iOS8 (runtime) but targeting iOS7 in App

Hi @exherb,
Thanks for submitting this PR :wink:
I am closing it as a duplicate of #209. I also created issue #212, in which we should address this use case (using WKWebViews with iOS 7.x as the Deployment Target) via the README documentation and the DIY approach.
For more info please read my comment from issue #209 and feel free to join the conversation there.
Cheers!


Problem with local API

Hi,
Currently having major problems with the local API. It doesn't appear to work at all. Had an application that worked last summer that now gives me no data at all (except version number). I don't get any track information, I can't pause or play or do anything at all.
Thought it had something to do with the new horrible windows store version of spotify, so I uninstalled that and force-installed a version of spotify I used last summer. But I still don't get anything.
Is there something I've missed somewhere? Have something changed? Is there any way I can test the local API or see if there's something wrong with the JSON data?

Already fixed. Check out commit 1cae73b

This should then work with the lastest windows store version of spotify?

Yes, after it's released. Or you use the CI artifacts here

Wow!
Thank you.


CMake error when bulid commandcenter

Hey, sorry to bother you.
When I use your commandcenter and build it,  I ran into a problem when I used your commandcenter and built it. I got an error while using cmake.
“-- Including ipv6_config.h from F:/commandcenter/build/cpp-sc2/contrib/ipv6-parse
CMake Error at cpp-sc2/src/CMakeLists.txt:107 (set_target_properties):
set_target_properties Can not find target to add properties to: sc2renderer”
Do you have any idea about this ? Thanks a lot.

by the way, I use windows as the development environment

Hi @Timkeeper2018
Fixed in https://github.com/cpp-sc2/cpp-sc2/commit/a319382048bf29fa31d03f41ff2d51ed0218214e but I forgot to update the API submodule in CommandCenter. :(
Fixed in https://github.com/cpp-sc2/commandcenter/commit/90a1c11678628025fda74b817a0bbe6b580f2f73, please update the submodule and retry.

@Timkeeper2018 have you had a chance to test the build?

Added couple of other fixes and CI. Now CommandCenter can be built under all platforms.
@Timkeeper2018 please let me know if build still doesn't work for you.

yes, it works, sorry, i forget to close it,thanks a lot


Null exception for invariant content

Hi,
i just created a pull request #17 to fix a null exception that can be thrown by the code when working with invariant content where the language is not set on the variants language property, but we need to use the culture set on the node (or that part of the content tree).
I was not sure if I should have started this by creating an issue first. Anyways,I like your module and hope this change will help more people.
David

@dvandevliet v1.3.0 has just been released on NuGet with your first contribution, a big #h5yr!


Update README.md

Change installation description to recommend working with content locally instead of requiring it and remove info about stateless applications.

@palmiak  Here's the PR to update the Statamic README after the release of persistent storage.


Inaccurate initSdk TypeScript signature

Report
Plugin Version
6.0.30
On what Platform are you having the issue?
ios and android
What did you do?
TypeScript types for initSdk are not correct
What did you expect to happen?
When only 1 arg is passed to initSdk, TypeScript should be able to infer that the return type is a Promise.
What happened instead?
TypeScript thinks that the return type is a Response, which could be could be void or a Promise

Please provide any other relevant information.
I opened a PR to fix this issue, but it was closed with no explanation. Can this PR please be reopened or responded to?:
https://github.com/AppsFlyerSDK/appsflyer-react-native-plugin/pull/187
I also had a PR to fix this same issue for the logEvent function, but it was also closed without explanation:
https://github.com/AppsFlyerSDK/appsflyer-react-native-plugin/pull/189

Hey @willcaul !
Your code updates will be included in the next react-native plugin version (6.0.33) with additional api.
Thank you for your understanding.

Hey @willcaul !
Your code updates will be included in the next react-native plugin version (6.0.33) with additional api.
Thank you for your understanding.

Ok thanks Amit!

Hi @willcaul !
A new version has released with your fixes.
Thank you!

Hi @willcaul !
A new version has released with your fixes.
Thank you!

Thanks Amit! 👍


Never sending textDocument/completion

Install plugin
Add .marksman.toml into folder with markdown documents
Start type a wikilink link [[F|]]

Not just no completion with a path appearing, no textDocument/completion request sent to server as well. It got sending textDocument/codeLens and textDocument/codeAction requests after textDocument/didChange.
Is it me or is it expected behaviour?

It sends if I trigger autocompletion manually.

Yeah, after some hustling it fixed for me too.


Custom UI option is not passed to parallel workers

Prerequisites

[x ] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[x ] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[x ] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[x ] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description
When using the --ui option together with --parallel (and j > 1) the ui option is not passed to the workers. This causes errors when running test files that depend on the UI being set up in the worker executing the test.
Steps to Reproduce
Given a test file test-with-ui.js using a custom UI (cakes for gherkin syntax for example)
Feature("Gherkin Syntax", () => {
  Scenario("Writing a simple Scenario", () => {
    Given("the UI is properly registered", () => {
      //noop
    });
    When("the test runs", () => {
      //noop
    });
    Then("some assertion", () => {
      // noop
    });
  });
});

And the custom UI is installed
npm i mocha-cakes-2
When running it in serial mode like this, it works
npx mocha --ui mocha-cakes-2 ./test-with-ui.js

But when running it in parallel like this, it fails
npx mocha --ui mocha-cakes-2 --parallel -j 2 ./test-with-ui.js

Expected behavior:
In the case above the outputs from both test runs should be the same and there should be no error thrown when running in parallel.
Actual behavior:
Serial mode works and outputs:
 Feature: Gherkin Syntax
    Scenario: Writing a simple Scenario
      ✔ Given the UI is properly registered
      ✔ When the test runs
      ✔ Then some assertion

Parallel mode crashes with the error message
1) Uncaught error outside test suite

  0 passing (206ms)
  1 failing

  1) Uncaught error outside test suite:
     Uncaught ReferenceError: Feature is not defined
      at Object.<anonymous> (test-with-ui.js:1:63)
      at Module._compile (internal/modules/cjs/loader.js:689:30)
      at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
      at Module.load (internal/modules/cjs/loader.js:599:32)
      at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
      at Function.Module._load (internal/modules/cjs/loader.js:530:3)
      at Module.require (internal/modules/cjs/loader.js:637:17)
      at require (internal/modules/cjs/helpers.js:22:18)

Reproduces how often:
100%
Versions
mocha --version 9.0.0
node --version v14.15.1
Additional Information
The root cause of the issue is that mocha refers to external UI:s in the options object as function pointers and not the UI identifier string. When the options object is being serialized all functions are (thankfully) ignored. This causes the mocha instance in the workers to default to the bdd UI.
A simple solution would be to map back to the string representation of the setting before passing the options to serialization. I tried this locally and for my case it worked.

A simplistic take is to update buffered-worker-pool.js like this (I don't know the code very well so this might cause more harm than good):
...
const registeredInterfaces = require('../mocha').interfaces;
...
/**
   * Given Mocha options object `opts`, resolves options.ui function references back
   * into static string references that can be serialized.
   *
   * @param {Options} [opts] - Mocha options
   * @private
   * @returns {Options} Options that can be serialized without losing ui reference
   */
  static generateSerializableOptions(opts={}) {
    const interfaceIds = Object.keys(registeredInterfaces);
    const uiRefAsStaticId = interfaceIds.find(id => registeredInterfaces[id] === opts.ui);

    if(uiRefAsStaticId && uiRefAsStaticId !== opts.ui) {
      return {
        ...opts,
        ui: uiRefAsStaticId
      }
    }

    return opts;
  }

  /**
   * Given Mocha options object `opts`, serialize into a format suitable for
   * transmission over IPC.
   *
   * @param {Options} [opts] - Mocha options
   * @private
   * @returns {string} Serialized options
   */
  static serializeOptions(opts = {}) {

    if (!optionsCache.has(opts)) {
      const serializableOpts = BufferedWorkerPool.generateSerializableOptions(opts);
      const serialized = serializeJavascript(serializableOpts, {
        unsafe: true, // this means we don't care about XSS
        ignoreFunction: true // do not serialize functions
      });
...

@love-expressen Thank you.
I haven't tested, yet and I need to do some investigation first.
I think the --ui option is not transmitted via IPC to the worker, but read from the argv array. In worker.js.
I have to do some debugging to understand why it's not working.

This may be caused by async delay features. For some reason my UI does not load when I run a test that throws before the delayed run function. Worse, it hides all stdout.
A weird way around it is to run a single test spec at a time.

I don't know if there are any more complex cases I'm missing, but for my case it's pretty straight forward;

mocha options are parsed and eventually passed to buffered-worker-pool's run method
setting a debugger here reveals that options.ui is a function reference and not a string if a custom ui is used.
later inside the run method the option is serialized and passed to the parallel-buffered-runner
serialization stripps the options.ui property since it's a function.
this obviously means the ui setting is not passed to parallel-buffered-runner or any downstream method (like worker.js)
I've already confirmed that passing a string as option.ui instead of a function reference to the serializeJavascript method solves my issues. See code example above.

@love-expressen I agree with your analysis. ui should be a string mocha-cakes-2, not a reference to mochaCakes function.
But I'm not happy with your solution ...
If I compare eg. the tdd interface, it's a string tdd which gets serialized. Both tdd and mocha-cakes-2 are included in Mocha.interfaces, so why don't they behave the same way? Maybe ui should never be set to a function reference, and if we solve this we have a nicer solution for this issue as well.

In lib/cli/run-helpers.js:

replacing: opts[pluginType] = require(pluginId);
by: map[pluginType] = require(pluginId);

also works, but I still have to check further consequences.

@love-expressen Currently the situation is:

user sets ui to a string mocha-cakes-2
Mocha overwrites ui with a function reference to the interface
your patch sets ui back to the string

There is no need to set ui to a function reference and by changing the two lines in lib/cli/run-helpers.js:

ui remains a string mocha-cakes-2
the mochaCakes function reference is added to Mocha.interfaces.
mocha-cakes-2 already does this on its own, but there may be other third package interfaces not adding it.

When using Mocha via API in parallel mode, this solution (neither your proposition) does not work.
const Mocha = require('mocha');
const mochawesome = require('mochawesome');

Mocha.interfaces['mocha-cakes-2'] = require('mocha-cakes-2');    // has to be set manually

const mocha = new Mocha({
  reporter: mochawesome,
  ui: 'mocha-cakes-2',                 // has to be a string
  parallel: true                       // parallel mode
})

mocha.addFile('./test-with-ui.js');
mocha.run();

Do you agree? Are you opening a PR? Or me?

Thanks for looking into this issue properly <3

But I'm not happy with your solution ...

I agree. Solving this properly at an earlier point if possible would be great.

...but there may be other third package interfaces not adding it.

I'm happy you brought this up. It's been bothering me, and I think we should aim for a solution that doesn't depend on this "hack".
I'm not sure what solution or test you're proposing to start with in a PR, so if you've got the time please open it and point me to where I can help :)


Fix styling issues

With the new onboarding flow changes, the existing UI styles have been affected and need to be updated.

All text is centered
Buttons look too big
Hard to see the separators between threads/messages

This should fix most of those problems:
--- a/chrome/assets/css/bootstrap.css
+++ b/chrome/assets/css/bootstrap.css
@@ -808,7 +808,6 @@ pre code {
 }

 .row {
-  text-align: center;
   margin-right: -15px;
   margin-left: -15px;
 }
@@ -2238,7 +2237,6 @@ textarea.input-lg {
 .btn {
   display: inline-block;
   padding: 6px 12px;
-  margin: auto;
   margin-bottom: 0;
   font-size: 14px;
   font-weight: normal;
@@ -2330,8 +2328,6 @@ fieldset[disabled] .btn-default.active {
 }

 .btn-primary {
-  font-size: 20px;
-  padding-left: 12px 45px 12px 45px;
   color: #ffffff;
   background-color: #428bca;
   border-color: #357ebd;
@@ -7099,4 +7095,4 @@ td.visible-print {
   td.hidden-print {
     display: none !important;
   }
-}

But I'm waiting for #8 to be merged, as there are new style changes incoming.

Hey @kbsriram, according to the UI for attachments, the position/ordering of buttons is slightly changing as well, therefore I scheduled the CSS changes together with the details about attachment icon and input, being both effected by each other. It's in the next CL.

These are fixed:

All text is centered
Buttons look too big

As for the separators between messages/threads, I'll fix them according to https://github.com/e2email-org/e2email/blob/05a24965c7bd97c75d5eada1857f222acf546ff7/screenshots/basic.png.


Add compatibility UUID for Xcode 6.3.2

Add compatibility UUID for Xcode 6.3.2

Already done, thanks very much!


command log: thin out the logs/cmd.log file periodically

When extracting log lines associated with a certain session (var names), the negatives could be overwritten to form the new filtered, cmds.log. However, this destroys the logging handle set up in python.
Find a way to edit cmds.log without destroying the handle, or similar solution that prevents the cmds.log to grow indefinitely.

This is handled by current log extraction, which is executed at request, or at session auto-shutdown.


[analyzer-lsp] Cannot Visit all Packages

Is this on purpose? Or did I misconfigure the LSP server?
Kind regards!

All the missing libraries seem to be Flutter-related.
Could you be using a Dart SDK analyzer, which doesn't have the Flutter SDK packages and libraries available?

Hi Lasse,
thanks a lot for responding so quickly!
I am not sure what you really mean. I have installed Flutter with asdf and it seems to be ok. Installation directory is .asdf/installs/flutter/3.13.5-stable/packages/flutter/ and looks fine. Under the lib directory is e.g foundation.dart to be found:
Screenshot is taken from this command:
ll .asdf/installs/flutter/3.13.5-stable/packages/flutter/lib/;\
ll .asdf/installs/flutter/3.13.5-stable/packages/flutter/lib/src/;\
ll .asdf/installs/flutter/3.13.5-stable/packages/flutter/lib/src/foundation/

When I open a file from a freshly created  Flutter project like lib/main.dart I can goto definition of e.g. MaterialApp - no problemo whatsoever:

But then it stops somehow for some stuff which it cannot find. (All the red wiggly stuff in the screenshot.)

The first screenshot from my initial post is actually from this file (material/app.dart).
This is my configuration for the LSP in neovim:
require("lspconfig").dartls.setup({
            -- cmd = { "dart", "language-server", "--protocol=lsp" },
            cmd = { "/home/schmidh/.asdf/installs/flutter/3.13.5-stable/bin/dart", "language-server", "--protocol=lsp" },
            filetypes = { "dart" },
            init_options = {
                closingLabels = true,
                flutterOutline = true,
                onlyAnalyzeProjectsWithOpenFiles = true,
                outline = true,
                suggestFromUnimportedLibraries = true,
            },
            -- root_dir = root_pattern("pubspec.yaml"),
            settings = {
                dart = {
                    completeFunctionCalls = true,
                    showTodos = true,
                },
            },
            on_attach = on_attach,
        })

cmd entry doesn't make a change if I use dart or /home/schmidh/.asdf/installs/flutter/3.13.5-stable/bin/dart.

My guess: When I goto definition in my flutter source code file, analyzer uses the package information from .dart_tool/package_config.json and jumps to the target without any issues. But being in that target file it has forgotten about all the packages in .dart_tool/package_config.json and can't resolve the import 'package:...; any more.
I think this is definitely a bug.

Workaround: Using --packages option when configuring the language server.
require("lspconfig").dartls.setup({
            cmd = { "dart", "language-server", "--protocol=lsp", string.format('--packages=%s/.dart_tool/package_config.json', vim.fn.getcwd()) },
            filetypes = { "dart" },
            init_options = {
                closingLabels = true,
                flutterOutline = true,
                onlyAnalyzeProjectsWithOpenFiles = true,
                outline = true,
                suggestFromUnimportedLibraries = true,
            },
            -- root_dir = root_pattern("pubspec.yaml"),
            settings = {
                dart = {
                    completeFunctionCalls = true,
                    showTodos = true,
                },
            },
            on_attach = on_attach,
        })

I think this should be done automatically for Dart projects.

@DanTup: any thoughts?

@mkohlhaas does this reproduce starting from a newly-created flutter create project? And does it only occur when using onlyAnalyzeProjectsWithOpenFiles: true?
If you can repro on a fresh project, a log file captured by adding the argument --instrumentation-log-file=/path/to/log.txt to the server may be helpful. Thanks!

 Thank you very much for you support!

@mkohlhaas does this reproduce starting from a newly-created flutter create project?

Yes.

And does it only occur when using onlyAnalyzeProjectsWithOpenFiles: true?

No.

Fresh flutter project:
flutter create fluttertst

LSP start:
cmd = { "dart", "language-server", "--protocol=lsp", "--instrumentation-log-file=/tmp/instrumentation.log" },

What did I do?

open editor (nvim)
open file lib/main.dart
goto definition MaterialApp (line 13 in lib/main.dart)
being in material/app.dart I wait for the red squiggly lines to show up and close editor

Two separate runs.

onlyAnalyzeProjectsWithOpenFiles = true
Log file in instrumentation_01.log
onlyAnalyzeProjectsWithOpenFiles = false in instrumentation_02.log.
Uploaded it to Google Drive because it was too big for Github.

Ok, so I think this is a similar issue to described in https://github.com/dart-lang/sdk/issues/50311#issuecomment-1295800131
What's happening here, is when you navigate to a file in the Flutter SDK, your editor is adding that project to the current workspace:
{
	"params": {
		"event": {
			"removed": [],
			"added": [
				{
					"uri": "file:\/\/\/home\/schmidh\/.asdf\/installs\/flutter\/3.13.5-stable\/packages\/flutter",
					"name": "\/home\/schmidh\/.asdf\/installs\/flutter\/3.13.5-stable\/packages\/flutter"
				}
			]
		}
	},
	"method": "workspace\/didChangeWorkspaceFolders",
	"jsonrpc": "2.0"
}

This creates a new analysis context to try and analyze package:flutter, however because there's no .dart_tool/package_config.json in your Flutter SDK, the URIs cannot be resolved.
There are two possible solutions:

Your editor should not add the Flutter SDK to the workspace when you navigate to it (it's unnecessary and makes the server think it's a project you're working on, rather than just a dependency).
Run flutter update-packages which will fetch dependencies (and create .dart_tool/package_config.json files) for all of the Flutter packages (this is what contributors to Flutter will do so that they can open the project without seeing the same errors you're seeing).

IMO the first option is best - because the behaviour of your editor seems odd to me - jumping to the code file of a dependency should not be a signal that you want to add that project to your workspace and analyze it. I suspect you'll see the same kinds of errors if you jump to something in the Pub cache, because those also don't have .dart_tool/package_config.json files. Whether your editor has the ability to control this, I don't know.
The second option is simple and requires no options in your editor, but it will only solve the problem for the Flutter framework (not Pub packages).


remove st2api dependency on st2actions

all utils that st2api requires are moved to st2common.
moved around some tests.
migrated affected tests to using fixtures.
verified fix by running st2api standalone.

LGTM

We had this issue pop up a couple of times now. We should add some tests for that, otherwise it's just a question of time of when it will repeat again in the future.
We could start with an integration test which verifies that st2api and st2auth only depend on st2common and work stand-alone. Or even just grepping st2api/ and st2auth/ for st2actions., st2reactor., etc. and error out if a match is found would be better than nothing.


[dif/rv_timer] add function to write to counter

This fixes #7921.
Signed-off-by: Timothy Trippel<EMAIL_ADDRESS>

btw, not sure if related to some of the changes you are planning to make, this usually how we advance the timer:
https://cs.opensource.google/opentitan/opentitan/+/master:sw/device/sca/lib/sca.c;l=241


Add a configuration warning to [Oriented]PathFollow

Limitations: Warning about up normals does not update yet when changing up_vectors_enabled in the parent's curve.

You can use update_configuration_warning to update the warning, e.g. similar to:
https://github.com/godotengine/godot/blob/4f5a7ebaecfcf00cf1e5c4af4b20034f0dcecd29/scene/3d/remote_transform.cpp#L124-L131

Thanks, I've added updating when up_vectors_enabled change :).

Could you squash the commits, and add the same warnings to the 2D equivalents of those nodes?

Could you squash the commits, and add the same warnings to the 2D equivalents of those nodes?

Sure, I'll squash them.
The warnings are already there for the 2D equivalent PathFollow2D: https://github.com/godotengine/godot/blob/bde3e884c7b1506dd74cb39ea479ea98dd04e7a1/scene/2d/path_2d.cpp#L264-L274
There is no 2D equivalent for a OrientedPathFollow, so nothing to do there.

Thanks!


Update aws-java-sdk-dynamodb to 1.12.576

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" }
}]

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

Superseded by #510.


openssl 3.2.0-alpha1 breaks on NonStop because of poll()

The introduction of poll() in to the OpenSSL code at 3.2 breaks the builds on NonStop as this method is not available. The call will cause a reintroduction of using the FLOSS layer, which we removed at 3.0. FLOSS is only generally available in 32-bits on NonStop as it is considered pretty much obsolete. This is a bit of a showstopper. There is no way around the situation that I can easily see.
The first compile error is:
c99: running /usr/cmplr/ccomfe -Z8 -ZBL --c99 -ZO2 -Zg3 -ZS/tmp/t2130706481ABIEGA.T -D_XOPEN_SOURCE -ZR8 -m -Zf -ZT -D_TANDEM_SOURCE -ZNW203 -ZNW220 -ZNW272 -ZNW734 -ZNW770 -ZNW1506 -Zz -I. -Iinclude -Iapps/include -I/usr/include -DOPENSSL_PIC -DOPENSSLDIR="/usr/local/ssl" -DENGINESDIR="/usr/local/lib64/engines-3" -DMODULESDIR="/usr/local/lib64/ossl-modules" -DOPENSSL_BUILDING_OPENSSL -DOPENSSL_VPROC= -D_XOPEN_SOURCE -D_XOPEN_SOURCE_EXTENDED=1 -D_TANDEM_SOURCE -DB_ENDIAN -DNDEBUG apps/lib/app_libctx.c
  #    include <poll.h>
                       ^
"/home/jenkinsbuild/.jenkins/workspace/OpenSSL-3.2_Monitor/include/internal/sockets.h", line 120: catastrophic error(4093):
          cannot open source file "poll.h"

The config is:
Command line (with current working directory = .):

    perl ./Configure nonstop-nsx_64

Perl information:

    perl
    5.30.3 for NSV-D-nonstop_kernel

Enabled features:

    apps
    argon2
    aria
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    bulk
    cached-fetch
    camellia
    capieng
    cast
    chacha
    cmac
    cmp
    cms
    comp
    ct
    deprecated
    des
    dgram
    dh
    docs
    dsa
    dso
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    ecx
    egd
    engine
    err
    filenames
    gost
    http
    idea
    legacy
    loadereng
    md4
    mdc2
    module
    multiblock
    nextprotoneg
    ocb
    ocsp
    padlockeng
    pic
    pinshared
    poly1305
    posix-io
    psk
    quic
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    secure-memory
    seed
    shared
    siphash
    siv
    sm2
    sm2-precomp
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    ssl-trace
    static-engine
    stdio
    tests
    tls
    ts
    ui-console
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method

Disabled features:

    acvp-tests          [cascade]        OPENSSL_NO_ACVP_TESTS
    afalgeng            [not-linux]      OPENSSL_NO_AFALGENG
    asan                [default]        OPENSSL_NO_ASAN
    asm                 [no asm_arch]    OPENSSL_NO_ASM
    brotli              [default]        OPENSSL_NO_BROTLI
    brotli-dynamic      [default]        OPENSSL_NO_BROTLI_DYNAMIC
    buildtest-c++       [default]
    winstore            [not-windows]    OPENSSL_NO_WINSTORE
    crypto-mdebug       [default]        OPENSSL_NO_CRYPTO_MDEBUG
    default-thread-pool [cascade]        OPENSSL_NO_DEFAULT_THREAD_POOL
    devcryptoeng        [default]        OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128 [default]        OPENSSL_NO_EC_NISTP_64_GCC_128
    external-tests      [default]        OPENSSL_NO_EXTERNAL_TESTS
    fips                [default]
    fips-securitychecks [cascade]        OPENSSL_NO_FIPS_SECURITYCHECKS
    fuzz-afl            [default]        OPENSSL_NO_FUZZ_AFL
    fuzz-libfuzzer      [default]        OPENSSL_NO_FUZZ_LIBFUZZER
    ktls                [default]        OPENSSL_NO_KTLS
    makedepend          [unavailable]
    md2                 [default]        OPENSSL_NO_MD2 (skip crypto/md2)
    msan                [default]        OPENSSL_NO_MSAN
    rc5                 [default]        OPENSSL_NO_RC5 (skip crypto/rc5)
    sctp                [default]        OPENSSL_NO_SCTP
    tfo                 [default]        OPENSSL_NO_TFO
    thread-pool         [cascade]        OPENSSL_NO_THREAD_POOL
    threads             [config]
    trace               [default]        OPENSSL_NO_TRACE
    ubsan               [default]        OPENSSL_NO_UBSAN
    unit-test           [default]        OPENSSL_NO_UNIT_TEST
    uplink              [no uplink_arch] OPENSSL_NO_UPLINK
    weak-ssl-ciphers    [default]        OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                [default]        OPENSSL_NO_ZLIB
    zlib-dynamic        [default]        OPENSSL_NO_ZLIB_DYNAMIC
    zstd                [default]        OPENSSL_NO_ZSTD
    zstd-dynamic        [default]        OPENSSL_NO_ZSTD_DYNAMIC
    ssl3                [default]        OPENSSL_NO_SSL3
    ssl3-method         [default]        OPENSSL_NO_SSL3_METHOD

Config target attributes:

    AR => "ar",
    ARFLAGS => "qc",
    CC => "c99",
    HASHBANGPERL => "/usr/bin/env perl",
    RANLIB => "ranlib",
    RC => "windres",
    bn_ops => "SIXTY_FOUR_BIT",
    build_file => "Makefile",
    build_scheme => [ "unified", "unix" ],
    cflags => "-g -O2 -Wextensions -Wnowarn=203,220,272,734,770,1506 -Wbuild_neutral_library -Wverbose -Wtarget=tns/x -Wsystype=oss -Wlp64 -WIEEE_float",
    cppflags => "",
    defines => [ "OPENSSL_BUILDING_OPENSSL", "OPENSSL_VPROC=\$(OPENSSL_VPROC)", "_XOPEN_SOURCE", "_XOPEN_SOURCE_EXTENDED=1", "_TANDEM_SOURCE", "B_ENDIAN" ],
    disable => [ "threads" ],
    dso_scheme => "DLFCN",
    enable => [ "egd" ],
    ex_libs => "-lrld",
    includes => [  ],
    lflags => "-Wxld=\"-set systype oss\" -Wxld=\"-set data_model lp64\" -Wxld=\"-set floattype ieee_float\"",
    lib_cflags => "",
    lib_cppflags => "",
    lib_defines => [  ],
    module_cflags => "",
    module_cxxflags => undef,
    module_ldflags => "-Wshared",
    multibin => "64",
    multilib => "64",
    perl => "/usr/bin/perl",
    perl_platform => "Unix",
    shared_argfileflag => "-Wxld_obey=",
    shared_cflag => "",
    shared_defflag => "-Wxld_obey=",
    shared_defines => [  ],
    shared_extension => ".so",
    shared_ldflag => "-Wshared",
    shared_rcflag => "",
    shared_target => "nonstop-shared",
    sys_id => "TANDEM",
    thread_defines => [  ],
    thread_scheme => "(unknown)",
    unistd => "<unistd.h>",

Recorded environment:

    AR =
    ARFLAGS =
    AS =
    ASFLAGS =
    BUILDFILE =
    CC =
    CFLAGS =
    CPP =
    CPPDEFINES =
    CPPFLAGS =
    CPPINCLUDES =
    CROSS_COMPILE =
    CXX =
    CXXFLAGS =
    HASHBANGPERL =
    LD =
    LDFLAGS =
    LDLIBS =
    MT =
    MTFLAGS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    RM =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = ar
    ARFLAGS         = qc
    ASFLAGS         =
    CC              = c99
    CFLAGS          =
    CPPDEFINES      =
    CPPFLAGS        =
    CPPINCLUDES     =
    CXXFLAGS        =
    HASHBANGPERL    = /usr/bin/env perl
    LDFLAGS         =
    LDLIBS          =
    PERL            = perl
    RANLIB          = ranlib
    RC              = windres
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    Makefile

build file:

    Makefile

build file templates:

    Configurations/common0.tmpl
    Configurations/unix-Makefile.tmpl

Thanks for this report.
Currently, poll(3) is only used by our QUIC functionality, therefore you should be able to continue using Nonstop by disabling QUIC at build time.
Unfortunately this file poll.h is still included anyway so a small patch would be needed to avoid including this when it is not needed.
If you see the definition of poll_two_fds in ssl/quic/quic_reactor.c there is a select() based implementation available. This is picked up automatically if POLLIN is not defined so updating the code in internal/sockets.h should be adequate.

Thanks. I should have a PR later today for this fix.

PR #22005 submitted.


popf-release: 0.0.3-1 in 'eloquent/distribution.yaml' [bloom]

Increasing version of package(s) in repository popf-release to 0.0.3-1:

upstream repository: https://github.com/fmrico/popf.git
release repository: https://github.com/fmrico/popf-release.git
distro file: eloquent/distribution.yaml
bloom version: 0.9.0
previous version for package: null

popf

No changes

Hi!!
This package is a requirement for another package(s) that I am preparing from
https://github.com/IntelligentRoboticsLabs/ros2_planning_system
It's my first ROS package. I hope everything would be ok.
Best
Francisco

Hi @mjcarroll
I received an mail from ROS2 Buildfarm reporting a build failed in my package. I did not include some library dependencies.  I have tried to fix it in this way:

I clone the popf-release repo and checkout to debian/eloquent/bionic/popf branch
I added the dependencies in the debian/control file:

Source: ros-eloquent-popf
Section: misc
Priority: optional
Maintainer: Francisco Martin<EMAIL_ADDRESS>Build-Depends: debhelper (>= 9.0.0), bison, flex, coinor-libclp-dev, coinor-libcoinutils-dev, coinor-libcbc-dev, coinor-libcgl-dev, coinor-libclp1, coinor-libcoinutils3v5, coinor-libcbc3, coinor-libcgl1, ros-eloquent-ament-cmake, ros-eloquent-rclcpp, ros-eloquent-ros-workspace
Homepage:
Standards-Version: 3.9.2

Package: ros-eloquent-popf
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, bison, flex, coinor-libclp1, coinor-libcoinutils3v5, coinor-libcbc3, coinor-libcgl1, ros-eloquent-rclcpp, ros-eloquent-ros-workspace
Description: The POPF package

I committed and pushed

I am not sure if this is the way to fix this kind of errors. May you confirm that the process is correct?
Should I wait for another build of the ROS2 build farm?
Sorry for the inconvenience
Francisco

If you want the buildfarm to pick up the changes you need to release a new version. It always builds the tag for the released version. It's possible to patch dependencies in the release repository however it's much better to capture dependencies in your package.xml file in the upstream source so that it will be available on all platforms not just Ubuntu bionic.


Add support for satellite graphs in graph API

Release notes: https://www.arangodb.com/docs/stable/release-notes-new-features37.html#satellitegraphs
Looking at the documentation for the HTTP API, it is not gonna be straightforward to include. They use the existing replicationFactor attribute to identify creation of satellite graphs.

replicationFactor: The replication factor used when initially creating collections for this graph. Can be set to "satellite" to create a SatelliteGraph, which will ignore numberOfShards, minReplicationFactor and writeConcern (Enterprise Edition only).

https://www.arangodb.com/docs/stable/http/gharial-management.html

Took a peek at the java driver implementation. They use a dedicated object to represent the replication factor:
https://github.com/arangodb/arangodb-java-driver/blob/f75985b35693b793dfc3c4fe4663653a34919bba/src/main/java/com/arangodb/entity/ReplicationFactor.java#L26

You might also want to consider the alternative approach adopted in the upcoming reactive Java driver, which has an interface ReplicationFactor and 2 implementations NumericReplicationFactor and SatelliteReplicationFactor.
However this is possible because Java allows covariant return types for overridden methods, but this is only possible from C# 9. Maybe with previous versions you can achieve something similar returning a covariant generic.
https://github.com/arangodb/arangodb-java-driver/blob/next/arangodb-java-driver/src/main/java/com/arangodb/next/api/entity/ReplicationFactor.java
https://github.com/arangodb/arangodb-java-driver/blob/next/arangodb-java-driver/src/main/java/com/arangodb/next/api/entity/SatelliteReplicationFactor.java
https://github.com/arangodb/arangodb-java-driver/blob/next/arangodb-java-driver/src/main/java/com/arangodb/next/api/entity/NumericReplicationFactor.java

Thanks for the tip @rashtao !
Another approach would be to create a separate method, e.g. PostSatelliteGraph. This would be really easy to implement, but it would not have a one to one relationship with a specific route contrary to other methods.

@DiscoPYF , what if we change the type of ReplicationFactor to object and then add some validation in PostGraphAsync()?


Using end_image with Nim-Video/cogvideox-2b-img2vid renders pink noise

Not sure if I can give much more details, but when trying to use Nim-Video/cogvideox-2b-img2vid with end_image. I always generate pink noise. Very strange. Attached is my workflow.
CogVideoX_1_5_I2V_00001.json
https://github.com/user-attachments/assets/739d599b-0921-48e1-a9ac-5de24de63e5e

@kijai any idea why this is happening?

@kijai any idea why this is happening?

The model probably just doesn't support that, even if it didn't generate noise it probably wouldn't work well. The only models trained for interpolation are the specific 5b Interpolation model and the Fun -models.


[serialization] BLS12381AggregateSignature should not have an option

It results in a non standard serialized representation, which is actually returned also to users via APIs.
Alternatives:

use inf as the default/empty signature
do not implement Default and remove Option<sig>. Instead, modify NW's structs to use Option<BLS12381AggregateSignature>.

fixed


Replacement of the Dark mode button

Issue Description:
The current implementation of the dark mode button in our application is not good UI and the first user that comes on the website cannot be able to detect that so the replacement is necessary. This documentation outlines the problem, proposed solution, and any additional considerations related to this issue.
Problem:
The existing dark mode button has been reported to have the following issues:
Not good UI design.
Visual glitches and rendering problems.
User feedback indicating difficulty in toggling dark mode.
Proposed Solution:
To address the issues mentioned above, we propose the replacement of the current dark mode button with a more robust and user-friendly implementation. The new dark mode button should adhere to the following guidelines:
Consistency: Ensure consistent behavior across various devices and browsers.
Visual Appeal: Design a visually appealing dark mode button that integrates seamlessly with the overall user interface.
Accessibility: Ensure that the dark mode toggle is accessible and easy to use for all users, including those with disabilities.
User Feedback: Implement clear feedback mechanisms, such as visual indicators and tooltips, to inform users about the state of dark mode.
Implementation Plan:
Design:
Work with the design team to create a visually appealing dark mode button that aligns with the application's design language.
Consider user feedback on the existing button and incorporate improvements in the new design.
Development:
Replace the current dark mode button with the newly designed one.
Uploading

SO PLEASE ASSIGN ME THIS ISSUE UNDER JWOC 24

Please Assign me this issue under JWOC 24

Hey @prakharsingh-74, good idea. However, we already have an issue on the same topic. So, we're closing this one.


Incorrect positions with placement auto

Reproduction demo
https://codesandbox.io/s/react-popper-v2x-issue-template-vb3kt?file=/src/index.js
Steps to reproduce the problem

ensure the codesandbox has enough room along both axis' so that auto move it to the side as well as bottom/top
notice an axis while scrolling change calculates the wrong offsets (further scrolling fixes it)

The issue is that the new arrow position makes the popper longer/shorter/wider/etc
What went wrong?
This behavior makes sense to me abstractly, position changes require the popper to render with the new position in order to be the correct size. What i don't understand is why i don't usually see this with the non react version, and is there a general why to handle this? In React-overlays we have an effect that checks if the placement changed in state, and triggers a forceUpdate but this leads to situations where it loops indefinitely in narrow cases where the new placement also causes a placement change.
Any other comments?
It seems like modifiers do something to avoid these loops, but i'm not sure if the same thing is possible to do outside of them in react-land. Also how Tippy seem to avoid this?

Realizing the reason this works, is that most examples use offsets instead of padding to make room for the arrow yeah?

The issue is that the new arrow position makes the popper longer/shorter/wider/etc

You can't use margin to offset the popper because it changes its size which causes problems like the flip loop. You can only use the offset modifier.
It also happens in the core version, see https://popper.js.org/docs/v2/migration-guide/#5-ensure-your-popper-and-arrow-box-size-is-constant-for-all-placements

I know that margin doesn't work, the example here doesn't use margin. The unclear part here is you also can't use padding for accomplish this, which isn't really covered anywhere (it'd be hard to warn about for obvious reasons i know).
Doing markup like the code sandbox is very common, and not obviously an example of using margin to offset the popper, tho that is what is happening in practice.

the example here doesn't use margin

It does? Not on the popper itself but an inner element that mimics padding. That's the same thing as far as Popper is concerned with this issue (changing its dimensions based on the placement).

Overall it seems like the real restriction is that the popper element should not change dimensions because of a placement?

Correct, you can't conditionally change the popper's size based on the placement, it's a limitation

It does? Not on the popper itself but an inner element that mimics padding.

Right, that was my (pedantic) point the popper element does not use margin, I see now that it's effectively the same thing using padding on the inside. I'm not trying to be difficult, i'm sharing how my brain thought about this. reading https://popper.js.org/docs/v2/migration-guide/#4-remove-all-css-marginsm and seeing the console warnings and it wasn't obvious to me that "padding on an inner element" was actually the same thing until I wrote out the issue and something clicked in my head. In retrospective duh.
So I guess i'm just suggesting that the docs/warning aren't as being as clear as they could be about what the happy path is for styling.


Emacs OS X GUI doesn't work

I guess it's because we build with --disable-ns-self-contained. The GUI is actually unusable for me. It opens behind the terminal, without starting an actual OS X application in the Dock. All keyboard commands are sent to the terminal.

Attempt to fix at https://github.com/conda-forge/emacs-feedstock/pull/3

So I saw a message about pulling broken OS X builds, but was on my phone. Does that need to happen? I can put them under a different channel label (e.g. broken) so you can still get to them if you need, but they won't get installed by default.

There's no need to move stuff for now. I've got a "working" build (still some issues, but I'm trying to fix them now).

I merged https://github.com/conda-forge/emacs-feedstock/pull/3, but now I'm getting this error (and the package is broken)
Warning: arch-dependent data dir '/Users/travis/miniconda3/conda-bld/recipe_1481871472196/work/emacs-25.1/nextstep/Emacs.app/Contents/MacOS/libexec/': No such file or directory
Warning: arch-independent data dir '/Users/travis/miniconda3/conda-bld/recipe_1481871472196/work/emacs-25.1/nextstep/Emacs.app/Contents/Resources/etc/': No such file or directory
Warning: Lisp directory '/Users/travis/miniconda3/conda-bld/recipe_1481871472196/work/emacs-25.1/nextstep/Emacs.app/Contents/Resources/lisp': No such file or directory
Error: charsets directory not found:
/Users/travis/miniconda3/conda-bld/recipe_1481871472196/work/emacs-25.1/nextstep/Emacs.app/Contents/Resources/etc/charsets
Emacs will not function correctly without the character map files.
Please check your installation!

(in case anyone is seeing this and needs to fix emacs, downgrade to build 4, conda install emacs=25.1=4)

So it's referencing stuff from the work directory. I checked and the path is hardcoded in the binary executable. If we can't figure out how to make it not do this in the build, the only thing I can think of is to rig the work directory to be as long as the long placeholder prefix, and replace it with the real placeholder prefix. That doesn't sound fun, though (unless conda-build lets you set the work directory somehow, we'd have to manually (re)install miniconda to some long prefix path).
Also, does conda build not delete the work directory during the tests? That would have caught the issue right away. CC @msarahan

The broken package has been removed from conda-forge. It's still at https://anaconda.org/asmeurer/emacs/files (emacs=25.1=5, broken channel) in case anyone wants to have a look.

Oh, conda-build does have a croot flag, along with --no-build-id. It's not really clear from the docs what the build id is when that flag is used, but I believe this should be sufficient to set a long work directory.
Now my question is, is there a "correct" way to make permanent modifications to the build scripts in a feedstock? If I just modify .travis.yml that will get reset on each rerender.

Oh, --no-build-id means it just skips the recipe_... subdirectory entirely.

OK, here's attempt 2 (work in progress): https://github.com/conda-forge/emacs-feedstock/pull/10. I just went ahead and edited the .travis.yml with large warning signs.
One big problem, if someone rerenders without leaving those changes in the build will NOT fail, because the tests don't pass (because the work directory isn't being deleted). So I should probably work on making the tests fail so that it doesn't accidentally get broken.

I am seeing an error for 25.2-1. Similar to above, but added for transparency:
Warning: arch-dependent data dir '/Users/travis/miniconda3/conda-bld/emacs_1504153408821/work/emacs-25.2/nextstep/Emacs.app/Contents/MacOS/libexec/': No such file or directory
Warning: arch-independent data dir '/Users/travis/miniconda3/conda-bld/emacs_1504153408821/work/emacs-25.2/nextstep/Emacs.app/Contents/Resources/etc/': No such file or directory
Warning: Lisp directory '/Users/travis/miniconda3/conda-bld/emacs_1504153408821/work/emacs-25.2/nextstep/Emacs.app/Contents/Resources/lisp': No such file or directory
Error: charsets directory not found:
/Users/travis/miniconda3/conda-bld/emacs_1504153408821/work/emacs-25.2/nextstep/Emacs.app/Contents/Resources/etc/charsets
Emacs will not function correctly without the character map files.
Please check your installation!

I was able to downgrade to 25.1-4 which opens but then the gui does not respond and keyboard tries to input on the bash terminal. I am running Sierra version 10.12.6.


Video Conferencing Tooling

What video conferencing tools are users comfortable with, for open-source related projects.
Would users prefer to use OSS/FOSS tools, and have a strong preference to lean towards either one.
Which tools would you suggest?
Also what are peoples preferences for video communication

webinar style
group style

For personal meetings, I've always just grabbed a google meet, but I can imagine there will be restrictions for larger groups, and there may be concerns on AI, collecting data.
There are other options available to maintainers, through their employers, Zoom for example.
Both google meet/zoom are not OSS, and therefore may not be suitable for some members who simply won't use those platforms.
Just want to gauge interest. Do people care? I've often had to sign up to new platforms to watch a single event and then never used it again.

We used SmartBears zoom, and managed to link this up with YouTube for live-streaming.
All worked pretty well, and was easy enough to setup.
We will provide some instructions for others, in case they wanted to do it themselves for their own projects etc.
Will close this now but feel free to still chime in if you have thoughts about video conf tooling 👍🏾


Add Highlight In SQL

Description
Support highlighting function in SQL query engine.
Issues Resolved
Github Issue: 636
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented.

[x] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I'm wondering are we sending another PR for user manual separately?

I added highlight to functions.rst under commit: 232b19f5924d2c46fd08b9d60abadb0d207ad016

Under commit 9fbea3072bbf6cd3f89851a20344eecf720ac219 I have changed the output format to be more useable to the end user. See revisions to functions.rst for new output format. I have also changed highlight all, and wildcard to unsupported for this version as we want to iterate on the output format for multiple returned highlight fields.

@dai-chen could you review this please


Add CLI version switching

Closes #538
Description
Adds ability to select versions of the CLI with native support for flow-c1

For contributor use:

[x] Targeted PR against master branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

tests pass locally - there are seemingly issues with @vscode/test-electron that break these, will be addressed subsequently (probably need to update)

How does the correct language server get chosen based on the version of flow-cli used?

How does the correct language server get chosen based on the version of flow-cli used?

The LanguageServerAPI watches for the binary to change from the CliProvider and will restart accordingly.  I realized it maybe wasn't super clear, so I've moved some stuff around and added some more comments to make it more obvious that this is how it works.


Car rides get real messed up

The plugin doesn't handle car rides correctly. If you have a ride of many trains of one sports car each, each train is actually three cars; the first and last are invisible. The plugin currently adjusts all 3 cars which winds up being a glitchy mess. The plugin should only touch the second car and leave the others alone

Fixed in version 2.


[Event Request] codeunit 6620 "Copy Document Mgt."- OnBeforeCopyThisLine

Hi, would it be possible to get an event OnBeforeCopyThisLine codeunit 6620 "Copy Document Mgt.", like this :
    procedure CopySalesDocLine(var ToSalesHeader: Record "Sales Header"; var ToSalesLine: Record "Sales Line"; var FromSalesHeader: Record "Sales Header"; var FromSalesLine: Record "Sales Line"; var NextLineNo: Integer; var LinesNotCopied: Integer; RecalculateAmount: Boolean; FromSalesDocType: Enum "Sales Document Type From"; var CopyPostedDeferral: Boolean; DocLineNo: Integer): Boolean
    var
        RoundingLineInserted: Boolean;
        CopyThisLine: Boolean;
        CheckVATBusGroup: Boolean;
        InvDiscountAmount: Decimal;
        IsHandled: Boolean;
        Result: Boolean;
        SalesDocType: enum "Sales Document Type";
        QtyToQtyFree: Boolean;

        OnCopySalesDocLineOnBeforeCopyThisLine(ToSalesHeader, ToSalesLine, FromSalesLine);
        IsHandled:=false;
        OnBeforeCopyThisLine(IsHandled,CopyThisLine,ToSalesHeader,Result,QtyToQtyFree,RecalculateLines,SalesDocType,LinesNotCopied);
        if IsHandled then
            exit(Result);
        if CopyThisLine then begin

    [IntegrationEvent(false, false)]
    local procedure OnBeforeCopyThisLine(var IsHandled: Boolean;var CopyThisLine: Boolean;var ToSalesHeader: record "Sales Header";var Result: Boolean;var QtyToQtyFree: Boolean;var RecalculateLines: Boolean;var SalesDocType: Enum "Sales Document Type";var LinesNotCopied: Integer)
    begin
    end;

Thanks!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


ensure the container see the mount point of the rootfs

Signed-off-by: Lai Jiangshan<EMAIL_ADDRESS>

LGTM


Update data test descriptions

What are you changing in this pull request and why?
Generic Test descriptions can now be documented
Closes https://github.com/dbt-labs/docs.getdbt.com/issues/6293
Checklist

[ ] I have reviewed the Content style guide so my content adheres to these guidelines.
[ ] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
[ ] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

🚀 Deployment available! Here are the direct links to the updated files:

https://docs-getdbt-com-git-test-description-dbt-labs.vercel.app/reference/resource-properties/description

hey @matthewshaver , do you think we should modify one of the examples under the 'examples' header to include tests?
e.g.
- name: color
  tests:
    - accepted_values:
        values: ['blue', 'green', 'red']
        description: "{{ doc('color_accepted_values') }}"

also it maybe out of scope but would it be a good idea to link to the description property page here?

Good questions @mirnawong1 - I only updated to stress all data tests in the description. There was an earlier PR from some others that didn't do it then. Maybe because it would be a lot of version blocking

My vote is to add some examples, even if they're not truly inside of version blocks and just have a comment beside them or something. I was just sharing info on how this worked, and wound up having to backsolve it myself instead of using the docs.
A couple of examples are here if you want to leverage them: https://discourse.getdbt.com/t/is-it-possible-to-add-a-description-to-singular-tests/5472/4


Aftr execution task "Clone an Element Using jQuer" there is an extra button

steps:

perform a task
click on the button "run tests"

actual result: there are 3 buttons "target5"
Expected Result: there are 2 buttons "target5"

Looks like a duplicate of #5072.


Version 5.6.0-beta.2 - Gmail and WhatsApp not working

I thought I'd give the beta a try to see if it fixes the hibernation issues I've been having.
Unfortunately, Gmail and WhatsApp both complain about the browser.

Deleted everything and started from scratch and it seems okay now, so I will close this.

Same issue here.
@patrickrushton when you say you deleted everything you mean you reinstalled Ferdi?


Auto Focus Not Working Ng2 Semantic ui Modal

AutoFocus is Not Working in Ng2 Semantic ui Modal.
<ng-template let-context let-modal="modal" #modalTemplate>
Example

<button class="ui red button" (click)="modal.deny('denied')">Cancel
<button class="ui green button" (click)="modal.approve('approved')">OK

Hi there, in order to help you I need to see a reproduction scenario in plunkr, as the issue template suggests. Please make one and comment it here and I can try to help out.

I want to Display a form in Modal but when Opening the Modal the Focus is not Automatically Set to the First Text Box Even When I gave autofocus also.Please let me Know How to Set the Focus in TextBox when Opening Modal itself.

How are you opening the modal, is it using a template, component, or just automatically?

By Using Template.

So I've had a think and the only way to do this outside of the library is going to be less than ideal, so I'm going to add a feature in the 0.9.0 release that focusses any element inside the template that has the autofocus attribute automatically on open :)

can I know when the 0.9.0 version will release.

Very soon

This is now live in 0.9.0 :smile:

Thank You,The Autofocus was working fine in Chrome and Firefox But it was not working in Internet Explorer.

Sorry, to clarify do you mean it wasn't working and now it is, or that it currently isn't working?

Currently it was not working in IE .

Ok I've tested it in IE11 and can see it isn't working - apologies, I was getting confused by the 2 different tenses. I'm not quite sure why, but I'll open a new bug to track it.


[Port dspace-7_x] Fixing Crossref document type issue with new metadata mapping processor

References

Fixes #9900
Main version: #9910

Description
This PR makes use of a mechanism available for external sources that enable you to do value mapping. Meaning, you can replace a value by defining something like:
journal-article=Article

Instructions for Reviewers
To test this, you can see it on the original issue #9900, you can use the user interface and you just need to go to your "mydspace" area and do an import metadata from crossref. Then, when you try to import a record, You will see "Article" instead the "journal-article" as the Publication type.
List of changes in this PR:

I've changed crossref integration spring configuration to support to new SimpleMapConverter
I've added a file with mapped values (I've tried to do my best here)
I've created a new JSON processor

Thanks @paulo-graca! I tried this on DSpace 7.6.3 and it worked as expected. I imported a journal article and a book chapter using custom type mappings for our repository (we use Journal Article and Book Chapter).