Add ability to remove part of the series' data

Hi there, first off what a great library thank you very much for it!
As I am streaming a lot of data into my chart I need to remove old data items for performance reasons.
I am currently doing this by calling setData on each render pass.
I know that this process could be optimised so my feature suggestion is to add a removeData method to the DataUpdatesConsumer and series API.
I'll have a crack it myself when I have some time to learn how to debug TS :)

How many bars you have? I'm asking it because I just want to understand the case when it comes slow for you. We have tested it with several thousands and it was ok.
What do you use to update the data? update or setData?

Hi @timocov, I have 1min candle data spanning years.  I agree with you a couple of thousand bars is great when the chart is not rendering.
However I am streaming in bars so there are a couple of renders every second.    When in reality there could just be 1 bar added at the latest time, and 1 bar removed from the tail.

I presume update is less intensive than setData.  So all I need is a remove :)

Meaning I call setData a couple of times each second

Can you use update instead? It's aim is in update the latest bar or append the new one from the right and make it faster.

I presume update is less intensive than setData.

Yeah, it should.

when the chart is not rendering.

It's possible to get reproduce of performance issues you faced so you need to worry about that? We like to improve the project to make it faster and performative.
As workaround or improving the perf you can strip bars only several times. I meant, for instance, 1 time per 100-1000 bars.

Ive encountered the same issue.... as chart can get quite heavy with time Im looking for a way to strip old data from the chart, like to free up memory if that makes sense? But no remove function...
I was thinking bout gettings points of dataUpdatesConsumer some way, remove the whole chart, recreate it and set data but surely there is a better way to do this right?

As workaround or improving the perf you can strip bars only several times. I meant, for instance, 1 time per 100-1000 bars.

Thanks for the workaround @timocov .  I don't have a repro yet sorry but ill let you know when I do.

But no remove function... I was thinking bout gettings points of dataUpdatesConsumer some way, remove the whole chart, recreate it and set data but surely there is a better way to do this right?

@Tucsky yes, you can set new data with small count of bars.
Removing "bars" is tricky. Remove specific bar? Remove bars before passed? Remove the the only 1 series? We need to have more consistent solution than just "remove some bars because we can't call setData". And, if you have any repro of issues drawing several thousands bars and call update there - it'd be helpful there. Right now I see at https://leeoniya.github.io/uPlot/bench/lightweight-charts.html (afaik it has 160k points) and it draw them perfectly.

yes, you can set new data with small count of bars
ended up doing exactly that, and as you said it might not even be needed, chart itself is fast af. I have a module using lightweight charts which is adding new bar every second, I just sleep better knowing it wont have (604800*nb of series) bars after a week of having it open 😁

yes, you can set new data with small count of bars

ended up doing exactly that, and as you said it might not even be needed, chart itself is fast af. I have a module using lightweight charts which is adding new bar every second, I just sleep better knowing it wont have (604800*nb of series) bars after a week of having it open 😁

A bar a second works nicely - i'm replaying ticks as fast as I can which leads to multiple updates per second - where it starts to degrade.

Since this ticket was opened we improved updating the data (both setData and update) a lot so probably now you can use any of them to update the data or to implement a strategy of having only a few bars on the chart without performance issues. Let me know if you're still experiencing the issue or have anything to add here.


Error in errorlog method

I encountered this error this morning.  It looks like error is a class and not a string, but I haven't had a chance to dig in any deeper yet.  Note that nothing was logged to errorlogging_webhook.
Python 3.7.2.
[!] We encountered a small issue, please check error logging slack channel.
--
  | Traceback (most recent call last):
  | File "sublert.py", line 444, in <module>
  | posting_to_slack(new_subdomains, False, None)
  | File "sublert.py", line 384, in posting_to_slack
  | slack(data)
  | File "sublert.py", line 109, in slack
  | errorlog(errorlog, enable_logging)
  | File "sublert.py", line 148, in errorlog
  | slack_data = {'text': '```' + error + '```'}
  | TypeError: can only concatenate str (not "function") to str

You're correct! your fix should resolve it, thank you!


"implement" "jet" "dashboard"

This is an example of the "cheating" option for firing jets, implemented in the treewalking interpreter.  Included are jets for decrement and cut, since those are straightforward to do on bitslices without a separate bignum library.
Additionally, this includes a bugfix in the allocator, basic printing functions for nouns, and renames the axis function to slot because having the verb and noun named the same was awkward.
The commits are self-contained, let me know if you prefer those as separate PRs.

Thanks, I appreciate the rust tips!  I've never written rust before, so I don't know shortcuts or idioms.
Can you explain more what a jet trait buys us?  I suppose if we had other operations we wanted to add to a jet, it would keep it all in the same place.

Can you explain more what a jet trait buys us? I suppose if we had other operations we wanted to add to a jet, it would keep it all in the same place.

https://github.com/urbit/new-mars/pull/12#discussion_r1095936657 may be a somewhat satisfactory explanation. Another way of saying the same thing in fewer words is that a trait is a zero-cost way of explicitly specifying the semantics of jets and making that specification checkable by the type system.

@philipcmonk I'm fine to either merge this and then merge Peter's tas! macro after, or to just merge the tas! macro into your branch and then merge. Either way I'd like to get both PRs in


Make the available files list expandable

Currently if you have dozens of files it takes a while to scroll-down.

Closed by: https://github.com/biocore/qiita/pull/2539


chore(docs): update Authentication Service documentation

chore(docs): update Authentication Service documentation

The changelog is missing, lets wait for the feature to be tagged before merging this one


Remove Distorted Screenshots for Certain Instances

These don't gel with the design, let's remove these. If we don't have a badge for an instance or group, we can just use a ? badge.
I'll work on creating more badges. The squished & distorted images look awful.

Also please provide a list of instances / groups where we don't have badges. I think it's mostly just PVP groups?

2v2, 3v3, 5v5, and all battlegrounds are the only ones I've seen @Gogo1951, but for now they are back to just using our ? icon

we could also just use the pvp icon for those and call it a day, dont think we need new badges for each bg/arena

we could also just use the pvp icon for those and call it a day, dont think we need new badges for each bg/arena

did this


Example: plot several somas in same plot, each with different color.

Current coverage is 100.00%

Merging #71 into master will not affect coverage as of 51a60b9

@@            master     #71   diff @@
======================================
  Files           26      26
  Stmts          922     922
  Branches         0       0
  Methods
======================================
  Hit            922     922
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 51a60b9

Powered by Codecov. Updated on successful CI builds.

And now?


✨ Added functionality to enable seek gesture during initial and pause…

Added initial and pause state to seekTo method of PlayerController to enable gesture during those states.

Hi @KeithBacalso,
Thank you for the PR. We truly appreciate your efforts! However, this update has already been included in the latest release. As a result, we’ll be closing this PR.
We value your ideas and welcome any new suggestions or improvements you’d like to propose in the future.


WaitGroups?

Hello, thank you for putting together such a great resource!
I was wondering if you plan to add a section for WaitGroups in this book. If not, then would you be ok if I submit something as a pull request?

我靠，中文书都能看懂？


[4pt]  -Display Comments pop up with selected item's details - Student B

Create a comments popup only with the top section (displaying details of the selected item)

When the popup loads, the webapp retrieves data from the selected API and shows details about the selected item.
Add event to button prepared by your teammate that will open your popup. You need to communicate with your team member to make sure that you do not block each other (most likely the easiest solution is to merge the list of items feature to the dev branch before you try to add that event).

The pull-request to the following issue is https://github.com/Sajeelzafar/JavaScript-Capstone/pull/28.


🔒Your funds are safe, once the transaction is confirmed, you will receive + 122346,00 NOT

🔒Your funds are safe, once the transaction is confirmed, you will receive + 122346,00 NOT
Originally posted by @wlofman021 in https://github.com/tonkeeper/opentonapi/issues/389

:)

من دریافتی نداشتم

really?

hi haw to claim this reward?

31 Tem 2024 Çar 01:25 tarihinde sara59e @.***> şunu
yazdı:

من دریافتی نداشتم
—
Reply to this email directly, view it on GitHub
https://github.com/ton-blockchain/verifier/issues/215#issuecomment-2259308140,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BISYRC625ZVTMLC3DDYPEBLZPAHEFAVCNFSM6AAAAABKEVLEYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJZGMYDQMJUGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Open

#218

Claim now

🔒Dana Anda aman, setelah transaksi dikonfirmasi, Anda akan menerima +122346,00 BUKAN
Awalnya diposting oleh@wlofman021dalam penjaga ton/opentonapi#389

My scam, no money was deposited into my wallet, you just took

Hello thank you

122346,00

UQDasWTnuOI4srBPkX9pufz71AV6UuJmApkUhAHeD8Kg2dHz

:)

So good

Great

Nice

Good

Great

Great

Good

Nice

Good

Great

Great 💯

🔒Your funds are safe, once the transaction is confirmed, you will receive + 122346,00 NOT
Originally posted by @wlofman021 in tonkeeper/opentonapi#389

12345

12345

12345

12345

      hi, somebody know what is wrong with this project!? What a problem? Why they don't return the money? thanks in advance!


TypeError: can't compare offset-naive and offset-aware datetimes in ExecuteRequestBody.last_item

When using the Theoriq library, I encounter a TypeError when comparing datetimes in the last_item property of ExecuteRequestBody. The error occurs because the library attempts to compare datetime objects where some have timezone information (offset-aware) and others don't (offset-naive).
Stack Trace
TypeError: can't compare offset-naive and offset-aware datetimes
return max(self.dialog.items, key=lambda obj: obj.timestamp)
File "/usr/local/lib/python3.11/site-packages/theoriq/schemas/request.py", line 148, in last_item
if not req.last_item or not req.last_item.blocks:
File "/app/server.py", line 172, in execute

2024-11-09 10:12:14,106 -<PHONE_NUMBER>71328 - client.py-client:1038 - INFO: HTTP Request: GET https://theoriq-backend.prod-02.chainml.net/api/v1alpha1/auth/biscuits/public-key "HTTP/1.1 200 OK"
Nov 9 11:12:14 AMTypeError: can't compare offset-naive and offset-aware datetimes
Nov 9 11:12:14 AM ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 9 11:12:14 AM return max(self.dialog.items, key=lambda obj: obj.timestamp)
Nov 9 11:12:14 AM File "/usr/local/lib/python3.11/site-packages/theoriq/schemas/request.py", line 148, in last_item
Nov 9 11:12:14 AM ^^^^^^^^^^^^^
Nov 9 11:12:14 AM if not req.last_item or not req.last_item.blocks:
Nov 9 11:12:14 AM File "/app/server.py", line 172, in execute
Nov 9 11:12:14 AMTraceback (most recent call last):
Nov 9 11:12:14 AM2024-11-09 10:12:14,051 - ERROR - Error processing request: can't compare offset-naive and offset-aware datetimes
Nov 9 11:12:14 AMTypeError: can't compare offset-naive and offset-aware datetimes
Nov 9 11:12:14 AM ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 9 11:12:14 AM return max(self.dialog.items, key=lambda obj: obj.timestamp)
Nov 9 11:12:14 AM File "/usr/local/lib/python3.11/site-packages/theoriq/schemas/request.py", line 148, in last_item
Nov 9 11:12:14 AM ^^^^^^^^^^^^^
Nov 9 11:12:14 AM if not req.last_item or not req.last_item.blocks:
Nov 9 11:12:14 AM File "/app/server.py", line 172, in execute
Nov 9 11:12:14 AMTraceback (most recent call last):
Nov 9 11:12:14 AM2024-11-09 10:12:14,051 -<PHONE_NUMBER>71328 - server.py-server:199 - ERROR: Error processing request: can't compare offset-naiv

tyvm @okoliechykwuka for reporting the issue.

@okoliechykwuka a fix has been merged. Thank you again for reporting this issue.

You are welcome @aflament


[BUG 🐞] Dark mode toggle not working for the first time

Description
I've encountered this issue in many project which uses next-themes.
How to reproduce:

clear local storage theme
reload website
-try switching mode
It doesn't work for the first time because clearing local storage sets theme to system by default and then sets to initial theme on click.

Video:
https://github.com/warmachine028/nike/assets/103115789/e19c7925-ab8d-47aa-b2b0-65f692b9e098
Screenshots
No response
Additional information
Make sure to read the CONTRIBUTING and SETUP docs before proceeding
Happy contributing. 💐
Star my other Repositories here

work on it

Sure !


Emoji support 👉😎👉 💩

Support emoji in text. Without emoji this framework is not Hipster enough.
😂😂😂

We will need a font fallback mechanism for this to work properly or rewrite the text handling somehow, though i'll defer to @Gillibald & @nc4rrillo for that subject :)

After we have migrated Direct2D1 to the highest possible version we can work on this.
The hard thing is we have to do character matching on our own because we use a TextRenderer.
Skia can support it with the help of some other libraries like Harfbuzz etc.
You can already use emojis if you use a font that supports it we just don't support character fallbacks. Skia even supports colored fonts.

Loading Emoji from OpenType font ...
I invite / recommend you to visit this https://github.com/samhocevar/emoji.wpf too.

Thanks for the link. Seeing how Typography can work in such a environment helps to hopefully get it integrated into Avalonia some time in the future. I would much prefer using Typography for all text processing. We currently don't support visual inlines that are needed for this approach.

I played a bit with Lunacy recently and the emojis were working nicely:

At first I concluded than Avalonia was supporting font Emojis but I then saw that issue. Might be interesting to see how they do it.
There seems to be some restrictions with "joint" emojis:

Fixed in #4893.


Docs for pagination: let data key be a function

Update docs per the change in https://github.com/11ty/eleventy/pull/1711 . That one must get merged first.

This can be labeled on-hold as it's waiting for a feature to be merged into 11ty.


Raises incorrect error from gem, causing an error in ActiveRecord

The Bundler bug
When requiring a gem that doesn't exist:

Bundler raises a Gem::LoadError (here)
Rubygems raises a Gem::MissingSpecError (here from here from here)

They are not directly substitutable, because they are initialized with different arguments:
Gem::LoadError.instance_method(:initialize).parameters
# => [[:rest]]

Gem::MissingSpecError.instance_method(:initialize).parameters
# => [[:req, :name], [:req, :requirement]]

The ActiveRecord bug
This causes a bug in ActiveRecord. When it fails to load the adapter, it tries to reraise the error (here).

If Bundler is loaded, it gets a Gem::LoadError, succeeds at reraising and provides the helpful  message "Could not load the 'sqlite3' Active Record adapter. Ensure that the adapter is spelled correctly in config/database.yml and that you've added the necessary adapter gem to your Gemfile."
If Bundler is not loaded, it gets a Gem::MissingSpecError, then errors while trying to reraise, causing an ArgumentError with the unhelpful "wrong number of arguments (given 1, expected 2)"

You can reproduce my error with this gist.
However, if we strip away all the layers of complexity, it's just this:
begin
  begin
    raise Gem::LoadError.new('somegem')
  rescue Gem::LoadError => err
    raise err.class, "I am a helpful message!"
  end
rescue Object
  $! # => #<Gem::LoadError: I am a helpful message!>
end

begin
  begin
    raise Gem::MissingSpecError.new('somegem', 'somerequirement')
  rescue Gem::LoadError => err
    raise err.class, "I am a helpful message!"
  end
rescue Object
  $! # => #<ArgumentError: wrong number of arguments (given 1, expected 2)>
end

Anecdote to show that it matters
I was somewhat embarrassed when I discovered this as I was showing off a gem I wrote. We assumed it was a bug in my code and I wasn't able to show the example. If I had gotten the helpful error, I would have realized I hadn't installed sqlite3 on that version of Ruby.
Fixing this will break ActiveRecord
Note that fixing this will break ActiveRecord. I know it's already broken, but this will cause the broken case to become the common case. I'll probably submit a bug report there, too, but it took a bit to debug this, so don't have time just now.
I'm not sure the best solution for ActiveRecord, they could raise it like this: raise err, "helpful message...", that will fix the error by bypassing #initialize. However, Gem::MissingSpecError overrides the message, so their helpful message won't be returned, so, IDK.
begin
  begin
    raise Gem::MissingSpecError.new('somegem', 'somerequirement')
  rescue Gem::LoadError => err
    raise err, "I am a helpful message!"
  end
rescue Object
  m = $!.method(:message)

  $!                  # => #<Gem::MissingSpecError: I am a helpful message!>
  $!.message          # => "Could not find 'somegem' (somerequirement) among 97 total gem(s)\nChecked in 'GEM_PATH=/Users/josh/.gem/ruby/2.4.1:/Users/josh/.rubies/ruby-2.4.1/lib/ruby/gems/2.4.0', execute `gem env` for more information"
  m.super_method.call # => "I am a helpful message!"

  m.source_location.tap { |f, l| break File.readlines(f)[l-1, 4] }
  # => ["    def message # :nodoc:\n",
  #     "      build_message +\n",
  #     "        \"Checked in 'GEM_PATH=\#{Gem.path.join(File::PATH_SEPARATOR)}', execute `gem env` for more information\"\n",
  #     "    end\n"]
end

I'm not sure how this is an issue with Bundler and not ActiveRecord?

Thanks for working on this figuring out this issue. This is probably an issue more for ActiveRecord then Bundler, it will need to handle this particular scenario. I suggest raising an issue with the Rails project and passing along this information.


handle train/test slices in hdf5 file for Imagenet

Two options for doing this:

three separate datasubsets (keys in the hdf5 file), one for train, one for validation, one for testing

one large hdf5 file but three subslice keys (e.g. lists of indices in to the big data file, each stored as an hdf5 array), one for train, one for validation, one for testing


[WIP] Docs: Create conceptual and procedural content for topic-to-schema mapping

Notes for reviewers:

An HTML preview is available for review here.

Although we've been calling this feature topic-to-schema mapping internally, I shifted away from that term because
there is no notion of a map (as far as I am aware) underpinning the linkages between topics and schemas. Just appropriate use of IDs (and ID strategy) in client application code. I think association works well an alternative, in the couple of cases where it's needed.

I drafted this documentation on the assumption that we will resolve the usability bug described here.

Looks great John! The only real question I had was on consistency of using "matching" or "associated" schema.

Just a few comments with minor (non)issues.

Thanks for reviewing @rkubis.

@EricWittmann @bibryam @rkubis It appears that topic-to-schema mapping is now live in production, so I'm planning to merge this PR today in preparation for publishing of the doc.


Add MINECRAFT Coingecko Token id

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: FTkj421DxbS1wajE74J34BJ5a1o9ccA97PkK6mYq9hNQ
Token Name: Synex Coin
Token Symbol: MINECRAFT
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token: https://synexcoin.dev
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_): https://www.coingecko.com/en/coins/synex-coin

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

Started a new pr


feat: added asJson methods (#563)

1. Description

1.1. Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[ ] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[ ] I have updated/added relevant examples in examples.

1.2. Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

1.3. Related Issues

Codecov Report

Merging #571 (de2d447) into main (419b23d) will increase coverage by 4.42%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #571      +/-   ##
==========================================
+ Coverage   65.30%   69.73%   +4.42%
==========================================
  Files         213      200      -13
  Lines        2061     1946     -115
==========================================
+ Hits         1346     1357      +11
+ Misses        715      589     -126

Impacted Files
Coverage Δ

...atproto/lib/src/identities/identities_service.dart
100.00% <100.00%> (ø)

...oto/lib/src/repositories/repositories_service.dart
100.00% <100.00%> (ø)

...kages/atproto/lib/src/servers/servers_service.dart
100.00% <100.00%> (ø)

packages/atproto/lib/src/sync/sync_service.dart
93.54% <100.00%> (+5.31%)
:arrow_up:

packages/xrpc/lib/src/xrpc.dart
73.33% <100.00%> (+0.45%)
:arrow_up:

... and 13 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[10.x] Add methods dumpWhen and ddWhen to Str and Collection

I believe it would be useful to have such a shortcut for dumping things especially when working in large nested arrays/objects.
usage:
// Collection / EloquentCollection

collect([1,2,3]) // or User::get()
    ->dumpWhen(fn ($items) => $items->count() === 3) // or ddWhen()
    ->toArray();

// Str
Str::of($firstName)
    ->append($lastName)
    ->dumpWhen(fn ($str) => $str->endsWith('A')) // or ddWhen()
    ->toString();

Why need add a condition for dd or dump?
It's an additional method, you can do like this:
$collect = collect([1,2,3])->toArray();

if (...) {
   dd();
}

Let's say we have n depth array of objects. While we are traversing the whole data, it would be useful to stop and check data if condition is met or not.

So, Do you think this method is helpful for most of the projects!!
I think is good for the macro in the Collection

The Enumerable@when() method accepts a third argument that runs a default callback.
Wouldn't this work the same?
$hotels = collect([
    collect(['id' => 3, 'name' => 'Sheraton', 'rating' => null]),
    collect(['id' => 4, 'name' => 'Hilton', 'rating' => 3]),
]);

$ratings = $hotels->map(fn ($hotel) => $hotel->when(
    is_null($hotel->get('rating')),
    $hotel->dd(),
    fn () => $hotel->only('id', 'rating'),
));

Although, as it is meant to be used while debugging, I would personally switch to a regular closure and use an if statement inside it.
Most IDE's have shortcuts for converting between regular closures and arrow functions.
Lastly, I know Laravel is ok with adding features on minor releases, but I am not sure if that extends to adding methods to interfaces/contracts.
Maybe, if maintainers think this is a good addition to the framework, you might need to add these methods to the base classes first, and then send a PR to add it to the Enumerable interface to 11.x.
But I am not totally sure about this.

Or even:
$hotels = collect([
    collect(['id' => 3, 'name' => 'Sheraton', 'rating' => null]),
    collect(['id' => 4, 'name' => 'Hilton', 'rating' => 3]),
]);

$ratings = $hotels
    ->map(fn ($hotel) => $hotel->only('id', 'rating'))
    ->transform(fn ($hotel) => $hotel->when(is_null($hotel->get('ratings')), fn () => $hotel->dd()));

Or terser:
$hotels = collect([
    collect(['id' => 3, 'name' => 'Sheraton', 'rating' => null]),
    collect(['id' => 4, 'name' => 'Hilton', 'rating' => 3]),
]);

$ratings = $hotels
    ->map(fn ($hotel) => $hotel->only('id', 'rating'))
    ->transform(fn ($hotel) => $hotel->get('ratings') ?? dd($hotel));

As you can see from the name of the methods, this is just a shortcut of ->when(condition, fn () => dd())

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

@monurakkaya actually the when method already has support for a Higher Order Proxy, I didn't know that.
It allows one to do this:
$hotels = collect([
    collect(['id' => 3, 'name' => 'Sheraton', 'rating' => null]),
    collect(['id' => 4, 'name' => 'Hilton', 'rating' => 3]),
]);

$ratings = $hotels->map(
    fn ($hotel) => $hotel->only('id', 'rating')
        ->when(\is_null($hotel->get('rating')))->dd()
);

I thought you'd like to know, as it seems very handy for debugging and somewhat similar to your proposal.


Theme isn't being registered

Description
I get this error:
Metro error: Unistyles: You're trying to get theme "undefined" but it wasn't registered.

  10 | }
  11 |
> 12 | const styles = StyleSheet.create(theme => ({
     |                           ^
  13 |   container: {
  14 |     backgroundColor: theme.colors.surface.primary,
  15 |     flex: 1,

However when I remove the theming options from there and reload it works. Then when I add it back in and don't do a full refresh (meaning hot reload kicks in) it works fine and the colors work as expected, so my unistyles.ts must be loaded somehow.
I use Expo Router and Unistyles v3 and used the config from the Theming section in the docs and just changed the colors, but it also won't work if i don't change anything.
Steps to Reproduce

Setup a project with Expo Router
Use the minimal config from the Theming section in the v3 docs
Use this code and apply it to a View for example:

const styles = StyleSheet.create(theme => ({
  container: {
    backgroundColor: theme.colors.surface.primary,
    flex: 1,
    justifyContent: "center",
    alignItems: "center",
  },
}));

Snack or Repository Link (Optional)
Closed source. However I am more than happy to send over code snippets for specific files, if asked to.
Unistyles Version
3.0.0-beta.1
React Native Version
0.76.3
Platforms
Web
Expo
Yes

Had a similar issue. Make sure that:

Your unistyle configuration is imported
You have an initial theme configured
Both theme AND breakpoints are set

In my case it was because I had no breakpoints configured.
StyleSheet.configure({
    settings: {
        initialTheme: 'light',
    },
    breakpoints,
    themes: appThemes
})

Same problem on my side, even though I'm doing everything as explained in the documentation
import { StyleSheet } from "react-native-unistyles";

const lightTheme = {
  colors: {
    primary: "#ff1ff4",
    secondary: "#1ff4ff",
  },
  gap: (v: number) => v * 8,
};

const darkTheme = {
  colors: {
    primary: "#aa12ff",
    secondary: "pink",
  },
  gap: (v: number) => v * 8,
};

const appThemes = {
  light: lightTheme,
  dark: darkTheme,
};

const breakpoints = {
  xs: 0,
  sm: 300,
  md: 500,
  lg: 800,
  xl: 1200,
};

type AppBreakpoints = typeof breakpoints;
type AppThemes = typeof appThemes;

declare module "react-native-unistyles" {
  export interface UnistylesThemes extends AppThemes {}
  export interface UnistylesBreakpoints extends AppBreakpoints {}
}

StyleSheet.configure({
  settings: {
    adaptiveThemes: true,
  },
  breakpoints,
  themes: appThemes,
});

Guys, you need to read docs better. For expo router there is one more requirement: https://www.unistyl.es/v3/guides/expo-router

Both theme AND breakpoints are set

In my case it was because I had no breakpoints configured.

There is no such requirement, both are optional. If that's the case then it's bug.

Had a similar issue. Make sure that:
* Your unistyle configuration is imported

* You have an initial theme configured

* **Both theme AND breakpoints are set**

In my case it was because I had no breakpoints configured.
StyleSheet.configure({
    settings: {
        initialTheme: 'light',
    },
    breakpoints,
    themes: appThemes
})

Did all of that. Just used the default config provided in the docs.

Guys, you need to read docs better. For expo router there is one more requirement: https://www.unistyl.es/v3/guides/expo-router

I'm aware and followed these steps.

I had the same issue, I was just missing the following steps:

Add a +html.tsx file to the app folder.
Add the line import '../assets/unistyles' to the newly created file.

These instructions were detailed here:  https://www.unistyl.es/v3/guides/expo-router#static-rendering
Probably worth mentioning that the expo example was pretty helpful. But it was missing the import line for it to work on the web 👍

Hey! Yes, this fixed it. I was not really sure what the +html should contain and I wasn't even aware it uses static rendering. Thank you for your help :pray:

Also I recommend importing the unistyles file in the _layout.tsx. That way you don't override any defaults and it still seems to work just fine.

Expo removed a lot of files from the SDK 52 starter. Like Babel config, +html etc. Not sure why..

I had the same problem.
Did read the expo docs.
Having a root index.js entry point as mentioned did not help.
I ended up importing unistyles config file at the root _layout file and it works (I do not use expo web).


Add bug report issue template.

Adds a bug report template similar to the one that Statamic uses to keep bugs organised, and to minimize the chance of getting bug reports that are missing information.

Thanks Jelle.


Test Gateway API v1.2 Release Candidate

Test Gateway API v1.2 Release Candidate and give feedback: https://kubernetes.slack.com/archives/CR0H13KGA/p1726530817027909.
To test:

update go.mod to point to v1.2.0-rc1 branch
make any changes necessary to go code
update conformance tests to point to v1.2.0-rc1
run conformance tests

If any conformance tests fail, triage failures and file issues. If it's an issue with NGF, file in our repo. If it's an issue with the Gateway API itself, file an issue in their repo.
If all conformance tests pass, post in the Gateway API slack channel that the release candidate looks good.

Update this discussion with the outcome of the testing: https://github.com/kubernetes-sigs/gateway-api/discussions/3349

Conformance tests passes with gateway API version v1.2.0-rc1
CONFORMANCE PROFILE
apiVersion: gateway.networking.k8s.io/v1
date: "2024-10-01T21:05:06Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.2.0-rc1
implementation:
  contact:
  - https://github.com/nginxinc/nginx-gateway-fabric/discussions/new/choose
  organization: nginxinc
  project: nginx-gateway-fabric
  url: https://github.com/nginxinc/nginx-gateway-fabric
  version: edge
kind: ConformanceReport
mode: default
profiles:
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 0
  name: GATEWAY-GRPC
  summary: Core tests succeeded.
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 33
      Skipped: 0
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 9
      Skipped: 0
    supportedFeatures:
    - GatewayPort8080
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - GatewayHTTPListenerIsolation
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteDestinationPortMatching
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRouteRequestMirror
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestTimeout
  name: GATEWAY-HTTP
  summary: Core tests succeeded. Extended tests succeeded.
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 11
      Skipped: 0
  name: GATEWAY-TLS
  summary: Core tests succeeded.


Multi Concurrent Running Localnet

Provide ability to have multiple-instances of localnet running

Summary
I recommend to use multiple VM, one per localnet.
Details
Now that we have more experience... I end up running 3x localnet simultaneously using VM (MacOS VM +  Windows 11/WSL2 VM + Linux Ubuntu host).
This is working well, particularly when the VM uses the precompiled Sui binaries (Suibase fully installed in <2 minutes and no need for a lot of assigned vCPU).
I think this is a good workaround versus having Suibase deal with all sort of conflicts (particularly, managements of "ports" for the local process).
I found the user experience also good (just click on the VM window... there is nothing needed on the CLI for the user to "switch" from one "localnet" to another).


use sudo when doing a git clean

because container creates .tox directory as root user, outside
the container, cleaning requires sudo

Refer to this link for build results (access rights to CI server needed):
https://jenkins.bigswitch.com/job/openstack_horizon_bsn_pull_req/189/


add playlist support

Add option to play a list of messages and/or audio files
Add option repeat_playlist to post_action: repeat whole playlist. repeat_message will repeat only the last item in case of a playlist.
Add option repeat_wait for an extra delay between repeated messages (in seconds).

closes #37

Is this still ongoing?


Swiper, only reload/refresh fixes display issue

Displaying 3 slides/images per view, looped, centered.
With a clean cache, Swiper starts with the last slide and misses the first to the right. Browser refresh seems to fix it: swiper starts/initializes with first slide, no blank slides remain.
The amount of images is dynamic.
UPDATE:
The issue is with the CSS we added:
.swiper-container {
width: 100%; height: 100%;
margin-left: auto; margin-right: auto;
}
.swiper-slide {
max-width: 1200px;
height: auto;
text-align: center;
line-height: 0;
}
.swiper-slide img {
height: 550px;
width: auto;
}
.swiper-slide:nth-child(1n) {
height: 550px;
width: auto;
}
Removing the very last bit (nth-child) resets the slider to always start with the first slide. But the images stop sitting next to each other, but instead are spread apart.
Created this to demonstrate a little quicker:
http://jsfiddle.net/L3b1fzh9/13/

When slidesPerView: 'auto' is used, you need to specify swiper-slide width in order to make it work correctly

Thx. Changing swiper-slide width to width: auto; and adding margin: 0 auto; is the solution. And removing .swiper-slide img and .swiper-slide:nth-child(1n) completely.


Install react-bootstrap package.

This will be needed as it is a dependency in the current template front-end.
All that needs to be added here the is the react-bootstrap package to package.json.

Please assign this task to me

Hi @manuel12
I can able to see in package.json that latest react-bootstrap which is 2.8.0 is already added in the package.json.
Could you please let me know if anything else is expected here?

@Anupam2528 @JesusC-R Yes. I've updated the package sometime ago already.
Closing as  finished.


Update battery-menubar extension

Description
Add battery cycles and health
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for the update @yarnaid 🔥
@panrafal do you mind checking this update 🙂

One last thing, do you think we can make the new metadata image look like the other, otherwise, can we take some new?

I'll update images soon

One last thing, do you think we can make the new metadata image look like the other, otherwise, can we take some new?

I've updated the images, check, please

Awesome, thanks 🔥


Generate a sample with 10-15 hospitals in the LA area

Harbor-UCLA
UCLA
LA General Medical Center
Keck Hospital
Cedars Sinai
White Memorial
Glendale Adventist
Verdugo Hospital
Arcadia USC
Good Samaritan Hospital
"maybe add a Kaiser too"
Check if you can add the two fields for facility ID to the hospital file for later post processing in format operations, or if that will mess with Synthea

Check if you can add fields to the hospital file, or if that will mess with Synthea

I made an override file with these:
Harbor-UCLA
RONALD REAGAN UCLA
LA General Medical Center
Keck Hospital
Cedars Sinai
White Memorial
Glendale Adventist
Verdugo Hospital
Good Samaritan Hospital
Arcadia USC
Kaiser - Los Angeles
I am looking for the HCAI numbers now

For Good Samaritan Hospital is it the one in LA or the one in Bakersfield?  I wasn't sure if that's the hospital we are working with and wanted it in the list for some reason or if we just want the big LA one

Ok, so this works, yay!  I have output that has the correct facility IDs now.
One hiccup though - I ran it for population 10 and got 54 patients (which is a separate issue I referenced on the call last week) with 3449 encounters.
Of these encounters, we had 27 that met the requirement to be reported in our output (i.e. filtered for type inpatient).  And of those 27, 25 were in a hospital from our list.  One of the ones that was not from a hospital was in a "primary_care_facility" from another input file for Synthea.
Diagnosis code was:
32485007	Hospital admission (procedure)
Procedure codes were:
225338004	Risk assessment (procedure)
33367005	Angiography of coronary artery (procedure)
415070008	Percutaneous coronary intervention (procedure)
433236007	Transthoracic echocardiography (procedure)

CSV from the above referenced example run:
csv_HCAIPDD_12-20-2023_1532.csv

I ran a bigger run (n=500) which resulted in 1600 records.  Attached here
csv_HCAIPDD_12-22-2023_1348.csv


Physics Bullet

Feature description
The Bullet is already integrated into atta, but we need to provide an UI to configure Bullet. Testing if it works properly with the newer atta versions is also necessary.
Tasks

[x] Validate if Bullet works
[x] Save physics configuration
[x] Better physics drawer
[x] Improve simulation stepping
[ ] Bullet configuration UI
[ ] Motor support
[ ] Examples

[ ] Basic collision example
[ ] Basic joint example
[ ] Robot motor example

Better step control, physics configuration, and collider/aabb rendering

It was necessary to perform coordinate system handedness conversion, but now the contacts are being displayed properly


Action for opening module documentation

Description of the PR
After selecting a module, an option appears to open the documentation (if exists) in the default web browser

It would be nice to have an option to open the docs in IntelliJ

It would be nice to have an option to open the docs in IntelliJ

Which one would you like to see implemented: opening in web browser or opening in IntelliJ? (Preferably not both, it forces users to make a rather pointless decision)


[BUG] helm command is not working properly.

Describe the bug
helm command is not working.
To Reproduce
Steps to reproduce the behavior:
following the guide in https://github.com/alibaba/GraphScope/blob/main/charts/graphscope/README.md
it seems doesn't work.
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

GraphScope version: v0.2.1
OS: MacOS

Additional context
I suggest we add a new action in CI for checking helm

Thanks for reporting this problem and a new action in CI will be added.
Problem Reason
Follow the debug mode of helm install, this is caused by an existence path graphscope/graphscope (case insensitive) in your current directory.


Nodeos Command Line Reference

Add the attached markdown content in a new page guides/nodeos-config-options

Nodeos Application Options:
Config Options for eosio::chain_plugin:
  --blocks-dir arg (="blocks")          the location of the blocks directory
                                        (absolute path or relative to
                                        application data dir)

  --protocol-features-dir arg (="protocol_features")
                                        the location of the protocol_features
                                        directory (absolute path or relative to
                                        application config dir)

  --checkpoint arg                      Pairs of [BLOCK_NUM,BLOCK_ID] that
                                        should be enforced as checkpoints.

  --wasm-runtime runtime                Override default WASM runtime

  --abi-serializer-max-time-ms arg (=15)
                                        Override default maximum ABI
                                        serialization time allowed in ms

  --chain-state-db-size-mb arg (=1024)  Maximum size (in MiB) of the chain
                                        state database

  --chain-state-db-guard-size-mb arg (=128)
                                        Safely shut down node when free space
                                        remaining in the chain state database
                                        drops below this size (in MiB).

  --reversible-blocks-db-size-mb arg (=340)
                                        Maximum size (in MiB) of the reversible
                                        blocks database

  --reversible-blocks-db-guard-size-mb arg (=2)
                                        Safely shut down node when free space
                                        remaining in the reverseible blocks
                                        database drops below this size (in
                                        MiB).

  --signature-cpu-billable-pct arg (=50)
                                        Percentage of actual signature recovery
                                        cpu to bill. Whole number percentages,
                                        e.g. 50 for 50%

  --chain-threads arg (=2)              Number of worker threads in controller
                                        thread pool

  --contracts-console                   print contract's output to console

  --actor-whitelist arg                 Account added to actor whitelist (may
                                        specify multiple times)

  --actor-blacklist arg                 Account added to actor blacklist (may
                                        specify multiple times)

  --contract-whitelist arg              Contract account added to contract
                                        whitelist (may specify multiple times)

  --contract-blacklist arg              Contract account added to contract
                                        blacklist (may specify multiple times)

  --action-blacklist arg                Action (in the form code::action) added
                                        to action blacklist (may specify
                                        multiple times)

  --key-blacklist arg                   Public key added to blacklist of keys
                                        that should not be included in
                                        authorities (may specify multiple
                                        times)

  --sender-bypass-whiteblacklist arg    Deferred transactions sent by accounts
                                        in this list do not have any of the
                                        subjective whitelist/blacklist checks
                                        applied to them (may specify multiple
                                        times)

  --read-mode arg (=speculative)        Database read mode ("speculative",
                                        "head", "read-only", "irreversible").
                                        In "speculative" mode: database
                                        contains state changes by transactions
                                        in the blockchain up to the head block
                                        as well as some transactions not yet
                                        included in the blockchain.
                                        In "head" mode: database contains state
                                        changes by only transactions in the
                                        blockchain up to the head block;
                                        transactions received by the node are
                                        relayed if valid.
                                        In "read-only" mode: (DEPRECATED: see
                                        p2p-accept-transactions &
                                        api-accept-transactions) database
                                        contains state changes by only
                                        transactions in the blockchain up to
                                        the head block; transactions received
                                        via the P2P network are not relayed and
                                        transactions cannot be pushed via the
                                        chain API.
                                        In "irreversible" mode: database
                                        contains state changes by only
                                        transactions in the blockchain up to
                                        the last irreversible block;
                                        transactions received via the P2P
                                        network are not relayed and
                                        transactions cannot be pushed via the
                                        chain API.

  --api-accept-transactions arg (=1)    Allow API transactions to be evaluated
                                        and relayed if valid.

  --validation-mode arg (=full)         Chain validation mode ("full" or
                                        "light").
                                        In "full" mode all incoming blocks will
                                        be fully validated.
                                        In "light" mode all incoming blocks
                                        headers will be fully validated;
                                        transactions in those validated blocks
                                        will be trusted

  --disable-ram-billing-notify-checks   Disable the check which subjectively
                                        fails a transaction if a contract bills
                                        more RAM to another account within the
                                        context of a notification handler (i.e.
                                        when the receiver is not the code of
                                        the action).

  --maximum-variable-signature-length arg (=16384)
                                        Subjectively limit the maximum length
                                        of variable components in a variable
                                        legnth signature to this size in bytes

  --trusted-producer arg                Indicate a producer whose blocks
                                        headers signed by it will be fully
                                        validated, but transactions in those
                                        validated blocks will be trusted.

  --database-map-mode arg (=mapped)     Database map mode ("mapped", "heap", or
                                        "locked").
                                        In "mapped" mode database is memory
                                        mapped as a file.
                                        In "heap" mode database is preloaded in
                                        to swappable memory.
                                        In "locked" mode database is preloaded
                                        and locked in to memory.

Command Line Options for eosio::chain_plugin:
  --genesis-json arg                    File to read Genesis State from

  --genesis-timestamp arg               override the initial timestamp in the
                                        Genesis State file

  --print-genesis-json                  extract genesis_state from blocks.log
                                        as JSON, print to console, and exit

  --extract-genesis-json arg            extract genesis_state from blocks.log
                                        as JSON, write into specified file, and
                                        exit

  --print-build-info                    print build environment information to
                                        console as JSON and exit

  --extract-build-info arg              extract build environment information
                                        as JSON, write into specified file, and
                                        exit

  --fix-reversible-blocks               recovers reversible block database if
                                        that database is in a bad state

  --force-all-checks                    do not skip any checks that can be
                                        skipped while replaying irreversible
                                        blocks

  --disable-replay-opts                 disable optimizations that specifically
                                        target replay

  --replay-blockchain                   clear chain state database and replay
                                        all blocks

  --hard-replay-blockchain              clear chain state database, recover as
                                        many blocks as possible from the block
                                        log, and then replay those blocks

  --delete-all-blocks                   clear chain state database and block
                                        log

  --truncate-at-block arg (=0)          stop hard replay / block log recovery
                                        at this block number (if set to
                                        non-zero number)

  --import-reversible-blocks arg        replace reversible block database with
                                        blocks imported from specified file and
                                        then exit

  --export-reversible-blocks arg        export reversible block database in
                                        portable format into specified file and
                                        then exit

  --snapshot arg                        File to read Snapshot State from

Config Options for eosio::history_plugin:

  -f [ --filter-on ] arg                Track actions which match
                                        receiver:action:actor. Actor may be
                                        blank to include all. Action and Actor
                                        both blank allows all from Recieiver.
                                        Receiver may not be blank.

  -F [ --filter-out ] arg               Do not track actions which match
                                        receiver:action:actor. Action and Actor
                                        both blank excludes all from Reciever.
                                        Actor blank excludes all from
                                        reciever:action. Receiver may not be
                                        blank.

Config Options for eosio::http_client_plugin:
  --https-client-root-cert arg          PEM encoded trusted root certificate
                                        (or path to file containing one) used
                                        to validate any TLS connections made.
                                        (may specify multiple times)

  --https-client-validate-peers arg (=1)
                                        true: validate that the peer
                                        certificates are valid and trusted,
                                        false: ignore cert errors

Config Options for eosio::http_plugin:
  --unix-socket-path arg                The filename (relative to data-dir) to
                                        create a unix socket for HTTP RPC; set
                                        blank to disable.

  --http-server-address arg (=<IP_ADDRESS>:8888)
                                        The local IP and port to listen for
                                        incoming http connections; set blank to
                                        disable.

  --https-server-address arg            The local IP and port to listen for
                                        incoming https connections; leave blank
                                        to disable.

  --https-certificate-chain-file arg    Filename with the certificate chain to
                                        present on https connections. PEM
                                        format. Required for https.

  --https-private-key-file arg          Filename with https private key in PEM
                                        format. Required for https

  --https-ecdh-curve arg (=secp384r1)   Configure https ECDH curve to use:
                                        secp384r1 or prime256v1

  --access-control-allow-origin arg     Specify the Access-Control-Allow-Origin
                                        to be returned on each request.

  --access-control-allow-headers arg    Specify the Access-Control-Allow-Header
                                        s to be returned on each request.

  --access-control-max-age arg          Specify the Access-Control-Max-Age to
                                        be returned on each request.

  --access-control-allow-credentials    Specify if Access-Control-Allow-Credent
                                        ials: true should be returned on each
                                        request.

  --max-body-size arg (=1048576)        The maximum body size in bytes allowed
                                        for incoming RPC requests

  --http-max-bytes-in-flight-mb arg (=500)
                                        Maximum size in megabytes http_plugin
                                        should use for processing http
                                        requests. 503 error response when
                                        exceeded.

  --http-max-response-time-ms arg (=30) Maximum time for processing a request.

  --verbose-http-errors                 Append the error log to HTTP responses

  --http-validate-host arg (=1)         If set to false, then any incoming
                                        "Host" header is considered valid

  --http-alias arg                      Additionaly acceptable values for the
                                        "Host" header of incoming HTTP
                                        requests, can be specified multiple
                                        times.  Includes http/s_server_address
                                        by default.

  --http-threads arg (=2)               Number of worker threads in http thread
                                        pool

Config Options for eosio::login_plugin:
  --max-login-requests arg (=1000000)   The maximum number of pending login
                                        requests

  --max-login-timeout arg (=60)         The maximum timeout for pending login
                                        requests (in seconds)

Config Options for eosio::mongo_db_plugin:

  -q [ --mongodb-queue-size ] arg (=1024)
                                        The target queue size between nodeos
                                        and MongoDB plugin thread.

  --mongodb-abi-cache-size arg (=2048)  The maximum size of the abi cache for
                                        serializing data.

  --mongodb-wipe                        Required with --replay-blockchain,
                                        --hard-replay-blockchain, or
                                        --delete-all-blocks to wipe mongo
                                        db.This option required to prevent
                                        accidental wipe of mongo db.

  --mongodb-block-start arg (=0)        If specified then only abi data pushed
                                        to mongodb until specified block is
                                        reached.

  -m [ --mongodb-uri ] arg              MongoDB URI connection string, see:
                                        https://docs.mongodb.com/master/referen
                                        ce/connection-string/. If not specified
                                        then plugin is disabled. Default
                                        database 'EOS' is used if not specified
                                        in URI. Example: mongodb://<IP_ADDRESS>:27
                                        017/EOS

  --mongodb-update-via-block-num arg (=0)
                                        Update blocks/block_state with latest
                                        via block number so that duplicates are
                                        overwritten.

  --mongodb-store-blocks arg (=1)       Enables storing blocks in mongodb.

  --mongodb-store-block-states arg (=1) Enables storing block state in mongodb.

  --mongodb-store-transactions arg (=1) Enables storing transactions in
                                        mongodb.

  --mongodb-store-transaction-traces arg (=1)
                                        Enables storing transaction traces in
                                        mongodb.

  --mongodb-store-action-traces arg (=1)
                                        Enables storing action traces in
                                        mongodb.

  --mongodb-expire-after-seconds arg (=0)
                                        Enables expiring data in mongodb after
                                        a specified number of seconds.

  --mongodb-filter-on arg               Track actions which match
                                        receiver:action:actor. Receiver,
                                        Action, & Actor may be blank to include
                                        all. i.e. eosio:: or :transfer:  Use *
                                        or leave unspecified to include all.

  --mongodb-filter-out arg              Do not track actions which match
                                        receiver:action:actor. Receiver,
                                        Action, & Actor may be blank to exclude
                                        all.

Config Options for eosio::net_plugin:
  --p2p-listen-endpoint arg (=<IP_ADDRESS>:9876)
                                        The actual host:port used to listen for
                                        incoming p2p connections.

  --p2p-server-address arg              An externally accessible host:port for
                                        identifying this node. Defaults to
                                        p2p-listen-endpoint.

  --p2p-peer-address arg                The public endpoint of a peer node to
                                        connect to. Use multiple
                                        p2p-peer-address options as needed to
                                        compose a network.
                                          Syntax: host:port[:<trx>|<blk>]
                                          The optional 'trx' and 'blk'
                                        indicates to node that only
                                        transactions 'trx' or blocks 'blk'
                                        should be sent.  Examples:
                                            p2p.eos.io:9876
                                            p2p.trx.eos.io:9876:trx
                                            p2p.blk.eos.io:9876:blk

  --p2p-max-nodes-per-host arg (=1)     Maximum number of client nodes from any
                                        single IP address

  --p2p-accept-transactions arg (=1)    Allow transactions received over p2p
                                        network to be evaluated and relayed if
                                        valid.

  --agent-name arg (="EOS Test Agent")  The name supplied to identify this node
                                        amongst the peers.

  --allowed-connection arg (=any)       Can be 'any' or 'producers' or
                                        'specified' or 'none'. If 'specified',
                                        peer-key must be specified at least
                                        once. If only 'producers', peer-key is
                                        not required. 'producers' and
                                        'specified' may be combined.

  --peer-key arg                        Optional public key of peer allowed to
                                        connect.  May be used multiple times.

  --peer-private-key arg                Tuple of [PublicKey, WIF private key]
                                        (may specify multiple times)

  --max-clients arg (=25)               Maximum number of clients from which
                                        connections are accepted, use 0 for no
                                        limit

  --connection-cleanup-period arg (=30) number of seconds to wait before
                                        cleaning up dead connections

  --max-cleanup-time-msec arg (=10)     max connection cleanup time per cleanup
                                        call in millisec

  --net-threads arg (=2)                Number of worker threads in net_plugin
                                        thread pool

  --sync-fetch-span arg (=100)          number of blocks to retrieve in a chunk
                                        from any individual peer during
                                        synchronization

  --use-socket-read-watermark arg (=0)  Enable experimental socket read
                                        watermark optimization

  --peer-log-format arg (=["${_name}" ${_ip}:${_port}])
                                        The string used to format peers when
                                        logging messages about them.  Variables
                                        are escaped with ${<variable name>}.
                                        Available Variables:
                                           _name  self-reported name

                                           _id    self-reported ID (64 hex
                                                  characters)

                                           _sid   first 8 characters of
                                                  _peer.id

                                           _ip    remote IP address of peer

                                           _port  remote port number of peer

                                           _lip   local IP address connected to
                                                  peer

                                           _lport local port number connected
                                                  to peer

Config Options for eosio::producer_plugin:
  -e [ --enable-stale-production ]      Enable block production, even if the
                                        chain is stale.

  -x [ --pause-on-startup ]             Start this node in a state where
                                        production is paused

  --max-transaction-time arg (=30)      Limits the maximum time (in
                                        milliseconds) that is allowed a pushed
                                        transaction's code to execute before
                                        being considered invalid

  --max-irreversible-block-age arg (=-1)
                                        Limits the maximum age (in seconds) of
                                        the DPOS Irreversible Block for a chain
                                        this node will produce blocks on (use
                                        negative value to indicate unlimited)

  -p [ --producer-name ] arg            ID of producer controlled by this node
                                        (e.g. inita; may specify multiple
                                        times)

  --private-key arg                     (DEPRECATED - Use signature-provider
                                        instead) Tuple of [public key, WIF
                                        private key] (may specify multiple
                                        times)
  --signature-provider arg (=EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV=KEY:5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3)
                                        Key=Value pairs in the form
                                        <public-key>=<provider-spec>
                                        Where:
                                           <public-key>    is a string form of
                                                           a vaild EOSIO public
                                                           key

                                           <provider-spec> is a string in the
                                                           form <provider-type>
                                                           :<data>

                                           <provider-type> is KEY, or KEOSD

                                           KEY:<data>      is a string form of
                                                           a valid EOSIO
                                                           private key which
                                                           maps to the provided
                                                           public key

                                           KEOSD:<data>    is the URL where
                                                           keosd is available
                                                           and the approptiate
                                                           wallet(s) are
                                                           unlocked

  --keosd-provider-timeout arg (=5)     Limits the maximum time (in
                                        milliseconds) that is allowed for
                                        sending blocks to a keosd provider for
                                        signing

  --greylist-account arg                account that can not access to extended
                                        CPU/NET virtual resources

  --greylist-limit arg (=1000)          Limit (between 1 and 1000) on the
                                        multiple that CPU/NET virtual resources
                                        can extend during low usage (only
                                        enforced subjectively; use 1000 to not
                                        enforce any limit)

  --produce-time-offset-us arg (=0)     Offset of non last block producing time
                                        in microseconds. Valid range 0 ..
                                        -block_time_interval.

  --last-block-time-offset-us arg (=-200000)
                                        Offset of last block producing time in
                                        microseconds. Valid range 0 ..
                                        -block_time_interval.

  --cpu-effort-percent arg (=80)        Percentage of cpu block production time
                                        used to produce block. Whole number
                                        percentages, e.g. 80 for 80%

  --last-block-cpu-effort-percent arg (=80)
                                        Percentage of cpu block production time
                                        used to produce last block. Whole
                                        number percentages, e.g. 80 for 80%

  --max-block-cpu-usage-threshold-us arg (=5000)
                                        Threshold of CPU block production to
                                        consider block full; when within
                                        threshold of max-block-cpu-usage block
                                        can be produced immediately

  --max-block-net-usage-threshold-bytes arg (=1024)
                                        Threshold of NET block production to
                                        consider block full; when within
                                        threshold of max-block-net-usage block
                                        can be produced immediately

  --max-scheduled-transaction-time-per-block-ms arg (=100)
                                        Maximum wall-clock time, in
                                        milliseconds, spent retiring scheduled
                                        transactions in any block before
                                        returning to normal transaction
                                        processing.

  --subjective-cpu-leeway-us arg (=31000)
                                        Time in microseconds allowed for a
                                        transaction that starts with
                                        insufficient CPU quota to complete and
                                        cover its CPU usage.

  --incoming-defer-ratio arg (=1)       ratio between incoming transactions and
                                        deferred transactions when both are
                                        queued for execution

  --incoming-transaction-queue-size-mb arg (=1024)
                                        Maximum size (in MiB) of the incoming
                                        transaction queue. Exceeding this value
                                        will subjectively drop transaction with
                                        resource exhaustion.

  --producer-threads arg (=2)           Number of worker threads in producer
                                        thread pool

  --snapshots-dir arg (="snapshots")    the location of the snapshots directory
                                        (absolute path or relative to
                                        application data dir)

Config Options for eosio::state_history_plugin:

  --state-history-dir arg (="state-history")
                                        the location of the state-history
                                        directory (absolute path or relative to
                                        application data dir)

  --trace-history                       enable trace history

  --chain-state-history                 enable chain state history

  --state-history-endpoint arg (=<IP_ADDRESS>:8080)
                                        the endpoint upon which to listen for
                                        incoming connections. Caution: only
                                        expose this port to your internal
                                        network.

  --trace-history-debug-mode            enable debug mode for trace history

Command Line Options for eosio::state_history_plugin:
  --delete-state-history                clear state history files

Config Options for eosio::trace_api_plugin:
  --trace-dir arg (="traces")           the location of the trace directory
                                        (absolute path or relative to
                                        application data dir)

  --trace-slice-stride arg (=10000)     the number of blocks each "slice" of
                                        trace data will contain on the
                                        filesystem

  --trace-minimum-irreversible-history-blocks arg (=-1)
                                        Number of blocks to ensure are kept
                                        past LIB for retrieval before "slice"
                                        files can be automatically removed.
                                        A value of -1 indicates that automatic
                                        removal of "slice" files will be turned
                                        off.

  --trace-minimum-uncompressed-irreversible-history-blocks arg (=-1)
                                        Number of blocks to ensure are
                                        uncompressed past LIB. Compressed
                                        "slice" files are still accessible but
                                        may carry a performance loss on
                                        retrieval
                                        A value of -1 indicates that automatic
                                        compression of "slice" files will be
                                        turned off.

  --trace-rpc-abi arg                   ABIs used when decoding trace RPC
                                        responses.
                                        There must be at least one ABI
                                        specified OR the flag trace-no-abis
                                        must be used.
                                        ABIs are specified as "Key=Value" pairs
                                        in the form <account-name>=<abi-def>
                                        Where <abi-def> can be:
                                           an absolute path to a file
                                        containing a valid JSON-encoded ABI
                                           a relative path from `data-dir` to a
                                        file containing a valid JSON-encoded
                                        ABI

  --trace-no-abis                       Use to indicate that the RPC responses
                                        will not use ABIs.
                                        Failure to specify this option when
                                        there are no trace-rpc-abi
                                        configuations will result in an Error.
                                        This option is mutually exclusive with
                                        trace-rpc-api

Config Options for eosio::txn_test_gen_plugin:
  --txn-reference-block-lag arg (=0)    Lag in number of blocks from the head
                                        block when selecting the reference
                                        block for transactions (-1 means Last
                                        Irreversible Block)

  --txn-test-gen-threads arg (=2)       Number of worker threads in
                                        txn_test_gen thread pool

  --txn-test-gen-account-prefix arg (=txn.test.)
                                        Prefix to use for accounts generated
                                        and used by this plugin

Application Config Options:
  --plugin arg                          Plugin(s) to enable, may be specified
                                        multiple times

Application Command Line Options:
  -h [ --help ]                         Print this help message and exit.

  -v [ --version ]                      Print version information.

  --full-version                        Print full version information.

  --print-default-config                Print default configuration template

  -d [ --data-dir ] arg                 Directory containing program runtime
                                        data

  --config-dir arg                      Directory containing configuration
                                        files such as config.ini

  -c [ --config ] arg (=config.ini)     Configuration file name relative to
                                        config-dir

  -l [ --logconf ] arg (=logging.json)  Logging configuration file name/path
                                        for library users

@AngeloCG97  I noticed this page is still missing on the english site
https://guias.eoscostarica.io/docs/herramientas/opciones-configuracion-nodeos


kdePackages.plasma-mobile: fix

Dirty hotfix closing https://github.com/NixOS/nixpkgs/issues/316958.
CC @NixOS/qt-kde, this is very ugly and I've no idea if there's a clean way to solve the cause rather than the symptom.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

That's probably fine tbh.


Fix bug in overwrite when using schema-qualified table names

This patch fixes #97, an issue where using SaveMode.Overwrite with schema-qualified table names (such as my_schema.my_table) would lead to "Invalid operation: syntax error at or near ".";" messages from Redshift.
The problem is that the ALTER TABLE ... RENAME command only accepts unqualified table names as the new names, so we need to strip off the schema prior to performing the renaming.
In order to keep this code clean, this patch introduces a new TableName case class which manages all of the escaping and parsing logic for table names, then uses that class to fix the Overwrite issue.

/cc @cfeduke

My experience in working with a wrapper for TableName makes me want to use similar wrappers to automatically handle column name quoting in the other parts of spark-redshift. I'll leave that refactoring to future work, though.

Current coverage is 94.73%

Merging #102 into master will decrease coverage by -0.08% as of 698d546

@@            master    #102   diff @@
======================================
  Files           11      12     +1
  Stmts          444     475    +31
  Branches       109     116     +7
  Methods          0       0
======================================
+ Hit            421     450    +29
  Partial          0       0
- Missed          23      25     +2

Review entire Coverage Diff as of 698d546

Powered by Codecov. Updated on successful CI builds.

LGTM


Testing on deed page: swap donation ask for email sign up

@mattl will you provide status update?

Waiting on Trilogy.

I'm guessing we're not doing this now.


Add more infoview tests.

Tried to be exhaustive with this; let me know if I missed anything.

(sorry for accidentally making this branch on upstream - was messing around with Github CLI)

(sorry for accidentally making this branch on upstream - was messing around with Github CLI)

Nah no big deal, either way's fine.

Nice. Thanks!

Nice. Thanks!
Something odd is happening in one of the tests I think though -- it happens both locally and I see in CI:
https://github.com/Julian/lean.nvim/runs/2834969873?check_suite_focus=true#step:10:102
See how it says there's an error? But it's clearly exiting with successful exit status... No idea what's up there. Any chance you see it?

See how it says there's an error? But it's clearly exiting with successful exit status... No idea what's up there. Any chance you see it?

Good catch - turns out we were't giving the Lean 4 server enough time to start up. I didn't notice this locally because I had manually set a larger timeout. Should be fixed now.

The reason the error wasn't caught is because I put failing code inside of a describe block, rather than an it block. Fixed - though the real solution would be to use Busted's setup function. But it looks like plenary.nvim doesn't provide this yet.

OK I gave up and wrote myself a poor man's elan so never mind that comment (though who knows, it may still be useful).

I combined the files into one which I think makes it a bit easier to find what's where, but other than that think lgtm, will merge as soon as CI finishes.

Hmm are these still running in separate nvim instances? I put them in separate files I thought this was necessary for separate instances. Otherwise we'd be running helpers.setup more than once in a single instance, and these would be less like unit tests.

AFAIK multiple files vs one files doesn't affect that really (there's some parallelization, but stuff can run in the same nvim).
So, it's always dirty (which of course is nonideal), and yes we're calling enable multiple times in the same nvim, but I think we could have been doing so previously as well.

From nvim-lua/plenary.nvim:

It will search for files with the pattern *_spec.lua and execute them in parallel in separate neovim instances.

Haven't looked into the code myself, but you're saying this line isn't entirely accurate?

Never mind, it seems you're correct that plenary is mapping separate instances for each file: https://github.com/nvim-lua/plenary.nvim/blob/816d6c62bd020c0b29102be0890edb0c9e072373/lua/plenary/test_harness.lua#L70-L77
That's a bit unfortunate... but ok will revert.

Merged, thanks again.


Expose the condition parameter from the underlying Mount in Image.copy_local_file

The Image.copy_local_file function is just a thin wrapper around a Mount, which has a "condition" concept that operates analogously (although inversely) to a Docker ignore file. This PR exposes the underlying condition so users don't need to instantiate a Mount directly just to leverage that feature.
Note that I think that condition being an inclusion criterion is arguably confusing since most people find themselves looking for an ignore operation. Not sure what to do about that, though, besides trying to document it well.
Changelog

The Image.copy_local_dir method now has a condition parameter, which can be used to select the files that should get copied.

After discussion on Slack, I think it's preferably to hold off on committing to an API for filtering in Image methods. Users can use the more verbose Image.copy_mount(Mount.from_local_dir("data/", condition=...)) in the meantime.


ENH: Call the DWI plot method from nireports

Call the DWI plot method from its new location in nireports.

Depends on https://github.com/nipreps/nireports/pull/101 and a new release of nireports.

Please change from draft to "ready for review" if it is ready.

OK, I see that nireports is not pinned, and since a new release was made with this, this is ready to go.


Nested $refs return wrong schemaPath

This is about ajv 6.0.0, any options.
If a $ref to a definition contains another, nested $ref, schemaPath seems to refer to the root of current schema instead of the document as a whole. There's no way to then get the full schema path to the error, which is what I need.
JSON Schema
{
  "$schema": "http://json-schema.org/draft-06/schema#",

  "definitions": {
    "address": {
      "type": "object",
      "properties": {
        "street_number":  { "$ref": "#/definitions/number" },
        "street_address": { "type": "string" },
        "city":           { "type": "string" },
        "state":          { "type": "string" }
      },
      "required": ["street_number", "street_address", "city", "state"]
    },
    "number": {
      "type": "number"
    }
  },

  "type": "object",

  "properties": {
    "billing_address": { "$ref": "#/definitions/address" },
    "shipping_address": {
      "allOf": [
        { "$ref": "#/definitions/address" },
        { "properties":
          { "type": { "enum": [ "residential", "business" ] } },
          "required": ["type"]
        }
      ]
    }
  }
}

Sample data
{
  "shipping_address": {
    "street_address": "1600 Pennsylvania Avenue NW",
    "city": "Washington",
    "state": "DC",
    "type": "business"
  }
}

Your code
(using ajv-cli for this test)
Validation result, data AFTER validation, error messages
simple_data.json invalid
[ { keyword: 'required',
    dataPath: '.shipping_address',
    schemaPath: '#/required',
    params: { missingProperty: 'street_number' },
    message: "should have required property 'street_number'" } ]

What results did you expect?
I expected the schemaPath to be like #/properties/shipping_address/allOf/0/required, instead it points erroneously to #/required. This problem only occurs with nested $refs, which my full schema happens to have a lot of.
Are you going to resolve the issue?
I can have a quick look if this is an easy fix, but it would be a lot easier for someone with some understanding of the inner workings of the ajv reference and id resolver to come up with a suitable fix.

duplicate of #512


Clean up for the new domain name changes.

Issue #: 15877
Description of changes:

Clean up unused files;
Enable cloud build PR review feature;
Move firebase and cloud build configuration to UI CD flow in bcregisty-sre repo;
Update environment variables' value;

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

/gcbrun

Temporary Url for review: https://business-create-dev--pr-535-n8znx2hk.web.app

/gcbrun

Temporary Url for review: https://business-create-dev--pr-535-n8znx2hk.web.app


I want to support micromdm How to start kmfddm

I want to support micromdm How to start kmfddm

Follow along with the Guide: https://github.com/jessepeterson/kmfddm/blob/main/docs/quickstart.md :)
Instead of starting NanoMDM, use the -dm switch to MicroMDM.

Follow along with the Guide: https://github.com/jessepeterson/kmfddm/blob/main/docs/quickstart.md :)
Instead of starting NanoMDM, use the -dm switch to MicroMDM.

-enqueue-key   What should I fill in for this parameter?

-enqueue-key -enqueue What should I fill in for this parameter?

These are the API key for MicroMDM and the API URL for submitting commands: usually /v1/commands of your MicroMDM server.

-enqueue-key -enqueue What should I fill in for this parameter?

These are the API key for MicroMDM and the API URL for submitting commands: usually /v1/commands of your MicroMDM server.

thank you


The requested URL was rejected. Please consult with your administrator

After successful Nagad payment, call back URL not working and browser showing me this error in live mode The requested URL was rejected. Please consult with your administrator.

I've contacted Nagad with a callback URL and support id which was the browser showing me with an error. Now Nagad fixed that issue.


compileSdkVersion 22 fails

I'd love to use your library but when I include it in gradle I fail the gradle sync with compileSdkVersion 22.
It works if I use compileSdkVersion 23 but I currently have no time to adapt to all the changes in Marsmallow. Is there anyway of getting around this?

Interesting, to be honest, I don't know what are the implications of lowering the target SDK version...
How will it affect existing devs?
How do other libraries handle it? Looking at another popular cropping library it also targets 24...
It is very easy for you to just fork it and change only this value.

@stefanb22 You should clone the project. Then decrease the compileSdkVersion to 22 and add the "cropper" as a module.

@sunshinetpu I know it is always an option to clone a project, but is it the correct option to use in you opinion?


Opening solution in Visual Studio 2015 with NodeJS Tools breaks TS build

Category

[x] Question
[ ] Bug
[ ] Enhancement

Observed Behavior
I tried opening and running a new project (Drop 6) in Visual Studio with NodeJS Tools installed.
When running the gulp serve command however, I receive lots and lots of Typescript errors.
I tried investigating the issue myself, and I noticed that when opening the project in Visual Studio, an index.d.ts file is generated in the typings directory, with the following content, along with the globals directory and its content:
/// <reference path="globals/gulp/index.d.ts" />
/// <reference path="globals/node/index.d.ts" />
/// <reference path="globals/react-dom/index.d.ts" />
/// <reference path="globals/react/index.d.ts" />

Is this something I can disable? Removing the index.d.ts file fixes the gulp command, but I can't be expected to do this everytime I (or someone else) open the project...
Executing with gulp serve --verbose produces the following output:
http://pastebin.com/SkggPTPN
Steps to Reproduce

Create a new project with yo generator
Open the project in Visual Studio 2015 with NodeJS tools installed
Run gulp serve either from VS Task Runner Explorer or command line

(Copy of issue https://github.com/SharePoint/sp-dev-fx-webparts/issues/72)

@Trickass There seems to be some issues with Visual Studio and TypeScript. Visual Studio by default is looking for the TypeScript installed by Visual Studio and not what the web project is using. So, this is creating issues within Visual Studio.
At this point, I think this is an issue with Visual Studio and discuss with the Visual Studio Community.

Thank you @chakkaradeep I'll see if I can post an issue there. Doesn't sound like an easy fix then? :)

@Trickass I tried working through them and I was not able to. On the other hand, open it in VS Code and everything works! ;)

@Trickass This is a royal PITA when it comes to NodeJS & Visual Studio. VS's Node tools installs it's own version of Node so when it runs from VS, it uses that one. Drives me nuts. When you use VSCode, it's using the one on your system... so effectively you have two node installs.
You can see where your global node modules are from each environment. In a normal command prompt & in a VS Dev Command prompt run npm help. The last line shows the location of NPM... one folder up is the path of the globally installed packages. I bet you get two different experiences.
You can also check the TypeScript version in each command prompt. Run tsc -v in each command prompt to check. I bet the VS Command Prompt shows something <v2. Once you know where you are, you can verify which one you need to upgrade.
Thank help?

Visual Studio 2015 – How to update NodeJS and/or NPM to their latest version mentioned how to use the latest node.js from your VS. By following those steps, you can make sure your VS are using a consistent node.js.
what I figured out was that I had to use VS for code editing and rely on the browser's debug feature to debug code because the auto generated SPfx code somehow were broken when you simply pressed F5 in VS even though you followed the import project as node.js project from dev.office.com.

@chakkaradeep VS Code indeed works well. Only issue I have with using it, is that we use TFS instead of GIT in our team at the moment. For now I simply check in using VS, and develop using VS Code, but would be easier if I either make VS work, or VSCode has TFS support :)
@frankchen76 I'll check out the links you provided!

@NickSevens there seems to be a TFS extension for VS Code. May be that could work?
Let us know if the suggestions in this thread works. If you have already started a discussion on the VS forum, then please add a link reference to that discussion here and feel free to close this issue.
Thanks!

It appears the index.d.ts file is not generated when importing the project (as described in the link of @frankchen76), which allows me to run the project.
For me this is resolved :)