Appstudio update test-component-pac-qvso

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-qvso-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
21 seconds
inspect-image

✅ Succeeded
1 minute
deprecated-base-image-check

✅ Succeeded
41 seconds
clamav-scan

✅ Succeeded
10 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
18 seconds
label-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
11 seconds
show-summary

✅ Succeeded
7 seconds
show-sbom

Pipelines as Code CI/test-component-pac-qvso-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
22 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
20 seconds
deprecated-base-image-check

✅ Succeeded
21 seconds
inspect-image

✅ Succeeded
43 seconds
clamav-scan

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
15 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
12 seconds
show-summary

Pipelines as Code CI/test-component-pac-qvso-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
22 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
21 seconds
inspect-image

✅ Succeeded
20 seconds
deprecated-base-image-check

✅ Succeeded
43 seconds
clamav-scan

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
15 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
12 seconds
show-summary


Add freebsd support for sysinfo

I'm not sure if bevy works on FreeBSD or not. But in case it does, better allow sysinfo to be used as well if users want.

I don't think I've ever seen anyone try to use Bevy with freebsd, but I think this change is correct regardless in case we do add support or they just want to use the ECS or something.


Allow AwsDriver to work even if you haven't explicitly required 'chef/pr...

...ovisioning/aws_driver'

CC @tyler-ball @fnichol

Rebasing to get Travis to pass.  Otherwise, :+1:

Does it work to load the driver if no aws config exists? When we put our recipe together the chef run failed at compile time because aws config didn't exist yet.

I get [2015-04-06T17:51:06-05:00] ERROR: No credentials loaded!  Do you have a ~/.aws/config? if I don't have credentials, and it is a compile time bug.  @jkeiser is this the intended behavior?  @dblessing is your desire to have the recipe only fail if a call to AWS is attempted?

Lazy load would be great. Then the first part of recipe manage the configuration before any provisioning resources.

@dblessing Will you file a new issue on lazy loading?

Yep, I created one a while back. #145


Heroku : No application found to handle 'web_url'

I am trying to deploy my node.js application to heroku .I am following this tutorial.
But when I did heroku open below error is shown:
$ heroku open
Opening commentsystems... failed
 !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       No application found to handle 'web_url' (Launchy::ApplicationNotFoundError)
    Command:     heroku open
    Version:     heroku/toolbelt/3.42.37 (i386-mingw32) ruby/2.1.7
    Error ID:    a55dc665a86a49558f08b0af24a4a9d9

    More information in C:/Users/ABC/.heroku/error.log

error.log
Heroku client internal error.
No application found to handle 'web_url'
C:/Program Files (x86)/Heroku/vendor/gems/launchy-2.4.3/lib/launchy/application.rb:24:in `handling'
C:/Program Files (x86)/Heroku/vendor/gems/launchy-2.4.3/lib/launchy.rb:43:in `app_for_uri'
C:/Program Files (x86)/Heroku/vendor/gems/launchy-2.4.3/lib/launchy.rb:28:in `open'
C:/Program Files (x86)/Heroku/lib/heroku/helpers.rb:389:in `block in launchy'
C:/Program Files (x86)/Heroku/lib/heroku/helpers.rb:280:in `action'
C:/Program Files (x86)/Heroku/lib/heroku/helpers.rb:387:in `launchy'
C:/Program Files (x86)/Heroku/lib/heroku/command/apps.rb:233:in `open'
C:/Program Files (x86)/Heroku/lib/heroku/command.rb:212:in `run'
C:/Program Files (x86)/Heroku/lib/heroku/cli.rb:33:in `start'
C:/Program Files (x86)/Heroku/bin/heroku:29:in `<main>'

Then I tried
heroku config:set HEROKU_URL=$(heroku info -s | grep web-url | cut -d= -f2)

After that when I ran heroku open same error message was shown.
Is there anything I am doing wrong ?
Any help would be appreciated.
Thanks

@singhakash sorry for the delayed response but I have not been able to reproduce the issue you encountered.  Could you please set HEROKU_DEBUG=1 and try again and paste the output, the extra output should help me debug.

It worked now . I am not sure but it might be the Procfile issue.


Column type declaration is wrong for deeply nested values

From the documention
Column Options
accessor: String | Function(originalRow, rowIndex) => any
If a string is passed, the column's value will be looked up on the original row via that key, eg. If your column's accessor is firstName then its value would be read from row['firstName']. You can also specify deeply nested values with accessors like info.hobbies or even address[0].street
Next example shows how wrong Column type declaration makes TS errors:
import { Column } from "react-table";

export interface RowData {
  person: Person,
  profile: Profile
}

const columns: Column<RowData>[] = [
  {
    accessor: 'person.name'   // <--- TS2322: Type "person.name" is not assignable to type "person" | "profile".
  },
  {
    accessor: 'profile.userName' // <--- TS2322: Type "profile.userName" is not assignable to type "person" | "profile".
  }
]

The cause of the issue is too strict declaration of accessor field
{ accessor?: (keyof D extends never ? IdType<D> | Accessor<D> : Accessor<D>) | undefined; };

You should give more flexible rule for the field (add  | string option)
export type ColumnWithLooseAccessor<D extends object = {}> =
    & ColumnInterface<D>
    & ColumnInterfaceBasedOnValue<D>
    & (
        | { Header: string }
        | { id: IdType<D> }
        | { accessor: keyof D extends never ? IdType<D> : never | string}  // <-- here
    )
    & { accessor?: (keyof D extends never ? IdType<D> | Accessor<D> : Accessor<D>) | string | undefined; }; // <-- and here

I have this issue as well when running it with ts.
Looking for a solution or suggestion...
@BanderasPRO Did you manage to solve this issue?


how to authorize one module to call another module as in solidity?

I want to only allow only one module to call another module.
In ethereum solidity, it is quite easy to do since the sender will change to the calling contract.
Can I change the sender as I do in solidity?
Thanks.
George wu

This looks resolved, please reopen if it hasn't been.


[Import term] Quantification method from PRIDE

Term name and id
Quantification method (PRIDE_0000307)
Term link
http://purl.obolibrary.org/obo/PRIDE_0000307
Parent term(s)
No response
Child term(s)
The following child terms are desirable so that they can directly be used for PRIDE submission.

Please state the reason to import this term into dpbo
Terms are needed for creation of a template and subsequent submission to the PRIDE repository, as they have their own CV.
Your ORCID
0000-0002-8493-1077

Quantification method and child terms have been imported to dpbo.


added Bfs algorithm

Thank you for your contribution. Please provide the details requested below.
ISSUE NUMBER
#104
Please provide a link to the issue this pull request addresses.
https://github.com/codeIIEST/Algorithms/issues/104
SHORT DESCRIPTION
Added Breadth first search algorithm
TESTING
Just need to run the code and you can see the results

some tests are failing , please fix them

I want to close this PR and open a new one @prateekiiest

ok


Use react-lifecycles-compat polyfill

Deepest apologies for the reckless release of v7.4.0 without the React 16.3 polyfill.
Closes #4078
Fixes #4069
Fixes #4070
Fixes #4072

Published in v4.7.1.

Nope.

@erikras wait, but react-lifecycles-compat doesn't support the UNSAFE_ methods as far as I can tell... I think my PR is correct (I tested it :D). See https://codesandbox.io/s/r0o9q33lmp


feat(dbmigration): added licensetype table

added licensetype table for FOSS and COTS and also license_type_id attribute to offer table with default value of 1. Added Audit table for modified offer
ref:-CPLP-2489

i suppose to close this pr since all changes are already included in #316

@jjeroch  According to philip all changes related to CPLP- 2488 , CPLP-2489 and CPLP -2491 were already incorporated in PR https://github.com/catenax-ng/tx-portal-backend/pull/316  so other PR created for CPLP-2488 and 2489 i.e pr https://github.com/catenax-ng/tx-portal-backend/pull/314 IS NOT REQUIRED. Now everything is approved and merged to dev


working on springify the tr069 server (part 4)

with all necessary steps done, I can now port the FreeACS tr069 server to spring boot. Hurra. It will be awesome. It will be testable. And it will be working exactly the same as before :P

@pingwiniasty this is a pretty nasty rewrite. I don't have the patience to do small pull requests.
Your best hope to get an overview of this pr is to checkout the branch. And take a look around.

DBI is a bean of it self. Skipped the DBAccess wrapping.
Replaced custom logging with sl4j
Using Lombok to generate logger where I need a logger
Removed custom security and added conditionally loaded security config based on auth.method
etc etc

Oh and I removed some tests. Need to add them back. So lets do this in two steps. First you review and do some critical thinking ;) then we merge, and then I make a new pull request with tests. I will have to rewrite the tests anyway. The old tests is safely stored in git history.

Oh and I should maybe add back the feature to use or not use file auth. I can add this is in the security config based on the properties.

Ok, I'll check it today ;)

@pingwiniasty now I have added conditional file auth, a discover unit test (WITH digest authentication, yey 👍 ). So now I shouldn't touch this more before it enters master. The test is miles more readable than the old test. I may need to add test for basic authentication and no authentication too, but the fact is that the authentication part is so loosely coupled to the tr069 controller now so that if one work, the other should also work. But yes we need to test all use cases over time.

No patience:) we will do it like this. I merge now. And then you can take a look on master when ever you want @pingwiniasty. I will make sure to squash this pr into a single commit

Sorry, today I have no time to get to computer :(

@pingwiniasty no problem :) no stress. The important thing is that you know that i am making changes. And what they are. Have a nice saturday evening!!


Front camera photo mirrored

Steps to Reproduce
Picture controller take photo on front camera
Expected results
Save photo with no mirror effect
Actual results
Save photo with mirror effect
About your device

Brand
Model
OS

Oneplus
7 Pro
Android 10

Hi, thank you for reporting this.
I put this as an enhancement.

This is actually Bug, because taken photo which is saved is mirrored

there is pretty simple to fixed this bug,,,
you should mirror back as result file.
first, you need to install flutter plugin called image_editor.
then,
look at my takePhoto function.
_takePhoto() async {
    final Directory extDir = await getTemporaryDirectory();
    final testDir =
        await Directory('${extDir.path}/toko_kece/media').create(recursive: true);
    final String filePath = '${testDir.path}/toko_kece${DateTime.now().millisecondsSinceEpoch}.jpg';
    await _pictureController.takePicture(filePath);
    // lets just make our phone vibrate
    HapticFeedback.mediumImpact();

    setState(() {});
    print("----------------------------------");
    print("TAKE PHOTO CALLED");
    final file = File(filePath);
    print("==> hastakePhoto : ${file.exists()} | path : $filePath");
    print("----------------------------------");

    if (_sensor.value == Sensors.FRONT) {
      // 1. read the image from disk into memory
      Uint8List imageBytes = await file.readAsBytes();

      // 2. flip the image on the X axis
      final ImageEditorOption option = ImageEditorOption();
      option.addOption(FlipOption(horizontal: true));
      imageBytes = await ImageEditor.editImage(image: imageBytes, imageEditorOption: option);

      // 3. write the image back to disk
      await file.delete();
      final res = await file.writeAsBytes(imageBytes);
      Navigator.of(context).pop(res);
    } else {
      Navigator.of(context).pop(file);
    }
  }

and voila,
you can preview the image after you mirror back the result from camera.

there is pretty simple to fixed this bug,,,
you should mirror back as result file.
first, you need to install flutter plugin called image_editor.
then,
look at my takePhoto function.
_takePhoto() async {
    final Directory extDir = await getTemporaryDirectory();
    final testDir =
        await Directory('${extDir.path}/toko_kece/media').create(recursive: true);
    final String filePath = '${testDir.path}/toko_kece${DateTime.now().millisecondsSinceEpoch}.jpg';
    await _pictureController.takePicture(filePath);
    // lets just make our phone vibrate
    HapticFeedback.mediumImpact();

    setState(() {});
    print("----------------------------------");
    print("TAKE PHOTO CALLED");
    final file = File(filePath);
    print("==> hastakePhoto : ${file.exists()} | path : $filePath");
    print("----------------------------------");

    if (_sensor.value == Sensors.FRONT) {
      // 1. read the image from disk into memory
      Uint8List imageBytes = await file.readAsBytes();

      // 2. flip the image on the X axis
      final ImageEditorOption option = ImageEditorOption();
      option.addOption(FlipOption(horizontal: true));
      imageBytes = await ImageEditor.editImage(image: imageBytes, imageEditorOption: option);

      // 3. write the image back to disk
      await file.delete();
      final res = await file.writeAsBytes(imageBytes);
      Navigator.of(context).pop(res);
    } else {
      Navigator.of(context).pop(file);
    }
  }

and voila,
you can preview the image after you mirror back the result from camera.

Thanks billbull21. You save my life!


Use respond_to_missing instead of respond_to

Best to override respond_to_missing? instead of respond_to?. It's faster and allows accessing method.
Builds on #28

Coverage increased (+0.003%) to 94.963% when pulling fe69deb17d9d083d59fa913e8b34f3d1908b71fd on marcandre:respond_to_missing into 7dffc5d7be0863821067bb16c1b20ef412d26389 on weppos:master.

Out of my curiosity, do you have any relevant docs or resource I can read about how respond_to_missing? is faster and why it is better?

Well, I kind of misspoke, it's probably not much faster for methods using method_missing, but it is faster for standard instance methods.
The main reason is that it makes it possible to access a method even when implemented this way.


http client memory leak

This code has a memory leak. Memory grows with every request.
package main

import (
    "fmt"
    "net/http"
	"io"
	"io/ioutil"
	"time"
)
func main() {
    httpClient := &http.Client{}
	for {
		res, err := httpClient.Get("https://google.com/")
		if err != nil {
			return
		}
		defer res.Body.Close()

		io.Copy(ioutil.Discard, res.Body)
		fmt.Println(res.StatusCode)

		time.Sleep( time.Second * 1 )
	}
}

go version go1.12.5 windows/amd64

defer runs when the function (here main()) returns, so if you call it in a loop it is never going to run, and they will accumulate in memory, also keeping references to the request bodies.

Ok. I rewrote - the problem remains! Why do you close the ticket without checking in practice?
package main

import (
	"fmt"
	"net/http"
	"io"
	"io/ioutil"
	"time"
)
func main() {
	httpClient := &http.Client{}

	for {
		res, err := httpClient.Get("https://google.com/")
		if err != nil {
			return
		}

		io.Copy(ioutil.Discard, res.Body)

		fmt.Println(res.StatusCode)

		time.Sleep( time.Second * 1 )
		res.Body.Close()
	}
}


Integer message requires translating into Spanish and Russian

#46

(I also don't know these languages)


feat(bulk-model-sync-gradle): make request timeout configurable

Depending on the size of the model, the import into the model-server might have some long-running HTTP calls. As the default timeout was not sufficient in all cases, it can now be configured by users of the task.

:tada: This PR is included in version 3.18.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix typo introduced by linter refactoring

Short description
This addresses #731, which is a bug introduced by the linter refactoring
Proposed changes
Complete the refactoring by fixing the variable reference
Resolved issues
Fixes: #731

#732 already fixes it


docs: Docusaurus v3.0 blog post

Motivation
Docusaurus v3 blog post
https://deploy-preview-9433--docusaurus-2.netlify.app/blog/releases/3.0

Have we mentioned the maintenance state of v2 onwards anywhere? I think for every new major release, we should restate the note on https://docusaurus.io/community/release-process#versions, because it helps with discoverability. We can add this to the intro section:

This also means v2 has now entered maintenance mode. It will continue to receive support only for major security issues for 3 months (ending in late January, 2024). Otherwise, all features will be frozen and non-critical bugs will not be fixed.
It is recommended to upgrade within that time frame to v3.

@dmitryvinn To make editorial suggestions, please use the suggestion button, especially because otherwise it's hard to see how the Markdown works.


listen on custom port remote machine

Is it possible to specify on which port the remote/public server listens to? I would like to forward port 25 on the remote to my local machine so I can receive email. It seems to only listen to port 80.

Tunwg only works for HTTP servers(more specifically any protocol which can support SNI over TLS), and is not meant as a generic tunnel between two machines.


resolves #1557 fix spacing after first line of indented paragraph

I figured it out. The value for the spacing after the first line was not being computed correctly. It affected some fonts, but not others. The fix will ensure the value is computed correctly.


Unable to install plugin that requires additional permissions

There are some plugins like the ingest-attachment plugin that requires some additional privileges. In the Elasticsearch documentation it is said that such plugins can be installed by using --batch. However, I can't seem to make it work.
This is what I have:
embeddedElastic = EmbeddedElastic.builder()
                .withElasticVersion("5.6.3")
//                .withPlugin("ingest-attachment")
                .withPlugin("--batch ingest-attachment")
                .build()
                .start();

I thought I can just add anything into the expression. However, it seems that it doesn't work properly. Maybe such option is not allowed to be passed onto the ProcessBuilder.
If there is no way to do it with the current API. I would propose that either you pass that argument always or you add the ability for it to be passed, either via a free text or a boolean (isBatch).

For some reason this is working now (without the need to install the plugin via batch). So I am not sure whether I was doing something wrong yesterday or something else was the issue. In any case I think it is not an issue of embedded-elasticsearch


Document blackfire.io cli client setup and usage

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Anja Leichsenring seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks so much for exploring this territory and taking the time to document this!


Double slashes in request line when using HAPROXY_0_HTTP_BACKEND_PROXYPASS

Using HAPROXY_0_HTTP_BACKEND_PROXYPASS adds an extra / to the request line.
Setup to reproduce:

marathon-lb v1.3.2, group = internal
Default nginx docker image named "testapp" in marathon

Labels for testapp:
HAPROXY_GROUP=internal
HAPROXY_0_VHOST=internal.example.com
HAPROXY_0_PATH=/testapp
HAPROXY_0_HTTP_BACKEND_PROXYPASS_PATH=/testapp

I expected the requests to end up like this:
http://internal.example.com/testapp     -> GET /
http://internal.example.com/testapp/    -> GET /
http://internal.example.com/testapp/foo -> GET /foo

But in the logs this is what I see:
[04/Aug/2016:08:15:17 +0000] "GET / HTTP/1.1" 200
[04/Aug/2016:08:15:18 +0000] "GET // HTTP/1.1" 200
[04/Aug/2016:08:15:20 +0000] "GET //foo HTTP/1.1" 404

Looking through the code this is consistent with how this is implemented:
reqirep  "^([^ :]*)\ {proxypath}(.*)" "\\1\ /\\2"

This could be fixed by adding a optional /like so:
reqirep  "^([^ :]*)\ {proxypath}/?(.*)" "\\1\ /\\2"

The proposed fix is available in PR #286.


Ollama run in other machine

Hi,
Thanks for the app. How to connect to Ollama that runs on other machine?
Tried to change this but failed.
RequestUri = new Uri("http://10.20.xxx.xxx:11434/api/generate", UriKind.Absolute),

Hey,
can you reach your server in the CLI? What do get with curl -v http://10.20.xxx.xxx:11434/ ? "Ollama is running" or a 403 Forbidden?


Fix 22369 - Omit unreachable statements in std.concurrency

Instantiating these templates with noreturn values / callbacks causes
the versioned statements to become unreachable.

Includes #8265 to make the test case compilable

It seems to me that noreturn has the same stink as void in requiring these special cases


Questions about development progress and plans

Hi there, I'm a research student in the field of multi-agent systems, and I'm fascinated by this amazing environment and keen to track your progress. It appears that you have been actively updating this repository lately, which presents a slight challenge for me to seamlessly integrate it into my own codebase. I was wondering if there is a development plan or any specific goals you have set for this project recently?

Hi!
Thanks for the nice comment :) I currently do not have a set agenda for this work as I have now published the paper using this environment. However, I want to support agents entering and exiting at any time step, and am currently implementing it. This should not affect any of the current functionality and seamlessly integrate using default arguments turning it off. If you need anything specific I would recommend to just freeze on a certain commit or I could add a tag on one version that you can then more easily return to if you wish to. Just tell me what you prefer!

Thank you for your response. I plan to incorporate the latest commit before attempting to implement the functionality of agents entering and leaving. I believe that version is comprehensive, and it would be helpful if you could add a tag to indicate it as such for other developers.


Resolve constructor arguments

Constructor arguments are resolved and filled in object creation for the
Mockito field injection refactoring.
ReBoot now first refactors src directory and then the test directory.
Otherwise it has to guess how code will look like after a refactoring
(ReBooting test first, before src).
Closes #6

Codecov Report

Merging #9 into master will decrease coverage by 0.14%.
The diff coverage is 63.93%.

@@            Coverage Diff             @@
##           master       #9      +/-   ##
==========================================
- Coverage   74.15%   74.00%   -0.15%
==========================================
  Files           6        6
  Lines         178      227      +49
  Branches       54       73      +19
==========================================
+ Hits          132      168      +36
- Misses         24       27       +3
- Partials       22       32      +10

Impacted Files
Coverage Δ

...ot-core/src/main/kotlin/nl/thanus/reboot/ReBoot.kt
0.00% <0.00%> (ø)

...ain/kotlin/nl/thanus/reboot/refactoring/Mockito.kt
85.71% <78.72%> (-6.60%)
:arrow_down:

...n/kotlin/nl/thanus/reboot/refactoring/Autowired.kt
82.14% <100.00%> (ø)

...lin/nl/thanus/reboot/refactoring/RequestMapping.kt
81.39% <100.00%> (ø)

Continue to review full report at Codecov.

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


[AutoRelease] t2-network-2024-06-19-49703(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/2048
Recording test success
BuildTargetingString
azure-mgmt-network
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/2048


chore: Add workflows

Fixes #6
Summary

Adds useful workflows for the org project and others

ehhh @crookse heelp me

got you fam

we good now

lgtm


Confusing PolicyBrain releases

@brittainhard,
You created release 1.0.2 over a week ago, but TaxBrain still isn't running that version.
And now there is a pre-release of version 1.0.3 even though there are pending pull requests.
What is pre-release 1.0.3?
Are you going to skip 1.0.2?  If so, what was the point of creating release 1.0.2?
As you can see, I'm very confused about the release numbering and what it means.
Please explain.
Are you trying to follow the rules of semantic versioning?
@MattHJensen @hdoupe @GoFroggyRun

I think this question is best addressed to @hdoupe. We are transitioning versioning and milestone responsibilities to Hank.
@martinholmer

@hdoupe said in discussion of #672:

Version 1.0.2 was released but still had bugs.

That's my core question: why did @brittainhard do that?
Why not fix the bugs in 1.0.2 and then release 1.0.2?

@hdoupe said:

This is the process that I envision using:

Tag pre-release and push to the test server for testing
Find bugs and update pre-release with fixes
Push the same version (but with the fixes) to the test server
Upon getting sufficiently satisfying performance, do a full release and push the full release to the production server. At this point, any modifications to the code base will go into a different release.

This makes sense to me.  Do you have the permissions required to do all these steps yourself?

@martinholmer we are still working out kinks in the PolicyBrain release process. I talked to Matt about this on a call last Friday.
Setting up a consistent, well managed release process is difficult for any project that has many contributors, especially open source projects, which tend to be much more loosely organized. Indeed, in my experience, solid release processes in this context are the exception rather than the rule.
There is often the temptation for "feature creep". In open source applications. There is always a way to make something better than it was before, and there is always an urge to make it available sooner rather than later. Going forward, my plan is to have us stick to milestones very closely.
With version 1.0.3, we had code that was a combination of bugfixes and features. I felt that since it contained both of these, we needed a new version rather than an update to version 1.0.2. If we re-released version 1.0.2 with this new code we would be re-writing the version history, so I chose to create a new tag.

@brittainhard said:

With version 1.0.3, we had code that was a combination of bugfixes and features. I felt that since it contained both of these, we needed a new version rather than an update to version 1.0.2. If we re-released version 1.0.2 with this new code we would be re-writing the version history, so I chose to create a new tag.

This makes sense to me.  Do you think that PR's #670 and #671 fit under Version 1.0.3?

@hdoupe and @brittainhard, thanks for all the explanation about how the PolicyBrain release process is going to work.


There are no UTs for packages/drivers/odsp-driver/src/rateLimiter.ts

Also, can we add telemetry when we hit some limits? Like 6 concurrent requests?
Ideally this is flexible functionality exposed by RateLimiter, where users of it can add their own policy.

Resolving as unit tests were added in this PR: https://github.com/microsoft/FluidFramework/commit/a9b08ce59e5947a05c4fd83d830ed8285f77a35d.
Also we already log the length of wait queue for blobs fetch telemetry as that would be the place most likely to hit the limit.


finish packaging/debug a bit

Confirmed that radam install from git repo works (with pip install ., not with python setup.py install) and reworked setuptools syntax to avoid built-in python packages. As a result, also removed radam from the package file structure, since the original file lives in misc if it's needed.
For ease, added a .gitignore file to avoid upload of .egg_info and .DS_store files.
Everything else should be the same as ~an hour ago.
(Note that there is an error in the most updated setuptools that requires downgrading to setuptools<70 or the latest beta version, which may pose a problem for some people.)

Had an error in .gitignore, so fixing and re-PRing.


[Bug]: Incorrect compiler warning when a type is used in a client where both type and the client have module-level visibility

Description
See the issue summary. I had to mark the type public as a temporary measure.
Steps to Reproduce
type Employee record {|
....
|};

client class RainierClient {
    resource function 'select employees() returns stream<Employee, error?> {
       ....
    }
}

This code triggers a compiler warning:
attempt to expose non-public symbol 'Employee'
Affected Version(s)
Ballerina 2201.3.0 (Swan Lake Update 3)
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

This is probably because resource methods are public implicitly. Either way should go away when we remove this warning altogether, since the spec doesn't require it.

Looks like this is fixed now. Please confirm and close.

Still seeing the warning (U10).


Update for MSAL Net 2

Given the new update to MSAL Net 2 (https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/msal-net-2-released#migrating-from-adalnet-3x-or-4x-to-msalnet-2x), could this example be altered to reflect the changes?
From what I can tell, the only change in this would be changing the body of GetUserAccessTokenAsync to use cca.GetAccountsAsync() and checking the result for items, rather than using cca.Users. Or would you use cca.GetAccountAsync?
Anyways, I would submit a pull request, but with the new changes I am not able to get this sample to work (my cca.GetAccountsAsync() returns an empty IEnumerable; no clue why, and I can't find any documented issues on this on Stack Overflow or on the MSAL repo). I don't want to submit a PR for something I haven't been able to test!
Anyways I'm guessing
if (!cca.Users.Any()) throw new ServiceException(new Error

...
`
would need to change to
var accounts = await cca.GetAccountsAsync();`
if (!accounts.Any()) throw new ServiceException(new Error
...

in the GraphAuthProvider class.
If I can get the GetAccountsAsync to return properly, I'll try to put a pull request together.

I have the same problem.
We have Azure AD User schema extensions and want to read them in a ASP.NET Core API request.
I cannot get a working sample and the latest MSAL package has a huge number of breaking changes.
Any news here?

Having the same issue, I'm not finding any of the MSAL samples working with the latest changes.

Thank you for getting this to our attention! I have updated and tested the sample, it should work. 😊


Cleanup dictionary and forward index loading in SegmentPreProcessor

Move the dictionary and forward index loading logic into the LoaderUtils class

Codecov Report

Merging #6455 (6a23379) into master (1beaab5) will decrease coverage by 1.19%.
The diff coverage is 56.80%.

@@            Coverage Diff             @@
##           master    #6455      +/-   ##
==========================================
- Coverage   66.44%   65.25%   -1.20%
==========================================
  Files        1075     1330     +255
  Lines       54773    64909   +10136
  Branches     8168     9467    +1299
==========================================
+ Hits        36396    42357    +5961
- Misses      15700    19520    +3820
- Partials     2677     3032     +355

Flag
Coverage Δ

unittests
65.25% <56.80%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...e/pinot/broker/api/resources/PinotBrokerDebug.java
0.00% <0.00%> (-79.32%)
:arrow_down:

...ot/broker/broker/AllowAllAccessControlFactory.java
71.42% <ø> (-28.58%)
:arrow_down:

.../helix/BrokerUserDefinedMessageHandlerFactory.java
33.96% <0.00%> (-32.71%)
:arrow_down:

...ker/routing/instanceselector/InstanceSelector.java
100.00% <ø> (ø)

...ava/org/apache/pinot/client/AbstractResultSet.java
66.66% <0.00%> (+9.52%)
:arrow_up:

.../main/java/org/apache/pinot/client/Connection.java
35.55% <0.00%> (-13.29%)
:arrow_down:

...inot/client/JsonAsyncHttpPinotClientTransport.java
10.90% <0.00%> (-51.10%)
:arrow_down:

...not/common/assignment/InstancePartitionsUtils.java
73.80% <ø> (+0.63%)
:arrow_up:

...common/config/tuner/NoOpTableTableConfigTuner.java
100.00% <ø> (ø)

...ot/common/config/tuner/RealTimeAutoIndexTuner.java
100.00% <ø> (ø)

... and 1170 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #6455 (6a23379) into master (1beaab5) will decrease coverage by 1.19%.
The diff coverage is 56.80%.

@@            Coverage Diff             @@
##           master    #6455      +/-   ##
==========================================
- Coverage   66.44%   65.25%   -1.20%
==========================================
  Files        1075     1330     +255
  Lines       54773    64909   +10136
  Branches     8168     9467    +1299
==========================================
+ Hits        36396    42357    +5961
- Misses      15700    19520    +3820
- Partials     2677     3032     +355

Flag
Coverage Δ

unittests
65.25% <56.80%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...e/pinot/broker/api/resources/PinotBrokerDebug.java
0.00% <0.00%> (-79.32%)
:arrow_down:

...ot/broker/broker/AllowAllAccessControlFactory.java
71.42% <ø> (-28.58%)
:arrow_down:

.../helix/BrokerUserDefinedMessageHandlerFactory.java
33.96% <0.00%> (-32.71%)
:arrow_down:

...ker/routing/instanceselector/InstanceSelector.java
100.00% <ø> (ø)

...ava/org/apache/pinot/client/AbstractResultSet.java
66.66% <0.00%> (+9.52%)
:arrow_up:

.../main/java/org/apache/pinot/client/Connection.java
35.55% <0.00%> (-13.29%)
:arrow_down:

...inot/client/JsonAsyncHttpPinotClientTransport.java
10.90% <0.00%> (-51.10%)
:arrow_down:

...not/common/assignment/InstancePartitionsUtils.java
73.80% <ø> (+0.63%)
:arrow_up:

...common/config/tuner/NoOpTableTableConfigTuner.java
100.00% <ø> (ø)

...ot/common/config/tuner/RealTimeAutoIndexTuner.java
100.00% <ø> (ø)

... and 1170 more

Continue to review full report at Codecov.

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


panic: runtime error: slice bounds out of range

$ gci -local istio.io -w main.go
panic: runtime error: slice bounds out of range [630:619]

goroutine 1 [running]:
github.com/daixiang0/gci/pkg/gci.processFile(0x7ffd12f2fb49, 0x7, 0x51df20, 0xc00000e010, 0xc00000c060, 0x0, 0x0)
        /home/howardjohn/go/pkg/mod/github.com/daixiang0/gci@v0.0.0-20200727065011-66f1df783cb2/pkg/gci/gci.go:288 +0xc3d
github.com/daixiang0/gci/pkg/gci.ProcessFile(...)
        /home/howardjohn/go/pkg/mod/github.com/daixiang0/gci@v0.0.0-20200727065011-66f1df783cb2/pkg/gci/gci.go:261
main.main()
        /home/howardjohn/go/pkg/mod/github.com/daixiang0/gci@v0.0.0-20200727065011-66f1df783cb2/main.go:58 +0x237

$ cat main.go
// +build integ
// Copyright Istio Authors
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
//     http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

package telemetry

import (
        "fmt"
        "os"

        "istio.io/istio/pkg/test/framework/resource"
        )

        _ = resource.Cluster
        _ = fmt.Println
        _ = os.Stdout

I'm getting a similar error. It looks like it's in the same code.
https://github.com/daixiang0/gci/blob/v0.2.9/pkg/gci/gci.go#L305 is the culprit.
I get the error on v0.2.7 and v0.2.9
❯❯ gci -w -local "some-local-package" .
panic: runtime error: slice bounds out of range [154:143]

goroutine 1 [running]:
github.com/daixiang0/gci/pkg/gci.processFile({0xc00047f460, 0xc}, {0x125f200, 0xc0000aa008}, 0xc0003a9360)
        $HOME/go/pkg/mod/github.com/daixiang0/gci@v0.2.7/pkg/gci/gci.go:315 +0x9cd
github.com/daixiang0/gci/pkg/gci.visitFile.func1({0xc00047f460, 0xc}, {0x1266c70, 0xc00018c4e0}, {0x0, 0x0})
        $HOME/go/pkg/mod/github.com/daixiang0/gci@v0.2.7/pkg/gci/gci.go:271 +0x92
path/filepath.walk({0xc00047f460, 0xc}, {0x1266c70, 0xc00018c4e0}, 0xc000316c10)
        /usr/local/opt/go/libexec/src/path/filepath/path.go:418 +0x125
path/filepath.walk({0x7ffeefbff68a, 0x1}, {0x1266c70, 0xc000365040}, 0xc000316c10)
        /usr/local/opt/go/libexec/src/path/filepath/path.go:442 +0x28f
path/filepath.Walk({0x7ffeefbff68a, 0x1}, 0xc000316c10)
        /usr/local/opt/go/libexec/src/path/filepath/path.go:505 +0x6c
github.com/daixiang0/gci/pkg/gci.WalkDir({0x7ffeefbff68a, 0x1}, 0x0)
        $HOME/go/pkg/mod/github.com/daixiang0/gci@v0.2.7/pkg/gci/gci.go:278 +0x38
main.main()
        $HOME/go/pkg/mod/github.com/daixiang0/gci@v0.2.7/main.go:57 +0x178

I find the file doing it, it's a file that is used to just import development tooling. It doesn't end in a new line.
// +build tools

package build

import (
	_ "github.com/golangci/golangci-lint/cmd/golangci-lint"
	_ "gotest.tools/gotestsum"
)

Therefore the assumption that the import end flag is followed by a new line will cause an off by one error.

Removing the new line after the ) at https://github.com/scottgreenup/gci/blob/v0.2.9/pkg/gci/gci.go#L30 worked for me locally on a pretty large project.

This is all pre v0.3.0 though.

Now do not paic.


fix(Version): add version .rc file

:tada: This PR is included in version 6.2.5-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.2.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


 This is both expensive and time consuming.
What do we think about introducing a new variable pems_clearinghouse_start_date which can be set to, e.g., 2023-01-01 for the time being? We can filter our base models according to this date, and once the dust settles a bit, move it back to the actual start of the historical PeMS data.

@ian-r-rose I agree with your approach and like the idea. The proposed start date should be fine for where we are at in the project and it gives us a full year of data which I believe is adequate for the time being to perform QA/QC. There may be other anomalies farther back in time but these will be easier to identify once we have some visualization and reporting tools.

@kengodleskidot would you be willing to take this on?


Dependency on safe-buffer breaks browser builds

Describe the bug
The @near-wallet-selector/core dependency on near-api-js and safe-buffer breaks builds for the browser.
Output errors such as this:
✘ [ERROR] Could not resolve "buffer"

    node_modules/safe-buffer/index.js:2:21:
      2 │ var buffer = require('buffer')
        ╵                      ~~~~~~~~

  The package "buffer" wasn't found on the file system but is built into node.
  Are you trying to bundle for node? You can use "platform: 'node'" to do
  that, which will remove this error.

Not trying to build for Node here, so that doesn't help.
To Reproduce
Steps to reproduce the behavior:
Using a tool like esbuild or estrella, set platform to "browser" (default value)
await build({
  bundle: true,
  entry: `${__dirname  }/src/scripts/index.tsx`,
  outdir: `${__dirname }/dist/static/scripts`,
  minify: true,
  format: 'esm',
  target: 'es2017',
  platform: 'browser'
});

Expected behavior
Since near-wallet-selector is meant for browser web apps, it shouldn't have dependency on Node libraries. Builds for the browser should work out-of-the-box without any workarounds.
Additional context
I'm also happy to hear any suggestions on how to build for the browser today.

Hi, @BobbyRadford thank you for raising this issue.
Buffer is not used directly by @near-wallet-selector/core but it's used by near-api-js.
In the modern bundlers node native libraries are not added in the browser-based projects by default so you will need to provide buffer as a polyfill.
Have you tried installing buffer as a dependency or a devDependency? ( in esbuild the error goes away if you install it.)

Yeah, it makes sense to use only "browser-compatible" libraries/modules but at the moment buffer is used by near-api-js a lot.
From my investigation so far I found out that buffer and process are being used by near-api-js so you must provide them as polyfills in your dApp.
Also just installing the buffer or process package in a dApp created with esbuild does not completely fix the issue, i.e installing the @near-wallet-selector/my-near-wallet and trying to sign in from the modal would show an error:
"Buffer is not defined"
Since I am not very familiar with esbuild the easiest way I could do to fix this issue was by:

Install buffer and process as dependencies

Create a polyfills.ts in your project and add:

import * as process from "process";
import { Buffer } from "buffer";
Object.assign(self, {
  process,
  global: self,
  Buffer,
});

Import polyfills.ts in your main ts/tsx file.

This is a simple demo (copy of wallet-selector/examples/react with esbuild):
https://github.com/kujtimprenkuSQA/guest-book-esbuild
This is the commit where I added buffer and process as polyfills:
https://github.com/kujtimprenkuSQA/guest-book-esbuild/commit/98928f9b31b5f27815b6c13ccb33a870825143fb
I am not very familiar with this bundler though so forgive my lack of  following the "best practices" in this case.

Hi @BobbyRadford and thanks for raising this issue! I will close it for now if there are no additional questions. Feel free to reopen it.


Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform

There is an improvement notice in Chrome developer tools:
Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform
A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced.To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.Note that for performance reasons, only the first access to one of the properties is shown.AFFECTED RESOURCES1 source
bootstrap-native.min.js:1

github lag duplicate #437


Full Librispeech recipe

Besides working on the PR #67 and #85, I'll add a full Librispeech recipe, which will support selecting the subsets, e.g. train-clean-100, train-clean-360, dev-clean, and so on.
The full Librspeech recipe will be ready before Oct. 15  @pzelasko @danpovey @songmeixu @qindazhu

Fantastic!! Many thanks! We may create example scripts with k2 based on your recipe.

It's merged, I extended the example notebook to include a DataLoader and make sure that it works without issues (PR #95, will merge after Dan's review)


Divide and Conquer probably

Lessen the strain on analyze-ratings.py to decrease its processing time

There was some problem with the invite you sent me. Send it again.

Here is the document which details the category cross-correlation algorithm (a kind-of generic-baseline K-means clustering): Category cross-correlation.pdf


how can i add aesthetic loss and clip loss during training to increase the aesthetic score and clip score of the generated imgs

how can i add aesthetic loss and clip loss to increase the aesthetic score and clip score of the generated imgs

Do you want to try to import RL methods, like DPO, into training Diffusion models?

We have included K=1 support in AlignProp, which will significantly reduce the memory usage. I would be happy to help with the integration if needed.
(https://github.com/mihirp1998/AlignProp/blob/a831a5fb3a644817957f334f4dd2d8971e3c550b/config/align_prop.py#L129)


HBASE-22891 Use HBaseQA in HBase-PreCommit-GitHub-PR job

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
64
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

0
shelldocs
1
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

+1
asflicense
17
The patch does not generate ASF License warnings.

137

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-518/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/518

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 9995490abf8e 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-518/out/precommit/personality/provided.sh

git revision
master / 84ee378df1

Max. process+thread count
47 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-518/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) shellcheck=0.4.4

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
101
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

+1
asflicense
18
The patch does not generate ASF License warnings.

184

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-518/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/518

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 824909ec7ace 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-518/out/precommit/personality/provided.sh

git revision
master / b329bf0a57

Max. process+thread count
46 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-518/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) shellcheck=0.4.4

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
223
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

+1
asflicense
18
The patch does not generate ASF License warnings.

302

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-518/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/518

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 28f6a3f691ca 4.4.0-154-generic #181-Ubuntu SMP Tue Jun 25 05:29:03 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-518/out/precommit/personality/provided.sh

git revision
master / 4268774de1

Max. process+thread count
51 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-518/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) shellcheck=0.4.4

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


skip immediate revalidation when initalData is provided

This fixes #194.
I wasn't sure if this should be set via another option or not but if so let me know and I can update.

@addstar34 do you think this PR could introduce a regression i described in #230 ?

After upgrading, if I set the initialData options, SWR does not send the request.
I'm not using with SSR. It is a CRA application.


Added ability to switch languages

@skaterdav85 yo dude. This one is same as PR #42 updated for recent changes in master.
This isn't really a breaking change, just makes the whole language switching/adding new languages much easier. No more custom language builds, just include the additional language files that you want.

Btw once this one is merged I can hopefully work on browserify stuff.

awesome! can you update the README for this?


Doesn't update if made to change width without re-rendering

Here's a codesandbox demo:
https://codesandbox.io/s/react-textarea-autosize-bug-2hc6yv
If you press the "Toggle sidebar" button, then the textarea gets squished by the expanding sidebar and fails to become taller to account for the further-wrapped text.
A fix would be to use ResizeObserver specifically to track changes to the element's width. ResizeObservers have had support on all popular browsers since 2020.
The window resize listener at https://github.com/Andarist/react-textarea-autosize/blob/896596a5a9ab02d566f528442758a43633843481/src/index.tsx#L101 would be unnecessary if a useLayoutEffect call like this was present there instead which set up the ResizeObserver:
React.useLayoutEffect(() => {
  // monitor for changes to width
  if (globalThis.ResizeObserver) {
    let knownWidth = libRef.current.clientWidth;
    const ro = new ResizeObserver((entries) => {
      const newWidth = entries[entries.length-1].contentRect.width;
      if (newWidth !== knownWidth) {
        knownWidth = newWidth;
        resizeTextarea();
      }
    });
    ro.observe(libRef.current);
    return () => {
      ro.disconnect();
    };
  }
}, []);

Additionally, even though issue https://github.com/Andarist/react-textarea-autosize/issues/337 isn't really this library's fault, using a ResizeObserver would work around that issue as it would get triggered as soon as the textarea is inserted into the document.

@Andarist I am also facing a similar issue; once its width changes, it doesn't adjust the rows accordingly. When can we expect this to be fixed, or would you like me to raise a pull request to address it?

A PR is always appreciated but I can't promise that I will actually have time to review this. The fact that we don't quite have automated tests here doesn't help 😢

Need this update

Ended up forcing rerender on focus, but still need this to be automatic


Request: Remove the some type restrictions on Computed Properties syntax.

TypeScript Version:  2.4.0
Code
In ES6 Computed Properties syntax, we are allowed to use any type as the property of an object. e.g.:
const s = Symbol()

// `[ts] A computed property name must be of type 'string', 'number', 'symbol', or 'any'.`
const awesomeObj = {
    [() => {}]: 'function',
    [null]: 'null',
    [undefined]: 'undefined',
    [s]: 'symbol',
}

console.log(Object.keys(awesomeObj)) // ["() => {}", "null", "undefined"]

Above are valid usages, but TS tips me: [ts] A computed property name must be of type 'string', 'number', 'symbol', or 'any'.
Another non-sense restriction is we can't set symbols or any other types exclude string and number as object's indexes while we defining object interface.
--del--
// `An index signature parameter type must be 'string' or 'number'.`
interface IAwesomeObj {
    [key: any]: number
}

--del--
--updated--
// `An index signature parameter type must be 'string' or 'number'.`
interface IAwesomeObj {
    [key: Symbol]: number
}

--updated--
The key will eventually be string or symbol, but TS should allow us defining any types as the properties.

In redux-actions, there is a usage like:
const noop = createAction('INCREMENT');

const reducer = handleActions({
  [noop]: (state, action) => ({
    counter: state.counter + action.payload
  })
}, { counter: 0 });

noop is a function, and its toString mehtod will return string 'noop', all seems right but in TS we get errors.
To workaround, I have to:
const reducer = handleActions({
  [noop as any]: (state, action) => ({
    counter: state.counter + action.payload
  })
}, { counter: 0 });

Hope a TypeScript official solution.

They should all be invalid because they are pointlessly bad code that offers no benefits.
Each one of those values that you rightly point out are tolerated as computed keys in JavaScript are, with the exception of symbols, converted into Strings.

Your example from the second post should work though, and I'm pretty sure it used to

@aluanhaddad I update the second example, It should support Sybmol keys

@aluanhaddad In redux-actions, we use the created action function as the key, and this action function implements that it's toString method return its Action type, so actually this action function refers to an string.

In redux-actions, we use the created action function as the key, and this action function implements that it's toString method return its Action type, so actually this action function refers to an string.

That sort of magical implicit coercion is exactly why JavaScript has a bad name for itself.  That sort of bad coding practice is exactly what TypeScript is for.  Why try to fight it?
The Symbols as a index type is a duplicate of #1863

@kitsonk I agree with you that it's a discouraged tricky in a way. But, in redux-actions usage, I think it's naturally reusing the action function itself as its reducer identification. Maybe a modification can be done to eliminate smell by making the action function takes its Action Type as a property. But someway somehow there always be someone would love to employ implicit toString method calling in Computed Property syntax, because of the javascript just has the magic.

@kitsonk Thx for your opinions and I get many thoughts. Just in that implements toString is under controlled, altering on function's prototype doesn't affect the behaviour of that usage, am I'm missed some other situation?

You can already do the "indexable function" type with the existing affordances:
type FWithString<T extends Function> = T & string;

function createAction<T extends string>(name: T): FWithString<() => {type: T}> {
  const a = () => ({ type: name });
  a.toString = () => name;
  return a as any as FWithString<() => {type: T}>;
}

const noop = createAction('NOOP');

// You can call it
const a = noop();

// You can also index with it
const handler = {
  [noop]: 123
}

Just to add a little bit to @kitsonk's point about it being poor coding practice, there are libraries and even ECMAScript feature implementations like Array.isArray that rely on .toString behavior.  If we were talking about Arrays for example, this would break.

Duplicate of https://github.com/Microsoft/TypeScript/issues/5579

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


test-branch/execute-job/comment-from-wrong-user-on-pr/a5b8e74d-1ec0-4ff4-ae7a-714976dd2636

PR for testing dca6765c92dcb6678d1d657039ca29d79c1c8749

/canonical/self-hosted-runners/run-workflows dca6765c92dcb6678d1d657039ca29d79c1c8749


Add new classes to describe different voltage levels of the energy grid

Description of the issue
From #1828 and oeo-dev 89
It should be possible to differentiate the different voltage levels:

High Voltage
Low Voltage

And the type of network system:

Transmission system
Distribution System

Connecting terms would be:

TSO
DSO

Ideas of solution
Part of #1828
Workflow checklist

[x] I discussed the issue with someone else than me before working on a solution
[x] I already read the latest version of the workflow for this repository
[x] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

And the type of network system:

Transmission system
Distribution System

These should become subclasses of power system. In oeo-dev 89 we had the idea of adding a power distribution function and a power transmission function to distinguish the power systems by their purpose.
Add transmission network and distribution network as alternative labels?!

Comment on https://github.com/OpenEnergyPlatform/ontology/issues/1828#issue-2198494373 (Anis) and https://github.com/OpenEnergyPlatform/ontology/issues/1828#issuecomment-2422326472 (Madeleine):
The electricity distribution system cannot be a subclass of energy system because it is a part of the power system (subclass of energy system). It is not identical with the power system or with any kind of complete power system.
In Germany, the highest voltage level is the level of the transmission system and it depends if and which  2nd level part of the grid is counted in transmission or in distribution system
Comment on https://github.com/OpenEnergyPlatform/ontology/issues/1828#issuecomment-2031559751 (Mirjam)
This comment refers to the question if energy distribution system component is equivalent to grid component.

electricity distribution system component is more specific because the electricity distribution system is not the whole grid (I suppose grid is equivalent to power system or to transmission + distribution system together as parts of the power system?)
Since cables have been mentioned; in my opinion, it is problematic to have electrical devic-es/equipment as subclass of grid component. E.g. cable cannot be a subclass of it. Cables exist independently from grid components.
And, grid component is more a role than a class so at least a further subclassing will always be problematic. It is more like a grid (or power system?) has a relation to devices/equipment (e.g. cables) which are their components: "grid" "has component" "cable"

Comments on https://github.com/OpenEnergyPlatform/ontology/issues/1960#issue-2628692551 (Ludwig):
I think we should at least introduce the terminology used in Germany, defined by DIN norms (accord-ing to https://de.wikipedia.org/wiki/Hochspannung)
Note that other countries may have a different mapping of voltage levels to network levels (transmis-sion system TS, distribution system DS) (I do not know if the term "network level" is correct as the generic term for TS and DS, but "network" is alternatively used instead of system in the various terms we have so far.)
Voltage levels Germany:
•	low voltage (230/400 V up to 1kV)
•	medium voltage (10 kV up to 35 kV)
•	high voltage (110 kV)
•	extra high voltage (220 kV, 380 kV)
TS is extra high, the others are DS (typically)
E.g. USA: there is an ultra high voltage level beyond 1 MV
Comment on https://github.com/OpenEnergyPlatform/ontology/issues/1960#issuecomment-2451792877 (Mirjam):
Definition of power system: "A power system is an energy system covering the generation, transpor-tation, distribution and consumption of electrical energy."
Thus, TS and DS both cannot be subclasses since they do not include generation, consumption, and distribution respectively transport.

Comment on #1828 (comment) (@koubaa-hmc) and #1828 (comment) (@madbkr):
The electricity distribution system cannot be a subclass of energy system because it is a part of the power system (subclass of energy system). It is not identical with the power system or with any kind of complete power system.
In Germany, the highest voltage level is the level of the transmission system and it depends if and which 2nd level part of the grid is counted in transmission or in distribution system

Thanks for the clarification of the part of relation @UStucky I also very much agree that there should be a grid component role. Based on your comments, the ontological model could look like this (not yet taking into accout the voltage levels):

Adding this here from issue #1975, since it's also relevant to this issue: Here's some information regarding Germany/US voltage level differences.
Germany (source: https://www.smard.de/page/en/wiki-article/5884/214026)

Voltage
System

Ultra High Voltage
n/a
n/a

Extra High Voltage
220kV to 380kV
transmission

High Voltage
110kV
interregional distribution

Medium Voltage
10kV to 30kV
regional distribution

Low Voltage
400V
local distribution

USA (source: https://www.generatorsource.com/Articles/Generator-Info/High-Medium-and-Low-Voltage-Differences.aspx and my personal experience working as a power engineer for US utility companies)

Voltage
System

Ultra High Voltage
> 765kV
transmission

Extra High Voltage
345kV to 765kV
transmission

High Voltage
115kV to 230kV
transmission

Medium Voltage
2.4kV to 69kV
69kV is transmission. < 69kV is distribution.

Low Voltage
240 to 600V
distribution

The 400 V low voltage are for all three phases (Drehstrom) between any two conductors; 230 V is from any conductor out of the three to ground wire

The grid component role looks good. Thanks @stap-m
The roles transmission grid role and distribution grid role
with subclasses interregional distribution, regional distribution and local distribution cover all system roles.
The artificial object can be the existing electricity grid OEO_00000143. (alt label: Stromnetz, electricity network)
voltage level are very useful, thanks @amanda-wein
What relation is this? And are the level classes or instances?
And I am not sure how to define the voltage.
As far as I remember some are "lists" like "220 kV" or "380 kV".
And some are ranges like "10kV to 30kV".
Can someone clarify this?
The related terms cable or  electricity cable must be considered as well. @UStucky
With underground cable (Erdkabel) and overhead cable (Freileitung).
And the related topic substation. (Trafostation)
That are quite a lot of new terms and needed definitions. 👀

I would say that voltage level is the class, the levels explicitely named so far are instances of it; German voltage levels are different instances from US voltage levels. An instance of a distribution system has 1 to n voltage levels; dto. an instance of transmission system. DS and TS in US are different instances from German DS and TS respectively.
As for the question of detail - it depends on how the domain OEO describes is defined; I think the Common INformation Model (CIM) is a good example and can guide an ontologization of the technical stuff of power grids (and other stuff, too); Link e.g.: https://zepben.github.io/evolve/docs/cim/cim100; I have some Enterprise-Architect models from a few years ago.
If we take a look at the class VoltageLevel in CIM we can find that in general the values are ranges, described by their limiting voltages (which does not exclude single valued VLs).

and for each of those classes, specify the precise voltages and the system (electricity transmission system or electricity distribution system) that it falls under? That does get a bit complicated with US medium voltage being both transmission and distribution, though.

We want to implement the grid component role, so a grid level has transmission grid role and/or distribution grid role.
I think we should start at the top concepts:
OEO:power system A power system is an energy system covering the generation, transportation, distribution and consumption of electrical energy. (DE: Energieversorgung/Elektrisch)
Missing relation to:
OEO:electricity grid An electricity grid is a supply grid that transports and distributes electrical energy / electricity. (DE: Stromnetz)
NEW:
An electricity grid has one ore more grid level: A grid level is part of an electricity grid and is characterized by its voltage level and grid component role and its geographic coverage.
(DE: Netzebene)
NEW:
A voltage level is a characteristic (?) of a grid level. Extend definition
electricity grid has part some electricity grid component: An electricity grid component is a grid component that is part of an electricity grid.

link / OEO:power line A power line is a grid component link that is an uninterrupted transmission system between two nodes in an electricity grid. (DE: Stromleitung)
OEO:switchyard: A switchyard is an electricity grid component that connects different levels of voltage (@amanda-wein I would follow your definition) #1975
OEO:transformer: A transformer is an electricity grid component that passively transfers electrical energy from one electrical circuit to another.
NEW: substation has part some transformer ? (similar to OEO:power plant
OEO:power plant A power plant is an energy transformation unit consisting of power generating units and a grid component that feeds electric energy into an electric grid.
OEO:energy storage unit An energy storage unit is a grid component that stores energy.
OEO:grid node A grid node is a grid component of a supply grid where two or more links meet.
Some connection to the demand/consumption: OEO:energy demand sector An energy demand sector is a sector that covers energy consumers. The grid connection of the consumer.

--->
I think we should start at the top concepts:
OEO:power system A power system is an energy system covering the generation, transportation, distribution and consumption of electrical energy. (DE: Energieversorgung/Elektrisch)
Missing relation to:
OEO:electricity grid An electricity grid is a supply grid that transports and distributes electrical energy / electricity. (DE: Stromnetz)
<---
So, the electricity grid can only be the TS and DS part of the power system- as far as it is specified now in this discussion.
And what about "grid level"? That is a new term (regarding this discussion) - it is translated to "Spannungsebene", but that is (should be?) the voltage level. Is there a differnece? What does the geographic coverage (?) has to do with it? An electric system is rarely characterized in terms of any geography (as long as it is not relevant where some part of it is located because someone has to go out to fix something or the like).
If it comes to describing the technical power system/grid or whatever it may be called, I think it is mainly a matter of part-whole and nothing else. When I speak of a grid component, then it is just the collection of the parts of the grid. It is a relation between the grid and the entities that are parts of it. It is the property, predicate, relation, however it is called, of a grid, we can call it grid components, and the real things that are members of the collection are devices, equipment that are components of the grid.

The voltage level could be modelled as quality (physical property) of  grids/systems which may have in addition a role or function of distribution/tansmission (to be specified). Like this, we can decouple the voltage level and the distribution/transmittion role/fuction of a grid.

link / OEO:power line A power line is a grid component link that is an uninterrupted transmission system between two nodes in an electricity grid. (DE: Stromleitung)
.......

As said above, the "grid components" should be classified as artificial objects. For the Arisotelian def this results in something like:
A power line is an artificial object  that is a link in an uninterrupted transmission system between two nodes. We could/should extend the def with a sentence like It has the grid component role./ It is usually used as grid component. / ...
This holds for all grid components.

A question: is the electricity distribution system the same as the electricity distribution grid? Or is the grid part of the system?

NEW:
An electricity grid has one ore more grid level: A grid level is part of an electricity grid and is characterized by its voltage level and grid component role and its geographic coverage.
(DE: Netzebene)

As far as I understand "Netzebenen", they are mainly labels for certain types of grids (with a certain voltage level, in a certain region (DE, AT, CH)), but not actually "part" of the grid. For modelling of the physical stuff they don't play a role, right? Maybe we can add them after clarifying the rest.

OEO:transformer: A transformer is an electricity grid component that passively transfers electrical energy from one electrical circuit to another.

On a slightly different topic, this definition is a bit misleading - a transformer often connects two different electrical circuits, but it doesn't necessarily have to. For a distribution-level transformer that steps down from 12kV/4kV/etc. to 240V, the wires and equipment on either side of that transformer would be considered a single circuit by the system operator. I think something like "A transformer is an electricity grid component that passively transfers electrical energy from one voltage level to another" would be a bit more accurate.

And what about "grid level"? That is a new term (regarding this discussion) - it is translated to "Spannungsebene", but that is (should be?) the voltage level. Is there a differnece? What does the geographic coverage (?) has to do with it? An electric system is rarely characterized in terms of any geography (as long as it is not relevant where some part of it is located because someone has to go out to fix something or the like).

As far as I understand "Netzebenen", they are mainly labels for certain types of grids (with a certain voltage level, in a certain region (DE, AT, CH)), but not actually "part" of the grid. For modelling of the physical stuff they don't play a role, right? Maybe we can add them after clarifying the rest.

I would agree that I don't think geographic coverage has much to do with the definitions of grid levels (Netzebenen). The distinction between transmission and distribution grid levels impacts the responsible parties for maintaining and operating the system (TSO & ISO & RTO for transmission, DSO for distribution), the regulatory environment for the system, and the financial market structure for the system. I suppose geography becomes relevant when you're talking about transmission interconnections between different companies/states/countries, since that impacts regulatory oversight and electricity markets.
But from a standpoint of just the physical stuff that makes up the grid (transformers, cables, switches, etc), the names transmission and distribution don't really matter - the operating voltage level (Spannungsebene) is more relevant than the grid level (Netzebene) its assigned to.

OEO:transformer: A transformer is an electricity grid component that passively transfers electrical energy from one electrical circuit to another.

On a slightly different topic, this definition is a bit misleading - a transformer often connects two different electrical circuits, but it doesn't necessarily have to. For a distribution-level transformer that steps down from 12kV/4kV/etc. to 240V, the wires and equipment on either side of that transformer would be considered a single circuit by the system operator. I think something like "A transformer is an electricity grid component that passively transfers electrical energy from one voltage level to another" would be a bit more accurate.

Regarding transformers:

The definition from CIM:
"An electrical device consisting of  two or more coupled windings, with or without a magnetic core, for introducing mutual coupling between electric circuits. Transformers can be used to control voltage and phase shift (active power flow).
A power transformer may be composed of separate transformer tanks that need not be identical.
A power transformer can be modeled with or without tanks and is intended for use in both balanced and unbalanced representations.   A power transformer typically has two terminals, but may have one (grounding), three or more terminals.
..."
A UML diagram from CIM showing the model "around" PowerTransformer:

And we canot state that a transformer transfers energy from one "voltage level" to another, since these are not (!) voltages, they are related to ranges of voltage values.


Cordova: iOS: autopopulate of Send Funds fields from URI/QR has bug that placeholder remains despite value

autopopulate of Send Funds amount field from request doesn't cause placeholder to disappear despite value present
(relatively minor issue)

Closing as iOS Cordova build deprecated


[New Port Request]

Library name:
sonic
Library description:
Simple library to speed up or slow down speech
Source repository URL:
https://github.com/waywardgeek/sonic

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.

Hope it will be added to vcpkg, please reopen it.

Hope it will be added to vcpkg, please reopen it.

Could you please submit a PR to add this port to vcpkg?


[Docs - Advanced - Async Actions] remove note about fetch

Remove this note: https://redux.js.org/advanced/async-actions#note-on-fetch
Obsolete and irrelevant for redux tutorial.

Thanks!


Bug : Testing with version-12

Old database migration error

Hello @sammish
Fixed this on new update.


Deploy GlusterFS by default, with a prompt

By default we should assume that we are meant to deploy the GlusterFS DaemonSet. However, we should prompt the user whether they want to deploy GlusterFS or not. This prompt should also include a small note as to the firewall requirements on the node for GlusterFS. The -g option should still be retained, with the slight modification that it simply assumes 'yes' and skips the prompt entirely.

Wouldn't having a prompt mechanism break unattended setups?

Possibly, but we have a prompt right now for the case where the script detects both oc and kubectl on the same system. I'm not sure one would want or be able to make an unattended setup for production, and in most automation scenarios I can think of it'd be trivial to do something like echo n | gk-deploy. We could also create a --no-gluster flag to get around this.


Added support for structs.

At the current state adding structs to the code breaks parsing, especially structs with functions which is the only easy way of adding non-material function "libraries" to the code node in UE4, i.e:
struct Functions
{
    float4 SomeLocalFunction(float4 A, float4 B)
    {
        return lerp(A, B, 0.25);
    }
};

void MaterialFunc(
    float4 A,
    float4 B
    out float4 Color)
{
    Functions fun;

    Color = fun.SomeLocalFunction(A, B);
}

If file contains multiple material functions, structs will be added to all of the code nodes.

Thanks! Sorry it took this long - I've manually merged it here with a few minor changes: https://github.com/Phyronnaz/HLSLMaterial/commit/91d4593dde61f9a941dfae6a54a93d5f02f0701a


unable to parse host/domain out of resolved FQDN

try to get a certificate  based on my netcup domain. Unfortunally it fails as found in cert-manager pod log
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: kube-mydomain-net-cert
  namespace: cert-manager
spec:
  commonName: 'kube.mydomain.net'
  secretName: kube-mydomain-net-cert
  dnsNames:
    - 'kube.mydomain.net'
    - '*.kube.mydomain.net'
  issuerRef:
    name: letsencrypt-staging-netcup
    kind: ClusterIssuer

But it will not fullfill the certificate request. I know i have to wat about 10min to propagate, but its still pending also for a day.
I0524 18:35:21.307621       1 dns.go:88] cert-manager/challenges/Present "msg"="presenting DNS01 challenge for domain" "dnsName"="kube.mydomain.net" "domain"="kube.mydomain.net" "resource_kind"="Challenge" "resource_name"="kube-mydomain-net-cert-g47p8-752194941-2691253898" "resource_namespace"="cert-manager" "resource_version"="v1" "type"="DNS-01"  E0524 18:35:21.432257       1 controller.go:166] cert-manager/challenges "msg"="re-queuing item due to error processing" "error"="unable to parse host/domain out of resolved FQDN ('_acme-challenge.kube.mydomain.net.')" "key"="cert-manager/kube-mydomain-net-cert-g47p8-752194941-2691253898"
a query with dig provides the soa entry set to define, wihich domain is authorative
dig @root-dns.netcup.net _acme-challenge.pvekube.tdressler.net. soa txt
;; Warning, extra type option

; <<>> DiG 9.16.1-Ubuntu <<>> @root-dns.netcup.net _acme-challenge.kube.mydomain.net. soa txt
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22304
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 2585cb374e444deff7dc9acf628d289675d83ae79e8368ec (good)
;; QUESTION SECTION:
;_acme-challenge.kube.mydomain.net. IN TXT

;; AUTHORITY SECTION:
mydomain.net. 86400 IN SOA root-dns.netcup.net. dnsadmin.netcup.net.<PHONE_NUMBER> 28800 7200 1209600 86400

subdomain kube doesnt exists, but other providers (like hetzner) are still greating an "_acme-challenge.kube" TXT record in mydomain
looking into the webhook code the mentioned dnsName '_acme-challenge.kube.mydomain.net. matches  the regexp which triggers this message using a regexp tester
Maybe this line below is the problem?
if match != nil {
should be
if match == nil {

I've just got the same issue

@Tommi2Day I switched the condition as mentioned by you and now it seems to work. Atleast a txt record was created. I'm currently waiting for the propagation:
Status:
  Presented:   true
  Processing:  true
  Reason:      Waiting for DNS-01 challenge propagation: DNS record for "..." not yet propagated
  State:       pending
Events:
  Type    Reason     Age   From                     Message
  ----    ------     ----  ----                     -------
  Normal  Started    14m   cert-manager-challenges  Challenge scheduled for processing
  Normal  Presented  14m   cert-manager-challenges  Presented challenge using DNS-01 challenge mechanism

Everything works for me after that change. I made a pull request.

Thanks @Mik4sa for testing and raising the PR. i was not sure if this code line was really the problem as the certmanager log mentioned dns.go.  There was no meanfull logentry in the netcup webhook pod.. Unfortunally i dont have enough  knowledge how to build my own version to check this out.
@aellwein : Can you please check the PR and relase a new version now? Additional maybe its worth to include more logging to the webhook pod to see the processing steps

@Tommi2Day @Mik4sa Thanks for pointing this. You are right, the check for nil should be inverted, it slipped through somehow. I will merge the PR asap.
Regarding pod logs, what exactly would you like to see there?

I've just published a new bugfix release 1.0.3 to ArtifactHub. May take some time until they updated the caches, stay tuned for 1.0.3. And big thanks for testing and using the software!

I can confirm Release 1.0.3 solved the issue for me. THX for the fast response


unpin r-akima

Description

Closes #3563

We need a more recent version of r-akima to be able to get support for Python 3.12 in.

Before you get started

[x] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Any changed dependencies have been added or removed correctly
[x] 🛠 All checks below this pull request were successful

very many thankyous, Saskia :beer:


Write ATS for TG requirement 50

Any possible (i.e. available) combinations of CRS/DataSetIdCode/DataSetIdNamespace/language shall be made available through pre-defined stored queries.

TG Requirements 49 (#5), 50 (#6) and 51 (#7) together specify the use of Stored Queryies to make pre-defined datasets available. Combined these requirements in one ATS.


renamed html renderers

rename:

html-renderer to inline-html-renderer
standalone-html-renderer to html-renderer

fixed in 5aaedf35f880d9e3fb5670657a69743e885e331b


Upgrade underlying Terraform provider to v0.26.0

pulumi-hcp is currently based on v0.24.1, but v0.26.0 is the current release.
The key change we get by this is https://github.com/hashicorp/terraform-provider-hcp/pull/290.

Fixed by #12


Avoid UI conflict between odf-console and odf-multicluster-console using flags

Signed-off-by: Gowtham Shanmugasundaram<EMAIL_ADDRESS>

/approve
/override ci/prow/odf-console-e2e-aws
/lgtm


Are frequent parameter changes dangerous?

Recently, I came across an interesting post which reads

I can't comment much on older Luxtronik versions, but if you would reverse engineer, you would see that the 2.1 Luxtronik has a Micron 1.8V 128MB NAND, which pretty certainly means it's one of those 100k erase count chips, and trust me they do balance the eraseblocks. There is an Atmel ARM-board in the luxtronik. Without going too much into the details my take is that changing a setting once or twice a day isn't going to wear that thing out any time soon, but I wouldn't go excessive on those settings changes.

Similarly, a Finnish post (maybe by the same person) translates to

The little birds sang that Luxtronik has Micron's 128 megabyte 1.8V Nand flash, which based on that voltage is most likely SLC technology and lasts up to 100,000 erase cycles per erase block. I hear that on average there are not fifty writes per erase block per year, so we can get to the point that the luxtronik will never die in terms of the number of writes. Even if you fiddle with its settings several times a day, it won't.
So I think tuning the relays is pointless. That Nand is very durable, something the Germans have done right.

Now I am wondering what "I wouldn't go excessive" really means.
I tried to make up some numbers. The first thing I don't know is the size of the erase blocks. In what follows, I use 128kb, but I might be totally wrong. Maybe we can use the featurebug and get this information via ssh? If we have 100k erase cycles per erase block, this means that we have 100M "write actions" (each one writing one erase block).
The next thing that we need to know is how many periodically occurring write actions we have.

Every two hours, the controller writes the DTA file NewProc (size 350 kb). [This can be seen by looking on the time stamp, since this file is served by the web server.] This means 3 write actions + file system overhead.
For each parameter change, the file appl_param2 is removed, appl_param1 is moved to appl_param2 and appl_param1 is rewritten. [Again, these files are served by the the server.] It is not clear to me, how many write actions this needs (in particular, the file system overhead again).
Every two hours, there is a parameter update (related to Heizgrenze), maybe only in the heating period?

Is there any idea how to estimate the file system overhead? Would it help to know the file system?
I think there are no other frequently occurring write actions. I think we can safely ignore firmware updates and other stuff which only happens now and then.
So, let us assume that each DTA file write takes 5 write action and each parameter change takes 3 write actions. Crunching some numbers, I get the following life time estimates:
without any parameter changes: 2851.9 years
1 parameter change per hour:   1629.7 years
10 parameter change per hour:   335.5 years
1 parameter change per minute:   62.0 years
1 parameter change per second:    1.1 years

These numbers should be taken with a huge bag of salt (as I do not have any clue what is happening on the NAND level). However, the lifetime of 2850 years fits nicely with the 50 erase cycles per block per year from above.
If these numbers are roughly correct, writing a parameter each second will kill your heat pump controller within one year. Moreover, one should bear in mind that these numbers could easily be wrong by one or two orders of magnitude. In this case, even 1-2 parameter changes per hour could be dangerous in the long term.
Does anybody have some ideas how to check/validate/improve these numbers?

I just asked my heat pump:
# ubinfo /dev/ubi0
ubi0:
Volumes count:                           6
Logical eraseblock size:                 129024
Total amount of logical eraseblocks:     1024 (132120576 bytes, 126.0 MiB)
Amount of available logical eraseblocks: 62 (7999488 bytes, 7.6 MiB)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  10
Current maximum erase counter value:     179
Minimum input/output unit size:          2048 bytes
Character device major/minor:            253:0
Present volumes:                         0, 1, 2, 3, 4, 5

The erase block size is really 128kb. If I further interpret this numbers correctly, I have (at least) one erase block with 179 erases, the others have lower counts. My heat pump is now almost three years old, again the numbers align well with the above posts. Since October 2023, I was changing parameters quite often (50-100 times per day).
At the time of the last boot (229 days ago), the counters were differently:
# dmesg | grep "NAND device" -A 75
NAND device: Manufacturer ID: 0xc8, Chip ID: 0x61 (Unknown ESMT NAND 128MiB 1,8V 8-bit)
Scanning device for bad blocks
1 cmdlinepart partitions found on MTD device atmel_nand
Creating 1 MTD partitions on "atmel_nand":
0x000000000000-0x000008000000 : "UBI"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd0 to ubi0
UBI: MTD device name:            "UBI"
UBI: MTD device size:            128 MiB
UBI: number of good PEBs:        1024
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     6
UBI: available PEBs:             62
UBI: total number of reserved PEBs: 962
UBI: number of PEBs reserved for bad PEB handling: 10
UBI: max/mean erase counter: 117/91
UBI: image sequence number: 0
[...]

Great question. I asked me the same in the past.
So I'm very interested.

I read a little bit about the file system UBIFS, which is at work on the heat pump. I realized, that I have a misconception in my first post: On the NAND memory, the data is written in chunks of 2048 bytes (a "page"). An erase block has to be erased, if all pages in it are written. Hence, the situation should be a little bit better than the estimates in my first post, since the 9 kB of appl_param1 can be written in 5 pages (+ file system overhead) and not on a full erase block.
However, I still think that one should not attempt to change parameters every second. If one limits oneself to one change per minute, one should be safe, but I will offer no guarantees...

Do you think we should add a default throttle that prevents high frequent writes (but can be overridden If a user wants to and is aware of the shortening of the heatpumps lifespan)?

I am not sure. I can imagine that the situation is a little bit better than in my rough calculations, and then the frequent writes should not be a problem. If they really are a problem, then this is rather a bug in the Luxtronik controller itself and should be fixed by the firmware.
I would vote for adding a warning to the README (maybe including a link to this issue).


[New Issue] FranceConnect can get the User's Infomation

Scenario : FranceConnect requests Authorization
Given FranceConnect has sent a valid client_id attribute and a state attribute when calling the /authorize url
When The Aidant has entered valid User information
Then  Aidant connect returns a code along with the state parameter
Scenario : FranceConnect requests Token
Given AidantConnect has Authorized a FC connection
When FranceConnect has sent valid attributes when calling the /token url
Then  Aidant connect returns  token along with a token_id object
Scenario : FranceConnect requests UserInfo
Given AidantConnect has given a token to FC
When FranceConnect has sent valid attributes when calling the /user_info url
Then  Aidant connect returns  formated user information

Information given tp FC to create AidantConnect as an Identity Provider on the integration plateform

Titre: AidantConnect
Authorization URL : http://localhost:8000/authorize
Token URL:  http://localhost:8000/token
UserInfo URL:  http://localhost:8000/userinfo
Status URL: http://localhost:8000/status


+1 470 NPA XXXX

Country/region affected (e.g., "US"): US/Atlanta
Example number(s) affected ("+1<PHONE_NUMBER>"): +1 470 NPA-XXXX
The phone number range(s) to which the issue applies ("+1 555 555-XXXX"):+1 470 NPA-XXXX
The type of the number(s) ("fixed-line", "mobile", "short code", etc.):
The cost, if applicable ("toll-free", "premium rate", "shared cost"):
Supporting evidence (for example, national numbering plan, announcement from mobile carrier, news article): http://www.allareacodes.com/470

Duplicate of #1527.


Perturbation methods should modify normalized values

Modify perturbation methods to only modify the normalized values in Parameters.

A modification may not be necessary if #24 is implemented correctly.


Phrasing in INSTEAD OF

In the explanation for "INSTEAD OF" the following appears: "You can't define INSTEAD OF triggers on updatable views that use WITH CHECK OPTION. SQL Server Doing so results in an error when an INSTEAD OF trigger is added to an updatable view WITH CHECK OPTION specified."
It looks to me that "SQL Server" should not be there, and it should be written as: "... on updatable views that use WITH CHECK OPTION.

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

ID: 2d8add50-414a-a033-6fc0-84de1c7735f2
Version Independent ID: 8f2f3149-7035-b3d4-6f09-a6eadd015e24
Content: CREATE TRIGGER (Transact-SQL) - SQL Server
Content Source: docs/t-sql/statements/create-trigger-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@luis-flores -- Luis, thank you for your feedback.  I am looking into this article.

Thank you for your feedback.  I have updated the documentation and it should be live by tomorrow.


Error when overwriting method

I just added this to the sluggable parameters
'method' => function ($string, $separator) {
    return strtolower(preg_replace('/[^a-z]+/i', $separator, $string));
},

But it throws me this exception : Constant expression contains invalid operations
Any idea?

What version of PHP?

PHP 7

Don't think this is related to sluggable, since that error relates to constants. (I just googled this: http://www.exakat.io/prepare-for-php-7-error-messages-part-2/).
Maybe something further up your class?

Closed for lack of response.


Add dice roll

@mcthomas Thomas, this is a cool service, but it is not a console service. With this approach you can extract any script from any service from the internet and execute it locally.
It should be something like this:
curl roll.the.dice

Ah, that makes sense, thank you for your comment!  Admittedly, I'm just learning and I don't know how to host something like that, but if I manage to, I will submit another pull request.

Please write if you need any help


 is ignored when html-minify

Hello @nuxtjs
I found out that  will be ignored while html-minify works. The spaces in the nuxt-link remain the same. How can I fix this

@NguyenThanh1995 Could you provide a reproduction using https://template.nuxtjs.org ? 🙏

I create a new project with default options using yarn create-nuxt-app and the option build.html.minify is suggested on the nuxtjs homepage.  it does not have any other libraries.  If you include spaces in  it will not be removed by minify html even in production.

@NguyenThanh1995 Would you please create a reproduction? I do not understand the issue from your description.


Disabled backButton

Hi there,
Is there a way to disable the back button completely all I can find is this backTitle: null
Thanks

If you don't want anything on the left side at all you could overwrite the header.left property to erase it. Or did you want to disable it but keep it visible?

Hi,
Thanks for the answer. Could you show me how you do it please ?
For now I reset the router which is not a good solution ...
const resetAction = NavigationActions.reset({
  index: 0,
  actions: [
    NavigationActions.navigate({ routeName: 'Proteges'})
  ]
});

Yes I agree with @joemckie, the fix here is to override header.left

@ThomsCass
new StackNavigator({
   ...
}, {
  navigationOptions: {
    header: {
      left: null
    }
  }
}

Off the top of my head but should work

StackNavigator is a function, not a class 😄

Oh yeah you're right, I just had to write it like that cause of my eslint

Thanks @joemckie, header: { left: null} worked for me.

@MrHubble Click on the Android entity keys to return to the above can still return. And can not really be disabled.

Set headerLeft: null for navigationOptions of your screen to remove left item in navigation bar.

Any suggestion for using DrawerNavigator!, as we make  headerLeft: null, React Component used in Drawer in headerLeft will be gone.


miscellaneous backend fixes

- Summary

- Test plan

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Deploy preview for netlify-cms-www ready!
Built with commit 594f313cfc30d9a5271aa93d593b71a5607604f9
https://deploy-preview-1568--netlify-cms-www.netlify.com

Deploy preview for cms-demo ready!
Built with commit 594f313cfc30d9a5271aa93d593b71a5607604f9
https://deploy-preview-1568--cms-demo.netlify.com

@erquhart Updated!


bool compare: add Zero and Empty

2 blocks of commits:

Refactoring to prepare the next block

gen: move assertion sorter to a function so it could be reused
bool_compare: use variables in generator
bool_compare: use predicting order for tests
bool_compare: refactor tests to easily add use cases

Add zero and empty detection to bool-compare Fixes https://github.com/Antonboom/testifylint/issues/106

I can split the PR into 2-3 PRs if you prefer

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.793%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2025

Relevant Lines:
2159

💛  - Coveralls

@Antonboom I closed #106
So closing this PR would be logic.
But I made refactoring in the tests that I think that could be interesting to keep.
So everything except the last commit.
Would you agree me to open another PR about the refactoring only?

https://github.com/Antonboom/testifylint/pull/121#issuecomment-2166625063

was opened, let's close this one


[beta][UX] Change the image to open in new tab

Nest an Anchor Element within a Paragraph
http://beta.freecodecamp.com/en/challenges/basic-html-and-html5/nest-an-anchor-element-within-a-paragraph
The image in the instruction panel opens on the same tab.
To change the destination of the link add target="_blank" to the anchor tag.

Mind if I pick this up?


New package: Ripple v1.0.1

Registering package: Ripple
Repository: https://github.com/WiredBrains-Lab/Ripple.jl
Created by: @azraq27
Version: v1.0.1
Commit: 14cb8f11644e9e8a4a01937ead7181edee355005
Reviewed by: @azraq27
Reference: https://github.com/WiredBrains-Lab/Ripple.jl/issues/1#issuecomment-1747804263
Description: Julia Pkg providing utilities for working with the Ripple electrophysiology recording system

The proposed name "Ripple" is similar to "Stipple", but I don't think those names will be confused, and the Package is meant to provide methods to support products with the brand name "Ripple".

Yes, sorry. In the time since I originally submitted the first version, I've made several additions and bugfixes. I didn't realize this hadn't been merged yet. Is it waiting on something?

Your comment https://github.com/JuliaRegistries/General/pull/92792#issuecomment-1749592609 (and now these newer comments as well) don't contain the noblock tag and thus block automerge.
I do not know how well the registry handles two "new package" PRs, so I guess the cleanest thing would be to abandon this one and instead focus on #93103.