[ERR] SRVR: unable to create server: no active channels exist

Background
After starting LND and unlocking the wallet, LND reports an error starting the server reporting that no active channels exist after restarting the daemon and after successfully opening a channel. Unable to issue any commands at this point due to daemon stopping.
Your environment

lnd version 0.5.1-beta commit=
Linux thrasher-raspi-01 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
bitcoind 0.17.0

Expected behaviour
LND daemon continues running and allows commands to be issued to it (Abandon/Close the lost channel)
Tell us what should happen
Log
2019-01-02 00:56:10.547 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default
2019-01-02 00:56:10.547 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-01-02 00:56:10.549 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-01-02 00:56:10.559 [INF] RPCS: password RPC server listening on [::]:10009
2019-01-02 00:56:10.559 [INF] RPCS: password gRPC proxy started at <IP_ADDRESS>:8080
2019-01-02 00:56:10.561 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create a wallet, `lncli unlock` to unlo                                           ck an existing wallet, or `lncli changepassword` to change the password of an existing wallet and unlock it.
2019-01-02 00:56:36.157 [INF] LNWL: Opened wallet
2019-01-02 00:56:36.945 [INF] LTND: Primary chain is set to: bitcoin
2019-01-02 00:56:36.958 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on tcp://*:28332
2019-01-02 00:56:36.958 [INF] LTND: Initializing bitcoind backed fee estimator
2019-01-02 00:56:36.959 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on tcp://*:28333
2019-01-02 00:56:36.964 [DBG] LNWL: Using minimum fee rate of 253 sat/kw
2019-01-02 00:56:49.350 [INF] LNWL: The wallet has been unlocked without a time limit
2019-01-02 00:56:49.361 [INF] LTND: LightningWallet opened
2019-01-02 00:56:49.361 [DBG] LNWL: Birthday block has already been verified: height=551722, hash=000000000000000000267c87d375ebeecb20c86                                           a593de929cc9607e9269c4de5
2019-01-02 00:56:49.390 [INF] HSWC: Restoring in-memory circuit state from disk
2019-01-02 00:56:49.391 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
2019-01-02 00:56:49.392 [ERR] SRVR: unable to create server: no active channels exist

2019-01-02 00:56:49.393 [INF] LTND: Shutdown complete

Did you initially create the wallet with the same version of lnd?


Linting project package

Made a golint pass on package project 🐙.
Main changes :

Event becomes EventType and ProjectEvent becomes Event (because it's in project package already).
The event type names are now CamelCase and prefixed with Event : SERVICE_ADD -> EventServiceAdd.
The same with State.

Some improvements, to do probably later (in separate PR and some later on) :

when docker v1.9 will be released, vendor it and use StrSliceinstead of StringorSlice as it's doing the same thing.
Refactor a little bit types_yaml.go and there is some duplication between Command and StringorSlice and even more with MaporEqualSlice, MaporColonSlice and MaporSpaceSlice.

🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

LGTM

ping @aduermael @gdevillele

LGTM, also needs rebase
@vdemeester what did you use to automate these renames?  Was it just sed ?

@dnephin Good old GNU/Emacs, some temporary key binding and a good dose of patience :wink:.
Rebased too :smiley_cat:.

https://github.com/golang/tools/tree/master/refactor looks like an interesting set of tools (there's one for renaming things).  I've never used them, but I hope to get a chance to sometime soon.

@dnelphin gofmt let u do small refactoring too ;-)


Lotus RPC fixes

Summary of changes
Changes introduced in this pull request:

Fixes for making Forest CLI auth with and make RPC calls to the Lotus daemon

Reference issue to close (if applicable)

Closes #1222
Other information and links

let's revisit this once we get around it again.


SAK-33744: Apply keyboard navigation to GB column headers and cell menus

I tried this and found a few issues.

You can't escape from the View Columns dropdown, you have to tab your way out of it
You can't tab between the tabs in the item order lightbox.
In the cells, you can't trigger the dropdown menu, focus never moves to them.

So, a bit more work is needed. This is not easy work, so kudos for attacking it.

See my comment about missing things.

Thanks to you for the help to see the bugs that I have skipped.
The error of the view columns drop-down is resolved.
On the other hand you can access the upper menu by pressing ctr + space, you cannot easily change it to a tab since the table is made with handsontable and does not allow access with tab, we have already looked at it and would have to reimplement the entire table, if Any notes I can take care of let me know.


What's the difference from virtual dom libraries?

Good day!
Say please, what's the difference from virtual dom libraries making Inferno so fast?
Say from virtual-dom...
Thanks.

Ok, now I see readme of perf-spike branch, so another question: are there (global) differences unnoted there?

Hi @kuraga, thanks for checking Inferno out. The key difference is that Inferno uses templates to represent fragments of virtual DOM. The virtual DOM gets pre-compiled once into a DOM static nodes and gets given instructions and a shape. It then uses these to make highly optimal passes to the DOM to create/update/remove the dynamic parts. It never needs to "diff" virtual DOM, it simply diffs the values that get passed into the fragment and mutates the DOM structure it already knows about.
I hope that explanation helped detail what goes on within the core of Inferno!

@trueadm , thanks very much for reply! But further: Suppose the whole tree is dynamic. There are variables in each attribute, every tag name is variable and contents of tags are also variables :smile: Which scheme of updating do we have in this case, and are there differences from other libraries here?

@kuraga in the case that everything is dynamic, it would simply traverse through each shape in the tree and update each one, ensuring the changes are all carried out. This should be a very fast operation, still much faster than typical virtual DOM implementations as they still have to carry out a render to work out what has changed. Inferno already knows what can change so simply does a === check on values and updates as necessary.

@trueadm ,

does a === check

Left operand is property of Fragment object (e.g. {tag: 'li', attrs: { className: 'row' }, text: text}, and right operand is property of HTMLElement object, am I right?

@kuraga Sorry I'm a bit lost by that comment. Inferno will build a tree for the fragment {tag: 'li', attrs: { className: 'row' }, text: text}. The tree will consist of shape(s) that are highly optimised objects that do very specific tasks to the DOM or of child shapes in the tree.
In the example given, it would know only to "diff" the text value on that fragment, thus only touching the HTMLElement and its Text child object to change its nodeValue.

@trueadm Just my English is too bad to ask precisely... I'm asking about what exactly does it compare with ===.

simply does a === check on values and updates as necessary.

Can you point out a line of code of this check, please?

@kuraga it's done within the shapes, for example:
const nextValue = getValueWithIndex(nextItem, valueIndex);

if (nextValue !== getValueWithIndex(lastItem, valueIndex)) {
	domNode.firstChild.nodeValue = nextValue;
}

So, shape is compared with shape.
Thanks very much!
Last question: are there plans about unit tests

Yes, there are plans for UTs although the ATs provide great coverage and feedback given the fact the API of Inferno is tiny.

On 18 Dec 2015, at 13:07, Alexander Kurakin<EMAIL_ADDRESS>wrote:
So, shape is compared with shape.
Thanks very much!
Last question: are there plans about unit tests
—
Reply to this email directly or view it on GitHub.

Thanks very much!

@kuraga No problem! Inferno has always been about three things:
1 have the absolute best performance in regards to manipulation of the DOM
2 keep a React like API, allowing for people to migrate projects to Inferno with little overhead
3 have the absolute best performance when handing server-side rendered text (Node)
We're still to build on point 3, and point 2 still has some coverage that needs expanding on (stateless components for example). In its current state, Inferno simply destroys every other framework out there in terms of performance (virtual DOM and non virtual DOM frameworks alike). I've managed to get performance almost 30% faster in the vdom benchmark compared to the older Inferno thanks to help from the author of Cito and his methods of template initialisation.
I see great things from Inferno in the future and I'd love to get more people contributing and adding ideas if you're interested.

@trueadm Big thanks for discussion.
I am just trying to create own minimalistic component-based library. So, immutable model as a dependency, DOM manipulation as a dependency, and Application class (with application loop) and Component class (immutable). See: RotorJS.
It uses virtual-dom. And I like virtual-dom interface but yesterday I opened VDOM Benchmark... And saw that virtual-dom conception isn't optimized.
As I'm creating RotorJS just-for-fun-and-knowledges I'm interested of other conceptions. The fastest libraries are Inferno, Vidom and Snabbdom. Vidom's creator said that Vidom applies patches directly to DOM instead of "patch vDOM and then re-render the whole DOM". As I see, Inferno do the same. Both of you have "some additional optimizations" :smile: but code is too hard to see all of them now.
By the way, which "tricks" have been gotten from other libraries? So I'm interested of mechanisms and not real usage. And I'm a fan of conceptions "let's be compatible with standards but not other products", and "good interface and speed instead of simple entry point". So, I like very much point 1 and 3 but :-1: point 2 :smile: And sure :+1: for 100%-coverage of unit-tests (by the way, it's a good documentation, too!)
I hope I'll understand you're mechanisms, and maybe transfer RotorJS to Inferno. Because I like very much 1) static-parts idea and 2) apply directly to DOM. Hope, there are some more techniques... (which have or would been gotten from other libraries, too :smile: ) And code will be stable! :smile:

The author of Cito and I have been working on ideas and concepts for a very long time. I've not taken much inspiration from else-where to be honest as I don't see too much value in what other people are doing in the virtual DOM scene (all attempting to solve the same "problem" even though the problem to begin with shouldn't have been one). I'll keep an eye on RotorJS, it looks promising.
In respect to my point 2, it's simple why I've done this. If Inferno didn't do this, it would add very little value to anyone. The realism is this: if it's not React or React-like, no one will use it. The adoption of React and the fact it's quickly becoming the most used frontend view/component library makes it very hard to beat, especially with Facebook backing it. So in my opinion, it's best to offer an API surface that matches people using React, rather than try and convince them that React's API is all wrong.

@trueadm regarding point 2, couldn't that be handled with another library? React may be nothing in 1.5 years.

@stevenvachon whilst it's true, React might not be here in 1.5 years, I very much doubt that. React doesn't care about the DOM, it's more the fact it's addressed the hardest problem around, how to properly build componentized UIs regardless of their target endpoint (desktop, mobile, web etc). I don't see any other library coming remotely close to replacing React's principles.
I'm definitely behind a functional approach and using immutable data a single atomic store (i.e. Redux) to work with Inferno – as that's a very smart approach to complicated large scale applications. If people can simply do this: import {Inferno as React} from 'inferno' and their application gains an instant 10-20x performance boost, well that's a very compelling point indeed.

Yeah, agree with @trueadm ! Further-more I think (every) library should be as more modularized as possible... So, it's good idea to separate JSX (done), Ract-like features and DOM manipulate functions and component functions should (well, may) be in different libs...

@kuraga I like the idea of separating the DOM from the components, as React does with react-dom. I just haven't seen it as a priority right now.

Well, you're really fast result and painstaking (as of count of good-stored TODOs in code) approach are more important, you're right! :smile:

@trueadm do you plan to have hyperscript [1] or jsonml [1] transpiler (probably augmented with any needed Inferno-isms) so that a dev can use those shortened formats to define templates rather than the long-form required by Inferno's createElement?
i'm also wondering how a template compiled using createElement rather than template strings can determine the immutability of any node without regenerating the template - i did not see any way to indicate node immutability in these cases. does it just fallback to typical vdom recreate-the-world & diff/patch?
[1] https://github.com/dominictarr/hyperscript
[2] http://www.jsonml.org/

Inferno's Inferno.TemplateFactory.createElement is simply a factory method that creates a object literal that looks like { tag: 'div', attrs: {}, children: [ ... ] }. It would be very trivial to write your own that follows any other type of template out there, including hyperscript. These all go inside Inferno templates and works out what is dynamic or not by what is passed through as arguments.
const template = Inferno.createTemplate((val1, val2, val3) => ({tag: 'div', children: [val1, val2, val3]}))
Inferno.render(template('Value 1', Value 2', 'Value 3'), document.body);

So super easy to write and customise how you like, either at compile-time (for better performance) or run-time (no need for a transpiler/compiler).

ah i see. i think the missing piece in that scenario for me would be something like function argument reflection [1]. that way the template can be compiled once with getters/setters inserted in place of where the arguments are used in the func body so the diff can be done just on the passed args and the setters/DOM patch invoked where they differ.
[1] http://stackoverflow.com/questions/1007981/how-to-get-function-parameter-names-values-dynamically-from-javascript

@leeoniya if I'm not confusing your question, Inferno does this already. Templates are only compiled once. Each variable in the arguments represents a pointer to where the value exists in the arguments for the fragment.

no, no there's no question. just thinking out loud to grok the core idea and clarifying that it uses reflection to determine what parts of the func body are static.

@leeoniya this works the exact same as before. You can't do things like this inside templates val1 + val2 or  val1.map(...). Everything is literally based on pointers to values passed into the fragment. Exactly the same as how ES2015 template strings work.

got it, thanks!
btw, sorry for disappearing off gitter, i couldn't realistically help with my schedule and spend time troubleshooting the bunch of issues that came up with installing the build dependencies on Windows. Contributing wasn't as simple as "git clone, npm install, write js" :) Maybe i missed something.

I believe @Kflash fixed that with a new workflow, so you should be able to do that now on Windows! on the perf-spike branch anyway. Which is in far better shape than the new-build branch. Just getting test coverage up to 95%+.

@trueadm Do you have any sense of what the performance of perf-spike is like versus master(or what is on vdom-benchmark)?

In my testing, the new perk-spike was about 30% faster than the last Inferno on the vdom-benchmark. :)

@trueadm ,

keep a React like API, allowing for people to migrate projects to Inferno with little overhead

vs

While the cito.vdom API is kept simple

What do you think? Not a good option?

Maybe we are mistaking different things, I was talking about the Component Lifecycle API. If we're talking about the general API, Inferno's API is vastly simpler than both.
Inferno.render() does everything you need, mounting, partial mounting and unmounting.
React's best API is its component API, i.e: componentDidMount, componentWillUpdate etc.

Hm... Yes. I'm interested about DOM manipulation :smile:

Can the diff algorithm be used for diffing "real" DOM nodes or is it tied to inferno's vdom implementation ?

@kapouer Inferno only diffs against Inferno's vdom nodes and tries to avoid touching the DOM where possible (for better performance). The only exception to this is where Inferno needs to hydrate the vdom against the real DOM (which is currently a WIP for 0.8).

I'm asking because there is no "perfect" solution for diffing real dom nodes using basic level1 api (nodeType, attributes, nodeName, childNodes). Morphdom is not right and diffDOM has subtle errors,
hence the interest - but i don't want to take hostages about that :)

hi there can anyone help me how to use inferno js in php, i mean what must i do for make it working in php, i use inferno v1.0.0 beta 37, thanks before .

@trueadm Do you have any sense of what the performance of perf-spike is like versus master(or what is on vdom-benchmark)?

This page seems not exists

@mcooder the benchmark was removed a while ago. This is a very old thread.


Unofficial Extras callbacks

Currently only squad update and language change are supported callbacks. The keybind change callback as well as the upcoming chat message callback need to be added.

Keybind change callback has been added in https://github.com/Zerthox/arcdps-bindings/commit/c5314c36d846499e84e32a6a8a407211e25d1e06 https://github.com/Zerthox/arcdps-bindings/commit/fd038c84133512d2cfdde007b6a9a06e88b0bba2.

Closing. Upcoming chat message callback is now tracked in #7.


Continuous undoing things while pressing Ctrl+Z

Right now if we press Ctrl+Z, only one "undo" is done. No matter how long we're pressing it.
I think it should activate "continuous undo mode" after holding Ctrl+Z for more than 0.5s (or different value) to undo things faster/more efficiently.

This is because MenuButton ignores echo's.
#36493 should resolve this.

I think https://github.com/godotengine/godot/pull/36493 has indeed fixed this. Holding Ctrl+Z on master build does undo continuously.


[REQUEST] Add option to extract only certain flags from the pattern in extract

Implemented and planned for release v0.0.1.


Add ProjectImportedEventArgs so loggers are notified when a project is imported

This ties into the new evaluation context as well.
Event triggers if an import does not occur because the condition is false, an import does not occur because a wild card does not match, or an import occurs.

Will this tell me when an SDK style project is expanded?

It's awesome to have this, do you think we could get this in today so I can hack on the viewer over the weekend? I'd like to implement preprocessed view for projects.

@KirillOsenkov sorry this didn't make it on Thursday because I hit an issue with testing it out.  I'm hoping to get things resolved in stand up today.

@dotnet-bot test OSX Build for CoreCLR please

So what about the SDK style projects? Will it report when imports are made for the SDK props and targets?

@KirillOsenkov yes, all evaluated imports will be logged.

Awesome. So, let's get this in?

Looks great!

BTW I've already implemented stitching preprocessed views together based on this. Works like a charm.


https://github.com/Victoria129/ruby-capstone/projects/1

We are two people in this group.
Team member #1 - Victoria Tumwebaze
Team member #2 - Samuel Knower Amankwaa-Frempong

Hi @Victoria129, @frempongdev,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that has missing information in the Description, kindly make sure to add a link to the GitHub Project
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.

Hi @frempongdev  @Victoria129   ,
Great job for implemented  the some of the Project Requirement , but there are some changes that need to be implemented in order to proceed to the next project 👍
Highlights 👏🏻
✔ Good Job for Provide link to their GitHub project
✔ Good Job for Provide Information about the number of people in their group
✔ Good Job for Implemented Ruby group capstone: set up your Kanban board

Required Changes ♻
Check the comments below the review.

[ ]  As stated in the project requirement Kindly make sure that each card on the board has the number of points in the [Xpt] prefix. That number should indicate the number of points that show how complex the task is. 1 point = 1 hour of work.
a description of the task and Has a description of the task.

[ ] But in the case of yours Kanban board there is no he number of points in the [Xpt] prefix on all of your cards and some of your cards has no  a description of the task. Just Like the following cards, So Kindly Fix it before resubmit for review.

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Hi @Victoria129  & @frempongdev
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights
:heavy_check_mark: Number of points for each card added
:heavy_check_mark: Great effort in making the requested changes
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Problem running MindsDB with CrateDB

Hi there,
@hammerhead recently evaluated the Forecasting Quarterly House Sales with MindsDB tutorial with CrateDB and this Python driver (thanks!), so I would like to report about the outcome.
With kind regards,
Andreas.
Report

An error is thrown while computing the model, and the model is set to failed. The same example works well when using PostgreSQL.

INFO:type_infer-6520:Analyzing a sample of 5
INFO:type_infer-6520:from a total population of 5, this is equivalent to 100.0% of your data.
INFO:type_infer-6520:Infering type for: saledate
INFO:type_infer-6520:Column saledate has data type categorical
INFO:type_infer-6520:Infering type for: ma
INFO:type_infer-6520:Column ma has data type binary
INFO:type_infer-6520:Infering type for: type
INFO:type_infer-6520:Column type has data type binary
INFO:type_infer-6520:Infering type for: bedrooms
INFO:type_infer-6520:Column bedrooms has data type binary
WARNING:type_infer-6520:Column saledate is an identifier of type "UUID"
WARNING:type_infer-6520:Column bedrooms is an identifier of type "No Information"
INFO:dataprep_ml-6520:Starting statistical analysis
INFO:dataprep_ml-6520:Dropping features: ['saledate']
Traceback (most recent call last):
  File "/path/to/mindsdb/lib/python3.8/site-packages/pandas/core/indexes/base.py", line 3361, in get_loc
    return self._engine.get_loc(casted_key)
  File "pandas/_libs/index.pyx", line 76, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/index.pyx", line 108, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/hashtable_class_helper.pxi", line 5198, in pandas._libs.hashtable.PyObjectHashTable.get_item
  File "pandas/_libs/hashtable_class_helper.pxi", line 5206, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 'saledate'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/path/to/mindsdb/lib/python3.8/site-packages/mindsdb/integrations/libs/ml_exec_base.py", line 128, in learn_process
    ml_handler.create(target, df=training_data_df, args=problem_definition)
  File "/path/to/mindsdb/lib/python3.8/site-packages/mindsdb/integrations/handlers/lightwood_handler/lightwood_handler/lightwood_handler.py", line 67, in create
    run_learn(
  File "/path/to/mindsdb/lib/python3.8/site-packages/mindsdb/utilities/functions.py", line 58, in wrapper
    return func(*args, **kwargs)
  File "/path/to/mindsdb/lib/python3.8/site-packages/mindsdb/integrations/handlers/lightwood_handler/lightwood_handler/functions.py", line 147, in run_learn
    run_generate(df, predictor_id, args)
  File "/path/to/mindsdb/lib/python3.8/site-packages/mindsdb/utilities/functions.py", line 58, in wrapper
    return func(*args, **kwargs)
  File "/path/to/mindsdb/lib/python3.8/site-packages/mindsdb/integrations/handlers/lightwood_handler/lightwood_handler/functions.py", line 58, in run_generate
    json_ai = lightwood.json_ai_from_problem(df, problem_definition)
  File "/path/to/mindsdb/lib/python3.8/site-packages/lightwood/api/high_level.py", line 74, in json_ai_from_problem
    stats = statistical_analysis(
  File "/path/to/mindsdb/lib/python3.8/site-packages/dataprep_ml/insights.py", line 61, in statistical_analysis
    df = cleaner(data, dtypes, args.get('pct_invalid', 0),
  File "/path/to/mindsdb/lib/python3.8/site-packages/dataprep_ml/cleaners.py", line 57, in cleaner
    data = clean_timeseries(data, timeseries_settings)
  File "/path/to/mindsdb/lib/python3.8/site-packages/dataprep_ml/cleaners.py", line 397, in clean_timeseries
    if pd.isna(row[tss['order_by']]):
  File "/path/to/mindsdb/lib/python3.8/site-packages/pandas/core/series.py", line 942, in __getitem__
    return self._get_value(key)
  File "/path/to/mindsdb/lib/python3.8/site-packages/pandas/core/series.py", line 1051, in _get_value
    loc = self.index.get_loc(label)
  File "/path/to/mindsdb/lib/python3.8/site-packages/pandas/core/indexes/base.py", line 3363, in get_loc
    raise KeyError(key) from err
KeyError: 'saledate'

Hi. The upstream issue has been closed as completed, but without any further information. Can we re-evaluate the situation?
-- https://github.com/mindsdb/mindsdb/issues/5483#event-11584077360

Hi,
I checked the commit history since the last time I looked at it, and I don't see any changes. The closing of the upstream issue probably has to be interpreted as "won't fix", since there are also no linked pull requests or anything else.

Thanks. Can you re-open the issue, and can we discuss it? I would like to use your insights to eventually submit a patch, when applicable. However, I haven't approached the topic yet, a concise minimal reproducer could help.

Dear @chandrevdw31,
thank you for submitting GH-118. Does that mean MindsDB works well together with CrateDB now?
As you can read from this discussion, we could not derive any clear outcome from https://github.com/mindsdb/mindsdb/issues/5483 ff., and did not re-evaluate the situation yet on our behalves.
With kind regards,
Andreas.

Thank you very much, Chandre. Do you have any news to report about this matter?
/cc @hlcianfagna

Hi again. Hereby, let me also ping @kneth. Maybe he can team up with @chandrevdw31 to make a difference in resuming progress here?

https://github.com/crate/crate-clients-tools/pull/118


Build Python SDK for HCX Participant System to help in integrating with HCX

Project Details
What is HCX?
The Health Claim Exchange(HCX) Specification is a communication protocol that facilitates the exchange of health claim information between payers, providers, beneficiaries, and other relevant entities. It is designed to be an interoperable, machine-readable, auditable, verifiable, which helps ensure that the information being exchanged is accurate and trustworthy. It is an open standard based communication.
More details are here
Features to be implemented
Build a python SDK for integrator to integrate with HCX.

Understanding JSON Web Encryption
Parsing and validating incoming requests.
Generating outgoing requests.

Current Scenario: Currently, SDKs are available in Java and .Net.
Acceptance Criteria: A python SDK which will process the incoming and outgoing requests of the participant.
Learning Path
Complexity
Medium
Skills Required
Python
Name of Mentors
@shiva-rakshith @saurabh-singh-17 @maheshkumargangula
Project size
8 Weeks
Milestones

[ ] Understand HCX APIs
[ ]  Build python SDK which will initialize participant configuration, processes requests received by the participants and generates  requests that need to be sent by the participant.

I would like to work on this issue.

I am interested in this project. I am quite familiar with Python and it's related libraries and have contributed to open source projects using this tech stack. I would love to build the Python sdk for this project.

This project looks really interesting! As a Python enthusiast, I'm excited about the opportunity to work with Python as the tech stack. I'd love to contribute to this project and learn from the team.

I am new to this stuffs but would love to contribute

Hi , I would like to contribute to this project as I am very familiar with Python and it seems very interesting to me .I am going to submit a proposal on this :)

take me in.

Hi, I'm interested in this project. I have prior experience with python. I want to work on this issue and contribute to this project.

Hi could you please elaborate a little more process requests by participant i.e what type of data would be the input(an example would be helpful) and what type of response needs to be generated. Is it just parsing, validating and giving response or some kind of process automation?

Hi, I'm interested in this project. I have knowledge in python.

Hi, I will be very excited to work with you

I don't know how to work on this project. Can you give any information
about this project.

Hi, I'm interested in this project. It would be great to work on this project and bring in more creativeness and innovation to the idea.

i am intrested in this project

I have prior experience in Python and I'm enthusiastic about joining this project. I'm eager to contribute my skills and knowledge to address the issues at hand and make a positive impact on the project.

I am fairly proficient in the language and would like to contribute to this issue. Please assign me this.

i have good knowledge in python skills i am very much intrested to contribute on this issue i will give my 100 percent on this project

Hi, I would like to contribute to this. May I know how can I get started? By the way, I'm also submitting it on C4GT. But I would love to contribute anyway.
Skills I Have: Python, different API working and integration into platforms.

Hello Sir,
I am currently in final year of BSc  from IIT Madras. I am proficient with python and have build web applications using python in past. I am really interested to work on this project using Python.
Please have a look at my most recent python project link

Hi All,
Glad to hear that you are interested in contributing to this project. Please submit your proposal.

hello sir,
being proficient in this programming language and also having built quite a few projects also I feel that this will be a great project for me to show my expertise.
Kindly allow me to contribute.
Also, could you explain what all problems are we facing with this so that I can mention it.

Sir,
I am interested in this project and also I have very good experience in python programming. I think I can make a very good contribution to the project

Hello sir, I possess strong proficiency in working with Python.  So I would love to work on this project. Please assign me and let me know how can I start working on this project.

Hello sir, I have experience of working with almost 2 years in python, in different fields and hence have explored the language quite well. Hence I feel that I could be the right match for working in this project.

Hello sir. I have experience in integrating different products from one architecture to another. I have also experience in Python and Javascript. I am submitting my proposal and ideas for this project on c4gt since I feel this particular project has great potential to make an impact on society. It would be extremely kind of you to consider me for contributing to this project.

Hi @shiva-rakshith, I am really interested in the project. Can you please elaborate on the acceptance criteria for C4GT. Do we need to build python SDK before selection or after selection. If not then please elaborate on the acceptance criteria to get selected for C4GT.
Thanks.

Hi @shiva-rakshith  ,
I'm Jainendra Tripathy, and I am interested in contributing to this project. I'm an AI and ML developer with good hands-on experience in Python.
I have a strong understanding of Python, and I'm always looking for new ways to learn and grow. I'm also a quick learner and always willing to help.
I'm available to contribute . I'm eager to get started and make a difference. I'm confident I can help you take this project to the next level.
If you're interested in having me contribute, please let me know. I'm happy to answer any questions you have.
And I am also applying to the C4GT too please consider my application.
Thanks,
Jainendra Tripathy

Hi @shiva-rakshith,  i am keen on contributing to this project. I am confident on my skills and i can work through the fundamental understanding of this project and establish good shape to it by achieving the milestones with greater efficiency.

@shiva-rakshith @saurabh-singh-17 @maheshkumargangula
Dear Sir's
I am interested to join and contribute in this project. I have required knowledge in python and i'm kinda a quick learner and I can adapt to new things!.

@shiva-rakshith @saurabh-singh-17 @maheshkumargangula
Respected Mentors,
I am intrested in this project and I want to  contribute in this project. I am very much familiar with Pyhton and have build ML & AI  related projects for it  one of them is listed below :
https://github.com/VivekPrakashNitH/open-air-gym

Dear Mentors,
I am writing to express my interest in the project . I am a freshy Python developer with experience in building SDKs and integrating with cloud-based systems. I am also familiar with the HCX Participant System and I am confident that I can contribute to this project.

Sir, I would like to contribute to this. I have knowledge of python and have used its libraries for Image Processing, Deep learning projects. This would be a great opportunity for me.
Looking forward in contributing to this.

Dear Mentors, I have submitted my proposal for the project  "Build Python SDK for HCX Participant System to help in integrating with HCX #51"..and looking forward to learn and contribute.
Thank you!!

Dear Mentors,
I would like to express my strong interest in working on the Python SDK development project for integrating with the Health Claim Exchange (HCX) system. With my solid command over Data Structures and Algorithms (DSA) and proficiency in Python, I am confident in my ability to contribute effectively to this project. I am eager to learn the HCX APIs, design the SDK, and ensure seamless communication and data exchange between all participants. I would greatly appreciate the opportunity to work on this project.
Thank you for your consideration.
Sincerely,
Darshan Sharma

I would like to contribute to this. I have knowledge of python and have used its libraries for Image Processing, Deep learning projects. This would be a great opportunity for me.
Looking forward in contributing to this.


Fix transparency state initialization

Initialize some Instance members and store transparency so it's not lost when the instance doesn't have a base.

Thanks!


Module build failed after update to 2.0.1

Hi,
I am getting the below error on 2.0.1, but not on 2.0.0.
Error: Module build failed (from ./node_modules/vue-md-loader/index.js):
TypeError: this.getOptions is not a function
    at Object.module.exports (E:\git\project\node_modules\vue-md-loader\index.js:7:24)
    at eval (webpack-internal:///./src/assets/markdown.md:1:7)
    at Object../src/assets/markdown.md (https://localhost/js/app.js:5881:1)
    at __webpack_require__ (https://localhost/js/app.js:854:30)
    at fn (https://localhost/js/app.js:151:20)
    at VueComponent.created
    ...

I could be totally wrong, but looking at the source and what changed, I would guess that loader-utils should not have been removed like they were in 59ae702. The v3 way of calling getOptions() makes it seem like we don't need the dependency but I guess we do.
Downgrading fixes it for me, but I thought it was worth pointing out anyway.

Hello. Thanks for report. I guess this is a mistake, if you're using webpack v5, this should not happen. I just updated the release note to point this out. If you still need webpack v4 or lower, pls use 1.x of this plugin. Thanks.
If you are using webpack v5 then this issue happens, pls let me know. We can continue on this topic.

That makes sense. I cannot go into webpack upgrade at the moment, so I'll stay on the old version. Thanks for clearing it up!

Welcome.


Redux-form submit buttom

as

use version "redux-form": "^5.3.6", it will definately solve the problem


RandomSecret is now appending a data folder as of v0.8.18

Somewhere between v0.8.14 and v0.8.18 RandomSecret starting appending a data folder to the secret path.
Example:
apiVersion: redhatcop.redhat.io/v1alpha1
kind: RandomSecret
metadata:
  name: spatial-frontend-pipeline
  namespace: spatial-frontend-pipeline
spec:
  authentication:
    path: kubernetes/vault-config-application-configurator/aw-ue1-mt1
    role: pipeline
    serviceAccount:
      name: pipeline
  isKVSecretsEngineV2: true
  path: pipeline/kv/data/ci-automation/github-webhook-secrets/
  secretFormat:
    passwordPolicyName: 30-char-alphanumeric-only
  secretKey: secret

writes a secret value to pipeline/kv/data/ci-automation/github-webhook-secrets/data/spatial-frontend-pipeline
older versions of RandomSecret wrote the secret to pipeline/kv/data/ci-automation/github-webhook-secrets/spatial-frontend-pipeline
it seems like a data is being prepended to the metadata.name now. This is not desired since the final path does not match spec.path.

I do confirm that I experience this problem as well.
All deployments upgrading to v0.8.18 is failing because of this issue - this makes it a blocker.
Root cause analysis
This change comes from PR #175 merged and delivered in v0.8.17 (see https://github.com/redhat-cop/vault-config-operator/releases/tag/v0.8.17).
The idea of this PR is to remove the burden from the user to deal with the /data part of the path that Vault requires when dealing with kv-v2 by automatically adding it.
This is done by this code part: https://github.com/redhat-cop/vault-config-operator/blob/v0.8.17/api/v1alpha1/randomsecret_types.go#L95-L98
The logic added by this code change is to add the /data to the configured path attribute if not already there in the kv-v2 case.
This logic is actually flawed: the /data path segment must lie right after the kv-v2 mount path, but before any path within this secret engine, as specified in https://developer.hashicorp.com/vault/api-docs/secret/kv/kv-v2#create-update-secret :

POST | /:secret-mount-path/data/:path

With vault-config-operator, the last segment of the path is the name of the RandomSecret entity.
But nothing prevents adding intermediate path levels between /data and this name - this is actually quite useful and normal with kv use cases.
Illustration with the RandomSecret below (few details stripped out for conciseness) using a kv-v2 engine mounted at /kv/usage1:
apiVersion: redhatcop.redhat.io/v1alpha1
kind: RandomSecret
metadata:
  name: myownsecret
spec:
  isKVSecretsEngineV2: true
  path: /kv/usage1/data/test
  secretKey: secret

This should create a kv-v2 secret at relative path test/myownsecret (full path: /kv/usage1/data/test/myownsecret, but this code change creates it at test/data/myownsecret (full path: /kv/usage1/data/test/data/myownsecret), which is wrong.
Note that specifying path: /kv/usage1/test (as this code change would have suggested) fails entirely, because the generated path is then /kv/usage1/test/data/myownsecret which is not API compliant and is rejected by the kv-v2 API endpoint.
Potential mitigations

Alternative 1

To allow the user to avoid dealing with the /data path segment her/himself, knowledge about the mount path of the kv-v2 secret engine is required: this would allow to insert this /data segment after the secret engine mount path if not already there.
This would require to query Vault for the kv-v2 secret mounts (hence also requiring the appropriate permissions to do so against /sys/mounts , see https://developer.hashicorp.com/vault/api-docs/system/mounts#list-mounted-secrets-engines ), get their mount paths, and strip the longest match against those mount paths from the path attribute to add the /data path segment if required.
It looks a pretty nasty heavy chunk to swallow...

Alternative 2

Revert this logic change (and the corresponding doc section) - still leaving the doc improvements in place, though.
This peculiar /data path requirement in Vault's kv-v2 secret engine is disturbing for users, right, but it's Vault's own requirement - why should the vault-config-operator take care of doing this?
Attempting to hide this away from the user is also probably not a good idea, especially that this is clearly documented and advertised in Vault's documentation.

Additional note

The RandomSecret admission controller (https://github.com/redhat-cop/vault-config-operator/blob/main/api/v1alpha1/kubernetessecretenginerole_webhook.go) could be slightly augmented to check that the path attribute does contain a /data/ substring when attribute isKVSecretsEngineV2 is true.
This would help users to understand immediately that there is a problem and avoid them scratching their head about why the secret is not created in Vault until they go checking the operator's log (which can be messy if there is activity going on).
@raffaelespazzoli and @trevorbox what's your take on this?

@raffaelespazzoli and @trevorbox any news on this one?

Hello,
Is there any workaround to use RandomSecret CR with versions later than 0.8.18?

@davoustp thanks for the rca on this issue. PR is coming...

Awesome, thanks @trevorbox and @raffaelespazzoli ! 🥇


Add a --skip-build flag for npm install

At the end of npm install, it runs a full build.  This is great for a lot of use-cases but sometimes I just need to resolve a conflict in the package-lock.json quickly and the build is only going to get longer.  Could we consider adding a --skip-build flag of some kind to the install task?

Yeah, I've had the same annoyance regarding regenerating package-lock.  I'm cool with this suggestion.  I'd also be cool with removing the automatic build entirely.  Running npm install and then npm run build when necessary would be just fine.


mWeb - Chat scrolls back to linked message after receiving new message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/44819
Action Performed:

Open a chat conversation with a user(B) that has scrollable history
Go to the top comment and copy the link to that comment
Open another chat, send link and tap link to navigate to comment
Scroll to bottom to chat conversation
With User B, send any message to chat

Expected Result:
User receives new message smoothly
Actual Result:
Chat conversation scrolls up to highlighted message that was navigated to initially
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/54c40146-2a95-4c34-9e45-78c99b4ebb2d
View all open jobs on GitHub

@bfitzexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

I guess this came from https://github.com/Expensify/App/pull/41962

Proposal
Please re-state the problem that we are trying to solve in this issue
Chat scrolls back to linked message after receiving new message
What is the root cause of that problem?
In here:
https://github.com/Expensify/App/blob/c973e622ac7bf94a537b01e75408aff782123db3/src/pages/home/report/ReportActionsView.tsx#L141-L143
and in here:
https://github.com/Expensify/App/blob/c973e622ac7bf94a537b01e75408aff782123db3/src/pages/home/report/ReportActionsView.tsx#L146-L157
We depend the useMemo and useLayoutEffect on route which is from useRoute.
Each time user receive new message, the route changes and retriggrer both the useMemo and useLayoutEffect. Inside useMemo the isFirstLinkedActionRender.current will be set to true and will make the report scroll to the linked message.
What changes do you think we should make in order to solve the problem?
We could depend the useMemo and useLayoutEffect above on route.path instead of route.

Cool, assigning you @ishpaul777

@tsa321 can you please link your Upwork profile?

Offer sent @tsa321.
I'm now out of office, so adding a BZ buddy to finalise the payout
@ishpaul777 can you complete the BZ checklist:

[ ] The PR that introduced the bug has been identified. Link to the PR:
[ ] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] Determine if we should create a regression test for this bug.
[ ] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:


RUMM-2335 Add Session Replay Public API tests

What does this PR do?
In this PR we are adding the unit tests for the Public API of Session Replay feature.
Please not that the nightly tests coverage was dropped to 0.90 due to the newly introduced 2 methods. These will be covered later in another PR once Session Replay alpha will be ready.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

:exclamation: No coverage uploaded for pull request base (feature/session-replay-vo@68da559). Click here to learn what that means.
The diff coverage is n/a.

@@                     Coverage Diff                      @@
##             feature/session-replay-vo     #985   +/-   ##
============================================================
  Coverage                             ?   82.70%
============================================================
  Files                                ?      299
  Lines                                ?     9835
  Branches                             ?     1622
============================================================
  Hits                                 ?     8134
  Misses                               ?     1216
  Partials                             ?      485


[SPARK-28056] [PYTHON] add doc for SCALAR_ITER Pandas UDF

What changes were proposed in this pull request?
Add docs for SCALAR_ITER Pandas UDF.
cc: @WeichenXu123 @HyukjinKwon
How was this patch tested?
Tested example code manually.

Test build #106598 has started for PR 24897 at commit f91604b.

Test build #106598 has finished for PR 24897 at commit f91604b.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

LGTM.

Test build #106604 has started for PR 24897 at commit eacb5e4.

Test build #106604 has finished for PR 24897 at commit eacb5e4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged into master.

Hi @mengxr, can you update here too?
https://github.com/apache/spark/blob/113f8c8d136d493ca34f3d29985df870a368a39f/python/pyspark/sql/functions.py#L2908-L2952

Will submit a PR!


Arrival time predicted by TauP is different from the one of pyOcto?

Hi, I tried calculating arrival times using TauP model in obspy, my layered model and the event location output by pyOcto. Then I calculated the difference between the arrival times modelled by TauP and the phase picks that had been used as input to pyOcto. I found that the difference was larger than the residual output by pyOcto. I have also tried cake from pyrocko, but it just returned an empty list. Could you how pyOcto forward model the arrival time? Thanks!

Hi @zhong-yy ,
I assume you're using PyOcto with a 1D model? The calculation is defined here. It is using an eikonal solver. Potential sources for differences that come to my mind are:

PyOcto takes station elevation into account in an approximate way only. It calculates the travel time to the zero-plane and adds a correction for the elevation assuming vertical incidence and a fixed velocity.
PyOcto assumes all layers are gradient layers. Some ray traces assume constant velocity per layer.

Hi @yetinam  thank you very much for the explanation. I think it is because I didn't set up the 1D model for ray tracing properly.


Spinner: Adds isDelayed prop to component

There is a class in SLDS which adds a 300ms delay to the spinner,
but it wasn't being used here. This commit adds a prop isDelayed
to add that class to the spinner if needed.
Fixes #1891
Additional description

CONTRIBUTOR checklist (do not remove)
Please complete for every pull request

[x] First-time contributors should sign the Contributor License Agreement.  If you haven't before, wait a few minutes and a bot will comment on this pull request with instructions.
[x] npm run lint:fix has been run and linting passes.
[x] Mocha, Jest (Storyshots), and components/component-docs.json CI tests pass (npm test).
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[x] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[x] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

REVIEWER checklist (do not remove)

[ ] TravisCI tests pass. This includes linting, Mocha, Jest, Storyshots, and components/component-docs.json tests.
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

Required only if there are markup / UX changes

[ ] Add year-first date and commit SHA to last-slds-markup-review in package.json and push.
[ ] Request a review of the deployed Heroku app by the Salesforce UX Accessibility Team.
[ ] Add year-first review date, and commit SHA, last-accessibility-review, to package.json and push.
[ ] While the contributor's branch is checked out, run npm run local-update within locally cloned site repo to confirm the site will function correctly at the next release.

I went ahead and added the Jest DOM snapshots for the Spinner.
@pulkonet Looks good! Thank you.


Mobile App in React Native

Is it a good idea to start the development of a Mobile App for Traccar in React Native?

that would be awesome

Personally I don't think it makes much sense. I think it's better to put time into making the web app that can work well on mobile screen.

Ionic Capacitor can be use to make a good hybrid mobile app, it would take lot of stress out compared to the react native option.
I'm currently creating an app with vue.js and capacitor and it quite nice.

We already have a React based app. Why invent something else?


Embeddium donation prompt is rendered transparent

Environment:

Minecraft 1.21
NeoForge 21.0.141-beta
AcryliCraft neoforge-1.6.1+1.21
Embeddium 1.0.7+mc1.21
YetAnotherConfigLib 3.5.0+1.21-neoforge

Embeddium

With AcryliCraft

Seems like they have a timer to keep track of the installation time and show this prompt, making it tricky to reproduce this bug. Did you also find any other screen rendered like this?

I tried to modify the value after "t": in embeddium-fingerprint.json to ensure that it could be reproduced again.

That did the trick, I'll see what I can do with the rendering.

Oh, my fault. They accidentally render the background again after drawing the prompt content, and my code just clears up everything when background is rendered, including their already rendered UI. The 2 buttons weren't affected because they're rendered afterwards as renderables on the screen.

This should fix this problem and similar problems alike.


[DOCS-289] Add a PR template

Changelog
Added

Page
Deploy Preview
Comment

[Name]
[Link]
[Comment]

Updated

Page
Deploy Preview
Comment

[Name]
[Link]
[Comment]

Preview This Change
To see how this change looks in production, scroll down to Deploy Preview. Select the link that looks like https://deploy-preview-<num>--cobalt-docs.netlify.app/
Variables
Help us support a “Write once, publish everywhere” single source of truth. If you see a line that looks like:
{{ % asset-categories % }}
You’ve found a shortcode that we include in multiple documents.
You’ll find the content of the shortcode in the following directory:
https://github.com/cobalthq/cobalt-product-public-docs/tree/main/layouts/shortcodes
That shortcode has the same base name as what you see in the PR, such as asset-categories.html.

@mjang-cobalt Reopening this PR to add an example shortcode to the template. Initially, I thought the shortcode {{% asset-categories %}} wouldn't render properly, but I think it looks good. Let's try to check it once again.


lapps and lif discriminators

These are two separate discriminators but they have the same URI  http://vocab.lappsgrid.org/ns/media/jsonld#lif which looks funky.
It also involves some weirdness in discriminators.config line 143.
Maybe get rid of one of them.

Since this is a breaking change it should really be timed with the next major release (3.0.0) of the org.lappsgrid.discriminator module. The DSL generates Java code so we will need to identify any other code that uses Uri.LAPPS.
In the meantime I will investigate marking the relevant bits of generated Java classes as @Deprecated so Java will warn when they are being used.

I think this was solved in https://github.com/lapps/vocabulary-pages and can probably be closed here..

Agreed.


Site loading skipped

Commit https://github.com/nanoc/nanoc/commit/213ba4f88948ddd5de58546862cb939741f67e2e caused a small bug in 4.8.3 that results in the "Loading site..." step being skipped. The "Compiling site..." step now does the loading instead.
Steps to reproduce

in default.rb put puts "I'm loading"
nanoc compile

Expected behavior
(in 4.8.2)
Loading site… I'm loading done
Compiling site…
Actual behavior
(in 4.8.3)
Loading site… done
Compiling site…
I'm loading
Details
The line site.nil? that was removed in the commit apparently implicitly triggered the loading, because restoring it fixes the bug. It would probably be a good idea to make that more explicit in the code.

Good catch—I’ve started work on a fix in #1212.

The overlap between #load_site and #site has always bothered me. Looks like I finally got bit by it.
I’ll leave this issue open until I have a proper refactoring that makes this code less brittle, and makes the tests cover this case in a nice way.

PR #1213 improves the situation by not making #load_site bypassable.


ONEPLUS 3 Phone  no check

ONEPLUS 3 phone  no root，but checked is rooted

You should provide more information about this, such as screenshot of the result

This is likely due to them leaving a busybox binary (or similar) in the production build of their Oxygen rom, as they did with the OnePlus 2.

I am using this library to detect root in my app, and it works great except this scenario. It falsely detects that OnePLus 3 has root, while it doesn't have root. I can understand the issue you have mentioned that they have left busybox binary in the rom, but is there a workaround for this? This is pretty important for my app to detect root with as much accuracy as possible?

I suggest you create your own method similar to the isRooted method in the base of the library. But comment out / remove the call to check for the busybox binary.
Something like this should work:
`    public boolean isRooted() {
RootBeer rootBeer = new RootBeer(Context context);
boolean rootManagement = rootBeer.detectRootManagementApps();
boolean potentiallyDangerousApps = rootBeer.detectPotentiallyDangerousApps();
boolean suBinary = rootBeer.checkForBinary("su");
boolean busyboxBinary = false; // rootBeer.checkForBinary("busybox");
boolean dangerousProps = rootBeer.checkForDangerousProps();
boolean rwSystem = rootBeer.checkForRWPaths();
boolean testKeys = rootBeer.detectTestKeys();
boolean testSuExists = rootBeer.checkSuExists();
boolean testRootNative = rootBeer.checkForRootNative();
    return rootManagement || potentiallyDangerousApps || suBinary
            || busyboxBinary || dangerousProps || rwSystem || testKeys || testSuExists || testRootNative;
}`

Thanks for the suggestion. Will do that.


Rolling restart can leave ipam hung

If you have peers A, B, C running, then you kill A, start a new A', kill B, start a new B', etc., then you will end up with a ring owned by the old A, B, C and none of the running peers have any space.  If they try to ask for any space they will only try to contact the now-gone peers.
(To trigger this symptom requires that the new peers have unique PeerName, i.e. the weave bridge has also been recreated)
This can be worked around by calling weave rmpeer on the new peers or (somewhat less reliably) by calling weave reset when shutting down each peer.  Or by shutting down all the old ones before starting any new ones.
The weave logs are not very helpful; just a series of messages like:
weave 2015/06/11 12:20:12.412849 [gossip IPallocation]: unknown relay destination: 02:5e:a2:16:13:16

This will be resolved by #678. @bboreham did you have some other, separate solution in mind? Or some stop-gap, such as making it more detectable for users what is happening and what they should do about it?

Mostly wanted to document the problem and current mitigations.
Post-#1010 there is a message to tell you there are no peers available to talk to, but I think it's -debug level.

This got fixed in #1624. except for the case where the hosts are restarted w/o rmpeer, i.e. w/o invoking weave reset. We should document the need to invoke weave reset on a rolling restart, or indeed any controlled node shutdown.

We should document the need to invoke weave reset on a rolling restart, or indeed any controlled node shutdown.

That is no longer true, post #1866. -> fixed.


Allow fine tuning for volume by default

Before opening the issue, have you...?

[X] Searched for existing issues

Is your feature request related to a problem? Please describe
My external display has too large steps between volume settings. Using +/- results in too big of a jump in volume. I am forced to use Option+Shift+Volume key to adjust my volume on this external screen.
Describe the solution you'd like
I'd like to be able to set this screen to increase/decrease by smallest possible increments by default, without having to press Option+Shift.
Thanks!
Describe alternatives you've considered
Using the Option+Shift+volume -- works, but is not as elegant and seamless.
Anything else?
No response

This option is already in the app.


change default db admin password

Sorry the last pr wasn't tested, i make some fixes in this one

is this a good idea to add change password functionality to tests?

Testing specific configurations can be difficult, but if you want to create another PR in the future for it, I would approve.


Run v2 - NMS: No tests selected by default on fresh install

I did a fresh install of the NMS app. After loading the app:

I tapped the 'Run' button and all tests were deselected by default (I think they should be selected, I am pretty sure that is what our probe app does)
Also tests were not selected on the test overview screen

Expected result

I had expected everything would be selected by default

This looks fixed now


Maven Repo down?

Hey, I'm trying to add your great library to my maven project but it seems that the fanciful artifact is missing?
    <repository>
        <id>fanciful-mvn-repo</id>
        <url>http://repo.franga2000.com/artifactory/public</url>
    </repository>
    <dependency>
        <groupId>mkremins</groupId>
        <artifactId>fanciful</artifactId>
        <version>0.3.1</version>
    </dependency>

Not found: http://repo.franga2000.com/artifactory/public

Just ran into this as well

Fanciful is licensed under MIT so either way, it's always possible to simply include the project's source manually.

Check these two pull requests for alternative repositories @Lolmewn
https://github.com/mkremins/fanciful/pull/65
https://github.com/mkremins/fanciful/pull/66


ADD INITCAP support for scalar strings.

Summary of the changes / Why this improves CrateDB
Checklist

[ ] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[ ] Documentation has been updated if necessary
[x] CLA is signed

Can one of the admins verify this patch?

ok to test

@last-ent Thanks a lot for this contribution! Looks great in general, just some comments regarding performance and documentation:

I think the function could be optimized by operating directly on the underlying char array of the string. This would avoid any copy of chars through replacing the chars directly on that array.
This new function should be documented and mentioned at the CHANGES file.

Hey @seut ,
I have made the changes you asked. Hope it's all good now.
Cheers!

Benchmark results comparing operating-on-token vs. operate-on-complete-string:
Benchmark                               Mode  Cnt   Score   Error  Units
InitCapBenchmark.testCapitalize         avgt  100   2.533 ± 0.024  ms/op
InitCapBenchmark.testCapitalizeByToken  avgt  100  11.733 ± 0.146  ms/op

Benchmark source: https://gist.github.com/seut/cac2eab1c68eda387d8c399f211aa707

@last-ent As discussed we took over this PR and merged it just now. Thanks again for your contribution!


Cannot auto refresh upon changes

Hi ,
I followed the tutorial via Angular2 5 mins quickstart.
When i run using the npm start, it is able to run in the browser but it cannot auto refresh the browser whenever it has any changes. It only detects changes but the browser wont auto refresh.
Is there any additional setting that i should include for the browser-sync?
Please advise.

Having the same issue.  Running node 5.9.0, npm 3.7.3.  Tried clearing cache.

Related: https://github.com/angular/angular/issues/7652
A workaround is to use an earlier version of the quickstart until this is resolved:
$ git clone  https://github.com/angular/quickstart  my-proj
$ cd my-proj
$ git checkout tags/2.0.0-beta.9

same err on ubuntu 14.04 with node 4.4. My docker image for issue:
docker pull sergiator/angular2-quickstart-lite-server-issue
docker run -it -p 3000:3000 -p 3001:3001 --name lite-issue angular2-quickstart-lite-server-issue cd quickstart && npm start
Then run from another terminal:
sudo docker exec -i -t bash ./changer.sh

https://github.com/angular/angular/issues/7705#issuecomment-200019429

This appears to be fixed in the latest 2.0.0.beta.12 release of the Angular2 Quickstart. Closing.


Microsoft Store semver style

A recent fork by @Warhammer4000 showed this as a need;

We are adjusting the code to have semver like "major.minor.patch.0" the last input is for microsoft store it doesn't need to be changed and can always stay at 0.

It could be good to put in an argument/flag to format the semver output of this GitHub Action in additional styles, starting with that Microsoft Store style.

Implemented.


New aka.ms link

Aka.ms link name
mcra
Category (Optional. Select None to auto-select)
None

Thank you for submitting aka.ms/mcra. Your link already exists at akaSearch.net. 🙏✅


UX for setting up your bitcoin address should be n00b friendly

This is a big leap for users. The level of personal responsibility for key management is different than they may be accustomed to.

[ ] In the first message to setup your account it should tell you how to do this.
[ ] when selecting setup bitcoin address it should also give instructions

Is Coinbase suitable?

Also:

[ ] when you join the slack instance (different welcome message) it should give these instructions.

Repro: type welcome me WxmhxTuxKfjnVQ3mLgGZaG2KPn


Hg/cql as map

Wanted to see how bad generic solution to parse cql as map would be in comparison to strongly typed functions.
Here are the results:
go test ./cqlasmapbenchmark_test.go -bench=. -benchmem -benchtime=5s
goos: darwin
goarch: amd64
cpu: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
BenchmarkGenericMapInt32Int32-8   	  103459	     60339 ns/op	   36097 B/op	    1498 allocs/op
BenchmarkMapInt32Int32-8          	  142498	     41311 ns/op	   30137 B/op	       8 allocs/op
PASS

Please let me know if you guys see some easy way to optimise it.

@Kulezi I've come up with some idea. It might be helpful with #176 please take a look.

After correcting your functions to use correct map serialization i compared them to my implementation to also see, if using buffer doesn't impact performance in this simple case.

 Code
func (c CqlValue) AsInt32Map() (map[int32]int32, error) {
	if c.Type.ID != MapID {
		return nil, fmt.Errorf("%v is not a map", c)
	}
	if c.Type.Map.Key.ID != IntID && c.Type.Map.Value.ID != IntID {
		return nil, fmt.Errorf("%v is not a map[int32]int32", c)
	}

	raw := c.Value
	if len(raw) < 4 {
		return nil, fmt.Errorf("not enough bytes")
	}

	n := int(binary.BigEndian.Uint32(raw))
	raw = raw[4:]
	if len(raw) != 16*n {
		return nil, fmt.Errorf("not enough bytes")
	}

	res := make(map[int32]int32, n)
	for i := 0; i < n; i++ {
		key := int32(binary.BigEndian.Uint32(raw[4:8]))
		value := int32(binary.BigEndian.Uint32(raw[12:16]))
		res[key] = value

		raw = raw[16:]
	}
	return res, nil
}

func BenchmarkMapInt32Int32PP(b *testing.B) {
	c := mapint32int32AsCql(n)

	b.ResetTimer()
	for i := 0; i < b.N; i++ {
		m, err := c.AsInt32Map()
		if err != nil {
			b.Fatal(err)
		}

		if int32(len(m)) != n {
			b.Fatalf("invalid length %v", len(m))
		}
	}
}

Results on my machine:
goos: linux
goarch: amd64
cpu: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
BenchmarkGenericMapInt32Int32-8            65420             93640 ns/op           44289 B/op       1498 allocs/op
BenchmarkMapInt32Int32-8                   85294             70556 ns/op           38329 B/op          8 allocs/op
BenchmarkMapInt32Int32PP-8                183400             37013 ns/op           21945 B/op          7 allocs/op
PASS

I think that without getting rid of interface{} we won't see better performance and I don't see a workaround that can do this.
So i guess I'll stick with my current approach for #176, and leave thinking about a general solution for when we will need it.

No interface{} please.

It was just an experiment, as Paweł said let's stick with naive approach for now.
Generic code had shown that the ghaction and linter settings has to be adjusted, which I have done in this pr. Do we want to merge these commits? Eventually I can create separate pr with linter changes.
@mmatczuk

Thanks! I was just looking to fix the same thing today!


Remove deprecation as not found in master/sample-helm-config.yaml

Deprecation not found in sample-helm-config.yaml now
https://raw.githubusercontent.com/Azure/application-gateway-kubernetes-ingress/master/docs/examples/sample-helm-config.yaml

@thomast1906 : Thanks for your contribution! The author(s) have been notified to review your proposed change. @caya

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@greg-lindsay - Can you review this old PR and determine whether it needs to be closed or merged?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
@MicrosoftDocs/public-repo-pr-review-team

@ShannonLeavitt due to the age of the PR there are conflicts. I will address it in another PR and we can close this one. #please-close


[5.5] Fix migration pluralization in make:model command for special cases

Fix migration pluralization in make:model command for special cases like a CamelCased 'MetaData' model.
At the moment php artisan make:model MetaData --migration will generate a migration for 'meta_datas' table whereas Eloquent looks for a 'meta_data' table.
This fix enables you to name your model 'MetaData' instead of 'Metadata' and still have a correctly pluralized table migration for 'meta_data' generated.

This wouldn't always be preferable I don't think?

@taylorotwell Don't you think some people might call their model MetaData instead of Metadata? These guys will get a meta_datas table and Eloquent expecting meta_data when scaffolding ...

@taylorotwell The thing is: Eloquent uses Str::plural->Str::snake whereas Makemodel createMigration() uses the reverse Str::snake->Str::plural. This should at least be consistent


Fixed condition in Custom DataSource Sandcastle example

The condition was reversed. (The function wasn't called anyhow, and it's not possible to update the height after the entities have been created, but someone might call it before loading the data, so this might be relevant...)

Thank you so much for the pull request @javagl! I noticed this is your first pull request and I wanted to say welcome to the Cesium community!
The Pull Request Guidelines is a handy reference for making sure your PR gets accepted quickly, so make sure to skim that.

:x: Missing CONTRIBUTORS.md entry.

Please add yourself to the contributors file!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Thanks again for your contribution @javagl!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks for the PR @javagl!  Sorry we missed your PR when you first opened it.  I went ahead and committed this change this change (9fb39ba7e576992447a4219d77d6d1ae65acf21d)  so it will be fixed in the next release.


RSA padding oracle issue

I've discovered a bug that can turn out to be a security vulnerability for Parsec clients that use Parsec in a very specific way.
TL;DR: If any Parsec client uses the service for TLS 1.2 pre-master secret decryption with RSA PKCS#1 v1.5, they're vulnerable to Bleichenbacher's padding oracle attack.
The bug
The Parsec service, following the lead of the PSA Crypto, supports two algorithms for asymmetric encryption/decryption: RSA OAEP, and RSA PKCS#1 v1.5. While both algorithms deal with padding, the current issue only applies to RSA PKCS#1 v1.5, so this issue touches on the use of that one only.
Whenever we complete an psa_asymmetric_decrypt operation, we perform a conversion from the provider-specific error code to the Parsec-specific error code (i.e., the code that will be sent to the Parsec client). Given that these error codes are not exactly "standardised" across the providers, we decided (on first implementation) to properly map only the codes that seem most relevant and that have an equivalent in the PSA Crypto API, and for the rest to return a generic error. The bug concerns these mappings (or lack thereof) - we do not properly map the error codes signifying an invalid padding to PsaErrorInvalidPadding for the TPM and PKCS11 providers. This means that Parsec clients would instead get a generic error code instead when a padding is found to be invalid.
The security issue

Ok, so why is an invalid padding important in the case of RSA PKCS#1 v1.5 encryption?

RSA PKCS#1 v1.5 encryption is vulnerable to a type of attack that was discovered by Bleichenbacher back in '98 (see a summary here). The attacker leverages knowledge of when a ciphertext they sent produced an invalid padding when decrypted (i.e., a padding oracle) to break the system and recover the session key.

Well then it's good that we don't reveal information about when the padding is incorrect, right?

The padding oracle problem is relevant in the context of TLS - TLS 1.2 allows the client to unilaterally produce a Pre-Master Secret (PMS), encrypt it with the server's public key, and continue to use that PMS to secure the channel post-handshake. Thus, if PKCS#1 v1.5 is used, the server must take some precautions to never reveal that the PMS decryption resulted in an invalid pad. Instead, the server should just choose a random value R as a placeholder and pretend that nothing bad happened. (This will result in an error later on in the handshake when the PMS is actually supposed to be used.) The problem with our bug is: the server cannot perform this mitigation if it doesn't know the error was caused by an invalid padding. Generic errors in our backends are most likely very infrequent, so the confusion between "padding error" and "generic error" can easily be used as a padding oracle.
The fix
All we need to do is to make sure we always report back when a padding error has just happened. We should also test for this.

This issue puts Parsec in a tricky situation, particularly with regards to new providers in the future.
RSA decryption providers and implementations (such as the Parsec service) have to report back some error code when a decryption fails. The error could either be "benign" (something from which an attacker cannot learn anything about the key or plaintext), or "malign" (from which they could learn). If the returned error code is always the same, generic over all errors, then the user/client has no choice but to assume the worst and perform whatever mitigation are expected for the "malign" case. If the returned error code can distinguish between the two types of errors, then clients can go ahead and perform different steps based on that (for example, implementing the mitigations only when a "malign" error occurs). Parsec is in the latter category - we send different response codes for different problems.
Now, the problem is that Parsec may not always be able to properly satisfy that contract. If a backend does not differentiate between the error types, then we (1) send out a generic error, or (2) send out a "malign" error code. For (1), the client could end up in a pickle, not performing the required mitigations. For (2), our reported error code will technically be incorrect, probably a lot of the time. (1) is obviously worse, but (2) isn't that good either.
And then there are things like PKCS11, for which different implementations can do different things. SoftHSMv2, for example, always replies with GENERIC_ERROR when decryption fails (option (1) from above), even though a specific error code for "malign" errors exists.
It's a mess.


custom moons don't load with LethalMin installed

other than the host being the only one being able to control Pikmin, the mod works well! Until custom moons...I tried Aquatis and the moon would not load and was stuck on "Waiting for players". Can try with other moons but thought would post here because this mod is super impressive and would love to see it being able to be used fully! Great job

Usually, glitches like this occur due to an error, could you show me what the console logs when you attempt to load a custom moon?

Fixed it


License

Hello,
Thanks for developing such a great library. My colleagues and I have been using MonologFX in a Java7 tool and we'd like to release the tool under GPLv3. We are wondering under what license MonologFX is provided? We'd like to make sure the license of MonologFX is compatible with GPLv3 (e.g. a GPLv3 license or Apache 2.0 License).
Thank you!
Regards,
Julian

Hi Julian,
Thanks for the kind words! I didn't realize I hadn't put a license in the header - mea culpa. My intention has always been to provide the least restrictive and most practical license for the MonologFX code, and my understanding is that the MIT license (even more than the Apache license) satisfies that. I'll update the headers soon, but bottom line, a simple acknowledgement of my original copyright is truly all I ask. :)
Glad you like the library!
All the best,
Mark

Hi Mark,
Thanks so much for your prompt reply! The MIT license works perfect and it is compatible with the GNU GPL license we are going to use. We will definitely acknowledge your copyright in the license statement. Thanks again for your help!
Best regards,
Julian

Hi Julian,
You're very welcome, best of luck to you and your team!
All the best,
Mark
On Thu, Jun 4, 2015 at 9:48 PM, julianchin<EMAIL_ADDRESS>wrote:

Hi Mark,
Thanks so much for your prompt reply! The MIT license works perfect and it
is compatible with the GNU GPL license we are going to use. We will
definitely acknowledge your copyright in the license statement. Thanks
again for your help!
Best regards,
Julian
—
Reply to this email directly or view it on GitHub
https://github.com/hecklerm/MonologFX/issues/3#issuecomment-109144082.


feat(shield): add validation rules for org/project filters

Merging with breaking changes as they are unused fields.


[python] update numpy version

The numpy version that was added in #15178 is too old, and is not compatable with newer version of Python, e.g, 3.10. Since we upgraded CI to use Ubunut 20.04, which ships with Python 3.8.5, numpy version 1.22.0 should be compatable with both the officially supported Python version, and more modern versions of Python, e.g., 3.10.
Signed-off-by: Timothy Trippel<EMAIL_ADDRESS>

looks like we may need to upgrade private CI VMs to 20.04 as well, if this is possible? @GregAC @mundaym @jprendes

(assuming we can resolve the CI issues)

I tried with numpy version 1.22.0 and confirm that it works locally with Python 3.10.7 on my Google provisioned machine.

Confirmed with @jprendes, he is going to be upgrading the remaining CI machines to Ubuntu 20.04, and then this should pass CI.

Thanks @timothytrippel and @jprendes !

@vrozic and I discussed to just again drop the numpy dependency to unblock this. Because at the moment, the topgen integration of strong random (which requires #15178) has been postponed. Vladimir, can you please comment on this and do a PR as discussed?

Indeed, I've added numpy to the requirements to enable strong_random integration.
In the meantime we've decided to move this integration to M3, so numpy is not needed at the moment.
I will quickly make the PR to remove it from the python-requirements.txt

That would be great, thanks @vrozic !

I've temporarily removed numpy requirement in #15875
It will be needed again once we start working on integrating strong_random class, but that can wait until all CI machines are upgraded.

SG, thanks @vrozic and @vogelpi ! I will close this PR then.


Slow "> Building page:"

In dev mode, Next takes 26+ seconds to build a page for me.
 DONE  Compiled successfully in 26253ms
This has become a major pain during development, each time I change code.
I presume this is because I have lots of npm packages (48), or they are large/complex.
Do others experience this?
Can anything be done to speed this up, besides removing packages?

Use the webpack analyzer and see what are the packages in your app: https://github.com/zeit/next.js/tree/v3-beta/examples/with-webpack-bundle-analyzer
You may be using some server side NPM modules or some unwanted modules.
Try to get rid of them.

@arunoda Thanks.
Any idea if incremental webpack compilation is on the horizon?

@tashburn we already do that.
We only compile only the page you are viewing.
BTW: Double check whether you are using the latest version of Next.js

@tashburn I have the same problem.  I just started the troubleshooting process today.

If anyone of you can send me the repo, I can have a look at this.

@brentmclark Super, thanks!

hey @arunoda wanted to send you a (trimmed down) repo demonstrating what our company (@brentmclark and myself) are experiancing: repo
The part I want to point out is: when running (yarn run dev:start) you will land on a page that has a link to a second page.  That is our optimized link.
However, on the second page, if you click on either the root (which is an already built page) or the "third page" which is an unbuilt page, both take event a few seconds to build.
Now those are extremely light pages, our real app has over 600kb of styles, and a ton more components ect for each page, moving the build page time up to 5-10 seconds.  However the fact that these trimmed down pages still take  few seconds to load is the issue to me.
Any thoughts?

@tashburn, FWIW @chaffeqa discovered a config setting that we are trying out coupled with a healthy dose of prefetching.  24 hours may be the wrong length of time; we are fine tuning as we go.
Toss this into a next.config.js (or modify your existing one).  onDemandEntries is  sibling to the webpack property.
module.exports = {
  onDemandEntries: {
    // on dev, since our pages are so expensive, lets keep them for 24 hours
    maxInactiveAge: 1000 * 60 * 60 * 24,
  },
}

Increasing the maxInactiveAge really only addresses the symptom, not the root problem.  however, it had a sizable impact on our developer experience.

Also, we hadn't run a yarn install in a while.  When I ran one, I found that several of our dependencies had minor and/or patch updates.  After running rm -rf ./node_modules && rm yarn.lock && yarn install my compile times dropped by about 50%.
These things are purely anecdotal, but if they can bring you similar results that would be great!

@chaffeqa The app build time seems pretty standard to me. See:

I check the bundle and seems like you can get rid of some of the modules which are marked in red. (I assume they are server only modules)

Anyway, try to load those modules as on-demand modules with dynamic imports.

As a long term solution we are looking to use the autodll plugin (https://github.com/zeit/next.js/pull/2433) or some other caching machanism to make the dev re-build time smaller.

BTW: Apollo client seems to pretty big too.

It's part of our very near-term roadmap to dramatically speed up compilation performance, both for dev and prod. A big part of that is doing less work.

(i.e.: webpack tends to redo the whole project from scratch every time you start it up. There's a lot of time to save there)

@brentmclark Thanks for the suggestions. The onDemandEntries setting will just prevent the unmounting of pages within 24h, yes? If so, that will definitely help some.
I tried updating to the very latest version of Next, and i reinstalled all my modules per your suggestion (thanks). My dev build times have not really changed -- startup is still 6-9s (which happens whenever I change server code), and one of my key pages takes 9-29s. Not sure why there's so much variability in the time taken.
@arunoda I used the Webpack Bundle Analyzer and was able to remove maybe 10% of my modules. A modest improvement.
@rauchg said It's part of our very near-term roadmap to dramatically speed up compilation performance, both for dev and prod. Love it! That will make a huge impact.

My dev build times have not really changed -- startup is still 6-9s (which happens whenever I change server code), and one of my key pages takes 9-29s.

I assume what's happening here is webpack restarts from the scratch.

Thanks @arunoda for looking!  So that repo was an copy of our actual project, however I removed all the actual components (pages) and instead made those x3 "mock routes" (I did that to not disclose business data).  I left all the dependencies in though that we used, as well as imported them, just to help demonstrate the performance with those dependencies.
Unfortunately most of those dependencies are required in the common chunk since they are consumed by redux, which is required on every page obviously.
So you are correct on the compilation times being "normal", however the main issue I'm referring to with that "sample" app is that: try starting at http://localhost:8000, then click Route Two, then on that click Root.  You will see a 404 page for 1 second, then the page loads.  No rebuild.
> Building page: /route-one
 DONE  Compiled successfully in 4414ms                                                                                04:48:05
GET / 200 5202.810 ms - 3329
GET / 200 9.402 ms - 3328
 WAIT  Compiling...                                                                                04:48:06
> Building page: /route-two
 DONE  Compiled successfully in 1820ms                                                                                04:48:08
GET / 200 137.186 ms - 3328
Client pings, but there's no entry for page: /
GET / 200 9.760 ms - 3329
GET / 200 10.049 ms - 3328
Client pings, but there's no entry for page: /
GET / 200 6.781 ms - 3329
GET / 200 10.076 ms - 3328

I think thats a root route issue (route matching?).
The second being: from there, go back to Route Two and click Route Three (which has not been built).  That hangs after clicking for ~3 seconds, then renders the page.  This is the normal slowness we are all referring to, fixed probably by DLL significantly.
I saw the DLL pull request actually earlier this week and was pumped for that, that's probably the dev experience win.  I did want to reach out and mention that my experience with the DLL plugin is that it's got tough edge cases to deal with (much like hot reloader).  So I'd advise to do similar to what react-boilerplate did and make it opt-out-able.  Mainly for you're own github issue sanity 😉
The last thing I'd like to mention in ideas is: potentially making next-routes a first class citizen of next.js.  I say this because we were able to use that plus the preload and dev-prebuild optimizations to make a way more performant and standard router (@tashburn you may want to look into this for your dev issue), not to mention the redirectUrl option that was a huge user experience win, and we used it in our <Link /> component).
PS feel free to use that repo for any ideas/performance testing

@tashburn yep, the onDemandEntries change will simply prevent page unmounting for 24 hours.

Our two cents - now that we're fully migrated over to next, we're seeing issues similar to @chaffeqa - particularly since every page requires most of our JS because of our mobx stores (like what is described above with redux).
In addition, we get the memory fault described in #282 at least a few times a day (much more for team members with less powerful computers).
We moved from base webpack + dll plugin, which did not have any of these issues. There was a longer startup cost (60s), but subsequent pages did not have to rebuild, and we did not run into memory leaks. This is a MUCH nicer dev experience imho, since we only really need to do a cold start once or twice a day, but we're constantly navigating pages.
Question 1: is there a way to compile all the pages on server start (to disable the on demand page fetching)?
Question 2: If there is anything that we can try to help this situation and speed up our development? DDL plugin sounds promising (and helped us before) - particularly since we load heavy dependencies like https://github.com/codemirror/CodeMirror, https://github.com/jpuri/react-draft-wysiwyg, and https://github.com/Semantic-Org/Semantic-UI-React.
Above complaints aside, thanks for all the hard work that's been put into next - it's a fantastic library :).

Any progress towards this?
Just started with next, myself, and noticed this same pattern.
Initial load is long (along with any loads to subsequent routes), but afterwards navigating to any route that has already loaded previously is pretty quick.
If you idle on the site for awhile, the pattern repeats itself.

@tashburn @chaffeqa @brentmclark I think I've narrowed this down to the postcss-import and postcss-easy-import being the bottleneck.
Can you try removing that and tell me if it's faster?

Maybe, its tough for me to tell if its much faster, but it may be!

I'm not using postcss

@tashburn @chaffeqa that was a red herring for me. At this point, it's almost unusable.

We're going to integrate webpack dll in Next v5

I was suffering long full page refreshes. Turned out to be an issue with OSX and IPv6 and resolving addresses in the hosts file.
The issue was around using .local as an extension on my ... local ... machine. The DNS resolver would time out after 20+ seconds. Something to do with .local being reserved by the OS.
This hit me recently as my local Next.js site is pulling from a locally hosted API.
This is the first part of my hosts file. Adding entries to the ::1 line removed the long wait.
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
<IP_ADDRESS> localhost
<IP_ADDRESS> broadcasthost
::1 localhost example.local
fe80::1%lo0 localhost

<IP_ADDRESS> example.local


Thermal Expansion Crescent Hammer

After update 680/681 Thermal Expansion Crescent Hammers have a issue with permissions inside the owners claim.
GIF of the problem: https://gyazo.com/e21adfbdae9e37a611ee7db1faf688e9
GPDebug: https://griefprevention.github.io/debug/?SxXxsb9ifZ
SF: 3616/3614
GP: 681
ThermalExpansion/COFHCORE:  CoFHCore-1.12.2-<IP_ADDRESS>-universal/ThermalExpansion-1.12.2-<IP_ADDRESS>-universal

https://github.com/CoFH/CoFHCore/blob/1.12/src/main/java/cofh/core/item/tool/ItemHammerCore.java

Unable to reproduce on clean server.

I can reproduce, I was able to take players machines with a crescent hammer exactly like in the OP.
Only difference in my setup, is SF 3616

Ok the problem actually seems to be with interact-block-secondary being TRUE. It is FALSE by default, but I had changed it TRUE for us.
Even if item-use or interact-item-secondary are FALSE it allows the wrench to work anyway.
I also noticed if item-spawn is TRUE, you can duplicate machines and ducts when interact-block-secondary is FALSE.

I did what @kencinder suggested, but putting item-spawn to FALSE caused other mod mechanics to break, mainly what I've been able to find was Fluix Cystal production and machines that "drop" the end result on the ground. Such as the Metal Former from Immersive Engineering

Still unable to reproduce on clean server with all interact flags set to true. Reproduce this on a CLEAN server and provide exact steps.

It's not possible to reproduce this on a test server by yourself using claimflagdebug, the claim has to belong to another user.
I tried on a clean test server and wasn't able to reproduce anything either by using claimflagdebug
All the following done in a claim owned by another user, using either DEFAULT or CLAIM flags.

Set interact-block-secondary TRUE, interact-item-secondary FALSE and item-spawn FALSE
Crouch+Right-Click with a crescent hammer and you can remove the machines+itemducts AND they disappear...gone without a trace.

Set interact-block-secondary FALSE, interact-item-secondary TRUE and item-spawn TRUE.
Crouch+Right-Click with a crescent hammer and you can duplicate machines+ducts.

Set interact-block-secondary TRUE, interact-item-secondary FALSE and item-spawn TRUE.
Crouch+Right-Click with a crescent hammer and you can remove the machines+itemducts. They however do not duplicate or disappear.

One would expect interact-item-secondary FALSE to disallow the wrench itself being used on anything, but it's not being stopped and resulting in the above behaviours.
SF 3616
GP 683
LP 4.3.108


Build Error for v4 and .NET 6 in Isolation

We recently converted a function app from Core 3.1 to .NET 5 (v3), and now attempting to further convert to .NET 6 (v4).
I'm getting the following build error in Microsoft.Azure.Functions.Worker.Sdk.targets:

Invalid combination of TargetFramework and AzureFunctionsVersion is set.

Our project settings are correctly set:
<PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <AzureFunctionsVersion>v4</AzureFunctionsVersion>
    <OutputType>Exe</OutputType>
    <Configurations>Debug;Release;dev_ase</Configurations>
</PropertyGroup>

which appears to get thrown if the _ToolingSuffixis blank, but following the logic for _ToolingSuffix in the PropertyGroup node, I don't see why it is.

What version of Microsoft.Azure.Functions.Worker.Sdk package are you using?

@kshyju I'm using 1.3.0.

Could you share your .csproj file? Specifically the package references
section.
On Tue, Feb 8, 2022 at 4:58 PM Ryan Downs @.***> wrote:

@kshyju https://github.com/kshyju I'm using 1.3.0.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-functions-dotnet-worker/issues/802#issuecomment-1033217824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABDIVMRHQ4AUSQCYV3WOBLU2G327ANCNFSM5N3445AA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@kshyju
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <AzureFunctionsVersion>v4</AzureFunctionsVersion>
    <OutputType>Exe</OutputType>
    <Configurations>Debug;Release;dev_ase</Configurations>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Azure.Messaging.ServiceBus" Version="7.1.2" />
    <PackageReference Include="Microsoft.AspNetCore.WebUtilities" Version="2.2.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.6.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.0.13" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.ServiceBus" Version="4.2.1" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Timer" Version="4.1.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.3.0" />
    <PackageReference Include="Microsoft.Azure.ServiceBus" Version="5.2.0" />
    <PackageReference Include="Microsoft.EntityFrameworkCore" Version="3.1.15" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="3.1.15">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="3.1.15" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="3.1.15">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="5.0.2" />
    <PackageReference Include="Serilog" Version="2.10.0" />
    <PackageReference Include="System.Net.NameResolution" Version="4.3.0" />
  </ItemGroup>
  <ItemGroup>
    <None Update="host.json">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </None>
    <None Update="local.settings.json">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
      <CopyToPublishDirectory>Never</CopyToPublishDirectory>
    </None>
  </ItemGroup>
</Project>

I tried your .csproj file content as it is on a new function app and able to build without any issues (using visual studio 2022). Could you give that a shot on your side? If you still reproduce, could you share that minimal repro? (a github repo would work best). Thanks!

This issue was caused by a core tools bug which sets incorrect function version in the .csproj file (v3 instead of v4). It is fixed now and will be released shortly.