Fails when there is an escape character in a commit message

Indeed, it is a bad idea to have such characters in the commit messages but darcs chandles them:
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/parsers/treeparser.rb:96:in `rescue in parse': #<RuntimeError: Illegal character "\b" in raw string "Toujours en DISCUSS a l'IEG\bSG"> (REXML::ParseException)
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/text.rb:140:in `block in check'
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/text.rb:136:in `each'
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/text.rb:136:in `check'
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/text.rb:122:in `initialize'
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/parsers/treeparser.rb:47:in `new'
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/parsers/treeparser.rb:47:in `parse'
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/document.rb:448:in `build'
/usr/lib/ruby/gems/3.2.0/gems/rexml-3.2.5/lib/rexml/document.rb:101:in `initialize'
../darcs-to-git/darcs-to-git:326:in `new'
../darcs-to-git/darcs-to-git:326:in `read_from_repo'
../darcs-to-git/darcs-to-git:564:in `<main>'
...
Illegal character "\b" in raw string "Toujours en DISCUSS a l'IEG\bSG"
Line: 6126
Position: 465373

The problem suggested by this stacktrace is that Darcs is outputting characters that are illegal in XML — we're using this darcs command to export changes.

Darcs is outputting characters that are illegal in XML

You mean darcs should escape these characters, and I should report this bug against darcs ?

Yes. In XML 1.0 these characters were completely illegal, and in XML 1.1 they must be escaped. Here they are apparently unescaped, and are therefore invalid for both versions of the XML format.

Yes. In XML 1.0 these characters were completely illegal, and in XML 1.1 they must be escaped.

https://bugs.darcs.net/issue2732


KAFKA-10431: Sequential selection of payload in ProducerPerformance

https://issues.apache.org/jira/browse/KAFKA-10431
Currently, ProducerPerformance randomly selects a payload from the payload file when sending message. This might cause the some payloads being selected more times than others. It's better to do sequential selection of payloads.
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ijuma Please review this patch. Thanks.

Currently the --num-records is the actual number of records sent, which are randomly selected from the payload file.
What if  --num-records < the entries in the payload file?, Would you then start reading from the start of the payload file again?

@zaahirlaher Duplicates could not be avoided with the randomly-selecting strategy as well. Besides, it could happen that some events would not be chosen to be sent at all. Looping all the messages from the start of the file is a better message-selection method.


washer time remain defaults to 0:01

Using the integration on a brand new LG front load washer, everything works as expected except when there is no load the remain time attribute defaults to 1:00, not sure where this is coming from but it reports this even when the washer is off.

@mcnutter1 is it a WM8900HBA ? I am having the exact same issue.
Also with the count down timer, it seems to keep going down 1 minute on lovelace.

@mcnutter1 is it a WM8900HBA ? I am having the exact same issue. Also with the count down timer, it seems to keep going down 1 minute on lovelace.

Exactly, same model.
I made some workarounds in the Lovlace UI to make it look nicer by using a condition for that field to show.
Also, for some reason the Power On attribute is always on, even when the Washer is Off.

Please provide integration diagnostic file when device is in this specific state / condition

Close this a s duplicate of #544


[compdb] Expand response files inline based on a switch.

References to response files in a clang compile_commands.json file can
be tricky to deal with when tooling expects all the command flags to be
present in the 'command' field.
This change introduces a '-x' option to '-t compdb' that will expand
@rspfile style response file invocations inline.
E.g.
$ ninja -t compdb cc
[
  {
    "directory": "/src/foo",
    "command": "cc -foo -bar @foo.obj.rsp",
    "file": "foo.cc"
  }
]

$ ninja -t compdb -x cc
[
  {
    "directory": "/src/foo",
    "command": "cc -foo -bar foo.cc",
    "file": "foo.cc"
  }
]

Does this change seem reasonable?
I tested this manually. The tools are all implemented in ninja.cc and none of them seem to have tests. I'd need to refactor that file to expose the tooling for tests. I wanted to check with folks on whether this is a reasonable change before I went ahead and did the necessary reworking of ninja.cc to expose tools for tests.

The reason for the rspfile in the first place is when command lines exceed OS limits.  Is it possible to adjust your .ninja generator to not use them in cases like these where you believe you can use the command line without an rspfile?

Those were just examples :) The use case here is to make the compile_commands.json file more readily consumable.
As you noted, the response files are only useful as a workaround for shell command line restrictions. These limits don't translate to the use cases for a compilation database. The clang tooling, for example, parses the command line directly rather than pass it through the shell.
A more real world example would be Chromium. On Windows we make heavy use of response files in clang-cl and cl invocations. A typical command line looks like:
C:\goma/gomacc.exe ../../third_party/llvm-build/Release+Asserts/bin/clang-cl.exe /nologo /showIncludes /FC @obj/third_party/protobuf/protoc_lib/cpp_field.obj.rsp /c ../../third_party/protobuf/src/google/protobuf/compiler/cpp/cpp_field.cc /Foobj/third_party/protobuf/protoc_lib/cpp_field.obj /Fd"obj/third_party/protobuf/protoc_lib_cc.pdb"

Let's say we need to consume the compilation database for semantic code completion or source indexing, then we'd need to always run a full build and retain the response files. All this despite the fact that the full command line was always available to ninja the whole time. It would be much easier if we had something like the -x option to expand the full command line.

Sorry, this fell through the cracks. I'll address @jhasse 's comments in a new patchset shortly.

Re Chromium: Apparently I wondered why we use rspfiles for compiles before in https://chromium-review.googlesource.com/c/chromium/src/+/832593#message-0406d8fd9edea87bf503144ce90c918968b26e9c and the answer was "no good reason" and we removed that. So chromium compdbs no longer use rspfiles for compiles.
The patch is still useful for other projects, and the bar for -t tools is lower, so I'm fine merging this. But it's a close call since
1.) The -d keeprsp -n workaround isn't that bad.
2.) Most projects shouldn't use rspfiles for their compiles.

2.) Most projects shouldn't use rspfiles for their compiles.

What do you think about making them opt-in instead? That way projects like Meson would also not need to check for availability of the -x flag to fix https://github.com/mesonbuild/meson/issues/3030.

"them" meaning?

rspfiles

Sorry, I've mixed up some stuff. I meant for the compdb tool, so that instead of passing -x, rsp files will get expanded by default, regardless of their use for compiling.

That seems overly magic to me.
Tangentially, do you know why meson uses rspfiles for compiles?

(Addressed the comment and updated the PR, also tested on macOS and Linux with a build file that used rspfile.)

Tangentially, do you know why meson uses rspfiles for compiles?

Yes, to fix https://github.com/mesonbuild/meson/issues/271.

(I'm using the PR in my own ninja fork (https://github.com/leandros/ninja) for roughly 6 months in production without any problems.

@Leandros gn doesn't use rspfiles by default for compiles any more, see my https://github.com/ninja-build/ninja/pull/1223#issuecomment-378969196 above. I commented on the meson issue.
(To be clear, I'm not arguing against this patch, I'm just saying that generators that produce ninja files containing many rspfiles for compilations likely have opportunities to improve since rsp files shouldn't be necessary for the vast majority of compiler invocations, and including them slows down your build.)

Thanks for the patch!

And just to reiterate, users of ninjas that don't have this flag yet can run ninja -d keeprsp -n to generate the rsp files and then use the compdb that does point to rspfiles.

Yay!


macOS: Unable to compile universal scipy

When using universal Python version and trying to install scipy, I'm getting a build of scipy that does not work for one of the architectures.
Apparently, issue is due to fact that gfortran unable to build binaries with multiple architectures.
$ gfortran -arch i386 -arch x86_64 x.f
gfortran: warning: x86_64 conflicts with i386 (arch flags ignored)

On top of that, numpy.distutils replace architecture i386 with i686, which doesn't work even by itself
$ gfortran -arch i686 x.f
gfortran: error: this compiler does not support i686

gfortran was installed as part of Homebrew's gcc package:
$ gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/local/Cellar/gcc/7.1.0/libexec/gcc/x86_64-apple-darwin16.5.0/7.1.0/lto-wrapper
Target: x86_64-apple-darwin16.5.0
Configured with: ../configure --build=x86_64-apple-darwin16.5.0 --prefix=/usr/local/Cellar/gcc/7.1.0 --libdir=/usr/local/Cellar/gcc/7.1.0/lib/gcc/7 --enable-languages=c,c++,objc,obj-c++,fortran --program-suffix=-7 --with-gmp=/usr/local/opt/gmp --with-mpfr=/usr/local/opt/mpfr --with-mpc=/usr/local/opt/libmpc --with-isl=/usr/local/opt/isl --with-system-zlib --enable-checking=release --with-pkgversion='Homebrew GCC 7.1.0' --with-bugurl=https://github.com/Homebrew/homebrew-core/issues --disable-nls
Thread model: posix
gcc version 7.1.0 (Homebrew GCC 7.1.0)

Reproducing code example:
arch -32 python -mscipy.special

Error message:
$ arch -32 python -mscipy.special
Traceback (most recent call last):
  File "/usr/local/Cellar/python27/2.7.13_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 163, in _run_module_as_main
    mod_name, _Error)
  File "/usr/local/Cellar/python27/2.7.13_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 111, in _get_module_details
    __import__(mod_name)  # Do not catch exceptions initializing package
  File "/Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/special/__init__.py", line 640, in <module>
    from ._ufuncs import *
ImportError: dlopen(/Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/special/_ufuncs.so, 2): no suitable image found.  Did find:
    /Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/special/_ufuncs.so: mach-o, but wrong architecture
    /Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/special/_ufuncs.so: mach-o, but wrong architecture

$ file /Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/special/_ufuncs.so
/Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/special/_ufuncs.so: Mach-O 64-bit bundle x86_64

But some libraries were built as universal binaries:
$ file /Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/_lib/*.so
/Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/_lib/_ccallback_c.so:    Mach-O universal binary with 2 architectures: [i386: Mach-O bundle i386] [x86_64: Mach-O 64-bit bundle x86_64]
/Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/_lib/_ccallback_c.so (for architecture i386): Mach-O bundle i386
/Users/user/.virtualenvs/d/lib/python2.7/site-packages/scipy/_lib/_ccallback_c.so (for architecture x86_64):   Mach-O 64-bit bundle x86_64

Scipy/Numpy/Python version information:
$ lipo -info /usr/local/Cellar/python27/2.7.13_2/bin/python2.7
Architectures in the fat file: /usr/local/Cellar/python27/2.7.13_2/bin/python2.7 are: x86_64 i386

Python 2.7.13 or 3.6.1
Numpy 1.12.1
Scipy 0.19.1

There was a temporary OS X build issue that was fixed just a couple of days ago. Can you try again?
If it remains, then looks like a regression in gfortran

@rgommers Could you please point me to issue/commits? I didn't find them while searching.

@sashkab that was gh-7558

OS X build is fine for me right now, with gfortran 4.9.1 (also installed with Homebrew). If your issue is not solved with current master, checking that you can build with 4.9.1 but not with 7.1.0 anymore would be helpful.

Build is fine, but a lot of .so's are built as thin binaries x86_64; while others are fat with i386 x86_64.

That's weird, can you put your full build log in a gist and link to it?
Note that SciPy should work for you now, i386 is basically irrelevant by now.

i386 is basically irrelevant by now.

Unfortunately not for us. We sometimes need to run our code in the 32-bit environment on 64-bit macOS system. Not only we couldn't built scipy as universal build, we failed to build it as 32-bit version as well, due to the code in the numpy's distuils. We managed to built 32-bit only version by removing L291-292 and  changing L295 to for arch in ["i386"]:.
Not sure if it matters, gfortran is version 7.1.0 from homebrew.

Hmm, that code on L291-295 hasn't been changed in 7 years, so must be something in newer gfortran. That definitely used to work.

Unfortunately not for us. We sometimes need to run our code in the 32-bit environment on 64-bit macOS system.

Out of interest: can you share why you need this?

I'm currently having this problem too, but really just because I'm curious what the "best" way to create a fat binary with gfortran on OS X is (I have the Homebrew gfortran, version 7.2.0).
The following example "works", but it is inelegant. TL;DR, but two static binaries and combine them with lipo (yes, the tool's name is an inside-joke about fat-binaries).

Simple subroutine in foo.f90:
subroutine bar(x, y, z) bind(c, name='bar')
  integer, intent(in) :: x, y
  integer, intent(out) :: z

  z = x + y

end subroutine bar

Compile two static binaries:
$ gfortran -arch i386 -c foo.f90 -o foo.o
$ ar -rcs libfoo_i386.a foo.o
$ rm -f foo.o
$
$ gfortran -arch x86_64 -c foo.f90 -o foo.o
$ ar -rcs libfoo_x86_64.a foo.o
$ rm -f foo.o

and then combine them:
$ lipo \
>   libfoo_i386.a libfoo_x86_64.a \
>   -create \
>   -output libfoo.a
$
$ # Inspect our work
$ otool -L libfoo.a
Archive : libfoo.a
libfoo.a(foo.o):
$ file libfoo.a
libfoo.a: Mach-O universal binary with 2 architectures
libfoo.a (for architecture i386):       current ar archive random library
libfoo.a (for architecture x86_64):     current ar archive random library

Then if we want to, for example, use it from a Cython module wrapper.pyx:
cdef extern void bar(int *x, int *y, int *z)

def triple_bar(int x, int y):
    cdef int z
    bar(&x, &y, &z)
    return 3 * z

We can make a fat binary Python extension module (this is a bit stripped down / let distutils do this for you):
$ cython wrapper.pyx
$ clang \
>   -arch i386 -arch x86_64 \
>   -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 \
>   -c wrapper.c \
>   -o wrapper.o
$ clang \
>   -arch i386 -arch x86_64 \
>   -bundle \
>   -undefined dynamic_lookup \
>   -L. -lfoo \
>   wrapper.o \
>   -o wrapper.so
$
$ file wrapper.so
wrapper.so: Mach-O universal binary with 2 architectures
wrapper.so (for architecture i386):     Mach-O bundle i386
wrapper.so (for architecture x86_64):   Mach-O 64-bit bundle x86_64

once doing this, we can use the fat binary:
$ arch -32 /usr/bin/python -c 'import wrapper; print(wrapper.triple_bar(3, 7))'
30
$ arch -64 /usr/bin/python -c 'import wrapper; print(wrapper.triple_bar(2, 3))'
15

NOTE: The above uses the OS X system Python 2.7 so you may have a different include dir than /System/Library/.../python2.7 and a different executable than /usr/bin/python
(Empirically, I've observed that the x86_64 non-fat binary works just fine with arch -32, but the i386 non-fat binary does not work with arch -64.)

NumPy dropped 32-bit macOS support and didn't fix a bug related to that: https://mail.python.org/pipermail/numpy-discussion/2018-August/078582.html. So we're not supporting it anymore either; 32-bit macOS is not relevant anymore. So closing as wontfix.


percent of windows for mod CpG had less than 1 calls greater than 50.00 windows are uncovered, aborting.

hi @adamewing,
Firstly thank you for providing this package. ı am trying to see whole chromosome methylation for different sample and I used methylartist region -i 22:1-50818468 -d allcombined_data_nanopolish.txt -p 32 -g Homo_sapiens.GRCh38.106.sorted.gtf.gz -n CG -r wholegenome.fasta --skip_align_plot --panelratios 1,0,1,4 --height 4.5 --genepalette viridis --samplepalette viridis but ı get 89.10 percent of windows for mod CpG had less than 1 calls
greater than 50.00 windows are uncovered, aborting.
I have a very small read depth it might cause the error but ı am wondering if is there any way to turn around this. thanks.

You could try setting --maxuncovered to 100 but if coverage really is that low the output may not be that useful or representative of reality. Another option with similar caveats would be to try larger values for -s (--smoothwindowsize) to include more reads per window - the automatically set value will be at the beginning of the terminal output.

hi @adamewing  thank you for your advice but ı am getting a different error and ı don't understand why because it pops up even in previous working examples. the error is methylartist database (seg_chrom) does not exist, check that full path is included if not in current working directory. I checked the bed and .tsv file and ı can definitely say that there is seg_chom column in .tsv file I am cofused. thanks

This might be due to the wrong file being passed to -d, could you tell me the command line args & full output?

yes ı picked up the wrong file that was my mistake thanks for the answer.:) not .tsv file it should be.txt file ..:(

No worries - presuming this is closable but let me know if you're still having trouble.


Add a Gitter chat badge to README.md

FOSS-Cell-GECPKD/tetris now has a Chat Room on Gitter
@AnandBaburajan has just created a chat room. You can visit it here: https://gitter.im/FOSS-Cell-GECPKD/tetris.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Thank You


Added Singly Linked List [Java]

fixes #126

By submitting this pull request I confirm I've read and complied with the below requirements.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the coding guidelines for this project.
[x] My code follows the skeleton code structure.
[x] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.

@aashutoshrathi Please fix your codacy.

@Monal5031 Please update your review.

@singhpratyush I tried solving the issues by changing it to private. But then the Node can't be accessed in the LinkedList class.

How to call the main method if it's not in public class of the program? Therefore, shouldn't the filename and public class name should be consistent?

@PiyushPawar17 Adding to what @singhpratyush said, does this Java file run as it is? Because it's main method is located in LinkedListTest class whereas file name is LinkedList. I recommend you merge both classes into class LinkedList.

@aviaryan @singhpratyush I merged both classes into class LinkedList but "non-static type variable T cannot be referenced from a static context" this error occurred.

@singhpratyush Please update your review.

@singhpratyush @aviaryan Is that change fine?

@singhpratyush Please update your review.

@aviaryan: Codacy issues are valid.


Using a piped function within another function

Describe the issue
Inside the Pipe Operator section:
There doesn't seem to be an example of using a piped function within another function in the curriculum. For example:
the hint shows for the example:
add = fn int1, int2 -> int1 + int2 end
subtract = fn int1, int2 -> int1 - int2 end
multiply = fn int1, int2 -> int1 * int2 end

10
|> add.(2)
|> multiply.(2)
|> subtract.(4)

which can be confusing because we have been writing functions up to this point now. I think it would be helpful to at least give a small example of how a pipe is added inside a function. Example:
add = fn int1, int2 -> int1 + int2 end
subtract = fn int1, int2 -> int1 - int2 end
multiply = fn int1, int2 -> int1 * int2 end

all_together_now = fn -> 10
  |> add.(2)
  |> multiply.(2)
  |> subtract.(4)
end

#calling the function
all_together_now.()

You could use a smaller example without giving a full solution of course, just so people could see how to actually use pipes within a function.
Hope that helps.

I'm not sure how adding Pipes within a function adds more clarity. Pipe operators are a separate concept from writing code inside the body of a function, and it doesn't change how we use them, whether they are inside a function or not.
I will close this issue for now but am still open to further discussion if you disagree.

Maybe it's my lack of understanding, but this bit of code
10
|> add.(2)
|> multiply.(2)
|> subtract.(4)
Is confusing on it's own. There's the number 10, but no indication that anything is being done to it. Am I just missing something, because I thought that pipes are away to organize/use functions within a function.

A pipe takes any value and passes it as the first argument to a function. It is a way of calling a series of functions.
flowchart
i1[input 10]
f1[add 2]
o1[output 12]
f2[multiply 2]
o2[output 24]
f3[subtract 4]
o3[output 20]

i1 --> f1 --> o1 -->
f2 --> o2 -->
f3 --> o3

Therefore it's common to start with an elixir term such as 10 and then pipe it into the first function in a series of piped functions.
So the following code evaluates like so:
Step 1:
10
|> add.(2)
|> multiply.(2)
|> subtract.(4)

Step 2
12
|> multiply.(2)
|> subtract.(4)

Step 3
24
|> subtract.(4)

Step 4
20

Ahhh ok that makes sense now. Thank you 😊
On Sat, Oct 1, 2022, 2:10 AM Brooklin Myers @.***>
wrote:

A pipe takes any value and passes it as the first argument to a function.
It is a way of calling a series of functions.
flowchart
i1[input 10]
f1[add 2]
o1[output 12]
f2[multiply 2]
o2[output 24]
f3[subtract 4]
o3[output 20]
i1 --> f1 --> o1 -->
f2 --> o2 -->
f3 --> o3
Therefore it's common to start with an elixir term such as 10 and then
pipe it into the first function in a series of piped functions.
So the following code evaluates like so:
Step 1:
10|> add.(2)|> multiply.(2)|> subtract.(4)
Step 2
12|> multiply.(2)|> subtract.(4)
Step 3
24|> subtract.(4)
Step 4
20
—
Reply to this email directly, view it on GitHub
https://github.com/DockYard-Academy/beta_curriculum/issues/405#issuecomment-1264272862,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEHURANDP22TRUQ6LLPDCMTWA7PVDANCNFSM6AAAAAAQW477IQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

It does help us organize functions, as the alternative would be the following without the pipe operator:
|subtract.(multiply.(add.(10, 2), 2), 4)

However, the within a function part is optional, not mandatory. Using the pipe operator within a function is the same as writing any code. There is no change, we simply put the same code in the body of the function.

I think I should add this to the reading material. I'm going to reopen this issue to remind myself to address this.

Closing this issue because we already have the example I thought I needed to add in:


Not able to boot bootstrap server --bootstrap ignition file its running in loop and starting with emergency mode

We are installing OKD 4.5.0 Openshift version on RHCOS 4.5.2 & RHEL 7.8 (service server) Operating system . we are planning to create 3 master and 2 worker node.
We have created Service server (Helper node) with RHEL OS.
Ignition files(bootstrap ,master and worker) has been created on Same server.
While running kernel command with bootstrap ignition file its running in loop and starting with emergency mode on bootstrap server .
We are unable to boot the bootstrap node .
Attached error screenshot . Please help us to resolve the issue.

OKD 4.5.0 Openshift version on RHCOS 4.5.2

OKD doesn't have 4.5.0 version and it doesn't use RHCOS. See installer troubleshooting

Hi Vadim,
We have download OKD 4.5.0 software from below link.
https://github.com/openshift/okd/releases/download/4.5.0-0.okd-2020-07-29-070316/openshift-client-linux-4.5.0-0.okd-2020-07-29-070316.tar.gz
https://github.com/openshift/okd/releases/download/4.5.0-0.okd-2020-07-29-070316/openshift-install-linux-4.5.0-0.okd-2020-07-29-070316.tar.gz

As per documentation FCOS is only supported operating system.
https://docs.okd.io/latest/architecture/architecture-rhcos.html#rhcos-about_architecture-rhcos
FCOS is the only supported operating system for OKD control plane, or master, machines. While FCOS is the default operating system for all cluster machines, you can create compute machines, which are also known as worker machines, that use Fedora as their operating system


Could not load module lime@lime_application_create__prime

Describe your bug here.
I wanted to play a mod but wanted to play the game first. BUT it said the message instead of the game

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No, I got it and it said the message when opened

corrupted lime.ndll or if you installed 32-bit install 64-bit

corrupted lime.ndll or if you installed 32-bit install 64-bit

I installed 64-bit.


Latest release information on the Design system website

As a Design System user
I want access the list of items included in the latest release directly from the Design System website
So that I don't have to use any other sources
Description
Currently we only provide the release information in the slack channel with the link to GitHub.
Users from outside of ONS can't easily access the release details which would include:

release number
release date
link to GitHub release note

Other Design systems are including the detail of latest release on the main page.
It would be a good practise to do the same.
Acceptance Criteria

User can open Design System website
User can see release number
User can see release date
User can see link to GitHub release note

Visualisation/Input from UCD

Linked User stories/epics
Technical details (optional)
Link to the latest release
MVP (optional)
Suggestion - replicate GDS example and manual update

UCD team to be consulted

Ticket added to UCD board for design: https://jira.ons.gov.uk/browse/CU-121

I'm closing this ticket as we cover it in ticket #204


Keyboard shortcut for selecting Conda environment in Visual studio code for Mac is missing

Of course I have faith that most users of VS Code on Mac knows about the corresponding keyboard shortcut for CTRL-SHIFT-P (CMD-SHIFT-P) for opening the Command Palette, but i still think it is worth mentioning.
Also, another thing. Sometimes I have needed to restart VS Code before it could recognize my newly created environments. I'm not sure if it was due to some setting or error on my side, but if it is a common thing, then I think that also would be worth mentioning in the document.
Thanks in advance!

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

ID: 955b2d92-2d6a-787e-6612-d226e09b9a9a
Version Independent ID: 734d767b-f22d-2ba6-aabf-98b07bf5abfc
Content: Configure a development environment for Azure Machine Learning
Content Source: articles/machine-learning/service/how-to-configure-environment.md
Service: machine-learning
GitHub Login: @rastala
Microsoft Alias: roastala

@ArvidBaa Thanks for the feedback! We are currently investigating and will update you shortly.

@ArvidBaa Hi, thanks for the reporting, I have fixed it. You should see the change shortly.  We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


waitdelay property sign has no effect on trains

Info
Please provide the following information:

BkCommonLib Version (/train version): 1.20.6-v1
TrainCarts Version (/train version): 1.20.6-v1
Server Type and Version (/version): Paper 1.20.6

Bug
The property sign does not change the wait.delay property of trains as intended.
Description
The waitdelay property sign should modify the waitdelay property of trains.
However, in my testing, it does not have any effect on the train at all.
Expected behaviour
The sign should change the train's wait delay to the amount defined on the sign.
E.g., a waitdelay property sign with the number set to 5 should change the train's wait delay to 5 seconds.
Actual behaviour
The sign does not have any effect on the train, even when using an always-on power mode [+train].
The train retains the same wait delay it has previously set.
Steps to reproduce
For a wait delay of 5 seconds:
Build a waitdelay property sign with the following format:
[+train]
property
waitdelay
5

Have a train run over the sign.

It works for me, but maybe its not fully clear what the wait delay does. With a wait delay set, if the train is put to a complete stop (not if its moving super slowly following another train), then before starting to move again it waits this delay.
How did you expect the wait delay to function?
What I tested:
I spawned a train with a wait distance set, delay 0, then a waitdelay property sign sets it to 5. Now when the train is stopped by a still-standing train, and I destroy that still-standing train, it waits for the $waitdelay before starting to move again.

That is exactly how I expected the wait delay to function.
For whatever reason, when I tested it, the waitdelay property sign does not do anything.
I even selected the train and ran /train property wait delay to check, and indeed the sign did not change the wait delay.

Was the placement correct, so that the train is facing the sign (direction?). Can you [+train:*] to activate from any direction

The sign was placed on the side of the block the rails are on, so the train sees the side of the sign. This should be a correct placement as far as I know.

Can you include a screenshot? It sounds correct yes. Still worth checking if the * makes a difference

This was the setup I had:

The sign was lined up with a bunch of other property signs (the others all work by the way).
I had a train run over it, then I ran /train wait delay to check it's wait delay, instead of 5 it was 20:

I don't even know where the 20 came from, since I did not set the number 20 in the DefaultTrainProperties config at all.
I also tried with the *, sadly it did not make any difference.

As a hunch, I decided to place another waitdelay sign further down the track just by itself:

This time, it actually worked:

Not sure what is going on here but at least I made progress.

The 20 came from the waitacceleration sign, and without your screenshots I never wouldve figured that out haha
Thanks, this should fix it
https://ci.mg-dev.eu/job/TrainCarts/1600/

Looks good, though I sadly can't test it right now since its a build for 1.21, and our server can't update to that until all our plugins are updated.

Builds 1.21 work on older server versions


[Tests-only] bump web and core commit id

bump web and core commit id

https://drone.owncloud.com/owncloud/ocis/3941/73/7
various changes to line numbers of expected failures are needed.
https://drone.owncloud.com/owncloud/ocis/3941/27/7


PowerToys Run calculation error

Microsoft PowerToys version
0.65.0
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
PowerToys Run
Steps to reproduce
In the PowerToys Run box entering "0.071 * sqrt(2)" or "0.071 * 1.41"

✔ Expected Behavior
0.100. Correct answer to equation
❌ Actual Behavior
1.00. Incorrect answer
Other Software
No response

Unfortunately, this is a known issue. See /duplicate #19741. The cause is that the first zero(s) in the fractional part are trimmed off.


ImportError: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found

Hello. I have installed the most recent version of habitat-lab from the master branch, and installed habitat-sim via the headless option
conda install habitat-sim withbullet headless -c conda-forge -c aihabitat
I am trying to run the DD-PPO training script indicated here: https://github.com/facebookresearch/habitat-challenge#pointnavobjectnav-baselines-and-dd-ppo-training-starter-code
When I tried running the DD-PPO script by
sh habitat_baselines/rl/ddppo/single_node.sh from the habitat-lab directory, it gave me an error
ImportError: /lib64/libstdc++.so.6: version CXXABI_1.3.8' not found`
I suspected a gcc version mismatch, and tried conda install habitat-sim withbullet headless -c conda-forge -c aihabitat with gcc 4.8.5, 5.4.0 and 9.3.0 but none of them worked.
Would appreciate any pointers!
Please find attached the error message screen shot.

Conda ships its own libstdc.  Doing ls ${CONDA_PREFIX}/lib | grep stdc should show it. That should also get picked up automatically, but you can add export LD_LIBRARY_PATH=${CONDA_PREFIX}/lib:${LD_LIBRARY_PATH} to help things out.

Wow, you are amazing!! Adding the latter solved it! Thank you so much!!


REED unable to synchronize network data to Leader when Leader has smaller routerupgradethreshold

Describe the bug
If the Leader has smaller routerupgradethreshold than the REED, the REED will keep sending AddressSolicit and being rejected by the Leader. In the meantime, the REED won't be able to synchronize local network data to Leader, e.x. it won't be able to become Primary BBR.
To Reproduce

Git commit id: master
IEEE 802.15.4 hardware platform: simulation
Build steps:

make -f examples/Makefile-simulation BACKBONE_ROUTER=1 THREAD_VERSION=1.2

Network topology

Leader---REED

Execution steps:

Start the leader and wait for it to become leader
Set routerupgradethreshold to 1 on Leader: routerupgradethreshold 1
Start the REED
Start BBR service on REED: bbr enable
Wait for a long time, but REED never become Primary BBR:

node 2> bbr enable
Done
node 2>
node 2> bbr
BBR Primary: None
Done

Expected behavior
The REED should become Primary BBR.
Proposed fix
A simple fix can be if the REED receives a/as ACK with status == 1 (No Address Available), it can update its routerupgradethreshold like below:
routerupgradethreshold = min(routerupgradethreshold, active_router_count)

This can help the node exit REED status and return back to child state.
Thoughts? @librasungirl @jwhui

It should be a common issue regardless of the Thread version. And it may happen in user scenarios when Thread devices from different vendors have different routerupgradethreshold configuration (though default 16, but it is configurable).
@simonlingoogle in your proposal, will it change the mRouterUpgradeThreshold?
I may suggest to introduce a variable like mRunningRouterUpgradeThreshold, thus when the device need to become Leader due to lost of Leader, it still have the chance to adopt its original mRouterUpgradeThreshold value when deciding whether or not to allocate Router ID for the others.

It should be a common issue regardless of the Thread version.

Yes, it is a common issue. I am using BBR service mainly for easy illustration. The issue can happen whenever the Leader has smaller routerupgradethreshold than the REED.

@simonlingoogle in your proposal, will it change the mRouterUpgradeThreshold?

Yes.

I may suggest to introduce a variable like mRunningRouterUpgradeThreshold, thus when the device becomes Leader somehow e.g. due to lost of Leader, it still have the chance to adopt its original mRouterUpgradeThreshold value when deciding whether or not to allocate Router ID for the others.

I would prefer not introducing another variable a little bit because extra RAM and code will be required for storing, accessing and updating the new mRunningRouterUpgradeThreshold variable, whereas in the proposed fix, no other logic change is required after mRouterUpgradeThreshold is altered.
We also need to clear mRunningRouterUpgradeThreshold when  mRouterUpgradeThreshold is configured again otherwise the new mRouterUpgradeThreshold is ineffective, to the surprise of users.

If so, some scenarios you may need to consider

how many active routers would you expect in the Thread Network formed by the device itself if it once joined  a Thread network with lower upgradethreshold?
what if there is partition and migration, and the device attaches to a partition with a Leader which has bigger upgradethreshold setting, should it try to become active router? How to update to a bigger upgradethreshold?

how many active routers would you expect in the Thread Network formed by the device itself if it once joined  a Thread network with lower upgradethreshold?

mRouterUpgradeThreshold will keep unchanged without further configuration.

what if there is partition and migration, and the device attaches to a partition with a Leader which has bigger upgradethreshold setting, should it try to become active router? How to update to a bigger upgradethreshold?

It can't. But it would be the responsibility of the network administrator to set routerupgradethreshold configuration correctly in the whole network. So, the proposed fix is a simple workaround for OpenThread to "fix" the incorrect configuration.

@jwhui Any thoughts on this issue?

@jwhui Any thoughts on this issue?

The Thread Specification sets ROUTER_UPGRADE_THRESHOLD to 16 and does not provide any provisioning for changing the value. As a result, any Thread network in production should this value.
Is changing the ROUTER_UPGRADE_THRESHOLD needed for testing when operating as a reference device in the Thread Test Harness? If so, I would be fine introducing a new variable. We may also want to wrap the ROUTER_UPGRADE_THRESHOLD setting under the REFERENCE_DEVICE build feature.

The Thread Specification sets ROUTER_UPGRADE_THRESHOLD to 16 and does not provide any provisioning for changing the value. As a result, any Thread network in production should this value.

👍
Confirmed there is note in the API as well.
https://github.com/openthread/openthread/blob/b37528645a57ca963dc847a67a2d783d401c20c6/include/openthread/thread_ftd.h#L342-L354

Is changing the ROUTER_UPGRADE_THRESHOLD needed for testing when operating as a reference device in the Thread Test Harness? If so, I would be fine introducing a new variable. We may also want to wrap the ROUTER_UPGRADE_THRESHOLD setting under the REFERENCE_DEVICE build feature.

Yes,  different from Thread 1.1 TH, to avoid a large scale testbed for REED DUT role, Thread 1.2 TH chooses to update the ROUTER_UPGRADE_THRESHOLD on the reference leader device which would reject the address solicit from DUT to fake the test scenario.

Yes, different from Thread 1.1 TH, to avoid a large scale testbed for REED DUT role, Thread 1.2 TH chooses to update the ROUTER_UPGRADE_THRESHOLD on the reference leader device which would reject the address solicit from DUT to fake the test scenario.

Despite that, the Thread 1.2 certification do requires that the REED DUT, which is not necessarily a Reference Device, to work normally when the Leader keeps rejecting it's a/as. Unfortunately the current OT implementation does not work well in such condition.
We would require the new variable mRunningRouterUpgradeThreshold logic on all REED devices (can not wrap with REFERENCE_DEVICE).

Despite that, the Thread 1.2 certification do requires that the REED DUT, which is not necessarily a Reference Device, to work normally when the Leader keeps rejecting it's a/as. Unfortunately the current OT implementation does not work well in such condition.
We would require the new variable mRunningRouterUpgradeThreshold logic on all REED devices (can not wrap with REFERENCE_DEVICE).

I don't think we should be assuming a different value for the router upgrade threshold.
How about we allow sending SVR_DATA.ntf after a REED receives an ADDR_SOL.rsp message with Status TLV indicating "No Address Available"?

How about we allow sending SVR_DATA.ntf after a REED receives an ADDR_SOL.rsp message with Status TLV indicating "No Address Available"?

Sounds great to me. This will make OT work normally in REED state. I will create a PR to enhance accordingly.

PR #4834 has been created for addressing this issue.
However I found there is some issues in the current fix.
Whenever the REED tries to send SVR_DATA.ntf, it will check ExpectBecomeRouterSoon and giveup sending if ExpectBecomeRouterSoon returns TRUE.
If the REED sends SVR_DATA.ntf before sending ADDR_SOL.req, and then the ADDR_SOL.req is rejected, the REED will have to wait for a period of time (at most GetRouterSelectionJitterTimeout()+1 seconds) for the next SVR_DATA.ntf.
Same issue may also apply to future Thread 1.2 DUA registraion features, in which DUA registration will be delayed until next renewing.
So, should the REED try to resend SVR_DATA.ntf and DUA registration when its a/as is rejected?


how can i delete some fields with dejavu

like this tittle, i want to delete some fileds with dejavu，but i can not find that。-_-;

@silvermoonhy you cannot delete a field using Dejavu.
Schema setting is an exclusive feature of https://appbase.io/#hosting,
You can bring your own ElasticSearch Cluster to Appbase.io or create one using Appbase hosting services.
Here is an example of that


Subtitle styles are broken

Color is missing and format has errors based on Validator (tried rescale-subtitles true/false - was no difference)
Before
[V4+ Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Default,Noto San,30,&H00FFFFFF,&H000000FF,&H00000000,&H501D0032,0,0,0,0,100,100,1,0,1,1.5,0,2,0,0,30,1

After Sushi.Net
[v4+ styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Default,Noto Sans,30,&H00FFFFFF,&H000000FF,,&H501D0032,0,0,0,0,100,100,,0,1,1.5,0,2,0000,0000,0030,1

Issues

OutlineColour value is gone
Spacing value is gone (Validator - Skipping style value "" with non-numerical value for style field Spacing https://validator.subtitledpro.com/ )

Yes, there is a problem, the current parser do not take in account the
actual format line. But uses the more common one. Will fix.
El El lun, 11 dic. 2023 a la(s) 09:23, enter-a-random-username <
@.***> escribió:

Color is missing and format has errors based on Validator (tried
rescale-subtitles true/false - was no difference)
Before
[V4+ Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Default,Noto San,30,&H00FFFFFF,&H000000FF,&H00000000,&H501D0032,0,0,0,0,100,100,1,0,1,1.5,0,2,0,0,30,1
After Sushi.Net
[v4+ styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Default,Noto Sans,30,&H00FFFFFF,&H000000FF,,&H501D0032,0,0,0,0,100,100,,0,1,1.5,0,2,0000,0000,0030,1
Issues

OutlineColour value is gone
Spacing value is gone (Validator - Skipping style value "" with
non-numerical value for style field Spacing
https://validator.subtitledpro.com/ )

—
Reply to this email directly, view it on GitHub
https://github.com/maxpiva/Sushi.Net/issues/10, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI4G3OG7QX6IMWG3G5X5SDYI33K5AVCNFSM6AAAAABAPVOF5GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZTKNJWGEZTQOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I just ran into this issue as well. Is there a workaround?

Manually editing the file.
Writing my own script to fix the file.
Converting all ,, to ,?


Complete versioning of docs-searchbar in package.json

Update docs-searchbar minor patch

bors merge

bors merge


3600 fix dumb typo in management command

This fixes reporting in the new management command solr_update.

Pull Request Checklist:

[ ] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

[Enter positive test case here] After the change, the complete number of SOLR resources after update are reported. Before the change, only the ones before the update are reported.

@sblack-usu This corrects the printout for the management command. Dumb but effective.


sil: init at 1.3.0

Motivation for this change
Sil is a nice Middle-earth roguelike.
Some slightly annoying implementation wrinkles, in that we want to setup a user-specific data dir on startup, and copy in the shared data files.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build sil

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘Sil-1.3.0’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/games/sil/default.nix:48 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Failure on aarch64-linux (full log)
Partial log (click to expand)
trying http://www.amirrorclear.net/flowers/game/sil/Sil-130-src.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 17.0M  100 17.0M    0     0  6805k      0  0:00:02  0:00:02 --:--:-- 6805k
unpacking source archive /build/Sil-130-src.zip
error: zip file must contain a single file or directory.
hint: Pass stripRoot=false; to fetchzip to assume flat list of files.
builder for '/nix/store/5gyp2dk205s8zdyas1c40aj20n3y4kcc-source.drv' failed with exit code 1
cannot build derivation '/nix/store/sy0ywrk6dlhrgyazpwvb8pz1zwwm6s53-Sil-1.3.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/sy0ywrk6dlhrgyazpwvb8pz1zwwm6s53-Sil-1.3.0.drv' failed

Failure on x86_64-linux (full log)
Partial log (click to expand)
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 34140  100 34140    0     0   122k      0 --:--:-- --:--:-- --:--:--  122k

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0 17.0M    0  170k    0     0   125k      0  0:02:19  0:00:01  0:02:18  125k
  4 17.0M    4  745k    0     0   320k      0  0:00:54  0:00:02  0:00:52  319k
 12 17.0M   12 2176k    0     0   654k      0  0:00:26  0:00:03  0:00:23  654k
 29 17.0M   29 5128k    0     0  1181k      0  0:00:14  0:00:04  0:00:10 1181k
 55 17.0M   55 9720k    0     0  1824k      0  0:00:09  0:00:05  0:00:04 2016k
 94 17.0M   94 16.0M    0     0  2600k      0  0:00:06  0:00:06 --:--:-- 3280k
100 17.0M  100 17.0M    0     0  2711k      0  0:00:06  0:00:06 --:--:-- 4060k
unpacking source archive /tmp/nix-build-source.drv-0/Sil-130-src.zip
error: zip file must contain a single file or directory.
hint: Pass stripRoot=false; to fetchzip to assume flat list of files.
builder for ‘/nix/store/fms5bz66ym6jgclzzwalvs8izyb7qrm2-source.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/s6dw3axfrybqgprslv1ihj9wxnfk365g-Sil-1.3.0.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/s6dw3axfrybqgprslv1ihj9wxnfk365g-Sil-1.3.0.drv’ failed

I get the same failure as @GrahamcOfBorg

Hm, weird, I definitely don't get that. I'm building with nix-build -I nixpkgs=/path/to/my/fork -A sil, which seems to work fine.
I've added stripRoot=false, which doesn't seem to affect buildability for me, but maybe will fix it.

I'm able to build it.
@GrahamcOfBorg build sil

Success on x86_64-linux (full log)
Partial log (click to expand)
/tmp/nix-build-Sil-1.3.0.drv-0/source/Sil/src/util.c:238: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/7bs46ajnzw51r105qawls18q93if5m14-Sil-1.3.0
shrinking /nix/store/7bs46ajnzw51r105qawls18q93if5m14-Sil-1.3.0/bin/.sil-wrapped
strip is /nix/store/5qj61lcvzlap87rf6blvf8p577d482bv-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/7bs46ajnzw51r105qawls18q93if5m14-Sil-1.3.0/bin
patching script interpreter paths in /nix/store/7bs46ajnzw51r105qawls18q93if5m14-Sil-1.3.0
checking for references to /tmp/nix-build-Sil-1.3.0.drv-0 in /nix/store/7bs46ajnzw51r105qawls18q93if5m14-Sil-1.3.0...
/nix/store/7bs46ajnzw51r105qawls18q93if5m14-Sil-1.3.0

Success on aarch64-linux (full log)
Partial log (click to expand)
/build/source/Sil/src/util.c:238: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/2i9sqpfwm2l3g1m4pl602wyhr0z3jhy5-Sil-1.3.0
shrinking /nix/store/2i9sqpfwm2l3g1m4pl602wyhr0z3jhy5-Sil-1.3.0/bin/.sil-wrapped
strip is /nix/store/xmpjypwjmp2qi1chs5kr0hacnh161ls4-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/2i9sqpfwm2l3g1m4pl602wyhr0z3jhy5-Sil-1.3.0/bin
patching script interpreter paths in /nix/store/2i9sqpfwm2l3g1m4pl602wyhr0z3jhy5-Sil-1.3.0
checking for references to /build in /nix/store/2i9sqpfwm2l3g1m4pl602wyhr0z3jhy5-Sil-1.3.0...
/nix/store/2i9sqpfwm2l3g1m4pl602wyhr0z3jhy5-Sil-1.3.0

Sorry, I've been on holiday! Updated.


Add Array typehints

This is still completely untested yet.
This draft PR is for code change review and discussion, potentially addressing (or partially addressing at least) #638
Some of it may be able to be trimmed down, made clearer, or better expressed.  For instance, I'm not completely thrilled with ArrayHint, and I think there might be a better way around that with generics, but it would possibly involve some API change, as then VariantArray couldn't use the generic version to export due to needing to be able to implement Export with multiple Hint types.

All good points.  I've tried to address them here.  Still untested.  I'll set aside some time to test them tonight, in 10 hours or so.

I've set up a simple example that looks to be working as expected for me.  So far, it just sets some simple properties of single and double arrays with and without hints.

Since the PR is being inactive, I have taken the liberty to make some changes and squash the commits. Since this is technically a breaking change (changing the Export::Hint type of VariantArray from () to ArrayHint), it is postponed to 0.10.
In the future, we might want to make the "no hint available" hint type a "never" type, so that users will have to use None for those properties. This will make it no longer a breaking change to add hints for those types.

Ah, thanks.  Sorry this one slipped through the cracks.  I meant to clean it up but it fell entirely off my radar.


Fix broken link to downloads page for 2.0.3

Thanks! I made the fix in this commit: https://github.com/dotnet/core/commit/d93d169543032b282cc458c6ec69ee4965f8ea1e


Updated docs: handling liquid variables

I turned crazy trying to find this feature, but looking in the code a few days ago I found that in the plugin constructor it's able to parse {{ }} variables. I added to the docs.

Nice addition, thanks a lot!


Add MDX readme

It would be good to show off the library in the README using MDX à la https://github.com/ocaml-multicore/eio

[x] Simple read example #6
[ ] Reading raw JSON as a string
[ ] Writing a TopoJSON OCaml value to JSON
[ ] API examples (e.g. reading some foreign members)

I've opened separate issues for each of the tasks.


ncmpc: 0.49 -> 0.51

Some maintenance tasks and version bump: https://raw.githubusercontent.com/MusicPlayerDaemon/ncmpc/v0.51/NEWS
Things done

Built on platform(s)

[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[x] Fits CONTRIBUTING.md.

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

needs rebase

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 353958

x86_64-linux

:white_check_mark: 2 packages built:

ncmpc
ncmpc.doc

x86_64-darwin

aarch64-darwin


[Feature request] Customizable hotkeys

Hi.
I have noticed that you added "☑ Basic controls" in your todo list.
The WASD hotkeys are compatible with the QWERTY and the QWERTZ keyboard layouts, but not with AZERTY.
For example, the french keyboards use the AZERTY keyboard layout and the WASD hotkeys are not really easy to use (ZQSD is used instead).
When your game is more complete, could you please consider adding an option to let the user (the player) customize hotkeys?
Thanks in advance.

Good point! I shall incorporate that via bevy_input_mapper at some point.


Error Handling if No Markets

If there are no markets created yet, the front end doesn't know what to do.

Conditional rendering sorts out these issues
I like to implement a loader until the data is pulled and rendered in order to ensure these errors don't happen
If there's no data, render a relevant message

For some reason, the PR as I have created it thus far breaks, "Create.jsx," such that it enters in an invalid date.

@markokovac16 would you happen to be able to look at this?

Awesome, thanks!

Fixed here https://github.com/openpredictionmarkets/socialpredict/commit/2fb05e6209a1ea65d197e97d07ae63c756838597


Scale out of cf-api-server doesn't work beyond 5 replicas in cf-for-k8s

We did a scalability tests on cf-for-k8s v-0.6.0. We started with one replica of cf-apiserver and started pushing buildpack based apps. After certain number of apps we could see cf-apiserver fails with the following error
Waiting for app to start...
Unexpected Response
Response code: 503
CC code:       0
CC error code:
Request ID:    f4f086f1-0ae3-4f07-9f0d-471c6b8028fa::be866d01-d450-4acb-87f1-f504de7e92e0
Description:   {
  "description": "Instances information unavailable: No running instances",
  "error_code": "CF-InstancesUnavailable",
  "code": 220002
}

500s' get piled up then if increase the replicas ,it takes sometime to starting working again. You can correlate with the following graph.

Again after certain apps push succeeded, it failed with the same error again. In the same phase we increased replicas till 5 and able to push till 1600 Application instances  beyond which scaling doesn't help.
Just for the note: we used the default configurations for the capi deployment.

Hi @KesavanKing! Could you look for the associated log line in the cf-api-server logs? It should have a backtrace that we could use to narrow down what the issue is here.

Following are the error log messages which we get from capi:
Unexpected Response
Response code: 503
CC code:       0
CC error code:
Request ID:    d27900c8-4163-4e70-94ba-f1ef67854595::113dba44-8156-4018-87fe-1158206c40f4
Description:   {
  "description": "Instances information unavailable: No running instances",
  "error_code": "CF-InstancesUnavailable",
  "code": 220002
}

{"timestamp":"2020-09-04T03:26:28.841440757Z","message":"all_instances_for_app.error","log_level":"error","source":"cc.diego.instances_reporter","data":{"request_guid":"d27900c8-4163-4e70-94ba-f1ef67854595::ffa09e10-730d-4926-9c8b-e9b2a80a5c0f","error":"No running instances"},"thread_id":47026329335120,"fiber_id":47026327709520,"process_id":1,"file":"/cloud_controller_ng/lib/cloud_controller/diego/reporters/instances_reporter.rb","lineno":42,"method":"rescue in all_instances_for_app"}

Other error logs:
Warning message w.r.t to log-cache:
{"timestamp":"2020-09-04T10:51:58.864750324Z","message":"rescuing GRPC Unavailable error: #<struct Struct::Status code=14, details=\"Socket closed\", metadata={}>","log_level":"warn","source":"cc.logcache.client","data":{"request_guid":"a5a4be3b-4d37-4509-9cc5-6022dc47ad6a::7cf2ec6c-2881-4ea2-9402-f6f9fea86c8d"},"thread_id":47145215417060,"fiber_id":47145211220640,"process_id":1,"file":"/cloud_controller_ng/lib/logcache/client.rb","lineno":57,"method":"rescue in with_request_error_handling"}

Log-cache was consuming high memory reported in this issue. So we thought this is impacting the capi and scaled to two replicas but didn't help out. We saw frequent warning logs.
Failed to resolve update conflicts after retries
From our previous issue #48  , retry logic has been implemented in this (https://github.com/cloudfoundry/cloud_controller_ng/commit/9ea993cc9932146b16ebdb6d17ccf61487e10136) and now we could see failures after three retries.
{"timestamp":"2020-09-04T11:34:52.475991124Z","message":"Failed to resolve update conflicts after 3 retries: ","log_level":"error","source":"kubernetes.update_reapply","data":{"request_guid":"f6616f42-7600-41f4-81a0-a3a1c1c70a89::e5fd47a6-017b-4b71-82ad-9ad8906d8d92"},"thread_id":47196692167440,"fiber_id":47196690470320,"process_id":1,"file":"/cloud_controller_ng/lib/kubernetes/update_reapply_client.rb","lineno":43,"method":"block in retry_on_conflict"}

Broken Pipe Error
{"timestamp":"2020-09-04T10:19:16.239772697Z","message":"app_event_emitter.emit.failed","log_level":"error","source":"cc.runner","data":{"request_guid":"b4f88ce4-9486-475f-bf21-7d1acdd7a51b::3cb2ee2b-0458-4b53-a6b1-8b5df041a640","app_id":"a1205c04-22d5-459e-8ea4-f42bf0c3bf35","message":"Creating build for app with guid a1205c04-22d5-459e-8ea4-f42bf0c3bf35","error":"Broken pipe"},"thread_id":46951993395000,"fiber_id":46951987974220,"process_id":1,"file":"/cloud_controller_ng/lib/app_log_emitter.rb","lineno":12,"method":"rescue in emit"}

We have all the logs in place ,if you need more logs please reach out to us on slack we will share the loki instance

We tried another round of tests to check the max concurrent pushes. During that time we could see nginx container went for frequent restarts and we observed the following error message.
2020/09/14 12:38:48 [info] 6#0: *4675 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /healthz HTTP/1.1", upstream: "http://unix:/data/cloud_controller_ng/cloud_controller.sock:/healthz", host: "localhost:80"

During the scale tests on cf-for-k8s 0.7.0 release , we found one more issue. Most of the cf push was failing with the call to /v3/process/UUID/stats
When we do a cf curl /v3/processes/UUID/stats the response time was shooting beyond 18 seconds. The relevant log which we found is
{"timestamp":"2020-10-02T03:19:16.027511805Z","message":"stats_for_app.error","log_level":"info","source":"cc.diego.instances_reporter","data":{"request_guid":"5b1ea345-eebe-4aca-9c06-a99e7391ccb7::2515f881-0f2a-46df-8dec-388501673725","error":"No running instances"},"thread_id":47248886568360,"fiber_id":70325610875860,"process_id":1,"file":"/workspace/lib/cloud_controller/diego/reporters/instances_stats_reporter.rb","lineno":61,"method":"rescue in stats_for_app"}

@KesavanKing What were the results of your max concurrent push testing? What was the max you were able to achieve? We are planning to run our own scale tests to observe the max concurrent pushes, but it would be good to see if we are able to reproduce what you're seeing in your tests.

Hi @piyalibanerjee ,
We have tried varying from 10 to 40 concurrent pushes.  If we go beyond 20 concurrent pushes , we see lot of failures with unmarshalling error .
Error unmarshalling the following into a cloud controller error: no healthy upstream

When we go beyond ~600 apps, 20 concurrent pushes didn't sustain. So we stick with 10 concurrent pushes on high loads.
In our recent scale tests for release 1.0.0 we kept 20 concurrent pushes and it behaved well.
May be we will do dedicated max-concurrent push tests for latest release and let you know the more granular details of it.
And worth noting it here, during  our last tests for max-concurrent push , we found this #70  latency issue.

@KesavanKing We just concluded our own testing for concurrent push and saw a similar result. Beyond 20 concurrent pushes the cf-api-server will become unhealthy and then requests to it will result in a "no healthy upstream" response with a 503 status code. Scaling out your cf-api-server should allow you to increase the number of concurrent pushes. We expect cf-for-k8s should be able to handle ~20 concurrent pushes per cf-api-server instance.
Here are a few questions that will help us to better understand and address this issue:
In the original description of this issue you mention that scaling the cf-api-server beyond 5 instances did not appear to help.

What errors did you observe when you had more than 5 cf-api-servers?
What operations were you attempting to do at the time?
If you were pushing apps concurrently, how many concurrent pushes were you attempting?

Hi @matt-royal ,
Thanks for the confirmation on the concurrent pushes.
Beyond 5 replicas, the whole push itself is not consistent. We try to scale out ,scale up the CAPI instances and  we saw different failovers. We have added all the error log messages which we observed during the tests  in the above comments.

Referring all the error logs here too.
CF-StatesUnavailable
nginx container restart
 call fails to v3/processes/UUID/stats

We were performing concurrent pushes operations. And a separate script which push a simple app --> start the app --> Check route availability--> Delete the app.

In recent 1.0.0 scale tests we kept 20 concurrent pushes.

@KesavanKing Thank you for that additional information. It sounds as though we should be able to reproduce the problem you're seeing with the following steps:

Scale up cf-api-server to 6 instances
Run a script to do 20 concurrent app pushes
Observe errors and logs for failed push operations for step 2

Does that sound right?

Yes perfect.

@KesavanKing We weren't able to reproduce this issue. Here's what we did:

Provision a GKE cluster with 20 nodes
Deploy the standard cf-for-k8s to the cluster, then scale up the cf-api-server to 6 replicas
Run 20 parallel cf push commands (using the dora app in cf-acceptance-tests) until we had a total of 60 apps on the platform.

One of the pushes failed due to a bad response from eirini, but that was the only error we saw.

Hi @matt-royal ,

Again after certain apps push succeeded, it failed with the same error again. In the same phase we increased replicas till 5 and able to push till 1600 Application instances beyond which scaling doesn't help.

As stated in our first comment, you need to push more than 1600 applications.

FYI , in the latest scale tests on cf-for-k8s-1.1.0 also faced the same issue.
https://github.com/perf-cfk8s/docs/wiki/cf-for-k8s-1.1.0

Given the conversation around converging on a shared CF on K8s vision, we won’t be focused on scaling the current cf for k8s and are going to close the issue.
We’d recommend either commenting on the document to discuss scaling needs or attending the Cloud Foundry for Kubernetes SIG meeting on the calendar here: https://www.cloudfoundry.org/community-calendar/


Support #if SNIPPET in snippets

It's closer to C# syntax, can be used to verify that snippets still build after replacement and I can type it without having to consult the doc.

If we decide to do this I'll update all existing snippets and remove the commend syntax.

@tg-msft once opened this issue => https://github.com/Azure/azure-sdk-for-net/issues/8539
1y 1/2 later it is getting done!!

Fixes: https://github.com/Azure/azure-sdk-for-net/issues/8539

If we decide to do this I'll update all existing snippets and remove the commend syntax.

Maybe not, there are a LOT of them. I might ask service owners to clean up their samples.

Maybe not, there are a LOT of them. I might ask service owners to clean up their samples.

Feel free to create issues per library and we can track the progress in the Eng Excellence epic.

Will refactoring work in the #if SNIPPET branch?
No, unfortunately, Roslyn treats the text in disabled branches as absent from the syntax/semantic tree.
Should we file a work item to schedule a weekly build with -d SNIPPET to make sure all the code that doesn't run still compiles?
Will do.

Filed: https://github.com/Azure/azure-sdk-for-net/issues/20431 https://github.com/Azure/azure-sdk-for-net/issues/20432


Sim800C Reset Pin

Hi Majerle,
I'm using Sim800C. It hasn't got a reset pin. in gsm.c i added defines below. fyi.
#if defined(GSM_RESET_PIN)
/* Try with hardware reset */
if (gsm.ll.reset_fn != NULL && gsm.ll.reset_fn(1)) {
gsm_delay(2);
gsm.ll.reset_fn(0);
gsm_delay(500);
}
#endif
        /* Send manual AT command */
        AT_PORT_SEND_BEGIN_AT();

I don't catch why did you do it this way?
If you do not have reset pin, you can still reset it with AT command that is implemented in the lib.

Thanks


Lifted the validation API

Based on a comment of https://github.com/apple/swift-package-manager/pull/1536 elevated the validate API to the init() level.

@swift-ci please smoke test

@swift-ci please smoke test


Update broken link in FAQ

The CF conventions link in the FAQ is broken. This updates it to the standard location at http://cfconventions.org, which should be kept up to date.

Thanks!


No need to translate at Math area

Math expression Ai, j∈R doesn't need to be translate to Japanese punctuation.

Merged #188.


Simplified footer and made its background orange

Implements #542  with a new SCSS component, as well as the introduction of colors from the Jupyter brand guide.
Along the way, it fixes #531 by deleting the social links. They are so buried on the page I don't see a need to try to redesign them. We can always work the social media back into the page in the future as an enhancement. For now, I say let's close the bug.
Before:

After:

Here's what the brand guide has to say about the orange:

Jupyter Orange is the primary brand color. It should never be used in tints or shades. On any Jupyter collateral that isn’t greyscale, this orange should be present.

My take is we should hoist the flag and be loud and proud. Orange is the anthem.


is it supported to set key code of round bracket ?

seems config syntax doesn't support raw key code of (
leftshift = overload(shift, ()

right now, I used shift combo key
leftshift = overload(shift, S-9)

That’s because keyd deals with keys and not symbols. There is unicode support, but you have to set it up as explained in the documentation. Your second approach is the way to go about it in my opinion.


Update neo4j page

After successful update to new version with Factory design pattern update example how to use this library.
https://neo4j.com/developer/php/

https://github.com/neo4j-documentation/developer-guides/compare/publish...stefanak-michal:patch-1

https://github.com/neo4j-documentation/developer-guides/pull/199


Add lesson and task storage tests

Codecov Report

Merging #170 (d42c95d) into master (93e1af6) will increase coverage by 8.76%.
The diff coverage is 80.00%.

@@             Coverage Diff              @@
##             master     #170      +/-   ##
============================================
+ Coverage     36.55%   45.31%   +8.76%
- Complexity      525      633     +108
============================================
  Files           155      155
  Lines          3173     3173
  Branches        388      388
============================================
+ Hits           1160     1438     +278
+ Misses         1956     1640     -316
- Partials         57       95      +38

Impacted Files
Coverage Δ

...ava/jarvis/storage/JsonSerializableLessonBook.java
72.72% <0.00%> (+45.45%)
:arrow_up:

.../jarvis/model/exceptions/LessonClashException.java
100.00% <100.00%> (+100.00%)
:arrow_up:

...ain/java/jarvis/storage/JsonLessonBookStorage.java
86.95% <100.00%> (+47.82%)
:arrow_up:

src/main/java/jarvis/model/Studio.java
70.27% <0.00%> (+8.10%)
:arrow_up:

src/main/java/jarvis/model/Consult.java
75.00% <0.00%> (+10.00%)
:arrow_up:

src/main/java/jarvis/model/MasteryCheck.java
75.00% <0.00%> (+10.00%)
:arrow_up:

src/main/java/jarvis/model/LessonAttendance.java
55.35% <0.00%> (+12.50%)
:arrow_up:

src/main/java/jarvis/model/LessonNotes.java
74.39% <0.00%> (+13.41%)
:arrow_up:

...rc/main/java/jarvis/model/StudioParticipation.java
65.90% <0.00%> (+15.90%)
:arrow_up:

src/main/java/jarvis/model/LessonBook.java
59.37% <0.00%> (+18.75%)
:arrow_up:

... and 18 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Experiment

I want to merge changes back to master.

Ok, I agree

another comment

yet one more


Given the same link to two people find themselves in two different rooms

Occasionally it happens that two people with the same eyeson call link do not see each other in call, as if they are in two different rooms.
What could be the problem that given the same link people do not see each other during the video call? On our side it turns out to be ok, can you give us a technical reason to investigate? Thank you very much

As you join participants of the same meeting, ensure to use a unique identifier id and they are guaranteed to be in the same video conference.

[...] given the same link [...]

I guess you're talking about the guest link that can be shared during an active meeting by the participants w/o further interaction with the eyeson API. Here as well you have to ensure the participants that share the guest-link are in the same meeting, the most straightforward way to do so is to use an unique identifier.
Let me know if you have any further questions!


Deleting items in aws sdk v2

For better environment configuration we could add reference config with endpoint, credentials (maybe somebody wants to test it not locally
Plus, socker compose with dynamo image. I didn’t find it and was needed to start it by myself. It could be also useful

I saw a SBT plugin for launching local dynamo, sorry, but why we can't just have a docker compose instead? we could choose between docker images and better configure file instead of SBT ones

I'm not necessarily opposed to the idea, as improving the testing environment has been on our mind for quite some time. Using docker for integration tests seems like a reasonable idea and I'm open to improving scanamo-testkit to help developers poke at dynamo either with or without scanamo.

FYI, you can start Dynamo in-process.  Here is the core code:
    val port = 8042
    val file = new File("/some/path/to/where/sqllite/shared/libraries/are)
    SQLite.setLibraryPath(file.getAbsolutePath)

    // start server
    val localArgs = Array("-inMemory", "-port", s"$port")
    server = ServerRunner.createServerFromCommandLineArgs(localArgs)
    server.start()

We have a test fixture that looks like:
  def withDynamoLocal[T](config: DynamoConfig, port: Int = defaultPort)(func: Dynamo => T): T = {

    [code above]
    server.start()

    try {
      func(server.dynamo)
    }
    finally {
      try {
        server.stop()
      } catch {
        case t: Throwable =>
          logger.error("Error shutting down DynamoDb Local", t)
      }
    }
  }

We can also update the SBT test run task to automatically start and stop DynamoDB in interactive mode. This seems like the one with less friction.


Rake Task Wish #1 - download external images to local objects folder

Rake task that goes and grabs all the external images in a collection and downloads them to the Objects folder

From CONTENTdm or using some method to configure the API
or just using what ever links the user produces in a CSV?
Does it rename the files via objectid or something?

I agree with @dcnb that serving files locally has several advantages. The most basic version would probably download the files and replace the external links with local ones. The information about the previous location is then lost. Is this what you had in mind?

@maehr you might want to check our recent Rake tasks in rake-utilities-for-digital. It is pretty specific to our usecase right now, but the task migrate_contentdm we used to download files out of our CONTENTdm repository to prep for our static version. It would be a bit similar to your idea of a Omeka downloader.

p.s. @dcnb original request is probably best using something like download_by_csv task


Scss doesn't compile, how to enable?

<style lang="scss">

</style>

throws errors as there's no preprocessor for scss and doesn't seem it can be configured.
How to enable again?

We've created a PR to support this, in conjunction with this package https://atmospherejs.com/seamink/vue3-sass
Meanwhile replace vuejs:vue3 with seamink:vue3 - see details here https://atmospherejs.com/seamink/vue3


Logging by url route

What steps will reproduce the problem?
Try to create logging logic of the web-application based on url hardcoded routes or based on regex. Let's say I have /admin (would log everything within backend side) or /admin/bank/* (would log everything within bank controller)  route and I would like to get all _GET, _POST requests happening in it.
What is the expected result?
I would like to be able to set up this kind of structure:
'log' => [
    'targets' => [
        [
            'class' => 'yii\log\FileTarget',
            // 'categories' => ['backend'],
            'urlMatch' => ['/admin/*'], // <---
            'logVars' => ['_GET', '_POST'],
            'logFile' =><EMAIL_ADDRESS>        ],
    ],
],

So that covers all of the requests on the admin/*.

With categories, I will need to go to each controller or model and place this category to get the loggin information, which is not very comfortable.

If there is anything like this already, please provide a link, this will be useful.
Additional info

Q
A

Yii version
2.0.11

PHP version
5.5.9

Operating system
Ubuntu 14.04

Advanced app or basic
Advanced

It's a little useful, Should we add it?

yii\log\Target::$enabled could support closures - then you could filter logs by anything, for example all activity of users with specific role.

I don't think it's a particularly good idea. If the application is structured properly, a set of classes is typically used in multiple URLs so it's better to stick to categories. If you still need that, @rob006 provided a solution.

@samdark This is not a solution - right now yii\log\Target::$enabled does not support closures, so you can't use it.

OK. Adding closures makes sense.

@cebe could you briefly give an example of how to use this new addition?

@bologer define log targets for everything you need to be logged and configure the 'enabled' property by checking the current request for whatever you need, so it only logs things when the condition is true.

@cebe can be described in docs - http://www.yiiframework.com/doc-2.0/guide-runtime-logging.html ?

not sure, this is a very specific use case. Added an example to setEnabled: 9d854c0


Improve scaling of to_pandas

There are a few issues with to_pandas poor scaling:

we get partitions serially, much like in #2813, which is again a problem for Dask (but could also be a problem for Ray in multi-machine setup, where it would pull in data from other nodes serially instead of pulling them all at once)
we reconstruct the dataframe by repeatedly calling pandas.concat() which in turn does a lot of memory copying due to how its internal structure is managed.

I wasn't able to find out a good sequence of incantations for Pandas to not copy blocks around during concatenation, so I believe that to improve performance we have to manually construct underlying Pandas block structure into a set of pre-allocated blocks (as we're solving a much simpler task than regular pandas.concat() - we know that we've split the dataframe perfectly when distributing, so there should not be any conflicts in column names or indices).

I wasn't able to find out a good sequence of incantations for Pandas to not copy blocks around during concatenation

Can you give an example of what you're trying to do?  This may be fixed in newer pandas:
arr = np.random.randn(4, 2)
arr2 = np.random.randn(4, 3)
df = pd.DataFrame(arr)
df2 = pd.DataFrame(arr2)

res = pd.concat([df, df2], axis=1)
>>> res._mgr.nblocks
2


Fatal error: Unexpectedly found nil while unwrapping an Optional value

Flutter add to ios project.
generate contacts_service.framework
when I run IOS the error happened as below. Please help to check.
2020-07-24 14:32:45.860038+0800 iosaar[13535:8826645] [VERBOSE-1:callback_cache.cc(132)] Could not parse callback cache, aborting restore
Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Users/limi/Downloads/flutter/.pub-cache/hosted/pub.flutter-io.cn/contacts_service-0.4.6/ios/Classes/SwiftContactsServicePlugin.swift, line 16
2020-07-24 14:32:45.861449+0800 iosaar[13535:8826645] Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Users/limi/Downloads/flutter/.pub-cache/hosted/pub.flutter-io.cn/contacts_service-0.4.6/ios/Classes/SwiftContactsServicePlugin.swift, line 16
(lldb)

Facing this same issue, any update on this??


Bundle cache

Actions CI with Ruby is far slower than other CI products because it downloads and installs gems every time. For a tiny Rails site this adds about 3 minutes to the runtime, big sites I imagine would be far worse.
Is there a way to do what other CI tools do and cache the bundle folder so that on subsequent runs only updated / new gems are installed?
For example CodeShip says they "automatically configures bundler to use the $HOME/cache/bundler directory, which we save between builds to optimize build performance". I assume they set a default bundler config:
https://bundler.io/v1.1/man/bundle-config.1.html
And then any user supplied bundle install command will use that default config including the cache.
https://bundler.io/bundle_install.html
It looks like --path might be what does it.

Right now we don't have this type of caching, but it's definitely on the feature backlog short list. We're tracking this in https://github.com/actions/toolkit/issues/47, does the feature discussed there look like it meets your needs?
If so, can we close here and track in that issue?

Thanks for that, base level caching does seem to be a prerequisite. That issue seems to be asking more for user defined "workspaces" but we'll see how it evolves.
I think this issue should stay open as some work would need to be done here to build on top of the low level caching. You could argue the user should set up a bundle cache themselves, but you could argue they should set up Ruby themselves too. It would be lovely if when you bundle install via the setup-ruby action it's automatically configured to be cached and fast. People coming from other CIs will expect it, and those who don't might not think to do it themselves.
Perhaps add a "blocked" tag or similar until toolkit has caching? Some work could be done here in the mean time to automatically add a bundler config file pre-populated with best-practice defaults such as --jobs=4 (or however many cores these machines have for faster parallel bundling).

Thanks for the feedback ❤ its helpful and maybe can help shape some of how we approach caching.

I think this issue should stay open as some work would need to be done here to build on top of the low level caching. You could argue the user should set up a bundle cache themselves, but you could argue they should set up Ruby themselves too.

I'm not 100% convinced that it makes sense for this action to do that job, but also not 100% convinced that it shouldn't be this action. Lets definitely keep open and readdress once caching is implemented.

Some work could be done here in the mean time to automatically add a bundler config file pre-populated with best-practice defaults such as --jobs=4

I'm interested, but not convinced we should do this. My instinct is to just follow the Ruby defaults (which in theory should be setting best practices) - curious as to why you think we should create our own here

We found where Bundler caches things and how to make the new actions/cache work with that. The default bundle cache lives in ~/.bundle so just caching that folder should allow bundler to detect and reuse it. Or you can move it elsewhere with bundler's --path flag.
Below is our setup for Ruby, we needed to specify a Ruby version so couldn't use setup-ruby but the cache bit should be translatable.
linters:
    name: Linters
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1
      - uses: actions/cache@preview
        id: ruby-cache
        with:
          path: ~/local/rubies
          key: ruby-2.6.5
      - uses: clupprich/ruby-build-action@master
        name: Install of Ruby 2.6.5
        id: ruby
        with:
          ruby-version: 2.6.5
          cache-available: ${{ steps.ruby-cache.outputs.cache-hit == 'true' }}
      - name: Remove ruby-build script
        run: rm -rf ruby-build/script
      - name: Print Ruby version
        run: ${{ steps.ruby.outputs.ruby-path }} --version
      - uses: actions/cache@preview
        id: bundle-cache
        with:
          path: ~/.bundle
          key: ruby-2.6.5
      - name: Build
        run: |
          gem install bundler
          bundle install --jobs 4 --retry 3

RE sensible defaults for Bundler: Bundler isn't automatically optimised for CI or production setups, I imagine partly because it wouldn't work well running on a single threaded Raspberry Pi type setup and they don't want to make any assumptions for you, and partly because it's really old and they don't want to introduce even potentially breaking changes. But on CI which you want to be fast and reliable, I don't see any reason not to have it install in multiple threads, and retry a couple times on network glitches.
So my preference would still be to have smart defaults in this action that optimise for speed and reliability. That'll make the out of box experience much better for the vast majority of people. Then anyone with large legacy setups can override the defaults; because they'll surely know their setup is weird and have the skills to configure for it already.
I guess it depends what GitHub's goals for default Actions are. If it's just to have a very basic bare minimum setup that can be built upon then sure don't do any of this. But I'd question the value of that since you can run custom commands anyway if you want a minimal setup. If the goal is sensible defaults to get people up and running quickly without having to customise a bunch of YAML then absolutely you should set these things.
Also note other CIs like CodeShip automatically cache the .bundle folder and install in parallel with retries. And so does Heroku even for deployment. If anything goes funny you just reset the cache. Since GitHub is one of the biggest Rails companies I certainly expected this action to be the most polished.

@sfcgeorge We have examples of using Ruby in the examples page of the actions/cache here
If you think this example is insufficient, or want to add another example, feel free to open a PR

I guess it depends what GitHub's goals for default Actions are

Right now, the cache action is meant to allow enough explicit configuration to enable caching for any workflow, without making assumptions of the repo's workflows or contents. The downside of this is that more configuration is required for most workflows compared to other CI providers that just enable caching by default. You can see more discussion on this issue https://github.com/actions/cache/issues/94.
Are you having issues using the cache action specifically with the workflow you provided?
I'd also recommend updating to v1 of the cache action for better performance, we've made a lot of improvements since preview

I've added further comments https://github.com/actions/cache/issues/94#issuecomment-571690134
I do have caching working, my issue is that it's not on by default when Bundler locally caches by default. Why should the default be different, and worse, in my fancy cloud CI?

Closing in favor of the cache action.  I don't think there's any action for the setup-ruby action here.  Correct me if I'm wrong.
@joshmgross - perhaps a link in this readme over to the cache example so it's discoverable?


[AutoPR securityinsights/resource-manager] Adding AWS CloudTrail to swagger

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6122

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/5722


Retire EOL Python 3.4

Python 3.4 is EOL.

Python 3.4 has now reached its end-of-life and has been retired. No more releases will be made.
https://www.python.org/dev/peps/pep-0429/

Also, the async/await keywords are nicer to work with in 3.5+ (used by the aiohttp client).
https://www.python.org/dev/peps/pep-0478/
https://www.python.org/dev/peps/pep-0492/
When can we deprecate / remove support for python 3.4?

Yes, PR is welcome I would say :smile:

I suppose we can EOL anything around 2.7 as well
It goes out with the end of the year.
@hjacobs I can do the PR if you tell me how to do that exactly ;-)
Will dropping any references (i.e. setup.py, tox) sufficient?

From what I can tell, we are talking about sth like that.
I noticed travis failing a lot because Flask (dev envs) does not work with Py34.
I will drop PR, maybe even today.


Apache Request Headers Fix

Included a file into config.php referencing an Apache Request Headers replacement function, to rectify newer versions of PHP not supporting the apache_request_headers function, then causing a server error.

Thanks @adampankow. I somehow have missed this for a good portion of this year. I don't give this repo much attention anymore as I don't have any SolusVM based VPS's any longer.


SelectedTracks

Bug
The latest changes to the player are not compatible with the previous API.
There is no method in Video.tsx for selecting video tracks.
In methods for selecting audio and text tracks, the fields of an selectedTrack now depend on its type (value/index). Changing audo track causes the sound to drop out.
There are no changes at Documentation related to selectedTracks too.

@gizomo Thank you for the report.
@KrzysztofMoch can you have a look please ?
I confirm : selectedVideoTrack is missing in Video.tsx
Not sure about the point about selectedAudioTracks, do you have the issue on android ios or both ?

Video.tsx contains this code where object can have selectedAudioType and value/index:
const _selectedAudioTrack = useMemo(() => {
  if (!selectedAudioTrack) {
    return;
  }
  if (typeof selectedAudioTrack?.value === 'number') {
    return {
      **selectedAudioType**: selectedAudioTrack?.type,
      **index**: selectedAudioTrack?.value,
    };
  }
  return {
    **selectedAudioType**: selectedAudioTrack?.type,
    **value**: selectedAudioTrack?.value,
  };
}, [selectedAudioTrack]);

But code for android Exoplayer waits only type and value
private static final String PROP_SELECTED_AUDIO_TRACK = "selectedAudioTrack";
private static final String PROP_SELECTED_AUDIO_TRACK_TYPE = "**type**";
private static final String PROP_SELECTED_AUDIO_TRACK_VALUE = "**value**";

The same goes for selectedTextTrack
private static final String PROP_SELECTED_TEXT_TRACK = "selectedTextTrack";
private static final String PROP_SELECTED_TEXT_TRACK_TYPE = "**type**";
private static final String PROP_SELECTED_TEXT_TRACK_VALUE = "**value**";

As long as selectedAudioTrack is set to undefined, sound works. But as soon as you transfer any object to this prop, sound drop out.

For IOS SelectedTrackCriteria also waits only type and value

Okay, @gizomo thanks for investigation 🙏
@freeboub looks like we need to update JS or Native side - lets discuss
I will mark this as critical for release

What was wrong with the previous implementation?
Why not always set an object with type and value at _selectedAudioTrack and _selectedTextTrack as it was before?

@gizomo you right, i have made mistake while adding types - created PR #3288 with fix.
Cloud you test it ? Thanks for your help 🙌

Sorry, I already merge the fix, I was looking good on my side.
@gizomo your feedback is anyway welcome !
I close the ticket, will be available in 6.0.0-alpha.9


remove the rename link

what did you do to get this error message? that "name" is from the translation json file. Did you try to switch the language?

There is an issue with translation on master branch. Issue #1325  created


[INTEGRATION][dbt] fail execution if OPENLINEAGE_URL is unset

Currently, dbt-ol will run even if OPENLINEAGE_URL is unset. This causes nomal dbt execution, after which user sees that events weren't emitted.
We should assume that variables/config should be set and valid - and fail the run if they aren't. After all, if someone wouldn't need lineage events, they wouldn't use our wrapper.
When https://github.com/OpenLineage/OpenLineage/issues/287 is done, we should use emitting dbt parent run as way to check if URL is valid and reachable.
This will require change with introduction of client Backend or Transport - we should check if any transport is configured correctly, instead of just simple http one.
Signed-off-by: Maciej Obuchowski<EMAIL_ADDRESS>

Codecov Report

Merging #286 (627bfa8) into main (cece24c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #286   +/-   ##
=======================================
  Coverage   87.69%   87.69%
=======================================
  Files          31       31
  Lines        1707     1707
=======================================
  Hits         1497     1497
  Misses        210      210

Continue to review full report at Codecov.

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


Texture selection

When using kappa near zero or negative, the texture on the manifold looks awful.
I'd like it to be possible to select between textures that are fit to a certain range of kappa or upload the texture for the manifold.

Fixed in 94645ee04fea4b6d7911844d23175249c38916a0


Metamodel: Nothing in union type

value t = type([1, "2", true]);
print(t.typeArgumentList[0]);
// prints Nothing|ceylon.language::true|ceylon.language::String|ceylon.language::Integer

Nothing shouldn't be in the union type, and even if it were supposed to be there it should be fully qualified.

More and more the TypeDescriptor looks like a shadow version of the typechecker's Type, with it's duplicate elimination for unions, etc. I now filter out Nothing when forming a union.


SQS Lambda snippets without batch item handling

Issue #, if available:
Description of changes:
Adding basic code snippets for SQS lambda handlers for .NET, Typescript and Javascript without batch item handling
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for the contribution - this will be live at serverlessland.com/snippets/integration-sqs-to-lambda shortly.