project-wide search and replace (wip)

This is work in progress

add replace.html
in replace() in ambuda/views/proofing/project.py

Tests

built container with make docker-start
checked Texts, Dictionaries, and Proofing pages.

@akprasad, I didn't test the entire feature as I don't have post-OCR data. One UI issues I found so far

Added a Search & replace in the project link in the /proofing//edit page. However, it points back to edit page. Not sure why

You need to review and test UI and backend.

Thanks for the quick implementation! I'll patch and take a look as soon as I can, Saturday at the latest.
As an aside, why does this PR have 200+ commits? I think this PR is including changes from your prior PRs.

Thanks for the quick implementation! I'll patch and take a look as soon as I can, Saturday at the latest.
As an aside, why does this PR have 200+ commits? I think this PR is including changes from your prior PRs.

I was wondering about the same. Then I read https://stackoverflow.com/questions/16306012/github-pull-request-showing-commits-that-are-already-in-target-branch and thought GitHub is showing only in my fork.
Not sure how to fix this one. @shreevatsa, you work on a fork. Do you see this issue?

Thanks for the quick implementation! I'll patch and take a look as soon as I can, Saturday at the latest.
As an aside, why does this PR have 200+ commits? I think this PR is including changes from your prior PRs.

I was wondering about the same. Then I read https://stackoverflow.com/questions/16306012/github-pull-request-showing-commits-that-are-already-in-target-branch and thought GitHub is showing only in my fork.
Not sure how to fix this one. @shreevatsa, you work on a fork. Do you see this issue?

The funny thing I noticed is the Files changed count is 3 while Commits count is 228.

Not sure how to fix this one. @shreevatsa, you work on a fork. Do you see this issue?

I think you need to merge the main branch of the main repo. See the part above (just before the PR name) where it says:

kvchitrapu wants to merge 228 commits into ambuda-org:main from kvchitrapu:main

This is what I would do:
Run git remote -v to see whether you've added ambuda-org/ambuda as a remote: this is what I see:
git remote -v
myfork	git@github.com:shreevatsa/ambuda.git (fetch)
myfork	git@github.com:shreevatsa/ambuda.git (push)
origin	https://github.com/ambuda-org/ambuda (fetch)
origin	https://github.com/ambuda-org/ambuda (push)

(I just used the names myfork and origin but you can use anything.)
If it's not there, then add it:
git remote add origin https://github.com/ambuda-org/ambuda

(use a different name if origin is already taken)
Then you can fetch: git fetch origin (or whatever the name of the remote is)
And git merge remotes/origin/main or whatever the name is: I think if you run git branch -a it will show the branch.

I noticed that GitHub has a feature that should makes this easier:

I noticed that GitHub has a feature that should makes this easier: just click on "Sync fork"

Thanks for checking @shreevatsa. Tried both sync commands and Sync fork button couple of days ago. The repo header on github still shows a disconnect between # commits ahead of main and Sync fork. The commits ahead count is non-zero, while Sync fork declares main is up-to-date. I'll keep looking.

I noticed that GitHub has a feature that should makes this easier: just click on "Sync fork"

Thanks @shreevatsa for checking. I tried both sync using git fetch commands and also Sync fork button. No change. I'll keep looking.

I'm free to look at this PR but I see it's closed -- are you creating a new version with a different git history?

I don't like the commit history. I'm going to reset my fork and hopefully fix this issue for good. I'm raising a new PR with those changes in a few minutes. I hope you are not working when I pulled back.


Small improvements

Coverage increased (+1.1%) to 94.858% when pulling 4f045a32444ec0f4ef587fef7a7693db212bda80 on 1011X:master into da75ee2190fb488408c645aef05ea6eab9403b58 on johannhof:master.

Thanks!


ISPN-14179 Update for Infinispan Quarkus

https://issues.redhat.com/browse/ISPN-14179

This accidentally disables logging output for some reason.. still investigating why as the methods are all invoked still.

Pretty sure it was because I accidentally moved the logJVMInformation method before the logger initialization. Verifying..

Should be working fine now that I swapped the position of the logging and JVM information methods.

Merged, thanks


feat: loading screen improvements (first iteration)

Can we do something about the TOS checkbox and unity loading on the background? It's impossible to check that checkbox and there is no indication on what's is going on :)

We put a spinner, for the time being, until the Unity module is initialized to avoid the TOS check box issue.

@moliva is it possible to change the spiner? It looks too bold :P
/See asset attached/

I want it to look like this

The tooltip images are requested by the browser and get a 304 status, but still the requests are taking ~300ms. I pushed a fix to this caching images and making the browser load them from its own memory, making local requests of ~3ms instead.


Custom containers

Hey,
I'm trying to add ::: custom containers (similar to markdown-it).
This is where I got so far. Child inlines seem to work OK, but child blocks don't (I only need paragraphs as a minimum requirement).
Any help would be greatly appreciated.

Never mind. Now that I've done a complete rewrite of IncorporateLine(), I think I've got an idea or two.

Sounds very promising! Hats off to you for doing this! Unfortunately it seems that the CommonMark spec development has stalled so extensions is the only way to move forward.

The spec may be stalled, but the implementation doesn't need to be.
How should we proceed? The changes I've made are pretty heavy (and there's
still work to do). Will you consider adding me as co-author or would it be
better for all involved if those were released separately?
On Dec 14, 2015 10:17 AM, "Kārlis Gaņģis"<EMAIL_ADDRESS>wrote:

Sounds very promising! Hats off to you for doing this! Unfortunately it
seems that the CommonMark spec development has stalled so extensions is the
only way to move forward.
—
Reply to this email directly or view it on GitHub
https://github.com/Knagis/CommonMark.NET/issues/65#issuecomment-164374865
.

I gave you write access to this repository. I think that it would be better for no one if we start creating two different releases.

Thanks. I really appreciate your input on my contribution, past and future.
You may see the progress I've made so far in the (inappropriately named)
pipe-tables branch.
On Dec 14, 2015 10:36 AM, "Kārlis Gaņģis"<EMAIL_ADDRESS>wrote:

I gave you write access to this repository. I think that it would be
better for no one if we start creating two different releases.
—
Reply to this email directly or view it on GitHub
https://github.com/Knagis/CommonMark.NET/issues/65#issuecomment-164378047
.


Error: Contract has not been deployed to detected network (network/artifact mismatch)

I am facing the issue while using the latest version of this truffle box.
However, it is not preset if I run ng serve -prod.
node -v

v8.11.1

truffle version

Truffle v4.1.5 (core: 4.1.5)
Solidity v0.4.21 (solc-js)

npm version

{ 'angular-truffle-box': '0.0.0',
npm: '5.8.0',
ares: '1.10.1-DEV',
cldr: '32.0',
http_parser: '2.8.0',
icu: '60.1',
modules: '57',
nghttp2: '1.25.0',
node: '8.11.1',
openssl: '1.0.2o',
tz: '2017c',
unicode: '10.0',
uv: '1.19.1',
v8: '6.2.414.50',
zlib: '1.2.11' }

ng version

Angular CLI: 1.7.3
Node: 8.11.1
OS: linux x64
Angular: 5.2.9
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router
@'angular/cli: 1.7.3
@'angular/language-service: 4.4.6
@'angular-devkit/build-optimizer: 0.3.2
@'angular-devkit/core: 0.4.8
@'angular-devkit/schematics: 0.3.2
@'ngtools/json-schema: 1.2.0
@'ngtools/webpack: 1.10.2
@'schematics/angular: 0.3.2
@'schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.11.0

JavaScript libraries' versions as mentioned at current package.json:

"@angular/animations": "^5.2.9",
"@angular/common": "^5.2.9",
"@angular/compiler": "^5.2.9",
"@angular/core": "^5.2.9",
"@angular/forms": "^5.2.9",
"@angular/http": "^5.2.9",
"@angular/platform-browser": "^5.2.9",
"@angular/platform-browser-dynamic": "^5.2.9",
"@angular/platform-server": "^5.2.9",
"@angular/router": "^5.2.9",
"core-js": "^2.5.4",
"rxjs": "^5.5.8",
"web3": "^1.0.0-beta.34",
"zone.js": "^0.8.23"

Did you run truffle migrate after starting testrpc?

Your update https://github.com/Quintor/angular-truffle-box/pull/36 resolved the issue. Thanks,


How to build the binaries with Translation feature enabled

Hi, it may sound a little weird. I think ungoogled-chromium is a great alternative and I would like to build my own windows binaries with enabling Google Translate (which is contradictory to the principles of ungoogle-chromium).
I tried to remove the following files and edit the series file.
patches/core/ungoogled-chromium/disable-translate.patch
patches/core/inox-patchset/0014-disable-translation-lang-fetch.patch
After building, it turns out the translation feature is still not working.
Please help and tell me which file(s) is needed to be removed or edited. Thanks

Related to #999


newbies

Why is sbt so difficult to work? clone from git and type set compile, should everything be self-contained?:
Error:Error while importing SBT project:...[info] Resolving com.fasterxml.jackson.module#jackson-module-scala_2.11;2.4.4 ...
[info] Resolving org.scala-lang#scala-reflect;2.11.2 ...
[info] Resolving com.fasterxml.jackson.core#jackson-annotations;2.4.4 ...
[info] Resolving com.thoughtworks.paranamer#paranamer;2.6 ...
[info] Resolving com.google.code.findbugs#jsr305;2.0.1 ...
[info] Resolving org.scala-lang#scala-compiler;2.11.1 ...
[info] Resolving org.scala-lang#scala-reflect;2.11.1 ...
[info] Resolving org.scala-lang.modules#scala-xml_2.11;1.0.2 ...
[info] Resolving org.scala-lang.modules#scala-parser-combinators_2.11;1.0.1 ...
[info] Resolving jline#jline;2.11 ...
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::          UNRESOLVED DEPENDENCIES         ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: com.twitter.common#metrics;0.0.29: not found
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[trace] Stack trace suppressed: run 'last :update' for the full output.
[trace] Stack trace suppressed: run 'last :ssExtractDependencies' for the full output.
[error] (:update) sbt.ResolveException: unresolved dependency: com.twitter.common#metrics;0.0.29: not found
[error] (:ssExtractDependencies) sbt.ResolveException: unresolved dependency: com.twitter.common#metrics;0.0.29: not found
[error] Total time: 5 s, completed Feb 5, 2016 3:14:21 PMSee complete log in /Users/don/Library/Logs/IntelliJIdea15/sbt.last.log

Ah good old sbt.
Same problems here btw. I'll go through the code anyway.


Improve block break animations

Fixes the starting block not breaking
Allows multiple block break animations simultaneously
Makes the blocks play an animation before they disappear behind you
Update break sound effect & particles to match the block being broken

Ok


Closes #33 Create derive_params_by_age() which creates records for growth chart data by age

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md under the header # admiralpeds (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[x] Build admiralpeds site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the Reference page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

In derive_params_growth_age function, can we modify the code to assign PARAMN for Z-score and percentile parameters? As for now, its taking same PARAMN of the input parameter from VSTESTCD.

Once the function is applied, should it not keep the derived parameters only instead of all records from the input dataset ?
Filter is needed to keep only the newly derived ones:

@Lina2689 for PARAMN please use same approach in the template as here https://pharmaverse.github.io/admiral/articles/bds_finding.html#paramcd for consistency with admiral.
@Fanny-Gautier this is the usual convention for all admiral derive_param_xxx() functions, e.g. see https://pharmaverse.github.io/admiral/reference/derive_param_bmi.html. Also in our ADVS example (https://pharmaverse.github.io/admiral/articles/bds_finding.html) we keep the source record parameters as well as the newly derived rows. This gives greater transparency and traceability as you can see where the derived records came from in one place.
Let me know if you disagree though or have any other thoughts on this. We generally try and keep the package extensions as similar as possible to admiral so that users find it easy and familiar when swapping between them.

@rossfarrugia if you want to merge this soon, we can allow others to work in parallel with a "working" function and thoroughly get test/edge cases later as a separate task/issue
@kabis-ops I've addressed or added and emoji to most of the comments thus far, if you wanna take another look please do

@zdz2101 i added comments where i think my input was needed, but shout if any others you want me to look at.
thinking about your comment above i would keep this PR open and let the review continue here for now until all these comments are closed out rather than merge too early, as me, @Lina2689 and @Fanny-Gautier could just copy your function code from this branch and run in ours if we want to try out the latest for the template or vignette PRs.
then if any of us spot further comments we can add back here, and you have it all controlled in one place rather than having to make subsequent issues/PRs.
i agree we could then make another issue for building out more unit tests later if you prefer, as it gives an opportunity for others in our team to jump in. whoever takes this we should provide the useful doc David sent of tips around testing.


deps: updates to latest brave and reporter

some notes here https://github.com/spring-projects/spring-boot/pull/40343

sorry zipkin-aws 1.2.4 wasn't fully converged in maven central, but it is now. if you don't mind kicking the build

Thanks for the PR. #671 #666 and #672 have been merged now so these deps are all upgraded for the upcoming 1.3.0 tracing release.

@shakuzen thanks tons. I'm glad we have a clean dep set ready for the next boot!


Setting transform for a Node2D outside the tree doesn't invalidate the global_transform

Godot version
v4.1.stable.official
System information
Godot v4.1.stable - Arch Linux #1 SMP PREEMPT_DYNAMIC Wed, 21 Jun 2023 20:46:20 +0000 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (nvidia; 535.54.03) - AMD Ryzen 9 5950X 16-Core Processor (32 Threads)
Issue description
Setting transform for a Node2D outside the tree doesn't invalidate global_transform, so after setting transform, reading global_transform doesn't reflect the change.
Because set_global_transform internally sets transform and does not invalidate the global one, this also means that if you set global_transform and then immediately read it back, you don't get the transform you just set. This was why I noticed the bug.
I infer from https://github.com/godotengine/godot/pull/67710 that reading the global_transform of a Node2D which is outside the tree is expected to work and should return the transform relative to the root of the disconnected tree branch.
It seems that prior to 0a9f72d5a80c8957ef5172f546c9076089862cef, a newly created CanvasItem's global_transform was marked as invalid, so the first time it is read, it is updated from the current transform. After that commit, the global_transform appears to be marked as valid from birth.
Manually invoking _invalidate_global_transform on the node causes global_transform to update as expected, the next time it is read. Perhaps the solution is doing that automatically in set_transform, something which currently only happens if the transform is in the tree?
A Node3D has the same behaviour, but it is still considered an error to access the global_transform outside the tree, and an error is reported when you try to do so.
Steps to reproduce
Make any node and attach a script to it:
extends Node

func _ready() -> void:
  var node := Node2D.new()
  node.transform.origin.x = 1
  assert(node.global_transform.origin.x == 1, "First assignment got lost")
  node.transform.origin.x = 2
  assert(node.global_transform.origin.x == 2, "Second assignment got lost")

In 4.1, the first assertion will fail. In versions before 0a9f72d5a80c8957ef5172f546c9076089862cef, the first assertion will pass, but the second assertion will fail.
Minimal reproduction project
node2d-transform-bug.zip

Can reproduce in:

v4.1.stable.official [970459615]
v4.1.1.stable.official [bd6af8e0e]

Can't reproduce in:

v4.1.2.stable.official [399c9dc39]
v4.1.3.stable.official [f06b6836a]
v4.1.4.stable.official [fe0e8e557]
v4.2.stable.official [46dc27791]
v4.2.1.stable.official [b09f793f5]
v4.2.2.stable.official [15073afe3
v4.3.dev5.official [89f70e98d]

Closing as fixed, likely by #80105.


Allow CPU fallback like standalone rife-ncnn-vulkan

There does not seem to be a way to run interpolation on CPU if no GPU is available. This is a feature in the original/standalone rife-ncnn-vulkan though.
Any chance this can be added?

Currently this plugin also shows integrated graphics that are on cpus.
[0 NVIDIA GeForce RTX 4090]  queueC=2[8]  queueG=0[16]  queueT=1[2]
[0 NVIDIA GeForce RTX 4090]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[0 NVIDIA GeForce RTX 4090]  fp16-p/s/u/a=1/1/1/1  int8-p/s/u/a=1/1/1/1
[0 NVIDIA GeForce RTX 4090]  subgroup=32  basic/vote/ballot/shuffle=1/1/1/1
[0 NVIDIA GeForce RTX 4090]  fp16-8x8x16/16x8x8/16x8x16/16x16x16=0/1/1/1
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  queueC=1[4]  queueG=0[1]  queueT=0[1]
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  fp16-p/s/u/a=1/1/1/1  int8-p/s/u/a=1/1/1/1
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  subgroup=64  basic/vote/ballot/shuffle=1/1/1/1
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  fp16-8x8x16/16x8x8/16x8x16/16x16x16=0/0/0/0

Pure cpu inference is not planned.

Currently this plugin also shows integrated graphics that are on cpus.
[0 NVIDIA GeForce RTX 4090]  queueC=2[8]  queueG=0[16]  queueT=1[2]
[0 NVIDIA GeForce RTX 4090]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[0 NVIDIA GeForce RTX 4090]  fp16-p/s/u/a=1/1/1/1  int8-p/s/u/a=1/1/1/1
[0 NVIDIA GeForce RTX 4090]  subgroup=32  basic/vote/ballot/shuffle=1/1/1/1
[0 NVIDIA GeForce RTX 4090]  fp16-8x8x16/16x8x8/16x8x16/16x16x16=0/1/1/1
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  queueC=1[4]  queueG=0[1]  queueT=0[1]
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  fp16-p/s/u/a=1/1/1/1  int8-p/s/u/a=1/1/1/1
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  subgroup=64  basic/vote/ballot/shuffle=1/1/1/1
[1 AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)]  fp16-8x8x16/16x8x8/16x8x16/16x16x16=0/0/0/0

Pure cpu inference is not planned.

CPUs don't have GPUs, you mean SoC

According to intel, "Integrated graphics is a GPU built into the processor". A System-on-a-Chip like the Apple M1 should be detected with this plugin as well. I know what was meant, but I don't plan on adding support for cpu inference. I was just showing what devices my system detects for reference.


feat: Able to pretty print sql query result in http output

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
#2877
What's changed and what's your intention?
src/servers/src/http.rs
src/servers/src/http/handler.rs
src/servers/src/http/table_result.rs
Able to pretty print sql query result in http output.
Like this:

Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
Format the output like Clikehouse's Pretty .
How does this PR work? Need a brief introduction for the changed logic (optional)
Caculate each column's max width, and then print the result.
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)
It does'not work well in browser.

Checklist

[ ]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.
[x]  This PR does not require documentation updates.

Cool! I like the result. Let me take a closer look at the implementation.


Handle the following lambda event

no one is taken care of this pr

@pypratik not really sure what the PR was about?


Use the new groupings for ViewModels in generated components

When generated a new component we should include the different groupings for derived, settable properties, functions, etc. Need to find a source for what these look like and bikeshed on it a little bit.

The logic guide shows these groupings: https://github.com/canjs/canjs/issues/4266

This is in major.


Updated detailed versions to 1.0.8

hmm... something has broken at some point...
I'll merge it manually.

Merged manually


Inline variable

Trivial change

Thanks for the interest, but this PR doesn't change anything meaningfully. Also, this fixture doesn't do any teardown, so there's no point yielding instead of returning.


Availability of code

Hello, may I inquire when the code for the paper will be made available?

Hello, may I inquire when the code for the paper will be made available?

We apologize for the delayed response and thank you for your interest in our work! We are currently organizing the code and will do our best to make it publicly available within this month!

@ChnQ Hi, will you be releasing the code?

Thank you for your interest in our work. The code has now been open-sourced. Thank you for your patience!


feat: finish web scraping on the backend

👨💻 Changes proposed(required)

change testing.js to phones.js
create phone search page

✔ Check List (Check all the applicable boxes)(required)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

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


better framework  Documentation

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: Darwin bicepjai-mac.local 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
Python Version: Python 2.7.11
Python Bitness: 64
How did you install Zipline: pip
Python packages:
bcolz==0.12.1
Bottleneck==1.0.0
cachetools==1.1.5
click==4.0
contextlib2==0.4.0
cyordereddict==0.2.2
Cython==0.22.1
decorator==4.0.0
epydoc==3.0.1
intervaltree==2.1.0
Logbook==0.12.5
multipledispatch==0.4.8
networkx==1.9.1
numexpr==2.4.6
numpy==1.11.0
pandas==0.16.1
pandas-datareader==0.2.1
patsy==0.4.0
python-dateutil==2.4.2
pytz==2015.4
requests==2.9.1
requests-file==1.4
scipy==0.15.1
six==1.10.0
sortedcontainers==1.4.4
SQLAlchemy==1.0.8
statsmodels==0.6.1
toolz==0.7.4
zipline==1.0.0

Now that you know a little about me, let me tell you about the issue I am
having:
I am trying to understand the framework better such as class hierarchies and as such.
Description of Issue
when i run
(master)[zipline]$ PYTHONPATH=. && epydoc --pdf zipline

What did you expect to happen?
generate document

What happened instead?

(master)*[zipline]$ PYTHONPATH=. && epydoc --pdf zipline
+-----------------------------------------------------------------------------------------
| In /Users/bicepjai/Projects/softwares/zipline/zipline/__init__.py:
| Source code parsing failed (but introspection was successful).
|     Error: Error during parsing: invalid syntax (/Users/bicepjai/Projects/softwares/
|            zipline/zipline/__init__.py, line 19) -- Attempted relative import in
|            non-package, or beyond toplevel package
|
+-----------------------------------------------------------------------------------------
| In /Users/bicepjai/Projects/softwares/zipline/zipline/dispatch.py:
| Import failed (but source code parsing was successful).
|     Error: NameError: name 'namespace' is not defined (line 19)
|
Warning: Unable to extract the base list for zipline.finance.execution.ExecutionStyle: Bad
         dotted name
Warning: Unable to extract the base list for zipline.finance.cancel_policy.CancelPolicy:
         Bad dotted name
Warning: Unable to extract the base list for zipline.finance.slippage.SlippageModel: Bad
         dotted name
Warning: Unable to extract the base list for zipline.finance.controls.TradingControl: Bad
         dotted name
Warning: Unable to extract the base list for zipline.finance.controls.AccountControl: Bad
         dotted name
Warning: Unable to extract the base list for zipline.pipeline.engine.PipelineEngine: Bad
         dotted name
Warning: Unable to extract the base list for zipline.pipeline.term.Term: Bad dotted name
      00:03                                 Progress:                                 01:46
  3% [===----------------------------------------------------------------------------------]
      Building documentation: zipline.pipeline.term (/Users/bicepjai/Projects/softwares/...

UNEXPECTED ERROR:
data type not understood

Use --debug to see trace information.

Here is how you can reproduce this issue on your machine:
Reproduction Steps

goto zipline folder
just try running epydoc --pdf zipline

What steps have you taken to resolve this already?
im trying to reach out to the community
Sincerely,
jay

For Zipline we use sphinx to generate our docs. This is what you see on zipline.io. If you would like to build the docs locally, you can cd into docs/ and run make html and then open up the pages with $BROWSER build/html/index.html

I was looking for more like module explanations like lean-block-diagrams


Add explicit dev setup for easy contributions

[ ] ESLint
[ ] Prettier
[ ] VSCode workspace settings and recommended extensions (ESLint, Prettier, etc.)
[ ] .editorconfig for the others
[ ] Husky, Commitlint and Commitizen with pre-commit / pre-push hooks

Note that this is part of growing our quality score on npms / npmjs.com quality index:
quality =
  carefulness: calculateScore(quality.carefulness, aggregation.carefulness, 0.8),
  tests: calculateScore(quality.tests, aggregation.tests, 0.7),
  health: calculateScore(quality.health, aggregation.health, 1),
  branding: calculateScore(quality.branding, aggregation.branding, 1),

  weightedMean([
    [scores.carefulness, 7], // 0.87, 7 (ESLint config needed)
    [scores.tests, 7],       // 0.85, 7 (CodeCov / Coveralls instead of CodeClimate :-/)
    [scores.health, 4],      // 1.00, 4
    [scores.branding, 2],    // 0.60, 2 (need custom Homepage, e.g. GH Pages)

  // => 0.87 * 7 + 0.85 * 7 + 4 + 0.6 * 2 = 86,2% (npm dit 78% !)
  // Avec ESLint configuré => 90,8%
  // Avec ESLint + custom HP => 94,7%
  // Avec ESLint + custom HP + CodeCov pour les tests => 100%

All these measures have been implemented, closing.


Unexpected token import when using TypeScript and Jest examples

I'm encountering a weird issue with either Babel or Next.js when trying to run TypeScript jest tests.
I can run the Jest test written in plain ol' JavaScript just fine, but the Footer.test.tsx file fails with an unexpected token import message:
`
PASS  ./demo.test.js
FAIL  components/Layout/Footer/Footer.test.tsx
● Test suite failed to run
/Users/rob/repos/crypto-insights/src/web/components/Layout/Footer/Footer.test.tsx:3
import { shallow } from 'enzyme'
^^^^^^

SyntaxError: Unexpected token import

  at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:318:17)

`
Using the Next.js examples with-jest and with-typescript, I've got the following configuration in place:
// tsconfig.json {   "compilerOptions": {     "jsx": "react-native",     "module": "commonjs",     "strict": true,     "target": "es2017"   } }
// .babelrc {   "env": {     "development": {       "presets": ["next/babel"]     },     "production": {       "presets": ["next/babel"]     },     "test": {       "presets": [["next/babel", { "preset-env": { "modules": "commonjs" } }]]     }   } }
// jest.config.js module.exports = {   setupFiles: ['<rootDir>/jest.setup.js'],   testPathIgnorePatterns: ['<rootDir>/.next/', '<rootDir>/node_modules/'],   testRegex: '\\.test\\.*',   moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx'],   collectCoverageFrom: [     '!jest.setup.js',     '**/*.{js,jsx,ts,tsx}',     '!build/**',     '!coverage/**'   ] }
`// jest.setup.js
import { configure } from 'enzyme'
import Adapter from 'enzyme-adapter-react-16'
configure({ adapter: new Adapter() })
`

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
Shouldn't I be able to run my jest test written in TSX:
`// Footer.test.tsx
import { shallow } from 'enzyme'
import { Footer } from './Footer'
describe('Footer', () => {
it('should render', () => {
const wrapper = shallow()
expect(wrapper).toBeDefined()
})
})
`
Current Behavior
I can run the Jest test written in plain ol' JavaScript just fine, but the Footer.test.tsx file fails with an unexpected token import message:
`
PASS  ./demo.test.js
FAIL  components/Layout/Footer/Footer.test.tsx
● Test suite failed to run
/Users/rob/repos/crypto-insights/src/web/components/Layout/Footer/Footer.test.tsx:3
import { shallow } from 'enzyme'
^^^^^^

SyntaxError: Unexpected token import

  at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:318:17)

`
Any help would be appreciated. Thanks!!

Next 5 just went out, can you try it out and the plugin for typescript too ?

Heya. I’m experimenting with Next 5, and I have come across a few oddities. The good news is that I was able to get the typescript and scss plugins to work in dev mode…
The bad? I’ve created a demo project to highlight some of those concerns:
https://github.com/TheRobBrennan/demo-nextjs-v5 https://github.com/TheRobBrennan/demo-nextjs-v5
The two big issues I’ve encountered so far are:
SCSS is working for dev mode but NOT for production
Redux is connected and works within the app; but it DOES NOT WORK with simple testing...why? pages/redux.test.tsx has a test that calls attention to this for the time being.
Of note, I’m using the same test that worked fine in Next 4, so…something is a little different…Not sure whose domain that falls into, though.
Rob Brennan |<EMAIL_ADDRESS>Phone<PHONE_NUMBER>
Skype      The.Rob.Brennan
Web         http://www.woatw.com
http://www.therobbrennan.com

On Feb 5, 2018, at 3:00 PM, Luis Fernando Alvarez D<EMAIL_ADDRESS>wrote:
Next 5 just went out, can you try it out and the plugin for typescript https://github.com/zeit/next-plugins/tree/master/packages/next-typescript too ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/zeit/next.js/issues/3663#issuecomment-363250713, or mute the thread https://github.com/notifications/unsubscribe-auth/AD2AGgef1VADTPN9j6QbtSnjcTkDHdcGks5tR4gIgaJpZM4R3pba.

I'm running into an issue that might or might not be related to this.
I'm using mapbox-gl. Usually one would simply import the commonjs entrypoint, but instead I'm importing mapbox-gl/src using another babel-loader to transpile these files. Like so:
import MapboxMap from 'mapbox-gl/src/ui/map';

Since mapbox-gl/src is es6+flow, I configured next.config.js like so:
module.exports = {
  webpack: config => {
    config.module.rules.push({
      test: /mapbox\-gl\/src\/.+\.js$/,
      loader: 'babel-loader',
      options: {
        presets: [
          'babel-preset-flow',
          'babel-preset-env',
        ],
        plugins: [
          'babel-plugin-static-fs',
          'babel-plugin-transform-class-properties'
        ]
      }
    });

    return config;
  }
};

running next works, but after triggering build by requesting http://localhost:3000 I get this error:
/Users/aleksey/my-project/node_modules/mapbox-gl/src/ui/map.js:30
import type {LngLatLike} from '../geo/lng_lat';
^^^^^^

SyntaxError: Unexpected token import

These import statements should have been babelified out (as seen by the intermediaries produced inside .cache: gzcat node_modules/.cache/babel-loader/a2b2aa6e1bdb254f0db2d539f7b03e24a389bbb7.json.gz | jq -r  .code), but I think some webpack plugin that's loaded by next is ignoring the transpiled file, and using a require() instead.

@TheRobBrennan is this still relevant?

@timneutkens I don't believe so. Everything seems to be in a great place.

how closed this issue? I run into the same issue as well.

how closed this issue? I run into the same issue as well.
same

same here with 6.0.0-canary.2 / node 8.11.1
Spent some time trying different versions (starting with a merge of copy+paste from examples).
e.g:
"dependencies": {
    "next": "6.0.0-canary.2",
    "react": "16.2.0",
    "react-dom": "16.2.0"
  },
  "devDependencies": {
    "@types/next": "2.4.8",
    "@types/react": "16.1.0",
    "@zeit/next-typescript": "0.1.1",
    "enzyme": "3.3.0",
    "enzyme-adapter-react-16": "1.1.1",
    "jest": "22.4.3",
    "react-test-renderer": "16.3.0",
    "typescript": "2.8.1"
  }

No avail ...

The example project works fine. Trying to get it to work in an actual project always fails.
My theory: There is something wrong with the compile steps and actual compile errors get swallowed. Then afterwards it tries to use the uncompiled .tsx and fails.

@timneutkens @TheRobBrennan can we get this issue re-opened or should we create a new one?

Sure - reopened 😊

I was using "with-jest-typescript" example and ran into this problem, looks like changing  tsconfig.json compilerOptions.jsx from "preserve" to "react" gets the tests running, but breaks the app.
So ended up with custom tsconfig.jest.json
// tsconfig.jest.json
{
  "extends": "./tsconfig",
  "compilerOptions": {
    "jsx": "react"
  }
}

and updated the test.config.js
...
  globals: {
    "ts-jest": {
      useBabelrc: true,
      tsConfigFile: "tsconfig.jest.json"
    }
  },
...

Upon @makstr 's suggestion, if you face trouble resolving modules, try
{
  "extends": "./tsconfig",
  "compilerOptions": {
    "jsx": "react",
    "module": "commonjs"
  }
}

as mentioned in ts-jest doc.
The tsconfig.js 's compilerOptions is set to esnext.

Should be solved with the Next 7 rewrite of next/dynamic.


S2n leaks

Description of changes:
Fixes potential memory leaks
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2410 (1f20d07) into main (c2741f7) will decrease coverage by 0.12%.
The diff coverage is 37.50%.

@@            Coverage Diff             @@
##             main    #2410      +/-   ##
==========================================
- Coverage   81.93%   81.80%   -0.13%
==========================================
  Files         270      269       -1
  Lines       18616    18425     -191
==========================================
- Hits        15253    15073     -180
+ Misses       3363     3352      -11


Exposed the mongoStore and passport objects

Exposed the mongoStore and passport objects in the amna object for more auth options in apps.

<EMAIL_ADDRESS>is released


Amend RFC 517: Add material for stdio

Expand the section on stdin, stdout, and stderr while also adding a new section
explaining the fate of the current print-related functions.
Rendered

The format!/write!/… macros should write only once, not call write(2) multiple times.

Then they have to allocate memory first which is not acceptable.

Maybe a new macro for that purpose then (e.g. formatbf!)?

So just write!(dst, "{}", format!(whatever))

Yeah, not sure we want to write this for each println!…

I think the move we made in old_io to providing a global stdin buffer, together with locking, has worked pretty well (thanks @sfackler!)
Personally, I would suggest the following variant of the design for consistency:

stdin as you proposed it,

stdout and stderr as also using a global lock (and, for stdout, global buffering), in particular so that conveniences like write_all behave atomically. Alternatively, we could skip the lock for stderr since it's unbuffered, if atomicity for convenience methods is not considered important enough.

_raw variants for all three (no locking or buffering) in std::io

Just to clarify why this kind of global design is useful, consider some alternatives:

We could just not buffer at all (basically, just expose the raw variants), but that would be a surprise to most people and would not be very ergonomic. If you failed to buffer, you'd pay in performance, and if you did buffer, you'd have to set it up yourself (probably including some kind of global to share the buffer between different functions). Centralizing this functionality with good defaults is worthwhile in my opinion.

We could forgo the atomicity but retain semi-global buffering by allocating buffers in a thread-local way  (dropping the locks). By buffering thread-locally, we would (1) ensure that buffering happens and (2) avoid problems like stdin().read_line(..); stdin().read_line() creating multiple buffers. But the stdin handle would be effectively unusable across threads, since even if e.g. those thread we're coordinating when to read lines, data would be locked away in one thread's buffer when another tried to read.

On the other hand, of course it's important to provide all of the raw handles to that people can build their own buffering/coordination strategy without paying any cost.
I don't think the RFC says where these constructors should live, but I would propose std::io for all of them (including the raw variants).

@aturon

Personally, I would suggest the following variant of the design for consistency:

I like the sound of all this. I've pushed an update which includes:

All global handles are locked by default.
The stdout handle is now globally buffered
Raw versions of each handle have been added as foo_raw for each respective version.
APIs and trait implementations sketched out.

@l0kod

The format!/write!/… macros should write only once, not call write(2) multiple times.

As @mahkoh mentioned these are fundamentally unable to prevent many calls to the Write::write function without some form of intermediate buffering. It is likely that objects used with write! will need to use some form of buffering to ensure reasonable performance. This is why, for example, the stdout stream is buffered-by-default. Today each call to println! is likely to only invoke write(2) once.

BTW, I strongly suggest we land some preliminary version of this ASAP, since we need to start getting feedback on the new APIs. We can and should be very clear that none of it will be stabilized until the RFC is finalized, of course.

I have created a PR for this RFC, but I would like to stress that it is not final at all. We need to implement these APIs to allow crates to migrate to std::io which facilitates the rapid implementation, but it's perfectly ok for the RFC to diverge from the implementation and all changes will be implemented promptly upon acceptance of this RFC.

Don't forget the FromRawFd trait ;)

This API looks really like a custom implementation of a general file-descriptor/handle type (e.g. IoHandle/IoDesc).
It would be nice to have an inner (common) file descriptor type with the lock feature (cf. Lazy<Mutex<T>>).

@l0kod

Don't forget the FromRawFd trait ;)

We're currently leaving that for a future RFC as it's only somewhat tangentially related to the stdio bits of this RFC.

This API looks really like a custom implementation of a generic file-descriptor/handle type

I agree! We're just not ready at this time to commit to that kind of an API.

I've pushed an update which is pretty different in how the raw input/output handles are dealt with, especially on windows.  At this point I would be content with stdout_raw and friends simply returning io::Result<StdoutRaw> and friends on all platforms.

The set_stdout and set_stderr functions will be moved to a new
std::fmt::output module and renamed to set_print and set_panic,
respectively. These new names reflect what they actually do, removing a
longstanding confusion. The current stdio::flush function will also move to
this module and be renamed to flush_print.

set_stderr should be called set_error_print and should be accessible via println_err and print_err macros or similar. Furthermore these Writers should be stored in Mutexes and be inherited by child threads. It's currently not possible to capture the full output of a thread because the thread can itself spawn child threads which don't inherit the stdout and stderr. This can be seen when one uses multithreaded tests.

I've pushed an update which recommends that the raw stdio primitives are not implemented or stabilized at this time. Otherwise the interface remains the same and continues to be somewhat high level. It's quite similar to what's implemented today, but a few tweaks will be necessary for the implementation.
The update also revises that std::fmt::output will not be added at all, it will be removed with no replacement.

@mahkoh I agree there are some interesting questions around std::fmt::output and I've removed it from the RFC.

Hm, the windows behaviour seems to be very "fancy" to me, less minimal than we might hope for std. However, it seems the problem itself is sufficiently complicated that it may not be possible to get a totally minimal resolution while maintaining some semblance of sanity. (I do not know enough about IO on windows to judge with much precision.)

Hm, the windows behaviour seems to be very "fancy" to me, less minimal than we might hope for std. However, it seems the problem itself is sufficiently complicated that it may not be possible to get a totally minimal resolution while maintaining some semblance of sanity.

I agree, I'm not super comfortable about this either. I've been considering it a hard constraint though that the stdio handles must implement Read and Write, and given that I think that this is basically the most reasonable thing to do on windows for now. I personally also think that giving access to the raw handles when possible will also help quite a bit.

This still doesn't address writing to stderr. Having to create your own thread local variable just to do some error reporting is annoying.

@mahkoh

This still doesn't address writing to stderr. Having to create your own thread local variable just to do some error reporting is annoying.

Can you clarify where this thread local variable is coming from? The new primitives are not thread local, and the std::fmt::output module is not being added and the old functionality is being removed.

@alexcrichton one thing I found confusing in the current text was the discussion of locking. It wasn't clear to me whether the value returned by stdin itself performed locking, or whether that was the responsibility of the client. In particular this text feels ambiguous:

All operations on this handle will first require acquiring a lock to ensure access to the shared buffer is synchronized. The handle can be explicitly locked for a critical section so relocking is not necessary. The Read trait will be implemented directly on the returned Stdin handle but the BufRead trait will not be (due to synchronization concerns). The locked version of Stdin will provide an implementation of BufRead.

It may be that this text is implicitly referencing the existing API or other things with which I am unfamiliar? In general though this text sounds to me as if the locking is something the user does ("first require acquiring a lock", "relocking is not necessary", "ButRef trait will not be impemented"), but there is no coverage of what API would be offered. I am guessing that I am misinterpreting this paragraph though.

@nikomatsakis I tried to clarify that section a bit to make it a little more explicit, but let me know if anything is off!

This RFC has now been merged. It is a conservative refinement of the previous incarnation of stdio handles, in particular clarifying the interaction with Windows consoles/unicode requirements.
We will definitely need to revisit this topic to introduce raw handles and redirection for println and panic, but that can all be added backwards-compatibly.

but that can all be added backwards-compatibly.

No it cannot. The RFC says that stdout() writes to the stdout of the process, that is, it's equivalent to writing to fd 1. Code that needs this guarantee would have to be changed if at any point stdout() can become thread specific.

@mahkoh
I'm not referring to changing the target of stdout; I'm talking about the target of println and panic. In principle code could be assuming that these macros target fd 1, but I expect their contract to not actually make such a promise given the intent to allow redirection later.

What are you thinking that you'd consider having println write to something other than stdout() a good design? How does println not just being a shortcut for writeln!(stdout(), ...).unwrap() be acceptable?

Stdout/in/err are unlikely to ever become thread local again. We used that design in old_io and it didn’t work out. Now we have one a single handle and are locking for thread safety instead.
Regarding println! redirection: we already have writeln! macro, which is basically a println! with an argument to specify output writer.

@nagisa: How did it not work out? Why do you think that that implies that it cannot work out?

Regarding println! redirection: we already have writeln! macro, which is basically a println! with an argument to specify output writer

Then libraries that want to allow having their output captured cannot use writeln? And they cannot write anything to stderr?

For example, it is a serious problem in some terminal programs that you cannot capture the output of libraries which then mess up your output. You have to hack around this by replacing fd 1 and 2 temporarily with /dev/null before library calls (e.g.). The rust stdlib should not inherit this problem.

@mahkoh

What are you thinking that you'd consider having println write to something other than stdout() a good design? How can println not just being a shortcut for writeln!(stdout(), ...).unwrap() be acceptable?

The previous design made it possible to redirect println at the thread level, and in principle that redirection could be inherited -- while still keeping stdout as process level fd 1. Note, this RFC specifically does not take such a step, and I'm just saying that it was a part of the discussion that didn't come to a close here and should be followed up on soon.

For example, it is a serious problem in some terminal programs that you cannot capture the output of libraries which then mess up your output. You have to hack around this by replacing fd 1 and 2 temporarily with /dev/null before library calls (e.g.). The rust stdlib should not inherit this problem.

Right, so I'm wondering what proposal you have in mind? A few of your comments on this thread seem to be alluding to a design, but it'd help to see it spelled out a bit more explicitly.
My main point here is that the current RFC doesn't address these problems and so we need to revisit it.  Depending on the precise contract we give, it should be possible to add redirection later, but in any case we can probably address it before 1.0 regardless.

Right, so I'm wondering what proposal you have in mind?

See #973


Inconsistent type names

Reference: http://docs.diesel.rs/diesel/sql_types/index.html
Why is the I in BigInt capitalized but not the i in Tinyint?

#1807


Scenario compatibility

Prerequisite: #319
changes:

modified definition of node, edge, connections, and types to use integers and floats instead of strings
modified the definition of shapes in edges to include lists of (x,y) tuples instead of strings
modified the base scenario class to convert the integers, floats, and shapes to be compatible with sumo.

Pull Request Test Coverage Report for Build 2109

31 of 31 (100.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.04%) to 84.182%

Files with Coverage Reduction
New Missed Lines
%

flow/envs/bay_bridge/base.py
1
63.25%

Totals

Change from base Build 2107:
0.04%

Covered Lines:
6908

Relevant Lines:
8206

💛  - Coveralls


Storage Cost Reduction

Design Doc
Currently, every time we upload a new release version of HELM evaluations, we have to upload an entire run suite. Each release version is about 300 GB in size. This means that our storage cost is 300 GB times the number of release versions. However, the diff between the new release version and the previous release version is usually very small (e.g. a small number of runs added or modified).
This PR reduces the storage cost by allowing for uploading only the diff between release versions when a new release comes out.
We do this by modifying helm-summarize. The usage is helm-summarize --suites <list_of_run_suites> -- releases <release_name>. This would allow us to upload only the diff between the new release version and previous release version (in the form of a single run-suite) and then include runs in from previous suites in the release as well by simply including those suites in the --suites argument to helm-summarize. To release new results, we can simply upload the new diff run suites, and the new release version.

@yifanmai
Sorry for the delay. I have the CLI portion of the change done but have one issue on the frontend.
Last we spoke, I believe you said I could store a flag in the summary.json detailing whether or not we’re using a release (the new functionality) or a suite (the old functionality). However, we need to know which we’re using to be able to load the summary itself. (see here vs here, for instance — the summary can be in either the runs or releases directories.)
As such, I think we need a slightly different strategy. I see a few options:

Store the summary at another path that doesn’t depend on whether we use a release or a suite
Use the URL parameters to determine if we’re using release or suite. To keep things backwards compatible, we could default to suite if no URL parameters are specified but require that newer versions of HELM always specify a URLparameter like release=v1  or release=LATEST or suite=v2 . Then, we can use whichever is specified to know which we should use (i.e., if release=v1  is specified, then we know the user is using a release and we should read files from the benchmark_output/releases directory).
Disallow name collisions between suites and releases, and check both the summary URLs using the runs and releases directory. Only one will exist and from there, we'll know what the user is using.

Let me know what you would prefer and/or if you have other ideas for how to style this.

I need to think more about this... some initial thoughts:

Store the summary at another path that doesn’t depend on whether we use a release or a suite

Unfortunately this breaks reverse compatibility... the older data release won't have this file, so a newer frontend will break against an older release

Use the URL parameters to determine if we’re using release or suite. To keep things backwards compatible, we could default to suite if no URL parameters are specified but require that newer versions of HELM always specify a URLparameter like release=v1  or release=LATEST or suite=v2 . Then, we can use whichever is specified to know which we should use (i.e., if release=v1  is specified, then we know the user is using a release and we should read files from the benchmark_output/releases directory).

This is kind of okay but I have a slightly different suggestion that I'll discuss later. Also, putting an additional parameter is all the links is a bit tricky.

Disallow name collisions between suites and releases, and check both the summary URLs using the runs and releases directory. Only one will exist and from there, we'll know what the user is using.

This is a little weird because it means that a 404 will be part of normal operation for the new-style frontend. This is not great because 404 are usually reported as errors on the server or GCS, and that messes up monitoring. Also the 404 is not cached client side (I think) which means the frontend is permanently slower.
A couple more suggestions:

Add a release flag to helm-server; new style is only used when the release flag is specified. For static file deployment, this means setting the release as a JavaScript constant. User should use it like This is basically the same as your second suggestion, except that we're making the configuration a flag / JavaScript constant rather than having it be a url parameter.
Double-write summary.json to both runs and releases. Frontend reads the runs/run_suite/summary.json first. If the release_name field is set, it switches to new-style frontend and goes to releases/release_version/summary.json next. If the field is unset, it switches to old-style frontend.

Ah I see. Perhaps I'll try your suggestion 1); that sounds cleaner, I think.

There are still reverse compatibility issues. If I do helm-summarize on main and then run helm-server on this branch, the raw run pages and the Results > Core scenarios page don't work.
If you need any help with debugging this, I can take a look on Monday.

So, I checked doing helm-summarize with the main branch and it output the files exactly as I expected. The only thing is, I didn't test the thing you checked (Results > core scenarios) -- I only looked at raw results. (In other words, this was a problem even if I did the summarization in my branch -- I just didn't check this because I'm not super familiar with the web UI, so I only checked Raw Results).
Regardless, it was an easy fix -- it's just because I defined a variable in the wrong scope. If you pull it now, that should work. But, yes, I may need help checking that everything works if you have time Monday since I just haven't used the Web UI much. Sorry about that!

OK, so I fixed that issue and a few other minor bugs. To me, everything looks OK now, except that on my instance I get the following two errors in the console:

Whereas on the prod instance at https://crfm.stanford.edu/helm/latest/, I see one of the errors but not the other:

It should be noted that I see those same two errors in the console (for sample_train and multi_label) when I run helm-server from the main branch, too, though, so I'm assuming it's just to the run_specs config I used for my local runs.
Either way, to me, now, I don't notice any difference between the web UI from the main branch and from this branch on the following pages:

Raw Results
Raw Results > boolq:model=huggingface_gpt2
Results
Results > Core Scenarios

HOPEFULLY that means that, finally, the backwards compatibility is there and we're OK. Sorry about all the back-and-forth.

Thanks, this looks good now! The new error is a result of adding a new field in #1785. I think I want to keep the console logging but downgrade it to a warning; I'll send you a PR for it.


adds support for AsyncIterator in cursors, and adds single file responsible for loading esnext tests

Fixed NODE-1684
CC @vkarpov15

Nice! Looking forward to writing a blog post about this :)

This PR broke my team's last production deploy because it introduces a feature only available in newer node releases.  Is there a reason this was accepted while breaking backwards compatibility without a major version bump?

@majorhayes the Node10+ code is hidden behind feature detection, and should only be pulled in if you have support for it. What version of node are you using, and are you using any additional runtimes or compilers on top of it?

I read in the release notes that what you described was the intention.  We're running 8.11.3 in production without any build process.
The error is that node 8.11.3 crashes while parsing the file.  Maybe there's an issue with the file getting required when it shouldn't be?
async function* asyncIterator() {
              ^

SyntaxError: Unexpected token *

@majorhayes we actively test against all major supported versions of node (and some no-longer-supported versions). You can see here the most recent test against v8.15.1 working without issue. We have another report this morning of breakage over in NODE-1908 that's related to transpiling the driver, which is something we do not actively test. Is it possible that something similar is happening in your environment?
NOTE: I just installed v8.11.1 locally, and ran the test suite without incident.

Did some digging. It turns out one of the packages that we require uses babel-polyfill. So, while we don't use babel directly, this module does, which causes Symbol.asyncIterator to be defined, but node still is unable to parse the async_iterator.js file.
I think a more robust feature detection should be used, perhaps a try/catch around the require statement.

@majorhayes Thank you so much for looking into this, and many apologies for the disruption. We're working on a patch release presently and will make sure this fix gets in.

I really appreciate your quick and courteous response.

@majorhayes v3.2.2 has just been released, it should resolve your issue. Thanks again for letting us know.


How to fix the rope end with a site?

Hi, I am new in Mujoco. I'm looking for some help with acquiring the rope end 3D coordinates position.

FIrstly, as far as I refer the tutorial, it seems that we can only know the start coordinate of rope rather than the end one.  Also, only two methods can provide "pos" information: directly define the "pos" coordinate or using "joint" attribute "ref". If I add a joint at the end of rope, they cannot be connected. Therefore, could you provide me a tip how to get the rope end coordinate?

Secondly, I tried my best to find other solution to solve the problem, for example, I defined a new small "capsule" type body, and connect it with the rope end, so I can receive the almost same coordinate of rope end. But I also find the capsule would float, then the rope end would separate from it. I think using "anchor" attribute can solve it but actually not. I am not sure if I should twick the param or other params, such as "solimp", the "pos" of two bodies or else.

Here is a model which explains my question:
reacher_update.txt
Here is a screenshot / video, illustrating my question:

Thanks!

I'm not really sure what you actually did in your second point, but if all you want is the position of the tip of the rope, you should add a <site> in the innermost body, make sure that it's positioned correctly within that body so that it's at the tip of your last capsule, then read what you want from d->site_xpos.

@saran-t  Thanks for your answer! Actually, the sencond point is very similar with the "site" method, so just leave it now.
By using the function of site, I could know the last capsule position. But when I rotate the arms, the end of rope would be detached with the "site".  What should I do to fix them together, so whatever the arm rotates, the "site" would reprsent the rope end position?

I tried  but  is not a body, so I cannot connect them. Also,  if I using ,  it would not match my physical model because I just need a rope and the position of the rope end.

Maybe you could still use equality constraints between the arm and the rope's body, and use the "relpose" attribute in the xml to set it according to where the site / rope end is.

@Balint-H  Hi, I follow your advice but receive an error:
XML Error: Schema violation: unrecognized attribute: 'relpose'
this is the code,  it seems not support "relpose" attribute
<equality>         <connect body1="body1" body2="CB9" anchor="0 0 0" relpose="0 0 0.38 0 0 0 0" />     </equality>

Hello, relpose is only available in the weld type equality constraints. With it you can define any spatial relationship, even if its not satisfied at the start (at which point it will quickly snap to satisfy it). weld also constrains orientation to match as well, which might be fine for your case or not. If not, you should stick to connect, however then the constraint is assumed to be satisfied at the start. You should move the target to the end of the rope in the MJCF, and define the anchor location from body1's frame of reference to be the tip of the rope. In this case you can remove the fingertip object and connect the target to CB9 directly.

Thank you! I find another instead method, which is defining a very small freejoint box at the end of rope. Thus I would track the rope end, but I am not sure if it would affect my simulation result. And I would also try your suggestion later.

I would close the issue because I find a way to solve the question. We can set two sites between the second joint end and tip, then using tendon to connect them.

Thank you! I find another instead method, which is defining a very small freejoint box at the end of rope. Thus I would track the rope end, but I am not sure if it would affect my simulation result. And I would also try your suggestion later.

would you like to show this method to us? that would be a major help to me. Thank you in advance!


Add Score

Hey @Priyanshi662 I would like to Add score and high score in Archery Game which will enhance user experience.

Please assign it to me under JWOC

@itsmeabhishek03 progress?

hey @Priyanshi662 will raise PR soon will that be okay ?

@itsmeabhishek03 I'll be closing this issue, since it has been too much time


ImportError: dowhy is no longer a dependency of the main econml package; install econml[dowhy] or econml[all] to require it, or install dowhy separately to use dowhy from econml

import dowhy
import econml.dowhy
est = LinearDML(model_y=GradientBoostingRegressor(), model_t=GradientBoostingRegressor(),
featurizer=PolynomialFeatures(degree=2, include_bias=False))
est_dw = est.dowhy.fit(Y, T, X=X, W=W, outcome_names=["log_demand"], treatment_names=["log_price"], feature_names=["income"], confounder_names=confounder_names, inference="statsmodels")
ImportError: dowhy is no longer a dependency of the main econml package; install econml[dowhy] or econml[all] to require it, or install dowhy separately to use dowhy from econml

The error message indicates that dowhy is not installed.
you can install dowhy separately. Do you see the message even after installing dowhy?

i have installed dowhy，but the error still  exists.
I found that this error is related to the version of Python, and it will appear in the latest version of Python
---- Replied Message ----
| From | Amit @.> |
| Date | 07/12/2023 19:28 |
| To | py-why/dowhy @.> |
| Cc | Yif18 @.>,
Author @.> |
| Subject | Re: [py-why/dowhy] ImportError: dowhy is no longer a dependency of the main econml package; install econml[dowhy] or econml[all] to require it, or install dowhy separately to use dowhy from econml (Issue #969) |
The error message indicates that dowhy is not installed.
you can install dowhy separately. Do you see the message even after installing dowhy?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


[5.5] [WIP][Moved] Added password argument to Encrypter, and new methods encryptWithPassword/encryptStringWithPassword

I am building an application that requires user input password encrypted data. Currently Laravel defaults to using the APP_KEY as the encryption password. I added updates that will allow users to pass in a custom password string to the encrypt, encryptString, decrypt, and decryptString methods. If no password, the default APP_KEY will be used. This update will allow Laravel users to easily add custom passwords to their encrypted data.
In an age of domestic surveillance and data warehousing, it is crucial that developers can easily access the encryption tools needed to provide users secure data.
This is an updated version of: https://github.com/laravel/framework/pull/18090

This has been updated, and the tests are passing. Is there anyone that can provide feedback or review? Thanks.

No need for any of this. All you need to do is:
$encrypter = new Encrypter('key', 'cipher');

The goal was not to change the cipher, but to change the password used to encrypt the data. This should not have been closed.


Exclamation mark ("!") in Python interactive session ouput get the the "err" class

(Original issue 947 created by vrutsky on 2014-01-09T13:46:19.418168+00:00)
See following example:
>>> print "test! another!"
test! another!
>>> import pygments
>>> pygments.__version__
'1.6'
>>> from pygments.lexers import PythonLexer
>>> from pygments.formatters import HtmlFormatter
>>> from pygments import highlight
>>> s = u"""
... >>> print "test! another!"
... test! another!
... """
>>> s
u'\n>>> print "test! another!"\ntest! another!\n'
>>> highlight(s, PythonLexer(), HtmlFormatter())
u'

>>> print "test! another!"\ntest! another!\n

\n'
>>>

(Original issue 947 last updated on 2014-01-09T15:19:30.603320+00:00)
(Issue automaticaly closed due to status in Bitbucket: invalid)

(Original comment by birkenfeld on 2014-01-09T14:16:01.737290+00:00)
Hi,
for Python console output you should use the "python console" lexer. It will not apply Python highlighting for lines not starting with >>>/...

(Original comment by vrutsky on 2014-01-09T15:19:30.600337+00:00)
Yes, using pygments.lexers.PythonConsoleLexer helps, thanks!
In markdown or command line pycon format specification helps.


MSCRM Export Solution: An Unexpected Error occurred

In my Solution Export VSTS task an Exception is thrown. After setting debug mode this is the stack trace with the most usefull errormessage. When I export the solution manually no errors occur.
Message: System.AggregateException: One or more errors occurred. ---> System.Security.Cryptography.CryptographicException: Keyset does not exist
2018-12-07T08:05:48.0559799Z ##[debug]
2018-12-07T08:05:48.0581628Z ##[debug]   at Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationContext.RunAsyncTask[T](Task`1 task)
2018-12-07T08:05:48.0600006Z ##[debug]   at Microsoft.Crm.ObjectModel.CanvasAppTokenService.RetrieveToken()
2018-12-07T08:05:48.0629944Z ##[debug]   at Microsoft.Crm.Tools.Core.ImportExportPublish.CanvasAppHandlerInternal.d__20.MoveNext()
2018-12-07T08:05:48.0648010Z ##[debug]--- End of stack trace from previous location where exception was thrown ---
2018-12-07T08:05:48.0668184Z ##[debug]   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2018-12-07T08:05:48.0686062Z ##[debug]   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2018-12-07T08:05:48.0706178Z ##[debug]   at Microsoft.Crm.Tools.Core.ImportExportPublish.CanvasAppHandlerInternal.d__19.MoveNext()
2018-12-07T08:05:48.0724491Z ##[debug]   --- End of inner exception stack trac...).

I did some more research on the error and it only occurs when you have a Canvas app in the dynamics solution. When I remove the Canvas app I can export the solution normally. This is a new feature in the Dynamics solution structure.

@JoostVeldhuis Thanks for the update much appreciated. I would suggest you raise a case with MS as this is likely caused by the backend. Let me know if there are any changes I can do to make this work.


Feature/arbitrary meta options

Adding ability to add arbitrary options to fields

Closing in favor of https://github.com/lara-zeus/bolt/pull/301


WSO APIM 3.2 - POST, PUT and DELETE requests are not working with Class Mediator

Affected Product Version:
WSO2 API Manager 3.2
Following are the environment details for above issue scenario.

OS: Linux (Ubuntu 20.04)
Client: Postman and Inbuilt Swagger
Env (Docker/K8s): Standalone

Description:
I have deployed a sample Rest service which accept HTTP methods of GET, POST, PUT and DELETE methods and returns a dummy output.
Then I have proxy above REST service through WSO2 API Manager (3.2 version) by creating a new service and providing above REST endpoint as the back end endpoint.
Above attempt was successful without any issue.
Then I created a custom class mediator by following the documentation at : https://apim.docs.wso2.com/en/3.2.0/learn/api-gateway/message-mediation/adding-a-class-mediator/
My class mediator is as follows,
public class DummyMediator extends AbstractMediator {
    private static final Log log = LogFactory.getLog(DummyMediator.class);
    public boolean mediate(final MessageContext synCtx) {
        log.info("Mediating through dummy mediator...");
        return true;
    }
}

I have configured above custom mediator to be used in global manner by defining the sequence xml file under : repository/deployment/server/synapse-configs/default/sequences
<?xml version="1.0" encoding="UTF-8"?><sequence xmlns="http://ws.apache.org/ns/synapse" name="WSO2AM--Ext--In">
    <class name="com.mediator.DummyMediator"/>
</sequence>

Above attempt was successful, but the response is only returning in GET requests. For other HTTP methods (such as POST) WSO2 is not returning the intended response from back end. It simply hangs and return timeout error as follows,
[2022-01-27 17:11:04,833]  INFO - DummyMediator Mediating through dummy mediator...
[2022-01-27 17:12:23,108]  INFO - EndpointContext Endpoint : dummythree--v1.4_APIproductionEndpoint with address http://localhost:9595/mock/dummy has been marked for SUSPENSION, but no further retries remain. Thus it will be SUSPENDED.
[2022-01-27 17:12:23,109]  WARN - EndpointContext Suspending endpoint : dummythree--v1.4_APIproductionEndpoint with address http://localhost:9595/mock/dummy - current suspend duration is : 30000ms - Next retry after : Thu Jan 27 17:12:53 IST 2022
[2022-01-27 17:12:23,110]  INFO - LogMediator {api:admin--dummythree:v1.4} STATUS = Executing default 'fault' sequence, ERROR_CODE = 101504, ERROR_MESSAGE = Send timeout
[2022-01-27 17:12:23,171]  WARN - TimeoutHandler Expiring message ID : urn:uuid:72a608e8-4860-40ec-921e-cc1b210facc1; dropping message after GLOBAL_TIMEOUT of : 120 seconds for null, URI : http://localhost:9595/mock/dummy, Received through API : admin--dummythree:v1.4

However, When I tried above same steps in WSO2 APIM 4.0 version, everything works fine - means I can get response for all HTTP methods.
I would like to know whether this behavior is a known issue in WSO2 APIM 3.2 version and any workaround to fix it.

This issue seems to be fixed in wso2am-<IP_ADDRESS> patch version.


Publish 04/07/2022, 10:30 AM

Docs Build status updates of commit 0cfd181:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoStorageQuota.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


CRI-O: add e2e branch tests

Add branch tests to be used in postsubmits over at openshift/release https://github.com/openshift/release/pull/498
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

@mrunalp @stevekuznetsov PTAL

@stevekuznetsov took care of your comments :)

@runcom do the XML generation in a new PR :)

@runcom do the XML generation in a new PR :)

yup, I'm doing it in https://github.com/openshift/aos-cd-jobs/pull/945


IPv6

Add ipv6 flag and field to kurl spec
Detect ipv6 ip and use as private address
Update curl commands to work with ipv6 ips
Configure host sysctls for IPv6
Configure latest antrea and rook addon versions to work with IPv6
Local registry uses cluster DNS name on host since images tagged with IPv6 ip are an invalid reference
Make skaffold work without vandoor db

Thanks @DanStough , could you merge?

docs need to be written for kurl.sh

[sc-30387]


v1.1 Release

Hello, I would like to use the java.time.Instant implementation. What needs to be done to get to a v1.1 release ?

Published 0.2.0 right now.


VCQ 171989 - VCQ: RWS Moravia: [Source issue] [Incomprehensible instruction]

Please check this source string and see if it needs to be updated, the highlighted part is not clear: "Arrange the text box to the left of the button, aligned next to the text box, as shown below:"
I guess it should be "Arrange the text box to the left of the button, aligned next to the button, as shown below:". Another option could be: "Arrange the text box to the left of the button, aligned with the text in the button, as shown below:".

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

ID: 48ba6a76-eb0b-e8f2-dfc9-d2c0df6261a4
Version Independent ID: 8d62fdee-f44a-3d40-6800-04d7bd6193f8
Content: Get started with WebView2 in WinForms apps - Microsoft Edge Development
Content Source: microsoft-edge/webview2/get-started/winforms.md
Product: microsoft-edge
Technology: webview
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for filing this. I'll open a task on our backlog to take care of this.

Thankyou

The screenshot below the instructions do show a baseline alignment overlay (a pink line that is aligned with where the text sits in the button, and where the text will also be aligned in the textbox). So I believe the right wording should be:
"Arrange the text box to the left of the button, aligned with the text in the button, as shown below".

Got it thanks!


Signature extraction failed: Traceback (most recent call last)

C:\Users\Walves>youtube-dl --version
2018.12.09
C:\Users\Walves>youtube-dl -F https://www.youtube.com/watch?v=dhQ5IC0NGUM
[youtube] dhQ5IC0NGUM: Downloading webpage
[youtube] dhQ5IC0NGUM: Downloading video info webpage
[youtube] dhQ5IC0NGUM: Downloading js player vfl4UMq4Z
ERROR: Signature extraction failed: Traceback (most recent call last):
File "e:\program files\python\lib\site-packages\youtube_dl\extractor\youtube.py", line 1225, in _decrypt_signature
video_id, player_url, s
File "e:\program files\python\lib\site-packages\youtube_dl\extractor\youtube.py", line 1132, in _extract_signature_function
errnote='Download of %s failed' % player_url)
File "e:\program files\python\lib\site-packages\youtube_dl\extractor\common.py", line 777, in _download_webpage
raise e
File "e:\program files\python\lib\site-packages\youtube_dl\extractor\common.py", line 772, in _download_webpage
expected_status=expected_status)
File "e:\program files\python\lib\site-packages\youtube_dl\extractor\youtube.py", line 267, in _download_webpage_handle
*args, **compat_kwargs(kwargs))
File "e:\program files\python\lib\site-packages\youtube_dl\extractor\common.py", line 642, in _download_webpage_handle
content = self._webpage_read_content(urlh, url_or_request, video_id, note, errnote, fatal, encoding=encoding)
File "e:\program files\python\lib\site-packages\youtube_dl\extractor\common.py", line 692, in _webpage_read_content
webpage_bytes = urlh.read()
File "e:\program files\python\lib\http\client.py", line 461, in read
s = self._safe_read(self.length)
File "e:\program files\python\lib\http\client.py", line 609, in _safe_read
raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(524288 bytes read, 567781 more expected)
(caused by IncompleteRead(524288 bytes read, 567781 more expected)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Network issue on your side.


dependabot.yml for CI Docker and Github actions

First dependabot.yml file for version updates. By way of example it includes a simple initial configs for the existing CI Dockerfile and Github actions.
Associated repo UI config to enable dependabot is:

Go to "Security (tab)/Code security and analysis (side tab)/Dependabot"
Enable:

Alerts
Security Updates
Grouped Security Updates
Version Updates (for which dependabot.yml holds the config - Github should find the committed file)
Action Runners (soon to be mandatory)

Tailor the dependabot.yml file for additional package mangers as required. Similarly alert settings and some PR config can be set via the UI according to taste.

@alan-forbes-cp I squashed both commits and added the label [CP-Sec] to the commit message, no changes added to the file itself.


froala editor resets model

When using the  froala editor my model gets reset.
When typing into the editor, the model doesn't get updated. But when you do a selection and make bold for example, it does update the model.
So for example:
So I have a controller: "Controller" and this is coupled to a view with an input and a textarea.
The textarea has the froala directive on it.
Controller:
this.model = {
    'title': 'title',
    'answer': 'answer'
}

and answer is bound to the editor.
If you output it in the view,  using

{{
 Controller.model | json
}}

it prints:
{
  'title': 'title'
}

When typing in editor there is no modification, so the view stays as above.
But after selecting and making the contents of the editor bold, the view updates the update for the model as:
{
  'title': 'title',
  'answer': '
answer

}

It only seems to be the problem when the initial value is no HTML!
Edit: It is also the case when the model has HTML, but the model is still reset, and only get's filled in after doing an action in the toolbar!
Grtz

It' also only working on setting bold. When I click underline or italic, it doesn't do anything..
This has some really weird behaviour :) For 100$ I expect more

After further investigation it seems that editor doesn't like child properties of an object on the scope.
If the value in the ng-model is a direct value on the scope it seems to work. Please fix this?

@samvloeberghs Hmm, that's strange as my model is a property on an object thats on scope and it works fine. I'll look into this.


Ability to read cloudflare_api_token R2/S3 equivalent keys

Current Terraform and Cloudflare provider version
Terraform v1.5.5
on darwin_arm64

provider registry.terraform.io/cloudflare/cloudflare v4.15.0

Description
Today the API value of the token is produced but the S3 equivalent keys are not. Wondering if there's a way to provide those keys through Terraform so that they can be referenced in other resources.
Use cases
For example, getting the S3 equivalent keys and passing it to an Elastic Beanstalk environment.
Potential Terraform configuration
resource "cloudflare_api_token" "r2" {
  name = "r2"

  policy {
    permission_groups = [
      data.cloudflare_api_token_permission_groups.all.r2["Workers R2 Storage Bucket Item Read"],
      data.cloudflare_api_token_permission_groups.all.r2["Workers R2 Storage Bucket Item Write"]
    ]
    resources = {
      "com.cloudflare.edge.r2.bucket.*" = "*"
    }
  }
}

resource "some_other_resource" "r2" {
  r2_access_key = cloudflare_api_token.r2_access_key
  r2_secret_key = cloudflare_api_token.r2_secret_key
}

References
No response

duplicate of #2713, specifically https://github.com/cloudflare/terraform-provider-cloudflare/issues/2713#issuecomment-1694723003

Makes sense, docs would be nice!


No welcoming window & pulling manifest Error: pull model manifest: file does not exist

What is the issue?
When I first installed the ollama, I didn't see the welcoming window pops up, just a windows notification by it says "click here to start"
Clicking that notification gives me a powershell window as shown
and when I tried to run the command to get started it gives me the error below
pulling manifest
Error: pull model manifest: file does not exist

What did you expect to see?
There should be a welcoming window for me to get started
Steps to reproduce
Reinstall
Are there any recent changes that introduced the issue?
no change
OS
Windows
Architecture
Other
Platform
WSL, WSL2
Ollama version
0.1.29
GPU
Nvidia
GPU info
w
CPU
Intel
Other software
Open WebUI

Hi @HWiwoiiii, the install experience you are describing is what I expect on Windows at the moment. We don't have a welcome screen there yet.
For the ollama run problem, the issue is the name of the model you are trying to run. This should work:
ollama run llama2:13b
The error message is not very obvious in this case, sorry about that. Let me know if this works for you.

Yes it works splendidly now, ty very much
/***

          ii.                                         ;9ABH,

         SA391,                                    .r9GG35&G

         &#ii13Gh;                               i3X31i;:,rB1

         iMs,:,i5895,                         .5G91:,:;:s1:8A

          33::::,,;5G5,                     ,58Si,,:::,sHX;iH1

           Sr.,:;rs13BBX35hh11511h5Shhh5S3GAXS:.,,::,,1AG3i,GG

           .G51S511sr;;iiiishS8G89Shsrrsh59S;.,,,,,..5A85Si,h8

          :SB9s:,............................,,,.,,,SASh53h,1G.

       .r18S;..,,,,,,,,,,,,,,,,,,,,,,,,,,,,,....,,.1H315199,rX,

     ;S89s,..,,,,,,,,,,,,,,,,,,,,,,,....,,.......,,,;r1ShS8,;Xi

   i55s:.........,,,,,,,,,,,,,,,,.,,,......,.....,,....r9&5.:X1

  59;.....,.     .,,,,,,,,,,,...        .............,..:1;.:&s

 s8,..;53S5S3s.   .,,,,,,,.,..      i15S5h1:.........,,,..,,:99

 93.:39s:rSGB@A;  ..,,,,.....    .SG3hhh9G&BGi..,,,,,,,,,,,,.,83

 G5.G8  9#@@@@@X. .,,,,,,.....  iA9,.S&B###@@Mr...,,,,,,,,..,.;Xh

 Gs.X8 S@@@@@@@B:..,,,,,,,,,,. rA1 ,A@@@@@@@@@H:........,,,,,,.iX:

;9. ,8A#@@@@@@#5,.,,,,,,,,,... 9A. 8@@@@@@@@@@M;    ....,,,,,,,,S8

X3    iS8XAHH8s.,,,,,,,,,,...,..58hH@@@@@@@@@Hs       ...,,,,,,,:Gs

r8,        ,,,...,,,,,,,,,,.....  ,h8XABMMHX3r.          .,,,,,,,.rX:
:9, .    .:,..,:;;;::,.,,,,,..          .,,.               ..,,,,,,.59
.Si      ,:.i8HBMMMMMB&5,....                    .            .,,,,,.sMr
SS       :: h@@@@@@@@@@#; .                     ...  .         ..,,,,iM5
91  .    ;:.,1&@@@@@@MXs.                            .          .,,:,:&


remove mlir14 label

hmm, seeing a random test fail.  Running again to see if reproducible.  If not, will merge and then go try to track down this failure separately.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Files with Coverage Reduction
New Missed Lines
%

mlir_graphblas/engine.py
1
74.9%

mlir_graphblas/tests/test_profile.py
4
51.95%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2050

Relevant Lines:
2571

💛  - Coveralls


Unable to map using a rotating LiDAR

Hi,
I'm using a rotating LiDAR to map the given environment. But due to the rotation of the laser scan, it is not able to produce an appropriate map of the environment.
Here is my bag data Bag and gazebo visulaization Video
My config file is
include "map_builder.lua"
include "trajectory_builder.lua"

options = {
map_builder = MAP_BUILDER,
trajectory_builder = TRAJECTORY_BUILDER,
map_frame = "map",
tracking_frame = "base_link",
published_frame = "base_link",
odom_frame = "odom",
provide_odom_frame = true,
publish_frame_projected_to_2d = false,
use_odometry = true,
use_nav_sat = false,
use_landmarks = false,
num_laser_scans = 1,
num_multi_echo_laser_scans = 0,
num_subdivisions_per_laser_scan = 1,
num_point_clouds = 0,
lookup_transform_timeout_sec = 0.2,
submap_publish_period_sec = 0.3,
pose_publish_period_sec = 5e-3,
trajectory_publish_period_sec = 30e-3,
rangefinder_sampling_ratio = 1.,
odometry_sampling_ratio = 0.1,
fixed_frame_pose_sampling_ratio = 1.,
imu_sampling_ratio = 1.,
landmarks_sampling_ratio = 1.,
}

MAP_BUILDER.use_trajectory_builder_2d = true
TRAJECTORY_BUILDER_2D.num_accumulated_range_data = 5

TRAJECTORY_BUILDER_2D.ceres_scan_matcher.translation_weight = 5.
TRAJECTORY_BUILDER_2D.ceres_scan_matcher.rotation_weight = 1e-2
TRAJECTORY_BUILDER_2D.use_online_correlative_scan_matching = true
TRAJECTORY_BUILDER_2D.use_imu_data = false
POSE_GRAPH.constraint_builder.fast_correlative_scan_matcher.linear_search_window = 5.
TRAJECTORY_BUILDER_2D.real_time_correlative_scan_matcher.angular_search_window = math.rad(35.)
POSE_GRAPH.constraint_builder.min_score = 0.80
POSE_GRAPH.constraint_builder.global_localization_min_score = 0.5

POSE_GRAPH.optimization_problem.huber_scale = 1e2
POSE_GRAPH.optimization_problem.acceleration_weight = 1e4

return options

Any workaround to map the environment?

Closing for inactivity, we can't invest time to help you with your setup anymore unfortunately.


React-Plugin does not respect the jsxImportSource from TSConfig

Description
A user shouldn't have to define jsxImportSource twice, if it's in a TSConfig then it's already defined.
ESBuild (and hopefully Vite) already respects that as far as I know for:
jsxFactory
jsxFragmentFactory
I think the plugin should do that for jsxImportSource as well.
Suggested solution
Read TSConfig.compilerOptions.jsxImportSource ?? options?.jsxImportSource ??  "react"
Alternative
Building a  shim for the auto-import and let ESBuild the whole thing instead of using the plugin.
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Notes:

[ ] TSConfing "jsx": "react" is opt out of automatic runtime.
[ ] TSConfig defined "jsxImportSource": "react" is default to current settings.
[ ] Anything else, read pass on as is.

Did a go at it.
const jsxImportSrc = tsBuildConfig.compilerOptions.jsxImportSource
const jsxOption = tsBuildConfig.compilerOptions.jsx === "react"
  ? {}
  : jsxImportSrc === "react"
    ? {}
    : { jsxRuntime: "automatic" as const, jsxImportSrc, }

ReactPlugin({ ...jsxOption, })

Worked perfectly with others, like @emotion/react
    "jsx": "react-jsx",
    "jsxImportSource": "@emotion/react",

and
    "jsx": "react-jsx",
    "jsxImportSource": "react",

Does esbuild support jsxImportSource? According to https://esbuild.github.io/content-types/#tsconfig-json only a few fields are supported which Vite passes. Maybe this is related to plugin-react and it's babel transform, but regardless it would be great if you can submit the PR so it's easier to view the proposed changes.

All the heavy lifting is already done by the React plugin, this is purely a convenience feature. Making sure that we don't repeat configs and keep one single source of truth.

Yes, esbuild does support jsxImportSource.


bug(matTooltip): tooltip doesn't work with ChangeDetectionStrategy.OnPush

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I have a table with tooltips inside rows:
 <ng-container matColumnDef="icons">
    #

      tooltip

  </ng-container>

The table can have thousands of rows, that's why I have to use ChangeDetectionStrategy.OnPush. However, with such strategy tooltips are shown without text.
Reproduction
StackBlitz demo is here
Expected Behavior
Tooltips must be shown with text.
Actual Behavior
Tooltips are shown without text
Environment

Angular: 13.3.9
CDK/Material: 13.3.7
Browser(s): FF 95
Operating System (e.g. Windows, macOS, Ubuntu): Ubuntu

It doesn't work, because you're detaching the ChangeDetectorRef in the constructor which is going to disable change detection for the entire app.

@crisbeto  I detach it because I use onPush strategy. If I don't call this._changeDetectorRef.detach(); then angular doesn't work in onPush mode.

OnPush change detection is activated when you set changeDetection: ChangeDetectionStrategy.OnPush, but that doesn't mean that change detection will be disabled completely, otherwise nothing would ever happen in the app.

@crisbeto Thank you very much for your explanation. This is a modified version of the demo with three modifications:

detach() is commented
added fooTest getter in .ts console.log('change was checked');  return true;
added `{{fooTest}} in .html

With these modifications when you move mouse over tooltip you see in console change was checked. So, when we don't call datach() method in constructor angular continues to check view/model. And when I have thousands of rows and any event is processed (keypress, mouse wheel etc) I see serious performance problems although nor view nor model has been change.

That happens because the tooltip is listening to some events which will trigger change detection. Change detection in itself isn't slow (it's basically a bunch of === expressions), it's what your app does in response to it is what causes the slowdown. I'm closing the issue because the tooltip is working as expected.


storage::new_locked_contract unnecessarily uref_name argument

A uref_name argument is an optional String argument where an "access token" will be stored after creating a contract package. It's used to determine whether a contract can be upgraded and whether the issuer of that action has required permissions to do so.
A contract that is locked cannot be upgraded, ever, hence the existence of uref_name argument is misleading – it has no effect.
API should be updated to remove that unused argument. Similarly, the creation of the access token is a waste of CPU and space in the GlobalState since it cannot be used.

This is incorrect. A locked contract cannot be upgraded but the package can still be managed for instance user group access.

Ok, thanks. I asked Michał about it before creating the ticket but he must
have forgotten about it. I will close the ticket.
On Thu, Jun 17, 2021 at 16:29 edhastings @.***> wrote:

This is incorrect. A locked contract cannot be upgraded but the package
can still be managed for instance user group access.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/casper-network/casper-node/issues/1606#issuecomment-863240263,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHCGINCC4N2WCDALUU6XQLTTH2DZANCNFSM463D4S4Q
.

--
Pozdrawiam,
Mateusz Górski

No worries!


sql, tracing: save traces in Jaeger format

PR: https://github.com/cockroachdb/cockroach/pull/47303
From release notes:

Statement diagnostics zip bundles now contain a representation of the statement trace that can be imported into Jaeger for visualization. [#47303][#47303] {% comment %}doc{% endcomment %}

This was documented in 20.1.x by Ryan already.


extend latex2page to include equation numbering

Is your feature request related to a problem? Please describe.
n/a
Describe the solution you'd like
HR32 says she wants latex2page to be expanded include equation numbering
Additional context
n/a

Ok.  I think I have a robust solution for this (but it is very, very ugly).  Basic idea:

Preflight - scan through LaTeX source and find all labeled equation environments (could alternatively pick up all numbered eqs, but if the point here is cross-referencing, then why number unreferenced eqs?).  Could maybe make this a user toggle (number all vs. only referenced).  In any case, scan through all equation, eqnarray, align (other?) envs and make dictionary of labels vs eq number.
In the pandoc-generated HTML, at the same time as we're replacing the codecogs url with the canvas url, for each equation to be numbered, update as follows:

 ([equation nmber])

Update any references elsewhere in the HTML to the equation number instead of the label name (just a global replace like the others already in use).

Caveats: block math environments (eqnarray and align) can only have a single link as they are going to appear as a single image in the rendered html.  The internal dict should basically just map all relevant eq. numbers to a single reference.  I don't think this will be a major issue, but if people hate this, then just don't use these envs for eqs you want to reference in the text.

Addressed by v2.9.0.


Request to add XP Area guides

Can we add a section for what areas are good to xp at what levels?
e.g. Oz Fields are good around level 30 (+/- a few levels).

This is a great suggestion and I would love this information. I've personally never made it past maybe 70 and have no clue where to level next. Maybe even some links to maps, and mobs to avoid and such would be helpful. If you wanted to submit a PR, you're more than welcome!

I'll start one -- If anyone reads this and has examples and info, please add it and i'll work on the pull.

Now what I'd really love is a list of mobs in each area with links back to a mob page that includes things like exp, health, item drops, special skills, etc. But I'd definitely need @michaelprograms' help with building out something like that

@colinchilds That may require a lot of effort :P Certain areas are up for re-balancing too (eventually), so would need to update lists a lot. I think something like a suggested level range would be a good starting place before we dive too deep into details, for sure.
There is partially completed work in-game for this type of list, but I doubt it'll be finished anytime soon. Here's a preview of it, maybe it can be used for a good starting point of inspiration:

The goal of this was to give areas a "level" value and then map that value to level classifications:
string classify_level(int level) {
    switch(level){
        case 150..179:  return "Titan"; break;
        case 125..149:  return "Late Legend"; break;
        case 90..124:   return "Legend"; break;
        case 70..89:    return "Late Elite"; break;
        case 50..69:    return "Elite"; break;
        case 35..49:    return "Late High Mortal"; break;
        case 20..34:    return "High Mortal"; break;
        case 6..19:     return "Mid"; break;
        case 1..5:      return "Newbie"; break;
        default:        return ""; break;
    }
}

There's some problems with this list though, because it aggregates all islands into Ocean area, so its missing quite a few areas/sub-areas that should be separated out.

Oh, this is definitely a great starting point. I'm not super familiar with how the mobs are set up in the source code, but I was thinking if we could get some sort of dump of all the mobs/areas, I could write a script that parses them to keep the list up to date. That way we could just get a new dump and run the script again to update the site. If that doesn't sound easy/feasible though, I get it.


Unable to find a pod with name IBAnimatable

https://cocoapods.org/?q=IBAnimatable
Have you push it to pod trunk?

I am working on it now. Will keep you posted.


Add mixture/normal_mixture

#197
I wasn't able to run sampling with xla enabled, so the tests are pretty trivial for now since the sampling with nuts takes forever to give some results without xla.
I will tackle (but maybe somebody can help me) the problem so flagging as in progress.
[UPD] my fault, tfp versioning problem, in master the bug was fixed recently.

I think also you also need to add a line in distributions/__init__.py:
from .mixture import *

the tests look quite good, though, thank you!

@junpenglao can we ping the thread again? I wasn't able to get the response.

I pinged the TF thread as I tried to do some modeling in pymc4 and also hit the same bug.

@junpenglao since the tests are not that great for now, can I just mark tests with batch_ndim=0 to xfail? Then hopefully change it back once the issue solved on the tf side.


imagesoutdir gets accidentaly formated

imagesoutdir somehow gets accidentaly formated in some cases.
E.g. when I introduce _ in the path, and also after some math in the document.
Repro:
Blah latexmath:[a = b] _x_ blah.

processed with:
asciidoctor -b html5 -r asciidoctor-mathematical -a stem=latexmath \
-a mathematical-format=svg -a imagesoutdir=$PWD/_eq imgoutdir.adoc

produces:
<img src="whatever/eq/stem-e62d239822831122dd571c0d362408f7.svg"

Where the  that replaced  _ breaks things. I think the path should be taken verbatim. Or am I supposed to decorate the attribute somehow so replacements are not done on it? Though pass:[] or +++ seems to break things even more.
Tested with asciidoctor (<IP_ADDRESS>) and asciidoctor-mathematical (0.2.2) and other dependencies are current versions of whatever the ruby-gems provides.

I will look into this issue.

Any news?


What does “max_length” mean in config.json of successor

What does “max_length” mean in config.json of successor?
I set max_seq_length=128 when I Run compression, but the "max_length" in  config.json of successor is 20.

这是input_id的长度吧