HBASE-24546 CloneSnapshotProcedure unlimited retry

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  6s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  1s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m  6s
branch-2.2 passed

+1 :green_heart:
compile
0m 55s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 22s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m  6s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
branch-2.2 passed

+0 :ok:
spotbugs
3m 20s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 17s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 42s
the patch passed

+1 :green_heart:
compile
0m 54s
the patch passed

+1 :green_heart:
javac
0m 54s
the patch passed

+1 :green_heart:
checkstyle
1m 19s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 17s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
26m 24s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 35s
the patch passed

+1 :green_heart:
findbugs
3m 28s
the patch passed

_ Other Tests _

-1 :x:
unit
168m 31s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 37s
The patch does not generate ASF License warnings.

234m 26s

Reason
Tests

Failed junit tests
hadoop.hbase.quotas.TestClusterScopeQuotaThrottle

Subsystem
Report/Notes

Docker
Client=19.03.11 Server=19.03.11 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1916

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux d9bb4412386f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1916/out/precommit/personality/provided.sh

git revision
branch-2.2 / f3e912b7d8

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/1/testReport/

Max. process+thread count
4380 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 12s
branch-2.2 passed

+1 :green_heart:
compile
0m 56s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 20s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m  5s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
branch-2.2 passed

+0 :ok:
spotbugs
3m 23s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 22s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 40s
the patch passed

+1 :green_heart:
compile
0m 55s
the patch passed

+1 :green_heart:
javac
0m 55s
the patch passed

+1 :green_heart:
checkstyle
1m 15s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m  3s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
25m 15s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 34s
the patch passed

+1 :green_heart:
findbugs
3m 16s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
166m 30s
hbase-server in the patch passed.

+1 :green_heart:
asflicense
0m 36s
The patch does not generate ASF License warnings.

229m 21s

Subsystem
Report/Notes

Docker
Client=19.03.11 Server=19.03.11 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1916

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 019766351e58 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1916/out/precommit/personality/provided.sh

git revision
branch-2.2 / e7f17fe68d

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/2/testReport/

Max. process+thread count
4484 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 11s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 15s
branch-2.2 passed

+1 :green_heart:
compile
0m 56s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 19s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m  0s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
branch-2.2 passed

+0 :ok:
spotbugs
3m 18s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 16s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 41s
the patch passed

+1 :green_heart:
compile
0m 56s
the patch passed

+1 :green_heart:
javac
0m 56s
the patch passed

+1 :green_heart:
checkstyle
1m 18s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m  0s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
25m 12s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 35s
the patch passed

+1 :green_heart:
findbugs
3m 17s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
179m 25s
hbase-server in the patch passed.

+1 :green_heart:
asflicense
0m 33s
The patch does not generate ASF License warnings.

243m 29s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1916

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux ebc0fd97eb30 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1916/out/precommit/personality/provided.sh

git revision
branch-2.2 / 4be5fe3154

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/3/testReport/

Max. process+thread count
4531 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1916/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Cross-contract calling: simple debugger

Description
Motivation
While full, true contract debugging is currently not achievable, we still can try to get some insights from an outside client to the contracts pallet's internals. Since it is the pallet that owns and maintains call stack, we can take an advantage of this direct access.
Intended usage
Target environment/client
Surely, when we work in a full-stack setting (i.e. including node layer), there's no point in introducing breakpoints. In the case of an RPC call, we could try returning some trace, similarly to a debug buffer. However, my intention is to achieve more interactive experience.
Suppose that we own/hold the whole runtime (embedded within externalities) and have direct (synchronous) access to it. Then, we can establish a simple callback-based communication with the contracts pallet. This is exactly the case when working with tools like https://github.com/Cardinal-Cryptography/drink, but also for pallet's unit tests, or even try-runtime suite.
Workflow
For now, we add just two simple breakpoints: just before and after an Executable object is invoked. Hence, we can debug complex multi-contract execution traces. Since the whole runtime is synchronous, naturally the callbacks will stop execution and progress when the handling is done.
Plan
In the near future we plan to add more such breakpoints, providing further information, but firstly we want to check the approach and define what things would be useful.
Checklist

[x] My PR includes a detailed description as outlined in the "Description" section above
[ ] My PR follows the labeling requirements of this project (at minimum one label for each A, B, C and D required)
[x] I have made corresponding changes to the documentation (if applicable)
[ ] I have added tests that prove my fix is effective or that my feature works (if applicable)
[ ] If this PR alters any external APIs or interfaces used by Polkadot, the corresponding Polkadot PR is ready as well as the corresponding Cumulus PR (optional)

I think this is a good idea. One thing that is important to me is that all this debugging code doesn't increase the complexity of the production code too much. What I mean by that is that we don't end up with a lot of compile time features and associated types added to Config.
I expect that over time you come up with more things you want to add to this debugging interface. Therefore I think we should make sure that we always only have a single feature and associated type.
Concretely:

Rename feature to unsafe-debug so that it will enable/disable all debugging (except debug buffer which is OK for production use).

Make sure all the debugging traits are grouped by a single trait to we always only need a single associated type on the Config:

trait Debug: ExecutionObserver + ExecutionTrace + ...
{
}

The downside is that all traits need to be implemented but we can just have sensible default implementations.

In order to provide some reasonable usecase, I prepared an example scenario of cross contract calling and debugged it using drink library (after necessary on-spot enrichments). The code is available on a branch: https://github.com/Cardinal-Cryptography/drink/tree/pallet-breakpoint.
In the example we have 3 simple contacts: a, b and c. In the scenario, we call contract a with some u32 value. Contract a forwards the argument to b, b forwards it to c and c returns a result of some arithmetic operation, which is then returned up the stack to the caller.
Note: since it was faster to use call builder pattern in the contracts, I also passed the addresses of b and c along the u32 argument (so that delegation is possible).
After running ./debugger_showcase.sh you should see:
Building contract c
Building contract b
Building contract a
Drinking

running 1 test

successes:

---- tests::test stdout ----
Contract with hash `0x118a…8b5e` has been called with data:
    new
and returned:
    ()

Contract with hash `0x2b1e…9b14` has been called with data:
    new
and returned:
    ()

Contract with hash `0x38fa…c6bc` has been called with data:
    new
and returned:
    ()

Contract with hash `0x118a…8b5e` has been called with data:
    call { arg: 7 }
and returned:
    Ok(22)

Contract with hash `0x2b1e…9b14` has been called with data:
    call { account_c: 5HHtX3hsCmVUTzpQtQKTnNyAQLnVzgUNrefA1kYvFwPfYbMX, arg: 7 }
and returned:
    Ok(22)

Contract with hash `0x38fa…c6bc` has been called with data:
    call { account_b: 5CjYz6jzGja6WnwTWgC11mMCSyscknKoAb3JpmuCQ3TfUs3m, account_c: 5HHtX3hsCmVUTzpQtQKTnNyAQLnVzgUNrefA1kYvFwPfYbMX, arg: 7 }
and returned:
    Ok(22)

The hardest part is to enable arbitrary handler. Why the hardest? Because the handler is invoked by the runtime. And since it is passed as an associated type to the pallet configuration, it must be fixed - we cannot have e.g. generic runtime. The way I chose to solve the problem (and actually there's the only one I know) is to outsource handler via runtime interface to a specially registered externalities extension. That way we can pass to the drink's Session any type that implements certain trait.

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3311091

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3311179

now I'm getting:
error[E0437]: type `Debug` is not a member of trait `pallet_contracts::Config`
    --> bin/node/runtime/src/lib.rs:1262:2
     |
1262 |     type Debug = ();
     |     ^^^^^^^^^^^^^^^^ not a member of trait `pallet_contracts::Config`

after adding the type declaration (previously it was complaining about not including this member). I guess that this kitchen-sink thing is compiled in multiple configurations, but I don't know how to get it right :(
at least test passes correctly (at least locally for me :stuck_out_tongue: )

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3313848

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3315822

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3319296

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3319295

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3319386

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3323056

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3324722

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3326497

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3326483

/bot rebase

bot rebase

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3331877

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3331879

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3331878

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3332279

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3332277

We need approval from CI team then we can merge.

bot merge


Replace the MonadReader instance with a more general version

The current MonadReader instance is specialized for the internal Connection state. However this makes PGTransactionT less useful as a generic transformer. A more general MonadReader instance would be something like
instance MonadReader r m => MonadReader r (PGTransactionT m) where

To regain the current behavior a getConnection function could be added.

@jfischoff thanks, good idea. We'd be happy to accept a PR for this -- is this something you'd be interested in contributing? Otherwise we're happy to make the change.

I have made code change, I'll submit a PR tonight.
On Wed, Aug 24, 2016 at 12:50 PM Reid Draper<EMAIL_ADDRESS>wrote:

@jfischoff https://github.com/jfischoff thanks, good idea. We'd be
happy to accept a PR for this -- is this something you'd be interested in
contributing? Otherwise we're happy to make the change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/helium/postgresql-transactional/issues/12#issuecomment-242133578,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKSO_YkohGoky-wqvBHa0ZogAJvVdQzks5qjHZAgaJpZM4Jrl7j
.


Bug fixed Contactus page

Summary
Briefly describe the purpose of this PR.
Description
Explain in detail what this PR is all about. This should include the problem you're solving, the approach taken, and any technical details that reviewers need to know.
PR Description:

Fixed UI Collision: Resolved a critical issue where the chatbot close button was overlapping with the dark mode toggle. This collision was causing usability challenges, making it difficult for users to access either button independently.

Enhanced User Experience: By separating these controls, users can now close the chatbot or toggle dark mode without accidental interactions or confusion. This improvement ensures a smoother and more intuitive user experience.

Increased Accessibility: Ensured that all interactive elements on the page are easily accessible and functional, particularly for users who rely on these features for a comfortable browsing experience.

Consistency in Design: Maintained design consistency across the interface by positioning the buttons in a way that aligns with standard UI/UX practices, reducing potential user frustration and increasing overall satisfaction.

Images
Include any relevant images or diagrams that can help reviewers visualize the changes, if applicable
Issue(s) Addressed
Enter the issue number of the bug(s) that this PR fixes

Template should be strictly Closes <issue_number>
Example: Closes #1366

Prerequisites

[X] Have you followed all the CONTRIBUTING GUIDELINES?

@Its-Aman-Yadav Sir, If possible please label this PR to level2 , I worked hard for this not only provide spacing between the close button and dark mode , I also added cursor pointer , Flex box , border radius and transition functionality.
Thankyou for your understanding.


Change name to elm-route-url

I'm planning to change the name of this repository to elm-route-url, to reflect the fact that the next version won't be limited to just the hash -- you will be able to route based on the full URL if you like.
Let me know if anyone has a better idea for a name ...

why not just elm-route?

There already is a Bogdanp/elm-route ...

So, the rename to elm-route-url is done. I re-published all the previous versions in the Elm package repository under the new name (as well as the new version).
Github does redirects for the old name, so installing elm-route-hash 1.x still works -- this shouldn't break anything for anyone.


DynamoDB: Model duplication

Describe the feature
There are some places where request objects define different API entries with almost identical parameters.
For example, TableCreationParameters of ImportTableRequest is almost a copy of CreateTableRequest.
Is your Feature Request related to a problem?
It would be nice if it were possible to generalize over such API entries, e.g. define table definitions in a single place
Proposed Solution
Provide a way to generalize code over almost completely same request objects
Describe alternative solutions or features you've considered
No response
Acknowledge

[ ] I may be able to implement this feature request

AWS Kotlin SDK version used
0.19.5-beta
Platform (JVM/JS/Native)
JVM
Operating System and version
Linux

Hi @eiennohito, thanks for reaching out.
The AWS SDK for Kotlin's service types (e.g., CreateTableRequest and TableCreationParameters) are code-generated from models maintained by service teams themselves. Service model authors often reuse types between different APIs but may choose not to because the APIs offer divergent capabilities (or may in the future). In the case of the APIs you mentioned, CreateTable supports additional features like creating LSIs, configuring DynamoDB Streams, and tagging, whereas ImportTable does not.
Our code generator cannot infer any relationship between the two types based solely on their structure because they may diverge over time or may assign different meaning to identically-named parameters. Given that the Kotlin language itself provides no generalized solution for this (e.g., duck typing, type classes, etc.), I do not believe we can implement this feature at this time.


Expand augur-api to cover more contracts

Our tests talk to the contracts using augur-api but right now augur-api only has the Augur and Universe contracts. The tests can add new contract apis themselves but those should be in augur-api anyway,.

PR #1387 merged


Pager View with reanimated not work

Environment
expo@latest
react-native-pager-view  5.4.9
react-native-reanimated 2.3.1
react-native-gesture-handler 2.1.0
react-native-screens 3.10.1

Description
i am trying to use re-animated component with 'createAnimatedComponent' with hooks useHandler and useEvent.
I hope it goes as expected, but it doesn't seem so

Reproducible Demo
expo snack

Hey @dodicandra
it works like a charm on my phone iOS 16+
https://user-images.githubusercontent.com/360936/199774122-b75fee0c-b54a-499f-baa1-4bf2df4b06e8.MP4
If your problem is solved can you please close the issue?
It sparks joy for maintainers ✨

Environment
expo@latest react-native-pager-view 5.4.9 react-native-reanimated 2.3.1 react-native-gesture-handler 2.1.0 react-native-screens 3.10.1
Description
i am trying to use re-animated component with 'createAnimatedComponent' with hooks useHandler and useEvent. I hope it goes as expected, but it doesn't seem so
Reproducible Demo
expo snack

I inform the RC version it doesn't run well but on the stable version it's fine. so I decided to close this issue


UI - [VAPOR] Contributions to proposals

Do the following calculations in /proposals?status=active

Load the VAPOR of the connected user
Calculate the amount of KOIN that can be allocated with that VAPOR
Use the following function to get the contributions of the user:

const { result: userContributions } = await contract.functions.get_contributions_by_user({
  account: "13e7ugtkg8CQD8JiPgNa6HaZr89xmTiwXn",
  start: 0, // first page
  limit: 20, // proposals per page
  direction: 0,
});

since the contract is not yet ready use this dummy data as response
const userContributions = [
  {
    proposal_id: 17,
    shares: "500000000000",
  },
];

Compute the VAPOR contribution: vapor = (user shares) x (Vapor in the proposal) / (total shares in the proposal)
Compute the KOIN contribution: koin = vapor * total koins in vapor contract / total supply of vapor.
Display the KOIN contribution of this user on each proposal in the list.

Function name is updated to : get_user_contributions
const { result: userContributions } = await contract.functions.get_user_contributions({
  account: "13e7ugtkg8CQD8JiPgNa6HaZr89xmTiwXn",
  start: 0, // first page
  limit: 20, // proposals per page
  direction: 0,
});


Add Home and Default category

This allows the app to be set as the default launcher currently it doesn't prompt for that because that would require more code so you have to set the default in settings. But this makes the app perfect for a dedicated tablet/phone controller.

Thanks for your PR. It's a good idea, but it needs more modifications in order to work correctly:

When app is visible (hass ui or password prompt) and I press back, screen goes black
When device is unlocked using fingerprint, app lock screen appears (it should be unlocked automatically, there is no need to authenticate the user twice).

Yeah there needs to be a refresh page option as well, the pressing back going to a black page is how i am currently refreshing the content.
Didn't run into the app lockscreen because i have it disabled because i use it as my main hub so don't need auth.


fix: update default app.css tailwind syntax to use @tailwind (#3149)

Minor change to switch from older @import 'tailwindcss/... syntax to @tailwind as recommended in Tailwind docs.
This encourages users to avoid a possible cache invalidation issue.
See: https://tailwindcss.com/docs/installation#:~:text=Add the Tailwind,main CSS file.
See: https://github.com/roots/bud/issues/2455
The cache invalidation logic for @tailwind was introduced in Tailwind 3.0.24. Sage's app.css was written originally for Tailwind 2.0.2 on Sage 10.0.0-beta.1

Thank you!


The "Location" Filed Is Not Updated as Introduced

I followed the instruction here to setup the Application Gateway and the DNS record, the Domain the Cookie did change to the custom domain name, instead of the domain of Web App. However, the Location filed in the response didn't change to the custom domain.
After investigation, I found it was due to the coding of the redirection in the Web App that full URL (http://xxxxx.azurewebsite.net) was configured as the target page. So I suggested to highlight here that the update of the "Location" Filed is influenced by the coding too.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aacd2683-3d38-ac23-22bb-fadd39d16dcc
Version Independent ID: 0eef0b80-ee12-958f-cbf3-e35ab8e7e535
Content: Troubleshooting Azure Application Gateway with App Service – Redirection to App Service’s URL
Content Source: articles/application-gateway/troubleshoot-app-service-redirection-app-service-url.md
Service: application-gateway
GitHub Login: @abshamsft
Microsoft Alias: absha

Hi @chenshunshou Thank you for your feedback! We will review and provide an update as appropriate.

@chenshunshou, You can rewrite the location header from the application gateway side to the client using this feature of rewriting. As you mentioned earlier yes coding has an impact on URL redirections where we can overcome that using the above-mentioned URL rewriting technique. I am assigning this issue to the content author to update the document post validation.
@abshamsft, Could you please provide your insights on this?

@chenshunshou We've added the instructions for rewriting the Location header in the response. We'll proceed to close this issue.
#please-close


update

update needed for next release

The conflict relationship does not need to be updated; since KJRContinued provides KJR, it is already considered a conflict:

Thanks for the update!


The sdxl comparison generation is very good. But compared to SD1.5, there is an issue

The three models of SD1.5 have no effect, but instead have deteriorated. I hope they can be improved

Can you provide more detailed information?

Can you provide more detailed information?

Oh, i know the reason. Because resadapter is not training on 256x1024 (1:4) ratio.
Thanks for your test, i will train resadapterv15 for broading ratio.

We have update the latest version of resadapter_v1_sdv15.https://huggingface.co/jiaxiangc/res-adapter/tree/main/resadapter_v1_sd1.5
Now we are training resadapter_v2_sdv15 for broad ratio.


[youtube] Age gated video fail with 404 error

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2021.06.06
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

youtube-dl -v -F https://www.youtube.com/watch?v=XgnwCQzjau8
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'-F', u'https://www.youtube.com/watch?v=XgnwCQzjau8']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.06.06
[debug] Python version 2.7.16 (CPython) - Darwin-20.5.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] XgnwCQzjau8: Downloading webpage
[youtube] XgnwCQzjau8: Refetching age-gated info webpage
WARNING: unable to download video info webpage: HTTP Error 404: Not Found
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/bin/youtube-dl/__main__.py", line 19, in <module>
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 475, in main
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 465, in _real_main
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2069, in download
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 808, in extract_info
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 815, in wrapper
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 836, in __extract_info
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1503, in _real_extract
  File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2644, in compat_parse_qs
  File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2614, in _parse_qsl
AttributeError: 'bool' object has no attribute 'split'

Description

Test link:
https://www.youtube.com/watch?v=XgnwCQzjau8
maybe adding these params:
https://stackoverflow.com/questions/67615278/get-video-info-youtube-endpoint-suddenly-returning-404-not-found/67629882#67629882
here:
https://github.com/ytdl-org/youtube-dl/commit/24297a42efc52862cb9510d32b28efd7faf49af6
helps or at least gives a hint.

Ok ,so I added params below:
'html5': '1',
'c': 'TVHTML5',
'cver': '6.20180913',
Here: https://github.com/ytdl-org/youtube-dl/commit/24297a42efc52862cb9510d32b28efd7faf49af6
and the issue seems to be gone... Not sire how solid of a solution that is..

Ok ,so I added params below:
'html5': '1',
'c': 'TVHTML5',
'cver': '6.20180913',
Here: 24297a4
and the issue seems to be gone... Not sire how solid of a solution that is..

This seems to work for now. But this will break eventually too

Thank you very much!
I have been looking for a solution for hours. How did you find it so fast?
YouTube really seems committed to blocking any third-party tool that alters its restrictions...

Ok ,so I added params below:
'html5': '1',
'c': 'TVHTML5',
'cver': '6.20180913',
Here: 24297a4
and the issue seems to be gone... Not sire how solid of a solution that is..

lol, I found out that this is mimicking TV client like this

UA: Mozilla/5.0 (Linux; U; Android 4.1.1; nl-nl; POV_TV-HDMI-200BT Build/JRO03H) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30
(second image is saying "Log in to Google account" and "To watch this video, age verification is required")

Ok ,so I added params below:
'html5': '1',
'c': 'TVHTML5',
'cver': '6.20180913',
Here: 24297a4
and the issue seems to be gone... Not sire how solid of a solution that is..

lol, I found out that this is mimicking TV client like this

UA: Mozilla/5.0 (Linux; U; Android 4.1.1; nl-nl; POV_TV-HDMI-200BT Build/JRO03H) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30
(second image is saying "Log in to Google account" and "To watch this video, age verification is required")

Is that octopus image exclusive to the Japanese version of YouTube, considering that the Japanese like to give everything a mascot? I haven't seen it on any European or American versions of the site.

@rjdg14

Is that octopus image exclusive to the Japanese version of YouTube, considering that the Japanese like to give everything a mascot? I haven't seen it on any European or American versions of the site.

I don't know. Check it yourself if you wish.

It doesn't work anymore:

@ezhikus thats not even a valid video: https://www.youtube.com/watch?v=XgnwCQzjau8

@89z No, it's recently deleted. It existed as of @ezhikus's commented.


Fork of detectionlab

Hi,
as you can read on the readme detectionlab is not supported anymore by clong.
Therefore I created a fork to support and coordinate further development.
Please find it at https://github.com/DetectionLab/DetectionLab or the respective homepage https://detectionlab.net
There's also a github discussions page available in case you have questions.
Greetings
security-companion

@clong: I have a question. I read on the readme on this repo that DetectionLab is no longer actively being maintained or developed. That's why I made a fork and a new homepage to ensure future development of the project.
But now I saw that you are still merging pull requests and making other commits which confuses me a bit.
Honestly I would prefer not having 2 places where development goes on (this repo and my fork) and 2 homepages because from my point of view it's just double work and confuses users.
So if you decide going on to work on this repo it is fine for me and I can delete again my repo any my homepage.
What do you think?
Greetings

@security-companion I'm not doing any new development, but if I see PRs that will fix bugs, I will check in and merge them from time to time

Honestly I would prefer not having 2 places where development goes on (this repo and my fork) and 2 homepages because from my point of view it's just double work and confuses users.

¯\_(ツ)_/¯ It was your choice to set up the fork and website - please don't try to exert control over what I do with my own project's repo.

view.

Not sure why you got that super positive response above - thanks for trying to keep a good project alive @security-companion - FWIW asking someone to clarify their intention with a project to avoid duplicate work and ultimately benefit the user-base shouldn't cause anyone to get offended or feel controlled - However, there's always someone choosing to find offense where there isn't any. Cheers @security-companion - Would be more than delighted to contribute maintaining a fork or any other way if you end up pursuing that path. Cheers


Patient update fails

Addresses #75 - patient update was failing if the cda_identifier wasn't present, and exceptions with an uploaded archive were showing up as "duplicate file" errors.

'duplicate file' error is no longer an issue, but patient record still fails to update.

SECOND.zip
FIRST.zip

I just tried it and was able to get the import to work (see example record
attached).  Is anyone else able to reproduce?
On Mon, Jun 12, 2017 at 10:43 AM, npm526<EMAIL_ADDRESS>wrote:

'duplicate file' error is no longer an issue, but patient record still
fails to update.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OSEHRA/popHealth/pull/92#issuecomment-307829608, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7FIoPuuVxvEORssgrO7FFVxI5RzTDMks5sDVysgaJpZM4NIQ1g
.


Nonce Support Added

Fix #193 for redux_support branch

@linkRace Can you please review & merge?

@samsel review?
4.x has support for redux. right? or only redux_support branch has this?


Optimize download function

Pass duplicates instantly.

Done https://github.com/LuckyTea/BID/commit/1a8653f92a91aaeb15e4c96e8f9aca192f8d2d73


Trigger stimulus action on other controller

Thanks for your work on this, it looks like it will become a really nice component.
Can I ask if it is possible at the moment to call an action on another stimulus controller when an item is selected from the list? I've tried setting a data attribute directly on the combo box and also via input: ... but neither seems to be setting the action. Maybe that is still in the pipeline. :)
Thanks.

Hey @robingram, thanks!
Yes, that's supported although not documented yet. This should work:
<div data-controller="foo">
  <%= combobox_tag :movie, [options], data: { action: "hw-combobox:selection->foo#doSomething" } %>
</div>

hw-combobox:selection is emitted when the combobox is closed and the selection is finalized.
hw-combobox:preselection is emitted when the active option changes due to navigating with the keyboard or typing in the combobox.
You can use either, but my example above uses hw-combobox:selection
Finally, hw-combobox:removal is emitted in multiselect comboboxes only (not documented yet) when the user removes a selection chip.
Let me know if you run into trouble! Closing for now.

Thanks for the super speedy reply. That's working with hw-combobox:selection. 👍

This is super awesome, thank you so much for the awesome lib. Can this be added to the docs please? It takes a while to find the closed issue and figure it out.


Question about using existing SSH keys

I would like to build a SoftLayer_Virtual_Guest_Template that utilizes existing SSH keys that are already in SoftLayer rather than passing a new one every time. Does the current functionality support this? If so, how should I declare that my new virtual server utilizes the existing SSH key?
Thanks

Yes, I think you'd need to find the ID of the existing SSH key and add the ID to the section that has the array of key IDs.
I'll close this issue but if above does not work please reopen. Best.


Error when using the plugin, Error: RangeError: options.port should be >= 0 and < 65536. Received type number (NaN).

When using the plugin I'm facing an error stating:

Error: RangeError: options.port should be >= 0 and < 65536. Received type number (NaN).

Disabling, or removing, the plugin solves the issue.
Because I couldn't install this plugin via the UI due to some npm-error, I cloned the repository in the plugins folder and built the plugin myself (tried both prod and dev builds).
Steps I have taken:

Navigate to the plugins folder

Perform a git clone https://github.com/GillesZunino/insomnia-plugin-azure-ad-authentication.git

cd .\insomnia-plugin-azure-ad-authentication\

Run npm run build:prod

Start Insomnia client

Reload all plugins (there's only this one)

Configure a request to use the plugin

Invoke it and see the error.

I'm using the Postman callback URL over here because that one is already configured in our App Registration

Re-using the Postman callback URL (https://oauth.pstmn.io/v1/callback or variants) for "Redirect Url" as show above is not currently supported.
We now reject these urls early in the configuration dialog. We also no longer fail with a cryptic exception. The documentation has been updated to indicate that any redirect url against *pstmn.io cannot be used.
I will produce a release in the next few days.

Yes! It is still in dev, not yet released and not ready for consumption. Thank you.


nebirhos zsh-theme hostname is too long

Hello,
It appears for issue #6028 there was a change made to show the full hostname in the prompt.  The hostname for my machine is controlled by my work and is very long.  I think a better option for this prompt would be the short hostname.  This is populated in $SHORT_HOST.  This would solve the issue in #6028 and still work for people that have long full hostnames.
Thanks!

Can you submit a PR?


mikkt space and glTF

This is a placeholder for tracking whether or not mikkt space support in babylonjs makes sense.
See thread:
http://www.html5gamedevs.com/topic/34364-gltf-support-and-mikkt-space/

Reference material:
https://github.com/gltf-rs/mikktspace/tree/master/libmikktspace
Not sure if it make sense to rewrite in typescript, or use emscripten to compile the above for babylon.
https://github.com/kripken/emscripten

Great description of the situation:
https://wiki.blender.org/index.php/Dev:Shading/Tangent_Space_Normal_Maps

Closing as we do not plan to work on it. Please reopen if this needs to be reevaluated

FYI: https://github.com/KhronosGroup/glTF/issues/1252#issuecomment-771358688

There is now a WebAssembly module for MikkTSpace: donmccurdy/mikktspace-wasm: MikkTSpace vertex tangent calculation for JavaScript/TypeScript/Node.js, using Web Assembly. (github.com). It would be good to integrate.

@bghgary do babylonjs shaders make use of the MikkTSpace tangents mentioned above?

If tangents are provided, yes. If not, we use a runtime compatible algorithm.
https://github.com/BabylonJS/Babylon.js/blob/61c912b555c549794d976204975a051c038429d6/packages/dev/core/src/Shaders/ShadersInclude/bumpFragmentMainFunctions.fx#L84-L107


Investigate more accurate integration.

Not sure which one works best for peaking distribution.
http://en.wikipedia.org/wiki/Gaussian_quadrature
http://en.wikipedia.org/wiki/Clenshaw–Curtis_quadrature

This will not be done since the package is now effectively superseded and almost unmaintained. Closing.


Adds additional time data to dump status output

Resolves #999 - Adds the timestamp data to the output for dump status.
The implementation diverges from the update implementation where there is ultimately a ProcessedUpdateResult struct. Only to keep the code changes on the smaller side for dump. Happy to address any feedback or go a different route!

Hello @mitch292!
Thanks for your involvement. This is our fault because we didn't take the time to update the contributing part in the README, but we cannot accept PR on MeiliSearch for the moment (see #1318). Sorry for this!!
The refactor on which we are working is in this repository -> https://github.com/meilisearch/transplant/
So your PR could be useful in this repo 🙂 I totally understand if you don't have the time to do it, but if you are ok I can create an issue on transplant for the same issue as the #999 one.

I'm closing this PR since it will be fixed in transplant repo! Thank @mitch292 for this PR anyway, we are sorry not to be able to merge it!


extracted buildModuleSchema in parsers-common.js

Summary
This PR is a task from #34872

Extract the buildModuleSchema function (Flow, TypeScript)in the parsers-commons.js function. The two functions are almost identical except for the filter(property =>) at the end of the function, which is different based on the language.

Changelog
[Internal] [Changed] - Extract the function isModuleRegistryCall in parsers-common.js
Test Plan
I tested using Jest and Flow commands.

Hi @dakshbhardwaj, thank you for taking this.
Just a question: are you sure you added/committed all the changes? I can see the new function in the parsers-common.js, but I can't see it used, nor the same code removed from the other files.
Could you double check that please? :pray:

Hi @dakshbhardwaj, thank you for taking this.
Just a question: are you sure you added/committed all the changes? I can see the new function in the parsers-common.js, but I can't see it used, nor the same code removed from the other files. Could you double check that please? 🙏

Hi @cipolleschi i haven't removed it from the other files because this pr has dependency from the other tasks as some other functions are also needed to be moved to parsers-common.js so i'll push the code once those pr's are merged

Hey @dakshbhardwaj !
Just heads up, the dependent changes are merged :)

@dakshbhardwaj could you please rebase on top of main, please?

gentle ping to @dakshbhardwaj, are you still interested working on this?

Closing this as the author is not responsive.


Several errors trying Certify 2.0 intro techniques

I've been working my way through a number of the Certify 2.0 features that were described here:
https://research.ifcr.dk/certipy-2-0-bloodhound-new-escalations-shadow-credentials-golden-certificates-and-more-34d1c26f0dc6
I created a simple domain user named john to match your examples but I'm having issues with a few commands:
#1
Bloodhound: I can't see any data from the bloodhound import:
Certipy find<EMAIL_ADDRESS>-bloodhound
[] Finding certificate templates
[] Found 33 certificate templates
[] Finding certificate authorities
[] Found 1 certificate authority
[] Trying to get CA configuration for 'toondom-TOONDOMCA-EXT-CA' via CSRA
[!] Got error while trying to get CA configuration for 'toondom-TOONDOMCA-EXT-CA' via CSRA: CASessionError: code: 0x80070005 - E_ACCESSDENIED - General access denied error.
[] Trying to get CA configuration for 'toondom-TOONDOMCA-EXT-CA' via RRP
[!] Failed to connect to remote registry. Service should be starting now. Trying again...
[] Got CA configuration for 'toondom-TOONDOMCA-EXT-CA'
[] Found 12 enabled certificate templates
[*] Saved BloodHound data to '20220812181400_Certipy.zip'. Drag and drop the file into the BloodHound GUI
The command worked and if I drag and drop the .zip file onto the Bloodhound Windows GUI, I see the import process but no data shows up in the Bloodhound console.
#2
I tried the shadow technique but got this error:
Certipy shadow auto<EMAIL_ADDRESS>-account 'johnpc'
[] Targeting user "'JOHNPC'$"
[] Generating certificate
[] Certificate generated
[] Generating Key Credential
[*] Key Credential generated with DeviceID '2d258854-0eb1-5bae-5020-4384cc4dd67c'
[-] Got error: invalid attribute type msDS-KeyCredentialLink
Any idea why it doesn't like attribute type msDS-KeyCredentialLink?
#3
Certipy req<EMAIL_ADDRESS>-ca "toondom-TOONDOMCA-EXT-CA" -template "Machine"
[] Requesting certificate
[-] Got error while trying to request certificate: code: 0x80094012 - CERTSRV_E_TEMPLATE_DENIED - The permissions on the certificate template do not allow the current user to enroll for this type of certificate.
[] Request ID is 14
Would you like to save the private key? (y/N) n
Why would I get CERTSRV_E_TEMPLATE_DENIED?
#4
In your article about the ESC1 exploit, you have an example command like this:
Certipy req<EMAIL_ADDRESS>-ca "toondom-TOONDOMCA-EXT-CA" -template "ESC1" -alt<EMAIL_ADDRESS>But ESC1 is not a valid template so I'm assuming it is a vulnerable template that was discovered by Bloodhound and I would use that name instead.  How can I use Certify to directly show me any vulnerable templates?  I found an old blog by someone that used the find -vulnerable command but that does not seem to be valid in Certify 2.0.
Sorry about so many questions in 1 issue.
Thanks,
Rick

Hello could I get some help with these issues?
Thank you.

Hello @rick-engle
I suggest reading the white paper or blog post "Certified Pre-Owned" mentioned in my blog post as two of these errors (#3 and #4) are related to how AS CS works. For #3, the user John is simply not allowed to enroll in the "Machine" template. Users are by default allowed to enroll in the "User" template, whereas domain computers are allowed to enroll in the "Machine" template. For #4, the ESC1 template does not exist by default, but is a result of a misconfiguration. This is all explained in the aforementioned white paper. For #1, you should do some queries in order to get the result. You can check the custom queries in my repo. For #2, I am not sure of why the error happens, but it could be that the active directory schema does not support this attribute. I haven't seen it before though.


Change the way flying unit move.

It's awful

On direction change... while moving on a strait line it is ok :D


Text drop-down appears below stack of blocks

See:

Only appears to affect hat blocks, which is strange.


Add workflows to sign container images and helm charts

What does this Pull Request accomplish?
Adds new reusable workflows and documentation to sign container images and helm charts published to Artifactory.
Why should this Pull Request be merged?
We need these features to enable delivering signed containers and helm charts to our customers.  These workflows will enable adding signing to many different repos without having to reimplement the logic.
What testing has been done?
These reusable workflows have been tested from another repo.  See the workflow run here:
https://github.com/neilvana/signing-dev/actions/runs/1925257319

We should squash this pull request.  It has a lot of noise.


Auto-troubleshooting on wrong instance settings

when bad jvm opts are specified e.g bad go tpl delimiter is used then the only way to figure out why AEM is not starting / is not reachable so long it to preview stdout.log

GAP is smarter now as it is after some timeout printing last lines of that log file automatically. AEMC could too.

it could also be a part of timeout checker in AEMC after some refactoring
https://github.com/wttech/gradle-aem-plugin/blob/main/src/main/kotlin/com/cognifide/gradle/aem/common/instance/check/TimeoutCheck.kt#L31


Drop support for Node.js v0.10, add support for v6 LTS

According to the Node.js Foundation Official LTS Schedule, tomorrow (1st October) is the end of support for Node.js v0.10 and the start of LTS support for v6.
In accordance with that schedule and our own commitment to the Node.js LTS schedule, we will be dropping support for Node v0.10 and adding support for v6.
We are currently in the process of releasing Ghost 0.11.1, which is a maintenance release with bug fixes and dependency updates. This will be the final version which officially supports Node.js v0.10.
Ghost 0.11.2 will be released very quickly after 0.11.2, with no changes other than the officially supported Node.js versions being swapped.
Ghost 0.11.2 will be released as soon as the following conditions are met:

[x] We've shipped 0.11.1
[ ] The Node Foundation have announced EOL for v0.10 and the new v6 LTS version number
[ ] I have the time to create & publish the release (it is happening at the weekend after all)

Note: the EOL for Node 0.10 is now happening on the 31st, instead of the 1st October. LTS for v6 will be declared somewhere mid-October. We'll update our plan as and when these announcements come, based on how close together they're going to be :)

Node v6 should become LTS on the 18th fwiw:
https://twitter.com/thealphanerd/status/786106360677142528

v6 became LTS this 2016-10-18 https://nodejs.org/en/blog/vulnerability/october-2016-security-releases/

I'm well aware. The LTS release will happen asap.

FYI, Node v6 support was merged in this week, however a bug deep on our Ghost-Admin dependency tree made releasing tricky. That is now resolved, however with Node v0.10 EOL happening early next week, I'm holding off from releasing until that has happened now.
Better news: we're vastly improving our internal release processes for Ghost v1.0, with the intention of releasing far more regularly than we ever have with pre 1.0 Ghost.

Ghost's Node version support has been updated in 0.11.3, and the supported version guide has been updated to match.


Variables in dotenv-filename

Scenario: I have justfile which wants to use a specific env file. This name is also been used few times in the recipes, so I want to put it into variable.
Unfortunately, currently it's impossible to use variable names in dotenv-filename directive.
I understand that this creates some kind of circular dependency, but having ability to use variable in both dotenv-filename and in other places made is really natural. May be, it's possible to forbid redefinition of variables used to load dotenv-filename?
Alternatively, dotenv-filename can be processed at a specific moment, may be with a different directive compare to set. Or it can be a command for recipe to move it to runtime...

Variables can depend on dotenv variables, regardless of whether they're redefined, since they can use env variables, so I don't think this is possible in general. I'll leave it open though, in case anyone has any clever ideas.

Yes, please! It will solve my usecase, and it sounds ..  sound.

This would also be very helpful to us. I particularly like the get_setting approach suggested above.
To clarify our use case, we use just in a repo which records past and future on-chain governance actions to be taken on the Optimism rollup network. These actions need to be signed by multisig participants, and we use just to define the commands the signers need to run.
In the root of the repo we have a couple justfiles, and in subdirs we have a structure like:
/path/to/action/
├── README.md   # describes the action
├── .env        # contains action specific variables that all signers need (ie. multisig contract nonce)
└── input.json  # defines the transactions to sign

The just recipe needs to be able to find both the .env file and the input.json file, but there isn't a straightforward way AFAICT to pass in path/to/action and use that to both:

call dotenv-filename at the global level of the justfile
pass path/to/action to the just recipe itself.

Aside from get_setting another nice syntax would be to ability to set dotenv-filename within a recipe:
foo dirpath:
	dotenv-filename(join(dirpath,".env")
	input_path=join(dirpath,"input.json")
	echo "now we are going to sign the tx in ${input_path}"

Great thought, @laniakea64!
I think this should be pretty simple. I'd just make it setting(name). In particular, name can be a keyword token. If anyone wants to take a crack at this, feel free!

I also want to use set dotenv-filename dynamically. However, I want to pick from different env files (containing different passwords for example).
I don't see a reason why
set doting-filename := "$ENV_FILE"

should not work or be counterintuitive. In this case, strings need to be parsed, but the grammar doesn't change.
The slightly more convenient case
set doting-filename := env('ENV_FILE', '.env')

would require a grammar extensions for setting to sth. like this:
setting       : ...
              | 'dotenv-filename' ':=' value

The invocation would could look like this: ENV_FILE='.env.prod' just a/b

@casey Is there a good reason to limit settings to strings?

@jneuendorf-i4h If you're setting it via environment variable, can you use shell-expanded string?
set dotenv-filename := x'${ENV_FILE:-.env}'

Thanks a lot, your suggestion works! 🙏


[feature] Start migration to TypeScript

Motivation and Context
Depends on #411. Don't merge without it
Migrates index.js to typescript and update circleci to check types as well.
How Has This Been Tested
npm test and npm run check_types
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Closing this stale PR.


Define Vulnerability Report Process

From Reporting section of https://bestpractices.coreinfrastructure.org/en/projects/5719

The project MUST publish the process for reporting vulnerabilities on the project site.
If private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private.
The project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days.

Additional information from the badge process:
_A clearly designated mailing address on https://PROJECTSITE/security, often in the form<EMAIL_ADDRESS>This MAY be the same as its bug reporting process. Vulnerability reports MAY always be public, but many projects have a private vulnerability reporting mechanism.
Examples [of private reporting] include a private defect report submitted on the web using HTTPS (TLS) or an email encrypted using OpenPGP._

@dcmiddle is this issue still relevant or can be closed?
If it's still relevant to what release do you think we should map it to (mid-November, end-December, mid-February etc...)?

@dcmiddle do you think this can converge for the V0.3.0 release?

We need 2 things: A reporting mechanism and a SECURITY.md file.
The mechanism can be an email address or private github issues.
If we opt for an email address then I recommend that we populate the security email list as an alias of the Steering Committee list.
1. That list is actively maintained
2. Those individuals should know who to contact to address a security issue
The other option is private github issues.
Then we just need to document which of those paths in our SECURITY.md file.
I recommend we enable private issues. We can do that on all repos and then in the security.md clarify that if you don't know which repo to use pick our main repo.

There was a suggestion about adding these people as part of the security reporting.
I think a CNCF mailing list is a bit of a non-starter. The mailing list we already have isn't up-to-date and we can't manage it ourselves. We could create a new mailing list somewhere else.
I think private issues are a better approach. Users might not be as familiar with this, but the security tab is pretty easy to find in a repo. Private issues are only available at the repository level. Issues are visible to the maintainers of each repo as well as an organization-wide security team. This seems pretty good. I will experiment with the feature a little bit. We shoudl also start drafting a security.md that we can put in each repo.

start drafting a security.md that we can put in each repo.

I've started looking into what's appropriate given our maturity and adoption level. I'll plan to put up a draft PR on the .github repo that will then automagically appear in all the repos.

Ok, we can turn on reporting independently from making security.md On Thursday I will ask if there are any objections to turning on the reporting for each repo.

Sounds great. We will want maintainers familiar with private issues before we advertise them in the security.md.


Validate client secret for confidential clients

As discussed in this thread https://github.com/aliev/aioauth/discussions/91, the example app currently doesn't validate client secrets. This adds validation for client secrets as well as some tests to ensure the functionality works. The database schema was also changed to allow null client secrets for public non-confidential clients.
Before adding validation:
FAILED tests/test_oauth2.py::test_authorization_code_no_secret - AssertionError: no client secret for a confidential client should be rejected
FAILED tests/test_oauth2.py::test_authorization_code_wrong_secret - AssertionError: wrong client secret for a confidential client should be rejected

Results (28.04s):
       6 passed
       2 failed
         - tests/test_oauth2.py:88 test_authorization_code_no_secret
         - tests/test_oauth2.py:109 test_authorization_code_wrong_secret

After adding validation:
Results (26.11s):
       8 passed

Hey, @shawnz. It looks good. Should I merge it?

Sure! Thanks for your time with this


Files not mount at startup on windows

When I click on the virtual drive, it seem it's unmounted.
Keybase correctly launch at startup.
If I quit and relaunch the app, all works good, until next computer restart.
Keybase GUI Version: 5.7.0-20210622155205+e3826b703a

Windows problem, report it on Github
On Sat, 31 Jul 2021, 19:46 lcaminon, @.***> wrote:

When I click on the virtual drive, it seem it's unmounted.
Keybase correctly launch at startup.
If I quit and relaunch the app, all works good, until next computer
restart.
Keybase GUI Version: 5.7.0-20210622155205+e3826b703a
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/24583, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOP7L25NM35TD4K4K4JAZ3T2PWAXANCNFSM5BJ7YH3A
.


Only see Twilio numbers for login used

Is your feature request related to a problem? Please describe.
Yes/No, Keep other admins from seeing all numbers associated with my Twilio account.
Describe the solution you'd like
I have multiple yap instances setup for Regions, ASC's and Metros. I would like for the logged in user only see their Twilio number information and not all of the numbers I have for my Twilio account.
Describe alternatives you've considered
Open to suggestions.

Here is what every user sees.

I've thought about this as well and would also like this feature. Not sure how to do it as there is no way of knowing out service body is tied to what number with the configuration and login level that  I know of.

Yea it is helpful as an admin to easily see but you can also just check twilio and see too.

I'm good with removing it.

removed in master


09/12/2018 17:45 : Create Pull Request for branch master -> prTesting1_2018091217

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

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


Minor improvements

Hello,
Great work! I'll let myself to make a PR with minor changes:

Fixed Readme - it was still pointing to the forked namespace
Documentation improvements
Making slf4j and timber dependencies transitive, like Readme says
Adding you as an author :)

Thank you very much!


Transition SelectTagHelper and OptionTagHelper to use context.Items.

Added functional tests to validate data created from a SelectTagHelper does not impact following <select> tags.

#3347

/cc @dougbu

:watch:

Updated.

:watch:

Updated.

:shipit: but may want to wait for Coherence to catch up since we can't confirm MVC builds at the moment.


Adding phoneNumberTag formatting to columns block

Enabling phone number pulling from sales phone number sheet for columns block.
Resolves: MWPW-137207
Test URLs:

Before: https://main--express--adobecom.hlx.page/express/pricing/business?lighthouse=on
After: https://mwpw-137207--express--adobecom.hlx.page/express/pricing/business?lighthouse=on

Codecov Report

Merging #318 (dd0cd3a) into stage (a21bcdb) will decrease coverage by 0.17%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##            stage     #318      +/-   ##
==========================================
- Coverage   50.95%   50.79%   -0.17%
==========================================
  Files          33       33
  Lines       10005    10011       +6
==========================================
- Hits         5098     5085      -13
- Misses       4907     4926      +19

Files
Coverage Δ

express/blocks/columns/columns.js
36.11% <57.14%> (+0.23%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Spine-TS] Group Container and Root Bone Position Problem

Hey guys,
Some things I noticed about the new Spine-TS:
When you put the Spine object inside a group, scaling a group does not affect the Spine object properly. In the old phaser-spine, you can scale the container group using Phaser, and the Spine object will scale accordingly. It doesn't happen here. It seems you need to scale the Spine object itself.
How the object is placed onto the stage is rather wonky and unpredictable. It doesn't seem to honor the Root bone's x and y coordinates nor Spine's 0,0 world coordinates. It seems to be somewhere on the top and left, maybe treating the Spine object as an image and laying it down like an image, where the 0,0 is the top left hand corner.

Ok, I tried placing different sized animations in a group, and the 0,0 point is dependent on the size and is somewhere the top left of the entire animation body (is it treating it like an image?) . The centerX and centerY properties change. If the 0,0 position in spine equals the 0,0 world position of the Spine editor like in the old version, that would make things more predictable, but since it's always somewhere on the top left, this makes it unpredictable to work with.

Based on my experiments, it seems that the origin/anchor position of the Spine animation is dependent on the width/height of it. So take the following for example, I have 2 animations, 1 that's full size, and the other shrunk to 20% (by importing a new Spine Data, altering the scale, and using image assets that's the same as the scale). I grabbed the Spine object's width and height, and positioned the root bone until it very closely matches the parent group's x and y points (where scaling the spine object will be very close to using the root bone's position as the anchor of the scaling.)
100% Size:
Spine Width (In Px, Phaser): 1830
Spine Height (In Px, Phaser): 1804
Approx. center where the root has to be in:
x: -700
y: 1242
20% Size:
Spine Width (In Px, Phaser): 366
Spine Height (In Px, Phaser): 361
Approx. center where the root has to be in:
x: -140
y: 248
I don't know why it's like this, but I'm trying to find some meaning into these numbers. Maybe someone can figure this out one?

Ok, when I set the anchor of the Spine object to (0.5, 0.5), it helps.  I need to move around the skeleton's x and y (not bone[0]'s x and y) for me to be able to adjust the spine object's position so it can scale properly. If I cancel out root's X and Y offset by moving it to the opposite direction, it should move it down to the 0,0 position in Spine and in Phaser. I usually have my root on the upper right quadrant in the editor. If I do this, it seems to move X properly, but the Y, it can't figure out. It's always above the root! In other words, the root is always below it, when it's supposed to be centered already.

Another observation between WebGL and Canvas. In WebGL, to get the same result, the Y needs to be negative. In the above example, if Y was set to 2000px, this needs to be -2000px in WebGL.

@AleBles - Do you see this problem on your end? This thing is making Spine-TS unusable and I can't find a fix for it :(

I'm actually working on it inbetween :p

Yeah, I'm just seeing whether it's just me or it's really a problem others can see too.

Just to make sure we implement it correct: should the position you put down in Phaser always be the spot where the rootbone is located?
Then as a second question, how should we handle anchor's then?
In order for Phaser anchor's to work correctly you'd expect this lib to ignore the rootbone and just use the Phaser point as the top-left corner of the image.
Toughts @shibekin69 ?

Yes on the first question.
Hmm.. Is there a way to make it work both ways so that for 1.) those who want to use the root bone as the center of the spine object, and 2.) those who want to just use the top left of the image can use the plugin according to their preference?
Personally, I'd prefer to use the root bone as the center of the spine object with anchor 0.5, 0.5 so that it's predictable when I spawn it on screen and when I do transforms on it. Here's an idea, how about being able to initialize the anchor of the root when spawning a new spine object with 0.5, 0.5 as the default?
Something like this:
game.load.spine('spineboy', '/path/to/spineboy.json', {
  x: 100, // x position of root on the screen
  y: 100,  // y position of root on the screen
  anchorx: 0.5, //anchor x of root
  anchory: 0.5 //anchor y of root
})

Then just be able to change/tween the x, y, anchorx, and anchory any time after initialization.
The ability to change the anchor x and y of the root will let you change the way you scale the spine object. So for some games, like side scrollers (ex: contra), this might be set to where the feet's touching the ground (0.5, 1) and scaling it will make it grow upward and not clip the floor. Others who make maybe top down shooters, flying monsters, or other kinds of stuff, use 0.5, 0.5 or some other arbitrary number (like myself) to have an even scaling or some kind of scaling specific to their needs.
It's easier to use the root bone as the spawn point in phaser since it's very easy to also set it in the spine editor visually no? Doing invisible guess work with phaser was quite a pain.

We could go for a simple boolean or such where the bound position can be changed on the fly, maybe even generic plugin setting?

Bound position?
So in the mode where the root position is not going to be treated as the center of the spine object, the position set in phaser will be the 0,0 origin shown in the spine editor? I think this is how the current phaser-spine worked no?

That's what I meant but after discussing with our artist am leaning more towards a solution where anchor and rootbone are the same thing.
So if you create a spine with your root bone in the death center if the animation, this will also be reflected towards the anchor (will be set to 0,5; 0,5). The moment you adjust the anchor we'll ignore the position of the rootbone and just anchor it according to regular sprite behaviour.
This means that the rootbone only dictates the default position of the anchor point and you're freely to adjust it anyway you like.
Example; a spine animation that is 200 wide and 400 heigh, with a rootbone positioned slightly above the bottom-middle will load up with an initial anchor of (0.5; 0.9) (ofcourse exactly calculated based on the spoine dimensions).

Ah, that makes sense. Can you have a function that resets the anchor to the
root bone's position?
On Aug 29, 2017 8:58 PM, "Ale Bles"<EMAIL_ADDRESS>wrote:

That's what I meant but after discussing with our artist am leaning more
towards a solution where anchor and rootbone are the same thing.
So if you create a spine with your root bone in the death center if the
animation, this will also be reflected towards the anchor (will be set to
0,5; 0,5). The moment you adjust the anchor we'll ignore the position of
the rootbone and just anchor it according to regular sprite behaviour.
This means that the rootbone only dictates the default position of the
anchor point and you're freely to adjust it anyway you like.
Example; a spine animation that is 200 wide and 400 heigh, with a rootbone
positioned slightly above the bottom-middle will load up with an initial
anchor of (0.5; 0.9) (ofcourse exactly calculated based on the spoine
dimensions).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/orange-games/phaser-spine/issues/72#issuecomment-325655565,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL7YA9To3_BNrbADaEz9O8J6gjvThxGrks5sdAr_gaJpZM4O8WVo
.

So Canvas rendering should be good now. Moving on to WebGL ;x

Ok, I'm testing out the canvas version. Moving the group container where it's in doesn't move the spine object. So if you do this:
spineContainerGroup.x = 200  <-- does not work
spineContainerGroup.children[0] = 50  <-- works
I tried to make x, y, centerX, and centerY  properties start with 0 and it as it is. It's still all over the place. Hmm. I'm trying to make the root bone align with my spineContainerGroup's 0,0.

Btw, I deal with large spine animations, spine width and heights that's anywhere between 2000 x 2000 to 3000 x 3000. So there might be some weird problems that only appear when offsets are exaggerated because of this?

This is probably related to the group.x and group.y not working right now with the spine-ts-position WIP build, I'm using the Juicy screen shake plugin. It doesn't shake the Spine objects along with the other stuff on screen.

I've been playing around with different spine objects, and there's a weird x offset if there's horizontal white space from the root bone to the edge of your spine's images. Please see pic:

Here are my observations for the other quadrants. Just an FYI. The most important I guess might be the upper right one, since that's where the PSD to Spine export script places the output.

Pfff this is going in baby steps xD, Should be ok now for the Y axis, on to X ;x

Proposed fix whilst keeping the adjustable anchor here:
https://github.com/orange-games/phaser-spine/commit/6241a742748a9ace3fa4446efe8f326a9b2dc0e4#commitcomment-24040207

Hi,
Is this fixed? if yes then in which branch?

No idea, I'm confused myself lol

I had a similar problem when I attached a hitbox to a brush bone and the Y value was mirrored. I think that spine can solve this problem, but I don't know how yet
// update method
const hitboxCoords = { x: leftArm.worldX, y: leftArm.worldY * -1 + this.game.canvas.height - 10 };
this.boy.physicsBody.position.copy(hitboxCoords);


Example for get_file_to_stream is not working, with open returns something different from IOBase

In this section
https://docs.microsoft.com/en-us/azure/storage/files/storage-python-how-to-use-file-storage#get-file-from-share-snapshot
the expected data type for stream= should be IOBase, however the 'wb' mode causes the stream to be BinaryIO, how do we change the mode so that we can get the expected IOBase stream

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d143392d-fe64-ab13-cb20-2f97a2baae7d
Version Independent ID: 4feca477-11fa-3403-3a02-344b35361f4e
Content: Develop for Azure Files with Python
Content Source: articles/storage/files/storage-python-how-to-use-file-storage.md
Service: storage
Sub-service: files
GitHub Login: @wmgries
Microsoft Alias: tamram

@saulcruz, Thanks for the Comment. We are actively investigating and will get back to you soon.

@saulcruz I'd recommend checking the following documentation: https://docs.python.org/3/library/io.html#io.BufferedIOBase
It seems that it could work when using the 'w' only, as an example from python's above documentation: ```
with open('spam.txt', 'w') as file:
file.write('Spam and eggs!')
I didn't see a specific option in the storage SDK fro this option. Let me know if this helps.

Thanks,
Adam

@saulcruz, Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion


New Organization: Hack for LA's Sandbox

A new organization, Hack for LA's Sandbox, has been submitted.
Please visit https://api.civictechindex.org/admin/data/organization/1102/change/ to review and approve it.

This issue can be revised to be a testing issue for people automating the new org approval process.  the HfLA sandbox is actually part of Hack for LA, but we use it to test things, because its both is its own github org and it has repos with various levels of permissions.


#4314 Height issue in create, teleport, transform , transfer

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[x] Refactoring

Context

[x] Closes #4314
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address:
Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

legit, wfm
pay 30

😍 Perfect, I’ve sent the payout
💵 $30 @ 23.8 USD/KSM ~ 1.261 $KSM
🧗 EzGc4s9PgCPx1YnF3fqzhLzVHpHMTL4LWPScwpDrR8JKgSU
🔗 0xed9ad3c80918d0f2e4db7922a9da04713de68f5edcdfe67765a7f880d204f7ab
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Iron Gods:  Part 1:  Garmen Ulreth, Khonnir Baine, and Sanvil Trett import with formula errors.

These Iron Gods AP, part 1, NPCs import with formula errors.

Read the known quirks.  As of now, all class HP is imported as blank, throwing the error, you need to go into classes and change it.  this will occur with everything with class levels until it is fixed.


Create Java FlatMap example

Add an example for Java FlatMap UDFs similar to Java Map UDFs.

[ ] Should show how to return zero or more results.
[ ] Should show how to retain state across invocations.

Added example in branch https://github.com/nebulastream/nebulastream-tutorial/tree/23-java-flatmap-udfs, however it reads the Java client dependency from the local Maven repository.


Bigtable emulator does not support ARM

It looks the the emulator only works on x64 architectures for Linux, OSX, and Windows.

Memo for the error
~/suztomo/java-bigtable/google-cloud-bigtable-emulator$ mvn test -DtrimStackTrace=false  -Dtest=com.google.cloud.bigtable.emulator.v2.EmulatorTest

...
INFO] Running com.google.cloud.bigtable.emulator.v2.EmulatorTest
[ERROR] Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.042 s <<< FAILURE! - in com.google.cloud.bigtable.emulator.v2.EmulatorTest
[ERROR] com.google.cloud.bigtable.emulator.v2.EmulatorTest.testDataClient  Time elapsed: 0.016 s  <<< ERROR!
java.lang.UnsupportedOperationException: Unsupported architecture: aarch64
	at com.google.cloud.bigtable.emulator.v2.Emulator.getBundledResourcePath(Emulator.java:236)
	at com.google.cloud.bigtable.emulator.v2.Emulator.createBundled(Emulator.java:65)
	at com.google.cloud.bigtable.emulator.v2.EmulatorTest.setUp(EmulatorTest.java:49)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...

From Emulator.java:
    String unformattedArch = System.getProperty("os.arch");
    String arch;

    switch (unformattedArch) {
      case "x86":
        arch = "x86";
        break;
      case "x86_64":
      case "amd64":
        arch = "x86_64";
        break;
      default:
        throw new UnsupportedOperationException("Unsupported architecture: " + unformattedArch);
    }

    return String.format(
        "/gcloud/bigtable-%s-%s/platform/bigtable-emulator/cbtemulator%s", os, arch, suffix);

We need to start publishing aarch64 to gcloud sdk and then we can update this wrapper

Is the publishing on the horizon? <3

Any update and temproray solutions for this?
This is what I see if I try to run gcloud beta emulators bigtable start
WARNING: The ARM versions of the components [bigtable] are not available yet. To download and execute the x86_64 version of the components, please install Rosetta 2 first by running the command: softwareupdate --install-rosetta.
ERROR: (gcloud.beta.emulators.bigtable.start) The following components are unknown [bigtable].

Any updates on this? Is there a plan to release an ARM-compatible emulator? Any timelines?
Shopify is moving all of its engineers to Apple M1 laptops and this is blocking several repositories from being compatible with the ARM architecture.

Hi @liufuyang and @alejandrolujan, we can confirm that the emulator update for ARM64 (macOS and Linux) is complete, and should be included in a gcloud SDK release happening soon (currently I'd expect this to release in mid-December).
You can follow the Cloud SDK release notes here, and the ARM emulator update will be noted there once included in the release:
https://cloud.google.com/sdk/docs/release-notes
As a workaround I believe It's possible to manually build the emulator (it's OSS) with a golang SDK and then put the binary in the right place but I have not tried it - though since the emulator is releasing shortly you may just want to wait for it rather than trying such workarounds?

Hey @rameshdharan, thanks for the update! I assume this library will be updated at the same time? We don't use the SDK, but this library directly.

@sap1ens yes, thanks for mentioning that - I believe we will still need to (trivially) update this library shortly thereafter; specifically AIUI the google-cloud-bigtable-emulator's pom.xml will need to include bigtable-darwin-arm and bigtable-linux-arm in the <componentNames> section, and that will start working once the components are released (via the Cloud SDK release).

Confirming that it looks like ARM64 support was added in the emulator in late 2021: https://cloud.google.com/sdk/docs/release-notes#36700_2021-12-14 so this should be unblocked now.

Seems like it was fixed? https://github.com/googleapis/java-bigtable/pull/1094


[Feature]

Is your feature request related to a problem? Please describe.

Describe the feature you'd like

Background transparency blur
Additional context
The Transparency Feature can't blur the background right now, wich makes Discord fit in less with the other transparent and blurred applications I use

You can use CSS for that, getting the lowest class and then adding blur to it.

You can use CSS for that, getting the lowest class and then adding blur to it.

How would I do this ? I don't work much with CSS and didn't find something about a lowest class

How would I do this ? I don't work much with CSS and didn't find something about a lowest class

Use a 3rd party alternative like Glasscord.

Use a 3rd party alternative like Glasscord.


Add a sorting mechanism for fields

Currently the non-determinism of Python dict traversal shuffles the fields of e.g. an object instance around a lot. This is not desirable for a UI. Should double check how other form generators from jsonschema handle the issue.

I had a look at what JS form generators do to solve this issue and there seems to be two approaches:

https://github.com/mirshahreza/json-editor documents the non-determinism. In fact, you seem to have de facto (in the sense of not guaranteed by any standard, but happens to be true almost always) input order preservation in JavaScript, which makes this a good enough solution.
https://github.com/json-editor/json-editor introduces a new field into jsonschema (here called propertyOrder) that is used as a sorting criterion.
https://jsonforms.io/ defines a separate ui-schema that contains data only relevant for the form generation process.


add mocha compilers option to transpile es2015

I have a same issue as mentioned in #5 .
I think this issue will be fixed if this plugin passes compiler-option to mocha :)

@laardee I verified its functionality by running following command in my serverless project:
sls invoke test --compilers js:babel-register
You have to install these dependencies if you try that.

babel-register
babel-preset-es2015

and add this to package.json
"babel": {
  "presets": [
    "es2015"
  ]
}

Please point my mistakes out above if any, cause I'm just a beginner in any of node.js, babel or serverless...

@ryof would the project be something like this https://github.com/SC5/serverless-mocha-plugin/tree/babel-tests/test/test-service-node6.10-babel? I made that integration test for testing this feature. You can rebase it to your fork, it is in the 'babel-tests' branch. After rebase you can run only that test with mocha test/integration6.10-babel.js -t 10000
The test contains test and function templates that have some ES2015 features used. It first creates a test, then a function with test and then runs the tests.

@laardee could you please review my changes again? :)

Oh, definitely, I try to review the changes today. Sorry about that.

Is it possible to write the tests in TypeScript? Thanks

Is there a way to configure a default value for the --compilers flag? I'd really prefer to just run sls invoke test and not sls invoke test --compilers js:babel-core/register


disable virtual env prompt

Revert change to disable pyenv virtual env prompt

cc @krokrob isn't it a problem for the Data setup 🤔 ?

@ssaunier no, it was disabled before. I re-enabled it by mistake during my refactoring of the setup. That's what we want for the data setup. For the web setup, it's useless.
Message from a former data alumni:

Perfect, thanks for the additional info! 🙏 🙏 🙏


write to buffer first as much as possible

In original code, if (mBuffer.position() + len >= mUserConf.FILE_BUFFER_BYTES), then current buffer to write will always be written to file since
if (len > 0) {         appendCurrentBuffer(b, off, len);       } will always hold, otherwise, IndexOutOfBoundsException will be thrown earlier.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2651/
Test PASSed.