Error when using Exim "sendmail"

I get the following error:
A message that you sent using the -t command line option contained no
addresses that were not also on the command line, and were therefore
suppressed. This left no recipient addresses, and so no delivery could
be attempted.
------ This is a copy of your message, including all the headers. ------
Date: Wed, 09 Jun 2010 00:22:26 +1200
From: samuel.williams@NOSPAM
To: samuel@NOSPAM
Message-ID: 4c0e360234e31_3554241c2728745db@NOSPAM
Subject: Website Contact: Moo
Mime-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Testing

Oh man I just spent 2-3 hours debugging this issue.
The exim conf fix did it for me:
extract_addresses_remove_arguments = false
@mikel any idea if these fixes will go into the core gem? Thanks!

Hi, just thought I'd add my 2c. From the exim man page:

-t        When Exim is receiving a locally-generated, non-SMTP message on its standard input, the -t option causes the recipients of the message to be obtained from the To:, Cc:, and Bcc: header lines in the message instead of from the command arguments. The addresses are extracted before any rewriting takes place and the Bcc: header line, if present, is then removed.
             If the command has any arguments, they specify addresses to which the message is not to be delivered. That is, the argument addresses are removed from the recipients list obtained from the headers. This is compatible with Smail 3 and in accordance with the documented behaviour of several versions of Sendmail, as described in man pages on a number of operating systems (e.g.  Solaris 8, IRIX 6.5, HP-UX  11).  However,  some versions  of Sendmail add argument addresses to those obtained from the headers, and the O'Reilly Sendmail book documents it that way. Exim can be made to add argument addresses instead of subtracting them by setting the option extract_addresses_remove_arguments false.

The easiest way to fix this in rails is simply to
config.action_mailer.sendmail_settings = {
  :arguments => "-i"
}

However in the long run, mail should either remove the -t option, or not specify the recipients on the command line (I think this is the better choice)

add pull request https://github.com/mikel/mail/pull/296

Thank you, timsjoberg. This is really a difficult-to-track bug. You don't know what to suspect when there are several possible culprits. Just to confirm, both extract_addresses_remove_arguments = false in exim's configuration and arguments => "-i" is what is needed for it to work. I really was nuts on this one.

Hi all, I have added an Exim deliver manager in commit #632c05e  This is currently in master.
Please let me know if this handles your issues as I don't use Exim.

I was hit by this yesterday and spent hours figuring out the problem; pretty daunting if you just want to install some random RoR app and emails don't work because of this. I know https://github.com/mikel/mail/issues/70#issuecomment-3489405 suggest a new driver, but I'd like to point out timsjoberg excellent analysis at https://github.com/mikel/mail/issues/70#issuecomment-2639987 , a conclusion to which I ultimately came to.
Maybe there's a easier way to have a Sendmail transport configuration which is more compatible out there?
thanks for considering

@mfn did you see my comment immediately above yours?  I have added a separate Exim driver in the latest Mail gem.

@mikel : yes I did; I wasn't ignorant, sorry if that sounded so.
My stance is: I'm wondering if it really needs it's own "driver" when it's just about, maybe (needs thorough investigation), the order or about the parameter which could be changed to work with exim and still be compatible with sendmail and others (I was under the assumption that exims' sendmail link is meant to be compatible).
Because whether it's a configuration like timsjoberg suggested or a new driver: the user will be surprised it doesn't work out of the box. Why the surprise? Usually the application on the system "just work" with the local MTA without special handling.
Just wanted to better describe my point, I'm not arguing against your fix.
thanks

@mfn Oh OK, that makes sense.
What would actually be cool is an update to the README describing how to set up with Exim.  Would you be able to craft this?


No matching handler?

I've been using Stetho for a while now on various projects, using 1.5.0
When I open up dev tools on chrome while the app is running, Logcat spews out the following message and doesn't show up as a device on //inspect
W/stetho: I/O error: java.io.IOException: No matching handler, firstByte=71
2-3 times a second
Seems unique considering I haven't found any threads related to this message

I got the same error. After some inspection, I found this may because of the missing .enableWebKitInspector(Stetho.defaultInspectorModulesProvider(context)) line. see https://github.com/facebook/stetho#custom-dumpapp-plugins

Ugh yup, thanks @huww98


Add instructions to remove virtual keyboard in README.md

Every time I set up this, I had to lookup the instructions to remove the virtual keyboard... so I thought it would be helpful to those who also lookup the same info.

Well done!

Well done!


A few game related services and tweaks

Once again, here are some details on less intuitive commits:

AMotionEventAction::down_time is used to better understand and respond to complex touch gestures.
Serialization caches are accessed in the game WBTW to selectively delete data from the memory.
ThinGame::tick is basically a counter of the current game logic frame. This value must be modified externally in mutliplayer games or sometimes when deserializing a game.
ImprovedNoise can be useful in the lib, from experience it gives a better result that our current noise algorithms and it is in 3D. However it has less customization options.
EulerCamera::camera_to_world is used to translate mouse position to in-world 3D coordinates in simple games viewed from directly above or from the side, like SDO and Action Nitro.

+1


Move Configuration annotation from internal to public API

This should probably always have been public as it's expected to be used in 3rd party rule sets.

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

  Generated by :no_entry_sign: dangerJS against 4353c97bca53f7f83f9786608ae7d55ac402af0e

Is this really the case? What are the benefits for 3rd party rule authors to use the annotation. It is only used to generate the documentation for the 1st party rules. Or am I missing something?

It is only used to generate the documentation for the 1st party rules

It should be available for third party rules to use as well so they can also generate documentation.


Examples page

Hey all,
This is a initial draft of an examples page. Doesn't have a finished example yet.
There are a couple of different places we can draw some inspiration from.

https://threejs.org/examples/
https://docs.pmnd.rs/react-three-fiber/getting-started/examples
https://examples.deno.land/

Category names can easy change over time as the list grows.
For this PR, I thought before making examples we give give some thought to the following:

what examples could live on this page (made in repo, svelte REPL, codesandbox or other)
whether or not a resource should live within the repo i.e. big models/textures
any other questions / concerns

I'm not sure how to make the PR collaborative so that others can make examples along side this one (so the live site doesn't have placeholder content ...or is deploying / updating the website a separate sub-command?)

Closing as we'll be working on #131


python exception 'CommunicationUserIdentifier' object has no attribute 'identifier'

I'm following the quickstart for the "Create an Identity" section, and I'm getting an exception when attempting to print the identifier property of the created CommunicationUserIdentifier object
'CommunicationUserIdentifier' object has no attribute 'identifier'

Looking at the reference docs here
https://azuresdkdocs.blob.core.windows.net/$web/python/azure-communication-identity/1.0.0/index.html#creating-a-new-user
I see, the way to get this property is to use the properties['id'] accessor.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a29430c6-fd84-c423-db14-4f87853dc5d6
Version Independent ID: 99605c52-055e-8361-4540-2527fd0ad342
Content: Quickstart - Create and manage access tokens - An Azure Communication Services quickstart
Content Source: articles/communication-services/quickstarts/access-tokens.md
Service: azure-communication-services
GitHub Login: @tomaschladek
Microsoft Alias: tchladek

Hi @darkorm , thanks for your feedback! We will review and update this doc accordingly.

@darkorm thank you very much for your feedback. We have updated the public documentation.

Thanks for updating the doc @tomaschladek .  We will now proceed to close this thread.


Cant load or save map

I tried to load a map of the latest version but reading the main page i realized that it cant read this map version. So i will have to use another map viewer.

Would you mind dropping a world download so we can look into this?

Tried to zip and upload but didn't accept. Sorry for the delay. Didnt read the email.
https://drive.google.com/file/d/15ES_1hPPjpVDDOaH9XhdfqEsJDm4M7Hy/view?usp=sharing

Having a very similar issue, I can't load any worlds from my local files, nor do the file -> Example map selections work...


How are static routes generated for the sitemap?

Are static routes generated manually? If so, would adding them to the python script and then outputting all the routes to the same                   sitemap.xml file be equivalent?

Short answer: yes.
The static routes are generated by hand. They're saved to an XML file.
There's no reason why the sitemap has to be divided into 2 files. I just chose to do it that way. Equivalently, all of the URLs could be in on file.
Yes, alternatively the Python script could produce a single sitemap XML file with all of the "static" and dynamic (those which depend on the content in the database) paths.

Great. I made a change to the generation in #1824  and also added the routes for the simulator standards.
Let me know if there are any issues.

I glanced. It looks good. Google will complain if it isn't.
Thanks for including the routes for the standards pages.
Ideally, the whole sitemap would be dynamically generated from the application. I couldn't figure out a way to do it. With enough effort I'm sure we could figure out a way, but with relatively little effort we can get 95% of the way to automating the sitemap. The static routes just have to be manually updated.


(Not BUG) The "..." class can't have an empty ID attribute when flexEnabled is "true".

Is there anyway of just disable this warnings?

It is not an error from this linter.


Vulnerability roundup 98: genann-1.0.0: 2 advisories [9.8]

search, files

[ ] CVE-2018-13996 CVSSv3=9.8 (nixos-unstable)
[ ] CVE-2018-13997 CVSSv3=7.5 (nixos-unstable)

Scanned versions: nixos-unstable: 257cbbcd3ab.
Cc @IvarWithoutBones

These have long been fixed.

These have long been fixed.


Add Python library to format trackbacks in Python

Add a simple Python library to set up Python development environment.
Also,

Enable Python lint checks with pylint and yapf.
Enable continuous build with travis-ci.

Yu, thank you for the setup!
Just a few nitpicks.

Could you please fold the small fixup commit (e.g. using git rebase -i) to keep a commit as a meaningful unit of change?
Could you please add documentation for all command-line flags you are adding (I spotted one with empty doc string)
Could you please add a section to README file that would describe the development/testing scenario that your change enables?

Could you please fold the small fixup commit (e.g. using git rebase -i) to keep a commit as a meaningful unit of change?

I think we can "Squash and merge" commits when you merge my PR:
https://help.github.com/en/articles/about-pull-request-merges#squash-and-merge-your-pull-request-commits
But I'm happy to squash them on my side.

Could you please add documentation for all command-line flags you are adding (I spotted one with empty doc string)
Could you please add a section to README file that would describe the development/testing scenario that your change enables?

Added more docs and comments.


Double free when calling bv.file.close() from API with certain binaries

This seems like it only happens with Fat Mach-O files.

Fixed in 1.2.1972-dev


Feat: Create Instructions to run the node and deploy in local blockchain

Create Instructions to development purpose

How to run local node
How to deploy smart contracts in local node

Closing this issue to fix the branch
#17 New Branch


Detect whether a cell has a formula in it.

Detect whether a cell has a formula in it. Which I feel is easier to

@MathNya i was looking into the code, I can see that this already implemented.

@agentjill
Thank you for your confirmation.
I will now close this issue.


Blocking on pending requests despite block == false

I am using the litellm client to benchmark a HuggingFace TGI server.
In token_benchmark_ray.py, req_launcher.get_next_ready() is called periodically to fetch pending results, with the block parameter set to False.
However, the call is actually blocking until all pending requests are complete, which can be very long if I set a high number of concurrent requests (typically 128).
The result is that instead of continuously injecting new requests as they complete, the benchmark script instead sends a batch of max_concurrent_requests, waits for them to complete, then sends another batch.
Is this the expected behaviour ? I double-checked why the call is blocking and from the code in request launcher this seems to be the normal behaviour because it only checks if there are still requests in the ray actor pool.

I have the same issue with you. (https://github.com/ray-project/llmperf/issues/56)
I think the get_next_ready function should return the result as soon as the request is finished in nonblock mode.


It can't load DigiTimes' feed

Description
tuifeed fails to load DigiTimes news feed
Steps to reproduce
Add https://www.digitimes.com/rss/daily.xml feed and run tuifeed
"DIGITIMES" = "https://www.digitimes.com/rss/daily.xml"

Expected behaviour
Load the feed and list feed contents.
Error shown
tuifeed show the following error
Could not fetch feed "DIGITIMES": HTTP request failed: https://www.digitimes.com/rss/daily.xml: Connection Failed: An existing
connection was forcibly closed by the remote host. (os error 10054)

Environment

OS: Windows 10 x64
Architecture x86_64
Rust version: ?
tuifeed version: 0.1.0

The reason is related to the TLS protocols used by the website, which are incompatible with rustls. Unfortunately this is not working even when switching go native-tls, so there's nothing I can do.


Cosmos prefix removal from *Response

Based on customer feed back and naming standards we will remove Cosmos prefix from  *Response

@kirankumarkolli
There is already a FeedResponse that is used by the v2 implementation that cause a name conflict. I'm going to do the following for any conflicts I find. Rename old response FeedResponse->DocumentFeedResponse; CosmosFeedResponse -> FeedResponse.


destructuring-assignment is too greedy. Should only apply within components.

I enabled this rule and immediately ran into issues within files that aren't React related, nor do they look like a component. For example:
I had to rename these to properties instead of props: https://github.com/milesj/shapeshifter/commit/52e33fed6c5386f80ffffa3a270e6d6fd9997b05#diff-392ca8d88bc7e496ea34c73c8cc8258c
Had to disable this line because it thought context was React related: https://github.com/milesj/boost/blob/master/tests/Routine.test.js#L825
And all of these errors when pulled into another project. None of which is React.
/Users/Miles/Sites/beemo/packages/core/src/Beemo.ts
  188:23  error  Must use destructuring context assignment  react/destructuring-assignment
  221:73  error  Must use destructuring context assignment  react/destructuring-assignment
  244:41  error  Must use destructuring context assignment  react/destructuring-assignment

/Users/Miles/Sites/beemo/packages/core/src/CleanupRoutine.ts
  25:7  error  Must use destructuring context assignment  react/destructuring-assignment

/Users/Miles/Sites/beemo/packages/core/src/configure/CreateConfigRoutine.ts
   49:34  error  Must use destructuring context assignment  react/destructuring-assignment
   55:5   error  Must use destructuring context assignment  react/destructuring-assignment
  124:21  error  Must use destructuring context assignment  react/destructuring-assignment
  124:46  error  Must use destructuring context assignment  react/destructuring-assignment

/Users/Miles/Sites/beemo/packages/core/src/driver/RunCommandRoutine.ts
   43:26  error  Must use destructuring context assignment  react/destructuring-assignment
   73:5   error  Must use destructuring context assignment  react/destructuring-assignment
  214:24  error  Must use destructuring context assignment  react/destructuring-assignment
  215:25  error  Must use destructuring context assignment  react/destructuring-assignment
  241:11  error  Must use destructuring context assignment  react/destructuring-assignment
  268:20  error  Must use destructuring context assignment  react/destructuring-assignment
  269:47  error  Must use destructuring context assignment  react/destructuring-assignment

/Users/Miles/Sites/beemo/packages/core/src/ExecuteScriptRoutine.ts
  25:32  error  Must use destructuring context assignment  react/destructuring-assignment

/Users/Miles/Sites/beemo/packages/core/src/SyncDotfilesRoutine.ts
  36:32  error  Must use destructuring context assignment  react/destructuring-assignment

I see that you're checking for a component, but perhaps TS is conflicting.

It’s possible that our component detection breaks with the TypeScript parser. Do the errors still occur if the files are converted to regular JS?

I also see that this only seems to complain about context; so maybe there’s a specific bug around that facet of the rule.

I'll try and double check JS only files, will be a bit tough.

Every single file in my project is now errors - no react imported or used anywhere close.

@bradennapier that's a separate issue (and definitely a bug) - can you file that as a separate issue?

Maybe this temporary solution works. add following line in "rules"
"react/destructuring-assignment": [true, { "extensions": [".jsx"] }],
but It may also occur again with some other eslint-plugin-react rules later, in .js file.
I want to restrict eslint-plugin-react warning only in .jsx file. I don't know how to.


ktlint forces single-line raw string to new line when used as named argument

Expected Behavior
The following code should lint without complaints:
fun myFun(regexp: String) {}

fun exampleCall() {
    myFun(regexp = """^[^\s@]+@[^\s@]+\.[^\s@]+$""")
}

Observed Behavior
ktlint complains with the following error:
/path/to/Example.kt:4:19: Missing newline after "=" (indent)

ktlint format will then reformat the code to:
fun myFun(regexp: String) {}

fun exampleCall() {
    myFun(regexp =
            """^[^\s@]+@[^\s@]+\.[^\s@]+$""")
}

This is slightly annoying on its own, but then this bug seems to interact with other indentation issues (possibly #764 or #805) where IDEA and ktlint's formatting rules don't match each other. IntelliJ IDEA's formatter (with the default applyToIDEAProject settings) will reformat the file to:
fun myFun(regexp: String) {}

fun exampleCall() {
    myFun(
        regexp =
        """^[^\s@]+@[^\s@]+\.[^\s@]+$"""
    )
}

Which then causes another complaint from ktlint:
/path/to/Example.kt:6:1: Unexpected indentation (8) (should be 12) (indent)

Subsequent ktlint/IDEA formats will cycle between these two indentations.
Steps to Reproduce
The above code sample should suffice for reproduction.
Your Environment

Version of ktlint used: 0.38.1
Name and version (or code for custom task) of integration used): Gradle plugin 9.4.0
Version of Gradle used (if applicable): 5.6.2
Operating System and version: Mac OS X 10.15.6 x86_64

Related Issues
I know #764, #805, and some other issues cover bugs around the new indent rule. I couldn't tell immediately whether this issue should be folded into one of those or stand on its own. I think an important distinction is that, regardless of the bugs ktlint has around formatting multi-line raw strings, the main problem I want to cover with this ticket is that a short raw string should be allowed to be on a single line when used as a named argument.
Additionally, I think this bug is another good reason to prioritize #631. I wouldn't mind this bug nearly as much if I had a simple way to ignore it the indent rules for a given line or block.

While doing a workaround for this (extracting my raw string to a variable, so I could pass the variable instead of it being defined inline), I noticed ktlint also turns:
const val EMAIL_RE = """^[^\s@]+@[^\s@]+\.[^\s@]+$"""

Into:
const val EMAIL_RE =
    """^[^\s@]+@[^\s@]+\.[^\s@]+$"""

I'm not sure if this is a bug or intentional (I can't find any style guide reference indicating raw strings should be defined on their own line). Thankfully, IDEA doesn't try to reformat that line, so it still works as a workaround for now.

This was fixed in 0.39.0, please check out the latest version

Ah, apologies for the duplicate; ktlint-gradle still defaults to 0.38.1 and I didn't think to check if it was the newest!


stack_llama: update instructions in README and fix broken _get_submodules

The parameter names for merge_peft_adapetr.py are out of date in the README
LlamaModelForCausalLM does not have an attribute _get_submodules

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

Also save tokenizer in merge_peft_adapter.py

Wow, you are super quick! Thanks

I'd like to say thank you for putting this repo together. I have been concerned about the likes of ChatGPT taking away the ability to fine-tune models for specific tasks and this is a great piece of work towards democratizing NLP.

Also save tokenizer in merge_peft_adapter.py

same problem, but my peft==0.3.0


Add AutoPlay & USB notifications options

Hi, I thought these could be useful to have in your script.
I added an option to disable & restore AutoPlay + disable USB notifications which could annoy users of Windows - it should get rid of Scan and Fix which happens on every USB Drive known to mankind. The code for Scan and Fix has been broken for many years now..

Wow, i didn't even think about this annoying issues, Thanks for contributing


Handle missing qubit properties in Target generation

Summary
This commit handles and edge case in the Target object generation when
building a backend object. Some backends are missing T1, T2, and
frequency for some (or all) qubits. To handle this edge case we
shouldn't fail if they're missing just simply not populate the
properties on that qubit. These are optional properties and are not
required to build a Target, so if they're missing on the API response
payload we can just exclude them from the output Target object.
Details and comments

Looks good - I can update this in qiskit-ibm-runtime too


Podman now looks like a dependency in the RPM installation

What happened:
Install is suddenly failing when the Podman binary is not found, it was working 24 hours ago. There has been only one commit merged since then and it's possible it may be related to If a service stops with error request all the other services to stop but I'm not even sure that would be reflected in the RPM install yet.
I'm installing from nerdalert/microshift-installer using the RPM install instructions.

Below are the logs:

Jan 31 01:53:49 cluster-b systemd[2096]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Jan 31 01:53:49 cluster-b systemd[1]: microshift.service: Main process exited, code=exited, status=203/EXEC
Jan 31 01:53:49 cluster-b systemd[2097]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Jan 31 01:53:49 cluster-b systemd[2097]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Jan 31 01:53:49 cluster-b systemd[1]: microshift.service: Control process exited, code=exited, status=203/EXEC
Jan 31 01:53:49 cluster-b systemd[1]: microshift.service: Failed with result 'exit-code'.
Jan 31 01:53:49 cluster-b systemd[1]: Failed to start MicroShift Containerized.
Jan 31 01:53:50 cluster-b systemd[1]: microshift.service: Scheduled restart job, restart counter is at 5.
Jan 31 01:53:50 cluster-b systemd[1]: Stopped MicroShift Containerized.
Jan 31 01:53:50 cluster-b systemd[1]: microshift.service: Start request repeated too quickly.
Jan 31 01:53:50 cluster-b systemd[1]: microshift.service: Failed with result 'exit-code'.
Jan 31 01:53:50 cluster-b systemd[1]: Failed to start MicroShift Containerized.

Ive only been digging into Microshift the past couple of days and haven't looked into if there is any e2e spun up yet. Would like to contribute if I can be of assistance getting some rolling if there isn't any.
How to reproduce it (as minimally and precisely as possible):

running the script linked and commenting out the Podman install (I have added Podman as a workaround)
or using the RPM instructions on the website

Anything else we need to know?:

If Podman is a requirement, I will update the rpm install docs.

Environment:

Fedora 35
VirtualBox 4xcore 4BG mem
Microshift version:
MicroShift Version: 4.8.0-0.microshift-2022-01-06-210147
Base OKD Version: 4.8.0-0.okd-2021-10-10-030117

Thanks!

Hi @nerdalert, thanks for giving MicroShift a try!
In your script you're installing MicroShift via RPM, which creates the microshift.service for you that you can then start. No need for Podman for this.
From your log output, I suspect you may have tried deploying MicroShift on Podman on the same machine and overwritten the microshift.service file doing so?
I'm going to close this issue as not-a-bug. If you believe this is incorrect, please feel free to reopen.

We have a microshift-containerized service in the rpm for convenience, don't use that service just the plain "microshift"

Thanks for the assist @mangelajo @fzdarsky!
Just to double check, here is what I am installing for the RPM install per the QuickStart instructions. This is a fresh Fedora install that I'm snapshotting for a fresh OS every time I have installed. The microshift.service file that gets put installed is the one containing the Podman startup.
Are the install commands I'm using below wrong? Thanks!
sudo dnf module enable -y cri-o:1.21
sudo dnf install -y cri-o cri-tools
sudo systemctl enable crio --now

sudo dnf copr enable -y @redhat-et/microshift
sudo dnf install -y microshift firewalld
sudo systemctl enable microshift --now

# no microshift.service file
brent@cluster-a:~$ ls /usr/lib/systemd/system/ | grep micro
brent@cluster-a:~$

# Install
brent@cluster-a:~$ sudo dnf module enable -y cri-o:1.21
sudo dnf install -y cri-o cri-tools
sudo systemctl enable crio --now
[sudo] password for brent:
Fedora 35 - x86_64 - Updates                                                                                41 kB/s |  13 kB     00:00
Fedora 35 - x86_64 - Updates                                                                                1.1 MB/s | 5.0 MB     00:04
Fedora Modular 35 - x86_64 - Updates                                                                                69 kB/s |  14 kB     00:00
Dependencies resolved.
===============================================================================================================================================================================================================================
 Package                                               Architecture                                         Version                                                Repository                                             Size
===============================================================================================================================================================================================================================
Enabling module streams:
 cri-o                                                                                1.21

Transaction Summary
===============================================================================================================================================================================================================================

Complete!
Last metadata expiration check: 0:00:06 ago on Tue 01 Feb 2022 12:01:25 PM EST.
Dependencies resolved.
===============================================================================================================================================================================================================================
 Package                                                     Architecture                           Version                                                              Repository                                       Size
===============================================================================================================================================================================================================================
Installing:
 cri-o                                                       x86_64                                 1.21.3-1.module_f35+13330+6bc9c749                                   updates-modular                                  23 M
 cri-tools                                                   x86_64                                 1.19.0-1.module_f35+12974+2bc66b5d                                   updates-modular                                 6.1 M
Installing dependencies:
 conmon                                                      x86_64                                 2:2.0.30-2.fc35                                                      fedora                                           56 k
 container-selinux                                           noarch                                 2:2.173.1-1.fc35                                                     updates                                          49 k
 containernetworking-plugins                                 x86_64                                 1.0.1-1.fc35                                                         fedora                                          8.7 M
 containers-common                                           noarch                                 4:1-32.fc35                                                          updates                                          76 k
 criu                                                        x86_64                                 3.16.1-2.fc35                                                        updates                                         529 k
 fuse-common                                                 x86_64                                 3.10.5-1.fc35                                                        fedora                                          8.3 k
 fuse3                                                       x86_64                                 3.10.5-1.fc35                                                        fedora                                           54 k
 fuse3-libs                                                  x86_64                                 3.10.5-1.fc35                                                        fedora                                           92 k
 libbsd                                                      x86_64                                 0.10.0-8.fc35                                                        fedora                                          104 k
 libnet                                                      x86_64                                 1.2-4.fc35                                                           fedora                                           57 k
 libslirp                                                    x86_64                                 4.6.1-2.fc35                                                         fedora                                           72 k
 runc                                                        x86_64                                 2:1.0.2-2.fc35                                                       fedora                                          3.1 M
 socat                                                       x86_64                                 <IP_ADDRESS>-1.fc35                                                       updates                                         302 k
Installing weak dependencies:
 fuse-overlayfs                                              x86_64                                 1.7.1-2.fc35                                                         fedora                                           72 k
 slirp4netns                                                 x86_64                                 1.1.12-2.fc35                                                        fedora                                           55 k

Transaction Summary
===============================================================================================================================================================================================================================
Install  17 Packages

Total download size: 42 M
Installed size: 212 M
Downloading Packages:
(1/17): fuse-common-3.10.5-1.fc35.x86_64.rpm                                                                                50 kB/s | 8.3 kB     00:00
(2/17): conmon-2.0.30-2.fc35.x86_64.rpm                                                                                234 kB/s |  56 kB     00:00
(3/17): fuse3-3.10.5-1.fc35.x86_64.rpm                                                                                232 kB/s |  54 kB     00:00
(4/17): fuse-overlayfs-1.7.1-2.fc35.x86_64.rpm                                                                                133 kB/s |  72 kB     00:00
(5/17): libbsd-0.10.0-8.fc35.x86_64.rpm                                                                                239 kB/s | 104 kB     00:00
(6/17): fuse3-libs-3.10.5-1.fc35.x86_64.rpm                                                                                121 kB/s |  92 kB     00:00
(7/17): libnet-1.2-4.fc35.x86_64.rpm                                                                                428 kB/s |  57 kB     00:00
(8/17): libslirp-4.6.1-2.fc35.x86_64.rpm                                                                                293 kB/s |  72 kB     00:00
(9/17): slirp4netns-1.1.12-2.fc35.x86_64.rpm                                                                                176 kB/s |  55 kB     00:00
(10/17): container-selinux-2.173.1-1.fc35.noarch.rpm                                                                                14 kB/s |  49 kB     00:03
(11/17): containernetworking-plugins-1.0.1-1.fc35.x86_64.rpm                                                                                1.6 MB/s | 8.7 MB     00:05
(12/17): containers-common-1-32.fc35.noarch.rpm                                                                                110 kB/s |  76 kB     00:00
(13/17): criu-3.16.1-2.fc35.x86_64.rpm                                                                                317 kB/s | 529 kB     00:01
(14/17): socat-<IP_ADDRESS>-1.fc35.x86_64.rpm                                                                                182 kB/s | 302 kB     00:01
(15/17): runc-1.0.2-2.fc35.x86_64.rpm                                                                                418 kB/s | 3.1 MB     00:07
(16/17): cri-tools-1.19.0-1.module_f35+12974+2bc66b5d.x86_64.rpm                                                                                704 kB/s | 6.1 MB     00:08
(17/17): cri-o-1.21.3-1.module_f35+13330+6bc9c749.x86_64.rpm                                                                                1.1 MB/s |  23 MB     00:21
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                1.4 MB/s |  42 MB     00:29
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.

Created symlink /etc/systemd/system/multi-user.target.wants/crio.service → /usr/lib/systemd/system/crio.service.
brent@cluster-a:~$ sudo dnf copr enable -y @redhat-et/microshift
/usr/lib/python3.10/site-packages/dnf-plugins/copr.py:433: DeprecationWarning: distro.linux_distribution() is deprecated. It should only be used as a compatibility shim with Python's platform.linux_distribution(). Please use distro.id(), distro.version() and distro.name() instead.
  dist = linux_distribution()

Enabling a Copr repository. Please note that this repository is not part
of the main distribution, and quality may vary.

The Fedora Project does not exercise any power over the contents of
this repository beyond the rules outlined in the Copr FAQ at
<https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-in-copr>,
and packages are not held to any quality or security level.

Please do not file bug reports about these packages in Fedora
Bugzilla. In case of problems, contact the owner of this repository.
Repository successfully enabled.
brent@cluster-a:~$ sudo dnf install -y microshift firewalld
Copr repo for microshift owned by @redhat-et                                                                                6.8 kB/s | 2.7 kB     00:00
Package firewalld-1.0.1-2.fc35.noarch is already installed.
Dependencies resolved.
===============================================================================================================================================================================================================================
 Package                                     Architecture                    Version                                                  Repository                                                                          Size
===============================================================================================================================================================================================================================
Installing:
 microshift                                  x86_64                          4.8.0-2022_01_06_210147.fc35                             copr:copr.fedorainfracloud.org:group_redhat-et:microshift                           34 M
Installing dependencies:
 microshift-selinux                          noarch                          4.8.0-2022_01_06_210147.fc35                             copr:copr.fedorainfracloud.org:group_redhat-et:microshift                           19 k

Transaction Summary
===============================================================================================================================================================================================================================
Install  2 Packages

Total download size: 34 M
Installed size: 154 M
Downloading Packages:
(1/2): microshift-selinux-4.8.0-2022_01_06_210147.fc35.noarch.rpm                                                                                148 kB/s |  19 kB     00:00
(2/2): microshift-4.8.0-2022_01_06_210147.fc35.x86_64.rpm                                                                                2.0 MB/s |  34 MB     00:17
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                2.0 MB/s |  34 MB     00:17
Copr repo for microshift owned by @redhat-et                                                                                9.1 kB/s | 1.0 kB     00:00
Importing GPG key 0xC6BC2A0E:
 Userid     : "@redhat-et_microshift (None) <<EMAIL_ADDRESS> Fingerprint: C950 F16F F4CC 32E0 BCDA 1DF3 4730 C786 C6BC 2A0E
 From<EMAIL_ADDRESS>Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Installing       : microshift-selinux-4.8.0-2022_01_06_210147.fc35.noarch                                                                                1/2
  Running scriptlet: microshift-selinux-4.8.0-2022_01_06_210147.fc35.noarch                                                                                1/2
  Installing       : microshift-4.8.0-2022_01_06_210147.fc35.x86_64                                                                                2/2
  Running scriptlet: microshift-4.8.0-2022_01_06_210147.fc35.x86_64                                                                                2/2
  Running scriptlet: microshift-selinux-4.8.0-2022_01_06_210147.fc35.noarch                                                                                2/2
  Running scriptlet: microshift-4.8.0-2022_01_06_210147.fc35.x86_64                                                                                2/2
  Verifying        : microshift-4.8.0-2022_01_06_210147.fc35.x86_64                                                                                1/2
  Verifying        : microshift-selinux-4.8.0-2022_01_06_210147.fc35.noarch                                                                                2/2

Installed:
  microshift-4.8.0-2022_01_06_210147.fc35.x86_64                                                             microshift-selinux-4.8.0-2022_01_06_210147.fc35.noarch

Complete!

service fails to start since its looking for podman

# Start the service
brent@cluster-a:~$ sudo systemctl enable microshift --now
Created symlink /etc/systemd/system/multi-user.target.wants/microshift.service → /usr/lib/systemd/system/microshift.service.
Created symlink /etc/systemd/system/default.target.wants/microshift.service → /usr/lib/systemd/system/microshift.service.
Job for microshift.service failed because the control process exited with error code.
See "systemctl status microshift.service" and "journalctl -xeu microshift.service" for details.

logs out microshift.service file

brent@cluster-a:~$ systemctl status microshift.service
× microshift.service - MicroShift Containerized
     Loaded: loaded (/usr/lib/systemd/system/microshift.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Tue 2022-02-01 12:03:25 EST; 6s ago
       Docs: man:podman-generate-systemd(1)
    Process: 1631 ExecStartPre=/bin/rm -f /run/microshift.service.ctr-id (code=exited, status=0/SUCCESS)
    Process: 1632 ExecStartPre=/usr/bin/mkdir -p /var/hpvolumes (code=exited, status=0/SUCCESS)
    Process: 1633 ExecStart=/usr/bin/podman run --cidfile=/run/microshift.service.ctr-id --cgroups=no-conmon --rm --replace --sdnotify=container --label io.containers.autoupdate=registry --network=host --privileged -d --na>
    Process: 1634 ExecStopPost=/usr/bin/podman rm -f --ignore --cidfile=/run/microshift.service.ctr-id (code=exited, status=203/EXEC)
   Main PID: 1633 (code=exited, status=203/EXEC)
        CPU: 4ms

Feb 01 12:03:25 cluster-a systemd[1]: microshift.service: Scheduled restart job, restart counter is at 5.
Feb 01 12:03:25 cluster-a systemd[1]: Stopped MicroShift Containerized.
Feb 01 12:03:25 cluster-a systemd[1]: microshift.service: Start request repeated too quickly.
Feb 01 12:03:25 cluster-a systemd[1]: microshift.service: Failed with result 'exit-code'.
Feb 01 12:03:25 cluster-a systemd[1]: Failed to start MicroShift Containerized.
brent@cluster-a:~$ systemctl status microshift.service^C
brent@cluster-a:~$ journalctl -u microshift.service
-- Journal begins at Thu 2022-01-27 17:56:12 EST, ends at Tue 2022-02-01 12:03:25 EST. --
Feb 01 12:03:24 cluster-a systemd[1]: Starting MicroShift Containerized...
Feb 01 12:03:24 cluster-a systemd[1617]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1617]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Main process exited, code=exited, status=203/EXEC
Feb 01 12:03:24 cluster-a systemd[1618]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1618]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Control process exited, code=exited, status=203/EXEC
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Failed with result 'exit-code'.
Feb 01 12:03:24 cluster-a systemd[1]: Failed to start MicroShift Containerized.
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Scheduled restart job, restart counter is at 1.
Feb 01 12:03:24 cluster-a systemd[1]: Stopped MicroShift Containerized.
Feb 01 12:03:24 cluster-a systemd[1]: Starting MicroShift Containerized...
Feb 01 12:03:24 cluster-a systemd[1621]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1621]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Main process exited, code=exited, status=203/EXEC
Feb 01 12:03:24 cluster-a systemd[1622]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1622]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Control process exited, code=exited, status=203/EXEC
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Failed with result 'exit-code'.
Feb 01 12:03:24 cluster-a systemd[1]: Failed to start MicroShift Containerized.
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Scheduled restart job, restart counter is at 2.
Feb 01 12:03:24 cluster-a systemd[1]: Stopped MicroShift Containerized.
Feb 01 12:03:24 cluster-a systemd[1]: Starting MicroShift Containerized...
Feb 01 12:03:24 cluster-a systemd[1625]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1625]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Main process exited, code=exited, status=203/EXEC
Feb 01 12:03:24 cluster-a systemd[1626]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1626]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Control process exited, code=exited, status=203/EXEC
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Failed with result 'exit-code'.
Feb 01 12:03:24 cluster-a systemd[1]: Failed to start MicroShift Containerized.
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Scheduled restart job, restart counter is at 3.
Feb 01 12:03:24 cluster-a systemd[1]: Stopped MicroShift Containerized.
Feb 01 12:03:24 cluster-a systemd[1]: Starting MicroShift Containerized...
Feb 01 12:03:24 cluster-a systemd[1629]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1629]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Main process exited, code=exited, status=203/EXEC
Feb 01 12:03:24 cluster-a systemd[1630]: microshift.service: Failed to locate executable /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1630]: microshift.service: Failed at step EXEC spawning /usr/bin/podman: No such file or directory
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Control process exited, code=exited, status=203/EXEC
Feb 01 12:03:24 cluster-a systemd[1]: microshift.service: Failed with result 'exit-code'.
Feb 01 12:03:24 cluster-a systemd[1]: Failed to start MicroShift Containerized.

brent@cluster-a:~$ cat /usr/lib/systemd/system/microshift.service
# container-microshift.service
# autogenerated by Podman 3.4.0
# Fri Nov  5 14:30:39 UTC 2021

[Unit]
Description=MicroShift Containerized
Documentation=man:podman-generate-systemd(1)
Wants=network-online.target crio.service
After=network-online.target crio.service
RequiresMountsFor=%t/containers

[Service]
Environment=PODMAN_SYSTEMD_UNIT=%n
Restart=on-failure
TimeoutStopSec=70
ExecStartPre=/bin/rm -f %t/%n.ctr-id
ExecStartPre=/usr/bin/mkdir -p /var/hpvolumes
ExecStart=/usr/bin/podman run --cidfile=%t/%n.ctr-id --cgroups=no-conmon --rm --replace --sdnotify=container --label io.containers.autoupdate=registry --network=host --privileged -d --name microshift -v /var/run:/var/run -v /sys:/sys:ro -v /var/lib:/var/lib:rw,rshared -v /var/hpvolumes:/var/hpvolumes -v /lib/modules:/lib/modules -v /etc:/etc -v /run/containers:/run/containers -v /var/log:/var/log -e KUBECONFIG=/var/lib/microshift/resources/kubeadmin/kubeconfig quay.io/microshift/microshift:latest
ExecStop=/usr/bin/podman stop --ignore --cidfile=%t/%n.ctr-id
ExecStopPost=/usr/bin/podman rm -f --ignore --cidfile=%t/%n.ctr-id
Type=notify
NotifyAccess=all

[Install]
WantedBy=multi-user.target default.target

We had a bug introduced in our rpm spec file, I'm sending a bugfix.

Latest RPM fixes this
[ec2-user@ip-172-31-86-161 ~]$ rpm -qa | grep podman
[ec2-user@ip-172-31-86-161 ~]$ rpm -qa | grep microshift
microshift-4.8.0-2022_02_02_194009.el8.x86_64
microshift-selinux-4.8.0-2022_02_02_194009.el8.noarch
[ec2-user@ip-172-31-86-161 ~]$ sudo systemctl status microshift
● microshift.service - MicroShift
   Loaded: loaded (/usr/lib/systemd/system/microshift.service; disabled; vendor preset: disab>
   Active: active (running) since Thu 2022-02-03 14:02:44 UTC; 30min ago
 Main PID: 20312 (microshift)
    Tasks: 30 (limit: 204094)
   Memory: 808.2M
   CGroup: /system.slice/microshift.service
           └─20312 /usr/bin/microshift run

Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:12.996247   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:12.996362   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:12.996767   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:12.997624   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:12.998203   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:12.999520   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:12.999776   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:13.000435   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:13.007088   2031>
Feb 03 14:33:13 ip-172-31-86-161.ec2.internal microshift[20312]: W0203 14:33:13.007124   2031>


Two issues with Netcdf output files

Hi
I have encountered two separate issues related to writing the output NetCDF file, for which I was unable to find any mention of Github issues. I am hoping you will be able to diagnose what is going on. I've pared down my actual code to a very simple one that illustrates the problems (please see below). FYI -- I am running parcels version 2.1.2 installed with python 3.6.

Temporary files "out-XXX" are not collated into a single NetCDF file. When running the code, no error is given, however the npy files are left in the out-XXX/o/ directory. If I uncomment Line 41 (pfile.close=(True), and rerun the code, the NetCDF file is produced. If I then re-comment like 41, delete the NetCDF file, and run it again, I get no error the first time, but subsequently get
Exception ignored in: <bound method ParticleFile.del of <parcels.particlefile.ParticleFile object at 0x1193f25f8>>
Traceback (most recent call last):
File "/Applications/anaconda3/envs/py3_parcels/lib/python3.6/site-packages/parcels/particlefile.py", line 195, in del
self.close(True)
File "/Applications/anaconda3/envs/py3_parcels/lib/python3.6/site-packages/parcels/particlefile.py", line 200, in close
self.export()
File "/Applications/anaconda3/envs/py3_parcels/lib/python3.6/site-packages/parcels/particlefile.py", line 352, in export
raise RuntimeError("No npy files found in %s" % self.tempwritedir_base)
RuntimeError: No npy files found in out-DNYKZMWL
If I run it again, I get no error, and a NetCDF output is created, but an out-XXX folder is also created and remains.

When I run the code with Line 41 uncommented so I do get an output file: for the situation where particles on "land" (i.e. velocity = 0) have their depth reset to 1 (Line 15), the netCDF file correctly stores the particle locations, such that the depth of particle 1 is reset to 1m at the first output time. However, if I instead delete land particles (i.e. uncomment line 9), the output file doesn't show the delete until the second output time. This happens even when the output file deltat is greater than the particle dt. If I restrict the simulation to the single particle that gets deleted, I get a warning that the Particle set is empty at the first output time. So the code recognizes the deletion at the correc time, but it doesn't write the file that way.

Any advise you can give would be very welcome.
Parcels simple code below*******
from parcels import ParticleFile, JITParticle, ParticleSet, FieldSet, Field
from datetime import timedelta as delta
import numpy as np
def CheckLand(particle, fieldset, time):
(up, vp, wp) = fieldset.UVW[time, particle.depth, particle.lat, particle.lon]
if fabs(up) < 1e-8 and fabs(vp) < 1e-8 and fabs(wp)<1e-8:
particle.depth = 1
#particle.delete()
xdim = ydim = 3
zdim = 3
uu = np.zeros((xdim, ydim, zdim))
uu[2,:,:] = 1
dimensions = {'lon': np.linspace(0., 2, xdim, dtype=np.float32),
'lat': np.linspace(0., 2, ydim, dtype=np.float32),
'depth': np.linspace(0., 2, zdim, dtype=np.float32)}
data = {'U': uu,
'V': np.zeros((xdim, ydim, zdim), dtype=np.float32),
'W': np.zeros((xdim, ydim, zdim), dtype=np.float32)}
fieldset = FieldSet.from_data(data, dimensions, mesh='flat')
#Define ICs so one particle has zero velocity (land) and one has non-zero velocity
lonp=[1, 0.5]
latp=[1, 1.5]
depthp=[.5, 1.5]
pset = ParticleSet.from_list(fieldset=fieldset, pclass=JITParticle, lon=lonp, lat=latp, depth=depthp)
pfile = ParticleFile("Testing", pset, outputdt=delta(hours=1))
kernels =  pset.Kernel(CheckLand)
pset.execute(kernels, runtime=delta(hours=2),
dt=delta(hours=1),
output_file=pfile,)
#pfile.close(True)

Hi @ElizaJayne11, thanks for reporting these issues, and also for providing such a nice minimal code! That really helps us with debugging!
Re your point 1: This is because of how python closes files upon exit of the script. The easiest way to work around this is to define the ParticleFile object within the pset.execute, so
pset.execute(kernels, runtime=delta(hours=2), dt=delta(hours=1),
             output_file=ParticleFile("Testing", pset, outputdt=delta(hours=1)))

Re your point 2: I fear that this is not easy to fix. The way that writing files is implemented in Parcels, is that all the deleted particles are written only every outputdt, mostly for efficiency and speed. This also means that deleted particles are written at the next outputdt. Changing this will be a massive rewrite of the code, something that I don't expect we'll do in the near future. Is this a problem for you?

Hi Erik
Thanks for your informative feedback. I really appreciate you taking the time to help.
Specifying the ParticleFile in the execute statement worked (good to know it is just a Parcels thing, and not something I was doing wrong).
With regard to the writing of deleted particles: It is not a real problem, as worst-case I can always write output files at double the frequency. I am confused however, because it sounds like if a particle is deleted between the initial conditions and first outputdt, it should appear as deleted in the second output file. That is different than what I am seeing in my code, where it only appears deleted at third outputdt file.

Hi @ElizaJayne11, sorry for the slow response. The two writings is because the ParticleSet is written at time 0 before any kernels are applied, so only at time 3600 is the particle deleted, and hence it is again written then as last deleted. Makes sense?


I don‘t understand, and I use the latest version of bosh-scaler.
ljx@ubuntu:~/bosh-scaler$ git pull
Already up-to-date.

Hi @lijianxun , now bosh-scaler is hard to maintain the codes.
If you paste your error logs to this issue, it may be helpful to reply to you, but may not be able to solve.

Hi @ozzozz , I use httperf to measuring web server performance, and hope that the httperf can trigger the out-conditions.
But the bosh-scale get an error when I use httperf :
ljx@ubuntu:~/bosh-scaler$ bundle exec ./bin/scaler ./config/sample.yml
/home/ljx/bosh-scaler/lib/scaler/runner.rb:39: warning: kqueue is not supported on this platform
/home/ljx/bosh-scaler/lib/scaler/collectors/bosh_nats_collector.rb:58:in block in connect_to_mbus': NATS faild to connected to mbus://nats:nats@<IP_ADDRESS>:4222 (RuntimeError)         from /var/lib/gems/2.1.0/gems/nats-0.4.28/lib/nats/client.rb:506:in call'
from /var/lib/gems/2.1.0/gems/nats-0.4.28/lib/nats/client.rb:506:in receive_data'         from /var/lib/gems/2.1.0/gems/eventmachine-1.0.8/lib/eventmachine.rb:193:in run_machine'
from /var/lib/gems/2.1.0/gems/eventmachine-1.0.8/lib/eventmachine.rb:193:in run'         from /home/ljx/bosh-scaler/lib/scaler/runner.rb:40:in start'
from /home/ljx/bosh-scaler/lib/scaler/runner.rb:7:in run'         from ./bin/scaler:5:in '
ljx@ubuntu:~/bosh-scaler$

Hi @lijianxun ,
bosh-scaler seems to connect to NATS server in BOSH.
Is <IP_ADDRESS> the correct BOSH VM's IP address?
Is port 4222 the correct NATS's port?
Is nats:nats the correct NATS's ID/PW?
Check them all, please.

Hi, I suspect the httperf affect the performance of NATS.
I found another problem:
E, [2015-11-26T02:52:02.721354 #89883] ERROR -- : Updating deployment manifest of cf-deployment failed: undefined method `push_static_ip' for nil:NilClass
What can I do to solve it, thank u very much!


config artnet universe UX

the lower-four-bits logic is undocumented/difficult to config correctly in the CLI/web UI
artnet_add_output crashes into a bootloop if universe & 0xFFF0 does not strictly match the artnet.universe
artnet.universe can be configured with a value that has 0x000F bits set, and will thus never pass the artnet_add_output check, and always enter a bootloop

https://github.com/SpComb/esp-projects/commit/e594e3cd7f0f191576509d7681912c9e3bb1987f should have fixed the config, such that it is no longer possible to mis-configure the artnet universe


Add clarification for login_required decorator

ref #313

merged in 434c19933eb445907d73b9bb9e4973d546f5ee52, after fixing the author name for the commit so it was associated with your email.  You can git config -g user.email "my@email" to fix that.  Cleaned up in 169a4e0c44dcf8414d7cc27d405e9afdcd29a53c.  Thanks!

@davidism The added documentation doesn't make sense at all to me.


Version 0.7.3

Landed in https://github.com/metarhia/globalstorage/commit/b63bc13385c3dfe894acd514e06e034db287189d.


Describe where to find logs for Airnode deployed to a cloud provider

e.g. CloudWatch in AWS. It would also be helpful to describe the organization of log groups (e.g. for gateway vs. blockchain requests).
Perhaps this would work well as a new page, e.g. "Monitoring Airnode", within the API Providers section following the "Deploying Airnode" page.

Good idea, good location.

@martinkolenic  - testing this should be simple: the next time you are deploying to GCP and AWS just confirm that the instructions to view the logs are understandable.


New version: GiulioSorrentino.WinDateFrom version 4.6

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I'm seeing in file that the url is https://github.com/numerunix/WinDateFrom.avalonia/releases/download/4.6/WinDateFrom.Avalonia-4.6-x64.msi
that is correct.
Why does exist the exe in the log?

URL: https://github.com/numerunix/WinDateFrom.avalonia/releases/download/4.6/WinDateFrom.Avalonia-4.6-x64.msi
Status Code: 200
(Automated message - build 813)

Automatic Validation ended with:

URI: https://github.com/numerunix/WinDateFrom.avalonia/releases/download/4.0/WinDateFrom-4.0-x64.exe, Validation result: Failed, Http status code: NotFound

(Automated response - build 813.)

[Policy] Network-Blocker

Nope i removed all versione, the ones rhat remains are 4.6 in msi. The package .exe does not exists anymore.

Hello there, the url windatefrom-4.0 has been deleted, the new url is 4.6 msi, due to a security fix that invalidate all previous version.
Thanks

I solved the network blocker, the url was in windaframe.locale.en-us.
Try now thanks

smart screen

All is done, it must only be approved.

Please, delete all previous version from your repository and approve it. That are dead links.


[HW] workshop-spring-stargate Lucas Herrera

Name:  Lucas Herrera
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/lucasaherrera/
Attach the homework step I screenshots below:
Attached
Attach the homework step II screenshots below:
Attached
DA Elevation Phase 3 HW.pdf

Nice job Lucas, looks good. Here's your badge -> https://api.badgr.io/public/assertions/OL5Z4NrWSlKUfSpb6kMCvA?identity__email=lucas.herrera%40datastax.com.
BTW, some of your images contained your Astra token. I've since delete the PDF you attached and the history, but please go and remove your token from the Astra UI to be safe.


Rename accordion module

Hey @OsamaAtReloadly do you see anything wrong with this PR?

You need to sync your branch with main @OsamaAtReloadly

The PR is supposed to be into develop not main 👀

@OsamaAtReloadly  you have to also increase the package version otherwise the build won't be successful

@OsamaAtReloadly you have to also increase the package version otherwise the build won't be successful

Updated now.


Fix pylint warning.

To fix https://github.com/iterative/dvc-objects/actions/runs/6162702142/job/16724739641#step:5:72Ç
Do we care about respecting the reference implementation? Should we add and honor the on_error arg instead?

Sorry, merged by accident and reverted. Need to take a closer look and try to fix properly.


Unable to import/use SnapshotHelper.swift in Objective-C project

Hi All I'm also facing same issue. I configured snapshot and generated SnapshotHelper.swift, added it to my Test Target and writing following code in Test.m file throws error

XCUIApplication *app = [[XCUIApplication alloc] init];
[Snapshot setupSnapshot:app];
[app launch];

But it is showing error "Use of undeclared identifier 'Snapshot'".
Bridge file UITests-Bridging-Header.h is empty with comments

//
// Use this file to import your target's public headers that you would like to expose to Swift.
//

XCode : 7.3.1
Defines Module : YES
Can any one resolved this issue

I'm also getting "Use of undeclared identifier 'Snapshot'" issue following the Quick Start
Note: I'm using the Xcode 8 Bridging-Header helper when adding the SnapshotHelper.swift file

@Sea-Eagle Are you still running into this issue? Did you follow these steps:
Create a new UI Test target in your Xcode project (top part of this article) Run snapshot init in your project folder Add the ./SnapshotHelper.swift to your UI Test target (You can move the file anywhere you want) (Objective C only) add the bridging header to your test class. #import "MYUITests-Swift.h" The bridging header is named after your test target with -Swift.h appended. In your UI Test class, click the Record button on the bottom left and record your interaction To take a snapshot, call the following between interactions Swift: snapshot("01LoginScreen") Objective C: [Snapshot snapshot:@"01LoginScreen" waitForLoadingIndicator:YES]; Add the following code to your setUp() method

Sorry for delay.
Still I'm getting the issue even following above steps
On Sep 27, 2016 11:12 PM, "Todd Burner"<EMAIL_ADDRESS>wrote:

@Sea-Eagle https://github.com/Sea-Eagle Are you still running into this
issue? Did you follow these steps:
Create a new UI Test target in your Xcode project (top part of this
article)
Run snapshot init in your project folder
Add the ./SnapshotHelper.swift to your UI Test target (You can move the
file anywhere you want)
(Objective C only) add the bridging header to your test class.
#import "MYUITests-Swift.h"
The bridging header is named after your test target with -Swift.h appended.
In your UI Test class, click the Record button on the bottom left and
record your interaction
To take a snapshot, call the following between interactions
Swift: snapshot("01LoginScreen")
Objective C: [Snapshot snapshot:@"01LoginScreen"
waitForLoadingIndicator:YES];
Add the following code to your setUp() method
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/issues/6119#issuecomment-249940754,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT-nrqrXhK2CzN8usw254FZHDL83r4Ceks5quVV-gaJpZM4J8tfX
.

@Sea-Eagle Thanks for following up. Can you provide a sample project or exact repro steps from a blank project? I'd love to investigate this. Thanks!

I had the same issue because I did not import the right bridging header file. The quick start says

#import "MYUITests-Swift.h"
The bridging header is named after your test target with -Swift.h appended.

I think the use of the bridging header word is a bit misleading since you must #import "My_App_UI_Tests-Swift.h", which is not the My App UI Tests-Bridging-Header.h file generated by Xcode when you added the first swift file to your project.
You have to guess the My_App_UI_Tests-Swift.h filename since it only exists deep inside the derived data directory of your project. If you don't want to guess the filename, you can find it like that:
find ~/Library/Developer/Xcode/DerivedData/ -name "*-Swift.h"

I encountered same issue. In my case project cleanup, rebuild and restart of tests helped. file was generated with correct name.


Unable to scroll & select emojis in some categories.

Describe the bug
Some of the categories are un-scrollable & unable to pick the top few rows of these categories. Can expand modal to cause the category to become scrollable.
To Reproduce
I haven't done any tweaking besides setting a theme. So not many steps to reproduce apart from:

install package
use package

Expected behavior
I'd expect to be able to scroll each category correctly
Screenshots

This happens on both iOS and Android. Using Expo 48.

Hi, thanks for reporting. Can you add a minimal reproducible code here - https://snack.expo.dev/? I've tried to reproduce it by myself in 2 applications and I couldn't so it may be something specific to your project

I see this too. The first 2 default categories work and so does the last category. I can repro it in my app but not a basic template. It's definitely something in my app.

I'm trying to narrow it down and looks like the react emoji picker bugs out whenever a react-reanimated animation plays :(

@yefim thanks for co-reporting, it seems that we might need to look into prioritizing reanimated integration in our roadmap
@crumb1e have you been able to find a solution in your case? Happy to look into it more carefully though we need more info first

@yefim thanks for co-reporting, it seems that we might need to look into prioritizing reanimated integration in our roadmap
@crumb1e have you been able to find a solution in your case? Happy to look into it more carefully though we need more info first

@Okelm Apologies been super busy, will see if I can get some more info tomorrow!

Hmmm I'm able to get it working with some react-native-reanimated animations but not others :/ this is very peculiar. See this working as expected Snack: https://snack.expo.dev/@yefim/emoji-picker-reanimated

When I expand the 3rd category (the broken one), I am able to scroll on the bottom half of the category. This makes it seem as if there is something on top of the top half of the ScrollView but I cannot find anything there with the inspector. Here's a video
https://github.com/TheWidlarzGroup/rn-emoji-keyboard/assets/1170843/d8edcfa0-a4b7-4103-b975-1fe0c50bf0a7

AHA! I have a Snack that can reproduce the issue! https://snack.expo.dev/@yefim/rn-emoji-keyboard-reaniamted-expo48?sdkVersion=48.0.0

The working Snack is using Expo 47, react-native-reanimated 2.12.0.
The broken one is using Expo 48, react-native-reanimated 2.14.4.

Any ideas on a workaround? I can try downgrading our reanimated package

Havent got a chance to reproduce and compare, any kind of investigation like this would be appreciated.

Did you check out the Snack I linked with the reproduction? https://github.com/TheWidlarzGroup/rn-emoji-keyboard/issues/138#issuecomment-1624387514
I'm not able to downgrade the react-native-reanimated library in my project :(

Hi, thanks for the repro @yefim I've been looking at it, but I haven't figure out how to fix it yet. For now I know that the problem are layout entering animations. So if u want an instant fix, you have to get rid of them for now, and I will try to find a fix as fast as possible :)

@yefim @crumb1e I have found a solution. You had problems only on iOS right? Because I couldn't reproduce it on Android.
https://github.com/TheWidlarzGroup/rn-emoji-keyboard/pull/145

Yes, I'm only seeing this on iOS. We aren't currently building on Android.

Hi @crumb1e @yefim
Thanks for reporting this issue, it has been resolved by @mateki0 and released in the latest version 1.5.0. I highly encourage you to update and test if everything works properly. If there is something that still needs improvement, please let us know 😄

it works thank you !

On behalf of crumb1e, we've just updated to 1.5.0 so will keep an eye out :) thanks!


syntax: Provide default.yaml as fallback definition

This will provide a basic rule set which is applied in the moment no known file type can be found or identified. The approach is heavily inspired by nano and his default.nanorc. Now it's possible that files without any extension will be highlighted even they aren't explicitly added to a dedicated syntax definition (e.g. /etc/fstab or config files present under /etc/default/).
Closes #2926

I like the idea but I think your default.yaml is doing too much. A lot of the time when I'm editing a file with an unknown type it's going to be plaintext in which case I don't really want special characters or quotes to be highlighted. Thus I'd prefer to only include rules that are extremely unlikely to match in an unrelated context, similar to the default.nanorc you linked.
Your definition for config categories/sections currently allows newlines which is probably not intended. I would change it to
- identifier: "^\\[[^\\[\\]]+\\]$"

I would also add the spaces before tabs highlighting from default.nanorc:
- error: " +\\t+"

I like the idea but I think your default.yaml is doing too much. A lot of the time when I'm editing a file with an unknown type it's going to be plaintext in which case I don't really want special characters or quotes to be highlighted. Thus I'd prefer to only include rules that are extremely unlikely to match in an unrelated context, similar to the default.nanorc you linked.

That's something which can be discussed, because it's something tightly coupled to personal preferences. When I edit "unknown" file types then these are quite often configuration files present in the /etc/ folder/tree. The usage of assignments and strings are normal there.

Your definition for config categories/sections currently allows newlines which is probably not intended.

Yes, you're right. Should have been used as in the nano rule from the beginning.

I would also add the spaces before tabs highlighting from default.nanorc:

Done.

When I edit "unknown" file types then these are quite often configuration files present in the /etc/ folder/tree. The usage of assignments and strings are normal there.

Wondering if that could be addressed with something like this in settings.json:
    "/etc/*": {
        "filetype": XXX
    }

Maybe not, but you can also always resort to some Lua scripting.

I would also add the spaces before tabs highlighting from default.nanorc:

There is a PR https://github.com/zyedidia/micro/pull/1897. We might still hope it will be merged some day. If it will, and if we even go ahead and make those hltaberrors and hltrailingws options enabled by default, then spaces before tabs (and other similar errors) will be highlighted automatically for all file types, so this error: " +\\t+" will be superfluous.

Wondering if that could be addressed with something like this in settings.json:

But then we add for every location again a new settings entry, like path x and then y etc. pp.
Let us try to watch from a different perspective:
micro has/provides the capability with the syntax option to be active by default and advertises his self to be...

[...] micro aims to be somewhat of a successor to the nano editor [...] Here is a picture of micro editing its source code. {syntax highlighting screenshots attached}

...so why not doing more or less the same as nano does and provide and use a default template in the moment nothing other fits? We don't need to define other fancy paths/locations, we just have or could have a simple default template, which can be maintained as we do with the rest. The workflow doesn't need to be changed. No additional Lua plugin needs to be involved.
Otherwise I expect some more "issues" being opened like the one I try to fix with this feature. :smile:

I'm not against a default highlighting as such, I was merely commenting on your specific use case of editing various configs files in /etc, for which you might want a richer highlighting than what is suitable for a default template (i.e. for arbitrary plain-text files), as @Andriamanitra pointed out.

Ah, ok. Then I got you wrong yesterday...sorry for that.
Then we've already two votes against the special characters and the quotes.
Any suggestions what else shall be removed?
I assume, that the configuration section isn't needed as well, since we should focus on plain text only.

this error: " +\t+" will be superfluous.

Then we shouldn't add it from the beginning, am I right? Otherwise it needs to be removed afterwards, in case #1897 is merged.

Wondering if that could be addressed with something like this in settings.json:

I used your tip for now and set the file type of these files to ini, because this will give me the necessary highlighting I would expect for the files in this particular directory.
Maybe this PR could become handy for different scenarios. :)

nice, i would have added a screenshot to illustrate tho

Are there any additional ideas, hints or suggestions to add for the default/unknown definition?

Just came cross this issue. Would like see default syntax configuration. For example sudo nano /etc/ssh/ssh_config ..etc.
Currently, is it possible to define a default one by myself?

Overriding the default will work earliest after the PR has been merged. As alternative you can create your explicit user defined highlighting for ssh_config etc.


Public methods

Make all methods public and add a Bytes() function to be able to extract the entire bitstream. This allows full use of the library in other packages.

I've closed this pull request for now as it fails go vet due to error not being returned from some methods.

Figure it out. WriteByte is a "canonical method." There are two options: one is to return nil on exit every time, or to rename WriteByte to something like WriteOneByte. I've taken the latter approach; let me know if you'd prefer the former.


[templates] Apply shellcheck to launcher templates

Just spotted the template:
https://github.com/jreleaser/jreleaser/blob/7ed38b21da3d1f4ceafb2b2eeb8192580191696f/core/jreleaser-templates/src/main/resources/META-INF/jreleaser/templates/java-archive/java-archive/bin/launcher.tpl
Running shellcheck yields some interesting results. E.G. backticks are being used over the $() alternative which can do better escaping.
Task List

[X] Steps to reproduce provided
Run shellcheck
[ ] Stacktrace (if present) provided
[ ] Example that reproduces the problem (link to git repository is ideal)
[X] Full description of the issue provided (see below)

Steps to Reproduce

run shellcheck

Expected Behaviour
no issues found
Actual Behaviour
Some issues found
Environment Information

Operating System: Linux or Mac
JReleaser Version: git
JDK Version: n/a

🎉 This issue has been resolved in v1.5.1 (Release Notes)


Installing zarrdataset

Description:
I attempted to follow the installation instructions for zarrdataset as provided in the documentation. However, I encountered an issue while using the command python setup.py -e ., which resulted in an error stating that the option -e is not recognized.
Undeterred, I proceeded to install the package using the following commands:
python setup.py build
python setup.py install

Despite successful execution, it appears that only the dependencies were installed, and the zarrdataset package itself is missing. I realized this when attempting to import zarrdataset.
Could you please provide guidance on the correct installation procedure or address this issue? Your assistance is greatly appreciated.
Environment:
Python version: 3.7.7
Operating System: CentOS Linux 7
Thank you for your attention to this matter.

Hi @HappyHackingOrange, thanks for trying to install this package and raising this issue.
Certainly the installation instructions are wrong, and the actual way to install this package is using pip.
So try with the following command from within the zarrdataset folder and let me know if that worked or not.
pip install -e .

Thank you for the quick response. That command didn't work, but entering python -m pip install -e . actually worked for me.

Great! I'll update the installation instructions to include this info. Thanks!


Add add-ons APIs

Add the APIs of the following add-ons:

Access Control Testing
Ajax Spider
Alert Filters
Export Report
Import files containing URLs
Log File Importer
Plug-n-Hack Configuration
Replacer
Reveal
Revisit
Selenium
SOAP
Wappalyzer - Technology Detection
WebSockets

looking forward to see this PR merged.


Export timesheet as pdf without comments

When adding work days, a HiWi can add comments on what was done during the logged timeslot.
while this information may be interesting for the WiMi who employed him, it is not necessary to include these comments in the exported timesheet that can be handed in.
There should be an option to hide comments on export.

implemented in ae82e4b76012898aaffac3125a1f72b7455e6833
no tests yet, i dont know how

tests not necessary


Fix dependency-review for commits in main

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Upgrade to Chrome/Edge version 109 (ExtentReports.Core 1.0.3) - "configureView is not defined"

Steps to reproduced:

Upgrade Chrome/Edge to version 109
ExtentReports.Core 1.0.3
ExtentV3HtmlReporter

Generate html report file and open it with Edge/Chrome having version 109.
The user is not able to load test details:

Having exact same issue. Deleting that line of code does not fix the problem.

One of my team members found a fix for it -
When changing links shown in picture with these

https://www.extentreports.com/resx/v3html/js/extent.js https://www.extentreports.com/resx/v3html/css/extent.css
Then it should fix the issue. Even changing just extent.css link fixes it.

This workaround works. Thank you

Closing - this library is not part of the framework and is maintained by SimplyTest https://www.nuget.org/packages/ExtentReports.Core.


skopeo copy push file to local registry failure

Potential issue
Currently the tests do not fail on the CI, as we use docker major version 25 but the tests probably will start to fail in the future when github actions will upgrade to docker major version 26.
Issue description
With docker version >=26.0.0 and skopeo version 1.15.1, it fails to copy-push to local registry with the below error.
Error response from daemon: {"message":"http: server gave HTTP response to HTTPS client"}

Steps to reproduce

clone this repo git clone https://github.com/paketo-community/ubi-base-stack.git
run ./scripts/test.sh

Steps to reproduce without using the test.sh script

 docker run -d -p 5000:5000 --restart=always --name registry registry:2
download the build.oci image from here https://github.com/paketo-community/ubi-base-stack/releases/tag/v0.0.65 (any oci image will do)
copy the image to local registry with skopeo  skopeo copy  oci-archive:path/to/build.oci docker://localhost:5000/build-image-test:latest --dest-tls-verify=false

you should get the below error
FATA[0000] trying to reuse blob sha256:98be1b9a299ccd651050fba79b85d091348447816285d33bc7c09d5679f69300 at destination: pinging container registry localhost:5000: Get "https://localhost:5000/v2/": http: server gave HTTP response to HTTPS client

@pacostas is this still an issue, just asking since its been open for quite a while and with the latest update we won't be using skopeo anymore


Implement binding generator in Rust

The PR totally rewites the OCaml binding generator in Rust. Now the re-generated code passes every test on tch-rs and on large projects including rust-bert and my yolo-dl.
My motivation was to add libtorchvision bindings, but stuck in the OCaml bindgen code. I felt the pain in the hassle of codegen in strings. The rewriting will gain us the Rust's safety feature and make the project self-hosted. (I did not blame OCaml. It's a good language and I learned it recently.)

Declaration file deserialization is done with serde in declarative way.
Generated Rust code is assembled with quote token by token rather in strings.
It becomes easy to refactor and maintain. Every stage is explicitly and statically typed. The compiler type checking will be a good aid.

The new generated bindings should maintain the compatibility with previous code. It is ensured by tests some manual audit on rustdoc. To check if the new bindings works for your project, run make gen in tch-rs directory and add this to your project Cargo.toml.
[patch.crates-io]
tch = { path = "/path/to/tch-rs" }
torch-sys = { path = "/path/to/tch-rs/torch-sys" }

BTW, I'm working on libtorchvision bindings. It will be easier if this PR can be accepted.

Looks great! hasktorch also generate bindings from Declarations.yaml,what is left to be done?

Just played around with this PR,build without problem and MNIST example works(on newest arch linux)

Looks great! hasktorch also generate bindings from Declarations.yaml.Does this use rust-bindgen?

@doofin It generates every function signature according to Declarations.yaml without bindgen.

BTW,does this imply that we will get the same api as the pytorch cpp api?

Basically yes, Declarations.yaml is generated by compiling libtorch.

It is already the case that the Rust api in this create is automatically generated from Declarations.yaml and it has been so since the first version of this crate. You can find the generated api in tensor_generated.rs for example.
The design goal was indeed to keep the api as close as possible to the C++ one (which itself is pretty close  to the Python version), so that it's easier to port examples and applies existing tutorials. And it should be possible to write more Rust idiomatic crates on top of this one.
The part generating the code from Declarations.yaml is actually in OCaml as it's shared with the ocaml-torch sister project. OCaml is not required to compile this crate though as the generated files are checked in in the repo. This PR rewrites the code generation in Rust, however we would like to keep it in OCaml at the moment so as to continue sharing code and functionalities with ocaml-torch.

Great,maybe it's better to start a new separate project for codegen.

Seems it is decided to couple the OCaml project, though I think the opposite. I will move the code to another repo for those interested.


GE plugin 3.12.4 & More gradle-build-action

Closes https://github.com/gradle-nexus/publish-plugin/pull/194

Ooops, misoperated.

Ooops, misoperated.


Replace initialization with declaration in grpc query handlers

Description

closes: #3376
Commit Message / Changelog Entry
type: commit message

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

thanks! Be prepared for some tests maybe failing since they sometimes assert that nothing has been returned (which now will be different because tests have been written to expect an empty slice and not a nul slice).
I.e you might need to tweak some of the tests too.

thanks! Be prepared for some tests maybe failing since they sometimes assert that nothing has been returned (which now will be different because tests have been written to expect an empty slice and not a nil slice).
I.e you might need to tweak some of the tests too.

Lmao. I will be

Codecov Report

Merging #3436 (46c7d22) into main (3a7106c) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3436   +/-   ##
=======================================
  Coverage   78.54%   78.54%
=======================================
  Files         181      181
  Lines       12581    12581
=======================================
  Hits         9882     9882
  Misses       2265     2265
  Partials      434      434

Impacted Files
Coverage Δ

modules/core/02-client/keeper/grpc_query.go
69.45% <100.00%> (ø)

modules/core/03-connection/keeper/grpc_query.go
90.83% <100.00%> (ø)

modules/core/04-channel/keeper/grpc_query.go
84.55% <100.00%> (ø)

Nice! I did not originally do an exhaustive search but trying one now does seem to find an additional instance in the query for DenomTraces:
https://github.com/cosmos/ibc-go/blob/2632ae24926e251fb70efabaa1a8b92755c7bccc/modules/apps/transfer/keeper/grpc_query.go#L53
I'm not able to grep for any other instance, hopefully this is the last of em.

Hey @expertdicer I think you'll need to resync the branch with main. It may be easier to work off a personal fork and use the "Allow edits from maintainers" checkbox. That would allow us to handle cases like this and speed up PRs being merged :)
Thanks for all your contributions lately ❤

Looks like there was a merge conflict


[5.5] Ensure that verbose (-v) mode applies to in-place execution.

Cherry-pick of https://github.com/apple/swift-driver/pull/715
For compiles which fall under our "in-place execution" flow, ensure that we print the in-place job before executing it if -v was specified.
Resolves rdar://79295614

@swift-ci please test


Update Update-CsUserDatabase.md

https://github.com/MicrosoftDocs/office-docs-powershell/issues/3211

Docs Build status updates of commit 43cb211:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Update-CsUserDatabase.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

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

File
Status
Preview URL
Details

skype/skype-ps/skype/Update-CsUserDatabase.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Multiple Public & Secret Key depend on the merchant

Hi
is it possible to make the Secret key and publishable key accept multiple values ?!
for example if we have 3 vendors, each vendor can add his own secret and public key, and assume vendor 1 added them, so when a customer buy his products he will pay through the first P & S keys, when another customer buy products of No 2 vendor, he will pay through the second P & S keys and etc...
is it possible ?!
please respond ASAP
Thank you ...

Hello,
No it's not possible.

Hi, thanks for reply
can you briefly explain why so I can show it to the client
Thank you


question: 2d_vqvae_tutorial.ipynb

Is there a way to use several GPUs for training? I have tried this notebook in kaggle, where one can use two T4 GPUs, but it uses only one.

In general its recommended to use DistributedDataParallel to train with multiple GPUs. There is an example here. I don't think this approach is compatible with notebooks, though, you would have to use a python script.
I think you might be able to use the simpler DataParallel with a Jupyter notebook, but I've not tried myself.


[e2e]: go schedule main adversarial-build-provenance slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2812097211
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.schedule.main.adversarial-build-provenance.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.schedule.main.adversarial-build-provenance.slsa3.yml
Trigger: schedule
Branch: main
Date: Sun Aug  7 09:23:21 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2816807366
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.schedule.main.adversarial-build-provenance.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.schedule.main.adversarial-build-provenance.slsa3.yml
Trigger: schedule
Branch: main
Date: Mon Aug  8 09:25:17 UTC 2022
Tests are passing now. Closing this issue.


add default protocol

Cronjob fails without protocol.
Minio needs http, this should be good with s3://

/override ci/prow/integration-test


When is ANDROID_NDK defined?

I see here the following:
#if defined(ANDROID_NDK) || defined(__BORLANDC__) || defined(__QNXNTO__)

Where is ANDROID_NDK defined? Shouldn't it be some target_compile_definitions in CMakeLists.txt?

Let me be more specific: I am building using dockcross for android-x86_64, where it fails because apparently fseeko64 is not a part of Android x86_64, but fseeko is (see more details and the CI build error here).
I fixed the build with the following patch:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 7f41f04..482f950 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -33,6 +33,10 @@ target_compile_definitions(
     PRIVATE $<$<CXX_COMPILER_ID:MSVC>:_CRT_SECURE_NO_WARNINGS>
 )

+if(ANDROID)
+    target_compile_definitions(tinyxml2 PRIVATE ANDROID)
+endif()
+
 set_target_properties(
     tinyxml2
     PROPERTIES
diff --git a/tinyxml2.cpp b/tinyxml2.cpp
index 7c4e7b7..a568336 100755
--- a/tinyxml2.cpp
+++ b/tinyxml2.cpp
@@ -103,7 +103,7 @@ distribution.
 #if defined(_WIN64)
        #define TIXML_FSEEK _fseeki64
        #define TIXML_FTELL _ftelli64
-#elif defined(__APPLE__) || defined(__FreeBSD__)
+#elif defined(__APPLE__) || defined(__FreeBSD__) || defined(ANDROID)
        #define TIXML_FSEEK fseeko
        #define TIXML_FTELL ftello
 #elif defined(__unix__) && defined(__x86_64__)

Does it make any sense at all, and should I instead try to reuse this ANDROID_NDK? Also would you be open for a PR with that patch (otherwise I'll keep it as a patch step in my project)?


feat(CarbonCharts): Support Carbon Charts

Issue: #
WIP. Investigation into wrapping Carbon Charts inside Magma
Carbon Storybook
What I did

Screenshots (if appropriate):
Checklist

[ ] changeset has been added
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works

How to test

Design feedback:

Focus color when tabbing through legend is still incorrect. Needs to match the light blue we use on other elements.

Looks like we still need a border on the checkboxes in the legend when they're turned off. Otherwise they disappear from view.  Hopefully we can have the border only when they're turned off?

Please use #454545 in light mode.

Please use #FFFFFF in dark mode.

Due to the update to the checkboxes, it looks like it introduced some additional styling issues.

In light mode, the active checkboxes are now visually smaller and missing the 2px border radius, but they're fine in dark mode.
This becomes easier to see when some checkboxes are active and others aren't.
The checkboxes in dark mode are still missing the white outline asked for in the comment above.

Everything is looking good at this point. Can't promise there won't be tweaks down the road. But consider this "Approved" without actually approving the PR.


soc: xtensa: esp32s3: add support for SPIRAM

Add support for external PSRAM for esp32s3.
Test esp32s3 for cache coexistence. Update test documentation.
Add section to allocate memory of WiFi and NET stack in SPIRAM

Could we please wait until https://github.com/zephyrproject-rtos/zephyr/pull/58454 gets merged?


Provide multiple starts for fitting

Consider multiple starting points for the optimization to have a better chance of discovering the global minimum.

One strategy is to use Latin Hypercube Sampling (LHS) to sample the parameters used for input. I've used the pyDOE implementation in the past. Also I remember a conversation with Jens Timmer a few years back who suggested the fitting itself should be done in log space and converted back at the end.


Added fromBytes

Added a "fromBytes" as a counterpart to "toBytes". Also "toBytes" was missing from the readme.
For some reason doco would not regenerate the entire doc output, so I manually added the entries for fromBytes/toBytes. (It is certainly possible I might have been using doco wrong.)

Thanks, looking fine to me!