Add missing metadata for kafka client sasl scram mechanism

What does this PR do?
Closes #510
Add missing metadata for Kafka Client SCRAM/SASL mechanism.
Note: This is my first PR in this repo: any help in the code review is greatly appreciated!
Code sections where the PR accesses files, network, docker or some external service
(example link to code section)
Checklist before merging

[ ] I have considered including reachability metadata directly in the library or the framework (see our contributing document)
[x] I am the original author of all content provided in the pull request, and I did not copy the content from any other source (see the tests section from our contributing document)
[ ] For all tests where I am not the sole author, I have added a comment that proves I may publish them under the specified license (see the tests section from our contributing document)
[x] I have properly formatted metadata files (see our formatting guide)
[x] I have added thorough tests (see the tests section from our contributing document)
[x] I have filled all places where my pull request accesses files, network, docker, or any other external service (see the section above)

Could you please verify the checkboxes. Especially: For all tests where I am not the sole author, I have added a comment that proves I may publish them under the specified license (see the tests section from our contributing document)

Could you please verify the checkboxes. Especially: For all tests where I am not the sole author, I have added a comment that proves I may publish them under the specified license (see the tests section from our contributing document)

Help me understand this thing. I've added a test method and I'm the only author of this method. I should add no comment, right? And then I should check the box.
For the other check, yes I've consider adding the metadata to the Apache repository but I don't know how to make a contribution on their repos.

I've checked the box considering the fact that I'm the sole author of the added test method offered in this PR.

Perfect, thank you for responding so quickly.

For the other check, yes I've consider adding the metadata to the Apache repository but I don't know how to make a contribution on their repos.

Thanks, that is OK. Ideally in those cases we should open a ticket on the repo stating that the support is needed. This allows the community to upvote the ticket.


Game crashes

The game crashes when opening a new adventure, Ice Palace, and importing a save
Player.log

Only workaround is try to rest on save and get rid of any effects before trying to import. If that doesn’t work export the heroes using ctrl shift e and start a new game with them.


AttributeError: 'AdamW' object has no attribute 'train'

Although unsloth was not the cause, the title error occurred at the start of training and accelerate seemed to be affecting it.
https://github.com/huggingface/transformers/issues/33620
pip install accelerate==0.34.2

I have been able to train without any problems using the following version.
Thank you.
$ pip list
Package                  Version
------------------------ ------------
accelerate               0.34.2
aiohttp                  3.9.5
aiosignal                1.3.1
async-timeout            4.0.3
attrs                    23.2.0
bitsandbytes             0.43.1
certifi                  2024.7.4
charset-normalizer       3.3.2
click                    8.1.7
datasets                 2.20.0
dill                     0.3.8
docker-pycreds           0.4.0
docstring_parser         0.16
einops                   0.8.0
filelock                 3.15.4
flash-attn               2.6.3
frozenlist               1.4.1
fsspec                   2024.5.0
gitdb                    4.0.11
GitPython                3.1.43
hf_transfer              0.1.8
huggingface-hub          0.23.4
idna                     3.7
Jinja2                   3.1.4
markdown-it-py           3.0.0
MarkupSafe               2.1.5
mdurl                    0.1.2
mpmath                   1.3.0
multidict                6.0.5
multiprocess             0.70.16
networkx                 3.3
ninja                    <IP_ADDRESS>
numpy                    1.26.4
nvidia-cublas-cu12       <IP_ADDRESS>
nvidia-cuda-cupti-cu12   12.1.105
nvidia-cuda-nvrtc-cu12   12.1.105
nvidia-cuda-runtime-cu12 12.1.105
nvidia-cudnn-cu12        <IP_ADDRESS>
nvidia-cufft-cu12        <IP_ADDRESS>
nvidia-curand-cu12       <IP_ADDRESS>
nvidia-cusolver-cu12     <IP_ADDRESS>
nvidia-cusparse-cu12     <IP_ADDRESS>
nvidia-nccl-cu12         2.20.5
nvidia-nvjitlink-cu12    12.5.82
nvidia-nvtx-cu12         12.1.105
packaging                24.1
pandas                   2.2.2
peft                     0.11.1
pillow                   10.4.0
pip                      22.0.2
platformdirs             4.2.2
protobuf                 3.20.3
psutil                   6.0.0
pyarrow                  16.1.0
pyarrow-hotfix           0.6
Pygments                 2.18.0
python-dateutil          2.9.0.post0
pytz                     2024.1
PyYAML                   6.0.1
regex                    2024.5.15
requests                 2.32.3
rich                     13.7.1
safetensors              0.4.3
sentencepiece            0.2.0
sentry-sdk               2.7.1
setproctitle             1.3.3
setuptools               59.6.0
shtab                    1.7.1
six                      1.16.0
smmap                    5.0.1
sympy                    1.13.0
tokenizers               0.20.0
torch                    2.3.0
tqdm                     4.66.4
transformers             4.45.1
triton                   2.3.0
trl                      0.9.6
typing_extensions        4.12.2
tyro                     0.8.5
tzdata                   2024.1
unsloth                  2024.9.post3
urllib3                  2.2.2
wandb                    0.17.4
wheel                    0.43.0
xformers                 0.0.26.post1
xxhash                   3.4.1
yarl                     1.9.4

Sorry on the delay - I added accelerate>=0.34.2 in pyproject.toml so future installs won't have this issue - thanks for the fixes everyone!

Updating unsloth_env_file.yml with:
accelerate==0.34.2
in https://github.com/unslothai/unsloth/wiki#nvidia-pascal-support
also works and allows training on nvidia pascal P40 P100

Maybe it is irrelevant, because I don't use unsloth, but I had the same issue. In my trainer.py the code
model.train()
        if hasattr(self.optimizer, "train") and callable(self.optimizer.train):
            self.optimizer.train()

caused the issue. I changed it to:
model.train()
        if hasattr(self.optimizer, 'train'):
            self.model.train()

and the training started without an error. Maybe that helps someone.
Update accelerate is probably better, but that didn't worked in my case. (I used Oobabooga with Training PRO extension)


New Commands fail in docker-entrypoint.sh script

Hello,
I am trying to add some commands to the docker-entrypoint.sh and it seems to be failing. Specifically I am trying to run envsubst. Here is the exact command:
envsubst < /workspace/config/mongod.conf.template > /workspace/mongod.conf
I have added the above line right before the exec $@ at the end of the script. I keep getting this error:
./start-db.sh: line 378: /workspace/mongod.conf: Permission denied
Other commands such as unset, ls, pwd work fine but I am not sure why this specific envsubst command keeps failing? Any ideas, thoughts, help would be much appreciated.
Note: I have tested the above failing command stand-alone and in a different script and it runs without any issues but fails in the docker-entrypoint.sh script.

It's likely due to not running as root:
https://github.com/docker-library/mongo/blob/3f117ac35a947ddff307aee85ecd5abe9e3a0fe1/4.0/docker-entrypoint.sh#L22
If you pre-create /workspace or use /tmp or something writable my the mongodb user instead, it will probably work.

@tianon When I try to run my commands before the gosu I am root but my commands run twice once as root and then as mongodb user. Any ideas on why that is the case?

That'd be because of the same line I linked you to: https://github.com/docker-library/mongo/blob/3f117ac35a947ddff307aee85ecd5abe9e3a0fe1/4.0/docker-entrypoint.sh#L22
The gosu re-runs the entrypoint as mongodb.

(Closing this, since it's not an issue with the image itself perse.)


Homebrew support

Hi, thanks for useful tool. Would you please consider porting it to Homebrew systems also?
Best regards,

hey there, binaries are the way to go, i don't use brew and not familiar with it, sorry!

@ashkrosh our project now contains a HomebrewFormula/terraform-docs.rb. This file will be updated with each new release of terraform-docs and will be contributed to the upstream github.com/Homebrew/homebrew-corerepository. Since today, we have v0.4.5 available as a release and available viabrew`. Have fun! :)


CertificateStore controller should periodically fetch the latest

Describe the solution you'd like
CertificateStore controller should periodically fetch the latest if the version of the certificate is not pinned.
Today, the customer will have to update the CRD with the latest version in a cert rotation scenario.

Wonder if we can just fetch all certificates as some certificate might be deleted from Key Vault.

This would solve #1131

closing in favor of tracking working in #1131. CertificateStore is deprecated and new features for fetching will target KeyManagementProvider resource instead


Adding smart contracts functionality to the Coretime chain

This RFC proposes adding smart contracts to the Coretime chain using platforms like Ethereum’s Solidity or Polkadot's Ink!. This will support automated region trading, dynamic pricing, and other advanced functionalities, expanding the chain's capabilities and fostering innovation. This suggestion follows discussions in PR #94.

To expand more on this, wonder why don't we just create a new Contract Hub system parachain that is ready to XCM any other system parachains in the ecosystem? I saw there is a proposal for expanding the functionalities of the Asset Hub via contract execution as well: https://polkadot.subsquare.io/referenda/885 and I saw this is a conflict of interests while we keep making the system parachains more complicated instead of simplifying the way other L1 parachains can XCM to these system parachains.
Let me know if this is not a correct place to start a further discussion.

In my mind the complication this brings to coretime is mostly integrating one more pallet. While if we not do this, we push the complexity to the developers of smart contracts. While we are working on making XCM easier and better integrated/accessible to smart contracts/ .... it will nevertheless always be a bit more complex than just calling a function, it will always stay asynchronous, it will always be much slower and it will always be of higher cost. Therefore it makes sense to stay on a chain where you can and only go cross chain when there is an actual need. E.g. getting funds to the Coretime chain to interact with the market.

I am in favour of this. I think asking contract developers to deal with XCM is a big ask when there is essentially no need for this. Sharding is a tool for scalability but we are not there, yet.  It is good that we have XCM once sharding is useful, though.

Seems like the sentiment is overall positive for this proposal, could we maybe proceed with the voting process?

/rfc propose

I think the RFC should specify that we want to deploy the same pallet that we deploy on AssetHub for contract execution. While this seems to be implied it should be explicitly stated in my opinion. This is important to make sure that we don't end up with two incompatible solutions and set of toolings.
In this scenario runtime functionality will be exposed via pre-compiles. I assume that there will just be a different set of pre-compiles on AssetHub vs. Coretime. From the point if view of Solidity developers it is just a different set of .sol interface files they can make use of.

Seems like the sentiment is overall positive for this proposal, could we maybe proceed with the voting process?

Once the open suggestions are addressed I can propose it.


Executing XLA compiled function inside tf.GradientTape context leads to extraneous GPU kernels and D2D copies

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04.3
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): v1.12.1-21967-gd80fda0 2.1.0-dev20200109
Python version: 3.6.9
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: CUDA Version 10.1.243 / cuDNN <IP_ADDRESS>-1
GPU model and memory: TITAN V, 12GB

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
I am trying to speed my code using tf.function decoration, with experimental_compile=True. I observe that my code indeed runs faster using this decoration, but executing the function within a tf.GradientTape() context seems to generate two GPU kernels instead of one, even though I am not computing any gradients. Moreover, executing the function inside of the tf.GradientTape() context produces two D2D copies, which are not present when executing outside of tf.GradientTape(). The following illustrates my point (the first kernel is running outside tf.GradientTape()and the second is running inside tf.GradientTape():

Describe the expected behavior
I am not sure if this behavior is expected or not. If it is not expected, I would certainly like it if there were less GPU kernel calls, leading to much faster code.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
import tensorflow as tf
from tensorflow.python import eager

def main():

    assert tf.executing_eagerly()

    gpus_p = tf.config.experimental.list_physical_devices('GPU')
    if gpus_p:
        try:
            # Currently, memory growth needs to be the same across GPUs
            for gpu in gpus_p:
                tf.config.experimental.set_memory_growth(gpu, True)
        except RuntimeError as e:
            # Memory growth must be set before GPUs have been initialized
            print(e)

    def tf_forward(x,xmax):
        return tf.quantization.fake_quant_with_min_max_vars(inputs=x,
                                                            min=-xmax,
                                                            max=xmax,
                                                            num_bits=8)

    tf_forward_tf_function = tf.function(func=tf_forward,
                                        experimental_compile=True)

    x = tf.random.uniform(shape=[3, 3, 96, 1])
    xmax = tf.Variable(0.5)

    tf_forward_tf_function(x,xmax)

    eager.profiler.start()
    for n in range(1000):
        x = tf_forward_tf_function(x,xmax)
        with tf.GradientTape() as tape:
            tape.watch(x)
            x = tf_forward_tf_function(x,xmax)

    profiler_result = eager.profiler.stop()
    eager.profiler.save('/test/log', profiler_result)

if __name__ == '__main__':
    main()

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Thanks for such a detailed bug report! I have a fix ready which removes the two extra D2D copies.

I'll mark the bug as fixed based on removing those extra copies. From what I understand, the fact that the kernel for gradient computation is launched regardless of whether derivative is used is just a property of eager runtime, and can not really be avoided (if you don't need the gradients => don't launch under the gradient tape).

Thank you! I apologize for the silly question, but how do I get the fix for the D2D copies?

You would have to wait for it to land after it passes internal testing.

Actually apologies, this was the incorrect commit, the proper fix has still not landed yet.


Error playing episodes: invalid audio file

Tried playing episodes of this podcast using this proxy using overcast on iOS.
The subscription went fine, but no files can be downloaded: the error message is invalid audio file.
Let me know if you need any more info.

Hmm, the link in the <enclosure> tag of the first episode is https://mediapolisvod.rai.it/relinker/relinkerServlet.htm?cont=DKGSblGDaPvCh9zKPSVAXAeeqqEEqualeeqqEEqual and for some reason it returns 403 when I try to access it with curl, but if I set -H 'User-agent: ' it correctly redirects to the audio file at https://creativemedia3-rai-it.akamaized.net/podcastcdn/Rai/audiocut/20866360_1800.mp4.
I think the relinker implements a check on the User-agent header and blocks it if it's not a browser or the raiplay app, so I assume Overcast makes a request with its own user agent and gets blocked by the relinker.
If this is the problem this I'd have to either:

make a request to each episode link while generating the RSS XML to resolve it to the correct audio file, which would increase loading time a lot
implement another endpoint to resolve the relinker links, and in the RSS XML change the <enclosure> links to this endpoint

Are there other podcasts that don't have this problem in Overcast? If there are, can you send me the links here?

I fixed this with the latest commit, if you're running your own server please update it. I'll be updating https://kirarin.hootr.club/sarasara/ tomorrow probably.


Replace '<' and '>' with "<" and ">" in code block

revealjs-codeblock/revealjs-codeblock.lua

Hey you know you don't have to close and re-open PR's to change their content right? If you need to tweak something just force push to the same branch that you opened the original PR from.
Crosslinking previous iterations: #110 and #112.

Hey you know you don't have to close and re-open PR's to change their content right? If you need to tweak something just force push to the same branch that you opened the original PR from.
Crosslinking previous iterations: #110 and #112.

I am not familiar with PR, it should be OK this time

Thank you!


Performance of format_with

We use format_with in our code.
module Grape
  class Entity
    format_with(:iso_timestamp) { |dt| dt.utc.iso8601 if dt }
  end
end

with_options(format_with: :iso_timestamp) do
    expose :created_at
    expose :updated_at
end

But when I saw newrelic.

So why format_with consume so much time?Any device for optimizing?
What about use cache method_missing to rewrite this method?

Sorry, I made a mistake.It's Grape::Middleware::Formatter#call,not format_with.It's reasonable for Grape::Middleware::Formatter#call to consume so much time, right?

So it's rendering of an entity to json, right? You should have more details inside that part and see what the breakdown there is. In a project we've switched rendering to oj for example and got a 30% improvement.

Newrelic plots like this one above are very familiar to me from my work.
Grape::Middleware::Formatter consumes large time, that's right. But note that this time is not only the time spent in the Grape::Middleware::Formatter code:

It's a Grape::Entity exposure logic that I'm trying to optimize.
It's also a  methods calls (done by Grape::Entity) to an object/objects you're representing. Every exposure is a method call to an object. This method calls could be heavy, especially if you use ActiveRecord (query building, etc). For example, we saved a lot of CPU time when switched to ElasticSearch (using Chewy).
And, of course, it's a JSON rendering.

So, all that stuff happens in just one middleware: Grape::Middleware::Formatter.
1 and 2 (and probably 3 too) could be optimized by introducing a cache layer, i'm working on this idea now.

FWIW we use Garner at API level and mongoid-cached-json for JSON rendering.

@dblock this is good, but Grape::Entity still lacks russian doll caching for nesting entities. This is something that could optimize rendering itself.

So it's rendering of an entity to json, right? You should have more details inside that part and see what the breakdown there is. In a project we've switched rendering to oj for example and got a 30% improvement.

@dblock Is that project open source? If so could you may be post a link?


[FEATURE] Version Bump to TS 5.5

TS 5.2 is now almost two years old, I'd appreciate a version bump of the peer dependency to the current version.

Thanks for the reminder, will be done by the end of the week!


Socket integration with Process

I'd be nice to have bidirectionnal intégration between socket and process modules.

which process opened this socket ?
which sockets open this process ?

For instance:
>>> host.socket('tcp://22').process
<process sshd (pid=17542)>
>>> host.process.get(pid=17542).sockets()
[<socket tcp://22>] # this object does not exist yet, it has to be defined

@philpep do you mind if I give. this a try ?


Example of using a custom IHttpWebRequestFactory with SolrNet.Core and SolrNet.Microsoft.DependencyInjection package

I cant find out how to use SolrNet.Core and the SolrNet.Microsoft.DependencyInjection package together, can anyone point me in the right direction.
I thought that maybe adding a connection into the provider or adding the IHttpWebRequestFactory would do the trick but it didnt. I cant find any other way to add credentials either. Below is an example of what I was trying
SolrConnection connection = new SolrConnection(silrUrl);
connection.HttpWebRequestFactory = _httpWebRequestFactory;
IServiceProvider provider = new ServiceCollection().AddSingleton<ISolrConnection>(connection).AddSingleton<IHttpWebRequestFactory>(_httpWebRequestFactory).AddSolrNet(solrT).BuildServiceProvider();
ISolrOperations<EmptySolrResponse> solr = provider.GetRequiredService<ISolrOperations<EmptySolrResponse>>();

See https://github.com/SolrNet/SolrNet/blob/master/Documentation/Initialization.md#microsoftextensionsdependencyinjection-aspnet-core
You have to register it using the AddSolrNet extension method: services.AddSolrNet("http://localhost:8983/solr");
After that you can get the service ISolrOperations<EmptySolrResponse> from the DI.

I am doing exactly that in my example and the link provided does nothing more then I had already done in my example. So I will now assume that SolrNet.Microsoft.DependencyInjection is incompatible with solr servers that require authentication.

That's exactly my problem: I can't find a way to use the above code to connect to a Solr Server that requires user credentials!

I really don't understand, why such an important subject like Authentication isn't covered in the Documentation! Any help will be much appreciated!


Release for Scala 2.13.0-M5

I guess depends on https://github.com/scala-stm/scala-stm/pull/5 first?

https://github.com/scala-stm/scala-stm/

Great!


refactor: Separate database integration from trie into its own crate

Closes #8514

perhaps we kick this off by extracting these:
https://github.com/paradigmxyz/reth/tree/01fd9b3c76705e582cea17774f269fe4a78d8af3/crates/primitives/src/trie
to trie-types instead and then try to move more stuff from reth-trie there?

Hey @mattsse, thank you for reviewing my PR so swiftly.
So far I've been thinking that crates:

reth-trie  - contains types and behavior of the Trie domain, but does not depend on a database, the concept of database does not really exist there. Should I rename it to reth-trie-types?
reth-trie-db - is a projection of the reth-trie into the database, but does not define any concepts of the Trie domain. It implements the traits defined by the Trie domain using reth_database. There might be other implementations than the reth_database. that's why the reth-trie-db shouldn't contain domain behavior or types, otherwise that would lead to duplication of knowledge.

I haven't looked into the primitives crate yet, so that's where I'll go next. It does make sense to pull the trie module out of that crate and put it into the reth-trie crate.

Superseded by #9282


Small updates typos and others

Solve:
#142
#148

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Verifying Clerk JWT

Hello, thank you for building this library for Cloudflare Workers.
Description
I'm trying to use this library to verify the authenticity of a session token with the public key. I am using Clerk for the sessionToken and JWT, which uses RS256.
const splitPem = JWT_VERIFICATION_KEY.match(/.{1,64}/g) as string[]
const publicKey = '-----BEGIN PUBLIC KEY-----\n' + splitPem.join('\n') + '\n-----END PUBLIC KEY-----'
const authorized = await jwt.verify(sessionToken, publicKey, {
   algorithm: 'RS256'
})

jwt.verify always returns false. Any pointers?

Was using the wrong JWT_VERIFICATION_KEY
Library works as expected!


writing style guide

Let's write one.
some links given here: https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source/issues/19 :
Nielsen, Jakob. 1997. ‘How Users Read on the Web’. Nielsen Norman Group (blog). 1 October 1997. https://www.nngroup.com/articles/how-users-read-on-the-web/.
‘Writing Digital Copy for Domain Experts’. n.d. Nielsen Norman Group. Accessed 17 November 2017. https://www.nngroup.com/articles/writing-domain-experts/.
Consider those for whom English is a second language, too.
https://meta.wikimedia.org/wiki/Writing_clearly
File to be found https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/WritingStyleGuide.md

copying slack information:
jennifer go on the coc
https://docs.google.com/document/d/1LOQRIH-NBb1m8sNQz7B8sdcCH55HeQOuTvjPXo6MKbw/edit#
resources:
The resources I am most familiar with on global English are just regular books, The Global English Style Guide: Writing Clear, Translatable Documentation for a Global Market by John Kohl and The Elements of International English Style by Edmond Weiss.
https://vlc.nccommunitycolleges.edu/faculty/accessibility/compliance-standards/
https://ec.europa.eu/info/sites/info/files/styleguide_english_dgt_en.pdf

this may goes with translation, with the first translation being "into international english" then we go to other languages.
NB: international english should be better translated by machines like deepl.com

Hi J,
Yes, OK its on my books :-) I'll assign some time block to this and get on with it. Thanks Simon

I found the file where you want the guide to be written - https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/WritingStyleGuide.md I'll get to it and pop up on slack


Support using pre-existing Android Studio Key

If a developer has Android Studio installed, we could use the developer key that Android Studio creates for them.
We would want to:

[ ] Have a look for the key in the default location for that OS.
[ ] Change our default key alias from android to androiddebugkey.
[ ] Either automatically use the default passwords or mention them to the user when prompting.

The default location and key set up can be found here.

In our case, we're not creating a debug key, and we should avoid using the debug key for deploying apps on Play.
That key we need to generate is either the upload key or the production key.

Ah, user error on my part - maybe it would be nice to explicitly disallow it as I was able to use my debug key by just pointing to the path and using the default passwords.

We need at least to show a warning.

Closing this, as using the default key is not recommended for security reasons.


wait-for-redis fails to detect redis with default image

OAuth2-Proxy Version
helm chart version 7.7.1
Expected Behaviour
Configuring the helm chart to work with the redis subchart should work with the default waitForRedis container image.
Current Behaviour
When configured to work with redis, the deployment never becomes healthy because the wait-for-redis initContainer just spins its wheels:
$ kubectl logs -f lee-oauth2-proxy-79cb74fcb9-2kdk9 -c wait-for-redis
Checking standalone Redis...
Checking Redis at lee-redis-master:6379... Elapsed time: 0s
Redis is down at lee-redis-master:6379. Retrying in 5 seconds.
Checking Redis at lee-redis-master:6379... Elapsed time: 5s
Redis is down at lee-redis-master:6379. Retrying in 5 seconds.
Checking Redis at lee-redis-master:6379... Elapsed time: 10s
Redis is down at lee-redis-master:6379. Retrying in 5 seconds.
...
Redis is down at lee-redis-master:6379. Retrying in 5 seconds.
Checking Redis at lee-redis-master:6379... Elapsed time: 145s

But redis seems to be up and healthy.
When I try to inspect whats going wrong, it looks to me like its trying to run netcat command to wait for redis, but it doesn't seem like the default image (bitnami/kubectl) defined by the chart even has netcat installed.
$ docker run -it --entrypoint "/bin/bash" bitnami/kubectl
I have no name!@818c61fb65df:/$ nc
bash: nc: command not found

Note that when I run the same helm deploy with initContainers.waitForRedis.enabled = false then the deploy succeeds.
However, I'd prefer to have this set to true because when its false the oauth2-proxy pod errors out and restarts a few times while redis is coming up.
Steps To Reproduce

with the latest version of the helm chart (7.7.1)
with sessionStorage.type = redis, redis.enabled = true, and initContainers.waitForRedis.enabled = true
perform the helm deploy and monitor the status

Possible Solutions
Use a different base image, such as alpine, that actually includes netcat.
Alternatively, update the check-redis.sh script to use an alternative command for checking that redis is listening.
Configuration details or additional information
Previously I was using version 6.23.1 of the helm chart and it was working with the same config.
I tried reviewing the release notes from 7.x and beyond, but couldn't tell if there is something I'm supposed to change or not.
Select snippets from my override.yaml:
  httpScheme: https
  service:
    appProtocol: https
    portNumber: 443
  extraArgs:
    # cookie_refresh > 0 requires oauth tokens in sessions. session_cookie_minimal cannot be set
    cookie-refresh: 10m
    cookie-expire: 30m
    redis-insecure-skip-tls-verify: "true"
  # refer to https://oauth2-proxy.github.io/oauth2-proxy/docs/configuration/alpha-config/
  alphaConfig:
    enabled: true
    ...
  sessionStorage:
    type: redis
  # use a redis subchart
  redis:
    enabled: true
    tls:
      enabled: true
      authClients: false
      autoGenerated: true
    master:
      affinity:
      persistence:
        enabled: false
      containerSecurityContext:
        runAsNonRoot: true
        allowPrivilegeEscalation: false
        readOnlyRootFilesystem: true
    replica:
      affinity:
      persistence:
        enabled: false
      containerSecurityContext:
        runAsNonRoot: true
        allowPrivilegeEscalation: false
        readOnlyRootFilesystem: true

when I override the waitForRedis image with the stock alpine image, it works just fine (with the same exact config):
  initContainers:
    waitForRedis:
      enabled: true
      image:
        repository: alpine

How do folks feel about changing the default?

@lmsurpre, the waitForRedis container already uses the Alpine image.
https://github.com/oauth2-proxy/manifests/blob/main/helm/oauth2-proxy/values.yaml#L308-L311
We switched two months ago with v7.5.0 Ref: https://github.com/oauth2-proxy/manifests/pull/197
I advise you to clean up the values.yaml file you use, starting from the default one of the latest version of the chart.

@lmsurpre, have you managed to solve your issue?

I am closing the issue due to a lack of feedback.
Please open a new one if the problem continues or everything needs clarification.


Log errors when offline

I'm getting errors when the sync server is not reachable that are polluting my terminal - is this just me? error sending request for url and some additional items?
Thanks for the project - use it multiple times a day!

Happy to hear you like Atuin!
Hmm those errors shouldn't be making their way to your terminal.
Just a couple of questions
What shell do you use?
How have you setup the atuin integration?

Hi,
Using fish shell on MacOS. Getting this sort of thing:

Integrating like this in fish.config:
    # Try https://github.com/ellie/atuin
    # dont bind to up arrow
    set ATUIN_NOBIND true
    atuin init fish | source
    # But bind to CTRL+R
    bind \cr _atuin_search

Hmm, I'm not to familiar with fish, but it does look like we are missing the /dev/null redirect that we use for bash/zsh. Maybe that's the issue

I can confirm. We are currently using &; disown to spawn the end command in the background, but my testing shows it still outputs the stdout/err. We just need to add &>/dev/null and it should be good

Resolved by #518


DevEnv takes a long time to initialize

Description
In order to build a Visual Studio Installer Project (.vdproj), Visual Studio must be ran via DevEnv.exe. When building the installer, it takes anywhere from 2-10. This appears to be regression from #128. I'm not sure when the regression initially occurred as this is the first time I needed DevEnv.
In the reproduction steps below, I use seanmiddleditch/gha-setup-vsdevenv@v4. This appears to be required to ensure the installer is built due to the behavior of DevEnv.exe. It seems likely that you may be able to start and wait for the DevEnv process to finish, but I doubt that will result in a faster build. This action does add a lot of clutter to the environment variables as well.
Unfortunately, all our repositories are private and can't be shared publicly. For troubleshooting, I attempted to test our Action against windows-2019 based on #128. I experienced the same issue, as mentioned in Actual Behavior.
Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[X] Windows Server 2019
[X] Windows Server 2022

Image version and build link
windows-2019 -> 20220316.1
windows-2022 -> 20220316.1
Is it regression?
Maybe, see description
Expected behavior
I expected about 20-30 seconds, but I'd be happy with less than 120 seconds.
Actual behavior
It takes at least 2 minutes to start DevEnv, but typically takes 5-10 minutes. The last two runs clocked in at 8:40 and 8:28 on windows-2022 and windows-2019, respectively.
Repro steps
name: DevEnv Test
on: workflow_dispatch
jobs:
  build:
    runs-on: windows-latest
    steps:
    - name: Setup MSBuild.exe
      uses<EMAIL_ADDRESS>
    - name: Setup VS Dev Environment
      uses: seanmiddleditch/gha-setup-vsdevenv@v4

    - name: Restore NuGet Packages
      run: msbuild /t:Restore

    - name: Build the application
      run: msbuild /t:Build /p:Configuration=Release

    # Required to Build VS Installer Projects
    - name: Disable Out of Process Building
      run: .\DisableOutOfProcBuild.exe
      working-directory: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\VSI\DisableOutOfProcBuild

    # Can take 10+ minutes to complete
    - name: Build the Installer
      run: DevEnv Installer/Installer.vdproj /build Release

Hello @MH-ZShearer ,
We will take a look at it.

Hello there, I have the same problem. Any progress?

Hello there, I have the same problem. Any progress?

Currently, no updates.

I'm also having the same problem. Initialization takes 10min on windows-2022.
Doing the exact same thing as @MH-ZShearer (building an installer)

In the same boat

Same on my side...

Same here. I'm building an installer with devenv and it can easily take 10+ minutes.

new image has been delivered.
I'm closing this issue, feel free to reopen if is still a concern

Thanks for taking your time, but I’m afraid it still takes very long before the project starts building.
I’ve just rebuilt my package.
The runner had version “2.305.0” and was using a Windows Server 2022 (10.0.20348).

Fri, 23 Jun 2023 11:50:28 GMT  Copyright (C) Microsoft Corp. All rights reserved.
Fri, 23 Jun 2023 11:50:28 GMT
Fri, 23 Jun 2023 11:50:28 GMT  The license for Visual Studio expires in 19 days.
Fri, 23 Jun 2023 11:50:28 GMT  Rebuild started...
As you can see, it again takes almost 7 minutes before VS creates its first output.
When I built the project 2 weeks ago on a runner version “20230606.1”, this was the output:
Mon, 12 Jun 2023 10:53:17 GMT           Run devenv.com $env:Solution_Name /rebuild "$env:Configuration|x86" /project $env:Installer_Project /log
Mon, 12 Jun 2023 11:00:01 GMT
Mon, 12 Jun 2023 11:00:01 GMT           Microsoft Visual Studio 2022 Version 17.6.2.
7 minutes.
Am I too impatient and have to wait for an image version newer than 20230612.1 (unfortunately, you didn’t mention what the “new” image version was) or didn’t the fix work as hoped for?
Best regards
Martin Müller
Von: ilia-shipitsin @.>
Gesendet: Freitag, 23. Juni 2023 13:32
An: actions/runner-images @.>
Cc: Martin Müller @.>; Comment @.>
Betreff: Re: [actions/runner-images] DevEnv takes a long time to initialize (Issue #5301)
new image has been delivered.
I'm closing this issue, feel free to reopen if is still a concern
—
Reply to this email directly, view it on GitHubhttps://github.com/actions/runner-images/issues/5301#issuecomment-1604152871, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AROFYVQ4RHLLZY35CGFZC63XMV5ELANCNFSM5R7UH7DA.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

it was a false alarm from my side.
I'll check next week

Ok, no problem.
Got a bit too excited :)
I'm looking forward to your next update.

Should be deployed now

Great, thank you so much!!

Mon, 26 Jun 2023 11:41:16 GMT	Copyright (C) Microsoft Corp. All rights reserved.
Mon, 26 Jun 2023 11:41:16 GMT	The license for Visual Studio expires in 24 days.
Mon, 26 Jun 2023 11:41:16 GMT	Rebuild started...
1:20 minutes is a lot better than the ~7 minutes it took before.
Thanks again!

I just had a build take 10mins to start up:

https://github.com/tgstation/tgstation-server/actions/runs/5382159227/jobs/9767199703

I've noticed no perceivable difference than before. It still takes several minutes to even start devenv. The last 3 runs took 6:23, 6:28, and 7:57 minutes each just to start devenv with the entire build taking roughly 3 minutes longer each.
@martinmueller4voice since it appears to be working for you, it may be possible that we're setting up our devenv a bit differently, if that can even make a difference. Does your workflow differ from my original post? Are you able to post at least the important parts of your workflow for comparison?

Hmmm - I don't know what's going on...
Those are the build durations for the last 3 builds:

The 6 1/2 minute run was the one that made me cheer.
But the build from last week took >10 minutes again, while everything I had changed was the tag.
The fast run was with runner Version: 20230620.1.0
The latest, slow run was with runner  Version: 20230625.1.0
So from my point of view, something changed between 20230620 and 20230625 that reverted the speedup again.

@martinmueller4voice , I've added "vdproj" warmup. Warmup itself is simple vdproj.
can you share your details ? some project that is slow

My projecct mainly contains those steps to build the setup project:
# Install the .NET 7 workload
- name: Install .NET
uses: actions/setup-dotnet@v3
with:
dotnet-version: 7.0.x
# Install GitVersion
- name: Install GitVersion
uses<EMAIL_ADDRESS>with:
versionSpec: '5.x'
# Setup NuGet
- name: Setup Nuget
uses<EMAIL_ADDRESS># Add  MSBuild to the PATH: https://github.com/microsoft/setup-msbuild
- name: Setup MSBuild.exe
uses<EMAIL_ADDRESS># Execute all unit tests in the solution
- name: Execute unit tests
run: dotnet test -c Debug # Or else it looks as if Release is selected and there the .vdproj cannot be loaded
# Setup devenv environment
- name: Setup VS Dev Environment
uses: seanmiddleditch/gha-setup-vsdevenv@v4
# Copy asp.net 7 x86 prerequisite Bootstrapper package
- name: Copy ASP.NET 7 x86 Bootstrapper package
run: dotnet run --project $env:SetupHelper
# Build installer
- name: Build installer
run: devenv.com $env:Solution_Name /rebuild "$env:Configuration|x86" /project $env:Installer_Project /log
As you can see, the last step is the first one where devenv is actually started.
With the exact same steps, the build using 20230620.1 took 1:19 min to start devenv.com:
Mon, 26 Jun 2023 11:39:57 GMT Run devenv.com $env:Solution_Name /rebuild "$env:Configuration|x86" /project $env:Installer_Project /log
Mon, 26 Jun 2023 11:41:16 GMT
Mon, 26 Jun 2023 11:41:16 GMT Microsoft Visual Studio 2022 Version 17.6.4.
The build using the 20230625.1 runner took 5:13 min again to start devenv.com:
Wed, 05 Jul 2023 12:36:31 GMT Run devenv.com $env:Solution_Name /rebuild "$env:Configuration|x86" /project $env:Installer_Project /log
Wed, 05 Jul 2023 12:41:44 GMT
Wed, 05 Jul 2023 12:41:44 GMT Microsoft Visual Studio 2022 Version 17.6.4.

Does this change based on the size of the runner we use or something? I am using larger 16 core runners for a build and when I just run devenv.exe /updateconfiguration it can take anywhere from like 1-2 minutes, up to as long as almost 20 mintes:

Is this expected behavior if the runner image already had this command run?
Runner information:
Current runner version: '2.306.0'
Runner name: 'win-server2022-latest-16core_155c5158a61a'
Runner group name: 'win-server2022-latest'
Machine name: 'runner'
Operating System
  Microsoft Windows Server 2022
  10.0.20348
  Datacenter
Runner Image
  Image: windows-2022
  Version: 20230716.1.0
  Included Software: https://github.com/actions/runner-images/blob/win22/20230716.1/images/win/Windows2022-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20230716.1

Images are the same, @maxim-lobanov any ideas?

Can I ask if this is closed because it's a known issue?

Since we already had short startup times at some point, I feel that getting this to work reliably is just a small step away, even though I cannot say for sure what @maxim-lobanov did exactly with those images.
I fear that, once it's a known issue, it will stay a known issue indefinitely.
Any other opinions?

I still see very long times (~5 min) to simple start a dev shell in github hosted runners. Is there any update on this?

Because there doesn't seem to be any progress, I thought I'd suggest using a local (self-hosted) runner.
Recently, I had to switch to a self-hosted runner because of new code signing requirements where you have to have a hardware module physically connected to the build machine.
Since this local runner doesn't have to be provisioned every time with a partially initialized VS, this can be a huge time saver.
And the best part: Self-hosted runners are not billed by minute.

Hi @martinmueller4voice, thanks for your reply! Unfortunately, one of the reasons to migrate to github actions was to avoid maintaining servers for CI, so we'd like to avoid self-hosted runners if we can.

Same problem here another 3 months later, builds with devenv.exe take at least 5-10minutes to start up on a Github runner....


RSD endpoint returns 'Page not found'

If you enable the RemotePublishing feature, this meta is added:
<link href="http://localhost:2918/xmlrpc/metaweblog/4sycaf2c49s4kxdmm421jda0cs/rsd" rel="EditURI" title="RSD" type="application/rsd+xml" />
but the url returns a 'Page not found'.
I don't understand why the request doesn't enter in the Rsd method of the RemotePublishingController in Orchard.Lists because in the startup.cs, there is this map routing instruction:
routes.MapAreaRoute(
                name: "RSD",
                areaName: "Orchard.Lists",
                template: "xmlrpc/metaweblog/{contentItemId}/rsd",
                defaults: new { controller = "RemotePublishing", action = "Rsd" }
            );

This controller is assigned to the Orchard.RemotePublishing feature, which is defined by another module.
This is not wrong (new feature in OC) but might have been broken at some point when we played with ShellFeatureApplicationPart.
This controller should be registered if the Orchard.RemotePublishing is enabled.
/cc @jtkech

Here my findings.

So, without [Feature("Orchard.RemotePublishing")] it works, otherwise it doesn't work.

In ModularApplicationModelProvider.OnProvidersExecuted() there is this line.
var controllerType = controller.ControllerType.AsType();
var blueprint = _provider.GetFeatureForDependency(controllerType);
if (blueprint != null)
{
  controller.RouteValues.Add("area", blueprint.Extension.Id);

Here i can see that the area we add for RemotePublishingController is Orchard.XmlRpc. This is not Orchard.Lists, this is the id of the extension to which the feature belongs.

I tried to use this area name when we define the route, but it doesn't work.

But, just for testing, if in the above code i use this.
  var id = controllerType.GetTypeInfo().Assembly.GetName().Name;
  controller.RouteValues.Add("area", id);

Then it works.

So, it seems that for a controller type, the area need to be related to the module in which it is defined. In O1, i couldn't find a module which defines a controller type with a feature attribute, this for a feature which doesn't belong to this module. Ok for other types, but not for controller types.

So, i could get it working just by doing the 2 following changes.

By using areaName: "Orchard.XmlRpc" for the map routing in Orchard.Lists startup.

But also by using area = "Orchard.XmlRpc" to register the link in ListPart.RemotePublishing.cshtml.

Best

For now that will do. This is a new feature with some very advanced scenario, I am ok with it.
Thanks @jtkech.


How to run auto format on save?

Description
The formatters runs exactly when I return to Normal mode(from insert mode). I would like to set it to run on the file save. Is there any way to do that? How can I turn off the auto formatters?
Neovim version
NVIM v0.6.1
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by builduser
Features: +acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/share/nvim"
Run :checkhealth for more info
Nvim-lspconfig version
No response
Operating system and version
Manjaro Linux on the 5.16 Kernal
Affected language servers
clangd
Steps to reproduce

Open a file and edit and make a mistake on purpose.
Go back to normal mode.

Actual behavior
The file gets formatted right when you get back to normal mode.
Expected behavior
No response
Minimal config
call plug#begin()
Plug 'ms-jpq/coq_nvim', {'branch': 'coq'} " for autocomplete
Plug 'neovim/nvim-lspconfig'
call plug#end()

" Lang Server Conf
lua << END
local coq = require "coq"
local servers = { 'clangd', 'rust_analyzer', 'tsserver', 'pyright', 'sumneko_lua', 'golangci_lint_ls', 'kotlin_language_server', 'bashls' }
for _, lsp in pairs(servers) do
    require('lspconfig')[lsp].setup(coq.lsp_ensure_capabilities {
    on_attach = on_attach,
    flags = {
      debounce_text_changes = 150,
    }
  })
end
vim.lsp.set_log_level('debug')
END

LSP log
https://gist.github.com/Moncheeta/3c9a4f33621d9f8ccaf15a425b2e1b9d

That's not a minimal config, you'll need to reproduce with our minimal config as indicated in the issue template. I can assure you the issue is in your configuration, as neovim does not automatically format, ever.

My bad. After further investigation, I found out that a plugin was doing it. Sorry!

My bad. After further investigation, I found out that a plugin was doing it. Sorry!

It would have been nice to tell which one and what you did change.

It was a long time ago. I remember that I removed some sort of auto save plugin.

I also had a similar issue, and I realized that I had in my config this autocommand:
    vim.api.nvim_create_autocmd("BufWritePre", {
        buffer = buffer,
        callback = function()
            vim.lsp.buf.format { async = false }
        end
    })


What is the state of the mempool development?

Which branch is the more advanced? master or MemPool?

HI mempool mostly complete, all the core mempool tests are passing
There are some todo's like witness and FeeRateLimiter, maybe some other minor stuff.

Thank you. I'll look at that.


Fix SQL in certain locales

I received bug reports of PRIMARY being compiled to prımary (dotless i), causing errors. Using the US locale for String.toLowerCase() should fix that.
Updated all dependencies (except for bintray release, seems to cause compilation errors with Shadow).

 You should sign our Contributor License Agreement in order to get your pull request merged.

Thanks for submitting! I would create 2 PRs as the changing the dependencies is not related to the issue fix, and if the commits are squashed it wouldn't appear as separate commits. Also please see the comments, just a few minor things. Thanks!

@npurushe No problem, fixed and split the dependency updates into pull request #96. Interesting that the Android Studio code style defaults are different from IntelliJ.

Looks good thanks!


map2, map3, etc

Would you mind adding such functions? It seems strange that they aren't in the stdlib...

Sure, I'll try to add them when I get a chance. They should be around I agree

I see that these are implemented, so I think this issue can be closed :)

Sweet, thanks to whoever merged that!


Should we install libc++.(dylib|so) into $PREFIX as well?

$ otool -l cquery
Load command 13
          cmd LC_LOAD_DYLIB
      cmdsize 48
         name @rpath/libclang.dylib (offset 24)
   time stamp 2 Thu Jan  1 08:00:02 1970
      current version 4.0.0
compatibility version 1.0.0
Load command 14
          cmd LC_LOAD_DYLIB
      cmdsize 48
         name @rpath/libc++.1.dylib (offset 24)
   time stamp 2 Thu Jan  1 08:00:02 1970
      current version 1.0.0
compatibility version 1.0.0
Load command 15
          cmd LC_RPATH
      cmdsize 80
         path @loader_path/../lib/clang+llvm-4.0.0-x86_64-apple-darwin/lib (offset 12)

There is a /usr/lib/libc++.1.dylib in my macOS, so it can still find one. Just not sure whether there are some compatibility problems.

PRs are welcomed. I do not have a Mac OS X for testing.
On Linux, libstdc++.so.6 is DT_NEEDED. The current installed files are not self-contained but those needed libraries can all be provided by the host system. libtinfo.so.5 requires tinfo 5 which does not exist on system distros (e.g. Arch Linux. ncurses5-compat-libs provides the lib)
Is libc++ used on Mac OS X?
%  readelf -d build/release/lib/clang+llvm-5.0.0-linux-x86_64-ubuntu14.04/lib/libclang.so.5 | grep NEEDED
 0x0000000000000001 (NEEDED)             Shared library: [libdl.so.2]
 0x0000000000000001 (NEEDED)             Shared library: [librt.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libtinfo.so.5]
 0x0000000000000001 (NEEDED)             Shared library: [libpthread.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libz.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libstdc++.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [ld-linux-x86-64.so.2]
`

libstdc++ and libc++ are two libraries that implement C++ standard library. On macOS, the default is the latter and it is bundled with macOS. On linux, the default is the former. I am just thinking about the compatibility problem that might occur.

On Linux and FreeBSD, symbol versioning is used, and ubuntu14.04 is a quite old distribution, its symbols are likely covered by newer glibc/libstdc++, so I do not worry much about version compatibility. https://people.freebsd.org/~deischen/symver/freebsd_versioning.txt . Does Mac OS X provide similar symbol versioning mechanism?

Hmmm i'm still learning this. Let's wait until this problem occur in real world.

The current rsync usage is terrible and it definitely should be improved... I guess it may break if paths contain quotes or space. waf also caches commands and the rsync command sometimes does not re-trigger.


Fix issue #579

Changed: handle case for vertices with textures and normals (e.g. 1/1/1).

Fixes #591.

Thanks!


"a=rtpmap:111 opus/48000/2"  parsed as "encoding: 2"

The SDP line a=rtpmap:111 opus/48000/2 is parsed as follows:
rtp: {
  codec: "opus",
  encoding: 2,
  payload: 111,
  rate: 48000
}

Why encoding: 2?

SDP RFC specifies.
 a=rtpmap:<payload type> <encoding name>/<clock rate> [/<encoding
         parameters>]

Fine. Thanks.


All the open pulls from exa

[ ] https://github.com/ogham/exa/pull/1221
[ ] https://github.com/ogham/exa/pull/1219
[ ] https://github.com/ogham/exa/pull/1210
[ ] https://github.com/ogham/exa/pull/1204
[ ] https://github.com/ogham/exa/pull/1202
[ ] https://github.com/ogham/exa/pull/1201
[ ] https://github.com/ogham/exa/pull/1199
[ ] https://github.com/ogham/exa/pull/1196
[ ] https://github.com/ogham/exa/pull/1194
[ ] https://github.com/ogham/exa/pull/1192
[ ] https://github.com/ogham/exa/pull/1191
[ ] https://github.com/ogham/exa/pull/1190
[ ] https://github.com/ogham/exa/pull/1188
[ ] https://github.com/ogham/exa/pull/1184
[ ] https://github.com/ogham/exa/pull/1178
[ ] https://github.com/ogham/exa/pull/1177
[ ] https://github.com/ogham/exa/pull/1175
[ ] https://github.com/ogham/exa/pull/1169
[ ] https://github.com/ogham/exa/pull/1165
[ ] https://github.com/ogham/exa/pull/1164
[ ] https://github.com/ogham/exa/pull/1162
[ ] https://github.com/ogham/exa/pull/1160
[ ] https://github.com/ogham/exa/pull/1156
[ ] https://github.com/ogham/exa/pull/1150
[ ] https://github.com/ogham/exa/pull/1149
[ ] https://github.com/ogham/exa/pull/1148
[ ] https://github.com/ogham/exa/pull/1146
[ ] https://github.com/ogham/exa/pull/1144
[ ] https://github.com/ogham/exa/pull/1141
[ ] https://github.com/ogham/exa/pull/1140
[ ] https://github.com/ogham/exa/pull/1136
[ ] https://github.com/ogham/exa/pull/1128
[ ] https://github.com/ogham/exa/pull/1121
[ ] https://github.com/ogham/exa/pull/1120
[ ] https://github.com/ogham/exa/pull/1119
[ ] https://github.com/ogham/exa/pull/1102
[ ] https://github.com/ogham/exa/pull/1100
[ ] https://github.com/ogham/exa/pull/1099
[ ] https://github.com/ogham/exa/pull/1094
[ ] https://github.com/ogham/exa/pull/1085
[ ] https://github.com/ogham/exa/pull/1070
[ ] https://github.com/ogham/exa/pull/1064
[x] https://github.com/ogham/exa/pull/1061
[ ] https://github.com/ogham/exa/pull/1057
[ ] https://github.com/ogham/exa/pull/1051
[ ] https://github.com/ogham/exa/pull/1049
[ ] https://github.com/ogham/exa/pull/1018
[ ] https://github.com/ogham/exa/pull/1006
[ ] https://github.com/ogham/exa/pull/981
[ ] https://github.com/ogham/exa/pull/975
[ ] https://github.com/ogham/exa/pull/960
[ ] https://github.com/ogham/exa/pull/941
[ ] https://github.com/ogham/exa/pull/908
[ ] https://github.com/ogham/exa/pull/880
[ ] https://github.com/ogham/exa/pull/872
[ ] https://github.com/ogham/exa/pull/869
[ ] https://github.com/ogham/exa/pull/867
[ ] https://github.com/ogham/exa/pull/861
[ ] https://github.com/ogham/exa/pull/857
[ ] https://github.com/ogham/exa/pull/855
[ ] https://github.com/ogham/exa/pull/797
[ ] https://github.com/ogham/exa/pull/786
[ ] https://github.com/ogham/exa/pull/370

For reference to anyone that lands at zetta here, but unaware of the upstream discussion that spurred this fork (README lacked link), there was a separate fork roughly at the same time, Eza: https://github.com/ogham/exa/issues/1139#issuecomment-1656702098
Seems this was discussed in: https://github.com/syphar/zetta/issues/2#issuecomment-1656714075
With issues being tracked similar to PRs above in this eza issue: https://github.com/cafkafk/eza/issues/65

Presently unclear if both projects will continue individually, or if eza will merge back into zetta afterwards (with exa PRs merged that exa can upstream if it resumes development), otherwise zetta (or eza) may diverge from that point onwards.


Uninstall will close your Hyper-V!!!!!

After uninstalling archwsl according to the document, my WSL failed to start. I thought there was a problem with my distribution, but after reinstalling a new distribution, I was surprised to find that WSL still couldn't start. Upon checking the settings, I discovered that Hyper-V had been turned off!!! Please point this out in the document, dear author.

for anyone who needs to uninstall, I'd suggest uninstalling with wsl --unregister Arch. Any reason why this wouldn't be enough?


Running tests fails with 401 when running on a BC25 sandbox container with AAD authentication

Describe the issue
When trying to run tests in the current sandbox container with country w1 and AAD authentication, it fails with a 401.
Scripts used to create container and cause the issue
$artifactUrl = Get-BCArtifactUrl -type Sandbox -select Current -country w1
$userName = "bcadmin"
$password = ConvertTo-SecureString -String "Passwordhere" -AsPlainText -Force
$credential = New-Object -TypeName "System.Management.Automation.PSCredential" -ArgumentList $userName, $password
$licenseFileUri = 'C:\Licenses\BC-License.bclicense'
$additionalParameters = @("--volume ""C:\Apps:C:\Agents""")
$aadUser = '' # EntraID user name
$aadPassword = '' # EntraID password
$aadcredential = ([PSCredential]::new($aadUser, (ConvertTo-SecureString -String $aadPassword -AsPlainText -Force)))
$bcAuthcontext = New-BcAuthContext -credential $aadcredential -tenantID $tenantId

New-BCContainer -accept_eula `
                -Credential $credential `
                -licenseFile $licenseFileUri `
                -artifactUrl $artifactUrl `
                -containerName bc `
                -auth AAD `
                -doNotCheckHealth `
                -memoryLimit 20G `
                -AadTenant $tenantId `
                -AadAppId $appId `
                -AadAppIdUri $appIdUri `
                -authenticationEMail $userPrincipalEmail `
                -updateHosts `
                -multitenant:$false `
                -includeTestToolkit `
                -includeTestLibrariesOnly `
                -additionalParameters $additionalParameters `
                -useBestContainerOS

Run-TestsInBCContainer -containerName bc -credential $credential -accessToken $bcAuthcontext.AccessToken -testSuite 'DEFAULT'

Full output of scripts
BcContainerHelper version 6.0.24
BC.HelperFunctions emits usage statistics telemetry to Microsoft
Running on Windows, PowerShell 5.1.19041.4894
Using Container
Connecting to http://localhost:80/BC/cs?tenant=default
CommunicationError : Response status code does not indicate success: 401 (Unauthorized).
at <ScriptBlock>, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 93
at AwaitState, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 222
at OpenSession, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 200
at Initialize, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 61
at ClientContext, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 20
at New-ClientContext, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\PsTestFunctions.ps1: line 48
at <ScriptBlock>, <No file>: line 58
at AwaitState, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 234
at OpenSession, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 200
at Initialize, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 61
at ClientContext, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 20
at New-ClientContext, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\PsTestFunctions.ps1: line 48
at <ScriptBlock>, <No file>: line 58
ClientSession State is Uninitialized (Wait time 10 seconds)

Exception Script Stack Trace:
at AwaitState, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 234
at OpenSession, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 200
at Initialize, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 61
at ClientContext, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\ClientContext.ps1: line 20
at New-ClientContext, C:\ProgramData\BcContainerHelper\Extensions\bc\PsTestTool\PsTestFunctions.ps1: line 48
at <ScriptBlock>, <No file>: line 58

PowerShell Call Stack:
at Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.24\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 71
at Run-TestsInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.24\AppHandling\Run-TestsInNavContainer.ps1: line 430
at <ScriptBlock>, <No file>: line 1

Container Free Physical Memory: 17.1Gb
Disk C: Free 122Gb from 127Gb

Services in container bc:
- MicrosoftDynamicsNavServer$BC is Running
- MSSQL$SQLEXPRESS is Running

Relevant event log from container bc:
- 20241003 12:50:20 - MicrosoftDynamicsNAVClientWebClient

  Category: Microsoft.IdentityModel.S2S.Extensions.AspNetCore.S2SAuthenticationHandler
  EventId: 0
  ConnectionId: 0HN73HE3S4D58
  RequestId: 0HN73HE3S4D58:00000001
  RequestPath: /BC/cs

  CorrelationId: 330e15c3-8e57-4c70-a767-0e22b0d10335
  Exception: Microsoft.IdentityModel.Tokens.SecurityTokenInvalidAudienceException: IDX10214: Audience validation failed. Audiences: 'https://api.businesscentral.dynamics.com'. Did
not match: validationParameters.ValidAudience: 'null' or validationParameters.ValidAudiences: 'null, dd395f20-2cf2-4e15-a4e3-2bf88691b000, null, dd395f20-2cf2-4e15-a4e3-2bf88691b000'.
     at Microsoft.IdentityModel.Tokens.Validators.ValidateAudience(IEnumerable`1 audiences, SecurityToken securityToken, TokenValidationParameters validationParameters)
     at Microsoft.IdentityModel.JsonWebTokens.JsonWebTokenHandler.ValidateTokenPayloadAsync(JsonWebToken jsonWebToken, TokenValidationParameters validationParameters, BaseConfigura
tion configuration)
     at Microsoft.IdentityModel.JsonWebTokens.JsonWebTokenHandler.ValidateJWSAsync(JsonWebToken jsonWebToken, TokenValidationParameters validationParameters, BaseConfiguration conf
iguration)
  Detailed stack trace is only included at verbose log level! To log full stack trace see https://aka.ms/sal/stacktrace-help.

- 20241003 12:50:20 - MicrosoftDynamicsNAVClientWebClient

  Category: Microsoft.IdentityModel.S2S.Extensions.AspNetCore.S2SAuthenticationHandler
  EventId: 0
  ConnectionId: 0HN73HE3S4D58
  RequestId: 0HN73HE3S4D58:00000001
  RequestPath: /BC/cs

  IDX10214: Audience validation failed. Audiences: 'https://api.businesscentral.dynamics.com'. Did not match: validationParameters.ValidAudience: 'null' or validationParameters.Val
idAudiences: 'null, dd395f20-2cf2-4e15-a4e3-2bf88691b000, null, dd395f20-2cf2-4e15-a4e3-2bf88691b000'.

at Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.24\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 113
at Run-TestsInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.24\AppHandling\Run-TestsInNavContainer.ps1: line 430
at <ScriptBlock>, <No file>: line 1
Run-TestsInBCContainer Telemetry Correlation Id: dc6c6e08-5e2c-4c45-b848-caad5197a581
ClientSession State is Uninitialized (Wait time 10 seconds)
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.24\AppHandling\Run-TestsInNavContainer.ps1:570 char:17
+                 throw $_.Exception.Message
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (ClientSession S...ime 10 seconds):String) [], RuntimeException
    + FullyQualifiedErrorId : ClientSession State is Uninitialized (Wait time 10 seconds)

Screenshots
none
Additional context
This happens all the time with the BC25 Sandbox container
It used to work 2 days ago when the current version was BC24.5

Could you supply the container generation log?

Also - can you login to the WebClient using AAD Auth?

Hi Freddy,
There were no issues compiling and publishing apps or logging in to the web client.
Here's the container generation log:
BcContainerHelper is version 6.0.24
BcContainerHelper is running as administrator
HyperV is Enabled
Host is Microsoft Windows 10 Pro - 10.0.19045.4894
UsePsSession is True
UsePwshForBc24 is True
UseWinRmSession is allow
UseSslForWinRmSession is True
Docker Client Version is 23.0.1
Docker Server Version is 23.0.1
Removing Session bc
Removing container bc
Removing entries from hosts
Removing bc from container hosts file
Removing bc-* from container hosts file
Removing Desktop shortcuts
Removing C:\ProgramData\BcContainerHelper\Extensions\bc
Fetching all docker images
Fetching all docker volumes
Using image mcr.microsoft.com/businesscentral:ltsc2019
Disabling Health Check (always report healthy)
Creating Container bc
Style: sandbox
Multitenant: No
Version: 25.0.23364.25044
Platform: 25.0.24985.0
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.17763.6054 (ltsc2019)
Host OS Version: 10.0.19045.4894 (22H2)
Using hyperv isolation
Using locale en-US
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file C:\NavOne\Licenses\BC24-License.bclicense
Additional Parameters:
--volume "C:\work\NavOne:C:\Agents"
--expose 5986
--env customNavSettings=ValidAudiences=dd395f20-2cf2-4e15-a4e3-2bf88691b000;https://api.businesscentral.dynamics.com,DisableTokenSigningCertificateValidation=True,ExtendedSecurityT
okenLifetime=24,ClientServicesCredentialType=NavUserPassword
--env customWebSettings=AadApplicationId=dd395f20-2cf2-4e15-a4e3-2bf88691b000,AadAuthorityUri=https://login.microsoftonline.com/domain.com
Files in C:\ProgramData\BcContainerHelper\Extensions\bc\my:
- AdditionalOutput.ps1
- AdditionalSetup.ps1
- HelperFunctions.ps1
- license.bclicense
- MainLoop.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container bc from image mcr.microsoft.com/businesscentral:ltsc2019
b5d188c1b4f05316867dc028cd0d30e858b5b0fafe2435b4c4e66789a88a8f2a
Waiting for container bc to be ready
Using artifactUrl https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/sandbox/25.0.23364.25044/w1
Using installer from C:\Run\240
Installing Business Central: multitenant=False, installOnly=False, filesOnly=False, includeTestToolkit=False, includeTestLibrariesOnly=False, includeTestFrameworkOnly=False, includ
ePerformanceToolkit=False, appArtifactPath=c:\dl\sandbox\25.0.23364.25044\w1, platformArtifactPath=c:\dl\sandbox\25.0.23364.25044\platform, databasePath=c:\dl\sandbox\25.0.23364.25
044\w1\BusinessCentral-W1.bak, licenseFilePath=c:\dl\sandbox\25.0.23364.25044\w1\Cronus.bclicense, rebootContainer=True
Installing from artifacts
Starting Local SQL Server
Starting Internet Information Server
Copying Service Tier Files
c:\dl\sandbox\25.0.23364.25044\platform\ServiceTier\Program Files
c:\dl\sandbox\25.0.23364.25044\platform\ServiceTier\System64Folder
Copying Web Client Files
c:\dl\sandbox\25.0.23364.25044\platform\WebClient\Microsoft Dynamics NAV
Copying ModernDev Files
c:\dl\sandbox\25.0.23364.25044\platform
c:\dl\sandbox\25.0.23364.25044\platform\ModernDev\program files\Microsoft Dynamics NAV
Copying additional files
Copying ConfigurationPackages
C:\dl\sandbox\25.0.23364.25044\platform\ConfigurationPackages
Copying Test Assemblies
C:\dl\sandbox\25.0.23364.25044\platform\Test Assemblies
Copying Extensions
C:\dl\sandbox\25.0.23364.25044\w1\Extensions
Copying Applications
C:\dl\sandbox\25.0.23364.25044\platform\Applications
Copying dependencies
Importing PowerShell Modules
Restoring CRONUS Demo Database
Setting CompatibilityLevel for CRONUS on localhost\SQLEXPRESS
Modifying Business Central Service Tier Config File for Docker
Creating Business Central Service Tier
Installing SIP crypto provider: 'C:\Windows\System32\NavSip.dll'
Starting Business Central Service Tier
Importing license file
Stopping Business Central Service Tier
Installation took 116 seconds
Installation complete
Initializing...
Setting kubernetes.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting host.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to <IP_ADDRESS> in container hosts file
Starting Container
Hostname is bc
PublicDnsName is bc
Using AccessControlService Authentication
Creating Self Signed Certificate
Self Signed Certificate Thumbprint 216D170A742D452E73BD2DFC495744C239090165
DNS identity bc
Modifying Service Tier Config File with Instance Specific Settings
Modifying Service Tier Config File with settings from environment variable
Setting ValidAudiences to dd395f20-2cf2-4e15-a4e3-2bf88691b000;https://api.businesscentral.dynamics.com
Setting DisableTokenSigningCertificateValidation to True
Setting ExtendedSecurityTokenLifetime to 24
Setting ClientServicesCredentialType to NavUserPassword
Starting Service Tier
Registering event sources
Creating DotNetCore Web Server Instance
Using application pool name: BC
Using default container name: NavWebApplicationContainer
Copy files to WWW root C:\inetpub\wwwroot\BC
Create the application pool BC
Create website: NavWebApplicationContainer without SSL
Update configuration: navsettings.json
Done Configuring Web Client
Modifying Web Client config with settings from environment variable
Setting AadApplicationId to dd395f20-2cf2-4e15-a4e3-2bf88691b000
Setting AadAuthorityUri to https://login.microsoftonline.com/domain.com
Enabling Financials User Experience
Using license file 'c:\run\my\license.bclicense'
Import License
Creating http download site
Setting SA Password and enabling SA
Creating bcadmin as SQL User and add to sysadmin
WARNING: This license is not compatible with this version of Business Central.
Creating SUPER user
WARNING: This license is not compatible with this version of Business Central.
WARNING: This license is not compatible with this version of Business Central.
Enable PSRemoting and setup user for winrm
Creating self-signed certificate for winrm
Container IP Address: <IP_ADDRESS>
Container Hostname  : bc
Container Dns Name  : bc
Web Client          : http://bc/BC/
Dev. Server         : http://bc
Dev. ServerInstance : BC
Setting bc to <IP_ADDRESS> in host hosts file

Files:
http://bc:8080/ALLanguage.vsix

WARNING: You are running a container which is 73 days old.
Microsoft recommends that you always run the latest version of our containers.

Container Total Physical Memory is 20.5Gb
Container Free Physical Memory is 17.4Gb

Initialization took 46 seconds
Ready for connections!
Reading CustomSettings.config from bc
Creating Desktop Shortcuts for bc
Synchronizing Permissions Mock on default
App successfully synchronized
Installing Permissions Mock on default
App successfully installed
Synchronizing Test Runner on default
App successfully synchronized
Installing Test Runner on default
App successfully installed
Synchronizing Any on default
App successfully synchronized
Installing Any on default
App successfully installed
Synchronizing Library Assert on default
App successfully synchronized
Installing Library Assert on default
App successfully installed
Skipping app 'C:\Applications\TestFramework\TestLibraries\permissions mock\Microsoft_Permissions Mock.app' as it is already installed
Synchronizing Library Variable Storage on default
App successfully synchronized
Installing Library Variable Storage on default
App successfully installed
Publishing C:\ProgramData\BcContainerHelper\Extensions\bc\669c031d-e58e-4944-8dac-651488d58da8\Microsoft_System Application Test Library.app
Synchronizing System Application Test Library on tenant default
Installing System Application Test Library on tenant default
App Microsoft_System Application Test Library.app successfully published
Publishing C:\ProgramData\BcContainerHelper\Extensions\bc\ab36cd6b-fe04-4ea0-9f7e-3ed22a5de63c\Microsoft_Business Foundation Test Libraries.app
Synchronizing Business Foundation Test Libraries on tenant default
Installing Business Foundation Test Libraries on tenant default
App Microsoft_Business Foundation Test Libraries.app successfully published
Publishing C:\ProgramData\BcContainerHelper\Extensions\bc\96d2024d-4684-4e0f-ae9f-a8be35fc2958\Microsoft_Tests-TestLibraries.app
Synchronizing Tests-TestLibraries on tenant default
Installing Tests-TestLibraries on tenant default
App Microsoft_Tests-TestLibraries.app successfully published
Synchronizing AI Test Toolkit on default
App successfully synchronized
Installing AI Test Toolkit on default
App successfully installed
TestToolkit successfully imported
Cleanup old dotnet core assemblies
Container bc successfully created

Use:
Get-BcContainerEventLog -containerName bc to retrieve a snapshot of the event log from the container
Get-BcContainerDebugInfo -containerName bc to get debug information about the container
Enter-BcContainer -containerName bc to open a PowerShell prompt inside the container
Remove-BcContainer -containerName bc to remove the container again
docker logs bc to retrieve information about URL's again

When you say that this worked with 24.5 - did you use another AAD App or did you not specify any scopes for New-BcAuthContext ?
The default scope for New-BcAuthContext is api.businesscentral.dynamics.com/.default (which is for online)
Since the audience validation fails - I assume your scope or AAD app is wrong?

Basically, nothing in the pipelines changed between Tuesday (current is 24.5) and Wednesday (current is 25.0), so it seems to be the BC25 has changed.
I am trying to help investigate where I can, and can see some differences between the Microsoft.Dynamics.Framework.UI.Client.dll files in C:\bcartifacts.cache\sandbox\25.0.23364.25044\platform\Test Assemblies and C:\bcartifacts.cache\sandbox\24.5.23489.25038\platform\Test Assemblies:
For instance, JsonHttpClient.cs in that dll file has a new AgentTaskIdentifierHeaderName header, not sure if it was intentional or for testing only.
Not sure if that is a factor at all, but there is definitely quite a few changes in that dll file, which is referenced in ClientContext.ps1 to help with authentication before running tests.

I have a repro scenario here - will contact the team

Apparently in BC25, there is a new setting in navsettings.json, which needs to be set to Valid Audience.
"AadValidAudience": "https://api.businesscentral.dynamics.com"
Will fix this in ContainerHelper.

Thanks for the quick response. I've added it as a workaround until the new version is released:
Invoke-ScriptInBcContainer -containerName bc -scriptblock {
    Set-NAVWebServerInstanceConfiguration -WebServerInstance BC -KeyName AadValidAudience -KeyValue 'https://api.businesscentral.dynamics.com'
}

Fix is in BcContainerHelper preview as well.


[web] Added basic shim to prevent crashing

What issue is this PR fixing?

https://github.com/expo/expo/issues/8585

How did you test this PR?

I eyeballed it

LGTM


[Bug]: render-engine init not rendering cli arguments correctly

Summary Of Actions
When I initialize a template with title and description it doesn't convert the template to the correct python code.
It should be
{
"SITE_TITLE" : "Hello world",
"SITE_DESCRIPTION" : "simple site for testing"
}

Not
{
SITE_TITLE : "Hello world",
SITE_DESCRIPTION : "simple site for testing"
}

Operating System
Windows
What Python Version are you using?
Python 3.10
Have you installed Plugins/Themes/Custom Parsers?
NO
What did you enter to get the output that you recieved?
render-engine init --owner-name="John Aziz"<EMAIL_ADDRESS>--title="Hello world" --site-description="simple site for testing"

Output
app.site_vars.update({
    SITE_TITLE:"Hello world",
    SITE_DESCRIPTION:"simple site for testing",
    "OWNER":{
        "name": "John Aziz",
        "email"<EMAIL_ADDRESS>    },
    "NAVIGATION":[
        {
            "name": "Home",
            "url": "/",
        },
        {
            "name": "Collection Page",
            "url": "/example-page.html",
        }
    ]
    })app.site_vars.update({
    SITE_TITLE:"Hello world",
    SITE_DESCRIPTION:"simple site for testing",
    "OWNER":{
        "name": "John Aziz",
        "email"<EMAIL_ADDRESS>    },
    "NAVIGATION":[
        {
            "name": "Home",
            "url": "/",
        },
        {
            "name": "Collection Page",
            "url": "/example-page.html",
        }
    ]
    })

In the upcoming 2024.1.1 release we switch this init completely to cookiecutter which means these steps will not work as you believe.

@kjaymiller Note that the fix is only available using the github release the pypi release is still at 2023-10-4
To get the update I used this command to install render engine if anyone faces the same issue:
pip install git+https://github.com/render-engine/render-engine.git#egg=render-engine


Ollama support doesn't work as shown in docs

Example in "docs/lmms.md" shows code as:
import vision_agent as va

model = va.lmm.get_lmm("llava")
model.generate("Describe this image", "image.png")

which shows the following error:
Traceback (most recent call last):
  File "/mnt/d/coding/Testing/vision-agents/agent.py", line 9, in <module>
    model = va.lmm.get_lmm("llava")
            ^^^^^^^^^^^^^^
AttributeError: module 'vision_agent.lmm' has no attribute 'get_lmm'

I'm using the 0.2.109 version.

I changed the code as:
import vision_agent as va

model = va.lmm.OllamaLMM("llava:7b")
response = model.generate(prompt = "Describe this image", media=["jar.png"])
print(response)

and the changed the lmm.py as the following:
# stream = stream.json()
# return stream["message"]["content"]

response = stream.content.decode('utf-8')
json_objects = response.strip().split('\n')
parsed_data = []
for obj in json_objects:
    parsed_data.append(json.loads(obj))

res = ''.join(obj['response'] for obj in parsed_data)
return res

Because earlier stream.json() was showing the following error:
Traceback (most recent call last):
  File "/home/lzytitan/miniconda3/envs/test/lib/python3.11/site-packages/requests/models.py", line 962, in json
    return complexjson.loads(self.content.decode(encoding), **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/lzytitan/miniconda3/envs/test/lib/python3.11/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/lzytitan/miniconda3/envs/test/lib/python3.11/json/decoder.py", line 340, in decode
    raise JSONDecodeError("Extra data", s, end)
json.decoder.JSONDecodeError: Extra data: line 2 column 1 (char 99)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/mnt/d/coding/Testing/vision-agents/agent.py", line 4, in <module>
    response = model.generate(prompt = "Describe this image", media=["jar.png"])
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/lzytitan/miniconda3/envs/test/lib/python3.11/site-packages/vision_agent/lmm/lmm.py", line 448, in generate
    stream = stream.json()
             ^^^^^^^^^^^^^
  File "/home/lzytitan/miniconda3/envs/test/lib/python3.11/site-packages/requests/models.py", line 970, in json
    raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Extra data: line 2 column 1 (char 99)

Now this works fine for me, I tested it 10 times with different images and prompt. But is it really the correct way to solve this?

Hey @lzytitan494 , thanks for bringing these issues up. On the first post, that is some old documentation I've forgotten to remove, your second post is how you should query the Ollama model.
There's a bug in generate where I don't explicitly pass stream=False if it's not streaming. I'll have a PR up today that fixes this as well as adds better Ollama support for VisionAgent.

This PR should fix the issue and also adds OllamaVisionAgentCoder class https://github.com/landing-ai/vision-agent/pull/208

Yes, I have checked the updated llm.py file it works fine. Thank you.


Inlay Hints Color Change in v0.2.12

In v0.2.12, the color of the inlay hints has shifted to a green tone that feels visually unappealing.
Current appearance in v0.2.12:

For comparison, here is how they appeared in v0.2.11:

I typically don't enable inlay hints personally, but have for the past few days. I agree: doesn't look too nice 😅 I'll rollback.


Fix Presto bitwise_shift_left function

Bitwise_shift_left function has a bug where if the bits field is 64 it right shifted instead of left shifted. This PR fixes this bug.

@pedroerp Yes validated this with presto.


Switch to php-cs-fixer

We currently use https://github.com/squizlabs/PHP_CodeSniffer for formatting. I have been annoyed with it because:

it keeps messing up complex types in PHPDocs (e.g. https://github.com/webonyx/graphql-php/pull/1016#discussion_r756812057)
the way it aligns some code is nearly impossible to do right manually
alignment leads to ugly diffs
configuration options are very hard to discover
XML-based configuration is clunky

I propose we switch to https://github.com/FriendsOfPHP/PHP-CS-Fixer instead. I am using it in a lot of projects and have not had much issues with it at all. It addresses the above mentioned pain points:

it deals fine with complex types (e.g. https://github.com/nuwave/lighthouse/blob/04a74cc6bbc6e592de988096a890958ebe112a4e/src/Schema/AST/DocumentAST.php#L40)
my code is mostly fine the way i type it
it is easily configured to left-align everything
https://mlocati.github.io/php-cs-fixer-configurator
PHP-based configuration is nice and composable

👍🏼
from my side.
Whilst I'm happy both projects are maintained, my impression is that with PHP adaptions, adjustments, release cadence and whatnot makes a healthy project, next to the technical things pointed out, php-cs-fixer is in a better state.
My experience is similar and I propose it also in many projects working on.
This combined with a CI webhook to auto-add a commit reduces developer friction a lot.

FWIW: It would be great to move forward with this, as currently phpcs/phpcbf don't work at all:
vendor/bin/phpcbf
ERROR: Referenced sniff "Doctrine" does not exist

Run "phpcbf --help" for usage information


The image size should be configurable

The image size should be tunable/configurable. Currently, it's rather small. As an example beneath, the size of a map image is too small to recognize any relevant details:

Saemi as comparison:

Do you think the server response should contain the size of the image?
Irrespective of that we can have a max image size as a widget initialization
setting.


Improve license parsing

Fixes https://github.com/ros-infrastructure/superflore/issues/271
Corresponding changes for catkin_pkg:
https://github.com/ros-infrastructure/catkin_pkg/pull/296

@shr-project Friendly ping; what's the status of this PR?  It is still marked as "Draft".

@shr-project Friendly ping; what's the status of this PR? It is still marked as "Draft".

@clalancette It depends on https://github.com/ros-infrastructure/catkin_pkg/pull/296 which wasn't merged yet

@shr-project friendly ping.

@hidmic I'm sorry, I don't have the test environment for this anymore and don't work on meta-ros (where the license parsing changes were already applied through superflore).
Someone else will need to pick this up or close, sorry.

There hasn't been any progress in a long time, so I will close the PR.
@shr-project if you or someone else are planning to pick this up feel free to reopen or open a new PR.


dotnet run

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/run
Operating System: macos
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant

The "Hello World" string is not displayed on my terminal.

@ceana8 You appear to be missing the cd MyApp which is the second instruction on the previous (create) tutorial:  https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/create

Let us know if the tip from @bartonjs helps you to continue


pkg/compiler: deduplicate Types in descriptions

Add prog.Ref Type that serves as a proxy for real types
and allows to deduplicate Types in generated descriptions.
The Ref type is effectively an index in an array of types.
Just before serialization pkg/compiler replaces real types
with the Ref types and prepares corresponding array of real types.
When a Target is registered in prog package, we do the opposite
operation and replace Ref's with the corresponding real types.
This brings improvements across the board:
compiler memory consumption is reduced by 15%,
test building time by 25%, descriptions size by 33%.

The diff coverage is 68.21%.

@@            Coverage Diff             @@
##           master    #1694      +/-   ##
==========================================
+ Coverage   56.41%   56.62%   +0.20%
==========================================
  Files         148      148
  Lines       27574    27518      -56
==========================================
+ Hits        15557    15583      +26
+ Misses      11225    11147      -78
+ Partials      792      788       -4

Impacted Files
Coverage Δ

pkg/build/netbsd.go
0.00% <0.00%> (ø)

prog/types.go
73.15% <26.47%> (-8.05%)
:arrow_down:

prog/target.go
66.66% <88.88%> (+3.09%)
:arrow_up:

pkg/compiler/gen.go
94.21% <95.65%> (+0.11%)
:arrow_up:

pkg/compiler/compiler.go
93.90% <100.00%> (+0.09%)
:arrow_up:

pkg/serializer/serializer.go
75.52% <100.00%> (+14.91%)
:arrow_up:

tools/syz-trace2syz/parser/strace.go
41.55% <0.00%> (-19.38%)
:arrow_down:

prog/rand.go
88.64% <0.00%> (+0.36%)
:arrow_up:

tools/syz-trace2syz/parser/lex.go
93.88% <0.00%> (+2.63%)
:arrow_up:

Continue to review full report at Codecov.

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


fromEvent() should emit error when NodeJS EventEmitter emits error event

error events are special in NodeJS. They make the process crash if there is no handler for them. That makes them the standardised event name for any error, be it on a stream, socket, child process or custom event emitters.
As a user, if I want to convert a stream into an Observable for example:
Observable.fromEvent(net.connect(1234), 'data')

I would expect a socket error to be emitted as an Observable error, so I can handle it with operators (like reconnect etc). Instead, a socket error would crash the process.
https://nodejs.org/api/events.html#events_error_events

But it is very specific to node IMHO.
You can create your own factory function by wrapping Observable.fromEvent with Observable.defer and handle the error case there (maybe by merging normal events with error events).

Yep, it is specific to node. But so is bindNodeCallback, and fromEvent is documented as handling NodeJS EventEmitters specifically. The use case for wrapping NodeJS EventEmitters is huge.

@MidnightWonderer that's what I figured at first, but @felixfbecker is right, we do say we support it.
It should be easy enough to add the new behavior given the code is already forking at node based emitters.  I imagine we just need to add something like sourceObj.addListener('error', subscriber.error.bind(subscriber));

yep, it would just need a
sourceObj.once('error', err => subscriber.error(err))

What if you are creating multiple observables off the same EventEmitter?
const socket = net.connect(1234);
const data$ = Observable.fromEvent(socket, 'data');
const drain$ = Observable.fromEvent(socket, 'drain');

Do we want the same error to be sent to both observables?

@felixfbecker I would be more comfortable with the following which uses a merge to add in the error logic:
const event$ = Observable.merge(
  Observable.fromEvent(socket, 'data'),
  Observable.fromEvent(socket, 'error').mergeMap(x => Observable.throw(x))
);

Otherwise, feel free to move forward some of the rx-node project from v4

The proper answer here is to use the above suggestion.
In RxJS 6+, that would be something like this:
import { merge, fromEvent } from 'rxjs';
import { tap } from 'rxjs/operators';

const event$ = merge(
  fromEvent(socket, 'data'),
  // convert error events to errors.
  fromEvent(socket, 'error').pipe(tap(err => { throw err; }));
);


Remove bytecode files and add more exclusions

Python bytecode files were removed, I also added more exclusions from gitignore.io to the .gitignore file.
Tell me if you would like to port this code to python3 too. I could help you with that.

Thank you for pull request :)
Um.. I wanted to port it to python3 but I so busy..


Scribble doesnt work for instrumenting libraries

Given the following sample:
library Foo {
        /// #if_succeeds $result == 1;
        function foo() internal returns (uint) {
                return 1;
        }
}

Scribble will produce code that looks like this:
...
library Foo is __scribble_ReentrancyUtils {
function foo() internal returns (uint RET_0) {
        RET_0 = _original_Foo_foo();
        unchecked {
            if (!(RET_0 == 1)) {
                emit AssertionFailed("0: ");
                assert(false);
            }
        }
    }
...

This doesn't compile as libraries can't inherit from other contracts. The only reason that inheritance is there is to provide the AssertionFailed event. We should special-case this and add that event directly to libraries when they need instrumentation.
Note that we also need to introduce an error message whenever a user tries to define a constant on a library - as that also is currently stored in the utils contract.

Fixed by #189


Private registry push api fail : "BLOB_UPLOAD_INVALID"

I search how to push for using registry v2 api(https://docs.docker.com/registry/spec/api/#completed-upload).
I received 202 Accepted code about all 'Chunk Upload', but I get this error message in 'Completed Upload' step.
[root@user:/root/test] curl -X PUT -v \
>   http://localhost:5000/v2/redis/hello/blobs/uploads/4eac9236-d1eb-4048-8572-89b9371033ce?_state=Wi...J9?digest=sha256:e8f2305ed6ac0d5e2c79349c3129bca7ec32497bad23336e59f8ee3d793473db \
>   -H "Content-Type: application/octet-stream"

* About to connect() to localhost port 5000 (#0)
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 5000 (#0)

> PUT /v2/redis/hello/blobs/uploads/4eac9236-d1eb-4048-8572-89b9371033ce?_state=Wi...J9?digest=sha256:e8f2305ed6ac0d5e2c79349c3129bca7ec32497bad23336e59f8ee3d793473db HTTP/1.1
> User-Agent: curl/7.29.0
> Host: localhost:5000
> Accept: */*
> Content-Type: application/octet-stream
>
< HTTP/1.1 404 Not Found
< Content-Type: application/json; charset=utf-8
< Docker-Distribution-Api-Version: registry/2.0
< X-Content-Type-Options: nosniff
< Date: Tue, 26 Feb 2019 10:40:51 GMT
< Content-Length: 89
<
{"errors":[{"code":"BLOB_UPLOAD_INVALID","message":"blob upload invalid","detail":204}]}
* Connection #0 to host localhost left intact

What does the error code '204(sometimes code : 208)' mean?
And.. where can I get proper digest value in this case?

After reading the documentation I think you forgot the header part:
Content-Length: <size of chunk>
Content-Range: <start of range>-<end of range>

Maybe I am wrong but in your curl command this part is missing.

I solved this problem.
That value is about URL parameter length. Maybe.. It is a problem about parameter length.
So I used '--data' and '-G' option in using PUT parrameter :D

hi @bluefriday
I have the same problem.
here is my code
curl -X PUT -v -H "Authorization: Bearer $token" -H "Content-Type: application/octet-stream" -H "Content-Length: $size" --data-binary @"50670****bfbe56/layer.tar" $location?digest=sha256:d2*******4675
Can u share curl command for uploading layer?

hello @btsken
My curl for the PUT action is:
curl -v -X PUT -G \
   -H "Content-Type: application/octet-stream" \
   -T 726*****f9e \
   --data "digest=sha256:726*****f9e" \
   --data "_state=koE***D%3D" \
   http://localhost:5000/v2/nginx/blobs/uploads/4****b18-****-****-****-1d31a84****0

I hope it helps.
If you need further sharing, please leave a comment.

It works.
Thank you very much!


Add documentation to KeyCode for Mac users

Objective
KeyCode::*Win and KeyCode::*Alt might be confusing for some Mac users.
Solution
Added some small documentation to clarify the mappings for those developing on a Mac.
Additional Context
Related issue: #3240

bors r+


Kubernetes README

See discussion on #1103, this is just that with squashed commits.

Fixed weird, erroneous commit.

If this is just docs, can it be merged?

@anners Sure!

@siddharthist
I will push some more updates and make new PR soon.
I missed the part when you get your K8's cluster up and running and log in to the mater kubectl command would not work as it needs to be configure to consume /etc/kubernetes/kubectl.config file.

Sorry for the typo :-(   and thanks for merging this

This still needs review from another team member.


Bump hamcrest/hamcrest to 2.0-dev

Refs #464

Tests pass, so I guess it does solve the problem.
Or maybe we have some code left that orders auto-loader of PHPUnit and Hamcrest to play along? If that is the case, then we need to remove that and use new method, that autoloads Hamcrest global functions where needed in test suite of Mockery.

I don't think mockery's test suite was affected, as it only comes in to play if people manually attempt to load phpunit's assert functions.

Any chance this could be reverted. Getting this when running composer update:
Problem 1
    - mockery/mockery dev-master requires hamcrest/hamcrest-php ^2.0@dev -> no matching package found.

@warrickhill what version of composer are you using? Do you have a custom repository set up for hamcrest?

I have just run
You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug
Updating to version 593b88e41487f481d4368a4d331146914c1c2981.
    Downloading: 100%
Use composer self-update --rollback to return to version 03299ff075236be27be356498d6c64def973fe41```

I am getting the problem on both versions. composer install also doesn't work.

No i'm not using a custom repo for hamcrest

@warrickhill Do you have "minimum-stability": "dev" set?  It won't pull through if you're set to stable only

Ah yeah, that would be the problem. I think you'll need to adjust the minimum-stability setting, or manually require hamcrest/hamcrest-php: "^2.0@dev" for now

both those solutions have worked. I think we will have to manually require hamcrest for now. thanks

min stability dev, then prefer stable true is often a good combination

https://github.com/CachetHQ/Cachet/blob/v2.0.4/composer.json#L102-L103


Update README.md to include project info and setup steps.

Update README.md to include Project information, how to setup project, how to contribute, project tech stack, list of moderators to approach help for specific issue. Modify current README.md and remove redundant data.
Basic Techincal Info

Project Based on React JS
We would be using Yarn to setup the project.
Tech Stack would include React JS, PostgreSQL for now.

EDIT :- List of moderators to approach would be shared shortly.

For the list of moderators to contact can I use the one that was given on the discord server?

Sure

Whatever was present in the README beforehand, is to be removed or not?

Put your content at the top, and refractor the already content upto yarn
build, remove everything below that and put inside the rest inside a
"contribution section".
On Tue, 23 Mar, 2021, 2:06 pm Ayush Shukla, @.***>
wrote:

Whatever was present in the README file beforehand, is to be removed or
not?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LNMIIT-CODING/stonks-frontend/issues/1#issuecomment-804719799,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQRHA5TT7OSX5ASGSKNNZJLTFBHILANCNFSM4YXS5P7Q
.

@Ayush-Shukla02
Steps to contribute:

Fork the repo
Take up an issue
Write code
Commit changes in a new branch
Make a PR

Yes I have made the necessary changes till now in the forked repo. Once completed I will make PR. Or if you say I can make one now to show the current status.
@AkMo3

Yup, it would be better

I have made the PR

Also check and verify whether the mods' and members' list needs any changes.