Fixed #30416 -- Restore terminal state when reloading.

Runserver's reloader only ensures that ECHO is on currently.
In acbb911ad5 (#15880) special handling of SIGTTOU was added, but this
can be avoided by checking if stdin is a tty.
https://code.djangoproject.com/ticket/30416#ticket

/cc @kmtracey (via https://github.com/django/django/commit/f5b22ed9977d19bc35ed02bcb965c0e0f48ef127)

The failing test (utils_tests.test_autoreload.StartDjangoTests.test_echo_on_called) is only a mocking one - easy to adjust, but could test it for real maybe then.

I would very much like to get rid of ensure_echo_on, as I've got no real clue how (or why) it works. As mentioned in the ticket, as you clearly know a lot about this, could you leave some steps to reproduce the issue?
I'm slightly nervous about removing it as it's been there for a while, so manual testing of this is needed.

Closing as per ticket: https://code.djangoproject.com/ticket/30416#comment:5

@orf see https://code.djangoproject.com/ticket/30416#comment:6

@blueyed Hi! I'm doing some PR cleanup, would you have time to update this PR with latest main? Thank you!


Add Integration Tests and whats new for RT improvements - [Merge last]

This adds a what's new section with the changes in the other PRs.
Also adds an Integration Test suite that tests all classification / exception routing behaviors.
This relies on all other PRs being merged, won't even compile before that.
Since all the other PRs are related, I chose this strategy in order to avoid conflicts and still keep the PRs small.
PLMK if there's anything else needed.
Thanks!

I'll adjust this PR later today to reflect what will get into 2.8.3.

These are some minor polishing to the docs and a what's new entry with the new features. PLMK if there's anything to change, or anything else to do for this release.
I removed the Integration Test suite since it was mostly to test blocking retries and combinations with other exception classification-based routing. I don't think they'd add much value without it. I can submit them again once we implement the blocking retries feature.
Thanks

...and cherry-picked


Improved general project formatting and readability + Lombok

Added Lombok dependency
Migrated some getters and constructors to Lombok.
Improved general code formatting
Improved HandshakePacketHandler formatting and readability

Not a great fan of adding an extra dependency plus an annotation processor for something seemingly unnecessary as not much boilerplate code is saved.
Also not a great fan of adding one extra line between the last method and the end of the class and call it "improved formatting.
Exception handlers sound like a good idea, but imo the implementation is flawed at best. If a system like that should be implemented, I think abstraction is the way to go, not one class without one super class. That could be done super easy, e.g. one abstract class called "ExceptionHandler", implementing those methods with the parameters, and then storing them in a Map with the exception as the key and the corresponding handler as the value. I do not see though that that is needed in the amount of exceptions we are currently dealing with; it's just not necessary.

Not a great fan of adding an extra dependency plus an annotation processor for something seemingly unnecessary as not much boilerplate code is saved.

Lombok can save a lot of code in the future, the current project is so simple that's the reason why you don't see too many changes.

Also not a great fan of adding one extra line between the last method and the end of the class and calling it "improved formatting". Many of those formatting changes you made are purely subjective and cannot be called improvements. They depend on the guidelines and are not universal. As everyone from the TCPShield team is using IntelliJ, their default settings are our code standards.

I call that consistency, and if you add a blank line before the first method, you should add one at before the last one. It also will help git to understand better future changes.

Exception handlers sound like a good idea, but imo the implementation is flawed at best. If a system like that should be implemented, I think abstraction is the way to go, not one class without one super class. That could be done super easy, e.g. one interface called "ExceptionHandler", implementing those methods with the parameters, and then storing them in a Map with the exception as the key and the corresponding handler as the value. I do not see though that that is needed in the amount of exceptions we are currently dealing with; it's just not necessary.

Yeah, the problem is every handler has different requirements, so the abstract class only will be able to manage the config and logger instances. I had thought about it.


Fix chunk spec fetcher usage with ordered dynamic tables

Fix critical bug in queue agent static exports.
TODO: Description.

Shipped!


Add API key Gradle task to build.gradle files in samples

This PR adds a Gradle task to all of the sample build.gradle files. The API key task creates a gradle.properties file in the .gradle folder if one doesn't already exist. The API key is set as a system property in the run task to allow the key to be used within in the samples.
Some things I would like some feedback on:

Added some instructions to the README on API keys. Are the IDE instructions clear?
For the terminal instructions, I followed the existing convention and added the step ./gradlew build, which would create the  gradle.properties file. When testing out that command or ./gradlew run, I got the error Could not find or load main class org.gradle.wrapper.GradleWrapperMain. To run ./gradlew run, I had to run the wrapper task before hand, which also creates the gradle.properties file. The issue is documented here. Should I replace ./gradlew build with gradle wrapper?

@JonLavi

@JonLavi I've added the instructions to create the Gradle wrapper to the Readme. I renamed the variables in the apiKey task, but I found if I renamed the task itself the build was failing if the gradle.properties file did not already exist.
I've also added back the Gradle badge that was taken out when the reference to the bintray repository was removed.

@Rachael-E @JonLavi I've renamed the task to createGradlePropertiesAndWriteApiKey instead of creating two separate tasks, as Gradle seems to default to writing apiKey = in the properties file if I attempt to have a separate task just to create the file.
Strangely, I found that if I renamed the task apiKey to something like createProperties, if the gradle.properties did not exist, the build process failed with the error: Build file 'C:\Users\sim11117\samples\arcgis-runtime-samples-java\analysis\analyze-hotspots\build.gradle' line: 61
A problem occurred evaluating project ':analyze-hotspots'.

Could not get unknown property 'apiKey' for task ':analyze-hotspots:run' of type org.gradle.api.tasks.JavaExec.

I've added a note in the Readme about the Gradle task, and added a comment to the run task explaining the apiKey as a system variable.

@Rachael-E @JonLavi I've renamed the task to createGradlePropertiesAndWriteApiKey instead of creating two separate tasks, as Gradle seems to default to writing apiKey = in the properties file if I attempt to have a separate task just to create the file.
Strangely, I found that if I renamed the task, if the gradle.properties did not exist, the build process failed with the error:
> Could not get unknown property 'apiKey' for task ':analyze-hotspots:run' of type org.gradle.api.tasks.JavaExec.

I resolved this by adding the system property line in the run task to a doFirst block.
I've added a note in the Readme about the Gradle task, and added a comment to the run task explaining the apiKey as a system variable.


Tracking: Styleguide Compliance

See Filipe's document about defaults: https://docs.google.com/document/d/1_sY01kQTVE-WoNjHgd_hLmbUF5q9X4o10XbEJRyu06w/edit

Also: style guide says we separate 3rd party imports from app imports with a blank line. We should do a pass on the generated code for this.


change the way candidates are emitted; add icegatheringstate

Description

fixes p2p test when promises are uses
adds icegathering state

The logic to start emitting candidates after the promise is resolved is getting crazy.
@pthatcherg: is that any different in the browser?

LGTM


Solr Backup recurrence/schedule not enabled by helm 0.7.1

I use the Helm, and, i can't found the options to configure the recurrence/schedule in the helm. I can only configure the repository

But, the schedule i not found the param and i need create by out of helm.
Please, help me to configura 100% in the helm?

That just configures a repository for your backups to use. You have to use a separate SolrBackup resource to actually take a backup.
The Solr Helm chart does not install a SolrBackup resource currently, though it could be added as a feature.

That just configures a repository for your backups to use. You have to use a separate SolrBackup resource to actually take a backup.
The Solr Helm chart does not install a SolrBackup resource currently, though it could be added as a feature.

@HoustonPutman We have a similar requirement. Will it be a feature for solr-operator chart or solr chart? Since, CRD are managed by solr-operator it make sense there but from ease of uss perspective it would be good if we extend it in the solr chart itself.


Storing Google photos locally to minimize Internet bandwidth ??

Sorry, this is not an issue rather a feature question/request.  Is there any way to store the photos from Google Drive locally to minimize Internet traffic?
I am building a pi_mirror for someone with limited bandwidth and it would be best to check for new photos in the album, download those to a local storage (partition or usb flash) and rotate/display images from that location on the Magic Mirror.  This would limit Internet calls for each album update and image url.  It may also reduce problems with number of API calls (could just update once or twice a day to get any new images).
I could probably spin off a new fork, but I wanted to see if anyone has already invented this wheel.
Thanks, Pete

I abandon this improvement. Sorry I was too busy and lost my interesting about this issue. If who can make PR about this, gladly I’ll accept.


[New Extension] Podcasts Now

Description
Podcasts Now is an extension that allows users to manage, and listen to their podcasts through Raycast based on Music.app.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@thomaslombart Thank you for reviewing. Your suggestions are amazing which lead me to do a bit refactor and make the extension have better performance and user experience. I also appreciate you found all the grammar mistakes in README and package.json files. As not a native English speaker, I should take them to go through Grammarly first.
I refactor the code a bit and also implement the menu bar command which it's totally a great feature for me and this extension. Please review it again.

Hey @cloudy9101, sorry for the late review. I was on vacation. I tried testing your extension again but couldn't because of an error:

Could you fix it so I can test the rest of the extension? 😊

Hi @thomaslombart , the error should be fixed, could you please test again?


Engineering prioritization next enhancements

Context
As part of our retros (among other discussions), it is quite clear we need to come up ASAP with a better way to produce a curated backlog with prioritized tasks that we can consume in out sprint planning meetings to create upcoming iterations.
Proposal
We have been discussing several ways to improve the process and one key decision was to create a sync meeting where we revisit the current backlog (in the Eng board), we refine the task and we "properly" prioritize them (from top to bottom and for each allocation) accoordingly to the perceived priority and contextual information we might have.
We will further iterate on this process to gain experience, discover failures and make improvements.
cc @2i2c-org/engineering for visibility
Updates and actions

We had one iteration of the backlog refinement meeting that works well.
@haroldcampbell setup a monthly meeting.
I (Damián) think a montly meeting is not the right cadence so, after discussing it with Harold, I updated the calendar invite to be a biweekly 30 min sync meeting (to have more iterations of the activity) which is "in sync" with the sprint retro/planning (to reduce the lag).
We are still thinking the best way for people to participate in this process in a async fashion (more of that in an upcoming messaage).

I (Damián) think a montly meeting is not the right cadence so, after discussing it with Harold, I updated the calendar invite to be a biweekly 30 min sync meeting (to have more iterations of the activity) which is "in sync" with the sprint retro/planning (to reduce the lag).

With a montly meeting, I have a concern is that we aren't fast enough to increase prio of:

support tickets
new hub requests
and anything else that would feel awkard to have a response time of up to month to get started on

But, its based on an assumption of the scope of the prioritization meeting that it should prioritize among everything. With a monthly meeting, the scope of what is to be prioritized could need to be adjusted to just prio among certain things - leaving other things to be prioritized per sprint in another meeting or similar.
With this comment, my wish is that its made clear what is to be prioritized in this monthly meet - because as soon as its not done in sync with sprints that becomes a question with no obvious answer.


Add support for vertex reranker

https://cloud.google.com/generative-ai-app-builder/docs/ranking
Reference implementation:
const auth = new GoogleAuth();

async function rerank(
  query: string,
  documents: Document[]
): Promise<Document[]> {
  const client = await auth.getClient();
  const projectId = await auth.getProjectId();

  const response = await client.request({
    method: "POST",
    url: `https://discoveryengine.googleapis.com/v1/projects/${projectId}/locations/global/rankingConfigs/default_ranking_config:rank`,
    data: {
      model: "semantic-ranker-512@latest",
      query: query,
      records: documents.map((doc, idx) => ({
        id: `${idx}`,
        content: doc.text(),
      })),
    },
  });
  return (response.data as any).records.map((r: any) => {
    const doc = documents[r.id];
    return {
      ...doc,
      metadata: {
        ...doc.metadata,
        score: r.score
      }
    };
  });
}

const reranked = await rerank("why is the sky blue", [
  Document.fromText(
    "A canvas stretched across the day,\nWhere sunlight learns to dance and play.\nBlue, a hue of scattered light,\nA gentle whisper, soft and bright."
  ),
  Document.fromText(
    "The sky appears blue due to a phenomenon called Rayleigh scattering. Sunlight is comprised of all the colors of the rainbow. Blue light has shorter wavelengths than other colors, and is thus scattered more easily."
  ),
]);

returns:
[
  {
    "content": [
      {
        "text": "The sky appears blue due to a phenomenon called Rayleigh scattering. Sunlight is comprised of all the colors of the rainbow. Blue light has shorter wavelengths than other colors, and is thus scattered more easily."
      }
    ],
    "metadata": {
      "score": 0.78
    }
  },
  {
    "content": [
      {
        "text": "A canvas stretched across the day,\nWhere sunlight learns to dance and play.\nBlue, a hue of scattered light,\nA gentle whisper, soft and bright."
      }
    ],
    "metadata": {
      "score": 0.39
    }
  }
]

Added to next branch in https://github.com/firebase/genkit/pull/803


fix(ui): fix title with itemValueMapper function

Issue:
What I did
How to test

Deploy preview for mcs-lite-introduction ready!
Built with commit e55943602dcec649aec137c04db8597ab14e30ba
https://deploy-preview-665--mcs-lite-introduction.netlify.com

Deploy preview for mcslite ready!
Built with commit e55943602dcec649aec137c04db8597ab14e30ba
https://deploy-preview-665--mcslite.netlify.com

Deploy preview for mcs-lite-ui ready!
Built with commit e55943602dcec649aec137c04db8597ab14e30ba
https://deploy-preview-665--mcs-lite-ui.netlify.com


Link to YouTube video?

Hi @Benedict-Carling. I couldn't find the link to the YouTube video. Is it there? Perhaps could be either on the home or on the designer page itself.

Closed by commit b72a24c2b81de655b0bf152a5434539fb0ba77ac

Have a YouTube window within the about page to make it clearer.


Work listing - BE

Link to Ticket
Description of Changes Made
This updates the existing WorkIndexPage model and associated templates, so that child work and historical work pages are displayed. The intro field is als removed from the model, as it is no longer required, as per design.
How to Test

by going to http://localhost:8000/work

Screenshots

Expand to see more

MR Checklist

[x] Add a description of your pull request and instructions for the reviewer to verify your work.
[x] If your pull request is for a specific ticket, link to it in the description.
[x] Stay on point and keep it small so the merge request can be easily reviewed.
[x] Tests and linting passes.

Unit tests

[ ] Added
[ ] Not required

Documentation

[ ] Updated build docs
[ ] Updated editor guidelines (https://docs.google.com/document/d/1PAWccdQ4tfaZsrEWmpDhvP3GH5RRmBOARFVp4b-kje8/edit?usp=sharing)
[x] Not required

Browser testing

[x] I have tested in the following browsers and environments (edit the list as required)

Latest version of Chrome on Linux
Latest version of Firefox on Linux

Data protection

[x] Not relevant
[ ] This adds new sources of PII and documents it and modifies Birdbath processors accordingly

Accessibility

[ ] Automated WCAG 2.1 tests pass
[ ] Manual WCAG 2.1 tests completed
[ ] I have tested in a screen reader
[ ] I have tested in high-contrast mode
[ ] Any animations removed for prefers-reduced-motion
[x] Not required

Sustainability

[ ] Images are optimised and lazy-loading used where appropriate
[ ] SVGs have been optimised
[x] Perfomance and transfer of data considered
[ ] If JavaScript is needed alternatives have been considered
[ ] New font variants have not been added
[ ] Not required

Pattern library

[ ] The pattern library component for this template displays correctly, and does not break parent templates
[ ] The styleguide is updated if relevant
[ ] Changes are not relevant the pattern library

@engineervix when I test this on my local build I'm getting an error:

@engineervix when I test this on my local build I'm getting an error:

Thanks Helen, fixed in 8fab6e7


return value of Update().Save() should contain any Edges on the original object

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
when entity.Update().Save() return the updated copy of the original entity it should also contain any previously eager loaded edges.
I think this could be done by looking at the .Edges of the oldValue at the end of the .Save method?
If you think this is worth adding and that's a possible direction then I wouldn't mind giving it a shot to implement it...
Motivation 🔦
imagine the following
user := client.User.Query().WithCompany().OnlyX()

if somethingsomething {
    user = client.User.UpdateOne(user).SetName("Buddy").SaveX()
}

fmt.Printf("company: %s \n" user.Edges.Company.Name)

now depending on if the update branch happened or not user.Edges.Company will be nil or still have the value from WithCompany.

Hey @rubensayshi and thanks for proposing this.
The mutation can contain changes to the edges, so old values should be removed from the Edges struct before we copy from it. Other solution is to query the database for getting the eager-loaded edges, but I prefer to avoid it.

Hey @rubensayshi and thanks for proposing this.
The mutation can contain changes to the edges, so old values should be removed from the Edges struct before we copy from it. Other solution is to query the database for getting the eager-loaded edges, but I prefer to avoid it.

maybe eager-load them (again) if they were eager-loaded before?

maybe eager-load them (again) if they were eager-loaded before?

and maybe a good starting point would be (regardless) to add something like Edges.CompanyOrGet(), similar to CompanyOrErr() but then it will query for the edges if it hasn't been loaded yet?
it's kinda hard to easily fetch edges if you didn't eager-load them without fetching them multiple times if they've already been fetched by something upstream.

and maybe a good starting point would be (regardless) to add something like Edges.CompanyOrGet(), similar to CompanyOrErr() but then it will query for the edges if it hasn't been loaded yet?
it's kinda hard to easily fetch edges if you didn't eager-load them without fetching them multiple times if they've already been fetched by something upstream.

Create has a similar problem;

owner := ...
pet := client.Pet.Create().SetOwner(owner).SaveX(ctx)

// need to set the owner edge again yourself or query for it
pet.Edges.Owner = owner

Create has a similar problem;

owner := ...
pet := client.Pet.Create().SetOwner(owner).SaveX(ctx)

// need to set the owner edge again yourself or query for it
pet.Edges.Owner = owner

I was thinking for the Update it could be as simple as:
// card_update.go
func (cuo *CardUpdateOne) sqlSave(ctx context.Context) (_node *Card, err error) {
	// ...

	if cuo.mutation.oldValueProvided {
		oldValue, err := cuo.mutation.oldValue(ctx)
		if err != nil {
			return nil, err
		}

		if oldValue.Edges.Owner != nil && len(cuo.mutation.OwnerIDs()) == 0 && !cuo.mutation.OwnerCleared() {
			_node.Edges.Owner = oldValue.Edges.Owner
		}
	}

	// ...

or we could mutate the original Card instance passed into UpdateOne(card):
// card_update.go
func (cuo *CardUpdateOne) sqlSave(ctx context.Context) (_node *Card, err error) {
	// ...

	if cuo.mutation.oldValueProvided {
		oldValue, err := cuo.mutation.oldValue(ctx)
		if err != nil {
			return nil, err
		}

		_node = oldValue
	}

	_spec.Assign = _node.assignValues
	_spec.ScanValues = _node.scanValues
	if err = sqlgraph.UpdateNode(ctx, cuo.driver, _spec); err != nil {

	// ...

I was thinking for the Update it could be as simple as:
// card_update.go
func (cuo *CardUpdateOne) sqlSave(ctx context.Context) (_node *Card, err error) {
	// ...

	if cuo.mutation.oldValueProvided {
		oldValue, err := cuo.mutation.oldValue(ctx)
		if err != nil {
			return nil, err
		}

		if oldValue.Edges.Owner != nil && len(cuo.mutation.OwnerIDs()) == 0 && !cuo.mutation.OwnerCleared() {
			_node.Edges.Owner = oldValue.Edges.Owner
		}
	}

	// ...

or we could mutate the original Card instance passed into UpdateOne(card):
// card_update.go
func (cuo *CardUpdateOne) sqlSave(ctx context.Context) (_node *Card, err error) {
	// ...

	if cuo.mutation.oldValueProvided {
		oldValue, err := cuo.mutation.oldValue(ctx)
		if err != nil {
			return nil, err
		}

		_node = oldValue
	}

	_spec.Assign = _node.assignValues
	_spec.ScanValues = _node.scanValues
	if err = sqlgraph.UpdateNode(ctx, cuo.driver, _spec); err != nil {

	// ...

I see that in func (cc *CardCreate) createSpec() (*Card, *sqlgraph.CreateSpec) there's already _node.Field = value assignments, we could take the same approach in UpdateOne when UpdateOne(card) was used and avoid the extra SELECT from the func (u *updater) node(ctx context.Context, tx dialect.ExecQuerier) error as well ?

I see that in func (cc *CardCreate) createSpec() (*Card, *sqlgraph.CreateSpec) there's already _node.Field = value assignments, we could take the same approach in UpdateOne when UpdateOne(card) was used and avoid the extra SELECT from the func (u *updater) node(ctx context.Context, tx dialect.ExecQuerier) error as well ?

Has Ruben proposal been debated/considered? It's annoying to deal with reloading edges mannualy. Sometimes is also hard to track all mutations from an entity alongside a request and this introduces unexpected panics.

@rubensayshi - We can start by adding With<E> to the Create/UpdateOne builders and then optimize the UpdateOne builder to retain types that were not updated in the mutation.

introduces unexpected panics

Can you elaborate on this? Note you can use <E>OrErr to get edges.


1.6: Oil level became Unavailable

Describe the bug
Thanks for all the work you guys do. Much appreciated! This isn't really a big problem for me. I just wanted to report it.
Suddenly (after upgrading to 1.6) my Oil level became Unavailable. It had previously returned 100%.
The variable OIL_LEVEL_DIPSTICKS_PERCENTAGE (value: true) is present in the debug logs.
This entity is no longer being provided by the audiconnect integration. If the entity is no longer in use, delete it in settings.

To Reproduce
None.
Expected behavior
Showing some kind of value.
Screenshots

Logfile
home-assistant_audiconnect_2024-04-16T12-55-52.255Z.log

When I look at how this was previously implemented, I understand why it is now Unavailable. Since the JSON returned doesn't contain any float value (number) - but an boolean (true) value.

Thanks for reporting @mm98 !
#383 should have removed the old sensor (as it did), and added a new sensor (binary) for your True state value. Seems it didn't do the latter portion. I'll look into it in a little bit. I think some logs are showing true while others are showing True. I wouldn't think that would be an issue, but we can adjust for that easily.

I guess the new binary sensor is there? The old sensor you can delete safely.

I'll close this, since I can just use the binary sensor.

I havbe the same problem as @arandax.

@arandax @xhemp please provide logs so we can investigate.

@coreywillwhat Just tossing my hat into the ring here too. The original oil level sensors became unavailable as described by the OP of this issue. I deleted it since Home Assistant said it wasn't being managed or something like that anymore. The replacement / newer binary_sensor mentioned as the solution to this issue does not exist / was not created The only oil related sensors I have now are the oil change distance and oil change time.
Other than the missing oil level sensors, everything else seems to be working fine (34 entities created by this integration with valid data)
I did enabled debug logging but didn't see any unusual errors. I do have 2x 403 ClientResponseErrors but those are for the trip data and climater which I'm pretty sure are not features supported by my 2019 B9 Audi (US).
The only oil level related log lines I found are the following:
2024-04-29 01:56:46.309 DEBUG (MainThread) [custom_components.audiconnect.audi_models] TRY APPEND FIELD: Searching for 'OIL_LEVEL_DIPSTICKS_PERCENTAGE' at location=['oilLevel', 'oilLevelStatus', 'value', 'value']
2024-04-29 01:56:46.309 DEBUG (MainThread) [custom_components.audiconnect.audi_models] TRY APPEND FIELD: Value for 'OIL_LEVEL_DIPSTICKS_PERCENTAGE' is None or missing; not appending field.

-Gary

On a side note, I just loaded up the MyAudi App (Android) and it also no longer shows me the oil level or even simple status (e.g: Oil Level: OK) in there. I see fuel level but no oil level unless they hid it somewhere that I have not found yet.
So, maybe for me, not having an oil level status is an Audi issue (or "feature") for my car and not a problem with the integration?
I did find an Audi World forum post of others talking about the MyAudi app no longer reporting oil level / status from 2022. It sounds like for the B9 the accuracy of the oil level reported in the MyAudi app was hit or miss. Originally the MyAudi app would report oil level as a % then they changed it to a simple status (OK / Low I guess) and now it's just gone.
https://www.audiworld.com/forums/a4-b9-platform-discussion-212/app-cant-check-oil-3037827/

Thanks for providing logs and your investigation @heymoe !
I can confirm the Audi API is no longer reporting the oil level, neither percentage nor binary, for your vehicle based on the log data you provided. Sorry for your loss :(

No problem. Thanks for confirming Audi removing the feature for my car and for keeping this integration working in general.


feat: cleanup old static channel backup files

how much space will the backup take?
If we create a SCB only if a channel is created and no longer on startup, do we then even need to clean it up in the app?

how much space will the backup take?
If we create a SCB only if a channel is created and no longer on startup, do we then even need to clean it up in the app?

Hmm, maybe you are right and this is enough. My hub was a bit of an exception, currently I have 250MB of backups across 17 files

Do we have an estimate of the average file we expect?
If somebody has a lot of channels and activity maybe we can expect them to delete those files?
and on average it just fills up a bit.


Failure to scan layers over 200MB

Due to this line, we cannot scan layers larger than 200MB. This value should probably be configurable and not hard-coded.

To be accurate, it prevents analysis of layers that contain files that match the extraction pattern AND are over 200MB.


Implementation of UtilityBrandedToken with Internal

Fixes :- #45
UtitlityBrandedToken is internal so that it is for the token-economies they are minted for.
It contains methods for setting coGateway address,minting and burning tokens apart from standard EIP20 methods.
Minting can only be done on registered internal actor.

For Minted vs. Transfer and Burnt vs. Transfer,new ticket needs to be created.


Allow domains where TLD is >6 characters

It appears this library assumes the domain TLD will not be more than 6 characters but these days, many are: https://newgtlds.icann.org/en/program-status/delegated-strings
I'm not terribly well versed in RFC 1035, but in Section 2.3.1 there doesn't seem to be any mention about a maximum length so I'm curious about how this constraint ended up in here, and how necessary it is. I wonder if it might make sense to remove this constraint altogether.
Regardless, this change is trivial; it just allows for domains with a longer TLD. The length that I changed it to is fairly arbitrary. From the aforementioned list, it seems the longest (as of March 2019) is 18 characters. This change increases it to 26 characters; again, fairly arbitrarily.
I don't often open pull-requests, but when I do, it's for a one character change.

Thanks!
And: funny; that traces all the way back to before Benny through my tenure to Les H. Must have been "good enough" back in the day. I'm a little embarrassed that I didn't catch it when I did my re-vamp.
Anyway, +1 for the one-character change! :-)
We could just amp it to 50, too, to be a bit safer. I'm not sure there'd be any significant downsides.

Thanks! I'll do a release soon (probably Saturday)

Thanks folks.
Speaking of releases, might you be able to do formal tagging/releasing in github for each release when you do? I'm happy to help out if there's anything I can do to assist.
Thanks again!

Also, I didn't update the comment at the bottom that has the full regex; should probably be done before release.

I doubt it is up to date to be honest. I think it's there for illustrative purpose.

Released in 1.1.3. Tagged every version in Maven, which should be picked up automatically by Github.


Spring-cloud-config support to getting the config bu calling RESTFUL API?

Currently , i want to get the sping-boot config by calling the restful api, what should i do?

Have you looked here? https://github.com/spring-cloud/spring-cloud-config/blob/master/docs/src/main/asciidoc/quickstart.adoc
On mobile or I'd give an example

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Possibility to have modifier at row and cell level

Hi,
great work porting the data-table, I had some hack before, but this implementation works well.
Just a feature nice to have and is to have modifiers at row or cell level, so for example is possible to add event on click of the row.
In any case this library already simplify a lot my life.

Found the way to setup an onClick on each row, so I'm happy with it:
 row {
    onClick = {
         onClickRow(currentRow)
     }
    cell {
            ///something
   }
}

It would be possible to add, but it seems like a bit of a clumsy API to have a modifier as an argument to a non-composable function.
Yeah, onClick might make more sense as a parameter. I had it as a property because it could use values from the row lambda closure. That probably isn't very interesting and it makes the API a bit more complicated to use, so maybe I'll change it for the next version.


Implement a signal that produces random triggers (e.g. "dust")

In Flocking, there's the Dust unit generator. Signaletic should have an equivalent, but I think it would be nice if it were able to support changing between unipolar and bipolar impulses by setting a parameter.

Resolved in #36 and #40.


Update to clean-css 4.x

User story
As a front-end developer, I want to update clean-css to 4.x, to be on a current version and avoid a security issue with 3.x.
Acceptance criteria

[x] clean-css 4.x is used to minimize assets in production

Fixed with https://github.com/mozilla/kuma/pull/5135, deployed to stage and production on 2018-12-07.


Sequence diagram enhancement

Thanks for your tootl, it's very useful!
Just to know your plans to add sequence diagram like https://github.com/bramp/js-sequence-diagrams
I read that it's in your roadmap. I never wrote a vsCode extension, but If I can help, tell me.

Hi, I will resume the development of this extension very soon, and will start with the mentioned sequence diagram.

I have already commenced. Will have a new release in very few days.

It is published now, with basic functionalities.


Possibly add tinyset to hashing-section

This HashSet-replacement (no HashMap, it seems like) sounds like it could be interesting: https://docs.rs/tinyset/latest/tinyset/index.html
Unfortunately, I don't have the expertise to know in which cases it will perform better/worse than other HashSets and what risks are associated with it.

Thanks for the suggestion. I think this is a bit too niche to be worth mentioning.


tests: run multiple simultaneous tcpreplay tests

For now, I am using TCPREPLAY_LIMIT=70000
In case I make it more (like 700000), test can (not always) somewhy drop with such error message:
Perform load test                                                     ...Second signal will force exit.
Second signal will force exit.
.[ ERROR ] tcpreplay: execution failed (type)
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/scapy/sendrecv.py", line 549, in sendpfast
    stdout, stderr = cmd.communicate()
                     ^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/subprocess.py", line 1209, in communicate
    stdout, stderr = self._communicate(input, endtime, timeout)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/subprocess.py", line 2108, in _communicate
    ready = selector.select(timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/selectors.py", line 415, in select
    fd_event_list = self._selector.poll(timeout)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/robot/running/signalhandler.py", line 40, in __call__
    self._stop_execution_gracefully()
  File "/usr/local/lib/python3.12/site-packages/robot/running/signalhandler.py", line 43, in _stop_execution_gracefully
    raise ExecutionFailed('Execution terminated by signal', exit=True)
robot.errors.ExecutionFailed: Execution terminated by signal
[ ERROR ] tcpreplay: execution failed (type)
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/scapy/sendrecv.py", line 549, in sendpfast
    stdout, stderr = cmd.communicate()
                     ^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/subprocess.py", line 1209, in communicate
    stdout, stderr = self._communicate(input, endtime, timeout)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/subprocess.py", line 2108, in _communicate
    ready = selector.select(timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/selectors.py", line 415, in select
    fd_event_list = self._selector.poll(timeout)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/robot/running/signalhandler.py", line 40, in __call__
    self._stop_execution_gracefully()
  File "/usr/local/lib/python3.12/site-packages/robot/running/signalhandler.py", line 43, in _stop_execution_gracefully
    raise ExecutionFailed('Execution terminated by signal', exit=True)
robot.errors.ExecutionFailed: Execution terminated by signal
Perform load test                                                     | FAIL | load test                                                     .
Process 2 Failed
------------------------------------------------------------------------------
Loadtest                                                              | FAIL |
1 test, 0 passed, 1 failed
==============================================================================

An example of test logs.
Without threads:
Perform load test
.Resulting pps: 166255.77
.Resulting mbps: 1465.71
.Resulting packets: 70000

With 2 threads:
Perform load test
.Resulting pps: 288043.65
.Resulting mbps: 2539.38
.Resulting packets: 140000

For now, I am using TCPREPLAY_LIMIT=70000 In case I make it more (like 700000), test can (not always) somewhy drop with such error message:

That error is appearing because of <timeout> parameter of Wait Async All method. It sets an upper bound of how much seconds can each thread live. If the thread fails to finish at the time allotted to him, robot test fails with error "Process N Failed". So <timeout> should be set with computational power of computer in mind.

An evidence of working processor cores:


Add support to Windows

issue #3
updated to issue #20

Please resolve the conflicts in install.sh file.

@Cereal84 i'm not getting what is the conflict.

If you see this page you can see "This branch has conflicts that must be resolved".
It reports that there is a conflict/s in install.sh file between your branch and the main, these conflicts depends on the fact that the file was updated in main branch and its history goes forward respect your branch.
I suggest you to rebase your branch with the main one and resolve locally the conflicts, check this doc.
    $ git checkout main
    $ git fetch
    $ git pull origin main
    $ git checkout Install.sh-new
    $ git rebase main

If you are not confident on rebase your branch you can update the main branch in your machine and create a new branch based on that main, add your changes and push a new PR.
    $ git checkout main
    $ git fetch
    $ git pull origin main
    $ git checkout -b fix_issue_20

@Cereal84 now is it fine?

i'm creating new pr due to some reasons and closing this one.


[Backport 2.x] Adds various Query overrides to Keyword Field (#10425)

Backport of #10425
The keywordfield mapper provides access to various query types, e.g. the termsQuery, fuzzyQuery. These are inherited as is from the StringType. But we do not take into account the fact that keyword fields can have doc_values enabled. This PR adds the ability for various queries to first check if doc_values are enabled and if so out-source the work to lucene to decide if it's better to use index values or doc_values when running queries.
Signed-off-by: Harsha Vamsi Kalluri<EMAIL_ADDRESS>(cherry picked from commit 63aff16c0d08bac44e1d1a6158ee3f838a043074)

Description
[Describe what this change achieves]
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[X] Commits are signed per the DCO using --signoff
[X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[X] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

com.carrotsearch.randomizedtesting.ThreadLeakError: 1 thread leaked from SUITE scope at org.opensearch.repositories.s3.S3BlobContainerRetriesTests:
   1) Thread[id=38, name=sdk-ScheduledExecutor-2-0, state=TIMED_WAITING, group=TGRP-S3BlobContainerRetriesTests]
        at java.base@17.0.8/jdk.internal.misc.Unsafe.park(Native Method)
        at java.base@17.0.8/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
        at java.base@17.0.8/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
        at java.base@17.0.8/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
        at java.base@17.0.8/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
        at java.base@17.0.8/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
        at java.base@17.0.8/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
        at java.base@17.0.8/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base@17.0.8/java.lang.Thread.run(Thread.java:833)

@msfroh backport PR.


⚠ SceneTime has degraded performance

In 16e7482, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1373 ms

Resolved: SceneTime performance has improved in 8c4496c after 6 minutes.


Enable small dot in interpreter

This PR lowers minimal size of dot matrices available in interpreter and enables related tests.

not sure why it was not enabled in #4345, though
+cc @whitneywhtsang

not sure why it was not enabled in https://github.com/triton-lang/triton/pull/4345, though

Oh, I guess I forgot... Thanks


Can't record microphone (Windows 10 Pro Version 22H2)

Tested versions
I'm having issues in every version I tested (can't remember them all)
My Project is running on Godot v4.3 (GodotSteam 4.11)
Also tried the Recording Demo but the problem hasn't vanished
System information
Windows 10 Pro - GodotSteam 4.11 - OpenGL3 - Forward+
Issue description
I want to implement a voice chat and therefore need to record the microphone. I can hear myself when I unmute my mute-bus - I have a record and a mute-bus. But when trying to record the microphone I only get an array of 0s. When monitoring the decibels everything seems to be right.
I tried this on another system (Windows 10 Home) and it worked. Apps like Discord work without any troubles on my system. I even tried recording audio with a custom Python Script and I got a recording
This is really frustrating and I would appreciate some help :-)
Steps to reproduce
To reproduce this you'd just need a Input AudioStream with a Recording Bus which uses a AudioEffectRecord and a output like an AudioStreamPlayer or any other way to know your get_recording().data
Minimal reproduction project (MRP)
This Script is getting called every X amount of frames and if a certain decibel threshold has been surpassed:
func gatherRecordingData() -> AudioStreamWAV:
        var sample:AudioStreamWAV = AudioStreamWAV.new()
	sample.mix_rate = 22050
	print(effect.get_recording().data)
	sample.data = effect.get_recording().data
	sample.format = AudioStreamWAV.FORMAT_16_BITS
	print(sample.data) #returns just 0s
        return sample

You can ignore the first print, it was from a test - also just zeros

Please upload a minimal project showing this bug to aid in testing and fixing, the provided example isn't detailed enough

Thanks for the response @AThousandShips!
Sure here is an example project which (hopefully) should work on other systems
recordingissueexample.zip


Select from menu of timeseries

https://github.com/rte-antares-rpackage/manipulateWidget

Outside of scope


[$250] Long workspace name breaks the alignment of side arrow - @Tushu17

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Create a workspace
Go to General Settings
Use a long name for workspace
Now go to settings and see the arrow at the right side of workspace.

Expected Result:
It shouldn't break the alignment of the side arrows.
Actual Result:
Long workspace name disturb the alignment of the side arrow of workspace.
Workaround:
unknown
Platform:

Where is this issue occurring?

Web

Version Number: 1.1.46-1
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @Tushu17
Slack conversation:
https://expensify.slack.com/archives/C01GTK53T8Q/p1648247302114379
View all open jobs on GitHub

https://www.upwork.com/jobs/~017410ee10e9594e18

I was able to fix this by setting flex-shrink to 1 on the container view

Nice! LGTM 👍

@roryabraham Were you able to reproduce this issue?
I am unable to reproduce this one,

You can reproduce it by adding more workspaces

Still no luck @nadir,

5 workspaces seem to trigger it

@nadir
I am not unable to reproduce this yet.

@mvtglobally Can you check whether this is still reproducible?
I am unable to reproduce this.

@Santhosh-Sellavel thanks for checking, I did not verify this (since it was reported by Applause)

You need to have 5 Workspaces to be able to reproduce it. Issue reproduced  for build <IP_ADDRESS>

surely it has to do with the length of the workspace name and not the number of workspaces?

Unless I'm mistaken, it has been 12 days since we've heard from @nadir. According to our contributing guidelines:

Daily updates on weekdays are highly recommended. If you know you won’t be able to provide updates for > 1 week, please comment on the PR or issue how long you plan to be out so that we may plan accordingly. We understand everyone needs a little vacation here and there. Any issue that doesn't receive an update for 1 full week may be considered abandoned and the original contract terminated.

Since it's been 12 days and they were pinged for an update in their PR, I'm going to unassign them.
@arielgreen Can you please cancel the upwork contract and open it back to applications?

done

Price increased.

I’m not able to reproduce this even once, were you able to reproduce @roryabraham?
@mvtglobally & @Tushu17 Is this occurring consistently for you all. If then Please share the following info: Platform: In Mac or Windows Browser: Display Size in inches: Thanks!

Is this still reproducible?

Is this reproducible?

Yes @Santhosh-Sellavel It's still reproducible in Window on chrome.

Windows OS?

Windows OS?

@Santhosh-Sellavel Yes

https://github.com/Expensify/App/blob/569289ba2cb2c99971f6164cd869e67efedc4a48/src/components/MenuItem.js#L62
adding flex: 1 at the parent of the title is fixing this issue
Before this change

After this change

Thanks, @Tushu17, I was able to reproduce this one, on chrome (Windows).
The issue exists on staging but is no longer reproducible in the main branch. Check out the video in the slack thread!
cc: @roryabraham

@Santhosh-Sellavel can you please retest on staging today? There was a staging deploy yesterday, so the main branch was deployed to staging environment.

Issue unable to reproduce for me on staging. @Tushu17 can you confirm the same?

@Santhosh-Sellavel @roryabraham
I think this commit is fixing this issue https://github.com/Expensify/App/commit/388cfe3793be3fb3f0f570c31049a8f57b051853
this change I already commented but I think this change was already done before my comment
https://github.com/Expensify/App/issues/8461#issuecomment-1117862841

Issue unable to reproduce for me on staging. @Tushu17 can you confirm the same?

@Santhosh-Sellavel yup, It's no more reproducible.

Actually, I'll leave this open for you and just unassign myself

My mistake, @Santhosh-Sellavel is also eligible for C+ compensation for reviewing https://github.com/Expensify/App/pull/8576, even though it wasn't merged.

@Tushu17 and @Santhosh-Sellavel just sent over offers to both of you via Upwork, once you accept I will pay out the job and close the issue.

@arielgreen Thank you, Offer accepted.

@arielgreen
Accepted the offer, thanks!

Paid.


Re-design ssh Key as Verifier only

Previously, ssh Key satisfied both the dsse.Verifier interface and served as TUF metadata key container. Unfortunately, it didn't seem feasible to wire up the key container with the current TUF metadata implementation, which uses SSlibKey.
This commit re-designs the ssh key implementation to use SSlibKey as key container and a separate Verifier for verification.
See https://github.com/gittuf/gittuf/pull/429#issuecomment-2151588628 for more detailed design considerations.
Change details:

Add an SSHKeyTypeConstant
Rename Import to NewKeyFromFile
Replace ssh Key with ssh Verifier, which satisfies the dsse.Verifier interface, but is otherwise a black box (no key details exposed).
Change NewKeyFromFile to return an SSlibKey, to be included in TUF metadata.
Add NewVerifierFromKey function to create an ssh Verifier from a  corresponding SSlibKey, e.g. included in TUF metadata, to verify  a signature from an ssh Signer.
Add TUF metadata integration POC / usage example in tuf_test.go (see comment in #429).

Note that unlike #429, this PR does not add a "ssh Verifier to SSlibKey" conversion function, because with the re-design there does not seem to be a use case.
The general workflow should be:

Import SSlibKey from ssh key file
Add to TUF metadata, or cache otherwise
Convert Key to Verifier when verifying a related signature

Btw. creating a Signer is currently a bit cumbersome:
https://github.com/gittuf/gittuf/blob/bd5d1d715414e66910e00fa1bc0d23e642af60cb/internal/signerverifier/dsse/dsse_test.go#L65-L78
NewSignerFromFile(path string) or NewSignerFromKey(key SSLibKey, path string) functions would be helpful. I can add those in a separate PR, if there is a need.


i think the code cant close the pop up window after a video has been posted

VM398:49 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at waitForElement (:49:34)
at SuccessDialog.closeDialogButton (:97:26)
at SuccessDialog.close (:101:30)
at Object.publishDrafts [as publish_drafts] (:227:26)
^^ this is the error throw back in the developer console

Same problem
The issue:
Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at waitForElement (:52:34)
at SuccessDialog.closeDialogButton (:77:26)
at SuccessDialog.close (:81:30)
at main (:205:26)
waitForElement @ VM4449:52
closeDialogButton @ VM4449:77
close @ VM4449:81
main @ VM4449:205
async function (async)
main @ VM4449:194
(anonymous) @ VM4449:210
(anonymous) @ VM4449:211

i have a suspircion that the issue lies with the getElementbyId for the close button. it is current "iron-icon".. can't seem to find a better Id to call the close button.. zzz

changing
const DIALOG_SELECTOR = 'ytcp-dialog.ytcp-video-share-dialog > paper-dialog:nth-child(1)';
to
const DIALOG_SELECTOR = 'ytcp-dialog.ytcp-video-share-dialog > tp-yt-paper-dialog:nth-child(1)';
seems to fix it for me

sad. youtube introduced 'checks' and now the code doesnt work at all

sad. youtube introduced 'checks' and now the code doesnt work at all

Yea, pls fix it guys :))

guys, I need your help.  Is it possible to modify this script so that instead of making all the videos available, each video is sent for a different hour in postponed publication, it is desirable that this can be configured, for example, the script is launched, the first video is sent on March 21 at 10 am, the next 11 am, and so on  Further.  Well, of course, the problem with YouTube checks needs to be solved, I would be very grateful and in the future I would thank

You have to do it semi-manually now. Steps:

run javascript
close the prompt
repeat

You have to do it semi-manually now. Steps:

run javascript
close the prompt
repeat

It has no sence in this way, that's the same that we can do w/o any script step by step make each video public

You have to do it semi-manually now. Steps:

run javascript
close the prompt
repeat

It has no sence in this way, that's the same that we can do w/o any script step by step make each video public

That is why I said semi-manual. Anyway, since the process is repetitive, it is possible to fully automate it by using AHK.

I got it working but I don't know how to leave a comment on the code.
I removed " > paper-dialog:nth-child(1)" and changed "iron-icon" to "tp-yt-iron-icon"
Not sure if the 2nd change is necessary but it's working.

I got it working but I don't know how to leave a comment on the code.
I removed " > paper-dialog:nth-child(1)" and changed "iron-icon" to "tp-yt-iron-icon"
Not sure if the 2nd change is necessary but it's working.

i submitted a pull request with this fix about 2 weeks ago and it hasnt gone through yet unfortunately

I got it working but I don't know how to leave a comment on the code.
I removed " > paper-dialog:nth-child(1)" and changed "iron-icon" to "tp-yt-iron-icon"
Not sure if the 2nd change is necessary but it's working.

i submitted a pull request with this fix about 2 weeks ago and it hasnt gone through yet unfortunately

because it does not fix it

I got it working but I don't know how to leave a comment on the code.
I removed " > paper-dialog:nth-child(1)" and changed "iron-icon" to "tp-yt-iron-icon"
Not sure if the 2nd change is necessary but it's working.

i submitted a pull request with this fix about 2 weeks ago and it hasnt gone through yet unfortunately

because it does not fix it

it did work when I submitted it, however it appears that they've changed it yet again, breaking it. I'll see if i can fix it. i reckon they'll change it again though in a few days as it seems to be...

@reisher
I've hopefully fixed it. would you kindly test for me (before youtube messes with it again)?
#2

@reisher
I've hopefully fixed it. would you kindly test for me (before youtube messes with it again)?
#2

It works now but only for one video as soon as it finishes the window is closed but it won't proceed to the next video

@reisher
I've hopefully fixed it. would you kindly test for me (before youtube messes with it again)?
#2

It works now but only for one video as soon as it finishes the window is closed but it won't proceed to the next video

It works perfectly for me i.e. everything is fully automated.

@reisher
I've hopefully fixed it. would you kindly test for me (before youtube messes with it again)?
#2

It works now but only for one video as soon as it finishes the window is closed but it won't proceed to the next video

It works perfectly for me i.e. everything is fully automated.

Even if it works, how many video can you upload to yt without delayed publication before it will get shadowban and zero views for them?)
I tried to upload about 30~50 video by this way but everytime it's getting shadowban)
However, if those videos published with delayed piblication, even every 15-30min or a hour, it works good ans getting views)
That's why i requested

guys, I need your help. Is it possible to modify this script so that instead of making all the videos public, each video is sent for a different hour in postponed publication, it is desirable that this can be configured, for example, the script is launched, the first video is sent on March 21 at 10 am, the next 11 am, and so on Further. Well, of course, the problem with YouTube checks needs to be solved, I would be very grateful and in the future I would thank

Personally, this isn't an issue for me as I only use this for unlisted videos, and it is also be beyond my javascript abilities but that's beside the point. I would recommend you open another issue for this as a suggestion, since this is just about the bugs introduced with youtube changing their HTML :) Hopefully the owner can give you some advice then.

Even if it works, how many video can you upload to yt without delayed publication before it will get shadowban and zero views for them?)
I tried to upload about 30~50 video by this way but everytime it's getting shadowban)
However, if those videos published with delayed piblication, even every 15-30min or a hour, it works good ans getting views)
That's why i requested

guys, I need your help. Is it possible to modify this script so that instead of making all the videos public, each video is sent for a different hour in postponed publication, it is desirable that this can be configured, for example, the script is launched, the first video is sent on March 21 at 10 am, the next 11 am, and so on Further. Well, of course, the problem with YouTube checks needs to be solved, I would be very grateful and in the future I would thank

Personally, this isn't an issue for me as I only use this for unlisted videos, and it is also be beyond my javascript abilities but that's beside the point. I would recommend you open another issue for this as a suggestion, since this is just about the bugs introduced with youtube changing their HTML :) Hopefully the owner can give you some advice then.
Ok, sorry for the flood, but...
1.What's the reason to upload unlisted videos?))

I guess the "promises" in javascript would get this point with delayed publications))

Ok, sorry for the flood, but...
1.What's the reason to upload unlisted videos?))
2. I guess the "promises" in javascript would get this point with delayed publications))

I just use it for playing music through a discord bot. It's unlisted as I don't want actual people to watch it and report for copyright etc. So i have plenty of songs that i need to publish in bulk unlisted that this script helps with😃
That might be a solution. However, as said before my javascript skills are only enough to fix bugs like this so I can't say if that would work

Again, I would recommend you open another issue on the repository so you can suggest the feature you want as this issue is just about a bug and not a suggestion.

Even if it works, how many video can you upload to yt without delayed publication before it will get shadowban and zero views for them?)
I tried to upload about 30~50 video by this way but everytime it's getting shadowban)
However, if those videos published with delayed piblication, even every 15-30min or a hour, it works good ans getting views)
That's why i requested

guys, I need your help. Is it possible to modify this script so that instead of making all the videos public, each video is sent for a different hour in postponed publication, it is desirable that this can be configured, for example, the script is launched, the first video is sent on March 21 at 10 am, the next 11 am, and so on Further. Well, of course, the problem with YouTube checks needs to be solved, I would be very grateful and in the future I would thank

Personally, this isn't an issue for me as I only use this for unlisted videos, and it is also be beyond my javascript abilities but that's beside the point. I would recommend you open another issue for this as a suggestion, since this is just about the bugs introduced with youtube changing their HTML :) Hopefully the owner can give you some advice then.

Ok, sorry for the flood, but...
1.What's the reason to upload unlisted videos?))
2. I guess the "promises" in javascript would get this point with delayed publications))

Stop derailing the thread. Nobody cares.

sorry guys, didn't notice the discussion, I will look into it on saturday, promise!


Added ISshSession.SetTimeout based on the previously missing libssh2_…

…session_set_timeout API.

@pyscripter , please don't forget to merge before doing modifications on your side :)


ST7789 display is blank

Hey,
I'm running the latest from master trying to get a ST7789V2 working.
The code I'm using is below. I have hooked a logic analyser up and see a LOT of SPI traffic, but the display is just black. The backlight is working (it's just hard wired to high).
Any hints on how to debug a black screen? I'm a bit lost and there is so much traffic being generated that it's hard to manually verify it's correct.
// Display
const W: i32 = 240;
const H: i32 = 280;

    let mut gpio_dc = Gpio::get_pin(0).unwrap();
    let dc = gpio_dc.make_output().unwrap();

    let di = SPIInterface::new(Spi, dc);

    let mut delay = Delay;
    let mut display = Builder::new(ST7789, di)
        .display_size(W as u16, H as u16)
        .invert_colors(ColorInversion::Inverted)
        .init(&mut delay)
        .unwrap();

    // Text
    let char_w = 10;
    let char_h = 20;
    let text_style = MonoTextStyle::new(&FONT_10X20, Rgb565::WHITE);
    let text = "Hello World ^_^;";
    let mut text_x = W;
    let mut text_y = H / 2;

    // Alternating color
    let colors = [Rgb565::RED, Rgb565::GREEN, Rgb565::BLUE];

    // Clear the display initially
    display.clear(colors[0]).unwrap();

    writeln!(Console::writer(), "Done clear\r").unwrap();

    // Draw text
    let right = Text::new(text, Point::new(text_x, text_y), text_style)
        .draw(&mut display)
        .unwrap();
    text_x = if right.x <= 0 { W } else { text_x - char_w };

We have recently added a section about the RESET pin to the troubleshooting docs, which might be your problem: https://github.com/almindor/mipidsi/blob/master/docs/TROUBLESHOOTING.md#reset-pin

Thanks. The reset pin is held high. I'll try connecting it to the crate.
I'll also try slowing down the SPI speed to see if that helps

If that doesn't fix the problem: How do you control the CS pin? Your code snippet doesn't show how the SpiDevice is created. It's important that the CS pin is driven high before Builder::init is called. If you use a SpiDevice implementation from  the embedded-hal-bus crate this is ensured if you use at least version 0.2.0.

The reset pin troubleshooting didn't seem to fix the issue. Neither did slowing down the SPI speed.
The CS pin is controlled as part of the embedded-hal implementation, the CS pin seems to be driven high before Builder::init is called

The communication looks OK at first glance. Did you create the capture before you added the reset pin to a GPIO? Because the 0x01 command is the soft reset command and that should only be sent if reset isn't controlled by this crate.
Judging by the screenshot you are using a Salae logic analyzer. I've attached a Saleae capture file of a successful initialization of a ST7789 display.
st7789.zip

That was captured before the reset pin was setup as a GPIO.
I am using a Salae. I looked at your capture and it seems pretty similar. I've attached mine if that's helpful. Really the only difference is that mine has a longer delay between the operations
st7789-not-working.zip

Strange, I don't see any reason why this wouldn't work. Can you test the display with another library/platform to make sure the hardware is OK?

I don't really have a different platform to try unfortunately

I'm slowly running out of ideas. One of the last things I could think of is to try the original init sequence from the Seeedstudio/Waveshare code. Try to replace the init method in https://github.com/almindor/mipidsi/blob/master/mipidsi/src/models/st7789.rs with this:
fn init<RST, DELAY, DI>(
    &mut self,
    dcs: &mut Dcs<DI>,
    delay: &mut DELAY,
    options: &ModelOptions,
    rst: &mut Option<RST>,
) -> Result<SetAddressMode, InitError<RST::Error>>
where
    RST: OutputPin,
    DELAY: DelayNs,
    DI: WriteOnlyDataCommand,
{
    let madctl = SetAddressMode::from(options);

    match rst {
        Some(ref mut rst) => self.hard_reset(rst, delay)?,
        None => dcs.write_command(SoftReset)?,
    }
    delay.delay_us(150_000);

    dcs.write_raw(0x36, &[0x00])?;
    dcs.write_raw(0x3A, &[0x05])?;
    dcs.write_raw(0xB2, &[0x0B, 0x0B, 0x00, 0x33, 0x35])?;
    dcs.write_raw(0xB7, &[0x11])?;
    dcs.write_raw(0xBB, &[0x35])?;
    dcs.write_raw(0xC0, &[0x2C])?;
    dcs.write_raw(0xC2, &[0x01])?;
    dcs.write_raw(0xC3, &[0x0D])?;
    dcs.write_raw(0xC4, &[0x20])?;
    dcs.write_raw(0xC6, &[0x13])?;
    dcs.write_raw(0xD0, &[0xA4, 0xA1])?;
    dcs.write_raw(0xD6, &[0xA1])?;
    dcs.write_raw(0xE0, &[0xF0, 0x06, 0x0B, 0x0A, 0x09, 0x26, 0x29, 0x33, 0x41, 0x18, 0x16, 0x15, 0x29, 0x2D])?;
    dcs.write_raw(0xE1, &[0xF0, 0x04, 0x08, 0x08, 0x07, 0x03, 0x28, 0x32, 0x40, 0x3B, 0x19, 0x18, 0x2A, 0x2E])?;
    dcs.write_raw(0xE4, &[0x25, 0x00, 0x00])?;
    dcs.write_raw(0x21, &[])?;
    dcs.write_raw(0x11, &[])?;

    delay.delay_us(120_000);

    dcs.write_raw(0x29, &[])?;

    Ok(madctl)
}

Thanks for the idea. I tried that, but still no luck.
I also tried changing some of the MCU SPI PIN settings to see if there is something that the ST7789 doesn't like (this does work with other SPI devices), but no luck.
Do you have a good example of a ST7789 that is known to work? I can see if I can test that instead

I never had any problems with the cheap ST7789 modules you can get on AliExpress or ebay. Just make sure to avoid modules that don't expose the CS pin. This style, which is similar to the module you used, is one which I've tested successfully: http://www.lcdwiki.com/1.69inch_IPS_Module
I'm starting to think that the level shifter on your module might cause the problem. The TXB series level shifters can lead to some weird issues, like in this article that was recently featured on Hackaday: https://joshua0.dreamwidth.org/74833.html.

That's an interesting idea. I'll try a different module and see how that goes


Run IGV Web App with different host IP and port

Is there a way to specify a different host IP and port, rather than localhost:8080? I 've read the README and the wiki, and can't find anything.
I guess IGV Web App runs the IGV.js npm http-server under the hood. So I tried the following arguments from npm http-server:
-p or --port Port to use (defaults to 8080)
-a Address to use (defaults to <IP_ADDRESS>)

These did not seem to do anything.
Is there a way to change the host IP and port?

Thank you @jrobinso this works exactly the way I needed it to. I just call the https-server module directly from the IGV Web App source:
node_modules/http-server/bin/http-server -a <IP_ADDRESS> -p 80 dist


As a web3 user, I want to use IDEM as a wallet connect wallet, so that I can use IDEM on web 3 sites

Would have this as a goal in the roadmap. Get main functionality working first.


feat: add expression and expression subcategory page

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your default branch!
[x] Make sure you are making a pull request against the default branch (left side). Also you should start your branch off default branch.
[x] Check the commit's or even all commits' message styles matches our requested structure.
[x] Check your code additions will fail neither code linting checks nor unit test.
[x] I have added necessary documentation (if appropriate)

Linked Issues
Fixes
Description
add expression and expression subcategory page
Only wisdom, Editorial and Miscellaneous were added.
Remaining will be added later.
❤Thank you!
Post merge checklist

[x] Follow steps from the guidelines for contributing to this repository.
[x] If you are a new contributor, ping in the thread and one of the maintainers will add you to all-contributors list.

@120EE0692 ?

@120EE0692 I recommend having a custom subcategory filter (in the getStaticProps section) for the catch-all file as we have varied non-article subcategories in the editorial. Also, consider if a catch-all would work here since the UI may differ for each.

Non-article subcategories are yet not prepared.

 @120EE0692 ?

@120EE0692 I recommend having a custom subcategory filter (in the getStaticProps section) for the catch-all file as we have varied non-article subcategories in the editorial. Also, consider if a catch-all would work here since the UI may differ for each.

Non-article subcategories are yet not prepared.

I understand, however, it is better to have the filter from now itself. And display not-found for others.

 @120EE0692 ?

@rutajdash

The error is still persisting in a clean environment, please see what is the issue.

 @120EE0692 ?

@rutajdash

The error is still persisting in a clean environment, please see what is the issue.

@rutajdash

When I am using this this is working fine.
As I noticed in the production database the podcast and editorial subcategory, numbers get swapped. Hence I also change in app. Maybe in this link https://project-reclamation-staging.herokuapp.com/v1/graph the number may not get swapped, and hence when it makes the request for the editorial it get a null response.


Consider support for PN532 RFID/NFC Boards

Library - https://github.com/Seeed-Studio/Seeed_Arduino_NFC

Implemented by #4


Feature request: Simple counter of Immortalized/Duplicated/Frozen crew

People often brag/celebrate of how many crew they have, but they don't really know that, because in fact there is no simple way to get the real number of how many crew we immortalized. The in-game counter in Cryostasis Vault is buggy and does not show the actual immortalized crew especially when there are dupes. You can do a simple check by freeze/unfreeze crew and watch the counter. The achievement counter (which disappear after 600) is buggy and unreliable too.
It would be really nice to have a proper simple counter of how many crew is immortalized (w/ or w/o dupes).
There is so many number in stats page, but nowhere the immortalized count can be found.
I guess also a chart similar to "Owned vs. Not Owned crew per rarity" would fine too.

A roster summary button has been added to the bottom of the crew player tool, which inventories your crew by rarity, skills, immortalizations, among other things.


Alexa Comms is not working

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide
Briefly summarize your issue:
While running Alexa comms, failed to create SipUserAgentInterface_create which results in "Failed to create to SampleApplication!"
What is the expected behavior?
Alexa should run with the Comms feature.
What behavior are you observing?
Alexa is not working at all.
Provide the steps to reproduce the issue, if applicable:
AVS SDK- 1.18
AlexaCommsLib_3.2.23
comms_adapter.1.6
Alexa.txt
Tell us about your environment:
Linux-Ubuntu 16.04
What version of the AVS Device SDK are you using?
  1.18

Tell us what hardware you're using:
Artik305
Tell us about your OS (Type & version):

[ ] Linux

Hi @Alexa-AUH thanks for posting
Can you please reach out to your amazon representative to receive further support?


Update user admin page

Overview
This PR adds two features to the user admin page

Send password reset email
Contact info fields

Closes #192
Notes
#192 asks for user address on this page, but we don't have this field in the database.
Testing Instructions

[ ] Ensure admin can create a new user
[ ] Ensure that admins can send a password reset email for a user
[ ] Ensure that email contains the correct reset link
[ ] Ensure that contact info can be edited on the user admin page

Checklist

[ ] fixup! commits have been squashed
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
[ ] README.md updated if necessary to reflect the changes
[ ] CI passes after rebase

Taking a look now


Code coverage flakes

We're getting (at least I'm getting) a lot of flakes in the code coverage / Cargo Tarpaulin action.  Seems like there's a specific integration test that passes in the normal test runs, but under Tarpaulin fails to connect to its spawned Spin.
@FrankYang0529 I think you are the person who knows about the code coverage stuff - would you be able to take a look please?  Thanks!

Related thought: given that the integration tests already run as part of the build action, could we skip running this rather lengthy action on every iteration of every PR, and instead do it like the audit one, a distinct action running on a schedule against main only in the Fermyon org?  Are we actually using the PR-level coverage info?
cc @vdice who was involved in the original code coverage discussion/planning

👍 I'm in support of restricting the code coverage action to run on main only for the near future.  Cron approach, as used by audits, seems appropriate.
We talked about utilizing the coverage results on PRs as a follow-up, but as 1. the check isn't entirely reliable (eg #1063 ) and 2. it takes quite a large amount of time to run, I agree it should harden against main first, where we can address both points, before incurring costs to contributors/PRs.

@FrankYang0529 I have skipped the problematic test for now but if you have any ideas on how to reinstate it that would ge great - thanks!

Not sure where this ended up but it's been inactive for over a year, and CI seems as happy as CI ever is, so closing.


Get wikidata exact mappings

Many Wikidata equivalences are listed through the "exact match" property rather than through properties specifically referring to identifiers from a given resource.

Better suited for semra


Examine use of feeds

It's possible to use e.g. releases or tags feeds which would yield significant performance benefits if the desired information is contained there (because the recency information is readily available, which is not if used /tags API).
But this would bring extra dependencies (feedparser or...)?

1.0.0 uses feeds where available (and thus much faster) :)


rebar_app_info:applications/1 can return out of date information

If an applications .app.src file is updated to add/remove applications and a provider depends on compile, the old applications list is returned by rebar_app_info:applications/1 inside the provider.

Wait, why would the applications list get updated? Still seems like something good to fix so I am looking into it, but found that odd.

Because the application now depends on a new application. I added an application to the app.src file and then ran rebar3 dialyzer. The dialyzer command did not see that an application had been added because it uses rebar_app_info:applications/1 to fetch applications used by the project application(s). I ran rebar3 dialyzer again and it saw the new application.
I think this means that any provider depending on compile does not get updated rebar_app_info.

Aaah, ok, I know why this is I think, will fix today.

So doing this for deps would be a bit of a pain, but doable. I've pushed a fix for project apps only for now.

Merged. Open another one if we need to do something about deps.


remove test failure if warnings are printed when package is imported

This is a very brittle test, if any of the dependencies shows something to stderr this will fail. On 1.7 this happens (https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/9bb1633_vs_dd12291/MeasureTheory.1.7.0-beta2-9a791aa09fb.log). For example:
WARNING: Wrapping `Vararg` directly in UnionAll is deprecated (wrap the tuple instead

I would say this test needs to be more precise if it is to be useful.

Thanks @KristofferC . We were having trouble with this for a while because of some subtleties in KeywordCalls.jl. I think we're past this now, so I'll merge this to be sure we're ok for 1.7. If we start seeing issues like this again we can revisit and try to be more precise as you suggest.

@cscherrer We should probably register a new release, since PkgEval only uses registered versions of packages

Sounds good. I've got some changes coming in dev, but we can push this to the front

I updated the version to 0.8.2. Let's make sure tests pass, then we can register


Config backups via API failing after 24.7 update

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug

After updating to 24.7, my backup script using the API is no longer working

To Reproduce

Create a new user
Grant the user effective privileges GUI - Diagnostics: Configuration History
Create an API key and download it
Take the key and secret from the file and use it in the below command

curl -k -u "mykey":"mysecret" https://opnsense_ip_here/api/core/backup/download -o "backup.xml"

Edit the backup.xml file and you should see content like this

{"errorMessage":"Endpoint not found"}

Expected behavior

A plain text XML file is created containing the backup

Describe alternatives you considered

Manual backups (pls no)
Google Drive (no thanks)
Nextcloud (I don't run it in my stack)

Relevant log files

I submitted a crash report as it showed up in the UI
I included the below unique string as a reference

HVXlVji19cIuE9uz6fhZ

Environment

VM running in Proxmox

upgraded to the latest version?

Yes, should be fixed in 24.7_9 already.

Hey, yeah I'm on the latest version - I upgraded the firewall before I
posted this thread
Has there been a new release in the hours since?
On Thu, 1 Aug 2024, 08:47 Franco Fichtner, @.***> wrote:

Closed #7697 https://github.com/opnsense/core/issues/7697 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/opnsense/core/issues/7697#event-13721327970, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARBSAZ5IRD6X6YF4S26DF5TZPHRY3AVCNFSM6AAAAABLZH2VNCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTG4ZDCMZSG44TOMA
.
You are receiving this because you authored the thread.Message ID:
@.***>

BTW https://github.com/opnsense/plugins/blob/stable/23.7/sysutils/api-backup/Makefile#L3

Ah, must be something I've missed - I see a scheduled backup ran and
completed
I'll do another update check and reboot and try again
You're right on the endpoint too and I have a typo above - my actual script
has "/this" at the end
On Thu, 1 Aug 2024, 08:49 Franco Fichtner, @.***> wrote:

BTW
https://github.com/opnsense/plugins/blob/stable/23.7/sysutils/api-backup/Makefile#L3
—
Reply to this email directly, view it on GitHub
https://github.com/opnsense/core/issues/7697#issuecomment-2262280695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARBSAZ3GLXDHXQKBBPEPEJDZPHR7XAVCNFSM6AAAAABLZH2VNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRSGI4DANRZGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Final update - latest update fixed it
I then had a problem with doing the backup as a cron job, but it was because a variable had been cut in half so the password was wrong


Security hole in blacklist for MySQL

The EXPLORER_SQL_BLACKLIST includes INSERT INTO - on MySQL the INTO is optional - so you can still run inserts on MySQL by just doing INSERT <table> VALUES (<data>);.

This should be resolved by release 2.5


rekor-server: 1.3.4 -> 1.3.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sigstore/rekor/releases.
meta.description for rekor-server is: Sigstore server, the Signature Transparency Log
meta.homepage for rekor-server is: https://github.com/sigstore/rekor
meta.changelog for rekor-server is: https://github.com/sigstore/rekor/releases/tag/v1.3.5
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.5 with grep in /nix/store/ykvpairz1s8zk1nfgarq70c12d1slhhm-rekor-server-1.3.5
found 1.3.5 in filename of file in /nix/store/ykvpairz1s8zk1nfgarq70c12d1slhhm-rekor-server-1.3.5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
rekor-cli
rekor-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ykvpairz1s8zk1nfgarq70c12d1slhhm-rekor-server-1.3.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rekor-server https://github.com/r-ryantm/nixpkgs/archive/cf838c3a0ce69970b7d74e86af5ee6251d9225c2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cf838c3a0ce69970b7d74e86af5ee6251d9225c2#rekor-server

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ykvpairz1s8zk1nfgarq70c12d1slhhm-rekor-server-1.3.5
ls -la /nix/store/ykvpairz1s8zk1nfgarq70c12d1slhhm-rekor-server-1.3.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

rekor-cli
rekor-server

Maintainer pings
cc @LeSuisse @06kellyjac @developer-guy for testing.

Will be done in #286021.


Logo Home Link not working

It should use HOME_LINK instead of HOME_URL substitution in the page template.
I also needed to use APP_ALIAS instead of APP_ID in the Home URL (User Interface Attributes)
Somehow the link did not work with APP_ID

Good point. Try with #HOME_LINK# instead of &HOME_LINK.. I'll change it for next version. Thanks!


Add/Remove the platform restrictions so we can use it with lemon loader maybe?

I've removed the platform restrictions with 9fb6b23dbfacac7242757d3435d7074084c92908 so you can try if it works but I can't test it


Reduce image footprint by using fedora minimal image as base image

Type of change

Refactoring

Description
Given that fedora-minimal has been available for a while now and seems to be a common upstream for rhel-based images, I propose that we move to this. This should:
a) Hopefully fix CI issues with missing docker images
b) Reduce the image size
It would also change from installing jdk-devel to jdk-headless.
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests profile=smoke

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=smoke

:x: Test Summary :x:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 3
PASS: 1
FAIL: 2
SKIP: 0
BUILD_NUMBER: 223
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testCreateDeleteAddressSpace in io.enmasse.systemtest.isolated.brokered.SmokeTest
testAddressTypes in io.enmasse.systemtest.isolated.brokered.SmokeTest

@enmasse-ci run tests profile=smoke

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=smoke

:x: Test Summary :x:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 3
PASS: 1
FAIL: 2
SKIP: 0
BUILD_NUMBER: 225
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testCreateDeleteAddressSpace in io.enmasse.systemtest.isolated.brokered.SmokeTest
testAddressTypes in io.enmasse.systemtest.isolated.brokered.SmokeTest

@enmasse-ci run tests profile=smoke

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 3
PASS: 3
FAIL: 0
SKIP: 0
BUILD_NUMBER: 228

@enmasse-ci run tests profile=shared

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: shared
TEST_CASE:
TOTAL: 139
PASS: 127
FAIL: 0
SKIP: 12
BUILD_NUMBER: 231


feat: #tno-1489 - no re-alerting on migration

after discussion with stakeholder (Scott) we can ignore the alert attribute
it's enough that an Editor can trigger a new alert manually if they choose

Keeps things simple 😃


Let Mbed TLS enable ENTROPY_GENERATOR when there is an entropy driver available on the platform

TL;DR
This is an alternative implementation of #82497 since this PR had issues and it was reverted in #82807.
Here Mbed TLS enables ENTROPY_GENERATOR on platforms that have an entropy driver available. In order to do this a new Kconfig is added, CONFIG_CSPRNG_AVAILABLE, which is set to true when the devicetree chosen property "zephyr,entropy" is set.
When the entropy driver is not available, then Mbed TLS enables CONFIG_TEST_RANDOM_GENERATOR instead.
Background
Enabling the entropy driver
By default when a platform has an entropy HW available in the SOC it does not get automatically enabled, but CONFIG_ENTROPY_GENERATOR has to be defined. The reason for this is that:

in the devicetree we have both the node specific to the entropy device and "zephyr,entropy" chosen property set;
in Kconfig we have the driver specific Kconfig (ex: CONFIG_ENTROPY_NRF5_RNG) enabled.

Since CONFIG_ENTROPY_GENERATOR is not enabled at "high level", the sub-Kconfig platform specific driver is not taken into account in the build so the driver is not enabled. This means that both CONFIG_ENTROPY_HAS_DRIVER and CONFIG_CSPRNG_ENABLED are not enabled by default.
Mbed TLS
Mbed TLS need a cryptographically secure random number generator (CSPRNG) to work properly from a crypto security point of view (key generation, signatures, etc). A test/fake random generator would work the same from a build point of view, but that would be extremely bad on the practical side because all crypto algorithms would become extremely weak and easily to attack.
Proposed solution
Since CONFIG_ENTROPY_HAS_DRIVER and CONFIG_CSPRNG_ENABLED are not enabled by default even on platforms that actually has an entropy IP there was no easy way for Mbed TLS to tell if CONFIG_ENTROPY_GENERATOR had to be enabled or not. What we can do is to add another help symbol, CONFIG_CSPRNG_AVAILABLE, which can be used to say something like: "if you enable CONFIG_ENTROPY_GENERATOR then you can achieve CONFIG_CSPRNG_ENABLED on this platfom".
Then when CONFIG_CSPRNG_AVAILABLE is not enabled, Mbed TLS "knows" that it has no other choice than enabling TEST_RANDOM_GENERATOR in order to be buildable. This is a bad implementation form a cryptographic point of view, there would be no better choice for such a platform a part from completely excluding all samples/tests that include crypto, of course.
History (How do we came here?)

In the TinyCrypt deprecation PR #79931 there were many boards/samples/tests changes which were simply aimed at enabling CONFIG_ENTROPY_GENERATOR to let Mbed TLS access some good entropy/random value source. Of course this was not really scalable.
One possible option was that the subsystem willing to make use of Mbed TLS had to enable CONFIG_ENTROPY_GENERATOR on its own, but that was not really elegant either because that subsystem (ex: bluetooth) might be platform agnostic and does not really care about how that stuff is implemented.
#82497 tried to overcome this problem by letting CONFIG_ENTROPY_GENERATOR auto-enabling whenever "zephyr,entropy" was set in the devicetree. However this caused a lot of side effects because entropy drivers started to be included in a lot of samples/tests which required ad-hoc fixes. That's why the PR was eventually reverted in #82807.

As reported by @dleach02 the fix introduced here is still failing in:
west build -p -b frdm_k64f/mk64f12 samples/bluetooth/peripheral_ht -T sample.bluetooth.peripheral_ht.frdm_kw41z_shield

As reported by @dleach02 the fix introduced here is still failing in:
west build -p -b frdm_k64f/mk64f12 samples/bluetooth/peripheral_ht -T sample.bluetooth.peripheral_ht.frdm_kw41z_shield

Is it really? I just checked out this PR branch and ran the above command, and it seems to build just fine.

I had to rebase to solve a conflict with main, but I did not change anything during the rebase so all the commits belonging to this PR are the same.

@valeriosetti there's another conflict in samples/bluetooth/st_ble_sensor/prj.conf that needs fixing.
After that, @ceolin @d3zd3z please have a look.


Update aver

Updating AVer code to use the latest visca library release.  We fixed an item and need it in place.

Pushed changes up and validated.


Zip exercises

Zipping works. Refactored tests.

Coverage decreased (-0.52%) to 84.98% when pulling 217840b5d0f871a2dd1bb4c37044a3a12f51f7b2 on zipExercises into<PHONE_NUMBER>6bc15ee223c9eed28bec71b162cea5 on master.


Increase Test Coverage

Unit tests sometimes let some errors slip through. Improved coverage would give it a more accurate output of if the code is working.

Test coverage has been improved to cover a significant portion of the current codebase.


added chest to recipe

I want to die.
Look at the issue

as referenced in #4 I will close this PR


GCMD Platform Keywords need to be updated

Describe the bug
The GCMD Platform Keywords were updated recently. pyQuARC is currently using the older version which causes errors that aren't valid.
To Reproduce
Steps to reproduce the behavior:

On the umm_g support branch, change the platform type to "Propeller" in the dif10 test file
Run pyQuARC
See error "Error: The provided platform type Propeller does not comply with the GCMD. Please submit a request to<EMAIL_ADDRESS>to have this platform type added to the GCMD Platforms KMS."

Expected behavior
No error expected since this is a valid platform type
Outputs
Error: The provided platform type Propeller does not comply with the GCMD. Please submit a request to<EMAIL_ADDRESS>to have this platform type added to the GCMD Platforms KMS.
Additional context
GCMD Platform Keywords were recently updated.

We already have this category, but it wasn't working because the GCMD url changed from gcmdservices.gsfc.nasa.gov to gcmd.earthdata.nasa.gov. Fixed in an upcoming PR.


Add accelerate support for Large Language Models

This PR adds accelerate support to run very large language models on lm-evaluation-harness 🚀
Tested on OPT-175 on JZ super computer (8xA100). In order to run properly you need:

Enough GPU RAM to put the model, OR
Enough GPU+CPU RAM using CPU offloading (slower) OR
Enough GPU+CPU RAM+ disk space (even slower)

Added new args:

--accelerate: activates accelerate offloading
--skip_tokenizer: skips the tokenizer check (to run BLOOM or any other model that uses a tokenizer that is different from GPT2)
In model_args (optional args):

max_memory that corresponds to the maximum memory you want to allocate on each GPU
device_map that corresponds to the device_map that is supported by accelerate. See the doc

Others:

Added support for inferring model that uses different tokenizer that GPT2Tokenizer (useful for BLOOM) here

Updated also the README to add examples and instructions, let me know if I should add anything else
cc @StellaAthena @thomasw21
cc-ing also @sgugger in cased I missed some important args for accelerate

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Executes but quickly leads to "Expected all tensors to be on the same device"

Hi,
I prepared a pdb for protein and one for ligand.  Libraries are all installed including Nvidia drivers on A100 40GB.
The following is the error message which is saying tensors are split on cuda:0 and cpu.
DiffDock will run on cuda
Generating ESM language model embeddings
Processing 1 of 1 batches (1 sequences)
HAPPENING | confidence model uses different type of graphs than the score model. Loading (or creating if not existing) the data for the confidence model now.
/home/xxx/anaconda3/envs/diffdock/lib/python3.9/site-packages/torch/jit/_check.py:181: UserWarning: The TorchScript type system doesn't support instance-level annotations on empty non-base types in __init__. Instead, either 1) use a type annotation in the class body, or 2) wrap the type in torch.jit.Attribute.
warnings.warn("The TorchScript type system doesn't support "
Size of test dataset:  1
0it [00:00, ?it/s]@> 2310 atoms and 1 coordinate set(s) were parsed in 0.02s.
@> 2310 atoms and 1 coordinate set(s) were parsed in 0.02s.
Failed on ['complex1'] Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu!
1it [00:00,  1.49it/s]
Failed for 1 complexes
Skipped 0 complexes
Results are in ./4wkq/output

Removing system CUDA and installing CUDA 11.7 plus its default Nvidia driver solves this error.


use the x86 nUnit runner to execute x86 assemblies

By default Giles does not inspect the assembly it is trying to load for platform information. Attempting to execute code compiled to x86 will cause the default nUnit runner to get mad.
giving us the good ole:
Could not load file or assembly 'GildedRose.Console, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.

old issue, x86 runner now solves this problem.


Problem when trying to contribute

I am trying to contribute LVideoOverlay.  I'm starting by simply copying LImageOverlay code and replacing where necessary.  I followed the steps to run code locally for contributors, however it seems to not be picking up the changes I made because running the (modified to include a video overlay) example gives the error "export 'LVideoOverlay' was not found in 'vue2-leaflet'.  I am running Windows, and this is the first time I've tried using Symlinks on Windows.  The yarn commands all execute successfully, and I'm running the command prompt as Administrator.

@carljones4 Thank you for wanting to contribute!
if yarn link is not working for you, you can try to follow this:
https://medium.com/@mtfranchetto/the-solution-for-a-working-npm-yarn-link-ddcb4f3c785e

Closing due to inactivity


How to avoid first page to load with default language and only THEN translate

Subject of the issue
Hi
I am using Angular-translate in my ionic (1) app. And translateChangeSuccess is fired AFTER my first page is loaded, so the user sees the default language, then it is changed to his language just before his eyes. Which is bad UX.
Can you please help me improve that ?
Thanks for yo uhelp
Your environment

version of angular-translate v2.8.1
version of angular ionic 1.3
which browser and its version Chrome Version 58.0.3029.96 (64-bit)

Expected behaviour
The first page should load with the right language

If you're using ui.router, you might consider placing an resolve with resolving your language in there.

As already said: eventually you will have to look for something like ui router's resolve method or similar ideas.