Feature | latest mkdocs + releases and version sections + cloudtrail update

What?
Commits on Jul 8, 2022

pointing to latest makefiles lib version to use material mkdocs 8.3.9 - @exequielrafaela
Necessary updates to css styles for material mkdocs version 8.3.9 - @exequielrafaela
fixing landing "why tech stack" hyperlink - @exequielrafaela
Updating mkdocs.yml with extra needed markdown_extentions + Releases sections routes - @exequielrafaela
releases and versions related sections added - @exequielrafaela
updating how-it-works features security services cloudtrail section - @exequielrafaela
Merge branch 'master' into feature/how-it-works-cloudtrail-update - @exequielrafaela
fixing user-guide leverage cli terraform command info box text format - @exequielrafaela

Why?

Upgrading material mkdocs version
Updating Cloudtrail section to meet the std format
Pending to publish Release, version and compatibility matrix section

@angelofenoglio everything ready for re-review when possible. As agreed after you resolve all the conversations and approve the PR I'll proceed to merge.
Thanks for your collab!
CC: @binbashar/leverage-ref-architecture-aws-admin @binbashar/leverage-ref-architecture-aws-dev


lowest option price as main price

Hi, how do I make a item with a 0 price show the lowest option price as the main price, so for a item it will show FROM £lowest option price so for example FROM £3.00

Could you provide some more information around which field are you referring to? Maybe a screenshot of the field will help.

Hi
So sorry I managed to get it sorted in the end
From: shivamriky<EMAIL_ADDRESS>Sent: 01 March 2017 15:17
To: tastyigniter/TastyIgniter
Cc: ianhaney; Author
Subject: Re: [tastyigniter/TastyIgniter] lowest option price as main price (#157)
Hello! Any updates?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tastyigniter/TastyIgniter/issues/157#issuecomment-283368385 , or mute the thread https://github.com/notifications/unsubscribe-auth/APl3pSTRzDUYu-o1L9SRuDdZ6VQnRbUaks5rhYv2gaJpZM4L3OJH .  https://github.com/notifications/beacon/APl3pQdBZ1IC1hrPIyKeHmZor4VnTFyIks5rhYv2gaJpZM4L3OJH.gif

Hi
I need help with this again as building another food ordering website and can't find the developer who did the work for me
The link is https://www.broadwaymediadesigns.co.uk/sites/fastfoodparadise/index.php/


Added Hologram platofrm

Very nice platform, used them for a couple of projects, lots of integration.

@botto thank you


PersistGate integration

Hi!,
I read in the issues, that there is no integration with redux-persist v5.
But is it possible to use the PersistGate for blocking my UI to render before the store is rehydrated?

There is still an issue with Redux Persist v5 integration that is addressed in PRS #135 and #143, but have yet to be merged. Once that is fixed, you should be able to use v5 and <PersistGate />.
For now, with v4, you can use offlineConfig.persistCallback() to achieve the same effect.

So... any news about this ?

I think we have to use it the redux-persist v4 way: https://github.com/rt2zz/redux-persist/blob/v4.10.2/docs/recipes.md#delay-render-until-rehydration-complete
But then see https://github.com/redux-offline/redux-offline/issues/182#issuecomment-362391149 for not dispatching persist/REHYDRATE twice.

@DaniloCouto The mentioned PRs have been merged, so this should work. You will have to setup Redux Persist v5 yourself though. This library uses v4 by default.

Well, I've created my own """PersistGate""".
I created a component that holds the child components if the event 'REHYDRATE_STORE' isn't fired.
reducers/rehydrate.js
export default (state = false, action) => {
  switch (action.type) {
    case 'REHYDRATE_STORE':
      return true;
    default:
      return state;
  }
};

reducers/index.js
import { combineReducers } from 'redux';
...
import Rehydrate from './rehydrate'

export default combineReducers({
  ...
  rehydrate: Rehydrate,
  ....
});

rehydrateComponent.js
import React, { Component } from 'react';
import { View, ActivityIndicator } from 'react-native'; // yeap, I use react-native , but you get the idea.
import { connect } from 'react-redux';

class Rehydrate extends Component {
  render() {
    if (!this.props.rehydrate) {
      return (
        <View
          style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}
        >
          <ActivityIndicator size={'large'} />
        </View>
      );
    }
    return this.props.children;
  }
}

export default connect(state => {
  return {
    rehydrate: state.rehydrate
  };
})(Rehydrate);

your main js file, in my case App.js
  ....
  render() {
    return (
      <Provider store={store}>
        <Rehydrate>
           {/* Insert your nav components here, good luck */}
        </Rehydrate>
      </Provider>
    );
  }
  ...

It's a little buggy on React-native Live-reload, because sometimes the REHYDRATE_STORE event doesn't trigger.
Well, I hope I've helped someone. I'm pretty new to react.

What's the state of this? Should we be making our own PersistGate or should there be a change in redux-offline? Or are we waiting on redux-persist?

@carlosbensant's example is to redo the existing PersistGate functionality using the persistCallback (I'm assuming, it seems like that part is hidden in your configureStore). @wacii's suggestion is to setup your own persistor. Either way, you're reimplementing something these packages already implemented, which isn't ideal.
I think a solution that allows us to reuse existing work and more "plug and play" is the way to go. @pdpino's suggestion of exposing the redux-offline's persistor fits. And if they're up for making the necessary PR, then all the better!
I think we mostly need "sign off" on this (and how it's done) so that @pdpino's time isn't wasted.

@saiichihashimoto Redo? What!? Nothing has been reimplemented. You misunderstood what's @wacii suggested above.

There is still an issue with Redux Persist v5 integration that is addressed in PRS #135 and #143, but have yet to be merged. Once that is fixed, you should be able to use v5 and <PersistGate />.
For now, with v4, you can use offlineConfig.persistCallback() to achieve the same effect.

First of all, PersistGate is only available in Redux Persist v5 and this version is not officially supported by Redux Offline.
In Redux Offline, we already have a functionality to mimic the PersistGate behavior using offlineConfig.persistCallback(). This functionality is the one I'm using in my example, I'm not doing such a thing like "reimplementing something these packages already implemented.".
For clarity's sake, here is also an example of my configureStore function:
export default function configureStore( initialState, persistCallback ) {
    const rootReducer = combineReducers(reducers)
    const composeEnhancers = /* window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__ || */ compose

    return createStore(
        rootReducer,
        initialState,
        composeEnhancers(
            offline({
                ...offlineConfig,
                effect,
                discard,
                returnPromises: true,
                persistCallback: persistCallback
            }),
            applyMiddleware(
                thunk,
                logger,
                authMiddleware
            ),
        )
    )
}

Good night!

@carlosbensant Maybe I'm misunderstanding. Even with persistCallback, we can't use the <PersistGate /> that redux-persist provides, can we?

@saiichihashimoto you are talking about redux-persist v5 and @carlosbensant is talking about redux-persist v4. We allow users to disable the default redux-persist so that they can install externally the latest version. That said, we don't really maintain such solutions (yet). If you want to used the recommended approach you just need to use the persist provided by redux-offline and setup a persistCallback.


http shutdown() may lose an active connection.

What version of Go are you using (go version)?

go version go1.12.4 darwin/amd64

Does this issue reproduce with the latest release?
yes go 1.12
What operating system and processor architecture are you using (go env)?
go env Output
GOARCH="amd64"
GOBIN="/usr/local/go/bin"
GOCACHE="/var/root/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/var/root/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/ax/Desktop/ArcTestHttpServer/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build931930631=/tmp/go-build -gno-record-gcc-switches -fno-common"

my english is not very good. I try to describe it.
i found a problem in http shutdown(), when the shutdown function is executed, srv.mu.Lock() is executed. but at this time the net accept function can still be executed normally, execute c.setState(c.rwc, StateNew) put a new connection into activeConn and wait for srv.mu.Unlock().
when shutdown() finishes processing all activeConn connections, it will execute srv.mu.Unlock() and end the shutdown function, c.setState() gets the lock and puts a new connection into activeConn. At this point, there will still be an active connection after the shutdown() is completed.

I have encountered the same problem.
When Shutdown method is called, it will first close the Listener and then close all the active connections, but the code in method Serve will give a chance for a connection returned by Accept but has not been added to active connection array when shutdown is closing all the active connections, then the newly established connection will not be closed.
Parts of the codes in server.Serve:
rw, e := l.Accept()

		if e != nil {
			select {
			case <-srv.getDoneChan():
				return ErrServerClosed
			default:
			}
		// unrelated codes are ignored

		tempDelay = 0
		c := srv.newConn(rw)
               // connection will be added to arry in setState method
		c.setState(c.rwc, StateNew) // before Serve can return
		go c.serve(ctx)

As this issue pointed out:
If you want the server to shut down gracefully, you can use the Shutdown method. With that approach, you'd need to communicate the start of shutdown to the handlers by whatever mechanism you like (such as canceling a context.Context), and they can report an appropriate error explicitly.

It seems that they don't think this problem as a bug. Maybe we should set the shutdown flag before we call Shutdown method, and just return an error if a request is received after the server shutdown.

This does not look like a duplicate of #31438. Here the connection has not reached the handler yet.
This looks like it might be a bug.

@FiloSottile, @andybons, if this is a bug report about Go 1.12, how is this a release blocker for Go 1.14?

Hm. I didn’t notice that. Will remove release-blocker for now pending more context from @FiloSottile.

Hello all,
I, too, find the Shutdown() method counter intuitive. From the documentation I got an impression that when it is called, the server will wait for all handler goroutines to complete, gracefully close the open connections and after that return.
But in fact, none of this is true for me. Open connections are interrupted, no waiting whatsoever happens. There is nothing graceful as compared to Close()!


Using of Ecma 2015 export/import throws error

i'm trying to use postscrib in an sdk i'm creating , it works very good, but when i try to add export class or import statements it fails, i overcome this by using other way of export, but i'm loosing all the power of class in ecma 2015, is there away to over come this?
This the error i get: Uncaught SyntaxError: Unexpected token export
the trace:
Uncaught Error: Script error. - : 0
at Object.error (cro:170)
at active.win.onerror (cro:244)

It's really hard to help with no code provided.


Cache request

Hello,  i would like to program a cache in the api gateway for an specific route. When the api gateway receive a call for a service A for example, the first time the request will be the real to the service A but the second time i want to get the cache from the apigateway and return to the client the cached response if the request is the same. It's possible with a global filter? do you have any example?
I aprecciate so much your help.

Duplicates #1719


Query for IS NOT NULL

Chances are I'm missing this somewhere in the docs but is there a way to check if a field IS NOT NULL?
Trying jsonb_where(:data, date: "IS NOT NULL") results in literal use of "IS NOT NULL" as a string. Trying !nil naturally results in a check for true.

To my knowledge, not queries aren't currently supported. I don't think it would take too much work to get them going though.

@adambedford We've added a few scopes to address this in version 1.0.0.beta.3. Hope they help!

@crismali Wonderful, thank you!


Multiline strings do not work.

ljs code:
print([[hi]])

output:
ljsjit: test.ljs:1: invalid long string delimiter near '['

NOTE: Multiline strings do work in ljs but not ljsjit

I found a workaround:
print([=[hi]=])

I believe the error is from llex.c, Line 517


Support tool mode

Registers the nativescript as a tool class so that it can be used in tool mode for EditorPlugins.

Thanks! :D


Add NET6 and NET8 to JetBrains.FormatRipper

Hey, Snyk is reporting issues with Formatter ripper;
<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>The projects we have at NET6 and NET8, but because FormatRipper is compile against netstandard1.0, its falling back to an older version.
Could you add NET6 and NET8 to the compilation targets?

netstandard2.0 was added and will be available in next release.


Add Profitiability filter for Hideout Crafts page

Describe the Feature Request
Feature: A toggle-able filter to hide all crafts with negative profit to the /hideout-profit page. It should be placed inline with the 2 existing filters, in the style of  the Empty Fuel filter.

I'm not sure how much additional marginal utility this feature adds beyond the current ability to sort crafts by profitability. Can you explain your use case a bit more in terms of why this filter is more useful than just sorting the list and stopping once you scroll to a craft that isn't profitable?

Yeah I agree it's limited in use. It came to mind while sorting by flea throughput and wanting to only see results that are profitable and high throughput.

I see, but isn't "profitable and high throughput" the same thing as the top of the list when sorting for profit/hour?


added lines to setup.cfg for config files

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

Comparison is base (6ba0b03) 66.46% compared to head (d071405) 66.46%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   66.46%   66.46%
=======================================
  Files          16       16
  Lines        1005     1005
=======================================
  Hits          668      668
  Misses        337      337

Flag
Coverage Δ

unittests
66.46% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Updates Sensu description

Hi @brian-brazil , including you here since you're listed as a Maintainer. This doc change updates the Sensu description with more updated information.

@asachs01 First, you'll need to provide a DCO on your commit (and all future commits).

I've made some tech-writer-y critiques. I'll leave content critique to others.

Signed-off-by: Aaron Sachs<EMAIL_ADDRESS>

Thanks!


Center buttons in view

I'm unsure of what this centerButtons property is supposed to do.  When I build this branch and set the centerButtons flag to YES for the cars example (in the example project), the buttons on the ends of the list are never fully visible on screen.  I think that is bug with this implementation, but I'm not sure what the intended behavior is for centerButtons.

Hello, this need to center all buttons in center of view.
|----------|button|-||button|----------|
like this.

Have you tried the property centerAlignButtons? Setting this to YES
should accomplish what I think you are describing.
On Wed, Nov 25, 2015 at 10:19 PM, ZhuchoG<EMAIL_ADDRESS>wrote:

Hello, this need to center all buttons in center of view.
|----------|button|-||button|----------|
like this.
—
Reply to this email directly or view it on GitHub
https://github.com/hightower/HTHorizontalSelectionList/pull/62#issuecomment-159792216
.

--
Erik Ackermann
Mobile Development
(212) 951-0496
LinkedIn http://www.linkedin.com/in/erikackermann
176 Grand Street, 3rd Floor - New York, NY 10013

I tried, but it makes layout like this
|-----|button|-----|button|-----|

I see.  Maybe we need better names for these flags.  The existing flag (centerAlignButtons) is more like justify and your implementation is probably more aligned with what people call "center".  Let me think if there's a good way to rename these to be less confusing without breaking backward compatibility too bad.

@ZhuchoG I think I accomplished this goal here: https://github.com/hightower/HTHorizontalSelectionList/pull/72
Let me know if that works.  Going to close this PR.


[BUG]: Block application failed after finalization (at height 1444139)

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior
This node is new and was started and has not been shut down.
git checkout v0.4.1
docker compose --profile all up
Node failed to sync.
Logs attached.
koinos node logs.zip
Expected behavior
No response
Steps to reproduce
No response
Environment
- OS:
Ubuntu 20.04 LTS
VPS on Digital Ocean
4vCPUs
8GB RAM

Anything else?
No response

Duplicate of koinos/koinos-state-db-cpp#1


chore: Upgrade aws-sdk dependency

Issue #, if available:
Description of changes:
Self explanatory. See inline comments for defaults
Testing

[x] Tested in my dev pipeline
[x] Tested device farm locally (becase we do not use it in dev-pipelines anymore)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Build before

Build after


docs: more instructive quickstart

Codecov Report

Merging #75 (3b88d5e) into main (650a8c8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #75   +/-   ##
=======================================
  Coverage   97.17%   97.17%
=======================================
  Files          65       65
  Lines        4382     4382
=======================================
  Hits         4258     4258
  Misses        124      124


Exceptions are not caught, if a global tuple is used as exception types

The commit 6cc0a3a758937921fd5889eecb301ae4c65c7f5c broke exception handling, if the exception type is a tuple of exceptions.
The following code
MyExceptions = (KeyError, ValueError)
def a():
        _MyExceptions = MyExceptions
        try:
                int("x")
        except _MyExceptions as e:
                print("Handling exception a")
def b():
        try:
                int("x")
        except MyExceptions as e:
                print("Handling exception b")
a()
b()

gives this result with CPython and Cython before 6cc0a3a758937921fd5889eecb301ae4c65c7f5c:
Handling exception a
Handling exception b

With commit 6cc0a3a758937921fd5889eecb301ae4c65c7f5c or later it does not catch the first and the second exception anymore in Cython:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "test.pyx", line 13, in init test
    a()
  File "test.pyx", line 5, in test.a
    int("x")
ValueError: invalid literal for int() with base 10: 'x'

In current Cython master branch it is a bit better in that is succeeds to catch the first exception with the local tuple, but still fails to catch the second one with the global tuple.
Handling exception a
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "test.pyx", line 14, in init test
    b()
  File "test.pyx", line 10, in test.b
    int("x")
ValueError: invalid literal for int() with base 10: 'x'

Duplicate of #2425.


fix(curriculum): Updated code example for rpg explaintion on variables

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #53424

Hey @shanmukh-sai2003
Thank you for opening this pull request.
Related issue is limited to the "first time" code contributors to this repository. Because of that I'm going to close this PR. We would welcome future pull requests from you.
Thank you and happy coding.


V1.0.23.ipv6 doesn't work

In versions 1.0.22 and 1.0.23, ipv6 can't work normally. The garbled code problem of 1.0.22webdav function when accessed through a web browser will also appear in 1.0.23. (The video feedback is only 1.0.21 and 1.0.23.)
https://github.com/Tiarait/HTTP-FS-file-server/assets/100478073/0c0b658c-096b-4e92-ba7a-bbdabfc7a3e7

Oh, I think I understand. The fact is that /files/ is a web interface with styles and scripts, and /webdav/ is a purely XML scheme (API) for webdav clients and I duplicate it using the HTTP/S protocol as well.
How connect webdav on macOS
How connect webdav on windows
Webdav client Chrome extension
In the next update I will try to write a simple interface for /webdav/ for http/s protocol without using styles and scripts so that there is no confusion. Like this

fixed in 1.0.24


Pre-warmed instances pricing clarification

Hi,
It's written that "When the app is idle and no events are triggering, the app will be provisioned and running on five instances. At this time, you will not be billed for a pre-warmed instance as the always ready instances aren't used, and no pre-warmed instance is even allocated." What I'm wondering is at which point will I be billed for the pre-warmed instances? We have a heavy function with quite a long cold startup so I'd be interested in increasing the number of pre-warmed instances but I'm a bit worried it would cost too much.
Thanks,
Frank

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

ID: 3847e16b-92ae-0202-c7e1-ca9a8474e65f
Version Independent ID: a25b6b5b-05ab-b3b2-616c-5d06eadb928d
Content: Azure Functions Premium plan
Content Source: articles/azure-functions/functions-premium-plan.md
Service: azure-functions
GitHub Login: @jeffhollan
Microsoft Alias: jehollan

Hello @FrankGagnon, Thank you for your feedback! We will review and update as appropriate.

As soon as an always ready instance becomes active we immediately pre warm the desired pre warmed instances and billing for them starts right then. So yes, if you set like 10 pre warm the moment one becomes active all 10 pre warm would be allocated and billing would start.
As an aside feel free to shoot me a note on scenario. For most part increasing pre warm May only be needed if you have a very heavy function and very rapid burst scale with no tolerance for latency - curious if that maps to what you're going for and if so let me know. Happy to help. Jeff.Hollan at microsoft.com

@jeffhollan Thanks for your quick response!
In our Premium Function App we currently publish 18 Node functions each ranging from 9 MB to 25 MB of JS code. Since the Functions are so heavy, they take some time to startup (this made the Consumption plan unusable). The functions serve external customer API requests, so the load is very hard to predict. We haven't rolled this out in production yet so I'm still looking at the parameters we'll be able to tune until then.
If you're interested in more details, we can get in touch.

Hello @FrankGagnon,  Since the resolution was provided above by Jeff, I'm going to have this thread closed as it isn't an issue with docs. If you run into other issues or have docs specific feedback, please don't hesitate to open a new issue. Thanks!


Latest Bug - asked to report

Checklist

[ ] I'm reporting a broken site support issue
[ ] I've verified that I'm running youtube-dl version 2019.07.30
[ ] I've checked that all provided URLs are alive and playable in a browser
[ ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE
Issues downloading a YouTube vid.  I LOVE your program, by the way. Here are the details. Hope this helps. Linux Mint
xxxx@xxxx ~ $ youtube-dl -k --output --verbose "~/Desktop/GerardMorin/%(title)s.%(ext)s" https://youtu.be/KVeDKuHPDK8
ERROR: fixed output name but more than one file to download
xxxx@xxxx ~ $ youtube-dl -k --output "~/Desktop/GerardMorin/%(title)s.%(ext)s" https://youtu.be/KVeDKuHPDK8
[youtube] KVeDKuHPDK8: Downloading webpage
[youtube] KVeDKuHPDK8: Downloading video info webpage
WARNING: Unable to extract video title
[youtube] KVeDKuHPDK8: Downloading js player vflPI0brM
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1342, in _decrypt_signature
video_id, player_url, s
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1250, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1314, in _parse_sig_js
jscode, 'Initial JS player signature function name', group='sig')
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 1004, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by RegexNotFoundError(u'Unable to extract \x1b[0;34mInitial JS player signature function name\x1b[0m; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

I ran the update command but it stated
xxxx@xxxx ~ $ sudo youtube-dl -U
[sudo] password for jeff:
It looks like you installed youtube-dl with a package manager, pip, setup.py or a tarball. Please use that to update.
The Synaptic Package Manager says I have the current version of youtube-dl (2016.02.22-1) ... but that looks like a 2016 year and version. What command should I run for linux mint to get this up-to-date? Thanks in advance.

also just tried this ...
xxxx@xxxx ~ $ sudo apt-get install youtube-dl
Reading package lists... Done
Building dependency tree
Reading state information... Done
youtube-dl is already the newest version (2016.02.22-1).
The following packages were automatically installed and are no longer required:
libwireshark8 libwiretap6 libwscodecs1 libwsutil7 mint-meta-core mintwelcome
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
BUT, IT'S NOT WORKING ... was working fine this morning.
xxxx@xxxx ~ $ youtube-dl -k --output "~/Desktop/GerardMorin/%(title)s.%(ext)s" https://youtu.be/q1ZKqIOgYQM
[youtube] q1ZKqIOgYQM: Downloading webpage
[youtube] q1ZKqIOgYQM: Downloading video info webpage
WARNING: Unable to extract video title
WARNING: Requested formats are incompatible for merge and will be merged into mkv.
[download] /home/jeff/Desktop/GerardMorin/_.mkv has already been downloaded and merged


Remove Google.Cloud.Diagnostics.AspNet source code

The package remains listed in nuget.org, and it makes sense to keep it in the README; it's perfectly usable, we're just not taking it any further.
If we get requests to build a version of it targeting GAX v3, we can revert this commit at that point.

Travis is failing thouhg, I think maybe because the folder is not deleted?

Travis is failing because it is deleted. It tries to build "things that have changed" - but in this case, the change is a deletion. This always happens when we delete a project, but it's never worth fixing!

Ahhh, makes sense!


feat(pg): Install Sphinx fork during sphinx install

Purpose

Updates the sphinx install command to install the Sphinx Foundy fork binaries
Updates installation docs to no longer recommend installing the fork via foundryup
Updates ci guide to recommend running yarn sphinx install —confirm instead of using the foundry GitHub action integration

Todo

[ ] Test CI guide

If we're keeping the troubleshooting section, we need to update it to use sphinx install instead of foundryup


chore(deps)!: update esbuild to 0.16.1

Description
https://github.com/evanw/esbuild/blob/main/CHANGELOG.md#0160
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

/ecosystem-ci run


[BugFix] Fix FE dead lock bug where db lock and TabletInvertedIndex lock waiting for each other

backport #30703

[FE Incremental Coverage Report]
:disappointed: fail : 3 / 22 (13.64%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/leader/ReportHandler.java
0
18
00.00%
[964, 966, 967, 968, 969, 973, 974, 975, 979, 980, 981, 984, 986, 987, 991, 994, 995, 997]

:large_blue_circle:
com/starrocks/catalog/TabletInvertedIndex.java
3
4
75.00%
[205]

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)


Failure to build with no-fake-scoped-enums with emscripten

When generating with fake scoped enums disabled, using the latest emscripten webgpu.h, I see multiple compilation errors from the WEBGPU_CPP_IMPLEMENTATION section of webgpu.h.
To generate:
python3 ./generate.py -u webgpu.h -t emscripten/webgpu.template.hpp -o webgpu.hpp -d defaults.txt -d extra-defaults.txt --no-fake-scoped-enums

When building, I get compilation errors such as:
webgpu.hpp:1341:16: fatal error: assigning to 'WGPUBackendType' from incompatible type 'wgpu::BackendType'
 1341 |         backendType = BackendType::Undefined;
      |                       ^~~~~~~~~~~~~~~~~~~~~~

These could be resolved with a change like backendType = static_cast<WGPUBackendType>(BackendType::Undefined).

Thanks for reporting this, I have to admit that I undertested this feature. Keeping this open until I fix and add automated tests! Thanks again for your multiple contributions!

Back at this, I realize that the issue you report is precisely why I had to use fake enums. So if you find a way to work it around properly, I would be happy to switch everything to real enums!
 You may always force the enum type when using magic_enum functions, e.g.:
ErrorType errorType = /* ... */;
std::cout << "Device error: " << magic_enum::enum_name<WGPUErrorType>(errorType);

But of course you will have the WGPUErrorType_ prefix in this case. Maybe a solution for you would be that the C++ wrapper also includes some enum to name conversion utilities? Ideally we should try and have this a compile-time thing so that it remains zero-overhead.


add post-install tooltip text

Required if add-on is accepted for publication in the web store.

Added.


Update iostream and related unitttest.

MicroProxySSLIOstream will now handle connect.
Modify unittest to test all iostream.

Coverage increased (+0.7%) to 71.745% when pulling 204ef95059122238c8bc8e1280550c9b0c0d67ed on iostream-refactor into cb2b8c94e4132e3eac93967a43f84a445bda6b20 on master.

Coverage increased (+0.8%) to 71.76% when pulling 204ef95059122238c8bc8e1280550c9b0c0d67ed on iostream-refactor into cb2b8c94e4132e3eac93967a43f84a445bda6b20 on master.

@chhsiao90 please help me review, thanks.

Coverage increased (+0.8%) to 71.76% when pulling 69079d84db886e2b78e3883521243c40d1622776 on iostream-refactor into cb2b8c94e4132e3eac93967a43f84a445bda6b20 on master.

Coverage increased (+0.8%) to 71.76% when pulling 57cc521030fb392de32f3ad1e301dc250a56712c on iostream-refactor into cb2b8c94e4132e3eac93967a43f84a445bda6b20 on master.

Coverage increased (+0.9%) to 71.907% when pulling 279c3ecec21707736e68dc88f78f86f2763e0119 on iostream-refactor into cb2b8c94e4132e3eac93967a43f84a445bda6b20 on master.

LGTM.
Is it ready for merge or still in progress?

Ready to merged, thanks.


Configure HTTPS connection

We should be able to configure HTTPS connections
We could try to add certificates to the spring gateway directly or replace spring gateway and configure apache2 or nginx loadbalancer

Or we could use an azure builtin solution


[fix][python] Task switch branch not show in webui

when create task switch in python api, switch branch not show correctly, due to we add some unnecessary attribute to switch task, this patch we add _task_ignore_attr in class Task to ignore those unnecessary attribute from _task_default_attr

PTAL @jieguangzhou thanks

Codecov Report

Merging #12120 (d46d5fc) into dev (6eb1eb7) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #12120      +/-   ##
============================================
- Coverage     38.68%   38.67%   -0.01%
+ Complexity     4009     4004       -5
============================================
  Files          1001     1001
  Lines         37422    37390      -32
  Branches       4262     4255       -7
============================================
- Hits          14476    14462      -14
+ Misses        21300    21283      -17
+ Partials       1646     1645       -1

Impacted Files
Coverage Δ

...org/apache/dolphinscheduler/remote/utils/Host.java
42.55% <0.00%> (-2.13%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
51.42% <0.00%> (-1.43%)
:arrow_down:

...rver/master/runner/task/BlockingTaskProcessor.java
75.86% <0.00%> (-0.55%)
:arrow_down:

...heduler/api/service/impl/ResourcesServiceImpl.java
51.68% <0.00%> (-0.47%)
:arrow_down:

.../dolphinscheduler/plugin/task/spark/SparkTask.java
72.56% <0.00%> (-0.25%)
:arrow_down:

...eduler/api/service/impl/DataSourceServiceImpl.java
30.06% <0.00%> (ø)

...cheduler/server/master/utils/DependentExecute.java
0.00% <0.00%> (ø)

.../dolphinscheduler/plugin/task/datax/DataxTask.java
0.00% <0.00%> (ø)

...phinscheduler/plugin/task/chunjun/ChunJunTask.java
0.00% <0.00%> (ø)

... and 11 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

LGTM, wait CI


[Bug]: Cant start Download / Empty Cipher

Client version
2.6.2
Node version
18.16.1
Operating System type
Windows
Operating system version
Windows 11
Describe the bug
i tried to download the video-data with "start_dowload"

eufy-security-client.cmd --command device.start_download -a TXXXX /path/to/file cipherId -v

But end on an Unexptected Error
2023-06-25 08:38:02.087  ERROR Unexpected error
 TypeError  Cannot convert undefined or null to object
error stack:
• station.ts:3642 startDownload
    node_modules\eufy-security-client\src\http\station.ts:3642:21

• task_queues:95 processTicksAndRejections
    node:internal\process\task_queues:95:5

• message_handler.ts:321 handle
    src\lib\device\message_handler.ts:321:25

• server.ts:125 receiveMessage
    src\lib\server.ts:125:21

it happens on both: Windows (Debugging) and Home Assistand Setup
To reproduce

Server / Client Setup with German Account
getting local events
Try to Download with path and cipher

Screenshots & Logfiles
No response
Additional context
Seems like the Client cant find the Cipher. The Request on "v1/app/cipher/get_ciphers" is just an empty Success without Data
{
  method: 'post',
  endpoint: 'v1/app/cipher/get_ciphers',
  responseType: 'json',
  data: {
    cipher_id: [ (int) ],
    user_id: <string>,
    transaction: '1687682282065'
  }
}
{
  status: 200,
  statusText: 'OK',
  headers: {
    date: 'Sun, 25 Jun 2023 08:38:02 GMT',
    'content-type': 'application/json; charset=utf-8',
    'content-length': '31',
    connection: 'close',
    vary: 'Origin, Origin',
    server: 'APISIX/3.3.0'
  },
  data: { code: 0, msg: 'Erfolgreich.' }
}

Eufy has changed some things and therefore this functionality is now deprecated.
Here everything must be reimplemented from scratch.

I see the issue closed with the label "done". Does this mean that the functionality was implemented?


Differentiate metrics from servers sharing a cloned DB

Rationale
Our metric tracking gets confused when we have multiple servers using DBs with the same ServerInstallationGUID. That's common for staging and production servers since they frequently take a DB backup and restore it. Less commonly, one production server forks from another.
Reviewing actual metric data, we reliably pull the server host name and can use it to distinguish these instances from each other.
Changes

Identify servers based on GUID and host name
Stop caring if an install used the Windows installer, which is long dead
Track more per-instance properties, like organization name and server IP, solely the session level as they can change over time

@labkey-martyp happy to walk through this with you, as the nominal Mothership feature owner.


Only change scheme of .swiftinterface files to readonly if old scheme was file

I’m working on adding semantic functionality to generated interfaces in SourceKit-LSP and this will generate reference documents with a sourcekit-lsp: scheme and a .swiftinterface file. We shouldn’t change those URIs to a readonly scheme.

What happens if the user modifies the contents of a document with the sourcekit-lsp: scheme?

Non-file URL schemes are automatically marked as non-editable by VS Code.


feat(linter): typescript-eslint/no-floating-promises

https://github.com/oxc-project/oxc/discussions/2855

OMG this is amazing, fingers crossed for communicating with the ts server, as discussed in https://github.com/oxc-project/oxc/discussions/2855

@valeneiko Such an amazing effort! Feel free to ping me with preliminary results!

@Boshen Almost there!
It now successfully detects a floating Promise in a simple file:
cargo run --bin oxlint -- --typecheck-plugin -A all -D no-floating-promises \
  --tsconfig ./crates/oxc_linter/fixtures/typecheck/tsconfig.json \
  ./crates/oxc_linter/fixtures/typecheck/sample.ts

async function funcAsync() {
  return Promise.resolve();
}

function func() {
  return 7;
}

export async function test() {
  func();
  funcAsync();
}

I tested this on cal.com, and it's working on multiple files!
It panic with
called `Result::unwrap()` on an `Err` value: CommandFailed("Error processing request. Cannot read properties of undefined (reading 'kind')\nTypeError: Cannot read properties of undefined (reading 'kind')\n    at isDeclarationNameOrImportPropertyName (/Users/bytedance/github/oxc/npm/oxc-typecheck/node_modules/.pnpm/typescript@5.4.4/node_modules/typescript/lib/typescript.js:87886:25)\n    at getTypeOfNode (/Users/bytedance/github/oxc/npm/oxc-typecheck/node_modules/.pnpm/typescript@5.4.4/node_modules/typescript/lib/typescript.js:85186:11)\n    at Object.getTypeAtLocation (/Users/bytedance/github/oxc/npm/oxc-typecheck/node_modules/.pnpm/typescript@5.4.4/node_modules/typescript/lib/typescript.js:46305:23)\n    at Module.isPromiseArray (file:///Users/bytedance/github/oxc/npm/oxc-typecheck/dist/rules/no-floating-promises.js:4:26)\n    at noFloatingPromises::isPromiseArray (file:///Users/bytedance/github/oxc/npm/oxc-typecheck/dist/handlers.js:46:43)\n    at executeCommand (file:///Users/bytedance/github/oxc/npm/oxc-typecheck/dist/server.js:41:26)\n    at onMessage (file:///Users/bytedance/github/oxc/npm/oxc-typecheck/dist/server.js:26:48)\n    at Interface.<anonymous> (file:///Users/bytedance/github/oxc/npm/oxc-typecheck/dist/server.js:16:9)\n    at Interface.emit (node:events:518:28)\n    at [_onLine] [as _onLine] (node:internal/readline/interface:416:12)")

I think it's due to providing utf8 span positions instead if utf16, we don't need to worry about this as there is already a tracking issue.
Now onto performance: if performance of what we have right now is less or equal to @typescript/eslint, then we are all good!

@valeneiko Can you time our setup and compare to one or two repositories with no-floating-promises on? https://github.com/search?q=no-floating-promises&type=code
https://github.com/mermaid-js/mermaid seems like a good place to start: Finished in 41ms on 397 files with 89 rules using 12 threads.

@Boshen I have tried to run lint on the repo you linked, but it fails with the exact same error. And it's cause is not just encoding differences.
Take a look at the AST of one of the files from the repo:

oxc: link
typescript: link

OXC makes a request for CallExpression at (58, 1758), but typescript has this node at (56, 1754). Looks like typescript includes leading newlines and spaces as part of the CallExpression span.
Do you have any suggestions for how we can better map between the two? I am thinking we could try a full path or just child indexes, but now quite sure how to get this from OXC.
On a side note, I finished the remaining parts of the lint rule.

@Boshen I have tried to run lint on the repo you linked, but it fails with the exact same error. And it's cause is not just encoding differences.
Take a look at the AST of one of the files from the repo:

oxc: link
typescript: link

OXC makes a request for CallExpression at (58, 1758), but typescript has this node at (56, 1754). Looks like typescript includes leading newlines and spaces as part of the CallExpression span.
Do you have any suggestions for how we can better map between the two? I am thinking we could try a full path or just child indexes, but now quite sure how to get this from OXC.
On a side note, I finished the remaining parts of the lint rule.

Ahh such a big blocker, where is typescript eslint do the conversion? It's probably in https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-estree/src/ast-converter.ts but I can't find it from a quick scan.
I need to measure the effort of going forward with this experiment with we want to do the conversion.
In the meantime, can you help out and just ignore the error / crash and let the whole thing complete so we can compare the total running time between typescript eslint and our approach?
It's gonna be a lot of balancing of tradeoffs 🥵

Ahh such a big blocker, where is typescript eslint do the conversion?

Here is the conversion logic in typescript-eslint: https://github.com/typescript-eslint/typescript-eslint/blob/9c94b81b2560558fcc2d85dd644679a5dbf4a277/packages/typescript-estree/src/convert.ts#L757
If I understand it correctly, typescript eslint build their own AST by visiting the AST typescript produced.

In the meantime, can you help out and just ignore the error / crash and let the whole thing complete so we can compare the total running time between typescript eslint and our approach?

Ok. I'll find a way to ignore those errors for now.

If I understand it correctly, typescript eslint build their own AST by visiting the AST typescript produced.

Yeah I saw that too, but I can't find where it's changing the span positions :-(

Ok. I'll find a way to ignore those errors for now.

Thank you!

Yeah I saw that too, but I can't find where it's changing the span positions :-(

They don't need to. Instead of looking up nodes by spans, the just directly map the nodes, because they store which TS node they used to create each one.

...

I've pushed the commits to ignore the errors. And managed to run the rule against mermaid repo. I've modified their .eslintrc.cjs to only enable @typescript-eslint/no-floating-promises and ESLint runs in 3.2 seconds. OXC with that single rule takes 90 seconds (using 24 threads), or 220 seconds (single threaded). There is obviously something wrong.

It could be that mapping errors lead us to type check different code paths.
Out lint rule implementeation is not 100% correct, so we may be calling TS more than necessary

I know at least 1 case: () => new Promise(). ESLint completely skips those, but we call typecheck and generate an error.

But more likely there is something wrong in our JS side implementation. It should not be taking this long.

But more likely there is something wrong in our JS side implementation. It should not be taking this long.

I agree, my guess is that typescript eslint is using some kind of caching technique or some API that we don't know about 😅

Result of running OXC in debug mode against mermaid with all the measurements:
                      #: average /   total
                  parse: 0.007ms /  0.225s
              stringify: 0.019ms /  0.624s
                   open: 7.939ms / 66.672s
                  close: 0.320ms /  0.127s
         isPromiseArray: 0.173ms /  2.703s
          isPromiseLike: 0.014ms /  0.226s
isValidRejectionHandler: 0.039ms /  0.000s
             getProgram: 0.015ms /  0.460s
         getTypechecker: 0.000ms /  0.008s
                getNode: 0.004ms /  0.114s
        channelOverhead: 0.070ms /  2.261s
                   idle: 0.071ms /  2.283s

A few observations:

Actual work is basically the same as typescript-eslint
We spend over 3 seconds on just communication overhead

We could lower it by not sending file content
We should pipeline the requests, so that TS is never idle
We could use something faster than JSON

We spend most of our time opening files in TS

This seems like an unnecassary step - we should look into how ESLint does it

A few observations:

I see these are optimizations that can be done later.
Performance wise we are on the correct path, which is really good news 👍 .
Now the last puzzle piece to solve is the mismatched AST nodes. Let's explore this for a few days before jumping to any conclusions.

After looking at a few different examples, OXC and TS have both different structure and different spans. So mapping code is unavoidable.
One idea comes to mind:

Build a visitor, that walks the tree in the same order on both sides. Then we can assign each node an id, and look it up by id on both sides. Visitor implementation in TypeScript is only about 600 lines (here). So not too diffucult to map. And we can probably exploit the fact that nodes are going to be visited in the order they appear in the source file. And only assign the Ids to nodes that map nicely (at least to start with), since we only need to be able to resolve a subset of them anyway.

After exploring it a bit more, I don't think my previous idea would be enough. At this point the only solution I see is to fully map the AST. But given the effort required to maintain it I am not sure it would be worth it: we don't gain anything perf wise by having an ability to write these rules in rust.

After exploring it a bit more, I don't think my previous idea would be enough. At this point the only solution I see is to fully map the AST. But given the effort required to maintain it I am not sure it would be worth it: we don't gain anything perf wise by having an ability to write these rules in rust.

😢 It's sad to see that you have spent so much time and energy on this but it's blocked by how typescript works. TypeScript doesn't offer linter plugins, and we are forced to do this whole round trip despite us willing to do all these hard work, but we'll also need to maintain this whole round trip.
I think at this point, we should just stop thinking about porting these rules from @typescript/eslint and start innovating our own set of rules that can help people catch bugs.
I mean, it was tried before https://github.com/microsoft/TypeScript/pull/53146 and it wasn't prioritized ...
If anyone is going to ask again about typing rules, I'll just point them to this PR :-(

So back to the drawing board.
Since we have cross-file linting working with --import-plugin, should we start innovating with cross-file information, and maybe start implementing things like #[must_use]?
What do you think?

Since we have cross-file linting working with --import-plugin https://oxc-project.github.io/blog/2024-05-04-import-plugin-alpha.html, should we start innovating with cross-file information, and also look into things like #[must_use]?
What do you think?

Sound like a logical next step. It does feel like re-implementing TypeScript in Rust, but maybe we only need a very small subset to get most of the way. The complex part would be symbol resolution and I think we should start with that.
I am not so sure about adding extra annotation to code, I would prefer enabling this rule instead: explicit-module-boundary-types. Then the cross-file step could easily mark if a function or method returns a promise. And even without the rule, most of those functions would be annotated with async already, and we could use that instead of the return type. But regarless of the approach, we would need to have an ability to resolve references to their corresponding symbols, so that we could look up annotations on them.

Let me organize this a bit tomorrow.

The complex part would be symbol resolution and I think we should start with that.

If the goal is still no-floating-promises, I think we can get it working first by marking exported async functions of a module as async in ModuleRecord
https://github.com/oxc-project/oxc/blob/07076d9765cee6f4986c5a4e599f9edc61f60d8f/crates/oxc_syntax/src/module_record.rs#L67-L68

I am not so sure about adding extra annotation to code, I would prefer enabling this rule instead: explicit-module-boundary-types.

I meant marking things with extra annotations, there is a system in rust where you can mark things with different things in compile time, #[must_use] is one of them.
Now that you have mentioned it, maybe we can leverage isolated-declarations? And just do linting under isolated-declarations 🤔 We prepare for the future 😆
https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-beta/#isolated-declarations

Now that you have mentioned it, maybe we can leverage isolated-declarations?

Yes, this is exactly what I meant. But since that feature is not even out in TS, explicit-module-boundary-types could still make sense, and achieves the same result.

If the goal is still no-floating-promises, I think we can get it working first by marking exported async functions of a module as async in ModuleRecord

That could be a good start. I was mostly concerned about complexity of doing it for cases other than named import of a function:
// foo.ts
export function foo() {}
export const obj = { foo() {} };
export class Cls { foo() {} }

// -- default / namespace import
import mod from './foo';
mod.foo(); // <-- How do we resolve foo?

// -- object properties
import {obj} from './foo';
obj.foo(); // <-- How do we resolve foo?

// -- class fields
import {Cls} from './foo';
const x = new Cls();
x.foo(); // <-- How do we resolve foo?

I feel said about closing this PR :-(
Continue in https://github.com/oxc-project/oxc/issues/3105#issuecomment-2100859582

Source: https://speakerdeck.com/unvalley/exploring-type-informed-lint-rules-in-rust-based-linters


Revert "Refactor:extract common module postgresql-common"

Reverts apache/skywalking#3725
According to https://github.com/apache/skywalking/pull/3727#issuecomment-546852048. This is an unnecessary refactor. Even it is harmless, it don't really support a new version as the PR described before, the new versions of JDBC driver have been supported by existing codes. So I am running rolling back.
FYI @aderm

ACK. It is not necessary at present. Can I wait until later if I need to add it?

What dou you mean wait?

The latest PG version is already PG12, and it is not clear whether current version can support it.

You could choose any time you need to add it back. I just mean, we don't need it now.

ACK


[badge] Card not visible after proposing, but visible after refresh

Show card after proposing in list of cards.

This is not a database, this is a blockchain. The problem is here since the beginning and that's why we display the message.
It now takes even more time since we need dgraph to sync the data first


CMilliTimer: Number of Member Variables

Can you reduce the number of member variables in CMilliTimer?
If so, would that be an improvement?

Prolly.
It might require some contorted logic to deal
with the rollover condition.
I need to do some testing in that area anyway.
I'm nor sure how much of an improvement it
would make. It could save
On 01/20/2017 10:19 AM, James Prior wrote:

Can you reduce the number of member variables in CMilliTimer?
If so, would that be an improveme

--
Jon
http://www.jondbennett.com


Function: gram_schmidt_classical()

In the lecture material, it defines the gram_schmidt_classical() function, for this part what code " R[:i,i] = Q[:,:i].T @ v " means here?

The expression Q[:, :i].T @ v is taking the inner product of the first i columns of Q with v, returning the result in a vector of length i. That vector of length i is deposited in the first i entries of column i in R: R[:i, i].
If you're working on the homework, I'd suggest trying to adapt the naive code, instead of this more optimized variant.


[0.62.0-rc.2] - Modal is always presented as full screen modal presentation style on ios

Description:

presentationStyle for the Modal component no longer has any effect on how the react native modal is presented.

React Native version:
    OS: macOS 10.15.3
    CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
    Memory: 279.68 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.19.0 - ~/.nvm/versions/node/v10.19.0/bin/node
    Yarn: 1.22.0 - /usr/local/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v10.19.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 23, 26, 27, 28, 29
      Build Tools: 26.0.3, 27.0.3, 28.0.2, 28.0.3, 29.0.2
      System Images: android-22 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>10548
    Xcode: 11.2.1/11B53 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.11.0 => 16.11.0
    react-native: 0.62.0-rc.2 => 0.62.0-rc.2

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
Issues without reproduction steps or code are likely to stall.

import React from 'react';
import {View, StatusBar, ActivityIndicator, Modal, Button} from 'react-native';

const App = () => {
  const [showModal, setShowModal] = React.useState(false);
  return (
    <>
      <StatusBar barStyle="dark-content" />
      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
        <Button onPress={() => setShowModal(true)} title="Toggle Modal" />
      </View>

      <Modal visible={!!showModal} presentationStyle="formSheet">
        <View
          style={[
            {
              flex: 1,
              backgroundColor: 'green',
              alignItems: 'center',
              justifyContent: 'center',
            },
          ]}>
          <ActivityIndicator color="white" size="large" />
        </View>
      </Modal>
    </>
  );
};

export default App;

Expected Results
Modal component should allow various flavours as described https://facebook.github.io/react-native/docs/modal#presentationstyle
Snack, code example, screenshot, or link to a repository:

Hello @owinter86 Modal was moved here: https://github.com/react-native-community/react-native-modal
Check if the issue persists with the module, if it does open an issue on that repo!

Hey @safaiyeh this is just a javascript extension to the react native modal, this component was not part of the lean core effort. All the native modules for this still exist in react native core.

I'm experiencing the same issue after going from rc1 to rc2, with no changes to react-native-modal

@owinter86 the modal is always showing as pageSheet not fullScreen. Also see the discussion from this PR... https://github.com/facebook/react-native/pull/27618

Fixed in RC.3

I was. using react-native-loading-spinner-overlay and in that component used Modal and ActivityIndicator, but sometimes the spinner is not showing since the visible param is true.


Custom font does not get loaded in TextComponent.textRenderer

Current bug behavior
Custom font works when a Component is tested in isolation, but not when nested inside some other Components, for some reason. The following is Component
part of '../../side_panel.dart';

class _ScoreNumberTextComponent extends TextComponent<TextPaint> {
  factory _ScoreNumberTextComponent.top({
    required Vector2 size,
    required Vector2 position,
    required ValueListenable<int> scoreListenable,
  }) =>
      _ScoreNumberTextComponent._(
        size: size,
        position: position,
        scoreListenable: scoreListenable,
        angle: radians(-90),
      );

  factory _ScoreNumberTextComponent.bottom({
    required Vector2 size,
    required Vector2 position,
    required ValueListenable<int> scoreListenable,
  }) =>
      _ScoreNumberTextComponent._(
        size: size,
        position: position,
        scoreListenable: scoreListenable,
        angle: radians(90),
      );

  _ScoreNumberTextComponent._({
    required super.size,
    required super.position,
    required super.angle,
    required this.scoreListenable,
  }) : super(
          anchor: Anchor.center,
          text: scoreListenable.value.toString(),
          textRenderer: TextPaint(
            style: TextStyle(
              color: ConstColours.navajoCream,
              fontSize: size!.y,
              fontFamily: 'VCR OSD Mono',
            ),
          ),
          scale: Vector2.all(1.3),
        ) {
    scoreListenable.addListener(_updateScoreText);
  }

  final ValueListenable<int> scoreListenable;

  void _updateScoreText() => text = scoreListenable.value.toString();
}

The normal nested stack of this Component is FlameGame -> RecrangleComponent -> RectangleComponent -> TextComponent<TextPaint>, for which it defaults to the normal font.
Expected behavior
When used in isolation, this does load the font correctly:
import 'dart:async';

import 'package:flame/components.dart';
import 'package:flame/game.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(
    GameWidget(
      game: TestFlameGame(),
    ),
  );
}

class TestFlameGame extends FlameGame {
  @override
  FutureOr<void> onLoad() async {
    await add(
      _ScoreNumberTextComponent(
        size: Vector2(40, 40),
      ),
    );

    return super.onLoad();
  }
}

class _ScoreNumberTextComponent extends TextComponent<TextPaint> {
  _ScoreNumberTextComponent({
    required super.size,
  }) : super(
          anchor: Anchor.center,
          position: size! / 2,
          angle: radians(-90),
          text: '01 ABC',
          textRenderer: TextPaint(
            style: TextStyle(
              color: Color(0xFFFDDFB1),
              fontSize: size.y,
              fontFamily: 'VCR OSD Mono',
            ),
          ),
        );
}

Steps to reproduce
It works fine on Zapp.run
But using the same files locally, and it doesn't work

The only major difference is that, locally, the use case is a Flutter package (game widget is exported), and not a Flutter game directly.
Flutter doctor output

[✓] Flutter (Channel stable, 3.16.1, on Microsoft Windows [Version 10.0.22621.3007], locale en-NL)
    • Flutter version 3.16.1 on channel stable at C:\tools\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7f20e5d18c (9 weeks ago), 2023-11-27 09:47:30 -0800
    • Engine revision 22b600f240
    • Dart version 3.2.1
    • DevTools version 2.28.3

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at C:\Users\ahalm\AppData\Local\Android\sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: C:\Program Files\Other Apps\programming\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✗] Visual Studio - develop Windows apps
    ✗ Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[✓] Android Studio (version 2023.1)
    • Android Studio at C:\Program Files\Other Apps\programming\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at C:\Program Files\Other Apps\programming\IntelliJ IDEA 2023.1.3
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (4 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 12 (API 31) (emulator)
    • Windows (desktop)            • windows       • windows-x64    • Microsoft Windows [Version 10.0.22621.3007]
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 120.0.6099.227
    • Edge (web)                   • edge          • web-javascript • Microsoft Edge 120.0.2210.144

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

More environment information

Log information

More information

Easier to provide more information, code, logs, on demand.

 Yes

For anyone who wants a solution, I used this SO Post. Basic asset duplication is needed, along with redeclaration.
Looks like incorrect behaviour, so I have filed a bug For Flutter.


Call stack only shows top frame

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:32:36.023Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

vscode-eslint
dba
1.4.3

EditorConfig
Edi
0.11.1

vsc-material-theme
Equ
1.1.2

JSDocTagComplete
Hoo
0.0.2

vscode-esformatter
how
1.5.2

output-colorizer
IBM
0.1.2

vscode-puglint
mrm
2.3.0

debugger-for-chrome
msj
3.5.0

code-spell-checker
str
1.5.1

(2 theme extensions excluded)

Lately I've been running into this issue many times per day, but I can't see the pattern that causes this.

When I hit a breakpoint, only the top stack frame is shown. More frames are displayed once I step to the next line. However, this is not possible if the line I'm breaking on is a throw statement, which makes this an annoyance.
Restarting VS Code fixes this briefly, but VS Code will start misbehaving again shortly after.
I've had this in multiple projects in various source files, so I doubt it is related to anything specific in these projects.
What can I do to gather more insights on this?

What version of node are you using?

8.9.0

Here are some things which could help us track this down

Can you create a small reproducable sample such that we look into this on our side (probably not, right?)
I think you know how to run vscode out of source, put a breakpoint here and check what callstacks vscode is asking for and what it is getting back. fyi for optimazation reasons vscode should first ask for the first stack frame and then for the rest. Maybe there is an issue and vscode does not ask for the rest. Code pointer
Option 3 is to set logging for the node2 debugger, which @roblourens can assist with

Thanks for the suggestions.

I don't see what's causing this, so, no.
In theory, yes, I know how to do it. In practice, not so much. This just leads me to new problems to solve. I'm stuck on "Configured debug type 'node' is not supported." and the extension marketplace is empty in the development build.
Would appreciate it.

Let's first go with option 3 with @roblourens
And if that does not work I can give tips on how to setup debugging on your machine so we get more details.

@isidorn Trying to figure it out myself right now. It's a bit confusing that verboseDiagnosticLogging is not detected as a valid setting in the launch.json, but it surely does log a lot of information.

After a couple of runs, I'm assuming that the additional (very noticeable) delay introduced by the verbose logging is preventing the issue from happening.
I'd really like to look into debugging the code itself, as that looks very promising from what I can tell. Is there some hacky way I could just add some logging, rebuild and put the .exe into my Program Files to replace my current stable setup or something like that?

That switch is deprecated, set "trace": true and upload the file here. There should be less delay because it won't log to the console.

I have the same issue on my home workstation and was able to reproduce it with trace enabled. I'd rather not make the file publically available. Can I share it privately somehow?

Feel free to email it to me, at the address in my profile.

@roblourens Done

Thanks.
@isidorn The log shows only a single stackTrace request for one frame. The adapter responded with the single frame, and "totalFrames":143.

@roblourens thanks for analysing the logs, so it seems to be an issue on the vscode side.
From my theoretical analysis of the code here it might be that vscode fetched 1 call stack, waited for 420ms as designed and in those 420ms got a clearThreads threads call which would cancel all scheduled fetchings.
This could happen by pressing step / continue. @roblourens is there something like that in the log in the 420ms window.
Unfortunetely I can not provide more help with the information I am given.
@roblourens maybe you could send me the logs on my email
@oliversalzburg if you have time maybe you could setup development vscode, place some breakpoints on the spots I gave you and setup debugging by simply copying the node-debug and node-debug2 extensions from your applicaiton into your user oss-dev folder as I explain here https://github.com/Microsoft/vscode/issues/20623#issuecomment-279969736

Alright, I copied my extensions over.
When I run the Launch VS Code config, it will launch the development version of Code, but the host instance will show:

Cannot connect to runtime process, timeout after 10000 ms - (reason: Got a response from the target app, but no target pages found).

If I try to Attach to VS Code after the previous attempt launched VS Code, I get the same error message.
So I just opened the DevTools in the development build and placed the breakpoints in there, but, to no avail. When starting my application I still get:

Configured debug type 'node' is not supported.

I'm not on OSX, so the paths from #20623 were only an indication of where to look. I guess those were not the extensions I was looking for.

Breakpoint on https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/common/debugModel.ts#L821 hit, continue
Breakpoint on https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/electron-browser/rawDebugSession.ts#L344 hit, args.levels === 1

When waiting on this breakpoint for some time and then continuing, it will be hit again with 20 more stack frames and the error is not reproduced.
When not waiting, we continue

Breakpoint on https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/common/debugModel.ts#L822 hit
I can't evaluate this.schedulers.has(thread.getId()) in the console, says this is undefined.

Breakpoint on https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/common/debugModel.ts#L828 is hit. So, I assume the mentioned expression evaluates to false.

However, next a breakpoint on https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/common/debugModel.ts#L824 is hit, even though we never went into the previous branch.
Makes no sense to me. Maybe it's due to working with transpiled sources.

Breakpoint on https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/electron-browser/rawDebugSession.ts#L344 hit again, args.levels === 19

No more breakpoints are hit afterwards and I see a call stack with 1 frame in the UI.

@oliversalzburg thanks a lot for the investigation. @roblourens since the last breakpoint is hit it seems like vscode sends out another stackFrame request with levels 19 to get the rest of the stack frames. Is this not what you are seeing in the logs

Let me know if I should check anything else.

@isidorn I forwarded the logs. They only show the one stackFrame request.

 In theory, it could be different root causes for the same problem.
If I'm unresponsive during next week, it's because I'm on a holiday. I'd be happy to pick up again afterwards if you need me.

@oliversalzburg I have looked into the logs and it seems to not be related to the breakpoint investagion you did. Though I might be wrong.
Can you either of:

Try to get a reproducable sample which you caould share with me
Do a screen sharing session with me so with debug this together

Moving to decmeber since you are on vacation so no need to rush this

@isidorn A screen-sharing session sounds like a good idea, please get in touch via email (in my profile) so we can figure out a good time.

During the debugging session, we noticed that the second .stackTrace() call in getCallStackImpl is rejected with an error message of "No call stack available.".

Exactly. Also @oliversalzburg is using node version 8.9.0
On the vscode side the issue is that I do not properly show the error if the second call stack returns erroniously (which I will look into fixing).
As the real issue is on the node debug side forwaridng to @roblourens
@roblourens let us know what other deatils you need as @oliversalzburg is happy to help

I also noticed that this behavior seems to only happen when I restart the debugging session. When I stop and start it instead, the error does not reproduce.

I'm debugging, something weird is happening. I think vscode the debug adapter is actually not terminating correctly when using 'restart'.

It also reproes with the legacy adapter. Could something have changed on the vscode side? @weinand

@isidorn that's in your area. Are you aware of any related changes in that area?

Debug any node app with legacy or inspector
Run ps ax | grep nodeDebug, see one debug adapter
Press reload
Run ps ax | grep nodeDebug, see two debug adapters
Stop debugging
Run ps ax | grep nodeDebug, see one debug adapter process remaining

We are leaving the process behind after reloading. But the adapter should have shut itself down. Could be a change in the vscode-debugadapter module but I don't see anything.

@roblourens great catch about multiple session lying around.
The issue was that I was for some weird reason reusing the internal debug session id for a newly restarted process. Since this is a actually a brand new session now i do not treat specially.
Not a candidate since multiple restarts only leave 1 extra session in total and this was also happening in previous stable.
@oliversalzburg you can pick up the vscode insiders from Monday if you watn your issue fixed. Thanks again for great help.

@roblourens You really mean "reload" and not "restart", right?
In what version of VS Code are you seeing this?
I cannot reproduce the problem of a left behind DA, neither in Stable nor in Insider (and neither "reload" nor "restart").

@isidorn Awesome :) Thanks everyone

I guess I mean restart. I'll try with Isidor's fix.


suggest: trigger when one starts typing before a word, e.g.,

| - cursor
const foo = new Foo()
|foo

typing in c when the current cursor is should trigger suggest, e.g., with suggestion console, etc.
Before
https://github.com/microsoft/vscode/assets/16353531/8c2dbd24-9592-4ed8-b01a-949de91d8406
After
https://github.com/microsoft/vscode/assets/16353531/3ce9f253-9d1c-4569-8cea-2f1f2452656e

I just tested the issue in my daily workflow and it really exists. Excellent observation and work :)

@imvicencio

Nice work, Is there any way to test this change?

Before the PR's merged, one can only test checking out this branch and running from sources.
After it's merged, it should be within the VS Code Insiders the day after.


Dogfood allow-scripts workflow here

Pending review of allow-scripts

TypeError [ERR_INVALID_URL]: Invalid URL: undefined
    at onParseError (internal/url.js:259:9)
    at new URL (internal/url.js:335:5)
    at getCanonicalNameInfo (/Users/Etienne/Desktop/lavamoat-stuff/lavamoat/packages/node/test/projects/2/node_modules/@lavamoat/allow-scripts/src/index.js:258:15)
    at getCanonicalNameInfoForTreeNode (/Users/Etienne/Desktop/lavamoat-stuff/lavamoat/packages/node/test/projects/2/node_modules/@lavamoat/allow-scripts/src/index.js:443:12)
    at loadAllPackageConfigurations (/Users/Etienne/Desktop/lavamoat-stuff/lavamoat/packages/node/test/projects/2/node_modules/@lavamoat/allow-scripts/src/index.js:452:42)
    at async setDefaultConfiguration (/Users/Etienne/Desktop/lavamoat-stuff/lavamoat/packages/node/test/projects/2/node_modules/@lavamoat/allow-scripts/src/index.js:159:7)
    at async start (/Users/Etienne/Desktop/lavamoat-stuff/lavamoat/packages/node/test/projects/2/node_modules/@lavamoat/allow-scripts/src/cli.js:26:7) {
  input: 'undefined',
  code: 'ERR_INVALID_URL'
}

this is likely broken due to a lack of workspaces support. that should be resolved by https://github.com/LavaMoat/LavaMoat/pull/184 and then we can revisit this work

blocked by https://github.com/LavaMoat/LavaMoat/pull/184


Do not overload index with WithdrawalIndex and ValidatorIndex

in the function withdraw_balance the variable index takes different meanings and types. This confused at least one member of our team.

fwiw the types do not change and I'd say this implies the meaning does not change but I'd support this PR if it clarifies things

fwiw the types do not change and I'd say this implies the meaning does not change but I'd support this PR if it clarifies things

I think the confusing thing is statements like
        index=state.next_withdrawal_index,
        address=ExecutionAddress(state.validators[index].withdrawal_credentials[12:]),

Where in one line index is assigned a WithdrawalIndex and in the very next line, index is used with the ValidatorIndex that was passed to the function.


add zephyr-7b

Zephyr-7b seems outperforming chatgpt, it's small and look promising

Subtle question:
ChatGPT:

Mistral-7b:

Zephyr-7b: