Install script for a .esd file.

What should I fix in the bat file to make installation possible with a compressed esd file? Do I need to use "/export-image" command and convert it to wim first?

Correct me if I wrong (I've copied just installation section):
`::
:: Installation Section
::
echo [i] Converting an Copying Recovery Image...
md R:\RecoveryImage
cd X:\Windows\System32
dism /export-image /SourceImageFile:G:\sources\install.esd /SourceIndex:1 /DestinationImageFile:R:\RecoveryImage\install.wim /Compress:recovery
echo [i] Deploying Windows Image...
dism /Apply-Image /ImageFile:R:\RecoveryImage\install.wim /Index:1 /ApplyDir:W:\
echo [i] Copying Recovery Tools...
md T:\Recovery\WindowsRE
copy W:\Windows\System32\Recovery\winre.wim T:\Recovery\WindowsRE\winre.wim
echo [i] Writing Boot Configuration Data...
bcdboot W:\Windows /s S: /f UEFI
echo [i] Setting up Recovery Environment...
W:\Windows\System32\reagentc /setosimage /path R:\RecoverImage /target W:\Windows /index 1
W:\Windows\System32\reagentc /setreimage /path T:\Recovery\WindowsRE /target W:\Windows
echo Installation done.`

When you run dism to export the image to R:\RecoveryImage\, you specify the parameter /Compress:recovery, which requires a destination image file that ends with .esd.
You can read about it in the DISM Image Management Command-Line Options.
So I suggest you to use this:
echo [i] Exporting Recovery Image...
md R:\RecoveryImage
cd X:\Windows\System32
dism /export-image /SourceImageFile:G:\sources\install.esd /SourceIndex:1 /DestinationImageFile:R:\RecoveryImage\install.esd /Compress:recovery

And of course, you also have to update the Deploy subsection to use the install.esd file:
echo [i] Deploying Windows Image...
dism /Apply-Image /ImageFile:R:\RecoveryImage\install.esd /Index:1 /ApplyDir:W:\

I cannot test this right now though. Give it a try.

Installation was completed and windows have been installed successfully, and it's working fine. Although I am not sure about recovery tools, because it gave me error messages about some "agent".

I will close this issue then. If the recovery tools do not work feel free to open another issue.


Update README.md

Adding some useful Tech Community links to the README file.
Proposed changes

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have signed the CLA (in all commits with git commit -s)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

Is this meant to be shown in Cumulocity or only on GitHub?


Scaling Image to fit the screen

Image is not showing at full width of the WebView, it has blank space all around (like if you open a little iamge in your desktop browser). Any solution ?

First, you should check whether the blank space is actually outside of the WebView or inside of it. You could do this by loading a website with colored background and see if there’s also blank space around the site.
If it’s outside, adjust your layout to specify correct layout widths, heights, margins and paddings. Additionally, you may try
myWebview.setScrollBarStyle(View.SCROLLBARS_OUTSIDE_OVERLAY);

to make sure the scroll bar is not causing the blank space.
If it’s inside, the following two methods (with proper values) might be the only thing you can do:
myWebView.setInitialScale(50);
// or
myWebView.zoomBy(50.0f);


[1.12] Bump Mesos to nightly 1.7.x d0186a2

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/3e185f14075b827b8ea3b03a48ed2cd136ce8158...d0186a2cef8da2ba2af54185eee691b8a94cb305

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot override-status teamcity/dcos/test/azure/arm https://jira.mesosphere.com/browse/DCOS-43260

@mesosphere-mergebot merge-it


Update ClusterLocalModel to LocalModelCache

What this PR does / why we need it:
This PR rename the local model custom resource from ClusterLocalModel to LocalModelCache to align with the vision of adding companion resource ModelCache for remote model cache using high speed storage.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Type of changes
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

This is just a renaming, right?

Correct

/rerun-all

/lgtm


Multi-project mode for GitHub Action

[ ] add input to enable multi project mode if array of directories/config provided
[ ] run collect for each project and produce individual artifacts (code-pushup-report-<project-name>)
[ ] run compare for each project and merge diffs into single markdown body (using implementation from code-pushup/cli#731)

I did some research and concluded that the GitHub Action will have to know about specific monorepo tool conventions, otherwise the configuration burden on the user would be huge, and action inputs don't have support for complex data structures.
I've distinguished the following monorepo scenarios to get started (JS -focused):

Nx, Turborepo - cacheable, will use the monorepo input
PNPM, Yarn, NPM - concept of packages/workspaces, will use the workspace input
no tooling - just folders with individual configs, fallback for non-JS codebases, will use the projects input

Nx
- uses: code-pushup/github-action@v0
  with:
    monorepo: nx

List projects using npx nx show projects --with-target=code-pushup --json.
Get individual project config using npx nx show project <name> --json.
Execute Code PushUp commands with npx nx code-pushup <name> -- for cached executions.

Important: Target executor must forward both commands and arguments to the underlying code-pushup binary (breaks assumptions of current @code-pushup/nx-plugin:autorun executor).

TBD: If code-pushup target isn't used (i.e. they're not using our Nx plugin), then we could still fall back on search for code-pushup.config.{ts,mjs,js} and running those using the binary (uncached).

Turborepo
- uses: code-pushup/github-action@v0
  with:
    monorepo: turbo

Determine workspace type using packageManager field in package.json.
Check for code-pushup command in turbo.json.

If present, use npx turbo run code-pushup -F <name> -- for cached executions.
Otherwise, behave as if workspace: pnpm|npm|yarn|bun was set.

Use package manager to list projects.

PNPM workspace
- uses: code-pushup/github-action@v0
  with:
    workspace: pnpm

List projects using packages glob in pnpm-workspace.yaml.
Determine project name from name in each package's package.json.
Run Code PushUp commands using pnpm -F <name> code-pushup (script > binary).

Yarn workspace
- uses: code-pushup/github-action@v0
  with:
    workspace: yarn

List projects using workspaces glob in root package.json.
Determine project name from name in each package's package.json.
Run Code PushUp commands using yarn workspace <name> code-pushup (script > binary).

NPM workspace
- uses: code-pushup/github-action@v0
  with:
    workspace: npm

List projects using workspaces glob in root package.json.
Determine project name from name in each package's package.json.
Run Code PushUp commands using npm -w <name> run code-pushup -- (script) or npm -w <name> exec code-pushup -- (binary).

no tooling
- uses: code-pushup/github-action@v0
  with:
    projects: frontend,backend

Folders explicitly listed, separated by commas, each may contain globs.
Determine project name from name in package.json if available, otherwise fallback on folder/path.
Run Code PushUp in each project directory using npx --no-install code-pushup.

Implementation notes
The idea is that although we support many different types of monorepo setups, the projects configurations can be parsed and normalized in a separate layer. Once converted, the main flow of the GitHub Action will run on a single generic projects interface.
type ProjectConfig = {
  /** display name */
  name: string;
  /** command to execute code-pushup on given project */
  bin: string;
  /** working directory for running command (default is root) */
  directory?: string;
}

// normalized Nx projects
[{ name: 'utils', bin: 'npx nx code-pushup utils --' }, ...]
// normalized PNPM packages in workspace
[{ name: '@repo/utils', bin: 'pnpm -F @repo/utils code-pushup' }, ...]
// normalized folders from "no tooling" scenario
[{ name: 'frontend', bin: 'npx --no-install code-pushup', directory: 'frontend' }, ...]

Auto-detection of monorepo tool
It's feasible that we can auto-detect which monorepo tool is being used without a user specifying it:

Nx: check for nx.json
Turborepo: check for turbo.json
PNPM workspace: check for pnpm-workspace.yaml
Yarn workspace: check for yarn.lock and "workspaces" in package.json
NPM workspace: check for package-lock.json and "workspaces" in package.json

Then the input could be a simple boolean (monorepo: true). But we'd likely still need a structured input for the no tooling scenario, unless we try to infer projects by recursively searching for code-pushup.config file locations.
However, I don't think we can reliably detect if the GitHub Action should run in monorepo mode or not. E.g. some Nx repos use an "all in one" approach, so detecting Nx shouldn't automatically activate monorepo mode.


Enables the CI build to work for polly.

The bintray artifacts have been created.
The github service has been added to the repo.
core/core.go had to be renamed to core/polly.go to satisfy the build env.
Some artifacts that have been stubbed out have been created: example /test and /polly/cli these are only stubs enough to make the CI build work

Yea, since I enabled the CI build for the repo... a build is going to take place but that isnt obviously going to work since I am checking in the files that the CI builds needs.

Pooo..... looks like I need some help with this. The reason why this CI build fails is because the command "git describe --long --dirty" fails to grab a version number from the last annotated tag. I created one (0.0.1) that enabled it to work in my private repo, but it didnt seem to work in this repo. This is cause the filename and the RPM builds to fail.

Thanks for the fix @clintonskitson

Squash that pig!

LGTM!


LAMHDI SO review ticket #5: ‘genome’

The current definition of genome reads: “a sequence collection that is the sum of genetic material within a cell or virion”
We propose small change to: “a sequence collection that represents the sequence of the sum genetic material within a cell or virion”.
As a side note, it would be nice to clarify what the final logical relationship is between SO classes (as information content entities?) and their corresponding physical/molecular sequences. For example, the relation between an SO:genome and a material genome (ie the sum genetic material of a cell), or an SO:gene and a physical/molecular gene. A Bada and Eilbeck 2011 paper proposes the relation ‘denotes’, a child of ‘is_about’, but we have reservations here . . . perhaps we can discuss on future call or separate tracker item.

Response from @keilbeck to Matthew Brush
Hi Matt
Since we got the travel grant to work with you on these issues, I am making all the lamdi requests 'pending'
--K


Have issue to render Ukrainian characters

the problem occurs with characters 'і' та 'ї' as seen below
https://twitter.com/aceCourtBot/status/1481934051216924673?t=gqHf24qh73mOczcGmvs0CA&s=09

Related common issue: https://github.com/LuisMayo/objection_engine/issues/53


Fixes 'bug' where users are not warned about transparent pixels

Adds a check to the onChangedCurrentColor and if it's the transparent pixel we display a warning to the user, else remove the warning.

We got it handled on the dev branch already, thanks for the heads up.


Possible to create more than one token with different API Keys?

Issue
I have to create two tokens:

One that I will use (our API Key)
One that our partner will use (Partner API Key)

I'd like the user only to input their information once. Is it possible to create two tokens using different API Keys? Have you came across this use case before? And if so; what's the most common solution to the problem?

We would recommend using Stripe Elements to tokenize the card information once, and then using backend Stripe APIs to extend access to that card to other accounts. Please feel free to reach out to Stripe Support if you need help with the details!

Thanks for the swift reponse @asolove-stripe.


[Fix] Replaced nonexistent status() method by getStatusCode()

Fixed issue in assertRedirect method.

status does exists just only on Illuminate\Http\Response.


2 worker log rotation only rotates 1 worker's log file

Is this a bug, feature request, or feedback?
Bug
What is the current behavior?
Intermittent integration test failure
What is the expected behavior?
Test always passes
What OS and version of Wallaroo are you using?
Ubuntu Xenial 16.04.6 LTS, Wallaroo master branch at commit f748f92efe3d3ee08dc9a454ce6dd66d6a9c56fe
Steps to reproduce?
while [ 1 ]; do make integration-tests-testing-conformance-all debug=true resilience=on PONYCFLAGS="--verbose=1"; if [ $? -ne 0 ]; then echo STOP; exit 1; fi; done
See log files at http://wallaroolabs-dev.s3.amazonaws.com/logs/test-artifacts.a.20190708.tar.gz
If I massage the initializer and worker1 logs to add INIT and WRK1 fields to their logs, then also ignore GlobalConnectorStreamRegistry and ConnectorSource,Sending acks lines, then here's the timeline.  Log rotation takes place on worker1 but not on initializer.  The test harness never progresses to the later steps of the test case because the expectation that the log rotation step would complete promptly was false.
Note also that the initializer does not initiate new checkpoints after checkpoint #3 had finished and the log rotation started.
1562375768.721872,INIT,|~~ INIT PHASE IV: Cluster is ready to work! ~~|
1562375768.721904,INIT,Sent control message to worker1
1562375768.721911,INIT,initializer reported topology ready!
1562375768.721916,INIT,All 2 workers reporting Topology ready!
1562375768.721954,INIT,Application has successfully initialized.
1562375768.722111,WRK1,|~~ INIT PHASE IV: Cluster is ready to work! ~~|
1562375769.021142,INIT,ExternalChannelConnectNotifier (initializer): server closed
1562375769.032358,WRK1,ExternalChannelConnectNotifier (worker1): server closed
1562375769.046096,INIT,ExternalChannelConnectNotifier (initializer): server closed
1562375769.176012,INIT,INFO,ConnectorSource,Detector source: accepted a connection 0x7f7657e55000
1562375769.723003,INIT,Sent control message to worker1
1562375769.723042,INIT,Initiating barrier protocol for CheckpointBarrierToken(1).
1562375769.723081,INIT,Sent control message to worker1
1562375769.725715,INIT,Checkpoint_Initiator: Event Log CheckpointId 1 complete for worker initializer
1562375769.725754,WRK1,Sent control message to initializer
1562375769.725771,WRK1,Sent control message to initializer
1562375769.725902,INIT,Checkpoint_Initiator: Event Log CheckpointId 1 complete for worker worker1
1562375769.725928,INIT,Checkpoint_Initiator: Checkpoint Barrier CheckpointBarrierToken(1) Complete
1562375769.726023,INIT,Sent control message to worker1
1562375769.726191,WRK1,Sent control message to initializer
1562375769.726946,INIT,Sent control message to worker1
1562375770.742000,INIT,Sent control message to worker1
1562375770.742020,INIT,Initiating barrier protocol for CheckpointBarrierToken(2).
1562375770.747770,INIT,Sent control message to worker1
1562375770.793775,WRK1,Sent control message to initializer
1562375770.793789,WRK1,Sent control message to initializer
1562375770.797057,INIT,Checkpoint_Initiator: Event Log CheckpointId 2 complete for worker worker1
1562375770.803078,INIT,Checkpoint_Initiator: Event Log CheckpointId 2 complete for worker initializer
1562375770.816201,INIT,Checkpoint_Initiator: Checkpoint Barrier CheckpointBarrierToken(2) Complete
1562375770.823021,INIT,Sent control message to worker1
1562375770.834917,WRK1,Sent control message to initializer
1562375770.846263,INIT,Sent control message to worker1
1562375771.864440,INIT,Sent control message to worker1
1562375771.864470,INIT,Initiating barrier protocol for CheckpointBarrierToken(3).
1562375771.877879,INIT,Sent control message to worker1
1562375771.964803,WRK1,Sent control message to initializer
1562375771.964818,WRK1,Sent control message to initializer
1562375771.977032,INIT,Checkpoint_Initiator: Event Log CheckpointId 3 complete for worker worker1
1562375771.990213,INIT,Checkpoint_Initiator: Event Log CheckpointId 3 complete for worker initializer
1562375772.038154,INIT,Checkpoint_Initiator: Checkpoint Barrier CheckpointBarrierToken(3) Complete
1562375772.054010,INIT,Sent control message to worker1
1562375772.085572,WRK1,Sent control message to initializer
1562375772.115868,INIT,Sent control message to worker1
1562375772.211507,INIT,ExternalChannelConnectNotifier (initializer): server closed
1562375772.231450,WRK1,ExternalChannelConnectNotifier (worker1): server closed
1562375772.231470,WRK1,Starting event log rotation.
1562375772.231510,WRK1,Sent control message to initializer
1562375772.242760,INIT,Starting event log rotation.
1562375772.245348,INIT,Initiating barrier protocol for LogRotationBarrierToken(worker1->1).
1562375772.245428,INIT,Initiating barrier protocol for LogRotationBarrierToken(initializer->1).
1562375772.258559,INIT,Sent control message to worker1
1562375772.258578,INIT,Sent control message to worker1
1562375772.384603,WRK1,Sent control message to initializer
1562375772.444582,INIT,Sent control message to worker1
1562375772.467723,WRK1,EventLog: Rotating log file.
1562375772.467861,WRK1,EMERGENCY,none,START of rotation: finished writing to /tmp/res-data.wzd07f_t/Multi Partition Detector-worker1-0000000000000000.evlog
1562375772.468755,WRK1,EMERGENCY,none,FileBackend: create: filepath = /tmp/res-data.wzd07f_t/Multi Partition Detector-worker1-0000000000007D89.evlog
1562375772.469244,WRK1,EMERGENCY,none,END of rotation: starting writing to /tmp/res-data.wzd07f_t/Multi Partition Detector-worker1-0000000000007D89.evlog
1562375772.469766,WRK1,EventLog: Rotating log file complete.
1562375772.470939,WRK1,SimpleJournalNoop: dispose_journal
1562375772.471060,WRK1,Sent control message to initializer
1562375773.127091,INIT,Sent control message to worker1
1562375802.192390,INIT,INFO,TCPSink,TCPSink connection closed

This is a bad sequence: the LogRotationResumeBarrierToken doesn't appear in this bad case, but ForwardedInjectBarrierFullyAckedMsg does:
1562619174.718816,INIT,Checkpoint_Initiator: Event Log CheckpointId 3 complete for worker initializer
1562619174.848105,INIT,YO: ExternalMsgDecoder._RotateLog
1562619174.848110,INIT,Received ExternalRotateLogFilesMsg on External Channel
1562619174.861099,WRK1,YO: ExternalMsgDecoder._RotateLog
1562619174.861104,WRK1,Received ExternalRotateLogFilesMsg on External Channel
1562619174.861116,WRK1,Starting event log rotation.
1562619174.861133,WRK1,YO: create ChannelMsg: ForwardInjectBlockingBarrierMsg
1562619174.868901,INIT,Starting event log rotation.
1562619174.873522,INIT,Initiating barrier protocol for LogRotationBarrierToken(worker1->1).
1562619174.873560,INIT,Initiating barrier protocol for LogRotationBarrierToken(initializer->1).
1562619174.969267,INIT,YO: create ChannelMsg: ForwardedInjectBarrierFullyAckedMsg
1562619174.998492,WRK1,EventLog: Rotating log file.
1562619174.998553,WRK1,EMERGENCY,none,START of rotation: finished writing to /tmp/res-data.wgukmh_8/Multi Partition Detector-worker1-0000000000000000.evlog
1562619174.999201,WRK1,EMERGENCY,none,FileBackend: create: filepath = /tmp/res-data.wgukmh_8/Multi Partition Detector-worker1-0000000000007D89.evlog
1562619174.999315,WRK1,EMERGENCY,none,END of rotation: starting writing to /tmp/res-data.wgukmh_8/Multi Partition Detector-worker1-0000000000007D89.evlog
1562619174.999761,WRK1,EventLog: Rotating log file complete.
1562619174.999798,WRK1,YO: create ChannelMsg: ForwardInjectBarrierMsg
1562619204.838838,WRK1,...Removing /tmp/res-data.wgukmh_8/Multi Partition Detector-worker1.evlog...

This is a good sequence:
1562620243.429599,INIT,Checkpoint_Initiator: Event Log CheckpointId 3 complete for worker initializer
1562620243.779193,INIT,YO: ExternalMsgDecoder._RotateLog
1562620243.779198,INIT,Received ExternalRotateLogFilesMsg on External Channel
1562620243.785590,INIT,Starting event log rotation.
1562620243.788272,INIT,Initiating barrier protocol for LogRotationBarrierToken(initializer->1).
1562620243.801342,WRK1,YO: ExternalMsgDecoder._RotateLog
1562620243.801347,WRK1,Received ExternalRotateLogFilesMsg on External Channel
1562620243.806350,WRK1,Starting event log rotation.
1562620243.809208,WRK1,YO: create ChannelMsg: ForwardInjectBlockingBarrierMsg
1562620243.818256,INIT,Initiating barrier protocol for LogRotationBarrierToken(worker1->1).
1562620243.835769,INIT,EventLog: Rotating log file.
1562620243.835828,INIT,EMERGENCY,none,START of rotation: finished writing to /tmp/res-data.s8g9wk2n/multi_partition_nitializer-0000000000000000.evlog
1562620243.836992,INIT,EMERGENCY,none,FileBackend: create: filepath = /tmp/res-data.s8g9wk2n/multi_partition_detector-initializer-0000000000007E5D.evlog
1562620243.837078,INIT,EMERGENCY,none,END of rotation: starting writing to /tmp/res-data.s8g9wk2n/multi_partition_detector-initializer-0000000000007E5D.evlog
1562620243.837353,INIT,EventLog: Rotating log file complete.
1562620243.860118,INIT,YO: create ChannelMsg: ForwardedInjectBarrierFullyAckedMsg
1562620243.870269,WRK1,EventLog: Rotating log file.
1562620243.870325,WRK1,EMERGENCY,none,START of rotation: finished writing to /tmp/res-data.s8g9wk2n/multi_partition_detector-worker1-0000000000000000.evlog
1562620243.871209,WRK1,EMERGENCY,none,FileBackend: create: filepath = /tmp/res-data.s8g9wk2n/multi_partition_detector-worker1-0000000000006ACD.evlog
1562620243.871354,WRK1,EMERGENCY,none,END of rotation: starting writing to /tmp/res-data.s8g9wk2n/multi_partition_detector-worker1-0000000000006ACD.evlog
1562620243.871980,WRK1,EventLog: Rotating log file complete.
1562620243.872535,WRK1,YO: create ChannelMsg: ForwardInjectBarrierMsg
1562620243.875750,INIT,Initiating barrier protocol for LogRotationResumeBarrierToken(worker1->1).
1562620243.909724,INIT,YO: create ChannelMsg: ForwardedInjectBarrierFullyAckedMsg
1562620244.520454,INIT,Checkpoint_Initiator: Event Log CheckpointId 4 complete for worker initializer

This patch "eliminates" the test failures, until the bug can be found & fixed.
diff --git a/testing/tools/integration/cluster.py b/testing/tools/integration/cluster.py
index 174043c72..479db7ae1 100644
--- a/testing/tools/integration/cluster.py
+++ b/testing/tools/integration/cluster.py
@@ -631,6 +631,7 @@ class Cluster(object):
         # send a log rotate command directly to each worker's external channel
         for w in to_rotate:
             send_rotate_command(w.external, w.name)
+            time.sleep(2.0)

         # Wait for log rotation watcher to return
         wflr.join()

@slfritchie should this be closed now?

No, this ticket should remain open.  PR #2960 didn't fix the underlying problem.


no oauth.json is created

I have following code, but there is no oauth.json generated after login:
uploader = YoutubeUploader('****************************content.com','*********************************03')
uploader.authenticate()
Everytime I run my script, the web browser opens for authentication.
I do not run uploader.close()

Same problem


channel: Use TypeScript unions for AjaxRequestHandler.

CZO discussion thread
Reason for 2nd Commit:
Since the type of request_method(AjaxRequestHandler) has
been extended in the previous commit.Consequently the 'data'
field of 'request_method' has to be typed such that it
satisfies this change.
Because request_method's type can also be 'typeof patch' which
does not accept undefined 'data' field, I haved 'omit'-ted
'undefined' from 'data's type in function signature to satisfy
TypeScript.
Now ,in support of the changes I have made to two different function
sign(namely setting_ui.do_settings_change & dialog_widget.submit_api_request)
I am stating some points about data field inside these respective
function signs.
1.settings_ui.do_settings_change: For this 'data' was actually never
undefined. Each function call has a 'data' object passed( with one
or more fields).
2.dialog_widget.submit_api_request: For this case many function calls actually didn't have
'data' field (ie.'data' was undefined). BUT,for those cases it was defaulted
to '{}'(see function sign).
    export function submit_api_request(
    request_method: AjaxRequestHandler,
    url: string,
    data: Parameters<AjaxRequestHandler>[0]["data"] = {},

So effectively 'request_method' didn't recieve
an undefined 'data' for this case too. I have removed the defaulting
and passed '{}' in the function calls for those cases, which effectively
does the some job.But satisfies the type.
For both these cases 'data' field isn't undefined and hence Omit makes
sense IMO.

Since the 'request_method' is now a union of 'typeof call' and 'typeof patch', 'data' field cannot be undefined.

Can you explain what you mean by "data" cannot be undefined? I feel like the more precise language would really help here; I don't think this is a concrete issue, just a type-checking issue, but it's very ambiguous in the commit message for the second commit.

Updated the commit messages to be more discriptive & addressed #29263(comment).

OK, this seems fine, merged, thanks @LaPulgaaa!
I think there may be a better world where we have separate functions for the different HTTP methods, but it seems like a bit of a bother to do that refactor.


Suggestions for improving real-time performance?

My particular use case requires me to have access to the transcription of a fully uttered sentence as quickly as possible, as it is being uttered.
Are there any optimizations I can make to how I use faster-whisper that will benefit this?
Currently I'm detecting the speech and once it is finished, I give the whole thing to faster_wisper to transcribe. This is problematic because if it's a long sentence, I have to wait until the end to begin processing the beginning. Is there some reasonable way I can feed the beginning into faster_whisper before the rest of the sentence is done, without sacrificing accuracy?
Since my understanding of the model is limited, I'm unsure if I'm missing something more obvious to improve this, like I don't know if the model even technically needs the whole thing to begin processing or if it could do the work as it comes in, in a way that just isn't done normally since it's not a concern if you're loading data at the rate it can be read, rather than the rate it is spoken.
Would love any input on this.

u can inspire from various repo shared in openai/whisper#2

You do not necessarily need to wait for a sentence to finish to start transcribing. You could also start with a shorter sequence and then when more is available send more afterwards. Obviously the accuracy will get higher as time goes on and the sentence becomes more complete, but even before you can get good results (at least while using the largest model).


Improve CORS middleware

Codecov Report

Merging #13 (f174242) into master (8d41b9d) will increase coverage by 2.62%.
The diff coverage is 97.46%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage   72.25%   74.87%   +2.62%
==========================================
  Files          22       22
  Lines         555      621      +66
==========================================
+ Hits          401      465      +64
- Misses         95       96       +1
- Partials       59       60       +1

Impacted Files
Coverage Δ

internal/app/api/net/http/middleware/cors.go
97.43% <97.33%> (-2.57%)
:arrow_down:

internal/app/api/config/config.go
90.27% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add logic to re-try chooseBest() (which will select best forwarder)

changes differentiate beteween fatal errors (for e.g. ipsec init)
from transient errors (heartbeast misses). In case of transient
errors OverlayForwarder is marked to be unhealty. When overlay forwarder
is unhealty its kept on hold so chooseBest() will skip selecting the forwarder
Once OverlayForwarder is considered healthy run chooseBest() again so the
forwarder can be selected if its the best forwarder
Fixes #1737

Some of the users tried private image for this patch (see #1737) but unfortunately issue did not occur to verify the patch works. I have tested the patch by injecting the heartbeat misses. Please review the changes and if the retry approach is fine.

Addressed review comments PTAL

I tried this out: my principal tool to turn off fastdp was:
sudo iptables -D INPUT -p udp --dport 6784 -j DROP
sudo iptables -D OUTPUT -p udp --dport 6784 -j DROP

I tried various combinations and all seemed fine.  Thanks!


Execution order support

Hello!
Could you use last allure version with order execution support - https://github.com/allure-framework/allure2/releases/tag/2.3.4?
Thanks.

Done. Thank you for the reminder!

Thanks!
v2.3.4 doesn't work correctly :( I'm going to create new issue.


small refactoring

:white_check_mark: Build karma 2457 completed (commit https://github.com/karma-runner/karma/commit/d4d3804759 by @anthony-redFox)

:white_check_mark: Build karma 2471 completed (commit https://github.com/karma-runner/karma/commit/070f600af8 by @anthony-redFox)

@johnjbarton cc

Really sorry for the delay.
We've switched to commitlint and semantic release.  That means merged commits will drive the release (yay). But the commits need to be describe in a formatted way.
Can you rebase and repush? That will force you through the commitlint.  I guess yours would be something like
chore(server): Convert PromiseContainer to object and remove initializeMimeTypes.

:white_check_mark: Build karma 2487 completed (commit https://github.com/karma-runner/karma/commit/917c8212b6 by @anthony-redFox)

@johnjbarton  done

:white_check_mark: Build karma 2488 completed (commit https://github.com/karma-runner/karma/commit/1e40ad5d95 by @anthony-redFox)


failed install still installs plugget package

got this error.
WARNING:root:Failed to install addon mesh-fairing, a py module with same name exists
WARNING:root:skipping addon install 'mesh-fairing', clashing py-module already imported

but plugget still installed the package, showing it as installed

tried to install https://github.com/hannesdelbeke/unreal-plugin-python-script-editor
failed install pyside2 (and we already had pyside6 installed)
requirements failed, but plugget package install was success

leads to impression it was success


Use Citeproc for citation styles

We could use something like citeproc-java to support a lot of citation styles without a lot more work!

During testing I found that this will lead to a vast performance loss when building the document. We need to introduce some kind of caching for already built stuff (when the literature source file *.tdr) has not changed.

TODO

[ ] New attribute the the info file: bibliography where the value is a bibliography file (supporting BibTex, EndNote and RIS (supported by citeproc-java)).
[ ] Loading bibliography file (from info file) for citeproc-java using a new generic citation style class (CSLCitationStyle maybe?).
[ ] Using the new CSLCitationStyle class for citations and generating bibliography leveraging citeproc-java

Estimated to be done by 18th of September

Example
Info file:
encoding = UTF-8
language = en

bibliography.file = refs.bib
bibliography.style = apa

Bibtex file (refs.bib)
@INPROCEEDINGS{Shor,
    author = {P. W. {Shor}},
    booktitle = {Proceedings 35th Annual Symposium on Foundations of Computer Science},
    title = {Algorithms for quantum computation: discrete logarithms and factoring},
    year = {1994},
    pages = {124-134} }

Thaw document text file (*.tdt)
Lorem ipsum dolor sit amet, consetetur sadipscing elitr,
sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat,
sed diam voluptua #CITE, 'Shor, locator=page 124'#.

#REFERENCES#

Result (Screenshot)


Faq Component Added

The faq component is added with 8 question which could be modified

If possible remove conflicts

I have resolved the issues please recheck


Enable InternalsVisibleTo Test Projects

One thing that I noticed while ramping up on MDS was that the MDS projects don't have InternalsVisibleTo assembly attributes to expose internal classes/methods/fields to the test projects. Although in an ideal world, we wouldn't expose the internal objects, but if we want to be able to have very thorough code coverage via granular unit tests, without making internal interfaces public, we will need this attribute enabled. As far as I can tell, this is generally accepted standard practice. However, I'd be curious to see the discussion on this.
At a minimum, I'd recommend:

Adding InternalsVisibleTo attributes to these projects:

netcore/Microsoft.Data.SqlClient
netfx/Microsoft.Data.SqlClient

Make the internals visible to these projects:

Microsoft.Data.SqlClient.ManualTesting.Tests
Microsoft.Data.SqlClient.Tests

Please let me know your thoughts!

I think it makes sense to Add InternalsVisibleTo, for this project.
There will always be parts of this project, which will require unit testing, and will never be a part of the public surface area of the Library.
I looked at few other libraries which follow a similar technique for unit testing/benchmarking of internals etc.
NpgSql being one of them https://github.com/search?q=repo%3Anpgsql%2Fnpgsql InternalsVisibleTo&type=code
Historical context: When this library was part of .Net Runtime repo as SDS, the guidance was to stay away from internals visible to in favor of making our APIs/public surface area written in a way that it is unittestable.
However I dont see that as a practical way of unit testing SqlClient, because there is no reason for the internals to ever be exposed  as a public API, e.g. Parser/StateObject etc.
I vote for making this change, but the internals visible to, should only make the internals visible to, our test projects, not everything.

Also, developers may start exposing more internal details than necessary which can lead to a less clean and maintainable codebase. It might be tempting to make more internals visible just to simplify testing.

One consideration when adding InternalsVisibleTo is maintenance. If we decide to improve or refactor parts of the code in the future, we might encounter extensive test failures due to the tight coupling between tests and internal implementation details. This could result in significant additional development time to fix the tests.

Personally, I'm of the opinion that this is a feature rather than a bug, but there is definitely a balance to be found. I think we would not want to start exposing the privates of a component, but testing at a granular level allows you to build confidence at each level. My testing philosophy might be a bit heavily weighted towards one side of the spectrum, tho.
Anyways, I'm not planning to write a billion tests at this point, but having the option to back fill some unit tests related components are changed would be useful.

I agree we should be able to unit test our classes, that will help us write better code with a more modular design. I agree with @saurabh500 this was a blocked practice before but with modern tooling requirements, this should be added.

@JRahnama you have some valid points, however the tradeoff is that writing good, and perhaps complicated unit tests, allows the author of the change to focus on the methods being changed, rather than the big picture which is lot more complex and may be a cognitive overload. I would argue that it is lot more time consuming and strenuous to review code looking at the big picture, rather than reviewing the unit tests in isolation.
This also helps the authors of the perf test to test their changes in isolation.
Causing a unit test break, should be lot more thought provoking to see what could be the upstream impact of the change, rather than a tax to pay because of large refactoring.
Also change in the unit test allows the code reviewer to look deeper into "what really changed" rather than waiting for a regression to be surfaced in the CI, with the complex distributed nature of the testing.
Yes, we need to have a balance of what is being exposed as internals vs what should be kept private. The Code reviewers should provide the feedback that too many internals are being exposed, instead structure the code to lot more testable from internals rather than making anything private. This then makes the author of the change rethink their code and its testability.
I foresee this change bring the following:

Big changes don't need to come in at once. Anyone making larger changes can send the changes iteratively, rather than implementing the big feature, by making sure that they don't break anything that exists and add coverage for their iterative changes even if they are internal.
There is active perf work in progress, so that author of perf changes can Benchmarks of internals rather than relying on figuring out how to hit the code paths using public APIs. At the same time, say things like changing a byte[] to Span to reduce on-heap allocations, can be tested much more easily. (too late for this since the contributors have already been through this pain)

Of course this doesn't mean that we don't do our integration tests. They will continue to be as important as they are now, but unit testing allows for a tighter loop of development.

@benrr101 Would you like to own this.
I think making InternalsVisibleTo, along with unit testing an internal would be the right way to go. Also it would be interesting to see if you have a thought in mind on what the namespace placement for unit tests should be? Should they match the class being tested? Or anything else that you have in mind?

FWIW I generally agree with @saurabh500... I do always go as far as possible in testing/benchmarking using public APIs only - that has the advantage of testing the actual user-facing API end-to-end (providing more test value/coverage), and not being sensitive to internal refactors etc. But there are specific cases where it does make sense. If you look at Npgsql, IIRC there are very very few tests using InternalsVisibleTo to cover internal types - but they do exist. It does require a bit of discipline, since sometimes it requires more effort to implement test coverage via the public test API; but it's almost always better to do that if that's possible.
On a very related note... Many of the cases where I originally thought I'd need to resort to unit testing, were cases which relied on the database sending back exceptional/weird results that can't be triggered in a normal test; for example, how does one test the database crashing in the middle of a command? We ended up doing a small "mock PostgreSQL" implementation in our tests; this allows us to write tests where we can exactly control what protocol messages are sent back by the database, and when. Of course, doing this is an investment (it wasn't as big as I thought), but it's really valuable and definitely better than trying to cover things via unit tests.

I'm not sure it's a good idea. Since netcore doesn't have strong naming if you add internals visible to anyone can simply name their assembly as the test assembly and get access to the internals. However if they do that then they're silly and they can get the code and make their own version these days.

Since netcore doesn't have strong naming if you add internals visible to anyone can simply name their assembly as the test assembly and get access to the internals. However if they do that then they're silly and they can get the code and make their own version these days.

They can also already use reflection to access any internal (or even private thing). public/internal/private really isn't about security or anything like that - it's just a matter of signalling to users which APIs should be used, but if users are intent on bypassing those signals, they can always do that anyway...


Encoder Esc-button

Hi, me again,
I'm fairly new to arduino, and would like to add an escape-button to the encoder-control when double-clicking the encoder. How could i implement that in the LCDML_control doc?

You can add this feature by ussing OneButton Library (it also works setting up on joystick control)
https://github.com/mathertel/OneButton
Also you must to include it on header of main arduino ino
 #include <OneButton.h>
Besides on the header of LCDML_CONTROL over encoder control setup after the definition pins
you should add this lines:
  OneButton button(_LCDML_CONTROL_digitalread, true);
  void enter(){LCDML_BUTTON_enter();}
  void quit(){LCDML_BUTTON_quit();}

comment this lines
// global defines
  uint8_t  g_LCDML_CONTROL_encoder_t_prev = 0;

on LCDML_CONTROL_loop
comment the following lines
  unsigned char t = digitalRead(_LCDML_CONTROL_encoder_pin_button);

  // change button status if high and low active are switched
  if (_LCDML_CONTROL_encoder_high_active == 1) {
    t != t;
  }

and this
    g_LCDML_CONTROL_encoder_t_prev = 1;
also this
else {
    // check button press time for enter
    if((millis() - g_LCDML_DISP_press_time) >= _LCDML_DISP_cfg_button_press_time) {
      g_LCDML_DISP_press_time = millis(); // reset button press time

      // press button once
      if (!t && g_LCDML_CONTROL_encoder_t_prev == 0) {
          LCDML_BUTTON_enter();
      }
      else {
        g_LCDML_CONTROL_encoder_t_prev = 0;
      }
    }
  }

and at last add this code
on LCDML_CONTROL_setup
  button.attachClick(enter);
  button.attachDoubleClick(quit);

on LCDML_CONTROL_loop before
// read encoder status
add this
	button.tick();
You're done
Regards

Great, thank you! Great match: OneButton is exactly the lib I am using for my projects :-)
Menu works fine! Just one correction to your code:
instead of:
OneButton button(_LCDML_CONTROL_digitalread, true);
should be:
OneButton button(_LCDML_CONTROL_encoder_pin_button, true);

That it's true I forgot to make that correction because actually I made that fix for joystick control, anyway it works for both making that correction, now you can close this issue.
Regards

I would also try to use an other Rotary Encoder handler based on pin change interrupt... there is wonderful library by Matthias Hertel, http://www.mathertel.de; available @ https://github.com/mathertel/RotaryEncoder

OK, just did it! works fine.
Just a quick question:  having encoder handler based on pin change interrupt, do I still need the following line in the    LCDML_CONTROL_setup    code:
  // set encoder update intervall time
  LCDML_BACK_dynamic_setLoopTime(LCDML_BACKEND_control, 5UL);  // 5ms

@sgryb
You're right. if you use that library you can delete that line, but in LCDML_CONTROL you need to redefine the buttons up and down, it'll not work properly as is.
Can you share your button up / down definitions for who wants to implement this?
Regards

Sure, here we go:

include library  to the main arduino.ino code:
#include <RotaryEncoder.h>

now with both OneButton and RotaryEncoder the entire CONTROL WITH ENCODER section looks like:
`
// *********************************************************************
// *************** (3) CONTROL WITH ENCODER ****************************
// *********************************************************************
#elif(_LCDML_CONTROL_cfg == 3)
// settings
#define _LCDML_CONTROL_encoder_pin_a           10 // pin encoder b
#define _LCDML_CONTROL_encoder_pin_b           8  // pin encoder a
#define _LCDML_CONTROL_encoder_pin_button      A3 // pin taster
#define _LCDML_CONTROL_encoder_high_active     0  // (0 = low active (pullup), 1 = high active (pulldown)) button

// source  https://github.com/Jomelo/LCDMenuLib/issues/14
// source: https://github.com/mathertel/OneButton
OneButton button(_LCDML_CONTROL_encoder_pin_button, true);
void enter(){LCDML_BUTTON_enter();}
void quit(){LCDML_BUTTON_quit();}
// Set global vars for a RoraryEncoder
static int16_t enLast = 0;
int16_t enValue;
int enSteps = 0;
boolean up = false;
boolean down = false;
// for RotaryEncoder
// source: https://github.com/mathertel/RotaryEncoder
RotaryEncoder encoder( _LCDML_CONTROL_encoder_pin_a, _LCDML_CONTROL_encoder_pin_b );
// The Interrupt Service Routine for Pin Change Interrupt 0
// This routine will only be called on any signal change on D8 and D10: exactly where we need to check.
ISR(PCINT0_vect) {
encoder.tick(); // just call tick() to check the state.
}
// *********************************************************************
// setup
void LCDML_CONTROL_setup()
{
// init pins  ->  do not need that; it is done in encoder initiation: RotaryEncoder encoder();
//pinMode(_LCDML_CONTROL_encoder_pin_a      , INPUT_PULLUP);
//pinMode(_LCDML_CONTROL_encoder_pin_b      , INPUT_PULLUP);
button.attachClick( enter );
button.attachDoubleClick( quit );
// You may have to modify the next 2 lines if using other pins than 8-PB0 and 10-PB2 - PORTB
uint8_t *pcmask=digitalPinToPCMSK(8);
PCICR |= (1 << digitalPinToPCICRbit(8) );
*pcmask |= (1 << digitalPinToPCMSKbit(8)) | (1 << digitalPinToPCMSKbit(10) );
}
// *********************************************************************
// loop
void LCDML_CONTROL_loop()
{
// check buttons
button.tick();
// check Encoder
enValue = encoder.getPosition();
enSteps = enValue - enLast;     // I use enSteps for counting encoder clicks for catching fast rotation in main loop()
if( enValue > enLast ) {
down = true;
LCDML_BUTTON_down();
} else if( enValue < enLast ) {
up = true;
LCDML_BUTTON_up();
}
enLast = enValue;
}
// *********************************************************************
// ******************************* END *********************************
// *********************************************************************
`

@fietstasss
Could you fix your issue?


Create a plugin to allow us to easily create escalation incidents to specific Pagerduty teams

The full context for for this plugin (and requirements) are in the following Jira tickets:

MORPH-636
MORPH-645
MORPH-646

Would love your comments and feedback!
(Note that this should close out all the stores in the Lassie epic!)

reading through the test cases everything looks alright


Incorrect LTComponent in a rotated LTChar

In the construction of an LTChar class, the bounding box of the char is calculated based on the rotated coordinates of the character's bounding box.
However, the LTComponent is initialized on the coordinates of a bounding box containing only  the rotated lower left and upper right corners.
In most cases where there is a rotation, the rotated top left and bottom right corners may be outside of the LTComponent bounding box.
I have tested this file, and put a breakpoint in the LTChar init method.
Correct implementation will be:
       bbox_upper_left = (bbox_lower_left[0], bbox_upper_right[1])
       bbox_lower_right = (bbox_upper_right[0], bbox_lower_left[1])
       (ll_x, ll_y) = apply_matrix_pt(self.matrix, bbox_lower_left)
       (ur_x, ur_y) = apply_matrix_pt(self.matrix, bbox_upper_right)
       (ul_x, ul_y) = apply_matrix_pt(self.matrix, bbox_upper_left)
       (lr_x, lr_y) = apply_matrix_pt(self.matrix, bbox_lower_right)
        x0 = min([ll_x, ul_x, lr_x, ur_x])
        x1 = max([ll_x, ul_x, lr_x, ur_x])
        y0 = min([ll_y, ul_y, lr_y, ur_y])
        y1 = max([ll_y, ul_y, lr_y, ur_y])
        LTComponent.__init__(self, (x0, y0, x1, y1))

That's indeed a bug.
In my own words: the layout algorithm here interprets the text state, graphics state, matrix and font to compute the bounding box of the "layout character". It does so by only computing the lower left and upper right corner of the bounding box. However, this is not a correct representation for a bounding box of a rotated character. For example, when the lower left corner has the same x-coordinate as the upper right coordinate it has zero width.
The proposed solution is to use the outer bounding box that tightly fits the rotated bbox coordinates (see figure). This is a fine fix since it is clearly an improvement over the current situation.

However, the underlying problem is that a single bounding box is not a correct representation of a rotated bounding box. Perhaps we should store the rotated bounding box information in LTComponent besided the outer bounding box info.
After setting the correct bounding box coordinates the HWTLConverter should also be updated to properly show rotated bounding boxes.


'amplify pull' does not pull down aws-exports.js file

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
7.6.5
What operating system are you using?
mac
Amplify Categories
Not applicable
Amplify Commands
pull
Describe the bug
'amplify pull' does not pull down aws-exports.js file.
I deleted and created cognito ( auth ). I need to update aws-exports  file on other frontend project
Expected behavior
aws-exports.js file to be updated.
Reproduction steps
1 web frontend  + amplify project
1 ios frontend project ( which already did amplify pull )
at backend project delete auth. create auth. which changes cognito id.
at ios amplify pull. aws-exports file not changed. even if you delete aws-exports file, amplify pull won't create it.
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
There was a same issue. But it closed automatically. https://github.com/aws-amplify/amplify-cli/issues/5512
workaround:
Delete amplify folder on ios project. but you have to go through all questions

Hard to tell but this might be related to an issue I started seeing 12 hours ago. We have an automated amplify build triggered on every code change. With the last build we started seeing the following error on the front end:
Error: Region is missing
The error seems to happen when we make any requests to s3.
Comparing the latest build to an older one I can see that the amplify-meta.js file is missing the output block from the "s3Media" section. That's where the region had been usually configured.

Hey @goldwareJapan :wave: thanks for raising this! In your iOS app did you originally select to not modify the backend?
> amplify pull --appId d1vfckhhiu71it --envName staging
? Select the authentication method you want to use: AWS profile

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use default
Amplify AppID found: d1vfckhhiu71it. Amplify App name is: amplifyapp
Backend environment staging found in Amplify Console app: amplifyapp
? Choose your default editor: Visual Studio Code
? Choose the type of app that you're building javascript
Please tell us about your project
? What javascript framework are you using none
? Source Directory Path:  src
? Distribution Directory Path: dist
? Build Command:  npm run-script build
? Start Command: npm run-script start
? Do you plan on modifying this backend? No

If so, we will need to run the full amplify pull command with the appId and envName as shown in the sample above to update the exports file.

did you originally select to not modify the backend?

Yes. We did select not

run the full amplify pull command with the appId and envName

Tried with full argument. still same result. aws-exports.js file not being created.
❯❯❯ ls apps/back/src/aws-exports.js
apps/back/src/aws-exports.js
❯❯❯ mv apps/back/src/aws-exports.js apps/back/src/aws-exports1.js
❯❯❯ ls apps/back/src/aws-exports.js
ls: apps/back/src/aws-exports.js: No such file or directory
❯❯❯ amplify pull --appId $appId --envName dev
Opening link: https://ap-northeast-1.admin.amplifyapp.com/admin/*******/dev/verify/
✔ Successfully received Amplify Studio tokens.
Amplify AppID found: *******. Amplify App name is: ******
Backend environment dev found in Amplify Console app: ******

Added backend environment config object to your project.
Run 'amplify pull' to sync future upstream changes.

❯❯❯ ls apps/back/src/aws-exports.js
ls: apps/back/src/aws-exports.js: No such file or directory

Is it because I selected
Source Directory Path:   apps/back/src

Is it because I selected
Source Directory Path: src

tried with src. still same.

as experiment I created new folder and tried pulling as javascript with no frame work.
❯❯❯ amplify pull --appId ****** --envName dev                                                                                cognito ✭ ✖
Opening link: https://ap-northeast-1.admin.amplifyapp.com/admin/******/dev/verify/
✔ Successfully received Amplify Studio tokens.
Amplify AppID found: ******. Amplify App name is: ******
Backend environment dev found in Amplify Console app: ******
? Choose your default editor: Visual Studio Code
? Choose the type of app that you're building javascript
Please tell us about your project
? What javascript framework are you using none
? Source Directory Path:  apps/back/src
? Distribution Directory Path: dist
? Build Command:  npm run-script build
? Start Command: npm run-script start
? Do you plan on modifying this backend? No

Added backend environment config object to your project.
Run 'amplify pull' to sync future upstream changes.

and tried deleting aws-exports.js and pulled with full command. it is not creating file again.
https://github.com/aws-amplify/amplify-cli/issues/9416#issuecomment-1005286276

on a main react project with Do you plan on modifying this backend? Yes
tried deleting aws-exports.js and amplify pull. It creates aws-exports.js file again.

OK. Now I have a more serious problem.
When I checkout to another env and push. it created 2 Cognito pools. but aws-exports.js file does not change.
I have no idea where to get newly created env's cognito_user_pool_id. ( I can copy it from Cognito admin console. Don't want it to be hardcoded. I want it to be changed with amplify commands )
Because I want my production users to be on 1 user pool and dev users on another user pool.

Hey @goldwareJapan thank you for those details!  I was able to successfully reproduce two issues:

cognito_user_pool_id value is not updated in aws-exports.js when pulling environments in a project where we selected to not modify the backend
cognito_user_pool_id value is not updated in aws-exports.js after pushing a new environment, requiring us to run amplify env checkout <newly-created-environment> to update the value

Reproduction Steps:

create new project amplify init -y
add auth with defaults amplify add auth
push amplify push -y
observe aws_user_pools_id reflects newly created userpool
add another environment amplify env add next
push amplify push -y
observe cognito_user_pool_id is not updated, run amplify env checkout next to update the value in aws-exports.js
in a separate directory, pull the existing app with amplify pull --appId <existing-amplify-app-id> --envName dev, choose not to modify backend
observe aws-exports.js is created and the cognito_user_pool_id is populated correctly
pull the next environment with amplify pull --envName next
observe cognito_user_pool_id is not updated

note: we are unable to run amplify env checkout next to update the exports file as we did not choose modify the backend when we pulled the app
we are unable to remove the aws-exports.js file and recreate with amplify pull --envName next

As a workaround, we can remove the second project's amplify/ directory as well as the aws-exports.js file and re-pull the new environment to generate the aws-exports.js with the new User Pool: amplify pull --appId <existing-amplify-app-id> --envName dev

@yuth this appears to be also affecting the GraphQL API's URL

@yuth this appears to be also affecting the GraphQL API's URL

It is because the CLI is treating all the values from the prev env as custom config and retaining the value. I am working on a fix for that


Add label support introduced in V0.17

Cf.
https://bitcoincore.org/en/releases/0.17.0/#label-and-account-apis-for-wallet,
some methods have been deprecated. To ensure backwards compatibility,
the deprecated methods are not removed in this commit.
The gist of the changes is that the "account" concept is replaced by
the "label" concept which map one-to-one to labels used in the
GUI version of Bitcoin Core. Thus the CLI use of labels is
compatible with GUI use of labels. Previously this was not the case.
See the above link for a description of the new methods.
Added methods:

GetAddressInfo
GetAddressByLabel
GetReceivedByLabel
ListLabels
ListReceivedByLabel:
Like ListReceivedByLabel but the field InvolvesWatchOnly is added. It
indicates if the returned balance includes tx outputs sent to
watch-only addresses. This field is null if the reveived amount is 0.
SetLabel

Changed methods:

ListUnspent:
Added a "Label" field, but kept the "Account" field for backwards
compatibility. Both cases are handled in the associated response
class' ToString method.

The method arguments named "account" have not been renamed to label.
This may be appropriate to do for v0.18 or if the backwards compatibility
is removed from this library.

This commit is intended to close Issue #93.

Thank you! I will make sure to review this over the weekend. It looks promising from what I see already. :100:

@Sword-Smith

To ensure backwards compatibility, the deprecated methods are not removed in this commit.

I think, sooner or later, we have to drop support for old(er) versions. As stated in the official docs:

The account can continue to be used in V0.17 by starting bitcoind with the -deprecatedrpc=accounts argument, and will be fully removed in V0.18.

@Sword-Smith, thank you! This is now up on NuGet as BitcoinLib 1.11.0.


Uninstalled extensions not deleted, keep reloading

Insiders, Mac

I've got a few extensions installed that I have previously uninstalled, but at some point they are being loaded again.
For example, in this picture you can see the kubernetes and hue extensions, which I've previously uninstalled (a number of times).

I went and uninstalled the kubernetes, hue, and shades of purple extension again. But when we look at the .vscode-insiders\extensions folder, you can see the folders still there, plus a number of others that I've uninstalled in the past (marked with red arrow):

Also, as you can see above, i'm getting a number of versions of the extensions being left on the disk as well.
And eventually, i can't figure out when, these extensions on disk that i previously uninstalled will be loaded again (see the first picture).
Any ideas on what i can look for?

@chrisdias we do not remove the uninstalled or outdated extensions immediately. Clean up is done after you restart VS Code. Please restart VS Code and all of them will be gone.
Regarding showing uninstalled extension, do you have steps to repro? When you install an extension, we do not remove it immediately. Instead we tag it in an internal file and we do not show/load those tagged extensions. You should not see the uninstalled extensions after you reload. Please try and let me know if you see otherwise.

@chrisdias Regarding clean up, there was a bug in insiders that clean up was not getting called at start up. Fixed it. But this should not impact the issue you reported showing uninstalled extensions in the UI. I would still need some help (steps) from you to repro.

@chrisdias Can you please check the contents of .obsolete file in your extensions folder?

I upgraded my Insiders build yesterday and did not see the "old" extensions activated again.  So that was goodness.  There is no .obsolete file in the .vscode-insiders/extensions folder and all of the duplicate/uninstalled extensions have been deleted from there, so that's goodness too.

So, it looks like things have been cleaned up.  I'll close for now and reopen if it starts happening again.


explicit commit()

Dexie should use IDB's commit() as a performance optimization as it helps cut down on trips through the event loop and, in the case of Chromium, IPC. It appears that commit() is used only for rw transactions and only temporary ones.
I'm curious to know why the change was made to remove commit() from temp readonly txns. In Chromium at least, commit() also works on readonly transactions and will help by unblocking queued (rw) transactions faster.
It also seems like it should be possible to call commit() when the txn scoping function completes for non-temporary transactions, but perhaps I'm missing something.

Thanks for your findings. Reason for this change was that I was not certain whether the call to tx.commit could slow down the reading operation itself as the result is already retrieved before calling it (even though, as you're pointing out, there might still be a theoretical gain of committing readonly transactions to resume other rw transactions earlier). Might need to be measured to know how it would affect the read operations in the normal case.
Regarding non-temporary / explicit transactions, it would be a breaking change to explicitly commit them when the scopeFunctions's promise is resolves - it's not uncommon to create a transaction and execute operations without awaiting them and instead rely on the transaction's promise to know when all operations were done. This would not work for update() operations since they involve a sequence of get()/put() under the hood.


Sync Percentage 99.88% & Sync Status OFFLINE

EU Indoor miner is stuck in Sync Percentage 99.88% & Sync Status OFFLINE   , after PoC v11 and rollback  PoC v10

same here @shawaj an update would be nice even if its not good news currently.

Please email<EMAIL_ADDRESS>this is not a support channel


latest document is not latest

The latest document is not latest according to the source code. Does it just work like this or something is wrong?

@lixxu I think it might correlate with pypy releases. Note that it says 0.4.1 in the tab header, which I believe is the latest published version.

imo stable version should be 0.4.1

@lixxu which is what the docs are, no?

currently the latest doc and the stable doc points the same document, I think latest doc should be synced with the latest commit version, while the stable doc synced with published version. Anyway, it's not big issue as it's only the document, you may close it or I'll close it. This issue is sounds like a suggestion.

@lixxu I was wondering that too. @kdelwat may have an idea, he's the one who setup the sphinx/readthedocs integration for us.

This is working now so I'm going to close this for the time being.


Remove Dropdown list from collection tile

The dropdown list only contains 1 item - Edit Name.
The dropdown list should be removed and instead an Edit button should be added.

I want to try to work on this.

Where can I find the dropdown list this is referring to?

Here you go: https://github.com/mannprerak2/putaway/blob/27ee27b010391d6d486ee839ff11ef45040a5169/src/components/tiles/CollectionTile.svelte#L270

@mannprerak2 Thanks, I see it now


Clarifying exclusive identifier behavior

Related: https://github.com/MicrosoftDocs/powerquery-docs/issues/151
Clarifying to reflect the fact the special exclusive identifier reference rules don't apply to global identifiers and Section1!-style references.

Docs Build status updates of commit 05f28bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-basic-concepts.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@DougKlopfenstein

@bgribaudo and @ehrenMSFT
Should the sentence mentioned above be retained? If so, please add it back in to the PR and let me know if all the other changes are approved. Thanks.


Revert this back to the hardcoded version from change in SAK-40634

Thansk @jonespm

Sure, let me know if you have any questions about SAK-40658 when updating that. I'm still in Slack and github, but don't have any easy way to release anything at the moment. Should be easy for @ern  (or whoever is doing releases now)

Thanks @jonespm.

@jonespm The good thing about https://jira.sakaiproject.org/browse/SAK-40634, despite it broke the Jenkins build only, is that 2 of 3 plugins use webjars and a human-readable version.
Thanks for fixing this


Shot sequence problem

This seem to post the _hit event early on the first switch:
shots:
shot_terra_1_right_orbit:
switch_sequence: s_orbit_right, s_orbit_left
time: 3s
profile: terra1_profile
show_tokens:
leds: led_right_orbit_arrow
From: https://groups.google.com/forum/m/#!topic/mpf-users/p-sarKgsoOk

No reproducible. Added a test.


WIP: Added Test Files For GraphQL Package

Task linked: CU-33qw99 Graphql Package Unit Testing

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Registration page of some packages has incorrect "listed" attribute.

Some packages are listed in V2 but have a registration page that suggests they are unlisted and vice versa.
It seems to me like Catalog2Registration either skipped or incorrectly updated these when they were listed or unlisted.
They all appear in the search index and flat container correctly.
The issue has occurred more recently than the last search index rebuild so it is likely an issue with just Catalog2Registration itself.
Here is a report containing every package with this issue.

One of the issues: https://github.com/NuGet/NuGetGallery/issues/3709

Another issue: https://github.com/NuGet/NuGetGallery/issues/3716

All affected packages were reflowed.


build_sdist expects only .tar.gz

The user can pass in though { "--global-option": ["--formats=zip"]} so the generated file can also have .zip extension. https://github.com/pypa/setuptools/blob/master/setuptools/build_meta.py#L181

Looking into it...

I posed a question about this on the mail list but ask here as well.
<EMAIL_ADDRESS>I am unclear what is going wrong  running: (python3 setup.py sdist --formats zip) gives what i would expect to be the desired result.
[setup-tools-tes ~ 04:17] $ python3 setup.py sdist --formats zip
running sdist
running egg_info
writing HelloWorld.egg-info/PKG-INFO
writing dependency_links to HelloWorld.egg-info/dependency_links.txt
writing top-level names to HelloWorld.egg-info/top_level.txt
reading manifest file 'HelloWorld.egg-info/SOURCES.txt'
writing manifest file 'HelloWorld.egg-info/SOURCES.txt'
warning: sdist: standard file not found: should have one of README, README.rst,
README.txt, README.md
running check
warning: check: missing required meta-data: url
warning: check: missing meta-data: either (author and author_email) or (maintainer and
maintainer_email) must be supplied
creating HelloWorld-0.1
creating HelloWorld-0.1/HelloWorld.egg-info
copying files to HelloWorld-0.1...
copying setup.py -> HelloWorld-0.1
copying HelloWorld.egg-info/PKG-INFO -> HelloWorld-0.1/HelloWorld.egg-info
copying HelloWorld.egg-info/SOURCES.txt -> HelloWorld-0.1/HelloWorld.egg-info
copying HelloWorld.egg-info/dependency_links.txt -> HelloWorld-0.1/HelloWorld.egg-info
copying HelloWorld.egg-info/top_level.txt -> HelloWorld-0.1/HelloWorld.egg-info
Writing HelloWorld-0.1/setup.cfg
creating 'dist/HelloWorld-0.1.zip' and adding 'HelloWorld-0.1' to it
adding 'HelloWorld-0.1'
adding 'HelloWorld-0.1/HelloWorld.egg-info'
adding 'HelloWorld-0.1/setup.py'
adding 'HelloWorld-0.1/PKG-INFO'
adding 'HelloWorld-0.1/setup.cfg'
adding 'HelloWorld-0.1/HelloWorld.egg-info/SOURCES.txt'
adding 'HelloWorld-0.1/HelloWorld.egg-info/top_level.txt'
adding 'HelloWorld-0.1/HelloWorld.egg-info/dependency_links.txt'
adding 'HelloWorld-0.1/HelloWorld.egg-info/PKG-INFO'
removing 'HelloWorld-0.1' (and everything under it)
[setup-tools-tes ~ 04:17] $ ls dist/
HelloWorld-0.1.zip

@adamRogerson There's nothing wrong with what you've posted. The command you ran is intended to produce a zip file and that's what it did. If you have other expectations, please file a separate ticket and describe what you expected to happen differently.

@gaborbernat The code has changed a lot since this issue was reported... and I see that --formats gztar is now hard-coded into the build_sdist command.
https://github.com/pypa/setuptools/blob/297f2adceda3af402fc08311e42505c8cdc9c54b/setuptools/build_meta.py#L211-L214
I suspect that would cause errors if someone tried to use the --global-option to specify a zip. Does that address the issue? I'm assuming yes and closing the issue, but if the issue remains, please reopen and describe how one could replicate it.


Prepare for version 2.1.0 release

Need to prepare the next big release where develop branch is pushed alongside with updated libroadrunner, antimony, etc.
TODO:

[x] Fix AUTO 2000 plugin
[x] Fix Travis CI for Tellurium develop branch (issue with omex testing)
[x] Release new libRoadRunner
[x] Fix Travis CI for libRoadRunner (issue with dependency .deb not updated to include nleq2)

Noticed that there are some issues with Spyder 3.3.0 running on Python 3.6 due to PyQt5. Also, Spyder 3.3.0 drops support for PyQt4 which is an issue for Python 2.7 version. For now, I will be generating Python 3.7 version with Spyder 3.2.8 only. Working to find solutions for Python 3.6 version and Python 2.7 version of Spyder 3.3.0.


Modals Cleanup

Added a Styled Modal with warn levels and a title
Added a Confirmation Modal for yes/no modals
Fixed styling in Popup
Moved ConfirmationModal to dialog package

Replaced with https://github.com/kgrgreer/foam3/pull/443


Can this project run on Heroku

Hey, I’m wondering if there is a way to deploy this into Heroku. (https://heroku.com)

I don't think this would work on Heroku. Not sure what kinda of specks Heroku offers, but I'm pretty sure it cant handle what n.eko needs (at least on the free tier) I'll leave this open for anyone who wants to attempt this.

Due to heroku memory limitations, this would pretty much never be able to run

Do you know any other free providers that would be able to run it?

I am personally not even sure how rabb.it was able to keep proving their services for how long they did at all.
The resources it takes up aren't exactly lightweight, so if they had went paid they might have been able to keep afloat.

I’m new to hosting something like this so something like a video guide would be helpful xD

@TheFatalKiller DigitalOcean is currently offering $100 in credit (and their VMs are billed hourly) to new users. You could also try Vultr who are giving away $50 in credit to new users. Either of these will be fine.


HLS Predictive Preload

Now that https://github.com/Deathspike/animesync/issues/19 is implemented, performance is pretty good. Now each piece request uses the existing proxy connection and incurs no TCP connection overhead. However, sending a HTTP request message from the EU to the US still carries a 100-200ms penalty because of physics. All of the tested applications, ffmpeg, vlc and video.js request and wait the completion of a piece before requesting the next. The sequence is as followed:

Request p1 (+100ms)
Download p1 (+500ms)
Request p2 (+100ms)
Download p2 (+500ms)
Request p3 (+100ms)
Download p3 (+500ms)

Predictive preloading should make animesync aware of the next piece in the HLS manifest. Once p1 is requested, a connection for p2 should also be established. The second connection does not have to download the HTTP body, but only the headers. Then once the request for p2 comes in, a pipe is established between the open preloaded connection and the requestee. As a result, the remaining request overhead should mostly be cut out. This is the sequence:

Request p1 (+100ms), prepare p2
Download p1 (+500ms)
Request p2 (use existing pipe), prepare p3
Download p2 (+500ms)
Request p3 (use existing pipe), prepare p4
Download p3 (+500ms)

This should yield a nice performance benefit.

With the latest fixes to the agent connector and agent pools, there's no notable delay when setting up the next piece request. This idea is therefore not necessary and won't be implemented. The mentioned changes will be live in 0.10.0.


Use of "dots" in assembly instruction names

Issue to track how dots are used in the proposed instruction assembly names.

I would remove the “.” unless the two (or more) instructions are really very close variations of one operation.  The .vv, .vi, .vs, .vx variations of essentially the same vector instruction are an example of this.  If the instructions represent different basic operations, then I would refrain from using the base + dot + suffix format to name them.
Therefore, I would propose removing the dots from all the current mnemonics such as  saes32.encs, saes32.encsm where the underlying computation is different.  (Note, I also recommend removing the leading "s")

Therefore, I would propose removing the dots from all the current mnemonics such as saes32.encs, saes32.encsm where the underlying computation is different. (Note, I also recommend removing the leading "s")

Agreed with both points. I'll take this action once we know exactly what each instruction should be called.


Connection dies when left idle

Steps I took:

Created a new linux VM with boot2docker-vagrant
Created a new container with fig up -d and the fig.yml file in this repository
SSHed to the new container, and installed drupal
Navigated to http://<IP_ADDRESS>/
Saw that Drupal was installed
Went to lunch (gone about 30 minutes)
Returned to see that my SSH session to my new container had terminated with the following error:

root@41d21429d40c:/var/www# Couldn't connect to Docker daemon - you might need to run `boot2docker up`.

Saw that my VirtualBox VM was in an "aborted" state (whatever that means)

Attempted to run fig run --rm web bash and received the same error as above
Attempted to run fig up -d and received the same error as above.
Booted my linux VM in the VirtualBox UI
Attempted to run fig up -d and received the following error:

Recreating demo_dbdata_1...
Recreating demo_db_1...
Cannot start container bfa220b0c6e7441ca28acecb8e870011e2846a7171b13cd690f5f0b5273ee83c: Error starting userland proxy: listen tcp <IP_ADDRESS>:3306: bind: cannot assign requested address

Ran the following three commands:

vagrant halt
vagrant up
fig up -d

Saw that my container started successfully, with the following message

Recreating drupal7_dbdata_1...
Recreating drupal7_db_1...
Recreating drupal7_web_1...

@MKorostoff  this will be pretty difficult to reproduce and debug. Have you experience this issue recently?

I'm not sure why this would be closed.  I have not used drude really at all since this was first reported, but I experienced it twice in my week with drude.

@MKorostoff this was closed for the lack of feedback and since no one else reported a similar issue.
If you continue to use drude and have this issues, then let me know, so it can be debugged.


TypeError in /clan/rfyqy-nb-ry82uv80

Error in ClashLeaders
TypeError in /clan/rfyqy-nb-ry82uv80
Cannot read property 'iconUrls' of undefined
View on Bugsnag
Stacktrace
webpack:///js/components/PlayerComparison.vue?5779:12 - PlayerComparisonvue_type_template_id_39a24aea_scoped_true_render

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/shbb-swry-v0q8qc02

An error linked to this issue has been reopened in Bugsnag
TypeError in /clan/kamimboto-2y98j0u8

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/jotto-yp99v9q


Generate Profiling Database

Hi
It would be very useful to have the option to generate a profiling database and not just the HTML report. The database would contain the values displayed in the report (one or more dataframes that can be saved to csv, as an idea), it could be used to maintain historical profiling information as well as an input for other downstream processes.

The calculated results are already saved to an object so if you only want those without the report you could just use
import pandas_profiling
import pandas as pd
df = pd.read_csv("https://data.nasa.gov/api/views/gh4g-9sfh/rows.csv?accessType=DOWNLOAD", parse_dates=['year'], encoding='UTF-8')
res = pandas_profiling.describe.describe(df)
print(res)

The functionality seems, for the largest part, already in place.


Correct polymorphism in ClusterTarget/AddOnClusterTarget

AddOnClusterTarget needs to be a subclass of ClusterTarget
see
https://github.com/redhat-developer/app-services-sdk-java/compare/0.10.0...lucamolteni:0.10.0-AddOnCluster?expand=1#diff-349cd8b62a4f79f02d18e78d32ce7450586b7570b96164ed577b73128cc5e856R47

@valdar we need this change in the managed connector repository as well


Feature request: standalone configuration file

While working on projects that do not have a package.json file present it would be nice to still be able to pass options to nyc. Would you consider adding support for an alternative standalone configuration file similar to istanbul's .istanbul.yml?

You can add a package.json file with just the nyc config:
{
  "nyc": {
    "exclude": [
      "**/*.spec.js",
      "build"
    ]
  }
}

I agree with @sindresorhus. The contents of an nyc config are just not substantial enough to warrant their own file. It drives me crazy that even a minimal project needs nearly 10 files, only two of which (index.js and test.js) contain code. I don't want to pile more files in the base dir of projects for no good reason.

@gdeoliveira does @sindresorhus' approach of an empty package.json do the trick for you?

Just to clarify I wasn't proposing to move the configuration of the tool to a separate file when a package.json file is available, merely that it would be nice to be able to configure nyc on a non-node project via a secondary/alternative configuration file.
@bcoe It's a nice workaround but I think I'll stick to passing the options directly to the tool for the time being.

Let's continue this discussion here: https://github.com/istanbuljs/nyc/issues/287


xorm reverse doesn't support postgresql inet type

When I use xorm reverse tools to reverse my database tables, It occured that "[Error] reverse.go:160 Unknown colType: inet", not support postgresql inet?
-- Table: public.logs

-- DROP TABLE public.logs;

CREATE TABLE public.logs
(
    uid uuid NOT NULL DEFAULT uuid_generate_v4(),
    meta_data jsonb,
    created_at timestamp with time zone,
    updated_at timestamp with time zone,
    deleted_at timestamp with time zone,
    created_user_uid uuid DEFAULT uuid_nil(),
    updated_user_uid uuid DEFAULT uuid_nil(),
    comment text COLLATE pg_catalog."default",
    ip inet,
    client_refer uuid,
    src_addr inet,
    CONSTRAINT logs_pkey PRIMARY KEY (uid)
)
WITH (
    OIDS = FALSE
)
TABLESPACE pg_default;

ALTER TABLE public.logs
    OWNER to tsl;

Currently not supported yet.


Automatically create PR with Terraform plan output to Production

Automatically create PR with Terraform plan output to Production. This need to be create anytime the latest tf code is merged to production for DevOps team to approve  before the apply

I was able to autocreate the PR but still unable to parse terraform plan into the PR.
I opened this issue in stackoverflow


Every 40-60 minutes packets dropped on VXLAN network interface

Expected Behavior
No dropped packets on vxlan network interface during normal operation.
Current Behavior
Each host experience short period packet drop of transmit packet on vxlan network interface every 40-60 minutes.
Possible Reason

Some kind of hourly internal Calico job, like configuration rebuild, creates pause in vxlan interface functioning?
Configuration in my calico-vxlan.yaml file produces Calico miss-configuration?

Steps to Reproduce

clone https://github.com/gvych/calico-packet-drop-problem repository git clone https://github.com/gvych/calico-packet-drop-problem.git; cd calico-packet-drop-problem
create AWS EKS cluster cd eksctl create cluster -f eksclt.yaml
install Calico kubectl apply -f calico-vxlan.yaml
install prometheus-operator using Helm helm repo add prometheus-community https://prometheus-community.github.io/helm-charts; helm repo update; helm install prometheus prometheus-community/kube-prometheus-stack
establish connection to Grafana kubectl port-forward -n default  svc/prometheus-grafana 8080:80
login to Grafana using credentials User:admin Pass:prom-operator on http://localhost:8080
each hour you will see metric instance:node_network_transmit_drop_excluding_lo:rate5m{} increases (independently for each server) Grafana Request Example

Using request rate(node_network_transmit_drop_total [10m] ) > 0  you can see, that all packet drop events occur on vxlan.calico network interfaces

Context
Our system experiencing sporadic TCP connection resets from Pods to other Pods or public internet (error messages we get: "read: connection reset by peer reset by peer").
Your Environment

Calico version:
"cniVersion": "0.3.1"
image: docker.io/calico/cni:v3.22.0
image: docker.io/calico/pod2daemon-flexvol:v3.22.0
image: docker.io/calico/node:v3.22.0
image: docker.io/calico/kube-controllers:v3.22.0
Orchestrator version:
AWS EKS version.Info{Major:"1", Minor:"20+",
Operating System and version:
Default AWS nodes used by eksctl (us-east-2 region)
t3a.small	ami-0e0c65ae692674f99
Link to your project (optional):
https://github.com/gvych/calico-packet-drop-problem

Are there any logs coming from calico/node at the time of the packet loss that might suggest it's performing some work? I'm not aware of any cyclic background task like this but perhaps there's something going on (e.g., a resync with the datastore or something)

Is there any chance this is DHCP renewal on the nodes?  Calico doesn't have any timers that trigger hourly.

Are there any logs coming from calico/node at the time of the packet loss that might suggest it's performing some work? I'm not aware of any cyclic background task like this but perhaps there's something going on (e.g., a resync with the datastore or something)

Nope, background "noise" logs did not differ in any way from logs around packet drops.

Is there any chance this is DHCP renewal on the nodes? Calico doesn't have any timers that trigger hourly.

Very interesting idea. Will check!

Yeap, default lease time from AWS VPC is 1 hour
[root@ip-192-168-108-88 dhcp]# cat /var/lib/dhclient/dhclient--eth0.lease ...   option dhcp-lease-time 3600;
Will look deeper into AWS EC2 side.
Thanks for the great hint!


dedicated diff for components.params

The bug was caused because we used ParametersDiff to compare params under components.
I renamed ParametersDiff to ParametersDiffByLocation and created a new type, ParametersDiff, to compare params under components without considering the param location (query, path, header or cookie).
Also added an "InDiff" field to ParameterDiff to cover the use case that a parameter under components could be modified by changing its location.

Codecov Report

Merging #354 (3420a62) into main (3a7f646) will decrease coverage by 0.15%.
The diff coverage is 88.77%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #354      +/-   ##
==========================================
- Coverage   80.55%   80.41%   -0.15%
==========================================
  Files         191      191
  Lines       10033    10083      +50
==========================================
+ Hits         8082     8108      +26
- Misses       1641     1659      +18
- Partials      310      316       +6

Flag
Coverage Δ

unittests
80.41% <88.77%> (-0.15%)
:arrow_down:

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

Files Changed
Coverage Δ

checker/checker.go
42.43% <0.00%> (ø)

diff/parameters_diff_by_location.go
74.80% <86.66%> (ø)

diff/parametes_diff.go
89.83% <89.83%> (ø)

diff/components_diff.go
94.44% <100.00%> (ø)

diff/headers_diff.go
95.23% <100.00%> (ø)

diff/method_diff.go
85.93% <100.00%> (ø)

diff/parameter_diff.go
72.72% <100.00%> (+0.50%)
:arrow_up:

diff/path_diff.go
88.46% <100.00%> (ø)

report/report.go
75.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


min_scene_len usage of

After testing, it is found that min_scene_len does not post-process the threshold segmentation results. For example, the four scenes are 2.3s, 1.2s, 3s, 2.2s. When min_scene_len=5, the output result will be 2.3+1.2+3=6.5s, 2.2s . But the current result may be like this 5s, 3.7s like this.

I looked at the source code and felt that using the content threshold to segment first, and then filtering with duration will get reasonable results. In a video with complex textures, if the _frame_score>_threshold of multiple consecutive frames is possible, the result will become unstable if the strip is split according to _min_scene_len. for example:
The _frame_score of 100-120 frames is 50 greater than _threshold, and the initial duration, such as 15 frames, will be cut to the 100th frame, and if it is set to 30 frames, it will be cut to the 115th stitch, so that the boundary of the frame will change.

I can't claim to fully understand the issue, but if you set min_scene_len=5, then that will set it to 5 frames rather than 5 seconds. To set the min_scene_len to 5 seconds, you need to append s onto the number (e.g. min_scene_len="5s" in python).
Your second point (if I understand correctly) is actually something I have come across before and done some initial thinking about. If I understand, then you are pointing out that there are instances in which a video can have different periods (scenes perhaps) in which a low threshold makes sense, but then other periods in which a high threshold makes sense. The best solution present in pyscenedetect right now is the detect-adaptive detector that does try to adapt to the nearby frames and adjust the threshold as it goes. However, there is no perfect algorithm, so we are always open to new approaches.

Thank you for your reply. What you said makes sense. At present, I am processing the content threshold and the minimum duration asynchronously. That is to say, the default value is 15, and a post-processing is added to limit the duration.


Locale data has not been initialized

Locale data has not been initialized, call initializeDateFormatting().
after adding
Intl.defaultLocale = 'ar';
intl: ^0.17.0

use this
import 'package:intl/date_symbol_data_local.dart';
initializeDateFormatting('fr_FR', null).then((_) => runYourCode());


FPS limit

Forum: https://forum.playcanvas.com/t/feature-request-fps-limiter-out-of-box-in-editor/21263
This is a feature request to allow a user to limit the FPS. It is useful for high end mobile devices, that can output 90-120 FPS, eating away the battery. It would be nice if such an option would be exposed in the Editor.

Closed in favor of #4597


Connector not working with Styled Player List

Mod Name
Styled Player List
Mod Homepage
https://modrinth.com/mod/styledplayerlist
Minecraft version
1.20.1 (LTS)
Describe the bug
Styled player list will not show the code in the player tab correctly when using sinytra.
Steps to reproduce

Open AT Launcher
Create a 1.20.1 forge server in the "create pack" tab (make sure to accept the TOS in the files)
Install Styled Player List, Sinytra, and Forgified Fabric API into the servers mods folder
Go to "Create Pack", create a 1.20.1 neoforge instance (I tried normal forge before this, i had the same issue, so i tried neoforge)
Install Styled Player List, Sinytra, and Forgified Fabric API into the mods folder
Go to the instances tab and press play
Click multiplayer and join the LAN server
Push tab, youll see the issue.

default.json the only config folder I edited to customize the playertab
Logs
https://gist.github.com/nyaukii/5d8550371ae77962fd9b70b81c0b6943
Additional context
I was previously using Styled Player List in a normal fabric instance in single player and it worked perfectly fine, but when I tried to use it for forge using sinytra it broke, thought I could fix it by making a server since thats the only way it would let me see the tab, and then the tab was all messed up.

As our LTS support target, 1.20.1 now only receives critical fixes related to Connector bugs. Please upgrade to the latest version for mod compatibility support.


Better portal caching

It takes a few seconds for the first portal to load up. Portals need to be cached in their different views so they can quickly clone new views

#91 will improve on this


[hotfix] simplify code

Motivation
Simplify code of ManagedLedger.getManagedLedgerInfo()
Modifications
unify the method of generating ManagedLedgerInfo
Verifying this change
This change is a  code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: （no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (no)

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@Renkai  PTAL

@BewareMyPower PTAL


Don't use RabbitMQ vhost if == '/'

The default RabbitMQ vhost is called '/' which is rejected by Graphite as a metric name. Instead we substitute the name 'default'.
Also fixed the markdown in the documentation string.

Thanks!

Hrm. This is breaking tests. Can you look at it and see why?


add user option "both", search forward and backward at the same time

I know this may make performance worse, but I think this is more convenient.

Already possible, see FAQ / Bidirectional search.