GNRD is grabbing extra words after a taxon name

GNRD is finding a correct taxon name, but grabbing a following word that it shouldn't. Words like "clade", "complex", and "genome" are very common

data package ID
name
error type
text string
notes

497
X. tropicalis genome
false positive

should    not have grabbed "genome"

1218
Giardia lamblia genome
false positive

should  not have grabbed   "genome"

422
Marmota clade
false positive

should  not have grabbed the   "clade"

743
Cymbella ventricosa
false positive

should have grabbed the /turgida too, maybe

956
foraminifera
false negative

should have grabbed this and not "benthic foraminifera"

274
Gasteracantha clade
false positive
Gasteracantha clade as sister
should not have captured "clade"

313
T. hudsonicus clade
false positive

should not have captured "clade"

252
R. antirrhini complex
false positive

should not have captured "complex"

333
C. maculata complex
false positive

should not have captured "complex"

333
C. striata complex
false positive

should not have captured "complex"

333
C. striata plex
false positive

should not have captured "complex", which was on line break

307
Glossina distribution
false positive
surveys of Glossina distribution to monitor
should not have captured "distribution"

225
A. aspera eastern
false positive
of the A. aspera eastern Caribbean data set
should not have captured "eastern"

313
T. hudsonicus genotype
false positive

should not have captured "genotype"

317
Ndundulu haplotype
false positive

should not have captured "haplotype"

317
Ndundulu kipunji haplotype
false positive

should not have captured "haplotype"

252
R. antirrhini lineages
false positive
associated R. antirrhini lineages,
should not have captured "lineages"

313
Tamiasciurus lineages
false positive

should not have captured "lineages"

268
Anolis may
false positive
ecology of Anolis may represent
should not have captured "map"

313
Tamiasciurus may
false positive
Tamiasciurus may lead
should not have captured "may"

323
T. truncatus may
false positive

should not have captured "may"

329
H. gardneri may
false positive
in H. gardneri may arise
should not have captured "may"

333
C. striata may
false positive

should not have captured "may"

252
L. vulgaris origin
false positive

should not have captured "origin"

317
Rungwecebus specimen
false positive

should not have captured "specimen"

307
G. palpalis subspecies
false positive
uncharacterized G. palpalis subspecies
should not have captured "subspecies"

252
Linaria taxa
false positive

should not have captured "taxa"

313
T. hudsonicus used
false positive

should not have captured "used"

946
X. clivii after
false positive

should not have grabbed "after

1326
Acanthopagrus schlegeli after
false positive

should not have grabbed "after" - related to false negative

422
Alaskan broweri
false positive

should not have grabbed "Alaskan"

1359
O. tuberosa alliance
false positive

should not have grabbed "alliance"

422
American broweri
false positive

should not have grabbed "American"

422
Asiatic camtschatica
false positive

should not have grabbed "Asiatic"

422
Both caudata
false positive

should not have grabbed "both"

684
N. multifasciatus candidate
false positive

should not have grabbed "candidate"

1158
S. glynni change
false positive

should not have grabbed "change"

432
Caenorhabditis clade
false positive

should not have grabbed "clade"

432
Rhabditis clade
false positive

should not have grabbed "clade"

684
L. lemairii clade
false positive

should not have grabbed "clade"

684
L. callipterus clade
false positive

should not have grabbed "clade"

825
D. simulans clade
false positive

should not have grabbed "clade"

1044
C. ohridella clade
false positive

should not have grabbed "clade"

1359
O. acetosella clade
false positive

should not have grabbed "clade"

1359
O. rosea clade
false positive

should not have grabbed "clade"

1523
K. septemlobus clade
false positive
Within the K. septemlobus clade, the haplotypes
should not have grabbed "clade"

457
Trichoptera clades
false positive

should not have grabbed "clades"

505
C. ignobilis clades
false positive

should not have grabbed "clades"

505
C. melampygus clades
false positive

should not have grabbed "clades"

684
L. callipterus clades
false positive

should not have grabbed "clades"

684
Eretmodus clades
false positive

should not have grabbed "clades"

765
Afrotheria clades
false positive

should not have grabbed "clades"

1005
Neotropical clades
false positive

should not have grabbed "clades"

1044
Phyllonorycter clades
false positive

should not have grabbed "clades"

1359
Oxalis clades
false positive

should not have grabbed "clades"

726
Aedes taeniorhynchus collection
false positive

should not have grabbed "collection"

1027
Boechera stricta collection
false positive

should not have grabbed "collection"

448
P. hylocetes complex
false positive

should not have grabbed "complex"

448
A. tigrinum complex
false positive

should not have grabbed "complex"

448
Ambystoma tigrinum complex
false positive

should not have grabbed "complex"

835
I. batatas complex
false positive

should not have grabbed "complex"

966
Drosophila serrata complex
false positive

should not have grabbed "complex"

1048
Burkholderia cepacia complex
false positive

should not have grabbed "complex"

1048
B. cepacia complex
false positive

should not have grabbed "complex"

1310
Paxillus involutus complex
false positive

should not have grabbed "complex"

1469
Lycaeides complex
false positive

should not have grabbed "complex"

1519
A. tumefaciens confer
false positive
A. tumefaciens confer the ability to
should not have grabbed "confer"

1292
Acropora coral larvae
false positive

should not have grabbed "coral larvae"

366
Mytilus data
false positive

should not have grabbed "data"

448
P. aztecus data
false positive

should not have grabbed "data"

1158
Pocillopora data
false positive

should not have grabbed "data"

1293
S. pelliserpentis data
false positive

should not have grabbed "data"

1349
D. ferruginea data
false positive
fit the D. ferruginea data equally well
should not have grabbed "data"

684
N. fasciatus distribution
false positive

should not have grabbed "distribution"

972
G. clavigera distribution
false positive

should not have grabbed "distribution"

1414
Neotyphodium occultans endophyte
false positive

should not have grabbed "endophyte"

340
Arthroleptis expanded
false positive
that Arthroleptis expanded out of
should not have grabbed "expanded"

454
S. jarrovii form eight
false positive
S. jarrovii form eight basal clades
should not have grabbed "form eight"

634
R. amarus form host-specific
false positive

should not have grabbed "form host-specific"

1414
Neotyphodium fungi
false positive

should not have grabbed "fungi"

415
Drosophila genes
false positive

should not have grabbed "genes"

432
C. elegans genes
false positive

should not have grabbed "genes"

917
Oxphos genes
false positive

should not have grabbed "genes"

1441
L. cerasina genes
false positive

should not have grabbed "genes"

505
C. ignobilis genetic
false positive

should not have grabbed "genetic"

520
Y. pestis genetic
false positive

should not have grabbed "genetic"

825
D. mauritiana genetic
false positive

should not have grabbed "genetic"

825
D. sechellia genetic
false positive

should not have grabbed "genetic"

929
S. cerevisiae genetic
false positive

should not have grabbed "genetic"

929
S. paradoxus genetic
false positive

should not have grabbed "genetic"

1027
Boechera genetic
false positive

should not have grabbed "genetic"

1048
Z. mays genetic
false positive

should not have grabbed "genetic"

1093
Sorex genetic
false positive

should not have grabbed "genetic"

1310
L. amethystina genetic
false positive

should not have grabbed "genetic"

481
D. mojavensis genome
false positive

should not have grabbed "genome"

520
R. norvegicus genome
false positive

should not have grabbed "genome"

733
S. vulgaris genome
false positive

should not have grabbed "genome"

733
A. thaliana genome
false positive

should not have grabbed "genome"

825
D. sechellia genome
false positive

should not have grabbed "genome"

1234
B. mori genome
false positive

should not have grabbed "genome"

1158
S. glynni genotype
false positive

should not have grabbed "genotype"

1158
Symbiodinium genotype
false positive

should not have grabbed "genotype"

505
Caranx hybrids
false positive

should not have grabbed "hybrids"

505
C. melampygus hybrids
false positive

should not have grabbed "hybrids"

733
Senecio hybrids
false positive

should not have grabbed "hybrids"

733
Spartina hybrids
false positive

should not have grabbed "hybrids"

972
Pinus banksiana hybrids
false positive

should not have grabbed "hybrids"

972
P. banksiana hybrids
false positive

should not have grabbed "hybrids"

1005
C. porosus hybrids
false positive

should not have grabbed "hybrids"

1060
Boechera hybrids
false positive

should not have grabbed "hybrids"

1414
N. occultans hyphae
false positive

should not have grabbed "hyphae"

710
S. cerevisiae isolates
false positive

should not have grabbed "isolates"

929
S. cerevisiae isolates
false positive

should not have grabbed "isolates"

1234
B. mori larva
false positive

should not have grabbed "larva"

457
Annulipalpian larvae
false positive

should not have grabbed "larvae"

457
Integripalpian larvae
false positive

should not have grabbed "larvae"

457
Spicipalpian larvae
false positive

should not have grabbed "larvae"

1207
Drosophila melanogaster larvae
false positive

should not have grabbed "larvae"

1292
A. millepora larvae
false positive

should not have grabbed "larvae"

1316
Drosophila melanogaster larvae
false positive

should not have grabbed "larvae"

1457
H. erythrogramma larvae
false positive
H. erythrogramma larvae develop
should not have grabbed "larvae"

422
Petromarmota lineage
false positive

should not have grabbed "lineage"

432
Caenorhabditis lineage
false positive

should not have grabbed "lineage"

536
Aphelocoma lineage
false positive

should not have grabbed "lineage"

684
L. callipterus lineage
false positive

should not have grabbed "lineage"

972
G. clavigera lineage
false positive

should not have grabbed "lineage"

972
Grosmannia clavigera lineage
false positive

should not have grabbed "lineage"

536
Aphelocoma lineages plus
false positive

should not have grabbed "lineages plus"

405
Trabeculus lineages
false positive

should not have grabbed "lineages"

536
Aphelocoma lineages
false positive

should not have grabbed "lineages"

684
L. callipterus lineages
false positive

should not have grabbed "lineages"

884
Pogonomyrmex lineages
false positive

should not have grabbed "lineages"

999
P. antipodarum lineages
false positive

should not have grabbed "lineages"

1060
Boechera lineages
false positive

should not have grabbed "lineages"

1332
Rhinella margaritifera lineages
false positive

should not have grabbed "lineages"

1332
Al. femoralis lineages
false positive

should not have grabbed "lineages"

1332
Ad. heyeri lineages
false positive

should not have grabbed "lineages"

1359
Oxalis lineages
false positive

should not have grabbed "lineages"

1519
A. tumefaciens lineages
false positive
A. tumefaciens lineages compete for a
should not have grabbed "lineages"

946
X. largeni loci
false positive

should not have grabbed "loci"

366
M. edulis locus
false positive
for any M edulis locus studied
should not have grabbed "locus"

825
D. sechellia mate
false positive

should not have grabbed "mate"

340
A. sylvaticus may
false positive
While A. sylvaticus may comprise
should not have grabbed "may"

340
Arthroleptis may
false positive
within Arthroleptis may aid
should not have grabbed "may"

356
N. yunnanensis may
false positive
that N. yunnanensis may be a specie complex
should not have grabbed "may"

405
Procellaria westlandica may
false positive

should not have grabbed "may"

405
Pu. huttoni may
false positive

should not have grabbed "may"

422
Petromarmota may
false positive

should not have grabbed "may"

432
C. elegans may
false positive

should not have grabbed "may"

481
D. mojavensis may
false positive

should not have grabbed "may"

505
C. melampygus may
false positive

should not have grabbed "may"

726
A. taeniorhynchus may
false positive

should not have grabbed "may"

923
Neofelis may
false positive

should not have grabbed "may"

929
S. cerevisiae may
false positive

should not have grabbed "may"

1005
Crocodylus may
false positive

should not have grabbed "may"

1005
C. porosus may
false positive

should not have grabbed "may"

1070
Aphelocoma californica may
false positive

should not have grabbed "may"

1070
A. alexandri may
false positive

should not have grabbed "may"

1070
P. edulis may
false positive

should not have grabbed "may"

1234
B. mori may
false positive

should not have grabbed "may"

1310
L. amethystina may
false positive

should not have grabbed "may"

1371
M. arion may
false positive

should not have grabbed "may"

1398
S. alterniflora may
false positive

should not have grabbed "may"

1441
Laupala may
false positive
across Laupala may have
should not have grabbed "may"

1457
H. erythrogramma may
false positive

should not have grabbed "may"

1158
Symbiodinium may
false positive

should not have grabbed "may"- related to false negative?

1087
Rhizoglyphus means
false positive

should not have grabbed "means"

1191
Varroa mite
false positive

should not have grabbed "mite"

1076
M. strigosum origin
false positive

should not have grabbed "origin"

422
Perhaps broweri
false positive

should not have grabbed "Perhaps"

457
Wormaldia plus
false positive

should not have grabbed "plus"

700
M. huetii plus
false positive

should not have grabbed "plus"

1109
Salmo trutta pose
false positive

should not have grabbed "pose"

383
Macroscelides proboscideus sequence
false positive

should not have grabbed "sequence"

422
Marmota sequence
false positive

should not have grabbed "sequence"

438
Scaptomyza sequence
false positive

should not have grabbed "sequence"

487
Tenebrio molitor sequence
false positive

should not have grabbed "sequence"

743
Sellaphora sequence
false positive

should not have grabbed "sequence"

1480
Ap. longa sequence
false positive
an Ap. longa sequence in public
should not have grabbed "sequence"

1441
L. eukolea sire
false positive

should not have grabbed "sire"

1441
L. cerasina sire
false positive

should not have grabbed "sire"

634
A. cygnea site
false positive

should not have grabbed "site"

1332
R. dapsilis specimen
false positive

should not have grabbed "specimen"

432
C. elegans strain
false positive

should not have grabbed "strain"

432
C. briggsae strain
false positive

should not have grabbed "strain"

497
X. tropicalis strain
false positive

should not have grabbed "strain"

798
H. armigera strain
false positive

should not have grabbed "strain"

929
S. cerevisiae strain
false positive

should not have grabbed "strain"

929
S. paradoxus strain
false positive

should not have grabbed "strain"

1519
A. tumefaciens strain
false positive
A. tumefaciens strain 15955
should not have grabbed "strain"

1519
Agrobacterium tumefaciens strain
false positive
Agrobacterium tumefaciens strain 15955
should not have grabbed "strain"

514
Peromyscus studies
false positive

should not have grabbed "studies"

1457
Heliocidaris subspecies
false positive

should not have grabbed "subspecies"

1457
H. erythrogramma subspecies
false positive

should not have grabbed "subspecies"

438
Antopocerus taxa
false positive

should not have grabbed "taxa"

536
Aphelocoma taxa
false positive

should not have grabbed "taxa"

612
Vitis taxa
false positive

should not have grabbed "taxa"

1076
Melampodium taxa
false positive

should not have grabbed "taxa"

743
Aulacoseira sequence types
false positive

should not have grabbed "types"

464
Drosophila melanogaster used
false positive

should not have grabbed "used"

481
D. mojavensis used
false positive

should not have grabbed "used"

497
X. tropicalis used
false positive

should not have grabbed "used"

684
Cytb genes used
false positive

should not have grabbed "used"

1005
C. novaeguineae used
false positive

should not have grabbed "used"

1228
R. sylvatica used
false positive

should not have grabbed "used"

1044
Cameraria versus
false positive

should not have grabbed "versus"

1044
Cameraria ohridella versus
false positive

should not have grabbed "versus"

1076
M. nayaritense versus
false positive

should not have grabbed "versus"

1463
Lerista bougainvilli via
false positive

should not have grabbed "via" - table and line break problem

933
T. grallator volcano
false positive

should not have grabbed "volcano"

956
Benthic foraminifera
false positive

should not have grabbed benthic

956
For foraminifera
false positive

should not have grabbed for

313
T. hudsonicus form distinct
false positive
and T. hudsonicus form distinct genetic
grabbed too much

186
L. vilgalysii sequence
false positive

grabbing extra words

186
Lepidostroma vilgalysii specimen
false positive

grabbing extra words

252
R. antirhini complex
false positive
within the R. antirhini complex does
interpreted R. antirhini complex as name

192
Haloferax volcanii
false negative

picked up extra word

192
Haloferax volcanii strain
false positive

picked up extra word

202
Chlamydomonas used
false positive

picked up extra word

209
Aedes aegypti strain
false positive

picked up extra word

209
Sclerotinia sclerotiorum strain
false positive

picked up extra word

209
Escherichia coli strain
false positive

picked up extra word

209
C. cinerea strain
false positive

picked up extra word

209
C. cinerea young
false positive

picked up extra word

209
C. elegans larvae
false positive

picked up extra word

209
E. coli strain
false positive

picked up extra word

209
A. aegypti larvae
false positive

picked up extra word

209
A. gossypii strain
false positive

picked up extra word

215
Ostomya lineages
false positive

picked up extra word

215
Anticorbula may
false positive

picked up extra word

215
Selection??????mya arenaria
false positive

picked up extra word

215
Pachydon grade
false positive

picked up extra word

215
Pachydon may
false positive

picked up extra word

215
A. mencheri present
false positive

picked up extra word

182
Mimulus
false negative

picked up the "hybrids"

1310
T. scalpturatum complex
false positive

related to false negative? should not have   grabbed "complex"

110
Aulacoseira clade
false positive

used many times in text

110
Navicula clade
false positive

used many times in text

137
Oikopleura genome
false positive

used many times in text

I will check these words if they can be places in rejection dictionary.
https://github.com/gnames/gnfinder/issues/64

We can regect these as species epithets:
after
alliance
candidate
change
clade
clades
collection
complex
confer
coral
distinct
distribution
eight
endophyte
expanded
fungi
genes
genetic
genome
genotype
grade
haplotype
host-specific
hybrids
isolates
larva
larvae
lineage
lineages
map
origin
sequence
site
specific
specimen
strain
studies
subspecies
taxa
type
types
used

We can regect these as uninomials:
american
asiatic
both
perhaps
benthic
for
selection

These are ambiguous as species, so they can only be figured out on the verification stage.
may
data
hyphae
locus
loci
plus
mate
means
mite
pose
sire
via
versus
volcano
volcanii
young
present


Colors: Concider a blue secondary color palette

We should probably have a secondary blue color palette for our secondary button instead of using blue-900 with less opacity for hover and active.

The new palette should be more neutral.
Current blue palette:

This will not be relevant anymore since we have decided a accent and a neutral color for the Button Component


Update colors for Demo Architecture to match website theme #5360

@svrnm My apologies, I must have skipped something in the previous PR...please, kindly review it sir. Thank you

@svrnm Please, I don't understand why other people's commits are showing in my pull request, I made some changes trying to remove layouts/partials/ecosystem/registry/entry.html and when trying to commit it, it merged with other people's commit. Please, is there anything I can do to rectify it? Thank you I tried deleting the branch, reverting all changes made but it's still there

I am not 100% sure what the reason for that is, there are multiple possibilities, but here is what you might want to do:

Make a copy of your changes and move it out of the folder where you have your locally cloned repository, e.g. mv content/en/docs/demo/architecture.md ~ will move the architecture file into your home directory
Checkout the main branch once again git checkout main. You may get some errors blocking you from that, you can do git checkout main --force as well, but note that this will delete everything you worked on so make sure you have a backup
Now go to your fork on github.com (https://github.com/olamideTiana/opentelemetry.io) and make sure that your main is in sync with https://github.com/open-telemetry/opentelemetry.io. Right now it says that it is 30 commits ahead which seems odd.
When you have fixed that pull your clean main locally (git pull) and verify that the latest commit locally is the same as the one remote (git log) and what you see on top of your fork.
With this clean state, create a new PR (git checkout -b name-of-your-branch), copy the file back to where it belongs, e.g. `mv ~/architecture.md content/en/docs/demo/architecture.md), commit that change, push it and create a new PR

Hope that helps!

@svrnm Thank you. I will try that now

@svrnm Please, I don't understand why other people's commits are showing in my pull request, I made some changes trying to remove layouts/partials/ecosystem/registry/entry.html and when trying to commit it, it merged with other people's commit. Please, is there anything I can do to rectify it? Thank you I tried deleting the branch, reverting all changes made but it's still there

I am not 100% sure what the reason for that is, there are multiple possibilities, but here is what you might want to do:

Make a copy of your changes and move it out of the folder where you have your locally cloned repository, e.g. mv content/en/docs/demo/architecture.md ~ will move the architecture file into your home directory
Checkout the main branch once again git checkout main. You may get some errors blocking you from that, you can do git checkout main --force as well, but note that this will delete everything you worked on so make sure you have a backup
Now go to your fork on github.com (https://github.com/olamideTiana/opentelemetry.io) and make sure that your main is in sync with https://github.com/open-telemetry/opentelemetry.io. Right now it says that it is 30 commits ahead which seems odd.
When you have fixed that pull your clean main locally (git pull) and verify that the latest commit locally is the same as the one remote (git log) and what you see on top of your fork.
With this clean state, create a new PR (git checkout -b name-of-your-branch), copy the file back to where it belongs, e.g. `mv ~/architecture.md content/en/docs/demo/architecture.md), commit that change, push it and create a new PR

Hope that helps!

@svrnm Thank you sir, it actually worked, am I free to close this PR?


Is the comment intentional?

https://github.com/Azure/Azure-Sentinel/blob/5f7026dc3bfaa5f131076a347750e71a801da32c/Detections/ASimAuthentication/imAuthPasswordSpray.yaml#L18
@YaronFruchtmann : is the comment at this line intentional? an edit issue?

removed


Kerlink self-witnessing only clusters

Hotspot b58 Addresses
112Px38FjcobibDCYQwfZPNJ8VGpJ5oeaceNewuYXv6kT6GrWASC
11dNeUzFmfdCsHugZneixGVqd6LAKr27NEwndR3yZWt62w792Ph
11okS9tVyfx2SSwyuziPifntJfnzxxn72fScmREPi7jj8miYpPF
11oia3ZaENWRo2pmkpw3jD2eyd9cfzLHve4i8PxYd5qqjx1aJWd
11ou6s48KhnmKWFrrGaDApi1sVytGHQHpcCcKRzkKTpPpbs3zvg
11tTvfYrxhFmuurX2JdayAZN41KZa8BSrQcp1fnkH1z1kzfmBS7
11ygVf4CYQRqY1jmyQWWhnGxYjXe5NBC4Jawjp9rwq1hE97Tv6N
112uA6Q3c9axe8V8Xu8nvKbJx5HvRJxYkwWpQrsdeLdPiQdYdguP
Discord Handle
No response
Reason(s)

Self witnessing (cannot be witnessed by nearby miners which are there a few months ago)
This is a cluster of many hotspots witnessing each other only.
They only witness each other although there are PLENTY of other hotspots in the area

custom-carbon-panther (Kerlink). Address : 112Px38FjcobibDCYQwfZPNJ8VGpJ5oeaceNewuYXv6kT6GrWASC, witness for 3 days

Maker
Number of witnessed

Linxdot
1

Bobcat
14

Kerlink
5

SenseCAP
11

Heltec Automation
1

None
3

SyncroB.it
1

Nebra Ltd
4

Milesight
3

PantherX
1

Browan/MerryIoT
1

Did we need to validate all the list ?
Example:
orbiting-shadow-wasp (bobcat)
eager-blush-hippo (linxdot)
....


[Question]:  [!] Your project requires a newer version of the Kotlin Gradle plugin.                     │ │ Find the latest version on https://kotlinlang.org/docs/releases.html#release-details, then │ │ update D:\my_happy\android\build.gradle:                                                   │ │ ext.kotlin_version = ''

Please check the following before submitting a new issue.

[X] I have searched the existing issues.
[X] I have carefully read the documentation.

Please select for which platform(s) you need help

[X] Android
[ ] iOS
[ ] Linux
[ ] macOS
[ ] Web
[ ] Windows

Your question
[!] Your project requires a newer version of the Kotlin Gradle plugin.                     │
│ Find the latest version on https://kotlinlang.org/docs/releases.html#release-details, then │
│ update D:\my_happy\android\build.gradle:                                                   │
│ ext.kotlin_version = ''                                                    This issue is comming again and again in android but on ios its working fine
Version
latest   geolocator: ^12.0.0

I have this problem too

I managed to solve this problem by modifying the version number in the android/settings.gradle file
from: id "org.jetbrains.kotlin.android" version "1.7.3" apply false
to: id "org.jetbrains.kotlin.android" version "1.9.0" apply false

Thankyou! It helped a lot.


most recent Firefox nightly fails to animate cube after update

I updated FF on 11/30 to the most recent nightly. After applying changes, the sample index.html loads, the cube flashes momentarily - and then disappears. Buttons work fine, but no spinning cube. Same code shows the cube in Chrome and Edge.

cc: @caseyyee @jcarpenter

Hmm.  Seems to work for me here using 45.0a1 (2015-11-30)
Will check to see if others are experiencing similar issues.
@pindiespace are you using Mac, PC or Mobile?

I'm using Windows. I've tried the non-nightly on win and mac v. 38 and it
works fine. Possibly something to do with the nightly update itself. I did
a second update this a.m. with the same result.
On Tue, Dec 1, 2015 at 5:30 PM, Casey Yee<EMAIL_ADDRESS>wrote:

Hmm. Seems to work for me here using 45.0a1 (2015-11-30)
Will check to see if others are experiencing similar issues.
@pindiespace https://github.com/pindiespace are you using Mac, PC or
Mobile?
—
Reply to this email directly or view it on GitHub
https://github.com/borismus/webvr-boilerplate/issues/70#issuecomment-161150643
.

--
=================
Dr. Pete Markiewicz
Email<EMAIL_ADDRESS>Sustainable virtual design blog:
http://sustainablevirtualdesign.wordpress.com
Sustainability template: http://greenboilerplate.com
*Teaching site: *http://plyojump.com http://www.plyojump.com/
*Buy my book! *- Millennials and the Popular Culture
Lifecourse: http://www.lifecourse.com/store/catalog/lca/mpc.html

AmazonAuthor Page:*
http://www.amazon.com/Pete-Markiewicz/e/B0069VZ7BG/ref=ntt_athr_dp_pel_pop_2
On that page, see my DARPA Grand Challenge 2005 entry video, "Team
Robomonster":
*Team Robomonster *(DARPA 2005 Grand Challenge):
http://robotsthatjump.wordpress.com/category/team-robomonster/
*Indiespace *(1st to sell downloaded music, March 1994):
http://www.indiespace.com. Also see http://archive.org under
"Kspace.com" 1996 for our original site.
============================================================
=================

Required a complete uninstall of Nightly, Firefox, plus zapping appData AND files left over in Program Files. OK now...

@pindiespace Yikes!   Sounds like something a new profile could have fixed.   It could be that your existing/old profile could have become damaged or corrupt.    For next time, try these steps to create a new one: https://developer.mozilla.org/en-US/docs/Mozilla/Multiple_Firefox_Profiles
Sorry you had to go through that.    I did do some testing and it seemed to work fine here.


Cant parse json if an attribute have text/json.

Steps required to reproduce the problem

Use the following json and run it through: php (new Printer)->print($json, '  ')

$json = {"type": "auth-token", "error": "Server error: POST https://wsx.xxxxxxx.net/sms/send resulted in a 500 Internal Server Error response:\n{"status":106000,"description":"Unknown error","translatedDescription":null}", "queue": "auth", "token": "XXXXX", "origin": "XXXXXX", "identifier": null, "recipients": [{"email"<EMAIL_ADDRESS>"mobile": "11111111", "mobile_country_code": "0047"}], "request_ip": "x.xxx.xx.xxx", "destination": "004711111111", "consignor_id": null, "sms_error_code": null, "sms_error_description": null}
Expected Result

Valid JSON.

Actual Result

is not valid JSON.

@leitom
Can you share a - redacted - JSON file that represents what you have? Looks like the JSON copied from the issue description is invalid.

{
"type": "auth-token",
"error": "Server error: POST https://xxxxx.xxxxxx.net/sms/send resulted in a 500 Internal Server Error response:\n{"status":106000,"description":"Unknown error","translatedDescription":null}",
"queue": "auth",
"token": "XXXXX",
"origin": "foobar",
"identifier": null,
"recipients": [
{
"email"<EMAIL_ADDRESS>"mobile": "11111111",
"mobile_country_code": "0047"
}
],
"request_ip": "<IP_ADDRESS>",
"destination": "004711111111",
"consignor_id": null,
"sms_error_code": null,
"sms_error_description": null
}

Thank you, @leitom!

test.txt

I have tried to reproduce this with the following script, however I get valid JSON as output. (Both input and output are parsed by jq without issue.)
<?php
use Ergebnis\Json\Printer\Printer;
require_once __DIR__ . '/vendor/autoload.php';

$in = file_get_contents(__DIR__ . '/test.json');
$out = (new Printer)->print($in, '  ');
file_put_contents(__DIR__ . '/output.json', $out);

@leitom are you able to reproduce with this code snippet / input? I wonder what version of the library you're using. (I tested on the current HEAD which is d9e4dbb328d4ec08b3669e415cc104b20ae7f1d0.)

@fredden @leitom
I have added a test to assert that it works as expected in #683, closing for now!

Thank you, @fredden, for testing!


nix: wlroots hidpi patch broken

Basically a repeat of #1842, it appears that the recent bump of the wlroots dependency has broken the patch again:
       > applying patch /nix/store/jik866wm430p50kdvvfw3sspzsqknsmr-wlroots-hidpi.patch
       > patching file include/xwayland/xwm.h
       > Hunk #2 succeeded at 99 (offset 2 lines).
       > patching file xwayland/xwm.c
       > Hunk #1 FAILED at 19.
       > Hunk #3 succeeded at 969 (offset 3 lines).
       > Hunk #4 succeeded at 1001 (offset 3 lines).
       > Hunk #5 succeeded at 1019 (offset 3 lines).
       > Hunk #6 succeeded at 1137 (offset 3 lines).
       > Hunk #7 succeeded at 1778 (offset 3 lines).
       > Hunk #8 succeeded at 1796 (offset 3 lines).
       > Hunk #9 succeeded at 2141 (offset 3 lines).
       > 1 out of 9 hunks FAILED -- saving rejects to file xwayland/xwm.c.rej

I tried to have a look at updating the patch myself, but it isn't really documented how the patch differs from the upstream patch, but it appears to include parts that aren't upstream: https://gist.github.com/Kiskae/6f5087778206305c165c2546c6d276d5/revisions?diff=split

@fufexan for nix

What happened though, why was the version rolled back @vaxerski? https://github.com/hyprwm/Hyprland/commit/bae19cb10e0c7f972c4461d1b80b416a6db6d561.
1d64e1 is from March 20, and 5ae17de is from March 2.

whattt

should be fixed now, idk why it rolled to 5ae17de, it's at 89dcecba39d4f49b673f2fa976354c91413a4c3f now

wlroots-hyprland-hidpi-nvidia: 2023-03-20_1d64e12 → 2023-03-28_89dcecb

appears to be fixed.

Woah, it's broken again after the latest wlroots dependency update 1a5d5bf.
@fufexan any ideas?

The main issue is Nixpkgs' xwayland version was updated, and the HiDPI patch no longer applies. I'll have to figure that out first.


React dev tools

Firstly, Storybook is a great tool.
Secondly, is it possible use the React (Chrome) dev tools to inspect the components/iframe?
I think this can be enabled by adding (see https://github.com/facebook/react-devtools/issues/76) to the iframe:
if (window.parent !== window) {
  window.__REACT_DEVTOOLS_GLOBAL_HOOK__ = window.parent.__REACT_DEVTOOLS_GLOBAL_HOOK__;
}

I think we should support. Send us a PR.

Cool... I'll look into this. Official assigned! :smile:

Awesome.

I was just about to submit a PR for this yesterday. Great timing. Will submit now

Merged #104 and released as v1.11.0

is this broken in v4 I am unable to inspect inside the iframe

Yeah I've added it as suggested there and was able to select it in the devtools 🍰

I'll add it in a PR I'm working on!

thanks @ndelangen, may you link it here when ready so we know when and where it is fixed?

@ndelangen  the issue I am facing is with info @storybook/react v4.0.0-alpha.12

This is no longer working for me in Storybook 4.0.0 and 4.0.2, despite the fix. Any ideas?

I made a new issue for the inspector, the actual elements panel in devtools works fine: https://github.com/storybooks/storybook/issues/4769


where do I download ../dist/Vimeo.min.js

With the Vimeo.js file I'm getting this error also. Vimeo.js?ver=1.0.0:94Uncaught TypeError: Cannot read property 'getJSON' of undefined

seems like this file is actually located in lib/vimeo.min.js rather than dist. Also the issue with getJSON seems to be the same issue as #74, which might be an issues with the version of jquery being used or something that has yet to be determined. If you have any other questions feel free to re-open this issue


Updates to cloudflare_record resources don't work when using deprecated value field

Confirmation

[X] This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
[X] I have searched the issue tracker and my issue isn't already found.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
4.39.0 and 4.40.0 both exhibit this behaviour
Affected resource(s)
cloudflare_record
Terraform configuration files
resource "cloudflare_record" "immich_app_release_domain" {
  name = "a.update.test.example.org"
  proxied = true
  ttl = 1
  type = "CNAME"
  value = "test.example.org"
  zone_id = var.zone_id
}

Link to debug output
https://gist.github.com/zackpollard/85c3a4922e9d5221b12dcbd61749a147
Panic output
No crash
Expected output
The dns record to change in cloudflare.
Actual output
The dns record value remains unchanged, terraform completes successfully and without manual inspection you wouldn't know what had happened.
Steps to reproduce

Create resource given above
Alter resource value
Apply changes
Apply changes again and see that terraform tries to update it for a second time
Check dashboard, record is not updated.

Additional factoids
It looks like this may be fixed in main, but not yet released (link included in references). I would like to request a new provider is released ASAP. The current behavior where the value field that was the recommended method up to two releases ago, silently fails to update, is very scary. I'm surprised a bugfix version wasn't immediately released, this could be breaking production deployments all over the place without people realising what is going on.
References
https://github.com/cloudflare/terraform-provider-cloudflare/commit/e4e87a2f2601b7eb66fd96191744aa231eca0c6d

Sorry, just noticed the debug logs are from 4.39.0 as I was testing which previous versions were also affected. If you would like me to attach logs from 4.40.0 I can do that, but the bug absolutely still exists in that version.

this is already fixed by #3776 and will be released with the next mainline release based on https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/contributing/release-process.md
if you want to use the fix immediately, you can build a custom version following the docs at https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/contributing/using-non-released-versions.md

this is already fixed by #3776 and will be released with the next mainline release based on https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/contributing/release-process.md
if you want to use the fix immediately, you can build a custom version following the docs at https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/contributing/using-non-released-versions.md

Right, I'm just surprised this isn't deemed as needing a hotfix. The two latest versions out there right now won't update DNS records values if you were using the previously accepted value property. That seems like a pretty serious bug and the worst part is terraform succeeds and says the resource was updated.


Add RetryCountKey - Allow other middlewares access to what retry count we are on.

This will allow other middlewares the ability to see retry count on either the request or response depending on where the middlewares are applied.

Recommend hiding whitespace as it reformatted a bunch more than what I changed.


Add support for UICollectionView

Actual Behaviour
Currently, it is supporting normal views and UITableView.
Expected Behaviour
Add support for UICollectionView
Screenshots of the issue
N/A
Would you like to work on the issue?
Anyone can take the issue. Feel free to open the PR.

I want to help as I need this, but not sure how

@jondwillis please go ahead 🙏

@jondwillis is it still in progress ?

@majeedyaseen sorry, no. i did a quick check and must have deleted my local tweak at some point.


Proposal: Add a staticPrefix option to prefix image location

Hi there :wave:
Thanks a lot for this plugin, it's great and I really appreciate it :heart:
I am submitting this pull request as a proposal to address a use-case that I would like to see added.
I'm using this plugin in a NextJS project.
My markdown content has images in the same location as the .md file, and they are referenced like:
![Example image](example.png)

As things are now, I can instruct this plugin to drop the generated files in the public folder so they are accessible. However, the generated html will use src="example-640.png" which won't work for me (I need /example-640.png).
In addition, I'd like to put all these files in a dedicated folder under public so I can add that folder to my .gitignore file and avoid clashes with other statically served files.
This pull request implements this by adding a staticPrefix option that defaults to false.
When set to a string, it will prefix the src and also save the file in that subfolder.
If I set this to /mdx_files/ (for example), the example above:
![Example image](example.png)

Will now be rendered with src='/mdx_files/example-640.png' and the files wll be saved in public/mdx_files, which means that things just work.
I'm sure there's other ways to implement this, but I wanted to try to help by taking a stab at it :slightly_smiling_face:
I hope I was able to explain my use-case, and that you'll might want to add this option.
Thanks in advance for considering it.

Thanks for the PR. I will take a look alter and figure out why the tests where not running for this PR.
One thing I already noticed is that I think the name staticPrefix is a bit confusing. Maybe we can come up with a clearer name, eg, targetPathPrefix.

Oh yeah, naming things is hard. You do what you think is best.


📖IOTSTOOL1955: Add update campaign example

Codecov Report

Merging #418 into master will decrease coverage by 0.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #418      +/-   ##
==========================================
- Coverage   80.57%   80.36%   -0.22%
==========================================
  Files         221      221
  Lines        4639     4639
  Branches      673      673
==========================================
- Hits         3738     3728      -10
- Misses        899      909      +10
  Partials        2        2

Impacted Files
Coverage Δ

src/legacy/connect/connectApi.ts
69.67% <0%> (-2.01%)
:arrow_down:

src/common/pagination.ts
85.18% <0%> (-1.49%)
:arrow_down:

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 1e1ddbb...c335c5e. Read the comment docs.


[ios build] Could not find 'bundler' (2.1.4)

Just tried out the eas build for ios and getting the following error :

Fri, 18 Dec 2020 16:40:06 GMT
[stderr] /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'bundler' (2.1.4) required by your /usr/local/turtle-v2/src/services/worker/workingdir/build/ios/Gemfile.lock. (Gem::MissingSpecVersionError)
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] To update to the latest version installed on your system, run `bundle update --bundler`.
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] To install the missing version, run `gem install bundler:2.1.4`
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] Checked in 'GEM_PATH=/Users/expo/.gem/ruby/2.6.0:/Library/Ruby/Gems/2.6.0:/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/gems/2.6.0', execute `gem env` for more information
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/specification.rb:1449:in `block in activate_dependencies'
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/specification.rb:1438:in `each'
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/specification.rb:1438:in `activate_dependencies'
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/specification.rb:1420:in `activate'
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems.rb:304:in `block in activate_bin_path'
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems.rb:303:in `synchronize'
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] 	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems.rb:303:in `activate_bin_path'
Fri, 18 Dec 2020 16:40:06 GMT
[stderr] 	from /usr/local/bin/fastlane:23:in `<main>'
Fri, 18 Dec 2020 16:40:06 GMT
Destroying keychain - /var/folders/97/73j93h690g9gdn54bh_zskm40000gn/T/turtle-v2-3fb707aa-f557-4140-9ada-46121386e3fb.keychain
Fri, 18 Dec 2020 16:40:10 GMT
Removing provisioning profile
Fri, 18 Dec 2020 16:40:10 GMT
Xcode build logs not found
Fri, 18 Dec 2020 16:40:10 GMT
Build failed: fastlane exited with non-zero code: 1

for anyone facing this issue in the future remove fastlane Gemfile and  Gemfile.lock from your ios directory


Feature Request: Option for seriesTitle

Option for seriesTitle to update both the Localized name and the name in Kavita instead of just the localized name.
This should NOT apply to the sort names, only names and localized names.

sort name will be update along side with main title for consistency reasons
If sort name field is locked then komf will respect the lock and will not update sort name

Yes, that is what I meant, I just realized I made that unclear.
I meant to say it should not apply to series with locked sort names*


Add MCM-RB code

Done here https://github.com/qiskit-community/qiskit-device-benchmarking/pull/37.


ParquetFileFormat supports data cache

Data cache is very important for improving performance.  OapFileFormat has supported but ParquetFileFormat has not yet.  However,  ParquetFileFormat is the main file format in Baidu OAP production and the large memory machine may be introduced in future.  The design is in the following google-doc: https://docs.google.com/document/d/1FLchKxcxuQXZm3v40Fw4L6i_LuV-OMxdZRbmwmBmqdQ/edit?usp=sharing

already support


prime sender-files to retrieve the sender's file is broken.

The prime cli for getting sender's file using message_id is broken.  It needs to be look into it.
Error messages:
./prime sender-files --env prod --message-id 9e60a9c2-1cd1-440f-8de3-c6e22335429a -o ./junk/from_storage
Exception in thread "main" java.lang.StackOverflowError
at com.github.ajalt.clikt.parameters.options.FlagOption.getValue(FlagOption.kt:41)
at com.github.ajalt.clikt.parameters.options.OptionDelegate$DefaultImpls.getValue(Option.kt:91)
at com.github.ajalt.clikt.parameters.options.FlagOption.getValue(FlagOption.kt:24)
at com.github.ajalt.clikt.parameters.options.FlagOption.getValue(FlagOption.kt:24)
at gov.cdc.prime.router.cli.SenderFilesCommand.getSilent(SenderFilesCommand.kt:79)
at gov.cdc.prime.router.cli.SenderFilesCommand.echo(SenderFilesCommand.kt:219)
at gov.cdc.prime.router.cli.SenderFilesCommand.echo(SenderFilesCommand.kt:219)
at gov.cdc.prime.router.cli.SenderFilesCommand.echo(SenderFilesCommand.kt:219)

Hi @oslynn thanks for writing this ticket, please correct me if I'm wrong... is this a bug? And could you update the ticket to let us know what's the ask for this ticket? Investigate to understand the fix? Fix it if we already know the problem? Or something else? You don't have to take on the ticket, but if you could edit the problem statement and acceptance criteria, that would be very helpful. Thank you!

closing as duplicate ticket


SO-4943: rare upgrade sync revision duplication

This PR fixes a rare revision duplication issue when performing synchronization on an upgrade branch from the original branch.

Codecov Report

Merging #912 (2f5b4d0) into 8.x (fece141) will decrease coverage by 0.00%.
The diff coverage is 80.00%.

@@             Coverage Diff              @@
##                8.x     #912      +/-   ##
============================================
- Coverage     62.64%   62.64%   -0.01%
  Complexity    11642    11642
============================================
  Files          1725     1725
  Lines         55716    55716
  Branches       5297     5297
============================================
- Hits          34904    34902       -2
- Misses        18591    18593       +2
  Partials       2221     2221

Impacted Files
Coverage Δ

...b2international/index/revision/RevisionBranch.java
94.78% <ø> (ø)

...om/b2international/index/revision/StagingArea.java
93.12% <80.00%> (-0.17%)
:arrow_down:

.../b2international/index/es/client/EsClientBase.java
65.47% <0.00%> (-1.20%)
:arrow_down:

...ernational/snowowl/internal/eventbus/EventBus.java
67.82% <0.00%> (-0.50%)
:arrow_down:

.../snomed/core/ecl/SnomedEclRefinementEvaluator.java
85.67% <0.00%> (-0.28%)
:arrow_down:

...index/src/com/b2international/index/es/EsNode.java
82.29% <0.00%> (+1.04%)
:arrow_up:

...onal/snowowl/snomed/core/tree/TerminologyTree.java
87.75% <0.00%> (+2.04%)
:arrow_up:

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 fece141...2f5b4d0. Read the comment docs.


Add Nelson-Siegel-Svansson algorithm

As agreed, the Nelson-Siegel-Svansson was added and will be implemented shortly.

First version uploaded. We still need to test it and write the README file.


Add EventDispatcher

To determine if an event was triggered, we can add a simple EventDispatcher implementation

@roxblnfk, WDYT about PhpUnit mock? It allows you to determine if an event was triggered and how many time was it triggered too. You can see an example here.

@roxblnfk, WDYT about PhpUnit mock? It allows you to determine if an event was triggered and how many time it was triggered too. You can see an example here.

Interesting, of course, but I don't think this code is intuitive


Cesium stops rendering cesium 1.108

Getting this error
"
Cesium.js:22364 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘_target’)
at UniformSampler.set (Cesium.js:22364:23)
at ShaderProgram._setUniforms (Cesium.js:23287:19)
at continueDraw (Cesium.js:36008:19)
at Context.draw (Cesium.js:36072:5)
at DrawCommand.execute (Cesium.js:20250:13)
at executeCommand (Cesium.js:221224:17)
at executeCommands2 (Cesium.js:221474:11)
at executeCommandsInViewport (Cesium.js:221938:5)
at Scene4.updateAndExecuteCommands (Cesium.js:221745:7)
at Picking.pick (Cesium.js:211209:11)
at Scene4.pick (Cesium.js:222473:26)
at _callee6$ (Pools.tsx:2193:1)
at tryCatch (runtime.js:63:1)
at Generator.invoke [as _invoke] (runtime.js:293:1)
at Generator.next (runtime.js:118:1)
at asyncGeneratorStep (asyncToGenerator.js:3:1)
at _next (asyncToGenerator.js:25:1)
at asyncToGenerator.js:32:1
at new Promise ()
at asyncToGenerator.js:21:1
at onMouseMove (Pools.tsx:2179:1)
at handleMouseMove (Cesium.js:178115:7)
at handlePointerMove (Cesium.js:178504:7)
at HTMLCanvasElement.listener (Cesium.js:177861:7)
"
I have implemented clipping on google photorealistic tiles. The problem is, when I clip an area, and then on mouse hover on 3D model / extruded polygon within clipped area, viewer gets crashed… I don't know why is this happening because with cesium 1.91 everything is working fine.

Hi @ggetz,
I am having the same issue as reported in #11410 ,
My implementation a bit different in terms of adding clipping planes. I have multiple options in the UI, and user can select to clip any of the part of 3D tilesets (bind to the UI using a polygon).
But the problem is, when I switch from 1 clipping area to another, and as soon as I zoom in or out the viewer throws above error.

Got it, thanks @saadatali48. I'll close this issue to keep the discussion in #11410.


Make clean failed on ubuntu 2204

What happened:
# make clean
git checkout bpf/kmesh/bpf2go/bpf2go.go config/kmesh_marcos_def.h mk/api-v2-c.pc mk/bpf.pc bpf/kmesh/include/config.h
error: pathspec 'bpf/kmesh/include/config.h' did not match any file(s) known to git
make: *** [Makefile:157: clean] Error 1

This is introduced in #264
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Kmesh version:
Others:

@lec-bit can you take a look

Seems we have moved the file to bpf/kmesh/ads/include/config.h

/assign @Okabe-Rintarou-0

/assign

@Okabe-Rintarou-0 You can apply for kmesh memeber as well https://github.com/kmesh-net/kmesh/issues/new?assignees=&labels=&projects=&template=membership-request.md&title=REQUEST%3A+New+membership+for+<your+name>


Enable UITest Android AppCenter

Defined a new configuration called UITEST to build Android enabled for UITest on AppCenter

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


support license_links csv option

This change adds license_links to the AVAILABLE_COLUMNS for --format csv.
Background
Added in to have some parity with the --report html format (which has links to licenses) since I mainly use the csv format

Thanks for this!


fix(Geosuggest): fix input id and label for

Description
Fixes
https://github.com/ubilabs/react-geosuggest/issues/490
Right now the label and id input do not work as its explained in the documentation and also how one would probably expect (the label "for" attribute would link to the input "id" :
In the readme section :

If the label and a id prop (see "Others") were supplied, a  tag with the passed label text will be rendered. The  element's for attribute will correctly point to the id of the  element.

However what happens currently is this :

With this PR the label for and input id will match. a test was also included to insure this stays as expected in the future

Note : I do understand this could potentially break people's end to end tests which is actually how I found otu the issue myself trying to upgrade to the latest version, because this was already changed as previously the input id was the props.id directly (which is what I would expect)- This technically could be considered a breaking change, but a breaking change was already then made in https://github.com/ubilabs/react-geosuggest/pull/464 so I guess here is not really anything new.
Checklist

[x] All tests passing
[x] Created tests which fail without the change (if possible)
[x] Extended the README / documentation, if necessary
[x] Commits and PR follow conventions

Will look into these today, sorry was away for vacation but happy to continue the work here

Any chance that this gets merged? I would love to have this fix and do an update on our end ;) thanks!


Special characters

Source information
فضاء الروايات
Steps to reproduce
Open any novel in (فضاء الروايات) source and the chapters contains tons of special characters between every single paragraph making it very annoying........this didn't exist in the previous version of the app but only after I updated to the beta version of 2.0.0

Expected behavior
Only the chapters and the content of the novel should be visible
Actual behavior
Special characters
LNReader version
2.0.0
Android version
Android 11
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.1.19.
[X] I have updated all installed extensions.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Will the problem be fixed in the next update? Because I tried the source after receiving that the issue is closed in the 2.0 version and now it's just an infinite loading screen whenever I click on a novel.Sent from my Galaxy
-------- Original message --------From: nyagami @.> Date: 5/28/24  11:16 AM  (GMT+02:00) To: LNReader/lnreader-plugins @.> Cc: Mingo3347 @.>, Author @.> Subject: Re: [LNReader/lnreader-plugins] Special characters (Issue #874)
Closed #874 as completed via #920.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

ye, I think it is broken again, should be another issud

Issue submitted.Sent from my Galaxy
-------- Original message --------From: nyagami @.> Date: 5/30/24  5:14 AM  (GMT+02:00) To: LNReader/lnreader-plugins @.> Cc: Mingo3347 @.>, Author @.> Subject: Re: [LNReader/lnreader-plugins] Special characters (Issue #874)
ye, I think it is broken again, should be another issud
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Render administrative boundary on landuse areas

Administrative boundaries may sometimes coinside with landuse areas, e.g. several disjoint landuse=residential areas my form an administrative boundary of a hamlet.
If the landuse tag is defined in a line which is a member of a boundary relation then the boundary is not rendered.

But if a line is a member of a boundary relation and a landuse one then both are rendered.

If would be nice to render the boundary in the former case as well.

I'll see if this is something we can support.


Add Aries Engine

Codecov Report

Merging #234 (6a1cf4d) into master (cd3191f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #234   +/-   ##
=======================================
  Coverage   91.35%   91.35%
=======================================
  Files         128      128
  Lines       15567    15567
=======================================
  Hits        14221    14221
  Misses       1346     1346

Impacted Files
Coverage Δ

unified_planning/engines/factory.py
83.79% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@mikand Sorry for the late reply! The PR is still in the draft since unified planning requires a GRPC server based on which Aries is built. There is already a base work available at up-aries and I will submit the work upstream.

@alvalentini The planner is now available in PyPi.

@alvalentini The planner is now available in PyPi.

@franklinselva Ok, add it in the setup.py file as an extra requirement

Yes !


Does mmrazor support instance segmentation model?

Checklist

I have searched related issues but cannot get the expected help.
I have read related documents and don't know what to do.

Describe the question you meet
Does mmrazor support instance segmentation model? Such as RTMDet-ins(https://github.com/open-mmlab/mmdetection/tree/3.x/configs/rtmdet)，what do i need to pay attention to if possible, thanks.

Yes, we support segmentation models. MMRazor works as a model wrapper so that any model can be compressed with MMRazor.
We list some examples for you below.
Distillation
mmrazor/configs/distill/mmseg/cwd at main · open-mmlab/mmrazor · GitHub
Pruning
mmrazor/configs/pruning/base/group_fisher at main · open-mmlab/mmrazor · GitHub
Quantization
mmrazor/configs/quantization/ptq/base at main · open-mmlab/mmrazor · GitHub

Hi, my friends;)
would like to follow this issuese!
dose mmrazor support mmsegmentation among qat? since ptq could be implemented independendly.
If Yes, could u offer some instances? They could from mmsegmentation for sure.
many thanks!
have a nice day

Has anybody been able to apply quantization to rtmdet-ins? Any examples please?

@jslok Are you able to quantize the rtmdet-ins?


SyntaxError with strict mode

Hi, I'm trying to use vantage but when I require the lib in my code I get this error :
[...]/node_modules/vantage/lib/vantage.js:766
    function parseArgsByType(arg, cmdArg) {
    ^^^^^^^^
SyntaxError: In strict mode code, functions can only be declared at top level or immediately within another function.
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/halfman/beam.io/server.js:6:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)

Here is my environment :
$ uname -srvo
Linux 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 21:17:31 UTC 2015 GNU/Linux

$ npm --versions
{ 'beam.io': '0.0.0',
  npm: '2.11.3',
  http_parser: '2.3',
  modules: '14',
  node: '0.12.7',
  openssl: '1.0.1p',
  uv: '1.6.1',
  v8: '<IP_ADDRESS>',
  zlib: '1.2.8' }

Note : I also get the same error if I type "vantage" in console.
Thanks for your help.

Whoops - created this problem yesterday and right away pushed a fix to this in Github but didn't push to NPM.
NPM v1.3.2 has this amended. Thanks for letting me know.

Thanks :smile:

Yeah no problem.
:rocket:


Can't manually set path to pylsp per-project

Because it's common to use multiple installations of Python for different projects (either to use different Python versions, or different virtualenvs), and the recommended way to handle this with python-lsp-server is to install the server into the virtualenv itself: https://github.com/emacs-lsp/lsp-mode/issues/393#issuecomment-404949030
There doesn't seem to be a way for me to tell this plugin where to look for the pylsp binary, so the only way I can use this plugin is by making sure I have the right install for the project I want to work on in my PATH, then launching Chime by running /Applications/Chime.app/Contents/MacOS/Chime, which is… not ideal (and will probably prevent me from working on multiple Python projects at once, too).

First, thank you so much for taking the time to open this issue. This kind of feedback is sooo helpful.
This problem sounds fairly similar to what we had to do for Ruby. That extension jumps though a bunch of hoops to find the language server and also use the desired configuration. I think we can do a similar thing here. But, do get it right, I need to better understand what a good approach would be. This kind of logic is exactly what the extensions are for - the goal is to make things as smooth as possible for users so they do not need to think about it.
I saw in the linked issue someone suggest starting with something like this:
#!/bin/bash
PYLS=`pwd`/venv/bin/pyls
$PYLS $@

I'm not familiar with pyls, or python in general. Do you have any suggestions on what should be done to best locate the executable?

There's a bunch of different approaches to Python environment isolation. The most basic are "virtual environments", which are an isolated copy of Python in a user-specified directory with their own site-packages directories (which is where stuff goes when you pip install something). Then there's other tools (virtualenvwrapper, pyenv-virtualenv, pipenv, poetry, flit, ...) that typically will create a virtualenv in a predictable (but tool-specific) place, but there are plenty of people still just using ordinary virtualenvs in whatever location they please.
All that to say, I would not solely rely on autodetecting the right Python installation to use. You could write some auto detection logic to set a sensible default, but some way to manually specify a path to an executable is going to be a necessity in some cases.
Setting auto detection aside, there are two ways to have users set things up:

Tell users that they need to install the language server themselves into their virtualenv, and then let them configure a path to a pyls binary.
Have your own bundled copy of the language server, let your users specify the path to their python binary, and then prepend it to the Python module search path (so, doing the equivalent of PYTHONPATH=path/to/extension/bundled-packages path/to/user/configured/python -m pyls, which will create an environment that contains whatever packages the user has installed and the packages you bundle, with the latter taking precedence).

Most editor integrations I've seen seem to prefer the former approach, but I think there's merit to the latter: there's no extra step to getting it working on a project, the user doesn't have to add extra packages to their virtualenv that might cause dependency conflicts or other issues in other cases, and you don't have to worry as much about compatibility between the language server and the plugin because you know what version you're bundling.


Fix server selection

Task/Issue URL: https://app.asana.com/0/488551667048375/1204626421744357/f
Description
See asana task for complete description
Steps to test this PR
See asana task for test description

Current dependencies on/for this PR:

develop

PR #3170   👈

This comment was auto-generated by Graphite.


Partitions for Db2 for IBM i

Hello,
We're currently working on a project where we ingest data from a source and load them to our Azure infrastructure. We use the DBeaver Db2 for IBM i connector (using DBeaver version <IP_ADDRESS>408041519, and the default settings of the connector) to connect to the source system and validate the quality of the ingested data, as we don't have a direct access to the source system. In this type of database each table could have more than one partition (also called "member"). But, whenever querying a table, DBeaver is showing the data for the main member only. For example, the table MBM could have files MBM, FUEL, WEEK, etc., but by running a "SELECT * FROM SCHEMA.MBM", we only get the records in the MBM file, not in the FUEL, etc., files.
We know the table has more partitions that are not shown, but can be queried via system table QSYS2.SYSPARTITIONSTAT.
We do not see the additional files (members) in DBeaver, we can only see that there is more members only via SQL like this:

SELECT 'LEBPCSF' as LIBRARY, TABLE_Name as TABLE_NAME
	,TABLE_PARTITION as member_name, number_rows
FROM QSYS2.SYSPARTITIONSTAT
WHERE TABLE_SCHEMA = 'LEBPCSF' AND TABLE_NAME = 'MBM';

It would be amazing, if the partitions are visualised somewhere in DBeaver, so that we can query them, too. This way, we could pool all the data for a single table together.
Thank you

Thank you for request.


Add a Slack alarm when our WAF rate limiter is hit

Description
From #incident-2024-11-07-high-level-of-callback-failures-though-notify:
Set up a Slack notification to alert the team when the WAF rate limiter threshold is exceeded. This alert will help monitor unusual traffic or possible DDoS attempts in real time, allowing the team to respond promptly.
Acceptance Criteria:

[ ] Slack notification is triggered when the WAF rate limiter is hit.
[ ] Test the alarm by simulating rate limiter triggers

This might cause a lot of noise, especially outside of business hours.  The rate limiting is demonstrating that the system is behaving as designed and I wonder if there is a different approach that could provide an early warning sign that something is wrong with incoming traffic.
In this particular case if we actually checked the Notify reference number on the callback against known emails that our system had sent in the reliability queue we would have known something was immediately wrong.  This Sev 2 alarm would have identified a possible misuse of our API callback and the WAF Rate Limiter worked as designed by blocking further traffic.


Mobile version

At the moment, the control only available via keyboard. Would be nice if it will support mobile (phone) control via touching the screen. Just add a settings button into corner, one of settings should be "enable screen control". When it's activated, shows on the screen the control which could be used by mobiles/clicking.

Thank you for creating this ticket! I'll see what I can do!


Support mutable config for all kinds of shadowed services

Background
As EaseMesh has started to support non-java applications, the shadow service only supports java for now. So we want to expand our product to include as many features as possible for non-java services, shadow service is the next choice.
Shadow service supports changing the addresses of some middleware, for example, the process needs to change production endpoints to staging/testing ones in case of disturbing the production lines.
We inject all containers with sidecar and EaseAgent[1]. But only applications running in JVM will load and launch EaseAgent. And sidecar will notify EaseAgent of the shadowed middleware information through sidecar protocol[2].
On the other hand, there's no explicit information about whether the internal running application is a Java application or not. So we must distinguish the type of applications before passing corresponding configs.
So we can break down the things that we must do to support mutable config for all kinds of shadowed services:

We must know which type of application running (Java with EaseAgent and others such as golang, python, etc.)
After knowing the information above, we need to deliver user-defined config to shadowed services running in containers

Proposal
In the need to generalize this feature, we should expand the existing sidecar protocol for the language-insensitive guarantee.
Agent Type
There are mainly two kinds of learning agent type of applications:

Manual. User give it to use in service spec, such as:

echo 'kind: Service
metadata:
  name: service-001
spec:
  registerTenant: "tenant-001"
  agentType: EaseAgent # GoSDK, PythonSDK...
  #...

This is the simplest solution, but it actually relies on the users' awareness, which could give us the wrong information.

Automatically. We expand the sidecar protocol on the agent side for http://localhost:9900/agent-info, which returns the agent information including agent type, such as

agentType: EaseAgent # GoSDK, PythonSDK, None...
agentVersion: v2.2.1

This method would give us the real result and need no awareness from users. But it could bring complexity and make inconsistency among different service instances, which might give inconsistent agent types in some cases (although it's the responsibility of users to prevent it from happening).
So in another perspective, the manual solution is to add static service-level information, but the automatic one is to add dynamic service-instance-level information.
IMHO, the automatic one is better in the case of rigid standards.
Deliver Config
Currently, only EaseAgent can take up config(only the observability part). Besides that, we prepare to support map other configs into the application which means the container in terms of Kubernetes env.
Config categories could be these below:

Env: They could be copied, and then added, deleted, or mutated by users. (NOTICE: Some env generated by EaseStack are dedicated, which could not be copied)
ConfigMap: They would be copied into another config map(such as the name of shadow-xxx-configmap-01), and then be mutated by users.
Secret: Same as ConfigMap.

The more work for ConfigMap and Secret is the extra lifecycle management while deleting Shadow Service. An example would be
apiVersion: apps/v1
kind: Deployment
metadata:
  name: order-mesh
spec:
  template:
    spec:
      containers:
      name: order-mesh
      image: megaease/consuldemo:latest
      - env:
        - name: DEBUG
          value: false
    volumeMounts:
    - name: cm-01
      mountPath: "/etc/config-01"
    - name: secret-01
      mountPath: "/etc/secret-01"
  volumes:
  - name: cm-01
    configMap:
      name: cm-01
  - name: secret-01
    secret:
      name: secret-01

shadowed into:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: order-mesh-shadow                       # append suffix -shadow
spec:
  template:
    spec:
      containers:
      name: order-mesh
      image: megaease/consuldemo:latest
      - env:
        - name: DEBUG
          value: false                       # changed from false to true
        - name: MYSQL_ADDRESS                # add a new env
          value: mysql://<IP_ADDRESS>:13306
    volumeMounts:
    - name: cm-01
      mountPath: "/etc/config-01"
    - name: secret-01
      mountPath: "/etc/secret-01"
  volumes:
  - name: cm-01
    configMap:
      name: cm-01-order-mesh-shadow                       # append suffix -order-mesh-shadow
  - name: secret-01
    secret:
      name: secret-01-order-mesh-shadow                # append suffix -order-mesh-shadow

As we can see, the format of copies is {configmap/secret name}-{deployment/statefulset name}-shadow, which contains the content which is coped and changed by users (if they want).
The reason we add {deployment/statefulset name} into the shadowed config name is that the original configmap/secret may be shared by multiple deployments/statefulsets. As we split them totally, the cleaning of one shadow resource won't affect others. As we see, this brings a certain amount of complexity as a cost.
The added APIs would be:

Control Plane: add APIs for retrieving deployment/statefulsets specs and their Secrets and ConfigMaps.
Shadow service: adds the creation API for handling shadowing Secrets and confiConfigMapsgmap besides shadowed component.

Reference
[1] https://github.com/megaease/easeagent
[2] https://github.com/megaease/easemesh/blob/main/docs/sidecar-protocol.md

Retrieval of deployment spec exmaple:

$ curl http://<IP_ADDRESS>:32202/apis/v2/mesh/services/order-mesh/deployment
which contains 3 major fields:

app: objest, deployment spec as k8s Deployment spec.
configMaps: array, the item is k8s ConfigMap spec.
secrets: arrays, the item is k8s Secret spec.

{
  "app": {
    "metadata": {
      "name": "order-mesh",
      "namespace": "mesh-service",
      "uid": "38071fc0-19a3-4a6d-b2c4-70c8d58c5e1b",
      "resourceVersion": "11688463",
      "generation": 2,
      "creationTimestamp": "2022-07-15T13:43:38Z",
      "annotations": {
        "deployment.kubernetes.io/revision": "2",
        "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"apps/v1\",\"kind\":\"Deployment\",\"metadata\":{\"annotations\":{\"mesh.megaease.com/service-name\":\"order-mesh\"},\"name\":\"order-mesh\",\"namespace\":\"mesh-service\"},\"spec\":{\"replicas\":1,\"selector\":{\"matchLabels\":{\"app\":\"order-mesh\"}},\"template\":{\"metadata\":{\"labels\":{\"app\":\"order-mesh\"}},\"spec\":{\"containers\":[{\"env\":[{\"name\":\"SERVICE_NAME\",\"value\":\"order-mesh\"},{\"name\":\"ZIPKIN_SERVER_URL\",\"value\":\"https://dev.megaease.cn/zipkin\"}],\"image\":\"megaease/consuldemo:latest\",\"imagePullPolicy\":\"IfNotPresent\",\"name\":\"order-mesh\",\"ports\":[{\"containerPort\":80}]}]}}}}\n",
        "mesh.megaease.com/service-name": "order-mesh"
      },
      "managedFields": [
        {
          "manager": "kubectl-client-side-apply",
          "operation": "Update",
          "apiVersion": "apps/v1",
          "time": "2022-07-15T13:43:38Z",
          "fieldsType": "FieldsV1",
          "fieldsV1": {
            "f:metadata": {
              "f:annotations": {
                ".": {},
                "f:kubectl.kubernetes.io/last-applied-configuration": {},
                "f:mesh.megaease.com/service-name": {}
              }
            },
            "f:spec": {
              "f:progressDeadlineSeconds": {},
              "f:replicas": {},
              "f:revisionHistoryLimit": {},
              "f:selector": {},
              "f:strategy": {
                "f:rollingUpdate": {
                  ".": {},
                  "f:maxSurge": {},
                  "f:maxUnavailable": {}
                },
                "f:type": {}
              },
              "f:template": {
                "f:metadata": {
                  "f:labels": {
                    ".": {},
                    "f:app": {}
                  }
                },
                "f:spec": {
                  "f:containers": {
                    "k:{\"name\":\"order-mesh\"}": {
                      ".": {},
                      "f:env": {
                        ".": {},
                        "k:{\"name\":\"SERVICE_NAME\"}": {
                          ".": {},
                          "f:name": {},
                          "f:value": {}
                        },
                        "k:{\"name\":\"ZIPKIN_SERVER_URL\"}": {
                          ".": {},
                          "f:name": {},
                          "f:value": {}
                        }
                      },
                      "f:image": {},
                      "f:imagePullPolicy": {},
                      "f:name": {},
                      "f:ports": {
                        ".": {},
                        "k:{\"containerPort\":80,\"protocol\":\"TCP\"}": {
                          ".": {},
                          "f:containerPort": {},
                          "f:protocol": {}
                        }
                      },
                      "f:resources": {},
                      "f:terminationMessagePath": {},
                      "f:terminationMessagePolicy": {}
                    }
                  },
                  "f:dnsPolicy": {},
                  "f:restartPolicy": {},
                  "f:schedulerName": {},
                  "f:securityContext": {},
                  "f:terminationGracePeriodSeconds": {}
                }
              }
            }
          }
        },
        {
          "manager": "kube-controller-manager",
          "operation": "Update",
          "apiVersion": "apps/v1",
          "time": "2022-10-01T07:54:55Z",
          "fieldsType": "FieldsV1",
          "fieldsV1": {
            "f:status": {
              "f:conditions": {
                ".": {},
                "k:{\"type\":\"Available\"}": {
                  ".": {},
                  "f:type": {}
                },
                "k:{\"type\":\"Progressing\"}": {
                  ".": {},
                  "f:lastTransitionTime": {},
                  "f:status": {},
                  "f:type": {}
                }
              }
            }
          }
        },
        {
          "manager": "kubectl-edit",
          "operation": "Update",
          "apiVersion": "apps/v1",
          "time": "2022-10-01T08:38:24Z",
          "fieldsType": "FieldsV1",
          "fieldsV1": {
            "f:spec": {
              "f:template": {
                "f:spec": {
                  "f:volumes": {
                    "k:{\"name\":\"config\"}": {
                      ".": {},
                      "f:configMap": {
                        ".": {},
                        "f:defaultMode": {},
                        "f:name": {}
                      },
                      "f:name": {}
                    }
                  }
                }
              }
            }
          }
        },
        {
          "manager": "kube-controller-manager",
          "operation": "Update",
          "apiVersion": "apps/v1",
          "time": "2022-10-07T03:38:38Z",
          "fieldsType": "FieldsV1",
          "fieldsV1": {
            "f:metadata": {
              "f:annotations": {
                "f:deployment.kubernetes.io/revision": {}
              }
            },
            "f:status": {
              "f:availableReplicas": {},
              "f:conditions": {
                "k:{\"type\":\"Available\"}": {
                  "f:lastTransitionTime": {},
                  "f:lastUpdateTime": {},
                  "f:message": {},
                  "f:reason": {},
                  "f:status": {}
                },
                "k:{\"type\":\"Progressing\"}": {
                  "f:lastUpdateTime": {},
                  "f:message": {},
                  "f:reason": {}
                }
              },
              "f:observedGeneration": {},
              "f:readyReplicas": {},
              "f:replicas": {},
              "f:updatedReplicas": {}
            }
          },
          "subresource": "status"
        }
      ]
    },
    "spec": {
      "replicas": 1,
      "selector": {
        "matchLabels": {
          "app": "order-mesh"
        }
      },
      "template": {
        "metadata": {
          "creationTimestamp": null,
          "labels": {
            "app": "order-mesh"
          }
        },
        "spec": {
          "volumes": [
            {
              "name": "agent-volume",
              "emptyDir": {}
            },
            {
              "name": "sidecar-volume",
              "emptyDir": {}
            },
            {
              "name": "config",
              "configMap": {
                "name": "game-demo",
                "defaultMode": 420
              }
            }
          ],
          "initContainers": [
            {
              "name": "initializer",
              "image": "megaease/easeagent-initializer:latest",
              "command": [
                "sh",
                "-c",
                "set -e\ncp -r /easeagent-volume/* /agent-volume\n\necho 'name: order-mesh\ncluster-name: easemesh-control-plane\ncluster-role: secondary\ncluster-request-timeout: 10s\ncluster:\n  primary-listen-peer-urls: http://easemesh-control-plane-service.easemesh:2380\nlabels:\n  mesh-alive-probe: http://localhost:9900/health\n  mesh-application-port: 80\n  mesh-service-labels: \n  mesh-service-name: order-mesh\n' > /sidecar-volume/sidecar-config.yaml"
              ],
              "resources": {},
              "volumeMounts": [
                {
                  "name": "agent-volume",
                  "mountPath": "/agent-volume"
                },
                {
                  "name": "sidecar-volume",
                  "mountPath": "/sidecar-volume"
                }
              ],
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "containers": [
            {
              "name": "order-mesh",
              "image": "megaease/consuldemo:latest",
              "ports": [
                {
                  "containerPort": 80,
                  "protocol": "TCP"
                }
              ],
              "env": [
                {
                  "name": "SERVICE_NAME",
                  "value": "order-mesh"
                },
                {
                  "name": "ZIPKIN_SERVER_URL",
                  "value": "https://dev.megaease.cn/zipkin"
                },
                {
                  "name": "JAVA_TOOL_OPTIONS",
                  "value": " -javaagent:/agent-volume/easeagent.jar -Deaseagent.log.conf=/agent-volume/log4j2.xml "
                }
              ],
              "resources": {},
              "volumeMounts": [
                {
                  "name": "agent-volume",
                  "mountPath": "/agent-volume"
                }
              ],
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            },
            {
              "name": "easemesh-sidecar",
              "image": "megaease/easegress:server-sidecar",
              "command": [
                "/bin/sh",
                "-c",
                "/opt/easegress/bin/easegress-server -f /sidecar-volume/sidecar-config.yaml"
              ],
              "ports": [
                {
                  "name": "sidecar-ingress",
                  "containerPort": 13001,
                  "protocol": "TCP"
                },
                {
                  "name": "sidecar-egress",
                  "containerPort": 13002,
                  "protocol": "TCP"
                },
                {
                  "name": "sidecar-eureka",
                  "containerPort": 13009,
                  "protocol": "TCP"
                }
              ],
              "env": [
                {
                  "name": "APPLICATION_IP",
                  "valueFrom": {
                    "fieldRef": {
                      "apiVersion": "v1",
                      "fieldPath": "status.podIP"
                    }
                  }
                }
              ],
              "resources": {},
              "volumeMounts": [
                {
                  "name": "sidecar-volume",
                  "mountPath": "/sidecar-volume"
                }
              ],
              "terminationMessagePath": "/dev/termination-log",
              "terminationMessagePolicy": "File",
              "imagePullPolicy": "IfNotPresent"
            }
          ],
          "restartPolicy": "Always",
          "terminationGracePeriodSeconds": 30,
          "dnsPolicy": "ClusterFirst",
          "securityContext": {},
          "schedulerName": "default-scheduler"
        }
      },
      "strategy": {
        "type": "RollingUpdate",
        "rollingUpdate": {
          "maxUnavailable": "25%",
          "maxSurge": "25%"
        }
      },
      "revisionHistoryLimit": 10,
      "progressDeadlineSeconds": 600
    },
    "status": {
      "observedGeneration": 2,
      "replicas": 1,
      "updatedReplicas": 1,
      "readyReplicas": 1,
      "availableReplicas": 1,
      "conditions": [
        {
          "type": "Progressing",
          "status": "True",
          "lastUpdateTime": "2022-10-01T08:38:26Z",
          "lastTransitionTime": "2022-07-15T13:43:38Z",
          "reason": "NewReplicaSetAvailable",
          "message": "ReplicaSet \"order-mesh-65bb5976cc\" has successfully progressed."
        },
        {
          "type": "Available",
          "status": "True",
          "lastUpdateTime": "2022-10-07T03:38:38Z",
          "lastTransitionTime": "2022-10-07T03:38:38Z",
          "reason": "MinimumReplicasAvailable",
          "message": "Deployment has minimum availability."
        }
      ]
    }
  },
  "configMaps": [
    {
      "metadata": {
        "name": "game-demo",
        "namespace": "mesh-service",
        "uid": "6c2d970e-cfb2-4c3f-bd6b-92a6356771fb",
        "resourceVersion": "11260453",
        "creationTimestamp": "2022-10-01T08:37:41Z",
        "annotations": {
          "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"v1\",\"data\":{\"game.properties\":\"enemy.types=aliens,monsters\\nplayer.maximum-lives=5    \\n\",\"player_initial_lives\":\"3\",\"ui_properties_file_name\":\"user-interface.properties\",\"user-interface.properties\":\"color.good=purple\\ncolor.bad=yellow\\nallow.textmode=true\\n\"},\"kind\":\"ConfigMap\",\"metadata\":{\"annotations\":{},\"name\":\"game-demo\",\"namespace\":\"mesh-service\"}}\n"
        },
        "managedFields": [
          {
            "manager": "kubectl-client-side-apply",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-10-01T08:37:41Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {
              "f:data": {
                ".": {},
                "f:game.properties": {},
                "f:player_initial_lives": {},
                "f:ui_properties_file_name": {},
                "f:user-interface.properties": {}
              },
              "f:metadata": {
                "f:annotations": {
                  ".": {},
                  "f:kubectl.kubernetes.io/last-applied-configuration": {}
                }
              }
            }
          }
        ]
      },
      "data": {
        "game.properties": "enemy.types=aliens,monsters\nplayer.maximum-lives=5    \n",
        "player_initial_lives": "3",
        "ui_properties_file_name": "user-interface.properties",
        "user-interface.properties": "color.good=purple\ncolor.bad=yellow\nallow.textmode=true\n"
      }
    }
  ],
  "secrets": null
}

$ curl http://<IP_ADDRESS>:32202/apis/v2/mesh/customresources -X POST --data-binary @./ss.json
The added major fields are:

envs: users added or changed enviorments.
configMaps: all configMaps retrieved and changed.
secrets: all secrets retrieved and changed.

ss.json looks like:
{
  "kind": "ShadowService",
  "name": "shadow-001",
  "namespace": "mesh-service",
  "serviceName": "order-mesh",
  "envs": {
    "MY_ENV": "FreeMine",
    "ZIPKIN_SERVER_URL": "http://fake_addr:12030"
  },
  "configMaps": [
    {
      "apiVersion": "v1",
      "kind": "ConfigMap",
      "metadata": {
        "labels": {
          "esl-component": "nginx1",
          "esl-stackId": "easetest2-default-docker_desktop",
          "esl-stackName": "easetest2",
          "esl-version": "a4b870a2-2a4e-451b-b143-fb0f9a3bf207"
        },
        "name": "nginx1",
        "namespace": "default"
      }
    }
  ],
  "secrets": [
    {
      "apiVersion": "v1",
      "data": {
        "ca.crt": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUMvakNDQWVhZ0F3SUJBZ0lCQURBTkJna3Foa2lHOXcwQkFRc0ZBREFWTVJNd0VRWURWUVFERXdwcmRXSmwKY201bGRHVnpNQjRYRFRJeU1ERXhPVEE1TkRrd00xb1hEVE15TURFeE56QTVORGt3TTFvd0ZURVRNQkVHQTFVRQpBeE1LYTNWaVpYSnVaWFJsY3pDQ0FTSXdEUVlKS29aSWh2Y05BUUVCQlFBRGdnRVBBRENDQVFvQ2dnRUJBS1czCkdHTzE1OURtNVI0dnMyaUNsUXIxcExMd1lLK2NKc3RBT0pzbGw0eEZQYk5oTUVNYlRjSHJrazhpYnRkclVGemIKVU45WXhEN3RMTU04dWpLWnRXTldFdDMydExJNUhJTzczYTFtRUpFSnI1UG9EcG9GTHdSYWxPWXFNNG54RjI5awp1M1hJbkh6QUV2MzFyakdhQ0pBeFBuTmdLQlZrV0hNL0c2RlBxRWZpSk9WK3hiMXdKRmdkZE1UUEZrNjEyVmtnCktxR0wxRUpUNFRPSkZzS0pvSHk2M2VFblVQOUM5NitJbmZ3RmFGS3huQWdzMENnYnpMYmp1ZlBVa052a3pTU0sKLzk2elRxMkhXc05DMjlNcFhvOGs3clY0L2xYeGhuSWEzdVo1dGZsQnU1dTExVUMzcGR3VWU3ZTFkOTVYZWU0ZwpENFhkbTlFTGNBb0NhbVcvNURVQ0F3RUFBYU5aTUZjd0RnWURWUjBQQVFIL0JBUURBZ0trTUE4R0ExVWRFd0VCCi93UUZNQU1CQWY4d0hRWURWUjBPQkJZRUZNWFhjMnFGSVZsQVh5NFlXVFBSOXlLWEIzMjFNQlVHQTFVZEVRUU8KTUF5Q0NtdDFZbVZ5Ym1WMFpYTXdEUVlKS29aSWh2Y05BUUVMQlFBRGdnRUJBQ3dEb1JpQzRRMmFpZTRIK1hHQQpoL2pXOGQ0cmkrL0kzMFhNQ05VNVUvK0Nib290azBTc0JhTjBQOVYxeXBkeDZDOXg3a2FSUGRqSkJVVU1qVGJuClZiZkJKV1VVNFpwcHJHMDRXU1I3NjBYWS91Sk9VVGtKWkdURXlIbG1FMk40eGdTYVpmWUhmZU1YekV5RTdoOWEKTUNYRFE0dFViajZQejl4WTFWZTRXQnJvdldxWFN4WVUwemRGMUNrbG5qa3EwU1lQcnVJRUdDNDdENDcrNks5aQpRSjBhQWFRQ29RY01xdnVDODVUd0VqeHluQnY3NStTYnVkSEkxVk1UQzJCUGFBMWlxRHluNDF4d3hiT2d4SForCnVZdUdtUVB0cnNHYjF4QmRrZ1hXYUlUSmtJOGxHYWpmNTFTN25BWHdpeVp1SE10MS9WTXUzTG00T2tqRU1xWHIKcXNvPQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==",
        "namespace": "ZGVmYXVsdA==",
        "token": "ZXlKaGJHY2lPaUpTVXpJMU5pSXNJbXRwWkNJNkltWmpNall0Y2xoWVgxSndVRlJuVDFoTlUybDFYMnBrZFdWSlFWRnBTRzVYTWtSS01WZGhjblpUVlRRaWZRLmV5SnBjM01pT2lKcmRXSmxjbTVsZEdWekwzTmxjblpwWTJWaFkyTnZkVzUwSWl3aWEzVmlaWEp1WlhSbGN5NXBieTl6WlhKMmFXTmxZV05qYjNWdWRDOXVZVzFsYzNCaFkyVWlPaUprWldaaGRXeDBJaXdpYTNWaVpYSnVaWFJsY3k1cGJ5OXpaWEoyYVdObFlXTmpiM1Z1ZEM5elpXTnlaWFF1Ym1GdFpTSTZJbVJsWm1GMWJIUXRkRzlyWlc0dFkyUjBjbk1pTENKcmRXSmxjbTVsZEdWekxtbHZMM05sY25acFkyVmhZMk52ZFc1MEwzTmxjblpwWTJVdFlXTmpiM1Z1ZEM1dVlXMWxJam9pWkdWbVlYVnNkQ0lzSW10MVltVnlibVYwWlhNdWFXOHZjMlZ5ZG1salpXRmpZMjkxYm5RdmMyVnlkbWxqWlMxaFkyTnZkVzUwTG5WcFpDSTZJbUZrWVRFd05qWXpMVEJpWTJFdE5EYzRZeTA0TVdFMUxUazJZVE00TXpsbE1tTmhaQ0lzSW5OMVlpSTZJbk41YzNSbGJUcHpaWEoyYVdObFlXTmpiM1Z1ZERwa1pXWmhkV3gwT21SbFptRjFiSFFpZlEuYmFwY093RE5FYlhOaDM1bkdRcnlEU2tFQzh2UmdFenc0OERBNFdXMmxmSWFIN21Zb2RYWGNORS1iek9PMzZ4eldkWndtTm53ODRoYlQ1LWE5NHJtTXB1QlA2MVhucno2VzZNcUFvcmxSMWlGcmxJUFVsb3J3NWhEYS1xUlRDRlMzNDVQN2F5ZjNDM1ZueDRrYVJFYzZUbk5PWGdtNlU0RE1hQXZqbm9NTG5CSWlCVkdzUVhvUWxlREVTLUpVNEp5VUhVeWRKT2kxR244VnV4MjlXcDhtV3BiUHA0UGhOaXhaX2U2dmFjajRWNmF1N0NObm5URE82MVBvZzlDeGdPRXpxbklCZlpJLWs3bUdpQVFNT2RCZG0yWUJJSUUwZjBvTExqWnUwamtBSlk1MFpGMVNVOVZQYVo4NUprVUtLWFNieGo5cWFvUVZrcEd4Q2RsWDJsbUtR"
      },
      "kind": "Secret",
      "metadata": {
        "annotations": {
          "kubernetes.io/service-account.name": "default",
          "kubernetes.io/service-account.uid": "ada10663-0bca-478c-81a5-96a3839e2cad"
        },
        "name": "default-token-cdtrs",
        "namespace": "default"
      },
      "type": "kubernetes.io/service-account-token"
    }
  ]
}


ParagraphStyle support?

NSMutableParagraphStyle support would be great, if possible

Could you please clarify? You can set NSParagraphStyleAttributeName with paragraphStyle method:
NSMutableParagraphStyle *ps = [[NSMutableParagraphStyle alloc] init];
ps.lineBreakMode = NSLineBreakByTruncatingMiddle;
NSAttributedString *result = [@"string" makeString:^(BOStringMaker *make) {
    make.paragraphStyle(ps);
}];

Whoops, my mistake, I missed that! Sorry


Performance Improvements Using Html Minify

@mariobehling @championswimmer I was just experimenting with different npm modules and found htmlminifier interesting.
For the issue https://github.com/fossasia/open-event-webapp/issues/781
Improvements are not much its only 150kb improvement in the size of HTML file for Fossasia Zip, but the improvement can be seen on a large scale when ZIP is very large.

Current coverage is 42.58% (diff: 22.22%)

Merging #790 into development will increase coverage by 0.04%

@@           development       #790   diff @@
=============================================
  Files                6          6
  Lines              731        735     +4
  Methods             73         74     +1
  Messages             0          0
  Branches           118        118
=============================================
+ Hits               311        313     +2
- Misses             420        422     +2
  Partials             0          0

Powered by Codecov. Last update 84fea42...b245e72


infra: add ci/cd with github actions

add ci/cd with github actions

dotnet buid, test and publish
add auto ci when development branch receive new pushes

added!
#22


Failed to ensure directory

I have got an error when download a file when use FileDownloadUtils.getDefaultSaveFilePath(url) for save Path.
I added permission on manifest:
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>     <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
And i got task error status -3 on destroy notification.
Have any suggestion for fix this problem?

Sorry, I can't understand what's the problem you occurred, If -3 is the status of FileDownloadStatus, it is FileDownloadStatus#completed, what is means your download is complete successful.


Delay in actions

Hi,
I just set this up on a Doit dev kit v1, and when I press the buttons in HA the delay between the button press and the switchbot curtains actually moving is very inconsistent.
Sometimes it goes right away but it usually takes a while, I've seen it take up to 15 seconds.
Is there a way to figure out why it's that slow ? I have the board a couple of meters away from the switchbots, I can't get it any closer. Rssi is somewhere between 50 and 70 usually.
The blue LED on the board comes on when the curtains are moving, not when the button is pressed. Does that mean the delay is in mqtt or in ble ?
Thanks

Looking at the comments around the LED defines, it sounds like the blue LED comes on when it's processing a command from MQTT.
So presumably the fact that the LED is on while the curtains start moving would indicate that the link between the switchbots and the board is fine, but for some reason there's a huge delay somewhere in the chain HA -> MQTT -> ESP32.
HA and MQTT are running on a proper x86_64 server, not a pi so it's probably not just the server being slow, but is there a way to make sure ?

when the esp32 receives and starts processing the command you will see {status":"controlling"} on the main MQTT topic. This should happen basically immediately
The LED should stay on for entire duration from the time the command is received to when it was sent successfully. If the LED is not on for the full 15 seconds then the delay would seems to be from HA MQTT
you can install the MQTTExplorer app to easily watch all the mqtt traffic. The esp32 status should change to controlling right after the MQTT message is received on the 'set' topic
if you plug the esp32 into your pc you can watch the serial monitor messages by changing this value in the code printSerialOutputForDebugging = true;

Hey,
Thanks for that, tried it with the debug on and using mosquitto_sub -h <IP_ADDRESS> -p 1883 -u mqttuser -P mqttpassword -t "switchbotrelay-livingroom/#" -d to monitor the mqtt topics.
When I click on the button in home assisstant, I can see the mqtt message imediatly :
Client mosq/Kutw5gau7ld3sge6bv received PUBLISH (d0, q0, r0, m0, 'switchbotrelay-livingroom/esp32/curtain/main-door/set', ... (5 bytes))

But the esp32's logs nothing at that time. Maybe 10 seconds later, the esp32 logged the command and the switchbot immediatly started moving.
So I guess the issue is between MQTT and the esp32, any ideas why it sometimes doesn't get the message right away ?
It's got decent signal, according to the unifi controller the experience is 75% whatever that means, and HA reports the esp's rssi at around -65.

Correction, it seems fixed now. I just created a separate user for HA and for the ESP32 and reconfigured home assistant, not sure which of these two actions solved the issue but it just works now. I wonder if sharing a user was causing it ?
Anyway I'll keep a close eye on it for a day or two and if the issue doesn't return I'll close it, seems like it was my setup indeed.
Thanks !

Still working perfectly fine, must have been the shared user.
Closing it then, thanks !


Add visual marker for Packages

ScanCode collects packages and they are a natural break and summarization point where I want to focus my review first and eventually create a component at that level.
As a start, I would like to have a visual indication that a node is a package (as reported by ScanCode as being a package)

I want to work on this issue.  I have successfully deployed the app locally. Can you guide me on how I should start?

@pombredanne Yes, it does! I will go through the files to figure out ways to implement this. Would you be available if I have a doubt or get stuck?
Thanks in advance.

we will sure be available. Feel free to submit a pull request early even if this is work in progress ass it will make the review by @jdaguil much easier.

@pombredanne Okay sure. I will try to understand the underlying working of the app and start working on this issue as soon as possible.

@Rishav159 Do not hesitate to ask questions here :) Small code changes one at a time are always easier to review and swallow...

@pombredanne Thanks for this kind of support! I am really glad.
Okay so as I can understand till now, the app takes in a JSON file generated by the scancode-toolkit as input and shows it in different views. Trying to understand the JSON file, It contains a key 'files' with an array of information of the all the files/directory in the folder.
Now how do I identify a package node? Is it related to the 'packages' key ? The given sample JSON does not have any package maybe ?
Thanks

@Rishav159 to get some packages scanned, download a few RPMs and npms in a directory and scan the directory with scancode --package --license --copyright .... You will see detected packages as an array under the "packages": []

@pombredanne Okay. I will try that.

@pombredanne I have added a (P) identifier at the end of the files that include packages.
You can find the changes here
Should I create a pull request?

@Rishav159 Thanks! and yes , please create a PR. These are best for review

@pombredanne Okay I will create a PR. I have only updated the node view for now. Updating the tree view is a little confusing as I have no experience with the Jstree. I will trying digging deep into it.

@pombredanne I have changed the identifier to make the text-background color of filenames to green for files which has packages. Creating a new PR. Please review.

merged #309, closing this.