text:
Inconsistent condition generation

Almost each time when I call paket.exe install it change my paket.lock file from

CommonServiceLocator (1.3) - framework: >= net40, monoandroid, portable-net45+wp80+wpa81+win+MonoAndroid10+xamarinios10, xamarinios, winv4.5, winv4.5.1, wpv8.1, wpv8.0, sl50

to

CommonServiceLocator (1.3) - framework: >= net40, monoandroid, portable-net45+wp80+wpa81+win+MonoAndroid10+xamarinios10, xamarinios, winv4.5, wpv8.0, sl50

and vise versa.
What actually change most of my csproj files from

When Condition="($(TargetFrameworkIdentifier) == 'WindowsPhoneApp') Or ($(TargetFrameworkIdentifier) == '.NETCore') Or ($(TargetFrameworkIdentifier) == '.NETFramework' And ($(TargetFrameworkVersion) == 'v4.0' Or $(TargetFrameworkVersion) == 'v4.5' Or $(TargetFrameworkVersion) == 'v4.5.1' Or $(TargetFrameworkVersion) == 'v4.5.2' Or $(TargetFrameworkVersion) == 'v4.5.3' Or $(TargetFrameworkVersion) == 'v4.6' Or $(TargetFrameworkVersion) == 'v4.6.1')) Or ($(TargetFrameworkIdentifier) == 'Silverlight' And $(TargetFrameworkVersion) == 'v5.0') Or ($(TargetFrameworkIdentifier) == 'WindowsPhone' And $(TargetFrameworkVersion) == 'v8.0') Or ($(TargetFrameworkIdentifier) == 'MonoAndroid') Or ($(TargetFrameworkIdentifier) == 'Xamarin.iOS') Or ($(TargetFrameworkProfile) == 'Profile5') Or ($(TargetFrameworkProfile) == 'Profile6') Or ($(TargetFrameworkProfile) == 'Profile7') Or ($(TargetFrameworkProfile) == 'Profile14') Or ($(TargetFrameworkProfile) == 'Profile19') Or ($(TargetFrameworkProfile) == 'Profile24') Or ($(TargetFrameworkProfile) == 'Profile31') Or ($(TargetFrameworkProfile) == 'Profile32') Or ($(TargetFrameworkProfile) == 'Profile37') Or ($(TargetFrameworkProfile) == 'Profile42') Or ($(TargetFrameworkProfile) == 'Profile44') Or ($(TargetFrameworkProfile) == 'Profile47') Or ($(TargetFrameworkProfile) == 'Profile49') Or ($(TargetFrameworkProfile) == 'Profile78') Or ($(TargetFrameworkProfile) == 'Profile84') Or ($(TargetFrameworkProfile) == 'Profile92') Or ($(TargetFrameworkProfile) == 'Profile102') Or ($(TargetFrameworkProfile) == 'Profile111') Or ($(TargetFrameworkProfile) == 'Profile136') Or ($(TargetFrameworkProfile) == 'Profile147') Or ($(TargetFrameworkProfile) == 'Profile151') Or ($(TargetFrameworkProfile) == 'Profile157') Or ($(TargetFrameworkProfile) == 'Profile158') Or ($(TargetFrameworkProfile) == 'Profile225') Or ($(TargetFrameworkProfile) == 'Profile240') Or ($(TargetFrameworkProfile) == 'Profile255') Or ($(TargetFrameworkProfile) == 'Profile259') Or ($(TargetFrameworkProfile) == 'Profile328') Or ($(TargetFrameworkProfile) == 'Profile336') Or ($(TargetFrameworkProfile) == 'Profile344')"

to

When Condition="($(TargetFrameworkIdentifier) == '.NETFramework' And ($(TargetFrameworkVersion) == 'v4.0' Or $(TargetFrameworkVersion) == 'v4.5' Or $(TargetFrameworkVersion) == 'v4.5.1' Or $(TargetFrameworkVersion) == 'v4.5.2' Or $(TargetFrameworkVersion) == 'v4.5.3' Or $(TargetFrameworkVersion) == 'v4.6' Or $(TargetFrameworkVersion) == 'v4.6.1')) Or ($(TargetFrameworkIdentifier) == '.NETCore' And $(TargetFrameworkVersion) == 'v4.5') Or ($(TargetFrameworkIdentifier) == 'Silverlight' And $(TargetFrameworkVersion) == 'v5.0') Or ($(TargetFrameworkIdentifier) == 'WindowsPhone' And $(TargetFrameworkVersion) == 'v8.0') Or ($(TargetFrameworkIdentifier) == 'MonoAndroid') Or ($(TargetFrameworkIdentifier) == 'Xamarin.iOS') Or ($(TargetFrameworkProfile) == 'Profile5') Or ($(TargetFrameworkProfile) == 'Profile6') Or ($(TargetFrameworkProfile) == 'Profile7') Or ($(TargetFrameworkProfile) == 'Profile14') Or ($(TargetFrameworkProfile) == 'Profile19') Or ($(TargetFrameworkProfile) == 'Profile24') Or ($(TargetFrameworkProfile) == 'Profile31') Or ($(TargetFrameworkProfile) == 'Profile32') Or ($(TargetFrameworkProfile) == 'Profile37') Or ($(TargetFrameworkProfile) == 'Profile42') Or ($(TargetFrameworkProfile) == 'Profile44') Or ($(TargetFrameworkProfile) == 'Profile47') Or ($(TargetFrameworkProfile) == 'Profile49') Or ($(TargetFrameworkProfile) == 'Profile78') Or ($(TargetFrameworkProfile) == 'Profile84') Or ($(TargetFrameworkProfile) == 'Profile92') Or ($(TargetFrameworkProfile) == 'Profile102') Or ($(TargetFrameworkProfile) == 'Profile111') Or ($(TargetFrameworkProfile) == 'Profile136') Or ($(TargetFrameworkProfile) == 'Profile147') Or ($(TargetFrameworkProfile) == 'Profile151') Or ($(TargetFrameworkProfile) == 'Profile157') Or ($(TargetFrameworkProfile) == 'Profile158') Or ($(TargetFrameworkProfile) == 'Profile225') Or ($(TargetFrameworkProfile) == 'Profile240') Or ($(TargetFrameworkProfile) == 'Profile255') Or ($(TargetFrameworkProfile) == 'Profile259') Or ($(TargetFrameworkProfile) == 'Profile328') Or ($(TargetFrameworkProfile) == 'Profile336') Or ($(TargetFrameworkProfile) == 'Profile344')"

and vise versa.
It's annoying. Why this happens?
my paket.dependencies file
source https://nuget.org/api/v2

nuget CommandLineParser
nuget DocumentFormat.OpenXml
nuget DotNetZip
nuget MahApps.Metro 1.1.2
nuget MahApps.Metro.Resources 0.4.0
nuget Microsoft.Composition
nuget MvvmLightLibs
nuget NLog
nuget SharpShell
nuget WpfAnimatedGif
nuget squirrel.windows
nuget TaskScheduler

group Build
	source https://nuget.org/api/v2
	nuget FAKE

group Test
	source https://nuget.org/api/v2
	nuget NUnit
	nuget NUnit.Console

My paket.lock file:
NUGET
  remote: https://www.nuget.org/api/v2
  specs:
    CommandLineParser (1.9.71)
    CommonServiceLocator (1.3) - framework: >= net40, monoandroid, portable-net45+wp80+wpa81+win+MonoAndroid10+xamarinios10, xamarinios, winv4.5, wpv8.0, sl50
    DeltaCompressionDotNet (1.0.0)
    DocumentFormat.OpenXml (2.5)
    DotNetZip (1.9.8)
    MahApps.Metro (1.1.2)
    MahApps.Metro.Resources (0.4.0)
      MahApps.Metro (>= 1.0.0)
    Microsoft.Composition (1.0.30)
    Mono.Cecil (0.9.6.1)
    MvvmLightLibs (5.2.0)
      CommonServiceLocator (>= 1.0) - framework: net35, sl40
      CommonServiceLocator (>= 1.3) - framework: >= net40, monoandroid, portable-net45+wp80+wpa81+win+MonoAndroid10+xamarinios10, xamarinios, winv4.5, wpv8.0, sl50
    NLog (4.2.3)
    SharpShell (2.2.0)
    Splat (1.6.2)
    squirrel.windows (1.2.5)
      DeltaCompressionDotNet (>= 1.0.0)
      Mono.Cecil (>= 0.9.6.1)
      Splat (>= 1.6.2)
    TaskScheduler (2.5.16)
    WpfAnimatedGif (1.4.14)

GROUP Build
NUGET
  remote: https://www.nuget.org/api/v2
  specs:
    FAKE (4.22.6)

GROUP Test
NUGET
  remote: https://www.nuget.org/api/v2
  specs:
    NUnit (3.2.0)
    NUnit.Console (3.2.0.1)
      NUnit.ConsoleRunner (3.2.0)
      NUnit.Extension.NUnitProjectLoader (3.2.0)
      NUnit.Extension.NUnitV2Driver (3.2.0)
      NUnit.Extension.NUnitV2ResultWriter (3.2.0)
      NUnit.Extension.VSProjectLoader (3.2.0)
    NUnit.ConsoleRunner (3.2.0)
    NUnit.Extension.NUnitProjectLoader (3.2.0)
    NUnit.Extension.NUnitV2Driver (3.2.0)
    NUnit.Extension.NUnitV2ResultWriter (3.2.0)
    NUnit.Extension.VSProjectLoader (3.2.0)

May it be because MvvmLightLibs has very interesting dependencies?

Can you please create an csproj, paket.dependencies + paket.lock
combination that has that issue? Thx
On Mar 28, 2016 13:42, "Sergey Tihon" notifications@github.com wrote:

May it be because MvvmLightLibs
https://www.nuget.org/packages/MvvmLightLibs/ has very interesting
dependencies?
[image: image]
https://cloud.githubusercontent.com/assets/1197905/14077343/405cbc7c-f4f3-11e5-8b82-48e8eaed312e.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1552#issuecomment-202351350

Here it is https://github.com/sergey-tihon/paket-MvvmLightLibs
When I call

.paket\paket.bootstrapper.exe
.paket\paket.exe install

Using  2.56.1.0

I see

Thx. Will investigate tomorrow.
On Mar 28, 2016 5:58 PM, "Sergey Tihon" notifications@github.com wrote:

Here it is https://github.com/sergey-tihon/paket-MvvmLightLibs
When I call
.paket\paket.bootstrapper.exe
.paket\paket.exe install
Using 2.56.1.0
[image: image]
https://cloud.githubusercontent.com/assets/1197905/14082103/e18c20b0-f516-11e5-845f-657088aa2ae0.png
I see
[image: image]
https://cloud.githubusercontent.com/assets/1197905/14082130/0080fa54-f517-11e5-8a50-772b5501e83f.png
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1552#issuecomment-202457138

Thank you

this is fixed now, but install/update will still change it one more time to a now stable version.

Thank you!

did it work?

paket.exe install changed project files once, but after paket.exe update I see changes again

I think the green one after update is correct and should be stable
On Mar 29, 2016 12:38 PM, "Sergey Tihon" notifications@github.com wrote:

paket.exe install changed project files once, but after paket.exe update
I see changes again
[image: image]
https://cloud.githubusercontent.com/assets/1197905/14105304/71cbbb62-f5b3-11e5-981f-980305ac3ad3.png
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1552#issuecomment-202826581

It looks strange...

True. Can you copy and break the existing Integration test?
On Mar 29, 2016 12:41 PM, "Sergey Tihon" notifications@github.com wrote:

It looks strange...
[image: image]
https://cloud.githubusercontent.com/assets/1197905/14105388/f3d32000-f5b3-11e5-8846-07d91c3e66df.png
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1552#issuecomment-202827375

paket.exe install change it again

Sorry buddy. Please try to create yet another integration test. Will fix
asap
On Mar 29, 2016 12:43 PM, "Sergey Tihon" notifications@github.com wrote:

paket.exe install change it again
[image: image]
https://cloud.githubusercontent.com/assets/1197905/14105425/2a96fd46-f5b4-11e5-9282-8e11f886fa9a.png
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1552#issuecomment-202827909

Here it is #1556

ok, please give it another try

After paket.exe update I see

When I run paket.exe install again - wpav8.1 disappears

Please try with -f. Maybe now it's an issue with your cache

Even after update/install steps I see short package versions in spec

Is it OK?

Making the dependencies requirement with 3 digits is expected and guards you against conflicting responses from multiple source feeds

So 3 digits should be stable

paket.exe install -f:

paket.exe update -f:

project files changes

The next paket.exe install removes wpav8.1 again

The good news is that I probably have repro again #1557

New error (on my machine) is strange ...

Expected string length 515 but was 513. Strings differ at index 86.
Expected: "...\n    CommonServiceLocator (1.3.0) - framework: >= net40, m..."
But was:  "...\n    CommonServiceLocator (1.3) - framework: >= net40, mon..."
---------------------------------------------^

Ahhh, sorry, forgot to prepare scenarioName
I will try to come up with new repro ...

(reverting that change with 3 digits versions)

One more integration test for this issue #1560

Thank you @forki
It works now !!!

authors: forki sergey-tihon

repo: fsprojects/Paket


text:
UPath formatting of empty netloc breaks compatibility

UPath._format_parsed_parts currently drops the netloc portion completely when netloc is empty. This leads to a shortened URI with single slash format.
For example, _format_parsed_parts currently shortens protocol:///path to protocol:/path. This unfortunately breaks compatibility with RFC 3986 format, which is assumed by fsspec and third-party libraries that use it (e.g. pandas). Per RFC 3986, an empty host/authority field can be valid.
UPath should offer an attribute to allow implementations to specify whether empty netloc's are valid or not. In the case where they are valid, it shouldn't treat empty string netloc any differently. Without a flag like this, implementations would need to override _format_parsed_parts to change one line.
I am building a UPath implementation for the boxfs implementation and I have to do just that. Netloc (URI host/authority) doesn't have a meaning in this "protocol", so I plan to leave it blank.

Hi @tehunter
Thanks for opening the issue!
Your suggestion definitely sounds like a useful addition. At some point it would also make sense to normalize upaths URIs to the at-least-2-slash versions by default to be better compatible with fsspec. Although I need to give this a bit more thought together with relative URIs.
My current understanding of RFC 3986 is that protocol:/path uri is within RFC 3986 spec and equivalent to protocol:///path unless we are provided with a specific RFC for the protocol (scheme) (see: rfc3986 Section 3: where hier-part would be path-absolute or below)
For now I would say we should add:
class UPath(...):
    _uri_keep_empty_authority: bool = False

Would you want to implement a PR with the changes? (I'm currently working on python 3.12 support)
Cheers,
Andreas :smiley:

source: gharchive/issue

authors: ap-- tehunter

license: MIT

license_type: permissive

license_source: github-api


text:
duplicated metrics with node_exporter

I see grok-exporter output some go_mem* metrics by default. But all these metrics are already available with node-exporter.
One important point is that some metrics display different help string between grok_exporter and node-exporter. This will get Prometheus to complain the difference.
e.g:
node-exporter: # HELP go_memstats_sys_bytes Number of bytes obtained from system.
grok-exporter: # HELP go_memstats_sys_bytes Number of bytes obtained by system. Sum of all system allocations.
Would you please remove duplicated metrics with node exporter or update the help text string?

A little bit of background for those who find this in their Google searches: The metric go_memstats_sys_bytes is produced by the Prometheus client library for the Go programming language. That means, every exporter written in Go provides this metric. The metric shows the memory consumption of the exporter. This is useful to observe the behavior of the exporter itself, but it does not say anything about the system being monitored.
It's not a duplicate metric. It's just that both the node_exporter and grok_exporter are written in Go, so the both export this metric for observing the exporters' memory consumption.
The reason why there are different HELP messages is that grok_exporter uses an older version of the client library, and the message changed with the newer version used in node_exporter. I updated the client library, so with the next grok_exporter release the HELP messages should be the same. You can safely ignore the Prometheus warning.

authors: fstab kingbyteking

license_source: bigquery


text:
promagent-agent loaded from the system class loader  FAILURE

Command Pass
mvn clean install
ERROR

[INFO] ------------------------------------------------------- [INFO]  T E S T S [INFO] ------------------------------------------------------- [INFO] Running io.promagent.agent.JarFilesTest [INFO] [INFO] Results: [INFO] [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] promagent framework 1.0-SNAPSHOT ................... SUCCESS [  0.434 s] [INFO] promagent-agent loaded from the system class loader  FAILURE [  7.030 s] [INFO] promagent-api API for implementing hooks ........... SKIPPED [INFO] promagent-internal classes shared across deployments SKIPPED [INFO] promagent.war ...................................... SKIPPED [INFO] promagent-maven-plugin 1.0-SNAPSHOT ................ SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 7.578 s [INFO] Finished at: 2018-08-09T18:34:46+02:00 [INFO] ------------------------------------------------------------------------ [ERROR] Java heap space -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError
I am using JAVA8

This is weird. It seems that the build fails because it runs out of memory. I tried a few settings, and even with 32M heap space the build works fine (MAVEN_OPTS="-Xmx32m").
Could you try again? Maybe something else was running on your machine so that you actually ran out of memory.

Please tell me exactly which Java version, Maven version and OS you are using, so I can try to reproduce it. I am using Java 1.8.0_172 and Maven 3.5.4 on macOS.

I can reproduce the error on Windows. It seems to be related to the beta version of Junit5. As a quick workaround, try the following two changes in promagent-framework/pom.xml:

Update the Junit5 version: <junit5.version>5.0.0-RC2</junit5.version> -> <junit5.version>5.2.0</junit5.version>
Remove this dependency:

<dependency>
    <groupId>org.junit.platform</groupId>
    <artifactId>junit-platform-surefire-provider</artifactId>
    <version>${junit5.surefire.version}</version>
</dependency>

I didn't commit this change yet, because I want to make sure that this does not cause any problems with the docker tests on macOS or Linux. But it seems to fix the build issue on Windows.

As Instructed:

It seems you also added <scope>test</scope> in the plugin configuration (the highlighted line in your screen shot). This should be removed.

Thanks, Mate Problem solved.

authors: fstab iankittomar

repo: fstab/promagent


text:
Kade griffith

Fixed bugs, cleaned up code.

Fixed bugs that caused routing to be a little messed up. Merging my own code due to the fact that app won't work as intended unless this request is merged

source: gharchive/pull-request


text:
Detekcija nošenja zaštitnih maski na videu u realnom vremenu korišćenjem kompjuterske vizije

Tim
Vukašin Ocokoljić, sw60/2017
Romana Erdelji, sw58/2017
Milorad Radović, sw67/2017
Asistenti
Dragan Vidaković,
Milica Škipina
Definicija problema
Cilj projekta je detekcija nošenja zaštitnih maski u realnom vremenu. Ulaz u sistem predstavlja video snimak ljudi sa maskama ili bez maski. Izlaz iz sistema je filtriran video snimak, odnosno skup slika,  na kojoj su crvenom bojom uokvireni ljudi koji ne nose masku, a zelenom oni koji je nose.
Motivacija zašto vredi rešavati dati problem
Usled epidemije Korona virusa krajem 2019. godine svet je počeo rapidno da se menja. Iako je veliki broj aktivnosti prešao u online režim rada, još uvek postoje one za koje to nije moguće.
Zaštitne maske, kao način prevencije širenja virusa, postale su jedan od obeležja epidemije. Ljudi su u obavezi da nose maske u zatvorenom, dok ta praksa na otvorenom prostoru još uvek nije zastupljena.
Ukoliko bi zaštitne kamere na ulasku u objekte koristile ovaj softver, te bi se omogućilo prepoznavanje da li se prilikom ulaska u objekat poštuju pravila nošenja zaštitnih maski.
Ovo bi pomoglo u otkrivanju lica koja ne nose masku pri ulasku u objekat, te se naknadno može aktivirati alarm ili na neki drugi način obavestiti dežurno lice. Na taj način softver bi pomogao u zaštiti života i sprečavanju širenja virusa.
Skup podataka
Na linku  se nalazi skup podataka koji bismo koristili ali zbog nedovoljnog broja podataka moramo da ga proširimo.
Na linku  se nalaze podaci koji su već prošli kroz proces augmentacije (na slikama su ljudi bez maske i oni kojima je maska veštački stavljena), te bismo ih korisliti kao dopunu na prvi skup podataka.
Na linku  se nalaze samo lica bez maski gde bismo mi vršili augmentaciju i preradu podataka kao što je urađeno na prethodno opisanom skupu podataka. Potom bismo ih takođe ubacili u skup podataka, ukoliko to bude bilo neophodno za bolje rezultate.
Metodologija
Pre samog rada sa konvolutivnim neuronskim mrežama potrebno je pretprocesirati podatke i tu je potrebno izdvojiti video u skup frejmova odnosno slika na kojima će se dalje raditi treniranje i obeležavanje. Po uzoru na radove koje smo pročitali prilikom traženja literature zaključili smo da bi ovakav sistem mogao biti dizajniran iz dve komponente. Prva komponenta je ekstraktor bitnih osobina koji je baziran na ResNet-50 modelu dubokog učenja. Druga komponenta koja se koristi za detekciju zaštitne maske koja je bazirana na YOLO v2 modelu. Za treniranje bismo koristili dva skupa podataka koji su navedeni iznad. Takođe nakon istraživanja ćemo utvrditi da li možemo da upotrebimo transfer learning, ukoliko pronađemo odgovarajući istreniran model.
Evaluacija
Skup podataka bismo razdvojili na trening skup, validacioni skup i test skup. Nakon treniranja modela na test skupu možemo evaluirati dati model pomoću metrika i zaključiti koja najbolje opisuje model. Metrika koja bi se koristila za evaluaciju uspešnosti verovatno bi bila average precision i log-average miss rate. Pomoću ovih metrika ćemo videti koji optimizacioni algoritam daje najbolju uspešnost. Osim samih metrika pokušali bismo da naš kroz algoritam pustimo demo video snimak i na njemu analiziramo uspešnost samog modela, odnosno broj dobro i loše prepoznatih objekata.

Tim
Vukašin Ocokoljić, sw60/2017
Romana Erdelji, sw58/2017
Milorad Radović, sw67/2017
Asistenti
Dragan Vidaković,
Milica Škipina
Definicija problema
Ulaz u sistem predstavlja slika ljudi sa maskama ili bez maski. Izlaz iz sistema je filtrirana slika na kojoj su crvenom bojom uokvireni ljudi koji ne nose masku, a zelenom oni koji je nose.
Motivacija zašto vredi rešavati dati problem
Usled epidemije Korona virusa krajem 2019. godine svet je počeo rapidno da se menja. Iako je veliki broj aktivnosti prešao u online režim rada, još uvek postoje one za koje to nije moguće.
Zaštitne maske, kao način prevencije širenja virusa, postale su jedan od obeležja epidemije. Ljudi su u obavezi da nose maske u zatvorenom, dok ta praksa na otvorenom prostoru još uvek nije zastupljena.
Ukoliko bi zaštitne kamere na ulasku u objekte koristile ovaj softver, te bi se omogućilo prepoznavanje da li se prilikom ulaska u objekat poštuju pravila nošenja zaštitnih maski.
Ovo bi pomoglo u otkrivanju lica koja ne nose masku pri ulasku u objekat, te se naknadno može aktivirati alarm ili na neki drugi način obavestiti dežurno lice. Na taj način softver bi pomogao u zaštiti života i sprečavanju širenja virusa.
Skup podataka
Na linku se nalazi skup podataka koji bismo koristili ali zbog nedovoljnog broja podataka moramo da ga proširimo.
Na linku se nalaze podaci koji su već prošli kroz proces augmentacije (na slikama su ljudi bez maske i oni kojima je maska veštački stavljena), te bismo ih korisliti kao dopunu na prvi skup podataka.
Na linku se nalaze samo lica bez maski gde bismo mi vršili augmentaciju i preradu podataka kao što je urađeno na prethodno opisanom skupu podataka. Potom bismo ih takođe ubacili u skup podataka, ukoliko to bude bilo neophodno za bolje rezultate.
Metodologija
Po uzoru na radove koje smo pročitali prilikom traženja literature zaključili smo da bi ovakav sistem mogao biti dizajniran iz dve komponente. Prva komponenta je ekstraktor bitnih osobina koji je baziran na ResNet-50 modelu dubokog učenja. Druga komponenta koja se koristi za detekciju zaštitne maske koja je bazirana na YOLO v2 modelu. Za treniranje bismo koristili dva skupa podataka koji su navedeni iznad. Takođe nakon istraživanja ćemo utvrditi da li možemo da upotrebimo transfer learning, ukoliko pronađemo odgovarajući istreniran model.
Evaluacija
Skup podataka bismo razdvojili na trening skup, validacioni skup i test skup. Nakon treniranja modela na test skupu možemo evaluirati dati model pomoću metrika i zaključiti koja najbolje opisuje model. Metrika koja bi se koristila za evaluaciju uspešnosti verovatno bi bila average precision i log-average miss rate. Pomoću ovih metrika ćemo videti koji optimizacioni algoritam daje najbolju uspešnost.

U delu Skup podataka nedostaju spomenuti linkovi.

U delu Skup podataka nedostaju spomenuti linkovi.

Nažalost su nestali linkovi prilikom kopiranja iz dokumenta. Sada su dodati.

Pošto se tim sastoji od tri člana, predlažemo sledeće:

da se projekat proširi tako da radi detekciju na videu
da se tim redukuje na 2 člana ukoliko se funkcionalnost ne bi menjala (da radi detekciju sa slike).

Vašu konačnu odluku (kada je donesete) napišite u sledećem komentaru.

Prihvatamo prvu opciju da se projekat proširi tako da radimo detekciju na videu. Da li je potrebno da menjamo predlog projekta u odnosu na ovu izmenu?

Zamolio bih vas da korigujete predlog projekta u skladu s izmenom.

Poštovani,
Izmenili smo predlog projekta u skladu sa sugestijama.

Tema odobrena.
Ostavite link ka GitHub repozitorijumu projekta.
Srećan rad.

Link ka repozitorijumu: https://github.com/Vukeezy/FaceMaskDetection


text:
Update documentation for the floating point type, expressions and elements of the DSL

[ ] Create a summary on floating point support in Theta akin to bitvectors.md
[ ] Update the description of the CFA formalism in README.md
[ ] Add some example CFAs to showcase the new expressions (also suitable for testing purposes)

I think point number one is optional. It is nice to have a long and detailed description if you have time, but the important thing is to update the CFA formalism readme (point 2). You might just list the available operators/expressions there.

Please see PR #127, I think I covered all important aspects for point 2.

authors: hajduakos leventeBajczi

repo: ftsrg/theta


text:
你们上面的人怎么知道基层的情况呢？

基层不是党员的，一个人也要挂十几个号，要不然哪来那些好看的数据，三天两头催催催，天天活都不少，这是加快我们猝死啊

有些是强制性的，像上面时不时的也要来检查，现在还好取消了排名，不然我们这些不想刷的人会被整天说的。

排名又启用的了哦。是恢复可以看排名的了。

还真是，之前都没注意到排名的

也不怕。只要头头没有三天两天的在群里发排名就好。
总有人要最后一名的吧。

基层不是党员的，一个人也要挂十几个号，要不然哪来那些好看的数据，三天两头催催催，天天活都不少，这是加快我们猝死啊

这个我们用外挂的不是无耻的，最无耻的是强迫下属帮自己刷分的，或者叫亲属朋友代刷的，难道以后要搞人脸识别

难道以后要搞人脸识别

搞人脸识别不还更好了......
尽快落实到每个党员都要做是最好的，能给党员同志们分享一些福报
比起隔壁要死要活的996才哪到哪呢

这个我们用外挂的不是无耻的

哦，你是党员啊，那就真是无耻啊
又不去学技术自制脚本反侦测PR或是自用
认为这个组织没有腐化（或者认为其腐化了却又绥靖之），又反对一个~明面上的~进步党派~夹带皇家私货~的意识形态灌输
前不久还叫我五毛来着
吃个皇粮的官五想绥靖皇室就好好按照要求为皇室服务，进步思想没有，契约精神也没有？

顶层开展学习活动本是好意，而且说实在的，抛开主旋律内容不说，学习强国这个APP其他内容质量本身也是上乘
无奈一级一级下来到最后成了逼基层刷分的活动
妈的我都感觉丢人，好好的东西最后弄成这样，也不知道这个用积分花样考核的馊主意是谁想出来的

repo: fuck-xuexiqiangguo/Fuck-XueXiQiangGuo


text:
显存恒定9G左右

+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.179                Driver Version: 535.179      CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA RTX A5000               Off | 00000000:65:00.0 Off |                  Off |
| 65%   85C    P2             228W / 230W |   9721MiB / 24564MiB |    100%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A     13160      C   python3                                    9716MiB |
+---------------------------------------------------------------------------------------+
该状态下平均30帧/每秒 约2分钟，10秒的视频要20分钟以上，提升显存使用率能否降低时间？

我用 A100 推理也是稳定占用 9G 显存，输出视频 25fps，每秒音频推理2分钟，15s就是半小时，巨慢无比！

太慢了

authors: Tanwei99 jsyqrt piwawa

repo: fudan-generative-vision/hallo


text:
chore(main): release eslint-config-fuf-base 0.4.0

:robot: I have created a release beep boop
0.4.0 (2024-04-03)
Features

vitest-config: add inital vitest config package (d609279)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fuf-stack/ts-project-setup/releases/tag/eslint-config-fuf-base-v0.4.0 :sunflower:

authors: fuf-cavendish toxsick

repo: fuf-stack/ts-project-setup


text:
MPL: 多視点2D姿勢からの3D人体姿勢推定

タイトル: MPL: 多視点2D姿勢からの3D人体姿勢推定
リンク: https://arxiv.org/abs/2408.10805
概要:
2D画像から3D人体姿勢を推定することは、オクルージョンや投影による取得の問題があるため困難です。この課題に対処するために、単一視点と複数視点の両方で、学習ベースのアプローチが広く研究されてきました。しかし、これらの解決策は、トレーニングのための3D姿勢と対になった（複数視点の）「現実世界」の画像が不足しているため、現実世界のケースに一般化することができません。このため、本研究では、大規模で豊富なトレーニングデータセットが存在する2D姿勢推定と、合成2D-3D姿勢ペアからトレーニング可能なTransformerベースのネットワークを用いた2D-to-3D姿勢リフティングを組み合わせることを提案します。実験結果から、2D姿勢を三角測量して得られた3D姿勢と比較して、MPJPE誤差が最大45%減少することが実証されました。フレームワークのソースコードはhttps://github.com/aghasemzadeh/OpenMPL で公開されています。

論文要約
論文要約:  MPL: 多視点2D姿勢からの3D人体姿勢推定

課題:

2D画像から3D人体姿勢を推定することは、奥行き情報がないため難しい。
既存の学習ベースの手法は、現実世界のデータ不足が課題。

提案手法 (MPL):

大規模な2D姿勢データセットを活用。
2D姿勢から3D姿勢への変換には、合成データで学習したTransformerベースのネットワークを使用。

利点:

現実世界のデータ不足を解消。
従来の三角測量ベースの手法と比べて、最大45%の精度向上を実現。

その他:

ソースコードは公開済み。

@yukihiko-fuyuki が以下のラベルを提案し、適用しました：

paper-implementation
3D-scene-representation
pose-estimation

以下の新しいラベルが作成され、適用されました：

pose-estimation

repo: fulfulggg/Information-gathering


text:
🛑 Waddle Penguins Island - API is down

In 72893c9, Waddle Penguins Island - API (https://api.waddlepenguins.me/) was down:

HTTP code: 502
Response time: 220 ms

Resolved: Waddle Penguins Island - API is back up in f196427 after 12 minutes.

repo: fullmoondev/status


text:
Fix string functions bug

main changes:

fix tests and add missing tests
add throwErr
add isNullable
add passesMin
add testRegex
add missing case transformers
fix string functions
update readme

fix tests and add missing tests
add throwErr
add isNullable
add passesMin
add testRegex
add missing case transformers
fix string functions
update README

authors: AmirabbasJ frontendmonster

repo: fullstacksjs/toolbox


text:
Refactored AppBar using flexbox

Used flexbox in app bar which is more reliable

Bonus Refactored svg to SvgIcon
closes #16
closes #17

Awesome, thanks @pantharshit00 !

repo: fus-marcom/franciscan-react


text:
Possibility to shape how bundles are emited

I have a scenario in which I am only loading JS if I am on a specific browser, supporting ES6 with async await. For all other browsers I am disabling the app. It is a corporate app so don't judge.
I can now do:
<script type="text/javascript">
            function isGeneratorSupported() {
                try {
                    eval('(function*(){})()');
                    return true;
                } catch (err) {
                    return false;
                }
            }
            let c = document.getElementById('hiddenContent');
            if (!isGeneratorSupported() || /MSIE \d|Trident.*rv:/.test(navigator.userAgent)) {
                c.style.display = 'block';
            } else {
                $bundles
            }
        </script>

and
WebIndexPlugin({
        template: 'src/client/index.html',
        emitBundles: bundles =>
          bundles
            .map(b => `document.write('<script type="text/javascript" src="${b}"><\\/script>');`)
            .join('\n')
      }),

@tomitrescak ?

authors: nchanged tomitrescak

repo: fuse-box/fuse-box

license: mit


text:
Optimized how the ElementBatcher calculates renderbounds for larger lists

This PR contains:

[x] Changelog
[-] Documentation
[-] Tests

wrong origin

repo: fusetools/fuselibs-public


text:
feat(fusion-cli): add graceful shutdown to start command

This PR proposes to add signal handling to the $ fusion start command. This solves 2 issues:

In a docker container the nodejs process is PID 1 which causes the fusion start command to not stop on SIGINT or SIGTERM. This will make sure fusion actually listens and respects these signals.
fusion start will gracefully exit and allows open connections to finish

 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.

authors: CLAassistant pheew

repo: fusionjs/fusionjs


text:
Add token expiry and logout fn

Closes #228
Closes #216
Adds the logout function that should really just be called to take care of #232 and #158.
Some of the motivations for this approach: https://github.com/fusor/mig-ui/issues/228#issuecomment-506033628
Notably:

We don't want every caller to the client to define token expiry behavior; it should be easy to get a client and the client should default to that behavior

It's desirable to keep the client decoupled from redux. It's likely we'd need to dispatch some router action to move to a new location (/login), but it's questionable the client should be calling redux directly

Think this achieves that.

I saw this break compass tests for inexplicable reasons, so if they still show up in the travis log I'll have to dig into it. I don't believe the errors had anything to do with the PR, so we may have to repair compass or disable it until we have the bandwidth to fix.

repo: fusor/mig-ui


text:
Attach router bug workaround in S5.

Temporary workaround for S5 failing.
When subnet contains host routes, route manager requires the subnet to
contain a router and raiese error when that a router is being attached
to that subnet.
This tempoary fix removes host_routes from subnet info while actual fix
is being worked on.

Discussed with @pkommoju and @DavidLiu506. As this PR is a temporary fix, we are safe to close it as the actual fix has been merged to master.

authors: pkommoju xieus

repo: futurewei-cloud/alcor


text:
Prevent duplicate input overwriting

Ityfuzz uses ConstantHintedMutator and VMStateHintedMutator which apply discovered values directly to the input bytes as a mutation.
This is really nice, but has a flaw when it comes to producing many duplicated values.
Each input is mutated several times under the hood which is controlled by havoc_times (max of 10) and max_stack_pow (max of 128). So each input can be mutated ~1280 times before being executed.
Since ConstantHintedMutator and VMStateHintedMutator completely overwrite the input, all of the prior mutations are wasted. These also have a ~1/5 chance to be selected as the next mutator, so we overwrite all the mutations already performed frequently.
This PR creates a MutatorMetadata object that makes these mutators skip if the input has already had a full overwrite this cycle.
This has the immediate effect of performing much less duplicated runs.
Without PR:

31.6% duplicates vs 68.4% unique values

With PR

21.8% duplicates vs 78.2% duplicates

@plotchy Thanks for your work. Once the conflicts are resolved, this PR can be merged.

authors: jacob-chia plotchy

repo: fuzzland/ityfuzz


text:
개발 환경 셋업 및 개발 방법을 알고싶습니다

깃헙을 처음 사용하는 사람들을 위해 깃헙의 사용법을(linux  기준)
명령어별로 명확하게 알려주는 문서가 필요할 것 같습니다.

올렸습니다.

repo: fuzzythecat/OceanView


text:
Streamline the configuration

The installation of dependencies and setup for Windows has been removed
Instead of uploading all files from the install directory, only specific shared libraries are uploaded now.

Todo: need to check that the artifacts are correctly uploaded

Was it not possible to use Clang-cl instead of cl? libriscv definitely builds and runs complex programs on Clang-cl. It's one of the things I test for each release.
It also builds in MinGW - which is how I build my game client.

Does clang-cl ship with microsoft visual studio?

Yes, it's one of the install options. Same with git (which might be OK to have)

There's three bugs here. One is windows support, the other is failing to upload and a can't compile bug.
So I want to focus on the upload shared library here.
# For the other pr.
    - name: Install Dependencies (Windows)
      if: matrix.config.os == 'windows-latest'
      run: |
        choco upgrade ccache ninja

    - name: Setup MSVC (Windows)
      if: matrix.config.os == 'windows-latest'
      uses: ilammy/msvc-dev-cmd@v1

authors: fire fwsGonzo

repo: fwsGonzo/godot-riscv


text:
Fix mqtt publish

Add missing Time.h
Add missing sprintf to buf before publishing the phase_%d/status

@g3gg0 mind checking if Time.h is correct? I just added all function from Time.ino


text:
Unreliable test for Gitlab

The test for Gitlab seems to fail a lot. There is not much output
Tests run: 29, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 404.681 sec <<< FAILURE! - in io.dockstore.client.cli.GeneralWorkflowET
testManualPublishGitlab(io.dockstore.client.cli.GeneralWorkflowET)  Time elapsed: 0.947 sec  <<< FAILURE!
java.lang.AssertionError: Unexpected call of System.exit(6).

Failed tests:
  GeneralWorkflowET.testManualPublishGitlab Unexpected call of System.exit(6).

Tests run: 158, Failures: 1, Errors: 0, Skipped: 2

Change the test so that it will wait and retry on failure to hopefully reduce how often we get a false positive failure.
(do an exponential back-off or similar) https://docs.aws.amazon.com/general/latest/gr/api-retries.html

Saw this with testDockerhubGitlabManualRegistrationDuplicates too.


text:
fix for process_schemas.py docs

correct the syntax used to create the protocol definitions python script.
Fixes #1329

obsolete, closing...


text:
Feedback: The Worst Function in the World

Do we really need this more complicated problem? Couldn't you just use the colorizer problem on a chain?

I realize you want to use Nesterov's "worst function in the world" but I think you could achieve almost as much drama with a very similar function and slightly different wording.

It seems like the exact same arguments should go through, except a bit cleaner. You loose the observation about the conditioning number, but that feels like a tangent.

This would nicely feed from the laplacian systems section if you had that as a previous section. You could begin this section by saying something like

Earlier, when we talked about the colorizer problem, we observed that wirey graphs cause bad conditioning in our optimization problem. Taking this to its extreme, we can look at a graph consisting of a single path -- a function so badly conditioned that Nesterov called a variant of it "the worst function in the world...

You haven't introduced the term "convex rosenbrock" but use it here:

I believe I've hit all the points here. Can this issue be closed?

authors: colah gabgoh

repo: gabgoh/post--momentum


text:
[PIM-99] 워크스페이스/보드 생성, 수정, 삭제 E2E 테스트 구현

워크스페이스/보드 생성, 수정, 삭제 E2E 테스트 구현
지라 티켓 번호
PIM-99
PR 타입(하나 이상의 PR 타입을 선택해주세요)

[x] 기능 추가
[ ] 기능 삭제
[ ] 버그 수정
[ ] 의존성, 환경 변수, 빌드 관련 코드 업데이트
[x] 리팩토링
[ ] UI 구현 및 변경

구현 내용
1. 워크스페이스 생성, 수정 삭제 E2E 테스트

createWorkspace -> deleteWorkspace
createWorkspace -> updateWorkspace

2. 보드 생성, 수정 삭제 E2E 테스트

createWorkspace -> createBoard -> deleteBoard
createWorkspace(위에서 생성 이미 했으면 안해도 됩니다!) -> createBoard -> createBoard

리뷰 포인트
yarn test:cypress 실행이 잘 되는지 확인해주세요~!

수정했습니다!

테스트가 잘 진행되용 🤩 전체 코드 테스트 할 때, 순서대로 실행이 되지않아서 수정/삭제 부분에서 테스트 실패가 발생하는데 해당 부분은 보드 생성 코드를 추가해서 해결하면 좋을 것 같습니다!

수정 완료 했습니다!

테스트 잘 됩니당 ~~ 회원가입부터 차례로 진행되도록 연결해도 좋을 것 같아요~~!

수정 완료 했습니다!


text:
launch.json

Type: Performance Issue
no code is executing
Extension version: 2.0.3
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.73GB (2.01GB free)

Process Argv
--crash-reporter-id acffc7dc-7636-412d-8d1d-e6bdff76ddaf

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	    98	  1656	code main
    0	   181	  1264	   window (launch.json - html - Visual Studio Code)
    0	    27	 14272	   crashpad-handler
    0	    40	 14664	   utility-network-service
    0	   129	 15668	   extension-host
    0	    84	 26356	     "C:\Users\Punith Reddy\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node "c:\Users\Punith Reddy\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=15668
    0	   190	 16856	   gpu-process
    0	    87	 17532	   issue-reporter
    0	   101	 23740	   shared-process
    0	    82	  8792	     "C:\Users\Punith Reddy\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node "c:\Users\Punith Reddy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork" ms-vscode.pwa-node "{\"common.vscodemachineid\":\"4d0d5f9cde73f90ec914ca17a6c0ea24f89abbd7537f1c4f6cc63e1dd64bede3\",\"common.vscodesessionid\":\"9719d5f5-f2d7-4208-93d7-7e45b50528ca1676966065400\"}" 0c6ae279ed8443289764825290e4f9e2-1a736e7c-1324-4338-be46-fc2a58ae4d14-7255
    0	    79	 19716	     ptyHost
    0	    66	 15124	       C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "try { . \"c:\Users\Punith Reddy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\contrib\terminal\browser\media\shellIntegration.ps1\" } catch {}"
    0	     6	 26012	       console-window-host (Windows internal process)
    0	    77	 25680	     fileWatcher

Workspace Info
|  Window (launch.json - html - Visual Studio Code)
|    Folder (html): 5 files
|      File types: json(1) css(1) html(1) js(1)
|      Conf files: launch.json(1)
|      Launch Configs: chrome;

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaac:30438847
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1:30587005
2e4cg342:30602488
pyind779:30662992
89544117:30613380
pythonsymbol12:30657548
a9j8j154:30646983

Hello @punith36, thanks for reporting this. Is this still happening with v2.0.4?


text:
Fixes #296 Cannot find valid target when multiple drop types specified

Fixes the issue from #296 where drop types are compared by reference only. If both drop types are arrays, an additional array comparison is performed.

This fix happens to work, but this is not the underlying issue.
Description in https://github.com/gaearon/react-dnd/issues/296#issuecomment-165277413 is incorrect:

Although the types are not changed occurs initialization below and takes some time.

JavaScript is single threaded (from user’s perspective) so a race condition is not the problem here. The problem is in DnD Core removing handlers immediately which can cause problems during nested updates: for example, a hover() action causing removeTarget().
The solution would be to change HandlerRegistry in dnd-core to delay deleting old handlers until the next tick.

Fixed in dnd-core via f1893a64965d2a294611d4d0449e5250a58308e0.

authors: gaearon mahlero

repo: gaearon/react-dnd


text:
abigen: fix abi generated from hardhat

Motivation
fix #683
Solution
Use parsed api as api_str, not original input.

Think this change breaks a few things?

This seems to have diverged from the original purpose of the PR, suspect because it's based against lerencao:master? Closing and we can have a new PR from a branch w/o conflicting changes, if possible please!

Oh, sorry for that.
I will fire another PR to address this.

Thanks~!

authors: gakonst lerencao

repo: gakonst/ethers-rs


text:
WebGL2 获取深度图错误

webgl1 正确

it's not supported  to sample depthTexture filterable  in webgl2 : https://github.com/KhronosGroup/OpenGL-API/issues/84
you can set depthTexture as depthTexture.filterMode = TextureFilterMode.Point

@GuoLei1990 give warning in engine?

it's not a bug, please use correct filterMode in OpenGL

authors: yuufen zhuxudong

repo: galacean/engine


text:
[WIP] tutorial "Introduction to Python"

First version of the tutorial, based on the Carpentries tutorials: https://swcarpentry.github.io/python-novice-inflammation/, https://swcarpentry.github.io/python-novice-gapminder/ .
Submitted for the Gallantries project @mcmaniou, @fpsom

xref https://github.com/gallantries/organisation/issues/3
I'll have a look at this! But it's great that you kicked it off @mcmaniou! I think in the long term we might want to make those lessons a bit more modular, but for now having it in one file is great.
I started to renew my university's curriculum based on the same but I was starting to think about making some changes to the swcarpentry. Maybe we'd like to discuss these in our gallantries meeting:

the entry point for my students is folks who have never had a programming course, maybe it would make sense to have two entrypoints, one for "I know another programming language" and one for "I don't know any programming languages", with the bulk of it remaining the same
Including more exercises for students with faded, incomplete examples (since it's a jupyter notebook.)

That's something we could think about discussing (gtn + gallantries) as well? is it better to have the tutorial in the GTN where we can have nice tip / solution boxes / etc? Or would it make more sense to have it in the format of a notebook they load into jupyter where the code could be runnable without the copy/pasting step. I recently had fairly good success with https://github.com/aaren/notedown to convert markdown documents into notebooks (automatically marking the python code blocks as runnable cells) which could make this blending of tutorial/notebook a bit more smooth.

None of the above discussion is a blocker for this PR, btw. I attempted to push a commit to fix the frontmatter and allow building but this PR is from the main branch, which does not allow maintainers to push fixes, so, here are the changes that should be made:
rename from topics/introduction/tutorials/python-basics/Introduction_to_Python.md
rename to topics/introduction/tutorials/python-basics/tutorial.md
index 991bdc28c7..559172f15e 100644
--- a/topics/introduction/tutorials/python-basics/Introduction_to_Python.md
+++ b/topics/introduction/tutorials/python-basics/tutorial.md
@@ -3,9 +3,9 @@ layout: tutorial_hands_on

 title: Introduction to Python
 level: Introductory
-zenodo_link: ""
-requirements: ""
-follow_up_training:""
+zenodo_link: https://zenodo.org/record/3477564
+requirements: []
+follow_up_training: []

 questions:
 - How can I run Python programs using Galaxy?
@@ -17,11 +17,8 @@ objectives:
 - Learn the fundamentals of programming in Python
 - Use the scientific libraries pandas, numpy and matplolib to explore tabular datasets

-time_estimation: ""
-key_points:""
-
-supporting_material:
-- [Dataset](https://zenodo.org/record/3477564/files/annotatedDEgenes.tabular)
+time_estimation: 8H
+key_points: []

@mcmaniou could you please add yourself to the Contributors file? I think that will fix the linting errors.

@mcmaniou could you please add yourself to the Contributors file? I think that will fix the linting errors.

Thank you for the quick response. I hope everything works now

Looks good. I'll probably open a PR to work on the GTN specific formatting changes that would be needed since that's a lot of work.

@hexylena In the next few days, I will split the tutorial in three modules (basics, advanced-numpy-pandas and plotting) and then push another commit. Could you please postpone the merging step till then?

Absolutely :)

Another thought: We could also retain the original structure from the carpentries? Rather than merging them into three bigger modules. It'd probably make it easier to keep up to date with anything the carpentries improves in the future?

This tutorial is a mix of the two Carpentries tutorials and does not follow their original structure. But it could be split into more modules. For example:

data types - variables
lists - strings - type conversion
built-in Python functions
conditionals
loops
functions
libraries - numpy
pandas
plotting
Would that help?

Yeah! That sounds good.

FWIW, I think that splitting in into so small modules, might make it more difficult for learners to actually follow. Plus, some modules will end up being tiny, at least in comparison to other tutorials in GTN.
In the case of the three, slightly larger modules, we'll be still referencing the relevant Carpentries lessons, but at the same time we might be updating these independently.
That being said, if you'd think that having the 9 tutorial files that @mcmaniou listed, I won't argue too much against. :)

at least in comparison to other tutorials in GTN.

I'm not so worried about that, there's room for variety.
I don't know. On one hand it seems like it'll be easier to maintain if they're smaller (just diff this file vs carpentries to see if we want their updates) but there's a good point about following all of them is generally what you'll do (maybe a problem to be solved by learning paths)

@shiltemann @bebatut not sure if either of you have an opinion here?

Since no one else has comments, I think we go with your proposal @fpsom @mcmaniou, I think I'm alone in thinking it would be easier. Sorry for the delay!

:) I highly doubt that you are alone in thinking this - my main argument is that, because the content has been adapted from the carpentries lessons, any updates from that side won't be as easy (or automat-able) to propagate here...

Oh no worries! It's the worst season for those :(

No worries @mcmaniou!! It happened to me too, there's too much going on lately :( This looks fantastic.
The instructions for fixing the branch are a bit complicated, you can either do it yourself or you could add me to your repository as a collaborator and I can do them for you? Whatever works for you.

How to rebase your branch
Rebase against the main branch (I think since you're on a main branch it's a bit more complicated, I can suggest the following instructions)
git checkout -b python-tutorials # Create a new branch from the current status of the `main` branch
git push # Push the new branch to your github fork
git checkout main # Swap back to main
git remote -v # This will print a list of remotes, please double check that there is one set for the 'upstream' of https://github.com/galaxyproject/training-material.git. If there is not, run the next commented out command
# git remote add upstream https://github.com/galaxyproject/training-material.git
git fetch upstream
git reset --hard upstream/main # This will make your main branch match the GTN's current main branch
git checkout python-tutorials # Now we can start rebasing
git rebase upstream/main # Rebases it against main so the new `data-science` folder will be available

After you've done that could you move the python tutorials into the new data science topic? Something like this should be ok
git mv topics/introduction/tutorials/python* topics/data-science/tutorials/

And once you've done all that, you can edit this pr (pencil icon at the top) to change the source branch to be your new python branch.
I'm sorry for the whole complicated dance

@hexylena I don't think I can change the source branch in the pr, only the base branch. It looks like I should perform all the steps you described and then create a new pr. I hope I am wrong though

Oh, shoot, you're right! I thought you could change the source branch, hmm. Ok, then yes, could you do that and create a new PR?

Yes, I will do that rignt now and name it: [WIP] tutorial "Data Science - Introduction to Python".

authors: fpsom hexylena mcmaniou

repo: galaxyproject/training-material


text:
Sentinel 5P to panoply

Turorial on how to download Sentinel 5P with a Copernicus openeo notebook and then visualise those data with Panoply.

Give your pull request a good title

e.g. "Fix typo in ansible-galaxy tutorial" or "Add new transcriptomics tutorial covering a new sequencing technology"

Describe your changes in detail, list anything you still need some help with or things that are still TODO
Check that your images are allowed to be re-hosted by the GTN!
Still working on it? Make it a Draft pull request

Once it is ready, choose Ready for Review
Then the automated tests will run and we will know to review and merge it

The last thing not going through is the test-data part.

Thank you @hexylena !!


text:
suggest make fix for new tool

documentation tweak
Installation sequence for tool-installers

[ ] Test using @galaxybot test this
[ ] Inspect CI output for expected changes
[ ] Deploy using @galaxybot deploy this if test install was successful
[ ] Merge this PR

thanks @fubar2 !

repo: galaxyproject/usegalaxy-tools


text:
what if I have already installed redis, Rabbitmq, memcached before?

what if I have already installed redis, Rabbitmq, memcached before? Do I need to change the docker-compse.yml?
I run the container, but it seems will never finished:
The log just stays at this part:
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:32 ===
rabbitmq_1   | accepting AMQP connection <0.344.0> (172.27.0.2:35436 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.354.0> (172.27.0.2:35444 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.363.0> (172.27.0.2:35448 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.372.0> (172.27.0.2:35450 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.381.0> (172.27.0.2:35454 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.384.0> (172.27.0.2:35456 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.387.0> (172.27.0.2:35458 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.390.0> (172.27.0.2:35460 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.417.0> (172.27.0.2:35462 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.426.0> (172.27.0.2:35464 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.437.0> (172.27.0.2:35466 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.446.0> (172.27.0.2:35468 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.455.0> (172.27.0.2:35470 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.464.0> (172.27.0.2:35472 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.473.0> (172.27.0.2:35474 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.482.0> (172.27.0.2:35476 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.491.0> (172.27.0.2:35478 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.500.0> (172.27.0.2:35480 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.509.0> (172.27.0.2:35482 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.518.0> (172.27.0.2:35484 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.527.0> (172.27.0.2:35486 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.536.0> (172.27.0.2:35488 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.545.0> (172.27.0.2:35490 -> 172.27.0.4:5672)

BELOW is the entire log:

tarting dockerzulip_rabbitmq_1 ...
Starting dockerzulip_memcached_1 ...
Starting dockerzulip_rabbitmq_1
Starting dockerzulip_zulip_1 ...
Starting dockerzulip_memcached_1
Starting dockerzulip_zulip_1
Starting dockerzulip_redis_1 ...
Starting dockerzulip_redis_1
Starting dockerzulip_database_1 ...
Starting dockerzulip_database_1 ... done
Attaching to dockerzulip_zulip_1, dockerzulip_redis_1, dockerzulip_rabbitmq_1, dockerzulip_memcached_1, dockerzulip_database_1
zulip_1      | === Begin Initial Configuration Phase ===
zulip_1      | Preparing and linking the uploads folder ...
redis_1      | Starting redis-server...
zulip_1      | Prepared and linked the uploads directory.
zulip_1      | Executing nginx configuration ...
zulip_1      | Nginx configuration succeeded.
redis_1      |                 _._
redis_1      |            _.-``__ ''-._
redis_1      |       _.-``    `.  `_.  ''-._           Redis 3.0.6 (00000000/0) 64 bit
redis_1      |   .-`` .-```.  ```\/    _.,_ ''-._
redis_1      |  (    '      ,       .-`  | `,    )     Running in standalone mode
zulip_1      | Exectuing certificates configuration...
redis_1      |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
redis_1      |  |    `-._   `._    /     _.-'    |     PID: 1
redis_1      |   `-._    `-._  `-./  _.-'    _.-'
redis_1      |  |`-._`-._    `-.__.-'    _.-'_.-'|
zulip_1      | Certificates configuration succeeded.
redis_1      |  |    `-._`-._        _.-'_.-'    |           http://redis.io
zulip_1      | Setting database configuration ...
redis_1      |   `-._    `-._`-.__.-'_.-'    _.-'
redis_1      |  |`-._`-._    `-.__.-'    _.-'_.-'|
zulip_1      | Setting key "DATABASES", type "array" in file "/home/zulip/deployments/current/zproject/settings.py".
redis_1      |  |    `-._`-._        _.-'_.-'    |
redis_1      |   `-._    `-._`-.__.-'_.-'    _.-'
redis_1      |       `-._    `-.__.-'    _.-'
redis_1      |           `-._        _.-'
redis_1      |               `-.__.-'
redis_1      |
zulip_1      | Setting key "REMOTE_POSTGRES_HOST", type "string" in file "/etc/zulip/settings.py".
redis_1      | 1:M 23 Apr 12:03:20.693 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
zulip_1      | Setting key "REMOTE_POSTGRES_SSLMODE", type "string" in file "/etc/zulip/settings.py".
redis_1      | 1:M 23 Apr 12:03:20.693 # Server started, Redis version 3.0.6
zulip_1      | Database configuration succeeded.
redis_1      | 1:M 23 Apr 12:03:20.693 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1      | 1:M 23 Apr 12:03:20.693 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1      | 1:M 23 Apr 12:03:20.693 * DB loaded from disk: 0.000 seconds
redis_1      | 1:M 23 Apr 12:03:20.693 * The server is now ready to accept connections on port 6379
redis_1      | 1:M 23 Apr 12:03:20.693 * The server is now ready to accept connections at /var/run/redis/redis.sock
zulip_1      | Setting Zulip secrets ...
zulip_1      | Secrets already generated/existing.
zulip_1      | Secret found for "rabbitmq_password".
zulip_1      | Secret found for "email_password".
zulip_1      | Secret found for "secret_key".
zulip_1      | Linking secrets from data dir to etc zulip  ...
zulip_1      | Linked existing secrets from data dir to etc zulip.
zulip_1      | Zulip secrets configuration succeeded.
zulip_1      | Activating authentication backends ...
zulip_1      | Setting key "AUTHENTICATION_BACKENDS", type "array" in file "/etc/zulip/settings.py".
zulip_1      | Adding authentication backend "EmailAuthBackend".
zulip_1      | Authentication backend activation succeeded.
zulip_1      | Executing Zulip configuration ...
zulip_1      | Setting key "EXTERNAL_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "EMAIL_HOST", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1      | Setting key "ALLOWED_HOSTS", type "array" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "NOREPLY_EMAIL_ADDRESS", type "string" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "ZULIP_ADMINISTRATOR", type "string" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "REDIS_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "RABBITMQ_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "EMAIL_HOST_USER", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1      | Setting key "DEFAULT_FROM_EMAIL", type "string" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "MEMCACHED_LOCATION", type "string" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "EMAIL_USE_SSL", type "bool" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1      | Setting key "ADMIN_DOMAIN", type "string" in file "/etc/zulip/settings.py".
zulip_1      | Setting key "EMAIL_USE_TLS", type "bool" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1      | Setting key "EMAIL_PORT", type "integer" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1      | Zulip configuration succeeded.
zulip_1      | Auto backup enabled.
zulip_1      | === End Initial Configuration Phase ===
zulip_1      | === Begin Bootstrap Phase ===
zulip_1      | Waiting for database server to allow connections ...
database_1   | LOG:  database system was interrupted; last known up at 2018-04-23 11:32:44 UTC
database_1   | LOG:  database system was not properly shut down; automatic recovery in progress
database_1   | LOG:  invalid record length at 0/1C34D48
database_1   | LOG:  redo is not required
database_1   | LOG:  MultiXact member wraparound protections are now enabled
database_1   | LOG:  autovacuum launcher started
database_1   | LOG:  database system is ready to accept connections
zulip_1      | .(Re)creating database structure ...
zulip_1      | Setting up the database, schema and user ...
database_1   | ERROR:  role "zulip" already exists
database_1   | STATEMENT:  CREATE USER zulip;
zulip_1      | ERROR:  role "zulip" already exists
zulip_1      | ALTER ROLE
database_1   | ERROR:  database "zulip" already exists
database_1   | STATEMENT:  CREATE DATABASE zulip OWNER=zulip;
zulip_1      | ERROR:  database "zulip" already exists
database_1   | ERROR:  schema "zulip" already exists
database_1   | STATEMENT:  CREATE SCHEMA zulip AUTHORIZATION zulip;
zulip_1      | ERROR:  schema "zulip" already exists
zulip_1      | Creating tsearch_extras extension ...
database_1   | FATAL:  password authentication failed for user "postgres"
database_1   | DETAIL:  User "postgres" has no password assigned.
database_1   | 	Connection matched pg_hba.conf line 95: "host all all all md5"
zulip_1      | psql: FATAL:  password authentication failed for user "postgres"
zulip_1      | Database structure recreated.
zulip_1      | Bootstrapping RabbitMQ ...
zulip_1      | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
zulip_1      | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_HOST
zulip_1      | + RABBITMQ_HOST=rabbitmq
zulip_1      | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
zulip_1      | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_USERNAME
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:23 ===
rabbitmq_1   | Starting RabbitMQ 3.5.5 on Erlang 18.1
rabbitmq_1   | Copyright (C) 2007-2015 Pivotal Software, Inc.
rabbitmq_1   | Licensed under the MPL.  See http://www.rabbitmq.com/
rabbitmq_1   |
rabbitmq_1   |               RabbitMQ 3.5.5. Copyright (C) 2007-2015 Pivotal Software, Inc.
rabbitmq_1   |   ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
rabbitmq_1   |   ##  ##
rabbitmq_1   |   ##########  Logs: tty
rabbitmq_1   |   ######  ##        tty
rabbitmq_1   |   ##########
rabbitmq_1   |               Starting broker...
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:23 ===
rabbitmq_1   | node           : rabbit@zulip-rabbit
rabbitmq_1   | home dir       : /var/lib/rabbitmq
rabbitmq_1   | config file(s) : /etc/rabbitmq/rabbitmq.config
rabbitmq_1   | cookie hash    : GV+nrYKFBanPWZTyha8flg==
rabbitmq_1   | log            : tty
rabbitmq_1   | sasl log       : tty
rabbitmq_1   | database dir   : /var/lib/rabbitmq/mnesia/rabbit@zulip-rabbit
zulip_1      | + RABBITMQ_USERNAME=zulip
zulip_1      | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
zulip_1      | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_PASSWORD
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:24 ===
rabbitmq_1   | Memory limit set to 12828MB of 32071MB total.
zulip_1      | + RABBITMQ_PASSWORD=zulip
zulip_1      | + sudo rabbitmqctl -n rabbitmq delete_user zulip
zulip_1      | Error: unable to connect to node rabbitmq@4ad22389d7ad: nodedown
zulip_1      |
zulip_1      | DIAGNOSTICS
zulip_1      | ===========
zulip_1      |
zulip_1      | attempted to contact: [rabbitmq@4ad22389d7ad]
zulip_1      |
zulip_1      | rabbitmq@4ad22389d7ad:
zulip_1      |   * connected to epmd (port 4369) on 4ad22389d7ad
zulip_1      |   * epmd reports: node 'rabbitmq' not running at all
zulip_1      |                   no other nodes on 4ad22389d7ad
zulip_1      |   * suggestion: start the node
zulip_1      |
zulip_1      | current node details:
zulip_1      | - node name: 'rabbitmq-cli-118@4ad22389d7ad'
zulip_1      | - home dir: /var/lib/rabbitmq
zulip_1      | - cookie hash: zeflNrF5gIbWqWe2i1PUIQ==
zulip_1      |
zulip_1      | + true
zulip_1      | + sudo rabbitmqctl -n rabbitmq delete_user zulip
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:24 ===
rabbitmq_1   | Disk free limit set to 50MB
zulip_1      | Error: unable to connect to node rabbitmq@4ad22389d7ad: nodedown
zulip_1      |
zulip_1      | DIAGNOSTICS
zulip_1      | ===========
zulip_1      |
zulip_1      | attempted to contact: [rabbitmq@4ad22389d7ad]
zulip_1      |
zulip_1      | rabbitmq@4ad22389d7ad:
zulip_1      |   * connected to epmd (port 4369) on 4ad22389d7ad
zulip_1      |   * epmd reports: node 'rabbitmq' not running at all
zulip_1      |                   no other nodes on 4ad22389d7ad
zulip_1      |   * suggestion: start the node
zulip_1      |
zulip_1      | current node details:
zulip_1      | - node name: 'rabbitmq-cli-231@4ad22389d7ad'
zulip_1      | - home dir: /var/lib/rabbitmq
zulip_1      | - cookie hash: zeflNrF5gIbWqWe2i1PUIQ==
zulip_1      |
zulip_1      | + true
zulip_1      | + sudo rabbitmqctl -n rabbitmq delete_user guest
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:25 ===
rabbitmq_1   | Limiting to approx 1048476 file handles (943626 sockets)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:25 ===
rabbitmq_1   | FHC read buffering:  ON
rabbitmq_1   | FHC write buffering: ON
zulip_1      | Error: unable to connect to node rabbitmq@4ad22389d7ad: nodedown
zulip_1      |
zulip_1      | DIAGNOSTICS
zulip_1      | ===========
zulip_1      |
zulip_1      | attempted to contact: [rabbitmq@4ad22389d7ad]
zulip_1      |
zulip_1      | rabbitmq@4ad22389d7ad:
zulip_1      |   * connected to epmd (port 4369) on 4ad22389d7ad
zulip_1      |   * epmd reports: node 'rabbitmq' not running at all
zulip_1      |                   no other nodes on 4ad22389d7ad
zulip_1      |   * suggestion: start the node
zulip_1      |
zulip_1      | current node details:
zulip_1      | - node name: 'rabbitmq-cli-343@4ad22389d7ad'
zulip_1      | - home dir: /var/lib/rabbitmq
zulip_1      | - cookie hash: zeflNrF5gIbWqWe2i1PUIQ==
zulip_1      |
zulip_1      | + true
zulip_1      | + sudo rabbitmqctl -n rabbitmq add_user zulip zulip
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:25 ===
rabbitmq_1   | Priority queues enabled, real BQ is rabbit_variable_queue
zulip_1      | Error: unable to connect to node rabbitmq@4ad22389d7ad: nodedown
zulip_1      |
zulip_1      | DIAGNOSTICS
zulip_1      | ===========
zulip_1      |
zulip_1      | attempted to contact: [rabbitmq@4ad22389d7ad]
zulip_1      |
zulip_1      | rabbitmq@4ad22389d7ad:
zulip_1      |   * connected to epmd (port 4369) on 4ad22389d7ad
zulip_1      |   * epmd reports: node 'rabbitmq' not running at all
zulip_1      |                   no other nodes on 4ad22389d7ad
zulip_1      |   * suggestion: start the node
zulip_1      |
zulip_1      | current node details:
zulip_1      | - node name: 'rabbitmq-cli-456@4ad22389d7ad'
zulip_1      | - home dir: /var/lib/rabbitmq
zulip_1      | - cookie hash: zeflNrF5gIbWqWe2i1PUIQ==
zulip_1      |
zulip_1      | RabbitMQ bootstrap succeeded.
zulip_1      | Executing Zulip first start init ...
zulip_1      | First Start Init not needed. Continuing.
zulip_1      | Migrating Zulip to new version ...
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:25 ===
rabbitmq_1   | msg_store_transient: using rabbit_msg_store_ets_index to provide index
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:25 ===
rabbitmq_1   | msg_store_persistent: using rabbit_msg_store_ets_index to provide index
rabbitmq_1   |
rabbitmq_1   | =WARNING REPORT==== 23-Apr-2018::12:03:25 ===
rabbitmq_1   | msg_store_persistent: rebuilding indices from scratch
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:26 ===
rabbitmq_1   | started TCP Listener on [::]:5672
rabbitmq_1   |  completed with 0 plugins.
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:26 ===
rabbitmq_1   | Server startup complete; 0 plugins started.
zulip_1      | Operations to perform:
zulip_1      |   Apply all migrations: analytics, auth, confirmation, contenttypes, sessions, sites, social_django, zerver
zulip_1      | Running migrations:
zulip_1      |   No migrations to apply.
zulip_1      | Zulip migration succeeded.
zulip_1      | Post setup scripts execution ...
zulip_1      | No post-setup.d folder found. Continuing.
zulip_1      | === End Bootstrap Phase ===
zulip_1      | === Begin Run Phase ===
zulip_1      | Starting Zulip using supervisor with "/etc/supervisor/supervisord.conf" config ...
zulip_1      |
zulip_1      | 2018-04-23 12:03:27,861 CRIT Supervisor running as root (no user in config file)
zulip_1      | 2018-04-23 12:03:27,862 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
zulip_1      | 2018-04-23 12:03:27,862 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
zulip_1      | 2018-04-23 12:03:27,862 WARN Included extra file "/etc/supervisor/conf.d/zulip.conf" during parsing
zulip_1      | 2018-04-23 12:03:27,862 WARN Included extra file "/etc/supervisor/conf.d/zulip_db.conf" during parsing
zulip_1      | Unlinking stale socket /var/run/supervisor.sock
zulip_1      | 2018-04-23 12:03:28,174 INFO RPC interface 'supervisor' initialized
zulip_1      | 2018-04-23 12:03:28,175 CRIT Server 'unix_http_server' running without any HTTP authentication checking
zulip_1      | 2018-04-23 12:03:28,205 INFO supervisord started with pid 1
zulip_1      | 2018-04-23 12:03:29,208 INFO spawned: 'zulip-django' with pid 567
zulip_1      | 2018-04-23 12:03:29,211 INFO spawned: 'zulip-tornado' with pid 568
zulip_1      | 2018-04-23 12:03:29,214 INFO spawned: 'process-fts-updates' with pid 569
zulip_1      | 2018-04-23 12:03:29,217 INFO spawned: 'cron' with pid 570
zulip_1      | 2018-04-23 12:03:29,220 INFO spawned: 'nginx' with pid 571
zulip_1      | 2018-04-23 12:03:29,222 INFO spawned: 'zulip_events_message_sender-0' with pid 572
zulip_1      | 2018-04-23 12:03:29,225 INFO spawned: 'zulip_events_message_sender-1' with pid 573
zulip_1      | 2018-04-23 12:03:29,228 INFO spawned: 'zulip_events_message_sender-2' with pid 574
zulip_1      | 2018-04-23 12:03:29,230 INFO spawned: 'zulip_events_message_sender-3' with pid 575
zulip_1      | 2018-04-23 12:03:29,233 INFO spawned: 'zulip_events_feedback_messages' with pid 576
zulip_1      | 2018-04-23 12:03:29,235 INFO spawned: 'zulip_deliver_enqueued_emails' with pid 577
zulip_1      | 2018-04-23 12:03:29,238 INFO spawned: 'zulip_events_slow_queries' with pid 578
zulip_1      | 2018-04-23 12:03:29,240 INFO spawned: 'zulip_events_user_presence' with pid 579
zulip_1      | 2018-04-23 12:03:29,242 INFO spawned: 'zulip_events_invites' with pid 580
zulip_1      | 2018-04-23 12:03:29,244 INFO spawned: 'zulip_events_outgoing_webhooks' with pid 581
zulip_1      | 2018-04-23 12:03:29,246 INFO spawned: 'zulip_events_signups' with pid 582
zulip_1      | 2018-04-23 12:03:29,248 INFO spawned: 'zulip_events_embedded_bots' with pid 583
zulip_1      | 2018-04-23 12:03:29,249 INFO spawned: 'zulip_events_email_mirror' with pid 584
zulip_1      | 2018-04-23 12:03:29,251 INFO spawned: 'zulip_events_user_activity_interval' with pid 585
zulip_1      | 2018-04-23 12:03:29,253 INFO spawned: 'zulip_events_missedmessage_emails' with pid 586
zulip_1      | 2018-04-23 12:03:29,255 INFO spawned: 'zulip_events_missedmessage_email_senders' with pid 587
zulip_1      | 2018-04-23 12:03:29,256 INFO spawned: 'zulip_events_user_activity' with pid 588
zulip_1      | 2018-04-23 12:03:29,258 INFO spawned: 'zulip_events_deferred_work' with pid 589
zulip_1      | 2018-04-23 12:03:29,259 INFO spawned: 'zulip_events_embed_links' with pid 590
zulip_1      | 2018-04-23 12:03:29,261 INFO spawned: 'zulip_events_missedmessage_mobile_notifications' with pid 591
zulip_1      | 2018-04-23 12:03:29,263 INFO spawned: 'zulip_events_error_reports' with pid 592
zulip_1      | 2018-04-23 12:03:29,265 INFO spawned: 'zulip_events_digest_emails' with pid 593
zulip_1      | 2018-04-23 12:03:29,267 INFO spawned: 'zulip_events_email_senders' with pid 594
zulip_1      | 2018-04-23 12:03:29,269 INFO spawned: 'zulip_deliver_scheduled_messages' with pid 595
zulip_1      | 2018-04-23 12:03:30,860 INFO success: zulip-django entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,860 INFO success: zulip-tornado entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,860 INFO success: process-fts-updates entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,860 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,860 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,860 INFO success: zulip_events_message_sender-0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,861 INFO success: zulip_events_message_sender-1 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,861 INFO success: zulip_events_message_sender-2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,861 INFO success: zulip_events_message_sender-3 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,862 INFO success: zulip_events_feedback_messages entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,862 INFO success: zulip_deliver_enqueued_emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,862 INFO success: zulip_events_slow_queries entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,863 INFO success: zulip_events_user_presence entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,863 INFO success: zulip_events_invites entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,863 INFO success: zulip_events_outgoing_webhooks entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,864 INFO success: zulip_events_signups entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,864 INFO success: zulip_events_embedded_bots entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,865 INFO success: zulip_events_email_mirror entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,865 INFO success: zulip_events_user_activity_interval entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,865 INFO success: zulip_events_missedmessage_emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,866 INFO success: zulip_events_missedmessage_email_senders entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,866 INFO success: zulip_events_user_activity entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,866 INFO success: zulip_events_deferred_work entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,867 INFO success: zulip_events_embed_links entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,867 INFO success: zulip_events_missedmessage_mobile_notifications entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,867 INFO success: zulip_events_error_reports entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,868 INFO success: zulip_events_digest_emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,868 INFO success: zulip_events_email_senders entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1      | 2018-04-23 12:03:30,868 INFO success: zulip_deliver_scheduled_messages entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:32 ===
rabbitmq_1   | accepting AMQP connection <0.344.0> (172.27.0.2:35436 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.354.0> (172.27.0.2:35444 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.363.0> (172.27.0.2:35448 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.372.0> (172.27.0.2:35450 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.381.0> (172.27.0.2:35454 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.384.0> (172.27.0.2:35456 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.387.0> (172.27.0.2:35458 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.390.0> (172.27.0.2:35460 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.417.0> (172.27.0.2:35462 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.426.0> (172.27.0.2:35464 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.437.0> (172.27.0.2:35466 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.446.0> (172.27.0.2:35468 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.455.0> (172.27.0.2:35470 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.464.0> (172.27.0.2:35472 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.473.0> (172.27.0.2:35474 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.482.0> (172.27.0.2:35476 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.491.0> (172.27.0.2:35478 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.500.0> (172.27.0.2:35480 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.509.0> (172.27.0.2:35482 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.518.0> (172.27.0.2:35484 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.527.0> (172.27.0.2:35486 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.536.0> (172.27.0.2:35488 -> 172.27.0.4:5672)
rabbitmq_1   |
rabbitmq_1   | =INFO REPORT==== 23-Apr-2018::12:03:33 ===
rabbitmq_1   | accepting AMQP connection <0.545.0> (172.27.0.2:35490 -> 172.27.0.4:5672)

I accidentally press Ctr +C, and it displayed as below:
^CGracefully stopping... (press Ctrl+C again to force)
Stopping dockerzulip_zulip_1     ... done
Stopping dockerzulip_redis_1     ... done
Stopping dockerzulip_memcached_1 ... done
Stopping dockerzulip_rabbitmq_1  ... done
Stopping dockerzulip_database_1  ... done
then I listed all containers and saw this:
toan@www:~/docker-zulip/docker-zulip$ docker container ls -a
CONTAINER ID        IMAGE                                                 COMMAND                  CREATED             STATUS                        PORTS               NAMES
4ad22389d7ad        quay.io/galexrt/zulip:1.8.0-1                         "/sbin/entrypoint.sh…"   2 hours ago         Exited (0) 26 seconds ago                         dockerzulip_zulip_1
3ba7a77ce4f3        quay.io/sameersbn/redis:latest                        "/sbin/entrypoint.sh"    2 hours ago         Exited (0) 29 seconds ago                         dockerzulip_redis_1
111ef14513e1        quay.io/sameersbn/memcached:latest                    "/sbin/entrypoint.sh…"   2 hours ago         Exited (137) 20 seconds ago                       dockerzulip_memcached_1
d975f0d2f20e        rabbitmq:3.5.5                                        "/docker-entrypoint.…"   2 hours ago         Exited (143) 30 seconds ago                       dockerzulip_rabbitmq_1
3b49b3b0a85e        quay.io/galexrt/postgres-zulip-tsearchextras:latest   "docker-entrypoint.s…"   2 hours ago         Exited (0) 28 seconds ago                         dockerzulip_database_1
Is it true that the container ran well?

This is the log for the database service:
database_1   | LOG:  database system was shut down at 2018-04-24 07:49:23 UTC
database_1   | LOG:  MultiXact member wraparound protections are now enabled
database_1   | LOG:  database system is ready to accept connections
database_1   | LOG:  autovacuum launcher started
database_1   | ERROR:  role "zulip" already exists
database_1   | STATEMENT:  CREATE USER zulip;
database_1   | ERROR:  database "zulip" already exists
database_1   | STATEMENT:  CREATE DATABASE zulip OWNER=zulip;
database_1   | ERROR:  schema "zulip" already exists
database_1   | STATEMENT:  CREATE SCHEMA zulip AUTHORIZATION zulip;
database_1   | FATAL:  password authentication failed for user "postgres"
database_1   | DETAIL:  User "postgres" has no password assigned.
database_1   | 	Connection matched pg_hba.conf line 95: "host all all all md5".
Is this true that the error comes to exist with password authentication for user "postgres"?

@toan2948 It's just saying the user, database, etc already exists.. When using the docker-compose.yml as is provided in this repository, the database, user, etc are already configured, so no postgres superuser access is needed.

Closing because reporter wants to use the containers coming with the default docker-compose.yml.

repo: galexrt/docker-zulip


text:
Cocoapods 0.37.0 + Xcode 6.3 Warning: Multiple build commands for .../config_auto.h

Xcode is warning that config_auto.h is present twice in the Headers Build Phase and unfortunately cannot decide what to do with the fact that one config_auto.h comes from Tesseract and the other from Leptonica. Looking over the extended warning output (below) it becomes clear that both config_auto.h files end up at the same location when built, one presumably overwriting the other.
--verbose
warning: Multiple build commands for output file /Users/ian/Library/Developer/Xcode/DerivedData/Socratic-bayktzfmsafuxtbjfwcckwnwdjug/Build/Products/Debug-iphoneos/Pods-Socratic/TesseractOCR.framework/PrivateHeaders/config_auto.h

@yoiang, are those files different?
As I think those files are auto generated by the configure utility and should contain some target specific macros used in all other library headers. Since the target is the same for Tesseract and Leptonica I believe those 2 headers should be similar. But can you confirm this for me?

@yoiang,  I've tried xCode 7 with cocapods 0.38.2 version.
I couldn't reproduce your issue. Is it still reproduced in your case? Can you give more details?

@kevincon, let's close this.

I have the same issue on cocoapods v0.39 with TesseractOCRiOS v4.0.0

I cannot see this in the most recent commit.
Pls, use a developer version to fix this issue.

When is this fix going live?

@Wolfenberg it seems not being reprodecued in latest commit.

@ws233 I'm using the latest 4.0.0 from CocoaPods (0.39.0) and see this warning

@Wolfenberg, I'm talking about the last commit from the master of the repo.
You are talking about the last Cocoapod release.

Has this issue been resolved? I am facing the same problem.
Build failed:
Showing Recent Messages
:-1: Multiple commands produce '/Users/a608612/Library/Developer/Xcode/DerivedData/LoveInASnap-euozazwrksjcphdlmxledcbrjrmb/Build/Products/Debug-iphonesimulator/TesseractOCRiOS/TesseractOCR.framework/PrivateHeaders/config_auto.h':

Target 'TesseractOCRiOS' (project 'Pods') has copy command from '/Users/a608612/Desktop/OCR_Tutorial_Resources/LoveInASnap/Pods/TesseractOCRiOS/TesseractOCR/include/leptonica/config_auto.h' to '/Users/a608612/Library/Developer/Xcode/DerivedData/LoveInASnap-euozazwrksjcphdlmxledcbrjrmb/Build/Products/Debug-iphonesimulator/TesseractOCRiOS/TesseractOCR.framework/PrivateHeaders/config_auto.h'
Target 'TesseractOCRiOS' (project 'Pods') has copy command from '/Users/a608612/Desktop/OCR_Tutorial_Resources/LoveInASnap/Pods/TesseractOCRiOS/TesseractOCR/include/tesseract/config_auto.h' to '/Users/a608612/Library/Developer/Xcode/DerivedData/LoveInASnap-euozazwrksjcphdlmxledcbrjrmb/Build/Products/Debug-iphonesimulator/TesseractOCRiOS/TesseractOCR.framework/PrivateHeaders/config_auto.h'

authors: Japspre Wolfenberg parthgargava ws233 yoiang


text:
Update FUNDING.yml

Changes

...

Checklist

[x] Read the contribution guide and accept the code of conduct
[ ] Readme (updated or not needed)
[ ] Tests (added, updated or not needed)

Codecov Report

Merging #431 (df83acd) into main (fb63366) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #431   +/-   ##
=======================================
  Coverage   52.52%   52.52%
=======================================
  Files          66       66
  Lines        2056     2056
  Branches      376      376
=======================================
  Hits         1080     1080
  Misses        914      914
  Partials       62       62

authors: codecov-commenter webbertakken

repo: game-ci/unity-builder


text:
Update installation for Brew instructions

@jsingle

Nice - virtualbox can be installed as a cask?

Yessir

authors: jsingle thieman

repo: gamechanger/dusty


text:
⚠ Auth API Endpoint has degraded performance

In 02b4830, Auth API Endpoint (https://auth.roblox.com) experienced degraded performance:

HTTP code: 200
Response time: 1726 ms

Resolved: Auth API Endpoint performance has improved in 848da10.


text:
Method Last resort sets last_move_info incorrectly

https://github.com/gamescomputersplay/minesweeper-solver/blob/a420b1377bbf530eb236f108531ad162a3ebbaad/minesweeper_solver.py#L716
Should be
self.last_move_info = ("Last Resort", None, None)

You are right. Fixed.

repo: gamescomputersplay/minesweeper-solver


text:
[Bug] 鼠标滚轮/滚动条不生效

Please search before asking

[X] I searched in the issues and found nothing similar.

Please read README

[X] I have read the troubleshooting section in the README in detail.

使用的版本
3.11.16
系统 System
win10 LTSC
复现步骤 Reproduce step
存放在分享目录中的视频，如果数量较多，且设置使用potplayer播放时，播放完成关闭播放器，此时云盘中滑动鼠标滚轮，没有反应，拖动右侧滚动条也无反应。必须刷新下或者点别的目录再点回来才能翻滚或者拖动
你看到了什么错误？What errors do you see?
滑动鼠标滚轮，没有反应，拖动右侧滚动条也无反应
你期望看到什么？What did you expect to see?
滚轮滑动时页面相应上移/下移，右侧滚动条可以拖动并且页面也相应上下移动
还有其他的内容吗？Anything else?
No response
你是否愿意提交一份 PR 来修改这个错误？Are you willing to submit a PR?

[ ] 我愿意提供 PR! I'm willing to submit a PR!

3.11.16-fix
修復了

3.11.16-fix 修復了

3.11.6 版本下，当同时进行的下载任务有很多时，在「传输 - 下载中」界面仍然存在这个问题。

authors: SuLingGG gaozhangmin wentlwr

repo: gaozhangmin/aliyunpan


text:
tv版解析配置失败

Please search before asking

[X] I searched in the issues and found nothing similar.

Please read README

[X] I have read the troubleshooting section in the README in detail.

使用的版本
1.1.0
系统 System
安卓
复现步骤 Reproduce step
1.进入app没有任何播放视频
2.配置地址后解析配置失败
你看到了什么错误？What errors do you see?
配置地址后解析配置失败
你期望看到什么？What did you expect to see?
可以播放视频
还有其他的内容吗？Anything else?
No response
你是否愿意提交一份 PR 来修改这个错误？Are you willing to submit a PR?

[X] 我愿意提供 PR! I'm willing to submit a PR!

官方下手，第三方云盘都要钱了你不知道？

官方下手，第三方云盘都没法免费了

tv版不能播放了，版本20240706-1948

发件人: sheepmiee @.>
发送时间: 2024年6月13日 15:30
收件人: gaozhangmin/aliyunpan @.>
抄送: lz198892 @.>; Author @.>
主题: Re: [gaozhangmin/aliyunpan] tv版解析配置失败 (Issue #446)
官方下手，第三方云盘都没法免费了
―
Reply to this email directly, view it on GitHubhttps://github.com/gaozhangmin/aliyunpan/issues/446#issuecomment-2164829173, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BJEAU75J3IHTDN7BRQFSMPTZHFDCPAVCNFSM6AAAAABJGB53W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUHAZDSMJXGM.
You are receiving this because you authored the thread.Message ID: @.***>


text:
Configure Hibernation via boolean in Shoot spec

What this PR does / why we need it:
The current behavior of triggering Gardener to hibernate or wake-up a shoot uses implicit logic. Furthermore, the fact that losing min and max values for the worker pools after hibernating a Shoot is unfortunate. This PR introduces a new field in the Shoot spec allowing to set true/false in order to trigger the hibernation/wake-up. The old behavior does still work but we have to remove this in a future version because we don't to maintain two different approaches.
Which issue(s) this PR fixes:
Fixes #191
Special notes for your reviewer:
none
Release note:
Gardener does now support the `.spec.hibernation.enabled` field in the Shoot specification for triggering hibernation/wake-up. The current behavior (setting `min=max=0` for all worker groups) is still supported but deprecated and will be removed in a future 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.

LGTM

@Adracus @zanetworker We have rebased our branch, addressed and adressed your feedback. Kindly do another review.

LGTM

authors: CLAassistant rfranzke timuthy zanetworker

repo: gardener/gardener


text:
Fix audit policy webhook

How to categorize this PR?

/kind regression
/priority 1
What this PR does / why we need it:
This PR fixes several regressions in the AuditPolicy webhook in GAC (ref #3720) introduced in g/g@v1.20.0:

shoot's were still mutated, even if they were already marked for deletion. When the referenced audit policy was changed during ongoing deletion, this caused the gardenlet to fail removing its finalizer, which in turn caused Shoots to hang in a Deleted Succeeded state forever.
shoot's were validated/mutated, even if the spec didn't change. If for some reason, the referenced audit policy was already gone or change in an invalid manner, this prevents any updates to shoot metadata (e.g. adding the deletion confirmation annotation or removing the finalizer).
create/update requests for shoot's in v1alpha1 fail, because the admission webhook always tries to decode them in version v1beta1
I added some missing unit test cases along the way.

It also fixes one bug in GCM:

when a referenced auditpolicy was updated, GCM is supposed to immediately start a reconciliation for the referencing shoots. It does so by sending an empty patch, relying on the auditpolicy webhook (or resourcereference admission plugin in older versions) to update the resourceVersion field in the ConfigMapRef. However, since https://github.com/gardener/gardener/pull/3116 updating the resourceVersion was only done if the shoot spec changed. This is fixed in GCM now, by explicitly updating the spec with the updated resourceVersion of the audit policy configmap.

Special notes for your reviewer:
Thanks @BeckerMax for your help and 👀 and 🧠 on this.
Release note:

Several regressions related to the `AuditPolicy` validation are fixed.

/assign

/squash

/squash

Let's please keep the commits, they are logically self-contained.
/keep-commits

/lgtm
discussed concerns personally

Thanks to all reviewers!

authors: BeckerMax timebertt