New module: app_info

Add a simple module to get application informations (status, update, etc)
This is intended to be a foundation for the next module for app management

@aalaesar package managers in general resolve better if you send the complete list of apps in one command. I know this works for example for apt and pip packages. Not sure if it is the case for occ, but could be worth to try for make it more efficient.

@aalaesar package managers in general resolve better if you send the complete list of apps in one command. I know this works for example for apt and pip packages. Not sure if it is the case for occ, but could be worth to try for make it more efficient.

hmm
I suspected that calling occ would be costly in time (maybe that's how the run_occ function is implemented that is not optimized)
There is indeed the risk for the module to badly scale (in running time) in case of large amount of application installed on an instances.
In that case I think splitting the information gathering In Two modules would be simplier:

one module to get facts about the nexcloud server with general information (all applications and update available), easy to get in a static and limited number of calls to occ.
one app_info module to get more details about one application in particular

Hello there.
I'm back after some personal issues that took me away from my projects.
I wanted to finish the app_info module.
From my point of vue, the module is finished
but the CI seems broken with concurrency issues with docker and the tests running in parallel, and also the occ install command failing somehow 😕
as the change is not related to the installation role, this can be merged.

@staticdev @wiktor2200
Gentle up :smile:  could you review the module?
it's a fairly simple one as it only gather infos for only one app

I'm not convinced only by naming for "shipped" apps, I'd personally rename it to "pre-installed", "default", "enabled_by_default' or similar. Here in documentation https://docs.nextcloud.com/server/latest/admin_manual/apps_management.html#apps-management they call them: default enabled or enabled by default.
But it's up to you, so I leave approve for your code :)

Hello there ! 😃
Thank you for your feedback .
Regarding your 2 points:
I'm simply reusing the terminology used by the occ cli to list or filter the apps that comes preinstalled with the server, but I'm not saying it's the best word.
Regarding pre installed apps I think they are not all pre-enabled, so its hard to tell which one was enabled at any given time, as the list of enabled apps is live, and there is no filter of my knowledge to list de pre enabled apps, I can't  generate this info.

Sorry also for taking long and welcome back! From my side the functional side looks good. I found a couple of issues with the imports, some are super minor/cosmetic but anyway they should be on top level.

Hello There ! :smiley:
Thank you for your feedback.
Regarding your comments we will have to decide between official  ansible doc regarding module code format or python formatting good practices :confused:
Regards
Aal.

I'm simply reusing the terminology used by the occ cli to list or filter the apps that comes preinstalled with the server, but I'm not saying it's the best word.
Regarding pre installed apps I think they are not all pre-enabled, so its hard to tell which one was enabled at any given time, as the list of enabled apps is live, and there is no filter of my knowledge to list de pre enabled apps, I can't generate this info.

Ok, so let's stick to one naming convention or we would to change it everywhere otherwise (we still can in the future).
And that's true, pre-enabled apps are hard to determine and I think it also has changed over time in official Nextcloud repo, so I agree with current solution. :)

Sorry also for taking long and welcome back! From my side the functional side looks good. I found a couple of issues with the imports, some are super minor/cosmetic but anyway they should be on top level.

Hello There ! 😃 Thank you for your feedback. Regarding your comments we will have to decide between official ansible doc regarding module code format or python formatting good practices 😕 Regards Aal.

Oh my, this documentation really surprises me. Looks like it is stopped in time. In this case, let's keep your solution. If I have some time i will create an issue on Ansible side.

closing in favor of #367


Move all benchmarks to the benchmarks project. [HPPC-53]

Issue: HPPC-53 (migrated from JIRA), created by Dawid Weiss (@dweiss), resolved Mar 14 2011

Comment by Dawid Weiss (@dweiss) (migrated from JIRA)
In trunk.


Some apps have low resolution icons displayed

It appears that some apps recently started having low resolution (64x64) icons displayed on the Flathub website for some reason. These apps are for example Firefox, Thunderbird and Minecraft Bedrock Launcher. Note that Minecraft Bedrock Launcher uses a svg icon.

Another apps where I noticed this issue are jamovi and ONLYOFFICE Desktop Editors. The first app also seems to use a svg icon, however the second one has png icons.

Another apps where I noticed this issue are jamovi and ONLYOFFICE Desktop Editors. The first app also seems to use a svg icon, however the second one has png icons.

The issue comes from using 64px icons instead of the 128px ones

The issue comes from using 64px icons instead of the 128px ones

I think is a regression of the new backend. I've filled an issue there and I'm closing this one

I think is a regression of the new backend. I've filled an issue there and I'm closing this one


Misleading exception

When trying to upload an object to s3 an exception occurs when not providing a bucket name in the PutObjectRequest.
Expected Behavior
The exception message refers to the empty bucket name
Current Behavior
The exception complains about the x-amz-server-side-encryption header:
Amazon.S3.AmazonS3Exception: x-amz-server-side-encryption header is not supported for this operation.
Possible Solution
Exception should state the problem and not send users to chase unrelated problems
Steps to Reproduce (for bugs)
try to upload a document using the following request:
PutObjectRequest request = new PutObjectRequest
{
BucketName = null,
Key = "someKye",
InputStream = stream,
ServerSideEncryptionMethod = ServerSideEncryptionMethod.AES256
};
Context
well.... trying to upload a document
Your Environment

AWSSDK.Core version used: <IP_ADDRESS>
Service assembly and version used:
Operating System and version: Win 10
Visual Studio version:  -
Targeted .NET platform:  Core 2.1

.NET Core Info

.NET Core version used for development: 2.1.302

Thank you for reporting this.  I was able to reproduce it, so I'll look into how to fix it.  We're working towards making our error messages more helpful.  This was a good catch.


[Bug]: boundingBox() returns coordinates for elements with visibility: hidden

Minimal, reproducible example
import { launch } from 'puppeteer';

export async function isElementVisibleByBoundingBox(elementHandle) {
  return Boolean(await elementHandle.boundingBox());
}

export async function getVisibleElementByBoundingBox(page, selector) {
  const element = await page.$(selector);
  if (element && (await isElementVisibleByBoundingBox(element))) {
    return element;
  }
}

(async () => {
  const browser = await launch({ headless: false });
  const page = await browser.newPage();

  await page.goto('https://puppeteer-boundingbox-isvisible.vercel.app/');

  const elementWithBoundingBox = await getVisibleElementByBoundingBox(
    page,
    '[data-test-id="link-about"]',
  );

  if (elementWithBoundingBox) {
    console.log('[data-test-id="link-about"] is visible with boundingBox()');
  } else {
    console.log(
      '[data-test-id="link-about"] is not visible with boundingBox()',
    );
  }

  await browser.close();
})();

Error string
no error
Bug behavior

[ ] Flaky
[ ] PDF

Background
No response
Expectation
The boundingBox() method should return null if an element is not visible, including if it has the CSS property visibility: hidden. This is stated in the Puppeteer documentation:

This method returns the bounding box of the element (relative to the main frame), or null if the element is not visible.

Expected Puppeteer test result:
[data-test-id="link-about"] is not visible with boundingBox()

Reality
The boundingBox() method returns the coordinates with the width and height of an element even if it has the CSS property visibility: hidden. This means that tests that use boundingBox() to check if an element is visible can fail even if the element is not actually visible on the page.
Actual Puppeteer test result:
[data-test-id="link-about"] is visible with boundingBox()

Steps to reproduce:

Clone repo with git clone https://github.com/ProchaLu/puppeteer-boundingbox-isvisible.git
install the dependencies with pnpm install
run the test with node util/test.mjs

If you want to test locally and make some changes, don't forget to change the URL in the util/test.mjs file.
Puppeteer configuration file (if used)
No response
Puppeteer version
21.5.0
Node version
v20.9.0
Package manager
pnpm
Package manager version
8.9.2
Operating system
macOS

Follow up issue to

https://github.com/puppeteer/puppeteer/issues/7463

Workaround:
As a workaround, I use isVisible() to check if the element is visible or not.
export async function isElementVisibleByIsVisible(elementHandle) {
  return await elementHandle.isVisible();
}

export async function getVisibleElementByIsVisible(page, selector) {
  const element = await page.$(selector);
  if (element && (await isElementVisibleByIsVisible(element))) {
    return element;
  }
}

Tests with different CSS properties that hide elements

display: none

[data-test-id="link-about"] is not visible with boundingBox()
[data-test-id="link-about"] is not visible with isVisible()

opacity: 0

[data-test-id="link-about"] is visible with boundingBox()
[data-test-id="link-about"] is visible with isVisible()

Thank you for the thorough explanation and examples.
I believe that the current Puppeteer implementation are correct as visibility is said to be ... CSS property shows or hides an element without changing the layout of a document. which implies that it still affects the layout and has an observable boundingBox.
I think the documentation should be update to be more in line with display: none explanation docs.


Fix homepage to use SSL in doubleTwist Cask

The HTTP URL is already getting redirected to HTTPS. Using the HTTPS URL directly
makes it more secure and saves a HTTP round-trip.

Looks good, thanks! :+1:


New package: BaytesPMCMC v0.1.0

Registering package: BaytesPMCMC
Repository: https://github.com/paschermayr/BaytesPMCMC.jl
Created by: @paschermayr
Version: v0.1.0
Commit: 63dfaedb6ba088f942b60682998c0ecde296edbf
Reviewed by: @paschermayr
Reference: https://github.com/paschermayr/BaytesPMCMC.jl/commit/63dfaedb6ba088f942b60682998c0ecde296edbf#commitcomment-64015059
Description: A library to perform particle MCMC proposal steps for parameter in a ModelWrapper struct, see ModelWrappers.jl.

Dear maintainers of the general registry, could please consider this PR?
The name is fine as MCMC and PMCMC are clearly separeted with different meanings in the Markov Chain Monte Carlo literature. I would like to avoid writing overly long and complicated package names (BaytesParticleMarkovChainMonteCarlo), writing parts full and parts as abbreviation (BaytesParticleMCMC) or start a new MCMC package, as there exist already way too many of those in the Julia registrty.
Thank you for your time and effort!
cc: @DilumAluthge

Sorry for the double post, but is there something else I can do for this package to be merged without automerge?


Minor errors fixed in README.rst

Fixed some minor spelling and grammar errors. Made small modification to some sentences to make them more concise.

great, thank you.


[Event Request] Page 9249 "Analysis by Dimensions Matrix" - OnAfterSetDimBudgetFilters

Request a new event in function SetDimBudgetFilters in page 9249 "Analysis by Dimensions Matrix":
    local procedure SetDimBudgetFilters(var TheAnalysisViewBudgetEntry: Record "Analysis View Budget Entry"; LineOrColumn: Option Line,Column)
    var
        DimCodeBuf: Record "Dimension Code Buffer";
        DimOption: Option "G/L Account",Period,"Business Unit","Dimension 1","Dimension 2","Dimension 3","Dimension 4","Cash Flow Account",CashFlow;
    begin
        ...

        OnAfterSetDimBudgetFilters(TheAnalysisViewBudgetEntry, AnalysisView);     //NEW
    end;

    //NEW
    [IntegrationEvent(false, false)]
    local procedure OnAfterSetDimBudgetFilters(var TheAnalysisViewBudgetEntry: Record "Analysis View Budget Entry"; AnalysisView: Record "Analysis View")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Investigate SKIA images loading issue

Author the user story for this feature
As a developer, I want to understand the SKIA renderer images problem so I can find ways of fixing it.
Is your feature request related to a problem? Please describe.
When running the Metrics application using the SKIA renderer, the images do not load.
Describe the solution you'd like
We should find the reason for images do not load in the SKIA renderer.
Describe alternatives you've considered
No alternatives are considered.
Additional context
No additional context.

We can try a workaround to load images suggested in the linked Flutter issue.


When will the update be released in the Microsoft Store <IP_ADDRESS>?

When will the update be released in the Microsoft Store <IP_ADDRESS>?

@OneIPhy <IP_ADDRESS> is still in pre-release so <IP_ADDRESS> is the latest. I am just working on it when i have the time. Not sure when i will release it.


Attempting to tab-complete a facet before the content types are loaded selects the partial facet name

If you have a Story type, for instance, load a new add well form, focus the search box, then type st<tab>. "ST:" will be your selected facet.

this is just a duplicate of armstrong/armstrong#32


Failing while building wildfly-openssl:1.0.4.Final using mvn clean install (wildfly-openssl:1.0.4.Final)

Package artifact id: wildfly-openssl
source code url: https://github.com/wildfly-security/wildfly-openssl/tree/1.0.4.Final
Issue Description: Failing while building wildfly-openssl:1.0.4.Final using mvn clean install (wildfly-openssl:1.0.4.Final)
JDK Version: 1.8
Build CMD: mvn clean install
MVN Version: 3.9.6
Error Log:
[ERROR] Command execution failed.
java.io.IOException: Cannot run program "nmake" (in directory "C:\code\Code-Latest\wildfly-openssl1.0.4.Final\code\wildfly-openssl\windows-x86_64"): CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start (ProcessBuilder.java:1048)
at java.lang.Runtime.exec (Runtime.java:621)
at org.apache.commons.exec.launcher.Java13CommandLauncher.exec (Java13CommandLauncher.java:61)
at org.apache.commons.exec.DefaultExecutor.launch (DefaultExecutor.java:279)
at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:336)
at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:764)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)
attach
Failed_java_8.txt
ment: build log attached (jdk 1.8)
OS: windows 10

Please update on it.

Hi, the 1.0.x branch is no longer being maintained. Have you tried using a newer version of WildFly OpenSSL (the latest version is 2.2.5.Final)?

Hi, the 1.0.x branch is no longer being maintained. Have you tried using a newer version of WildFly OpenSSL (the latest version is 2.2.5.Final)?

As per our rq., need to build 1.0.4 version only. Please help me on this version.


generate more meaningful UUIDs for report directories

UUIDs in the style of what we have for the chem-bench app might be nice (or what wandb does)

https://github.com/nebbles/hruid-python
https://github.com/orf/human_id
If we do datetime + a name based on the code in ChemBench we should be good to go

see also https://github.com/materialsproject/jobflow/issues/519
also linked to the question if we want to keep the current structure of having one json per question (which leads to massive PRs that are difficult to render)

@n0w0f and @AdrianM0 we discussed this some time ago:

did you reach a consensus/idea and what would be a good model
how would we handle the UUIDs of the existing reports? Keep them? Migrate them? Rerun them (might not be possible for some old models)

could be smth like this?
def unique_id(model_id: str) -> str:
       return model_id + datetime.datetime.now().strftime("%Y%m%d_%H%M")

and those UUIDs are somehow also something that would be good to think about for the question identifiers. At this point, it is always a bit tedious to find the right questions. And, if at some point we would reorder the folders, it would be even harder to find anything.


Dismiss button not accessible from keyboard

I just implemented the cookie consent and tried to click on the dismiss button from the keyboard. Doesn't work. Clicking on the Link works though. How can I change that or could you please fix that?
Thanks a lot and thank you for this nice Plugin.

There is no support in the tool for this at the moment, but you should be able to focus the dismiss button, and then click it with the keyboard by pressing enter when it is focused.
document.querySelector('.cc-dismiss').focus();

You could also add your own keyboard handler. I.E:
cookieconsent.initialise({
  // ... options ...
}, function(popup) {
  var handler = function(event) {
    // if key <enter>
    if (event.keyCode === 13) {
      popup.setStatus(cookieconsent.status.ALLOW);
      popup.close();

      document.removeEventListener('keyup', handler);
    }
  };
  document.addEventListener('keyup', handler)
})

This will accept and close the popup if enter if pressed


How to work on a case where both the paths are unclosed?

Hi, Adam first thank you very much for creating such a wonderful library, I'm trying to find the intersection of 2 unclosed paths but right now I don't think the library supports this...are there any plans for this?

Hi! I'm glad to hear you're enjoying the library :)
the method findIntersectionsWithClosedPath:andBeginsInside: is unfortunately named - it will in fact return intersection points for two unclosed paths. It's on my todo list to make a 2.0 version of this package that would simply clean up the method names and public functions so that it's clearer. Does that method return what you need if you try it on two unclosed paths?


ac-go-live

Docs Build status updates of commit d6826ea:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:warning:Warning

Details

msteams-platform/get-started/get-started-dotnet-app-studio.md
:warning:Warning

Details

msteams-platform/get-started/get-started-nodejs-app-studio.md
:warning:Warning

Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/images/Cards/carousel.png
:white_check_mark:Succeeded

msteams-platform/concepts/Cards/cards-reference.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-configuration.md
:white_check_mark:Succeeded

msteams-platform/includes/get-started/get-started-use-app-studio.md
:white_check_mark:Succeeded

msteams-platform/publishing/apps-publish.md
:white_check_mark:Succeeded

msteams-platform/publishing/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/publishing/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/publishing/office-store-guidance.md
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md

Line 118: [Warning] Link https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-send-and-receive-messages?#start-a-conversation contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.

msteams-platform/get-started/get-started-dotnet-app-studio.md

Line 104: [Warning] Link https://azure.microsoft.com/en-us/free/ contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.

msteams-platform/get-started/get-started-nodejs-app-studio.md

Line 12: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 18: [Warning] Invalid file link:(~/get-started/get-started-tenant).
Line 19: [Warning] Invalid file link:(~/get-started/get-started-configure-teams).
Line 128: [Warning] Invalid file link:(~/get-started/get-started-nodejs-in-azure).
Line 178: [Warning] Invalid file link:(~/get-started/get-started-nodejs-in-azure).
Line 178: [Warning] Invalid file link:(~/get-started/get-started-nodejs-in-azure#configureenvironmentvariables).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


add cmd take-ownership

add cmd implementation of take-ownership

init config store
get existing test report
update task status to In Progress in test report
get subtasks of jira story created by art team
filter out QE subtasks
get owner email from cmd option, if it is not set,  get it from config store
update assignee of QE subtasks
get all advisories
check errata state of the advisory. if it is not QE log a warning message
update qe email of advisories to owner email
update task status to Pass in test report

cmd help
./cli -r 4.12.11 take-ownership -h
Usage: cli take-ownership [OPTIONS]

  Take ownership for advisory and jira subtasks

Options:
  -e, --email TEXT  email address of the owner, if option is not set, will use
                    default owner setting instead
  -h, --help        Show this message and exit.

cmd output
./cli -r 4.12.11 take-ownership
2023-05-17T16:08:45Z: WARNING: email option is not set, will use default setting
2023-05-17T16:08:49Z: INFO: task [Take ownership of advisories] status is changed to [In Progress]
2023-05-17T16:08:52Z: INFO: found subtask ART-6490 - release blocker indicator
2023-05-17T16:08:53Z: INFO: found subtask ART-6491 - [Wed] Prepare the release
2023-05-17T16:08:54Z: INFO: found subtask ART-6492 - [Wed-Fri] QE does release verification
2023-05-17T16:08:54Z: INFO: found subtask ART-6493 - [Wed] Promote the tested nightly to 4-stable in CI and sign
2023-05-17T16:08:55Z: INFO: found subtask ART-6494 - [Thu] Perform weekly CVP content_set_check review
2023-05-17T16:08:56Z: INFO: found subtask ART-6495 - [Post Release Creation] Perform weekly security checks and updates
2023-05-17T16:08:56Z: INFO: found subtask ART-6496 - [Fri/Mon] QE moves advisories to REL_PREP
2023-05-17T16:08:57Z: INFO: found subtask ART-6497 - [Mon] [Once REL_PREP] ART provides non-golang container-first sources and operator-sdk
2023-05-17T16:08:58Z: INFO: found subtask ART-6499 - [Mon-Wed] EXD CLOUDDST pushes advisory content to production CDN
2023-05-17T16:08:59Z: INFO: found subtask ART-6500 - [Mon-Wed] EXD CLOUDDST pushes release content to customer portal
2023-05-17T16:08:59Z: INFO: found subtask ART-6501 - [Mon-Wed] QE notifies ON_QA bugzilla owners and analyze ci failures
2023-05-17T16:09:00Z: INFO: changed assignee of ART-6492 to<EMAIL_ADDRESS>2023-05-17T16:09:04Z: INFO: changed assignee of ART-6496 to<EMAIL_ADDRESS>2023-05-17T16:09:05Z: INFO: changed assignee of ART-6501 to<EMAIL_ADDRESS>2023-05-17T16:10:05Z: WARNING: advisory state is not QE, it is SHIPPED_LIVE
2023-05-17T16:10:17Z: INFO: qe email of advisory 112393 is updated to<EMAIL_ADDRESS>2023-05-17T16:10:17Z: WARNING: advisory state is not QE, it is SHIPPED_LIVE
2023-05-17T16:10:38Z: INFO: qe email of advisory 112392 is updated to<EMAIL_ADDRESS>2023-05-17T16:10:38Z: WARNING: advisory state is not QE, it is SHIPPED_LIVE
2023-05-17T16:10:48Z: INFO: qe email of advisory 112394 is updated to<EMAIL_ADDRESS>2023-05-17T16:10:48Z: WARNING: advisory state is not QE, it is SHIPPED_LIVE
2023-05-17T16:11:01Z: INFO: qe email of advisory 112391 is updated to<EMAIL_ADDRESS>2023-05-17T16:11:01Z: WARNING: advisory state is not QE, it is SHIPPED_LIVE
2023-05-17T16:11:10Z: INFO: qe email of advisory 112395 is updated to<EMAIL_ADDRESS>2023-05-17T16:11:12Z: INFO: task [Take ownership of advisories] status is changed to [Pass]

lgtm

/retitle OCPQE-17512 add cmd take-ownership


fix(List): update styles for Teams Dark and HC themes

Fixes #1056.
Dark theme
Before

After

HC theme
Before

After

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Resolve syncing conflicts from repo_sync_working_branch to master

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to master.

@cxwtool : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Mikejo5000 Could you take a look to make sure the correct moniker year is retained? Select Resolve conflicts and scroll down to the yellow highlighted conflict. The conflict needs to be resolved and this PR merged for repo sync to resume. I think it pertains to https://github.com/MicrosoftDocs/visualstudio-docs/pull/7307, merged yesterday in the public repository. Thanks.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

I'm resolving the conflict in favor of the latest update, for "2019" in https://github.com/MicrosoftDocs/visualstudio-docs-pr/pull/9079 (internal link). This conflicts with the update in https://github.com/MicrosoftDocs/visualstudio-docs/pull/7307, so @Mikejo5000 please check and follow up if needed. I'll merge this PR.


Template cleanup and additional options.

Extract templates into external files.
Fix stalePullRequest script (which mostly worked but was behind a boolean check that always failed.)
Consoliate all repository options into a RepositorySettings object, this also allows for all RepositorySettings options to be specified as part of the configuration.
Update specs

Closes #53
Closes #18

@mramato, thanks for the pull request!
I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.
I am a bot who helps you make Cesium awesome! Thanks again.


Site redesign

I'm thinking of redesigning the site. The current design is fine and simple but can be improve further.
I'm willing to adjust the layout, color scheme, font, and a few other feature for a better readability and navigation. This should not affect the simplicity and comfyness aspect of the site.
I'll update with a quick Figma design later in this issue. And I just want to get an approval first before actually started coding it.

I started to realized that I'm creating a problem that doesn't exist. Here is what I'm aiming for.

Not much has changed.

All fonts will be web-safe
Paragraphs' font should be any sans-serif equivalent
Home page is a little more compact (desktop).
Border is lighter
A little less contrast between background and foreground.
for each of the article pages, they will have the width of about 50vw for desktop view.

I changed the design a little in the latest commit, what do y'all think of it so far?

This is perfect. A little narrower width for the article page would be nice.

I added some fixes in the latest commit. Glad it's looking better!


[binlog] Add new port

Describe the pull request
Add binlog, a high performance C++ log library to produce structured binary logs.

What does your PR fix?
New port.

Which triplets are supported/not supported? Have you updated the CI baseline?
All except UWP and Windows ARM, No

Does your PR follow the maintainer guide?
Hopefully?

Yes

@eddiejames, Thanks for your pr, please get failure logs here. Please ping me if you need any help.

@eddiejames, Thanks for your pr, when I tested the binlog:x64-windows usage, I got a error:
could you please take a look:
1> [CMake] CMake Error at F:/Feature-test/binlog/vcpkg/installed/x64-windows/share/binlog/binlogTargets.cmake:96 (message):
1> [CMake]   The imported target "binlog::bread" references the file
1> [CMake]
1> [CMake]      "F:/Feature-test/binlog/vcpkg/installed/x64-windows/tools/binlog/bread.exe"
1> [CMake]
1> [CMake]   but this file does not exist.  Possible reasons include:
1> [CMake]
1> [CMake]   * The file was deleted, renamed, or moved to another location.
1> [CMake]
1> [CMake]   * An install or uninstall procedure did not complete successfully.
1> [CMake]
1> [CMake]   * The installation package was faulty and contained
1> [CMake]
1> [CMake]      "F:/Feature-test/binlog/vcpkg/installed/x64-windows/share/binlog/binlogTargets.cmake"
1> [CMake]
1> [CMake]   but not all the files it references.

CMakelists.txt:
cmake_minimum_required (VERSION 3.8)

project(test)

find_package(binlog CONFIG REQUIRED)

add_executable (main "CMakeProject42.cpp" "CMakeProject42.h")

target_link_libraries(main PRIVATE binlog::binlog binlog::headers)

CMakeProject42.cpp:
#include "CMakeProject42.h"
#include "binlog/binlog.hpp"

using namespace std;

int main()
{
	cout << "Hello CMake." << endl;
	return 0;
}

hi (binlog author here), thanks for the new port! What's the root cause of the error? Is the bread.exe install path wrong somehow? I'd rather have a fix here, so the vcpkg install is complete, if possible, otherwise the users will have an incomplete distribution, forced to recompile some parts on demand when eventually needed.

Hi, thanks for your quick response. As far as I understand, vcpkg doesn't allow any executables to be packaged, so I had to remove them after the build step in the vcpkg configuration for binlog. @JonLiu1993 is my understanding correct here?

hi (binlog author here), thanks for the new port! What's the root cause of the error? Is the bread.exe install path wrong somehow? I'd rather have a fix here, so the vcpkg install is complete, if possible, otherwise the users will have an incomplete distribution, forced to recompile some parts on demand when eventually needed.

Hi, thanks for your quick response. As far as I understand, vcpkg doesn't allow any executables to be packaged, so I had to remove them after the build step in the vcpkg configuration for binlog. @JonLiu1993 is my understanding correct here?

@eddiejames, Yes, we should remove remove *.exe after the build step in the vcpkg configuration.

Yes, we should remove remove *.exe after the build step in the vcpkg configuration.

No, removal after build is just the last resort to get rid of large binaries. It wastes build time, and it creates problems with exported config, as reported above.
The preferred way is to control the build of executables via a CMake option, which can be mapped to an optional features.
And extra care is needed with the CMake config for tools which must run on the host, not target.

I agree that building something just to remove it afterwards is incorrect. binlog cmake can be changed to optionally avoid building/install binaries.
However: binlog produces binary logfiles, that can be converted to text using bread (bread.exe above). If binaries get removed, what's the proposed use workflow? How is the user going to read the logfiles? Will the user build bread separately? Isn't that a bit unconvenient? Doesn't vcpkg support building/installing tools?

However: binlog produces binary logfiles, that can be converted to text using bread (bread.exe above). If binaries get removed, what's the proposed use workflow? How is the user going to read the logfiles? Will the user build bread separately? Isn't that a bit unconvenient? Doesn't vcpkg support building/installing tools?

The tools can be requested via a port "feature". I hope the log files are portable, so I can use my x64-linux tools to convert arm-android log files, and don't need arm-android bread?

Strictly speaking, they are not portable, however, in practice, they are, as long as the different platforms use the same endianness  and floating point representation. (rationale: https://binlog.org/Mserialize.html#overview)

Draft this PR since it seems that no progress is being made.

The referenced PR that blocked this was merged, please re-open this. Thanks!

Pinging @eddiejames for response. Is work still being done for this PR?

@eddiejames, Please let me know if this PR is ready for review, Thanks.

@eddiejames, Please let me know if this PR is ready for review, Thanks.

Yes it is.

Tetsed usage by binlog:x64-windows triplet successfully:
    # this is heuristically generated, and may not be correct
    find_package(binlog CONFIG REQUIRED)
    target_link_libraries(main PRIVATE binlog::binlog binlog::headers)


Dependabot includes markup in commit messages making logs harder to read.

These commits make git log significantly harder to read. Especially in a repo like the buildroot that gets frequent commits from this bot.
This issue tracks sanitizing the commit messages of dependabot to get rid of markup. Or replace the markup that is more readable in terminal logs, like Markdown.
An example:
commit e31fb200d71d8eff96484d011bde3769f6b59501
Author: dependabot[bot]<EMAIL_ADDRESS>Date:   Mon May 15 09:36:23 2023 +0000

    Bump google/mirror-branch-action from 1.0 to 2.0 (#42037)

    Bumps [google/mirror-branch-action](https://github.com/google/mirror-branch-action) from 1.0 to 2.0.

    Commits

30c52ee Update dependencies.</l
i>

4544d8a Update deprecated actio
n environment

884625c Bump node-fetch from 2.
6.0 to 2.6.1

d9fb13d Bump @â
actions/core from 1.2.4 to 1.2.6

4083f5d Unify placeholders in R
EADME.md

394f8d4 Bump lodash from 4.17.1
5 to 4.17.19 (#3)

5d7016e The sample uses: line should reference <a<EMAIL_ADDRESS>(#1)

See full diff in compare view

    [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=google/mirror-branch-action&package-man
ager=github_actions&previous-version=1.0&new-version=2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#
about-compatibility-scores)

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot
rebase`.

    ---

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:
    - `@dependabot rebase` will rebase this PR
    - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
    - `@dependabot merge` will merge this PR after your CI passes on it
    - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
    - `@dependabot cancel merge` will cancel a previously requested merge and block automerging
    - `@dependabot reopen` will reopen this PR if it is closed
    - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

This might not be actionable from our side. Dependabot may not have configuration to change the commit message output.


[BUG]: Gradle task does not apply sonarQubeGradlePluginVersion

Task name
Gradle
Task version
2.x, AND 3.x
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 20.04
Task log
A problem was found with the configuration of task ':sonarqube' (type 'SonarQubeTask').
  - In plugin 'org.sonarqube' type 'org.sonarqube.gradle.SonarQubeTask' property 'pluginVersion' is private and annotated with @Internal.

    Reason: Annotations on private getters are ignored.

    Possible solutions:
      1. Make the getter public.
      2. Annotate the public version of the getter.

    Please refer to https://docs.gradle.org/7.6.1/userguide/validation_problems.html#private_getter_must_not_be_annotated for more details about this problem.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 18s
##[debug]Exit code 1 received from tool '/home/azureuser/myagent/_work/10/s/gradlew'
##[debug]STDIO streams have closed for tool '/home/azureuser/myagent/_work/10/s/gradlew'
Error: The process '/home/azureuser/myagent/_work/10/s/gradlew' failed with exit code 1
##[debug]taskRunner fail
    at ExecState._setResult (/home/azureuser/myagent/_work/_tasks/Gradle_8d8eebd8-2b94-4c97-85af-839254cc6da4/2.219.0/node_modules/azure-pipelines-task-lib/toolrunner.js:942:25)
    at ExecState.CheckComplete (/home/azureuser/myagent/_work/_tasks/Gradle_8d8eebd8-2b94-4c97-85af-839254cc6da4/2.219.0/node_modules/azure-pipelines-task-lib/toolrunner.js:925:18)
    at ChildProcess.<anonymous> (/home/azureuser/myagent/_work/_tasks/Gradle_8d8eebd8-2b94-4c97-85af-839254cc6da4/2.219.0/node_modules/azure-pipelines-task-lib/toolrunner.js:838:19)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1093:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)

Relevant log output
n/a

Aditional info
# YAML Pipeline
- task: Gradle@2
  inputs:
    gradleWrapperFile: 'gradlew'
    tasks: 'build'
    publishJUnitResults: true
    testResultsFiles: '**/TEST-*.xml'
    javaHomeOption: 'JDKVersion'
    gradleOptions: '-Xmx3072m'
    sonarQubeRunAnalysis: true
    sqGradlePluginVersionChoice: 'specify'
    sonarQubeGradlePluginVersion: '3.3'
    spotBugsAnalysis: false

This problem occurs when sonar.gradle already exists under the task directory.
$ cat myagent/_work/_tasks/Gradle_8d8eebd8-2b94-4c97-85af-839254cc6da4/2.219.0/node_modules/azure-pipelines-tasks-codeanalysis-common/sonar.gradle
allprojects {
    // Apply to the main build script a new repository and a dependency on the SonarQube plugin
    buildscript  {
        repositories {
            maven {
                url "https://plugins.gradle.org/m2/"
            }
        }
        dependencies {
            classpath "org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:2.6.1"
        }
    }

    // After the project has been evaluated (and the dependency above has been added, apply the SonarQube plugin
    afterEvaluate { project ->
        if (project.getParent() == null && !project.plugins.hasPlugin('org.sonarqube')) {
            //Add sonar plugin only to root projects, and only if it is not already applied
            project.apply plugin: 'org.sonarqube'
        }
    }

The expected behavior is that the contents of sonar.gradle will be updated if sonarQubeGradlePluginVersion is specified.
// sonar.gradle
classpath "org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:3.3"
A temporary workaround is to delete the Gradle task directory.
$ rm -rf myagent/_work/_tasks/Gradle_8d8eebd8-2b94-4c97-85af-839254cc6da4/

Hi, @kaito-ms thanks for reporting!
We are working on more prioritized issues at the moment but will get back to this one soon.


Support for <source> sub-element of item

https://www.rssboard.org/rss-specification#ltsourcegtSubelementOfLtitemgt

A source must have a URL element but the W3C Feed  Validation Service does not return an error or warning for missing text within the <source> element.


allow PrivateIdentifier in QualifiedName

Fixes https://github.com/microsoft/TypeScript/pull/47696#discussion_r846981685

This seems like an API change that has to happen thanks to the cast noted in: https://github.com/microsoft/TypeScript/pull/47696#discussion_r846981685

@jakebailey As I understand your last comment, need to do the following list of items

Change the name type from Identifier to MemberName

https://github.com/microsoft/TypeScript/blob/45faac7e70174d3738c9b5e290a76a4ebb67d518/src/compiler/types.ts#L2354-L2358

Add PrivateIdentifier parsing support to parsePropertyAccessEntityNameExpression

https://github.com/microsoft/TypeScript/blob/45faac7e70174d3738c9b5e290a76a4ebb67d518/src/compiler/parser.ts#L8449-L8457

Change parseEntityName  to parsePropertyAccessEntityNameExpression https://github.com/microsoft/TypeScript/blob/45faac7e70174d3738c9b5e290a76a4ebb67d518/src/compiler/parser.ts#L3191

Change exprName: EntityName to expression: PropertyAccessEntityNameExpression and node.exprName = exprName; to node.expression = expression;

https://github.com/microsoft/TypeScript/blob/45faac7e70174d3738c9b5e290a76a4ebb67d518/src/compiler/factory/nodeFactory.ts#L1885-L1891
Am I right?

I think there may have been a miscommunication when I read the notes, because maybe it's PropertyAccessExpression that is the one to be using here, or similar. @rbuckton @andrewbranch

@jakebailey I think we can try to change TypeQuery from entityName to an expression. It will even resolve this issue https://github.com/microsoft/TypeScript/issues/19707.

Maybe; I can see that coming up in #48763.

I think we shouldn’t change the behavior of #19707 at this point post-beta. My suggestion would be (for now) to parse only a dotted name still, and pick whatever legal type for the API makes sense. Expression would let us change #19707 in the future without changing the type again, but I’m not too concerned about widening the type of TypeQuery['exprName'] more in the future if we need to.
(Note: changing PropertyAccessEntityNameExpression might make sense in order to make the narrowest possible type for what we will parse here, but its parsing functions and most of its existing uses are JSDoc-specific. I’m not sure it’s worth it to mess with that.)

I'm looking at this currently, and the trouble I'm seeing is that TypeQuery contains an EntityName, which is recursive with QualifiedName:
    export interface QualifiedName extends Node {
        readonly kind: SyntaxKind.QualifiedName;
        readonly left: EntityName;
        readonly right: Identifier;
        /*@internal*/ jsdocDotPos?: number;                      // QualifiedName occurs in JSDoc-style generic: Id1.Id2.<T>
    }

    export type EntityName = Identifier | QualifiedName;

What was broken about #47696 was that there was a cast to Identifier that hid the fact that while parsing entity names we now could get PrivateIdentifier too and add it to the chain of things in the qualified name.
So if we make TypeQuery have a plain Expresssion rather than an EntityName, that wouldn't change the fact that the new behavior allows PrivateIdentifier in a qualified name, which people in the design meeting didn't seem to like.
I almost think we should revert #47696 (then approach #19707 in a later release), unless you're seeing a more reasonable parser change here than I am. It seems like the options are:

Make qualified name allow a private identifier in the chain (people didn't like this)
Parse out a PropertyAccessExpression instead, which is a chain that allows it and is similar, but that expression could technically be something like this.foo['xyz'].bar which is more than a dotted name.
Parse out EntityNameOrEntityNameExpression by adding private identifiers to PropertyAccessEntityNameExpression, somehow, but as mentioned, that's all JSDoc stuff. But, EntityName/QualifiedName are already also very weird too and aren't really reachable via normal expressions?

I do think making it Expression is the "right" thing long term, at least on my view of the operator being "the type of what you get when you write out this expression".

I almost think we should revert https://github.com/microsoft/TypeScript/pull/47696 (then approach https://github.com/microsoft/TypeScript/issues/19707 in a later release),

Oke, I'll add changes to revert #47696

The plan for what the tree actually looks like will follow directly from what we choose for the API type:

Expression, PropertyAccessExpression, or new type that is recursive PropertyAccessExpression allowing only itself and MemberName: tree looks like a PropertyAccessExpression
New type that looks like QualifiedName but allows MemberName: tree looks like it does now

There’s not so much a problem with the shape of the tree as there is a disagreement between the type and reality.

We decided to revert this; I'll be sending a PR shortly to do it.

I think a better approach would have been to allow #name in an indexed access type, rather than in a type query, i.e.:
class C {
  #x: Foo;
  private _x: Foo;

  method() {
    const p1: this[#x] = this.#x;
    const p2: this["_x"] = this._x;

    const obj = this;
    const p3: typeof obj[#x] = this.#x; // parsed as `(typeof obj)[#x]`
    const p4: typeof obj["_x"] = this._x; // parsed as `(typeof obj)["_x"]`
  }
}

This would mean adding a PrivateNameTypeNode and we could then avoid changing TypeQueryNode or QualifiedName in any way. I would also expect that #x in a type is only legal inside of the class body, just like how a runtime private name is scoped.
If you need to access the type of a private named class member outside of the class, you would need to introduce a type alias or interface for it. If a class makes a private-named index access type public, our declaration emit would also need to synthesize a type for it outside of the class. This means that the type import("foo").Bar[#baz] would only be legal inside of a class body that declares #baz.

@rbuckton can you stick that on #47595? I think Ryan there was arguing against it, so good to note in case we actually do have this feature.


Use opcode from context and OOG in Arithmetic Operations

Time spent on this PR: 0.3
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
All the Arithmetic opcodes use the same internal exec_arithmetic_operation function with an extra opcode
parameter.
What is the new behavior?
The opcode number is taken directly from the ctx and StopAndArithmeticOperations.exec_arithmetic_operation
is consequently directly used in evm.cairo.
OOG during these opcodes is now raised.

how come ef-tests are failing?


Improvement for k8s.io/docs/tutorials/hello-minikube/

To stop the proxy, run Ctrl+C to exit the process. The dashboard remains running.

Nope, when you press Ctrl+C after running minikube dashboard the dashboard stops working.

@cawoodm Thanks for the first issue here!
By saying "when you press Ctrl+C after running minikube dashboard the dashboard stops working", do you mean the web browser cannot access the dashboard page after Ctrl+C?
This is the expected behavior. After the proxy is stopped, the current web browser session stops working. But the dashboard server is still running in the background, you can open another proxy connection to access it again.
I can try to improve the doc if the original sentence confuses new learners.

Hello,
From a user perspective the dashboard is unusable after Ctrl+C and if you start it again it’s on a different port so it looks very mich like it’s stopped. The real question is why starting the dashboard should block the CLI like this. I’d say the behaviour is unnecessarily confusing for beginners and the documentation compounds this.

Let me improve the doc to clarify this.
/triage accepted
/kind feature

/assign


Implement REFT parser module

Allen's tool is a command line utility
add as an integrated parser for 1.0 release?

It will get plenty of use for the ARC01 cruise.

REFT is Reference Temperature?

That's correct.

Sub issue of #111


python311Packages.dateparser: 1.1.8 -> 1.2.0

Description of changes
Diff: https://github.com/scrapinghub/dateparser/compare/refs/tags/v1.1.8...v1.2.0
Changelog: https://github.com/scrapinghub/dateparser/blob/refs/tags/v1.2.0/HISTORY.rst

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 270324 run on x86_64-linux 1

2 packages marked as broken and skipped:

archivebox
archivebox.dist

114 packages built:

aws-sam-cli
aws-sam-cli.dist
csvs-to-sqlite
csvs-to-sqlite.dist
gruut (python311Packages.gruut)
gruut.dist (python311Packages.gruut.dist)
home-assistant-cli
home-assistant-cli.dist
home-assistant-component-tests.gdacs
home-assistant-component-tests.geo_rss_events
home-assistant-component-tests.ign_sismologia
home-assistant-component-tests.qld_bushfire
home-assistant-component-tests.renault
home-assistant-component-tests.unifiprotect
hydrus
hydrus.doc
invoice2data
invoice2data.dist
khoj
khoj.dist
komikku
paperless-ngx
parsedmarc (python311Packages.parsedmarc)
parsedmarc.dist (python311Packages.parsedmarc.dist)
python310Packages.aio-georss-client
python310Packages.aio-georss-client.dist
python310Packages.aio-georss-gdacs
python310Packages.aio-georss-gdacs.dist
python310Packages.asf-search
python310Packages.asf-search.dist
python310Packages.dateparser
python310Packages.dateparser.dist
python310Packages.dsnap
python310Packages.dsnap.dist
python310Packages.flask-common
python310Packages.flask-common.dist
python310Packages.georss-client
python310Packages.georss-client.dist
python310Packages.georss-generic-client
python310Packages.georss-generic-client.dist
python310Packages.georss-ign-sismologia-client
python310Packages.georss-ign-sismologia-client.dist
python310Packages.georss-ingv-centro-nazionale-terremoti-client
python310Packages.georss-ingv-centro-nazionale-terremoti-client.dist
python310Packages.georss-nrcan-earthquakes-client
python310Packages.georss-nrcan-earthquakes-client.dist
python310Packages.georss-qld-bushfire-alert-client
python310Packages.georss-qld-bushfire-alert-client.dist
python310Packages.georss-tfs-incidents-client
python310Packages.georss-tfs-incidents-client.dist
python310Packages.georss-wa-dfes-client
python310Packages.georss-wa-dfes-client.dist
python310Packages.gruut
python310Packages.gruut.dist
python310Packages.maya
python310Packages.maya.dist
python310Packages.parsedmarc
python310Packages.parsedmarc.dist
python310Packages.python-binance
python310Packages.python-binance.dist
python310Packages.pyunifiprotect
python310Packages.pyunifiprotect.dist
python310Packages.renault-api
python310Packages.renault-api.dist
python310Packages.secure
python310Packages.secure.dist
python310Packages.wktutils
python310Packages.wktutils.dist
python311Packages.aio-georss-client
python311Packages.aio-georss-client.dist
python311Packages.aio-georss-gdacs
python311Packages.aio-georss-gdacs.dist
python311Packages.asf-search
python311Packages.asf-search.dist
python311Packages.dateparser
python311Packages.dateparser.dist
python311Packages.dsnap
python311Packages.dsnap.dist
python311Packages.flask-common
python311Packages.flask-common.dist
python311Packages.georss-client
python311Packages.georss-client.dist
python311Packages.georss-generic-client
python311Packages.georss-generic-client.dist
python311Packages.georss-ign-sismologia-client
python311Packages.georss-ign-sismologia-client.dist
python311Packages.georss-ingv-centro-nazionale-terremoti-client
python311Packages.georss-ingv-centro-nazionale-terremoti-client.dist
python311Packages.georss-nrcan-earthquakes-client
python311Packages.georss-nrcan-earthquakes-client.dist
python311Packages.georss-qld-bushfire-alert-client
python311Packages.georss-qld-bushfire-alert-client.dist
python311Packages.georss-tfs-incidents-client
python311Packages.georss-tfs-incidents-client.dist
python311Packages.georss-wa-dfes-client
python311Packages.georss-wa-dfes-client.dist
python311Packages.maya
python311Packages.maya.dist
python311Packages.python-binance
python311Packages.python-binance.dist
python311Packages.pyunifiprotect
python311Packages.pyunifiprotect.dist
python311Packages.renault-api
python311Packages.renault-api.dist
python311Packages.secure
python311Packages.secure.dist
python311Packages.wktutils
python311Packages.wktutils.dist
tts
tts.dist
unifi-protect-backup
unifi-protect-backup.dist
webmacs
webmacs.dist


Release build freeze after update  gradel(com.android.tools.build:gradle) to (4.0.1)

release build freeze after update gradle plugn from 3.6.3  to 4.0.0+
I tried every 4.0.0+ version but no luck
toolsGradle : com.android.tools.build:gradle:4.0.1
**distributionUrl ** = https://services.gradle.org/distributions/gradle-6.4-all.zip
please help me

Sorry that you're having trouble with Gradle!
Your issue lacks information about how to reproduce the problem you're having. A reproducer project can really help us track down and fix your problem quicker.  We may also be able to suggest workarounds or ways to avoid the problem if we can reproduce it.
This issue will be closed after 7 days, unless you can provide more information.

Closed due to lack of feedback.


0.10.4 can't connect to Unifi Protect

Unifi Protect Backup version: 0.10.4
Unifi Protect version: 2.11.21
Python version: 3.10
Operating System: Ubuntu 22.04.4 LTS
Are you using a docker container or native?: Native

Description
After upgrading it can't connect to Protect.
What I Did
2024-02-17 13:56:16 [  WARNING  ] unifi_protect_backup.unifi_protect_backup_core :  Failed to connect to UniFi Protect, retrying in 2s...
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/unifi_protect_backup/unifi_protect_backup_core.py", line 190, in start
    await self._protect.update()
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 673, in update
    self._bootstrap = await self.get_bootstrap()
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 991, in get_bootstrap
    data = await self.api_request_obj("bootstrap")
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 379, in api_request_obj
    data = await self.api_request(
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 358, in api_request
    data = await self.api_request_raw(
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 319, in api_request_raw
    response = await self.request(
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 255, in request
    await self.ensure_authenticated()
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 416, in ensure_authenticated
    await self.authenticate()
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 441, in authenticate
    response = await self.request("post", url=url, json=auth)
  File "/usr/local/lib/python3.10/dist-packages/pyunifiprotect/api.py", line 257, in request
    request_url = self._url.joinpath(url[1:])
AttributeError: 'URL' object has no attribute 'joinpath'

Reverted back to 0.9.5 and have no issues. Let me know if you need any other information.

Hi,
Thanks for reporting this, looks like its an issue with the underlying python library this tool is based on. I will raise an issue with them and report back once its resolved

should be fixed in the latest release


fix the layout of README.md

The layout of the README.md can be improved. Also, using a linter may help fix some of the issues.

It may be a good idea to split the current README.md into 3 parts.

Information about the extension and usage instructions
Tutorial
Developer documentation


feat: jboss port offset configuration

Closes #57

Thanks for the PR! Can you please rebase?

Brilliant, thank you very much for the contribution


Gauge API : Add DoubleGauge Support (Part2)

Codecov Report

Merging #1496 into master will increase coverage by 0.07%.
The diff coverage is 89.28%.

@@             Coverage Diff              @@
##             master    #1496      +/-   ##
============================================
+ Coverage      82.4%   82.48%   +0.07%
- Complexity     1609     1626      +17
============================================
  Files           246      248       +2
  Lines          7566     7650      +84
  Branches        713      723      +10
============================================
+ Hits           6235     6310      +75
- Misses         1113     1120       +7
- Partials        218      220       +2

Impacted Files
Coverage Δ
Complexity Δ

...c/main/java/io/opencensus/metrics/DoubleGauge.java
78.26% <78.26%> (ø)
2 <2> (?)

...o/opencensus/implcore/metrics/DoubleGaugeImpl.java
93.44% <93.44%> (ø)
15 <15> (?)

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 418e675...73b1603. Read the comment docs.


Allow configurable puppeteer chrome locations

I want to be able to use this on Lambda / etc and point to a chrome installed in node_modules/*.  Is there a way to have the puppeteer instance options be configurable instead of magically having a chrome instance found or the user providing the puppeteer browser themselves?

Yes, we can expose complete Puppeteer configurability so that you could do those kind of things, including running against bundled Chromium tip of the tree.
Having said that, I've heard that running headful Chrome on Lambda is challenging, so if you want to run things in the cloud, Headless Chrome driven by Puppeteer is your best bet.

Gotcha, yeah I was looking at this as a fancy wrapper on top of Puppeteer at first and for generating screenshots and allowing screenshots of a file that's located in a specific directory without having to start a server.  But after looking more, it's another way of creating desktop apps, etc :P.


Fingerprint Toyota Corolla Hybrid Jun 2021 model (made in Japan)

Reason for pull request:  Toyota Hybrid Corolla(car.corollah_tss2:)  JUNE 2021 build not currently supported by Comma AI .  To ensure the car is supported in the next release
Export from my Comma Connect
CarFw = [
( ecu = esp,
fwVersion = "F152612D00\000\000\000\000\000\000",
address = 1968,
subAddress = 0 ),

What's your dongle ID?

Reason for pull request: Toyota Hybrid Corolla(car.corollah_tss2:) JUNE 2021 build not currently supported by Comma AI . To ensure the car is supported in the next release
Export from my Comma Connect
CarFw = [
( ecu = esp,
fwVersion = "F152612D00\000\000\000\000\000\000",
address = 1968,
subAddress = 0 ),

What's your dongle ID?
4a444eab146265fe

Hi, My dongle ID is: 4a444eab146265fe


Improve cross-endpoint request retries

[x] I have viewed signed and have submitted the Contributor License Agreement

[x] I have made this pull request to the main branch

[x] I have run all the unit tests using scripts/run-unit-tests-in-docker from routing-release.

[ ] (Optional) I have run Routing Acceptance Tests and Routing Smoke Tests on bosh lite

[ ] (Optional) I have run CF Acceptance Tests on bosh lite

This PR updates gorouter behaviour so that existing retry logic to the same endpoint for idempotent requests is also attempted accross endpoints, for the case when the server fails to provide an HTTP response.
The Go standard library default HTTP transport retries requests on encountering certain errors where the request qualifies as being idempotent. Specifically:
// Transport only retries a request upon encountering a network error
// if the request is idempotent and either has no body or has its
// Request.GetBody defined. HTTP requests are considered idempotent if
// they have HTTP methods GET, HEAD, OPTIONS, or TRACE; or if their
// Header map contains an "Idempotency-Key" or "X-Idempotency-Key"
// entry. If the idempotency key value is a zero-length slice, the
// request is treated as idempotent but the header is not sent on the
// wire.

This was implemented in 2013 and updated in 2018 to add support for idempotency key headers.
Errors which allow retries to take place are an HTTP2 cached connections issue and the following two errors:
if _, ok := err.(transportReadFromServerError); ok {
  // We got some non-EOF net.Conn.Read failure reading
  // the 1st response byte from the server.
  return true
}
if err == errServerClosedIdle {
  // The server replied with io.EOF while we were trying to
  // read the response. Probably an unfortunately keep-alive
  // timeout, just as the client was writing a request.
  return true
}

Retrying when the above two errors occur runs the risk of mutating non-idempotent requests causing bad things to happen (eg duplicate charges), which is why the go standard library only attempts to make these requests when the request meet the idempotency criteria. The current Gorouter ProxyRoundTripper delegates backend requests to the dropsondeRoundTripper which itself delegates requests to the standard library default transport. By virtue of delegating to transport.go's RoundTrip method the Gorouter already retries and accepts the risk of retrying potentially mutating non-idempotent requests, when those requests meet the idempotency criteria required by http.Request.isReplayable(). As this risk is already accepted and acted on by the Gorouter this PR updates behaviour so that:

empty server response errors (ie io.EOF errors) for qualifying requests are retried
retries happen across endpoints

At least one scenario where extending idempotent request retry logic to other endpoints would help improve the stability of Cloud Foundry is when route integrity is enabled and the Envoy sidecar is listening but the application is not yet listening, either because it is being started or has crashed or some other reason. In this situation the following happens:

The gorouter successfully establishes a TCP connection to the Envoy TCP Proxy
Envoy cannot proxy the request so does not respond*
The gorouter proxy round tripper gets an io.EOF error from the standard library HTTP transport and returns it to the user as an endpoint_failure-type 502 error.

I was unable to find an implementation I was completely happy but I went with this: I've added a check in ProxyRoundTripper#RoundTrip to replace io.EOF with a new error type in cases where the request matches the idempotency criteria. This error is then checked by a new classifier added to the RetriableClassifiers  group. This avoids having to refactor the Classifier interface to add an http.Request argument, which would have needed a lot of refactoring to handle other areas in the code where classifier is called, such as when pruning endpoints. If you have suggestions for better implementations, please share!
I implemented the unit tests as a table-based test in order to mirror the tests in the standard library's transport_test.go, but with some more cases as there were are a few code paths missing coverage in the standard library tests.
~This PR is not yet mergeable because I'm still waiting for some CLA-related admin, which will take about a week, but I'm publishing now to hopefully start a discussion about this change.~
cheers,
Pete
*After a successful three-way TCP handshake between the gorouter and Envoy, the gorouter sends the HTTP request data. Envoy does not respond so the gorouter closes the TCP connection after about half a second.

[ ]  I have viewed signed and have submitted the Contributor License Agreement
[x]  I have made this pull request to the main branch
[x]  I have run all the unit tests using scripts/run-unit-tests-in-docker from routing-release.
[ ]  (Optional) I have run Routing Acceptance Tests and Routing Smoke Tests on bosh lite
[ ]  (Optional) I have run CF Acceptance Tests on bosh lite

This PR updates gorouter behaviour so that existing retry logic to the same endpoint for idempotent requests is also attempted accross endpoints.
The Go standard library default HTTP transport retries requests on encountering network errors where the request qualifies as being idempotent. Specifically:
// Transport only retries a request upon encountering a network error
// if the request is idempotent and either has no body or has its
// Request.GetBody defined. HTTP requests are considered idempotent if
// they have HTTP methods GET, HEAD, OPTIONS, or TRACE; or if their
// Header map contains an "Idempotency-Key" or "X-Idempotency-Key"
// entry. If the idempotency key value is a zero-length slice, the
// request is treated as idempotent but the header is not sent on the
// wire.

This was implemented in 2013 and updated in 2018 to add support for idempotency key headers.
The current gorouter ProxyRoundTripper delegates backend requests to the dropsondeRoundTripper which itself delegates requests to the standard library default transport. Therefore requests to a given backend are currently retried using this logic when those requests meet the idempotency criteria. On retrying, if the second request also fails with a network error, that error is escalated to the ProxyRoundTripper as an io.EOF error. Although the gorouter does attempt to retry many classes of errors against different endpoints, it does not attempt to retry these kind of network failure requests.
At least one scenario where extending idempotent request retry logic to other endpoints would help improve the stability of Cloud Foundry is when route integrity is enabled and the Envoy sidecar is listening but the application is not yet listening, either because it is being started or has crashed or some other reason. In this situation the following happens:

The gorouter successfully establishes a TCP connection to the Envoy TCP Proxy
Envoy cannot proxy the request so does not respond*
If the request met the idempotency criteria it is attempted again against the same endpoint and fails for the same reason
The gorouter proxy round tripper gets an io.EOF error from the standard library HTTP transport and returns it to the user as an endpoint_failure-type 502 error.

This PR adds a step between steps 3 and 4 which retries qualifying requests against other endpoints.
I was unable to find an implementation I was completely happy with so I'm presenting the 'least-worst' implementation I could think of: I've added a check in ProxyRoundTripper#RoundTrip to replace io.EOF with a new error type in cases where the request matches the idempotency criteria. This error is then checked by a new classifier added to the RetriableClassifiers group. This avoids having to refactor the Classifier interface to add an http.Request argument, which would have needed a lot of refactoring to handle other areas in the code where classifier is called, such as when pruning endpoints. If you have suggestions for better implementations, please share!
I implemented the unit tests as a table-based test in order to mirror the tests in the standard library's transport_test.go, but with some more cases as there were are a few code paths missing coverage in the standard library tests.
kind regards,
Pete

Hi @peterellisjones ,
Thank you for submitting this PR! I had never heard of the Idempotency-Key before, very cool. Just glancing over the code, it all makes sense to me.
I'll add this to our team's backlog for a more thorough review.

Hi @peterellisjones,
Thank you for taking the time to write all this out and submit a PR. Thanks for the unit tests as well, they're great.
Reproducing
The only thing that I'm struggling with is how to test this functionality on an environment.
❓ Do you have steps to manually exercise this functionality? Can you please share them if you do?
Thanks,
@jrussett

Hi @jrussett here's how I tested the changes:
Setup
Start nats server
nats-server

Start Gorouter
cd routing-release/src/code.cloudfoundry.org/gorouter
GOPATH=~/workspace/routing-release GO111MODULE=auto go run main.go

Register test apps at  <IP_ADDRESS>:9000 and <IP_ADDRESS>:9001
watch -n 10 'nats-pub "router.register" "{ \"host\": \"<IP_ADDRESS>\", \"port\": 9000, \"uris\": [ \"test-app.internal\" ], \"app_guid\": \"abc123\" }"'

watch -n 10 'nats-pub "router.register" "{ \"host\": \"<IP_ADDRESS>\", \"port\": 9001, \"uris\": [ \"test-app.internal\" ], \"app_guid\": \"abc123\" }"'

I then deployed a simple test app to listening on port 9001 -- this would be the "good" app that I would expect the gorouter to retry requests against when requests fail against a "bad" app running on port 9000
package main

import (
	"fmt"
	"log"
	"net/http"
	"os"
)

var port = os.Getenv("PORT")
var logger = log.New(os.Stdout, "", 0)

func main() {
	logger.SetFlags(log.Lmicroseconds)

	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		logger.Println("Handling request")
		fmt.Fprintln(w, "OK")
	})

	logger.Printf("Listening on port %s\n", port)
	log.Fatal(http.ListenAndServe(fmt.Sprintf(":%s", port), nil))
}

Scenario 1: App not listening - no change in behaviour expected
When the first app (port 9000) is not running, I verified that all requests are sent to the second app (port 9001), and that no requests fail (the gorouter logs also confirmed this)
➜ curl  -X GET <IP_ADDRESS>:8081 -H "Host: test-app.internal"
OK

This is existing behaviour of the Gorouter, due to dial errors being retried.
Scenario 2: App fails before sending first byte - retries now expected
I then updated the first app (port 9000) to crash before sending the first byte:
package main

import (
	"fmt"
	"log"
	"net/http"
	"os"
)

var port = os.Getenv("PORT")
var logger = log.New(os.Stdout, "", 0)

func main() {
	logger.SetFlags(log.Lmicroseconds)

	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		panic("Crash before sending first byte")
	})

	logger.Printf("Listening on port %s\n", port)
	log.Fatal(http.ListenAndServe(fmt.Sprintf(":%s", port), nil))
}

In this scenario when the current version of the gorouter is running and a request is sent to the first app, the customer gets a 502 bad gateway error from the gorouter
curl  -X GET <IP_ADDRESS>:8081 -H "Host: test-app.internal"
502 Bad Gateway: Registered endpoint failed to handle the request.

and the gorouter logs show the EOF error
{"log_level":3,"timestamp":1622018215.1270452,"message":"backend-endpoint-failed","source":"gorouter.stdout","data":{"route-endpoint":{"ApplicationId":"","Addr":"<IP_ADDRESS>:9000","Tags":null,"RouteServiceUrl":""},"error":"EOF","attempt":1,"vcap_request_id":"964d44ac-03fd-4b2a-4b5f-694a3c6e5bfa"}}
2021/05/26 09:36:55 http: proxy error: EOF

I then confirmed that with the gorouter running my changes qualifying requests are always retried against other endpoints and never fail:
➜ curl  -X GET <IP_ADDRESS>:8081 -H "Host: test-app.internal"
OK

However due to the idempotency criteria, a request that is not a body-less GET/OPTIONS/TRACE/HEAD or does not have X-idempotency-key or idempotency-key headers, still fails with the original behaviour:
➜ curl  -X PUT <IP_ADDRESS>:8081 -H "Host: test-app.internal" -d '{}'
502 Bad Gateway: Registered endpoint failed to handle the request.

Scenario 3: App fails after sending first byte - no change in behaviour expected
The current golang behaviour for http.Transport is that qualifying requests are not retried if connections fail after sending the first byte and I wanted to make sure my changes matched this to keep the scope of changes conservative. Therefore to make sure that I wasn't accidentally introducing retries for these requests I created an app that fails after sending a partial response:
package main

import (
	"fmt"
	"log"
	"net/http"
	"os"
)

var port = os.Getenv("PORT")
var logger = log.New(os.Stdout, "", 0)

func main() {
	logger.SetFlags(log.Lmicroseconds)

	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		w.Write([]byte("OK"))
		if f, ok := w.(http.Flusher); ok {
			f.Flush() // Force write response bytes
		}
		panic("Crashing mid-response")
	})

	logger.Printf("Listening on port %s\n", port)
	log.Fatal(http.ListenAndServe(fmt.Sprintf(":%s", port), nil))
}

I then confirmed that in these situations the existing behaviour remains, which is that the transfer is closed mid-stream and is not retried
➜ curl  -X PUT <IP_ADDRESS>:8081 -H "Host: test-app.internal" -d '{}'
curl: (18) transfer closed with outstanding read data remaining
OK%

In this situation the gorouter logs the following, and no retries are attempted.
2021/05/26 09:53:42 httputil: ReverseProxy read error during body copy: unexpected EOF

Scenario 4: Envoy listening but app is not - retries now expected
From the perspective of the gorouter this scenario is identical to scenario 2. To verify this I ssh'd into a running Cloud Foundry app to copy an envoy.yaml configuration. I then removed any config I was confident was not relevant, and updated it to listen on port 9000 (replacing the first app), and to proxy traffic to a non-existent app listening on port 7000:
static_resources:
  clusters:
    - circuit_breakers:
        thresholds:
          - max_connections:<PHONE_NUMBER>
      connect_timeout: 0.250s

      load_assignment:
        cluster_name: 0-service-cluster
        endpoints:
          - lb_endpoints:
              - endpoint:
                  address:
                    socket_address:
                      address: <IP_ADDRESS> # IP of my laptop
                      port_value: 7000

      name: 0-service-cluster
      type: STATIC
  listeners:
    - address:
        socket_address:
          address: <IP_ADDRESS>
          port_value: 9000
      filter_chains:
        - filters:
            - name: envoy.tcp_proxy
              typed_config:
                "@type": type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy
                cluster: 0-service-cluster
                stat_prefix: 0-stats
                access_log:
                  - name: envoy.access_loggers.stdout
                    typed_config:
                      "@type": type.googleapis.com/envoy.extensions.access_loggers.stream.v3.StdoutAccessLog
      name: listener-9000

I then started Envoy locally with the following Dockerfile
FROM envoyproxy/envoy-dev:19210537c7169ed7c8560cdaf16f9b3590db3215
COPY envoy.yaml /etc/envoy/envoy.yaml
RUN chmod go+r /etc/envoy/envoy.yaml

And ran it with
docker build -t local-envoy .
docker run -it -p 9000:9000 -v $(pwd)/logs:/var/log -e ENVOY_UID=777 local-envoy

This gave me the following setup:

Envoy listening on port 9000 and forwarding traffic to port 7000
Nothing listening on port 7000 (simulating an app that is not listening because it is restarting or has crashed)
A healthy app listening on port 9001
The gorouter configured to send traffic to a single app listening on ports 9000 and 9001

Without the change what happens in this situation is identical to scenario 1: The gorouter gets an empty response from Envoy, the roundtrip call fails with an io.EOF error, and the gorouter sends the customer a 502 bad gateway response.
With the change the failed request to Envoy is successfully retried against the healthy app.
@jrussett, @ameowlia I hope this is useful -- please let me know if you'd like any more details
cheers,
Pete

Update: my CLA issues are all resolved (I'm doing this work on behalf of SAP)

🎉  Thank you @peterellisjones for this PR and for the clear acceptance steps! 🎉


How to post data for authentication from ASP.Net MVC to IdentityServer4 login controller.

I Have an ASP.Net MVC application with Owin configuration and IdentityServer4.
How to post data for authentication from ASP.Net MVC application to IdentityServer4 login controller.

This seems to be a general question about IdentityServer - not a bug report or an issue.
Please use one of the our free or commercial support options
See here for more details.
Thanks!


display of transcript variants in GO annotation

On the website, it might be nicer to display these as trm1.1 or trm1.2
so it is clear that there are not the normal sys ID

That's implemented now.  I'll check the main site on Wednesday morning then close the issue.


Output images are very similar

Based on Google and Azure score output images are 95-97% equal to the original. Which means that most of face recognition services will consider them as the same one.
So what am i doing or understanding wrong?

Thanks for the question. Please checkout my answer to a similar question.


Correcting PSModulesPath to PSModulePath

Per the powershell documentation, this variable should be PSModulePath, not PSModulesPath

@pargall : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@SnehaGunda: I'm sorry - only the author of this article, @markjbrown, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Thanks for catching/correcting.
#sign-off


👷♂ Fix Typos & Add codespell CI Action

Description
I fix the typo "psuedorandom" (and further typos like "Novermber" or "choosen") and add the codespell GitHub Action to check automatically for typos in the future.
Checklist
Ensure you completed all of the steps below before submitting your pull request:

[x] Ran forge fmt?
[x] Ran forge snapshot?
[x] Ran forge test?

Wow, this is incredible! Tysm!


⚠ Samsung has degraded performance

In 409cc37, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2870 ms

Resolved: Samsung performance has improved in 110bc09.


Satchel can be put inside itself

Describe the bug
i was using the occultism satchel and accidentally put it inside itself.
To Reproduce
Steps to reproduce the behavior:

open occultism satchel
place satchel inside itself
See error

Expected behavior
i expected the satchel to not be able to be moved when open or inable to go inside it's inventory
Screenshots
it happened so fast i couldn't capture it
System (please complete the following information):

Occultism Version: unsure
OS: Windows
Minecraft Version: 1.16
Modpack Link and Version, or list of mods: Enigmatica 6

@Toonlink264 thank you for your report!
May I ask you too look in your mod folder what the file name of occultism is to find the version?
This is a known bug that was fixed recently so I'd like to verify if it is on the buggy version or if we need to look into it again.
Thank you!

@Toonlink264 thank you for your report!
May I ask you too look in your mod folder what the file name of occultism is to find the version?
This is a known bug that was fixed recently so I'd like to verify if it is on the buggy version or if we need to look into it again.
Thank you!

Closed until we can get a repro.

Closed until we can get a repro.

whoops i completely forgot about this. I'm on 1.0.9

@Toonlink264 Can you try if you can reproduce this on the latest occultism version (1.0.12)?
I could not reproduce it so far and want to verify if it is fixed or if I'm not doing it right :)
Thank you!


update TG based on direct email from Kanton Thurgau Staatskanzlei

merged version of  #263

Should I solve the merge conflict?

@zukunft I have resolved the merge conflict. Let's see if we can get this data into master.

@tlorusso Please merge if you agree.

The data has not been published on the web, I just got an email.

Merci


Add feature to export APIs as DAT-Files

User story
For some use cases it can be useful to export existing APIs in a bulk operation as a DAT file. Therefore, the CLI should support DAT in addition to CSV, JSON, Console export formats.
For this it should offer the same filter options.

To export one or multiple APIs the command is:
apim api get -s api-env -o dat -t C:\temp\irweuroiw -deleteTarget -n "Order*"


Azure CNI & Accelerated Networking/Azure Route tables

I'm wondering if Azure CNI is compatible with Accelerated Networking.
I've deployed a cluster several time with both accelerated networking enabled and disabled on the agent VMSS and each time Accelerated Networking was enabled I ended up having problem with the network.
The observed problem was the impossibility to contact a pod hosted on one node from a second pod hosted on a second node.
Today I've been able to reproduced the problem with Accelerated Networking disabled.
After deploying a brand new cluster we forgot to add the agent subnet to the cluster Azure Route table and the cluster started to behave like if Accelerated Networking was enabled.
As soon as we added the agent subnet to the cluster route table everything started working normally.
So I'm wondering if enabling Accelerated Networking leads to bypass Azure Route tables.
Regards

@sylr Are you sure you are using Azure CNI? It does not require a route table to work. You can confirm if azure cni was used to setup PODs by looking at the log files on the agent nodes @ /var/log/azure-vnet*

Hi, @sharmasushant
Very interesting question, I'm not at work anymore so I can't answer you clearly.
What I know is that I've some Azure CNI components installed on my nodes (it's part of the acs-engine deployment) but I can't be certain it is used.
What I know it that I use the networkPolicy None in my acs-engine deployment so maybe @jackfrancis could tell us if I use it in such cluster.

If you used latest or recent acs-engine, then you should be using Azure cni, and you should not require route table setup for communication to work. What version of acs-engine you used?

@sylr Any update? Please share acs-engine version? And the Azure CNI logs from /var/log/azure-vnet* so that we can validate Azure CNI version as well.

Like I said I use networkPolicy None and after some research it means it uses Kubenet so I'm not using CNI even if it has been installed on the nodes:
root@k8s4-euw-dev-agent-vmss-000000:~# ll /opt/cni/bin
total 49016
drwxr-xr-x 2 root root     4096 Apr 12 09:22 ./
drwxr-xr-x 3 root root     4096 Jul 31 09:38 ../
-rwxr-xr-x 1 root root  4028260 Apr 12 09:21 bridge*
-rwxr-xr-x 1 root root 10232415 Apr 12 09:22 dhcp*
-rwxr-xr-x 1 root root  2856252 Apr 12 09:21 flannel*
-rwxr-xr-x 1 root root  3127363 Apr 12 09:21 host-device*
-rwxr-xr-x 1 root root  3036768 Apr 12 09:22 host-local*
-rwxr-xr-x 1 root root  3572685 Apr 12 09:21 ipvlan*
-rwxr-xr-x 1 root root  3084347 Apr 12 09:21 loopback*
-rwxr-xr-x 1 root root  3613497 Apr 12 09:21 macvlan*
-rwxr-xr-x 1 root root  3550877 Apr 12 09:21 portmap*
-rwxr-xr-x 1 root root  3993428 Apr 12 09:21 ptp*
-rwxr-xr-x 1 root root  2641877 Apr 12 09:22 sample*
-rwxr-xr-x 1 root root  2850029 Apr 12 09:21 tuning*
-rwxr-xr-x 1 root root  3568537 Apr 12 09:21 vlan*

So I guess my problem is not related to Azure CNI after all.
Sorry to have bothered you.


Getting module not found error on versions after 0.7.4

Can you provide a demo with a reproduction?

Hi, I actually was struggling with a similar issue today. I think is just an issue with older create-react-app projects, which has trouble interpreting the exports field as seen here.
This issue is can be resolved by adding:
"main": "./dist/index.js",
"module": "./dist/index.mjs",

back to package.json. These were removed in #136.
It would be great if these fields could be added back to support older apps.

@emilkowalski any updates on this?

Same issue here.

This issue is can be resolved by adding:
"main": "./dist/index.js",
"module": "./dist/index.mjs",

back to package.json. These were removed in #136.
It would be great if these fields could be added back to support older apps.

I second that. Found the same issue in a vite app today.
Otherwise eslint is reporting:
error  Unable to resolve path to module 'sonner'  import/no-unresolved

Import from dist import { Toaster } from 'sonner/dist'; was a solution for me.

As a fix import it like this
import { Toaster } from 'sonner/dist';

Same issue, and importing from 'sonner/dist' doesn't work either.

Same issue here.

Any updates?


[Feature request] Add config subcommand

Is your feature request related to a problem? Please describe.
It can be difficult to debug some issues since it isn't clear what config is being used. There have been times, like here: https://github.com/tinted-theming/tinty/issues/19, where someone was editing a config but that config wasn't being used by tinty.
Describe the solution you'd like
Add a subcommand to return the config file and/or the path to config/data dirs.

chezmoi has a cat-config sub command which might also be an option https://www.chezmoi.io/reference/commands/cat-config/
Unrelated (similar) is the cd command, which could be useful to switch into the data directory: https://www.chezmoi.io/reference/commands/cd/


32-bit instead of 64-bit

Hi! I used ReLinker for my project to increase robust of library loading, but I faced strange crashes when I try to load my native library on 6 platform (I can not reproduce on any of my phones, it is from crashlytics)
Fatal Exception: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/<apppackage>/app_lib/libmylib.so" is 32-bit instead of 64-bit
       at java.lang.Runtime.load(Runtime.java:332)
       at java.lang.System.load(System.java:1069)
       at com.getkeepsafe.relinker.ReLinker.loadLibrary(ReLinker.java:75)

It looks strange cuz I have only armeabi-v7a and x86 libraries in my project and appropriate abi-filter setting in gradle. Do you have any idea?

That means you're mixing 64 bit binaries and 32 bit binaries. You can only ship either all 32 bit binaries or all 64 bit binaries. This is not an issue with ReLinker.
Check your dependencies and what type of binary they're using (this is a common problem when using fresco, for example).

I am sure, that I shipped only 32-bit binaries in project. If I have mixing 64/32 binaries format the I have app crash on any devices, but there is not. It happens only for some devices and only on android 6
https://yadi.sk/i/XqzqcOFt3GAEib


support consumption from Power BI with updated schema creation

@tsikiksr : Thanks for your contribution! The author, @jpe316, has been notified to review your proposed change.

Hi @tsikiksr - since you're a Microsoft PM, you should be working in the private repository. @jpe316, we'd prefer to close this PR and have @tsikiksr  submit these changes to the private repo (azure-docs-pr ) ? that way we can use the staging and validation tools there to check. This contains more content that we can comfortably review in the public repo.
Here's some information:

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.

After you review staging and fix all validation issues, you can tag an author for review or add the sign-off comment to let PR reviewers know that the updates are ready to be merged.

Read about authors working in the public repo for more information.

If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.

Thanks.
#please-close


Update README.md to add a bin for examples

Took a look at the examples section and just moved it all to a bin for anyone's reference.

Coverage remained the same at 87.742% when pulling aa5f0eb03b8d6aa08299b2a682a08fc6758c1ba3 on mrwillis:patch-1 into 5bdf775e2873fcbe5e32af91ce5aa60a6d64dd0f on hyojin:master.


"+ Add New Vessel" should not appear in the "Find records" search

"+ Add New Vessel" should only appear in pre-boarding search, not the "find records" search.

@Sheeri it was added in #198
Should we remove it from Find Records?

Correct, please remove it from Find Records but keep it in the search when "Board Vessel" is clicked.


⚠ Node - us-a6008253.yalaso.top has degraded performance

In ca9fdaa, Node - us-a6008253.yalaso.top (http://us-a6008253.yalaso.top/api/v1/ping) experienced degraded performance:

HTTP code: 200
Response time: 3240 ms

Resolved: Node - us-a6008253.yalaso.top performance has improved in 88153ce.


Error Code: M7031-1105

I have followed the latest guide for Digital Ocean and it seems to work as I can see the  US content however when I try to play anything it gives me an error about internet connection issues.
This is on chrome, I am using tunnel broker and the latest guide to attempt this.

Just tested on Vultr, works fine. Carefully check all your settings and re-build.


Tagemoua patch1

Add internationalization by adding the possibility to enter the form in 3 languages and having the frontend displayed on the 3 languages

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 56.768%

Files with Coverage Reduction
New Missed Lines
%

services/dkg/pedersen/handler.go
3
87.21%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
3271

Relevant Lines:
5762

💛  - Coveralls

I don't understand what causes these errors ?

You should start by removing everything you put at the root of the repo, i.e the /node-modules/* and a couple of other files.


Fix some of the bugs created by changing the text size at a OS level

Summary
Address some of the issues when the text is set to a different size at OS level. Not addressed anything regarding size of display (different setting at least in Android).
Ticket Link
https://mattermost.atlassian.net/browse/MM-44709
Screenshots
Before:

After:

Release Note
NONE

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/23006
https://circleci.com/gh/mattermost/mattermost-mobile/23005

Artifact links:
https://output.circle-artifacts.com/output/job/eebcf100-a7a5-4a05-9d57-9a37102a0da5/artifacts/0/tmp/artifacts/Mattermost_Beta.apk
https://output.circle-artifacts.com/output/job/2e77a051-6316-41e2-a28a-e0f4d592e0d0/artifacts/0/tmp/artifacts/Mattermost_Beta.ipa

There are definitely a number of issues introduced with this:
I'll start with the home screen for now, but I think this is going to require a lot of review time to identify all the issues that might be affected by this.
* The team sidebar icons scale up - I think we can keep those a fixed size

I thought keeping them at fixed size make things cluttered, since the letters and the badge numbers grow / shrink. But I can revert the scalling of the icons themselves.

* The unread dot becomes an oval shape and is positioned incorrectly (probably because the team icons are scaling up)

Yes, I may have missed something with the scalling of that.

* 'unreads' filter button next to the 'Find Channels' input is smaller than the height of the find channels input

Missed it in my local :sweat_smile:

* The 'Threads' icon doesn't scale the same way as the channel icons and avatars do

Missed it in my local : sweat_smile:

* Not all changes seems to happen immediately when playing around with the OS text size options. Sometimes I have to close the app and restart it for changes to apply. The channel icons and avatars, for example, seem to stay the same size un

This is not hard to solve, but requires a bit more of work. The problem is that right now there is nothing listening to changes in the ratio changes, but even if nothing is listening, the text changes sizes...
So we would have to create a hook that, for example, when the app comes into view, checks again the ratio, and propagates the change. That would create some artifact of everything that have to change size moving into place just after you open the app.
Whether it makes sense to do this in this PR or not, 0/5. I will give it a quick try when I start fixing all these issues.

* Are we able to increase the spacing between items when scaling up the items? It gets quite tight
  ![IMG_9411](https://user-images.githubusercontent.com/2040554/171904145-3e12790f-186e-4d21-a7b8-db6c2f7141e6.PNG)

If I am not mistaken, should not be much of a problem. We just need to adjust a few values. But this will be the kind of changes you will need to restart the app to properly see the changes until we have the hook I was talking about.

Also noticed this in the servers bottom sheet:
* the button label 'Add a server' gets cut off

Didn't check the bottom sheet yet, but I can give it a look.

This PR can be considered a POC. Further work will need to be done to properly define what are exactly the changes we want to make, and the different parts of the ui that will need to be updated.


Integrals not compatible with ForwardDiff (Turing)

When running an integral from numbers propagated from Turing using ForwardDiff, I get the following error:
StackOverflowError:

Stacktrace:
 [1] cachedrule(#unused#::Type{ForwardDiff.Dual{ForwardDiff.Tag{Turing.TuringTag, Float64}, Float64, 9}}, n::Int64) (repeats 79984 times)
   @ QuadGK ~/.julia/packages/QuadGK/buWps/src/gausskronrod.jl:253

Is this module not compatible with Turing?

It's ForwardDiff compatible. What did you run? It would be good to have an MWE of what you're trying to differentiate.
FWIW, here's what's tested with autodiff: https://github.com/SciML/Integrals.jl/blob/master/test/derivative_tests.jl
If we can learn what case we missed then we can fix it.

I'm not sure how to create a MWE of my code because I'm not sure how much of it will still work after I strip out the non-pertinent sections. But I'll try.
The code that errors is
function dNdr(r, p)
    Mass, zmin, zmax = p[1], p[2], p[3]
    α = 0.133
    β = -1.995
    γ = 0.263
    η = 0.0993
    A = 0.0104
    r̄ = 0.00972
    zfac = ((1+zmax)^(η+1) - (1+zmin)^(η+1))/(1+η)
    Nm = A * (Mass*1e-12)^α * r^β * exp((r/r̄)^γ) * zfac
    return Nm
end

function intdNdr(Mass, zmin, zmax, rmin, rmax)
    prob = IntegraleProblem(dNdr,rmin,rmax, [Mass, zmin, zmax])
    sol = solve(prob, QuadGKJL(), reltol=1e-4)
    return sol
end

function MdNdr(r, p)
    Mass, zmin, zmax = p[1], p[2], p[3]
    α = 0.133
    β = -1.995
    γ = 0.263
    η = 0.0993
    A = 0.0104
    r̄ = 0.00972
    zfac = ((1+zmax)^(η+1) - (1+zmin)^(η+1))/(1+η)
    Mz = A * Mass * (Mass*1e-12)^α * r^(β+1) * exp((r/r̄)^γ) * zfac
    return Mz
end

function intMdNdr(Mass, zmin, zmax, rmin, rmax)
    prob = IntegralProblem(MdNdr,rmin,rmax, [Mass, zmin, zmax])
    sol = solve(prob, QuadGKJL(), reltol=1e-4)
    return sol
end

From Turing, the parameter which needs to be differentiated is a 9-dimensional vector parameters.
These are passed into my custom code which is basically a forward propagator where some quantity x[i+1] depends on x[I]. η is created by a function of a few of the elements of the vector parameters. Mass an iterative quantity like this, and each element is the sum of the previous element with some function wrapping the integral intdNdr. Something like
function find dM(Mass, zmin, zmax, rmin, rmax)
    zmin and zmax come from another propagated value
    rmin depends on Mass[begin]
    rmax is a constant
    dM = do continuous math (intMdNdr(Mass, zmin, zmax, rmin, rmax))

and Mass[I+1] = Mass[i]+ dM(Mass, zmin, zmax, rmin, rmax)
I've been told that perhaps its easier to make a custom rule to implement the fundamental theorem of calculus, but I don't quite see how that applies.
Thanks

This was a downstream issue fixed by https://github.com/JuliaMath/QuadGK.jl/pull/61


App blank when using Tauri 1.0.2

I'm using this plugin in https://github.com/Uninen/tauri-vue-template but for some reason it doesn't play well with the latest Tauri. Not sure where the problem actually is, but both Tauri and the Vue front both run fine, they just doesn't boot together when running vite-tauri dev; all I get is a blank screen.
I'm using the latest version of vite-plugin-tauri but also teted with two older versions, both of which don't work either w/ the latest Tauri.

I'm pretty sure it was just a configuration issue. I'm closing this now as it isn't relevant for me anymore (and is probably invalid in any case). Sorry for the noise!


Disable allow_reuse_address (SO_REUSEADDR) on Windows

Fix #10578: az login hangs when more than one instances of az login are launched at the same time on Windows or WSL
The root cause is that HTTPServer can't detect port is in-use on Windows.
To repro, launch az login but do not continue in the browser. Then run az login from another terminal and continue with the login. One of the az instance will get stuck.
This PR disables HTTPServer.allow_reuse_address so that the correct routine is resumed.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

Try to test CI, will close and re-open

I can't cancel my approval now, which can be done before the permission change. Please don't merge before a real approval.

I think we don't need to support multiple az login at same time since we don't support multiple accounts. We can let all other az login fail if there is an az login running. az login should not interleave.
And if we support multiple az login, add write locks to token files. I've seen broken accessTokens.json because of concurrent write. The content is interleaving.

/azp run

https://github.com/Azure/azure-cli/issues/26180

@welersonlisboa, this issue is not relevant to https://github.com/Azure/azure-cli/issues/26180.