GroupMemoryBarrier? GroupMemoryBarrierWithGroupSync?

I have seen miniEngine use XXXMemoryBarrierWithGroupSync exclusively across all its cs where there need a 'sync'. But after looking through several of them I found most of them just need memory barrier, so it may be benificial (conceptually) to use XXXMemoryBarrier instead of XXXMemoryBarrierWithGroupSync.  Or are there some reasons to stick with the GroupSync version which I missed? Or am I misunderstand XXXMemoryBarrierWithGroupSync?
Thanks
Peng

Great observation!  I'm responsible for almost all of those group syncs, and I tend to default to the GroupMemoryBarrierWithGroupSync() call.  You're probably aware of the difference of the various barriers, but I'll briefly paraphrase the differences.
GroupMemoryBarrier - Wait for all issued reads and writes from groupshared memory (LDS) to finish
DeviceMemoryBarrier - Same but for system/video memory
AllMemoryBarrier - Flush any and all memory transactions (Group + Device)
Now appending "GroupSync" to the call also synchronizes all of the threads so that they've executed all of the same instructions.  This can result in subtle race conditions if left off.  Suppose you do a GroupMemoryBarrier without a GroupSync.  If not all of the threads are at the same program counter (PC), then some of those threads might not have issued their read or write instructions before saying "wait for all that have been issued".  To be safe and make sure you wait for all memory transactions that you expect to be issued, you need to get all of your threads in sync.
That concern is really only valid when your group thread count is larger than the GPU's native wave size.  All of the threads in the same wave are naturally at the same instruction.  It's only when thread groups are broken up into multiple waves that you have threads issuing different instructions.  But in the case where your thread count equals the wave size, the shader compiler can silently optimize out your group sync because it knows its not necessary.
So long story short, it's better to be safe.  And it's hard to be too safe in this case because the compiler will ignore your request when it's not necessary.
I wanted to point out one more thing.  I almost never use a Device or AllMemoryBarrier because I tend to read from system memory and write to groupshared memory.  By the time the write has happened, the read from device memory must also have happened.  If I was just reading into registers, I would need a DeviceMemoryBarrier.
Cheers,
James

Thanks James for such detailed explanation, that's really informative. But what would be the proper and safe case to use GroupMemoryBarrier then, since compiler can opt out the GroupSync when threads are within one wavefront/warp. Or GroupMemoryBarrier will be deprecated later?

You might need inter-thread synchronization only within a wave or smaller.  For example, maybe your thread group size is 256, but your threads are operating on data in groups of 4x4.  You need to flush writes before reads or vice versa, but you can assume all threads working on the same set of data are doing so in lock-step.  So MemoryBarrior is useful but not GroupSync.

ah, yup. Thanks for all your time answering my questions :-)

Sorry for asking in a closed issue but that's exactly the problem I'm trying to understand for a couple of weeks. I tried to compare gpu memory barriers with c++11 memory fences with different memory ordering (relaxed, seq_consistency, acquire/release) but I can't see the similarities. @stanard, after your great explanation memory barriers start to make some sense to me thought not absolutely clear. Can you please explain it one more with an example. Let's take this pseudocode:
shaderResource.store(42); // #1
GroupMemoryBarrier(); // #2
int i = shaderResource.load(); //#3

Am I correctly understanding that if thread1 and thread2 (a hypothetical group made of 2 threads) are from different waves than this flow is possible?

thread1 writes to the resource (#1). Since thread2 is from another wave it doesn't go with thread1 in a lockstep and it doing nothing for now (I mean it's possible to do nothing).
thread1 reaches barrier (#2). No more threads in a group accessed memory untill this moment - only thread1. That means that this barrier can be passed for this thread. thread2 still doing nothing.
thread1 reads from the memory (#3). Now, at the same time, thread2 starts to write (#1). Ans it's a classical race condition.

Is my understanding correct?

Hi @nikitablack,
I think your understanding is there, but you need a DeviceMemoryBarrier() when writing to memory.
You are correct that because thread2 comes from a different wave, it could write to the same location that thread1 is about to reload.  You need a GroupSync to guarantee that both threads have issued their write instructions.  But it's generally a bad thing to have multiple threads writing to the same location anyway.
I should also point out that results could change if your threads came from different thread groups because then they could be running on different compute units, execute at different times, and even go through different L1 caches.  And there are no dispatch-wide memory barriers, so you couldn't synchronize those two threads.
When it comes to multi-threaded GPU memory accesses, try to have threads be responsible for their own data (like SIMD).  Use groupshared memory to share information between threads for things like scatter, gather, convolutions, etc.  If you want to write a single value as the result of your dispatch, put a branch around it:  if (DispatchThreadID == 0) { // write value }
Good luck!  Welcome to mind-bending world of very parallel algorithms.  :-)
-James

Thank you @stanard, I think I got it.
Just to summarize (taking the example from my previous post):

if we have two threads from the same group and the same wave - there're no chances of data race. We don't need to sync here.
if we have two threads from the same group but from different waves - there's a chance of data race. We need to sync here.
if we have two threads from different groups - we can't share the same group memory (it's obvious), but we can share device memory. But there're no such barriers in d3d - all barriers work only in the same group. We need another sync mechanism, but not barriers. Atomic counters maybe.

And yes, this all applies only to situation where we have a write to the same data (as in my example). As @stanard pointed out:

it's generally a bad thing to have multiple threads writing to the same location anyway.


Add "Impersonate user" setting to Datasource

Implements #2148
ToDo:

[x] Fix async case
[x] Write tests

Current solution works for sync queries but doesn't for async. It says

'_AppCtxGlobals' object has no attribute 'user'

Which makes sense. My first idea would be to pass it as a parameter to get_sql_results for the async case.

Coverage increased (+0.02%) to 69.137% when pulling ddd7c66e200c6f666fa7ce0d7a1a0493e6b8ff92 on dmigo:master into 3dfdde130a88d3a12a6e084adc07d284ed6090e6 on apache:master.

Coverage increased (+0.02%) to 69.137% when pulling ddd7c66e200c6f666fa7ce0d7a1a0493e6b8ff92 on dmigo:master into 3dfdde130a88d3a12a6e084adc07d284ed6090e6 on apache:master.

Coverage increased (+0.02%) to 69.137% when pulling 018017d11bf9ee0ccf53aa0f71643493ee86445c on dmigo:master into 3dfdde130a88d3a12a6e084adc07d284ed6090e6 on apache:master.

Coverage increased (+0.02%) to 69.137% when pulling fa9b606e9cb7edac1c35d30af34c46e70b57d9d5 on dmigo:master into 3dfdde130a88d3a12a6e084adc07d284ed6090e6 on apache:master.

Coverage increased (+0.02%) to 69.137% when pulling fa9b606e9cb7edac1c35d30af34c46e70b57d9d5 on dmigo:master into 3dfdde130a88d3a12a6e084adc07d284ed6090e6 on apache:master.

hmm... Tests seem to be kinda off. How could I restart them?

Coverage decreased (-0.001%) to 69.117% when pulling 0945f55877fa883e366fbfa7005af9b179aa527a on dmigo:master into 3dfdde130a88d3a12a6e084adc07d284ed6090e6 on apache:master.

@mistercrunch
All the code that makes difference is covered, I don't really think it would make sense to add any more tests as a part of the current PR.
Travis fails with js tests, though I didn't touch any js in this PR.

Coverage decreased (-0.001%) to 69.117% when pulling a62f02e3cb3474a43122ec09fabd4e02773a17cc on dmigo:master into 147c12dddf0da742f1c33c6fee3b2a4b9dbd12c8 on apache:master.

@mistercrunch
All the code that makes difference is covered, I don't really think it would make Sinn to add any more tests as a part of the current PR.

Coverage decreased (-0.001%) to 69.111% when pulling b92e03d155397bdf406e2e7f564c47c7ef074b80 on dmigo:master into 7c1b56f3a95a89dc8200bf91bfa609e7760707da on apache:master.

Coverage decreased (-0.001%) to 69.118% when pulling 95f1b0d7c5e8ee12bb7c06ad4e01e380b2301b5a on dmigo:master into 3c0e85e2c074755eb2883dc75b92aad83a3f0261 on apache:master.

Coverage decreased (-0.001%) to 69.118% when pulling 95f1b0d7c5e8ee12bb7c06ad4e01e380b2301b5a on dmigo:master into 3c0e85e2c074755eb2883dc75b92aad83a3f0261 on apache:master.

Coverage decreased (-0.001%) to 69.153% when pulling 31e78051a88597ce651e7de2332de138980b1d07 on dmigo:master into fdee06bbf2a3a9289dd92bbc88c919f68a81b9ea on apache:master.

Coverage decreased (-0.001%) to 69.14% when pulling 5c02f71826d0d008bdc9eeb0dd1b4bae21ad03bf on dmigo:master into e22aecb0d1244bae49d3e5b36ef2f9ddc7517c1a on apache:master.

Coverage decreased (-0.001%) to 69.14% when pulling 5c02f71826d0d008bdc9eeb0dd1b4bae21ad03bf on dmigo:master into e22aecb0d1244bae49d3e5b36ef2f9ddc7517c1a on apache:master.

Coverage decreased (-0.001%) to 69.14% when pulling 5c02f71826d0d008bdc9eeb0dd1b4bae21ad03bf on dmigo:master into e22aecb0d1244bae49d3e5b36ef2f9ddc7517c1a on apache:master.

Coverage decreased (-0.001%) to 69.14% when pulling 5c02f71826d0d008bdc9eeb0dd1b4bae21ad03bf on dmigo:master into e22aecb0d1244bae49d3e5b36ef2f9ddc7517c1a on apache:master.

Coverage decreased (-0.001%) to 69.14% when pulling 5c02f71826d0d008bdc9eeb0dd1b4bae21ad03bf on dmigo:master into e22aecb0d1244bae49d3e5b36ef2f9ddc7517c1a on apache:master.

Is there anything in the docs about this?
Seems like it sets the DB user in the connection string to the superset user name, but I don't understand how the password for that DB user is set?


Converting from CSS to SASS

I made the switch to use SASS instead of pure CSS. The stylings work well in development, but when I package the app, Most of the styling doesn't work. I think it may have something to do with sass-loader vs css-loader. I added node-sass and sass-loader.
I have this in my webpack.config.production.js
    loaders: [
      // Extract all .global.scss to style.css as is
      {
        test: /\.global\.scss$/,
        loader: ExtractTextPlugin.extract(
          'style-loader',
          'css-loader',
          'sass-loader'
        )
      },

      // Pipe other styles through css modules and append to style.css
      {
        test: /^((?!\.global).)*\.scss$/,
        loader: ExtractTextPlugin.extract(
          'style-loader',
          'css-loader?modules&importLoaders=1&localIdentName=[name]__[local]___[hash:base64:5]',
          'sass-loader?modules&importLoaders=1&localIdentName=[name]__[local]___[hash:base64:5]'
        )
      },

      { test: /\.woff(\?v=\d+\.\d+\.\d+)?$/, loader: 'url?limit=10000&mimetype=application/font-woff' },
      { test: /\.woff2(\?v=\d+\.\d+\.\d+)?$/, loader: 'url?limit=10000&mimetype=application/font-woff' },
      { test: /\.ttf(\?v=\d+\.\d+\.\d+)?$/, loader: 'url?limit=10000&mimetype=application/octet-stream' },
      { test: /\.eot(\?v=\d+\.\d+\.\d+)?$/, loader: 'file' },
      { test: /\.svg(\?v=\d+\.\d+\.\d+)?$/, loader: 'url?limit=10000&mimetype=image/svg+xml' },
    ]
  }```

You have a misunderstanding of how ExtractTextPlugin works. Here is the signature:
ExtractTextPlugin.extract([notExtractLoader], loader, [options])
So, you should do something like:
ExtractTextPlugin.extract(
  'style-loader',
  'css-loader!sass-loader'
);

Not

```js
ExtractTextPlugin.extract(
  'style-loader',
  'css-loader',
  'sass-loader'
);

Thanks @chentsulin that worked!
Which resources can I read to have more grasp on these webpack configuration that you'd recommend?

@ceemion What does your webpack.config.development look like?


Allow specifying files in persistent configuration

It would be nice, if I could specify the files to check, format, etc. via the ruff configuration file (in my case pyproject.toml). I thought of something analogous to the files directive of mypy.
Maybe I missed something, but I found no mention of this ability to specify files in the ruff documentation and found no issues about it, when I searched for the terms files config here.
Just trying out something like this gave me an error for commands like ruff check or ruff format:
# pyproject.toml
[tool.ruff]
files = ["src", "tests"]
# ...

ruff failed
  Cause: Failed to parse /path/to/pyproject.toml
  ...
unknown field `files`

I assume this is expected and not a bug. Therefore please consider this a humble feature request.

You can use include (and extend-include) and exclude (and extend-exclude) to specify which files should be included when running check or format.

I think this is a bit different @MichaReiser. In mypy, specifying files lets you run mypy without passing it any files (and it uses that list as the default).

So the ask here is that you can set files in the configuration, and ruff check would default to checking those files (instead of .).

But I think that's roughly the same, isn't it?

A comma-separated list of paths which should be checked by mypy if none are given on the command line. Supports recursive file globbing using glob, where * (e.g. .py) matches files in the current directory and **/ (e.g. **/.py) matches files in any directories below the current one. User home directory and environment variables will be expanded.

You can set exclude and include and that specifies the paths that Ruff checks by default. You can explicitly pass files to ruff check that aren't covered by the set defined by exclude/include and ruff will check those files (unless force-exclude is specified)

@MichaReiser Maybe I am misunderstanding the logic of those directives. Would you be so kind and provide the correct configuration to accomplish the following:

ruff check (without any following positional arguments) should operate on the directories src and tests only.
The default inclusion and exclusion patterns of ruff are applied unchanged.

Yeah you might be right. It might be possible but you would at least need to override include but then there's https://github.com/astral-sh/ruff/issues/9019


Month view stop working

Im using cdn, not sure if you just drop an update on it but my calendar month view stop working without any changes. I figure out I have to add display: contents to the .ec-body class to get it back working. The week and day view were working okey
https://snipboard.io/kFeWab.jpg

In v0.15.0 I dropped support for IE. Do you have this issue reproduced on demo?

In v0.15.0 I dropped support for IE. Do you have this issue reproduced on demo?

No, I took a look and demo was working fine. I was making some changes in localhost and after 3pm the calendar stop showing. I removed my changes to see what was going on but still the same. Then I took a look into the main web page and the calendar was gone too, without pushing any changes. Luckily it was just a css fix, thank you for the cdn link, I was going to ask how to stop auto-updates

In v0.15.0 I dropped support for IE. Do you have this issue reproduced on demo?

To reproduce it, initialize the calendar using example in Pre-built browser ready bundle, and setting the view to "dayGridMonth"
After setting the height, the days will start showing again.

In v0.15.0 I dropped support for IE. Do you have this issue reproduced on demo?

To reproduce it, initialize the calendar using example in Pre-built browser ready bundle, and setting the view to "dayGridMonth"
After setting the height, the days will start showing again.

Thanks a lot for the tip. I fixed this issue in version 0.15.1. Please check.
I also corrected the README so that the code for cdn specifies the version of the library.

I hope I can close this issue.


Error in fetching the image

On android getting the colour is failing with the below trace:

Error: ImageColors: https://mobile-a5b2257ca.hana.ondemand.com/mobilemediaimage/ImageSet(Objecttype='KLAH',Objectkey='MYM_L5',Doctype='B0')/$value
at Object.promiseMethodWrapper [as getColors] (NativeModules.js:103)
at Object.getColors (index.js:8)
at eval (VM6 RootHierarchyNode.bundle:62)
at commitHookEffectListMount (ReactNativeRenderer-dev.js:15561)
at commitPassiveHookEffects (ReactNativeRenderer-dev.js:15618)
at Object.invokeGuardedCallbackImpl (ReactNativeRenderer-dev.js:265)
at invokeGuardedCallback (ReactNativeRenderer-dev.js:476)
at flushPassiveEffectsImpl (ReactNativeRenderer-dev.js:18795)
at unstable_runWithPriority (scheduler.development.js:653)
at runWithPriority (ReactNativeRenderer-dev.js:5268)

The image is not public but the same link works when given like and the image loads perfectly:
<Image               source={{uri: 'https://mobile-a5b2257ca.hana.ondemand.com/mobilemediaimage/ImageSet(Objecttype='KLAH',Objectkey='MYM_L5',Doctype='B0')/$value')}}             />

The image is not public but the same link works when given like and the image loads perfectly:
<Image source={{uri: 'https://mobile-a5b2257ca.hana.ondemand.com/mobilemediaimage/ImageSet(Objecttype='KLAH',Objectkey='MYM_L5',Doctype='B0')/$value')}} />

Sorry, this doesn't seem to work for me. Could you clarify?

Closing due to no response.

Hello,
The image has required the user to be authenticated to be displayed.

So the issue is: On iOS, the library somehow uses the standard network protocols to make requests.
But on Android, it requests images using a separate client. That's why it should require an Authorization header. What do you suggest for this?

I will see what I can do when I find some time. If you are in a rush you can download the image and save it to a file ahead of time and pass the file URI to ImageColors instead.


Can't run sample code

I've used the commands from https://facebook-sdk.readthedocs.org/en/latest/install.html to install the sdk, which is recognized by PyCharm, but when I run the project as app engine website it gives me this error:
INFO     2015-03-29 22:18:30,182 module.py:737] default: "GET / HTTP/1.1" 500 -
ERROR    2015-03-29 22:19:07,986 wsgi.py:263]
Traceback (most recent call last):
File "/opt/google_appengine/google/appengine/runtime/wsgi.py", line 240, in Handle
handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
File "/opt/google_appengine/google/appengine/runtime/wsgi.py", line 299, in _LoadHandler
handler, path, err = LoadObject(self._handler)
File "/opt/google_appengine/google/appengine/runtime/wsgi.py", line 85, in LoadObject
obj = import(path[0])
File "/home/juliano/Documents/Projetos/Fb2/fb.py", line 1, in
import facebook
ImportError: No module named facebook
INFO     2015-03-29 22:19:08,003 module.py:737] default: "GET / HTTP/1.1" 500 -

It looks like you've already received an answer to the question you posted on StackOverflow, so I am closing this issue.


public=True branch fails in s3_get_data

If you read through the preceding code, you'll see that you are appending to a variable that's not set up yet.
https://github.com/neurodata/ndmg/blob/c995f311c7d845fa78fd86e41a939d42d1156698/ndmg/utils/s3_utils.py#L117
More generally, you're duplicating stuff that you could just let the S3 libraries / command-line utilities handle - and this might break for some users in unexpected ways. For example, I have multiple AWS accounts and select them with the variable AWS_PROFILE. You're overriding that behavior by going straight to default (which may or may not exist for some people!).
But I appreciate it's a hard thing to provide a simplified interface to any of Amazon's Baroque APIs.

Thanks for the catch!
I think this function is in need of a rewrite anyway - I have been annoyed at the code that pulls and pushes s3 data for quite awhile anyway (it could be much more simple, and use boto3).
Probably the solution is to just remove the public logic entirely, and just use boto3.client's behavior.


LoggerT and CreateLogger(...Type) don't include resolved type parameter name

When using CreateLogger<SomeService<TKind>> logs don't include the resolved type of TKind.
That is, they just show up just as 'SomeNamespace.SomeService'.
From a quick look, it seems that TypeNameHelper.GetTypeDisplayName in Shared supports this. Is there a reason CreateLogger/LoggerT aren't using it?
edit: Sorry for the confusion - Markdown killed the "TKind" above.

What do you mean by resolved type of TKind? Can you please provide a code sample and the result you are expecting.

Looking again at TypeNameHelper, this behavior seems to be intentional:
https://github.com/aspnet/Extensions/blob/55518d79834d3319c91f40b449d028338b129ed6/src/Logging/Logging.Abstractions/src/TypeNameHelper.cs#L51-L54
If the goal is to avoid the '.' character in order to maintain log category hierarchy, there are certainly other solutions that would avoid it but still disambiguate the types. Even just not emitting the namespace of the type parameter wouldn't be perfect but would be better than today, IMO.
e.g.
info: loggertest.Foo`1[String][0]
      test from fooString
info: loggertest.Foo`1[Int32][0]
      test from fooInt

and of course keeping the full name but using a different separator character is another alternative.
All that said, loggerFactory.CreateLogger(GetType().ToString()); is an easy workaround. Just seems like use of generics + logging is high enough that the existing behavior will bite people once it's too late and they already have ambiguous logs.

Another workaround is to override ILogger<T> service with implementation that formats category differently.
    public class Logger<T> : ILogger<T>
    {
        private readonly ILogger _logger;

        /// <summary>
        /// Creates a new <see cref="Logger{T}"/>.
        /// </summary>
        /// <param name="factory">The factory.</param>
        public Logger(ILoggerFactory factory)
        {
            if (factory == null)
            {
                throw new ArgumentNullException(nameof(factory));
            }

-            _logger = factory.CreateLogger(TypeNameHelper.GetTypeDisplayName(typeof(T)));
+            _logger = factory.CreateLogger(typeof(T).ToString());
        }

        IDisposable ILogger.BeginScope<TState>(TState state)
        {
            return _logger.BeginScope(state);
        }

        bool ILogger.IsEnabled(LogLevel logLevel)
        {
            return _logger.IsEnabled(logLevel);
        }

        void ILogger.Log<TState>(LogLevel logLevel, EventId eventId, TState state, Exception exception, Func<TState, Exception, string> formatter)
        {
            _logger.Log(logLevel, eventId, state, exception, formatter);
        }
    }

I see your point but this feature is not frequently requested and has a risk of breaking exising logging setups.


Detect cider-disconnect, close listen-socket

If you have a weasel-repl open and kill emacs (or close the repl buffer) then the listen-socket for the websocket connection stays open, leading to a BindException: Address already in use.
A new weasel-repl should either use an already existing socket (if that's possible) or close other ones automatically.
If #51 implements close-on-disconnect we could implement it for the other direction too.

:+1:

autogenerated with https://github.com/MalloZup/doghub:  issue inactive since 450 days. Please update the issue or close it


docs: Add gtk.enable to home manager instructions

When trying to set this up in NixOS, I noticed that you also have to enable GTK management in home manager for the GTK theming to work. This could probably also be solved by instead making the home manager module automatically set gtk.enable = true if the gtk segment is enabled.

I definitely agree, in fact I think the example nixos derivation should probably enable/install all apps that get configureed (at least, the one in the flake, as its built as a ci check and some errors are missed until the app is actually enabled in hm)

Its a good point though on noting enable must be set in documentation, versus using something like app.enable = lib.mkForce true.
It would probably be more convenient to force enable, but are there any drawbacks or blocked patterns here? I cant think of much reason a user would want to enable the themes and not the app

What does mkForce do exactly? I'm still pretty new to Nix and especially to NixOS/home-manager.


Automated cherry pick of #3523: lockman: log bug with Errorf

Cherry pick of #3523 on release/2.11.
#3523: lockman: log bug with Errorf

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@6fc1d3a). Click here to learn what that means.
The diff coverage is 19.53%.

@@              Coverage Diff               @@
##             release/2.11   #3618   +/-   ##
==============================================
  Coverage                ?   7.14%
==============================================
  Files                   ?     479
  Lines                   ?   77782
  Branches                ?       0
==============================================
  Hits                    ?    5557
  Misses                  ?   71756
  Partials                ?     469

Flag
Coverage Δ

#aFlag
7.14% <19.53%> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/db/lockman/inmemory.go
67.07% <0%> (ø)

pkg/cloudcommon/db/lockman/bug.go
0% <0%> (ø)

pkg/cloudcommon/db/lockman/etcd.go
20% <20%> (ø)

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 6fc1d3a...ba93c96. Read the comment docs.

/lgtm

/approve

/approve


Cannot construct NetworkManagementClient because type incompatible @azure/arm-network

Package Name: @azure/arm-network
Package Version: 19.1.0
Operating system:
[ ] nodejs

version:

[x] browser

name/version: Edge dev preview

[x] typescript

version: 3.8.3

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
cannot compile the following code
const subscriptionId = "xxx"
const authManager = new AuthManager({
    clientId: "xxx"
})

document.addEventListener("DOMContentLoaded", () => {
    authManager.finalizeLogin().then((res) => {
        var results = document.getElementById('results')
        if (!res.isLoggedIn) {
            results.innerText = "Not logged in"
        } else {
            const creds = res.creds
            const client = new NetworkManagementClient(creds, subscriptionId); // this line doesn't compile, see below for error.
        }
    })
})

The error is
  Types of property 'signRequest' are incompatible.
    Type '(webResource: import("D:/dev/az-api-test/node_modules/@azure/ms-rest-browserauth/node_modules/@azure/ms-rest-js/es/lib/webResource").WebResource) => Promise<import("D:/dev/az-api-test/node_modules/@azure/ms-rest-browserauth/node_modules/@azure/ms-rest-js/es/lib/webResource").WebResource>' is not assignable to type '(webResource: import("D:/dev/az-api-test/node_modules/@azure/ms-rest-js/es/lib/webResource").WebResource) => Promise<import("D:/dev/az-api-test/node_modules/@azure/ms-rest-js/es/lib/webResource").WebResource>'.
      Types of parameters 'webResource' and 'webResource' are incompatible.
        Type 'import("D:/dev/az-api-test/node_modules/@azure/ms-rest-js/es/lib/webResource").WebResource' is not assignable to type 'import("D:/dev/az-api-test/node_modules/@azure/ms-rest-browserauth/node_modules/@azure/ms-rest-js/es/lib/webResource").WebResource'.
          Types of property 'headers' are incompatible.
            Type 'import("D:/dev/az-api-test/node_modules/@azure/ms-rest-js/es/lib/httpHeaders").HttpHeaders' is not assignable to type 'import("D:/dev/az-api-test/node_modules/@azure/ms-rest-browserauth/node_modules/@azure/ms-rest-js/es/lib/httpHeaders").HttpHeaders'.
              Types have separate declarations of a private property '_headersMap'.

To Reproduce
Steps to reproduce the behavior:

start a new typescript web client project
npm install @azure/ms-rest-browserauth and npm install @azure/arm-network
try to construct NetworkManagementClient like my code above
compile fails

Expected behavior
The code compiles
Screenshots
N/A
Additional context
The reason behind this is @azure/ms-rest-browserauth and @azure/arm-network use their own different @azure/ms-rest-js, which causes the error.
Question:
Many @azure js sdk libs depend on @azure/ms-rest-js. Is it possible to use Peer Dependencies, so each sdk client shares a single copy of @azure/ms-rest-js instead of having copies for everyone? And it should also solve this kind of issues.
related:
https://github.com/Azure/azure-sdk-for-js/issues/4145
https://github.com/Azure/azure-sdk-for-js/issues/4793

This seems to be another instance of a management package needing to be regenerated to work with the newer version of ms-rest-js, see #7763

@xirzec  The version of Network SDK is already 2.X  https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/network/arm-network/package.json#L7 why there still has problems.

Actually, this looks like a subtly different bug with types. One mistake that was made was typing public interfaces with a concrete class (WebResource) instead of using an interface type that omits private members. We have similar issues inside @azure/core-http.
@daviwil can you take a look at what is going on here specifically?

This is most likely because @azure/ms-rest-browserauth is still using v1 of @azure/ms-rest-js. See https://github.com/Azure/ms-rest-browserauth/blob/8f4a086253bb36cd50faf727ed8b7cd08fb9ff4f/package.json#L45
https://github.com/Azure/ms-rest-browserauth/issues/29 should fix that

Many @Azure js sdk libs depend on @azure/ms-rest-js. Is it possible to use Peer Dependencies, so each sdk client shares a single copy of @azure/ms-rest-js instead of having copies for everyone? And it should also solve this kind of issues.

The problem is that we have a mix of Azure sdks that depend on different major versions of @azure/ms-rest-js. The newer lot are incompatible with older dependency versions and vice versa. Therefore, all sdks cannot share a single copy of @azure/ms-rest-js.

@seekerlee We just released version 1.0.0 of the @azure/ms-rest-browserauth package where the dependency on @azure/ms-rest-js is updated. Please try this latest version and the issue you are seeing should be resolved.

thank you!


Updated to swift 3 syntax and changed NSURL to URL

Closing as no longer needed due to new pull request #12


Random join option

An option to join a round but with a random option (maybe called any?) for those who don't care what they want.
Possible slack commands:
/teatime joinrandom
/teatime joinany
/teatime luckydip
/teatime join random will break if theres an option called random

I think I lick luckydip the most


Feature Request: Allow formatting of pagination page ranges for i18n...

Hello!
While all the other text in the table can be internationalised, there is one item that can't:

1-10 of 100

Could we have an option to at least change the word "of"?
Thanks! :-)

sure! I'll add that in to the next patch.

added in v1.9.1

@xaksis That's great news. I'll update to it later this week. Thanks so much for the quick patch!


cache block during eth replay

Describe your changes and provide context
Prevent having to query block for every transaction
Testing performed to validate your change
replay

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 62.31%. Comparing base (cd3e074) to head (8890bdf).

Additional details and impacted files

@@            Coverage Diff             @@
##            seiv2    #1471      +/-   ##
==========================================
+ Coverage   62.04%   62.31%   +0.26%
==========================================
  Files         352      352
  Lines       24402    24397       -5
==========================================
+ Hits        15140    15202      +62
+ Misses       8398     8325      -73
- Partials      864      870       +6

Files
Coverage Δ

app/eth_replay.go
0.00% <0.00%> (ø)

x/evm/keeper/keeper.go
59.32% <0.00%> (+1.18%)
:arrow_up:

... and 2 files with indirect coverage changes

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 61.72%. Comparing base (ae86474) to head (130affe).

Additional details and impacted files

@@            Coverage Diff             @@
##            seiv2    #1471      +/-   ##
==========================================
- Coverage   61.87%   61.72%   -0.16%
==========================================
  Files         354      354
  Lines       24650    24646       -4
==========================================
- Hits        15253    15213      -40
- Misses       8515     8554      +39
+ Partials      882      879       -3

Files
Coverage Δ

app/eth_replay.go
0.00% <0.00%> (ø)

x/evm/keeper/keeper.go
49.28% <0.00%> (+0.69%)
:arrow_up:

... and 1 file with indirect coverage changes


bgcolor deprecated

bgcolor is deprecated, using style instead

Deprecated is not really a word used in the email world. Some email programs will only accept deprecated markup, but it's true that the current mixture of styles and html attributes is confusing to say the least, and not only applicable to this template.
I'd rather rely on mailchimp and others who spend a lot of time thinking about compatibility issues, but sometimes we need our template eg. for webserver use, and this was pretty good from the start. I added some outlook-specific adjutements to the IGSO fork.

@tund3r I'd rather keep it in there for email client compatibility purposes. Just in case.


Inheritance

Classes and structs should be allowed to inherit from other classes and structs respectively.
class Animal {
}

class CatDog: Animal {
}

struct Sport {
}

struct Football: Sport {
}

Note that a struct can't inherit from a class and vice versa, as that would break the reference counting ownership model.

I know it's very very early but I hope to see soon some proper light RFCs so some thought goes into these and a public roadmap. Very interested how this will evolve.

Great input!

Dart uses mixins, a concept which lets you add features to a class without using multiple inheritance like explained in this article.
If you are allowing inheritance, please consider adding super calls in the constructor and avoid having to call the super constructor explicitly, as was just announced in Dart 2.17 :)


Migrate /subscribers command to Helix API

As part of Twitch's announced deprecation of IRC-based commands (see here for more info, the /subscribers command needs to be migrated to use the relevant Helix API endpoint.
Helix API reference: https://dev.twitch.tv/docs/api/reference#update-chat-settings
Split from #3956

I'd like to migrate this command (see #3966).


should I worried about  mutex  in Mapscan?

should I worried about map mutex when use row. Mapscan?
rows, err := db.Queryx("SELECT * FROM place")
for rows.Next() {
results := make(map[string]interface{})
err = rows.MapScan(results)
}
since map  need rwmutex to use in concurrency
https://blog.golang.org/go-maps-in-action

If the map is local to that goroutine (it probably will be) you won't need
a mutex - the only thing writing to the map should be the MapScan method.
On Fri, Oct 9, 2015 at 8:00 AM arief nur andono<EMAIL_ADDRESS>wrote:

should I worried about map mutex when use row. Mapscan?
rows, err := db.Queryx("SELECT * FROM place")
for rows.Next() {
results := make(map[string]interface{})
err = rows.MapScan(results)
}
since map need rwmutex to use in concurrency
https://blog.golang.org/go-maps-in-action
—
Reply to this email directly or view it on GitHub
https://github.com/jmoiron/sqlx/issues/176.

so the problem appear when I create map in main the written by goroutines so I need mutex.  map inside goroutines is no problem?

Correct. If you're sharing a map around your program - and have multiple
writers - you must use a mutex (else you will suffer problems).
If you have a HTTP handler that calls a database function, and the function
creates (and returns) a map of the results, that's fine.
On Fri, Oct 9, 2015 at 9:43 AM arief nur andono<EMAIL_ADDRESS>wrote:

so the problem appear when I create map in main the written by goroutines
so I need mutex. map inside goroutines is no problem?
—
Reply to this email directly or view it on GitHub
https://github.com/jmoiron/sqlx/issues/176#issuecomment-146733889.

great! thanks a lot

You only have problems when accessing the same data from different goroutines.   I also suggest trying out the race detector.

thank you


Fail updating astroarch.

When I try to update astroarch using sudo pacman -Syu. I get a error with astroarch.db download.
failed retrieving file astroarch.db from astroarch.astromatto.com:9000: the request url returned error: 404

hi @jmvillalba my server died when I was on holiday, I will rebuild it today, so it should be available again in a couple of hours

@jmvillalba everything should be up since last week. I am closing this but please feel free to re-open if something is still now working, thanks!

Thanks for your work.
Great!
El lun., 2 ene. 2023 11:50, Mattia Procopio @.***>
escribió:

@jmvillalba https://github.com/jmvillalba everything should be up since
last week. I am closing this but please feel free to re-open if something
is still now working, thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/devDucks/astroarch/issues/12#issuecomment-1368831974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ2ILSYCFO2L7SPOCLAE2QTWQKXGRANCNFSM6AAAAAASQNDFFQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Uses IRI class in all vocabularies

This PR addresses GitHub issue: #171
It uses IRI instead of URI in all classes in the org.eclipse.rdf4j.model.vocabulary package

Looks good to me. I'll run quick smoke test and if nothing breaks, I'll merge. Thanks!


How i can pass delegate to SetValue?

In Jint i can make something like this:
_engine.SetValue("print", (text)=>{Console.WriteLine(text);});

Is there any way to make something like this in Topaz? I get a Tenray.Topaz.TopazException: Constructor call on null is not defined. when i try to pass a delegate to engine.SetValue()

The following code works fine. Could you share the exact code that you get the exception?
    public void TestLambdaFunction()
    {
        var engine = new TopazEngine();
        engine.SetValue("print", (string text) => { Console.WriteLine(text); });
        engine.ExecuteExpression("print('text')");
    }

I get exception when i try to use engine.SetValue("print", (text)=>{Console.WriteLine(text);});, but its work when i mark types explicit like in your explame (string text)=>{Console.WrtieLine(text);}, thanks you for the help!


Update otel

Update otel

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.80%. Comparing base (4a94a4e) to head (2202897).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   93.80%   93.80%
=======================================
  Files           6        6
  Lines         210      210
=======================================
  Hits          197      197
  Misses          9        9
  Partials        4        4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


GitLab cache problem

So, I've been using GitLab CI to automatically deploy native versions as well as WebAssembly versions of my application. The problem is, that if I enable cache to speed up compilation, cargo-web produces outdated binary. Native builds with cargo build work fine.
I've managed to get a minified example here: https://gitlab.com/kuviman/cargo-web-cache-test
This is just a simple hello-world app:
fn main() {
    println!("This is my test. My test is amazing.");
}

Here's what I do in the script:
cargo web deploy --release --target wasm32-unknown-emscripten

And I cache the entire target directory:
cache:
  paths:
    - target

The first build (when nothing is yet cached) goes fine, but if I change the text in the example, I see that cargo web still produces old wasm file (I check it using node)
This is the job's (https://gitlab.com/kuviman/cargo-web-cache-test/-/jobs/114564134) log:
$ cargo web build --release --target wasm32-unknown-emscripten
info: downloading component 'rust-std' for 'wasm32-unknown-emscripten'
info: installing component 'rust-std' for 'wasm32-unknown-emscripten'
   Compiling cargo-web-cache-test v0.1.0 (/builds/kuviman/cargo-web-cache-test)
    Finished release [optimized] target(s) in 1.29s
$ cargo web deploy --release --target wasm32-unknown-emscripten
    Finished release [optimized] target(s) in 0.00s
The `cargo-web-cache-test` was deployed to "/builds/kuviman/cargo-web-cache-test/target/deploy"!
$ cat src/main.rs
fn main() {
    println!("This text is in code but not in wasm binary");
}
$ (cd target/deploy && node cargo-web-cache-test.js)
This is my test. My test is amazing.
$ (cd target/wasm32-unknown-emscripten/release && node cargo-web-cache-test.js)
This is my test. My test is amazing.
$ cargo run
   Compiling cargo-web-cache-test v0.1.0 (/builds/kuviman/cargo-web-cache-test)
    Finished dev [unoptimized + debuginfo] target(s) in 0.94s
     Running `target/debug/cargo-web-cache-test`
This text is in code but not in wasm binary

I am pretty sure it's an issue with cargo-web, and I wonder if this also can be reproduced on Travis or is it GitLab-specific

Hmm... this is interesting. Although if it reproduces on wasm32-unknown-emscripten it may simply be a rustc bug. (I don't do too much acrobatics on wasm32-unknown-emscripten, unlike on wasm32-unknown-unknown.) I'm guessing the issue here might be that the process of restoring the cache changes the mtime of some of the files in relation to others which makes the build system think that there is nothing to rebuild.
Can you do a retest and run this command before cargo web build and after? (Both with a clean cache and a full cache?)
find . -type f -print0 | xargs -0 ls -l --time-style="+%F %T.%N"

Ok, and I've also changed the message to be generated so we see that wasm file contains previous build easier:

$ date "+%F %T.%N" > message
...
$ cat message
2018-10-30 23:16:39.281211204
$ (cd target/wasm32-unknown-emscripten/release && node cargo-web-cache-test.js)
2018-10-30 23:12:23.156200724

Job with cache cleared: https://gitlab.com/kuviman/cargo-web-cache-test/-/jobs/114620889
Job with cached produced by previous one: https://gitlab.com/kuviman/cargo-web-cache-test/-/jobs/114621656
I see that times of files in target/ look like real ones of the previous build, and source files are just cloned, so source files are newer than built app, and everything should be rebuilt correctly.
I am pretty sure that actual compilation is being done. In my real project that is a repo consisting of several crates, cargo shows that all these crates are being compiled.
I assume that multiple files are generated when compiling (crate-$hash directories with different hashes), and when linking wrong files are being used.
Although I see no problem when using it on my PC.
This may be a rustc bug indeed. I should test this without cargo-web I suppose. wasm32-unknown-unknown does work, it looks like, but I prefer using stable.

Sorry, forgot to include find output after build. Here:

https://gitlab.com/kuviman/cargo-web-cache-test/-/jobs/114627055
https://gitlab.com/kuviman/cargo-web-cache-test/-/jobs/114627630

It is also strange that with clean cache, cargo is building the app twice: first taking 1.5 sec (little time), and second taking 1.5 min (long time).
With full cache, there is only one build, and only the short (1.5 sec) one
Isn't it true that most time here should be spend in emscripten, so this should indicate that emcc is not run with cache? Double build is coming from cargo-web, right?

Hello! I was trying to see if this would work with rustc, and it does work properly.
But there is this strange thing: cargo-web says (this job, clean build no cache involved):
cargo_web::cargo_shim: No artifacts were generated yet build succeeded; retrying...

And in a log of build without cargo-web you can see that there are artifacts, although I tried to replicate the environment exactly, so the only difference should be in how emscripten is set up.
According to this commit there is some issue with newly installed emscripten, although I can't find more info on that.
So, what happenes is I think this: this bug (bug in Emscripten?) is still happening, but rustc thinks the old wasm is still the output. And even double build does not help. What helps though is removing .js & .wasm files from the target/../../deps directory

Yes, there is a bug, either in rustc or in Emscripten where immediately after a clean installation of Emscripten the first build produces no artifacts. I have no idea why.
In your job without cargo-web are you sure the docker image with the Emscripten doesn't have the Emscripted already "warmed up"? E.g. ~/.emscripten, ~/.emscripten_cache, ~/.emscripten_cache.lock, ~/.emscripten_sanity should not exist.

I think I'm running into this problem. I am building locally but via a Docker image, and the artifact is not updated
docker run -ti --rm -v $(pwd):/src -w /src remram/rust-cargo-web:latest cargo web deploy --release


Icon or IconButton in Tab

I dynamically create a list of Tab inside Tabs. It works perfectly. I want to close the Tab on clicking a close icon in the Tab and get struck with it .
Tab accepts only lable and value as parameters. I am using the lable parameter to add IconButton to the tab. The IconButton gets displayed but when is use onClick on this IconButton the function doesn't get triggered when I click this IconButton. Is it possible to add Icon or IconButton in Tab?
Also, I am thinking if it will make more sense to have leftIcon, rightIcon, rightIconButton` properties in Tab as we do in ListItem

+1, it would be great to have onClickon IconButton components.

@ganesshkumar  have you tried using onTouchTap={this.handlerFunction } instead of onclick?

Any workaround to be suggested here?

An icon property was added to the Tab component a long time ago.
It looks like this:
    /**
     * Sets the icon of the tab, you can pass `FontIcon` or `SvgIcon` elements.
     */
    icon: PropTypes.node,

I'm closing the issue.


Implement z_listunifiedreceivers and z_validateaddress RPCs

Motivation
Some mining pools use these RPCs to check addresses.
Specifications
https://zcash.github.io/rpc/z_listunifiedreceivers.html
https://zcash.github.io/rpc/z_validateaddress.html
https://zcash.github.io/rpc/validateaddress.html
Designs
We can call the zcash_address crate to validate shielded and unified addresses. (Zebra also has its own transparent address parsing, but we'd be better to just be consistent and use zcash_address for everything.)
We just need to implement these fields:
Transparent:

p2pkh
p2sh
scriptPubKey (optional, only do it if it's easy)
pubkey (optional, only do it if it's easy)
isscript

Shielded:

sapling
orchard

All:

isvalid
address
type
address_type (same as type)
ismine - always false, because Zebra doesn't have a wallet

Related Work

#5719

We should implement these, however since they are not strictly mining RPCs they don't fall within the scope of the MVP.

We should implement these, however since they are not strictly mining RPCs they don't fall within the scope of the MVP.

Some mining pools won't be able to use Zebra until we implement these RPCs.

I added validateaddress to this ticket, because some mining pool software needs it. The fields are almost exactly the same as z_validateaddress, just with different names.

Note that the type field is deprecated and will be disabled by default in zcashd 5.4.0. It is being renamed to address_type.

Note that the type field is deprecated and will be disabled by default in zcashd 5.4.0. It is being renamed to address_type.

Since that change hasn't been released yet, we might use both names until miners update.

Hey team! Please add your planning poker estimate with Zenhub @arya2 @conradoplg @dconnolly @oxarbitrage @teor2345 @upbqdn

@arya can you please update the estimate here, if necessary, after splitting off the original issue


Gamescope doesn't update with new frames from aplication after #6268 presumably

System Info and Version
 System/Version info
Hyprland, built from branch  at commit 9994b73ad0af5c9ba5fc4058234cea77d0a1ddb1  ().
Date: 2024-06-08
Tag: , commits:

flags: (if any)

System Information:
System name: Linux
Node name: nixos
Release: 6.9.3
Version: #1-NixOS SMP PREEMPT_DYNAMIC Thu May 30 07:45:04 UTC 2024

GPU information:
09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c3) (prog-if 00 [VGA controller])

os-release: ANSI_COLOR="1;34"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="24.11.20240607.051f920"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 24.11 (Vicuña)"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="24.11 (Vicuña)"
VERSION_CODENAME="vicuña"
VERSION_ID="24.11"

plugins:
  hyprsplit by shezdy ver 1.0

======Config-Start======

Config File: /home/noah/.config/hypr/hyprland.conf: Read Succeeded
exec-once = /nix/store/bnipzdfv788l7yvgn7k7s7gp76sd1zpz-dbus-1.14.10/bin/dbus-update-activation-environment --systemd DISPLAY HYPRLAND_INSTANCE_SIGNATURE WAYLAND_DISPLAY XDG_CURRENT_DESKTOP && systemctl --user stop hyprland-session.target && systemctl --user start hyprland-session.target
plugin=/nix/store/861wyd4zv4xcwg18qa0nwg1c7yk1fa06-hyprsplit-0.1/lib/libhyprsplit.so
$mod=SUPER
debug {
  disable_logs=false
  enable_stdout_logs=true
}

decoration {
  blur {
    enabled=true
    passes=3
    size=5
  }
  blurls=bar-0
  blurls=bar-1
  blurls=launcher
  blurls=notifications0
  blurls=notifications1
  blurls=mpris
  rounding=8
}

device {
  name=wacom-intuos-s-pen
}

dwindle {
  preserve_split=true
}

general {
  border_size=2
  col.active_border=rgba(74c7ecff)
  col.inactive_border=rgba(1e1e2eff)
  gaps_in=5
  gaps_out=10
}

input {
  accel_profile=flat
  follow_mouse=1
  mouse_refocus=false
}

misc {
  disable_hyprland_logo=true
}
animation=workspaces, 1, 5, default, slidevert
animation=windows, 1, 5, default, slide
animation=layers, 1, 5, default, slide
bind=, XF86AudioPlay, exec, playerctl play-pause
bind=, XF86AudioNext, exec, playerctl next
bind=, XF86AudioPrev, exec, playerctl previous
bind=CTRL, Print, exec, satty-shot
bind=, Print, exec, hyprshot -m output -o ~/Pictures/Screenshots
bind=$mod, p, exec, wl-copy $(hyprpicker)
bind=$mod, h, movefocus, l
bind=$mod, l, movefocus, r
bind=$mod, k, movefocus, u
bind=$mod, j, movefocus, d
bind=$mod SHIFT, h, movewindow, l
bind=$mod SHIFT, l, movewindow, r
bind=$mod SHIFT, k, movewindow, u
bind=$mod SHIFT, j, movewindow, d
bind=$mod, slash, togglesplit
bind=$mod, mouse_down, split:workspace, e-1
bind=$mod, mouse_up, split:workspace, e+1
bind=$mod, t, togglefloating
bind=$mod, c, killactive
bind=$mod, q, exec, shutdown-menu
bind=$mod, B, exec, firefox
bind=$mod, y, exec, kitty -e yazi
bind=alt, f4, exec, hyprctl kill
bind=$mod, Return, exec, kitty
bind=$mod, Space, exec, fuzzel
bind=$mod, E, exec, bemoji -n
bind=$mod, a, exec, kitty -e ollama run mixtral
bind=$mod SHIFT, a, exec, llm-actions
bind=$mod, 1, split:workspace, 1
bind=$mod SHIFT, 1, split:movetoworkspace, 1
bind=$mod, 2, split:workspace, 2
bind=$mod SHIFT, 2, split:movetoworkspace, 2
bind=$mod, 3, split:workspace, 3
bind=$mod SHIFT, 3, split:movetoworkspace, 3
bind=$mod, 4, split:workspace, 4
bind=$mod SHIFT, 4, split:movetoworkspace, 4
bind=$mod, 5, split:workspace, 5
bind=$mod SHIFT, 5, split:movetoworkspace, 5
bind=$mod, 6, split:workspace, 6
bind=$mod SHIFT, 6, split:movetoworkspace, 6
bind=$mod, 7, split:workspace, 7
bind=$mod SHIFT, 7, split:movetoworkspace, 7
bind=$mod, 8, split:workspace, 8
bind=$mod SHIFT, 8, split:movetoworkspace, 8
bind=$mod, 9, split:workspace, 9
bind=$mod SHIFT, 9, split:movetoworkspace, 9
bind=$mod, 0, split:workspace, 10
bind=$mod SHIFT, 0, split:movetoworkspace, 10
binde=, XF86AudioRaiseVolume, exec, wpctl set-volume -l 1.4 @DEFAULT_AUDIO_SINK@ 1%+
binde=, XF86AudioLowerVolume, exec, wpctl set-volume -l 1.4 @DEFAULT_AUDIO_SINK@ 1%-
binde=$mod CTRL, l, resizeactive, 10 0
binde=$mod CTRL, h, resizeactive, -10 0
binde=$mod CTRL, k, resizeactive, 0 -10
binde=$mod CTRL, j, resizeactive, 0 10
bindm=$mod, mouse:272, movewindow
bindm=$mod, mouse:273, resizewindow
exec-once=ags
exec-once=fcitx5
exec-once=wpaperd
exec-once=mpv --no-video --volume=150 /nix/store/ag6v7p7x8ksxirkyqjl9xfsmhzr45w31-start.wav
layerrule=ignorealpha, bar-0
layerrule=ignorealpha, bar-1
layerrule=ignorealpha, notifications0
layerrule=ignorealpha, notifications1
layerrule=ignorealpha, mpris
layerrule=ignorealpha, launcher
layerrule=noanim,selection
monitor=DP-2, 1920x1200, 1920x0, 1
monitor=DP-1, 1920x1080@165, 0x0, 1, vrr, 1
windowrulev2=noanim, class:^(com.gabm.satty)$
windowrulev2=size 640 360, title:(Picture-in-Picture)
windowrulev2=pin, title:^(Picture-in-Picture)$
windowrulev2=move 1906 14, title:(Picture-in-Picture)
windowrulev2=float, title:^(Picture-in-Picture)$

======Config-End========

Bug or Regression?
Regression
Description
Gamescope was working okayish once #6159 was fixed but after #6268 being merged (I assume) it doesn't update when a new frame is submitted after a few frames. Chromium does kinda but only every few minutes, Kitty doesn't at all after the first few frames enough to see cursor blink then it freezes, and QT apps seem uneffected.
How to reproduce

Use newest Hyprland version with Wayland Core rewrite
Open Kitty in Gamescope
See no new frames or anything after first few
Open Chromium browser
See new frames only every few minutes

Crash reports, logs, images, videos
WAYLAND_DEBUG=1 gamescope -r 165 -W 1920 -H 1080 kitty closing instantly after trying to type (no new frames after first few)
wl_debug_kitty.txt
WAYLAND_DEBUG=1 gamescope -r 165 -W 1920 -H 1080 brave waiting for it to update then closing
wl_debug_kitty.txt
https://github.com/hyprwm/Hyprland/assets/45698918/0fafaac0-350f-4a35-a920-084744bda68b

must be the work of an enemy stand

works for me just fine, both nested and on a real session.

I reproduced it on my system loading the default Hyprland config with --config

still can't repro. Does it go away with debug:damage_tracking=1?

Time to give myself a seizure

tracking not blink

I thought it was like that Android developer setting sorry, but it doesn't do anything it's the same

Maybe this could be the home manager module?

what about damage_tracking = 0?

Same thing

then dunno lemao

I'm having the same issue with krita under gamescope, happens only  after opening the canvas (that, as far as I know, uses a gl context) not in the initial view.

works for me (excuse my artistic prowess)

just in case, I  tested with gamescope 3.14.16

I must just have skill issue I guess

Just tested Krita, it bugs in the same way for me so we both have the same issue seemingly. Judging by @leiserfg he seems to also be using NixOS maybe?... Curious
https://github.com/hyprwm/Hyprland/assets/45698918/db7bef94-34dc-4986-9357-c60d77ea39ac
Also noticed drop downs are bugged, likely Gamescope maybe? I'd hope but still :/

Judging by @leiserfg Github profile he seems to also be using NixOS maybe?

Yes, I'm in nixos too.

Home manager module? I have both installed since it caused issues with XWayland to only have the home manager module
{inputs, ...}: let
  global = import ../global-var.nix;
in {
  programs.hyprland.enable = true;

  home-manager.users.${global.username} = {pkgs, ...}: {
   ...
wayland.windowManager.hyprland = {
      # Uses package from flake pulling the newest Git version
      package = inputs.hyprland.packages.${pkgs.system}.hyprland;
      enable = true;
      ...

Also find it really weird that with Hyprland somehow the corner rounding effects Gamescope?! I thought it was nested compositor so that wouldn't have a effect on it right?

Anyway, you seem to be the Nix guy @fufexan maybe look into this and see if you can reproduce it. As only two people having this happen to be Nix users, I imagine something needs to be updated or something? Other person also seems to be using hm module when I take a look at their dots

Yes, I'm the other person 😄  I'm using hyprland from the flake but building it myself following nixpkgs from stable to avoid messing with mesa versions.

Getting the same issue in both kitty and krita. Running gamescope 3.14.18.

Chromium gives interesting errors which is only app that semi works bit not really
[22345:22345:0615/141034.048079:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[0615/141038.916356:ERROR:process_memory_range.cc(75)] read out of range
[22345:22345:0615/141038.940406:ERROR:gpu_process_host.cc(999)] GPU process exited unexpectedly: exit_code=512
[22652:22652:0615/141039.114948:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
xdg_backend: Changed refresh to: 59.950hz
xdg_backend: Changed refresh to: 164.917hz
xdg_backend: Changed refresh to: 59.950hz
xdg_backend: Changed refresh to: 164.917hz
[22652:22652:0615/141054.244930:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!

I found a good workaround for now though! --backend sdl completely bypasses the issues

I found a good workaround for now though! --backend sdl completely bypasses the issues

I moved to 3.14.18 to test it, it does not fix the issue for real (to me). At least with krita it blinks a lot, alternating between new and old frames. And new ones are not coming all the time, so more like old and older frames.

I found a good workaround for now though! --backend sdl completely bypasses the issues

I moved to 3.14.18 to test it, it does not fix the issue for real (to me). At least with krita it blinks a lot, alternating between new and old frames. And new ones are not coming all the time, so more like old and older frames.

Do you happen to be using NVIDIA? I am not haviing any issues like that, but reminds me of explicit sync issues a lot. Only bug I have in Krita with --backend sdl is for some reason the cursor is locked to the canvas and will teleport back if you move outside of it

I can reproduce this on Arch.   The --backend sdl workaround works for me while lightly testing (tested in Dota 2) , as seems to downgrading to gamescope 3.14.2.

So I guess this isn't NixOS :o

I noticed something really weird when I tried --backend sdl on Sway, in Krita at least it acts like Hyprland before https://github.com/hyprwm/Hyprland/issues/6159 was fixed but Kitty seems uneffected. The normal Wayland backend is fine and works perfectly, so it's opposite on Sway than in Hypland which is strange coincidence

Do you happen to be using NVIDIA?

No, AMD with igpu (framework13).

Here from https://github.com/ValveSoftware/gamescope/issues/1374, seems to be an issue with Hyprland. Downgrading to 39 helped, using the default config didn't. Using --force-composition for gamescope fixes it as well but leads to horrible performance. AMD 6700XT here.

Can confirm that flag also works for me maybe gives more insight, also it seems to make the borders not rounded

Completely forgot about that I am sorry

 Not an issue on my end here on the amd desktop. I'll test my laptop tomorrow, but I doubt anything will be different.
Is there anything in common between you guys that could be a clue in why this happens?
I assume disabling damage tracking doesnt fix this

Maybe going out of a limb here but what GPU exactly? Everyone that has had this is using RNDA2, aren't you on RDNA3 GPU? I forgot didn't you once say something like 7800 XT? At this point only thing I can think of, and no disabling damage tracking does nothing

I had this issue on Hyprland (but not on X11 or sway), with both my igpu (intel) and egpu (nvidia 555) while trying to run vkcube through gamescope. The --backend sdl flag resolved the issue. Arch btw.

Well another major rewrite is soon, might fix or more likely not. But at least Vaxry can focus on squashing a hopefully most of the bugs that came with it

thats the plan

So far Aquamarine has has no effect unfortunately

I still can't repro this. IMO this is some config opt doing this.

Try default config then because happens there

I'm just notifying that in aquamarine this is still happening.

Has been fixed by #7110 on my end.

It was also fixed for me (please leave a 👍  to avoid more me-too comments).

:)

Same, but also it crashes when I fullscreen with meta + f also seriously hate how they insist on using meta... who's idea was that at Valve? I think it's the same people that can't count to 3


Update mapping with BasicAirData GPSLogger v3.0

Hello LearnOSM team,
Today we updated BasicAirData GPSLogger to the v3.0 (https://github.com/BasicAirData/GPSLogger).
The new release brings many interesting features for the users and some news on user interface.
For example we introduced a new bottom bar, strongly inspired by audio recorders, with the hope to give users a more friendly interface.
I updated article and images, describing the basic usage with the new UI.
I added also the GIMP format of the image that contains some text, in case some translators would edit it.
Feel free to delete if it is the wrong place to store it.

PS: I hope this is the right place to request the pull.
If not, please tell me where to post and I'll be glad to move it in the right repo.

You found the perfect location for the pull request. Just be a little patient as we are all volunteers and take care of this project in our spare time - and I was travelling. I should be able to integrate this by the weekend.

Perfect.

We understand perfectly: also BasicAirData is made by volunteers, we use our spare time to take care of it.

Thanks for the update!

To date only the English version of the BasicAirData GPS Logger article is published (with related updated images), but the page in other languages describe the old way to work.
As a result, images and text are not coherent, and could create confusion for users.
Is there a way to mark the changed part of the article as untranslated in Transifex, in order to report to translators that some paragraphs would need a review?
Thanks.

Thank you for notifying us - there was a glitch in updating the English source. I fixed this now, updated the German translation and will pull it over to LearnOSM tonight.
We have no influence on how quickly other languages will be translated - Transifex clearly shows translation quota for the different sources, interested people can see where work is left to be done. But as with LearnOSM itself almost everyone does the work in his/her spare time so we will have to wait.

Perfect, thanks again.
I taken the opportunity to update italian translation too.

I just pushed the updated contents in Dutch, German and Italian to the website.


[Bug] [DataQuality]  Incorrect concatenated SQL in the generated JSON for 'multi table accuracy check'

Search before asking

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

What happened
Incorrect concatenated SQL in the generated JSON for 'multi table accuracy check'
It should be test. test1, not test_ test1
What you expected to happen
Problem with string concatenation
How to reproduce
Create a task to reproduce it
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

duplicate https://github.com/apache/dolphinscheduler/issues/14157 and close


Add support for "conf" format

Hi, thank you for this great app! I wanted to show a Supervisor conf snippet, but the format is not listed. Here is a file example (looks like Github does not support it either, it works on VSCode by the way):
[program:laravel-worker]
process_name=%(program_name)s_%(process_num)02d
command=php /home/forge/app.com/artisan queue:work sqs --sleep=3 --tries=3 --max-time=3600
autostart=true
autorestart=true
stopasgroup=true
killasgroup=true
user=forge
numprocs=8
redirect_stderr=true
stdout_logfile=/home/forge/app.com/worker.log
stopwaitsecs=3600

Working example on VSCode (through md format)

Hi @khalyomede, thanks, I'm glad you like Showcode!
Showcode uses Shiki under the hood for syntax highlighting, and conf it is not listed there as a supported language:
https://github.com/shikijs/shiki/blob/main/docs/languages.md
We'll have to add it as a custom language, though I'm not sure where that language would be located/hosted. Do you have an idea?

Hey @stevebauman, thanks for the clarification!
I may give a try to open an issue on https://github.com/shikijs/shiki to add support for this format what do you think about it?

Sure you can give it a shot!
Though, maybe .ini is what you're looking for? Seems to provide very similar highlighting:

With github-dark-dimmed:

Oh, that is actually just perfect! Thank you :rocket: I will close this one for now.

Perfect! No problem, always happy to help 🙏

I'll add conf in the list as an alias for ini for others in the future 👍


HKDF 2: use internal implementations in TLS 1.3

Description
This is a follow-up to https://github.com/ARMmbed/mbedtls/issues/5401 and https://github.com/ARMmbed/mbedtls/issues/5402: now that we have internal implementations of HKDF components in ssl_tls13_keys.c we should used them instead of mbedtls_hkdf_ functions.
Resolve #5403
Todos

[x] Tests

Internal CI's all green :tada:


⚠ ComboForum has degraded performance

In 64a706d, ComboForum (https://comboforum.com) experienced degraded performance:

HTTP code: 200
Response time: 3344 ms

Resolved: ComboForum performance has improved in ee55110.


[BUG] tf.layers.dropout not working

To reproduce the issue:
sess = tf.Session()
x = tf.ones([4, 4])
y = tf.layers.dropout(x, 0.5)
sess.run(y)

This version works well:
sess = tf.Session()
x = tf.ones([4, 4])
y = tf.nn.dropout(x, 0.5)
sess.run(y)

Tensorflow version: 1.13.3
OS:  Ubuntu 18.04

I think this API tf.layers.dropout is already deprecated

I think tf.layers.dropout would use keras.layers.Dropout
And finally call this "lambda: array_ops.identity(inputs)" to return the exactly same tensor

It would be more reasonable if it is wrapped to tf.nn.dropout

@ghostplant I tried executing the code on Colab with Tensorflow 1.13.1
import tensorflow as tf
sess = tf.Session()
x = tf.ones([4, 4])
y = tf.layers.dropout(x, 0.5)
sess.run(y)

Is this the expected output
array([[1., 1., 1., 1.],
[1., 1., 1., 1.],
[1., 1., 1., 1.],
[1., 1., 1., 1.]], dtype=float32)
Thanks!

@gadagashwini No, if you use tf.nn.dropout instead, you should get the expected output: somes are zero and others are two.

@ghostplant You are correct. With tf.nn.dropout i am able to get expected result. Thanks!

The following will work:
import tensorflow as tf
sess = tf.Session()
x = tf.ones([4, 4])
y = tf.layers.dropout(x, 0.5, training=True)
sess.run(y)

Note in the doctoring of tf.layers.dropout:
    training: Either a Python boolean, or a TensorFlow boolean scalar tensor
      (e.g. a placeholder). Whether to return the output in training mode
      (apply dropout) or in inference mode (return the input untouched).

@yongtang Thank you. It is a little weird that training is set to False by default, because it is just not what this operator describes to be, so I think it would be more reasonable to change the default value. I think many developers don't even notice this case when they just select to use a dropout operator.


ci: run examples/basic on CI

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[x] Other (please describe): CI

Codecov Report
Patch coverage has no change and project coverage change: +0.32 :tada:

Comparison is base (2948145) 64.70% compared to head (fb7cc02) 65.02%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #729      +/-   ##
==========================================
+ Coverage   64.70%   65.02%   +0.32%
==========================================
  Files         227      227
  Lines       22610    22610
==========================================
+ Hits        14629    14702      +73
+ Misses       7219     7159      -60
+ Partials      762      749      -13

Flag
Coverage Δ

51.98% <ø> (+0.53%)
:arrow_up:

go-1.17.x
64.48% <ø> (+0.04%)
:arrow_up:

go-1.19.x
64.49% <ø> (+0.13%)
:arrow_up:

go-1.20.x
64.35% <ø> (ø)

integration
51.98% <ø> (+0.53%)
:arrow_up:

macOS
41.31% <ø> (+0.02%)
:arrow_up:

ubuntu
41.28% <ø> (-0.02%)
:arrow_down:

unit
41.37% <ø> (+0.01%)
:arrow_up:

windows
41.32% <ø> (+0.03%)
:arrow_up:

ydb-22.5
51.37% <ø> (-0.07%)
:arrow_down:

ydb-23.1
51.83% <ø> (+0.70%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 15 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add Level 3 to LF-Edge lanscape

Add logo and metadata for Level 3

CenturyLink purchased them and I don't see century link on the landscape, I am going to use century link's logo and details

CenturyLink seems more like a Comcast or Verizon vs. Level 3 was CDN

This is certainly one of those interesting ones that spans across several categories. They do have some stand-alone products that could probably be represented across categories. For example, their CDN Edge Compute product could go in the 'CDN & Distributed Caches' category, and the main CenturyLink logo could really be placed across both 'IAAS' and 'Wireline' categories.


Add init file for NationalInstruments

Fixes issue #61
Add empty init.py file for NationalInstruments folder
@WilliamHPNielsen

@mgunyho @Jajiko to solve issue #61 this pr was created and an empty init file was added. Following that some minor mypy issues are coming. Is this something you might want to look into?

I can try to look into it

I can't reproduce the errors in RFSG.py. I kind of understand where they are coming from, but for me mypy doesn't report them as errors (running with mypy --config-file=../../../mypy.ini RFSG.py in the NationalInstruments folder). The other ones I've fixed, I'll test if they really work and publish them then.

@mgunyho please make sure that your locally installed mypy version is same as mentioned in https://github.com/QCoDeS/Qcodes/blob/master/test_requirements.txt file.

I figured it out, I had to run mypy qcodes_contrib_drivers in the root folder. I couldn't test everything today, I'll get back to it next week.

I finally got around to testing this with the hardware, sorry for the delay. I've pushed the latest version to https://github.com/mgunyho/Qcodes_contrib_drivers/commit/23a7e763e390d9f6c8e7377aacf020443ab956fa
I had to override __getattr__ and __setattr__ in NIDLLWrapper to stop mypy from complaining, do you think that's a good idea / does it cause too much confusion?

@mgunyho I think its better to add ignore type comments to silence the issues https://mypy.readthedocs.io/en/stable/common_issues.html#spurious-errors-and-locally-silencing-the-checker

that feels a bit hackish to me, as you would have to add an ignore comment every time you register or access a wrapped method

@mgunyho This is of cause to a certain extend a matter of personal preference but I would not call it hacking but rather honerst.
There is a very good reason why MyPy warns when you dynamically create attributes outside __init__. As far as possible that should always be avoided. You have found a way that tricks mypy into not giving that warning but there is no guarantee that this will be the case for any future version of mypy which may impose stricter checks. Furthermore its hard to understand why this works as the standard library defines the same signature for __setattr__ https://github.com/python/typeshed/blob/master/stdlib/2and3/builtins.pyi#L100
It's therefor hackish in my opinion to rely on overwriting __setattr__ and __getattr__ like this. Having to add an ignore comment for every variable is annying but makes it clear that you are aware of the issues in the design of the code.

Hmm, that is fair enough, and indeed it is confusing why this changes the behavior compared to the standard library stubs.
Do you think setting attributes outside init is fine here (self.wrapper.Function = self.wrapper.wrap_dll_function(...))? I originally had it so that wrap_dll_function would do setattr(self, name, func), but I changed to the current version because it's much more explicit and easier to understand. The previous version had similar issues with mypy complaining about non-existent attributes, both when registering and accessing them.
Nevertheless, I've removed the __get/setattr__ overrides and added type: ignore as of commit https://github.com/mgunyho/Qcodes_contrib_drivers/commit/1320ab2bdae2e2533e1dbaba2b0c081c9a8b802e

I would normally prefer not to define attribues outside init but I think its ok in this case since its relatively clear that this is correct and done on purpose and not due to a typo so lets go ahead with that

@mgunyho are you interested in putting those changes into a pull request ?

My branch (https://github.com/mgunyho/Qcodes_contrib_drivers/commit/7a616d0d11df2643be539546124a3e1466fb98a8) is on top of this one, so @Akshita07 could just pull my changes to this branch, but I can also make a separate PR if you wish


Send error codes

Is it possible to send these error codes in custom policies ourselves? For example if an API we have returns false, is there any way to return a specific error code?

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

ID: fd9c64ff-5065-9a2b-4965-c48685482fe1
Version Independent ID: 3ff9871f-d28d-b752-750e-1142556ec8cb
Content: Error code reference - Azure AD B2C
Content Source: articles/active-directory-b2c/error-codes.md
Service: active-directory
Sub-service: b2c
GitHub Login: @mmacy
Microsoft Alias: marsma

Makes sense, didn't think of that solution!
Thanks! :)


ExcludeFromTopology attribute pollutes contracts project

ExcludeFromTopology  is required if you dont want topics to be created for abstract types and/or interfaces that are not consumed. This is important in Azure for performance reasons. Problem is adding ExcludeFromTopology  populates the contracts assembly with a dependency to MassTransit.Abstractions.
I suggest doing a fluent mapping like FluentValidation or Entity framework. This way you keep your message types agnostic from Mass transit.

Please change "To avoid using the property, the publish topology can be configured along with the bus:"
To "To avoid using the attribute, the publish topology can be configured along with the bus:"
I actually didnt get it in the docs that this was supported


Bump npm version

We've made some feature updates to the master branch including adding the ability to save postal addresses.
We should have someone other than me who added the code do a thorough test and then bump the npm version so people using the library can be notified and start using the feature.

I'm going to close this because there likely won't be a package bump until Version 2.0 is released with full Android support and Promises instead of Callbacks. And then after that we'll keep the npm package as updated as possible.


Add ErrorLink

Something comparable to Apollo's ErrorLink

Similar request https://github.com/zino-app/graphql-flutter/issues/419
I too really like to have this feature to catch Network error and to handle appropriately outside components. I see an approach in this repo https://github.com/ygmpkk/flutter_graphql_backenderrorlink
but, as far as I see, ClientExceptions from http package is not able to capture by this package and may need to implement at core.

@smkhalsa @bsr203 I sent a pull request (#445) to add ErrorLink.

@jayjun thank you so much for your work on it. This was much needed feature for me. I didn't test it, but there has been lot changes around splitting network error etc. In the stable branch  I couldn't handle http error (status code 401 etc) through a custom link. It may all solved now with the changes in beta branch. But please confirm your changes make it possible to catch errors at network level. thanks again. bsr

Now that #445 has been merged, we can close this issue.


Proposal: Separate Primary Replicant loading from the rest of HistoricalManagementDuties

Motivation
Loading primary replicants for Druid Segments is one of the most important things that the Coordinator does. Without a primary replicant available on the cluster, a segment is not available for querying. The Coordinator performs primary replicant loading within a set of Coordinator duties that relate to Historical Management. This grouping can result in the coordinator spending a lot of time doing other things such as loading non-primary replicants, balancing segments, etc. A side effect of this waiting for other Coordinator jobs to complete before more primary replicants can be loaded is that data stays unavailable for longer than it otherwise might have to. This can be a negative end user experience. Breaking primary replicant loading out into its own scheduled runnable group can guarantee that primary replicants are loaded more regularly.
Proposed changes
POC Code Link
I am proposing an optional new DutiesRunnable in the DruidCoordinator. Operators can choose whether or not to break primary replicant loading out into its own DutiesRunnable. If they choose not to enable the dedicated primary replicant loading, their coordinator will function just as it always has. If they choose to enable the dedicated primary replicant loading, their coordinator will add a scheduled DutiesRunnable dedicated to executing matching LoadRule for segments and only doing the primary replicant load for that LoadRule when ran. The HistoricalManagement DutiesRunnable will continue all other HistoricalManagement duties including performing non-primary replicant loading and replicant dropping while executing a matched LoadRule for a segment.
My POC implementation for the proposal exposes two new Coordinator runtime configurations for operators: druid.coordinator.loadPrimaryReplicantSeparately and druid.coordinator.period.primaryReplicantLoaderPeriod. If they choose to enable the first, then a scheduled executor with a configurable backoff period is configured for loading primary replicants.
The new DutiesRunnable would have consist of two duties, UpdateCoordinatorStateAndPrepareCluster and RunRules.

There is an open TODO on analyzing the negative effects of having two DutiesRunnable with UpdateCoordinatorStateAndPrepareCluster. It is possible that only one of the two should execute the full thing and the other should run a scaled down duty.

RunRules and LoadRule will need a mode associated with them. Now we will be executing RunRules in one of two modes. One mode is to only execute LoadRule rules that match. The other is to run all matched Rule. LoadRule is similar, for the primary replicant load, it should run in a mode where it only loads a primary replicant. There also needs to be a mode for skipping primary replicant load. And then lastly, a mode for running all of LoadRule and not worrying about replicant types.
Rationale
I think the biggest benefit here is more control for the operator to ensure that primary replicant loading is running as often as needed. In the case of large clusters who do lots of balancing, and non-primary replicant loading due to servers coming in and out of the cluster, primary replicant loading can get blocked often enough that users are asking about why their new segments aren't becoming available in a timely manner after batch indexing finishes.
As for alternative approaches, I have not thought of any similar ways to achieve this elevated priority for loading primary replicants at this time. I am definitely open to suggestions though.
Operational impact
This section should describe how the proposed changes will impact the operation of existing clusters. It should answer questions such as:

Is anything going to be deprecated or removed by this change? How will we phase out old behavior?

N/A

Is there a migration path that cluster operators need to be aware of?

Enabling this requires coordinator config changes and a restart.

Will there be any effect on the ability to do a rolling upgrade, or to do a rolling downgrade if an operator wants to switch back to a previous version?

rolling upgrade to the first version that includes this would not require any changes because not adding the configs will leave the coordinator as is. An operator can enable after upgrade if they so choose.
Downgrading should not have any impact. The configs, even if specified by operator would be ignored and coordinator would go back to how it operated before there was a dedicated primary replicant loader.

Test plan (optional)
TBD
Future work (optional)
TBD

+1
If this feature allows an admin to set a configuration property on the (dynamic) coordinator config to control primary replicant loading specifically, this could be extremely valuable because it could potentially improve realtime task publishing time (which in turn can prevent pending or even failed tasks and therefore ingest lag, etc) and also prevent segments in limbo that have been published but are not queryable (which may even relate to query failure rates, too).
This is such a critical aspect of the system, and it deserves as much of an interface as non-primary replicants currently have in the coordinator dynamic config.  +1


Update Legacy Tests to V2

Fixes https://github.com/bacalhau-project/expanso-planning/issues/535
This will Break Existing Tests in Create, Validate Test Suites
Which should be deprecated.
The tests have been moved to /cmd/cli/job/run_test.go

as discussed previously, we should keep the tests that are specifically targeting legacy cli. The goal is migrate devstack and scenario tests that testing our system end to end to no longer use the legacy API, and start using the new APIs for job submission and listing. In terms of CLI testing, we already have tests that test the new CLIs.


bump dependencies

Applied mkpr on undefined
/tmp/mkpr.sh

:tada: This PR is included in version 1.15.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Encountered warning [413]: Failed to flush the buffer..error_class=Fluent::Plugin::ElasticsearchOutput::RecoverableRequestFailure error=could not push logs to Elasticsearch

Dear team,
Fluentd pods are showing warning error code [413] frequently
[warn] : [out_es] Failed to flush the buffer. retry_times=1 next_retry_time=2023-04-04 03:39:56 +0000 chunk="5f74fb50c7268c61110c61bdd7f31b7a" error_class=Fluent::Plugin::ElasticsearchOutput::RecoverableRequestFailure error="could not push logs to Elasticsearch cluster ({:host=>''elasticsearch-sample-elastic.apps.example.locadomain", :port=>443, :scheme=>"https", :user=>"elastic", :password=>"obfuscated"}): 413 "
I am using fluentd buffer configuration:

bulk_message_request_threshold 10MB
slow_flush_log_threshold 200s

@type "file"
path  "/var/log/fluentd/buffers/containerlogs"
total_limit_size 5120MB
flush_thread_count 4
flush_interval 10s
overflow_action drop_oldest_chunk

Dear team,
Please let us know how this issue can be fixed. we are stuck on this issue.

Dear team,
Please reply on this issue, as this error is occurring frequently.

[warn] : [out_es] Failed to flush the buffer. retry_times=1 next_retry_time=2023-04-04 03:39:56 +0000 chunk="5f74fb50c7268c61110c61bdd7f31b7a" error_class=Fluent::Plugin::ElasticsearchOutput::RecoverableRequestFailure error="could not push logs to Elasticsearch cluster ({:host=>''elasticsearch-sample-elastic.apps.example.locadomain", :port=>443, :scheme=>"https", :user=>"elastic", :password=>"obfuscated"}): 413 "

The trailing error code 413 means Payload Too Large.
Probably you send too large data due to too high input rate.
How about limiting the data size of one request by chunk_limit_size?
https://docs.fluentd.org/configuration/buffer-section#buffering-parameters
BTW I believe it's not Fluentd's bug, it's usage issue. so I close this issue.
If you have any question about usage of Fluentd, please post your question to other community:
https://github.com/fluent/fluentd#more-information


Release 2020.09.2 builds with old version number 2020.09.1

Configuration:

RDKit Version: 2020.09.2

Description:
Far from critical and mainly FYI, but I think the RDKit Release_2020.09.2 is still configured with revision number "1"
https://github.com/rdkit/rdkit/blob/Release_2020_09_2/CMakeLists.txt#L124

damn. I forgot to change that. Thanks for noticing.
Any thoughts on how/if to fix that?
The other thing I could do is just plan to release 2020.09.3 sooner and make sure it's fixed there.

I also can't think of any different solution than just waiting for the next patch revision. The only limitation with the 2020.09.2 release is that the version number returned by the code may be not sufficient to identify it, but distribution packages are usually versioned based on the git tag, and in the worst (but hopefully sufficiently unlikely) case, one could probably test some feature that changed after the 2020.09.1 release.

Closing this because we know about the problem and it's been fixed for the 2020.09.3 release.

Closing this because we know about the problem and it's been fixed for the 2020.09.3 release.


Bugfix. I think this was rare and happened only on cache hit.

Traceback (most recent call last):
...
File "/home/vmagent/app/main.py", line 40, in synth_fortune
return redirect(url_for(serve_fortune, path=digest))
File "/usr/local/lib/python2.7/dist-packages/flask/helpers.py", line 268, in url_for
if endpoint[:1] == '.':
TypeError: 'function' object has no attribute 'getitem'

Simple fix.


Add doc functionality to print subcommands list

Notes for Reviewers

This PR fixes #12933

Signed commits

[x] Yes, I signed my commits.

I think that the Kanvas Snapshot Service is working now, so I'm re-running the workflows.

@alphaX86 can you resync your branch


Verify choice page: Radio buttons should be headers

We are still investigating the best layout for this page. Firmstep are to provide a technical option to follow the service pattern.


Install wechat-web-devtools error

brew cask install wechat-web-devtools
==> Downloading http://dldir1.qq.com/WechatWebDev/mina/20160923/wechat_web_devtools_0.9.092300.dmg
Already downloaded: /Users/apple/Library/Caches/Homebrew/Cask/wechat-web-devtools--0.9.092300,20160923.dmg
==> Verifying checksum for Cask wechat-web-devtools
Error: It seems the App source is not there: '/usr/local/Caskroom/wechat-web-devtools/0.9.092300,20160923/微信web开发者工具.app'

You must always follow the reporting bugs guide. When you opened this issue, the template in place urged you to do so and gave you the relevant links.
The template also stated clearly that

if it is apparent you ignored the instructions for reporting issues, your issue may be closed without review.

That seems very much to be the case, here, which is why this was closed.
Again, as the template states (emphasis added)

When the guide isn‘t followed we get the same issues over and over. Having to repeatedly deal with the same solved and documented problems leads to maintainer burnout and a lot of wasted hours that could instead have been spent improving Homebrew-Cask itself and fixing real bugs.

I’ll add it is exhausting, and when maintainers are exhausted, everyone loses.
A lot of work was put into those guides precisely so we can keep things running smoothly.
I ask that you respect our time and efforts and follow the guides.


Firestore: Add a test and readme about the android global refs crash

Add a test and release notes entry for a fix to an intermittent crash in Firestore on Android when large documents and/or a large number of documents with large arrays or maps were used. See https://github.com/firebase/firebase-unity-sdk/issues/569 and https://github.com/firebase/firebase-cpp-sdk/pull/1364 for details.

Integration tests: https://github.com/firebase/firebase-unity-sdk/actions/runs/5459341301


Some small question about OpenCV

why you implement OpenCV I do not get it? I just feel like it will slow everything. если вдруг разговариваешь на русском можешь ответить не на английском?

I don't think OpenCV will slow down the program much. Here is the profiling result on a benchmark.

In some cases, this library uses OpenCV for some frame post-processing (like rotation and color conversion). The implementation in OpenCV is already fast (with the existence of plenty optimization e.g. SIMD).
The main reason using OpenCV here is: in practice you're not just only grabbing a frame, but also processing that image, and probably you will use OpenCV to do that (since it may be the most popular C++ image processing library). So why don't we just return frames in the OpenCV format?


Performance improvement might not be genuine due to warm up issues

In the examples, the first run could be slow due to cuda warmup issues.

Also we should specify the expected improvement in each readme.


Support for Oracle Linux?

Oracle Linux has SCL support. It would be great to have this container for building stuff on OL. Any chance you could make that a feature?

@hhorak @notroj ?

A similar PR is in https://github.com/sclorg/s2i-base-container/pull/111 -- we discussed it already before, that maintaining more copies of Dockerfiles is not easy and we should rather limit the copies we take care of to minimum. Even worse state would be to not update the Dockerfile.
However, since all the derivatives (https://upload.wikimedia.org/wikipedia/commons/a/a3/Redhat_family_tree_11-06.png) would be almost the same as the RHEL one, wouldn't it be enough to change the Dockerfile on the fly during build (FROM field and repo name)?

It should be the same, but our base images are different to the RHEL ones and we don't require any subscription management, so just changing the repo names isn't quite the same.

@jgsuess @Djelibeybi Hi! Could I ask what do you see as the advantages of basing the images on Oracle Linux instead of CentOS?

It allows integrated testing with the UEK, which can behave
 differently from stock kernel, without leaving the container.
Just for disclosure: I work for Oracle Labs, but this is private
interest. I like OL as a platform.
Best, JG
On Thu, 2018-03-15 at 10:54 +0000, torsava wrote:

@jgsuess @Djelibeybi Hi! Could I ask what do you see as the
advantages of basing the images on Oracle Linux instead of CentOS?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@jgsuess Since these requests for more bases are multiplying (centos6, OL, Alpine, ...), we've discussed this issue with the other maintainers and we sadly don't think it's feasible for us to maintain so many variants.
However, if we could help your usecases within the centos based image, please let us know.


Factor out pipelines or Switch to Highland >3

Pipeline performance is very slow in Highland < 3
see https://github.com/caolan/highland/issues/270

Done in https://github.com/koopjs/GeoXForm/commit/32d8c42dad382ef59c6536f72223c75c662e7cfc


Version Control & Hello World

Problem
There are a bunch of apps designed for RWW / solid; but they're not often working with the newer servers and/or to the newer specs.  When new comers are interested in testing out how to get a server working, how to build an app - or how to fix an old one so it works with the newer standards, these constituents of 'issues' appear to make it harder than is ideal for on-boarding new eco-system participants, or improving the means of support by existing ones.
Considerations:

AUTH apps are bound to specified servers (rather than decoupled)
Most Apps expect to use WebID-TLS & alot of documentation also speaks of WebID-TLS as the auth method. I suspect most core developers are using WebID-TLS.
RWW.io is now non-functional.

IDEA:  AUTH method: http://webcivics.org/dev/index.html highlights the means to decouple the TLS used to authenticate against, the account / persona label; and the WebID-OIDC password.  The 2nd factor was intended to be the WebID-TLS Certificate: in which, the earlier concept of http://mediaprophet.org/ux_KB/page4115294.html#0 related to the means in which to make distinct semantics based upon an interoperable framework of users wanting to use a matrix of WebID-[auth] methods to authenticate themselves and the use of devices (from TVs to FitBits to SmartPhones, Shared Personal Computers, Tablets, etc.) with their private and personal data; interoperable with a socially-aware web application / platform framework.
Whether a user decides they want to use WebID-TLS and have no WebID-OIDC used in relation to their data is imho, the users decision, that should / could be both flexible and able to be changed based on the data-owners context of their solid-pod usage environment / situation.
In a linked yet seperate area;  I've found it hard to find the resource that shows how to build a 'hello world app' from scratch, using WebID-OIDC and one of the currently functioning public servers.

Is there a 'hello-world' resources for new app developers as to provide a basic guide (and example) of how to build an APP using modern formats.

Is there a guides on how to make use of existing apps (that use older methods)

How is version control managed? Updating an app that works on an old server (ie; gold or the php code-base) shouldn't remove the means for those apps to work with those old servers, unless something the server depends upon is no-longer functional or has critical security risks that results in an upgrade script being the preferred option (or some other solution).

Related knowledge:

What is an RDF Ontology?
How to make one, (and how to make 'sameAs' references with one).
is there a registry of Ontologies used by Solid?  (ie: look-up a function) (ie: perhaps by way of resource similar to http://lod-cloud.net/ ?)

Solid App - Branding
branding framework could help solve framework issues such as how to define Recommendations about 'privacy preserving' development of solid Apps; and how to distinguish between the characteristics of different apps.
Perhaps making something like tweetFi, to ontologically define a series of trust vectors / framework qualities - for an app?
Some apps may never see user-data.  Some apps might seek to make use of aggregated data for good open-data purposes - some might seek to exploit personal data.
Having some sort of framework to bind the app developer to their claims, should help users...?  This might also be attached to the same mechanism used, to manage the version control issue...
ie: new version of app, new permissions - perhaps people just choose not to upgrade...

Hi @mediaprophet
Thank you for your input, let me know if there are any concrete actions you suggest to take and how to go about it.
Mitzi

Owing to behaviours, I left your solid community sometime ago and am
considering how to best help alternatives, such as globalCoin powered
solutions.  Where publishing work freely, good ideas get taken up, and I
don't need to put up with poor moral grammar.
Let's ensure all outstanding matters are closed. I want nothing more to do
with you.
I've closed out my w3c account but have Been advised their provenance
policy is different to the one demonstrated here, so,  I'm unable to
distort history in any better way as may best suit your needs.
On Wed., 19 Jun. 2019, 7:27 pm Mitzi László<EMAIL_ADDRESS>wrote:

Hi @mediaprophet https://github.com/mediaprophet
Thank you for your input, let me know if there are any concrete actions
you suggest to take and how to go about it.
Mitzi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/solid/solid-apps/issues/13?email_source=notifications&email_token=AIKBW2KOCWMCO2ZLARPYGKLP3H3X3A5CNFSM4FKCHGNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYBIRSY#issuecomment-503482571,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIKBW2MMEH4U4OO7O6SR2WLP3H3X3ANCNFSM4FKCHGNA
.


merge latest ui code to dev

merge latest ui code to dev @2017/03/27

Coverage remained the same at 54.452% when pulling 88783af85100b228806d48525be495c269448daa on fix/merge_latest_ui_code_to_dev into 3ce9188e1d1b6dea842e8d3471bc557403aad0c2 on dev.


Fix keylog mode not working correctly on certain OpenSSL versions

Fixes #533
The root cause of the problem was that the offset of the client_random member within the ssl3_state_st structure varies across different OpenSSL versions.
Although the offsets for the ssl3_state_st->client_random member (SSL3_STATE_ST_CLIENT_RANDOM) were already generated for all supported OpenSSL versions, but they were not being utilized correctly.

To solve this issue, the existing SSL3_STATE_ST_CLIENT_RANDOM offsets have been integrated into the code, ensuring that ecapture can accurately retrieve the client_random value from the correct location within the ssl3_state_st structure, regardless of the OpenSSL version being used.

isn't the ssl3_state_st structure of the 1.1.0 series like this?

Yes, it's not just a minor difference between 1.1.0 and 1.1.1. The ssl3_state_st structure in the 1.0.2 series is completely different from the 1.1.0 and 1.1.1 series.