Windows distribution problems with löve - cannot load module libcurl.

After downloading the libcurl.dll (with SSL support) that is linked in the readme and putting it next to my love.exe, the library works right away for me. But for three out of three friends that I asked to try it too, everyone gets the error:

msg = string: "luajit-request/luajit-curl.lua:28: cannot load module 'libcurl': Das angegebene Modul wurde nicht gefunden.\13\

I made sure that love.exe is 32-Bit, just as libcurl.dll. Dependency walker tells me that libcurl.dll has three dependencies: zlib1.dll, ssleay32.dll and libeay32.dll, which I hoped would be included in libcurl.dll. But just to make sure, I searched them from other places on my computer and put them next to the exe too. Then I got a "missing ordinal 4445 in dll" error instead, most probably because their versions do not match, but maybe that's a lead? I also tried setting PATH and LUA_CPATH to the directory of the .dll and I passed a full absolute path to the dll to ffi.load instead, but I still get the error I mentioned in the start of this issue.
I would guess that most people will have trouble using the library, because everyone else seems to be having the problem.

It turns out the only working version of libcurl.dll I have found so far that works on all computers tested is the one linked here: https://curl.haxx.se/download.html
(Win64 Generic - Win64  x86_64  CAB | 7.54.1 | binary | SSL - link: https://skanthak.homepage.t-online.de/download/curl-7.54.1.cab) I don't what's going on with the other ones, but maybe you can update the link in the readme?

Good catch, just like your other issues!
I have this fuzzy memory that the haxxe.se links didn't have Windows binaries whenever I wrote that README, or at least not with SSL support built in?
I'll update the README!

README has been updated to point to those binaries instead, thank you!

It's a pleasure! I'm really thankful you made this and if I can contribute only by complaining, I'll gladly take it :D

Data point for future visitors:
I tried getting the latest binaries out of haxx.se, but they did not work for me. I just got a lot of the following.

When I used the old one linked above, it worked fine.

(Win64 Generic - Win64 x86_64 CAB | 7.54.1 | binary | SSL - link: https://skanthak.homepage.t-online.de/download/curl-7.54.1.cab)

(I'm using Love2D 11.3.0)


How to visualize the loaded staticmesh of object?

My code is as flows, i use LoadMeshToStaticMesh to load .obj and .mtl file.
It encounters no error, but the object is not visuable in when play.
I spend 2 days to try visualizing the static mesh, but get no answer.
ALoader::ALoader()
{
 	// Set this actor to call Tick() every frame.  You can turn this off to improve performance if you don't need it.
	PrimaryActorTick.bCanEverTick = true;
	ShitMesh = CreateDefaultSubobject<UStaticMeshComponent>(TEXT("Mesh"));
	RootComponent = ShitMesh;

	ShitMesh->SetMobility(EComponentMobility::Movable);
}

// Called when the game starts or when spawned
void ALoader::BeginPlay()
{
	Super::BeginPlay();

	FVector Position;
	Position.X = 300.0f;
	Position.Y = 20.0f;
	Position.Z = 100.0f;

	FRotator Rotation;
	Rotation.Yaw = -33.0f;
	Rotation.Pitch = 32.0f;
	Rotation.Roll = 0.0f;

	FString path = TEXT("/Users/aa/Documents/Unreal Projects/Fproject/Content/Developers/models/drill.obj");
	auto aaloader = NewObject<ULoaderBPFunctionLibrary>();
	drill = aaloader->LoadMeshToStaticMesh(RootComponent, path, EPathType::Absolute);
	ShitMesh->SetStaticMesh(drill);
	ShitMesh->SetWorldLocationAndRotation(Position, Rotation);
}

the object is too small to be see. Scale the object will do.

the object is too small to be seen. Scale the object will do.


[BP-738] Add PayRemainder action to Paypal payment method Order TransactionBui…

…lder

@mgroensmit can you please open the PR against develop branch, in order to fit our development and release process?

@mgroensmit I added some notes about how to contribute, you can find them here
The main idea is that you branch from develop and open a PR against develop.

Makes sense, I'll do that.


does not show an alternative translation when the language is empty

hello, I installed your plugin because I had some problems with gutenberg, but I ran into a problem that when switching to a second language where there is no translation yet, the content is not shown.
(checkbox) Show post content in an alternative language when translation is not available for the selected language.
When a page or a post with an untranslated content is viewed, a message with a list of other available languages is displayed, in which languages are ordered as defined by option "Default Language / Order". If this option is on, then the content of the first available language will also be shown, instead of the expected language, for the sake of user convenience.
using 'ACF blocks' latest version and wp 5.9.3.
Has anyone else encountered this issue and found a way to fix it?
Thank you!

Hello, I did not quite understand your problem ... You may have encountered the situation that I just did not check or did not expect.
Could you describe what happens in more detail? Unfortunately, the phrase "ran into a problem that when switching to a second language where there is no translation yet, the content is not shown" did not help me much.
What will help me:

the raw content of the document that you edit (with QTX blocks  - [:en] and etc)
Screenshot to show how it looks on the screen (what happened)
your description how it should look


Possibility to add postRenderers to extraRoutes

🧩 Feature request
Description
Hi there !
Thank you for Scully !
I'm working on an Angular App, with the Router and Scully, but not with the default urls provided by route configuration.
Thanks to Angular UrlSerializer, I can get some nice SEO friendly urls coming from a CMS (Drupal), mapped to an internal Angular route. So my app works well with both urls, the technical angular ones and the content oriented Drupal ones.
When I render Scully, I ask Drupal for all the paths of my contents thanks to extraRoutes, and it works well.
I'm using :
<EMAIL_ADDRESS><EMAIL_ADDRESS>Describe the solution you'd like
The problem/question I try to solve is that I would like to use the FlashPreventionPlugIn to test it and see if it improves my rendering or not. With ExtraRoutes I don't see how to do it. I tried to add the plug-in in defaultPostRenderers property but it doesn't work.
Do you have an idea how to do it ?
Describe alternatives you've considered
Instead of returning an array of url as string, return a map, with the url as key, and an object as value, like the routes ones. I don't know if it is a good idea ;-)

Exrtaroutes are just added to the unhandled route list, so they are not different from any other route Scully tråvereses.
Adding the flashprevention to the defaultPostRenderers should do the trick.
I would need to have access to a way to reproduce your issue, so I can work on fixing it.

Ok, thank you @SanderElias , I'll try again to add flashprevention defaultPostRenderers and let you know here.

Hi @SanderElias,
I could add the scully-plugin-flash-prevention in defaultPostRenderers config and it works well. I'm almost sure I add a problem doing it earlier. Maybe it was due to older version of Scully.
Thank you!


Fix sample directory link in README

The sample directory has changed from "samples" and the links in the README are pointing to a 404 now

I signed it!

Good catch! Thanks for the pull request! :+1:


Enhancement: Make underlying injector accessible from library

While integrating Flask-Injector I stumbled among a few cases where retrieving my injector-managed instances using dependency injection is not feasible. For example, I might have code like the following
@app.route("/foo")
@cost_center
def foo(db: sqlite3.Connection):
    users = db.execute('SELECT * FROM users').all()
    return render("foo.html")

where cost_center is some function-based decorator that measures runtime stats about the respective route and uses a request-scoped Stats-Collector to solve this task.
So far I think the best way to implement this is to give access to the underlying injector used by Flask-Injector itself, i.e. injector.get(StatsCollector, scope=request). Since this requires the developer to manage separate access to the injector, it would be nice if Flask-Injector could support this use-case directly instead.
Given the current architecture, I am not sure whether there is a clean approach to this. At least I wanted to document this might be a valid use-case.

I'm not sure why is using dependency injection here not feasible. I've done it in the past using the following pattern, but maybe it's not acceptable in your case (just off the top of my head, may not run without some changes):
def cost_center(function):
    @functools.wraps(function)
    def wrapper(*args, **kwargs):
        collector = kwargs.pop('__cost_center_collector')
        # use collector here
        return function(*args, **kwargs)
    # Dependency injection happens based on type hints, so if we return a wrapper with
    # an extra annotation we'll get an extra dependency injected.
    wrapper.__annotations__['__cost_center_collector'] = TheCollectorClass
    return wrapper

Wow, it took me some moments to get what's happening here... brilliant! Thank you very much..

No worries. I'll keep in mind this may be mentioned somewhere in the documentation, could come in handy. :)


redirects to connectENV if ENV is DOCKER

redirect to connectENV if ENV is DOCKER

looks good to me. What happens if ENV is not set?

if ENV is not set. we proceed to make the call via the RDS_PROXY_ENDPOINT.
I have pushed up a change, that defaults ENV to "DOCKER" if not set. This is assuming other envs (such as PROD, DEV) return the relevant ENV (which I assume is the case, given this line: https://github.com/Pennsieve/pennsieve-go-core/pull/28/files#diff-008a6d91ac50c4d58e86c312eeb971b894835ae427237a2e03acdcb5b5a2bd01R77)


etherscan api key not used

Hey,
thanks for this module. While reviewing the code I noticed that there seems to be no usage of the etherscan api key. So it won't be used at all, is that right? I assume it still works, because etherscan is kind of lazy about api key usage, though.
Best,
Caspar.

Hey Caspar. The latest master is using Infura nodes instead of Etherscan, that's why there is no API key usage. Need to update README 😅
If you want to test against Ethserscan, you can use the previous version: https://github.com/leapdao/eth-node-healthcheck/tree/v1.0.2 (published on npm just now)

I've updated README to conform with latest code (published as 1.1.0). Hope it helps

Hey troggy,
thanks for the quick reply. All good then!


Add actual dates to lecture 1

Currently lecture 1 has xs for the dates of the exams

dealt with in #41


Remove docs server in Play! 2.6.x when running in dev mode

Documentation server was removed from development mode in version 2.6.0-M4 (see pull request and a commit).

New 1.0.0-beta8-SNAPSHOT snapshot deployed.


E2's array/quat/vec2/vec/vec4 types are immutable, except for one tiny place

#411 added mutability to these types, which were never supposed to be mutable. This mutability causes bugs: in the following code snippet, Array and Table (which are intentionally mutable types) will update when In does, but Vector won't.
@inputs In
@outputs Array:array Table:table Vector:vector
Array[1, number] = Table[1, number] = Vector[1] = In

It also means that table cloning is less efficient and the optimizer will have a harder time optimizing code blocks that manipulate vectors.
@Divran @bigdogmat @TomyLobo thoughts? What if the E2 compiler issued a warning on those setters for a few months before we removed them?

This has been complained about before in #1348.

I think the operator is good, but it does need to trigger ouput vectors.

I believe this was fixed already. Need to check

Fixed by https://github.com/wiremod/wire/pull/2315


[Fix] Fix for SUN RGB-D, when creating .pkl files

When reading calibration files, both Rt and K are being stored as Rt values only. This should fix the issue.

 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.

Related to issue #507

Hi @virusapex ,
Thanks for your kind PR. Would you like to sign the CLA thus we could merge it?

Hi @virusapex ,
Thanks for your kind PR. Would you like to sign the CLA thus we could merge it?

Done, @ZwwWayne ! Sorry for the delay.

Hi!
@virusapex
First of all, we want to express our gratitude for your significant PR in the OpenMMLab project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


feat($q): manage bulk promises as a promise

As $q.all() reject with a first rejected promise, $q.some() proceed execution until all promises
are rejected or resolved. It can be useful for independent bulk promises.
No breaking changes.

Given that Angular 2 is moving to ES6 Promise and given that this can be implemented using a third party library, I am closing this issue


Collage, Container, Datapoint, Fieldset, Heading: use generated props tables

Refactor docs to use generated props tables: Collage, Container, Datapoint, Fieldset, Heading
Also, removed unneeded React imports (probably from an older version of the scaffolding script)


Update bootstrap-datepicker.js

Updated z-index functionality in "place" function to check for explicit z-index set through stylesheet. Current func. retrieves z-index based on DOM stack. In some instances you might want to specify the z-index through a CSS class instead. Updated func. will first reset picker z-index and check for z-index set via stylesheet. If not-specified, DOM stack is used.

@CheapSk8 can you rebase your PR against the current master?

ping @CheapSk8

Sorry, I have been away on a project. I just merged the latest master down and am going to see if I can fire up my test app again and test this.

I updated and resubmitted as #1419

I have a situation where a sibling element (not parent) is absolutely positioned.  In this rare case, hardcoding the z-index with !important works i.e.
.datepicker-dropdown {
  z-index: 1036 !important;
}

Since !important works, it could be argued that this pull may not be needed.  On the other hand, many people don't know about !important, so this pull request is helpful.   Either way, I wanted to note my current workaround for the case of overlapped absolutely positioned components that are not in the same stack.


Add version log message to main init

Add an info level log statement about the import of plottr. This is useful for readers of the log messages to track versions.
@jenshnielsen, @wpfff

@WilliamHPNielsen this breaks since there is a module called log within the top level of plottr


set container times to ET (logs, cron)

https://stackoverflow.com/questions/57607381/how-do-i-change-timezone-in-a-docker-container

set for crond


Fire events for directory creation/deletion

Prerequisite #6069, otherwise these will be untrustworthy
Design and implement events for the creation and deletion of subdirectories.
Also consider that the scenarios in which events are suppressed may be more complex than for key set/delete since the contained values of the subdirectory could end up different.  The logic is more complex than "last write wins", which is part of what #6069 needs to address.  One example:

ClientA - create subdir "foo"
ClientB - create subdir "foo"
ClientA - set key "foo/keyA"
ClientA - delete subdir "foo"
ClientA - create subdir "foo"
ClientA - set key "foo/keyB"
All of ClientA ops get sequenced
All of ClientB ops get sequenced

Expected eventually-consistent result is that both clients see subdirectory "foo" with a key "keyB".  ClientA's events seem fairly straightforward (probably just ignore the superfluous creation from B when it gets sequenced), but it's less obvious to me what events ClientB should see and in what order.

Probably bad:  ClientB sees no events for ClientA's create/delete.
ClientB would have no clue that "foo/keyA" is now gone.  This is the status quo given the currently LWW approach for subdirectories.
Probably bad:  ClientB gets events from ClientA's create/delete but cannot distinguish them from the scenario where they have no outstanding create of their own.
In this scenario ClientA's delete should only delete the ack'd contents of "foo" -- from ClientB's perspective "foo" should still exist locally (it is still awaiting its own create to be ack'd) and also any unacked contents ClientB may set (which will be sequenced after their own create).  Whereas if ClientB had no outstanding create of its own, ClientB would immediately see "foo" get deleted.  So, ClientB probably wants to know if "subDirectoryDeleted" actually deleted the subdirectory, vs. if it's actually still there due to a pending op.  Or at minimum, we'd need to specify that "subDirectoryDeleted" might not mean the subdirectory was actually deleted and that customers should inspect to see if its still there.

ClientA's events seem fairly straightforward (probably just ignore the superfluous creation from B when it gets sequenced)

I'm not sure on that. I.e. I'm not sure it's the conclusion I'd jump right away as I think creation (with semantics we have today) is the source of the problem.
For example, if creation op always wipes out content of existing sub-directory with same name AND every op (including creation) mentions identity of sub-directory instance (guid assigned at creation), then

all ops for "another" instance of sub-directory with same name are easy to ignore (if latest state has different guid).
creations are not coalesced, last one wins, another one loses, and all the ops for that loser will be ignored.

Basically, it's the same problem as assigning alias / name to root data store. Either need synchronization or overwrite semantics.
I think other solutions are possible here (with tracking more state for in-flight ops) to make it eventually consistent, but I'm not convinced it will result in something user wants. I.e., if clients operating on sub-directories likely expect certain structure (certain keys filled in on creation of sub-directory to be always there) and would be very surprised to find no such structure (and just a single key) if one client deleted sub-directory concurrently with another client changing single key in such sub-directory (latter ordered last). So, I think clients would prefer sub-directories to have identify that is defined not just by its name (but also includes guid assigned at creation).
I have not though about it, but maybe it's possible to support other types of creation disposition (see dwCreationDisposition in CreateFile), it's just that CREATE_NEW type of creation disposition (what we have today) likely requires synchronization and different modes likely can't be used on same name / directory (i.e., it's impossible to describe how they compose). So maybe (in some distant future) we will decide to support different modes for directory as a whole (mode fixed at creation).
P.S.: It's interesting that win32's CreateDirectoryEx does not provide same abilities to RE controlling creation disposition modes.
+@nanorga +@jatgarg
Also +@DLehenbauer for thoughts on how other DDSs (Shared/Property Tree) approach same problem of sub-tree identity management

The CreateDirectoryEx, returns error code on creation of another directory with same name. So we can consider following the same structure or probably not if this does not serve the requirements of apps.
I do the like the idea of introducing guid for subdirectories so that we can separate ops for those as in if User1 creates subdirectory foo and then user 2 creates another foo and then user 1 deletes foo that he created then after all the process we will still have foo that user2 created with a different guid. This does for other operations too. But  currently for ex. the getSubdirectory() takes name as input to return the corresponding subdirectory. But after allowing same name subdirectories with different guid, would we be passing guid along with name as input?

For our usage, I don't see any issues with the "overwrite on create" proposal.
The most common scenario we have where something will be removed then re-added with the same key is undo and redo. My expectation is that the 'redo' operation will boil down to us re-adding each item in the subdirectory one-by-one, so starting from a 'blank' slate is perfectly fine.
I think solutions where we try to resolve conflicts by merging subdirectories together will be overly complex and prone to all kinds of problems.
Our directories behave like the C++ objects they represent. If we create/allocate a new object in C++, we proceed to set all its members. If a new one is created, the old one is freed and the new one takes over and all its members are again initialized.

Thanks Nate! I'll point out that redo (in your example) will wipe out changes from other clients in between undo & redo (if they created same sub-directory). But I think it should not be resolve at that level.
If we go with "overwrite on create" proposal, then I see 3 options RE how it's implemented:

Can we leverage existing map / directory logic here somehow? Are there any other simpler ways of achieving same thing?
Each directory op has new "identity" property - uuid uniquely identifying instances of sub-directory, in addition to keeping path property. Summaries need to also store uuid of each sub-directory. Each client implements LWW by tracking local "lie" (uuid for create/delete operations) until its ops are acked, as well as current (acked) uuid for each sub-directory.

con: bigger op sizes

Same but remove path from op payload to reduce payload size.

pro: smaller payload sizes
con: need to track uuid -> path mapping on each client (as well as un-acked local changes) and rebuild mapping on load. But do not need to track per-client info, only acked state and local (this client) state. All ops for unknown uuids are ignored.

Each client tracks (path, seq#) -> uuid (changes on sub-directory create & delete), and (path, ref seq#, clientId) -> uuid (changes as client creates or deletes sub-directories, and when client's ref seq# moves forward) to be able to calculate uuid for each path + client combo at any moment in time. Same info is written to summary, of course. No changes in op payload size, as identity (uuid) can be recalculated on each client individually.

pro: exactly same op payload
con: much more complicated and error-prone code.

Note: Opened #8938 to consider using more compact version of uuid generation.
I'd go with # 2 initially (as it seems like the most trivial to implement), followed by # 3 (as a way to compress payload sizes).
I feel like # 4 is the ideal, but a bit too complicated solution. That said, if there is any way to reuse code and get # 4 out of existing building blocks, or produce common building blocks that can be reused later in other DDSs, I'd consider it.
Note that we also need for sub-directory to throw some error when in-memory objects are used after it was deleted.

Just FYI - Vlad's suggestions are progressing down the same evolution as SharedTree (ids on every mode, using id's exclusively in ops, compressing the ids, and then eventually switching to paths with sophisticated rebasing in order to partition edits without maintaining the id maps in memory.)
The other interesting point in the design space is the 'Git' like approach of implicitly creating/destroying directories based on if they contain items.  Concurrent insertion of different keys under the same new path will implicitly create identical directory structure and the keys at the leaves merge with LWW semantics.  If you desire 'id' semantics, you use compound paths like '/name/uuid/', which is a bit yucky, but also a familiar technique from file systems.

I thought about implicit creation, but then directory becomes pretty much a map :)
We would still likely want to have "delete sub-directory" primitive, which would have pretty much same issues as today (what happens if sub-directory delete happens at the same time as another client changes a key?), resulting either in orphan keys, or a need for some kind of serialization on app side to avoid running into such cases. So, I'm not sure it's great solution.
Possible solution in this space - separate existing "set of modify key" primitive into three primitives - "create or overwrite key", "modify if exists key" and "delete key" primitives (later can potentially be merged with second one). That way we can give developers more control to create content in one go (using first primitive), and then leverage second primitive to keep making changes to keys until sub-directory is deleted. It assumes that new keys are not added after initial creation.

@nanorga, please glance at my last reply RE potential alternative.
I think we still prefer to overwrite on create for sub-directories, but worth considering alternatives before committing.
@ChumpChief - would be great to hear your thoughts on proposed direction.

Given amount of content in this issue, I'll repropose it to track eventual consistency issue, not events.

@vladsud - Distinguishing 'set' (update or insert) from 'replace' (if unchanged) is good.  Share.js and others make the same distinction.
I'd suggest the verb 'clear()' instead of 'deleteSubDirectory()', where removing all keys implicitly removes the directory.  As you say, clear() would cause a subsequent 'replace()' to fail, while 'set' would implicitly re-create the directory by repopulating it.
I agree with #8969, where you state that the directory events should be a reflection of local state changes.

I have some second thoughts here. Mostly due to two things:

main solution  proposed earlier is complicated and hard to explain.
It uses a combination of LWW (last writer wins) and FWW (first-writer-wins) for different kinds of interactions, which is not consistent (LWW for keys, and FWW for nodes).

Sidenote: I do not think we ever examined LWW rule across framework and if FWW (in case of conflict, i.e. client not observing other changes) is a better overall strategy, as it gives the looser obvious point to recover (re-merge). And we (today) use combination of LWW & FWW across repo, which is obvious inconsistent, and likely will likely result in very interesting bugs.

Here is one other possible solution in this space:

We use LWW rule across the board, including creation / deletion of sub-directories.

One important exception: an op that sets the key in sub-directory that does not exist (at the time when op is sequenced) results dropping this op on the floor.

Create sub-directory overwrites previous content of sub-directory (exposed as delete + create events, if sub-directory already existed).
We issue disposed events for sub-directories and abandon this instance (in-memory), and if sub-directory is recreated, it's a new im-memory object.

This is much simpler implementation, but it pushes some responsibility to users. I.e. I'd expect creation and initial population of sub-directory to happen in one batch, to ensure that all that activity is handled together (goes through and overwrites whatever content was there, no partial execution).
1b & 3 can be modified to add strict LWW, and thus implicit directory creation on any key change. But this makes it really hard to leverage directories and keep app level constraints (sub-directory either does not exists, or fully initialized and its content makes sense from app perspective), and likely requires "set" and "replace" semantics for key changes as mentioned in earlier comment.

Put summary of discussions in first description for easier navigation

so i've briefly skimmed this. My 2cents are that directory should be a simple dds, and basically a map but with a slightly nicer api that lets you get partitions (directories). Thes partitions(directories) can be passed around, and to consumers it just looks like they have a map. To me this is option 1, directories implicitly exist if they have keys, and do not if they do not have keys. The api can still support getting or holding am empty directory, but it is just an in-memory construct.
I don't understand the need to separate "set" and "replace", this seems like unnecessary complexity. If we absolutely need the ability to make a directory empty rather than clear, i'd consider something like #8690 (obliterate).  Obliterate would operate on operations it hasn't seen. Basically, all map operations with a ref seq below the sequence number of the obliterate op would be ignored.

Thanks Tony! I've updated description in original post with a bit more cases based on our offline discussion.
obliterate and replace are very similar in nature as they essentially provide FWW resolution. The shape might be different - it can CAS (compare-and-swap), limited CAS (replace if undefined), or something similar. The only difference I see is how such primitive interacts with LWW operations (set). While it's important, I'd think that most users would need to use either LWW or FWW resolution for a key (and not mix them, other than maybe initialization if it does not matter there), and thus I find it less interesting (when making decisions on which way to go). That said, I find CAS kind of primitives easier to reason (and how they interact with LWW operations), as that's how shared memory works in multi-threaded world, and thus there is a lot of experience / research to tap here.

The first above scenario seems to assume that directories are real things that can be created and removed, but i'm not sure we need that.  If it was useful there could be events that say directory foo has keys, and directory foo does not have keys at any particular time based on the local state, b is still allowed to have a local instance whether is has keys or not. Then the problem becomes what operations can be done on keys, rather than what operations can be done on directories. This seems like a simpler model to me.

so looking at the directory code. it looks like it has existing ops for directory operations. it also looks like the real issue is the second scenario. I think this can be pretty easily fixed my appropriately managing sequence numbers. Basically, on create the dir gets a seq, and only sets after that seq apply, those below that are just dropped on the floor. you can also allow coalescing creates.
Are we trying to redesign it, or just fix it?

Just fix it :) And yes, I'm gravitating toward # 1 (virtual directories).
I believe your last post is describing solution # 2 or # 3. I.e., depending on how overlapping creates, create + delete compose (LWW or FWW), it's hard to say what exactly you mean. sets are easier, as it's somewhat expected that if two clients concurrently created and populated sub-direction in one batch, then only one set of changes will survive (not merge of those changes).

if i were just going to fix it i'd do something like this (super hacky and untested proof of concept):
https://github.com/microsoft/FluidFramework/compare/main...anthony-murphy:dir-fix
basically, dirs need a create seq and only actions above the create seq or by the create client are allowed to go through. it's very similar how we coalesce deletes in merge tree, only this coalesces inserts. there would need to be a bunch of work to handle detach and emit the appropriate events on the appropriate clients. I need to think more, but i think we really only need to track the sequence client meta data for create. once the dirs create seq drops below the msn, we can throw that data away.

@anthony-murphy "basically, dirs need a create seq and only actions above the create seq or by the create client are allowed to go through. it's very similar how we coalesce deletes in merge tree, only this coalesces inserts."
Does this mean that creating a sub directory which already exists would be a noop and then any modifications by any client on that subdirectory would merge the changes(i.e. work on same subdirectory)? So I am assuming it will be called as FWW for creation of subdirecotry?

https://dev.azure.com/fluidframework/internal/_workitems/edit/512


[Proposal] SOAR-0012 Generate enums for server variables

Motivation
As requested by @czechboy0 in #618 I have created this proposal for community feedback.
Modifications
Added the proposal.
Also fixed a typo in the document for the proposal process.
Result
N/A
Test Plan
N/A

Looks good overall, almost ready to go into review. Could you just slightly elaborate on the behavior with the feature flag enabled/disabled in the API stability section? Right now it sounds like it could be API breaking even for folks who don't opt-in, which isn't the case.

Whoops, SOAR-0011 is already taken, please use SOAR-0012 :) #626

Fixed :)

Looks good overall, almost ready to go into review. Could you just slightly elaborate on the behavior with the feature flag enabled/disabled in the API stability section? Right now it sounds like it could be API breaking even for folks who don't opt-in, which isn't the case.

Done :)


add in dockerfile why which is needed

which is missing in CentOS and its needed for maven to work properly

@rasheedamir Image is available for testing. docker pull docker.io/stakater/maven-centos:7-1.8-3.5.4


[BUG] Some sensor have wrong scale

Version of the custom_component
0.12.1
Describe the bug
Readout of HEATER_PRESSURE seems to be wrong calculated / scaled.
It reads out via integration to: 0.15 bar but in reality and readout directly via modbus register
      - name: "LWZ DRUCK-HEIZKREIS"
        slave: 1
        address: 13
        input_type: input
        unit_of_measurement: bar
        device_class: pressure
        scale: 0.1
        precision: 1

reporting 1.5bar.
Same with VOLUME_STREAM
      - name: "LWZ VOLUMENSTROM"
        slave: 1
        address: 14
        input_type: input
        unit_of_measurement: l/min
        scale: 0.1
        precision: 1

Can confirm that VOLUMENSTROM and DRUCK-HEIZKREIS are now at correct scale! Thanks!


Migrate JAX internals to builtin Python logging

This commit changes the JAX codebase to use Python's builtin logging instead of ABSL logging. With the latter being used in JAX code as of now, the change to Python builtin logging is advised for the following reasons (among others):

absl-py can be removed as an external dependency of JAX.
Builtin logging brings the option of adding more log handlers, for example file handlers for log dumps or writers to different IO streams.

Logging in JAX is ported over to take place at the module level. While previously, some Python namespaces within JAX already used module-scoped logging via absl.vlog, the following idiom was adopted to provide the same functionality in Python builtin logging:
logger = get_logger(__name__)
logger.debug(...)
logger.info(...)

This way, all log messages emitted from JAX contain their origin information directly within the logger name. Furthermore, the builtin root logger is left untouched, which is beneficial for downstream users planning to customize the Python root logger.
The package absl-py was removed from JAX's install requirements, and added into its test requirements. Tests are not yet migrated in this change.
Fixes #6308.

Tests are not yet migrated in this change.

There's no point migrating the tests anyway really, since the tests have a hard absl-py dependency for other reasons anyway (e.g., they use absltest). That's fine, they are tests after all.

Thanks for the comments, I'll update the vlog situation and the commit message accordingly.
What do you think about adding optional config flags for log dumps (similar to XLA dumps via XLA_FLAGS) and setting the Python logging verbosity inside get_logger? I didn't include them yet, but it might be an easy way to influence JAX-wide logging in a single setting.

Well, I'm not necessarily opposed to adding a config flag, but it would have to improve over:
import logging
logging.getLogger("jax").setLevel(logging.DEBUG)

which is pretty good as is. So I'd be inclined to err on the side of not adding anything for the moment.

I think I'd be tempted to promise/document that JAX will log under the "jax" logger (and nested loggers) and let everyone use the Python APIs as they see fit.

Changes after your comments:

Set vlog -> logging.debug everywhere, with logging.isEnabledFor(logging.DEBUG) priority.
Changed logs to deferred string interpolation with %s style.
Changed the jax.util.get_logger function to return a single logger named "jax", instead of dynamically-named loggers.
Removed formatter code, enabled logging.DEBUG priority.
Reworked your etils PR from yesterday to use the jax.util.get_logger method.
Updated the commit message to not mention test migration anymore.

Thanks. I had a major misunderstanding about how logging works, especially about the propagation situation. I think I cleaned it up now - in particular I reverted my change to #12780, since that was the desired solution after all.
Also caught two more unconditional string interpolations along the way.

Thanks for the PR!


recipes: Heterogeneous performance harts

Replace negative description of heterogeneous architectures by helpful links.
Closes: #110

Sure.


CASMTRIAGE-6646 Deterministic SNMP Settings

Description

Use a more deterministic, and straight-forward method for updating customizations.yaml with sls_input_file.json's switch targets.
This new method is less error prone, removing any need to copy-paste and munge inputs together.
Checklist

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[ ] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.6


Slim 2: Avoid removal of physical path in PATH_INFO

Hi,
I have a Slim application where each URL within the controllers is prefixed with the base_url path (that is a string constant defined in my app config file). This allows me to use different base paths (ex: if running behind a reverse proxy, in a different folder, etc.).
But, I noticed that in Environment.php, line 143, the "physical" path is removed from PATH_INFO that will be consumed by the router.
By doing so, it's impossible to run correctly Slim in a subfolder, because all requests have the base path removed.
Is this a bug?
Is it possible to tell Slim not to remove the physical path? I can edit the Environment.php by myself, but, obviously, I can't use composer if I modify Slim libs files.

Can you provide a unit test or code that shows the problem?

Oh. For Slim 2, we're only fixing security issues as Slim 3 is now released.


Digital Signature Certificate based Encrypt and Decrypt

Hello,
Can you please integrate the digital signature certificate based encryption and decryption for the same project and update us

can you please share me your mail address so that i can send you exact scenario

<EMAIL_ADDRESS>pubkey: https://privatebin.net/?ca10bea53f29ec23#8HdyaLN54jQMK2jrQnrHXwngCrJ9h1wCXpuQCDV1d9Yv


Establish CI workflow

Added

ci.yml for basic CI workflow
CompatHelper.yml to keep track of package updates
TagBot.yml for release tagging

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@a0d8aa2). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   98.41%
=======================================
  Files           ?        1
  Lines           ?       63
  Branches        ?        0
=======================================
  Hits            ?       62
  Misses          ?        1
  Partials        ?        0

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


ginkgo-kubernetes-all.Jenkinsfile: fix misplaced bracket

Fixes: dcc4f78376fb ("Test: Fix issues with Ginkgo Kubernetes Job")
Signed-off-by: André Martins<EMAIL_ADDRESS>

This change is

test-missed-k8s

Build failure is legitimate:
20:14:47     k8s1-1.11: 	[WARNING FileExisting-crictl]: crictl not found in system path
20:14:47     k8s1-1.11: Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl
20:14:47     k8s1-1.11: I0719 20:14:45.728864    3518 kernel_validator.go:81] Validating kernel version
20:14:47     k8s1-1.11: I0719 20:14:45.729026    3518 kernel_validator.go:96] Validating kernel config
20:14:47     k8s1-1.11: 	[WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 18.03.0-ce. Max validated version: 17.03
20:14:47     k8s1-1.11: [preflight] Some fatal errors occurred:
20:14:47     k8s1-1.11: 	[ERROR KubeletVersion]: the kubelet version is higher than the control plane version. This is not a supported version skew and may lead to a malfunctional cluster. Kubelet version: "1.11.0-beta.0" Control plane version: "1.10.5"
20:14:47     k8s1-1.11: [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
20:14:47 The SSH command responded with a non-zero exit status. Vagrant
20:14:47 assumes that this means the command failed. The output for this command
20:14:47 should be in the log above. Please read the output to determine what
20:14:47 went wrong.
20:14:47

Link:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/570/

test-me-please

test-missed-k8s


fix OtakuDesu

Source name and language
OtakuDesu [Indonesian]
Describe your suggested feature
please fix
Other details
haven't noticed for too long
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I have updated the app to version 0.13.5.
[X] I will fill out all of the requested information in this form.

what the bug...


Read only types for Record

For v4.0.0-rc.9, Record({ counter: 0 }) corresponds to type RecordOf<{ counter: number }>,
It would be great if it corresponded to type RecordOf<$ReadOnly<{counter: number }>>.
Would a PR making this change to the Flow types be welcome?
Here's an example of a change to immutable.js.flow:
// The type of runtime Record instances.
- type RecordOf<Values: Object> = RecordInstance<Values> & Values;
+ type RecordOf<Values: Object> = RecordInstance<Values> & $ReadOnly<Values>;

Great idea - in fact everywhere Values is referenced (sometimes as T) this should be the correct behavior.

Should we also use $Exact ?
The semantics are as follows:
T: { a: number, b: string }

foo: $Exact<T> = { a: 3 } // error
bar: $Exact<T> = { a: 3, b: 'hello' } // fine

I'm not sure that's necessary since Exact and & do not always interact together the way you might expect, but if you find that it improves type correctness I'm open to looking at PRs


Frame rotation is reset when deleting a frame

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce

With "Rotate all images" enabled in settings, rotate an image (Ctrl+R)
Delete a frame (Alt+Del)
Frame orientation is reset to default

Expected Behavior
I'd expect the frame orientation to remain active for all frames (except maybe the deleted frames). It happens both when "Show deleted frames" is enabled and when it's not.
Possible Solution
frameAngles is still set correctly after frame deletion, so the information is still there. It looks like if I remove this line that everything works as it should. Is there a reason why this is in there?
Context
This makes the image rotation feature unusable for my usecase, and I need all images to be rotated 90 degrees, and a considerable amount of images in the dataset are being deleted.
Environment
Using self-hosted CVAT v2.11.1

Hello, Has this issue been resolved? I would like to resolve this issue if it has not been as I am currently working on a open source project with bugs that need fixing and I would like to take this task on. Please let me know.


Update for CUDA 12.4.1

xref: https://github.com/conda-forge/cuda-feedstock/issues/23

@conda-forge-admin, please rerender

Was missing cuda-gdb on linux_aarch64. This is now uploaded, but may still be mirroring

@conda-forge-admin, please restart ci


Add ticket creation function

Add optional function to create ticket/issue for manual changes detected for script.
Idea is that if there is a change performed not via automated deployment service, there should be automated way to flag such change and track it.

Implemented in #7


add job id to admin jobs

Coverage increased (+0.008%) to 92.908% when pulling 52ce01a65a4ede2a0a60bf8dec8a656938f44fc9 on antgonza:add-job-id-to-admin-jobs into da851aaeb8385fbf55d0e263e42f618a43f7deaa on qiita-spots:dev.


Fix integration CI not reporting success correctly

Codecov Report

Merging #32 (6e3eb2b) into master (4f0d89d) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Current head 6e3eb2b differs from pull request most recent head 0c4de29. Consider uploading reports for the commit 0c4de29 to get more accurate results

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
- Coverage   79.92%   79.90%   -0.02%
==========================================
  Files          26       26
  Lines        1514     1513       -1
  Branches       93       92       -1
==========================================
- Hits         1210     1209       -1
  Misses        288      288
  Partials       16       16

Flag
Coverage Δ

unittests
79.90% <ø> (-0.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

flow_py_sdk/client/entities.py
47.36% <0.00%> (-0.40%)
:arrow_down:

Continue to review full report at Codecov.

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


Add methods for listing & revoking named user api keys

Also changes the createApiKey method to accept an optional description for the key.
Resolves: #486
Change-Type: minor

I'm not sure changing resin-requests types is a breaking change, since Bluebird promises should mean we've effectively widened the types of request. Any existing code should still work, I think, it's just that now even more promise methods are available, right?

I actually had to change a method in the UI that was typed to return an es6 Promise to return a Bluebird Promise and that was the reason I added the Breaking comment. Should I remove it?

All looks great! I'm not 100% sure what our position is on breaking changes for types only, which don't actually break at runtime, but I'm fine with being cautious and marking that as breaking as well anyway.
:+1: :shipit:

The part that I liked in this PR a lot, was that the new TS model uses the sdk's exported typings for pine and request.


Fix InsecureRequestWarning when making Elasticsearch requests

This warning keeps appearing in the dashboard logs:
[WARNING] py.warnings:connectionpool:_validate_conn:857: /usr/share/archivematica/virtualenvs/archivematica-dashboard/local/lib/python2.7/site-packages/urllib3/connectionpool.py:857: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings

We should work out what’s causing it, and address it.

Closing as redundant – we no longer use Elasticsearch in Archivematica, so these errors are irrelevant.


Workflow for AutoTP

This PR add a new extendable workflow for automatic tensor parallelism (https://www.deepspeed.ai/tutorials/automatic-tensor-parallelism/).  The workflow aims to provide a way to validate AutoTP for LLM models.

The specific error below is because of the container is not created with CAP_SYS_NICE capability.  I'll check the additional flags I use for container and post it here.
set_mempolicy: Operation not permitted
setting membind: Operation not permitted

On my system docker container needs to be started with SYS_NICE capability with the following flag.
  --cap-add SYS_NICE

Not sure how to turn on this for DeepSpeed runner.
Without this capability, we have to remove --bind_cores_to_rank flag, but this would significantly impact the running time of the test.

A proper behavior of DeepSpeed --bind_cores_to_rank is only bind memory to NUMA node if system allows to.  The makes DeepSpeed behave more graceful in docker environment.  The latest fix in DeepSpeed had been verified on my own runner, with and without SYS_NICE capability.
https://github.com/delock/DeepSpeedSYCLSupport/actions/runs/7581455004/job/20649083143
https://github.com/delock/DeepSpeedSYCLSupport/actions/runs/7581918228/job/20650446510

Hi @loadams the blocking issue for this PR had been resolved.  Can you help restart the workflow?   Thanks!

@tjruwase Thanks!  Currently the workflow passed.  One thing I'm not sure is whether the checkpoint downloaded will be preserved across different runs.  This will be most time consuming part of this workflow.   Will need some comments (i.e. which directory in runner can preserve?) or observe another run to see whether the checkpoint preserves.

@delock, it is great to see the CI now passing.
I think @mrwyattii or @loadams would be the best to answer questions about the checkpoint.

@mrwyattii @loadams it will be great if there is any link showing how persistency is done on this runner.

@delock, it is great to see the CI now passing.
I think @mrwyattii or @loadams would be the best to answer questions about the checkpoint.

@mrwyattii @loadams it will be great if there is any link showing how persistency is done on this runner.

@delock, it is great to see the CI now passing.
I think @mrwyattii or @loadams would be the best to answer questions about the checkpoint.

I know @mrwyattii and I still need to leave feedback on this PR, but an example of where things are on the blob storage here, I'm not sure that's the best example, but that's one that shows persisting a larger download/install.

@mrwyattii @loadams it will be great if there is any link showing how persistency is done on this runner.

@delock, it is great to see the CI now passing.
I think @mrwyattii or @loadams would be the best to answer questions about the checkpoint.

I know @mrwyattii and I still need to leave feedback on this PR, but an example of where things are on the blob storage here, I'm not sure that's the best example, but that's one that shows persisting a larger download/install.

Thanks for the suggestion.  By looking at the usage of '/blob' in DeepSpeed workflows.  I found I need to use the default value of TRANSFORMERS_CACHE.   Let me make the change and see if it persists.

Hi @loadams can you help start the workflow?  The model checkpoint path had been moved to /blob which should be persistent.

Hi @loadams can you help start the workflow? The model checkpoint path had been moved to the persistent storage as suggested.

Apologies, I was out but it should be running now.

Hi @loadams can you help start the workflow? The model checkpoint path had been moved to the persistent storage as suggested.

Apologies, I was out but it should be running now.

Thanks!   The failure in the workflow should be due to version mismatch between pytorch (2.2.0) and Intel extension for PyTorch (2.1).   The recent failure in cpu-inference workflow should also be caused by this reason.  An upcoming release of Intel extension for Pytorch should fix it.  Let me ping you when the new version is released.

@loadams Intel Extension for Pytorch 2.2 had been released today.  Restart the workflow should resolve the failure.
https://pypi.org/project/intel-extension-for-pytorch/

Hi @loadams can you help start the workflow? The model checkpoint path had been moved to the persistent storage as suggested.

Apologies, I was out but it should be running now.

Thanks! The failure in the workflow should be due to version mismatch between pytorch (2.2.0) and Intel extension for PyTorch (2.1). The recent failure in cpu-inference workflow should also be caused by this reason. An upcoming release of Intel extension for Pytorch should fix it. Let me ping you when the new version is released.

The latest error is caused by change of command line in DeepSpeedExamples hf_compare.py.  The latest commit adapt to this change.

Hi @loadams, can you help start the workflow for this PR? Thanks!

@loadams thanks for start the workflow.  Now this workflow is ready for testing autotp for various popular modules.   Should we continue add new models into this PR?   I plan to add model for validation one by one so we have a steady growing list.

Hi @loadams I have added gptj and baichuan7b model to autotp workflow, can you help start the workflow?

Hi @loadams I have added gptj and baichuan7b model to autotp workflow, can you help start the workflow? Thanks!

Done.

Now this workflow is ready for testing autotp for various popular modules. Should we continue add new models into this PR? I plan to add model for validation one by one so we have a steady growing list

For this, I think the concern that @mrwyattii and I had was is there any way to include this in the existing cpu-inference workflow since the setup is similar?  Perhaps adding a step that only runs if the build is a scheduled build (non-PR weekly job) that then opens an issue if this workflow fails?

Hi @loadams I have added gptj and baichuan7b model to autotp workflow, can you help start the workflow? Thanks!

Done.

Now this workflow is ready for testing autotp for various popular modules. Should we continue add new models into this PR? I plan to add model for validation one by one so we have a steady growing list

For this, I think the concern that @mrwyattii and I had was is there any way to include this in the existing cpu-inference workflow since the setup is similar? Perhaps adding a step that only runs if the build is a scheduled build (non-PR weekly job) that then opens an issue if this workflow fails?

I think its doable.  We can test these steps in cpu-inference workflow then guard the steps with schedule event.

Hi @loadams I have added gptj and baichuan7b model to autotp workflow, can you help start the workflow? Thanks!

Done.

Now this workflow is ready for testing autotp for various popular modules. Should we continue add new models into this PR? I plan to add model for validation one by one so we have a steady growing list

For this, I think the concern that @mrwyattii and I had was is there any way to include this in the existing cpu-inference workflow since the setup is similar? Perhaps adding a step that only runs if the build is a scheduled build (non-PR weekly job) that then opens an issue if this workflow fails?

I think its doable. We can test these steps in cpu-inference workflow then guard the steps with schedule event.

Sounds good, thanks!  Just tag me when you need the workflows started.

@loadams I have moved autotp workflow to the end of cpu-inference workflow.  Can you help start the workflow?  Thanks!
I didn't find the reason for GPT-J failure.  This model is special because it has a single big FP32 model checkpoint (24GB), probably this added too much memory pressure.  I replaced it with Falcon-7b which has much smaller chunk of model checkpoint.  Let's see whether this will pass.  I also added a probe for /blob to understand the capacity of checkpoint cache.

@loadams Falcon 7b model is not supported by DeepSpeed AutoTP yet.   I updated the workflow to test Baichuan 7b instead.  Can you help restart the workflow?  Thanks!

Hi @loadams the command line of baichuan model had been changed to fix the test error.   The reason is Baichuan model contains remote code so need to set trust_remote_code to true.  Can  you help restart the workflow?  Thanks!

hi @loadams @tjruwase can you help start this work flow? thanks!

Hi @loadams , I see the environment issue should have been fixed.  Can you help restart the workflow?

Hi @loadams , I see the environment issue should have been fixed. Can you help restart the workflow? Thanks!

@delock - yes, apologies that took so long.

@loadams I ran these two tests on my local environment.  It didn't took so long.  Can you help run this workflow again to see whether it is reproducible?  Thanks!

@loadams I ran these two tests on my local environment. It didn't took so long. Can you help run this workflow again to see whether it is reproducible? Thanks!

Re-running now

Hi @loadams, I tried run these UTs in my environment and didn't see this timeout.  Since CPU UT is already covered by workflow cpu-torch-latest.  I removed unit tests in this workflow and focus on AutoTP test only.  I also removed dependency on oneCCL and use stock pytorch to better focus on AutoTP functionality.  Can you help start the workflow?  Thanks!

Hi @loadams, I tried run these UTs in my environment and didn't see this timeout. Since CPU UT is already covered by workflow cpu-torch-latest. I removed unit tests in this workflow and focus on AutoTP test only. I also removed dependency on oneCCL and use stock pytorch to better focus on AutoTP functionality. Can you help start the workflow? Thanks!

Done

For Baichuan model failure.  I'm seeing it pass on my local environment with exactly the same arguments.  From failed log in the workflow I see 'file not found' error when acquiring a lock.  Suspect because of HF_HOME had not been properly set.  Will point HF_HOME to /blob/ to try again
runner/_work/DeepSpeed/DeepSpeed/DeepSpeedExamples/inference/huggingface/text-generation/utils.py", line 43, in __init__
    self.tokenizer = AutoTokenizer.from_pretrained(model_name, padding_side="left", trust_remote_code=trust_remote_code)
  File "/tmp/actions-runner/_work/DeepSpeed/DeepSpeed/unit-test-venv/lib/python3.8/site-packages/transformers/models/auto/tokenization_auto.py", line 829, in from_pretrained
    return tokenizer_class.from_pretrained(
  File "/tmp/actions-runner/_work/DeepSpeed/DeepSpeed/unit-test-venv/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2047, in from_pretrained
    resolved_vocab_files[file_id] = cached_file(
  File "/tmp/actions-runner/_work/DeepSpeed/DeepSpeed/unit-test-venv/lib/python3.8/site-packages/transformers/utils/hub.py", line 398, in cached_file
    resolved_file = hf_hub_download(
  File "/tmp/actions-runner/_work/DeepSpeed/DeepSpeed/unit-test-venv/lib/python3.8/site-packages/huggingface_hub/utils/_validators.py", line 119, in _inner_fn
    return fn(*args, **kwargs)
  File "/tmp/actions-runner/_work/DeepSpeed/DeepSpeed/unit-test-venv/lib/python3.8/site-packages/huggingface_hub/file_download.py", line 1451, in hf_hub_download
    with WeakFileLock(lock_path):
  File "/opt/conda/lib/python3.8/contextlib.py", line 113, in __enter__
    return next(self.gen)
  File "/tmp/actions-runner/_work/DeepSpeed/DeepSpeed/unit-test-venv/lib/python3.8/site-packages/huggingface_hub/utils/_fixes.py", line 83, in WeakFileLock
    lock.acquire()
  File "/tmp/actions-runner/_work/DeepSpeed/DeepSpeed/unit-test-venv/lib/python3.8/site-packages/filelock/_api.py", line 262, in acquire
    self._acquire()
  File "/tmp/actions-runner/_work/DeepSpeed/DeepSpeed/unit-test-venv/lib/python3.8/site-packages/filelock/_unix.py", line 44, in _acquire
    os.fchmod(fd, self._context.mode)
FileNotFoundError: [Errno 2] No such file or directory

Hi @loadams after reading the error log I suspect Baichuan model under TRANSFORMERS_CACHE is corrupted.  I unset TRANSFORMERS_CACHE since we set HF_HOME for this model.  I also add a peek to TRANSFORMERS_CACHE and HF_HOME in case a manual cleanup will be needed.  Can you help start the workflow?  Thanks!

@loadams @tjruwase the latest error in Baichuan model AutoTP is very wierd.  It complains about lock file not found or attribute not found.  Which I cannot reproduce locally.  It indicates probably there is some courrpted states in hf_hub downloaded data.
Currenlty bloom and opt model AutoTP is consistently running well.  Can we merge this baseline first then seek add new autotp model validation in followup PR?  It might take a while to debug this issue.  I'll submit a commit disable baichuan test first.


Model stuck after saving a checkpoing when using the FSDPStrategy

Bug description
I'm training a GPT model using Fabric. Below are the setups for Fabric
It works well if I'm running without saving a checkpoint. However, if I save a checkpoint using ethier torch.save with fabric.barrier() or with fabric.save() the training will stuck.
I saw torch.distributed.barrier() have a similar issue. I don't have a similar utilities in my code. Not sure if there is a same usage in Fabric.
What version are you seeing the problem on?
v2.1
How to reproduce the bug
strategy = FSDPStrategy(
            auto_wrap_policy={Block},
            activation_checkpointing_policy={Block},
            state_dict_type="full",
            limit_all_gathers=True,
            cpu_offload=False,
        )
self.fabric = L.Fabric(accelerator=device, devices=n_devices, strategy=strategy, precision=precision)

Saving model with
state = {"model": model}
full_save_path = os.path.abspath(get_path(base_dir, base_name, '.pt'))
fabric.save(full_save_path, state)

Error messages and logs
# Error messages and logs here please

No errors, only stuck!
Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow): lightning, mainly using Fabric
#- PyTorch Lightning Version (e.g., 1.5.0): 2.1.3
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0): 2.1.2+cu118
#- Python version (e.g., 3.9): 3.10.13
#- OS (e.g., Linux): Ubuntu
#- CUDA/cuDNN version: 11.8
#- GPU models and configuration: A100 40Gx2
#- How you installed Lightning(`conda`, `pip`, source): pip
#- Running environment of LightningApp (e.g. local, cloud): local

More info
I think it relates to the communications betweeen the systems.
cc @awaelchli @carmocca

@charlesxu90 are you able to share the code? or a minimized version that reproduces the problem?

Sorry, I cannot share my code. I solved it by not saving checkpoints in the middle.

I meet the same problem. Who can help me?


ENH:optimize: Rewrite nnls in Python

Reference issue
Part of #18566, as one of the low-hanging fruits.
What does this implement/fix?

Pythonized Nonnegative Least Squares function optimize.nnls
Implemented the faster NNLS instead of the classical NNLS algorithm which is typically very slow. For large problems the performance difference is very obvious.
Added a tolerance keyword atol to control the inner iteration behavior. Since the algorithm errors out, the user needs something to relax the problem. I used atol just in case in the future we need rtol, so we don't need to deprecate tol keyword.
Added two more tests and that's 100% improvement on the number of tests.
Deleted the fortran77 code.

Since I am not super up-to-date with optimize etiquette, please let me know if I'm going against the grain.
This PR now opens up the possibility to solve multiple RHS through vBenthem, Keenan,  https://doi.org/10.1002/cem.889 but since there are too many things happening, I'd like to leave it to later as an enhancement. Also now code is a bit more readable (or at least familiar syntax) so probably if needed can be Cythonizable.

Good work here! One question from me: Are there benchmarks for small matrices? nnls can be the bottleneck in nested optimization problems. I am not sure if a pure numpy implementation is as fast there as the classic fortran code. For larger problems I expect the new implementation to be faster though due to the algorithmic improvements.

Ah good one, let me run some benchmarks

For small arrays indeed there is some performance loss with this PR. The quickest way is to cythonize it obviously. But not sure if it is worth it since I don't know how much this is being used..

Also it'd be useful IMO to compare to https://github.com/scipy/scipy/blob/v1.10.1/scipy/optimize/_lsq/bvls.py, which is user-facing through lsq_linear.

For small arrays indeed there is some performance loss with this PR. The quickest way is to cythonize it obviously. But not sure if it is worth it since I don't know how much this is being used..

This is impressive. For small problems there is a minor performance loss but I don't think it must be a blocker here. Cythonization can be done in a follow up.

What do the optimize residents think about this rewrite?

Sorry, not familiar with this area. Id say if the python code is clean, and there's a performance benefit, then a merge should occur as is

OK let's get it in. Since we still have some time for v.1.12 we will have the chance to remedy should something arise. Thanks everyone.


Feature request: Ability to remove flags

I have development nginx configuration, it is working on localhost with HTTP, but proxies requests to HTTPS upstream. And I need to remove Secure flag from upstream cookies.
I've found two questions from guys with same need, both without answers:
https://serverfault.com/questions/853228/nginx-reverse-proxy-remove-secure-from-cookies
https://stackoverflow.com/questions/41628020/nginx-remove-secure-flag-to-cookies-from-proxied-server

Meanwhile I forked this module and changed it to nginx_unsecure_cookie_module
I'm frontend developer, my C/C++ knowledges are super low, so I wouldn't dare make a PR :) I just chopped your code and changed append part to strip "Secure" flag.
But this, of course, not a flexible solution.

hi,
do you know if there is an nginx docker image with nginx_unsecure_cookie_module
as we already have one with nginx_cookie_flag_module => https://hub.docker.com/r/rplan/nginx

@boly38 Hi!
I made docker image with this module, but it is stored in internal repository.
It could be dangerous, if someone will use this image without fully understanding, what one is doing. That is why I did't make public image.
But you can easily build your own image, just copy official nginx Dockerfile and add module while build nginx.
Here is example:
https://gist.github.com/yumauri/2c93e727ee15f32529da351b030e1190
(I took not latest image, because they changed build process, and I didn't dig it yet)

@yumauri thanks for your input, this save me a lots of time :) 👍

@boly38 mentioned your image in readme :)

not sure that makes me happy ;) now cyberdefence will know who is root responsible !
(just kidding, thanks 👍 )

Since version 1.19.3 nginx supports proxy_cookie_flags, so I've archived my repo.


(🎁) Rule for providing keyword argument when non-meaningful literal is passed as positional argument

For the following call:
a = textwrap.TextWrapper(70, "", "", True, True, False, True, True, False, 4)

It's very hard to understand what the code is doing. Instead you'd want to have keyword arguments:
a = textwrap.TextWrapper(
    width=70,
    initial_indent="",
    subsequent_indent="",
    expand_tabs=True,
    replace_whitespace=True,
    fix_sentence_endings=False,
    break_long_words=True,
    drop_whitespace=True,
    break_on_hyphens=False,
    tabsize=4
)

Inspired by: https://github.com/pylint-dev/pylint/issues/385

Reminiscent of the flake8-boolean-trap rules.


destVI bugs

We have identified several issues with the current version of the DestVI code:

(critical) the current code doesn't train at all on master. Can has flagged an issue with the nobs that needs to be resolved
(important, minor) there is an undesirable setup on the neural net architecture of the amortization network for the proportions (not for the gamma used throughout the paper)
(important, minor) there is some discrepancy in the treatment of the library size that must be figured out in between CondSCVI and DestVI

1 is fixed by branch fixed_elbo from Adam this morning
2 I will try with simulated data and open a branch afterwards
3 Currently running some tests and

Using the lymph node dataset from the preprint.

not sure if related but trying destVI on a new dataset following the tutorial, I get kernel error at this stage:
sc_model.train(
    max_epochs=250,
)

Other times instead, can't reproduce, I get nan in the encoder output (again trying to reproduce but can't rn). Few months ago it was working fine though. Will try if #1457 fix it.

ok, having the same issue with Stereoscope implementation, I'm afraid is independent. Am currently on a mac. Apologies for hijacking the issue.

The reason for the PR is not numerical instability but instability for estimated cell type proportions with two bug . If it is also an issue with Stereoscope, I would suggest to check the input data first (single dataset where this is happening) and you might want to reduce learning rate in CondSCVI

This should have been closed by #1457


Added AREG SDK to the C++ list.

It is definitely not a dead project, it is new and has room to grow. It offers a solution of the relatively new IoT paradigm called "mist computing". It is cross-platform, suitable for embedded and high-end systems.

@lk-geimfari, thank you for merging. But I've checked the C++.md file and didn't find there the updates. Was there a problem?

@lk-geimfari, thank you for merging. But I've checked the C++.md file and didn't find there the updates. Was there a problem?

I was updating C++ list yesterday, to make list looks better and accidentally removed this new project. That's totally my bad, gonna fix ASAP.
Thank you for noticing!

@lk-geimfari, Thank you! I appreciate that.

Done!


[flake8-pyi] Implement PYI017

Summary
Implements PYI017 or Y017 from flake8-pyi plug-in. Mirrors upstream implementation. It checks for any assignment with more than 1 target or an assignment to anything other than a name, and raises a violation for these in stub files.
Couldn't find a clear and concise explanation for why this is to be avoided and what is preferred for attribute cases like:
a.b = int

So welcome some input there, to learn and to finish up the docs.
Test Plan
Added test cases from upstream plug-in in a fixture (both .py and .pyi). Added a few more.
Issue link
Refers: https://github.com/astral-sh/ruff/issues/848

Thanks for working on this! It looks like a good start. Would you mind marking this as a draft until the documentation is done?

Sure! I'm probably going to need some help with that from someone who knows more about flake8-pyior stub files though. Could you maybe mark it as such with a label of some sorts? Upstream plug-in does not have much more to say on it than:
Stubs should not contain assignments with multiple targets or non-name targets. E.g. T, S = TypeVar("T"), TypeVar("S") is disallowed, as is foo.bar = TypeVar("T").

And browsing through https://peps.python.org/pep-0484/#stub-files and https://typing.readthedocs.io/en/latest/source/stubs.html I can find no mention of it either

@AlexWaygood might have some more details on the intent of the rule.

I can do it when I’m back on my computer, but I’d recommend looking through the Git history upstream. There‘s often additional context in the PR summaries and release notes.

Found this: https://github.com/PyCQA/flake8-pyi/pull/76 which links to https://github.com/python/typeshed/issues/4913 and then https://peps.python.org/pep-0613/ which seem to hint at
a.b = int
a = b = int

possibly not being valid explicit type aliases and therefore problematic but I'm not sure.

To me, a.b = int in a stub files looks like an anti-pattern, it's definitely more readable if you'd b: int inside the class or module a

In general, stub files should be thought of as "data files" for a type checker. They're not intended to ever be executed. As such, it's useful in general to enforce that only a subset of Python syntax is allowed in a stub file, to ensure that everything in the stub is 100% unambiguous when it comes to how the type checker is supposed to interpret it. (If it's not, there's not much point in having the stub files at all!)
So, without doing too much historical research into why we originally implemented this check, I feel like it's of a piece with this general principle.

In other words: there's basically no reason anybody should ever need to use multiple assignment, or assignments to non-Name targets, in a stub -- and if somebody's trying to do that for whatever reason, it likely indicates some kind of misunderstanding on their part.
We could probably improve the error message and docs over at flake8-pyi!

Thanks for the explanation! I'm happy with that as a ## Why is this bad? snippet. Will add and open up for review again.


Review the calculation of disease risk

James asked about the calculation of ORR (Overall Relative Risk) of diseases - is it sensible to divide the relative risks over the average relative risk for the whole population?

Uploading the STOP paper appendix for info.
STOP-model-paper-appendix.pdf
From discussions with @israel-vieira and @jzhu20, I'm a bit more convinced that this is correct. Let me know if you see something wrong.
Incidence is constant, taken from the beginning of the simulation, as is the expected risk from factors and disease taken at start.
Therefore, in order to 'update' incidence for a given year (as it were), you multiply it by average risks at the time, divided by the expected risks recorded at start:
P_disease = incidence * (mean_risk_at_current / mean_risk_at_start)

This gives P_disease = incidence * (x / x) for some x when mean current risk equals mean start risk, with incidence taken at start. This is what you want, since, if risk hasn't changed, probability of new disease should equal incidence.

I reckon that, for a given year (or we understand it as for a given distribution of risk factors and diseases),

adjusted incidence rate of a disease = incidence rate (by age and gender, assumed constant over time) * ORR
ORR = multiplication of all the relative risks / population-level average of relative risks

where the population-level average of relative risks is changing over distribution of risk factors and diseases, but for each age*gender group at a time, it's constant.
Population-level average of ORR is constantly 1, i.e., E(ORR)=1, so that
E(adjusted incidence rate of a disease) = E(incidence rate) * E(ORR) = E(incidence rate), which makes sense; otherwise, population-level incidence will change over time.

Continued in  #308


Enrich loki.source telemetry using discovery components

Background
If you use a component such as loki.source.syslog, you may want to add extra labels to your logs using discovery components such as discovery.http. This is not possible at the moment.
Proposal
One way to do this in the future would be to have a new component which works as follows:

Both "discovery" and "log" labels need to have a common label in order to be joined. This can be configurable in the new component, e.g. under a join_label argument. By default this could be set to __address__.
The new component persists in memory the latest labels received from discovery.http.
When it receives logs from components such as loki.source.syslog, it will:

Check if the logs contain the configured join_label.
If they do, add the latest "discovery" labels to the logs as labels.
If they don't, then passthrough the logs as they were.

A few notes:

Should join_label be a string or a list? If it's a list, all labels in the list must be the same in the sets of "log" and "discovery" labels.
The reason we need a new component as opposed to a new standard library function is that the component must be stateful. Standard library functions are stateless.
Does the fact that the component is stateless has a negative effect on clustering?
Can the component's memory consumption blow up if it persists too many labels in memory? Should we configure a limit?

Hi, I'm really happy this is proposed! I wanted to add that the same functionality would be applicable to metrics, not only logs. E.g. we have some vendor systems which can natively push prometheus / otel but where we can't specify custom label-sets at the source. I would also advocate for the list approach as it's much more flexible. Even better would be some set theory as e.g. you might want to join the label-sets by hostname [OR/AND] by IP.


Flighttask offboard setpoint mixing

This PR will allow to mix setpoints through offboard such as:
position xy + velocity z
velocity xy, position z
yaw + yaw-speed

Cool!


Metronome tick size above player head

Would it be possible to add configuration to adjust size of metronome above player head.
This should be similar to TOB qol plugin insatnce timers.

Yep I added the option of adjusting the size of the overhead metronome in V1.4 as well as a few other things. Thanks for the suggestion, the TOB qol plugin was helpful to look at and to implement this change.


use yt entrypoints

bump min yt version so we can use the new frontend entrypoints
update workflows

Closes #9


Remove version number from the module name

Closes #27

@TavoNiievez Thank you for all the work - I tested this new repository in one of my projects and it worked fine.
The new package codeception/module-doctrine is not available on packagist yet (https://packagist.org/packages/codeception/).

@W0rma I already talked to @DavertMik about this via Slack. I don't have permissions to publish it myself.

@W0rma it is already published, thank you.

@TavoNiievez That's great. Thank you!


How to set Folder Chooser Dialog as uncancellable?

Hi Aidan,
Is there a way to dismiss the Dialog only when a folder is chosen? Or better, can we (developers) have the possibility to choose whether the "Cancel" button should appear or not? I'm making an app to install Custom ROMs so I let users to choose the folder where they placed the ROM's zip file. The Dialog code is located in onCreate method so users must choose a folder before continuing. Could you help me? Thanks in advance!

@peppe130 passing 0 for the cancel button should hide it, as long as you're using version <IP_ADDRESS> of the library.
Also, FolderChooserDialog is a DialogFragment, so you can call setCancelable on it.
FolderChooserDialog dialog = new FolderChooserDialog.Builder(this)
    .cancelButton(0)
    .build();
dialog.setCancelable(false);
dialog.show();

Perfect!!!!! Thank you very much!

I found a bug! Also in root directory "/" the Dialog keep showing the three dots to get to parent folder. By pressing on them, the app crashes :)

Weird, it doesn't happen to me 😮


Multiprocessor Specification question.

I compiled bochs without --enable-smp, I found its speed was very slow.
So I want ot ask if I compile boshc with --enable-smp, it will affect my fuzz program result or not?

What exactly do you mean by very slow? Bochs as a software emulator is very slow by definition, guest execution speeds around 50-150M IPS are expected.
I have never used --enable-smp so it's hard for me to comment on how it will affect the performance, but according to the documentation:
Do not expect this option to speed up your simulation! On the contrary, it has to spend extra time simulating the different CPUs (even if they're mostly idle) and the communication between them.
So I would advise against enabling SMP.

OK, I see. Thanks.


Fix for footer gap due to custom kerning requirements

The reason this fix is needed is that the custom kerning requirements that translate individual letters up and down by certain percentages create a space at the foot of the container. This gap is filled to a certain extent by the footer, however on larger screens this this gap increases as the font size is linked to the screenwidth for the large text. We can not simply put overflow hidden on the container as this cuts off the text when we hover on the right of the screen. This need for both custom kerning AND hover right means we are stuck doing something a little fiddly to fix this (and many other things).
SO. I have slightly decreased the font size on all the text (I think this as low as we can go without discussing with BMEOF) and adding a tiny bit of padding on the top of the footer.
This will need to be checked on a few devices and browsers to make sure I have completely covered the gap. Please check on mobile as well. I do not want to launch something half fixed as we have done that a few times recently and it is probably going to start annoying the client at some point.
There is a possibility that if this doesn't cover enough and the gap appears on larger screens then you could make padding top on the footer a vw unit.
When you do merge and show BMEOF can you tell them (in simplified terms) what we have done and check he is OK with that.

Issue on mobile, last link + footer are cut off


Update readme and/or jspm with test dependencies

path, logging, binding all need to be installed to run the tests.

@PWKad We have someone who wants to submit a PR to fix our promise issue but would like to wait until this is fixed up. Any chance you can resolve this soon?


Will this support incremental processing ?

Incremental what?

incremental kapt. i'm sorry zac, i don't know whether to choose incremental kapt, incremental processing, or incremental annotation. i don't know the difference

This isn't an annotation processor. KSP is a different API


Custom Theme Resets After Closing/Restarting App

In Latest Fdroid Release, Whenever We Close/Reopen App, Previously Made Custom Theme Resets.
Android 10, MIUI 12.5

Na versão mais recente do Fdroid, sempre que fechamos/reabrimos o aplicativo, redefinimos o tema personalizado anteriormente.
Android 10, MIUI 12.5

Hello, can you inform the theme you are using when this happens and the version of your app

Custom Theme in 1.8.3

The One Which Can Be Customized From Settings>Themes Section.

I've fixed it. Wait for the update. Thanks for reporting.

Custom Theme in 1.8.6

version code?
312


[Do not merge] Remove the use of NIO from WebSocket code

This branch is not ready, though its in a working state, the EchoClient works, though currently we are not handling fragmentation, this is being worked on.
Its mostly a request for comments at this stage.
Below are some things that I know are bad and I am working on them:

processHandshake() should be moved back to processData() as it previously was and as it is in other autobahn implementations.
The http status parsing code should be moved back to parseHttpStatus() from processHandshake, again due to similar reasons.
Remove commented code.
Add code comments, where applicable.
...and more.

One reason the diff might look funny is because in some files tab size of this project was 3 spaces, in others 4, so that was conflicting a bit with my editor. Will also do another PR to make that uniform everywhere, but later.

Awesome! Thanks for your work! Collaboration is starting good=)
Cleaning up the tabs mess: +1
Rgd testing the WebSocket layer: guess you are aware of https://github.com/crossbario/autobahn-testsuite ?
In the end, this should pass 100% green (without the tests for websocket-compression probably, because this is completely unimplemented in AB-Android right now). It did pass 100% green in the past - and it also does test fragmentation and all kinds of corner cases. Just mentioning here so you are aware.
Sidenote: I have an issue https://github.com/crossbario/crossbar-docker/issues/13 to simplify usage of AB testsuite also using a Docker image. Let me know if that would simplify things for you, then I can do that. Easy.

Rgd testing the WebSocket layer: guess you are aware of https://github.com/crossbario/autobahn-testsuite ?

I was aware of the autobahn-testsuite, its famous ;) but in current context, I hadn't looked into it.

In the end, this should pass 100% green (without the tests for websocket-compression probably, because this is completely unimplemented in AB-Android right now). It did pass 100% green in the past - and it also does test fragmentation and all kinds of corner cases. Just mentioning here so you are aware.

I didn't know if the current implementation was passing that suite, though I presume we won't be getting a 100% pass rate today, will first run tests for the fuzzing client and see the pass rate on master. So that I have a baseline success rate for this pull request.

Sidenote: I have an issue crossbario/crossbar-docker#13 to simplify usage of AB testsuite also using a Docker image. Let me know if that would simplify things for you, then I can do that. Easy.

Wrote there, but yep, that will indeed make things simpler.

Ok, so this branch got bigger than I anticipated. There was some offset issue that took me a while to figure but now we are at least able to run some autobahn tests.
Though it seems performance is quite slow than previous implementation using NIO so that is something to fix. Currently I am reading the raw InputStream instead of using a buffered stream, also the data array is being recreated (very inefficient), so these are things that I plan to fix in next iteration, instead of making this branch even bigger.
Once this lands, the 4 space tabs and Dockerfile branches are incoming.

Updated the title as I believe we can now consider this for landing.
On a slightly different note: The copyright header still refers to tavendo. @oberstet what are your thoughts on updating the copyright header, shall it be done in one go or slowly as we go forward ?

@om26er rgd copyright header: good point! we should change that in one go over all files to the following:
///////////////////////////////////////////////////////////////////////////////
//
//  AutobahnJava
//
//  Copyright (c) Crossbar.io Technologies GmbH and contributors
//
//  Licensed under the MIT License.
//  http://www.opensource.org/licenses/mit-license.php
//
///////////////////////////////////////////////////////////////////////////////

Thanks for merging this.
I have been profiling the performance and blame the recreation of the buffer that holds the data (I wrote that). The latest commits(already merged) in this branch make use of BufferedInputStream, that improves the performance a bit but the real fix is in maintaining a single buffer and seeking through it, instead of recreating it. Now that this PR is merged, I'll do that in another one.

@om26er sounds good! thanks for your work! I'll try to prioritize creating a Docker image for the AB testsuite .. in days.


DBZ-7706 added mongo-sharded-replicaset tag to system tests

for replicaset test added new tag and removed all others, so this test is ran only if explicitly specified

Please add the Jira issue url to the PR.


add support for proxy

 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.asathy856 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


More repo cleanup

Fix and document pre-commit.
Configure tools inside pyproject.toml instead of separate files
Only publish docs on push to main (not PRs)
Update contributor and readme (sort of)

closes #79


Renaming some types? And API function?

Hmmm.... the names of the types are really not good.
cmatrix_t is actually holding a numpy array (not a matrix). What about renaming to npy_array_t?

PR #10 will probably take care of this.

closed by PR #10


Update 02_merge_detection_data notebook with real datasets

Summary

How to test

Checklist

[ ] I have added unit tests to cover my changes.
[ ] I have added integration tests to cover my changes.
[ ] I have added the description of my changes into CHANGELOG.
[ ] I have updated the documentation accordingly

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below).

# Copyright (C) 2023 Intel Corporation
#
# SPDX-License-Identifier: MIT

Codecov Report
Patch coverage has no change and project coverage change: -0.02 :warning:

Comparison is base (6b15e81) 78.76% compared to head (faf6de5) 78.74%.

Additional details and impacted files
@@                Coverage Diff                 @@
##           releases/1.3.0    #1025      +/-   ##
==================================================
- Coverage           78.76%   78.74%   -0.02%
==================================================
  Files                 237      237
  Lines               27085    27085
  Branches             5404     5404
==================================================
- Hits                21333    21328       -5
- Misses               4492     4494       +2
- Partials             1260     1263       +3

Flag
Coverage Δ

macos-11_Python-3.8
?

ubuntu-20.04_Python-3.8
78.74% <ø> (ø)

windows-2019_Python-3.8
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

In the second paragraph,

"Then, we will export the merged dataset as yolo format."

but no yolo export example cell found in the notebook.

Correct, I updated the introduction and added filter and reindex operations.


GitHub Actions example: GitHub token is required for v2

💁 A GitHub token is required to use the Coveralls GitHub Action as of version 2. This change corrects the example to reflect that.

🙋 @littleforest, would you please approve the pending workflows when you have a chance?

Hi @sgerrand. It is my understanding that the GitHub-token option is set to a default value and so not required, per the example.
I have just tested this with the basic usage example to confirm.
    - name: Coveralls
      uses: coverallsapp/github-action@v2

Can you also please verify the same, or share your failing example so we can investigate?
🙏

👋 The failing run I had previously observed was https://github.com/sgerrand/ex_incident_io/actions/runs/9489007509/job/26149309040 – perhaps the failure was due to something else. Apologies if that was the case.

I've just confirmed that the action works without that key being specified. Sorry for the noise!


Help flag pukes when a configuration file is not found

When there is not a configuration file found, the restclient pukes on the help menu. This should not happen since the help menu exists to help someone build a config file.

This didn't just happen with the --help menu. It occurred with every argument. It should have thrown a nicer error, but I fixed it with issue #7 by creating a configuration wizard if the configuration file isn't found or is empty.


Changing DEPTH to RADIUS error 3D model

input.zip
Hi Kuangdai,
I hope you are well. I'm doing some test runs on my laptop to get a 3D model working and I’m not sure if there’s just a typo in my input files (attached), but when I change the coordinates.vertical parameter from “DEPTH” to “RADIUS” in the 3D model section I get the error message:
!!!!!!!!!!!! AxiSEM3D ABORTED UPON RUNTIME EXCEPTION !!!!!!!!!!!
FROM: sg_tools::inparamVertical
WHAT: Parameter coordinates:vertical must be either RADIUS or DEPTH.
Model name: Mantle_Vel_Gradient_Blob
Class name: StructuredGridV3D
TIME: 2020-12-17T11:38:06
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I can just change my model to use depth rather than radius but just wanted to check what I was doing wrong or if there was a bug. In input.zip are the input files and the code used to make the 3D model.
Cheers,
Jamie

Thanks. There was a typo in the code. Fixed.


semtech udp parsing error invalid Json string for TxAck frame

It seems that some semtech json stuff from my kerlink iFemToCell ( not helium hotspot, vanilia iFemToCell) is not correctly managed by the gateway-rs software.
INFO uplink @2523639308 us, 904.90 MHz, Ok(DataRate(SF10, BW125)), snr: -8.2, rssi: -123, len: 23 from 72:76:FF:00:39:03:00:AE, module: gateway
 INFO rx1 downlink @2528639308 us, 926.30 MHz, DataRate(SF10, BW500), len: 17 via 72:76:FF:00:39:03:00:AE, module: gateway
 WARN ignoring semtech udp parsing error invalid Json string for TxAck frame: . JsonError: expected value at line 1 column 1, raw bytes [2, 139, 165, 5, 114, 118, 255, 0, 57, 3, 0, 174, 0], module: gateway
 WARN ignoring rx1 downlink error: SendTimeout, module: gateway

here is what I see as json, I assume it is somewhere else:
 {"rxpk":[{"tmst":1337602716,"time":"2022-07-18T06:57:39Z","chan":0,"rfch":0,"freq":903.900000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-4.5,"rssi":-125,"size":23,"data":"AJouPdfv+YFgmGG/w5b5gWDh2Ut7KjY="}]

here is what I see as json, I assume it is somewhere else:
 {"rxpk":[{"tmst":1337602716,"time":"2022-07-18T06:57:39Z","chan":0,"rfch":0,"freq":903.900000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-4.5,"rssi":-125,"size":23,"data":"AJouPdfv+YFgmGG/w5b5gWDh2Ut7KjY="}]

Thanks.. looks like @lthiery has a fix in the works. Looks like this forwarder encodes the null in a cstring somehow :/


v0.7.0 fails to compile.

When using freshly installed v0.7.0 i get the following compilation errors:
Performing "debug" build using /usr/bin/ldc2 for x86_64. serverino 0.7.0: target for configuration "lib" is up to date. matura-api ~master: building configuration "application"... ../.dub/packages/serverino-0.7.0/serverino/source/serverino/daemon.d(491,61): Error: no property releasefor typestd.socket.Socket../.dub/packages/serverino-0.7.0/serverino/source/serverino/main.d(187,59): Error: template instanceserverino.daemon.Daemon.wake!(app)error instantiating ../.dub/packages/serverino-0.7.0/serverino/source/serverino/main.d(158,14):        instantiated from here:wakeServerino!(app) /usr/bin/ldc2 failed with exit code 1.
The error dissapears when chenged to v0.6.5

Hi @IGIAG. Probably you have a old version of dmd. Socket.release() was added in a recent version of dlang. Could you check which version are you running?

Ok, released a new minor version. If you're using a old compiler, websockets are disabled and a warning is shown.
You can also build your project without websockets using the config disable_websockets


stuck on chrome page

Hi,
When I start the bot, after the connexion to windscribe, I have this error 'the process "chome.exe" not found', then, it goes to that page and get stuck here.

(Also there are other websites such as clictune where it may be possible to do similar projects, if you are interested)

This almost definitely because of your keyboard layout, I had the same problem using Danish keyboard layout. The ":" is replaced with "/". Also the chrome.exe not found is nothing you should worry about. Hope it helps  :D
@softmachine1

@KevinGeLe  is correct about this, the "chrome.exe" not found is nothing, its normal. and the webpage not found is because of the ":" replaced with "/", try to stop the code in the VM and set the keyboard layout to ENglish, it wont matter to you anyways.
@softmachine1


[LoadingButton] Fix variant default prop not inheriting from MuiButton theme slot

[x] I have followed (at least) the PR section of the contributing guide.

Fixes #29740

Not sure why this is closed. Attempting to set MuiButton variant property using defaultProps does not seem to work, as of 5.8.7. Can we reopen, or should I open another issue?

This is an issue in version 5.8.7, perhaps a regression?


LogAnalytics: update readme and fix conflicts by autorest.java

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run unifiedPipeline

Hi, @xseeseesee. The PR has be closed for a long time and it's related branch still exist. If no further used for over 14 days, I will delete this related branch. Please tell me if you still need this branch.

Hi, @xseeseesee. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.