Make failure

The most recent version (downloaded from the master as of 5 minutes ago) is throwing the following error while making on (at least two of) the TRIUMF machines:
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx: In function ‘int G__TGRSIFitDict_621_0_4(G__value*, const char*, G__param*, int)’:
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error:                 namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error:                 namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error:                 namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error:                 namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error:                 namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error:                 namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error:                 namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error:                 namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: expected ‘)’ before ‘G__int’

You had to make clean with the old master before downloading the new master. The other way to get around this now that it is to late is to delete any Dictionaries that are anywhere in the libraries folder.

On Oct 20, 2015, at 6:18 PM, jhenderson88<EMAIL_ADDRESS>wrote:
The most recent version (downloaded from the master as of 5 minutes ago) is throwing the following error while making on (at least two of) the TRIUMF machines:
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx: In function ‘int G__TGRSIFitDict_621_0_4(G__value, const char, G__param*, int)’:
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: expected ‘)’ before ‘G__int’
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531.

Tried removing all libraries (that we could find), which didn't help.
I should also point out that this occurred with two new clones, not from pulls, so I'm not entirely sure how it can be a lingering problem from a previous version.

try:
rm -f find -name *.so
rm -f find -name *Dict*
make clean
make -j
In the $GRSISYS directory.  I can get the current master to compile on
grsimid00.
On Tue, Oct 20, 2015 at 6:55 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Tried removing all libraries (that we could find), which didn't help.
I should also point out that this occurred with two new clones, not from
pulls, so I'm not entirely sure how it can be a lingering problem from a
previous version.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149725441
.

This is likely due to an old compiler or ROOT version I would guess. Can you try commenting out the template constructors in TDecayFit within the TDecay.h. Nothing should be using them at this point.

On Oct 20, 2015, at 6:18 PM, jhenderson88<EMAIL_ADDRESS>wrote:
The most recent version (downloaded from the master as of 5 minutes ago) is throwing the following error while making on (at least two of) the TRIUMF machines:
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx: In function ‘int G__TGRSIFitDict_621_0_4(G__value, const char, G__param*, int)’:
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3425: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3430: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3439: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3443: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3451: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3455: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3462: error: expected ‘)’ before ‘G__int’
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: reference to ‘ROOT’ is ambiguous
/opt/root/include/Rtypes.h:190: error: candidates are: namespace ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:53: error: namespace TGRSIFunctions::ROOT { }
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: expected primary-expression before ‘)’ token
.build/libraries/TGRSIAnalysis/TGRSIFit/TGRSIFitDict.cxx:3464: error: expected ‘)’ before ‘G__int’
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531.

True, if you didn’t change your system variables this could also be an issue.

On Oct 20, 2015, at 7:01 PM, pcbend<EMAIL_ADDRESS>wrote:
try:
rm -f find -name *.so
rm -f find -name *Dict*
make clean
make -j
In the $GRSISYS directory. I can get the current master to compile on
grsimid00.
On Tue, Oct 20, 2015 at 6:55 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Tried removing all libraries (that we could find), which didn't help.
I should also point out that this occurred with two new clones, not from
pulls, so I'm not entirely sure how it can be a lingering problem from a
previous version.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149725441
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149726352.

Also you may have to remove
$GRSISYS/libraries/TGRSIAnalysis/TSiLi/SiLiHit.cxx
and I meant grsmid01 not grsmid00.
On Tue, Oct 20, 2015 at 7:01 PM, Peter<EMAIL_ADDRESS>wrote:

try:
rm -f find -name *.so
rm -f find -name *Dict*
make clean
make -j
In the $GRSISYS directory.  I can get the current master to compile on
grsimid00.
On Tue, Oct 20, 2015 at 6:55 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Tried removing all libraries (that we could find), which didn't help.
I should also point out that this occurred with two new clones, not from
pulls, so I'm not entirely sure how it can be a lingering problem from a
previous version.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149725441
.

also, which account are you using?
On Tue, Oct 20, 2015 at 6:55 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Tried removing all libraries (that we could find), which didn't help.
I should also point out that this occurred with two new clones, not from
pulls, so I'm not entirely sure how it can be a lingering problem from a
previous version.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149725441
.

OK, @pcbend your instructions worked. I'm not sure which dictionaries we must've missed. Thanks.

I pulled a fresh clone into ~/packages/temp on grsmid01.  It compiles on
runs.
root-config --version
5.34/28
If you tell me a machine and or account name, i can snoop a bit.
On Tue, Oct 20, 2015 at 7:03 PM, Peter<EMAIL_ADDRESS>wrote:

also, which account are you using?
On Tue, Oct 20, 2015 at 6:55 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Tried removing all libraries (that we could find), which didn't help.
I should also point out that this occurred with two new clones, not from
pulls, so I'm not entirely sure how it can be a lingering problem from a
previous version.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149725441
.

no problem, glad it worked.
On Tue, Oct 20, 2015 at 7:08 PM, jhenderson88<EMAIL_ADDRESS>wrote:

OK, @pcbend https://github.com/pcbend your instructions worked. I'm not
sure which dictionaries we must've missed. Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727291
.

I think it might be worth putting that command into the clean target, we’ve had this problem come up many times now.

On Oct 20, 2015, at 7:08 PM, pcbend<EMAIL_ADDRESS>wrote:
no problem, glad it worked.
On Tue, Oct 20, 2015 at 7:08 PM, jhenderson88<EMAIL_ADDRESS>wrote:

OK, @pcbend https://github.com/pcbend your instructions worked. I'm not
sure which dictionaries we must've missed. Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727291
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727377.

sounds fine to me, it is also good to be aware stray .cxx files will muck
up the make as well...
On Tue, Oct 20, 2015 at 7:10 PM, Ryan Dunlop<EMAIL_ADDRESS>wrote:

I think it might be worth putting that command into the clean target,
we’ve had this problem come up many times now.

On Oct 20, 2015, at 7:08 PM, pcbend<EMAIL_ADDRESS>wrote:
no problem, glad it worked.
On Tue, Oct 20, 2015 at 7:08 PM, jhenderson88<EMAIL_ADDRESS>wrote:

OK, @pcbend https://github.com/pcbend your instructions worked. I'm
not
sure which dictionaries we must've missed. Thanks.
—
Reply to this email directly or view it on GitHub
<
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727291

.

—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727377
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727575
.

Yep. I think the SiliHit you pointed out is not part of the git though.

On Oct 20, 2015, at 7:12 PM, pcbend<EMAIL_ADDRESS>wrote:
sounds fine to me, it is also good to be aware stray .cxx files will muck
up the make as well...
On Tue, Oct 20, 2015 at 7:10 PM, Ryan Dunlop<EMAIL_ADDRESS>wrote:

I think it might be worth putting that command into the clean target,
we’ve had this problem come up many times now.

On Oct 20, 2015, at 7:08 PM, pcbend<EMAIL_ADDRESS>wrote:
no problem, glad it worked.
On Tue, Oct 20, 2015 at 7:08 PM, jhenderson88<EMAIL_ADDRESS>wrote:

OK, @pcbend https://github.com/pcbend your instructions worked. I'm
not
sure which dictionaries we must've missed. Thanks.
—
Reply to this email directly or view it on GitHub
<
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727291

.

—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727377
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727575
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149727916.

So it seems I was overly hasty in thinking this was fixed, rather I just didn't notice the failure due to the '-j' option.
I am using my account on belodon, James is using his account on smilodon.
I will try commenting out the segments @r3dunlop suggested, and will also try compiling on my account on another machine to see if it's a local issue.

Or try the ROOT::Math::ParamFunctor constructor as well.

On Oct 20, 2015, at 7:21 PM, jhenderson88<EMAIL_ADDRESS>wrote:
So it seems I was overly hasty in thinking this was fixed, rather I just didn't notice the failure due to the '-j' option.
I am using my account on belodon, James is using his account on smilodon.
I will try commenting out the segments @r3dunlop https://github.com/r3dunlop suggested, and will also try compiling on my account on another machine to see if it's a local issue.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149730162.

Doesn't compile on midtig02.
Does compile on Horus and grsmid01 (both on my account).
Seems to be a local issue. There's a discrepancy in the root (sub)version. 5.34.21 on the machines it works on, 5.34.28 on the ones it doesn't.

Got those the wrong way around: 5.34.28 on the machines it works on, 5.34.21 on the ones it doesn't.

So both belodon and smilodon are using root version 5.34/21;
I would highly recommend moving to the latest (and last) version of root
5.34/34 or at least the version tiguser is using.
On Tue, Oct 20, 2015 at 7:25 PM, Ryan Dunlop<EMAIL_ADDRESS>wrote:

Or try the ROOT::Math::ParamFunctor constructor as well.

On Oct 20, 2015, at 7:21 PM, jhenderson88<EMAIL_ADDRESS>wrote:
So it seems I was overly hasty in thinking this was fixed, rather I just
didn't notice the failure due to the '-j' option.
I am using my account on belodon, James is using his account on smilodon.
I will try commenting out the segments @r3dunlop <
https://github.com/r3dunlop> suggested, and will also try compiling on my
account on another machine to see if it's a local issue.
—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149730162
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149731990
.

Looking into the dictionary, I’m fairly confident that it is an issue with one of those constructors that your ROOT version can’t handle.

On Oct 20, 2015, at 7:30 PM, pcbend<EMAIL_ADDRESS>wrote:
So both belodon and smilodon are using root version 5.34/21;
I would highly recommend moving to the latest (and last) version of root
5.34/34 or at least the version tiguser is using.
On Tue, Oct 20, 2015 at 7:25 PM, Ryan Dunlop<EMAIL_ADDRESS>wrote:

Or try the ROOT::Math::ParamFunctor constructor as well.

On Oct 20, 2015, at 7:21 PM, jhenderson88<EMAIL_ADDRESS>wrote:
So it seems I was overly hasty in thinking this was fixed, rather I just
didn't notice the failure due to the '-j' option.
I am using my account on belodon, James is using his account on smilodon.
I will try commenting out the segments @r3dunlop <
https://github.com/r3dunlop> suggested, and will also try compiling on my
account on another machine to see if it's a local issue.
—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149730162
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149731990
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149733818.

This is an update note in the 5.34.24 patch
Core
Put dictionary generated code into the ROOTDict namespace against a bug in MSVC 12, 13 https://connect.microsoft.com/VisualStudio/feedback/details/817601/connectcrash-long-file-causes-vc12-update-1-c-compiler-to-crash-works-in-vc11
This looks to me to be exactly what your problem is.
There are also a bunch of Tree and I/O fixes, some which include memory leaks of STL. https://root.cern.ch/root-version-v5-34-00-patch-release-notes https://root.cern.ch/root-version-v5-34-00-patch-release-notes So I think you are stuck unless you upgrade. I also seem to remember having problems with certain ways we dealt with trees before version 24.

On Oct 20, 2015, at 7:30 PM, pcbend<EMAIL_ADDRESS>wrote:
So both belodon and smilodon are using root version 5.34/21;
I would highly recommend moving to the latest (and last) version of root
5.34/34 or at least the version tiguser is using.
On Tue, Oct 20, 2015 at 7:25 PM, Ryan Dunlop<EMAIL_ADDRESS>wrote:

Or try the ROOT::Math::ParamFunctor constructor as well.

On Oct 20, 2015, at 7:21 PM, jhenderson88<EMAIL_ADDRESS>wrote:
So it seems I was overly hasty in thinking this was fixed, rather I just
didn't notice the failure due to the '-j' option.
I am using my account on belodon, James is using his account on smilodon.
I will try commenting out the segments @r3dunlop <
https://github.com/r3dunlop> suggested, and will also try compiling on my
account on another machine to see if it's a local issue.
—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149730162
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149731990
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149733818.

Updated to ROOT 5.34.34
Now get an error with TScaler, which was being played with this morning, so I guess different problem.
Compiling bin/AddToChannelNumber [ERROR]
libraries/libTGRSIFormat.so: undefined reference to `TScaler::Print(char const, unsigned int) const'
collect2: ld returned 1 exit status
make: ** [bin/AddToChannelNumber] Error 1

This error message is due to some incomplete/wrong merging. Just remove the Print method from TScaler.h or do 'git checkout include/TScaler.h'. This should have been fixed in the recent versions of the code, but it might have found it's way in trying to merge your old version with the current version.

Did I not merge that fix yesterday? I swear I did…

On Oct 20, 2015, at 9:22 PM, Vinzenz Bildstein<EMAIL_ADDRESS>wrote:
This error message is due to some incomplete/wrong merging. Just remove the Print method from TScaler.h or do 'git checkout include/TScaler.h'. This should have been fixed in the recent versions of the code, but it might have found it's way in trying to merge your old version with the current version.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149751974.

It's fixed in the code that is in the repository, but I think if you do a pull upstream on an older version it might get merged back in?

https://github.com/GRIFFINCollaboration/GRSISort/pull/529/files
But the timestamp of the code in the repository should be newer since I pushed the fix after the faulty merge.

Oh I think I see what you are saying. If they tried to do a pull rather than a fetch. We should put up instructions for updating code without merging.

There now appears to be the following error, related to the GetXXXHit functions for many of the detectors (can't confirm it's for all of them):
libraries/TGRSIAnalysis/TTip/TTip.cxx: In member function ‘TTipHit* TTip::GetTipHit(const int&)’:
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected unqualified-id before ‘&’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected ‘)’ before ‘&’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected ‘{’ before ‘&’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected primary-expression before ‘||’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected primary-expression before ‘)’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected ‘;’ before ‘)’ token
This is with ROOT v5.34.34. Seems to be related to the error reporting in the various GetHit functions.

I just pulled the newest version on both OSX and CentOS and cannot reproduce these errors. Are you sure that the Tip code is the same as what is on the repo and that it wasn’t merged with something you were working on?

On Oct 21, 2015, at 1:49 PM, jhenderson88<EMAIL_ADDRESS>wrote:
There now appears to be the following error, related to the GetXXXHit functions for many of the detectors (can't confirm it's for all of them):
libraries/TGRSIAnalysis/TTip/TTip.cxx: In member function ‘TTipHit* TTip::GetTipHit(const int&)’:
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected unqualified-id before ‘&’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected ‘)’ before ‘&’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected ‘{’ before ‘&’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected primary-expression before ‘||’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected primary-expression before ‘)’ token
libraries/TGRSIAnalysis/TTip/TTip.cxx:105: error: expected ‘;’ before ‘)’ token
This is with ROOT v5.34.34. Seems to be related to the error reporting in the various GetHit functions.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149975447.

I get the same error with a direct clone of the master (GRIFFINCollaboration) version.

Can you remove the exception handling and see if it compiles? If that's the reason, you guys are running some seriously old gcc over there.

On Oct 21, 2015, at 2:05 PM, jhenderson88<EMAIL_ADDRESS>wrote:
I get the same error with a direct clone of the master (GRIFFINCollaboration) version.
—
Reply to this email directly or view it on GitHub.

Also try adding the stdexcept header.

On Oct 21, 2015, at 2:05 PM, jhenderson88<EMAIL_ADDRESS>wrote:
I get the same error with a direct clone of the master (GRIFFINCollaboration) version.
—
Reply to this email directly or view it on GitHub.

Do you have a machine, account, and filename?
On Oct 21, 2015 2:07 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Can you remove the exception handling and see if it compiles? If that's
the reason, you guys are running some seriously old gcc over there.

On Oct 21, 2015, at 2:05 PM, jhenderson88<EMAIL_ADDRESS>wrote:
I get the same error with a direct clone of the master
(GRIFFINCollaboration) version.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149980208
.

I am running this on belodon, my account (jhenderson) in Programs/GRSISort.
@jsmallcombe is getting the same error on his account on smilodon.
I'll try removing the exception handling.

It compiles if I comment out the exception handling for each detector hit function.

Including stdexcept seems to have worked.

#include  is needed to use std::out_of_range&
I am not sure how the newer complies the hits with out it... but including
it in the hits.cxx file allows me to compile on belodon.
On Wed, Oct 21, 2015 at 2:23 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Including stdexcept seems to have worked.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149984488
.

Newer c++ probably just assumes you want it included…
Can someone include the stdexcept header into the relevant files? I have other things to deal with right now.

On Oct 21, 2015, at 2:25 PM, pcbend<EMAIL_ADDRESS>wrote:
#include  is needed to use std::out_of_range&
I am not sure how the newer complies the hits with out it... but including
it in the hits.cxx file allows me to compile on belodon.
On Wed, Oct 21, 2015 at 2:23 PM, jhenderson88<EMAIL_ADDRESS>wrote:

Including stdexcept seems to have worked.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149984488
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/531#issuecomment-149985104.


Added functionality to set a default date.

If default_date is set{
If field is empty, uses default_date
If field has a value, uses value
}
If default_date is empty, defaults to today.

Closing.


Method which returns the lines of a CSV file as a Java 8 stream

I am thinking of something very similar to the lines method of BufferedReader: link
Would be very helpful to enable working with the lines in a parallel way.

Please note, that this requires all the cell processors are thread safe - at least the ones that deal with data from multiple rows such as the unique processor. But apparently, also date parsing requires synchronization.

BufferedReader.lines() method returns serial stream (not parallel). Using a Stream is lot easier than reading objects into a List. If not for parallel, serial execution could certainly benefit from this change.


⚠ Empornium has degraded performance

In 4c7712e, Empornium ($EMP) experienced degraded performance:

HTTP code: 500
Response time: 1048 ms

Resolved: Empornium performance has improved in 7537c8d after 6 minutes.


ArtifactDataWriter should only save tracked files

ArtifactDataWriter._save_ currently adds all files in its temporary directory to the tar file. It should only add files that were created with create_file in case other files are added to the temp dir through some other mechanism.

Closing as ArtifactDataWriter no longer exists.


Have the default or example values of Array  in Pojo

Is there a way to get the default value of the array in the pojo ?
For example my default json is :
{
  "checked": false,
  "dimensions": {
    "width": 11,
    "height": 10
  },
  "id": 1,
  "name": "A xxxx door",
  "price": 12.5,
  "tags": [
    "home",
    "green"
  ]
}

I would like to have the values of tags in the pojo as it is a default value
Attaching the schema as well .
schema.txt

Sorry, the example JSON is supposed to be a shortcut to generate types that can represent it. If you want more advanced features, like defaults, create a schema.


Record Square-calculated processing fee in payments

Can be retrieved from the Transactions API after the checkout completes

Also add a property/column/whatever with the "collected" amount for future reporting purposes.


Add pre-commit hooks

_Originally posted by @real-yfprojects in a comment to issue #1:

Will you add pre-commit hooks?

This is what I would use
repos:
  - repo: https://github.com/pre-commit/pre-commit-hooks
    rev: f71fa2c1f9cf5cb705f73dffe4b21f7c61470ba9 # frozen: v4.4.0
    hooks:
      # check file system problems
      - id: check-case-conflict
      - id: check-symlinks
      - id: destroyed-symlinks

      # unify whitespace and line ending
      - id: trailing-whitespace
        args: [--markdown-linebreak-ext=md]
      - id: end-of-file-fixer
      - id: mixed-line-ending

      # sort requirements.txt files
      - id: requirements-txt-fixer

      # python code
      - id: fix-encoding-pragma

      # check more
      - id: check-yaml
      - id: check-toml
      - id: check-xml
      - id: check-executables-have-shebangs
      - id: check-merge-conflict

  - repo: https://github.com/python-poetry/poetry
    rev: "fb493f2e80a11403fa289617a703ae622d4ccd75" # frozen: 1.3.0
    hooks:
      - id: poetry-check

  - repo: https://github.com/floatingpurr/sync_with_poetry
    rev: 6fd6194c7bbd629b18a7bcd7a4a38a57f128b451 # 0.4.0
    hooks:
      - id: sync_with_poetry
        files: ".pre-commit-config.yaml|poetry.lock"

  - repo: https://github.com/pycqa/isort
    rev: 5.12.0
    hooks:
      - id: isort
        name: isort (python)

  - repo: https://github.com/psf/black
    rev: 22.3.0
    hooks:
      - id: black

  - repo: https://github.com/pre-commit/mirrors-prettier
    rev: "cafd5506f18eea191804850dacc0a4264772d59d" # frozen: v3.0.0-alpha.4
    hooks:
      - id: prettier

  # only when we are using rST based docs
  - repo: https://github.com/rstcheck/rstcheck
    rev: "77751d7a7d81a5d47aa344d802f41809c4d063c0" # frozen: v6.1.1
    hooks:
      - id: rstcheck
        additional_dependencies: [sphinx]
        args: ["--config", "docs/rstcheck.cfg"]

  - repo: https://github.com/abravalheri/validate-pyproject
    rev: cc27459d0f843a9333dd181e7451a8d041591a25 # frozen: v0.12.1
    hooks:
      - id: validate-pyproject
        files: pyproject.toml$

  # your favourite linters, I personally use pylama
  - repo: local
    hooks:
      - id: pylama
        name: pylama
        entry: pylama
        language: system
        types: [python]

# configuration for the pre-commit.ci bot
# only relevant when actually using the bot
ci:
  autofix_commit_msg: |
    [pre-commit.ci] auto fixes from pre-commit hooks

    for more information, see https://pre-commit.ci, https://pre-commit.com and
    the `.pre-commit-config.yaml` file in this repository.

  autofix_prs: true # default
  autoupdate_branch: "develop"
  autoupdate_commit_msg: |
    [pre-commit.ci] Autoupdate pre-commit hook versions.

    for more information, see https://pre-commit.ci, https://pre-commit.com and
    the `.pre-commit-config.yaml` file in this repository.

  submodules: false # default

This is the basis for further contributions. I can open a PR setting up pre-commit (+ci) and resolving #14. So I can get started with other tasks.

Closed in #16.


Bastion can self repair when dead

Created by: MrKingMichael

moved from ow1_emulator_backup#610

mentioned in issue ow1_emulator_backup#609

mentioned in merge request ow1_emulator_backup!127

mentioned in merge request ow1_emulator_backup!128

Created by: MaxwellJung
@MrKingMichael reference this issue from now on instead of the duplicate


Identify driver variants

Match all mutations against known specific variants in CIViC
Also match non-synonymous coding variants against whitelist of known oncogenes (e.g. TP53, MYC, KRAS, NRAS, &c).
Plan: use Tier 1 oncogene list from COSMIC: https://cancer.sanger.ac.uk/cosmic/census?tier=1

This is being done in Vaxrank now


Overhauled the formatting and designs.

The intention is to get the module into a professional looking public framework, something that is more akin to JUCE's style and overal approach.
There are many changes here. A quicklist:

Stylistically changed many explicit variable types to use auto.
Sprinkled const-ref here and there, where necessary.
Flipped the wacky Yoda conditions.
Added a .gitattributes to make things consistent for cross-platform development.
Fixed up how third-party warnings are managed by adding a .h and .cpp to start/finish or push/pop ignoring warnings.
Lots of macro changes to use what JUCE offers, instead of the hand-rolled shenanigans.
Updated the .gitignore so the repo can cope with vscode and MSVC stuff.
Fixed Duktape's C++11 detection for MSVC.
Made Doxygen comments follow JUCE's conventions, and also reformatted them here and there.
Fixed up a lot of the C++11 (and up) std::function stuff to make it more readable.
Added more project support to the unit tests.
Added a JUCE module compatible macro to be able to enable/disable unit tests from the Projucer and its Cmake equivalents.
Tried to avoid implicit bool and pointer usage (you'll see explicit != nullptr and == nullptr comparisons now).

@nick-thompson Have a gander...

@jrlanglois this looks great. A Herculean effort!

In regards to the various formatting changes, an ideal thing here would be a clang-format config. I think there are some out in the wild on the JUCE forum which follow the JUCE style guide. Obviously this is separate from the overall refactors preferring auto etc which I think look great. Appreciate it'd be rather painful to separate those refactors from formatting though ....

Yeah I think clang-format and prettier config in repo, along with some checks in CI for compliance and probably some easily-initialised pre-commit hooks will be super valuable.  No reason to waste anybody's time worrying about formatting down the line when a lot of that burden can be tooled away.  Seems you've already decided to do this anyway https://github.com/nick-thompson/blueprint/issues/24

Thanks for the feedback folks! I'm glad to see there's interest. As I mentioned in my original post - treat this T H I C C PR as merely conceptual. Though looking back on it, it's fairly straightforward to break all of this down into sizeable chunks.

@JoshMarler

In regards to all the empty doxygen additions here. (@nick-thompson will correct me if I'm wrong on this one). I think the idea is that users will very rarely need to read into C++/Native other than View and ReactApplicationRoot.

I'd like to make the case that JUCE users will be interested in this, what with it being a JUCE module... This means C++ will likely be the first thing people think of, particularly when it comes to rolling out their own C++ classes for the JS mechanisms to interact with. Documentation will be good to have in place and will make it more digestible.
This might be less useful in granular terms (eg: ShadowView), but for the classes that users are most likely to touch it seems worthwhile.
Also, keeping in mind the freshness and early stages of this module, docs might help debug when things go awry.

Thanks for the feedback folks! I'm glad to see there's interest. As I mentioned in my original post - treat this T H I C C PR as merely conceptual. Though looking back on it, it's fairly straightforward to break all of this down into sizeable chunks.
@JoshMarler

In regards to all the empty doxygen additions here. (@nick-thompson will correct me if I'm wrong on this one). I think the idea is that users will very rarely need to read into C++/Native other than View and ReactApplicationRoot.

I'd like to make the case that JUCE users will be interested in this, what with it being a JUCE module... This means C++ will likely be the first thing people think of, particularly when it comes to rolling out their own C++ classes for the JS mechanisms to interact with. Documentation will be good to have in place and will make it more digestible.
This might be less useful in granular terms (eg: ShadowView), but for the classes that users are most likely to touch it seems worthwhile.
Also, keeping in mind the freshness and early stages of this module, docs might help debug when things go awry.

Totally fair comment. It would be nice if there was a clean single solution to generate docs for both sides of the API if possible. @nick-thompson, any thoughts on this?

Wow! @jrlanglois herculean effort indeed, very very much appreciated. And cheers to each of you for the discussion here.
High level comments: yea clang-format + prettier + automated clang-tidy/whatever CI checks is definitely the sustainable approach here, and one that we've planned to do but not gotten around to. Documentation, yea, @JoshMarler said it well; we're definitely aligning behind the idea of keeping the docs in one place, and that the most of the documentation will (and should) be geared towards the js side, so I'm starting to think it would be more maintenace than value to also support doxygen for the C++ side. That said, adding those docblock comments will indeed be helpful for contributors looking to understand the project, so I'm in favor of at least keeping up with our comments in the code!
@jrlanglois I see the breakout PRs, I'll go through and address each individually in more detail. Shall we consider this one closed then?

Ah, misread my notifications, I'm seeing now that those were issues opened, not breakout PRs! Ignore the end of my previous comment then :)
I'll read through the issues and leave comments in detail where I have them though. And yes, to @JoshMarler's other point, I think breaking this down into bite sized PRs will be the way forward!


Feature/prepml

📚 Documentation preview 📚: https://anemoi-inference--47.org.readthedocs.build/en/47/

I imagine this PR is to be merged after #33 ?


in windows browser(chrome,ie,edge,firefox), refresh page, then router leave and route to /

I have build a web app by vuejs with vur-router.
my router/index.js is below:

after build the app, it can be run under nginx server well.
But when I open a page is not '/home' (such as '/myLadings') in any browser in windows platform, then refresh this page , the router will be route to the route path '/', then to '/home'.
But this will not happen in mac or other linux platform.

yeah，I have the same problem in windows system. when open in new window，it will redirect to default page.


Sort all the python file imports

Signed-off-by: Tarun Kumar<EMAIL_ADDRESS>

Can you test it with Jenkins?

https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/view/RHODS_Quality_Gates/job/rhods-smoke/1871

failure is not related to this change

https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-smoke/1896/console


Not modern any more?

Thanks for the source for a real app. I just want to learn some from you but I find that EGOImageView is used instead of SDWebImage. So I think it's an old source right?

Hi, thanks for reaching out!
EGOImageView is indeed quite an old source now, but I've kept it because I like how simple it is to use. To be fair, I was thinking of changing it to SDWebImage. Just haven't found the time to do it yet. So to answer your question once and for all: EGO is old, the movies app, not so much ;)

There you go, no EGOImageView anymore :) https://github.com/KMindeguia/movies/commit/914e358fbed1f10ae115aca76122dfb3efc55b9a

Great quick hand👍


Update free-courses-pt_BR.md

What does this PR do?
Remove Resource(s)
For resources
free-courses-pt_BR.md
Description
This course does not exist anymore
Why is this valuable (or not)
How do we know it's really free?
For book lists, is it a book?
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

Thanks for doing the necessary work of keeping this list up to date!

It's a pleasure to help @eshellman  😄


Add "Steps to contribute" in the readme file.

Hi, i would really appreciate it if you assigned this issue to me, thanks!

Go ahead @SiddhiKhade

You can make two PRs.
The first one is by updating the readme and the second one is by adding your profile.

Anyone else wanna work on this issue.

i want to wor on this issue

Go ahead @sayan3270

Can I work on this issue?

I will add step by step guide on how to fork, clone, edit and make a pull request.
I will add what should be edited in data.json.

If this is good enough please assign this to me.

Hey @dubeyanant
This issue has already been assigned to @sayan3270
If @sayan3270 does not raise a pull request by the end of today then I will assign it to you.


How to trace the gorm's activity for better visibility?

Hi,
Thanks for the awesome project, i used to use gorp, and recently turn to gorm for the more friendly developer interface really helps. One way I liked gorp a lot is you could see every action it performs, especially thos transaction begin/rollback events, is there any easy way to accomplish this?

You want to see sql queries then
db.LogMode(true)

This method did help, but seems I need to modify the database/sql package to see more output. Thanks.


Add readline definitions

hmm, negative singleton number types should work: #776

Looks like it's working now, must have done something wrong. Updated.


Not able to use a referenced iOS binding project

We created an iOS binding project containing a .framework native reference.
Our .NET MAUI app now references the iOS binding project, but the namespaces used in the ApiDefinitions.cs and StructsAndEnums.cs (created with ObjectiveSharpie) will not get resolved in our MAUI app.
We tried a lot of things, but it seems not to work at all. Are there one or two positive examples of binding iOS native frameworks?
Thanks...

Replaced by #1514


refactor(compress): using compression pool

refactor(compress): using compression pool to reduce GC
Change
add compression pool
resue compression pool for reader

@xuthus5 please help review


"TS6143 --allowJs is not set" error but only on one setup

TypeScript Version:  2.2
We have several machines with the same Angular 2 + ASP.NET Core 1.6 project on them. All of the setups are similar as far as we can say and one of those VS.NET setups is having this error on build and we couldn't figure out what's different/missing:
Error	TS6143	Build:Module './src/common' was resolved to<EMAIL_ADDRESS>but '--allowJs' is not set.
<EMAIL_ADDRESS>13

The same project builds and runs fine on other setups. Here's what they all have common:

VS.NET 2017 15.2
TypeScript 2.2
.NET SDK 1.0.4

tsconfig.json is in the root folder of the project.
tsconfig.json:
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": [ "es2015", "dom" ],
    "suppressImplicitAnyIndexErrors": true
  },
  "exclude": [
    "node_modules",
    "wwwroot/Application/Models/Custom/**/*",
    "wwwroot/Application/Models/Generator/**/*",
    "wwwroot/Application/**/*.js",
    "wwwroot/Application/**/*.js.map"
  ]
}

What could be wrong with this problematic machine?

Seems like you must have different node_modules folder contents. Try setting up a package-lock.json and making sure you have identical NPM modules installed

Yes the problem was incomplete node_modules folder. We cleared cache, node_modules and restore clean and it works now.


[Help Wanted] Add "PDF" to Options menu to export pages to PDF

This would be adding the ability to export documentation pages in .rst to PDF, see previous discussion: https://github.com/mattermost/docs/issues/85#issuecomment-207398423
It would be nice if there was a way to export from .md files as well, but we can also do the work to convert those to .rst. The .rst format has more formatting options than markdown, and there are tools to help with conversion so it's probably good to do. The downside is that markdown is more popular.

Can i get some more information about this issue like what document should need to update and so on..

@wiersgallak - We don't provide Mattermost Product Documentation in a PDF format today because Mattermost docs are updated at regular interviews, and it's too easy for generated PDFs to become outdated. Is PDF availability something we want to consider for the future?

I'm voting against PDF versions for that exact reason. Our in-product help is a good example of static help that is out of date very quickly (but not anymore, thanks to you @cwarnermm!)


[Bug Report]: Image positioning problem with PDF export

Describe the Bug
The positioning of the images with the PDF export is superimposed with the text.
Perhaps, an adjustment problem with the page format!
The problem and random, it occurs after several manipulations:
Resizing / Alignment
Steps to Reproduce
Go to "https://demo.bookstackapp.com/books/bookstack-demo-site/page/mixed-content-example-page#bkmrk-full-width-image"
Cliquez sur Exporter
Sélectionnez PDF
Vérifier le PDF téléchargé
Expected Behaviour

Screenshots or Additional Context

Browser Details
No response
Exact BookStack Version
v22.10.2
PHP Version
7.4.26
Hosting Environment
wampserveur 3.2.6 - 64 bit

There is a problem with the pdf export, it does not respect the page structure at all when it comes to how the images are aligned.


Terraform apply not working with different policy_mode

{
    "type": "Microsoft.Authorization/policyDefinitions",
    "name": "Key-Vault-secrets-should-have-expiration-date",
    "properties": {
      "displayName": "Key Vault secrets should have an expiration date",
      "policyType": "Custom",
      "mode": "Microsoft.KeyVault.Data",
      "description": "Secrets should have a defined expiration date and not be permanent. Secrets that are valid forever provide a potential attacker with more time to compromise them. It is a recommended security practice to set expiration dates on secrets.",
      "metadata": {
        "version": "1.0.2",
        "category": "Key Vault"
      },
      "parameters": {
        "effect": {
          "type": "String",
          "metadata": {
            "displayName": "Effect",
            "description": "'Audit' allows a non-compliant resource to be created, but flags it as non-compliant. 'Deny' blocks the resource creation. 'Disable' turns off the policy."
          },
          "allowedValues": [
            "Audit",
            "Deny",
            "Disabled"
          ],
          "defaultValue": "Audit"
        }
      },
      "policyRule": {
        "if": {
          "allOf": [
            {
              "field": "type",
              "equals": "Microsoft.KeyVault.Data/vaults/secrets"
            },
            {
              "field": "Microsoft.KeyVault.Data/vaults/secrets/attributes.expiresOn",
              "exists": false
            }
          ]
        },
        "then": {
          "effect": "[parameters('effect')]"
        }
      }
    }
  }

This is the policy with different mode.Plan is successful. But during apply getting below error
Error: creating/updating Policy Definition "Key-Vault-secrets-should-have-expiration-date": policy.DefinitionsClient#CreateOrUpdateAtManagementGroup: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidProviderNameInPolicyAlias" Message="The policy definition 'Key-Vault-secrets-should-have-expiration-date' rule is invalid. The provider 'Microsoft.KeyVault.Data' referenced by the 'field' property 'Microsoft.KeyVault.Data/vaults/secrets/attributes.expiresOn' of the policy rule doesn't exist."
│
│   with module.Key-Vault["Key-Vault-secrets-should-have-expiration-date"].azurerm_policy_definition.def,
│   on ....\modules\definition\main.tf line 1, in resource "azurerm_policy_definition" "def":
│    1: resource azurerm_policy_definition def {
│
╵
╷
│ Error: creating/updating Policy Definition "Key-Vault-keys-should-have-expiration-date": policy.DefinitionsClient#CreateOrUpdateAtManagementGroup: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidProviderNameInPolicyAlias" Message="The policy definition 'Key-Vault-keys-should-have-expiration-date' rule is invalid. The provider 'Microsoft.KeyVault.Data' referenced by the 'field' property 'Microsoft.KeyVault.Data/vaults/keys/attributes.expiresOn' of the policy rule doesn't exist."
│
│   with module.Key-Vault["Key-Vault-keys-should-have-expiration-date"].azurerm_policy_definition.def,
│   on ....\modules\definition\main.tf line 1, in resource "azurerm_policy_definition" "def":
│    1: resource azurerm_policy_definition def {
Not able to resolve

I have ran tests with both the built-in and custom definitions and can confirm the built-in works due to the Mode having more permissions to view Microsoft.KeyVault.Data.

When I try to create the custom definition with the same mode I receive the below error:
module "keyvault_secret_expiration" {
  source              = "..//modules/definition"
  policy_name         = "keyvault_secret_expiration"
  policy_category     = "Key Vault"
  policy_mode         = "Microsoft.KeyVault.Data"
  management_group_id = data.azurerm_management_group.org.id
}

module "team_a_mg_keyvault_secret_expiration" {
  source            = "..//modules/def_assignment"
  definition        = module.keyvault_secret_expiration.definition
  assignment_scope  = data.azurerm_management_group.team_a.id
  assignment_effect = "Audit"
}

Error: creating/updating Policy Definition "keyvault_secret_expiration": policy.DefinitionsClient#CreateOrUpdateAtManagementGroup: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidPolicyDefinitionMode" Message="The creation of custom policy definition using mode 'Microsoft.KeyVault.Data' is not allowed. This mode is allowed only in built-in policy definitions."

You can however include any built-in definition (with restricted modes) to your custom initiatives as seen in this example
data "azurerm_policy_definition" "key_vault_secret_exp_builtin" {
  name = "98728c90-32c7-4049-8429-847dc0f4fe37"
}

Thanks it worked :)


Recording in archive

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Can I make recording in archive default behaviour without to have specify it all the time? As in --download-archive archive.txt
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
/

Create a config file and add --download-archive archive.txt to it


Table: Add table border prop

TODO

[x] Documentation
[x] Tests
[ ] Experimental evidence (required for Masonry changes)
[ ] Accessibility checkup

With border:

Did not update CHANGELOG.md since #849 has landed


DEV: LOG: JUnit Testing for WMLS_GetFromStore

EPIC:
#361 Log CRUD Implementation
Sizing:
M (2-3 Days)
Priority:
3
(Junit Test for GetFromStore should completed after GetFromStore to have something to work with)
Description:
This is the "R" in "CRUD".
NOTE:
-->Do NOT put non-WITSML into the WITSML Library; always can use the Library, however..
4. Refer to:
https://engdmzprism.portal.azure-api.net/docs/services/democore-Slb-Prism-Core-Service-ChannelReader-4/operations/Channels_PostDepthBoundaryAsync
This is the Swagger, and reveals the order in which things need to be done.

We hammered out the interface between LogConverterExtended & GetFromStore; changes were required on both sides, so the JUnit testing will have to change.

Pending review/ETA for close is EOD 5/2

Reopened to capture additional scope.

Junit test cases added for GetFromStore and this card can be closed.


Update CRDs

Update CRDs from enterprise

/merge-when-ready release-note-not-required docs-not-required delete-branch

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and delete the branch after I've merged it.


Multiple agent support in CLI

This PR updates the CLI to support deploying multiple agents per environment.
New commands:

list: lists all agents in the env
delete: deletes a given agent

Updated commands:

deploy: adds -s (slug) option (can be set by env variable as well)
develop: confirms develop when there are deployed agents

npx flatfile list

npx flatfile delete

npx flatfile deploy -s <slug>

npx flatfile deploy (no slug passed, but multiple listeners already present)

npx flatfile develop (when an environment has agents it requests confirmation to proceed)

Also adds an extractor listener example

Awesome description, and the screenshots are 👩🍳 !!

Now that I'm seeing it, I'm debating here is if we should clarify the commands a bit - should they be delete-agent (with a some kind of shorthand like da), list-agent (la) , etc
Wondering if as we add things here, if list, delete are too vague. We had a customer trying to add namespaces to environments and I'm wondering if some time we'll want to list environments, namespaces, spaces etc...
Thoughts @meritmalling?

Now that I'm seeing it, I'm debating here is if we should clarify the commands a bit - should they be delete -agent (with a some kind of shorthand like da), list -agents (la) , etc Wondering if as we add things here, if list delete are too vague. We had a customer trying to add namespaces to environments and I'm wondering if some time we'll want to list environments, namespaces, spaces etc...
Thoughts @meritmalling?

Really good thinking, we don't want to box ourselves in! I'll update those two!

Closer! But thinking we have a generic list/delete and then a flag to specify -agents(is it better practice here to prefix - or --) vs other resources.
For example, Maybe we expand each command to list all resources available to the CLI in some kind of tree it out to navigate cleanly.

I think we can revert those last changes and add more list / delete functionality later. Let's get this out the door and add more soon!


Adding ROIAlign backwards for CPU

Adding ROIAlign backwards implementation for CPU.
Implemented using vision's CUDA implementation for the same purpose.
Currently the layers branch is not compiling.

Thanks for the PR!
I believe we still need to modify this file in order for the CPU dispatch to work?

@fmassa My bad! Fixing this.

@fmassa Fixed the python interface

Can you make sure flake8 runs successfully on your code? CI is failing since there are some linter errors.

@sampepose  I believe the flake8 issues are on my end. I need to fix them before merging the layers branch into master.
And we don't currently have a linter for C++ in torchvision, so this should be fine.

@xssChauhan could you please write a small python file that tests that the gradients are indeed computed correctly?
For that, you can use PyTorch torch.autograd.gradcheck. Also, when running the code, make sure that you are using double tensors - if you use float tensors, you'll have problems because of the lack of precision for finite differences differentiation that gradcheck uses to compare the gradients.
Once we know that the gradcheck is passing, I'll merge this patch.
Thanks!

@fmassa Will do so

@fmassa Layers branch is currently not compiling.
Here's the error:

Yes. Initially thought that it was introduced by me. Then tried on the layers branch, and found the same issue.

weird. Let me try compiling it (last time I checked it was working)

Ok, I know what's going on.
You need to have a source install from PyTorch. The bug you are facing was fixed in https://github.com/pytorch/pytorch/pull/6986

Understood. Would install PyTorch from source.
Was using pip installation till now. Thank you :)

@fmassa Installed PyTorch from source and then tried compiling the layers branch.
Here's the error that i got:
running install
running bdist_egg
running egg_info
writing torchvision.egg-info/PKG-INFO
writing dependency_links to torchvision.egg-info/dependency_links.txt
writing requirements to torchvision.egg-info/requires.txt
writing top-level names to torchvision.egg-info/top_level.txt
reading manifest file 'torchvision.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found under directory '*'
warning: no previously-included files matching '*.py[co]' found under directory '*'
writing manifest file 'torchvision.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
running build_ext
building 'torchvision._C' extension
gcc -pthread -B /home/shikhar/anaconda3/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/shikhar/Documents/vision-org/torchvision/csrc -I/home/shikhar/anaconda3/lib/python3.6/site-packages/torch/lib/include -I/home/shikhar/anaconda3/lib/python3.6/site-packages/torch/lib/include/TH -I/home/shikhar/anaconda3/lib/python3.6/site-packages/torch/lib/include/THC -I/home/shikhar/anaconda3/include/python3.6m -c /home/shikhar/Documents/vision-org/torchvision/csrc/vision.cpp -o build/temp.linux-x86_64-3.6/home/shikhar/Documents/vision-org/torchvision/csrc/vision.o -DTORCH_EXTENSION_NAME=_C -std=c++11
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
gcc -pthread -B /home/shikhar/anaconda3/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/shikhar/Documents/vision-org/torchvision/csrc -I/home/shikhar/anaconda3/lib/python3.6/site-packages/torch/lib/include -I/home/shikhar/anaconda3/lib/python3.6/site-packages/torch/lib/include/TH -I/home/shikhar/anaconda3/lib/python3.6/site-packages/torch/lib/include/THC -I/home/shikhar/anaconda3/include/python3.6m -c /home/shikhar/Documents/vision-org/torchvision/csrc/cpu/ROIAlign_cpu.cpp -o build/temp.linux-x86_64-3.6/home/shikhar/Documents/vision-org/torchvision/csrc/cpu/ROIAlign_cpu.o -DTORCH_EXTENSION_NAME=_C -std=c++11
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
/home/shikhar/Documents/vision-org/torchvision/csrc/cpu/ROIAlign_cpu.cpp:226:66: error: macro "AT_ASSERT" passed 2 arguments, but takes just 1
   AT_ASSERT(!input.type().is_cuda(), "input must be a CPU tensor");
                                                                  ^
/home/shikhar/Documents/vision-org/torchvision/csrc/cpu/ROIAlign_cpu.cpp:227:64: error: macro "AT_ASSERT" passed 2 arguments, but takes just 1
   AT_ASSERT(!rois.type().is_cuda(), "rois must be a CPU tensor");
                                                                ^
/home/shikhar/Documents/vision-org/torchvision/csrc/cpu/ROIAlign_cpu.cpp: In function ‘at::Tensor ROIAlign_forward_cpu(const at::Tensor&, const at::Tensor&, float, int, int, int)’:
/home/shikhar/Documents/vision-org/torchvision/csrc/cpu/ROIAlign_cpu.cpp:226:3: error: ‘AT_ASSERT’ was not declared in this scope
   AT_ASSERT(!input.type().is_cuda(), "input must be a CPU tensor");
   ^
error: command 'gcc' failed with exit status 1

Ok, this is due to a recent change in PyTorch that modified the behavior of AT_ASSERT as you can see in https://github.com/pytorch/pytorch/pull/7104
I believe you can replace AT_ASSERT with AT_CHECK and it should compile.
And sorry for the troubles getting this branch to compile, as you can see PyTorch is evolving quite fast!

I'll do the changes.

Hey @fmassa
torchvision is now successfully compiling, but here's the issue that i am facing now:
Even the successful compilation does not seem to add layers or _C modules to torchvision.
Here are the steps that i took:

Install pytorch from source using the master branch and no cuda support.
Replace all the occurences of AT_ASSERT with AT_CHECK in nms_cpu.cpp and ROIAlign_cpu.cpp.
Install torchvision from source using layers branch

The build process throws no error.
In the shell:

Here are a couple of implementation details:

Using a conda environment

The build folder seems to have the compiled extension and the layers module

I dont know if it is relevant, but installing pytorch and vision from source has different effects

I have tried manually copying the contents of the build folder to the environment. The _C extension, is thus present in the environment package, but still does not appear in the terminal.

How can i fix this? Would be grateful for the help.

@fmassa My bad. from torchvision import pytorch seemed to do the trick. Thank you.

@xssChauhan is this ready for review? Did you manage to perform the gradcheck?

@fmassa The branch is currently not passing the gradcheck. I've been working on finding the issue.
My code is referenced from Caffe2 and vision's implementation of the same.
I recently stumbled upon this implementation that references caffe2 as well. Using the same parameters as in the link to run the gradcheck.

Since this PR seems to be abandoned, I have taken the liberty to add the backwards pass for CPU in #630.

Closing in favor of #630


nixos/freeradius : init - Added freeradius service

Inspired from the dhcpd service implementation
Only 2 configurations options at the moment:
enabled and path to configfile
folder networking has been chosen because radius is mainly used for network device and network authentication (e.g. WPA2 Entreprise)
Motivation for this change
Freeradius package is already supported by nix, but no service exists for nixos. This patch adds basic support to start the freeradius service.
Things done
I tested the service configuration in my personal nix installation successfully.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Closed by mistake? I see this PR was made from your master branch. It's a good idea to work on non-master branches for PRs.

Yes, I opened https://github.com/NixOS/nixpkgs/pull/34587 with the correct branch :)


Extended instruction tables are always regenerated even if there are no changes at all.

Hi,
Try to build Spirv-tools will always result in complete rebuild, because its cpp source files depends on "extended instruction tables" which are always regenerated even if up to date.

After switched my IDE from VS2019 to VS2015, problem solved. Seems like using CMake  with VS2019 will cause the problem.


Greeter card

A Personal greeter card that shows calendar events from calendar sensor and time of day and any additional sensor that the user wants
dynamic backgrounds from unsplash using their api lib already available
https://github.com/unsplash/unsplash-js
got a mock card layout as a suggestion

Can this be done with template sensors and picture-elements?

dont know yet reinstalled from the botched update that ballop pushed
On Tue, Jul 17, 2018 at 9:32 AM Marius<EMAIL_ADDRESS>wrote:

Can this be done with template sensors and picture-elements?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ciotlosm/custom-lovelace/issues/70#issuecomment-405487360,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACaIeFdz_2h6QamVDecVrFRAH8YrZgiDks5uHZKIgaJpZM4VQLto
.

can be done via picture elements


Determine and add an icon set to the site.

Determine and add an icon set to the site.

The choice was made to use the http://www.typicons.com/ icon set for its bold, rounded, and simple icons. The icons are used as an iconfont.


Design: Configurable Function Runtimes

When deploying with a given provider a nitric project needs to be able to provide more specific instructions for a functions deployment (i.e. deploy to a given service runtime e.g. Lambda/ECS Fargate/Lightsail).
Additional Considerations:

[ ] Add additional runtime specific configuration for functions (e.g. Provisioned concurrency for AWS lambda). Adding this consideration and these configuration options may be mutually exclusive across individual provider runtimes.

Acceptance Criteria:

[ ] A design proposal that allows an individual function to be deployed to a given runtime for a provider.

Example AWS configuration
name: my-aws-stack
provider<EMAIL_ADDRESS>config:
  # default function specs
  default:
    target: lambda
    memory: 256
    timeout: 15
  # TODO: Need a way to properly target a deployed function
  my-other-function:
    target: lightsail
    some-lightsail-property: ???

I could see categories of functions being useful too - e.g. 'small', 'medium', 'memory_optimized' - so it's quick to deploy a set of functions with similar hosting requirements. Should we consider changes to the handlers nitric.yaml property to match function types, then map those types to deployment configurations?

@jyecusch Do you see these categories being universal for all providers, unique to specific providers or configured as part of the stack using provider specific configuration?

I imagine the grouping being provider agnostic (project level), but the configuration of that group as provider specific (e.g. a 'large' function could be configured differently for AWS and Azure based on what config they offer)

Concepts from our design discussion:
Allow for named groups/categories of handlers.
nitric.yaml
name: diagram
handlers:
  - functions/*.ts
  - type: memory-optimized
    match: processing/*.ts
  - type: stateful
    match: services/*.ts

Map these named categories onto specific deployment targets and target configurations within stack files (allowing for provider and environment specific config).
dev-nitric.yaml
name: develop
provider: aws
region: ap-southeast-2
config:
  # default function specs
  default:
    target: lambda
    memory: 256
    timeout: 15
  # # TODO: Need a way to properly target a deployable function, currently names are inferred from files
  # # but dockerfiles should be different to ensure they're re-usable.
  stateful:
    target: lightsail
    memory: 1024
    some-lightsail-property: ???
  memory-optimized:
    target: fargate
    memory: 2048
    some-fargate-property: ???


Optimise "for ... in (x, y, z)" into C array iteration

Cython already optimises the common idiom for ... in [x, y, z] into the slightly more efficient for ... in (x, y, z), and then uses direct tuple array indexing for the iteration.
This could be optimised even further by using a stack allocated C array instead of the Python tuple. That would also allow iteration over plain C values for uniform tuple types and could avoid any intermediate Python object creation. In order to support that, it is necessary to 1) replace the TupleNode by a new CArrayNode (or at least mark it as special) early in the IterationTransform, 2) apply the C array transformation to the for-loop (also in IterationTransform), and then 3) determine the actual array type in the analyse_types() method (probably object in most cases).

i want to help implement this. Can you guide me as i'm new to this.

Hmm, looking into this again after a while, I think it's a bit too complex for a "first issue", sorry. I removed the labels.
The description above pretty much lists what needs to be done and at what places to look in the code. I added a comment on testing.


Clearing and Rescheduling Transport.Timeline with Players

What are you trying to do?
The end goal is to use Transport.Timeline and multiple Player instances to schedule players to play different parts of clips at different times along the timeline. This includes players being reused to play earlier or later segments of their audio at different points on the timeline. I have used a very short clip in the codepen, but each player will be 5-10 minutes long in production.
E.g.
0:00 Player 1
0:10 Player 1 Stop
0:10 Player 2 Start
0:20 Player 2 Stop
0:20 Player 1 Start at 10s offset
...etc
Describe the bug
The bug occurs when synced players are scheduled with Tone.Transport.scheduleOnce() with the first argument of player.start() undefined. This is necessary as otherwise when the transport is paused and restarted, all players that have already been started play simultaneously.
If the timeline is cancelled (whether from 0 or from any point in the timeline) with Tone.Transport.cancel(0) and then new events are scheduled with Tone.Transport.scheduleOnce. The issue occurs when the Transport is restarted from 0 after this scheduling.
The error thrown is: Uncaught Error: The time must be greater than or equal to the last scheduled time". This error stems from StateTimeline.add (Tone.js line 310), but I can't work out why this happens as all events should have been cancelled before new events were added (so there shouldn't be any scheduled events).
I would consider disposing of the timeline but I worry that this might not be performant when the number of events to schedule reaches tens or hundreds (or more).
To Reproduce
Please see the codepen here: https://codepen.io/jamescqcampbell/pen/gOvbarK?editors=0010
To reproduce issue:

Start audio context
Press play (works fine)
Press stop
Click Change Timeline (just clears and reschedules the same audio timeline)
Press play (should throw an error)
If no errors press stop and change timeline again, reliably happens for me on the first or second try

Expected behavior
I would expect the timeline to be completely cleared by Tone.Transport.cancel(0) and to be able to reschedule events from 0s with no issues.
What I've tried
Previously I was only cancelling events on the timeline after the point at which edits were made. I switched to cancelling and rescheduling the entire timeline because of this issue but it didn't help.
I have looked into whether this issue was caused by not disposing of the Tone instance on component refresh but I don't think that this is the case.
Additional context
I would like to be able to dynamically set and reset the timeline within react. This is a core part of what I would like to build so I am keen to help get this resolved.
All player events need to be synced to and controlled by the timeline such that when played back it sounds like a continuous piece of audio rather than a series of clips.

Did u manage to fix this?

Sadly not, what I did instead was to:

Create a ToneAudioBuffers with each of my audio sources.
When scheduling, create a new player for each section of audio (with the source from the buffer). I.e. I didn't reuse the same player each time for this.
Dispose of all of the players when rescheduling, but keep the ToneAudioBuffers and use that as the basis of the new set of players for the new schedule.

This works, though seeking can be a bit flaky (if you have any thoughts there please let me know!)
If anyone does solve this issue I'd be keen to know!


Added my name to names.txt

My name is Paul Oyediran

Please I am sorry for all the trouble we have caused you but count it all joy. Your PR is about to be merged and you will be able to see your name on this url.
To enable me to do this, READ the README again carefully, update your code with the latest and push the update. I am here for you for the next 6 hours before I close the PR so you can initiate a fresh PR which will be easier to merge.


Responsive marketplace styles

Goes with https://github.com/UW-Madison-DoIT/angularjs-portal/pull/399

:+1:

Maybe a poor question: why are "Browse" styles here in uw-frame when the app directory browsing is an angularjs-portal feature?

That is a very good point. We do have less in angularjs-portal :)

Yea, I did have an uneasy feeling making that change. I think they were originally there to keep all responsive styles in one place, i.e. only need one media query. But I'm thinking it's time to ditch that idea and put these styles in marketplace.less in angularjs-portal. Good call @apetro.

I don't think having 2 media queries will break the bank will it?

Styles have been moved.

Sometimes less is more :+1:


Mapping MODS to RDF: Recommendations & Strategies

"Members of the Samvera MODS and RDF Descriptive Metadata Subgroup will discuss the recently released MODS to RDF Mapping Recommendations (https://goo.gl/SGCfev), an application profile that provides recommendations for mapping MODS XML metadata for digital objects to RDF Linked Data classes and properties using a range of widely-adopted RDF namespaces.
The result of a 30-month collaborative process involving participants from more than a dozen academic and public libraries, the recommendations includes a comprehensive mapping of MODS elements to RDF using real-world metadata use cases and hundreds of examples. The mappings emphasize properties from existing vocabularies that are already extensively used, such as Schema.org, Dublin Core, BIBFRAME, BIBO, RDA, FOAF, EDM, and LC Linked Data Service datasets.
This talk will include an overview of the Recommendations document and the process by which it was created; as well as a discussion of the difficulty of modeling complex metadata in RDF, and challenges to implementing the recommendations within Samvera, Fedora, and Hyrax-based systems."
Eben English<EMAIL_ADDRESS>Emily Porter<EMAIL_ADDRESS>

Confirmed 8/10  Recording OK

Both registered 8/14 - system info


Adds Amrit Science Campus, Kathmandu, Nepal

Website: https://amritcampus.edu.np/
College Page for CS/IT Faculty:
https://amritcampus.edu.np/departments/computer-science/

Provides Bachelor level IT course of 4 years (8-semesters).
The college has a valid microsoft teams id. Here is a screenshot of ms-teams

Email id: is at top left corner
Another from teams app.

@philipto kindly review, I'll be happy to provide any other required information.

@hemanta212 Thank you for the clarification. Pull request merged.


add deploy property token

Added deployment of Property Payment Token ("MockToken", "MTK") and included in Property Vault constructor.
Removed individual deployment scripts; all are now in combined script 00_deploy_property_rwa.ts
Minor type errors for gasPrices in hooks useProperyData.ts. Removed temporarily


watcher mod have only config.bin

Hello, you make awesome tool. But i have a problem. I can't monitoring server on map, no one vehicle or players i can't see.
When server start, in path @DayZServerManager creating new mod Scripts.pbo every time.
But inside this pbo i see only config.bin
When i try compile pbo from watcher_mod folder, and give it to server mod, i have error on start up, "Can't compile engine"
Can you check it?
Error log when i give pbo compiling by my self
`
Log D:\JNVanila\JNVanila\profiles\script_2021-10-11_04-10-39.log started at 11.10. 04:10:39
SCRIPT    (E): @"DayZServerManager/Scripts/Common,-1": Path not found
SCRIPT    (E): Can't compile "Engine" script module!
DayZServerManager/Scripts/Common: Path not found
`

And IsMissionClient() can't work with full vanilla server, this must replace with !GetGame().IsClient()
https://github.com/mr-guard/dayz-server-manager/blob/601d75ef1f233c9f99cfc36b21b77b6c7461d459/watcher_mod/DayZServerManager/Scripts/5_Mission/DayZServerManager/Game/DayZServerManagerWatcher.c#L82

Ok, i am trying to make PR))
Can you give example for hook on server start?
I need run my own bat script every time before server start.

Sorry for breaking promises but I won't be able to look into it this weekend.
I will update this issue once I find some spare time

Thanks for the pull request.
I have been busy the last few months, but I have been able to put in some work into the manager lately.
There will be a rewrite of the manager (soon) which should fix your issues
Please stay patient, I will keep you informed :)

Thank you, I am very glad to see your answer =)
And now we have new problems)

We cant add custom config key, like enableCfgGameplayFile = 1;
Map are broken, because cant resolve this addres https://senfo.space/dayzmaps/chernarusplus/data.json
And when map be working, they show wrong coordinates (just little lower then real position)
After few days of working, manager crashing without any logging.

But anywau, manager are awesome, hope you can make some cool update for fix it 👍

The first two issues should be resolved in v2.1.3
This is a intermediate version while I work on 3.0.0

Very glad to see you )) Thanks for new update.
Can you teach me little bit?
I wanna try to fix some bugs and test it on my own server.

To compile the typescript to JavaScript

npm run build

To compile and pack it into a exe

npm run buildAndPack

Note: this requires you to have mikeros tools installed and available in the PATH
Have a look in the package.json
It contains all build scripts

Many thanks, i will try it on weekend


Update collections.md

@m-mohr  @dthiex @ValentinaHutter @christophreimer @bschumac
I took the liberty of extending Daniel's pull request to come to a first draft of a harmonized collection spec.
I mostly limited myself to the things that I think are agreed upon already, so that we can quickly approve and have at least something on the web page.

Looks good to me, but I support Daniel's change requests.

@jdries Would you be okay with the suggestions in my comment?

Yes! I may need to look a bit further

I took the liberty of extending Daniel's pull request to come to a first draft of a harmonized collection spec.
I mostly limited myself to the things that I think are agreed upon already, so that we can quickly approve and have at least something on the web page.

Thanks a lot for adding some substance to this. Let's wait for someone from EODC to look at this and then merge it to have an initial version out and improve on it when necessary.

@dthiex agree with your proposal for angles as well. Will you extend it with the other angles? (I added some placeholders.)

Will you extend it with the other angles? (I added some placeholders.)

Not sure what exactly you mean here. How I see it, we use both the exact angles for sunAzimuth and sunZenith so I think there is no generalisation needed here so I'd say we can remove those from here.

This is fine for EODC, you can go ahead. Please let us know if you need any more information.

@jdries Not sure what exactly you mean here. How I see it, we use both the exact angles for sunAzimuth and sunZenith so I think there is no generalisation needed here so I'd say we can remove those from here.

@dthiex  indeed, so we only need to add the harmonized names, and explain that these are in fact the exact angles.
I think we can merge after that.

@jdries @m-mohr You are too fast for me... Thanks 🙇


Remove test support binder from being injected in start.spring.io and put new test binder in its place

There is a corresponding initilaizr issue - https://github.com/spring-io/start.spring.io/issues/385
Once it is resolved we can close this one.

I believe that has been addressed