How to use with React Hooks

What are your vision of using react-easy-state with the new and fresh React Hooks?
https://reactjs.org/docs/hooks-intro.html

No idea yet. I am on a holiday with very limited internet. I will catch up with React news in a week when I get back. (I guess there is a lot of news)

Yup lot of news! This is not a question only for this library but also for other state libraries like Mobx so I think by when your are back there might be some addition research from others on how to use, I will try to research my self.
So in the mean time enjoy your vacations ;-)

So this is what I have come up with so far:
import React, { useState, useEffect } from "react";
import ReactDOM from "react-dom";
import { store, view } from "react-easy-state";
import { observe, unobserve } from "@nx-js/observer-util";

const useEasyState = store => {
  const [state, setState] = useState(store);

  const handleStateChange = () => {
    console.log(state);
    setState({ ...state });
  };

  useEffect(
    () => {
      const fn = observe(handleStateChange);
      return () => unobserve(fn);
    },
    [store]
  );

  return state;
};

const counter = store({
  num: 0,
  increment: () => {
    return counter.num++;
  }
});

const Counter = () => {
  console.log("RENDERING");
  const { increment, num } = useEasyState(counter);
  return <button onClick={increment}>{num}</button>;
};

function App() {
  return (

      <Counter />

  );
}

const rootElement = document.getElementById("root");
ReactDOM.render(<App />, rootElement);

The useEasyState does all the trick delegating the store value to the hook state it self and thats it, there might be some minor things that I am not considering but its a starting point. With this you can import the hook like this.
import { useEasyState } from 'react-easy-state'

Let me know what you think when you are back.

Here is the working example:
https://codesandbox.io/s/n49v8llw70

Hi All! I am back 🙂
Thanks for all the demos so far, I will catch up with them in the afternoon.

Thanks for the effort @cayasso and @Penspinner. Here is my feedback/thoughts:

I think migrating internally to react-hooks without an external API change has no big benefit. The current React state will continue to be supported and the current perf is pretty good.

We could simplify the API down to single function much like @cayasso did. With hooks we wouldn't even need store, just the useStore function. (Use store can wrap the passed object with a reactive store, since store wrapping is idempotent).

Something like:
import React from "react";
import ReactDOM from "react-dom";
import { useStore } from "react-easy-state";

const counter = {
  num: 0,
  inc: () => {
    return counter.num++;
  }
};

const Counter = () => {
  const { inc, num } = useStore(counter);
  return <button onClick={inc}>{num}</button>;
};

const rootElement = document.getElementById("root");
ReactDOM.render(<Counter />, rootElement);

There are two questions to consider:

How to add this? Should we keep the current 2 function API and add this new function as a different way of usage?

How to support local state?

Let me know what you think.

My 5 cents.

How to add this? Should we keep the current 2 function API and add this new function as a different way of usage?

I'm fine with view + useStore as you proposed. Personally, I don't see a value in state methods (they are not composable and spray logic into different places) but that's another question.

How to support local state?

I would say state is "local" or "global" depending on the file it's located in... and that's all.
No extra technical differences are required.

I think migrating internally to react-hooks without an external API change has no big benefit. The current React state will continue to be supported and the current perf is pretty good.

Yes. I know. Just trying to see if the implementation was correct or if it would be cool to try it out.
One thing I'm not sure about is would useStore(counter) create a global store? Would another component that useStore(counter) be re-rendered if the other component mutates counter properties?
import React from "react";
import ReactDOM from "react-dom";
import { useStore } from "react-easy-state";

const counter = {
  num: 0,
  inc: () => {
    return counter.num++;
  }
};

const Counter1 = () => {
  const { inc, num } = useStore(counter);
  return <button onClick={inc}>{num}</button>;
};

const Counter2 = () => {
  const { inc, num } = useStore(counter);
  return <button onClick={inc}>{num}</button>;
};

const App = () => (
  <>
    <Counter1 />
    <Counter2 />
  </>
);

const rootElement = document.getElementById("root");
ReactDOM.render(<App />, rootElement);

Welcome back @solkimicreb hope you enjoyed your vacations!

I pretty much agree with all that @ivan-kleshnin mentioned. view + useStore and that local vs global doesn't really matter in this case.

@solkimicreb in your example I don't think it is possible for useStore to wrap the object with a reactive store, because (and correct me if I am wrong) the object need a reference to the reactive object for example:

const counter = {
  num: 0,
  inc: () => {

    // won't work, it need a reference to "counterStore"
    return counter.num++;

    // will work because its a reference to reactive counterStore
    return counterStore.numm++;
  }
}

const counterStore = store(counter)

@NaNdreas the update is not released yet. Current easy-state will indeed cause that error.

I'm really just worried about the API changing too much (a lot of refactoring)

To my understanding, everything is 100% backward compatible. It's only if you move to hooks in your code base – you'll need to apply this new API.

I did some research and everything I wrote so far was more or less incorrect, sorry about that. Now I have a tiny working demo to back up the ideas. Big thanks @Penspinner for your demo! My one is a slightly modified version of yours.
I hoped to shrink the current API to a single hook, but it turned out that we have to keep both the store (as @cayasso pointed out) and the view function. The good news is that we can continue to support all use cases with the current API at least.
This is the proposed API for the new use cases.

The new version will work with pre-react-16.7 class and function components. (No breaking changes)
It will work together with hooks and support local state in  React 16.7+ function components.

import React from 'react';
import ReactDOM from 'react-dom';
import { view, store } from 'react-easy-state';

// this is a global store which is shared between component instances
const globalStore = store({ show: true })

const toggleShow = () => (globalStore.show = !globalStore.show)

// using store inside a function component creates a local store that is not shared between component instances
const Counter = view(() => {
  const localStore = store({ num: 12 })
  const inc = () => localStore.num++

  return <button onClick={inc}>{localStore.num}</button>
});

const App = view(() => (

    {globalStore.show && <Counter />}
    <button onClick={toggleShow}>Toggle Counter</button>

))

ReactDOM.render(<App />, document.getElementById('root'));

You can find the codesandbox demo with the initial implementation here.
Let me know what you think.

It looks great to me, I like the fact that we continue using the same API, there is one change only, I noticed that in easyState.js you have this line scheduler: setState,, this line like that will cause the following error when using regular react hooks in a function with view(...):
TypeError: Cannot read property '0' of undefined

You can reproduce the error here https://codesandbox.io/s/l5nkkqqp0l notice what happen when you increment.
The solution is to use scheduler: () => setState(), as in @Penspinner initial code.

@solkimicreb
Just tried your example. Looks fine except for a few things.

When pressing the Toggle Counter button, App gets logged to the console twice. Not sure why. Is it supposed to do that?
Also one thing I noticed about the store function is that the React team emphasized that hooks should be in the top level at all times to function correctly. So useMemo shouldn't be in an if statement. It seems to work fine in your example, so Idk. https://reactjs.org/docs/hooks-rules.html

I hope to have some time over the weekend to implement this.
Thanks for the feedback @Penspinner

When pressing the Toggle Counter button, "App" is logged to the console twice. Not sure why. Is it supposed to do that?

This is a bug, I will look into it.

I noticed the store function is using useMemo within an if statement. The React team emphasized that hooks should be at the top level of a React function at all times to ensure things work as expected. It seems to work fine in your example, but not sure if it would function correctly all the times. https://reactjs.org/docs/hooks-rules.html

This won't be an issue. Every hook must be called in the exact same order on every render. (This is a lower level equivalent oh the 'hook rules'). My if block is doing exactly this, it calls useMemo when store is invoked from inside a render and does not call it otherwise. Without the if block we would actually break react because of the hooks called outside from renders. I will make sure to comment the final code about this.

Hooks update is ready, you can try the beta release with npm i react-easy-state@beta. The new code and readme is on this branch. Everything is as discussed in the final comments.
Please play with it a bit if you have some time. I don't expect to add any breaking changes, so don't be afraid to try it out. Thanks everyone for the help so far!

@solkimicreb thank you for taking the time and implementing this!

This were somehow caused by withRouter:
view(withRouter(Layout)) // worked previously
->
withRouter(view(Layout)) // works now

No time to investigate, m.b. will help someone.

Which version of React Router are you using?

4.3.0 and 4.4.beta

this is (most probably) not a batching issue

Maybe. The initial reason to think "it's batching" for me was that only state.loading =  update was skipped / lost while state.models = had effect indeed.

Tried with 4.3.0 and 4.4.beta

4.4.beta is using the new context api and I hoped it would eliminate this issue. I will add some React Router interaction tests and look into this before the next release. Thanks for the info again.

Are you sure it was working with view(withRouter(Layout)) previously

Yes, absolutely. Otherwise I wouldn't notice this change. I would estimate the probability that it was "something else affecting the impression" as extremely low in this case. Still it could be some weird combination of prop names, etc that made it work when it shouldn't.

Thanks! Did anyone else run into this issue?

Coming back to my suspended hooks branch  ;) I see that problem with React-Router is bigger than I thought.
Basically, with 6.0.6, useEffect in view + functional component triggers:

Error: Hooks can only be called inside the body of a function component

while this sketch implementation works fine: https://codesandbox.io/s/oq66nmyjpz ...
I've made a repo to demonstrate the bug:
https://github.com/ivan-kleshnin/react-easy-state-bug-demo
See src/pages/Home.js files and lines:
// export default Home // works fine
export default view(Home) // causes an error

Rechecked once again, and I see no problems with<EMAIL_ADDRESS>react@next and react-router@next. All possible sequences of decorators work equally fine in my cases.


Might be a minor typo "newtosoft" vs "newtonsoft"

https://github.com/RickStrahl/wwDotnetBridge/blob/68ab0ef617f93a4e77506c406f949936cd483dc3/Distribution/wwDotnetBridge.PRG#L186

Fixed. Thanks - better late than never 😄
This usually not a problem - it's the primary assembly that is affected by the zone identifier.


Does the newest version support cv::dnn::DNN_TARGET_CUDA,or will it?

Does the newest version support cv::dnn::DNN_TARGET_CUDA,or will it

At this time, OpneCvSharp has no plans to support CUDA features.


withRelated must contain Key

Related Issues: #IssueNumber if necessary

Introduction
When trying to retrieve information using withRelated function the function must contain the foreign key in order to work.
Issue Description
For example, I noticed that if I have two tables let's say "Ranks" and "Categories", ranks.category_id must match categories.id, and when trying to retrieve ranks from each category using 'withRelated' the query function must select the 'foreign key', otherwise it will return nothing.
Steps to reproduce issue
This won't work:
 withRelated: [                     { 'ranks': (qb) => qb.column('id', 'rank_name').debug() }                 ],
This will:
 withRelated: [                     { 'ranks': (qb) => qb.column('id', 'category_id', 'rank_name').debug() }                 ],
Expected behaviour
To not repeat or even require the foreign key that the model is trying to get.
Actual behaviour
Foreign Key is required and repeated.

any update on this ?


issue edit: newline in body does not work

Describe the bug
I want to update the body of an issue with
jira issue edit issue-001 -b "Line 1  \nLine 2  \n\nanother line"

I expected that \n would be interpreted as newline but it is just added to the body as plain text .
This is how the decription looks like in the jira webui.
Line 1  \nLine 2  \n\nanother line
I also tried to use \, <br>, <br\>, \r\n, adding two spaces. Nothing worked.
Please provide following details

JiraCLI Version:(Version="1.5.1", GitCommit="0e0f82d52ef5a775d2cc662fbe38d9732b9b5c59", CommitDate="2024-01-20T10:48:06+00:00", GoVersion="go1.21.5", Compiler="gc", Platform="linux/amd64")

Are you using Jira cloud or on-premise jira server?  Version:         1001.0.0-SNAPSHOT
  Build Number:    100262
  Deployment Type: Cloud
  Default Locale:  de_DE

What operating system are you using? Also mention version.Ubuntu bookworm/sid (jammy) x86_64
Ubuntu 22.04.4 LTS

What terminal are you using? Also mention version.Tilix

To Reproduce
Steps to reproduce the behavior:
see above
Expected behavior
\n should be interpreted as newline

@htammen @SimonHarteDP You need to pass it in a way that allows the shell to expand the character.
The following should work.
jira issue edit issue-001 -b $'Line 1  \nLine 2  \n\nanother line'

Words of the form $'string' are treated specially. The word expands to string,  with backslash-escaped characters replaced as specified by the ANSI C standard.

Thank you very much @ankitpokhrel. It works.


add www subdomain to ytd elements

closes #65
need to test more generic filters against mobile

Notable exclusions

emoji


[DS-4228] Fix colspan values in EditItemBitstreamsForm

The table of the EditItemBitstreamsForm was extended in 3e49b04e325fca595cdde93f02143dc3d6006fa0, but the colspan values were not adjusted.
It may be relevant for the styling of the table, because some rows will not have a right border.
I can create a backport for dspace-5_x, if this is merged.
Fixes #7568

@AlexanderS pardon my ignorance. I applied the patch but I still see a seemingly mismatched table in the Edit Item → Item Bitstreams screen:

Is this what the patch attempts to fix? Thank you.

@AlexanderS or @nwoodward : Looks like more recent tests by @alanorth show this not to be working correctly.  Any ideas of what might be going on & whether this needs updating?

I'm not sure. I recall when I tested this it got rid of a superfluous column in the table. @alanorth When I look at your screenshot I can't tell how the table columns are mismatched.

@nwoodward this was awhile ago, but looking at the screenshot again it does look like some table columns are messed up. Circled here:

Ah. Those buttons are enclosed in  tags, which is why there's a line break in between them. I had to inspect this page in Developer Tools and look at the HTML to see that the colspan didn't match the number of columns before the PR.


(bug) Fix beginKeywords to ignore . matches

Related: https://github.com/highlightjs/highlight.js/issues/2429 Resolves #2428
Attempts to restore as little as possible of the previous beginKeywords magic behavior as necessary just to prevent .keyword or keyword. from matching.  This is done via an internal onBegin callback that essentially ignores the match if a . is found.
What behavior does this NOT restore?  A failed match will NOT consume any content from the input stream, ie it will not advance the cursor.
Previously:
       v Parse cursor is here after failure to match.
A.class

Now:
  v Parse cursor is here (or earlier) after failure to match.
A.class

Ex:
    contains: [
      { beginKeywords: "class" },
      // this rule will still match class if the above rules fails to (because of a `.`)
      { begin: "class", className: "found" }
    ]

Also previously the match would actually start at the . (when one was present), which would prevent any other rules from matching if there was a failed keyword match - that is no longer the case.  The match now starts with the keyword itself and then looks backwards to see if there was a preceding . or not.

What else might still be an issue...
This new behavior means that when beginKeywords fails to match keywords now has a chance to.  I think this is new behavior, and correct behavior.  No other place in the parser does a rule silently consume content for a non-match, and I don't think beginKeywords should do so either.

MultiRegex is just a re-factoring of the behavior that was there before into a class, allowing us to work with a large group of regexes as a single search unit.
ResumableMultiRegex wraps multiple MultiRegex objects to allow resuming a multi-regex search at the same cursor position, allowing for the possibility of multiple regexes matching, instead of just the first.

See comments in source for more details

I think if you understand what's going on in highlight.js you understand the gist of it.  I wish I could think of better names though.  It's weird now because the MultiRegex has not only an index now but also a "which regex" to begin searching with index (which I called startAt), since now it's resumable at the same position to later regexes in the stack can be tried.
Wrapping a bunch of MultiRegexes was just the simplest way I could think of to accomplish the goal... but if someone knows a simpler way... the external API is simple enough:

exec(string)
matchAt
index

And actually this now allows for lazy-compiling of multi regexes... so for some grammars with a ton of complex modes it might be possible that some of those regex never even have to be compiled if those modes are never actually hit - so that's a nice small win.

Tried to improve naming.

Yes, it's a bit clearer this way.


LED Blink Feature

Step 1: What do you want?

Improve code (and need help).

Step 2: Describe your environment

Arduino IDE version: 1.8.3
dw1000 Library version: latest
Arduino device: Pro Mini 3.3v
Used adapter board: Wayne Breakout Board

Step 3: Describe the problem
How do you enable RX and TX Led blinking during ranging?
Observed Results:

What happened?  This could be a description, log output, etc.
I looked at the DW1000 class and added the following code in setup. But i am missing something i guess.

Expected Results:
Blink TX and RX LED during Ranging.
Relevant Code:

void setup() {
// ...
  DW1000.enableDebounceClock();
  DW1000.setGPIOMode(MSGP2, MSGP3);
  DW1000.enableLedBlinking();
//...
}

Wrong order? See #144

Thanks. The code seems to compile without any errors but i am somehow not able to get the intended behavior. I am using Wayne breakout board; Pins 12 and 13  (GPIO 3 / TXLED, GPIO 2 / RXLED) from the DWM1000 are soldered properly to the Wayne board with 0603 smd led and 1k resistors.

Same here, I can successfully implemetrent BasicSender and verify packet sending, but the TXLED wont turn on

Then fix it and make a pull request...

Okay, I have been able to get it to work. But somehow it seems to be at random even though it is not doing any ranging.
DW1000.enableDebounceClock();
DW1000.enableLedBlinking();
// enable GPIO2/RXLED blinking
DW1000.setGPIOMode(MSGP2, LED_MODE);
// enable GPIO3/TXLED blinking
DW1000.setGPIOMode(MSGP3, LED_MODE);

Anyone else has the same issue?

The dw1000 is a network device. RX and TX shows input and output, which do not depend on any "ranging".

Thanks for clarifying @Rotzbua . Adding to that there are several configurations after looking at dw1000_user_manual_v2.05 PG 122, which can be done
DW1000.setGPIOMode(MSGP2, LED_MODE);
MSGP0:
When operating as the RXOKLED driver, the output is asserted briefly when the receiver
completes the reception of a frame with a good FCS/CRC.
MSGP1:
When operating as the driver, the output is asserted briefly when the receiver detects the
SFD sequence  in  the  RX  frame.
MSGP2:
When operating as the RXLED driver, the output is asserted when the receiver is on, and stays
on for a brief period after the receiver is turned off.
MSGP3:
When  operating  as  the TXLED driver, the output is  asserted  briefly  when  the  transmitter
completes  sending  a  frame.
MSGP4, MSGP5, MSGP6:
The pin operates as the EXTPA / EXTTXE / XTRXE output.
MSGP7, MSGP8:
The pin operates as GPIO7 and GPIO8 respectively when LED_MODE is set.
Hope this helps other.

Thanks for research 👍 , please can you copy your collected and summarized information to wiki? The wiki can be easily edited by button top right "edit". The wiki is open for everybody to write and edit.

@Rotzbua, Updated the wiki. Please check and add/correct if necessary.
https://github.com/thotro/arduino-dw1000/wiki/DW(M)1000-LED-Blink-Feature

@werty37 Thanks a lot!


Append entry

This revives #178 and fixes #279 and #280

will need a little more work, the symlinks need to be buffered/sorted and then written at the end.

Closing for now. I think the real problem is that tar is a unix format. For it to be a proper cross platform format it would have to encode with the symlink if it's a file or a directory symlink. Anything else is really just a hack.


Many updates to latest nGraph Architecture and feature docs

Fabulous updates all throughout the theme and intro and visual aides as well

Please merge what's been approved thus far.  The next round of doc updates can be in a separate PR.  Thanks


Uses a MatcherAbstracts string form in error output

Fixes #697
I don't think it's a good idea to use __toString for arbitrary objects for now as we really can't guarantee a reasonable error message if we do so. Going forward, I plan to use sebastianbergmann/comparator or possibly just it's dependencies to provide better output.

Coverage increased (+0.3%) to 73.634% when pulling d1ca5444c8252cb08e11ee53af8ffe87b40fb03d on davedevelopment:to-string into 0653a4f0c50149e7b89e9978f04c941de82c7549 on padraic:master.


Scripts for generating key pair

Steps to run the script:

Build the Hotshot repo following its readme.
Run just async_std gen_key_pair.

The input config file is in config/ValidatorConfigFile.toml.
The output validator key pair is in: config/ValidatorConfigOutput.
And an example for validator key pair easier visualization is in config/ValidatorConfigExample.


Update aks-create-clusters-cli.md

update for GA

@sethmanheim
Can you review the proposed changes?
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.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Hi @guanghuthegreat  - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

Moved to release branch in private repo. #please-close


Unmount

I integrated substance editor into the react app.
I initialize it in componentDidMount lifecycle method.
But what is the proper way to release all resources on componentWillUnmount?

Use comp.remove(). This disposes the whole tree and removes the element from parent.
Alternatively, if you only want to have the events triggered, you can call comp. triggerDispose().

thank you!


wallet-ext: qredo connect add organization field

add organization field in injected inputs
this changes the way wallet identifies that 2 connections are different (to be the same must also have the same organization)
this fixes the issue when injecting accounts with the same service and apiUrl, but different organization was replacing the existing connected wallets

closes APPS-1215

Lock files changes look unrelated but looks good generally

Yes it's unrelated, but running pnpm i on main changes the lock file as well. I will remove the lock file from this PR anyway


[Question] How to extract php-fpm Dockerfile, add new customization and use it?

Like title, I need to add ioncube into php-fpm docker but I can't find a way to do that properly, can you please help?

@hoanglan87 The builds for all images used by Warden can be found here:
https://github.com/davidalger/warden/tree/develop/images
IonCube is included in all the PHP versions except for PHP 7.3 as the guy maintaining the IUS RPMs has decided to stop packing ioncube into the RPMs: https://github.com/iusrepo/wishlist/issues/248
I have not had the time to pivot that away from using IUS to downloading the loader and installing it in similar fashion to what has been done with Source Gaurdian (this Dockerfile is the base for all FPM images used by Warden):
https://github.com/davidalger/warden/blob/develop/images/php-fpm/Dockerfile#L36-L53
So there are probably two ways to go about this:
a) You could submit a PR that downloads ioncube loaders similar to the Source Gaurdian loader is downloaded (see dockerfile above)
b) Some vendors such as Unirgy offer Source Guardian encoded versions of their extensions for recent Magento and PHP versions. If the extensions you are using are available using Source Gaurdian, you could replace the IonCube version with one encoded using SG (this of course has implications on changing deployed infrastructure if the site is already live)

hi @davidalger,
Thank you
Where should I put that Dockerfile so warden can use it? I suppose I can just add a build step to include ioncube into the Dockerfile

hi @davidalger I have created a pull request for adding ioncube for php 7.3
https://github.com/davidalger/warden/pull/109


Bug: Web3onboard not connecting to metmask in new release

Current Behavior
Web3onboard is throwing an error when connecting to metamask when the selected chain in metamask doesn't match the chains specified in the web3onboard init function. Seems like a condition is missed in the recent release of the secondary token balances feature. It's possible that appChain can be "undefined" where the chain selected in metamask is different than the chains mentioned while configuring web3onboard
Error shown:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'secondaryTokens')
Expected Behavior
Should connect to metamask despite having rpc in chains array
Steps To Reproduce

Choose a polygon chain in metamask
Mention only Ethereum chain rpc while initiating web3 onboard
It will not connect and throw an error

What package is effected by this issue?
@web3-onboard/core
Is this a build or a runtime issue?
Runtime
Package Version
2.22.1
Node Version
No response
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Anything else?
No response
Sanity Check

[X] If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.

@mbcse thanks for reporting!
There is a fix for this on @web3-onboard/core v2.19.0-alpha.1 and an official release will be out shortly.

@mbcse a fix for this is available with the latest versions of the core/react/vue packages. Thanks for raising this issue and please let us know if you have any other issues!


debug lol

What is your question?
Is there a way to tell if debug mode is on?
(Debug mode is when botplay can be changed from the pause menu.)

The only way to tell is to check said pause menu

chartingMode

Ok thanks


Add recommendations for checkbox questions with no answer

Addresses https://github.com/civiform/civiform/issues/7067

I wasn't able to get the hint syntax to work :(


fix batch_to_right

#1883
This is the PR related to the issue "[Bug]: pad_right_to in data_utils.py does not check ndim correctly".
Thanks!

@Gastron Can you take a look?

Yes this looks like a straight-forward mistake. Weird that it wasn't caught before. Thank you for fixing this.


Don't run 'make release' on PRs

Don't run make release on PRs. Takes 20-25 minutes to run (90% of total time) on drone-servers... Make-shift solution until we bring up more drone-agents...
The only thing this does is disabling build-tests on all architectures excluding amd64

LGTM

We had disabled that in the past, until some architectures failed on master. That's why we always enabled it

@bkcsoft @tboerger What time do we star to upgrade Drone to 0.7.x version?

LGTM

@tboerger right, but running make release takes a shit-ton of time 😞


Replace Zipkin specific implementation with opentracing abstraction

Even though this package is tagged with "open-tracing", the source code is full of direct Zipkin reference rather than using Opentracing abstraction.
I think adopting Opentracing specification is a strict superior approach, as you not only get Zipkin implementation for free but a couple of others in the field. For me, this is a major blocker of using this package, since we use jaeger tracer.
I am happy to submit PR if this sounds good to you.

I just realized Zipkin has been taken down from supported list from Opentracing. Interesting. Certainly makes things harder to unify. I need to rethink my proposal.


Terminal Not Working

Issue Type: Bug
So I was coding my discord bot and tried to run it in the terminal as intended; so I pressed "run active file" so it automatically put "C:Users/Wyllan/Desktop/Flamingo/bot.py" but it just went to a new new line and put "C:Users/Wyllan/Desktop/Flamingo>" with new line and a space.
I do not know how to replicate but plz help.
VS Code version: Code 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:22:06.216Z)
OS version: Windows_NT x64 6.3.9600

System Info

Item
Value

CPUs
AMD A6-6310 APU with AMD Radeon R4 Graphics     (4 x 1797)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
6.93GB (2.98GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

python
ms-
2020.7.94776

atom-keybindings
ms-
3.0.8

mcscript
Ste
0.0.3

I disabled extensions and it still didn't work :'(

Please provide a screenshot or a gif illustrating the problem (attaching images won't work via email, you need to go to github.com). See this wiki page for more general info on how to report actionable terminal issues.
/label "needs more info" integrated-terminal


Task4: Circle of contributors

Brief Information
This pull request is in the type of (more info about types):

[ ] build
[ ] ci
[ ] docs
[x] feat
[ ] fix
[ ] perf
[ ] refactor
[ ] test

Related issues (all available keywords):

keyword #xxx

Details
This feature issue is to track task which is mentioned in https://github.com/hypertrons/hypertrons-crx/issues/808
In order to present warehouse contributors in a more diverse manner, as well as their contribution size and collaborative relationships. We constructed an Active Developer Collaboration Network on the homepage to replace the original Circle of Contributors.

In addition, we have set up a toggle button where users can switch the contributor interface view to the Circle of Contributors by clicking the button.

For more information, please refer to the README_808 of fork repository and feel free to share your views in this issue.
Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA

Others

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: johnathon:x: MrH233johnathon seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Confirm if you forgot to run `yarn run prettier`.

check and update the format of files with "yarn run prettier --write"

First please sign the CLA

Also, I hope you can adjust the size of the container after you switch back to the original view, so that its size is consistent with the original github

At the same time, please adjust the style of the switch button to keep it consistent with GitHub's native style.

Thank you for your valuable suggestions. I have improved and submitted the feature functionality as requested.

Thanks for the edit! Could you give me a diagram to show me what it looks like after the warehouse is switched when the network graph data cannot be found?


Clarify whether arrays and bit registers of size 0 are allowed

What is the expected enhancement?
I suggest that it should be stated explicitly whether bit registers or statically-sized arrays of size 0 are allowed by the spec.
Since it is not currently mentioned, I believe that registers with zero bits should be supported, but qe-qasm does not currently support them: https://github.com/openqasm/qe-qasm/issues/37.
For what it's worth, a zero-sized array on the stack is disallowed in C by the standard.  However, I think there is a stronger case for allowing them in OpenQASM, for two reasons:

An unused empty array in a C can be eliminated from the code and replaced with NULL without the semantics of that code changing, AFAICT.  By contrast, removing an output array register of zero bits from an OpenQASM program would change the result; the register would no longer be included in the output.
OpenQASM code is often generated by a computer program, and the output is typically consumed by a computer program.  Running a program, with certain inputs, might sometimes result in a classical register of zero size, and it would be nice not to have to special case this both when the OpenQASM is generated and when the output is consumed.

If it is decided instead that arrays of size 0 should not be allowed, then I suggest that it be clarified that every dimension of the array must be at least 1 (e.g., array[float[32], 3, 0, 2] would contain zero elements and therefore also be disallowed).

From my opinion a zero-size register feels fine for the 2 reasons given. If are able to PR to implement the spec change it will be easier to validate.

@garrison are you working on that PR?

I would still love to do this.  I will try to finish the PR soon.


Example for using collection_item in a sample/preview

Sorry for posting this here in the issue tracker, but I haven't found a link to a discussion board or similar...
I'm setting up a "news preview" in my app using collection_item in my app and it works like a charm 🪄
BUT: I can't figure out how to show them in an admin preview using the sample block. Here's what I've got:
name: "three columns with images"

category: blog

settings:
- label: "Title"
  id: title
  type: text
  default: Headline
- label: "Overview link"
  id: overview_link
  type: link
  with_text: true
  default: { text: "Link", href: "#" }

blocks:
- name: "Item"
  type: item
  limit: 3
  settings:
  - label: "News Item"
    id: news_item
    type: collection_item
    collection_id: news_items

blocks_label: "Top 3 News Items"

sample:
  settings:
    title: Aktuelle News
    overview_link: { text: "Link", href: "#" }
  blocks:
  - type: item
    settings: ???

This is probably hard to generalize, if it works at all, but one could potentially link to a test fixture or something?

👋 @julianrubisch, the documentation is incomplete indeed and I've to update it.
In the meantime, you could use any as the id of the collection item. Something like this?
sample:
  settings:
    title: Aktuelle News
    overview_link: { text: "Link", href: "#" }
  blocks:
  - type: item
    settings:
       news_item:
           id: any


Websocket not working in prod build (node-server) with base url

Environment
Preset: node-server
Nitro: 2.9.6
Node: v18.18.0 (Stackblitz) / v20.5.1
Reproduction
The chat example from crossws.
No websocket logs are printed and the ping button doesn't work either. Removing the baseURL or switching to dev works.

Note: The error handler does a redirect because I don't know how to tell Stackblitz to open a specific path (if that is even possible)...
Describe the bug
Websocket in production build (node-server) with a baseURL other than / does not work.
Additional context
Looks like the asset handler that is in front gets picked.
https://github.com/unjs/h3/issues/719 Maybe related and this belongs to h3?
Logs
No response

I have the same issue, everything works as expected with no baseUrl or '/', but as soon as i have a baseUrl set, it will connect to any given ws url, but the handler never gets hooked.
Tested on:
nodejs 20, 22
deno 2.0.6
bun 1.1.34
I also tested nuxi-nightly.


Dev branch

Checklist

[x ] I ran npm test locally and it passed without errors.

[ x] I only edited the _data/pixels.json file.

[ x] I entered the username in the pixels.json that I'm also using to create this pull request.
[ x] I acknowledge that all my contributions will be made under the project's license.

Looks like you've got a merge conflict. Resolve this, and it should get merged in for you.
Merge conflicts occur when two or more changes have happened to the same file and Git is unable to work out which of the changes it needs to keep. In this case, it's both.
There are many ways to resolve merge conflicts, the easiest will be using the visual editor which Github provides, you can see that on this page. Github also provide instructions on some of the other ways to make these changes.

Thanks for the help @lukeberry99! Since there are some issues with the automation right now, I actually resolved the merge conflict for @DanKremer


fix(quickstarts): fix auth issue and too many redirects error

fixes https://github.com/nhost/projects/issues/51

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

Comparison is base (e9d5d0a) 86.80% compared to head (b4dccd4) 86.80%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2437   +/-   ##
=======================================
  Coverage   86.80%   86.80%
=======================================
  Files          85       85
  Lines        9328     9328
  Branches      489      489
=======================================
  Hits         8097     8097
  Misses       1231     1231

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


Adding about block for home page.

Related Issue or bug

Adding About block for home page.
Working for both Light and Dark Theme

Fixes: #289
Screenshots
light Theme

Dark Theme

@smaranjitghose @anushbhatia Review it 🔥

Design is pretty clean thou so do follow the same only change the presentation format for it

https://codepen.io/jorgesanes10/pen/QdMEXr

Icons are pretty decent but add colours to them either by adding a circular bg to the icon or by making cards for all of them and having distinct colour added to them

Sure !!

Design is pretty clean thou so do follow the same only change the presentation format for it

Check Now !!

I have change the color of icon to white & the shadow color in dark theme.

Thank you very much @anushbhatia Sir for merging.


Are Channels Implemented in the API?

I've been reading through the gdax official documentation and they mention that we need to subscribe to channels in order to get updates. I couldn't find any channel subscriptions in the code. Is the WebsocketFeed stream subscribe to a "full channel" ?
https://docs.gdax.com/#channels

almost have a working example now. Essentially you need to process messages in sequential order. Since the websocketfeed relies on TCP based comms you should get all the messages, you just need to process them in the correct order... and timeout if the one you're waiting for next doesn't arrive in a sensible time frame.

I have a working example - it will be available soon enough. Next few days or couple of weeks max I'm hoping

I've implemented the LiveOrderbook now should be available any day now with any luck

I kinda refactored your code for level2 and ticker channels. It was quick and dirty just to get my bot running. I realized that the connections through org.apache.tomcat.websocket.WsWebSocketContainer keeps disconnecting when using channels. Not sure why. so I switched the socket implementation to TooTallNate/Java-WebSocket. which is a standalone socket implementation and it worked fine.

ok - Full LiveOrderbook is available now over at my repo www.github.com/robevansuk/gdax-java. Fully tested and reconnects on timeouts if the message we're waiting for isn't received within 15 seconds.

I figure realtime is likely to offer much better algo trading! imaging monitoring the rate of trades coming in, seeing a spike and being able to place a trade instantly. Surely that's going to make/save more than a few %?


Username 666 easter egg not an issue just an idea

You can add username 666 into yt2009 when you type in /666 it says the account is suspended but after refreshing a few times it becaumes like in the vid this would be a cool easter egg

would be kinda funny but not sure whether something like that is something actually worth development time and would be actually used

would be kinda funny but not sure whether something like that is something actually worth development time and would be actually used

what about making /666 just go to the video?

if this was added, wouldn't it be inaccurate to actual old youtube?


Error: nothing found to replace when no match found

In some cases, if no match is found, it's not a mistake.
For example: Read a folder with several files in it, then execute the ruplacer command for each file to replace, for example, "Hi" with "Bye" in each file read. If "Hi" is found, replace, otherwise skip (this should not be considered an error). If a match is found, OK, otherwise, SKIP. Wouldn't it be better to have a skip flag to prevent this behavior?
In my terminal, I get a lot of errors when there aren't any.

Other proposal: With ripgrep for example, it's possible to display only the modified items in output and not the entire file content + changes, especially for large files. This could be an idea for a new feature flag.

@dmerejkowsky That's true, but in fact I use a regex on top of it to look for different files in which I want to make the changes.  The ruplacer command is therefore called for each file in the loop, which is why the message is displayed several times, and that's normal. The problem is the error display. If ruplacer finds nothing, then there's nothing to change, so skip it. I don't pass global folder as arguments to ruplacer, but specific files.. For example:
// node
const result = /*find with regex somes files*/

result.forEach((file) => {
     const command = `ruplacer --go "find" "replace with" "${file}"`
    ...
})


F1 score not equals the result of the formula

in beta6, F1 score not equals the result of the formula
F1 != 2*Precision*Recall/(Precision+Recall)
Accuracy:        0.9434
Precision:       0.6258
Recall:          0.5170
F1 Score:        0.5451
Accuracy:        0.9438
Precision:       0.5964
Recall:          0.5138
F1 Score:        0.5381
Accuracy:        0.9424
Precision:       0.6036
Recall:          0.5222
F1 Score:        0.5471

This formula is only relevant if you only have two classes. If you have more than 2 classes, F1 is calculated differently. See the javadoc here:
https://deeplearning4j.org/api/latest/org/nd4j/evaluation/classification/Evaluation.html
Unfortunately, you didn't provide us with enough information to be able to say what exactly is happening in your case.

There are 12 classes here in nlp task. most examples are in 2 classes and a bit examples are in other 10 classes.

Then you are definitively in the "more than 2 classes" camp. And that means the formula you suggested above does not apply to your case, but instead this applies:

For multi-class classification, binary metric methods such as f1(), precision(), recall() will report macro-average (of the one-vs-all) binary metrics. Note that you can specify micro vs. macro averaging using f1(EvaluationAveraging) and similar methods


Normalize legend on  y-axis  (round grid to either 50s or 100s or some number that makes sense based on the data (ie:  show 50, 100, 150, 200 instead of 36, 72, 123, 179, etc)

Hi @AbhishekMuknak 👋
This can be achieved using the props-
maxValue
stepValue
noOfSections
These props are correlated:
They must follow the relation:
maxValue = noOfSections * stepValue;

For example, to show 50, 100, 150, 200, you can set
maxValue = {200}
stepValue = {50}
noOfSections = {4}

Find details here- Bar Chart props
I hope it helps🤗


Different behavior between Chrome/Firefox implementation and polyfill

I'm having a hard time nailing it down, but my code works in both the latest Firefox and Chrome, and when I run the tests in Selenium, but when I require the polyfill for Poltergeist/Phantomjs, I get different behavior. It appears that my callback isn't being called when I nest promises. Pardon the messy code, it's in transition:
var TimeframeStore = {
  ...
  getAll: function () {
    return new Promise(function (resolve, reject) {
      TaskStore.getAll().then(function (data) {
        this.updateModels(data);
        request({
          method: 'get',
          url: this.url(),
          success: function (data) {
            medianProductivity = data.meta.medianProductivity;
            resolve(this.getData());
          }.bind(this)
        });
      }.bind(this));
    }.bind(this));
  }
}

and inside my component:
var TimeframesIndex = React.createClass({
  ...
  componentDidMount: function () {
    TimeframeStore.getAll().then(function (data) {
      this.updateTimeframes(data);
      TimeframeStore.on('change', this.loadTasks);
    }.bind(this));
  },

  loadTasks: function () {
    TimeframeStore.getAll().then(this.updateTimeframes);
  },
  ...
}

It works as expected in componentDidMount, but when it gets called a second time in loadTasks, even though I can confirm that resolve gets called within the nested promise, updateTimeframes never gets called.

This might be an issue with the way you are polyfilling, but I can't be sure. Can you make sure there isn't another error? Try putting an error handler on your getAll() call. The error should tell you what is going on.

Right now I'm polyfilling like:
if (!window.Promise) {
  window.Promise = require('promise-polyfill');
}

It works fine in other situations. I just tried adding error handlers both to loadTasks and as a second argument to TaskStore.getAll() and saw nothing from either of them. If I log out in loadTasks and in the success: callback from request it shows up for both, but not in updateTimeframes after that. I may just sidestep the issue by getting rid of the second request. It was a quick and dirty attempt to tie the stores together, but I think I know where I want it to go next.

I haven't seen an issue like this before. I and others are using the library the exact same way in production. Not saying there isn't an issue, but most likely it is something in your model code. Is the code in a public repo? I'll take a look. If not, it would be really helpful if you can reproduce the issue in jsfiddle.
Since you are only seeing the issue when polyfilling, maybe some code executing before you do
if (!window.Promise) {
  window.Promise = require('promise-polyfill');
}

? Maybe code is holding on to an undefined reference? Just a guess. I might be way off.

It's a private rails app, but I can add you as a contributor if you want to poke around. There isn't an existing reference, since when I remove the polyfill it throws an error saying Promise is not defined or the like, which is what prompted me to add it in the first place. I'm not too sure how to go about breaking it down into a more useful repro, but I'll take another look at it tomorrow morning and see what I can come up with.

Another thought. Could you try testing another library? Try using bluebird or another Promise library. Do you still see the issue?

Sure, I'll give that a shot.

Hmm, fails the same way with bluebird, too. It also fails Selenium if I override the browser implementation with the polyfill, though I haven't been able to reproduce the issue manually in the browser.

I am not too familiar with debugging PhantomJS. I know there are some ways to open the Chrome debugger and see what is going on. http://phantomjs.org/troubleshooting.html . The other option is to throw some console.log statements in your code. Let me know what you find.
Promises are pretty basic at their core. It keeps an array of callbacks and then calls each callback in the array asynchronously when resolve or reject is called.
Here is a link to where the library calls the callbacks async https://github.com/taylorhakes/promise-polyfill/blob/master/Promise.js#L33 . Might help to throw a console log statement in there or pause the debugger and see what is happening.

Okay, I think I know what's wrong. I'm using sinon.useFakeTimers() in my tests which stubs out setTimeout. handle gets called, but the scheduled function in asap never does. I'm guessing the native implementation doesn't make use of setTimeout, which is why it works with Selenium. And the fact that I can't reproduce the error in dev is because I'm not using sinon.
I'll go ahead and close this, but if you have any suggestions I'd be glad to hear them. It would be great if there was a way to set the browser time without stopping it completely. I tried using clock.tick(5) and that didn't make a difference...

I've gone with a different approach which allows me to go without sinon.useFakeTimers(), but I just came across this issue on Bluebird that seems like it deals with this use case. Not sure if it's something that promise-polyfill should address as well: https://github.com/petkaantonov/bluebird/issues/631


Added json files to the list of UnityFileExtensions

XRTK - Mixed Reality Toolkit Pull Request
Overview

Changes

Fixes: #689
Fixes: https://github.com/XRTK/SDK/issues/201

/azp run

/azp run

/azp run

/azp run

Thanks @StephenHodgson , this will be very useful for the Steam platform, so long as it is able to return the path to the json files.


Reading progress not saved in HTML

Version 1.1.8 (31.12.2021 10:00 PM)
When activating "Render HTML" and leaving the current book, the reading progress is lost. The progress bar is also not shown.
When deactivating "Render HTML" the progress bar returns and progress is also saved again, but the images are then missing.

Resolved in lnreader@d333381959f02004c1defac543f6e360fb759f2e


color gradation reversal

This is a great piece of software, thanks!
Could it be better if the visual aid's colors were reversed, meaning when the node is at 100% capacity, its red on the right vs on the left (which would be green). So at a glance, a user would know that if its red, the node is fully utilized.

I picked the current color scheme so that low utilization (bad) was red and high utilization (good) was green.  I'm happy to accept a PR that leaves this as the default but has a command line option to swap it.


Simplify internal logic of Table.order_by, avoid unnecessary warning

Pull Request Description

Fixes #8213

Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

I don't seem to see a noticeable difference in performance. The new approach seems to be slightly faster, but it is within error-of-measurement range.


⚠ Bofrost.com has degraded performance

In 044a74f, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 859 ms

Resolved: Bofrost.com performance has improved in 541c102 after 21 minutes.


GEODE-7536 - Break Gfsh out into separate module

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

This initial PR contains two commits. The first should essentially just contain file moves. The second contains code changes that would be more relevant for reviewing.

@jmelchio For your review


Q: Move the ABRP integration to the gateway?

This is more of a question, but looking at the evolution of the MQTT gateway I'd suggest to move the ABRP integration there in order to keep the library "clean" of any non-saic API code

I am not even using this and I don't know if anyone else does.
Since the update_abrp() method is using the data structures vehicle_status: OtaRvmVehicleStatusResp25857 and charge_status: OtaChrgMangDataResp, it is more or less bound to the SAIC API.
If we decouple the method parameters, we could move it away from the client.

I am 😁  it's very useful to let ABRP know when the car is charging and to record trips/consumption stats without having to plug an ODB dongle in every time.
Let's leave this here for know, but I'm sure we can get everything from the gw vehicle handler right now

Also using it and just posted a question on ABRP integration in the gateway-topic/issues. Who is the developer of the ABRP connector? Maybe he/she can answer my question.


init() missing 1 required positional argument: 'name' with coverage ~= 6.1

After updating to coveralls ~= 3.3 and trying to run the CI of pylint with coverage ~= 6.1 we are running into an error. Based on the traceback I'm reporting it here. Running with coverage ~= 5.5 does not fail.
2021-11-04T11:04:44.0937803Z Submitting coverage to coveralls.io...
2021-11-04T11:04:44.1569408Z Traceback (most recent call last):
2021-11-04T11:04:44.1572295Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/reporter.py", line 122, in report
2021-11-04T11:04:44.1573884Z     from coverage.report import Reporter  # pylint: disable=import-outside-toplevel
2021-11-04T11:04:44.1575607Z ImportError: cannot import name 'Reporter' from 'coverage.report' (/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coverage/report.py)
2021-11-04T11:04:44.1576500Z
2021-11-04T11:04:44.1577134Z During handling of the above exception, another exception occurred:
2021-11-04T11:04:44.1577658Z
2021-11-04T11:04:44.1578094Z Traceback (most recent call last):
2021-11-04T11:04:44.1578880Z   File "/home/runner/work/pylint/pylint/venv/bin/coveralls", line 8, in <module>
2021-11-04T11:04:44.1579559Z     sys.exit(main())
2021-11-04T11:04:44.1580635Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/cli.py", line 95, in main
2021-11-04T11:04:44.1581485Z     result = coverallz.wear()
2021-11-04T11:04:44.1582616Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/api.py", line 252, in wear
2021-11-04T11:04:44.1583503Z     json_string = self.create_report()
2021-11-04T11:04:44.1585067Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/api.py", line 330, in create_report
2021-11-04T11:04:44.1585940Z     data = self.create_data()
2021-11-04T11:04:44.1587096Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/api.py", line 384, in create_data
2021-11-04T11:04:44.1588222Z     self._data = {'source_files': self.get_coverage()}
2021-11-04T11:04:44.1589453Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/api.py", line 404, in get_coverage
2021-11-04T11:04:44.1590540Z     return CoverallReporter(workman, workman.config, base_dir,
2021-11-04T11:04:44.1592115Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/reporter.py", line 23, in __init__
2021-11-04T11:04:44.1593006Z     self.report(cov, conf)
2021-11-04T11:04:44.1594179Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/reporter.py", line 125, in report
2021-11-04T11:04:44.1595096Z     return self.report5(cov)
2021-11-04T11:04:44.1596276Z   File "/home/runner/work/pylint/pylint/venv/lib/python3.8/site-packages/coveralls/reporter.py", line 71, in report5
2021-11-04T11:04:44.1597368Z     matcher = FnmatchMatcher(prep_patterns(config.report_include))
2021-11-04T11:04:44.1598457Z TypeError: __init__() missing 1 required positional argument: 'name'

Run of the CI can be found here https://github.com/PyCQA/pylint/runs/4104109552?check_suite_focus=true
Perhaps #330 only adds support for 6.0 and not 6.1?
Happy to provide any other details or data necessary to fix this!

It might be easier to address in coveragepy. I opened https://github.com/nedbat/coveragepy/issues/1273 for it.

I have similar problem running coveralls in GitHub Action
  coveralls
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.10.0/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.10.0/x64/lib
    GITHUB_TOKEN: ***
    COVERALLS_SERVICE_NAME: github
Submitting coverage to coveralls.io...
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/reporter.py", line 122, in report
    from coverage.report import Reporter  # pylint: disable=import-outside-toplevel
ImportError: cannot import name 'Reporter' from 'coverage.report' (/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coverage/report.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.0/x64/bin/coveralls", line 8, in <module>
    sys.exit(main())
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/cli.py", line 95, in main
    result = coverallz.wear()
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/api.py", line 252, in wear
    json_string = self.create_report()
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/api.py", line 330, in create_report
    data = self.create_data()
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/api.py", line 384, in create_data
    self._data = {'source_files': self.get_coverage()}
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/api.py", line 404, in get_coverage
    return CoverallReporter(workman, workman.config, base_dir,
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/reporter.py", line 23, in __init__
    self.report(cov, conf)
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/reporter.py", line 125, in report
    return self.report5(cov)
  File "/opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/coveralls/reporter.py", line 76, in report5
    matcher = FnmatchMatcher(prep_patterns(config.report_omit))
TypeError: FnmatchMatcher.__init__() missing 1 required positional argument: 'name'
Error: Process completed with exit code 1.

@TheKevJames Will need to pin the version to the next release of coverage as this will be fixed in that version.

@TheKevJames Please pin coverage to 6.1.2 😄

Please pin coverage to 6.1.2 😄

@DanielNoord I wouldn't suggest pinning coverage. It's much better to exclude incompatible versions. -> #337

Yeah, that's what I meant. Thanks for opening the PR 🎉

Hey folks, thanks for investigating this and special thanks to @cdce8p for the fix. I've just released coveralls v3.3.1 with the included restriction.
Separately, I'll investigate further our use of internal APIs from coverage-py as mentioned in https://github.com/nedbat/coveragepy/issues/1273 . I really thought we'd managed to fix that issue...


Fix usage example in readme

I've got TypeError: HeaderGenerator is not a constructor when I used it as in usage example.

the readme is for the next version that is not yet released, its correct for the code in master, we dont use default export anymore

Ok, cool 😎


[TAG] Move website content to main branch

This PR proposes merging the website content currently in the jekyll branch into the main branch in a website subdirectory.
This will make it easier for contributors to add content and update styles for our blog - just update the website dir in the main branch.
The script isn't needed since the bundled Action "step" executes equivalent functionality, but leaving it just in case.
Verified that the slightly updated workflow runs fine here: https://github.com/joshgav/tag-app-delivery/actions/runs/4368966252/jobs/7642214572
Related: #326, #318
cc @krumware @thschue

Instead of this we'll move to Hugo and migrate the content as in #333 and #329.


Tree view doesn't programatically collapse Tree items

I'm developing custom VSCode extension and i want to have an option to quickly collapse some expanded tree view items.
For this purposes I've tried to trigger onDidChangeTreeData event and recreate TreeItem with desired collapsible state, but it din't have effect.
There is a pretty similar issue https://github.com/Microsoft/vscode/issues/44746 , but solution mentioned in there is only suitable for expanding tree items (I tried to call reveal with expand: false option, and it didn't work also).
Also Collapse all button is not suitable for my needs.
I'm on Version 1.37.0

Duplicate of https://github.com/microsoft/vscode/issues/92176


tcp error, os error 111

Command:
./ord --data-dir xxx --bitcoin-data-dir xxx --bitcoin-rpc-password xxx --bitcoin-rpc-url <IP_ADDRESS> --bitcoin-rpc-username xxx index run
Error:
[2024-03-21T05:59:20Z ERROR ord::index::updater] Couldn't receive txs failed to fetch raw transactions after 5 retries: error trying to connect: tcp connect error: Connection refused (os error 111)
error: failed to get transaction for a2df039d22ce84803de677328efe3a2fe82b0102d66c32f899715608babd1214
How do I fix him?
OS: Ubuntu 22.04.3 LTS
Ord Version: 0.16.0

Delete the bitcoin core rpc configuration and update the index using a cookie file to resolve the issue.

Delete the bitcoin core rpc configuration and update the index using a cookie file to resolve the issue.

can you specify the method? I encounter the same issue

@yadgen  can you add some details on how you fix the issue? appreciate it!


Add javadoc and unit test for branch spot features

Add TestGraph1, TestGraph2 and TestGraph2
Add javadoc and unit test for BranchNSpotsFeature
Add javadoc and unit test for BranchDisplacementDurationFeature
Add javadoc and unit test for BranchDepthFeature

Code looks good. Could you check if the javadoc is correct. The BranchGraph often seems to be flipped when compared to the ModelGraph. And I would suggest to avoid the terms Spot-Graph and BranchSpot-Graph and stick with the more widely used terms ModelGraph and BranchGraph.

I made the respective changes in the javadoc.

I added a method getSpotFeatureProjection() to FeatureComputerTestUtils.
Even though this method is not (yet) used in this repository, I think, it makes still sense to have it for future tests on the Spot level.

Hi @tinevez,
@stefanhahmann wrote some unit tests for the existing branch spot features.
There are also two new classes ExampleGraph1 and ExampleGraph2, that can be reuse in other unit tests.
I think the PR is ready to be merged. What do you think?


Cache computation of JSON nodes to improve performance

WIP. Seeing 4x speedup on large nested schema after adding caching, but we can probably squeeze more performance out of this. Not sure if the frozendict dep is strictly necessary; just trying out a quick idea.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 58.17%. Comparing base (8d63c79) to head (3484fe8).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #995       +/-   ##
===========================================
+ Coverage   44.74%   58.17%   +13.42%
===========================================
  Files          62       62
  Lines        4392     4394        +2
===========================================
+ Hits         1965     2556      +591
+ Misses       2427     1838      -589

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

@riedgar-ms tests/unit/library/test_json.py::TestOneOf::test_oneOf_compound[True] is currently failing because the warning only happens on the first call (the second just hits the cache). Any thoughts?

An open question: is top/module-level caching a good idea? I could add a layer of encapsulation such that all of the underscore prefixed functions only maintain a cache within a single call to json... Thoughts?

An open question: is top/module-level caching a good idea? I could add a layer of encapsulation such that all of the underscore prefixed functions only maintain a cache within a single call to json... Thoughts?
Also, feeling pretty okay about the frozendict requirement. It helps a lot with making everything nicely hashable without too much fuss.

You might want to cross check with Paul, since he's been doing the async/multithreaded stuff.

@paulbkoch would love your input on the caching business here :)

Currently, the performance gain on actually constructing the grammar doesn't seem super affected by this PR (I think thanks to #1007, which provided a significant boost on its own).
However, caching is still needed -- otherwise we hit a limit on the number of symbols that llguidance currently allows in a grammar. Raising that limit is a non-fix, as it has implications about the performance of mask computation.

An open question: is top/module-level caching a good idea? I could add a layer of encapsulation such that all of the underscore prefixed functions only maintain a cache within a single call to json... Thoughts?

The one scenario I could think of where per-json call caching might be superior is in the case of a long running workload with constantly changing JSON schemas that are unique per call.  In that case module level caching will keep consuming more and more memory.  Given the JSON schemas and grammars are pretty compact, it would probably take a long time to exhaust memory though, so it's probably not the most important thing to solve.  In terms of async, I can't think of an issue this caching would create, at least not after your other PR on fixing threaded grammars @hudson-ai.
The rest of the PR looked fine to me.  I can't say that I understood all the JSON schema nuances here, but the application of caching to the existing code looked good to me.

The one scenario I could think of where per-json call caching might be superior is in the case of a long running workload with constantly changing JSON schemas that are unique per call. In that case module level caching will keep consuming more and more memory. Given the JSON schemas and grammars are pretty compact, it would probably take a long time to exhaust memory though, so it's probably not the most important thing to solve. In terms of async, I can't think of an issue this caching would create, at least not after your other PR on fixing threaded grammars @hudson-ai.

Agreed. If I can get my other PR on method decoration together, it would make it really easy to cache on a per-schema basis (one schema = one instance of a GenJSON class, methods are cached at the instance level...).
If there are no objections, it would be great to merge this PR (and per-schema caching could go in a future one).
Just want to reiterate that this introduces a new dependency in frozendict

Closing as this work is moving into llguidance


Loading Very slow switch tabs .Very slow

I have the lasted version but it loads very slow changing tab to tab , I cleared my history but still very slow .

Hi, thanks for the report.  Is switching tabs suddenly a lot slower than it used to be, or has it always been this slow?  How slow are we talking about?  Do all tabs take the same amount of time to switch to, or do some take longer than others (e.g., those with more items)?  What do you mean when you say you cleared your history?  Also, can you attach your DebugInfo.Log file?  That might have some information about what is going on.

I've tested this and it works absolutely fine for me.

Is procurement being kept up to date?
On Wednesday, December 6, 2023 at 12:43:48 AM CST, Charles Macanka @.***> wrote:
Closed #1016 as not planned.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

It currently needs a few updates, but I hope to get caught up soon.
This bug was closed because it did not have any actionable information, and it has sat idle for years.


Add categories to mark active in menu correctly

Fixes #156

Also need to change type: server to category: api in API docs.

I would love to not reintroduce the category keyword in the front matter for this really, as it's cumbersome and error-prone.
I was about to do it using URL prefix because really it makes sense, if you're under /docs/guides/foo and you go back to docs/guides you should go to the parent page. Mind doing that instead?
I'm aware that this won't work for the unofficial install ~methods~ method and hmm... I'm not too offended by this one not marking the install page as active really. For one thing, it's the only page in there, and... I have suggested to kill it in a couple places 😬

I tried the URL, but it uses the folder name, so it doesn't match, unsure if there's another method


Update secp256r1 Package to utilize agent_dart 1.0.0-dev.18

Our package is currently running into this issue: https://github.com/magiclabs/magic-flutter/issues/45 due to an error with legacy version of agent_dart 1.0.0-dev.17. Could you please consider releasing a new version of this package that points to the latest version of agent_dart?  Thanks!

For reference, here's the original issue on agent_dart's repo: https://github.com/AstroxNetwork/agent_dart/issues/70

This can be done by flutter pub upgrade automatically without any changes to downstream packages.


Crawling Ethereum blockchain data

The Ethereum blockchain caller should be callable from the command line.
Crawler interface
Transaction blocks
Add blocks (optionally adding transactions at the same time)
ethcrawler blocks add \
    --blocks <list of block numbers or block range in the format {start_block}-{end_block}> \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI \
    [--transactions]

Latest block to have been added
ethcrawler blocks latest \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI

Check if there are any missing blocks
ethcrawler blocks missing \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI

Transactions
Add transactions
ethcrawler transactions add \
    --block <block number> \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI

Get transaction by hash
ethcrawler transactions get \
    <txhash> \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI

List transactions in given blocks
ethcrawler transactions list \
    --blocks <list of block numbers or block range in the format {start_block}-{end_block}> \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI

Jobs
See which jobs failed (with hopefully some log messages or link to Humbug journal entry)
ethcrawler jobs errors \
    --jobtype {blocks|transactions|pending_transactions} \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI

ethcrawler jobs pending \
    --jobtype {blocks|transactions|pending_transactions} \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI

ethcrawler jobs replay \
    --jobtype {blocks|transactions|pending_transactions} \
    --db <database connection string> # This is probably better as environment variable - MOONSTREAM_DB_URI

There should be a jobs table (or one jobs table per job type) in the database that tracks the state of jobs.
Each job should contain 3 time stamps: submitted_at, started_at, completed_at.
started_at and completed_at can be NULL.
Besides that, the job should also accept arguments (as passed to crawling worker functions).

@kompotkot is synchronizing some old transactions into the database currently. Once he is done with the current job, we will have to update our Postgres instance to one that has more memory (this is our bottleneck currently, for sync jobs).
We will go live in Alpha with subscriptions only guaranteed for future transactions. This will give us a week or two of time to synchronize with the old parts of the blockchain.

In a good state for now. All other improvements to be made opportunistically.


Expose new metrics for memory usage in the cgroup.

The metric "mem_kmem_usage_bytes" is the total kernel memory usage by
processes in the cgroup in bytes.
The metric "mem_kmem_tcp_usage_bytes" is the total memory usage for TCP
buffers in bytes.

Mind squashing this locally on your end since you've got follow on commits here that should be part of the original single commit?

Mind squashing this locally on your end since you've got follow on commits here that should be part of the original single commit?

Squashed.


Add alternative VS Code/Windows Terminal themes

What is the intent with these alternatives? I would prefer to have one canonical implementation for each app if possible. Are there improvements here that we could bring to the current ports?

What is the intent with these alternatives? I would prefer to have one canonical implementation for each app if possible. Are there improvements here that we could bring to the current ports?

I didn't want to install a theme pack with unrelated themes, and wanted to choose my accent colors. The terminal themes include a light version. All themes are built from the color scheme as provided on the website to make changes & improvements easier. I only saw 2 published extensions that did not fit my needs.
Feel free to close the PR and port any changes if you'd like. These were made for my own personal use, mostly.
Thanks for the great color scheme!


Upgrades.

CM motivated by #148
Quite a bit of CM change so we should review with care in addition to checking the bug fix.
Probably sensible to review the back catalog of incremental parse bugs as they're quick to test.

Seems fixed but we should fix #233 and retest to be more confident.

Other than code structure issues this seems to be working well.

Rebased on main with fix for #233 so once that's deployed I'll retest.


Enhance API Reference Documentation for nnbench

Enhance API Reference Documentation for nnbench
Similar to lakefs-spec (https://github.com/aai-institute/lakefs-spec/pull/273#pullrequestreview-1948477032), we would like to make improvements to the API reference documentation generation for the nnbench library. The proposed changes include:

Extracting module docstrings for root-level modules:

Update the gen_api_ref_pages.py script to extract the module docstrings for root-level modules in the package.
Add the extracted docstrings to the index page of the API reference.
Utilize the docstring_parser library to parse the docstrings.

Adding links to root-level modules on the index page:

Include links to the root-level modules on the index page of the API reference.
Generate these links automatically based on the navigation structure.

Updating dependencies:

Add the docstring-parser library to the documentation dependencies in pyproject.toml.

These enhancements aim to provide a more comprehensive and user-friendly API reference documentation for the nnbench library. The inclusion of module docstrings and links to root-level modules will make it easier for users to navigate and understand the library's structure and functionality.

Solved with https://github.com/aai-institute/nnbench/pull/123


Fix build warning for AccountSettingReducer

https://github.com/EhPanda-Team/EhPanda/issues/356
Fix a bunch of build warning in AccountSettingReducer

@tatsuz0u Thanks for the detailed comments! Could you take another look?

LGTM!
cc @chihchy


Updated steel it section... please don't run code climate on my accou…

…nt...
also add todos
What does this PR do? (User can login)
no functional change... but hoping people won't use my token to run code climate!
Where should someone start to review?
meh
How could you test this PR's functionality?
with your eyeballs... do these works make sense?
New dependencies?
Gif of your feels

+1


Powershell or Graph API available?

Is it possible to get this information about Call Quality using powershell or programmatically with Graph?

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

ID: 9374347d-42cb-4955-6eac-3efd04eef66d
Version Independent ID: 985dbd00-b456-13c3-5928-b423084d3a87
Content: Monitor and troubleshoot Direct Routing - Microsoft Teams
Content Source: Teams/direct-routing-monitor-and-troubleshoot.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@Elecktrus thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


"pip install" should not be executed if no deps

Summary
=======
Variable []
Fixed []

Versions
========

FAIL max: Install failed
  $ /tmp/tmp3ylczuet/bin/python -m pip installERROR: You must give at least one requirement to install (see "pip help install")
  WARNING: You are using pip version 20.1.1; however, version 20.2.3 is available.
  You should consider upgrading via the '/tmp/tmp3ylczuet/bin/python -m pip install --upgrade pip' command.

I can check this out. Can you assign this to me

Here you go!
Steps to reproduce:

Make an empty directory somewhere, I'll call it /tmp/example
Create /tmp/example/setup.py containing these lines, representing a minimal setuptools project that has no dependencies:

from setuptools import setup
setup()

Set up pessimist development environment

cd /path/to/pessimist
make venv
source .venv/bin/activate

4. Run against that directory.

python -m pessimist /tmp/example

The bug is calling `run()` to install packages, when there were no packages that needed to be installed.  This triggers the "Install failed" message.  Those should be some hints to get you started; feel free to ask questions.

Fixed in https://github.com/python-packaging/pessimist/commit/b9cfb1ea1fbfdc5aa419bcae8d9203dfae523305


Namespace ElectronNET could not be found

Hello,
I was looking at trying Electron.NET for the purposes of building an x-plat app in a language (C#) that I'm familiar with.
I followed the guide in the readme - Installed the global tooling, created a new MVC app, installed the ElectronNET.API nuget package, made the appropriate changes to Program.cs and Startup.cs, and ran electronize init.
Here's output from electronize init:
PM> electronize init
Adding our config file to your project...
Search your .csproj to add the needed electron.manifest.json...
Found your .csproj: C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\Launcher.FotC.csproj - check for existing config or update it.
electron.manifest.json will be added to csproj.
electron.manifest.json added in csproj!
Search your .launchSettings to add our electron debug profile...
Debug profile added!
Everything done - happy electronizing!

After this, I was ready to start. Since this is just to see it run, I thought I'd use the built-in web page that tells you all about IIS. So to start, I ran electronize start. Here's the output from that:
PM> electronize start
Start Electron Desktop Application...
Microsoft Windows [Version 10.0.17134.376]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC>dotnet publish -r win-x64 --output "C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\obj\Host\bin"
Microsoft (R) Build Engine version 15.9.20+g88f5fadfbe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.
  Restoring packages for C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\Launcher.FotC.csproj...
  Generating MSBuild file C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\obj\Launcher.FotC.csproj.nuget.g.props.
  Generating MSBuild file C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\obj\Launcher.FotC.csproj.nuget.g.targets.
  Restore completed in 2.09 sec for C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\Launcher.FotC.csproj.
Program.cs(6,7): error CS0246: The type or namespace name 'ElectronNET' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\Launcher.FotC.csproj]
Startup.cs(5,7): error CS0246: The type or namespace name 'ElectronNET' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\Launcher.FotC.csproj]
C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC>
Error occurred during dotnet publish: 1

After a bit of investigation, I found that the dotnet publish command runs a dotnet restore, which removes the ElectronNET.API nuget package. In other words, the build process removes the API and then complains that it couldn't find it.
I've asked around in a C# group that I'm in but we were unable to diagnose this behavior. We did break down a few of the steps and we found that running dotnet restore did indeed remove the package, though its output doesn't represent that:
PM> dotnet restore
  Restoring packages for C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\Launcher.FotC.csproj...
  Generating MSBuild file C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\obj\Launcher.FotC.csproj.nuget.g.props.
  Generating MSBuild file C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\obj\Launcher.FotC.csproj.nuget.g.targets.
  Restore completed in 1.95 sec for C:\Users\Foxtrek_64\Documents\Projects\LuzFaltex\Launcher.FotC\Launcher.FotC.csproj.

Any assistance on this issue would be appreciated. I would rather like to see this work.

Edit: I seem to have made a very strange discovery. Running electronize start from PowerShell makes it past the restore successfully. After installing Node.js (doh!), I was able to get the app to start successfully.
So, I pose this question to you: why did this task fail when running under the Package Manager Console but when running under PowerShell it worked just fine?
Also, as an interesting note, despite the documentation saying dotnet electronize ..., attempting to run that results in an error stating No executable found matching command "dotnet-electronize". When I installed electronize, it told me to use it as just electronize, so that's what I've been doing. Is this a result of outdated documentation?
Here's a screenshot of the working app:

We updated the readme - don't use "dotnet electronize" instead use just "electronize".
Hope this helps!

I had this same problem with the build process removing the Electronize.API package. The solution I found was that electronize didn't like the way Visual Studio installed it. To fix this, I just installed it from the terminal.
dotnet add package ElectronNET.API

And it worked like a charm.

I had this same problem with the build process removing the Electronize.API package. The solution I found was that electronize didn't like the way Visual Studio installed it. To fix this, I just installed it from the terminal.
dotnet add package ElectronNET.API

And it worked like a charm.

this still exist until this days. xD this should be in the readme xD It took a lot of try  cant figure it out why is it uninstall itself xD


Fix for Step 2 of the Add a Command section

(int)TestCommandPackageGuids.cmdidTestSubCmd in the second steps first line of code should just be cmdidTestSubCmd otherwise it can't compile.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/extensibility/adding-a-submenu-to-a-menu.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Bug] Snapshot contract errors for dbt_change_type and dbt_unique_key

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Defining in the config of a snapshot schema that contracts are to be enforced, one gets error relating to fields

dbt_change_type
dbt_unique_key

If one includes them in the schema for the first run of a snapshot, this generates an error since the fields do not exist yet. In subsequent snapshots (after an initial snapshot, and where a change has occurred) one gets an error if they are missing in the schema definition. This then requires one, especially in the development phase, to continually put these contracts in or take them out. Understandably, one has to define a contract for all columns in the schema that finally appear in the snapshot table. However, for internally generated columns, this is wasting development time. This doesn not happen for  dbt_scd_id column for example.
Expected Behavior
If  columns do not appear in the snapshot tables, and are internal, it should not cause a problem to not define their contracts directly in a schema.
Steps To Reproduce

Create schema for snapshot, with enforced contract in the config. Do not include contract for dbt_change_type and dbt_unique_key
Create a snapshot
Try and create a further snapshot where changes have occurred

Relevant log output
No response
Environment
- Python: 3.11
- dbt:1.7.1
- db: postgres

Which database adapter are you using with dbt?
postgres
Additional Context
No response

Thanks for reporting this @david-burke5000 !
Initial assessment
I suspect that we didn't intentionally include support model contracts for snapshots -- it's not listed here either way.
But at the very least, you did figure out how to get model contracts to work for snapshots in dbt-postgres (albeit with behavior that is a bit wonky).
When I tried it locally with dbt-postgres, I got the same behavior as you, but it didn't really work at all when I tried with dbt-snowflake.
Options
We've got a couple options moving forward:

Leave things as-is but update the documentation here to indicate that contracts are not supported for snapshots
Explicitly disable support by detect if a contract is defined on a snapshot and raising an error or a warning
Explicitly enable support by adding test cases and making code updates to dbt-postgres, dbt-snowflake, etc.

I'm going to label this as "refinement" for us to take a closer look.

We talked about this briefly today (@graciegoheen and myself). We thought we'd leave this in the Court of the Mesh King 👑  to decide. What do you think @jtcohen6?

@david-burke5000 @dbeatty10 My inclination is that we should not seek to officially support contracts on snapshots. Here's my rationale:
For snapshots that depend on sources (best practice), when a column in the upstream source system is added or changes data type, the snapshot will handle this by adding a new column with that name / data type. If a column is removed, the snapshot does not remove its corresponding column. In this way, we ensure that data is not lost (good!), but we trade off having a fully predictable schema for snapshots.
For snapshots that depend on models, and sit in the middle of the DAG (not something we encourage outright, but it definitely happens): I would recommend limiting the transformation logic in the snapshot to just select * from {{ ref('upstream_model') }} — something @graciegoheen and I have been discussing! — and applying the model contract on upstream_model instead. Then any schema mismatches will be caught by a build failure in upstream_model (good!), rather than the snapshot. Build failures for snapshots are scarier, because there's the potential implication of data loss.
To that end, I've opened a docs PR:

https://github.com/dbt-labs/docs.getdbt.com/pull/4954

What say ye? Any strong dissent?

No dissent from me, but I do think if we go this route we should add an error message when you attempt to add a contract to a snapshot, so folks don't get into this tricky spot.

To round out this story, here's the components that would be the most helpful:

flesh out the documentation

https://github.com/dbt-labs/docs.getdbt.com/pull/4954

add an error message when you attempt to add a contract to anything other than a model (snapshot, source, seed, etc.)

https://github.com/dbt-labs/dbt-core/issues/9607

explain the option of using a pass-through model to enforce contracts for these cases as needed

e.g., post on Discourse or somewhere else with instructions

Workaround using a pass-through model
Suppose you have a snapshot (or seed) named not_a_model. (Without loss of generalization, we can imagine a source with a similar name, but it would use source() instead of ref() below.)
To add a pass-through model contract, you can do the following:

Make a simple pass-through view
Enforce a contract on the pass-through view

1. Make a simple pass-through view
models/contract_for_not_a_model
{{ config(materialized="view") }}

select * from {{ ref("not_a_model") }}

2. Enforce a contract on the pass-through view
models/_models.yml
models:
  - name: contract_for_not_a_model

    contract:
      enforced: true

    columns:

      # snapshot-specific columns

      # your columns here

      - name: column_1
        data_type: dtype_1

      # etc.

      # snapshot-specific columns

      - name: dbt_scd_id
        data_type: text

      - name: dbt_updated_at
        data_type: timestamp

      - name: dbt_valid_from
        data_type: timestamp

      - name: dbt_valid_to
        data_type: timestamp

Dear @graciegoheen, @dbeatty10, @jtcohen6 ,
Thank you for your support and feedback on this issue! I am working together with @david-burke5000.
Unfortunately I am a bit late to this discussion but please allow me to add my two cents.
I am commenting the situation with the dbt-postgres-adapter in mind.
We work in a highly regulated industry where it is imperative that we track how data has changed over time. This is where we rely on the SCD2 snapshots to build the history of the data, incl. the time intervals a record is valid. All our downstream models are based on these snapshots.
Consequently, we want to ensure that the data in these snapshot tables is trustworthy by defining the appropriate data contracts (including database constraints, especially foreign key references).
Our current DAG: source table => view (adding metadata and derive surrogate key column + dbt tests) => snapshot (with data contracts) => any downstream model
Snapshosts vs. incremental models:
@jtcohen6 argued:

if a column is removed, the snapshot does not remove its corresponding column. In this way, we ensure that data is not lost (good!), but we trade off having a fully predictable schema for snapshots.

Currently contracts are supported for incremental models. As far as I understand, the behavior for incremental models with on_schema_change: append_new_columns is the same as for snapshots: new columns are added to the table, deleted columns are left within the table.
What is the reasoning to treat snapshots differently from increment models? In both cases, if the structure of an upstream model should change, it would be required to update the respective contract of the table.
Workaround using a pass-through model:
The workaround to add a view-based pass-through model would not (fully) work, as database constraints (e.g. not_null, primary_key, foreign_key) can only be applied on an actual table (in our case the snapshot table) and not on a view.
Adding a materialized pass-through model also seems rather unintuitive.
Kindly ask for further consideration and feedback on our thoughts.
Thank you and best regards!