And "BRAVE NEW WORLD" text contain

B
We define an electronic coin as a chain of digital signatures. Each owner transfers the coin to the next by digitally signing
R
a hash of the previous transaction and the public key of the next owner and adding these to the end of the coin.
A
A payee can verify the signatures to verify the chain of ownership.
V
The problem of course is the payee can't verify that one of the owners did not double-spend
the coin.
E
A common solution is to introduce a trusted central authority, or mint, that checks every transaction for double spending
N
After each transaction, the coin must be returned to the mint to
E
issue a new coin, and only coins issued directly from the mint are trusted not to be double-spent.
W
The problem with this solution is that the fate of the entire money system depends on thecompany running the mint,
W
with every transaction having to go through them, just like a bank
O
We need a way for the payee to know that the previous owners did not sign any earlier transactions.
R
For our purposes, the earliest transaction is the one that counts
L
so we don't care about later attempts to double-spend
D
The only way to confirm the absence of a transaction is to
be aware of all transactions.

This has already added to the repository. I'm closing this issue.
https://github.com/AlberTajuelo/bitcoin-0.2-image-puzzle?tab=readme-ov-file#14-welcome-to-the-brave-new-world


Fix bugs found in publish after 1.112 release

These are just the ones I found when trying to run ppm publish patch, but I'm sure there are other bugs. The PPM rewrite was gigantic.

Added some tests. I don't love them — they construct a false reality! — but they're better than the nothing that we had.

I have catch the same bug

These new tests pass locally for me. I'll get around to fixing them.

OK, found the problem with the tests. CI is good. This one is definitely a candidate for “squash and merge.”

Do we need a 1.112.1 for this?

Yes. We should test other aspects of ppm to see if other bugfixes can be addressed in a patch release, but so far the only bugs reported are with publishing.

Okay, I saved a copy of the original branch at https://github.com/DeeDeeG/ppm/tree/bug-fixes-original, for reference.

Oh, actually... Hmm. I think I accidentally bypassed the branch protection rules (that I didn't recall we had set up) with admin powers.

Manually merged via commit https://github.com/pulsar-edit/ppm/commit/f660a7a70d9ce0b7b5f7c0fe1e2af6890af205fa (a fake-GitHub-merge-commit-looking actual-merge-commit that I prepared on the CLI).

So, if you prefer the PR to look purple and say "merged" I'll back out the manual merge and do it via the GUI here, but otherwise this'll be red and "closed", but the changes are in master branch at the moment one way or the other.

@DeeDeeG For tracking and changelog reasons I'd say lets properly merge this one, but at the end of the day, as long as we remember the changes are in here, I suppose it doesn't matter too much

CI passed with my rebased commits (as they should, I didn't change any code at all), and I can confirm the "diff" between the original and the rebased version is none, only thing I did was the cleaner commit history.
Finally merging. Thanks much for the fix and added tests!


[Bug] Move line up in folded code

VSCode Version: 1.9.1
OS Version: Win 10

Steps to Reproduce:

Fold a part of code and add a line after this folded part.
Try to move up this line.
The line to move up will be changed with the first line of the folded part of code.

@Nimzozo Can you please attach a small code that shows the issue. Also describe what you think the expected result should be.
I tried this and see that the line gets moved up one line. Then the folding regions are reevaluated. Folding regions are based on the indentations, so either the moved up line likely becomes the last line of the folded range, or goes inside the folded range.
So from how I see it is is all as expected.

Closing as more information is needed.

@aeschli I'm sorry, I wasn't very active on Github lately. I admit I can't really reproduce or remember the exact way this bug happened.
Also I'm now using VSCode latest version, so this issue might have been corrected.


Slice args for iterators

It seems convenient to take optional Array.slice-like arguments to the iterators, so you can iterate over just part of a list.
Possible apps:

Render only the part of a list that is scrolled into view.

Optimizations for formattedSlices when applied to a small list (suggested change, list with many tombstone marks).

Find all formats in a particular slice so you can overwrite all of them, clearing the format.

[ ] Formatting.formattedSpans

[ ] Formatting.formattedSlices

[ ] RichList.formattedValues

[ ] RichList.entries

Looks like this is need in list-demos Prosemirror binding: get the formattedText() form of a single block, to create a new ProseMirror node for that block.


Handlers get message only the first time

I'm trying to use mbassador in a Play based application that publish messages when certain routes are executed. When I start my application and visit the route that emits messages, handlers receive the message. But if I do it again, handlers won't get any message.
Looking through the documentation, I see this

The basic contract of the bus is that it will deliver a specific message exactly once to each of the subscribed message handlers.

But the second time I visit the route, a new message is created with a different message UUID, so it should send the message to the handlers. Am I missing something here?

Could you please post SSCCE?

I assume you have weak references to your listeners. They have most likely
been GC'ed.
2015-11-08 12:19 GMT+01:00 Jose Armesto<EMAIL_ADDRESS>
I'm trying to use mbassador in a Play based application that publish
messages when certain routes are executed. When I start my application and
visit the route that emits messages, handlers receive the message. But if I
do it again, handlers won't get any message.
Looking through the documentation, I see this
The basic contract of the bus is that it will deliver a specific message
exactly once to each of the subscribed message handlers.
But the second time I visit the route, a new message is created with a
different message UUID, so it should send the message to the handlers. Am I
missing something here?
—
Reply to this email directly or view it on GitHub
https://github.com/bennidi/mbassador/issues/128.

Ok, thanks


Updated HMAC Key for 4.55.1

Also the tests must be broken, because getting post details works, but fails in Travis.


Fatal Error Impossible to create your administrator account. Please, check your database credentials.

On setup page, when I've filled out everything and click Launch Install, it gives me the following error:

Fatal Error Impossible to create your administrator account. Please, check your database credentials.

The credentials are fine, and it even creates the tables in the database (all of which are empty)
Reloading the home page asks me to fill up the entire forms all over again.
Can you help @JohanDufau

Hi, nearly same pb here, would you have any advice @JohanDufau ?
The setup page stays stuck on the "loading" and never changes.
Reloading the home page asks me to fill up the entire forms all over again.


Any way to negate STARTS_WITH ?

In my code I need a way to filter out entries NOT starting with a specific string.
Tried "NOT STARTS_WITH" and "!STARTS_WITH" but no luck.
Is there any way to achieve this?

@Vacilando I am afraid that is not possible since Drupal Core doesn't support those operators.
Following are the operators exposed by Drupal Core.
\Drupal\jsonapi\Query\EntityCondition::$allowedOperators = [
  '=', '<>',
  '>', '>=', '<', '<=',
  'STARTS_WITH', 'CONTAINS', 'ENDS_WITH',
  'IN', 'NOT IN',
  'BETWEEN', 'NOT BETWEEN',
  'IS NULL', 'IS NOT NULL',
];

Please note that drupal-jsonapi-params is only trying to provide a wrapper generate URLs. It doesn't modify/alter anything that Core does.

Is there any way to achieve this?

An inefficient way to solve this would be to get all items and then filter them out with the results from STARTS_WITH.  Otherwise, you would have to implement some endpoint serving Views or Custom REST plugin to support your use case. These solutions are out of scope of drupal-jsonapi-params module though.


Replace status boolean with ConnStatus enum.

Also remove Connection::shutdown and fold its behaviour into Connection::close, i.e. the close will append a graceful GoAway frame to the buffer before proceeding to close the connection.
The new ConnStatus enum has three states, Open, Shutdown and Closed. Most places continue to distinguish only between Open and not open. Shutdown is set by close in case it can not complete the close but is notified again. Besides calling close again, only flushing the connection is possible in Shtudown mode.

I suggest keeping a dummy shutdown() function marked as #[deprecated] and that just calls close().
This way, it's not a breaking change and we don't have to publish a new major version.


Devon rules should only check dependencies within the same package-namespace and only for valid OASP packages

See here:
https://devon-sonarqube.dev.s2-eu.capgemini.com/sonarqube/project/issues?id=io.oasp.application%3Amtsj&issues=AWIKDRKdvBcKeFLsmwmE&open=AWIKDRKdvBcKeFLsmwmE
The rule complaints about java.sql.Timestamp what is not from an OASP/Devon project. Therefore all this leads to false-positives.

Please add a test with this case that will then be red. Then fix the issue and see if the test gets green.

verified as fixed. Thanks @Capgemini-Sam


[Dask] Expected error randomly not raised in Dask test

2021-03-23T11:32:00.3655481Z         error_msg = "has multiple Dask worker processes running on it"
2021-03-23T11:32:00.3656048Z         with pytest.raises(lgb.basic.LightGBMError, match=error_msg):
2021-03-23T11:32:00.3656573Z >           dask_model3.fit(dX, dy, group=dg)
2021-03-23T11:32:00.3657297Z E           Failed: DID NOT RAISE <class 'lightgbm.basic.LightGBMError'>

https://github.com/microsoft/LightGBM/blob/77d54b3d22e6b55371e25f962f14d00d50f9e55c/tests/python_package_test/test_dask.py#L1058-L1060
Refer to https://github.com/microsoft/LightGBM/pull/4068#issuecomment-798972044 and https://github.com/microsoft/LightGBM/pull/4068#issuecomment-804857749 for full logs.

hmmm interesting. In the logs mentioned in those comments, it looks like this is a different root cause from what was fixed in #4071. I think that' what's happening here is that the data is still all ending up on one worker somehow. This is possibly the same underlying problem as https://github.com/microsoft/LightGBM/issues/4074, actually.
Error code 104 means "connection reset by peer" (link), which could occur in distributed training if one of the Dask workers dies and is restarted.
Similarly here, if one of the workers died before training started, then it's possible that Dask would have moved the training data back to the other worker, and that then dask_model3.fit() was fitting on only a single worker.
It's possible that one of the workers died because the two previous .fit() calls before this one left behind objects that caused it to run out of memory or caused other errors on the workers.
There's no reason that this test has to be in the same test case as the other network params tests. I just did that to try to minimize the total runtime of tests (number of times we call _create_data()). I think that moving this to its own standalone test case might reduce the risk of this specific failure.

It's possible that one of the workers died because the two previous .fit() calls before this one left behind objects that caused it to run out of memory or caused other errors on the workers.

client = <Client: 'tcp://<IP_ADDRESS>:36289' processes=2 threads=2, memory=16.70 GB>

I believe 16Gb should be enough for toy datasets we use for tests...

I think that moving this to its own standalone test case might reduce the risk of this specific failure.

Yeah, sure. But it doesn't fix underlying issue unfortunately.
I remember I asked this question before but didn't get a clear answer. Has Dask something like "global option for reproducibility"? Similarly to deterministic param in LightGBM. We use Dockers a lot to make out testing environments deterministic and don't change hardware settings for agents, so I'm quite curious why with all seeds fixed and same machine configs we get very different results and frequent failures with Dask.

so I'm quite curious why with all seeds fixed and same machine configs we get very different results and frequent failures with Dask

A couple points on this:

"with Dask" is a bit unfair. The Dask tests are the only automated tests that this project has had on distributed LightGBM training and I don't believe that all of the flakiness is just due to code in lightgbm.dask or its tests. Without dedicated tests on distributed training without Dask (#3841), it's hard to know which problems are "Dask problems" and which are "LightGBM problems" (see https://github.com/microsoft/LightGBM/pull/3952#pullrequestreview-610403805 for an example of what I think might be a "LightGBM problem").

Each test case for the Dask tests involves 4 processes: the main pytest process, a dask-scheduler process, and two dask-worker processes. These processes all compete with each other and with other processes running in the CI environment (like any Azure processes that are running in the background to communicate logs and statuses) for CPU time and memory, and so it's possible for them to randomly and occasionally fail for reasons like "this task took a little too long and triggered a timeout".

Has Dask something like "global option for reproducibility"? Similarly to deterministic param in LightGBM

This would be incredibly difficult for Dask or any distributed system to achieve. If you want to write code of the form "move this exact data to this exact worker and then run this exact task on this exact worker..." you can do it with Dask's low-level APIs, but at that point you're not really getting much benefit from Dask because you are doing all the work that its higher-level APIs are intended to abstract away.
Once you get into coordinating processes and not just threads within one process, it becomes much more difficult to predict the exact behavior of the system. LightGBM is able to offer a deterministic=True parameter because it completely controls the running code within a single process.

This would be incredibly difficult for Dask or any distributed system to achieve.

Absolutely agree with this for the case of "real world". But I thought with only two test workers and deterministic data partitioning algorithm (looks it is wrong for Dask) given the same dataset we don't have a lot of variants.


Does statuses/user_timeline not support tweet_mode=extended

I tried the following:
this.twitterClient.get('statuses/user_timeline.json?tweet_mode=extended', {});

But there is no full_text or extended_tweet property coming back on the response, what am I missing?

For anyone that comes looking, it needs to be included in the payload object.
this.twitterClient.get('statuses/user_timeline.json', { tweet_mode: 'extended' });


solana tweak tx timeout & fix typo

❓ Context

increase solana tx confirmation timeout to 100 seconds
fix typo

@gre , thanks for taking time to review. I think Hakim has moved all the changes to https://github.com/LedgerHQ/ledger-live/pull/105. So I close the PR.


Fixed direct link for BluetoothTerminal class

The file was put inside a folder named "src" since the last edit on this readme.

Oh, thank you @GuilhermeRossato !


[Import term(s)]http://purl.obolibrary.org/obo/EO_0001001

Term accession number(s):EO_0001001
AND CHILDREN
Reasoning
important terms to describe plant abiotic stress application which i cannot fiind in the recent vocabulary
e.g. temperature regime, salt ttreatment etc.

The Plant Environment Ontology (EO) as been deprecated so it is no longer possible to import terms directly from the ontology. Two options for using these terms are as follows:

The EFO has imported these terms into their ontology. As EFO is included in SwateDB, it is possible to use these exact terms (with EO ids) in Swate.

According to https://obofoundry.org/ontology/eo.html, "If you are using classes like EO:nnnnnn then you should be able to substitute this for PECO:nnnnnn, as all of the numeric parts of the ID are preserved." PECO is also in SwateDB so the terms should already be included in Swate. Please note: the PECO term labels are slightly changed (for example, the EO_0001001 term label is 'plant treatment' whereas the PECO_0001001 term label is 'plant exposure').


what hell going on? it doesn't work at all!

what hell going on? it doesn't work at all!

sorry, it same my fault!

You did a great job!
http://learnjade.com/tour/nesting/
OK

http://html2jade.org/
Error:


Rework setting image tags to support PRs better

Changes introduced with this PR
This PR reworks the reusable workflow which builds plugin container images.  It combines into one all the steps which handle different cases of generating container image tags depending on the CI trigger.  And, if the trigger is a Pull Request, it uses the name of the PR branch instead of the name of the GitHub "ref" (which is usually something generic, like 17/merge).  And, it picks a few bits of lint.
So, the tags will now be one of the following:

releases:  release and latest [this is unchanged]
the main branch:  main_latest [this is unchanged]
PRs: <PR_branch_name>_<last_commit_hash> [this is new]
tags and other branches: <tag-name_or_branch-ref>_<commit_hash> [this is unchanged]

This PR was tested using https://github.com/arcalot/arcaflow-plugin-rtla/pull/5 for PR builds and for tag builds, and it will use https://github.com/arcalot/arcaflow-plugin-rtla/pull/4 for testing main builds (i.e., once this PR is merged, then that one can be merged, and then this one will get tested 🙂).

By contributing to this repository, I agree to the contribution guidelines.

I kinda wish it was easier to follow this in the workflow log.

Yeah; I did make it show its work for you, though.

it will use arcalot/arcaflow-plugin-rtla#4 for testing main builds (i.e., once this PR is merged, then that one can be merged, and then this one will get tested 🙂).

And, it did, and it worked!


Added SwitchScene event

(see: https://github.com/Palakis/obs-websocket/blob/4.x-current/docs/generated/protocol.md#switchscenes for more info about this event)

Thank you very much for your contribution!
It looks good! I'll merge it.
Please note that it could take a while for a new version to deploy to nexus, though.

Great! Can you update the project version and deploy the new version to Maven Repository?

Yes! Sorry I didn't see your second PR so I need to do another release. This PR is in release 1.0.2


Version 2

[x] Keyboard navigation
[x] Aria Roles fixes (fixes #9)
[x] Smart "scrollTo" behavior
[x] Automatically sync selection
[x] Tree filtering now handled by arborist
[x] Moves "openness" state into the tree with an "initialOpens" prop
[x] Simple NodeApi class for use in the node renderer
[x] Ability to specify the drag handler (fixes #38)
[x] Splits the NodeRenderer into a RowRenderer and a NodeRenderer with defaults resulting in less boilerplate. (fixes #8)
[x] Adds an onActivate callback
[x] Adds an onSelect callback (fixes #44)
[x] Adds an onCreate callback
[x] Adds an onDelete callback
[x] Adds an onScroll callback (fixes #30)
[x] Improved abstractions for focus, selection, and activation (fixes #1, fixes #6)
[x] Fixes the bug where you can drag a parent into itself (fixes #41)

Remaining Items

[x] Document the new APIs
[ ] Make some Demos
[x] Fix the bugs that surface while doing the above

Hi @jameskerr, I have this running and everything works (with checkboxes). Thank you!
https://user-images.githubusercontent.com/64754391/197047335-d65a7351-099d-4a1b-8911-99e49d020394.mp4

@mooijtech YES! Thanks for posting that.


Support github auth on API UI

It's really confusing hitting the API UI from the browser and then having to type in your access key/api key.  Additionally, if you aren't careful you can create a HTTP session for the UI with those basic auth credentials.

I think to do we'd have to pass the JWT around as a cookie instead of the Authorization header (or completely rewrite the API UI so it's an application that makes AJAX requests instead of a bolt-on to the browser directly making HTTP requests).
Cattle would have to handle login and error cases somehow, e.g. if the token is invalid or expired..  And the API would have to live on the same hostname as the UI (or a subdomain).

As discussed, we can implement this on top of Basic auth by sending a known username like x-api-bearer and the JWT token as the password.
@hibooboo2 I think this should be your next thing after finishing the project updates.
If api.security.enabled is false then auth of this form should be ignored.  This will fix the weird case @tfiduccia got into today where the browser is stil sending authorization headers but no authorization is required, no hosts/anything show up, and the UI won't let you go to manage access controls because the credentials don't allow it to hit githubConfig.

Username: x-api-bearer or x-api-bearer=PROJECT_ID
Password: JWT_DATA

v0.17.0
Verified Fixed


SecurityContext GoDoc error in v1 types.go

This line of GoDoc appears to be a vestige from an earlier version of the API:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/api/v1/types.go#L1943
The line says SecurityContext.Privileged must match Container.Privileged.  Container.Privileged no longer exists in the v1 API.
I believe the line should be removed.  Or, replaced, in which case with what?

That line should be removed, as well the comment a few lines above about Container.Capabilities, which has the same problem.

Fixing this one this morning.


[bad code] Allow sigil to use interpolated strings or publish a function that takes a variable (i.e. not a macro).

Hi,
first of all I wanted to say that this module is the bees knees and I love it and I find it very useful. Thank you for your great work.
 Right now the sigils don't allow that to happen:
iex(2)> ~g/graph LR a #{"-->"} b/
** (FunctionClauseError) no function clause matching in DG.Sigil.sigil_g/2
    (dg 0.1.0) expanding macro: DG.Sigil.sigil_g/2
    iex:2: (file)

Unfortunately my macro skills are not yet relevant enough to make this work (I've tried for a while now and failed). So as a temporary workaround I've de-macroed the original gen function and it works alright but is not DRY.

I've added interpolation support. Going to make a release soon.

v0.2.0


Property is not configurable

Hi!
I have a problem with passing the updated data array when re-entering the screen where I use your list. Being on screen 1, I click on the second photo, move to screen 2 where I use your list, click the heart to change the attribute in the data array on screen 1 using Redux, go back to screen 1, and see the heart on the second photo. When I want to view this photo again, I click on it to go back to screen 2, and a Reanimated library error pops up. I suspect that the list keeps certain values that do not reset. Sometimes an error with the description appears - [Reanimated] Tried to modify key ${key} of an object which has been already passed to a worklet. See
https://docs.swmansion.com/react-native-reanimated/docs/guides/troubleshooting#tried-to-modify-key-of-an-object-which-has-been-converted-to-a-shareable
for more details.[
https://github.com/Skipperlla/rn-swiper-list/assets/110234655/c54429e9-bbd6-449a-a035-82f8e6905d74
]
System:
OS: macOS 14.5
CPU: (11) arm64 Apple M3 Pro
Memory: 87.22 MB / 18.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.2.0
path: /opt/homebrew/bin/node
Yarn:
version: 1.22.22
path: /opt/homebrew/bin/yarn
npm:
version: 10.7.0
path: /opt/homebrew/bin/npm
Watchman:
version: 2<IP_ADDRESS>
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.15.2
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.5
- iOS 17.5
- macOS 14.5
- tvOS 17.5
- visionOS 1.2
- watchOS 10.5
Android SDK: Not Found
IDEs:
Android Studio: 2023.3 AI-233.14808.21.2331.11709847
Xcode:
version: 15.4/15F31d
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.11
path: /usr/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.74.1
wanted: 0.74.1
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false

I'll work on it.

frankly I did a test on this but I couldn't get any results for the moment, I guess you might have missed a part in using the library, could you take a look at this https://github.com/react-navigation/react-navigation/issues/11289 also if you can send me your code I can quickly debug it @Smigi33

I've tried a test on this but I'm guessing that you may have missed a part in the use of the library, also if you can send me your code I can quickly debug it. @Smigi33

@Smigi33 @Skipperlla
is this fixed Guys
whenever i used any Select dropdown
when i select any of the dropdown i am getting the same above mentioned error
e.g:- i tried Native base Select Component, i built custom select dropdowns but same error
please confirm once


[CDS-101519] Added Disable Artifact Validation

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 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.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6763d2db6a809f315702564d--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6763d5a6b16ae347605b76c1--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6763da3d2fc6d480f510ba87--harness-developer.netlify.app

Lets keep this on hold for a bit. We are thinking of adding sidecar artifacts as part of this as well

Adding a "On hold" label as per Piyush's recommendation. Please reach out to me on slack when you need a review @vishal-av


nav improvements and grow section

I messed up the merge — instead of pulling my hair out trying to fix it, I just pulled your branch down, did a bunch of work, then pushed back upstream.
Closing this PR, thanks for the work!


Adding a tutorial for seeding a local postgres database

Hello.
There is no tutorial about seeding a local database in "Chapter 6: Setting Up Your Database". I changed the route.ts file so it would seed the local postgres database. I would be happy to make a tutorial for it, but I'm not sure how can I contribute to the dashboard app's tutorial. Neither I did find any guides on contributing to the tutorial. Is there a way to edit the existing chapter 6, or to add a new chapter about seeding a local postgres database?

A tutorial would be great. I followed all steps, but it seems that something is missing because I'm not getting the data into the database.

return Response.json({
message:
'...,
});
You need to delete the file above, and you may consider using bcryptjs instead of bcrypt. Here is how you go about it:

pnpm install bcryptjs
Replace import for bcrypt with bcryptjs -> import bcrypt from 'bcryptjs';
Adjust the code to use bcryptjs -> const hashedPassword = await bcrypt.hash(user.password, 10);

That should fix it.

return Response.json({ message: '..., });
You need to delete the file above, and you may consider using bcryptjs instead of bcrypt. Here is how you go about it:

pnpm install bcryptjs
Replace import for bcrypt with bcryptjs -> import bcrypt from 'bcryptjs';
Adjust the code to use bcryptjs -> const hashedPassword = await bcrypt.hash(user.password, 10);

That should fix it.

This method still failed, and the console shows a 500 error along with an Uncaught Error: [object Object]

What worked for me is setting the seed/route.ts like below:
import bcrypt from 'bcrypt';
import { db } from '@vercel/postgres';
import { invoices, customers, revenue, users } from '../lib/placeholder-data';

const client = await db.connect();

async function seedUsers() {
  await client.sql`CREATE EXTENSION IF NOT EXISTS "uuid-ossp"`;
  await client.sql`
    CREATE TABLE IF NOT EXISTS users (
      id UUID DEFAULT uuid_generate_v4() PRIMARY KEY,
      name VARCHAR(255) NOT NULL,
      email TEXT NOT NULL UNIQUE,
      password TEXT NOT NULL
    );
  `;

  const insertedUsers = await Promise.all(
    users.map(async (user) => {
      const hashedPassword = await bcrypt.hash(user.password, 10);
      return client.sql`
        INSERT INTO users (id, name, email, password)
        VALUES (${user.id}, ${user.name}, ${user.email}, ${hashedPassword})
        ON CONFLICT (id) DO NOTHING;
      `;
    }),
  );

  return insertedUsers;
}

async function seedInvoices() {
  await client.sql`CREATE EXTENSION IF NOT EXISTS "uuid-ossp"`;

  await client.sql`
    CREATE TABLE IF NOT EXISTS invoices (
      id UUID DEFAULT uuid_generate_v4() PRIMARY KEY,
      customer_id UUID NOT NULL,
      amount INT NOT NULL,
      status VARCHAR(255) NOT NULL,
      date DATE NOT NULL
    );
  `;

  const insertedInvoices = await Promise.all(
    invoices.map(
      (invoice) => client.sql`
        INSERT INTO invoices (customer_id, amount, status, date)
        VALUES (${invoice.customer_id}, ${invoice.amount}, ${invoice.status}, ${invoice.date})
        ON CONFLICT (id) DO NOTHING;
      `,
    ),
  );

  return insertedInvoices;
}

async function seedCustomers() {
  await client.sql`CREATE EXTENSION IF NOT EXISTS "uuid-ossp"`;

  await client.sql`
    CREATE TABLE IF NOT EXISTS customers (
      id UUID DEFAULT uuid_generate_v4() PRIMARY KEY,
      name VARCHAR(255) NOT NULL,
      email VARCHAR(255) NOT NULL,
      image_url VARCHAR(255) NOT NULL
    );
  `;

  const insertedCustomers = await Promise.all(
    customers.map(
      (customer) => client.sql`
        INSERT INTO customers (id, name, email, image_url)
        VALUES (${customer.id}, ${customer.name}, ${customer.email}, ${customer.image_url})
        ON CONFLICT (id) DO NOTHING;
      `,
    ),
  );

  return insertedCustomers;
}

async function seedRevenue() {
  await client.sql`
    CREATE TABLE IF NOT EXISTS revenue (
      month VARCHAR(4) NOT NULL UNIQUE,
      revenue INT NOT NULL
    );
  `;

  const insertedRevenue = await Promise.all(
    revenue.map(
      (rev) => client.sql`
        INSERT INTO revenue (month, revenue)
        VALUES (${rev.month}, ${rev.revenue})
        ON CONFLICT (month) DO NOTHING;
      `,
    ),
  );

  return insertedRevenue;
}

export async function GET() {
  // return Response.json({
  //   message:
  //     'Uncomment this file and remove this line. You can delete this file when you are finished.',
  // });
  try {
    await client.sql`BEGIN`;
    await seedUsers();
    await seedCustomers();
    await seedInvoices();
    await seedRevenue();
    await client.sql`COMMIT`;

    return Response.json({ message: 'Database seeded successfully' });
  } catch (error) {
    await client.sql`ROLLBACK`;
    return Response.json({ error }, { status: 500 });
  }
}

The last try catch block was not getting executed. After commenting like shown above, I got it working!


get_all_members() does not return all the Members the client can see.

Summary
get_all_members() does not return all the Members the client can see.
Reproduction Steps

call get_all_members()
create a loop that will save every member on a new line on a file
see file lines
despair

Code
class MyClient(discord.Client):
    async def on_ready(self):
        users = self.get_all_members()

        with open("cache.txt", "a", encoding="utf-8") as f:
            for user in users:
                f.write(f'{user} || {user.activities} || {user.raw_status}\n')
        f.close()

Expected Results
All 250,000+ Members in the file
Actual Results
Only exactly 11,413 Members in the file
System Information

Python v3.10.1-final
discord.py-self v1.9.1-final
aiohttp v3.7.4.post0
system info: Windows 10 10.0.22000

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shared the entire traceback.
[X] I am using a user token (and it isn't visible in the code).

Additional Information
No response

Discord doesn't send you member information directly, users don't have a special endpoint for this like bots do. Instead, user accounts need to subscribe to member events to piece it together, and as you can see from other issues, this functionality is currently broken.
Extras - https://stackoverflow.com/questions/66413043/discord-selfbot-cant-get-all-members-just-part-of-it

The functionality works ok-ish most of the time, you just need to properly configure the GuildSubscriptionOptions or manually run guild.subscribe() for every guild you want members from.
2.0's guild member fetching will be far more robust.


Dragging window from maximized state title bar rendering issue

[√] Flutter (Channel stable, 2.0.1, on Microsoft Windows [Version 10.0.19041.331], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[X] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.9.1)
[√] Android Studio (version 4.1.0)
[√] VS Code (version 1.54.1)
[√] Connected device (2 available)

You have to grab it from the outer edge while it is maximized

Here is a frame from the GIF above

Here is a minimum reproduction of the issue
https://github.com/geocine/flutter-jitter-issue
main - Flutter demo, simple Hello World
issue/jitter - Added bitsdojo_window

Should be fixed by https://github.com/bitsdojo/bitsdojo_window/commit/3fd4412c7b071e257b3ff33c863438ad358049ab


Cannot Install Tensorflow on QPython3

Sorry, QPython will not support tensorflow in the near future, I suggest you to consider keras  is a high-level neural networks API, written in Python and capable of running on top of TensorFlow, CNTK, or Theano and you can install keras-aipy3 from QPYPI.
We will announce it in facebook(https://www.facebook.com/qpython) when QPython supports tf in the future.


[Feature, Request], DateTimePicker, plugin, is, hard, to, use

Existing Component
是
Component Name
DateTimePicker
Description
now i'm use datetimePicker. but if i want to change time，it's must click confirm button， it could be changed when click the time。
also because it‘s hard to use， if i directly change the time use keyboard， but the real model is not change， its display time not equals the real time。
datePicker is easy to use， hope can change just like java datepicker plugin， thanks

We have no plan to change its interaction behavior.


feat: allow setting default platform globally via Python

It would be very nice if we could globally set the default platform via jax.config.update("jax_default_device", ...). This was mentioned as a to-do by @skye in gh-9118.

Context: I'm working on adding support for JAX in SciPy (scipy/scipy#20085), which involves testing across various devices. We have an environment variable SCIPY_DEVICE, which we currently use with PyTorch like torch.set_default_device(SCIPY_DEVICE). It would be easier if we could keep this at the level of a string like "cuda" or "cpu" rather than having to pass in device objects.
Feel free to suggest an easier way to do this if you see one by the way!

Okay, I suppose jax.config.update("jax_default_device", jax.devices(SCIPY_DEVICE)[0]) works - still, this would be nice to have!

Hey @lucascolley , thanks for the request! But help me understand: does this already work? What's left to do?

Hey @mattjj, currently I can do jax.config.update("jax_default_device", jax.devices('cuda')[0]). This request (and the TODO in the code) is to just be able to do jax.config.update("jax_default_device", 'cuda') for the same result. And similarly for other platforms (cpu, tpu?)

Thanks for clarifying!
That seems like a slight type error though... the default device needs to be a single device, whereas 'cuda' refers to a platform, for which there may be (and typically are) several devices. I guess the intent is arguably clear, but it seems oddly single-device specific...

Does jax.config.update('jax_platforms', 'cpu') work?
https://github.com/google/jax/blob/0dde8f7f9607d09841ece7125dfc0773c3613fab/jax/_src/config.py#L912-L926

Does jax.config.update('jax_platforms', 'cuda') work?

No, not quite. IIUC, that would mean that I can only use CUDA devices. I still want to be able use other platforms, just not by default.
A further extension: I would like jax.config.update("jax_default_device", 'cuda:1') to work also.

I was looking for similar flexibility. Turns out you can pass jax_platforms as a list, such as "cpu,cuda" which will default to placing arrays on cpu but still keep the cuda platform available for use. This doesn't work as a context manager though like default_device.

That's somewhat useful, although it still requires obtaining a list of available platforms.

A further extension: I would like jax.config.update("jax_default_device", 'cuda:1') to work also.

In fact, this would probably be enough to address this issue alone. I understand that it seems like "a slight type error", but I think 'cuda:1' is a very reasonable and useful syntactic-sugar for jax.devices('cuda')[1]

Thanks for the discussion!
My understanding is that there's already a way to express this, using both jax_default_device and jax.devices(platform)[index], and we're just talking about syntactic sugar / a convenience wrapper.
While I can appreciate that syntactic sugar can be convenient, in general it's also desirable to get expressiveness through composing up simple things rather than building complicated things. In this case, I'd rather not make jax_default_device more complicated (in the sense of accepting platform-like arguments, or developing a platform-and-device-index mini-language in strings).
I understand that there's no clear answer here, and you may disagree. But that's my current best judgement.
Thanks for the suggestion. Hopefully you can just define a convenience wrapper in your code that amounts to the same thing!


Use Self where possible

Change Summary

Some cleaning, can be reviewed commit per commit.

Related issue number

Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Please review

Is this one intended to be a breaking change ?

@vikyw89 You can read more about it here: https://typing.readthedocs.io/en/latest/spec/historical.html#positional-only-parameters.
It is technically a breaking change, although using __model_name as a kw-argument would have be caught by type checkers in the first place. Sorry for the inconvenience, probably the changelog should be updated as per the issue that was opened by @fraser-langton


Write response comments for AT, IR, PE, PL, SA, SC, SI

In order for our next JAB Q&A meeting to run smoothly and effectively, we need to review their comments ahead of time and write response comments.
We should send our PMO a copy of our response comments as soon as we can.
We're writing comments in this copy of the workbook.
Note: We don't yet have a complete set of comments - one of the TRs is still working on AT, PE, PL (expected soon) - but we can still get started on this.
Ideally we should send this by COB Wednesday.
Acceptance criteria
We have response comments for all of the following:

[x] 0 AT items
[ ] 21 IR items
[x] 1 PE item
[x] 1 PL item
[ ] 3 SA items
[ ] 20 SC items
[ ] 28 SI items

And:

[ ] We've emailed the updated workbook to our PMO

I wrote draft comments for about ~18 easy ones. There are tricky IR ones about information spillage, and a lot of the SC and SI ones are specific technical questions that I can't answer.

Updated the workbook link to one with additional IR and SI comments.

Sent and meeting held


'bigint' is not comparable to 'number' with loose equality

TypeScript Version:  3.3.3

Search Terms: bigin == number not comparable loose equality
Code
1n == 1

error:
This condition will always return 'false' since the types 'bigint' and 'number' have no overlap.

but in chrome 72.0.3626.121
> 1n == 1
< true

and in MDN https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt

And similar issues
let x = [1, 2, 3]
x[1n]

error:
Type '1n' cannot be used as an index type.

in Chrome
>  let x = [1, 2, 3]
   x[1n]
<  2

Playground Link:
http://www.typescriptlang.org/play/index.html#src=1n %3D%3D 1
http://www.typescriptlang.org/play/index.html#src=let x %3D [1%2C 2%2C 3]
x[1n]
Related Issues:
https://github.com/Microsoft/TypeScript/issues/30655

I agree that the error message This condition will always return 'false' is not strictly correct. But comparing number and bigint values for equality should definitely cause a type-checking error. It is not obvious how to compare a bigint to a number—should they be coerced to numbers or bigints before doing the comparison? It makes sense to me that the compiler requires you to explicitly coerce one of them.
Number(1n) == 1.2 // false
1n == BigInt(1.2) // RangeError: The number 1.2 cannot be converted to a BigInt because it is not an integer

Number(BigInt(Number.MAX_SAFE_INTEGER) + 2n) == Number.MAX_SAFE_INTEGER + 2 // true
BigInt(Number.MAX_SAFE_INTEGER) + 2n == BigInt(Number.MAX_SAFE_INTEGER + 2) // false

The compiler gives the same warning if you tried to compare strings and numbers:
// This condition will always return 'false' since the types '"1"' and '1' have no overlap.
'1' == 1 // true

The fact that bigints can't be used as indices is intentional. Arrays, strings, TypedArrays, etc. are meant to be indexed with numbers, so the compiler should warn you if you are indexing with a bigint.
Again, the same is true when strings are used in place of bigints:
// Element implicitly has an 'any' type because index expression is not of type 'number'.ts(7015)
['a', 'b', 'c']['1'] // 'b'

We discussed adding bigint index signatures and eventually decided against it.

@calebsander
I just ran into the issue of comparing a string and a number: '0' != 0 // false
TS2367: This condition will always return 'true' since the types 'string' and '0' have no overlap.
The double equals operator should be thought of as a function with two any parameters since it doesn't do type equality like the triple equals operator does. Or maybe it's possible to improve the core type definitions by encoding the coercion rules into them?

I think it's good that the compiler gives an error in this case. In my experience, comparing values of different types is usually a mistake. If not, you can explicitly convert the number to a string or the string to a number. But I agree that the error message is misleading—perhaps for == it should just say "Cannot compare values of type 'string' and type '0'".

@calebsander
should be error only when strictly

There are lots of things which are technically valid JavaScript, but TypeScript rightly warns about them because they are usually not what the programmer meant to write. For example, you can multiply two strings in JS and they will be coerced to numbers, but TypeScript forces you to explicitly coerce them. I think this is reasonable behavior, and == and === should both require their operands to have the same type.

TS may rightly want to error on people using == at all. But... if someone uses == instead of ===, then TS should accurately make its assumptions about what == will do. It appears from this thread (and others) that's not the case. Wanting to throw useful errors is fine, but incorrectly representing how JS works is not.
IOW, the vastly more common perspective (much to my chagrin) is that devs default to using ===, and that's ESPECIALLY true for those who use type systems like TS. So, if someone is going out of their way to use TS, and they choose a ==, and that's allowed by their linter/settings, then the assumption should be they intended to do that, and that they intended to take advantage of the coercive capabilities of ==.

The interesting thing about comparing numbers with bigints in JavaScript is that it is not implemented by coercing both operands to numbers, nor is it implemented by coercing both arguments to bigints. Instead, the exact real values are compared. Here are some examples:
These values are different:
> 10n**50n == 10**50
false

But they become equal when coerced to numbers:
> Number(10n**50n) == Number(10**50)
true

These values can be compared:
> 1n == 1.5
false

But cannot be coerced to bigints:
> BigInt(1n) == BigInt(1.5)
Uncaught:
RangeError: The number 1.5 cannot be converted to a BigInt because it is not an integer

Currently, it is not possible to get this comparison semantics in TypeScript without using type assertions. I agree that == operator shouldn't have the same strict type checking rules as === operator, as the use of the former signals the intent that the operands may be of different types.

This error makes sense for ===, but not for ==. As @abacabadabacaba explained, there is no easy workaround of casting operands to number or bigint.
Please fix it.

Currently, it is not possible to get this comparison semantics in TypeScript without using type assertions.

I believe (but could be wrong) that the following replicates the == behavior
function compare(n: number, bi: bigint): boolean {
  return Number.isInteger(n) && BigInt(n) === bi;
}

Note that it's not clear that that's such a useful operation, since BigInts' reason for existing is to handle values outside of the safe integer range, and there be dragons there (as noted in https://github.com/microsoft/TypeScript/issues/30540#issuecomment-495393886):
Number.MAX_SAFE_INTEGER + 2 == BigInt(Number.MAX_SAFE_INTEGER) + 2n; // false
Number.MAX_SAFE_INTEGER + 1.5 == BigInt(Number.MAX_SAFE_INTEGER) + 1n; // true

Therefore, it may well in practice be inappropriate to compare using the == behavior; instead, one of the following may be preferable:
function compare(n: number, bi: bigint): boolean {
  return Number.isSafeInteger(n) && BigInt(n) === bi;
}

function compare(n: number, bi: bigint): boolean {
  if (!Number.isSafeInteger(n)) {
    throw new Error("attempted to compare unsafe number with bigint");
  }
  return BigInt(n) === bi;
}

Providing this info not particularly to weigh in on whether the == should be allowed here in TS, but as a reference for some relevant info on the topic that hasn't been brought up in this thread yet, and may be helpful to others like me who stumble upon this issue.

I believe (but could be wrong) that the following replicates the == behavior

I'm not sure I would recommend this construct as it relies on type assertions. This means that the following similar usage compiles fine despite probably not being what you want.
function compare(n: string, bi: bigint): boolean {
	return Number.isInteger(n) && BigInt(n) === bi;
}

Of course if you wrap it in a function it is probably fine. But this is a lot of overhead and reduction in clarity to what could be a built-in operator which is safe for the given types.

Note that it's not clear that that's such a useful operation,

I don't think I agree. The problem in this example isn't at all related to BigInt or the comparison, it is just that you are leaving the range of a Number. That is a questionable thing to do whether or not BigInt is involved. By that argument you can say that === should be banned on numbers because Number.MAX_SAFE_INTEGER + 1.5 === Number.MAX_SAFE_INTEGER + 1.

By that argument you can say that === should be banned on numbers because Number.MAX_SAFE_INTEGER + 1.5 === Number.MAX_SAFE_INTEGER + 1.

This isn't that preposterous a conclusion 🙂! In most programming languages we do avoid exact equality comparison between floats, and use a separate integer type (or multiple) for integer operations.
It's just in JS, as far as I'm aware, where it's canonical to use the mantissa of floats to represent exact integers, and so we make a habit of performing integer-like operations on floats.

Anyways, the important points I was trying to make were simply:

You can replicate the == behavior without using the == operator or a type assertion

But please use that with caution depending on your specific context. Don't blame me if it was a bad idea for your use case 🫶


Google auth configuration screen flow has changed

@jehiah ready for review - the auth token generation flow has changed a little, mostly for the better.

doc_updates++


Architecture as Code - Working Group Meeting - Tuesday 27th August

Date
Tuesday 27th August - 11:00 EST / 16:00 BST
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[x] Convene, roll call, welcome new people
[x] Approve previous meeting minutes
[x] Recap of CALM / AasC and purpose for new joiners if needed (@rocketstack-matt / 5mins)
[x] OSFF Updates (@dc-ms / 5 mins)
[x] Update on Resiliency Requirements (@develontopia / 5 mins)
[x] Control Requirements (@jpgough-ms / 30 mins)
[ ] AOB, Q&A & Adjourn (5mins)

Zoom info
Join Zoom Meeting

https://zoom.us/j/94904595244
Meeting ID: 949 0459 5244
Passcode: 545224
Find your local number: https://zoom.us/u/aesEqmNODb

Github Repo: https://github.com/finos/architecture-as-code/
Project Board: https://github.com/orgs/finos/projects/98
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Karl Moll / FINOS

Matthew Gardner / Morgan Stanley

Aidan McPhelim / Morgan Stanley

Will Osborne / Morgan Stanley

George  Ball / Independent

Miguel Gasca / Morgan Stanley

Matthew Auburn / Morgan Stanley

Denis Coffaro / Morgan Stanley

Fleur Edwards / Nomura

Edi Baker-Wells / Natwest

Yan Tordoff /  Morgan Stanley

Shari Lines / Morgan Stanley

OSFF NYC Details : •	https://events.linuxfoundation.org/open-source-finance-forum-new-york/

OSFF Presentation on YouTube & Powerpoint deck shown briefly in the working group.

Two in-person events the same day, at MSFT offices in Times Square
AI Readiness SIG (Members Only)
https://www.finos.org/hosted-events/2024-09-12-ai-readiness-sig-nyc
Tech Sprint (TraderX: there is an ongoing initiative which is very relevant to AaC):
https://www.finos.org/hosted-events/2024-09-12-finos-tech-sprint-coding-session

Christopher Avalos / Goldman Sachs

Red Hat

David Johnston
Anurag Saran
Naaz Page

Broken URL in Agenda:
Project Board: https://github.com/orgs/finos/projects/98

Dorothy Ewuah / Turntabl

Broken URL in Agenda:
Project Board: https://github.com/orgs/finos/projects/98

Project boards are only visible to repo members

Abdul Faheem Kassim / Turntabl

Joseph Peter Yoofi Brown-Pobee / turntabl

FINOS Meeting August 27, 2024
Commenced 11:02 EST
Introduction / FINOS Disclaimer Completed
Agenda & Attendance noted https://github.com/finos/architecture-as-code/issues/360 - Done
Previous minutes approved by attendees and closed out https://github.com/finos/architecture-as-code/issues/308 - Done
August Release (objectives / current state / blockers)

CALM Overview for new joiners @rocketstack-matt

Brief overview and introduction

Relationships/Intentions

Nodes explained

Instances lead us to Patterns

Link to presentation and OSFF London video : https://github.com/finos/architecture-as-code/issues/360#issuecomment-2312858289

OSFF Update @dc-ms

OSFF FINOS NYC Event
September 30 – October 1
Multiple CALM related presentations
CALM specific on October 1st – 3:45PM EST
Based on issues and questions that were asked – using the platform to review

Problem statement
Industries
Solutions
Domains – Janette (@develontopia)

Co present with David Johnson from Red Hat sharing a field perspective
Objective is awareness, contribution and consumption
https://events.linuxfoundation.org/open-source-finance-forum-new-york/
API Days London (Link will be in an issue)
Security Domains + Observability – (Link will be in an issue)

Functional Update @jpgough-ms

Schema and Model
Domains
Controls

Resiliency Domain

Christopher Avalos to sync up with Janette Schulze
General discover on more contributors in this space

Issues https://github.com/finos-labs/architecture-as-code/issues
Adjourned 12:01 EST

Elisha Amenuveve / Turntabl

Konadu Appiah / Turntabl

Approved at https://github.com/finos/architecture-as-code/issues/394


wait for cluster green status before moving on

really should be waiting for all shards to be ready before moving on

@diwu1989 , for what reasons did you cancel this PR?


Enabling the RSpec BeforeAfterAll Rubocop rule

https://www.rubydoc.info/gems/rubocop-rspec/1.15.0/RuboCop/Cop/RSpec/BeforeAfterAll
What are you trying to accomplish?
The BeforeAfterAll RSpec rule was disabled in some parts of the ecosystme.  This PR will enable and fix those scenarios it identifies.
Anything you want to highlight for special attention from reviewers?
Please watch for code duplications or conflicts.
How will you know you've accomplished your goal?
The Rubocop rule will work and the tests will not fai afterwards.
Checklist

[ ] I have run the complete test suite to ensure all tests and linters pass.
[x] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

Some of the rubocops were mixed up in main, so with a merge from main, things got out of sync.  This branch should reflect the rubocop status in main.

@GarryHurleyJr still looks like there are unrelated changes in this PR. Maybe easiest to just do a hard reset to main and re-apply the changes.

@GarryHurleyJr still looks like there are unrelated changes in this PR. Maybe easiest to just do a hard reset to main and re-apply the changes.

The problem is that PR #9820 re-added some other rubocop rules that had been removed.  I am going to update that here so that we are at least showing the proper status of this file.

https://github.com/dependabot/dependabot-core/pull/10041 contains the code that was muddying this PR.

creating a new PR for this issue


Potential Virus Detected

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
2.8.0
What problem did you encounter?
System.IO.IOException: Operation did not complete successfully because the file contains a virus or potentially unwanted software.  : '%UserProfile%\AppData\Local\Bloxstrap\Downloads\50e0fc0c3acbc05c24281840f541418f'
   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at Bloxstrap.Bootstrapper.ExtractPackage(Package package, List`1 files)
   at Bloxstrap.Bootstrapper.<>c__DisplayClass33_1.<UpgradeRoblox>b__6()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.<>c.<.cctor>b__272_0(Object obj)
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at Bloxstrap.Bootstrapper.UpgradeRoblox()
   at Bloxstrap.Bootstrapper.Run()
   at Bloxstrap.Bootstrapper.Run()

False positive, and not a Bloxstrap issue.


[Breadth Coverage] Onboard Azure StreramAnalytics Commands

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
no
Describe the solution you'd like
A clear and concise description of what you want to happen.
Support StreamAnalytics service.
https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftstreamanalytics
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

in S165.

in S165.

starts from S164.

https://github.com/Azure/azure-cli-extensions/pull/1386


Fix case of PloS

As reported in the forum, the abbreviation of "PLoS Genetics" had "s" in lowercase.

LGTM! But I can't merge it in  (no rights)
@koppor Could you enable rights here?

Access rights should be ok now.

And it is merged :-)


allow plugins to be specified by a dll file path

This allows plugins to be specified using the path to a dll. This adds to the existing behavior of allowing plugins to be specified using an assembly name.

@david-driscoll I could alternately PR this to master. Rebasing from there to the lsp branch will result in a small merge conflict. Let me know if you have a preference.


Add talosctl as a new CLI tool.

Signed-off-by: Matthew Richardson<EMAIL_ADDRESS>Description
Add talosctl command-line tool for managing Talos Linux OS clusters.
Motivation and Context
Fixes https://github.com/alexellis/arkade/issues/720

[X] I have raised an issue to propose this change, which has been given a label of design/approved by a maintainer (required)

How Has This Been Tested?
make test && make e2e

Test results

fatal: No names found, cannot describe anything.
CGO_ENABLED=0 go test github.com/alexellis/arkade github.com/alexellis/arkade/cmd github.com/alexellis/arkade/cmd/apps github.com/alexellis/arkade/cmd/kasten github.com/alexellis/arkade/cmd/system github.com/alexellis/arkade/cmd/venafi github.com/alexellis/arkade/pkg github.com/alexellis/arkade/pkg/apps github.com/alexellis/arkade/pkg/archive github.com/alexellis/arkade/pkg/config github.com/alexellis/arkade/pkg/env github.com/alexellis/arkade/pkg/get github.com/alexellis/arkade/pkg/helm github.com/alexellis/arkade/pkg/k8s github.com/alexellis/arkade/pkg/types -cover
?   	github.com/alexellis/arkade	[no test files]
ok  	github.com/alexellis/arkade/cmd	(cached)	coverage: 17.4% of statements
ok  	github.com/alexellis/arkade/cmd/apps	(cached)	coverage: 2.0% of statements
?   	github.com/alexellis/arkade/cmd/kasten	[no test files]
?   	github.com/alexellis/arkade/cmd/system	[no test files]
ok  	github.com/alexellis/arkade/cmd/venafi	(cached)	coverage: 3.2% of statements
?   	github.com/alexellis/arkade/pkg	[no test files]
?   	github.com/alexellis/arkade/pkg/apps	[no test files]
?   	github.com/alexellis/arkade/pkg/archive	[no test files]
ok  	github.com/alexellis/arkade/pkg/config	(cached)	coverage: 22.9% of statements
?   	github.com/alexellis/arkade/pkg/env	[no test files]
ok  	github.com/alexellis/arkade/pkg/get	(cached)	coverage: 49.9% of statements
ok  	github.com/alexellis/arkade/pkg/helm	(cached)	coverage: 6.2% of statements
?   	github.com/alexellis/arkade/pkg/k8s	[no test files]
?   	github.com/alexellis/arkade/pkg/types	[no test files]
fatal: No names found, cannot describe anything.

[ ] Yes
[X] No

Types of changes

[ ] 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 change)

Documentation

[X] I have updated the list of tools in README.md if (required) with ./arkade get -o markdown
[ ] I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I've read the CONTRIBUTION guide
[X] I have signed-off my commits with git commit -s
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

[ ] I have tested this on arm, or have added code to prevent deployment

Hey @mrichar1 !
Thanks for the PR, you can test this on arm using the --os and --arch flags for arkade get, check out this file for examples: https://github.com/alexellis/arkade/blob/master/hack/test-dagger.sh

Tested with arch and os flags:
+ go build
+ ./arkade get talosctl --arch arm64 --os darwin --quiet
🐳 arkade needs your support, learn more: https://my.arkade.dev
+ file /home/mrichar1/.arkade/bin/talosctl
/home/mrichar1/.arkade/bin/talosctl: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
+ rm /home/mrichar1/.arkade/bin/talosctl
+ ./arkade get talosctl --arch x86_64 --os darwin --quiet
🐳 arkade needs your support, learn more: https://my.arkade.dev
+ file /home/mrichar1/.arkade/bin/talosctl
/home/mrichar1/.arkade/bin/talosctl: Mach-O 64-bit x86_64 executable
+ rm /home/mrichar1/.arkade/bin/talosctl
+ ./arkade get talosctl --arch x86_64 --os linux --quiet
🐳 arkade needs your support, learn more: https://my.arkade.dev
+ file /home/mrichar1/.arkade/bin/talosctl
/home/mrichar1/.arkade/bin/talosctl: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=4CjhX_WYFbO_mlV-yXCz/weUbeKA0NkynMftVqKF5/DGxqmDLJ6mZ3kKDZlZXs/1KgFD-RHV0KbYNRiyHJb, stripped
+ rm /home/mrichar1/.arkade/bin/talosctl
+ ./arkade get talosctl --arch arm64 --os linux --quiet
🐳 arkade needs your support, learn more: https://my.arkade.dev
+ file /home/mrichar1/.arkade/bin/talosctl
/home/mrichar1/.arkade/bin/talosctl: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=O-QIyspeqDAIML4CVYbU/inTFWtB7jBnBrJpY0WUu/5_Wbtghwhumb-M_u8z09/HbN9HsjpnGt9308E0axL, stripped
+ rm /home/mrichar1/.arkade/bin/talosctl
+ ./arkade get talosctl --arch x86_64 --os ming --quiet
🐳 arkade needs your support, learn more: https://my.arkade.dev
+ file /home/mrichar1/.arkade/bin/talosctl
/home/mrichar1/.arkade/bin/talosctl: PE32+ executable (console) x86-64 (stripped to external PDB), for MS Windows
+ rm /home/mrichar1/.arkade/bin/talosctl

LGTM!
(Cc: @alexellis)

Just need a rebase on this and we can move forward. Thanks

Closed via b9ca577f38a21c6bffc6dcefdb65eb1343014450

Thanks for contributing.


add remoteAuthority to IWorkspaceProvider.open

This allows to specify a remote authority when opening an empty window through the IWorkspaceProvider.
This follows the same model as with the native host service:
The remoteAuthority can be undefined so it will be deducted from the currently open remote, or null then a non-remote (local) window will be opened.

I added the code that also reads out the authority from the query parameters.
Thinking about this more, I want to suggest a different approach
export type IWorkspace = IWorkspaceToOpen | IFolderToOpen | IEmptyRemotWorkspace | undefined;
interface IEmptyRemoteWorkspace { remoteAuthority: string }
The IEmptyRemoteWorkspace is only used when the remote authority changes to a different authority.
undefined is still valid and used for empty workspaces when the remote authority does not change.
That should minimize the breakage

Yes that sounds reasonable!

I implemented the suggestion with IEmptyWorkspace (can also represent a local workspace, if you want to switch from remote to local)
I think the cases where remotes are changes are quite rare. Only now this becomes a topic when vscode.dev supports locals and remotes and we have scenarios that switch from one remote to another (tunnels to 'wsl in tunnels')

Test failures in the browser integration tests that I don't yet understand...

Is this still relevant?


How to use reapp-ui in my project

my code :
"use strict";
/**
*

Created by rocky on 16/4/26.
*/
import React, {
Component
} from 'react';
import Button from "reapp-ui/components/Button";

export default class IndexPage extends Component {
render() {
return (

Try dragging this view from the left edge to go back!

);
}
}
error :
Uncaught TypeError: Cannot read property 'filter' of undefined

My code :
"use strict";
/**
*

Created by rocky on 16/4/26.
*/
import React, {
Component
} from 'react';
import Button from "reapp-ui/components/Button";

export default class IndexPage extends Component {
render() {
return (

Try dragging this view from the left edge to go back!

);
}
}
Browser Error :
Uncaught TypeError: Cannot read property 'filter' of undefined
componentProps  @   ComponentProps.js:15
render  @   Button.js:120
render  @   enhancer.js:132

error :
Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's render method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner).

my code is your demo.
package.json :
"dependencies": {
"keymirror": "^0.1.1",
"q": "^1.4.1",
"react": "^15.0.1",
"react-dom": "^15.0.1",
"react-list": "^0.7.18",
"react-redux": "^4.4.5",
"react-router": "^2.3.0",
"reapp-ui": "^0.12.84",
"redux": "^3.5.2",
"redux-thunk": "^2.0.1",
"underscore": "^1.8.3"
},

麻烦楼主用markdown先整理下代码。看起来费劲。

请楼主贴完整代码

问题是这样的，我想使用reapp-ui作为我一个内容项目UI开发的框架，但是再耦合上去的时候很多都无法使用。能否给一个Demo，让我看看如果只使用reapp-ui作为UI层面开发框架使用（不想用reapp-kit作为管理 - 能否兼容最近的react 5.x的版本）


Works fine from IntelliJ IDEA. But fails to execute from terminal

@archie94 can you look into it?

@ghoshbishakh I am downloading the IDE. What is the error you are getting?

@ghoshbishakh can we create a jar file and run from terminal?

@archie94 I am not familiar with java, try whatever you feel right.

@ghoshbishakh created jar and works in terminal.

@archie94 great. can you somehow test it once?

@ghoshbishakh I tested the jar file with an android device. Found these bugs:

The pc app is unable to find the list of missing files from the android device.
java.io.FileNotFoundException: /www/database/fileDB.txt (Permission denied) when thread tries to find the list of its files.
The service is not stopping on closing the app from terminal.


feature: Add support for cuda implicit types

Did you check the tree-sitter docs?

[x] I have read all the tree-sitter docs if it relates to using the parser

Is your feature request related to a problem? Please describe.
Some cuda keywords are not recognized properly (I am trying to create an emacs backend)
Describe the solution you'd like
There is not any inclusion for the implicit cuda types in the grammar like:
"dim3"
     "char1" "uchar1" "char2" "uchar2" "char3" "uchar3" "char4" "uchar4"
     "short1" "ushort1" "short2" "ushort2" "short3" "ushort3" "short4" "ushort4"
     "int1" "uint1" "int2" "uint2" "int3" "uint3" "int4" "uint4"
     "long1" "ulong1" "long2" "ulong2" "long3" "ulong3" "long4" "ulong4"
     "float1" "float2"  "float3" "float4"
     "double1" "double2"

Adding this may be pretty simple to do.
At the same time there are well defined cuda intrinsic patters that could be included.. this is an extra, but good to mention (as they don't seem complicated either:
There are other type specifiers: __managed__ __restrict__
Some very common intrinsics:

__syncthreads,
atomic{Add,And,CAS, Dec,Exch,...}
__shfl_{up,down,xor}_sync
__[a-z]+_sync
"__is{Global,Shared,Constant,GridConstant,Local}"

And Primary expressions really very useful in kernels:

gridDim blockIdx blockDim threadIdx warpSize

Describe alternatives you've considered
No response
Additional context
No response

I can add __managed__ as this is probably required to parse the CUDA code correctly. But about the built-ins, what do you exactly want this grammar to provide? Do you want to have them highlighted? Hightlights should be done in the queries for your favorite editor.

I can add __managed__ as this is probably required to parse the CUDA code correctly. But about the built-ins, what do you exactly want this grammar to provide? Do you want to have them highlighted? Hightlights should be done in the queries for your favorite editor.

Hi:
Actually the main concern are the types because Emacs handles those conceptually:
The definition is actually pretty simple; something like:
cuda_primitive_type: _ => token(choice(
	    'dim3',
	    ...[1, 2, 3, 4].map(n => `int${n}`),
	    ...[1, 2, 3, 4].map(n => `uint${n}`),
	    ...[1, 2, 3, 4].map(n => `short${n}`),
	    ...[1, 2, 3, 4].map(n => `ushort${n}`),
	    ...[1, 2, 3, 4].map(n => `long${n}`),
	    ...[1, 2, 3, 4].map(n => `ulong${n}`),
	    ...[1, 2, 3, 4].map(n => `char${n}`),
	    ...[1, 2, 3, 4].map(n => `uchar${n}`),
	    ...[1, 2, 3, 4].map(n => `float${n}`),
	    ...[1, 2].map(n => `double${n}`),
	))

And then just need to extend the primitive_type of c/c++ grammar to include those as well.

 Why build that into the parser? I only added modifiers that would otherwise destroy parsing of regular C++ code. Matching something like dim3 or float4 is something for the queries.


chore: comment out test job

Comment out test job.
The display of testing tasks in the production environment is confusing. https://prow.tidb.net/?job=echo-test.

/approve


Update electron to 11.4.8

Details
Updates Electron.js to 11.4.8
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/165490
Fixes https://github.com/Expensify/Expensify/issues/165489
Fixes https://github.com/Expensify/Expensify/issues/165488
Fixes https://github.com/Expensify/Expensify/issues/165487
Fixes https://github.com/Expensify/Expensify/issues/165484
Fixes https://github.com/Expensify/Expensify/issues/165483
Fixes https://github.com/Expensify/Expensify/issues/165480
Fixes https://github.com/Expensify/Expensify/issues/165479
Fixes https://github.com/Expensify/Expensify/issues/165478
Fixes https://github.com/Expensify/Expensify/issues/165477
Fixes https://github.com/Expensify/Expensify/issues/165473
Fixes https://github.com/Expensify/Expensify/issues/165469
Fixes https://github.com/Expensify/Expensify/issues/165467
Fixes https://github.com/Expensify/Expensify/issues/165466
Fixes https://github.com/Expensify/Expensify/issues/165465
Fixes https://github.com/Expensify/Expensify/issues/165464
Fixes https://github.com/Expensify/Expensify/issues/165463
Fixes https://github.com/Expensify/Expensify/issues/165462
Tests

Run the desktop app with npm run desktop, and try to do a full regression test. Try sending messages, attaching images, clicking on links, opening and closing modals, etc... be sure to click on a link in a chat and and external link outside the chat (for example, Settings -> About -> View Code. Also close the app and restart it.
Run a local staging build of the desktop app by running npm run desktop-build. If you've got the staging app installed, uninstall it by dragging it to the trash. Once the local build finishes, double-click on the file that's created at dist/Expensify.cash.dmg. Finish the installation and the repeat step 1 with the locally-built desktop app.

QA Steps
Please perform exploratory testing on the first version of the desktop app including this PR in addition to the regular regression tests.
cc @Expensify/applauseleads - Please let me know if there is a process through which I should request exploratory testing.
Tested On

[ ] Web
[ ] Mobile Web
[x] Desktop
[ ] iOS
[ ] Android

Screenshots
Desktop

🚀 Cherry-picked to staging in version: 1.0.62-7🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Well, that's not right ... 🤔

@roryabraham Are there any specific areas in the app that are being affected by this PR? I can give some instructions to the team for the exploratory but if would be great to have a to have a focus.

Unfortunately this affects the whole desktop app, but some things we could focus on are things that are specific to desktop only, such as the MacOS system menus, window resizing and the custom status bar, hotkeys, auto-updating, closing and relaunching the app, etc...

🚀 Deployed to production in version: 1.0.64-0🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


ccm doesn't seem to work with version 4.0-rc1

CCM doesn't seem to work with the following...
ccm create test -v 4.0-rc1

13:23:22,354 ccm WARNING Downloading 4.0-rc1 failed, trying to build from git instead.
The error was: Invalid version 4.0-rc1 (underlying error is: HTTP Error 404: Not Found)
https://gitbox.apache.org/repos/asf/cassandra.git git:cassandra-4.0-rc1

The archive is available at http://archive.apache.org/dist/cassandra/4.0-rc1/

Works with 4.0.0....
ccm create test -v 4.0.0
10:57:35,385 ccm INFO Downloading http://archive.apache.org/dist/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz to /tmp/ccm-nnhb03n8.tar.gz (44.386MB)
  46541792  [100.00%]10:57:39,458 ccm INFO Extracting /tmp/ccm-nnhb03n8.tar.gz as version 4.0.0 ...
Current cluster is now: test


Sandboxed systemd service

Should resolve #312, relates to discussion #51. Attempts to sandbox chiadog as a systemd service, and safeguard any sensitive chia files in .chia/mainnet that we don't need access to.

Add a scripts/linux/chiadog.service systemd example that attempts to run chiadog in a more isolated environment. Create a new limited user each run (making much of the filesystem readonly), and set .chia/mainnet folders other than log to inaccessible.
Move the offset file - previously, the debug.log.offset file was kept in the chiadog directory, but when running in a read only filesystem we can't write there. Create a temporary directory when running, and store the offset file there. This also means we no longer need to delete the offset file on startup.

A good way to test this is to switch out the ExecStart for an ls -lh .chia/mainnet and see what files are accessible inside the environment, or try to run venv/bin/chia wallet show inside and make sure it fails. Ideally I'd like to have chiadog show a warning when it starts up if it's able to access configuration directories, but I figure that could be added in another PR.
There are a bunch of different strategies in systemd for setting this up, I went with what seems to be the most compatible version (compatible with systemd 235, which I believe is available in Ubuntu 18), explicitly declaring InaccessiblePaths. The other way, using TemporarilyFilesystem to block everything out and binding the one file we need, is maybe a bit more elegant, but needs at least systemd 238 (around Ubuntu 20). Since it's not possible to say "make everything except the logs folder inaccessible" however (declaring .chia as inaccessible makes all child directories inaccessible and can't be overridden by other directives), we need to remember to add any new paths if new versions of chia add additional directories we don't want access to.

Hi @alexking,
this was really delightful to review, really appreciated the detailed documentation and careful considerations. 👍 💯
I'll go ahead and merge this into dev, and it'll make it into the final release for 2021 :-)
Thanks!

Thanks! Also I just noticed that Chia is migrating their keys to ~/.chia_keys, so I'll submit another to include that as inaccessible.


Deprecate enum

Should enums be marked as deprecated or not recommended to use?

Enums are not deprecated and there are no planes to depreciate them either.

@mhegazy maybe some updates to the docs, since they are not working properly?

Working properly in what sense?

@DanielRosenwasser https://github.com/vkurchatkin/typescript-vs-flow/blob/master/ts/4.ts

This is working as intended to support flag enums.. consider:
enum flags {
    red = 0x0001
    round = 0x0010;
    hasSeeds = 0x0100;
}

declare function isValid(flags: Flags): booelan;

isValid(/*tomato*/ 0x0111) // true;

So if all what you want is a set of literals, do not use enums. use union types.. e.g.
export function test(v: 1 | 2 | 3 | 4) {
}

test(100); // Error

you could give them symnbolic names if you want, and still use union types:
type Up = 1;
type Down= 2;
type Left= 3;
type Righ= 4;

export function test(v: Up | Down | Left | Righ) {
}

This is working as intended to support flag enums

It makes enums essentially this:
type  Flags = number;
const red = 0x0001
const round = 0x0010;
const hasSeeds = 0x0100;

Enum has two uses, one as a collection of constants, as you point out, and the other as a type. Number is allowed to allow for flag enums, and to allow for numeric manipulations on enum values.
If you need a closed set of constants, use literal types.

not being able to have enums as static properties on a class is annoying.
e.g.
class Drink {
  static enum Size {Small, Medium, Large}
}


Request: Patches that have been "Checked" marked different than Completed

Love the plugin and the idea behind it! But i really wanted it so that at a glance I could know what patches need to be reset to be "pre-planted" for Farming Contracts.
I just check-healthed my Potato Cactus and it doesnt change in the plugin until I pick all the cactus and remove it. Could there be a status for patches with a "Check Health" to be like "Checked" or something?

Sure! I'll see if I can update it during the week, otherwise I'll update it next weekend.
Until then, make sure to empty your patches immediately ;-)

I've updated the plugin to include the "Checked" state. You can also pick your own colors when runelite has approved the changes to the plugin.
https://github.com/runelite/plugin-hub/pull/6869 when this is merged you can use the updated plugin!


Support cf docker builds

Is there a related GitHub Issue?
#2823

What is this change about?

Support CFBuilds with docker lifecycle
Remove logging tests

Does this PR introduce a breaking change?
No

Acceptance Steps
See #2823

Tag your pair, your PM, and/or team
@danail-branekov

@danail-branekov @georgethebeatle The logging tests were introduced as part of #2540. The helper functions in the controllers use logr.FromContextOrDiscard() to extract the logger from the context, and @kieron-dev and I felt that it would be too easy to break logging by not attaching a logger to the context in the controllers' ReconcileResource() functions so we decided to add these tests to confirm that everything is wired together correctly.


User setting ignored if pcre2 is available

Proposed change

Currently cannot use yaml-bare/:tag: if pcre2 is available. This change makes it look to the config setting first.
Type of change

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (thank you!)
[ ] Code quality improvements to existing code or addition of tests
[ ] Documentation update

Additional information

This PR fixes or closes issue: NA
This PR is related to issue: NA

Checklist

[x] I am running the latest version of the plugin.
[x] The code change is tested and works locally.
[x] There is no commented out code in this PR.
[x] The code has been formatted using Stylua (a .stylua.toml file is provided)
[x] The code has been checked with luacheck (a .luacheckrc file is provided)
[x] The README.md has been updated according to this change.
[x] The doc/telekasten.txt helpfile has been updated according to this change.

Indeed! Thank you very much for fixing my mistakes :smile:


Nether portal can only be lit with flint and stell.

Cannot be lit with fire charge and natural file which make it hard to create nether portal for skyland players

Do what the vanilla nether portal does and instead of listening for flint and steel, activate if any fire ever reaches the inside of the portal.
That way dispensers can light portals, maybe explosions that create fire, fire charge, etc.


Panic Crash

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xc31bf5]
goroutine 6184 [running]:
main.(*peer).logWireMessage(0xc420271080, 0x14a3a00, 0xc42090e300, 0x14a3a01)
/home/ubuntu/projects/lightning/src/github.com/lightningnetwork/lnd/peer.go:930 +0x965
main.(*peer).readNextMessage(0xc420271080, 0x0, 0xc4205ecce8, 0xc4205ece78, 0xc4205ecce8)
/home/ubuntu/projects/lightning/src/github.com/lightningnetwork/lnd/peer.go:457 +0x172
main.(*peer).readHandler(0xc420271080)
/home/ubuntu/projects/lightning/src/github.com/lightningnetwork/lnd/peer.go:656 +0x18f
created by main.(*peer).Start
/home/ubuntu/projects/lightning/src/github.com/lightningnetwork/lnd/peer.go:286 +0x83f
Running 7a3116f8a97223bb8403aedb058bb4a6f0417eca

Ah, guessing you were connected to either eclair or c-lightning as I'm not sure if both of them have properly implemented the data loss protection option. Will fix!


Why am I receiving an error when trying to create a property?

Thanks for stopping by to ask us a question! Please make sure to include:
Thanks for creating this awesome library!
- What you're trying to do
I'm trying to create a property using the @google-analytics/admin package on npm.
- What code you've already tried
const [response] = await analyticsAdminClient.createProperty({
parent: 'accounts/261520513',
property: { displayName: 'yoyo', timeZone: 'America/Chicago' },
});
- Any error messages you're getting
3 INVALID_ARGUMENT: The value for the 'parent' field was invalid but must be in format 'accounts/123'.

This worked
const [response] = await analyticsAdminClient.createProperty({
    property: { parent: 'accounts/261520513', displayName: 'yoyo', timeZone: 'America/Chicago' },
  });


Apply infinite scroll to search page

I hope you apply infinite scroll to the search page instead of loading the whole result for better performance.

Sounds like a good idea, there's definitely some perf to be gained by preventing adding items that aren't on screen.
Be careful of the async enumerable which is returning items one at a time as soon as they're ready.

Async Enumerable solves this problem


Release 0.2.0

@JuliaRegistrator register(branch=release)

Registration pull request created: JuliaRegistries/General/1328
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" a46e09423d57f9868685e0c93d7fa16ab44c88ff
git push origin v0.2.0


[ENH] WindowSummarizer inputs for lag_config

Is your feature request related to a problem? Please describe.
I am sorry, I am not able to find where this was discussed earlier, but I finally got to test this out in 0.10.1. I have some observations and feedback. Please feel free to chime in.
import pandas as pd
from sktime.transformations.series.window_summarizer import WindowSummarizer
from sktime.datasets import load_airline

y = load_airline()
kwargs = {
    "lag_config": {
        "lag": ["lag", [[1, 0], [5, 0]]],
        "mean": ["mean", [[3, 0], [3, -1], [12, 0]]],
        "std": ["std", [[4, 0]]],
    }
}
transformer = WindowSummarizer(**kwargs)
y_transformed = transformer.fit_transform(y)
pd.concat([y, y_transformed], axis=1)[:20]

Describe the solution you'd like
Observation 1:
It seems that the window starting is not referenced to the current data point but rather the 1 period prior. So if I want to get the mean of last 3 values (including current value), I need to specify [3, -1]. This seems quite odd. I would have thought [3, 0] would have made more sense, i.e. window size of 3 starting at the current value (0).
If I wanted the window size of 3 starting at prior value, I would specify [3, 1] in that case which again is more intuitive to me.
So in this case, the interpretation would be [window_length, starting_at (w.r.t **current** data point)] vs. the way it is implemented which is [window_length, starting_at (w.r.t **prior** data point)].
Observation 2:
For "lag" feature, the window length currently does not have any significance, i.e. [1, 0] gives the same results as [5, 0]. So instead of [window_length, starting_at], maybe this should be interpreted as [lag, starting_at]. With this,
[1, 0] would mean the 1st observation prior to current (lag 1 in the true sense of it)
[5, 0] would mean the 5th observation prior to the current (lag 5 in the true sense of it)
[1, 2] = [3, 0] would mean the 1st observation prior to the 2nd observation prior to the current observation (lag 3 in the true sense of it).
I feel this nomenclature is more intuitive, but that is just my opinion. Feel free to chime in if this would be feasible and easier to understand.

This seems quite odd. I would have thought [3, 0] would have made more sense, i.e. window size of 3 starting at the current value (0).

Yes, agreed!!
I have had long discussions with @danbartl about this, and he was adamant about that you suggested the convention that leads to the "-1". This is quite funny 😆 since your comment confirms it must has been some kind of miscommunication.
Anyway, we have jointly agreed that we will change it to "0 lag means output = input time series", and that the current situation has the status of a bug because there is such a strong user expectation.
Unfortunately, @danbartl is off sick, so the fix might not make it into 0.11.0.

(the work is being carried out in this PR https://github.com/alan-turing-institute/sktime/pull/2154)

Thanks @fkiraly . Yes, it might have been miscommunicated/misinterpreted. But I am glad that the change is happening now.
Just so we avoid miscommunication again, could you clarify what you mean by the following. I am not sure I follow that.

"0 lag means output = input time series"

@fkiraly Also, would this change apply to "Observation 2" as well (for lags) or only for functions like "mean", "median", etc.?

@ngupta23, regarding observation 1: this is one of those things where you get more confused the more you look at it...
If you had the time, I would much appreciate if you could look into the docstring of the PR
https://github.com/alan-turing-institute/sktime/pull/2154/files
and check whether the indexing is now "right" in your opinion. And/or play around with it.
Re observation 2, indeed, we've discussed that it should be easier to pass lags, without the window_length number. I'm not sure whether that's already included in #2154 though.

@fkiraly I think it is still not consistent with what is proposed in this issue
https://github.com/alan-turing-institute/sktime/pull/2154/files#r835367534

@danbartl, appreciate your eyes on this once you are back...

Fixed by https://github.com/alan-turing-institute/sktime/pull/2316


Yatin: Watch officemyoffice.com

Yatin requests the watch of the watch_keyword officemyoffice\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

officemyoffice\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

officemyoffice\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Rejected by tripleee in Charcoal HQ. Reason: 'sorry, duplicated again (network trouble on my side)'

Rejected by tripleee in Charcoal HQ. Reason: 'sorry, duplicated again (network trouble on my side)'


[objc] Use enums instead of string values for platform/target/compilationtarget, and add initial scaffolding for iOS/watchOS/tvOS + framework support.

Build failed

Build and tests passed.


Add mediafuse

Domain(s) to be blocked?

player.mediafuse.com [see below]
hb.mediafuse.com

Where?
Found in Quartz site

https://qz.com/1802881

Who?
Mediafuse describes itself as,

We provide digital publishers with strategy, operations, and technology to maximize advertising revenue. Our unique approach combines a team of programmatic yield managers, consultants, ad tech developers, ad operations, and propriety ad technology.

Before you add,
Just confirm if the player subdomain is necessary for the news site to display any videos or it's just used for irrelevant video ads.
hb subdomain is definitely used for ads, as seen on the HTML of the site linked above

@StevenBlack, maintainer of "shady-hosts" list @shreyasminocha added above mentioned domains in commit https://github.com/shreyasminocha/shady-hosts/commit/9269b3fee135adc4195ce371e4f50beb46c25673


Add Praeco to README

👋 I thought it would be good to add Praeco to the README alongside the kibana plugin. It's come along quite a ways and is pretty full-featured now!

Given the recent Amazon news with Open Distro for Elasticsearch, it might be good to add Praeco to the Elastalert README to show Elastalert already has a rich GUI with way more features ;)
https://github.com/ServerCentral/praeco
https://opendistro.github.io/for-elasticsearch/features/alerting.html
☮


title from package.json?

can we set the 'name' in package.json as the window title?

This should work (put it as the "template" in the package settings):
<% var packageName; try { packageName = JSON.parse(require('fs').readFileSync(projectPath + '/package.json', {encoding: 'utf8'})).name; } catch (e) { packageName = ''; } if (packageName) { %><%= packageName %><% } %>

It will attempt to read and parse the package.json at the root of the project (i.e. opened folder) and take the name from there.


Listen on multiple addresses for the APIs

Listening on multiple addresses for both the HTTP and PG API can simplify deployment scenarios where an API needs to be locally accessible (e.g. <IP_ADDRESS>), but also externally accessible without opening it to <IP_ADDRESS> or ::.

Fixed in #195 and #196


add xlsx import support using openpyxl

Hi!
Added xlsx support to django-import-export.

Thanks @shalakhin
I have rebased your changes and did a little cleanup for importing openpyxl. Please check it, if everything is ok I'll release it.

@bmihelac you are welcome!

@bmihelac can you add me to contributors list please? Forgot to add myself

sure thing, added!

Thank you! Have a nice day!
On 18 груд. 2015 12:46 +0200, Bojan<EMAIL_ADDRESS>wrote:

sure thing, added!
—
Reply to this email directly orview it on GitHub(https://github.com/django-import-export/django-import-export/pull/367#issuecomment-165745209).


[#22] | add statistic result

title: Issue #22 | add statistic result

What type of PR is this? (select all that apply)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 🚧 Breaking Change
[ ] 🧑💻 Code Refactor
[ ] 📝 Documentation Update

Description

create result page for showing user statistic data
I use chart.js for statistic data

The stats data is still dummy, I have not connect to db yet.

Related Tickets & Documents

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings

UI accessibility concerns?

Added/updated tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

I made the dashboard using recharts, how about we just use recharts since its pretty easy and looks nice.

I made the dashboard using recharts, how about we just use recharts since its pretty easy and looks nice.

ohh so that is ur pr for issue #58, is that included the issue #22?

hold for merge

@webdevcody ready for merge


chore(package): update puppeteer to version 1.18.1

 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.


#006: Add Input Parameter to can define variables

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

19 of 20 (95.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+6.8%) to 97.297%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

entrypoint.py
11
12
91.67%

Totals

Change from base Build<PHONE_NUMBER>9:
6.8%

Covered Lines:
36

Relevant Lines:
37

💛  - Coveralls


feat(mobile): add proper styles for mobile version

Extract footer filter to its own component, fix checkbox issue where it didn't look exactly round

Closes #15