text:
chore: fix typos

Type of changes

[ ] Bug fix
[ ] New feature
[x] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[ ] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[ ] I accept that @willmcgugan may be pedantic in the code review.

Description
Few more typos.

thanks

authors: aaronst willmcgugan

repo: Textualize/rich


text:
🛑 node3.th7bo.com is down

In 3996c98, node3.th7bo.com (node3.th7bo.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: node3.th7bo.com is back up in a11ebba after 4 hours, 54 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Add gitignore

Add .gitignore for ignorning some config, editor, system files mentioned in issue 21

Add a subclassed bot example with discord.py too
path : python/discord.py/subclassed-bot

source: gharchive/pull-request

repo: The-Coding-Academy/Community-Bin


text:
[Idea, Q&A] Add issue regression tests

Prompt
Currently only perfomance benchmarks are done and no compatability/feature tests are done.
For example

if you try to run a design wtih FP_DEF_TEMPLATE specified, it crashes, see: https://github.com/The-OpenROAD-Project/OpenLane/issues/869.

There is also other issues caused by a lot of reworks in the python scripts like defutil.py.

There is cases where small die areas crash the flow (see: https://github.com/The-OpenROAD-Project/OpenLane/issues/879)

Hi-Z inouts are connected to tie-low cell and it's impossible to disconnect it.

Specifying USE ANALOG in LEF should force the router to ignore the pin, however the flow crashes stating that USE ANALOG is an invalid.

Placing an LEF cell which contains met3 causes the flow to place met3 blockages over the macro (I assume at least), which in turn causes some met3 pins to be inaccessible.

This is just a couple I noticed, probably there is more.
Proposal
My proposal is to add a set of tests that cover issues that happened in the past. This will help to reduce the gap between 100% coverage of all options and current state of OpenLane.
I am open to discussion, and if OpenLane devs arent against it, I can even implement it with integration with current CI flow.

For example: Specifying the def currently causes the flow to not crash (with applied relevant fixes to above mentioned issues), however the floorplan's pin and macro locations dont match the specified def. This was not the case with v0.23.
If I added my def_test as a part of bug regression testing, this would allow me to create a test script which compares the flows reports and defs/gds to what should have been in the output, but only checking for the relevant parts, like pin/macro locations.
Obviously this creates a little more work, but this will reduce the amount of issues at the end of the day and make OpenLane more production-ready.

100% agreed. If you can get something implemented, please, by all means.

Let me know what you think about my idea of implementing this.
Modify flow.tcl to source checks/post_run_hooks.tcl which will do the checking. This will allow to add a just any forms of checks in the flow, without introducing too much new code.
Then for issues, we will have minimal designs which reproduce this issues and checks can be added to checks/post_run_hooks.tcl that make sure that issue that we had with the design is didn't comeback as result of code changes.
For example: To test issue #869 I would have run with FP_DEF_TEMPLATE specified. The run will be called def_test and will contain post_run_hooks.tcl which will compare pins from a known-to-be-good def to pin locations from final def file. For other issues related to FP_DEF_TEMPLATE other tests might be introduced to post_run_hooks.tcl, while not adding new designs.
For issues that require a design like Hi-Z inout issue, a designs/issue_878_disconnected_outputs_shouldnt_be_tied_low and will contain the hooks + short readme explaining the issue and giving links and other info.

Sober, but perhaps hide this feature behind a flag. For security purposes. The config.tcl is already enough a security headache as is.

Following does not generate an stdout, coudl you help me debug it?
exec $::env(OPENROAD_BIN) -python $::env(DESIGN_DIR)/hooks/post_run.py

Currently I don't know how to fill the regression_tests csvs, so my def_test design will be there and will not crash the flow.

Thank you for the issue and thank you for contributing. Most users don't get this far. :)

authors: armleo donn

repo: The-OpenROAD-Project/OpenLane


text:
read_power_activities SEGFAULT

Describe the bug

untar crash.tar.gz
./run-me-mock-array-asap7-base.sh

Crash:
$ ./run-me-mock-array-asap7-base.sh
OpenROAD v2.0-14511-gedb4e7e37
Features included (+) or not (-): +Charts +GPU +GUI +Python
This program is licensed under the BSD-3 license. See the LICENSE file for details.
Components of this program may be licensed under more restrictive licenses which must be honored.
[INFO ODB-0227] LEF file: /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lef/asap7_tech_1x_201209.lef, created 24 layers, 9 vias
[INFO ODB-0227] LEF file: /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lef/asap7sc7p5t_28_R_1x_220121a.lef, created 212 library cells
Signal 11 received
Stack trace:
 0# 0x00005F8D92694553 in openroad
 1# 0x00007B574E042990 in /lib/x86_64-linux-gnu/libc.so.6
 2# odb::dbHashTable<odb::_dbInst>::find(char const*) in openroad
 3# sta::dbSdcNetwork::findInstance(char const*) const in openroad
 4# sta::dbSdcNetwork::findPin(char const*) const in openroad
 5# sta::ReadVcdActivities::setVarActivity(char const*, std::vector<sta::VcdValue, std::allocator<sta::VcdValue> > const&, int) in openroad
[deleted]

Expected Behavior
Error/warning messages
Environment
OpenROAD v2.0-14511-gedb4e7e37

To Reproduce
See above
Relevant log output
No response
Screenshots
No response
Additional Context
No response

While we should protect against the crash, you should note that you haven't loaded any design (eg .def or .v):
source $::env(SCRIPTS_DIR)/read_liberty.tcl
read_lef $::env(TECH_LEF)
read_lef $::env(SC_LEF)

read_power_activities -scope TOP/MockArrayTestbench/postSynthesis -vcd designs/src/mock-array/MockArrayTestbench.vcd

Thanks! Yes I am aware of the problem in the script; I moved up the read_power_activities to verify that the file was found because the subsequent commands take a long time...

Had things worked properly we would have errored with no design before even trying to load the file.

I see.
Practically, this is just a small nit to convert a segfault to an actionable error...

Yes

authors: maliberty oharboe

repo: The-OpenROAD-Project/OpenROAD


text:
Implement the TokenVault

this change will remove the ERC20Helper.sol from this project.
the Final interface will be used:
    function deposit(address from, uint _amount) external;
    function withdraw(address to, uint _amount) external;

current version
https://github.com/The-Poolz/VaultFactory/blob/master/contracts/IVault.sol
this will be called in 2 cases:

Creation - in the creation, instead of calling the Transfer Directly, will be called the function from the NFT contract
Withdraw - this is called from the NFT, it needs to change the states in the provider, and get the amount, if it > 0 , call the provider

to manage this, the NFT will need 2 new states:

id to TokenVault - can be joined with the Id to provider
token to TokenVault - to know what value to give to a new token

and will need a function that will call the https://github.com/The-Poolz/VaultFactory/blob/c5d421e3878bdb56007877c068a88575787a09ee/contracts/IVaultFactory.sol#L7
CreateNewVault
and register to token to tokenVault

on #32 there is exmaple

repo: The-Poolz/LockDealNFT


text:
[FEATURE] Upgrade to C++ 23 Standard

Detailed description
I propose upgrading our project's C++ version from C++11 to C++23.
Context

Improved Language Features: C++23 includes modern features like improved constexpr, modules, and enhanced ranges, which can simplify code.
Better Performance: Features like coroutines and more efficient constexpr usage can lead to faster and more readable code.
Future Proofing: Aligning with the latest standard ensures compatibility with modern libraries and keeps the project maintainable.

Possible implementation
No response
Additional information
No response

https://github.com/TheAlgorithms/C-Plus-Plus/pull/2746
You can see my proposal for 17 here.
if we update to 23 right now, we will lose arm compatibility
esp has no such issues though

closing since no comment from author.

repo: TheAlgorithms/C-Plus-Plus


text:
Enable cache sweeping in CI

Addresses part of #212.
I recently merged a feature into Leafwing-Studios/cargo-cache v2.3.0 that automatically deletes unused build artifacts before creating a new cache, to prevent cache sizes from snowballing.
It's disabled by default due to backward compatibility reasons, so this PR enables it. Cache sweeping should keep cache sizes small and workflow runs fast.
(As an side, should a cache be used at all in the release build? Caching prevents builds from being reproducible, and can introduce the occasional issue when building.)

I made a temporary commit (7188e2c623e4b4fc97cd9abad3d55c3ae364544d) that updates some dependencies, which will make some build artifacts stale. After looking at the run, it removed 365 MiB on the Clippy and Docs jobs and removed a whopping 3.68 GiB on the Tests job.
These savings will only occur when a fallback key is used (typically when Cargo.lock or Cargo.toml is changed), but are quite significant. The only downside is an ~2 second overhead in the cache action from downloading cargo-sweep.

That's really impressive :D Good work!


text:
🛑 BentleyHensel.com is down

In 9e9c025, BentleyHensel.com (https://bentleyhensel.com/) was down:

HTTP code: 530
Response time: 86 ms

Resolved: BentleyHensel.com is back up in 8f70a26.

repo: TheBoatyMcBoatFace/upptime


text:
Launchbuddy blocked as trojan

Hi, windows defender now consider launchbuddy as trojan, with code "Trojan:Script/Oneeva.A!ml"

Closing issue as it references an old version:
Mainissue:
https://github.com/TheCheatsrichter/Gw2_Launchbuddy/issues/363

authors: TheCheatsrichter sciandapol


text:
Call the layer's OnDetach before deleting it.

Resolves issue #47
the leaks where discovered in #125

I would just like to point out that this does not resolve the issue alone. Only with the other 3 PRs of yours is the issue resolved.

How do i point that out?

I suggest you remove the closing keywords and we make a task list on the issue itself. I have suggested it there.

OK, i'll edit my comments.

authors: IshoAntar Puddlestomper

repo: TheCherno/Hazel


text:
Caching .editorconfig file(s)

Hello, I am currently an employee at Microsoft. We would like to use this library for a large project; however, we would like to have a caching layer to not have to parse the .editorconfig file(s) every time we are using them. Is this something you would entertain as an open-source contribution?

+1 we have a linting application that needs to run over hundreds to thousands of files while the configs won't change. To speed this up caching read editor-configs in memory would be preferable. I think we could do this in a way that keeps the existing API intact and adds opt-in caching :).

That's fantastic! We probably won't start on this right away as it will be an optimization but I expect to want to it soon, we will keep you posted and can post a design proposal to this issue.


text:
Error when selecting an NC program after running Color Holes

If I select an NC program in a file where Color Holes has been used, I get the following error popup:
Failed: Traceback (most recent call last):   File "E:/Organized Things/Work Stuff/Fusion Addins/Color-Holes-for-Fusion360-main/Color Holes.py", line 86, in notify     if len(sels) == 1 and sels[0].entity.objectType == "adsk::fusion::BRepFace":   File "C:\Users/npola/AppData/Local/Autodesk/webdeploy/pre-production/19107935ce2ad08720646cb4a31efe37d8a5f41b/Api/Python/packages\adsk\core.py", line 14821, in _get_entity     return _core.Selection__get_entity(self) RuntimeError: 3 : It is an unknown type of CAM object.

I can't really do anything about this until they fix/improve some parts of the Fusion API, I made a post on the forums about it on the API forum:
https://forums.autodesk.com/t5/fusion-360-api-and-scripts/selection-object-entity-fails-with-runtimeerror-3-when-a-setups/td-p/11088871

authors: TheEppicJR npolanosky


text:
Determine core module dependencies

Current list:

Plutonium (lmao)
DAE
Midi QoL
DFred's Convenient Effects
times-up

Item Macro is technically not needed since its data is stored in flags regardless, and other modules can access it. Details on this and 'ecosystem' modules like about-time can be exposed in the README.
'Rarely used' modules such as Active Auras and Better Curses are handled on a per-item basis, but they can still be listed in the README.
If there's any more to be made, now's the time to say it!

ItemMacro

Active Auras is another module commonly used ...

ItemMacro

We don't actually need ItemMacro as a dependency; Midi-QoL can execute the macro whether or not the module is enabled. The only reason to have the module enabled is to read/edit the macro... which users probably shouldn't be doing. So, ItemMacro isn't actually a module dependency, it's just a secret tool we use 😏

Active Auras

In the data there's a required array for each item, which lists any additional modules that are required to run the automation. Active Auras was basically the reason for this: yes, it's hugely useful when it's needed, but there is probably several cases where you'd never need it (e.g. my campaign right now!). So, no need for the computational overhead.
This issue is basically to list the module dependencies we will force everyone to activate in all cases. Honestly, I feel like it's 100% complete now, but I'd like to confirm before forgetting...

Do we need Advanced Macros? I can't remember if that's a dependency of anything else, but I feel it's important for our Item Macro wrangling.

Do we need Advanced Macros?

No.

authors: Spappz jbowensii

repo: TheGiddyLimit/plutonium-addon-data


text:
Контроль обновлений

Что если перенаправлять запрос последней версии приложения обновления на сторонний (напр, отслеживать с помощью репозитория на github)?
Сейчас сложно понять обновился ли сам мод (+это уведомление об обновлении), чтобы обновляться на новую версию приложения, не проверяя его страницу релизов - а так можно просто не пускать ему последнее обновление. Когда модификация обновится - обновить в репозитории и дать ему скачать версию с официальных серверов + обновить мод заодно, т.е. только перехватывать только проверку.

Во первых авто обновление мода уже есть в моде. Проблема в подходе описанном вами в том что если приложение обновляется, то мод автоматически после обновления не сможет поставиться. Для обновления мода между версиями приложения нужно создать отдельную программу которая будет независимо следить за обновлением приложения, чтобы по его окончанию установить, поверх новой версии приложения, модификацию.
Я если честно не хотел бы делать такое. Ибо количество точек отказа сильно возрастает. У меня в планах было переработать авто обновления, однако пока что реализовать их к меня не получилось.

Надо бы кстати поправить этот баг наконец то...

authors: TheKing-OfTime kittaro

repo: TheKing-OfTime/YandexMusicModClient


text:
🛑 Vaultwarden is down

In 9544da9, Vaultwarden (https://vaultwarden.sny.sh) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Vaultwarden is back up in 874a6bc after 14 minutes.

repo: TheLastZombie/upptime


text:
🛑 Faircamp is down

In 58e3fe8, Faircamp (https://faircamp.sny.sh) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Faircamp is back up in e14e05e after 58 minutes.


text:
Korean translation(Fix)

Thank you for signing up for the Korean translation.
But, We've made a few changes. Please update to the next version. Thank you.
https://github.com/TheMysticSword/MysticsItems/issues/286

Done! Sorry that it took this long!

repo: TheMysticSword/MysticsItems


text:
RareObjectMapper

An ObjectMapper simply maps between two similar objects - if the fields are all the same between two reflected objects it should be able to assign one to the other in a single statement without mentioning any fields explicitly and without any assignment overloads.
If field names differ but the types do not, it should be trivially easy to define a mapping between said fields.
If a function is needed to map between two objects it should be easy to provide one, and take advantage (or disable) automatic mapping between fields with the same name/type,

Part of the motivation with object mapper is to be able to define an object mapping, and then other reflection extensions like RareJson can automatically take advantage of a mapping.
Say you have a type which due to being from a 3rd party library or for security concerns or whatnot cannot be reflected directly; if you had such a type annotated with NOTE(MyType, Json::MappedBy), then to serialize/deserialize you need only define how to programmatically transform to/from MyType/MyProxyType - you don't need to make a json reader/writer customization which would need to deal with the intricacies of JSON.
If the transformation between two such types is trivial (meaning all the fields are public and of the same name/type), then I think it best that the user use (and RareCpp support) reflection proxies which enable constructs to work on a class which does not contain the REFLECT macro directly, e.g.
struct UnownedObject
{
    int a;
    int b;
};

template <> struct Reflect::Proxy<UnownedObject> : public UnownedObject
{
    REFLECT(Reflect::Proxy<UnownedObject>, a, b)
};

Only "direct" mappings should be done by default (that is, assignable types of the same name in both classes), auto-mapping to getters/setters/constructors can be done, or even preferred over direct mappings, if set as such via annotations in the reflected class or proxy...
Reason being that C++ has no widespread concept of a "bean" the fact that a "getX" or "setX" method exists in a class is a very weak hint that there's actually a variable called "x" in both objects which said methods are appropriate for getting or setting; and even if they do get or set a variable called "x" there's no telling whether these should only be done as part of a sequence of events, whether some ownership changes, or some destructive move occurs.
While some of these risks are shared by auto-mapping raw fields users will expect these fields to be automatically assigned to each other by the mapper where compatible by the default behavior (which will of course be overridable) - whereas I'm sure invocation of auto-detected methods will occasionally surprise - if instead client code must put a "Bean" annotation on the class/proxy, then they're being explicit that they've setup their getters and setters (or that the proxied class has setup getters and setters) in a manner appropriate for automatic use.

In addition to mapping between reflected objects... containers of primitives, reflected objects, and assignables should also be auto-mappable where compatible
anyiterable<T> <--> anyiterable<T>
anymap<K,T> <--> anymap<K,T>
anymap<K,T> <--> anyiterable<pair<K,T>>
anymap<K,T> <--> anyiterable<tuple<K,T>>

Special care needs to be given to unique_ptrs, they could be destructively moved, but that's not necessarily intuitive, probably best is similar to what was done for json: set null if null in source, assign value if already allocated, allocate and assign value otherwise.

Something I neglected to take seriously early: assignment operators and constructors taking the "from" value as an argument and assigning/building the "to" value should be auto-detected and used to the extent possible; I think this may result in a lot of rework to the object mapper as when available there's no reason the user should have to add another method to the object mapper namespace to do the mapping; these should just be picked up and used.
Another point I've neglected is that adding mappings in the way I'm currently doing them (a full specialization of a function in the object mapper namespace) is poor in an organizational sense - it could force code for a particular object to be located very far away from the object. Using SFINAE I could detect whether particular method names were added to an object and use those for mappings (for cases where assignment operators/constructors do not suffice). As assignment operators/constructors/methods within the objects themselves would most often be preferable having such options would make it unnecessary to use function full-specialization (which is not reliably detectable in the library and has serious limitations to what you can template) and preferable to partial template specialization on a struct (which is reliably detectable in the library code and allows for incredibly flexible templates, especially when done in headers).
Before I go off coding neglecting yet another point I'm going to research whether there's some reasonably standard conversion methodology I'm missing and could take advantage of besides assignment operators/constructors/library specific methods.

Something I neglected to take seriously early: assignment operators and constructors taking the "from" value as an argument and assigning/building the "to" value should be auto-detected and used to the extent possible; I think this may result in a lot of rework to the object mapper as when available there's no reason the user should have to add another method to the object mapper namespace to do the mapping; these should just be picked up and used.
Another point I've neglected is that adding mappings in the way I'm currently doing them (a full specialization of a function in the object mapper namespace) is poor in an organizational sense - it could force code for a particular object to be located very far away from the object. Using SFINAE I could detect whether particular method names were added to an object and use those for mappings (for cases where assignment operators/constructors do not suffice). As assignment operators/constructors/methods within the objects themselves would most often be preferable having such options would make it unnecessary to use function full-specialization (which is not reliably detectable in the library and has serious limitations to what you can template) and preferable to partial template specialization on a struct (which is reliably detectable in the library code and allows for incredibly flexible templates, especially when done in headers).
Before I go off coding neglecting yet another point I'm going to research whether there's some reasonably standard conversion methodology I'm missing and could take advantage of besides assignment operators/constructors/library specific methods.

Something I neglected to take seriously early: assignment operators and constructors taking the "from" value as an argument and assigning/building the "to" value should be auto-detected and used to the extent possible; I think this may result in a lot of rework to the object mapper as when available there's no reason the user should have to add another method to the object mapper namespace to do the mapping; these should just be picked up and used.
Another point I've neglected is that adding mappings in the way I'm currently doing them (a full specialization of a function in the object mapper namespace) is poor in an organizational sense - it could force code for a particular object to be located very far away from the object. Using SFINAE I could detect whether particular method names were added to an object and use those for mappings (for cases where assignment operators/constructors do not suffice). As assignment operators/constructors/methods within the objects themselves would most often be preferable having such options would make it unnecessary to use function full-specialization (which is not reliably detectable in the library and has serious limitations to what you can template) and preferable to partial template specialization on a struct (which is reliably detectable in the library code and allows for incredibly flexible templates, especially when done in headers).
Before I go off coding neglecting yet another point I'm going to research whether there's some reasonably standard conversion methodology I'm missing and could take advantage of besides assignment operators/constructors/library specific methods.

Something I neglected to take seriously early: assignment operators and constructors taking the "from" value as an argument and assigning/building the "to" value should be auto-detected and used to the extent possible; I think this may result in a lot of rework to the object mapper as when available there's no reason the user should have to add another method to the object mapper namespace to do the mapping; these should just be picked up and used.
Another point I've neglected is that adding mappings in the way I'm currently doing them (a full specialization of a function in the object mapper namespace) is poor in an organizational sense - it could force code for a particular object to be located very far away from the object. Using SFINAE I could detect whether particular method names were added to an object and use those for mappings (for cases where assignment operators/constructors do not suffice). As assignment operators/constructors/methods within the objects themselves would most often be preferable having such options would make it unnecessary to use function full-specialization (which is not reliably detectable in the library and has serious limitations to what you can template) and preferable to partial template specialization on a struct (which is reliably detectable in the library code and allows for incredibly flexible templates, especially when done in headers).
Before I go off coding neglecting yet another point I'm going to research whether there's some reasonably standard conversion methodology I'm missing and could take advantage of besides assignment operators/constructors/library specific methods.

Another thing I'd like to explore is defining bi-directional mappings; via reflection we have automatic bi-directional mappings for fields of the same name; but constructors, assignment operators, and even my custom library functions so far are all uni-directional and to do a custom mapping two ways requires two function definitions; there might be no good way to have a custom bi-directional mapping via a single definition but I do think it's worth taking a stab at.

Another thing I'd like to explore is defining bi-directional mappings; via reflection we have automatic bi-directional mappings for fields of the same name; but constructors, assignment operators, and even my custom library functions so far are all uni-directional and to do a custom mapping two ways requires two function definitions; there might be no good way to have a custom bi-directional mapping via a single definition but I do think it's worth taking a stab at.

With respect to the earlier investigation, besides assignment operators and constructors the only other standard conversion methodology was user-defined conversion operators; I'm able to capture all of these by detecting whether "lhs = rhs" is valid or "lhs = static_cast<decltype(lhs)> rhs" is valid.
One thing I'm going to put a hold on/not have in the first draft implementation is default construction points - in a few places the destinations are required to be default constructable for now (if not manually specialized), I'd like to add something to check for different paths to get a thing constructed/copied/converted which may also be valid for the object mapper to use.

Finished as of #75

repo: TheNitesWhoSay/RareCpp


text:
New function

Hello, I need a function for converting a untis date into js date object.

Ok, this is not that hard. I will do this later.

I know, I do this with a function like that
function convert(untisdate) {                 var ud = untisdate.toString();                 return new Date(ud.substr(0,4) + '.' + ud.substr(4,2) + '.' + ud.substr(6,2));             } but it will be a nice feature, if it is intecraded in the lib.

Implemented both (time and date) in https://github.com/TheNoim/WebUntis/commit/adf606b743e44b9c994362f2ed22bea0bdc26c93

I have not tried it yet, but then i get back a js or a untis date in the functions like gettimetablefortoday().

i do this e.jsdate = untis.convertUntisDate(e.date); and i get this error
(node:6268) UnhandledPromiseRejectionWarning: TypeError: untis.convertUntisDate is not a function     at data.forEach.e (c:\Users\wolflu\Desktop\UntisAPI\index.js:40:39)     at Array.forEach (<anonymous>)     at untis.getOwnTimetableForRange.then (c:\Users\wolflu\Desktop\UntisAPI\index.js:33:18)     at process._tickCallback (internal/process/next_tick.js:68:7) warning.js:18 (node:6268) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)

Oh, I now my problem, i had to do e.jsdate = WebUntisLib.convertUntisDate(e.date) because untis is my object whith will be created by login and not the variable which I set by require. Thank you for this quickly change. I don't know any faster guys than you. Thank You

Can you tell my how big the api pdf is?

277kb

Thanks, bit I mean the number of pages

@TheNoim are using an older version. It's 13 pages and you can request it via Untis Helpdesk

ok thank you very much, because I am considering whether I should inquire

authors: TheNoim dunklesToast luwol3

repo: TheNoim/WebUntis


text:
Allow FCM credential via JSON string in env var.

Description

Adds ability to configure FCM credentials via a JSON string as an alternative to configuring with a file.

Motivation and Context
Support configuration via AWS parameter store secret for ECS instances as part of PP-41.
How Has This Been Tested?

Manually verified that dictionary could be used to configure firebase_admin credentials.
Updated tests for new test cases.
CI passes for the PR's branch.

Checklist

[X] I have updated the documentation accordingly.
[X] All new and existing tests passed.

@RishiDiwanTT requesting your review here, since you've done the bulk of the notification work.

repo: ThePalaceProject/circulation


text:
Bounds check negative index in std::array

#define SOL_CHECK_ARGUMENTS
#define SOL_SAFE_USERTYPES
#include "sol.hpp"

class MyData
{
public:
    std::array<int, 3> three_integers;
};

lua.new_usertype<MyData> ("MyData", "three_integers", &MyData::three_integers);

local my_data = MyData.new()
my_data.three_integers[1] = 7 -- OK, great
my_data.three_integers[2] = 7 -- OK, great
my_data.three_integers[3] = 7 -- OK, great
my_data.three_integers[4] = 7 -- OK, throws Lua exception
my_data.three_integers[0] = 7 -- BAD, silent memory error
my_data.three_integers[-1] = 7 -- BAD, same

Compiler:

Apple LLVM version 7.0.2 (clang-700.1.81)
Target: x86_64-apple-darwin14.5.0
Thread model: posix

sol.hpp:

Generated 2017-05-04 07:17:19.632331 UTC
This header was generated with sol v2.17.1 (revision 7b78558)

There's no real precedent for behavior here, since Lua tables will just attempt to insert the value as best it can (and succeed because they're associative dictionaries with a loose definition for what encompasses a sequence, and it will snap that definition in 2 and return to being an associative dictionary if you look at it funny).
What I can do is -- at the very least -- prevent memory errors by swallowing those inputs and performing no changes on the underlying container. But what kind of exception should I throw...?

Added a few errors if SOL_CHECK_ARGUMENTS is defined, I guess. This should be good enough for your case (since you're defining the safety features), but for other people who like the speed and live on the edge, they can enjoy having no errors if they don't care about safety.
https://github.com/ThePhD/sol2/tree/develop/single/sol

Thanks for looking into this. My two cents are that std::array is a user data, not a table. So its behavior under newindex need not emulate that of a Lua table. In fact, I would prefer 0-based indexing on the array, rather than 1. Safely disregarding out-of-range indexes seems OK to me.
But, is it really only "living on the edge" to allow users of your application to modify arbitrary memory addresses? This sounds to me like it's asking for major vulnerabilities; what happens if I do
for i = 0, 10000000 do
  my_data.three_integers[-i] = 999
end

?

My only assumption is that the user knows what they're doing, at all times. They can forfeit this burden of responsibility by defining SOL_SAFE_USERTYPES and SOL_CHECK_ARGUMENTS.
All example code is written with the safety features on SOL_CHECK_ARGUMENTS. I've also gone through most of the documentation and all complete examples include
#define SOL_CHECK_ARGUMENTS
#include <sol.hpp>
...

or similar. I would love to have safety -- for arguments, for functions, for return types, for userdata -- be always on, but I have a demographic that is keenly interested in having these checks omitted because they A) perform the checks themselves by writing loops that iterate over specific bounds B) use the pairs abstraction afforded to them in Lua 5.2+ C) have a vested interest in high performance and D) type-pun and bit-twiddle to emulate old hardware and low-level VMs.

authors: ThePhD jzrake

license: mit

license_source: bigquery


text:
Ad blockers are not allowed on YouTube ( Pictures showa upp ) after the speed up and there to no auto skip

After pressing allow Youtube ads this comes

After this when we click in in cross option again first pop up comes

same here

I've updated the script to fix the detection. Please let me know if it works for u now. v5.4
also this a duplicate issue.
(https://github.com/TheRealJoelmatic/RemoveAdblockThing/issues/439)

authors: TheRealJoelmatic kaliko69 petr-hybler

repo: TheRealJoelmatic/RemoveAdblockThing


text:
Move Wiki Generation Logic to this Repo

Currently, we generate the wiki inside the Sample Programs repo, and I just find that incredibly clunky. I'd like to move that logic here if possible.
Probably going to leave the Travis CI logic in Sample Programs that way we can use it to trigger Wiki/Website builds and whatnot in the future.

I used this command: git log --pretty=email --patch-with-stat --reverse -- tools/generate-wiki.py | (cd ../sample-programs-wiki-generator && git am)
It seemed to do the trick.

I love it 💯  The distribution in the Sample Programs wiki is fixed now. Python isn't overrunning it. haha


text:
Authentication

Set up SignUp component with AWS amplify.
Set up Google sign in.
Set up Facebook sign in.
Set up 2-Factor Authentication.
https://aws.github.io/aws-amplify/media/authentication_guide.html
Set up the message styling that is sent out to users.
https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pool-settings-message-customizations.html

Both the SignUp and SignIn components have similar code. We will be refactoring them into one file.

repo: TheSourceOfTruth/TheSourceOfTruth


text:
Contract overlay doesn't clear

Not sure what changed recently as I just noticed this today, but when completing a contract the overlay for that contract doesn't clear itself and continues to point towards the person you just finished, including flashing arrow over their head, until you go and get a new contract.

@xSlysoft Have you completed > 1000 contracts and/or have over 1000 points?

Hello!
I've been experiencing the same problem recently. I have completed around 1500 contracts.

This should have been fixed in 1c43b1805a6fd29030d1c9b6e3af3246ad683b78 as it now includes commas in the points and contracts regex matcher. If this error still persists after version 1.4 please open a new issue.

Sorry I didn't get an email notification for your comment, no I did not have > 1000 contracts but I did have > 1000 points. However, the issue is fixed now on my end. Thanks.

authors: IchottMano TheStonedTurtle xSlysoft

repo: TheStonedTurtle/Mahogany-Homes


text:
[Candidate 2v2 Green Silk ZH v1] Units and Rangers can be air dropped on outer islands

Observed behavior
Units and Rangers can be air dropped on outer islands. The Dozer I managed to drop just once. Appears to be not straight forward to do.
Expected behavior
Units and Rangers can not be air dropped on outer islands.
Screenshots

Green Silk ZH v1.zip
Fixed this issue, along with #570 and #568.

Fixed

authors: Jundiyy xezon

repo: TheSuperHackers/GeneralsRankedMaps


text:
Fix readLine's needsHardReset condition

As is, needsHardReset is never set by readLine.
If reads are failing, when attempt is finally zero and causes the while loop to exit, it is also post-decremented and becomes 255 (since it is unsigned). Hence the condition to set needsHardReset is never met.
In fact, the condition attempts<=0 is true only when the last read attempt actually succeeded. In this case, attempt was 1 and is decremented to 0 before the final call to readBytesUntil returns read>0. The while loop exits because !read is false and the value of attempt remains at 0, unchanged, because of short-circuited &&.
Use https://godbolt.org/z/000v_I as a playground to prove this to yourself.
The solution is to ignore attempts after the loop. It did its job already. The important question is whether read is zero or not. If so, we need to reset the module.

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

https://github.com/TheThingsNetwork/arduino-device-lib/issues/242

Thanks!

repo: TheThingsNetwork/arduino-device-lib


text:
Add Color Variables to theme-variables.css

I've never personally truly standardized color variable names.
I tend to name them things like:
dark-blue
blue
light-blue
I think that practice is fine, but I think having Primary Secondary etc. is good and more site agnostic.
Maybe it makes sense to kinda combine the best of both worlds.
Users would create their own color variable names, then assign primary, secondary etc. colors to reference the named colors?
Example of the concept:
https://getbootstrap.com/docs/4.0/utilities/colors/

I agreeOn May 14, 2019 9:23 AM, Jon McLaren notifications@github.com wrote:I've never personally truly standardized color variable names.
I tend to name them things like:
dark-blue
blue
light-blue
I think that practice is fine, but I think having Primary Secondary etc. is good and more site agnostic.
Maybe it makes sense to kinda combine the best of both worlds.
Users would create their own color variable names, then assign primary, secondary etc. colors to reference the named colors?
Example of the concept:
https://getbootstrap.com/docs/4.0/utilities/colors/
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

I think lets go with it, whoever gets a chance to implement it first, go for it.
These would go in theme-variables.css

Agreed, what we're talking is kind of a hybrid.

I'm torn on it, I like my variable names to be semantic and descriptive. In my experience if a brand changes colors, then they're probably changing their website theme anyways

I also agree with that too. I can't say after a site's been up a long while I've really needed to re-color it very often, and when I have needed to do that. find and replacing the color name var if it was used instead of the primary secondary wasn't a big deal at all. Took all of 5 seconds.
This is kinda why I think a hybrid approach might be better.
Example
user makes a blue variable
Primary  == blue variable
everything in crankshaft that might use primary is now using blue.
for text color classes for example both text-blue and text-primary could make the color blue

@TheWebTech I'll take this guy on.
I agree with a hybrid approach, though we might want to consider how to handle darkening/lightening colors. Has one of you ever created a macro that handles something like that, that we could integrate for easier control of such situations? It would be great if we could plug in something like:
`
{% set brandBlue = #0366d6 %}
{% set primaryColor    = brandBlue %}
.btn-funtimes {
color: lighten( {{ primaryColor }} , 10 )
}`

Totally agree on it would be great to have macros for handling the color lightening/darkening.
I haven't created one but I'm sure we could reference one built for scss or another tool and basically just rebuild it using HubL.
otherwise for light and dark users could also specify hsl colors but, I think most devs prefer hex or rgba since they're easier to read and know what's going on.

I'll do some investigation.

Resolved by @danaholdt in #77
Any further discussion on color vars or related to colors make a new issue

authors: TheWebTech adesignl danaholdt jfudman

repo: TheWebTech/CrankShaft


text:
🛑 Language Explorer production is down

In a17015a, Language Explorer production (https://app.languageexplorerapp.co.uk/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Language Explorer production is back up in a3a717f.

repo: TherapyBox/upptime


text:
🛑 VocaQuest server production is down

In b8a0181, VocaQuest server production (https://srv.voca-quest.com/) was down:

HTTP code: 502
Response time: 330 ms

Resolved: VocaQuest server production is back up in e56cc51.


text:
🛑 Stream staging CMS is down

In 44dde0d, Stream staging CMS (https://stream-cms.internal.therapy-box.co.uk/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Stream staging CMS is back up in 9726f7f.


text:
🛑 Language Explorer production is down

In 669628a, Language Explorer production (https://app.languageexplorerapp.co.uk/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Language Explorer production is back up in c229253.


text:
🛑 Outlook is down

In a3b1e38, Outlook (https://outlook.live.com) was down:

HTTP code: 417
Response time: 113 ms

Resolved: Outlook is back up in a98eaef after 12 minutes.

repo: Thexyz/Email-Monitoring


text:
Sleep Mode broken a screen touch does not prevent sleep mode

I don’t see any checks for a screen touch that resets “timerPress” counter I only find it present in setup and for the check togo to sleep. If ’SLEEP_INTERVAL_SECS is set it will go into hard sleep at SLEEP_INTERVAL_SECS always.
There is no way to stop sleep after sleep timeout display screens starts.

Expected behavior
A screen press should restart the sleep mode timer and abort activating sleep mode
Actual behavior
With  SLEEP_INTERVAL_SECS set the device will go to sleep regardless of any screen touch
Test code
in settings.h Set SLEEP_INTERVAL_SECS to 15
The device will go to sleep in 15 seconds even if the screen is touched
Fix:

Added timerPress = millis(); after screen touch check in loop().
Moved sleep code to a function outside of main loop for clarity.
added abort for any screen touch and a new option for light off mode.

Additions:
Addition to settings.h a boolean for HARD_SLEEP.

false turns the back light LED off.
true  existing "Hard sleep" mode.

Weather Station Color version
Master
Hardware
ThingPulse Weather Station Color kit purchased through Amazon April 2021

Put these proposed changes in a draft request "Time period"


text:
Fix(url): field validation

Resolves #661
Fixes #661

@emmatown ? It's ruining my ux in production site

Hey @ArnavK-09
@emmatown is on holiday this week, but I've tried to reproduce the problem you're reporting and can't quite understand how it's not working for you (and also, how this fixes it)
I'm happy to push through a fix for you while she's away, but will need some more information to ensure this is the correct change.
The current validation logic is intended to:

Ensure that if there is a value provided, it is actually a valid URL
Only if isRequired === true, also ensure that a value (not an empty string) has been provided

When I add a field with this config to my test project:
url: fields.url({ label: 'URL' }),

... it doesn't seem to cause a problem saving an entry with no value in the field (which is how I interpret your fix to work)
Setting the option to false, like this, also works:
url: fields.url({ label: 'URL', validation: { isRequired: false } }),

The way I read the change you're proposing here, format validation would only happen if the field is required, which is not the intended behaviour. If you want to allow any format of value in the field, you could just use fields.text
Can you help clarify what behaviour you're seeing that's different, and how this fix resolves the issue?
Thanks

Hey @JedWatson

Thanks for looking into the matter, actually the problem triggers on creating new post., Kindly checkout  Some screenshots below

The problem
https://github.com/Thinkmill/keystatic/assets/69188140/a186988a-8c01-47f0-b114-414d86a1505b
My Default Config

Even my I don't pass any validation prop
https://github.com/Thinkmill/keystatic/assets/69188140/4cff9c1c-283e-4d49-a44b-b4b6faa07f26

I request you to kindly fix #661, and it would be alright if this pull req doesn't fix the issue actually I haven't tested the changes, but please positively fix with any other change

✨ Regards

Maybe !isRequired validation is extra in my pull req I guess so, since on init the value passed is '' not null, ig

repo: Thinkmill/keystatic


text:
When the schema is typed as JSONSchema, FromSchema is never

Hello,
The newly created type from a schema is never if the schema is typed as JSONSchema.
Let me demonstrate with an object example provided in the README.MD
When typed as JSONSchema
In the following example, I denote objectSchema variable as JSONSchema, and it is indeed helpful when I am typing properties.
However, when I declare Object using objectSchema, its value is never.
import type { FromSchema, JSONSchema } from "json-schema-to-ts"

const objectSchema: JSONSchema = {
      type: "object",
      properties: {
            foo: { type: "string" },
            bar: { type: "number" },
      },
      required: ["foo"],
} as const;
type Object = FromSchema<typeof objectSchema>;

Here you can see the type when I hover over Object:

When NOT typed as JSONSchema
The very same example, however, works when I don't annotate objectSchema.
import type { FromSchema } from "json-schema-to-ts"

const objectSchema = {
      type: "object",
      properties: {
            foo: { type: "string" },
            bar: { type: "number" },
      },
      required: ["foo"],
} as const;
type Object = FromSchema<typeof objectSchema>;

I'm really not sure why, and I'm confused as FromSchema is already defined as a generic expecting JSONSchema type, however, resulting in never when a value typed as JSONSchema.
export declare type FromSchema<S extends JSONSchema> = Resolve<ParseSchema<DeepWriteable<S>>>;

Hello @omer-to !
I understand it is confusing, but this is the expected behavior.
A constant (objectSchema here) can only have one type. If you don't assign one to it, TS will infer it from its definition. The as const statement forces it to be as narrow as possible. Notice the difference:
const objectSchema = {
      type: "object",
      properties: {
            foo: { type: "string" },
            bar: { type: "number" },
      },
      required: ["foo"],
}

type testWidened = typeof objectSchema
// => { type: string, properties: { foo: string, bar: string }, required: string[] }
// The type is not narrow, for instance, the hard string "number" is widened as a general string

const objectSchema = {
      type: "object",
      properties: {
            foo: { type: "string" },
            bar: { type: "number" },
      },
      required: ["foo"],
} as const

type testNarrow = typeof objectSchema
// => { type: "object" , properties: { foo: "string", bar: "number" }, required:["foo"] }
// (I omitted the readonly part for the sake of simplicity)
// The type is narrow, for instance "number" is kept as the hard string "number"

const objectSchema: JSONSchema = {
      type: "object",
      properties: {
            foo: { type: "string" },
            bar: { type: "number" },
      },
      required: ["foo"],
} as const;

type testAssigned = typeof objectSchema
// => JSONSchema
// The assigned type JSONSchema overrides the inferred type from TS

In order for FromSchema to be able to infer the valid type from a schema, the input schema type needs to be as narrow as possible. Otherwise, it won't be able to apply any logic to it. For instance, if every type keyword value is widened as a general string or as a union of hard strings ("object" | "array" | ...), FromSchema won't have enough information on the schema to operate. FromSchema<JSONSchema> will not return anything, the JSONSchema definition is too large to infer anything.
However, that doesn't prevent it from enforcing that the input schema type should follow a certain shape, and that means extending a certain type. That's the meaning of the S extends JSONSchema that you found in the definition. This allows S (which is, in your case  { type: "object" , properties: { foo: "string", bar: "number" }, required:["foo"] }) to be validated against JSONSchema, while not being strictly equal to JSONSchema.
I hope it makes things a bit clearer. The main takeaway is that you cannot both assign JSONSchema and apply FromSchema to the same const simultaneously. Cheers !

@ThomasAribart I was struggling with a similar issue. I am trying to infer a JSONSchema argument of an execute function with this library. I was attempting it this way:
import { FromSchema, JSONSchema } from 'json-schema-to-ts';

type Method<Input = JSONSchema> = {
  input: Input;
  execute: (input: FromSchema<Input>) => void;
}

const method: Method = {
  input: {
    type: 'object',
    properties: {
      name: {
        type: 'string',
      }
    }
  },

  execute({ name }) {

  }
}

What I'd like to achieve is that the input JSON schema gets translated as a typed argument inside the execute function. As you explained above this is likely not possible this way... Do you have any ideas to achieve the same result? Or is this not possible?

Not sure why, but by using a function to create the method I do get proper type information:
import { JSONSchema, FromSchema } from "json-schema-to-ts";

function createMethod<Input extends JSONSchema>(options: {
  input: Input;
  execute: (input: FromSchema<Input>) => void;
}) {}

createMethod({
  input: {
    type: "object",
    properties: {
      name: {
        type: "string",
      },
    },
  } as const,
  execute: (input) => {
    return input.name; // string
  },
});

You can do the following:
import { FromSchema, JSONSchema } from 'json-schema-to-ts';

type Method<Input extends JSONSchema = JSONSchema> = {
  input: Input;
  execute: (input: FromSchema<Input>) => void; // <= Here error will not be raised because Input extends JSONSchema
}

const method: Method<typeof yourSchema> = {
  ...
}

The second method will work also 👍 I'm closing this issue :)

@ThomasAribart Will the satisfies operator of Typescript 4.9 make it possible to check the type against JSONSchema?

Yup :) Gonna add it to the docs !

Yup :) Gonna add it to the docs !

I think it should be mentioned in the FAQ
https://github.com/ThomasAribart/json-schema-to-ts/blob/HEAD/documentation/FAQs/can-i-assign-jsonschema-to-my-schema-and-use-fromschema-at-the-same-time.md

authors: Momics ThomasAribart Zhincore alphaone omer-to

repo: ThomasAribart/json-schema-to-ts


text:
🛑 Qbit is down

In d0266b7, Qbit (https://qbit.cond.dk) was down:

HTTP code: 523
Response time: 402 ms

Resolved: Qbit is back up in 58c904f.


text:
Change to logfmt format

The logfmt doesn't really have a standard, but it is described here:
https://www.brandur.org/logfmt, along with its best practices.
The new implementation uses vectored writing, reducing the amount of
copying when formatting the log record.
TODO:

[ ] Use vectored I/O in key-values of the record.
[ ] Benchmark copying into a single buffer vs. using more vectored I/O. I.e. at what point is copying x bytes cheaper than using another iovec.

Blocked by https://github.com/sval-rs/value-bag/issues/15.

Some follow up issues: #34, #35.

repo: Thomasdezeeuw/std-logger


text:
Can not select mods

2/12/21- Installed UMF followed the instructions w/ no issues, mods loaded into folder, game starts up, enabled mods. They show up as a selection during game play ie: "1,2,3" for weapons selection, but they will not select when choosing the corresponding number for the mod/weapon?

Updated: The scroll on the mouse allowed me to select the weapon mods... newb moment I guess

Sorry for the late response, but yes you're right you have to use the scroll-wheel to select custom tools.
This is intentionally done to keep the official number -> tool mapping that the game has.

authors: Thomasims xShawnDx

repo: Thomasims/TeardownUMF

license: Unlicense


text:
Improve Gcov reports

This commits does some work on the gcov plugin most of which is clean up.
The two new things this commit does:

Now puts the gcov coverage html report into artifacts
Adjust level of detail in the report by defining either 'basic' or 'advanced'

The new setting can be added to the project.yml as such:
:gcov:
  :html_report_type: basic

or
:gcov:
  :html_report_type: advanced

Did you notice that it does not take gcov_compiler, etc. from the target file but rather from the provided default.yml file (inside plugin?) Can we maybe fix that as well?

@Letme  yes, but it's not an easy conversion as then we will need to get all settings from the configuratior and default back to the hardcoded if the configurator's settings are not found. After this update I actually understand the configuratior will enough to do it.
I'd also need to look into how compatible the gcov's results display would be with different configurations as I'm not sure how tightly coupled they are with the hardcoded options.

I have simply deleted default options and now it seems to work just fine. There is some difference with how current test_compiler config handles object and source files (not needed to be -o {2} -c {1} flags anymore), I would assume gcov_compiler would do the same and after deleting settings I needed to find correct parameters myself with a bit of playing but now it works if I compile with gcc or with clang (gcov or llvm-cov - and some wrapper script to make it llvm-cov gcov).
I would be very happy if you could do it - I am willing to send you some chocolate :smiley:

I'll see what I can do over the next few days. No promises, but I'll at least try.

I don't know the gcov plugin itself well, but I've recently built and/or cleaned up some of the other plugins. If I can answer a question or two, feel free to email me directly.

@Letme
After some experimenting, it seems this functionality already exists in the same fashion as it does in the normal Ceedling. I was able to get llvm-cov by doing the following:
:tools:
  :gcov_compiler:
    :executable: clang
    :arguments:
      - -fprofile-arcs
      - -ftest-coverage
      - -I"$": COLLECTION_PATHS_TEST_SUPPORT_SOURCE_INCLUDE_VENDOR
      - -I"$": COLLECTION_PATHS_TEST_TOOLCHAIN_INCLUDE
      - -D$: COLLECTION_DEFINES_TEST_AND_VENDOR
      - -c "${1}"
      - -o "${2}"
  :gcov_linker:
    :executable: clang
    :arguments:
      - --coverage
      - ${1}
      - -o ${2}
  :gcov_fixture:
    :executable: ${1}
  :gcov_report:
    :executable: llvm-cov-3.5
    :arguments:
      - -n
      - -p
      - -b
      - -o "$": GCOV_BUILD_OUTPUT_PATH
      - "\"${1}\""

I will admit these settings we're not 100% and I kept getting odd errors from llvm-cov (unexpected number of edges), but at least it ran in a way that someone who does work with llvm-cov could probably get running easily.

@dpostorivo I can paste you my ones which also works, but you need to delete default.yml
Thing is, new Ceedling conf does not need ${1} in compiler and linker, it also does not need -Is since it takes that from :flags: directive (which remembers me I have :test: in flags but not :gcov:, so that might be a reason).
Anyway I have following
 :gcov_compiler:
    :executable: clang
    :arguments:
      - -Iemlib/inc/
      - -IEFM32TG/Include/
      - -ICMSIS/Include/
      - -D'__ARM__'
      - -D'__SOFTFP__'
      - -D'__CLANG__'
      - -Wno-pointer-to-int-cast
      - -Wno-int-to-pointer-cast
      - -Wall
      - -Wno-address
      - -Wno-attributes
      - -Wno-unused-function
      - -std=c99
      - -fshort-enums
      - -pedantic
      - -fprofile-arcs
      - -ftest-coverage
      - -D$: COLLECTION_DEFINES_TEST_AND_VENDOR
      - -I"$": COLLECTION_PATHS_TEST_SUPPORT_SOURCE_INCLUDE_VENDOR
      - -c ${1}                       #source code input file (Ruby method call param list sub)
      - -o ${2}                       #object file output (Ruby method call param list sub)
  :gcov_linker:
    :executable: clang
    :arguments:
      - ${1}
      - -lm
      - -D$: COLLECTION_DEFINES_TEST_AND_VENDOR
      - -I"$": COLLECTION_PATHS_TEST_SUPPORT_SOURCE_INCLUDE_VENDOR
      - -lgcov
      - --coverage
      - -o ${2}            #executable file output (Ruby method call param list sub)
  :gcov_fixture:
    :executable: ${1}
  :gcov_report:
    :executable: llvm-cov
    :arguments:
      - gcov
      - -n
      - -p
      - -b
      - -o "$": GCOV_BUILD_OUTPUT_PATH
      - "\"${1}\""
  :gcov_post_report:
    :executable: lcov
    :optional: FALSE
    :arguments:
        - --directory build/gcov/out/
        - --gcov-tool './scripts/llvm-gcov.sh'
        - --no-external
        - --capture
        - --config-file .lcovrc
        - --output-file build/artifacts/gcov/lcov.info

and scripts/llvm-gcov.sh is just a wrapper for llvm-cov with gcov as direct argument.
#!/bin/bash
exec llvm-cov gcov "$@"

However to get a proper nice report out, I still need to have a target in Makefile for genhtml:
	@$(GENHTML) build/artifacts/gcov/lcov.info -o build/coverage/ --config-file .lcovrc

@Letme  I'm not sure why you would have to delete default.yml. Is it just the gcov_post_report that doesn't work if default or is it all of the gcov plugin?

It seems like I have some really specific stuff, but if default.yml is there, it does not use the clang to compile, but normal GCC and then concats arguments together, while  executable remains the on in default. Of course if I change the one in default.yml then it uses that program.
Fishy thing is also that dependencies and preprocessing is also done by gcc, but I assume this is because I do not have nothing for that defined in my clang target yml (only compiler&linker, test_compiler&test_linker, gcov_compiler&gcov_linker&gcov_fixture&gcov_report) .

@Letme I think that issue has been taken care of? There were some quirks in the way configuration options were getting merged that I believe are doing better now?

This is all fairly unrelated to this MR which can go in as it is.
On the other side, I have applied the patch to latest master, but I get order of flags mixed. I do not know what might be wrong, but
  :gcov_report:
    :executable: llvm-cov
    :arguments:
      - gcov
      - -n
      - -p
      - -b
      - -o "$": GCOV_BUILD_OUTPUT_PATH
      - "\"${1}\""

Produces error:
> Shell executed command:
'llvm-cov -n -p -b -o "build/gcov/out" "adc.c" gcov'
> And exited with status: [1].

Order of flags passed changed for some reason (and here it is important). It was preserved before this I also tried 'llvm-cov gcov' as executable, but then it complains (as before)
ERROR: Config filepath [:tools][:gcov_report][:executable]['llvm-cov gcov'] does not exist in system search paths.

Anyway unrelated and should not be blocking this MR.

OK edit of above: This PR does not introduce anything new. The issue from above is fixed if I delete default.yml in gcov plugin . This should be merged in.

authors: Letme dpostorivo mvandervoord

repo: ThrowTheSwitch/Ceedling


text:
LoRA was trained, but does not work in Stable Diffusion

Hello, I do not understand what the problem, the learning process is fine, but when I try to generate images, nothing changes. LoRA has no effect at all on generation
===================================BUG REPORT===================================
Welcome to bitsandbytes. For bug reports, please submit your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
================================================================================
use 8-bit AdamW optimizer | {}
running training / 学習開始
  num train images * repeats / 学習画像の数×繰り返し回数: 2200
  num reg images / 正則化画像の数: 0
  num batches per epoch / 1epochのバッチ数: 1100
  num epochs / epoch数: 1
  batch size per device / バッチサイズ: 2
  total train batch size (with parallel & distributed & accumulation) / 総バッチサイズ（並列学習、勾配合計含む）: 2
  gradient accumulation steps / 勾配を合計するステップ数 = 1
  total optimization steps / 学習ステップ数: 1100
steps:   0%|                                                                                | 0/1100 [00:00<?, ?it/s]epoch 1/1
steps: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1100/1100 [05:10<00:00,  3.54it/s, loss=0.152]save trained model to LoRA/output/Tqweqwfd.safetensors
model saved.
steps: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1100/1100 [05:10<00:00,  3.54it/s, loss=0.152]

The training schedule is as follows

Training parameters:
{
  "pretrained_model_name_or_path": "XpucT/Deliberate",
  "v2": false,
  "v_parameterization": false,
  "logging_dir": "LoRA/log",
  "train_data_dir": "LoRA/input",
  "reg_data_dir": "",
  "output_dir": "LoRA/output",
  "max_resolution": "512,512",
  "learning_rate": "0.0001",
  "lr_scheduler": "constant",
  "lr_warmup": "0",
  "train_batch_size": 2,
  "epoch": "1",
  "save_every_n_epochs": "1",
  "mixed_precision": "fp16",
  "save_precision": "fp16",
  "seed": "385405080",
  "num_cpu_threads_per_process": 2,
  "cache_latents": true,
  "caption_extension": ".txt",
  "enable_bucket": false,
  "gradient_checkpointing": false,
  "full_fp16": false,
  "no_token_padding": false,
  "stop_text_encoder_training": 0,
  "use_8bit_adam": false,
  "xformers": true,
  "save_model_as": "safetensors",
  "shuffle_caption": false,
  "save_state": false,
  "resume": "",
  "prior_loss_weight": 1.0,
  "text_encoder_lr": "5e-5",
  "unet_lr": "0.0001",
  "network_dim": 128,
  "lora_network_weights": "",
  "color_aug": false,
  "flip_aug": false,
  "clip_skip": 2,
  "gradient_accumulation_steps": 1.0,
  "mem_eff_attn": false,
  "output_name": "Tqweqwfd",
  "model_list": "runwayml/stable-diffusion-v1-5",
  "max_token_length": "75",
  "max_train_epochs": "",
  "max_data_loader_n_workers": "1",
  "network_alpha": 128,
  "training_comment": "Trigger word: Tqweqwfd",
  "keep_tokens": "0",
  "lr_scheduler_num_cycles": "",
  "lr_scheduler_power": "",
  "persistent_data_loader_workers": false,
  "bucket_no_upscale": true,
  "random_crop": false,
  "bucket_reso_steps": 64.0,
  "caption_dropout_every_n_epochs": 0.0,
  "caption_dropout_rate": 0,
  "optimizer": "AdamW8bit",
  "optimizer_args": "",
  "noise_offset": "",
  "LoRA_type": "Standard",
  "conv_dim": 1,
  "conv_alpha": 1
}

Generation without LoRA

Generation with LoRA

I am using runpod service for train model on linux. Can you please suggest what is the problem?

Hi, you are not the only one with the problem. So far, no solution :(.
The last update of bmaltais/kohya_ss has enabled linux support.
Can you try to generate LoRA there?

Ok, I'll try to install according to his instructions. Thanks for the answer)

+1

authors: AlexSgt Thund3rPat YeHaijia


text:
🛑 Melon Ticket is down

In ec52d4a, Melon Ticket (https://ticket.melon.com) was down:

HTTP code: 406
Response time: 991 ms

Resolved: Melon Ticket is back up in 06cdf38 after 20 minutes.

repo: TicketOpen/status


text:
Install htslib from tiledb channel

This PR replaces the vendored build of htslib with a conda binary from the tiledb channel. This should be a temporary workaround.  TileDB-Inc/htslib-feedstock builds against a matrix of multiple libdeflate variants and both openssl 1.1.1 and 3, which avoids the conda solver problems we had in #62.  Once bioconda starts building against openssl 3 like conda-forge is, then we can switch back to bioconda (we'll also likely need to stop supporting Python 3.7 at that point).
Closes #76
Additional context: The next step will be to attempt a Windows build using tiledb::m2w64-htslib

From the Linux build logs:

libtiledbvcf is built with openssl 3, libdeflate 1.17, tiledb 2.14.1-hd532e3d_1, and tiledb::htslib 1.16-h769fb50_4
tiledbvcf-py is built with openssl 3, libdeflate 1.17, tiledb 2.14.1-hd532e3d_1, and tiledb::htslib 1.16-h769fb50_4 for Python 3.8, 3.9, and 3.10
tiledbvcf-py is built with openssl 1.1.1, libdeflate 1.17, tiledb 2.14.1-hc2ae436_1, and tiledb::htslib 1.16-h94f6b6d_4 for Python 3.7

Thus the main concern is the build for Python 3.7. tiledbvcf-py for Python 3.7 is still co-installed with libtiledbvcf 0.22.2-h1d2eca6_3, which was built against libtiledb that was linked against openssl 3.  The reason the conda solver is fine with this situation since libtiledbvcf doesn't use run_exports for openssl:
"libtiledbvcf-0.22.2-h1d2eca6": {
  "recipe": {
    "c_compiler": "gcc",
    "c_compiler_version": "11",
    "channel_targets": "tiledb main",
    "cxx_compiler": "gxx",
    "cxx_compiler_version": "11",
    "target_platform": "linux-64"
  }
},

Do we anticipate any problems using tiledbvcf-py with a libtiledbvcf built against an openssl3-linked tiledb, but is ultimately being installed in a conda env that instead contains an openssl1.1.1-linked tiledb?
INFO (libtiledbvcf,lib/libtiledbvcf.so): Needed DSO lib/libtiledb.so.2.14 found in conda-forge::tiledb-2.14.1-hd532e3d_1

Note: it's a similar situation for the macOS builds. Even though htslib doesn't depend on openssl on macOS, tiledb does, so the Python 3.7 env always installs an openssl1.1.1-linked tiledb

Do we anticipate any problems using tiledbvcf-py with a libtiledbvcf built against an openssl3-linked tiledb, but is ultimately being installed in a conda env that instead contains an openssl1.1.1-linked tiledb?

I adapted the quick start instructions into recipe tests, and the Python 3.7 env had no problem downloading and extracting data from s3. If in the future a user identifies a problem, we can drop 3.7 from the build matrix

repo: TileDB-Inc/tiledb-vcf-feedstock


text:
Stop camera at universe border

The camera used to stop at the edge of the universe. Should that be reimplemented?

later on I would like the universe to be so large, and nothing interesting be located near the edge so that the player basically never has to see the edge or worry about flying out of the universe. So, it shouldn't matter that much either way.
Anyway, it's fine the way it looks now.


text:
register 1.2.0

@JuliaRegistrator register()
Release notes:

Interface for univariate Taylor polynomial propagation univariate_tpp
more interfaces for derivative
low-level mutating functions to allow precise preallocations -> not really documented yet
fix a bug in type promotion

Registration pull request created: JuliaRegistries/General/110892
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.2.0 -m "<description of version>" 0fa38e7f359e726d6c5299ef84f3a55240d1ce0e
git push origin v1.2.0


text:
Do not persist dangerous flags such as push --force or --force-with-lease by default

The --force and --force-with-lease flags are seemingly persisted across different pushes. This is most likely unwanted and runs users into the danger of force-pushing to a branch they don't want to force-push to.
Describe the solution you'd like
Simply avoid persisting these flags' values across pushes.

Thanks for pointing out that there's something for this. Adding it to my config as well!
Still, I believe those would be good defaults.

Yea, my thinking was that I would leave it up to the user to disable, but maybe sensible defaults are a better way to go.

This has been merged :)

authors: CKolkey fnune

repo: TimUntersberger/neogit


text:
Restrain progress messages

This PR ports the logic from #205 to the new event-driven scheduler logic. Most of the logic is unchanged or simplified, due to the state maintained by the new reachability tracker.
One important change is that the default behavior is now with the progress accumulation optimization enabled, rather than disabled as it is in #205. To return to the old behavior, where progress messages are eagerly exchanged rather than exchanged only when justified, set the environment variable
DEFAULT_PROGRESS_MODE = EAGER

This should cause all progress messages to be exchanged as soon as they are available, even if they cannot obviously improve the progress of the computation.
The down side for non-eager progress message exchange is the potential increase of the critical path for latency sensitive, progress bound computations. Where one worker.step() could have circulated all outstanding progress messages, we may need multiple rounds in order to inform participants that they should now send their updates.
It remains an open question how painful this is, but the alternative (eager progress messages) has a known downside of many orders of magnitude increase in the volume of progress traffic. Ideally, some experimentation will begin to surface any problems, and we can look at ways to fix things further.

Is there a reason why this is configured via an environment variable and not as a compile-time feature?
And does either mode affect running in Configuration::Thread?
Thanks!

Good questions both.

The environment variable approach lets us better test with and without, to relate the performance of two configurations. The test is not expensive (the variable is read once per scope, and the boolean bound internally), and the compiled code are not much different. Perhaps it should be added to per-scope configuration parameters, but I think at least for experimentation the environment variable approach makes things a bit easier to test, diagnose, and debug.

Good question. I think "mostly no". There might be some corner cases where it makes an interesting change. I think I could write such a demonstration (e.g. a scope whose inputs don't advance, but which contains a flatmap that slowly plays out its data; would accumulate updates until the scope input advances). If it does have a noticeable impact something is probably mis-understood on my part, though.

Not planning on landing this without further testing, and perhaps without swapping the defaults back to eager to avoid surprises for folks not paying attention to our public test schedule.

Ok, thanks for clearing things up :)

Merged with default changed back to old behavior. Switching default will be a more interesting choice that should call for a bit of experimentation.

authors: comnik frankmcsherry

repo: TimelyDataflow/timely-dataflow


text:
Genbank error checking

This is a genbank error checking file. As with the other branches, multi genbank parsing was removed. Parse, write, and read now defaults to outputting a list, though we don't have multi-genbank working quite yet.
I deleted TestLocusParseRegression because it doesn't work. These two lines are different, which the old parser did not pick up, but the newer parser picks up.
https://github.com/TimothyStiles/poly/blob/359da2c15a5b20c12b68d5eb25f8254dd67ee62a/data/puc19static.gbk#L43
https://github.com/TimothyStiles/poly/blob/359da2c15a5b20c12b68d5eb25f8254dd67ee62a/data/puc19.gbk#L43

Biggest concern is that the original Genbank/MultiGenbank paradigm has been overwritten where now MultiGenbank is now just being called Genbank. Can we have both?

Biggest concern is that the original Genbank/MultiGenbank paradigm has been overwritten where now MultiGenbank is now just being called Genbank. Can we have both?

Yes - Genbank is just MultiGenbank of list size 1 (in fact, the parser only does single Genbank right now, gotta fix it up to do multi. Lemme try that out). Much easier than having separate functions I think.
Removed redundancy in latest push and deleted puc19static - which was broken in multiple ways.

@Koeng101 don't forget to merge upstream. I'm pretty sure I deleted that static puc19 file in my last merged PR.

Biggest concern is that the original Genbank/MultiGenbank paradigm has been overwritten where now MultiGenbank is now just being called Genbank. Can we have both?

Yes - Genbank is just MultiGenbank of list size 1 (in fact, the parser only does single Genbank right now, gotta fix it up to do multi. Lemme try that out). Much easier than having separate functions I think.

@Koeng101 I think separate functions would be better for clarity but we can debate later. It'd be super easy to add a variadic argument to a multigenbank parser to limit number of genbanks parsed and just call that from our "single" genbank parser.

@Koeng101 don't forget to merge upstream. I'm pretty sure I deleted that static puc19 file in my last merged PR.

Yes, it is merged upstream, and no, it wasn't deleted because it was used for testing.

I think separate functions would be better for clarity but we can debate later

Ye that is fair

@TimothyStiles How is this looking? I recall I removed the multi-genbank functions, but is there anything else?

@Koeng101 found an issue with the genbank parser where it somehow strips out complements from the gbk string while parsing. Any idea on what's going on here?

Also need to fix qualifier line breaks but that should be easy enoug

h

repo: TimothyStiles/poly


text:
Улучшение интервалов по свечам

Устранить два одинаковых Enum: ru.tinkoff.invest.openapi.model.res.CandleResolution и ru.tinkoff.invest.openapi.model.stream.CandleInterval, не вижу ни одной причины зачем использовать два Enum.
Использовать более расширенный Enum ru.tinkoff.invest.openapi.model.stream.CandleInterval в качестве основного, поскольку в ru.tinkoff.invest.openapi.model.res.CandleResolution нет интервала 4hour а он очень нужен для технического анализа.

Enum из пакета model.rest сгенерирован. Придётся отказаться от генерации моделей из сваггера целиком. Расширенный Enum использовать не совсем корректно, поскольку при использовании 4hour будет возникать ошибка.
Это проблема скорее на уровне API, а не SDK. Думаю, лучше обратиться с этим вопросом в соответствующий репозиторий. Хотя сейчас готовится к выпуску API версии 2.0, где всё поменяется, поэтому вряд ли в текущей версии эту проблему устранят.

authors: Freeongoo zlumyo

repo: Tinkoff/invest-openapi-java-sdk


text:
Отмена частично исполненной лимитной заявки

Что случилось?
У меня вопрос, почему лимитная заявка, которая частично исполнена(например из 100 лотов взялось 50), не может быть закрыта?
Из API приходит такая ошибка:
639195280bb74a3a4faf12155315610b CancelOrder INVALID_ARGUMENT 30059 (<StatusCode.INVALID_ARGUMENT: (3, 'invalid argument')>, '30059', Metadata(tracking_id='639195280bb74a3a4faf12155315610b', ratelimit_limit='100, 100;w=60', ratelimit_remaining=99, ratelimit_reset=32, message='cancel order error: The order has been partially or fully executed.'))
Судя по описанию ошибки, сказано, что нельзя закрыть лимитную заявку, так как она частично или полностью исполнена. При этом в документации Tinkof API про это не сказано ни слова, да и в самом териминале можно отменять частично исполненные заявки. Просьба разъяснить этот момент, так как он является очень важным, для торговых роботов по лимитным заявкам.
Общая идея такая, что заявка должна сниматься по истечению таймера в 10 секунд, не важно частично она исполнена или нет. Если исполнена полностью, понятное дело, что она не будет сниматься.
Воспроизведение
1. Создание AsyncClient
2. Выставление лимитной заявки через await client.orders.post_order()
3. Запуск таймера на 10с
4. Получение состояния ордера каждые 0.5с с помощью await client.orders.get_order_state()
5. Если какая-то часть заявки исполнилась, то выставляется заявка в обратную сторону на то кол-во лотов, что исполнилось.
6. По прошедствию 10 секунд, если запрашиваемое количество лотов != исполненное количество лотов, то выполняется await client.orders.cancel_order()
7. В случае если заявка была частично исполнена, то приходит ошибка.

Tinkoff Invest Version
0.2.0-beta43
Python Version
3.10
OS
Windows
Логи
No response

Добрый день, была такая проблема, уже решена.

authors: AlexanderVolkovTCS artemtyupov

repo: Tinkoff/invest-python


text:
Numpad support not working with laptop

Hey, love the concept but my computer's numpad support isn't being picked up by OW. I don't know how to modify the code to make a personal patch, so if there's a way you could add rebinding to the mod settings menu for people whose numpad options are limited, it would help a lot!

Okay nevermind I come back an hour later and it works no issue. Outer wilds is finicky with it's inputs huh. Thanks for the awesome mod

repo: TitchDEV/remoteautopilot


text:
Add support for Debian 12 (bookworm)

Just a reminder to myself. There was some kind of Python issue.

Turns out the issue was actually with mpich and MPI_Finalize(). Some kind of race condition.

Done. Added support for mantic also. Removed support for stretch and kinetic.

repo: Tjoppen/fmigo


text:
Triton部署TensorRT-LLM报错

请问23.12的triton镜像，0.7.0版本的TensorRT-LLM，可以成功用Triton部署qwen 吗？我测试跑起来有很多报错
python build.py --hf_model_dir /mnt/workspace/model_hub/third_party/Qwen-14B-Chat
--dtype float16
--max_batch_size 4
--max_input_len 2048
--max_output_len 2048
--use_inflight_batching
--paged_kv_cache
--remove_input_padding
--output_dir ./trt_engines_14b_chat_new/trt_engines/fp16/1-gpu/
部分报错信息：
请问23.12的triton镜像，0.7.0版本的TensorRT-LLM，可以成功用Triton部署qwen 吗？我测试跑起来有很多报错
python build.py --hf_model_dir /mnt/workspace/model_hub/third_party/Qwen-14B-Chat
--dtype float16
--max_batch_size 4
--max_input_len 2048
--max_output_len 2048
--use_inflight_batching
--paged_kv_cache
--remove_input_padding
--output_dir ./trt_engines_14b_chat_new/trt_engines/fp16/1-gpu/
部分报错信息：
[TensorRT-LLM][INFO] [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +0, GPU +8, now: CPU 27075, GPU 27524 (MiB)
[TensorRT-LLM][INFO] [MemUsageChange] Init cuDNN: CPU +1, GPU +10, now: CPU 27076, GPU 27534 (MiB)
[dsw-6138-7785b6c584-qtx6w:371163:0:371172] Caught signal 11 (Segmentation fault: address not mapped to object at address (nil))
==== backtrace (tid: 371172) ====
0 0x0000000000042520 __sigaction() ???:0
1 0x00000000010d475f createInferRuntime_INTERNAL() ???:0
2 0x000000000107dd42 getInferLibVersion() ???:0
3 0x00000000010808ec getInferLibVersion() ???:0
4 0x0000000001081e32 getInferLibVersion() ???:0
5 0x000000000108220c getInferLibVersion() ???:0
6 0x00000000010b59b1 createInferRuntime_INTERNAL() ???:0
7 0x00000000010b6777 createInferRuntime_INTERNAL() ???:0
8 0x0000000000127022 tensorrt_llm::runtime::TllmRuntime::TllmRuntime() :0
9 0x00000000000809cf tensorrt_llm::batch_manager::TrtGptModelInflightBatching::TrtGptModelInflightBatching() :0
10 0x000000000007099f tensorrt_llm::batch_manager::TrtGptModelFactory::create() :0
11 0x0000000000067222 tensorrt_llm::batch_manager::GptManager::GptManager() :0
12 0x0000000000048cbc triton::backend::inflight_batcher_llm::ModelInstanceState::ModelInstanceState() :0
13 0x0000000000049d62 triton::backend::inflight_batcher_llm::ModelInstanceState::Create() :0
14 0x0000000000039bb5 TRITONBACKEND_ModelInstanceInitialize() ???:0
15 0x00000000001a7226 triton::core::TritonModelInstance::ConstructAndInitializeInstance() :0
16 0x00000000001a8466 triton::core::TritonModelInstance::CreateInstance() :0
17 0x000000000018b165 triton::core::TritonModel::PrepareInstances(inference::ModelConfig const&, std::vector<std::shared_ptrtriton::core::TritonModelInstance, std::allocator<std::shared_ptrtriton::core::TritonModelInstance > >, std::vector<std::shared_ptrtriton::core::TritonModelInstance, std::allocator<std::shared_ptrtriton::core::TritonModelInstance > >)::{lambda()#1}::operator()() backend_model.cc:0
18 0x000000000018b7a6 std::_Function_handler<std::unique_ptr<std::__future_base::_Result_base, std::__future_base::_Result_base::_Deleter> (), std::__future_base::_Task_setter<std::unique_ptr<std::__future_base::_Resulttriton::core::Status, std::__future_base::_Result_base::_Deleter>, std::thread::_Invoker<std::tuple<triton::core::TritonModel::PrepareInstances(inference::ModelConfig const&, std::vector<std::shared_ptrtriton::core::TritonModelInstance, std::allocator<std::shared_ptrtriton::core::TritonModelInstance > >, std::vector<std::shared_ptrtriton::core::TritonModelInstance, std::allocator<std::shared_ptrtriton::core::TritonModelInstance > >)::{lambda()#1}> >, triton::core::Status> >::_M_invoke() backend_model.cc:0
19 0x0000000000197a1d std::__future_base::_State_baseV2::_M_do_set() :0
20 0x0000000000099ee8 pthread_mutexattr_setkind_np() ???:0
21 0x0000000000181feb std::__future_base::_Deferred_state<std::thread::_Invoker<std::tuple<triton::core::TritonModel::PrepareInstances(inference::ModelConfig const&, std::vector<std::shared_ptrtriton::core::TritonModelInstance, std::allocator<std::shared_ptrtriton::core::TritonModelInstance > >, std::vector<std::shared_ptrtriton::core::TritonModelInstance, std::allocator<std::shared_ptrtriton::core::TritonModelInstance > >)::{lambda()#1}> >, triton::core::Status>::_M_complete_async() backend_model.cc:0
22 0x0000000000191dc5 triton::core::TritonModel::PrepareInstances() :0
23 0x0000000000196d36 triton::core::TritonModel::Create() :0
24 0x0000000000287330 triton::core::ModelLifeCycle::CreateModel() :0
25 0x000000000028aa23 std::_Function_handler<void (), triton::core::ModelLifeCycle::AsyncLoad(triton::core::ModelIdentifier const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, inference::ModelConfig const&, bool, bool, std::shared_ptrtriton::core::TritonRepoAgentModelList const&, std::function<void (triton::core::Status)>&&)::{lambda()#2}>::_M_invoke() model_lifecycle.cc:0
26 0x00000000003ded82 std::thread::_State_impl<std::thread::_Invoker<std::tuple<triton::common::ThreadPool::ThreadPool(unsigned long)::{lambda()#1}> > >::_M_run() thread_pool.cc:0
27 0x00000000000dc253 std::error_code::default_error_condition() ???:0
28 0x0000000000094ac3 pthread_condattr_setpshared() ???:0
29 0x0000000000125814 clone() ???:0
[dsw-6138-7785b6c584-qtx6w:371163] *** Process received signal ***
[dsw-6138-7785b6c584-qtx6w:371163] Signal: Segmentation fault (11)
[dsw-6138-7785b6c584-qtx6w:371163] Signal code: (-6)
[dsw-6138-7785b6c584-qtx6w:371163] Failing at address: 0x5a9db
[dsw-6138-7785b6c584-qtx6w:371163] [ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f280198d520]
[dsw-6138-7785b6c584-qtx6w:371163] [ 1] /usr/local/tensorrt/lib/libnvinfer.so.9(+0x10d475f)[0x7f2790b0f75f]
[dsw-6138-7785b6c584-qtx6w:371163] [ 2] /usr/local/tensorrt/lib/libnvinfer.so.9(+0x107dd42)[0x7f2790ab8d42]
[dsw-6138-7785b6c584-qtx6w:371163] [ 3] /usr/local/tensorrt/lib/libnvinfer.so.9(+0x10808ec)[0x7f2790abb8ec]
[dsw-6138-7785b6c584-qtx6w:371163] [ 4] /usr/local/tensorrt/lib/libnvinfer.so.9(+0x1081e32)[0x7f2790abce32]
[dsw-6138-7785b6c584-qtx6w:371163] [ 5] /usr/local/tensorrt/lib/libnvinfer.so.9(+0x108220c)[0x7f2790abd20c]
[dsw-6138-7785b6c584-qtx6w:371163] [ 6] /usr/local/tensorrt/lib/libnvinfer.so.9(+0x10b59b1)[0x7f2790af09b1]
[dsw-6138-7785b6c584-qtx6w:371163] [ 7] /usr/local/tensorrt/lib/libnvinfer.so.9(+0x10b6777)[0x7f2790af1777]
[dsw-6138-7785b6c584-qtx6w:371163] [ 8] /opt/tritonserver/backends/tensorrtllm/libtriton_tensorrtllm.so(+0x127022)[0x7f279f579022]
[dsw-6138-7785b6c584-qtx6w:371163] [ 9] /opt/tritonserver/backends/tensorrtllm/libtriton_tensorrtllm.so(+0x809cf)[0x7f279f4d29cf]
[dsw-6138-7785b6c584-qtx6w:371163] [10] /opt/tritonserver/backends/tensorrtllm/libtriton_tensorrtllm.so(+0x7099f)[0x7f279f4c299f]
[dsw-6138-7785b6c584-qtx6w:371163] [11] /opt/tritonserver/backends/tensorrtllm/libtriton_tensorrtllm.so(+0x67222)[0x7f279f4b9222]
[dsw-6138-7785b6c584-qtx6w:371163] [12] /opt/tritonserver/backends/tensorrtllm/libtriton_tensorrtllm.so(+0x48cbc)[0x7f279f49acbc]
[dsw-6138-7785b6c584-qtx6w:371163] [13] /opt/tritonserver/backends/tensorrtllm/libtriton_tensorrtllm.so(+0x49d62)[0x7f279f49bd62]
[dsw-6138-7785b6c584-qtx6w:371163] [14] /opt/tritonserver/backends/tensorrtllm/libtriton_tensorrtllm.so(TRITONBACKEND_ModelInstanceInitialize+0x65)[0x7f279f48bbb5]
[dsw-6138-7785b6c584-qtx6w:371163] [15] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x1a7226)[0x7f2802389226]
[dsw-6138-7785b6c584-qtx6w:371163] [16] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x1a8466)[0x7f280238a466]
[dsw-6138-7785b6c584-qtx6w:371163] [17] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x18b165)[0x7f280236d165]
[dsw-6138-7785b6c584-qtx6w:371163] [18] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x18b7a6)[0x7f280236d7a6]
[dsw-6138-7785b6c584-qtx6w:371163] [19] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x197a1d)[0x7f2802379a1d]
[dsw-6138-7785b6c584-qtx6w:371163] [20] /lib/x86_64-linux-gnu/libc.so.6(+0x99ee8)[0x7f28019e4ee8]
[dsw-6138-7785b6c584-qtx6w:371163] [21] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x181feb)[0x7f2802363feb]
[dsw-6138-7785b6c584-qtx6w:371163] [22] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x191dc5)[0x7f2802373dc5]
[dsw-6138-7785b6c584-qtx6w:371163] [23] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x196d36)[0x7f2802378d36]
[dsw-6138-7785b6c584-qtx6w:371163] [24] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x287330)[0x7f2802469330]
[dsw-6138-7785b6c584-qtx6w:371163] [25] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x28aa23)[0x7f280246ca23]
[dsw-6138-7785b6c584-qtx6w:371163] [26] /opt/tritonserver/bin/../lib/libtritonserver.so(+0x3ded82)[0x7f28025c0d82]
[dsw-6138-7785b6c584-qtx6w:371163] [27] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253)[0x7f2801c4f253]
[dsw-6138-7785b6c584-qtx6w:371163] [28] /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3)[0x7f28019dfac3]
[dsw-6138-7785b6c584-qtx6w:371163] [29] /lib/x86_64-linux-gnu/libc.so.6(clone+0x44)[0x7f2801a70814]
[dsw-6138-7785b6c584-qtx6w:371163] *** End of error message ***
Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
I0102 12:39:14.735676 371187 pb_stub.cc:1963] Non-graceful termination detected.
I0102 12:39:14.737329 371188 pb_stub.cc:1963] Non-graceful termination detected.
mpirun noticed that process rank 0 with PID 0 on node dsw-6138-7785b6c584-qtx6w exited on signal 11 (Segmentation fault).

一样的，这个是trtion的bug，用llama也是一样，得等下一版triton了！😅

好吧，再请教个问题，开启nflight_batching，需要同时使能remove_input_padding，但使能remove_input_padding，多batch会有问题，这个问题有解吗？

好吧，再请教个问题，开启nflight_batching，需要同时使能remove_input_padding，但使能remove_input_padding，多batch会有问题，这个问题有解吗？

这个不是bug，而是开启inflight-batching后，单次请求只能单batch，由triton那边组织多batch。

懂了，目前有哪个版本的triton镜像和TensorRT-LLM，是可以跑inflight-batching的吗

0.5.0分支配合23.10 triton。

我用23.10 triton编译0.5.0 的TensorRT-LLM会报链接错，请问这是什么问题呢？
[ 98%] Built target kernels_src
[ 98%] Built target tensorrt_llm_static
[100%] Linking CXX shared library libtensorrt_llm.so
/usr/bin/ld:../../tensorrt_llm/batch_manager/x86_64-linux-gnu/libtensorrt_llm_batch_manager_static.pre_cxx11.a: file format not recognized; treating as linker script
/usr/bin/ld:../../tensorrt_llm/batch_manager/x86_64-linux-gnu/libtensorrt_llm_batch_manager_static.pre_cxx11.a:1: syntax error
collect2: error: ld returned 1 exit status
gmake[3]: *** [tensorrt_llm/CMakeFiles/tensorrt_llm.dir/build.make:715: tensorrt_llm/libtensorrt_llm.so] Error 1
gmake[2]: *** [CMakeFiles/Makefile2:677: tensorrt_llm/CMakeFiles/tensorrt_llm.dir/all] Error 2
gmake[1]: *** [CMakeFiles/Makefile2:684: tensorrt_llm/CMakeFiles/tensorrt_llm.dir/rule] Error 2
gmake: *** [Makefile:179: tensorrt_llm] Error 2
Traceback (most recent call last):
File "/mnt/workspace/zsf/code/TensorRT-LLM/Qwen-TensorRT-LLM-v0.5.0/tensorrtllm_backend/tensorrt_llm/./scripts/build_wheel.py", line 248, in
main(**vars(args))
File "/mnt/workspace/zsf/code/TensorRT-LLM/Qwen-TensorRT-LLM-v0.5.0/tensorrtllm_backend/tensorrt_llm/./scripts/build_wheel.py", line 152, in main
build_run(
File "/usr/lib/python3.10/subprocess.py", line 526, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: C

/usr/bin/ld:../../tensorrt_llm/batch_manager/x86_64-linux-gnu/libtensorrt_llm_batch_manager_static.pre_cxx11.a: file format not recognized; treating as linker script明显是没有用git-lfs拉取大文件下来。
顺便说一句：23.10不用编译trt-llm，可以直接pip安装。
可以参考下面的教程：
https://zhuanlan.zhihu.com/p/664545577

0.5.0分支配合23.10 triton。

跑起来了，感谢大佬

恭喜

repo: Tlntin/Qwen-TensorRT-LLM


text:
Register pytest markers and upgrade pytest

Registering the markers used by pytest helps to prevent typos, as unknown markers in newer versions raise a warning.
https://docs.pytest.org/en/latest/mark.html#registering-marks

Coverage remained the same at 82.497% when pulling 0243b04463f612d38549a47957d05630412306a2 on snorfalorpagus:markers into 32eeb62cd97acd191fe8434e2fde9d934efa7226 on Toblerity:master.

Fantastic. Thanks, @snorfalorpagus !

This MR broke the appveyor build. Something to do with an older version of argparse but I haven't managed to reproduce it locally yet.

@snorfalorpagus  There is a similar bug report in the pytest issue tracker: https://github.com/pytest-dev/pytest/issues/5594
Maybe something is odd with our Python setup on appveyor.

I think the reason is that we install the argparse library with requirements.txt. Dropping this requirement fixes this issue. I think this should not be a problem as we won't support Python < 3.5 with Fiona 2.0 and argparse is in the standard library after Python 3.2.  To be safe we could add
argparse==1.4.0 ; python_version <= '3.4'
(From https://pypi.org/project/argparse/ I assume the separate argparse library provides bugfixes up to 3.4)
It's strange that the error is not present on travis.

authors: coveralls rbuffat sgillies snorfalorpagus

repo: Toblerity/Fiona


text:
Running the docker-compose for the given repo doesn't work

I have cloned this repo and trying to run the sample application as it is in docker. Upon running "docker-compose up" the container for drkiq database gets exited at start and the application is not running at expected.
Logs are given below
sudo docker logs 039dad81986b
I, [2022-03-07T18:47:58.460070 #7]  INFO -- : Refreshing Gem list
I, [2022-03-07T18:47:59.290132 #7]  INFO -- : listening on addr=0.0.0.0:8010 fd=13
E, [2022-03-07T18:47:59.363708 #7] ERROR -- : FATAL:  database "drkiq" does not exist
 (ActiveRecord::NoDatabaseError)
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/postgresql_adapter.rb:50:in `rescue in postgresql_connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/postgresql_adapter.rb:33:in `postgresql_connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:887:in `new_connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:931:in `checkout_new_connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:910:in `try_to_checkout_new_connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:871:in `acquire_connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:593:in `checkout'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:437:in `connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:1119:in `retrieve_connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_handling.rb:221:in `retrieve_connection'
/usr/local/bundle/gems/activerecord-6.0.3.4/lib/active_record/connection_handling.rb:189:in `connection'
config/unicorn.rb:30:in `block in reload'
/usr/local/bundle/gems/unicorn-5.5.5/lib/unicorn/http_server.rb:542:in `spawn_missing_workers'
/usr/local/bundle/gems/unicorn-5.5.5/lib/unicorn/http_server.rb:144:in `start'
/usr/local/bundle/gems/unicorn-5.5.5/bin/unicorn:128:in `<top (required)>'
/usr/local/bundle/bin/unicorn:23:in `load'
/usr/local/bundle/bin/unicorn:23:in `<top (required)>'
/usr/local/lib/ruby/2.7.0/bundler/cli/exec.rb:63:in `load'
/usr/local/lib/ruby/2.7.0/bundler/cli/exec.rb:63:in `kernel_load'
/usr/local/lib/ruby/2.7.0/bundler/cli/exec.rb:28:in `run'
/usr/local/lib/ruby/2.7.0/bundler/cli.rb:476:in `exec'
/usr/local/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/local/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/usr/local/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor.rb:399:in `dispatch'
/usr/local/lib/ruby/2.7.0/bundler/cli.rb:30:in `dispatch'
/usr/local/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/base.rb:476:in `start'
/usr/local/lib/ruby/2.7.0/bundler/cli.rb:24:in `start'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/libexec/bundle:46:in `block in <top (required)>'
/usr/local/lib/ruby/2.7.0/bundler/friendly_errors.rb:123:in `with_friendly_errors'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/libexec/bundle:34:in `<top (required)>'
/usr/local/bundle/bin/bundle:23:in `load'
/usr/local/bundle/bin/bundle:23:in `<main>'

Any help would be highly appreciated.

Hi, you need to run the db creation command:
$ docker-compose run drkiq rake db:reset
$ docker-compose run drkiq rake db:migrate

You can find the full tutorial here: https://semaphoreci.com/community/tutorials/dockerizing-a-ruby-on-rails-application

repo: TomFern/dockerizing-ruby


text:
CodeArea styling issue

I set my CodeArea background color to black, this means that I'm typing "in the dark" until my highlighting logic catches up. I'm borrowing very heavily from the Async example.
I added this so that the text will show up as something visible right away:
.styled-text-area .text {
    -fx-fill: purple;
}

However, now the problem is that my StyleSpans for color is being overriden by this one. I'm not savvy enough to figure out how to fix this by somehow tweaking the passed in styling classes to be more specific. How should I address this?

Hi, if your style class is highlight, then this should do it:
.styled-text-area .text.highlight {
    -fx-fill: yellow;
}

Note the lack of whitespace between .text and .highlight.

awesome, great, that worked.

authors: TomasMikula jtrunick

repo: TomasMikula/RichTextFX


text:
Secure way to transport the log.csv [Generated by detector.py]

Is there a part where i could validate the Trained model.

Is there any secure way to transport the log.csv from infected machine to the analysis VM. Making sure that the ransomware doesn't infect or corrupt the log.csv file.

Hi Motti, apologies for the late reply, appears that I didn't have notifications on for issues. Hope I'm not too late. Indeed, the transportation of the log.csv from the infected machine is a limitation of this research. I would argue there is no risk-free way to do this, but you can minimize risks by comparing hashes (which, as you will know from this research, you should definitely not trust), open contents in a sandboxed VM (a .csv file is not an executable, you can see even from the hex that it should be a legitimate file and not infected), etc. Feel free to develop your own methodology.
It's quite unlikely that these files would be targeted for infection, although they could be modified. In the end it will always be like the research states - a "cat and mouse game".
Although I can't provide a direct "correct" answer to your question, I hope this allows you to hypothesize and think of methodologies to do this part of the process.

authors: MottiKumar TomasPhilippart

repo: TomasPhilippart/ebpfangel