Recent errors with chocolatey 1.2.0

Hi!
I am using this Github action for the Exiv2 project. Few days ago I noticed that the Cygwin builds started to fail, and when I compare the failing jobs:
https://github.com/Exiv2/exiv2/actions/runs/3365823530/jobs/5585304895
With the non failing ones from 1 week ago:
https://github.com/Exiv2/exiv2/actions/runs/3332745648/jobs/5513973618
The only different that I see is that apparently chocolatey got upgraded from version 1.1.0 to 1.2.0.  The error is not very informative and just says this:
Chocolatey installed 0/0 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
The system cannot find the file specified
Error: Process completed with exit code 1.

The pipeline can be found here: https://github.com/Exiv2/exiv2/blob/dc5dc0d2e39aba87e38cda8378ffd90b833877a6/.github/workflows/on_PR_windows_matrix.yml#L165
Do you know what could be happening? Or any other feedback that could help me to fix this situation?
Thanks in advance for your time and for this nice github action :)

Also happening for me: https://github.com/cpanel/p5-cPanel-APIClient/actions/runs/3369854268/jobs/5590289790

Same here in my project:
https://github.com/gansm/finalcut/actions/runs/3347219222/jobs/5562942770

Same thing happening in hiredis:
https://github.com/redis/hiredis/actions/runs/3380340217/jobs/5613014442

I have the same error, here is the error I got from the logs:
2022-11-07T22:35:19.3222967Z  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
2022-11-07T22:35:19.3223386Z 2022-11-07 22:35:07,866 4196 [DEBUG] - Sending message 'PostRunMessage' out if there are subscribers...
2022-11-07T22:35:19.3223687Z 2022-11-07 22:35:07,866 4196 [ERROR] - The system cannot find the file specified
2022-11-07T22:35:19.3224116Z 2022-11-07 22:35:07,897 4196 [ERROR] - More Details: System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
2022-11-07T22:35:19.3224416Z    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
2022-11-07T22:35:19.3225014Z    at chocolatey.infrastructure.commands.CommandExecutor.execute_static(String process, String arguments, Int32 waitForExitInSeconds, String workingDirectory, Action`2 stdOutAction, Action`2 stdErrAction, Boolean updateProcessPath, Boolean allowUseWindow, Boolean waitForExit)
2022-11-07T22:35:19.3225565Z    at chocolatey.infrastructure.commands.CommandExecutor.execute(String process, String arguments, Int32 waitForExitInSeconds, String workingDirectory, Action`2 stdOutAction, Action`2 stdErrAction, Boolean updateProcessPath, Boolean allowUseWindow)
2022-11-07T22:35:19.3226040Z    at chocolatey.infrastructure.app.services.CygwinService.install_run(ChocolateyConfiguration config, Action`1 continueAction)
2022-11-07T22:35:19.3226552Z    at chocolatey.infrastructure.app.services.ChocolateyPackageService.perform_source_runner_function[T](ChocolateyConfiguration config, Func`2 function)
2022-11-07T22:35:19.3226948Z    at chocolatey.infrastructure.app.services.ChocolateyPackageService.install_run(ChocolateyConfiguration config)
2022-11-07T22:35:19.3227360Z    at chocolatey.infrastructure.app.runners.GenericRunner.run(ChocolateyConfiguration config, Container container, Boolean isConsole, Action`1 parseArgs)
2022-11-07T22:35:19.3227757Z    at chocolatey.infrastructure.app.runners.ConsoleApplication.run(String[] args, ChocolateyConfiguration config, Container container)
2022-11-07T22:35:19.3227961Z    at chocolatey.console.Program.Main(String[] args)

https://github.com/jkroepke/helm-secrets/actions/runs/3414624012/jobs/5682825355

This project seems to be dead, so I switched to cygwin/cygwin-install-action.
Everything works as before:
https://github.com/gansm/finalcut/actions/runs/3566270301/jobs/5992496219

This project seems to be dead, so I switched to cygwin/cygwin-install-action.
So did I

@egor-tensin
I confirmed this issue closed by v4!
example: https://github.com/yanorei32/VRChatRejoinTool/pull/40
I think this issue should probably be closed.
Thank you!


Added Keysight N5230A PNA-L

Adding basic support for Keysight VNA N5230A.
Expect more devices from me over the next few days/weeks.

@dahlend any chance you will continue work on this PR?

Ah im sorry, I totally forgot about this, I no longer work with any hardware. I will close this.


prepping for rebase and PR

Description
Profiles seed was exporting profileList, which does not get called anywhere in the codebase. Removed it.
https://loom.com/share/0a2749c4d63746b3bdda40d3b8b193a0
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[ √ ] My code follows the style guidelines of this project
[ √ ] I have performed a self-review of my own code
[ √ ] I have removed unnecessary comments/console logs from my code
[ √  ] I have made corresponding changes to the documentation if necessary (optional)
[ √ ] My changes generate no new warnings
[ √ ] I have checked my code and corrected any misspellings
[ √ ] No duplicate code left within changed files
[ √ ] Size of pull request kept to a minimum
[ √ ] Pull request description clearly describes changes made & motivations for said changes

Could you check again? I believe I forgot to push the change for the profiles seed earlier.

Yes, Ryan H. and I saw that but he said it's not needed.


Extend documentation of /scheduler/jobs by the possibility to get a single job

How do I get the definition of a single job:
/scheduler/jobs/search?name=<job_name>

+1 to add this to the documentation as it is very helpful.


feat(map_loader): display curbstone as marker array (#4958)

(cherry-pick)display curbstone as marker array
original PR: https://github.com/autowarefoundation/autoware.universe/pull/4958
Issue: https://tier4.atlassian.net/browse/RT0-29081
Description
curbstone(縁石)がrvizに表示されていないため、実車実験やpsimで車両がcurbstoneにどれぐらい近づいているか把握できない。対策としてMarkerArrayを追加し、curbstoneをrvizで表示する。
https://tier4.atlassian.net/browse/RT0-29081
Tests performed
藍色の線でcurbstoneが表示される。

Effects on system behavior
Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@Motsu-san
This is the cherry-pick of https://github.com/autowarefoundation/autoware.universe/pull/4958 .
Could you approve this? Thank you.


Make improvements on selectBestHost method

Is your feature request related to a problem? Please describe.
Current way of selecting the best host is just by finding out which node responds the first API request.
Describe the solution you'd like
We should consider adding validation, it does not handle if the node itself is out of sync.
Describe alternatives you've considered
On the new mobile wallet, i make request every 240 seconds for checking out if the node is out of sync
Additional context
API Method https://signum-network.github.io/signumjs/classes/core.chainservice.html#selectbesthost

It would be an improvement which will benefit all current wallets


[FLOC 2339] Update to authentication docs from MY feedback

Fixes 2339
This issue resolves the feedback from @myechuri, following an installation run-through.
Note that this only fixes point 4 in the issue. I think points 1 - 3 have already been addressed in previous PRs. Please advise if that is not the case.

:+1: LGTM. Merge when ready.


WebSocket error on signIn in Firefox

In Firefox, invoking the signIn method leads to a WebSocket error:

The same code works in Chrome and Safari.
This happens with a create-react-app project, on http://localhost:3000
Versions used:
userbase-js 2.0.0
Firefox Developer Edition 78.0b9
Firefox 77.0.1

Ack'd, working on this and will provide a detailed write-up on it. Thank you for reporting.

Can confirm that the bug is fixed in 2.0.1 – thank you so much!

Can confirm that the bug is fixed in 2.0.1 – thank you so much!

Summary of the bug
The AES-KW crypto algorithm was introduced in #155 (userbase-js v2.0.0). Clients used AES-KW to wrap private keys, which were then stored on the Userbase server. The client then used AES-KW again to unwrap the private keys in order to sign in.
The AES-KW unwrap function is broken in Firefox, so userbase-js v2.0.0 functions signUp(), signIn(), and init() are broken in Firefox.
Solution
We replaced usage of the AES-KW algorithm entirely with AES-GCM in userbase-js v2.0.1 (#164).
userbase-js versions <= 2.0.0 still work. When a developer updates to version 2.0.1, the userbase-js client generates new private keys, which are then encrypted and stored on the server in place of the wrapped private keys and are used to authenticate the user in subsequent visits to the app.
Preventing cross-browser bugs in the future
We’ve added Firefox to our test suite in #165. Every PR will now run our entire set of unit tests against Firefox.
We have a series of manual tests to run against Safari, Safari iOS, and Chrome Android as well. For the immediate future, running these manual tests is a matter of discipline on our end that we will stick to.
We're also exploring incorporating BrowserStack into our CI pipeline to automate testing across a wider range of browsers, but it’s not on the immediate roadmap.


thankyou

thankyou all of you .
I have solved my error by just installing tensorflow==1.5
by the command "pip install tensorflow==1.5"

Glad the issue is resolved, moving this to closed status.


Example fixes

"Type 'string | undefined' is not assignable to type 'string | T | Promise<string | T | null> | null'."

Thanks! Can you replace || with ?? please?


Indicate implementation class in REST API

This follows up on #51 and bring the work to completion

@reviewbybees in particular @christ66

Renamed to _class based on the discussion in #51
The behaviour of how/when _class property gets written is now user-controllable
Added a mode that produces _class more intelligently

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

And now?

:bug: since the PR breaks the binary compatibility of the publicly exported API.

Impact: https://github.com/search?utf8=✓&q=+"stapler.export.DataWriter"+"startObject("&type=Code&ref=searchresults
Affected project: https://github.com/stapler/stapler-adjunct-nvd3
Affected project: https://github.com/tatablack/CiInformer

Hmm, DataWriter wasn't meant to be implemented by outside as Flavor was supposed to be the contact point, but oh well.

I will massage the change some more and come back.

@reviewbybees This change is ready once again

Added some comments and suggestions but :bee: overall.

@kohsuke will it handle a case of class name conflicts in different packages?

will it handle a case of class name conflicts in different packages?

Yes because the default behavior is IF_NEEDED without .simple().

I have a class com.org.my.plugin.MyAction
I serialize it (i.e. for a backup) since it's only one class with name MyAction then it will be serialized as MyAction
then I install another plugin which creates MyAction too, now I have data serialized with packages, right? But old data is unambiguous now

Again the default behavior would be to emit something like
"actions": [
  {
    "_class": "com.org.my.plugin.MyAction",
    "someattr": "somevalue"
  }
]

Anyway this patch affects the “exported REST” API. It has nothing to do with serialization. In Jenkins that is handled by XStream, which has an unrelated format which always records FQNs where needed.

ok then, just haven't noticed this default behavior in tests, sorry :)


--version option doesn't work gives error Cannot find module '../package' but no version

./node_modules/.bin/mocha-webpack --version
Advanced options:
--async-only, -A
...
Cannot find module '../package'

Thanks for reporting.
Fixed & released in 0.3.0.


feat/add question counter

Fixes #7

[x] I have read and agree to the Code of Conduct, and have followed the Contributing guidelines.

Pull Request Type

[x] New feature

@eduardconstantin Please review it!

you can use this state from Quiz component as a counter, no need to make a new state inside the QuizForm component

@eduardconstantin Done!!

Thank you for helping me with this issue!

Thank you for guiding me!! Have a good day!!


Basic analytics for users

It might be a useful feature if users could see basic analytics for their account page on Gratipay, even if it's just counting pageviews.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/7221732-basic-analytics-for-users?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

GA has an API, the data could be pulled from there to display for users.

Do we still use GA? We added Piwik too somewhere, IIRC....

No GA since #761, as you've found. We used Piwik most recently, but stopped paying for it at https://github.com/gratipay/inside.gratipay.com/issues/328.

I'd like to work on analytics for users - Is it okay if I setup a Piwik instance on Digital Ocean? Do we have a team account there that you can add me to?

Ah, just saw this - https://github.com/gratipay/gratipay.com/issues/761#issuecomment-164339195

IMHO, they are already plenty of analztics / tracking stuff all around we can iembed and bind to a Grtipay button e.g

@emanwebdev Does Piwik fit the bill? What do you mean by "bind to a Gratipay button"?

Piwik is a good option. IMHO


Add task type "Review Request" for both Clouds

Description

Currently, privileges for reviewing requests, are granted based on a user's roles and the status of a product or request. To better manage these privileges, we want to introduce a new Task type Review Request within the system. When a new request is created, a task will be generated and used to manage review permissions, ensuring consistent tracking.

Technical Details

Add a new Task type to the Prisma schema. (possibly we might add two separate ones for private and public)
Automatically create a task when a request is initiated and close the task when the request is completed.
Display the task in the task side panel.
Assign read privileges for products/requests based on associated tasks.
Grant review request document-level permissions based on assigned tasks.

Definition of Done (DOD)

A new task is generated when a request is created, and the review workflow works as expected, including email notifications.

Edit Request that was auto-approved has status Partially provisioned, though logs show that it was successfully approved:

After submitting a Create request, private-reviewers get an empty email about Edit request waiting for review:

After submitting a Create request, private-reviewers also get an email about Delete request waiting for review:

After clicking the Request link, the browser shows application error and doesn't display the contents of the page:

After submitting Edit request, increasing quota, Reviewers receive the email about Delete request waiting for review:

After submitting Edit request, increasing quota, Users receive email about Automatic approve, which is not true in this case:

After Rejecting Delete request, User doesn't receive any email

Now everything works good, all the users, having private-reviewer role receive tasks when there is a new request (of any type) waiting for approval. The link leads to the request. The emails are reflecting right stages of the flow and are displayed in full.


organization_settings: Move settings to new lines.

Fix #20415

Moved the setting to a new line.
Removed the colon from the translations too.

Testing plan:
Manually
GIFs or screenshots:

You need not change the translation files, those are handled by transifex.

You need not change the translation files, those are handled by transifex. You can have a look at documentation.

Oh okay..thanks.

You can make the changes in this PR iself. No need to make another PR.

You can make the changes in this PR iself. No need to make another PR.

There were other CI errors as well, and the changes were not so much. Reverting all the changes in the translation files would be a bit tedious😅.


Fix bug when updating the divisions and value of the slider at the same time

Description
When updating the divisions and value of the slider at the same time, the position of the thumb is wrong because the old divisions value is used.
Related Issues
Fixes #65943
Tests
See files.

Looks good! Could you do the same update for RangeSlider as well?

Looks good! Could you do the same update for RangeSlider as well?

@guidezpl Nice caught :)

Well done. Thanks.


Interested in collaborating

Hello,
Earlier this evening I randomly came across your post on users.rust-lang.org from several months ago looking for feedback on this library. I wasn't previously aware of the project and was impressed by its breadth and the amount of work that's already gone into it. I run a trading operation on a rust codebase so this is definitely of major interest to me! I'd be interested in collaborating and wanted to send some initial thoughts from a couple hours with the code.
You mentioned in the post you were new to rust, so I included various recommendations from my own experience. Perhaps some of it will be obvious or things you already know - but I thought it couldn't hurt. Like you, I see rust as an incredible tool for this application, owing to the great performance, powerful type system, modern packaging system, etc. But there are definitely still bumps along the way during the learning curve.
In any event, here are various thoughts I jotted down while diving into the project for the first time:

The number one thing I wanted/expected to see are some examples. Examples are integrated into cargo (cargo run --example pricing) and I often start there when I'm looking at a project for the first time.

On the other hand, there's plenty of tests. (Second step is often git clone then cargo test for me). Perhaps some of the tests include code that would be suitable to use in examples. Do you have any recommendations on which ones to look at?

One of the biggest issues I face is needing to use different number types in different situations and performance and ergonomics pitfalls associated with juggling all of them, converting from one to the other, etc. In many cases, correct precision is required and a decimal type is needed. (I have been using the rust wrapper to the decNumber lib for over a year, it seems by my lights to be the best choice at the moment). In many other cases, the performance hit from using decimal is very, very steep compared to the floating point primitives (f64/f32). Rust tends very much towards prudence when it comes to floating point, with a carefully designed api, but it still takes a lot of care to avoid blowups. A third option that sometimes presents itself is to use integer types as fixed-point, for instance when the precision of prices is static. This can be very fast and precise, but it's not always available. I saw that the library generally uses f64, I was wondering if you had further thoughts on how that has worked for you in this application.

I'm intrigued by the date functionality here; it might be worth pursuing it as a stand-alone crate. Currently the chrono crate has a pretty good handle on power/completeness/correctness and it works very well with serde for deserialization. However, the main chrono DateTime<Utc> type is somewhat heavyweight: it's an i32 for the date, two u32s for the time, plus an offset enum (which I believe is zero-sized, however). I frequently use nanosecond timestamps stored in an i64/u64 for performance, and there's no good library that I've seen that focuses less on the kitchen sink, and more on the most performant possible way to store/operate on times.

Regarding the Error struct defined in core::qm:
pub struct Error {
    message: String
}

(Haven't been able to tell if this is widely used throughout the library or not). Error-handling has been a moving target in rust, with the std Error trait falling out of favor and several different crates trying to make error-handling more ergonomic have risen and fallen. Personally, I have come to prefer using Error enums defined on a per-crate or per-mod basis. In this case, it might look something like this:
pub enum Error {
    Io(std::io::Error),
    ShapeError(ndarray::ShapeError)
    // ...
}

A lot of the time I keep it even simpler with "zero-size" enums with no data associated with each variant, but the variant name alone is enough to act on the error.
The advantages of localized, lightweight error types include:

In rust, matching on or otherwise manipulating/operating on types is very ergonomic and powerful, while matching/operating on strings is relatively painful, owing to the strict ownership semantics and String/str divergence.

If latency is a priority, as it often is in trading, incurring a heap allocation (for the message String) just to handle an error is somewhat wasteful.

This is especially true because in idiomatic rust, program crashes are very rare and there's little need to gather as much information as possible for piecing together what went wrong after the fact. Your debugging time is more likely to be spent on the front-end getting the program to compile in the first place.

Regarding this comment/question:
impl Black76 {
    pub fn new() -> Result<Black76, qm::Error> {

        // For some reason we cannot use the ? operator for this sort of error.
        // as a workaround, do it manually for now.
        match Normal::new(0.0, 1.0) {
            Ok(normal) => Ok(Black76 { normal: normal }),
            Err(e) => Err(qm::Error::new(&format!("RSStat error: {}", e)))
        }
    }
    // ...
}

The Normal::new function from the statrs crate returns Result<T, StatsError>. Since Black76::new returns Result<Self, qm::Error>, you would only be able to use the question mark operator if a From<_> impl exists to convert a StatsError into a qm::Error. You already have a long list of these From<_> impls in core::qm, so perhaps you discovered this along the way.
Incidentally, the statrs::StatsError is a great example of a robust, but lightweight error enum that covers the various types of errors that can come from the library without any allocations. &'static str (string literals) used in many of the variants are very ergonomic for that purpose.
In this case, however, handling the error isn't even necessary. The error can only arise if either argument is NaN or a negative value is passed as the std_dev argument, which is clearly is not the case since it's being passed float literals. In my judgement, this is a perfect use of .unwrap() or .expect("statrs::Normal::new(0.0, 1.0)"). I typically note why an unwrap is safe with a quick comment.

One test failed on my machine (using nightly-2018-12-02), which seems to be a floating point issue:
thread 'math::brent::tests::problem_of_the_day' panicked at 'result=192.80753261197134 expected=192.80752497643797', src/math/brent.rs:146:9

Hope these initial comments are helpful to you. I'm looking forward to delving further into this. I'd be interested to hear what the current status on the project is, and if you have any ideas for areas where collaboration would be especially useful.
Jonathan

Hi Jonathan,
Wow! This depth of feedback is what I was hoping for when I put the project on GitHub. Thanks very much. Here are a few responses to your issues:
Examples:
Ideally what I wanted for examples was real world examples. Unfortunately, I do not have easy access to real market data. If you do, that would really help the project. Until I have some decent examples, the place I'd recommend looking at first for most users is the very top level tests -- facade/c_interface.rs. At present, the facade is all defined in terms of JSON inputs. Moving forward, I think there should be lower-level ways of getting data into QuantMath, but this does at least work and allow you to do pricing. As you are interested in interfacing from Rust, I'd start at the level below the facade -- pricers/selfpricer.rs and pricers/montecarlo.rs.
Numeric types:
I have always used f64 or its equivalent in other languages for financial maths. I can see that this gives inaccurate results, but in practice the input data is not that great anyway. For some applications such as accrual-valued equity swaps and settlement, I can see that you may need greater accuracy. My gut feel would be to write templated code for functions I knew might need decimal accuracy, but to avoid it for most of the library. I don't think anybody is going to want risk calculated more accurately than f64.
Date/time:
Please feel free to disagree, but my experience is that finance is either interested in nanosecond accuracy for high-frequency trading, or else it is good enough to hit the right date. Date-time brings a host of issues, like what is the settlement period for different times of day, do you need to handle intraday discounting, or how you handle timezones and changes to daylight-saving time. For every purpose I've experienced in finance, it's good enough to have a date plus some indication of how far you are through the trading day, such as an enum (open/close) or a day fraction -- volatility time,  which may not be a linear function of real clock time.
Errors as strings:
I've always liked strings as errors in finance for the reason that you seldom want to recover from an error -- you just want to report as much detail as possible to the user and then abort that calculation. (I once worked on a library that tried all sorts of ways of getting a vol, and if all else failed, it used 30%! -- I don't want that sort of philosophy in QuantMath.) However, I take what you are saying about the cost and awkwardness of strings. Maybe a way forward would be to use lightweight error types for the low-level modules, and keep string errors for the higher levels, where we need to be able to report a lot of detail.
statrs error:
Your analysis is exactly correct here! Feel free to make the change you suggest.
The failing test:
I only have a couple of machines here that I can test the code on -- it does not surprise me that different architectures would give slightly different results. The difference we are seeing here is a relative error of  about 1e-8, even though I was asking Brent for an accuracy of 1e-10. Maybe it is just differences between the trig functions on my and your machines (see http://notabs.org/fpuaccuracy/)
Contributions:
Pretty much anything would be welcome, from code tidyup through major chunks of new functionality. What sort of trading are you doing, and what are your requirements from a pricing library?
Marcus

I'm glad you found it helpful! To give you a bit more background about myself, I trade on the crypto markets, at relatively "high frequency" (the infrastructure is very young, it's milliseconds that matter still, not nanoseconds). Although I studied programming, I worked as a political reporter after school; my interest in trading came from an experience of using machine learning to forecast the outcomes of congressional votes, which we hoped to sell to hedge funds. (The forecasts were perfect, the sales less so -- it's still hard to trade an informational edge like that, we found).
Anyway, that's all to say it's less that I know exactly what I want to use here than I am very excited by the wealth of knowledge the code contains and all that I can learn from it. For instance, I had never encountered the term "bump" before yesterday, which I gather means to update calculations incrementally on receiving market new data. It's also to point out that my reference point of latency-sensitive code that runs 24/7 (no "trading day") and must never crash is pretty different from running a daily analysis - so my performance concerns may be overzealous.
I collect lots and lots of market data but I doubt it's the kind needed here. However, I found the functions in risk::marketdata::tests that generate dummy data so that should be enough to craft some examples out of.
One major thing I noticed from my further review of the code was the extensive use of single-use reference count types (RcRateCurve, RcDividendStream, etc). Also from the use of several serde alternatives I gather there was some friction with std::rc::Rc and serializing/deserializing the data.
On one previous occasion, I remember facing a similar problem that I solved by enabling the "rc" feature in serde (it's listed in the Cargo.toml. I believe it allows Rc<T> to be serialized as T, although it's been a while.
In general, it's far preferable to use a generic Rc type that wraps the underlying types, e.g. Rc<RateCurve> instead of RcRateCurve, as a RateCurve type really has no business mucking about with reference counting, and the one-off types create a lot of noise in trying to read and understand the code.
Can you explain what problems you faced that led you to these design choices? I have in mind several occasions where I ended up doing similar things simply because it seemed to be the only way to accomplish what I wanted the code to do. I gather that the intended use is to be able to load the underlying data from file, so serialization is important. Was the use of reference counting types primarily for convenience, or necessity (cyclic data structures, etc.)?
On a related front, many of the reference counted types use Arc, the thread-safe reference counted type that uses atomics under the hood. In my experience, Arc is surprisingly expensive - the type has to be quite large for simply cloning it to be slower. Also, I didn't find any multi-threaded code in the library itself. But the scope of the data here also matters. Broadly speaking, in a serious use of this library, how many "things" are we talking about? Thousands? Single-digit millions? At hundreds of millions the tab really starts to rack up from Arc, String, etc., but maybe that's way beyond what's plausible (in my high freq world the data piles up at a staggering pace).
I've forked the library and begun some work around the edges, I plan on submitting various pull requests here and there coming forward. First significant one will be to construct an example based on the monte carlo tests. Thanks for making this code public! The scope of the project is quite amazing and I'm very pleased I found it.


Swift Demo Project

When attempting to use the "Voice Button Request" nothing happens and there is an error logged into console:
2017-01-02 01:45:02.102002 ApiAIDemoSwift[917:151587] [] nw_endpoint_handler_add_write_request [1.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-01-02 01:45:02.102678 ApiAIDemoSwift[917:151588] [] __tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-01-02 01:45:06.285527 ApiAIDemoSwift[917:151589] [] nw_endpoint_handler_add_write_request [2.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-01-02 01:45:06.286643 ApiAIDemoSwift[917:151589] [] nw_endpoint_handler_add_write_request [2.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-01-02 01:45:06.288061 ApiAIDemoSwift[917:151586] [] __tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument```

Assuming Voice has been deprecated - it might be useful to remove `Voice button Request` from demo

From further testing it seems that different Client Keys perform differently

let clientkey_APIAi = "b316a120a0ab4383980746032c21c4f5" // This one from the sourcecode seems to work pretty consistently.

let clientkey_APIAi = "d915ba7bf4e842af9b7cc2c6ebf1a686" // This test one that I generated recently seems to fail 100%

Is there a setting/ differnce in these codes which can result in the Voice recognition not returning any data

I'm having the same issue.  The requestVoice() API method is still listed in the README.md as a valid option, but this appears to be broken on IOS (Android is working just fine).  Can we get official word on this as a viable option?  If anyone has a solution for IOS, I'd greatly appreciate it!


Lock file maintenance

This PR contains the following updates:

Update
Change

lockFileMaintenance
All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving<EMAIL_ADDRESS>npm error Found<EMAIL_ADDRESS>npm error node_modules/vitest
npm error<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error   packages/tests
npm error<EMAIL_ADDRESS>npm error     node_modules/@studiometa/js-toolkit-tests
npm error       workspace packages/tests from the root project
npm error   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error   node_modules/@vitest/ui
npm error     peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error
npm error Could not resolve dependency:
npm error peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error node_modules/@vitest/coverage-v8
npm error<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error   packages/tests
npm error<EMAIL_ADDRESS>npm error     node_modules/@studiometa/js-toolkit-tests
npm error       workspace packages/tests from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-07T10_05_33_536Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-07T10_05_33_536Z-debug-0.log


Fix #2052: Math.nextUp(0.0) == Double.MinPositiveValue

Scala.MinValue, it should have been Scala.MinPositiveValue

Can one of the admins verify this patch?

Could you make the title of the commit message fit on one line? Suggestion:
Fix #2052: Math.nextUp(0.0) == Double.MinPositiveValue.

Details here.

Updated.

LGTM. Jenkins, test this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2498/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3233/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2503/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3238/
Test FAILed.

@soc, can you also rebase on top of master.

Addressed @sjrd's comment and rebased as @nicolasstucki suggested.

LGTM. Jenkins, retest this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2548/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3291/
Test PASSed.


Wrong documentation about unit for memory option

Documentation says that you can set memory limit in megabytes, like this --memory=4m, but actually it is setted in mebibyte, which more than megabyte on 48_576 byte.
With runtime option --memory=4m I have that limit from docker inspect "Memory": 4194304

@heruv1m, I believe you created the issue in the wrong repository. Please have a look at https://github.com/moby/moby instead.


Explicitly declare dependency on com_google_protobuf//:any_proto [phab:D2149]

Created by schroederc at 2018-01-25 23:05:11:

fromberger accepted this revision at 2018-01-25 23:06:01

schroederc closed via commit 5e968870282fe4b8c6df577da49bfc29ad58d8ea at 2018-01-25 23:07:06


"enum" does not work within "items"

Tested using the following against 2d404b8035f8dc349ebbf6b9281d173473a7c871 on 6.0.0-dev. "two" is not defined in the enum, but is still considered valid. This should actually be an error.
Other constraints within items seem to work fine.
{
    "testArray": ["one", "two", "three"]
}

{
    "type": "object",
    "properties": {
        "testArray": {
            "type": "array",
            "items": {
                "type": "string",
                "enum": ["one", "three"]
            }
        }
    }
}

steve@neith /tmp $ ~/dev/json-schema/bin/validate-json --verbose test.json schema.json
OK. The supplied JSON validates against the schema.

Hi,
5.2.7 & 6.x.x-dev branch can be fixed this situation by
https://github.com/justinrainbow/json-schema/search?q=0254213bb945ade4b4c3a8f292352759f2ab6e8d&type=Commits
, it would be great if v6.0.0 released... (v6.0.0 also contains keyword const ...)

This seems to have been fixed since then, at least with 5.2.10 I get the expected error:
JSON does not validate. Violations:
[testArray[1]] Does not have a value in the enumeration ["one","three"]

I've been looking into this report but neither on the main (aliased as 6.0.0-dev) or  5.x.x  branches is the above reproducible. I've also check the latest tag (v5.2.13) for which I also cannot reproduce.

@DannyvdSluijs Thanks - will close as fixed.


Fix some alerts founded the LGTM system

Signed-off-by: Taras Drozdovskyi<EMAIL_ADDRESS>Problem
Fix LGTM alerts
Change overview
Some LGTM alerts are fixed.

@tdrozdovsky - zap failures. Guessing some python files are generated from zap and you have to update the zap templates. Also make sure that the templates will not eventually use the given imports

@tdrozdovsky - zap failures. Guessing some python files are generated from zap and you have to update the zap templates. Also make sure that the templates will not eventually use the given imports

@andy31415 I excluded this file. Next time I carefully examine this question. Thank you!

After ToT merging I got:
ImportError: Failed to import test module: test_generated_clusterobjects
Traceback (most recent call last):
  File "/usr/lib/python3.9/unittest/loader.py", line 436, in _find_test_path
    module = self._get_module_from_name(name)
  File "/usr/lib/python3.9/unittest/loader.py", line 377, in _get_module_from_name
    __import__(name)
  File "/__w/connectedhomeip/connectedhomeip/src/controller/python/test/unit_tests/test_generated_clusterobjects.py", line 2, in <module>
    import chip.clusters as Clusters
  File "/__w/connectedhomeip/connectedhomeip/.environment/pigweed-venv/lib/python3.9/site-packages/chip/clusters/__init__.py", line 25, in <module>
    from . import Attribute
  File "/__w/connectedhomeip/connectedhomeip/.environment/pigweed-venv/lib/python3.9/site-packages/chip/clusters/Attribute.py", line 199, in <module>
    None, py_object, c_uint16, c_uint32, c_uint32, c_uint16, c_void_p, c_size_t)
NameError: name 'c_void_p' is not defined

At this point I am not sure I trust this LGTM thing. For the '== None' vs 'is None' fine, but the various improvements in imports seems not very stable.

In hindsight maybe a /rebase before merging such PRs would have helped with CI. guessing new usages of things appeared in time.

@andy31415

After ToT merging I got:
ImportError: Failed to import test module: test_generated_clusterobjects
Traceback (most recent call last):
  File "/usr/lib/python3.9/unittest/loader.py", line 436, in _find_test_path
    module = self._get_module_from_name(name)
  File "/usr/lib/python3.9/unittest/loader.py", line 377, in _get_module_from_name
    __import__(name)
  File "/__w/connectedhomeip/connectedhomeip/src/controller/python/test/unit_tests/test_generated_clusterobjects.py", line 2, in <module>
    import chip.clusters as Clusters
  File "/__w/connectedhomeip/connectedhomeip/.environment/pigweed-venv/lib/python3.9/site-packages/chip/clusters/__init__.py", line 25, in <module>
    from . import Attribute
  File "/__w/connectedhomeip/connectedhomeip/.environment/pigweed-venv/lib/python3.9/site-packages/chip/clusters/Attribute.py", line 199, in <module>
    None, py_object, c_uint16, c_uint32, c_uint32, c_uint16, c_void_p, c_size_t)
NameError: name 'c_void_p' is not defined

Looking at these lines, I see that there is the error. Tell me please, what you did I would like to reproduce to avoid further.
Of course this import is a smell code and in this case, I can suggest exclude this type of error as false-positive.
Please give me the answer or what do think about it. It is very important for me.
P.S. From the LGTM side, it is only recommendations, but if you look deeper from the security side, the incorrect transformation of pointers can lead to vulnerability.


-u and -d clarification

Could you please clarify from where the upstream and downstream options extend the clipping.
If upstream goes upstream from the 5' most base of primer, it will extend away from the primer. But if downstream extends downstream from the 5' most base of the primer it will extend into the primer? If these functions did the same thing I would expect the default values to be the same for each?
I also assume that upstream only extends upstream from the first primer? Clipping upstream from the second primer would clip bases in the amplicon?
Do these options work the same given each strand?
I am using a bedpe file so perhaps these options are not relevant in my use case?

To process each BAM alignment, BAMClipper needs to assign it to a primer by matching the alignment starting position and primer 5' end position. The default parameters -u 1 and -d 5 mean the alignment starting position can be shifted by at most 1 bp upstream and 5bp downstream and still assign to the same primer. After the primer assignment to the alignment, BAMClipper always clips the alignment all the way to the primer 3' end position, regardless of -u and -d. So the non-primer bases in between the primer pair will not be clipped.
Moreover, -u and -d are applied to both primers of each amplicon, relative to their own strand. Refering to the example bedpe line in README.md, the 5' position of left primer is chr20:31022897 (1-based coordinate) and right primer is chr20:31023123 (1-based coordinate). Forward alignment from left primer can start at any base at chr20:31022896-31022902. Reverse alignment from right primer can start at any base at chr20:31023118-31023124.

That's very helpful. Thank you


windows app creates conflict with existing mapped drive

From @JonBoley on June 28, 2016 14:3
I already had a drive mapped to K:\, so when Keybase created a drive, it overwrote the existing mapping but the description still indicates the old position.
In the screenshot here, it was something called \\usglvcpg01\cpg:

Perhaps it should allow the user to specify the drive letter?
Or at least warn that the previous mapping will be overwritten.
Copied from original issue: keybase/keybase-issues#2319

Hi, I'll close this as a duplicate of #3195.  I think we'll have a fix soon.

You can now choose the mount point by issuing keybase kbfsmount set X: and rebooting.


Mark interfaces as sealed

This allows simplifying when expressions by removing the need for an else condition.

Fair enough :)
Just to double-check my understanding though, such a custom implementation of UCT<> would not work with .fold(), given that its implementation is also based on a when, right? As in, it would fall into the else branch and therefore trigger an exception?

I wonder if it would be an option to have an open base interface and then a sealed sub-interface, so that customers could choose between either depending whether they'd prefer the ability to have custom implementations or the ability to enumerate all implementations… But maybe that's overkill.

Fair enough :)
Just to double-check my understanding though, such a custom implementation of UCT<> would not work with .fold(), given that its implementation is also based on a when, right? As in, it would fall into the else branch and therefore trigger an exception?

All operators should work because internally we call asLceType() to get a sealed Type.

I wonder if it would be an option to have an open base interface and then a sealed sub-interface, so that customers could choose between either depending whether they'd prefer the ability to have custom implementations or the ability to enumerate all implementations… But maybe that's overkill.

Even with a sealed hierarchy, I don't think the public API would be nicer than fold as we currently have this nested Type class with various branches. You would have to know when to use Type.Error.Typed versus Typed.Error.ThrowableType
when(event) {
    Type.Loading.Unit ->
    Type.Error.ThrowableType ->
}

For context, we use this single Type hierarchy to represent all cases because it allows us to map from one type to another without any allocation cost.

Gotcha, thanks for the explanation! Luckily I can now use fold for things like non-local returns 😀


user12986714: Watch onlinestreet.co.uk

user12986714 requests the watch of the watch_keyword onlinestreet\.co\.uk. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

onlinestreet\.co\.uk has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Daniil in Charcoal HQ


Remove CDash integration

This has been dormant for a year now. CDash does not work well for us since most systems that we are interested in do not seem to support execution via cron. A better solution might be to use a github-actions runner.

This needs another review.


$VERSION doesn't have value

Running script with mysql:
line 510: 0018: value too great for base (error token is "0018")

Trying to access $VERSION value has no output.
Need to force base 10?

That field should contain the Zabbix db version, something like 5000005 in Zabbix 5.0, or 6000000 in Zabbix 6.0... 0018 is a weird value.
With an empty $VERSION I assume the query "select optional from dbversion;" failed.

$DB_VER has a value of 6000018.
So in the code
re='(.*)([0-9]{2})([0-9]{4})'
    if [[ $DB_VER =~ $re ]]; then
        VERSION="_db-${DBTYPE}-${BASH_REMATCH[1]}.$(( ${BASH_REMATCH[2]} + 0 )).$(( ${BASH_REMATCH[3]} + 0 ))"
    fi

${BASH_REMATCH[3]} return the last 4 digits which is 0018 and bash doesn't like it.
And if I replace re='(.*)([0-9]{2})([0-9]{4})' with re='(.*)([0-9]{2})([0-9]{2})' bash doesn't complain and I get db-mysql-600.0.18.sql.gz .
I'm not sure if there is any need for $VERSION though.

The shell tries to interpret 0018 as an octal number, as it starts with a zero. It then proceeds to fail as 8 is not valid.
Looks like +0 was used to ensure the result was a number, even when the db version was shorter than expected, but with my current version of bash, there's no difference between $(( )) and $(( +0 )).
I tested on 5.0.5, please change as following and check if it works for you too:
- VERSION="_db-${DBTYPE}-${BASH_REMATCH[1]}.$(( ${BASH_REMATCH[2]} + 0 )).$(( ${BASH_REMATCH[3]} + 0 ))"
+ VERSION="_db-${DBTYPE}-${BASH_REMATCH[1]}.$(( 10#0${BASH_REMATCH[2]} )).$(( 10#0${BASH_REMATCH[3]} ))"

It's working as expected, thank you!
..._db-mysql-6.0.18.sql.gz


ISPN-13746 Server hinting

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

Awesome. Thanks for your reviews and suggestions. Here is the backport PR https://github.com/infinispan/infinispan/pull/10066

thanks @dvagnero


Multiple issues for an NVIDIA pdf

Attach (recommended) or Link to PDF file here: http://us.download.nvidia.com/Windows/361.43/361.43-win10-win8-win7-winvista-desktop-release-notes.pdf
Configuration:

Web browser and its version: Firefox 68 beta 6
Operating system and its version: Fedora 30 fully updated + proprietary NVIDIA drivers
PDF.js version: no idea
Is a browser extension: no

Steps to reproduce the problem:

Open this PDF

What is the expected behavior? (add screenshot)
(Google Chrome on the same PC)

What went wrong? (add screenshot)

Wrong (varying) spacing between letters
Wrong strokes width
Bad kerning

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Duplicate of #2739.

#2739 was closed and never fully fixed.

And this is how it should look like:

#2739 was closed and never fully fixed.

Please see https://github.com/mozilla/pdf.js/issues/2739#issuecomment-450633930:

This PDF file looks good now on Arch Linux, i.e., it renders exactly the same in PDF.js for me as it does in Okular. Since the file does not embed its fonts, there is not much more we can do here.

Arch Linux is not the Linux. Fedora is also very popular. There are literally hundreds of thousands of people who use NVIDIA proprietary drivers under Linux. It's not the reason to say "there is not much more we can do here".
You're pretty much saying, "We couldn't care less about a large number of Linux users because in our very particular distro under very particular graphics drivers it just works". No, it doesn't.
If you need any data from me, like drivers versions, libraries version, etc. I can readily provide it.

This also seems to affect Windows:

Sorry for the noob question, but if the font isn't embedded, where does PDFium fetch it from in Chromium?

Since the file does not embed its fonts, there is not much more we can do here.

The PDF file itself does not embed all of its fonts, which is a deprecated practice in the specification (because of font substitution issues similar to this one), and the PDF.js library is thus at the mercy of the platform/operating system to provide some reasonable default standard font.

Yes, I know the font should be included in the PDF file, but the underlying OS providing the default standard font (Windows 10 1809) is the same for Chromium and Firefox Nightly, hence the question. Does PDFium come with some predefined set of fonts potentially unavailable in operating systems? Also, spacing seems to look better when PDF.js is running in Chromium (the screenshot I posted in the previous comment is from Nightly):

I'm not really sure how to proceed here. For me it looks exactly like the second screenshot in https://github.com/mozilla/pdf.js/issues/10878#issuecomment-498026964. Yes, it's a substituted font, but if the PDF file doesn't embed the fonts, we can only fall back to a close substitute as explained in https://github.com/mozilla/pdf.js/issues/10878#issuecomment-498048215. We could try to look into why it's not the same substitute as in Chrome, but it will always be a substitute and is likely to differ between operating systems and platforms.

You're pretty much saying, "We couldn't care less [...]"

That's not true. If there is in fact something that can still be done about this or if there was an oversight, we're always willing to reopen issues (which we do now because I think the question is https://github.com/mozilla/pdf.js/issues/10878#issuecomment-498177749 is a good question), but only if the discussion is constructive. Remember that most people here aren't employees, but help out in their spare time.

FWIW, PDFium matches what Adobe Acrobat Reader DC displays on the same system (fresh VBox VM for Windows 10):

Thank you for making the comparison. Here I also see some differences between Adobe Acrobat Reader DC and PDFium, in particular the "December 21, 2015" text where the "5" character looks thicker (more bold) than in PDFium, but you're right that especially the large white text looks better in those two applications than in PDF.js.

Another PDF with a completely broken kerning:
http://pascal.hansotten.com/uploads/docs/euler stanford CS-TR-65-20.pdf

#16363 might have fixed this, can you still reproduce in latest Firefox Nightly?

PDFium displays it better than pdf.js, https://github.com/mozilla/pdf.js/issues/10878#issuecomment-498614407 still applies. https://github.com/mozilla/pdf.js/issues/10878#issuecomment-505764669 seems fixed, so that was something different.

@calixteman
It indeed looks to be fixed in the nightly - when will the fix land in stable?


Internal error where running out of offers

Hi.
I just synced with github and got the latest code and tried to run the release branch.
I get the following repeatedly as output (only pasted it once here):
2016-Feb-24 08:35:21 RippleCalc:WRN deliverNodeForward: INTERNAL ERROR: Ran out of offers.
2016-Feb-24 08:35:53 RippleCalc:WRN advanceNode: Unreachable: Fell off end of order book.
RPC calls return empty responses. I am assuming something is broken...
Help?

I doubt there's any connection between the warnings in your log and the RPC issues. Can you tell us more about what RPC calls you're issuing and what responses you are getting?


[fix][test]Fix ManagedLedgerTest#avoidUseSameOpAddEntryBetweenDifferentLedger

Motivation

Fix https://github.com/apache/pulsar/issues/16665
The root cause is that: When we called ManagedLedgerImpl#updateLedgersIdsComplete -> OpAddEntry#initiate, and then If ledger.asyncAddEntry(L140) callback successfully, the OpAddEntry state will be COMPLETED instead of INITIATED

https://github.com/apache/pulsar/blob/a1b8476e40b6a40e82062915d13e4dc9d7dff9cb/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/OpAddEntry.java#L125-L140
Modifications

Fix https://github.com/apache/pulsar/issues/16665

Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

I am trying to fix this test,  PTAL~  @codelipenghui , thanks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


feat: support cross-domain request, simplify code

it doesn't work when I try to proxy a server which cross-domain request is unsupported.
it seems some code is unnecessary?

Hey @ansiz, I believe what would work without changing API is to provide your custom Backend function that would add/modify the Origin header. The Backend function naming could be misleading, think of it as Director function.
Moreover we could not simply change the API due to backward-compatibility reasons - if I have a custom Director function that does more than the default one, it would be impossible for me to migrate it over once you removed the function.

@rjeczalik Thanks for your quick reply, yes you are right.  I will try to implement according to your suggestion.

@rjeczalik In addition, I try to use websocketproxy in my project which has a requirement to  establish dozens of proxy handlers, I found those code here: https://github.com/koding/websocketproxy/blob/master/websocketproxy.go#L57-L61 can't be assign new value due to those code are in the anonymous function(closure),  I'm not quite understand why we must copy this value if the handler can't be different in twice initialization, and why we copy those value？
I mean the NewProxy is not really new even the incoming target url.URL is different, I'm not sure wether I made some mistakes or misunderstood？
I feel sorry my English is not very good，hope you can understand and looking forward to your reply， thanks again : )

@ansiz: and why we copy those values？

Since the r comes from the http.Handler and according to its documentation:

Except for reading the body, handlers should not modify the provided Request.

@ansiz: can't be assign new value due to those code are in the anonymous function(closure)

Just create a custom director:
wp := &websocketproxy.WebsocketProxy{
	Backend: func(r *http.Request) *url.URL {
		u := *target
		u.Fragment = r.URL.Fragment
		u.Path = r.URL.Path
		u.RawQuery = r.URL.RawQuery

		return &u
	},
}

While writing this example I realised you would need to extend WebsocketProxy with some Header func(*http.Request) http.Header that you can use to provide custom header. This would involve refactoring out L89-L119 to some separate function, say DefaultHeader.

@rjeczalik Thanks a lot, you are really a nice and patient maintainer.

Doing my best 😎 Thanks!


AVRO-1913: No warnings in the generated Java code.

In my projects this reduces the compiler warnings to 0 in the generated code.

+1 (assuming tests pass, please run them before committing)
Thanks for fixing these, @nielsbasjes!

I committed both AVRO-1913 and AVRO-1914 locally and then ran within docker
./build.sh clean test dist rat
Everything passed successfully.

These still seem to exist in 1.8.2, but the issue is closed -- did the PR get abandoned?


Seg fault for specific boundary selection

Using the current planet.pbf db on osm.conveyal.com this command results in a seg fault:
vex /mnt/osm/db 13.923403897723343 120.9375 16.636191878397646 123.75 manila.pbf
Core was generated by `'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00000000004053f5 in load_tags (coded_tags=0x7f566e6f5000 <error: Cannot access memory at address 0x7f566e6f5000>, keys=0x2271c2c8 <payload_buffer+864936>,
vals=0x2271c2d8 <payload_buffer+864952>) at pbf-write.c:244
244	static size_t load_tags(uint8_t *coded_tags, /OUT/ uint32_t **keys, /OUT/ uint32_t **vals) {

I'm seeing something similar. I noticed it only because this sometimes results in zero-length output files:
vex /metro_extracts/work/vex_db "47.225" "8.275" "47.533" "8.800" zurich.pbf
Mapping file '/metro_extracts/work/vex_db/grid' of size 2.0 GiB.
Mapping file '/metro_extracts/work/vex_db/ways' of size 3.0 GiB.
Mapping file '/metro_extracts/work/vex_db/nodes' of size 44.7 GiB.
Mapping file '/metro_extracts/work/vex_db/node_refs' of size 29.8 GiB.
Mapping file '/metro_extracts/work/vex_db/way_blocks' of size 6.6 GiB.
Mapping file '/metro_extracts/work/vex_db/relations' of size 45.8 MiB.
Mapping file '/metro_extracts/work/vex_db/rel_members' of size 610.4 MiB.
min = (47.22500, 8.27500) max = (47.53300, 8.80000)
Acquiring shared read lock on database.
Opening file 'zurich.pbf' as append stream.
Mapping file '/metro_extracts/work/vex_db/tags' of size 4.0 GiB.
Mapping file '/metro_extracts/work/vex_db/tags.005' of size 4.0 GiB.
Mapping file '/metro_extracts/work/vex_db/tags.003' of size 4.0 GiB.
Mapping file '/metro_extracts/work/vex_db/tags.006' of size 4.0 GiB.
Mapping file '/metro_extracts/work/vex_db/tags.001' of size 4.0 GiB.
Mapping file '/metro_extracts/work/vex_db/tags.002' of size 4.0 GiB.
Mapping file '/metro_extracts/work/vex_db/tags.004' of size 4.0 GiB.
Writing data blob containing nodes.
Writing data blob containing nodes.
Writing data blob containing nodes.
Writing data blob containing nodes.
Writing data blob containing nodes.
Segmentation fault (core dumped)

There's a fixed-size table for tag references that might be at fault. Have either of you seen anything like:
too many key/val string table references in a block.
Segmentation fault (core dumped)

I haven't seen that particular message prior to the segfault.

I can't reproduce the manila or zurich segfault on Philippines/Switzerland extracts loaded into vex, seems to only happen on full planet. Investigating.

@heffergm any chance you were loading a new planet file into an existing database directory? That has undefined behavior and I've seen it cause segfaults before. I should have mentioned that in the README. I have added a check and VEX will only load data into a new, empty directory now.

It’s possible I had overwritten the db directory, but I’m not 100% sure. Didn’t realize that was a bad idea. I’ll modify the behavior for re-creating the data dir and when I get a chance to test let you know if it changes things.
--
Grant Heffernan

Il giorno 01/mag/2015, alle ore 01:24 PM, Andrew Byrd<EMAIL_ADDRESS>ha scritto:
@heffergm https://github.com/heffergm any chance you were loading a new planet file into an existing database directory? That has undefined behavior and I've seen it cause segfaults before. I should have mentioned that in the README. I have added a check and VEX will only load data into a new, empty directory now.
—
Reply to this email directly or view it on GitHub https://github.com/conveyal/vanilla-extract/issues/10#issuecomment-98182456.

Note that the new code attempts to create the data dir when you load a PBF, so all you need to do is remove the data directory before running the load action.

Got it, thanks.
--
Grant Heffernan

Il giorno 01/mag/2015, alle ore 01:29 PM, Andrew Byrd<EMAIL_ADDRESS>ha scritto:
Note that the new code attempts to create the data dir when you load a PBF, so all you need to do is remove the data directory before running the load action.
—
Reply to this email directly or view it on GitHub https://github.com/conveyal/vanilla-extract/issues/10#issuecomment-98183113.

Getting the following trying to build the latest:
---- Begin output of make -j36 ----
STDOUT: clang  -Wall -std=gnu99 -O3 -g    -c -o dedup.o dedup.c
clang  -Wall -std=gnu99 -O3 -g    -c -o fileformat.pb-c.o fileformat.pb-c.c
clang  -Wall -std=gnu99 -O3 -g    -c -o idtracker.o idtracker.c
clang  -Wall -std=gnu99 -O3 -g    -c -o intpack.o intpack.c
clang  -Wall -std=gnu99 -O3 -g    -c -o map.o map.c
clang  -Wall -std=gnu99 -O3 -g    -c -o osmformat.pb-c.o osmformat.pb-c.c
clang  -Wall -std=gnu99 -O3 -g    -c -o pbf-read.o pbf-read.c
clang  -Wall -std=gnu99 -O3 -g    -c -o pbf-write.o pbf-write.c
clang  -Wall -std=gnu99 -O3 -g    -c -o tags.o tags.c
clang  -Wall -std=gnu99 -O3 -g    -c -o vex.o vex.c
STDERR: In file included from pbf-write.c:2:
In file included from ./pbf.h:4:
./fileformat.pb-c.h:7:10: fatal error: 'protobuf-c/protobuf-c.h' file not found
#include <protobuf-c/protobuf-c.h>

Yeah there have apparently been some changes to the protobuf-c library. We should be generating those source files as part of the build process instead of checking them in. Do this:
$ rm fileformat.pb*
$ rm osmformat.pb*
$ protoc-c fileformat.proto --c_out=.
$ protoc-c osmformat.proto --c_out=.
$ make clean && make

Oh and you need to install the package  protobuf-c-compiler (on debian or ubuntu).

So testing on a fresh db, I'm seeing different but odd behavior:
vex /metro_extracts/work/vex_db 47.225 8.275 47.533 8.800 zurich.pbf
Mapping file '/metro_extracts/work/vex_db/grid' of size 2.0 GiB.
Could not memory map file.

But this is perfectly fine:
root@extractor1:/tmp# vex /mnt/metro/vex_db 51.481 -0.674 51.544 -0.514 slough_england.osm.pbf
Mapping file '/mnt/metro/vex_db/grid' of size 2.0 GiB.
Mapping file '/mnt/metro/vex_db/ways' of size 3.0 GiB.
Mapping file '/mnt/metro/vex_db/nodes' of size 44.7 GiB.
Mapping file '/mnt/metro/vex_db/node_refs' of size 29.8 GiB.
Mapping file '/mnt/metro/vex_db/way_blocks' of size 6.6 GiB.
Mapping file '/mnt/metro/vex_db/relations' of size 45.8 MiB.
Mapping file '/mnt/metro/vex_db/rel_members' of size 610.4 MiB.
min = (51.48100, -0.67400) max = (51.54400, -0.51400)
Acquiring shared read lock on database.
Opening file 'slough_england.osm.pbf' as append stream.
Mapping file '/mnt/metro/vex_db/tags' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.002' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.001' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.003' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.004' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.005' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.006' of size 4.0 GiB.
Writing data blob containing nodes.
Writing data blob containing nodes.
Writing data blob containing nodes.
Writing data blob containing nodes.
Writing data blob containing nodes.
Writing data blob containing nodes.
Writing data blob containing nodes.
Mapping file '/mnt/metro/vex_db/tags.008' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.007' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.015' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.010' of size 4.0 GiB.
Mapping file '/mnt/metro/vex_db/tags.009' of size 4.0 GiB.
Writing data blob containing ways.
Writing data blob containing relations.

I'm consistently getting what I suspect are segfaults for these extracts, based on their 0 length size:
0	antwerp_belgium.osm.pbf
0	berlin_germany.osm.pbf
0	cheshire_england.osm.pbf
0	dakar_senegal.osm.pbf
0	dresden_germany.osm.pbf
0	dublin_ireland.osm.pbf
0	glasgow_scotland.osm.pbf
0	hamburg_germany.osm.pbf
0	hangzhou_china.osm.pbf
0	johannesburg_south-africa.osm.pbf
0	leipzig_germany.osm.pbf
0	manchester_england.osm.pbf
0	southampton_england.osm.pbf
0	winterthur_switzerland.osm.pbf
You can find the corresponding bbox's here: https://github.com/mapzen/metroextractor-cities/blob/master/cities.json

Long story short:

the original stack trace was likely me having overwritten an existing db with a new one, so I've implemented your suggestion and will purge the directory ahead of time

the subsequent failures weren't vex, they were part of a downstream osmconvert process. Unfortunately we need to support .osm output, and it looks like osmconvert chokes on converting the vex pbf output

OK @heffergm thanks for the feedback. Will take it into consideration in further work.

After a clean import of planet.osm on our dev server it still segfaults. The reason however is probably very simple: the number of ways in OSM grew much faster than I expected and exceeded a constant I had defined.

Confirmed, the continuing segfaults were due to some table size constants that were too small. I'm adding range checks so this doesn't fail silently in the future and increasing the sizes. In the long run though they will need to expand automatically to accommodate any possible entity index.


Add support for EmbeddedEntity in Datastore

Currently there is no support for embedded entities and no mentions of them in the documentation or Datastore example.

Actually this is supported.
You can set an entity as a property of another entity by using either set(String, Value<?>) and passing an EntityValue or by using the newly released set(String, FullEntity<?>).

It will be nice to add this information to the Datastore example and JavaDoc.

It will be nice to add this information to the Datastore example and JavaDoc.

Javadoc should already be in place. I will take care of adding this to the example.

An example for datastore's embedded entities has been added in #980, see here.


Single block missing after warp sync.

Currently after the warp sync we end up with the full block history, except there's one block body missing.
Warp sync selects block X as target. It then downloads warp proofs, which includes header for X. Then it dowloads the state and passes the state + header to the client, where it gets imported. After that sync starts gap sync process, which downloads block headers and bodies up to block X-1, but not including X. It also starts syncing blocks X+1 ..   normally.  So we end up with no body in the database for block X.  This can be reproduced by trying to sync a new node off a warp-synced node or by simpy trying to export the target block. There are two ways to fix that:

Add an andditional step to warp sync that downloads block body for X and passes it along with the header and state for import in the first phase of warp sync.
Extend gap sync to include block X. However, since header X is already in the DB, X is considered to be an existing block with state. Changes to the client code will be required to allow importing just the body for such blocks.

Cc @altonen @dmitry-markin


No placeholder or text in input field

Bug, feature request, or proposal:
I have updated a project from Angular 2 to Angular 4 and now I'm having a very strange issue: in all browsers, except FireFox on a Mac, the placeholder and text are not visible in an input field.
What is the expected behavior?
This is how it looks in FireFox on a Mac

What is the current behavior?
This is how it looks in Chrome, Safari and IE

What are the steps to reproduce?
This is my package.json
{
"name": "pegasus-ceRegistrar",
"version": "0.0.1",
"dependencies": {
"@angular/animations": "^4.3.2",
"@angular/cdk": "github:angular/cdk-builds",
"@angular/common": "^4.3.2",
"@angular/compiler": "^4.3.2",
"@angular/compiler-cli": "^4.3.2",
"@angular/core": "^4.3.2",
"@angular/forms": "^4.3.2",
"@angular/http": "^4.3.2",
"@angular/material": "^2.0.0-beta.8",
"@angular/platform-browser": "^4.3.2",
"@angular/platform-browser-dynamic": "^4.3.2",
"@angular/platform-server": "^4.3.2",
"@angular/router": "^4.3.2",
"@angular/upgrade": "^4.3.2",
"@types/core-js": "^0.9.42",
"@types/hammerjs": "^2.0.34",
"@types/node": "^8.0.17",
"angular-in-memory-web-api": "^0.3.2",
"angular2-cookie": "^1.2.6",
"angular2-jwt": "^0.2.3",
"concurrently": "^3.5.0",
"core-js": "^2.4.1",
"grunt": "^1.0.1",
"grunt-contrib-clean": "^1.1.0",
"grunt-contrib-copy": "^1.0.0",
"grunt-shell": "^2.1.0",
"hammerjs": "^2.0.8",
"jwt-decode": "^2.2.0",
"lite-server": "^2.3.0",
"load-grunt-tasks": "^3.5.2",
"ng2-cookies": "^1.0.12",
"ng2-responsive": "^0.8.4",
"reflect-metadata": "^0.1.10",
"rollup": "^0.45.2",
"rollup-plugin-commonjs": "^8.0.2",
"rollup-plugin-node-resolve": "^3.0.0",
"rollup-plugin-uglify": "^2.0.1",
"rxjs": "^5.4.2",
"systemjs": "^0.20.17",
"tslint": "^5.5.0",
"typescript": "^2.4.2",
"zone.js": "^0.8.16"
}
}
This is my systemjs.config.js
(function (global) {
System.config({
paths: {
'npm:': 'node_modules/'
},
map: {
Application: 'bin-debug',
  // angular bundles
  '@angular/core': <EMAIL_ADDRESS>  '@angular/common': <EMAIL_ADDRESS>  '@angular/compiler': <EMAIL_ADDRESS>  '@angular/forms': <EMAIL_ADDRESS>  '@angular/http': <EMAIL_ADDRESS>  '@angular/material': <EMAIL_ADDRESS>  '@angular/animations': <EMAIL_ADDRESS>  '@angular/animations/browser': <EMAIL_ADDRESS>  '@angular/platform-browser/animations': <EMAIL_ADDRESS>  '@angular/platform-browser': <EMAIL_ADDRESS>  '@angular/platform-browser-dynamic': <EMAIL_ADDRESS>  '@angular/router': <EMAIL_ADDRESS>  '@angular/upgrade': <EMAIL_ADDRESS>
  // CDK individual packages
  '@angular/cdk/platform': <EMAIL_ADDRESS>  '@angular/cdk/a11y': <EMAIL_ADDRESS>
  // other libraries
  'rxjs': 'npm:rxjs',
  'ng2-cookies': 'npm:ng2-cookies',
  'ng2-responsive/bootstrap': 'npm:ng2-responsive/bootstrap',
  'ng2-responsive/browsers': 'npm:ng2-responsive/browsers',
  'ng2-responsive/config': 'npm:ng2-responsive/config',
  'ng2-responsive/custom-sizes': 'npm:ng2-responsive/custom-sizes',
  'ng2-responsive/devices': 'npm:ng2-responsive/devices',
  'ng2-responsive/pixelratio': 'npm:ng2-responsive/pixelratio',
  'ng2-responsive/responsive': 'npm:ng2-responsive/responsive',
  'ng2-responsive/responsive-window': 'npm:ng2-responsive/responsive-window',
  'ng2-responsive/useragent': 'npm:ng2-responsive/useragent',
  'ng2-responsive': 'npm:ng2-responsive',
  'ng-select': 'node_modules/ng-select'
},
packages: {
  Application: {
    main: './main.js',
    defaultExtension: 'js'
  },
  'ng2-cookies': {
    main: './ng2-cookies.js',
    defaultExtension: 'js'
  },
  rxjs: {
    main:'./bundles/rx.min.js', defaultExtension: 'js'
  },
  'ng2-responsive/bootstrap': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive/browsers': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive/config': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive/custom-sizes': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive/devices': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive/pixelratio': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive/responsive': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive/responsive-window': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive/useragent': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng2-responsive': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'ng-select': {
    main: 'index.js',
    defaultExtension: 'js'
  }
}

});
})(this);
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: 4.3.2
Material: 2.0.0-beta.8
OS: mac and windows
TypeScript: 2.4.2
Browsers: Chrome, Safari, IE
Is there anything else we should know?
I have created a new Angular-CLI project with material and that works fine. So it's not an issue in Angular or Material but something in my config files.
Does anybody have any idea what I'm doing wrong?

Found the solution for this: it was one of the css files in the my html file. After deleting this css file, everything worked again.


Swaps: min to receive

Thanks for noticing/reporting @pradel
It looks like the amount shown is divided by a hundred million the expected minimum is closer to 6.2 sUSDT (based on slippage tolerance)

This was code written by Alex team, not correct? What is correct here?

Current, new BigNumber(swapSubmissionData.swapAmountTo).times(1 - swapSubmissionData.slippage)

just formatting?

this looks like it should be ~6.2 in this example not 0.00000...6


CUDA_HOME environment variable is not set

Hi,
When I try running this from the readme usage section:
python main.py --text "a hamburger" --workspace trial -O
I get this error:
OSError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root.
What should I do about this?
Here is the full error:
C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\amp\autocast_mode.py:198: UserWarning: User provided device_type of 'cuda', but CUDA is not available. Disabling
  warnings.warn('User provided device_type of \'cuda\', but CUDA is not available. Disabling')
Traceback (most recent call last):
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\raymarching\raymarching.py", line 10, in <module>
    import _raymarching as _backend
ModuleNotFoundError: No module named '_raymarching'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 84, in <module>
    from nerf.network_grid import NeRFNetwork
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\nerf\network_grid.py", line 6, in <module>
    from .renderer import NeRFRenderer
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\nerf\renderer.py", line 12, in <module>
    import raymarching
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\raymarching\__init__.py", line 1, in <module>
    from .raymarching import *
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\raymarching\raymarching.py", line 12, in <module>
    from .backend import _backend
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\raymarching\backend.py", line 31, in <module>
    _backend = load(name='_raymarching',
  File "C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\utils\cpp_extension.py", line 1202, in load
    return _jit_compile(
  File "C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\utils\cpp_extension.py", line 1425, in _jit_compile
    _write_ninja_file_and_build_library(
  File "C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\utils\cpp_extension.py", line 1514, in _write_ninja_file_and_build_library
    extra_ldflags = _prepare_ldflags(
  File "C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\utils\cpp_extension.py", line 1617, in _prepare_ldflags
    extra_ldflags.append(f'/LIBPATH:{_join_cuda_home("lib/x64")}')
  File "C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\utils\cpp_extension.py", line 2125, in _join_cuda_home
    raise EnvironmentError('CUDA_HOME environment variable is not set. '
OSError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root.

What happens when you type "nvcc" into the command line? Or "nvidia-smi"? This might help https://github.com/facebookresearch/pytorch3d/issues/517

i had the same "ModuleNotFoundError: No module named '_raymarching'" error without the OsError for the home variable, I removed the underscore from '_raymarching' in raymarching.py on line 10 (just to try), it let me through until i hit an error "TypeError: _morton3D.forward() takes 2 positional arguments but 4 were given"

What happens when you type "nvcc" into the command line? Or "nvidia-smi"? This might help facebookresearch/pytorch3d#517

When I type nvcc, it gives an error "The term 'nvcc' is not recognized".
When I type nvidia-smi i do get something: A bunch of data pops up with a lot of N/A's. I don't want to link it yet cause I don't know if it shows any personal information that I shouldn't sent on the internet!

I also tried to follow the link you shared but it wants me to set CUDE_HOME variable in system variable but it wants it set to a path that I seem not to have.
Path: C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\bin
I don't have that path. I don't have a folder called "NVIDIA GPU Computing Toolkit"

That may be the problem. You are missing the CUDA toolkit. This happens when you either don't have the it installed or you don't have NVIDIA GPU (e.g. Mac does not have one and therefore you will get this error)

That may be the problem. You are missing the CUDA toolkit. This happens when you either don't have the it installed or you don't have NVIDIA GPU (e.g. Mac does not have one and therefore you will get this error)

Fortunately I have an NVIDIA GPU in my computer. I could try to install the toolkit but I removed the underscores in the code and it went a lot farther this time. I got to a point where it was downloading things it needed and then it even attempted to run the training process but then this error came up:
[INFO] loaded stable diffusion!
C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\cuda\amp\grad_scaler.py:115: UserWarning: torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.
  warnings.warn("torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.")
[INFO] Trainer: ngp | 2022-10-07_11-29-36 | cpu | fp16 | trial
[INFO] #parameters: 12248183
[INFO] Loading latest checkpoint ...
[WARN] No checkpoint found, model randomly initialized.
==> Start Training trial Epoch 1, lr=0.010000 ...
  0% 0/100 [00:00<?, ?it/s]C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\amp\autocast_mode.py:198: UserWarning: User provided device_type of 'cuda', but CUDA is not available. Disabling
  warnings.warn('User provided device_type of \'cuda\', but CUDA is not available. Disabling')
Traceback (most recent call last):
  File "main.py", line 145, in <module>
    trainer.train(train_loader, valid_loader, max_epoch)
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\nerf\utils.py", line 453, in train
    self.train_one_epoch(train_loader)
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\nerf\utils.py", line 665, in train_one_epoch
    self.model.update_extra_state()
  File "C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\autograd\grad_mode.py", line 27, in decorate_context
    return func(*args, **kwargs)
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\nerf\renderer.py", line 574, in update_extra_state
    indices = raymarching.morton3D(coords).long() # [N]
  File "D:\CodeProjects\VisualStudioCode\Other\DreamFusion\stable-dreamfusion\raymarching\raymarching.py", line 94, in forward
    if not coords.is_cuda: coords = coords.cuda()
  File "C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\cuda\__init__.py", line 211, in _lazy_init
    raise AssertionError("Torch not compiled with CUDA enabled")
AssertionError: Torch not compiled with CUDA enabled
  0% 0/100 [00:00<?, ?it/s]

Would this error be because of the missing tool kit still?

I think that removing the underscore wont fix your issue. The issue is still the same:
C:\Users\Matthew\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\cuda\amp\grad_scaler.py:115: UserWarning: torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.
  warnings.warn("torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.")

If you try running:
torch.cuda.is_available()

It should throw out True, otherwise you dont have CUDA available (maybe still not the toolkit available).

I suspect that what I changed is still good since even if I had got the CUDA issue solved, those would still pop up. But maybe not. Also where do I find the tool kit? And is there any special things I have to do to install it or does it come with an installer?

it is available on NVIDIA website, CUDA Toolkit https://developer.nvidia.com/cuda-downloads
you may want to look for  CUDA 11.6

So no that didn't fix it. I think I will just wait till someone makes a more accessible version or someone makes a website to run it in, even a google colabs project would work!

Hello, I think I have the same issue.
OSError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root.

If you try running:

torch.cuda.is_available()

returns True.


about lockpart settings

What are all the lockparts that you can configure? ( exunysdeveloperaimbot.settings.lockpart = ec: head, torso, neck )
basically, what are all the things i can put here?

Wrong repository for this issue.


MODOAIPMH-200: Implement the endpoint for getting list of sets

PURPOSE
Implement endpoint for retrieving list of sets.
https://issues.folio.org/browse/MODOAIPMH-200

INFO: lint-raml: Using lint-raml version: 1.4.2
INFO: lint-raml: Investigating and determining configuration: mod-oai-pmh/ramls
INFO: lint-raml: Not assessing schema descriptions, as per option '--validate-only'.
INFO: lint-raml: Assessing RAML files (https://dev.folio.org/guides/raml-cop/):
INFO: lint-raml-cop: Processing RAML v1.0 file: oai-pmh-set.raml
ERROR: lint-raml-cop:   raml-cop detected errors with oai-pmh-set.raml:
[ramls/raml-util/rtypes/collection.raml:59:0] ERROR Can not parse JSON example: Unexpected token '"createdDate"'
INFO: lint-raml-cop: Processing RAML v1.0 file: oai-pmh.raml
INFO: lint-raml-cop:   raml-cop did not detect any errors with oai-pmh.raml
ERROR: lint-raml: There were processing errors. See list above.

Note: When those errors are fixed, then the INFO messages will be gone too. See Jenkins "Artifacts" tab.

INFO: lint-raml: Using lint-raml version: 1.4.2
INFO: lint-raml: Investigating and determining configuration: mod-oai-pmh/ramls
INFO: lint-raml: Not assessing schema descriptions, as per option '--validate-only'.
INFO: lint-raml: Assessing RAML files (https://dev.folio.org/guides/raml-cop/):
INFO: lint-raml-cop: Processing RAML v1.0 file: oai-pmh-set.raml
ERROR: lint-raml-cop:   raml-cop detected errors with oai-pmh-set.raml:
[ramls/raml-util/rtypes/collection.raml:59:0] ERROR Can not parse JSON example: Unexpected token '"createdDate"'
INFO: lint-raml-cop: Processing RAML v1.0 file: oai-pmh.raml
INFO: lint-raml-cop:   raml-cop did not detect any errors with oai-pmh.raml
ERROR: lint-raml: There were processing errors. See list above.

Note: When those errors are fixed, then the INFO messages will be gone too. See Jenkins "Artifacts" tab.

INFO: lint-raml: Using lint-raml version: 1.4.2
INFO: lint-raml: Investigating and determining configuration: mod-oai-pmh/ramls
INFO: lint-raml: Not assessing schema descriptions, as per option '--validate-only'.
INFO: lint-raml: Assessing RAML files (https://dev.folio.org/guides/raml-cop/):
INFO: lint-raml-cop: Processing RAML v1.0 file: oai-pmh-set.raml
ERROR: lint-raml-cop:   raml-cop detected errors with oai-pmh-set.raml:
[ramls/raml-util/rtypes/collection.raml:59:0] ERROR Can not parse JSON example: Unexpected token '"createdDate"'
INFO: lint-raml-cop: Processing RAML v1.0 file: oai-pmh.raml
INFO: lint-raml-cop:   raml-cop did not detect any errors with oai-pmh.raml
ERROR: lint-raml: There were processing errors. See list above.

Note: When those errors are fixed, then the INFO messages will be gone too. See Jenkins "Artifacts" tab.


No login page

Hey,
There's probably a simple solution to this, but I don't get a login page after following all of the instructions. Instead, I just get a line of text and a changelog link: "Version - 0.6.0 #1a22bb1 - Changelog." What am I doing wrong here? Didn't see any errors during the process of installing. I'm running nodejs v0.12.7, mongodb shell version is 3.0.4, npm version 2.11.3, on Debian 7.
Mitch

Any errors in whether the web console or one of the two terminals? Seems like a weird issue. What you see is part of the template that is server-side rendered

No errors in either, but I imagine the error is still on my part. Any next steps to suggest? I'll redo the installation procedure in the meantime.

Check in the page, to see the url of the app.js. And try to access that directly. In hot server it should be something like localhost:2992...

Yeah, that's right; and no, I can't access it ("//localhost:2992/_assets/app.js") from my PC. I'm running this all on a google compute virtual machine instance. Is it just that I'm not viewing the site from the server from which I'm running? I've been able to deploy other apps and frameworks.

Hum that's a good question! I don't think the webpack config is made for that right now... I'll try to look at it tonight!

@mgleed Can you try with v0.6.1? I've proxied webpack from koa, so it should be fine now!

Unfortunately, with the new version, "npm run build && npm test" failed. Here is the npm log file:
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/bin/npm', 'run', 'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose node symlink /usr/bin/node
5 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
6 info prebuild<EMAIL_ADDRESS>7 info build<EMAIL_ADDRESS>8 verbose unsafe-perm in lifecycle true
9 info<EMAIL_ADDRESS>Failed to exec build script
10 verbose stack Error<EMAIL_ADDRESS>build: NODE_ENV=production webpack --config webpack.config.js --separate-stylesheet -p --progress --profile --colors
10 verbose stack spawn ENOENT
10 verbose stack     at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:17:16)
10 verbose stack     at ChildProcess.emit (events.js:110:17)
10 verbose stack     at maybeClose (child_process.js:1015:16)
10 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
11 verbose pkgid<EMAIL_ADDRESS>12 verbose cwd /home/mitchellgleed_gmail_com/tvapp/koa-react-full-example
13 error Linux 3.16.0-0.bpo.4-amd64
14 error argv "node" "/usr/bin/npm" "run" "build"
15 error node v0.12.7
16 error npm  v2.13.1
17 error file sh
18 error code ELIFECYCLE
19 error errno ENOENT
20 error syscall spawn
21 error<EMAIL_ADDRESS>build: NODE_ENV=production webpack --config webpack.config.js --separate-stylesheet -p --progress --profile --colors
21 error spawn ENOENT
22 error Failed at the<EMAIL_ADDRESS>build script 'NODE_ENV=production webpack --config webpack.config.js --separate-stylesheet -p --progress --profile --colors'.
22 error This is most likely a problem with the koa-react-full-example package,
22 error not with npm itself.
22 error Tell the author that this fails on your system:
22 error     NODE_ENV=production webpack --config webpack.config.js --separate-stylesheet -p --progress --profile --colors
22 error You can get their info via:
22 error     npm owner ls koa-react-full-example
22 error There is likely additional logging output above.
23 verbose exit [ 1, true ]

Can you delete node_modules and re-install? I'm in the dark right now, because test passed.

I just did another fresh install and it seemed to work this time! Not sure what happened last round, sorry about that. The page is up and running, and I see the sign-in page as expected.
Thanks!

Great :dancer:


[RCTDevMenu] Swizzle of motionEnded:withEvent: over riding existing implementations

I use the shake gesture in my app, and the current implementation of RCT_motionEnded:withEvent: is squashing my implementation. I'd like to change this method to call the existing implementation if one exists. (whether it be implemented via category or previous swizzle)
Would this be a desired pull request? If so, is there an existing preferred style of this type of swizzling in the React Native code base? (I've been storing procs via a static typedef variable when I will need to call the initial implementation eventually.)

@MattFoley You can see the original implementation here
https://github.com/facebook/react-native/blob/0764e4ef293eb19da6b52c74df5f154e04854e70/React/Modules/RCTDevMenu.m#L156.
I was able to create my own method to override this but couldn't really find a way a nice way to switch between my own and the dev menu.
Here's how that looked.
https://gist.github.com/christopherdro/8418aa334ec5e6027f0d
Hope this helps. :)

I was looking there when I posted this issue, and I thought about implementing something similar to your solution, but I don't think that's a permanent solution for React Native.
It would be pretty easy for me to fix this so both any existing implementation and the RN implementations are both called, and that is much more developer friendly.

Nice, that would be a really awesome addition!

Glad to hear it. It may take me a few days to get to it, but I will eventually and I'll link back to this issue when I do.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/rctdevmenu-swizzle-of-motionendedwithevent-over-riding-existing-implementations
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.

Same issue here, Instabug not working under Debug build type, but working under Release.
This makes difficult to test Instabug settings.


Exporter 400 status error in AWS ECS

I've deployed the exporter  to AWS ECS. I’m using CF_API_TOKEN to authenticate and I’m unable to resolve this error which occurs when the container is being launched:
http Status 400 invalid request headers (6003)
I’ve used tokens that were scoped for logging/analytics as well as global with no success. Any suggestions are appreciated. This is only an issue within ECS, running the container locally works without errors.

Could you share your task definition?
It could probably helps to find an issue


[HUDI-6179] Add description to the DeltaStreamer config group

Change Logs
As above.
Impact
Improves documentation and config page generation.
Risk level
none
Documentation Update
As above.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

CI failures are due to flaky tests.  Merging this PR.


Feature/add gitlab documentation

Adapted parts of the documentation to match an easier to follow getting started guide.
Changes

docs

Checklist

[x] Read the contribution guide and accept the code of conduct
[x] Readme (updated or not needed)
[x] Tests (added, updated or not needed)

@GabLeRoux shall we merge a WIP version in order to keep forward momentum?


"OpenCVExample/CPP" sample depends on abandoned "Microsoft/opencv" repository

I'm reporting issue to not your repository but your repository will never look well till "Microsoft/OpenCV" issues will not be solved. Please look at guide by link
https://github.com/Microsoft/Windows-iotcore-samples/tree/develop/Samples/OpenCVExample/CPP
It reference other link
https://github.com/Microsoft/opencv/tree/vs2015-samples
I you documentation you say "Download Microsoft's fork of the OpenCV library". You say download because "git clone" doesn't work
https://github.com/Microsoft/opencv/issues/83
Then look, for example I decided to use Windows IoT and OpenCV in my production solution on x84 and ARM architecture. You should provide the sample to mix it in the best way. We are happy that you evolve Windows-iotcore-samples but you have dependency to abandoned "Microsoft/opencv" repository and attaching dependent dll files in very bed way because you add dll files only for particular architecture. You are working in cook company that has MSBuild and lots of professionals so you should provide sample with good approach of linking OpenCV.
Microsoft is one company and both repositories "Microsoft/Windows-iotcore-samples " and "Microsoft/OpenCV" should look well. Please, try to ping the responsible man for "Microsoft/OpenCV" because only you may do this.
I also have created an issue https://github.com/Microsoft/opencv/issues/82
But I think that their issue is also issue of your repository.
We hope you will be able to manage this. Thank you.

@saraclay You just closed my complain.


[PDI-18401] Table Input Step in <IP_ADDRESS> with variables broken

[PDI-18401] Issue between 8.2 and 8.3 was that an extra dialog box opened up with redundant errors. These errors will be captured regardless. So the fix to restore previous functionality was to change the RuntimeException into a LogError.
[PDI-18401] Moved message statements into the appropriate message.properties file.

:white_check_mark: Build finished in 17m 19s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3601, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 26m
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3601, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 20m 25s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3606, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 17m 9s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3606, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


Docs: centos_INSTALL.md and debian_INSTALL.md, paths

I recommend replacing the instances of /root with $HOME.
Also i wonder if cd /opt are real necessary or can be changed to cd /tmp.

Hi @paololucente ,
(it's clearly not the final *_INSTALL version).
At the moment, to make it simpler, I'm assuming that the whole procedure is conducted as 'root'.
for what concerning '/opt' it is probably a good choice whenever the standalone version of the collector is installed, however it's not really necessary when the library version is installed.

Hi @paololucente ,
the *_INSTALL procedures are now officially deprecated. install.sh should be used instead.


User domain separator character should taken from the CarbonConstants

There are many places in our code where we have explicitly used "/" as the user store domain separator. This is a bad practice and also makes it hard to make the user store domain separator configurable.
A few places where we have hardcoded the user store domain separator.
https://github.com/wso2/carbon-identity-framework/blob/bd59e45738df29e66019eaeb2cbb7add855db052/components/user-mgt/org.wso2.carbon.identity.user.profile/src/main/java/org/wso2/carbon/identity/user/profile/mgt/UserProfileAdmin.java#L109
https://github.com/wso2/carbon-identity-framework/blob/bd59e45738df29e66019eaeb2cbb7add855db052/components/user-mgt/org.wso2.carbon.identity.user.profile/src/main/java/org/wso2/carbon/identity/user/profile/mgt/UserProfileAdmin.java#L120
We should improve the code to use the constant defined in CarbonConstants[1].
[1] https://github.com/wso2/carbon-kernel/blob/949e17f14eab27f857800eb8f5064d67432b19f1/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/CarbonConstants.java#L388-L397
Moved from: https://wso2.org/jira/browse/IDENTITY-5619

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


positionOfNext(String) improperly handles comments within string literals

ex:
String url = "https://example.com"

Given the above source string, if you were to execute positionOfNext("."), you would get -1 due to the // being interpreted as a line comment.
I discovered this one (similar example) while trying to fix the parsing of J.Case statements within the G island grammer (via GroovyParserVisitor), but a quick inspection shows that the J parsers also have the same defect.

More specifically this PR:
https://github.com/openrewrite/rewrite/pull/3021

@knutwannheden, this hasn't yet been fixed, so I've reopened the issue.

@knutwannheden, this hasn't yet been fixed, so I've reopened the issue.

Thanks for clarifying.

Apologies about the confusion there.
The PR that I linked, was more pointing to the bucket of work that I was performing to fix J.Case parsing in Groovy when I found this defect. In it's specific case, it was looking for the next , character when at the beginning of the first G.ListLiteral element's ". This defect resulted in it returning the , argument from the .join(String) method invocation.


Create example code for initialise custom EAM actor with whitelisted addresses

Create sample code/repo for users to know how to modify the code/genesis/config to use different permission mode in custom EAM actor.

We dont need this anymore as the genesis is updated to config this. We just need some documentation somewhere on using the cli.


Add toggle behavior

opening the extension more than once would leave previous iframes on the page

Thank you!