cc: No valid input files specified, no output generated

I hope this is the correct place to post Jpype compile issues like this, if not I am all ears and will move this ASAP.
Bit of Background
I sent a pull request a few days ago in regards to having sunos in the platform.py file.
Now that I have cc installed, I am able to use that update. I put print statements in those lines to see that they were working that's the "SUN OS Detected" output.
Issue/Error
I am running into an issue with the _jpype module compiling, giving the following error:
cc: No valid input files specified, no output generated
error: command 'cc' failed with exit status 1

What I have done
I did some research, and was only able to find this post. Unfortunately, I was unable to tell if my issue was similar.
I tried creating my own Makefile with:
python setup.py build_ext --makefile
and even after changing the line endings to LR, instead of CRLR. I was still unable to compile. I stopped, for fear I was getting into the weeds.
System Info
uname -a returns:
SunOS krowvin 5.11 <IP_ADDRESS>.0 sun4v sparc sun4v
My version of cc that I am using is: Developer Studio 12.6
You can see at the end I tried manually running the command with CC (the C++ compiler for Solaris.
Terminal Output

Tried importing jpype to see what state it was in, sure enough no _jpype pyc file exists
Cleaned the build from my previously failed attempts
Attempted the Install
Manually tried to run using CC instead of cc

**(jpype) krowvin:~/jpype-master$**  python -c "import jpype; jpype.startJVM(jpype.get_default_jvm_path());import jpypex"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/krowvin/jpype-master/jpype/__init__.py", line 18, in <module>
    import _jpype
ModuleNotFoundError: No module named '_jpype'
**(jpype) krowvin:~/jpype-master$ python setup.py clean --all**
Falling back to provided JNI headers, since your provided JAVA_HOME "/mysoftware/java/java8/jdk1.8.0_202" does not provide jni.h
Falling back to provided JNI headers, since your provided JAVA_HOME "/mysoftware/java/java8/jdk1.8.0_202" does not provide jni.h
Falling back to provided JNI headers, since your provided JAVA_HOME "/mysoftware/java/java8/jdk1.8.0_202" does not provide jni.h
Found native jni.h at /mysoftware/java/java8/jdk1.8.0_202/include
SUN OS Detected
/krowvin/jpype/lib/python3.6/site-packages/setuptools/dist.py:331: UserWarning: Normalizing '1.2.2_dev0' to '1.2.2.dev0'
  normalized_version,
running clean
removing 'build/temp.solaris-2.11-sun4v.64bit-3.6' (and everything under it)
removing 'build/lib.solaris-2.11-sun4v.64bit-3.6' (and everything under it)
'build/bdist.solaris-2.11-sun4v.64bit' does not exist -- can't clean it
'build/scripts-3.6' does not exist -- can't clean it
**(jpype) krowvin:~/jpype-master$ python3 setup.py install**
Falling back to provided JNI headers, since your provided JAVA_HOME "/mysoftware/java/java8/jdk1.8.0_202" does not provide jni.h
Falling back to provided JNI headers, since your provided JAVA_HOME "/mysoftware/java/java8/jdk1.8.0_202" does not provide jni.h
Falling back to provided JNI headers, since your provided JAVA_HOME "/mysoftware/java/java8/jdk1.8.0_202" does not provide jni.h
Found native jni.h at /mysoftware/java/java8/jdk1.8.0_202/include
SUN OS Detected
/krowvin/jpype/lib/python3.6/site-packages/setuptools/dist.py:331: UserWarning: Normalizing '1.2.2_dev0' to '1.2.2.dev0'
  normalized_version,
running install
running bdist_egg
running egg_info
writing JPype1.egg-info/PKG-INFO
writing dependency_links to JPype1.egg-info/dependency_links.txt
writing entry points to JPype1.egg-info/entry_points.txt
writing requirements to JPype1.egg-info/requires.txt
writing top-level names to JPype1.egg-info/top_level.txt
package init file 'jpype/_pyinstaller/__init__.py' not found (or not a regular file)
reading manifest file 'JPype1.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.jar' under directory 'native'
warning: no files found matching '*.class' under directory 'native'
writing manifest file 'JPype1.egg-info/SOURCES.txt'
installing library code to build/bdist.solaris-2.11-sun4v.64bit/egg
running install_lib
running build_py
creating build/lib.solaris-2.11-sun4v.64bit-3.6
creating build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_core.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jthread.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/types.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_gui.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jpackage.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jcustomizer.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jio.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/protocol.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jarray.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_classpath.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_pykeywords.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jexception.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/__init__.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jcollection.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/dbapi2.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/beans.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jvmfinder.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jstring.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jclass.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jproxy.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jmethod.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jobject.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/nio.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/imports.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/pickle.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jinit.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
creating build/lib.solaris-2.11-sun4v.64bit-3.6/jpype/_pyinstaller
copying jpype/_pyinstaller/test_jpype_pyinstaller.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype/_pyinstaller
copying jpype/_pyinstaller/hook-jpype.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype/_pyinstaller
copying jpype/_pyinstaller/entry_points.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype/_pyinstaller
copying jpype/_pyinstaller/example.py -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype/_pyinstaller
copying jpype/_core.pyi -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jthread.pyi -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jio.pyi -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jstring.pyi -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
copying jpype/_jcollection.pyi -> build/lib.solaris-2.11-sun4v.64bit-3.6/jpype
running build_ext
Call build extensions
Jar cache is missing, using --enable-build-jar to recreate it.
  /mysoftware/java/java8/jdk1.8.0_202/bin/javac -cp lib/asm-8.0.1.jar -d build/temp.solaris-2.11-sun4v.64bit-3.6/org.jpype/classes -g:none -source 1.8 -target 1.8 -encoding UTF-8 native/java/org/jpype/JPypeUtilities.java native/java/org/jpype/JPypeKeywords.java native/java/org/jpype/JPypeSignal.java native/java/org/jpype/JPypeContext.java native/java/org/jpype/PyExceptionProxy.java native/java/org/jpype/html/AttrGrammar.java native/java/org/jpype/html/AttrParser.java native/java/org/jpype/html/HtmlWriter.java native/java/org/jpype/html/Parser.java native/java/org/jpype/html/HtmlGrammar.java native/java/org/jpype/html/HtmlParser.java native/java/org/jpype/html/HtmlHandler.java native/java/org/jpype/html/HtmlTreeHandler.java native/java/org/jpype/html/Html.java native/java/org/jpype/pkg/JPypePackage.java native/java/org/jpype/pkg/JPypePackageManager.java native/java/org/jpype/proxy/JPypeProxy.java native/java/org/jpype/pickle/Encoder.java native/java/org/jpype/pickle/Decoder.java native/java/org/jpype/pickle/ByteBufferInputStream.java native/java/org/jpype/classloader/JPypeClassLoader.java native/java/org/jpype/classloader/DynamicClassLoader.java native/java/org/jpype/javadoc/JavadocExtractor.java native/java/org/jpype/javadoc/JavadocException.java native/java/org/jpype/javadoc/JavadocRenderer.java native/java/org/jpype/javadoc/DomUtilities.java native/java/org/jpype/javadoc/Javadoc.java native/java/org/jpype/javadoc/JavadocTransformer.java native/java/org/jpype/ref/JPypeReference.java native/java/org/jpype/ref/JPypeReferenceSet.java native/java/org/jpype/ref/JPypeReferenceQueue.java native/java/org/jpype/ref/JPypeReferenceNative.java native/java/org/jpype/manager/MethodResolution.java native/java/org/jpype/manager/TypeFactoryNative.java native/java/org/jpype/manager/TypeFactory.java native/java/org/jpype/manager/ModifierCode.java native/java/org/jpype/manager/TypeManager.java native/java/org/jpype/manager/ClassDescriptor.java native/java/org/jpype/manager/TypeAudit.java
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Copy file native/java/org/jpype/html/entities.txt build/temp.solaris-2.11-sun4v.64bit-3.6/org.jpype/classes/org/jpype/html/entities.txt
  /mysoftware/java/java8/jdk1.8.0_202/bin/jar cvf build/lib.solaris-2.11-sun4v.64bit-3.6/org.jpype.jar -C build/temp.solaris-2.11-sun4v.64bit-3.6/org.jpype/classes .
added manifest
adding: org/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/pickle/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/pickle/ByteBufferInputStream.class(in = 1179) (out= 649)(deflated 44%)
adding: org/jpype/pickle/Decoder.class(in = 683) (out= 406)(deflated 40%)
adding: org/jpype/pickle/Encoder.class(in = 710) (out= 421)(deflated 40%)
adding: org/jpype/classloader/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/classloader/DynamicClassLoader$1.class(in = 1876) (out= 790)(deflated 57%)
adding: org/jpype/classloader/JPypeClassLoader.class(in = 2649) (out= 1413)(deflated 46%)
adding: org/jpype/classloader/DynamicClassLoader.class(in = 6303) (out= 3073)(deflated 51%)
adding: org/jpype/JPypeContext.class(in = 9634) (out= 4679)(deflated 51%)
adding: org/jpype/PyExceptionProxy.class(in = 223) (out= 189)(deflated 15%)
adding: org/jpype/pkg/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/pkg/JPypePackage.class(in = 4038) (out= 2090)(deflated 48%)
adding: org/jpype/pkg/JPypePackageManager.class(in = 7815) (out= 3609)(deflated 53%)
adding: org/jpype/pkg/JPypePackageManager$ModuleDirectory.class(in = 1752) (out= 877)(deflated 49%)
adding: org/jpype/JPypeUtilities.class(in = 779) (out= 444)(deflated 43%)
adding: org/jpype/JPypeSignal$1.class(in = 576) (out= 360)(deflated 37%)
adding: org/jpype/JPypeContext$1.class(in = 480) (out= 311)(deflated 35%)
adding: org/jpype/manager/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/manager/ClassDescriptor.class(in = 1130) (out= 672)(deflated 40%)
adding: org/jpype/manager/TypeAudit.class(in = 251) (out= 172)(deflated 31%)
adding: org/jpype/manager/TypeFactory.class(in = 644) (out= 332)(deflated 48%)
adding: org/jpype/manager/TypeManager.class(in = 14911) (out= 7068)(deflated 52%)
adding: org/jpype/manager/ModifierCode.class(in = 2632) (out= 1425)(deflated 45%)
adding: org/jpype/manager/TypeManager$1.class(in = 177) (out= 135)(deflated 23%)
adding: org/jpype/manager/MethodResolution.class(in = 4502) (out= 2186)(deflated 51%)
adding: org/jpype/manager/TypeManager$Destroyer.class(in = 1116) (out= 626)(deflated 43%)
adding: org/jpype/manager/TypeFactoryNative.class(in = 772) (out= 414)(deflated 46%)
adding: org/jpype/JPypeKeywords.class(in = 1448) (out= 775)(deflated 46%)
adding: org/jpype/proxy/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/proxy/JPypeProxy.class(in = 2535) (out= 1254)(deflated 50%)
adding: org/jpype/javadoc/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/javadoc/DomUtilities.class(in = 3165) (out= 1450)(deflated 54%)
adding: org/jpype/javadoc/JavadocTransformer.class(in = 9712) (out= 4497)(deflated 53%)
adding: org/jpype/javadoc/JavadocRenderer.class(in = 7226) (out= 3569)(deflated 50%)
adding: org/jpype/javadoc/JavadocException.class(in = 277) (out= 198)(deflated 28%)
adding: org/jpype/javadoc/JavadocTransformer$Workspace.class(in = 916) (out= 430)(deflated 53%)
adding: org/jpype/javadoc/Javadoc.class(in = 626) (out= 346)(deflated 44%)
adding: org/jpype/javadoc/JavadocExtractor.class(in = 6370) (out= 3034)(deflated 52%)
adding: org/jpype/JPypeSignal.class(in = 1711) (out= 820)(deflated 52%)
adding: org/jpype/ref/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/ref/JPypeReferenceSet$Pool.class(in = 690) (out= 405)(deflated 41%)
adding: org/jpype/ref/JPypeReferenceNative.class(in = 267) (out= 204)(deflated 23%)
adding: org/jpype/ref/JPypeReference.class(in = 541) (out= 355)(deflated 34%)
adding: org/jpype/ref/JPypeReferenceSet.class(in = 1628) (out= 927)(deflated 43%)
adding: org/jpype/ref/JPypeReferenceQueue.class(in = 3058) (out= 1433)(deflated 53%)
adding: org/jpype/ref/JPypeReferenceQueue$1.class(in = 185) (out= 143)(deflated 22%)
adding: org/jpype/ref/JPypeReferenceQueue$Worker.class(in = 1560) (out= 748)(deflated 52%)
adding: org/jpype/html/(in = 0) (out= 0)(stored 0%)
adding: org/jpype/html/Parser.class(in = 3984) (out= 1900)(deflated 52%)
adding: org/jpype/html/HtmlHandler.class(in = 352) (out= 218)(deflated 38%)
adding: org/jpype/html/Parser$MatchRule.class(in = 1073) (out= 605)(deflated 43%)
adding: org/jpype/html/HtmlGrammar$Escaped.class(in = 1048) (out= 556)(deflated 46%)
adding: org/jpype/html/AttrGrammar$EndQuoteRule.class(in = 1130) (out= 564)(deflated 50%)
adding: org/jpype/html/HtmlGrammar$Directive.class(in = 910) (out= 476)(deflated 47%)
adding: org/jpype/html/Parser$1.class(in = 161) (out= 132)(deflated 18%)
adding: org/jpype/html/HtmlParser.class(in = 531) (out= 306)(deflated 42%)
adding: org/jpype/html/AttrGrammar.class(in = 2221) (out= 984)(deflated 55%)
adding: org/jpype/html/HtmlGrammar$Token.class(in = 2243) (out= 1174)(deflated 47%)
adding: org/jpype/html/AttrGrammar$State.class(in = 1830) (out= 776)(deflated 57%)
adding: org/jpype/html/AttrGrammar$BooleanRule.class(in = 1209) (out= 634)(deflated 47%)
adding: org/jpype/html/Parser$Entity.class(in = 774) (out= 391)(deflated 49%)
adding: org/jpype/html/HtmlGrammar$StartComment.class(in = 1554) (out= 723)(deflated 53%)
adding: org/jpype/html/HtmlGrammar$1.class(in = 171) (out= 136)(deflated 20%)
adding: org/jpype/html/AttrGrammar$IgnoreWSRule.class(in = 819) (out= 458)(deflated 44%)
adding: org/jpype/html/HtmlGrammar$CompleteElement.class(in = 1709) (out= 853)(deflated 50%)
adding: org/jpype/html/HtmlGrammar$BeginElement.class(in = 2130) (out= 962)(deflated 54%)
adding: org/jpype/html/HtmlGrammar$EndElement.class(in = 1392) (out= 664)(deflated 52%)
adding: org/jpype/html/Parser$Grammar.class(in = 254) (out= 165)(deflated 35%)
adding: org/jpype/html/AttrGrammar$QuoteRule.class(in = 1087) (out= 545)(deflated 49%)
adding: org/jpype/html/HtmlGrammar.class(in = 5251) (out= 2249)(deflated 57%)
adding: org/jpype/html/Parser$State.class(in = 349) (out= 198)(deflated 43%)
adding: org/jpype/html/HtmlGrammar$Cleanup.class(in = 2482) (out= 1179)(deflated 52%)
adding: org/jpype/html/Parser$Token.class(in = 215) (out= 167)(deflated 22%)
adding: org/jpype/html/HtmlGrammar$Comment.class(in = 1744) (out= 805)(deflated 53%)
adding: org/jpype/html/HtmlGrammar$EndCData.class(in = 1648) (out= 834)(deflated 49%)
adding: org/jpype/html/HtmlGrammar$StartQuote.class(in = 1259) (out= 611)(deflated 51%)
adding: org/jpype/html/HtmlGrammar$CData.class(in = 1700) (out= 777)(deflated 54%)
adding: org/jpype/html/AttrParser.class(in = 649) (out= 360)(deflated 44%)
adding: org/jpype/html/AttrGrammar$AttrRule.class(in = 1223) (out= 641)(deflated 47%)
adding: org/jpype/html/HtmlWriter.class(in = 3444) (out= 1779)(deflated 48%)
adding: org/jpype/html/entities.txt(in = 3616) (out= 1559)(deflated 56%)
adding: org/jpype/html/HtmlGrammar$Quoted.class(in = 1638) (out= 748)(deflated 54%)
adding: org/jpype/html/HtmlTreeHandler.class(in = 5222) (out= 2595)(deflated 50%)
adding: org/jpype/html/HtmlGrammar$StartElement.class(in = 1624) (out= 784)(deflated 51%)
adding: org/jpype/html/HtmlGrammar$State.class(in = 2080) (out= 905)(deflated 56%)
adding: org/jpype/html/AttrGrammar$Token.class(in = 1791) (out= 931)(deflated 48%)
adding: org/jpype/html/Parser$Rule.class(in = 351) (out= 197)(deflated 43%)
adding: org/jpype/html/HtmlGrammar$EndDirective.class(in = 1404) (out= 677)(deflated 51%)
adding: org/jpype/html/HtmlGrammar$MergeText.class(in = 996) (out= 525)(deflated 47%)
adding: org/jpype/html/Html.class(in = 5891) (out= 3223)(deflated 45%)
adding: org/jpype/html/HtmlGrammar$EndComment.class(in = 1670) (out= 853)(deflated 48%)
Call build ext
building '_jpype' extension
creating build/temp.solaris-2.11-sun4v.64bit-3.6/native
creating build/temp.solaris-2.11-sun4v.64bit-3.6/native/common
creating build/temp.solaris-2.11-sun4v.64bit-3.6/native/python
cc -DNDEBUG -O -m64 -std=c99 -m64 -std=c99 -xcode=pic32 -Inative/common/include -Inative/python/include -Inative/embedded/include -I/mysoftware/java/java8/jdk1.8.0_202/include -I/mysoftware/java/java8/jdk1.8.0_202/include/solaris -I/krowvin/jpype/include -I/mysoftware/python/v3.6.4/include/python3.6m -c native/common/jp_arrayclass.cpp -o build/temp.solaris-2.11-sun4v.64bit-3.6/native/common/jp_arrayclass.o
cc: No valid input files specified, no output generated
error: command 'cc' failed with exit status 1
**(jpype) krowvin:~/jpype-master$** CC -DNDEBUG -O -m64 -std=c99 -m64 -std=c99 -xcode=pic32 -Inative/common/include -Inative/python/include -Inative/embedded/include -I/mysoftware/java/java8/jdk1.8.0_202/include -I/mysoftware/java/java8/jdk1.8.0_202/include/solaris -I/krowvin/jpype/include -I/mysoftware/python/v3.6.4/include/python3.6m -c native/common/jp_arrayclass.cpp -o build/temp.solaris-2.11-sun4v.64bit-3.6/native/common/jp_arrayclass.o
CC: illegal option usage -std=c99
CC: illegal option usage -std=c99
(jpype) krowvin:~/jpype-master$

This is certainly the correct place.  The first thing that we need to address is what is the official compiler for Python on sun?   I assume it is CC but it has been years since I used a sun system.   There is a requirement that all Python modules use the same compiler (or variant of in the case of C++).   If our platform is gcc then using the vendor compiler would be a bad start.   There are ways to get this both from command line and also from internal Python module variables.
https://stackoverflow.com/questions/15350780/how-to-check-which-compiler-was-used-to-build-python
The makefile that we build with --makefile uses the options in platform.py.  The defaults are for g++ so it is not unexpected that some (or all) or the command line arguments may be off.   Trim off any arguments in the makefile that do not apply.  Then you will need to deal with compiler failures on things like "nothrow" depending on what the standard of C++ that sun is supplying.  Once you have a working makefile save it and then port the required options to platform.py.

This is certainly the correct place.  The first thing that we need to address is what is the official compiler for Python on sun?   I assume it is CC but it has been years since I used a sun system.   There is a requirement that all Python modules use the same compiler (or variant of in the case of C++).   If our platform is gcc then using the vendor compiler would be a bad start.   There are ways to get this both from command line and also from internal Python module variables.
https://stackoverflow.com/questions/15350780/how-to-check-which-compiler-was-used-to-build-python
The makefile that we build with --makefile uses the options in platform.py.  The defaults are for g++ so it is not unexpected that some (or all) or the command line arguments may be off.   Trim off any arguments in the makefile that do not apply.  Then you will need to deal with compiler failures on things like "nothrow" depending on what the standard of C++ that sun is supplying.  Once you have a working makefile save it and then port the required options to platform.py.

Hello again Thrameos,
Checking the compiler for python from the link you provided returns:
python3 -c "import sys; print(sys.version)" 3.6.4 (default, Apr 9 2018, 14:45:48) [C]
Calling the interpreter returns
python3
Python 3.6.4 (default, Aug 9 2018, 14:46:26) [C] on sunos5

Seeing it's just C, would that be cc? Which I believe is the c compiler for Solaris.
Some more details about my attempt at compiling with CC:
For starters,
I tried removing -std=c99 from the command, and I also set every include to the full path. My thought process was that the include file was cpp, while "cc" is a the C compiler (not CPP).
This was the output/command i'm currently working with:
Should I go back to cc? The errors make me think it's compatibility issues going from dos to unix.
 Adding a new line does make these go away.

One additional detail, since you mentioned the systems python this might be relevant.
The system has Python 3.5.2 installed by default for python3.
I have exported a new path that points to a python 3.6.4 directory, overriding the python3.5 path in .bashrc.
I also have a python 3.8.0 directory, and debated trying the install with that in the path instead.

Compiler
C is pretty unhelpful.  But as it isn't gcc I would guess you are correct that it must have been CC.
Warnings
The warnings are just about unterminated lines.  This isn't a dos or unix issue.   It is simply that the files were formatted without a newline at the end which appears to be a warning for this compiler.  I believe those are safe to ignore.
Errors
The errors indicate that CC does not recognize the C++ keyword "override"
https://en.cppreference.com/w/cpp/language/override
override was introduced in C++-11.  So the C++ compiler that you are attempting to use is likely very old or has an older standard as the default.   The override specification optional so we have a few ways to get around it.    Unfortunately if you are not C++-11 compliant then you are likely to run into a whole lot of additional issues.  There are also going to be issues with nothrow or similar specifications as JPype is written for C++11 or later.
Looking over the docs for Developer Studio 12.4 it seems like adding --std=c++11 to the arguments should fix it.
https://docs.oracle.com/cd/E37069_01/html/E37071/gndfg.html
Of course having once been a sysadmin for sun and HPUX machines I know that frequently vendors are misleading about the level of compliance.  If that is the case then you would have to try adding #define override at the top of the jpype.h header to remove the optional specification.
Advice
Unfortunately you are diving into deep water.   Porting to a new compiler is usually non-trivial.  The expected errors will be one of

Compiler switch differences.  These are pretty trivial but it takes time to parse through technical documentation for the compiler to get them right.
Compiler differences where some syntax is acceptable for one compiler by not for another.  Usually this is handled either by adding a #define or #ifdef depending on the severity of the incompatibility.
OS differences this will happen where ever something deviates from unix standard.   The likely place for this type of failure is the shared library loading routine in jp_platform.cpp.   If your system is not compatible with shl_load or dlopen you would have to replace that section with the sun specific shared load routine and the corresponding #if statement.   See the _HPUX section as an example.
Sizing and alignment issues.   While JPype runs on both 32 an d64 bit compilers, there are always edge cases in which the size of an object was assumed to be something and another compiler makes different assumptions.  If this is encountered it is unlikely that you can clear it up yourself as the types of errors that are generated from this are crashes and often not where the error was first made.  The most likely source would be in pyjp_value.cpp where we muck with the Python object table.   I would normally try to fix this sort of problem by adding additional padding to the structure overhead and see if it clears up.

I am not saying "Abandon all hope all ye who enter here" but there is a non-trivial possibility that you could start the porting work and get to point that is very challenging to proceed.  Depending on your level of technical comfort it may not be worth your effort.  As a programmer with 25 years of experience I have been outside by comfort zone at times and taken weeks to find nasty compatibility bugs.  That said I will try my best to advise you on these issues as porting to other platforms is always appreciated.   I just can't guarantee success.

Compiler
C is pretty unhelpful.  But as it isn't gcc I would guess you are correct that it must have been CC.
Warnings
The warnings are just about unterminated lines.  This isn't a dos or unix issue.   It is simply that the files were formatted without a newline at the end which appears to be a warning for this compiler.  I believe those are safe to ignore.
Errors
The errors indicate that CC does not recognize the C++ keyword "override"
https://en.cppreference.com/w/cpp/language/override
override was introduced in C++-11.  So the C++ compiler that you are attempting to use is likely very old or has an older standard as the default.   The override specification optional so we have a few ways to get around it.    Unfortunately if you are not C++-11 compliant then you are likely to run into a whole lot of additional issues.  There are also going to be issues with nothrow or similar specifications as JPype is written for C++11 or later.
Looking over the docs for Developer Studio 12.4 it seems like adding --std=c++11 to the arguments should fix it.
https://docs.oracle.com/cd/E37069_01/html/E37071/gndfg.html
Of course having once been a sysadmin for sun and HPUX machines I know that frequently vendors are misleading about the level of compliance.  If that is the case then you would have to try adding #define override at the top of the jpype.h header to remove the optional specification.
Advice
Unfortunately you are diving into deep water.   Porting to a new compiler is usually non-trivial.  The expected errors will be one of

Compiler switch differences.  These are pretty trivial but it takes time to parse through technical documentation for the compiler to get them right.
Compiler differences where some syntax is acceptable for one compiler by not for another.  Usually this is handled either by adding a #define or #ifdef depending on the severity of the incompatibility.
OS differences this will happen where ever something deviates from unix standard.   The likely place for this type of failure is the shared library loading routine in jp_platform.cpp.   If your system is not compatible with shl_load or dlopen you would have to replace that section with the sun specific shared load routine and the corresponding #if statement.   See the _HPUX section as an example.
Sizing and alignment issues.   While JPype runs on both 32 an d64 bit compilers, there are always edge cases in which the size of an object was assumed to be something and another compiler makes different assumptions.  If this is encountered it is unlikely that you can clear it up yourself as the types of errors that are generated from this are crashes and often not where the error was first made.  The most likely source would be in pyjp_value.cpp where we muck with the Python object table.   I would normally try to fix this sort of problem by adding additional padding to the structure overhead and see if it clears up.

I am not saying "Abandon all hope all ye who enter here" but there is a non-trivial possibility that you could start the porting work and get to point that is very challenging to proceed.  Depending on your level of technical comfort it may not be worth your effort.  As a programmer with 25 years of experience I have been outside by comfort zone at times and taken weeks to find nasty compatibility bugs.  That said I will try my best to advise you on these issues as porting to other platforms is always appreciated.   I just can't guarantee success.

I have been outside by comfort zone at times

I'm struggling, but I like to think I/we have gotten somewhere. I'm not quite 25 years of experience, but I am grateful for all your help.
From what you mentioned
I tried adding --std=c++11, but it still failed (Showed the same override errors)
i.e.
"native/common/include/jp_encoding.h", line 58: Error: "," expected instead of "                         override".
Re/defining the override in the jype header file allowed the command to run with zero errors (Just the warnings we discussed).
But it did not continue with the rest of the compile, as I was manually running the command with CC instead of part of the setup.py (For debugging).
Trying to force setup.py to use CC/GCC
I tried using export cc=CC, but it still tried to compile with cc. Is there a way to change the default compiler, or does python decide that? Once I have gcc installed, I would rather go with it - seeing as Solaris compile tools are a bit... Mystical (To me at least).
Here is the output of CC working manually in the terminal:
(jpype) krowvin:~/jpype-master$ CC -DNDEBUG -O -m64 --std=c++11 -xcode=pic32 -Inative/common/include -Inative/python/include -Inative/embedded/include -I/mysoftware/java/java8/jdk1.8.0_202/include -I/mysoftware/java/java8/jdk1.8.0_202/include/solaris -I/home/usace/m5ec9crg/jpype/include -I/mysoftware/python/v3.6.4/include/python3.6m -c native/common/jp_arrayclass.cpp -o build/temp.solaris-2.11-sun4v.64bit-3.6/native/common/jp_arrayclass.o
CC: Warning: Option --std=c++11 passed to ld, if ld is invoked, ignored otherwise
"native/common/include/jpype.h", line 195: Warning: Last line in file "native/common/include/jp_tracer.h" is not terminated with a newline.
"native/common/include/jpype.h", line 197: Warning: Last line in file "native/common/include/jp_typemanager.h" is not terminated with a newline.
"native/common/include/jpype.h", line 198: Warning: Last line in file "native/common/include/jp_encoding.h" is not terminated with a newline.
"native/common/include/jpype.h", line 199: Warning: Last line in file "native/common/include/jp_modifier.h" is not terminated with a newline.
"native/common/include/jpype.h", line 200: Warning: Last line in file "native/common/include/jp_match.h" is not terminated with a newline.
"native/common/include/jpype.h", line 203: Warning: Last line in file "native/common/include/jp_classhints.h" is not terminated with a newline.
"native/common/include/jpype.h", line 204: Warning: Last line in file "native/common/include/jp_method.h" is not terminated with a newline.
"native/common/include/jp_value.h", line 19: Warning: Last line in file "native/common/include/jp_class.h" is not terminated with a newline.
"native/common/include/jpype.h", line 209: Warning: Last line in file "native/common/include/jp_primitivetype.h" is not terminated with a newline.
"native/common/include/jp_primitivetype.h", line 18: Warning: Last line in file "native/common/include/jp_boxedtype.h" is not terminated with a newline.
"native/common/jp_arrayclass.cpp", line 20: Warning: Last line in file "native/common/include/jp_stringtype.h" is not terminated with a newline.
11 Warning(s) detected.

I am looking into getting gcc installed on the system.
It looks like Developer Studio 12.6 (What is installed on the system) is the latest Oracle has to offer.
Would I need to do something in particular with python3 in order to make the compilation work against gcc instead of cc/CC?

I have been outside by comfort zone at times

I'm struggling, but I like to think I/we have gotten somewhere. I'm not quite 25 years of experience, but I am grateful for all your help.
From what you mentioned
I tried adding --std=c++11, but it still failed (Showed the same override errors)
i.e.
"native/common/include/jp_encoding.h", line 58: Error: "," expected instead of "                         override".
Re/defining the override in the jype header file allowed the command to run with zero errors (Just the warnings we discussed).
But it did not continue with the rest of the compile, as I was manually running the command with CC instead of part of the setup.py (For debugging).
Trying to force setup.py to use CC/GCC
I tried using export cc=CC, but it still tried to compile with cc. Is there a way to change the default compiler, or does python decide that? Once I have gcc installed, I would rather go with it - seeing as Solaris compile tools are a bit... Mystical (To me at least).
Here is the output of CC working manually in the terminal:
(jpype) krowvin:~/jpype-master$ CC -DNDEBUG -O -m64 --std=c++11 -xcode=pic32 -Inative/common/include -Inative/python/include -Inative/embedded/include -I/mysoftware/java/java8/jdk1.8.0_202/include -I/mysoftware/java/java8/jdk1.8.0_202/include/solaris -I/home/usace/m5ec9crg/jpype/include -I/mysoftware/python/v3.6.4/include/python3.6m -c native/common/jp_arrayclass.cpp -o build/temp.solaris-2.11-sun4v.64bit-3.6/native/common/jp_arrayclass.o
CC: Warning: Option --std=c++11 passed to ld, if ld is invoked, ignored otherwise
"native/common/include/jpype.h", line 195: Warning: Last line in file "native/common/include/jp_tracer.h" is not terminated with a newline.
"native/common/include/jpype.h", line 197: Warning: Last line in file "native/common/include/jp_typemanager.h" is not terminated with a newline.
"native/common/include/jpype.h", line 198: Warning: Last line in file "native/common/include/jp_encoding.h" is not terminated with a newline.
"native/common/include/jpype.h", line 199: Warning: Last line in file "native/common/include/jp_modifier.h" is not terminated with a newline.
"native/common/include/jpype.h", line 200: Warning: Last line in file "native/common/include/jp_match.h" is not terminated with a newline.
"native/common/include/jpype.h", line 203: Warning: Last line in file "native/common/include/jp_classhints.h" is not terminated with a newline.
"native/common/include/jpype.h", line 204: Warning: Last line in file "native/common/include/jp_method.h" is not terminated with a newline.
"native/common/include/jp_value.h", line 19: Warning: Last line in file "native/common/include/jp_class.h" is not terminated with a newline.
"native/common/include/jpype.h", line 209: Warning: Last line in file "native/common/include/jp_primitivetype.h" is not terminated with a newline.
"native/common/include/jp_primitivetype.h", line 18: Warning: Last line in file "native/common/include/jp_boxedtype.h" is not terminated with a newline.
"native/common/jp_arrayclass.cpp", line 20: Warning: Last line in file "native/common/include/jp_stringtype.h" is not terminated with a newline.
11 Warning(s) detected.

I am looking into getting gcc installed on the system.
It looks like Developer Studio 12.6 (What is installed on the system) is the latest Oracle has to offer.
Would I need to do something in particular with python3 in order to make the compilation work against gcc instead of cc/CC?

Manual build
If you can get it to compile without errors, then just edit the makefile, call make,  and it will build the module.   Typically you will find the resulting module under build/lib.${arch} .  Just copy it and the org.jpype.jar to the top level and run python -m pytest test/jpypetest and see if it worked.   If it does then you can use python setup.py install to complete the process.  I rarely run the setup.py version as I am doing development.   It is just a matter of getting things in the right place after the build completes.
Getting setup.py to use settings
The compiler is typically controlled by the setuptools/distutils that come with Python.  They have a lot of options and such, but the documentation is often so bad that I end up having to go read the source code until I figure out how they intended for it to work.   Your guess on setting cc=CC seems very reasonable but you have to get into build_ext in distutils (and the patches that get added in setuptools) to see what env variable it pulls.   It is a real pain because you have to read through the layering caused by the distutils, distutils/ccompiler, distutils/unixcompiler.py, setuptools/*, and then the project copy (setupext/build_ext).  But if you got it to a makefile and got it working once I can likely guide you how to alter platform.py to make that the default for the system.
https://docs.python.org/3/extending/building.html
My guess is the the export cc is only used for C compilation and that Python looks at a different variable for C++ compilation.  As this is challenging I will show you how I go about it...  Starting from distutils lets grep for "cc"  which takes us to this section.
From unixcompiler.py

    # These are used by CCompiler in two places: the constructor sets
    # instance attributes 'preprocessor', 'compiler', etc. from them, and
    # 'set_executable()' allows any of these to be set.  The defaults here
    # are pretty generic; they will probably have to be set by an outsider
    # (eg. using information discovered by the sysconfig about building
    # Python extensions).
    executables = {'preprocessor' : None,
                   'compiler'     : ["cc"],
                   'compiler_so'  : ["cc"],
                   'compiler_cxx' : ["cc"],
                   'linker_so'    : ["cc", "-shared"],
                   'linker_exe'   : ["cc"],
                   'archiver'     : ["ar", "-cr"],
                   'ranlib'       : None,
                  }

    if sys.platform[:6] == "darwin":

So now we know that there is a map which has the default "compiler_cxx"  so lets grep again to see where it interacts with environ calls.  This leads us to sysconfig.py
(cc, cxx, cflags, ccshared, ldshared, shlib_suffix, ar, ar_flags,
         configure_cppflags, configure_cflags, configure_ldflags) = \
            get_config_vars('CC', 'CXX', 'CFLAGS',
                            'CCSHARED', 'LDSHARED', 'SHLIB_SUFFIX', 'AR', 'ARFLAGS',
                            'CONFIGURE_CPPFLAGS', 'CONFIGURE_CFLAGS', 'CONFIGURE_LDFLAGS')

        if 'CC' in os.environ:
            newcc = os.environ['CC']
            if (sys.platform == 'darwin'
                    and 'LDSHARED' not in os.environ
                    and ldshared.startswith(cc)):
                # On OS X, if CC is overridden, use that as the default
                #       command for LDSHARED as well
                ldshared = newcc + ldshared[len(cc):]
            cc = newcc
        if 'CXX' in os.environ:
            cxx = os.environ['CXX']
        if fnmatch.filter([cc, cxx], '*-4.[0-8]'):
            configure_cflags = configure_cflags.replace('-fstack-protector-strong', '-fstack-protector')
            ldshared = ldshared.replace('-fstack-protector-strong', '-fstack-protector')
            cflags = cflags.replace('-fstack-protector-strong', '-fstack-protector')
        if 'LDSHARED' in os.environ:
            ldshared = os.environ['LDSHARED']
        if 'CPP' in os.environ:
            cpp = os.environ['CPP']
...
        compiler.set_executables(
            preprocessor=cpp,
            compiler=cc_cmd,
            compiler_so=cc_cmd + ' ' + ccshared,
            compiler_cxx=cxx,
            linker_so=ldshared,
            linker_exe=cc,
            archiver=archiver)

(You would then have to trace down set_executables and so forth if we wanted to understand the whole process, but I think we have our answer)
So you need to use export CXX=CC to get C++ compiler set.   Setting cc will cause C to compiler with the specified compiler but leave c++ with the default according to the code.
Using gcc
You shouldn't have any issue using gcc so long as your Python was also compiled with the same compiler tools.  Mixing and matching usually gives less that desirable results as ABIs do not mix unless they are pure C code.  Of course that depends on figuring out how to get Python to compiler with a different compiler.

Manual build
If you can get it to compile without errors, then just edit the makefile, call make,  and it will build the module.   Typically you will find the resulting module under build/lib.${arch} .  Just copy it and the org.jpype.jar to the top level and run python -m pytest test/jpypetest and see if it worked.   If it does then you can use python setup.py install to complete the process.  I rarely run the setup.py version as I am doing development.   It is just a matter of getting things in the right place after the build completes.
Getting setup.py to use settings
The compiler is typically controlled by the setuptools/distutils that come with Python.  They have a lot of options and such, but the documentation is often so bad that I end up having to go read the source code until I figure out how they intended for it to work.   Your guess on setting cc=CC seems very reasonable but you have to get into build_ext in distutils (and the patches that get added in setuptools) to see what env variable it pulls.   It is a real pain because you have to read through the layering caused by the distutils, distutils/ccompiler, distutils/unixcompiler.py, setuptools/*, and then the project copy (setupext/build_ext).  But if you got it to a makefile and got it working once I can likely guide you how to alter platform.py to make that the default for the system.
https://docs.python.org/3/extending/building.html
My guess is the the export cc is only used for C compilation and that Python looks at a different variable for C++ compilation.  As this is challenging I will show you how I go about it...  Starting from distutils lets grep for "cc"  which takes us to this section.
From unixcompiler.py

    # These are used by CCompiler in two places: the constructor sets
    # instance attributes 'preprocessor', 'compiler', etc. from them, and
    # 'set_executable()' allows any of these to be set.  The defaults here
    # are pretty generic; they will probably have to be set by an outsider
    # (eg. using information discovered by the sysconfig about building
    # Python extensions).
    executables = {'preprocessor' : None,
                   'compiler'     : ["cc"],
                   'compiler_so'  : ["cc"],
                   'compiler_cxx' : ["cc"],
                   'linker_so'    : ["cc", "-shared"],
                   'linker_exe'   : ["cc"],
                   'archiver'     : ["ar", "-cr"],
                   'ranlib'       : None,
                  }

    if sys.platform[:6] == "darwin":

So now we know that there is a map which has the default "compiler_cxx"  so lets grep again to see where it interacts with environ calls.  This leads us to sysconfig.py
(cc, cxx, cflags, ccshared, ldshared, shlib_suffix, ar, ar_flags,
         configure_cppflags, configure_cflags, configure_ldflags) = \
            get_config_vars('CC', 'CXX', 'CFLAGS',
                            'CCSHARED', 'LDSHARED', 'SHLIB_SUFFIX', 'AR', 'ARFLAGS',
                            'CONFIGURE_CPPFLAGS', 'CONFIGURE_CFLAGS', 'CONFIGURE_LDFLAGS')

        if 'CC' in os.environ:
            newcc = os.environ['CC']
            if (sys.platform == 'darwin'
                    and 'LDSHARED' not in os.environ
                    and ldshared.startswith(cc)):
                # On OS X, if CC is overridden, use that as the default
                #       command for LDSHARED as well
                ldshared = newcc + ldshared[len(cc):]
            cc = newcc
        if 'CXX' in os.environ:
            cxx = os.environ['CXX']
        if fnmatch.filter([cc, cxx], '*-4.[0-8]'):
            configure_cflags = configure_cflags.replace('-fstack-protector-strong', '-fstack-protector')
            ldshared = ldshared.replace('-fstack-protector-strong', '-fstack-protector')
            cflags = cflags.replace('-fstack-protector-strong', '-fstack-protector')
        if 'LDSHARED' in os.environ:
            ldshared = os.environ['LDSHARED']
        if 'CPP' in os.environ:
            cpp = os.environ['CPP']
...
        compiler.set_executables(
            preprocessor=cpp,
            compiler=cc_cmd,
            compiler_so=cc_cmd + ' ' + ccshared,
            compiler_cxx=cxx,
            linker_so=ldshared,
            linker_exe=cc,
            archiver=archiver)

(You would then have to trace down set_executables and so forth if we wanted to understand the whole process, but I think we have our answer)
So you need to use export CXX=CC to get C++ compiler set.   Setting cc will cause C to compiler with the specified compiler but leave c++ with the default according to the code.
Using gcc
You shouldn't have any issue using gcc so long as your Python was also compiled with the same compiler tools.  Mixing and matching usually gives less that desirable results as ABIs do not mix unless they are pure C code.  Of course that depends on figuring out how to get Python to compiler with a different compiler.

I wanted to let you know I was able to get this to compile on Solaris. I ended up having to get cc installed. Eventually I needed another package installed on the system and it wound up in IT while I waited for them to install it. I tried again today and was able to compile and import Jpype!
Thank you for all your help Thrameos!


Update meta.yaml

Checklist

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

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

@conda-forge-admin, please rerender

@fhh2626
Your SHA256 hash mismatches. I would like to merge the PR from the bot in #11 .


[BEAM-9888] Drop data based on input watermark in @RequiresTimeSortedInput

Backport of [BEAM-9888].
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

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

See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

XLang
---
---
---

---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

cc @ibzib
Can we merge this into 2.21.0? If it is too late, please feel free to close this PR. Thanks!

changed target release to 2.22.0 - see https://issues.apache.org/jira/browse/BEAM-9888 for more details

Ah, I didn't get notified about the comments. Ok.


Translation errors for Simplified Chinese and Traditional Chinese

ℹ Computer information

PowerToys version: v0.31.1
PowerToy Utility: PowerToys Settings
Running PowerToys as Admin: Yes
Windows build number: 19042.789

📝 Provide detailed reproduction steps (if any)

Some translation errors. (Although there is an Issue template for submitting translation errors, I don’t know what template to submit the issue because it is not only a translation problem.)

✔ Expected result

Translation errors.

Suggest to translate as: 用💗制作。
I don't know how to translate it.

❌ Actual result

Translation errors.

In the "About" in the upper right corner of the "General" tab, there is a translation problem in the second paragraph. Incorrect translation: 使用💗制作。
In the setting pages of Color Picker, Image Resizer, PowerRename and PowerToys Run, the content under the heading "Properties" on the right is not translated.

📷 Screenshots

Translation errors

@lc6464
is this for Traditional and /or Simplified?
We only track one problem per issue, so I'll edit your issue to remove the UI problem that you reported, that by the way is already tracked in another issue.

is this for Traditional and /or Simplified?
We only track one problem per issue, so I'll edit your issue to remove the UI problem that you reported, that by the way is already tracked in another issue.

This translation suggestion applies to both Simplified Chinese and Traditional Chinese, but there is a slight difference.
Simplified: 用💗制作
Traditional: 用💗製作
Regardless of whether it is simplified or traditional, "使用" is changed to "用".
"使用心" in Chinese is very strange, it should be changed to "用心". That's 用💗制作(Simplified): or 用💗製作(Traditional).

https://ceapex.visualstudio.com/CEINTL/_workitems/edit/376425

I found that the problem of 使用💗制作。 reappeared in version 0.43.0.

I found that the problem of 使用💗制作。 reappeared in version 0.47.0.

Typical zh-MS lol

微软中文可还行🤣
It is so funny that zh-MS.

filling a new bug here.  https://ceapex.visualstudio.com/CEINTL/_workitems/edit/496897

This error reappeard in 0.53.1.
Why is the same bug reappearing again and again?

This error reappeard in 0.53.1. Why is the same bug reappearing again and again?

I found it, too...
Why this bug reappearing again and again?

It's been almost a year and I've seen this bug fixed and reproduced several times...

cc: @crutkas

it shouldn't be retranslated if we haven't touched it.  We did however just do a massive flip in translation systems but it shouldn't have been retranslated to best of my knowledge.  I'll file another bug

Filed again and added the other older links as a reminder.
https://microsoft.visualstudio.com/OS/_workitems/edit/37673951

此问题在v0.53.3中再次出现

@niuyuhao0818 aware, 0.55 may have it fixed which is why i added "revisit" tag

We just released 0.55 and looking at the issue, this was fixed.  Can someone please validate /needinfo

It's still there in 0.55.0.
Seriously??

reopened issue, seems like there was a misunderstanding in the issue with how stuff got imported here with the new loc team.  Thanks everyone for understanding

提供图片

This issue has not been resolved until the current latest version v0.55.1.

Fixed in 0.56.2.


feature: configurable background color for filtered posts

When reading through posts, it would be very useful to visually distinguish more clearly between filtered posts and unfiltered posts.
Since other elements of the interface have configurable colors (which is excellent and much appreciated!), It would be very useful to be able to figure this also. In the Mastodon official web interface, the colors for filtered posts are slightly more faded, etc. but different people have different needs, So making this a configurable option would probably scale best.
As you can probably see, I am using filters a lot ... and really enjoying this app.Thank you for your work on it - it is very helpful for my life and work!

About keyword filters?
Filters are for hiding content.
I don't quite understand the need to highlight with a background color for the "filtered posts" that does not shows content.
What kind of display do you want?

Since both filtered posts and unfiltered posts are exactly the same color, and can have many words in them, when you are reading quickly, they look very similar. If the filtered posts had a different background color, it would be easier to differentiate them.

If it is easier, instead of a customizable background color, enabling the user to select a different font or font size might also work well. Or even font style, perhaps changing the filter words to be italics, for example.

0e28b9d7167b4d9be0c422873805e1ec6e9a549b


fix: add missing format and type field

Fields format and type are present in the README.md but not implemented.

Hi @lucarin91 thanks for the PR, does this fix any open issue?
can you add some unit test for this ?


Update for New translation strings JA ZH-CN/TW EO EN

Thank you very much for the contributions and fixes!


New PyATL website with addtional functionality.

Already reviewed by @fimion before to this PR.
Please refer to https://github.com/pabloriveracelerity/podium-django/blob/master/PYATL-USER-GUIDE.md for more info about the functionality included.

Looks good to me. I think I have to be at a computer to approve.


Clang : Please use the /MD switch for _AFXDLL builds

When I run Clang Power Tools->Compile on my projects that are DLL I get the above error.  As you can see from the screenshot below I have /MDd set so I don't understand why I'm getting this build issue.  My project builds fine with MSVC.  This is an MFC project.

Hello,
I'm afraid we cannot reproduce the issue. Please attach a sample project so that we can further investigate this.
Regards,
Gabriel.

We're having the same issue on VC15.7.5.  Same as Donaldpherman, our RuntimeLibrary is set to Multi-threaded Debug DLL (/MDd)
I'm attaching a non-trivial project file with this issue.  Let me know if you need a simpler case to debug.
FwSrv.zip

Hi again,
Thank you for helping us investigate this issue by attaching a sample project.
We've isolated the issue and pushed a fix; it'll be available in the next release of Clang Power Tools (v5.0).
Regards,
Gabriel.

Hello again,
A quick update: We've had a bit of rescheduling of the release schedule and version v4.10 was released a few days ago, instead of v5.0. Nonetheless, the fix is included in v4.10.
Regards,
Gabriel.


"metadata-export" script should NOT allow file location to be specified via REST API /scripts endpoint

Created based on feedback in https://github.com/DSpace/dspace-angular/pull/636#pullrequestreview-441228120
Currently, in the Scripts & Processes UI, any administrator can specify a --file location, for the metadata-export script.  Since that script is only able to write a file to the server where DSpace is running, it's unlikely the Admin will know an exact path to type in. Additionally, this could be a security issue if you can write the output file anywhere on the system. Ideally, instead, the file should always be written to the [dspace]/exports/ folder (which is where it was written in DSpace 6.x, IIRC).
Ideally, the REST API should NOT allow a --file parameter to be passed in.  Instead, it should automatically create a new file in the [dspace]/exports/ folder at all times.  Therefore, the user should not be able to specify this location, however they can download the file once the export completes.

we estimate the work to be around 3 hours

@tdonohue There is some misunderstanding on how the "--file" options works. For the REST call this requires a file name, while for the CLI it DOES require a file PATH. This wasn't clear from the help messages as they are currently the same between REST & CLI, the following PR rectifies that issue: https://github.com/DSpace/DSpace/pull/2901
A small note on the [dspace]/exports folder: This folder wasn't used for the metadata-export script, but rather for the SAF exports, in DSpace 6 the csv generated by the metadata-export script was stored in memory before offering the download to the end user. The SAF exports where to big to store in memory & that is why that exports folder was created. But we can now stop using this exports folders as processes make use of bitstreams to store files now.

@KevinVdV : Thanks for clarifying the different usage of the --file option.  However, I'd still much rather remove this flag from the REST API and provide a default name (as I see no reason why the name of the file should be something the user can specify). This is exactly what this Angular UI PR does (it sets the name to [uuid].csv & doesn't provide an option to change it): https://github.com/DSpace/dspace-angular/pull/798
That behavior will provide a more consistent interaction with the "metadata-export" script, no matter whether you use it via the new "Export" UI or via the Processes UI.  The current Processes UI behavior is not user friendly as it requires a --file to be specified before you can start an export.

@KevinVdV : Based on the recently submitted solution for limiting the --email flag to CLI (see #2915), I'd recommend we implement a similar solution for this --file flag.  It should only be possible to set from the CLI, and otherwise should default to something like [uuid].csv or [type]-[uuid].csv or similar.

@tdonohue I opened up a new PR for this issue that follows the suggestion you made: https://github.com/DSpace/DSpace/pull/2924


Support fail over mechnism of vineyard

Assuming that the vineyard uses perisitent volume for data storage, when a vineyard node fails, we need to automatically restore the data in the node and import it to the new vineyard node.

Use Statefulset to create vineyard cluster for uniquely identifies.
Define CRD Backup to store the data for a while and Restore to recover the data while vineyard fails.
The vineyard operator monitors the status of the vineyard at regular intervals, when a vineyard fails, then the operator recreates a new vineyard node, and reloads the data through the previously saved CRD Backup information.

closed as #1117


Set next and prev to use paginate_links array

Ticket:
Reviewer: @jarednova
Issue
The Timber::get_pagination function accepts a preferences array, which can include arguments like a custom base or format for the pagination links.  These args are then passed into the the paginate_links function, which generates the pages attribute of the pagination array.  However, the next and prev attributes of the array are generated separately, using get_next_posts_page_link and previous_posts, neither of which uses the prefs array.  So basically the issue is that if you try to pass custom args, they will not be incorporated into the next and prev links.
Solution
Instead of using get_next_posts_page_link and previous_posts, just get the next and prev links from the pages array generated by paginate_links.
Impact
None
Usage
No changes
Considerations
--
Testing
Tests are included!

Awesome – thanks @lggorman! I'll review this once the tests pass

Coverage decreased (-0.004%) to 88.246% when pulling 6a4d119fdca14e98d716190c31bbd04d14f30785 on lggorman:next-prev-links into 8034b50b77d40c5f92b9509926d78181b46663f7 on timber:master.

Coverage increased (+1.2%) to 89.421% when pulling 6a4d119fdca14e98d716190c31bbd04d14f30785 on lggorman:next-prev-links into 8034b50b77d40c5f92b9509926d78181b46663f7 on timber:master.

This is great @lggorman! With this gap patched, I'd still like you to think about the best API to interact with pagination; we can talk next week a little more about how this might take shape

Does this solve #671 ?

@connorjburton Don't think so unfortunately -- this just sets next and prev to pull from that pages array, so if that's empty as well there's still going to be an issue.


On bundled chromium, can't play video mp4

The video is not playing on chromium. It works on chrome though. Seems it is missing video codex or something. Is there a way to enable them?

You can look at this question from the puppeteer FAQ: https://github.com/puppeteer/puppeteer#q-what-features-does-puppeteer-not-support

Puppeteer is bundled with Chromium — not Chrome — and so by default, it inherits all of Chromium's media-related limitations. This means that Puppeteer does not support licensed formats such as AAC or H.264. (However, it is possible to force Puppeteer to use a separately-installed version Chrome instead of Chromium via the executablePath option to puppeteer.launch. You should only use this configuration if you need an official release of Chrome that supports these media formats.)

No prob. For now, I have changed the format to WebM.


Dev gate applicator

Description

Changed the way Gate Objects are structured. Each non-core openqaoa module will need a GateApplicator object which contains library specific functions on how the gates are applied to the circuit. The Gate Object now acts as an interface.
Each Backend now creates a GateApplicator Object that, together with the Gate Object apply the right library gate to the Backend's internal circuit
The implementation of GateApplicator for Qiskit, Braket and Pyquil backends.
Dynamic generation of constants: DEVICE_NAME_TO_OBJECT_MAPPER , DEVICE_ACCESS_OBJECT_MAPPER. Based on the presence of the particular module.
get_qaoa_backend and create_device updated to dynamically find a module if it has been installed.
plugin_finder.py is added which helps facilitate the function needed to dynamically find modules within the environment.
Updated test_gates.py unittests

Checklist

[ ] I have performed a self-review of my code.
[ ] I have commented my code and used numpy-style docstrings
[ ] I have made corresponding updates to the documentation.
[ ] My changes generate no new warnings
[ ] I have added/updated tests to make sure bugfix/feature works.
[ ] New and existing unit tests pass locally with my changes.

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Name the new unit-tests that you have added along with this change.

Since, I proposed the design in this PR, it makes sense that either @raulconchello, @Q-lds, be the primary reviewer of this PR. I am adding you both for now. I will be reviewing it too

NOTE: If not done yet, run black formatter before merging


onEnter not always fired

Version
v4.0.0-beta.28
0.44.2
Expected behaviour
onEnter should be called everytime i switch tab
Actual behaviour
gets called first, but not everytime

Please give me more details and reopen the ticket if any. It may not called if you have stack inside your tab

@aksonov Does this mean onEnter is never called inside any scene inside tabs?
I have this setup:
                  <Tabs key='tabbar'>
                    <Stack key='tab_1'>
                      <Scene key='home'
                             component={HomeView}/>
                    </Stack>
                    <Stack key='tab_2'>
                     <Scene key='start_create'
                            component={HomeCreateView}/>
                    </Stack>
                  </Tabs>

and basically in ever Scene
  static onEnter() {
    console.log('On Enter')
  };

gets not fired.


Removed author field from pubspec.yaml

Tiny fix, only deletes 'author' field from pubspec.yaml (it is no longer recommended to have this field).

Landing, TBR.


Configuring PostCSS to work with TailwindCSS

Hi!
Awesome project - been playing with it for the last hour and super impressed! 👏
I am trying to use TailwindCSS with gridsome. I have tried the following approaches but neither are working (the CSS file doesn't run through PostCSS)

add a postcss key to package.json:

"postcss": {
    "plugins": {
      "tailwindcss": "./tailwind.js",
      "autoprefixer": {}
    }
  }

Add a .postcssrc.js or postcss.config.js file in root:

const tailwindcss = require('tailwindcss')

module.exports = {
  "plugins": [
    require('tailwindcss')('tailwind.js'),
    require('autoprefixer')(),
  ]
}

Neither are working.
Solution 1 is what works with vue-cli 3.
Is there a different way to achieve this? Is chainwebpack the way to do it?
Thanks in advance 🎉

Thank you :)
Looks like the postcss-loader isn't picking up your config because gridsome is adding the autoprefixer plugin. The plan is to have a postcss option in gridsome.config.js, but the option is not implemented yet. We can consider not adding custom postcss options in the webpack config, and take full advantage of the postcss-load-config module instead. But for now you can add options with chainWebpack. The rule name is postcss-loader.

Woooo! I got it working.
I probably did it totally wrong and did some damage, but for now it allows me to run my CSS through PostCSS :)
Here's what I added to my gridsome.config.js file. Please know this code is probably not the proper implementation, but it got me where I wanted for my weekend fun project..
chainWebpack: config => {
  config.module
    .rule('postcss-loader')
    .test(/\.css$/)
    .use(["tailwindcss", "autoprefixer"])
    .loader('postcss-loader')
},

Looking good!!
I think you are adding you own postcss-loader for .css files which picks up your config. But you can also modify the existing rule with the following code. It will look for a tailwind.js file on root in your project.
chainWebpack: config => {
  config.module
    .rule('css') // or sass, scss, less, postcss, stylus
    .oneOf('normal') // or module
      .use('postcss-loader')
        .tap(options => {
          options.plugins.push(tailwindcss('./tailwind.js'))
          return options
        })
},

We are going to make this easier :)

Ah, I was super close - I played with the .tap() options modifier but couldn't find the right syntax / chain order.
Thanks for that, much cleaner solution! I will try it and then close the issue! 😁

Works beautifully! Thanks you 🎉

question about using 'chainWebpack', is this overriding gridsome default postcss ? seems no more autoprefixer when using

When using code posted in your comment : https://github.com/gridsome/gridsome/issues/9#issuecomment-429655559, i dont see any css prefixed in the output css after build :/
EG:
display: flex;

By default, did i need to add .browserslistrc or something ?

This is how I use PurgeCSS:

Install purgecss with npm install purgecss
Create purgecss.config.js in the root of project and add to it:

module.exports = {
  content: [
    './dist/**/*.html',
    './dist/assets/js/*.js'
  ],
  css: [
    './dist/assets/css/*.css'
  ],
  rejected: true
}

Add next script into package.json: "purgecss": "node_modules/purgecss/bin/purgecss --config ./purgecss.config.js --out ./dist/assets/css"
Modify build script: "build": "gridsome build && npm run purgecss"

For me works perfectly for deleting unused CSS of fontawesome library, but also should work with other packages. Reduced one of .css bundles size from 60K to 8K.

Hey, still need some help. I'm trying to add some plugins to postCSS, however the processor is not compiled well.
gridsome.config.js
const postcssPlugins = [
    require('postcss-mixins'),
    require('autoprefixer'),
    require('postcss-nesting'),
    require('postcss-custom-media'),
    require('postcss-hexrgba'),
    require('postcss-automath')
]

module.exports = {
    siteName: 'khoipro',
    plugins: [],
    chainWebpack: config => {
        config.module
					.rule('postcss-loader')
					.oneOf('normal')
					.test(/\.css$/)
					.use(postcssPlugins)
					.loader('postcss-loader')
    }
}

postcss.config.js
const config = {
    plugins: [
        require('postcss-mixins'),
        require('autoprefixer'),
        require('postcss-nesting'),
        require('postcss-hexrgba'),
        require('postcss-automath'),
        require('postcss-critical-split')({
            'output': process.env.ENV === 'production' ? 'rest' : 'input',
            'startTag': 'defer:start',
            'endTag': 'defer:end',
            'blockTag': 'defer'
        })
    ]
}

module.exports = config

@khoipro not sure if you solved or not but ideally you'll either push or unshift postcss plugins to whatever's already on Gridsome's config like shown here: https://github.com/brandonpittman/gridsome-plugin-tailwindcss/blob/master/gridsome.server.js#L27-L42


Support for OAS 3.0.1

Hi there! Since OAS 3.0.1 is now published, are there any plans to rev gnostic's current draft support of the spec?

Yes, definitely intent, though timing is unclear. Probably in the next month or so. Thanks for posting!

Please check v0.2.0 for a schema for OAS 3.0.1.


Added line activation

Added request mocker to mock responses in tests
Added decorators to handle complex view logic
Added action tests

Still needs to be tested against connect, opened PR to get feedback

@abulrim Please post a link to this PR in Slack, #connect-ruby, and the team will review it.

👍

Need a version update?

updated version to 0.4.5

Just has the one comment left otherwise. 👍

Hm... yeah I think it's better to stay consistent. I'll change to activate.

Renamed to activate, bumped conduit version


Gracefully handling removal of Test resource outside terraform

It might seem, like a small change but produces beautifull results.
Instead of:

piotr@piotr-ThinkPad-E595:~/Projects/kentik/terraform-provider-kentik-synthetics/examples/resources/kentik-synthetics_test$ terraform apply
kentik-synthetics_test.example-hostname-test: Refreshing state... [id=3]
╷
│ Error: failed to read test
│
│   with kentik-synthetics_test.example-hostname-test,
│   on resource.tf line 1, in resource "kentik-synthetics_test" "example-hostname-test":
│    1: resource "kentik-synthetics_test" "example-hostname-test" {
│
│ error: 404 Not Found, status: 404 Not Found, body: {{"code":2,"message":"test GET failed: no such test "3""}
│ }

We get:

piotr@piotr-ThinkPad-E595:~/Projects/kentik/terraform-provider-kentik-synthetics/examples/resources/kentik-synthetics_test$ terraform apply
kentik-synthetics_test.example-hostname-test: Refreshing state... [id=3]
Note: Objects have changed outside of Terraform
Terraform detected the following changes made outside of Terraform since the last "terraform apply":
... missing resource ...
Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ignore_changes, the following plan
may include actions to undo or respond to these changes.

https://clkentik.atlassian.net/browse/KNTK-298

Will merge after @Fenthick approves the PR.

@ziemowit141 Could you do the same in Cloud Export?


Implement timeouts for m2c and compiler invocations

As this title suggests, this PR caps the runtime for all compiler / m2c calls. Currently, the timeout is five seconds for both.
There may well be a better place to put the compile timeout; as ever, happy to change :)

Thanks for this - it's great! Unfortunately it seems something with it breaks the windows build (but to be honest I couldn't care less about the windows build)
As for the other builds, the slowness of wine makes some build take longer than 5s. I think we could just increase the timeout when running tests, for now. but yeah this is revealing how crappy wine is for this project, which is a fun side-effect

Changes look good. The GitHub Actions runners aren't very fast, which means the tests fail. Could you make the timeout configurable via an environment variable (or a .env file)? We can default to a more liberal value like 15s so that the tests pass. We can then change the timeout at deploy-time based on how fast the server is.

Making them django settings that are in the .env makes sense to me. I think the default in the repo should be 10s for compilations and 5 for decompilations (if we want to separate the two). we still need to decide what we're going to do about Windows though. maybe it's an easy fix, not sure

If we can't easily fix this for Windows, perhaps we could just ignore the timeout values on Windows (i.e. default to 0s = no timeout)? If they are set, we can emit a warning that timeouts aren't supported on Windows.

alright!
Despite my mentioning wrapt_timeout_decorator in the Discord, it turned out it was loosely typed enough to cause all sorts of headaches when trying to integrate it. Borrowing its secret sauce dill did allow for relatively painless Windows support, though.


onLayoutChange event not emit while dragging conditon

Describe the bug
onDragStop method will invoke onLayoutMaybeChanged function and compare newLayout with oldLayout.
there the issue.
onDragStart method assign layout to oldLayout ( pass by reference)
onDrag method get moved layout use moveElement, but moveElement change the originalLayout , not a clone object
so onDragStop method get same newLayout and oldLayout
Your Example Website or App
none
Steps to Reproduce the Bug or Issue

set allowOverlap = true
move the layout
not emit layoutChange event

Expected behavior
as normal
react-grid-layout library version
1.3.4
Operating System Version
macOS
Browser
Chrome
Additional context
No response
Screenshots or Videos
No response

See #1775 . I suspect the problem is the same, and the solution provided could work.


Map scrolling by itself

Hi,
I’ve got a map that uses Leaflet and Angular and is resized to fill the available screen. Here’s an example:
http://conwy.opus4.co.uk/planning/localism/abergele/maps/abergele-placemaking-plan
It works fine in Opera and Firefox (both latest) until you maximise the browser, then the map mysteriously starts moving downwards all by itself. I’m baffled by this. It only happens when the browser is truly maximised too—resizing the browser to fill the screen doesn’t cause this effect.
In IE11 and Chrome (latest) it moves downwards by itself all the time even when the browser is windowed.
The map sits in a DIV which is given 100% width/height, which in turn sits inside another div that gets its height set by Javascript to be 100% width/height minus the header bar at the top of the page. The map then of course expands to fill the resized DIV.
Has this behaviour been experienced before? It seems to be occurring sometime around when the invalidateSize() function gets called following the map resizing, but I’m not entirely sure about that.
Thanks.

In addition, when I view the code in Developer Tools I see the following:

Where the second parameter to the translate3d is continuously increasing by 1px.
Not sure if this is of any help in figuring out what’s going on though!

Super-weird. So far I've been able to trace it down to panInsideBounds which is called when maxBounds is set. No idea why it thinks the view is outside of max bounds by 1px though. Maybe a rounding issue somewhere. What maxBounds do you set there?

Hmm, code got stripped sorry. Here it is properly:
<div class="leaflet-map-pane leaflet-pan-anim" style="transform: translate3d(357px, 54px, 0px); -webkit-transition: all 0.25s cubic-bezier(0, 0, 0.5, 1); transition: all 0.25s cubic-bezier(0, 0, 0.5, 1);">

It does indeed appear to be connected to the maxBounds property. I commented it out and then the map works exactly as expected in all four browsers I tested it in.
Here’s the code I’m using to set up the map:
// Create the projection
this.crs = new L.Proj.CRS(
	'EPSG:' + config.projection.code, // Eg. 27700
	config.projection.proj4, // The proj4 string
	{
		resolutions: config.panZoom.resolutions, // Array of resolutions
		origin: [0, 0]
	}
);

// Get the bounds from the config
var southWest = this.crs.projection.unproject(L.point([config.panZoom.maxExtents.left, config.panZoom.maxExtents.bottom]));
var northEast = this.crs.projection.unproject(L.point([config.panZoom.maxExtents.right, config.panZoom.maxExtents.top]));
var bounds = L.latLngBounds(southWest, northEast);

// Create the map
this.map = new L.Map(
	'opusMap',
	{
		crs: this.crs,
		continuousWorld: true,
		worldCopyJump: false,
		attributionControl: false,
		zoomControl: false,
		maxBounds: bounds,
		maxZoom: config.panZoom.resolutions.length - 1, // The number of resolutions -1 to account for array indexing
		minZoom: 0
	}
);

A lot of the things in the code above are supplied via a config object that’s passed to the function creating the map. The projection is created using the Proj4 plugin, and the bounds are generated from some coordinates passed in and reprojected by the Proj4 plugin.
Commenting out the "maxBounds" line in the map creation block has solved the immediate issue, but now of course users can scroll the map way outside the area I want them to see, so it’s not a great solution really.

Sounds awfully similar to #2427, which we never really solved...

Yes, very likely the same issue, so closing as duplicate.
It didn't reproduce at first but started reproducing when I set true fullscreen mode.


Allow manual entry of links

Working & undocumented links to certain databases exist and work.  These links are not returned by einfo, but can be seen in the output of elink when no --linkname is specified.  Using these links in subsequent elink queries actually work too, so:

[ ] elink: Allow manual entry of link name (pending response from NCBI about whether hidden link names are valid, e.g. gene_nucleotide_pos)
[ ] elink: Allow manual entry of "to db" (pending response from NCBI about whether hidden link names are valid, e.g. gene_nucleotide_pos)

However, NLM has responded to my query about these undocumented links...

Collecting the linkname will be a difficult task, that will take time and coordinate/check with relevant groups maintaining individual databases. Your patience will be greatly apprecired.
If you want to explore it on your own, I would suggest that you take a look at the web interface - the advanced page for each database, set the index field to "filter" and check the terms under "dbname all", such as "nuccore all" and see the indexed terms, most of which should be the linkname from that source database to other target database. hold ctrl key you can select multiple - with selection going into the text box above for copy/paste.

https://bioinformatics.stackexchange.com/questions/14135/why-doesnt-an-entrez-eutils-einfo-request-for-gene-return-the-link-gene-nuc/14326#14326


Starfinder>Witchwarper: Alternate Outcome action cost+scope

Alternate outcome is a reaction, not just a free reroll.
Can also be used to turn a hostile crit against you or ally within 100ft into a normal hit.

Resolved.


S3E17 AMC Meeting (NLP) Announcement

AMC Meeting Announcement

S2E17
Season 3 Episodes 17

Date
7-10 pm, Sunday

Location
821, 8th floor, BUPT Research Building

Chairman
@qhduan

Vice-chairman
@23LuZ

Previous Meeting

Minutes
Link

Blog
S3E15 (Season 3 Episodes 15)

Issue
#426

Agenda
1. Oral

Oral should be prepared for 15 - 30 minutes, and no more than 45 minutes, including Q/A.

Presenter
Paper

N/A
N/A

2. Poster

Posters should be prepared for 5 - 10 minutes, and no more than 15 minutes, including Q/A.
No more than 4 posters per seminar. If there are more than 4 posters proposals(PRs), the chairman should pick at most 4, and leave the others in the PR queue.

Presenter
Paper

@huan
Improving Multi-turn Dialogue Modelling with Utterance ReWriter

@newip
Deep Learning in Spiking Neural Networks

3. After Party
Everyone will be welcome. You can join or not join as you want (not required by the AMC), and change your mind at any time.

After Party will be started right after all the meeting agenda had been fulfilled.
We will find a bar and drink beers and talk whatever we want. (we can expect that it will be related to meeting topics of the day)
The bill will be paid AA

Party Animals

List all members here except those who confirmed not coming. Put 🍺 instead of 🍻 in front of the members' name if they said "maybe". Do not list them who said "not this time".

🍺 @huan
🍺 @newip
🍺 @duan

Newcomers

Please remove the following table and set the number to 0 if there's no newcomer.

Newcomers number: 1

Referrer
Newcomer
Bio

@huan
@Mingkko
李重阳，目前在读研一，是沙龙的新人。对机器学习和NLP方面有很大兴趣，经学长推荐，想参加沙龙和大家进行学习交流。

Confirmed Attendees
Total number: 4

The member that does not give a talk should be quoted after a member who gives a talk.
Example: Alice_ will give a talk but Bob_ does not, and Bob_ wants to go with Alice:
@Alice (@Bob_)_

Role
People List

🧓 Chair
@qhduan

🧑 Vice-chair
@23LuZ

🗣 Oral
N/A

📰 Posters
@huan

📰 Posters
@newip

👶 Newcomers
@Mingkko

申请挂靠 @huan 如同意还请回复：）

同意

Hello! I would appreciate it if you could please avoid @-mentioning me :)

Hello! I would appreciate it if you could please avoid @-mentioning me :)

@alice SRY! we will change the template ASAP. Thanks for pointing out.


add pokemon type support

Adds support for editing a pokemon info's types!
Relies on backend PR for support of the apply function call

Closes #30

YAYY looks cute


Add test verifying that example pass all consul healthchecks

What is the issue?
Lacking HTTP request to verify that presto health checks have passing status
Suggestion(s)/solution(s) [Optional]
Add ansible playbook. Example in terraform-nomad-minio module
Checklist (after created issue)

[X] Added label(s)
[X] Added to project
[X] Added to milestone

It actually exists at the beginning of https://github.com/fredrikhgrelland/terraform-nomad-presto/blob/master/dev/ansible/05_presto_create_tables.yml


Fix #3423

What does the pull request do?
Making binding DataGridTextColumn to nullable numeric types possible
What is the current behavior?
Binding DataGridTextColumn text property to a nullable number fails, while nullable string and non-nullable number works.
Repro
..\samples\ControlCatalog\Models\Person.cs
Change FirstName property type from string to int?
..\samples\ControlCatalog\Pages\DataGridPage.xaml.cs
Update FirstName instantiations by adding integer numbers
Run demo and switch to DataGrid->Editable
FirstName cells are empty
What is the updated/expected behavior with this PR?
FirstName cells are no longer empty
Fixed issues
Fixes #3423

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

Superseded by https://github.com/AvaloniaUI/Avalonia/pull/3942


Configuration to remove leading zero

Hi, this plugin is very nice, congrats for it! I'm think about a configuration to enable option to remove leading zero, what you think about that?

That sound like a neat feature. Although I've been kind of busy lately. It will take me a couple of weeks to get to it.
PRs are welcome though 🙂


Nexys a7 example

I created example projects for the Digilent Nexys A7 and Nexys 4 DDR boards.
Since this is my first pull request, I hope its the right way to do it

Awesome! Thank you very much! 👍


An error is reported in the video input

Hello, I would like to ask, can't a new video be directly input and then generate a new clear video?Does it have to be framed?1.I use restormer and get an error "assert inp_img.shape[1] == 1, "Input images should contain only 1 frame."
AssertionError: Input images should contain only 1 frame.” 2. "AttributeError: 'EasyDict' object has no attribute 'model'" is also reported with dbn

Hi @txy00001, the video should be first split into frames. Meanwhile, Restormer is an image model, thus can only restore 1 frame when inference once.


a11e596 Terminated

Steps to reproduce

Use upload example file.
Run it.

Failure Logs
Terminated

Expected behavior
A succesful upload.
Current behavior
Terminated
No error, no warning.
Version
Edge
Anything else?
No response
Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

Hi! Can you clarify a bit? By terminated do you mean the upload simply stops with no warning?

Affirmative, it only write Terminated output.

I think the issue is resolved somehow in the current version.

I am reopening this issue to provide updated information regarding the previous "Terminated" problem encountered. Additionally, I want to share new details about the available RAM during the testing process.

Use the example file with a size of 1.1 GiB.
Execute the upload process.
Observe the outcome.

The upload process terminates and only outputs "Terminated". No error messages or other warnings are displayed.
Successful upload should occur.
The upload process halts with the "Terminated" output. No error messages or warnings are shown.
The version used is Edge.
During the testing, the system had 984 MiB of RAM available.
No response was provided.

1.1 GiB file that resulted in the "Terminated" message.
221 MiB file that was successfully uploaded.

Thank you for your attention to this matter. I hope this information, along with the RAM details, can help in resolving the "Terminated" issue I experienced previously. If there are further steps I need to take, please let me know.

In this update, I will also propose a workaround that involves modifying the #uploadVideo method in the fetch_function function call.
Workaround Proposal:
You can try using the createReadStream function instead of readFileSync and add a new property called duplex with the value set to 'half' in the #uploadVideo method's fetch_function function call. Here's an example:
const file = createReadStream('videoFile.mp4');

yt.studio.upload(file, {
    title: 'videoFile.mp4',
    description: new Date().toString(),
    privacy: 'UNLISTED'
})

And in the #uploadVideo method:
async #uploadVideo(upload_url: string, file: BodyInit): Promise<UploadResult> {
    const response = await this.#session.http.fetch_function(upload_url, {
        method: 'POST',
        headers: {
            'Content-Type': 'application/x-www-form-urlencoded',
            'x-goog-upload-command': 'upload, finalize',
            'x-goog-upload-file-name': `file-${Date.now()}`,
            'x-goog-upload-offset': '0'
        },
        body: file,
        duplex: 'half'
    });

    if (!response.ok)
        throw new InnertubeError('Could not upload video');

    const data = await response.json();

    return data;
}

Please note that while this workaround may help, it's not guaranteed to solve the issue, and there is a possibility that it could have unintended consequences.


Capo is always set to None

I just installed the application, and it seems to be exactly something I have been praying for, so a big thank you first and foremost. Second, I have this small issue that I don't think would be hard to fix: all tabs have "Capo: None" in their header. This is the case even for tabs I know for a fact need a capo, for instance Wonderwall (see screenshot; capo should be in 2). Thank you in advance for your attention!

!

Hi there, sorry for the delay!  Good catch!  I'll have to look into that in more detail to figure out what the issue is.  Note that even for some songs that might need a capo, if the tab author forgot to list that in the metadata the tab will still show as needing no capo.  I don't think that's the issue here, since I looked around quickly and couldn't find any songs that showed a non-zero capo in the app.  I'll update here when I know more.

This issue seems to still be around; reopening for more research

This is fixed in the latest update. For any tab that is already saved locally to your phone, just reload that tab (three dot menu then Reload).


Use dateAdded from titleparser

@iKlsR This should fix the issue where all tab groups report the same date when synced. Mind testing?
https://github.com/eggplanetio/tidytab/releases/tag/2.20.0-beta.1

@briangonzalez Looks good! Thanks. :shipit:


Update to PyPi-based mxtheme version 0.3.*

Description of changes:
Bump-up the mxtheme requirement listed in requires-docs.txt to a newer version which is also available in PyPi.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-149/1 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-149/1/index.html

@aalexandrov the mxtheme does not yet have a release cycle.


audited file count is 0/0 (100%) in packages with variants

by testing the dashboard with this file, I realized that all packages with variants are shown with audit progress 100% and with 0 files, even if underlying data tell another thing.
See f.e. package linux-oniro-5.10.61+gitAUTOINC+3b283fa8d4_452ea6a15e-r0. This is the entry shown in the dashboard:

And these are the data found in the loaded json file (the older variant is fully reviewed, apart from 1 file, while the newer one has still 49688 files to audit; aliens4friends correctly set the "aggregate" flag only in the first one, and the Dashboard's expected behaviour would be to show audit data progress only about the first one to represent the real overall audit progress
    {
      "id": "linux-oniro-5.10.61+gitAUTOINC+3b283fa8d4_452ea6a15e-r0-531ff926+a4f",
      "name": "linux-oniro",
      "version": "5.10.61+gitAUTOINC+3b283fa8d4_452ea6a15e",
      "revision": "r0",
      "variant": "531ff926",
      "debian_matching": {
        "name": null,
        "version": null,
        "ip_matching_files": 0
      },
      "session_state": {
        "selected": true,
        "selected_reason": "Added variant",
        "uploaded": false,
        "uploaded_reason": "Package already present in Fossology"
      },
      "statistics": {
        "files": {
          "audit_total": 64422,
          "audit_done": 64421,
          "audit_to_do": 1,
          "upstream_source_total": 70347,
          "unknown_provenance": 13,
          "known_provenance": 72391,
          "total": 72404
        },
       "licenses": {
        ...
        },
        "aggregate": true
      },
...
    {
      "id": "linux-oniro-5.10.61+gitAUTOINC+3b283fa8d4_452ea6a15e-r0-dbcbbde3+a4f",
      "name": "linux-oniro",
      "version": "5.10.61+gitAUTOINC+3b283fa8d4_452ea6a15e",
      "revision": "r0",
      "variant": "dbcbbde3",
      "debian_matching": {
        "name": null,
        "version": null,
        "ip_matching_files": 0
      },
      "session_state": {
        "selected": true,
        "selected_reason": "Initial state",
        "uploaded": null,
        "uploaded_reason": "Unknown upload status"
      },
      "statistics": {
        "files": {
          "audit_total": 64444,
          "audit_done": 14756,
          "audit_to_do": 49688,
          "upstream_source_total": 70347,
          "unknown_provenance": 13,
          "known_provenance": 72391,
          "total": 72404
        },
       "licenses": {
        ...
        },
        "aggregate": false
      },

@mrabans I solved the issue, I'm making a PR right now


Get yarn cache directory

coverage: 100.0%. remained the same
when pulling 3dbe5079c45f4c8fd461f1ba08440e82312459f4 on get_yarn_cache_directory
into 0690a9ea32de36ca177b0adb20c8220a29b9f013 on master.


Overrides renovate.json on onboarding MR w/ GitLab API v4 (GitLab CE 9.3.5 0c9ceb3)

Configured and ran renovate to update projects on a self-hosted GitLab CE. Renovate is running w/ a personal access token from my account, thus commits made by renovate show up w/ my persoanl profile picture.
Renovate created the initial onboarding merge request (first commit).
Me then edited renovate.json on the branch (second commit).
Renovate then ran again and did override the renovate.json again (third commit, second picture).

Why did that happen? Is that configurable behaviour? Is my configuration wrong? Is it a bug?
The config.js for renovate is minimalistic:
module.exports = {
    platform: 'gitlab',
    endpoint: 'https://GITLAB_CE_935/api/v4',
    token: 'PERSONAL ACCESS TOKEN',
    onboarding: true,
    timezone: 'Europe/Amsterdam',
    logLevel: 'trace',
    repositories: [
        '184' // <-- had to put project ids instead of project names here (for whatever reason)
    ],
    semanticCommits: true,
    semanticPrefix: 'chore',
    labels: ['renovate']
};

Yes it happens if you use the same user to edit the file as Renovate is using. Renovate:

uses the the account id to determine if commits were made by it or not
assumes any commits you made with the same user account must be its own
retains control of the renovate json and keeps it "current" until anyone else starts editing the branch

The result is what you saw - it will override any changes you make to renovate json using the same account.

Ok, so using a dedicated account for renovate should fix this?
Oh, and ultra-fast cool response time! :rocket: :steam_locomotive:

Yes, a dedicated account is definitely recommended as it also makes it easier to distinguish between when the bot did something (eg close or merge a PR) versus when you did. I'll leave this issue open as a reminder to improve the docs on this topic


Allow Environment.from_string() to take a filename for the loaded template

I currently use Environment.from_string() to dynamically load template files, and I would like to be able to set the correct file name on them so the generated tracebacks are much more helpful in identifying the source file (rather than the tracebacks saying the file was <template>). The reason I am not using a Loader is twofold: none of these files ever need to be rendered twice, and Loader is blocking (i.e. not async).
Please look at the PR as an example of the approach itself. If you think this is something that would be approved, I'll finish up the tests and documentation.
To do

Add tests that demonstrate the correct behavior of the change. Tests
should fail without the change.
Add or update relevant docs, in the docs folder and in code.
Add an entry in CHANGES.rst summarizing the change and linking to the issue.
Add .. versionchanged:: entries in any relevant code docs.

As explained in https://github.com/pallets/jinja/issues/1316, we don't plan to add this.

Thanks for clarifying this. I do think this is a needless restriction, especially considering https://github.com/pallets/jinja/issues/1304 has not been worked on (I get it, we're all busy, this is not a criticism). Switching to loaders, while possible, would add some unneeded blocking file I/O to my application, just to get a better hint in the traceback.

There's another option offered in the issue I linked, which does allow setting the filename. I don't know your exact circumstance, but I wouldn't expect loading the template to be a significant length of blocked time. You could also use a thread executor if it was an issue: https://docs.python.org/3/library/asyncio-task.html#running-in-threads

has not been worked on (I get it, we're all busy, this is not a criticism)

Thanks for understanding. I'm always happy to review a good design or PR! I don't personally use asyncio, so waiting for me to do something about it is going to take a lot longer, compared to someone who needs and understands asyncio contributing to the project.

I admit I completely missed that one suggestion earlier, but I'm happy to report that I successfully implemented it in https://github.com/bartfeenstra/betty/pull/1861.
Thanks for your time and work on Jinja! 😊


Add KOCMOC AXIUS LINK REMIX by Sleeping Hummingbird

Song Name
KOCMOC AXIUS LINK REMIX
Artist Name
Sleeping Hummingbird
Source
Youtube
Youtube Link
0k0JZ5yveow
Direct File Link
No response
Song ID
6666
Start Offset [ms]
78
Extra
Created from Auto Nong.
Created for level: 69196070
Downloaded: Yes

accept


Make the content boxes inside the claim boxes behave reasonably.

I'm pretty confident that the big obstacle here will be the zeroth order claims. What is the user interaction going to be like?

I'm thinking that the zeroth order claims will look something like this:
[real input] * P([formula input] | abcdef) + [real input] * P([formula input] | abcdef) = [real input] + [real input] * P([formula input] | abcdef) + [real input] * P([formula input] | abcdef) + [real input] * P([formula input] | abcdef)
where "abcdef" represents the claim ID of the zeroth order claim.


I made easy to switch on/off of this script.

You can use it when access to google currently.
(Implementation is quite crude! sorry!)

LGTM!

You did it! You created a perfect regex pattern!
It's a popular security issue and you fixed!

Sorry...


⚠ Jenkins Plugins Artifactory has degraded performance

In ebab525, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2108 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 4b0cd8b.


Add test without gradient accumulation

Add a new test that does standard batched training without gradient accumulation.
Renames the existing test to specify that it has gradient accumulation.
Closes #806

Also, I am not sure if we should keep the old test? We should probably test the gradient accumulation part differently (sort of like a unit test)...

I agree that it should be reworked, but maybe in a different PR? We can create an issue for this.


sds.c typo: nul -> null.

Signed-off-by: Bo Cai<EMAIL_ADDRESS>

The character '\0' is called NUL. See man ascii. NULL is a pointer. It is a quirks of the C language that they can be used interchangeably.

@kloetzl  So it is, thanks.


Feature/more examples 2

Adding some more text borrowed from A. Downey's book

Codecov Report

:exclamation: No coverage uploaded for pull request head (feature/more-examples-2@fbd8603).

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c0298e...fbd8603. Read the comment docs.


CE Weights After Labelling

Hello, thanks for your work and making it public.
In the compute_labels function, after centroid assignments are found, assignment counts are accumulated to get the CE weights due to possible imbalance. However, classes are weighted directly proportional to assignment counts but not inversely proportional. I feel the weights should be inversely related to the pixel counts if the aim is solving the imbalance. Are there any reasons to make it directly proportional?

Hi! Sorry for the very late response. We have


Efficient quire

@tungen I've moved the efficient QUIRE part your PR #4 to this PR,
I've also changed some coding style issue for you, please check if I've done anything wrong.

@yangarbiter @tungen is this ready for merge?

It's good to merge now.

@yangarbiter @lsc36
The coding style is changed and it looks more concise now.
I ran the code for a while and has no error.
If any further modification is needed please let me know. Thanks.