[BUG] Azure Identity credentials don't obey proxy when acquiring login tokens

Library name and version
Azure.Security.KeyVault.Secrets 4.6.0
Describe the bug
Our hosts require HTTPS proxy for all egress.  We can configure the SecretClientOptions.Transport with a suitable proxy (see attached sample program), and requests to the Azure KeyVault obey this proxy.  However, requests from within SecretClient to obtain login tokens do not obey the proxy, and thus they fail to complete.  If a proxy is set via SecretClientOptions.Transport, it should be used for all requests made by SecretClient or any libs that it uses.
Expected behavior
A proxy set viat SecretClientOptions should be used to all requests made by, or on behalf of, SecretClient.
Actual behavior
Requests made by SecretClient to acquire login tokens do not use the configured proxy.
The only way for login tokens to be acquired successfully is to change the HttpClient.DefaultProxy, which globally affects all HttpClient instances - obviously not a suitable solution.
Reproduction Steps
Use this project to reproduce the issue:
https://github.com/paulmedynski/azure-key-vault-proxy
Run with --help for options related to Azure Key Vault and whether or not a proxy is used.
All egress allowed, no proxy specified:
$ dotnet run -- -u https://<keyvault>/ -t <tenantId> -a <appId> -c <cert.pem> -k my-secret-name

11:54:30.338 info: KeyVaultProxy[0] Creating SecretClient for vault URL=https://<keyvault>/ tenantId=<tenantId> appId=<appId>...
11:54:30.351 info: KeyVaultProxy[0] Using auth type=cert (cert.pem)
11:54:30.353 info: KeyVaultProxy[0] Getting secret for key=my-secret-name...
11:54:31.606 info: KeyVaultProxy[0] Secret for key=my-secret-name is: id=https://<keyvault>/secrets/my-secret-name/945c0e7946314f90bb3d5e6f74e1d120 name=my-secret-name value=shhh_secret

No egress allowed, no proxy specified:
Configure an HTTPS proxy on localhost:8888, for example tinyproxy.
Configure iptables to reject all outbound traffic except from the proxy:
# iptables -F OUTPUT
# iptables -A OUTPUT -j ACCEPT -m owner --uid-owner tinyproxy
# iptables -A OUTPUT -j ACCEPT -o lo
# iptables -A OUTPUT -j REJECT

$ dotnet run -- -u https://<keyvault>/ -t <tenantId> -a <appId> -c <cert.pem> -k my-secret-name

14:34:13.245 info: KeyVaultProxy[0] Creating SecretClient for vault URL=https://<keyvault>/ tenantId=<tenantId> appId=<appId>...
14:34:13.258 info: KeyVaultProxy[0] Using auth type=cert (cert.pem)
14:34:13.260 info: KeyVaultProxy[0] Getting secret for key=my-secret-name...
14:34:19.074 fail: KeyVaultProxy[0] Failed to fetch secret for key=my-secret-name: Retry failed after 4 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (Connection refused (<keyvault>:443)) (Connection refused (<keyvault>:443)) (Connection refused (<keyvault>:443)) (Connection refused (<keyvault>:443))

Note that the initial connection to the Key Vault is refused, as expected.
No egress allowed, SecretClient proxy specified:
$ dotnet run -- -u https://<keyvault>/ -t <tenantId> -a <appId> -c <cert.pem> -k my-secret-name -p localhost:8888

14:36:14.837 info: KeyVaultProxy[0] Creating SecretClient for vault URL=https://<keyvault>/ tenantId=<tenantId> appId=<appId>...
14:36:14.848 info: KeyVaultProxy[0] Using auth type=cert (cert.pem)
14:36:14.848 info: KeyVaultProxy[0] Using proxy localhost:8888
14:36:14.850 info: KeyVaultProxy[0] Getting secret for key=my-secret-name...
14:36:21.633 fail: KeyVaultProxy[0] Failed to fetch secret for key=my-secret-name: ClientCertificateCredential authentication failed: Retry failed after 4 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (Network is unreachable (login.microsoftonline.com:443)) (Network is unreachable (login.microsoftonline.com:443)) (Network is unreachable (login.microsoftonline.com:443)) (Network is unreachable (login.microsoftonline.com:443)) See the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/clientcertificatecredential/troubleshoot

Now we see that the login token requests are failing, because they aren't using the proxy!  This can be corroborated by inspecting the proxy logs and noting that only the initial Key Vault was tunneled through the proxy.  The login token requests did not pass through the proxy.
No egress allowed, HttpClient.DefaultProxy specified:
$ dotnet run -- -u https://<keyvault>/ -t <tenantId> -a <appId> -c <cert.pem> -k my-secret-name -p localhost:8888 --global-proxy

14:37:50.710 info: KeyVaultProxy[0] Creating SecretClient for vault URL=https://<keyvault>/ tenantId=<tenantId> appId=<appId>...
14:37:50.720 info: KeyVaultProxy[0] Using auth type=cert (cert.pem)
14:37:50.721 info: KeyVaultProxy[0] Using proxy localhost:8888  (global)
14:37:50.722 info: KeyVaultProxy[0] Getting secret for key=my-secret-name...
14:37:52.433 info: KeyVaultProxy[0] Secret for key=my-secret-name is: id=https://<keyvault>/secrets/my-secret-name/945c0e7946314f90bb3d5e6f74e1d120 name=my-secret-name value=shhh_secret

Everything works when the global HttpClient.DefaultProxy is specified.  This isn't a suitable solution though, since other HTTP connections within the app may rely on a default proxy specified by environment variables for example.
Environment
$ dotnet --info
.NET SDK:
Version:           8.0.202
Commit:            25674bb2f4
Workload version:  8.0.200-manifests.4e94be9c
Runtime Environment:
OS Name:     debian
OS Version:  12
OS Platform: Linux
RID:         linux-x64
Base Path:   /usr/share/dotnet/sdk/8.0.202/
.NET workloads installed:
There are no installed workloads to display.
Host:
Version:      8.0.3
Architecture: x64
Commit:       9f4b1f5d66

@christothes:  Would you please offer your thoughts?

Hi @paulmedynski-microsoft
Could you try passing options to your credential with the Transport set the same way as in your SecretClient?
Some additional context:
TokenCredential implementations in Azure.Identity are essentially their own clients and the TokenCredentialOptions implementation accepted by each credential uses its own transport and pipeline. Since TokenCredentialOptions inherits from ClientOptions, the same transport options are settable there
https://github.com/Azure/azure-sdk-for-net/blob/5c7c95433e4cd3374f80294443b11dadf1ddb8f6/sdk/identity/Azure.Identity/src/Credentials/TokenCredentialOptions.cs#L13


Code completion after buffer or temp-table keyword

When using the buffer keyword, the code completion suggestions like fields before the buffer names. It would be nice if the buffer name was listed first, then the fields in this situation.
For example:
define temp-table ttFoo no-undo
    field FooId as integer
    field FooName as character
    field BarId as integer
    field BazId as integer.

define buffer bttFoo for ttFoo.

define variable vBufferHandle as handle no-undo.

vBufferHandle = buffer btt

After btt, the suggestions are the fields of bttFoo (in order), then bttFoo at the end.

Good point, that will be improved.

In widName rule, wrap all identifier references with bufferIdentifier, datasetIdentifier, … so that this can be trapped by C3 as a rule stop.


JSON schema should use anyOf instead of oneOf

I'd implemented JSON schema to use oneOf property about union type following NestJS guide.
However, TypeBox author (@sinclairzx81) announced me that it is not right and must be changed to anyOf.
Therefore, do change it.

Considering #294 feature, oneOf should be kept.


this allows for sending exception data if there's a compile error

Previously, if there was a compile time error the handler would try to emit run_status.all_resources.length which wasn't yet available, so you'd get an "undefined method 'length'" error and nothing would be emitted to datadog.
Now it has better error checking and additionally sends run_status.formatted_exception and run_status.backtrace in the event of a compile error - which allows you to actually see in datadog console what the compile issue was.

No update on this PR. Closing.


Fix Willpower Down Icon

Loving the sheet, just pulling to fix a mismatched icon.

Oh you're the best!


Extend CI to test example configs are valid

Hey @CillianFn and @pranay101, this issue was inspired by #52 and #47. If either of you would like to pick this up, that would be a great help!
To summarize: we should start treating our configs like code and include them in our automated checks. For this issue to be fixed, we should add to our CI build to test that all the example configs parse correctly (check for correct syntax). For now, I think it's sufficient to run each config with the -d, --dry-run flag. Later, we can check that the semantics of the configs are correct.

hey @alxmrs, it'll be great working on this issue. But this issue seems too technical to me right now can you please break it down a bit.

Given that #56 is merged, we can call this issue fixed.


Documentation and Websites Major Issues!

Godot version: 3.x and 2.x
OS/device including version: Not relevant for this issue.
Issue description:  May I make a couple of suggestions that I feel (and I am sure many others that read this will too) would propel Godot to the stratosphere and most definitely put it on par or above with GameMaker Studio, Coco2d, Unity, Unreal, Construct, and many other professional and commercial game engines. I am sure many people do not currently feel like it is because of the lack of these 2 suggestions below:
#1. Hold off on all new features, bug fixes, and everything else until the ENTIRE documentation of Godot 3 is finished with complete descriptions, explanations, and samples. I can't count how many times I have had to find videos by different users just to do simple things that could have been MUCH easier explained in the documentation IF the documentation had been completely finished. Lots of times I can't even find videos for certain things mentioned in the documentation. This lacking of a GULLY FINISHED Godot documentation only hurts Godot in the present and the future.
#2. The Godot website, forums, and market place all are lacking in continuity of design. They look nothing alike at all. Even though they have links for each on the Community page, it does give the impression that these are not official Godot sites and not really part of Godot's website. I am sure many of people when they clicked the links and it went to those sites, they just pretty much just gave up on their problem and/or left Godot all together.
Now you may not think these are MAJOR ISSUES, but seriously, stop and really, really think about what I am saying. Look at it from a complete beginner's point of view and/or someone who has used Godot not very much at all. I am sure you will then see just how important these 2 suggestions really are.
Please?
Thank You!
Steps to reproduce: Just look at the documentation and those web sites.
Minimal reproduction project:  Just look at the documentation and those web sites.

Obviously they are extremely important.
This is honestly a good problem to have. ;)
to sum up: godot improoves in such a fast pace so that docs and video tuts struggle to keep up.
Of course that is a huge issue especially for beginners. But it is also the only way godot could have become the engine it is nowadays.
Stopp to implement features would have hurt godot in the past in also would hurt it now. It's just a strange proposal for an open source project to ask stop adding new features if ppl want to work on them.
This is just the way it is with open source. There are a ton of amazing ppl who write docs. And if there are more ppl needed, there needs to be an incentive.
It would be amazing if the Godot Patreon for example would have even more supporters so that ppl can get paid for documenting. (I'm generally advocating a open source culture where supporting with money is more common. almost like tips in a restaurant)
I still totally agree that any work on documentation is worth A LOT.
So thank you for making bringing up the topic.
I hardly disagree with asking ppl to stop adding features, AND BUG FIXES.
Fist this is totally not how open source works. If I want to propose an idea/ feature I should be allowed to. If everybody hates it, fine, but everyone can work on whatever he wants.
But your post already inspired me for example to maybe put some hours in it. It's just impossible to actually force it.
Second the added features is what makes godot even be competitive. This is exactly how it should be.

Hold off on all new features, bug fixes, and everything else until the ENTIRE documentation of Godot 3 is finished with complete descriptions, explanations, and samples

I wouldn't prefer having a buggier, less capable engine in favor for complete documentation. While I agree that the docs is important, it should not be in a way of engine development. Open source softwares get features fast and it is difficult to keep the docs up to date. Also, users already have various ways of asking for help from the community. Discord, IRC, Reddit, Q&A, Facebook Group etc.
I was a beginner once too.  It should not be too hard to follow the official tutorial. At least that's the point of having a tutorial. (If some parts are difficult to understand, please specified it so it could be improved. Preferably in https://github.com/godotengine/godot-docs/. Saying the whole docs needs improvement is not that helpful.)

A lot of users really like the documentation, so instead of complaining about something more general, I suggest you just open an issue here:
https://github.com/godotengine/godot-docs/issues
complaining about what you had difficulty with

To think that if we stop accepting PRs here in favor of PRs to documentation would improve the docs is a fallacy. If we tell everyone to only work on the docs, people will simply go away. We're not entitled to tell what people should do in their free time. Most contributors that could fix a bug don't feel confident to write new documentation, especially those who are not native English speakers.
When I started using Godot, before 2.0 was out, the documentation was awful. Most of the API classes and functions were undocumented  It used the GitHub wiki, so we couldn't even search for stuff, nor could the community edit it to improve it. It has come a long way since then. Now most of the API has documentation, especially the more high-level stuff (which is mostly used). And the tutorials are much more useful and cover more ground.
There's no reason to believe that the documentation won't get better if we don't focus 100% of the time on it. There are many regular contributors to the docs, including people doing revision and organization. It will only get better.
Eventually Godot will settle and won't have more major features to add, then it'll be a great time to fill in the blanks. Otherwise even if we fill the whole doc now it will have to be mostly thrown away in the next version. Godot 3.0 was a huge change and 3.1 will be quite big as well, especially in terms of interface (new Inspector, new animation tools), so focusing on 3.0 docs, means rewriting some chunks for 3.1.
I'm not saying we should ignore the documentation, only that it can keep growing on its own pace, no need to drop everything else in favor of it.

About the second point, we could make a new face to the asset library and the QA website, but it's not a dire situation. You can open issues on https://github.com/godotengine/godot-website and https://github.com/godotengine/godot-asset-library about this.

Just to note, most FOSS projects have their documentation done by the community, not the developers (the developer's job is to accept proposed changes from users).
I especially wouldn't like to see bugfixes halted until the docs. are complete (look at all of the Unity and Unreal forum threads talking about how buggy those engines are, Godot can make headway just by being an engine where the vast majority of things just work).

A lot of users really like the documentation (...)

like me. i love godot docs and glancing through it often.
On the other hand, its true that most of people like to code fast, skiping comments and explanations on how something work or documenting things because we keep everything in our minds. This way we code faster and quickly move forward to see how it works, but then most of us should be experienced to know that later it will end up very deadly.
Undocumented code without comments after enought time, turns unmaintanable even for its own author. Additionaly, it virtually does not exists since almost no one know that its there except fiew who made it or seen it merged. Its a waste to not share with world news about new shiny things that lurks within engine.
It could be good if feature author at least could add his feature to table of contents in docs, and write even if fiew words and many TODO examples should be here, TODO whatever here.
To give community sign that something like that even exsists.
If theres a road leading somewhere, some people might find it interesting to explore it and share what they found by completing documentation with more details / examples ect.
Just leave a small TODO, TODO, TODO in docs for people to know that it exists, else it sink in oblivion.

Maybe it is just me, I don't know, but I get the feeling that everyone here thinks I am putting Godot down and that is just farther from the truth. I love Godot, I really do! I am not really complaining here, I am just making suggestions that I truly believe will improve Godot overall.
I can truly understand you all not wanting to hold off on new features and bug fixes and the like, these are great things that make any engine good and worthwhile.  But just for a second see this, you can have all the new features and bug fixes you want, but if there is no really good documentation that fully explains what they are, how to use them, and demonstrates each , how useful are those new features if you can't figure out how to use them, seriously!?
I understand that Godot is rapidly changing, what was yesterday is not the same today. But if you don't have good documentation on what is today, then how are you suppose to use it tomorrow?
To just say that is how open source works is just completely blind. I have used and still continue to use a lot (and I do mean a lot) of open sourced software, and while there may be some with so-so or decent or bad or even no documentation, this is not the normal. I would venture to say MOST open source software HAS VERY GOOD good documentation, with great explanations and great examples.
Yes I do understand,  you don't want to hold off on new features and bug fixes, so don't. As you said, people will work on what they want, when they want, and how they want. But that doesn't mean you have to accept their new features and bug fixes without full, proper documentation for each NEW feature and bug fix, BEFORE it is added to Godot! This way the documentation will MOST DEFINITELY improve as well as Godot its self.
Once again I just want to say, I love Godot and I am not putting it down or complaining about it, I am only suggesting how it can be made much, much, much better!  For Everyone!!!

I have to agree that the documentation does need some work, but it shouldn't be at the expense of 3.1 having a much longer development time. I've seen many, many things in the docs that don't have a description, but more often than not they're somewhat self-explanatory, or are things I'm probably not going to need. And if someone does need an explanation on it, that's what things like the project's Discord or even the Q&A website are for.

I understand that Godot is rapidly changing, what was yesterday is not the same today. But if you don't have good documentation on what is today, then how are you suppose to use it tomorrow?

I don't agree with this idea that the documentation we have now is bad, though. Of course, it could really use some improvements (several pages in the docs haven't really been maintained), but I don't think it's at that unusable level yet.

Yes I do understand, you don't want to hold off on new features and bug fixes, so don't. As you said, people will work on what they want, when they want, and how they want. But that doesn't mean you have to accept their new features and bug fixes without full, proper documentation for each NEW feature and bug fix, BEFORE it is added to Godot! This way the documentation will MOST DEFINITELY improve as well as Godot its self.

Disagree with this idea. I think that would push people away from wanting to add new features, as odd as that might sound. Not everyone really considers themselves capable of writing some good documentation, myself included (I'd of contributed loads to the documentation had I not felt I wasn't capable of writing well), so I feel that requiring full documentation of added features will just turn people off from contributing. While it certainly isn't a bad idea to ask for some basic documentation, it's not something I feel we should expect from every PR, whether new feature or otherwise.
I imagine that when 3.1 is about to hit, though, maybe there'll be some more contributions to the docs? Or perhaps there could be more docs sprints, since those got at least a few pages updated every time one happened.

Also, I have a suggestion for you. If the documentation is so lacking to you, perhaps you could help improve it? I don't mean to sound rude, but it feels like the time spent complaining about the docs being lacking, could have been spent improving the docs.

Sorry. You still haven't show me what part of the docs that's confusing to you.
I will tell you what exactly is wrong with your proposal:

May I make a couple of suggestions that I feel (and I am sure many others that read this will too) would propel Godot to the stratosphere and most definitely put it on par or above with [...]

This is just what you believe. These 2 suggestions are simply not enough to make Godot "on par or above" other engines. I could make an "engine" with very well described int main(int argc, char **argv) that you can understand that the first glance, but if that's the only function I have, is it on par with Unity?

Hold off on all new features, bug fixes, and everything else until the ENTIRE documentation of Godot 3 is finished

Like 100% of it? Imagine it happened. We would have 1,000+ PR on backlog. Merging it would be nightmare and rendering most of the docs useless/inaccurate. That would have meant the docs is not "finished." We would have to stop everything to finish the docs again. etc. Expect Godot 3.1 to come in 2025 at best.

I can't count how many times I have had to find videos by different users just to do simple things that could have been MUCH easier explained in the documentation IF the documentation had been completely finished. Lots of times I can't even find videos for certain things mentioned in the documentation.

You have the community at your expense. Use it to your advantage.
When I started, there was virtually NO videos on Godot Engine, let alone what I specifically want to learn. The community wasn't this big either. What did I do? I re-read the tutorial several times until I know the basics of it. (most of what you need to know is in the tutorial. you usually don't use what's not mentioned often.) I did "Trial and error" in the editor. Godot makes this very easy with scene system. Try everything you want to know.
I understand we learn best from different methods but we're sure our resources work for the majority of people. You can't just disregard them and say that we need to do something "better." At least tell us the exact part you find confusing.
(I'll skip the part about website. The design can be improved, but it serves purposes for now and is not a priority.)

you can have all the new features and bug fixes you want, but if there is no really good documentation that fully explains what they are, how to use them, and demonstrates each , how useful are those new features if you can't figure out how to use them, seriously!?

This is where I'd ask the community to help, search the blog post on the new feature, and/or look up the relevant part in the source code. It's not impossible.

But if you don't have good documentation on what is today, then how are you suppose to use it tomorrow?

In my opinion, what we have is pretty good. Because you haven't tell me what's wrong with it, I can't see it.

I would venture to say MOST open source software HAS VERY GOOD good documentation, with great explanations and great examples.

Link me to them please. It would be nice to know how they manage to do it. But to be able to do the same, they must have similar constraints. (have to implement large amount of features in short amount of time. etc.)

Yes I do understand, you don't want to hold off on new features and bug fixes, so don't. As you said, people will work on what they want, when they want, and how they want.

then why did you say...

But that doesn't mean you have to accept their new features

... Isn't this the same as "holding off on new features" for ones without docs update?

and bug fixes without full, proper documentation for each NEW feature and bug fix, BEFORE it is added to Godot! This way the documentation will MOST DEFINITELY improve as well as Godot its self.

I hope we agree that fixing the engine bugs on user end is harder than our end. That's why we have to merge bugfix so that users affected by it don't have to fix it themselves, while something like "not understanding how things work in the engine" can be solved easily by resorting to the community and/or source code.
We're currently holding off features that aren't part of the roadmap for some time. It has several cons.

By the time it's ready to be reviewed, it's outdated.
The contributor stopped working on it. (It's abandoned.)
It can leads to misunderstanding between the maintainers and the contributor. Something like "I wouldn't have worked on it if you told me first that it wouldn't get merged. Why didn't you tell me?"

Etc. That's why we try to discuss and merge it before it gets too old. Also, what we merge is what the community wants and we agree that it brings a smoother workflow. I'm not certain that stopping the merge would be justified.
We already enforce adding docs entry for new methods from contributors. Most of them gladly do it, but wouldn't you agree that "we're not gonna merge this because you don't provide docs" too aggressive? Several useful functions might not end up in the engine if we're too strict with the policy.
Also I'd respect reduz as he's one of the project founders. We're basically using what he made. I think it's not cool to have him describe everything he did just so we can understand it.

I am only suggesting how it can be made much, much, much better! For Everyone!!!

Not for me at least. It's already good enough. This assumption doesn't make it better. Now I doubt that the whole proposal is based on your assumptions and it's not going to work.

This is how it is. You can make suggestions. You can tell us what's wrong and we'll discuss on how to solve it. But NOT tell us to stop everything we're doing and do something else instead. I do what I do and feel like doing. It's not worth it and it's not going to happen.
I know that you love Godot. Most of us do. Loving is not enough. Also, doing what you're doing right now is not enough either. If you're not ready to contribute, at least tell us what part exactly that has issues. Maybe if you list methods with uncomplete docs, I could explain them better. (if I'm not too busy)
In conclusion:

I don't know what to do with this issue. It's too vague.
Stopping everything won't magically create a better docs and make Godot better. At least in the near future.
In this situation, the issue is too vague to justified "stopping everything." It is an illogical solution.

TLDR: tell me what exactly wrong with the docs/what you want to do but can't because the docs is incomplete.


Fix unit tests broken in v4

Unit tests in v4 are broken since merging #442 as it exports a function using self which doesn't exist in node contexts.

Gah, can't believe I didn't notice the failing unit tests. This could also impact anyone running the code in node SSR, so we should fix ASAP.
Rather than using globalThis (which will error in some older browsers), I think it would be better to just move the const rIC = self.requestIdleCallback || self.setTimeout; line within the whenIdle() function. This is what we do for cases that reference document in other parts of the code.


[proposal] Bower support

Hi,
Nice picker. Please add support for Bower.
Thanks

Would be nice, yes.

Still would be nice.

Hi @spajz, @dobromir-hristov, @infomiho,
Ok, done! ;o)
bower install tinyColorPicker


system.copySystemConfiguration = true;     is broken

when I have it in my config, I get:
building Nix...
building the system configuration...
these derivations will be built:
/nix/store/mjbzg37h0bbmx3q1frvpi8zs9yqdd0cm-nixos-15.06.git.5b27d9bM.drv
building path(s) ‘/nix/store/nszq7y1qshvlys6nsb8z2cf0kmpkwdid-nixos-15.06.git.5b27d9bM’
cp: cannot stat '/etc/nixos/configuration.nix': No such file or directory
builder for ‘/nix/store/mjbzg37h0bbmx3q1frvpi8zs9yqdd0cm-nixos-15.06.git.5b27d9bM.drv’ failed with exit code 1
error: build of ‘/nix/store/mjbzg37h0bbmx3q1frvpi8zs9yqdd0cm-nixos-15.06.git.5b27d9bM.drv’ failed
same happens on 14.12.

Is your configuration.nix somewhere odd? Do you have chroot builds turned on?

@copumpkin
Yes, I have chroot builds turned on:
https://github.com/magnetophon/nixosConfig/blob/master/common.nix#L20

I think chroot builds will break it, if I understand it correctly. That's probably a problem :smile:

Tested again on e1af50c, same problem.

@magnetophon Current status?

Not fixed, still the same problem. The file needs to be accessed during evaluation time already, not so late as build-time.

@vcunat: thanks, fixed!

@vcunat: thanks, fixed!


Use env vars in Smee instead of CLI flags:

Description

This allows an unset value for an env variable to invoke Smee's automatic IP detection to trigger. With CLI flags this automatic IP detection doesnt work.
Why is this needed

Fixes: #
How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[ ] added unit or e2e tests
[ ] provided instructions on how to upgrade

Looks good!


Google OIDC cannot sign in.

Describe the bug
When signing in with Google, it directs to the error page with the message: Failed to perform post authentication steps. Error message: com.linkedin.data.template.RequiredFieldNotPresentException: Field "value" is required but it is not present
To Reproduce
Steps to reproduce the behavior:

Try to sign in with Google, then failed.

Expected behavior
It used to direct to the datahub main page after signing in.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: macOS 12.1
Browser: safari
Version: 15.2

Additional context
The datahub was deployed by helm on GKE and integrated with confluent Kafka, google cloud SQL.
We found the issue with charts version: 0.2.29 and datahub version: v0.8.16.
And later upgraded to 0.2.45 and v0.8.26 respectively, but the issue is still there.
Also the error log were collected as attachs
datahub-gms.error.log
datahub-frontend.error.log

Looking into the error log from datahub-gms, I found an exception, org.apache.kafka.common.errors.SerializationException: Error registering Avro schema:, then I tried to refresh the Kafka client configuration with a new one.
It results fixed the issue, the issue should belong to our side and I am going to close it.
Many thanks.


ApiLoggerInterface Issue

Hello,
Laravel version: "laravel/framework": "^6.18.35"
I'm using the below 2 packages at the same time:
"awt/apilogger": "dev-master"
"tightenco/ziggy": "^1.0"

I've added @routes to some blade files which will be used to get all routes in the javascript files. Now I wanted to add some other packages and after installing/removing other packages I'm getting the error in pages where I've added @routes
I tried removing, installing, and updating the package. Also, checked some solutions and tried this one (Stackoverflow).
The error screenshot is attached. Can I get the solution for the same?

This doesn't look related to Ziggy. You said you tried uninstalling Ziggy, do you still see this error without @routes and without Ziggy installed?

No, After removing @routes the error is not showing.
But, I've added the same issue to the apilogger. And I'm sure that the error comes between these 2 packages only.

Can you share a complete stack trace or any other debugging info? That screenshot looks like there's an error in your homenew.blade.php view, can you share that? With the information I have here this still doesn't seem related to Ziggy.

There is nothing different debugging for this. If I removed the Ziggy, APILogger package it'll work fine. But with these two packages, I'm not able to add any new packages.
It's only one type of the defined process before jquery and another js file that requires to get the routes, nothing else.

@kuldeepBacancy I'd like to try to help debug this but I need more information. Can you please share a complete stack trace? Your original screenshot says the error is on line 19 of ApiLoggerInterface—what is on that line?
It looks like that package might be interacting with your routes in some weird way, are there any routes in your application where if you comment out the route completely, this error disappears and the page loads? If so can you share those route definitions?
It would be great if you could share a reproduction repo for this issue, or a link to your app if it's open source.

The ApiLoggerInterface uses union types, which were added in PHP 8.0. Upgrading your PHP version should resolve this issue.


Add activemq config for fcrepo

Ticket
https://github.com/Islandora-CLAW/CLAW/issues/711
Issue
Fcrepo wasn't coming up because of two activemq, embedded and external. Same fix as for the vagrant box we need to configure fedora to not start activemq broker.
Testcase
Run playbook and make sure fcrepo comes up.

@whikloj @dannylamb @ajs6f
ran into this while testing the crayfish pull. if anyone has time to review and merge would be most appreciated.

I'll wait a bit through today in case anyone else has comments, then I'll merge this. It's pretty much a no-brainer.

@whikloj @ajs6f updated the path for the config file.

I know @dannylamb is out this week, so can I assume that everyone who wants to has chimed in on this PR?


FPSMeter is causing main thread activity

The FPS Meter widget is updated via rAF. While not a problem in itself, this is causing issues for WAAPI/CSS animations in some browsers (see https://github.com/slaylines/canvas-engines-comparison/issues/69 for these tests).
In Blink (Chromium), the presence of a rAF will cause the animations – which already happened on the compositor – to also happen on the main thread because you could query for style values inside the rAF. Because of this, WAAPI/CSS animations perform worse when the FPS Meter is present.
See https://bramus.github.io/canvas-engines-comparison/dom-waapi.html for an implementation that allows disabling the FPS Meter widget.

For comparison, here’s a performance profile measured in Safari to show the difference.

With FPS Meter
Without FPS Meter

(Note that the 9fps in the one screenshot isn’t representative. It’s the ongoing profiling that is slowing things down. When not profiling, the reported number is around 49fps on my machine)


Get query raw column value as a int

My query is returning a string for the created_at and updated_at columns (they are timestampz that I'm converting to millisecond precision unix timestamps) but I want it to be returned as an int/number. I need it as an integer because of my sync mechanism dictated by my local DB package.
The timestamps were created like this: timestamps(true, true)
Query code
 const columns = [
          'id',
          'description',
          raw('round(extract(epoch from created_at) * 1000)').as('created_at'),
          raw('round(extract(epoch from updated_at) * 1000)').as('updated_at')
        ];

const created = await Table.query().select(columns)
console.log(created);

Console.log result
[
  Table {
    id: '1',
    description: 'Banana',
    created_at: '1642701405550',    //not sure why this is a string
    updated_at: '1642701405550'    //not sure why this is a string
  },
  ...
]

Desired result
[
  Table {
    id: '1',
    description: 'Banana',
    created_at:<PHONE_NUMBER>550,
    updated_at:<PHONE_NUMBER>550
  },
  ...
]

Things I tried

Casting the raw column query like this: raw('CAST(round(extract(epoch from created_at) * 1000) AS bigint)').as('created_at') but it didn't seem like it changed anything
Tested just removing the select but it just became a stringified DateTime
JSON.parse(created) didn't work either which makes sense since it's an Object hahah
Ran the raw sql in pgAdmin and the timestamps returned as numeric type

You need to configure the database client to return the given data type as a number. Most database clients return 64bit (or larger) integers as strings because they don't fit insider javascript numbers. Javascript numbers can only hold 53 bit integers and everything larger than that gets truncated.

Not sure if this is the best way but I ended up doing this in the database setup based off this comment https://github.com/knex/knex/issues/3071#issuecomment-509429039
    const parseTimestamp = (val) => {
        return val === null ? null : new Date(val).getTime();
    };
    types.setTypeParser(builtins.TIMESTAMPTZ, parseTimestamp);


bower.json name

The name in the bower.json file is listed as shepherd but one installs the package with bower install shepherd.js. Should they not be the same? it's certainly confusing with no bower install instructions documented.

Agreed, this was a cause for confusion!

Since v1.0.0, we've decided to prefix all Tether based projects with tether-. So you should now be able to install shepherd via tether-shepherd on npm and bower and the names in the *.json should be correct as well.

Thanks for the update :+1:


Log stack, app, stage and instanceId in AWS

Ronseal. This helps us investigate problems by filtering down the logs.

 [Giant] Log stack, app, stage & instanceId in AWS


Implement pipes

Implement pipes (| character). The output of each command in the pipeline is connected to the input of the next command via a pipe

https://github.com/tonnytg/42_minishell/blob/main/srcs/pipes/pipes.c


Process Management -- No way to list or stop running fuel-core nodes from Forc

There is no nice way to list, stop or start running fuel-core nodes nicely started by Forc.
As proposed earlier in my target, this can get quite annoying when you're doing a lot of stop/start like testing and doing basic node management.
I propose this be implemented sooner rather than later to manage this:
https://github.com/FuelLabs/sway/issues/423#issuecomment-979185301

Closing this for multiple reasons.

The proposed solution of using PID files is Linux-specific. Building out a generic solution that works across platforms is non-trivial.
Nodes don't need to be started and stopped by users for testing, ever. The SDK will handle launching and shutting down a node as needed.
The only time nodes need to be started and stopped during testing is by the protocol developers. Forc is meant for end-users, and should not have features that are only relevant to the protocol developers and not users.
Node management is infrastructure-related, and is not relevant to Sway and dapp development. A separate binary should be development if there is a concrete and actionable need to manage infrastructure.


[Bug]: page.evaluate error message lost for asynchronous react error

Bug expectation
A React component mounted in page.evaluate performs async work before failing. Puppeteer used to output the exact error message but since 20.2.0 started to give an empty error message. Reproduced in 20.3.0 20.4.0 and 20.0.5 but not in 20.1.0
This seems linked to https://github.com/puppeteer/puppeteer/pull/10114
While debugging a different case than the reproducer, exception details passed to getErrorDetails in util.ts has more call frames than exception stacktrace and getErrorDetails returns { message: '', name: 'Error' }:
{
  exceptionId: 1,
  text: 'Uncaught (in promise) Error: Missing translation key obs.introduction.challenges.titlee',
  lineNumber: 15,
  columnNumber: 51,
  scriptId: '4',
  stackTrace: {
    callFrames: [
      [
        {
          functionName: 'onMissingKey',
          scriptId: '4',
          url: 'pptr:evaluate;defineRenderObsSlides%20(file%3A%2F%2F%2Fapp%2Ftest%2Futils%2Fobs-env.js%3A2%3A16)',
          lineNumber: 14,
          columnNumber: 50
        },
        {
          functionName: 'useI18n',
          scriptId: '19',
          url: 'http://localhost:64000/components/i18n/i18n.js',
          lineNumber: 112,
          columnNumber: 26
        },
        {
          functionName: 'useI18n',
          scriptId: '19',
          url: 'http://localhost:64000/components/i18n/i18n.js',
          lineNumber: 9,
          columnNumber: 19
        },
        {
          functionName: 'ChallengesSlide',
          scriptId: '33',
          url: 'http://localhost:64000/components/obs/introduction/challenges.js',
          lineNumber: 89,
          columnNumber: 14
        },
        {
          functionName: 'renderWithHooks',
          scriptId: '7',
          url: 'http://localhost:64000/libs/react-dom.js',
          lineNumber: 16314,
          columnNumber: 19
        },
        {
          functionName: 'mountIndeterminateComponent',
          scriptId: '7',
          url: 'http://localhost:64000/libs/react-dom.js',
          lineNumber: 20083,
          columnNumber: 14
        },
        {
          functionName: 'beginWork',
          scriptId: '7',
          url: 'http://localhost:64000/libs/react-dom.js',
          lineNumber: 21596,
          columnNumber: 17
        },
        {
          functionName: 'beginWork$1',
          scriptId: '7',
          url: 'http://localhost:64000/libs/react-dom.js',
          lineNumber: 27435,
          columnNumber: 15
        },
        {
          functionName: 'performUnitOfWork',
          scriptId: '7',
          url: 'http://localhost:64000/libs/react-dom.js',
          lineNumber: 26569,
          columnNumber: 13
        },
        {
          functionName: 'workLoopSync',
          scriptId: '7',
          url: 'http://localhost:64000/libs/react-dom.js',
          lineNumber: 26475,
          columnNumber: 6
        },
        {
          functionName: 'renderRootSync',
          scriptId: '7',
          url: 'http://localhost:64000/libs/react-dom.js',
          lineNumber: 26443,
          columnNumber: 8
        },
        {
          functionName: 'performConcurrentWorkOnRoot',
          scriptId: '7',
          url: 'http://localhost:64000/libs/react-dom.js',
          lineNumber: 25747,
          columnNumber: 75
        },
        {
          functionName: 'workLoop',
          scriptId: '6',
          url: 'http://localhost:64000/libs/react.js',
          lineNumber: 2652,
          columnNumber: 35
        },
        {
          functionName: 'flushWork',
          scriptId: '6',
          url: 'http://localhost:64000/libs/react.js',
          lineNumber: 2625,
          columnNumber: 15
        },
        {
          functionName: 'performWorkUntilDeadline',
          scriptId: '6',
          url: 'http://localhost:64000/libs/react.js',
          lineNumber: 2919,
          columnNumber: 22
        }
    ]
  },
  exception: {
    type: 'object',
    subtype: 'error',
    className: 'Error',
    description: 'Error: Missing translation key obs.introduction.challenges.titlee\n' +
      '    at Object.onMissingKey (pptr:evaluate;defineRenderObsSlides%20(file%3A%2F%2F%2Fapp%2Ftest%2Futils%2Fobs-env.js%3A2%3A16):15:51)\n' +
      '    at Object.useI18n [as buildTranslate] (http://localhost:64000/components/i18n/i18n.js:113:27)\n' +
      '    at useI18n (http://localhost:64000/components/i18n/i18n.js:10:20)\n' +
      '    at ChallengesSlide (http://localhost:64000/components/obs/introduction/challenges.js:90:15)\n' +
      '    at renderWithHooks (http://localhost:64000/libs/react-dom.js:16315:20)\n' +
      '    at mountIndeterminateComponent (http://localhost:64000/libs/react-dom.js:20084:15)\n' +
      '    at beginWork (http://localhost:64000/libs/react-dom.js:21597:18)\n' +
      '    at beginWork$1 (http://localhost:64000/libs/react-dom.js:27436:16)\n' +
      '    at performUnitOfWork (http://localhost:64000/libs/react-dom.js:26570:14)\n' +
      '    at workLoopSync (http://localhost:64000/libs/react-dom.js:26476:7)',
    objectId: '-7725925962384502251.3.1'
  }
}

reproducer.zip
Bug behavior

[ ] Flaky
[ ] PDF

Minimal, reproducible example
const http = require('node:http');
const puppeteer = require('puppeteer');

(async function () {
  const server = http.createServer((req, res) => {
    res.end(`


Add credhub exporter

This PR integrates a new exporter for monitoring some content of a credhub server, specifically creation dates of credentials and expiration of certificates (it does not yet provide metrics about the credhub server health such as error rates, response times, or total number of entries).
This PR includes an associated alerts that triggers when certificates are close to expiration.
We'd be happy to transfer ownership of the orange-cloudfoundry/credhub_exporter to the https://github.com/bosh-prometheus/ organization if this makes more sense for the community to contribute maintenance.
The PR requires blob credhub_exporter-0.1.4.linux-amd64.tar.gz to be added at path credhub_exporter/credhub_exporter-0.1.4.linux-amd64.tar.gz
Relates to orange-cloudfoundry/paas-templates#84

Thanks @psycofdj. I upload the credhub_exporter-0.1.4.linux-amd64.tar.gz  blob at https://github.com/bosh-prometheus/prometheus-boshrelease/commit/2b6421aa7e045e242e92c3a490804f08095d2104.


Increase the HTTP timeout

I have a custom API for Willow, and it's working pretty well in general, but sometimes if OpenAI takes too long to respond (mostly because of multiple roundtrips with actions like adding appointments), Willow times out. Is there a way to increase the timeout? I'm fine with a 30 sec timeout when it has to do things like read me my calendar, as I know that will take a while.

I just flashed 0.3.0-rc.2, but the timeout doesn't seem to have increased to 10 seconds (it seems to time out after 5 seconds for me). Also, what's the rationale behind such a short timeout? If I'm asking something, I'd probably prefer to wait for the response, rather than get an error, especially when the response does something somewhere (like add a calendar event).
Maybe 30 sec would be preferable? The best would be a configurable timeout via WAS, if possible.

I suspect you're confusing the timeout to WIS with the timeout to the HTTP REST endpoint. That would explain why you're seeing 5s: https://github.com/espressif/esp-idf/blob/v5.1.1/components/esp_http_client/esp_http_client.c#L145. Can you confirm this?

Yes, sorry, I didn't realize that code wasn't for the API server. Is it possible to set the API server timeout to something long, 30 or 60 sec? Anything above that, I'd probably write something async and use the new (and fantastic) notifications feature.
I don't think the UX would suffer, especially if the request is abortable (ie I can say the wake word while waiting and it will cancel the old request and begin a new cycle).

Please try enabling WAS Command Endpoint mode in WAS Advanced settings. This should have a timeout of 30s. WAS Command Endpoint mode will eventually become default, and endpoint support will eventually be removed from Willow, so it's unlikely we will make any new changes to the endpoint code in Willow.

I can certainly do that, thank you. Is there any documentation for how to use the command endpoint? I haven't managed to find anything on the Willow site or Google.

Ah, is the difference that the WAS connects to my REST API, rather than Willow directly? I'm going to have some Docker rearranging, if so. Out of curiosity, doesn't that increase the latency?

There is brief info about command endpoint support in WAS here.

Out of curiosity, doesn't that increase the latency?
We actually experience lower latency with WAS Command Endpoint mode. The WebSocket connection to WAS is always open, so there is no overhead to setup a new connection when you make a request. This now happens on the machine running WAS, which is almost always going to be more powerful than the ESP32-S3 in the Willow device.

This worked great, thanks! There's only one bug: The screen turns off on the timeout, regardless of whether there's a request in flight. Instead, the screen should turn off timeout seconds after the end of activity.

Fixing that might be very tricky to get right. In any case, that belongs in a separate issue.

Filed #349, thank you.


Add Run In Postman facility to all REST APIs

Is your suggestion related to a missing or misleading document? Please describe.
Run In Postman is a facility provided in documentation to import REST APIs as a collection to Postman. This facility is only provided in some REST APIs only.
Describe the improvement
Below figure shows  Run In Postman  feature in claim management REST API guideline (https://is.docs.wso2.com/en/latest/develop/claim-management-rest-api/). Similar to it Run In Postman facility needs to be included in each REST APIs to increase the usability when using the documentation.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Add visuals and examples

Description
Added animations and visuals that showcase the implementation of algorithms as well as examples of the expected outputs on a simple dataset
Pull request type

[x] Fix or improvement of an existing page

Related PRs and issues
Closes: https://github.com/memgraph/documentation/issues/352

This still needs to be updated with proper graph visuals


Allow force removing containers with unavailable OCI runtime

When the OCI runtime associated to a container could not be found in the configuration, removing that container is not possible. Allow force removing the container by detecting when this happens.

This typically happens when you create a container with a specific runtime in libpod.conf, and later the runtime name is changed in the the conf, with outcome:
$ pd rm -f 06
Error: container 060314dd88dc22cdf6d21b8f8146dcf2481ab158c5a29f79a9ecb81cef2e6d9e was created with OCI runtime my_runtime, but that runtime is not available in the current configuration: internal libpod error

/ok-to-test

I understand the intent here, but I don't know if trying to convince the existing remove API to work with containers which completely lack a valid runtime is sane.
We may want a new API to forcibly evict a container from the DB and storage with minimal checks. Retrieve it from the DB; if there's an error doing so, skip everything else and try removing from the DB. If we can successfully retrieve the container, remove from storage.

thanks @mheon, you're right, I felt my changes were kindof hacky instead of a proper solution. I'll evaluate what you proposed and see if I can come back with something better.

@mheon following your advice a possible way to handle this is:

Adding an evict flag to rm (better to have --force used to stop running containers)
Add a DB API to retrieve a container ID / config.
Add an Evict API to remove a container without the OCI runtime interaction using the container config retrieved with the previous API.

Any feedback?

I have some thoughts about the CLI here (I think allowing --force to be passed more than once might make sense, like multiple --verbose calls for more logging - --force --force or -ff to aggressively remove).
My thought here would be that Evict() or whatever we would choose to name the API - would take a full container ID as an argument, as opposed to a container itself. It would attempt to retrieve the container from the DB, and if that was successful, try and perform a normal removal. If any errors occurred, it would clean up as best as it could, and make absolutely certain the container was removed from the DB. If retrieving the container from the DB failed, we remove the container from the DB directly, then use the RemoveStorageContainer() API to remove it from c/storage.

I'm closing this and continuing in a new PR to keep things cleaner: https://github.com/containers/libpod/pull/3549


[WIP] Move pattern compilation to module level

@pipermerriam is this along the lines of what you were talking about in the last pr?
'It's small savings but moving this to a module level definition instead of re-defining it everytime this function runs will yield some albeit minor speed improvements.'

@pipermerriam Should be good to go - or close this pr since it's minor - and i'll include the change down the road.


add text "my text"

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Please don't spam our repo by submitting PRs that randomly jam "my text" into articles.


gitkraken: 4.0.2 -> 4.0.5

Motivation for this change
Fixes #47498. Note that the releases have moved to a new URL; I'm not sure they still host the earlier versions.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

Does it only segfault for me?
$ nix-shell -p gitkraken
[nix-shell:~/git/nixpkgs]$ gitkraken
Segmentation fault (core dumped)

Works here.

Should be ok then I guess.


Add some path to tease out negative volume tets.

cqid: VisIt00008918cqsubmitter: Cyrus Harrisoncqsubmitdate: 04/10/09 Hank Shay has some data where the simulation says there are inverted tets. To find out where things are going wrong he tried to use the volume expression & look for negative volumes - but it appears VisIt is being too smart here and fixing the inverted tets somewhere in the pipeline. For debugging he wants a version of the volume expression that can identify this case.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 36
Status: Pending
Project: VisIt
Tracker: Feature
Priority: Normal
Subject: Add some path to tease out negative volume tets.
Assigned to: -
Category: -
Target version: -
Author: Cyrus Harrison
Start:
Due date:
% Done: 0%
Estimated time:
Created: 06/21/2010 07:15 pm
Updated: 07/06/2010 07:43 pm
Likelihood:
Severity:
Found in version: 2.12.3
Impact: 3 - Medium
Expected Use: 2 - Rare
OS: All
Support Group: DOE/ASC
Description:
cqid: VisIt00008918cqsubmitter: Cyrus Harrisoncqsubmitdate: 04/10/09 Hank Shay has some data where the simulation says there are inverted tets. To find out where things are going wrong he tried to use the volume expression & look for negative volumes - but it appears VisIt is being too smart here and fixing the inverted tets somewhere in the pipeline. For debugging he wants a version of the volume expression that can identify this case.
Comments:
The desired solution is to add an argument to the volume expression that allows a user to override the default behavior when they want to use the expression to debug inverted tets.

Taking out of reviewed state for discussion.
Current version of the volume expression displays negative volumes by default. Exactly the desired solution indicated by the comment.
I tested this by:
loading arbpoly-zoohybrid.silo, then exporting as VTK and using the tetrahedralize export option.
I then loaded the exported database, created a volume expression for the mesh and plotted a Pseudocolor plot.
The legend shows a negative minimum value.
I also added a Threshold operator to display only those cells with negative values.
There is an option to force avtVMetricVolume to use only positive volumes, but that setting isn't exposed to the user. It is set by certain queries that utilize it. (Should forcing positive volumes be a user-settable option)?
Looking at the history of avtVMetricVolume, and the verdict library used to calculate the tet volume, it appears that allowing negative volumes has been part of the volume expression for a very long time.
Should this be closed?

We decided to take low-hanging fruit label off as this is likely more involved. In particular, Silo plugin has auto-detection logic that examines the first tet of a ucd mesh and if that first tet is inverted, it will invert every tet in the mesh it finds. This auto-logic would foil in any attempt to view negative volumes later on.
We could make that Silo plugin logic part of a read option (which is on by default) and if a user turned that off, then negative volume tets would make it into VisIt and then the proposed fix, to add an argument to volume expression to allow negative volumes would then address this issue.
For non-silo data, of course, just enhancing the volume expression would suffice. However, do other users in the world really want negative volume tets?

@markcmiller86 see my comments above. The volume expression already allows negative volumes by default.

Ah, ok. I misunderstood. Ok, so I think this is a low-hanging fruit item but for a different reason than it was first categorized that way. All that we need is a database read option to disable the tet checking and correcting logic in Silo plugin which is here...
https://github.com/visit-dav/visit/blob/96f93d6c68b43e3367ac0ed53d42c08d3d69ea13/src/databases/Silo/avtSiloFileFormat.C#L10414-L10424

We should add an option to Silo database read options that turns off auto inverting of tets.


Example: linting/validation

Hey, I was wondering if you'd consider throwing up a sample for enabling linting/validation? I'm trying to get mine setup with YAML but I'm not really sure to start.
So far I've got it working with the following in template tags:
        <editor
          v-model="form.content"
          @init="editorInit"
          lang="yaml"
          :theme='editorTheming()'
          :height="windowHeight"
          :width="windowWidth"
          class="editor"
        ></editor>

and the following in script tags:
  components: {
    editor: require("vue2-ace-editor")
  },
  methods: {
    editorInit() {
      require("brace/mode/yaml");
      require("brace/theme/twilight");
      require("brace/theme/textmate");
    },
    editorTheming(){
      if ( this.$vuetify.theme.dark == false) {
        return "textmate"
      } else {
        return "twilight"
      }
    },

This works great and has auto light/darkmode to match my theme but no syntax highlighting or errors.

same request


Avoid crash when Quick Inserting actor with embedded CEs

Including embedded-CEs-in-embedded-items, i.e. spells.

Sort-of. It would be irrelevant, as new IDs are generated when you add a document to another document (otherwise you'd run into all sorts of ID-collision problems when, say, dragging an item to a sheet multiple times), but...
Plutonium's Quick Inserts stuff (ab)uses Foundry's "temporary" documents, which don't get run through the same pipeline (and so don't get the ID-cleaning-before-save pass), and therefore spits model validation errors if we don't manually scrub them up

and after all that spilled ink: https://github.com/DFreds/dfreds-convenient-effects/releases/tag/v4.0.0

Delete internal Effect class in favor of using ActiveEffect directly

so this is going to become irrelevant very quickly!


refactor: extract swapper actions to separate file

Description
Extract swapper actions to a separate file for easier maintenance and extensibil
ity moving forward.
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
Progress towards https://github.com/shapeshift/web/issues/3468
Risk
Small, refactor only. If it works at all it probably works as it should.
Testing
Refactor only, so no changes expected - however the swapper should continue to w
ork as expected.
Engineering
☝
Operations
👆
Screenshots (if applicable)
N/A

Current dependencies on/for this PR:

develop

PR #4077

PR #4078

PR #4079

PR #4080

PR #4096   👈

This comment was auto-generated by Graphite.


EXSWHTEC-224 - Test cases ID clean up and documentation for Memory Management, Vulkan Interop Memory Management and Peer-to-Peer access

Added Doxygen comments for all Test Cases regarding all Memory Management APIs. They will not be listed to have more clear description.
Added Doxygen comments for all Test Cases regarding Vulkan Interop APIs:

hipExternalMemoryGetMappedBuffer
hipImportExternalMemory
hipDestroyExternalMemory
hipSignalExternalSemaphoresAsync
hipWaitExternalSemaphoresAsync
hipImportExternalSemaphore
hipDestroyExternalSemaphore

Added Doxygen comments for all Test Cases regarding Peer-to-Peer access APIs:

hipDeviceCanAccessPeer
hipDeviceEnablePeerAccess
hipDeviceDisablePeerAccess
hipMemGetAddressRange
hipMemcpyPeer
hipMemcpyPeerAsync

The goal is to generate HTML pages for Test Plan based on the state of tests source code.
Depends on:

#15
#16
#17
#18
#19
#25
#26
#27
#28
#29
#31
#32
#34
#49
#51
#52
#53
#54
#55
#56
#96

@milos-mozetic
Will you please resolve the merge conflicts for this PR?


Add post-hook

Refers to https://github.com/kereis/traefik-certs-dumper/issues/77

Hey,
thank you for your contribution again. 😄
In that case, you were faster than me. 🚀 I will check your implementation with mine ASAP.

I added some documentation, as well as some logging stuff. Feel free to take a look at it. :)


Zotero URI links result in "page not found" error

Describe the issue
When clicking the link in a Zotero URI property in Notion, the user ends up on a Zotero error page with the error message: page not found.
To Reproduce
Steps to reproduce the behavior:

Go to a Notion page created by Notero that includes the Zotero URI property
Click on the link in the Zotero URI property
See the "page not found" error page

Expected behavior
Clicking the link opens the desired item in the Zotero web library.
Screenshots
https://user-images.githubusercontent.com/299357/202096649-17264929-c22d-432f-a228-471cd99e3e1e.mp4

I've reached out for support in the Zotero forums.

Response from Dan Stillman (Zotero team) in the forums:

Yes, sorry, we had to shut those off due to abuse (though note that, while getItemURI() worked in practice, it was never guaranteed to provide a web link — that's just a URI to identify the item).
The web API provides the canonical web library URL for every item in links.alternate.href.
For the client, we'll add a function to get web library links using the username slug. For now, you can use Zotero.Users.getCurrentUsername() and apply the same transformation we use for the API. (There won't be a username if the person hasn't synced.)

Hi @dvanoni ,
my way for solving this issue is to use a chrome add-on called "URL redirect for developers" as a middle point to open the zotero application and find the item.
the code to import into the add-on is shown below:
{
  "settingsSchemaVersion": 1,
  "enabled": true,
  "removeCSPRules": [],
  "redirectRules": [
    {
      "enabled": true,
      "fromPattern": "*://www.zotero.org/{user}/items/{id}",
      "toPattern": "zotero://select/library/items/{id}"
    },
    {
      "enabled": true,
      "fromPattern": "http://zotero.org/users/{user}/items/{id}",
      "toPattern": "https://www.zotero.org/{user}/items/{id}"
    }
  ]
}

add the extension from chrome extension market

click the import button and paste the codes shown above

As long as the chrome open, click on the "zotero url" the chrome will redirect back to the zotero application and find the item it points to.

it works for me since almost all the time when I use zotero, I also keep the chrome on.
https://user-images.githubusercontent.com/42455304/206180957-add78271-0981-4c1a-a6d1-6ef7e0bea2b2.mov

Also facing this problem.

The problem has not been solved?

I haven't had time to get to this one yet, but it's on the todo list!

By the way, happen to have any experience using LiquidText? I'd love to figure out a way to also add liquidtext links to this database. For example:
[[GFM](lt://openProj/F76A9861-A78F-4BE3-973E-6D511348F1A7)](lt://openProj/F76A9861-A78F-4BE3-973E-6D511348F1A7)

@austinmw, unfortunately, it looks like Notion still only supports http and https links.
You could try using the Chrome extension that @sheldon123z mentioned above with something like the following:
From: http://openProj/{projId}
To: lt://openProj/{projId}
Then, when you paste one of those LiquidText links into Notion, you'd need to replace the leading lt with http so that Notion will recognize it as a link.
I haven't used the extension myself, so I'm not sure if I have it quite right, but let me know if you give it a try!

Another URL redirect tool was shared here: https://github.com/dvanoni/notero/issues/78#issuecomment-1378732014

Hi. thanks for this awesome tool.
I propose a little hint on README about this issue.
I started using this plugin today and was confused about why the links were not working.

If you're using Firefox, the extension Firefox Redirector provides a workaround. I had success with the following wildcard rule:

@sheldon123z Hi, could you please share the link to the Chrome add-on you use? I cannot find it on Chrome extension market. xiexie.

@sheldon123z Hi, could you please share the link to the Chrome add-on you use? I cannot find it on Chrome extension market. xiexie.

sorry reply so late, I didn't see your message, here is the extension github page, it seems like already removed from Chrome extension market. Please copy & paste the codes I provided, it should work.
https://github.com/wavebeem/url-redirect-webextension

@Skywuuuu
Another point for achiving this is that keep your browser and Zotero application open at the same time, then you can click the Zotero link on notion, the browser will redirect you to Zotero and have the correct item selected.

url-redirect-webextension-master.zip

This should be fixed in v0.5.6! Please let me know if you have any trouble with it.


Event Hubs Trigger Checkpoint Context

Overview
When statefully stream processing via an Event Hubs triggered Azure Functions instance it is sometimes necessary to periodically checkpoint in-memory state (which has been materialized from multiple event batches) to durable storage.
For consistency and efficiency this checkpointing should ideally not be constrained to happening every batch of messages per partition and should arguably occur at the end of the batch of messages which will trigger a checkpoint of the event hub by the underlying EventHubListener, immediately prior to that checkpoint.
To do this, the application needs be aware of the Event Hubs trigger runtime's intent to checkpoint a given batch on a given partition.
Considerations
A PartitionContext is already exposed by as a bindable parameter but it is immutable. It is also not publicly extendable with additional properties within the context of the Event Hubs binding library.
Currently the EventHubListener is unaware of whether it needs to checkpoint until after a function is invoked. This will now need to be calculated prior.
Proposal
~Expose a new CheckpointContext which, initially, exposes to the application whether it IsCheckpointingAfterInvocation. This context in future could also provide more detail around how close the runtime is to checkpointing, for example the number of remaining invocations, so application checkpointing can be distributed uniformly over the Event Hub batch checkpointing frequency if desired.~
As per @jsquire's propsal, extend PartitionContext with a new publicly available class (proposing TriggerPartitionContext) which, initially, exposes to the application whether it IsCheckpointingAfterInvocation. This context in future could also provide more detail around how close the runtime is to checkpointing, for example the number of remaining invocations, so application checkpointing can be distributed uniformly over the Event Hub batch checkpointing frequency if desired.
Usage
[FunctionName(nameof(OnEventHubTrigger))]
public async Task Run(
    [EventHubTrigger("%EventHubName%", Connection = "EventHubConnectionString")] EventData[] events,
    TriggerPartitionContext partitionContext)
    {
        await ProcessBatchAsync(events);

        if (partitionContext.IsCheckpointingAfterInvocation)
        {
            await CheckpointInMemoryStateToStorageAsync();
        }
    }

closes #28649

/azp run net - eventhub - tests


hi

hello

hello?

Not an issue, should be closed 👎

Not an issue, should be closed -1

what?

Not an issue, should be closed -1

Maybe let them explain the issue before you close the ticket


Link frontend with backend API Conversation

Use https://github.com/arc53/DocsGPT/wiki/API-docs as you guide,
Use API at docsgpt.arc53.com/api/answer for now, ill replace it later in code with correct local address
/api/answer gives answer to a question, should be triggered everytime user sends a message
Here is example fetch
fetch("https://docsgpt.arc53.com/api/answer", {
      "method": "POST",
      "headers": {
            "Content-Type": "application/json; charset=utf-8"
      },
      "body": JSON.stringify({"question":"Hi","history":null,"api_key":"OPENAI_API_KEY","embeddings_key":"OPENAI_API_KEY",
      "active_docs": "javascript/.project/ES2015/openai_text-embedding-ada-002/"})
})
.then((res) => res.text())
.then(console.log.bind(console))

What is active_docs and how to construct it.
Its language + name + version + model
if language and name are the same then its
language + .project + version + model
So for something like pandas it will look like
python/pandas/1.1.1/openai_text-embedding-ada-002/

Finished it in api-linking branch,


ADD : Loader

Related to #163
closes #163
Describe the changes you've made
ADD : Loader
An animating loader has been added with matching css styles

Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Code has been tested and verified by me on localhost
Checklist:

[X] My code follows the guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.

Screenshots (Images)

Before the changes
After the Changes

Recordings (Video with audio)

Before the changes
After the Changes

<Upload_Recording>
<Upload_Recording>

https://github.com/prakhartiwari0/Arito/assets/94990764/d689e5f0-c796-41a8-be5e-2bed0b8f9804

Sorry to say but we reverted your PR.
As the code doesn't make any significant improvement in the code base. You set a timer for 2sec to display the loader which makes no sense.


Support the GPT UI

Which GPT UI are you referring to? This one?
https://github.com/ricklamers/gpt-code-ui
~~https://github.com/amauryfischer/Auto-GPT-WebUI~~

When I had created the ticket I was inspired by https://github.com/ConnectAI-E/AutoGPT-Next-Web
Now as I go through the repository I can't tell if how it relates to significant-gravitas/auto-gpt


Allow KME listener bind address in cmdline

Signed-off-by: Rajeev Ranjan<EMAIL_ADDRESS>

@rranjan3
Looks like the CI build did not run because of Jenkins resource problems.


disable operator test again

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
e9deb50e7db9ec3810dbeb2079d398c4236eb94f
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
7d4a67f762a3dc01d63e794e8799f6d3c53d416c
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
7d4a67f762a3dc01d63e794e8799f6d3c53d416c
link
/test release-notes_istio

integ-telemetry-mc-k8s-tests_istio
7d4a67f762a3dc01d63e794e8799f6d3c53d416c
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


v4l2decode: add wayland display to v4l2 decoder

support wayland display for v4l2 decoder
Signed-off-by: jkyu<EMAIL_ADDRESS>

+1

merged as 2d4a5362ddefd2a71929c3fce28b4af35c2be356


Fix memory leak occuring with new layout of string tensors

Also fix and actually use JavaCPP deallocator for TF_Session as well
Fixes #251 and we should probably add a regression test for that somewhere.
What would be a good place?

Thanks @saudet , can you please rebase your changes on the r0.3 branch instead? We'll merge it in that branch to quickly release a version 0.3.1 with these fixes.
For the regression test, what about here?

I've changed the base to r0.3 and it seems like it can still merge this, so go ahead!


Heart Rate and Calories don't show on localhost:8080 or after running start.bat

Running start.bat only prints
"node ./public/app.js
Listening at port 8080
Client connected"

If you aren’t seeing any heart rate or calorie data being printed to the console then the watch data isn’t getting received. Make sure you have the IP address and port inputted correctly on the watch and that the watch is on the same network as the device you are tying to receive the data on.


PixelServer should set cache-control on images being returned to github

It's not complicated to add this, and if it results in even slightly better numbers I'm completely fine with it.
Reference for Adding Cache-Control Headers
<Snipped from a mail from @pakrym >
Looking at https://github.com/Azure/azure-sdk-for-net/pull/8559 PR to update pixel tracking links today I investigated a little bit to see how exactly it works.
What if found is that Github is seems to be caching images according to https://help.github.com/en/github/authenticating-to-github/about-anonymized-image-urls and what I see in the browser so I’m not sure how pixel tracking would work.
What’s interesting is that we did collect some data from pixel-server. But the data we collected looks very suspicious.

Adding the header is not enough, we also need to understand where the current data is coming from a db why does it look like this.

Additionally, @pakrym suggested that we log the referrer headers to understand where our traffic is coming from.  This could give us some clarity on how how github is caching the images.


check sequence id before updating resource status.

This PR aims to verify the sequence ID (generated using https://github.com/bwmarrin/snowflake) before updating the resource status. This is done to maintain the order of resource status updates.
ref: https://issues.redhat.com/browse/OCM-5359
/assign @qiujian16 @skeeey @clyang82

Appended test results:
# make test && make test-integration
CGO_ENABLED=1 GOEXPERIMENT=boringcrypto go install -ldflags="" ./cmd/maestro
OCM_ENV=testing gotestsum --format short-verbose -- -p 1 -v  \
	./pkg/... \
	./cmd/...


Ensure Portal E2E & functional tests run in RDev

Add test fixtures, as needed, to seed data required for these tests. These can be dynamically-generated or statical fixtures, as appropriate. Ideally, test fixtures should be made available for usable in RDev stacks for ad hoc testing, via scripts/commands that can seed the stack.
Add configuration, as needed, for FE to identify the BE endpoint for a specifc RDev stack

This issue does not cover invocation of these scripts in GHA, which will be handled by #5455.

Supersedes #5454, though there may be some additional points to consider in that issue.

@Bento007 Portal functional tests all work/pass now on RDev as a result this work, right? I suppose we can remove the "functional" part of this issue's title?

Done!


Move setClientLibToken to ServiceOptions.

After discussion with @chingor13, moving this API to ServiceOptions to use more broadly.

cc @dazuma


Add package-lock.json into the .gitignore file

Hi, Can you assign this issue to me? I  am new to open source and would like to work on this.

Hi @Ishpreet01 , we are currently not onboarding contributors outside of PB. Will let you know if anything comes up


ios: Don't destroy gltfio materials between asset loads

This causes a crash because materialProvider deletes an internal dummyTexture, which is never re-created.

Interesting, we should consider adding an evict() method to MaterialProvider for clients who need to free up memory.

Yeah, this could be useful.


Feature request ; Level of Details Calculation.

add level of details calculation in Malloy, a typical use case, is sum all, which basically return the total sum regardless of the grouping, is this something already supported, otherwise what's the plan if not

Hey @djouallah,  If I'm understanding what you're asking for, I believe something like this should get you the calculation you want:
query: table('malloy-data.faa.airports') -> {
  nest: airports_by_state is {
    group_by: state
    aggregate: airport_count is count()
  }
  aggregate: total_airport_count is count()
}

Or was there something different you had in mind?

Also worth checking out Aggregate Locality  - I believe this may be along the lines of what you're looking for and should give you a lot of flexibility about how/where to aggregate.

@anikaks   thanks, but maybe, it will be nice if it is defined at the measure level not in the Query
maybe something like total_airport_count is count(), all(), so it does ignore aggregation regardless of the Query used ?

@lloydtabb and I were talking about this today; there's definitely something there in navigating the aggregate locality / aggregating without grouping. Thanks for the feature request!


Add CityCatalyst

Insert URLs to the project here:
https://github.com/Open-Earth-Foundation/CityCatalyst
In one sentence, explain what the project is about:
Open Source carbon accounting for cities

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

Documentation: https://github.com/Open-Earth-Foundation/CityCatalyst/wiki

@lemilonkh @cephaschapa @evanp


overlay2: fix unmounting layer without merge dir

@dmcgowan
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

@cpuguy83 https://github.com/docker/docker/pull/31069/files#diff-a15814b493b1d5546c0fd85701e21142L480

cherry-picked into 17.03.1 through https://github.com/docker/docker/pull/31754


Treat non-embedded data

Need a function that also embeds the data if a single time series is provided.

Done in #11


Responsive Footer

Description
The footer is now responsive for bigger screens as well.
Fixes #84

Bugs
New Feature
Documentation

How Has This Been Tested?
On live server
Checklist:

[x] My PR follows the style guidelines of this project
[x] I have performed a self-review of my own code or materials
[x] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes

Hello @anushruti11 this needs work, you have just fixed the footer, it should not overlap the main content and appear only when scrolled down to the bottom.

Hello @anushruti11 this needs work, you have just fixed the footer, it should not overlap the main content and appear only when scrolled down to the bottom.

Please guide me over this. Which CSS attribute should be used here for a responsive footer in screens like iPad. Although, it is responsive in the other alternatives, but for iPad screen only sticky footer works.

@manankohlii I need your guidance.

@anushruti11 waiting for mentors to be assigned to this project, you may get in touch with them. Otherwise you always have YouTube.

@shivamsingh124 can you guide me over this ?

https://stackoverflow.com/questions/54646939/why-is-my-positionsticky-not-working-on-ios
You should check this once if you still need any kind of guidance let me know.

https://stackoverflow.com/questions/54646939/why-is-my-positionsticky-not-working-on-ios
You should check this once if you still need any kind of guidance let me know.

@shivamsingh124 I tried this but it isn't working. The footer is still not responsive for iPad screen.

Please share the deployed link I'll check it.

Please share the deployed link I'll check it.

https://anushruti11.github.io/spacex-launch-data/

@shivamsingh124 Any updates?

Yes,
The link you gave at the time of submission and that you provided me 11 days ago are not the same (was expected to be ) previously you used fixed position so it got struck for whole page then use used sticky.
Reason it got delayed.
use Sticky providing offset from Top accordingly.
you can also achieve this with assigning value to bottom using js when it got scrolled to the bottom.

P.S. If you haven't got your answer then do describe your problem in a documented form.

Yes,
The link you gave at the time of submission and that you provided me 11 days ago are not the same (was expected to be ) previously you used fixed position so it got struck for whole page then use used sticky.
Reason it got delayed.
use Sticky providing offset from Top accordingly.
you can also achieve this with assigning value to bottom using js when it got scrolled to the bottom.

@shivamsingh124 could you please share the deployed link of this output?

Haven't deployed nor saved have just changed code on inspect element.
Follow the steps mentioned to get the same output.


Is there any way I can d/l an environment for an I-4

Not sure why it won't d/load the soft ware been having problems finding the correct one

I don't know what an I-4 is. Sounds like this may not be related to the article...?

Closing because this doesn't appear to be relevant. Please correct me & explain a bit more if I'm wrong!


Corrected the incorrect description of the Producer module

What is the purpose of the change
Corrected the incorrect description of the Producer module in this picture (Incorrectly introduced Consumer in the Producer module)
Brief changelog
Graphic correction
Verifying this change
https://github.com/apache/rocketmq/issues/2855#issue-873498812

Pls make your pr  request to develop branch.

@b1n90 ping

on it.
发自我的iPhone
------------------ Original ------------------
From: Heng Du @.>
Date: Fri,May 21,2021 9:35 AM
To: apache/rocketmq @.>
Cc: b1n90 @.>, Mention @.>
Subject: Re: [apache/rocketmq] Corrected the incorrect description of the Producer module (#2856)
@b1n90 ping
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

see #2857

It seems two different pr.

Coverage decreased (-0.04%) to 51.795% when pulling 6e39f9252a758794e3d047fde7bafa530f800a9c on b1n90:master into b4240d5cea8d001c21b9c0d73f5aa700fcd0d568 on apache:master.


Reduce app bundle size

Right now the bundle (which you can get by running npm run build inside the client directory) stands at ~6.8 MB. This is significantly smaller when g-zipped, but is still way too large and could be trimmed down. We should look into webpack minification customization, make sure tree shaking is working, and also figure out if we want to bundle images and other static files.

Closing as stale. I'll open another issue about removing static files from the bundle because I think it's easier to tackle that one area, but I don't think this is a huge deal because right now our bundle is only 3.5 MB uncompressed, 812 kb compressed. The larger problem is that the entire bundle needs to be loaded for the page to start loading but we don't need everything in there for the initial page load.

See this article for details about reading the Chrome devtools network tab: https://developer.chrome.com/docs/devtools/network/reference/#total-size
I ran the source-map-explorer npm package on our project to generate the figure below (best viewed in new tab), and it looks like some of the biggest offenders for our bundle are static assets like the logos and building and department catalogs, which would be better loaded at runtime instead of bottlenecking the bundle download, but those would only net us about 50k less uncompressed, which is pretty much negligible:


Upgrade django prices

With this PR: https://github.com/mirumee/django-prices/pull/73, django-prices will be able to support multi currencies. We should proceed with all described steps needed to upgrade package

Problem with django-prices 1.04 - #4378

Little update: I will start working on it from Wednesday after as we have a few things to discuss before migrating 👍


nvcc fatal   : Value 'sm_20' is not defined for option 'gpu-architecture'

When I try to generate a python wrapper, it returns error information as follow:
nvcc fatal   : Value 'sm_20' is not defined for option 'gpu-architecture'
My cuda version is 11.0, and using a GTX 1050ti gpu.
Any idea how to solve this?
Thanks!

Hi there,
This looks like an nvcc issue; the options are listed on the docs: https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#virtual-architecture-feature-list
(nvcc has changed the available keywords for that option)
KN

On Aug 11, 2020, at 12:38 PM, T.L<EMAIL_ADDRESS>wrote:
When I try to generate a python wrapper, it returns error information as follow:
nvcc fatal : Value 'sm_20' is not defined for option 'gpu-architecture'
My cuda version is 11.0, and using a GTX 1050ti gpu.
Any idea how to solve this?
Thanks!
https://user-images.githubusercontent.com/55120383/89941196-aed03e00-dbe8-11ea-971c-3f226d5a774a.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/SLACKHA/pyJac/issues/38, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABOPYAW4E4DA4KNQPXBDJ3SAGM4PANCNFSM4P3OI56Q.

Hi there, This looks like an nvcc issue; the options are listed on the docs: https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#virtual-architecture-feature-list (nvcc has changed the available keywords for that option) KN
…
On Aug 11, 2020, at 12:38 PM, T.L @.***> wrote: When I try to generate a python wrapper, it returns error information as follow: nvcc fatal : Value 'sm_20' is not defined for option 'gpu-architecture' My cuda version is 11.0, and using a GTX 1050ti gpu. Any idea how to solve this? Thanks! https://user-images.githubusercontent.com/55120383/89941196-aed03e00-dbe8-11ea-971c-3f226d5a774a.png — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#38>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABOPYAW4E4DA4KNQPXBDJ3SAGM4PANCNFSM4P3OI56Q.

Hi Kyle,
Em... I am new to nvcc, how can I fix this issue? I do find "'nvcc': ['-arch=sm_20', '--ptxas-options=-v'" in the 'pyjacob_cuda_setup.py.in' file. But, no matter how I adjust the arch value, it still reports 'sm_20' error.

Update:
I changed all the 'sm_20' in the libgen.py file and in the 'pyjacob_cuda_setup.py.in' into 'sm_61'.
The error fixed.
But new error information shows up as follows:
cl : Command line warning D9002 : ignoring unknown option '-fPIC'
fatal error C1083: Cannot open include file: 'helper_cuda.h': No such file or directory

Final Update:
Using Linux instead of Windows, everything solved.


Malformed nifti header from epi unwarp artifact.

We should check nifti headers of files we produce to make sure they are in good order.

This is a common problem with several of the FSL outputs. Which file is this?

I guess this is not a problem anymore. Please reopen if we see this again.


Variables cannot be passed into ternaries

@umuro fyi.

Yes, it will be fixed with the new parser... Nevertheless worth adding to my unit test collection

Fixed in https://github.com/quantified-uncertainty/squiggle/pull/546


Boolean/array selection on Orbit and PhaseSpacePosition not working

e.g.,
ix = np.array([0,1,2,3,7])
w[ix]

I think this is fixed


Regex patterns on topic names

What is currently missing?
Currently only topic prefix and suffix can be enforced.
Possibility to have regex patterns on topic names would be more generic
How could this be improved?
Introducing pattern at topic request level
Is this a feature you would work on yourself?

[X] I plan to open a pull request for this feature

Leaving a comment to I'm sure not to miss updates on this :D
If that's implemented, we need to update our search elements in the UI. They currently communicate that the search will be for an exact match.


Can you give me some advice?I use the same parameters to run.But why the  Reformulated Querys are the same as the origin Querys ?

For how many iterations the model was trained? It is common that it will start producing new queries only after iteration 50K, sometimes 100K. This corresponds to 1 or 2 days of training on a GPU.
What is the Recall@40 on the train and validation sets?

Closing this since there was no answer.


Update package.json react version deps

Upgrade peer and dev dependencies to rely on React v15

:) thanks


site not using 100% width on iPhone 6S

First, thank you for a fantastic theme with clear installation and use instructions!
I built a site using a fork of HPSTR and it looks great on the desktop, iPad, and iPhone in landscape. However, in portrait position, there is about 1/3 of screen width that is blank. See image below. It resizes just fine when you re-orient the phone to landscape, but will not resize properly in portrait. Where do I begin to try to fix this? I poked around the web and it was suggested that I add body { min-width: 980px } to body in the css somewhere. Where should I begin modifying the css?

The problem is the long code blocks in your posts. If you scroll down about half way in your first post and look at the ~Library/Application Support/ line you'll see what I mean.
Code blocks have styling set on them to not wrap lines, which is causing is long string of text to extend outside of its parent container and push everything else outside the viewport.
You could remove white-space: nowrap; from it in the CSS but that will likely break something else.
The quick fix would be to not do such long inline code blocks and use the {% highlight %}{% endhighlight %} instead, which isn't ideal for single lines but it will make it a block element with scroll bars to avoid pushing everything else around.

I changed the long single code blocks to the {% highlight %}{% endhighlight %} from the back tics and that cured the problem.  Thank you so very much! Mark this as solved.


Add ReportError support for tasks

Going to skip this for now since it doesn't make sense in a non-scripting scenario. We might revisit this in the future if there's a demand for it.


Allow people to change their Scrapbook username via a command

/scrappy-changeusername
Checks that the username they want to set doesn't already exist in Airtable
Changes their username in Airtable
Finds every update that includes their previous username and replaces every instance of those with their new username

Closing for now because I don't actually want to do this anymore because I'm worried people will use this to troll


Gif don't play when it is a second page

Steps to reproduce

Set page layout to Double pages
Set orientation to Landscape
Go to a manga that has a gif Sore wa Rei no Shiwaza desu Chapter 5 has a gif on page 24

Expected behavior
The gif should play
Actual behavior
The gif doesn't play
Crash logs
No response
Neko version
2.13.3
Android version
Android 13
Device
Samsung Tab S7+
Other details
This also Happens to my phone. I can't remember if the gif plays when its the first page but when its a single page it works fine.
Phone:
Samsung Galaxy S10
SM-G973F
Neko: v2.13.3
Android 13
LineageOS: 20-20230526-Nightly-beyond1lte
411 dp
Jif
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to the newest version Latest.
[X] I have filled out all of the requested information in this form.

This still happens on my tablet and my phone. I set it to right to left and it looks like Fig 1 then I see the gif on the left side and the manga page on the right. When the gif is on the left page (when reading mode is set to Right to Left) is doesn't play the gif animation (eyes Blinks). if the gif is right page (Still in right to left reading mode) it plays fine. To see this in action Switch it Fig 2 and move to the last pages. At lest for me the last page disappears for some reason but the gif starting playing.
Reading mode
when I switched the reading mode to left to right the gif doesn't play when it is on the right side of both pages.
Fig. 1

Fig. 2

Device Specs
Phone:
Samsung Tab S7+
SM-T970
Neko: v2.13.5
Android 13
764 dp
One Ui: 5.1.1


exogenous variables

Description
Thank you for your labors.
Please, if it is possible, add to this package the possibility of supplying not only lag / sliding variables, but also exogenous variables
Use case
No response

Hi. Do you mean this: https://nixtla.github.io/mlforecast/forecast.html#dynamic-features?