pushd into current directory cause popd to fail

If you pushd into the current directory, the command will exit successfully but without putting the current directory into the stack, causing the subsequent popd to fail either because a stack mismatch, or because the stack is empty.
This cause rosworkon drone gsg in drone/catkin_ws to exit with exit code.
Test case 1:

Open new terminal.
Run pushd ~/
Run popd
failed with popd: directory stack empty

Test case 2:

Open new terminal.
Run cd /
Run pushd ~/
Run pushd ~/
Run popd, this should cd to ~/ and pop the stack to /, but it cd to / instead and stack is now empty.
Run popd again, stack is empty so command failed with popd: directory stack empty

I this this is a bug on bash, just opened an issue on gnu, will see what they say.
but for the time being, we can add to be beginning of the script:
if [[ $(pwd) -ne ${HOME} ]]; then
  pushd ${HOME}
  pushd_home='true'
fi

And make sure that the immediate next pushd will never be to ${HOME}
Then add at the end of the script:
if [[ ${pushd_home} ]]; then
  popd
fi

why is this specific to the home directory?

Not specific to home, just give that as an example

@Baycken Did you use bash or zsh in your tests?
Everything works as expected in bash.


Returned buildings back to the terrain generation algorithm

Fixes #178

Please play test if you have a chance.

1. Buildings spawning on top of fuel bases
Needs a check to make sure there is no fuel station at the same location
2. Buildings sometimes spawn in view of the player
Might be an issue with love.math.random(200,2000). 200 might not be enough to let them spawn outside of the players field of view? Needs testing.
3. Old buildings should be removed
Same as for the terrain. Doesn't need to be fixed for this PR I guess :wink:
Just as an note: I haven't looked at the code too much.

I'm okay with 1 and 3 but 2 happened just the one time and couldn't be replicated. I'll dig deeper.

I had it at least 3-4 times, especially while flying a bit faster.

Hope someone can have a quick playtest on this one. It's not 100% fixed but fixed enough.

Still sometimes get buildings on top of fuel bases but I don't see any buildings popping in anymore, so that's nice.


Decode test update

Coverage remained the same at 83.231% when pulling 724dc1c5921caba9195d31303640eb6a8ea98763 on rust-av:decode_test_update into 4cbb647643d07279c3d3234344cd7f6da942fa77 on xiph:master.


Last chunk in retry mechanism never gets transferred

While sending the missed chunks, the last chunk in the transfer report never gets sent.

Fixed in the release prior to c75f8f16ce4a7a39d92c6a9f9b8bc0c9e4c39529.


Update silta-examples.md

Few notes for redirect definitions

Should the dollar $ (stop character?) be explained how to use for the from rule?
And also the variables like $request_uri?

@kirkkala that goes into nginx syntax territory and i don't feel confident enough about it to document it yet. This will be a future addition ;)


Change config reference

removed double entry for public IP

@EricBergDE : Thanks for your contribution! The author, @cherylmc, has been notified to review your proposed change.

@EricBergDE Thanks for the correction, Eric! I've reviewed the article to verify the duplication & fix. I'll merge this now.


Add support for UseDefaultCredentials Option

Allow Integrated Windows Authentication to be used when authenticating
to the Exchange server.
I apologize in advance if any part of this pull request is improper. I am very inexperienced with Online Collaboration. I considered creating a JUnit test for the new functionality but I didn't know how I could test the code without a server to contact. I tried to minimize the impact of this code so it only affects users who have enabled the UseDefaultCredentials feature. I disabled it by default to mirror the .NET API.

Hi @LukeWage, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

Current coverage is 10.42%

Merging #517 into master will decrease coverage by -0.01% as of cac2222

@@            master    #517   diff @@
======================================
  Files          550     550
  Stmts        20436   20442     +6
  Branches      2626    2629     +3
  Methods          0       0
======================================
  Hit           2132    2132
- Partial        153     154     +1
- Missed       18151   18156     +5

Review entire Coverage Diff as of cac2222

Powered by Codecov. Updated on successful CI builds.

@LukeWage, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, AZPRBOT;


System restore point

If anything goes wrong and any system tools stops working, restore point helps recover the windows installation.
Todo:

[ ] Add a prompt to create restore point before launching GUI
[ ] Check for existing restore points created by this tool in last few minutes and if exists prompt for user

Thank you for your work....  Is there any way to "uninstall" your software and leave Windows as it was before apply your script?
Thankyo

Thank you for your work.... Is there any way to "uninstall" your software and leave Windows as it was before apply your script?

As of now, No. But it's doable. Please feel free to open a new issue. I'll work on it after the holidays.


Disable default outbound connectivity on all subnets

Benefit/Result/Outcome
This moves existing subnets off default outbound access. Also, this prevents new and future subnets from having default outbound access.
Description
SFI for MLZ resources.
Acceptance Criteria

SFI instructions: https://msazure.visualstudio.com/AzureWiki/_wiki/wikis/AzureWiki.wiki/673113/-SFI-NS2.6.1-Move-off-default-outbound-access-feature-to-other-method-of-outbound-connectivity?anchor=removing-default-outbound-access-ips


Instances are killed after 600 seconds. Lack of Documentation and Configurability for --auto-shutdown-after.

Lack of Documentation and Configurability for --auto-shutdown-after Parameter in EdgeDB
Summary
I've encountered significant operational challenges due to the lack of documentation and configurability for the --auto-shutdown-after parameter in EdgeDB. This has led to unexpected auto-shutdown behaviors that are particularly problematic in scenarios where constant availability and low latency are crucial.
Detailed Description
EdgeDB instances in my setup are unexpectedly shutting down after a certain period of inactivity, causing a delay of 5-10 seconds upon the first request after the shutdown. This delay is detrimental to the performance and user experience of my application. Furthermore, the auto-shutdown also disrupts access to the EdgeDB UI, requiring manual intervention to restart the service or trigger an EdgeQL query to reactivate it.
No Google search led me to anything, which is definitely a bummer. While investigating, I lost crucial time debugging the "unexpected shutdowns". I looked through the code in this repo, and found the guilty parameter. --auto-shutdown-after. A quick $ top revealed that it was indeed passed to the running instances, with value 600, or 10min. I found a discussion (EdgeDB GitHub Discussion #4298) mentioning that --auto-shutdown-after can't be altered except by running EdgeDB with the --foreground flag, which sets --auto-shutdown-after=-1. However, running EdgeDB outside of a systemd service is not viable for production environments.
Steps to Reproduce

Set up EdgeDB in a production environment.
Observe the automatic shutdown of EdgeDB instances after a period of inactivity.
Experience delays in response time and UI access upon reactivation.

Relevant Logs and Discussions

Gist with Logs
EdgeDB GitHub Discussion #4298

Proposed Solution

Documentation: Update the EdgeDB documentation to include information about the --auto-shutdown-after parameter, its default behavior, and its impact on EdgeDB instances.
Configurability: Introduce a way to configure the --auto-shutdown-after parameter value, either through service files or server configuration (similar to existing parameters like session_idle_timeout or session_idle_transaction_timeout). This would provide much-needed flexibility for different production scenarios.

Conclusion
The current lack of documentation and configurability for the --auto-shutdown-after parameter significantly hampers the usability of EdgeDB in production environments where constant availability and low latency are essential. Addressing these issues would greatly enhance the operational experience for users like myself.

Forgot to mention, but let's say in a situation where my app is not very busy, like during off-peak hours, and there's only one request every 10 minutes or so. In this case, each of these requests could end up taking an extra 5-10 seconds because of the auto-shutdown. This is a significant concern for maintaining smooth user experience.

I'm open to any interim solutions or workarounds that you might suggest. If there's a temporary fix or a best practice to mitigate this issue until a permanent solution is implemented, that would be greatly appreciated

@bastien8060 Bastien, are you using edgedb CLI tooling to run EdgeDB in prod? We do use auto-shutdown-after parameter but only in development mode to allow people to run multiple versions of EdgeDB side by side without worrying about RAM/CPU.

Hi, and thanks a lot for the reply! I did a bit more research on my end in the meantime! Seems like my instances are still restarting (receiving signal 15) every so often, despite overriding auto shutdown to -1. Something else might be at play. I am on the latest version of both cli and edgedb. I ran the simple installation guide from edgedb quickstart.
On a side thought, EdgeDB doesn't run in development mode by default, right? Or should I try installing EdgeDB like in the bare-metal deployment guide? I have an edgedb.toml file with all my migrations in a dbschema folder, and edgedb project info shows my instance. i assume from that I have a project. Are projects not intended for development?
Cli: 4.0.2+be1da74
Server: 4.0+d568f08

@bastien8060 Bastien, are you using edgedb CLI tooling to run EdgeDB in prod? We do use auto-shutdown-after parameter but only in development mode to allow people to run multiple versions of EdgeDB side by side without worrying about RAM/CPU.
The reason why auto-shutdown-after parameter isn't documented is because it's only used for dev mode, there don't seem to be other good use cases for it (especially in prod).

But about your comment, it does make a lot of sense! I'm guessing I should follow the docs here then: https://www.edgedb.com/docs/guides/deployment/bare_metal. Correct?

Yes, that's right, @bastien8060. The CLI instances are intended for development only. When you install using the instructions at the guide you cited, you won't experience the auto-shutdown.

Hi @raddevon :),
I have a same issue, (I think I did something wrong with bare metal set up) how to check if my edge db is running on production mode?


Extended linking kinds

This RFC proposes adding a kind for object files which are passed directly to the linker.
Please bikeshed vigorously on the name of the kind.
rendered

cc @alexcrichton

I'm considering extending this RFC to also add kind=resource for foo.res resource files and kind=object for foo.obj object files. Would anyone be interested in these additions?
cc @danielkeep @DroidLogician

@retep998 At that point, wouldn't kind=dont_look_dont_touch_just_pass be better?  Would kind=resource and kind=object do anything other than just passing the files along?  Also, whilst object should map to other linkers, what should rustc do when it's told to link a resource, and the backend is ld?  (I'm asking because I really have no idea.)
All that having been said: being able to link in resources and object files without having to use the gcc crate to build a fake static library first would be nice.

I'd kinda prefer kind=object and kind=resource since they are explicit about your intent, and they also don't allow completely arbitrary linker arguments to be passed. It's actually kinda weird in that you can do rustc main.rs -l dylib=/out:foo and end up with a binary called foo.lib.

Just a bit of clarification on how resource files get passed in.

The main difference between using the MS resource tools and the GNU  tools is that MS rc generates a ".res" file in a special binary resource  format, which can be passed directly to MS link, while the GNU linker  ld only supports resources in ".o" (same as ".obj") format. source

So this means for msvc you'd use kind=resource with a .res file you got a from a .rc file using rc.exe. For gnu you'd use windres.exe to create a .o from your .rc and pass it with kind=object. Does this seem fine?

the kind=object seems more elegant to me. Rather than get into the details of how rustc interacts with the linker, it is about operating in a mode where rustc does the absolute minimum and the user is then responsible for linking. That seems like a good scenario to be able to handle.
I am less convinced by the utility of kind=resource, aiui, kind=object would have the same effect. Although I see the point about intent, it seems a bit sub-optimal to add such a facility which is targeted at a single linker on a single platform.

@nrc We could make it so that with both gnu and msvc you'd pass your .rc file using kind=resource and then rustc does all the hard work of shelling out to rc.exe or windres.exe and passing it along appropriately to the linker.

This sentence seems to be the key motivation, but I don't understand it: "kind=static doesn't work because it causes rustc to bundle the library into the *.rlib instead of passing it along to the linker, which results in rustc not looking in the standard library paths for the library."
What is the difference between "passing it along to the linker" and not doing that? Surely the code is linked either way right?

@brson The linker has a set of paths that it looks in for libraries. rustc does not know what those paths are. Suppose I have a static library located in one of those folders that the linker normally looks in for libraries. If I use kind=static, rustc will look for the library instead of the linker. Since rustc doesn't know about the path where the static library is, it will fail to locate it. Meanwhile using kind=betterstatic, rustc simply tells the linker to link that library, and at link time the linker looks through its paths and does find the library, and things end up working.

Thanks for the explanation.
As an alternative proposal, what if we taught rustc about the pre-defined linker paths? The separation between the linker and compiler in rustc is artificial, a historical accident. If it worked the way we wished the linker would be integrated into rustc and rustc would know whatever the linker knows.
With the actual state of the world where linkers are ancient monoliths, adding this knowledge to rustc would not be simple, but there's probably a way.

When bundling another library into a Rust .rlib instead of passing it to the linker, there are other issues as well. For example if that library was compiled with LTCG, passing it to the linker will work fine, but if rustc bundles it into the .rlib the LTCG data is ruined. https://github.com/rust-lang/rust/issues/26003
Actually, how about we try coming up with arguments for when kind=static would be better than kind=betterstatic.

Since the library is bundled into the .rlib, you don't have to keep the library around for link time, so that is one less thing to pass to the linker. Although this isn't useful in standard Cargo scenarios since the library will always be around for link time anyway and you're not manually invoking the linker.

Can anyone think of any other reasons?

I updated the RFC to add kind=object. I didn't add kind=resource as it is fairly simple to use rc.exe and cvtres.exe for msvc or windres for mingw to create object files that can be passed along to the linker.

Note that for resource files, the user cannot simply use lib.exe to create a .lib from the compiled .obj. A resource file compiled into a .obj and passed to the linker will work correctly, while if it is compiled into a .lib, it will no longer work. Thus there is a very real and legitimate need for kind=object.

Ping @rust-lang/tools, this RFC seems to've stalled. Can someone summarize the current state of play and try to make progress?

static-nobundle got implemented via the dllimport RFC, so at the moment this RFC is just proposing to add linking to object files.

@retep998 Looks like the RFC hasn't been updated with that more narrow focus/motivation?

Pushed a commit to narrow the focus of the RFC.

@retep998 Thanks!

@retep998 thanks for updating the RFC. After reading it though I feel like it may be a bit too broad to solve a specific problem? The motivation here seems to be supporting resource files on Windows better, but the solution, adding kind=object, to me seems overly broad for such a problem. Is there perhaps something more focused and perhaps even more first class that we can do to support resource files?
I'd personally have questions about the RFC as-listed, for example how are object files actually found and passed to the linker? The linker AFAIK doesn't use -L on all platforms to search for object files, so actual paths to object files need to be passed. Is the compiler searching for object files? Does the object kind specify a full path? (if a full path then this is inconsistent with other #[link] attributes.

The linker AFAIK doesn't use -L on all platforms to search for object files, so actual paths to object files need to be passed

I gave this a test and link.exe searches your /LIBPATH stuff for all input, not just libraries, so that's fine. ld however only searches -L for -l stuff and -l seems to ignore object files. Ugh.
The other use case I mentioned, using object files to prioritize over libraries, also seems like a link.exe specific thing according to gcc's documentation, which makes me wonder how lld acts in that case...
I guess it looks like I'll be rewriting the RFC again to just focus on resource files directly because object files with ld are a pain.

Ok cool if we don't want support for arbitrary object files then focusing on just resource files sounds good to me. I wonder though if could perhaps go for a bit more of an ergonomic inclusion, as well as lifting some requirements? I could imagine, for example:

Could we find resource files similarly to how we find source code? That is if you say foo.rc it looks in the current directory of the current module for foo.rc? Or are foo.rc files generated and not handwritten?
First off, is there a use case for allowing resource files in libraries? If not then we could just make that a hard error and not worry about saving paths or such.
If we do want to allow resource files in libraries, perhaps we could support them explicitly without having to save off paths? That is, we could just put the rc file into the rlib and then whenever we link the rlib we take it out and pass it manually to the linker.

Could we find resource files similarly to how we find source code? That is if you say foo.rc it looks in the current directory of the current module for foo.rc? Or are foo.rc files generated and not handwritten?

Allowing resource files to be generated by a build script would be desirable, so anything that prevents that from working probably wouldn't be a good idea.

First off, is there a use case for allowing resource files in libraries? If not then we could just make that a hard error and not worry about saving paths or such.

A library may wish to bring along a resource file to provide some things that it needs. For example a UI library may want to define some resources so that it can use them. So resource files from a library definitely seems like a worthwhile use case to support.

If we do want to allow resource files in libraries, perhaps we could support them explicitly without having to save off paths? That is, we could just put the rc file into the rlib and then whenever we link the rlib we take it out and pass it manually to the linker.

We don't necessarily have to compile the resource file immediately, saving it somewhere and later compiling it right before passing it to the linker is fine. However what we cannot do is put the compiled resource file in a library and pass that library to the linker, because the linker will fail to recognize the compiled resource file in the library.

Ok so it seems to be like we may not want to use #[link] for this if we're just slurping up resource files (either handwritten or generated) because that's related moreso to extern blocks and linking native libraries.
Perhaps something like:
#[windows_resource = "foo.rc"]
extern {} // ??

That way if you want to include a file relative to a source file you can do so. If you want to generate it via a build script then you can do so and include that via include!
I kinda like the idea of not running rc and/or windres until the very end. That way we just put the files in rlibs and forget about them. At the end we extract all resource files, compile them all, and pass them all to the linker.
I'm not really sure where or how to precisely specify the inclusion of a resource file, though. We could maybe slap it on a module or something like that, but it seems like almost a hack no matter how we slice it unfortunately.

@alexcrichton Oh, there might actually be an issue with storing resource files to compile them later, because when resource files are compiled they pull in other files around them, like icons and manifests and stuff. If you store the rc then those other files won't be around when you need them. So you'll have to compile the resource file on the spot and then somehow keep track of or store the compiled .res file to later pass to the linker.

What are your thoughts on how resource files are declared? I feel like #[link] is the wrong place to describe exact paths to files (as that's not elsewhere what it's used for today) and a custom attribute here is warranted, but I'm curious what you think.

I personally don't care too much about what the syntax for declaring resource files is. If someone proposes a better syntax that others agree on, then I'll gladly update the RFC.

Ok well in that case my proposal is:
#[windows_resource = "foo.rc"]
extern {}

The foo.rc file here is located with the same logic as #[path] (e.g. in the same dir by default) and the compiler also verifies that the extern block is empty. I feel that this is more suitable than #[link] because it's using the existing infrastructure we have today to find source files (which I'm currently under the impression an rc file is), and it doesn't reuse #[link] which would have very different lookup semantics.
This also differentiates itself as a windows-specific extension (like #![windows_subsystem]) as opposed to throwing it into the ring with #[link]

But why does it need an extern block? Why not as a crate attribute?

@alexcrichton What would be the recommended way to link a resource file that is generated using a build script using your attribute?

I kinda agree with @retep998: linking in an object file (not necessarily resources) is just something you sometimes need to do when building for a custom target.
Right now you basically have to dump linker args with -Zprint-link-args and then run it yourself, which soon will only be possible on nightly.

@Boscop with a crate attribute it's difficult to include something dynamically generated, such as (to answer @retep998's question as well) with an extern block you can generate $OUT_DIR/foo.rs with the extern contents and then in your code include!(concat!(env!("OUT_DIR"), "/foo.rs"));
@vadimcn just to clarify, but you're pushing back on the trimming down of this RFC from object files to just resource files? If so, can you clarify why archives wouldn't work? (e.g. why raw object files must be used)

Having to generate a rust file in order to link to a generated resource file seems rather convoluted. I'd rather have a rustc flag to link in a resource file and cargo would support some sort of cargo:windows_resource output from build scripts to specify that flag.

@alexcrichton: I liked the part about linking object files in general, not just outputs from windres/cvtres.  On more than one occasion during my hacking I had wished I could pass objects directly to Rust compiler, like I can do with GCC.   It would also let us deal with resources, so we'd be killing two birds with one stone :)

Agreed, being able to just link to object files would be nice. Maybe rustc could look through -L paths for object files. Since those won't come from system directories, it might be OK not to rely on the linker for finding those.

I would also be ok with linking arbitrary object files with logic that looks like:

The compiler finds an object file (by path) via searching
If building an rlib, the compiler puts the object in the rlib
If building an executable, just pass the object
If building an executable with an object in an rlib, take the object out, modify the rlib, and then pass those all to the linker

I don't feel that it's strictly necessary, but I'm comfortable with those semantics and if we want to go back to arbitrary object files that'd be ok.

Since those won't come from system directories, it might be OK not to rely on the linker for finding those.

Unfortunately, this is wrong! Due to the overriding nature of object files in the msvc toolchain, msvc actually provides a set of object files to override certain behavior. If you want to link to one of those object files, the linker must be able to link to those object files, and expecting the rlib to adequately inform rustc of where those object files is just not going to work.

Discussed at the @rust-lang/tools triage a few days ago, the conclusion we reached were:

It seems prudent to refocus this RFC on object files instead of just resource files. In addition to what's been brought up so far we'd have to otherwise expose configuring the resource file compiler path and also arguments to the resource file compiler, both of which are just more easily done if we operate through object files.
We should use -L for lookup paths to object files, and the compiler itself should be responsible for finding these files. If an extension is missing the compiler can look for foo.o or foo.obj, but if an extension is already specified the compiler will look for that file instead.

Does that make sense? How does that sound to you @retep998?

We should use -L for lookup paths to object files, and the compiler itself should be responsible for finding these files.

So what happens if I want to link a system object file, like one of the object files provided by VC++?

IMO, the single namespace for native libs (due to using lookup paths) is already a problem. Having to deal with a single namespace for objects (again, due to the proposed use of lookup paths) doesn't seem like a good idea if it's not a problem to specify full paths.

@retep998 I'm not sure, you tell me what would happen!
@jmesmon I think it'd be fine to accept full paths on the command line, but objects may also want to be encoded into the source file itself in which case a full path may not always be desired.

@alexcrichton Well, if rustc were responsible for finding the object files and not the linker, I'd be screwed. This is the same thing that happened with kind=static, where I couldn't link to static system libraries.

Ok, do you have a proposal to fix that problem?

The problem is that link.exe is the only linker that supports searching library paths for arbitrary object files. ld will search for libfoo if you specify -lfoo so that won't do to find foo.o while just passing foo.o to ld won't search the library paths. Here are a couple options I thought of:

gnu and msvc have somewhat different behavior. While they will both attempt to pass absolute paths when possible and for relative paths they will try to locate the object file to pass an absolute path, gnu will simply error if rustc cannot find the object file, while msvc will trust that the object file can be found in one of the library paths and leaves it up to the linker to actually error.
msvc has its own special kind specifically for system object files. If other linkers end up supporting this, we can extend this kind to those linkers.

Could you elaborate on the motivation for system object files? Could that perhaps get punted to a future RFC?
Could you also elaborate what your first option would look like? E.g. the specifics of lookup.

I'm going to close this RFC for the time being, to keep our queue clean, as it's waiting on follow up from its author, @retep998. Please feel free to reopen if/when you're ready to pick this topic back up.


[release-1.21] Bump grpc-go and x/net

Manual cherrypick required.
#50236 failed to apply on top of branch "release-1.21":
Applying: Bump grpc-go and x/net
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump grpc-go and x/net
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

opened, will fix.

Little extra work required -> https://github.com/istio/istio/pull/50259 should do it.

Closed by https://github.com/istio/istio/pull/50259


Support nav_msgs/Path in Webviz

Summary
Add support for the message nav_msgs/Path to webviz
Test plan
I built locally and tested with a bag with a Path in it. Here's a gif of the Path  in Webviz

Versioning impact
Might recommend a patch version at most

Also seems like there's an issue with the test here. Not sure how to fix
{ CredentialsError: Missing credentials in config
    at IncomingMessage.<anonymous> (/home/circleci/project/node_modules/aws-sdk/lib/util.js:865:34)
    at IncomingMessage.emit (events.js:203:15)
    at IncomingMessage.EventEmitter.emit (domain.js:448:20)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  message: 'Missing credentials in config',
  retryable: false,
  time: 2021-03-04T21:46:00.662Z,
  code: 'CredentialsError',
  originalError:
   { message: 'Could not load credentials from any providers',
     retryable: false,
     time: 2021-03-04T21:46:00.662Z,
     code: 'CredentialsError' } }

@vidaaudrey added sample data here https://drive.google.com/file/d/1xEoG3L6u5tPVwijMh_A1VnzSvQTCVpSB/view?usp=sharing
Still a little confused about how to make a story though? I see this using the fixture but I don't see how to use it?

Good to know. thanks for the update. Should I close the PR when it makes it in in the open source build?

Yeah, you could close it later. I will tag you.
On Mar 18, 2021, at 6:29 PM, Carl Saldanha @.***> wrote:

Good to know. thanks for the update. Should I close the PR when it makes it
in in the open source build?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cruise-automation/webviz/pull/592#issuecomment-802443905,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACT5KNJDFFF2TXDSEEBNUDTTEKSJFANCNFSM4YT4HUWA
.

@cjds FYI this PR here added the support for nav_msgs/Path. Will close this PR now. Let me know if you have any questions.

I pulled the docker image from https://hub.docker.com/r/cruise/webviz
It doesn't draw anything on the 3D plot.
Also, I ran into this issue once:

Try Foxglove Studio, which supports nav_msgs/Path: https://foxglove.dev/docs/studio/panels/3d#path


Update rautomation.gemspec

@jarmo Could you review and merge the code

No Jarmo.
Thank you
Regards,
Pradeep.
On Thu, 31 Jan 2019 at 5:08 PM, Jarmo Pertman<EMAIL_ADDRESS>wrote:

Any information regarding this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jarmo/RAutomation/pull/123#issuecomment-459313447,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcbbPmy6cea7OUBTD_SbDq4kB3pu_bdKks5vItWrgaJpZM4Z5mUx
.

Done in version 1.0.0


[Bug]: The inference speed of vllm running command-r-plus-gptq is very slow

Your current environment
Collecting environment information...
PyTorch version: 2.3.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.29.3
Libc version: glibc-2.35

Python version: 3.10.14 (main, May  6 2024, 19:42:50) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-6.5.0-35-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA L20
GPU 1: NVIDIA L20
GPU 2: NVIDIA L20
GPU 3: NVIDIA L20

Nvidia driver version: 550.67
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      46 bits physical, 57 bits virtual
Byte Order:                         Little Endian
CPU(s):                             80
On-line CPU(s) list:                0-79
Vendor ID:                          GenuineIntel
Model name:                         Intel(R) Xeon(R) Silver 4316 CPU @ 2.30GHz
CPU family:                         6
Model:                              106
Thread(s) per core:                 2
Core(s) per socket:                 20
Socket(s):                          2
Stepping:                           6
CPU max MHz:                        3400.0000
CPU min MHz:                        800.0000
BogoMIPS:                           4600.00
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 invpcid_single intel_ppin ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect wbnoinvd dtherm ida arat pln pts vnmi avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid fsrm md_clear pconfig flush_l1d arch_capabilities
Virtualization:                     VT-x
L1d cache:                          1.9 MiB (40 instances)
L1i cache:                          1.3 MiB (40 instances)
L2 cache:                           50 MiB (40 instances)
L3 cache:                           60 MiB (2 instances)
NUMA node(s):                       2
NUMA node0 CPU(s):                  0-19,40-59
NUMA node1 CPU(s):                  20-39,60-79
Vulnerability Gather data sampling: Mitigation; Microcode
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI Syscall hardening, KVM SW loop
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] torch==2.3.0
[pip3] torchvision==0.18.0
[pip3] triton==2.3.0
[pip3] vllm_nccl_cu12==<IP_ADDRESS>.4.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
[conda] torch                     2.3.0                    pypi_0    pypi
[conda] torchvision               0.18.0                   pypi_0    pypi
[conda] triton                    2.3.0                    pypi_0    pypi
[conda] vllm-nccl-cu12            <IP_ADDRESS>.4.0             pypi_0    pypiROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.4.2
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0	GPU1	GPU2	GPU3	CPU Affinity	NUMA Affinity	GPU NUMA ID
GPU0	 X 	PIX	SYS	SYS	0-19,40-59	0		N/A
GPU1	PIX	 X 	SYS	SYS	0-19,40-59	0		N/A
GPU2	SYS	SYS	 X 	PIX	20-39,60-79	1		N/A
GPU3	SYS	SYS	PIX	 X 	20-39,60-79	1		N/A

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

🐛 Describe the bug
 docker run -d --restart always --shm-size 10.24gb --gpus all -v /data/llm/models:/root/.cache/huggingface -e MODEL=/root/.cache/huggingface -e CUDA_VISIBLE_DEVICES=0,1,2,3 -e HF_ENDPOINT=https://hf-mirror.com -p 8000:8000 --name vllm vllm/vllm-openai:latest --model /root/.cache/huggingface/c4ai-command-r-plus-GPTQ --max-model-len 96336 --quantization marlin --tensor-parallel-size 4 --gpu-memory-utilization 0.98 --served-model-name c4ai-command-r-plus

When running the command-r-plus-gptq model with vllm, the gpu-memory-utilization value is 0.95, and the video memory usage is very low. The inference speed is very slow, as shown in the figure below:

It looks like you are running batch size 1. Try submitting more requests or using tensor parallelism


Implement Subcategories

I want to have categories be hierarchical, so that a category can have a parent category (which can have a parent category, etc.)
Syntactically I think :: would make the most sense.
You'd have e.g. a category uni::math::calculus::weep that allows you to track all the time you spend weeping in relation to your calc class, categorized as math as part of your university curriculum.
The upside would be that you could track as granularly as you wanted and still maintain categorization e.g. to get easy high-level summaries.
So if you have the following time totals tracked:

uni: 10h
uni::math: 20h
uni::math::calc::weep: 5h

then the total for summarizing by uni would be 35h, the total for summarizing by uni::math would be 25.

Alternatively: go more into the regex-direction:

retain categories as a flat list (mostly for naming, coloring)
let users write regexes anywhere that filtering is used
user can choose to adhere to any category naming scheme they want and write the appropriate regexes.
in this case goals would apply to another config section called 'groups' or something, characterized by regex(es) instead of categories


Images

These are the 3 images that I found that were greater than 1 MB.  I ended up grabbing new screen shots with a  smaller  window size  because simply changing image dimensions (first commit) resulted in a fuzzy image.  It might be better to try the compression route with Squoosh.

Very nice!


When typing inputs shows many $<5> on "SSH Secure Shell Client"

It shows many $<5>when I used "SSH Secure Shell Client" to connect to Linux box and do things(Get-Host) below:

Steps:
$ git clone --recursive https://github.com/PowerShell/PowerShell.git

$ sh -c 'echo "deb [arch=amd64] http://apt-mo.trafficmanager.net/repos/dotnet/ trusty main" > /etc/apt/sources.list.d/dotnetdev.list'
$ apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893
$ apt-get update
$ apt-get install dotnet=<IP_ADDRESS>425-1

$ apt-get install g++ cmake make lldb-3.6 strace

$ apt-get install libpam0g-dev libssl-dev libcurl4-openssl-dev libboost-filesystem-dev

$ cd PowerShell
$ dotnet restore
$ ./build.sh
$ ./bin/powershell.sh

Is there a proper resolution for this with Win32 OpenSSH or is the official answer to use putty?

It's beta software, and there is not a resolution I know of. I would recommend following up with the Win32 OpenSSH project. Please do reference this issue in your bug report.


Package compilation problem

Hi,
Is me again, sorry for keep bugging. I would like try out this socially_normative_navigation and I face some issue in compiling and using it. I tried compiling this package using catkin_make -DCATKIN_WHITELIST_PACKAGES="socially_normative_navigation" and i received this:
CMake Error at /opt/ros/indigo/share/catkin/cmake/catkin_workspace.cmake:95 (message):   This workspace contains non-catkin packages in it, and catkin cannot build   a non-homogeneous workspace without isolation.  Try the   catkin_make_isolated' command instead. Call Stack (most recent call first):   CMakeLists.txt:63 (catkin_workspace)
fully output in the terminal is in file (catkin_make_record) below.
catkin_make_record.txt
So I tried using catkin_make_isolated -DCATKIN_WHITELIST_PACKAGES="socially_normative_navigation".
The build seems okay then but after I tried running roslaunch snn_launchers lobby.launch, it failed to run. The output in the terminal is shown in the log file (roslaunch_log) below.
roslaunch_log.txt
I am not sure which dependencies that I have missed out and how to really use the package. May you provide me some insights on the issue? Thanks a lot.

I do not understand the compile problem, why dont you use simple catkin build -c to build your workspaces.
For running, it is missing some SPENCER robot files (the model files etc). I still need to cleanup the code to remove those. But i believe as long as you have your robot setup with a transform publisher with the standard frames base_footprint and odom then it should be fine.

Thanks for your reply. Sorry for not using catkin build. I just tried it out again and it built successfully. I ran roslaunch snn_launchers lobby.launch again and get the same error output.
roslaunch_log2.txt
Ya, I think is some missing SPENCER files. It's okay, I will try to implement other components like the social_compliance_layer.

Thanks for contribution. When I ran "roslaunch snn_launchers lobby.launch",I get an error:
ResourceNotFound: spencer_description
Where can I get the missing SPENCER files?


Set up some baseline stuff for this repo.

Enable CircleCI

Enable linting (and fix a lint error)

Enable Mergify

Enable codecov.io

Add a Makefile and CONTRIBUTING.md

Thanks so much for doing that Martin - it would've taken me a big chunk of time to figure out how to do this right.


1inch quotes failing

Overview
currently in Prod, we are unable to fetch 1inch quotes for swapper.
This error reads in the console: Failed to load resource: net::ERR_NAME_NOT_RESOLVED
and the error message "An error occurred getting a quote" is displayed to the user.
References and additional details
https://github.com/shapeshift/web/assets/94998097/e938d473-5723-499a-9691-18d018f2ccfb
Acceptance Criteria
1Inch quotes working again.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

we moved to their low tier b/c they want us to pay 10x 0x.

We probably also need to migrate our API key as well.
Its worth considering if we should remove the error message and just not display 1inch if no quote is available since we expect intermittent errors that really shouldnt be user facing.  @twblack88 thoughts?

@twblack88 - discussed with eng team today, and the consensus is that since lifi include 1inch and there is significant overlap with 0x that it would be best to just disable 1inch in production.  I want to make sure you are good with this before we move forward.

yeah is fine.


How to include images?

Hello,
Thank you for your very nice template!
I am trying to include an image, but I get an errors
Array is empty

Array index out of bounds (index: 1, len: 0)

when I do that?
I literally just added a #image("myimage") to a section.
Here is the full document
#import "@preview/diatypst:0.1.0": *

#show: slides.with(
  title: "Title", // Required
  subtitle: "Subtitle",
  date: "29.08.2024",
  authors: ("Me"),

  // Optional Styling
  ratio: 16/9,
  layout: "medium",
  title-color: aqua.darken(50%),
  footer: true,
  counter: true,
)

#outline()

= Section

== Sub-section

Remove this text to fix the issue.

#image("myimage.jpeg")

Hi,
thanks for the heads up and sorry for the delay. It seems to be a problem with the counter. As a short term fix, you can just include a slide afterwards (with a new Heading) and at least for me that solves the problem. I'll try to fix the problem

Should be closed with the new version 0.2


Inquiry About Project Deployment

I'm interested in deploying your project, but I’m a bit unclear about the steps involved. Could you please provide some guidance or documentation on how to set up and deploy the project?

Thanks for your interest in the project. I just updated the README with detailed instructions on how to configure and deploy it. Take a look at it.
If you have more questions or need help, feel free to contact me.


allow export line

some people want to declare vars and then export them like this:
SOME=thing
export SOME
this pull request will allow that and even validate that the var is set

Thanks!


6800XT Stable Diffusion (Automatic1111) Black Screen Reboot

I'm on ROCm 5.6.0
Linux kernel 6.5.0-1-MANJARO
ROCm info output:
ROCk module is loaded
=====================
HSA System Attributes
=====================
Runtime Version:         1.1
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE

==========
HSA Agents
==========
*******
Agent 1
*******
  Name:                    AMD Ryzen 7 7700X 8-Core Processor
  Uuid:                    CPU-XX
  Marketing Name:          AMD Ryzen 7 7700X 8-Core Processor
  Vendor Name:             CPU
  Feature:                 None specified
  Profile:                 FULL_PROFILE
  Float Round Mode:        NEAR
  Max Queue Number:        0(0x0)
  Queue Min Size:          0(0x0)
  Queue Max Size:          0(0x0)
  Queue Type:              MULTI
  Node:                    0
  Device Type:             CPU
  Cache Info:
    L1:                      32768(0x8000) KB
  Chip ID:                 0(0x0)
  ASIC Revision:           0(0x0)
  Cacheline Size:          64(0x40)
  Max Clock Freq. (MHz):   5573
  BDFID:                   0
  Internal Node ID:        0
  Compute Unit:            16
  SIMDs per CU:            0
  Shader Engines:          0
  Shader Arrs. per Eng.:   0
  WatchPts on Addr. Ranges:1
  Features:                None
  Pool Info:
    Pool 1
      Segment:                 GLOBAL; FLAGS: FINE GRAINED
      Size:                    31974820(0x1e7e5a4) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
    Pool 2
      Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
      Size:                    31974820(0x1e7e5a4) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
    Pool 3
      Segment:                 GLOBAL; FLAGS: COARSE GRAINED
      Size:                    31974820(0x1e7e5a4) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
  ISA Info:
*******
Agent 2
*******
  Name:                    gfx1030
  Uuid:                    GPU-e0ce170bfa1769dd
  Marketing Name:          AMD Radeon RX 6800 XT
  Vendor Name:             AMD
  Feature:                 KERNEL_DISPATCH
  Profile:                 BASE_PROFILE
  Float Round Mode:        NEAR
  Max Queue Number:        128(0x80)
  Queue Min Size:          64(0x40)
  Queue Max Size:          131072(0x20000)
  Queue Type:              MULTI
  Node:                    1
  Device Type:             GPU
  Cache Info:
    L1:                      16(0x10) KB
    L2:                      4096(0x1000) KB
    L3:                      131072(0x20000) KB
  Chip ID:                 29631(0x73bf)
  ASIC Revision:           1(0x1)
  Cacheline Size:          64(0x40)
  Max Clock Freq. (MHz):   2575
  BDFID:                   768
  Internal Node ID:        1
  Compute Unit:            72
  SIMDs per CU:            2
  Shader Engines:          4
  Shader Arrs. per Eng.:   2
  WatchPts on Addr. Ranges:4
  Features:                KERNEL_DISPATCH
  Fast F16 Operation:      TRUE
  Wavefront Size:          32(0x20)
  Workgroup Max Size:      1024(0x400)
  Workgroup Max Size per Dimension:
    x                        1024(0x400)
    y                        1024(0x400)
    z                        1024(0x400)
  Max Waves Per CU:        32(0x20)
  Max Work-item Per CU:    1024(0x400)
  Grid Max Size:<PHONE_NUMBER>(0xffffffff)
  Grid Max Size per Dimension:
    x<PHONE_NUMBER>(0xffffffff)
    y<PHONE_NUMBER>(0xffffffff)
    z<PHONE_NUMBER>(0xffffffff)
  Max fbarriers/Workgrp:   32
  Pool Info:
    Pool 1
      Segment:                 GLOBAL; FLAGS: COARSE GRAINED
      Size:                    16760832(0xffc000) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       FALSE
    Pool 2
      Segment:                 GROUP
      Size:                    64(0x40) KB
      Allocatable:             FALSE
      Alloc Granule:           0KB
      Alloc Alignment:         0KB
      Accessible by all:       FALSE
  ISA Info:
    ISA 1
      Name:                    amdgcn-amd-amdhsa--gfx1030
      Machine Models:          HSA_MACHINE_MODEL_LARGE
      Profiles:                HSA_PROFILE_BASE
      Default Rounding Mode:   NEAR
      Default Rounding Mode:   NEAR
      Fast f16:                TRUE
      Workgroup Max Size:      1024(0x400)
      Workgroup Max Size per Dimension:
        x                        1024(0x400)
        y                        1024(0x400)
        z                        1024(0x400)
      Grid Max Size:<PHONE_NUMBER>(0xffffffff)
      Grid Max Size per Dimension:
        x<PHONE_NUMBER>(0xffffffff)
        y<PHONE_NUMBER>(0xffffffff)
        z<PHONE_NUMBER>(0xffffffff)
      FBarrier Max Size:       32
*******
Agent 3
*******
  Name:                    gfx1036
  Uuid:                    GPU-XX
  Marketing Name:          AMD Radeon Graphics
  Vendor Name:             AMD
  Feature:                 KERNEL_DISPATCH
  Profile:                 BASE_PROFILE
  Float Round Mode:        NEAR
  Max Queue Number:        128(0x80)
  Queue Min Size:          64(0x40)
  Queue Max Size:          131072(0x20000)
  Queue Type:              MULTI
  Node:                    2
  Device Type:             GPU
  Cache Info:
    L1:                      16(0x10) KB
    L2:                      256(0x100) KB
  Chip ID:                 5710(0x164e)
  ASIC Revision:           1(0x1)
  Cacheline Size:          64(0x40)
  Max Clock Freq. (MHz):   2200
  BDFID:                   28160
  Internal Node ID:        2
  Compute Unit:            2
  SIMDs per CU:            2
  Shader Engines:          1
  Shader Arrs. per Eng.:   1
  WatchPts on Addr. Ranges:4
  Features:                KERNEL_DISPATCH
  Fast F16 Operation:      TRUE
  Wavefront Size:          32(0x20)
  Workgroup Max Size:      1024(0x400)
  Workgroup Max Size per Dimension:
    x                        1024(0x400)
    y                        1024(0x400)
    z                        1024(0x400)
  Max Waves Per CU:        32(0x20)
  Max Work-item Per CU:    1024(0x400)
  Grid Max Size:<PHONE_NUMBER>(0xffffffff)
  Grid Max Size per Dimension:
    x<PHONE_NUMBER>(0xffffffff)
    y<PHONE_NUMBER>(0xffffffff)
    z<PHONE_NUMBER>(0xffffffff)
  Max fbarriers/Workgrp:   32
  Pool Info:
    Pool 1
      Segment:                 GLOBAL; FLAGS: COARSE GRAINED
      Size:                    524288(0x80000) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       FALSE
    Pool 2
      Segment:                 GROUP
      Size:                    64(0x40) KB
      Allocatable:             FALSE
      Alloc Granule:           0KB
      Alloc Alignment:         0KB
      Accessible by all:       FALSE
  ISA Info:
    ISA 1
      Name:                    amdgcn-amd-amdhsa--gfx1036
      Machine Models:          HSA_MACHINE_MODEL_LARGE
      Profiles:                HSA_PROFILE_BASE
      Default Rounding Mode:   NEAR
      Default Rounding Mode:   NEAR
      Fast f16:                TRUE
      Workgroup Max Size:      1024(0x400)
      Workgroup Max Size per Dimension:
        x                        1024(0x400)
        y                        1024(0x400)
        z                        1024(0x400)
      Grid Max Size:<PHONE_NUMBER>(0xffffffff)
      Grid Max Size per Dimension:
        x<PHONE_NUMBER>(0xffffffff)
        y<PHONE_NUMBER>(0xffffffff)
        z<PHONE_NUMBER>(0xffffffff)
      FBarrier Max Size:       32
*** Done ***`

System will freeze, go to a black screen, wait, then attempt a reboot shortly. Reboot will succeed but VGA will not reinitialize.
Hard poweroff is required to power down card and reset VGA.
I've done stress testing to try and rule out RAM overclocking, CPU undervolting, etc.
None of these things seem to factor into whether it crashes.
GPU temperatures seem stable (junction around 90C max, everything else below 70C).
Issue does not occur during gaming, or even heavy gaming workloads.
Tested Linux 6.1.39, 6.2.0, 6.3.13, 6.4.4, and 6.5.0, issue occurs on all versions.
Steps to reproduce:
Run Automatic1111 Stable Diffusion until issue occurs.

try pytroch 1.13

I get the same crashes with a RX6800 within a minute with PyTorch rocm5.42 and PyTorch rocm5.5 (nightly) running stable diffusion or whisper. However PyTorch rocm5.2 runs without issue, you can install from the previous-versions page but be aware there is no python 3.11 version so installing it can be a pain.
After the crash, power off, power on, running journactl -b-1 shows an error about 50% of the time (shown below). Machine learning on RDNA2 is a no go for the foreseeable future.
May 11 13:59:42 crash kernel: i2c-designware-pci 0000:08:00.3: Unable to change power state from D3hot to D0, device inaccessible
May 11 13:59:53 crash kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=5509, emitted seq=5512
May 11 13:59:53 crash kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
May 11 13:59:53 crash kernel: amdgpu 0000:08:00.0: amdgpu: GPU reset begin!
May 11 13:59:53 crash kernel: amdgpu: Failed to suspend process 0x8007
May 11 13:59:53 crash kernel: amdgpu 0000:08:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:41 param:0x00000000 message:DisallowGfxOff?
May 11 13:59:53 crash kernel: amdgpu 0000:08:00.0: amdgpu: Failed to disable gfxoff!

Jun 14 10:47:36 crash kernel: i2c-designware-pci 0000:08:00.3: Unable to change power state from D3hot to D0, device inaccessible

Jun 21 21:43:48 crash kernel: amdgpu 0000:08:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: Failed to export SMU metrics table!
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: Failed to export SMU metrics table!
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: Failed to export SMU metrics table!

Try disable integrated graphic, I had the similar problem when it was active while I used HIP

Try disable integrated graphic, I had the similar problem when it was active while I used HIP

Doesn't work, it's another thing I tried

I get the same crashes with a RX6800 within a minute with PyTorch rocm5.42 and PyTorch rocm5.5 (nightly) running stable diffusion or whisper. However PyTorch rocm5.2 runs without issue, you can install from the previous-versions page but be aware there is no python 3.11 version so installing it can be a pain.
After the crash, power off, power on, running journactl -b-1 shows an error about 50% of the time (shown below). Machine learning on RDNA2 is a no go for the foreseeable future.
May 11 13:59:42 crash kernel: i2c-designware-pci 0000:08:00.3: Unable to change power state from D3hot to D0, device inaccessible
May 11 13:59:53 crash kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=5509, emitted seq=5512
May 11 13:59:53 crash kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
May 11 13:59:53 crash kernel: amdgpu 0000:08:00.0: amdgpu: GPU reset begin!
May 11 13:59:53 crash kernel: amdgpu: Failed to suspend process 0x8007
May 11 13:59:53 crash kernel: amdgpu 0000:08:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:41 param:0x00000000 message:DisallowGfxOff?
May 11 13:59:53 crash kernel: amdgpu 0000:08:00.0: amdgpu: Failed to disable gfxoff!

Jun 14 10:47:36 crash kernel: i2c-designware-pci 0000:08:00.3: Unable to change power state from D3hot to D0, device inaccessible

Jun 21 21:43:48 crash kernel: amdgpu 0000:08:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: Failed to export SMU metrics table!
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: Failed to export SMU metrics table!
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Jun 21 21:43:49 crash kernel: amdgpu 0000:08:00.0: amdgpu: Failed to export SMU metrics table!

Glad to know I'm not crazy and someone else is experiencing this. PyTorch workloads are the only workloads I've seen this happen under.

ROCm 5.4 doesn't support your video card. And I think Pytorch 1.13 also not support you card
You should use at least ROCm 5.6 and rebuild Pytorch 1.13 with support you card.

Or if it possible you can use Pytorch from this Docker container that already built with support you card ( https://hub.docker.com/layers/rocm/pytorch/rocm5.6_ubuntu20.04_py3.8_pytorch_1.13.1/images/sha256-267e5045f7c51b7ae252d429f664dca83a5fa8d99100c45ca736a26758748ee2?context=explore)

And I think that better to use latest stable release of Linux kernel with this Docker.

I'm pretty sure this is a firmware bug considering the nature of it. But I can try playing with the versions again. Frankly I really don't think the version of Torch, a userspace program, should have the slightest bearing on crashing the entire system. I might give that Docker image a try, but I'm not hopeful.

ROCm 5.4 doesn't support your video card.

Currently AMD does not support any RDNA2 consumer hardware with Rocm on Linux. However some RDNA2 chips sometimes work due to similarity with the supported "Radeon Pro W6800". I have no issues with the following torch version regardless of system Rocm version 5.2 through 5.6.
# ROCM 5.2 (Linux only)
pip install torch==1.13.1+rocm5.2 torchvision==0.14.1+rocm5.2 torchaudio==0.13.1 --extra-index-url https://download.pytorch.org/whl/rocm5.2

I'm pretty sure this is a firmware bug considering the nature of it. But I can try playing with the versions again. Frankly I really don't think the version of Torch, a userspace program, should have the slightest bearing on crashing the entire system. I might give that Docker image a try, but I'm not hopeful.

AMD GPUs crashing the system from user-space is often reported at the DRM repo, unfortunately it is rare to see issues closed successfully.
There are however 34 entries of 6800/XT users using Stable Diffusion with Torch 2.0+, weather they did this between crashes I don't know.

@lenhone I guess perhaps we might just have "bad" silicon or some other hardware issue going on. I've tried power limiting the card so I doubt it's power related. But at the same time, considering the crash only happens when running AI, and only AI, I must assume it's an issue with ROCm/Linux Kernel DRM. Considering the card's blatant refusal to reset itself after this failure, maybe it's even the VBIOS, or some random PCIe issue on my motherboard. I guess that's the very unfortunate part, that it could be so many things going wrong.
In a major turn of misfortune, I did in fact use that exact version of Torch like you specified, and still managed a crash.
Also if you don't mind my prying, do you happen to have the Linux kernel version you're using, and are you using the PRO version of the amdgpu driver? Also to clarify, your card does refuse to reinitialize VGA after the hard crash then reboot (black screen but Linux boots underneath, card is completely locked up)? I do want to isolate variables so I can maybe reproduce your success.
Sidenote: You don't happen to also be using Ryzen 7000 and an X670E motherboard, do you? (with your GPU made by XFX?) 😬

I'm pretty sure this is a firmware bug considering the nature of it. But I can try playing with the versions again. Frankly I really don't think the version of Torch, a userspace program, should have the slightest bearing on crashing the entire system. I might give that Docker image a try, but I'm not hopeful.

PyTorch should be built with support you card, I mean that I not sure that official PyTorch rebuild with support you card but I sure that Docker container that i sent support it (see screenshot)
PS: I had DRM/AMDGPU errors with official PyTorch and after rebuild it fixed.

@Walaryne Try using the 5.19 kernel for my rx7900xtx it works without an issue. testes kernels

@Walaryne Try using the 5.19 kernel for my rx7900xtx it works without an issue. testes kernels

I could try it, hopefully that's not too old of a kernel for my AM5 system though.

im on am5 too it works

@Kademo15 Were you experiencing the same crashes described here? (Card stuck in unrecoverable state till force poweroff?)
Because if this works, we have a jumping off point for bisecting the kernel/firmware.

Also if you don't mind my prying, do you happen to have the Linux kernel version you're using, and are you using the PRO version of the amdgpu driver? Also to clarify, your card does refuse to reinitialize VGA after the hard crash then reboot (black screen but Linux boots underneath, card is completely locked up)? I do want to isolate variables so I can maybe reproduce your success.

Hi Walaryne, answers to you questions below.

Current kernel is 6.4.7-arch1-2
I use opencl-amd from the AUR which installs the .deb packaged rocm stuff from repo.radeon. For example https://repo.radeon.com/rocm/apt/5.6/pool/main/h/hip-runtime-amd/hip-runtime-amd_5.6.31061.50600-67~22.04_amd64.deb.
My system also refuse to reinitialize VGA after the hard crash. I am left with a black screen until I power off and power on again.

There are many variables that may cause the crash. Unfortunately I have not crossed any off the list as I don't have any duplicate hardware.

GPU - Overheating / defective silicone / defective bios
Mother board - Power delivery (does the mother board prevent the GPU powering up after crash)
CPU - MCE / Power issues with C-state

Best of luck with your investigations, report back if you stop the crashes!

@Walaryne no not these but i had my share of compiling issues when i was on the 6.x kernels

Looks like this issue is similar to https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/11155#issuecomment-1589973562
I have installed CoreCtl and have access to the "advanced" voltage offset / GPU clock / Memory clock. Hopefully I get some time in the near future to play with these settings to see if stability improves.

Looks like this issue is similar to AUTOMATIC1111/stable-diffusion-webui#11155 (comment)
I have installed CoreCtl and have access to the "advanced" voltage offset / GPU clock / Memory clock. Hopefully I get some time in the near future to play with these settings to see if stability improves.

I was able to give your suggestion a try last night, sadly no dice for me. At least not on Torch 2.0. Still doing more research though, trying not to give up. Let me know how it works for you.

I experience the reboots/blue screens with Windows 11, 650W, Intel Arc 750 (but using CPU for rendering), AMD Ryzen 9 5950X with bigger image sizes and within the last 30% of generation. What BIOS Settings do you use for your RAM? Because I am currently trying to run RAM at lower speeds to see if is more stable then.

@Walaryne  Can you please test with latest ROCm 6.1.1 to see if it resolve your issues. Thanks!

@Walaryne Closing ticket since we haven't heard from you in a while. Please re-open if you still encounter the issue with the latest ROCm software. Thanks!


enrich existing PR template to smooth the review process

Closes: https://github.com/osmosis-labs/osmosis/issues/1261
NOTE! I‘m using the proposed PR template for this PR, to demonstrate how it can work
What is the purpose of the change
Adding a bit more templating to help smooth the review process, as well as fostering a engineering habit of emphasizing documentations and tests.
Brief change log

updated PR template with more critical self-check aspects for PR submitters, while trying to keep it simple and lean

PR Formatting

Is PR targeted against correct branch (see CONTRIBUTING.md)  (yes)

Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (no)
How is the feature or change documented? (not applicable)

Codecov Report

Merging #1264 (0f811a1) into main (b6d342a) will decrease coverage by 0.82%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1264      +/-   ##
==========================================
- Coverage   20.90%   20.08%   -0.83%
==========================================
  Files         196      203       +7
  Lines       25425    26786    +1361
==========================================
+ Hits         5316     5379      +63
- Misses      19118    20409    +1291
- Partials      991      998       +7

Impacted Files
Coverage Δ

x/incentives/types/query.pb.go
0.81% <0.00%> (-0.03%)
:arrow_down:

x/claim/abci.go
0.00% <0.00%> (ø)

x/epochs/abci.go
100.00% <0.00%> (ø)

x/gamm/module.go
62.50% <0.00%> (ø)

x/lockup/abci.go
0.00% <0.00%> (ø)

x/claim/module.go
58.06% <0.00%> (ø)

x/gamm/handler.go
5.88% <0.00%> (ø)

x/mint/genesis.go
69.23% <0.00%> (ø)

x/claim/handler.go
0.00% <0.00%> (ø)

x/epochs/module.go
48.64% <0.00%> (ø)

... and 99 more

Continue to review full report at Codecov.

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

Appreciate all the clarifications @jblbit , I saw your example PR descriptions such as #1268 which looks great. I see the value in having to encourage everyone to put more thought into the descriptions by having fewer checkboxes. Open to trying that first

to avoid the excessive checkboxes in template like cosmosSDK's, which is unreadable and resulting in people just completely ignore them

I think the major issue with people not utilizing the template in the SDK is stemming from the fact that the team is not encouraging its use. If we want to encourage all contributors to use our template, we should ultimately start reminding each other to fill in the description in every PR and not ignore it

I think part of the problem with checkboxes, is they don't work too well in the PR creation template. (You have to manually type x, or do a thing after hitting submit)

Hi @alexanderbez !

Love the motivation for this! I'm a bit hesitant because it makes the template more verbose for the PR author.

Good question. To clarify, it's not aimed to save time for PR author, but for PR reviewers. So please evaluate it from a reviewer angle, e.g. would you be able to review someone else's PR with this template more efficiently and confidently, even with little context? Honestly authors should take the extra work to make it easy to review by others, and don't count on reviewers to check for them.

Can we find a happy medium similar to what we do for the SDK?

As mentioned here, we discussed and wanted to try sth new rather than what cosmosSDK does. I suspect why the PR review process in cosmosSDK is not effective is mostly counting too much on reviewers rather than authors, and also checkbox in practice don't work as most expected.

Hi all, based on feedback, I'm gonna take out the part of "Is PR targeted against correct branch" which is inherited. This may just be a bylaw and no need to check for every PR.
BTW, Roman opened a PR with this new template as a good example. It makes it much easier at least for me to ramp up and review, compared to most other opened PRs.
All being said, understand it's a bit different from what we have so far, but I highly recommend trying it which has been proven at scale. We can always make changes based on real feedback afterwards rather than debating beforehand :)

I'm down to try this and iterate on it!
I actually like the non-checkbox system, and want to try it out at least. I feel like I've been in projects using checkboxes for PRs for years now, (not just in Cosmos), and none have had great success with getting contributors to follow the checkboxes. (in part, because imo the markdown syntax is confusing in preview)
We may want to cut down on the intro blurb so more of the relevant text automatically fills in, but I think that will become more apparent as we do more PR's and iterate on the templtae

Yeah totally down to at least try it as well!

Hi all, thank you for trying it out！Love to hear your feedback in a few weeks.
Can you help merge it, or grant me write access to merge it?
btw, in order to see it takes effect, all of us will be leading the change here, as nothing comes for granted :) e.g. we have to be the role model to follow it ourselves; if someone is not following it, please politely point it out and ask them to reformat.

I'm highly skeptical PR authors will fill this out in detail, but I suppose it can't hurt to try.


docs Fix invalid link and typo of Master Branch

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


postboot on slice update/modify not working properly

Here's the setup i tried that failed.

Create a 2 node WAN topology with L2 links between the nodes(one at each site). Interfaces set to "auto"
Submit slice
Created nodes with IP addresses assigned by fablib.
Modify the slice by adding third node at a third SITE
Add an interface tied to a new L3 network at each site. This interface is set to auto. Node routing for L3 networks is also set at this point with templates.
Submit(modify)
Upon slice being ready,
Expectation: All nodes ready and interfaces have IP
What I got:  The extra added node (4) has its IP configure on the dataplane interface and route added. The other nodes that existed before the modify do not have their newly added Interface configure. Those interfaces are still down with no IP assignment.

Forcing a node.config() on those nodes forces the postboot config that was messed up.

Here's the run thru.

Create your experiment using "create_l2network_wide_area_auto.ipynb" notebook.
Next run this block from
https://github.com/fabric-testbed/mflib/blob/d71fc68dae6e724cdcfc39853d097c7f0bb1636e/mflib/mflib.py#L105
then submit

@hussamnasir Just a small update: I just got around to look into this, and I'm able to reproduce what you've described above, I think.  Thank you for the detailed steps.
I'm trying to work out what is going on for now.

Sorry, I spoke too early when I said I could reproduce this: what I "reproduced" seems to be a transient error from the testbed, not the error @hussamnasir describes above.
(On Tuesday Nov 7, the error I saw was that nodes did not get a management address.  However that is not the original issue.  On hindsight, I wish I had taken copies of logs or screenshot of the notebook, but it did not occur to me to do this at the time.)
Now, back to the actual issue.  This is way I have understood this: you create a slice following steps 1-5, then do slice.submit() (step 6), then do MFLib.addMeasNode(slice), then do slice.submit() again. This will result in a modify operation.

The problem is that the interfaces added by MFLib (Node1-meas_nic_Node1_MICH-p1, Node2-meas_nic_Node2_NCSA-p1, and meas-node-meas_nic_meas-node_EDC-p1) do not have an IP address.  I am unsure if this is a fablib issue though.
There's a variation of the above: created a slice with steps 1-5, then do MFLib.addMeasNode(slice), then do slice.submit().  This should not involve a modify operation.  Result: two of the interfaces added by MFLib get an address, there's a third one that do not have an address.

I think postboot has nothing to do with this (or maybe I've misunderstood things), because for each of the nodes in the slice, post_boot_commands is an empty list:
{'Node1': {'fablib_data': {'instantiated': 'True',
   'run_update_commands': 'False',
   'post_boot_commands': [],
   'post_update_commands': []}},
 'Node2': {'fablib_data': {'instantiated': 'True',
   'run_update_commands': 'False',
   'post_boot_commands': [],
   'post_update_commands': []}},
 'meas-node': {'fablib_data': {'instantiated': 'True',
   'run_update_commands': 'False',
   'post_boot_commands': [],
   'post_update_commands': []}},
...

Ah. At last. This is what I was looking for. It is in my opinion 99.9% the issue.

@hussamnasir I'm so sorry that this took such a long time, and thank you so much for your patience! The amount of state we're keeping around and the fact that a thread pool was invoking Node.config() and messed with my head.
My branch is really messy right now. I will clean things up and submit a PR for review later. Please bear with me for a few more days, because I have to be away.


cuelang.org: preprocessor: hidden directives break editor syntax highlighting

What page were you looking at?
https://cuelang.org/
What version of the site were you looking at?
https://github.com/cue-lang/cuelang.org/commit/ac04bd4b223e8e2ce007c0eddf907ea0934cb0d4
What did you do?
I authored cuelang.org content using hidden _upload and _script directives.
What did you expect?
I expected my editor's simplistic markdown syntax highlighting not to break/degrade.
What did you see instead?
The _script and _upload directives trick my editor into thinking that a section of italic text has begun.
Unless I include some alphanumeric text directly followed by an underscore, the editor's italic highlighting persists to the end of the file.
Please: rename the directives so that if they start with an underscore, then they also end with an underscore.
e.g. _upload_, script_ or hidden_upload all /don't/ trick my editor.

Closed via https://github.com/cue-lang/cuelang.org/commit/3180bf38576a2ff53b055940d2ee862ec45a3e06


安装之后报错

Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

from EETQ import quant_weights, preprocess_weights, w8_a16_gemm
File "", line 1
from EETQ import quant_weights, preprocess_weights, w8_a16_gemm
IndentationError: unexpected indent
from EETQ import quant_weights, preprocess_weights, w8_a16_gemm
Traceback (most recent call last):
File "", line 1, in
ImportError: /usr/local/lib/python3.10/dist-packages/EETQ.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZN3c106detail23torchInternalAssertFailEPKcS2_jS2_RKSs

Make sure the pytorch==2.1.2. Or install EETQ via the source.


Fastlane  :  Could not complete submission of dSYM

New Issue Checklist

[ yes] Updated fastlane to the latest version
[yes ] I read the Contribution Guidelines
[yes ] I read docs.fastlane.tools
[ yes] I searched for existing GitHub issues

Issue Description
I can build falstlane after moving to my new M2 mac from Intel
When building the app VIA fastlane the Dsym is empty ..
Command executed
bundle exec fastlane build
Complete output when running fastlane, including the stack trace and command used
▸ Processing Info.plist
▸ Generating 'MyApp.app.dSYM'
▸ Running script 'Run Script'
Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Realm' from project 'Pods')
Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'PromisesObjC' from project 'Pods')
** ARCHIVE FAILED **
The following build commands failed:
PhaseScriptExecution Run\ Script /Users/user/Library/Developer/Xcode/DerivedData/MyApp-dgiquvsgpvkjfjcvhtcnrnpbekbj/Build/Intermediates.noindex/ArchiveIntermediates/MyApp/IntermediateBuildFilesPath/MyApp.build/Release-iphoneos/MyApp.build/Script-F9921F87220DFB5500CED15A.sh (in target 'MyApp' from project 'MyApp')
(1 failure)
[20:03:41]: Exit status: 65
+---------------+-------------------------+
|            Build environment            |
+---------------+-------------------------+
| xcode_path    | /Applications/Xcode.app |
| gym_version   | 2.213.0                 |
| export_method | app-store               |
| sdk           | iPhoneOS16.4.sdk        |
+---------------+-------------------------+
[20:03:41]: ▸ error: Could not complete submission of dSYM at /Users/user/Library/Developer/Xcode/DerivedData/MyApp-dgiquvsgpvkjfjcvhtcnrnpbekbj/Build/Intermediates.noindex/ArchiveIntermediates/MyApp/BuildProductsPath/Release-iphoneos/MyApp.app.dSYM: Error Domain=com.crashlytics.mac.error-domain.process-dsym Code=2 "File no longer exists at (null)" UserInfo={NSLocalizedFailureReason=File no longer exists at (null)}
[20:03:41]: ▸ Command PhaseScriptExecution failed with a nonzero exit code
[20:03:41]: ▸ warning: Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Realm' from project 'Pods')
[20:03:41]:
[20:03:41]: ⬆  Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
[20:03:41]: 📋  For the complete and more detailed error log, check the full log at:
[20:03:41]: 📋  /Users//Library/Logs/gym/MyApp.log
[20:03:41]:
[20:03:41]: Looks like fastlane ran into a build/archive error with your project
[20:03:41]: It's hard to tell what's causing the error, so we wrote some guides on how
[20:03:41]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[20:03:41]: Before submitting an issue on GitHub, please follow the guide above and make
[20:03:41]: sure your project is set up correctly.
[20:03:41]: fastlane uses xcodebuild commands to generate your binary, you can see the
[20:03:41]: the full commands printed out in yellow in the above log.
[20:03:41]: Make sure to inspect the output above, as usually you'll find more error information there
[20:03:41]:
+------------------+-----------+
|         Lane Context         |
+------------------+-----------+
| DEFAULT_PLATFORM | ios       |
| PLATFORM_NAME    | ios       |
| LANE_NAME        | ios build |
| BUILD_NUMBER     | 331       |
+------------------+-----------+
[20:03:41]: Error building the application - see the log above
+------+------------------------+-------------+
|              fastlane summary               |
+------+------------------------+-------------+
| Step | Action                 | Time (in s) |
+------+------------------------+-------------+
| 1    | Verifying fastlane     | 0           |
|      | version                |             |
| 2    | default_platform       | 0           |
| 3    | increment_build_numbe  | 2           |
|      | r                      |             |
| 💥   | gym                    | 153         |
+------+------------------------+-------------+
[20:03:41]: fastlane finished with errors
Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
13.3

Ruby
3.2.2

Bundler?
true

Git
git version 2.39.2 (Apple Git-143)

Installation Source
~/.gem/bin/fastlane

Host
macOS 13.3 (22E252)

Ruby Lib Dir
/opt/homebrew/Cellar/ruby/3.2.2/lib

OpenSSL Version
OpenSSL 1.1.1t  7 Feb 2023

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
14.3.1

Swift Version
5.8.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.116.0"

default_platform :ios

platform :ios do
  before_all do
    ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-asc_provider myteam"
    ENV["FASTLANE_USER"] = "mylogin"
    ENV["FASTLANE_APPLE_APPLICATION_SPECIFIC_PASSWORD"] = "mypwd"
  end
  # 1
  desc "Creating a code signing certificate and provisioning profile"
  # 2
  lane :provision do
    # 3
    produce(
      app_name: 'MyApp',
      language: 'French',
      app_version: '3.0',
      sku: '1234abcd'
    )
    # 4
    cert
    # 5
    sigh(force: true)
  end

  desc "Create ipa"
  lane :build do
    increment_build_number
    gym(
    export_method: "app-store" # or "ad-hoc"
    )
  end

  desc "Upload to App Store"
  lane :upload do
    deliver
  end

  lane :clean_build_folder do
    sh 'rm -rf ./build'
  end

  lane :beta do
     get_certificates           # invokes cert
     get_provisioning_profile   # invokes sigh
     build_app
  end

  lane :release do
     sync_code_signing
     disable_automatic_code_signing(path: "MyApp.xcodeproj")
     build_app
     enable_automatic_code_signing(path: "MyApp.xcodeproj")
     upload_to_testflight(
	username: "myUsername",
  	app_identifier: "com.MyAppSeries.MyApp",
  	itc_provider: "mydate")
  end

  error do |lane, exception|
  # This block is called if there was an error running a lane.
  end

end

`./fastlane/Appfile`
app_identifier("com.MyAppSeries.MyApp") # The bundle identifier of your app
apple_id("my login") # Your Apple email address

itc_team_id("myid") # App Store Connect Team ID
team_id("personnalid") # Developer Portal Team ID
asc_provider("personnaldata")
# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.213.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.5.1

did_you_mean
1.6.3

syntax_suggest
1.0.2

bundler
2.1.4

pathname
0.2.1

set
1.0.3

tsort
0.1.1

rake
13.0.6

rexml
3.2.5

CFPropertyList
3.0.6

concurrent-ruby
1.2.2

i18n
1.14.1

minitest
5.18.0

tzinfo
2.0.6

activesupport
7.0.5

public_suffix
4.0.7

addressable
2.8.4

httpclient
2.8.3

json
2.6.3

algoliasearch
1.27.5

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.777.0

aws-sigv4
1.5.2

jmespath
1.6.2

aws-sdk-core
3.174.0

aws-sdk-kms
1.66.0

aws-sdk-s3
1.123.1

babosa
1.0.4

claide
1.1.0

fuzzy_match
2.0.4

nap
1.1.0

netrc
0.11.0

ffi
1.15.5

ethon
0.16.0

typhoeus
1.4.0

cocoapods-core
1.12.1

cocoapods-deintegrate
1.0.5

cocoapods-downloader
1.6.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.1

cocoapods-trunk
1.6.0

cocoapods-try
1.2.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.3.1

gh_inspector
1.1.3

molinillo
0.8.0

ruby-macho
2.5.1

nanaimo
0.3.0

xcodeproj
1.22.0

cocoapods
1.12.1

colored
1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.4

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.8.1

emoji_regex
3.2.3

excon
0.100.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.3.0

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.3

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.7

jwt
2.7.1

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.5.2

mini_mime
1.1.2

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

webrick
1.8.1

google-apis-core
0.11.0

google-apis-androidpublisher_v3
0.43.0

google-apis-playcustomapp_v1
0.13.0

google-apis-iamcredentials_v1
0.17.0

google-apis-storage_v1
0.19.0

google-cloud-env
1.6.0

google-cloud-errors
1.3.1

google-cloud-core
1.6.0

google-cloud-storage
1.44.0

mini_magick
4.12.0

naturally
2.2.1

optparse
0.1.1

plist
3.7.0

rubyzip
2.3.2

security
0.1.3

simctl
1.6.10

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2023-06-12

 [REPLACE THIS WITH YOUR INFORMATION]

Can someone help ?

same here ! I was running on 14.3, fully deleted it  moved to 14.2 , cause I saw this on apple forum
update cocoapod to 1.12.1
still have the same error
"Command PhaseScriptExecution failed with a nonzero exit code"
found this video  https://www.youtube.com/watch?v=TZVQGY0T3k4 and remove the script in run script:
${PODS_ROOT}/FirebaseCrashlytics/upload-symbols -gsp ${PROJECT_DIR}/HangersPro/GoogleService-Info.plist -p ios ${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}
it works for archive .. not sure of the impact and probably will prevent me from using fastlane
How is this preventing the archive  and is this ok to do ?

Same here


Speed up to_database.py

The deploy job with to_database.py keeps timing out. I'm going to try and speed this up so that all states will be updated, but if anyone has any ideas on where to improve that would be helpful. It looks like most of the time is spent in update_subobjects(), and I'm going to look towards select_related() for a possible solution.

Thanks for taking a look- there's definitely optimization to be done.
Travis is a bit limiting in terms of time so my plan was to start running
it on our ECS cloud instead of Travis (and to get us through January to run
it locally on updated states) but if you find major speedups that'd be
great.
On Thu, Jan 3, 2019 at 2:59 PM Chris Nardi<EMAIL_ADDRESS>wrote:

The deploy job with to_database.py keeps timing out. I'm going to try and
speed this up so that all states will be updated, but if anyone has any
ideas on where to improve that would be helpful. It looks like most of the
time is spent in update_subobjects(), and I'm going to look towards
select_related() for a possible solution.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openstates/people/issues/55, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAfYlI0XiY5OCg6975PZansgCHCxCtcks5u_mENgaJpZM4ZorqU
.


Consistent Interface parameter placement

With this PR I'm just trying to align the placement of Interface in
the API, it's just cosmetic, but I find that having Interface either
at the beginning (this PR's option) or at the end is desirable.

I would suggesting putting Interface at the end consistently is the better option - it's the way we usually do it when binding to an effectful JS API.
The reason for that is it plays better with bind and traverse, since you can do things like foo =<< interface... I think for this API that probably isn't going to get much use, but I'd still suggest following it because it's the more common convention. All the web libraries use that convention - I'm not sure about the other node ones that have this kind of situation, but if they differ I'd say they should be changed similarly.

I would suggesting putting Interface at the end consistently is the better option - it's the way we usually do it when binding to an effectful JS API.
The reason for that is it plays better with bind and traverse, since you can do things like foo =<< interface... I think for this API that probably isn't going to get much use, but I'd still suggest following it because it's the more common convention. All the web libraries use that convention - I'm not sure about the other node ones that have this kind of situation, but if they differ I'd say they should be changed similarly.

Hah, I see @thomashoneyman said otherwise in https://github.com/purescript-node/purescript-node-readline/pull/21#issuecomment-758172141, but personally I still think it's right to put Interface at the end for the reasons I mentioned above.

Hah, I see @thomashoneyman said otherwise in https://github.com/purescript-node/purescript-node-readline/pull/21#issuecomment-758172141, but personally I still think it's right to put Interface at the end for the reasons I mentioned above.

@garyb I'm happy to defer :) I sometimes put these sorts of values as the first argument because it's easier to scan over them if they're in a consistent position (vs. depending on the number of arguments) and because you can partially-apply if you're going to be using the function several times. Given that the web libraries already use your suggested placement I think that's enough reason to stick with that, let alone your other reasons.

@garyb I'm happy to defer :) I sometimes put these sorts of values as the first argument because it's easier to scan over them if they're in a consistent position (vs. depending on the number of arguments) and because you can partially-apply if you're going to be using the function several times. Given that the web libraries already use your suggested placement I think that's enough reason to stick with that, let alone your other reasons.

I put it in the first position cause I was thinking about partial application as well, but I'm happy with either as long as it's consistent.

I put it in the first position cause I was thinking about partial application as well, but I'm happy with either as long as it's consistent.

@razcore-art let's go with @garyb's suggestion!

@razcore-art let's go with @garyb's suggestion!

I've updated the PR, should be good to go.

I've updated the PR, should be good to go.