fix #1943 fix the bug of gitment

fix the bug of gitment, change document.location.href to document.location.pathname

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines.
[x] Tests for the changes have been added (for bug fixes / features).

[x] Muse | Mist have been tested.
[x] Pisces | Gemini have been tested.

[ ] Docs have been added / updated (for bug fixes / features).

PR Type
What kind of change does this PR introduce?

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

What is the current behavior?

Issue Number(s): N/A
What is the new behavior?
Description about this pull, in several words...

Screens with this changes: N/A
Link to demo site with this changes: N/A

How to use?
In NexT _config.yml:
...

Does this PR introduce a breaking change?

[ ] Yes.
[ ] No.

In #1943 instead of document — window. Are u test it?

@ivan-nginx I haven't tested it yet, just modify the file as what @icearith say. But I see somebody have tested it in https://github.com/imsun/gitment/issues/46.

This modification is cloud only be a hot-fix level solution for this issue, because this is a problem related to the design of Gitment. Some guys mentioned that Gitment should use permalink  in hexo to identify the unique post.
Although this solution is not 100% reliable, it could also improve the reliability of this plugin, because many links pass arguments to URLs, for example, http://a.com?from=baidu this is regarded as a different post from http://a.com.
This commit could solve this issue from URL level, the issues mentioned in https://github.com/imsun/gitment/issues/46 should be label as a upstream issue, which should be solved in upstream repository.

So? What's the difference between document and window?
Please, not need to add code into master if you not test it in realtime. NexT already have thousand bugs.

It's ok to close this PR, and wait somebody or me have better solution, then fix this bug.

@ivan-nginx I mean,  the point is that href is definitely wrong, pathname should be used.

It's ok to do 100% bugfix PR's. And it's ok to test all changes before make PR into master branch.
Guys, let me explain there something. There is 3 ways:

document.location.href
document.location.pathname
window.location.pathname

What's the right answer? :smiley:
P.S. I don't talk about «Oh no, u not tested it, this is wrong bugfix, etc.». A just talking about right way to fix.

I changed document.location.pathname to window.location.pathname.


Server Endpoints UI in Info section should be updated

Describe the issue:

Server Endpoints UI in Info section should be updated
The following Server endpoints should be removed

Web finger
Session Iframe
Dynamic Client Registration

How to reproduce:

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

@asekawa Can you give the reasoning behind the request to remove these?
Session iframe is required for an application using session management.
And this info was present in the resident idp configs. It makes sense to remove webfinger (as this is a server-level ep) and the DCR as this is needed to create the app mainly. But we need to have this info in some place

Webfinger endpoint> is redundant as the Discovery endpoint also serves the same purpose.
Session iframe > As @janakamarasena suggested we can enable this only for OIDC types of apps other than M2M and Mobile (i.e, enable for SPA, TWA - OIDC, Standard based - OIDC)
DCR > is needed before creating the application, It doesn't make sense after creating the application.
+1 to move this under a sensible server-level section. But not needed under each application.


Feedback on “Pod Topology Spread Constraints” concept

Pay attention to an extract from Implicit conventions:

any Pods located on those bypassed nodes do not impact maxSkew calculation - in the above example, suppose the node node1 does not have a label "zone", then the 2 Pods will be disregarded, hence the incoming Pod will be scheduled into zone A.

"in the above example" phrase is supposed to point to example: conflicting topology spread constraints (by meaning), presently it is formulated like it points to not appropriate previous closest example - example: topology spread constraints with node affinity what leads to misunderstanding

/retitle Feedback on “Pod Topology Spread Constraints” concept

Thanks for the comment @SlavaUtesinov
/language en
/kind bug
/priority backlog

/triage accepted

/assign

Fixed this issue by PR #43702

/close


"no sensors added" view is flickering every time when opening sensors

App version 1.11.5
See the video
https://user-images.githubusercontent.com/1311912/179400337-055aabaa-4682-485a-8ecf-53bccf3eb37d.mp4

@laurijamsa can you check it too?

QA passed


tr_shader: always iterate grouped stages

Fixes #1185:

https://github.com/DaemonEngine/Daemon/issues/1185

Alongside fixing #1185, this is something I wanted to do anyway, in order to move the next for loop after the first GroupActiveStages call to a dedicated function (this is a code validating shader stages and disabling invalid ones).
The bug is that we are now more agressive at disabling unsupported stages as soon as possible, and the stage validation code was stoping iterating the stages on first disabled stage found.
The material looks like this:
tremor/54ECD65C96E1201DEABD3DDB5B656605
{
	{
		map $lightmap
		rgbGen identity
	}

	// Q3Map2 custom lightstyle stage(s)
	{
		map $lightmap
		blendFunc GL_SRC_ALPHA GL_ONE
		rgbGen wave sawtooth 0 1 0 0.5 // style 1
		tcGen lightmap
		tcMod transform 1 0 0 1 0.45410 0.18457
	}

	{
		map textures/tremor/grate3.tga
		blendFunc GL_DST_COLOR GL_ZERO
		rgbGen identity
	}
}

Light styles are not supported on light modes ≠ 3 (light mapping), so it is expected the material is turned into this:
tremor/54ECD65C96E1201DEABD3DDB5B656605
{
	{
		map $lightmap
		rgbGen identity
	}

	{
		// disabled stage
	}

	{
		map textures/tremor/grate3.tga
		blendFunc GL_DST_COLOR GL_ZERO
		rgbGen identity
	}
}

But the loop doing an early break on the disabled stage, it turned the material into this:
tremor/54ECD65C96E1201DEABD3DDB5B656605
{
	{
		map $lightmap
		rgbGen identity
	}
}

Only painting the light with no texture blended over.

Once fixed, not only the engine properly removes the unsupported light style stage as expected while keeping the texture stage, producing something like this:
tremor/54ECD65C96E1201DEABD3DDB5B656605
{
	{
		map $lightmap
		rgbGen identity
	}

	{
		map textures/tremor/grate3.tga
		blendFunc GL_DST_COLOR GL_ZERO
		rgbGen identity
	}
}

But the collapsing code called after that even collapses the material into this:
tremor/54ECD65C96E1201DEABD3DDB5B656605
{
	{
		diffuseMap textures/tremor/grate3.tga
	}
}

C:\projects\daemon\src\engine\renderer\tr_shader.cpp(5654,29): error C2220: the following warning is treated as an error [C:\projects\daemon\build\client-objects.vcxproj]
C:\projects\daemon\src\engine\renderer\tr_shader.cpp(5654,29): warning C4018: '<': signed/unsigned mismatch [C:\projects\daemon\build\client-objects.vcxproj]

LGTM I guess.
It kind of sucks that we are doing GroupActiveStages() as many as 5 times. The stage struct is over 1k in size so it would be better not to copy it so many times.

Yeah but doing it that way makes such very convenient, and that time is only spent at load time… This is a very good trade-of given the huge simplification of code that provides. Maybe in the future we would be able to migrate to some more clever struct, but this is fine for now.


.NET 8: Enable full linux-portable CI build

Describe the Problem
Unified build seeks to expand the number of platforms that .NET 8 can source-build on, and replace the existing Microsoft official build with source-build. Part of this is enabling a build for the Linux portable assets we produce.
Describe the Solution
Enable a full linux-portable build of source-build in CI.

Covered in that other issue


INTEGRATED 829

Implemented the solr worker services.

New task can be registered by tagging them as integrated_solr.task and adding the task class as attribute.
Errors are logged by monolog with in the channel solr.

Can one of the admins verify this patch?

Approved!


Expose disk io metrics

Disk IO metrics are useful to identify disk bandwidth hogging application. Since containers typically share a local disk, these metrics will be very useful.

Good idea. I will take a look.

Any update on this ??

@vishh @mwielgus
I am now working on adding disk io stats metrics to Heapster. Did you have any thought about this? For example, which metrics should be collected and the metric names.
I  prefer to add both read and write bytes per second metric separately. With this original data, we can also get the aggregated bytes per second including both read and write.

/remove-lifecycle stale

Close this as disk io has been added to heapster with legacy source.
/close


feat: Fourier transform of iterated derivatives

We show that the Fourier transform of an iterated derivative is the Fourier transform of the original function multiplied by a power function. We deduce bounds on ‖w‖ ^ n * ‖iteratedFDeriv ℝ k (𝓕 f) w‖ in terms of integrals of iterated derivatives of f (up to order n) multiplied by power functions (up to order k).

The PR is a little bit longish. If you think it's too long, please complain, I can try to split it (although there is no natural splitting point, I can do it a little bit arbitrarily).

Thanks a lot for the great review! I have taken care of everything.

maintainer merge

bors r+


commonjs module export

This PR adds an export for commonjs if module object is found as well as adding an example built with browserify

Looks excellent - anyone got a mo to review this? I'm away on holiday currently
Cc @xStrom @nathanbedford @jmeas @reppners

I should have a chance to check it out later tonight.

@timruffles @nathanbedford Please see the latest changes - the code should not pollute global namespace anymore

@tonickkozlov much better, just one more thing: could you please update the readme to show an example of how to provided the module with a config object if used in a commonjs environment?

@nathanbedford please see the new changes

@tonickkozlov thanks for your persistence.  This will be a nice addition!


Langchain retrieval agents colab: Fix link to full example

The previous link was broken, probably because the target notebook moved at some point.

LGTM- thank you!


A number of features broken on docs sites

Search bar, accessibility menu, print button and mobile view sidebar expand button are all broken on our docs websites.

The issue is the docrender changes for accessibility need to be integrated into the cloud.

Fixed by https://github.com/Microsoft/pxt-backend/pull/28


Use CAPI/CAPZ defaulting for all resources

Towards https://github.com/giantswarm/giantswarm/issues/15570
This PR adds support for CAPI/CAPZ defaulting on all resources that support it. The patches are automatically generated based on the differences in the resources from before to after applying the defaults.
There are some messages below that hopefully explain my logic.

Tested again ✅


Import 1.6.2 and 1.7.0 changes

Import changes oreleased with the version 1.6.2 and 1.7.0.

Fixed on rebase


update publishing_api app to use new modules

This PR implements the Trello card and follows on from PR_24 and PR_27
Main changes made are:

apps/publishing_api module now calls modules/app and the copy-pasted common stuff is deleted.
push variables up to the govuk composition module.
names of AWS secrets are prefixed with publishing_api_app rather than publishing_api to
maintain consistency with other apps. The changes to AWS secrets were made via aws cli.

Checks done are:

terraform plan works but this has not been applied yet
terraform fmt

Future work:

verify that this PR does not break any functionality when applied.
refactor out some hard coded values that also exist in other apps modules

Thanks.


Don't stub getter properties

Sinon version : 1.14.1 Environment : node 0.12.2
I found that sinon.createStubInstance caused an error when the class has a getter property and the getter method uses a property initialized in the constructor.
Here is a code snippet to reproduce this error.
var sinon = require('sinon');

function C(o) {
    this._o = o;
}

Object.defineProperty(C.prototype, 'v', {
    get: function() {
        return this._o.v;
    },
    enumerable: true
});

var s = sinon.createStubInstance(C);

Here are the error messages.
/tmp/t.js:9
        return this._o.v;
                      ^
TypeError: Cannot read property 'v' of undefined
    at C.Object.defineProperty.get [as v] (/tmp/t.js:9:23)
    at Object.stub (/tmp/node_modules/sinon/lib/sinon/stub.js:53:38)
    at Object.sinon.createStubInstance (/tmp/node_modules/sinon/lib/sinon/util/core.js:356:26)

This patch makes sinon.stub access properties using getOwnPropertyDescriptor and not to call getters on an object.
What do you think?

What do you think?

I think this looks pretty good :+1:, however I'd like to see what @cjohansen and @mantoni think of it, before merging it

Seems fine with me.


What is the exact string of the default namespace?

FlyBase_miscellaneous_CV
?

Make sure it is in Chado load checks

Lets close this for now until it becomes an issue again.


bash: wp: command not found

Hi
I am trying to run on a Windows 10, and I get an error on installing, exactly on executing this:
heroku run wp core install \     --url=my-app-name.herokuapp.com \     --title="WordPress on Heroku" \     --admin_user="admin" \     --admin_password="correct-horse-battery-staple" \<EMAIL_ADDRESS>The error is this one:
Running wp core install ....(my app details here)..... on my-app-name... up, run.6039 (Free)
bash: wp: command not found

I have tried using CygWin, cmd.exe, git bash. Same error on all of them.
The wp.bat file path is added in my PATH variable. What else can I do?
Thank you.

Hey @fcristel, there's an existing issue for this that was fixed but I got the same thing. I've figured out what it was for me, might be the same for you. I needed to add my SSH key to Heroku first because the Git remote is set with --ssh-git.
https://devcenter.heroku.com/articles/keys#adding-keys-to-heroku
Add your SSH key to Heroku first, then you must delete your app, delete the Git repo and re-run from scratch or you'll get errors when trying to checkout your branch.
You can delete with:
heroku apps:delete your-app-name
Then just delete the entire heroku-wp folder and follow the guide again. Hopefully this helps :-)

If you're seeing bash: wp: command not found it's probably because you haven't made the initial commit which runs the build on Heroku and installs composer and wp-cli. When I ran init.sh I found myself in a branch with the name of my app which I didn't want. The init.sh tried to make "an initial commit" which I found dangerous to my repository. I started by developing locally before my first deployment. I'm not sure what the author was going for here.
I solved the issue by checkout master back out git checkout master, deleting that new branch which I didn't need git branch -D {that branch}, and making an initial commit to Heroku to run the build for the first time git push heroku master. After that it installed everything I was able to run the WordPress install command because composer and wp-cli etc were in place.


[Feature] multiple zendesk instances

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
We have multiple zendesk instances in our organization, how would I setup this package so that I can create the models for each of the zendesk instances we have.
(They are all in separate schemas; zendesk_concierge, zendesk, zendesk_partner_success, etc....)
Describe alternatives you've considered
No response
Are you interested in contributing this feature?

[ ] Yes.
[X] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[ ] No.

Anything else?
No response

hey there! we were actually heavily considering rolling this out in the coming quarter.
i am curious about your use case -- does each zendesk instance belong to a different department or subsidiary in your org?

hey there! we were actually heavily considering rolling this out in the coming quarter.
i am curious about your use case -- does each zendesk instance belong to a different department or subsidiary in your org?

Yes, we have 5 different zendesk instances and each belongs to a different organization in the building and different metrics, tickets, and tracking associated to it. In zendesk they're separated by different subdomains so there is an individual connector for each in Fivetran.

Gotcha! so the solution we were thinking of rolling out would union together these different instances' source data and produce 1 set of output models -- which you could split out into individual ones based on the source_relation column. would that work for your use case?

I think that would work. Thank you. Please keep me posted when you prioritize and plan to roll this out as our depts are bummed that ticket_metrics is the biggest table they aren't able to see at the moment.

Hi, I was wondering if you could provide an update on the progress of this issue @fivetran-jamie ? I am eager for this to be released!


Adding porch image builds for every PR merged tagged latest

Porch images will be built every merged PR and pushed to Docker Hub with tags: 'latest' and usual tag that's prow's job ID

/approve
/lgtm


Locks down public Service Bus endpoints

PR for issue #441
What is being addressed and how

Network rules added to Service Bus to allow connections from the subnets of the TRE API and the Resource Processor

Why are we suddenly using service endpoints when we have private link configured?
Happy to chat tomorrow.

@marrobi I couldn't get it working without the service endpoints - most likely due to my lack of expertise when it comes to Terraform. Let's keep this PR open until you get back and let's have that chat tomorrow.

Service Bus Networking blade after the change:

Access to the Service Bus from the outside is blocked:
Failed to send a Service Bus message: ServiceBusAuthorizationError: Ip has been prevented to connect to the endpoint.


remove unreachable statement

we're returning before this and it will never run
 140/365 = 0.3836

@miq-bot add_label cleanup

@gtanzillo @lpichler Please also review.

@gtanzillo @lpichler Please also review.


Password Length

Password Length
User Story
AS AN employee with access to sensitive data,
I WANT to randomly generate a password that meets certain criteria,
SO THAT I can create a strong password that provides greater security.
Acceptance Criteria
GIVEN I need a new, secure password,
WHEN prompted for the length of the password,
THEN I choose a length of at least 8 characters and no more than 128 characters.

Complete. See deployed site: https://nestibry.github.io/umn-bcc-mod03-password-generator/


Address dependency on package with high severity security vulnerability

The latest version of db-migrate depends on a package with a high severity vulnerability (https://github.com/advisories/GHSA-fwr7-v2mv-hh25). It is my understanding that db-migrate does not directly use the affected package async, but rather indirectly imports it via prompt.
Please switch to an unaffected version of prompt or replace it altogether (e.g. https://github.com/db-migrate/node-db-migrate/pull/778).

The latest beta tag series no longer requires prompt but I'm sure those of us using the 0.11.x series would like to see this resolved on that branch.
There is a new version of prompt with an updated async version, however, as noted in this commit, prompt still depends on an older version of winston which requires the old vulnerable async version:
https://github.com/flatiron/prompt/commit/4736c828879af1b35acb83928e12db3d02754a59
So I think prompt needs to also update it's winston dependency version and then db-migrate will be good (once updated of course).

As seen here getting prompt updated for winston is going to be work: https://github.com/flatiron/prompt/pull/226
The master branch of this project no longer uses prompt, so if someone wanted to do some git history diving and find out what change removed that dependency maybe the maintainer would be open to backporting that to the v0.11.x branch.

The master branch of this project no longer uses prompt, so if someone wanted to do some git history diving and find out what change removed that dependency maybe the maintainer would be open to backporting that to the v0.11.x branch.

Found it, a0432f1a6648cdc060e2d427fd1a5c8314c52c8d - which is listed as a breaking change so probably not something that would be backported to the v0.11.x series.

Found it, a0432f1 - which is listed as a breaking change so probably not something that would be backported to the v0.11.x series.

Thank you for examining this.
As a result of your research I tested 1.0.0-beta.18 on a couple of projects a large number of Postgres migrations, and it worked.
Would it be crazy to switch ... ? 😬

Found it, a0432f1 - which is listed as a breaking change so probably not something that would be backported to the v0.11.x series.

Thank you for examining this.
As a result of your research I tested 1.0.0-beta.18 on a couple of projects a large number of Postgres migrations, and it worked.
Would it be crazy to switch ... ? 😬

We upgraded to the latest beta version in one of our projects with no problem so it's not crazy. However, we tried doing the same in another project which is pretty similar and for some reason we now get hangs in our tests. I'm not sure if it's a bug in our project or not. But if the beta version works for you then that's probably the fastest and easiest way to resolve the CVE issue.
#627 also has some statements on the stability of the beta series.

Found it, a0432f1 - which is listed as a breaking change so probably not something that would be backported to the v0.11.x series.

Thank you for examining this.
As a result of your research I tested 1.0.0-beta.18 on a couple of projects a large number of Postgres migrations, and it worked.
Would it be crazy to switch ... ? grimacing

We upgraded to the latest beta version in one of our projects with no problem so it's not crazy. However, we tried doing the same in another project which is pretty similar and for some reason we now get hangs in our tests. I'm not sure if it's a bug in our project or not. But if the beta version works for you then that's probably the fastest and easiest way to resolve the CVE issue.
#627 also has some statements on the stability of the beta series.

Considering making the jump to 1.0.0-beta.18 from 0.11.x.  Did you happen to overcome the issues you were having in the project that was hanging during tests?

Winston published a new version 2.4.6 which fixes the vulnerability. Prompt is now taking the fixed version of winston so it seems the vulenerability is fixed on<EMAIL_ADDRESS>npm ls:

Thanks for the pointer @travivi This did the trick for me 👍


Update tensorflow:grpc++

Updated targets to //tensorflow:grpc++ from @com_github_grpc_grpc//:grpc++
Closes #51770

Hi @ishark @yuefengz , could you please have a look at this PR? Thanks!

Hi @ccrusius , could you please have a look at this PR? Thanks!

Hi @ccrusius Can you please review this PR ? Thank you!

Hi @ccrusius , could you please take a look at this PR? Thanks!

Those particular lines in the BUILD files are automatically re-written when we export our internal repository to GitHub. @ishark would have a better idea about how to deal with this - Isha, could you take a look?

Hi @ishark , could you please take a look at the issue in BUILD files? Thank you very much!

@sachinprasadhs Can you please resolve conflicts? Thank you!

@sachinprasadhs Can you please resolve conflicts? Thank you!

This should happen at the same time as upgrading protobuf. That one is blocked.

Closing as blocked by protobuf update. When protobuf updates this will also be updated, so the PR will be obsolete


[Monitor][Ingestion] Allow IO type in upload

Typing for logs argument is changed to indicate an IO type can be passed in. An IO type is checked for and passed in as is without chunking.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-monitor-ingestion


Cross-resource group volume restores don't work for Azure

In Azure, all resources are contained within a resource group (RG). If a user takes a backup, including PV snapshots, in Cluster A, which is contained in RG A, then tries to restore it into Cluster B, which is contained in RG B, this will fail. The issue is that we take a resource group as part of the cloud-credentials secret for Azure, and this value is used for both fetching snapshots and creating volumes.
We need to keep track of the RG where the snapshot exists so that we can correctly locate it. We could do this by capturing the full resourceID of the snapshot in VolumeBackupInfo and using that when restoring.

I was able to get this working by storing the full snapshot URI rather than just the name within the backup status, and parsing it during restore to figure out which RG the snapshot was coming from.

@skriss Is this something I can do? Or code-related?

Something like this?
"status": {
    "version": 1,
    "expiration": "2018-04-05T00:36:26Z",
    "phase": "Completed",
    "volumeBackups": {
      "pvc-9b7fa5fc-20d2-11e8-af30-000d3a1d304f": {
        "snapshotID": "/subscriptions/SUBID/resourceGroups/MYRGNAME/providers/Microsoft.Compute/snapshots/MYRGNAME-dynamic-pvc-9b7fa5fc--2f3bba47-310a-4078-85de-269b844a2d41",
        "type": "Premium_LRS"
      },

@stephenlawrence we'll have to make a code change to support this; the restore process won't work correctly if it finds a snapshotID with the format you provided. I'll review the proposed code change with @ncdc today.


Parse JSON inside prism-http

Chore summary
The JSON parsing logic is currently a responsibility of prism-http library clients. Here is how it looks in prism-http-server: https://github.com/stoplightio/prism/blob/master/packages/http-server/src/server.ts#L41. The goal is to move that logic to prism-http.
The reason behind:

modules should have clear interface, having an exception for JSONish content is not clear for the user
detecting a JSON is tricky, content-type might be application/something+json
a client of prism-http might not be aware that he needs to detect JSON content and parse it. It just adds complexity

Tasks

[ ] Move detecting and parsing of JSON content to prism-http module
[ ] Change types, so that body must be a string (or undefined)
[ ] Remove parsing logic from prism-http-server
[ ] remove parsing logic from request-maker (introduced in https://github.com/stoplightio/request-maker/pull/149)

Closing as this is as it is not relevant anymore.


New User: Moneytree

Moneytree is a leading personal finance application that supports over 1,300 financial institutions in Japan.
Please fill the following out:

Name: Moneytree
Homepage url: https://moneytree.jp
Brand Guidelines/Licensing: N/A
Logo: Attached below.

Nice, wanna open a PR for it? Here's some examples

@thejameskyle Done: https://github.com/babel/babel.github.io/pull/558


MangaPark - Switch numbers to strings

You might be busy with other things but I thought this was a good idea.
https://github.com/inorichi/tachiyomi-extensions/pull/2163 has been sitting there for a while.
I wasn't sure what your exact thoughts were but just going off of the review that arkon left, I switched the numbers to strings.
This PR ensures you still get credit for the original idea of for mangapark source filtering.
Feel free to edit any of it as well.

Actually, I just realized that because I ended up forking your patch, I have your commit on my branch now.
This PR was originally was to ensure you got credit for your edit. If you do pull, it will update the pull that you opened on the main branch or I could submit the patch as well if you are too busy too.
Hope everything is going well.


World2Data plugin behaves weird when installed in mac and win

🐛 Bug
To Reproduce
Steps to reproduce the behavior:

Install World2Data plugin
World2Data plugin is included in the Installed Plugins section and it is checked

Close the Plugin Installation window
Click on Plugins menu

WINDOWS behavior: world2data menu is not displayed

MAC behavior: world2data menu is displayed as expected

On MAC, open the plugin installation window
Look for the world2data plugin and uncheck it
Close the window and click on the Plugin menu again

plugin remains in menu when unchecked, this change is not caught by the app
https://user-images.githubusercontent.com/63799148/157516223-4f085c59-508a-4448-9486-0124a31c2d9c.mo
Environment
napari: 0.4.15rc3
Platform: macOS-11.6.4-x86_64-i386-64bit
System: MacOS 11.6.4
Python: 3.9.10 | packaged by conda-forge | (main, Feb 1 2022, 21:28:27) [Clang 11.1.0 ]
Qt: 5.12.9
PySide2: 5.13.2
NumPy: 1.22.3
SciPy: 1.8.0
Dask: 2022.02.1
VisPy: 0.9.6
napari: 0.4.15rc3
Platform: Windows-10-10.0.17763-SP0
Python: 3.8.12 | packaged by conda-forge | (default, Oct 12 2021, 21:22:46) [MSC v.1916 64 bit (AMD64)]
Qt: 5.12.9
PySide2: 5.13.2
NumPy: 1.22.3
SciPy: 1.8.0
Dask: 2022.02.1
VisPy: 0.9.6

Weird, thanks :) Did this happen for other plugins, too? I will check this.

I can't reproduce the macOS part of this.
Can someone with Windows see if the plugin works?
It's npe1.


Clean up Sublist exercise and fix warnings

Clean up Sublist exercise
Add white space around brackets for better readability
Fix remaining OCLint warnings

@masters3d

Nice work!


Rename _type to type_ for field names

https://github.com/AngryLawyer/rust-sdl2/search?utf8=✓&q=_type
I guess type_ better fits normal conventions?

Yeah sure


Allow to deploy services in different resource groups

Description
Typically activity tracker resources would be in an audit related resource group, and logging/monitoring would be in an obvervability one.

FYI, the ability to create COS resources in a different resource group has been indirectly addressed in https://github.com/terraform-ibm-modules/terraform-ibm-observability-da/pull/175 using new optional input cos_resource_group_name.
There are however further discussions continuing in https://github.com/terraform-ibm-modules/terraform-ibm-observability-da/issues/189


java.lang.IndexOutOfBoundsException: index=2 length=2 capacity=0

curl -X GET -H 'Accept: application/sbe' -H 'X-MBX-SBE: 1:0' 'https://api.binance.com/api/v3/exchangeInfo' | java -jar ./target/sbe-sample-app-1.0-SNAPSHOT.jar -
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0curl: (6) Could not resolve host: application
curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535
curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535
Exception in thread "main" java.lang.IndexOutOfBoundsException: index=2 length=2 capacity=0
at org.agrona.AbstractMutableDirectBuffer.boundsCheck0(AbstractMutableDirectBuffer.java:1716)
at org.agrona.AbstractMutableDirectBuffer.getShort(AbstractMutableDirectBuffer.java:366)
at spot_sbe.MessageHeaderDecoder.templateId(MessageHeaderDecoder.java:126)
at com.binance.sbe.sbesampleapp.App.main(App.java:233)

@wuhewuhe The SBE is only available for Spot Testnet for now: https://testnet.binance.vision/api/v3/exchangeInfo
When it's available in the live exchange, it'll be announced here: https://github.com/binance/binance-spot-api-docs/blob/master/CHANGELOG.md


Add support for Gradle 5+

Fixes #274

Thanks @vkryachko for this PR. Do we have latest version with this fix in?

@evant Thanks for merging. Would you be able to cut a release with this fix and publish it on plugins.gradle.org?

There were some other changes that needed to be made, working on it


Vlen readonly

[Description of PR]

Fixes #514

TODO:

[ ] Unit tests and/or doctests in docstrings
[ ] Tests pass locally
[ ] Docstrings and API docs for any new/modified user-facing classes and functions
[ ] Changes documented in docs/release.rst
[ ] Docs build locally
[ ] GitHub Actions CI passes
[ ] Test coverage to 100% (Codecov passes)

Hello @ivirshup! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file numcodecs/tests/test_vlen_utf8.py:

Line 89:42: W292 no newline at end of file


Input type in the text description should be textarea

As you can see the current input type seems to be text hence we cannot add new line .

I want to work on this under JWoC'22

@r3yc0n1c  Assigned the issue to you , for any problem reach out to us on discord .


Update egg-pterodactyl-mohist.json

Add Java21 and convenience description

Sorry but #33 did this all in one go


Reproduce the numbers you reported

Hi @kkahatapitiya ,
Thank you in advance for your excellent work!
As you mentioned in your README.md: "use this evaluation script to reproduce our reported numbers."
I want to know where I can get your results (such as this "test_submission_localize.txt", which is required by "Charades_v1_localize.m"), because I want to reproduce the numbers you reported.
I'm looking forward to your reply!
Thanks

localize_corr_v1.csv is the file you are looking for.

Hi,
Does this mean I can type the command line below directly in MATLAB?
[rec_all,prec_all,ap_all,map]=Charades_v1_localize('localize_corr_v1.csv','Charades_v1_test.csv');

Yes, I think so. The annotation file should be Charades_vu17_validation.csv

Yes, It solved my problem. Thanks.


chore: retain conformance.yaml supported versions

keep the three most recent release conformance.yaml files

after this change is merged and the CI job run, a pull request will be triggered to remove all conformance.yaml prior to v1.28


Vampire drain not effected by apprentice stone

Describing the bug
As the title states, Vampire Drain is not effected by the apprentice stone. The Novice level spell should not cost magicka when cast but it does. (Have not tested other vampire spells)
To Reproduce
Just use Vampire Drain while under the effect of the apprentice stone.
Expected behavior
It should not drain magicka

Please follow the bug report template... I need saves, I can't just waste time setting up the same scenario when looking into these issues.


Histograms and Buckets

Left the sampling methods as a todo for next round. I'll do that once the basic design is stabilized.
Fixed a minor typo in the membership maps as well.

Maybe the information has to be folded into the Bucket class – the buckets could have left and right margins.


Python interface: 'level' for Certainty is missing

The Certainty attribute in the English language model has a marker, span and level. When using the m_index property in the Python interface, the marker can be found through ['sent_attributes'], the span through ['path_attributes']. The level, currently either 0 (uncertain) or 9 (certain), should be in ['sent_attributes'] too, but it is missing.
Example:
Input = "This might be a problem."
['sent_attributes'] = [{'type': 'Certainty', 'offset_start': 7, 'offset_stop': 12, 'marker': 'might', 'value': '', 'unit': '', 'value2': '', 'unit2': '', 'entity_ref': 1}]

Version 1.0.3 solves this Issue.


ARK SE: Force Close Windows

Force close ShooterGameServer.exe - Windows
Feature Information:
ShooterGameServer.exe can crash or hang on occasion, but the windows process does not fully close. When this happens the "Stop" server button does not function. This is because the doexit command will never complete as the server is not responding.
Please could a timer be added, so that after doexit is run if it does not successfully close after x time then the process will be forcefully closed. The only work around for this currently, is to fully close and restart the instance which is not always ideal if the admin only has permissions within that specific instance.
I confirm:

[x] that I have searched for an existing feature request matching the description.

The generic instance type has replaced this.


feat: add wolfi support

Signed-off-by: Sertac Ozercan<EMAIL_ADDRESS>Add Wolfi-based image support. This does not support distroless alpine.
Closes #38

Codecov Report
Base: 34.45% // Head: 34.12% // Decreases project coverage by -0.34% :warning:

Coverage data is based on head (ab7a059) compared to base (8d4a9c0).
Patch coverage: 4.76% of modified lines in pull request are covered.

:exclamation: Current head ab7a059 differs from pull request most recent head 1a38503. Consider uploading reports for the commit 1a38503 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   34.45%   34.12%   -0.34%
==========================================
  Files          12       12
  Lines        1126     1137      +11
==========================================
  Hits          388      388
- Misses        717      728      +11
  Partials       21       21

Impacted Files
Coverage Δ

pkg/pkgmgr/apk.go
44.18% <0.00%> (-3.32%)
:arrow_down:

pkg/pkgmgr/pkgmgr.go
16.86% <33.33%> (-0.42%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


[Monitoring V2 UI] Update k3s defaults to also enable k3sServer

Related Backend Issue: https://github.com/rancher/rancher/issues/29445
Context
Once the fix for the above issue is merged in with https://github.com/rancher/charts/pull/786, a new exporter k3sServer will be introduced. To support both the original released version and the new released version, we need to support setting both k3sServer.enabled and k3sControllerManager.enabled / k3sScheduler.enabled / k3sProxy.enabled to true by default for k3s clusters.
Specific changes requested
Basic Configuration
Related Issue (already merged): https://github.com/rancher/dashboard/issues/908
The Basic Configuration for Monitoring should be updated to additionally set k3sServer.enabled=true if the Cluster Type is detected to be k3s. We will continue to set k3sControllerManager.enabled / k3sScheduler.enabled / k3sProxy.enabled to true if the Cluster Type is detected as k3s to support the older version of the rancher-monitoring chart.
If the rancher-monitoring version is 9.4.200 or below, the k3sServer.enabled flag will be ignored in favor of k3sControllerManager.enabled / k3sScheduler.enabled / k3sProxy.enabled. If the version is 9.4.201+, the opposite will happen.
Advanced Configuration
Related Issue (pending merge): https://github.com/rancher/dashboard/issues/909
The Advanced Configuration Exporters section will need to be modified for k3s but this will depend on the rancher-monitoring version that is used.
If the rancher-monitoring version is 9.4.200 or below, we should see exactly what was detailed on the original ticket.
However, if the version is 9.4.201+, for k3s clusters only we should see the following:

Header / Label Name
k8s YAML
Description
Input
Default

Export K3s Server Metrics
k3sServer.enabled
N/A
boolean
true (disabled for all clusters except k3s when the rancher-monitoring version is 9.4.201+)

This issue impacts https://github.com/rancher/dashboard/issues/908 and .

I'll update this issue once more once the backend changes are in, but @westlywright does this look okay to you?
I'm specifically concerned about the upgrade case in that a user who already has rancher-monitoring deployed in version 9.4.200. Is it possible for us to update their values.yaml on an upgrade with the following logic:
If k3sControllerManager.enabled or k3sScheduler.enabled or k3sProxy.enabled, then k3sServer.enabled

If this is not possible, then a user who migrates from 9.4.200 to 9.4.201 will see all of their metrics collected for kubeProxy / kubeScheduler. / kubeControllerManager disappear on the upgrade since the PushProx exporters will be removed and nothing will replace it.

This is validated on rancher:v2.5-0465f049780def811e00ab32067f95734f6a88f5-head single-install with the latest UI.
case 1: fresh installation of monitoring v2 9.4.201 on k3s cluster
Both the new k3sServer and existing k3sControllerManager, k3sScheduler, and  k3sProxy are enabled.
Monitoring is deployed successfully and functional.

case 2: upgrade monitoring form 9.4.200 to 9.4.201
The following changes are applied when upgrading the monitoring app, and we can see the existing k3sControllerManager, k3sScheduler, and  k3sProxy components are removed with only .enabled: true left, and the new k3sServer is added

Monitoring is deployed successfully and functional after upgrading.


Constant: with or without sigil?

The docs are currently vague on the use of sigils in constants.
In 5to6-nutshell:

In Perl 6, constant is a declarator for variables, just like my, except the variable is permanently locked to the result of its initialization expression (evaluated at compile time).
So, change the => to = , and add a sigil.

But some examples do not actually use sigils, and in Terms this is explicit:

Constants are declared with constant and do not require a sigil. The RHS is evaluated at compile time, what may be too early to make sense.

So, regardless of whether they are required, I think the docs should at least be consistent in what they recommend, and this should probably be reflected in the examples.
Thoughts?

Sigilless variables.
Also relevant?

There is no recommendation possible because sigils provide interface as explained all over the place (because the behaviour provided by a sigil depends on context). No sigil is also a sigil (implicit binding) but 5to6 is a bad place to explain that. The recommendation for one who wants to port Perl 5 code will most likely make sense.
EWONTFIX, closed


train_on_batch for multiple predictions

Hi,
I'm not pointing a problem, I'm just wondering how I can manage to do what I want. I explain myself :
For an image X, the Y that I want to predict is a couple of numpy array [Y1, Y2]. Y1 is (38, 60, 18) shaped and Y2 is (38, 60, 72) shaped. As I am working with a big dataset, I would like to use the train_on_batch function. However, this function should take a numpy array of X  values (which is not a problem) and a numpy array of Y values. Because Y1 and Y2 are not of the same shape, I can't stack them into a single array, and using a list raise an exception because train_on_batch calls the Y shape. Does anyone has an idea about how I can trick that ?
Thanks for reading

If by "I want to predict is a couple of numpy array [Y1, Y2]", you mean that that you want to predict multiple outputs from the same model, you could opt for using functional api to build a model which allows a model to have multiple outputs and thus while using train_on_batch, you could supply the different outputs as a list and won't have to pass them in a single concatenated array.


Cannot use styled-jsx in next.js 3.0 project

Here's the error I'm getting on server startup:
Module build failed: ReferenceError: [BABEL] ./pages/learn/course.js?entry:
Unknown option: ./node_modules/styled-jsx/babel.js.inherits.
Check out http://babeljs.io/docs/usage/options/ for more information about options.

A common cause of this error is the presence of a configuration options object
without the corresponding preset name. Example:

Invalid:
  `{ presets: [{option: value}] }`
Valid:
  `{ presets: [['presetName', {option: value}]] }`

For more detailed information on preset configuration,
please see http://babeljs.io/docs/plugins/#pluginpresets-options.
(While processing preset: "./node_modules/styled-jsx/babel.js")

My .babelrc
{
  "presets": [
    "next/babel",
    "styled-jsx/babel"
  ]
}

Package versions:

next 3.0.3
styled-jsx 1.0.10

Why are you adding styled-jsx/babel to Next.js?  I was following the setup in this project's readme. Thanks!


Unable to use class decorator with static member functions

TypeScript Version<EMAIL_ADDRESS>Code
@testDecorator()
export class TestClass {

    public static create() {

        return new TestClass();
    }
}

Expected behavior:
<EMAIL_ADDRESS>generates the correct code. Here the static function "create" uses the decorated constructor function (the variable declared in the first line).
var TestClass = (function () {
    function TestClass() {
    }
    TestClass.create = function () {
        return new TestClass();
    };
    TestClass = __decorate([            <-- correct position
        testDecorator()
    ], TestClass);
    return TestClass;
}());
exports.TestClass = TestClass;

Actual behavior:
<EMAIL_ADDRESS>generates the wrong code. Here the static function "create" uses the variable declared in the first line, but this is not the decorated constructor function.
var TestClass = (function () {
    function TestClass() {
    }
    TestClass.create = function () {
        return new TestClass();
    };
    return TestClass;
}());
TestClass = __decorate([           <-- wrong position
    testDecorator()
], TestClass);
exports.TestClass = TestClass;

For a detailed code sample look at #10840.

@rbuckton : From my point of view this bug still exists in the latest nightly. Could you please give me a feedback why the position of the decorator code was changed or is there a plan to fix it?

@ahagelstein: If, for example, you wanted to have a decorator that set writable to false to make a static field read-only, this would not work if static assignments occurred after decorators were run. We will not be changing the emit for decorators until the official proposal for decorators for ECMA-262 advances, as it is a significant change from the current approach.

What I need for my implementation is a decorator which monitors the constructor function of the decorated class (see #10840). If an instance is created the decorator code is called because the decorator creates a new construtor function for the class (a kind of inheritance).
With<EMAIL_ADDRESS>there is no problem.
But with<EMAIL_ADDRESS>the code of the decorator has moved (see example above) and the decorator code is no longer visible from a static method within the class. If I create the instance outside the decorated class the code works.
Is the NEW position of the decorator code in<EMAIL_ADDRESS>the final position?

Closed with #12247. Thanks.


20H2 OS Version is not available for Lenovo Models

On what model are you trying to apply the drivers ?

I am trying to get Lenovo Models for Windows 10 20H2. Despite full internet access, tool is not able to query the catalog site. I think that's why I am not able to select 20H2 in drop down.
I am using the stable release 6.4.9

have you applyed the exe with the lenovo fix, or only run the installer? i had the same at first, but after updating the exe it works fine

Yes, @AlkHacNar is right, you need to update the tool to the latest version


Long-press not detected in iOS 13

The demo fiddle works in 14 but not 13.
This is because both support pointer events, but 13 doesn't fire pointerdown until the same time it fires pointerup - when you release your finger.
I'm not actually using this library, I ran into the issue in my own code and wondered if this might have the same problem.

I think this may just be browserstack


x/tools/cmd/godoc: godoc shows initializers for unexported fields

http://tip.golang.org/pkg/go/types/#pkg-variables:
var Typ = [...]*Basic{
    Invalid: {Invalid, 0, "invalid type"},
    [...]
}

http://tip.golang.org/pkg/go/types/#Basic:
type Basic struct {
    // contains filtered or unexported fields
}

It seems somewhat inconsistent that godoc would hide unexported fields from the Basic type description, but then show the values used to initialize them within Typ.  It's not legal for users to write types.Basic{types.Invalid, 0, "invalid type"}.

In general godoc shows the initializers unmodified. It is up to the code author to put something useful there (or not). In this case if the definition of Typ should be hidden then the idiom is
var Typ [...]*Basic = basicTypes

var basicTypes = [...]*Basic{...}

That is, I don't think this is a bug in godoc.


Provide some default output when tool is signing

Is your feature request related to a problem? Please describe.
It was not clear to me that the tool was working due to other issues in my CI, see background in https://github.com/dotnet-foundation/wg-maintainers/issues/90#issuecomment-1684531111. This caused me to spend a lot of time poking the sign tool than finding my ultimate problem in my build configuration.
It wasn't until I did --verbosity Debug that I saw it actively doing things, but that was hard to find out to even turn on as an option as that PR is still open #541.
Describe the solution you'd like
It'd be nice at minimum for the tool to spit out something like
13 Packages Signed

to the console, or maybe even better like:
Signed CommunityToolkit.Uwp.Animations.nupkg
Signed CommunityToolkit.Uwp.Behaviors.nupkg
...
13 Packages Signed

Then maybe there should be an additional -s|--silent parameter which suppresses this default output if it's unwanted.
Describe alternatives you've considered
🤷♂ don't know how else this would have gone differently since the tool doesn't give me any information outside a success code. Since it's meant to run in a CI, it's not something you generally try and test and poke locally.
It would have been nice to have more docs on the CLI parameters discoverable from the readme of the repo though, hopefully #541 on that side can be merged soon.
Additional context
Version: 0.9.1-beta.23356.1
Background: https://github.com/dotnet-foundation/wg-maintainers/issues/90#issuecomment-1684531111

Related to this, I actually noticed that most of the messages are coming at the Information verbosity level, many which seems like would make better Debug level messages, leave Information for starting signing, number of signed files, finished signing...
Many of the CreatePrimarySignatureAsync messages seem like a Debug level message, along with the temp files created from the other ones, anything related to those seems like Debug info... e.g.
Rebuilding container C:\Users\runneradmin\AppData\Local\Temp\rymbx5eo.si2\ejyysss0.nupkg from C:\Users\runneradmin\AppData\Local\Temp\aonx4b4a.lhu.
info: Sign.Core.INuGetSignTool[0]
      Signing C:\Users\runneradmin\AppData\Local\Temp\r1g1wxhd.2ax\wotgur5g.nupkg.


Error after running 'make' command

Hi, I am running Ubuntu 16.04. Tesseract-3.05, leptonica-1.74
I was running Tesseract-4.00.00alpha previously and used QT box editor to edit box files. I couldn't train version-4 and so decided to roll back to 3.05 on account of more help being available.
So I installed 3.05 but after that QT box editor wouldn't run. So i removed it, and decided to install it again.
But now I am getting this error after running the 'make' command.
g++ -m64 -Wl,-O1 -o qt-box-editor-1.13dev temp/main.o temp/MainWindow.o temp/ChildWidget.o temp/DelegateEditors.o temp/TessTools.o temp/SettingsDialog.o temp/GetRowIDDialog.o temp/ShortCutsDialog.o temp/FindDialog.o temp/DrawRectangle.o temp/qrc_application.o temp/qrc_QBE-GNOME.o temp/qrc_QBE-Faenza.o temp/qrc_QBE-Oxygen.o temp/qrc_QBE-Tango.o temp/moc_MainWindow.o temp/moc_ChildWidget.o temp/moc_DelegateEditors.o temp/moc_SettingsDialog.o temp/moc_GetRowIDDialog.o temp/moc_ShortCutsDialog.o temp/moc_FindDialog.o temp/moc_DrawRectangle.o   -L/usr/X11R6/lib64 -llept -ltesseract -lQt5Svg -lQt5Widgets -lQt5Gui -lQt5Network -lQt5Core -lGL -lpthread
//usr/local/lib/libtesseract.so: undefined reference to `pixReadFromMultipageTiff'
//usr/local/lib/libtesseract.so: undefined reference to `pixReadMemFromMultipageTiff'
collect2: error: ld returned 1 exit status
Makefile:200: recipe for target 'qt-box-editor-1.13dev' failed
make: *** [qt-box-editor-1.13dev] Error 1

If I understood it correctly: this error message is  not coming from qt-box-editor (it does not use this function) but from tesseract and it is related to leptonica.
Do you have more leptonica version in you system?
The missing functions were added to leptonica 2 year ago). So it should be part of 1.74 version (anyway I would suggest to user recent version 1.75.3)

I am currently using Leptonica-1.74.4
I will try to install 1.75.3 and see if the problem vanishes
Thanks.

So, I realised what was causing the issue (probably). As per the INSTALL guide in your package, I was installing libleptonica-dev using
sudo apt-get install libleptonica-dev
This was installing libleptonica-dev version 1.73.1
I had also separately installed leptonica-1.75.3.
I still got the same error as before.
So, I removed libleptonica-dev package
sudo apt-get remove libleptonica-dev
And then ran the make command which ran successfully and now QT box editor is running as before.
As per my understanding libleptonica-dev and leptonica (both installed separately) are different packages. But I guess I am wrong. Because as per documentation QT requires libleptonica-dev but I have only leptonica and QT is working fine.
Please correct me if I am mistaken
Best Regards

You are mixing topics: libleptonica-dev is package of development files of leptonica library.
So you had installed 2 version of same library (but they provide different features). Advanced users should know how to handle such situation.
From my experiences to have installed more version of leptonica (or tesseract) is just source of pain...


Choose single assertion library and test engine

Expected Behavior
Project uses a single assertion library and a single JUnit test engine.
Current Behavior
Assertion libraries in use:

kotlin-test
AssertJ
JUnit Jupiter

Both JUnit and Spek are used as test engines.
Context
It's easier to contribute when a single assertion library and a single test engine is used across the project. Tests will complete more quickly on first run and in CI (fewer dependencies to pull) and may execute more quickly as well.
Assertions
Jupiter can be removed easily - it's only used in a single test (possibly by accident?). kotlin-test's assertions are very basic and would be easy to replace with AssertJ. It would be cumbersome to go the other way, as kotlin-test doesn't have a fluent API.
Propose using only AssertJ for assertions. DONE!
Test Engine
The project uses Spek much more than JUnit. However, Spek 2 is on the horizon (now at RC1). If migrating to Spek 2, majority of Spek tests would need to be modified to take advantage of improvements. JUnit is better supported both by maintainers and with external libraries and has better IntelliJ integration, though migrating to Spek 2 would be simpler.
Propose selecting either JUnit or Spek as the preferred test engine, and migrate tests accordingly (though if Spek is chosen, first migrate the JUnit tests to Spek 1, and handle Spek 2 migration separately if desired).

As you said, I'd go with spek2 after migrating everything to spek1 from junit5.
I've started using spek1 2 years ago but had to switch to junit5 for a while as there were some bugs/breaking things in the intellij plugin.


feat: add forking branches

That's good. How about the weird reverse case of uploading a new project that's blatantly a fork of an existing one, but with all the git history erased?

It's super common in grant applications to crypto-currency projects.


[ISSUE] When using non-default registries, the keycloak initContainer will use the wrong image name

Describe the issue:
This issue was found during testing of the AWS Marketplace installation method. the initContainer in keycloak's subchart improperly sets the image name.
helm template\
    -f ~/test6/values.yaml \
    -f ~/test6/values-aws.yaml \
    --show-only charts/identity/charts/keycloak/templates/statefulset.yaml \
    charts/camunda-platform | grep -e "image:" -e "name:"

Values files linked below
Output:
...
          image: '709825985650.dkr.ecr.us-east-1.amazonaws.com/camunda/identity:8.4.0'
          name: copy-camunda-theme
            name: camunda-theme
          image: '709825985650.dkr.ecr.us-east-1.amazonaws.com/camunda/camunda8/keycloak:22.0.5'
          name: copy-configs
            name: config
            name: quarkus
        - name: keycloak
          image:<PHONE_NUMBER>50.dkr.ecr.us-east-1.amazonaws.com/camunda/camunda8/keycloak:22.0.5
  ...

Notice how the identity image should be camunda/camunda8/identity  instead of camunda/identity.  in the values-aws.yaml, we specify a different registry.

Actual behavior:
Image name for this initContainer is currently:
image: '709825985650.dkr.ecr.us-east-1.amazonaws.com/camunda/identity:8.4.0'

Expected behavior:
Image name for this initContainer should be
image: '709825985650.dkr.ecr.us-east-1.amazonaws.com/camunda/camunda8/identity:8.4.0'

How to reproduce:
See top of issue

Logs:
ImagePullBackOff

Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

Platform: AWS Marketplace
Helm CLI version: 3.11.0
Chart version: 9.0.2
Values file: values-aws.yaml.txt
values.yaml.txt

Fixed by: https://github.com/camunda/camunda-platform-helm/issues/1449
Now it's possible to set the Identity image inside Keycloak via global.identity.image.


fix(build): add pack step to build to create a tarball

This is for the staging link, due to npm 5 update

@joshuawilson fabric8/fabric8-ui:SNAPSHOT-PR-2323-1 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2323-fabric8-planner.badger.fabric8.io


BUG: Kundera Cassandra CQL still requires thrift port to be open

When looking CassandraSchemaManager.initiateClient it seems that native protocol is not being used, only thrift, even for CQL.
Since 2.2 (or was it 3.0?), thrift port is not even open by default because it is being phased out.

@hkroger
Yes, thrift port is being phased out and we are planning it in our future releases.
Let us know if you want to work on this with us. Also check out contribution guidelines.
-Karthik


Add new language file (Bangladesh Bangla lan.)

i create Bangla language file for  bootstrap-datepicker  . bangla formate date picker . bangla people want bangle date picker then i create bangla date picker for bootstrap-datepicker . i think its file useful for bangla people . please add this file and used all bangla people
Best Regard
Karim Khan

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Related tickets
fixes #X, partially #Y, mentioned in #Z

License
MIT

Hi @karim-khan
Thanks for your contribution! You've only created a minified file, but we generate these files automatically. So to add a new language you should create a new file in  js\locales directory


cmd/cgo: generated code uses aliases even in modules using Go older than 1.9

Go version
go version devel go1.23-722d59436b Thu May 16 02:00:26 2024 +0000 linux/amd64
Output of go env in your module/workspace:
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/dominikh/.cache/go-build'
GOENV='/home/dominikh/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/dominikh/prj/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/dominikh/prj'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/dominikh/prj/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/dominikh/prj/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.23-722d59436b Thu May 16 02:00:26 2024 +0000'
GODEBUG=''
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/tmp/foo/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1611460511=/tmp/go-build -gno-record-gcc-switches'

What did you do?
Try to go build
-- foo.go --
package pkg

// #include <stdlib.h>
import "C"

func foo() {
	C.malloc(0)
}
-- go.mod --
module example.com

go 1.0

What did you see happen?
# example.com
$WORK/b001/_cgo_gotypes.go:23:6: type alias requires go1.9 or later (-lang was set to go1; check go.mod)

What did you expect to see?
No failure.
I'm mostly filing this for the sake of documentation, as it's probably not worth fixing. I don't think it negatively impacts any real projects. Any 1.0 module can upgrade to 1.9 (or 1.21, for that matter) without risking backwards incompatible changes. Additionally, any code base targeting a Go version older than 1.9 is unlikely to be a Go module in the first place.

Thanks, I don't think this is worth spending time on.  If someone wants to send a fix, we can take a look.


Nix flakes & GHC 9.2.3

This PR includes several small quality of life improvements.
Nix
Flakes
https://nixos.wiki/wiki/Flakes
shell.nix has been replaced with flake.nix and flake.lock. This gives us fixed dependencies, but in a more ergonomic, standard, and safe way than how we've solved this in Web. The lockfile can be updated at any time with nix flake update.
The use of flake-utils in flake.nix is configuring a distinct setup for each possible system architecture. To not do so would require the use of --impure, which is best avoided as this offers us some guarantees about the reproducibility of our flake.
cc @unsplash/web Flakes are still technically considered experimental, so you'll need to enable flakes in your Nix installations like so:

https://nixos.wiki/wiki/Flakes#Installing_flakes
https://github.com/samhh/dotfiles/blob/47f2af3c2247862a22247696c6ce24ae9b8acaf0/modules/core.nix#L7

If you're using direnv, you'll need to replace use nix with use flake and run direnv allow again.
This won't affect your usage of any projects not using flakes, such as Web. This repo can serve as a testbed for our use thereof.
Haskell
GHC 9.2
We've upgraded to GHC 9.2.3. Those of you on M1 Macs should experience faster compilation as per the release notes: https://www.haskell.org/ghc/blog/20211029-ghc-9.2.1-released.html
The new default set of language extensions, GHC2021, has been enabled.
The compiler and other build dependencies are available via Nix, however the language server needs to be installed externally. Ensure you're using at least version <IP_ADDRESS> of haskell-language-server, which should include a binary for 9.2.3.
If you've installed your Haskell stuff via ghcup you should be good to install what's needed provided you're on at least ghcup 0.0.7.
If you're using Nix for everything including the language server then a recent-ish nixpkgs should include support for 9.2.3.
Record dot syntax
The new OverloadedRecordDot extension has been enabled. This allows us to do the following:
data MyType = MyType { myField :: Int }

f :: MyType -> Int
f x = x.myField

Revolutionary.
Updating fields
A new extension for updating record fields has been created, OverloadedRecordUpdate, however this is still considered experimental so I've neglected to enable it.
Generated field selectors
GHC 9.2 includes support for the NoFieldSelectors extension. This prevents the compiler from automatically generating functions for all record fields, which in turn enables the use of field names such as id.
This caused a bit too much breakage to include in this PR.

@samhh I have a go at installing Flakes but I might need your help. Can we huddle sometime?


adding vg api

@mergifyio rebase

This is too complex to include, #588 is a simpler API that lets CSI-drivers handle the grouping of volumes how they like.


fix Lighthouse CI errors

enable disabled rules and fix errors
current rules disabled:
        "color-contrast": "off",
        "errors-in-console": "off",
        "installable-manifest": "off",
        "maskable-icon": "off",
        "offline-start-url": "off",
        "service-worker": "off",
        "splash-screen": "off",
        "themed-omnibox": "off",
        "unused-javascript": "off",
        "uses-responsive-images": "off",
        "works-offline": "off",
        "tap-targets": "off",

Also consider switching to https://github.com/marketplace/actions/lighthouse-ci-action

looks to have been fixed by #34

looks to have been fixed by #34


causes errors in stateful widget Flutter

The library causes errors if imported in a stateful widget.
This might be due to collision of name "State"

Can you provide more details: a stack trace of the error, and a minimal flutter application reproducing the problem?

i forked it and changed the State class from State to GameState(using it in a game) and everything works fine . So i was right

Can you provide more details: a stack trace of the error, and a minimal flutter application reproducing the problem?

Flutter has a reserved name "State"

Can you provide more details: a stack trace of the error, and a minimal flutter application reproducing the problem?

Ahh, why don't you then just alias the import of this library or Flutter, or hide the unwanted State class?
import 'package:statemachine/statemachine.dart' as sm;

See the language tour on how to import libraries: https://dart.dev/guides/language/language-tour#using-libraries


fixed python3.5 format

Fixed a few remaining strings that were not complaint with python3.5

This passes checks and @danclaudino is covered under UT-Battelle MLA. Thanks!


Website is down

Hello. The website is seems to be down and inaccessible from Finland for at least three hours now.

@junelsolis  Thank you for the report. Unfortunately, some of the hardware underlying the website developed a  fault during this weekend. We are working on it in cooperation with our provider University of Dundee IT and Dell. Please see https://forum.image.sc/t/ome-system-down/101981/2

Thank you again @junelsolis , also for the quick noticing that the site is accessible now again.

Thanks for fixing the website, and in a larger sense, OMERO and Bio-Formats :)


Foreign languages not showing properly

I've been trying to use this for my community, but I cannot get Korean to display properly IRC -> Discord. Is there any possible way to solve it?

Can't seem to be able to reproduce this using version 0.6.1 of discord-irc:

Might have been fixed by upgrading to version 6.1.0 of discord.js. Could you try again using the latest version of discord-irc? Thanks!


Can't build dev container on D:

If Dockerfile and devcontainer.json in D: drive on Windows (that is D:\.devcontainer\Dockerfile & D:\.devcontainer\devcontainer.json)
D:\.devcontainer\Dockerfile
ARG VARIANT="bullseye"
FROM mcr.microsoft.com/devcontainers/rust:1-${VARIANT}

D:\.devcontainer\devcontainer.json
{
	"name": "Sample",
	"build": {
		"dockerfile": "Dockerfile"
	}
}

Build container with devcontainer will fail:
# in D:\
devcontainer build .
[18 ms] @devcontainers/cli 0.20.0. Node.js v16.14.2. win32 10.0.22621 x64.
[797 ms] Start: Run: docker build -t dev_container_feature_content_temp -f C:\Users\USER\AppData\Local\Temp\devcontainercli\container-features\0.20.0-1666419425720\Dockerfile.buildContent C:\Users\USER\AppData\Local\Temp\devcontainercli\container-features\0.20.0-1666419425720
[975 ms] Sending build context to Docker daemon    297kB
[1007 ms] Step 1/2 : FROM scratch
 --->
Step 2/2 : COPY . /tmp/build-features/
[1007 ms]
[1013 ms]  ---> Using cache
[1014 ms]  ---> 65d7fa21086a
[1014 ms] Successfully built 65d7fa21086a
[1022 ms] Successfully tagged dev_container_feature_content_temp:latest
[1022 ms] SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and reset permissions for sensitive files and directories.
[1027 ms] Start: Run: docker build -f C:\Users\USER\AppData\Local\Temp\devcontainercli\container-features\0.20.0-1666419425720\Dockerfile-with-features -t vsc-vscode-remote-try-rust-2b487e416576759e13404c2a21fd7848 --target dev_containers_target_stage --build-arg VARIANT=bullseye --build-arg _DEV_CONTAINERS_BASE_IMAGE=dev_container_auto_added_stage_label --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp D:\.devcontainer
[1122 ms] unable to prepare context: unable to get relative Dockerfile path: Rel: can't make C:\Users\USER\AppData\Local\Temp\devcontainercli\container-features\0.20.0-1666419425720\Dockerfile-with-features relative to E:\.devcontainer
[1125 ms] Exit code 1

Looks like filepath.Rel (https://github.com/docker/cli/blob/v20.10.20/cli/command/image/build/context.go#L358) in docker-cli will fail due to devcontainer create Dockerfile-with-features in system drive regardless original workspace.
The devcontainer should create temp files in same drive as workspace instead of just creating in Windows temp.

Is there a known workaround for that? Also we observe it on C: drive 😢

Is there a way to downgrade or workaround this issue? I am unable to rebuild my image and can not get into my dev environment, this is not limited to just the D: drive. My devcontainer/docker service is on a remote server using docker context to communicate remotely.
I am getting
unable to prepare context: unable to get relative Dockerfile path: Rel: can't make C:\Users\<redacted>\AppData\Local\Temp\devcontainercli\container-features\0.23.2-1667553015190\Dockerfile-with-features relative to \\?\c:\Users\<redacted>\Desktop\php\.devcontainer

I am also facing the same , in windows I have set virtual drive as V: => c:\myfiles\
docker build -f C:\Users<user>\AppData\Local\Temp\devcontainercli\container-features\0.25.2-1673283658137\Dockerfile-with-features -t vsc-project-f9af19950fe987d4e0a42ac4a1093111 --target dev_containers_target_stage --build-arg _DEV_CONTAINERS_BASE_IMAGE=dev_container_auto_added_stage_label --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp v:\esag_github\project.devcontainer
unable to prepare context: unable to get relative Dockerfile path: Rel: can't make C:\Users<user>\AppData\Local\Temp\devcontainercli\container-features\0.25.2-1673283658137\Dockerfile-with-features relative to V:\esag_github\project.devcontainer

Got this issue today.


Adding identity to VM and VMSS properties

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[ ] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[x] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

@nkuchta,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

This addresses #870.
@fearthecowboy any update?

I've been trying to track this down. I've gone thru a bunch of things, but I think I now know who to hit over the head. Stay tuned.

Fixed CI!

 https://github.com/Azure/azure-sdk-for-ruby/pull/716

 https://github.com/Azure/azure-sdk-for-python/pull/1029

 https://github.com/Azure/azure-sdk-for-node/pull/2094


1.16.5 crash on death

Whenever I get killed by any mob, the game crashes. Here are some crash logs from that:
https://crashy.net/AgGPfPtgkm6BHpnX5RVV
https://crashy.net/nTPj0qZw84g8zKCqzEmy
https://crashy.net/XkqGmIzKc3fjdX0rdAkh
https://crashy.net/UQwQ4zDiBqV5FLO0FVBQ
Then, if I try to re-join the world it crashes again. Here is the crash log from that:
https://crashy.net/Gt1XCw0J9MWQjjhcfLX7
If, instead of trying to re-join, I decide to create a new world... my model looks like this:

Something corrupts the pose stack. Any mod can basically cause that. Since the 1.16 release has been out for a long time without anyone having issues like that, it's probably some other mod. Try removing mods till this error goes away.

Stale.


Fix for issue #277

Pull Request (PR) description
Fixes an issue in SCDLPComplianceRule where when multiple SensitiveInformation object where found, nothing was being returned.
This Pull Request (PR) fixes the following issues

Fixes 277

This change is

@desmay would you have a few minutes to help review this PR?

Codecov Report

Merging #327 into Dev will decrease coverage by 0.04%.
The diff coverage is 90.16%.

@@            Coverage Diff             @@
##              Dev     #327      +/-   ##
==========================================
- Coverage   90.12%   90.07%   -0.05%
==========================================
  Files          79       79
  Lines        7946     7969      +23
  Branches       11       11
==========================================
+ Hits         7161     7178      +17
- Misses        774      780       +6
  Partials       11       11

Impacted Files
Coverage Δ

..._SCDLPComplianceRule/MSFT_SCDLPComplianceRule.psm1
95.15% <90.16%> (-3.45%)
:arrow_down:

Continue to review full report at Codecov.

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


grangerise, carbamic (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


Help container is not always drawing top border

The help scrollpane sometimes does not have the top border drawn.
Looks a bit poor.
If you resize the screen it draws so it's probably a painting issue

Can you provide a screen shot of it happening?

Just tried about twenty different pages in the help going clickety click and could not reproduce it.
I'll close it (nothing to do) unless I come across it again and get a screen shot


Generate report in XML?

Hi,
Does your plugin allow the user at all to specify the output format of the test once the process is finished? In order to work with the likes of OWASP DefectDojo (which says it will only work with the XML formatted output from ZAP).
Reading your documentation, and looking at the source code, it wasn't clear that through the groovy coding in the Jenkinsfile that a user could declare this ? (if not, I might look to implement this and open up a PR)
Thanks

Hey
This currently can't be done. It wouldn't be difficult to add a download as XML button to the report. I can take a look at adding that soonish or feel free to make a PR (but make sure to use the new repo:  https://github.com/jenkinsci/zap-pipeline-plugin )
Thanks


InstructBLIP generation parameters

Hello, I want to ask what generation parameters and what language model or pretrained weight you guys use in producing results in the paper?  In our practice, we found that InstructBLIP results are much higher than results in the paper.
For example, in popular and adversarial, our accuracy results are 84% and 81%, however in paper results are 71% and 62%

sorry, my bad, the results I should refer to is this:

but the gap is still large

Hello, @JulioZhao97
We used the default parameter settings of InstructBLIP and we didn't use any system prompt.

Did the results in Table4 (the above results) evaluated using json files in output/coco?

Thanks for your time, it seems that whether or not the first letter of prompt is capitalized has a big impact on performance


Hover / play interactions

Mary can talk to Walker or others to get more details on this.

and analytics for these events?

analytics are happening elsewhere (https://github.com/USGS-VIZLAB/gages-through-ages/issues/12), but presumably will be aligned w this


[Snyk] Upgrade @loopback/core from 5.1.3 to 5.1.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @loopback/core from 5.1.3 to 5.1.4.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2023-12-12.

Release notes

Package name: @loopback/core

5.1.4 - 2023-12-12<EMAIL_ADDRESS>

5.1.3 - 2023-09-12

    from @loopback/core GitHub release notes

Commit messages

Package name: @loopback/core

5326aa3 chore: publish release
565fc1f fix: fix import update-notifier
73a58da chore: update dependency loopback-datasource-juggler to ^5.0.4
8a26eac chore: update dependency loopback-connector-mysql to ^7.0.5
8d65cbc chore: update dependency cacache to ^18.0.1
051ef7f chore: update dependency @ types/node to ^16.18.68
6f7054a chore: update dependency @ types/tunnel to v0.0.6
c50527c chore: update api-extractor packages
b2d2196 chore: update dependency pacote to ^17.0.5
dd34097 chore: update dependency testcontainers to ^10.3.2
a09cbd4 chore: update dependency strong-error-handler to ^5.0.5
d64ebc5 chore: update github/codeql-action action to v2.22.9
dcda7ba chore: update dependency lint-staged to ^15.2.0
d792eaa chore: update dependency swagger-ui-dist to v5.10.3
ba4f954 chore: update dependency autocannon to ^7.14.0
660b623 chore: update dependency @ types/type-is to ^1.6.6
6d47787 chore: update dependency @ types/yeoman-environment to ^2.10.11
e8408dc chore: update dependency puppeteer to ^21.6.0
1a528ba chore: update dependency casbin to ^5.28.0
05b0618 chore: update commitlint monorepo to ^18.4.3
87839f9 chore: update github/codeql-action action to v2.22.8
593e82d chore: update dependency @ types/uuid to ^9.0.7
88cddae chore: update dependency @ types/yeoman-generator to ^5.2.14
6d8e2bc chore: update dependency sequelize to ^6.35.1

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

already done


Load testset in Playground

Description
We would like to load the test set data with one button click in the playground. This would allow users to quickly get started with the playground.
Describe the solution you'd like
Add a button to the right of 2. Preview and test (in the playground) that allows to load a test set. Clicking on the button would show a modal where the user can select the test set between multiple choices. After confirming, the data set will be appended to the already existing rows.
Additional context
Add any other context or screenshots about the feature request here.

Assing me this issue @mmabrouk . I will try to finish it until the end of the work week.

@mmabrouk Here you go. The loading of test sets data is done.
I don't really like that I had to fetch the data for specific test set then add it.
But the api works like this and I don't get test set data when I fetch the list of them.

@suadsuljovic The issue is that test sets could be very large. It does not make sense to fetch all of the data at once, no? Or did I misunderstand you?

It first fetches the all test set names as a list.
Then when user selects one it fetches that test set's data.
It doesn't do fetching for all test set's data. Only the selected one.

As mentioned, I find it better this way, because test sets can include lots of data, so it does not make sense to fetch all the data at once (for all test sets).
Maybe a clarification here: right now our examples have small test sets, but in the future we would want the test sets to come from production data: after the developer deploys the llm app, we monitor its usage and use the data gather from the user interaction as a test set. This will make the test sets quite large.


Support a local engine flag in the tool integration tests

I recently had to debug a regression in the flutter_tools integration tests using a local build of the engine binaries.
I was able to do this by patching _setupProcess in https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/integration.shard/test_driver.dart to add a --local-engine flag to the command line that it generated.
It would be useful to have a flag in the test runner that can select a local engine.
@jonahwilliams

This will be easier to do once https://github.com/flutter/flutter/pull/64980 lands


Cherry toast disposed with an Active Ticker

══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown while finalizing the widget tree:
_CherryToastState#57988(tickers: tracking 1 ticker) was disposed with an active Ticker.
_CherryToastState created a Ticker via its TickerProviderStateMixin, but at the time dispose() was
called on the mixin, that Ticker was still active. All Tickers must be disposed before calling
super.dispose().
sometimes it pops even I showed the Cherry toast once

@pagebook1 can you provide more info about this bug, package version, flutter version

I just published a new version fixing this bug
https://pub.dev/packages/cherry_toast


+1 vs +11 phone number

+16467057784
+116467057784
are both valid numbers.
too easy to enter the wrong number

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

Fixed and deployed a while ago:


Support Codelyzer 5

I'm submitting a ...  (check one with "x")
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><5.0.0".

Expected/desired behavior
No warning.
What is the motivation / use case for changing the behavior?
Warningless :)
Other
What was the reason to remove support for 5.0.0?

@TheAifam5 that's all about public API change in codelyzer.
Please see https://github.com/mgechev/codelyzer/blob/master/CHANGELOG.md

@fulls1z3 could you please shed more light on this?
This is connected only with changing names of rules or there is something more fundamental.
I am just curious - if only naming then of course community can help with that but if there is something more fundamental then indeed it can be more challenging

@AdaskoTheBeAsT @TheAifam5 see my PR #37

:tada: This issue has been resolved in version 1.14.5 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

Something went wrong :)
[error] FatalError: Failed to load src/tslint.json: Unexpected string in JSON at position 3852 in node_modules/angular-tslint-rules/tslint.json
    at new FatalError (node_modules/tslint/lib/error.js:27:28)
    at Object.findConfiguration (node_modules/tslint/lib/configuration.js:57:15)
    at _lint (node_modules/@angular-devkit/build-angular/src/tslint/index.js:137:40)
    at _run (node_modules/@angular-devkit/build-angular/src/tslint/index.js:57:35)
    at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:52:5)
    at Function.Module.runMain (internal/modules/cjs/loader.js:880:11)
    at internal/main/run_main_module.js:21:11

@TheAifam5 known issue, bumped version after version to match<EMAIL_ADDRESS>use v1.18.0 and it works


Offline marker in lists not reliable

On yesterdays caching trip with NB0302 I had some problems with the offline-logging.
I stored some offline logs (just typed a few words and pressed back). The toast message "Log saved" was shown.
After that the following things appeared somehow randomly among the caches:

The orange marker was not shown for all caches where I saved a log but for some it worked.
If I deleted the offline log the orange-marker stays in the list for all caches where I have tried that
After accessing the offline-log again (back in my warm car) and sending the log it gets marked green+orange in the list

I assume its related to the latest changes, but I wanted to create a separate issue to test if it is fixed after the problems are solved.

I assume this is related to the issues @blafoo is currently addressing with #1084

Duplicate of #1059 and should be fixed with #1084. But there are a lot of open issues, so this can take a while.


ENG 2494 Fix a bug where metric graph dates are cutted off

Describe your changes and why you are making these changes
This PR improves the magin of metric plots so that x-axes will not be cut off.
Related issue number (if any)
ENG 2494
Loom demo (if any)

Checklist before requesting a review

[ ] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[ ] I have performed a self-review of my code.
[ ] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[ ] If this is a new feature, I have added unit tests and integration tests.
[ ] I have run the integration tests locally and they are passing.
[ ] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[ ] All features on the UI continue to work correctly.
[ ] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

@agiron123 actually I know it as it's mentioned in the bug report :)


Adjust the docker-compose command to docker compose in the README file

The command docker-compose command is wrong, the correct one is docker compose. Without the -

https://docs.docker.com/reference/cli/docker/compose/

Thank you for pointing out the needed docs update. Just to clarify docker-compose is not wrong, it's now just a wrapper script/command that calls docker compose for backward compatibility.
When some of these docs were written, the compose subcommand didn't exist and docker-compose was a completely separate tool (written in Python).
PRs are welcome BTW.


can not find a proper IAM service linked role for this cloudformtion

Hello team,
would you please also share the IAM policy of the service role when you launch this cloudformation template?
We can not use fulladmin for it ,must keep the least priviledge ,I tried several times, but still fail,
"because no identity-based policy allows the iam:PassRole action(Service:Lambda, status code:403)"
Thanks.

If it is a PassRole exception, try to allow PassRole in your deployment role.  For example, add the following section to your deployment role.

{
        "Sid": "AllowLimitedPassRole",
        "Effect": "Allow",
        "Action": "iam:PassRole",
        "Resource": "arn:aws:iam::123456789012:role/replace_with_your_deployment_role"
}


Start-SFApplicationUpgrade requires both Id and Name and ApplicationParameters are required.

Describe the bug
Start-SFApplicationUpgrade requires both Id and Name and Parameters are required.
Expected behavior
It should only accept Application Id or Name and Parameters should be an optional argument.
Additional context
In addition to above, cmdlet should also handle parameters passed as powershell HashTable.

Module with the fix is published (version =1.0.3-preview2)


use a base image for docker

Fixes the fact that there are too many images with the same stuff installed


beginConnect gone?

Hi,
first: i really like that you are working on the project again.
I asked how to cancel a bt-connect after one second about 7-8 years ago and now since i improved my coding skills i'm trying to improve my c# app which i'm still using.
I found some interesting code (MarcFletcher/NetworkComms.Net) examples to timeout a connect but the current version of your btclient doesn't have a beginConnect method anymore....
not an issue but maybe you can give me a hint:
i need to transfer data to 20 devices (moving people) fast. i try to connect to 7 at a time and if all 7 are in range everything works perfectly. if one device is out of range the connect to this device does block the bluetooth radio. timeout is 5 seconds.
i want to decrease to 1 second, since if the device is in range it will connect in less than 700ms.
(the device are not discoverable by the way and do not have any bt-le, only bt with serial port)

In order to support Unity and the Mono runtime the socket functions were wrapped directly from the Win32 API so ConnectAsync and Begin/EndConnect are not currently implemented.
I think a possible workaround would be to create a separate thread with a reference to the Client socket and call Close() on this socket after the desired timeout if it didn't succeed.

Hi,
first: i really like that you are working on the project again.
I asked how to cancel a bt-connect after one second about 7-8 years ago and now since i improved my coding skills i'm trying to improve my c# app which i'm still using.
I found some interesting code (MarcFletcher/NetworkComms.Net) examples to timeout a connect but the current version of your btclient doesn't have a beginConnect method anymore....
not an issue but maybe you can give me a hint:
i need to transfer data to 20 devices (moving people) fast. i try to connect to 7 at a time and if all 7 are in range everything works perfectly. if one device is out of range the connect to this device does block the bluetooth radio. timeout is 5 seconds.
i want to decrease to 1 second, since if the device is in range it will connect in less than 700ms.
(the device are not discoverable by the way and do not have any bt-le, only bt with serial port)

That's a good suggestion. I would definitely like to add back Async methods however currently the Win32 implementation uses native Winsock functions rather than the .NET implementation of Socket because this is the only working option when running on Mono (Unity etc). Also there isn't an equivalent on Android so would need to find a way to implement in a way which can work across platforms.

4.0.12 adds these back to the Win32 specific version of the assembly. They won't appear in a cross platform context.


rke2 cluster in "hang" state following deletion by standard user

Setup

Rancher version: 2.6.4-rc8
Browser type & version: Chrome - Version 99.0.4844.51 (Official Build) (arm64)

Describe the bug
When a standard user deletes an rke2 custom cluster (as cluster-owner), UI "hangs" on Waiting for machine [machine_id] to delete.
To Reproduce

Fresh install of rancher v2.6.4-rc8
As admin, create a standard user
As standard user, create a cluster (rke2 custom)
As standard user, delete the cluster
Reproduced

Result
cluster is deleted and cluster role binding is removed; UI stuck in "hang" state
Expected Result
cluster is deleted, cluster is removed from UI
Screenshots

Additional context

Detailed Description

Context

We'd need to confirm our delete logic here. The possible scenario UI should watch out for is:

UI gets the delete request
UI sends the delete request
UI then assumes that it will be deleted and removes the item from the list, then waits on backend for confirmation

If that last point isn't the case, meaning that UI does wait for confirmation of deletion, then this is likely backend related.

@gaktive I have been investigating the issue and I am quite certain that the issue is backend related.
Looking into the Websocket messages for the deletion of a RKE1 cluster as admin, here are the most relevant messages received:
provisioning.cattle.io

management.cattle.io

For a standard user:
management.cattle.io

What we are missing on the FE side is the provisioning.cattle.io message about removal of the cluster while as a standard user, which is responsible for the removal on the FE (which we never receive), hence why the FE is not "live updated" (item removed from the list) but does in fact disappear once we refresh it.
FYI @richard-cox @nwmac

Thanks @aalves08. If that's the case, please file a ticket in rancher/rancher with that explanation and link back to here, or then transfer this ticket over to that repo and let me know so I can ensure someone on Team 2 (or elsewhere) can jump on it.


Unable to import repository from GOGS

I too am unable to import a repo, internally hosted on an old GOGS implementation ( Gogs Version: <IP_ADDRESS>1)
The URL is 'http://aurowgit01.rbc.int:3000/mwoodward/Ansible' (also tried appending .git but does not work either)
I get 'Invalid GitHub or GitLab URL'
I have 'requires auth' ticked and username/password entered.

Hi @emjayit thank you for your ticket!   We currently only support importing repositories from GitHub or GitLab.  We will update the docs to make this clear, and work on adding support for import from more providers.

Hey @emjayit, we've release a new version v3.0.0-beta.4 which added support to import from gogs.
You can pull the latest image from DockerHub with docker pull harness/gitness:latest or docker pull harness/gitness:v3.0.0-beta.4


Drivers: I2S: STM32: Mishandling of Master Clock output (MCK)

Proposal to rectify the raised issue https://github.com/zephyrproject-rtos/zephyr/issues/54841 the reference manual for families supporting I2S have a section under the I2S peripheral (shared with SPI) called Clock generator that expands on the clock details.
The master clock output pin is enabled by setting the specific alternate function, in some cases multiple pins present such function for the same peripheral instance. Therefore, the detection of the pin can be made by leveraging device tree and its API. Since there are multiple options for different driver instances, an exhaustive search across all of the possible ports and pins needs carrying out. On top it, the device tree API operates at pre-compile time. These two reasons are the basis for having a set of macros that will generate the DT checks for the desired function on the specified port and pin ranges. This makes to determine during the driver initialisation whether the master clock output has been requested to be set.
The bit rate, I2S CK, is adjusted around the different constraints imposed by having MCK and channel widths.
A couple of sanity checks on existing operations have also been added, essentially to ensure that the rates are achievable and compliant with the hardware constraints.
The functionality introduced depends on https://github.com/zephyrproject-rtos/hal_stm32/pull/162 & https://github.com/zephyrproject-rtos/hal_stm32/pull/163

Not sure why twister is complaining as result of the last commit with:
INFO    - The following issues were found (showing the top 10 items):
INFO    - 1) tests/lib/mpsc_pbuf/libraries.mpsc_pbuf_concurrent on qemu_x86_64 failed (unexpected eof)

I can run it locally OK.
$ west twister -p qemu_x86_64 -s tests/lib/mpsc_pbuf/libraries.mpsc_pbuf_concurrent
Renaming output directory to /media/srv/extra/zephyrproject/zephyr/twister-out.1
INFO    - Using Ninja..
INFO    - Zephyr version: v3.3.0-rc3-84-g31463fa0c013
INFO    - Using 'zephyr' toolchain.
INFO    - Building initial testsuite list...
INFO    - Writing JSON report /media/srv/extra/zephyrproject/zephyr/twister-out/testplan.json
INFO    - JOBS: 4
INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
INFO    - Total complete:    1/   1  100%  skipped:    0, failed:    0
INFO    - 1 test scenarios (1 test instances) selected, 0 configurations skipped (0 by static filter, 0 at runtime).
INFO    - 1 of 1 test configurations passed (100.00%), 0 failed, 0 skipped with 0 warnings in 67.65 seconds
INFO    - In total 24 test cases were executed, 0 skipped on 1 out of total 540 platforms (0.19%)
INFO    - 1 test configurations executed on platforms, 0 test configurations were only built.
INFO    - Saving reports...
INFO    - Writing JSON report /media/srv/extra/zephyrproject/zephyr/twister-out/twister.json
INFO    - Writing xunit report /media/srv/extra/zephyrproject/zephyr/twister-out/twister.xml...
INFO    - Writing xunit report /media/srv/extra/zephyrproject/zephyr/twister-out/twister_report.xml...
INFO    - Run completed


[Bug] Can't degit into an empty directory when omiting folder name

I'm trying to clone a repo into the current directory I'm on, and I keep getting an error, event when the directory is empty.
This is the error I'm getting:
! destination directory is not empty, aborting. Use --force to override

@Rich-Harris I'm not mistaken, it's a bug, right?

same too. weird.

same here

what version are you on? v2.8.0 worked here

same too. weird.

I receive the notification from Github and just test it with degit sveltejs/template my-app, nothing is wrong. I forgot to check the degit version. (It's late, because I reinstall degit just now.)

I am having the same issue trying to use the clone('./') It does not like this


Add tree-sitter-vim

Not sure if its ok to just randomly PR a new grammar but here I am :shrug:

You forgot to add the submodule reference. I added it at the latest commit and merged your PR. Thanks!


Update Node to 16

Background
Per this thread, I noticed the deprecation notice for Node 12 and this PR is for updating this GitHub Action to use Node 16. I don't believe this fixes the original issue in the thread.
Changes

Remove trailing space in line 39
Update Node to 16

Testing
Do I need to bump action version?

[TODO] Test locally with Act before merging


Set grader to nil explicitly

Pull Request Test Coverage Report for Build 3220

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

Totals

Change from base Build 3219:
0.0%

Covered Lines:
1482

Relevant Lines:
1523

💛  - Coveralls