text:
Скласти таймлайн

Скласти список всіх (важливих) життєвих подій, визначних дат, досягнень, періодів, що дали приємний і неприємний досвід, тощо. В цьому конкретному випадку довгих списків не буває, натомість бувають погано згорнуті, тому пакуємо сюди все підряд, а про "лишні" події можна буде промовчати пізніше. Список повинен бути систематизованим і посортованим в такий спосіб, щоб читач швидко зрозумів "паттерн" і міг легко орієнтуватись в просторі і часі цього резюме.

EXPERIENCE
2018 Amongst many fighters of the past was featured in the movie "Ready Player One". Ryu ready always!
2017
United with unknown until then to me Power Rangers to defea resurrected M.Bison.Damn good fighters they are, even not knowing karate ways!
2016
In "Street Fighter V" once and for all erased M.Bison from earth and tamed my inner Evil Ryu. Also spent some time on a side-project, mini-series "Street Fighter: Resurrection".
2014
Filmed in a martial arts tutorial "Street Fighter: Assassin's Fist", revealing to audience forgotten art of Ansatsuken.
2012 The gods of intenet concluded me in the animated movie "Wreck-It Ralph", but rewarded me with a good drink for it!
2008
My evil alter ego sneaked out of control and became a boss in "Street Fighter IV".
2006
Borrowed my famous ripped gi to Soki in "Onimusha: Dawn of Dreams", gods informed me he needed that for the battle.
1998
Defeated M. Bison in "Street Fighter Alpha 2", bastard wanted to use my heroic body for his evil intentions, but retreated with shame. Also this year I encountered Marvel universe in "Marvel vs. Capcom: Clash of Super Heroes" fighter,loyal to my employer, Capcom, of course.
1997
Reunited with Ken, my friend and opponent in "Street Fighter III". Men's friendship works mysteriously. Also helped with Arika project "Street Fighter EX"
1996
Took care of villainous Akuma in "Street Fighter Alpha 2". As a freelance on "Super Puzzle Fighter II Turbo" tried myself in a new genre, puzzle games. Let the wrath of seven heavens come upon these malicious enigmas, never again!
1995
Kept fighting in "Street Fighter Alpha: Warriors' Dreams".
1994 Screened in a movie "Street Fighter", so that the batllesof past would not be forgotten by millenial generation.
1991
Was promoted to "Street Fighter II". Didn't stay there for long, celebrations and office dwelling is not for me!
1987
Started working for Capcom project "Street Fighter". My partner was Ken Masters, the boss'name was Sagat.
PUBLICATIONS
2011 The true and humble story of me under pseudonim Tyler Wilde in an article "The evolution of Ken and Ryu"
2003-2018 For 15 years I have published comic books with Udon Entertainment depicting my adventures, bitter lessons and great victories.

So interesting and inspired.

authors: Olga-Golubova Roma-Chi

repo: Olga-Golubova/homepage


text:
Error when Aniseed not installed explicitly

tomiciccola on discord pointed out that if you don't have Aniseed explicitly installed alongside Conjure you get the following error: conjure.aniseed.macros module not found
This is not intended, Conjure should work totally fine without Aniseed and use the one bundled with the project. I'll get this fixed ASAP.

I can't reproduce this actually, can anyone else?

Wasn't really a bug, but if you want to use the bundled Aniseed Conjure ships with you need to require conjure.aniseed.* prefixed modules, if you want to use the Aniseed plugin you're depending on explicitly you can drop the conjure.* prefix.

source: gharchive/issue

repo: Olical/conjure

license: Unlicense

license_type: permissive

license_source: github-api


text:
Exporting an entire vault with links

I have a vault with lots and lots of atomic notes, interlinked into a big ball of knowledge and thinking (I know you probably do, too).
I'd like to back it up as a physical book. To do that, I'd like to export the whole vault as a PDF, with the following features:

Notes alphabetically sorted by title (case insensitive).
Automatic page numbers.
An automatically-generated ToC referring to notes by page numbers.
An automatically-generated index, by tag, referring to notes by page numbers.
Each individual [[internal wikilink]]`` will have the relevant page number next to it, as [[internal wikilink]] (15)`.
Graphics would be embedded (not a must).
YAML front-matter would be printed as-is, in the context of a note.

I understand this plugin does not do all of this out of the box, but I also know Pandoc is powerful. Has anyone done anything like this using obsidian-pandoc? Is it remotely possible? (I am open to sponsoring this work as a paid open-source project.)

Thank you @transiscodev - this is a project I'm happy to sponsor and support financially. Email me ez@zsa.io and let's talk and see how we can make this happen!

repo: OliverBalfour/obsidian-pandoc

license: MIT


text:
QMake build file

Can you add please qmake build file?

I don't know much about qmake, feel free to submit a PR. Supporting qmake that would to the same as my cmake script would be quite hard since i'm using cmake to download dependencies (QOlm, spdlog, MaterialDesignIcons, ...) and generating source files)
But i would advise you to move to cmake anyway since Qt is also moving to cmake. Have a look at https://github.com/OlivierLDff/QQuickStaticHelloWorld for a very simple qt quick project.
What problem do you encounter with cmake?
You should also check this great guide for modern cmake : https://cliutils.gitlab.io/modern-cmake/

Yes i know,im verry new on cmake
Le lun. 27 juil. 2020 à 06:44, Olivier Le Doeuff notifications@github.com
a écrit :

I don't know much about qmake, feel free to submit a PR. Supporting qmake
that would to the same as my cmake script would be quite hard since i'm
using cmake to download dependencies (QOlm, spdlog, MaterialDesignIcons,
...) and generating source files)
But i would advise you to move to cmake anyway since Qt is also moving to
cmake. Have a look at
https://github.com/OlivierLDff/QQuickStaticHelloWorld for a very simple
qt quick project.
What problem do you encounter with cmake?
You should also check this great guide for modern cmake :
https://cliutils.gitlab.io/modern-cmake/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664152007,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS76BXSE3W3WSG2KUD3R5UO4NANCNFSM4PILWM4Q
.

So what is blocking you on cmake? Do you have a project you want to move to cmake and you can't?

many things,
first Qt creator editor integration,
i use set(QML_IMP...
Not work,
Just one time its work, after restart project no,
I have build many other module and library, i integrate easly with include
.pri
Cmake doest not work with my mvcs2019 it show MSB1001 project file not
found, just mingw and arm
Le lun. 27 juil. 2020 à 06:54, Olivier Le Doeuff notifications@github.com
a écrit :

So what is blocking you on cmake? Do you have a project you want to move
to cmake and you can't?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664156243,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS356BPUCYJSVIMM5OTR5UQBRANCNFSM4PILWM4Q
.

i think you speak french, i can write you with this, because my english is
so bad
Le lun. 27 juil. 2020 à 07:03, Black Enokas abdramanesakone1@gmail.com a
écrit :

many things,
first Qt creator editor integration,
i use set(QML_IMP...
Not work,
Just one time its work, after restart project no,
I have build many other module and library, i integrate easly with include
.pri
Cmake doest not work with my mvcs2019 it show MSB1001 project file not
found, just mingw and arm
Le lun. 27 juil. 2020 à 06:54, Olivier Le Doeuff notifications@github.com
a écrit :

So what is blocking you on cmake? Do you have a project you want to move
to cmake and you can't?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664156243,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS356BPUCYJSVIMM5OTR5UQBRANCNFSM4PILWM4Q
.

Arrives tu à builder Qaterial par example? Ou plus simple mon project QQuickStaticHelloWorld

Oui sans problème,  avec mingw
J'ai meme créé un.autre project et integrer Qaterial
Le lun. 27 juil. 2020 à 07:21, Olivier Le Doeuff notifications@github.com
a écrit :

Arrives tu à builder Qaterial par example? Ou plus simple mon project
QQuickStaticHelloWorld
https://github.com/OlivierLDff/QQuickStaticHelloWorld
[image: helloworldcmake]
https://user-images.githubusercontent.com/17255804/88514270-103dbd80-cfea-11ea-8237-41282250dc03.gif
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664167810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS4BCR6Q7J2TBBE2CB3R5UTHHANCNFSM4PILWM4Q
.

Mais est il pas possibles de generer un lib comme libQaterial qui est seras
directement installé parmi les lib et fonctinneras automatiquement sans
pourtant avoir a integrer Qaterial a chaque project
Le lun. 27 juil. 2020 à 07:24, Black Enokas abdramanesakone1@gmail.com a
écrit :

Oui sans problème,  avec mingw
J'ai meme créé un.autre project et integrer Qaterial
Le lun. 27 juil. 2020 à 07:21, Olivier Le Doeuff notifications@github.com
a écrit :

Arrives tu à builder Qaterial par example? Ou plus simple mon project
QQuickStaticHelloWorld
https://github.com/OlivierLDff/QQuickStaticHelloWorld
[image: helloworldcmake]
https://user-images.githubusercontent.com/17255804/88514270-103dbd80-cfea-11ea-8237-41282250dc03.gif
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664167810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS4BCR6Q7J2TBBE2CB3R5UTHHANCNFSM4PILWM4Q
.

Qaterial.zip
Ok i see what you mean, i haven't done any install target. But you can compile Qaterial as a library without any issue.
Note that in the screen cmake .. works and i don't need to do cmake -DCMAKE_PREFIX_PATH=Path/to/qt because i have an environment variable Qt5_DIR set to C:\Qt\5.15.0\msvc2019_64

[image: image.png]
watch i copy file lib on msvc2019_64 lib directory but not work
Le lun. 27 juil. 2020 à 09:43, Olivier Le Doeuff notifications@github.com
a écrit :

[image: qaterialcompi4]
https://user-images.githubusercontent.com/17255804/88516202-3153dd80-cfed-11ea-8283-921a842efef8.gif
Qaterial.zip
https://github.com/OlivierLDff/Qaterial/files/4980606/Qaterial.zip
Ok i see what you mean, i haven't done any install target. But you can
compile Qaterial as a library without any issue.
Note that in the screen cmake .. works and i don't need to do cmake
-DCMAKE_PREFIX_PATH=Path/to/qt because i have an environment variable
Qt5_DIR set to C:\Qt\5.15.0\msvc2019_64
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664177255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS27FXF54BEZDGIRZPLR5UVY3ANCNFSM4PILWM4Q
.

Have you telegram?
Le lun. 27 juil. 2020 à 09:57, Black Enokas abdramanesakone1@gmail.com a
écrit :

[image: image.png]
watch i copy file lib on msvc2019_64 lib directory but not work
Le lun. 27 juil. 2020 à 09:43, Olivier Le Doeuff notifications@github.com
a écrit :

[image: qaterialcompi4]
https://user-images.githubusercontent.com/17255804/88516202-3153dd80-cfed-11ea-8283-921a842efef8.gif
Qaterial.zip
https://github.com/OlivierLDff/Qaterial/files/4980606/Qaterial.zip
Ok i see what you mean, i haven't done any install target. But you can
compile Qaterial as a library without any issue.
Note that in the screen cmake .. works and i don't need to do cmake
-DCMAKE_PREFIX_PATH=Path/to/qt because i have an environment variable
Qt5_DIR set to C:\Qt\5.15.0\msvc2019_64
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664177255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS27FXF54BEZDGIRZPLR5UVY3ANCNFSM4PILWM4Q
.

Je ne vois pas ton image

[image: image.png]
Le lun. 27 juil. 2020 à 10:00, Olivier Le Doeuff notifications@github.com
a écrit :

Je ne vois pas ton image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664185483,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDSYLLOTWF67VXYZKFKLR5UX3LANCNFSM4PILWM4Q
.

Its just, Application output error, module "Qaterial"" is not installed
Le lun. 27 juil. 2020 à 10:03, Black Enokas abdramanesakone1@gmail.com a
écrit :

[image: image.png]
Le lun. 27 juil. 2020 à 10:00, Olivier Le Doeuff notifications@github.com
a écrit :

Je ne vois pas ton image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664185483,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDSYLLOTWF67VXYZKFKLR5UX3LANCNFSM4PILWM4Q
.

As tu bien fait dans ton main.cpp
qaterial::loadQmlResources(); qaterial::registerQmlTypes();
Le lun. 27 juil. 2020 à 10:04, ssakone notifications@github.com a écrit :

Its just, Application output error, module "Qaterial"" is not installed
Le lun. 27 juil. 2020 à 10:03, Black Enokas abdramanesakone1@gmail.com a
écrit :

[image: image.png]
Le lun. 27 juil. 2020 à 10:00, Olivier Le Doeuff <
notifications@github.com>
a écrit :

Je ne vois pas ton image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664185483>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AJRCDSYLLOTWF67VXYZKFKLR5UX3LANCNFSM4PILWM4Q

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664187282,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDU27DM7F355IGLUHSOLN3R5UYIZANCNFSM4PILWM4Q
.

Regarde le main.cpp du helloworld
https://olivierldff.github.io/Qaterial/Quickstart.html
Le lun. 27 juil. 2020 à 10:05, Olivier Le Doeuff olivier.ldff@gmail.com a
écrit :

As tu bien fait dans ton main.cpp
qaterial::loadQmlResources(); qaterial::registerQmlTypes();
Le lun. 27 juil. 2020 à 10:04, ssakone notifications@github.com a
écrit :

Its just, Application output error, module "Qaterial"" is not installed
Le lun. 27 juil. 2020 à 10:03, Black Enokas abdramanesakone1@gmail.com
a
écrit :

[image: image.png]
Le lun. 27 juil. 2020 à 10:00, Olivier Le Doeuff <
notifications@github.com>
a écrit :

Je ne vois pas ton image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664185483
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AJRCDSYLLOTWF67VXYZKFKLR5UX3LANCNFSM4PILWM4Q

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664187282,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDU27DM7F355IGLUHSOLN3R5UYIZANCNFSM4PILWM4Q
.

Now i have this error when i try compile
[image: image.png]
link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:WINDOWS
"/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls'
version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language=''
processorArchitecture=''" /MANIFEST:embed /OUT:debug\untitled6.exe
@C:\Users\bot\AppData\Local\Temp\untitled6.exe.78072.5375.jom
main.obj : error LNK2019: symbole externe non r‚solu "void __cdecl
qaterial::registerQmlTypes(char const *,unsigned char,unsigned char)"
(?registerQmlTypes@qaterial@@YAXPEBDEE@Z) r‚f‚renc‚ dans la fonction main
main.obj : error LNK2019: symbole externe non r‚solu "void __cdecl
qaterial::loadQmlResources(void)" (?loadQmlResources@qaterial@@YAXXZ)
r‚f‚renc‚ dans la fonction main
debug\untitled6.exe : fatal error LNK1120: 2 externes non r‚solus
jom:
C:\Users\bot\Documents\build-untitled6-Desktop_Qt_5_15_0_MSVC2019_64bit-Debug\Makefile.Debug
[debug\untitled6.exe] Error 1120
jom:
C:\Users\bot\Documents\build-untitled6-Desktop_Qt_5_15_0_MSVC2019_64bit-Debug\Makefile
[debug] Error 2
10:38:28: Le processus "C:\Qt\Tools\Preview\Qt Creator
4.13.0-beta1\bin\jom.exe" s'est terminé avec le code 2.
Le lun. 27 juil. 2020 à 10:06, Olivier Le Doeuff notifications@github.com
a écrit :

Regarde le main.cpp du helloworld
https://olivierldff.github.io/Qaterial/Quickstart.html
Le lun. 27 juil. 2020 à 10:05, Olivier Le Doeuff olivier.ldff@gmail.com
a
écrit :

As tu bien fait dans ton main.cpp
qaterial::loadQmlResources(); qaterial::registerQmlTypes();
Le lun. 27 juil. 2020 à 10:04, ssakone notifications@github.com a
écrit :

Its just, Application output error, module "Qaterial"" is not installed
Le lun. 27 juil. 2020 à 10:03, Black Enokas <abdramanesakone1@gmail.com

a
écrit :

[image: image.png]
Le lun. 27 juil. 2020 à 10:00, Olivier Le Doeuff <
notifications@github.com>
a écrit :

Je ne vois pas ton image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664185483

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AJRCDSYLLOTWF67VXYZKFKLR5UX3LANCNFSM4PILWM4Q

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664187282>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AEDU27DM7F355IGLUHSOLN3R5UYIZANCNFSM4PILWM4Q

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664188035,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS5NIYBLLCZZX63HVMTR5UYO3ANCNFSM4PILWM4Q
.

Je ne vois pas ton image.
J'ai discord si tu veux.

i accidentrly close it

Il faut que tu ais les headers dans ton path d'include, et que tu te link à Qaterial.lib.
Mais je ne sais pas comment faire ça avec qmake. A quoi ressemble ton .pro?

Je pense qu'il faut quelque chose comme ça
LIBS += c:/Qaterial/build/Release/Qaterial.lib
INCLUDEPATH += c:/Qaterial/include`
LIBS += c:/Qaterial/build/_deps/spdlog-build/Release/spdlog.lib
LIBS += c:/Qaterial/build/_deps/qolm-build/Release/QOlm.lib

j'ai deja mis les header, Pour integrer la lib il faut juste que je le
copie dans C:\Qt\5.15.0\msvc2019_64\lib,
Généralement c'est comme sa je fais
Le lun. 27 juil. 2020 à 10:45, Olivier Le Doeuff notifications@github.com
a écrit :

Il faut que tu ais les headers dans ton path d'include, et que tu te link
à Qaterial.lib.
Mais je ne sais pas comment faire ça avec qmake. A quoi ressemble ton .pro?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664207913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS4D62BU3H3BRXPMYC3R5U5ENANCNFSM4PILWM4Q
.

Peut être que ça marche, mais je te d'essayer LIBS += c:/Qaterial/build/Release/Qaterial.lib. Au moins tu devrais avoir un erreur de qmake s'il ne trouve pas la librairie je pense.

sa requiert aussi spdlog.lib, que j'ai deja importé
Le lun. 27 juil. 2020 à 10:48, Black Enokas abdramanesakone1@gmail.com a
écrit :

j'ai deja mis les header, Pour integrer la lib il faut juste que je le
copie dans C:\Qt\5.15.0\msvc2019_64\lib,
Généralement c'est comme sa je fais
Le lun. 27 juil. 2020 à 10:45, Olivier Le Doeuff notifications@github.com
a écrit :

Il faut que tu ais les headers dans ton path d'include, et que tu te link
à Qaterial.lib.
Mais je ne sais pas comment faire ça avec qmake. A quoi ressemble ton
.pro?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#issuecomment-664207913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRCDS4D62BU3H3BRXPMYC3R5U5ENANCNFSM4PILWM4Q
.

My project fille
`QT += quick
CONFIG += c++11
SOURCES +=
main.cpp
RESOURCES += qml.qrc
LIBS += $$PWD/../../Downloads/Qaterial/Qaterial.lib
$$PWD/../../Downloads/Qaterial/spdlog.lib
$$PWD/../../Downloads/Qaterial/QOlm.lib
INCLUDEPATH += E:/homeMusic/Qaterial/include
DEPENDPATH += E:/homeMusic/Qaterial/include
`
	link /NOLOGO /DYNAMICBASE /NXCOMPAT /OPT:REF /INCREMENTAL:NO /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /MANIFEST:embed /OUT:release\untitled6.exe @C:\Users\bot\AppData\Local\Temp\untitled6.exe.79108.500.jom Qaterial.lib(Utils.obj) : error LNK2019: symbole externe non r‚solu "__declspec(dllimport) public: static void __cdecl QQuickStyle::setStyle(class QString const &)" (__imp_?setStyle@QQuickStyle@@SAXAEBVQString@@@Z) r‚f‚renc‚ dans la fonction "void __cdecl Qaterial_loadResources(void)" (?Qaterial_loadResources@@YAXXZ) Qaterial.lib(Utils.obj) : error LNK2019: symbole externe non r‚solu "__declspec(dllimport) public: static void __cdecl QQuickStyle::setFallbackStyle(class QString const &)" (__imp_?setFallbackStyle@QQuickStyle@@SAXAEBVQString@@@Z) r‚f‚renc‚ dans la fonction "void __cdecl Qaterial_loadResources(void)" (?Qaterial_loadResources@@YAXXZ) Qaterial.lib(Utils.obj) : error LNK2019: symbole externe non r‚solu __imp_SetProcessDPIAware r‚f‚renc‚ dans la fonction "void __cdecl dynamic initializer for 'private: static class HighDpiFix HighDpiFix::singleton''(void)" (??__E?singleton@HighDpiFix@@0V1@A@@YAXXZ)
release\untitled6.exe : fatal error LNK1120: 3 externes non r‚solus`

My main.cpp
`#include
#include <Qaterial/Qaterial.hpp>
#include
int main(int argc, char *argv[])
{
QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
QGuiApplication app(argc, argv);

QQmlApplicationEngine engine;
engine.addImportPath("qrc:///");
qaterial::loadQmlResources();
qaterial::registerQmlTypes();

const QUrl url(QStringLiteral("qrc:/main.qml"));
QObject::connect(&engine, &QQmlApplicationEngine::objectCreated,
                 &app, [url](QObject *obj, const QUrl &objUrl) {
    if (!obj && url == objUrl)
        QCoreApplication::exit(-1);
}, Qt::QueuedConnection);
engine.load(url);

return QGuiApplication::exec();

}
`

I made it work
QT += quick quickcontrols2

CONFIG += c++11
SOURCES += HelloWorld.cpp

RESOURCES += HelloWorld.qrc

DEFINES += "QATERIAL_STATIC=1"

LIBS += C:/Users/olivi/Desktop/Qaterial/build/Release/Qaterial.lib
LIBS += C:/Users/olivi/Desktop/Qaterial/build/_deps/spdlog-build/Release/spdlog.lib
LIBS += C:/Users/olivi/Desktop/Qaterial/build/_deps/qolm-build/Release/QOlm.lib
LIBS += User32.lib
INCLUDEPATH += C:/Users/olivi/Desktop/Qaterial/include/
INCLUDEPATH += C:/Users/olivi/Desktop/Qaterial/build/_deps/spdlog-src/include

The problem was that QATERIAL_STATIC wasn't defined. Forgot about it since cmake define it automatically in super build.
Ensuite les QQuickStyle::setFallbackStyle c'est qu'il manque quickcontrols2 comme module
Et User32 c'est parce que j'appelle la focntion set process dpi aware de windows (pour géré les configs avec écran 4K et 1080p)
J'ai utilisé les sources de :
https://github.com/OlivierLDff/Qaterial/tree/master/tools/HelloWorld

Yeah, its work,
Thank you.
please give me your discord.

Mon discord : reivilo1234#0459
Le lun. 27 juil. 2020 à 11:32, ssakone notifications@github.com a écrit :

Closed #55 https://github.com/OlivierLDff/Qaterial/issues/55.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/OlivierLDff/Qaterial/issues/55#event-3588981064, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDU27FUT5ZBGE72SPRPD2DR5VCTXANCNFSM4PILWM4Q
.

authors: OlivierLDff ssakone

repo: OlivierLDff/Qaterial


text:
Navigation

Navigate images to readme file

closed


text:
🛑 Open Science Community Nigeria - API is down

In 4e9198c, Open Science Community Nigeria - API (https://api.oscnigeria.org/status) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Open Science Community Nigeria - API is back up in a2e6b3f after 21 minutes.

repo: OluwaninsolaAO/uptime-monitoring


text:
Peer to peer review 23/12/21

Hi @keroloussamy and @Omar-Muhamad
Congratulations on your advance so far 😃. Here I have some suggestion for you:

In this line of code is unnecessary the use of this expression [...], because you already have the data in form of on an array  in the previous line. https://github.com/Omar-Muhamad/JavaScript-Capston-Project/blob/ba0fbe9d14965bd2a54830120fd5e163bcd55038/src/mealAPI.js#L30-L31 In that way you prevent creating an unnecessary copy of your data.
For maintainability, it would be better to have this big code separated on different dedicated functions: https://github.com/Omar-Muhamad/JavaScript-Capston-Project/blob/ba0fbe9d14965bd2a54830120fd5e163bcd55038/src/mealAPI.js#L11-L35

Happy coding 🍀

Thanks, @williamrolando88 😃

repo: Omar-Muhamad/JavaScript-Capston-Project


text:
Do not show rich presence when nothing is playing

#18
#9

Can you please re add line 174 in screen shot. I removed it by accident.

Okay no problem

source: gharchive/pull-request

authors: Ombrelin mclarence

repo: Ombrelin/plex-rich-presence


text:
CSProj Loading Error

When I try to load a fairly-simple tree of csproj files (private repo, though I can tell you it is a fairly simple port of PowerShell), the following exception is thrown (original, unedited transcript):
Starting OmniSharp server at 11/5/2016, 10:50:13 PM
    Target: /Volumes/Sources/SunburstApps/src/PowerShell

OmniSharp server started wth Mono
    Path: /Users/wjk/.vscode/omnisharp~netcoreapp10/OmniSharp
    PID: 14713

OmniSharp: -s /Volumes/Sources/SunburstApps/src/PowerShell --hostPID 14667 DotNet:enablePackageRestore=false --encoding utf-8 --stdio
[INFORMATION:OmniSharp.Startup] Omnisharp server running using Stdio at location '/Volumes/Sources/SunburstApps/src/PowerShell' on host 14667.
[INFORMATION:OmniSharp#MSBuild] No solution files found in '/Volumes/Sources/SunburstApps/src/PowerShell'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/tools/TypeCatalogGen/TypeCatalogGen.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/tools/Microsoft.PowerShell.ResGen/Microsoft.PowerShell.ResGen.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/tools/Microsoft.PowerShell.BuildDependencies/Microsoft.PowerShell.BuildDependencies.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/System.Management.Automation/System.Management.Automation.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/powershell-win/powershell.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/powershell-unix/powershell.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.WSMan.Runtime/Microsoft.WSMan.Runtime.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.WSMan.Management/Microsoft.WSMan.Management.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.Security/Microsoft.PowerShell.Security.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.PSReadLine/Microsoft.PowerShell.PSReadLine.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.PackageManagement/Microsoft.PowerShell.PackageManagement.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.LocalAccounts/Microsoft.PowerShell.LocalAccounts.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.CoreCLR.Eventing/Microsoft.PowerShell.CoreCLR.Eventing.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.CoreCLR.AssemblyLoadContext/Microsoft.PowerShell.CoreCLR.AssemblyLoadContext.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.ConsoleHost/Microsoft.PowerShell.ConsoleHost.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.Commands.Utility/Microsoft.PowerShell.Commands.Utility.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.Commands.Management/Microsoft.PowerShell.Commands.Management.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PowerShell.Commands.Diagnostics/Microsoft.PowerShell.Commands.Diagnostics.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PackageManagement.NuGetProvider/Microsoft.PackageManagement.NuGetProvider.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PackageManagement.MetaProvider.PowerShell/Microsoft.PackageManagement.MetaProvider.PowerShell.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PackageManagement.CoreProviders/Microsoft.PackageManagement.CoreProviders.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PackageManagement.ArchiverProviders/Microsoft.PackageManagement.ArchiverProviders.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.PackageManagement/Microsoft.PackageManagement.csproj'
[INFORMATION:OmniSharp#ProjectFileInfo] Using toolset 15.0 for '/Volumes/Sources/SunburstApps/src/PowerShell/src/Microsoft.Management.Infrastructure.CimCmdlets/Microsoft.Management.Infrastructure.CimCmdlets.csproj'
[ERROR:OmniSharp.Startup] The project system 'MSBuildProjectSystem' threw exception during initialization.
'System.Management.Automation' is already referenced.
   at Microsoft.CodeAnalysis.Workspace.CheckProjectDoesNotHaveProjectReference(ProjectId fromProjectId, ProjectReference projectReference)
   at Microsoft.CodeAnalysis.Workspace.OnProjectReferenceAdded(ProjectId projectId, ProjectReference projectReference)
   at OmniSharp.MSBuild.MSBuildProjectSystem.UpdateProjectReferences(Project project, IList`1 projectReferences) in /Volumes/Sources/Third-Party/omnisharp-roslyn/src/OmniSharp.MSBuild/MSBuildProjectSystem.cs:line 397
   at OmniSharp.MSBuild.MSBuildProjectSystem.UpdateProject(ProjectFileInfo projectFileInfo) in /Volumes/Sources/Third-Party/omnisharp-roslyn/src/OmniSharp.MSBuild/MSBuildProjectSystem.cs:line 310
   at OmniSharp.MSBuild.MSBuildProjectSystem.Initalize(IConfiguration configuration) in /Volumes/Sources/Third-Party/omnisharp-roslyn/src/OmniSharp.MSBuild/MSBuildProjectSystem.cs:line 91
   at OmniSharp.Startup.Configure(IApplicationBuilder app, IServiceProvider serviceProvider, IOmnisharpEnvironment env, ILoggerFactory loggerFactory, ISharedTextWriter writer, IOmnisharpAssemblyLoader loader, IOptions`1 optionsAccessor) in /Volumes/Sources/Third-Party/omnisharp-roslyn/src/OmniSharp.Host/Startup.cs:line 183
[INFORMATION:OmniSharp.Startup] Configuration finished.
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /currentfilemembersastree: 200 64ms

Several projects reference System.Management.Automation.csproj, both directly and indirectly. (I have to duplicate the references across many different projects because MSBuild <ProjectReference>s are not transitive.) What's strange is that this error only shows up after the very last project is loaded, Microsoft.Management.Infrastructure.CimCmdlets. If it was a problem about the DLL being added to the workspace too many times, it ought to occur at the time it is added the second time (by my observation, that would probably be during the loading of Microsoft.PowerShell.Security.csproj).
I would prepare a PR that prevents the adding of duplicate projects to the workspace, except that I cannot easily write any C# in VSCode right now because of omnisharp-vscode#836 et al. (As a developer, I am very dependent on the correct functioning of my IntelliSense. When it malfunctions, I have a very hard time writing any code at all.)

It appears that a netcoreapp1.0 version of OmniSharp is being used to open .csproj files. This isn't very functional today. It seems like you've downloaded OmniSharp and set the "omnisharp.path" setting in VS Code, correct? If these are standard .csproj proejcts that target a .NET desktop framework you might have more luck downloading a Mono version of OmniSharp instead of the netcoreapp1.0 version for this particular project.

@DustinCampbell I actually forgot to mention that these are Core projects. In addition, yes, I have set the omnisharp.path VSCode setting. The main reason I did this is because if I use the bundled copy of OmniSharp, it emits errors while trying to load the Core csproj files. The same error is given on every project; I have reproduced one below:
[ERROR:OmniSharp#ProjectFileInfo] The "ResolvePackageDependencies" task failed unexpectedly.
System.TypeLoadException: Could not load type 'NuGet.Common.INuGetPathContext' from assembly 'NuGet.Common, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
   at Microsoft.NET.Build.Tasks.ResolvePackageDependencies.get_PackageResolver()
   at Microsoft.NET.Build.Tasks.ResolvePackageDependencies.ResolvePackagePath(LockFileLibrary package)
   at Microsoft.NET.Build.Tasks.ResolvePackageDependencies.GetPackageAndFileDefinitions()
   at Microsoft.NET.Build.Tasks.TaskBase.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__25.MoveNext()

I have built a custom copy of OmniSharp (following these directions) to avoid these errors.

OK. That makes sense. Yeah, that error is going to be expected because that task requires a newer version of NuGet than what is bundled with OmniSharp. You might want to try the new release preview release I just put out https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.5-future-preview1. This includes at least initial support for MSBuild-based .NET Core projects.

Well, that didn't work. I now get this exception on every project:
Microsoft.Build.Exceptions.InvalidToolsetDefinitionException: Error reading the toolset information from the configuration file "System.Configuration (6)". Unrecognized configuration section <startup> ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section <startup> (/Users/wjk/.vscode/extensions/ms-vscode.csharp-1.5.0-future-preview1/bin/omnisharp/MSBuild.dll.config line 6)
  at System.Configuration.ConfigInfo.ThrowException (System.String text, System.Xml.XmlReader reader) [0x00007] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at System.Configuration.SectionGroupInfo.ReadContent (System.Xml.XmlReader reader, System.Configuration.Configuration config, System.Boolean overrideAllowed, System.Boolean root) [0x00170] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at System.Configuration.SectionGroupInfo.ReadRootData (System.Xml.XmlReader reader, System.Configuration.Configuration config, System.Boolean overrideAllowed) [0x00007] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at System.Configuration.Configuration.ReadConfigFile (System.Xml.XmlReader reader, System.String fileName) [0x000ec] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at System.Configuration.Configuration.Load () [0x00052] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at System.Configuration.Configuration.Init (System.Configuration.Internal.IConfigSystem system, System.String configPath, System.Configuration.Configuration parent) [0x00065] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at System.Configuration.Configuration..ctor (System.Configuration.InternalConfigurationSystem system, System.String locationSubPath) [0x0005c] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at System.Configuration.InternalConfigurationFactory.Create (System.Type typeConfigHost, System.Object[] hostInitConfigurationParams) [0x0000e] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at System.Configuration.ConfigurationManager.OpenMappedExeConfiguration (System.Configuration.ExeConfigurationFileMap fileMap, System.Configuration.ConfigurationUserLevel userLevel) [0x00005] in <42f076b78acf4ebd9ea481aca766b25b>:0
  at Microsoft.Build.Evaluation.ToolsetConfigurationReader.ReadApplicationConfiguration () [0x00036] in <1be2c21a97cd402db77c8e905b7fd466>:0
  at Microsoft.Build.Evaluation.ToolsetConfigurationReader.get_ConfigurationSection () [0x00019] in <1be2c21a97cd402db77c8e905b7fd466>:0
   --- End of inner exception stack trace ---
  at Microsoft.Build.Exceptions.InvalidToolsetDefinitionException.Throw (System.Exception innerException, System.String resourceName, System.String[] args) [0x0001b] in <1be2c21a97cd402db77c8e905b7fd466>:0
  at Microsoft.Build.Evaluation.ToolsetConfigurationReader.get_ConfigurationSection () [0x00067] in <1be2c21a97cd402db77c8e905b7fd466>:0
  at Microsoft.Build.Evaluation.ToolsetConfigurationReader+<>c__Iterator0.MoveNext () [0x00024] in <1be2c21a97cd402db77c8e905b7fd466>:0
  at Microsoft.Build.Evaluation.ToolsetReader.ReadEachToolset (System.Collections.Generic.Dictionary`2[TKey,TValue] toolsets, Microsoft.Build.Collections.PropertyDictionary`1[T] globalProperties, Microsoft.Build.Collections.PropertyDictionary`1[T] initialProperties, System.Boolean accumulateProperties) [0x00057] in <1be2c21a97cd402db77c8e905b7fd466>:0
  at Microsoft.Build.Evaluation.ToolsetReader.ReadToolsets (System.Collections.Generic.Dictionary`2[TKey,TValue] toolsets, Microsoft.Build.Collections.PropertyDictionary`1[T] globalProperties, Microsoft.Build.Collections.PropertyDictionary`1[T] initialProperties, System.Boolean accumulateProperties, System.String& msBuildOverrideTasksPath, System.String& defaultOverrideToolsVersion) [0x0000c] in <1be2c21a97cd402db77c8e905b7fd466>:0
  at Microsoft.Build.Evaluation.ToolsetReader.ReadAllToolsets (System.Collections.Generic.Dictionary`2[TKey,TValue] toolsets, Microsoft.Build.Evaluation.ToolsetRegistryReader registryReader, Microsoft.Build.Evaluation.ToolsetConfigurationReader configurationReader, Microsoft.Build.Collections.PropertyDictionary`1[T] environmentProperties, Microsoft.Build.Collections.PropertyDictionary`1[T] globalProperties, Microsoft.Build.Evaluation.ToolsetDefinitionLocations locations) [0x00044] in <1be2c21a97cd402db77c8e905b7fd466>:0
  at Microsoft.Build.Evaluation.ProjectCollection.InitializeToolsetCollection (Microsoft.Build.Evaluation.ToolsetRegistryReader registryReader, Microsoft.Build.Evaluation.ToolsetConfigurationReader configReader) [0x00020] in <1be2c21a97cd402db77c8e905b7fd466>:0
  at Microsoft.Build.Evaluation.ProjectCollection..ctor (System.Collections.Generic.IDictionary`2[TKey,TValue] globalProperties, System.Collections.Generic.IEnumerable`1[T] loggers, System.Collections.Generic.IEnumerable`1[T] remoteLoggers, Microsoft.Build.Evaluation.ToolsetDefinitionLocations toolsetDefinitionLocations, System.Int32 maxNodeCount, System.Boolean onlyLogCriticalEvents) [0x0012b] in <1be2c21a97cd402db77c8e905b7fd466>:0

Whoa -- what OS are you using? OSX?

Also, could you share one of the project files?

Yeah, OSX. Here is a sample project file, as well.

Hmmm... this works for me on OSX (Sierra) with a newly created .NET Core project using the latest CLI. The project isn't all that different:
<Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" />

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp1.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Compile Include="**\*.cs" />
    <EmbeddedResource Include="**\*.resx" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NETCore.App">
      <Version>1.0.1</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.NET.Sdk">
      <Version>1.0.0-alpha-20161104-2</Version>
      <PrivateAssets>All</PrivateAssets>
    </PackageReference>
  </ItemGroup>

  <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
</Project>

And I'm scratching my head a bit at why System.Configuration might throw. The MSBuild.dll.config file should look like the following and I don't see anything controversial there. Hmmm...
<?xml version="1.0" encoding="utf-8"?>
  <configuration>
    <configSections>
      <section name="msbuildToolsets" type="Microsoft.Build.Evaluation.ToolsetConfigurationSection, Microsoft.Build, Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
    </configSections>
    <startup useLegacyV2RuntimeActivationPolicy="true">
      <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6" />
    </startup>
    <runtime>
      <DisableFXClosureWalk enabled="true" />
      <generatePublisherEvidence enabled="false" />
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Framework" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
          <bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="15.1.0.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
          <bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="15.1.0.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Conversion.Core" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
          <bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="15.1.0.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Tasks.Core" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
          <bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="15.1.0.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Utilities.Core" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
          <bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="15.1.0.0" />
        </dependentAssembly>
        <dependentAssembly>a
          <assemblyIdentity name="Microsoft.Build.Engine" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
          <bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="15.1.0.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Conversion.Core" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
          <bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="15.1.0.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Activities.Build" culture="neutral" publicKeyToken="31bf3856ad364e35" />
          <bindingRedirect oldVersion="4.0.0.0" newVersion="15.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="XamlBuildTask" culture="neutral" publicKeyToken="31bf3856ad364e35" />
          <bindingRedirect oldVersion="4.0.0.0" newVersion="15.0.0.0" />
        </dependentAssembly>
      </assemblyBinding>
    </runtime>
    <!-- To define one or more new toolsets, add an 'msbuildToolsets' element in this file. -->
    <msbuildToolsets default="15.0">
      <toolset toolsVersion="15.0">
        <property name="MSBuildRootWorkaround704" value="$([MSBuild]::GetCurrentExecutableDirectory())" />
        <!-- See https://github.com/Microsoft/msbuild/issues/704 -->
        <property name="MSBuildToolsPath" value="." />
        <property name="MSBuildToolsPath32" value="$(MSBuildToolsPath)" />
        <property name="MSBuildToolsPath64" value="$(MSBuildToolsPath)\amd64" />
        <property name="MSBuildRuntimeVersion" value="4.0.30319" />

        <property name="TargetFrameworkRootPathSearchPathsOSX" value="/Library/Frameworks/Mono.framework/External/xbuild-frameworks/" />
        <projectImportSearchPaths>
          <searchPaths os="windows">
            <property name="MSBuildExtensionsPath" value="$(MSBuildProgramFiles32)\MSBuild"/>
            <property name="MSBuildExtensionsPath32" value="$(MSBuildProgramFiles32)\MSBuild"/>
            <property name="MSBuildExtensionsPath64" value="$(MSBuildProgramFiles32)\MSBuild"/>
          </searchPaths>

          <searchPaths os="osx">
            <property name="MSBuildExtensionsPath" value="/Library/Frameworks/Mono.framework/External/xbuild/"/>
            <property name="MSBuildExtensionsPath32" value="/Library/Frameworks/Mono.framework/External/xbuild/"/>
            <property name="MSBuildExtensionsPath64" value="/Library/Frameworks/Mono.framework/External/xbuild/"/>
          </searchPaths>
        </projectImportSearchPaths>
      </toolset>
    </msbuildToolsets>
  </configuration>

I can't find the MSBuild.exe.config file. Where would it be located? Furthermore, I am using a copy of Mono installed using Homebrew, not from any official Mono or Xamarin installer. Therefore, /Library/Frameworks/Mono.framework doesn’t exist on my system. However, seeing as OmniSharp downloads its own private copy of Mono, this shouldn't affect anything.

It's MSBuild.dll.config in the MSBuild xplat builds.
Yeah, I wouldn't expect that to affect anything. It shouldn't actually be looking there for anything anyway.

Yeah, but where would I find that on my system? I want to verify that its contents match the example above. In addition, updating .NET CLI (to version 1.0.0-preview4-004071) doesn’t change anything.

According to the exception you got, it should be in /Users/wjk/.vscode/extensions/ms-vscode.csharp-1.5.0-future-preview1/bin/omnisharp/MSBuild.dll.config

I got a repro

BTW, my MSBuild.dll.config exactly matches yours.

FYI, I'm getting closer on this. I'll let you know when I have a solution

All right I've got a solution. I need to package it up again and provide you with instructions on how to try again once it's ready.

OK. If you still have the preview installed, try the following:

Close Visual Studio Code
In the terminal window enter the following:

cd /Users/wjk/.vscode/extensions/ms-vscode.csharp-1.5.0-future-preview1/
rm -rf bin
rm install.lock

Now, open Visual Studio Code and load your project. Fingers crossed!

It works! Thank you so much! What exactly was the cause of this, by the way?

Well, it nearly caused me to lose my remaining hair.
The problem was that I did not include the machine.config file that is necessary to let the whole System.Configuration system work. The error was completely correct. <startup> really was unrecognized -- because it wasn't defined anywhere.

And I am still having problems. I see “0 projects” in the VSCode status bar, and my intellisense is broken. (If I restart OmniSharp, it appears to be functional, but as soon as I start typing something it dies; the completion list simply says “Loading” and the “# references” lines in the editor vanish.) Furthermore, the OmniSharp log still displays the error about System.Management.Automation being referenced twice.

Note that when I place my cursor on a symbol and press F12, the OmniSharp log displays the following error:
[ERROR:Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware] An unhandled exception has occurred: A task was canceled.
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /gotoDefinition: 500 2275ms

This might have something to do with the broken intellisense.

The "0 projects" issue is here: https://github.com/OmniSharp/omnisharp-vscode/issues/835

Are you able to add me to your repo? If so, I'll take a look. I'd like to get this working for you.

@DustinCampbell I’ve just sent you an invite to wjk/SunburstApps.

thanks. I'll try it out and see if I can't get some fixes for you.

@DustinCampbell I’ve removed your push access from wjk/SunburstApps, because you don’t need it anymore; I have opened the repository up to all contributors.

Sounds good. I've cloned the project and am working through issues.

OK. I see why your getting that duplicate reference. Should be easy to fix.

Note: the reason duplicate references are being added is because it's defined that way in your projects. Both powershell-unix/powershell.csproj and powershell-win/powershell.csproj reference System.Management.Automation.csproj and they both import Microsoft.PowerShell.SDK.targets which also adds the same reference again. OmniSharp should have been resilient against this case but it wasn't.

That did it, all right. The duplicate-reference error is gone.

I'll have a real fix coming for you soon. The duplicate reference shouldn't be something you have to manage.

Nonetheless, thank you very, very much. I would never have found it on my own. Thank you!

OK. I've updated the binaries again with a couple of fixes. You can refresh them by doing the following:

Close Visual Studio Code
In the terminal window enter the following:

cd /Users/wjk/.vscode/extensions/ms-vscode.csharp-1.5.0-future-preview1/
rm -rf bin
rm install.lock

There are still several bugs lingering, but I'm going to resolve this one because I think we've gotten to the heart of it.

authors: DustinCampbell wjk

repo: OmniSharp/omnisharp-roslyn

license: mit

license_source: bigquery


text:
Upgraded to latest lsp-0.13 alpha for testing

@mholo65 This upgrade went pretty well things seem to working..  I dunno if might help with your other issue.

@david-driscoll I tried the alpha bits yesterday, with no success. Actually it didn’t even initialize using the C# LSP Client (version 0.12.1). Saw another exception too bubble up regarding converting ”empty json rpc response” to a ”initialized response”.. Or something like that. Can look again with this PR instead.

Seeing this with C# LSP Client when updating Omnisharp to use LSP libs 0.13.0-alpha*
Finding descriptor for initialized
Starting: Routing Notification initialized
Converting params for Notification initialized to OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializedParams
Failed to handle request initialized - System.ArgumentException: Object of type 'OmniSharp.Extensions.JsonRpc.EmptyRequest' cannot be converted to type 'OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializedParams'.
   at System.RuntimeType.TryChangeType(Object value, Binder binder, CultureInfo culture, Boolean needsSpecialCast)
   at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig)
   at System.Reflection.RuntimeMethodInfo.InvokeArgumentsCheck(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.HandleNotification(IMediator mediator, IHandlerDescriptor handler, Object params, CancellationToken token)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteNotification>d__5.MoveNext()

Initialized params is empty, so don't know what happened here. https://microsoft.github.io/language-server-protocol/specification#initialized
Will look into this, and also try to fix the issues seen in #1505 and #1525 as these are not fixed yet with updating LSP libs.

Fixes #1505
Fixes #1525

Eagerly awaiting this merge! Was also running into the didChange handler failures.

How's this coming along? Any blockers?

Surprised this wasn't included in the last release :(

I chatted with @mholo65 yesterday and we updated the test from #1583 from Linux since it's unstable on Azure DevOps with the LSP changes in. We can investigate that separately next and it shouldn't hold up this PR, the test still runs on Mac and Windows for now.
Should be good to go now.

authors: david-driscoll filipw mholo65 sebasmonia vincentwoo


text:
Adds parallel execution of background Roslyn analyzers

Fixes #2241
This PR builds upon the work started by @TomasEkeli in #2285 and adds some further improvements.
The original PR:

uses one semaphore for foreground worker and another for background worker, which could potentially use twice the configured threads when both workers are active
parallelizes only at the project level. This can yield a nice perf boost when there are many projects to analyze, but will be less effective when there are fewer projects (but potentially containing many files)
keeps the same diagnostics events (i.e. project start/stop) which, as visualized in a client like VS Code with just one status bar message at a time, has no real meaning anymore since multiple projects are now actually analyzed simultaneously

This PR addresses the above points by:

Parallelizing both at the project level (with no throttling) and at the document level (with throttling) to ensure the intended concurrency in both scenarios (many projects vs. few projects) while still respecting the global configured limit
Using a member-level semaphore for the throttling mechanism
Adding a new BackgroundDiagnosticStatus event (and associated model types) in addition to the existing ProjectDiagnosticStatus event. The new event is modeled around total and remaining number of documents currently being analyzed, instead of the notion of current project. An update event is emitted every 24 documents (results in reasonable frequency on most machines, could be made time-based as an improvement) allowing clients to display meaningful progress. Code for handling the new status event can eventually be added to omnisharp-vscode and other clients.
Retaining the old status events for backward compat with clients, "shimmed" - displays as Analyzing (23%)

This PR also parallelizes slightly more aggressively by defaulting to 75% of available processors (rather than 50%).

The improvements in this PR have been merged into the original PR #2285 - closing this one.


text:
Make SDK build of OmniSharp the default

In preparation for taking a new build of O# without the included Mono/MSBuild.
Part of https://github.com/OmniSharp/omnisharp-vscode/issues/5120

very exciting 😅

authors: JoeRobich filipw

repo: OmniSharp/omnisharp-vscode


text:
Fix parameters due to breaking changes in jsonrpc

Bump required versions for jsonrpc_base, jsonrpc_async and jsonrpc_websocket due to breaking changes in jsonrpc_async, jsonrpc_base and jsonrpc_websocket.
Fix parameters as per recommendation in the release notes.

Thanks @cgtobi!

authors: OnFreund cgtobi

repo: OnFreund/PyKodi


text:
сверстали мобильную версию header и menu

fixes #6

Да, еще один коммент на будущее: в названии пулреквеста не нужно добавлять глагол, вида "сделали", название пулреквеста должно отражать, что он содержит. Например: "верстка мобильной версии шапки и меню".

Обратил внимание еще на один момент: делайте, пожалуйста, почаще коммиты. У вас на всю задачу один коммит. Лучше разбивать задачу на небольшие логически законченные промежуточные шаги и коммитить отдельно их. Сделали разметку? Коммит. Добавили стили для всего блока? Коммит. Добавили стили для ссылок? Коммит.


text:
setup CI

https://docs.travis-ci.com/user/languages/ruby/

complete. thanks @sayhiben and @barbeau!

authors: aaronbrethorst bbodenmiller

repo: OneBusAway/onebusaway-deep-links


text:
IE11 Support

It doesn't seem to work in IE11 or is there any workaround for this?

any console error?

@kenberkeley It's just a syntax error. I scan the output code in the console and it points to
 pageSizeOptions: { type: Array, default: () => [10, 20, 40, 80, 100] },

I don't know why it's not compiling to a code readable by the browser.

also, check your babel-env config

I'm using Laravel Mix, any idea on how to do that?

checkout the relevant doc

authors: VerzatileTom kenberkeley


text:
Updated README

Signed-off-by: Tomasz Rybicki tomasz.rybicki@intel.com

ok to test

retest this please

repo: Open-CAS/standalone-linux-io-tracer


text:
Maps between target-types and build-types are missing

Maps between target-types and build-types are missing
The NXP Open-CMSIS-Pack cproject/csolution could be like this way:
cproject.yml
---
project:
  device: MK64FN1M0VLL12
  components:
  - component: NXP::Device:SDK Utilities:debug_console_lite
    ...
  groups:
  - group: source
    files:
    - file: boards/src/demo_apps/hello_world/hello_world.c
  - group: board
    files:
  - group: MK64F12/iar
    files:
    - file: devices/MK64F12/iar/MK64FN1M0xxx12_flash.icf
      for-type:
      - ".debug"
      - ".release"
      for-compiler:
      - IAR
  - group: MK64F12/arm
    files:
    - file: devices/MK64F12/arm/MK64FN1M0xxx12_flash.scf
      for-type:
      - ".debug"
      - ".release"
      for-compiler:
      - AC6
  - group: MK64F12/gcc
    files:
    - file: devices/MK64F12/gcc/MK64FN1M0xxx12_flash.ld
      for-type:
      - ".debug"
      - ".release"
      for-compiler:
      - GCC
  setups:
  - setup: IAR
    for-compiler: IAR
    for-type: ".release"
    misc:
    - ASM:
      C:
      CPP:
  - setup: IAR
    for-compiler: IAR
    for-type: ".debug"
    misc:
    - ASM:
      C:
      CPP:
  - setup: AC6
    for-compiler: AC6
    for-type: ".release"
    misc:
    - ASM:
      C:
      CPP:
      Link:
  - setup: AC6
    for-compiler: AC6
    for-type: ".debug"
    misc:
    - ASM:
      C:
      CPP:
      Link:
  - setup: GCC
    for-compiler: GCC
    for-type: ".debug"
    misc:
    - ASM:
      C:
      CPP:
      Link:
  - setup: GCC
    for-compiler: GCC
    for-type: ".release"
    misc:
    - ASM:
      C:
      CPP:
      Link:

csolution.yml
solution:
  target-types:
    - type: mdk
      compiler: AC6
    - type: armgcc
      compiler: GCC
    - type: iar
      compiler: IAR

  output-dirs:
    outdir: ./$TargetType$/$BuildType$
    rtedir: ./RTE/$TargetType$

  build-types:
    - type: debug
    - type: release

  projects:
    - project: hello_world.cproject.yml

This way is generally compatible with NXP SDK database.
But there are some examples that different compilers don't share same build-types.
In some cases(real world case), IAR/MDK support ram_0x1400_debug/ram_0x1400_release/debug/release, but armgcc just supports debug/release. Looks like there is no way in exsiting mechanism to support such cases because build-types are for all target-types. Obviously, armgcc+ram_0x1400_debug and armgcc+ram_0x1400_release cannot build passed.
Suggestion: add for-type inside build-types to specify the target-types OR add for-type inside target-types to specify the build-types

Is it possible to use the (not-)for-type filter on the project level for this? For example, if mdk is not compatible with debug:
solution:
  target-types:
    - type: mdk
    - type: iar
  build-types:
    - type: debug
    - type: release
  projects:
    - project: hello_world.cproject.yml
      not-for-type: +mdk.debug

If I understood correctly, that could be functionally what you need if not especially clear semantically.

@mcgordonite I do agree. The documentation is here:
https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/YML-Input-Format.md#projects
There is also an example given.

Thank you very much @mcgordonite. Your suggestion works.

authors: jkrech mcgordonite tcsunhao

repo: Open-CMSIS-Pack/devtools


text:
[csolution/packchk] 'name' attribute specifying folder in pack with file element causes segmentation fault.

Packs that have a file element + name attribute of the form:
<file category="source" name="source_path/" ...
... cause a segmentation fault when attempting to convert the solution:
$ csolution convert -s .csolution.yml
Segmentation fault (core dumped)
This was discovered while editing a custom CMSIS pack.
Looking at the doc for the 'name' attribute, it is clearly mentioned "in the format path/name.extension", so I was likely wrong to specify it as "path/". Yet, a segmentation fault seems a bit harsh.
packchk did not reject this construct, so maybe a bug should be raised against it too.
Found in v1.3.0

Fixed in packchk 1.3.98 -
https://github.com/Open-CMSIS-Pack/devtools/releases/tag/tools%2Fpackchk%2F1.3.98
included in CMSIS-Toolbox 1.5.0
https://github.com/Open-CMSIS-Pack/cmsis-toolbox/releases/tag/1.5.0

authors: jkrech smartinou


text:
temporal_extent in load_collection includes the second element

The openEO API https://processes.openeo.org/#load_collection specifies that the second element should be excluded.

a temporal_extent from 2021-06-01 00:00 to 2021-06-01 23:59 gives no result since of a whole day is subtracted in map_processes_ocs.py::exclusive_date, a few seconds should do the trick (assuming the problem is that OpenEO is "up to" and the cube is "up to and including").
When you have several images a day and want one image, subtracting a whole day makes things difficult for us.

Would it be possible to use second instead of day here or would that cause other problems that I cannot see ?

Good point, @m-mohr could you please tell me if subtracting 1 second behavior would still be API compliant?

I think you nay need to subtract depending on the granularity of the input.
If you receive 2020-01-01T00:00:00Z you'd need to subtract a second so that you get 2019-12-31T23:59:59Z.
If you receive 2020-01-01 you'd need to subtract a day so that you get 2019-12-31 (at 0:00:00).

Should it not be 2019-12-13 (23:59) ?

That's a good question. Having a closer look, the process description doesn't define this. Actually, you could probably also just remove 1 s always and be compliant as it's undocumented right now. I think actually my first comment is likely not the common understanding, but the more common understand when people read this is what @danielFlemstrom says. So maybe indeed just remove a second always.

Just a clarification of our problem. This is an excerpt of the actual time sequence of a product we have:
2020-10-01 08:20:09
2020-10-01 09:21:39
2020-10-01 09:24:39
2020-10-01 10:01:08
2020-10-01 10:04:08
2020-10-01 11:02:38
2020-10-02 08:55:28
2020-10-02 09:34:57
2020-10-02 09:37:57
2020-10-02 10:34:05
So if you want to look at ONE of these pictures, say 2020-10-01 09:21:39 , it is quite tricky to get it right.

If you modify this line https://github.com/Open-EO/openeo-odc/blob/095d9c287d9a98ee77d421c31cb63cb741d42d02/src/openeo_odc/map_processes_odc.py#L60 with
            return np.datetime_as_string(np.datetime64(date) - np.timedelta64(1, 's'), timezone='UTC') # Substracts one second
and you provide in the openEO process graph a temporal extent of ["2020-10-01T09:21:39Z","2020-10-01T09:22:39Z"]  it should work fine!

Any chance of getting that fix into the repo ?

authors: clausmichele danielFlemstrom m-mohr

repo: Open-EO/openeo-odc


text:
Date Math processes

I just got this feature request:

Hi, I have a question on the usage of parameters in a UDP. Is it possible to do some date calculations on a parameter before using it later in the UDP? For example, this is a Python snippet that shows what I want to achieve:
 def pixel_inputs(vito_connection, bbox, start, end) -> DataCube:
      start_dt = pandas.to_datetime(start) - pandas.to_timedelta("90D")
      end_dt = pandas.to_datetime(end) + pandas.to_timedelta("90D")
      S2bands = vito_connection.load_collection(
           'TERRASCOPE_S2_TOC_V2',
           temporal_extent=[start_dt, end_dt]
           ....

This works fine when I run this as a normal Python script. But when I try to include it in a UDP, the start and end are UDP parameters and the pandas.to_datetime() method doesn't know what to do with a Parameter object. Is there another way to achieve this?

I think this is an interesting use case to start introducing "date math" processes, so that they can be used inside the UDP of this use case.
A good one to start seems to be something like date_shift (or date_delta, date_offset), taking arguments:

date (string): reference date to work from
delta (string): a string expressing a time shift, like "90D" (90 days) in the example (also see https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.to_timedelta.html). The delta probably also have to include a sign to indicated if the delta has to be added or subtracted.

and returning the shifted date (as string)

but I think we should look into libraries more into detail and figure out what they are actually doing. If we find a common ground there, it's makes implementing the process easier in most cases.

A couple of quick observations from the wild (Python):

Python builtin datetime.timedelta: largest scale to specify is day level, no support for weeks, months, years
pandas.to_timedelta doesn't seem to support month delta's (anymore?). Year delta's work, but it seems to be a constant offset of 365 days 05:49:12. For example:

"2020-01-01" + 1y -> '2020-12-31 05:49:12'
"2021-01-01" + 1y -> '2022-01-01 05:49:12'
this doesn't seem like something we want to replicate

the dateutil package (which is used in various other date handling libs) has a relativedelta (https://dateutil.readthedocs.io/en/stable/relativedelta.html) that does support months and years, and the behavior it implements on month overflow is to stick to the last day of the month, e.g.:

"2020-01-31 + 1 month -> 2020-02-29
"2021-01-31 + 1 month -> 2020-02-28
"2020-02-29 + 1 year -> 2021-02-28

we could also start with not supporting year and months, and only provide support for days, (maybe weeks), hours, minutes, ...
The discussion about years and months could be a different follow up issue

On a more general note, what you commonly find in date math libraries like dateutil  is date shifting (shifting the date some relative offset) and date replacing (setting certain date components , e.g. month, to a fixed value) functionality, provided in some symmetrical or even unified way.
Currently in  #248  we have the idea to do the date shift for a single temporal level (day/hour/..) at a time because that should be enough for most use cases. But for date replacing, you probably want to set multiple components at the same time (e.g round a date down to first of month, or up to last of month).
With that in mind, and after seeing some usage patterns of some python libraries, another approach we could take is providing these two related processes:

date_shift(date, value)
date_replace(date, value)

where value is an object, with fields "day", "hour", ..., for example:

date_shift(date, value={"month":1, "day":-2})`:  shift ahead 1 month and 2 days back
date_replace(date, value={"day":1, "hour":0, "minute":0, "second":0}): round down to first day of the month

the dateutil package (which is used in various other date handling libs) has a relativedelta (https://dateutil.readthedocs.io/en/stable/relativedelta.html) that does support months and years, and the behavior it implements on month overflow is to stick to the last day of the month, e.g.:

"2020-01-31 + 1 month -> 2020-02-29
"2021-01-31 + 1 month -> 2021-02-28
"2020-02-29 + 1 year -> 2021-02-28

That behavior seems pretty logical and reasonable to me. Would that explain it well enough?

If any of the changes result in an invalid date, the corresponding part is rounded down to the next valid date. For example, adding a month to 2020-01-31 would result in 2020-02-29.

I found that much simpler to understand in contrast for example to:

when shifting year or month components: first round down to first of the month (save this offset for later), shift years and/or months, add initial day offset back we subtracted earlier. e.g.: 2021-01-31 + 1 month -> 2021-01-01

I feel like that in our domain year and month would be the core use-cases, right? I mean hours, minutes and (milli)seconds are not the granularity of usual EO processing so we'd be left with just days (and the shortcut weeks).
... it should support something that's not just working on a fixed number of days, but give an advantage that can't be easily computed without "looking" at a calendar.

I understand that it looks underwhelming to have a solution where a day level shift is the only practically relevant option, but in the original use case of this feature request (date manipulation in UDPs) that would already be a game changer.

the JSON Schemas would still be different ...  So an alignment doesn't seem to help a lot here

Good point about the schemas, but that doesn't mean that you should drop a more loose form of uniform interface all together. Actually, in my former job I often had to do a lot of "date math" (using the arrow library) and that typically involved combinations of shift and replace (e.g. date.replace(day=1).shift(months=+1).shift(days=-1) to get last day of the month). Having a uniform interface for these methods made this a nice API to work with.

Also, in process definitions I usually try to avoid objects as parameters as they are harder to grasp from a user perspective.

True, but how would you propose to define date_replace, allowing multiple date components to be set at once?
The value of having both date_shift and date_replace (preferably in some uniform way)   is that it offers the end user a lot of flexibility to implement the desired month/year overflow handling according to their use case.

dateutil ... on month overflow is to stick to the last day of the month
That behavior seems pretty logical and reasonable to me.

Yes I agree, from all options I've seen so far this one would also my preference now.
Also note that this behavior could also be used for date_replace : date_replace(day=31)  would automatically snap to last day of month instead of giving some kind of value error. dateutil does this automatic snapping for example.

I've just pushed a new commit, please have another look. It mostly adds the date-only support.

I understand that it looks underwhelming to have a solution where a day level shift is the only practically relevant option, but in the original use case of this feature request (date manipulation in UDPs) that would already be a game changer.

The minutes/hours/seconds/milliseconds don't add much complexity so it's fine to keep them. With months and years we may seem to settle on something reasonable right now. I'll do further investigations in other languages next to verify that it's easy to implement though.

Good point about the schemas, but that doesn't mean that you should drop a more loose form of uniform interface all together. Actually, in my former job I often had to do a lot of "date math" (using the arrow library) and that typically involved combinations of shift and replace (e.g. date.replace(day=1).shift(months=+1).shift(days=-1) to get last day of the month). Having a uniform interface for these methods made this a nice API to work with.

On the other hand, we could also make date_replace work with the same API that is available in date_shift. For the usecase above that's totally fine at least.

True, but how would you propose to define date_replace, allowing multiple date components to be set at once?

In a world where there are only named parameters available, I'd go with parameters. But in JS for example that could lead to something like date_replace(date, year = null, month = null, day = 1). :-(

we could also start with not supporting year and months, and only provide support for days, (maybe weeks), hours, minutes, ...
The discussion about years and months could be a different follow up issue

I agree here, having the days would be already a good start and covering many use cases.

So I had a look at R's lubridate (nice cheatsheet, by the way: https://rawgit.com/rstudio/cheatsheets/master/lubridate.pdf ), JS's moment.js and Java's java.time. For them, all examples work correctly, including leap month and leap second "snapping". From what you have written, I assume Pythons dateutil package will works, too. See the PR for a new version of the process, please.

date_shift has been merged as a new process.

authors: clausmichele m-mohr soxofaan

repo: Open-EO/openeo-processes


text:
WP3 Validation of process metadata: test_process_metadata_functional() should ignore non-functional metadata in parameter schema

test_process_metadata_functions() from src/openeo_test_suite/tests/processes/metadata/test_process_metadata.py, check values within functional and non-functional parameters. For example, this function also tests for description, which is present in the schema parameter. Like"id": "array_append", "parameters": [     {           "description": "Value to append to the array.",           "name": "value",           "schema": {             "description": "Any data type is allowed."     }     }

This should not happen if -m "not optional" is added to the command.

non-functional parameters are skipped with -m "not optional". The longrunning marker has nothing to do with process metadata.
See the docs in readme about "WP3 Validation of process metadata":

Non-functional tests concern descriptions and other metadata of processes that have no impact on the actual behavior of the process, failures in these tests should be taken as warnings, but don't necessarily need to be fixed. These can be skipped by adding -m "not optional" to the pytest command.

There's was a mistake in last sentence. I have made the edit.

ok, I understand now, you are talking about non-functional fields in the schema of process parameters. The parameter's schema  is indeed being compared as a whole currently:
https://github.com/Open-EO/openeo-test-suite/blob/5b9727d6b6b8a05672bcdd1aafd0a289f32a472a/src/openeo_test_suite/tests/processes/metadata/test_process_metadata.py#L79-L80
Do you have some concrete examples of differing parameter schema's?

A couple of examples where even schemas are meant to be updated by implementations:

https://processes.openeo.org/#resample_spatial (method, more specifically the enum and description)
https://processes.openeo.org/#ard_normalized_radar_backscatter and https://processes.openeo.org/#sar_backscatter (options parameter)
https://processes.openeo.org/#ard_surface_reflectance (atmospheric_correction_options and cloud_detection_options)
...

authors: Jay-Gohil m-mohr soxofaan

repo: Open-EO/openeo-test-suite


text:
Time-dependent Side Views

Side Views are time-independent. So if we have a long flight (up to 8h for HALO), we need to "stitch" all the different time steps (e.g. in 1h steps). Is it possible to interpolates the side views for an average aircraft speed (which is available on MSS as Performance Setting)? The result would be

time-dependent Side Views

The MSS tool, with a proper performance-parametrization, has a pretty good understanding of when it is at each point along the flight track.
Taking this into account for the sideview would be a semi-useful feature, depending on the temporal resolution of available model data. The CLaMS group often provides only 12h or even 24h timesteps to avoid overly optimizing to the model forecast.
Currently the sideview requires the selection of a time. The WMS standard does not support the required features. We could extend our current extension further to not provide just the lon/lat values of the flightpath, but also timestamps. This could cause compatibility issues unless carefully implemented. One could add a new mode to let the MSS Server interpolate the available data in time.
Adding this seamlessly to the existing interface could be tricky, but is probably feasible. Adding the interpolation to the server would increase CPU+IO requirements for the server but that might be acceptable.
I guess this feature would require at least a week of implementation time, probably several (especially including testing etc.)
I am not sure if or when we might address this. Is there someone of the campaign who could address this with support by us?

Time interpolation is also of interest for the application of evaluating contrail energy forcing of long flights (+/-10h) which depends on solar angle and met. data. Hourly output can be created with the forecasting tool COCIP and could be interpolated in time.

repo: Open-MSS/MSS


text:
klite: update version to 18.1.5

Please verify if installation & runtime of the verb still works for the updated version (changelog) before merging, previously (https://github.com/GloriousEggroll/protonfixes/pull/80) I could test this with Persona 4 Golden but that game doesn't need it anymore and the obsolete gamefix has corrently been removed in the past.

I actually own Persona 4 Golden, but it's unfortunate I can't test it there either. Other than that, I currently do not have any other game available that I can test this unless @marianoag is open for testing this on Gabriel Knight 3.
However, in the meantime, what we can do is make another verb e.g. klite_latest.verb.

I actually own Persona 4 Golden, but it's unfortunate I can't test it there either. Other than that, I currently do not have any other game available that I can test this unless @marianoag is open for testing this on Gabriel Knight 3.
However, in the meantime, what we can do is make another verb e.g. klite_latest.verb.

Yes it still works.

authors: R1kaB3rN marianoag tgurr

repo: Open-Wine-Components/ULWGL-protonfixes


text:
fix: delete reduntant lock in storage

这个 PR 中主要做了两件事：

由于 Pika 的 CMD 层上了 Key 锁，所以把 Redis 层的 Key 锁进行了删除
如图所示，在 DB 层有两个重复的 shared_mutex 保护 DB 的变量，对于它们两个进行了整合操作

#2371 #2322

LGTM，加点测试用例，构造一下竞争场景

authors: Mixficsol wanghenshui

repo: OpenAtomFoundation/pika


text:
No summary text in evidence responses

Here is evidence 54e7712b38da0d6e9a000004 for example:
HTTP/1.1 200 OK
Connection: keep-alive
Content-Encoding: gzip
Content-Type: application/hal+json
Date: Fri, 20 Feb 2015 19:03:45 GMT
Keep-Alive: timeout=20
Server: nginx/1.4.6 (Ubuntu)
Transfer-Encoding: chunked
Vary: Accept-Encoding

{
    "evidence": [
        {
            "_links": {
                "collection": {
                    "href": "http://next.belframework.org/api/evidence",
                    "type": "evidence-collection"
                },
                "self": {
                    "href": "http://next.belframework.org/api/evidence/54e7712b38da0d6e9a000004",
                    "type": "evidence"
                }
            },
            "bel_statement": "p(evidence) increases p(canBeCreated)",
            "biological_context": [
                {
                    "name": "Species",
                    "value": [
                        9606,
                        10090
                    ]
                },
                {
                    "name": "Cell",
                    "value": [
                        "fibroblast",
                        "leukocyte"
                    ]
                }
            ],
            "citation": {
                "id": "10022765",
                "name": "None",
                "type": "PubMed"
            },
            "metadata": {
                "status": "draft"
            }
        }
    ]
}

Confirmed fixed and :+1: on the 7 minute response time. Have a :beer: on me.
We (Selventa/OpenBEL) need to start a contest for quickest turn-around from issue creation to fixed in production, because we're that good.

What :bug:? You didn't see anything (waves hands).

authors: abargnesi nbargnesi

repo: OpenBEL/openbel-server


text:
💡 [REQUEST] - minicpmv2.5的量化支持，autoGPTQ，autoAWQ

起始日期 | Start Date
No response
实现PR | Implementation PR
No response
相关Issues | Reference Issues
No response
摘要 | Summary
有考虑支持minicpmv2.5模型的量化吗？autoGPTQ,autoAWQ模型
基本示例 | Basic Example
无
缺陷 | Drawbacks
无
未解决问题 | Unresolved questions
minicpmv2.5考虑支持autoGPTQ和autoAWQ  量化吗？

你好，已经适配了awq，https://modelbest.feishu.cn/wiki/PAsHw6N6xiEy0DkJWpJcIocRnz9?from=from_copylink，请看这个地址

repo: OpenBMB/MiniCPM-V


text:
流式输出

请问在git主页的测试案例,如何实现模型的流式输出呢?
或者huggingface主页的推理示例如何实现流式输出,一个字一个字的输出 而非一句话一起输出

同问

同问，怎么设置？

authors: chuangzhidan liyandongpy sssssshf


text:
docker compose failed

Issue Description / 问题描述
docker compose up执行的过程中，在执行XAgentServer的dockerfile的时候报错。
错误：
=> ERROR [XAgentServer xagentserver  4/14] RUN apt-get install -y nginx systemctl

[XAgentServer xagentserver  4/14] RUN apt-get install -y nginx systemctl:
0.574 Reading package lists...
0.589 Building dependency tree...
0.591 Reading state information...
0.591 E: Unable to locate package nginx
0.591 E: Unable to locate package systemctl

failed to solve: process "/bin/sh -c apt-get install -y nginx systemctl" did not complete successfully: exit code: 100
Steps to Reproduce / 复现步骤
docker compose up / 请提供复现错误的具体步骤。
Expected Behavior / 预期行为
Describe the behavior you expected to see. / 请描述您期望的正确行为。
Environment / 环境信息

Operating System / 操作系统：
Python Version / Python 版本：
Other Relevant Information / 其他相关信息：

Error Screenshots or Logs / 错误截图或日志
If possible, please provide relevant screenshots or logs of the error. / 如果可能，请提供相关的错误截图或日志文件。
Additional Notes / 其他备注
If you have any additional information or notes, please add them here. / 如果有其他补充信息，请在此处添加。

您好，这种情况可能是网络问题导致上一步apt update未更新，您可以清除已经走过的docker后重新build将会解决这个问题。

非常感谢！确实是上一步update的原因。我清除过几次，结果都是一样的，后来加了-y 选项就可以了。

authors: lionday sailaoda

repo: OpenBMB/XAgent


text:
Feature request: As a vendor I should be able to cancel an order

Brief Description:
As a vendor I should be able to cancel an order.
Operating System (OS and version): Ubuntu 14.04
OpenBazaar version (shown on About OpenBazaar page in menu): 1.1.3
Hardware:
Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce):
Always
Steps to reproduce:

Buyer places an order
Buyer changes his mind and doesn't pay

Observed Behavior:
As a vendor I'm unable to cancel the order
Expected Behavior:
As a vendor I should be able to cancel the order
Additional info (links, images, etc go here):

In the latest client, we now hide orders which have been unfunded by default.

The reason we don't allow deleting an order is that if a buyer changes the mind again and does fund it, then the vendor will never even know that happened and the funds will be lost. Since it is annoying to vendors to see those unfunded abandoned orders the compromise is to simply hide the orders from view, unless you are specifically looking for them and then you can hit the "Show Unfunded" button.
I'm closing this issue.

authors: SamPatt kabo

repo: OpenBazaar/OpenBazaar-Client


text:
Connectivity status

Brief Description:
OB used to run just well for awhile on my notebook. I was able to browse listings and buy stuff. For about a week now, it doesn't display any other items. I can still browse my own page and listings. If I click on a shop from the following or followed tab, I get this message : "The page you're trying to view is currently offline". But it seems more probable that my node is somehow disconnected from the rest of the OB network.
I searched for a status page, but couldn't find one.
Operating System (OS and version): trisquel belenos
OpenBazaar version: 1.0.10
Hardware: lenovo x60
Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce): Always
Observed Behavior:
My node doesn't display any listings.
Expected Behavior:
I can browse other people's listings.
Additional info (links, images, etc go here):
My shop id is:
1ffccdef3156a75ea0275e2220567207a9ed23e7
Can anybody still connect to it?

With the newer versions the behavior seems to be correct, but I'm looking forward to the planned ipfs offline store feature.

repo: OpenBazaar/OpenBazaar-Server


text:
ETH precision: openbazaar-go updates

openbazaar-go updates
High-level overview

[ ] 1. repo.Listing abstraction (for handling contract versioning properly)

[ ] 2. (*repo.Listing) Quantity() big.Int respects versions properly (w/ unit tests)

[ ] 3. MarshalJSON and UnmarshalJSON

[ ] 4. protobuf changes (updates to proto usage should use repo.Listing getters for accessing changed schema data)

[ ] 5. JSON API updates

[ ] 6. openbazaar-go datastore migrations

Protobuf Schema

[x] 7. Create pb.CurrencyValue proto to track high-precision value of a currency

(smallest known precision is 1e-18)

proto CurrencyDefinition {
  string      code
  json.Number divisibility
}
proto CurrencyValue {
  CurrencyDefinition currency
  json.Number        value
}

[ ] 8. Restrict prior schema version to BTC, BCH, LTC, ZEC as accepted currencies for transactions (recommend creating non-proto type pb.Listing to manage version-specific marshal/unmarshal of JSON contracts and proper mapping of changing fields between current v4 and future v5 Listings.... Ex: pb.Listing.Price() can return a valid price regardless of source being v4 or v5.)

[ ] 9. Bump Listing to new schema v5

[ ] 9A. Update pb.Listing.Metadata.Coin[Type|Divisibility] to use pb.CurrencyDefinition

[ ] 9B. Update pb.ListingItem.Price to use pb.CurrencyValue

[ ] 9C. Merge pb.Listing.Metadata.PricingCurrency with pb.Listing.ListingItem.Price into pb.CurrencyValue

[ ] 9D. In pb.Listing.BuyerOrder update pb.Order_Payment.Amount and pb.Order_Payment.Coin to use pb.CurrencyValue

[ ] 9Di. Replace ModeratorInfo.Price usage with pb.CurrencyValue

[ ] 9Dii. Replace CoinType and pb.CoinDivisibility to use pb.CurrencyDefinition

[ ] 9E. Update pb.ListingItem.Skus.Quantity to use json.Number (to support larger inventory requirements in CRYPTOLISTING listings)

[ ] 9F. Update pb.Listing.BuyerOrder.RefundFee to use pb.CurrencyValue

[ ] 9G. In pb.Listing.BuyerOrder.Items collapse Quantity and Quantity64 ito json.Number

[ ] 9Gi. Properly represent that < v2 schema expects Quantity and >= v3 requires Quantity64

[ ] 9Gii. >= v5 requires json.Number to support (now) larger inventory requirements for Cryptocurrency listings

[ ] 9H. In pb.Listing.BuyerOrder update Amount and Coin to use pb.CurrencyValue

[ ] 9I. Update BuyerOrder schema version?

[ ] 9J. Update pb.VendorOrderConfirmation.RequestedAmount to pb.CurrencyValue

[ ] 9K. Update pb.VendorOrderFulfillment.Payout.PayoutFeePerByte to pb.CurrencyValue

[ ] 9L. Update pb.Dispute.Outputs[].Value to pb.CurrencyValue

[ ] 9M. Update pb.TransactionRecord.Value to pb.CurrencyValue

[ ] 9N. In pb.ShippingOption.Service update Price and AdditionalItemPrice  to pb.CurrencyValue

[ ] 9O. Update pb.Coupon.PriceDiscount to pb.CurrencyValue

*Note: I know there is redundant data with the currency type being expressed in every place where a value is represented. This was done intentionally so that knowledge of implicit relationships between fields aren't required to make sense of the data. Denormalizing data here also doesn't hurt us as we can ensure the implicit relationships are intact more easily with tests and validations.
API changes

[ ] 10. The JSON representation of the pb.CurrencyValue type above should be used in place of int usages for amount. The typical transformation will look similar to the following other indicated otherwise:

A value of 0.12345678 BTC might be represented like this before:
{
    "data": "value",
    "amount": 12345678, // this key is inconsistent across calls
    "coin": "BTC", // this key is inconsistent across calls
    "otherdata": "othervalue"
}

This data would be changed to look like:
{
    "data": "value",
    "amount": { // this key would match the replaced key in the BEFORE case
        "value": "12345678",
        "currency": {
            "code": "BTC", // this key would always be `code`
            "divisibility": 8
        }
    },
    "otherdata": "othervalue"
}

[ ] NOTE: We need to ensure values lower than 0 in the value field are rejected with an error explaining that the value must be a positive integer.

[ ] 11. POST /ob/purchase (POSTPurchase) response

Datastore migrations: SQLite data

[ ] 12. Cases

[ ] 12A. Migrate buyerOutputs and vendorOutputs which contain serialized sets of values:

[
  {
    "hash": "85499ec9b053772fc9ce95b695de1aa1fe83ea7daf44cda52ab27aac13a679d6",
    "value": 386091
  }
]

[ ] 13. Inventory

[ ] 13A. Migrate count from type integer to text
[ ] 13B. Migrate surcharge from type integer to text

[ ] 14. Notifications

[ ] 14A. Migrate serializedNotification to new model schema
[ ] 14B. Ensure all price values are strings

[ ] 15. Purchases/sales (consider merging these into one table and add a type column to differentiate?)

[ ] 15A. Migrate total from type integer to text?
[ ] 15B. Migrate transactions which contain serialized sets of values:

[
  {
    "Txid": "85499ec9b053772fc9ce95b695de1aa1fe83ea7daf44cda52ab27aac13a679d6",
    "Index": 0,
    "Value": 386091,
    "Address": "prv2kgx6m8ynestdmvhlndm237hhqgr4yce9q0a090",
    "Spent": true,
    "Timestamp": "2019-01-23T22:36:37.141428851-05:00"
  },
  {
    "Txid": "dde5a08c860faf7bd1b56d1528640fdbefd659ef798cfddb33e77b8b187fec4b",
    "Index": 0,
    "Value": -386091,
    "Address": "prv2kgx6m8ynestdmvhlndm237hhqgr4yce9q0a090",
    "Spent": true,
    "Timestamp": "2019-01-23T22:50:58.659452463-05:00"
  },
  {
    "Txid": "dde5a08c860faf7bd1b56d1528640fdbefd659ef798cfddb33e77b8b187fec4b",
    "Index": 0,
    "Value": -386091,
    "Address": "prv2kgx6m8ynestdmvhlndm237hhqgr4yce9q0a090",
    "Spent": false,
    "Timestamp": "2019-01-24T04:07:23.949652851Z"
  }
]

[ ] 16. stxos/txns/utxos (consider merging these into one table with a type differentiator?)

[ ] 16A. Migrate value from integer to text?

Changed the spec to remove the magnitude key in favor of a simpler "one value" reprentation.
{
    "data": "value",
    "amount": { // this key would match the replaced key in the BEFORE case
        "value": "12345678",
      //  "magnitude": -8,    # omit this key
        "currency": {
            "code": "BTC", // this key would always be `code`
            "divisibility": 8
        }
    },
    "otherdata": "othervalue"
}

@amangale Discussion has raised the following requirement:

NOTE: We need to ensure values lower than 0 in the value field when used in the JSON API are rejected with an error explaining that the value must be a positive integer. Recommend a 400 Bad Request error response.

@amangale you asked for some details of calls that use the amount field, here's what I turned up with a quick search that I know the desktop client uses. This may not include everything:

ob/purchase
wallet/spend
wallet/orderspend
wallet/balance
ob/listing/[id]/[slug]
ob/listing/ipfs/[hash]
ob/listings
ob/case/[id]
ob/order/[id]
ob/profile/[id] (in the moderator fee info)

@amangale
Ashwan, just following up on my comment in the slack thread:
Keep in mind that a few of those endpoints include the full listing which does already have the coinDivisibility in it in the metadata object. It’s a required field when creating the listing.
So, for those api’s no change is needed.
I think these are the ones with the full listing:

ob/listing/[id]/[slug]
ob/listing/ipfs/[hash]
ob/order/[id]

@amangale
Another thing is the metadata.coinDivisibility in the listing is in the old format (e.g. 100000000 instead of 8. Can you please make sure it uses the new format?
And I guess the server needs to be compatible with old listings using the old format.. or I guess maybe it just needs to migrate the data.

@amangale @jjeffryes @mg
Another thing with that endpoint list is that a few of those endpoints aren't READs from the server. They are the client posting data back to the server, so those don't need the coinDiv in them.
For ob/purchase, the client would use the coinDiv from the listing which is referenced by a hash included in the POST data. I'm assuming the server when it receives the post could also get the coinDiv from the listing and use it to process any price fields.
For wallet/spend, should the client just use the coinDiv provided via wallet/balance or is it better for the client to explicitly send back the coinDiv it's using in the spend call?
For wallet/orderspend, should the client use the coinDiv from the listing the order is for or same question as above, should the client explicitly provide it in the orderspend call?

@rmisio To respond to your old questions, I think posting the full definitions despite just getting them from a prior call makes the API more stateless. This means that a POST body might need to repeat the symbol and divisibility of the amount being sent. (The type and name can probably be omitted.) I think it's reasonable to accept just the string instead of the full definition, allow the server to assume the same divisibility as whats in the dictionary... but that would probably be a different key.

authors: drwasho jjeffryes placer14 rmisio

repo: OpenBazaar/openbazaar-go


text:
Reorganize CLI

Closes #24 and closes #25
This PR switches the CLI from using argparse to click. This comes with a few added benefits, including better automatic generation of help messages, the creation of sub-commands, the cleanup of flags.
~Right now this PR is marked as a draft because I have still yet to successfully generate a new graph.~ I've finally been able to download, parse, and output all of the files as TSV :smile:
One of the big issues I've found in the logic in this package is the global variables in from openbiolink import globalConfig - it makes the logic very nonlinear and hard to organize. It would be better for each function to take the values stored in the global configuration as arguments and only have the CLI or the user make the choices explicitly when calling those functions. This could be done in a subsequent PR

Please let me know if there's anything you'd like me to explain

I hope i am not too annoying, but I think you forgot the "--output_format" option, did not verify that though. Through this flag three arguments can be set: The actual format, if it should be one single file for edges,... or muliple (grouped by relations) and the separator of the file.

It's true, I skipped the --output_format option. I had a really hard time figuring out what it was doing, so I left it to only output whatever was set as the default. Maybe you could help improve this PR to re-incorporate that.

Great, thanks! If you don't want to change anything anymore, I would merge this with the master branch.

I’d call it ready to go. Grüße aus Bonn :)

authors: cthoyt nomisto

repo: OpenBioLink/OpenBioLink


text:
[Feature Request] Async Publisher.values

Combine added a values property (and a throwing counterpart) that lets you bridge from the world of Combine into async/await (on supported Swift version), and we don't have parity here.
Here's my attempt to implement this:
#if !canImport(Combine)

import OpenCombine

// TODO: write throwing variant, as well.
extension Publisher where Failure == Never {
    var values: AsyncPublisher<Self> {
        return AsyncPublisher(self)
    }
}

// Trying to keep the type names the same as Combine
struct AsyncPublisher<P: Publisher>: AsyncSequence where P.Failure == Never {
    typealias Element = P.Output

    let p: P

    init(_ p: P) {
        self.p = p
    }

    func makeAsyncIterator() -> Iterator { Iterator(p) }

    struct Iterator: AsyncIteratorProtocol {
        // Does this cancellable ever need to be nil-ed out? IDK.
        private let cancellable: AnyCancellable?
        private var streamIterator: AsyncStream<P.Output>.Iterator

        init(_ p: P) {
            var cancellable: AnyCancellable? = nil

            let stream = AsyncStream(P.Output.self) { continuation in
                cancellable = p
                    .handleEvents(receiveCancel: { continuation.finish() })
                    .sink(
                        receiveCompletion: { _ in continuation.finish() },
                        receiveValue: { continuation.yield($0) }
                    )
            }

            self.cancellable = cancellable
            self.streamIterator = stream.makeAsyncIterator()
        }

        public mutating func next() async -> P.Output? {
            return await streamIterator.next()
        }
    }
}
#endif

It's a little jank, so I don't feed confident opening a PR for it yet, but I'd appreciate some feedback and ideas!

Hi!
Thanks. Although it should be already implemented on #219, it just needs tests.

authors: amomchilov broadwaylamb

repo: OpenCombine/OpenCombine


text:
Allow only POST requests on /sp/consume-assertion

We stated that GET was also allowed in order to render more user
friendly error reports. That was not at all the case. In a recent effort
error reporting regarding disallowed request methods was improved.
So we can now start enforcing POST requests on the ACS endpoint. Any
other request method will result in routing exception that in turn will
be handled by the improved error reporting.
Task 2 of: https://www.pivotaltracker.com/story/show/164121663
Also see: #646

The build fails on the expectation added in the Behat test. This will not yet work until we are rebased onto #646

repo: OpenConext/OpenConext-engineblock


text:
Remove screenshot from microagent prompt

This removes the BrowserObservation screenshot from the microagent prompt.
Fixes https://github.com/OpenDevin/OpenDevin/issues/1545
This is based on what we do in MonologueAgent:
https://github.com/OpenDevin/OpenDevin/blob/91c8f1cb3f16904bac79f548bc1474c8601403f8/agenthub/monologue_agent/agent.py#L117
We might also consider making this a more general utility function in the future (converting history to text).
UPDATE: This is still buggy, will convert to an issue and ping when it's fixed.

We've done this in a few places now--we need a better solution 🙃
Actually--maybe we should put this in to_memory? I think that drops a few field

authors: neubig rbren

repo: OpenDevin/OpenDevin


text:
Release/oedatamodel v1.0.0

inital release of the oedatamodel version 1.0.0

fixed wrong branch name in #4

repo: OpenEnergyPlatform/oedatamodel


text:
居然还找到了作者的照片😂

哈哈哈哈哈

哼哼哼，这张有的憨。。当时随便弄了张上去，赶紧给本仙女删了吧，哼哼哼哼哼哼）

真棒，笑啦

哼哼哼，这张有点憨。。当时随便弄了张上去，赶紧给本仙女删了吧，哼哼哼哼哼哼）

现在的小朋友都这么厉害了吗  敲代码这么厉害哈哈哈哈哈

authors: WhaleFell demo2099 hhllee

repo: OpenEthan/SMSBoom