dark mode support?

do we have a plan to choose a different theme for dark mode?

Not at the moment but I'll look into it later when I have a chance. I'm open to ideas.

    hljs: {
      theme: 'night-owl', // light
      darkTheme: 'another-theme', // dark
    }

then generate another set of styles for dark mode
.dark\:{
    &hljs {
        &...styles
    }
}

this is basically the config of daisyui. What do you think?

@arily the only issue with that is how highlight.js works in general. I'd like to avoid needing to reinstantiate hljs when toggling dark mode. I have some other ideas that I'll hack on this weekend if I can find time.

Any updates on this? I'm also looking to use a different theme for dark/light mode.

Any updates on this? I'm also looking to use a different theme for dark/light mode.

I'll look into this more tomorrow. I've been meaning to do some cleanup anyway.

same lol


Instagram block

As a user, I want to see the Instagram posts on the main page to discover relevant information about the project quickly
Acceptance Criteria

Title ‘Ми в Інсті’ is present

Posts from Instagram are displayed under the Title ‘Ми в Інсті‘
The ‘Зацінити інстаграм‘ button is present on desktop version
The ‘Перейти в інстаграм‘ button is present on tablet and mobile version
All elements present according the mock-up
desktop
tablet
mobile

Cards of the posts are looped.

The arrows (right, left) are displayed on desktop version (On the tablet and mobile device, swipe to navigate)

By clicking on the arrows that are on the right and left side, you can scroll through posts from Instagram

The bottom pagination under the posts is displayed - only on tablet and mobile version

The quantity of squares matches the amount of posts

By scrolling right - left, the posts will change and also the bottom pagination under the posts also changes

Сlicking on the post window, will redirect the user to a separate Instagram page with this post
Сlicking on the ‘Зацінити інстаграм‘ will redirect the user to the main Instagram page of the site – desktop
Сlicking on the button ‘Перейти в інстаграм‘ will redirect the user to the main Instagram page of the site – tablet, mobile

Epic link #694

Added info about swiping for item 4: "On the tablet and mobile device, swipe to navigate."


[Bludit 2 Beta 3] Fixed pages do not work

Fixed pages do not work. The URL is shown in the browser, but it shows "Page not found".

I fix some bugs, could you try the new beta, https://github.com/dignajar/bludit/releases/tag/2.0-beta4

Hello Developers,
I have just uploaded the beta 4 and have errors in the fixed pages in the sidebar.
The errors look like this. How can I fix it?
Fatal error: Uncaught Error: Call to undefined method dbPages::getFixedDB() in /xxxxxxxxxx/bludit.wpzweinull.ch/bl-plugins/fixed-pages/plugin.php:45 Stack trace: #0 /xxxxx/bludit.wpzweinull.ch/bl-kernel/helpers/theme.class.php(150): pluginFixedPages->siteSidebar() #1 /xxxxx/bludit.wpzweinull.ch/bl-themes/editorial/php/sidebar.php(1): Theme::plugins('siteSidebar') #2 /xxxxxxxx/bludit.wpzweinull.ch/bl-themes/editorial/index.php(59): include('/xxxxxxx...') #3 /xxxxxxx/bludit.wpzweinull.ch/bl-kernel/boot/site.php(25): include('/xxxxxxxx...') #4 /xxxxxx/bludit.wpzweinull.ch/index.php(39): require('/www/htdocs/w01...') #5 {main} thrown in /xxxxxxx/bludit.wpzweinull.ch/bl-plugins/fixed-pages/plugin.php on line 45
Thanks in advance.

The issue is the plugin fixed-pages was renamed to static-pages, delete the old plugin from bl-plugins/fixed-pages folder.

Thanks for the hint, it had helped me very much and now everything again well.

I close the ticket. Please take a look at the new beta version to check possibles fixes for the issue, https://github.com/dignajar/bludit/releases/tag/2.0-beta7
Feel free to open a new ticket if the problem persists with the latest version.


I find the value of "unique visitors" is not right!

env：
GoAccess - 1.2
ubuntu 14.04
my goaccess command:
goaccess -f /srv/logs/access.log -o report.html

The result of "unique visitors" is : '10704"
But if I use shell command:
cat /srv/logs/access.log |awk '{print $1}'|sort|uniq -c|wc -l

The result is : "5025"

Please note that HTTP requests containing the same IP, the same date, and the same user agent are considered a unique visitor. In your case, I'm assuming you are only taking unique IPs.
The unique IPs count should be displayed right above the data column in the Visitors Panel.

Thank you for you reply!
In my opinion the "HTTP requests containing the same IP, the same date, and the same user agent are considered a unique visitor" should be less than unique IPs. Because it have too many restrictions.
I think one IP requested two or more API should be one unique visitor,is it right?

Not really. Think about a house where all of them go out with the same public IP, but each house member has a different device, e.g., D1 => Chrome, D2 => iPad, D3 => Android Firefox. All of them using the same IP but different agent. Thus IP, Date and Agent = unique visitor.

Thank you very much for you reply again!
What you explain is very well!It is real fact!


Onboarding

make it progressive: Goal-Gradient Effect

progressive onboarding:

privacy notice
sex chromosome selection
birth input
location input
WHY
pheno age
upload proof
upload photo

Some ideas for the join competition workflow:
peak emotional moment: send results button push (or click join?) - go beyond presenting a simple confirmation model: mailchimp "using a touch of brand character through illustration, subtle animation and humor. freddy the company's emblematic chimp mascot howers his finger over a large red button as if to imply he's eagerly awaiting your permission (maybe some play with the phoenix. as they're going through the process of registering the phoenix is burning to ashes. then at submit the phoenix has reborn) - the longer you wait the more nervous freddy seems to get. when finished easter egg freddy high 5 vs phoenix has reborn better and newer. red. this screen should provide details pertaining to the competition standing.
maybe phoenix fighting with a dragon? anyway, creativity can wait until we get here

pay attention to the start, end and peak-end for onboarding experience

Disclaimer
Should go something like this.
Privacy is your ability to selectively reveal yourself to the world. Be mindful if the information we're asking you really want to share.
Imagine you're Cristiano Ronaldo. Your responsibilities aren't exhausted by honing your skills, but they also include displaying them.
There's no sport without spectators.

Idea: how about onboarding with minimal information and additional info is like "registration into various leagues"?
So if someone provides their name, their date of birth, their pic, their pheno age and their proofs then the registration is done and after that asking for sex, height whatnot?


@owendodd => fix headers

and will switch appropriately

Rad! hitting that button was very empowering haha. :muscle:


Epic: Limits per branch

Motivation
As a user, I want to disable history for some branches
As a user, I want to set up a size limits for the history per branch
DoD
Implementation ideas
Tasks

[ ]

Other related tasks and Epics

Disable history

I don't think it's feasible to try not to have any history. Perhaps this as a user story would be As a user I want branch $X to cost me zero for the history...?
Was thinking that we already have gc_horizon and pitr_interval but we don't even have a concept of per-timeline configuration settings so now I understand this issue.

You're right. If we need to keep a small bunch of history for our internal, we will keep it. From customers' perspective, it should look like, they don't care about it and don't overpay for that stuff.

this will be closed in favor of roadmap item that we have nearly shipped: https://github.com/neondatabase/neon_roadmap/issues/41
(storage part is done already, the UI part is awaiting release ATM of writing)


Feature/add postgres container

Пока добавил один сервис metalamp-db-test

Можно смотреть @Znack
docker-compose up
haskell-starter-kit_db_1 is up-to-date
Creating haskell-starter-kit_backend_1 ... done
Attaching to haskell-starter-kit_db_1, haskell-starter-kit_backend_1
db_1       |
db_1       | PostgreSQL Database directory appears to contain a database; Skipping initialization
db_1       |
db_1       | 2021-03-08 03:47:03.393 UTC [1] LOG:  starting PostgreSQL 13.2 (Debian 13.2-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
db_1       | 2021-03-08 03:47:03.394 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
db_1       | 2021-03-08 03:47:03.394 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1       | 2021-03-08 03:47:03.405 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1       | 2021-03-08 03:47:03.423 UTC [25] LOG:  database system was shut down at 2021-03-08 03:39:20 UTC
db_1       | 2021-03-08 03:47:03.435 UTC [1] LOG:  database system is ready to accept connections
backend_1  | {"appInstanceName":"AppName","severity":"Info","message":"Starting application...","timestamp":"2021-03-08T03:47:08.487831433Z","trace":"[Lib.runLogExample#52] "}
backend_1  | {"appInstanceName":"AppName","severity":"Debug","message":"Here is how we work!","timestamp":"2021-03-08T03:47:08.488135667Z","trace":"[Lib.runLogExample#53] "}
backend_1  | [Debug#SQL] INSERT INTO "user"("created_at","phone") VALUES(?,?) RETURNING "id"; [PersistUTCTime 2021-03-08 03:47:08.547556948 UTC,PersistText "+79990424242"]
backend_1  | [Debug#SQL] SELECT "user"."id", "user"."created_at", "user"."phone"
backend_1  | FROM "user"
backend_1  | WHERE "user"."id" = ?
backend_1  | ; [PersistInt64 2]
backend_1  | Just (Entity {entityKey = UserKey {unUserKey = SqlBackendKey {unSqlBackendKey = 2}}, entityVal = User {userCreatedAt = 2021-03-08 03:47:08.547557 UTC, userPhone = "+79990424242"}})
backend_1  | {"appInstanceName":"AppName","severity":"Info","message":"Finishing application...","timestamp":"2021-03-08T03:47:08.618520904Z","trace":"[Lib.logInfo#24] "}
haskell-starter-kit_backend_1 exited with code 0


Updated Dependencies

My team was eager to use this very convenient package. Unfortunately, however, we faced some dependency conflicts when trying to do so. Instead of relying on our own fork, we thought an official PR would be more beneficial for everyone :D
Cheers!

Hello @QamilDragusha, thank you so much for your contribution to the project. Today I will upload a new version.


fix: flaky test failing on CI

Pull Request Test Coverage Report for Build 359336180

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 58.222%

Files with Coverage Reduction
New Missed Lines
%

pkg/metrics/sampler/sampler_routine.go
2
94.74%

pkg/integrations/v4/logs/cfg_watcher.go
4
67.5%

Totals

Change from base Build 357451715:
-0.01%

Covered Lines:
11234

Relevant Lines:
19295

💛  - Coveralls


Ability to add custom loss in OutputLayer

For class imbalance it is sometimes necessary to pass a custom loss function or a weighted loss. Especially for detection and segmentation, imbalance cannot be handled via sampling strategies.

Hi Julian,
While there is no pre-defined weighted loss, we do support FCMP type of loss, which is a user-defined loss function. You can write your own loss function with parameter fcmpAct and fcmpErr.

Hi Julian,
Please let me know if it solves the problem and we can go ahead closing this issue.
Thanks,
Maggie

@JulianMar11  - there is an example in the SAS documentation that shows how to define and use both a custom activation and a custom loss function.  Please see this page.

@JulianMar11 - did the documentation page help with your question?

No further feedback from @JulianMar11 - closing.


Existing vSphere node template can't be used after upgrading to 2.3.3

rancher/rancher:v2.3-head 75c231e51
UI: latest-2.3

Deploy Rancher v2.3.2
Create a vSphere node template using RancherOS
Create a cluster from the node template
Upgrade Rancher to v2.3-head
Create a new cluster from the existing vSphere node template

Cluster provisioning fails with an error: 	Error setting machine configuration from flags provided: Creation type manual not supported; Timeout waiting for ssh key

After upgrading, creationType is set to manual which was not present in 2.3.2.
2019/11/05 23:12:26 [INFO] successfully migrated node template [vsphere-232]
Editing to legacy allows the cluster to be provisioned.

https://github.com/rancher/machine/pull/47

rancher/rancher:v2.3-head
UI: latest-2.3

Create vSphere node template in 2.3.2
Create cluster from node template
Upgrade to v2.3-head
Create cluster from existing node template
vSphere node template contains creationType=legacy

Cluster creation succeeds.
#23920 Still occurs


feat(Tabs): Ideation for future development

THIS PR SHOULD NOT BE MERGED!
It strictly exists to provide context around some potentially advanced features for the new tabs component introduced in https://github.com/Codecademy/client-modules/pull/1867

🚀 Styleguide deploy preview ready!https://60d610ca8653ab814b0e3b13--gamut-preview.netlify.appDeploy Logs


receive from channel with timeout

how to do that?
in go i can
select {
case <-ch:
    // a read from ch has occurred
case <-timeout:
    // the read from ch has timed out
}

I think we'll eventually have a select expression: #688
Right now you need to do it in an ugly way: https://github.com/crystal-lang/crystal/blob/master/samples/channel_select.cr
Of course for timeout you need to spawn, sleep and then send through a channel. @waj wants things other than channels to be able to be used in select, so maybe there will be a simpler way to do this in the future.

Check https://github.com/crystal-lang/crystal/blob/master/samples/channel_select.cr
Eventually I think we'll have a select expression: https://github.com/crystal-lang/crystal/issues/688
For timeout you need to spawn, sleep and then send through a channel, although @waj wanted this to be simpler, maybe things other than channels could be used in select, but I don't know.

what about this?
ch = Channel(Nil).new
spawn do
  sleep 10.seconds
  ch.send(Channel::Timeout)
end

begin
  x = ch.receive
rescue Channel::Timeout
end

Exceptions are slow, they shouldn't be used for control flow.

Timeouts could be implemented in the receive_impl method of channels. The problem is how to report it to the blocked fiber. Maybe by returning an IO::Timeout? But then any ch.receive would have to be aware that it may receive en IO::Timeout...

add new method receive_timeout(10.seconds)

It'll be something like this:
select
when value = ch.receive
  puts value
when sleep(10.seconds)
  puts "Timeout!"
end

The idea is that this gets rewritten, so a call like ch.receive would be ch.receive_op, and sleep would be sleep_op, or something like that, so select is somehow extensible. But these are just ideas in the air, we didn't think it thoroughly.

but what if someone send to channel later, what happen in this case? block forever?

@kostya I don't know because I don't have much experience with channels and timeouts, but I guess on a timeout you'd close the channel so nothing else can be sent on it... maybe it depends on the specific scenario? Or else, we'd have to think how this is done in Go.

This is a receive timeout, so it should merely mean: it expected to receive a message within X seconds but it didn't receive one. I think it's up to the developer to decide to close the channel or not, depending on its usage and expectations.

hm, if i can close the channel so there is no problem. sender should crash in this case.

this is nice now i use:
spawn do
  sleep 10
  ch.close
end
res = ch.receive rescue "timeouted"

spawn do
  sleep 20
  ch.send 1 # => Exception
end


Authentication failed

Hello,
I'm using the latest version of Rainloop (1.14) with openbsd httpd and I get the error: Authentication failed when I try to log in.
I'm sure my password is good.
Here is the log I have when I log in (my information has been changed):
[14:14:20.705][d8e775e6] INFO[DATA]: [DATE:10.12.20][OFFSET:-00][RL:1.14.0][PHP:7][IP:<IP_ADDRESS>][PID:60626][OpenBSD httpd][fpm-fcgi]
[14:14:20.705][d8e775e6] INFO[DATA]: [Suhosin:off][APC:off][MB:on][PDO:~][Streams:tcp,udp,unix,udg,ssl,tls,tlsv1.0,tlsv1.1,tlsv1.2,tlsv1.3]
[14:14:20.705][d8e775e6] REQUEST[NOTE]: [GET] http://webmail.hostname.org/
[14:14:20.718][d8e775e6] INFO[MEMORY]: Memory peak usage: 2MB
[14:14:20.718][d8e775e6] INFO[TIME]: Time delta: 0.055972814559937

[14:14:21.013][eabafbae] INFO[DATA]: [DATE:10.12.20][OFFSET:-00][RL:1.14.0][PHP:7][IP:<IP_ADDRESS>][PID:78919][OpenBSD httpd][fpm-fcgi]
[14:14:21.013][eabafbae] INFO[DATA]: [Suhosin:off][APC:off][MB:on][PDO:~][Streams:tcp,udp,unix,udg,ssl,tls,tlsv1.0,tlsv1.1,tlsv1.2,tlsv1.3]
[14:14:21.013][eabafbae] REQUEST[NOTE]: [GET] http://webmail.hostname.org/?/Css/0/User/-/Default/-/0f02fb6f9897aaf90b9e885d94f38646/Hash/-/
[14:14:21.027][eabafbae] INFO[MEMORY]: Memory peak usage: 2MB
[14:14:21.027][eabafbae] INFO[TIME]: Time delta: 0.057579040527344

[14:14:21.352][150fd65c] INFO[DATA]: [DATE:10.12.20][OFFSET:-00][RL:1.14.0][PHP:7][IP:<IP_ADDRESS>][PID:60626][OpenBSD httpd][fpm-fcgi]
[14:14:21.352][150fd65c] INFO[DATA]: [Suhosin:off][APC:off][MB:on][PDO:~][Streams:tcp,udp,unix,udg,ssl,tls,tlsv1.0,tlsv1.1,tlsv1.2,tlsv1.3]
[14:14:21.352][150fd65c] REQUEST[NOTE]: [GET] http://webmail.hostname.org/?/AppData@no-mobile-0/0/20782881742404158/
[14:14:21.357][150fd65c] APPDATA[DATA]: if(window.__initAppData){window.__initAppData({"Auth":false,"AccountHash":"","AccountSignMe":false,"AuthAccountHash":"","MailToEmail":"","Email":"","DevEmail":"","DevPassword":"","Title":"Webmail","LoadingDescription":"RainLoop","LoadingDescriptionEsc":"RainLoop","FaviconUrl":"","LoginDescription":"","LoginLogo":"","LoginBackground":"","LoginCss":"","UserLogo":"","UserLogoTitle":"","UserLogoMessage":"","UserCss":"","WelcomePageUrl":"","WelcomePageDisplay":"","IncludeCss":"","IncludeBackground":"","LoginDefaultDomain":"","DetermineUserLanguage":true,"DetermineUserDomain":false,"UseLoginWelcomePage":false,"StartupUrl":"","SieveAllowFileintoInbox":false,"ContactsIsAllowed":false,"ChangePasswordIsAllowed":false,"RequireTwoFactor":false,"Community":true,"PremType":false,"Admin":[],"Capa":["FOLDERS","MESSAGELIST_ACTIONS","DANGEROUS_ACTIONS","RELOAD","QUOTA","SETTINGS","ADDITIONAL_ACCOUNTS","IDENTITIES","THEMES","FILTERS","HELP","ATTACHMENTS_ACTIONS","MESSAGE_ACTIONS","COMPOSER","CONTACTS","SEARCH","SEARCH_ADV","GRAVATAR","ATTACHMENT_THUMBNAILS","PREFETCH","AUTOLOGOUT"],"Plugins":[],"System":{"version":"1.14.0","admin":false,"mobile":false,"mobileDevice":false,"webPath":"","webVersionPath":"rainloop\/v\/1.14.0\/","token":"3403b0f22542428af9e5222eb33737af","inIframe":false,"allowHtmlEditorSourceButton":false,"allowHtmlEditorBitiButtons":false,"allowCtrlEnterOnCompose":true,"customLoginLink":"","customLogoutLink":"","forgotPasswordLinkUrl":"","registrationLinkUrl":"","hideSubmitButton":true,"jsHash":"e87e39e557c3733406066e3c4c5a2253","useImapThread":true,"useImapSubscribe":true,"allowAppendMessage":false,"materialDesign":true,"folderSpecLimit":50,"faviconStatus":true,"allowCmdInterface":false,"useNativeScrollbars":false,"listPermanentFiltered":false,"themes":["Default","A","Blurred","DarkShine","Linen","Love","Snow","Squares","SquaresDark","Stripes","Wood","Xv","Clear"],"languages":["ar_SA","bg_BG","cs_CZ","da_DK","de_DE","el_GR","en_GB","en_US","es_ES","et_EE","fa_IR","fi_FI","fr_FR","hu_HU","id_ID","is_IS","it_IT","ja_JP","ko_KR","lt_LT","lv_LV","nb_NO","nl_NL","pl_PL","pt_BR","pt_PT","ro_RO","ru_RU","sk_SK","sl_SI","sv_SE","tr_TR","uk_UA","zh_CN","zh_TW"],"languagesAdmin":["cs_CZ","da_DK","de_DE","en_US","es_ES","fa_IR","fi_FI","fr_FR","hu_HU","id_ID","it_IT","ja_JP","lt_LT","nb_NO","nl_NL","pl_PL","pt_BR","ru_RU","sk_SK","sl_SI","sv_SE","zh_CN"],"appVersionType":"community","attachmentsActions":[]},"AdditionalLoginError":"","AllowGoogleSocial":false,"AllowGoogleSocialAuth":false,"AllowGoogleSocialAuthGmail":false,"AllowGoogleSocialDrive":false,"AllowGoogleSocialPreview":false,"GoogleClientID":"","GoogleApiKey":"","AllowFacebookSocial":false,"AllowTwitterSocial":false,"AllowDropboxSocial":false,"DropboxApiKey":"","SupportedFacebookSocial":true,"ProjectHash":"0f02fb6f9897aaf90b9e885d94f38646","NewMoveToFolder":true,"AllowLanguagesOnSettings":true,"AllowLanguagesOnLogin":true,"AttachmentLimit":26214400,"SignMe":"DefaultOff","UseLocalProxyForExternalImages":false,"ShowImages":false,"MPP":20,"SoundNotification":false,"DesktopNotifications":false,"Layout":1,"EditorDefaultType":"Html","UseCheckboxesInList":true,"AutoLogout":30,"UseThreads":false,"AllowDraftAutosave":true,"ReplySameFolder":false,"ContactsAutosave":true,"EnableTwoFactor":false,"ParentEmail":"","InterfaceAnimation":true,"UserBackgroundName":"","UserBackgroundHash":"","Theme":"Default","NewThemeLink":".\/?\/Css\/0\/User\/-\/Default\/-\/0f02fb6f9897aaf90b9e885d94f38646\/Hash\/-\/","Language":"en_US","LanguageAdmin":"en_US","UserLanguageRaw":"en_US","UserLanguage":"en_US","UserLanguageAdmin":"en_US","PluginsLink":"","LangLink":".\/?\/Lang\/0\/App\/en_US\/0f02fb6f9897aaf90b9e885d94f38646\/","TemplatesLink":".\/?\/Templates\/0\/App\/0f02fb6f9897aaf90b9e885d94f38646\/","StaticLibJsLink":"rainloop\/v\/1.14.0\/static\/js\/min\/libs.min.js?community","StaticAppJsLink":"rainloop\/v\/1.14.0\/static\/js\/min\/app.min.js?community","StaticAppJsNextLink":"rainloop\/v\/1.14.0\/static\/js\/app.next.js?community","StaticEditorJsLink":"rainloop\/v\/1.14.0\/static\/ckeditor\/ckeditor.js?community"});}
[14:14:21.364][150fd65c] INFO[MEMORY]: Memory peak usage: 2MB
[14:14:21.364][150fd65c] INFO[TIME]: Time delta: 0.055611848831177
[14:14:29.309][30ec4816] INFO[DATA]: [DATE:10.12.20][OFFSET:-00][RL:1.14.0][PHP:7][IP:<IP_ADDRESS>][PID:78919][OpenBSD httpd][fpm-fcgi]
[14:14:29.310][30ec4816] INFO[DATA]: [Suhosin:off][APC:off][MB:on][PDO:~][Streams:tcp,udp,unix,udg,ssl,tls,tlsv1.0,tlsv1.1,tlsv1.2,tlsv1.3]
[14:14:29.310][30ec4816] REQUEST[NOTE]: [POST] http://webmail.hostname.org/?/Ajax/&q[]=/0/
[14:14:29.312][30ec4816] AJAX[NOTE]: Action: DoLogin
[14:14:29.312][30ec4816] POST[DATA]: {"Email":"user@hostname.org","Login":"","Password":"*******","Language":"","AdditionalCode":"","AdditionalCodeSignMe":"0","SignMe":"0","Action":"Login","XToken":"3403b0f22542428af9e5222eb33737af"}
[14:14:29.322][30ec4816] IMAP[NOTE]: Start connection to "ssl://mail.hostname.org:993"
[14:14:29.369][30ec4816] IMAP[NOTE]: Connected (success)
[14:14:29.567][30ec4816] IMAP[DATA]: < * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN] Dovecot ready.\r\n
[14:14:29.568][30ec4816] IMAP[DATA]: > TAG1 AUTHENTICATE PLAIN\r\n
[14:14:29.570][30ec4816] IMAP[DATA]: < + \r\n
[14:14:29.570][30ec4816] IMAP[SECURE]: > *******\r\n
[14:14:31.137][30ec4816] IMAP[DATA]: < TAG1 NO [AUTHENTICATIONFAILED] Authentication failed.\r\n
[14:14:31.138][30ec4816] IMAP[WARNING]: MailSo\Imap\Exceptions\NegativeResponseException: MailSo-Imap-Exceptions-NegativeResponseException (ImapClient.php ~ 1876) in /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php:1876
Stack trace:
#0 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php(1953): MailSo\Imap\ImapClient->validateResponse()
#1 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php(283): MailSo\Imap\ImapClient->parseResponseWithValidation()
#2 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Mail/MailClient.php(93): MailSo\Imap\ImapClient->Login()
#3 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Model/Account.php(508): MailSo\Mail\MailClient->Login()
#4 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2154): RainLoop\Model\Account->IncConnectAndLoginHelper()
#5 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2405): RainLoop\Actions->CheckMailConnection()#6 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2457): RainLoop\Actions->LoginProcess()
#7 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/ServiceActions.php(174): RainLoop\Actions->DoLogin()
#8 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(150): RainLoop\ServiceActions->ServiceAjax()
#9 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(62): RainLoop\Service->localHandle()
#10 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(85): RainLoop\Service->__construct()
#11 /htdocs/mail/rainloop/v/1.14.0/app/handle.php(94): RainLoop\Service::Handle()
#12 /htdocs/mail/rainloop/v/1.14.0/include.php(228): include('/htdocs/mail/ra...')
#13 /htdocs/mail/index.php(13): include('/htdocs/mail/ra...')
#14 {main}
[14:14:31.138][30ec4816] IMAP[NOTICE]: MailSo\Imap\Exceptions\NegativeResponseException: MailSo-Imap-Exceptions-NegativeResponseException (ImapClient.php ~ 1876) in /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php:1876
Stack trace:
#0 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php(1953): MailSo\Imap\ImapClient->validateResponse()
#1 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php(283): MailSo\Imap\ImapClient->parseResponseWithValidation()
#2 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Mail/MailClient.php(93): MailSo\Imap\ImapClient->Login()
#3 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Model/Account.php(508): MailSo\Mail\MailClient->Login()
#4 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2154): RainLoop\Model\Account->IncConnectAndLoginHelper()
#5 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2405): RainLoop\Actions->CheckMailConnection()
#6 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2457): RainLoop\Actions->LoginProcess()
#7 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/ServiceActions.php(174): RainLoop\Actions->DoLogin()
#8 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(150): RainLoop\ServiceActions->ServiceAjax()
#9 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(62): RainLoop\Service->localHandle()
#10 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(85): RainLoop\Service->__construct()
#11 /htdocs/mail/rainloop/v/1.14.0/app/handle.php(94): RainLoop\Service::Handle()
#12 /htdocs/mail/rainloop/v/1.14.0/include.php(228): include('/htdocs/mail/ra...')
#13 /htdocs/mail/index.php(13): include('/htdocs/mail/ra...')
#14 {main}

Next MailSo\Imap\Exceptions\LoginBadCredentialsException: MailSo-Imap-Exceptions-LoginBadCredentialsException (ImapClient.php ~ 314) in /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php:314
Stack trace:
#0 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Mail/MailClient.php(93): MailSo\Imap\ImapClient->Login()
#1 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Model/Account.php(508): MailSo\Mail\MailClient->Login()
#2 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2154): RainLoop\Model\Account->IncConnectAndLoginHelper()
#3 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2405): RainLoop\Actions->CheckMailConnection()
#4 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2457): RainLoop\Actions->LoginProcess()
#5 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/ServiceActions.php(174): RainLoop\Actions->DoLogin()
#6 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(150): RainLoop\ServiceActions->ServiceAjax()
#7 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(62): RainLoop\Service->localHandle()
#8 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(85): RainLoop\Service->__construct()
#9 /htdocs/mail/rainloop/v/1.14.0/app/handle.php(94): RainLoop\Service::Handle()
#10 /htdocs/mail/rainloop/v/1.14.0/include.php(228): include('/htdocs/mail/ra...')
#11 /htdocs/mail/index.php(13): include('/htdocs/mail/ra...')
#12 {main}
[14:14:31.140][30ec4816] INFO[ERROR]: MailSo\Imap\Exceptions\NegativeResponseException: MailSo-Imap-Exceptions-NegativeResponseException (ImapClient.php ~ 1876) in /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php:1876
Stack trace:
#0 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php(1953): MailSo\Imap\ImapClient->validateResponse()
#1 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php(283): MailSo\Imap\ImapClient->parseResponseWithValidation()
#2 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Mail/MailClient.php(93): MailSo\Imap\ImapClient->Login()
#3 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Model/Account.php(508): MailSo\Mail\MailClient->Login()
#4 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2154): RainLoop\Model\Account->IncConnectAndLoginHelper()
#5 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2405): RainLoop\Actions->CheckMailConnection()
#6 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2457): RainLoop\Actions->LoginProcess()
#7 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/ServiceActions.php(174): RainLoop\Actions->DoLogin()
#8 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(150): RainLoop\ServiceActions->ServiceAjax()
#9 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(62): RainLoop\Service->localHandle()
#10 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(85): RainLoop\Service->__construct()
#11 /htdocs/mail/rainloop/v/1.14.0/app/handle.php(94): RainLoop\Service::Handle()
#12 /htdocs/mail/rainloop/v/1.14.0/include.php(228): include('/htdocs/mail/ra...')
#13 /htdocs/mail/index.php(13): include('/htdocs/mail/ra...')
#14 {main}
Next MailSo\Imap\Exceptions\LoginBadCredentialsException: MailSo-Imap-Exceptions-LoginBadCredentialsException (ImapClient.php ~ 314) in /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Imap/ImapClient.php:314
Stack trace:
#0 /htdocs/mail/rainloop/v/1.14.0/app/libraries/MailSo/Mail/MailClient.php(93): MailSo\Imap\ImapClient->Login()
#1 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Model/Account.php(508): MailSo\Mail\MailClient->Login()
#2 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2154): RainLoop\Model\Account->IncConnectAndLoginHelper()
#3 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2405): RainLoop\Actions->CheckMailConnection()
#4 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2457): RainLoop\Actions->LoginProcess()
#5 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/ServiceActions.php(174): RainLoop\Actions->DoLogin()
#6 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(150): RainLoop\ServiceActions->ServiceAjax()
#7 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(62): RainLoop\Service->localHandle()
#8 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(85): RainLoop\Service->__construct()
#9 /htdocs/mail/rainloop/v/1.14.0/app/handle.php(94): RainLoop\Service::Handle()
#10 /htdocs/mail/rainloop/v/1.14.0/include.php(228): include('/htdocs/mail/ra...')
#11 /htdocs/mail/index.php(13): include('/htdocs/mail/ra...')
#12 {main}

Next RainLoop\Exceptions\ClientException: AuthError[102] in /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php:2173
Stack trace:
#0 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2405): RainLoop\Actions->CheckMailConnection()
#1 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Actions.php(2457): RainLoop\Actions->LoginProcess()
#2 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/ServiceActions.php(174): RainLoop\Actions->DoLogin()
#3 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(150): RainLoop\ServiceActions->ServiceAjax()
#4 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(62): RainLoop\Service->localHandle()
#5 /htdocs/mail/rainloop/v/1.14.0/app/libraries/RainLoop/Service.php(85): RainLoop\Service->__construct()
#6 /htdocs/mail/rainloop/v/1.14.0/app/handle.php(94): RainLoop\Service::Handle()
#7 /htdocs/mail/rainloop/v/1.14.0/include.php(228): include('/htdocs/mail/ra...')
#8 /htdocs/mail/index.php(13): include('/htdocs/mail/ra...')
#9 {main}
[14:14:31.140][30ec4816] AJAX[DATA]: {"Action":"Login","Result":false,"ErrorCode":102,"ErrorMessage":"","ErrorMessageAdditional":"","Time":1867}
[14:14:31.145][30ec4816] INFO[MEMORY]: Memory peak usage: 2MB
[14:14:31.145][30ec4816] INFO[TIME]: Time delta: 1.8704500198364
[14:14:31.146][30ec4816] IMAP[NOTE]: Disconnected from "ssl://mail.hostname.org:993" (success)

Please could you help me ?
Thank's

Issue solved like used short login user.


Provide gdc builds via make

Fixes #131
Also includes a commit which avoids rebuilding dfmt on every test run and cleans up the makefile a little.

Duplicated LDC_FLAGS to GDC_FLAGS. Probably better if one changes the flags at some point.


About dependencies

Congrads for the great job. Could you please create a requirements.txt file for the dependencies ?

Good idea, thanks for suggesting.  I've begun this and some clean up in the reqs branch


Maturity classification & unstable folder

This adds a section to the readme on 'maturity classifications', and also has a very incomplete 'dataset collection' partially ported from https://github.com/cholmes/ogc-collection/blob/main/ogc-dataset-collection-spec.md
The remaining work is to go through each block and mark it with a maturity and a reference.
It is based off of PR #3, so that one should merge first.

I like the maturity classification, also having "mature" vs "stable".


Address user complaints about webpack 2 site visibility

To quote @dmitriid from https://github.com/webpack/webpack/issues/3275#issuecomment-260241927

update docs to clearly state which version of webpack they refer two
create page clearly detailing what 2.x is, how to get it etc.
update docs to reflect changes in plugins, loaders etc. (there are already people asking how to use, say, LoaderOptionsPlugin, see comments here
move information on webpack 2.x from gists, unfinished pages and Google docs (really?? really?? google docs????) to the place where they can be easily viewed and accessed by everyone

Closing in favor of #327.


Dragonrage: Watch koinfotech.com

Dragonrage requests the watch of the watch_keyword koinfotech\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

koinfotech\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Nisse Engström in Charcoal HQ


macOS: Build Fails, Seeed_Arduino_FreeRTOS.h Not Found

I've followed the procedure but ./arduino-build.sh --build fails with the following error:
% cd /Users/USER/Arduino/Libraries/Seeed_Arduino_edgeimpulse
% ./arduino-build.sh --build

Building Seeed_Arduino_edgeimpulse.ino
Still building...
In file included from /Users/USER/Arduino/Libraries/Seeed_Arduino_edgeimpulse/Seeed_Arduino_edgeimpulse.ino:24:0:
/var/folders/wn/n7qqb8ss0k3bvpqwfcdwp_7r0000gn/T/arduino-sketch-5058F1AF8388633F609CADB75A75DC9D/sketch/src/setup.h:25:10: fatal error: Seeed_Arduino_FreeRTOS.h: No such file or directory
 #include "Seeed_Arduino_FreeRTOS.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Error during build: exit status 1
./arduino-build.sh: line 44: exit: Building Seeed_Arduino_edgeimpulse.ino failed: numeric argument required

The Seeed_Arduino_FreeRTOS.h header file is located at /Users/USER/Arduino/Libraries/Seeed_Arduino_FreeRTOS/src/Seeed_Arduino_FreeRTOS.h.
What's going on?
% uname -a
Darwin MacBook.local 19.6.0 Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64 x86_64
% arduino-cli version
arduino-cli Version: 0.11.0 Commit: 0296f4df116385f868b67c5ffa7393936c3345c9
``

Refer to CI for specific compilation method
https://github.com/Seeed-Studio/Seeed_Arduino_edgeimpulse/blob/master/.travis.yml

I can’t see any difference between the CI and the Building the application I’ve followed with the error mentioned earlier.
Would you mind using the standard Arduino IDE instead of Arduino-CLI to build the example?
Thank you!

The main reason is that the SDK of EdgeImpulse does not conform to the directory structure of the Arduino Library.We need to follow the rules of the upstream game. @rei-vilo


Enable sub headers in docs

Resolves #3285
This is done by setting sidebarDepth to 1  in VuePress config  for the IoTDB-SQL section. The result is that we can now show second level headers (i.e. ## xxxx) in the sidebar of the IoTDB-SQL section. The sidebar of other sections remain unchanged for conciseness.
Also fixed the headings for some documents.
Final result
English:

Chinese:

Animation:

Coverage decreased (-0.005%) to 67.899% when pulling 8a68b5bae10a7d94c37d7de59e32b7cbbb701327 on liujiajun:patch-3 into a99bf9c78eb02f2258f442ae7af725f3fff23ad3 on apache:master.

@qiaojialin Thanks! Merged and CI seems ok now


As Em, I can make training comparisons that persist across their search.

Em can use the same functionality that exists for the filter tool to navigate across the site and retain their training comparisons.

Conditionally closing: adjust compare buttons and frame on mobile: https://www.figma.com/file/E93aghu0LH4kXQWReLfNNY/D4AD-Training-Explorer?node-id=2150%3A41


Fix buffer overflow in soundex library

No space was allocated for the null terminator in the result buffer. ASan catches this error when running the tests.
There's a potential issue that d (and i) will overflow, computing an incorrect result, except that they're tied to a VLA and the program would crash via stack overflow well before that point. Especially considering the VLAs (#58), this soundex library is questionable and probably shouldn't be used on untrusted input without careful review and fixes, and VLA removal.

Thanks! Released in 0.17.2 together with PRs #57 and #58.


[DOC] Update forum link on dev-env page

Insert the documentation link:
https://docs.luos.io/pages/low/dev-env.html
Describe the issue or the suggestion:
Note: More information about how Luos libs are managed into PlatformIO is available by following this post on our forum.
The link is deprecated.
How would you fix the issue / which content would you add or delete?
New link: https://community.luos.io/t/how-to-link-luos-with-platformio/303

Fixed on next release


Integrate remote policies [WIP]

This is WIP...
At this stage, this PR includes everything needed but authentication flow (which will be device flow).
This PR...
Changes

Introduced mechanism for remote policy fetching:

Added monokle.remotePolicyUrl config option. When set (passing URL to Monokle Cloud API) it will trigger downloading policy from the API.
Added Monokle: Download Policy command. It is designed to allow users to force download policy anytime (instead of waiting for periodical pull).
Added PolicyPuller class which instance is responsible for initial and periodical policy fetch (see more below).

Policy puller
PolicyPuller is responsible for remote policy fetching. It will query Cloud GraphQL API, first fetching user data (list of all projects) based on auth token. Then if a local folder is a git repo with any remote (so we can extract owner and name) it will be matched with a project.
Matching is done as follow:

If there is a project to which repo belongs to (based on repo owner and name) and has prChecks flag enabled - match with this project. prChecks flag indicates that this is a project from which we want to use policy, because GH bot is using it too.
If there is no such project, fallback to first project to which repo belongs to.

After matching with a project, Cloud GraphQL API will be queried for a policy. If there is one, it will be saved locally (in /path/to/extension/.monokle/ folder). On every validation, the policy is read from locally saved file.
The process above is the same for initial policy fetch (on extension activation) and on periodical fetches (every 30 seconds now).
Policies priorities
We have 4 types of policies configurations:

default - based on what @monokle/validation package provides.
file - read from monokle.validation.yaml file in folder root (can be added with Monokle: Bootstrap configuration) command.
config - read from local filesystem, based on monokle.configurationPath setting.
remote - fetched from remote API (Monokle Cloud).

The priorities are (from highest) - remote, config, file, default. Meaning that I can have local monokle.validation.yaml file, but when monokle.remotePolicyUrl is set, remote config will be used.
Handling special (kind of) cases
Assuming that monokle.remotePolicyUrl is configured correctly, the "happy case" is that a folder:

Is a git repository.
Has any remote configured.
Belongs to any project in the Monokle Cloud (based on remote owner/name).
And this project has policy configured.

In such case we can fetch remote policy.
Now, any of those may not be true, meaning that extension needs to react in each case. See below what will happen in each case:

Folder is not a git repo - show warning and fallback to local configs.
Folder is a git repo, but doesn't have any remotes - show error, don't validate.
Folder is a git repo, have remote, but does not belong to any project in the cloud - show error, don't validate.
Folder is a git repo, have remote, belongs to a project in the cloud, but project doesn't have a policy defined - show error, don't validate.

I think the key here is to provide clear messages, and if possible, with links to docs, or deep links to cloud (e.g. policy wizard) so users can act on those errors.
Fixes

Reworked tests. Enabled CC check on CI.
Added handling for invalid configs.

Before it would usually fallback to default policy, which was not really transparent for the user. Now, when there is a config file or a setting pointing to one, but invalid/non-existent, user will get error notification with explanation what went wrong and suggestions on a fix (for some cases).

Checklist

[x] tested locally
[x] added new dependencies
[ ] updated the docs
[x] added a test

@WitoDelnat @olensmar maybe you can take a quick look on the above description/assumptions (especially policy priorities and handling special cases) to make sure it also aligns with your vision?


change default node id by its label

How can I change the displayed id value by the node's name?

Try to modify appendTextToNode() in neo4jd3.js


getting email for Node.js 16 "AWS Lambda end of support for Node.js 16" for Lambda functions which are deployed using LZA 1.4.3

Today we have received emails for each account where we are using LZA 1.4.3 and all states that we need to upgrade existing Node.js 16 function to Node.js 20 before June 20,2024.
Can someone confirm this is taken care in latest release of LZA 1.5.2. or do we have to wait for next release of LZA for its resolution.

https://github.com/awslabs/landing-zone-accelerator-on-aws/issues/362

@rupeshdumbre2021 Thank you for opening this issue regarding the upcoming Node16 EOL in June of 2024. The fix for this will be tracked as part of #362.
To directly answer your question, v1.5.2 has many of the Lambda functions upgraded to Node18, but there are still some functions utilizing the Node16 runtime and need to be updated.
This issue will be closed in favor of #362


TST: Fix tests in TestGoogle

Fixes the tests in data reader that will be run when the bug in #9744 is fixed.
This needs to be merged before I can fix #9744.

thanks!


Remove ADAravis Deadtime Lookup Table

Fixes #304
Remove ADAravis deadtime lookup table, replace with a static value: the highest possible deadtime for an aravis detector.

@Tom-Willemsen we were just discussing this actually. The problem in general is the expectation that the verbs stage, trigger, kickoff etc. are called in a certain order and there is nothing to enforce that, it's convention only. I'm not sure where/how best to map the confusing web of dependencies of operations, in either a human or machine-readable way.
The water here is getting muddied because recent changes have added new verbs like prepare and declare_stream, increasing the number of permutations.

I'm not sure where best to put this comment, but could we maybe add some docs describing exactly what was wrong with the implementation being removed - maybe in an FAQ or pitfalls type document? It feels like an easy trap to fall into, and even after reading #308 and #304 I'm not convinced I actually understand why it was wrong.
In particular:

depends on prepare() in a way that blocks flyscanning plans

What is the exact dependency chain between "doing an extra read during prepare()" and "blocking fly scans"?

Just incase it wasn't explained: In fly scanning plans we want to be able to call prepare on all of our devices without them depending on one another for ordering. In the preparing planstub currently in ophyd-async we take a bunch of detectors and a flyer, make some objects which both of them need, and then prepare them both. However, in order to make said "stuff" we need the deadtime of the detector, which was previously found dynamically when prepare was called. Hence the circular problem.


owasp-zap-243-update

Update version and checksum for 2.4.3.

Thank you for the contribution. It was merged directly as 85c20c47e2d2cc2a3a84edbaa7635400e623ec98 to keep commit history cleaner. Your contribution is still credited to you.

Not to be obtuse, but so that I get it right next time, do you want me to submit directly to master instead of creating a working branch first? Or had someone already submitted a PR? (Perhaps that's happening automatically and I just am not aware.)

@kingthorin You did everything fine. That comment you see is an artifact of directly committing your PR (instead of a "merge") - we do this to keep the commit history cleaner. You'll see kingthorin committed with vitorgalvao, instead of two separate commits (owasp-zap-243-update and a merge pull request #xxxx from kingthorin)


Corrected Throughput measure for GaudiDDPMPipeline

What does this PR do?
The test GaudiDDPMPipelineTester::test_no_throughput_regression_bf16() fails with throughput comparison, but throughput was being measured inversely as sec/sample instead of samples /sec.
This PR does the follow

Corrected throughput measure formula for GaudiDDPMPipeline
Updated the Gaudi benchmark values for diffusion test test_no_throughput_regression_bf16()

Below is the summary of slow_diffusion tests
python -m pytest tests/test_diffusers.py -v -s -k "test_textual_inversion"
============================= test session starts ==============================
platform linux -- Python 3.10.12, pytest-7.4.4, pluggy-1.5.0 -- /usr/bin/python
cachedir: .pytest_cache
rootdir: /mnt/oh_pr
configfile: setup.cfg
collecting ... collected 159 items / 158 deselected / 1 selected
========== 1 passed, 158 deselected, 5 warnings in 160.91s (0:02:40) ===========
python -m pytest tests/test_diffusers.py -v -s -k "test_train_text_to_image_"
============================= test session starts ==============================
platform linux -- Python 3.10.12, pytest-7.4.4, pluggy-1.5.0 -- /usr/bin/python
cachedir: .pytest_cache
rootdir: /mnt/oh_pr
configfile: setup.cfg
collecting ... collected 159 items / 157 deselected / 2 selected
========== 2 passed, 157 deselected, 3 warnings in 486.10s (0:08:06) ===========
python -m pytest tests/test_diffusers.py -v -s -k "test_train_controlnet"
============================= test session starts ==============================
platform linux -- Python 3.10.12, pytest-7.4.4, pluggy-1.5.0 -- /usr/bin/python
cachedir: .pytest_cache
rootdir: /mnt/oh_pr
configfile: setup.cfg
collecting ... collected 159 items / 157 deselected / 2 selected
========== 2 passed, 157 deselected, 5 warnings in 201.56s (0:03:21) ===========
python -m pytest tests/test_diffusers.py -v -s -k "test_deterministic_image_generation"
============================= test session starts ==============================
platform linux -- Python 3.10.12, pytest-7.4.4, pluggy-1.5.0 -- /usr/bin/python
cachedir: .pytest_cache
rootdir: /mnt/oh_pr
configfile: setup.cfg
collecting ... collected 159 items / 157 deselected / 2 selected
========== 2 passed, 157 deselected, 6 warnings in 276.77s (0:04:36) ===========
python -m pytest tests/test_diffusers.py -v -s -k "test_no_"
============================= test session starts ==============================
platform linux -- Python 3.10.12, pytest-7.4.4, pluggy-1.5.0 -- /usr/bin/python
cachedir: .pytest_cache
rootdir: /mnt/oh_pr
configfile: setup.cfg
collecting ... collected 159 items / 153 deselected / 6 selected
===== 5 passed, 1 skipped, 153 deselected, 6 warnings in 416.68s (0:06:56) =====
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[x] Did you write any new necessary tests?

@jiminha @emascarenhas
Request to review PR for feedback

@deepak-gowda-narayana nice catch! You are right throughput typically measures the number of units processed per unit of time and here it is inverse of that!
Would you please post the tests and failures before this PR?

@deepak-gowda-narayana nice catch! You are right throughput typically measures the number of units processed per unit of time and here it is inverse of that!
Would you please post the tests and failures before this PR?

@yafshar
Sure, here is the test summary
Result Summary of fast_tests.sh
python -m pytest tests/test_gaudi_configuration.py tests/test_trainer_distributed.py tests/test_trainer.py tests/test_trainer_seq2seq.py
=============================================================================================== 81 passed, 8 skipped, 39 warnings in 109.40s (0:01:49) ================================================================================================
Result Summary of fast_tests_diffusers.sh
python -m pytest tests/test_diffusers.py
================================================================================================= 113 passed, 47 skipped, 280 warnings in 1229.45s (0:20:29) =================================================================================================
Result Summary of slow_tests_diffusers.sh
================================================================================================================== short test summary info ===================================================================================================================
FAILED tests/test_diffusers.py::GaudiDDPMPipelineTester::test_no_throughput_regression_bf16 - AssertionError: 6.937816172838211 not greater than or equal to 7.287651444971561
======================================================================================= 1 failed, 4 passed, 1 skipped, 154 deselected, 6 warnings in 358.13s (0:05:58) =======================================================================================
make: *** [Makefile:104: slow_tests_diffusers] Error 1

@regisss @yafshar PR Updated - removed absolute import path


Finish implementing remaining endpoints

[ ] /authenticate
[ ] /collections
[ ] /config
[ ] /data-objects
[x] /info
[ ] /metadata
[x] /query
[ ] /resources
[ ] /rules
[ ] /tickets
[ ] /users-groups
[ ] /zones

What does finish mean?
This issue doesn't state the work needed to close this issue.
Every modification to the application will be associated with an issue number, therefore, this issue doesn't help anyone in the grand scheme of things.
Closing.


Add myself to release list

Description
Would like release permissions for https://github.com/jenkinsci/change-assembly-version-plugin, cc @lkobus, @nilleb, @znek for sign-off
Submitter checklist for changing permissions
Always

[x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

@slide Is there a context for permissions that would speed this up, or are we waiting for approval by the pinged users?

I definitely approve, since I wasn't anymore aware of being a maintainer of
this plugin (sorry)
Le mar. 13 févr. 2018 à 18:21, Daniel Beck<EMAIL_ADDRESS>a
écrit :

@slide https://github.com/slide Is there a context for permissions that
would speed this up, or are we waiting for approval by the pinged users?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jenkins-infra/repository-permissions-updater/pull/589#issuecomment-365338756,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADVmx2LlvGrS798_U75cCFGbXOcjFqX8ks5tUcSKgaJpZM4SCuKg
.

It's not clear to me what the user list is based on. In the GitHub team, @lkobus and @sankethpb are developers, and here, only the former has access. @slide Could you clarify?

@daniel-beck This is the context https://github.com/jenkinsci/change-assembly-version-plugin/pull/17#issuecomment-364553617

@slide Well, @lkobus merged https://github.com/jenkinsci/change-assembly-version-plugin/pull/4 https://github.com/jenkinsci/change-assembly-version-plugin/pull/5 https://github.com/jenkinsci/change-assembly-version-plugin/pull/7 which are by the other users you mentioned, and how they got into the history, so that doesn't really count 😉
While @sankethpb is a committer, there's no activity of them I can find, so we'll wait for confirmation by @lkobus; I recommend you try to reach out to them directly.

Not sure how I got here, but I shouldn't have release permissions. So, no.

@znek You got here because I used the wrong list in my CC. Sorry about that.

Pinging @lkobus and @sankethpb again. We'd appreciate a response, thanks!

@lkobus replied directly to me via email, but I can ping again if desired for public confirmation.


Dependency compilation fails due to substrate updates

Description
Runtime build fails after adding in frontier pallets. Believe this is due to the following commit added to the substrate codebase - https://github.com/paritytech/substrate/commit/c45c1cbfde0037e6ef650146789a0aa0190fdefb.
Steps to Reproduce

Add frontier pallets to the runtime Cargo.toml.
No configuration has been changed on the runtime side of things apart from Cargo.toml file.
Run build using cargo build

Expected vs. Actual Behavior
Dependencies would be compiled even if not used in the runtime, due to changes to substrate codebase it fails.
Environment

Operating system: Mac OS Monterey 12.0.1
Project version/tag: latest master, aa5e518923e9cfd1348cfb767a6b10b1acf8ecc1
Rust version (run rustup show): rustc 1.55.0-nightly (e8cb1a4a5 2021-06-27)

Logs, Errors or Screenshots
   Compiling sp-consensus v0.10.0-dev (https://github.com/paritytech/substrate?branch=polkadot-v0.9.13#fcc54a72)
error[E0107]: this struct takes 0 generic arguments but 1 generic argument was supplied
  --> /Users/User/.cargo/git/checkouts/frontier-b4643f17507d3282/aa5e518/primitives/consensus/src/lib.rs:92:36
   |
92 | pub fn find_pre_log<Hash>(digest: &Digest<Hash>) -> Result<PreLog, FindLogError> {
   |                                    ^^^^^^------ help: remove these generics
   |                                    |
   |                                    expected 0 generic arguments
   |
note: struct defined here, with 0 generic parameters
  --> /Users/User/.cargo/git/checkouts/substrate-7e08433d4c370a21/3d005a3/primitives/runtime/src/generic/digest.rs:38:12
   |
38 | pub struct Digest {
   |            ^^^^^^

error[E0107]: this struct takes 0 generic arguments but 1 generic argument was supplied
   --> /Users/User/.cargo/git/checkouts/frontier-b4643f17507d3282/aa5e518/primitives/consensus/src/lib.rs:107:37
    |
107 | pub fn find_post_log<Hash>(digest: &Digest<Hash>) -> Result<PostLog, FindLogError> {
    |                                     ^^^^^^------ help: remove these generics
    |                                     |
    |                                     expected 0 generic arguments
    |
note: struct defined here, with 0 generic parameters
   --> /Users/User/.cargo/git/checkouts/substrate-7e08433d4c370a21/3d005a3/primitives/runtime/src/generic/digest.rs:38:12
    |
38  | pub struct Digest {
    |            ^^^^^^

error[E0107]: this struct takes 0 generic arguments but 1 generic argument was supplied
   --> /Users/User/.cargo/git/checkouts/frontier-b4643f17507d3282/aa5e518/primitives/consensus/src/lib.rs:122:32
    |
122 | pub fn find_log<Hash>(digest: &Digest<Hash>) -> Result<Log, FindLogError> {
    |                                ^^^^^^------ help: remove these generics
    |                                |
    |                                expected 0 generic arguments
    |
note: struct defined here, with 0 generic parameters
   --> /Users/User/.cargo/git/checkouts/substrate-7e08433d4c370a21/3d005a3/primitives/runtime/src/generic/digest.rs:38:12
    |
38  | pub struct Digest {
    |            ^^^^^^

error[E0107]: this struct takes 0 generic arguments but 1 generic argument was supplied
   --> /Users/User/.cargo/git/checkouts/frontier-b4643f17507d3282/aa5e518/primitives/consensus/src/lib.rs:144:34
    |
144 | pub fn ensure_log<Hash>(digest: &Digest<Hash>) -> Result<(), FindLogError> {
    |                                  ^^^^^^------ help: remove these generics
    |                                  |
    |                                  expected 0 generic arguments
    |
note: struct defined here, with 0 generic parameters
   --> /Users/User/.cargo/git/checkouts/substrate-7e08433d4c370a21/3d005a3/primitives/runtime/src/generic/digest.rs:38:12
    |
38  | pub struct Digest {
    |            ^^^^^^

For more information about this error, try `rustc --explain E0107`.
error: could not compile `fp-consensus` due to 4 previous errors
warning: build failed, waiting for other jobs to finish...
error: build failed

Bumped into the same error @firke, have you found any solutions?

@Shubham9517 yes, so i've forked frontier repo and in primitives/consensus/src/lib.rs removed all the  parts, like so:
old:
pub fn ensure_log<Hash>(digest: &Digest<Hash>) -> Result<(), FindLogError> {
new:
pub fn ensure_log(digest: &Digest) -> Result<(), FindLogError> {

Whether there is an official solution for this bug?


Documentation and confusion

Describe the bug
Everything runs smoothly except "eth_sendTransaction".
According to https://github.com/oliverw/miningcore/wiki/Coin-Daemon-&-Wallet-RPC#ethereum
you can run go-ethereum (geth) with:
$ geth --cache 1024 --mine --http --http.port 8545 --unlock  --password  --allow-insecure-unlock
Mining works fine.
But after a mined block, I get an error when Miningcore should reward the miners on the pool.
Miningcore says "System.Exception: eth_sendTransaction returned error: invalid sender code -32000"
Geth says err="invalid sender"
I can transfere founds in the go-ethereum javasript console.
Have I forgot something here ?
To Reproduce
Steps to reproduce the behavior:

Setup go-ethereum according to documentation.
Setup Miningcore according to documentation.
Run mining on Miningcore.
Find a block.
No payment for miners due to error in configuration.

Expected behavior
Mining and payment should work by following instructions or manual.
Screenshots
I can provide screenshot If needed, or any other information.
Maybe this is something that others also run into,
and can be fixed by providing a little more information.
Platform and software

Ubuntu 22.04 LTS
Latest Miningcore.
Go-ethereum (geth) v1.20.1-beta (https://github.com/ethereumpow/go-ethereum/releases)

Forgive my ignorance but isn't this question purely academic as of yesterday?

Maybe it is a bug ?

Maybe it is a bug ?

Its most likely a bug but what is the relevance after yesterdays merge?

Ah! Got it! :)
Have a pool 90% set up for ETHPOW fork :)

Ah ok. Will look into it in a bit.

Let me know if you need more info.
Thanks!

We also had an issue with miningcore when miningcore tried to pay miners more than the incoming balance in the base wallet.
It is possible that this was an issue (behaviour) beacause of a little messy dev-setup and the back and forth trying to get things working.
But it is very strange that miningcore are reporting reward: 5 when the ethereum pow block explorer says about 2 ether.
Here is the link to the dev setup: http://miningpool.no:4000/api/pools/miningpool1/blocks
UI is at http://miningpool.no/
You might want to look into this if this is related to the ethereum pow fork witch launches soon.

So it was an uncle identified as a full block?

I need to see the block explorer to be sure.
https://iceberg.ethwscan.com/blocks
But it is down at the moment.

Looks like the block explorer for the testnet is permanently down.
It should be easy to reproduce. I can make a compact list of steps.

Block reward should be 2.00 ETHW.

Work Great here.   Its actualy  2ethw +netfee so it can be higer and you have unicles that is less  and orphan  0.

Block reward should be 2.00 ETHW.

What coin are we actually talking about?

Ethereum POW (ETHPOW, ETW)
https://ethereumpow.org/

Ethereum POW (ETHPOW, ETHW) https://ethereumpow.org/

So this is an issue about a coin that's not actually supported by MC? And you didn't even mention that?

Sorry. I should have.
Thought since it is basicly ethereum i did not underline it.
I thought the issue was I/O related between MC and Geth.

Ah! Got it! :) Have a pool 90% set up for ETHPOW fork :)

What was the solution for your issue ```
System.Exception: eth_sendTransaction returned error: invalid sender code -32000"
Geth says err="invalid sender"

I remember seeing the same error a very long time ago while testing ETH, but cannot remember what the solution was.

What was it in your case?

Might be worth giving dev a shot. I have pushed 7973a2bf19a5acdddd57b1e88df3eebd4dd8d663 a couple hours ago.

Great! Thank you.

Any findings?

New server is up. But the blockchain is in "heal modus".
Will let you know.

New server is up. But the blockchain is in "heal mode". Will let you know.

So?

Still "State heal in progress"

Still "State heal in progress"

It really shouldn't take that long. I'd start over with a clean slate if I was you.

Ethw actualy  takes manny manny hours to sync.
We usualy dl chain add it inn manual as its multiple GB in size. And do a reindex as its faster.
Ethw is same as eth. Etc  dont alow you to runn wallet in prune. And dont realy help woth good nodes as it simple go slow.

Ethw actualy takes manny manny hours to sync. We usualy dl chain add it inn manual as its multiple GB in size. And do a reindex as its faster. Ethw is same as eth. Etc dont alow you to runn wallet in prune. And dont realy help woth good nodes as it simple go slow.

Hours? @binaryf posted his last update 7 days ago.


Setting for  updating Gads param on request

Provides a convenient option on Server request to specify whether it
need GAds params with the request
@aaustin @Sarkar

:+1: Looks good

nice one :+1:


arm/gicv3: replace this_cpu() to up_cpu_index()

Summary
arm/gicv3: replace this_cpu() to up_cpu_index()
If the core id needs to be included in the hardware register
calculation, up_cpu_index() should be used instead of this_cpu().
Signed-off-by: chao an<EMAIL_ADDRESS>Impact
N/A
Testing
ci-check

[Experimental Bot, please feedback here]
NuttX PR Requirements Review:
Verdict: This PR appears incomplete based on the provided information.
Reasons:

Summary: While it explains the technical change, it lacks context.

What problem does this fix?  Is this_cpu() causing a bug? If so, describe it.
Which hardware registers are affected? Be specific.

Impact:  Dismissing all impact with "N/A" is rarely accurate. Consider these:

Hardware: You explicitly mention "hardware register calculation". Which architectures/boards use GICv3 and are thus affected?
Compatibility:  Could this change break existing drivers or configurations that rely on the old behavior?

Testing:

"ci-check" is insufficient.  Provide:

Specific build hosts & targets used for verification
Actual test logs (before/after) demonstrating the problem and its resolution.

What was the expected behavior vs. the actual behavior before the fix?

Recommendations:

Expand the Summary with clear problem description, affected hardware, and benefits of the change.
Thoroughly analyze Impact. Even if the answer is "NO" for most, justify it briefly (e.g., "No impact on documentation, as this is a purely internal code change").
Provide detailed testing information.  This is crucial for reviewers to assess the validity of your PR.


Hello, World!

What does the program do ?

In what programming language it is written?

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Scala Stream Collector: implement back-pressure

With the current architecture, if we have a malfunctioning Kinesis stream, then we will:

Continue to accept events from a tracker cache and 200 them (so tracker deletes them from cache)
Add all these events to an in-memory buffer in the hope that Kinesis will start functioning again

In other words - we don't implement back-pressure, and we take a significant risk that we will end up with at-most-once processing rather than at-least-once processing.
A better approach would be to set a failure threshold (e.g. Kinesis out of action for X minutes, or N events in the in-memory buffer), and if that is reached, then we start returning 503s (or similar) and the trackers keep the events on their side...

/cc @fblundun @ninjabear

The other thing we discussed is a switch that starts the collector writing to a file or S3 bucket - meaning that we can rerun those events later if required.
The number of events that haven't made it into kinesis or the last kinesis write timestamp would be good information to put on any healthchecks the collector provides.
In my experience the JVM can be pretty unhelpful when trying to store large amounts of information in memory, I'd find it interesting to know what happens exactly when the collector tries to cache a lot of events (do we already have a JVM imposed limit for cache size?).

Thanks @ninjabear - good points. Rather than complect the fallback switch into the Scala Stream Collector, I think it would be better to do this out-of-band using the healthcheck. In other words:
On each collector instance:

Have a process checking the collector healthcheck
If backpressure gets too great, then restart the collector with the fallback config (which writes to S3)

Another thing to consider is that whether we want to enable the fallback on a box-by-box basis, or globally for the whole collector cluster. It might be more coherent to do the latter.
Have also added: #2466

I agree that it would be better to do the fallback globally - I can't imagine why one collector instance would need to fallback but others wouldn't.
Also - if we have an external process restarting the collector, we will need to make sure that any records buffered by the collector are flushed before the restart.

We could add Consul to the Collectors to allow them to communicate with each other?

I think communication rather than hard killing is a good idea. If Kinesis ceases to exist, the collectors need to do something with their in-memory data before they are killed and restarted. So we might as well just build in a way to switch between Kinesis and S3 (or another "safe" target) without the collector restarting.

I was just writing the same thing @fblundun, all of this can be done by treating the collector as a microservice with an api

This is cool...

It might not be a bad idea still to implement something like RocksDB on the box just in case the instance does get restarted so we are not depending on the in-memory storage?

Yes, I think that's orthogonal and we should be doing that anyway - we don't want to be in a situation where we can't bounce a box without losing data...


xilinx_srl pass for shift register extraction

Replaces both uses of shregmap inside synth_xilinx with a pmgen-based xilinx_srl
xilinx_srl works for both built-in $_DFF* cells as well as FDRE*...
... enabling synth_xilinx -abc9 to perform map_ffs before map_luts (and unblocking #1312 and #1181)
Remove shregmap -tech xilinx as superseded

Will merge when Jenkins comes back clean.


feat requ: when no heads exits, disable all header based features please

i use the plugin and disable all options to only render a very basic table..
OF COURSE THE TABLE NO HAS HEADER so got this error:
Uncaught TypeError: Cannot read property 'rows' of null vanilla-dataTables.js:250
build vanilla-dataTables.js:250
Plugin vanilla-dataTables.js:601
(anonymous function)

HAPENED DUE THE PAGINATION I GUESS, based on heading NOTE in documentation, so a header - less can be do, only disabling all heading based features, this help to solve the issue #4 and make it work with normal tables tags
the code init to do was:
</table><script src="http://<IP_ADDRESS>/~general/codeigniter/appweb/scripts/vanilla-dataTables.js"></script>
<script>
var optionstable306 = { sortable: false, searchable: false, fixedcolumn: false, perPage: 50 };
var datatable306 = new DataTable(document.getElementById('table306'), optionstable306);</script>

i set some hacks on the js code but i'll parse and post feedback here after some tests..

@Mobius1 i respond here due the facts:
i'm still studin if a rendering with no headers its possible, based on #5 seems that its possible..
this its the rendering results (with some errors): its xtremedly basic and u will think "well if no headers and will paint very basic, so for what use datatables?"...
well its due i'm integrating into codeigniter modified version, so if the table open tag does not providing header, will render very baic..
in the other hand, well if script initialization was not detect headers, event luach a exception u could launch a console log or only wrning and render only basic.. so developer got less frustrating (yeah i spend some hours to got it)

i got a decent code, tested i propose:
around line 560
		if (table.tHead === null)
		{
			_.options.sortable = false;
			_.options.searchable = false;
			_.options.fixedColumns = false;
		}

does all the trick and solves both problems.. but in the other hand i wish a miracle, ...could be possible make search without headers?

This is fixed in the latest release. :)

hey u made a totally different way of, the commit 313ec92 does not introduced new regresions?
ill' closes the #5 and #4 when i tested in good way, give a few hours, and please take in consideration the isse about got the pagination on the header

AWESOME; i'm able to search without headers, so with headers too!
closes #5 and #4 with commit 313ec92 THANKS!


Can't even build it :(

It gives out errors like "too many arguements for public! or something" for line 57,58 in xena.kt

@punkjj can you please download the project again, the build is now passing.

@Jonatino Now I'm getting a error "variable "mousepointerGlow" is never used , xena.kt like 175"

@punkjj that's just a warning. You can ignore that.


Remove as2

Summary
This pull request removes the AS1 and AS2 options from the onboarding college dropdown, replacing these with one "Arts and Sciences" option. Upon onboarding submission, whether the user is actually enrolled in AS1 or AS2 is determined by checking to entrance year the user recorded.
Test Plan
The new "Arts and Sciences" option:

Whether you're in AS1 or AS2 is inferred on onboarding submission:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Tested on preview url with entrance year before Fall 2020, Fall 2020, and after Fall 2020 and they all look good! 😄 The bug I noticed during dev meeting is when adding another major and clicking finish on the onboarding, navigating to the new added major's header doesn't display anything below it (steps and screenshots are below). It's fine after refreshing the page (progress bar + requirements show up), so I'm not sure how big of a problem this is. I tried the same steps on prod, and it seems to have expected behavior (progress bar + requirements show up after finishing edit profile w/o having to refresh).

Thank you for the detailed testing plan!! However, I still am not able to reproduce this :(

@einc could you try to see if you can replicate it?
@jessfeng did you try this on the dev webapp? If not could you see if it fails there, because if so, it is probably unrelated to my changes.

Additionally, I fixed the bug @einc pointed out during the meeting that A&S was still labeled pre-post 2020 in the reqs bar! This PR should be good to go now besides this potential bug.


Al Azhar University

Al Azhar University

#23721 add Al Azhar University

@AhmedHamdyAmeen Pull request merged. Please start requesting the licenses in about an hour, to let the changes to propagate through our system. Thank you.

Hello @philipto, Thank you for your support.


Suggestion: For each wallet there should be a file: [wallet-name]/index.ts

I might be jumping the gun here but eventually the array in data.ts will just get too large -> harder to maintain.
I think we can create a folder called wallets, then whenever a contributor wants to add a wallet, they can create an index file like this: wallets/trust-wallet/index.ts
Then all the wallet files will be exported to wallets/index.ts as:
// wallets/index.ts
import TrustWallet from "./trust-wallet";
import ZerionWallet from "./zerion-wallet";

export const allWallets = [TrustWallet, ZerionWallet, ...];

I thought the same :) The unique file system was a way to get started quickly but agree that it's becoming increasingly difficult to maintain as numbers grow - will add this to the to-do

Implemented this now - much better structure, thanks for suggesting!


Added removedTrom and addedTo socket verb actions

Hi,
i added the two socket verbs addedTo and removedFrom and did some small code cleanups. Would be really cool if could get it merged asap. :)

:+1:

Done! Thanks a lot!

 Would you create a release for it and publish the npm package?


improve node-controller query efficiency

What this PR does / why we need it:
improve node-controller query efficiency and convert the http status code using http package
Special notes for your reviewer:
Does this PR introduce a user-facing change?

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

Comparison is base (11803a7) 28.41% compared to head (b01a0f9) 28.41%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1304   +/-   ##
=======================================
  Coverage   28.41%   28.41%
=======================================
  Files          34       34
  Lines        3079     3079
=======================================
  Hits          875      875
  Misses       2089     2089
  Partials      115      115

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

@peng9808 can you have a look?

lgtm


Create post-link script to install Julia deps

Attempts to add a post-link script to install PySR's julia dependencies.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Addresses #38.

cc @ngam @mkitti

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The top level meta key azure is unexpected

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks, all suggestions implemented. Let's see if it works

Since the deps are changing, do I need to merge a new version of PySR (i.e., creating a v0.10.1), or is updating the build number enough?

Sounds good to me. If there's no response this week I will plan to merge this next weekend.
Also: I relaxed the Julia version requirement to 1.7.*.

@ngam that issue by itself is fine - that's how the normal PyJulia install process works - it installs PyCall.jl if it can't import it.
However, the other issues look to be new: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=551157&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d&l=683 from julia >1.7.1

pysr.install() is doing the following:

Install PyCall.jl using PyJulia's install() command. Code
Pkg.activate("pysr-0.10.0", shared=true) - (This should create a new env). Code
Pkg.add("SymbolicRegression"). Code
Pkg.instantiate(). Code


fw version size changed for d500

Tracked by: RSDEV-838
Needs to be aligned with FW

Where can I find the spec for the HKR FW version numbering?


fix: added some css padding to various screens

Resource card fix -
Before:

After:

Added padding -
Before: (no padding when the dropdown opens) Bucket creation page

After: (now there is padding after the dropdown opens) Bucket creation page

Here earlier we were using hardcoded pixels, now made it relative.

/assign @SanjalKatiyar

can u add screenshots ??

/test mcg-ms-console-e2e-aws

@debjyoti-pandit Can you also add Before screenshots maybe? Just to see how padding changed.

/assign @avanthakkar

/lgtm

/approve

/approve


Delay in search results

Describe the bug
Delay In search results
How to Reproduce
Steps to reproduce the behavior:

In the search bar type anything
Tap search
3.See the delay in loading results

If applicable, please include information about any settings that may be relevant to this issue (e.g. selected theme, auto clear option, etc).
Expected behavior
I am facing delay in search results. For example if I search for a place , for few seconds (7-8) there appears a blank white screen. It is quite strange as ut doesn't happens with any other browse that I use
Smartphone (please complete the following information):

DDG App Version: (5.75.1)
App Info
Device: [Motorola G9]
OS: [Android 10]
If applicable, add screenshots to help explain your problem.

Just to confirm, when you say it doesn't happen with any other browser, you mean using another browser and doing the same search with duckduckgo, right?
Thanks

Yup. When i use search in duckduckgo android app i get blank screen for few seconds before the result is displayed. But if search the same thing in another browser i do not face any such issue

@Amanraj13 could you please share a gif/small video?

Well.. i uninstalled the app. I will need to install it again

If it is possible for you please share a video. It will help people to understand your reported issue more clearly.

@Amanraj13 If you manage to unistall the app again, please provide us a gif or a video, it wil be very helpful to understand the issue. Thanks.

Closing this issue as we haven't received any similar feedback or bug reports similar to the described on this issue. We can't reproduce the error. Thanks.


Sklearn upgrade > 1.3

Describe changes
I fixed #2216 to achieve that sklearn version > 1.3 is required to be installed.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[ ] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

The changes in tests/conftest.py on lines 133 and 139 are just formatting changes that happen when I save the file in VSCode, I haven't changed anything inside it.
The change in tests/conftest.py is that I removed the deprecated execfile which was replaced with File in the new version.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@coderabbitai review

@Vishal-Padia please run the formatting script to fix the linting failures.

I'll run the formatting scripts to fix the linting failures.

I am getting an error while running this zenml integration install -y -i feast
I'll just solve it and then run the formatting scripts

Just run pip install -e ".[server,dev]" and that should be enough to run the formatting scripts.

okay I ran that command and many libraries got installed.

I pushed after running the formatting scripts.

@strickvl I got a notification saying that the run got cancelled. Some of the tests failed

https://github.com/zenml-io/zenml/actions/runs/7503345737?pr=2271 here you can view the progress of the tests. It's ok so far!

Hey, look all the checks passed

Nice @Vishal-Padia! Just waiting for @avishniakov's approval and we'll get it merged!


React 18 - @shopify/react-testing

Description
Base: #2241
Fixes https://github.com/Shopify/web/issues/63209
Fixes #2252
We're upgrading @shopify/react-testing to support React 18 while maintaining backwards compatibility with React 17. This takes a couple of steps:

We need to introduce a test matrix and namespaced npm packages so that we can test against both 17 & 18 and ensure we maintain backwards compatibility
We need to update to the new createRoot API, and provide a shim for it for React 17
We need to use the flushSync API within our custom act wrapper in order to help ease the transition to React 18 for shopify/web.

On flushSync
Our Web project has a lot of code that relies on some very specific ordering of promise resolution and state updates and thousands of tests break as a result of the new batching of state updates in React 18. Wrapping these act()s in flushSync helps make that a much easier update.
In the future, what we'd like to do is to transition web over to better testing and component structuring practices which removes the need for flushSync. To do that, we'll probably make an option to opt-out of flushSync on every act and run that as a test suite for Web that we know will be failing and then incrementally fix the tests that are failing because of it.

Type of change

[ ]  Patch: Bug (non-breaking change which fixes an issue)
[x] react-testing Minor: New feature (non-breaking change which adds functionality)
[ ]  Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[ ] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

Tested here against web running React 17 using a beta release of this PR in order to show that this version could be installed into web without error prior to upgrading to React 18: https://buildkite.com/shopify/web-ci-builder/builds/487393


Added drop down symbol for MORE

Fixes:  None
Description
I have added the dropdown symbol and when it is hovered it rotates 180 degrees and also, I have added the book recommendations to the more section so that it looks nice.
Issue Number: #840 added

[x ] Bug fix
[x ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[x ] I have made this from my own
[ ] I have taken help from some online resourses
[x ] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[x ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x ] My changes generate no new warnings
[x ] I have tested the changes thoroughly before submitting this pull request.
[x ] I have provided relevant issue numbers, screenshots, and videos after making the changes.

Fixes:  None
Description
I have added the dropdown symbol and when it is hovered it rotates 180 degrees and also, I have added the book recommendations to the more section so that it looks nice.
Issue Number: #840 added

[x ] Bug fix
[x ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[x ] I have made this from my own
[ ] I have taken help from some online resourses
[x ] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[x ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x ] My changes generate no new warnings
[x ] I have tested the changes thoroughly before submitting this pull request.
[x ] I have provided relevant issue numbers, screenshots, and videos after making the changes.

solve conflicts and make another PR