Current shinyDiagnostics doesnt work with issues regarding background

After using phenotypeR::phenotypeDiagnostics and feeding the results into phenotypeR::shinyDiagnostics, it threw an error:
Error in `omopViewer::exportStaticApp()`:
✖ `background` is not logical.
! `background` must be a logical; with length = 1; it can not contain NA; it can not be
  NULL.

Tagging @catalamarti as we briefly discussed this already

@xihang-chen can you try with the current github version? https://github.com/OHDSI/phenotypeR/blob/540078e916c4f5dc3ecb24c1b98428917ac1b172/R/shinyDiagnostics.R#L19 background is currently commented out there

@xihang-chen can you try again, this should now also be fixed

@edward-burn this has been resolved now! Thanks! closing this issue now


Incorrect handling of blank lines with NT-5890K

I have a thermal printer, which looks exactly as Zjang ZJ-5890K and is probably same same inside.
The line in source https://github.com/klirichek/zj-58/blob/master/rastertozj.c#L119 seems to assume that ESC J n skips 0.176n mm, however, on my printer it skips 0.125n mm, according to documentation and my own measurements.
Also, 0.176 equals 1/144 inches, not 1/44 inches, so the line had a mistype too.
However, for some reason, the printed files had too wide blank intervals, while they were supposed to be too narrow ...

Hey, sorry to revive this issue after so long. Hopefully if this is unhelpful to you it could at least solve this for others in the future.
I was able to add a hacky work-around to print blank lines as an image as normal, that still allows the printer to stop printing if there is nothing left to print (rather than stop printing at the end of the selected page size - which is what it does if you simply override line_is_empty)
I'm not great at writing C, and this is actually a guaranteed possible buffer overflow issue if you print a long, completely-blank image, and may break lots of things. So don't do that.
Anyways, I'm too lazy to throw together a PR, especially since it looks like no one is reviewing them anyways, so here's the snippet of code I modified, you can find where it is using the comments at the top
      // lazy output of current raster. First check current line if it is zero.
      // if there were many zeroes and met non-zero - flush zeros by 'feed' cmd
      // if opposite - send non-zero chunk as raster.
      unsigned char *pBuf = pRasterBuf;
      unsigned char *pChunk = pBuf;
      const unsigned char *pEnd = pBuf + iBytesChunk;
      unsigned char zeroArr[65534];
      memset(zeroArr, 0, 65534);
      const unsigned char *pZeroArr;
      pZeroArr = &zeroArr[0];
      int nonzerolines = 0;
      while ( pBuf<pEnd ) {
        if (line_is_empty(pBuf, width_bytes)) {
          if (nonzerolines) { // met zero, need to flush collected raster
            send_raster(pChunk, width_bytes, nonzerolines);
            nonzerolines = 0;
          }
          ++zeroy;
        } else {
          if (zeroy) { // met non-zero, need to feed calculated num of zero lines
            send_raster(pZeroArr, width_bytes, zeroy);
            zeroy=0;
          }
          if (!nonzerolines)
            pChunk = pBuf;
          ++nonzerolines;
        }
        pBuf += width_bytes;
      }
      send_raster(pChunk, width_bytes, nonzerolines);
      //flushBuffer();
    } // loop over page


GC Pause time for maps.

I understand that benchmarks will depend on the machine used.
Following is from a 2017 Macbook pro (2.8 GHz Intel Core i7, 16 GB 2133 MHz LPDDR3)
However native Maps seems to have had a massive improvement. Is this due to go 1.9?
go version go1.9.2 darwin/amd64
go run caches_gc_overhead_comparison.go
Number of entries:  20000000
GC pause for bigcache:  45.222µs
GC pause for freecache:  37.043µs
GC pause for map:  59.572µs

@irfn Looks interesting. We might need to do more benchmarks (best if we find what change fixes GC map issues in go). Maybe bigcache is no longer needed and we can rely on map from stdlib. That would be great!

Looks like bench inaccuracy due to different load in CPU(background processes etc).
Numbers are quite small(it's microseconds!) so any small fluctuations might cause quite different results.
I don't think bigcache isn't needed anymore, we might have bigger GC pauses, but during concurrent read/write shards will save us and lower our latency.
Here are my results.
Go:
go version
go version go1.9.2 darwin/amd64

Bench:
go run caches_gc_overhead_comparison.go
Number of entries:  20000000
GC pause for bigcache:  36.712µs
GC pause for freecache:  59.594µs
GC pause for map:  62.094µs

Machine:
MacBook Pro (15-inch, 2017)
2,9 GHz Intel Core i7
16 GB 2133 MHz LPDDR3

@cristaloleg I have similar results on same machine.
I am suggesting an improvement to the benchmark to get better visibility for go 1.9
There are some changes in go GC mentioned here wrt GC pauses. https://golang.org/doc/go1.9#gc
Mentioned: "The runtime.ReadMemStats function now takes less than 100µs even for very large heaps"
Few other things that point to fact that GC comparison would need to be checked again. @cristaloleg Like you mentioned the perf bottleneck may appear at higher amount of data / ops etc.

Yeah, GC isn't a problem anymore 😄

Maybe bigcache is no longer needed and we can rely on map from stdlib. That would be great!

Even if maps do end up with massive improvements, I hope bigcache stays around! It's still better than the alternatives, in my mind, haha.

Built-in map still looks like a problem for GC performance. Please take a look at the following posts:
https://www.komu.engineer/blogs/go-gc-maps
https://syslog.ravelin.com/gc-is-bad-and-you-should-feel-bad-e9bdd9324f0
https://www.reddit.com/r/golang/comments/7sws11/benchmarking_gc_pause_times_with_string_and_int/
I have tried the case which described in the first post on my computer with Go 1.10 and the result is the same. What do you think?

Bigcache is an exceedingly optimised version of the built-in map type that works around the garbage collection subsystem by using a (FNV-1a Hash Algorithm)[https://en.wikipedia.org/wiki/Fowler–Noll–Vo_hash_function] which converts our interface types into raw uint64s so we can store them in a standard map without pointers. By doing that, we are completely avoiding the GC. This is a great opportunity for a case study on this optimisation.

I tried to state that go1.10 has the same problem:
$ for t in 1 2; do go run gc.go $t; done
With a map of strings, GC took: 2.442295076s
With map of strings(that are hashed to ints), GC took:: 23.268634ms

$ go version
go version go1.10 darwin/amd64

@buraksezer gotcha! Sorry, missed some of the context. I reran the stats comparison with go1.10 windows/amd64 for #69 and fixed a GC bug if you want to see the updated comparisons.


Keploy Vscode Extension : Go

This pull request is the improved and beta version of the Vscode Extension for Keploy.
The extension only supports Go for now, including compiled Go binaries and go commands

@Akash-Singh04 We should atleast add some build check which perform npm install / build etc .


Update KeepAlive Publish Path Following Transition from Mosquitto to FlashMQ

According to the documentation in https://github.com/victronenergy/dbus-flashmq?tab=readme-ov-file#keep-alive, the Loader should publish keepAliveOption in a new location in the latest version of Venus OS.
Loader.prototype.sendKeepAlive = function (client, portalId, isFirstKeepAliveRequest) {
  this.logger.debug(`sending keep alive for ${portalId}, isFirstKeepAliveRequest: ${isFirstKeepAliveRequest}`)
  client.publish(`R/${portalId}/keepalive`, isFirstKeepAliveRequest ? '' : '{ "keepalive-options" : ["suppress-republish"] }')
}

To ensure compatibility with older versions of Venus OS, the Loader could either be parameterized, or if possible, the Venus version could be retrieved directly from the MQTT broker. This would ensure that the keepAliveOption is published correctly according to the specific OS version.

With a 'keepalive-options': ['suppress-republish'] (Venus OS 3.32 - FlashMQ), after a couple of hours, the loader does not receive some values anymore, e.g., Battery/0/Info/MaxChargeVoltage. Without this option, everything worked fine for me. I am not deep enough into the subject matter; could you please take a look at it?
Loader.prototype.sendKeepAlive = function (client, portalId, isFirstKeepAliveRequest) {
  this.logger.debug(`sending keep alive for ${portalId}`);
  client.publish(`R/${portalId}/keepalive`, '');
}

I am not deep enough into the subject matter; could you please take a look at it?

@ogurevich Thanks for helping me test this. Using the old DBus path should be OK, it still works, and suppress republish should only send changed values. Before the logic was broken in that it requested refresh of everything every 62 seconds. We are trying to get to the stage where only changed values are stored into the InfluxDB in that we really record what really happened without any duplicates. So the question is whether the Battery/0/Info/MaxChargeVoltage should change for you.

I've been using the Victron-Influx loader with a configuration set to suppress republishing ('keepalive-options': ['suppress-republish']). My understanding was that the loader should log the state of the system in a way that allows for snapshot-like analysis later on. However, with the suppress-republish option, I've observed that the loader stops receiving some values after a few hours, such as SELECT mean("value") FROM "battery/Info/MaxChargeVoltage" WHERE ("instanceNumber"::tag = '2') AND $timeFilter GROUP BY time($__interval) fill(null) This is not ideal as it seems to log points relatively infrequently, as shown in the graph to the left of the vertical line, potentially missing critical changes in the data.
The intended behavior, as I understand it, was to ensure the loader records system states accurately for later analysis, capturing what really happened without duplicates. However, the current setup with suppress-republish may not support this, as it results in less frequent data points, limiting the effectiveness of any subsequent analysis based on these snapshots.
Could you advise on how we might adjust the loader or its configuration to better capture continuous state changes without missing significant data points?

The point is to never loose any data. What gets published by the Venus on DBus gets later recorded via MQTT and stored to Influx. So we must not, and we should not be loosing any data.
Another point is how is Influx helping us or not to properly visualise the data. In other words, what would mean actually report for infrequently changing values...

Yeah, I understand what you are saying. Let's give it some thought to figure out what is the correct answer in that case.
One of the goals of this project is to get super high granularity data for investigation, and by suppressing re-sends of old values we also store only valid data that were published by the system. So missing data also has a meaning...
Goal of Grafana is to not duplicate VRM functionality, but rather enhance it.
Let's think about what should success look like in this case...

thank you for clarification and infos, should we close the issue ? And let some time for this thought :)

thank you for clarification and infos, should we close the issue ? And let some time for this thought :)

No please keep it open, you are raising a valid point and we should figure out what is the proper functionality...

Reflecting on our ongoing discussion about the efficiency of data handling in the Venus-Influx loader, I had a spontaneous idea that might be worth considering. What if we explore the possibility of developing a specialized agent—akin to a D-Bus metrics agent—that handles data directly from the source, bypassing MQTT entirely? This approach could ensure we only process and store significant changes directly from Venus OS, enhancing both efficiency and accuracy.
Such an agent could optimize how we handle data—minimizing unnecessary loads and enhancing data visualization directly from the D-Bus. This could lead to more accurate and meaningful insights, especially when capturing real-time changes without the overhead of MQTT.
This is just a thought experiment at this stage, but I believe it could lead to a robust discussion on possibly enhancing our current setup. What do you all think? Could this be a viable direction to explore further?
This version further tailors the idea to your concept of leveraging a D-Bus-centric solution, which could streamline data handling and reduce dependencies.


Work without jQuery

different from #41 approach.
maybe, using a lot of if block is not cool at all...

Closing since this has been stale. Feel free to comment or re-submit an updated PR.


[SPARK-17748][ML] Minor cleanups to one-pass linear regression with elastic net

What changes were proposed in this pull request?

Made SingularMatrixException private ml
WeightedLeastSquares: Changed to allow tol >= 0 instead of only tol > 0

How was this patch tested?
existing tests

Test build #68174 has started for PR 15779 at commit 2bee341.

@sethah @yanboliang I just saw your PRs for SPARK-17748.  Awesome change.  I just saw a few nits along the way.
The only major item is making SingularMatrixException private ml.  This would be the first public Exception type we have in MLlib, I believe.  If it is to be public, I'd prefer it live in spark.ml.linalg, so we could move it there instead of making it private.
Also, I'm not a big fan of using Exceptions to handle logic.  I'd prefer to change the use of CholeskySolver to pass the failure code, rather than relying on exceptions.  If that sounds good to you, then I'll make a follow up JIRA for it.
Thanks!

Test build #68174 has finished for PR 15779 at commit 2bee341.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68174/
Test FAILed.

+1 on removing the use of exceptions. I thought it was a bit of an awkward solution to begin with. Thanks a lot for this pr, I will take a look soon.

@jkbradley @sethah The idea of using failure code rather than exception sounds good to me. I thought users could get the exception and infer the cause of failure from it. After rethinking it, I think it's an expert exception that few users would like to intercept it, so using failure code should make more sense. Thanks for the follow-up work.

I agree that exceptions can become, quite surprisingly, part of a public API. It has to be done with care. I am not sure I agree that failure codes are better; they're exceptions that don't use a language API and are even more ignorable. If it's simply status, that makes sense; if it's indicating failure, you want it to be hard-er to ignore.

Test build #68312 has started for PR 15779 at commit 72a9302.

I should have clarified: I meant for us to use the failure code internally.  If the linear algebra ops become more public, then we may need to consider better ways to return result codes.  I'll make a JIRA for it.

Test build #68312 has finished for PR 15779 at commit 72a9302.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68312/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68353 has started for PR 15779 at commit 42ff98e.

LGTM

Test build #68353 has finished for PR 15779 at commit 42ff98e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68353/
Test PASSed.

Merged build finished. Test PASSed.

Thanks!  I'll merge this with master and branch-2.1

Linking commit for branch-2.1 since it hasn't linked automatically: [https://github.com/apache/spark/commit/21bbf94b41fbd193e370a3820131e449aaf0e3db]


Hidhide Hides Joy2Key Keyboard Input

[ x] I have searched open and closed issues for duplicates
[ x] I am submitting a bug report for existing functionality that does not work as intended
[x ] I have read the project documentation and not found a solution to my problem there
[x ] This isn't a feature request or a discussion topic

Bug description
Hidhide hides virtual key presses from joy2key
Steps to reproduce

Install Joy2Key
Install Hidhide
Hide controller input
Whitelist Joy2key & verify it receives controller input
Attempt to use Joy2Key output in another app

Actual result: Joy2key key presses are hidden by hidhide. If device hiding is disabled in hidhide joy2key key presses work as expected.
Expected result: I think hidhide shouldn't hide virtual keyboard events - only gamepad events
Screenshots

Machine info

CPU-Architecture: x64
Windows version: Windows 11 23H2
Software/driver version(s): 1.5.230
Any other helpful information

Without a proper investigation and bug report this can simply not be addressed, closing.


Updated blog link

I updated mint.json https://keyval.dev/blog/  to https://odigos.io/blog. Because when visiting the https://keyval.dev/blog/ come up with odigos.io home page.
Screenshort

@blumamir Kindly have a review. Thanks


Fix nested Any() not correctly tracking longestError. Fixes #3

We ran into this issue with nested Any() as well, digging into the debug traces, you can see that the inner any failed the individual parsers but didn't return any error back up the chain.
=== RUN   TestAny/Nested/Any(Seq,Any)
combinator_test.go:97 | bob             | ps {
combinator_test.go:94 | bob             |   seq {
combinator_test.go:94 |                 |     [a-z] found "bob"
combinator_test.go:94 |                 |     : did not find :
combinator_test.go:94 | bob             |   } did not find :
combinator_test.go:93 | bob             |   anyTrueFalse {
combinator_test.go:93 | bob             |     true did not find true
combinator_test.go:93 | bob             |     false did not find false
combinator_test.go:93 | bob             |   } found "[bob,]"
combinator_test.go:97 | bob             | } found "[bob,]"

What happens is in the outer Any() it runs a parser which sets an error, it then calls recover and calls the next parser. If that parser is an Any() then it saves error in longestError, but because recover was called, pos is set, but expected is empty. Subsequently the inner Any() will check the error pos against longest, but if all the inner Any()'s errors are before the outer one, it ends up returning out of the inner any() without having updated longestError. When it then returns back up the chain, error.expected is still not set.
This fix checks expected as well as pos when checking if it should update longestError.

Ahh, I didn't see PR #6 before, that's a better fix than this one.


Error in wasmprinter

Hi,
On parsing a component using wasmparser, encoding using wasm_encoder and trying to print it with wasmprinter, I get the following error:

I've stepped through a debugger and it seems like the wasm_encoder is able to encode it fine with the number of various sections such as canons, imports, exports, instances, being the same as in the actual component. Hence, I believe it's an error with the wasmprinter

Could you share the binary itself here too?

The binaries are at: https://github.com/thesuhas/orca/tree/main/tests/spin
I'm unable to paste .wat file here as it's too large. Hope a link to it on my repo is okay

Could you share the intermediate binary after passing through wasm-encoder which is considered invalid?

Hm ok so poking around it's definitely an invalid component, both from a validation perspective and a syntactic binary structure perspective. If you're exclusively using wasm-encoder then that may mean that the wrong wasm-encoder constructs are being used and/or being used in the wrong order or something like that.
Do you have a link to the code used to reencode the component?

Should be this: https://github.com/thesuhas/orca/blob/009ecd7bc5438d7dd000568ed199b995411a394b/src/ir/component.rs#L176
I have a bunch of test cases and it passes all of them except this, which leads me to believe it's probably an issue with a feature of components that wasn't tested in those. Another thing I noticed is earlier I was doing something like:
Payload::ComponentTypeSection(component_type_reader) => {
                    component_types = component_type_reader
                        .into_iter()
                        .collect::<Result<_, _>>()?;
                }

during parsing which meant only the last component type was being stored. Now I'm doing:
Payload::ComponentTypeSection(component_type_reader) => {
                    component_types.append(
                        &mut component_type_reader
                            .into_iter()
                            .collect::<Result<_, _>>()?,
                    );
                }

which means that there was something specific that I was not storing to encode before. Previously, I would not store any ComponentDefinedType due to this but now I do, which is what seems to be throwing the error.

Ok thanks for the link. Unfortunately though I can't at least easily figure out what's going on here. I think it's worth considering production of a syntactically invalid binary a bug in wasm-encoder, but without digging in more it's tough to say where the bug is.
FWIW while I can't be certain I would suspect that the bug here lies in a combination of your usage of wasm-encoder and wasm-encoder itself. I don't think that there's a bug with wasmparser, validation, or wasmprinter here.

I would suspect that the bug here lies in a combination of your usage of wasm-encoder and wasm-encoder itself

Do you mean instances of where wasm-encoder has nested encodes?

I mostly mean that if you use the API of wasm-encoder it should theoretically be impossible to produce a syntactically invalid module (you can produce a semantically invalid module though of course). Somehow though that's happening as you're exclusively using wasm-encoder yet an invalid module is being produced. I don't know why that's happening nor what might be causing that without digging in further.

Do you have any advice on how to isolate the issue? I've been trying to generate smaller components to test my solution but it is very non-trivial. For modules, we have the spec tests but for components there is nothing of the sort from what I can tell. The Component Model repository does mention there is a test suite coming but nothing right now.
The binary I provided was a base http-rust template from spin which is too big to use as a source of debugging.

We are looking into https://github.com/bytecodealliance/wasm-tools/tree/main/tests/local/component-model fow now

Ah looks like you've already found wasm-tools's own test suite and wasmtime has other files as well. If that doesn't help I'd recommend to start cutting out various bits and pieces manually in your host code that's doing the transcoding. It will quickly start producing a binary that doesn't pass validation but everything generated by wasm-encoder should be able to be run through wasmprinter to at least print without error.

It seems like there might be a bug in wasm-encoder and encoding component type sections? "data at end of section" basically just means a corrupt binary, so I think what needs to be debugged is the output of wasm-encoder rather than wasmprinter/wasmparser.

Found the issue! Was an extra byte being added by my code to Function Results. Thanks a lot for the help!

Was this a case of an extra byte being manually appended? Or was this a bug in wasm-encoder?

It was incorrect handling of the Function Results in the ComponentFuncTypeEncoder. In case of unnamed results, I would call .result but I would also call .results on an empty vector


[Do not merge] Delete frontend parts of document collections

Document collections are rendered by government-frontend
The template and controller aren’t used
The route is still used to generate the base_path
Whitehall is still responsible for the /series redirect

Ready to review. [Do not merge] flag is for more thorough testing with a branch deploy to Integration.

Deployed to integration and tested previewing/creating/editing document collections.


routeTree.gen not generated when setting up project

Which project does this relate to?
Router
Describe the bug
I have set up a new project using Vite/React/Typescript/yarn.
After that I follow the installation and quickstart docs on tanstack.com
I installed router
yarn add @tanstack/react-router
Installed Vite plugin and router devtools
yarn add -D @tanstack/router-plugin @tanstack/router-devtools
Configured vite plugin by adding TanStackRouterVite() to the plugins array in vite.config.ts
I add the files
src/routes/__root.tsx
 src/routes/index.lazy.tsx
 src/routes/about.lazy.tsx
 src/main.tsx

The following step is to update the main.tsx and here is instructions:
Regardless if you are using the @tanstack/router-plugin package or manually running the tsr watch/tsr generate commands from your package scripts, the following file will be generated for you at src/routeTree.gen.ts.
Hovewer, there is no routeTree.gen.ts generated for me. Am I missing some step?
Your Example Website or App
notavailable
Steps to Reproduce the Bug or Issue

Create a new project with Vite/React/Typescript using yarn.
Install tanstack/react-router yarn add @tanstack/react-router
Installed Vite plugin and router devtools yarn add -D @tanstack/router-plugin @tanstack/router-devtools
No src/routeTree.gen.ts is generated when I perform these steps

Expected behavior
As a developer, I expect routeTree.gen.ts to be generated when I perform the steps above, according to the documentation.
Screenshots or Videos
No response
Platform

OS: [macOS]

Additional context
No response

Como você resolveu? Estou com este problema, reinstalei os pacotes da package.lock.json e da node_modules e nada ainda.

@ViniciusPilati2005
unless we add createRootRoute it won't be generated, i got it from the warnings, now i feel it's true as there won't be tree without the seed or root !

my __root.tsx folder looks like this
export const Route = createRootRoute({
  component: () => (
    <>

        <Link to="/" className="[&.active]:font-bold">
          Home
        </Link>
        <Link to="/" className="[&.active]:font-bold">
          About
        </Link>
        <Link to="/password-changes" className="[&.active]:font-bold">
          password changes
        </Link>

      <Toaster />

      <Outlet />
      <TanStackRouterDevtools />
    </>
  ),
})

even adding the root file with the necessary dependencies, it does not generate

@ViniciusPilati2005 please create a minimal complete example and open a new issue


cannot connet to https://archive.org/download/pt711/PacketTracer7.1.1ForLinux64Bit.tar

Hai, i`m new in docker and i want to try this project but i get this error even though i already create Internet Archive account.

Will help me with this error please.
Thank you.

Hi, thanks for the report. it seems the archive doesn't exist anymore. packet-tracer is now available in version 7.3 as deb package for ubuntu 18.04. I'll have a closer look at it over the weekend and fix it.


permit install into windows program files

when installing terasology into program files, that dir is not writeable. starting up, terasology tries to create a folder in .local, which then fails.
therefor, permit two things with this change. first, permit calling the windows bat script from a different directory. it then needs to find the library relative to the start script location, not to the location where the script is called from.
second, before starting java, change to home directory. ideally, terasology itself should find a proper path by default. but program files as run directory is in any case wrong, so change.
this is the same change which was used to upload to chocolatey.

for the "cd" in the script - normally this should not be needed, as an app may folllow the xdg spec, and even use some library to make this easier, like https://github.com/dirs-dev/directories-jvm .


Allow usage of parent event types in wait_until_* tools

What was wrong?
The wait_until_* family of APIs do not allow matching against a parent event type. However, allowing that can be more convenient e.g.
bus.wait_until_any_connections_subscribed_to(BaseEvent)

How was it fixed?
Using issubclass for the type checking.
Cute Animal Picture

@pipermerriam I know you wanted to change this API as a whole, but I thought this change was small enough to put it off again. It makes the tests in Trinity more ergonomic.

This change would make it impossible to know for sure that someone was actually subscribed to your event since it would return True if they were subscribed to anything in the inheritance chain but not actually tell you if the specific event you are querying actually has a subscriber.

Mmh...ok, this is true for events that have further subsclasses. But you would still be able to exclusively match agianst a specific event that is at the very bottom of the inheritance chain.
Ok, so let's look at the actual use case: Let's imagine you have a class that streams 3 different event types. Usually streaming of these 5 events is setup in the same tick so when you write your tests you only care about that there is any subscriber at all.
You could write your tests like this:

def test_foo(bus):

await bus.wait_until_all_connections_subscribed_to(EventOne)

But picking EventOne feels like an arbitrary choice. Why not EventTwo? .
Or you could write

def test_foo(bus):

await bus.wait_until_all_connections_subscribed_to(EventOne, EventTwo, EventThree)

But hat feels cumbersome to maintain. What do you suggest?

So I'm going to divide this into two problems.
This first, using issubclass which results in an API that has the property of giving false positives is something I'm :-1: on.
The second is an efficient way to determine if some/all of the connected endpoints is subscribed to one or more events.
I'm going to advocate that the current API of only exposing any/all is insufficient and that we should rework this to a single lower level API that all the other ones build from.
The following is from the top of my head and has plenty of room for improvement.  Merely meant to be demonstrative of the concept.
def get_connected_endpoints(self) -> Tuple[str, ...]:
    # returns a tuple of the names of all connected endpoints
    ...

def get_remote_subscriptions(self) -> Tuple[Tuple[Optional[str], Set[Type[BaseEvent]]]:
    # returns a tuple of 2-tuples (<endpoint-name>, <subscriptions-set>).
    # connections which don't have a name use `None`
    ...

This exposes the base primitives for doing any check you might want, providing access to the set of connected endpoint names and the full data set of connection subscription information.
These would go on the EndpointAPI.  Then we can move the implementations of the wait_until_all/any onto BaseEndpoint and for cases like what you're trying to do, you can experiment with the right API locally using the base primitive APIs and then contribute it back upstream once you have something you think is right.
Also, get_connected_endpoints API would allow the implementation of is_connected_to to be moved to BaseEndpoint.

I like that direction.

Then we can move the implementations of the wait_until_all/any onto BaseEndpoint

I guess, to make that possible each endpoint would also need to expose an event for when the subscriptions are updated. Otherwise, the only other option for the BaseEndpoint to implement the wait_until_all/any methods that I see would be polling which doesn't seem ideal.
But maybe we can just raise an internal event for that that the BaseEndpoint could stream in the wait_until_all/any APIs.
I'll try something out.

Yeah, use of internal events (not asyncio.Event/trio.Event for signaling seems like it could be a nice way to implement these APIs in a generic way.


move_child/raise does not properly update order of execution

Godot version:
3.1.1 (Steam), 3.2-beta1
OS/device including version:
PC, Windows 10
Issue description:
Children rearranged with move_child method of Node (and raise method by its extension) sometimes receive input events in their initial order, not the actual tree order. The issue does not happen if the script with the _unhandled_input event bound is attached to the root of the child. But if handling is performed by one of the inner nodes of the child, then the order of execution is unexpected.
You can freely rearrange children with move_child and receive input events in tree order, if you have this hierarchy:
Root
- Child 3
- Child 1
- Child 4
- Child 2

The events will go through nodes in the order (2, 4, 1, 3). However, the order of execution will remain (4, 3, 2, 1) for the following hierarchy:
Root
- Child 3
-- ActualClickDetector
- Child 1
-- ActualClickDetector
- Child 4
-- ActualClickDetector
- Child 2
-- ActualClickDetector

By description move_child and raise should rearrange nodes inside their parent with the goal to affect the order of execution for signals and events as well as the draw order. It seems to me, that the inner hierarchy of moved children is not notified that the tree order has been changed.
The issue can be worked around by removing and adding back child (for raise case). But that workaround may not work for all move_child cases, because for that you would need to utilize add_child_below_node, and that method relies back on move_child internally.
Steps to reproduce:

Have a stack of nodes on top of each other (Children), each node (Child) having a shape that serves as a hitbox or boundaries.
Inside each Child there is a structure of nodes for whatever visual and logic purposes it requires; one of those inner nodes is there to detect clicks inside the hitbox (Detector).
Detector has _unhandled_input bound and expects InputEventMouseButton with pressed state; it then checks if a click hit inside its boundaries and performs some action if it did.
Whichever Child detects a click inside the hitbox first, marks input as handled, so other nodes do not receive it; Children receive the unhandled input event in tree order (topmost drawn/last in the hierarchy branch is the first).
Rearrange Children with move_child method, so that they do not follow the initial tree order.
Draw order is updated and respects tree order, however unhandled input is not respecting tree order and events are received in the initial order of Children.

Minimal reproduction project:
Attached: godot-bug-repro-move_child.zip
In this project there are 4 squares, which are added in particular order. Clicking on the topmost node under the mouse will rotate it 45 degrees.
Pressing a move_child button will randomly rearrange nodes with the move_child method. Clicking on the topmost node no longer works, initial order of elements is considered instead.
Pressing a remove_child + add_child button will randomly rearrange nodes with those two methods. Clicking on the topmost nodes still works as expected, actual order of elements is considered.
Clicking a reset order button will revert nodes to their initial order (using remove_child and add_child to achieve consistency).
Note: the example project uses raise instead of move_child for brevity. To my understanding of scene/main/node.cpp the end result is the same.

Still valid in 2c0d1c3


Is this project dead?

I'm waiting for 1.0 release for using in production while I read this article:
http://lua.space/webdev/the-best-lua-web-frameworks
But one years later, there's nothing happened.
So, is this project dead or not?

I'm really sorry! No, it's not dead. I just had to move countries and do visa applications  twice  and finish a master thesis! I'm getting back to it in the next couple of weeks. In the meantime contributions are welcome and if there are any features you are looking for specifically we can start discussion & design at our mailing list for the moment.
https://groups.google.com/forum/#!forum/sailor-l/join


Error: storage.AccountsClient List and listNextResults when retrieving storage accounts in TF Plan

Is there an existing issue for this?

I have searched the existing issues

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version
1.3.5
AzureRM Provider Version
3.39.1
Affected Resource(s)/Data Source(s)
azurerm_storage_account
Terraform Configuration Files
terraform {
  required_version = ">= 1.3"

  backend "azurerm" {
    key = "terraform.tfstate"
  }

  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "= 3.39.1"
    }
    azuread = {
      source  = "hashicorp/azuread"
      version = "=2.33.0"
    }
    random = {
      source  = "hashicorp/random"
      version = "=2.3.1"
    }
    null = {
      source  = "hashicorp/null"
      version = "=3.0.0"
    }
    kubernetes = {
      source  = "hashicorp/kubernetes"
      version = "~> 2.12.1"
    }
    helm = {
      source  = "hashicorp/helm"
      version = "=2.6.0"
    }
  }
}

Debug Output/Panic Output
GET /subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?%24skiptoken=<token>&api-version=2021-09-01 HTTP/1.1
Host: management.azure.com
User-Agent: Go/go1.19.3 (amd64-linux) go-autorest/v14.2.1 Azure-SDK-For-Go/v66.0.0 storage/2021-09-01 HashiCorp Terraform/1.3.5 (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev VSTS_b08a2afe-e3cc-4a64-8dc9-0932bc40bdd9_build_1_0 pid-222c6c49-1b0a-5959-a213-6608f9eb8820
Content-Type: application/json
X-Ms-Authorization-Auxiliary:
X-Ms-Correlation-Request-Id: e7cca614-d21d-b11c-c6f9-1c3b11df891c
Accept-Encoding: gzip: timestamp=2023-05-16T21:22:38.732Z
2023-05-16T21:22:39.106Z [DEBUG] provider.terraform-provider-azurerm_v3.39.1_x5: AzureRM Response for https://management.azure.com/subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?%24skiptoken=<token>&api-version=2021-09-01:
HTTP/2.0 502 Bad Gateway
Content-Length: 149
Cache-Control: no-cache
Content-Type: application/json; charset=utf-8
Date: Tue, 16 May 2023 21:22:39 GMT
Expires: -1
Pragma: no-cache
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: e7cca614-d21d-b11c-c6f9-1c3b11df891c
X-Ms-Failure-Cause: service
X-Ms-Request-Id: 4bf764e6-ab59-45ba-b449-fd7b0779403b
X-Ms-Routing-Request-Id: WESTUS:20230516T212239Z:4bf764e6-ab59-45ba-b449-fd7b0779403b

{"error":{"code":"ProviderError","message":"Resource provider 'Microsoft.Storage' failed to return collection response for type 'storageAccounts'."}}: timestamp=2023-05-16T21:22:39.106Z
2023-05-16T21:23:39.107Z [DEBUG] provider.terraform-provider-azurerm_v3.39.1_x5: AzureRM Request:
GET /subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?%24skiptoken=<token>&api-version=2021-09-01 HTTP/1.1
Host: management.azure.com
User-Agent: Go/go1.19.3 (amd64-linux) go-autorest/v14.2.1 Azure-SDK-For-Go/v66.0.0 storage/2021-09-01 HashiCorp Terraform/1.3.5 (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev VSTS_b08a2afe-e3cc-4a64-8dc9-0932bc40bdd9_build_1_0 pid-222c6c49-1b0a-5959-a213-6608f9eb8820
Content-Type: application/json
X-Ms-Authorization-Auxiliary:
X-Ms-Correlation-Request-Id: e7cca614-d21d-b11c-c6f9-1c3b11df891c
Accept-Encoding: gzip: timestamp=2023-05-16T21:23:39.107Z
2023-05-16T21:23:39.973Z [DEBUG] provider.terraform-provider-azurerm_v3.39.1_x5: AzureRM Response for https://management.azure.com/subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?%24skiptoken=<token>&api-version=2021-09-01:
HTTP/2.0 502 Bad Gateway
Content-Length: 149
Cache-Control: no-cache
Content-Type: application/json; charset=utf-8
Date: Tue, 16 May 2023 21:23:39 GMT
Expires: -1
Pragma: no-cache
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: e7cca614-d21d-b11c-c6f9-1c3b11df891c
X-Ms-Failure-Cause: service
X-Ms-Request-Id: 6a62563e-f585-434e-8c55-d82d70865347
X-Ms-Routing-Request-Id: WESTUS:20230516T212339Z:6a62563e-f585-434e-8c55-d82d70865347

{"error":{"code":"ProviderError","message":"Resource provider 'Microsoft.Storage' failed to return collection response for type 'storageAccounts'."}}: timestamp=2023-05-16T21:23:39.972Z
2023-05-16T21:25:40.055Z [DEBUG] provider.terraform-provider-azurerm_v3.39.1_x5: AzureRM Request:
GET /subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?%24skiptoken=<token>&api-version=2021-09-01 HTTP/1.1
Host: management.azure.com
User-Agent: Go/go1.19.3 (amd64-linux) go-autorest/v14.2.1 Azure-SDK-For-Go/v66.0.0 storage/2021-09-01 HashiCorp Terraform/1.3.5 (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev VSTS_b08a2afe-e3cc-4a64-8dc9-0932bc40bdd9_build_1_0 pid-222c6c49-1b0a-5959-a213-6608f9eb8820
Content-Type: application/json
X-Ms-Authorization-Auxiliary:
X-Ms-Correlation-Request-Id: e7cca614-d21d-b11c-c6f9-1c3b11df891c
Accept-Encoding: gzip: timestamp=2023-05-16T21:25:40.055Z
2023-05-16T21:25:40.381Z [DEBUG] provider.terraform-provider-azurerm_v3.39.1_x5: AzureRM Response for https://management.azure.com/subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?%24skiptoken=<token>&api-version=2021-09-01:
HTTP/2.0 502 Bad Gateway
Content-Length: 149
Cache-Control: no-cache
Content-Type: application/json; charset=utf-8
Date: Tue, 16 May 2023 21:25:39 GMT
Expires: -1
Pragma: no-cache
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: e7cca614-d21d-b11c-c6f9-1c3b11df891c
X-Ms-Failure-Cause: service
X-Ms-Request-Id: d5992d10-dfa0-41a9-91b8-00a3875e0bf9
X-Ms-Routing-Request-Id: WESTUS:20230516T212540Z:d5992d10-dfa0-41a9-91b8-00a3875e0bf9

{"error":{"code":"ProviderError","message":"Resource provider 'Microsoft.Storage' failed to return collection response for type 'storageAccounts'."}}: timestamp=2023-05-16T21:25:40.381Z
2023-05-16T21:27:02.996Z [DEBUG] provider.terraform-provider-azurerm_v3.39.1_x5: AzureRM Request:
GET /subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?api-version=2021-09-01 HTTP/1.1
Host: management.azure.com
User-Agent: Go/go1.19.3 (amd64-linux) go-autorest/v14.2.1 Azure-SDK-For-Go/v66.0.0 storage/2021-09-01 HashiCorp Terraform/1.3.5 (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev VSTS_b08a2afe-e3cc-4a64-8dc9-0932bc40bdd9_build_1_0 pid-222c6c49-1b0a-5959-a213-6608f9eb8820
X-Ms-Authorization-Auxiliary:
X-Ms-Correlation-Request-Id: e7cca614-d21d-b11c-c6f9-1c3b11df891c
Accept-Encoding: gzip: timestamp=2023-05-16T21:27:02.996Z
2023-05-16T21:27:02.997Z [ERROR] provider.terraform-provider-azurerm_v3.39.1_x5: Response contains error diagnostic: diagnostic_detail= diagnostic_summary="retrieving Account "***": retrieving next page of storage accounts: storage.AccountsClient#listNextResults: Failure sending next results request: StatusCode=502 -- Original Error: context deadline exceeded" tf_proto_version=5.3 tf_provider_addr=provider @module=sdk.proto tf_rpc=ReadResource @caller=github.com/hashicorp/terraform-plugin-go@v0.14.1/tfprotov5/internal/diag/diagnostics.go:55 diagnostic_severity=ERROR tf_req_id=55233742-8039-fcf4-2248-8dfb8f54b575 tf_resource_type=azurerm_storage_account timestamp=2023-05-16T21:27:02.997Z
2023-05-16T21:27:02.998Z [ERROR] vertex "module.system_storage_account.azurerm_storage_account.main" error: retrieving Account "***": retrieving next page of storage accounts: storage.AccountsClient#listNextResults: Failure sending next results request: StatusCode=502 -- Original Error: context deadline exceeded
2023-05-16T21:27:02.998Z [ERROR] vertex "module.system_storage_account.azurerm_storage_account.main (expand)" error: retrieving Account "***": retrieving next page of storage accounts: storage.AccountsClient#listNextResults: Failure sending next results request: StatusCode=502 -- Original Error: context deadline exceeded
2023-05-16T21:27:03.167Z [DEBUG] provider.terraform-provider-azurerm_v3.39.1_x5: AzureRM Response Error: Get "https://management.azure.com/subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?api-version=2021-09-01": context deadline exceeded for https://management.azure.com/subscriptions/<subscription id>/providers/Microsoft.Storage/storageAccounts?api-version=2021-09-01: timestamp=2023-05-16T21:27:03.167Z
2023-05-16T21:27:03.169Z [ERROR] provider.terraform-provider-azurerm_v3.39.1_x5: Response contains error diagnostic: diagnostic_detail= diagnostic_summary="retrieving Account "***": retrieving storage accounts: storage.AccountsClient#List: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded" tf_req_id=b210e926-5849-4ec3-882d-990ce8b45bb6 tf_resource_type=azurerm_storage_account @module=sdk.proto diagnostic_severity=ERROR tf_proto_version=5.3 tf_provider_addr=provider tf_rpc=ReadResource @caller=github.com/hashicorp/terraform-plugin-go@v0.14.1/tfprotov5/internal/diag/diagnostics.go:55 timestamp=2023-05-16T21:27:03.168Z
2023-05-16T21:27:03.169Z [ERROR] vertex "module.storage_account.azurerm_storage_account.main" error: retrieving Account "***": retrieving storage accounts: storage.AccountsClient#List: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded
2023-05-16T21:27:03.169Z [ERROR] vertex "module.storage_account.azurerm_storage_account.main (expand)" error: retrieving Ac

Expected Behaviour
Terraform should get the full list of storage accounts.
##Actual Behaviour
│ Error: retrieving Account "": retrieving storage accounts: storage.AccountsClient#List: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded
│
│ with module.storage_account.azurerm_storage_account.main,
│ on ../../../modules/providers/azure/storage-account/main.tf line 19, in resource "azurerm_storage_account" "main":
│ 19: resource "azurerm_storage_account" "main" {
│
╵
╷
│ Error: retrieving Account "": retrieving next page of storage accounts: storage.AccountsClient#listNextResults: Failure sending next results request: StatusCode=502 -- Original Error: context deadline exceeded
│
│ with module.system_storage_account.azurerm_storage_account.main,
│ on ../../../modules/providers/azure/storage-account/main.tf line 19, in resource "azurerm_storage_account" "main":
│ 19: resource "azurerm_storage_account" "main" {
│
Steps to Reproduce
This error happens in terraform plan.
My suspicion is that there is a maximum limit of storage accounts under the same subscription to be retrieved from storage.AccountsClient List API. If existing storage accounts exceeded the limit, storage.AccountsClient List API will unable to reply.
Important Factoids
No response
References
No response

If run Azure-CLI storage account list command, error will trigger as well:
az storage account list --subscription <subscription-id>
(ProviderError) Resource provider 'Microsoft.Storage' failed to return collection response for type 'storageAccounts'.
Code: ProviderError
Message: Resource provider 'Microsoft.Storage' failed to return collection response for type 'storageAccounts'.

@Pilotindream
The error is reported from storage server, so this is a server issue.
Would you like to raise a help request in Azure portal like following picture, then the related team will be engaged to help you?

@Pilotindream I hope you had a chance to look at the above comment. Could you please check if you had a chance to try the above suggestion ? If that didn't help, please open a support request with Microsoft as mentioned above.

@Pilotindream I hope you had a chance to look at the above suggestion. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.

We also sometime getting this issue. Once we got it on Sep 28 2023, when it got resolved without us doing anything next day. Now we got this again in one of our subscriptions. We opening an issue with Microsoft this time.


Show available custom capabilities

As multiselect with influence to example.
Maybe provide special node in status handle for available custom capabilities

Fixed in https://github.com/aerokube/selenoid-ui/pull/32.

https://github.com/aerokube/selenoid-ui/pull/284

Custom usecase for capability like environment : We have multiple application host - so i create a session with custom label like environments with value for example TeamCity ( used lable just for example like "manual")
 , please add ability to view this capability right in grid with active sessions

This could be added here iterating over labels
https://github.com/aerokube/selenoid-ui/blob/master/ui/src/components/Sessions/index.js#L93

that would look something like this

needs to be tested with different labels length as well as their number. I would propose something like key:value as the content of the badge, but maybe just value could be fine as well - feel free to try different ways


typo(Event): repository variable

draft
Hey, this is still in draft. The previous PR did have an issue. I still come across minor issues here and there.

Sorry, I saw you already fixed that one.


[Go Live][May 25]

Push to live

Docs Build status updates of commit fcb9162:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/m365-apps/extend-m365-teams-message-extension.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/extend-m365-teams-personal-tab.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/overview.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/prerequisites.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/publish.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Solid Angles: improve _GG.LOS_isVis_PtFromPts_VesStruct (flexibilty, kwdargs and multiple points)

Function _GG.LOS_isVis_PtFromPts_VesStruct() needs to be modified along the following lines:

should take not 1 but N pts as input (and return a N,M) array of boolean indices
k should be an optional keyword arguments (computed if not provided)
VPoly and VIn should be keyword arguments

This way teh fonction can easily be called for a large number of points from a config instance, and the inputs can be provided by an appropriate dictionnary produced by a specific Config class method.

I'm debuggin right now, and I am having a question for the 'k' and 'vis' arguments, as there are no comments I rather asked: What are the roles of k and vis ?
indok = ~(np.isnan(k) | np.isnan(kPOut))
if vis:
    ind = np.zeros((npts,),dtype=bool)
    ind[indok] = k[indok] < kPOut[indok]
else:
    ind = np.ones((npts,),dtype=bool)
    ind[indok] = k[indok] > kPOut[indok]
return ind

It seems that if we have a certain result ind with vis=True, then we will get ~ind with vis=False and that k is a kin (a.k.a. kmin), is this exact ?

Hi (sorry, was away the last days),
k is the distance from pts to Points (sometimes already calculated and provided by the user, if not it must be calculated).
vis is a keyword argument to indicate what we want as an output.
In principle, if we have:
ind0 = LOS_isVis_PtFromPts_VesStruct(..., vis=False, ...)
ind1 = LOS_isVis_PtFromPts_VesStruct(..., vis=True, ...)

We should have ind0 = ~ind1,
But in practice there may be some points for which the answer is not known because the intermediate function Calc_LOS_PInOut_Tor return NaN.
For those points, they are considered as False if vis=True, and False again if vis=False (so the function on ly returns True when the result is known, reliable and clear).
There might be a more clever way to do that, though.

Also, it would faster to call an intermediate function (Calc_LOS_PInOut_Tor) that only computes k (and not the 3 coordinates of each points)


Low level SCMP parser

This provides parser support for our existing SCMP libraries.
SCMP checksum not implemented yet.

This change is

Stalled for way too long. Closing.


PowerRenaming - renaming an item on OneDrive fails

A change to PowerToys v.20 added the ability for PowerRename to appear in the context menu for OneDrive contents.  Unfortunately, the actual rename fails in the below call to SHCreateItemFromParsingName with a filesystem path to a OneDrive item.  Returns 0x80004002 (E_NOINTERFACE).
IFACEMETHODIMP CPowerRenameItem::get_shellItem(Outptr IShellItem** ppsi)
{
return SHCreateItemFromParsingName(m_path, nullptr, IID_PPV_ARGS(ppsi));
}

Hmm... now I can't repro.


Update 'connected' variable in DbConnection Class

In the DbConnection class, there is a private variable named 'connected' which should be true if the user is connected to the database (after getRemoteConnection() is called) or false if they are not connected. Currently, it is not being updated to true when getRemoteConnection() is called. The code should be fixed so that the variable is up to date at all times.

There might be a method on the Connection object that we can provide a wrapper for, in lieu of duplicating that state.

The connection class that DbConnection is built off of has an isValid( ) method that checks whether there is a connection to the database. It works by sending a simple query, which seems more reliable than tracking it ourselves (especially since it is possible that you could lose connection, but the variable would not be updated).
You could call this at the beginning of each intent handler method, but then you would be querying the database twice - once to test for connection and then once with your actual query for information. I'm thinking about adding key/value to the map returned by the runQuery( ) method that would reflect whether the app was able to connect, so that we don't crash if there is no connection. Then, the handler methods would look like this:
if(!results.get("WasAbleToConnect").get(0))
    return newTellResponse("Sorry, I could not access my source of information at the moment", false);
else
    // Do normal response stuff

If the test is simply doing a query, then I guess we can just do whatever query we wanted to do in the first place and check if the result is null to find out if we were connected or not.


Add wordSeperator in config for integrated terminal (xterm)

This PR fixes #82173
A new section Terminal->Integrated->Word Separator has been added to the config with a default value of  ()[]{}'",. This value is further passed to the xterm.js constructor.

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

I think we should actually just change the default in xterm.js as it makes a lot of sense like this and have that bubble up to vscode: https://github.com/xtermjs/xterm.js/issues/2463
Also I'd like to avoid adding yet another setting unless there's a really compelling case to add it.

I would like to ask that this be reconsidered. Most modern terminals come with a default set of characters to include or exclude when double-clicking and let the user change the set if their workflow demands it, e.g. xfce4-terminal:

I ran into this because I used to double-click to select URLs in the vscode terminal, but this change in xtermjs removed that ability by removing the colon as part of a "word": https://github.com/xtermjs/xterm.js/pull/2474 This list, is as far as I can tell, now hard-coded into vscode.

Already undone https://github.com/microsoft/vscode/commit/502fe137129301c43cdc3da0b0516b42907d9544, we may add a setting for it in the future but I think it's in a decent state now.

That was certainly a much quicker response than I was expecting. Thanks for the follow-up.


JBPM-4895: Console: null column pre-selected when creating new Tasks …

…filter

It sounds like this test should go in dash builder? or the DataSetFilterEditor is bpm specific?

This code is related with the DatasetFilterEditor specific for the console. Just to allow create new filters, not to modify existing ones.

Looks good to me, just some minor update in the test class.

+1

master: 48c83c406ba24c32e2c5971ba31c6399b4867ecf


Make init callback optional

Hey Brian,
As we discussed during JSConf.eu, I think callbacks should actually be optional, especially when dealing with storage adapters we know are synchronous (e.g. localStorage). I see a lot of people just passing $.noop or Prototype.emptyFunction or function(){} as final arg, just because they have to.
So here's my pull request, with relevant passing tests :-)
Cheers!

Actually, I think the callback should be removed.

In an asynchronous environment, removing callbacks can lead to bad code like using 'setTimeout' to wait for initialization to complete.
Although I have already seen Bryan argue against deferred objects for the sake of execution speed, I wish Lawnchair used them.  In that case, you could ignore the returned promise.


add trail (row) selectors

Similar to tdb_set_filter, which filters events, it would be nice to get a view of traildb which only includes a subset of trails.
This could be especially powerful when paired with tdb_cons_append, since this would allow one to materialize a subset of an existing traildb.

Fixed by http://traildb.io/docs/technical_overview/#whitelist-or-blacklist-trails-a-view-over-a-subset-of-trails


Import Int64 type

browser.js file in apache/thrift repository doesn't export Int64 type in case of nodejs which will cause undefined type errors. This way we can't use the generated typescript files for clients.
This pull request creates an import for Int64 type in the generated typescript files if there are any usage of such type in the thrift files.

This was included in v2.0.5


Rendering is flipped (UD)

Rendering is flipped upside down around the x-axis.
(top left origin vs bottom left origin)

The rendering is fixed. Now the y-coordinate is updated accordingly.
However, there are wrong collisions detected along the track. It seems that removing the transpose (see map loading in track.py) messes up with the edt used in the scan computation.
@hzheng40 can you have a look?
It seems the transpose was already in the old gym (see set_map in main branch). So I guess the scan computation was relying on that somehow.


vxTwitter doesn't work with X links

So recently Twitter/X updated how you share on mobile, replacing Twitter links with X links instead, e.g. https://x.com/sorainu1211EAKA/status/1702276756944851399
vxTwitter doesn't seem to work with X links at this moment.
EDIT: I should elaborate. You can change X to vxtwitter and it will work, but it is quite a hassle to do so in my opinion.

Duplicate of #142
tl;dr Replace x.com links with fixvx.com (add fixv at the beginning)


Support Tact 1.4.0

The following is the list of IDE-relevant changes for Tact v1.4.0 which has been released. The full changelog is here: https://github.com/tact-lang/tact/blob/main/CHANGELOG.md#140---2024-06-21.
New or changed syntax

[ ] Unary bitwise NOT operation: ~.
[ ] Augmented assignment bitwise operators: |=, &=, ^=.
[ ] foreach loop for the Map type now works not only with simple identifiers, but with contract storage and struct fields too: foreach (k, v in self.map) {...} or foreach (k, v in struct.map) {...}.
[ ] Trailing semicolons in struct/message declarations are optional now: struct Foo {x: Int} is valid syntax now.
[ ] Trailing semicolon in for the last statement in a block is optional now: { let x: Int = 42 } is valid syntax now.
[ ] Type annotation for let-statements are optional now: let x = 42 is valid syntax now.

stdlib functions

[ ] Fixed the return type of skipBits in stdlib/std/cells.tact: extends mutates native skipBits(self: Slice, l: Int) (used to return Int, now it's void).
[ ] New loadBool method for slices.
[ ] New fromCell and fromSlice methods for struct parsing.
[ ] nativeThrowWhen has been renamed to nativeThrowIf.

Tact v1.4.0 has just been released, looking forward to see it supported in VS Code!

Tact v1.4.0 has just been released, looking forward to see it supported in VS Code!

ok, I will start next week already

Btw, in terms of Marketplace publishing, we should target Tact v1.4.1 bugfix release, which is going to be release early next week.

Added v1.4.0, I will wait for v1.4.1

Added v1.4.0, I will wait for v1.4.1

We just released 1.4.1 --<EMAIL_ADDRESS>

The new version for v1.4.1 has been published on the marketplace.

Awesome! Thanks so much. I'll open a separate issue to support Tact v1.4.2 which accumulates lots and lots of bug fixes


Clean up following merge

Minor rearrangement following deferred proxy merge and autopep8.  This will be merged once it clears CI.  Moved common functions to global scope so they don't get reevaluated multiple times.  Split deferred and non-deferred declaration paths to save attribute lookups.

Codecov Report

Merging #661 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #661      +/-   ##
==========================================
+ Coverage   78.05%   78.06%   +0.01%
==========================================
  Files         122      122
  Lines        9016     9024       +8
  Branches     3862     3862
==========================================
+ Hits         7037     7045       +8
+ Misses       1449     1448       -1
- Partials      530      531       +1

Impacted Files
Coverage Δ

jpype/_jproxy.py
95.60% <100.00%> (+1.62%)
:arrow_up:

native/common/jp_methoddispatch.cpp
83.33% <0.00%> (-1.20%)
:arrow_down:

Continue to review full report at Codecov.

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


.NET Standard v2.1 not working (Old Issue title: .NET Core 3.1 not working)

I am using Azure Media Services with a .NET Core 3.1 solution.
I would really like to use this library for migration, but it is not available due to a dependency error.
Can you please make it available?
Thank you.

Hello,
Sure, I added .Net Core 3.1 compatibility. Please update to version 1.0.10 and let me know if this works.
https://www.nuget.org/packages/MK.IO/

I will try it!!
Thanks for the quick response.

Hello
Sorry, I was using Azure Media Services from a .NET Standard v2.1 project (the same solution had a .NET Core 3.1 project).
I am getting a warning that it is not compatible.
Can you please support .NET Standard v2.1?
Also, I get the following CS1705 compile error when I try to get it from nuget and use it.
How should I deal with this?
Will .NET Standard v2.1 solve this problem?
CS1705
Assembly 'MK.IO' (ID 'MK.IO, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null') uses
'System.Runtime' (ID 'System. Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a')
which has a higher version than referenced assembly
'System.Runtime' (ID 'System. Runtime  Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a')

Hi,
I added support for .NET Standard and re-released the SDK.
See https://www.nuget.org/packages/MK.IO/1.0.11#supportedframeworks-body-tab
I don't know if this will solve CS1705. Please try the new version.

Hello.
Thanks as always for your quick response.
I tried from nuget and CS1705 was still the same.
I cloned the solution, linked it to my project and started it and it worked.
Here is my guess.
I am a little concerned that you are building with dotnet-version: 7.x in github workflows.
Runtime seems to have changed before and after .NET 7.
CS1705 occurred when I linked directly to netcoreapp3.1 MK.IO DLL (v<IP_ADDRESS>) and netstandard2.0 MK.IO DLL (v<IP_ADDRESS>) from nuget's download folder.
At the time of build, all MK.IO.DLLs seem to be using System.Runtime version <IP_ADDRESS>.
Reference
https://learn.microsoft.com/en-US/dotnet/standard/net-standard?tabs=net-standard-2-1#tabpanel_1_net-standard-2-1
https://stackoverflow.com/questions/75779845/dll-from-a-net-7-project-in-net-3-1-project
The best I can hope for is to be able to get it from nuget and use it as is in my solution.
I will continue to investigate and would appreciate it if you could contact me as soon as you find out something there as well.

Ok, I was able to reproduce the problem. I will investigate.

I finally found the issue! It took me time.. It was a problem with my GitHub action script which was putting all the SDK DLL from various .Net versions in the same folder. Then the nuget package was incorrect.
Please try version 1.0.14 on Nuget. It should work now.

Hello.
I just tried it and it works!
Thank you for solving the problem from my poor guess.


revert shell to bash when default bash shell is msys2 in windows image

actually allow injecting shell when https://github.com/actions/runner/issues/835 is fixed

this bug should be for another action, not this one...


adding 'orderBy' field to 'getEntries()' call results in zero entries being returned

I am querying stack driver using the code below.  The resulting query looks like:
resource.type="cloud_function"
resource.labels.function_name="handleClientOrder"
d0b5fb63-0214-11ea-8de1-0242ac110004

(If I paste this query into the stackdriver web ui it returns lots of results)
If I add orderBy: 'timestamp' to the options this query returns zero results.  If I remove it I get non-zero results.
const logging = new Logging();
const log = logging.log(`projects/${PROJECT_ID}/logs/cloudfunctions.googleapis.com%2Fcloud-functions`);

const pageSize = 3;
const orderBy = 'timestamp';
const filter = ['resource.type="cloud_function"', `resource.labels.function_name="${functionName}"`, queryText].join("\n");

const [entries, request, response] = await log.getEntries({
    filter,
    pageSize,
    //orderBy <- removing this makes the query work
});

const items = [];

for (let entry of entries) {
    const text = entry.data.toString();
    items.push(text)
}

Hey @npomfret Documentation/sample might mislead you.
The proper way to do orderby is "timestamp asc" or "timestamp desc" (default).
Please find reference for Java and Python Client.
I will create PR shorty about documentation and samples.


How to properly shutdown the ChangeFeedHost

What would be the right way to shutdown the host along with its observer. There was some code added #47 but I see that was later reverted.
Should we just terminate the executor service or is there a way to do proper shutdown such that leases can be removed?

In our case we do close the ExecutorService attached with ChangeFeedEventHost but still see error logs upon close like
[2019-06-07T06:51:03.639Z] [ERROR] Other exception not handled happened: null
java.lang.NullPointerException
	at com.microsoft.azure.documentdb.changefeedprocessor.services.CheckpointServices.getCheckpoint(CheckpointServices.java:77)
	at com.microsoft.azure.documentdb.changefeedprocessor.services.CheckpointServices.getCheckpointData(CheckpointServices.java:49)
	at com.microsoft.azure.documentdb.changefeedprocessor.services.ChangeFeedJob.QueryChangeFeed(ChangeFeedJob.java:159)
	at com.microsoft.azure.documentdb.changefeedprocessor.services.ChangeFeedJob.lambda$start$0(ChangeFeedJob.java:136)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)

Seems like each ChangeFeedJob has its own ExecutorService instance and there is no direct way to trigger its close as partitionManager instance is not exposed from the ChangeFeedEventHost


Select Menu

Issue Description
A new single select menu component is needed. This functionality already exists in the terra-form-select component. This logic needs to be pulled out into it's own component and updated with theming capability for the small screen size styles.
Issue Type

[x] New Feature
[ ] Enhancement
[ ] Bug
[ ] Other

JIRA created

@bjankord would you be able to post a comment when you close issues for easier reference?

Closed as not applicable.


TACKLE-558: Task cancelation

https://issues.redhat.com/browse/TACKLE-558

@gildub Per discussion with @jortel, a task in a scheduled state should be able to be cancelled also.

@ibolton336, tasks that are "Created" (Scheduled), "Running" (InProgress) or "Ready" (Scheduled) can be cancelled.

Can we cancel pending /scheduled tasks?


Progress bar not displayed when submitting a form

I noticed that the progress bar is not displayed when submitting a form.
While trying to understand the reason, I noticed that showProgressBarAfterDelay is called only after the submit is finished.
The method is called by visitRequestStarted, called by startRequest, and by keep going back into the stack, they are called into formSubmissionSucceededWithResponse, so when the submit is already terminated.
The result is that the progress ber is not displayed.
Is this a bug, or did I miss something?

I'm having the same issue, it looks like you have to redirect AFTER handling the form-submission:
Turbo Drive handles form submissions in a manner similar to link clicks. The key difference is that form submissions can issue stateful requests using the HTTP POST method, while link clicks only ever issue stateless HTTP GET requests.

After a stateful request from a form submission, Turbo Drive expects the server to return an HTTP 303 redirect response, which it will then follow and use to navigate and update the page without reloading.

That doesn't work for me because I want to redirect the users to a different page, and that extra request is not ideal.
An option for me would be to disable Turbo on the actual form, but right now that's not possible, although there is an open PR for that https://github.com/hotwired/turbo/pull/3
Hopefully that one will get merged soon 🤞
@coorasse please let me know if you find a workaround for this issue.
Cheers,
Jeff.

Ok, I found a temporal solution. Using the custom turbo events, you can capture the submit-start to load the progress-bar manually as follows:
<script>
    document.addEventListener('turbo:submit-start', function () {
        Turbo.navigator.delegate.adapter.showProgressBar();
    });
</script>

I  posted on the Hotwire forums asking whether it should be default for the progress bar to always show on form submission. Otherwise, repeatedly rejected forms can appear as no-ops...

I  posted on the Hotwire forums asking whether it should be default for the progress bar to always show on form submission. Otherwise, repeatedly rejected forms can appear as no-ops...

Ok, I found a temporal solution. Using the custom turbo events, you can capture the submit-start to load the progress-bar manually as follows:
<script>
    document.addEventListener('turbo:submit-start', function () {
        Turbo.navigator.delegate.adapter.showProgressBar();
    });
</script>

Is this still working for the latest version of Turbo? I'm loading Turbo via the hotwire-rails gem (and via the asset pipeline) and I get a Turbo is not defined error....

@wnm try
import { Turbo } from "@hotwired/turbo-rails"
window.Turbo = Turbo // Turbo available throughout app


Cold Fear → lighting issues

With d9vk

Without d9vk

System information

GPU: Nvidia GT 730M
Driver: 430.26-9
Wine version: Proton 4.2
DXVK version: 0.13

Apitrace file(s)
steam.2.trace.tar.gz
https://mega.nz/#!evQRiKoa!lL1qOOT7Uf758NYnSWwEKiX5T7DLg6ZmVHbHH8xsTfQ
Log files
coldfear_retail_d3d9.log

This is an OpenGL trace which is not useful to me. Please provide a D3D trace.

D3D trace (without d9vk installed):
https://mega.nz/#!m3w1wSob!VlaAmKtdVan3ujOQmJYzoL7Ir06qCTOY8odDdlDwd38

Fixed :tada:
Tested with #745 (jobs)


Support TS config files

ESLint 9.9.0 was just released with support for TS config files:
https://github.com/eslint/eslint/pull/18134

Not sure if it's as simple as adding eslint.config.ts, eslint.config.mts, and eslint.config.cts to https://github.com/microsoft/vscode-eslint/blob/release/3.0.10/server/src/eslint.ts#L800

Need also to at least pass --flag unstable_ts_config, but not having success using a TS config with just ESLint myself yet.
https://eslint.org/docs/latest/use/configure/configuration-files#typescript-configuration-files

You can add the following settings:
{
  "eslint.options": {
    "flags": ["unstable_ts_config"]
  }
}

eslint.options: options to configure how ESLint is started using either the ESLint class API or the CLIEngine API.
options.flags (string[])
Default is []. The feature flags to enable for this instance.

https://eslint.org/docs/latest/integrate/nodejs-api#parameters
https://github.com/Microsoft/vscode-eslint#settings-options

I added mjs and cjs to the watcher pattern. With the ts I would like to wait to see where the feature in eslint is heading to.

@dbaeumer what questions can I answer about this feature for you?
(In general, feel free to reach out via GitHub discussion or Discord if you're ever blocked waiting for info about what ESLint is doing.)

@nzakas my biggest question is currently why this is in ESLint since NodeJS itself added experimental support for this: https://nodejs.org/api/typescript.html#type-stripping

@dbaeumer because ESLint needs to run on multiple versions of Node.js, some of which don't have experimental support, as well as Bun and Deno. Once TypeScript support is built into Node.js as stable, and we are able to move off of support for older versions, we can remove the jiti dependency.

Hello, eslint VS extensions keeps looking for .eslintrc even though we migrated to eslint v9 and now using flat config base eslint.config.mjs
Any help? @polyzen @nzakas @dbaeumer

@gorstak17 please open a fresh issue for your problem, best with a GitHub repository I can clone with a minimal repro case that demos the problem you are seeing. This being said, please ensure that ESLint works correctly in the terminal before file the issue.

Anyone facing issues with an npm workspaces setup, you will need to also enable "eslint.workingDirectories": [{ "mode": "auto" }].


allow setting belongs_to optional: true

We have an audit model that gets used by all model classes. Some models are not per tenant (global). So we would like to say, that tenant is optional in audit class
class Audit < ApplicationRecord
  multi_tenant :tenant, optional: true
end

So we want to allow setting the optional: true on the belongs_to.

@vollnhals I wonder if it might not be better to include the multi_tenant annotation separately in each model then.
The belongs_to is one minor side effect of adding multi_tenant to a class. The more important change based on it happens in query rewriting, which you wouldn't want on a class thats not tenant-specific.
Maybe you can move the multi_tenant definition into a separate concern that gets included in those classes that are actually associated to a tenant?

@lfittl I cannot add the multi_tenant annotation separately in each model, because the Audit model belongs to many class polymorphically and the Audit model needs to have the multi_tenant behavior.
I will try to explain in more detail.
We use the audited gem to audit changes to application models. The gem allows you to provide / customize the Audit class. But there is only this one class, we cannot provide two versions (one with multi_tenant, one without).
We added multit_tenant :tenant to the audit class and it works for all the application models that are also multi tenanted.
But we have some models that are not multi tenant. In these cases the corresponding audit record also cannot have a tenant_id. So now Rails complains with a validation error that the belongs_to that was automatically added, has no value present.
The only solution I see is to disable that validation.
So that's why I added optional as an allowed argument.
Would you reconsider adding that change or do you see another better way to do it?

Closing in favor of #147 which includes tests


404 Error: Clicking on "LICENSE" Badge

Just going through I noticed that your license badge link is going to a 404.
https://github.com/kentcdodds/validate-commit-msg/blob/master/other/LICENSE
The culprit being:
https://github.com/kentcdodds/validate-commit-msg/blob/master/      OTHER      /LICENSE

Cool, thanks for finding that. Could you makeapullrequest.com?

On another note, trying Attempt 1, this raises a few questions..
By default semantic-release will push everything up to NPM, but since this is a Forked repo, that step isn't really necessary. Is semantic release smart enough to know the difference or is this something that the developer needs to be aware of?
I'm pretty fresh w/ semantic-release  so I'm not sure about these small intricacies.

Hey @oneezy,
I apologize that you had these difficulties! I've just worked on things to make them a little more straightforward and hopefully improve your contributing experience!
Could you follow the new Contributing guidelines and let me know whether that works better for you.
As with semantic-release, you should probably not be doing anything with that directly. Commitizen however should definitely work. Give it another shot and let me know if you have any additional trouble. Thanks!

I hope it's ok I went through and fix that @oneezy!


Tags Overview markup is broken

Steps to reproduce
Open https://rubydoc.info/gems/yard/file/docs/Tags.md#abstract
Actual Output
Starting with @abstract HTML tags start to sneak in making the doc hard to read:

Expected Output
Has no HTML tags:

Environment details:

OS: macOS 10.14, Firefox/Chrome

I have read the Contributing Guide.

Fixed in https://github.com/lsegal/yard/commit/4a8a1c70cee358c8ccd96ba7926aa11e278c8197
Thanks @lsegal ! ⚡

Thanks for reporting! This was also released in v0.9.23 updated rubydoc.info as well.


HttpRequest from dart:html don't not work in web workers on Safari

XMLHttpRequests which, according to MDN should work in regular web workers, don't work in Safari web workers when used through dart:html.
To reproduce this issue, setup a new Dart web project from the template (dart create -t xhr_worker). Create a new file web/worker.dart with the following content:
import 'dart:html';

void main() async {
  print(await HttpRequest.getString('index.html'));
}

Also, change web/main.dart as follows:
import 'dart:html';

void main() async {
  Worker('worker.dart.js');
}

I run this example with dart run build_runner serve "--define=build_web_compilers:entrypoint=compiler=dart2js" web:8080.
This works in Firefox and in Chrome, but fails in Safari (throws in _failedAsCheck, where object is an XMLHttpRequestProgressEvent and testRti is the RTI for Event).
Also, it's interesting that J.getInterceptor$(new Event('a')) returns a Dart Event, but J.getInterceptor$(object) returns an UnknownJavaScriptObject, even though the object is an event as well. I suspect this is because, despite these events being delivered in workers, the global scope for workers does not include XMLHttpRequestProgressEvent in Safari. Is there a way for the Dart SDK to work around this issue?

same issue for me too. Runs fine in chrome. but fails in safari.


Allow multiple alias arguments

This change makes up somewhat for thefuck's >100ms time to print the
aliases.
Some profiling shows that 50% of that time is spent loading a bunch of
unsued packages, and the other 50% is unavoidable overhead for starting
a python script.

Before, setting 10 aliases meant a 1second shell startup. Now:
$ time thefuck --alias a b c d e f g h i j
thefuck --alias a b c d e f g h i j  0.20s user 0.04s system 96% cpu 0.256 total
Not bad!

Bug in my PR:
TF_ALIAS doesn't get set, even though it is in the function:
function x () {
    TF_PYTHONIOENCODING=$PYTHONIOENCODING;
    export TF_SHELL=bash;
    export TF_ALIAS=x;                <---------------------
    export TF_SHELL_ALIASES=$(alias);
    export TF_HISTORY=$(fc -ln -10);
    export PYTHONIOENCODING=utf-8;
    TF_CMD=$(
        thefuck THEFUCK_ARGUMENT_PLACEHOLDER "$@"
    ) && eval "$TF_CMD";
    unset TF_HISTORY;
    export PYTHONIOENCODING=$TF_PYTHONIOENCODING;
    history -s $TF_CMD;
}

Bug in my PR:
TF_ALIAS doesn't get set, even though it is in the function:
function x () {
    TF_PYTHONIOENCODING=$PYTHONIOENCODING;
    export TF_SHELL=bash;
    export TF_ALIAS=x;                <---------------------
    export TF_SHELL_ALIASES=$(alias);
    export TF_HISTORY=$(fc -ln -10);
    export PYTHONIOENCODING=utf-8;
    TF_CMD=$(
        thefuck THEFUCK_ARGUMENT_PLACEHOLDER "$@"
    ) && eval "$TF_CMD";
    unset TF_HISTORY;
    export PYTHONIOENCODING=$TF_PYTHONIOENCODING;
    history -s $TF_CMD;
}

The problem is a littlle bit deeper than that, since really it doesn't make sense to have this variable that has "the alias". Of course, you can have more than one alias!
So the variable should just be done away with, and the tests for it.

The problem is a littlle bit deeper than that, since really it doesn't make sense to have this variable that has "the alias". Of course, you can have more than one alias!
So the variable should just be done away with, and the tests for it.

Furthermore, the "feature" of printing out the current alias magically with a nullary --alias also makes no sense when using multiple aliases, and has to go.

Furthermore, the "feature" of printing out the current alias magically with a nullary --alias also makes no sense when using multiple aliases, and has to go.

Thanks for taking the time to contribute, that's appreciated.
I'm afraid this feature won't benefit the majority of users. Even if it would — and it certainly does benefit some users — it can be solved in the shell by using alias. Every change adds complexity to the code. Code that need to be maintained. The less code we need to add the better.
Could you please try using alias and see if it is quick enough?
I tried on my end and the difference wasn't noticeable. Before changing .bashrc to include additional aliases:
$ cat .bashrc
eval "$(thefuck --alias)"
$ time bash .bashrc

real	0m0.163s
user	0m0.088s
sys	0m0.071s

After changing .bashrc to include additional aliases:
$ cat .bashrc
eval "$(thefuck --alias)"
alias f=fuck
alias k=fuck
alias fk=fuck
alias fu=fuck
alias fck=fuck
alias fuc=fuck
alias fuk=fuck
$ time bash .bashrc

real	0m0.165s
user	0m0.088s
sys	0m0.073s

Thanks for taking the time to contribute, that's appreciated.
I'm afraid this feature won't benefit the majority of users. Even if it would — and it certainly does benefit some users — it can be solved in the shell by using alias. Every change adds complexity to the code. Code that need to be maintained. The less code we need to add the better.
Could you please try using alias and see if it is quick enough?
I tried on my end and the difference wasn't noticeable. Before changing .bashrc to include additional aliases:
$ cat .bashrc
eval "$(thefuck --alias)"
$ time bash .bashrc

real	0m0.163s
user	0m0.088s
sys	0m0.071s

After changing .bashrc to include additional aliases:
$ cat .bashrc
eval "$(thefuck --alias)"
alias f=fuck
alias k=fuck
alias fk=fuck
alias fu=fuck
alias fck=fuck
alias fuc=fuck
alias fuk=fuck
$ time bash .bashrc

real	0m0.165s
user	0m0.088s
sys	0m0.073s

Could you please try using alias and see if it is quick enough?

$ cat .bashrc
eval "$(thefuck --alias)"
alias f=fuck
alias k=fuck
[...]

Oops, that really does negate the need for this issue indeed; I wasn't aware that this was possible!
Still, I think thefuck is way too slow at 165ms  just to make an alias. Would be good to pull that code out of all of the packaging systems and whatnot, could probably get it down to 50ms without any change in functionality.

Could you please try using alias and see if it is quick enough?

$ cat .bashrc
eval "$(thefuck --alias)"
alias f=fuck
alias k=fuck
[...]

Oops, that really does negate the need for this issue indeed; I wasn't aware that this was possible!
Still, I think thefuck is way too slow at 165ms  just to make an alias. Would be good to pull that code out of all of the packaging systems and whatnot, could probably get it down to 50ms without any change in functionality.


Extension - Configuration - Part 1: Initial configuration utilities

This is laying the groundwork for handling configuration properly from extensions, which define configuration settings, and wiring them up into the extension host.
When we send configuration updates to the extension host, there are two things we need:

A list of keys that have changed, with the full-path, like typescript.suggest.enabled.
The fully-expanded configuration, like: { "typescript": { "suggest": { "enabled": true } } }

We're missing both of these pieces today (well, we hard-code them specifically for the typescript / javascript language services - but that doesn't scale to bringing in new extensions).
This adds a couple of utilities that let us expand JSON into the fully-expanded format, and also gather a list of keys. These utilities will enable us to bring in the configuration settings and wire them up to be sent to the extension host.

/azp run


added some metabolic functions

Description
I have added equations 8 to 13. However I am unsure how to write the sum term from equation 1.
Fixes # (issue)
Type of change

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist

[ ] Make sure you've run the pre-commit checks: $ pre-commit run -a
[ ] All tests pass: $ poetry run pytest

Further checks

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

Okay so to plot values generated by functions (e.g. lambda) using the integration output you need to do the following:
output = integrate()
plot_time = output.t
# Find a and R values for species 1 for the whole simulation
species_1_a = output.y[4]
species_1_R = output.y[2]
# Use the a and R values to calculate lambda from the function you already defined
species_1_lambda = calculate_lam(a=species_1_a, R=species_1_R)
# Then plot lambda against time
plt.plot(plot_time, species_1_lambda)

To loop over the j function you would do something like this:
output = integrate()
plot_time = output.t
species_1_R = output.y[2]
metabolite_1 = output.y[6]
metabolite_2 = output.y[7]
# Create empty vector to store j value for each time point in plot_time
species_1_j = = np.zeros(len(plot_time))
for ind, _ in enumerate(plot_time):
    species_1_j[ind] = calculate_j(R=species_1_R[ind], s= metabolite_1[ind], w= metabolite_2[ind], v = 1.0)
# Then plot


how edit text of inline message reply markup ؟

how edit text of inline message reply markup ؟
e.CallbackQuery.InlineMessageId is null!!! allways

have you seen this in the docs

Please note, that it is currently only possible to edit messages without reply_markup or with inline keyboards.

also mentioned in #176

thanks


SSL problems

Essentially, all resources (images, stylesheets, redirects, etc.) need to be updated to support both http and https (ssl) if possible. SSL is becoming more and more common and the lack of support in this project is annoying and a risk, especially for modpack developers who may wish to ensure they cannot be subjected to a MitM attack.

Can't reproduce, mine works on SSL just fine (now if only Java supported the Lets Encrypt CA)

@NEXUS2345 this was fixed in #562. Consider updating to master.

Attempting it now after pulling from master. Will close ticket once I have confirmed SSL is working correctly.

I can confirm that SSL is working, however all of the stylesheets are being served over HTTP still, meaning Chrome and many other browsers will block them.

Javascript files are also not being served via HTTPS

That's not the case on my install... Can you link to your install so we can help debug?

https://solder.preludegaming.net/dashboard

Do you mind linking your own install as well? @skwerlman

https://solder.tetrarch.co
it looks like something is wrong with how you're redirecting to ssl. login.css is not being 301'd

It looks like you are using Cloudflare, have you enabled strict SSL on that subdomain?

Do you want a copy of the nginx config?

no; cf has issues with my letsencrypt cert. However, ssl does still work with cf disabled.

https://gist.github.com/NEXUS2345/2d37869119e76be36efa26e6923da181

Try using a seperate block for ssl redirection:
server {
    listen 80;
    server_name solder.preludegaming.net;
    return 301 https://$host$request_uri;
}

That is leading to a problem of too many redirects on dashboard... Might try reinstalling Solder altogether.

did you remove the listen 80; from the original block?

Yes but it is still redirecting.

What does your config look like now? Do you have any sort of redirect in the original block?

https://gist.github.com/NEXUS2345/a21afdb8b1c8a109ac52cd3ea87a46fc

Ok, I did the reinstall, and it made no difference. Pulled directly from master, and still having the issue.

Well, i'm at a loss, since I don't see anything in your config that would cause a redirect loop like that...
Here is my nginx conf if it proves useful. Sorry I can't be of more help...

I noticed that you are using PHP 5. We are running PHP 7, could this be the issue?

Nevermind, I fixed it, apologies for wasting your time, I had a misconfigured page rule.


Not working?

I have absolutely loved working with this library for what I'm researching so thank you.
That stated, today while using 0.1.9, I'm getting the exception "raise YouTubeTranscriptApi.CouldNotRetrieveTranscript(video_id)" for every video I've tried including videos that were collected as recently as yesterday.
I did already check to see if a new version had come out (which I also verified here), rebooted server in full to try and eliminate anything on my side that might be causing this.
Is anyone else also having this issue currently?

Also confirmed through the YouTube caption API that captions (both creator uploaded and auto-transcriptions) exist on multiple videos yet this library can't grab them. Run through both CLI and a Django app. Hoping this is something that is temporary but some confirmation from others involved with this would be nice.

Adding to the mystery, local dev machine now producing results. Production remains producing errors. Same video.

Appears to have been an issue with the originating server making the request. Closing.


Feature: Add support for RAW/DNG images and flags

It is possible to shoot RAW/DNG images on iOS and Android for a long time.
Could you add support for this feature as well?
Desired behavior:

Flag in AssetEntity.
Method to get RAW data if it differs from AssetEntity originBytes method.

Flag in AssetEntity.

I didn't see any necessity with a RAW field.

Method to get RAW data if it differs from AssetEntity originBytes method

Have you encountered any issues when obtaining the raw data of RAW images when using originBytes?

Closing as the issue is missing requirements and no response.


Mocked SRS with additional G2 points for Zeromorph

The degree check in Zeromorph requires additional G2 points. We need to mock an SRS with these points. See the original issue for more detail.

Duplicate


can I use the alertmanager templates?

hello Thanks for prometheus_bot.
can I use the alertmanager templates for the telegram templates?
thank you~

I use the production_example.tmpl but
Alert: {{ index $val.Annotations "name" }}
didn't show anything
how can I fix it?
out put
`~~~ Alerting ~~~
alertname = service_down
Status: FIRING 🔥
Active Alert List:
Alert:  <--- didn't show anything
Current value:Severity: critical
Active from: 11/04/2021 16:30:20
description: The service blackbox_http instance xxx is Down
summary: instance xxx can't work!!!
`

[ ffff]

fffff

You can try to ask @AndreaGreco about that template. Generally you can always sniff traffic between the bot and alert manager and add also log messages in go code.

You can try to ask @AndreaGreco about that template. Generally you can always sniff traffic between the bot and alert manager and add also log messages in go code.

ok! thank you

You can try to ask @AndreaGreco about that template. Generally you can always sniff traffic between the bot and alert manager and add also log messages in go code.

ok! thank you

Hi, pass too many years i don't remember for.
Read source code in main.go, if found solution rigth.
if problem persist write here again and i will try help you by reading source


Upgrade R to version 4.0.3

Updating R to major version 4. Worked with the  swcarpentry/r-novice-gapminder lesson generation.
Closes carpentries/lesson-docker#11

Just checked it against the r-intro-gapminder lesson and it works well!

Hey @zkamvar, very delayed on this but would you be happy to add the hacktoberfest-accepted tag to this PR? It's a pretty small change so no worries if you think it isn't enough for my hilarious last ditch attempt at hacktoberfest

Hey @zkamvar, very delayed on this but would you be happy to add the hacktoberfest-accepted tag to this PR? It's a pretty small change so no worries if you think it isn't enough for my hilarious last ditch attempt at hacktoberfest

Done. I would have labelled it much earlier if I knew. Hopefully this helps out.

Thanks! Ah no worries, I had another one lined up but I don't think it got accepted in time. Will see if it works retrospectively!


Removed ResourceId as it is not  a Host Entity Field.

Fixes #
Proposed Changes

the YAML validation is failing, please check it.


Merge code for Stack modules

Changes related to stack modules are made.

Can one of the admins verify this patch?

@invincibleJai can you make sure you rebase this to remove the merge commits?

Can you remove the cico file changes please - you just changed the permissions on them for some reason.

This has not been properly merged against my changes in master - we can work through it tomorrow.

This merge request has become obsolete and new one is #109


Update dsp.average for complex signals

Raise value error for complex Signals for modes: 'log_magnitude_zerophase', 'magnitude_zerophase', 'magnitude_phase', 'power'

What is the idea behind not having these modes for complex signals - wouldn't the operations be possible in general?