text:
Fix custom exception usage

fixes error that Unauthorized exception is used even though a custom exception should be used

Codecov Report

Merging #43 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #43   +/-   ##
=======================================
  Coverage   84.13%   84.13%
=======================================
  Files           3        3
  Lines         435      435
=======================================
  Hits          366      366
  Misses         69       69

Impacted Files
Coverage Δ

flask_authorize/plugin.py
89.81% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4115b70...51bcf13. Read the comment docs.

Just created a new 0.2.1 release with these fixes. Thanks!

source: gharchive/pull-request

authors: bprinty codecov-io mmarihart

repo: bprinty/Flask-Authorize

license: MIT

license_type: permissive

license_source: github-api


text:
Implement overview of bots running

As a ‹role›, I'd like to ‹feature short description› [ , in order to ‹value it adds›. ]

:thought_balloon: Hints & Thoughts
:question: Additional Questions to Answer / Consider

:white_check_mark: Conditions of satisfaction

[ ] Should ‹testable condition that should be satisfied›
[ ] Should ‹testable condition that should be satisfied›
[ ] …

This issue only makes sense from my point of view if the robots are running in the cloud (#20). Since this is not planned in the BP project scope, this issue also falls outside the project scope.

source: gharchive/issue

authors: SanJSp lukashueller


text:
missing function

Thank you for sharing the code to this fascinating paper. I'm currently trying to test the analysis on my own EEG data, however in example_code.m there is a call to a function grid_communities on line 44 which doesn't appear to be a built in MATLAB function or included in the fcn folder.
Thanks for your help!
Best,
Matteo

I just realise grid_communities is from the brain connectivity toolbox!


text:
Syncing from upstream zalando/patroni (master)

bt_gitbot

Pull Request Test Coverage Report for Build 5675454953

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.859%

Totals

Change from base Build 5665043920:
0.0%

Covered Lines:
12742

Relevant Lines:
12760

💛  - Coveralls

authors: bt-admin coveralls

repo: brain-tec/patroni


text:
chore(flagship): upgrade @types/yargs to 12.0.1

no breaking changes, searched for changed type definitions. Will be updating yarg as well.
Commit history:
https://github.com/DefinitelyTyped/DefinitelyTyped/commits/5344bfc80508c53a23dae37b860fb0c905ff7b

@bweissbart Wow that was sloppy of me. It got messy updating so here's the replacement PR: https://github.com/brandingbrand/flagship/pull/580

repo: brandingbrand/flagship


text:
Exposing fees in ReverseSwapInfo

Sending an onchain payment using a reverse swap results in a Payment that contains a ReverseSwapInfo. It would be useful if ReverseSwapInfo included the fees that were spent for the lockup and claim txs, as well as the swap provider fees. Right now we can only find out how much was spent on fees in total by comparing the sent LN funds and the resulting sent onchain funds.

Thanks @danielgranhao.
If we are changing the ReveseSwapInfo then let's also add the payment_hash so users can use payment_by_hash method to retrieve the associated payment.

Working on exposing the reverse swap fees.
I can add the fees for any new reverse swap, but not existing ones, because we don't have the data.
I was thinking about backfilling the fees for the existing swaps by looking at onchain transaction fees. But the tx ids are only persisted in the local storage, not the sync storage. So this data is lost when you lose your local data.
So a 2-fold question to @danielgranhao and @roeierez:

Is having the fees only for new swaps good enough?
It seems to me like we should store the claim and lockup tx ids in the sync database, why are they in the local database only?  (it was added in this PR https://github.com/breez/breez-sdk-greenlight/pull/728)

@JssDWt moving forward without backfilling the old swaps is fine enough IMO for this PR.
The lockup/claim tx are not synced because they are onchain data that is fetched from the blockchain.

I've just noticed I created another version of this issue earlier. It's almost an exact duplicate, but it also asks to add the recipient onchain address to ReverseSwapInfo. I still think it would be useful.

authors: JssDWt danielgranhao roeierez

repo: breez/breez-sdk-greenlight


text:
No destination in list_payments for incoming chain swap

Seems to be a regression since the claim_address is now optional and we only store it for outgoing chain swaps. Options:

add incoming liquid claim_address to swap on claim
add payment detail for the swap with the claim_address

Is this only for ongoing (pending) swaps?

I think all states in the receive case. Will confirm later

Confirmed this
{
      "destination": null,
      "tx_id": "03bd9f817a5f2ee43e4b103a013cdb0b52153eeddd5ad52c146b6ab60e5cf420",
      "timestamp": 1730901165,
      "amount_sat": 49457,
      "fees_sat": 543,
      "payment_type": "Receive",
      "status": "Pending",
      "details": {
        "Bitcoin": {
          "swap_id": "GHMXTonc4H2Y",
          "description": "Bitcoin transfer",
          "refund_tx_id": null,
          "refund_tx_amount_sat": null
        }
      }
    }

...
{
      "destination": null,
      "tx_id": "03bd9f817a5f2ee43e4b103a013cdb0b52153eeddd5ad52c146b6ab60e5cf420",
      "timestamp": 1730901165,
      "amount_sat": 49457,
      "fees_sat": 543,
      "payment_type": "Receive",
      "status": "Complete",
      "details": {
        "Bitcoin": {
          "swap_id": "GHMXTonc4H2Y",
          "description": "Bitcoin transfer",
          "refund_tx_id": null,
          "refund_tx_amount_sat": null
        }
      }
    }

@dangeross so we probably need to add the destination when we create the claim address and broadcast?

authors: dangeross roeierez

repo: breez/breez-sdk-liquid


text:
Create Count-ception.py

First commit of the count-ception method. Will need to work in how to import your data set since I used my own for testing

I see a new pull request has been created for this, so I'll mark this as closed.

authors: MichaelGinsberg brewinn

repo: brewinn/Roadrunner-CellCounter


text:
updated readme.txt

added second comment

NO!


text:
Auto-casting for subdocument._id not work

I have a schema
{
...
windows: [{name:String}]
...
}
If I run Model.find({windows._id:'string'}) everything is ok, mongoose is sending query {"windows._id":ObjectId('string')} and returns records;
If I extend the schema somehow (ex. just {S_V:Number}),
find() do not return anything, because mongoose is sending query {'windows._id':'string'}, which searches for string-type _ids and fails to find any.
This issue contains more information and real code example: https://github.com/Automattic/mongoose/issues/3364#issuecomment-141353516

May have to fix the cloning stuff, I'll check that

authors: Crotery sieira

repo: briankircho/mongoose-schema-extend

license: mit

license_source: bigquery


text:
Implement strikes, ban, deactivate, and reactivate account

Make sure to pnpm migration:up first before testing this PR.
Implemented strikes, ban, deactivate, and reactivate account in account settings.

Strikes screen working properly, displaying strikes count.
4/3 strikes, still not banned
When banned is applied, session is not deleted, not redirected to landing page
Input placeholder in deactivate modal can be changed into user's own username
Deactivated account notice properly showing (nice!)
Reactivate screen showing properly (nice!)

All good!

Error in ban resolved by clearing cookies.
Error card should have a background for proper visibility

authors: aaronjoshuaespinosa bricesuazo


text:
feat: add github workflow and script to update synapse tables

Here's the code for updating existing synapse tables when a push to project/data files is made to main.
This script will only work as long as the expected columns remain the same. I ran into too many bugs when trying to feed the synapse client a tsv to update tables with directly, which is why this script gets the rows from a tsv to add them as values.
We get only the files changed and pass them to the script. The script takes the changed files, takes snapshots of the associated tables, deletes all of their data, and repopulates using the new tsv. This may seem inefficient, but it's the best workaround for now, until synapseclient supports upserting to tables.
I also have the code for creating schemas on my fork here: https://github.com/katiestahl/b2ai-standards-registry/blob/main/.github/scripts/create_synapse_tables.py
I was unsure if I should add that to this PR or not, since it's pretty messy and could use some love in that regard (but it gets the job done :-) ), but it illustrates the schemas as they currently are, and if we ever need to add or update columns, we will need to update and run that script.
Also note: before merging this script, we will need to create a service account in synapse for updating the tables and add its auth token as a secret SYNAPSE_AUTH_TOKEN to our github actions. We should have a dedicated account in Synapse that's not tied to any of our personal accounts, so it's clear when the tables have been updated from the github action.

@caufieldjh re-requesting your review since I added some documentation and added the script for updating the table schemas in synapse. Someday, it would be cool to automate this, but synapse's defaults for creating schemas from tsv files directly doesn't quite work (ex; I ran into an issue where I created the tables from the tsv but went to update them after I deleted all of the rows with the exact same data, but the default character limits were not adjusted. So that's why everything has custom processing. Any time synapse client sees a string, it automatically imposes a 50 character limit).


text:
linkset paths wrong for ensembl mus musculus

In ensemble mus musculus linkset files there is an inconsistency between what the linkset path is and what the actual path should be.
http://bridgedb.org/data/linksets/MusMusculus/release87
should be
http://bridgedb.org/data/linksets/release87/MusMusculus
'release87' should be before 'MusMusculus'.

Patch put in place, but needs confirmation that the problem is fixed now.

authors: egonw ianwdunlop

repo: bridgedb/BridgeDb


text:
Html Elements cannot have direct inheritance

Related forum threads:
http://forums.bridge.net/forum/community/help/2153-html-elements-inheritance
http://forums.bridge.net/forum/community/help/2399-not-a-constructor-error
Expected
Not sure. Ideally would work. Might have to mark Element classes as sealed.
Actual
Throws JavaScript error.
TypeError: Illegal constructor.

Steps To Reproduce
public class App
{
    public static void Main()
    {
        var li = new Foo();
    }
}

public class Foo : LIElement { }

Few useful links:
http://stackoverflow.com/questions/1489738/how-to-inherit-from-the-dom-element-class
http://www.html5rocks.com/en/tutorials/webcomponents/customelements/

The second link shows exactly why I want to inherit from Dom elements.
I disagree that these elements should be sealed. Without inheritance, how can we create an element that is not a td inside a table tr. tr element will not identify any other element as a td. It must be a td and not a wrapper for a td. Am I right?

Changing to a question. This isn't really a limitation or defect of Bridge.
Maybe there's some way we could automatically handle this scenario, if someone mocks up the JavaScript required in the compiled output.
Another option is to replicate the inheritance technique used to define LIElement, but that doesn't actually add properties to the client-side instances of the object.
https://github.com/bridgedotnet/Bridge/blob/master/Html5/Elements/LIElement.cs
Hope this helps.

I don't know what is the best option. I know that using inheritance was the way I used to do it in Dart. Why avoid inheritance? Is it wrong?
Anyway, I'm just trying to make polymer work with Bridge because I don't want to use Dart anymore, even knowing that Dart has a solid polymer support.

I don't think there is anything particularly wrong with using inheritance, but it just obviously will not work with the way the JavaScript is currently being emitted.
If you can propose an option for what the compiled output should look like, then we should be able to offer some suggestions on how to achieve that syntax. There are several Attributes that can be used to control the constructor syntax and rendering of the properties.

I'm really new to Bridge and not that good in JS. I will left this task for you, but I think we can use vladsch second link as a reference and maybe see what is Dart output in these cases.
Don't get me wrong. I'm just anxious to make it work. I'm starting a new project, I don't like JS, JQuery, Angular.... Bridge seems to be what I think Microsoft should have done years ago. Thanks.

Happy to hear that Bridge is helpful for you. Thank you for sharing!
As for HTML Elements inheritance, I think there is a related issue with document.registerElement() feature request - #389.

All HTML[Tag]Element classes have been marked as sealed. These classes cannot be inherited.
Please see Issue #2362 and Pull Request #2364.

Please see Support for Custom Elements in Issue #2580.

authors: DaniilVeriga cassiot geoffreymcgill vladsch

repo: bridgedotnet/Bridge


text:
String (s) which are Object(s) should never be equal.

Expected
False
Actual
True
Steps To Reproduce
Type k and k again.
Live Bridge
Dot Net Fiddle
public class Program
{
	static object TryRead ()
	{
		string readline = Console.ReadLine();
		int value;
		if (int.TryParse(readline, out value))
			return value;
		else
			return readline;
	}
	[Ready]
	public static void Main()
	{
        object a = TryRead();
        object b = TryRead();
        Console.WriteLine(a == b);
	}
}

Also, if you type '7' then '7' again it has the same problem.

Yes, @michaelcheers, thank you, we reproduced the problem.
I just simplified you example:
Live Bridge
Dot Net Fiddle
public class Program
{
    [Ready]
    public static void Main()
    {
        object a = Convert.ToString(3);
        object b = Convert.ToString(3);

        var r = a == b;
        Console.WriteLine("Should be false for strings: " + r);

        object a1 = 7;
        object b1 = 7;

        var r1 = a1 == b1;
        Console.WriteLine("Should be false for int: " + r1);
    }
}

String (s) which are Object(s) should never be equal.

and

Boxed value types and String(s) should never be equal.

This titles are misleading, they can be equal, just not in the sample code. It is easy to write code using boxed values or strings which are stored in object-variables and actually must be equal.
So the "never" in "should never be equal" is definitely wrong.
I adjusted the sample code to present an example where the comparison must be true.
using System;

public class Program
{
	public static void Main()
	{
        object a = Convert.ToString(3);
        object b = a;

		var r = a == b;

        Console.WriteLine("Should be true for strings: " + r);

		object a1 = 7;
        object b1 = a1;

		var r1 = a1 == b1;

        Console.WriteLine("Should be true for int: " + r1);
	}
}

Also for strings, relying on them being different is (probably) relying on an implementation detail of the .NET runtime, due to string interning. Different .NET runtimes are allowed to behave differently in regards to which strings are automatically interned and which not, for example some versions of .NET will automatically intern all copies of the empty string to the same one.
Unless I missed something in the .NET specs that forbids it, runtimes would theoretically be allowed to intern all strings, making it behave like JS currently does. Of course native runtimes don't do that since it comes at a performance cost they don't want to pay.
So basically it is a choice on your side whether you want to replicate that implementation detail for strings in your JS-based runtime, in order to care for buggy programs which rely on that implementation detail. (Note that this is only for strings and not for boxed values, for boxed values the behavior is clearly specified, every time a value is boxed a new copy is created.)

@weltkante, thank you for the comments.
Yes, the same boxed object equals to themselves. I corrected the title.
Regarding string interning, as far as I know, in JavaScript world it also depends on implementation details.

When implementing, check this case as well - https://github.com/bridgedotnet/Bridge/issues/1514

authors: LeonidVeriga michaelcheers weltkante


text:
this error

src/flixel/util/_FlxSignal/Macro.cpp
Error: Main.cpp
include\openfl/events/ErrorEvent.h(50): error C2059: syntax error: 'constant'
include\openfl/events/ErrorEvent.h(50): error C2238: unexpected token(s) preceding ';'

src/flixel/util/_FlxSignal/Macro.cpp
Error: Main.cpp
include\openfl/events/ErrorEvent.h(50): error C2059: syntax error: 'constant'
include\openfl/events/ErrorEvent.h(50): error C2238: unexpected token(s) preceding ';'

just remove everything related to error events in main, something is wrong with the crash handler

only true haxe nerds can fix those issues without removing code 😎

only true haxe nerds can fix those issues without removing code 😎

k

repo: brightfyregit/Indie-Cross-Public


text:
Expose open file limit option for prerender command

With very large sites, it is possible that the prerender process will fail with an EMFILE, too many open files error. Currently this can be mitigated only be editing os configuration to increase open file limit. If we exposed an option for configuring the max number of open files, users would have more control over this issue, making the plugin more scalable.

Released in v0.1.0-beta.42.

There should be no performance degradation, but let me know if you notice the pre-rendering taking longer than usual.

authors: brillout gryphonmyers

repo: brillout/vite-plugin-ssr


text:
Update cloudflare-workers documentation

Add an updated example with a shorter worker config, streaming and esbuild.
https://github.com/Immortalin/vite-plugin-ssr-cloudflare-pages-demo

That's quite a nice example 👌.

authors: Immortalin brillout


text:
use docker to run v0.8.0, connect MQTT broker timeout

$ ./loraserver --db-automigrate --net-id 010203 --band EU_863_870 --postgres-dsn "postgres://dbuser:dbpwd@192.168.10.11/loraserver?sslmode=disable" --redis-url "redis://192.168.10.11:6379" --gw-mqtt-server "tcp://test.mosquitto.org:1883" --app-mqtt-server "tcp://test.mosquitto.org:1883"
INFO[0000] starting LoRa Server                          band=EU_863_870 net_id=010203 version=0.8.0
INFO[0000] connecting to postgresql
INFO[0000] setup redis connection pool
INFO[0000] gateway/mqttpubsub: connecting to mqtt broker  server=tcp://test.mosquitto.org:1883
INFO[0000] application/mqttpubsub: connecting to mqtt broker  server=tcp://test.mosquitto.org:1883
INFO[0000] gateway/mqttpubsub: connected to mqtt server
INFO[0000] gateway/mqttpubsub: subscribing to rx topic   topic=gateway/+/rx
INFO[0001] controller/mqttpubsub: connecting to mqtt broker  server=tcp://localhost:1883
INFO[0001] application/mqttpubsub: connected to mqtt server
INFO[0001] application/mqttpubsub: subscribing to tx topic  topic=application/+/node/+/tx
INFO[0001] applying database migrations
INFO[0001] controller/mqttpubsub: connected to mqtt broker
INFO[0001] controller/mqttpubsub: subscribing to tx topic  topic=application/+/node/+/mac/tx
INFO[0001] migrations applied                            count=0
INFO[0001] registering json-rpc handler                  path=/rpc
INFO[0001] registering gui handler                       path=/
INFO[0001] starting http server                          bind=0.0.0.0:8000
when I use docker to run v0.8.0, i/o timeout. v0.7.0 is ok
$ docker run --rm -p 8000:8000 loraserver:0.8.0 loraserver --db-automigrate --net-id 010203 --band EU_863_870 --postgres-dsn "postgres://dbuser:dbpwd@192.168.10.11/loraserver?sslmode=disable" --redis-url "redis://192.168.10.11:6379" --gw-mqtt-server "tcp://test.mosquitto.org:1883" --app-mqtt-server "tcp://test.mosquitto.org:1883"
time="2016-07-04T00:26:07Z" level=info msg="starting LoRa Server" band="EU_863_870" net_id=010203 version=
time="2016-07-04T00:26:07Z" level=info msg="connecting to postgresql"
time="2016-07-04T00:26:07Z" level=info msg="setup redis connection pool"
time="2016-07-04T00:26:07Z" level=info msg="gateway/mqttpubsub: connecting to mqtt broker" server="tcp://test.mosquitto.org:1883"
time="2016-07-04T00:26:22Z" level=fatal msg="gateway-backend setup failed: gateway/mqttpubsub: connecting to broker failed: Network Error : dial tcp 85.119.83.194:1883: i/o timeout"
$ docker -v
Docker version 1.11.2, build b9f10c9

I'm not sure how this is related to LoRa Server if it works without Docker. Might as well be a Docker network related issue. Out of curiosity I tried to reproduce your issue, but works like a charm here:
docker-compose run --rm loraserver bash

root@3dd9721cf9be:/go/src/github.com/brocaar/loraserver# loraserver --db-automigrate --net-id 010203 --band EU_863_870 --gw-mqtt-server "tcp://test.mosquitto.org:1883" --app-mqtt-server "tcp://test.mosquitto.org:1883" --controller-mqtt-server "tcp://test.mosquitto.org:1883"
INFO[0000] starting LoRa Server                          band=EU_863_870 net_id=010203 version=0.8.0-5-geb998f7
INFO[0000] connecting to postgresql
INFO[0000] setup redis connection pool
INFO[0000] gateway/mqttpubsub: connecting to mqtt broker  server=tcp://test.mosquitto.org:1883
INFO[0000] application/mqttpubsub: connecting to mqtt broker  server=tcp://test.mosquitto.org:1883
INFO[0000] gateway/mqttpubsub: connected to mqtt server
INFO[0000] gateway/mqttpubsub: subscribing to rx topic   topic=gateway/+/rx
INFO[0000] controller/mqttpubsub: connecting to mqtt broker  server=tcp://test.mosquitto.org:1883
INFO[0000] application/mqttpubsub: connected to mqtt server
INFO[0000] application/mqttpubsub: subscribing to tx topic  topic=application/+/node/+/tx
INFO[0000] applying database migrations
INFO[0000] controller/mqttpubsub: connected to mqtt broker
INFO[0000] controller/mqttpubsub: subscribing to tx topic  topic=application/+/node/+/mac/tx
INFO[0000] migrations applied                            count=2
INFO[0000] registering json-rpc handler                  path=/rpc
INFO[0000] registering gui handler                       path=/
INFO[0000] starting http server                          bind=0.0.0.0:8000

Btw, don't forget to pass the --controller-mqtt-server.

authors: brocaar ksuie

repo: brocaar/loraserver


text:
html lang=".." instead of body lang=".."

Hi!
First - thanks for a great little library :)
As it seem impossible to properly set body lang=".." in fresh, and as html lang=".." is a standard feature. Wouldn't it be better to use html lang=".." instead?
https://github.com/brocococonut/freshlate/blob/ac12cc5fddde4f3e0e34e44fb4bcd65d81906b52/freshlate/main.ts#L10
That line could be changed to
let language = document.documentElement.lang;

html lang=".." is set by
await start(
    manifest,
    {
        plugins: [languagePlugin({ ...languageConfig })],
        render: (ctx, render) => {
            ctx.lang = "sv"
            render();
        }
    }
);

While body lang=".." seem to be impossible to set, as fresh injects a clean  tag before any tsx is rendered, if you pass <body lang="sv"> as tsx, the actual output seem to be <body><body lang="sv">

Hmm, html lang is application wide - cannot be changed per route. So maybe it's just usable as an additional fallback.
But anyhow, body lang seem to be a bad choice for per route languages, make there is another (better) option?

Hey there!
Thanks for the first issue!
I was actually just thinking that a better route might be to use a "set-lang" property (or something similar) on any given tag and keep it as the current language until it reaches another set-lang. The main issue I can forsee doing it this way is it wouldn't necessarily be cascading like CSS would, but instead would be sequential and could be a bit messy when used across components. It would allow for customising the language used per route though.
As each request is server rendered, it might be best to just split the handling of what language to use off to the server, and set all subsequent renders that are client side to the one language based on what the server provides. It won't be reactive that way though 🤔
There's pitfalls with most ways of doing it unfortunately. I actually spun the translation library off into a separate package in my own code and was just using that with svelte to be completely honest 😅 I definitely should update and maintain this though.

The repo has been migrated over to https://github.com/locale-kit/locale-kit and https://github.com/locale-kit/locale-kit-fresh :)
Lemme know if that works for ya!

authors: Hexagon brocococonut

repo: brocococonut/freshlate


text:
Support bare repos

"bare": true
in the settings would be great

foreach needs to skip those

repo: brocode/fw

license: WTFPL


text:
[Bug]: # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbea6858c Trace/breakpoint trap (core dumped)

Version
0.8.0
Node version
no idea
Operating System type
Docker
Operating system version
Raspberry pi buster raspbian 10
Describe the bug
I did the following on my Raspberry PI 4:
pi@raspberrypi4:~ $ docker run -it -e USERNAME=xx@debeertjes.com -e PASSWORD=xxxx -p 3300:3000 bropat/eufy-security-ws:latest
Unable to find image 'bropat/eufy-security-ws:latest' locally
latest: Pulling from bropat/eufy-security-ws
5480d2ca1740: Already exists
00d662877661: Already exists
c234d4aeb7df: Already exists
9a2fd5970489: Already exists
649bdae7192a: Pull complete
95fb95b35ebd: Pull complete
79fdd427caa8: Pull complete
14f4fc71b2ae: Pull complete
6f7cc63d368a: Pull complete
f825059e16f1: Pull complete
Digest: sha256:aacda17a61ac5193029ac53303330525fe4296a4dce58c33a153208c96bab689
Status: Downloaded newer image for bropat/eufy-security-ws:latest

Fatal error in , line 0
unreachable code

#FailureMessage Object: 0xbea6858c
Trace/breakpoint trap (core dumped)
Can you tell me what's wrong?
I used port 3300 because port 3000 is used for zwave2mqtt
To reproduce
I did the following on my Raspberry PI 4:
pi@raspberrypi4:~ $ docker run -it -e USERNAME=xx@debeertjes.com -e PASSWORD=xxxx -p 3300:3000 bropat/eufy-security-ws:latest
Unable to find image 'bropat/eufy-security-ws:latest' locally
latest: Pulling from bropat/eufy-security-ws
5480d2ca1740: Already exists
00d662877661: Already exists
c234d4aeb7df: Already exists
9a2fd5970489: Already exists
649bdae7192a: Pull complete
95fb95b35ebd: Pull complete
79fdd427caa8: Pull complete
14f4fc71b2ae: Pull complete
6f7cc63d368a: Pull complete
f825059e16f1: Pull complete
Digest: sha256:aacda17a61ac5193029ac53303330525fe4296a4dce58c33a153208c96bab689
Status: Downloaded newer image for bropat/eufy-security-ws:latest

Fatal error in , line 0
unreachable code

#FailureMessage Object: 0xbea6858c
Trace/breakpoint trap (core dumped)
Can you tell me what's wrong?
I used port 3300 because port 3000 is used for zwave2mqtt
Screenshots & Logfiles
See above
Additional context

look here #47

pi@raspberrypi4:~ $ docker run -it --privileged -e USERNAME=xx@debeertjes.com -e PASSWORD=xxxx -p 3300:3000 bropat/eufy-security-ws:latest
2022-02-06 13:30:13.737  INFO  Eufy Security server listening on host 0.0.0.0, port 3000
2022-02-06 13:30:16.033  ERROR MQTT Error
Error  Connection refused: Not authorized
details:
{
code: 5
}
error stack:
• client.js:1386 MqttClient._handleConnack
node_modules/mqtt/lib/client.js:1386:17
• client.js:547 MqttClient._handlePacket
node_modules/mqtt/lib/client.js:547:12
• client.js:436 work
node_modules/mqtt/lib/client.js:436:12
• client.js:450 writable._write
node_modules/mqtt/lib/client.js:450:5
• _stream_writable.js:409 doWrite
node_modules/readable-stream/lib/_stream_writable.js:409:139
• _stream_writable.js:398 writeOrBuffer
node_modules/readable-stream/lib/_stream_writable.js:398:5
• _stream_writable.js:307 Writable.write
node_modules/readable-stream/lib/_stream_writable.js:307:11
• readable:754 ondata
node:internal/streams/readable:754:22
• node:events:390 emit
node:events:390:28
• readable:315 addChunk
node:internal/streams/readable:315:12
2022-02-06 13:30:16.074  INFO  MQTT connection closed
2022-02-06 13:30:17.174  INFO  No stations found.
2022-02-06 13:30:17.708  INFO  No devices found.
2022-02-06 13:30:17.735  INFO  Push notification connection successfully established

Is this normal:
@.:~ $ docker run -it --privileged -e USERNAME=
@. -e PASSWORD=xxxx -p 3300:3000
bropat/eufy-security-ws:latest
2022-02-06 13:30:13.737  INFO  Eufy Security server listening on host
0.0.0.0, port 3000
2022-02-06 13:30:16.033  ERROR MQTT Error
Error  Connection refused: Not authorized
details:
{
code: 5
}
error stack:
• client.js:1386 MqttClient._handleConnack
node_modules/mqtt/lib/client.js:1386:17
• client.js:547 MqttClient._handlePacket
node_modules/mqtt/lib/client.js:547:12
• client.js:436 work
node_modules/mqtt/lib/client.js:436:12
• client.js:450 writable._write
node_modules/mqtt/lib/client.js:450:5
• _stream_writable.js:409 doWrite
node_modules/readable-stream/lib/_stream_writable.js:409:139
• _stream_writable.js:398 writeOrBuffer
node_modules/readable-stream/lib/_stream_writable.js:398:5
• _stream_writable.js:307 Writable.write
node_modules/readable-stream/lib/_stream_writable.js:307:11
• readable:754 ondata
node:internal/streams/readable:754:22
• node:events:390 emit
node:events:390:28
• readable:315 addChunk
node:internal/streams/readable:315:12
2022-02-06 13:30:16.074  INFO  MQTT connection closed
2022-02-06 13:30:17.174  INFO  No stations found.
2022-02-06 13:30:17.708  INFO  No devices found.
2022-02-06 13:30:17.735  INFO  Push notification connection successfully
established
On Sun, Feb 6, 2022 at 2:22 PM bropat @.***> wrote:

Closed #78 https://github.com/bropat/eufy-security-ws/issues/78.
—
Reply to this email directly, view it on GitHub
https://github.com/bropat/eufy-security-ws/issues/78#event-6015030259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXIR3XBM4W5CSRMWUMB3F4DUZZYZVANCNFSM5NVKFQVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

repo: bropat/eufy-security-ws


text:
Cryptographic Issues

Using old MD5 encryption - See page 4 of the Security Report as it includes the files and
line number with a security issue

[x] test: make changes, rebuild docker container, build and complete test survey

repo: brown-ccv/redcap-image-annotator


text:
Get more Entities than cs_player_controller entities (eg. Chickens)

Hello @bruhmoment21,
first of all: thank you for you nicely written CS2 SDK.
I am using it, to learn more about the Source2 world.
Back to my "issues":
To get all available entities, I first extended the CEntityIdentity class using this dump:
https://github.com/Rebirator/CS2/blob/main/Schemes Dump.txt#L436
Now it looks like this:
class CEntityIdentity {
   public:
    SCHEMA_FIELD(m_designerName, "CEntityIdentity", "m_designerName",
                 const char*);
    SCHEMA_FIELD(m_name, "CEntityIdentity", "m_name",
                 const char*);
    SCHEMA_FIELD(m_pPrev, "CEntityIdentity", "m_pPrev",
                 CEntityIdentity*);
    SCHEMA_FIELD(m_pNext, "CEntityIdentity", "m_pNext",
                 CEntityIdentity*);
    SCHEMA_FIELD(m_pPrevByClass, "CEntityIdentity", "m_pPrevByClass",
                 CEntityIdentity*);
    SCHEMA_FIELD(m_pNextByClass, "CEntityIdentity", "m_pNextByClass",
                 CEntityIdentity*);
};

In esp::Render() we get a CCSPlayerController* (basically CBasePlayerController -> C_BaseEntity -> CEntityInstance -> CEntityIdentity*)
Adapting your bool C_BaseEntity::IsPlayerController(), we should be able to just cast the BaseEntity to  CEntityIdentity* and be able to check all the pIdentity->m_designerName().
Due to the fact that there are more Entities than just the Player entities, we need to "break out" and get the full list of entities.
void C_BaseEntity::checkAllEntities() {
    CEntityIdentity* pIdentity = m_pEntity();
    int o = 0;
    if (pIdentity) {

        while (pIdentity->m_pPrev() != nullptr) {
           pIdentity = pIdentity->m_pPrev();
        }
        while (pIdentity != nullptr) {

            if (pIdentity->m_designerName())  //like C_BaseEntitiy::IsPlayerControlled()
            {
                LOG("%i %s\n", ++o, pIdentity->m_designerName());
            }
            pIdentity = pIdentity->m_pNext();
        }
    }
}

result is this list:

1 weapon_ak47
2 weapon_ak47
3 weapon_sg556
4 weapon_famas
5 weapon_galilar
6 weapon_scar20
7 weapon_p250
8 weapon_scar20
9 weapon_m4a1
10 weapon_p250
11 weapon_galilar
12 info_particle_system
13 weapon_m249
14 weapon_fiveseven
15 viewmodel_attachment_model
16 viewmodel_attachment_model
17 cs_player_controller
18 cs_player_controller
19 cs_player_controller
20 cs_player_controller
21 cs_player_controller
22 cs_player_controller
23 cs_player_controller
24 cs_player_controller
25 cs_player_controller
26 csgo_viewmodel
27 point_worldtext
28 post_processing_volume
29 point_camera
30 point_camera
31 point_camera
32 point_camera
33 point_camera
34 basemodelentity
35 basemodelentity
36 basemodelentity
37 basemodelentity
38 basemodelentity
39 basemodelentity
40 basemodelentity
41 basemodelentity
42 basemodelentity
43 basemodelentity
44 basemodelentity
45 basemodelentity
46 basemodelentity
47 basemodelentity
48 basemodelentity
49 basemodelentity
50 basemodelentity
51 basemodelentity
52 basemodelentity
53 basemodelentity
54 basemodelentity
55 basemodelentity
56 basemodelentity
57 basemodelentity
58 basemodelentity
59 basemodelentity
60 basemodelentity
61 basemodelentity
62 basemodelentity
63 basemodelentity
64 basemodelentity
65 basemodelentity
66 basemodelentity
67 basemodelentity
68 basemodelentity
69 basemodelentity
70 basemodelentity
71 basemodelentity
72 basemodelentity
73 basemodelentity
74 basemodelentity
75 basemodelentity
76 basemodelentity
77 weapon_knife
78 c_cs_observer_for_precache
79 c_cs_player_for_precache
80 weapon_knife
81 weapon_glock
82 c_cs_observer_for_precache
83 c_cs_player_for_precache
84 weapon_knife
85 weapon_glock
86 c_cs_observer_for_precache
87 c_cs_player_for_precache
88 weapon_knife
89 c_cs_observer_for_precache
90 c_cs_player_for_precache
91 weapon_knife
92 weapon_glock
93 c_cs_observer_for_precache
94 c_cs_player_for_precache
95 weapon_knife
96 weapon_hkp2000
97 c_cs_observer_for_precache
98 c_cs_player_for_precache
99 weapon_knife
100 weapon_glock
101 c_cs_observer_for_precache
102 c_cs_player_for_precache
103 weapon_knife
104 c_cs_observer_for_precache
105 c_cs_player_for_precache
106 weapon_knife
107 weapon_hkp2000
108 c_cs_observer_for_precache
109 c_cs_player_for_precache
110 weapon_knife
111 weapon_glock
112 map_preview_camera_path
113 point_camera_vertical_fov
114 csgo_previewplayer
115 light_environment
116 env_cubemap_box
117 env_combined_light_probe_volume
118 info_particle_system
119 info_particle_system
120 info_particle_system
121 point_camera
122 light_environment
123 point_camera
124 light_environment
125 point_camera
126 light_environment
127 point_camera
128 light_environment
129 terrorist_team_intro_camera
130 map_preview_camera_path_node
131 map_preview_camera_path_node
132 map_preview_camera_path_node
133 counterterrorist_team_intro_camera
134 map_preview_camera_path_node
135 map_preview_camera_path_node
136 map_preview_camera_path_node
137 end_of_match_lineup_start
138 end_of_match_lineup_end
139 end_of_match_camera
140 map_preview_camera_path_node
141 map_preview_camera_path_node
142 map_preview_camera_path_node
143 team_select_camera
144 map_preview_camera_path_node
145 map_preview_camera_path_node
146 env_combined_light_probe_volume
147 light_environment
148 path_particle_rope
149 path_particle_rope
150 path_particle_rope
151 path_particle_rope
152 path_particle_rope
153 path_particle_rope
154 path_particle_rope
155 path_particle_rope
156 path_particle_rope
157 path_particle_rope
158 path_particle_rope
159 path_particle_rope
160 path_particle_rope
161 path_particle_rope
162 path_particle_rope
163 path_particle_rope
164 path_particle_rope
165 path_particle_rope
166 path_particle_rope
167 path_particle_rope
168 path_particle_rope
169 path_particle_rope
170 path_particle_rope
171 path_particle_rope
172 path_particle_rope
173 path_particle_rope
174 path_particle_rope
175 path_particle_rope
176 path_particle_rope
177 path_particle_rope
178 path_particle_rope
179 path_particle_rope
180 path_particle_rope
181 path_particle_rope
182 path_particle_rope
183 path_particle_rope
184 path_particle_rope
185 path_particle_rope
186 path_particle_rope
187 path_particle_rope
188 path_particle_rope
189 path_particle_rope
190 path_particle_rope
191 path_particle_rope
192 path_particle_rope
193 path_particle_rope
194 path_particle_rope
195 path_particle_rope
196 path_particle_rope
197 path_particle_rope
198 path_particle_rope
199 path_particle_rope
200 path_particle_rope
201 path_particle_rope
202 path_particle_rope
203 path_particle_rope
204 path_particle_rope
205 path_particle_rope
206 path_particle_rope
207 path_particle_rope
208 env_combined_light_probe_volume
209 env_combined_light_probe_volume
210 env_combined_light_probe_volume
211 env_combined_light_probe_volume
212 env_combined_light_probe_volume
213 env_combined_light_probe_volume
214 env_combined_light_probe_volume
215 env_combined_light_probe_volume
216 env_combined_light_probe_volume
217 env_combined_light_probe_volume
218 env_combined_light_probe_volume
219 env_combined_light_probe_volume
220 env_combined_light_probe_volume
221 env_combined_light_probe_volume
222 env_combined_light_probe_volume
223 env_combined_light_probe_volume
224 env_combined_light_probe_volume
225 env_combined_light_probe_volume
226 env_combined_light_probe_volume
227 env_combined_light_probe_volume
228 env_combined_light_probe_volume
229 env_combined_light_probe_volume
230 env_combined_light_probe_volume
231 env_combined_light_probe_volume
232 env_combined_light_probe_volume
233 env_combined_light_probe_volume
234 env_combined_light_probe_volume
235 env_combined_light_probe_volume
236 env_combined_light_probe_volume
237 env_combined_light_probe_volume
238 env_combined_light_probe_volume
239 env_combined_light_probe_volume
240 env_combined_light_probe_volume
241 env_combined_light_probe_volume
242 env_combined_light_probe_volume
243 env_combined_light_probe_volume
244 env_combined_light_probe_volume
245 env_combined_light_probe_volume
246 env_combined_light_probe_volume
247 env_combined_light_probe_volume
248 env_combined_light_probe_volume
249 env_combined_light_probe_volume
250 env_combined_light_probe_volume
251 env_combined_light_probe_volume
252 path_particle_rope
253 path_particle_rope
254 path_particle_rope
255 path_particle_rope
256 path_particle_rope
257 path_particle_rope
258 path_particle_rope
259 path_particle_rope
260 path_particle_rope
261 path_particle_rope
262 path_particle_rope
263 path_particle_rope
264 path_particle_rope
265 path_particle_rope
266 path_particle_rope
267 path_particle_rope
268 path_particle_rope
269 path_particle_rope
270 path_particle_rope
271 path_particle_rope
272 path_particle_rope
273 path_particle_rope
274 path_particle_rope
275 path_particle_rope
276 path_particle_rope
277 path_particle_rope
278 path_particle_rope
279 path_particle_rope
280 path_particle_rope
281 path_particle_rope
282 path_particle_rope
283 path_particle_rope
284 path_particle_rope
285 path_particle_rope
286 path_particle_rope
287 path_particle_rope
288 path_particle_rope
289 path_particle_rope
290 path_particle_rope
291 path_particle_rope
292 path_particle_rope
293 path_particle_rope
294 path_particle_rope
295 path_particle_rope
296 path_particle_rope
297 path_particle_rope
298 path_particle_rope
299 path_particle_rope
300 path_particle_rope
301 path_particle_rope
302 path_particle_rope
303 path_particle_rope
304 path_particle_rope
305 path_particle_rope
306 path_particle_rope
307 path_particle_rope
308 path_particle_rope
309 path_particle_rope
310 light_omni2
311 light_omni2
312 light_rect
313 light_rect
314 light_omni2
315 light_rect
316 light_rect
317 light_rect
318 light_rect
319 light_rect
320 light_rect
321 light_rect
322 light_rect
323 light_rect
324 light_rect
325 light_rect
326 light_rect
327 light_rect
328 light_omni2
329 light_rect
330 light_omni2
331 light_rect
332 light_rect
333 light_omni2
334 light_rect
335 light_rect
336 light_rect
337 light_rect
338 light_rect
339 light_rect
340 light_environment
341 light_rect
342 light_rect
343 worldent
344 cs_player_controller
345 cs_player_manager
346 cs_gamerules
347 vote_controller
348 vote_controller
349 vote_controller
350 env_cubemap_fog
351 env_sky
352 env_sky
353 sky_camera
354 env_sky
355 team_select_terrorist
356 team_select_terrorist
357 team_select_terrorist
358 team_select_terrorist
359 team_select_terrorist
360 team_select_terrorist
361 team_select_terrorist
362 team_select_terrorist
363 team_select_terrorist
364 team_select_counterterrorist
365 team_select_counterterrorist
366 team_select_counterterrorist
367 team_select_counterterrorist
368 team_select_counterterrorist
369 team_select_counterterrorist
370 team_select_counterterrorist
371 team_select_counterterrorist
372 team_select_counterterrorist
373 team_select_counterterrorist
374 team_select_terrorist
375 team_intro_counterterrorist
376 team_intro_counterterrorist
377 team_intro_counterterrorist
378 team_intro_counterterrorist
379 team_intro_counterterrorist
380 team_intro_terrorist
381 team_intro_terrorist
382 team_intro_terrorist
383 team_intro_terrorist
384 team_intro_terrorist
385 c_cs_observer_for_precache
386 c_cs_player_for_precache

I suspect, that (for example), chickens reside inside a basemodelentity (because: CChicken -> CDynamicProp -> C_BreakableProp -> CBaseProp -> CBaseAnimGraph -> C_BaseModelEntity).
How can I confirm, that a BaseModelEntity is in fact a Chicken?
Is there a better/faster solution to get all Entities without the cs_player_controller detour?
I am thankful for all suggestions leading in the right direction.

Sup, check this(see how that dude gets the smoke?) and this for GetClassInformation, also this.
Do you happen to have implemented Skeleton ESP? I'm getting an exception in GetBoneLocationAndRotation and would like some help before I commit die.

Edit: I realized I didn't read all the code and m_designerName is part of CEntityIdentity. Try m_name?

This does not work, because not all Entities have a name / Designername
here ist a full list of entities that I got using CEntityIdentity:
1 Designer: (null) | Name: (null)
2 Designer: (null) | Name: (null)
3 Designer: (null) | Name: (null)
4 Designer: (null) | Name: (null)
5 Designer: (null) | Name: (null)
6 Designer: (null) | Name: (null)
7 Designer: (null) | Name: (null)
8 Designer: (null) | Name: (null)
9 Designer: (null) | Name: (null)
10 Designer: (null) | Name: (null)
11 Designer: info_particle_system | Name: (null)
12 Designer: weapon_ump45 | Name: (null)
13 Designer: viewmodel_attachment_model | Name: (null)
14 Designer: viewmodel_attachment_model | Name: (null)
15 Designer: basemodelentity | Name: (null)
16 Designer: basemodelentity | Name: (null)
17 Designer: basemodelentity | Name: (null)
18 Designer: basemodelentity | Name: (null)
19 Designer: basemodelentity | Name: (null)
20 Designer: basemodelentity | Name: (null)
21 Designer: basemodelentity | Name: (null)
22 Designer: basemodelentity | Name: (null)
23 Designer: basemodelentity | Name: (null)
24 Designer: basemodelentity | Name: (null)
25 Designer: basemodelentity | Name: (null)
26 Designer: weapon_knife | Name: (null)
27 Designer: weapon_hkp2000 | Name: (null)
28 Designer: basemodelentity | Name: (null)
29 Designer: basemodelentity | Name: (null)
30 Designer: basemodelentity | Name: (null)
31 Designer: basemodelentity | Name: (null)
32 Designer: basemodelentity | Name: (null)
33 Designer: (null) | Name: (null)
34 Designer: (null) | Name: (null)
35 Designer: basemodelentity | Name: (null)
36 Designer: basemodelentity | Name: (null)
37 Designer: basemodelentity | Name: (null)
38 Designer: basemodelentity | Name: (null)
39 Designer: basemodelentity | Name: (null)
40 Designer: basemodelentity | Name: (null)
41 Designer: basemodelentity | Name: (null)
42 Designer: basemodelentity | Name: (null)
43 Designer: basemodelentity | Name: (null)
44 Designer: basemodelentity | Name: (null)
45 Designer: basemodelentity | Name: (null)
46 Designer: basemodelentity | Name: (null)
47 Designer: basemodelentity | Name: (null)
48 Designer: basemodelentity | Name: (null)
49 Designer: basemodelentity | Name: (null)
50 Designer: basemodelentity | Name: (null)
51 Designer: basemodelentity | Name: (null)
52 Designer: basemodelentity | Name: (null)
53 Designer: basemodelentity | Name: (null)
54 Designer: basemodelentity | Name: (null)
55 Designer: csgo_viewmodel | Name: (null)
56 Designer: basemodelentity | Name: (null)
57 Designer: basemodelentity | Name: (null)
58 Designer: basemodelentity | Name: (null)
59 Designer: basemodelentity | Name: (null)
60 Designer: basemodelentity | Name: (null)
61 Designer: basemodelentity | Name: (null)
62 Designer: basemodelentity | Name: (null)
63 Designer: point_camera | Name: screenshot_3
64 Designer: point_camera | Name: screenshot_2
65 Designer: point_camera | Name: screenshot_1
66 Designer: point_camera | Name: screenshot_0
67 Designer: point_camera | Name: screenshot
68 Designer: post_processing_volume | Name: (null)
69 Designer: (null) | Name: (null)
70 Designer: point_worldtext | Name: (null)
71 Designer: (null) | Name: (null)
72 Designer: (null) | Name: (null)
73 Designer: map_preview_camera_path | Name: (null)
74 Designer: point_camera_vertical_fov | Name: cam_buymenu
75 Designer: csgo_previewplayer | Name: vanity_character
76 Designer: light_environment | Name: (null)
77 Designer: env_cubemap_box | Name: (null)
78 Designer: env_combined_light_probe_volume | Name: (null)
79 Designer: csgo_previewmodel | Name: (null)
80 Designer: csgo_previewmodel | Name: (null)
81 Designer: weapon_negev | Name: (null)
82 Designer: weapon_glock | Name: (null)
83 Designer: env_combined_light_probe_volume | Name: cm_sky
84 Designer: point_camera | Name: cam_models
85 Designer: info_map_preview_particle_system | Name: (null)
86 Designer: info_map_preview_particle_system | Name: (null)
87 Designer: path_particle_rope | Name: (null)
88 Designer: csgo_previewplayer | Name: (null)
89 Designer: env_combined_light_probe_volume | Name: (null)
90 Designer: path_particle_rope | Name: (null)
91 Designer: path_particle_rope | Name: (null)
92 Designer: prop_dynamic | Name: (null)
93 Designer: csgo_previewplayer | Name: (null)
94 Designer: post_processing_volume | Name: (null)
95 Designer: light_environment | Name: (null)
96 Designer: env_sky | Name: dust_sky
97 Designer: light_omni2 | Name: (null)
98 Designer: env_cubemap_fog | Name: (null)
99 Designer: info_particle_system | Name: (null)
100 Designer: info_particle_system | Name: (null)
101 Designer: info_particle_system | Name: (null)
102 Designer: point_camera | Name: shot_camera
103 Designer: light_environment | Name: (null)
104 Designer: point_camera | Name: shot_camera
105 Designer: light_environment | Name: (null)
106 Designer: point_camera | Name: shot_camera
107 Designer: light_environment | Name: (null)
108 Designer: point_camera | Name: shot_camera
109 Designer: light_environment | Name: (null)
110 Designer: terrorist_team_intro_camera | Name: (null)
111 Designer: map_preview_camera_path_node | Name: (null)
112 Designer: map_preview_camera_path_node | Name: (null)
113 Designer: map_preview_camera_path_node | Name: (null)
114 Designer: counterterrorist_team_intro_camera | Name: (null)
115 Designer: map_preview_camera_path_node | Name: (null)
116 Designer: map_preview_camera_path_node | Name: (null)
117 Designer: map_preview_camera_path_node | Name: (null)
118 Designer: end_of_match_lineup_start | Name: (null)
119 Designer: end_of_match_lineup_end | Name: (null)
120 Designer: end_of_match_camera | Name: (null)
121 Designer: map_preview_camera_path_node | Name: (null)
122 Designer: map_preview_camera_path_node | Name: (null)
123 Designer: map_preview_camera_path_node | Name: (null)
124 Designer: team_select_camera | Name: (null)
125 Designer: map_preview_camera_path_node | Name: (null)
126 Designer: map_preview_camera_path_node | Name: (null)
127 Designer: env_combined_light_probe_volume | Name: (null)
128 Designer: light_environment | Name: (null)
129 Designer: path_particle_rope | Name: (null)
130 Designer: path_particle_rope | Name: (null)
131 Designer: path_particle_rope | Name: (null)
132 Designer: path_particle_rope | Name: (null)
133 Designer: path_particle_rope | Name: (null)
134 Designer: path_particle_rope | Name: (null)
135 Designer: path_particle_rope | Name: (null)
136 Designer: path_particle_rope | Name: (null)
137 Designer: path_particle_rope | Name: (null)
138 Designer: path_particle_rope | Name: (null)
139 Designer: path_particle_rope | Name: (null)
140 Designer: path_particle_rope | Name: (null)
141 Designer: path_particle_rope | Name: (null)
142 Designer: path_particle_rope | Name: (null)
143 Designer: path_particle_rope | Name: (null)
144 Designer: path_particle_rope | Name: (null)
145 Designer: path_particle_rope | Name: (null)
146 Designer: path_particle_rope | Name: (null)
147 Designer: path_particle_rope | Name: (null)
148 Designer: path_particle_rope | Name: (null)
149 Designer: path_particle_rope | Name: (null)
150 Designer: path_particle_rope | Name: (null)
151 Designer: path_particle_rope | Name: (null)
152 Designer: path_particle_rope | Name: (null)
153 Designer: path_particle_rope | Name: (null)
154 Designer: path_particle_rope | Name: (null)
155 Designer: path_particle_rope | Name: (null)
156 Designer: path_particle_rope | Name: (null)
157 Designer: path_particle_rope | Name: (null)
158 Designer: path_particle_rope | Name: (null)
159 Designer: path_particle_rope | Name: (null)
160 Designer: path_particle_rope | Name: (null)
161 Designer: path_particle_rope | Name: (null)
162 Designer: path_particle_rope | Name: (null)
163 Designer: path_particle_rope | Name: (null)
164 Designer: path_particle_rope | Name: (null)
165 Designer: path_particle_rope | Name: (null)
166 Designer: path_particle_rope | Name: (null)
167 Designer: path_particle_rope | Name: (null)
168 Designer: path_particle_rope | Name: (null)
169 Designer: path_particle_rope | Name: (null)
170 Designer: path_particle_rope | Name: (null)
171 Designer: path_particle_rope | Name: (null)
172 Designer: path_particle_rope | Name: (null)
173 Designer: path_particle_rope | Name: (null)
174 Designer: path_particle_rope | Name: (null)
175 Designer: path_particle_rope | Name: (null)
176 Designer: path_particle_rope | Name: (null)
177 Designer: path_particle_rope | Name: (null)
178 Designer: path_particle_rope | Name: (null)
179 Designer: path_particle_rope | Name: (null)
180 Designer: path_particle_rope | Name: (null)
181 Designer: path_particle_rope | Name: (null)
182 Designer: path_particle_rope | Name: (null)
183 Designer: path_particle_rope | Name: (null)
184 Designer: path_particle_rope | Name: (null)
185 Designer: path_particle_rope | Name: (null)
186 Designer: path_particle_rope | Name: (null)
187 Designer: path_particle_rope | Name: (null)
188 Designer: path_particle_rope | Name: (null)
189 Designer: env_combined_light_probe_volume | Name: (null)
190 Designer: env_combined_light_probe_volume | Name: (null)
191 Designer: env_combined_light_probe_volume | Name: (null)
192 Designer: env_combined_light_probe_volume | Name: cm_tcourtyard
193 Designer: env_combined_light_probe_volume | Name: (null)
194 Designer: env_combined_light_probe_volume | Name: cm_courtayrd_02
195 Designer: env_combined_light_probe_volume | Name: (null)
196 Designer: env_combined_light_probe_volume | Name: (null)
197 Designer: env_combined_light_probe_volume | Name: cm_001
198 Designer: env_combined_light_probe_volume | Name: cm_ramp_001
199 Designer: env_combined_light_probe_volume | Name: (null)
200 Designer: env_combined_light_probe_volume | Name: cm_235498
201 Designer: env_combined_light_probe_volume | Name: (null)
202 Designer: env_combined_light_probe_volume | Name: (null)
203 Designer: env_combined_light_probe_volume | Name: cm_street1
204 Designer: env_combined_light_probe_volume | Name: cm_004
205 Designer: env_combined_light_probe_volume | Name: cm_dip
206 Designer: env_combined_light_probe_volume | Name: (null)
207 Designer: env_combined_light_probe_volume | Name: (null)
208 Designer: env_combined_light_probe_volume | Name: (null)
209 Designer: env_combined_light_probe_volume | Name: cm_tunnel_01
210 Designer: env_combined_light_probe_volume | Name: (null)
211 Designer: env_combined_light_probe_volume | Name: (null)
212 Designer: env_combined_light_probe_volume | Name: cm_t_courtyard
213 Designer: env_combined_light_probe_volume | Name: (null)
214 Designer: env_combined_light_probe_volume | Name: cm_alley_01
215 Designer: env_combined_light_probe_volume | Name: cm_tunnel_03
216 Designer: env_combined_light_probe_volume | Name: cm_tunnel_3a
217 Designer: env_combined_light_probe_volume | Name: cm_ctspawnramp
218 Designer: env_combined_light_probe_volume | Name: (null)
219 Designer: env_combined_light_probe_volume | Name: cm_sky
220 Designer: env_combined_light_probe_volume | Name: cm_tunnel_01b
221 Designer: env_combined_light_probe_volume | Name: (null)
222 Designer: env_combined_light_probe_volume | Name: (null)
223 Designer: env_combined_light_probe_volume | Name: (null)
224 Designer: env_combined_light_probe_volume | Name: (null)
225 Designer: env_combined_light_probe_volume | Name: (null)
226 Designer: env_combined_light_probe_volume | Name: (null)
227 Designer: env_combined_light_probe_volume | Name: (null)
228 Designer: env_combined_light_probe_volume | Name: (null)
229 Designer: env_combined_light_probe_volume | Name: (null)
230 Designer: env_combined_light_probe_volume | Name: (null)
231 Designer: env_combined_light_probe_volume | Name: (null)
232 Designer: env_combined_light_probe_volume | Name: (null)
233 Designer: path_particle_rope | Name: (null)
234 Designer: path_particle_rope | Name: (null)
235 Designer: path_particle_rope | Name: (null)
236 Designer: path_particle_rope | Name: (null)
237 Designer: path_particle_rope | Name: (null)
238 Designer: path_particle_rope | Name: (null)
239 Designer: path_particle_rope | Name: (null)
240 Designer: path_particle_rope | Name: (null)
241 Designer: path_particle_rope | Name: (null)
242 Designer: path_particle_rope | Name: (null)
243 Designer: path_particle_rope | Name: (null)
244 Designer: path_particle_rope | Name: (null)
245 Designer: path_particle_rope | Name: (null)
246 Designer: path_particle_rope | Name: (null)
247 Designer: path_particle_rope | Name: (null)
248 Designer: path_particle_rope | Name: (null)
249 Designer: path_particle_rope | Name: (null)
250 Designer: path_particle_rope | Name: (null)
251 Designer: path_particle_rope | Name: (null)
252 Designer: path_particle_rope | Name: (null)
253 Designer: path_particle_rope | Name: (null)
254 Designer: path_particle_rope | Name: (null)
255 Designer: path_particle_rope | Name: (null)
256 Designer: path_particle_rope | Name: (null)
257 Designer: path_particle_rope | Name: (null)
258 Designer: path_particle_rope | Name: (null)
259 Designer: path_particle_rope | Name: (null)
260 Designer: path_particle_rope | Name: (null)
261 Designer: path_particle_rope | Name: (null)
262 Designer: path_particle_rope | Name: (null)
263 Designer: path_particle_rope | Name: (null)
264 Designer: path_particle_rope | Name: (null)
265 Designer: path_particle_rope | Name: (null)
266 Designer: path_particle_rope | Name: (null)
267 Designer: path_particle_rope | Name: (null)
268 Designer: path_particle_rope | Name: (null)
269 Designer: path_particle_rope | Name: (null)
270 Designer: path_particle_rope | Name: (null)
271 Designer: path_particle_rope | Name: (null)
272 Designer: path_particle_rope | Name: (null)
273 Designer: path_particle_rope | Name: (null)
274 Designer: path_particle_rope | Name: (null)
275 Designer: path_particle_rope | Name: (null)
276 Designer: path_particle_rope | Name: (null)
277 Designer: path_particle_rope | Name: (null)
278 Designer: path_particle_rope | Name: (null)
279 Designer: path_particle_rope | Name: (null)
280 Designer: path_particle_rope | Name: (null)
281 Designer: path_particle_rope | Name: (null)
282 Designer: path_particle_rope | Name: (null)
283 Designer: path_particle_rope | Name: (null)
284 Designer: path_particle_rope | Name: (null)
285 Designer: path_particle_rope | Name: (null)
286 Designer: path_particle_rope | Name: (null)
287 Designer: path_particle_rope | Name: (null)
288 Designer: path_particle_rope | Name: (null)
289 Designer: path_particle_rope | Name: (null)
290 Designer: path_particle_rope | Name: (null)
291 Designer: light_omni2 | Name: (null)
292 Designer: light_omni2 | Name: (null)
293 Designer: light_rect | Name: (null)
294 Designer: light_rect | Name: (null)
295 Designer: light_omni2 | Name: (null)
296 Designer: light_rect | Name: (null)
297 Designer: light_rect | Name: (null)
298 Designer: light_rect | Name: (null)
299 Designer: light_rect | Name: (null)
300 Designer: light_rect | Name: (null)
301 Designer: light_rect | Name: (null)
302 Designer: light_rect | Name: (null)
303 Designer: light_rect | Name: (null)
304 Designer: light_rect | Name: (null)
305 Designer: light_rect | Name: (null)
306 Designer: light_rect | Name: (null)
307 Designer: light_rect | Name: (null)
308 Designer: light_rect | Name: (null)
309 Designer: light_omni2 | Name: (null)
310 Designer: light_rect | Name: (null)
311 Designer: light_omni2 | Name: (null)
312 Designer: light_rect | Name: (null)
313 Designer: light_rect | Name: (null)
314 Designer: light_omni2 | Name: (null)
315 Designer: light_rect | Name: (null)
316 Designer: light_rect | Name: (null)
317 Designer: light_rect | Name: (null)
318 Designer: light_rect | Name: (null)
319 Designer: light_rect | Name: (null)
320 Designer: light_rect | Name: (null)
321 Designer: light_environment | Name: (null)
322 Designer: light_rect | Name: (null)
323 Designer: light_rect | Name: (null)
324 Designer: worldent | Name: (null)
325 Designer: cs_player_controller | Name: (null)
326 Designer: team_select_counterterrorist | Name: (null)
327 Designer: team_select_counterterrorist | Name: (null)
328 Designer: team_intro_terrorist | Name: (null)
329 Designer: team_select_counterterrorist | Name: (null)
330 Designer: team_select_counterterrorist | Name: (null)
331 Designer: team_intro_terrorist | Name: (null)
332 Designer: c_cs_observer_for_precache | Name: (null)
333 Designer: team_select_counterterrorist | Name: (null)
334 Designer: team_select_terrorist | Name: (null)
335 Designer: team_intro_counterterrorist | Name: (null)
336 Designer: vote_controller | Name: (null)
337 Designer: (null) | Name: (null)
338 Designer: (null) | Name: (null)
339 Designer: (null) | Name: (null)
340 Designer: vote_controller | Name: (null)
341 Designer: cs_player_manager | Name: (null)
342 Designer: (null) | Name: (null)
343 Designer: (null) | Name: (null)
344 Designer: cs_gamerules | Name: (null)
345 Designer: vote_controller | Name: (null)
346 Designer: c_cs_player_for_precache | Name: (null)
347 Designer: team_select_terrorist | Name: (null)
348 Designer: (null) | Name: (null)
349 Designer: env_cubemap_fog | Name: (null)
350 Designer: env_sky | Name: dust_sky
351 Designer: env_sky | Name: default_sky
352 Designer: (null) | Name: (null)
353 Designer: (null) | Name: (null)
354 Designer: sky_camera | Name: (null)
355 Designer: env_sky | Name: dust_sky
356 Designer: team_select_terrorist | Name: (null)
357 Designer: team_select_terrorist | Name: (null)
358 Designer: team_select_counterterrorist | Name: (null)
359 Designer: team_select_terrorist | Name: (null)
360 Designer: team_select_terrorist | Name: (null)
361 Designer: team_select_terrorist | Name: (null)
362 Designer: team_intro_counterterrorist | Name: (null)
363 Designer: team_intro_counterterrorist | Name: (null)
364 Designer: team_intro_terrorist | Name: (null)
365 Designer: team_intro_terrorist | Name: (null)
366 Designer: team_intro_counterterrorist | Name: (null)
367 Designer: team_select_terrorist | Name: (null)
368 Designer: team_select_terrorist | Name: (null)
369 Designer: team_intro_terrorist | Name: (null)
370 Designer: team_select_counterterrorist | Name: (null)
371 Designer: team_select_counterterrorist | Name: (null)
372 Designer: team_select_terrorist | Name: (null)
373 Designer: team_select_counterterrorist | Name: (null)
374 Designer: team_intro_counterterrorist | Name: (null)
375 Designer: team_select_counterterrorist | Name: (null)

I fixed the CChicken issues:
go to cschemasystem.hpp and edit the second SchemaClassInfoData_t
class SchemaClassInfoData_t {
   public:
    char pad0[0x8];
    const char* m_name;
    char* m_module;
    short GetFieldsSize() {
        return *reinterpret_cast<short*>((uintptr_t)(this) + 0x1C);
    }
    SchemaClassFieldData_t* GetFields() {
        return *reinterpret_cast<SchemaClassFieldData_t**>((uintptr_t)(this) +
                                                           0x28);
    }
};

Edit centityinstance.hpp
class IHandleEntity
{
   public:
    virtual class SchemaClassInfoData_t* GetClassInformation(void) = 0;
};

class CEntityInstance : public IHandleEntity {
   public:
    SCHEMA_FIELD(m_pEntity, "CEntityInstance", "m_pEntity", CEntityIdentity*);
};

in render::ESP (or whereever) loop through ALL entities using GetHighestEntityIndex().
  for (int i = 1; i <= interfaces::pEntitySystem->GetHighestEntityIndex(); ++i) {
        C_BaseEntity* pEntity =
            interfaces::pEntitySystem->GetBaseEntity<C_BaseEntity>(i);
        if (pEntity == nullptr) continue;
        auto pClientClass =
            reinterpret_cast<IHandleEntity*>(pEntity)->GetClassInformation();
        if (pClientClass == nullptr || pClientClass->m_name == nullptr)
            continue;
         if (strcmp("C_Chicken", pClientClass->m_name) != 0) continue; //check for that entity class actually want (here "C_Chicken")

        //Do whatever you want with your pEntity (at this stage it is class of "C_Chicken")
     }

GetBoneLocationAndRotation and would like some help before I commit die.

What's your exception?
I got it to read from m_bonedata without crashing, but the coords still seem to be off.

What's your exception? I got it to read from m_bonedata without crashing, but the coords still seem to be off.

I guess the address is wrong but I tried both the 24.03 game release and latest from 31.03.
Got it from here and here.
`class CGameSceneNode {
public:
SCHEMA_FIELD(m_vecAbsOrigin, "CGameSceneNode", "m_vecAbsOrigin", Vector);
class CSkeletonInstance* GetSkeletonInstance();  // Virtual Index 8

};
class CSkeletonInstance /* "client" / : public CGameSceneNode / "client" */
{
public:
unsigned char pad_150[0x10];                               // 0x150 - 0x160
CModelState m_modelState;                                  // 0x160 - 0x390
bool m_bIsAnimationEnabled;                                // 0x390 - 0x391
bool m_bUseParentRenderBounds;                             // 0x391 - 0x392
bool m_bDisableSolidCollisionsForHierarchy;                // 0x392 - 0x393
unsigned char m_bDirtyMotionType : 1;                      // 0x393 - 0x394
unsigned char m_bIsGeneratingLatchedParentSpaceState : 1;  // 0x393 - 0x394
// CUtlStringToken m_materialGroup;                           // 0x394 -
// 0x398
unsigned char pad_398[0x4];   // 0x394 - 0x398
uint8_t m_nHitboxSet;         // 0x398 - 0x399
unsigned char pad_399[0x57];  // 0x399 - 0x3F0
};`
CSkeletonInstance* CGameSceneNode::GetSkeletonInstance() {     //*reinterpret_cast<CSkeletonInstance**>((uintptr_t)this + 0x300);     return CALL_VIRTUAL(CSkeletonInstance*, 8, this); }
`struct CBoneData {
Vector Location;
float Scale;
Quaternion Rotation;
};
class CModelState /* "client" /
{
public:
unsigned char pad_0[0x80];  // 0x0 - 0xA0
CBoneData m_boneArray;
unsigned char pad_88[0x18];
void* m_hModel;                         // 0xA0 - 0xA8
const char* m_ModelName;                // 0xA8 - 0xB0
unsigned char pad_B0[0x38];             // 0xB0 - 0xE8
bool m_bClientClothCreationSuppressed;  // 0xE8 - 0xE9
unsigned char pad_E9[0x97];             // 0xE9 - 0x180
uint64_t m_MeshGroupMask;               // 0x180 - 0x188
unsigned char pad_188[0x9A];            // 0x188 - 0x222
int8_t m_nIdealMotionType;              // 0x222 - 0x223
int8_t m_nForceLOD;                     // 0x223 - 0x224
int8_t m_nClothUpdateFlags;             // 0x224 - 0x225
unsigned char pad_225[0xB];             // 0x225 - 0x230
};                                          // size - 0x230
 pPawn->GetBoneLocationAndRotation(
pLocalPlayerController->m_iTeamNum() == 2 ? tr[i][0]
: ct[i][0],
To, rot1);
pPawn->GetBoneLocationAndRotation(
pLocalPlayerController->m_iTeamNum() == 2 ? tr[i][1]
: ct[i][1],
From, rot1);`

I am trying to implement the exact same function. It's either returning garbage or SkeletonInstance* is just nullptr.

ill close the issue since it has been solved and yes chickens do not have a designer name. i personally would have checked for their model names. and regarding the second issue CSkeletonInstance is CGameSceneNode(simply cast the scenenode pointer to a CSkeletonInstance). you can confirm it by putting the address into reclass.

authors: CosminGRG Zwiebelmettwurst bruhmoment21


text:
Update view.php métodos flush() e assets()

A função assets() gerava caminhos não relativos ao ambiente padrão. Esta atualização, corrige este problema, adicionado a constante BASE  e reordenando a atribuição dos $add_js e $add_css, para que os mesmos encontres as constantes já definidas.

Bruno, acredito que entendi a pegada: este método permite a injeção de CSS por cdn, correto? Então quando quiser inserir a baseUrl, apenas tenho que chamar pelas configurações, não?

repo: brunosantoshx/hxphp


text:
Fix x/y in web_keyboard for up and right

Ran into this while making my nodeboat :)

D'oh, thanks!

authors: bryan-m-hughes jfhbrook

repo: bryan-m-hughes/heya


text:
Code doesn't work in the CLI

System.NullReferenceException: Object reference not set to an instance of an object
at BingChat.BingChatConversation.g__GetAnswer|3_1(BingChatConversationResponse response)
at BingChat.BingChatConversation.<>c__DisplayClass3_0.g__OnMessageReceived|2(String text)
--- End of stack trace from previous location ---
at HelloWold.Program.ComposeAnswerAsync(String request)
at System.Threading.Tasks.Task.<>c.b__128_1(Object state)
at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
at System.Threading.Thread.StartCallback()

Seems to be a duplicate of #3. I just left a message there, so you can check it out.

authors: DmitryBorodiy bsdayo

repo: bsdayo/BingChat


text:
Feature: Remove lodash dependency

This closes https://github.com/bsdfzzzy/vue2-hammer/issues/8 by removing the lodash dependency and instead using Object.keys().length for the if check.
This will make using vue2-hammer much smaller without the lodash dependency. 😉

Cool. Thanks for the improvement.

authors: bsdfzzzy gerardo-rodriguez


text:
SBW does not recognize LN QR codes

I keep having issues with SBW (on Android) not being able to recognize LN QR codes.
E.g. https://www.plebpay.com/5a2935d1-9cf3-4710-8405-99cb42d48154 works well in Muun and Breez, but SBW does not recognize it.
I open the camera in the app with the "[  ]" button, point it at the QR, but then nothing happens.

QR code on that page is missing a so called quiet zone (that is, a white border space as described here: https://delivr.com/faq/1455/whats-with-the-white-border-around-the-qr-code).
As things stand QR on that page is unscannable in both SBW and Android default scanner app, and probably in many other implementations so this is not something for SBW to fix.

Just for posterity: The issue is actually different - the QR code is color inverted.

Following wallets can read the PlebPay QR: Muun, Bitcoinbeach, CashApp
Following wallets can't: WoS, Breez, Strike, SBW

authors: btcontract notnout

repo: btcontract/wallet


text:
Update to .Net6

After a lot of work recently, this seems to be stable enough to merge to the main branch
It has been updated to .Net/EF Core 6 with all the latest dependencies. Most standard things are working with the exception of the normal Jet limitations (Schemas, computed columns, sequences, no skip...take and some basic types that have no equivalent in Jet e.g. DateTimeOffset, TimeSpan, DateOnly, TimeOnly)
Tests: A large number of tests have been updated to make sure they compile and work.
Most tests now that do fail in general fall in one of 2 categories

Tests that test or include an unsupported feature. Will probably never work
Tests that generate a different SQL than what is expected.
2.1. Some of these are because EF Core itself has changed since the test was last looked at and the SQL is by default different
2.2. Others are because of certain functions have to be rewritten for Jet. Most common are the CASE...WHEN, CAST, COALESCE statements which have been rewritten using IIF statements

Will be continuing work on getting more tests working
@lauxjpn or @bubibubi Can we look at getting this merged

Any on update on this? Thank you!

Haven't heard anything from @bubibubi or @lauxjpn so not sure. Still going through each test to see if I can make it pass
@nicovil Already have a ef core 7 build set up. Busy going through the tests to see if there are any major differences in what is passing or failing

Haven't heard anything from @bubibubi or @lauxjpn so not sure. Still going through each test to see if I can make it pass
@nicovil Already have a ef core 7 build set up. Busy going through the tests to see if there are any major differences in what is passing or failing

Hi @ChrisJollyAU . I cloned a fresh copy of your net6 repo and migrated stuff to .net 7, there are some changes in some visitors that makes the existing code not to compile, however they're 4 or 5 source code files only that needs to be fixed. There are some deprecated methods issues too.

@nicovil try the ef7 branch then

Haven't heard anything from @bubibubi or @lauxjpn so not sure. Still going through each test to see if I can make it pass
@nicovil Already have a ef core 7 build set up. Busy going through the tests to see if there are any major differences in what is passing or failing

@ChrisJollyAU Oh :) I have also made a test .net 7 build of the subject codebase and I have run the tests:
EFCore.Jet.IntegrationTests:
     77 passed, 29 failed (106 - total)

EFCore.Jet.Tests:
      15 passed, None failed    (15 - total)

EFCore.Jet.Data.Tests:
      67 passed,  14 failed   (81 - total)

EFCore.Jet.FunctionalTests:
     4084 passed, 8296 failed, 146 skipped, 4057 not run  (16583 - total)

I missed your .Net7 branch, I will watch its progress now . In the case any help with the tests' fixes is needed I may try to contribute.
Thank you for your great work!

@bubibubi is there a reason that this PULL-Request is ignored?
Would be really cool to officially provide the .NET 6 release!
Btw: Thanks a lot to @ChrisJollyAU

@timecreators I'd love to merge it too. Would do it if I had the permissions. In the meantime, I'm just trying to get all the SQL for the tests up to date and outputting as expected. Then to try sort out any further errors

@bubibubi is there a reason that this PULL-Request is ignored?
Would be really cool to officially provide the .NET 6 release!
Btw: Thanks a lot to @ChrisJollyAU

So sorry about this... I'm working hard on another project so I can just follow your great work.

@timecreators I'd love to merge it too. Would do it if I had the permissions. In the meantime, I'm just trying to get all the SQL for the tests up to date and outputting as expected. Then to try sort out any further errors

@ChrisJollyAU you should be able to merge now.

@bubibubi Thanks. Going to look into merging it in the next couple of days. Also will have a look at making a nuget release if I have the permissions

For all those following, this has now been merged into the master branch

For all those following, this has now been merged into the master branch

@ChrisJollyAU Great work, thank you!
I have just used the new version on my box with .NET 7 and VS 2022. I have changed global.json to:
{
  "sdk": {
    "version": "7.0.100",
    "allowPrerelease": false,
    "rollForward": "latestFeature"
  }
}

and I have run all the tests. Here are the results:

EFCore.Jet.Data.Tests
  Tests in group: 81
  Total Duration: 39.3 sec
   Outcomes
       81 Passed

EFCore.Jet.FunctionalTests
   Tests in group: 9522
   Total Duration: 2.5 min
   Outcomes
      7129 Not Run
      1773 Passed
      615 Failed
      5 Skipped

EFCore.Jet.IntegrationTests
  Tests in group: 106
  Total Duration: 16.5 sec
  Outcomes
      79 Passed
      27 Failed

EFCore.Jet.Tests
  Tests in group: 15
  Total Duration: 21.5 sec
  Outcomes
     15 Passed

@ShamilS you would still be targeting ef core 6 not ef core 7.
Also, doesn't look like you are running most of the functionaltests. From your results most are shown as not run

@ShamilS you would still be targeting ef core 6 not ef core 7.

@ChrisJollyAU I intentionally did so - just to see how it will work. I do not have .NET 6 at all on my main development PC now.
I have rerun EFCore.Jet.FunctionalTests. Results are:
     Tests in group: 9522
     Total Duration: 6,4 min
      Outcomes
         5067 Passed
         4270 Failed
         185 Skipped

Do these results look similar to yours?
I have then used another box with .NET 6 SDK v. 6.0.306 - the results for

EFCore.Jet.Data.Tests
EFCore.Jet.IntegrationTests
EFCore.Jet.Tests

are the same as for .NET7.
For the EFCore.Jet.FunctionalTests there are many tests, which do not run at all when running all the tests first time from within VS2022 Test Explorer. But when running some of the individual groups of tests of EFCore.Jet.FunctionalTests project - they run OK.
Should dotnet CLI be used to run the tests to have all of them running in proper order? (VS2022 Test Explorer Runner seems to be trying to run the tests (from different test projects) in parallel.

@ShamilS I have the same as you, but for my FunctionalTests this is the result EFCore.Jet.FunctionalTests Tests in group: 9522  Total Duration: 9.1 min
Outcomes  5069 Passed  4268 Failed  185 Skipped

@ChrisJollyAU Great news! My I assume that your current version of the EntityFrameworkCore.Jet -> Net6 is also .NET7 ready?
According to the stats there are just two(?) tests, which worked for you and not worked for my .NET7 tests.
Now if I log the EFCore.Jet.FunctionalTests running for .NET7 in a file and you do similar logging for EFCore.Jet.FunctionalTests running for .NET6 then we can find what is the difference and you'll get an opportunity to have released both .NET6 and .NET7 versions of the EntityFrameworkCore.Jet.
I'm running the tests here using the following dotnet CLI command line:
  dotnet test {{FullPathToProjectFolder}}\EFCore.Jet.FunctionalTests.csproj  --consoleLoggerParameters:ErrorsOnly --logger:console >!EFCore.Jet.FunctionalTests.log

But when I run the functional tests by the above command line I'm getting the following total stats:
        Failed!  - Failed:   360, Passed:   815, Skipped:     1, Total:  1176, Duration: 2 m 1 s - EntityFrameworkCore.Jet.FunctionalTests.dll (net6.0)

IOW, quite a few tests do not run somehow at all. How should I change the dotnet CLI command line to have all/most of the tests running?
Is there an (easy built-in into dotnet CLI options) way to collect just the names of the failed tests' classes and methods?
AFAIS I can write a simple code to collect the failed methods' and their classes(?) by parsing log file search for the Error Message: keywords and collecting the previous and the following to these keywords log file lines:
....
  Failed Model19_1_1Run [53 ms]
    Error Message:
     Test method EntityFrameworkCore.Jet.IntegrationTests.Model19_1_1.Model19_1_1JetTest.Model19_1_1Run threw exception:
        System.InvalidOperationException: The value of 'ClassB.Id' is unknown when attempting to save changes. This is because the property is also part of a foreign key for which the principal entity in the relationship is not known.

...
   Failed OrderBy_Skip_Count [58 ms]
   Error Message:
   Test method EntityFrameworkCore.Jet.IntegrationTests.Model_MainTests.MainJetTests.OrderBy_Skip_Count threw exception:
        System.InvalidOperationException: Jet does not support skipping rows. Switch to client evaluation explicitly by inserting a call to either AsEnumerable(), AsAsyncEnumerable(), ToList(), or ToListAsync() if needed.

...
Thank you.
P.S. Here is my test environment -  it's a new laptop without any legacy .NET versions.
  .NET SDK:
   Version:   7.0.100
   Commit:    e12b7af219

  Runtime Environment:
   OS Name:     Windows
   OS Version:  10.0.22621
   OS Platform: Windows
   RID:         win10-x64
   Base Path:   C:\Program Files\dotnet\sdk\7.0.100\

  Host:
    Version:      7.0.0
    Architecture: x64
    Commit:       d099f075e4

  .NET SDKs installed:
    7.0.100 [C:\Program Files\dotnet\sdk]

  .NET runtimes installed:
    Microsoft.AspNetCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
    Microsoft.AspNetCore.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
    Microsoft.NETCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
    Microsoft.NETCore.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
    Microsoft.WindowsDesktop.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
    Microsoft.WindowsDesktop.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

  Other architectures found:
    x86   [C:\Program Files (x86)\dotnet]
      registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

  Environment variables:
    Not set

  global.json file:
    Not found

  Learn more:
    https://aka.ms/dotnet/info

  Download .NET:
    https://aka.ms/dotnet/download

@ShamilS Just changing the global.json is just changing the SDK used to compile it with. It doesn't change the target framework and any other references. In one of your results you can still see the (net6.0) at the end.
There's not really a .Net 7 specific version out that will be out. EFCore.Jet is really tied to the related version of Entity Framework Core. So far EFCore and .Net (Core) have been linked (as in the version of EF Core can only be used with the same version of .Net Core).
This has changed with EF Core 7 as instead of it being only for .Net 7, you can use it on both .Net 6 and .Net 7. That's why #132 refers to EF Core 7 rather than .Net 7

@ShamilS Just changing the global.json is just changing the SDK used to compile it with. It doesn't change the target framework and any other references. In one of your results you can still see the (net6.0) at the end.

@ChrisJollyAU Thank you for your explanations. Still the question is why there are two more successful tests on your side when running tests from withing VS2022 and what are these failed here two tests?
What should be the dotnet CLI command line to run all the tests of the EFCore.Jet.FunctionalTests.csproj project?
If you don't have an out-of-hand answer on the latter question - just ignore both. If you do have - please post here the dotnet CLI command.

authors: ChrisJollyAU ShamilS bubibubi j-fdion nicovil timecreators


text:
bucket4j-hazelcast:7.6.0 UAT is getting failed while using mvn test

Hi Team,
I am making the build with UAT enabled of submodule bucket4j-hazelcast:7.6.0. I am using the below version.
Maven command - mvn test
Maven version I am trying - 3.3.1 and above.
JDK version- 8 , 11 and 17
Let me know which java version , Maven version and test command it will work?
I have also included log. Error we are getting.
build-bucket4j-hazelcast-7.6.0-2024-02-28-06-09-59-242-6273909608.txt
"[14 15:47:08.368] | [INFO] Running io.github.bucket4j.BlockingStrategyTest
[14 15:47:10.402] | [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.029 s - in io.github.bucket4j.BlockingStrategyTest
[14 15:47:10.403] | [INFO] Running io.github.bucket4j.util.concurrent.BatchHelperSpecification
[14 15:47:10.630] | [ERROR] Tests run: 8, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.222 s <<< FAILURE! - in io.github.bucket4j.util.concurrent.BatchHelperSpecification
[14 15:47:10.630] | [ERROR] test success async case(io.github.bucket4j.util.concurrent.BatchHelperSpecification)  Time elapsed: 0.004 s  <<< ERROR!
[14 15:47:10.630] | java.lang.reflect.InaccessibleObjectException: Unable to make java.util.concurrent.CompletableFuture(java.lang.Object) accessible: module java.base does not "opens java.util.concurrent" to unnamed module @6f29c911
[14 15:47:10.630] | at io.github.bucket4j.util.concurrent.BatchHelperSpecification.test success async case(BatchHelperSpecification.groovy:27)"
Please help.

What is UAT?

Should be moved to discussions.

I tried with JDK 8 , 11 and 17 . Do u want specific version? .
I tried with mvn test command and it got failed.
I want to run test cases of it.

What is UAT?

I tried with JDK 8 , 11 and 17 . Do u want specific version?

Sorry, but I can not believe in that. Please double check prior writting.  JPMS was even not exists in Java 8. Tests can not fail on Java8, because JPMS was introduced in Java 9.
As I can see from attachement, only groovy based tests were failed. And only bucket4j-core module was run, another submodules was skipped

So I totally do not understand why issue is named bucket4j-hazelcast:7.6.0 UAT is getting failed while using mvn test, there is no problems with Hazelcast, build even not reached this module.
Anyway, errors in your logs are self-describable, each fail is caused by java.lang.reflect.InaccessibleObjectException,    for example

That means that you use Java 17(or higher) where reflection is prohibited for unnamed modules. So you have to use Java 11 to make tests passed.

If you want to stay at java 17 then you need to modify configuration of maven-surefire-plugin there https://github.com/bucket4j/bucket4j/blob/master/bucket4j-parent/pom.xml#L162 by adding following lines:
<argLine>--add-opens java.base/java.time=ALL-UNNAMED</argLine>
<argLine>--add-opens java.base/java.math=ALL-UNNAMED</argLine>
<argLine>--add-opens java.base/java.lang=ALL-UNNAMED</argLine>
<argLine>--add-opens java.base/java.lang.reflect=ALL-UNNAMED</argLine>

But success is not guaranteed because, build was never tests aginst java17

Rechecked , I am using java 8 and tried maven version apache-maven-3.8.5 but UT is getting failed.

Rechecked , I am using java 8 and tried maven version apache-maven-3.8.5 but UT is getting failed.

Check it again,  InaccessibleObjectException introduced since Java 9, it can not be thrown from Java 8.

If you return yet another time without clear context, I will ban you permamently.

Rechecked , I am using java 8 and tried maven version apache-maven-3.8.5 but UT is getting failed.

Check it again, InaccessibleObjectException introduced since Java 9, it can not be thrown from Java 8.

If you return yet another time without clear context, I will ban you permamently.

Sure . Will check and confirm.

Tried but still got failing.

Checked and confirmed. and Tried on jdk 8 but still got failed.

This is the last warning prior permament ban. With wich errors build failed? Where is build log? Where is evidance in build log, that build was executed on Java 8?

At last i also got UT failure with OpenJDK18 and Maven 3.9.6

I also got UT failure with OpenJDK17,8 and Maven 3.9.6

I also got UT failure with OpenJDK17,8 and Maven 3.9.6

@sourabhmagdum45 please do not give up. Try 19, 20, 21 and do not forget about 9,10,11,12,13,14,15,16,17.
It will be extremelly productive for spending time to build project that is addressed for 1.8 on such versions.  Also I will be glad to know who also employed at your company. Let another colleagues do the same and answer to this thread.

Anyway, I am glad to meat with everybody in this thread, and I want to offer to play game that is very popular in Russia. Game is called Find black cat inside black room. The cat is java.lang.reflect.InaccessibleObjectException. The room is Openjdk 8 Repository. I have a few T-shirt with Bucket4j logo. Guy who first find the cat will win a prize, I will send it by email. I had tried to find a cat, but I failed.
Guys, t-shirt is awaiting you


text:
[DIP] replace C-style variadic function with std::vector

The checkDIPCommonTypes function uses C-style variadic arguments only for passing variadic numbers of the same type arguments, which should be avoided in C++. It is recommended to replace this usage with std::initializer_list or std::vector.
This PR also fixes the compilation failure in clang++, which will give a warning (as an error) for non-POD type Value in va_arg.

Can you please specify the clang version which leads to the mentioned failure

I was able to reproduce the error.
(Ref : https://github.com/meshtag/buddy-mlir/actions/runs/3439561667/jobs/5737001087#step:6:4405 )

Can you please specify the clang version which leads to the mentioned failure

Sorry for the late reply, I use clang 14 on my machine. Here is the output of clang -v:
clang version 14.0.5 (Fedora 14.0.5-1.fc36)
Target: x86_64-redhat-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-redhat-linux/12
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-redhat-linux/12
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64

These modifications seem to work on macos-latest configuration.
(Ref : https://github.com/meshtag/buddy-mlir/actions/runs/3442213404/jobs/5742558798 )

repo: buddy-compiler/buddy-mlir


text:
CentOps: Implement API Keys functionality

As a CentOps Architect
I want the /admin endpoints of the CentOps API to require use of admin API keys
So that only admins can call the /admin endpoints
Acceptance Criteria

Should handle all /admin endpoints in the following way:

[ ] Should return 400 BadRequest if X-Api-Key header is missing
[ ] Should return 401 Unauthorized if X-Api-Key header contains non-admin key

Should handle the public GET /participants and /institutions endpoints in the following way:

[ ] Should return 401 Unauthorized if X-Api-Key is revoked

Should handle PUT /participants and /institutions in the following way:

[ ] Should return 401 Unauthorized if X-Api-Key is revoked
[ ] Should fetch the entity id associated with the API Key and store it in the request context for use by the data access layer.

I will close this issue without a merge into main. Work for this issue will be in PR #58 and merge conflicts and PR comments will be address in the new issue.

repo: buerokratt/CentOps


text:
Image Rotate 180 angle

Hi, when there are any images uploaded from the photo gallery and try to preview using BFRImageViewController it rotates the image by 180 degrees angle

e

Could you share some code on how you're presenting it? I'm not seeing that on my end.

BFRImageViewController *imageVC = [[BFRImageViewController alloc] initWithImageSource:@[media_url]];
imageVC.transitioningDelegate = self;
[self presentViewController:imageVC animated:YES completion:nil];

The image probably has an EXIF tag that says "this image was taken upside down, rotate it for viewing", while this viewer does not support those tags

repo: bufferapp/buffer-ios-image-viewer


text:
Appcenter Post Build Script to upload source maps on build

I have this post-build script that runs after every appcenter build, but it doesn't upload source maps to the bugsnag API and fails with an error:  curl: (26) Failed to open/read local data from file/application
I do not any experience with shell scripting, please help with the script (pasted below), or put me in the right direction.
appcenter-post-build.sh
#!/usr/bin/env bash

# Post-build script section in log: `##[section]Starting: Post Build Script`

echo "**************** POST-BUILD SCRIPT INIT ******************"

# Generate sourcemaps for Bugsnag
echo "Installing react-native-cli..."
yarn add react-native-cli
echo "Installation successful..."

## Create sourcemaps and bundle
echo "Generating Source Maps..."
react-native bundle \
--platform android \
--dev false \
--entry-file index.js \
--bundle-output android-release.bundle \
--sourcemap-output android-release.bundle.map
echo "Source Maps Generated..."

## Upload sourcemaps to Bugsnag
echo "Uploading Source Maps..."
curl https://upload.bugsnag.com/react-native-source-map \
   -F apiKey=4..abcxyz..f \
   -F appVersion=$APPCENTER_BUILD_ID \
   -F dev=false \
   -F platform=android \
   -F sourceMap=@android-release.bundle.map \
   -F bundle=@android-release.bundle \
   -F projectRoot=`pwd`
echo "Source Maps Uploaded..."

echo "**************** POST-BUILD SCRIPT DONE ******************"

Script output in the logs from build:
[command]/bin/bash /Users/vsts/agent/2.155.1/work/1/s/appcenter-post-build.sh
**************** POST-BUILD SCRIPT INIT ******************
Installing react-native-cli...
yarn add v1.17.3
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " > react-apollo@2.5.8" has unmet peer dependency "react-dom@^15.0.0 || ^16.0.0".
warning "react-navigation > react-navigation-drawer@1.2.1" has unmet peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning "react-navigation > react-navigation-stack@1.4.0" has unmet peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning "react-navigation > react-navigation-tabs@1.1.4" has unmet peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning "react-navigation-material-bottom-tabs > react-navigation-tabs@1.0.0" has unmet peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning "@react-native-community/eslint-config > @typescript-eslint/eslint-plugin@1.13.0" has incorrect peer dependency "eslint@^5.0.0".
warning "@react-native-community/eslint-config > @typescript-eslint/parser@1.13.0" has incorrect peer dependency "eslint@^5.0.0".
warning "@react-native-community/eslint-config > eslint-plugin-react@7.12.4" has incorrect peer dependency "eslint@^3.0.0 || ^4.0.0 || ^5.0.0".
warning "@react-native-community/eslint-config > eslint-plugin-react-native@3.6.0" has incorrect peer dependency "eslint@^3.17.0 || ^4 || ^5".
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 15 new dependencies.
info Direct dependencies
└─ react-native-cli@2.0.1
info All dependencies
├─ async@0.2.10
├─ colors@0.6.2
├─ cycle@1.0.3
├─ deep-equal@1.0.1
├─ eyes@0.1.8
├─ i@0.3.6
├─ ncp@0.4.2
├─ pkginfo@0.4.1
├─ prompt@0.2.14
├─ react-native-cli@2.0.1
├─ read@1.0.7
├─ revalidator@0.1.8
├─ stack-trace@0.0.10
├─ utile@0.2.1
└─ winston@0.8.3
Done in 7.78s.
Installation successful...
Generating Source Maps...
/Users/vsts/agent/2.155.1/work/1/s/appcenter-post-build.sh: line 14: react-native: command not found
Source Maps Generated...
Uploading Source Maps...
curl: (26) Failed to open/read local data from file/application
Source Maps Uploaded...
**************** POST-BUILD SCRIPT DONE ******************
##[section]Finishing: Post Build Script

P.S. I had asked for support on email, but it has been 3 days already, and I'm really stuck with this, that's why posting it here. Thanks!

appcenter-post-build.sh: line 14: react-native: command not found

This looks like you do not have react-native on your PATH and so the source maps are not generated. The error you see is the Bugsnag tool not being able to find them for upload.
Please check the React Native installation guides and support. You need to check your npm/yarn setup to ensure it gets installed globally or added to your path manually.

authors: devautor tomlongridge

repo: bugsnag/bugsnag-react-native


text:
handle the webpack 5 default devtoolModuleFilenameTemplate format

Goal
Fix broken github links in stack frames in the dashboard by taking into account that webpack inserts a so-called namespace into source paths in the source map file. The format, at least for webpack 5 is webpack://[namespace]/[resource-path]?[loaders].
Design
Simple whilst maintaining backward compatibility.
This handles the most common use-cases but would not work for cases where output.devtoolModuleFilenameTemplate is customized. (https://webpack.js.org/configuration/output/#outputdevtoolmodulefilenametemplate)
Changeset

Added unit test coverage for the case where [namespace] is not an empty string, which is when the project has a package.json file.
Changed the regexps to handle the webpack://[namespace]/[resource-path]?[loaders] format
Fixed the e2e tests

Testing

Add a new test project fixture, webpack-2 with the only difference being that this project has a package.json file, which is sufficient to cause the sources in the built output to include the pkg.name, e.g. "webpack://this-package-name-is-used-in-the-source-paths/./lib/a.js"
Corrected the expectations in the e2e tests
Depended on this PR in a dashboard-js test branch and deployed to staging and verified the Github links are now working

I've tested the latest changes against the dashboard and with/without nosources, all working as expected.

repo: bugsnag/bugsnag-source-maps


text:
feat(rust): support progress_bar in command notifications

It also fixes the messages formatting generated when creating the default identity and vault.

For some reason, the local bats tests are hanging now in this PR. I'll check it out

repo: build-trust/ockam