Bug: Project shows "Cluster not ready"

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Unknown, happened after an upgrade.  Unable to reproduce
Result:

Other details that may be helpful:
The issue is related to DefaultNetworkPolicyCreated in API being set to unknown.
"lastUpdateTime": "2020-05-14T06:40:41Z",
"status": "Unknown",
"type": "DefaultNetworkPolicyCreated"

Previously it was possible to delete projectnetworkpolicies,cattle,io for the project in question and then force a sync by editing the project's description which would fix the unknown status.  In two other instances where this was seen however this didn't fix it.  Instead it came back as unknown.
kubectl delete projectnetworkpolicies.management.cattle.io -n p-69fs2

At the moment the only workaround is to delete the Unknown status directly from the project which will fix the UI although the underlying bug still exists.
kubectl get projects.management.cattle.io -A
kubectl get projects.management.cattle.io -n local p-ldn9h -o yaml > backup.yaml
kubectl edit projects.management.cattle.io -n local p-ldn9h

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.3
Installation option (single install/HA): HA

gz#11059
gz#11056
gz#11206
gz#10305
gz#12204
gz#13165
gz#13547
gz#14814
gz#14959
gz#15932

Additional information:

The happened after an upgrade from Rancher v2.3.5 to v2.4.3 and upgrade from Kubernetes v1.15.9 to v1.17.5,
The issue was observed in the System project of a downstream cluster

I've got the same problem with Rancher version v2.4.8. Would be awesome to see this actually fixed in v2.4.9.

I have the same issue upgrading from v2.4.5 to v2.4.8

We've experienced the same issue in a Rancher managed cluster after upgrading to 2.4.8. To troubleshoot, I opened our Rancher console, selected the cluster with the issue, then clicked Launch kubectl
When we try the workaround, the first kubectl command gives the following error
kubectl get projects.management.cattle.io -A
error: the server doesn't have a resource type "projects"
I have confirmed it is not in the list by running this command:
kubectl get crd
networksets.crd.projectcalico.org             2020-06-04T19:11:58Z
prometheuses.monitoring.coreos.com            2020-06-04T19:25:53Z
This tells me neither of the next two commands would work either. Do I have the option to create the entry? If so, would it look like this?
kubectl create crd -n local c-vfczk
And which cluster would I run it in? The Rancher cluster or the managed cluster with the issue?

same for me :

If someone has a workaround, I am interested.
Currently I am holding upgrade on other clusters.

@hcouplet , We are holding other cluster updates as well. Thank you for the screen shots. They mirror what we are seeing.
@patrick0057 , any thoughts?

Hi @hcouplet and @chrisgelhaus
The commands from @patrick0057 need to be applied on the local Rancher cluster itself (not on the Rancher managed ones). I was able to fix it using the commands down here:
kubectl get projects.management.cattle.io -A
kubectl get projects.management.cattle.io -n c-rsabc p-8r123 -o yaml > ~/Temp/backup.yaml
# Remove the whole entry with status "unavailable":
kubectl edit projects.management.cattle.io -n c-rsabc p-8r123

For me the regarding project object was inside another namespace (p-8r123) and not inside local as @patrick0057 wrote.
Hope this helps! If not please comment again. I hope Rancher fixes this issue soon (we opened a ticket via their support).
Regards,
Philip

This worked for me. Thanks.
As I am running rancher as docker, I had to run commands after :
docker exec -it rancher2 bash

Then, used the /tmp/ directory :
kubectl get projects.management.cattle.io -n c-vg59f p-ddhwb -o yaml > /tmp/backup.yaml
As vi was not in the docker image, I ran
apt-get update apt install vim-tiny

Hitting this too:
  - lastUpdateTime: "2020-09-01T18:49:55Z"
    status: Unknown
    type: DefaultNetworkPolicyCreated

Hi, confirming, that deleting the section from the project description restored status to Active. For us it was also about DefaultNetworkPolicyCreated:
  - lastUpdateTime: "2020-11-02T04:02:03Z"     status: Unknown     type: DefaultNetworkPolicyCreated

Confirming here too, this happened on a new installation after a Rancher version was downgraded from 2.4.15 to 2.4.5.
  status:
    conditions:
    - lastUpdateTime: "2021-05-06T19:28:10Z"
      status: "True"
      type: BackingNamespaceCreated
    - lastUpdateTime: "2021-05-06T19:28:10Z"
      status: "True"
      type: CreatorMadeOwner
    - lastUpdateTime: "2021-05-06T19:28:10Z"
      status: "True"
      type: InitialRolesPopulated
    - lastUpdateTime: "2021-05-06T19:33:36Z"
      status: "True"
      type: MetricExpressionDeployed
    - status: Unknown
      type: DefaultNetworkPolicyCreated
    podSecurityPolicyTemplateId: ""

The steps mentioned by @patrick0057 work to fix it and get the "System" project available in the UI again. Thanks for sharing this.

@sowmyav27 - According to the recent chatter on this ticket, it looks like this might have been fixed as part of something else we did post 2.4x, can you guys do a quick verification on this?

@Tejeev - If possible, could you provide reproduction steps for the QA team? Sowmya worked on this and wasn't able to reproduce successful, so we are thinking recent changes might have closed this but we want to confirm.

@Jono-SUSE-Rancher sorry I have none.  One of our customers had this back in 2.4.3 but they since upgraded and have not seen any issues for a very long time

@Jono-SUSE-Rancher Although is not a natural way to reproduce the issue you can edit the project medatada and modify the status to "error", "unkown", etc and it will reach the inconsistent state where "Cluster is not ready" but you can still access the project through the direct url.
On my case where the bug appeared when upgrading the monitoring app #33104 I could reproduce it in other projects by adding these lines:
  - lastUpdateTime: "2021-06-03T06:33:11Z"
    reason: Error
    status: "False"
    type: MonitoringEnabled

Although to reproduce it without manually editing the project template would require to manage having a failed monitoring app installation which would be tricky.
Maybe there are easier ways to get a failed status on project metadata.

QA is unable to reproduce this as well as us not seeing it on our current master branch. It looks like this will be fixed in v2.6. @Tejeev can you validate that this would be acceptable?


Support min file size

It's needed to compatibility with Yii2 FileValidator.
I develop a module for this framework to connect FilePond.
See also: tooSmall parameter

What is the use case for this in real life?

Use case in real life. For example, I want to upload video file. And I know, that minimum size of video in FullHD is 1 MB. So, if user will try to upload file, which is less than 1 MB, I can tell him about error before uploading this file on server.

@vommuan okay, and why is the minFileSize property not covering this use case?

@vommuan I see it's not documented :D My mistake. :)


Improve text generator

Current coverage is 80.39% (diff: 100%)

Merging #11 into master will increase coverage by 0.14%

@@             master        #11   diff @@
==========================================
  Files            30         30
  Lines           957        964     +7
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            768        775     +7
  Misses          189        189
  Partials          0          0

Powered by Codecov. Last update 762cec6...6024704


webui: setup application

Let's standup a basic app for hosting forms and tooling using this library.

https://github.com/moov-io/fincen/pull/21


Consider making policy-cidr-match-mode=nodes the default

As of v1.15, we support matching nodes via CIDR / IPBlock selectors. By default, nodes are only selectable via the host and remote-node entities, which requires the use of a CiliumNetworkPolicy.
However, this option is not enabled by default, which continues to surprise users. We did not make this option default out of concerns for scaling, since CIDR labels consumed quite a bit of memory -- at least 1 KiB per node, and much more if dual-stack. In a large cluster, this could be wasteful.
However, now that #30897 has merged, CIDR labels are quite cheap. At this point, the additional cost of an identity should be small.
Since the scaling objection has now been resolved, we have an opportunity to remove an option and fix an annoying policy wart that users consistently hit.

Is the intent for this setting to change for all new installations, or to default enable during upgrade? The reason I ask is that the former sounds low-risk, but the latter will impact the enforcement of user-provided network policies which is higher risk.
If we plan to force existing users to adopt this setting, then I would expect thorough documentation in the upgrade guide to clearly explain the previous and new behaviour, how to opt-out, and a proposed method for migration to ensure that users have the tools to continue to enforce the policies they expect.
Here's an example template we could use for such documentation:
https://docs.cilium.io/en/v1.15/operations/upgrade/#migrating-from-kvstore-backed-identities-to-kubernetes-crd-backed-identities
The structure there is roughly:

Concise summary
Impacted versions / configurations
Mitigation
Migration

Hey @squeed ,
This looks like a good first issue to me (please let me know if its not)  and I see you have this planned for 1.16 . I am happy to work on this or contribute to ongoing progress.

@Anurag252 please give it a shot.

@Anurag252 please give it a shot.
Thanks @aanm , Let me take a look.

I looked at the codebase and also the issue described here. I believe, I can make changes at

helm-values.rst to correct the default values
defaults.go to define nodes as default
values.yaml.tmpl to define default value.

I also understand from  comments above that we want to avoid upgrades automatically picking up this change
We also prefer to not add conditional upgradeComptability check like here and prefer that users pass --set policy-cidr-match-mode="" while upgrading if they do not want to enable this option.
Apart from adding this detail in release-notes, are there any more steps that we should be taking informing users that they are about to enable this option unless they pass --set policy-cidr-match-mode="". A printf without fail in validate.yaml closely resembling this comes to my mind .
Please let me know your thoughts.

The lowest risk to users is to implement with upgradeCompatibility. While that functionality is not perfect by any means, it is the best way we have to express defaults only for new installs currently.
Beyond that, this comment above outlines the sort of documentation I would expect as a user if I wanted to try to figure out how to handle this flag during upgrade: https://github.com/cilium/cilium/issues/31961#issuecomment-2093333938 .

The lowest risk to users is to implement with upgradeCompatibility. While that functionality is not perfect by any means, it is the best way we have to express defaults only for new installs currently.
Beyond that, this comment above outlines the sort of documentation I would expect as a user if I wanted to try to figure out how to handle this flag during upgrade: #31961 (comment) .

Okay, makes sense to me.

Posted a PR for this https://github.com/cilium/cilium/pull/34080

I've had a bit of a think about this, and I think we need to hold off until we have the ability to do partial wildcarding of policy selectors. Specifically, I'm concerned that this will cause larger clusters to exceed their policymap size.
If someone allows "proto ANY, port 53, 443, all nodes" via network policy, right now that is 6 PolicyMap entries (for TCP, UDP, SCTP). However, if we enable this flag by default, that is 6 * N entries. I could see this hitting bpf map size limits easily.
I think we should do this, but I want to add partial wildcarding, for which I have the beginnings of a design but probably won't land until v1.18.


Added 68 entries

Greetings.
Having learned of your list from https://github.com/collinbarrett/FilterLists/issues/647, I was reminded of a similar list made by Aegis Team. As their list was not made with adblockers in mind (although it is listed on FilterLists.com, as it's a decently good list for domains tools and uBO), and has largely different URLs to those of your list, I figured that I could suggest adding most of its entries to your list to give it an extra little bit of fodder.

From most of them I've tested, There quite a lot of website that went broken, non-used or used for others types of uses (Ads redirectors for example), Regardless, Those seem to be a great addition from the list. Thanks for your pull request!


Modifying Users

There's no way to modify the usm table. Why not?

Please go and challenge the original authors of the standard. That goes beyond the scope of any SNMP library.

You have a method to add users, but I figured out another way. My problem was doing a discovery via IP address, like SnmpSharpNet does.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Lex Li<EMAIL_ADDRESS>Sent: Wednesday, June 7, 2017 10:01:30 PM
To: lextm/sharpsnmplib
Cc: Willis, Brandon; Author
Subject: Re: [lextm/sharpsnmplib] Modifying Users (#35)
Please go and challenge the original authors of the standard. That goes beyond the scope of any SNMP library.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/lextm/sharpsnmplib/issues/35#issuecomment-306984899, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANiJdUw7ZXHhzmQjVZ1qKCn3YyJgdVwYks5sB2QKgaJpZM4NywDs.

Please start from the documentation site,
https://docs.sharpsnmp.com/en/latest/


Split Linter and normal Tests

Use a CI for Linter Tests and use a CI Workflow for unit tests.
Advantages:

It is easier to locate problems
better structure

Is this finished? If so please close


Fixes a bug with tag matching

Description
The tag matching logic was a little off and needed to be tweaked by adding a sub-query to the SQL that finds existing games. I also added a reference number footer to game embeds just for reference.
Checklist

[x] Add tests for these changes
[ ] Test coverage is not decreased
[ ] Entire test suite passes

Codecov Report

Merging #86 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #86   +/-   ##
=======================================
  Coverage   96.93%   96.93%
=======================================
  Files          21       21
  Lines        1207     1208    +1
  Branches      187      186    -1
=======================================
+ Hits         1170     1171    +1
  Misses         21       21
  Partials       16       16

Impacted Files
Coverage Δ

src/spellbot/data.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Using multiple plugins

I'm trying to use the Nest and Dyson plugins and I can't figure out how to combine the config files.
Here is my current config:
`{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154",
"manufacturer": "@nfarina",
"model": "Homebridge",
"serialNumber": "0.4.20"
},
    "platforms": [{
            "platform": "Nest",

            "token": "",

            "clientId": "",
            "clientSecret": "",
            "code": "DALHCTNG",

            "username": "username",
            "password": "password"
    }]

}
`
And I need to add
"platforms": [     // This is the config for this plugin       {       "platform": "DysonPlatform",       "name": "DysonPlatform",       "accessories": [         {           "ip": "ip of your device",           "displayName": "Name to be shown on Home App",           "serialNumber": "DYSON-XXX-XX-XXXXXXXX-XXX",           "password": "password of your device"         },         {           "ip": "ip of your second device",           "displayName": "Name to be shown on Home App",           "serialNumber": "DYSON-XXX-XX-XXXXXXXX-XXX",           "password": "password of your second device"         }         // If you have more than one device(s), just add the same config below       ]     }     // End of the config   ],

{

"bridge": {

"name": "Homebridge",

"username": "CC:22:3D:E3:CE:30",

"port": 51826
,
"pin": "031-45-154",

"manufacturer": "@nfarina",

"model": "Homebridge",

"serialNumber": "0.4.20"

There you can see what is missing


Error without statusText via HTTP/2 protocol

Hi
I use useFetch hook via HTTP/2 protocol. I need to handle Error via statusCode or statusText. According to the spec:

HTTP/2 does not define a way to carry the version or reason phrase that is included in an

It means i don't have methods for getting statusCode or statusText.
It is good idea to add statusCode to the error. What do you think?
Thanks

Thanks for reporting. Actually, I got exactly the same concern in a discussion in Twitter.
Let's fix it. Adding statusCode is OK. Or do we have a better solution? What do you think about attaching the response object as a whole?

Any variant suits me, but fist will be better. As for me adding response object as a whole isn't needed because when we handle error, we use only statusCode from error
Thanks

@Avantjurist Would you review #41?

Let me release it and see how it works out.

Published: https://www.npmjs.com/package/react-hooks-async/v/3.10.0

Could you please  my comment in closed PR

https://www.npmjs.com/package/react-hooks-async/v/3.10.1
Fixed. Thanks for your review!


Issue #259 - Added routes for each categories in the Book Categories section and created blank pages for each of the pages

…reated blank pages for each of them
Description
A clear and concise description of what the PR does.

This PR does the following:

Adds routes for each categories in the Book Categories section and created blank pages for each.

Related Issues
Link any related issues using the format Fixes #issue_number.
This helps to automatically close related issues when the PR is merged.

Fixes #259

Changes
List the detailed changes made in this PR.

Added a new feature to ...
Refactored the ...
Fixed a bug in ...

Testing Instructions
Detailed instructions on how to test the changes. Include any setup needed and specific test cases.

Pull this branch.
Run npm install to install dependencies.
Run npm test to execute the test suite.
Verify that ...

Screenshots (if applicable)
Add any screenshots that help explain or visualize the changes.
Additional Context
Any additional context or information that reviewers should be aware of.

This PR is based on the following...

Checklist
Make sure to check off all the items before submitting. Mark with [x] if done.

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x ] I am working on this issue under GSSOC

I missed the last point in the checklist. I am working on this issue under GSSOC'24 ext.

…reated blank pages for each of them
Description
A clear and concise description of what the PR does.

This PR does the following:

Adds routes for each categories in the Book Categories section and created blank pages for each.

Related Issues
Link any related issues using the format Fixes #issue_number. This helps to automatically close related issues when the PR is merged.

Placeholder: "Fixes Added workflow for closing old PRs  #123"

Changes
List the detailed changes made in this PR.

Added a new feature to ...
Refactored the ...
Fixed a bug in ...

Testing Instructions
Detailed instructions on how to test the changes. Include any setup needed and specific test cases.

Pull this branch.
Run npm install to install dependencies.
Run npm test to execute the test suite.
Verify that ...

Screenshots (if applicable)
Add any screenshots that help explain or visualize the changes.
Additional Context
Any additional context or information that reviewers should be aware of.

This PR is based on the following...

Checklist
Make sure to check off all the items before submitting. Mark with [x] if done.

[x]  I have performed a self-review of my code
[x]  I have commented my code, particularly in hard-to-understand areas
[x]  My changes generate no new warnings
[x ] I am working on this issue under GSSOC

Kindly add the issue no you are addressing @Lanaanvar

Please add some screenshots of the changes/features you have implemented.

Also kindly resolve these conflicts @Lanaanvar

Ok I will

@Lanaanvar look into the requested changes and then we can merge your branch.

ok

Please add some screenshots of the changes/features you have implemented.

The same way, blank pages are created for all categories in the section

Thank You


chore: upgrade dokka gradle plugin

Motivation and Context
Due to an issue between dokka and gradle (describe here), the build is failing on my machine.
Description
The dokka gradle plugin has been upgraded to v1.4.30 as suggested in that GitHub issue and the changes in the generated documentation should be minimal.
Testing
I have been able to generate the documentation successfully.
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hey there! Thank you for the contribution!
As far as I'm aware, the smithy-rs maintainers don't make use of the Dokka documentation for any of the Kotlin modules, which is probably why the newer codegen-server modules don't have it. As such, I'm leaning more towards removing it entirely from the build scripts. I want to understand better where you're coming from. What led you to try building these docs, and do you find the output useful for that goal?

I do check the generated documentation from time to time to visually browse the code (although having them published like the smithy javadoc would be really nice). In our particular case, we are publishing the smithy rust modules (more specifically codegen-core, codegen-client, codegen-server and rust-runtime) to a private Maven registry and this was causing issues while preparing the package in GitHub actions (as well as in my local machine).
My suggestion here is to keep it and let it be generate by default at the root project in order to simplify configuration the subprojects.


git+ssh for private git repositories

It would be really useful if it would be possible to import private repositories using git+ssh for private github repositories for example.

The .netrc method is working for me with go get, but not with godep restore. Any ideas?


AzureADGraphClient does not handle 429

Environment
Azure SpringBoot 2.1.7
Summary
AzureADGraphClient  throws:
Caused by: java.io.IOException: Server returned HTTP response code: 429 for URL: https://graph.windows.net/me/transitiveMemberOf?api-version=1.6
    at HttpURLConnection.getInputStream0(HttpURLConnection.java:1919)
    at HttpURLConnection.getInputStream(HttpURLConnection.java:1515)
    at HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
    at AzureADGraphClient.getResponseStringFromConn(AzureADGraphClient.java:74)
    at AzureADGraphClient.getUserMembershipsV1(AzureADGraphClient.java:61)
    at AzureADGraphClient.loadUserGroups(AzureADGraphClient.java:89)
    at AzureADGraphClient.getGroups(AzureADGraphClient.java:85)

Reproduce steps
In happens in our production system from time to time. I guess it happens on case of burst activity
Expected Results
I would expect AzureADGraphClient to wait by default the number of seconds described in Retry-After header before retrying at least once the call.
https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-request-limits#waiting-before-sending-next-request
Actual Results
AzureADGraphClient  throws without retrying at least once

Thanks for your feedback, we will inspect it and give you a response later.


Remove silence overwritte during screenshot

Description

During take screenshot, when extension is missed then existing file could be silent overwritte.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References

How has this been tested?

[x] manually
[x] all test passed

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

Hm. There is Question if it should be class for save screenshot, or more general case?

I think for now I'd just focus on reducing the duplicate code between QtMainWindow._screenshot_dialog and QtViewer._screenshot_dialog, but there could be other places where we could reduce duplicate code in the future.

Switch to using instance of QFileDialog is possibility to use setDefaultSuffix method which allow remove whole logic of adding suffix.

I remember us trying a bunch of stuff with that, but we could never get it working the way we wanted, see a long discussion with @GenevieveBuckley and I trying to do that here https://github.com/napari/napari/pull/944#discussion_r375638126, so I think I'd rather stick with the logic we have and just fix the "overwrite" bug you observed rather than try that again.

And what You think about store history of last visited locations instead of only last one?

I'm open to that, I think that is fairly standard these days.

 In PartSeg I give up from using native dialog. Th Qt one is much simpler to control.

The whole while is obsolete if ther wil be decision to use qt dialog instead of native one.
I do not found way to prevent close native dialog when select accept. I could hide while in additional functionbut it not looks like thing you expect. You could simple compare both dialog with change value of qt_dialog in constructor.

The whole while is obsolete if ther wil be decision to use qt dialog instead of native one.
I do not found way to prevent close native dialog when select accept.

Hmm ok, I think we still have a strong preference towards using the native. I can look more into this later tonight

Recursion may be an answer.
I have hope that it does not produce multiple save dialog on some system.


Preserving symlinks in sources directories creates dangling symlinks in the staging directories

#1580 introduced in reframe the default behaviour of copying symlinks onto the stage directory as symlinks rather than copying the content of the directory that the symlink points to. This works fine when the symlink points to another file that is under the same directory tree. However, this will create dangling symlinks if the original link pointed to a file/directory outside this directory tree.
In reframe, this could happen when a test case needs resources defined in another test.

We could do one of the following:

Perform the copy, check for broken symlinks and perform a copy of the actual file (without respecting the symlink).
Find out which links are going to be broken, ignore them in the first copy and then those copy manually without respecting the symlink.

Why not simply reverting #1580? Did this PR introduce any functionality that can't be achieved by marking the symlinks to be preserved in the reframe tests with self.readonly_files?

Why not simply reverting #1580? Did this PR introduce any functionality that can't be achieved by marking the symlinks to be preserved in the reframe tests with self.readonly_files?

@jjotero Yeah we can do this, or have another option whether to follow symlinks on the src directory or not.

@jjotero Yeah we can do this, or have another option whether to follow symlinks on the src directory or not.

If there isn't any scenario that breaks if #1580 is reverted, I think that'd be the cleanest (and also the easiest) solution. Regarding the option of treating symlinks inside src differently to symlinks elsewhere, I have the feeling that such changes might open other fronts for potential bugs.

If there isn't any scenario that breaks if #1580 is reverted, I think that'd be the cleanest (and also the easiest) solution. Regarding the option of treating symlinks inside src differently to symlinks elsewhere, I have the feeling that such changes might open other fronts for potential bugs.

At the time, I did not know about self.readonly_files.
I am ok with reverting.

At the time, I did not know about self.readonly_files.
I am ok with reverting.


periph-play: create an interactive web ui to run adhoc programs

Similar in spirit to https://play.golang.org/ and BoneScript which is on BeagleBone's default image.
The rough idea looks like:

Create a template:package main
import (
  "log"
  "periph.io/x/periph/host"
)
func main() {
  if _, err := host.Init(); err != nil {
    log.Fata(err)
  }
  {{.UserCode}}
}

Inject the user's code in the template.
Run goimports -w, found at https://golang.org/x/tools/cmd/goimports
Send the formatted user code back to the Web UI.
Report errors. In this case, the formatted code should be sent back with highlighting.
Stream results back via websocket.
Expose a Stop button that sends SIGTERM to the process.

Moved to https://github.com/periph/cmd/issues/1


[BUG] Unable to set TxPwr to OFF on Air band after set LOW, MID or HIGH

Unable to set TxPwr to OFF on Air band after set LOW, MID or HIGH.
Actually unable set TxPwr to OFF on any other band and mode. No OFF option at all.
To Reproduce
Steps to reproduce the behavior:

set VFO to air band for example 122000
Press menu and navigate to TxPwr (set to OFF as default)
Press menu again and set TxPwr to LOW or any other
Comfirm choice
Attempt to change TxPwr to OFF - no such option when pressing UP-DOWN keys. Only LOW, MID, High

Expected behavior
OFF - LOW - MID - HIGH options on TxPwr menu item
Details:

Firmware version: NUNU 20.5
Bandwidth: 25k
Power: OFF
RxAGC: LSOW
Gain settings (LNAs/LNA/PGA):
other:

Additional context

Yea I've noticed that power setting sometimes is not displayed. Not sure how that's supposed to work.
I will look into it.

Looking at the code, there should be no OFF option, so the bug is rather that something sets TxPwr to OFF.
I've might have experienced it once, however I was not able to reproduce it.
If someone manages to reproduce it, please post the steps here.


[move-only] Add support for escaping mutable vars.

rdar://105294941

@swift-ci smoke test

I did this in a different PR


Movie Details screen does not come up - Exception

Sorry about this, another issue I found.
So, the Home Page loads now with me explicitly providing the API key and URL. However, now clicking on a movie crashes with the following exception.
HttpExceptionWithStatus (HttpException: Invalid statusCode: 404, uri = https://image.tmdb.org/t/p/w780)
I am assuming it is not passing the movie id.
HttpExceptionWithStatus (HttpException: Invalid statusCode: 404, uri = https://image.tmdb.org/t/p/w780)

hi @vnl no problem at all, we all learn with this.
statically passing the API_KEY and baseurl won't solve you have to properly init the application
please refer to https://github.com/Iamzaryab/Movie-Application-Flutter-Clean-Architecture-RiverPod#getting-started
so basically steps are simple
1.Create a .env file in root directory
2.https://www.themoviedb.org/settings/api create an API from this website
3. BASE_URL=https://api.themoviedb.org/3/
4.API_KEY=PASTE_YOUR_API_KEY
that's it project will start working as expected

if you still find any issue please let me know

So, after sorting out the other issue I still get this issue.
I think it is trying to load pictures which are not there from the API.

Thank you for helping out. It turns out that if I had used Android Studio and just run the app instead of debugging, it would work straight away.
Thanks again @Iamzaryab I appreciate you spending time and explaining that.

No problem at all! I'm really pleased to hear that app is working now. If you ever have more questions or need help with anything else, just let me know.


Create a minimal test suite

What is the smallest set of files that tests everything we currently test with our larger test suite? Would it be worth determining this? I can imagine 10 JSON files that constitute an exhaustive test suite.

This is not a problem.


launch: program '' does not exist.

Steps to Reproduce:

Create an asp.net core app
Start the program with debugging.

Is there any way to fix the debugger.
The project runs properly without debugging.

Using VS for Mac 2019 build 17 - 8.10.14

@Satvik-web I don't think this repository contains any logic which would cause this error.  I would suggest filing a feedback ticket in VS for Mac with the problem details so someone can investigate.


Queries for popular items view

What is the problem to solve?
What are people searching for when they view

https://wellcomecollection.org/works/fuc864rh
https://wellcomecollection.org/works/mg56yqa4

What stage of research is it? (discovery/general usability testing/post release)
discovery
What are the objectives?

Identify common search behaviour that might benefit from a filter
Identify odd matches to queries for improvements to search

What are the assumptions?

that the views are by different users

What research technique is required?
Python

Investigating views of https://wellcomecollection.org/works/fuc864rh
Looking at 100,000 observations 28/6 - 1/7, 39 anonymousIds submitted the query, 'art of science' in image search and then used the red filter. No one tried any other filter (this is the first colour) or selected any other (the photo of the flask is the first result.) It's a pretty spectacular photo but still seems strange no one viewed anything else.

Investigating views of https://wellcomecollection.org/works/mg56yqa4
Code that worked for above returns only views and no searches. Is it possible to view a work without querying it (eg via Internet Archive) or is there something wrong with the code?
Pull request for review:
https://github.com/wellcomecollection/data-science/pull/86

Yes it is possible for users to click on a link on a site like wikipedia and fetch up at the item page. I checked Google Search Console and it seems that this is exactly what viewers of https://wellcomecollection.org/works/mg56yqa4 did. Case closed.
@harrisonpim if you could review the pull request, I'll close this ticket.

sorry tacey! will get on that now


Automatically call removeEmpty for all tokenizer calls

Right now implementors need to manually perform something like removeEmpty. This should be done automatically (but overridable) by the logic calling tokenize.
Issue raised in #63

:+1:

Released in 2.0.0

Nice! :+1: @kpdecker


Cannot change issuer field in FederatedIdentityCredential

What happened?
I created a simple FederatedIdentityCredential using the spec here: https://marketplace.upbound.io/providers/upbound/provider-azure-managedidentity/v0.41.0/resources/managedidentity.azure.upbound.io/FederatedIdentityCredential/v1beta1
It creates successfully. Then, I edit the issuer field to set a different value and I get the following:
- lastTransitionTime: "2024-01-10T22:29:44Z"
  message: async update failed: refuse to update the external resource: cannot change the value of the argument "issuer" from "old" to "new"
  reason: AsyncUpdateFailure
  status: "False"
  type: LastAsyncOperation

How can we reproduce it?

Create a valid FederatedIdentityCredential
Wait until it is synced and ready
Edit the resource's spec.forProvider.issuer field
Describe the resource to see the status.condition field containing the error

Note: Even though the update fails, it still shows the resource as Synced + Ready = True. Is that also a bug?
What environment did it happen in?

Crossplane Version: v1.14.5
Provider Version: v0.41.0
Kubernetes Version: v1.28.3
Kubernetes Distribution: AKS

Note that the azurerm provider does not mention any field being immutable: https://registry.terraform.io/providers/hashicorp/azuread/latest/docs/resources/application_federated_identity_credential
The Azure Portal also seems to allow editing the field.

@turkenf Thank you for your response!
You are indeed right. I am used to the azurerm documentation mentioning when fields force a recreate and hadn't thought checking the actual provider code.
I understand why this behaviour is replicated here.
My follow up question would be: is it possible to simply refuse the resource apply rather than accept the apply and then shoot an error that says update failed? I feel like for this type of error, it's best to fail as early as possible.
Thanks!

My follow up question would be: is it possible to simply refuse the resource apply rather than accept the apply and then shoot an error that says update failed? I feel like for this type of error, it's best to fail as early as possible.

Yes, possible, the related issue: https://github.com/crossplane/upjet/issues/78

Awesome! Will close this issue then!
Thank you for the help :)


proxy error { [Error: connect ECONNREFUSED <IP_ADDRESS>:80]

Would like to deploy this boilerplate to heroku but getting the above error.  Build is successful and website loads but routing seems broken because navigating pages via the navbar does not update the page.  Both master and heroku branch produce the same error.  Applied the heroku specific steps including:

Remove the "PORT": 8080 line from the betterScripts / start-prod section of package.json.
heroku config:set --app myapp NODE_ENV=production
heroku config:set --app myapp NODE_PATH=./src
heroku config:set --app myapp NPM_CONFIG_PRODUCTION=false
created Procfile in root directory with contents:  web: node bin/server.js

Full error from heroku logs --tail
2016-03-02T22:59:55.858547+00:00 heroku[router]: at=info method=GET path="/ws/?EIO=3&transport=polling&t=LCvZoIr" host=myapp.herokuapp.com request_id=65ac0375-dcc2-4d53-9ca5-a1b10b119705 fwd="<IP_ADDRESS>" dyno=web.1 connect=1ms service=4ms status=500 bytes=321
2016-03-02T22:59:55.853682+00:00 app[web.1]: proxy error { [Error: connect ECONNREFUSED <IP_ADDRESS>:80]
2016-03-02T22:59:55.853693+00:00 app[web.1]:   code: 'ECONNREFUSED',
2016-03-02T22:59:55.853729+00:00 app[web.1]:   errno: 'ECONNREFUSED',
2016-03-02T22:59:55.853730+00:00 app[web.1]:   syscall: 'connect',
2016-03-02T22:59:55.853731+00:00 app[web.1]:   address: '<IP_ADDRESS>',
2016-03-02T22:59:55.853732+00:00 app[web.1]:   port: 80 }
Demo link for this boilerplate seems to work fine on heroku?  Did I miss something?

I'm pretty sure its related to how you created a Procfile. You mentioned that your Procfile only runs the node bin/server.js while if you look at the npm run start it runs both the bin/server.js and the bin/api.js. I haven't ran it in heroku so not entirely sure what you're missing. But just wanted to point this out.

@metagearsolid did you find the solution. I have the same issue without heroku.


HDFS-16175.Improve the configurable value of Server #PURGE_INTERVAL_NANOS.

…ANOS.

Description of PR
How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m  4s

trunk passed

+1 :green_heart:
compile
23m 32s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m 50s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  9s

trunk passed

+1 :green_heart:
mvnsite
1m 43s

trunk passed

+1 :green_heart:
javadoc
1m  7s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 47s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 31s

trunk passed

+1 :green_heart:
shadedclient
16m 14s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 57s

the patch passed

+1 :green_heart:
compile
21m 59s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
21m 59s

the patch passed

+1 :green_heart:
compile
19m 21s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
19m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m  9s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 1 new + 282 unchanged - 0 fixed = 283 total (was 282)

+1 :green_heart:
mvnsite
1m 38s

the patch passed

+1 :green_heart:
javadoc
1m  6s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 38s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 41s

the patch passed

+1 :green_heart:
shadedclient
16m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 23s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m  0s

The patch does not generate ASF License warnings.

187m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3307

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux f7b8dd04e614 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 99409a5e9cb8b7eeefd71bb73b608ee7248616e8

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/1/testReport/

Max. process+thread count
1262 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

@jojochuang, @virajjasani, can you help review the code.
If there are some imperfections, welcome to communicate, and I will work hard to promote improvement.
thank you very much.

OK.
Thanks @jojochuang  for the comment. I will continue to work.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 24s

trunk passed

+1 :green_heart:
compile
22m 40s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m 34s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  8s

trunk passed

+1 :green_heart:
mvnsite
1m 39s

trunk passed

+1 :green_heart:
javadoc
1m 10s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 44s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 25s

trunk passed

+1 :green_heart:
shadedclient
15m 39s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 58s

the patch passed

+1 :green_heart:
compile
21m 27s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
21m 27s

the patch passed

+1 :green_heart:
compile
19m 15s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
19m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m  8s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 1 new + 282 unchanged - 0 fixed = 283 total (was 282)

+1 :green_heart:
mvnsite
1m 35s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m  7s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 40s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 38s

the patch passed

+1 :green_heart:
shadedclient
16m 32s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 47s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 57s

The patch does not generate ASF License warnings.

184m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3307

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux eaf8029a3eb7 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7accd25129849534ebe17f85ce8117ce7f20b141

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/2/testReport/

Max. process+thread count
2149 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  5s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 45s

trunk passed

+1 :green_heart:
compile
22m 39s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m 23s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m 31s

trunk passed

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 33s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 25s

trunk passed

+1 :green_heart:
shadedclient
18m 17s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 57s

the patch passed

+1 :green_heart:
compile
22m  1s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
22m  1s

the patch passed

+1 :green_heart:
compile
19m 19s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
19m 19s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 59s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 1 new + 282 unchanged - 0 fixed = 283 total (was 282)

+1 :green_heart:
mvnsite
1m 29s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 36s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 56s

the patch passed

+1 :green_heart:
shadedclient
20m 51s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 40s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

191m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3307

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 372f42a0f2de 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a818ea8f61df5c7ba46c52540905db2ca414303f

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/3/testReport/

Max. process+thread count
3137 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Thanks @jojochuang for the comment.
I have submitted some new codes, could you please review them?
Thank you very much.

Thanks @jojochuang  for the comment.
I will make some changes later.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 43s

trunk passed

+1 :green_heart:
compile
22m 44s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m 21s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m 32s

trunk passed

+1 :green_heart:
javadoc
1m  2s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 34s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 24s

trunk passed

+1 :green_heart:
shadedclient
18m  3s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 57s

the patch passed

+1 :green_heart:
compile
22m  4s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
22m  4s

the patch passed

+1 :green_heart:
compile
20m 59s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
20m 59s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 56s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 1 new + 282 unchanged - 0 fixed = 283 total (was 282)

+1 :green_heart:
mvnsite
1m 35s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m  1s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 36s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 45s

the patch passed

+1 :green_heart:
shadedclient
19m 17s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
19m  8s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

193m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3307

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux eed726a7a1af 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / dc4ad1a97276f0cf62a4e863d951a5be501ae0ec

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/4/testReport/

Max. process+thread count
1252 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

I submitted some new codes and got successful verification from jenkins.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m  5s

trunk passed

+1 :green_heart:
compile
22m 38s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m  3s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  2s

trunk passed

+1 :green_heart:
mvnsite
1m 35s

trunk passed

+1 :green_heart:
javadoc
1m 10s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 39s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 34s

trunk passed

+1 :green_heart:
shadedclient
15m 52s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 55s

the patch passed

+1 :green_heart:
compile
22m 23s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
22m 23s

the patch passed

+1 :green_heart:
compile
19m 42s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
19m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m  3s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 1 new + 282 unchanged - 0 fixed = 283 total (was 282)

+1 :green_heart:
mvnsite
1m 36s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m  6s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 38s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 54s

the patch passed

+1 :green_heart:
shadedclient
18m 26s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
41m 59s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

210m  1s

Reason
Tests

Failed junit tests
hadoop.ha.TestZKFailoverControllerStress

hadoop.ipc.TestRetryCache

hadoop.ipc.TestCallQueueManager

hadoop.metrics2.source.TestJvmMetrics

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3307

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 1b8547543f35 4.15.0-151-generic #157-Ubuntu SMP Fri Jul 9 23:07:57 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 87c6a82acbfe4e1d6ff83708a0df4c6c2ffa9021

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/5/testReport/

Max. process+thread count
1010 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3307/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Some anomalies happened here in jenkins.
But it does not seem to be related to the code I submitted.

@ayushtkn , can you help review the code.
Thank you very much.

Thanks @ayushtkn for the comment.

@ayushtkn , thanks for your help.
I don't know if this PR request can be merged into the trunk branch. If can, can you help me deal with it?
thank you very much. (I'm not sure if I should make such request.)

Merging it


1201_1 renww

やりなおし

11:57:56 AM: ---------------------------------------------------------------------
UNSUPPORTED BUILD IMAGE
The build image for this site uses Ubuntu 16.04 Xenial Xerus, which is no longer supported.
To enable builds for this site, select a later build image at the following link:
https://app.netlify.com/sites/frosty-panini-d896ea/settings/deploys#build-image-selection
For more details, visit the build migration guide:
https://answers.netlify.com/t/please-read-end-of-support-for-xenial-build-image-everything-you-need-to-know/68239

ビルドイメージのサポートが終了してしまっているようでです．


Remove URL from frontity exports

We've removed support for Node 8 and therefore deprecated the URL import from "frontity". This import was the only thing we had for backward compatibility with Node 8 so it's safe to deprecate it now.
The deprecation work has been done in this PR: https://github.com/frontity/frontity/pull/543

I've branched this out of master. I'll rebase it in code.

Done 👍

@luisherranz For next PR's related to Code Releases in this docs repository we simplified the process by:

not using the code branch
creating PR's directly against master
not merging these PR's until the release is done

https://github.com/frontity/docs/wiki/Code-Releases#documentation-changes-before-code-releases

Oh, I didn't know. Do you want me to rebase it again onto master or we can merge this as it is?

Oh, I didn't know. Do you want me to rebase it again onto master or we can merge this as it is?

If you don't mind I'd prefer if you rebase  it again onto master as we're not using code branch anymore and I'm not sure what's in there

Sure!

Done 🙂

@luisherranz Can this PR be merged?  Do you prefer me to do it?

Don't you wait until the next release?

Don't you wait until the next release?
Yes.

As this code has been released according. to this → https://github.com/frontity/frontity/releases/tag/frontity%401.11.0
I'm merging these changes


Set id field unsigned

Set id field unsigned at creation, negative values are not needed.

@lpotherat Thanks！


SolaceIO: separate auth and session settings

Refactored to separate authentication and session settings, and allow inheritance and overriding of SessionService.
Depends on https://github.com/apache/beam/pull/32400, waiting for that to be merged

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

@bzablocki @Abacn what are next steps on this PR?

It's blocked by https://github.com/apache/beam/pull/32400, waiting for that to be merged. I'll be monitoring it and ping you once it is ready for a review.

This PR is unblocked now, @sjvanrossum, would you mind taking a look? :)

assign set of reviewers

Hi @Abacn ! Would you mind taking a look a merging if it looks good? @sjvanrossum already reviewed and approved. thanks!

Friendly ping @m-trieu, @chamikaramj or @Abacn  :)

sorry for veing late, however I didn't see a review history for this PR. Coild you please confirm the comment above refer to this PR, and if so reviewer please review in this PR.


Added support of multiple Gateway API classes.

RFE https://github.com/kiali/kiali/issues/6429a

This breaks backward compatibility. Are we sure we want to do this?

Before this PR, the only supported GatewayClass was "istio", which was the default if no configuration touched, but now, when several implementations of Gateway should be supported, if still no configuration touched, the default is "istio". So we need this new way of config.

Before this PR, the only supported GatewayClass was "istio", which was the default if no configuration touched, but now, when several implementations of Gateway should be supported, if still no configuration touched, the default is "istio". So we need this new way of config.

OK. Sounds like this was rarely touched by a user. We should just document this change in the release notes (I think there is a "Breaking change" section somewhere - or something like that) where we should mention it.

OK. Sounds like this was rarely touched by a user. We should just document this change in the release notes (I think there is a "Breaking change" section somewhere - or something like that) where we should mention it.

+1, we can document the config change.  But because the previous attribute supported only one value, the default, it should be a no-op to replace it.


vncserver: Allow fb operation while no connection

Summary
VNC's frame buffer device should not block application's draw operation in any scenario if init ok.
Impact
VNC server
Testing
sim:vncserver

So, now the application using FB will start even when VNC client is not connected, right? I think it is the correct behavior, but there could be cases where the user want to see the application starting when he connects, the fbdemo is a good example.

Yes, how about enable nsh and let fb demo as a command line application so user can lauch it manually ?

So, now the application using FB will start even when VNC client is not connected, right? I think it is the correct behavior, but there could be cases where the user want to see the application starting when he connects, the fbdemo is a good example.

user can debug the initialization in sim easily, so is it critical to wait for connection at the initial phase?

@acassis Yes, how about enable nsh in sim:vncserver to let fb demo as a command line application? So user can launch it manually.

Yes, I think it's good idea, let's do it @no1wudi ?

Yes, in fact seen the "nsh>" over VNC is a nice feature and could be an alternative to Telnet :-)


Generate AI commit message automatically when git stage changes

Current
Copilot's AI generate commit message is great, but requires a button press.
Proposed feature
Add user setting to enable generate an AI commit message automatically when the git stage contents change, i.e. when new lines or files are staged or unstaged.
This will make the workflow even smoother.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Shape-change op testing

Testing for Broadcast, Reshape, Pad, and Slice
EDIT: and Transpose
To-do:

Figure out better method for constant padding value evaluation
Debug Symmetric/reflect padding
Test slice

Lingering issue: Reflect and Symmetric paddings still fail on PlaidML compiler optimization passes; a manual construction of symmetric padding using tf.slice+tf.reverse+tf.concatenate works fine

Note, the branch is currently referencing a sub-branch of PlaidML; this reference should be fixed before merging


Can´t open and use these SCAD files

I found the solution. I just had to download all files and open it from the extracted folder....
Close my issue, please.

I freshly installed OpenSCAD version 2021.01.
When opening your models there are different problems like this:
OpenSCAD 2021.01
https://www.openscad.org/
Copyright (C) 2009-2021 The OpenSCAD Developers
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
Loaded design 'C:/Users/---/Downloads/gridfinity_basic_cup.scad'.
WARNING: Can't open library 'gridfinity_cup_modules.scad'.
Compiling design (CSG Tree generation)...
WARNING: Ignoring unknown module 'basic_cup' in file gridfinity_basic_cup.scad, line 71
Compiling design (CSG Products generation)...
Geometries in cache: 0
Geometry cache size in bytes: 0
CGAL Polyhedrons in cache: 0
CGAL cache size in bytes: 0
Compiling design (CSG Products normalization)...
Normalized tree has 1 elements!
Compile and preview finished.
Total rendering time: 0:00:00.050
Loaded design 'C:/Users/---/Downloads/gridfinity_baseplate.scad'.
WARNING: Can't open include file 'gridfinity_modules.scad'.
Compiling design (CSG Tree generation)...
WARNING: Ignoring unknown variable 'gridfinity_pitch' in file gridfinity_baseplate.scad, line 72
WARNING: undefined operation (undefined / number) in file gridfinity_baseplate.scad, line 72
WARNING: undefined operation (undefined - number) in file gridfinity_baseplate.scad, line 72
WARNING: undefined operation (undefined - number) in file gridfinity_baseplate.scad, line 72
WARNING: Ignoring unknown module 'cornercopy' in file gridfinity_baseplate.scad, line 74
WARNING: Ignoring unknown module 'gridcopy' in file gridfinity_baseplate.scad, line 77

You also need to download gridfinity_cup_modules.scad


Jenkins Master failed to connect to Windows Slave agent in ECS cluster

I have using ECS cloud service plugin to create windows slave agent dynamically. i am able to build the container and its in running state , however the jenkins master is failed to connect the agent and agent status is offline in master
ECS Template Slave

Log:

Final error:

Final error:


NamedImageTransformer throws IndexOutOfBoundsException

Required Information

[X] AEM Version, including Service Packs, Cumulative Fix Packs, etc: CloudService
[X] ACS AEM Commons Version: 4.11
[ ] Reproducible on Latest? yes/no

Expected Behavior
stacktraces should not happen:
Actual Behavior
We see this stacktrace:
[<IP_ADDRESS> [1633015494300] GET /content/dam/path/to/some/asset.jpg.transform/1200/image.jpg HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught Throwable
java.lang.IndexOutOfBoundsException: off < 0 || len < 0 || off + len > b.length!
at java.desktop/javax.imageio.stream.ImageInputStreamImpl.readFully(Unknown Source)
at java.desktop/com.sun.imageio.plugins.tiff.TIFFIFD.readFieldValue(Unknown Source)
at java.desktop/com.sun.imageio.plugins.tiff.TIFFIFD.initialize(Unknown Source)
at java.desktop/com.sun.imageio.plugins.tiff.TIFFImageMetadata.initializeFromStream(Unknown Source)
at java.desktop/com.sun.imageio.plugins.tiff.TIFFImageReader.readMetadata(Unknown Source)
at java.desktop/com.sun.imageio.plugins.tiff.TIFFImageReader.seekToImage(Unknown Source)
at java.desktop/com.sun.imageio.plugins.tiff.TIFFImageReader.prepareRead(Unknown Source)
at java.desktop/com.sun.imageio.plugins.tiff.TIFFImageReader.read(Unknown Source)
at com.day.image.Layer.(Layer.java:706)
at com.day.image.Layer.(Layer.java:599)
at com.day.image.Layer.(Layer.java:522)
at com.day.cq.commons.ImageHelper.createLayer(ImageHelper.java:173)
at com.day.cq.commons.ImageResource.getLayer(ImageResource.java:633)
at com.adobe.acs.commons.images.impl.NamedTransformImageServlet.getLayer(NamedTransformImageServlet.java:446)
at com.adobe.acs.commons.images.impl.NamedTransformImageServlet.doGet(NamedTransformImageServlet.java:217)
The image dimensions of the original rendition are 1890x1890px
(It's totally clear to me that renditions should be created/handled on AEM CS differently, but I think that this issue ist most likely to appear on AEM 6.x as well.)

@joerghoh whats the cause of this exactly?
Is the request here is to capture this exception and throw the appropriate servlet exception w/ status?


SqliteException: SQLite Error 1: 'no such table: Projects'.

.NET SDK Version: 5

Steps to Reproduce:

Visual Studio, start new project from template item, build, run via buttons
Main page loads fine, swagger loads fine
Click on the any of the 'Projects' links for MVC or Pages
Error is thrown..

Sorry, there's probably an easy step to initialize the sqllite db (i think the last version of the project had an api call for it?) but i'm not finding anything in the tutorial info.

If you remove the database.sqlite file from the web app root, it should recreate and seed the db correctly on the next run.

@fspataro did @yuriburger 's response help?

@ardalis @yuriburger sorry for the delay, busy week...
Yes! Deleting the sqlite file solved the problem.  Closing the item.


Add sequence number provider

When configured, this provider outputs an incrementing sequence number for every log event.
This can be useful to detect gaps in your log stream and help identify problems with your log transport.
It also makes reading logs easier as it helps the reader to distinguish between missing log lines and flaky system behavior.

Thank you for the review, I rebase the commit with your remarks applied.

Merged.  Thanks!


libguestfs: fix perl commands

Motivation for this change
Commands depending on perl such as virt-list-partitions or virt-list-filesystems were not working, as some dependencies couldn't be found by perl.
Things done
Provide dependencies via PERL5LIB wrapper.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Seems virt-list-partitions or virt-list-filesystems have been replaced: https://libguestfs.org/virt-filesystems.1.html
Is this PR still needed?

In case we still need it, I merged master into it, to fix the conflicts.

I've opened a version update for libguestfs which addresses the issue with the Perl bindings: #185015. Note that as of libguestfs 1.46, many of the CLI tools (including virt-filesystems) have moved to the new guestfs-tools project. That one is not yet packaged for NixOS, but I'm giving it a stab right now.


Support for card payments

The library does not support card payment related endpoints

The PR: https://github.com/mnastalski/przelewy24-php/pull/15/commits


Vtk 8.2.0 and QT 5.12.2

With recent version it doesn't work the code. I just get a blank screen. But I found the solution, It doesn't require a external window anymore but vtkGenericOpenGLRenderWindow.

@kate14black If you don't mind, could you share your code? I still have no luck with the latest version of VTK and QT.

@jeongkyu check my pull request. I made the changes inside. I don't know if the author will respond to it.

@kate14black Thank you very much. Unfortunately, it still didn't work in my environment and I will do further research.

Based on this article i think you wase using Canvas 3d but it deprecated in Qt 5.12 see this,
Am i right ?


Fix LB weight setting for split horizon eds

cherry-pick (#12560) from release-1.1

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hzxuzhonghu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-integ-local-tests

prow/istio-pilot-multicluster-e2e.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-integ-local-tests

prow/istio-pilot-multicluster-e2e.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-integ-k8s-tests

prow/istio-integ-local-tests.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-integ-local-tests

@rshriram: changing LGTM is restricted to assignees, and assigning you to the PR failed.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu,rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

The bot is crazy. Re-apply @rshriram 's lgtm

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
73158823aefaa112d70be90862658be4660c4451
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


aikido_master07@hotmail

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

@shahram919 This azure-docs repository deals about feedback related to particular Azure document page (like correcting doc bugs, doc enhancements, product issues related to wrong doc instructions, etc.) so if your issue is intended to update / correct / enhance anything in an Azure document then please share Azure document link / URL along with providing details around the issue else I suggest you to ask the question in public forums like Microsoft Q&A, etc.

Closing this issue for now as there is no response on it.


The Farm: Instructions can be more clear

Hi!
I hope all are doing great!
In the instructions, I've found that it is not explicitly clear what should happen in the case of ErrScaleMalfunction and fodder < 0. It can mislead one to believe it is counted as "any other error" or all cases of fodder < 0 is a negative fodder error.
To make this clear in instructions, I think it is a good idea to add a new subsection in instructions on specifying different cases for ErrScaleMalfunction.
I would like to know what are your thoughts on this.
Thank you!

Thanks for opening this issue!

In the instructions, I've found that it is not explicitly clear what should happen in the case of ErrScaleMalfunction and fodder < 0

I don't see this as a problem as if there's an ErrScaleMalfunction and you multiply a negative fodder value by 2, it'll keep being negative, so I don't think there's doubt that a negative fodder always returns a negative fodder error, regardless of ErrScaleMalfunction. But maybe I'm overlooking something?
Where I see potential confusion is if we have fodder < 0 and cows < 0, where is not clear what should be returned: negative fodder error or a SillyNephewError? Returning one or the other just depends on the order the check is made, so it might be worth have the description clarify this.

Thanks for your reply, André!
The main confusion that this might make is if one considers ErrScaleMalfunction and fodder>0 as a single case of error. This will result in considering ErrScaleMalfunction and fodder<0 as another form of error and returning 0 and the same error by mistake. Since we also have the test case with negative fodder and no error as well.
Things might be a bit more clear by writing:
"For any other error besides ErrScaleMalfunction, return 0 and the error."
For example instead of using :
For any other error, return 0 and the error.
Of course, this can be only my problem and I am overthinking things! 😅
On your point about negative fodder and cows, I totally agree! 👍

I have created a PR to address both issues. it would be great if you could review it.


Error compiling for board Nucleo-144

Hello everyone,
I'm currently working on taking a picture with the nucleo 144 STM32 H743ZI board and an OV5642 5MP camera module by using the arduino IDE.
I have downloaded the required software in the boards manager and chose the exact board.
I have also downloaded the ArduCam library from here and edited the memorysaver.h file to my needs.
But when I try running the example program from the examples file in the ArduCam library, it doesen't compile it and puts out an error as you can see in image 1.
Image 2 contains the tools settings i used.
Btw: a simple blink program worked on the board, so I suspect there is something wrong with the compatibility of the board & library, but I'm really not sure there.
Thank you for your answers
Jakob Ternes

@JakobTernes
At present, the Arducam library  doesn't compatible with the stm32 platform.

Thanks a lot, that saved me quite some unnecessary work.


EPUB generation breaks links

Most links within the EPUB are broken, as book/lua/single-file-links.lua rewrites all internal links:
Case 1: [text](/chapter/#more-stuff) -> [text](#chapter-more-stuff)
Case 2: [text](/chapter/)            -> [text](#chapter)

Links that are covered by Case 2 work, as we generate the correct links for chapter headers via templating in book/epub.md.
Unfortunately, links within each chapter now need to be prefixed by their canonical chapter link, to be caught by Case 1, which currently isn't happening.

The following warnings emitted by Pandoc during EPUB generation are also due to the broken links:
[WARNING] Duplicate identifier 'confluence' at line 16247 column 1
[WARNING] Duplicate identifier 'substitution' at line 20742 column 1

There are sections called 'Confluence' and 'Substitution' and chapters whose titles (without subtitle) are the same.

This can probably be fixed with a minor Lua filter, which walks the document, and notes down the identifier of any level 2 headers (chapter headers) and then prefixes all headers with level <2 with that identifier and a hypen.


v6.0.6

2024-01-31 v6.0.6

remove fallback to coupon.order?.total_discount_amount that caused too great promotions in some cases


docs: Replace Advanced with relevant section for user Preferences.

This is a followup commit to #30824.
Fixes https://chat.zulip.org/#narrow/stream/9-issues/topic/.F0.9F.8E.AF.20help.20not.20updated.20for.20new.20preferences.20sections/near/1899330.
git grep in the help directory will still show up results for Advanced but those are mostly used in either plain english language instructions or refer to some other part of the app. At the point of writing this commit, there were 6 results for Advanced, 4 of which were plain english, 1 refers to the Advanced settings in chrome for desktop notifications, and another one refers to Advanced configurations for channel settings.
I've added one screenshot just for reference, but don't think we need screenshots for all changes.

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Sounds good to me, thanks!

Merged, thanks @shubham-padia!


bizarre value parsing in attachInterrupt.intHandler

The local intHandler function inside attachInterrupt contains:
m.value = parseInt(Number(gpioInt[n].value), 2);

I was honestly surprised this even works at all since gpioInt[n].value is a Buffer here, and passing it to Number() makes no sense. Apparently however it just stringifies the buffer and then converts that to number. Of course passing a number to parseInt() also makes little sense, it will again stringify it and again convert it to a number.
I'd suggest changing it to parseInt(gpioInt[n].value.toString(), 2) to clarify what it's doing and avoid two pointless conversions.

This issue was moved to beagleboard/bonescript#45


Spirit Guardains does not apply damage and produces a console error.

FVTT 0.8.8
DND5e 1.3.6
AA 0.3.03
NPCs also always fail even if they make the CON throw.
Console Error:
Macros.js:212 ReferenceError: targets is not defined
at Macro.eval (eval at callScriptMacroFunction (Macros.js:167), :22:101)
at async Macro.executeMacro (Macros.js:209)
at async daeMacro (dae.js:947)
at async update (dae.js:805)

Thanks for the report


Cache certs

This got nixed in the big refactor, but it seems worthwhile (cert
generation takes 80-100ms on my machine).
@rainforestapp/core @ukd1

Actually this isn't the right place to do it, reworking.


Get a key for the API access

Second step in the procedure:
https://www.ncbi.nlm.nih.gov/clinvar/docs/api_http/

This is done now:


static markup for a protected secure path

I have a protected route that is allowed once user is logged in. i.e : path='/user/:id'
Is it possible to generate static markup for this path at runtime using this lib?  i tired using
 "reactSnapshot": {
     "include": [
        "/",
       "/user/**"]
   }

that leads to error:  `No such filr or directory`

it should be actual urls, not wildcards

@stereobooster it wouldn't work for say "/user/:id"

I suppose the only thing you can do here is to create dedicated shell page and prerender it.

yeah that is always a option, but that would require me to manually generate a sttaic page and save it to the build everytime there is a chnage to private route.

you do not need SEO/SMO for private pages, so you can refuse from prerendering. If you care about load performance - private page can not be visited without visiting public page first (login), where you can install serviceworker with the shell provided.

yeah it was mostly for the performance I wanted the pre-render for private page.  quick followup: I'm using create-react-app and i'm registering service worker in my index.js is that enough? or do I need to do anything else for the service worker to cache the static html for the private route?

by default it caches only *.js, *.css and index.html. It can happen that you need adapt it a bit https://github.com/stereobooster/react-snap/blob/master/Recipes.md#configure-sw-precache-without-ejecting

thanks for that @stereobooster. so how is  build/shell.html  generated to the build directory , If react-snap is not used?

in case if you do not use prerenderer index.html serves as shell. If you use prerenderer you can create dedicated page (/shell) and add it to include config.

cool, thanks.


Please Update the LINK request

You have altered how to request LINK.  I had to search stack exchange to find the proper way to do it, please update the video or make a note in the video about the new way to do it.

You just have to use chainlink faucet:
https://faucets.chain.link/


Fix issues reported by Go Report Card

Codecov Report

Merging #3 (3ebb4c4) into master (8443e51) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #3   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           10        10
  Lines          946       945    -1
=========================================
- Hits           946       945    -1

Flag
Coverage Δ

unittests
100.00% <100.00%> (ø)

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

Impacted Files
Coverage Δ

pkg/option/completion.go
100.00% <100.00%> (ø)

pkg/option/format.go
100.00% <100.00%> (ø)

pkg/option/option.go
100.00% <100.00%> (ø)

pkg/option/optionset.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


bitcoin gold info?

BTG forked recently, should that be added to the list?
https://bitcoingold.org

sorry I should have checked the closed Issues first


Set container data without destroying and reinitializing

Whenever rotating an image, this changes the container's size and ratio. When a user rotates an image, I'd like to have cropper re-calculate all of the values of the container on the new size.
My setup looks like this:

When the image is rotated by 90 degrees:

I need to set the container and have all internal values respect the new height and width of my defined container without calling destroy and reinitializing. This causes a flash on the screen and seems unnecessary in terms of processing to do this.

After change the size of the container, you can trigger resize event on the window to force re-render the cropper:
$(window).trigger('resize');


[WB-5679] Fixed Summary Table Fetch

https://wandb.atlassian.net/browse/WB-5679
Description
Ensures that run.summary["my_table"] properly deserializes the data.
Cases:

wandb-artifact://GQLID
wandb-artifact-client://CLIENT_ID
wandb-artifact-client://SEQ_CLIENT_ID:alias

------------- BEGIN RELEASE NOTES ------------------
Users can now use run.summary["table"] to fetch a logged table.
------------- END RELEASE NOTES --------------------
Testing
New Unit Tests

@tssweeney is this PR still relevant?