[CCL] MeshShape in MeshDevice should be allowed to change its shape after open MeshDevide

Currently in TT mlir runtime, once we open mesh device using the number of device ids in a uniform way, for example 1x8 mesh shape for t3k, we cannot change it to 2x4, 4x2, or 8x1. It only allows to create sub-mesh, which is really subset of 1x8 including 1x1, 1x2, 1x4, or 1x8.
This issue tracks the ability to dynamically reshape the mesh  configuration at runtime after it is opened in any shape.

What is the use case that calls for dynamic re-shaping?

What is the use case that calls for dynamic re-shaping?

Each graph may open mesh device in different config at runtime. So, we open mesh device in a uniform way {1, num_of_device_ids()}, and later trying to reshape the mesh shape with the particular shape that the graph wants it to be. This is the summary of our intention AFAIK.


Add LGPL-2.1-or-later license too

[x ] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:
OmniORB software is licensed under multiple licenses, GPL-2.0-or-later for the programs, LGPL-2.1-or-later for the libraries.
I think COPYING.LIB should also be specified in the list of license_file metadata in the recipe.
I don't know how it works for the license metadata in the conda recipe. Can we specify a list of licenses here?
The conda-build documentation does not seem clear on that point.
If yes, I think it would be good to add LGPL-2.1-or-later to the list of licenses.
I think it would be also good to modify GPL-2.0-only to GPL-2.0-or-later too because the files in omniORB source code are specifying the "or later" option as you can see in the header of the following file:

https://sourceforge.net/p/omniorb/svn/HEAD/tree/tags/4_2_4/omniORB/src/tool/omniidl/cxx/idltype.cc
or the following file to illustrate a file where LGPL2.1 or later license applies:
https://sourceforge.net/p/omniorb/svn/HEAD/tree/tags/4_2_4/omniORBpy/include/omniORBpy.h

Thanks for the report. After a little digging, yes, this is all possible since SPDX identifiers allow expressions. I will add this license stuff to #12 before merging.


Black Sphere of Doom (model.dlb/etc will not display in the viewport properly)

Bare with me this is my first time submitting an issue on github. But anyway as you can see from the pic, when I open a vanilla c00 directory, it will not display it under any circumstance. I've tried different characters. This program started doing this for me a couple updates ago, it used to display characters just fine. Not sure what could have changed or if I did something. I tried re-downloading old versions, but those won't work anymore either. I never tried viewing stages or anything other than c00 stuff. Left panel properly previews textures, just the central viewport has a problem.

What GPU do you have? This looks similar to the issue in #117.

Hmm yeah. Mine is Intel(R) HD Graphics Family on a laptop.

CPU is Intel (R) Core(TM) i7-4600U CPU @ 2.10GHz

Does it work properly if you set DX12 in the preferences and then restart the application? You can also launch from commandline as ssbh_editor.exe --backend DX12.

No dice.

Apparently intel disabled DX12 in one of their driver updates a while back due to security vulnerabilties. You can find more information online if you search around. This isn't really something I can fix since there's no way for me to support DX11 at this time. Intel Haswell was released right around when Vulkan and DX12 were new, so the driver compatibility isn't great.

Ah, unfortunate. Thanks for the timely assistance.


Server may crash when a request's socket is ended manually

I use req.socket.end() to drop the requests that I won't response anything at all.
This performances well with https module,but will crash with http2.
here is a crash log I got:
....../node_modules/http2/lib/protocol/connection.js:302
        var frame = stream.upstream.read((this._window > 0) ? this._window : -1);
                          ^

TypeError: Cannot read property 'upstream' of undefined
    at Connection._send (....../node_modules/http2/lib/protocol/connection.js:302:27)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

First off, yes, this is a bug. However - you shouldn't be manually closing down sockets with HTTP/2. If you wish to not respond to a request, you should instead send a RST_STREAM with error code REFUSED_STREAM. (Or, if you're feeling exceedingly mean to the peer, you can just ignore it - HTTP/2 is an inherently parallel protocol.) There is no reason to close down the socket unless something has gone horribly wrong on the connection (pretty much all of these are enumerated by 7540, and are handled internally by node-http2).

Thank you for your suggestion.
By the way,"you can just ignore it" means I can just not do anything on the request?Will these request objects keep in node?

The request object will hang around, so just ignoring things isn't exactly suggested (unless you're ignoring them until a certain point in the future), but it won't break communication immediately (until you run out of memory).

Thanks for your answer.I've understood how it works.Should I leave the issue here or close it?


Milvus Roadmap is missing an introduction.

Issue
Milvus Roadmap is missing an introduction
Suggestion
Add an introduction to summarize what the page is about.

@claireyuw I have opened this issue and would love to take this up and fix this. Feel free to assign this to me.

/assign @Rutam21


docs need improving

https://docs.zarf.dev/docs/walkthroughs/big-bang#package-big-bang
in order to do a "zarf package create" on bigbang, you need to be logged into repo1.
See here:
https://repo1.dso.mil/big-bang/bigbang/-/blob/master/docs/guides/deployment-scenarios/quickstart.md#step-6-verify-your-ironbank-image-pull-credentials

I am confused, that is handled by the setup section: https://docs.zarf.dev/docs/walkthroughs/big-bang#setup

nope, you're not confused, we missed the step. I've asked Josi to put in a comment on the error you get if you can't auth to repo1 that explains you missed this step. :)


Suggestion: Enhancing error messages for clarity.

While reviewing the code, I noticed the following:

Enhancing error messages for clarity.

This could be improved to enhance the project quality. Let me know your thoughts!

Hello, we tried to solve the issue.
This is what we did:
Improved error messages in the TextMate module for better clarity and debugging. Added custom error classes and more informative error messages for missing environment variables and method calls.
You can review changes in this commit: https://github.com/mnmnk43434/drnic-ruby-on-rails-tmbundle-58/commit/14eefdc808d96d07f1eaf2353228b424a8257721.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.


Update Testing Guide

Deliverable 0c. - Testing and Testing Guide
Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.
This task is aimed at updating Testing Guide document.

https://github.com/eigerco/pallet-move/pull/137


Make it possible to start additional OTP-Applications

It should be possible to specify additional (external) OTP-Applications to be started in the boss.conf file. It is usefull to implement some complex backend functionality (e.g. gen_fsm ...)
A possible solution would be to add an {included_applications, [myapp]} tag to boss.conf which will be added to the boss application's environment.
When the boss-app is starting it evaluates this list and starts the apps in boss' supervisor.
I can try to implement it if you think it is a clean way and the feature is wanted.

as described in #530, there is Erlang way to do that


Add informative logging to wheel_resolver

The logging in wheel_resolver was unhelpful when executed in large environments. This change ensures we get information that helps with the debugging process instead of simply reporting an error generically.

Nit: The formatting changes were not necessary. We need to put some styling config in this repo.

@zgeor yep, but it's easier to format with the standards than to skip them.


is it possible to use vite-plugin-pwa with Nuxt3?

Hi, I have been trying to use it with Nuxt3 directly with the plugins system from Vite. it is my first try and so far it doesn't seem to be working:
in nuxt.config.ts
import { VitePWA } from 'vite-plugin-pwa'

  vite:{
    plugins: [
      VitePWA({
        includeAssets: ['favicon.svg', 'favicon.ico', 'robots.txt', 'apple-touch-icon.png'],
        manifest: {
          name: siteName,
          short_name: siteShortName,
          description: siteDescription,
          theme_color: '#FF0000',
          icons: [
            {src: 'pwa-192x192.png', sizes: '192x192', type: 'image/png', },
            {src: 'pwa-512x512.png', sizes: '512x512', type: 'image/png' },
            {src: 'pwa-512x512.png', sizes: '512x512', type: 'image/png', purpose: 'any maskable',
            }
          ]
        }
      })
    ]
  }

I have put it in this wip repo: https://github.com/ctwhome/top-nuxt3

@ctwhome I'll take a look:

we need to disable nuxt pwa, it is generating its own sw.js, see the build .output folder (inside the _nuxt directory you can find the sw generated by this plugin on your repro)
nuxt 3 is not yet released, and so not all modes are not yet ready: once released we'll take a look how we can add a module for this plugin

FYI: I clone your repo but I'm using pnpm instead yarn, you only need to run once installed viapnpm install: pnpm i --shamefully-hoist

@ctwhome the sw.js is not created by nuxt, you have the sw on the public directory.

@ctwhome I have it working,I just need to do some changes to support pages on offline (about on you repo), and I'll push to the main branch on my fork of your repro.
Anyway, this is a POC, we're waiting to the official pwa module on nuxt 3: I use pnpm as package manager.
I need to add a nuxt server middleware, use the inter plugin  communication like on svetlekit to make it work, take a look and new modules on root folder (build-pwa.ts and pwa-configuration.ts) and how I use them on nuxt.config.ts  and on build script on package.json, you will need to install esno as dev dependency. I also have included the ReloadPrompt.vue component and registering it on the default layout.
The head entry on nuxt.config.ts doesn't exist, it is meta, I have left a note on the configuration...
The app works and also with offline support.
I create a PR on your repo and so you can see the changes I applied to your codebase.

@ctwhome the PR also includes offline support for /about...
closing this for now...

Is this confirmed to have worked for Nuxt3? I only needregisterSW()on nuxt3, any tips?

@ChristopherJohnson25 check this entry and linked issues there on nuxt3 repo: https://github.com/ctwhome/top-nuxt3/issues/3

Hi Guys, i'm following this issue and wondering if this plugin will work on Nuxt3
For now I've tried and it doesn't properly works.
Uncaught (in promise) non-precached-url: non-precached-url :: [{"url":"index.html"}]

Any help would be great.
Thanks!

@re2005 try adding navigationFallback: '/' to  workbox  pwa plugin option.
I'm awaiting some nuxt changes to try to include also here (Vite PWA organization) an integration for Nuxt 3.

Thanks @userquin I'll give it a try.
Other updates on this subject ?
Cheers

@re2005 I'm working on it, we need some changes in Nuxt 3... I've it working on a private project with push notifications, the project will be also open source in a few weeks (I hope the first week on January we can release nuxt 3 pwa integration module)

Ow, that's awesome, really good work. Good luck with it. Will keep an eye here.
Thanks!

@re2005 I'm working on it, we need some changes in Nuxt 3... I've it working on a private project with push notifications, the project will be also open source in a few weeks (I hope the first week on January we can release nuxt 3 pwa integration module)

really excited
can not waiting any longer
keep up for the nuxt 3 pwa integration!

We've the application working with push notifications on alpha status, next week I'll start the integration, maybe adding also i18n pwa webmanifests support...

Are we talking about https://pwa.nuxtjs.org??

Are we talking about https://pwa.nuxtjs.org??

No, we're talking about @vite-pwa/nuxt, a new integration we'll start it next week, the logic is done, we only need to add the repo and publish it (I need to update my repo and then transfer it to vite org).

Ah okay, exciting! --- At nuxt side, there's PWA mentioned at their roadmap for 2022, and at least two PWA modules that I know of, the one I mentioned and one by kevinmarrec. Is this going to be another separate option?

Yes, @vite-pwa/nuxt will work only with Vite (webpack 4/5 will not work), about kevinmarrec integration you can use it with some limitations and about nuxt official pwa module I have no idea.
Check this tweet: https://twitter.com/userquin/status/1606967107325165570

Looking forward to it as well! Is there a way to start using the alpha version already?

Hey @userquin really appreciate the nice work done on this plugin.
I wondering if is possible to use it on my Nuxt v3  application, since the @vite-pwa/nuxt I can't manage to make it work.
Cheers

@re2005  Ask on nuxt discird server, pwa room or send a new issue to pwa nuxt repo with some info and a small repro of possible


Missing return in overridden method should give an error if it doesn't match the inferred return type

I would expect the following to give an analysis error in strong mode, but it doesn't (dartpad here):
import 'dart:async';

abstract class AsyncThing {
  Future doAsync();
}

class IncorrectAsyncThing implements AsyncThing {
  // Doesn't return a Future!
  doAsync() {
    print('hello');
  }
}

It only gives an error about a mismatched return type if you have an explicit return.
cc @leafpetersen

Note that inference correctly fills in the return type, but I think the code that emits the missing return hint doesn't look for an inferred type.

https://dart-review.googlesource.com/c/sdk/+/62727


Add any string suffix to number.

I know there is the possibility to add the currency suffix, but it would be useful to be able to add a more flexible suffix. For example "°C" for temperature values or "kg".

For a fixed suffix, the recommended way is to wrap the format function. For example:
const formatNumber = d3.format("d");
const formatCelsius = d => `${formatNumber(d)}°C`;

You can also combine the two like so:
const formatCelsius = (f => d => `${f(d)}°C`)(d3.format("d"));

We could perhaps formalize this pattern as:
const formatCelsius = d3.format("d", (f, d) => `${f(d)}°C`);

Or maybe make the arguments order-dependent to allow pre- (e.g., multiplying by 100) and post-formatting:
const formatCelsius = d3.format("d", s => `${s}°C`);


WriterMonad

Any reason that there is only transformer version WriterMonadT? Why there is no stand-alone version like you have for StateMonad?

It might be good to add one for convenience. But it can be derived directly from WriterT and Identity. In the future when we have interesting reasoning, we will likely only want the transformers so that we can avoid proving so much.

I'm going to mark this as 'wontfix' for the time being. If you think things would be better with a stand-alone writer monad, please submit a pull request.

I am not sure if this is the best way to implement this, but I am using this simple wrapper:
Section WriterMonad.
  Variable s t : Type.
  Variable Monoid_s : Monoid s.

  Definition writer := writerT Monoid_s ident.
  Definition runWriter x := unIdent (@runWriterT s Monoid_s ident t x).
  Definition execWriter x:= snd (runWriter x).
  Definition evalWriter x:= fst (runWriter x).
End WriterMonad.

If that is useful I can do a pull request for this definition along with simple example. However it might be to trivial to add.


Improve experience for creating multiple instances of a DbContext in the same request

While responding to https://github.com/aspnet/DependencyInjection/issues/352, I had what I think is a new idea (in the context of EF) that could help improve this experience. Here is a summary:

Add to the framework a new "factory" class, e.g. let's for now call it DbContextFactory<TContext> class. Its shape would look somewhat like this:

 public class DbContextFactory<TContext>
 {
   public DbContextFactory(
     IServiceProvider serviceProvider,
     DbContextOptions<TContext> options)
   {
     ...
   }
   public TContext Create()
   {
     ...
   }
}

The AddDbContext() method would register this in DI.
Users that need a single context per request scope would still resolve the TContext directly in constructors and users that need to create multiple instances could resolve the factory and then create the individual instances manually using the Create() method.

A few details/decision points:

Note that this does not replace the internal DbContextActivator mechanism but would be mostly sugar built on top of it (we still need a static place to stash the IServiceProvider).
There are possibly other variations on the pattern to consider, e.g. make the class non-generic and the  Create<TContext>() method generic, plus change where we pass the DbContextOptions, add a params object[] argument to Create(), etc.
We can change the registration in AddDbContext() to always go through an instance of this class or just leave it as it is now.
We actually already have the IDbContextFactory<T> type that this class could implement and that would become the actual service interface but it is currently used for different purposes. We need to understand if there is synergy in having the same type for all purposes of if it makes sense to look elsewhere.
We need to decide whether the type that uses would resolve should represent just a factory or be more of a lifetime manager for DbContext instance, e.g. does it just know how to create instances that then the user owns disposing at appropriate times or should it be an IDisposable itself that keeps records of instances returned and that takes care of disposing it. If we go with the later then it would be a higher level service that would depend on a IDbContextFactory<T> for the creation.

@ajcvickers I don't remember if we ever discussed doing something like this. Do you?
Another improvement in this area would be the ability to specify transient scoping when calling AddDbContext.

:+1: would be very nice !

@divega I don't remember discussing anything like this. I think it could work.

BTW we already have IDbContextFactory with a similar API surface, so maybe this overlaps with that in some way.

Need to decide if this "factory" should be IDisposable and remember instances it created to flow the call to Dispose() them or if the user would own calling Dispose() on each of them.

Need to decide if this "factory" should be IDisposable and remember instances it created

Whenever I've tackled exactly this question before I've always gone with:

Factories make instances of things. they never hold on to them
If I want to hold onto a context  and later Dispose it, I make a "DbContextManager" or "DbContextScope" this would, of course have the Factory injected in so it knows how to make new instances.

Factories make instances of things. they never hold on to them

@brendan-ssw totally agreed. If it handles the lifetime of the DbContext it is not just a factory anymore.  That is why I started wrapping the word "factory" in quotes :smile:
I will update the original description to account for this.

I believe previous EF versions had some odd assembly scanning logic so that if EF found an IDBContextFactory in the same assembly as your DbContext, EF internals would use that to instantiate DbContexts.- Worth keeping in mind if your intended factory was for the layer above EF.
I assume this has been changed in EF Core for a more explicit Dependency Injection approach?

We still have scanning logic in our design time tools, e.g. see
https://github.com/aspnet/EntityFramework/blob/dev/src/Microsoft.EntityFrameworkCore.Commands/Design/DbContextOperations.cs
I can't recall at the moment why this is needed but @bricelam for sure will.

IDbContextFactory is the design-time escape hatch for when we 1) can't create your service container, and 2) your DbContext doesn't have a default constructor.

@bricelam
Thanks, your comments have seriously helped my understanding here.
I typically use DI (usually with autofac) for everything and usually find that I can get everything working  just how I want it for my app's runtime but then stuggle to use the same dependency chain when trying to invoke migrations.
So, is there any way to configure the service container when invoking the dnx ef migration commands?
Right now my EFCore test project has a DbContext with an empty constructor just so I can run migrations.
With using a  DbContextFactory in this "escape hatch" way, I can't help feeling that this just passes the same problem down the chain: what if I want to inject a dependency into my DbContextFactory?

Think of IDbContextFactory as an application entry point. Just like the runtime entry point, it will need to setup the service container (e.g. by calling Startup.ConfigureServices)

Just repeat @bricelam's previous comment, we only use IDbContextFactory when we cannot figure out other ways to create the service container. We have conventions that look for Startup.ConfigureServices() and

(hit "comment" too soon) command parameters you can use to tell EF Migrations where to find the startup project at design-time so that we can create the same service container configuration you would have at runtime.

Per #4668 we removed magic injection for parameter-less constructors. The most intuitive way of creating non-scoped context instances (i.e. using the new keyword) should work just fine. It should also be easy enough to explain that you can resolve the DbContextOptions and pass it to constructors explicitly.
Given that, I suspect there may not be a big future for context factories at runtime.
I still think that IDbContextFactory is a weird name for something that is only supposed to help at design time,  but I think that is a different issue.
I propose we close this. Thoughts?
Cc @rowanmiller @ajcvickers

@divega Agree it can be closed.

:+1:


Some issues about Neovim.

In ui.lua, nvim-tree's git = {ignore = false} seems meaningless.
There is not any correspond valid config in the documentation: https://github.com/nvim-tree/nvim-tree.lua/blob/master/doc/nvim-tree-lua.txt#L407

nvim-tree's update_cwd is deprecated. Use sync_root_with_cwd instead. See: https://github.com/nvim-tree/nvim-tree.lua/blob/master/doc/nvim-tree-lua.txt#L626

There is not any correspond valid config in the documentation: https://github.com/nvim-tree/nvim-tree.lua/blob/master/doc/nvim-tree-lua.txt#L407

nvim-tree's update_cwd is deprecated. Use sync_root_with_cwd instead. See: https://github.com/nvim-tree/nvim-tree.lua/blob/master/doc/nvim-tree-lua.txt#L626

There are so many breaking change in nvim-tree, so my config may not suit for current version. All function I used is fine, but thanks for your reminding, I'll check the document.

I found out that your config do not include any number or relativenumber. Why?

You can search these in github webpage. You will find:
https://github.com/nanozuki/CrowsEnv/blob/d65b3f016fbfd92a11c789e35f33ff7316446d0c/dot_config/nvim/lua/config/editor.lua#L8

Here is a tip! You can use number and relativenumber in nvim-tree config too.

Here is a tip! You can use number and relativenumber in nvim-tree config too.

Oh, I got it, thanks!


Update wrappers built with tool_shed package instead of bioconda

[x] smalt
[x] freebayes
[x] mpileup
Have to move towards samtools mpileup to bcftools mpileup since deprecated
[x] phyml
contact owner of repo to move it toward bioconda/tools/iuc
[x] bcftools view
[x] bcftools call

Getting there!


gopatch: init at 0.2.0

https://github.com/uber-go/gopatch
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 232847 run on x86_64-linux 1

1 package built:

gopatch


Issue template

I have added a file called issue_template.md to help contributors submit their issues in a clean way

@codewithmide can you please check the reverted pull request and edit as it's show that it's an outed was of setting up issue template


[Bug] [Module Name] Cannot run program "sudo"

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I run shell task with DS failed. But I can run it in the bash command.
The directory actually exists in the system, I tried to run it under bash command,successfully.But failed to run in DolphinScheduler.
The Version is 3.2.1

[INFO] 2024-08-28 13:46:27.686 +0800 - Executing shell command : sudo -u root -i /tmp/dolphinscheduler/exec/process/root/14561355669280/14769037579424_1/10/24/10_24.sh
[ERROR] 2024-08-28 13:46:27.689 +0800 - shell task error
java.io.IOException: Cannot run program "sudo" (in directory "/tmp/dolphinscheduler/exec/process/root/14561355669280/14769037579424_1/10/24"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at org.apache.dolphinscheduler.plugin.task.api.shell.BaseShellInterceptor.execute(BaseShellInterceptor.java:47)
at org.apache.dolphinscheduler.plugin.task.api.AbstractCommandExecutor.run(AbstractCommandExecutor.java:138)
at org.apache.dolphinscheduler.plugin.task.shell.ShellTask.handle(ShellTask.java:85)
at org.apache.dolphinscheduler.server.worker.runner.DefaultWorkerTaskExecutor.executeTask(DefaultWorkerTaskExecutor.java:54)
at org.apache.dolphinscheduler.server.worker.runner.WorkerTaskExecutor.run(WorkerTaskExecutor.java:175)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 8 common frames omitted
[ERROR] 2024-08-28 13:46:27.689 +0800 - Task execute failed, due to meet an exception
org.apache.dolphinscheduler.plugin.task.api.TaskException: Execute shell task error
at org.apache.dolphinscheduler.plugin.task.shell.ShellTask.handle(ShellTask.java:97)
at org.apache.dolphinscheduler.server.worker.runner.DefaultWorkerTaskExecutor.executeTask(DefaultWorkerTaskExecutor.java:54)
at org.apache.dolphinscheduler.server.worker.runner.WorkerTaskExecutor.run(WorkerTaskExecutor.java:175)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Cannot run program "sudo" (in directory "/tmp/dolphinscheduler/exec/process/root/14561355669280/14769037579424_1/10/24"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at org.apache.dolphinscheduler.plugin.task.api.shell.BaseShellInterceptor.execute(BaseShellInterceptor.java:47)
at org.apache.dolphinscheduler.plugin.task.api.AbstractCommandExecutor.run(AbstractCommandExecutor.java:138)
at org.apache.dolphinscheduler.plugin.task.shell.ShellTask.handle(ShellTask.java:85)
... 5 common frames omitted
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 8 common frames omitted
What you expected to happen
It may be a bug??
How to reproduce
Just run a very simple shell task.It's like "echo A".
Anything else
No response
Version
3.1.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file password: changeme In the installer menu, select "gcc."

What's this bro?

It's not a bug. You should check your environment since Cannot run program "sudo" No such file or directory

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Firewall

Firewall (Bitdefender Total Security )is blocking requests from observatorycore.exe to https://edjp.colacube.net/: "Infected web-ressource found"

That would be coming from one of the plugins written by Matt G, not anything maintained at this repo.
I'll let him know this is happening, but closing the issue here.


Modularization: ipcache

Refactor ipcache into a control-plane and datapath cells. This is currently a collection of thoughts on how to go about it.
Handle-pattern instead of K8sCachesSynced
IPcache depends on knowing when the k8s stores have finished with synchronization with api server (initial listing). This is used to trigger reconciliation/garbage collection of the BPF maps which may contain old stale state. Since we may also get identities via kvstore, this abstraction doesn't actually work. Instead, consider a "handle"-based pattern:
type IPCache interface {
  NewHandle(source string) Handle
}

type Handle interface {
  Close()
  Synchronized()
  Upsert(ip string, hostIP net.IP, hostKey uint8, k8sMeta *K8sMetadata, newIdentity Identity) (namedPortsChanged bool, err error)
  // ...
}

Here each cell that wants to manage ipcache entries will ask for a handle and mark it as synchronized once its initial Upsert() calls have finished. When all handles have marked themselves as Synchronized() IPcache can start reconciling.
stream.Observable[IPCacheEvent]
Instead of hand-written support for listeners, expose a stream of IPCache events with the Observable type and implement it using stream.Multicast().
IPCache datapath
The datapath-side of IPCache is roughly implemented in pkg/datapath/ipcache, daemon/cmd/datapath.go and pkg/maps/ipcache. These should be unified into one cell that would on start initialize the ipcachemap and would handle the events from control-plane.
To keep dependency direction one-way, control-plane should do the ipcache.Observe() to register the datapath handlers.
DumpToListener (and the public mutex!) should be removed and instead Observe() should be called prior to start to guarantee that no events are missed.
API handlers
Once https://github.com/cilium/cilium/pull/24016 has been merged, implement the "GetIPHandler" in pkg/ipcache. This removes the other need for DumpToListener.
Testing
Integration tests for each handler (k8s, kvstore, ...) + ipcache (control-plane).
Test for GetIPHandler.
Privileged integration test for ipcache (control-plane) + ipcache (datapath).
Related: #23425

cc: @joestringer

I briefly looked into the "datapath" side of this and I identified a few different 'listeners' to userspace IPCache state that would all make sense as event handlers for events from the control-plane:

BPF Datapath (including pkg/datapath/ipcache, daemon/cmd/datapath.go and pkg/maps/ipcache)
Proxy / Envoy (including pkg/proxy/epinfo.go and maybe some references in pkg/envoy/resources.go).
WireGuard - pkg/wireguard/agent/agent.go


Reverse lookup for devices; position of coredns-omada in the plugin chain

Hi,
I was wondering if there is a reason why devices are not added to reverse zone. So I gave it a try and added it in update.go to see if it would work and it actually did ;-)
If you think this makes sense I could fork the repo and file a PR if you prefer it, but as it's a simple copy/paste of code and some small adjustments, I wouldn't mind if you just add it yourself.
The other thing is that I would like to start a discussion as I want to see coredns-omada at an "earlier place" in the "plugin chain". Btw, I saw the other issue regarding not putting it right at the beginning and the suggestion to have it before forward, so I know why it is currently right before forward.
I would like to see it before file/auto or even hosts as I would like to have coredns-omada handle most of the request and fall back to file/auto or even hosts for requests which are not "in omada clients/devices". The way it works in file/auto is, that the plugins are authoritive for whatever (sub-)domain the zone is configured for and wouldn't pass along the "plugin chain" if they can't handle the query. So they will not pass any query to coredns-omada. That would completely 'disable' coredns-omada for the sub-domain(s) in question. So I would like coredns-omada to handle most queries it can from 'clients/devices' and pass 'the rest' to file/auto which handle some fixed entries I added to zone files (or maybe to hosts bit preferably to file/auto). And for that coredns-omada would need to be before the other plugins in the chain.
Hope this makes sense.
Regards

Hi, feel free to raise a PR for the reverse zone for devices. I was planning to refactor that update function at some point as it has grown as features have been added but happy to get it added in for now.
Regarding the plugin order I would need to investigate the best place for it although its hard to predict which plugins users are using. Based on your use case it would seem that putting it directly above the file plugin and using the fallback option in the hosts plugin should work.
(The host plugin this supports fallthrough which should allow queries to fall back to omada - see the hosts plugin syntax.)

Thanks for the reply. I quickly forked the repo and created a PR for you to review.
Regarding the hosts plugin. I know about the fallthrough feature of the hosts plugin. To 'rely' on that would be ok too ;-) I would prefer file/auto anyway, to be honest.


Arch linux - No timestamp provided in packet

In Arch linux, everything is OK.
but this warning appears:
No timestamp provided in packet - expect low performance due to calls to gettimeofday

Same here...did you managed to solve this ?

Also the same problem......Is there any answer?


JavaScript unable to Send chat to console

Using JavaScript and trying to send chat to console seems to cause a cast error since JavaScript has no defined "Type".
"InvalidCastException: Cannot cast from source type to destination type."

For reference: http://oxidemod.org/threads/cast-error-when-sending-chat-to-console.7281/.


fix: 4955 gallery item price chart

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #4955
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[x] I've tested it at </bsx/collection>
[x] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

two questions here :)

is there some util for converting these currencies?
I have some trouble changing the z-index of the tooltip on price chart, what should the correct solution be here from the design perspective? Is adding margin allowed?

actually, it would be better if put that section in composables chain

moved to composables, and also used it in https://github.com/kodadot/nft-gallery/blob/main/components/gallery/GalleryItemAction/GalleryItemActionSection.vue#L49

2. I have some trouble changing the z-index of the tooltip on price chart, what should the correct solution be here from the design perspective? Is adding margin allowed?

yy, first and foremost the design of the popup should be different, but there is a issue with the styling iirc.

I think it can then overflow the chart and even the card itself if its not going to break other things

pay 35 usd

😍 Perfect, I’ve sent the payout
💵 $35 @ 32.73 USD/KSM ~ 1.069 $KSM
🧗 JHJGu2aWyAFBfcso8bR7ma82p15YAavyN6vQfJyWuhniNGa
🔗 0xa600801aea9d29f030988be56db5d28430c9b3efdecb793fe4d0b7ffef5f285f
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Website no longer generated

See https://github.com/tdwg/camtrap-dp/runs/8797650350, must be a Jekyll error.

Took a while to debug. Using a GitHub Actions workflow to see the logs didn't help that much. Eventually gitignored the Gemfile.lock file (only needed locally and generated automatically) and made use of the default GitHub Pages "Deploy from a branch" setup, which now works again. 🤷♂


Refactor module resolution Extensions, fix lookup priorities

Fixes two forever-standing resolution bugs:

The order of adding extensions vs. replacing extensions was backwards. Previously, for an import of "./foo.js", we would look up "./foo.js.ts" at a higher priority than "./foo.ts". This has been fixed in every module resolution mode.
Each module resolution algorithm previously ran two passes: one looking for .ts or .d.ts files, and then another full pass looking for .js files if the former returned nothing. This results in some priorities that are obviously wrong under allowJs, and since allowJs doesn’t actually affect resolution results (only whether JS resolutions are errors after the fact), probably always wrong by extension. An example:// dir/index.ts
export {}
// dir.js
export {}
// main.ts
import "./dir"

Here, import "./dir" should resolve to dir.js, but previously resolved to dir/index.ts in every module resolution algorithm. This has been fixed only in node16 and nodenext in an attempt to limit breaking changes to classic and node. Those algorithms now try all valid extensions in priority order for each lookup location. The exception is that node_modules lookups still happen in two passes: one that searches the implementation package followed by the @types package looking for .ts/.d.ts files for each node_modules folder found up the directory spine, followed (if necessary) by another pass up the directory spine looking for .js files in implementation packages. Making this change required a pretty extensive refactor of how the algorithms deal with extensions, and I think the result is much easier to reason about.

For file system hits and watches, this should be a wash—depending on what files are where, a given resolution might have a few more lookups, a few less, or the same number but in a different order.
Like most bug fixes, this is technically a breaking change, but only very strange edge cases that are already misbehaving should be affected.

Those algorithms now try all valid extensions in priority order for each lookup location. The exception is that for a given node_modules folder searched when looking up a non-relative name, the implementation package is searched for .ts/.d.ts files only, then the @types package is searched, then the implementation package is searched again for .js files.

I think this might be a problem for monorepos where @types packages might be hoisted to the monorepo root level while implementation packages might get installed in the monorepo subpackages due to different version requirements.

this has been fixed only in node16 and nodenext in an attempt to limit breaking changes to classic and node.

if this is breaking change anyway why not correct it for all algorithms.. Havent looked at changes yet and will do soon but does it simplify code even further or it makes it worse. Apart from being breaking change does it have any other reasoning not to break these two modes. Will it not do right thing.

I intend for classic and node to be essentially unmaintained after 5.0, so I don’t see a great reason to “fix” them if nobody has complained about this, but node16 and nodenext are new enough to bother fixing. It’s essentially a one-line change to opt node and classic into or out of the fix, so either way has little impact on code complexity.

I really expected a couple monorepos to fail there. Interesting.

Ah, the lack of failures could be due to low usage of node16 and nodenext. I’ll try applying the same fix to node and see how much stuff changes.

@typescript-bot test top100

@typescript-bot perf test this

@typescript-bot test top100 again, even though you haven’t finished the last one

^ Yeah, that’s what I expected. I’ve reverted the node_modules searching algorithm back to two full passes, so I expect the second top100 run to come back clean. Updated the PR description:

The exception is that node_modules lookups still happen in two passes: one that searches the implementation package followed by the @types package looking for .ts/.d.ts files for each node_modules folder found up the directory spine, followed (if necessary) by another pass up the directory spine looking for .js files in implementation packages.


Please, could you add batch file for console compilation of the solution

Please, could you add batch file for console compilation of the solution

This is done, when you get a chance could you try it out?
It created a file called BuildBenchmark.bat with the following contents:
@echo off
set _msbuildexe="%ProgramFiles(x86)%\MSBuild\12.0\Bin\MSBuild.exe"
if not exist %_msbuildexe% set _msbuildexe="%ProgramFiles%\MSBuild\12.0\Bin\MSBuild.exe"
if not exist %_msbuildexe% set _msbuildexe="%ProgramFiles(x86)%\MSBuild\14.0\Bin\MSBuild.exe"
if not exist %_msbuildexe% set _msbuildexe="%ProgramFiles%\MSBuild\14.0\Bin\MSBuild.exe"
if not exist %_msbuildexe% echo Error: Could not find MSBuild.exe.

@echo on
%_msbuildexe% Program.csproj /t:build /property:Configuration=Release


test_util: provide hook to easily set config values in test cases

Why? Reduces boilerplate associated with #7208. I made the solution general enough to handle similar future issues (e.g. testing with debug_nans enabled; #7510)

Errors look to be from the fact that the config is not reset after the test.

This looks good as is, or with a class decorator (to set _config) so things look more explicit.


[PE-D][Tester A] [Add Command] - Lowercase and Uppercase Input Validation

Using this;

I was attempting to do this;

Hence, I changed the name to Jany dOh and the app actually accepted the entry:

However, using the find command, I do note that the app does seem to recognize both entries as the same;

Might just be an issue with the input validation.

Labels: type.FunctionalityBug severity.Low
original: HM33-Stu/ped#17

For this either we edit the documentation or fix how the names are compared.

I feel that names should not have validation as 2 person can have the exact same names.


Watch folder

In response to #1149, this feature adds a preference to watch a folder for new .torrent files.
When a torrent file is saved on the watched folder it is automatically added to WebTorrent Desktop.
The feature can be enabled / disabled from preferences.

I really like this idea!
I think the wording on the the preferences could be phrased better as its not totally clear to me (and it doesn't mention "watching" at all)
Maybe:
(remove the header)

✅ Watch for new .torrent files and add them immediately.
Folder to watch: __________________________________________

Also, as this feature feels a little beyond the "keep things simple" user experience of this app, so it may be best to have this turned off by default.

Hey @Flet, thanks a lot for your feedback!
I like the rewording and simplification.
About the header, I think we still need it because there aren't preferences without headers. If we just remove the header the preference will look like being part of another section.
Maybe we can rename Downloads to Folders and add it under that section.
@feross, @dcposch, what do you guys think about this change?
Cheers!

Preview with proposed adjustments:

Hey @Flet, can you provide a review to move this one forward?
Thanks!


Ability to get the earliest and latest sample in a SamplePositionProperty

Feature
Feature Request: methods that allow user to get the earliest and latest sample in a SamplePositionProperty.
Following the SampledPositionProperty docs, I can add samples and get the interpolated position at a given time, but after adding the samples, I'm having a hard time being able to get the earliest and latest sample information to set the Cesium Clock startTime and endTime.
Wondering if others think this sounds like a potentially useful feature?

Thanks for the request @c3-victor-mao. Is this something you would consider contributing?

I'm closing this issue due to inactivity. If you believe this is still an issue, please feel free to re-open. Thanks!


touchesMoved:withEvent: shouldn't call setSelectedSegmentIndex:animated:

The current implementation does this:
- (void)touchesMoved:(NSSet *)touches withEvent:(UIEvent *)event
{
    // some stuff…

    [self setSelectedSegmentIndex:roundedSection animated:YES];
}

I believe most users will consider it unexpected if an app's state changes while they're still dragging their finger. Normally, it's safe to drag controls around on the screen, and nothing will take effect until the finger is lifted. For example, in Settings, a user can drag the Airplane Mode switch right and left, and Airplane Mode won't enable unless they lift their finger while the switch is enabled.
Instead, I believe this behavior should be in touchesEnded:, and touchesCancelled: should revert selectionView to its original state.

To be clear, it's not the UI updates I think are unexpected. I just think UIControlEventValueChanged shouldn't be sent until the finger is lifted.

I think you're correct. I'm swamped this week but I promise I'll get to it. :smile:

No rush… and I imagine we'll both be swamped next week :)

Yuuuuuuuuuup.

Fixed in 1.3.0


Use DNS for name resolution in most cases, fixes #416, fixes #834

The Problem/Issue/Bug:
It's icky messing with the hosts file and requires admin privileges.
Windows has a limit of 9 aliases on a line in the hosts file.
OP #416 requested non-hosts-file name resolution
OP #834 requested the ability to change the TLD in use, as is provided here.
How this PR Solves The Problem:
When the hostname is already resolvable, do not add it to the hosts file.
Note that this will require a transition to using "ddev.site" instead of "ddev.local"
TODO:

[x] Deal with the problem of a possible additional_fqdn that resolves already, provide a way to work around that.
[x] Provide a way to completely turn off this behavior in config.yaml
[x] This probably can't work with Docker Toolbox as currently envisioned (because the IP address is different)
[x] Provide configuration that allows an orderly transition to using "ddev.site" instead of "ddev.local"
[x] Change docs to use "ddev.site"
[x] Docs must explain how this works
[x] docs needs to say how to use ddev offline (may need ddev start to update, consider tld and useDNSwhen possible

Manual Testing Instructions:
Automated Testing Overview:

[ ] Test behavior with DNS resolution turned off (I don't think we can do this successfully because the tests don't actually modify /etc/hosts or use sudo)
[ ] Test behavior with TLD changed in config

Related Issue Link(s):
Release/Deployment notes:

@andrewfrench Another big one for your plate, but not as big. This one is easier to navigate and the results should be clear enough. Thanks!


bear: fix wrapper detection patch by checking result of find_executable

Motivation for this change
With the wrapper detection patch, if a build invokes an executable that cannot be found in PATH by find_executable, bear will fail with an AttributeError in os.path.realpath.
This can happen if the build invokes some project-local tool or command, like ./build-something.
Instead of calling using the result of find_executable directly, first check whether the executable was found and fall back to original Bear behavior if it was not.
The problem can be easily reproduced like this, for example:
cd /tmp \
    && mkdir -p test \
    && echo -e 'all:\n\t./command' > test/Makefile \
    && echo '#!/bin/sh\necho hello' > test/command \
    && chmod +x test/command \
    && bear make -C test

Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/17


having issues setting up depth buffer

Hello im using FSR in quality mode over Horizon Forbidden West and im usin cot6 shaders and i was able to go from a square window that was showing over the depth buffer to this, but still is not being set up correctly
How can i set this up correctly, in the screenshot i have scale over 1.5 and 1.5
I was able to fix over Preview depth buffer witch is fixing my entire screen and i saved the settings using cot6 addon but i dont kow how to set the buffer right without no issues and that weirds lines on the left i dont know what they are

but now if i move X scale over depth input
i have like ghosting
I dont know what in the hell is going, in 1.5 1.5 is fine
Wtf?
Can someone help me out?

From the screenshot, I think you have to set the depth input offset.
Note that the offset is by pixels. Offset X/Y and Scale X/Y are affected by each other, so repeat the increase or decrease until the game screen and the depth buffer are matched.
This issue is out of the scope of add-on support, so please continue to ask help on Discord.

thank you friend, im just new on this, is giving issues when using dlss >S


ref #663: Correctly detect update calls for cache clearing

Q
A

Branch
6.3.x

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Fixed issues
chameleon-system/chameleon-system#663

License
MIT

TCMSTableEditorMedia now uses bIsUpdateCall in order to check if the media is new or has existed before.

We will review this after the next release to be able to merge it into the correct branch for the release after the coming one.


Bug 2096510: template with no disks cant create VM

📝 Description
When trying to create a VM from a template with no disks, we get an error when clicking on review and create VirtualMachine
🎥 Demo
before:
https://user-images.githubusercontent.com/67270715/174563523-07ee9ea2-45c2-4039-8aaa-d2a5d091698e.mp4
after:
https://user-images.githubusercontent.com/67270715/174563566-1b0fa422-5be5-42f7-bcea-7d3a3634130e.mp4
Signed-off-by: Aviv Turgeman<EMAIL_ADDRESS>

/lgtm


Implemented Getting Zenodo citation

I've implemented two new functions in citations.jl:
get_zenodo_badge - This function reads the README.md file and extracts the link from the zenodo's badge;
get_citation_zenodo - This functions takes the badge link and obtains the bibtex.
I've modified the get_citations function to search for the badge in case no Citation.bib file is found. I've also added an argument zenodo=false  to get_citation, get_tool_citations and collect_citations. The default is false so that your previous tests do not break.
I've also implemented a testset for the zenodo functions. Note that some of your tests were already failing, and they are not related to the new functions.
I hope this PR is helpful.

Codecov Report

Merging #10 (d0fc2d8) into master (32fff07) will decrease coverage by 1.66%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage   90.00%   88.33%   -1.67%
==========================================
  Files           3        3
  Lines          90      120      +30
==========================================
+ Hits           81      106      +25
- Misses          9       14       +5

Impacted Files
Coverage Δ

src/citations.jl
91.30% <85.29%> (-6.20%)
:arrow_down:

src/tool_report.jl
83.33% <100.00%> (ø)

src/utils.jl
100.00% <0.00%> (ø)

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 8256957...d0fc2d8. Read the comment docs.

Thank you for your contribution!
I left some comments and suggestions on the specific parts of the code. It looks good, but I think it would be better to refactor the code a bit to return a merged citation dictionary from get_citation and maybe have a function get_badge_citations that would call get_citation_zenodo. This way it will be easier to extend for JOSS (and other types) of badges. I also think that we should default to getting all the citation data.
I'm wondering if we could just setup a regex for DOIs in badges.

Note that some of your tests were already failing, and they are not related to the new functions.

Can you provide some information about the failing tests? The CI doesn't show failing package tests and I also checked locally and I didn't encounter any problems.
The errors in CI like
Error: Can't open display: (null)

are due to the clipboard integration tests because I haven't managed to install xclip properly (#11).

What exactly do you mean by using "regex for DOI"? Do you mean, search for the "DOI" term, and then extract the badge link? I guess this could be done, although I'm not very good with regex.

By the way, here are the test failures I get when I just run the forked repo without my changes:
 [0c5d862f] Symbolics v0.1.27
┌ Warning: There was an error reading the CITATION.bib file for Distributions
│   exception = KeyError: key "july" not found
└ @ PkgCite ~/MEGA/EMAp/PkgCite.jl/src/citations.jl:15
┌ Warning: There was an error reading the CITATION.bib file for Distributions
│   exception = KeyError: key "july" not found
└ @ PkgCite ~/MEGA/EMAp/PkgCite.jl/src/citations.jl:15
┌ Warning: Overwriting julia_citations.bib
└ @ PkgCite ~/MEGA/EMAp/PkgCite.jl/src/citations.jl:53
[ Info: A julia_citations.bib file with the citations for LabelledArrays, QuadGK, Symbolics, RecursiveArrayTools, ArrayInterface and AbstractAlgebra was generated in the current working directory (/home/davibarreira/MEGA/EMAp/PkgCite.jl/test).
┌ Warning: There was an error reading the CITATION.bib file for Distributions
│   exception = KeyError: key "july" not found
└ @ PkgCite ~/MEGA/EMAp/PkgCite.jl/src/citations.jl:15
┌ Warning: There was an error reading the CITATION.bib file for Distributions
│   exception = KeyError: key "july" not found
└ @ PkgCite ~/MEGA/EMAp/PkgCite.jl/src/citations.jl:15
[ Info: The above sentence was copied to your clipboard.
┌ Warning: Overwriting julia_citations.bib
└ @ PkgCite ~/MEGA/EMAp/PkgCite.jl/src/citations.jl:53
[ Info: A julia_citations.bib file with the citations for LabelledArrays, QuadGK, Symbolics, RecursiveArrayTools, Julia, ArrayInterface and AbstractAlgebra was generated in the current working directory (/home/davibarreira/MEGA/EMAp/PkgCite.jl/test).
Clipboard: Error During Test at /home/davibarreira/MEGA/EMAp/PkgCite.jl/test/runtests.jl:81
 Unexpected Pass
 Expression: clipboard() == CITE_STR_JL
 Got correct result, please change to @test if no longer broken.

┌ Warning: There was an error reading the CITATION.bib file for Distributions
│   exception = KeyError: key "july" not found
└ @ PkgCite ~/MEGA/EMAp/PkgCite.jl/src/citations.jl:15
[ Info: The above sentence was copied to your clipboard.
┌ Warning: Overwriting julia_citations.bib
└ @ PkgCite ~/MEGA/EMAp/PkgCite.jl/src/citations.jl:53
[ Info: A julia_citations.bib file with the citations for LabelledArrays, QuadGK, Symbolics, RecursiveArrayTools, Julia, ArrayInterface and AbstractAlgebra was generated in the current working directory (/home/davibarreira/MEGA/EMAp/PkgCite.jl/test).
Clipboard: Error During Test at /home/davibarreira/MEGA/EMAp/PkgCite.jl/test/runtests.jl:89
 Unexpected Pass
 Expression: clipboard() == CITE_STR
 Got correct result, please change to @test if no longer broken.

Test Summary:              | Pass  Error  Broken  Total
PkgCite.jl                 |   24      2       1     27
  Empty env                |    1                     1
  Packages                 |    6              1      7
  Citations                |    4                     4
  Citations in .bib        |    5                     5
  Only direct dependencies |    3                     3
  PkgCite sentence         |    5      2              7
    Clipboard              |    2      2              4
ERROR: LoadError: Some tests did not pass: 24 passed, 0 failed, 2 errored, 1 broken.
in expression starting at /home/davibarreira/MEGA/EMAp/PkgCite.jl/test/runtests.jl:10
ERROR: Package PkgCite errored during testing

Also, can you give an example of what do you mean by the " but I think it would be better to refactor the code a bit to return a merged citation dictionary from get_citation and maybe have a function get_badge_citations that would call get_citation_zenodo"? I don't fully understand what exactly would be this merged citation dictionary.

I was thinking if there would be an edge case where we need to merge citations form the badge with the ones in the CITATION.bib file, but as I've said it the response comment, it would be better to just document that we prefer the CITATION.bib file over the badges and leave the implementation as is.

What exactly do you mean by using "regex for DOI"? Do you mean, search for the "DOI" term, and then extract the badge link? I guess this could be done, although I'm not very good with regex.

I was referring to parsing the README for badges and then look for DOI-like strings (things like "10.5281/ZENODO.4692172") insde them since the badge links contain the DOI information, but I see now that this will not work for Zenodo since there can be links with latestdoi that need to be followed for the DOI. I thought that the DOI info is present in the link like in the badge for Plots or DynamicalSystems.
Looking for the "DOI" string is indeed a better solution since it seems to be used in all the badges I've encountered.

Yeah, there are some cases where the DOI is in the badge, but for Zenodo, at least, this is not the correct way to setup. The reason is that for every new package version a new DOI is generated. So using "latestdoi" is the correct setup, hence, why I wrote that "warning". Perhaps, one can check if the badge has a DOI, and use that instead.

Regarding the failing tests, I marked the clipboard ones as broken since that functionality is broken on CI (and it didn't work on the local computer where I tested because xclip/xsel wasn't installed), but it worked on your computer. I think I will wrap those tests in a try that checks clipboard() works in a future PR. We can safely ignore this for now.

Yeah, there are some cases where the DOI is in the badge, but for Zenodo, at least, this is not the correct way to setup. The reason is that for every new package version a new DOI is generated. So using "latestdoi" is the correct setup, hence, why I wrote that "warning". Perhaps, one can check if the badge has a DOI, and use that instead.

It looks like looking for a badge that starts with "DOI" will cover all cases (and also work for JOSS badges). We could issue a warning in the case of Zenodo if we detect a badge that doesn't use latestdoi, but using a DOI for all the package versions (like Plots) or the latest one seems like something that not everyone will agree on, so we should test that the code works on both variants.

I'll do the following. I'll create a function that searchers for a badge with DOI, and get's the link. Now, if the link if from zenodo, then uses my code to get the bibtex. If it's a doi link, then I'll create another function to generate the bibtex from it.

Made all the suggested changes. The function get_zenodo_badge now is get_badge, and it looks for the DOI badge, and extracts the link. The function get_citation_zenodo is now get_citation_badge and it checks weather the link is already the DOI or if it's the latestdoi (for the Zenodo case). I guess this is all.
As I said in the other comment, I left the default as false and I think a new PR should be opened to turn true into the default, improve the documentation and fix the tests.

Thank you very much for your contribution!

Not a problem! Thanks for the pkg by the way :D


auto-configure setting does not create a namespace and Repository CRD

Hi, folks!
I set the value for auto-configure-new-github-repo to True
apiVersion: v1
data:
  application-name: Pipelines as Code CI
  auto-configure-new-github-repo: "true"
  auto-configure-repo-namespace-template: "{{repo_name}}-pipeline"
  bitbucket-cloud-additional-source-ip: ""
  bitbucket-cloud-check-source-ip: "true"
  default-max-keep-runs: ""
  error-detection-from-container-logs: "false"
  error-detection-max-number-of-lines: "50"
  error-detection-simple-regexp: |
    ^(?P<filename>[^:]*):(?P<line>[0-9]+):(?P<column>[0-9]+):([ ]*)?(?P<error>.*)
  error-log-snippet: "true"
  hub-catalog-name: tekton
  hub-url: https://api.hub.tekton.dev/v1
  max-keep-run-upper-limit: ""
  remote-tasks: "true"
  secret-auto-create: "true"
  secret-github-app-scope-extra-repos: "Stringls/artie"
  secret-github-app-token-scoped: "true"
  tekton-dashboard-url: ""
kind: ConfigMap
metadata:
  labels:
    app.kubernetes.io/part-of: pipelines-as-code
    app.kubernetes.io/version: v0.15.5
  name: pipelines-as-code
  namespace: pipelines-as-code

But when I try to add a new repository to my CI workflow it fails because of no namespace created
cannot find a namespace match for https://github.com/Stringls/test-repo

Logs of the controller
{"level":"info","ts":1676371985.5279555,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676371985.5282037,"caller":"settings/config.go:150","msg":"CONFIG: auto configure repo namespace template set to {{repo_name}}-pipelines"}
{"level":"info","ts":1676371985.5285232,"caller":"settings/config.go:150","msg":"CONFIG: auto configure repo namespace template set to {{repo_name}}-pipelines"}
{"level":"info","ts":1676371985.5287163,"caller":"settings/config.go:150","msg":"CONFIG: auto configure repo namespace template set to {{repo_name}}-pipelines"}
{"level":"info","ts":1676371985.5289354,"caller":"settings/config.go:150","msg":"CONFIG: auto configure repo namespace template set to {{repo_name}}-pipelines"}
{"level":"info","ts":1676371985.5291998,"caller":"settings/config.go:150","msg":"CONFIG: auto configure repo namespace template set to {{repo_name}}-pipelines"}
{"level":"info","ts":1676371985.5294359,"caller":"settings/config.go:150","msg":"CONFIG: auto configure repo namespace template set to {{repo_name}}-pipelines"}
{"level":"info","ts":1676371985.5296552,"caller":"settings/config.go:150","msg":"CONFIG: auto configure repo namespace template set to {{repo_name}}-pipelines"}
{"level":"info","ts":1676371998.6787953,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"severity":"INFO","timestamp":"2023-02-14T10:53:18.840178376Z","logger":"pipelinesascode","caller":"github/parse_payload.go:323","message":"issue_comment: pipelinerun recheck on Stringls/test-repo#1 has been requested","commit":"6134468","provider":"github","event-id":"c9dac9f0-ac55-11ed-9511-8b0f26e8d8a9"}
{"severity":"WARNING","timestamp":"2023-02-14T10:53:19.822759568Z","logger":"pipelinesascode","caller":"events/emit.go:49","message":"cannot find a namespace match for https://github.com/Stringls/test-repo","commit":"6134468","provider":"github","event-id":"c9dac9f0-ac55-11ed-9511-8b0f26e8d8a9","event-sha":"11d4a0861e3ee870e41f6b98728fc1e547f7f489","event-type":"pull_request"}
{"level":"info","ts":1676372328.199323,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"severity":"INFO","timestamp":"2023-02-14T10:58:48.407716956Z","logger":"pipelinesascode","caller":"github/parse_payload.go:323","message":"issue_comment: pipelinerun recheck on Stringls/test-repo#1 has been requested","commit":"6134468","provider":"github","event-id":"8e51e4d0-ac56-11ed-9549-b8bebda641c4"}
{"severity":"WARNING","timestamp":"2023-02-14T10:58:49.610422466Z","logger":"pipelinesascode","caller":"events/emit.go:49","message":"cannot find a namespace match for https://github.com/Stringls/test-repo","commit":"6134468","provider":"github","event-id":"8e51e4d0-ac56-11ed-9549-b8bebda641c4","event-sha":"11d4a0861e3ee870e41f6b98728fc1e547f7f489","event-type":"pull_request"}
{"level":"info","ts":1676372393.743666,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7437074,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7442343,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7466435,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7474515,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7479708,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7482412,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7484522,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7487464,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7489028,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7494297,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7494602,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7498295,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7499232,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.750522,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.750867,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7513514,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.751612,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7517872,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.750968,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7522094,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.752581,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7528944,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"level":"info","ts":1676372393.7548778,"caller":"settings/config.go:150","msg":"CONFIG: auto configure repo namespace template set to {{repo_name}}-pipeline"}
{"level":"info","ts":1676372399.0063024,"caller":"params/run.go:67","msg":"added or modifies events are coming"}
{"severity":"INFO","timestamp":"2023-02-14T10:59:59.187973535Z","logger":"pipelinesascode","caller":"github/parse_payload.go:323","message":"issue_comment: pipelinerun recheck on Stringls/test-repo#1 has been requested","commit":"6134468","provider":"github","event-id":"b8893c80-ac56-11ed-8403-2c5418ce102a"}
{"severity":"WARNING","timestamp":"2023-02-14T11:00:00.232242023Z","logger":"pipelinesascode","caller":"events/emit.go:49","message":"cannot find a namespace match for https://github.com/Stringls/test-repo","commit":"6134468","provider":"github","event-id":"b8893c80-ac56-11ed-8403-2c5418ce102a","event-sha":"11d4a0861e3ee870e41f6b98728fc1e547f7f489","event-type":"pull_request"}

What I am doing wrong?

hello 👋🏽 does your GitHub app configured for repository event? :)

I'm also getting the same message on my PR - https://github.com/ch007m/pac-demo/pull/1/checks. The github app has been created according to the following doc page: https://pipelinesascode.com/docs/install/github_apps/#setup-manually

yeah the event is missing there, as it is an optional feature
https://pipelinesascode.com/docs/install/settings/
here you can see
auto-configure-new-github-repo

If you have a GitHub App already setup then verify if the `repository` event is subscribed into your Github App setting.

@sm43 Is there any plans to support the existent repos for this automation feature as well? E.g. I have the existent repo and I want to simply add the pipelinerun definition into .tekton/ folder to enable CI on it

@anton-livewyer  there is no plans for this at the moment. having a catch all namespace for all pipeline may be something we can have with a regexp kind of matching for the repo URL but that's not planned at the moment...


How large is the dataset?

Hello,
How large is the dataset (in GB), and how long does it take for you to generate it? I'm trying to reproduce your results, and generation is taking a super long time, even on a machine with 64 CPUs.
Also, once you generated the dataset, how did you train your classification model?
Best,

Hi @greeneggsandyaml ,
Thanks for your comments.
[How large is the dataset?]
In our observation, FractalDB-1k (1k categories / 1k instances) is 13GB. You can download the dataset the linked page.
https://hirokatsukataoka16.github.io/Pretraining-without-Natural-Images/#dataset
[how long does it take?]
In terms of the rendering time, we can render 1 or 2 days without fractal category search. Did you try to render the fractal images with multi-thread execution? You can use the command in the execution file ( https://github.com/hirokatsukataoka16/FractalDB/blob/main/exe.sh ) instead of single-thread programming as follows.
# Multi-thread processing
for ((i=0 ; i<40 ; i++))
do
    python fractal_renderer/make_fractaldb.py \
        --load_root='./data/csv_rate'${fillrate}'_category'${numof_category}'_parallel/csv'${i} \
        --save_root='./data/FractalDB-'${numof_category} --image_size_x=${imagesize} --image_size_y=${imagesize} \
        --iteration=${numof_ite} --draw_type=${howto_draw} --weight_csv='./fractal_renderer/weights/weights_'${weight}'.csv' &
done
wait

[how did you train your classification model?]
We have assigned a simple CNN training which is similar to ImageNet training. However, the normalization is different from the standard mean pixel value. Especially in the ImageNet mean pixel value, we replaced from (123,117,104) to (127, 127, 127). At this moment, we are preparing to share our codes in pre-training/fine-tuning and their weights.

Hi @hirokatsukataoka16 ,
Thank you so much for your quick and comprehensive response! I really appreciate you answering my questions in detail.
I was able to download the dataset from the link on your project page, and I'm currently exploring the dataset. I look forward to seeing your training and fine-tuning code when it is released.
I'm going to close this issue for now, and I will reply if I have additional questions.
Best,

Thanks, @greeneggsandyaml ,
Feel free to ask me again!

Hi @greeneggsandyaml ,
I updated the repository including codes for pre-training and fine-tuning.

Hi @greeneggsandyaml ,
I updated the repository including codes for pre-training and fine-tuning.

Brilliant, thank you!
On Thu, Jan 7, 2021, 9:34 PM Hirokatsu Kataoka<EMAIL_ADDRESS>wrote:

Hi @greeneggsandyaml https://github.com/greeneggsandyaml ,
I updated the repository including codes for pre-training and fine-tuning.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hirokatsukataoka16/FractalDB-Pretrained-ResNet-PyTorch/issues/1#issuecomment-756508118,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APLDPRZFOG4ZPURWZB5CJGLSYZVNBANCNFSM4UKJ5NZQ
.

Brilliant, thank you!
On Thu, Jan 7, 2021, 9:34 PM Hirokatsu Kataoka<EMAIL_ADDRESS>wrote:

Hi @greeneggsandyaml https://github.com/greeneggsandyaml ,
I updated the repository including codes for pre-training and fine-tuning.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hirokatsukataoka16/FractalDB-Pretrained-ResNet-PyTorch/issues/1#issuecomment-756508118,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APLDPRZFOG4ZPURWZB5CJGLSYZVNBANCNFSM4UKJ5NZQ
.

Hello @ hirokatsukataoka16,
I am had another quick question about finetuning -- how did you prepare the PascalVOC and Omniglot datasets? My understanding is that PascalVOC is usually in a multi-class classification setup and Omniglot is usually a few-shot learning setup. Did you make them into single-class classification tasks, and if so how exactly did you go about it?
Thank you so much again for the paper and repo! It's a really nice idea.


Remove JLayout and replace with flex layout PART 3

See https://github.com/silverstripe/silverstripe-framework/issues/6012 for full description
PART 3:

[x] Security
[x] Reports

Requires Part 1 for review

Moved to other story


Distinguish incomplete chains from untrusted roots

At least in a naïve fashion, flagging likely incomplete chains from untrusted roots should be feasible by counting the number of certificates returned in "Certificate Chain Received" from sslyze. requests may also return something that could be useful.
I recallopenssl returns a 'depth' value, which, when a site is less than 2 deep, is a strong indication intermediate certs are not served, making the chain incomplete. If depth<2 and the certificate is not trusted in the Mozilla store, this seems to indicate an incomplete chain, while depth>=2 seems to indicate an untrusted root.

This remains a great idea, if we can somehow distinguish those things. I think it means going beyond sslyze's STDOUT output and digging into the (new) Python API in some way.


Convenient Blob Methods

Need to build some kind of container for our blobs that we can define nice convenient methods for, such as a findBlob method. More ideas for what kind of methods we want?

Covered by https://github.com/austin-garrard/blobber2/pull/29


PR: Learn and Retake Alice.

Join

-

Learn

Alice

fnCreate
fnPutString
fnGetString
fnToString

Retake

-

Other

-

OK.


HDDS-8929. Avoid list allocation for pipeline search

What changes were proposed in this pull request?
Pipeline#equals includes equality of getNodes(), which wraps the set of nodes in a new ArrayList (defensive "copy").  This is unnecessary, we can compare the underlying Set.
(see HealthyPipelineChoosePolicy.choosePipelineIndex in flamegraph from HDDS-8897)
https://issues.apache.org/jira/browse/HDDS-8929
How was this patch tested?
CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/5376416993

Thanks @adoroszlai work on this, this can really improve performance.
Although now look at the flame chart, The lock has little impact on latency, and whether the lock will be optimized subsequently, as it can improve throughput.

Thanks @guohao-rosicky, @sodonnel for the review.


Using correct driver for mysqlconnectorj

MySQLContainer now uses the correct mysql driver package, stop warnings

This was fixed in #1760, which is being released now in https://github.com/testcontainers/testcontainers-java/releases/tag/1.12.1


OVMF: support RiscV64

Description of changes
This brings the RISCV64 support to OVMF/EDK2.
Needs cleanup and I should dispatch some commits in other PRs to minimize this one.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I think you already handled this in #269877 and the backport.


Aborted (core dumped) with tf.raw_ops.LRNGrad

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.16.1
Custom code
Yes
OS platform and distribution
Ubuntu 20.04
Mobile device
No response
Python version
3.11
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
If  the dimension of output_image is less than input_grads and input_image, tf.raw_ops.tf.raw_ops.LoadAndRemapMatrix encounters "Aborted (core dumped)".
Standalone code to reproduce the issue
# LRNGradOp

import tensorflow as tf

depth_radius = 1
bias = 1.59018219
alpha = 0.117728651
beta = 0.404427052
input_grads = tf.constant([], shape=[0,0,0,0], dtype=tf.float32)
input_image = tf.constant([], shape=[0,0,0,0], dtype=tf.float32)
output_image = tf.constant([], shape=[0], dtype=tf.float32)
tf.raw_ops.LRNGrad(input_grads=input_grads, input_image=input_image, output_image=output_image, depth_radius=depth_radius, bias=bias, alpha=alpha, beta=beta)

Relevant log output
2024-05-01 03:28:07.055077: F tensorflow/core/framework/tensor_shape.cc:357] Check failed: d < dims() (1 vs. 1)
Aborted (core dumped)

Hi @LongZE666 ,
I tried to run your code on colab using TF v2.16.1, nightly and faced the same issue. Please find the gist here for reference.
Thank you!


Stack level too deep errors on 7.0.0+

If you are experiencing a stack level too deep error after upgrading to 7.0+ of the ruby agent, check out our troubleshooting guide on resolving the issue in your application.
Report a New Conflict
The ruby agent is able to automatically install compatible instrumentation when certain gems are detected in the application that are known to cause a conflict with the the agents use of Module#prepend.
To report a conflict to be added to the agent detection when automatically installing instrumentation, please provide the following after configuring the agent by following the troubleshooting guide

which agent configuration option was used to install the compatible instrumentation (Ex. instrumentation.net_http: prepend)
the gem (and version) that is conflicting with the agent. This would be the non-agent location in the stack trace that is part of the recursion. (Ex. /Users/user/.rvm/gems/ruby-2.6.5/gems/airbrake-10.0.1/lib/airbrake/rails/net_http.rb:11 or Airbrake v10.0.1)

Gems Known to Cause Prepend Conflicts (auto-detected in latest release v7.2.0)
Net::HTTP

Airbrake < 10.0.2
ScoutApm
Rack::MiniProfiler

Redis

PrometheusExporter

Resque

Airbrake < 11.0.3

Prepend conflict between httpclient instrumentation and Faraday v1.5.0.
instrumentation.httpclient: chain resolves the issue
No complete stack trace provided
Reported in https://github.com/newrelic/newrelic-ruby-agent/issues/714

We upgraded from newrelic_rpm 6.x to 8.8.0. I had to update our newrelic.yml config file. We also use scout_apm gem which still uses chain method for instrumenting.
First time I got the Stack level too deep error regarding net_http. That got solved adding instrumentation.net_http: chain to the config file. That said, according to your code, scout should be automatically detected as conflicting with prepend. For some reason, that didn't work.
But then it failed again, this time because of redis implementation. I added instrumentation.redis: chain to the config file, but it kept trying to use prepend and showing "Installing New Relic supported Redis instrumentation using Prepend". Then I tried overriding it setting NEW_RELIC_INSTRUMENTATION_REDIS=chain and that did work. So in this case, I don't know why the env var works but the yaml config doesn't.

Hi @oboxodo,
Thanks very much for this information. I'm very glad to hear that you were able to get things working, but sorry to hear you ran into a couple of issues.
New Relic and Scout
As for the issue with our code auto-detecting Scout and then using chain instead of prepend, that code will only work if Scout has already been loaded ("required" in a Ruby context) before the New Relic code is loaded. Typically to ensure that the Scout code is loaded before the New Relic code, you would make sure New Relic comes second in Gemfile:
# Gemfile - put New Relic last
gem 'scout_apm'
gem 'newrelic_rpm'

If it is not possible to place newrelic_rpm after scout_apm in Gemfile, then there are 2 other options:

Manually set any desired instrumentation.* config values to chain in the config file (as you have done)
Tell Bundler not to load the New Relic code yet via gem 'newrelic_rpm', require: false and then manually require the gem in an initializer within the monitored application.

If you feel that the New Relic code is definitely getting loaded after the Scout code and that our code for auto-detecting may have a bug, please let us know and we'll investigate farther.
Redis Instrumentation
In order to configure the New Relic agent to use "chain" instead of "prepend", the approach is to put the following in the configuration file:
instrumentation.<INSTRUMENTATION NAME>: chain

With net/http you were able to do this with instrumentation.net_http: chain. This is because lib/new_relic/agent/instrumentation/net_http.rb uses :net_http for its named value.
With Redis, you will need to do instrumentation.redis_instrumentation: chain. This is because lib/new_relic/agent/instrumentation/redis.rb uses :redis_instrumentation for its named value.
I completely understand how "redis" would make more sense than "redis_instrumentation", but at this point we cannot rename it without breaking existing clients that use the current name.

Thank you, @oboxodo! I have created #1267 to track the investigation into why the configuration file based approach to setting redis to use "chain" is not working.

Hi @oboxodo. Two things:

I was incorrect earlier when I stated that the configuration parameter should be instrumentation.redis_instrumentation. The correct parameter is instrumentation.redis, which you originally had. I obtained the "redis_instrumentation" value from the named :redis_instrumentation line in lib/new_relic/agent/instrumentation/redis.rb, however that the same file also has a configure_with :redis line that I missed earlier that permits the use of the shorter "redis" string.

I have been unable to reproduce the problem so far. To try to eliminate as many variables as possible, I put together a minimal set of instructions and Ruby code in a gist.

If you are able to help test this issue by following the instructions in the gist, that would be super helpful. If the gist fails for you, then there must be something different between your environment and mine. If the gist succeeds for you, then there must be something different between the gist's Ruby code and New Relic configuration and those of your application.

@fallwith ok, I found the "bug", and here's my proposed fix: https://github.com/newrelic/newrelic-ruby-agent/pull/1276
The problem is that the template newrelix.yml had no indentation on the default values (since this commit), and that causes that my (unindented) instrumentation.redis: :chain gets ignored. Because it's not part of the &default_settings. So, it's a yaml syntax issue, caused by a bad config template.
Once I indented the setting adding two spaces to it, it worked as expected.
Thanks!


Docker -  Missing "Targetare.ro" button

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:
1.Open the URL in the browser
2.Run scraper for "Docker" Company
3.Go to logo
4.Verify "Targetare.ro" button
EXPECTED RESULTS:
The "Targetare.ro" button is functional . Targetare link opens correctly
ACTUAL RESULTS:
Missing "Targetare.ro" button. Targetare link doesn't open targetare.ro

the company is not present on targetare.ro


Setting IFS in build_conda_env.sh script disrupts sourcing conda via module load

When loading more than one module, the scripts to build or activate the conda environment use a for loop that relies on IFS=' ', setting it to "$(printf '\n\t')" breaks this assumption.

I will set IFS=' ' only for the loop, restoring it to its original value afterwards.

That would work. Otherwise the modified IFS could be removed entirely, as it is just there to catch mistakes with unquoted variables, and every variable use (except for $MODULES_LIST, which we want to split) is properly quoted.


Bring back test_main

Now with a proxied ironicclient so it's not loaded on launch
added full env vars to test env

👍


Add titles and fixup descriptions for many subschema. Also make

jsconschema references relative again.

The absolute references used to work around jsonschema's (the python library) unconditional attempt to load RemoteRefs is no longer necessary. Relative references are necessary for some of the jsonschema documentation generators.

Validation completed https://common-jenkins.kubeme.io/job/K2/job/PR-494/8/


fix: fix ts types for actor bindings

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1470  👈 (View in Graphite)
#1469
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Add asan-ubsan instrumentation option

This option combines ASan with UBSan, which is very useful for running the replay tests as well as while iterating on a fuzz test locally.

bazel_lint failure is fixed by https://github.com/bazelbuild/rules_fuzzing/pull/233.

CI failure is fixed now.


Enable review releases for PRs

Review releases can speed up the collaboration and improve feedback process. To enable them, we need to:

[x] Ensure all pages are statically renderable
[x]  Configure yarn build in CI
[x] Find a configure hosting

Implemented via Netlify integration.
Example PR:
https://github.com/ScottishCovidResponse/rampvis-ui/pull/119
This specific PR got autodeployed to https://deploy-preview-119--rampvis-ui-development.netlify.app (note PR number in URL).
The tip of the main branch (nextjs-migrate at the time of writing) is available at https://rampvis-ui-development.netlify.app
There’s also https://github.com/ScottishCovidResponse/rampvis-ui/pull/97 which should automate official releases to the VM.


Get offline/unread messages

I am not entirely sure if this should be a bug or a feature request. In the deprecated chat versions I saw that there was the 'unread' property available in the deprecated chat history method. But the new chat features seem to be missing that property. I can use the offlineMessages event to check from which friends I received offline messages. Then I can request chat history for those friends to actually get those messages. However I still don't see how I could determine which of those old messages in history are unread offline messages. Is it possible to fix that or re-add that feature?!

Update to v4.9.1 and I've added an unread property to getFriendMessageHistory.


Update customize.json

Hi @garvkohli

Hi @garvkohli
Thanks a lot for checking out the project!
However, you don't need to create a PR on this repo to get this running. You can create a link directly in your fork and host your changes in there.
I'm closing this PR, but please feel free to comment/reach out if you need any help. 🙂


Emoji Command

Send the emoji pic link. Not the emoji 👅

Maybe extra Command, like >>emojilink

Thanks @Marcel26990


I add some magic to inject

Before the modification,we use inject like beblow:
@inject("color")
It is ok,But if I want to only visit deeper attributes like a.b,I can only do like this:
@inject("a")
then,visit b by this.props.a.b
after the modification,we can do like this:
@inject("a.b:propName")
then,visit b by this.props.propName

This is the kind of logic that imho doesn't belong to this package. First of all it needs a lot of documentation, and there are many libraries that do this properly better. Like a lodash pluck.  Furthermore this problem is easy to be solved in userland. You can simply create your own HoC by leveraging the fact that inject can also take functions, so you could do something like:
function pluckInject(path) {
   return inject(stores => pluck(stores, path))
}

@pluckInject("a.b.c") class MyComponent....


Not working after injection

So I tried injecting two ways, one with my own injector, and one with Cheat Engine. Both didnt work, but when I used Cheat Engine I got an actual error message, which read:
"Failed to find pattern 33 f6 48 0d ? ? ? ? 48 85 c9 74 13"
I clicked "Ok" and tried to open the cheat anyway, and when I clicked instert, nothing (on both injectors).
Error screenshot below

There was no response either

Fixed in 3029d40c91bdd36e173aa892119a489497dc9d87