libxml2: re-enable tests for darwin

Description of changes
Appears the lack of sandbox on most darwin machines allows the tests to accidentally find /usr/lib/libxml2.dylib, which causes problems.
~Only briefly tested.~
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

The tests work for me on Darwin:
running tests
check flags: -j8 -l8 SHELL=/nix/store/rsl77yd5mm22gvlrdqhqdva8n4axb1p8-bootstrap-tools/bin/bash VERBOSE=y check
make  all-recursive
  CC       runtest.o
  CC       testrecurse.o
  CC       testchar.o
  CC       testapi.o
make[1]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
  CC       testdict.o
  CC       runxmlconf.o
Making all in include
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include'
Making all in libxml
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include/libxml'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include/libxml'
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include'
Making all in .
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
make[2]: Nothing to be done for 'all-am'.
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
Making all in doc
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc'
Making all in .
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc'
Making all in devhelp
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/devhelp'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/devhelp'
Making all in examples
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/examples'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/examples'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc'
Making all in example
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/example'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/example'
Making all in fuzz
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/fuzz'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/fuzz'
Making all in xstc
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/xstc'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/xstc'
Making all in python
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make  all-recursive
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
Making all in .
make[4]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
Making all in tests
make[4]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python/tests'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python/tests'
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make[1]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
  CCLD     testchar
  CCLD     runxmlconf
  CCLD     testrecurse
  CCLD     testdict
  CCLD     runtest
  CCLD     testapi
[ -d test   ] || ln -s ./test   .
[ -d result ] || ln -s ./result .
./runtest && \
     ./testrecurse && \
    ASAN_OPTIONS="$ASAN_OPTIONS:detect_leaks=0"  ./testapi && \
     ./testchar && \
     ./testdict && \
     ./runxmlconf
## XML regression tests
## XML regression tests on memory
## XML entity subst regression tests
## XML Namespaces regression tests
## Error cases regression tests
## Error cases regression tests from file descriptor
## Error cases regression tests with entity substitution
## Error cases regression tests (old 1.0)
## Error cases stream regression tests
## Reader regression tests
## Reader entities substitution regression tests
## Reader on memory regression tests
## Walker regression tests
## SAX1 callbacks regression tests
## SAX2 callbacks regression tests
## SAX2 callbacks regression tests with entity substitution
## XML push regression tests
## HTML regression tests
## HTML regression tests from file descriptor
## Push HTML regression tests
## HTML SAX regression tests
## Valid documents regression tests
## Validity checking regression tests
## Streaming validity checking regression tests
## Streaming validity error checking regression tests
## General documents valid regression tests
## XInclude regression tests
## XInclude xmlReader regression tests
## XInclude regression tests stripping include nodes
## XInclude xmlReader regression tests stripping include nodes
## XPath expressions regression tests
## XPath document queries regression tests
## XPointer document queries regression tests
## xml:id regression tests
## URI parsing tests
## URI base composition tests
## Path URI conversion tests
## Schemas regression tests
## Relax-NG regression tests
## Relax-NG streaming regression tests
## Pattern regression tests
## C14N with comments regression tests
## C14N without comments regression tests
## C14N exclusive without comments regression tests
## C14N 1.1 without comments regression tests
## Catalog and Threads regression tests
Total 3349 tests, no errors
## Parsing recursive test cases
## Parsing non-recursive test cases
## Parsing non-recursive huge case
.........
Total 9 tests, no errors
Testing HTMLparser : 32 of 38 functions ...
Testing HTMLtree : 18 of 18 functions ...
Testing SAX2 : 38 of 38 functions ...
Testing c14n : 3 of 4 functions ...
Testing catalog : 27 of 36 functions ...
Testing chvalid : 9 of 9 functions ...
Testing debugXML : 25 of 28 functions ...
Testing dict : 10 of 13 functions ...
Testing encoding : 16 of 19 functions ...
Testing entities : 13 of 17 functions ...
Testing hash : 17 of 25 functions ...
Testing list : 19 of 26 functions ...
Testing nanoftp : 14 of 22 functions ...
Testing nanohttp : 13 of 17 functions ...
Testing parser : 61 of 70 functions ...
Testing parserInternals : 33 of 90 functions ...
Testing pattern : 10 of 15 functions ...
Testing relaxng : 14 of 24 functions ...
Testing schemasInternals : 0 of 2 functions ...
Testing schematron : 1 of 10 functions ...
Testing tree : 142 of 164 functions ...
Testing uri : 10 of 15 functions ...
Testing valid : 50 of 70 functions ...
Testing xinclude : 8 of 10 functions ...
Testing xmlIO : 41 of 51 functions ...
Testing xmlautomata : 3 of 19 functions ...
Testing xmlerror : 7 of 15 functions ...
Testing xmlmodule : 2 of 4 functions ...
Testing xmlreader : 76 of 86 functions ...
Testing xmlregexp : 16 of 30 functions ...
Testing xmlsave : 4 of 10 functions ...
Testing xmlschemas : 16 of 27 functions ...
Testing xmlschemastypes : 26 of 34 functions ...
Testing xmlstring : 26 of 30 functions ...
Testing xmlunicode : 166 of 166 functions ...
Testing xmlwriter : 52 of 80 functions ...
Testing xpath : 32 of 40 functions ...
Testing xpathInternals : 106 of 117 functions ...
Testing xpointer : 17 of 21 functions ...
Total: 1164 functions, 280912 tests, 0 errors
testing char range: 1 2 3 4 done
testing 1 byte char in document: 1 2 3 4 done
testing 2 byte char in document: 1 2 3 4 done
dictionary tests succeeded 20000 strings
xmlconf/xmlconf.xml is missing
  you need to fetch and extract the
  latest XML Conformance Test Suites
  http://www.w3.org/XML/Test/xmlts20080827.tar.gz
  see http://www.w3.org/XML/Test/ for information
Ran 0 tests, no errors
Total 0 tests, no errors
make[1]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make  all-recursive
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
Making all in .
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
Making all in tests
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python/tests'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python/tests'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
cd tests && make tests
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python/tests'
## running Python regression tests
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python/tests'
make[1]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make[1]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/fuzz'
  CC       testFuzzer.o
  CC       fuzz.o
  CC       genSeed.o
cp -r ./static_seed/regexp seed
cp -r ./static_seed/uri seed
  CCLD     testFuzzer
  CCLD     genSeed
./genSeed html '../test/HTML/*'
./genSeed schema '../test/schemas/*.xsd'
./genSeed xml '../test/*' '../test/errors/*.xml' '../test/errors10/*.xml' '../test/namespaces/*' '../test/valid/*.xml' '../test/VC/*' '../test/VCM/*' '../test/XInclude/docs/*' '../test/xmlid/*'
./genSeed xpath '../test/XPath'
## Running fuzzer tests
Successfully tested 951 inputs
make[1]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/fuzz'
make  check-recursive
make[1]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
Making check in include
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include'
Making check in libxml
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include/libxml'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include/libxml'
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include'
make[3]: Nothing to be done for 'check-am'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/include'
Making check in .
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
make  testSchemas testRelax testSAX testHTML testXPath testURI testThreads testC14N testAutomata testRegexp testReader testapi testModule runtest runsuite testchar testdict runxmlconf testrecurse testlimits
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
  CC       testSchemas.o
  CC       testRelax.o
  CC       testSAX.o
  CC       testHTML.o
  CC       testXPath.o
  CC       testURI.o
  CC       testThreads.o
  CC       testC14N.o
  CC       testAutomata.o
make[3]: 'testapi' is up to date.
make[3]: 'runtest' is up to date.
  CC       testRegexp.o
  CC       testReader.o
  CC       testModule.o
make[3]: 'testchar' is up to date.
make[3]: 'testdict' is up to date.
make[3]: 'runxmlconf' is up to date.
make[3]: 'testrecurse' is up to date.
  CC       runsuite.o
  CC       testlimits.o
  CCLD     testSchemas
  CCLD     testRelax
  CCLD     testXPath
  CCLD     testURI
  CCLD     testThreads
  CCLD     testC14N
  CCLD     testAutomata
  CCLD     testRegexp
  CCLD     testReader
  CCLD     testModule
  CCLD     runsuite
  CCLD     testlimits
  CCLD     testSAX
  CCLD     testHTML
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
Making check in doc
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc'
Making check in .
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc'
make[3]: Nothing to be done for 'check-am'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc'
Making check in devhelp
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/devhelp'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/devhelp'
Making check in examples
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/examples'
make  io1 io2 parse1 parse2 parse3 parse4 reader1 reader2 reader3 reader4 testWriter tree1 tree2 xpath1 xpath2
make[4]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/examples'
  CC       io1.o
  CC       io2.o
  CC       parse1.o
  CC       parse2.o
  CC       parse3.o
  CC       parse4.o
  CC       reader1.o
  CC       reader2.o
  CC       reader3.o
  CC       reader4.o
  CC       testWriter.o
  CC       tree1.o
  CC       tree2.o
  CC       xpath1.o
  CC       xpath2.o
  CCLD     io1
  CCLD     io2
  CCLD     parse1
  CCLD     parse2
  CCLD     parse3
  CCLD     parse4
  CCLD     reader1
  CCLD     reader2
  CCLD     reader3
  CCLD     reader4
  CCLD     testWriter
  CCLD     tree1
  CCLD     tree2
  CCLD     xpath1
  CCLD     xpath2
make[4]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/examples'
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc/examples'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/doc'
Making check in example
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/example'
make  gjobread
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/example'
  CC       gjobread.o
  CCLD     gjobread
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/example'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/example'
Making check in fuzz
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/fuzz'
make  testFuzzer
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/fuzz'
make[3]: 'testFuzzer' is up to date.
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/fuzz'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/fuzz'
Making check in xstc
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/xstc'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/xstc'
Making check in python
make[2]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make  check-recursive
make[3]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
Making check in .
make[4]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make[4]: Nothing to be done for 'check-am'.
make[4]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
Making check in tests
make[4]: Entering directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python/tests'
make[4]: Nothing to be done for 'check'.
make[4]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python/tests'
make[3]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make[2]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14/python'
make[1]: Leaving directory '/private/tmp/nix-build-libxml2-2.9.14.drv-0/libxml2-2.9.14'
checkPhase completed in 50 seconds

But it wants me to continue bulding over 150 more packages, so I Ctrl-C after it switched to building swift-corefoundation-unstable-2018-09-14.


Support for complex collections

Currently only simple collections are supported: n => n.SimpleCollection
Complex nested collections should be supported as well: n => n.Collection.Select(c => c.PropertyName)

I fixed the issue in https://github.com/danielpalme/GenericSearch/commit/f77278465c15377a1778190eb77073a50ed521e6
You can now search in complex collections. Usage:
.AddCustomSearchCriterion<GenericSearch.Data.SomeClass>(s => s.CollectionComplex.Select(c => c.TextNested))


fix: drag and drop mix of files and folders

Resolves #177

🐝 PR preview in Swarm
Preview URL: https://bafybwignzcgf7rmpchtj5ahffn44awi5d3pjbz3d5pocs7fibgopvf3pga.bzz.link
Swarm Hash: cdc88c5fc58f11e69e80e52b79c0591d1ede90e763ebdc297ca8099cfa976f30
Commit Hash: a150c1cfc2161b6ca786abfef78209716eeb1f59
Commit Message: fix: drag and drop mix of files and folders


Populate cells with user data

This branch adds displaying Steam profile information and profiles' images

I have made changes requested in this review


Snappy Crashing, Windows 2012 R2

Getting this error, just started.  Getting on 5 different servers.  Any thoughts?
[code]
Faulting application name: java.exe, version: 8.0.660.17, time stamp: 0x56147e23
Faulting module name: snappy-1.1.2-fd0acfbe-585c-4d4f-9075-6c4e6cae6ac6-snappyjava.dll, version: <IP_ADDRESS>, time stamp: 0x525f897b
Exception code: 0x40000015
Fault offset: 0x000000000000d391
Faulting process id: 0x5ac8
Faulting application start time: 0x01d13c1c04334c86
Faulting application path: C:\jdk\bin\java.exe
Faulting module path: C:\Windows\Temp\snappy-1.1.2-fd0acfbe-585c-4d4f-9075-6c4e6cae6ac6-snappyjava.dll
Report Id: 71d0ee61-a80f-11e5-80bf-7824af82661f
Faulting package full name:
Faulting package-relative application ID:
[/code]

Can replicate by parsing match #2017888634

Spoke with Spheenki,
Not an issue with Clarity.  Please close.


Windows version?

Is there a way to get this for windows?  Or is it mac only?

It's mac only for now :-)

Ok, that should be clarified on the website, to avoid confusion.

It's not written anywhere on the website that this is Mac only. I've downloaded it TWICE(!!) just to unzip and see mac files :disappointed:


Fix release chart update

refer to individual commits for more context.
gist:

set correct ovs cni image
fix operator name in chart

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.645%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5180

Relevant Lines:
13404

💛  - Coveralls


Let us right-click hop to cc mates

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've
considered.
Additional context
Add any other context or screenshots about the feature request here.

Duplicate of #5121


Change locality string table_of_contents

Source: https://github.com/metanorma/metanorma-ieee/issues/11
Change from:
<localized-string key="table_of_contents" language="en">Table of contents</localized-string>

to
<localized-string key="table_of_contents" language="en">Contents</localized-string>

From IEEE template:

@opoudjis thanks!


Potential fix for failing unit test on #1179

See comment in #1179

Merged, thank you for poking this!!!


Run tests when publishing to nixpkgs

Overview
I forgot to update and run tests on this PR: https://github.com/NixOS/nixpkgs/pull/79230. This adds documentation to remind future maintainers to do a better job.

Checklist

[x] Updated the documentation (code documentation, command help, ...)
[ ] Tested the change (unit or integration tests)
[ ] Amended the changelog in release.nix (see release.nix for instructions)

CI failure is unrelated


Puppeteer in Bitbucket Pipelines timeout

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.2.0
jest-puppeteer version: 2.2.3
jest: 22.4.3
Platform / OS version: Linux, docker: timbru31/node-chrome
URLs (if applicable):
Node.js version: 8.x

What steps will reproduce the problem?
So I'm using jest-puppeteer to run e2e tests in headless chrome. This works fine on my machine. The problem starts when running these tests in Bitbucket Pipelines. It runs the docker image specified above. I've tried that docker image locally and it works as expected.
Pipelines is giving me the following error:
Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.
By trial and error it is because of this line:
await page.waitForSelector('.account-container')
I've found out that await page.evaluate() has the same problem.
I've tried setting the timeout to something much higher, but that didn't change anything.
I've tried with these args:
    args: [
      '--no-sandbox',
      '--disable-setuid-sandbox',
      '-shm-size 1G'
    ]

I want to figure this out but I simply don't know what I can still try here.
Full test case code:
Please include code that reproduces the issue.
  it('should fill in valid credentials, press the login button and navigate to new pages', async () => {
    await page.goto(baseUrl)

    await expect(page).toFill(inputEmail, validEmail)
    await expect(page).toFill(inputPassword, validPassword)
    await expect(page).toClick('.button', { text: 'Log in' })

    await page.waitForSelector('.account-container') // this line freezes
  })

What is the expected result?
No timeout error. Test case should pass.
What happens instead?
Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.

@Christilut I'm experiencing the same thing, I believe. Where is the IP whitelist defined and what did you add to resolve this?


Block edge 4.4.23

4.4.23 needs to be disabled:
2 clusters currently failing (13%),  1 gone ( 7%),and 12 successful (80%), out of 15 who attempted the update over 7d
Currently failing classification:
* Down nodes: 1
* Node pressure: 1
* SDN issue: 1
* Untriaged: 1

4.4.23 can be enabled again:
1 clusters currently failing ( 7%),  0 gone ( 0%),and 13 successful (93%), out of 14 who attempted the update over 7d
Currently failing classification:
* Down nodes: 1
* Node pressure: 1
* SDN issue: 1


Update README and  git settings

Update gitignore: exclude Pods directory
Format README

The project is great! Carry on.

Thanks, buddy.
I really appreciated your help and it must take you some time to do this! But I won't merge this request for some personal reasons. I think it is unnecessary to exclude Pods directory since there is only one library, the Masonry, in there. Anyone who uses this demo will have to do one more step, that is, install pod.
And thank you, really!


Add generation evaluation decorator to provide yield return

from PR #41
sometimes, generation evaluation need to provide evaluation result in progress with token scale(like log_prob etc,)
for more advanced generation.

It looks like 'stream' support.


[release 1.30] upgrade kubernetes version and docs

closes #1398 and #1399

/cc @damemi

/cc @ingvagabund

Let's update https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/descheduler/descheduler-presubmits-master.yaml to deploy k8s 1.30 before merging this. Even though the master HEAD is currently v0.30.0-alpha.3.

@ingvagabund we typically have done that after the release branch is created, see 1.29 PR: https://github.com/kubernetes/test-infra/pull/31497

@ingvagabund https://github.com/kubernetes/test-infra/pull/32633

/test pull-descheduler-test-e2e-k8s-master-1-30

/test pull-descheduler-test-e2e-k8s-master-1-30

/approve
/lgtm


i think that would you like to get me example about conf

docs is to simlpe

The file is here:  https://github.com/niiknow/docker-nginx-image-proxy/blob/master/files/etc/nginx/sites-enabled/server.conf
The demo on the home page should be working now with the new v2, example: http://imageproxy.niiknow.org/rx/50/https://octodex.github.com/images/codercat.jpg


Focus states for buttons

Should we include focus states for buttons and anchors? When tabbing through the Bitters example page the focus states for text anchors are very subtle and the "button anchors" don't have focus indications.
We are currently setting outline to none here: https://github.com/thoughtbot/bitters/blob/master/app/assets/stylesheets/_typography.scss#L61
Should we consider not doing that?

This good to close now, @kylefiedler?


fix: premature close with chunked transfer encoding and for async iterators in Node 12

This PR backports the fix from #1064 to the 2.x.x branch following the comment here.
I had to add some extra babel config to allow using the for await..of syntax in the tests.  The config is only needed for the tests as this syntax is not used in the implementation.

Ok, I hadn't realised quite how far back in time the supported node versions would go, will see if I can fix up some the oldies.

I had to pin a few deps that have dropped compatibility with old node versions without releasing majors and I've added notes where this PR diverges from the fix in #1064 for the sake of compatibility with old node versions but this should be good for review.

Hey @xxczaki @bitinn @TimothyGu! Can one of you please have a look an release this? My team is facing huge issues that should be fixed with this patch backported to 2.x.x. Should only take a few minutes of your time!

bumping, @jimmywarting @achingbrain can this be merged?

@jimmywarting I'm good with merging this into 2.x, but I feel it's significant enough to warrant a minor version bump to 2.7.0. I'll leave it to you to merge so you can make the determination on versioning.

Hey :)
Is there a way I could use this even though it's not merged .. or can we just merge it? 🔥

friendly bump :)

Thanks so much for merging this. I don't think it's been released yet, is there any chance of getting it out of the door?

@jimmywarting we don't have semantic-release setup in the 2.x branch, we need to release manually, or setup semantic-release in there as well. Let me know if you'd like help with the latter

@gr2m if you could set it up, then it would be great

@gr2m @jimmywarting just a gentle reminder this still hasn't made it into a release.  Please could the 2.x.x branch have a release with this in it?

@gr2m @jimmywarting please, please, please can this be released?

hey sorry I'll look into it

there y'all go. Can you confirm it looks good?

@node-fetch/core I've setup automated releases in the 2.x branch, so backporting should be easy now, just send PRs against the 2.x branch and use the commit conventions

Thankyouthankyouthankyouthankyou!


Create raster mask as boolean (geovector/create_mask); display/save boolean as np.int8 for black/white display (georaster)

Currently, the Vector.create_mask() outputs np.int8 rasterized with 0/255 which is non-intuitive for mask manipulation. This functionality could be kept only for displaying in black/white in georaster.show() - and possibly saving to disk.

I agree on that this is not optimal. It's especially weird right now when you try to use the mask without converting to a boolean:
In [1]: import geoutils as gu

In [2]: dem = gu.georaster.Raster("examples/Longyearbyen/data/DEM_2009_ref.tif")

In [3]: outlines = gu.geovector.Vector("examples/Longyearbyen/data/glacier_mask/CryoClim_GAO_SJ_1990.shp")

In [4]: mask = outlines.create_mask(dem)

In [5]: masked_dem = dem.data[mask]
---------------------------------------------------------------------------
MemoryError                               Traceback (most recent call last)
<ipython-input-6-8acae57b5a94> in <module>
----> 1 masked_dem = dem.data[mask]

~/.local/share/conda/xdem/lib/python3.8/site-packages/numpy/ma/core.py in __getitem__(self, indx)
   3217         # mask of being reshaped if it hasn't been set up properly yet
   3218         # So it's easier to stick to the current version
-> 3219         dout = self.data[indx]
   3220         _mask = self._mask
   3221

MemoryError: Unable to allocate 6.26 TiB for an array with shape (985, 1332, 985, 1332) and data type float32


Use closure actions for 'onDragStart&onDragStop` drag actions

We can refactor this to use closure actions instead of action bubbling
https://github.com/heroku/ember-sortable#drag-actions

I’m inclined to leave the code and example as-is. My reasoning is that sendAction works with  onDragStart="myAction", onDragStart=(action "myAction"), and onDragStart=(action myAction) so we continue to offer full backwards-compatibility. Though I personally prefer onDragStart=(action myAction), onDragStart=(action "myAction") aligns better with Ember’s guides so I think we should stick with that.
Re-open if you disagree 😅


WIP - Add metrics hook

Summary | Résumé
Initial work to add metrics hooks - will fill out more detail once we have more mapped out and know which direction we're moving in.
This is the UI piece which will connect to https://github.com/cds-snc/covid-alert-app/pull/1371

I refactored the metrics.tsx file a bit - feel free to revert if don't like my changes!


Support pulling CA certs from default OS locations

We currently use /var/lib/rancher/etc/ssl/ca.crt file in order to get private / self signed CA certficates into the trusted OS store. This file is a non-standard location for the base operating system.
This was done by design to avoid having the privileged agent container from stepping outside of its boundaries. It is also done to isolate any differences between the base OS and the containers Ubuntu image.
It has been brought up that it might be worth revisiting this design to ease operational overhead.

+1

This was tied to v1.6 and the way TLS was handled. Since v1.6 is not gaining any additional feature enhancements at this time. I'm going to close this issue.


New version: TerraformLinters.tflint version 0.52.0

Pull request has been created with komac v2.3.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree


Fediverse => Bluesky: auto-generate embeds (with thumbnail images) for links?

I do not know if this is a general problem between platforms or if it is strictly an issue between Mastodon -> Bluesky, but whenever I post an article (or other external link) on Mastodon the thumbnail doesn't show up on Bluesky. You can see the link and click on it, but no thumbnail.
Would be great if this could be fixed.

This happens because in ActivityPub (Mastodon) link previews are generated by the receiver, but in Bluesky they are stored by the sender as part of the post itself. Bridgy Fed already handles this for web posts it seems (#1192).
Relevant Bluesky lexicons:

app.bsky.feed.post (.embed)
app.bsky.embed.external

Ok, my instance is Mastodon.nu if that is of any importance.

It's mainly the software and version that matters, as long as posts go through at all.
(The current Mastodon v4.3.1, in this case.)

This is an interesting one! @Tamschi is broadly right: Bluesky/ATProto link previews (including thumbnail images) are explicit metadata in post objects. ActivityStreams 2 post objects can have similar link preview metadata, eg in the attachment field, but fediverse clients and servers like Mastodon often generate them from the first link in the post instead. When they get a post with an attachment, they halfway honor it and render it similarly, but usually without an image, so it looks like a second class citizen.
Take https://indieweb.social/users/snarfed/statuses/112582713947140513 as an example. I authored it inside Mastodon, and included a single URL in the text. Mastodon renders a link preview embed for that URL, in both the source instance and remote instances, but it federates it as an AS2 Note with no attachment value. The user-visible link preview is handled entirely outside AP.

I haven't done a comprehensive survey, but afaik at least some other popular fediverse servers, if not most, do the same thing.
So, the common case is that fediverse link previews are a non-standard heuristic, and I'm reluctant to bake that kind of thing into Bridgy Fed. I get that it might still be the right thing to do for UX though! So I'm torn.
(I do indeed do this for web => Bluesky, but that situation is very different, since the source post is a single specific web page.)

More background on how fediverse servers, particularly Mastodon, prefer to generate their own link previews and don't really want (or trust) them in federated attachments: https://github.com/snarfed/bridgy-fed/issues/958

Any progress on this issue? I think it should be a priority, since many Bluesky users are (understandably) hesitant to click on a shortened URL. See example below.

No progress yet, sorry.
First step would be to decide that we want to apply this non-standard heuristic described above, specifically that if there are link(s) in the text and no explicit preview, we generate one automatically based on the first link. I don't love that, but I guess I'm ok with it.
After that, it's just the implementation work. PRs are welcome!

I can see why you're hesitant/reluctant, but as long as most fediverse clients and servers like Mastodon continue to mostly generate previews from the first link in the post, it sounds like a good fix.
Unfortunately, I'm not a coder myself, but I'm happy to give feedback on design proposals, if that is of any help.

Interestingly, there seems to be ongoing work on Mastodon's end to federate link previews: https://www.theregister.com/2024/05/06/mastodon_delays_fix_ddos/
The discussion on that is here: https://github.com/mastodon/mastodon/issues/23662
If they go ahead with standardising a federated link preview system, even if it's just a cached version without full trust, then that's likely something that Bridgy Fed could translate back and forth between the networks.

Can major platforms like Flipboard be persuaded to do anything different to make it work, or is that the wrong end to tackle the issue?

Good question! I talk with people at Flipboard and many of the other big platforms pretty regularly. There are a number of options here, discussed above, but the conclusion right now is probably just to generate the previews ourselves.

Thanks, just to add. I now see someone has noted that the bridged posts from Flipboard look like a bot and has added to a warning list. Small scale, but could be indicative of how viewers see the posts.

There has been a slight change. More of a text preview now appears on posts from Flipboard, but no image as yet.

Good eye! Yup, I shipped a first pass at this, it works, but doesn't include images yet. Working on those.

Sounds like a plan! Thanks.

I see previews now 👀

Me too, thank you for the fix. It looks so much better now. 🙌

Rolling this back temporarily due to #1575, sorry. It'll be back soon!

also, you'll want to mind the hashtag (induced) links in the bridged posts. I had a post from piaille.fr Masto that had a hashtag first thing, and it displayed on Bsky with the preview of piaille.fr :grin:

Updated and deployed again. Example:

https://indieweb.social/@snarfed/113576299711842461
https://bsky.app/profile/fedi.test.snarfed.org/post/3lca2dpcv4c32

My bluesky account is
https://bsky.app/profile/chaperon.fedibird.com.ap.brid.gy
but these toot is not reflected in blue sky.
https://fedibird.com/web/statuses/113586347590177723
https://fedibird.com/web/statuses/113581312460836009
There are several other posts that have not been reflected in blueSky since the day the link preview feature of this issue was implemented.
It appears to be mainly Twitter and Bluesky links, but there are a few other posts that are not being reflected.
Do you know the cause?

Working great for me, toots with links showing up with previews on Bluesky (my Mastodon account is on the instance Mastodon.nu, btw). Thank you for fixing this, @snarfed !

Just a short addon to this: it works well for short posts that are bridged, but for posts with more than 300 characters, it doesn't. Could this still be fixed?

@EmilJacobs right now, if a post is longer than 300 chars and we have to truncate it, we prioritize the link to the original post.

on some posts, it seems that the image size in the mirrored post is not set as per the original, see e.g.
https://bsky.app/profile/politipet.piaille.fr.ap.brid.gy/post/3lcl3tpopwai2
vs
https://piaille.fr/@politipet/113601175324204315

@popet-master yes! that's https://github.com/snarfed/bridgy-fed/issues/1571

I don't know if it’s ok to add to a closed issue.
This was fixed and working ok, but now it’s erratic and only works sometimes with links from Flipboard as fediverse shared on Bluesky.
If you look at @Ayethatllbright.flipboard.com.ap.brid.gy only three of the last 11 Flipboard posts have had an image preview show.

That's fine, it's regarding this feature after all.
I had a look at https://bsky.app/profile/Ayethatllbright.flipboard.com.ap.brid.gy:
It seems to be consistent regarding the linked domain. I have a hunch that Bridgy Fed is getting bot-filtered by some of them.
@snarfed can likely check this in the logs, but if that is indeed the case, then it's the respective websites that have to allow-list Bridgy Fed or at least serve it a simplified page that still contains the necessary meta data.

Good guess @Tamschi...but these are serving fine for us, looks like the bug here is #1615.


Configuraton Overrides

This container is great but I seem to be having a few issues with configuration.
Setting - V_RISING_SERVER_LIST_ON_EOS=true in my docker_compose.yml still results in ListOnEOS being false in the loaded ServerHostSettings.
If I try to set it in the ServerHostSettings.json that file seems to be recreated with fresh values every time the docker container is started. So if I set it there and start the server it will be turned back to false. Any idea how I can enable the settings?

I am also having this issue, there is a closed ticket about it where someone was able to resolve it on an earlier version but I can't get it to work with this one.

Right now the easiest workaround would be to define V_RISING_SERVER_DEFAULT_HOST_SETTINGS as false, which disables using the default config as a template, which it would then apply customizations to.
I'm working on bringing this project back to life, so it's unfortunately a bit of a work in progress right now, and there have been seemingly undocumented changes to the actual V Rising server, so getting all of those changes working and supporting all kinds of custom configs, as well as properly documenting usage, is something that will take a bit more time.

V_RISING_SERVER_DEFAULT_HOST_SETTINGS

When I set V_RISING_SERVER_DEFAULT_HOST_SETTINGS to false, my manually set ServerHostSettings.json file gets overwritten with default settings when starting the container.

I have done this as well, the settings were overridden .

Okay, I was able to get my settings to persist by commenting out the following commands in start_vrising.sh. I have 3 servers currently down, so I am trying to just get them running. But, I will take a deeper look and see if I can't resolve this with a PR.
`jq '.Name |= (env.V_RISING_SERVER_NAME)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.Description |= (env.V_RISING_SERVER_DESCRIPTION)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.Port |= (env.V_RISING_SERVER_GAME_PORT|tonumber)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.QueryPort |= (env.V_RISING_SERVER_QUERY_PORT|tonumber)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.Address |= (env.V_RISING_SERVER_BIND_IP)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.MaxConnectedUsers |= (env.V_RISING_SERVER_MAX_CONNECTED_USERS|tonumber)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.MaxConnectedAdmins |= (env.V_RISING_SERVER_MAX_CONNECTED_ADMINS|tonumber)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.Password |= (env.V_RISING_SERVER_PASSWORD)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.ListOnMasterServer |= env.V_RISING_SERVER_LIST_ON_MASTER_SERVER|test("true")' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.ListOnSteam |= (env.V_RISING_SERVER_LIST_ON_STEAM|test("true"))' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.ListOnEOS |= (env.V_RISING_SERVER_LIST_ON_EPIC_EOS|test("true"))' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.GameSettingsPreset |= (env.V_RISING_SERVER_GAME_SETTINGS_PRESET)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.SaveName |= (env.V_RISING_SERVER_SAVE_NAME)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.AutoSaveCount |= (env.V_RISING_SERVER_AUTO_SAVE_COUNT|tonumber)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"
jq '.AutoSaveInterval |= (env.V_RISING_SERVER_AUTO_SAVE_INTERVAL|tonumber)' "${V_RISING_SERVER_CONFIG_FILE}" > "/tmp/ServerHostSettings.json.tmp" && cp -f "/tmp/ServerHostSettings.json.tmp" "${V_RISING_SERVER_CONFIG_FILE}"`

Yeah, still no joy for me.

Yeah, still no joy for me.

I first commented out the following lines:

Here is my docker-compose setup:

Note that most of the config is commented out, and it was very trial and error based to get it all working. Plus the RCON config was still being overridden by the start_vrising.sh file, so don't expect to customize that without more modification.
Good luck!

I'll try getting this fixed today and will update here once the new image is published. Once that's done, be sure to use the "latest" tag when pulling the new image, to ensure you get the newest available image.

Thank you! I was thinking about altering the template for server host file and firering up the container to see if it would pull from that next, but I will just wait for the new image :D

Any updates on this? I'm still getting this issue myself, and i've even tried deleting and re-pulling the latest container from dockerhub to see if i had an older container that wasn't fixed yet, but nope. The container still changes V_RISING_SERVER_LIST_ON_EOS=true & V_RISING_SERVER_LIST_ON_STEAM=true back to false when started back up, even with docker-compose.yml set to V_RISING_SERVER_START_MODE: "2" and V_RISING_SERVER_UPDATE_MODE: "0" so steamcmd doesn't grab new files or updates.

To stop the config override I disabled the following via environmental variables
V_RISING_SERVER_DEFAULT_HOST_SETTINGS: false
V_RISING_SERVER_DEFAULT_GAME_SETTINGS: fals
I found this in the startup.sh script

Even with setting those env vars to false, it is still overwriting the settings with the defaults

Even with setting those env vars to false, it is still overwriting the settings with the defaults

Got an example env file? As soon as I applied those above settings, both my config files stopped getting overridden and I've had the server running for weeks now, restarting nightly and never override

it might be related to https://github.com/Didstopia/vrising-server/pull/10, some of the jq statements, especially the bools, didn't work


White Space around QR code

Hello,
First, thank you for this QR code generator :)
Secondly, is there a reason (or a way to remove), the white space around the QR code.  I attached an image, of what I am referring to as you can see there is white space all around the code in the QR code image.  I can do negative margins with css to make it a little better, but it's not the best solution.

Thank you again

Did you ever figure out a way to remove the white space around the QR code?

<ngx-qrcode
  elementType="url"
  [value]="url"
  [margin]="0"
  errorCorrectionLevel="L">
</ngx-qrcode>


Post DT API migration review

Describe the bug
Following move to new DT API (https://github.com/zephyrproject-rtos/zephyr/pull/25009 and cie), a systematic code review is needed around impacted code.
First reason is that a lot of code has been changed using scripts which is a usual source of bugs. Most of the time, lot of files where impacted, which is not easy to review, and hence some bugs have been merged (https://github.com/zephyrproject-rtos/zephyr/blame/master/boards/arm/atsamd21_xpro/pinmux.c#L23 -- fixed by https://github.com/zephyrproject-rtos/zephyr/pull/25252)
Second reason is that peripheral instances Kconfig symbols replacement by DT macros is not transparent in all areas. In a driver compiled under CONFIG_SPI control, CONFIG_SPI_1 is equivalent to DT_HAS_NODE_STATUS_OKAY(DT_NODELABEL(spi1)), but this is not valid in other areas.
Under boards/ or soc/, every piece of code under DT_HAS_NODE_STATUS_OKAY(spi1) is compiled in, whatever the status of CONFIG_SPI. So SPI related pins or clocks are activated unconditionally. Since this is the case for all peripherals (SPI, CAN, I2C, ...) this could potentially lead to, among others:

pin conflicts between peripherals that weren't enabled together until now
clocks being enabled for disabled peripherals
instances that used to be disabled in Kconfig but DT enables them by default, causing conflicts (eg. with shields)

These two cases are typically tricky to detect, and since current code coverage is not sufficient to guarantee all potential bugs introduced will be detected.
So it is safer to systematically review each change and in case of doubt re-introduce a peripheral Kconfig control on newly introduced instance dt macros:
#if DT_HAS_NODE_STATUS_OKAY(DT_NODELABEL(spi1)) && CONFIG_SPI
Expected behavior
No bugs where introduced following move to new DTS API
Impact
Wide spectrum of bugs in v2.3.0
Actions
I propose that each codeowner reviews, in his own area (boards/, soc/, ..) code impacted by new introduced DT macros (DT_HAS_NODE_STATUS_OKAY, DT_NODE_HAS_COMPAT_STATUS, ATMEL_SAM0_DT_SERCOM_CHECK, ..) and take appropriate actions.
In order to make this a task that can be completed in a finite amount of time, I've giving putting here
the various soc maintainers based on CODEOWNERS. I let people tick their area when they consider things are ok (don't hesitate to rework this list if required).
Check boards/ and soc/ for each of the hardware variants below:

[ ] arc/snps_*/                      @vonhust @ruuddw
[ ] nios2/                              @nashif @wentongwu
[x] arm/arm/mps2/                ? (@galak)
[ ] arm/atmel_sam/sam*/     @ioannisg, @nandojve, @fallrisk
[ ] arm/bcm*/                        @sbranden
[x] arm/infineon_xmc/           @parthitce
[ ] arm/nxp*/                         @MaureenHelm
[ ] arm/nordic_nrf/                @ioannisg
[ ] arm/qemu_cortex_a53/    @carlocaione
[ ] arm/st_stm32/                  @erwango
[ ] arm/ti_simplelink/             @bwitherspoon, @vanti, @Mani-Sadhasivam
[ ] arm/xilinx_zynqmp/          @stephanosio
[ ] xtensa/intel_s1000/          @sathishkuttan @dcpleung

Add a dependency to the subsystem Kconfig variable if it was present previously:
#if DT_NODE_UART... && CONFIG_UART

#24745 is related and really should be addressed before release too.  That involves assessing board defconfigs vs devicetree status values.

#24745 is related and really should be addressed before release too. That involves assessing board defconfigs vs devicetree status values.

Thanks @pabigot, this exactly one of the potential impacts. Btw https://github.com/zephyrproject-rtos/zephyr/issues/24509 is another bug related to that.

@erwango arm/infineon_xmc/ can be marked as done. Couldn't tick/edit myself.

For potential pinmux comments please see https://github.com/zephyrproject-rtos/zephyr/issues/24745#issuecomment-620236843 which identifies these boards as potentially using the same pin for multiple peripherals (only the boards are identified here; use the referenced script to see the specific pins and roles)
Conflicts for boards/arm/frdm_k22f/pinmux.c:
Conflicts for boards/arm/mec1501modular_assy6885/pinmux.c:
Conflicts for boards/arm/frdm_k82f/pinmux.c:
Conflicts for boards/arm/atsamr21_xpro/pinmux.c:
Conflicts for boards/arm/frdm_k64f/pinmux.c:
Conflicts for boards/arm/mec15xxevb_assy6853/pinmux.c:
Conflicts for boards/arm/twr_ke18f/pinmux.c:
Conflicts for boards/arm/hexiwear_k64/pinmux.c:
Conflicts for boards/arm/frdm_kw41z/pinmux.c:
Conflicts for boards/arm/hexiwear_kw40z/pinmux.c:
Conflicts for boards/riscv/rv32m1_vega/pinmux.c:

Example of script output:
Conflicts for boards/arm/frdm_k64f/pinmux.c:
	pinmux_pin_set(portb, 10, PORT_PCR_MUX(kPORT_MuxAsGpio));
	pinmux_pin_set(portb, 10, PORT_PCR_MUX(kPORT_PinDisabledOrAnalog));
	pinmux_pin_set(portc, 16, PORT_PCR_MUX(kPORT_MuxAlt3));
	pinmux_pin_set(portc, 16, PORT_PCR_MUX(kPORT_MuxAlt4));
	pinmux_pin_set(portc, 17, PORT_PCR_MUX(kPORT_MuxAlt3));
	pinmux_pin_set(portc, 17, PORT_PCR_MUX(kPORT_MuxAlt4));
	pinmux_pin_set(portc, 17, PORT_PCR_MUX(kPORT_MuxAsGpio));

Pinmux conflicts on STM32 based boards  with updated script in #24745
Conflicts for boards/arm/nucleo_f767zi/pinmux.c:
	{ STM32_PIN_PA7, STM32F7_PINMUX_FUNC_PA7_ETH },
	{ STM32_PIN_PA7, STM32F7_PINMUX_FUNC_PA7_SPI1_MOSI },
Conflicts for boards/arm/nucleo_f746zg/pinmux.c:
	{ STM32_PIN_PA7, STM32F7_PINMUX_FUNC_PA7_ETH },
	{ STM32_PIN_PA7, STM32F7_PINMUX_FUNC_PA7_SPI1_MOSI },
Conflicts for boards/arm/stm32vl_disco/pinmux.c:
	{ STM32_PIN_PB10, STM32F1_PINMUX_FUNC_PB10_I2C2_SCL },
	{ STM32_PIN_PB10, STM32F1_PINMUX_FUNC_PB10_USART3_TX },
	{ STM32_PIN_PB11, STM32F1_PINMUX_FUNC_PB11_I2C2_SDA },
	{ STM32_PIN_PB11, STM32F1_PINMUX_FUNC_PB11_USART3_RX },
Conflicts for boards/arm/nucleo_f756zg/pinmux.c:
	{ STM32_PIN_PA7, STM32F7_PINMUX_FUNC_PA7_ETH },
	{ STM32_PIN_PA7, STM32F7_PINMUX_FUNC_PA7_SPI1_MOSI },

The pinctrl-0 was introduced for Atmel SAM (not SAM0). It allowed us to remove dts_fixup and soc_pinmap files. In this case, problems can happen only with SAM0 variations that have pinmux.c file.
Should this to be applied on all boards///pínmux*.c files to avoid exceptions? I was wondering if there are exceptions, can we identify at review phase the possibles conflicts.

@nandojve Advice is to review all files that have been impacted by the migration. Conflicts could be identified txs to the script provided in #24745.

@erwango I don't think I see anything that needs to change for ti_simplelink, so marking done.

@vonhust and @ruuddw will you take a look for ARC-based platforms please?

@vonhust and @ruuddw will you take a look for ARC-based platforms please?

Checked, no issues (ARC EMSK and other boards have a different type of pinmux called pmodmux, no DT relation currently).

@nashif @MaureenHelm @ioannisg @jhedberg could you please check your respective platforms so we can close this soon?


Fix false positives for Style/AccessorGrouping when accessors have different access modifiers

Closes #8253
This PR:

extracts common functionality for visibility checking into helper module
handles accessor modifiers correctly
handles class << self accessors correctly

Great work!

Thank you for the quick fix :)


The performance of datepicker seems poor

plunkr: http://embed.plnkr.co/zeQzQgF1UKb2G66yoSRI/
Angular: 1.5.5
UIBS: 1.3.3
In my usage, i combine the datepicker and the timepicker. When i just upgrade to UIBS 1.3 form UIBS 0.13, i just find that as i change the timepicker, the corresponding changes of datepicker are slow.
Then i make a test. It turns out whenever i change the ng-model of datepicker, it will reconstruct the whole datepicker which can be concluded from 43 $destroy event.(see the console of the plukr if you change the date)

@e-cloud, we actually strongly recommend NOT using the same model object for both the datepicker and timepicker.
I'm closing this as something that is not going to be very high on our priority list.

In fact, the combination is not the point. It's all about datepicker's performance.
And there is no combination in the demo plunkr.

@e-cloud When changing the date bound to the ng-model, the day calendar needs to be rebuilt to correctly reflect the 'selected' date as it may be in a different month/year.  So what would you suggest?

such as keep the child scopes undestroyed, just update their value or so?
That's what it does in the old version.
But for maintainability, the profit may be minor.

The day calendar is built with nested ng-repeats:
https://github.com/angular-ui/bootstrap/blob/master/template/datepicker/day.html#L14
https://github.com/angular-ui/bootstrap/blob/master/template/datepicker/day.html#L16
Which I assume is destroying the day button scopes when the rows collection changes.


Create a .js file and write hello world

2. go to the src folder, then to student-contribution. create a simple file .js and do it

Good one 😊

Good one 😊


LateInitializationError: Field 'width' has not been initialized.

LateInitializationError: Field 'width' has not been initialized.
It gave me this error when I was trying to use it in my app, specifically in a ThemeData, this is my code:
static final ThemeData theme = ThemeData(

    // blanco puro Color(0xffFFFFFF)
    scaffoldBackgroundColor: blanco,
    // negro Color(0xff000000)
    shadowColor: negro,

    colorScheme: ColorScheme(
      // color1 el del igual Color(0xff8500C7)
      primary: color1,
      // color2 el del title del appbar y el boton menu Color(0xff7D00BA)
      primaryVariant: color2,
      // color3 el del operador Color(0xff6B00A1)
      onPrimary: color3,
      // color4 el del scaffold del drawer y divider del resultado Color(0xff52007A)
      secondary: color4,
      // color5(casi negro) el de los numeros del teclado y valores resultado Color(0xff27003B)
      secondaryVariant: color5,
      // blanco puro Color(0xffFFFFFF)
      error: blanco,
      // negro Color(0xff000000)
      onError: negro,

      // color fuera numero
      surface: colorFueraNumero,
      // color dentro numero
      onSurface: colorDentroNumero,
      // color fuera igual
      background: colorFueraIgual,
      // color dentro igual
      onBackground: color4,
      // color fuera operadores
      onSecondary: colorFueraOperadores,

      brightness: Brightness.light
    ),

    visualDensity: VisualDensity.adaptivePlatformDensity,

    appBarTheme: AppBarTheme(
      color: Colors.transparent,
      elevation: 0,
      centerTitle: true,
      textTheme: TextTheme(
        headline6: GoogleFonts.exo(color: color2, fontSize: 19.0.sp, fontWeight: FontWeight.w600)
      ),
      iconTheme: IconThemeData(
        color: Colors.white,
        size: 27.0.sp
      ),
    )
  );

It says that the fault is in the line of headline: and also in that of size: inside iconTheme
I send you a capture of all the errors.

Although there it says # 1 DeviceExt.w I have tried with all of them, 19.0.sp, 19.0.w, 19.0.h, 19.sp, 19.w, 19.h.
They all give those same mistakes.
I've been testing and I can't solve it, but the fact is that I was using the sizer package, the same one where you told me in response to my request to add ".sp" also in the "int" that this package of yours will use, but for now I will finish my app with that package and the next one I will start with yours, since it will be easier for me starting from scratch to find the errors.

The error occurred because you called 27.sp before src/helper.dart was able to execute width = boxConstraints.maxWidth. How did you use your ThemeData and did you wrap your MaterialApp with ResponsiveSizer widget?

I leave you a link with a test project that I did, where I make a main.dart with a simple page and put the ResponsiveSizer () widget as it is in the example of the package, the theme.dart file is also added, which is the I use to create my theme, if you try it, it should give you the same error as me.
I do not understand why it gives that error, with the other sizer package that is the one before your package it did not give me this problem, so I say that I will use your package in the next app to test it.
Maybe it may be that it is an error because I use the theme as a static variable to be able to call it without having to create an instance in each file where I want to use it (although I only use it in main), but as I have already said I am using it like this with the other packet and the error does not pass.
Here I leave the link to the test project that I mentioned before, so that you can do tests yourself:
https://github.com/Hekhy/responsive_try

Hello @Hekhy,
The repo you sent here is private. Kindly make the repo public so I could take a look at your test project.

Oh, sorry, I thought that private meant that only the person who sent the link could see it. I'm new to github and I'm not very good at it yet. Now you should be able to download it.
https://github.com/Hekhy/responsive_try

Thanks for pointing this out @Hekhy. It turns out that Device.setScreenSize() doesn't get called before MaterialApp is built. I'll create a PR soon to fix this issue.

@Hekhy The Device.setScreenSize function in ResponsiveSizer isn't called before you accessed 27.sp.  You could solve it by wrapping your MaterialApp with a FutureBuilder :
return ResponsiveSizer(
   child: FutureBuilder(
      future: Future.delayed(Duration.zero),
      builder: (BuildContext context, AsyncSnapshot snapshot) {
        return MaterialApp(
          theme: Tema.theme,

Perfect I will try it like that, although if you could add it as an update, no one will have problems. Thanks for the help :)

Thanks @Hekhy. I tried placing the FutureBuilder as part of the ResponsiveSizer widget. It didn't work because by passing Widget child <- (in your case, MaterialApp), Tema.theme gets called even before ResponsiveSizer gets to build its own widgets. I will add that as an update once I figure out a solution.

Hello @CoderUni,
Sounds good to me, I'll be attentive to new versions of the package or a possible notification from you, hopefully you can solve it soon.
And to say, not as it criticizes you or your package, but as it criticizes the Dart language, which is a bit strange that in the build of a widget the theme is loaded before the previous widgets as in this case the layoubuilder.
I don't know exactly how Dart works 100%, but I think it must have something to do with it first reads all the files and the file where the theme is reads it at the same time as the file where the app material is and how it doesn't load to time Device.setScreenSize (constraints, orientation); gives the error.
I suppose you had reached some similar conclusion, but I am telling you because the method used in the other sizer package was different, maybe you can walk there to solve the problem.
I also tried to put your package in my project locally, to be able to make changes and try to help you with the solution, but it can't, in the visual studio code editor it doesn't give me any code errors, apparently everything is fine, but when I launch The application to test gives me errors that make me think that the version of Dart that each of us has is different, maybe the problem can also go there, but I think my version is the last one since a few days ago I updated Flutter and Dart was updated automatically. I will also try to update it if it is not, and I will try again, but I say this hypothesis about the Dart version because when you configure the child argument of the ResposiveSizer widget in its constructor, you put required and I have always used @required, and it is there where is it giving me the error, and even if I change it and put @required it goes well, because I get an error in the editor and it tells me that the child argument cannot be null although calling MaterialApp as the child of ResposiveSizer, I have not managed to fix anything and that was the only change I had made.
I would like to have helped by doing my own tests, but it has not been possible.

Thanks for your insights @Hekhy . After analyzing the problem extensively, I've realized that I'm supposed to use a builder to build the child to solve the problem. I've updated the package (^2.0.0) to fix this issue.

Now it works!! Thank you!
The only thing I'm wondering is why you didn't create the widget like this:
class ResponsiveSizer extends StatelessWidget {
  const ResponsiveSizer({Key? key, required child}) : super(key: key);

  /// Builds the widget whenever the orientation changes
  final Widget child;

  @override
  Widget build(BuildContext context) {
    return LayoutBuilder(builder: (context, constraints) {
      return OrientationBuilder(builder: (context, orientation) {
        Device.setScreenSize(constraints, orientation);
        builder: (context, orientation, Device.screenType) {
          return child;
        }
      });
    });
  }
}

That way you could call it like this:
Widget build(BuildContext context) {
    return ResponsiveSizer(
      child: MaterialApp(

in the same way you had it before but with the added builder and so it is as clean as before, which is one of the things that I love about your package.

You cannot pass a child because you want it to rebuild whenever the orientation changes. This is why certain widgets like LayoutBuilder and StreamBuilder use the builder parameter.

Ah, okay, I didn't know, it's a shame it can't be done, it was so convenient to be able to use it just by calling the ResponsiveSizer widget and sending the child.
Never mind, great job!

@CoderUni Hello again, I'm sorry to come back here after so long, but I didn't want to open a new error just to ask you a question. I've been using the package, and it's going very well, the problem is that I don't know if I'm using it well. Since the same thing happened to me with the other sizer package. That is to say that I cannot adapt my application well to all screens and that it is perfect, and I think it is because I do not use it well. So my question would be, should I put the ResposiveSizer widget on every screen where I use it or just putting it in the main like this in the example works?


Error: Sprockets::FileOutsidePaths

Hello,
After setting the src_dir in in jasmine.yml, it shows the following error in browsers (/specs). The tests work fine from command line: bundle exec jasmine-headless-webkit. How can I make it work from both command line and browser?
jsmine.yml
src_files:
  - "mobile_application.js"
...
src_dir: app/assets/javascripts

Error in browser:
Error: Sprockets::FileOutsidePaths: /home/evgeny/web/digitalsafe/mobile_application.js isn't in paths: /home/evgeny/web/digitalsafe/spec/javascripts, /home/evgeny/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/jasmine-core-1.1.0/lib/jasmine-core, /home/evgeny/web/digitalsafe/app/assets/images, /home/evgeny/web/digitalsafe/app/assets/javascripts, /home/evgeny/web/digitalsafe/app/assets/stylesheets, /home/evgeny/web/digitalsafe/vendor/assets/stylesheets, /home/evgeny/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/jasmine-rails-0.0.3/app/assets/javascripts, /home/evgeny/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/jasmine-rails-0.0.3/app/assets/stylesheets, /home/evgeny/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/jquery-rails-1.0.19/vendor/assets/javascripts, /home/evgeny/web/digitalsafe/app/assets/javascripts [http://localhost:3000/assets/jasmine_rails/application.js:1]
ReferenceError: jasmine is not defined [http://localhost:3000/specs:15]

+1


Ability to delete a prompt

We need to have the ability to delete a prompt.
add a service method to prompts.service.ts to delete the prompt. You'l use Prisma to delete it (look at the other methods in the service).
Then add a deletePrompt mutation to the prompts.resolver.ts.
The Delete button should be displayed as follows:

There's already a prompt deletion confirmation modal implemened (check out apps/console/src/app/pages/prompts/[promptId]/index.tsx line 69). So all in all it's a fun task.
p.s. you'll need to adjust the Prisma Schema to cascade delete all dependants of a Prompt when you delete it. You can see how to do that here.

Can I work on this @arielweinberger ?

@alceil Of course! Go for it.

Since there's no progress with this one, I'll leave it to somebody else from the community for now.

@AyanDas348 would you like to take this?
It's quite simply - add a service method to prompts.service.ts to delete the prompt. You'l use Prisma to delete it (look at the other methods in the service).
Then add a deletePrompt mutation to the prompts.resolver.ts.

@arielweinberger Sure I'll give it a try. Thanks!

Fixed in #84, to be released very soon in v0.3.0


godot: 3.0.6 -> 3.1

Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] 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/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I tried the PR with nix-review and get
builder for '/nix/store/md5wmgwbyradx0jbb67bl67z7qrxnb0w-godot-3.1.drv' failed with exit code 2; last 8 log lines:
  unpacking sources
  unpacking source archive /nix/store/babbqrsgdig50ddxwb9mqr2rh5x9pcb3-source
  source root is source
  patching sources
  applying patch /nix/store/sh1yzanh647zbr7jcbw0wd3g1drdrbpp-pkg_config_additions.patch
  patching file platform/x11/detect.py
  patch: **** malformed patch at line 14: @@ -264,7 +270,7 @@ def configure(env):
cannot build derivation '/nix/store/lx75f4bsjig5i9j4nnxaia9ldaladxa8-env.drv': 1 dependencies couldn't be built
[1 built (1 failed), 5 copied (10.1 MiB), 1.8 MiB DL]
error: build of '/nix/store/lx75f4bsjig5i9j4nnxaia9ldaladxa8-env.drv' failed

@Moredread Ahh, sorry, I forgot to adjust the line numbers after I deleted a redundant line from the patch. I pushed a patch that applies properly now. :)


Add title attributes to NoteMenuBar buttons

Description
Closes #456
Browser checklist
This PR has been tested in the following browsers:

[x] Chrome
[x] Firefox
[x] Safari

Testing checklist

[ ] End-to-end tests have been created if necessary

I have not added tests for this feature but I can if needed.

I was wondering. If this adds actual tooltip. But title attribute is just fine.

cc/ @taniarascia

I would prefer an actual tooltip be created rather than the title attribute.

@taniarascia Do you want me to pull in a react tooltip package? Or should I make it a CSS only tooltip? Any design direction on how to tooltip works, I'm guessing have it work similar to how the title attribute tooltip works?

Sorry for the delay with this. If you want to just bring it up to date with master and keep the title attributes for now, it should be good to go. We can make more front end friendly tooltips in an additional PR.

Closing due to inactivity.


Video Quality(360p/720p/1080p) To Choose

Hi, I was wondering do you control the video quality(e.g. 360p/720p/1080p) when downloading the videos from youtube/bilibili, since tools like yt-dlp will automatically choose the best quality if using default settings. Thanks!

Thanks for your interest! We use 'you-get' with option '--format=flv360' to download the videos, and then use 'ffmpeg' to transcode.


Template for custom app nginx/worker images

Following the docs in https://github.com/frappe/frappe_docker, I've created worker and nginx images for a custom app. Now, the helm chart needs to be made aware of these additional images. It looks like a deployment template needs to be created and the job* templates modified accordingly.
Are there docs or examples available for inserting custom images like this?

just override values for image repo and tag with your images. (this should solve your problem)
if you need to add deployments of your own then as this chart as a sub chart and build your own chart (this is not what you're looking for, this is for custom non frappe apps working with frappe.)

open issue again if necessary.


Invalid header signature

when i am trying to import data from some xls files
NPOI.POIFS.FileSystem.NotOLE2FileException: 'Invalid header signature; read 0x6320656C6261743C, expected 0xE11AB1A1E011CFD0 - Your file appears not to be a valid OLE2 document'

I´m having the same problem, no feedback about this?

I'm have same problem too

@nrk6208  Hi , did you  solve that problem?

when i am trying to import data from some xls files
NPOI.POIFS.FileSystem.NotOLE2FileException: 'Invalid header signature; read 0x6320656C6261743C, expected 0xE11AB1A1E011CFD0 - Your file appears not to be a valid OLE2 document'

I am having the same problem,too.
did you solve that porblem?

I am having the same problem, too. In my case, I have imported wrong library (NPOI) for Asp.net core project. I must switch library to dotnetcore.NPOI and it works!


Quest v0.2 : MLS - Translating CQL results based on current selected Language preference

Is your feature request related to a problem? Please describe.
CQL evaluation results translated post computation based on the selected app language preference
Describe the solution you'd like
The current CQL statements do not have translation for the evaluations that are text based post computation
Subtask

[ ] Add language translation for G6PD test and G6PD control mode questionnaires
[ ] Research on how to do CQL results language conversion

Additional context
N/A
Screenshots

Closing this in favour of #3301


GDS UI copy changes

Codecov Report

Merging #444 (755fef7) into main (481e449) will decrease coverage by 9.45%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #444      +/-   ##
==========================================
- Coverage   47.16%   37.71%   -9.46%
==========================================
  Files         232      151      -81
  Lines       11615     2368    -9247
  Branches      606      606
==========================================
- Hits         5478      893    -4585
+ Misses       5180     1302    -3878
+ Partials      957      173     -784

Impacted Files
Coverage Δ

directory/pkg/gds/secrets/token.go

directory/pkg/gds/secrets/secret.go

directory/pkg/trtl/replica/prob.go

directory/pkg/gds/store/leveldb/iterator.go

directory/pkg/bff/parallel.go

directory/pkg/trtl/replica/stream.go

directory/pkg/bff/config/config.go

directory/pkg/trtl/replica/util.go

directory/pkg/gds/store/trtl/connect.go

directory/pkg/gds/models/v1/models.pb.go

... and 71 more

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 481e449...755fef7. Read the comment docs.


Added CSS recommendations guide

Q
A

content fix?
no

New article?
yes

Related issues?
N/A

What's in this Pull Request?
CSS recommendations guide

thx Waldek, appreciated.


Initial work towards Continuous deployment (commented out)

Not fully working, commented out in actions

Merging so that master builds and pushes with the github commit hash as the docker image tag


Refresh account balances with and without own node.

I do not see all the transactions (when I connect to the own node)which I have done using the Bithway node.
-While using Bithyve node:

-When connected to the own node by disconnecting the Bithyve node:

@cakesoft-swati They are all new transactions once they have confirmations they will be visible.

@cakesoft-swati They are all new transactions once they have confirmations they will be visible.

@cakesoft-swati They are all new transactions once they have confirmations they will be visible.

@cakesoft-swati please confirm if the balances refreshed after the transactions had confirmations.

@cakesoft-swati They are all new transactions once they have confirmations they will be visible.

@cakesoft-swati please confirm if the balances refreshed after the transactions had confirmations.

-Unable to reproduce this issue on dev app version 1.4.2(202)
-I can see the all transactions including unconfirmed one.

-Unable to reproduce this issue on dev app version 1.4.2(202)
-I can see the all transactions including unconfirmed one.


Manage site URL to allow proper SEO

The page created with the 1&1 web tool provides a URL based SEO where the spider-bots can easily crawl it and can identify that it's not the same content.
We need to find a way to use this type of functionality here as well.

Using Hash-Links for Page and SEO


Use static final instead of static const for token used with plugin_platform_interface

🐛 Bug Report
Describe the bug
This plugin should not use a const Object() as the platform interface token. There was an error in the documentation for  plugin_platform_interface; see https://github.com/flutter/flutter/issues/96178.
The consequence is that someone could develop an implementation of GeolocatorPlatform using implements instead of extends, and everything would work initially but changes to the platform interface would break that implementation.
To fix, use a static final Object _token = Object(); instead of static const Object _token = Object(); in GeolocatorPlatform.
Also, consider updating geolocator_platform_interface's dependency on plugin_platform_interface to ^2.1.1 and using PlatformInterface.verify instead of verifyExtends. This will prevent regressions.
/cc @stuartmorgan
Expected behavior
Should not be possible to build a class that implements GeolocatorPlatform using implements because GeolocatorPlatform uses a non-const token and calls verify.
Reproduction steps

Build a class that implements GeolocatorPlatform instead of using extends. Use const Object() as the token. e.g.

class DontDoThis extends PlatformInterface implements GeolocatorPlatform {
  DontDoThis(): super(token: const Object());
  ...
}
...
GeolocatorPlatform.instance = DontDoThis();

Make an app that depends on the new class and imports the file where it is defined.
Make a minor change to GeolocatorPlatform (adding a method).
Compile error "DontDoThis is missing implementations for these members ..."

Configuration
Version: geolocator 8.0.1. geolocator_platform_interface 3.0.1
Platform:
any

@collinjackson Thanks for reporting this issue. I've made a PR, will be merged soon, thanks!


FIX: Redirect loop with multiple confirmation tokens present (fixes #8607)

Looks like a couple of the unit tests need adjusting - expecting ?devbuildtoken= in the URL, could just look for devbuildtoken= in the URL instead

Tested:

/?flush
/dev/build?flush
/dev/build

LGTM

Looks like a couple of the unit tests need adjusting - expecting ?devbuildtoken= in the URL, could just look for devbuildtoken= in the URL instead

Ah yep, I’ve pushed up fixes for those

Merged up to 4.3


call onValueChange only when value changes

Summary
OnValueChange function of Picker is called when Picker is initialized.

Changelog
[Android][fixed] - OnValueChange will be called only when the selectedValue changes.

Test Plan
export default class App extends Component<Props> {
  constructor(props) {
    super(props);
    this.state = {language:"js",test:1}
  }
  render() {
    return (
      <View style={styles.container}>
        <Picker
          selectedValue={this.state.language}
          style={{height: 50, width: 100}}
          onValueChange={(itemValue, itemIndex) =>{
            this.setState({language: itemValue,test:2});
          }
        }>
          <Picker.Item label="Java" value="java" />
          <Picker.Item label="JavaScript" value="js" />
        </Picker>
        <Text>{this.state.test}</Text>
      </View>
    );
  }
}

Here state.test must be 1 when the app loads. But the onValueChange is called initially which changes state.test to 2. This pull request fixes the issue.

cc @Kudo since you recently fixed an issue with onValueChange.

Thanks @cpojer.
Hey @a-c-sreedhar-reddy, just to clarify which RN version you used.
My change landed after RN 0.59, so that if you tested on RN 0.58 or before, there might be another story.
I've tested your code, but seems works fine on RN 0.59.
Could you please double check your RN version and if RN 0.59 works for you?

Thanks @cpojer.
Hey @a-c-sreedhar-reddy, just to clarify which RN version you used.
My change landed after RN 0.59, so that if you tested on RN 0.58 or before, there might be another story.
I've tested your code, but seems works fine on RN 0.59.
Could you please double check your RN version and if RN 0.59 works for you?

    "react": "16.8.3",
    "react-native": "0.59.5"

This is what I tested with.

That's weird to me since I tested with the exact same version.
Supposedly this issue should not happen as it is handled by native side.
https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/views/picker/ReactPicker.java#L98-L103
  @Override
  protected void onLayout(boolean changed, int left, int top, int right, int bottom) {
    super.onLayout(changed, left, top, right, bottom);

    // onItemSelected gets fired immediately after layout because checkSelectionChanged() in
    // AdapterView updates the selection position from the default INVALID_POSITION.
    // To match iOS behavior, which no onItemSelected during initial layout.
    // We setup the listener after layout.
    if (getOnItemSelectedListener() == null)
      setOnItemSelectedListener(mItemSelectedListener);
  }

@Kudo  yes you are correct. I don't know why but its perfect now. May be I did not update node modules. Sorry for this.  To remove this commit should I again send a PR?

@Kudo  You are right. May be I did not update node modules. Sorry for this. Should I make a PR removing this change?

@a-c-sreedhar-reddy Sorry missed this. Your fix is fine for me.
In fact, from the semantic of onValueChange, it is no hurt to double check for value inequality.
Just to clarify if I was doing wrong in Java native side.


How to create Druid Hll(HyperLogLog) aggregation function

I have a field in druid spec configured as:
 "metricsSpec": [
      {
        "type": "HLLSketchMerge",
        "name": "approx_count",
        "fieldName": "approx_count",
        "lgK": 12,
        "tgtHllType": "HLL_4"
      }
    ]

And I want to perform aggregation on it:
"aggregations": [
  {
    "type": "HLLSketchMerge",
    "name": "approx_count",
    "fieldName": "approx_count"
  }
],

this works for me in rest api, but can't find how to do it from SuperSet.

Found How to do it, need to go to data source configuration and add one more metrics, like the bellow screenshot.


Add OpenWebText and Organize

@ndey96

Draft PR until I finish the README

@Quentin-Anthony looking great now! Can you just undo the changes to the mutransfer_lr_shakespeare_char folder? Then I'm good to merge

@Quentin-Anthony looking great now! Can you just undo the changes to the mutransfer_lr_shakespeare_char folder? Then I'm good to merge

Done!


fix history content from agent memory.

Description
define a new func to get agent history from memory

test


Staging next

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

merged master into staging-next to fix merge conflicts

just FYI, this will likely be the last staging-next before the branch-off on Sept 4th.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/marketing-team-can-we-present-nix-nixos-better/6249/106


feat(Options): Run Command

Run command should be able to give options to users as in:

Compiler Flags
Command-line Options
Driver
Input
Args

These must be optional.

Completed in efc00ca


GSSOC'23 - Added python script to play hangman

Description
I have added the Python script to play the classic Hangman game. Hangman is a popular word-guessing game where players try to guess a secret word by suggesting letters. This script will provide an interactive and enjoyable gaming experience for users.
Fixes #1876

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand [README.md](http://readme.md/)
[x] My documentation follows Template for [README.md](http://readme.md/)
[x] I have added the project meta data in the PR template.
[x] I have created the requirements.txt file if needed.

Project Metadata
If there is no-file/nothing to fill the below fields with, then type: none
Example: If no requirements.txt needed/present, then type none in Requirments.
Category:

[ ] Calculators
[ ] AI/ML
[ ] Scrappers
[ ] Social_Media
[ ] PDF
[ ] Image_Processing
[ ] Video_Processing
[x] Games
[ ] Networking
[ ] OS_Utilities
[ ] Automation
[ ] Cryptography
[ ] Computer_Vision
[x] Fun
[ ] Others

Title: Hangman game
Folder: hangman
Requirements: none
Script:  hangman.py
Arguments:  none
Contributor:  srujana-16
Description:  The Hangman game is a classic word-guessing game where the player tries to guess a secret word within a certain number of attempts.

Please add this as part of GSSOC'23


Re-Wrote this program

Re-wrote your program due to the EOF, I fixed it and never had the issue again. Now, there is a rate limit on the API. I've tested rotating proxies but it's just too slow and they don't connect fast enough after each password attempt. I was thinking Tor, but even then with new identities, those IP addresses will be API banned. This rate limit method from what I've observed through testing is x amount of passwords tried in x amount of time resulting in the block of sending API requests. And the API ban is not perm just temp, discovered while testing without my VPN accidentally.
Any ideas? I've had fun trying new ideas and such but am running dry.

Also, feel free to DM me on Instagram @TorinTurner for a more one on one conversation that is private.

awesome!  there are actually a couple ways to positively address it and i wasn’t keen on weaponizing it myself - i expected more people to “figure it out” and use it as a lesson if they wanted to get it working, but you know how that goes.  the program only serves one purpose (obviously nefarious), so i’ve been hesitant about personally patching it for people that are just looking for something plug and play.  the semaphore method illustrated has also fallen out of favor and superseded by other idiomatic plays.
Sent from my iPhone

On Nov 19, 2019, at 3:33 PM, Torin Turner<EMAIL_ADDRESS>wrote:

Also, feel free to DM me on Instagram @TorinTurner for a more one on one conversation that is private.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Of course, who wouldn't be hesitant? Programs like this can never be good if used by the wrong people. Ruining the fun for us who have fun finding these security loopholes and workarounds. The method was simple and I was surprised by its simplicity and ability to work as fast as it did with the API. I think a possible way around this API rating would be to figure out max attempts in a set time then setting a pause for proxy rotate (which is still too slow for my liking.)
I also haven't tried this yet and doubt it would work but instead of going through every password on said account may be possible the API block doesn't trigger when it is a new username per attempt.
So rotate through every username on the first password then so on.
I'll try this.

The normal login site does not trigger the Captcha if the username is changed by a capital letter or vice versa per attempt, allowing more attempts. As well as new username attempts completely reset it.

i hit you on instagram btw


Remove references to syscall package

The syscall package is deprecated since Go 1.4:

Deprecated: this package is locked down. Callers should use the corresponding package in the golang.org/x/sys repository instead. That is also where updates required by new systems or versions should be applied. See https://golang.org/s/go1.4-syscall for more information.

References to the syscall package in the codebase should be cleaned up as it is, in effect, not updated "not even to keep pace with changes in operating systems it references".

Hey @Rolinh, I'm still working on understanding the architecture of Cilium, but interested in the project, and got make running successfully!
Happy to take on this find/replace task following the go1.4-syscall directives. Any further instructions/guidance?

Hey @Ropes, thanks for contributing!

got make running successfully!

You may want to take a look at the contributor's guide which has instructions to bring up a vagrant VM for dev purposes.

Any further instructions/guidance?

Nothing that I can think of as of now.

@Rolinh thanks! I had a look at the contributor's guide, I'll get this branch running on Vagrant before PR.
Complication
I discovered a use of sycall.RawConn in pkg/fqdn/dnsproxy, udp.go. This is a tight coupling of syscall and the net package's ListenConfig.ListenPackage(...) implementation. There is no unix package equivalent, nor would the type system allow it.
Some design criteria of the DNS/UDP forwarding are written in SetSocketOptions:
	// Set up the raw socket for sending responses.
	// - Must use a raw UDP socket for sending responses so that we can send
	//   from a specific port without binding to it.
	// - The raw UDP socket must be bound to a specific IP address to prevent
	//   it receiving ALL UDP packets on the host.
	// - We use oob data to override the source IP address when sending
	// - Must use separate sockets for IPv4/IPv6, as sending to a v6-mapped
	//   v4 address from a socket bound to "::1" does not work due to kernel
	//   checking that a route exists from the source address before
	//   the source address is replaced with the (transparently) changed one

I don't posses a deep understanding of the UDP forwarding. However looking at the functionality of the package, and the design criteria above, I'm unsure if granular control of the net.ListenConfig->ListenPacket() can be achieved with the more connection based net package listener implementations. It might be possible, but it will be a more significant change. I can look into it, but I'd like feedback to determine if that's in scope.
Decision

Should the DNS proxy UDP listener be refactored to remove one use of syscall.RawConn?
I've replaced all other uses of syscall with x/sys/unix; going with the assumption that executing on Windows environments is not a project goal? Didn't see anything in the docs about running Windows k8s clusters so figured I could skip handling that. :D

Should the DNS proxy UDP listener be refactored to remove one use of syscall.RawConn?

Not sure. /cc @jrajahalme

I've replaced all other uses of syscall with x/sys/unix;

I think this is fine; Windows support would require a lot of work anyway.

syscall.RawConn is an interface that is part of the net API. As long as there is no replacement for it within net.ListenConfig IMO we have to keep using it. The interface itself has no references to the rest of the syscall package, it just happens to be defined there. Even the implementation of it in https://golang.org/src/net/rawconn.go only references syscall for syscall.EINVAL. Given this I see no immediate reason for net to change away from using syscall.RawConn.
All other references to syscall in pkg/fqdn/dnsproxy/udp.go should be trivially replaceable with unix.

Alright, I opened a PR to get feedback from the CI bots. Looks like Hound is not happy with some of the function return parameters in the files I updated.

Are these sort of formatting critiques blocking? If you'd like me to make changes I'm open to do it, but also don't want to end up in a mess of Yak fur if that's counter-productive..
I also booted up a local testing environment, which built(!), but have yet to run tests... Wanted to get this posted for those in EU.

The *WithErrno() functions are going away in #10058 in favor of error wrapping so it doesn't matter in this case.


Open multiple terminals with a custom command

Description
I'd like to write a custom command to open multiple terminals at once, but only one terminal actually opens.
Steps to reproduce

Open init.coffee script
Add:

atom.commands.add 'atom-workspace', 'custom:open-two-terms', ->
    editor = atom.views.getView(atom.workspace.getActiveTextEditor())
    atom.commands.dispatch(editor, 'platformio-ide-terminal:new')
    .then () -> atom.commands.dispatch(editor, 'platformio-ide-terminal:new')

Reload Atom window from the palette
Run the custom command from the palette

Expected behavior: Two terminals open
Actual behavior: Only one terminal opens
Reproduces how often: 100%
Versions

> atom --version
Atom    : 1.38.2
Electron: 2.0.18
Chrome  : 61.0.3163.100
Node    : 8.9.3

> apm --version
apm  2.1.7
npm  6.2.0
node 8.9.3 x64
atom 1.38.2
python 2.7.16
git 2.21.0

OS name and version: Fedora 30
Platformio-ide-terminal version: platformio-ide-terminal unknown.

I thought I had the latest version, which was obviously not the case. Now I'm stuck with #700 and cannot even open one terminal...

After updating Atom and rebuilding the package (because of incompatible native modules), the problem is still here.

@Arcesilas Thank you for opening this issue.

Platformio-ide-terminal version: atom-ide-terminal 5.0.1

This isnt correct repo, Im not even familiar with atom-ide-terminal (seems like a useless fork of this project), atom-ide-terminal != Platformio-ide-terminal also Platformio-ide-terminal is version 2.9.3 not 5.0.1, you definitely have wrong project.
Please go complain to https://github.com/qicrosoft/atom-ide-terminal maintainer.
Regarding your main question though, Im not sure its correct. Youre calling atom-ide-terminal this is Platformio-ide-terminal you need to call that when using this project.
Regarding issue #700, see https://github.com/platformio/platformio-atom-ide-terminal/issues/760
So because youre submitting an issue report to the wrong repo Im closing this as invalid. Feel free to use the correct project

@Arcesilas Thank you for opening this issue.

Platformio-ide-terminal version: atom-ide-terminal 5.0.1

This isnt correct repo, Im not even familiar with atom-ide-terminal (seems like a fork of this project just renamed nothing else been done), atom-ide-terminal != Platformio-ide-terminal also Platformio-ide-terminal is version 2.9.3 not 5.0.1, you definitely have wrong project.
Please go complain to https://github.com/qicrosoft/atom-ide-terminal maintainer. Thanks.
Regarding your main question though, Im not sure its correct. Youre calling atom-ide-terminal this is Platformio-ide-terminal you need to call that when using this project and Im not even sure thats the correct way to do it, if you look through the source code you should see how to call platformio-ide-terminal to open a new terminal.
Regarding issue #700, see https://github.com/platformio/platformio-atom-ide-terminal/issues/760
So because youre submitting an issue report to the wrong repo Im closing this as invalid. Feel free to use the correct project and update the issue ticket (I may repopen this then), but as is, providing support for some random project, is not something Im prepared to do at this time beyong what was said.
Thanks for understanding.

I forgot to mention that after updating Atom I could install platformio-ide-terminal (rebuilding the package with apm was required) and could make it work. And the problem is still the same:

Open init.coffee script
Add:

atom.commands.add 'atom-workspace', 'custom:open-two-terms', ->
    editor = atom.views.getView(atom.workspace.getActiveTextEditor())
    atom.commands.dispatch(editor, 'platformio-ide-terminal:new')
    .then () -> atom.commands.dispatch(editor, 'platformio-ide-terminal:new')

Reload Atom window from the palette
Run the custom command from the palette

Then, only one terminal opens.
It seems that while the terminal is animating, no other operation can be performed. Am I correct?
I'm sorry, it was late yesterday night, I was struggling with many terminals, many configurations, trying many init.coffee variations, I forgot to mention I was finally working with platformio-ide-terminal...

It seems that while the terminal is animating, no other operation can be performed. Am I correct?

No idea tbh, but you can disable animations to find out.
In Atom do:

File (menu)
Settings
Install
search for platformio-ide-terminal
Click platformio-de-terminal Settings button
scroll to Animation speed and turn this to 0

Also, you can try running the platformio-ide-terminal:new in the Auto Run Command setting above.

Also you can add logging to your init script to see whats going on, Im really not familiar with init scripts in atom, but seems if something is not happening you should be able to log the failure.
See https://discuss.atom.io/t/how-to-dispatch-a-command-on-atom/46552

Hi. Thanks for reopening and taking time to answer.

Anyway, I had already used console.log to see what happens. Here's an example:

atom.commands.add 'atom-workspace', 'custom:open-two-terms', ->
    editor = atom.views.getView(atom.workspace.getActiveTextEditor())
    atom.commands.dispatch(editor, 'platformio-ide-terminal:new')
    .then () -> atom.commands.dispatch(editor, 'platformio-ide-terminal:new')
    .then () -> console.log('Seems to be ok')

The message "Seems to be ok" is logged to console. Actually, I can see it is written before the terminal has finished to display, as you can see on this screencast:

Since then() returns a promise, the second command must have been run, or at least, started.
I'm not familiar at all with JS and CoffeeScript. I've tried to look at the source code of your package to see if I could change something to tweak the behaviour, before submitting any PR or so, but I'm very confused with ES2015 syntax and the mix with CoffeeScript... It's very different from what I learned (a little) 20 years ago... Thanks for taking time on this issue.

Ive really no better knowledge to impart here, Im also coffeescript JS challenged, You could try adding a pause to ensure that terminal has fully opened before issuing the second terminal open command.
Try to get some help in the Atom support thread to see if you get any better answers though, Im sorry I cant be of better help to you here.

I've already tried to add a pause with a custom sleep function, with no better result.
Thanks for your help anyway, I'll try to find out a way to open multiple terminals with one single command.
Can you please leave this issue open and update its labels?

Sure.

Hello World