the toolbar icons are hidden by another icon

see bellow:

on the screenshot there are only two icons affected but it affects all the icons in the toolbar (if selected in settings).
PS: thanks for this wonderful plamoid (efficient and discreet....). it deserves a coffee ;) . I don't know if themes downloaded via store.kde.org can be updated like widgets via a metadata.json file?!! if it is the case (confirmation), I will submit the idea to the 2 theme creators that I use so that they can think about this improvement
regards

This issue was fixed in version 2.8.1.

I don't know if themes downloaded via store.kde.org can be updated like widgets via a metadata.json file?!!

Although this won't differ much from updating the widgets and only requires small changes in the code, I don't like my current implementation; it needs improvements or a completely different approach.
Additionally, content creators often don't properly format their packages, which means they can't simply be installed via kpackagetool. For example, they might just upload an archive with a theme that needs to be copied manually.
Therefore, I don't plan to add anything other than widgets for now.

I also think that since the management of themes is not the same as that of widgets, the thing would not be possible.
concerning the issue, apdatifier was updated yesterday

but the plasmoid remains at version 2.8:

Remove the widget and install it again. I discovered a bug today: if you upgrade it through Apdatifier, version 2.8 is downloaded instead of 2.8.1 (yes, it will display as 2.8.1).

Remove the widget and install it again did the trick.
I observed 2 small issues:
A) the instances of the widget do not seem to be synchronized
B) an update announced by apdatifier and carried out via the terminal (or other) does not modify the state of the widget. you have to synchronize each instance individually
regards

You mean more than one running widget? But why would you need more than one?

You mean more than one running widget?
yes

But why would you need more than one?

i dont need more widget, but i have two screens : the first one has two pannel (each of them with one miniature box) and the second one with one pannel (miniature box)
apdatifier as widget appears in each pannel.

i dont need more widget

If you don't need more than one widget, you can simply disable it in the system tray settings

Ok, now it’s clear.

A)

I have an idea on how to implement this, but I can't promise anything yet.

B)

I plan to do this, but probably not anytime soon.

no problem, In any case, the widget is very successful.
the 2 points raised (A & B) will be improvements in visual consistency


Changes when using webpck watch mode do not regenerate the HTML file

I am having an issue where when running webpack in watch mode changes to the source that gets inlined does not trigger a rebuild of the html file.
Environment and package version

Webpack 5.27.2, HTML webpack plugin 5.3.1 , HTML inline script plugin 2.0.0
Reproduction link / code sample

Here is my webpack config which hopefully gives you an idea of the setup.
const path = require('path')
const CopyPlugin = require("copy-webpack-plugin");
const HtmlWebpackPlugin = require('html-webpack-plugin')
const HtmlInlineScriptPlugin = require('html-inline-script-webpack-plugin');

module.exports = (env, argv) => ({
  mode: argv.mode === 'production' ? 'production' : 'development'
  entry: {
    ui: './src/ui/ui.tsx',
  },
  module: {
    rules: [
      { test: /\.tsx?$/, use: 'ts-loader', exclude: /node_modules/ },
      { test: /\.css$/, use: [{ loader: 'style-loader' }, { loader: 'css-loader' }] },
      {
        test: /\.(png|jpg|gif|webp|svg|zip)$/,
        type: "asset/inline"
      },
    ],
  },
  resolve: { extensions: ['.tsx', '.ts', '.jsx', '.js'] },
  output: {
    filename: '[name].js',
    path: path.resolve(__dirname, 'dist'),
  },
  plugins: [
    new CopyPlugin({
      patterns: [
        { from: "src/manifest.json", },
      ],
    }),
    new HtmlWebpackPlugin({
      template: './src/ui/ui.html',
      filename: 'ui.html',
      chunks: ['ui'],
    }),
    new HtmlInlineScriptPlugin([/ui.js/]),
  ],
})

Steps to reproduce

Run webpack --watch
Make a change to ui.tsx

Webpack logs show that ui.tsx is regenerated but ui.html is not emitted. However if I change the HTML file itself ui.html does get emitted.
What is expected?

I would expect that the HTML file is regenerated when the code that is being inlined is changed.
What is actually happening?

Webpack does not regenerate the HTML file and no changes are actually written.
Let me know if you need any more info, thanks!

Hi @zlangbert, thank you for the detailed explanation of your issue. After investigating a bit, the issue seems to be laying in the html-webpack-plugin.
When looking at the source code of html-webpack-plugin, we can see on line 255 of this file if else logic to check whether the assets will be regenerated:
// Code from https://github.com/jantimon/html-webpack-plugin/blob/0a6568d587a82d88fd3a0617234ca98d26a1e0a6/index.js#L255-L263
if (isCompilationCached && options.cache && assetJson === newAssetJson) {
  previousEmittedAssets.forEach(({ name, html }) => {
    compilation.emitAsset(name, new webpack.sources.RawSource(html, false));
  });
  return callback();
} else {
  previousEmittedAssets = [];
  assetJson = newAssetJson;
}

While the default setting of isCompilationCached is true, assetJson and newAssetJson seems to have the same output equals to "['ui.js']", so the new assets isn't generated.

To solve the issue, I have 2 recommendations here:

Turn off caching by adding cache: false to HtmlWebpackPlugin, this will affect the performance of the webpack build

new HtmlWebpackPlugin({
  template: path.resolve(__dirname, '../src/ui/ui.html'),
  filename: 'ui.html',
  chunks: ['ui'],
  cache: false, // Turn off caching
})

Include the hash or chunkhash in the output filename

output: {
  filename: '[name].[hash].js', // or '[name].[chunkhash:8].js',
  // ...other output settings
},
plugins: [
  // ... other plugins here
  new HtmlWebpackPlugin({
    template: path.resolve(__dirname, '../src/ui/ui.html'),
    filename: 'ui.html',
    chunks: ['ui'],
  }),
  new HtmlInlineScriptPlugin([/ui.[a-zA-Z0-9]+.js/]),
]

Let me know if the above solutions solve your issue or not 😃

Hey @icelam, thank you so much for looking in to it and the detailed response.
Either of those options fix the issue for me, I will likely go with #2. Thank you!

@zlangbert You're welcome. Glad to hear that it solves the issue!


Weights min stake

This PR adds a check into the signed extension for pallet subtensor which blocks calls to set weights when the caller has less stake than predefined WeightsMinStake value.

Don't forget to update spec version


TypeError: Cannot read property 'binary' of undefined

https://sentry.io/matt-godbolt/compiler-explorer/issues/354099220/
TypeError: Cannot read property 'binary' of undefined
  at None (compiler.js:61)
  at Function._.each._.forEach (ext/underscore/underscore.js:153)
  at patchOldFilters (compiler.js:60)
  at new Compiler (compiler.js:77)
  at Hub.compilerFactory (hub.js:132)
...
(21 additional frame(s) were not displayed)

Whoops!


Fix jslint error.

Just like it says on the tin!

Duplicate of #305?

Whoops! Should've searched first. Thanks @PlasmaPower! :)


circular loadin indicator fixed #76

fixes #76
wrapped CircularProgressIndicator with Center() widget

@himanshugoyal77 good work, it is working.
@andoriyaprashant you should merge it.


Searching for newline characters in regex mode doesn't find any results

VSCode Version: 1.1.1
OS Version: Windows 7 Professional x64

Steps to Reproduce:

Create a document with multiple lines
Search for \n, \r or \r\n in regex mode.

What happens: When I try to search a multi-line text for \n, \r or \r\n in regex mode it doesn't find any results. However when I try to search for the same thing in Atom or Sublime, it finds results.
Atom

Sublime Text 3

VS Code

Duplicate of https://github.com/Microsoft/vscode/issues/313, be sure to :+1: it to help prioritize.


FromAsync Tasks For Only the End Method Example needs HELP!

the section "FromAsync Tasks For Only the End Method" talks about more than 3, ref and out parameters but the example has NONE of these and no declaration.  This example is basically worthless.

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

ID: a7a2d4f3-d369-9945-79d1-31efea2f06cc
Version Independent ID: 3004dcc5-a1d4-ba57-102d-46d955548085
Content: TPL and Traditional .NET Framework Asynchronous Programming
Content Source: docs/standard/parallel-programming/tpl-and-traditional-async-programming.md
Product: dotnet
GitHub Login: @rpetrusha
Microsoft Alias: ronpet

For starters, define the structure of the DoSomethingAsynchronously method.  Expanding upon this structure with an actual example when calling Task.Factory.FromAsync() including handling the callback and state parameters using a APM methods (i.e. have Begin/End)

an example with a ref and/or out parameter
public string DoSomethingAsynchronously(ref int TimesExecuted) { }
public IAsyncResult BeginDoSomethingAsynchronously(ref int TimesExecuted, AsyncCallback callback, Object state) { }
public string EndBeingDoSomethingAsychronously(ref int TimesExecuted, IAsyncResult asyncResult);

and

an example using more than 3 parameters
public string DoSomethingAsynchronously(int repeatTimes, DateTime waitDuration, bool ignoreOdds, string filePathToLogOutput) {}
public IAsyncResult BeginDoSomethingAsynchronously(int repeatTimes, DateTime waitDuration, bool ignoreOdds, string filePathToLogOutput, AsyncCallback callback, Object state) {}
public string EndDoSomethingAsynchronously(IAsynchResult asyncResult) {}


Replace the copyright statements in the license headers of ORT with a generic statement

Replace the explicit mentioning of copyright holders in the license headers of ORT with the generic statement "Copyright 201x-2020 The OSS Review Toolkit contributors". Check with LF if there are legal issues with that and if we need approval from every single copyright holder.

@tsteenbe is waiting for a meeting with Mike Dolan (general manager and lawyer from LF) to clarify details.

Guidance provided by LF:  "If all the contributors agree, you can start using "Copyright the OSS Review Toolkit contributors", as long as the contributors are listed in a file in the project."
Propose we do the following:

Draft a proposal to request the main copyright holder e.g. ORT TSC would like to simplify copyright holder statement in all its source code files. Our proposal is update the copyright for each file to "Copyright 201x-202x The OSS Review Toolkit contributors" and move you copyright to a file name X in the root of the code repository...
All ORT TSC members to vote on the text
@tsteenbe  and @tsteenbe  propose the change to their respective companies
Update CONTRIBUTING.md to mention the copyright holder that should but used. Possibly add a CI check.

@sschuberth  @mnonnenmacher  @fviernau To you agree to the above? Or have an alternative proposal?

Guidance provided by LF:  "If all the contributors agree, you can start using "Copyright the OSS Review Toolkit contributors", as long as the contributors are listed in a file in the project."
Propose we do the following:

Draft a proposal to request the main copyright holder e.g. ORT TSC would like to simplify copyright holder statement in all its source code files. Our proposal is update the copyright for each file to "Copyright 201x-202x The OSS Review Toolkit contributors" and move you copyright to a file name X in the root of the code repository...
All ORT TSC members to vote on the text
@tsteenbe  and @tsteenbe  propose the change to their respective companies
Update CONTRIBUTING.md to mention the copyright holder that should but used. Possibly add a CI check.

@sschuberth  @mnonnenmacher  @fviernau To you agree to the above? Or have an alternative proposal?

Maybe we should look into adopting AUTHORS Certificate e.g. Authors file in the root of the repo. Found it via https://writing.kemitchell.com/2016/05/13/License-from-Who.html

Maybe we should look into adopting AUTHORS Certificate e.g. Authors file in the root of the repo. Found it via https://writing.kemitchell.com/2016/05/13/License-from-Who.html

Doesn't our DCO check already cover the intent of the AUTHORS Certificate? At least the wordings of the first paragraphs sound very similar. IMO we just need to make it easier to discover who the actual authors / contributors are. Besides GitHub showing this, we could leverage something like the all-contributors GitHub action.

Doesn't our DCO check already cover the intent of the AUTHORS Certificate? At least the wordings of the first paragraphs sound very similar. IMO we just need to make it easier to discover who the actual authors / contributors are. Besides GitHub showing this, we could leverage something like the all-contributors GitHub action.

Besides GitHub showing this, we could leverage something like the all-contributors GitHub action.

More action for potential use:

https://github.com/wow-actions/update-authors (AUTHORS file)
https://github.com/minicli/action-contributors (CONTRIBUTORS file)
https://github.com/BobAnkh/add-contributors ("Contributors" section)
https://github.com/test-room-7/action-update-file (generic updating of files)

I like how PURL project did its copyrights see https://github.com/package-url/purl-spec/blob/master/mit.LICENSE#L1 but would make some change. I propose 'Copyright (c) the ORT authors' to each code file and then add a NOTICE with copyright attribution to the root of the code repository so we align with ORT's Apache-2.0 license lines 106-121.
Open discussions points for me:

What should be the contents of NOTICE file?
Propose to use  authors in the various copyright statements e.g. HERE Europe B.V, Bosch.io etc. so it a straightforward migration and then in a second step look how to automate generation of the NOTICE file.
How do we organize each authors to give its permission for this changes in writting?

Following the https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code#what-if-there-are-many-authors-or-copyright-is-held-by-a-legal-entity I propose the following change to ORT code base

Move all existing copyright statements found https://github.com/oss-review-toolkit/ort into a new NOTICE file in the root of https://github.com/oss-review-toolkit/ort
The NOTICE file will look something like the below. Note we should de-duplicate years similar to ORT's own logic.

The ORT Project

Copyright (C) 2017-2022 HERE Europe B.V.
Copyright (C) 2019-2020 Bosch Software Innovations GmbH
Copyright (C) 2020-2022 Bosch.IO GmbH
...

Add new copyright statement to each code file Copyright (c) YearA - YearB The ORT Project Authors (See NOTICE file in project root). Alternatively, we could also do Copyright (c) YearA - YearB The ORT Project Authors <https://github.com/oss-review-toolkit/ort/tree/NOTICE> but the link would in this case always point to the NOTICE of the latest dev version of ORT which may not be desirable.
Update the CONTRIBUTING.md to tell contributor to always add "Copyright (c) YearA - YearB The ORT Project Authors ..." and guidance on when their contribution is significant enough thtat the need to update the NOTICE.
Add a GitHub action to check each source code file in a pull request has the correct Copyright (c) YearA - YearB The ORT Project Authors ...

Note in the above proposal we do not ask contributors to sign over the copyright to a single entity therefore I do not see the need to ask each contributor to give his/her permission only the ORT TSC has to agree on this change.

Point 5. should already be covered by detekt checks that run in CI. However, we probably could auto-update the NOTICE file via a GitHub action (see above).

@sschuberth  As per Matija not every contributor is an author so we have to be careful on auto-updating the NOTICE file.

Discussed in TSC meeting of June 20, 2022. TSC is OK to go ahead with change @MarcelBochtler to run ORT over ORT to create the initial NOTICE file.

In the TSC meeting of July 4th, 2022 ORT TSC decided to use Copyright (C) YearA The ORT Project Authors (See NOTICE file in project root)


futa page

There are a lot of things I regret in life, spending an hour making this is one of them.

are you not gonna link to it on the main page or something?

oh yeah I forgot hold on

thanks


Error with table size not being divisible by text size

Hi, I'm getting an error because size of the suffix table is not divisible by length of the text.
https://github.com/google-research/deduplicate-text-datasets/blob/8a172b0d815862b1131da203be24d430e121a725/src/main.rs#L479
I'm running bash scripts/deduplicate_single_file.sh test.txt test_dedup.txt 20 1 where test.txt just contains a few paragraphs from a random Wikipedia article and some duplicate text that I manually added. I'm doing this mainly for debugging purpose (I would like to later make some edits to keep the first occurrence of duplicate samples and throw away the rest). If I run the command on my actual dataset that is roughly ~70GB big, I'm not encountering such issue. So I'm wondering what the issue is? Does the code not work with datasets that are too small?
Thanks!
Update: I just found out that running the command on the actual 70GB dataset also raised the same error.

Huh. Thanks for reporting this. I'm not sure what's going on right now but I'll look into it later this week.
To help me debug, could you upload (assuming it's safe to do so, but because you're saying it's wikipedia data I suspect it is) the exact file you're using in case that makes a difference?

I also have an unrelated question: Can this program handle UTF-8 text (e.g. Korean)?

Second, we don't want UTF8 strings. Everything is a [u8] byte array, because we might be working over token sequences which aren't valid UTF8.

I wasn't sure what this meant in the README.md. If we were to pass a file with utf-8 strings as input, does this mean we are essentially ignoring the utf-8 encoding and treat each byte individually for substring match?

Yeah, you're right in how it handles things: it doesn't understand the idea of a "letter" or "token" or anything -- it just thinks in terms of "bytes".

Okay this is very weird. I can't reproduce the error you see: when I run the commands everything comes out as expected.
Could you re-run the command and upload the following files:
test.txt.part.0-10490
test.txt.part.0-10490.table.bin
test.txt.table.bin

I think I figured out what the issue was. When I cleared the tmp folder and ran the command again, the error went away. My guess is that b/c the tmp folder never got cleared, I was merging tables from previous runs too. Maybe we shouldn't have this line commented out? https://github.com/google-research/deduplicate-text-datasets/blob/8a172b0d815862b1131da203be24d430e121a725/scripts/make_suffix_array.py#L90

Ah -- perfect yes thanks. I will do that.


TX calibration

using Revise
includet("software/scripts/checkIQimbalance.jl")
sample_rate = 5u"MHz"
tbb_iq, tbb_tx = do_txrx(:tbb_loopback; skip_sanity_check = true, sample_rate) # Run at least twice after every change
tbb_iq, tbb_tx = do_txrx(:tbb_loopback; skip_sanity_check = true, sample_rate)
make_txrx_plots(tbb_iq, tbb_tx; name="tbb_loopback", sample_rate)

cc @sjkelly


[PE-D][Tester D] Possible to add appointment dates before the current date

In the app, it is possible to add an appointment date which is supposedly invalid, like a date that has passed.
Currently, it is 3rd nov, but it is possible to schedule 2nd feb. This might result in incorrect dates input accidentally by financial advisors.

Perhaps, the same error message shown when there is an invalid time input, e.g 29:00, can be shown to the user for a possibly invalid date.

Labels: type.FeatureFlaw severity.Low
original: glenngnng/ped#7

the current behavior is not strictly 'incorrect' but 'can be better'. Will indicate as a planned enhancement.


Where is the ES6/ES2015 Version of this sdk?

Where is the ES6/ES2015 Version of this sdk?

The sample app should work with ES5 or ES6 with no modifications. If you encounter any specific bugs related to ES6, please feel free to file an issue here on github.


Add build script to react-native-babel-transformer

Summary:
When metro-react-native-babel-transformer was part of Metro, Metro would take care of building flow-typed src before publishing. React Native doesn't do that.
This diff adds build script, prepare and postpublish hooks to react-native-babel-transformer. The script is effectively is a copy-paste from react-native-codegen, we'll deduplicate them in the future.
Changelog: [Internal] - Add build script to react-native-babel-transformer
Differential Revision: D47006627

Closing as abandoned internally


Vickel: Watch 9jaleaks.ng

Vickel requests the watch of the watch_keyword 9jaleaks\.ng. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

9jaleaks\.ng has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Allow providing separate host/port parameters for Redis scaler

Use-Case
The config for the Redis Lists scaler requires the following format for the host/port:
address: REDIS_HOST # Required host:port format

In our deployments we have separate env vars for hosts and ports, so would like to have an alternative to provide this information in separate parameters, similarly to how it is allowed for PostgreSQL and MySQL scalers.
Specification

[ ] Keep address param working as is
[ ] Add host and port parameters (look at implementation of MySQL/PostgreSQL as example)
[ ] Add config check and log an error if both address and host/port provided

@inuyasha82 is working on a prototype of this, we would like to know if you folks agree with adding this and any suggestion welcome. Thanks!

That's a good point actually - I'm not sure if I'd bite the bullet and remove address or stick with both scenarios.
Thoughts by others?

@tomkerkhove
i think one problem is that scalers are not really standardized, so every scaler has a different behaviour.
i.e some like the redis scaler supporot only one format, usually host:port with different naming (redis has address, others have host, etc).
some like postgresql scaler have support for both format, host, port, and host:port but in this case is called "connection".
maybe some scalers doesn't support the host:port format.

@zroubalik What do you think about this? Should we take this standardization into account for 2.0?

I think we should, but I currently don't know all details about all scalers to make an informed decision. Therefore I don't know whether standardization is a good approach or not -> Do all scalers have similar needs/fields/paramteres to follow standardized format (given the nature of the scalers source, ie. queue/event/...)? Do we want to bring some partial mandatory format? Won't it bring unnecessary mess? We might need an analysis across all scalers, what parameters they are using and which way to see whether there is possibility to create some standard format.

From looking at a number of the scalers which have proper docs linked at https://keda.sh/ I found one at least does not need this type of information: https://keda.sh/scalers/gcp-pub-sub/ but many others do and they are far from consistent. Most seem to only accept a single param that should contain host:port info, and the name of the parameter varies a lot, some examples: serverAddress, natsServerMonitoringEndpoint, connection, address

I think it would make it simpler to learn how to work with different queues if this was a bit more standard.

What I'm reading is that:

We should not enforce mandatory fields
Create a list of commonly used parameters and assign a default name

Example - Connection strings use a variety of names, but we should standardize on connectionString or connection

We need to do the same for addresses in format of host:port, but provide alternative names for just host & port as well.
In case of 3, both approaches are ok and we should standardize on which approach (full or seperate) to favorite over the other

Can everybody agree with that? If so, I'll create a dedicated issue for that.
In terms of #694 itself, totally agree that we should add it but prefer address indeed

@tomkerkhove  yeah, i agree with your conclusions, as per 1 when you talk about mandatory fields, are u referring to some fields that should be commond in all scalers?
Cause  think that every scaler needs some mandatory fields in order to establish the connection, but of course every queue needs different mandatory fields.

Yeah i think it could be a good idea, makes things easier

yeah definetely!

Hi everyone, just to let u know that i created PR #710 to implement this request.

Thanks @inuyasha82!
See #712 for standardization!

I think we can close this


Video: Expose video driver functions

Sometimes you want a dummy driver, sometimes you want the offscreen driver, and sometimes on Linux you actually want to make a decision between X11 and Wayland.
This requires exposure of a couple of video driver functions which are unfortunately quite stringy. This exposes those functions and attempts to make them less stringy.

Hi, thanks for working to improve the library. I'll be taking a look at these additions later, I have some other stuff that I'm working on at the moment. But the changes look pretty solid.


$DATE reading

We now have access to a file in which the $DATE keyword is stored as 2016-Mar-03, which is different from the assumed format %d-%b-%Y. Therefore, loading the file with FCSData fails.

Note that %Y-%b-%d is not the standard format specified in the FCS standard, so in principle we wouldn't need to cover it. However, I think it is a failure of FCSData to crash in response to a nonstandard field. If the data field cannot be read, it should be set to None.

agree

a1d44e03024eaa32b036170eeaa1b7314d3ae979 handles the new date format, and returns None if the date cannot be parsed. It also fixes a different bug with the CREATOR keyword found when loading the same file.


Homer work

Finished topics 6-10, also linked my markdown pages in the readme

Resolved merge conflict (I linked my markdown pages to the readme)


fix: let aws take care of validation

Hi!
I like that module but I had trouble using it. I removed some ties to let AWS handle the validation.
regards

Thanks so much for your contribution!  We ended up having to take a broader approach with this (declaring the variable as a list(any) and providing usage examples) to achieve the desired outcome (completely omitting the NoDevice parameter is cleaner than trying to null it, for example.) This fix is available in 0.3.1 via https://github.com/rhythmictech/terraform-aws-imagebuilder-recipe/commit/a8fb6e25a0e80158cfb63f4cf97a8c276b1287bf.  I'm going to close this PR out as it is now redundant -- I needed to resolve this somewhat quickly as it was tied to a customer deliverable, so I just knocked it out myself.


FIX: Housekeeping - broken links, missing section, update ET conversion

A number of small issues are addressed, ensuring all links are correctly targeting other documents, removed the outdated BIDS conversion of the ET with bidsphysio, relinked lost section edf-to-bids.md.

I will make a speedy merge since we want to work on these changes as soon as possible.


Derequire

Hello
When trying rdom in ramda repl I noticed that I was getting an error when browserify was evaluating the already browserified dist/rdom.js.
Error: Cannot find module './tags'

I suspect this is because of the presence of a require call here
The issue can be recreated by running the following code in requirebin
var rdom = require('rdom');
var h1 = rdom.h1({}, ['hello']);
document.body.appendChild(h1);

The pull request adds a derequire step into the building of this library, which is intended to modify the references to require so a downstream browserify will not attempt to re-require them.
Great library BTW! Very straightforward.

"---FLAGRANT SYSTEM ERROR---"
well that's not very nice. Thanks for the fix

:dromedary_camel:

i'll release  a new package on npm tonight

🐙

https://www.npmjs.com/package/rdom
0.6.0


Complete API reference documentation for C#

Complete inline document comments in the C# library so we can publish the API reference on the Learn site.

@matthewbolanos - is this done or are you actively working on this? If not I'll move to backlog.


OpenMetrics integration does not support special target_info metric

Steps to reproduce the issue:
Configure an openmetrics check against a target that exports target metadata using the target_info convention
# TYPE target info
# HELP target Target metadata
target_info{env="prod",hostname="myhost",datacenter="sdc",region="europe",owner="frontend"} 1

Describe the results you expected:
I expected the tags within target_info to be attached on every other metric reported by this check and queryable in Datadog.
Describe the results you received:
I only see the tags local to each metric present and queryable in Datadog.
I see a separate target_info metric in Datadog with the target-scoped tags.
Additional context
One reason this feature is important as the OpenTelemetry specification mandates use of the target_info convention to report resource-scoped tags.

In SDK Prometheus (pull) exporters, resource attributes SHOULD be converted to a single target_info metric; otherwise, they MUST be dropped, and MUST NOT be attached as labels to other metric families. The target_info metric MUST be an info-typed metric whose labels MUST include the resource attributes, and MUST NOT include any other labels. There MUST be at most one target_info metric exposed on an SDK Prometheus endpoint.

@sirianni Hello! Thanks for opening up this issue. I'll create a card internally to properly triage this feature. Can I also ask that you kindly create a support ticket as well to help us better keep track of it? Thanks in advance!


Global Error response customization

Hi,
Is there a way to add some global customizations, such as adding a timestamp or tracing, to all error responses?
Best regards

See https://wimdeblauwe.github.io/error-handling-spring-boot-starter/current/#global-customization-of-the-response-json

Hi,
my mistake, I forgot add number 3.4.1. I cannot update to java 17.

If you need support for older versions, please contact me through my company.


Emphasizing that this is for preview

The tools don't say that it requires a preview version of VS, nor does the error in the installer.
It's mentioned in one line at the top. I've found other people who have run into the same issue when installing it, so hopefully this prevents others from having the same problem.

@DaveVoyles,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@DaveVoyles : Thanks for your contribution to the Azure documentation! The author, @rachelappel, has been notified to review your proposed change.

@DaveVoyles : Thanks for your contribution to the Azure documentation! The author, @rachelappel, has been notified to review your proposed change.

@DaveVoyles : Thanks for your contribution to the Azure documentation! The author, @rachelappel, has been notified to review your proposed change.

@DaveVoyles : Thanks for your contribution to the Azure documentation! The author, @rachelappel, has been notified to review your proposed change.

@DaveVoyles : Thanks for your contribution to the Azure documentation! The author, @rachelappel, has been notified to review your proposed change.

@DaveVoyles : Thanks for your contribution to the Azure documentation! The author, @rachelappel, has been notified to review your proposed change.

@DaveVoyles  Thanks for the contribution.
@ggailey777 Could you review?

@DaveVoyles Thank you for your contribution. While I do like your suggestion, I think that we can implement it a little bit better with a note at the top. I will take your feedback and implement a change which is a little bit more visible for the customer so they don't run into this same issue again. Thanks again for the suggestion! #please-close


Error on generating new ABP React template

I tried generating a new template and using the ABP backend which has support for this template, but it seems I'm having an error during the build up phase. What can the issue be?
@my-project/ui:dev: src/Permission/PermissionActions.tsx(1,44): error TS2307: Cannot find module '@my-project/hooks' or its corresponding type declarations.

Hello, I’m getting the same error. How did you solve it?


No dialog text bugfix

Address issue #28
Also include german translation fixes and adds russian language.

This PR should be split into multiple ones, each addressing specific changes/fixes (one for dialog fix, one for strings updates, one for build.gradle updates etc.).


Document - The ability to run DocumentController server side

Edit Delta Docs In Dart Server
You can edit delta docs on the server side using DocumentController. This can come in handy for a couple of scenarios:

SEO - You can get retrieve the plain text of a delta doc and then render it as a plain old html document using whatever server side technology you desire.
Elastic Search - If you need to write a search feature for a large number of documents, once again, you will need the plain text server side. Again running the visual editor on the server side is super handy.
Coop Editing - In case you want to implement a master server to compare the edits of multiple users, again you can run doc edits on the dart server itself.

Importing Visual Editor Server
By importing the server side library we ensure that no dart:ui dependencies are imported. Note that both the frontend and server versions of the library use the same code. They are just different export files.
import 'package:shelf/shelf.dart' as shelf;
import 'package:shelf/shelf_io.dart' as shelf_io;
import 'package:visual_editor/visual-editor-server.dart';

//...
// Convert delta text to plain text
final document = DeltaDocM.fromJson(jsonDecode(deltaText));
final plainText = DocumentController(document, null, null).toPlainText();

Took some effort, but now, thanks to the cleaned up code, it's completely possible to run DocumentController on the server side. Here's a snapshot from insomnia demonstrating a simple endpoint for converting delta docs to plain text.


Home Page: Add Mascot Image

As a developer, I want to:

[ ] Add NSC mascot image above the upcoming event on the right side

Hey @intisarosman1, I have already got this resolved.


Update from 0.3.4 to 0.3.5 fails

Hi,
I just tried to update to your latest release as we also faced the issue it fixes. Unfortunately the DB update/migration fails somehow and craft does an automatic rollback.
Not sure what I can provide you to help. Maybe a DB dump.
Cheers,
Pascal.

Are you able to get in contact through Slack? We can get things sorted through there.

Thanks for raising this issue, which we resolved over Slack. For future users, please read 0.3.4-0.3.5 notes


Implement Uint256SquareRoot

resolves issue #131

Please include benchmark tests for them as well. There is a dedicated file

@mmk-1 please fix conflicts so we can merge


PX4 mode bug

@mrpollo after this PR has merged, could you bump the pymavlink version to re-enable support for PX4?
https://github.com/ArduPilot/pymavlink/pull/42
/cc @LorenzMeier

Sure thing, just ping me when it gets merged

@mrpollo ping

hey @sanderux pymavlink needs a new release, it looks like it hasn't been released since 2.0.8 (thats the latest i could find on pypi), we need them to create a release and push that to pypi before I can make a new release

@mrpollo @peterbarker at my request tridge was kind enough to release pymavlink 2.2.0 on pypi. could you bump the version requirement in dronekit-python?

On Thu, 20 Apr 2017, Sander Smeets wrote:

@mrpollo @peterbarker at my request tridge was kind enough to release
pymavlink 2.2.0 on pypi. could you bump the version requirement in
dronekit-python?

I've changed it from a strict 2.0.6 requirement to >= 2.0.6.
I suspect PX4 Flight Core requires >= 2.2.2, 'though?

It does

Seems to be solved, thanks guys


Automate hub deploys when merging to master

Fixes #43

Fixed AZ service principal issue
CircleCI config
Move helm-hub-values from keybase repo to public config dir
Simple azure-cli-helm Dockerfile

Signed-off-by: Scott Rigby<EMAIL_ADDRESS>

@mattfarina I fixed the service principal thing finally, after fussing with it over the weekend. Also set up the job in circleci, except didn't add a value to SERVICE_PRINCIPAL_PASS yet, until at least another set of eyes are on this PR. Until then, the job will just fail.
What to do with the Dockerfile is another fun question - keeping all in one place for now. If this seems like a good place to stay (I think it could be, unless we think we'll re-use it) then we could hook it up to automatically build on dockerhub. I haven't set that up yet but could if we want once merged. Or we could move the file to another git repo somewhere. For now pushed to my docker hub user.

I'd love to use existing images as opposed to an all-in-one, so sketched that up in a separate branch here. Would like to get some feedback though before playing with that more. Maybe we can start with one image and iterate?

I think I've addressed all the concerns so far. Anyone interested to see this test out? I'll wait to add the SERVICE_PRINCIPAL_PASS ENV var to the CircleCI project until we're ready for that.

Following up from https://github.com/helm/hub/pull/70#issuecomment-487421324 I just added SERVICE_PRINCIPAL_PASS to circle.


Tidy up documentation

I've reorganised the documentation in the project. Overview of the larger changes:

The Smartdown README has moved to ./doc/.
The Ruby Smart Answer README has moved to ./doc/.
I've moved some things from the main README to the type-specific README where appropriate.
I've split each main section out of the main README and saved the content in a new file in ./doc/.
The main README is basically now just a table of contents linking to other documents.

NOTE. This is mostly reorganisation. I've not added or removed very much content at all.
This PR addresses a number of the items in the checklist of https://trello.com/c/TVYM7kGW/49-update-documentation-to-reflect-the-current-state-of-the-repo. Hopefully it gives us a good foundation on which to make some of the larger changes.

Haven't looked into this in detail, but very nice!
Would this be a good opportunity to use the styleguide template for the main README.md?
https://github.com/alphagov/styleguides/blob/master/use-of-READMEs.md

Would this be a good opportunity to use the styleguide template for the main README.md?

I've intentionally avoided making that change in this PR, although I think it can/should come soon after this is merged.

Other than my (all minor) comments looks good to me. :+1:


Avoid circular dependencies and option to build explicit types

Codecov Report

Merging #39 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #39   +/-   ##
=======================================
  Coverage   90.84%   90.84%
=======================================
  Files          52       52
  Lines         765      765
  Branches      119      119
=======================================
  Hits          695      695
  Misses         70       70

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 4db9c89...02f4e68. Read the comment docs.


feat: Rework weights and rounding to make tests stable

This fixes some unstable tests

This isn't an issue with the constraint weights. It seems to be an issue with rounding.
Sometimes it does this:
[src/layout/layout.rs:806] i = 1
[src/layout/layout.rs:807] changes.get(&element.start) = Some(
    37.5,
)
[src/layout/layout.rs:808] changes.get(&element.end) = Some(
    62.5,
)
[src/layout/layout.rs:810] size = 25

and other times it does this:
[src/layout/layout.rs:806] i = 1
[src/layout/layout.rs:807] changes.get(&element.start) = Some(
    37.49999999999999,
)
[src/layout/layout.rs:808] changes.get(&element.end) = Some(
    62.5,
)
[src/layout/layout.rs:810] size = 26

I think is this is a better way to round values:
            let start = (start * 100.0).round() as u16 / 100;
            let end = (end * 100.0).round() as u16 / 100;

I changed it to use the double precision rounding method. This commit has all the tests that I had to change to make it pass: https://github.com/ratatui-org/ratatui/pull/888/commits/1996db2ed2734a067b42476b71c14c9d61fa1c83
All of the changes are one off differences.
To make it more clear what users would experience, I added some tests for Flex::Start and Flex::SpaceBetween in this commit: https://github.com/ratatui-org/ratatui/pull/888/commits/94bce308c3dc05bdcd215cf578dae27cbc7108cd

I think this might be a better way to round values:

            let start = (start * 100.0).round() as u16 / 100;

            let end = (end * 100.0).round() as u16 / 100;

That sounds like it would work
There's a recent blog post I saw about servo where they ran into similar issues and switched to fixed point instead of floating point to address it. I think this effectively does the same thing, but I wonder if there would be any difference in the calculations doing the multiply on everything as the first step, and rounding to ints then dividing at the end. (Merely curiosity here)
https://servo.org/blog/2024/01/26/two-months-in-servo/

I just tried this and I think this is better?
            let start = ((start * 100.0).round() / 100.0).round() as u16;
            let end = ((end * 100.0).round() / 100.0).round() as u16;

37.4999 becomes 3749.99 gets rounded to 3750 and then that becomes 37.5 and rounded to 38.

Do you mean multiplying all user input by 100.0 before running the solver and then dividing by a 100.0 at the end?

I did it "properly" in this commit:
https://github.com/ratatui-org/ratatui/pull/888/commits/9e7c8624af81695b203b9ff16be433ea4dabc4e1
Which ends up causes some panics:
failures:

---- layout::layout::tests::split::min_max::case_4_min_max_priority stdout ----
thread 'layout::layout::tests::split::min_max::case_4_min_max_priority' panicked at src/layout/layout.rs:888:49:
attempt to multiply with overflow

---- layout::layout::tests::split::min_max::case_3_min_max_priority stdout ----
thread 'layout::layout::tests::split::min_max::case_3_min_max_priority' panicked at src/layout/layout.rs:888:49:
attempt to multiply with overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

There's two ways to do it

Round once

let start = (start * 100.0).round() as u16 / 100;
let end = (end * 100.0).round() as u16 / 100;

Round twice

let start = ((start * 100.0).round() / 100.0).round() as u16;
let end = ((end * 100.0).round() / 100.0).round() as u16;

The "round twice" makes the tests behave as they used to, but the "round once" works the same way was the scaling up the input and scaling down the output, which makes me think the "round once" approach is better?
The most recent commit has the scaling approach with the panics resolved by scaling after converting to f64.

I have reverted to this behavior:
let start = ((start * 100.0).round() / 100.0).round() as u16;
let end = ((end * 100.0).round() / 100.0).round() as u16;

i.e. the round twice approach in this comment: https://github.com/ratatui-org/ratatui/pull/888#issuecomment-1915870132


ACME Client Can not init api at renew

os-acme-client version: 3.2
After updating to the latest package I cant renew my certificates.
The following errors appeared:
2021-10-03T14:30:32 | acme.sh[66511] | ] Can not init api, for https://acme-v02.api.letsencrypt.org/directory
-- | -- | --
2021-10-03T14:30:22 | acme.sh[17358] | ] Sleep 10 and retry.
2021-10-03T14:30:22 | acme.sh[18517] | ] Can not init api for: https://acme-v02.api.letsencrypt.org/directory.
2021-10-03T14:30:21 | acme.sh[46222] | ] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 60
2021-10-03T14:30:00 | acme.sh[19136] | ] Sleep 10 and retry.
2021-10-03T14:30:00 | acme.sh[51173] | ] Can not init api for: https://acme-v02.api.letsencrypt.org/directory.
2021-10-03T14:29:58 | acme.sh[87136] | ] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 60
2021-10-03T14:29:37 | acme.sh[44096] | ] Sleep 10 and retry.
2021-10-03T14:29:37 | acme.sh[968] | ] Can not init api for: https://acme-v02.api.letsencrypt.org/directory.
2021-10-03T14:29:36 | acme.sh[58235] | ] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 60
2021-10-03T14:29:14 | acme.sh[83586] | ] Sleep 10 and retry.
2021-10-03T14:29:14 | acme.sh[45562] | ] Can not init api for: https://acme-v02.api.letsencrypt.org/directory.
2021-10-03T14:29:13 | acme.sh[29871] | ] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 60
2021-10-03T14:28:52 | acme.sh[49815] | ] Sleep 10 and retry.

Can anyone help me?

Hi!

Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 60

curl cannot verify letsencrypt.org cert. you can try @mimugmail method from https://forum.opnsense.org/index.php?topic=24950.msg119700#msg119700
(I think that applications that used LE certificate will lose the link to it, so it will be necessary to re-specify the certificate after renewal)
and it will not eliminate subsequent problems connecting to resources using the long-chain LE certs. the solution is not yet ready as far as I can see but you can search forum for possible workarounds


Feature none binarization

Hello,
I propose to add an option to disable the binarization which could be helpful in some cases.
The added code assumes that the image uses a correct width of PRINT_WIDTH = 384.
If you have any remarks on this pull request I am happy to incorporate them.

This pull request might solve issue #42.

Thanks @danielfomin96!


Background listens to wrong ReactFlow

Describe the Bug
If there are two ReactFlows, the Background of the second seems to listen to the first Flow, even though they are wrapped in ReactFlowProviders.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Have two ReactFlows, each wrapped with a ReactFlowProvider and a Background child
Zoom

Expected behavior
The background of the second flow should be separated from actions on the first one.
Screenshots or Videos
The top and bottom graphs are two separate ReactFlows . The bottom flow has nodesDraggable set to false.
https://user-images.githubusercontent.com/17252710/211806892-f418715a-3835-400d-b356-60c90d6fa472.mp4
Platform
all
Additional context
No response

Hey, if you have multiple flows on one page, you need to pass a unique id prop to each component to make React Flow work properly.


Unexpectedly found nil while implicitly unwrapping an Optional value

I’m encountering an error as shown in the picture. From what I can tell, this error seems to appear after the camera permission approval message, which leads me to believe it’s a camera-related issue. However, I’m unable to resolve this with my current abilities. Could you please assist me?
( I'm using MacBook Pro M2 and X Code 15.2 version...)

Change var screenRect: CGRect! = nil // For view dimensions to var screenRect = UIScreen.main.bounds // For view dimensions in ViewController. Helped in my case.


PWD on windows gives bad path

The PWD is possibly giving an undesirable path.  Seems like the user should see "/" as his root
Also running in Windows seems to give issues with pathing due to backslash versus slash.
Or, the problem is process.cwd() returning "C:\path\to\somewhere" and not using unix style "C:/path/to/somewhere"
C: PWD
S: 257 "\C:\path\to\user" is current directory

Hi,
Fixed this by changing
path = pathModule.join(pathModule.sep, cwd, path);
by
path = pathModule.join(cwd, path);
in function withCwd(cwd, path)
and by changing
glob.glob(pathModule.join(self.root, dir), self.fs, function(err, files)
by
glob.glob(dir, self.fs, function(err, files)
in FtpConnection.prototype._LIST
So far PWD and LIST are working fine on Linux & Windows

Thanks. Any chance you could turn this into a pull request?


FrozenError: can't modify frozen String

It seems that you are trying to modify the arguments I'm sending you:
FrozenError: can't modify frozen String
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder/xpath.rb:234:in `slice!'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder/xpath.rb:234:in `equal_pair'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder/xpath.rb:53:in `predicate_expression'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder/xpath.rb:43:in `process_attribute'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder/xpath.rb:113:in `block in class_string'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder/xpath.rb:113:in `map'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder/xpath.rb:113:in `class_string'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder/xpath.rb:27:in `build'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder.rb:150:in `build_wd_selector'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/locators/element/selector_builder.rb:34:in `build'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/element_collection.rb:41:in `build'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/element_collection.rb:16:in `initialize'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/elements/html_elements.rb:1159:in `new'
            /Users/yegor/.rvm/gems/ruby-2.6.0/gems/watir-6.16.5/lib/watir/elements/html_elements.rb:1159:in `divs'

See how rude it is! :)
I'm doing exactly this:
browser.divs(class: ['a', '!b'])

@yegor256 , do you know if the problem is specific to Ruby 2.6? We have tests running for Ruby 2.3 to 2.5 and I think we have a test for this.

I am having the same issue on ruby 2.6.3

Now I switched to ruby 2.5.3 and the problem persists

This is fixed in newer Selenium versions.


Feature Request: Capability to fix the seed for all keras kernel initializers

System information

TensorFlow version (you are using): 2.0-beta
Are you willing to contribute it (Yes/No): No

Describe the feature and the current behavior/state.
If you create a Keras model, the only way to make your model reproducible is to repeat setting the seed for the kernel_initializer in every layer. This makes the code bulky and more prone to error. For example, a reproducible code looks like this:
np.random.seed(1)
tf.set_random_seed(1)
# FEATURE REQUEST for another parameter like the ones above that we can set
# here and avoid repeating initializer seed in each and every layer below

model = tf.keras.Sequential()
model.add(tf.keras.layers.Dense(8, activation='relu', kernel_initializer=keras.initializers.glorot_uniform(seed=1), input_shape=[1]))
model.add(tf.keras.layers.Dense(8, activation='relu', kernel_initializer=keras.initializers.glorot_uniform(seed=1)))
model.add(tf.keras.layers.Dense(1, activation='linear', kernel_initializer=keras.initializers.glorot_uniform(seed=1)))

I wonder if you can add a default seed parameter that we can set and it affects all the initializers.
Will this change the current api? How?
No
Who will benefit with this feature?
Anyone who likes clean code and would like to create reproducible models.

@mhaghighat Sorry for the late response.
Look like you are looking for the following feature.
https://www.tensorflow.org/api_docs/python/tf/config/experimental/enable_op_determinism
If you think the above is not the feature you are looking, please feel free to open a PR in  keras-team/keras repo. repository.
Please note that Keras development moved to keras-team/keras repository to focus on only keras. Thanks!


commands break

All the commands work fine, but when I do !arturdebil, it just bans one person then it breaks, none of the other commands work.

I tested it on a server with 2 people

@potatoplayzzz are intents enabled?

yea I followed all your instructions

I think the problem is that one person is the owner, so they can't be banned


Expandable Row and Column Resize don't play nice together, can't get ColDef for ExpandableColumn

I was using both Expandable Row and the Column Resizing feature and it seems they don't play nice out of the box.  So i decided to keep the expandable buttons column non resizable. First it would be great to be able to provide your own coldef for the expandable row, but given that,I wanted to set {enableResize:false} on the coldef for the expandable row.If you try to get the vanilla coldef by using grid.getColumnDef('expandableButtons'), you get a null back even though grid.getColumn('expandableButtons') will indeed return the proper column. The reason after looking at the source code is that getColumnDef() looks through grid.options.columnDefs and of course expandableGrid being a plugin, that columndef is added after the fact. I am looking for a good workaround to it and will post it when I do

I think I fixed this earlier today/yesterday, when I tidied up the colDef for expandable - I made it both non-exportable, but also non-resizeable.  Could you check and confirm?

Assuming this is resolved, given no comment for 3 weeks.  Closed.


[Test] Need mechanism to thoroughly test module imports

Recently we released a module whose setup.py file was missing some necessary entries in it's packages list, resulting in a non-functioning build. The CI did not catch this because it only ensures that the wheel file builds and that az runs. This approach is insufficient because it is not guaranteed to trigger the relevant imports.
When we run a module's tests, we run the dev_setup.py script which doesn't rely on the packages list.
We need to ensure that our CI system will, as best as it can, detect packaging errors like this. Possible solutions:

include additional metadata in setup.py that runs certain commands after wheel installation to ensure that no import errors are thrown. This should be fairly easy to implement but the downside is that not every command which could be chosen is guaranteed to trigger the imports.
Run the tests using a wheel installation instead of a dev setup.  Since the tests aren't included in the packages, this could be tricky, but would be the most thorough option.

cc/ @troydai and @derekbekoe for thoughts on technical feasibility.

The live test today is doing this. And we can reorg our Travis CI automation logic to a formal: build -> install -> test flow.

It's good that the live tests will catch this, but then we need to have a policy to ensure that we examine a live test run after the last merge and prior to release to avoid this happening again in the future, which is pitfall rife for human error (mostly, forgetting).
If we could reconfigure the CI to do a "regular install" and then run the tests that would be ideal since the automation would catch this much faster.

@tjprescott we should do that. And it can probably save us more time by building package only once.


Use multiple sender id for multiple apps using brozot

I have multiple mobile apps (for each app I manage different server key and sender id) and I am using same laravel backend to send notifications to all different mobile apps.
How can I send notification to different app using different sender id (not using single sender id) with laravel brozot package?

I'm facing a similar situation. Is there a way we can override the FCM::send server and sender keys?

I am also facing the same issue. I have two apps one for service providers and other for customers and it has to be the same Laravel backend/application.

Please sort this out and push an update. We will also need the steps to add multiple server keys and sender IDs. Thank You.

Hi everybody
My proposition is to use the pull request of henrique1977 (#52) But I would like to change it a bit to not modifying the config array.
Do you think that this implementation could be good for this issue ?
If yes I will integrate the pull request
Best Regards

What happened with this? Did henrique1977's fix this got integrated? It seems good for me.

I'm using this version of the codebase and it works like a charm
https://github.com/brozot/Laravel-FCM/pull/52

@solancer 👍 . Can you please update the document or links how you achieved with multiple senders(projects).

you can add condition according to your app
if(app=='1'){
//if you want to send notification to first app
config(['fcm.http.server_key' => 'your first app  server key']);
config(['fcm.http.sender_id' => 'your first app sender id']);
}else{
//if you want to send notification to second app
config(['fcm.http.server_key' => 'your second app  server key']);
config(['fcm.http.sender_id' => 'your second app sender id']);
}

@

you can add condition according to your app
if(app=='1'){
//if you want to send notification to first app
config(['fcm.http.server_key' => 'your first app server key']);
config(['fcm.http.sender_id' => 'your first app sender id']);
}else{
//if you want to send notification to second app
config(['fcm.http.server_key' => 'your second app server key']);
config(['fcm.http.sender_id' => 'your second app sender id']);
}

It works like a charm! thx

you can add condition according to your app
if(app=='1'){
//if you want to send notification to first app
config(['fcm.http.server_key' => 'your first app server key']);
config(['fcm.http.sender_id' => 'your first app sender id']);
}else{
//if you want to send notification to second app
config(['fcm.http.server_key' => 'your second app server key']);
config(['fcm.http.sender_id' => 'your second app sender id']);
}

Hi everyone @luolongfei @brozot   I'm facing this issue....So this is the solution? but where I should put that condition?

any news on this?

you can add condition according to your app
if(app=='1'){
//if you want to send notification to first app
config(['fcm.http.server_key' => 'your first app server key']);
config(['fcm.http.sender_id' => 'your first app sender id']);
}else{
//if you want to send notification to second app
config(['fcm.http.server_key' => 'your second app server key']);
config(['fcm.http.sender_id' => 'your second app sender id']);
}
hi everone, i'm facing the issue but  Where i should put this code in my laravel project?

@FutureFutureTo
I've created one repository for each app and just put this two lines above in php before de FCM::sendTo of each repository:
config(['fcm.http.server_key' => env('FCM_SERVER_KEY')]);
config(['fcm.http.sender_id' => env('FCM_SENDER_ID')]);

hey thanks for getting back to me on this...i actually just ended up using the firebase php sdk and rolling my own solution


Handle cyclical requires

By either ignoring them as an invalid solution, or returning an appropriate error when there is no valid solution

We should allow modelling of cyclical graphs. It's a real situation that becomes an adoption hurdle when it happens. In particular, codebases that are messy shouldn't be forced to completely get their acts together before adopting CPS or any tools that require well formed CPS in the distant future.
It's probably OK to make support for cycles an explicitly opt-in feature though.

I looked at what pkgconf did again, I thought that it was aborting on cycles, but it breaks the cycle. I think it would be worth doing what pkgconf does. But we need to do anything other than what we do now, which is recurse until the stack overflows

It's a leetcode not-a-big-deal problem to walk a cyclical graph, so I'm sure we can manage. Someone write this up like it's leetcode, mark it help-wanted, and I'm sure someone will pick it up in due time.
I don't know if we need it for an MVP, to be clear.


Simple component test (clicking a checkbox) fails after creating new project with @vue/cli v5

Version
5.0.4
Reproduction link
github.com
Environment info
System:
    OS: macOS 12.3.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
  Binaries:
    Node: 16.14.0 - ~/.nodenv/shims/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 8.3.1 - ~/.nodenv/shims/npm
  Browsers:
    Chrome: 101.0.4951.64
    Edge: Not Found
    Firefox: 100.0
    Safari: 15.4
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.1.1
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  5.0.4
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  5.0.4
    @vue/cli-plugin-babel: ~5.0.0 => 5.0.4
    @vue/cli-plugin-router:  5.0.4
    @vue/cli-plugin-unit-jest: ~5.0.0 => 5.0.4
    @vue/cli-plugin-vuex:  5.0.4
    @vue/cli-service: ~5.0.0 => 5.0.4
    @vue/cli-shared-utils:  5.0.4
    @vue/component-compiler-utils:  3.3.0
    @vue/test-utils: ^1.1.3 => 1.3.0
    @vue/vue2-jest: ^27.0.0-alpha.2 => 27.0.0
    @vue/web-component-wrapper:  1.3.0
    jest-serializer-vue:  2.0.2
    vue: ^2.6.14 => 2.6.14
    vue-hot-reload-api:  2.3.4
    vue-loader:  17.0.0 (15.9.8)
    vue-style-loader:  4.1.3
    vue-template-compiler: ^2.6.14 => 2.6.14
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: 5.0.4

Steps to reproduce
Repository has identical projects generated with vue/cli v4 and v5.

Install dependencies for both projects using npm ci.
Within v4-test, run 'npm run test:unit'. Observe that the test passes.
Within v5-test, run 'npm run test:unit'. Observe that the same test fails.

What is expected?
The test clicks on a checkbox and should fire the @change event to update the component data.
What is actually happening?
No event is fired

Ran into this issue on an existing Vue 2 project while attempting to upgrade to vue/cli 5.
I'm guessing this isn't related to vue/cli itself but to some interaction between many of the jest-related libraries which use different major versions when generated with the different vue/cli versions. Let me know if one of those projects would be better suited to handle this bug.
Thanks!

Pretty certain this will be being caused by jsdom no longer triggering change/input events for radio/checkbox elements if they're not attached to the DOM. The change was introduced in v16.5.2.
You'll either have to use the setChecked method in Vue Test Utiles, or attach the element being tested to the DOM using the attachTo mount option.


[TIR] Support tensorization using ldmatrix + MMA

MMA and ldmatrix intrinsics were respectively added in https://github.com/apache/tvm/pull/9909 and https://github.com/apache/tvm/pull/10855, this PR enables using them together in a TIR schedule. I think this is a very cool example of using transform_layout + tensorize together to target very low-level instructions.
Writing many variants of intrinsic descriptions and their tensorized implemenations (different shape, data type, transposed or not etc) was very tedious, but still it was reasonably manageable thanks to recent improvements in TVMScript meta programming - see https://github.com/apache/tvm/pull/11097 and https://github.com/apache/tvm/pull/11324 and how they are exploited in tir/tensor_intrin/cuda.py.
Of all the possible variants of MMA + ldmatrix combinations, only 6 of them are supported for now:

ldmatrix always loads 4 8x8 matrices
Only support 16x8x16 shape (float16) and 16x8x32 shape (int8) for MMA. These shapes are only supported by Ampere, so sm75 (T4) or sm70 (V100) are not supported. Missing variants (16x8x8 or 8x8x4) can be easily added later if desired.
Since I always load 4 matrices for each of A and B, I issue two MMA calls to fully utilize the loaded matrices and compute 16x16 output tiles (one MMA call consumes only 2 8x8 matrices from B). Operating on 16x16 tiles also makes it easier to port existing schedules using WMMA intrinsics to use MMA + ldmatrix instead.

The test case test_tir_schedule_tensorize_ldmatrix_mma.py exercises all 6 supported variants. If we set measure_perf = True, it reports GFLOPS on 4k inputs. The following is an example output running on RTX 3070. In particular, I also have an equivalent schedule for the f16f16f32 case using WMMA intrinsic (~38 TFLOPS), MMA + ldmatrix one below is faster (~40 TFLOPS).
(trans means the matrix B is transposed, e.g. our dense op)
f16f16f32_m16n16k16: 40086.985791 GFLOPS
f16f16f32_m16n16k16_trans: 39576.507331 GFLOPS
f16f16f16_m16n16k16: 64315.448428 GFLOPS
f16f16f16_m16n16k16_trans: 61917.847391 GFLOPS
i8i8i32_m16n16k32: 91906.635057 GOPS
i8i8i32_m16n16k32_trans: 96388.844717 GOPS

@vinx13 @junrushao1994 @shingjan @Hzfengsy @yzh119 @KnowingNothing

This is super amazing work!!!!!!

The results look amazing, thank you @masahi !


Acrostiche:0.3.1

I am submitting

[ ] a new package
[x] an update for a package

Description: Merged a contribution from @caemor to fix an error when an array of one description was provided without a trailing comma.

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

This PR seems to want to merge all commits I have for this package again. I am not sure this is the expected behaviour (I am still trying to figure out Github's forks). Let me know if I need to change something.

Because I squash-merged your first PR, the commits from your fork aren't present in this repository. When starting on a new PR, ideally you would first sync up your fork with the upstream (this) repository. The easiest way to do this is to keep pull requests on separate branches of your repository instead of main and update main before starting a new feature branch. The diff looks okay though, so it shouldn't matter for this PR.


Bug while running chromite-uatg-tests

While running "uatg from-config -c config.ini -v debug" with the latest commits in uatg and chromite-uatg-tests, I got this error
Traceback (most recent call last):
File "/home/sneha/.local/bin/uatg", line 11, in
load_entry_point('uatg', 'console_scripts', 'uatg')()
File "/usr/lib/python3/dist-packages/click/core.py", line 764, in call
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/home/sneha/uatg/uatg/main.py", line 236, in from_config
generate_tests(work_dir=config['uatg']['work_dir'],
File "/home/sneha/uatg/uatg/test_generator.py", line 110, in generate_tests
asm_body = plugin.plugin_object.generate_asm()
File "/home/sneha/myquickstart/chromite_uatg_tests/modules/decoder/uatg_decoder_arithmetic_insts.py", line 39, in generate_asm
for inst in arithmetic_instructions['add-sub-reg']:
KeyError: 'add-sub-reg'

Solved the issue in chromite_uatg_tests repository in the dev-branch. Checkout the dev branch to resolve this issue immediately. The issue can be closed once dev is merged with main or by the next feature release.


Karma run on Windows7-x64 and GET NUMBER_MAX_VALUE error.

Two days ago,i try to install karma and run it . but karma not work. after update node and npm and karma to LTS, karma still not work. so I report a ISSUE:
https://github.com/karma-runner/karma/issues/2329
but karma member ignore and close it by no answer.
So i learn node-debug try to find out the reason. I debug karma line by line in pass two days,finally i found WHY. Here is
Expected behaviour
As ISSUE#2329 say, I want karma work. but karma does't.
Actual behaviour
karma does't work and no error log and no message output.
Environment Details

Karma version 1.2.0 NODE、NPM AND GULP all @LTS
Core-js version 2.4.1
Test code, gulpfile.js

var gulp = require('gulp');
var KarmaServer = require('karma').Server;

gulp.task('test',function(){
    new KarmaServer({
       configFile: 'karma.conf.js',
       singleRun: true
    }, done).start();
});

karma.conf.js is not necessary, because program run to line 2 and exception raised.
Steps to reproduce the behaviour

gulp test.
exception raised.

By node-debug , run node-debug ./node_modules/gulp/bin/gulp.js test get to CHROME BROWSER to debug program.
Below is js stack of This ISSUE:
karma/bin/karma
->karma/lib/cli.js#5
-> karma/lib/server.js#20
-> karma/lib/file-list.js#10
-> core-js/index.js#1
-> core-js/shim.js#36
-> core-js/modules/es6.math.acosh.js#9
here is es6.math.acosh.js code
// <IP_ADDRESS> Math.acosh(x)
var $export = require('./_export')
  , log1p   = require('./_math-log1p')
  , sqrt    = Math.sqrt
  , $acosh  = Math.acosh;

$export($export.S + $export.F * !($acosh
  // V8 bug: https://code.google.com/p/v8/issues/detail?id=3509
   && Math.floor($acosh(Number.MAX_VALUE)) == 710
  // Tor Browser bug: Math.acosh(Infinity) -> NaN
  && $acosh(Infinity) == Infinity
), 'Math', {
  acosh: function acosh(x){
    return (x = +x) < 1 ? NaN : x > 94906265.62425156
      ? Math.log(x) + Math.LN2
      : log1p(x - 1 + sqrt(x - 1) * sqrt(x + 1));
  }
});

Please see LINE 9, breakpoint at line 7 and i type Number.MAX_VALUE in Chrome console, debug program error and suddenly exit.
I try to comment line 9 and run gulp, gulp and karma work !
But i try another js file like this :
test.js
  console.log(Number.MAX_VALUE);

and run node test.js, output 1.7976931348623157e+308,didn't get error.
Ok,manager, Any idea ?

This does not sound like a karma bug. This repository is for issues with karma itself - see https://github.com/karma-runner/karma/blob/master/CONTRIBUTING.md
Closing this as a support issue.


something wrong with "grid. svox2.SparseGrid()" in "opt.py"

Thanks for your work.
When I ran the command "python opt.py  -t <log_dir> <data_dir>/0000 -c configs/meetroom_init.json --scale 1.0", I got a problem.
"Morton code requires a cube grid of power-of-2 size, ignoring...
Segmentation fault (core dumped)"
It looks like there is something wrong with "grid. svox2.SparseGrid()" in "opt.py".
Do you have any idea about this error?

Try the latest svox2 ?


Pass values from some field to a grid

Pass the values of some field to be displayed in the grid.

I need to pass values from several fields from an entity x to the entity grid Y through a MasterDetailRelation as shown in the image above

Check this example:
https://github.com/volkanceylan/Serene/blob/master/Serene/Serene.Web/Modules/BasicSamples/Dialogs/DefaultValuesInNewDialog/DefaultValuesInNewGrid.ts
               dlg.loadEntityAndOpenDialog(<Northwind.OrderRow>{
                    CustomerID: 'GOURL',
                    EmployeeID: lauraCallahanID,
                    DetailList: [{
                        ProductID: chai.ProductID,
                        ProductName: chai.ProductName,
                        UnitPrice: chai.UnitPrice,
                        Quantity: 5,
                        LineTotal: chai.UnitPrice * 5

}]


CUDA available check

In the application and the examples, check for CUDA available and if not print a warning and exit

Trying to run a single fit as Adrian did in 589cac5bd5686f0ab040a4d9ad58bac800e6a40f is not the right way. A fail in gpufit in principle requires cleaning up which we do not do yet. Much better is a dedicated alternative (function in the interface) that tells you whether CUDA is available and nothing else. I will do it.
Also, it needs to be done for every example and withing the bindings...

In 7e872ae5a2492826413b70d7177e1ae9b7be2df8 I changed the application so that it now tries to run gpufit normally and if this fails, print the error message and skips the gpufit computation henceforth but continues with cpufit alone.
On Lars computer he actually had a CUDA installed, but an older version (7.5 instead of 8.0) so the application failed there. with "CUDA driver version is insufficient for CUDA runtime version".
It seems there is more than one way to fail ("No CUDA, wrong CUDA, ...") and an additional function might still be a good idea. For now this workflow (try and check status) seems to be okay.

I reopen and will implement this (http://docs.nvidia.com/cuda/cuda-c-best-practices-guide/index.html#testing-for-cuda-availability).

In 4aeecaab8ebf8d46addc9aaec6b6cefa8ecbcecc I did this now. Only Matlab hasn't the cuda_available function yet, but it can just try to fit and then fail and see the reason.


How to enable tracing to show up in WebApi Owin project?

Sorry if this is a noob question but i'be been trying all day to try and get the MembershipReboot trace messages to appear when debugging my project.
I'm able to see my own trace messages but nothing from MembershipReboot.

Figured it out.
Just had to add a switch in the web.config.
Hope this helps others:
<system.diagnostics>

</system.diagnostics>

Any ideas how to get this working with ASP.NET 5 / Core? I've tried adding a similar structure to the appsetting.json file but no trace statements are being displayed for MR. Here's the JSON:
"system": {
  "diagnostics": {
    "switches": {
       "add": {
      "name": "MembershipReboot",
      "value": "Verbose"
       }
    }
  }
}

This would be another thing to change for ASP.NET Core -- how MR does logging. So many new things for the new scenario.

It's not entirely incompatible; at least I don't think it is. I was able to output a Trace log from within my project by writing something along the lines of Trace.WriteLine("I have nothing to say."). I'll do some further testing with the TraceSource object as is used by MR. However, I believe I'm just missing the equivalent of the config noted above to add the trace switch. The answer's out...


Test that git history is removed

cargo generate removes .git and then makes a blank one - this should be tested

I had this issue a few weeks ago.
I will propose a solution soon.


Reporter.log do not work inside onFinish event when calling testng ant task

In testng 6.8, I was able to call Reporter.log("foo") to publish reporter log in testng-result.xml during onFinish () event in ITestListener.
In testng 6.9, I am not able to publish reporter.log("foo") during onFinish event in ITestListener.
Note - This only happens when running testng in ant using TestNGAntTask class
Thanks

Could you share some code which could help us to understand clearly your problem and what you expect?


Add env field to ServingRuntime builtInAdapter settings

What this PR does / why we need it:
Built-in runtimes that use the built-in adapter container have certain specific parameters configured via the builtInAdapter section in the CRD.
However, there are certain other properties of the built-in runtimes that we may want to set/change for various reasons, so it would be good to extend this with a map of arbitrary environment variables to use for this purpose. Having this means that we can expose such additional properties for the built-in runtimes without requiring further changes to the CRD.
Note this will currently only be applicable for the built-in modelmesh multi-model runtimes.
Signed-off-by: Nick Hill<EMAIL_ADDRESS>Type of changes
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
Testing will be covered on the modelmesh controller side.

Thanks @pvaneck, I've now pushed an update for that.

@yuzisun Can you take a look and approve it if it looks good?

@yuzisun ping :)

/lgtm
/approve


Negotiate method should return 406 if can't find relevant response negotiator

Currently if you call response.Negotiate(model) and you ask for text/html and there is no negotiator that can handle html it will return json.  In this scenario it should return a 406 and empty body.

The specification for 406 (https://tools.ietf.org/html/rfc7231#section-6.5.6) says a payload with the available representations should be generated.  Should Negotiate be generating this to follow the spec or is returning an empty body a pragmatic choice?

I think it's the latter and the same approach we used in Nancy but didn't realise the server SHOULD return a payload.
I wonder if @darrelmiller has any opinion on this and what the body should look like

Personally I'm fine with the empty body.
If it was to generate a body, implementation-wise I guess IResponseNegotiator might need to expose the content type it will generate in order to build a list of available respresentations?

@jchannon
There was a draft proposal once upon a time that provided a way of describing the potential available variants, but I'm pretty sure it was all done in headers.  I suspect this 406 body is based on the same dream of returning a body from a 300.  However, until someone proposes a media type to do this and it gets some traction I think either an empty body, or some human readable HTML is the way to go.
On a related note.  Do you give the option for the server to say "I don't care that you asked for X, I don't support X, so I'm giving you the default Y"?  This is instead of doing 406.

Yeah that's what it does now, if I can't find a way to negotiate the Accept header it returns a JSON representation. I know that it's ok to do that I just had a thought I wondered if 406 would be better. I'm in two minds 😄

As a framework author, you get to have an opinion here.  Do you pick one way, or do you make it configurable?  The question is, what is a client going to do?  You are either returning an error code, or a content type they claim they can't handle.  The only upside to the second approach is a client can fallback to what a web browser does and say, would you like to save that to disk?


Why double the supernode list

Question

Why double the supernode list here?
https://github.com/dragonflyoss/Dragonfly/blob/master/dfget/core/core.go#L283

func adjustSupernodeList(nodes []string) []string {
switch nodesLen := len(nodes); nodesLen {
case 0:
return nodes
case 1:
return append(nodes, nodes[0])
default:
util.Shuffle(nodesLen, func(i, j int) {
nodes[i], nodes[j] = nodes[j], nodes[i]
})
return append(nodes, nodes...)
}

It's a simple retry mechanism when errors happened.

It's a simple retry mechanism when errors happened.

Thank you


Set up number of nodes and node type

Hello everyone, I'm having some problems to set up a ES cluster using terraform.
I'm not using the HCL, but I'm using CDKTF in Typescript.
Basically I'm trying to set up a small "example" cluster that I'm using for testing terraform and CDKTF
This is the code:
    new EcProvider(this, 'elastic_cloud_provider', {});

    const exampleELK = new Deployment(this, 'elastic_cloud_deployment', {
      name: 'example',
      region: 'eu-west-1',
      version: '8.9.0',
      deploymentTemplateId: 'aws-general-purpose-v5',
      elasticsearch: {
        hot: {
          autoscaling: {
            maxSize: "0g",
            maxSizeResource: ""
          },
          zoneCount: 2,
          size: '4g',
          nodeTypeData: 'true',
          nodeTypeMaster: 'true',
          nodeTypeIngest: 'true',
          nodeTypeMl: 'false'
        },
      },
      kibana: {
        zoneCount: 1,
        size: '1g',
      },
    });

I have a couple of question, is it possible to set up a number of nodes?
For example, I would like to set up 10 hot nodes, is it possible to do it?
Also, I'm getting this error with the nodeTypeXXXXX configuration:
               │ Error: Provider produced inconsistent result after apply
               │
               │ When applying changes to ec_deployment.elastic_cloud_deployment (elastic_cloud_deployment), provider
               │ "provider[\"registry.terraform.io/elastic/ec\"]" produced an unexpected new
               │ value: .elasticsearch.hot.node_type_ml: was cty.StringVal("false"), but now
               │ null.
               │
               │ This is a bug in the provider, which should be reported in the provider's own
               │ issue tracker.
               ╵
               ╷
               │ Error: Provider produced inconsistent result after apply
               │
               │ When applying changes to ec_deployment.elastic_cloud_deployment (elastic_cloud_deployment), provider
               │ "provider[\"registry.terraform.io/elastic/ec\"]" produced an unexpected new
               │ value: .elasticsearch.hot.node_type_ingest: was cty.StringVal("true"), but
               │ now null.
               │
               │ This is a bug in the provider, which should be reported in the provider's own
               │ issue tracker.
               ╵
               ╷
               │ Error: Provider produced inconsistent result after apply
               │
               │ When applying changes to ec_deployment.elastic_cloud_deployment (elastic_cloud_deployment), provider
               │ "provider[\"registry.terraform.io/elastic/ec\"]" produced an unexpected new
               │ value: .elasticsearch.hot.node_type_data: was cty.StringVal("true"), but now
               │ null.
               │
               │ This is a bug in the provider, which should be reported in the provider's own
               │ issue tracker.

From the issue 663, I got that

This was caused by autoscaling configuration we had to specify: max_size and max_size_resource under autoscaling as null explicitly

But as you can see I set up the max_size and max_size_resource as empty and got the error.
Any ideas I would really appreciate

tl;dr remove all the nodeType* attributes to fix the error you're seeing.
It looks like you're getting the same error as https://github.com/elastic/terraform-provider-ec/issues/663. nodeType* attributes aren't supported in 8.x stack versions, which only supports node roles. Really, you shouldn't need to specify these though, the provider will use the values from the deployment template.

I have a couple of question, is it possible to set up a number of nodes?
For example, I would like to set up 10 hot nodes, is it possible to do it?

Essentially no. Elastic Cloud only allows specifying the total size of a deployment in a single zone rather than individual node counts/sizes. To have 10 hot nodes per zone, you'd have to scale up to 10x the largest node size (~64G depending on the template). What are you trying to test with a specific node count?

Thanks for the reply, let me ask a few more questions :)
I understand that nodeType* is not supported with 8.X stack. But correct me if I'm wrong, but the node_roles is a read only variable.
So we are not able to change it, correct?
For example:
      elasticsearch: {
        master: {
          autoscaling: {},
          zoneCount: 1,
          size: '1g'
        },
        hot: {
          autoscaling: {},
          zoneCount: 2,
          size: '4g'
        },
      },
      kibana: {
        zoneCount: 1,
        size: '1g',
      },
    });

In the example above, there will be a master node with the master role, a kibana node and the hot node that they will have the roles ingest and data.
Is this correct?
@tobio regarding your question:

Essentially no. Elastic Cloud only allows specifying the total size of a deployment in a single zone rather than individual node counts/sizes. To have 10 hot nodes per zone, you'd have to scale up to 10x the largest node size (~64G depending on the template). What are you trying to test with a specific node count?

With the configuration above, I'm getting this error:
               │ Error: failed creating deployment
               │
               │   with ec_deployment.elastic_cloud_deployment (elastic_cloud_deployment),
               │   on cdk.tf.json line 126, in resource.ec_deployment.elastic_cloud_deployment (elastic_cloud_deployment):
               │  126:       }
               │
               │ api error: 1 error occurred:
               │        * cluster.dedicated_master_prohibited: Deployment template [General purpose]
               │ requires at least [6] data nodes before dedicated master can be specified.
               │ Found only [2] data nodes in the deployment (resources.elasticsearch[0])
               │
               │
               |
              ╷
               │ Error: failed creating deployment
               │
               │   with ec_deployment.elastic_cloud_deployment (elastic_cloud_deployment),
               │   on cdk.tf.json line 126, in resource.ec_deployment.elastic_cloud_deployment (elastic_cloud_deployment):
               │  126:       }
               │
               │ set "request_id" to
               │ "x8rl6ft0wxx3sfquv18nuucoycwv1oh8xogfvcssrz0vbjw14vr9nne48upniofr" to
               │ recreate the deployment resources

As far as I understand I would need to define the number of hot node to be able to set up a master node.
I understand I would be able to resize the number of node using autoscaling, but I would like to set up a number of node from the start to have.
Thanks again :)

As far as I understand I would need to define the number of hot node to be able to set up a master node.

Yea, this is a bit of a sharp edge with the provider at the moment. Ideally, you shouldn't have to care about master nodes unless you wanted a non-default size node. That is, the provider would just handle it. We have #635 to improve the usage around this.

but I would like to set up a number of node from the start to have.

So you can create a deployment with more than one hot node per zone. You'd just have something like:
hot: {
          autoscaling: {},
          zoneCount: 2,
          size: '174g'
        },

It looks like hot nodes on aws-general-purpose-v5 max out at 58G, so you'd have 3 nodes x 2 zones = 6 nodes total. I understand having to do the maths is annoying though.
Since you're in CDKTF you could calculate the required size in code. You'd have to get the deployment template with show_instance_configurations=true which will return the discrete node sizes available for the hot tier then multiple the max size by the number of nodes you're after.

If I need to migrate a Elasticsearch cluster, I would like to have the same number of nodes at the beginning.

Sizing isn't my area, but the normal advice here would be start off looking for similar available RAM/vCPU rather than pure node count. The RAM/CPU ratio is likely different between on prem and Cloud.


Add orphanet subset including source information

Supercedes #7017
@sabrinatoro this time with provenance! Thanks for the review.

@sabrinatoro yes-this is true. Since subsets are externally managed, they can contain obsolete classes. I added that talking point to the  Mondo technical call agenda.


Use URLSession to load images in the background + linting fixes

Hi @cameronshemilt & @mikakruschel ,
I am quite excited about the widget and have been using it since it was released 🚀
Currently I am having problems with the widget from time to time and am trying to debug it. I have seen that Xcode writes warnings that image data is loaded on the main thread. I fixed this with the async/await call to URLSession. I'm still looking at the widget issue when I get it working. Currently it's a bit difficult unfortunately as I need to set up all the BundleId, AppGroup, Keychain identifiers for my dev account. If there is interest, you can of course invite me as a developer to your dev account.
Best regards
Julian 🙂

Hey @JulianKahnert, thanks for your PR. We are currently working on a brand new version of ACWidget and will integrate your changes there. If you are interested we can share a TestFlight link as soon as the app is somewhat working.

Hi @mikakruschel , are you still working on this app? I really like it ☺

Hi @JulianKahnert, yes and no. We completely rewrote the app and added a ton more features to it: https://apps.apple.com/de/app/trendly-app-sales/id1669815607. We will update this repo with a link to the new app. Thanks for your interest!


Introduce nanosecond precision ticks

Purpose
This is a fix for #207, which dealt in round-off errors.
Other notable changes are:

removes clock.hrNow. Should not be an issue as it's an internal detail not documented in our API
throws on negative ticks. This is a breaking API change, but I would be very surprised if it affected anyone, as this essentially means backwards time travel.
change some test structure, replacing if() blocks with conditional this.skip()

Background
This PR fixes #207 by doing away with floats for representing time; opting to store milliseconds and millisecond decimals separately. We could have avoided the complications of storing two parts by opting to store all ticks as nanoseconds, but that would pose other round-off issues when adding/subtracting high-value milliseconds. Javascript is unable to represent the epoch as nanos due to too few bits for the Number type. See discussion in #207 for more background. The test cases found through that issue is included in the test suite.
I tried a few approaches, but this approach was the simplest one to follow and allowed me to do away with a bit of code. For a while I had problems with the behaviour that setting system time should not affect the hrtime, and I tried recreating the approach of using a separate clock for hrtime (which was the purpose hrNow served), but keeping the two clocks in sync, including the nanosecond offsets, with all the existing updateHrTime() callsites was just too much for my simple mind to fathom :boom: Instead I found a simpler solution which was just to record the delta between the new and old time when a new system clock is set and use that to compensate in the hrtime() function (see ae83b27).
closes #207
Verifying

clone the repo and checkout the branch
npm install && npm test
npm run test-cloud (if you have sauce labs credentials)
npm link - will install this as your local lolex
Require lolex in your repo and run against your own code/tests

this still can be potentially not as precise

Good point! We discussed this initially and agreed on truncating anything less than a nanosecond, so I'll add a final commit. Should suffice with a Math.floor() in nanoRemainder.

Truncation of sub-nanosecond values in place.

I have no further comments, would like to see at least one other 👍 before we merge this though

@SimenB  As in, if we can come up with other breaking changes we would like to see implemented before releasing a new major?
Or, can I think if any other breaking changes in this PR?

Thanks for checking, @novemberborn! Good to go, I assume.

Released Lolex 3


Apply filters only on server-side

Expected Behavior
When serverSide option is set to true, applyNewFilters function shouldn't apply filters on client-side but let the filters to be applied on server-side. Only chips should be displayed.
Current Behavior
Currently client-side filtering is applied before server-side filtering. This causes the content of the data table to change twice; first time it displays wrong data (client-side filtering applied) and second time it displays correct data (server-side filtering applied).
Steps to Reproduce (for bugs)
I followed this example https://github.com/gregnb/mui-datatables/blob/master/examples/serverside-filters/index.js along with server-side pagination. The issue is in handleFilterSubmit function where client-side filtering (i.e. applyNewFilters) MUST be applied before server-side filtering to resolve the final filters sent to the server-side for filtering.
Your Environment

Tech
Version

MUI-datatables
3.7.7

You could override the filterOptions logic method to return false.  This effectively disables client-side filtering, but it is still called (way more times than it should be - #1733).

Thanks, it seemed to work.
There's still one annoying thing when using server-side filtering with logic method set to return false. When invoking applyNewFilters method, the filter dialog is closed and chips are added, BUT only after that we can make the request to backend to get the filtered data. I think it should happen vice versa i.e. getting the data first and then closing the dialog and adding chips. Yes, it works both way and is more a matter of user experience.


Switch from cquery to clangd as a default C/C++ language server

cquery

not maintained for over a year
not available in any package manager
not even binary releases available, huge hassle to install

clangd

part of LLVM/Clang suite, many C++ developers have already installed
multiplatform
easily installed through package managers by a single command
actively developed

Proposed change
Change the default language server to clangd. It works out of the box like this:
[language.cpp]
command = "clangd"
args = []

I have tested and I think clangd is better than cquery.
The PR is created.


windowManager.show() doesn't work

I have just started with window_manager. WindowManager.show() must show a window but not thing shows up when I do this in the main function:
  WidgetsFlutterBinding.ensureInitialized();
  await windowManager.ensureInitialized();
  WindowOptions windowOptions = WindowOptions(
    size: Size(800, 600),
    center: true,
    backgroundColor: Colors.transparent,
    skipTaskbar: false,
    titleBarStyle: TitleBarStyle.hidden,
  );
  windowManager.waitUntilReadyToShow(windowOptions, () async {
    await windowManager.show();
    await windowManager.focus();
  });
runApp(MyApp());

Few things to do here

Remove the color.transparent 😅
Add 'await' on here below, like this
await windowManager.waitUntilReadyToShow ...
run flutter clean -> flutter pub get
and then try it 👍

What platform does the problem occur on? Is it a Release Mode?

Hey @lijy91, i believe Its actually just the combination of a transparent border with a hidden titlebar style causing it not to show, pretty much self explanatory if i must say 🙂 and a closed issue (but i understand it would be better if @dangluan343 affirms this)


Move to zlib-ng from the legacy zlib library

zlib-ng claims to have better optimizations and more improvements
then zlib project that is in the maintenance mode

Signed-off-by: Janusz Lisiecki<EMAIL_ADDRESS>

Relevant CI status in https://github.com/NVIDIA/DALI/pull/3570 (there was network issue that is why it failed, restarted and rechecking).


Add netherite horse armor

This armor prevents the horse from standing still when taking damage.

Netherite armor item currently has a broken texture, so + an investigation todo


[Bug]: Issue with Bitcrashing causing an issue with running the file.

Project Version
3.2.5
Platform and OS Version
Windows 11
Affected Devices
No device
Existing Issues
No response
What happened?
I'm having an issue regarding bitcrusher somehow crashing applio when selected for batch runs.
An error occurred during audio conversion: init(): incompatible constructor arguments. The following argument types are supported:
1. pedalboard_native.Bitcrush(bit_depth: float = 8)
Invoked with: kwargs: bit_depth=[{'type': 'update', 'visible': True}]
Traceback (most recent call last):
File "C:\Users*\Desktop\ApplioV3.2.5\rvc\infer\infer.py", line 497, in convert_audio
audio_output_path = self.post_process_audio(
File "C:\Users*\Desktop\ApplioV3.2.5\rvc\infer\infer.py", line 211, in post_process_audio
bitcrush = Bitcrush(bit_depth=bitcrush_bit_depth)
TypeError: init(): incompatible constructor arguments. The following argument types are supported:
1. pedalboard_native.Bitcrush(bit_depth: float = 8)
Invoked with: kwargs: bit_depth=[{'type': 'update', 'visible': True}]
Steps to reproduce

Simply run it with bitcrashing resulted in this error. For some reason its not giving the correct type. Found a solution which while inefficient, works.
...

Expected behavior
I expected it to work. In batch running, it completely fails outright and requires a full reboot (rerunning the .bat file).
Attachments
No response
Screenshots or Videos
No response
Additional Information
if bitcrush:
if bitcrush_bit_depth == [{'type': 'update', 'visible': True}]:
bit_depth = 8
bitcrush = Bitcrush(bit_depth)
else:
bitcrush = Bitcrush(bit_depth=bitcrush_bit_depth)
board.append(bitcrush)
Did some work to the applio files and created a simple hotfix for now.
For some reason the bitcrushbitdepth is returning a list of dictionaries??? [{'__type': 'update', 'visible': True}]
I presume this is due to the wrong data being assigned, but I don't have the technical knowhow to really 'fix' it.
This was in in the infer.py file

The solution is included in the actual code above, but it is a very poor solution. It does stop the crashing 👍