File not found when doing local install from folder

Hey there,
helm version
Client: &version.Version{SemVer:"v2.2.2", GitCommit:"1b330722aafcb8123114ae51f69d1e884a326f3e", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.0", GitCommit:"08c1144f5eb3e3b636d9775617287cc26e53dba4", GitTreeState:"clean"}

I cant do local install at all. From repos it works good.
For example i try to make that one
helm install --name prometheus-operator --set rbacEnable=true --namespace=monitoring helm/prometheus-operator

There is an error
Error: file "helm/prometheus-operator" not found

But ls helm/prometheus-operator shows
Chart.yaml  README.md  templates  values.yaml

Can you try ./helm/Prometheus-operator instead? Helm recognizes ./ as a reference to a local file path. Let me know if that works.

I also noticed that your client version is very out of date. Try updating that to v2.7.0 and try again.

@bacongobbler  I tried, no results. Well, i searched the whole universe and did not found how to update client (there is a part in documentation only about updating tiller)

Just fetch one of the releases from https://github.com/kubernetes/helm/releases and put in in your path, Alternatively, if you're on macOS try brew install kubernetes-helm.

@bacongobbler Thanks, now everything is perfect!

No problem :)


Add CNA handler

Update handler for CNA
Tests

https://www.reddit.com/r/rsgretrivr/comments/ca8nyg/murders_and_fights_but_some_tenants_say_orchard/
https://www.reddit.com/r/rsgretrivr/comments/ca8sor/new_national_dental_centre_set_up_to_cope_with/
https://www.reddit.com/r/rsgretrivr/comments/ca96vz/new_spca_upgraded_clinic_officially_opens_video/

The handler now uses lxml (already installed as dependencies in newspaper3k package) instead of Python’s html.parser for more accuracy when parsing HTML using BeautifulSoup.

@fterh Requiring forks to also setup Travis seems a bit onerous -- was that a deliberate decision? What do you think of having just PR Travis build on the original repo for now?

@changhuapeng Sorry, I missed this PR completely, for some reason I didn't get any notification. My internship ends this week, I'll take a look first thing next week. But if the tests pass, it should be fine, looks good!
@yleong No it wasn't a deliberate decision, I wasn't aware that happened o.o I hope I'm not misunderstanding you, you are suggesting to disable the "Travis CI - Branch" status check, and only leaving "Travis CI - Pull Request" right?

@fterh I'm not super familiar with Github-Travis integration too, but yeah, I was referring to disabling the Branch check and just relying on the Pull Request one.


Add LICENSE file to v_frame

Closes #2610

Coverage decreased (-0.5%) to 65.525% when pulling 3b316c91568bf1383d14f092d8d670252bdec560 on eclipseo:patch-1 into 81c9ee0cae80fa5e39fc6c0301aae72414d99c06 on xiph:master.


DB-4068 cherry-pick upstream HttpRequest/ObjectDecoder fixes (4.1.34/bdp master)

https://datastax.jira.com/browse/DB-4068
This is similar to #20, except this PR skips the first two cherries in that one's sequence (already applied upstream between 4.1.25 and 4.1.34).

I've force-pushed an amended tip-commit  updating the bom/pom.xml <version> and deleting <scm><tag> versions.  This amendment is structurally identical to the one described here: https://github.com/riptano/netty/pull/22#issuecomment-610328391.


CORE-7288 Add digest service for flows

WIP
runtime-os PR: #2502

Registered CORE-8151 to provide:

default digest algorithm
supported digest algorithms APIs


User-written scripts not registered to the GC, leading to confusing memory corruption.

Godot has it's own memory management, so there is no need for the D garbage collector to collect the script classes themselves.
However, consider a regular D array, allocated on the heap by the script:
class MissionResult : GodotScript!Node
{   alias owner this;
    int[] hits;

    @Method void _ready()
    {   if (Engine.isEditorHint()) return;
        hits = new int[](targetNames.length);
    }
}

This results in memory corruption! Since the D GC doesn't know about the MissionResult instance, it won't find any reference to the ints referred to by hits, and will therefore collect them the next time it needs to collect. It's especially confusing since hits usually seems to work right at first, but will then get strange values and at some point crash.
Ideally, there would be a global pool of Object references that the GC knows about, and createFunc and destroyFunc templates would add/remove references to the scripts to/from the said pool.
Now, I understand that Godot is designed to work without a garbage collector, so it might not be desirable to do this for all scripts. I think it should be done by default, though. The times when the GC has to be avoided are relatively rare, but the dangling pointer bugs with the present situation are really likely to happen and confusing when they do. Yes, the Godot data structures are good workarounds that don't suffer from this problem, but still.

Docs should mention that all allocations should be done with memnew, paired with memdelete calls.
There is no way to register all of Godot threads with D runtime, so any GC memory will be insta-freed.

There is no way to register all of Godot threads with D runtime, so any GC memory will be insta-freed.

You're thinking about scanning the stack and thread-local storage, right? There's no need to register all threads. Only those that run D code using the GC-controlled heap.
It seems the main scene-handling thread is the same that gets registered when DRuntime is initialised. I worked around my problem by storing a reference to each hits array to a static int[][] array. That did stop the memory corruption, meaning the runtime is aware of the thread where D scripts are run. Unless I'm mistaken, Godot doesn't do any multi-threading for scripts unless explicitly told to.
As for other threads that need to use the GC-controlled heap, thread_attachThis looks to me like it'd solve the problem. It needs to be called manually by the D script running in another thread, but it's better than no GC at least sometimes.

just some thoughts:

godot doesn't run multi-thread scripts by default, there is however some parts of the engine when it does access them from other threads
main thread (i.e. the one which godot runs its main loop, loads extension and runs scripts) should be registered automatically by D runtime, otherwise even having static array of "pinned" pointers won't work, right?

now an interesting part

scene nodes (any D object derived from node) actually might just work if one registers Godot's get_tree().root within GC https://dlang.org/phobos/core_memory.html#.GC.addRoot
plain Godot objects (derived from any class above Node in D) is a bit more complicated, I'm not so sure if Godot even tracks them because this is exactly what RefCounted does and plain Object has to be destroyed manually, so it seems pretty much any allocated non-Node object should be registered with GC.

just some thoughts:
* godot doesn't run multi-thread scripts by default, there is however some parts of the engine when it does access them from other threads

When explicitly calling the scripts from other threads, certainly. That page I linked even says it might be better to use threading facilities of the language when it's not GdScript, which seems excellent advice in case of D. But are there any other cases?

* main thread (i.e. the one which godot runs its main loop, loads extension and runs scripts) should be registered automatically by D runtime, otherwise even having static array of "pinned" pointers won't work, right?

That's right, unless that pinned pointer array was shared or __gshared, which it wasn't. I also verified it by running Thread.getThis.isMainThread from a Godot script, which said "true". If the thread wasn't registered, it would have crashed since Thread.getThis returns null if the thread is not registered.

now an interesting part
* scene nodes (any D object derived from node) actually might just work if one registers Godot's `get_tree().root` within GC https://dlang.org/phobos/core_memory.html#.GC.addRoot

Unfortunately I don't think that works. The runtime would be aware of the root itself, and if it happens to contain any direct pointer to GC-allocated memory, that wouldn't get collected. But the pointers to other nodes still point to nowhere from perspective of the runtime, since the nodes are not controlled by the garbage collector. Thus it wouldn't recursively scan the whole tree.
Which also means my original proposal (global pool of pointers to nodes) wouldn't work. They would be "pointing to nowhere" from GC perspective just like pointers in the root node in your idea. This trick worked in my test since the pointers in the pool were pointing directly to the GC:d array, not the node.

* plain Godot objects (derived from any class above Node in D) is a bit more complicated, I'm not so sure if Godot even tracks them because this is exactly what RefCounted does and plain Object has to be destroyed manually, so it seems pretty much any allocated non-Node object should be registered with GC.

The problem is not freeing the node in itself. Godot mechanisms for freeing that work just as well as they work for GdScript. The problem is freeing of any GC-collected memory allocated by the node. This issue applies equally to all D-written Godot objects, whether deleted with the root node, RefCounted or manually freed.
What might work is a variation of my original idea. createFunc and destoryFunc, instead of using a global pointer pool, would register/unregister the node to the GC as a root that isn't itself collected, with GC.addRange and GC.removeRange. That way, the GC should scan them as long as they exist, and when they get freed by Godot, regardless of mechanism, the GC is again informed.

The problem with adding bookmarks in createFunc is that it will make extra memory overhead, does every user really needs that? The answer is definitely no.
Therefore the suggested way is to allocate it yourself and only when needed, and while I'm not 100% sure it works every time I think regular scene nodes works fine as is.
For the rest of it even though it is somewhat cumbersome to do one can manually allocate/deallocate by using ctor/dtor.
This way it should provide fine-grained control over memory allocations without going full control freak mode as in C++.
Now there is another concern, adding infinitely large number of small memory ranges may or may not actually destroy performance, so the common practice anyway is to pool things(pool buffer, arena allocators, etc...), and this is somewhat orthogonal to pinning by default proposed to do on object creation in createFunc.
I mean if there is a solution that just works for everyone than sure I'm all in for it, but there is just too many tradeoffs that i'm still not aware of.
So, am I wrong?

I mean if there is a solution that just works for everyone than sure I'm all in for it, but there is just too many tradeoffs that i'm still not aware of.

Ultimately I think it depends much on what DRuntime does. It's supposed to scan it's internal list of addRanged memory ranges just like it'd scan a shared void[][] - so there is no reason why it should be much slower than a custom pointer pool would be. But it's possible it's not implemented efficiently - even if the scanning itself is, maybe adding and removing the ranges isn't.
But I also think that if the scripts can be scanned, even with a cost of some efficiency (not meaning total destruction of it), it's worth it. GdScript is almost entirely memory safe to use: even if you use a freed Godot object, you will get a principled error as opposed to random crashes and memory corruption that's the case with cstdlib free. This means there's potential to bring the same safety to D scripts, as long as the user stays within @safe D. Of course, godot-dlang isn't currently annotated as safe, but the potential is there and even without actually using the attribute it'd work quite well in practice. But this requires there are no footguns with using the GC normally.
But I agree that that there should probably be an UDA for turning the GC scanning off for that script.

So, am I wrong?

It's not right nor wrong, it's a design decision. Since you're the main developer, it's what convinces you that should ultimately get in, not what convinces me. I can post opinions but I understand that it's you picking the direction in the end.
I will read the DRuntime source code and post a further opinion on using addRange/deleteRange later, unless you immediately decide against using them.

Investigation done!
DRuntime internally uses treaps to store the scan ranges. This is definitely scalable, since the treaps are linked tree type structures, so there will never be massive reallocations all at once that would be the case were the ranges stored in monolithic arrays. But it does call malloc or free each time a scan range is added or removed, so it looked like pretty slow at small scale to me. How much? I decided it was best to stop guessing and benchmark it instead. You can check and redo the tests yourself if you think I got something wrong:
import core.memory : GC;
import std;
import std.datetime.stopwatch : StopWatch;

static import cstd = core.stdc.stdlib;

void main(string[] args)
{   // When true, we simulate using addRoot for Godot.
    // When false, we benchamark using our own pointer pool
    //   instead for comparison.
    bool useRangeAdder = {
        if (args.length != 2) throw new Exception("Two arguments please!");
        return args[1].to!bool;
    }();

    StopWatch timer;

    // Half a million void arrays, their contents simulating our Godot objects.
    // Not scanned by the GC, because it's allocated with malloc.
    auto unscannedList =
        (cast(void[]*) cstd.malloc(0x8_0000 * (void[]).sizeof))[0 .. 0x8_0000];

    // An array would be unrealistic as a general-purpose pointer pool
    // because it doesn't lend itself to removing
    // items efficiently from the middle. I believe this
    // would be a better choice.
    auto pointerPool = new RedBlackTree!(void*);

    timer.start();

    if (useRangeAdder) foreach(ref item; unscannedList)
    {   // Manually allocate the "Godot object"
        item = cstd.malloc(64)[0 .. 64];
        (cast(ubyte[]) item)[] = 0;

        // Add it manually to GC as a place to scan.
        GC.addRange(item.ptr, item.length);
    } else foreach(ref item; unscannedList)
    {   // Allocate the "Godot object" by GC, because it wouldn't get scanned
        // if we mallocated it.
        item = new void[](64);

        // Copy the pointer to it to the pool so the GC will find it.
        pointerPool.insert(item.ptr);
    }

    writeln("Allocations took ", timer.peek);
    timer.reset();

    GC.collect();
    writeln("GC took ", timer.peek);
    timer.reset();

    // now we deallocate every other object
    if (useRangeAdder) foreach(ref item; unscannedList.stride(2))
    {   GC.removeRange(item.ptr);
        cstd.free(item.ptr);
        item = null;
    } else foreach(ref item; unscannedList.stride(2))
    {   pointerPool.removeKey(item.ptr);
        item = null;
    }

    writeln("Deallocations took ", timer.peek);
    timer.reset();

    GC.collect();
    writeln("Another GC took ", timer.peek);
}

Result:
$ dmd -O -run app.d true
Allocations took 92 ms, 119 μs, and 5 hnsecs
GC took 27 ms, 459 μs, and 7 hnsecs
Deallocations took 64 ms, 513 μs, and 1 hnsec
Another GC took 22 ms, 474 μs, and 7 hnsecs

$ dmd -O -run app.d false
Allocations took 257 ms and 354 μs
GC took 39 ms, 265 μs, and 7 hnsecs
Deallocations took 46 ms, 926 μs, and 3 hnsecs
Another GC took 19 ms and 850 μs

it seems that addRange / removeRange are actually faster than a pointer pool would be! Plus, in this test the pointer pool actually has an advantage, because it doesn't have to be thread-safe, unlike the treaps at DRuntime, or a real pointer pool that was designed to work from many threads.
For me it seems addRange and removeRange are not going to cause any more performance trouble than the GC in general does.

Ok, thanks for your time on this investigation.
I think we can add new attribute to let createFunc/destroyFunc knows if memory should be added to GC scan, this way users will be able to control it AND this will be purely in opt-in manner.
Can't say if this is going to be safe, because for example any integer may cause false positives???
However there is few things I still don't understand about your specific issue, you say that regular D array in your GodotScript is "lost", however as long as your script entity is alive it means the array is still referenced by that object even though GC is not controlling the object itself.
Now how does GC.addRange(p, len) will help in this case if there is this line in the docs about it?

if p points into a GC-managed memory block, addRange does not mark this block as live.

Sure it doesn't mentions non GC-managed memory as it has no control over it and it has different purpose but still.

Can't say if this is going to be safe, because for example any integer may cause false positives???

Yes it is - and this is normal! At least formerly the D garbage collector was conservative, which means it just treats everything as a pointer (unless it can forgo scanning the memory area completely - think a character array, for example). A non-conservative GC is called "precise" - there have been efforts to make D GC precise but I'm not sure how that's going and if it's currently the default. Anyway, it has been conservative for most of D history without being a major problem. A conservative GC just means the object will sometimes not be freed at the first possible collection. It might in rare cases cause problems with memory leaks but it's not a memory safety problem.

you say that regular D array in your GodotScript is "lost", however as long as your script entity is alive it means the array is still referenced by that object even though GC is not controlling the object itself.

The GC starts by scanning the stack, thread-local storage (meaning static and global variables), shared variables and all addRanged memory. When it comes across a pointer:

if it points to a memory area allocated by the GC, it scans that too (unless it's typed as something that doesn't contain any pointers).
If it points somewhere else, it ignores it. This includes pointers to mallocated memory or other foreign memory allocation schemes.

Since the Godot object is allocated and deallocated by Godot, not by the D GC, it will not get scanned regardless of whether there are pointers to it. It will get scanned only if it is in the stack (meaning instanced there, not just referred to from there), or global memory, or addRanged to the GC.

if p points into a GC-managed memory block, addRange does not mark this block as live.

This means that addRange will not prevent the added memory itself getting garbage collected if it is allocated by the garbage collector. addRange is primarily meant for non-GCd memory anyway. If you wanted to "pin" something you allocated with the GC, addRoot would be a better choice.

Otherwise agreed, but it seems better than scan would happen by default, attributes (whether global or per-range, or both) would opt out. Avoiding the GC is kinda an advanced topic that's not often needed, but no-one want's bugs like what this topic is about. Better beginner-friendly by default.
But regardless of the default, it at least solves the issue so it's not like I'd be unhappy if you disagree.

Yeah, I decided to go with in enabled by default.
Also I haven't thoroughly tested yet but it seems like this fixed an issue in my own scripts where suddenly part of a string got overwritten by another thread (usually just few chars in front but this destroys the paths) even though that script is protected with mutexes.

Great!


Support data type syntax [Puppet 4]

From https://docs.puppet.com/puppet/latest/lang_data_type.html#parameter-lists
class ntp (
  Boolean $service_manage = true,
  Boolean $autoupdate     = false,
  String  $package_ensure = 'present',
  # ...
) {
  # ...
}

I added support for the define/class declaration syntax, and the selector syntax. At least the case syntax is missing, but it would be awesome if you could test it!

I have been using the master version for a while without problem. I am still using the puppet4 syntax scarcely but I would suggest to make a new release with the current changes (so I can more easily test it with more catalogs).
As an aside, the point that worries me the most for the moment is the dot alternative syntax for lambda and cie ($binaries.each |String $binary| {). I guess I should fill in a new issue about that.

Ah, that might not be too much trouble to add.

Uploaded 1.3.8

I just pushed datatype syntax support in lambda expressions.

Isn't this supposed to work ?
$xs =  ["hello", "world"]
each($xs) |String $x| {
}

I was trying it but got:
unexpected '|'
expecting '}', Statement, or rest of Statement


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_d6ee2524-7b32-4316-9846-ab4d752e6566/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_d6ee2524-7b32-4316-9846-ab4d752e6566.git

Docs Build status updates of commit 24f17a3:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2022-01-06-03-55-24 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Viewport gets distorted by addresses

The long length of addresses (such as 0x9ff48eeb5e408f691ce8752a6ef73a3f2a7a6d7739fa4788ad1587c6336c6499) in the markdown text does not wrap. This causes the mobile viewport to add a horse scroll bar.
Force the address to wrap to prevent the scroll bar. There is an example of this in BeaconItem.vue. This will require the addresses be wrapped in code elements with an a style. A class can be used if added to index.styl.
.beacon-id {
  max-width: 550px; // May not be needed
  overflow-wrap: break-word;
}

 0x9ff48eeb5e408f691ce8752a6ef73a3f2a7a6d7739fa4788ad1587c6336c6499

This has been moved to the JIRA board AN-540.


Add ability to download microphone data

Contents (#24)
New features

Add method for getting microphone metadata
Add method for downloading microphone data

Refactoring

Factor out dataset name

Style

Update isort pre-commit check
Improve isort config and run pre-commit on all files

Any thoughts or should I just merge @JuliusPlindastus @time-trader?

Hi @cortadocodes, I've just tested, and it works like a charm. Thanks!
My first time I have been asked to review. What's the best way to validate it? "Merge pull request"?

Great to hear @JuliusPlindastus! You can click "approve" within the "review changes" button at the top right of the "files changed" page. I can merge it without you doing that though so feel free to approve or not


/usr/lib/python2.7/site-packages is ignored by python

In my docker file I run apk add with some package which also includes python module.
It's ok on clear alpine base with apk add python and so on.
But when I try to use python:2.7-alpine as base image I get import error from my script using that module (placed in /usr/lib/python2.7/site-packages/)
The problem is that python sys.path does not contain it:
['', '/usr/local/lib/python27.zip', '/usr/local/lib/python2.7', '/usr/local/lib/python2.7/plat-linux2', '/usr/local/lib/python2.7/lib-tk', '/usr/local/lib/python2.7/lib-old', '/usr/local/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/site-packages']
As a workaround I can use
export PYTHONPATH=/usr/lib/python2.7/site-packages:$PYTHONPATH
I lost about 3 hour of my life with this problem.

Previous issue on this https://github.com/docker-library/python/issues/43#issuecomment-376351096

For cases like those, our compiled Python isn't likely to be sufficient for the package's needs, and it will likely make assumptions about the way Debian/Ubuntu distribute and compile Python, so in those cases you're definitely better off installing Python from Debian or Ubuntu directly to then install their .deb file on top.

if you need packages from Debian, you should probably go FROM debian:xxx and install Python itself from Debian too

I does not use something from Debian or Ubuntu - only alpine repositories and packages.

Alpine in this regard isn't any different, if you need that package then you should probably go FROM alpine and install Python and that package from Alpine's repo as our compiled Python may not be sufficient for what the package expects.
What package/module is it?

It's Suricata IDS and suricatasc.py.
But why not build "official" image with apk add python? Why do you compile it from source instead?

So for that you could either compile it from source in a Dockerfile FROM python
Or install the package in a Dockerfile FROM alpine with any required dependencies
https://github.com/docker-library/faq#why-do-so-many-official-images-build-from-source

Yes, it's what I did before. Thank you for assistance.
But the idea of compilation from sources ignoring repositories looks like we have a huge methodology inconsistency problem.

The versions of Python in the repositories of the stable Alpine and Debian releases are going to (usually intentionally) lag behind upstream's "latest and greatest" which is the biggest reason we compile from source in this particular case.

I thought there are some strong reasons why it lags (like regression testing or security review). Repository for me is like quality mark.


[WIP] CoreCLR port

I was interested in running on coreclr, so i didn't use #if statements. Hope this helps.
Do you have plans to support CoreCLR?

This would be incredibly useful if this library can become compatible with .NET Core, I'm working on an ASP.NET 5 project atm and would like to use this library, but unfortunately it will only target standard .NET Framework atm :(

@antonmes -
Thanks for the contribution! Yes, we plan on supporting CoreCLR...we were going to create a separate branch for CoreCLR so that there are no conflicts for users targeting older CLR versions.
You kind of beat me to the punch here, I was planning on branching after 2.2.3 which is planned for the first week of January. Perhaps you could rebase this on top of the core-clr branch once we get one in place?
Sorry I didn't respond sooner, I have been on (partial) medical leave for the last couple of weeks.
-Thanks
Jeff

Hey @antonmes, Jeff and I just talked about how to handle this.  This is definitely something we want to work on!  We think we'll need some more work before the merge to master though, so for now what we're going to do is create a feature branch where we work on updates/rebasing/etc.  It'll probably be January before we get into serious work, but wanted to let you know what's happening.
Thanks!

Merged to new branch feature/CoreCLR, where we'll work on this for merging into master.

@jeffrymorris, @ingenthr sorry, I didn't mean merging into master, just wanted to share some thoughts and save some time ;) thanks for answering! I can close this PR, right?

@antonmes no problem, go ahead and close it. We'll use the feature branch for reference and probably create a new one after 2.2.3 is released for core clr.
Thanks,
Jeff

Hey guys, you can delete feature/CoreCLR if you wish. Thanks!


Update 1.10.2 - BUGG ? waybill generation issues/problem in meeting page

I have tried to generate new waybill thru the meeting page ( module )The system doesn´t generate any waybill at all.

This works now.


Multiwoz evaluation

Hi, thank you for sharing the code!
I appreciate your work and I have a question.
The original MultiWoz evaluate.py calculates the INFORM score by checking if the first offered venue is correct or not.
elif len(venue_offered[domain]) > 0 and venue_offered[domain][0] in goal_venues: match += 1
However your evaluation code is checking if there's an overlap between offered venues and goal venues.
elif len(venue_offered[domain]) > 0 and len(set(venue_offered[domain])& set(goal_venues))>0: match += 1
Doesn't it lead to a higher score than the original evaluation code?

Hi,
We use this checking criterion because it can return a deterministic score for the same set of offered venues under different runs. In the original setting, the match score depends on the order of the venues which is random. Because any venue that meets the search constraint can be the "first offered venue", such randomness does not make sense. Our setting corresponds to the most optimistic results the original evaluation setting can obtain, when one of the overlaps is always returned as the first offered venue. In other words, our criterion is no better than the best score the original criterion can get. I remember that the largest gain of using our criterion is less than 0.5 on the match rate (not sure since this was done a long time ago), which may suggest that the difference is minimal.
Besides, these two criteria both have a problem. The offered venue is still possible to match the user's goal even if the system's belief in the user goals (informable slot values) does not exactly match the real user goal. Such lucky successes should be avoided, which can be done by comparing whether the set of offered venues is the same as the goal venues.
Hope this can help.

Hello guys,
I am currently going through evaluation scripts of several recent systems so I just would like to mention a few things here. @594zyc is right that this is an optimistic evaluation and that both criteria have a problem. I think that checking whether the set of offered venues is a non-empty subset of the set of venues complying the dialog goal makes more sense. It can be seen in MarCo and HDSA.
Also note that DAMD uses reduced database queries when a venue name is in search constraints (see these lines). I think that this also overestimates the actual system's performance, because previous ground-truth responses (including ground-truth names) are used as context during evaluation. And so the right venue name can be copied into the predicted dialog state in later turns and all the DST done up to this point (which might contradict the dialog goal) is in fact discarded.
All the best :slightly_smiling_face:

Hi, thank you both for answering!
As @Tomiinek said, I feel checking whether the set of offered venues is a non-empty subset of the set of venues makes sense.
However, for venue name constraints, I think the original evaluation code has the same logic here. So I guess it will be okay.

However, for venue name constraints, I think the original evaluation code has the same logic here. So I guess it will be okay.

No, I am afraid it is not. The logic you link accepts a dialog as matching if the name of a venue is in the dialog goal, i.e. the crowd worker was instructed to mention it during the data collection and the name is probably somewhere in user utterances.
However, the name constraints in case of DAMD is related to system responses only. If the user was not instructed to mention the name, we should rely just on the model predictions during evaluation. But the problem is that the predictions can be ignored later in the dialog if the reduced set of constraints is used for querying the database.
:thought_balloon:  The Inform Rate assesses if for each domain contained in the dialogue, the last mentioned entity (venue name or train id) for that domain match the requirements in the user's goal.

If the user was not instructed to mention the name, we should rely just on the model predictions during evaluation.

If the user wasn't instructed to mention the name, I thought the constraint would not have the name, so we just rely on the model predictions. Is it wrong to think this way?

The evaluation uses ground-truth utterances in the context, because there is no user simulator.
Let me think of an example:

The user is looking for a pricerange: cheap, food: Chinese restaurant. She is not instructed to mention a name, she just want to find out a cheap Chinese restaurant and its postcode.
The model at some point makes a mistake predicting a state pricerange: moderate, food: Chinese, and informs the user with "I have [name_restaraunt] matching your request, would you like me to book it for you?". Because the [name_restaurant] was mentioned, the set of offerend venues is updated. This set isn't a subset of the set of goal venues, so the dialog is not matching at this point.
And now comes the problem. The next turn is generated using the ground-truth context, so it can contain something similar to  "USR: Could you find me a cheap Chinese restaurant? SYS: Sure, I have Golden dragon matching your request, do you like it?". If the user now asks for example for the post code, i.e. "Yes I do, give me its postcode please.", the model can predict a partially incorrect state such as pricerange: moderate, food: Chinese, name: Golden dragon and inform the user with a utterance such as "[name_restaurant] postcode is [postcode]". The list of offered venues is changed again, because the name slot was encountered. The DAMD database ignores the pricerange and food slots and so the set of offered venues is now a non-empty subset of the goal venues and whole dialog is matching. However, the model saw the name of the restaurant in the ground-truth context and other problems with state tracking are ignored.

This problem can be emphasized in case of models that use a cumulative state and predict just changes of the state at each turn (e.g., MinTL).
The database like this makes of course perfect sense when chatting interactively with a human. But IMHO it overestimates the performance during the evaluation with ground-truth context utterances. Simply because the context might contain a venue name that the system couldn't offer.

Thanks for your detailed explanation! I understand what you're talking about.
If we use the ground truth context, it can be problematic.
However, what do you think when using the generated context as input? Do you think it's okay to only use name constraint (if it exists) for database query?

Yes, I think it is ok in this case :slightly_smiling_face:


Administrator filter doesn't catch Basic Admins

Issue
Logged in as a Super Admin, I go to the Users page of the Admin UI, click on the Administrator? filter and set it to "Yes", then click Apply. Only Super Admins appear in the list, no Basic Admins from any country appear.

Acceptance Criteria

[x] When I set the Administrator? filter to "Yes", and click Apply, a list of all admins, both Basic and Super, appear.
[x] When I add additional filters like "Base Country", the list is appropriately restricted to only those admins with a Base Country of X.

Housekeeping (where applicable)

[ ] Unit test/s written
[ ] i18n strings included
[ ] Is accessible to people using screen readers

Something I just noticed on Prod is that it's displaying some users besides Super Admins -- Mashal and Emily.
Guess: It's related to their Django permissions? (Mashal has more permissions than most because of her Workflow admin responsibilities.)

The Admin filter is now working as expected. All criteria passed.


LNK1104 cannot open file " .lib"

Hi, I'm trying to build the unimrcp 1.5 ver open source code on Visual studio 2017 with no edit to the code but end up getting this link error shown below;
" Error	LNK1104	cannot open file 'libunimrcpserver.lib mrcpsofiasip.lib mrcpunirtsp.lib unirtsp.lib mrcpserver.lib mrcpv2transport.lib mrcpsignaling.lib mrcpengine.lib mrcp.lib mpf.lib aprtoolkit.lib libaprutil-1.lib libapr-1.lib libsofia_sip_ua.lib ws2_32.lib winmm.lib'	"
These libraries are created in the ..\Debug\lib folder while building and I have tried including this path explicitly almost everywhere but with no luck.
"output_log.txt" is attached with the post, which shows the entire unimrcp project build log.
output_log.txt
I'm sure there is something that I am missing, if anyone could point in the right direction it would be of great help. Thanks!

Hi,
It does not seem you are using the released version. I noticed an additional module/plugin in the build log. The dependencies of the projects might be missing in your solution.
Please use the original release and compare with what you have.


Bug/FR: allow disabling some arguments because anthropic and mistral endpoint don't accept them

Hi,
Disclaimer
I was writing this issue while you answered #105  but now I'm confused as to wether i should post this one or not.
You said:

Mistran is not supported

and

don't give any warranties that non-OpenAI endpoints will fully compatible and all subsequent issues will be closed.

But the README says about endpoints:

Other (must be tested by community, don't be shy and provide your feedback)

For that and because I'm not sure if that's something that would best be solved in openai-kotlin or if that has more to do with arguments specified by SpeakGPT, I decided to post this issue to provide feedback because that would avoid hard crashes for some some endpoints (at least mistral and probably anthropic).
The issue
The mistral endpoint cannot currently be used: https://api.mistral.ai/v1/. I'm fairly that's because there's a mismatch in argument compatibility.
There's a lib called LiteLLM that provides a common python API to reach many LLM endpoints and their solution was to add a drop_params argument that drops any argument that is not supported by the specific endpoint.
As you can see in their API the mistral models don't expose logit_bias, presence penalty etc. But it supports additional arguments for example "safe_prompt".
I totally understand that SpeakGPT does not provide warranties for supporting any endpoints, but still decided to provide this feedback. I think a solution would be to allow disabling arguments per endpoint, but I of course totally understand if you think the changes are too involved and unecessary.
If you don't mind I'll post my suggestion on what maybe the easiest general solution would be:

add a list of checkbox in the "Edit API endpoint" window to selectively disable arguments like logit bias, temperature, top_p, frequency_penalty, presence_penalty. Also to disable vision or not.
add a field "extra argument" because some endpoints, can support some, for example mistral has a safe_prompt argument. But I'm sure in the future there will be many more specificities like that. For example anthropic does not have the penalty arguments
Optional: Automatically greying out the options in the quick settings if the selected endpoint does not support them, and hiding the "share image" buttons if vision is disabled.

The full error can be found below:
Expand

An error has been occurred during generation. See the error details below:

m2.a
	at w2.d.c(Unknown Source:131)
	at w2.d.a(Unknown Source:13)
	at w2.d.i(Unknown Source:89)
	at w2.c.m(Unknown Source:12)
	at x8.a.g(Unknown Source:5)
	at n9.k0.run(Unknown Source:101)
	at android.os.Handler.handleCallback(Handler.java:959)
	at android.os.Handler.dispatchMessage(Handler.java:100)
	at android.os.Looper.loopOnce(Looper.java:232)
	at android.os.Looper.loop(Looper.java:317)
	at android.app.ActivityThread.main(ActivityThread.java:8532)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
	at com.android.internal.os.ExecInit.main(ExecInit.java:50)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:359)
Caused by: g7.e: Client request(POST https://api.mistral.ai/v1/chat/completions) invalid: 422 Unprocessable Entity. Text: "{"object":"error","message":{"detail":[{"type":"extra_forbidden","loc":["body","presence_penalty"],"msg":"Extra inputs are not permitted","input":0.0,"url":"https://errors.pydantic.dev/2.6/v/extra_forbidden"},{"type":"extra_forbidden","loc":["body","frequency_penalty"],"msg":"Extra inputs are not permitted","input":0.0,"url":"https://errors.pydantic.dev/2.6/v/extra_forbidden"}]},"type":"invalid_request_error","param":null,"code":null}"
	at g7.j.m(Unknown Source:218)
	at g7.j.i(Unknown Source:12)
	at g7.u.b(Unknown Source:116)
	at a7.b.m(Unknown Source:461)
	at x8.a.g(Unknown Source:5)
	at n9.k0.run(Unknown Source:109)
	... 10 more

(Sorry for the many notification but: I confirm that using the openrouter endpoint and setting the model to mistralai/mistral-large-latest works perflectly fine. So that makes me hopeful that better support with openrouter would be a good way to support many more models without having to change the code too much.)

Fixed in SpeakGPT 3.25

Addendum: I see that in the system prompt window you indicate

Putting a system message at the end of conversation...

I'm pretty sure most LLM expect the system prompt to appear first:

On openai:

Typically, a conversation will start with a system message that tells the assistant how to behave

Also on mistral : https://docs.mistral.ai/api/

For your defense I also read this on openai:

Be aware that gpt-3.5-turbo-0301 does not generally pay as much attention to the system message as gpt-4-0314 or gpt-3.5-turbo-0613. Therefore, for gpt-3.5-turbo-0301, we recommend placing important instructions in the user message instead. Some developers have found success in continually moving the system message near the end of the conversation to keep the model's attention from drifting away as conversations get longer.

But that only applies to models that are not very good and for conversation that are quite long and for models with very short context length.

I think last models are quite powerful and have the big context windows so it's better to append system prompt at the end. Specially for this I run some experiments and noticed that if conversation is big system prompt is being ignored. So it will not be fixed.

Typically, a conversation will start with a system message that tells the assistant how to behave

I checked OpenAI dock now and didn't found such citations. Maybe in your country OpenAI has outdated docs. gpt-3.5-turbo-0301 model is deprecated and possibly shutdown. The whole year has passed since this recommendation is issued. During this period a lot things has changed.

I'm sorry I have given the wrong link : https://cookbook.openai.com/examples/how_to_format_inputs_to_chatgpt_models
That's where both citations come frome.
I strongly suggest aligning with what seems like best practices.
1.This quote from OpenAI:

Typically, a conversation will start with a system message that tells the assistant how to behave

Also from openai:

Be aware that gpt-3.5-turbo-0301 does not generally pay as much attention to the system message as gpt-4-0314 or gpt-3.5-turbo-0613. Therefore, for gpt-3.5-turbo-0301, we recommend placing important instructions in the user message instead. Some developers have found success in continually moving the system message near the end of the conversation to keep the model's attention from drifting away as conversations get longer.

The above quote means that "some developpers" (so it's not common) found a way that is relevant to "to keep the model's attention from drifting away as conversations get longer" so it's only relevant if the attention starts drifting away. Meaning that in all other cases the recommended way is to put the system prompt FIRST. That means that if indeed you tested and noticed that adding the system prompt at the end makes it not be ignored, that also suggest that if you have a 5 message long conversation (so NOT a situation where the attention is drifting away) but added the system prompt at the end then the 2 assistant so far would have been prompted incorrectly (what I mean by that is that the LLM was trained expecting the system prompt to be first so "getting ignored" is not a good test to see if it's properly followed when it's not ignored).

Additionnaly, in the 8 examples I count in the openai cookbook absolutely none contain a system prompt that is not before the user messages.

Another argument is that mistral which, although not officially supported, is a big player in the AI spaces even errors out if the system prompt is not first.

Another argument is that even Llama is expecting the system prompt first:

messages = [
{"role": "system", "content": "You are a pirate chatbot who always responds in pirate speak!"},
{"role": "user", "content": "Who are you?"},
]

To back my claim I also asked perplexity ai and it seems to agree mostly with me:

The dolphin family of fine tunes from someone well known as an example also puts the system prompt first:

I think those are 7 strong arguments, with sources, from OpenAI, Mistral and Meta. If you are still not convinced, I am extremely curious as to what kind of testing you have done that justifies not following what seems to me like established practices.
And to be clear: I'm not asking for another option, I'm asking for SpeakGPT to talk to LLMs the way they were trained.

Receive new update (SpeakGPT 3.26) and close your mouth please (I'm tired and nervouse for now because you sent too much notifications). Thanks!


Error in installing pagination

Hi, thanks for contributing!
This project is maintained in my spare time, so in order to help me address your issue as quickly as
possible, please provide as much of the following information as you can.
-- Michael
=======
Angular 2 version:"@angular/common": "2.0.0-rc.4",
ng2-pagination version: latest
Description of issue: Gives some warning errors when I issue the command
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
Steps to reproduce:
npm install ng2-pagination
Expected result:
clean install
Actual result:
I checked it is there in node_modules\ng2-pagination
in my component I put in my component
import {PaginatePipe, PaginationControlsCmp, PaginationService} from 'ng2-pagination';
localhost/:25 Error: Error: XHR error (404 Not Found) loading http://localhost:3001/ng2-pagination(…)
I also tried putting the js file in my index.html:

then it works!
Any relevant code:

Hi,
The warnings generated by npm when installing are nothing to do with this module. As you can see from the messages, they relate to other packages using fsevents and the last two are there just because the angular2-quickstart package.json file does not include a description or repository field, which npm expects it to. Anyway, they are just warnings and do not indicate anything to worry about really.
The real issue is probably a config thing with the systemjs loader. You need to make sure you configure it to know where the ng2-pagination-bundle.js file resides. Check out the Systemjs docs if that is the case.


allow setting storage backend when creating machine

Might require different provision strategy for different provider.
For example for using overlayfs on boot2docker, it's adding DOCKER_STORAGE=overlay to /var/lib/boot2docker/profile.  for btrfs it's also required to mkfs.btrfs first.

Thanks!  We are targeting this for the 0.3.0 release (https://github.com/docker/machine/issues/902).  We would love to have you help and test :)


📚 DOCS: fix typo

Codecov Report

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

@@             Coverage Diff              @@
##             rtd-theme      #83   +/-   ##
============================================
  Coverage             ?   88.98%
============================================
  Files                ?       11
  Lines                ?      917
  Branches             ?        0
============================================
  Hits                 ?      816
  Misses               ?      101
  Partials             ?        0

Flag
Coverage Δ

pytests
88.98% <0.00%> (?)

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

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 b3379ce...7647c52. Read the comment docs.


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 3bcfe44, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 9731 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in 742387b after 3 minutes.


Renaming k8s terraform folder

Proposed Changes

renaming folder \assets\queries\terraform\kubernetes_pod to \assets\queries\terraform\kubernetes

I submit this contribution under Apache-2.0 license.

@rafaela-soares can you resolve the conflicts? We can then merge this PR

@rafaela-soares can you resolve the conflicts? We can then merge this PR
Done 👍


Split BT-s?

In the CELEX -no matter what version- theBT-s are groupt within each BG and the colums give Info in which notive Type the BG/BT is Optional, Conditionaly Mandatory, Existing Mandatory or Mandatory. So far so good.
None of the BTs or BGs are devided in the CELEX. In the SDK -also different Versions-   however, ther are Rules for different "Parts" of BTs. Eg. BT-09 a and BT-09 b or BT-712 a and BT-712b. Where do theses divisions come from and where can Info on the parted BTs can be retrieved?

In the CELEX -no matter what version- theBT-s are groupt within each BG and the colums give Info in which notive Type the BG/BT is Optional, Conditionaly Mandatory, Existing Mmandatory or Mandatory. So far so good.
None of the BTs or BGs are devided in the CELEX. In the SDK however, ther are Rules for different "Parts" of BTs. eg. BT-09 a and BT-09 b or BT-712 a and BT-712b. Where do theses divisions come from and where can Info on the parted BTs can be retrieved?

Please see this page for explanations on why there sometimes are several fields for one BT:
https://docs.ted.europa.eu/eforms/latest/fields/index.html
As indicated there, for each field we indicate in fields.json the identifier of the BT to which the field corresponds.
As this is rather a question, I'm converting this to a "discussion".


feature request: permit separate x and y inputs for scale, outline, reduce

Currently — am I wrong? — these operations only seem to accept a single distance argument that represents a distance in both x and y. It would be useful to be able to pass separate distances in x and y for these operations.

out of curiosity, do you have a use case in mind? Is it to produce outlines that have different thickness when moving in the horizontal direction versus vertical direction?

Yes. I use non-uniform offsets frequently when designing fonts to make automated weight corrections (for instance, when shrinking the standard numerals so they can be used in fractions). Scaling the glyph will give you the right exterior dimensions. But the interior “color” still has to be adjusted (usually, you need to increase the weight, because scaling down makes the glyph comparatively too light). Hence the offset operation. But because a serif design is thinner in the horizontals, I need to make a smaller adjustment in the y direction than x.
The same logic, however, applies to any operation that moves points in the plane. (Of course, the single d argument would be a special case of a function that takes dx and dy)
Compare Bezier.js, which calls this operation a “graduated offset”. (BTW is this project related to that one? Both sets of curve demos are displayed the same way, which seems like it can’t be coincidence)

BezierKit started as a straight port of Bezier.js to Swift but its goals have changed since then (more oriented towards paths and compatibility with CoreGraphics, doing advanced vector boolean operations such as subtract and union, etc).
as I understand it Bezier.js graduated offsets refer to offsetting in the normal and anti-normal directions, which are relative to the direction of the curve. But you're talking about offsetting relative to the x and y axis, correct? So not quite the same thing?

Sorry, yes — my analogy was imprecise. The graduated offset is indeed a different concept. I just meant it as a demonstration of the visual effect of a non-uniform offset.

I do have an idea for you. I have no idea if this will work, but you could try it out ...
Instead of applying different distances to x and y as arguments to the offset method (I'll call them xDistance and yDistance) you could first scale the path non-uniformly, then apply the offset, then apply the inverse scale. Something like:
let scaleTransform = CGAffineTransform(scaleX: yDistance / xDistance, y: 1)
let scaledPath = path.applying(scaleTransform)
let offsettedPath = path.offset(xDistance)
let finalResult = offsettedPath.applying(scaleTransform.inverted())

So for example in this case if xDistance is 2x that of yDistance the ratio yDistance / xDistance is 1/2. This means we first scale the path so that it's squeezed in the x direction. Then we apply the offset (equal in both direction). Then when we apply the inverse scale, the offset in the x direction should double.

That might work. I’ll try it. The fact that offset introduces new intermediate points on the curves makes me wonder if they’ll get kinked when scaling down (type design happens on an integer-valued grid, not float, so precision sometimes becomes an issue). Is there a way to reduce the incidence of those intermediate points, or are they intrinsic to the math of offset?

The new intermediate points occur because unfortunately because it's only possible to approximate the offset of a bezier curve with another bezier curve. The curvier the curve the more intermediate points must be added to ensure the approximation is reasonably good.


Cherry pick remaining commits from raftstore-proxy-6.1 to raftstore-proxy

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 9 committers have signed the CLA.:white_check_mark: CalvinNeo:white_check_mark: breezewish:white_check_mark: purelind:white_check_mark: mornyx:white_check_mark: tier-cap:x: ti-srebot:x: tabokie:x: Connor1996:x: v01dstarYou have signed the CLA already but the status is still pending? Let us recheck it.


Tests not passing

  ● Test suite failed to run

    TypeScript diagnostics (customize using `[jest-config].globals.ts-jest.diagnostics` option):
    packages/web/src/UserList.tsx:34:8 - error TS2531: Object is possibly 'null'.

    34       {users.edges.map(({node}) => (
              ~~~~~
    packages/web/src/UserList.tsx:34:26 - error TS2339: Property 'node' does not exist on type '{ readonly node: { readonly id: string; readonly name: string | null; readonly email: string | null; }; } | null'.

    34       {users.edges.map(({node}) => (```

2 ways to fix this
disable typecheck on tests
or use this helper
https://github.com/zth/relay-utils#collectconnectionnodes
to make sure we typesafe

Thanks, that did seems to get rid of the error, however I'm facing another issue: Module '"../../../../../../../Users/Mikk/entria-fullstack/node_modules/@types/react-relay"' has no exported member 'Variables'. any ideas?

We can update the relay types or send a or fixing then on DefiniteTyped

I would appreciate it.

Closed on #80


updated mdm mdsd versions

Work item: https://msazure.visualstudio.com/AzureRedHatOpenShift/_workitems/edit/15945924
What this PR does / why we need it:
Updates mdm and mdsd versions.

LGTM


[QUESTION] What's the longhorn backup path pattern?

Hi together,
i have some special backup case. We have external properitary storage engines that provide us a lot of disk space. These storage engines do not provide s3 or nfs support and aren't capable for small files. They are optimized to store single large files.
No problem at all since i created a backup system that works with longhorn.
Currently i'm letting longhorn backup to an internal minio s3. I configured all backup jobs to retain 1 backup of every volume.
Once a time in a week a third party service i created by myself is connecting to this minio s3 and collecting all data in a tar archive and moving this archive to the external properitary storage. This works fine since a year now so that we can use the external storage and disk space.
But there is one thing that might break and that's why i'm writing here. If longhorn is creating a backup of a large volume this might take some more time as previously calculated. In this case it might happen that my third party backup job is starting too early and creating the tar archive and moving it happens while longhorn is creating the backup into the minio s3. That ends in broken backups for the large volumes.
To prevent this i thought about refactoring the backup-system to use the longhorn APIs to obtain all current COMPLETED backups only and creating archives and moving them to the properitary storage. In this case i should have any broken backups anymore. Even if a large backup job takes more time. In this case this backup will be collected in the next backup system job run when it's state will be COMPLETED.
To build this i would like to know wether you could tell me how the backup paths in the s3 storage get build? It might be necessary for me to iterate over the directories and to know what and how i can backup. Maybe the backup state is also written into the s3 filesystem so that i don't need to use the longhorn APIs directly?
I also think about open sourcing this service with k8s-cronjob later on.
Thank you very much and best regards!

The Longhorn backup store file structure:
<backup store work directory>/backupstore/volumes/
    <2 random characters>/<2 random characters>/<backup volume name>/
        volume.cfg
        backups/
            backup1.cfg
            backup2.cfg
            ......
        blocks/
            <2 random characters>/<2 random characters>/
                <backup data, 2MB block, the name is the checksum>.blk
            <2 random characters>/<2 random characters>/
                <backup data, 2MB block, the name is the checksum>.blk
            ......

One example:
[root@longhorn-test-nfs backupstore]# find backupstore/
backupstore/
backupstore/volumes
backupstore/volumes/94
backupstore/volumes/94/6b

backupstore/volumes/94/6b/pvc-2bd97565-bd12-42d9-aceb-ad2a6b976f17

backupstore/volumes/94/6b/pvc-2bd97565-bd12-42d9-aceb-ad2a6b976f17/blocks

backupstore/volumes/94/6b/pvc-2bd97565-bd12-42d9-aceb-ad2a6b976f17/blocks/ff
backupstore/volumes/94/6b/pvc-2bd97565-bd12-42d9-aceb-ad2a6b976f17/blocks/ff/b7
backupstore/volumes/94/6b/pvc-2bd97565-bd12-42d9-aceb-ad2a6b976f17/blocks/ff/b7/ffb7bdef0ee3b58d0db01b4c2f558301255273d3ab6974ae113d2b31b1cebfe9.blk

backupstore/volumes/94/6b/pvc-2bd97565-bd12-42d9-aceb-ad2a6b976f17/volume.cfg

backupstore/volumes/94/6b/pvc-2bd97565-bd12-42d9-aceb-ad2a6b976f17/backups
backupstore/volumes/94/6b/pvc-2bd97565-bd12-42d9-aceb-ad2a6b976f17/backups/backup_backup-022c59007dc24bc7.cfg

To avoid duplication, Longhorn applies incremental backup for each volume. Therefore, the data files in blocks are shared by all backups of this volume. It's trivial/complicated to figure out the blocks for completed backups then collect them.
Checking if the backup is in progress via the files in the backup store is difficult/tricky. Instead, you can verify if there are in-progress backups via kubectl -n longhorn-system get lhb --selector backup-volume=<Backup Volume Name>.


Month selectors not displaying, even without min or max date

I am rendering this element:
 <DatePicker className="due-date-input" onChange={this.handleChange} placeholderText={this.formattedForHumanDate(this.state.startDate)}/>
and in the browser it looks like this:

I cannot figure out why the month selector arrows are not showing up. From the docs, it looks like they should be default.

Any messages in the console?
Any changes on the css definition?
Does the document contain any element like the following if the calendar is popped out?
<a class="react-datepicker__navigation react-datepicker__navigation--previous">

Is the following css definition present on the page?
.react-datepicker__navigation--previous {
    left: 10px;
    border-right-color: #ccc;
}
.react-datepicker__navigation {
    line-height: 1.7rem;
    text-align: center;
    cursor: pointer;
    position: absolute;
    top: 10px;
    width: 0;
    border: 0.45rem solid transparent;
    z-index: 1;
}

@mgrdevport We were missing the z-index! Thank you for your help.


Please invite me to the GitHub Community Organization

Name
Anurag Sharma
Discord Username (if applicable)
Anurag#9801
Additional Context
I met Eddie a log back , but talked to him in last community call at Eddie Hub.

Welcome @Anurag30112003 Glad to have you in our community 🥳🎉


Fix FileOpenError

In fact the error here is not the FileOpenError, it's an UnicodeDecodeError, due to the filename contains Japanese which encoded in byte code. We need to ensure that the filename is encoded in unicode.

Thanks for that Jesse. Haven't touched this in a while.
Ran tests and it looks clean. I might add a test file with a utf-8 filename to help track this in the future.


Remove obsolete website links from example configurations

Overview
This pull request removes several outdated website links from the examples configuration file that were either no longer functioning or redundant due to redirections to the source URLs.
Changes

Removed specific website entries that are obsolete or duplicate the source links provided in the configuration.
Regarding vk audiopad, there was a link in the repository, so I used that and changed it to the website link.

Rationale
The removal of these links simplifies the information presented in the examples, ensuring that users are not misdirected by inactive or redundant URLs.
Request for Maintainers
If you find this pull request unnecessary, or if further modifications are required, please feel free to reject or suggest necessary revisions.
Just to be sure, the test has passed.
[INFO] [en] Creating an optimized production build...

✔ Client
  Compiled successfully in 7.01s

✔ Server

✔ Client
  Compiled successfully in 3.67s

✔ Server

[SUCCESS] Generated static files in "build".
[INFO] [ru] Creating an optimized production build...

✔ Client
  Compiled successfully in 2.93s

✔ Server

[SUCCESS] Generated static files in "build/ru".
[INFO] [uz] Creating an optimized production build...

● Client █████████████████████████ cache (99%) shutdown IdleFileCachePlugin
 serialize pack

● Server █████████████████████████ cache (99%) shutdown IdleFileCachePlugin
 stored

[SUCCESS] Generated static files in "build/uz".

$ eslint --cache "./**/*.{ts,tsx,js,jsx}" && stylelint --cache ./**/*.scss && prettier --check --cache .
Checking formatting...
All matched files use Prettier code style!

Thank you for reviewing this proposal！

Hi! Good catch, these links do need to be removed. Thanks for the contribution :)


Kusto p3 project away

Changelog category (leave one):

New Feature

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Add KQL operator :  project-away

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

will do optimization later in ticket  2347


Add support for poetry 1.4.x

-Updated poetry dependency in the plugin to accept 1.3.x and 1.4.x
-Tested successfully with poetry 1.4.2
I proposed 0.3.1 as version as it does not change any code and works both with 1.3 and 1.4. But imho a version 0.4.0 specific for 1.4. would also be totally fine.
Thanks for your work!

Thanks for this, will review in the next few days.

Hi @mniehoff,
Thank you for the pull request. I am unable to accept it at this time, but support for Poetry 1.4 has been added independently. I intend to share a more detailed contribution procedure once available.


Component with trait containing async fn

Hi!
I have the error
the trait `SQliteConnectionFactory` cannot be made into an object
consider moving `get` to another trait
only type `infrastructure::database::sqlite_connection_factory::SQliteConnectionFactoryImpl` implements the trait, consider using it directly instead

with the following code:
use std::error::Error;

use super::migrator::migrate_database;

use sea_orm::{Database, DatabaseConnection};
use shaku::Component;

use shaku::Interface;

pub trait SQliteConnectionFactory: Interface {
    async fn get(&self) -> Result<DatabaseConnection, Box<dyn Error>>;
}

#[derive(Component)]
#[shaku(interface = SQliteConnectionFactory)]
pub struct SQliteConnectionFactoryImpl {
    #[shaku(default)]
    database_url: String,
}

impl SQliteConnectionFactory for SQliteConnectionFactoryImpl {
    async fn get(&self) -> Result<DatabaseConnection, Box<dyn Error>> {
        let db = Database::connect(self.database_url.as_str()).await?;

        migrate_database(&db);

        Ok(db)
    }
}

impl SQliteConnectionFactoryImpl {
    pub fn new(database_url: String) -> Self {
        Self { database_url }
    }
}

if I remove the async from the trait (and impl) the error disappears.
What is the catch? How to have a Component (singleton) with a async function in trait?
Thanks!

I'll provide the answer here so others with the same issue can find the solution.
The async keyword is not currently supported on traits in the latest stable version of Rust. To work around this, you can use the async-trait crate:
https://github.com/dtolnay/async-trait


Make it possible for rule validators to render warnings

This function solves the problem (这个功能解决的问题)
Sometimes you need a field to call user's attention on its importance or impact without it being required. So it would be nice to create a rule that will trigger a warning if a user inputs certain value, or on user blur, just as you can do with errors.
Expected API (期望的 API)
When I was trying to implement this functionality, my two main ideas were the following:

Make it possible to return a different value on validator function, now you can only return Error or boolean, maybe if you returned a string it could be taken as a warning. For example

birthday: {
  validate(_: FormItemRule, value: string) {
     if (!value) return 'If you don't provide your birthday you won't be abled to claim your birthday present :('
  }
}

I know this option might not be ideal because the validation API seems to be a third-party tool.
2. Maybe if a message exists but field is not required, warning is deployed on trigger. For example:
birthday: {
  required: false,
  message: 'If you don't provide your birthday you won't be abled to claim your birthday present :(',
  trigger: ['blur']
}

Maybe there's other ways to make this solution more robust and self-explanatory, but this are the two options that came to mind when trying to make it work.

This issue does not have any recent activity. If you are still experiencing similar problems, open a new error, including a minimal copy of the problem


make rama-cli squid-config compatible

For some use cases or users a config is good enough. Especially if we allow the custom logic to also be controlled by the same config file this can be a very powerful concept.
For the v0.2 case might already be cool if the following config file could work:
acl SSL_ports port 443

acl Safe_ports port 80		# http
acl Safe_ports port 443		# https

acl CONNECT method CONNECT

http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports

http_port 8080

This would also make the glendc/rama:latest docker image to be useful out of the box for plenty of use cases.
The reference can be found here: https://www.squid-cache.org/Doc/config/
For the one picking this up, it's a nice opportunity to get your hands dirty with something like https://docs.rs/winnow/latest/winnow/ if you haven't used it already.

Moving this to v0.3, because as fun as it is, it does seem like a distraction from what we really need for now. Once v0.2 is out, it's definitely something we can tackle for v0.3.

Those that want to pick up this issue, be warned that it will require a decent time investment. There is a lot to be learned from this issue and pleasure taken from it, but it will require also plenty of work.
The code for the config will live in a new module rama::config, and can be seen as an alternate interface to the rust API. This will be the API that drives the rama binary tool, but next to that it should also be possible for people building proxies with rama to make use of this config module. Meaning that people should be able to expose their own middleware/services to be able to be configured/used with the config.
This story is about getting this API started. In reality this interface is a never ending story, just like the Rust API is a never ending one, but we have to start somewhere and for the config API that start is this story.
The steps that have to be completed for this story to be considered "resolved" (done):

add a chapter about the rama binary tool in https://github.com/plabayo/rama/tree/main/docs/book/src, here you are also to add a fully documented example of a config file that showcases all the possibilities. It is to serve as our roadmap for all that is considered the config so that we can also ensure that the parts we develop for this story are already prepared for the road ahead. Obviously stuff can still change a bit during the next weeks and months as we evolve this, but ideally the rough lines are already clear at this point
write a parser (using winnow) to parse the config into a Rust structure, so that the parsed structured (on success) can be used by others and ourself alike to put together a proxy stack. This step does not yet need to be able to fully parse everything that we document / dream of in step (1). Instead if should only parse the stuff that we'll already support in step (3)
create the initial version of the rama binary tool (which lives in https://github.com/plabayo/rama/tree/main/rama-cli) which reads a config (using step (2)) and creates a proxy stack based on that config to then also run it
add a couple of high level tests for it (E2E tests)

These steps are to be done one by one, in order, one branch/PR per step. They do not have to be done by the same person, but only one person/team should be active on this at the same time. And the one already working on one step gets preference on completing also the step after that, if that is what they want.
At all steps feel free to involve me and report regular. This way you are not alone in this and can we ensure that not too much work is done that shouldn't be done. Important at all times that we stay aligned. I am also here for guidance, mentoring and assistance. Can be via here (GitHub) or on Discord, or both.

What attracted me to the squid config format initially was how it allows you to also declare variables (acl's) and some similar features which makes for a pretty powerful config format.
A more traditional approach would be like toml or yaml. E.g. a much simpler format is something like fly's:
[[services]]
  internal_port = 8080
  protocol = "tcp"

  [services.concurrency]
    hard_limit = 25
    soft_limit = 20

  [[services.ports]]
    handlers = ["http"]
    port = "80"

  [[services.ports]]
    handlers = ["tls", "http"]
    port = "443"

Where you would allow middleware to be configured still in flexible ways, and can map handlers to specific services (e.g. tls could mean the default tls, while we could also allows rustls specifically etc. Http would be the default http proxy etc... Obviously this is a cloud web deployment config example so not 1-to-1 example applicable to proxies but it does show.
This is in a way a lot simpler, as we can just parse toml with serde, and allow within the defined format also dynamic fields that stuff can register into.
E.g. one could register a transport middleware (concurrency) to hook into the concurrency config property, e.g. (a simple example, don't take it as-is, unless you agree and want to take it further):
let mut cfg = rama::config::default();
cfg.register_middleware::<MyConcurrencyConfig>("concurrency", |cfg: MyConcurrencyConfig| {
    ConcurrencyLayer::new(/* ... */)
});

let proxy_services: Vec<_> = cfg.parse().await?.collect();
for proxy_service in proxy_services {
    /* spawn it */
}

There are of course still plenty of questions to answer even for such much simpler approach:

how to differentiate between transport middleware and http middleware
how to allow for upstream middleware (http layer <-> /* middelware */ <-> target)
etc...

And of course, to bring us back to the original topic of squid-inspired config. What does that format give us that would not be possible with a toml-based format. Or put in other words, what are the pros and cons of each approach?


Added guide on Server hosting for docker

This adds a guide to the Linux server hosting part of the wiki, I am marking this as a draft until I feel like this reads well and makes sense to people.

Just noticed #77 and its 100x better than mine, ignore all this.


Access Modifiers

Hi, great framework!
Most of the relevant classes in here don't have an access modifier which means that they are the default internal. To import and use this library, the view classes and their exposed properties need to be declared with public access modifiers to be used outside of the framework.
I have forked this and will work on adding the modifiers.

Thank you very much, appreciated.


Add Exponential Backoff mechanism

The current retry mechanism is too aggressive for SQL Azure.
Too many consecutive retries get "punished" by SQL Azure.
See:

Retry service specific guidance

Transient Fault Handling (Building Real-World Cloud Apps with Azure)

@gkorland I want to make sure I've understood the issue correctly-- is it possible that some users would see wait times for whatever action they're taking in the UI reach minutes?

@seanlindo no of course not but when a pool is retrying to fill the minimum connections it should use this retry gracefully.

I'll try to find some time to look over this. But, I'd definitely accept a PR for this.


Duplicated RESERVED Error Codes?

I noticed in the docs here https://github.com/ReactiveSocket/reactivesocket/blob/master/Protocol.md#error-codes that error codes have RESERVED as 0x0000 AND 0xFFFF. Is this intentional?

Yes, it is. Both all 0s and all 1s are good to reserve. Normally, I use all 1s for extension (such as with frame type EXT). Reserving all 0s is a convenient way to avoid having a blank field mean something meaningful.
This usually pertains to fields that act as decision points for processing.


Scope binaries are getting a bit big

-rwxr-xr-x 1 vagrant vagrant  22M Oct 17 12:36 scope-app
-rwxr-xr-x 1 vagrant vagrant  21M Oct 17 12:36 scope-probe

Making them one binary would probably save most of this, as I bet its mostly shared libraries.

I don't see how this is a problem.

It hit me when testing over the weekend; the total image is something like
70MB, and copying it to test VMs on GCE was taking a while.
On Mon, Oct 19, 2015 at 2:18 PM, Peter Bourgon<EMAIL_ADDRESS>wrote:

I don't see how this is a problem.
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/issues/569#issuecomment-149210792.


[AV2-291] feature/custom-branding-login-screen

hi @shawnm0705 i am not sure what is the standard experience/config API data format, so currently I'm using:

themeColor: for custom color (primary color)
logo: for custom logo

Please do let me know if there are different values i should use instead of those, thanks!


lattice issue when size * repeats is not a multiple of cell_size

Replicate bug on exaDEM with spheres and a radius size of 0.5
Bug:
init:
  - lattice:
      structure: SC
      types: [ 0 ]
      size: [ 1.0 , 1.0 , 1.0 ]
      repeats: [ 5, 5 , 5 ]
domain:
  cell_size: 2.0 m
  periodic: [false,true,false]

It fails with repeats: 5, 7
It works with 4, 6, and 10
It works if cell_size = 2.5
It works if the periodic parameter it set to  [false,false,false]
It seems that the periodic boundary is not adapted to the size * repeats defined into the lattice operator, as the cell size is not adapted by the lattice operator.
Solution: add a warning maybe ?

Lattice operator has recently changed for sake of simplicity and robustness regarding definition of domain properties. Previous lattice operator would typically act as a reader, and defines itself domain properties, but this lead to number of confusion about domain bounds, grid size and automatically generated transformation.
new implementation takes an existing domain and fill it entirely. thus, 1) domain has to be defined before placing lattice operator, and 2) repeats parameter of lattice no longer exists.
Here after is an exemple from exaStamp showing how to properly generate data from a lattice on the first run of a simulation and restart from dumps when some exist. Please note that not only the domain is defined, but the 'init_rcb' operator is placed right after in order to properly setup sub domain definition (necessary even if running sequential)
replicate_domain:
repeat: [ 1 , 1 , 1 ]
input_data:

###################################
Common part needed both
for initial setup and restart
###################################

particle_regions:

BOX:
bounds: [ [ 700 ang , 100 ang , 100 ang ] , [ 900 ang , 900 ang , 900 ang ] ]
SPHERE:
quadric:
shape: sphere
transform:
- scale: [ 160 ang , 160 ang , 160 ang ]
- translate: [ 180 ang , 180 ang , 180 ang ]

has_dump_file:
rebind: { result: has_dump_file }
body: [ file_exists: { filename: lastLegacyDump } ]

################################
Initial system setup

generate_initial_grid:
condition: not has_dump_file
body:
- message: "Initial run, building system ..."

*** Species configuration ***
    - species:
        verbose: false
        species:
          - H: { mass: 1.007 Da , z: 1 , charge: 0.5564 e-  , molecule: H2O }
          - O: { mass: 16 Da    , z: 8 , charge: 0.0 e-     , molecule: H2O }
          - M: { mass: 0.000 Da , z: 0 , charge: -1.1128 e- , molecule: H2O }
          - H2O:
              charge: 0.0 e-
              z: 0
              mass: 0.0 Da
              rigid_molecule:
                - O: [  0.00000000 ang ,  0.00000000 ang ,  0.00000000 ang ]
                - H: [  0.75695033 ang ,  0.58588228 ang ,  0.00000000 ang ]
                - H: [ -0.75695033 ang ,  0.58588228 ang ,  0.00000000 ang ]
                - M: [  0.00000000 ang ,  0.15460000 ang ,  0.00000000 ang ]

*** Domain configuration ***
    - domain:
        cell_size: 25.0 ang
        grid_dims: [ 40 , 40 , 40 ] # grid dimensions multiplied by cell_size must match bounds' size
        bounds: [ [ 0.0 ang , 0.0 ang , 0.0 ang ] , [ 1000.0 ang , 1000.0 ang , 1000.0 ang ] ]
        periodic: [true,true,true]
        expandable: false
        xform: [ [ 1 , 0, 0 ] , [ 0 , 1 , 0 ] , [ 0 , 0 , 1 ] ] # Identity, unless domain sides' lengths are not multiple of cell_size
    - init_rcb_grid

*** Generate lattice with geometrical constraints ***
    - lattice:
        structure: SC
        types: [ H2O ]
        size: [ 3.103 ang , 3.103 ang , 3.103 ang ]
        noise: 0.1 ang
        noise_cutoff: 0.2 ang
        region: SPHERE

user_function:
wavefront:
plane: [ 1 , 0 , 0 , -186.18 ang ]
wave: [ 0 , 0.1 , 0 , 0 ]
amplitude: 30.0 ang
*** Initialize temperature ***
    - random_orient

###################################
Restart from dump file
###################################

read_from_last_dump:
condition: has_dump_file
body:
- message: "Restart from last dump ..."
- read_dump_rigidmol:
filename: lastLegacyDump
replicate_domain # defaults to 1x1x1, may be overriden by --set-replicate_domain-repeat "[2,1,4]"

i'm not sure if the new implementation of lattice has been ported to exaNBody main branch, i'm checking this ... and submit a PR if necessary

I'm gonna try to add your operators (domain, lattice and init_rcb_grid) this morning in exaDEM.
We can still use "repeatsé, so it's probably not integrated.

Indeed; init_rcb_grid does not exist:
ERR: Unable to add operator 'init_rcb_grid' to batch
ERR:   | Could not find a operator factory for 'init_rcb_grid' (and no default declaration exists for this name)

Closing this issue due to merged devs that correct this bad behavior.


winner account name

display winner's account name instead of key

fixed by c6e4b7e5f4 (optimize notes display)


fix: unable to pass dynamic isItemLoaded function

What
Bug
Why
If we don't know how many items will be in list we should be able to pass dynamic isItemLoaded function to be able to check is item loaded or not.
How
We should take latest version of passing isItemLoaded function.
Checklist
Have you done all of these things?

[N/A] Documentation added
[x] Tests
[N/A] TypeScript definitions updated
[N/A] Add a changeset
[x] Ready to be merged

@qister Awesome, thank you mate 😎

@all-contributors please add @qister for code


Add getFreeDiskStorage() and getTotalDiskCapacity(), both iOS only

Added two functions for iOS:
getTotalDiskCapacity() - will return disk capacity in number of bytes
getFreeDiskStorage() - will return free disk storage in number of bytes

@lpetkovic any chance you could implement this for Android as well?

Seems like #43 was implementing Android support, maybe you could borrow @BigPun86 if he's okay with that

Sure, I’ll implement something similar for Android in the next couple of days.

I've added additional commit adding these functions for Android.
Total memory = all memory (root directory)
Free memory = external free memory (not including internal)
Let me know if you are happy with this.

Sure, will do!

Awesome work @lpetkovic, thank you! 🎉 🎉

0.15.0 is out with your changes, enjoy!


Wrong mesh order

https://github.com/pytorch/torchtitan/blob/d442743fed7980392a00eecd464b6db8522d8116/torchtitan/parallelisms/__init__.py#L46
Should be PP DP TP. This matters for NUMA across nodes.

good catch! submitting a fix soon


Fix bug that didn't call DBCreator.Init when --do-load=false

Codecov Report

Merging #141 (9f690a7) into master (56292c5) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #141   +/-   ##
=======================================
  Coverage   65.45%   65.45%
=======================================
  Files         145      145
  Lines        5948     5948
=======================================
  Hits         3893     3893
  Misses       1942     1942
  Partials      113      113

Impacted Files
Coverage Δ

load/loader.go
51.20% <100.00%> (ø)

Continue to review full report at Codecov.

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


refactor(table): change the paddings in the expandable content

fix #1507

Deploy preview for pf-next ready!
Built with commit a8e698fcf2bb8eea0333db721de684c0ea45bc4f
https://deploy-preview-1598--pf-next.netlify.com

Can you verify this is what it's supposed to look like on mobile?

@mcoker checked designs, I think its meant to be 32px padding left/right for the expandable content. As before it was 32px padding-left/right for the main content, then 64px for the expandable content. But after the change to 16px padding-left/right, I assume it will still be double padding. @kybaker can you review this padding on desktop and mobile ?

@mcoker updated spacing here after speaking with @kybaker

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


AWS deployment documentation

Document how to deploy to AWS with standard or custom containers.
Ideally a docs/deploy-aws.md should document the process.
Similar:

docs/deploy-docker.md
docs/deploy-cloudflare.md

@fredliubojin do you have specific views on what stacks would make sense to document? There are a variety of solutions to deploy on AWS, including EKS, LightSail, ECS, barebone EC2, BeanStalk, but probably we don't want to document all of those... I even wonder why one would deploy this on AWS rather than Vercel unless they are already operating on AWS (and I guess they would know which service they want to leverage)


sort propagated dependencies

this is so diff doesn't get polluted by random shuffling of propagated dependencies, e.g. https://github.com/NixOS/nixpkgs/pull/193924/commits/afb11da7dd0f47a17fb21ec9aa68d698fe55c100

ty !


Cannot stub HTTP calls from ActiveJob

Unsure if this is intentionally/unintentionally unsupported, or that I am simply doing something wrong (quite likely), but WebMock seems unable to mock HTTP calls performed in ActiveJob.
Scenario: I wrote some Rails system tests using MiniTest. The test goes through my app workflow which triggers some async (i.e. perform_later) calls to an ActiveJob that retrieve data from an external API. Even when running this system test using the exact stub_request code generated by the WebMock warning, the test continue to generate the ERROR -- Real HTTP connections are disabled. Unregistered request error message.
I assume that is because stubs made in WebMock do not affect calls made in a background worker, but wanted to confirm.
And yes I am aware that I can disable background jobs in Rails tests using include ActiveJob::TestHelper.
Thank you!

Stubs configured with WebMock are confined to the Ruby process in which they are set up. This means that when background workers operate as separate Ruby processes, the stubs won't have any effect on them.
It's important to note that this behavior extends beyond WebMock. Any stubbed Ruby method in one process won't influence the behavior of the same method in other Ruby processes.

Thank you for the explanation.


feat: expose bucket_endpoint variable

Description
Optional variable cos_bucket_endpoint was added to expose scc_instance_settings bucket endpoint.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

@ocofaigh I got this error when trying to run the complete example with changes - Can't configure a value for "object_storage.0.bucket_endpoint": its value will be decided automatically based on the result of applying this configuration.

@kierramarie Interesting - can you try a test with hard coding the value of an existing bucket and endpoint (that you didnt create using the same terraform apply as the module). Then at least we will know if the feature works at all with the provider

@ocofaigh okay, yeah. I used a bucket I created in the GUI and I still got the same error. And this is the name of the error; Error: Value for unconfigurable attribute

@kierramarie please create a provider issue

@kierramarie Actually, seems I already created a provider issue - the problem is the docs -> https://github.com/IBM-Cloud/terraform-provider-ibm/issues/5110


Vsix installation failed with error: The extenstion manifest is invalid

Version: NET Portability Analyzer v<IP_ADDRESS>.vsix

Extenstion was downloaded from Microsoft Marketplace https://marketplace.visualstudio.com/items?itemNa
me=ConnieYau.NETPortabilityAnalyzer

I just downloaded and installed the extension from the marketplace and did not get the same error.  What versions of Visual Studio do you have installed on your machine?
Cheers,
Connie

Two version:
VS2015 Professional 14.0.25431.01 Update 3
VS2017 Community 15.0.0+26228,9
Regards Grzegorz

I created a machine with both versions of Visual Studio but was unable to reproduce the issue and it installed correctly.  I found something similar on StackOverflow.  Can you try this solution? https://stackoverflow.com/a/33501473/4220757
Cheers,
Connie

Problem was with wrong default app for vsix files - I have "Visual studio selector". After changing to Microsoft VSIX Installer everything works. Thank you.


IncrementalSearchCV if not getting imported would show error

Regarding Issue #464

I believe @stsievert is already handling this in https://github.com/dask/dask-ml/pull/466

oh, sorry didn't saw that, I'll close this PR then!


Problem with "Problem" tab - input field and filter

VSCode Version: 1.45.1
OS Version:

Steps to Reproduce:

Change tabs with Output, Problem, Terminal
The input field change size, and change tabs to dots "..." what made disonanse on GUi

Yes, I agree that Problems filter input box seems larger than typically necessary, resulting in the loss of panel headers.

/duplicate


Remove the dns name component of this test.

Fixes https://github.com/pulumi/pulumi-azure-serverless/issues/19
The test doesn't really need this property set.  And setting it causes tests to have issues in parallel since two simultaneous runs of this test will both try to take the same dns-name-label which Azure doesn't allow.

LGTM


Changed AppDetailsPage IsXXX to a collection of readonly checkboxes

As part of this, created a new FrameworkTypes model, and AppRuntimeInfo now has an ObservableCollection of these. This should make it easier to add new framework types later (I added Python). In the UI, each item is represented by a readonly CheckBox in a WrapPanel, so that they flow when the window is sized. Standard CheckBox doesn't support readonly, so I added a custom ReadOnlyCheckBox control.
Also simplified the visibility of the problem fields in the AppDetailsPage - these are all now within a grid, so we only have to set visibility on the grid instead of on each field (should also improve perf very slightly).
Sorted the module list by name. Added a GridSplitter to the Modules page, so that the user can size the width of the list.
Also, when the user closes the Bar window, we save the expanded size to user settings (if not maximized).
Deleted some redundant fields and strings.

support readonly
Checkboxes have IsEnabled.    That does make the control read-only.  Did you need other behavior besides this?

Can you please put a video of the changes in the PR?


merge package from arlac77/npm-package-template

.travis.yml

chore(travis): remove node versions 10
chore(travis): add node versions 10.1

:tada: This PR is included in version 6.0.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[QUESTION] Use a relation field in a where clause

Is it possible to use a relation field in a where clause?

It seems that there is no access to the nested relation:

This is the example from the docs:

Dose drizzle only provide one nested layer?

Not implemented currently

@dankochetov alright, thanks for all your hard work and fast replies 😍
I'll do it in the server for now.
Btw, is this planned?

I also like to see this feature implemented!

yeah, this would be such a good add! +1 :)

+1. This is a must have for me too.

+1 This would be great

An issue for this feature already exists: #696

25 Dec 2024, 1+

is it completed?
how to solve it?


Added Block Logo

Description
Added block Logo
Fixes #
Insert the image of the art below
Checklist:
To fill the checklists, put x inside the brackets. [x]

[x] My code follows the guidelines of this project
[x] I have tested my code and it works properly
[x] I have added just one folder that includes my Art files (jsx and css)
[x] I have not edited App.js file
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] This is my original code and I have NOT copied the code from anywhere else.

Hi @ayushgupta0110, I would suggest you add some more elements or come up with some other art.

Okay!


Structures shift to center of canvas when enabling viewOnlyMode through the API

Description: When using the API call window.ketcher.editor.setOptions(JSON.stringify({ viewOnlyMode: true })), structures already present on canvas are unexpectedly moved to the center, as if a layout function is being applied. This behavior is unintended and disrupts the original positioning of structures.
Steps to Reproduce:

Add any structures onto the canvas.
Use the following API call: window.ketcher.editor.setOptions(JSON.stringify({ viewOnlyMode: true })).
Observe the position of the structures on the canvas.

Actual Result: The structures shift to center of the canvas, behaving as though a layout is being applied.
Expected Result: The structures should remain in their original position without any movement or layout changes.
Screenshots
https://github.com/user-attachments/assets/73bc2eb1-0619-4e34-bbf0-7542645001fd
Desktop:

OS: Windows 11
Browser Chrome
Version 128.0.6613.120 (Official Build) (64-bit)

Ketcher version
[Version 2.25.0-rc.1]
Indigo version
[Version 1.24.0-rc.1]
Bug found during testing: https://github.com/epam/ketcher/issues/4965

The issue isn't related to new changes in https://github.com/epam/ketcher/issues/4965


Assets are not included for the server (adapter-node)

Describe the bug
Bug
If you import an image on the server (e.g. in an endpoint), the file path will point to a non-existent file.
import Image from '$lib/svelte-welcome.webp';

console.log(Image); // /_app/immutable/assets/svelte-welcome-c18bcf5a.webp

When looking in /build/client/_app/immutable/assets folder, the file is not included.
Use case

I am using node-canvas on the server and in this case, I need to place an image on the canvas, so I need the image path
This is not an asset that I want to share publically, which is why I don't want to have it in the static folder

Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-eromzr?file=src/routes/todos/_api.js

Run npm run build
Run node build
Click on the "Todos" link
See image path in the console

Logs
No response
System Info
This command doesn't seem to work on StackBlitz 😄

Severity
serious, but I can work around it
Additional Information
I guess I can work around it by having all assets in the static folder, which is included in the build correctly.
But then all the assets are public. So then I guess I can have some sort of logic in hooks.ts that would prevent access to those files.

This is a serious issue ! Because assets are now considered as route by the layout... so it throws a 404 and event could erase $page.stuff if you use it for metadata in your __error.svelte

https://github.com/sveltejs/kit/pull/4974

possible related: #1567

I just got this issue using<EMAIL_ADDRESS>and my auto deploys (using adapter-auto) on vercel started throwing 404 for missing static files.

Everything is now working after doing npm update.
I got the following message with directions to change config

svelte-kit build is no longer available — use vite build instead

All good 😊

Opened https://github.com/vitejs/vite/issues/11429

Does a workaround exist?

Yes, import the assets somewhere in your client code. As long as you don't use them in client code, the paths will be treeshaken away so they won't impact your client-side bundle size.

I just tried vite 4.1.0-beta.1 which should have the fix from https://github.com/vitejs/vite/issues/11429 and my similar error still occurs, are others still seeing the same thing?

@thechubbypanda I'm also still facing the error with vite 4.1.0-beta.1, but I don't think it includes the fix, since it's not on the changelog document yet.

I had a similar issue with production. I used as background-image: url('images/hexagon.svg') in the <style></style>, but was not getting the image in the production. It was searching in _app/immutable.
But when i put the url as variable in the script, and did an inline styling lin style="background-image: url({src})" it worked just fine!
This example helped me.


Automated Latest Dependency Updates

This is an auto-generated PR with latest dependency updates. Please do not delete the latest-dep-update branch because it's needed by the auto-dependency bot.

Uh oh I see red tests...

Looks like they changed how the topological sort computes the order:
https://github.com/networkx/networkx/blame/main/networkx/algorithms/dag.py#L246
https://github.com/networkx/networkx/pull/4757
See 4757 in the release notes: https://networkx.org/documentation/stable/release/release_2.6.html#api-changes

Pinned networkx so I'll merge now!


refreshToken and refreshTokenLifetime is undefined when generating accessToken

Hi @Manokii thank you for the issue. Please add some more information:
Which version do you use?
Which workflow is affected?

I just read the docs, https://www.rfc-editor.org/rfc/rfc6749#section-4.4.3
I thought client_credentials grant are given refresh token, please disregard this issue