fix for TIKA-1988 contributed by<EMAIL_ADDRESS>

git clone https://github.com/USCDataScience/AgePredictor
cd AgePredictor
mvn clean install
cd ..
Build tika after merging PR and go back one directory cd ..
create a work directory mkdir tika_age
download and unzip model required.

curl -Lo model.zip "https://github.com/USCDataScience/AgePredictor/blob/master/model/model.zip?raw=true"
unzip model.zip
echo "I am a test file" > test.txt

java -jar ../tika/tika-app/target/tika-app-1.16-SNAPSHOT.jar --config=../tika/tika-parsers/src/test/resources/org/apache/tika/parser/recognition/tika-config-age.xml -m test.txt

This is for integrating author AgePrediction support in https://github.com/USCDataScience/AgePredictor

thanks @smadha missed this will review now!

@chrismattmann - Any comments?

Finally got this working!
LMC-053601:tika-parsers mattmann$ java -cp ../tika-app/target/tika-app-1.16-SNAPSHOT.jar:./model org.apache.tika.cli.TikaCLI --config=src/test/resources/org/apache/tika/parser/recognition/tika-config-age.xml -m test.txt
Jul 06, 2017 9:58:31 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: com.levigo.jbig2.JBIG2ImageReader not on class path. The ImageParser will skip jbig2 images
Jul 06, 2017 9:58:31 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: JBIG2ImageReader not loaded. jbig2 files will be ignored
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
TIFFImageWriter not loaded. tiff files will not be processed
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.

Jul 06, 2017 9:58:31 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: Tesseract OCR is installed and will be automatically applied to image files.
This may dramatically slow down content extraction (TIKA-2359).
As of Tika 1.15 (and prior versions), Tesseract is automatically called.
In future versions of Tika, users may need to turn the TesseractOCRParser on via TikaConfig.
Jul 06, 2017 9:58:31 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
Jul 06, 2017 9:58:31 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: com.levigo.jbig2.JBIG2ImageReader not on class path. The ImageParser will skip jbig2 images
Jul 06, 2017 9:58:31 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: JBIG2ImageReader not loaded. jbig2 files will be ignored
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
TIFFImageWriter not loaded. tiff files will not be processed
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.

Jul 06, 2017 9:58:31 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: Tesseract OCR is installed and will be automatically applied to image files.
This may dramatically slow down content extraction (TIKA-2359).
As of Tika 1.15 (and prior versions), Tesseract is automatically called.
In future versions of Tika, users may need to turn the TesseractOCRParser on via TikaConfig.
Jul 06, 2017 9:58:31 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
INFO  Running Spark version 2.0.0
WARN  Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
INFO  Changing view acls to: mattmann
INFO  Changing modify acls to: mattmann
INFO  Changing view acls groups to:
INFO  Changing modify acls groups to:
INFO  SecurityManager: authentication disabled; ui acls disabled; users  with view permissions: Set(mattmann); groups with view permissions: Set(); users  with modify permissions: Set(mattmann); groups with modify permissions: Set()
INFO  Successfully started service 'sparkDriver' on port 51510.
INFO  Registering MapOutputTracker
INFO  Registering BlockManagerMaster
INFO  Created local directory at /private/var/folders/n5/1d_k3z4s2293q8ntx_n8sw54mm5n_8/T/blockmgr-bd30e8b2-1f38-49f9-b170-c3a95a7e312b
INFO  MemoryStore started with capacity 2004.6 MB
INFO  Registering OutputCommitCoordinator
INFO  Logging initialized @1597ms
INFO  jetty-9.2.z-SNAPSHOT
INFO  Started o.s.j.s.ServletContextHandler@f73dcd6{/jobs,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@5c87bfe2{/jobs/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@2fea7088{/jobs/job,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@40499e4f{/jobs/job/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@51cd7ffc{/stages,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@30d4b288{/stages/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@4cc6fa2a{/stages/stage,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@40f1be1b{/stages/stage/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@7a791b66{/stages/pool,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@6f2cb653{/stages/pool/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@14c01636{/storage,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@590c73d3{/storage/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@6b9ce1bf{/storage/rdd,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@61884cb1{/storage/rdd/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@75ed9710{/environment,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@4fc5e095{/environment/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@435871cb{/executors,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@609640d5{/executors/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@79da1ec0{/executors/threadDump,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@19fb8826{/executors/threadDump/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@192d74fb{/static,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@4bef0fe3{/,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@62ea3440{/api,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@27953a83{/stages/stage/kill,null,AVAILABLE}
INFO  Started ServerConnector@25748410{HTTP/1.1}{<IP_ADDRESS>:4040}
INFO  Started @1705ms
INFO  Successfully started service 'SparkUI' on port 4040.
INFO  Bound SparkUI to <IP_ADDRESS>, and started at http://<IP_ADDRESS>:4040
INFO  Starting executor ID driver on host localhost
INFO  Successfully started service 'org.apache.spark.network.netty.NettyBlockTransferService' on port 51511.
INFO  Server created on <IP_ADDRESS>:51511
INFO  Registering BlockManager BlockManagerId(driver, <IP_ADDRESS>, 51511)
INFO  Registering block manager <IP_ADDRESS>:51511 with 2004.6 MB RAM, BlockManagerId(driver, <IP_ADDRESS>, 51511)
INFO  Registered BlockManager BlockManagerId(driver, <IP_ADDRESS>, 51511)
INFO  Started o.s.j.s.ServletContextHandler@5305c37d{/metrics/json,null,AVAILABLE}
WARN  Use an existing SparkContext, some configuration may not take effect.
INFO  Started o.s.j.s.ServletContextHandler@3c1e3314{/SQL,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@78e16155{/SQL/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@50b0bc4c{/SQL/execution,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@13c612bd{/SQL/execution/json,null,AVAILABLE}
INFO  Started o.s.j.s.ServletContextHandler@28fa700e{/static/sql,null,AVAILABLE}
INFO  Warehouse path is 'file:/Users/mattmann/tmp/tika1.15/tika-parsers/spark-warehouse'.
INFO  Block broadcast_0 stored as values in memory (estimated size 6.1 MB, free 1998.5 MB)
INFO  Block broadcast_0_piece0 stored as bytes in memory (estimated size 488.5 KB, free 1998.0 MB)
INFO  Added broadcast_0_piece0 in memory on <IP_ADDRESS>:51511 (size: 488.5 KB, free: 2004.1 MB)
INFO  Created broadcast 0 from broadcast at CountVectorizer.scala:243
INFO  Code generated in 1407.24616 ms
INFO  Starting job: first at AgePredicterLocal.java:114
INFO  Got job 0 (first at AgePredicterLocal.java:114) with 1 output partitions
INFO  Final stage: ResultStage 0 (first at AgePredicterLocal.java:114)
INFO  Parents of final stage: List()
INFO  Missing parents: List()
INFO  Submitting ResultStage 0 (MapPartitionsRDD[3] at javaRDD at AgePredicterLocal.java:112), which has no missing parents
INFO  Block broadcast_1 stored as values in memory (estimated size 10.5 KB, free 1998.0 MB)
INFO  Block broadcast_1_piece0 stored as bytes in memory (estimated size 5.3 KB, free 1998.0 MB)
INFO  Added broadcast_1_piece0 in memory on <IP_ADDRESS>:51511 (size: 5.3 KB, free: 2004.1 MB)
INFO  Created broadcast 1 from broadcast at DAGScheduler.scala:1012
INFO  Submitting 1 missing tasks from ResultStage 0 (MapPartitionsRDD[3] at javaRDD at AgePredicterLocal.java:112)
INFO  Adding task set 0.0 with 1 tasks
INFO  Starting task 0.0 in stage 0.0 (TID 0, localhost, partition 0, PROCESS_LOCAL, 6477 bytes)
INFO  Running task 0.0 in stage 0.0 (TID 0)
INFO  Code generated in 16.846256 ms
INFO  Finished task 0.0 in stage 0.0 (TID 0). 3228 bytes result sent to driver
INFO  Finished task 0.0 in stage 0.0 (TID 0) in 90 ms on localhost (1/1)
INFO  Removed TaskSet 0.0, whose tasks have all completed, from pool
INFO  ResultStage 0 (first at AgePredicterLocal.java:114) finished in 0.103 s
INFO  Job 0 finished: first at AgePredicterLocal.java:114, took 0.161496 s
Content-Length: 17
Content-Type: text/plain
Estimated-Author-Age: 32.29913797083779
X-Parsed-By: org.apache.tika.parser.CompositeParser
X-Parsed-By: org.apache.tika.parser.recognition.AgeRecogniser
resourceName: test.txt
INFO  Invoking stop() from shutdown hook
INFO  Stopped ServerConnector@25748410{HTTP/1.1}{<IP_ADDRESS>:4040}
INFO  Stopped o.s.j.s.ServletContextHandler@27953a83{/stages/stage/kill,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@62ea3440{/api,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@4bef0fe3{/,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@192d74fb{/static,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@19fb8826{/executors/threadDump/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@79da1ec0{/executors/threadDump,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@609640d5{/executors/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@435871cb{/executors,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@4fc5e095{/environment/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@75ed9710{/environment,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@61884cb1{/storage/rdd/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@6b9ce1bf{/storage/rdd,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@590c73d3{/storage/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@14c01636{/storage,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@6f2cb653{/stages/pool/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@7a791b66{/stages/pool,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@40f1be1b{/stages/stage/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@4cc6fa2a{/stages/stage,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@30d4b288{/stages/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@51cd7ffc{/stages,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@40499e4f{/jobs/job/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@2fea7088{/jobs/job,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@5c87bfe2{/jobs/json,null,UNAVAILABLE}
INFO  Stopped o.s.j.s.ServletContextHandler@f73dcd6{/jobs,null,UNAVAILABLE}
INFO  Stopped Spark web UI at http://<IP_ADDRESS>:4040
INFO  MapOutputTrackerMasterEndpoint stopped!
INFO  MemoryStore cleared
INFO  BlockManager stopped
INFO  BlockManagerMaster stopped
INFO  OutputCommitCoordinator stopped!
INFO  Successfully stopped SparkContext
INFO  Shutdown hook called
INFO  Deleting directory /private/var/folders/n5/1d_k3z4s2293q8ntx_n8sw54mm5n_8/T/spark-fa52d6bc-863e-4ee1-98da-8352c0c5c84e
LMC-053601:tika-parsers mattmann$

Will commit now!

Thanks @chrismattmann

@chrismattmann
I had the same issue with running the server on 1.17.
Can you please let me know if there is any installation i missed. I had a successful build when installing the git version.
Thank you

hi @r00t1ng what issue did you have?

Hi
Nov 22, 2017 8:41:43 PM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: JBIG2ImageReader not loaded. jbig2 files will be ignored
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
TIFFImageWriter not loaded. tiff files will not be processed
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
Thank you

gotcha @r00t1ng those are just warnings. If you inspect the full output you'll see this:
Content-Length: 17
Content-Type: text/plain
Estimated-Author-Age: 32.29913797083779
X-Parsed-By: org.apache.tika.parser.CompositeParser
X-Parsed-By: org.apache.tika.parser.recognition.AgeRecogniser
resourceName: test.txt

Thx. My problem resides in using tika to attempt text extraction from image based pdfs. I installed tesseract and it is being used by tika. I am also using your python wrapper with basic parsing for content. I am not getting anything out of various documents. Sorry if I post in the wrong repository.
Please advise.
Thank you

hi @r00t1ng got it. So if you are doing text extraction from image based PDFs and using the python wrapper, it should be working. You can control what parsers are getting called by providing a custom tika-config.xml file. Depending on what type of PDF it is, you should check:
1. Does Tesseract (outside of Tika) extract text from the PDF? If so what are the settings used from the command line?
2. If Tesseract doesn't extract text outside of Tika then Tika won't b/c it's just a pass through to Tesseract on that part.

Tesseract is working from within Tika so no segregated jobs. But what if tika does some text extraction and does not pass the file to tesseract as well?
Thank you

hi @r00t1ng if you are calling Tesseract and it's working fine from within Tika, basically the best recommendation I have is to file some new JIRA tickets here http://issues.apache.org/jira/browse/TIKA - attach the files (PDFs) that you are not having good results with and then identify what the expected text is.


Grunt crashing in Node.js v10

I am not able to run Grunt at all on the latest node.js v10.0.0
project [$!] is 📦 v2.0.2 via ⬢ v10.0.0 on 🐳 v18.05.0-ce-rc1 via 🐍 system
➜ ./node_modules/grunt-cli/bin/grunt
grunt[29375]: ../src/node_contextify.cc:631:static void node::contextify::ContextifyScript::New(const FunctionCallbackInfo<v8::Value> &): Assertion `args[1]->IsString()' failed.
 1: node::Abort() [/usr/local/bin/node]
 2: node::InternalCallbackScope::~InternalCallbackScope() [/usr/local/bin/node]
 3: node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
 4: v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [/usr/local/bin/node]
 5: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<true>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node]
 6: v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
 7: 0x33c44868427d
[1]    29375 abort      ./node_modules/grunt-cli/bin/grunt

Node.js Version: 10.0.0
NPM Version: 6.0.0

@shama Is anyone fixing this issue? What can I do to help?

@vinitkumar I'm not able to repro this issue. Grunt works for me with Node 10 and npm 6:

Maybe try reinstalling Node.js?

@shama It works for me too now. It happened with 10.0.0 but not with 10.1.0. Thanks for your time 👍

FWIW, this error should probably be reported to Node itself.

Upgrade Node to latest and it would work. It did the trick for me.
On Fri, 8 Jun 2018, 18:57 Dominik Ivaška<EMAIL_ADDRESS>wrote:

[image: image]
https://user-images.githubusercontent.com/11831491/41160562-697358d6-6b30-11e8-8b04-f29da8df9504.png
Same problem here
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gruntjs/grunt-cli/issues/118#issuecomment-395760417,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAg0TtqkZ-R5CjLRf0mVS8Sba2wOmS9nks5t6nvNgaJpZM4TvR_k
.

If it's still helpful to anyone, I resolved this by removing node_modules and package-lock.json and then doing a fresh npm install. Just removing node_modules didn't work. There was probably some weird dependency pinned in package-lock.json.


Use pelican:// protocol for pss.origin setting in the cache

This enables the pelican:// protocol for the cache's pss.origin setting.
Contains four parts:

Setting the pss.origin xrootd configuration variable directly
To avoid having to touch system files, creating a separate client plugins directory and point the cache at the new directory via environment variable.
Extending the "launcher" setup to take environment variable overrides
Updating the OSX GitHub builder scripts to patch in pelican:// support for XRootD.  For Linux, I assume we'll pull in the patched version via the OSG build.

Yes -- hand tested on both Linux and Mac (that debugging actually led to the last commit).


automatically recognize http:// and https:// as urls?

Proposal
It would be quite handy if URLs written in text were automatically rendered as live links by recognizing http:// and https:// and the content that follows

This should already take place. Are you perchance writing LaTex, rather tha MySt when this happens?

Yes, tex-to-myst specifically doesn't do this yet.


Add support for unpublishing with a redirect

Allows for the path of alternative content to be specified when unpublishing a document.
Needed for https://trello.com/c/xm4W1SzB

Can you add some screenshots?

@tijmenb screens added.


fix: update to eye v4.8.4

fix: update to eye v4.8.4

:tada: This PR is included in version 5.7.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v5.7.4

Your semantic-release bot :package::rocket:


redeclaration issue

In the quick tour there is a issue when creating main.bal file. There already declared c in the begining and again it has bee declared as another variable
int c = check choice
in this line. Among them One of the c variable should be changed as another variable name.

Duplicate of https://github.com/ballerina-platform/ballerina-www/issues/984, hence closing this issue.


Changing one input from UI updating two controls.

To report a bug please provide a reproduction of the issue in a code sandbox. You can fork this example.
I have  custom dropdown and radio button inputs. Sometime when is select the radio button the dropdown is also getting updated. I dont know how this is happening.

I need much more info to be able to help. Can you provide the code you are using? Are you using some kind of component library like angular material?
In general, as long as you are using different form controls for the dropdown and the radio inputs, I can't really see a reason why ngrx-forms would cause changes to the other control when changing one of them.

Gave same label 'for' name for two inputs. It was my mistake. Thanks for quick response. The library is very much helpful.


fix json Exception

What:

[ ] Bug Fix
[ ] New Feature

Description:

Related:

Throw contents to facilitate locating the cause of failure.


Suggesting that...

LBRY protocol needs tutorials and (more) explainations.
You guys need to show people how to put something inside lbry.
Tell people that this can be the storage solution for their applications and reduce hosting cost they are going to love it.

I was a teenager when I saw lbry, I thought you were definitely going to do something like this.
Now all the libraries from microsoft tells you how to build it and run it with a single command, for example creating your first hello world in razor page through asp.net, I am still not seeing how I can use the lbry protocol and I think it would be nice if it were to be made more clearer.

First of all. Dude, use a better title for this issue. Generic titles are completely useless because you can't tell what it is about with a quick glance, and you can't reference them later on.
Second. The code is open; a true programmer that knows what he is doing can just go inside the code, read the documentation, test things, and figure out things without needing to be hand held all the time. Obviously it's hard but this is the way in free software; if you are committed to the cause you can do it.
In fact you can write this type of documentation yourself, this is one of the best things newcomers can do; they can help by documenting things that seem poorly documented. You can't expect a software project with limited resources to have extremely detailed documentation for everything.

Tell people that this can be the storage solution for their applications and reduce hosting cost

And exactly what does this mean? The LBRY Inc. company isn't going to store everything for you. The BitTorrent system works in essentially the same way. Have you told everybody to use BitTorrent to save on hosting costs as well?

I am still not seeing how I can use the lbry protocol

Just like BitTorrent.

Ok. I need to talk to your manager.

you're right. I think lbry needs to go one step further in the direction I've mentioned, maybe not exact, but that's my opinion that it would help lbry to step up to the next level. Ok so if your resource is limited, that justified that you are not doing this while microsoft has made their products so easy to use, but what about this open letter from lbry saying you guys are trying to get to the next level and has expressed signals for community feedbacks? that's why I need to talk to your manager.

Hi @Xyncgas ! The odysee.com is a perfect self documented "interface" to lbry sdk. Yeah, there is a gap between GUI interface and doing all from command line, but, tbh, (1) is not that wide, if one wants to scripting, one already is willing to get their hands dirty of coding and (2) one needs a speck of learning about blockchain, DHT, and overall architecture of LBRY to know what is possible and what is not. My 2 cents . . .

Thanks.


docs: requirements for custom mitmproxy-ca.pem

Description
Extend documentation on what format the mitmproxy-ca.pem needs to
conform with so it can be used as a CA.
Fixes #4598
Checklist

[ ] I have updated tests where applicable.
[ ] I have added an entry to the CHANGELOG.

Fantastic, thanks! 🍰


feat(config): add an issue template

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

Project coverage is 97.65%. Comparing base (ce1dd2e) to head (033995d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   97.65%   97.65%
=======================================
  Files          10       10
  Lines         341      341
=======================================
  Hits          333      333
  Misses          8        8

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


Test building Kiwi via Carthage on CI

Fixes #631.

So unfortunately CI is currently never getting to the step I added because of the regression described in #652 (the first test run doesn't pass and so no other tests run).
When running this locally on my machine, I discovered another issue: the podspec appears to no longer lint correctly under 1.0:
% pod lib lint

 -> Kiwi (2.4.0)
    - ERROR | xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - NOTE  | xcodebuild:  $HOME/Library/Developer/Xcode/DerivedData/App-fedcijoiwrqxyugjwefskiujgwum/Build/Products/Release-iphonesimulator/Kiwi/Kiwi.framework/Headers/Kiwi.h:8:9: fatal error: 'XCTest/XCTest.h' file not found
    - NOTE  | xcodebuild:  /var/folders/nl/09nb5jwj5934y_z1cl7wbxg00000gn/T/CocoaPods/Lint/App/main.m:3:9: fatal error: could not build module 'Kiwi'
    - NOTE  | [OSX] xcodebuild:  $HOME/Library/Developer/Xcode/DerivedData/App-fedcijoiwrqxyugjwefskiujgwum/Build/Products/Release/Kiwi/Kiwi.framework/Headers/Kiwi.h:8:9: fatal error: 'XCTest/XCTest.h' file not found

@orta any ideas?

Offhand, I don't but I expect Specta may have the same problem as the Podspecs look the same

Rough gist is here: https://github.com/Quick/Quick/pull/530#issuecomment-219294935 - fix is this: https://github.com/specta/specta/commit/f69bdfa4591cb59f612e1dc3f9a318df5ba83451

Closing this as it's stale.


added elifetime

Can we add one entry about electron lifetime correction to event_info for S2(x,y) correction?

Hi Jianyu, it looks like you accidentally made a commit to our stable branch, which was meant to update on releases only. I've changed the permissions to prevent this now. Your PR also had a typo (causing the Travis test build to fail) and some unintended changes (changing the default context to point to your home directory). The idea of your change seemed fine, happy to consider this -- but please test it first, and have a look through the code comparison before you make a PR.


CORE-14573: Wrong status code reported for incorrect tenantId

When requesting a CSR for a tenant, we were not checking if a virtual node is registered for the tenant.
ValidateTenantId check was updated and it now returns 400 Bad Request if virtual node is not registered for the tenant.
As we do this check early on, tests had to be updated too to make sure they test the original functionality.

Closing this PR as a new one was opened for 5.1 branch.


Can not require('ipc') in tests

Hi,
I'm using the following code in one of my files:
const ipcRenderer = require('ipc');
//...
ipcRenderer.send(...)

It works well, but when I run npm run test it fails with error:
Error: Cannot find module 'ipc'

Could you please help?

Electron built-in modules are not available in a Node process (which is what we currently use in unit test from the cli). If your want to test files which require built-in Electron modules you have to run them in e2e test or prepare mock objects for them.

Is it correct to mock it in a such way:
// test/setup.js
//...
// Mocks for Electron
global.window.require = function () {
  return {
    ipcRenderer: {
      send: function () {
        // Fake sending message to ipcMain
      }
    }
  }
};

and then use the following code in app/actions/notifications.js:
var ipcRenderer = window.require('electron').ipcRenderer;

// other code

It works (and the same approach is used in e.g. (Gitify)[https://github.com/ekonstantinidis/gitify/blob/master/src/js/tests/stores/notifications.js], but I want to find the best solution.

Another solution is that you can use electron-mocha as an alternative of mocha.

Thank you


JS Compile error for recursive member class with defaulted parameter

Attempting to compile
interface Node {
    shared formal class SubNode(String? name = null)
            satisfies Node {}
}

interface MyNode satisfies Node {
    shared actual class SubNode(String? name)
            extends super.SubNode(name)
            satisfies MyNode {
        print("new");
    }
}

results in the incorrect error:
$ ceylon compile-js
Error: Errors found. Compilation stopped.
Note: Created module simple/1.0.0
source/simple/run.ceylon:7: error: Default expression missing for name
    shared actual class SubNode(String? name)
                                ^
1 error
ceylon compile-js: There was 1 error.

The JVM backend also gives an error. Is this even valid code? Can the subclass "undefault" a parameter?

@chochos it's legal, yes, and it doesn't mean "undefault". Parameter default args are always inherited!

@gavinking I guess default args are not just inherited but also "final"?

Yes.

Seems I'll need to refactor the whole way defaulted initializer parameters work (will be similar to regular method parameters)


The --print-computed-version flag output is incorrect

When you supply the --print-computed-version the version print to stdout is incorrect as it does not factor in the git commits, sha or branch naming elements.
Example
helm release ./helm/test --print-computed-version
0.2.1

helm release ./helm/test
INFO[0000] updating the Chart.yaml to version 0.2.1-0.development+c409e7f

Is this intended? It would appear some changes to the logic after that flag was introduced changed the order of calls and resulted in the printed version being incorrect. But just want to check.

I'm currently trying to fathom why I did it that way.
The current --print-computed-version is relying on the bump flag.

Can you see if the above works as you expect?

That looks exactly like the way i had a fix on a fork, I was just waiting on legal to be allowed contrib back. Thanks for the fix :).


New getenvoy version breaks old install methods using CLI + unpublishes older versions that were locked prior with no option to stay on older version

Describe the bug
A new version of getenvoy was released today that changes the command fetch to use and provides a new manifest that doesn't have older versions of envoy that were previously version locked. No option is provided to remain on the older version using the older manifest that references version 1.12.0.
Yes I recognize that the version is very old but upgrading that is currently out of scope due to the additional configuration changes and testing required (though it is in our long term roadmap)
To Reproduce
Steps to reproduce the behavior:

Run the old way of getting envoy curl -L https://getenvoy.io/install.sh | bash -s -- -b /usr/local/bin

Expected behavior
Installation steps for installing old versions still work, or at least the old version still exists as there's been no noticable deprecation notice (I have kept coming back to check every time bintray had an issue)
Environment (please complete the relevant information):

OS: AWS linux docker image

Additional context
We've been unblocked by converting to the RPM/Yum installation method which has 1.12.0 available. This is mainly to provide context to others that are also experiencing the issue

Hi, @nheaps-chwy thanks for reporting! We did have to change things including the format order to accommodate arm64, etc and fix some problems. While the biggest change is behind us, but I appreciate this came as a surprise to you. When we do version 1.0 (hoping very soon) all syntax and formats will be portable on each release.
On quickstart script
https://raw.githubusercontent.com/tetratelabs/getenvoy/master/site/install.sh is a modified copy "godownloader" script that gets a download from the current release, right now https://github.com/tetratelabs/getenvoy/releases/tag/v0.3.0
While this does accept a tag argument (like v0.3.0), it doesn't work with old releases. It isn't really a package manager and the godownloader project is abandoned. I had to change the script last night just to keep it working. I might also rewrite the downloader script for reasons like this, but not for the <0.3 versions.
To get an old release the same way as that script means finding the tag you want here and clicking "Assets". https://github.com/tetratelabs/getenvoy/releases or otherwise doing that in curl. The old versions are there.
The only stable package we have are brew packages. If you would use a RPM/YUM package of getenvoy we can add that. I'm surprised no one has asked, yet, so please do! We are trying to make changes based on end users, so it would help to raise that.
On binary URLs
Hosting binaries permanently has been a problem in the past as you noticed. We aren't currently doing permalinks.
For your information, we decided to only host non-EOL versions in the main json file per here https://github.com/envoyproxy/envoy/blob/main/RELEASES.md#release-schedule We didn't convert EOL versions into the new format to stop encouraging them, and also relay that these are not permanent URLs.
In your case, that edged out 1.12, but it wasn't completely unexpected someone might ask for an EOL version. I raised https://github.com/tetratelabs/getenvoy/pull/262 to add back 1.12 and 1.13 last patches.
FYI canonical version list is here https://raw.githubusercontent.com/tetratelabs/getenvoy/master/site/envoy-versions.json
but directly referenced via redirect in the default of ENVOY_VERSIONS_URL=https://getenvoy.io/envoy-versions.json
This URL can be overridden and we don't expect to make any breaking changes to the format now.
For example, it should be much easier to host your own json now that the URL parameter is no longer an internal detail, and the format is published. That said, you shouldn't need to.
In closing
Excellent issue! thanks for all the details it helps steer!

TODO: update website (sadly in a different repo) explaining what to do when the install script doesn't install the version you want.

https://github.com/tetratelabs/getenvoy/pull/264 describes better where versions come from and how to override

added this issue to ask envoy to retain the binaries they already build https://github.com/envoyproxy/envoy/issues/16830 This hopefully can bring long-term and permanent URLs for tarballs

I'll close this out with this which has all available versions now https://github.com/tetratelabs/getenvoy/pull/282


ValueError: could not determine extension of package

Such a great package--thanks for this!
here's the error:
❯ python-package-init --nixpkgs-root .  test-tube
Fetching package="test-tube" version="stable"
Traceback (most recent call last):
  File "/nix/store/ddc5pd1f8iasdikwq7l2mxs427g14687-python3.7-nixpkgs-pytools-1.3.0/bin/.python-package-init-wrapped", line 9, in <module>
    sys.exit(main())
  File "/nix/store/ddc5pd1f8iasdikwq7l2mxs427g14687-python3.7-nixpkgs-pytools-1.3.0/lib/python3.7/site-packages/nixpkgs_pytools/python_package_init.py", line 34, in main
    args.nixpkgs_root,
  File "/nix/store/ddc5pd1f8iasdikwq7l2mxs427g14687-python3.7-nixpkgs-pytools-1.3.0/lib/python3.7/site-packages/nixpkgs_pytools/python_package_init.py", line 66, in initialize_package
    metadata = package_json_to_metadata(data, package_name, version)
  File "/nix/store/ddc5pd1f8iasdikwq7l2mxs427g14687-python3.7-nixpkgs-pytools-1.3.0/lib/python3.7/site-packages/nixpkgs_pytools/python_package_init.py", line 111, in package_json_to_metadata
    package_version,
  File "/nix/store/ddc5pd1f8iasdikwq7l2mxs427g14687-python3.7-nixpkgs-pytools-1.3.0/lib/python3.7/site-packages/nixpkgs_pytools/utils.py", line 10, in determine_filename_extension
    raise ValueError("could not determine extension of package: {filename}".format(filename=filename))
ValueError: could not determine extension of package: test_tube-0.7.5.tar.gz

looks like the package name test-tube does not match what is found on pypi (test_tube).

I am getting this error (I think for the same reason) on a couple other packages: rsconnect-python, rsconnect-jupyter...

that is really unfortunate and as you said there are a couple of packages which do this. On Error we could perform a second lookup in the pypi overview page or we could simply guess the name by replacing the first - with a _.
Pull-Requests are highly appreciated for this issue :)

I believe this is the same issue encountered here, to make sure that insight is shared both ways :) https://github.com/DavHau/pypi-crawlers/issues/5#issuecomment-653484997


comment out a test_throws that we can now fix it

see https://github.com/SciML/DiffEqBase.jl/pull/852

Just remove it?


Only one MDX23C model is available to download? Why?

Hello, Anjok07. After updating my UVR to the latest version, I expected that there would be brand-new MDX23C models available to download. But, when viewing the Download Center, it only has one MDX23C: InstVoc HQ. Can you verify if there are any MDX23C models available other than the InstVoc HQ?

Only one? I see three MDX-C models:

Did you enter the VIP code like described here yet? https://www.buymeacoffee.com/uvr5/vip-model-download-instructions
I'm not sure, but maybe that's needed to unlock the additional models.

Did you enter the VIP code like described here yet? https://www.buymeacoffee.com/uvr5/vip-model-download-instructions I'm not sure, but maybe that's needed to unlock the additional models.

That's awesome! It worked. At first, I had no idea that there are VIP models. I finally got the other models for MDX23C and so are the rest after inputting the Download Code for VIP models. Thanks so much for the help, Mr. Chris.

you're welcome!

I think it's kinda gift-ware. The author asks for a little contribution, but the code also works if you don't donate anything.


[PE-D][Tester D] Attendance can be better implemented

Was able to add attendance beyond 10/10. Might be better for attendance to not have a default value of /10 or stop the incrementation at 10.

Labels: type.FeatureFlaw severity.VeryLow
original: ningtan11/ped#8

Removed "/10" by Dilys


fix: multiple landing page design issues

removes background on the Quoute widget requested by Ahmad.
changes the user's username to User if the username starts with fcc-.....

Could you fix the above bug in this PR also? You need to wrap this Padding widget with an Expanded widget

Also the Email a sign in code button text isn't centered


Standardize file format for ease of creating front ends.

This list should be created with machine parsing in mind. Currently there are some differences in how each category is laid out. Standardizing this would allow for easily spinning up front ends to display the info.

@AgentEnder yeah this sounds good , can you work regarding this ? to make it in a particulare format

I can, do you care to look at the current hugo impl from #50 before I start on it?

Hey @Ishaan28malik , Please do have a review for the following PR #93, Added Resources and Practice for React Developers


codegen: improve "could not find field" error message

https://github.com/graphql-rust/graphql-client/issues/97
I've considered adding newlines in between but I don't know if there's any existing convention that would conflict with that.

error: proc-macro derive panicked
  --> src/main.rs:23:10
   |
23 | #[derive(GraphQLQuery)]
   |          ^^^^^^^^^^^^
   |
   = help: message: Code generation failed.
           Could not find field `bananas`. Available fields: `__typename, codeOfConduct, codesOfConduct, license, licenses, marketplaceCategories, marketplaceCategory, marketplaceListing, marketplaceListings, meta, node, nodes, organization, rateLimit, relay, repository, repositoryOwner, resource, search, topic, user, viewer`.

That does look better. Added as an additional commit so it can be reviewed separately.

Looks good! We discussed the iter formatting issue on another channel - we should address that concern, rebase and then let's merge this.

So I should rebase and then do the thing without itertools?

yep - for the itertools part, you can implement a Display helper, something like:
struct CommaSeparated<T>(T);

impl<A, B> std::fmt::Display for CommaSeparated<A>
where A: Iter<Item=B>,
  B: Display {
 ....
}

If it's too hard we can think about keeping the itertools dependency.


Adopt more inclusive terminology

A lot of open-source projects and organizations are now opting to ban non-inclusive terms: master/slave, whitelist/blacklist, etc.

The Inclusive Naming Initiative launched recently, with members such as the Linux Foundation, the CNCF and various companies. Several related projects have also come into existence.

My employer, VMware, has publicly committed to adopting inclusive terminology.

The Linux Kernel coding style was updated a couple months back to advocate against using non-inclusive terminology and provide some alternative suggestions to the terms most commonly used: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst#4-naming

We should therefore make the following changes as soon as possible:

[x] Adopt inclusive terminology everywhere in code and documentation - this should match the changes to the P4Runtime spec (https://github.com/p4lang/p4runtime/pull/320) -> #59
[x] Rename the "master" git branch for the repository to "main"

Which words should be replaced?
The consensus is that at the very least "master/slave" and "whitelist/blacklist" should not be used. The IETF identifies some additional terms / metaphors (https://tools.ietf.org/id/draft-knodel-terminology-00.html) and notably recommends using the neuter "they" as the singular pronoun.
We also would like to avoid the following terms when possible: abort, kill, blackout, segregate/segregation

This is great.
If you can suggest a playbook for other p4lang repos, I'd be glad to put them into action.

@jnfoster I just try to follow the recommendations from https://inclusivenaming.org/language/word-list/ and https://tools.ietf.org/id/draft-knodel-terminology-00.html
I have been making my way through the repos I'm most involved with, and I took care of p4runtime, bmv2, PI and now this one.


CV - simple verification

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

@SudheendraKatte heads up on the merge conflict.

https://64b2e7591f52c13832151c38--harness-developer.netlify.app/docs/continuous-delivery/verify/cv-getstarted/configure-first-cv/#set-a-b[…]-testing , it mentions ServiceInstanceIdentifier and all , which is not applicable for simple verification
in simple verification there's no sensitivity also <- Select a continuous verification type, sensitivity, and duration heading is wrong

Closing this PR due to multiple merge conflicts. Refer the new PR

Closing this PR due to multiple merge conflicts. Refer the new PR


#5 - Untested code

didn't run the code, just added some info, posting in case I wader off.

Awesome, should be good. I'll test shortly


Typo in constant derivative transition model process covariance formula

The constant nth derivative linear transition model has a typo in the covar method on line 150. There is an N to the power of 2 when it should be N times 2 (extra asterisk).
Current: covar[l, k] = (igrand[l, k]*dt / (1 + N**2 - l - k))
Corrected: covar[l, k] = (igrand[l, k]dt / (1 + N2 - l - k))

Closed with #758. Thanks @KaidosUncle


[bug]: All fields reset on page reload!

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
N/A
What happened?
When reloading the web UI interface, all fields are now wiped blank. Previously (before I last updated a few days ago), when the render crashed or even if you just needed to refresh the webpage, the prompt, all selected items and fields were kept perfectly.
Screenshots
No response
Additional context
No response
Contact Details
No response

Not only the data entry fields, all settings (language, Display In-Progress Images, Confirm On Delete, Display Help Icons, Use Canvas Beta Layout) reset to defaults for me when I refresh the browser page. Tried to Reset WebUI from settings, restart InvokeAI, same effect when refreshing afterwards. v2.25, and it started happening suddenly when before it wasn't an issue within that same version.

May need to forcibly reset the browser's localStorage:

Run InvokeAI and open the app in your browser per usual
Open your browser's javascript console as described here: https://www.coursera.support/s/article/learner-000001653-How-to-open-the-Javascript-console?language=en_US
Paste this command and press enter: localStorage.clear()
Refresh the page

Hopefully this sorts this issue.

Hopefully this sorts this issue.

Yes, thank you, this indeed helped.


Moving args to querystring

Rather than passing the arguments in the json payload, the arguments are instead included in the query string.

What's the motivation behind this change?

This allows the ability to dynamically adjust the arguments. In my case, i am proxying gotty and the websockets using AspNetProxy. I have a requirement to dynamically change the resulting command that is ultimately being called at the point of the proxy. When the command argument is encapsulated in the InitMessage, it’s not possible to change the content of the initmessage, but i could when it was made available in the query string.

I personally prefer the commands not being readily available in e.g. proxy logs, but I'm sympathetic to your use case. Can you make it optional?


clarifications to .net design guidelines

I fixed a few bugs and added clarifications to many guidelines.

Also this left-aligns paragraph text (rather than justify).


Improve UI related to "Mask type"

The UI provides the user with ability to select a mask type between Mask-1, Mask-2 and Mask-3.
What is the difference between these ? Why would the user select one vs the other ?

An explanatory tooltip added for the mask selection dropdown. Thanks for the suggestion.

For reference, see https://github.com/mazurowski-lab/SlicerSegmentWithSAM/commit/8cb9617d4012de0fe6b661039796871aefc830d0


Added offline mode option

I added an option to disable checking if a user exists to be able to use this plugin on offline mode servers where people are using cracked launchers.

Stupid question: I need a kind of hybrid solution to this: I have this whitelister bot along with LoginSecurity but which remembers correct, deterministic, premium UUIDs for non-cracked users whilte putting local UUIDs for cracked ones. I noticed that it seems that with this setup, cracked users who have uppercase letters in their desired usernames actually get the wrong UUID computed, as if they had all-lowercase names. Will this allow for a fix to that issue or not really?


Syntax highlighting with bat

We are missing syntax highlighting for none dot version of zshrc file when using bat

Can we get syntax highlighting with nano?


Support for shell/command-line sql comparison

Is your feature request related to a problem? Please describe.
Comparing databases using UI means that we can't automate SQL Comparison for our CI/CD pipelines. Right now I want to have the ability to drop the pipeline if databases are not identical and no suitable migration script is provided.
But I can't.
Describe the solution or feature you'd like
The solution is to support a command-line interface. A pseudo-code would be:
azure-data-studio-sql-compare -sourceConnectionString="" -targetConnectionString="" -booleanResponse

And the response could be true/false, telling us whether databases are identical or different
Describe alternatives you've considered
Right now we can't have a fully automated CI/CD pipeline. We manually compare databases and manually monitor quality by push reviews to make sure migrations scripts are provided by developers.
Additional context
Azure Data Studio is awesome. And its extensions are even more awesome. SQL Compare is an amazing extension that is truly useful and we use it on a daily basis in all of our projects. Its CLI would make fully automated CI/CD pipelines possible.

@udeeshagautam @kisantia @Benjin FYI
@Nefcanto Are you referring to the schema compare extension or something else?

@Nefcanto sounds like the sqlpackage Deploy Report action might be able to do what you're looking for. Sqlpackage is a command line tool and the deploy report be an xml file with any differences between the source and target.

@Charles-Gagnon , yes, I'm referring to the schema compare extension with this id:
microsoft.schema-compare

@kisantia, thank you for that reference.
Is it a cross-platform utility? We're using Linux (Ubuntu and Debian).

@Nefcanto yup sqlpackage is cross-platform. Here's a link with the downloads for the different platforms: https://docs.microsoft.com/en-us/sql/tools/sqlpackage/sqlpackage-download?view=sql-server-ver15


Expand documentation of ZitiQL filtering language

The filter language description given below is incomplete:
https://openziti.github.io/api/rest/shared-api-capabilities/
For example, it lacks a descrition of the following valid filter:
GET /edge/client/v1/services?filter=anyOf(configs) contains ":configId"
The full grammar is described here for reference:
https://github.com/openziti/storage/blob/main/zitiql/ZitiQl.g4

More examples would be helpful beyond merely linking to the grammar def as we do currently, if only because it's not obvious to me from looking at the grammar def how to compose a valid filter like anyOf() or allOf().

Some additional resources:
https://github.com/openziti/storage/blob/74087e8052b7cb0fb69854e50570d3e8c7bca8c2/ast/README.md
https://github.com/openziti/storage/blob/74087e8052b7cb0fb69854e50570d3e8c7bca8c2/ast/node.go#L108
Also useful are the test files:
https://github.com/openziti/storage/blob/74087e8052b7cb0fb69854e50570d3e8c7bca8c2/ast/bolt_listener_test.go


Restarts in algorithm-operator

algorithm-operator restarts showing the events in pods log.
Apparently some limit is exeeded, throwing the folowing error:
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 message listeners added to [Redis]. Use emitter.setMaxListeners() to increase limit
Need to undrerstand where we register to an event in the event emiter and either unregister or avoid reregistering

Clarification:
algorithm operator isn't restarting. This happens on any start-up of the pod.
Detailed explanation in PR.


drivers: sensors: vcnl4040: Remove dts defaults

We should not be using defaults for enum properties, this should be
required: true instead.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

From what I can tell this currently defaults to the power-up sensor configuration.

@pabigot almost but not quite -- see details in my comment

@mbolivar-nordic Thanks; the datasheet is opaque and I only checked a couple values.   I agree changing the defaults to match the power-up defaults makes sense, especially if they're independent.
If some of the properties are dependent (if you change one, others must also change), then there's a case that they should all be required.  I'm tweaking the proposed guidance to reflect that.

In particular, that would allow users to configure just the properties they care about away from defaults in DTS.
Let's say I want to change the duty cycle (led-duty-cycle) from its default, but leave the integration time (proximity-it) at its default value. Right now, it looks like I can do that and things Just Work.
I don't have to understand anything about proximity-it, which happens to share bits in the PS_CONF1 register with where the led-duty-cycle value goes.

I also agree with @mbolivar-nordic on that point. I've recently refactored a display driver and decided to go with defaults in dts bindings file, https://github.com/zephyrproject-rtos/zephyr/blob/master/dts/bindings/display/ilitek%2Cili9340.yaml. One basically gets IC defaults if nothing is specified on DT. This makes developer life easier, as it's not required to have deep knowledge of the device in order to change some basic options. Another option would be to use DT_INST_PROP_OR inside the driver, so defaults would be kept there and not in dts bindings.


Support storing Bundle resources with type "searchset"

Describe the bug
When I POST a Bundle which a Bundle.type of "searchset", I get the following error in response:
<OperationOutcome xmlns="http://hl7.org/fhir">
    <text>
        <status value="generated"/>

Operation Outcome

                    ERROR
                    []

Unable to store a Bundle resource on this server with a Bundle.type value of: searchset

    </text>
    <issue>
        <severity value="error"/>

        <diagnostics value="Unable to store a Bundle resource on this server with a Bundle.type value of: searchset"/>
    </issue>
</OperationOutcome>

Both Rick and Lloyd agree that Bundles with a type of "searchset" should be able to be stored in HAPI. We need to be able to store examples of searchset bundles on the FHIR server.
To Reproduce
POST <base>/Bundle
<?xml version="1.0" encoding="UTF-8"?>
<Bundle xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://hl7.org/fhir fixed/fhir-all-xsd/bundle.xsd" xmlns="http://hl7.org/fhir">

    <id value="read-error-example"/>
    <meta>
        <lastUpdated value="2018-08-20T16:37:08-05:00"/>
    </meta>
    <type value="searchset"/>
    <total value="0"/>
    <link>
        <relation value="self"/>
        <url value="http://localhost/fhir-stu3/1.0.1/Organization?_format=xml"/>
    </link>
</Bundle>

Expected behavior
Successfully store the Bundle with a type of "searchset"
Environment (please complete the following information):

HAPI FHIR Version: 3.7.0 (both DSTU3 and R4)
OS: Linux
Browser: Chrome

What would be the use case for storing a search set? Wouldn't it be better to convert it to a collection?

We are trying to store all content related to an ImplementationGuide resource, and that includes examples of query results (i.e. a Bundle where type=searchset).

Our workaround right now is to comment out type=searchset, add type=collection, then when we export to run the IG publisher we have to manually remove the collection type and uncomment out the searchset type. It is a real pain.

If this would be allowed (which i support) you will run into issue #1250

I believe this is fixed now in the hapi-fhir-jpaserver-starter project. You can configure it to allow storing various types of bundles, including "searchset".

Apologies for reopening this, but how do we configure the jpa server to store a searchset bundle? I say this as someone starting with hapifhir. The use case is I am manually copying data from a custom plain server into a jpa server, using the transaction field on the home page of the jpa server.


No such module 'GTMSessionFetcherCore'

Description
Compilation error in FirebaseStorage pod, version - 10.10.0

Reproducing the issue
After upgrading from 9.6 to 10.10 version, getting compilation errors in FirebaseStorage pod wherever 'COCOAPODS' macro is used. In pods project the 'COCOAPODS=1' MACRO is already defined.
Firebase SDK Version
10.10.0
Xcode Version
14.1
Installation Method
CocoaPods
Firebase Product(s)
Storage
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

We'll likely need a reproducible example to help, since there is likely something corrupt in the project undefining the COCOAPODS macro.

Wrong configuration leading to COCOAPODS macro overriding


Fix issue #308 (Period Selector)

Just something that went wrong during a refactoring

Looks good to me, thanks @Afredon :+1:


2 enable students to view their grades online

The 2 commits here allowed for students to access theirs grades as they are being updated by the teacher on an online platform. There is a csv file that holds the student information and their grades, and a python code files that contains the content to create the user-interface.

New commits and changes addressing the pull request should link to the issue number. There is no need to create a new pull request just to address a pull request review. If the pull request is linked to the issue, new commits created that are linked to the issue will also be linked to the pull request.


feat: add MacOS support

Check it out. We're cross-platform.
A few tweaks were needed to make this work:

MacOS doesn't let you map character devices, so /dev/zero is no
good for use in tests. /etc/hosts was the first file I thought of
that would be guaranteed to exist and be user-readable.

.at(addr) uses MAP_FIXED_NOREPLACE, which doesn't exist (at least
not with that name) in MacOS. There might be a way to make that work
but for now it returns InvalidInput if you try to use it.

.with_huge_pages(pow) uses MAP_HUGE_MASK on linux, which also
doesn't exist in MacOS. Luckily there's a vague equivalent in the
VM_FLAGS_SUPERPAGE_SIZE stuff - except you don't get to choose the
page size, and you apply those flags to the fd instead of passing
them with the other flags.

And with that, mmarinus builds and all tests pass on MacOS. Fun!
[Harald Hoyer<EMAIL_ADDRESS>
adapted to current git HEAD
also use VM_FLAGS_SUPERPAGE_SIZE_ANY
extend CI for MacOS

Signed-off-by: Will Woods<EMAIL_ADDRESS>Co-authored-by: Harald Hoyer<EMAIL_ADDRESS>Signed-off-by: Harald Hoyer<EMAIL_ADDRESS>Supersedes: https://github.com/enarx/mmarinus/pull/9

Looking at the CI, this is producing warnings. We should clean those up.

I think it would be better to make .at() conditional on Linux so that people can see it in the docs.

@npmccallum hopefully addressed both points, please review

@haraldh Can you rebase?

@haraldh Can you rebase?

@npmccallum
already up2date


Text support?

Does lottie support text? I have tried using system supported fonts but I can't run animation. Same animation without text is running on Android device.

@zeljkoX Lottie doesn't yet support text


Water Library Support for Android

Is there any support of water library to create tun interface for Android? If so can you please attach the link

Is there any support of water library to create tun interface for Android? If so can you please attach the link


feature: Ability to search through key mappings, aka command palette

Did you check the docs?

[X] I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.
While I find which-key tremendously helpful, as a newcomer to the lazyvim project I find it a bit overwhelming to learn all key bindings. Furthermore I would love to be able to discover keybindings directly from neovim as I type out what I want. A command pallet is something I use in most software I use today, e.g., Arc, Raycast, VS Code... tremendously useful when learning and opens up the software to beginners learning the ropes.
Describe the solution you'd like
A version of "Telescope keymap" containing all keybindings, allowing me to search both via keybinding and description. I should also be able to apply the command.
Here is the result of typing ci into which-key and Telescope keymaps repsectively

The Telescope window does not show me any keymaps that begin with ci, e.g., w for "inner word". Nothing comes up when I search for "inner word" or "change inner word".
Describe alternatives you've considered
legendary.nvim and lazy's built in telescope keymap.
Additional context
No response

what has this todo with this plugin manager?
the iw in ciw is an independent operator-pending mapping. ciw isn't one mapping but actually two (actually they aren't even mapping but just builtin key combinations)

I did not know where to put this request. Happy to submit it elsewhere more appropriate.
Is that a relevant question? As a beginner user I want to be able to discover both lazy's convenient mappings as well as built in key combination and extensions.

Discoverability of lazy features is surely a high priority for new users. Maybe I should have put this request here https://github.com/LazyVim/starter instead?

lazyvim/lazyvim?
yes this is definitely a relevant question because if you don't treat c and iw separately there would perhaps be thousands of mappings (a talk where this is described https://www.youtube.com/watch?v=wlR5gYd6um0)

Thank you. Closing issue here and submitting on lazyvim/lazyvim, referencing our discussion.
Interesting. My initial thought was to follow which-keys suggestions which are closer to being in the tens, as oppose do thousand.


Update all.json from Allure Security findings

These are the new sites for today and the corresponding top-level domains added to all.json.
Please keep in mind that the script checks against all.json from the master branch. If there are open PRs, there may be duplicates.
Also, please check if the domains added are any well-known that shouldn't be blacklisted at the top level (eg. netlify, ddns, etc) and change these to include the subdomain.
Please check them for eligibility and liveness, add the additional information (urlscan, screenshot) were applicable, and separate them in eligible, non-eligible and dead.
The curator should only copy the "eligible" ones into the spreadsheet.
Below are 5 new scam sites, along with 5 domains added to all.json:

Site
Domain

walletport.info
walletport.info

walletconnect.dynssl.com
dynssl.com

stellardebug.com
stellardebug.com

fepvt.com
fepvt.com

www.walletappconnect.com
walletappconnect.com

Eligible

Site
Urlscan
Screenshot

Non-eligible

Site

Dead

Site

@frankywild Some sites for you


How to find the path of CUTLASS?

Hi! Thanks for your great work! I have a question about cutlass PATH.
As shown in the README, we should modify some of the parameters infinetune.sh, such as CUTLASS_PATH and WANDB_PROJECT. I wonder how I could find the proper path of cutlass on my machine.
When I run find -n "*cutlass*" under /, I can only get:
/root/anaconda3/envs/rdt/lib/python3.10/site-packages/deepspeed/inference/v2/kernels/cutlass_ops
/root/anaconda3/envs/rdt/lib/python3.10/site-packages/deepspeed/inference/v2/kernels/cutlass_ops/cutlass_ops.cpp
/root/anaconda3/envs/rdt/lib/python3.10/site-packages/deepspeed/inference/v2/modules/implementations/moe/cutlass_multi_gemm.py
/root/anaconda3/envs/rdt/lib/python3.10/site-packages/deepspeed/inference/v2/modules/implementations/moe/__pycache__/cutlass_multi_gemm.cpython-310.pyc
/root/anaconda3/envs/rdt/lib/python3.10/site-packages/deepspeed/ops/op_builder/inference_cutlass_builder.py
/root/anaconda3/envs/rdt/lib/python3.10/site-packages/deepspeed/ops/op_builder/__pycache__/inference_cutlass_builder.cpython-310.pyc
/root/anaconda3/pkgs/pytorch-2.5.1-py3.10_cuda12.4_cudnn9.1.0_0/lib/python3.10/site-packages/torch/_inductor/codegen/cuda/__pycache__/cutlass_epilogue_gen.cpython-310.pyc
/root/anaconda3/pkgs/pytorch-2.5.1-py3.10_cuda12.4_cudnn9.1.0_0/lib/python3.10/site-packages/torch/_inductor/codegen/cuda/__pycache__/cutlass_utils.cpython-310.pyc
/root/anaconda3/pkgs/pytorch-2.5.1-py3.10_cuda12.4_cudnn9.1.0_0/lib/python3.10/site-packages/torch/_inductor/codegen/cuda/cutlass_epilogue_gen.py
/root/anaconda3/pkgs/pytorch-2.5.1-py3.10_cuda12.4_cudnn9.1.0_0/lib/python3.10/site-packages/torch/_inductor/codegen/cuda/cutlass_lib_extensions
/root/anaconda3/pkgs/pytorch-2.5.1-py3.10_cuda12.4_cudnn9.1.0_0/lib/python3.10/site-packages/torch/_inductor/codegen/cuda/cutlass_utils.py

I tried to search "how to find my path to cutlass" on google, still with no corresponding answers.
Should I manually install something related to cutlass, which is not mentioned in the setup phase in README? If so, what should I do exactly? Thanks for your help!

i encountered the same issue and solved by installing it referring to https://blog.csdn.net/gitblog_00440/article/details/142837443?utm_medium=distribute.pc_relevant.none-task-blog-2~default~baidujs_baidulandingword~default-1-142837443-blog-123019605.235^v43^pc_blog_bottom_relevance_base2&spm=1001.2101.3001.4242.2&utm_relevant_index=4

i encountered the same issue and solved by installing it referring to https://blog.csdn.net/gitblog_00440/article/details/142837443?utm_medium=distribute.pc_relevant.none-task-blog-2~default~baidujs_baidulandingword~default-1-142837443-blog-123019605.235^v43^pc_blog_bottom_relevance_base2&spm=1001.2101.3001.4242.2&utm_relevant_index=4

It seems that I should clone the repo github.com/NVIDIA/cutlass and make my CUTLASS_PATH linked to this cloned directory. Thanks!


Issue with<EMAIL_ADDRESS>is not used' error

Issue Summary
Hello 👋
My latest version of the Reiro theme includes the aforementioned @page.show_title_and_feature_image helper, added in the post.hbs file, as below:

Unfortunately, despite this, many users experience an error when activating the theme. On my side, such an error no longer appears (localhost installation) and scan using GScan - gives no errors. So I am unable to answer why users continue to experience this error, despite the presence of a helper.
So I am not able to give the steps for reproduction for this case. Therefore (if there is no solution) could I ask you to remove this error from GScan?
Reason: This error relates to the Beta editor feature which is not yet an official release, this is a 'error' not a 'warning' which makes it all the more worrying for users (a lot of users don't even know that it is possible to activate the new Beta editor). Additionally when the helper is not used in a theme, there is already a nice message in the editor that explains why this function cannot be used:

It seems to me that at this stage (Beta) this information is sufficient. So given the above, I would ask the Ghost team to consider removing the error message 🙏
Steps to Reproduce
Unfortunately, I do not know the exact circumstances why the error appears in some users, despite the fact that it is used in the theme.
Ghost Version
5.59.1
Node.js Version
v18.17.0
How did you install Ghost?
localhost
Database type
SQLite3
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Hey @fueko, to clarify, the @page global should only be referenced within the page.hbs file or its partials. It should not be used within post.hbs.
As for the gscan error, users need to both update Ghost and their Reiro theme in order to not see the error.
The theme error should only show in admin (the red box in the sidebar) when it's not the only warning. If it's the only warning, we don't show the box and users should only see the message in the Post editor sidebar.
Could you provide some more details on what users are seeing with their error?

Hi @9larsons! Thank you for your reply.
My themes do not use the page.hbs file because, according to the Ghost documentation, it is not mandatory and in this case the post.hbs file is used (and I am not in favor of duplicating files if it is not necessary):

Could you provide some more details on what users are seeing with their error?

There is no confirmation but I can suspect that it is an error displayed  as a pop-up when theme is activated. Also as I mentioned no error is no longer visible with me when I added it to the theme, GScan also does not return any error.
So I understand that this helper works with pages, but for the past few years the post.hbs file has acted as a replacement for the page.hbs file, which was not mandatory. So will this be fixed as it was before (by which I mean that it is correct to use this helper anywhere, be it in the final post.hbs or page.hbs application)?

Ah, understood - thanks for reminding me of that! There's only a few cases users should be seeing:

No unknown globals; this would be if they installed the new version of your theme in a narrow window of Ghost releases, as we very shortly thereafter released the gscan version that would pick up the @page helper
Missing @page use; this would be if they have a recent version of Ghost and an old version of your theme, in which case they ought to install the newest version of your theme
Unknown @page feature use; this would only be the case if you had used @page.something that we didn't expect (anything that's not @page.show_title_and_feature_image)

We can certainly improve the error message to mention that the issue only applies if using the Beta editor, although that'll require a Ghost upgrade to be visible. It would be helpful to know what specific error message they are seeing.
I'll be looking at this more today.

Thanks for your explanation! I understand that the communique about the error may have been a boundary situation.
At this point, however, I'm more interested in the correctness of using this helper, because as I mentioned I use post.hbs files instead of page.hbs as well as custom-[name].hbs (which are common for post and pages in the current Ghost structure).
My question, then, is whether I can use (and it is correct) this helper in the partial files that the post.hbs as well as custom-[name].hbs files ultimately use (GScan detects this as correct without reporting a problem as well as the function of hiding the title worked correctly).

We can certainly improve the error message to mention that the issue only applies if using the Beta editor

The message should not appear when the theme is installed as @javierencalada mentioned in https://github.com/TryGhost/Ghost/issues/17777
@9larsons thanks so much for all your help!

My page was a bit out of date, so I'm just seeing your new messages. I'm going to shoot you an email to the address you have in GitHub - I'll want to take a closer look at those sites and the theme, since that's unexpected given what you've said.

The gscan changes were incorporated a few weeks ago with that last commit. I'm going to close this and please open a new issue if you feel there's necessary changes yet.


Fix/ci test zipkin

<!--
NOTE: Please read the CONTRIBUTING.md guidelines before submitting your p
### Summary

SUMMARY_GOES_HERE

### Full changelog

* [Implement ...]
* [Add related tests]
* ...

### Issues resolved

Fix(ci) pin Alpine release to 3.13

Hi, thank you for taking the time to send this PR.
We have started the process of incorporating the plugins that used to "live on their own repos" into the Kong repo, in order to alleviate multi-repo management tasks. The plan is that all bundled plugins will live inside the Kong repo eventually, so their CI will naturally be run on each change to Kong. This includes the Zipkin plugin.
As such, I am closing this PR. Thanks again.


The performance of the getCell method of the CollectionHandler class is different from that of the old version after migration.

In maxGraph0.8., When this.connectionHandler.errorequals empty string，this.connectionHandler.error && this.connectionHandler.error.length === 0equals false

But in the old version, the value of this expression（this.error != null && this.error.length == 0） was true

This is the result of the expression running on the console，the result is true

I made a fix in my project to keep the original functionality. If Return values for validateConnection  is an empty string, I will use an empty array instead.
this.graph.getPlugin('ConnectionHandler').validateConnection = function(source, target) {
let error = null;
if (!this.isValidTarget(target)) {
error = '';
}
error = this.graph.getEdgeValidationError(null, source, target);
return error === '' ? [] : error;
}

This appears to be an error in the code. Since "" is falsy, the statement will be false when this.error is an empty string even though that is clearly what the if-statement is looking for. This line has existed since version 0.1.0 and seems to have been a mistake in translating to TS.
I'm a little bit unclear on why we only want to run the if-statement if the string is specifically present and empty but not null, rather than when it is either empty or null. It seems to me that it would make the most sense to simply put if (!this.error) to cover both cases, but I could be missing some important details. Either way, we could easily fix this by reverting to the old version if (this.error !== null && this.error.length === 0)
I will follow up and look into why we might want to exclude the case where this.error is null, and submit a PR within the next couple days with whichever of the two above solutions makes the most sense.

Can't use (!this.error) because empty error message specifically means that the connection target was invalid. Fixed and made a PR.


⚠ PrivateHD has degraded performance

In e579f25, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2123 ms

Resolved: PrivateHD performance has improved in b48fa21.


dapr pub/sub and rabbitmq  attempt to reuse consumer ta

In what area(s)?
dapr pub/sub and rabbitMQ
What version of Dapr?

1.10.x
edge: output of git describe --dirty

Expected Behavior

Dapr establish connection with rabbitMQ and subcribes to topics and subjects properly
Actual Behavior
Dapr fails to connect to rabbitMQ  with the following error messages
2023-07-27 13:23:52 {"app_id":"scheduling-api","component":"dapr-pubsub (pubsub.rabbitmq/v1)","instance":"b253cc16b828","level":"error","msg":"rabbitmq pub/sub: error in subscriber for scheduling-api-add-site in channel.Consume: Exception (530) Reason: "NOT_ALLOWED - attempt to reuse consumer tag 'scheduling-api-add-site'"","scope":"dapr.contrib","time":"2023-07-27T17:23:52.436215609Z","type":"log","ver":"1.11.1"}
RabbitMQ gives the following error
2023-07-27 13:23:52 2023-07-27 17:23:52.435614+00:00 [error] <0.1975.0> Error on AMQP connection <0.1975.0> (<IP_ADDRESS>:40448 -> <IP_ADDRESS>:5672, vhost: '/', user: 'guest', state: running), channel 1:
2023-07-27 13:23:52 2023-07-27 17:23:52.435614+00:00 [error] <0.1975.0>  operation basic.consume caused a connection exception not_allowed: "attempt to reuse consumer tag 'scheduling-api-add-site'"
Steps to Reproduce the Problem
We have 8 .net microservices that have a subscription controller and hosted services that publish subjects to sync data across the different services.
The issue lies when we are starting up all the microservices at once using docker compose.  Once the services are started up it publish events like get-all-location-data to sync it location data with the actual location microservice. Dapr failed to connect to RabbitMQ and RabbitMQ gives the message attempt to reuse consumer tag. The issue does not happen if we give a thread.sleep(15000) at the hosted services before we publish any events. We are using the method PublishEventAsync. From what I can tell there is a timing issue that if you try to publish right at startup it cause dapr to loose connection it gets stuck at that consumer tag error messages. I see dapr trying to reconnect.
See the following code
protected override async Task ExecuteAsync(CancellationToken stoppingToken)
	{
		_logger.LogInformation("Waiting for app to Start");
		if (!await WaitForAppStartup(_lifetime, stoppingToken))
		{
			_logger.LogInformation("Failed for app to Start");
			return;

		}
		_logger.LogInformation("Application Started");
		_logger.LogInformation("Wait for Dapr SideCar to be Healthy");
		await _daprClient.WaitForSidecarAsync(stoppingToken);
		_logger.LogInformation("SideCar is Healthy");
		//Wait for everyting is subcribe
		Thread.Sleep(15000); // If we comment this out issue persist.
		PublishPermission();
		PublishUserMessages();
		await RequestLocationDataAsync();
	}

Any news on this

Are there any updates?

I faced this issue too


fix(storage-node): fix register storage unit bug

Type of change:

[x] Bugfix
[ ] New feature provided
[ ] Improve performance
[ ] Backport patches

What this PR does / why we need it:

Fix database not selected bug.
When register and unregister storage unit, use database first.
Pre-submission checklist:

[x] Did you explain what problem does this PR solve? Or what new features have been added?
[x] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?

Codecov Report

Merging #376 (47e3108) into main (cd25639) will decrease coverage by 0.02%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##             main     #376      +/-   ##
==========================================
- Coverage   48.52%   48.50%   -0.02%
==========================================
  Files          46       46
  Lines        5053     5063      +10
==========================================
+ Hits         2452     2456       +4
- Misses       2383     2387       +4
- Partials      218      220       +2

Impacted Files
Coverage Δ

...rator/pkg/reconcile/storagenode/aws/rdsinstance.go
22.14% <0.00%> (ø)

...perator/pkg/controllers/storage_node_controller.go
55.45% <50.00%> (+0.20%)
:arrow_up:

...here-operator/pkg/shardingsphere/shardingsphere.go
48.93% <62.50%> (-2.23%)
:arrow_down:

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

approve

#271


Test 2227 , IPv6 lane failing, because the stress test isnt sufficent in order to failing the migration

/kind bug
What happened:
running test 2227 on ipv6 lane
the test tries to stress by dirty memory pages,
and expect the migration to fail, which doesnt
i suspect its because its kind and not a provider like k8s with vm nodes.
tried to extend the stressing time to 60 seconds, and the 800M to 900M
it didnt help
What you expected to happen:
migration should fail and test pass
How to reproduce it (as minimally and precisely as possible):
run test 2227 on prow with all other ipv6 tests as well (on its own it passes)
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

i suspect its because its kind and not a provider like k8s with vm nodes.

AFAIK this test is passing on the ipv4 lane and even passing on the ipv6 one on master.
So I am unclear how this appeared with the introduction of the migration fixes.
It the test faulty?

when i last tried, it didnt pass on ipv6 kind, because the stressing there wasnt enough to make the migration fail, i tried to increase stress timeout and so on, and it didnt help,
once we have a k8s vm based provider, we can try again, maybe stress on container node.as we have on kind, isnt strong enough to cause the migration to fail.

I think it passes, see here: https://github.com/kubevirt/kubevirt/pull/3429/files#diff-d642ef9101fdb0671d818d73a1c3f977L1086
I did a rebase on that PR, lets see the current state.

it passed because you dont have their the migration fix imo,
with the migration fix, the migration pass, and then the test fails because it expect the migration to fail by causing dirty pages which should cause a slow migration, and to fail it

Ohh, you mean it should fail on timeout.

yep
also see here please it started to flake strongly on other lanes
(my PRs arent part of this report, see the pr list at the bottom of the page please)
https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flakefinder-2020-05-20-168h.html
i think the method there isn't deterministic , and it depends on too many factors that can change

/reopen
Config propagation fix is needed.


font size issues

hcam-finder version: 0.2.2
Python version: 3
Operating System: OS X

Various issues related to font size.

Should the font size be auto-calculated somehow? e.g by querying main GUI window size vs screen size?

Load Image button doesn't always fit the text

Tip text needs different wrapping at different font sizes :(

fixed here https://github.com/HiPERCAM/hcam_finder/commit/e675c3d99cf6c35a4e911844eaf53cc4a963f30e


Add transaction result data to IndexedTx

See https://github.com/cosmos/cosmjs/pull/1241

I'm unsure how to expose this value at higher level APIs (IndexedTx/DeliverTxResponse as well as InstantiateResult and friends) because it changes starting with Cosmos SDK 0.46:
https://github.com/cosmos/cosmos-sdk/blob/v0.46.3/proto/cosmos/base/abci/v1beta1/abci.proto#L128-L140
Adding new MsgData fields does not make much sense anymore. We probably need the Cosmos SDK 0.46 types in cosmjs-types first.


advection in AD-Mode

What changes does this PR introduce?
Feature update, maybe a small bug fix (in seaice_lsr)
What is the current behaviour?
with inAdExact = .False., one can trigger a number of approximations of the adjoint, some are related to KPP, some to SEAICE some are related to advection, but only with advection scheme 33 and without multiDimAdvection. I find this confusing and misleading, but I would like to use the advection functionality separately
What is the new behaviour
new parameter useApproxAdvectionInAdMode allows to just use the advection trick without unclear implications in other parts of the code: use advScheme 33 in forward part of the simulation but 30 in the AD-part, now also implemented for seaice_advection and gad_advection (i.e. with multiDimAdvection enabled).
Does this PR introduce a breaking change?
No, old set ups are not affected. I removed the inAdMode if-statement from seaice_lsr, but that shouldn't have any effect on any setup either.
Suggested addition to tag-index
o pkg/autodiff: add new parameter useApproxAdvectionInAdMode to replace inAdMode

if useApproxAdvectionInAdMode is True and advection scheme 33 use
advection scheme 30 in AD-model in seaice_advection, gad_advection
and gad_calc_rsh, model stops when parameters are set inconsistently
defaults to False, but is reset to True if inAdExact = False to be
backwards compatible
remove unnecessary inAdMode from seaice_lsr.F

@jm-c haven't done this yet, but should we test this functionality in one of the verification experiments? I suggest global_ocean.cs32x15.seaice

After a month of contemplation, I realised that one needs to change the way inAdMode is used for this trick. Since I want to differentiate between inAdExact = .FALSE., and useApproxAdvectionInAdModel = .TRUE., I always have to use inAdMode together with either of the flags. This means, that configurations that are using inAdMode in unpublished code will be affected by this change.
It also means that inAdMode could be hardwired to be True and False in autodiff_inadmode_set/unset_ad.F and we could get rid of the confusing flags inAdTrue/False (which, in theory, can be either True or False), or at least we could hardwire these flags in autodiff_readparms.F independently of the value of inAdExact or useApproxAdvectionInAdModel. Any opinions on that?

After a month of contemplation, I realised that one needs to change the way inAdMode is used for this trick. Since I want to differentiate between inAdExact = .FALSE., and useApproxAdvectionInAdModel = .TRUE., I always have to use inAdMode together with either of the flags. This means, that configurations that are using inAdMode in unpublished code will be affected by this change.
It also means that inAdMode could be hardwired to be True and False in autodiff_inadmode_set/unset_ad.F and we could get rid of the confusing flags inAdTrue/False (which, in theory, can be either True or False), or at least we could hardwire these flags in autodiff_readparms.F independently of the value of inAdExact or useApproxAdvectionInAdModel. Any opinions on that?

@jm-c
could you please update the reference output for global_ocean.cs32x15/input_ad.seaice?

@jm-c
could you please update the reference output for global_ocean.cs32x15/input_ad.seaice?

Just mentioning that I'm not ignoring the review request, and I should be able to get to it between now and next Wednesday.

Just mentioning that I'm not ignoring the review request, and I should be able to get to it between now and next Wednesday.

@mjlosch The changes you suggest for inAdMode (and removing inAdTrue, inAdFalse) might make the line of code longer
but it's certainly much easier to follow and understand. I would vote for.

@mjlosch The changes you suggest for inAdMode (and removing inAdTrue, inAdFalse) might make the line of code longer
but it's certainly much easier to follow and understand. I would vote for.

@mjlosch I updated the 2 (adm & tlm) reference output for global_ocean.cs32x15.seaice. AD gradient check are not as good as
they were before, but I guess this is expected ? And for TLM, it's a bit better.

@mjlosch I updated the 2 (adm & tlm) reference output for global_ocean.cs32x15.seaice. AD gradient check are not as good as
they were before, but I guess this is expected ? And for TLM, it's a bit better.

thanks @jm-c for the comments. I implemented the requested changes and resolved the conversations. The AD gradient checks should become worse, because we are no approximated the AD code on purpose. Not sure why the TLM checks get better, maybe because advScheme 33 is a bit more stable than 30?
I also implemented my suggestion of removing inAdFalse/True. I think it's an improvement, but it should also be documented in the tag-index (minimum), because it changes the meaning of inAdMode. Now it always means what the name implies (i.e. if True, we are "in AD-mode" in the backwards sweep, if False, we are in forward mode), and I tried to document that in AUTODIFF_PARAMS.h. Before this change inAdMode could be false, even when we were "in AD-mode", and it meant that we don't need to apply the modifications for a more stable (and inexact) AD run.

thanks @jm-c for the comments. I implemented the requested changes and resolved the conversations. The AD gradient checks should become worse, because we are no approximated the AD code on purpose. Not sure why the TLM checks get better, maybe because advScheme 33 is a bit more stable than 30?
I also implemented my suggestion of removing inAdFalse/True. I think it's an improvement, but it should also be documented in the tag-index (minimum), because it changes the meaning of inAdMode. Now it always means what the name implies (i.e. if True, we are "in AD-mode" in the backwards sweep, if False, we are in forward mode), and I tried to document that in AUTODIFF_PARAMS.h. Before this change inAdMode could be false, even when we were "in AD-mode", and it meant that we don't need to apply the modifications for a more stable (and inexact) AD run.

@mjlosch I have an other comment regarding the few check & stop in autodiff_readparms.F related to useApproxAdvectionInAdMode
and advection schemes: For my point of view (and I think the code allows this) I might want to use this feature (useApproxAdvectionInAdMode) for all tracers that use advScheme=33, even if other advection schemes are
used for other tracers/ice fields. A typical (and frequent) example would be SEAICEadvScheme=33 with tempAdvScheme=saltAdvScheme=2 (or = an other linear advection scheme). But the current check would stop the model run for
this type of param setting.

@mjlosch I have an other comment regarding the few check & stop in autodiff_readparms.F related to useApproxAdvectionInAdMode
and advection schemes: For my point of view (and I think the code allows this) I might want to use this feature (useApproxAdvectionInAdMode) for all tracers that use advScheme=33, even if other advection schemes are
used for other tracers/ice fields. A typical (and frequent) example would be SEAICEadvScheme=33 with tempAdvScheme=saltAdvScheme=2 (or = an other linear advection scheme). But the current check would stop the model run for
this type of param setting.

@jm-c
good point. What do you suggest?

We can require that at least one of the advection schemes (and there are 3+ parameters for advection in pkg/seaice alone) is 33 if useApproxAdvectionInAdMode=.TRUE.
I am sure you have more suggestions (-;

I would favour the warning (2).

@jm-c
good point. What do you suggest?

We can require that at least one of the advection schemes (and there are 3+ parameters for advection in pkg/seaice alone) is 33 if useApproxAdvectionInAdMode=.TRUE.
I am sure you have more suggestions (-;

I would favour the warning (2).

I think (3) would be better, i.e., a warning or a stop if ENUM_DST3_FLUX_LIMIT (=33) is never used
and useApproxAdvectionInAdMode=T (because, in this case, setting useApproxAdvectionInAdMode=T is
useless). And if we anticipate that a rarely use advected seaice-field might not be accounted for
in this check, then a warning would be better.
On Mon, Jan 25, 2021 at 07:33:56AM -0800, Martin Losch wrote:

@jm-c
good point. What do you suggest?

We can require that at least one of the advection schemes (and there are 3+ parameters for advection in pkg/seaice alone) is 33 if useApproxAdvectionInAdMode=.TRUE.
I am sure you have more suggestions (-;

I would favour the warning (2).
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/MITgcm/MITgcm/pull/404#issuecomment-766899746

I think (3) would be better, i.e., a warning or a stop if ENUM_DST3_FLUX_LIMIT (=33) is never used
and useApproxAdvectionInAdMode=T (because, in this case, setting useApproxAdvectionInAdMode=T is
useless). And if we anticipate that a rarely use advected seaice-field might not be accounted for
in this check, then a warning would be better.
On Mon, Jan 25, 2021 at 07:33:56AM -0800, Martin Losch wrote:

@jm-c
good point. What do you suggest?

We can require that at least one of the advection schemes (and there are 3+ parameters for advection in pkg/seaice alone) is 33 if useApproxAdvectionInAdMode=.TRUE.
I am sure you have more suggestions (-;

I would favour the warning (2).
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/MITgcm/MITgcm/pull/404#issuecomment-766899746

OK, I went with option (3). I agree, that it does make the most sense.

OK, I went with option (3). I agree, that it does make the most sense.

@jm-c can you confirm, that all reference AD/TLM-experiments pass on your reference machine? On my linux box I temporarily found that there are only 3 digits of agreement for global_ocean.cs32x15.seaice even directly after 1f8336b, but I cannot reproduce that now (i.e. now everything looks fine to me). git tricked me again ...

Checked on villon, no problem, got 16 digits for global_ocean.cs32x15.seaice in both ADM & TLM

One thing that might be useful: In gad_advection.F (and other similar S/R), if we rename the 2 arguments: advectionScheme &vertAdvecScheme to something else (e.g. advSchemeArg) and copy them to advectionScheme & vertAdvecScheme , we can
apply the useApproxAdvectionInAdMode trick to the copy and then simplify a bit the rest of the routine.
Also this way, if we decide an other non-linear advection scheme (e.g., 7 or 77) will be replaced in AdMode by an other one (e.g., 20 or 30 again), it will be straightforward.

@jm-c that sounds like a very useful suggestion, but I am afraid that I don't quite understand how you want to do it. Like this:
        advectionScheme = advectionSchArg
#ifdef ALLOW_AUTODIFF
        IF ( useApproxAdvectionInAdMode ) THEN
         IF (advectionSchArg.EQ.ENUM_DST3_FLUX_LIMIT )
     &          advectionScheme = ENUM_DST3
C        here is room for more of these tricks:
         ...
       ENDIF
#endif /* ALLOW_AUTODIFF */

(similar for vertAdvecScheme) and then remove the autodiff part later on?

@mjlosch Yes, you got it, it's exactly as I suggested. Also, one little advantage of doing this way is that it's more clear that we
really switch to using an alternate advection scheme in Adjoint mode (and not just part of it, e.g., in 1 direction but not in other directions).

@jm-c I really like your suggestion! Please have a look. I think that this is now good to go.

@mjlosch I am going to make a small PR on verification_other to update few files there (e.g., some data.seaice);
this is the reason why I've just merged-in master here, so that it would be easier to have both repos in sync.

@mjlosch A minor comment regarding useApproxAdvectionInAdMode check in autodiff_read_params.F : the logic is good. the choice between a stop or a warning is a bit subjective: when pkg/generic_advdiff is not compiled, a stop might look better than a warning ;
and the stop in case ENUM_DST3_FLUX_LIMIT is not used coould have been a warning (but we can keep a stop). Anyway, if you feel making a small changes there let me know. Otherwise I will move forward to merge this PR.

@jm-c I have not strong feelings about the stop/warning. We can do it as you suggest. Please feel free to do it, as I don't want to screw things up in the last minute.

@mjlosch I only changed 1 warning to a stop, but left the other as full stop. Going to merge it later today.


showsEmptyAlbums causing duplicate on albums

Basically when showsEmptyAlbums = false, you duplicate the albums.
Function in DKAssetGroupListVC.swift:212 (filterEmptyGroupIfNeeded). Need to create and return different array of strings, instead of appending to the already existing one.

Oh.. My fault!!!
Please check this: https://github.com/zhangao0086/DKImagePickerController/commit/8232489db48a071994771c698a6da01bbff6866e


docs: 잘못된 링크를 수정합니다

Overview
잘못 연결되어있던 일부 링크를 수정합니다.

기여 가이드에 대한 건의를 고민하다가 발견했네요 🙏🏻

PR Checklist

[x] I read and included theses actions below

I have read the Contributing Guide
I have written documents and tests, if needed.

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

Project coverage is 99.66%. Comparing base (a50bb9b) to head (ed9b520).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #256   +/-   ##
=======================================
  Coverage   99.66%   99.66%
=======================================
  Files          36       36
  Lines         601      601
  Branches      145      145
=======================================
  Hits          599      599
  Misses          2        2


Add Dart to supported languages

Given the rising popularity of Flutter to build mobile and Desktop applications, it would be great if support for Dart could be added.

For discussion about Dart language support, see https://github.com/apple/pkl/discussions/261


Need a Hackage release so I have a tarball to download.

https://github.com/bitemyapp/homebrew/blob/master/Library/Formula/termplot.rb#L8-L9
Alternately, Github, but Hackage seems the done thing.

Done:
https://hackage.haskell.org/package/termplot


[Bug] Swagger export not working with variables

Insomnia Version: 5.16.1
Operating System: macos

Details
When exporting the json data to use in swagger, it does not change the variables to the actual values.
Expected Results
http://myapi.com/v3/endpoint
Actual Results
{{ base_url }}/{{ version }}/endpoint
This throws off any and all swagger generators

Does Swagger have it's own way of doing variables?

P.S. I know absolutely nothing about Swagger

Hmm, it doesn't have variables in the same sense as Insomnia, but it does have path variables/parameters for instance. You can read more about path parameters here: https://swagger.io/docs/specification/2-0/describing-parameters/
It's a bit tricky, since some of the variables will be global (baseurl and maybe version of the API), but some are specific to the endpoint (clientid). I think you'd want to have the endpoint specific defined as path parameters, but have the global variables be resolved.

I was wondering if there was any updates on this.  I'm also having trouble getting an Insomnia API to import into swagger, due to in path parameters.

I'd like to dig a bit more into this but I'm sure on the replication steps. Some questions I have are

Are we exporting as a regular Insomnia JSON file?

How is that file then imported to Swagger (I haven't had much exposure to it and the most references I've seen is https://editor.swagger.io/ but that doesn't recognize the Insonmia export file

I did the v4 JSON

Thanks for the clarification @Fyb3roptik : how / where did you import into on the Swagger side of things?

Honestly, this was from a while ago and im not sure this is still an issue. I am not on the project anymore so feel free to close this issue. Sorry to waste your time

I don't think this is anything to do with swagger in particular because AFAIK there is no swagger tool that ingests an Insomnia export file.
Looking at the initial report, this issue seems very closely related to https://github.com/Kong/insomnia/issues/2688


build(v2): Remove unused deps from docusaurus-mdx-loader

Motivation
Remove unused dependency newly added in https://github.com/facebook/docusaurus/pull/3469#discussion_r505644245
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

There won't be a change cause it's already used in docusaurus-remark-plugin-npm2yarn

@hamzahamidi thanks!