Versioned release

Are there plans to make a versioned (numbered) release of wak?
Thank you.

I had not thought about that yet. Do you think it is mature enough for that yet? Are you using it?

I'm also using it to keep various build scripts (including autotools) happy. It works quite well with tcc too, I've just been putting
#!/usr/local/bin/tcc -run

at the top of the monolithic source file and running it like a script

I'm also using it to keep various build scripts (including autotools) happy. It works quite well with tcc too, I've just been putting
#!/usr/local/bin/tcc -run

at the top of the monolithic source file and running it like a script

If you don't mind sharing, what environment (libc version, tcc version,
operating system) are you running? I took a shot at running it like a
script and got a error:
$ ./monosrc/mono.c
In file included from ./monosrc/mono.c:24:
/usr/include/regex.h:682: error: '__nmatch' undeclared

That line of /usr/include/regex.h on my system (glibc 2.39-2 (x86_64) on Arch Linux) is:
extern int regexec (const regex_t *_Restrict_ __preg,
        const char *_Restrict_ __String, size_t __nmatch,
        regmatch_t __pmatch[_Restrict_arr_
          _REGEX_NELTS (__nmatch)],
         int __eflags);

Which evaluates to (when removing the irrelevant "const" and "restrict" stuff):
extern int regexec (regex_t *__preg, char *__String, size_t __nmatch, regmatch_t __pmatch[__nmatch], int __eflags)

The problem seems to be:
$ tcc -run -
extern int a(int b, char c[b]);
<stdin>:1: error: 'b' undeclared

Pointing it at my musl headers gives a different error in a typecast for bits/alltypes.h
My version of tcc might also just be old and someone patched in support for this
in a different version. Don't know

I'm using a recent build of the mob branch of https://repo.or.cz/w/tinycc.git. I've used glibc 2.35 on ubuntu 22.04, as well as my own fork of musl (https://github.com/davidar/musl/tree/tcc) which just has a handful of changes allowing musl itself to be built with tcc. If you're using a versioned release of tcc then it's probably missing quite a lot of changes as the last one was 6 years ago.
$ tcc -v
tcc version 0.9.28rc 2024-04-09 mob@6b3cfdd0 (x86_64 Linux)
$ tcc -run -
extern int a(int b, char c[b]);
main(){puts("ok!");}
-:1: warning: implicit declaration of function 'puts'
ok!

I'm using a recent build of the mob branch of https://repo.or.cz/w/tinycc.git.

I didn't know tcc was still being updated. Thanks!
My version of tcc was "tcc version 0.9.27 (x86_64 Linux)" which has a 2000-2006 Copyright notice (It's The latest version the Arch repos provide).
Using the version you provide, I'm not just able to compile wak, but with some minimal changes (#define QUIET in lib/portability.h (Because it only adds it if it's using gcc) and removing the LDOPTIMIZE flags tcc doesn't have) compile the toybox 5.5x faster than with gcc (28s -> 5s). Along with stuff like mksh, nawk, sbase, and many other programs.
Like I said, thanks!

@oliverkwebb No worries! I've been using tcc (and wak) for https://github.com/davidar/bootsh, it's quite impressive how much software can be compiled with it these days, and indeed it is quite fast. Having the one-file implementation of wak has been quite useful for bootstrapping it separately without bloating the main bootsh binary, so I hope that wak will remain a standalone project in addition to the option of integrating it with toybox. It's been quite indispensable too, given that so many C build systems rely on awk in one way or another, so thanks for your work on this compact and portable implementation :)

@davidar David, you're welcome! I'm glad someone is using wak to good purpose. Took a while to write it (understatement there), and I don't know if it will be accepted into toybox; I wrote it sort of on spec. Let me know if you find bugs (it has some for sure) or have ideas for enhancements. Trying to keep it small, but will consider it. I do intend to fix any real bugs but will probably not be doing much more unless/until Rob Landley gets it into toybox.
I tried tcc and it's amazingly fast; execution a bit slow but that's OK for what I'd want it for. Questions: I tried the #!/usr/local/bin/tcc -run to run it as a script and that worked fine. When I tried compiling, it didn't find the math functions until I added -lm to the tcc mono.c command line. Why does the -run thing work without -lm?

@raygard Generally speaking it's been working pretty well, but one issue that I've run into is with "interactive" awk scripts. For instance:
$ mawk '/^say / { print $2 }'
say hello
hello
say goodbye
goodbye
^D
$ ./wak.c '/^say / { print $2 }'
say hello
say goodbye
^D
hello
goodbye
^D

It seems like it's not line-buffering the input, though I'm slightly confused why that is as, looking at the code, it seems like it should be (at least in get_char, not sure about getrec_ functions). I can kind of get it to work by pressing ctrl-D after each line of input:
$ ./wak.c '/^say / { print $2 }'
say hello
^D
hello
say goodbye
^D
goodbye
^D

mawk behaves similarly in some circumstances (https://github.com/ThomasDickey/original-mawk/issues/41#issuecomment-241070898) because they're block buffering input, is wak doing something similar?

Why does the -run thing work without -lm?

Good question, initially I assumed it was just automatically adding common libraries for convenience, but that doesn't appear to be the case. I think it's actually just because -run executes the program in the same process as tcc, which itself is already linked to libm, so it's visible without needing to explicitly load it.

@davidar: I have addressed your problem with interactive input. Note that your fix was helpful but there was more to it. Simply using fgets() in place of fread() only works if RS is <newline> ("\n"), which is the default, but I've gone to some trouble to make wak work with arbitrary regex as RS. I have fixed up the code to use your fgets() approach only if input is a tty (isatty()) and RS is a newline.
Also, thank you muchly for the tip on using tcc, it's amazing! I am using your "script" trick and it's really nice to be able to tweak the code and run it immediately with no need for a separate compile. One thing though: some code requires the char type to be unsigned, and apparently tcc has it signed by default, so I have to use #!/usr/local/bin/tcc -run -funsigned-char in front of mono.c.

A additional note on compiler portability: I've also gotten the mono source code for wak to build under cproc, Which is essentially the dash of C compilers (ISO compliance over pragmatic use).
Since cproc has no -f options the source code has to be compiled with cproc monosrc/mono.c instead of make mono CC=cproc.


Install process on a windows 7(64 bits)

Hi everybody,
I am new to all of this and I'm facing problems installing everything. First of all, I am working on Windows 7 (64 bits) and I already have Pyhton 3.4.
To work with cocotb, I downloaded the minGWinstaller and checked the 3 packages as indicated on your datasheet, therefore I have now a console "MINGW32".
Then I downloaded "cocotb-0.3.zip", I unzipped it in the following paths ".\MinGW\msys\1.0" but when I'm doing the command "make" in the folder "cocotb-0.3" I have a lot of mistakes, starting by what is pasted below.
To be sure that what I understood is right: I do need to compile cocotb in order to use it therefore I have to use the "make" command.
Could somebody please explain to me what is wrong and what I have to do.
Thanks for advance
François
$ make
File "", line 1
import os.path,distutils.sysconfig;print os.path.sep+os.path.join(*list(dist
utils.sysconfig.get_python_lib(standard_lib=True).split(os.path.sep)[:-1]))
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_version()
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
make -k -C examples
make[1]: Entering directory /cocotb-0.3/examples'   File "<string>", line 1     import os.path,distutils.sysconfig;print os.path.sep+os.path.join(*list(dist utils.sysconfig.get_python_lib(standard_lib=True).split(os.path.sep)[:-1]))                                               ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_version()                                               ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_inc()                                               ^ SyntaxError: invalid syntax   File "<string>", line 1     import os.path,distutils.sysconfig;print os.path.sep+os.path.join(*list(dist utils.sysconfig.get_python_lib(standard_lib=True).split(os.path.sep)[:-1]))                                               ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_version()                                               ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_inc()                                               ^ SyntaxError: invalid syntax make[2]: Entering directory /cocotb-0.3/examples/plusargs'
make -C /cocotb-0.3/lib/gpi
File "", line 1
import os.path,distutils.sysconfig;print os.path.sep+os.path.join(*list(dist
utils.sysconfig.get_python_lib(standard_lib=True).split(os.path.sep)[:-1]))
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_version()
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
make[3]: python-config: Command not found
make[3]: Entering directory /cocotb-0.3/lib/gpi' gcc -Werror -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict -prototypes -Wno-unused-parameter -fno-common -g -DDEBUG -fpic -m32 -DFILTER -c -fpic -I/cocotb-0.3/include -I  -o /cocotb-0.3/build/obj/i686/gpi_logging.o gpi_ logging.c make[3]: gcc: Command not found make[3]: *** [/cocotb-0.3/build/obj/i686/gpi_logging.o] Error 127 make[3]: Target all' not remade because of errors.
make[3]: Leaving directory `/cocotb-0.3/lib/gpi'
make[2]: *** [/cocotb-0.3/build/libs/i686/libgpilog.so] Error 2
make -C /cocotb-0.3/lib/embed
File "", line 1
import os.path,distutils.sysconfig;print os.path.sep+os.path.join(*list(dist
utils.sysconfig.get_python_lib(standard_lib=True).split(os.path.sep)[:-1]))
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_version()
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_inc()

@fdesla Did you really mean cocotb-0.3? If so then this does not work on windows, you need version 1.0 at least. You can get this either via Cocotb-1.0.
You are correct that you need a working minGW environment, including gcc. Which from your later error does not seem to be there. The minGW tools page gives the steps needed to ensure that the environment is valid. MinGW

I downloaded through the website the 0.3 version... I tried with the 1.0 and I still have errors and when I'm looking to the MinGW installer I have :

So i do have the gcc compiler...

And thanks for your quick answer !!

@fdesla It's not quite clear but from the screen shot above you have the C++ (g++) compiler but not C (gcc) - installed as part of 'mingw-gcc'. Both are required. My installer shows many more packages than your output above too.
Inside a mingw shell you should be able to type
$> which g++
and
$> which gcc
There should produce the same output showing where the compiler is located in the mingw installation.
If this fails (which I think that it will) then you may need to modify the PATH environment variable to include the location where the binary is located.

I don't have the same path but I have both see below :

But there is something I don't understand. I should be looking for a gnu python compiler, shouldn't I?
Thanks again for your help!

@fdesla  The python compiler is simply "python" due to the language being interpreted. The build process with first build the libraries and then use python via the simulator to run a test. Since you have moved to the new version of cocotb (1.0) and changed your PATH can you post the output of the "make" command if you still have a problem.

Here is what I got after the "make" command on the MINGW32 console:
$ make
File "", line 1
And here is after the "python" command:
$ python
Python 3.4.3 (v3.4.3:9b73f1c3e601, Feb 24 2015, 22:43:06) [MSC v.1600 32 bit (In
tel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
Thanks for your attention!
from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED"
)
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
make -k -C examples
make[1]: Entering directory /cocotb-1.0/examples'   File "<string>", line 1     from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED" )                                                    ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_inc()                                               ^ SyntaxError: invalid syntax   File "<string>", line 1     from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED" )                                                    ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_inc()                                               ^ SyntaxError: invalid syntax which: iverilog: unknown command dirname: missing operand Try dirname --help' for more information.
make[2]: Entering directory /cocotb-1.0/examples/plusargs' /cocotb-1.0/makefiles/simulators/Makefile.icarus:43: *** "Directory containing I carus binaries must be included in system path".  Stop. make[2]: Leaving directory /cocotb-1.0/examples/plusargs'
make[1]: *** [plusargs] Error 2
File "", line 1
from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED"
)
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
File "", line 1
from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED"
)
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
which: iverilog: unknown command
dirname: missing operand
Try dirname --help' for more information. make[2]: Entering directory /cocotb-1.0/examples/sim_exit/tests'
/cocotb-1.0/makefiles/simulators/Makefile.icarus:43: *** "Directory containing I
carus binaries must be included in system path".  Stop.
make[2]: Leaving directory /cocotb-1.0/examples/sim_exit/tests' make[1]: *** [sim_exit/tests] Error 2   File "<string>", line 1     from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED" )                                                    ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_inc()                                               ^ SyntaxError: invalid syntax   File "<string>", line 1     from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED" )                                                    ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_inc()                                               ^ SyntaxError: invalid syntax which: iverilog: unknown command dirname: missing operand Try dirname --help' for more information.
make[2]: Entering directory /cocotb-1.0/examples/functionality/tests' /cocotb-1.0/makefiles/simulators/Makefile.icarus:43: *** "Directory containing I carus binaries must be included in system path".  Stop. make[2]: Leaving directory /cocotb-1.0/examples/functionality/tests'
make[1]: *** [functionality/tests] Error 2
File "", line 1
from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED"
)
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
File "", line 1
from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED"
)
^
SyntaxError: invalid syntax
File "", line 1
import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
which: iverilog: unknown command
dirname: missing operand
Try dirname --help' for more information. make[2]: Entering directory /cocotb-1.0/examples/adder/tests'
/cocotb-1.0/makefiles/simulators/Makefile.icarus:43: *** "Directory containing I
carus binaries must be included in system path".  Stop.
make[2]: Leaving directory /cocotb-1.0/examples/adder/tests' make[1]: *** [adder/tests] Error 2   File "<string>", line 1     from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED" )                                                    ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_inc()                                               ^ SyntaxError: invalid syntax   File "<string>", line 1     from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED" )                                                    ^ SyntaxError: invalid syntax   File "<string>", line 1     import distutils.sysconfig; print distutils.sysconfig.get_python_inc()                                               ^ SyntaxError: invalid syntax which: iverilog: unknown command dirname: missing operand Try dirname --help' for more information.
make[2]: Entering directory /cocotb-1.0/examples/endian_swapper/tests' /cocotb-1.0/makefiles/simulators/Makefile.icarus:43: *** "Directory containing I carus binaries must be included in system path".  Stop. make[2]: Leaving directory /cocotb-1.0/examples/endian_swapper/tests'
make[1]: *** [endian_swapper/tests] Error 2
make[1]: Target all' not remade because of errors. make[1]: Leaving directory /cocotb-1.0/examples'
make: *** [test] Error 2

@fdesla There is something a miss with your python installation. We have not tried 3.4 on windows but I have used 2.7. You are also missing the icarus simulator that is the default choice if the SIM environment variable is not set. Once installed this also needs to be on your PATH.

Okay thanks again ;)
I'll go for the 2.7 version of python but I don't want to use icarus, I'm working on vivado (I was hoping it will be detected...)
And how do I know the name of "my" variable SIM?

@fdesla I'm not sure you'll have much success with Vivado.  When I last checked they hadn't implemented enough of a foreign language interface to support Cocotb.


Remove !important from hidden

I regret the #18 . We need more specificity, but not so much; which avoids animation.
Maybe this is a better idea:
template {
  display: none !important;
}
[hidden][hidden] {
  display: none;
}

In case we need animation, we override the dsplay using !important. It has been proven to be safer.

WTF I closed this?


Seems to not be working at all on Android

Hi,
Thank you for this plugin. It's working like a charm on my desktop.
The problem is on Android :
Even the demo http://jqueryfiledownload.apphb.com/ doesn't work, it opens a new window(worst than if the plugin wasn't installed) and then it downloads the file.
Does anybody have this problem also ?
thank in advance :)

What's the exact browser you are using. Something must have updated since I last tested it.

On Jun 22, 2016, at 12:24 PM, Gabriel Deschildre<EMAIL_ADDRESS>wrote:
Hi,
Thank you for this plugin. It's working like a charm on my desktop.
The problem is on Android :
Even the demo http://jqueryfiledownload.apphb.com/ doesn't work, it opens a new window(worst than if the plugin wasn't installed) and then it downloads the file.
Does anybody have this problem also ?
thank in advance :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi John
I am using chrome and also tested with native browser on android 5 and 6
Le 22 juin 2016 10:33 PM, "John Culviner"<EMAIL_ADDRESS>a
écrit :

What's the exact browser you are using. Something must have updated since
I last tested it.

On Jun 22, 2016, at 12:24 PM, Gabriel Deschildre <
<EMAIL_ADDRESS>wrote:
Hi,
Thank you for this plugin. It's working like a charm on my desktop.
The problem is on Android :
Even the demo http://jqueryfiledownload.apphb.com/ doesn't work, it
opens a new window(worst than if the plugin wasn't installed) and then it
downloads the file.
Does anybody have this problem also ?
thank in advance :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/johnculviner/jquery.fileDownload/issues/123#issuecomment-227867867,
or mute the thread
https://github.com/notifications/unsubscribe/ADDvgBpRUQvShCwRZR8GqRI-x3KEOxhpks5qOZwVgaJpZM4I7oAC
.

k sounds good. let me know if you come up with a fix and do a PR otherwise I'll take a look when I get a chance


refactor: Make circle a type Circle

See https://github.com/leanprover-community/mathlib4/wiki/Tradeoffs-of-concrete-types-defined-as-subobjects for context

!bench

Personally, I like this change.

Oh hey Jireh.  Do you think we should deprecate circle and change the statements of these lemmas? or leave it as the PR currently is?

Thanks for considering that. It seems we still have to stabilize on a preferred spelling for the circle as a set in the plane. Somewhere else we use Metric.sphere.
I'm fine if we change the statements and deprecate. Either way, we'll need a way to refer to the set, and coercing the set to a type and then back to a set is definitely not the way!

Okay, what about I leave this PR as is, and if you want to deprecate circle then you can change the few theorems of yours that use it?

Okay, I'll get to it soon. If it's done before others comment on this PR, then maybe you can just deprecate here. But if this is done first, that's fine.

#15343

I'm un-requesting myself for review here - I don't know this part of the library well enough to have an informed opinion.


Batch sink for Spark SQL

Develop a batch sink for splice machine. In other words, it should be possible to run a structured query with the following:
dataframe.write.format("splice")

Fixed by 3092c673f2df6ea9afce4e3f0fc10f0f9cc7238e


regenerate-certs seems to have destroyed every single persistent container

My certificates expired at midnight apparently. I went in this morning and regenerated the certificates with docker-machine regenerate-certs --client-certs. To my dismay, every single container was gone afterwards. docker start produced no container errors. We run all our containers with --restart=always. This happened on six servers so it wasn't some kind of fluke.
docker-machine version 0.16.1, build cce350d7
Client:
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        6247962
 Built:             Sun Feb 10 04:13:50 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 03:42:13 2019
  OS/Arch:          linux/amd64
  Experimental:     false

It really sucked for me because I was expecting a small blip on the radar when restarting docker with the new certs, but nothing major... so I did it in an automated fashion. Suddenly everything was down. Yes I should have done one server first but I have done this in the past a couple years ago and don't remember this happening. No reasonable person would expect regenerating certificates to destroy every single persistent container.

If this happens for a technical reason, it's not mentioned on this page
https://docs.docker.com/machine/reference/regenerate-certs/

I have the same problem two time on the production server. This command shouldn't destroy containers.

I have the same problem two time on the production server. This command shouldn't destroy containers.

nice to know the problem isn't isolated to the area between my keyboard and my chair.

Did not notice this as I deployed app changes after regen certs in staging.
Definitely noticed that containers and images are gone after regen certs in production! I am currently working late to rebuild and deploy production apps (at least the volumes were not deleted).
$ docker-machine -v
docker-machine version 0.16.2, build bd45ab13
$ docker-machine ls
NAME               ACTIVE   DRIVER    STATE     URL                                               SWARM   DOCKER        ERRORS
app-production-1   -        generic   Running   tcp://app-production-1.example.com:2376           v18.01.0-ce

I usually don't complain about occasional problems with the gift that is open source... but how did a mature ops tool fail in a way that removes all containers and images !?


Using eslint-webpack-plugin instead of eslint-loader (deprecated) results in very slow server compiling on update

Versions

nuxt: 2.14.7
node: 14.14

Reproduction
Because of eslint-loader is deprecated, I`ve tried to use eslint-webpack-plugin. Results were pretty promissing for the first sign, but when I editted file, it took 4s for compiling server - compiling client was OK (100ms)
Init compilation took only 6s instead of 20s with eslint-webpack-plugin
Steps to reproduce
Replace
config.module.rules.push({
          enforce: 'pre',
          test: /\.(js|vue)$/,
          loader: 'eslint-loader',
          exclude: /(node_modules)/,
        })

with
import ESLintPlugin from 'eslint-webpack-plugin'

config.plugins.push(new ESLintPlugin())

in nuxt.config.js
What is Expected?
Simmilar compiling time on file update as with eslint-loader
What is actually happening?

Hi @jirkae! Good news is that this is already done by @nuxtjs/eslint v3.0.0


Save print function in TAP output handler before tests

I made this PR to fix https://github.com/Olivine-Labs/busted/issues/632

have you checked other output handlers for the same flaw?

can you update the PR to use io.write?


Formatting ordinal numbers

I read in this document, that I can use the say-as SSML element to interpret numbers as ordinal. Example given:
3rd.
From the w3.org ducument: https://www.w3.org/TR/2005/NOTE-ssml-sayas-20050526/#S3.6
Examples
123
In English, this example will likely be spoken as "One hundred twenty third."
Two two seems to contradict each other. Is it correct? Do the w3.org and cortana implements the SSML tags differently?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c89cf747-150d-8895-9771-237706f6a991
Version Independent ID: ca167625-aae9-76a9-b880-05173d67f67a
Content: Speech Synthesis Markup Language (SSML) Reference - Cortana
Content Source: docs/skills/speech-synthesis-markup-language.md
Product: cortana
GitHub Login: @v-anids
Microsoft Alias: v-anids

Not clear how ordinal 3 as "third" and ordinal 123 as "one hundred and twenty third" is contradictory.
Closing issue. Please reactivate with clarification, if desired.

Not clear how ordinal 3 as "third" and ordinal 123 as "one hundred and twenty third" is contradictory.
Closing issue. Please reactivate with clarification, if desired.


src/curl_fun.cpp:5:10: fatal error: 'jansson.h' file not found

(using macOS Sierra)
After doing "git clone --recursive  git://github.com/butor/blackbird.git" in /Users/username/ (creating a Blackbird folder) and downloading OpenSSL, Jansson, cURL, SQLite3 and sendEmail (and extracting) to /Users/username/ I proceeded to type "make" in the terminal. After some successes i recieved:
Compiling src/curl_fun.o:
src/curl_fun.cpp:5:10: fatal error: 'jansson.h' file not found
#include "jansson.h"
^
1 error generated.
make: *** [src/curl_fun.o] Error 1
I do not know why this happened, please help, thank you in advance

It looks like make can't find location of dependencies. See issue #114. In particular, scroll to the section where I described how to specify exactly where to look for those dependencies using INC_DIR and LIB_DIR.

mingw32-make VERBOSE=1 \ isn't a command for osx

Obviously not, use that as a starting point and modify the settings and commands as appropriate for your platform rather than following it verbatim.

it's not working, ill just do it on my linux instead


postinstall error - Expected the options.agent properties

We're seeing this postinstall issues with version 2
Downloading geckodriver... node_modules/geckodriver/node_modules/got/dist/source/create.js:121
                throw error;
                ^

TypeError: Expected the `options.agent` properties to be `http`, `https` or `http2`, got `_events`
    at normalizeArguments (node_modules/geckodriver/node_modules/got/dist/source/core/index.js:679:27)

Seems to be related to https://github.com/vladikoff/node-geckodriver/blob/main/index.js#L44
Can this be wrapped in a try/catch and attempt to keep going with installation on proxy set error?

The correct fix is to adjust the code to properly pick up the proxy config: https://github.com/sindresorhus/got#proxies
I think the settings changed when got got updated

@Noyabronok could you please check if https://github.com/vladikoff/node-geckodriver/pull/89 fixes your issue?

As v2.0.1 still shows this error: are #89 and #92 included in that release?

#89 fixes the problem that proxy setting was not taken properly by node-geckodriver process.
While @Noyabronok was requesting something like fail-safe handling:
"Can this be wrapped in a try/catch and attempt to keep going with installation on proxy set error?"
Not sure if I was reading it correctly,  but if yes then it's not connected to #89 actually.

We have updated the project setup and the wrapper doesn't automatically download the driver anymore. Let me know if you run into any issues with that.


Lock Error

I keep getting this error Getting unknown property: app\models\Salaries::lock, when i try to add something to table.
I have no Idea why.
Please help if possible.

Do you have lock column on your tables??
If you don't want to use Optimistic Lock feature, then leave optimistic lock option to empty..
If you want to ask anything, please use this
https://gitter.im/mootensai/yii2-enhanced-gii

I'll close this in assumption that you don't have lock column
If it still happen, please tell me..

This is weird! MySQL doesn't allow to name a field lock it's a reserved word!


python311Packages.google-cloud-tasks: 2.15.0 -> 2.15.1

Changelog: https://github.com/googleapis/google-cloud-python/blob/google-cloud-tasks-v2.15.1/packages/google-cloud-tasks/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 282068 run on x86_64-linux 1

2 packages built:

python311Packages.google-cloud-tasks
python311Packages.google-cloud-tasks.dist


feature(ekf_localizer): enable ekf_localizer test

Signed-off-by: kminoda<EMAIL_ADDRESS>Description
Enable a test in ekf_localizer

colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release --packages-select ekf_localizer
colcon test --packages-select ekf_localizer
colcon test-result --verbose

Related links

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

I think this tries to fix the error
.Ensure `rcl_node_fini` is called for all nodes before `rcl_context_fini`,to avoid leaking.

I could resolve the error by replacing the setup and teardown function
-  void SetUp() { rclcpp::init(0, nullptr); }
-  void TearDown() { (void)rclcpp::shutdown(); }
+  static void SetUpTestCase()
+  {
+    rclcpp::init(0, nullptr);
+  }
+
+  static void TearDownTestCase()
+  {
+    rclcpp::shutdown();
+  }

@IshitaTakeshi
Awesome, thanks! Yes, that was one of the points in this PR.
I also modified the topic name & message types in the test, as the original test is out-of-date due to the recent updates in ekf_localizer.

I will close this PR, since enabling the current test does not seem to have a large impact for now.


[error]Cannot read property 'queryResultType' of null

Is this an issue with the query results or the something in the code when it references the devops api? Seems like the latter as I can run the query from TF in Excel just fine.  Thanks for any future guidance.
I setup a simple query filtering based on the 'type' column on work items.
I setup a new pipeline that is only using this action and calling the mentioned work item query.

Used the forked version and this error went away.


Implement the new home page design structure

Task

Implement the new home page design structure, as discussed in the meeting

Deliverables

Updated home page design structure

Merged into release

Merged into release


does yabai still do border colours?

hi!
i just reinstalled yabai and my colour configurations don't seem to work, nor is a way to handle them described in the documents as far as i can tell. has this feature been removed? if so, at what version so i can use that version.
thank you in advance and sorry if this was already stated somewhere

just saw that they were nuked

just saw they were nuked

Go https://github.com/koekeishiya/limelight for a port of the border system that used to be in yabai.


Typo at https://docs.zowe.org/stable/user-guide/cli-installcli

Description

There appears to be a typo in the header - link above shows Installing Zowe CLI
Pages to Update

Screenshots

Expected behavior

Additional context

Hey, are you talking about the <!-- omit in toc --> in the header?


jadx.gui.ui.RenameDialog window never gets pack'ed or sized.

code should be added to call pack if mainWindow.getSettings().loadWindowPos(this); in initUI returns false.
mainWindow.getSettings().saveWindowPos(this); is never called so loadWindowPos will always return false. Other windows call saveWindowPos in the dispose @Override.
A rename keyboard shortcut wouldn't go amiss either.

@BlindWanderer thanks! Rename dialog should be fixed now.


Enterprise: document Analytics

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


add LOLCAT

adds LOLCAT

A second joke english language? I worry that the language menu will become a bit polluted. I'll keep this open for now until I figure out how to handle them well. Please also add your name to CREDITS.txt.

maybe a button to switch to the menu with joke languages? i also already added my name to CREDITS.txt

Ah yes I see that now. And yes, I think a separate menu would be ideal. I'll merge this in when that gets added.

A second joke english language? I worry that the language menu will become a bit polluted. I'll keep this open for now until I figure out how to handle them well. Please also add your name to CREDITS.txt.

I think people are gonna make translations to all the ones mc has, even stuff like anglish. You should definitely make a second menu

Anglish would be fun to see.


Translate ES Pig Latin note on lowercase input str

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[ ] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[x] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #9648

Description

Adds ES translation to the Pig Latin challenge based on translation suggested in this comment https://github.com/FreeCodeCamp/FreeCodeCamp/issues/9648#issuecomment-234809909

LGTM. Thanks Eric.


Trivial Gooey application never completes

Ubuntu 18, Python 3.6
Gooey 1.0.2
Expected: Run attached program, click start, it should complete immediately
Actual behavior: It never completes

$ python3 testapp.py  '/usr/bin/python3' -u 'app/testapp.py' --ignore-gooey  [never completes]

At this point, the application never completes.

testapp.zip

Please provide a minimal copy/pastable code example in the issue.  I can't look at a .zip on my phone.

`import sys
from gooey import Gooey, GooeyParser
class simpletest(object):
def init(self, args=[]):
    parser = GooeyParser(description="Why does this lock up?")

    parser.parse_args(args)

@Gooey()
def main():
simpletest(sys.argv[1:])
print("Blah")
if name == "main":
main()`

That... isn't valid python..
From what I can gather from your broken code sample is that you're trying to run Gooey via a class. See this issue for a class based example that can be run against the release branch.
Other than that, closing, as I have no idea what you're asking or trying to accomplish.


DEPTH TEST don't work

Hi Luca,
DEPTH TEST don't work. If you use a cube on your HelloTriangle example you can test this issue.
private void RenderControl_ContextCreated(object sender, GlControlEventArgs e){
.....
Gl.ClearColor(0.0f, 0.0f, 0.0f, 0.5f);               // Black Background
Gl.ClearDepth(1.0f);
Gl.Enable(EnableCap.DepthTest);                            // Enables Depth Testing
Gl.DepthFunc(DepthFunction.Lequal);                             // The Type Of Depth Testing To Do
Gl.Hint(HintTarget.PerspectiveCorrectionHint, HintMode.Nicest);
....
}
//CUBE
private static readonly float[] _ArrayPosition = new float[] {
-1.0f,-1.0f,-1.0f, // triangle 1 : begin
-1.0f,-1.0f, 1.0f,
-1.0f, 1.0f, 1.0f, // triangle 1 : end
1.0f, 1.0f,-1.0f, // triangle 2 : begin
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f,-1.0f, // triangle 2 : end
1.0f,-1.0f, 1.0f,
-1.0f,-1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
-1.0f, 1.0f,-1.0f,
1.0f,-1.0f, 1.0f,
-1.0f,-1.0f, 1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
-1.0f,-1.0f, 1.0f,
1.0f,-1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f, 1.0f,
1.0f,-1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
1.0f, 1.0f,-1.0f,
-1.0f, 1.0f,-1.0f,
1.0f, 1.0f, 1.0f,
-1.0f, 1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
-1.0f, 1.0f, 1.0f,
1.0f,-1.0f, 1.0f
};
    /// <summary>
    /// Vertex color array.
    /// </summary>
    private static readonly float[] _ArrayColor = new float[] {

0.583f,  0.771f,  0.014f,
0.609f,  0.115f,  0.436f,
0.327f,  0.483f,  0.844f,
0.822f,  0.569f,  0.201f,
0.435f,  0.602f,  0.223f,
0.310f,  0.747f,  0.185f,
0.597f,  0.770f,  0.761f,
0.559f,  0.436f,  0.730f,
0.359f,  0.583f,  0.152f,
0.483f,  0.596f,  0.789f,
0.559f,  0.861f,  0.639f,
0.195f,  0.548f,  0.859f,
0.014f,  0.184f,  0.576f,
0.771f,  0.328f,  0.970f,
0.406f,  0.615f,  0.116f,
0.676f,  0.977f,  0.133f,
0.971f,  0.572f,  0.833f,
0.140f,  0.616f,  0.489f,
0.997f,  0.513f,  0.064f,
0.945f,  0.719f,  0.592f,
0.543f,  0.021f,  0.978f,
0.279f,  0.317f,  0.505f,
0.167f,  0.620f,  0.077f,
0.347f,  0.857f,  0.137f,
0.055f,  0.953f,  0.042f,
0.714f,  0.505f,  0.345f,
0.783f,  0.290f,  0.734f,
0.722f,  0.645f,  0.174f,
0.302f,  0.455f,  0.848f,
0.225f,  0.587f,  0.040f,
0.517f,  0.713f,  0.338f,
0.053f,  0.959f,  0.120f,
0.393f,  0.621f,  0.362f,
0.673f,  0.211f,  0.457f,
0.820f,  0.883f,  0.371f,
0.982f,  0.099f,  0.879f

};

Shouldn't depth value cleared to 0?
Il gio 5 gen 2017, 21:00 gtumino<EMAIL_ADDRESS>ha scritto:

Hi Luca,
DEPTH TEST don't work. If you use a cube on your HelloTriangle example you
can test this issue.
private void RenderControl_ContextCreated(object sender,
GlControlEventArgs e){
.....
Gl.ClearColor(0.0f, 0.0f, 0.0f, 0.5f); // Black Background
Gl.ClearDepth(1.0f);
Gl.Enable(EnableCap.DepthTest); // Enables Depth Testing
Gl.DepthFunc(DepthFunction.Lequal); // The Type Of Depth Testing To Do
Gl.Hint(HintTarget.PerspectiveCorrectionHint, HintMode.Nicest);
....
}
//CUBE
private static readonly float[] _ArrayPosition = new float[] {
-1.0f,-1.0f,-1.0f, // triangle 1 : begin
-1.0f,-1.0f, 1.0f,
-1.0f, 1.0f, 1.0f, // triangle 1 : end
1.0f, 1.0f,-1.0f, // triangle 2 : begin
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f,-1.0f, // triangle 2 : end
1.0f,-1.0f, 1.0f,
-1.0f,-1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
-1.0f, 1.0f,-1.0f,
1.0f,-1.0f, 1.0f,
-1.0f,-1.0f, 1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
-1.0f,-1.0f, 1.0f,
1.0f,-1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f, 1.0f,
1.0f,-1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
1.0f, 1.0f,-1.0f,
-1.0f, 1.0f,-1.0f,
1.0f, 1.0f, 1.0f,
-1.0f, 1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
-1.0f, 1.0f, 1.0f,
1.0f,-1.0f, 1.0f
};
/// <summary>
/// Vertex color array.
/// </summary>
private static readonly float[] _ArrayColor = new float[] {

0.583f,  0.771f,  0.014f,
0.609f,  0.115f,  0.436f,
0.327f,  0.483f,  0.844f,
0.822f,  0.569f,  0.201f,
0.435f,  0.602f,  0.223f,
0.310f,  0.747f,  0.185f,
0.597f,  0.770f,  0.761f,
0.559f,  0.436f,  0.730f,
0.359f,  0.583f,  0.152f,
0.483f,  0.596f,  0.789f,
0.559f,  0.861f,  0.639f,
0.195f,  0.548f,  0.859f,
0.014f,  0.184f,  0.576f,
0.771f,  0.328f,  0.970f,
0.406f,  0.615f,  0.116f,
0.676f,  0.977f,  0.133f,
0.971f,  0.572f,  0.833f,
0.140f,  0.616f,  0.489f,
0.997f,  0.513f,  0.064f,
0.945f,  0.719f,  0.592f,
0.543f,  0.021f,  0.978f,
0.279f,  0.317f,  0.505f,
0.167f,  0.620f,  0.077f,
0.347f,  0.857f,  0.137f,
0.055f,  0.953f,  0.042f,
0.714f,  0.505f,  0.345f,
0.783f,  0.290f,  0.734f,
0.722f,  0.645f,  0.174f,
0.302f,  0.455f,  0.848f,
0.225f,  0.587f,  0.040f,
0.517f,  0.713f,  0.338f,
0.053f,  0.959f,  0.120f,
0.393f,  0.621f,  0.362f,
0.673f,  0.211f,  0.457f,
0.820f,  0.883f,  0.371f,
0.982f,  0.099f,  0.879f
};
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/luca-piccioni/OpenGL.Net/issues/31, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AEe6CbZPIsytspYKdwJrWeUBE0bmvrQ9ks5rPUvzgaJpZM4LcEaf
.

Personally I've never got a problem on the depth setup. Are you sure that your selected pixel format currently allocate depth buffer?
Currently I'm able to run another example with depth testing enabled with thousands of cubes and complexes meshes (50K polygons) without any issue.

I've tried different solution but issue remain.on c++ program is ok.
Il 05 gen 2017 9:17 PM, "Luca Piccioni"<EMAIL_ADDRESS>ha
scritto:

Shouldn't depth value cleared to 0?
Il gio 5 gen 2017, 21:00 gtumino<EMAIL_ADDRESS>ha scritto:

Hi Luca,
DEPTH TEST don't work. If you use a cube on your HelloTriangle example
you
can test this issue.
private void RenderControl_ContextCreated(object sender,
GlControlEventArgs e){
.....
Gl.ClearColor(0.0f, 0.0f, 0.0f, 0.5f); // Black Background
Gl.ClearDepth(1.0f);
Gl.Enable(EnableCap.DepthTest); // Enables Depth Testing
Gl.DepthFunc(DepthFunction.Lequal); // The Type Of Depth Testing To Do
Gl.Hint(HintTarget.PerspectiveCorrectionHint, HintMode.Nicest);
....
}
//CUBE
private static readonly float[] _ArrayPosition = new float[] {
-1.0f,-1.0f,-1.0f, // triangle 1 : begin
-1.0f,-1.0f, 1.0f,
-1.0f, 1.0f, 1.0f, // triangle 1 : end
1.0f, 1.0f,-1.0f, // triangle 2 : begin
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f,-1.0f, // triangle 2 : end
1.0f,-1.0f, 1.0f,
-1.0f,-1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
-1.0f, 1.0f,-1.0f,
1.0f,-1.0f, 1.0f,
-1.0f,-1.0f, 1.0f,
-1.0f,-1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
-1.0f,-1.0f, 1.0f,
1.0f,-1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f,-1.0f,
1.0f,-1.0f,-1.0f,
1.0f, 1.0f, 1.0f,
1.0f,-1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
1.0f, 1.0f,-1.0f,
-1.0f, 1.0f,-1.0f,
1.0f, 1.0f, 1.0f,
-1.0f, 1.0f,-1.0f,
-1.0f, 1.0f, 1.0f,
1.0f, 1.0f, 1.0f,
-1.0f, 1.0f, 1.0f,
1.0f,-1.0f, 1.0f
};
///
/// Vertex color array.
///
private static readonly float[] _ArrayColor = new float[] {
0.583f, 0.771f, 0.014f,
0.609f, 0.115f, 0.436f,
0.327f, 0.483f, 0.844f,
0.822f, 0.569f, 0.201f,
0.435f, 0.602f, 0.223f,
0.310f, 0.747f, 0.185f,
0.597f, 0.770f, 0.761f,
0.559f, 0.436f, 0.730f,
0.359f, 0.583f, 0.152f,
0.483f, 0.596f, 0.789f,
0.559f, 0.861f, 0.639f,
0.195f, 0.548f, 0.859f,
0.014f, 0.184f, 0.576f,
0.771f, 0.328f, 0.970f,
0.406f, 0.615f, 0.116f,
0.676f, 0.977f, 0.133f,
0.971f, 0.572f, 0.833f,
0.140f, 0.616f, 0.489f,
0.997f, 0.513f, 0.064f,
0.945f, 0.719f, 0.592f,
0.543f, 0.021f, 0.978f,
0.279f, 0.317f, 0.505f,
0.167f, 0.620f, 0.077f,
0.347f, 0.857f, 0.137f,
0.055f, 0.953f, 0.042f,
0.714f, 0.505f, 0.345f,
0.783f, 0.290f, 0.734f,
0.722f, 0.645f, 0.174f,
0.302f, 0.455f, 0.848f,
0.225f, 0.587f, 0.040f,
0.517f, 0.713f, 0.338f,
0.053f, 0.959f, 0.120f,
0.393f, 0.621f, 0.362f,
0.673f, 0.211f, 0.457f,
0.820f, 0.883f, 0.371f,
0.982f, 0.099f, 0.879f
};
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/luca-piccioni/OpenGL.Net/issues/31, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/
AEe6CbZPIsytspYKdwJrWeUBE0bmvrQ9ks5rPUvzgaJpZM4LcEaf>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luca-piccioni/OpenGL.Net/issues/31#issuecomment-270746035,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXrKVYk7VSwRkZA7alS72HBaRKncLr27ks5rPU_lgaJpZM4LcEaf
.

Usually with glEnable(depth_test) works, but not with your framework. What
do you mean 'selected pixel format'?
Il 05 gen 2017 9:47 PM, "Luca Piccioni"<EMAIL_ADDRESS>ha
scritto:
Personally I've never got a problem on the depth setup. Are you sure that
your selected pixel format currently allocate depth buffer?
Currently I'm able to run another example with depth testing enabled with
thousands of cubes and complexes meshes (50K polygons) without any issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luca-piccioni/OpenGL.Net/issues/31#issuecomment-270752902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXrKVX4ltpY5EPtxKlCoJAL60Eg2kc4Qks5rPVbKgaJpZM4LcEaf
.

What value do you have for the property DepthBits on your GlControl instance? The properties under Framebuffer section select the pixel format (i.e. the color buffers, depth buffer, pixel buffer; along with their precision). The control select the pixel format with allocate the minimum required buffers, so if the DepthBits property is set to 0, it means that you're requesting a pixel format without depth buffer, hence my question.

Additionally, the GlControl in design mode (within Visual Studio) displays the currently selected pixel format, updated with the properties of the GlControl.

[image: Immagine incorporata 1]
Ok yes is 0. Shoud it set manually?
2017-01-05 22:01 GMT+01:00 Luca Piccioni<EMAIL_ADDRESS>
What value do you have for the property DepthBitson your GlControlinstance?
The properties under Framebuffer section select the pixel format (i.e.
the color buffers, depth buffer, pixel buffer; along with their precision).
The control select the pixel format with allocate the minimum required
buffers, so if the DepthBits property is set to 0, it means that you're
requesting a pixel format without depth buffer, hence my question.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luca-piccioni/OpenGL.Net/issues/31#issuecomment-270756302,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXrKVaU5qmF2XgknsYvD7be1IfshwAjUks5rPVoNgaJpZM4LcEaf
.

Yes. 24 bits is the most common value.

Now its ok, thanks :)
Il 05 gen 2017 10:46 PM, "Luca Piccioni"<EMAIL_ADDRESS>ha
scritto:

Yes. 24 bits is the most common value.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luca-piccioni/OpenGL.Net/issues/31#issuecomment-270766799,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXrKVchzND-3fKKDJWVtlTjFFetRtryXks5rPWSugaJpZM4LcEaf
.


System unavailable: test-osuosl-aix71-ppc64-1 is hung

https://ci.adoptopenjdk.net/computer/test-osuosl-aix71-ppc64-1/
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_extended.functional_ppc64_aix/21/consoleFull
Machine is hung

Jenkins job stopped, I sort of assume the process will need to be stopped manually on the machine? Not sure. Also, test-osuosl-aix71-ppc64-1 isn't in inventory.yml

Seems to be okay running on a different job , therefore closing ...


A space is appended to every button when I end a gesture on the circle

Am I doing something wrong? :)
I didn't try the original 8Pen, but this looks like a recognition problem.

This is intentional: Don't lift your finger, but continue drawing letters until the word is finished.
At first this is sometimes quite hard, when you have to look at the letters to see where you have to continue, but just hold your finger on the circle until you know where to go next.

Also, you can draw the path for one letter, get back into the circle to validate it, and get out of the circle again to enter the letter without the space. Also works for a complex path of multiple letters.
(Not sure if this is intended UX or if the program just inserts a space when you lift from the central circle.)

get out of the circle

Yeah, much better, thanks.


INT closeout office space force bugfix

B-18497
B-18630
Summary
This PR addresses two issues:

Customer's were unable to choose a closeout office for their PPM shipment if they chose the "Space Force" branch of service.
Service Counselor's were unable to view/edit a customer's closeout office during counseling if the customer had chosen the "Space Force" branch of service.

Both of these should now be possible.
How to test

Login as a user, create a move with a PPM shipment.
On the first screen after choosing "PPM", where you input your estimated weights and departure dates, you should now see a "Closeout Office" field. You can choose whichever you like.
Complete the move then login as a Service Counselor with a GBLOC corresponding to your move's origin. Find and select the move.
On the shipment card, you should be able to see the customer's chosen closeout office.
If you click Edit Shipment, you should be able to edit the closeout office. Edit this to whatever you like, for this example, I'll edit the office to "PPPO NAVSUP FLCN Annapolis - USN" which has a GBLOC of "BGNC" (different from my move's original GBLOC).
Complete counseling of the move, then login as user and complete the "Upload PPM Documents" step to send the move to the closeout queue.
Now login as a Service Counselor under the GBLOC of the edited closeout office (mine is "BGNC"), change to the "PPM Closeout" tab, and you should now see your move. You should not see this move under any other GBLOCs.

Edited files:

src/pages/MyMove/PPM/Booking/DateAndLocation/DateAndLocation.jsx
src/components/Customer/PPM/Booking/DateAndLocationForm/DateAndLocationForm.jsx
src/components/Office/ShipmentForm/ShipmentForm.jsx

All others are changes being pulled in from latest MAIN branch.

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 5fdc526dfa8f47ff4d6fdc03bc1df4086eb8592d


Hero Banner component

There is a blank space in the hero banner component when the text is too small. The before element is inheriting its width from the parent so small text leads to this blank space section.
Like on this page:
https://main--sunstar-foundation--hlxsites.hlx.live/en/education/perio-link-night
You can set min-width to 150% on the before element.

FYI: @bosschaert @sdmcraft
Not a blocker

Didn't exactly got this issue.
@ehrro Can you please mention screen size also because its not reproducible at my end.

If you open the page you can see that there is a blank space gap on the left side:

The reason there is a gap here is because the width of the before blue element is based on it's parent and if the parent is not wide enough it won't fill the gap until the end.

If you open the page you can see that there is a blank space gap on the left side:

The reason there is a gap here is because the width of the before blue element is based on it's parent and if the parent is not wide enough it won't fill the gap until the end.

For me its not reproducible on any screen size. Can you please share browser and screen size ?


Manage pin modes for automatic mode changes

Manage pin modes: INPUT, OUTPUT, ADC, PWM, ...
Automatical pin mode changes:

When call digitalRead, then pin mode is automatically changed to INPUT
When call digitalWrite, then pin mode is automatically changed to OUTPUT
When call analogRead, then pin mode is automatically changed to ADC
When call analogWrite or tone, then pin mode is automatically changed to PWM

What is the default pin mode?: INPUT or OUTPUT`

At this time, is it needed?

analogRead, analogWrite, setWatch, pulseRead and pulseWrite function has a automatic mode change.
But I don't think automatic mode change is needed for digitalRead and digitalWrite because digitalRead can be used even though the pin mode is output.
So we don't have to change the code now.


Refactor Jenkins pipeline

Summary
This PR refactors the Jenkins pipeline to reduce the CPU cycles used in testing. This is part of a bigger plan written in https://github.com/stan-dev/design-docs/pull/22.
This PR adds the following:

adds faster failing:

If any of the test stages in parallel stage fail, all the other stages will immediately stop. We currently for example waste 2 hours of CPU cycles on distribution tests if OpenCL tests fail after a few minutes.

move Windows testing to merges to develop and on request:

Windows tests have almost never failed if the other tests passed. Given the very unlikely occurrence of fails only on Windows, I think its perfectly fine to only test on merges to develop. We also now run integration tests (compile all Stan test models on Windows) so any compile issues would be caught on PR tests as well. There will also be a way of requesting Windows tests explicitly.

threading tests only run on one Unix OS:

Given that the threading is done with TBB, there is no sense of running merge tests on both Mac and Linux. So we now run a single test on either Mac or Linux depending on which machine is free at the time.

moves Windows and OpenCL header checks to Github Actions

The Unix header check remains the first step. Those are simple tests but they do cut of ~15 minutes of potential AWS cycles.
Tests
/
Side Effects
/
Release notes
/
Checklist

[x] Copyright holder: Rok Češnovar, Univ. of Ljubljana
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Reducing the compute costs without compromising testing coverage will allow adding additional tests that will increase our coverage. Some of them are already in place: expression tests, integration tests on Windows. Ben Bales has prepared scripts for function-level performance tests we want to run weekly. We might also consider valgrind tests (both run weekly for example).
But we can't just add tests without optimizing the current state a bit first. This PR attempts just that.
Tagging a few devs that might have an opinion here
@syclik  @bbbales2 @t4c1 @SteveBronder @wds15 @bob-carpenter
I would like to have everyone that has an opinion on this, to be on board here.

move Windows testing to merges to develop and on request:

idk about this one, for c++1y there are some windows specific issues where they have the least implemented c++14 standard. Catching this later would be a bummer

idk about this one, for c++1y there are some windows specific issues where they have the least implemented c++14 standard.

Isnt this with g++ 4.9.3? Jenkins windows machines all have g++ 8.3.
We could move the free Github Actions Windows testing we have now to PRs. I am fine with that.

I think for cran we still need to pass on gcc 4.9.3 for R 3.7 tests :-(
https://cran.r-project.org/web/checks/check_flavors.html#r-oldrel-windows-ix86_x86_64

Yes, but this PR does not change how we check that (we run that check with Github Actions on merge).
I will move the g++ 4.9.3 check to run on PRs not on merges only. Thanks for bringing that up.

Actually, any compile issues would be caught in the Windows integration tests that compile Stan models: https://jenkins.mc-stan.org/blue/organizations/jenkins/Stan/detail/downstream_tests/2005/pipeline/160

Additionally moved header checks to Github Actions. Ready for review.

@serban-nicusor-toptal is there a way to set a maximum time limit for a Jenkins stage? Meaning that if it executes for more than X hours (not including waiting for free agents) it stops?

@SteveBronder can you take a look at this?

Github Actions has 4.9.3. Jenkins has 8.3
So this PR does not change coverage in that sense. I think these kinds of issues are fairly rare and hence we don't need to run it every time. If they do turn out to become more common, we can revisit this policy.
If either the author or the reviewer is unsure whether the code would run on Windows in general, they can run manual Jenkins tests that would use g++ 8.3. That is added to this PR.
For cases when we can check the same with 4.9.3, we would have to add manual checks for gcc 4.9.3. Those could be run manually as we do for release notes: https://github.com/stan-dev/math/actions?query=workflow%3A"Release+scripts"

Hey @rok-cesnovar you can use timeout but I can help too.

Hey @rok-cesnovar you can use timeout but I can help too.

Thanks! I think the integration stages in /stan would require the timeouts the most so if you have time, please add them there.

@SteveBronder can I merge this or do you want to discuss the c++1y further? Let me know.

Under 20 pulls! WOoo, getting the backlog cleared out

Woop woop. In before Tadej opens 5 more monday :)


[Breaking] Split as default and split extension files

Overtakes https://github.com/CreateAPI/CreateAPI/pull/87
Closes https://github.com/CreateAPI/CreateAPI/issues/74
Part of https://github.com/CreateAPI/CreateAPI/issues/60

What

Makes splitting files the default and makes a new --merge-sources flag
Creates separate extension files per purpose at the top level instead of merging them
Updates tests to reflect

extension using --merge-sources

I was under the impression that they should be broken out no matter what from https://github.com/CreateAPI/CreateAPI/issues/60 and personally think they should be. The only use case I can think of for merging schema-generated objects/paths would be for reference. While devs might also move files around, they will still have to be responsible for moving these extensions as well (split or merged).
Essentially, it splits the concerns of each file: Entities.swift for generated objects, Paths.swift for generated paths, and then each extension file is their own helper file.

#47

I don't think that this simple change in logic should worry about that until a consensus is reached there. I'll leave my thoughts on the issue.

I was under the impression that they should be broken out no matter wha

Doh, you are right.. I forgot that I even suggested that 😅  https://github.com/CreateAPI/CreateAPI/issues/60#issuecomment-1203141626

I don't think that this simple change in logic should worry about that until a consensus is reached there. I'll leave my thoughts on the issue.

Sure 👍

Let me just do some final tests of this change 👀 It's hard to review on GitHub as the diff freezes up my browser 😄

~Please can you revert the rest of the changes to Snapshots.swift 🙏~ Keep in mind that this diff is gigantic and barely loads in the browser so it makes it hard to efficiently review things 🙇
Its not worth changing it now, but my suggestion if we were to do this again would be to submit a pull request that switches --split for --merge-sources, but updates all the test fixtures that didn't use --split to use --merge-sources (and vice versa).. This would have helped us to be completely sure that the only other changes in output were related to moving the extensions since the diff would have been readable. We could then update all the fixtures to stop using --merge-sources in a separate PR where the diff is less important 🙏
Thanks again though for working on this! Will merge it once the checks finish ✅

Thanks again @LePips for the great contribution 🚀


runAsyncGetFirst() and runAsyncGetLast() have the same API documentation

Both mention

that upon execution will signal the last generated element of the

In the case of runAsyncGetFirst, I believe this should read first

I think we can close this issue (seee #442)

Thanks, closing.


Fix locale for khmer language

You should only modify files under /src.  The ones under /locale and /min are generated by the build process.  Please rebase.  Thanks.

@kruyvanna what do you think?

@ichernev: Sorry for late reply. This is looking good! please go ahead.
thanks @sereysethy for the PR

@ichernev any update?
For me it looks good.
Thanks in advance.

@kruyvanna sorry for me being late too :) I'll merge this in next release, thank you all.

Merged in a21e2aac9dd04d493e46a88c2e19a97b938120cc


[Bug]missing depenencies in package

aiohttp and PyJWT are required in latest version 1.20, please make them package depedencies.

@anyidea aren't they already there?
https://github.com/casdoor/casdoor-python-sdk/blob/f9b8204655c4a1a9b4c635a5f5141ed3b5b938f3/requirements.txt#L1-L6


Test against Ruby v3.1 and Ruby v3.2

Add CI setting for Ruby 3.1 and Ruby 3.2

Approve to run GitHub Actions


Prevent double submits of test order in queue

After entering a test result it is possible to double submit a test result. This causes an IllegalGraphqlArgumentException with the message "No active test order was found for that patient"
Steps to reproduce (easier with network delay)

add a patient to the conduct test page
add a test result and spam the submit button

Expected behavior: the submit button should be disabled between when the user clicks it and the server response

user transaction with issue

Did one query in that sequence take 3.2 seconds to complete?

getting test result use to take 3+ seconds. This was fixed in https://github.com/CDCgov/prime-simplereport/pull/424


Is there a way to load detail row component on the fly and not register it globally

I think using Vue.component and register detail component globally is not a very good practice. I mean it's not a big issue, but becomes when you have several tables in SPA application, meaningn I need to load all detail rows globally.
Is there work around for this?

If you use v.2.0, you won't have to. See here at line 82.

Unfortunately the link above returns empty result. Nothing renders...

See here at line 82.
[Vue warn]: Invalid prop: type check failed for prop "detailRowComponent". Expected String, got Object.

Local registration is working but with error in the console as mentioned above. Please fix. Thanks!

So its not a real warning but a bug? I'm having this too but everything works fine.

I got the same warn [Vue warn]: Invalid prop: type check failed for prop "detailRowComponent". Expected String, got Object. Does anyone know or solve it?


rename folder

Closes #511

Really cool 🎉 Thank you for the PR 🤝 I'll try it out later today 🏃♂

@shubham13695 -- please let me know if you'd like to address the concern I raised or you'd rather I finish up the feature after merging 👌
At the moment I'm really tempted to get version 3.0.0 released - and this feature could be added after (so there's no rush now).
Thank you again for your contribution 🙇

@whyboris  yes I address it that after changing the folder on physical directories we need to update that change in our app. I m figuring out how to do it as rightClickElement index return -1 . if you have any idea please share it with me.

I think this might only need a method in the ImageElementService to update all the objects in the imageElements array 🤔 (replacing the partialPath with the updated version of it).
So once the rename-folder-response comes back to Angular with a success, you would call that method 🤔

hi @whyboris
I don't know what wrong with imageElementService.imageElements like before I update the file partial path it already has updated the folder with an older one same thing happening with the video file also.
if i update the same video file twice it create one more file.

Cool! I checked out your branch -- somehow it creates the new elements (I'll look through your code again -- I didn't realize it did that somehow).
All you'll need to do is mark every element in the old folder path as deleted: true:

btw -- if you happen to know -- could you point out how the new elements get created with your code? I'm looking all over your new code and I don't see anything that adds the videos from the new renamed folder into the app gallery - yet the videos do show up 🤯 :trollface:
I don't understand how that happens from your code -- I'm glad that it does, but could you let me know if you happen to know? 😊 😅

I'm hoping to release version 3.0.0 this week. Because of limited times, and prioritizing the release, I chose not to include this feature in the initial 3.0.0 version.
I look forward to merging it in after a successful release of 3.0.0 🤝


Investigate deny-list performance

As part of the performance analysis we identified a potential problem in the query used to filter the results when applying the deny-list.
As an emergency action we disabled the deny-list temporarily (see https://github.com/decentraland/catalyst/pull/419) but we need to re-enable it without compromising performance.
We discovered that the query used to check the deny-list may grow unbounded and that may impact in the correct behaviour of the system.
An instance of this query is attached to the issue.
deny-list-query.txt

The deny-list has been re-enabled with a few performance improvements.


PA Onboarding - Create okta accounts for PADOH staff to access daily data

Problem statement
PA staff would like to access data to test for format and content. We are currently receiving data so the simplest option is to provision okta accounts.
What you need to know
Email account:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
Acceptance criteria

[ ] okta created for staff
[ ] confirmation from PA staff on access

waiting to confirm that results have been added after creating the PA primary receiver in production


Tracking objects in multiple cameras

Hello, What if I have multiple cameras, for example, 2 cameras and need to track the object from these 2 cameras, is this applicable?

We haven't really faced this use case before, but I guess you could create a distance function which uses the camera_id metadata to make sure the associations between objects of different cameras is being done correctly. It actually sounds quite interesting, please keep us posted.


assignment with array access and invocation expression

result[i / ReferenceFrameSize] = RenderTreeFrame.ComponentReferenceCapture(
    0,
    null,
    0
);
// should be
result[i / ReferenceFrameSize] =
    RenderTreeFrame.ComponentReferenceCapture(0, null, 0 );

This is really an edge case of #7


issues with ./deploy_runtime clone running within Watson Studio

I used Watson Studio notebook and executed
!cd pywren-ibm-cloud-master/runtime && ./deploy_runtime clone cactusone/pywren:3.5
This failed running the script, as there is no pywren.config file in local environment.
create_blackbox_runtime(image_name)   File "./deploy_runtime", line 70, in create_blackbox_runtime     config = wrenconfig.default()   File "/opt/conda/envs/DSX-Python35/lib/python3.5/site-packages/pywren_ibm_cloud-1.0.2-py3.5.egg/pywren_ibm_cloud/wrenconfig.py", line 108, in default     config_data = load(config_filename)   File "/opt/conda/envs/DSX-Python35/lib/python3.5/site-packages/pywren_ibm_cloud-1.0.2-py3.5.egg/pywren_ibm_cloud/wrenconfig.py", line 36, in load     with open(config_filename, 'r') as config_file: FileNotFoundError: [Errno 2] No such file or directory: '/home/dsxuser/.pywren_config'
In Watson Studio we use Python dictionary and provide configuration in runtime.
The best solution would be to pass this dictionary as an input to deploy_runtime ( make it optional of course )

If you want to send a dictionary as an input of a command, it should be serialized and transformed... It requires more lines of code.
If pyyaml package is integrated in Watson Studio, maybe better way to do this right now is to store the config dict into a file with:
with open('.pywren_config', 'w') as outfile:
    yaml.dump(config, outfile, default_flow_style=False)

@JosepSampe thanks.  i will handle this one, i think there is alternative easy way for notebooks to close runtime, without storing config file


chore: Remove x/params module

Deprecated in SDK 46. Already migrated everything internally, just need to remove and fix any upstream deps still on it (PFM, ICQ)
Assigning @joelsmith-2019
Pre-Req:

https://github.com/cosmos/ibc-apps/issues/87

closer to being possible now, can get in the next upgrade

blocked until https://github.com/cosmos/ibc-go/releases/tag/v8.0.0


auto_select_gpu does not free memory allocated on GPU for DDP/Horovod

🐛 Bug
If using both auto_select_gpu=True and the ddp or horovod accelerator, the memory allocated by pick_single_gpu is not freed by torch.
This can't be reproduced on Colab since DDP isn't supported.
To Reproduce
Paste this code into a file and run it:
import pytorch_lightning as pl
from torch import nn
from torchvision.models import resnet18
from torchvision.datasets import CIFAR10
from torchvision.transforms import ToTensor
from torch.utils.data import DataLoader
from torch.optim import SGD

class Model(pl.LightningModule):
    def __init__(self):
        super().__init__()
        self.model = nn.Linear(3072, 10)

    def train_dataloader(self):
        dataset = CIFAR10("__pycache__", download=True, transform=ToTensor())
        return DataLoader(dataset)

    def configure_optimizers(self):
        return SGD(self.model.parameters(), lr=0.01)

    def training_step(self, batch, _):
        x, label = batch
        y = self.model(x.view(x.size(0), -1))
        return nn.functional.cross_entropy(y, label)

trainer = pl.Trainer(accelerator="ddp", gpus=2, auto_select_gpus=True)

model = Model()
trainer.fit(model)

Expected behavior
The same amount of memory is allocated on both GPUs. However, nvidia-smi shows this:

Environment
* CUDA:
        - GPU:
                - GeForce RTX 2080 Ti
                - GeForce RTX 2080 Ti
                - GeForce RTX 2080 Ti
                - GeForce RTX 2080 Ti
        - available:         True
        - version:           10.2
* Packages:
        - numpy:             1.19.2
        - pyTorch_debug:     False
        - pyTorch_version:   1.6.0
        - pytorch-lightning: 1.0.3
        - tqdm:              4.50.1
* System:
        - OS:                Linux
        - architecture:
                - 64bit
                - ELF
        - processor:         x86_64
        - python:            3.8.5
        - version:           #110-Ubuntu SMP Tue Jun 23 02:39:32 UTC 2020

@awaelchli ideas?

I will try to reproduce asap.
My guess is we need to run auto_select_gpus before we launch the child processes. It looks like currently, each child process is running the auto_select_gpus.


Add detail page for Pods

Closes #3514

Adds Pod to Kind enum and creates FluxObject class extension
Adds functionality for DetailModal to display other components
Adds PodPage with API request for object NOTE: we have all the data, but it will not be auto-updated unless we run the request - this is adding a huge load on the k8s api and timing me out verrrrrry quickly
Adds PodDetail with basic display of info utilizing mostly existing components.
Moves class overrides of MuiTabs into theme and Tab into a separate component to reduce repetition (can't reuse SubRouterTabs because these tabs are not using routing)

Oh, why is there no status message then?
Ack on the table, maybe a separate table component so you don't have to make the other table be "one size fits all".

I don't know why there's no message - this is a pod in the flux-system kustomization that's created automatically from the reboot.sh script in enterprise which we're all using. I can look into if it's normal to have undefined messages but maybe it's something we should handle regardless? Could be helpful for people starting out.

Updated - I think the border around each container is a failed experiment but there has to be SOMETHING separating them.

@joshri some checks are failing. Did you run make proto?

@joshri Is the Message not found status message expected?

@JamWils ^^^

Re: Message not found - I added that to the PageStatus component to handle when no message comes back from computeMessage (i.e. Conditions objects have no message).

@joshri is this message displayed for all pods or do some pods have the computable message in the status conditions? Because now it reads as an error even though it is marked with green. It might be a bit confusing to the user.

All of my pods in the flux-system kustomization have no message in any conditions objects. Maybe just "No message" instead of "No message found"? I think just having the icon there also looks like an error, so I'd like to put something there

@opudrovs -
James and I decided to try out a Conditions table that expands on click for this page specifically which handles the issue with no message on page status - this is new code in the PageStatus component since the last time you reviewed.
To test it out, uncomment the case in DetailModal that gives access to the PodDetail page (also import PodPage into DetailModal again)
We're planning to merge this code without giving access to the feature while product decides whether to continue with this new detail pages initiative.

@joshri fine with me! I already approved this PR. Should I re-test it or will you do it yourself?
And some checks are failing. Probably another issue with the version of protobuf generator. Should I run and push make proto?

The checks have passed, cool!


Compile error on latest version

This is the error I am getting on all devices:
src/esphome/components/canopen/canopen.cpp:449:6: error: redefinition of 'void esphome::canopen::CanopenComponent::add_entity(esphome::light::LightState*, uint32_t, int8_t)'  void CanopenComponent::add_entity(esphome::light::LightState *light, uint32_t entity_id, int8_t tpdo) {       ^~~~~~~~~~~~~~~~ In file included from src/esphome.h:21,                  from src/esphome/components/canopen/canopen.cpp:2: src/esphome/components/canopen/canopen.h:369:8: note: 'void esphome::canopen::CanopenComponent::add_entity(esphome::light::LightState*, uint32_t, int8_t)' previously defined here    void add_entity(esphome::light::LightState *light, uint32_t entity_id, int8_t tpdo) {         ^~~~~~~~~~ Compiling .pioenvs/m5dial/src/esphome/components/display/rect.cpp.o *** [.pioenvs/m5dial/src/esphome/components/canopen/canopen.cpp.o] Error 1
esp32:
board: esp32-s3-devkitc-1
framework:
type: arduino
Is there any other information which can be helpful?

Thanks, I missed out 'light' platform in last refactor, I'm on it now.

It should be fixed now.


Absence of multiSchema preview feature shouldn't panic on mysql when declaring multiple database schemas in schema.prisma

Command: prisma db pull
Version: 4.7.1
Binary Version: 272861e07ab64f234d3ffc4094e32bd61775599c
Report: https://prisma-errors.netlify.app/report/14473
OS: x64 darwin 20.5.0
JS Stacktrace:
Error: [introspection-engine/connectors/introspection-connector/src/lib.rs:100:76] called `Result::unwrap()` on an `Err` value: "error: The `schemas` property is only availably with the `multiSchema` preview feature.\n  -->  schema.prisma:4\n   | \n 3 |   url      = env(\"DATABASE_URL\")\n 4 |   schemas  = [\"aiskorea\", \"farmsitter\", \"gem2\", \"wellgorwer2\"]\n   | \n"

Rust Stacktrace:
   0: backtrace::capture::Backtrace::new
   1: user_facing_errors::Error::new_in_panic_hook
   2: user_facing_errors::panic_hook::set_panic_hook::{{closure}}
   3: std::panicking::rust_panic_with_hook
   4: std::panicking::begin_panic_handler::{{closure}}
   5: std::sys_common::backtrace::__rust_end_short_backtrace
   6: _rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::result::unwrap_failed
   9: introspection_connector::IntrospectionContext::new_config_only
  10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  11: <futures_util::future::either::Either<A,B> as core::future::future::Future>::poll
  12: <futures_util::future::future::Then<Fut1,Fut2,F> as core::future::future::Future>::poll
  13: <futures_util::future::either::Either<A,B> as core::future::future::Future>::poll
  14: tokio::runtime::task::core::CoreStage<T>::poll
  15: tokio::runtime::task::raw::poll
  16: std::thread::local::LocalKey<T>::with
  17: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  18: tokio::runtime::scheduler::multi_thread::worker::Context::run
  19: tokio::macros::scoped_tls::ScopedKey<T>::set
  20: tokio::runtime::scheduler::multi_thread::worker::run
  21: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  22: tokio::runtime::task::harness::Harness<T,S>::poll
  23: std::sys_common::backtrace::__rust_begin_short_backtrace
  24: core::ops::function::FnOnce::call_once{{vtable.shim}}
  25: std::sys::unix::thread::Thread::new::thread_start
  26: __pthread_start

Did some investigation what that means, and making it error nicely is going to bubble the code changes all over the place.
The panic will be gone when multiSchema is GA, and we maybe don't want to do any fixes right now...

This is issue is still reproducible, and is due to a missing previewFeatures = ["multiSchema"].
generator client {
  provider = "prisma-client-js"

  // this is fixed by adding:
  previewFeatures = ["multiSchema"]
}

datasource db {
  provider = "postgresql"
  url = "***"
  schemas = ["public", "auth"]
}

This is not really a bug, it's working as intended. As Julius had said:

The panic will be gone when multiSchema is GA, and we maybe don't want to do any fixes right now...


Move to .NET 5 preview.1

PR Summary
Updated associated build files to netcoreapp5.0 and ref assemblies to 5.0-preview.1 where applicable.  Updated files.wxs to changes.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

It looks like there's an issue in .NET 5 preview1 where we set the main thread name and that somehow gets propagated as the process name on Linux (only) and so tests that check if it's pwsh ends up failing.  I'll see about putting in some reasonable workarounds for now and add a pending test to verify the process name.

.NET 5 specifically has improvements to regex, so needed to increase the size of the DOS test

On Windows, pwsh is crashing in a native API call.

.NET 5 specifically has improvements to regex, so needed to increase the size of the DOS test

cc @stephentoub  👏

It looks like there's an issue in .NET 5 preview1 where we set the main thread name and that somehow gets propagated as the process name on Linux (only)

@SteveL-MSFT is that a bug in .NET?

@danmosemsft The main thread name becoming the process name is a bug in .NET and is understood (https://github.com/dotnet/runtime/issues/33673).  That issue isn't blocking as it's currently only affecting tests.  The crashing issue (https://github.com/dotnet/runtime/issues/33703) is preventing us from moving to .NET 5.  Thanks!

There is already an issues filed for regex DOS tests:  https://github.com/PowerShell/PowerShell/issues/12138

@PoshChan retry macos

@SteveL-MSFT, successfully started retry of PowerShell-CI-macOS

.NET originally said that the perf improvement was due to optimization, but it's actually due to a bug.  I filed an issue to add it back to avoid delaying this PR.
https://github.com/PowerShell/PowerShell/issues/12155

.NET originally said that the perf improvement was due to optimization, but it's actually due to a bug

It's half and half :)  The algorithmic complexity improved, in part due to perf improvements, and in part due to a bug fixed in Preview 2 (https://github.com/dotnet/runtime/pull/33409).


Better error json

Improved method of sending error json.

Added serde and serde_derive as dependencies
Created response.rs to house serializable types

Hey @Redrield Thank you!
I will take a closer look and make some tests later but what I have seen so far is good. :)


Fix checkout service

Changes
This PR updates the Go serivce (checkoutservice) to use the new 1.21 spec of the http OpenTelemetry APIs. It changes the go.mod file to use our grafana repos for opentelemetry-go and opentelementry-go-contrib. These forks of the opentelemetry repos have been updated to use: server.name, server.port, client.name, client.port instead of peer.name and peer.port, as well as change http.url to url.full.
The PR also fixes some other minor issues:

The .NET service (cartservice) now runs with DOTNET_HOSTBUILDER__RELOADCONFIGONCHANGE to avoid this issue on Linux https://github.com/dotnet/AspNetCore.Docs/issues/19814
The front-end memory for Kubernetes has been expanded to 500Mi, since 200Mi causes OOM.
Ported docker compose commands for the Makefile.

Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[x ] CHANGELOG.md updated to document new feature additions
[ x] Appropriate documentation updates in the docs
[ x] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

Thanks Karen!


Persist config file settings when resetting form_validation

When checking multiple arrays using form_validation you have to call reset_validation between each separate check due to the instance of the library being a singleton.  The issue comes in when the settings are loaded from a config file as they are initially loaded from a parameter in the constructor, but are set to an empty array when resetting the class.  To get around this issue a copy of the config parameter is made and then the copy is used to reset the rules when clearing.

Hmm - this presumes that one wants to preserve those settings.
Better would be to add a parameter ... reset_validation($keep=false) and to treat accordingly.
This should have a changelog entry, and the user guide would need to be updated, IMHO.

Hmmm...  Would there ever be a case where a config loaded from a file would want to be changed?  The way we use it is that all of the validations are stored in that file so no matter what we need/want to check it is already loaded.
I would be happy to add the items you requested.  Forgive my ignorance, but this is the first time doing this.  Am I correct in thinking that user_guide_src/source/libraries/form_validation.rst would be where the user guide changes should go?  Not sure where to locate the changelog.

user_guide_src/source/libraries/form_validation.rst should be updated if the functionality changes, which you are proposing.
user_guide_src/source/changelog.rst should have a (potentially) single line entry indicating that some functionality has changed.
As to config changing, I have seen cases with several sets of validation rules ... one pre-loaded, and then reset & load a (possibly slightly) different second set. I just would not assume that the same config should automatically be reloaded.
Having a parameter $keep, which defaults to false, makes sure that the proposed changes do not break anyone's existing code, which is a good thing :)

In that case would you think it would be more beneficial for the masses to just skip clearing the current config instead of restoring it back to a copy of the original?  This would enable a reset to occur for any configuration instead of only for those loaded from a file.

A parameter to clear/keep the config settings, with the default being consistent with the current behaviour, would make most sense to me.

How does that look - is this ok?

Getting better :)
This isn't a bug ... your PR was originally described as an enhancement. In that case, the changelog entry would be a new feature, not a bug fix.
IIRC, a bug fix reference would be for an issue # previously reported, not for a problem with the PR itself.
I find your user guide additions confusing ...

You insist on passing TRUE, above line 717. This is opinion, not direction.
" This parameter must be true if your rules are being loaded from a config file" ... er, isn't your point to provide optional keeping of config rules? This suggests that the only reasonable value is TRUE if you have a config file. That is opinion, rather than direction.
The class reference for the method, lines 1079+ in the original .rst, need to be corrected as well.

Finally, your PR is not signed ... this is mentioned at the bottom of http://www.codeigniter.com/user_guide/contributing/index.html

@jim-parry - I read over the information you provided about signing the commits, but it appears that they refer to some command line application.  I have been using Git's build in file editor to make my changes.  Is it possible to sign off as requested from there or will I need to install and setup the local applicaiton?
@narfbg - Thank you for your comments.  I believe I have addressed all of the items you requested.

We still don't have an example of why this is really useful though ...

For this to be useful, two conditions have to come into play:

You have to be using config files to store your validation rules in groups (using run($group) rather than run() to perform validation)
You have to be performing multiple validations (requiring use of reset_validation())

I think each of these is relatively uncommon, so the combination of the two becomes even less common. However, I have seen complaints about the reset_validation() method resetting the _config_rules property (which, of course, I could not track down with a quick check of 2 or 3 places).
I've had enough reasons to use reset_validation() on my own, so, even though I don't use config files to store my validation rules, I do think it would be very frustrating if I did. After all, the property is only set in the constructor, and the library currently provides no way of restoring the rule groups once they've been cleared out by the reset_validation() method. Sure, you can use set_rules() to set validation rules on the individual fields, but you can't use the $group parameter of the run() method once the _config_rules property has been cleared out.

I see ... in that case I'd have to disagree with @jim-parry and say that this is indeed a bugfix and we don't need it to be optional.
It's just that whoever implemented the reset_validation() method (might've been me, don't remember) just made it reset all properties and never even considered what $_config_rules is there for.

I had attempted to describe the issue that this PR was addressing in my first post, but perhaps was not clear enough.  Hopefully now it is a bit clearer as to why I was trying to be so direct/forceful in the documentation about needing to have that parameter set when using config files.
@mwhitneysdsu - Thank you for providing the detailed explanation!
@narfbg - I can revert the proposed fix back to my original commit if that is what you think would be best.  Would there be any advantage in other situations of allowing people to choose to keep the configured validation rules during a reset_validation()?
@jim-parry - In your last comment there was mention of needing to sign off on the commits.  Is it possible to do so from Git's build in editor or do I need to download&configure some local command line utility?
Once a conclusion has been reached on what the most flexible and/or best fix is I will go back in and update the code accordingly. (& also address code format comments)

The documentation tool we use is http://sphinx-doc.org/
It was originally made for python docs, but has been adapted to many purposes.
Documentation sources are created using http://docutils.sourceforge.net/rst.html, although I understand that support for markdown format is underway.
The style we use was customized from https://pypi.python.org/pypi/sphinx_rtd_theme

@zoaked They don't have to choose, $_config_rules shouldn't ever be touched by reset_validation() in the first place ...
Just remove the $this->_config_rules = array(); line from that method and that's it.

@narfbg - I just updated the PR to reflect your suggestion

Done.

Nope, thanks.


calls: init at 0.0.1

Motivation for this change
The calls application is required to provide phone calls for the Librem 5 phone.
This is the initial commit for this application to be packaged for NixOS and the first step to getting NixOS to fully support the Librem 5 phone.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Resolves #65361

This and a lot of other Librem software has been packaged as part of #57614.
https://github.com/NixOS/nixpkgs/pull/57614/commits/ddee3c8a7b6fe716dc66417d88d348463be0cfdd looks pretty complete, perhaps out of date.

This and a lot of other Librem software has been packaged as part of #57614.

I had not found this. I'll make sure I hook everything I'm doing back into that.
Thanks!

I had a read of #57614 and note that he had put it "networking" where as I had put it in "radio".
Any thoughts on the correct location?

A calling application would be a networking application. Additionally all the applications in that directory have to relation to this one.

A calling application would be a networking application. Additionally all the applications in that directory have no relation to this one.

I can see why that would be applicable, but this application is using modem manager to use operate a mobile phone radio to place phone calls across a mobile phone network.
Happy to switch this to "networking", just wanted to make it clear that this was not a VOIP application.

I can see why that would be applicable, but this application is using modem manager to use operate a mobile phone radio to place phone calls across a mobile phone network.

Indeed, but I think it has fallen out of fashion to refer to those things as "radio" even though it's correct.
also

Additionally all the applications in that directory have no relation to this one.

calls has now been moved to networking.

Thanks for your time and input @worldofpeace
I originally based this work on how the related package, libhandy was packaged so your corrections and guidance have been helpful.
If I've understood your suggestions correctly, this last commit should be what you're looking for.

Finally bumped all-packages.nix.

This pull request has been mentioned on Nix community.
Applying: calls: Initial commit to package the application
Applying: Corrected licence
Applying: Corrected licence
Using index info to reconstruct a base tree...
M	pkgs/applications/radio/calls/default.nix
Falling back to patching base and 3-way merge...
Auto-merging pkgs/applications/radio/calls/default.nix
No changes -- Patch already applied.
~/P/nixpkgs ((07e4206a…)|…) $ nix-build -A calls
error: attribute 'calls' in selection path 'calls' not found

I've pushed a version with a cleaned-up history, upgraded to a recent version from upstream git, and tested the application as far as I could (I haven't managed to bend ModemManager to my will yet, but calls seems fine). Will merge on Monday if nobody objects, or as soon as someone approves :)

@lheckemann This was never moved to networking https://github.com/NixOS/nixpkgs/pull/65362#issuecomment-516202918.

@lheckemann Can we format the expression as @jtojnar https://github.com/NixOS/nixpkgs/blob/4bc5288ac9f6d99ca595433fcaf9fa4ca9fbe5a5/pkgs/applications/networking/calls/default.nix.
That's a code style we're pretty much going for. You could even push that expression manually.

Wow, that was a funky history. Rebase completely failed..? Anyway, here's my second cleanup attempt :)

@lheckemann libhandy and modemanager are both sill in nativeBuildInputs.


Consider JSpecify or The Checker Framework instead of JetBrains Annotations

Pros of JSpecify

Standard across multiple tools
Very well-defined spec
Fully supported by Kotlin

Cons of JSpecify

Not much adoption or support by tools yet
Still unstable

Pros of The Checker Framework

Can completely eliminate NullPointerExceptions

Cons of The Checker Framework

From what I know, even if we use The Checker Framework, IntelliJ will still assume unannotated types as @UnknownNullability

Pros of JetBrains Annotations

Full IDE support (good for newbies)

Cons of JetBrains Annotations

Some annotations use the TYPE_USE target while others don't
No documentation
Annotation must be applied on every type

Going to continue using JetBrains Annotations until JSpecify 1.0.0 releases.