Runtime Error ctorParameters.map is not a function

I'm submitting a
[ ] bug report => check the FAQ and search github for a similar issue or PR before submitting
[x] support request => check the FAQ and search github for a similar issue before submitting
[ ] feature request

Current behavior
I'm trying to use this component with ionic 2 but is not working, I'm getting this error:
"Runtime Error ctorParameters.map is not a function"
Stack
TypeError: ctorParameters.map is not a function
    at ReflectionCapabilities.parameters (/Users/ernaneluis/Developer/schild/SchildApp/node_modules/@angular/core/src/reflection/reflection_capabilities.js:61:45)
    at Reflector.parameters (/Users/ernaneluis/Developer/schild/SchildApp/node_modules/@angular/core/src/reflection/reflector.js:29:44)
    at CompileMetadataResolver.getDependenciesMetadata (/Users/ernaneluis/Developer/schild/SchildApp/node_modules/@angular/compiler/src/metadata_resolver.js:449:54)
    at CompileMetadataResolver.getTypeMetadata (/Users/ernaneluis/Developer/schild/SchildApp/node_modules/@angular/compiler/src/metadata_resolver.js:414:26)
    at eval (/Users/ernaneluis/Developer/schild/SchildApp/node_modules/@angular/compiler/src/metadata_resolver.js:557:41)
    at Array.forEach (native)
    at CompileMetadataResolver.getProvidersMetadata (/Users/ernaneluis/Developer/schild/SchildApp/node_modules/@angular/compiler/src/metadata_resolver.js:537:19)
    at eval (/Users/ernaneluis/Developer/schild/SchildApp/node_modules/@angular/compiler/src/metadata_resolver.js:235:71)
    at Array.forEach (native)
    at CompileMetadataResolver.getNgModuleMetadata (/Users/ernaneluis/Developer/schild/SchildApp/node_modules/@angular/compiler/src/metadata_resolver.js:226:44)

Reproduction of the problem
at app.module.ts
in @NgModule
when I try to add this
TranslateModule.forRoot()
or
  TranslateModule.forRoot({
        provide: TranslateLoader,
        useFactory: (createTranslateLoader),
        deps: [Http]
      })

in imports then I get that error.
My environment:
Ionic Framework: 2.0.0-rc.3
Ionic Native: 2.2.3
Ionic App Scripts: 0.0.46
Angular Core: 2.1.1
Angular Compiler CLI: 2.1.1
Node: 7.2.0
OS Platform: macOS Sierra
Navigator Platform: MacIntel
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 OPR/42.0.2393.94

I am also stuck with this issue.

Hello,
I think you have to upgrade your dependencies to use ng2-translate 5.0.0.
My environment is working with:
Ionic Framework: 2.0.0-rc.4
Angular Core: 2.2.1
Angular Compiler CLI: 2.2.1

I'm still getting the same error :( , even with this env:
Ionic Framework: 2.0.0-rc.4
Ionic Native: 2.2.11
Ionic App Scripts: 0.0.48
Angular Core: 2.2.1
Angular Compiler CLI: 2.2.1
Node: 7.2.0
OS Platform: macOS Sierra
Navigator Platform: MacIntel
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 OPR/42.0.2393.94

I fix this issue by running:
npm install
I have forgotten to do this.

I found it in compiled code { TranslateModule.ctorParameters = function () { return []; }; }, and i compare to @ngrx/store { StoreModule.ctorParameters = []; }.

This is a outdated angularJS issue, I had it when I was using an older version of AngularJS, but updating to the latest version made some other libraries fail, so I had to find a sweet spot.
For me, that was AngularJS version 2.2.1
You can update your package.json as so, so running npm install will install the required libraries.

"@angular/common": "~2.2.1",
"@angular/compiler": "~2.2.1",
"@angular/core": "~2.2.1",
"@angular/forms": "~2.2.1",
"@angular/http": "~2.2.1",
"@angular/platform-browser": "~2.2.1",
"@angular/platform-browser-dynamic": "~2.2.1",
"@angular/router": "~3.1.0",

I've found that this issue is caused by any number of packages expecting the version of Angular Core to be different than what is actually installed.
I was able to figure out the cause of this issue by looking at the error report from ng build:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
This helped me realize that one of my packages expected Angular to be at v2.4.4, but I'm using v2.0.1. I updated my package.json to have both packages set to my core version like this:
"dependencies": {     "@angular/core": "2.0.1",     "@angular/platform-server": "2.0.1", }
Your issue might not be with @angular/platform-server, but I hope this helps debug it

Closing this, let me know if you need it to be reopened.


Adding GroupBy and Aggregate

Not sure how the old commits came up with this :/ (those were already merged)
Also, Groupby operation needs to be added without an aggregation operation.
This need to be implemented in CPP side. Since that is not available.
The Python API capability is limited when providing an API like Pandas groupby.

@vibhatha coming to think of the aggre

sorry I mistakenly closed this PR! :grin:

Also reminding this: Groupby operation needs to be added without an aggregation operation.
This need to be implemented in CPP side. Since that is not available.
The Python API capability is limited when providing an API like Pandas groupby.
We may need to change how we do GroupBy and return an intermediate output. I think that is needed.

Also reminding this: Groupby operation needs to be added without an aggregation operation.
This need to be implemented in CPP side. Since that is not available.
The Python API capability is limited when providing an API like Pandas groupby.
We may need to change how we do GroupBy and return an intermediate output. I think that is needed.

I agree. Like I said previously, what pandas groupby returns is the indices of each group, and then we can apply an aggregation on each group. That is not so efficient for distributed operations because we would have to do a shuffle to get all the index rows in one place.


[DOCKER] Fix: install script regarding get-pip.py during docker build

Replaced the URL of get-pip.py from
https://bootstrap.pypa.io/get-pip.py
to
https://bootstrap.pypa.io/2.7/get-pip.py
, as the old one doesn't support python 2.7 any more and triggers below error during the building of Dockerfile.demo_android.

ERROR: This script does not work on Python 2.7 The minimum supported Python version is 3.6.

Other than this, the whole docker building procedure works OK.
@leandron Could you please help to review? Thanks.

we have dropped the support for python2.7 in the current mainline, so let us consider remove the python2 setup of pip instead. Thank you @brianlan

we have dropped the support for python2.7 in the current mainline, so let us consider remove the python2 setup of pip instead. Thank you @brianlan

Thanks @leandron, @tqchen. Will remove python2 setup and test again.

Removed get-pip.py for python2. I rerun the whole docker build process, it works fine.  @tqchen

Thanks @brianlan @leandron !


adding question for localStorage

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Successfully committed all the required changes.


When cache is updated, diagnostics aren't recomputed in time

Reported by NeunEinser

:tada: This issue has been resolved in version 3.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature request

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

@Pthannh thanks for submitting the issue, but I'm completely unsure what you're asking, since this is just the template :)
Please provide more details or I'm just going to close this with no action. Thanks!


update is no progress

the update is no progress, i can not know this is ok.

i update 20 minutes
i wait for this

Looks like a network issue. Try run it again later?
If the problem has not been solved, try if git clone github.com/lukesampson/scoop/ works. (remember to test this in a directory other than C:\Users\xxx)
If git clone github.com/lukesampson/scoop/ does not work, your connection may be blocked by firewall rules or your ISP. You can use a proxy to solve the problem.


Docker build error

I'm trying to build a new image using the dockerfile provided, but i'm getting following error.
ERROR: failed to solve: process "/bin/sh -c echo "Downloading Cambria font collection..."     && wget --quiet -O PowerPointViewer.exe http://downloads.sourceforge.net/mscorefonts2/PowerPointViewer.exe     && cabextract --lowercase -F 'ppviewer.cab' PowerPointViewer.exe     && cabextract --lowercase -F '*.ttc' --directory=/usr/share/fonts/msttcore ppviewer.cab     && rm -f PowerPointViewer.exe ppviewer.cab" did not complete successfully: exit code: 7
Is it possible that the PowerPointViewer.exe isn't available anymore on that link. Or is there another issue ?

Hi, we have not been able to reproduce this issue. Is this still occurring for you?

We're seeing the same error on our CI environment, but can't reproduce on a local machine either.
Removing the --quiet flag from the wget to see what's going on:
#10 [ 6/16] RUN wget -O PowerPointViewer.exe http://downloads.sourceforge.net/mscorefonts2/PowerPointViewer.exe
#10 0.890 Failed to read 102400 bytes (hostname='unlimited.dl.sourceforge.net', ip=xxx.xxx.xxx.xxx, errno=104)
#10 0.890 Failed to read -1 bytes (104) (http://unlimited.dl.sourceforge.net/project/mscorefonts2/cabs/PowerPointViewer.exe?viasf=1)
#10 0.890 Just got 593431 of 27024112 bytes (http://unlimited.dl.sourceforge.net/project/mscorefonts2/cabs/PowerPointViewer.exe?viasf=1)

RUN wget -O PowerPointViewer.exe http://downloads.sourceforge.net/mscorefonts2/PowerPointViewer.exe:
196.5 HTTP response 200 OK [http://unlimited.dl.sourceforge.net/project/mscorefonts2/cabs/PowerPointViewer.exe?viasf=1]
196.5 Unexpected body length 593431.

Problem was caused by Palo Alto XDR blocking the download.


-1 precision and F1 for ConLL data

Hi,
I'm unable to reproduce results for ConLL2003 NER data.
I even tried converting my data from BIO-BIOES using your script. Please help me understand what I've done wrong.
Below is the log with BIOES train:
Seed num: 42
MODEL: train
Load pretrained word embedding, norm: False, dir: ../data/glove.6B/glove.6B.100d.txt
Embedding:
pretrain word:400000, prefect match:3, case_match:0, oov:1, oov%:0.2
Training model...
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
DATA SUMMARY START:
I/O:
Start   Sequence   Laebling   task...
Tag          scheme: BMES
Split         token:  |||
MAX SENTENCE LENGTH: 250
MAX   WORD   LENGTH: -1
Number   normalized: True
Word  alphabet size: 5
Char  alphabet size: 3
Label alphabet size: 18
Word embedding  dir: ../data/glove.6B/glove.6B.100d.txt
Char embedding  dir: None
Word embedding size: 100
Char embedding size: 30
Norm   word     emb: False
Norm   char     emb: False
Train  file directory: ../data/modified_data/eng.train.bioes
Dev    file directory: ../data/modified_data/eng.testa.bioes
Test   file directory: ../data/modified_data/eng.testb.bioes
Raw    file directory: None
Dset   file directory: None
Model  file directory: ../data/charcnnwordlstmcrftestbioes
Loadmodel   directory: None
Decode file directory: None
Train instance number: 14986
Dev   instance number: 3465
Test  instance number: 3683
Raw   instance number: 0
FEATURE num: 0
++++++++++++++++++++++++++++++++++++++++
Model Network:
Model        use_crf: True
Model word extractor: LSTM
Model       use_char: True
Model char extractor: CNN
Model char_hidden_dim: 50
++++++++++++++++++++++++++++++++++++++++
Training:
Optimizer: SGD
Iteration: 100
BatchSize: 10
Average  batch   loss: True
++++++++++++++++++++++++++++++++++++++++
Hyperparameters:
Hyper              lr: 0.015
Hyper        lr_decay: 0.05
Hyper         HP_clip: None
Hyper        momentum: 0.0
Hyper              l2: 1e-08
Hyper      hidden_dim: 200
Hyper         dropout: 0.5
Hyper      lstm_layer: 1
Hyper          bilstm: True
Hyper             GPU: True
DATA SUMMARY END.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
build sequence labeling network...
use_char:  True
char feature extractor:  CNN
word feature extractor:  LSTM
use crf:  True
build word sequence feature extractor: LSTM...
build word representation...
build char sequence feature extractor: CNN ...
build CRF...
 Time: 164.08s, speed: 91.33st/s,  total loss: 14623.973976135254
totalloss: 14623.973976135254
Right token =  42974  All token =  51577  acc =  0.8332008453380383
Dev: time: 6.14s, speed: 565.80st/s; acc: 0.8332, p: -1.0000, r: 0.0000, f: -1.0000
Exceed previous best f score: -10
Save current best model in file: ../data/charcnnwordlstmcrftestbioes.0.model
Right token =  38553  All token =  46665  acc =  0.8261652201864352
Test: time: 5.83s, speed: 635.29st/s; acc: 0.8262, p: -1.0000, r: 0.0000, f: -1.0000
Epoch: 1/100
Learning rate is set as: 0.014285714285714285
Shuffle: first input word list: [2, 2]
Instance: 500; Time: 5.08s; loss: 431.2016; acc: 5391/6521=0.8267
Instance: 1000; Time: 5.47s; loss: 439.1820; acc: 10921/13222=0.8260
Instance: 1500; Time: 5.50s; loss: 423.6805; acc: 16460/19866=0.8286
Instance: 2000; Time: 5.46s; loss: 425.2254; acc: 22446/26950=0.8329
Instance: 2500; Time: 5.90s; loss: 435.6300; acc: 28570/34178=0.8359
Instance: 3000; Time: 5.35s; loss: 444.1788; acc: 34283/41039=0.8354
Instance: 3500; Time: 5.36s; loss: 430.6110; acc: 39931/47798=0.8354
Instance: 4000; Time: 5.26s; loss: 431.6148; acc: 45356/54376=0.8341
Instance: 4500; Time: 5.55s; loss: 450.8224; acc: 51271/61468=0.8341
Instance: 5000; Time: 5.46s; loss: 429.3036; acc: 57317/68630=0.8352
Instance: 5500; Time: 5.60s; loss: 449.7797; acc: 63241/75743=0.8349
Instance: 6000; Time: 5.27s; loss: 433.6448; acc: 68693/82380=0.8339
Instance: 6500; Time: 5.71s; loss: 456.3143; acc: 74874/89753=0.8342
Instance: 7000; Time: 5.25s; loss: 436.8700; acc: 80510/96573=0.8337
Instance: 7500; Time: 5.63s; loss: 430.2619; acc: 86279/103481=0.8338
Instance: 8000; Time: 5.72s; loss: 412.8583; acc: 92142/110434=0.8344
Instance: 8500; Time: 5.54s; loss: 398.9669; acc: 97755/117099=0.8348
Instance: 9000; Time: 5.58s; loss: 401.6885; acc: 103315/123734=0.8350
Instance: 9500; Time: 5.71s; loss: 401.0224; acc: 109076/130581=0.8353
Instance: 10000; Time: 5.61s; loss: 436.5150; acc: 114616/137309=0.8347
Instance: 10500; Time: 5.47s; loss: 422.0465; acc: 120169/144025=0.8344
Instance: 11000; Time: 5.45s; loss: 392.8255; acc: 125509/150463=0.8342
Instance: 11500; Time: 5.66s; loss: 430.9805; acc: 131225/157359=0.8339
Instance: 12000; Time: 5.81s; loss: 429.5823; acc: 137266/164574=0.8341
Instance: 12500; Time: 5.47s; loss: 409.2201; acc: 143011/171457=0.8341
Instance: 13000; Time: 5.26s; loss: 393.7457; acc: 148514/178056=0.8341
Instance: 13500; Time: 5.70s; loss: 444.4959; acc: 154245/184981=0.8338
Instance: 14000; Time: 5.38s; loss: 411.1087; acc: 159572/191452=0.8335
Instance: 14500; Time: 5.20s; loss: 397.2859; acc: 165118/198095=0.8335
Instance: 14986; Time: 5.40s; loss: 389.1057; acc: 170523/204566=0.8336
Epoch: 1 training finished. Time: 164.81s, speed: 90.93st/s,  total loss: 12719.768818855286
totalloss: 12719.768818855286
Right token =  42974  All token =  51577  acc =  0.8332008453380383
Dev: time: 6.16s, speed: 564.23st/s; acc: 0.8332, p: -1.0000, r: 0.0000, f: -1.0000
Right token =  38553  All token =  46665  acc =  0.8261652201864352
Test: time: 5.80s, speed: 638.96st/s; acc: 0.8262, p: -1.0000, r: 0.0000, f: -1.0000
Epoch: 2/100
Learning rate is set as: 0.013636363636363634
Shuffle: first input word list: [2, 2, 2, 2, 2, 2, 2, 2, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3]
Instance: 500; Time: 5.41s; loss: 436.1395; acc: 5824/7012=0.8306
Instance: 1000; Time: 5.48s; loss: 385.2749; acc: 11357/13599=0.8351
Instance: 1500; Time: 5.53s; loss: 415.0793; acc: 17094/20450=0.8359
Instance: 2000; Time: 5.55s; loss: 413.8247; acc: 22636/27161=0.8334
Instance: 2500; Time: 5.40s; loss: 420.5595; acc: 28451/34152=0.8331
Instance: 3000; Time: 5.18s; loss: 362.7070; acc: 33769/40470=0.8344
Instance: 3500; Time: 5.71s; loss: 408.6057; acc: 39442/47317=0.8336
Instance: 4000; Time: 5.42s; loss: 415.7353; acc: 45278/54329=0.8334
Instance: 4500; Time: 5.26s; loss: 390.8038; acc: 50917/61030=0.8343
Instance: 5000; Time: 5.49s; loss: 410.7181; acc: 56446/67705=0.8337
Instance: 5500; Time: 5.55s; loss: 417.0718; acc: 62245/74659=0.8337
Instance: 6000; Time: 5.48s; loss: 416.0790; acc: 68118/81681=0.8340
Instance: 6500; Time: 5.19s; loss: 404.0871; acc: 73511/88224=0.8332
Instance: 7000; Time: 5.23s; loss: 430.6882; acc: 79219/95148=0.8326
Instance: 7500; Time: 5.26s; loss: 414.4986; acc: 84977/102097=0.8323
Instance: 8000; Time: 5.44s; loss: 372.8214; acc: 90537/108671=0.8331
Instance: 8500; Time: 5.29s; loss: 376.0572; acc: 95977/115146=0.8335
Instance: 9000; Time: 5.74s; loss: 393.9897; acc: 101715/122009=0.8337
Instance: 9500; Time: 5.60s; loss: 444.6560; acc: 107654/129181=0.8334
Instance: 10000; Time: 5.45s; loss: 422.0748; acc: 113211/135972=0.8326
Instance: 10500; Time: 5.55s; loss: 415.9887; acc: 118967/142896=0.8325
Instance: 11000; Time: 5.37s; loss: 392.2800; acc: 124211/149289=0.8320
Instance: 11500; Time: 5.67s; loss: 405.8225; acc: 130222/156428=0.8325
Instance: 12000; Time: 5.65s; loss: 414.1149; acc: 136121/163498=0.8326
Instance: 12500; Time: 5.58s; loss: 410.7859; acc: 141971/170495=0.8327
Instance: 13000; Time: 5.44s; loss: 406.8974; acc: 147548/177214=0.8326
Instance: 13500; Time: 5.27s; loss: 398.6541; acc: 153373/184149=0.8329
Instance: 14000; Time: 5.46s; loss: 404.1680; acc: 159096/190973=0.8331
Instance: 14500; Time: 5.27s; loss: 383.6540; acc: 165023/197968=0.8336
Instance: 14986; Time: 5.25s; loss: 397.4585; acc: 170523/204566=0.8336
Epoch: 2 training finished.      Time: 163.63s, speed: 91.58st/s,  total loss: 11517.950781226158
totalloss: 11517.950781226158
Right token =  42974  All token =  51577  acc =  0.8332008453380383
Dev: time: 6.18s, speed: 563.97st/s; acc: 0.8332, p: -1.0000, r: 0.0000, f: -1.0000
Right token =  38553  All token =  46665  acc =  0.8261652201864352
Test: time: 5.90s, speed: 627.84st/s; acc: 0.8262, p: -1.0000, r: 0.0000, f: -1.0000

Your Word alphabet size: 5 is only 5, I am sure this is because of your data format is incorrect. Please check your data format should be the same as https://github.com/jiesutd/NCRFpp/blob/master/sample_data/train.bmes

Thank you for the quick response! I was able to find my issue from this.
My BIO dataset had word id as the first column.


adjust pg_regress to address invalid encoding issue on uos system

fix #482

An issue encountered within test framework pg_regress, specifically related to character encoding handling on the UOS1050a/1060e systems.
pg_regress invokes psql to execute SQL scripts, during dispatch_encoding test case test,  an error "invalid byte sequence for encoding 'UTF8': 0xba" encountered when create a table with Russian. This indicates that the system, potentially UOS, was unable to correctly identify certain character sequences as valid UTF-8 encoding, typically pointing to an operating system level bug.
To circumvent this bug, the invocation method of the testing framework was altered. Originally, the call used redirection and heredoc syntax "<<EOF" to pass the SQL script to psql.
' "/usr/local/cloudberry-db-devel/bin/psql" -X -a -q -d "regression" -v HIDE_TABLEAM=on -v HIDE_TOAST_COMPRESSION=on > "/code/cbdb_src/src/test/regress/results/dispatch_encoding.out" 2>&1 <<EOF
$(cat "prehook.sql" "/code/cbdb_src/src/test/regress/sql/dispatch_encoding.sql")
EOF'

The revised approach utilized process substitution <(...) which feeds output of a command to psql. The modified command like this:
"/usr/local/cloudberry-db-devel/bin/psql" \
-X -a -q -d "regression" \
-v HIDE_TABLEAM=on -v HIDE_TOAST_COMPRESSION=on \
< <(cat "prehook.sql" "/code/cbdb_src/src/test/regress/sql/dispatch_encoding.sql") \
> "/code/cbdb_src/src/test/regress/results/dispatch_encoding.out"

By doing so, the original error ceased to occur, allowing the tests to proceed. This could be because process substitution altered the data flow in a way that bypassed the triggering of the operating system-level bug.
In the output of the DDL, gibberish characters such as "ÐºÐ¾Ð»Ð¾Ð½ÐºÐ°" appear, indicative of incorrect UTF-8 encoding, likely due to mishandling by the system when dealing with these special characters. The revised invocation of the testing framework successfully avoided this issue, enabling the tests to run without being hampered by encoding errors.

In certain case,  it failed with the following error.  Will look into and fix it.
 /bin/sh: -c: line 0: syntax error near unexpected token `<'

cancel this PR as Hao Wu has another fix on this issue.


[Feature Request] for Pull Request, Resolve Conflicts via WEB

this is part of #5158 summary ... and could be an addition of #9013

https://stackoverflow.com/a/6283843
this solution prints out the merge wich can be also displaied in our web editor to resolve this ... ?

I'm new to gitea, but it looks like this button (under GitHub)

has no equivalent under gitea and I must solve PR manually ?
Thanks

@UBowt571 until now ... yes :/

+1

Is there someone already working on it ?
I think about trying to implement it (I'm a noob and this would be my very first fork) but I don't want to do the same work as someone else did

@UBowt571 All contributions are welcome! 😄

I'll try to have a go at this other the next week.

+1

@richmahn Ho, go ahead, I surrendered (normal as a French guy lol) and switched to self-hosted gitlab instead

@maskym Haha. Loved the French joke. I've been working on Gitea and with Go since 2016, even the one who added the original web interface for editing files, so I should be able to do it. Thanks for the update!

We are investigating if Geany would be a viable alternative for the huge Gitlab installation we have running now, and the only real blocker we are seeing now is the lack of conflict resolving withing the webinterface. This was mentioned in #14477 but lost traction and it never reached the 1.16 milestone.
@richmahn do you have any plans on implementing this? I have zero experience in coding for Gitea or Go, so I can't be of any help.

@MrHaroldA Totally forgot I even mentioned I would work on this. Will put it on my todo list and see if I can take a stab at it in the coming week.

@richmahn Still wish I had this feature sometimes for productivity sake 😆 By now, I had to learn git more in detail, can you imagine?

I have a PR that now says 2 files are in conflic with the recieving repo., but i still see now way to resolve this...  How in earths name can I now fix this? Local repo says everything is fine. Won't let me delete the PR either.

@richmahn any news on this?

@ktpx that's off topic ... but: merge target branch locally or rebase and push

@eUgEntOptIc44 Sadly haven't had time to work on it, but have mentioned it to my team how badly it is needed. Hopefully can look at it soon, or if someone else wants to get this done, let me know. Should we do it exactly like Github does it, or have some extra functionality to making merging easier?

@richmahn thank you for your update on this. I'd like to directly support on this by contributing code. Unfortunately my knowledge of go is very limited. However I hope that you or someone else might be able to do so.

@richmahn @eUgEntOptIc44 I am also interested in contributing to this feature that would be extremely helpful for my team's needs as well.
I would also mention that the way Github handles merge conflict would be a great baseline for an initial implementation.
Please let me know if available for collaboration on this much needed feature.

I'm not aware of any draft so I would say go on and it is yours ;)
If you need help just ask.
for the UI side I would have a look if it can be done in vue ...
example:  #19650 ...

@jayczech23 I'm still needing this and keep playing around with getting this implemented like Github. Can we collaborate together?

@jayczech23 Are you on the Gitea Discord server? If we could touch base there I would be far more likely to get to work on this and better communication since I do everything with Discord. https://discord.gg/mPWThBne

@richmahn sounds great. I will sign up on the Gitea Discord and send you a message.
Thanks!

Would love to get an occasional update on this or even help out. I am on the Gitea Discord as well and tagged you @richmahn

@jayczech23 @Alexander-Zierhut Ok, now I'm more clear on you both wanting to help. Awesome. I won't let this drop now. Would be a cool hack-a-thon. My work pays me to work on Gitea, but usually working on our own fork of it and then I merge in from upstream (Gitea). I have many coworkers who use our copy of Gitea for editing text files (content) rather than code.
A few things we need to figure out is first of all, I often get told when making a PR in Gitea that there is a conflict, due to different lines being edited, I think 2 apart, so the line between them still remains the same. This for some reason makes Gitea think there is a conflict. Yet if I merge master/main into the conflicting branch, it merges with no problem. That's one thing we need to solve....stop Gitea from declaring such a conflict (if it still is happening) as it is confusing.
Next is we need to mark up what a conflict editor UI should look like. Should it be just like Github, or something better?

@jayczech23 @Alexander-Zierhut I have added you to a Github test repo so we can see how Github does it, mock up the Gitea, and implement all the different paths a user might take:
Accept the collaboration and see this PR:
https://github.com/richmahn/test/pull/3

Here's a PR where the file was modified in base branch but deleted in the head branch. Github just says it is too complicated and says to deal with it on your computer. Wonder if there is a way we could deal with it in the UI?
https://github.com/richmahn/test/pull/4

Ditto with a binary file: https://github.com/richmahn/test/pull/5

Large file with conflicts: https://github.com/richmahn/test/pull/6/conflicts

If we make it exactly like Github we can then just copy their help pages:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
(Maybe the last one Gitea already has?)

So basically the base branch is being merged into the head branch to get the conflicts and the diff and then when the user submits the changes it updates with head branch with the base branch and fixes the conflicts. I wonder what the caveats are in doing this, such as as what if either branches are edited and pushed while the user is making their conflict resolution changes, if a temporary branch should be made to work from, etc. Thoughts? How do we properly map this out git-wise, gitea-wise and UI-wise? Do we lock the head branch or something? I wonder what Github does to handle conflict resolution and new changes while it is being done.

For simple conflicts, especially for writing documentation or books, this feature is really useful.
In these cases, I really don't want to wait until I can open my IDE to solve simple conflicts.

Any news with this issue?

@NatashaCyn Funny, I just thought about the dire need my organization has for this feature, yet I still haven't gotten to it. I really would like there to be a 2-3 of us working on this...not that I couldn't program it, as I even made the file editor/committer for Gogs/Gitea interface (the original anyway, I'm sure it has been refactored), but to make sure we are doing it right, both how Github does, but also maybe in a way that could improve on that, would be great to have others working on it.

@NatashaCyn I'm trying to get my company's fork and codebase up-to-date with Gitea 1.19.3 and release it. Once that is done, hopefully I can look more at the conflict resolver.

Ok, getting my company fork updated from v1.20, lol. Pretty much done.

Just wanted to add that this feature would be fantastic! If implementation hasn't started yet, I'd like to say I love how clear the IntelliJ/PyCharm style of merge conflict resolution is:

The sweet part about this implementation is two-fold:

Good labelling ("Your version", "Result", "Changes from ")
The little >> button (next to line numbers) to say "I want this change from this version", which basically lets you build the exact set of changes that you want

Unfortunately not a Go coder, but definitely following along in case there's anything minor I can contribute!

The main challenge with any sort of conflict resolution UI will always be horizontal space. As long as there's a synchronized horizontal scrollbar and a minimum about of horizontal space (enough room for 90/150/180/240 columns + surrounding UI), it should be workable!
This type of interface probably leaves mobile users out to dry, but I wonder how many people are trying to do complex merge conflict resolution on their mobile devices to begin with
Another alternative could be to do it in stages, eg "select changes from your version", "select changes from remote version", "final review", which you could do in some kind of tabbed UI, but then you lose the clarity of having the full picture laid out before you.
Interested to hear any thoughts from others!

I am excited to see this. @yardenshoham  thanks for accepting this.

Just to clarify, I think this is a good idea. I don't plan on implementing it personally.

@yardenshoham It's all yours!
haha. I know that. I don't mind doing it myself. I just need to find time as it is on my comapny's time the work I put into Gitea.

+1

hello guys, any news on this?

That was me ^
I'm testing the linked platform for bounties since bounty source went awol

Can I be assigned?

/attempt #9014

@oliverqx Want to team up? I've been meaning to get to this and my developers even asked about it recently and told them I would get to it once my big project that ended last quarter (March 31) was over, and now it is over. Interesting to see there is now a bounty on this.

Not trying to step on any toes here, but seeing what happens if someone else also does an attempt.

/attempt #9014

you can go ahead, I think i'll be busy for the following couple of weeks

Back to working on this finally. Just made a move across the country the last few months.

Back to working on this finally. Just made a move across the country the last few months.

Hope you've settled in well! :- ) Exciting stuff!

hi everyone :D how can i increase the bounty haha, this feature would be dope to manage our conflicts in our gitea soc/siem/soar project.

Please visit here https://console.algora.io/org/CommitGo/bounties/community?fund=go-Gitea%2Fgitea%239014


file upload not working on 2.5.0 remix

Reproduction
i upgraded remix to the latest version which is 2.5.0 now when i try to upload a file  and get it in actions. the below error message is coming.
ReferenceError: File is not defined     at <instance_members_initializer> (D:\work\monlam_ai_tools\node_modules@remix-run\node\dist\upload\fileUploadHandler.js:143:20)
System Info
File

Used Package Manager
npm
Expected Behavior
can u help
Actual Behavior
file should get uploaded

Can you provide a reproduction of the issue?

I have a similar issue:
ReferenceError: File is not defined
    at /Users/binajmen/.../node_modules/@remix-run/server-runtime/dist/upload/memoryUploadHandler.js:44:7

Hi @brophdawg11,
I reduced my project to a minimum reproduction:
https://github.com/binajmen/bug-remix-file-upload

sorry i couldnt reproduce the error because if I make a new app and try it it works . but I get the same error like @binajmen on old project even after upgrading remix to latest. any updates? on the issue?
thank you

Make sure that ALL your Remix packages are the same version.
@brophdawg11 created a script to properly update Remix.
npx upgrade-remix

https://npmjs.com/package/upgrade-remix

@binajmen It looks like your project isn't calling installGlobals() to install the File polyfill.  Adding that to the top of your express server fixes the issue 👍
@tenkus47 I believe this is likely your issue as well - if you are using a custom server please ensure you're installing the polyfills in your server.js/ts file

`import { Form, useSubmit } from "@remix-run/react";
import {
json,
unstable_composeUploadHandlers as composeUploadHandlers,
unstable_createFileUploadHandler as createFileUploadHandler,
unstable_createMemoryUploadHandler as createMemoryUploadHandler,
unstable_parseMultipartFormData as parseMultipartFormData,
} from "@remix-run/node";
import { Page } from "@shopify/polaris";
export async function action({ params, request }) {
const uploadHandler = composeUploadHandlers(
createFileUploadHandler({
directory: "public/uploads",
maxPartSize: 300000000,
}),
createMemoryUploadHandler(),
);
const formData = await parseMultipartFormData(request, uploadHandler);
const image = formData.get("image");
console.log(image)
if (!image || typeof image === "string") {
return json({ error: "something wrong", imgSrc: null });
}
return json({ status: false, message: "Please provide valid user data." });
}
export default function Index() {
const submit = useSubmit();
const handleFileUpload = (e) => {
console.log(e.currentTarget.files);
const formData = new FormData();
formData.append("image", e.currentTarget.files[0]);
submit(formData, { method: "post", encType: "multipart/form-data" });
}
return (

);
}
`
If also face this type of issue. my error code is 15:18:33 │ remix      │ ReferenceError: File is not defined 15:18:33 │ remix      │     at <instance_members_initializer> (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/node/dist/upload/fileUploadHandler.js:143:20) 15:18:33 │ remix      │     at new NodeOnDiskFile (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/node/dist/upload/fileUploadHandler.js:144:14) 15:18:33 │ remix      │     at /Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/node/dist/upload/fileUploadHandler.js:131:12 15:18:33 │ remix      │     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 15:18:33 │ remix      │     at async /Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/dist/formData.js:21:19 15:18:33 │ remix      │     at async Module.parseMultipartFormData (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/dist/formData.js:51:17) 15:18:33 │ remix      │     at async action (/Users/rostom/Shopify/trustsync-remix/app/routes/app.upload.jsx:22:20) 15:18:33 │ remix      │     at async Object.callRouteActionRR (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/dist/data.js:35:16) 15:18:33 │ remix      │     at async callLoaderOrAction (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/node_modules/@remix-run/router/dist/router.cjs.js:4166:16) 15:18:33 │ remix      │     at async submit (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/node_modules/@remix-run/router/dist/router.cjs.js:3520:16) 15:18:33 │ remix      │     at async queryImpl (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/node_modules/@remix-run/router/dist/router.cjs.js:3478:22) 15:18:33 │ remix      │     at async Object.queryRoute (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/node_modules/@remix-run/router/dist/router.cjs.js:3447:18) 15:18:33 │ remix      │     at async handleDataRequestRR (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/dist/server.js:122:20) 15:18:33 │ remix      │     at async requestHandler (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/server-runtime/dist/server.js:94:18) 15:18:33 │ remix      │     at async nodeHandler (/Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/dev/dist/vite/plugin.js:837:27) 15:18:33 │ remix      │     at async /Users/rostom/Shopify/trustsync-remix/node_modules/@remix-run/dev/dist/vite/plugin.js:840:15

Could you provide a reproduction?

No repro from me either, but chiming in that I'm also suddenly seeing an influx of this error. I've used to getting it in local development every now and then but I've not seen it happen in a hosted environment (Vercel).
I tried submitting a form without a file selected for upload and received File is not defined about 15 times in a row. I have a feeling that this somehow relates to the dev server.
For what it's worth, we're on 2.8.1 and this is what our upload handler looks like>:
const uploadHandler: UploadHandler = unstable_composeUploadHandlers(
  createS3UploadHandler('img'),
  unstable_createMemoryUploadHandler()
);

const formData = await unstable_parseMultipartFormData(
  request,
  uploadHandler
);

in which createS3UploadHandler streams the file to S3 and returns us some data in the form of a JSON blob.

Could you provide a reproduction?

please check this file, https://github.com/imrostom/shopify-image-upload/blob/main/app/routes/app.upload.jsx
i think it's shopify.server releted problem .

If someone can provide a minimal reproduction of the issue we'd be happy to take a look

If someone can provide a minimal reproduction of the issue we'd be happy to take a look

Issue solved after adding installGlobals(); in shopify.server.js


Add Tiltfile

Fixes #405.
This adds a simple Tiltfile + some instructions on how to use it. I have reused the e2e environment for tilt since I think that is where it would make most sense to work with tilt. I.e. you would change some part of the code or add a breaking e2e test and use tilt to be able to quickly make changes and check the behavior without having to rerun the test.
As mentioned in the docs, I have not included lvmd in the Tiltfile since it requires root and tilt doesn't really support that.
I have not tested this with minikube/deamonset.

I recommend running tilt ci in CI workflow.
https://docs.tilt.dev/ci.html
This will be able to detect a fault in tiltfile.
example:
https://github.com/zoetrope/website-operator/blob/c9ecbcc3dbe1a34932cba3a430d1bbc608f6281b/.github/workflows/ci.yaml#L69-L90


🎮 Game Request
Game Logic:
In "Bunny is Lost!", players control a bunny escaping a forest fire by jumping over obstacles and collecting carrots to maintain health. The game starts with a "Run!" button and features a main loop updating the bunny's movement, health, and collision with enemies like birds. The game ends if the bunny's health drops to zero or it gets caught by a bird.

Point down the features
Game points Features:

Dynamic scaling for different devices
Procedurally generated background music
Interactive controls via keyboard or touch
Collectible carrots for health
Challenging obstacles and enemies
Visual health and jump indicators
Endgame feedback on bunny’s fate

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @divyansh-2005 , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#4442

Hey @divyansh-2005 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹


Add <verbosity> config with enum values.

Value to command line arg mapping.

<verbosity>quiet</verbosity>: -q.
<verbosity>default</verbosity>, or missing: no extra args passed.
<verbosity>verbose<verbosity>: -v
<verbosity>very-verbose</verbosity>: -vv

This has been implemented, but a bit different.
The accepted values are the same as those passed to Cargo, e.g.: "", "-q", "-v", "-vv".
For example, for very-verbose mode: <verbosity>-vv</verbosity>.


[move-lang] use destruction pattern consistently for ModuleDefinition

Motivation
Coding style consistency, as ModuleDefinition is destructed in all other source compiler passes.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI

/land

:broken_heart: Test Failed - ci-test-success

/land

:broken_heart: Test Failed - ci-test-success

/land

:broken_heart: Test Failed - ci-test-success

Rebase and retry landing.
/land


Soliciting containerd CI requirements for Inclusive Integration with CNCF Projects

"CNCF is helping develop a cloud native software stack that enables cross-cloud deployments. Cross-project CI that ensures ongoing interoperability is especially valuable." - Dan Kohn Executive Director CNCF

[cncf-ci-public] CNCF CI Goals
[cncf-ci-public] Soliciting CI requirements via Project GitHub	Issues
This github issue is to provide a highly visible invite to be part of creating a cross-cloud cross-project CI within the diverse software communities of the Cloud Native Compute Foundation.
To fully understand our needs and expectations, some help documenting the current state of the containerd CI and ongoing requirements of the containerd community would be useful.
https://github.com/cncf/wg-ci/blob/master/projects/containerd.mkd
(currently https://github.com/cncf/wg-ci/pull/17)
As we collect containerd and  other project CI requirements, we'll use the cncf-ci issue at https://github.com/cncf/wg-ci/issues/12 and encourage you to join the discussion on the cncf-ci Mailing List

There is a discussion going on here https://github.com/containerd/containerd/issues/634

@hh do you mind if we close this issue and continue the discussion on #634?


Set an official coding style using clang-format

I suggest adding a .clang-format file.
This should help contributors to care less about coding style.
please refer to
https://clang.llvm.org/docs/ClangFormatStyleOptions.html

Can you confirm once the file settings are correct? XD


Remove docker-compose installation guide

This method will soon be depreciated and will have to be removed from the documentation.

The time has come:

https://github.com/SubstraFoundation/substra-backend/pull/299/commits/cbe4b1e913c7ef5c820a33fb1b0cb37170548db4
https://github.com/SubstraFoundation/hlf-k8s/pull/86/commits/062e8d233e692cc3f0ec645094ee6669c70fe4fe
https://github.com/SubstraFoundation/substra-tests/pull/126/commits/77b91f62f455fe73f6290f3549d489c962aeb0c8
To be coordinated with @Kelvin-M!


initial pubsub system tests

I think phpunit.system.xml should be phpunit-system.xml.dist or system.xml.dist to match the naming format of phpunit.xml.dist.


Optimize: bytes.Index and humanize.IBytes in SyncStandaloneReader

Opt:

Replace bytes.Index with bytes.Equal between lastBytes and EOF MARKER
Move humanize from every write to stats print

Before:

After:

Here's a question: Will doing this make the status interface unable to retrieve the humanized result? What if I want to view the status?

Currently Interface Statusable retrieve the humanized result only by method StatusString(). And StatusString can convert those stats to humanized result when called instead of calculated those stats to humanized result after every writing to rdb

Currently Interface Statusable retrieve the humanized result only by method StatusString(). And StatusString can convert those stats to humanized result when called instead of calculated those stats to humanized result after every writing to rdb

No no, you look at the Statusable interface, in the json result obtained using the web interface, the Status func is used to generate json result!

sure. Will check and fix it.

@EquentR Issue resolved.

@suxb201 看一下，好像是能提高一点点性能的样子


flash: spi_nor: fix building on XCC

For some reason, XCC fails to build complaining segfault
during CGPREP phase. Adding an assignment to a volatile
return value seems to fix this. This provides an easily
revertable commit to workaround the issue.
Fixes #37734
Signed-off-by: Daniel Leung<EMAIL_ADDRESS>

Changed to use volatile variable as it is more easily reverted. Also add a FIXME comment.


lxd/network/physical: Align with bridged

This fixes the function description for physical networks as it's not technically a no-op.
It also renames the start function to setup as it's called in the same way as that function in the bridged implementation.
Lastly the signature is changed to include the old config map as that will be needed later on when adding BGP.
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

jenkins: test this please

@tomponline should be good to go


Refactoring to support running on .Net Standard

I'm looking to use this project in a library targeting .Net Standard, as it will have Console and Desktop applications running .Net Core 8.0 and .Net 4.8.1, respectively.  There are some things I don't think I need like running remote executables, and so I've turned off build actions for files relating to this while I was in there.

Sorry I didn't mean to open a pull request against the main project 😬.


t.bailout results in a hang

The following hangs:
$ ../bin/node --version
v0.4.12
$ cat foo.test.js
var test = require('tap').test;
test("first", function(t) {
    t.end();
});
test("bail", function(t) {
    t.bailout("boom");
    t.end();
});
test("last", function(t) {
    t.end();
});
$ ../bin/node foo.test.js
# first
^C

I see this with both tap 0.0.14 and 0.0.1. My understanding from the example test file is that this should abort all subsequent tests in the test file.

Your understanding is correct.  This is a bug.

It hangs because the timeout is not cleared. It will hang until the timeout is cleared. Setting no timeout, timeout as infinity, causes the program to end on bailout. The processes exists with no output, but should send with "Bail out!" to let the harness know that things are not good.


Occasional segmentation fault during annotation step

Hi, thank you for the work on this really interesting tool!
I have a set of RNA-seq samples that I'm iterating over to call TRUST4 on. What is odd is that while most samples run end-to-end without any issue, several of my samples are failing during the annotation step with a segmentation fault, which is a rather opaque failure state so I don't have much insight into why it is failing. Here is an example of the log output for two samples where one succeeds followed by one that fails during the annotation step:
Succeeds
[Mon Jul 13 22:37:26 2020] TRUST4 begins.
[Mon Jul 13 22:37:26 2020] SYSTEM CALL: /home/ubuntu/TRUST4/fastq-extractor -1 samples/PC-1-1_1.fq -2 samples/PC-1-1_2.fq -t 16 -f TRUST4/mouse/mouse_IMGT+C.fa -o output/PC-1-1/PC-1-1_toa
ssemble
[Mon Jul 13 22:37:26 2020] Start to extract candidate reads from read files.
[Mon Jul 13 22:43:50 2020] Finish extracting reads.
[Mon Jul 13 22:43:50 2020] SYSTEM CALL: /home/ubuntu/TRUST4/trust4  -f TRUST4/mouse/mouse_IMGT+C.fa -o output/PC-1-1/PC-1-1 -t 16 -1 output/PC-1-1/PC-1-1_toassemble_1.fq -2 output/PC-1-1/
PC-1-1_toassemble_2.fq
[Mon Jul 13 22:43:53 2020] Read in and count kmers for 100000 reads.
[Mon Jul 13 22:43:55 2020] Read in and count kmers for 200000 reads.
[Mon Jul 13 22:43:58 2020] Read in and count kmers for 300000 reads.
[Mon Jul 13 22:44:01 2020] Read in and count kmers for 400000 reads.
[Mon Jul 13 22:44:11 2020] Found 406533 reads.
[Mon Jul 13 22:44:14 2020] Finish sorting the reads.
[Mon Jul 13 22:44:19 2020] Finish rough annotations.
[Mon Jul 13 22:44:19 2020] Processed 100000 reads (19559 are used for assembly).
[Mon Jul 13 22:44:23 2020] Processed 200000 reads (30992 are used for assembly).
[Mon Jul 13 22:44:34 2020] Processed 300000 reads (39967 are used for assembly).
[Mon Jul 13 22:44:45 2020] Processed 400000 reads (44026 are used for assembly).
[Mon Jul 13 22:44:45 2020] Assembled 44044 reads.
[Mon Jul 13 22:44:45 2020] Try to rescue 12906 reads for assembly.
[Mon Jul 13 22:44:49 2020] Rescued 226 reads.
[Mon Jul 13 22:44:50 2020] Extend assemblies by mate pair information.
[Mon Jul 13 22:44:51 2020] Remove redundant assemblies.
[Mon Jul 13 22:44:52 2020] Finish assembly.
[Mon Jul 13 22:44:52 2020] SYSTEM CALL: /home/ubuntu/TRUST4/annotator -f TRUST4/mouse/mouse_IMGT+C.fa -a output/PC-1-1/PC-1-1_final.out -t 16 -o output/PC-1-1/PC-1-1  -r output/PC-1-1/PC-
1-1_assembled_reads.fa > output/PC-1-1/PC-1-1_annot.fa
[Mon Jul 13 22:44:52 2020] Start to annotate assemblies.
[Mon Jul 13 22:44:53 2020] Start to realign reads for CDR3 analysis.
[Mon Jul 13 22:44:54 2020] Compute CDR3 abundance.
[Mon Jul 13 22:44:54 2020] Finish annotation.
[Mon Jul 13 22:44:54 2020] SYSTEM CALL: perl /home/ubuntu/TRUST4/trust-simplerep.pl output/PC-1-1/PC-1-1_cdr3.out  > output/PC-1-1/PC-1-1_report.tsv
[Mon Jul 13 22:44:54 2020] TRUST4 finishes.

Fails
[Mon Jul 13 22:44:54 2020] TRUST4 begins.
[Mon Jul 13 22:44:54 2020] SYSTEM CALL: /home/ubuntu/TRUST4/fastq-extractor -1 samples/PC-1-6_1.fq -2 samples/PC-1-6_2.fq -t 16 -f TRUST4/mouse/mouse_IMGT+C.fa -o output/PC-1-6/PC-1-6_toa
ssemble
[Mon Jul 13 22:44:54 2020] Start to extract candidate reads from read files.
[Mon Jul 13 22:51:25 2020] Finish extracting reads.
[Mon Jul 13 22:51:25 2020] SYSTEM CALL: /home/ubuntu/TRUST4/trust4  -f TRUST4/mouse/mouse_IMGT+C.fa -o output/PC-1-6/PC-1-6 -t 16 -1 output/PC-1-6/PC-1-6_toassemble_1.fq -2 output/PC-1-6/
PC-1-6_toassemble_2.fq
[Mon Jul 13 22:51:27 2020] Read in and count kmers for 100000 reads.
[Mon Jul 13 22:51:30 2020] Read in and count kmers for 200000 reads.
[Mon Jul 13 22:51:33 2020] Read in and count kmers for 300000 reads.
[Mon Jul 13 22:51:36 2020] Read in and count kmers for 400000 reads.
[Mon Jul 13 22:51:39 2020] Read in and count kmers for 500000 reads.
[Mon Jul 13 22:51:58 2020] Found 568504 reads.
[Mon Jul 13 22:52:01 2020] Finish sorting the reads.
[Mon Jul 13 22:52:08 2020] Finish rough annotations.
[Mon Jul 13 22:52:08 2020] Processed 100000 reads (25516 are used for assembly).
[Mon Jul 13 22:52:09 2020] Processed 200000 reads (61138 are used for assembly).
[Mon Jul 13 22:52:16 2020] Processed 300000 reads (82026 are used for assembly).
[Mon Jul 13 22:52:25 2020] Processed 400000 reads (94354 are used for assembly).
[Mon Jul 13 22:52:49 2020] Processed 500000 reads (107588 are used for assembly).
[Mon Jul 13 22:53:01 2020] Assembled 110498 reads.
[Mon Jul 13 22:53:01 2020] Try to rescue 11402 reads for assembly.
[Mon Jul 13 22:53:06 2020] Rescued 584 reads.
[Mon Jul 13 22:53:08 2020] Extend assemblies by mate pair information.
[Mon Jul 13 22:53:10 2020] Remove redundant assemblies.
[Mon Jul 13 22:53:11 2020] Finish assembly.
[Mon Jul 13 22:53:11 2020] SYSTEM CALL: /home/ubuntu/TRUST4/annotator -f TRUST4/mouse/mouse_IMGT+C.fa -a output/PC-1-6/PC-1-6_final.out -t 16 -o output/PC-1-6/PC-1-6  -r output/PC-1-6/PC-1-6_assembled_reads.fa > output/PC-1-6/PC-1-6_annot.fa
[Mon Jul 13 22:53:11 2020] Start to annotate assemblies.
Segmentation fault (core dumped)
system /home/ubuntu/TRUST4/annotator -f TRUST4/mouse/mouse_IMGT+C.fa -a output/PC-1-6/PC-1-6_final.out -t 16 -o output/PC-1-6/PC-1-6  -r output/PC-1-6/PC-1-6_assembled_reads.fa > output/PC-1-6/PC-1-6_annot.fa failed: 35584 at ./TRUST4/run-trust4 line 37.
samples/PC-2-3

TRUST4 Script
#!/usr/bin/env bash
proc=`nproc`
git clone https://github.com/liulab-dfci/TRUST4.git
mkdir -p output
for i in $(ls samples/*.fq | rev | cut -c 6- | rev | uniq)
    do
        echo ${i}
        base=`basename ${i}`
        mkdir -p output/${base}
        ./TRUST4/run-trust4 \
            -1 ${i}_1.fq \
            -2 ${i}_2.fq \
            -f TRUST4/mouse/mouse_IMGT+C.fa \
            --ref TRUST4/mouse/mouse_IMGT+C.fa \
            -o output/${base}/${base} \
            -t ${proc}
    done

These samples are all processed the exact same way, so the intermittent failure is somewhat puzzling to me. I will post an update if I figure out how to get the annotation step to run successfully.
Thank you for your time,
John

Thanks for sharing the results.
Does the file output/PC-1-6/PC-1-6_annot.fa contain any assemblies annotations?

Hi @mourisl , thank you for your reply. No, for all samples where it fails at the annotation step the _annot.fa file is empty.
-rw-rw-r--  1 ubuntu ubuntu   647831 Jul 13 21:37 DOR-0-3_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   447623 Jul 13 21:45 DOR-0-4_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   369792 Jul 13 21:52 DOR-0-7_annot.fa
-rw-rw-r--  1 ubuntu ubuntu        0 Jul 13 21:59 NC-1-2_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   319042 Jul 13 22:05 NC-1-4_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   295966 Jul 13 22:13 NC-1-5_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   573115 Jul 13 22:20 NC-1-6_annot.fa
-rw-rw-r--  1 ubuntu ubuntu        0 Jul 13 22:29 NC-2-1_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   537733 Jul 13 22:37 NC-2-7_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   819282 Jul 13 22:44 PC-1-1_annot.fa
-rw-rw-r--  1 ubuntu ubuntu        0 Jul 13 22:53 PC-1-6_annot.fa
-rw-rw-r--  1 ubuntu ubuntu        0 Jul 13 23:01 PC-2-3_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   887110 Jul 13 23:09 PC-2-5_annot.fa
-rw-rw-r--  1 ubuntu ubuntu        0 Jul 13 23:16 XP-1-4_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   762502 Jul 13 23:23 XP-1-5_annot.fa
-rw-rw-r--  1 ubuntu ubuntu        0 Jul 13 23:31 XP-1-7_annot.fa
-rw-rw-r--  1 ubuntu ubuntu   842778 Jul 13 23:39 XP-1-8_annot.fa
-rw-rw-r--  1 ubuntu ubuntu        0 Jul 13 23:48 XP-2-1_annot.fa
-rw-rw-r--  1 ubuntu ubuntu         0 Jul 13 23:58 XP-2-3_annot.fa
-rw-rw-r--  1 ubuntu ubuntu        0 Jul 14 01:43 XP-2-5_annot.fa

Can you share one of the _final.out files that failed to generate the _annot.fa file?  Thank you.

Hi @mourisl ,
Thank you — I'm checking with my supervisor about sharing the sequences, so will let you know shortly.
I noticed while looking at the files that all the failed samples were >= 4.4MB:
-rw-rw-r--  1 ubuntu ubuntu 2.9M Jul 13 21:37 DOR-0-3_final.out.
-rw-rw-r--  1 ubuntu ubuntu 2.0M Jul 13 21:45 DOR-0-4_final.out
-rw-rw-r--  1 ubuntu ubuntu 1.7M Jul 13 21:52 DOR-0-7_final.out
-rw-rw-r--  1 ubuntu ubuntu 4.8M Jul 13 21:59 NC-1-2_final.out   <=======
-rw-rw-r--  1 ubuntu ubuntu 1.4M Jul 13 22:05 NC-1-4_final.out
-rw-rw-r--  1 ubuntu ubuntu 1.4M Jul 13 22:13 NC-1-5_final.out
-rw-rw-r--  1 ubuntu ubuntu 2.6M Jul 13 22:20 NC-1-6_final.out
-rw-rw-r--  1 ubuntu ubuntu 6.2M Jul 13 22:29 NC-2-1_final.out   <=======
-rw-rw-r--  1 ubuntu ubuntu 2.5M Jul 13 22:37 NC-2-7_final.out
-rw-rw-r--  1 ubuntu ubuntu 3.7M Jul 13 22:44 PC-1-1_final.out
-rw-rw-r--  1 ubuntu ubuntu 7.2M Jul 13 22:53 PC-1-6_final.out   <=======
-rw-rw-r--  1 ubuntu ubuntu 8.4M Jul 13 23:01 PC-2-3_final.out   <=======
-rw-rw-r--  1 ubuntu ubuntu 4.0M Jul 13 23:09 PC-2-5_final.out
-rw-rw-r--  1 ubuntu ubuntu 4.4M Jul 13 23:16 XP-1-4_final.out   <=======
-rw-rw-r--  1 ubuntu ubuntu 3.4M Jul 13 23:23 XP-1-5_final.out
-rw-rw-r--  1 ubuntu ubuntu 5.1M Jul 13 23:31 XP-1-7_final.out   <=======
-rw-rw-r--  1 ubuntu ubuntu 3.8M Jul 13 23:39 XP-1-8_final.out
-rw-rw-r--  1 ubuntu ubuntu 7.4M Jul 13 23:48 XP-2-1_final.out   <=======
-rw-rw-r--  1 ubuntu ubuntu 8.5M Jul 13 23:58 XP-2-3_final.out   <=======
-rw-rw-r--  1 ubuntu ubuntu 6.6M Jul 14 01:43 XP-2-5_final.out   <=======

I then took one of the failed samples and cut it in half:
(base) ubuntu@ip-10-200-0-18:~$ wc -l output/NC-1-2/NC-1-2_final.out
12900 output/NC-1-2/NC-1-2_final.out

head -n 6450 output/NC-1-2/NC-1-2_final.out >output/NC-1-2/foo_final.out

(base) ubuntu@ip-10-200-0-18:~$ ./TRUST4/annotator -f TRUST4/mouse/mouse_IMGT+C.fa -a output/NC-1-2/foo_final.out -t 16 -o output/NC-1-2/foo -r output/NC-1-2/NC-1-2_assembled_reads.fa > output/NC-1-2/foo_annot.fa
[Tue Jul 14 20:33:18 2020] Start to annotate assemblies.
[Tue Jul 14 20:33:18 2020] Start to realign reads for CDR3 analysis.
[Tue Jul 14 20:33:19 2020] Compute CDR3 abundance.
[Tue Jul 14 20:33:19 2020] Finish annotation.

This also worked if I tailed the second half of the file. This machine has 32G of RAM so its not an issue with memory... Any thoughts?

Interesting. The annotation shouldn't take much memory so memory should not be the issue.  Can you try to run it with single thread (-t 1)?

Hi @mourisl — I should have included that in the previous comment, but I tried that next and it still failed. I don't know Perl or I would try to take a look, but is it possible there's a fixed-size data structure that is being overflowed?
(base) ubuntu@ip-10-200-0-18:~$ ./TRUST4/annotator -f TRUST4/mouse/mouse_IMGT+C.fa -a output/NC-1-2/NC-1-2_final.out -t 1 -o output/NC-1-2/foo -r output/NC-1-2/NC-1-2_assembled_reads.fa > output/NC-1-2/foo_annot.fa
[Tue Jul 14 20:40:33 2020] Start to annotate assemblies.
Segmentation fault (core dumped)

Hi @mourisl — I got permission to share one of the files in case it is helpful for debugging: NC-1-2_final.out

Thank you! I'll check this right away!

It finished successfully on my computer. Can you try to run it without option "-r"?
If this also fails, I would guess the executable I uploaded might not be fully compatible with your system. You can try the Singularity image (similar to docker but does not require root permission) in the release. There is a brief introduction about Singularity in the README. I created this image on Ubuntu, it's fairly straightforward to use Singularity.

Hi @mourisl — Thank you for taking the time to run that file. I'm on an Ubuntu EC2 machine, but will try both removing the -r option as well as the singularity container and will report back.

Hi @mourisl ,
I'm running into the same issue using the singularity container:
(base) ubuntu@ip-10-200-0-18:~$ singularity exec trust4-singularity.sif /TRUST4/run-trust4 -1 samples/NC-1-2_1.fq -2 samples/NC-1-2_2.fq -f TRUST4/mouse/mouse_IMGT+C.fa --ref TRUST4/mouse/mouse_IMGT+C.fa -o output/NC-1-2/NC-1-2 -t 16
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
[Tue Jul 14 21:41:14 2020] TRUST4 begins.
[Tue Jul 14 21:41:14 2020] SYSTEM CALL: /TRUST4/fastq-extractor -1 samples/NC-1-2_1.fq -2 samples/NC-1-2_2.fq -t 16 -f TRUST4/mouse/mouse_IMGT+C.fa -o output/NC-1-2/NC-1-2_toassemble
[Tue Jul 14 21:41:14 2020] Start to extract candidate reads from read files.
[Tue Jul 14 21:47:01 2020] Finish extracting reads.
[Tue Jul 14 21:47:01 2020] SYSTEM CALL: /TRUST4/trust4  -f TRUST4/mouse/mouse_IMGT+C.fa -o output/NC-1-2/NC-1-2 -t 16 -1 output/NC-1-2/NC-1-2_toassemble_1.fq -2 output/NC-1-2/NC-1-2_toassemble_2.fq
[Tue Jul 14 21:47:02 2020] Read in and count kmers for 100000 reads.
[Tue Jul 14 21:47:05 2020] Read in and count kmers for 200000 reads.
[Tue Jul 14 21:47:07 2020] Read in and count kmers for 300000 reads.
[Tue Jul 14 21:47:10 2020] Read in and count kmers for 400000 reads.
[Tue Jul 14 21:47:22 2020] Found 453867 reads.
[Tue Jul 14 21:47:25 2020] Finish sorting the reads.
[Tue Jul 14 21:47:30 2020] Finish rough annotations.
[Tue Jul 14 21:47:30 2020] Processed 100000 reads (25984 are used for assembly).
[Tue Jul 14 21:47:33 2020] Processed 200000 reads (47874 are used for assembly).
[Tue Jul 14 21:47:41 2020] Processed 300000 reads (59554 are used for assembly).
[Tue Jul 14 21:47:56 2020] Processed 400000 reads (69360 are used for assembly).
[Tue Jul 14 21:48:03 2020] Assembled 71191 reads.
[Tue Jul 14 21:48:03 2020] Try to rescue 9180 reads for assembly.
[Tue Jul 14 21:48:08 2020] Rescued 177 reads.
[Tue Jul 14 21:48:09 2020] Extend assemblies by mate pair information.
[Tue Jul 14 21:48:10 2020] Remove redundant assemblies.
[Tue Jul 14 21:48:11 2020] Finish assembly.
[Tue Jul 14 21:48:11 2020] SYSTEM CALL: /TRUST4/annotator -f TRUST4/mouse/mouse_IMGT+C.fa -a output/NC-1-2/NC-1-2_final.out -t 16 -o output/NC-1-2/NC-1-2  -r output/NC-1-2/NC-1-2_assembled_reads.fa > output/NC-1-2/NC-1-2_annot.fa
[Tue Jul 14 21:48:11 2020] Start to annotate assemblies.
Segmentation fault (core dumped)
system /TRUST4/annotator -f TRUST4/mouse/mouse_IMGT+C.fa -a output/NC-1-2/NC-1-2_final.out -t 16 -o output/NC-1-2/NC-1-2  -r output/NC-1-2/NC-1-2_assembled_reads.fa > output/NC-1-2/NC-1-2_annot.fa failed: 35584 at /TRUST4/run-trust4 line 37.

Trying the singularity container with minimum commands:
(base) ubuntu@ip-10-200-0-18:~$ singularity exec trust4-singularity.sif /TRUST4/annotator -f /TRUST4/mouse/mouse_IMGT+C.fa -a output/NC-1-2/NC-1-2_final.out
[Tue Jul 14 22:27:22 2020] Start to annotate assemblies.
Segmentation fault (core dumped)

Does the container version work for you?

I think I've figured out the bug. Can you pull the GitHub repo again and give it a try? Thanks.

Everything ran without issue — thank you for such a quick patch!

Thanks for sharing the file! Helped A LOT in the debugging.


t2 update: You need to unplug T2 before it can be detected over USB again

I'm really not sure why this might be. @kevinmehall may have an idea.
@kevinmehall do you need to explicitly take the device out of app mode after flashing it with the bootloader?

It should reset into the firmware after update unless it's skipping the last step of the firmware update process. Does the LED continue to blink?

No, the LED stops blinking which makes me think that it's back in regular firmware.
It's possible that the SAMD21 is a red herring and it's actually a problem with OpenWRT. When you run t2 list, if it finds a device over USB, it requests the hostname from OpenWRT - if it's not booted, then it won't show up (and it currently crashes something on the device so you have to restart it).

When I did an update with @dtex today, mine kept flashing, but IIRC his stopped.

@kevinmehall I believe the issue is that OpenWRT seems to be rebooted after the firmware is updated. If you run t2 list just after the update, OpenWRT won't be ready to serve the hostname so it doesn't appear with t2 list.
@rwaldron you seem to have uncovered a bug. LMK if you can repro it.

Nope - I was incorrect. If T2 is running, then the SAMD21 is put in bootloader mode and updated, the OpenWRT instance is not rebooted. However, I believe the SAMD21 is not able to reconnect to the domain socket.

After OpenWRT is updated, it is no longer running the SPI Daemon. If I manually try to get it running again, I get
root@Harold:/# /etc/init.d/spid restart
Failed to connect to ubus
Failed to connect to ubus

I don't exactly know why, but somehow https://github.com/tessel/t2-cli/commit/3ed1f0b8e92431804f5a1a6aa69a4a068734ee82 fixes this. I realized that OpenWRT wasn't being upgraded properly... somehow that was breaking the usb or spi daemon.


Update model.py

As per Issue #30 we get error when we use ResNet50 as feature extractor. When we register hook to final layer of bottleneck of ResNet50 then proper pool dims are generated. expected pool dims [512, 1024, 2048] where as earlier code would generate poll dims [128, 256, 512]. Now with this commit we will get proper pool dims.

This commit will make code run smoothly when resnet50 is selected as feature extractor.


executor: support select count(1) from table

related discussion: https://github.com/risinglightdb/risinglight/discussions/503
> select count(1) from t1;
thread 'tokio-runtime-worker' panicked at 'no column to iterate', src/storage/secondary/rowset/rowset_iterator.rs:40:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

We definitely need to consider row_handler as a normal column in optimizer, so as to support this case...

Should be the same as count(*) in the current framework. Only in edge cases will it be different from count(*).

Seems that it is supported while select count(*) from table is not supported, or are there any misoperations?
> select count(1) from pg_catalog.contributors;
+-------+
| count |
+-------+
| 30    |
+-------+
in 0.005s
> select count(*) from pg_catalog.contributors;
thread 'tokio-runtime-worker' panicked at 'index out of bounds: the len is 0 but the index is 0', src/optimizer/plan_nodes/internal.rs:67:29
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'failed to join query thread: JoinError::Panic(Id(30), ...)', src/main.rs:126:23
`

That's probably a bug. Count star is hard 😇


get_rpm_names_from_specfile on packages not yet built

If get_rpm_names_from_specfile is run on a spec that hasn't been run yet, common.inc won't exist and  it will not resolve correctly.
Also, this won't support --with or --without

The first issue is temporarily "resolved".
A full solution would be as follows

Use rpmspec against the real source dir to render the spec files. The same %%->%%%% patch will be needed
Create a set of srpms for that package's depcheck . Uses thes srpms for the final rpmnames checks. Instead of using the real source dir at this point, use fake source files. No need for the real source files. The important part is --with/--without can be added here.
Use these srpms to check for package names (and provides too eventually).

This may be slow and tedious, but it is complete and only needs to be done for dep checking, which is already slow.

Also missing provides names...


Airlocks don't automically open/stay open when a player is underneath one

They just close underneath you, probably should automatically open or stay open until the player moves.

This if() check is failing somehow:
https://github.com/space-wizards/space-station-14/blob/32103979ed3ba8d968d3846add43db68a23e32a7/Content.Server/GameObjects/Components/Doors/ServerDoorComponent.cs#L176-L182

It's probably the same bug that's breaking collision checks against people, #637

Was gonna say the same, probably caused by https://github.com/space-wizards/space-station-14/pull/625 since it disabled player collision

It's working now but is it intended that it works for items now?

Duplicate of #970


hits/hitsMax are either 0 or undefined on controllers

See also #457 - my is undefined in some of the same cases.
hits and hitsMax attributes are variably undefined and 0 in js responses from the game engine; based on investigation from asquared31415 in discord, controllers which have been unclaimed due to respawn will have zeroes but other controllers will have this attribute undefined: https://github.com/screeps/backend-local/blob/7520c8c7e6a443ad955d25e064dbd151a909d8cb/lib/utils.js#L151-L164
Instead of going to an Option<u32>  for hits/hitsMax in the public API, we should likely coalesce the None variant to 0, to make the API returns consistent with the documentation - the zeroes from unclaimed rooms will always be there, so we should make that the variant to be expected for controllers (as well as other invulnerable structures less complicated than the edge cases apparently present in controllers!)

(note that a lot of the other controller properties are not properly initialized or may become unset on respawn too, they all need additional work)

Copying from discord: upgrade_blocked, ticks_to_downgrade, safe_mode_available, progress, progress_total, and is_power_enabled maybe/probably need to handle an undefined case and potentially should coalesce to 0 or false

I recently sent a bug report because I mentioned this in passing and o4 asked me to send a report, which I had forgotten to do.  This fallback might be useful, but I expect that at some point this bug may be fixed.


design doesn't fit to swaggerapi/swagger-ui:v5.17.1

Hi there,
so your project has the most themes around, especially the dark ones.
But unfortunately using the latest Docker image the .css files simply destroy the entire layout.
Can u maybe fix them?
Thanks,
DaRolla

Is it possible to find out more? I have no problems with the docker


Manga Demon

Source information
Manga Demon 1.4.12
Source language
English
Source new URL
https://demonicscans.org/
Other details
No response
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

Duplicated issue


feat(InputField): addding onSelect onMouseUp, onMouseDown

@filipdanisko can you please fix TS lint? 🙏


feat(AlgebraicTopology/SimplicialSet): Add auxiliary ext lemma for paths

We implement the generalization of the path extensionality lemmas suggested by @joelriou in #19057. Two paths of the same nonzero length can be identified by constructing an identification between each of their arrows.
Co-Authored-By: Joël Riou

I see that the use of erw has increased the tech debt counter. Is this a tactic that should be avoided?

I see that the use of erw has increased the tech debt counter. Is this a tactic that should be avoided?

If there is a reasonable way to make rw/simp/simp_rw work, it is advisable to do so. Sometimes, especially in category theory, there are no easy workarounds. If everything else fails, we may occasionally use erw.

Thanks!
bors merge


Remove confusing reference to "real" in SUBAREA_*_BOUND_* rose edit variables

Describe the bug

The description of the SUBAREA_*_BOUND_* rose edit variables specifies the data type (real). This is both redundant as rose edit already checks the input is this type, and confusing users about the CRS in use (see #668).
How to reproduce
Steps to reproduce the behaviour:

Open rose edit
Observe the description of the SUBAREA bounds.

Expected behaviour

This reference to real should just be removed.

Fixed in #765.


Migrate tests to junit 5

Before this PR
Not all tests were running after adding jqwik
After this PR

==COMMIT_MSG==
Migrate tests to junit 5
==COMMIT_MSG==
Possible downsides?

Compare the number of tests run on develop, dfox/benchmarking, and this branch:
develop:

check: 31
unit-test: 47

dfox/benchmarking:

check: 35
unit-test: 11

this branch:

check: 35
unit-test: 50

👍


Incompatible with 1.20.1

Are there any plans to update Towelette to 1.20.1? I only ask because it's been a few months since its release and the creator still appears to be active on GitHub / CurseForge

+1. Tested on 1.20.4 and it crashes on load.
Not to press or anything, but I just wanted to add that I would be ecstatic to have this working! Our server runs this along with a small number of other mods, which are all up to 1.20
(Just commenting to let the author know this mod is loved)

Should now be resolved as of the 5.0.1 release.


Chromium Build always fails first time after clean

The first clean build of chromium seems to always fail. If you do a second clean build it doesn't.

I think this is resolved in the newer chromium sources. If it pops up again please reopen


Remove support for "skip_serializing", "skip_deserializing" and "skip_serializing_if"

We plan on removing "support" for these in the next major release.
Currently, fields annotated with one of these serde annotations are skipped. However, this behavious is incorrect, depending on your usecase.
Resolves #143

great, let's merge it then!


No PPM when connected to RC IN

I have been using SBUS no problems for a long while now but needed to switch to PPM due to current limitations with the TBS Crossfire.
I am unable to get any recognised PPM signal on the RC IN port. When I test the pin of the connector that plugs into RC IN with a scope when not connected, the signal looks fine, see below. When I connect to the RC IN port I get no signal, like the pin is grounded.
I have just flashed the latest stable release and still the same problem. I have briefly discussed the issue at #4983 but thought I would open a separate issue for it.

Starting pulse = 9360us
Channels ≈ 1300us
# define PPM_MIN_CHANNEL_VALUE	800
# define PPM_MAX_CHANNEL_VALUE	2200
# define PPM_MIN_START		2300

Bump, can anyone confirm that their PPM in via RC is working on Pixhawk V1 with latest stable?
Thanks

Ok solved it, always something simple. The cable was too long :)


Add Jiwei Guo as code owner of AoP

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


After exposing service via kubectl load balancer, see logon screen but cannot logon

Is this a request for help?:

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Version of Helm and Kubernetes:
Which chart:
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

Version of Helm and Kubernetes: Most recent on azure
Which chart: Stable Concourse
What happened: Deployed successfully and when using Kubectl port fowarding can logon and access concourse Ok. However, after I configured a load balancer to expose it via an external IP, I can see the logon screen but I cannot logon.
What you expected to happen:
I expected that I would be able to logon
How to reproduce it (as minimally and precisely as possible):
kubectl expose deployment mydeploymentnameofconcourseweb --port=80 --target-port=8080 --name=kube-concourse --type=LoadBalancer

Hey @sconrod-tester ,

Please correct me if I'm wrong, but, are you facing a redirect to an undesired location when trying to finish the login process?
That might be because concourse.web.externalUrl is not set (which is required for these scenarios).
I guess that's something we can improve in the README.
Could you please confirm if that's what's happening for you?

Thanks!


Feature request: search by block height

For now the search bar will return an error if a block height is entered: https://explorer.be.cash/search/750298.

Also https://explorer.be.cash/block/756537 doesn't work.


changed the api endpoint and related function

changed to schools

Awesome! Thanks so much for jumping in, @REPTILEHAUS! :)

#18


MRT injecting fails with "failed to send: EOF"

Hello,
First of all - thank you for this great tool :pray:
I'm trying to load an MRT dump file(https://data.ris.ripe.net/rrc03/2023.01/bview.20230101.0000.gz) using the gobgp CLI.
It works for ten records, but when I go to 100 or more, it returns:
root@abc:~# gobgp mrt inject global bview.20230101.0000 10
root@abc:~# gobgp mrt inject global bview.20230101.0000 100
failed to send: EOF

Do you have any idea why this could happen?
I appreciate any help you can provide.
Kamil

Thanks for the report! Can you try the latest master? Should be fixed by https://github.com/osrg/rustybgp/commit/310543d1bdd214cc6899b33e2897e883556bb42f
Looks like the mrt file includes routes that rustybgp can't handle. Fixed rustybgp to just ignore such rather than returning an error.

Thank you very much for fixing the code so quickly. It's still parsing the file, but I assume that it now works fine.
For those routes that are ignored - would it be beneficial to log them somehow(even on the "debug" level)?

Two additional things that I realised as it started to work:

I'm getting the following message printed multiple times as it parses:

failed to parse: unknown mup subtype: 185

As far as I know, the file should be fully compatible with the BGP specs, so this should be a valid route - have you ever seen this warning? We were getting the same from the gobgp router.

We are using a configuration that creates MRT update dumps every 60 seconds:

[[mrt-dump]]
  [mrt-dump.config]
    dump-type = "updates"
    file-name = "/tmp/mrt-updates-20160510.1546.dump"
    rotation-interval = 60

What was happening with gobgp is that it was parsing the file name, and when it found the 20160510.1546 part, it was actually clever enough to understand that this it Ymd.Hm and it was storing data to a new file every 60 seconds, i.e. "/tmp/mrt-updates-20230131.1518.dump", "/tmp/mrt-updates-20230131.1519.dump" etc. - is there any chance that this could be supported?
Please let me know if I should open separate issues for all three "problems" described above,
Thanks,
Kamil

gobgp command gives the following warning:
failed to parse: unknown mup subtype: 185

MUP SAFI looks like related. Please create an issue on gobgp.
About a way to dump MRT, feel free to create an issue on gobgp. Seems that everyone wants the own way to dump MRT. GoBGP can't support hundreds of ways to dump MRT. So I don't have any plan to add a new way though.

Hello @fujita
Thanks for your last answer. I just wanted to get back to dumping the MRT topic. What I tried to say is that I like the way that the gobgp is currently rotating dump files - I only pointed out that rustybgp is not behaving in the same way. Would it be possible to get consistent(or similar) behaviour as gobgp offers?
Thanks :pray:
Kamil


Scope of "controller" variable

I do not feel comfortable making changes that alter behavior at this time, since I do not have an environment to test at this time.
At first inspection, it looks like the variable "controller" would be undefined on lines 149 and 198. At second glance, it looks like it's reading from the module level controller variable, defined on line 212.
So to me it looks like the controller should be self.controller in the above two cases.
In addition, it looks like the name 'controller' is getting redefined from the module scope on lines 132, 143, and 156. In order to avoid confusion, perhaps the block of code inside of "if name == 'main'": could be put into a main function?

@roberttstephens Well it only took several years.  But I fixed the code. Good catch.


React native Discussions

Can we have a place to discuss doubts, how-tos and more on mailing lists or Gitter.im ? Or do we use this only - https://groups.google.com/forum/#!forum/reactjs ?

There's a new group (public) at https://www.facebook.com/groups/586400221495560.

Please let us know if that group isn't meeting the needs of the community and we'll work something else out.

This should work. But sometimes, writing markdown or syntax highlighted code snippets can be useful.

I totally agree. Feel free to link to gists from the Facebook group.


Adding unit tests on Github Actions workflow

Closes #11

I am getting these errors while running the test file:
test/runtests.jl: line 2: using: command not found
test/runtests.jl: line 3: using: command not found
test/runtests.jl: line 4: using: command not found
test/runtests.jl: line 5: using: command not found
test/runtests.jl: line 7: syntax error near unexpected token `SNN'
test/runtests.jl: line 7: `SNN = SpikingNeuralNetworks'

Hi @mohitsaxenaknoldus, thanks for doing that, and also letting me know the script is failing. Cheers!


Datalabels issues in columns

In the "Linke Column" layout and the Multiple Y-Axis, when enabling datalabels in more than one Series, then the position of the Columns breaks or some of the data labels, are not showing at all.
In the case of "Multiple Y-Axis" layout (https://apexcharts.com/javascript-chart-demos/mixed-charts/multiple-yaxis/), just by enable the datalabelds, the label disappears from the 1st and last column.
When playing with the window resizing, I noticed that if the window is smaller than 1430px all the labels are shown.
After that the 1st column's label is disappearing and a few more pixels wider, the same happens to last column.
In case of "Line Column", I had already configured it.
See it here : https://codepen.io/mixahlos/pen/zYJKxKm

I had the same problem and it was caused by the stroke option. In my case, the stroke.width array was missing one value, after putting all values, it worked.

I checked stroke.width array and it has all values necessary.

any solutions?


jellyfin

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

jellyfin``

@SvenDowideit @kudos [](**### [ Duplicate of #](_url_**)https://mail.google.com/)


Validate STAC Items before publishing

The publish function should properly validate STAC Items before publishing them to SNS.
However...given that the publish function is a Lambda function, and validation requires downloading multiple schemas, care should be taken to understand the performance implications here and how to mitigate. If this greatly impacts the lambda publish function average runtime then consider:

Caching schema retrievals at the module level so that subsequent lambda invocations using the same container will not have to refetch
combining all used extensions and schemas into single single file that can either be fetched from s3 or packaged with the lambda.

This issue should move to the publish task (https://github.com/Element84/publish-stac-task).


[BUG] Song is playing still it shows 'Nothing Playing'

To Reproduce
Steps to reproduce the behavior:

Go to 'Spotify' and play song.
Go to terminal and type swaglyrics -t
See error in the browser tab opened.

Expected behavior
Should have shown lyrics in the browser tab opened.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. Xubuntu 16.04]

@aadibajpai Please confirm this

Try playing/pausing a few times in Spotify.

@aadibajpai Nothing happens, continously sending request to /songChanged but couldn't detect

This happens with me rarely, try to rapidly play/pause until it flushes. It should work.

Can you try again or so to confirm if this is a persistent issue or what?

I have tried again, but doesn't help. Can this be a issue with dbus module.
Do i have to install it separately?
On Wed, Apr 3, 2019, 3:39 AM Aadi Bajpai<EMAIL_ADDRESS>wrote:

Can you try again or so to confirm if this is a persistent issue or what?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SwagLyrics/SwagLyrics-For-Spotify/issues/1133#issuecomment-479226908,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApSyULP6kyPdtg4XfJPDSuo3JNVKoqTtks5vc9UvgaJpZM4cXm92
.

Wait what, did you not install the dependencies?

No. I thought it will be installed by the setup command.
On Wed, Apr 3, 2019, 1:47 PM Aadi Bajpai<EMAIL_ADDRESS>wrote:

Wait what, did you not install the dependencies?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SwagLyrics/SwagLyrics-For-Spotify/issues/1133#issuecomment-479387626,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApSyUNsPxAepEHYBpEfeEYjTMMPPlc87ks5vdGOEgaJpZM4cXm92
.

Did it? You must have seen the output?

Can we add requirements.txt file? It will help to install the dependencies with just one command.

Not sure what you're doing wrong. Install using pip then try.

@aadibajpai I have checked all the dependencies thoroughly, but couldn't able to figure out the problem here. Amazing thing is, its not even showing me one error.

Can you please uninstall it and do a simple pip or pipe install swaglyrics and then try it. Please post screenshots so I can see what's happening 🙂

closing since no updates.

@aadibajpai Sorry for replying so late was stuck with some college work. The project is working absolutely fine now. Is there any issue in this project which you have in mind. I will be happy to pick that up :)


Migrate e2e tests on demand part 2

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 58.73%. Comparing base (767ffbb) to head (549f094).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3216   +/-   ##
=======================================
  Coverage   58.73%   58.73%
=======================================
  Files         326      326
  Lines       18118    18118
=======================================
  Hits        10641    10641
  Misses       6298     6298
  Partials     1179     1179

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Setup

🤞

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Version 1.14.10+build.15 has entire Fabric loader in it

Mod wasn't working so I took a look. The file is now more than 3 times the previous size. I opened her up in 7-zip. Found fabric-loader-0.10.6+build.214.jar in META-INF which wasn't in build 13.

Whoops, ok. I've reverted this version since it seems super messed up.


[FR] Provide forwarders configuration similar to Discovery of Designated Resolvers

Current behavior
Unbound can configure forwarding over both plain UDP, TCP or even also encrypted TLS. That is great. But if the client would like to know, how/whether it forwards queries somewhere, there is no simple way to query active configuration.
Especially not from unprivileged client, even on the same host.
Describe the desired feature
I think especially for localhost queries, there would be typically no danger in revealing, to which hosts it forwards and using which protocols. It should be possible to not reveal such information, if we want to keep it internal only. But some ACL should be able to configure it.

RFC 9460 - SVCB and HTTPS Resource Records - defines SVCB record for specification of encrypted protocol.
RFC 9462 - Discovery of Designated Resolvers - In normal way it specifies only how other client can connect to my server.
RFC 9606 - RESINFO - Provides some information about resolver behaviour.

I think we could extend Discovery of Designated Resolvers to provide similar configuration for forwarders configured. It may even support querying for subdomains.
; this would mean forwarding to encrypted dns.google server is configured
_dns-forward.resolver.arpa. 0 IN SVCB 1 dns.google alpn="dot"
; example subdomain is forwarded to different host
example._dns-forward.resolver.arpa 0 IN SVCB 1 dns.example.net

Question is, how to use SVCB to indicate plain protocol should be used. Is there correct alpn parameter specified for that case? How plain DNS forwarding should be specified, I am not sure.
Alternative might be extending RFC 9606 RESINFO record to make that possible. But I like using SVCB a bit more.
_dns-forward prefix is just my proposal, other name is for a discussion. _dns is already taken for different use case, obviously.
Potential use-case
If I have containers running on my host, where unbound is configured, they can typically reach my DNS cache. But they cannot reach host filesystem to read it from unbound configuration. If they could query forwarders over normal DNS port, they can indicate whether forwarding from this localhost cache is still encrypted.
Such information might be needed for Zero Trust network evaluation. There, program running in container cannot know, whether his localhost leads outside that host over unencrypted connection. There is no standard way to query that. I think using SVCB not only for my own listening ports, but also for forwarding definition, might allow nice way to any application to know, how protected is DNS leading further from the service, which were read from local /etc/resolv.conf file. Because otherwise it would depend.
It should be possible to hide this information, if forwarding target is not to be revealed. In that case queries to forwarding information should not be revealed, it should respond with REFUSED. Alternatively at least NXDOMAIN.
Such information might help with troubleshooting. I think default ACL would be the same as allow recursion specification.
What would you think about this idea?

Interesting information: dnsmasq can reveal forwarders by querying CH TXT servers.bind record. Of course, it specifies only global forwarders for .. It does not support encrypted DNS, so that is kind of enough for it. I think something better could be done also by unbound.

Although unbound-control list_forwards can list forwarders nicely, it requires privileges to access the control socket. But I think just read access to forwarding information should not require any privileges from applications.


Column View :: Show

What's the Problem?
When using up/down arrows for vertical navigation in column view, selected folder's contents are not being shown in the next column.
Solution/Idea
Make the column indexing/listing refresh whenever a folder is selected using arrows, as it is currently when using the mouse.
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.19042.1348
Windows Version
Windows 10 Pro Version 20H2 19042.1348 Windows Feature Experience Pack 120.2212.3920.0
Comments
No response

Merging with #7246.


Move coq-metacoq-template (and dependencies) to the "full" level

We can keep the other packages in extended, they change much more often.

@mattam82 : currently I am installing the opam meta package "coq-metacoq.1.2+8.17".
I wonder what opam packages I should install in full and extended level after the change.


Reference AutoAWQ in news

@tonylins Thank you for your support. I have added a reference in the news section.

You can now run the following to install the package!
pip install autoawq

https://github.com/casper-hansen/AutoAWQ