.NET 5

Do you accept PR? Looking to try implementing Hydra REST API in .NET and this project looks promising! Amazing work :)
Unfortunately I only have Mac and .NET Core branch uses preview version of .NET Core 1. I am in progress to upgrde it to .NET 5 and I hope everything keeps going well.
If you have anything specific about it let me know :) thanks!

Give me some time to review those branches, as I had totally no time to proceed with both. I'll try to return to you ASAP

Thanks @alien-mcl. This is helpful and I will start looking through the branch. Are there certain projects that it makes more sense to focus on (Ursa.Web vs Ursa.Owin, and which projects are for servers/production vs clients/consumption, etc)?

In short:
URSA.AutoFac - AutoFac connector for core
URSA.CastleWindsor - CastleWindsor connector for core
URSA.Client - angularJS experimental client
URSA.Core - core components, abstracts, etc.
URSA.Example.Client - example .net client
URSA.Example.OwinApplication - example OWIN application
URSA.Example.WebApplication - example oldschool ASP.net application
URSA.Http.AutoFac - AutoFac connector of the HTTP components
URSA.Http.CastleWindsor - CastleWindsor connector of the HTTP components
URSA.Http.Client.Proxy - proxy generation tool
URSA.Http.Client - please ignore that one
URSA.Http.Description - API description generating components
URSA.Http - HTTP components
URSA.Owin - OWIN connector components
URSA.Tools - common tools
URSA.Web - oldschool ASP.net connector components
I believe that oldschool ASP.net components can be ignored in case of .net Core port. I'd start with Core, Http, Description, Owin and AutoFac/CastleWindsor


Need to add appveyor.yml

Need to have appveyor.yml file in the repo and use it instead of the relying on appveyor config.

Fixed in 55579b6f7c985e3da11c6f1fab6071f47b11c0b8


Upgrade rails 5.0.6

Coverage remained the same at 100.0% when pulling 8a6e7894604a737037f33b696f563d0cbf245222 on upgrade/rails-5.0.6 into 1d6d0c9b05ab18a5e92f2dab578fff4f4a9bf9ec on master.


LineEncoder.addXxx methods throw unfriendly NullPointerException if it is already closed or finished

LineEncoder.addXxx methods (addText, addLine, addNewLine, etc.) throws NullPointerException if close() or finish() is already called. However, it is common mistake that filter plugin or output plugin calls unnecessary finish() method. So, this exception should be more descriptive.

A possible implementation is:

create a Writer whose append() and close() method throw an exception with descriptive message
LineEncoder.finish and close set it to this.writer rather than setting null


Prepare to 10.3 & 11.0 core

There's few modules were deprecated and Symfony 7 probably the primary source of issues, starting with Drush 13
(deprecated modules)[https://www.drupal.org/project/drupal/issues/3309322]
Forum #3274153: [11.x] [Meta] Tasks to remove Forum from core and move to contrib
Tracker #3274140: [11.x] [Meta] Tasks to remove Tracker from core and move to contrib
Action #3343371: [11.x] [Meta] Tasks to remove Action
Book #3376101: [11.x] [Meta] Tasks to remove Book
Statistics #3341091: [11.x] [Meta] Tasks to remove Statistics
Tour

test suite PHPUnit 11

Consider it working now Drupal 11 preparations and https://github.com/skilld-labs/skilld-docker-container/issues/461

https://www.drupal.org/project/big_pipe_sessionless/issues/3428235#comment-15703944
drupal/block_content_permissions
drupal/coffee
drupal/config_override_warn
drupal/custom_pub
drupal/formblock
drupal/layout_builder_modal
drupal/layout_builder_restrictions
drupal/layout_library
drupal/layout_paragraphs
drupal/log_stdout
drupal/manage_display
drupal/menu_admin_per_menu
drupal/menu_link_attributes
drupal/panels
drupal/panels_everywhere
drupal/paragraphs waiting for release
drupal/password_policy
drupal/pathauto
drupal/private_files_download_permission
drupal/redirect
drupal/remove_http_headers
drupal/role_delegation
drupal/seckit


gnused: 4.5 -> 4.7

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gnused/versions.
meta.description for gnused is: '"GNU sed, a batch stream editor"'.

Checks done (click to expand)

built on NixOS
/nix/store/d1zryd5rhvn10k7my3rbhb1jr7zfp6iz-gnused-4.7/bin/sed passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 4.7 with grep in /nix/store/d1zryd5rhvn10k7my3rbhb1jr7zfp6iz-gnused-4.7
directory tree listing: https://gist.github.com/c0329290d66163156c600128947c22ab
du listing: https://gist.github.com/8b1d27fd6c2aaa693e5560c49c3b122c

Rebuild report (if merged into master) (click to expand)

83742 total rebuild path(s)
27151 package rebuild(s)
26995 x86_64-linux rebuild(s)
21148 i686-linux rebuild(s)
15126 x86_64-darwin rebuild(s)
20473 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
AMB-plugins
AgdaSheaves
AgdaStdlib
CoinMP
DisnixWebService
EBTKS
EmptyEpsilon
FIL-plugins
Fabric
LASzip
Literate
MMA
NSPlist
OVMF
OVMF-CSM
PlistCpp
QuadProgpp
R
SDL
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_ttf
SDL_gfx
SDL_image
SDL_mixer
SDL_net
SDL_sixel
SDL_sound
SDL_stretch
SDL_ttf
SkypeExport
TotalParserCombinators
Xaw3d
_1password
_2048-in-terminal
_20kly
_2bwm
_389-ds-base
_90secondportraits
_915resolution
_9pfs
a2jmidid
a2ps
a52dec
aacgain
aacskeys
aalib

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d1zryd5rhvn10k7my3rbhb1jr7zfp6iz-gnused-4.7 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A gnused https://github.com/r-ryantm/nixpkgs/archive/95e850f881ae53a936fb9c59d7d67f7228f016cd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d1zryd5rhvn10k7my3rbhb1jr7zfp6iz-gnused-4.7
ls -la /nix/store/d1zryd5rhvn10k7my3rbhb1jr7zfp6iz-gnused-4.7/bin

Duplicate of https://github.com/NixOS/nixpkgs/pull/52576


Add query_arrow_stream

Summary
Adds a query_arrow_stream call that returns a generator that returns pyarrow.Table objects.
Issue #155
Checklist
Delete items not relevant to your PR:

[x] Unit and integration tests covering the common scenarios were added
[ ] A human-readable description of the changes was provided to include in CHANGELOG
[ ] For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Off topic but could we get a contributing guide? I'm not used to pylint and I feel like I'm being continually pranked :(

Sorry about the lint.  Quick and dirty from the Github action:
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install setuptools wheel
          pip install -r tests/test_requirements.txt
          pip install pylint
          python setup.py build_ext --inplace
      - name: Run Pylint
        run: |
          pylint clickhouse_connect
          pylint tests
          pylint examples

This looks awesome by the way, really appreciate it.


fix tests broken by auth refactor

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2164/
Test PASSed.


No result after yaws_api:parse_post(A) on MacOS Mojave

Just installed Yaws from scratch (from git repository, master branch) and got this result on yaws_api:parse_post [{[],undefined}] and all data is in result of yaws_api:parse_query.
The environment:

MacOS Mojave
Erlang/OTP 22 [erts-10.5]
Yaws from current state of master branch from Github Yaws 2.0.7

The HTTP POST request is:
POST /api/post_form?Name=3533&Age=2352353&Formula=235325352 HTTP/1.1 Content-Type: application/x-www-form-urlencoded Host: local.universal.backend:8080 Connection: close Content-Length: 0
The out() code is:
out(Yaws_arguments) -> 	io:format("Parsed POST data: ~p~n", [yaws_api:parse_post(Yaws_arguments)]), 	io:format("Parsed query data: ~p~n",[yaws_api:parse_query(Yaws_arguments)]), 	[ 		a_http_headers:cache(no), 		{ehtml,[ 			{pre,[],"1"} 		]} 	].
When I send GET request I see this in console:
Parsed POST data: [] Parsed query data: [{"Name","3533"},{"Age","2352353"},{"Formula","235325352"}]
When I send POST request I see this in console:
Parsed POST data: [{[],undefined}] Parsed query data: [{"Name","3533"},{"Age","2352353"},{"Formula","235325352"}]

Thanks for the details, I'll take a closer look.

OK, I've reviewed your issue and have duplicated what you're seeing, but Yaws is operating correctly. Here's the relevant part of the Yaws PDF documentation (which is generated from source file yaws.tex:

The differences between using the query part of the URL and a form are the following:

Using the query arg works with any kind of requests. We parse the query argument with the function yaws_api:parse_query(Arg)
If we use a form and POST the user data the client will transmit the user data in the body of the request.  That is, the client sends a request to get the page using the POST method and it then attaches the user data—encoded—into the body of the request.

A POST request can have a query part in its URL as well as user data in the body.

Preceding this text is an example that shows how yaws_api:parse_post/1 is used to handle the encoded data in the body of the POST.
Try changing your POST request to the following:
POST /api/post_form HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Host: local.universal.backend:8080
Connection: close
Content-Length: 39

Name=3533&Age=2352353&Formula=235325352

and then your appmod will print:
Parsed POST data: [{"Name","3533"},{"Age","2352353"},{"Formula","235325352"}]
Parsed query data: []

If my previous reply addresses your issue @alexandrkirilov please close the issue, but if you have further comments or questions, feel free to add them.

My apology for delay of closing this issue. This issue totally my bad. I've been using Yaws since 2012, but not last year. All of it forgotten.

Thanks, and no worries. I thought you might just be experimenting with my reply and maybe had some more questions.


Easier publishing

Use case
The current procedure for publishing an application to the Google Play Store is very tedious to setup and prone to many mistakes.
Likewise when you want to share a proof-of-concept application without going through the Google Play Store is also very tedious.
Proposal

Add a command line command to automate most of the publishing setup.
Add a command line command to easily build an "unofficial" app to share and install directly on a device (without going through the Play Store).

The output of flutter build apk can easily be shared and manually installed. Have you run into issues with this?
We can't really automate publishing for a variety of reasons. What particular steps do you find difficult?

Yeah I found it, its def easier.
https://flutter.dev/docs/deployment/android
I'm referring to that article,

Most of those steps require human input/decisions. For example, Its not reasonable for the flutter tool to generate a release config for you automatically.
Could you be more specific on which parts you're having trouble with?

Its not that I'm having problems, its jsut tedious. For example editing the AndroidManifest.xml file is error prone if you happen to change the com.example.YOUR-APP-NAME I had an app brick and crash on run just because of that.
Generating and using a keystore can also be automated and having the resulting .jks file managed is much better than having to manually create files.
The docs are also very misleading when it comes to building APKs with the bundletool, turns out its completely unnecessary (as I found out 20mins after posting this issue).

Hi @Ravenheart
You can change your Android package using Android Studio refractor solution
Can you link the docs you referring? Explain the issue
Thank you

I am using VSCode, the articles is this one: https://flutter.dev/docs/deployment/android
Its very weird having your package named "com.example.YOUR-APP" and changing that breaking the whole app. It should either be replaced with some generic "dev.flutter.YOUR-APP" name or allow us to change it to the proper name.

Hi @Ravenheart
Whenever you create a new project, you can specify android package name so you need to change it later.  Check out this answer and if needed to change, you can easily change it using refractor in Android Studio without breaking the app.
Example
flutter create --org dev.flutter.app_name app_name

Testing your appbudle using bundletool is not required
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


ls -k

Option is listed in one place, but not in the other and the tool doesn't seem to support it (least I haven't seen an FLAG(k) in the code)

sounds good, thanks for confirming


Too many changes warning is too persistent and in the wrong place

I checked-out an old commit from 7 years ago (a8c629dd0fd99c1eedfc804266ca18942cfada5c). The SCM view got stuck displaying the "busy" badge and showed many file changes, along with a warning about too many changes.
When I changed views, the warning stuck around even on top of other view containers. Eventually, it moved into the top right corner. The SCM view now appears to be permanently busy.

That does not look good. I am also able to reproduce in Stable so I believe that this was broken last milestone.
It's very easy to reproduce by setting git.statusLimit to 3 and then making changes to 4 files.

Adding @benibenj and @TylerLeonhardt to see if this rings a bell for them as the made changes to IContextViewService recently. Based on my tests, this worked fine in 1.87 but it's broken with 1.88. I stepped through the SCM code and it seems that no changes in execution there.

I didn't do any crazy changes there AFAIK, I feel like @benibenj was maybe more in there so could you take a look first?

Found the culprit #207520. Fix it with #211219

It turns out the fix actually breaks hovers entirely. @TylerLeonhardt you turned the disposable into a MutableDisposable which I believe does not work in this context. I think we should revert https://github.com/microsoft/vscode/pull/207520/commits/09d9b060a3eff4a3db0a19533ba8dfb01846a51c.

@benibenj I can drive reverting that commit but think this should be revisited in debt week as we have disposables there not getting disposed of.

Thank you @benibenj and @TylerLeonhardt.

@TylerLeonhardt I had a closer look at the code. The concept of using disposables for this case was flawed from the start. I created a fix for it.


Stricter types for JSON

lib Update Request
Configuration Check
My compilation target is ES2015 and my lib is the default.
Missing / Incorrect Definition
JSON.parse() and JSON.stringify()
The definitions for both of these functions currently accept a string, but this is not strict enough. Not all strings can be parsed or stringified. Many of these can be caught at a type level, meaning they could and should be added to the type definitions.
Sample Code
// @ts-expect-error
JSON.parse('')

// @ts-expect-error
JSON.parse("'foo'");

// @ts-expect-error
JSON.parse("[1, 2, 3, 4, ]");

// @ts-expect-error
JSON.parse('?')

// @ts-expect-error
JSON.parse("bar")

// @ts-expect-error
JSON.stringify({
    key: 2n
})

const circularReference: { myself?: any } = {};
circularReference.myself = circularReference;

// @ts-expect-error
JSON.stringify(circularReference)

TS Playground: https://www.typescriptlang.org/play?target=99#code/PTAEAEBcGcFoFMAeAHeBjSCBOWD2WAoAKQGUB5AOQDpkBDLaeACgHIWBKAgkCGBFdJng58xctToNmAIhYAzXLhbT2Abi48ocJKgzY8hUpRr1GTaQG0AjABpQAJjsBmOwBY7AXRXruYLf10hEUNxEylWAH4ODT8+HUF9USMJUxkAI3oVGN5tAT1hAzFjaEgsAEsAOwBzMrkATyYAbwJQVtAAa3g6gC4HCoIAX04CNFwKktA0Mqw0AFcAG3oAJXg5YXgKtHhextAAWzrGebkI3toKutAB0ABeUEaB9SmZheXV9c34KgOjuVvJ6ZzRZYFZrLAbLY+TRxPJBQrJKglcrVWoNZ5At5giHwThAA
Documentation Link
JSON
JSON.parse
JSON.stringify

This doesn’t seem very useful; it only works if you’re passing string literals to ‘JSON.parse()`, so the improved type checking is purely academic.  Also, how do you propose to detect circular references at type level without excluding valid recursive structures?

This doesn’t seem very useful; it only works if you’re passing string literals to JSON.parse()—it’s not possible to make a “JSON-compatible string” type without relying on generic inference—so the improved type checking is purely academic. Also, how do you propose to detect circular references at type level without excluding valid recursive structures?

You are mistaken.
https://www.typescriptlang.org/play?target=7#code/C4TwDgpgBAwglgJwMYFcA2BDBAlCAzCBCAOyQgB4AVAPigF4oBvAKCjagG0BrCEALigBnYAjjEA5lAA+UYigC2AI0LShIJQHs0AXQGVmAX2ahIUACJxBGNGg0B3CABMAUgGUA8gDkAClkERKCAAPYHooAHJw1QADABJGYVEJA3jwgBptKJl0gyyItKhM1XSoXINo43BoCysbeyc3LwA1axQKGjDFOHExUJkWdk4efiERMUkZOSUVGUF1RS1dKC6e4mBDVXhkdCxcAiJSdupmStMAQTqHFw8fPwDg0IZwkTa88Lxrfze5Gzy4ximygQ5RiACJ4olxgZQdEYhwIWNktpYTJoowEUlxAZyideoQPmQoI1PAB9dwANyIokc0AG7AA9AAqRmsQaM2AaYjkwjAQRQDBEjDkjCuJCiMChdyKABWECQoU8GmAGGAcE5UAAFMSAJSjTFQXoafnEKAaGVy4AAOlZ7HZAAEwFgMPIoMAHlAzlBhWg4I4iTc9eNrYMoPbHQhnVAiOS4NyEB6oHgUKRVergAALFWuiPEQR4DQIeR8jPQIiCdC8y1QSjpyyJ5PytUmutIaxoJyJgtQCAYJDpqDyCDTeMaPCu9PQM2y+XBtlQACSY4Fg+HUCQnOVYj5xAgwg7U4tggKJdku7dfoP8r5WGgIgwufzhY7ykft4nUHDJFCl9CllntvpG0PzuKhuxCEhHD5SEJGoDU3RCPQwLdYhIPMSw23qa4vF8BB-ECEIoAAflPOMoEQh4IL5C5bCuYkcLw91iMoMiSMIApo1jQhCIEODa0EAR7xAAphgEaDxAKb02gE4gQF1OhaEE7VpJAABuICmRZEN2RgTk415flBWFUVxVCSTbyNAVnCFEUxTgCUoClacFSVFUm01HVAwkf82DDJ0XTMhMrKM2z7LMgoUHLNsQGNU1zXlU14ywCMhNdI1lDXXSeScbzQygB0-KjCAwEwMh409JMUzcjMszvB8CyLcdS13CtBBy3yIxdQRHUJM5HFQsQaTWVzOQKOxazdIRuogAp7z9H0d2WIgMC4NdMwjeVCGLI0TyIYAUAQYgAFoAuJV13WAI15GW6A4FCHtBDgFQLsKjBHDawDBjEuA8BAKhYLM8jwJQvkagw2ibhaNA2j+ojWPjPR2KKkquJ4jNLGU4TeFExFxK9VoIGUuSFJkgout7CBuM8iZZAUIElKptTBg0oDcp0rkeWvQybJMvGofMgygu5uzJTi5zlVTE0tRuXUxLavLw0jALPUF4zhd5tpwsimxovvWKnIS-kEGS480ugdd2YQc85fyjrCuK8mypNJKMGi0cqevFCaeHYtM1CXt9IwD3+TAMAEA0bk5ssUJHyECB20bCRGr1i0PzDyBLcen2szsOAbGWaAvrwR63pZ9rIzJnq+r5Aav2G4hRvGguppmz35ugRQlpWvsnQ23DUqT3b9qOk6A3g0JnqungDTuwPHvjZ6lpLrSPvYQvfpoDUAerJDKLQ2oaIaCH8Zh4id1IhG7eRhBKY1QEZip7UOG0VQfjQUmpspsSX9pwh6bEtSjDMBpEgTARAMq5lCMSMklJCC+gJv6Lw0CqRwJOMwek9I8q8kOsESA8psFGwLMwKBFJkE0ktOGfwGpIjahOOgzBghsFBFwcAfBYcEBEJuEg2BZCKEQA1KCd4GgNDhFBNqNSaCMF2iwTgi0rDCHEJgdSCA5C7j8I4AARgKAAJgKAAZgKAAFgKNoUR4i6FSIYTIvBhA2EcMQSQ7hyjeFUMIuEGhEj6GMOYXI9hCjSFONUaCRQWBRG0MkdIphsibHyM4Q4pRlo14ajpGwESUAtHEEMO482wg1yIFQKAvYhASBkAEIwAcIB-BoDwJTQSpQwiMAMGpJAeSdg4HwEUw4lp5AVLjmOBgzTtgFPaQcMgZjwmWMidYghvjYmKLgQknG30QAagGfk3YwzikQG1EAA

That would exclude a ton of perfectly JSON-able objects.

That would exclude a ton of perfectly JSON-able objects.

For example?

@fatcerberus can you provide an example of something which this PR does not correctly parse or stringify?
Here you will find examples of a tree structure being parsed and stringified correctly:

My point was, your types are excluding .myself on the basis that it could be a self-reference.  That’s way too strict.  As for JSON.parse, those stop being useful the minute you start passing string variables to it instead of hard-coded strings.

My point was, your types are excluding .myself on the basis that it could be a self-reference. That’s way too strict. As for JSON.parse, those stop being useful the minute you start passing string variables to it instead of hard-coded strings.

const emptyString = ''
JSON.parse(emptyString) // no error

Cases in point:
const circularReference: { myself?: any } = {};
circularReference.myself = { foo: 812 };
JSON_Override.stringify(circularReference);  // error?!

const str = '{ "foo": "validJSON" }';  // pretend this was read from a file...
JSON_Override.parse(str);  // error. this is not useful.

The types only exist at compile time.  It seems like you might not fully understand how the type system works?

let str = '{ "foo": "validJSON" }';
JSON_Override.parse(str);  // error

let str = '{ "foo": "validJSON" }';
JSON_Override.parse(str);  // error

Like I said, these extra checks only work if you're passing literal-typed strings to parse.

you're just pasting code and adding // error
here is a TS Playground which shows that JSON_Override.parse(str); is not an error
If you can reproduce erroneous behaviour in TS Playground, feel free to send it.

It absolutely is an error.  You changed the let to const.

I used the const from your original comment

I can see that there is an error with let
I will investigate that

If you know your string statically at compile time, why do you need to parse it anyway?

@Josh-Cena A case might be using JSON.parse to load large objects. Might be practical in browsers with low performance computers.

@brunocrosier
https://262.ecma-international.org/6.0/#sec-json.parse
TL;DR: any JavaScript-like expression is a valid JSON
According to this, all of the values you provided should be parsable, including the empty string

For the record, “this isn’t a useful change” and “this demonstrates a misunderstanding of how TypeScript works” are mere observations and don’t constitute CoC violations.  I think it’s fair to criticize a feature request on those grounds, no?
Anyway: types are not values, and they exist only at compile time.  The proposed checks for JSON.parse only work when the compiler has a way to know, at compile-time, exactly what is being passed to that function—because your proposed types, besides rejecting ill-formed JSON string literals, also disallow passing any variable typed as string.  That’s not a useful behavior and would make the function very painful to use for almost all real-world use cases.

Your implementation of "JSON_Override" wrongly prevents leading or tailing whitespace characters.

Your implementation of "JSON_Override" wrongly prevents leading or tailing whitespace characters.
In general, as mentioned, this only works for string literals. A very narrow use case, but a whole buttload of added complexity, resulting in compilation slowdown and breaking changes (added global types). Especially such a generic name like CircularReference is a really bad idea.

I'm not sure why CircularReference is a bad idea. As long as the context is clear in the type file, it shouldn't matter at all

It has such a generic name, odds are such a name is already in use, resulting in a breaking change. The introduction of such a utility type also means the team can't update it in the future (if a new feature would be better suited for such a type), without causing yet another breaking change (see Omit<>). And the team has the position to not add new utility types, unless they're required for declaration emit purposes. See https://github.com/microsoft/TypeScript/issues/39522#issuecomment-656201388:

We've opted to not include utility type aliases in the lib unless they're required for declaration emit purposes.

You are right. At the moment, the types in this PR at the moment are too strict - particularly because of AllowedJSONParseText.
I still believe there is a lot of benefit in disallowing the parsing of an empty string, or the stringification of a bigint
What about something like this? It disallows values we know cannot be parsed / stringified (as opposed to the previous solution which would try to codify the allowed ones as a type and resolve to never otherwise)
TS Playground

That's a good point re: the replacer.
How about this?

[x] No utility types
[x] Only updates JSON.parse to disallow arguments we know cannot be parsed

I'm no member of the TypeScript team, so I have no say. But I don't see the point in vastly overcomplicating these types for a negligible use case. This would only work for inferred string literal types, and I can't think of a reason why you would pass a string literal to JSON.parse() instead of having the object literal directly.
Honestly, this would be much better suited as an ESLint rule.

Yeah, you're right actually. My bad


Simply paste the selected entry with Enter

Before Submitting Your Feature Request

[X] Check that there isn't already a similar feature request to avoid creating a duplicate.
[X] I have seen the FAQ.

Problem
Coming from Windows, I am used to pressing Windows + v to open the clipboard menu, selecting the entry I want to paste and then hit Enter to paste it ✅
With Maccy, for some reason I need to use command + enter. Why not make this configurable so I can simply use Enter to paste the selected entry?
👋🏻
Solution
No response

I had already done that - for some reason it did not work. It is working now 🤔🤷🏼 Thanks


Update radio buttons

Description
This PR updates all the radio buttons in the app to match the design.
Screenshot

PR submission checklist

[ ] I have tested single choice account selection
[ ] I have tested specific assets adding from account third party deposits settings
[ ] I have tested backup selection from restore backup screen
[ ] I have tested persona selection from dApp login screen

Just the radio buttons in customise fees seem a bit bigger.

Good catch.  Thanks!


Hello Eddie, wanted to part of this community

Hello there! first test issue in this community!

happy Engineers Day - ❤ from Nepal

Yay!

Hey @NirmalSilwal 😃, if you want to join the community open an issue in the support repo and add the "invite me to the organization" label. We have a FAQ for that question here 👍.
I'm glad you want to be a part of the community and contribute to open source. If you want to contribute with a new repository idea and a different stack, or add features to existing repos, we are more than welcome to help you do it 😃.

Hi @BOLT04 thank you for the clarification.
I am more than happy to be the  part of this organization. Looking forward to contribute.

@NirmalSilwal great screenshot 👍 .
Thanks @BOLT04 👍
@NirmalSilwal I see you are part of our community Github organisation now - if you have any issues let me know 🤓

yeah, thank you @eddiejaoude for having me in the organization 👍


Improve bidirectional solver

The CNF implementation for computing smallest bidirectional macro scheme is improved from O(n^4) total size to O(n^3).

@hdbn  Could you merge the latest main branch into this branch since we enabled CIs for pull requests in https://github.com/kg86/satcomp/pull/8?


Cut support for node < 4.0

Travis-ci build hangs on node 0.12 (but strangely works on node 0.10). Node 0.12 is now "end of life" so I'm bumping the minimal node version to 4.0.
Note: streamline may still work on older node versions, and you will only get a warning during install, but I won't be supporting it on versions < 4.0.

See 83dbb9c946d0a18d0029cfab17eac8c4c30dfceb


Possible to customize entire appbar/toolbar?

Hello, I was wondering if it is possible to customize the entire appbar/toolbar and replace it with a custom one (e.g. inflating it from some XML) and manually connecting the new buttons to the Crop Activity's callbacks.
Is this something that can be done? If so, could you link me to some helpful resources? Thanks!

You can use CropImageView in your custom activity: https://github.com/ArthurHub/Android-Image-Cropper/wiki/Using-CropImageView-in-own-Activity


Removing users in case of a security incident

Initially, this PR was adding one new page - "Removing users in case of a security incident", but after some discussions with @plaindocs, we decided that that new page should go into a "Security" section in Pipelines, but there was no "Security" section in Pipelines yet.
Now, this PR:

"Security" section in Pipelines
Adds "Removing users in case of a security incident" page in the Security section
Moves https://buildkite.com/docs/pipelines/secrets to the Security section
Moves https://buildkite.com/docs/pipelines/incoming-webhooks to the Security section
Moves https://buildkite.com/docs/pipelines/permissions to the Security section
Moves https://buildkite.com/docs/pipelines/audit-log to the Security section
Updates the sidebar accordingly

Please take a look at this PR, @plaindocs.
I don't understand what are the linter's problems with this PR as it doesn't appear to have trailing whitespace when I inspect the document in the editor. 🤔

Do you need to escape the - in the mail address?

@plaindocs please take another look at this one.

Let's rename the PR and put a small description in now we're making bigger changes.
I like how this looks, although not sure about Webhooks, maybe we need to split out the security content there. I'll dig in tomorrow.

Let's rename the PR and put a small description in now we're making bigger changes.
Yep, will do, @plaindocs!
not sure about Webhooks, maybe we need to split out the security content there.
The whole incoming webhooks page is basically the security of the incoming webhook page & it says so in the very first paragraph. So maybe let's just rename it, too.

@plaindocs! Ah, okay, I'm merging these two together & then merging the PR when (if! hahaha) the tests pass. Thanks for the review!


Stashes disappear after clicking the "pop" icon

V4.0.0
Something seems to have changed as popping via GUI seems to delete the stash, previously the stash was still there after popping.

Hi @sbungert-mms. If I understood correctly that's the expected behavior. To extract the changes from a stash without removing it from the stack you can use the  'Apply...' action (available via right click over the stash item on the tree). Would you let me know if that fixes the issue for you?

I thought about that before but never implemented it. I'll add it for the next release.


Remove L2 plugin parent class.

This removes the NeutronDbPluginV2 class from the
inheritance hierarchy. It also adds a weak reference
to the ML2 core plugin, and uses that reference to
call the methods that were previously inherited
from the NeutronDbPluginV2 class. It also addresses
some problems with the l3 plugin unit tests (still
can't run them individually using tox, but they will
run when .tox/py27/bin/activate is sourced and
python -m testtools.run is used).
Signed-off-by: Thomas Bachman<EMAIL_ADDRESS>

LGTM.

I'm going to provide a new one, addressing Bob's changes. Thanks!


Go runtime on Amazon Linux 2 is not documented

Hi,
Recently, Go runtime on Amazon Linux 2 is announced.
https://aws.amazon.com/about-aws/whats-new/2020/08/aws-lambda-supports-go-amazon-linux-2/
But, I can't find Amazon Linux 2 in the Go runtimes section.
https://github.com/awsdocs/aws-lambda-developer-guide/blame/0168ba0ea389592df2e41f9666850c4fa79ac6f1/doc_source/lambda-golang.md#L8-L10
The announce says that select provided.al2 ("provide your own bootstrap on Amazon Linux 2 runtime") to use Go runtime on Amazon Linux 2, but the example of deployment package still uses the go1.x runtime that is on Amazon Linux.
https://github.com/awsdocs/aws-lambda-developer-guide/blame/main/doc_source/golang-package.md#L21-L26
Where can I found the documents about Go runtime on Amazon Linux 2?

We do not have these instructions in the documentation yet, but there is a blog post that shows how to build Go functions on provided.al2 using SAM:
https://aws.amazon.com/blogs/compute/migrating-aws-lambda-functions-to-al2/


Fixed all merge errors. + added better images

Now git is showing more merge errors from my past commits.  Don’t worry, you can still create the pull request.
https://github.com/OpenCodeEra/OpenCodeEra/assets/129188028/baa1802e-ab6f-499d-809c-d40539807396

Give me some time to fix these merge errors.

The code was correct but not optimal


[Node] check if problem on Mac OS is relevant to us

We need to check with load is affected by similar issue is discussed here:
https://github.com/MetacoSA/NBitcoin/issues/345
https://github.com/MetacoSA/NBitcoin/commit/6ae1452e8e5252f3ea7aee3028d882199fe8e66a

i don't know, that code is completely different, so it might or might not, we need to check that  first before doing anything

In Bitcoin, the buffer sizes are the same as we have in our code.
For example for the receive buffer we have ReceiveBufferSize = 1000 * 5000;
In bitcoin, the DEFAULT_MAXRECEIVEBUFFER is 5000 and the seeting is set to 1000 * DEFAULT_MAXRECEIVEBUFFER.
Same values in this doc here: https://en.bitcoin.it/wiki/Running_Bitcoin.

Also, we're supporting Sierra and up and this error seems to affect Sierra and previous versions so the range of affected OSes that are affected is smaller.

From here it seems this is only a problem for VMs with memory < 8 GB: https://github.com/MetacoSA/NBitcoin/issues/345#issuecomment-369000907

My view is that we should close it and readdress if we see it in the wild.

Though it wouldn't hurt to just change one constant in the network peer constructor. Would there be any disadvantage of doing so?

Would there be any disadvantage of doing so?

Not that I can think of.
The buffers will be bigger so will take more space, but that's about it.
It might be hard to test as we'll need to find a Mac with Sierra and < 8 GB which might be tricky.
Happy either way, should take 5 sec to fix and 1h to test it didn't break anything.

I can fix it and test with my Windows box but I don't have a Mac to test with

Should note this change makes the buffers smaller not bigger. 5,000,000 -> 1,048,576 So I would expect if anything it might effect performance. I created a PR if you guys want to give it a whirl. I'm going to run some tests on it myself.

I would go for it, it should be trivial and I can't see any disadvantages.

ah yes indeed thanks @mikedennis, we're making the buffer to accommodate more platforms.

I can't see any disadvantages.
It might affect performance because the buffer is made smaller to cater for old versions of Mac.

Not sure why we need this:
Bitcoin doesn't have this limitation, and we're limiting every platform just to cater for Macs with < 8GB Ram.

I'm ok with that. Let's see what @mikedennis's tests yield.

Assigned myself as I can't assign @mikedennis so people see it's not free to take.


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Thanks!


Community Ideas

I'd like to collect the ideas from various discussions here to have a central place of discussion for what's on the table.

[x] Hide big submit form behind button (thx @nithinbekal)
[x] Make it clear that the title is tweeted after publication (thx @joekain)
[x] Make it clear that user names refer to GitHub accounts (thx @dbeck)

Let's hear how we can improve further! :+1:

The text in this screenshot is misleading because it suggests that my post will go to twitter referring to my twitter account. This is an issue for those like me who has different account name on github (dbeck) and twitter (@dbeck74).

Very true.
My idea would be the following: We add an octocat to the username to make it clear that these are GitHub users. I would not want to use real names here, nobody remembers "René Föhring" but some people might remember "rrrene", especially if they read it in pirate-voice.
We furthermore remove the "by @elixirstatus" part from the title placeholder, because this indeed refers to a Twitter account which is really misleading. The important message in the placeholder should be that it will be tweeted and should be phrased to suit that.

Here are a couple suggestions that I'd be willing to help with:

Add an optional Twitter handle field for the author so that via @handle is included in the tweet, adding author attribution on that platform.
Not sure of the exact UX flow here, but once a hyperlink is referenced, it would be nice if the site automatically grabbed meta information for the link, title and description mostly. This would improve the posting flow, reducing friction for actually posting.

I'm not sure if these have been suggested before elsewhere (currently on mobile), but let me know your thoughts.

Hi Shane,

Twitter handle: I think this could be a great addition. http://rubydaily.org/ has this as well and this feature would promote the coder's Twitter account for those interested.
Fetching link meta data: Could you elaborate on that? So while I'm typing my announcement in Markdown, then I am pasting a link to Github or my blog. What should happen "behind the scenes" and how should the UI react?

I really appreciate your input!

HI There,
For the meta data I would suggest to look at twitter card meta tags.
Best regards,  David
sent from my too smart phone.
sorry for the typos.
2015. aug. 16. 15:51 ezt írta ("René Föhring" notifications@github.com):

Hi Shane,

Twitter handle: I think this could be a great addition.
http://rubydaily.org/ has this as well and this feature would promote
the coder's Twitter account for those interested.
Fetching link meta data: Could you elaborate on that? So while I'm
typing my announcement in Markdown, then I am pasting a link to Github or
my blog. What should happen "behind the scenes" and how should the UI react?

I really appreciate your input!
—
Reply to this email directly or view it on GitHub
https://github.com/rrrene/elixirstatus-web/issues/25#issuecomment-131553728
.

And/or Open Graph ?

Yep. That one too :-)
sent from my too smart phone.
sorry for the typos.
2015. aug. 16. 17:04 ezt írta ("Udo Kramer" notifications@github.com):

And/or Open Graph http://ogp.me ?
—
Reply to this email directly or view it on GitHub
https://github.com/rrrene/elixirstatus-web/issues/25#issuecomment-131570055
.

Maybe I should have phrased that second part better:  (this got long fast, sorry for that)
It's clear that you can extract meta description and title from webpages. What was not entirely clear to me is what @slogsdon supposed to do with it.
If the suggestion is to use that data to auto-fill the announcement then I am not sure that is a good idea. @slogsdon's blog post is perfect for the suggested "auto-fill" functionality, but most announcements posted to ElixirStatus aren't.
Let me illustrate using two recent announcements written on elixirstatus.com recently:
Example 1:
# InchEx v0.4.0 released

I just released v0.4.0 of InchEx which brings Elixir v1.1 compatibility.

InchEx provides a Mix task to evaluate your inline docs and show you where they can be improved. Its `inchci.add` task can be used to add Elixir projects to Inch CI.

If we took the meta descriptions, it would contain GitHub's standard repo information:
# rrrene/inch_ex

inch_ex - Provides a Mix task that gives you hints where to improve your inline docs.

It loses the important message ("new version" and "Elixir v1.1 compatibility").

Example 2:
# P2P WebRTC file sharing app: Broker using Phoenix

In this blog post we discuss the few design decision that was taken in building a simple broker (in Phoenix) for connecting multiple browsers using WebRTC.

http://www.zohaib.me/p2p-webrtc-file-sharing-app-broker-using-phoenix/

I love both the article and the "appetizer" @zabirauf provided in the announcement. Using meta information it could have looked like this:
# P2P WebRTC file sharing app: Broker using Phoenix

WebRTC was created primarily for video and voice communication but it has the API to send raw binary data between two browsers as well. This opens up a lot of opportunities to create more peer to peer web application which...

Not terrible, but the hand-written version is so much better (as it should be) ...

Possible compromise
Announcements like this:
# How to add and test HTTP basic authentication in a Phoenix app

http://www.cultivatehq.com/posts/add-basic-authentication-to-a-phoenix-application/

that only contain a link could be transformed into something akin to Twitter cards.

@slogsdon @dbeck @optikfluffel What do you think?

@rrrene There are a couple of ways to handle this that I was thinking about originally.
Your possible compromise idea is definitely a good open for posts that contain only a link. This is also similar to one of the options I was thinking of when suggesting this in the first place, which is to display the grabbed meta data independent of the poster's content. Facebook and Google+ currently have the ability to do this for posted links.
Another, simpler option is to provide a "Suggest" button to the poster that would be entirely opt-in. The button would go grab the meta data and inject it into the title/description fields for the poster to edit as they see fit. Reddit has this ability for link posts, although it is limited to the title only since they do not allow accompanying text descriptions on link posts.

@slogsdon I certainly find the idea appealing, esp. as extra information about the posted links. It is a feature I like alot in chat apps, when they give you a preview of posted links.
The only thing I am uncertain about is how we implement this visually, on the frontend side, in a way that does not look "tacked on".

@slogsdon I just added the ability to add your Twitter handle on ElixirStatus. :+1:
@dbeck This might be interesting for you as well!

@rrrene thanks for the heads up! I appreciate this feature a lot, and of course your initiative from day one :)

Having a expertise level for the post might be useful like PragProg . Example link - https://pragprog.com/book/phoenix/programming-phoenix

@sairam This is an appealing idea. I would have one concern: Who would be the judge of that? The author?

It could be the author at first, but may be later readers can suggest where
it'd fit properly.
On Jan 4, 2016 12:43 AM, "René Föhring"<EMAIL_ADDRESS>wrote:

@sairam https://github.com/sairam This is an appealing idea. I would
have one concern: Who would be the judge of that? The author?
—
Reply to this email directly or view it on GitHub
https://github.com/rrrene/elixirstatus-web/issues/25#issuecomment-168532287
.


preprocess dataset & t2v training

I saw in the README that it can be used to train two models, class-conditional and unconditional Latte, using the FaceForensics dataset. Do I need to do any additional preprocessing on the FaceForensics dataset? In what form should I organize the data in the FaceForensics dataset?
In addition, how to train the t2v model?

I saw in the README that it can be used to train two models, class-conditional and unconditional Latte, using the FaceForensics dataset. Do I need to do any additional preprocessing on the FaceForensics dataset? In what form should I organize the data in the FaceForensics dataset? In addition, how to train the t2v model?

Hi, please refer to the pre-processing method provided in stylegan-v to process FaceForensics. The dataloader for FaceForensics is provided in Latte. A parameter data_path in the ffs_train.yaml  is /path/to/datasets/preprocess_ffs/train/videos/, which contains all videos in this folder.
As for the training code for T2V, please refer to https://github.com/maxin-cn/Latte/issues/4#issuecomment-1882255657.

How to download the FFS dataset？The original way is broken, could somebody give me a drive link?

求求你们了哥哥

求求你们了哥哥

https://huggingface.co/datasets/maxin-cn/FaceForensics


Importing a scenario from ETM into ETLoader does not work anymore

http://ivy.et-engine.com/testing_grounds/import crashes for me when I import a scaled scenario with the default topology.

Fixed with a new deploy.

I take that back, it's still failing when importing scenario 404841. Looking into it...


Query Subgraph for a single retirement

Description
This is the follow-up step on this PR.
Please review the latter first 🙏
This PR queries the subgraph with fetch and generates a Single page of a retirement for a specific address and index.
This is how I would continue the implementation.
=> See a generated page here
Further steps

[ ] Discuss how we get missing data from subgraph (certificate, PDF, retiree name)
[ ] Style and build the pages according to Figma Designs

Related Ticket
Part of https://github.com/KlimaDAO/klimadao/issues/345
Checklist

[x] Building the site with npm run build-site works without errors
[x] Building the app with npm run build-app works without errors
[x] I formatted JS and TS files with running npm run format-all

@ladytrekker when I log the code locally it seems like the subgraph returns 0 results no matter what index I put in. Am I doing something wrong?

@ladytrekker when I log the code locally it seems like the subgraph returns 0 results no matter what index I put in. Am I doing something wrong?

I DM you links from your test wallet which work
And yes, some queries do not work.
I can show the issue you later in the playground.


(Macrostrat web v5) Server-side reloading

Our "server-side-reloading" version of Macrostrat's core app is now the active site for all development for Macrostrat  v2. So we need to shift development to the main branch. This shifts us to Version 5 of Macrostrat's app.
The key improvement here is multiple independent pages in the same app. We're hoping to knit all of Macrostrat's public-facing user interfaces into this structure.
Tasks

[ ] Create a branch for the v4 app (legacy Webpack compilation toolchain)
[ ] Create a branch for the v4 app (modern Vite compilation toolchain)

Created new branches v4, [legacy-single-page-app](https://github.com/UW-Macrostrat/web/tree/legacy-single-page-app], and [v4-webpack](https://github.com/UW-Macrostrat/web/tree/v4-webpack] to record the changepoint to a new paradigm here.


Autosave / Crash Recovery

I've just lost another 30 minutes of work in Material Maker due to a random crash and the fact that I got into a flow and forgot to compulsively smash Ctrl+S every time I do anything,
Please. For the sake of mental health - implement a crash recovery system that'll automatically save progress every minute and prompt users to restore the autosave copy when the program is run again after the crash.

I'd rather have a crashless Material Maker, but this is just too easy to implement.

Well, we all would prefer that :D
And I really appreciate your work - I've been looking for such a program for years, and I've finally found it!
I think all creative programs need crash recovery as a safety net, because software is very complex and there's inevitably situations where the program will crash - all software of sufficient complexity crashes. But handling that gracefully ensures users they are not going to be hurt by the software. And there's nothing more soul-crushing to an artist, than seeing his work go down the drain of data loss :D
Please do implement this!

@unfa There should be basic recovery on master (you can grab a dev build there: https://github.com/RodZill4/material-maker/actions/runs/305265137). Saves every 15 seconds. Not sure it won't suggest to recover when no crash occurred, so please be aware you cannot trust this for now, and don't hesitate to report weird behavior.

Fantastic! I'll start testing this!
Thank you!

I've tested it today and it did rescue my progress after multiple segfaults!

Great. Did not have much time to test it more myself yet.


Find better color for pronunciation guides or make them variable

Some readers don't distinguish much between the normal text and pronunciation guide text. Part of the challenge is that making it stand out more means making the gray lighter which conflicts with contrast requirements for accessibility. The color can be fine-tuned (maybe a type of blue), or the color could be picked through the options dialog, although Fabric UI doesn't have an built-in color picker component.

Fluent UI has a Color Picker control that would be useful for this. We could let users pick the question text and pronunciation guide colors, since some users want true black instead of Fluent UI's default font color.

After playing around with the color picker component and seeing how the questions look like, I don't think it makes sense to  select arbitrary colors as most look terrible. This could be something with a small set of choices (black or default for normal text, different grays and blue-grays for pronunciation guides) makes sense.


Branch coverage not sent

I was able to display Line coverage using coveralls-jacoco-gradle-plugin and circleCI.
But I don't see branch coverage.
Branch coverage was visible when I don't use coveralls-jacoco-gradle-plugin.
Can coveralls-jacoco-gradle-plugin be made to show branch coverage?
https://docs.coveralls.io/api-jobs-endpoint#:~:text=JSON OBJECT%3A SOURCE FILE

Hi, it seems that while JaCoCo supports branch coverage, it's not exactly translatable to what coveralls expects. I might take a look at it if I get some time, but it may not be trivial to implement an/or give the desired information on branch hits/misses.

+1

Hi, @nbaztec, @snackattas.
From the coveralls.io side, let us know if we can help with the implementation.
In case it helps as a reference, I've attached an example of a Coveralls JSON-format Coverage Upload (the JSON file any Coveralls integration ultimately POSTs to https://coveralls.io/apio/v1/jobs):
Coveralls JSON-format Coverage Upload Example (4 files only) - 2024-03-18T100620.241.json
In this example I've removed all but the first four (4) files in the source_files collection. The first two files have branch coverage stats; the second two do not. So you can see how that's represented.
Let me know if you have any questions.

@Khaseyama  I wanted to verify branch coverage before the 1.2.20 release once but didn't get around it. Could you please verify if it works for you now?

@Khaseyama I wanted to verify branch coverage before the 1.2.20 release once but didn't get around it. Could you please verify if it works for you now?

thank you, I'll check.
It may take a while.

@nbaztec
I have confirmed that branch coverage is displayed in Coveralls in ver1.2.20.
Thank you!


Set up correct .lounge_home at install time

Thanks to https://github.com/thelounge/lounge/pull/1416, lounge add <user> and others can now work correctly without using LOUNGE_HOME or (deprecated) --home, by setting the correct path in .lounge_config.
This will be valid as of v2.5.0.

Fixed by #6


Better state management for min/max/restore buttons, fixes #94

Ok, so everything works, except for dragging the window from maximized away from the top. It's not possible.
Is this a bug in MarkPad or MA.Metro?

Bug in MarkPad with my code, I'll get that fixed up.

That should be fixed now - just pulled in more code from MA.M.
I might look at pulling bits of MA.M out a bit in the future so they're more reusable when you're not using MetroWindow

Brilliant. All fixed now.


Fix images in environment-monitoring.md

Images not migrated from confluence

https://github.com/frmscoe/docs/pull/83

Done


[table viz] adding support for pagination

@ascott @bkyryliuk @vera-liu

LGTM

is there a serverside pagination support?
can we send only one page data at a time so that UI won't crash for large datasets

Nope I'd recommend setting up a lower ROW_LIMIT in your superset_config.


The webui doesn't load

When opening the URL (http://<IP_ADDRESS>:7860) I get the "can't reach this page" message. I don't get any errors while loading, apart from the  "No module named 'triton'" one, which I assume is normal on Windows. I did have to install xformers for cuda 11.8 before though, as I the 12.1 ver. that downloaded automatically wasn't compatible with the PyTorch version. I have Python 3.9.13 installed in the venv.
Here's the log after I run webui.py:
A matching Triton is not available, some optimizations will not be enabled
Traceback (most recent call last):
File "G:\stable diffusion stuff\CharacterGen\CharacterGen\lib\site-packages\xformers_init_.py", line 57, in _is_triton_available
import triton  # noqa
ModuleNotFoundError: No module named 'triton'
G:\stable diffusion stuff\CharacterGen\CharacterGen\lib\site-packages\diffusers\utils\outputs.py:63: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
torch.utils._pytree._register_pytree_node(
G:\stable diffusion stuff\CharacterGen\CharacterGen\lib\site-packages\huggingface_hub\file_download.py:1132: FutureWarning: resume_download is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use force_download=True.
warnings.warn(
Some weights of UNetMV2DConditionModel were not initialized from the model checkpoint at stabilityai/stable-diffusion-2-1 and are newly initialized: ['class_embedding.linear_1.weight', 'class_embedding.linear_2.weight', 'camera_embedding.2.bias', 'camera_embedding.0.bias', 'camera_embedding.0.weight', 'camera_embedding.2.weight', 'class_embedding.linear_1.bias', 'class_embedding.linear_2.bias']
You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.
Some weights of the model checkpoint at stabilityai/stable-diffusion-2-1 were not used when initializing UNetMV2DRefModel: ['up_blocks.3.attentions.2.transformer_blocks.0.norm2.weight', 'conv_out.bias', 'up_blocks.3.attentions.2.transformer_blocks.0.ff.net.2.bias', 'up_blocks.3.attentions.2.transformer_blocks.0.ff.net.0.proj.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_q.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_k.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.norm3.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_v.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.ff.net.2.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_out.0.bias', 'conv_out.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_q.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.norm3.bias', 'conv_norm_out.bias', 'up_blocks.3.attentions.2.transformer_blocks.0.norm2.bias', 'up_blocks.3.attentions.2.proj_out.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_out.0.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_v.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_k.weight', 'up_blocks.3.attentions.2.proj_out.bias', 'up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_out.0.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.ff.net.0.proj.bias', 'conv_norm_out.weight', 'up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_out.0.bias']

This IS expected if you are initializing UNetMV2DRefModel from the checkpoint of a model trained on another task or with another architecture (e.g. initializing a BertForSequenceClassification model from a BertForPreTraining model).
This IS NOT expected if you are initializing UNetMV2DRefModel from the checkpoint of a model that you expect to be exactly identical (initializing a BertForSequenceClassification model from a BertForSequenceClassification model).
Some weights of UNetMV2DRefModel were not initialized from the model checkpoint at stabilityai/stable-diffusion-2-1 and are newly initialized: ['class_embedding.linear_1.weight', 'class_embedding.linear_2.weight', 'camera_embedding.2.bias', 'camera_embedding.0.bias', 'camera_embedding.0.weight', 'camera_embedding.2.weight', 'class_embedding.linear_1.bias', 'class_embedding.linear_2.bias']
You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.
G:\stable diffusion stuff\CharacterGen\CharacterGen\lib\site-packages\diffusers\utils\outputs.py:63: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
torch.utils._pytree._register_pytree_node(
Loading system
G:\stable diffusion stuff\CharacterGen\CharacterGen\lib\site-packages\torch\utils\cpp_extension.py:1967: UserWarning: TORCH_CUDA_ARCH_LIST is not set, all archs for visible cards are included for compilation.
If this is not desired, please set os.environ['TORCH_CUDA_ARCH_LIST'].
warnings.warn(
./3D_Stage/models/lrm.ckpt
finish loading!!
Running on local URL:  http://<IP_ADDRESS>:7860

The error is ModuleNotFoundError: No module named 'triton' you can follow the requirements.txt to download the weight.

same here even I installed all good and I have no triton import error, the terminal is keep shut down abruptly right after showing "finish loading!!, Running on local URL: http://<IP_ADDRESS>:7860" !


Simplify routes config (make it flat)

The config for nested routes is has a nested structure, which makes the API complicated. So we would like to make it flat for simplicity.

QA steps:

check that all links generated with { route: ... } are working correctly


removed duplicate hide method in ios source and add jasmine test cases

hi,
this solves the things i mentioned here.
regards
frank

Thanks!


feat: Expand on parse-mode docs

See conversations at https://github.com/grammyjs/website/pull/520

@KnightNiwrem is this on your todo list?

I'll take that as a no. Could you elaborate what needs to be done here?


Adding Windows Desktop Support

Windows desktop works as linux/macosx you just need to install VirtualBox and Vagrant on the host and call out to vagrant.exe in WSL. This is the easiest way to get the windows desktop working. The harder way so you dont have to use WSL is to rewrite the Makefile, build.sh and fetch.sh in PowerShell... or you could use Mage and write it once in go for all operating systems (my preferred method).

Adding .gitattributes so if a windows user has their git config autocrlf turned on (typical default) the repo will checkout properly so sh and yaml files work in linux properly
Adding VAGRANT env variable to the Makefile so you can pass in the vagrant.exe from the Windows host.

fixed #200

whoa !!!!!!!!!!!

can you test this and merge @knabben !??

testing..

/lgtm


SSLCertVerificationError

Hi, I've been using the Colab just fine but I'm getting this error in the "Instance Images" step.
SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)
Any way to resolve it? Thanks.

try a different browser


We're sorry box

I was trying to do some paragraph breaks in this but couldn't make it work. Needs to be all bold but in separate pars.

This has been updated based on our conversation. Have a look and see what you think.


nd4j-cuda-7.5 one-dimensional sum incorrect for big arrays

This is similar to https://github.com/deeplearning4j/nd4j/issues/733 but it starts happening with way smaller array sizes:
package com.example;

import org.nd4j.linalg.factory.Nd4j;

public class App {
    public static void main(String... args){
        // Uncomment to force doubles.
        //Nd4j.zeros(1);
        //DataTypeUtil.setDTypeForContext(DataBuffer.Type.DOUBLE);
        System.out.println(Nd4j.ones(1024 + 1).sumNumber().intValue());
    }
}

// Output: 1024
// Correct: 1025

I also tried to force this to use doubles, to see if that fixes the problem, and instead it results in this:
o.n.j.c.CudaEnvironment - Devices found: 1
o.n.j.c.CudaEnvironment - Device [0]: Free:<PHONE_NUMBER> Total memory:<PHONE_NUMBER>
o.n.j.h.i.CudaZeroHandler - Mapping device [0] to thread [1]
o.n.j.a.i.AtomicAllocator - Starting device GC for device: 0
o.n.j.a.i.AtomicAllocator - Starting zero GC for thread: 1
o.n.j.a.i.AtomicAllocator - Starting zero GC for thread: 0
o.n.j.a.i.AtomicAllocator - Starting zero GC for thread: 3
o.n.j.a.i.AtomicAllocator - Starting zero GC for thread: 2
-2147483648
CUDA error at C:/Users/dubs/Documents/stuff/clean/master/libnd4j/blas/cuda/NativeOps.cu:581 code=77(<unknown>) "cudaStreamSynchronize(*stream)"
CUDA error at C:\Users\dubs\Documents\stuff\clean\master\libnd4j\include\buffer.h:185 code=77(<unknown>) "cudaMemcpyAsync(bufferRef->data, bufferRef->gData, bufferTotalSize, cudaMemcpyDeviceToHost, stream)"
CUDA error at C:\Users\dubs\Documents\stuff\clean\master\libnd4j\include\buffer.h:186 code=77(<unknown>) "cudaStreamSynchronize(stream)"
CUDA error at C:\Users\dubs\Documents\stuff\clean\master\libnd4j\include\buffer.h:222 code=77(<unknown>) "cudaFree(bufferRef->gData)"
CUDA error at C:\Users\dubs\Documents\stuff\clean\master\libnd4j\include\buffer.h:222 code=77(<unknown>) "cudaFree(bufferRef->gData)"
CUDA error at C:\Users\dubs\Documents\stuff\clean\master\libnd4j\include\buffer.h:222 code=77(<unknown>) "cudaFree(bufferRef->gData)"

Fixed: https://github.com/deeplearning4j/libnd4j/pull/58

It should be noted: fix is temporary, and merge part will be reconsidered. Most probably tomorrow.

Is this done?

Yes, that's fixed quite some time ago. Also just check for blockwise sum - still ok.


Bugs of the BVH structure

I tried the BVH_Debugging.html, and found the strange rendering result (teapot model) as follow:

Is there any bug in the intersection algorithm?

Hi @JiaxiangZheng
It is not a bug in the intersection algo - it is a limitation of WebGL 1.0 (GLSL 2.0). You can read a more detailed explanation here - the paragraph underneath the text  "* .OBJ Model Loading Demo"
As soon as Three.js implements support for WebGL 2.0, these problems will go away.  WebGL 2.0 (GLSL 3.0) allows dynamic indexing of arrays inside shaders, for example currentBVH_Node = BVH_nodes[x] where 'x' is the right number of the branch to go down when traversing the BVH tree.  Currently with WebGL 1.0, I can't set 'x' without getting a compilation error.  'x' cannot be a variable, it must be a hard-coded constant like '1'. So I just randomly pick which branch to go down, left or right, instead of accessing them correctly by dynamic index.  Even though the BVH traverse algo is randomly and incorrectly choosing which branch to go down, you can see a cloud of all the triangles - they are all there in fact, it's just moving at 60fps switching back and forth branches, therefore you get a blurry model.
But at least I can see that it's loading and walking down the branches ok :)

You can always go with a stackless BVH though. This way you won't have to wait for three.js to add support for WebGL 2 and you will cut down the render times.

Hi @Mourtz
Thanks for the suggestion.  Yes this is a direction I would like to explore - there are 2 common approaches, the BVH and the K-D tree: mainly stemming from this paper.  It looks like some folks have already implemented it on CUDA hardware: GitHub link. I would need to port those CUDA kernels over to GLSL though.
The stackless one I really want to try is the LBVH because it dynamically creates the acceleration structure in parallel on the GPU every frame, which means you can have moving and dynamic models in the scene, rather than a pre-built, pre-loaded static scene (like a living room).  However I must also wait for WebGL 2.0 with this approach because Morton codes and bit manipulations are used to quickly create and sort the tree each frame: GitHub link.  WebGL 1.0 does not currently allow bit manipulations in GLSL shaders - it throws a compilation error.  But WebGL 2.0 does allow this indeed.

Wow haven't seen this approach before, adding this to my OpenCL path tracer shouldn't be so hard. I also found the paper. Should be quite hard to implement this to a GLSL raytracer though, would be awesome if you make it happen someday. Keep up the good work man! :)

@erichlof just found they have already added support for WebGL 2 in the dev branch. link

For the past 6 months, I have been working on an OpenCL raytracer for my BSc thesis and during this period  I understood a lot of stuff in this project are wrong. Hopefully, I will fix them sometime soon. Thanks for your kind words anyways. :)

Hi @JiaxiangZheng and @Mourtz ,
I just wanted to let you know I have implemented a working BVH builder for .obj models.  The new Iterative version is much more robust.  You can check it out here: BVH WebGL 2.0 demo
I'm going to go ahead and close out this issue because the old builder (the one that prompted this issue) which was buggy, has been replaced.


Embed themes as static web assets. Closes #22

Thanks!

Merging, will create a new release this weekend


Addition of Oracle EBS default users, passwords and URLs

Reference: https://the-infosec.com/2017/03/29/do-you-know-what-your-erp-is-telling-us/

Thank you!


Supported Data Sources - SQL Server in Azure VM?

The page mentions

Azure SQL

as the supported platform. Does this include SQL Server in an Azure VM? If so, what versions/configuratoins are supported?
According to https://learn.microsoft.com/en-us/data-integration/vnet/sql-server-and-custom-connectors SQL Server may be supported. However it's unclear and we do not want to make any assumption..

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

ID: 5091585c-6eae-176b-f97b-6e7bf5f18d3f
Version Independent ID: ece61ded-aee6-c780-25ef-d5c57161df7b
Content: Use virtual network (VNet) data gateway and data sources in Power BI
Content Source: data-integration/vnet/use-data-gateways-sources-power-bi.md
Service: virtual-network-data-gateway
GitHub Login: @nikkiwaghani
Microsoft Alias: nikkiwaghani

Any chance of getting an answer on this? We would like to know too

@VitalyMCT @jashwood
SQL server on a VM is not supported. The VNet data gateway support for Power Automate SQL Server and custom connectors (Preview) article refers to the direct VNet used in Power Apps/Automate, which is created in the Power Platform admin center in the Gateway drop-down box, not the VNet data gateway.

Thanks Doug

@DougKlopfenstein Understood. Could you please amend the article accordingly?
Microsoft's definition of Azure SQL includes SQL Server on Azure VM (https://azure.microsoft.com/en-us/products/azure-sql/#sql-database). So the wording in the article as it stands now is incorrect.

Thanks @VitalyMCT for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close

Can you please fix this? It's a one-word change: "SQL Server" => "Azure SQL". Customers keep getting confused.

Hi @VitalyMCT. I just checked and the document does refer to Azure SQL. Sorry for the confusion in the closure comment. :) Thanks for helping us improve the docs!

@VitalyMCT Ah indeed! I was somehow looking at the wrong doc before! I fixed it now. Thanks again for catching this and helping us keep the docs up to date!


chore(main): release 0.12.0

:robot: I have created a release beep boop
0.12.0 (2023-02-21)
Features

mine: add spaces between numbers and units (e523c01)
mine: update setting titles & subtitles (1663c96)
monitor: add refresh rate setting (eda813c)

Performance Improvements

[ImgBot] Optimize images (#134) (9885ae2)
monitor: slow down UI refresh (97ca177)

Code Refactoring

mine: add setIndex for _LoggerLevel (71ec345)
mine: selected.first -> selected.single (6401b80)
monitor: make refreshInterval private (766ff6e)
move ProviderScope out of App (c08e844)

Tests

add tests for App (0345fac)

Styles

add trailing comma (54a3d80)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/CCXXXI/ecg_monitor/releases/tag/v0.12.0 :sunflower:


Added customer model

Customer Model
Added Fields

ID
Name
Address
Email
Phone Number
Member Since

Testing with Factory Boy

Used Factory Boy to create fake data to test the model.

Additions here look good to me!


SetMaxWasmStack fails with async_stack_size error

As mentioned in https://github.com/bytecodealliance/wasmtime/pull/6762. I figure it's better to discuss wasmtime-go stuff here.
Currently doing this:
cfg := wasmtime.NewConfig()
cfg.SetMaxWasmStack(8388608)
engine := wasmtime.NewEngineWithConfig(cfg) // panics

Fails with this message:
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: max_wasm_stack size cannot exceed the async_stack_size', crates/c-api/src/engine.rs:33:38
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
SIGABRT: abort
PC=0x198cf4724 m=0 sigcode=0
signal arrived during cgo execution

goroutine 1 [syscall, locked to thread]:
runtime.cgocall(0x104609b88, 0x14000133c38)
	/opt/homebrew/Cellar/go/1.20.5/libexec/src/runtime/cgocall.go:157 +0x54 fp=0x14000133c00 sp=0x14000133bc0 pc=0x10438be14
github.com/bytecodealliance/wasmtime-go/v11._Cfunc_wasm_engine_new_with_config(0x153804340)
	_cgo_gotypes.go:1016 +0x38 fp=0x14000133c30 sp=0x14000133c00 pc=0x1044c0b78
github.com/bytecodealliance/wasmtime-go/v11.NewEngineWithConfig.func1(0x153804340?)
	/Users/guregu/go/pkg/mod/github.com/bytecodealliance/wasmtime-go/v11@v11.0.0/engine.go:33 +0x54 fp=0x14000133c70 sp=0x14000133c30 pc=0x1044c2ee4
github.com/bytecodealliance/wasmtime-go/v11.NewEngineWithConfig(0x140000161f0)
	/Users/guregu/go/pkg/mod/github.com/bytecodealliance/wasmtime-go/v11@v11.0.0/engine.go:33 +0x28 fp=0x14000133cb0 sp=0x14000133c70 pc=0x1044c2df8
github.com/trealla-prolog/go/trealla.init.0()
	/Users/guregu/code/trealla/go/trealla/wasm.go:31 +0x84 fp=0x14000133cf0 sp=0x14000133cb0 pc=0x1045fb704
runtime.doInit(0x105737ca0)
       ...

This led to me trying to set the async_stack_size, noticing it was missing from C API, and the wasmtime PR.

Oddly enough, I can't reproduce it when writing a test case against this repo
func TestEngineMaxStackSize(t *testing.T) {
	config := NewConfig()
	config.SetMaxWasmStack(8388608) // 8MiB
	engine := NewEngineWithConfig(config)
	require.NotNil(t, engine)
}

This passes with no issue.
But the same usage fails in trealla-prolog/go. I'll see if I can isolate it better.

Are you using a custom build of Wasmtime's C API? The check that you're failing is behind #[cfg(feature = "async")] which I think is disabled for the builds this repository uses but if you've got a custom build that feature may be enabled.
I also posted over on the Wasmtime PR, but I think this is still a bug to fix in Wasmtime.

I am seeing the same issue on GitHub actions, so it's probably not an environment issue, but still not sure of the root cause.
https://github.com/trealla-prolog/go/actions/runs/5649469168/job/15303868806
https://github.com/trealla-prolog/go/blob/b5c257d2a300289b14de160b07e79cecb182fd49/trealla/wasm.go#L28
I'll investigate more.

Oh, I think you were right after all about the custom build thing, I was just thinking in the wrong direction.
My custom build was OK, but replacing that with the libwasmtime.a from the go mod cache leads to the same panic.
So it seems like the released version of libwasmtime.a has async enabled.

Sent a quick PR with a little test in #183, it fails in CI so I think we've figured it out.

Confirmed that this is fixed with the latest version. Feel free to close or merge #183, which should be passing now.


[Suggestion] Insert recording to an existing record.

Assume I have recorded and edited a recording of several minutes, than I found something is missing, but I don't want to re-record and re-edit everything.
It'll be great if I can just start a recording without closing the current project and insert the newly recorded frames into the current position of the current project.
I hope it makes sense, this is really a great project and I appreciate your excellent work!

Hi, if I understood correctly, this feature already exists.

Hi, if I understood correctly, this feature already exists.

Oh my bad! It's so obvious but I didn't even notice it! Thank you!


Update init.py

Disable trash message.

Ah yeah so rn this is technically for private use (feel free to use it if you can figure out how) with revamp coming soon.
That was for testing, approved tho

Hi, How i can install this commit on replit project ?


Single image: There is no possibilities to merge polygons with each other or split a polygon into two polygons or more

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour
To be able merge several polygons - either with same classes or different ones - (more than two) with each other as the same class or assigning them a new label.
To be able to split a polygon into two or more polygons. Even splitting into two polygons will be great.
When annotating an object is not possible to be done with one polygon either because it is two big or it contains holes, one has to annotate the object into separate polygons which have to be merged with each other.
Current Behaviour
At the moment, splitting and merging features apply only to videos and not single images and one does not have any options to merge polygons with each other or split them.
Possible Solution
Merging:
One can think of keeping a button pressed and then select polygons and then press another button to merge them or another button to merge them and also ask for a new class naming.
Splitting:
One can think of splitting a polygon into two pieces in the editing mode, but instead of removing one of the polygons after the editing, keeping both polygons with a shared border.

Looks similar to #774 and #690
BTW, have you tried grouping feature?

@bsekachev
Yes, I have tried grouping feature. I can select more than one polygons, but it is not clear which button shall be pressed after polygons are selected. I activate the grouping feature with G and select polygons. The next step to merge them is either not defined or I can not find it.
Oops! I had not seen those previous issues.

You need activate grouping (with G, or with dedicated icon at left panel), select shapes, then deactivate grouping (in the same way). Selected shapes will be united to the same group and will have the same group_id in annotations file.
To reset group of an object you need to select it in grouping mode and press shift+g

@bsekachev
Grouping feature does not merge polygons with each other rather link them. In merging polygons, the overlapped area shalle be merge to make two or more polygons as one polygon. Also it should work if and only if the selected polygons have overlap with each other all.
However, in grouping feature, the polygons do not have to be overlapping each other and the feature keeps all of the polygon points which is unwanted.
Regarding the grouping feature itself, it is useful for another issue which I made to connect disconnected objects with each other which can be done with this feature. However, there is a problem here, the group-id does not appear in the annotation environment so it is not possible to tell which annotations are grouped with each other unless the annotations are dumped. Neither the color of polygons in instance mode or their ID during the annotation do not become one.

Also it should work if and only if the selected polygons have overlap

Why do you believe this restriction makes sense? Or I do not understand your use case.
In my opinion we should allow an annotator to decide what polygons should be merged.

However, there is a problem here, the group-id does not appear in the annotation environment so it is not possible to tell which annotations are grouped with each other unless the annotations are dumped.

I answered you in the separated issue.

From my point of view, there is a difference between merging and connecting/linking if the polygons have overlap each other.
Connecting/linking: polygons are separated and we want to assign them one unique object id while keeping all of the points.
Merging: making polygons (>=2) one polygon. It will be a 𝐴∪𝐵 and similar to the connecting operation if the polygons are separated, but if the polygons are overlapping each other, 𝐴∪𝐵 will be 𝐴∪𝐵 - 𝐴∩𝐵 i.e. the points in the intersection area will be removed.
https://intl.siyavula.com/read/maths/grade-10/probability/14-probability-03
Please let me know if I am missing a point here.
I mentioned the issues concerning merging features usability in the corresponding issue #2381

@bsekachev
any updates on this?

@arasharchor
The issue has been moved to backlog. It means, that the core team doesn't have any current plan on implementation of this.
CVAT is an open source tool and we hope the community help us with development it because internal resources are restricted


Switch ints that can't be negative to uints

I am opening this PR as part of the #118 work.
Running benchstat
goos: darwin
goarch: arm64
pkg: github.com/elastic/apm-data/codec
                         │ bench-main  │            bench-branch            │
                         │   sec/op    │   sec/op     vs base               │
Encode/format=json-10      22.04µ ± 2%   22.19µ ± 3%       ~ (p=0.271 n=10)
Encode/format=vtproto-10   1.357µ ± 6%   1.359µ ± 2%       ~ (p=0.971 n=10)
Decode/format=json-10      16.23µ ± 7%   16.28µ ± 9%       ~ (p=0.684 n=10)
Decode/format=vtproto-10   6.423µ ± 3%   6.430µ ± 3%       ~ (p=0.912 n=10)
geomean                    7.472µ        7.496µ       +0.31%

                         │  bench-main  │             bench-branch              │
                         │   bytes/op   │   bytes/op    vs base                 │
Encode/format=json-10      6.169Ki ± 0%   6.169Ki ± 0%       ~ (p=1.000 n=10) ¹
Encode/format=vtproto-10   2.702Ki ± 0%   2.702Ki ± 0%       ~ (p=1.000 n=10) ¹
geomean                    4.083Ki        4.083Ki       +0.00%
¹ all samples are equal

pkg: github.com/elastic/apm-data/input/elasticapm/internal/decoder
                   │ bench-main  │         bench-branch          │
                   │   sec/op    │   sec/op     vs base          │
NDStreamDecoder-10   42.51n ± 7%   43.08n ± 7%  ~ (p=0.529 n=10)

pkg: github.com/elastic/apm-data/model/modelpb
                          │ bench-main  │         bench-branch          │
                          │   sec/op    │   sec/op     vs base          │
APMEventToJSON/to-json-10   11.62µ ± 3%   11.66µ ± 6%  ~ (p=0.684 n=10)

I have changed the code generation to keep the elem < 0 check, as some values remain nullable.Int, due to them being from json, which doesn't know about signed integers.
And added a nolint to that bit of code generation to make staticcheck happy.

@dmathieu there are unfortunately a bunch of conflicts now, do you have bandwith today to get these fixed and merge this PR? Otherwise please ensure to hand over.

Ah yes, sorry. I missed the previous notification. I've rebased and will merge now.


feat(select): added selection leverage props to OptGroup

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

18 of 28 (64.29%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 84.308%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/select/src/presets/useSelectWithApply/options-list-with-apply/Component.tsx
2
3
66.67%

packages/select/src/components/options-list/Component.tsx
9
12
75.0%

packages/select/src/components/virtual-options-list/Component.tsx
7
13
53.85%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
9773

Relevant Lines:
10701

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

18 of 28 (64.29%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 84.063%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/select/src/presets/useSelectWithApply/options-list-with-apply/Component.tsx
2
3
66.67%

packages/select/src/components/options-list/Component.tsx
9
12
75.0%

packages/select/src/components/virtual-options-list/Component.tsx
7
13
53.85%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
9838

Relevant Lines:
10791

💛  - Coveralls


migration: Set fields correctly for migration block

The Shanghai and Cancun forks added new header fields.
Until now we were setting them with bogus data during the migration, this PR sets the ParentBeaconRoot to the correct value.
This doesn't write the ParentBeaconRoot to the EIP4788 contract. I started implementing this, but it turned out quite complicated. As the value, which would be written during the migration, would be overwritten in 4.5 hours (8191*2/60/60) for 2s blocks, I think it's not required for the migration.
Closes https://github.com/celo-org/celo-blockchain-planning/issues/350

Codecov Report
Attention: Patch coverage is 76.05263% with 91 lines in your changes missing coverage. Please review.

Project coverage is 80.81%. Comparing base (fede445) to head (c974330).
Report is 6 commits behind head on celo7.

Files with missing lines
Patch %
Lines

cannon/mipsevm/testutil/state.go
72.13%
30 Missing and 4 partials :warning:

cannon/mipsevm/testutil/evm.go
55.00%
25 Missing and 2 partials :warning:

cannon/mipsevm/testutil/vmtests.go
42.85%
6 Missing and 2 partials :warning:

cannon/mipsevm/multithreaded/instrumented.go
16.66%
5 Missing :warning:

cannon/mipsevm/singlethreaded/instrumented.go
0.00%
5 Missing :warning:

cannon/mipsevm/multithreaded/testutil/state.go
85.71%
4 Missing :warning:

cannon/mipsevm/singlethreaded/testutil/state.go
84.61%
4 Missing :warning:

cannon/mipsevm/testutil/mips.go
75.00%
2 Missing :warning:

cannon/mipsevm/testutil/oracle.go
83.33%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##            celo7     #212       +/-   ##
===========================================
+ Coverage   61.32%   80.81%   +19.49%
===========================================
  Files          20       32       +12
  Lines        1753     2466      +713
  Branches       71        0       -71
===========================================
+ Hits         1075     1993      +918
+ Misses        646      396      -250
- Partials       32       77       +45

Flag
Coverage Δ

cannon-go-tests
80.81% <76.05%> (-0.22%)
:arrow_down:

chain-mon-tests
?

sdk-tests
?

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

Files with missing lines
Coverage Δ

cannon/mipsevm/exec/mips_instructions.go
97.85% <100.00%> (ø)

cannon/mipsevm/exec/mips_syscalls.go
93.66% <100.00%> (ø)

cannon/mipsevm/multithreaded/mips.go
71.47% <100.00%> (ø)

cannon/mipsevm/multithreaded/stack.go
69.23% <100.00%> (ø)

cannon/mipsevm/multithreaded/state.go
93.12% <100.00%> (ø)

cannon/mipsevm/program/load.go
46.42% <ø> (ø)

cannon/mipsevm/program/patch.go
75.51% <100.00%> (ø)

cannon/mipsevm/singlethreaded/mips.go
94.00% <100.00%> (ø)

cannon/mipsevm/singlethreaded/state.go
91.15% <100.00%> (ø)

cannon/mipsevm/tests/helpers.go
100.00% <100.00%> (ø)

... and 10 more

... and 9 files with indirect coverage changes

Looks good, but you have a whole bunch of circleci tests failing, not sure what those could be.

The ones I checked before are related to the rebase, not the changes in this PR.


Placement in Items

The specification says "renders" should be in Item Properties, but the examples and schema seem to have it on the top-level. I think it should in the Item Properties. All extensions extend the Item Properties, which is the best-practice.

Just reviewed. We will need a version 2 as it is a breaking change.


Support for unescaped text/html embeds

This pull request allows the user to embed the text/html mime type, and have the embed data displayed, unescaped, in the scenario report.
The commit consists of 3 main changes:

Add a text/html mime_type handler to the if structure in _parseSteps. I just collects the data into a .html property on the step.
Add a relevant template structure to handle the .html property. It joins multiple attachments into a single HTML block, separated by a <br/> element.
Add an html embed step to the test data.

Coverage decreased (-0.2%) to 98.454% when pulling 32fa827e83971f1b55bdea1a421a9cb6774226a7 on yaronassa:master into 9ae460e1dc23056da0dbbb9e9a5e7bf487f5ffba on wswebcreation:master.

Tnx for the PR
I'm currently not available due to traveling and vacation. When I'm back I'll check and merge it.

@wswebcreation Hey, just noticed a bug that didn't output html embeds for hidden steps (I missed a condition in the template when adding my original changes).
Added the fix now.

@yaronassa
Can you push that fix and create a PR for it?

Yeah, sure, don't know why I pushed it here.
My bad


Lumen dependencies

Whilst Lumen itself does not depend on the zip extension being enabled, it would appear that lumen-installer in fact does.
The docs should probably be updated to reflect this in some way, this issue may need crossing over to laravel/lumen-docs, but seemed more appropriate to post here first.

We're open to pulls. :)


[Bugfix] Fix PP for ChatGLM and Molmo

#9242 accidentally removed PP support from ChatGLM. On the other hand, MolmoModel already supports PP but the top-level MolmoForCausalLM does not. This PR fixes both of these issues.
The input processors of these models and Qwen2-VL have also been cleaned up a bit.
Also fixes https://github.com/vllm-project/vllm/pull/9090#issuecomment-2418413863

Sorry for breaking your code! @lixiaolx can you test out this PR and see if you can load Qwen/Qwen2.5-Math-RM-72B now?

Sorry for breaking your code! @lixiaolx can you test out this PR and see if you can load Qwen/Qwen2.5-Math-RM-72B now?

@DarkLight1337 , I tried adding lm_head filtering to the model.py file of qwen_rm. Now I can load the model, but the final results of my test reference are all nan https://github.com/vllm-project/vllm/pull/8896. I tried printing the weights of the model, but it seemed that the weights were not loaded correctly.
add print code in
https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/model_loader/loader.py#L413
for name, param in model.named_parameters():             print(f"Parameter '{name}' =====tensor=======: {param}")

Sorry for breaking your code! @lixiaolx can you test out this PR and see if you can load Qwen/Qwen2.5-Math-RM-72B now?

@DarkLight1337 , I tried adding lm_head filtering to the model.py file of qwen_rm.
loader = AutoWeightsLoader(self,skip_prefixes=["lm_head"])
Now I can load the model, but the final results of my test reference are all nan https://github.com/vllm-project/vllm/pull/8896. I tried printing the weights of the model, but it seemed that the weights were not loaded correctly.
add print code in
https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/model_loader/loader.py#L413
for name, param in model.named_parameters():             print(f"Parameter '{name}' =====tensor=======: {param}")

Can you add print statements inside AutoWeightLoader and list out the weight names in the iterator? This should provide enough information for me to figure out the discrepancies.

Sorry for breaking your code! @lixiaolx can you test out this PR and see if you can load Qwen/Qwen2.5-Math-RM-72B now?

@DarkLight1337 , I tried adding lm_head filtering to the model.py file of qwen_rm.
loader = AutoWeightsLoader(self,skip_prefixes=["lm_head"])
Now I can load the model, but the final results of my test reference are all nan #8896. I tried printing the weights of the model, but it seemed that the weights were not loaded correctly.
add print code in
https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/model_loader/loader.py#L413
for name, param in model.named_parameters(): print(f"Parameter '{name}' =====tensor=======: {param}")

Can you add print statements inside AutoWeightLoader and list out the weight names in the iterator? This should provide enough information for me to figure out the discrepancies and fix them.

Any update? Otherwise, I'll merge this PR first and fix the model in another PR.

Sorry for breaking your code! @lixiaolx can you test out this PR and see if you can load Qwen/Qwen2.5-Math-RM-72B now?

@DarkLight1337 , I tried adding lm_head filtering to the model.py file of qwen_rm.
loader = AutoWeightsLoader(self,skip_prefixes=["lm_head"])
Now I can load the model, but the final results of my test reference are all nan #8896. I tried printing the weights of the model, but it seemed that the weights were not loaded correctly.
add print code in
https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/model_loader/loader.py#L413
for name, param in model.named_parameters(): print(f"Parameter '{name}' =====tensor=======: {param}")

Can you add print statements inside AutoWeightLoader and list out the weight names in the iterator? This should provide enough information for me to figure out the discrepancies and fix them.

Any update? Otherwise, I'll merge this PR first and fix the model in another PR.

I think I fixed the problem, so I'm going to merge this now. Please tell me if it still doesn't work.


[FEAT] Support Nextjs v15

Is your feature request related to a problem? Please describe.
❤
Describe alternatives you've considered
❤
Additional context
Hi I'm currently using Refine + Antd + Nextjs project in my company and the slow compiling time of Nextjs 13 is killing my teammates, so Nextjs 15 support in Refine would be great at the time being Nextjs v15.0.1 is marked as stable now
Describe the thing to improve
Luv u guys

Hey @jackytank thanks for the issue. Did you try using it with NextJS 15?

My project created by this preset npm create refine-app@latest -- --preset refine-antd when I follow this guide (https://ant.design/docs/react/use-with-refine)

my environment: node v21.1.0, npm 10.9.0

After create the project, I had update some of the package manually, and this is my current package.json with nextjs 15

{
  "name": "my-refine-remix-app",
  "version": "0.1.0",
  "private": true,
  "engines": {
    "node": ">=18.0.0"
  },
  "scripts": {
    "dev": "cross-env NODE_OPTIONS=--max_old_space_size=4096 refine dev --turbo",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "refine": "refine"
  },
  "dependencies": {
    "@ant-design/icons": "^5.0.1",
    "@ant-design/nextjs-registry": "^1.0.1",
    "@aws-sdk/client-cloudwatch": "^3.670.0",
    "@aws-sdk/client-cloudwatch-logs": "^3.670.0",
    "@aws-sdk/client-lambda": "^3.670.0",
    "@aws-sdk/client-s3": "^3.670.0",
    "@aws-sdk/client-sqs": "^3.670.0",
    "@refinedev/antd": "^5.43.1",
    "@refinedev/cli": "^2.16.39",
    "@refinedev/core": "^4.55.0",
    "@refinedev/devtools": "^1.2.9",
    "@refinedev/kbar": "^1.3.6",
    "@refinedev/nextjs-router": "^6.1.0",
    "@refinedev/simple-rest": "^5.0.1",
    "antd": "^5.21.3",
    "dayjs": "^1.11.13",
    "js-cookie": "^3.0.5",
    "json-edit-react": "^1.17.0",
    "lodash": "^4.17.21",
    "next": "^15.0.1",
    "react": "^18.3.1",
    "react-dom": "^18.3.1",
    "react-icons": "^5.3.0",
    "ssh2-sftp-client": "^11.0.0"
  },
  "devDependencies": {
    "@types/js-cookie": "^3.0.6",
    "@types/lodash": "^4.17.10",
    "@types/node": "^18.16.2",
    "@types/react": "^18.3.11",
    "@types/react-dom": "^18.3.1",
    "@types/ssh2-sftp-client": "^9.0.4",
    "@typescript-eslint/parser": "^6.21.0",
    "cross-env": "^7.0.3",
    "eslint": "^8",
    "eslint-config-next": "^14.1.0",
    "typescript": "^5.4.2"
  }
}

After upgrade to Next 15, I encounter these errors

Then I F12 open browser Dev tool, then a lot of error keep spawning infinitely

About the error cookies().get("theme") in above image I fixed it in src/app/page.tsx like this

Then there are a lot of errors still there

I panicked so I reverted back to Next 13, I hope those info can help you guys

Hey @jackytank I created an example using npm create refine-app@latest -- --example with-nextjs next-15-test command, as you mentioned, I had to await cookies() call.
Other than that, there are errors caused by ant design, which I should believe they should be warnings.
We need to update our template to have await on cookies() call but other than that I couldn't find any error related to Refine.
I can navigate around example's pages without any issues. This means our NextJS router works as expected. None of these errors should block using Next 15 with Refine.

Hey @jackytank I created an example using npm create refine-app@latest -- --example with-nextjs next-15-test command, as you mentioned, I had to await cookies() call.
Other than that, there are errors caused by ant design, which I should believe they should be warnings.
We need to update our template to have await on cookies() call but other than that I couldn't find any error related to Refine.
I can navigate around example's pages without any issues. This means our NextJS router works as expected. None of these errors should block using Next 15 with Refine.

oh I see so the errors are coming from Ant Design, I'll head over to antd repo and notify them to update, so I guess I need to wait a little more time until antd teams fix those errors, other than that Refine + next 13 is great

Hello everyone,
We have released support for Next.js 15 and we build an example that works with Next.js 15.
But unfortunately, npm create refine-app@latest does not currently support Next.js 15 because other integrations like Ant Design and Material UI also need to support Next.js 15 to ensure the application works smoothly.
If you're using Refine in a headless mode, you can upgrade to Next.js 15 or create a Refine project with Next.js 15 support using the following command:
npm create refine-app@latest -- --example with-nextjs-headless

Upgrade Notes
There are no breaking changes in Refine usage; however, you may need to update your application for React 19 and Next.js 15. You can find detailed information in the following links:

[Next.js 15 Upgrade Guide](https://nextjs.org/docs/app/building-your-application/upgrading/version-15)
[React 19 Upgrade Guide](https://react.dev/blog/2024/04/25/react-19-upgrade-guide)

If you encounter any issues, please let us know! 🚀


Feature/ux enhancement for options

Description

This PR will show the names of the issuers, ie Google, GitHub, etc in place of the issuer URLs to the user.

Fixes #691
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)

Additional requirements

[x] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Code of Conduct
By submitting this PR, you agree to follow our Code of Conduct.

[x] I agree to follow this project's Code of Conduct

Hi @kairoaraujo Kindly review these changes for #691

Thank you @kairoaraujo !!

@mukulbindal, if you have an interest in continuing to contribute to the RSTUF project, join us in the OpenSSF Channel
https://repository-service-tuf.readthedocs.io/en/stable/#slack-channel

Hi @kairoaraujo yes I am interested in contributing to RSTUF. Could you please help me signing up to slack, I don't see a sign up option :)

Hi @kairoaraujo yes I am interested in contributing to RSTUF. Could you please help me signing up to slack, I don't see a sign up option :)

You can go to this page https://openssf.org/getinvolved/
There is a link Join our Slack"


runtime

Could please provide the  runtime on KITTI?,I can not find it in paper.thank you!

Hi, here is an excerpt from our rebuttal:

Our GNN is capable of near-real-time inference: 33 FPS on NuScenes and 170 FPS on KITTI.
KITTI is faster, because, by protocol, we only track objects visible in the forward-directed camera, which is a substantially lower number.

The code will include a script to run the tracker online and it will output more precise numbers on your hardware. The release will be done this week, so check in on Monday.


Type instantiation is excessively deep and possibly infinite

Related plugins

[X] plugin-vue

[ ] plugin-vue-jsx

Describe the bug
I have this type of error when installing the Vite plugin Vue on my Nuxt app. I don't really know if I have to create this issue here or in the Nuxt repo, but I think it is more related to the plugin.

Reproduction
https://github.com/HugoRCD/shelve/blob/main/apps/app/nuxt.config.ts
Steps to reproduce
bun run dev
System Info
System:
    OS: macOS 15.0
    CPU: (8) arm64 Apple M1 Pro
    Memory: 75.13 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm
    pnpm: 8.15.6 - ~/Library/pnpm/pnpm
    bun: 1.1.15 - ~/.bun/bin/bun
  Browsers:
    Chrome: 122.0.6261.94
    Safari: 18.0

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Having the same issue. Everything works though, the error can be suppressed using @ts-expect-error or @ts-ignore.

Got the same issue with vue-tsc:

Will a fix be realeased for this


.gitignore'd files not greyed out when loading project via mapped drive

VSCode Version: 1.48.2
OS Version: Windows 10 (2004)

Steps to Reproduce:

Load a project from a samba path (\machine\share\project), files in .gitignore are correctly greyed out in the vscode explorer
Load the same project from a mapped drive X:\project, (where X: is mapped to \machine\share) and vscode doesn't grey out any files/folders in explorer

This issue may be connected with #70963

Does this issue occur when all extensions are disabled?: Yes

I'm getting many of the following in the output log (extension host):
[TIMESTAMP] [exthost] [error] {"message":"Git error","stdout":"","stderr":"fatal: x:\\project: 'x:\\project' is outside repository\n","exitCode":128}

and many of these in the log (window):
[TIMESTAMP] [renderer10] [error] Git error

But I don't see any issue when I load the project via \server\share\project

Upon further investigation I managed to resolve this issue by updating Git to the current version, 2.28. The problem occurred with git version 2.21, although strangely it worked fine on a cmd shell.