optimization: Compute derived props in componentWillReceiveProps not render

Render may run more often than componentWillReceiveProps. So any computation on incoming props can be computed in the constructor and componentWillRecieveProps. Once computed it may be stored as component instance attributes (assigned to this). Those derived props assigned to this can then be used in render.
I haven't benchmarked anything so I don't have a good sense of the savings but if I am working in dash-renderer (likely because I am doing that now) I'll use this issue to remind myself to offer up some examples.

This pattern is used in many places already so I am going to close this issue.


Certain sounds aren't working

https://github.com/jenius-apps/ambie/assets/152641387/4e68220a-c6d8-4be9-82c3-ed27a930c493
Certain sounds downloaded from the catalogue doesn't work

I'm not able to reproduce on my machines. Can you try reinstalling ambie, downloading one sound, and then letting it play?

Uploading Ambie2Short - Made with Clipchamp (1).mp4…
I've tried reinstalling twice. The issue's still there on my device.

https://github.com/jenius-apps/ambie/assets/152641387/d7f7c6e6-175b-4425-925a-fef9f2e690e9
I've tried reinstalling the app twice. The issue's still there on my device.
(I've sped up the video to compensate for slow download speed)

Hmm, this is strange. Can you share more information about your device?

OS version
device model
How many hard drives do you have on the machin? E.g. C:, D:\ = 2 drives
And which drive did you install ambie in?

OS Version: version 23H2 (0S Build 22631.3007)
Device Model: Acer Nitro 5 (AN515-44)
No. of Hard drives: 3
Ambie is installed in C drive

I have this issue too. on sounds like turning pages, library, cicadas and more

update: uninstalling and installing ambie again fixed the issue


XXX log google API responses to see why CI is failing, for example at https://github.com/josephfrazier/Reported-Web/runs/4343144637?check_suite_focus=true

heh, of course it would start passing once I start looking at it. Guess it's just flaky, maybe rate-limiting on Google's end?


Respect inclusive upper bound style in requirements.txt files

Fixes #5149.

I think we should ship this as-is, and can iterate on it further down the road based on user feedback.


Add retryable http client option

Since Symfony 5.2 it's possible to add a retrying strategy
I'm wondering if we should add the same option or let the hand on "root" http client configuration used by the end user.

@ismail1432 I am not sure about this feature. In my opinion the gloabl (root ) configuration is the better option. But it could be added to the docs of this repo to make developer aware of this retrying strategy.

Yes indeed, as you can configure whatever HTTP client that will be used thanks to api_platform_ms.http_client, I don't think this feature is necessary.
We can effectively be more meaningful in our documentation by showing an example of a custom HTTP client configuration and injection. But IMHO we should not focus only on retry.

Actually, it could be seen in:

https://github.com/mtarld/api-platform-ms-bundle/blob/master/README.md (configuration)
https://github.com/mtarld/api-platform-ms-bundle/blob/master/src/Resources/doc/tools/http-wrapper.md

I'm gonna close it, but feel free to open it again if you think it's still not enough :slightly_smiling_face:


Fix conditinal request expiration

Closes #464

Update CacheMixins _send_and_cache function to save CachedResponse with updated expiration date upon received 304 before returning the cached value.
Update BaseCaches save_response function to only create a CachedResponse instance if the argument is not already of type CachedResponse

Could you add a unit test for these changes? Also, looks like the test for immediate expiration (max-age=0 plus a validator) is currently failing.

Thanks a lot for the review! I implemented your suggestions with a few twists:

Instead of just returning the original CachedResponse object from the "from_response()" class method I create a copy of the object using attr.evolve. I guess users would not expect builder class methods like from_response to return the very same object but create a new one that can be modified without affecting the original.
According to the RFC mentioned in #464, we should update the actions variable using the combination of cached response and "Cache-Control" headers present in the 304 response. I thus added another actions.update_from_response() call if the response is in fact a 304 Not Modified.
I added a unit test that verifies the behavior explained above (i.e. the server relaxing max-age with its 304 response from 0 to 60s) and makes sure the Session doesn't try to re-validate for another max-age seconds.

With the changes outlined above, the regression on the test_conditional_request__max_age_0 test should have been resolved as well.

Merged. Thanks for the contribution!
Looks like tests for python 3.9 are failing, but I believe that's an issue with the build environment and not related to your changes. I'll fix that.

@meggiman Your changes are now in pre-release version 0.9.0dev2!

Awesome! Thanks a lot for being so quick to react to this issue and for this awesome project in general. It really saved me from a lot of trouble!


EPR MAG update

Summary
Updates to align with new guidelines website.
Details
These changes update URLs and align with a couple of minor title and section changes within the new guidelines website. The only potentially disruptive change is the moving and renaming of 'Managing focus' in 'Forms' section to become 'Changing focus' in 'Focus' section.
Motivation and Context
Issues #295  and #294 are relevant and both connected to the BBC accessibility guidelines moving to a new website.
How Has This Been Tested?
No tests have been run yet. This is a draft pull request to enable that to happen.
Types of changes

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

Checklist:

[ ] I've added tests for my code
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Thanks for the additional changes @llouisetaylor looks like I missed a few. Looks like the CI checks are still failing. I'm wondering if related changes are needed in the checks... thought detail implies it can't load electron (CI stuff is definitely not my area of expertise).

The above changes fixed 5/6 of the failing tests. The remaining test I had been struggling to understand:
Error: Failed to answer "Are actions triggered when appropriate for the type of user interaction?" with "Yes"
       Text in answer frame:
       Does focus or context automatically change during user input?

       No (or not applicable)Yes

I wonder if that's one of the non-automated tests mis-matching with something that has been changed. It is odd.

@andymsuk or @jroebu14 would one of you be able to help @llouisetaylor with the final failing test of this PR?


Minor naming changes in Shared FileSystems 4.20 Feature

Description
This PR fixes..

Change the UI tab name from Shared FIlesystem to Shared FileSystems
Rename Shared FileSystem VM to Shared FileSystem Instance
Remove create view table from schema-41910to42000 as it is not required.

Companion doc PR : https://github.com/apache/cloudstack-documentation/pull/435

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[x] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@abh1sar a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11104

@blueorangutan test

@abh1sar a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

@blueorangutan package

@JoaoJandre @rohityadavcloud
This PR contains some minor cosmetic changes related to naming conventions for the Shared FileSystems feature we are shipping in 4.20. But I think it has high impact in terms of user experience and clarity.
For example,

it is little jarring to see 'Shared FileSystem' as the only tab which is singular in UI. All other tabs ('Volumes', 'Snapshots' etc) are plural.
Cloudstack has the convention of calling user VM Instances, which we should maintain for Shared Filesystems VM as well.

The other small change is to just remove the user_vm_view definition from upgrade path, as we have separate files for creating views.
Can we please include this in 4.20.0?

@abh1sar as long as this is reviewed and tested, I think it's okay but since freeze is declared - it's upto our release manager @JoaoJandre to review and approve/merge.
I like that we've dropped the unnecessary views changes as they're not kept in separate file, LGTM overall.

@blueorangutan test

@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

@blueorangutan ui

@borisstoyanov a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/9675 (QA-JID-446)

[SF] Trillian test result (tid-11465)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 55009 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9675-t11465-kvm-ol8.zip
Smoke tests completed. 140 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_redundant_vpc_site2site_vpn
Failure
455.63
test_vpc_vpn.py

[SF] Trillian test result (tid-11466)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 52358 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9675-t11466-kvm-ol8.zip
Smoke tests completed. 141 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File


l not post api after clone project from git ( “CSRF token mismatch.” ) laravel 6.0 on mac os x

Laravel Version: 6.0
PHP Version: 7.3.9

Description:
l not post api after clone project from git ( "CSRF token mismatch." ) laravel 6.0 on mac os
Steps after clone
1.composer install
2.npm install
3.Create a copy of your .env file 4.php artisan key:generate
Post api format
General
Request URL: http://<IP_ADDRESS>:8000/login
Request Method: POST
Status Code: 200 OK
Remote Address: <IP_ADDRESS>:8000
Referrer Policy: no-referrer-when-downgrade
Response Headers
Connection: close
Content-type: text/html;
charset=UTF-8 Date: Fri, 13 Dec 2019 03:05:21 GMT Host: <IP_ADDRESS>:8000
X-Powered-By: PHP/7.3.9
Request Headers
Accept: application/json, text/plain, /
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9,th;q=0.8
Connection: keep-alive
Content-Length: 84 Content-Type: application/json;charset=UTF-8
Cookie: XSRF-TOKEN=eyJpdiI6IkxaNDc4UkdKQ0FJeDNxR0tVT3dEcmc9PSIsInZhbHVlIjoiTjdKQUo1OUNKV3ZmXC9NNnEreGdyNmtueVVYaVVseGVzeFAxanF2aFlyWm9nUVpKMm1EdlBaMTlaNFZQN0lHaFYiLCJtYWMiOiI4Y2M0ZTQ2YzNiMTllYzhiMWJhMTY0OTM4NDFhMmUwZmNmMTg2YWUxYWZkYTJiMzk1NGNhYTA0OWE2OGY0MmY5In0%3D; laravel_session=eyJpdiI6IlkyVjduS3ZMUnN2NU5tSHRxYURBSkE9PSIsInZhbHVlIjoiVVducUtRXC9xMHc0SGdvUEhqdlBTM2g1NTBscUw2MzdhRkR3RWxvZEtzajRrd2tvOEQwVURqcHViXC9RRDlTS3FDIiwibWFjIjoiZDNiZTA1M2I1MDkzZDM4ODQ3NTY4ZTQ2NjE0NGYzN2E0ZTRjNGMzYjU0OGQyNTNhZWIxYTRmMWVlNDhiNmFiNyJ9
Host: <IP_ADDRESS>:8000
Origin: http://<IP_ADDRESS>:8000
Referer: http://<IP_ADDRESS>:8000/
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
X-CSRF-TOKEN: TaSalYsNVkqlI37gaRCKKw6QNzJE9UwyPKNISzV2
X-Requested-With: XMLHttpRequest
X-XSRF-TOKEN: eyJpdiI6IkxaNDc4UkdKQ0FJeDNxR0tVT3dEcmc9PSIsInZhbHVlIjoiTjdKQUo1OUNKV3ZmXC9NNnEreGdyNmtueVVYaVVseGVzeFAxanF2aFlyWm9nUVpKMm1EdlBaMTlaNFZQN0lHaFYiLCJtYWMiOiI4Y2M0ZTQ2YzNiMTllYzhiMWJhMTY0OTM4NDFhMmUwZmNmMTg2YWUxYWZkYTJiMzk1NGNhYTA0OWE2OGY0MmY5In0=
error message
exception: "Symfony\Component\HttpKernel\Exception\HttpException" file: "/Users/sarun/Documents/GitHub/lottothai-frontend/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php"
line: 223
message: "CSRF token mismatch."
The same code can be used normally on windown.
But the difference on windown
**Response Headers
Set-Cookie: XSRF-TOKEN=eyJpdiI6IjErRkVVSUhxclhWbHBvOEtXMFd2Mnc9PSIsInZhbHVlIjoidzNwejVHc21qUzl5Yk9sVFE5QkxhbFpDdjl3OGVJNG1yMmZGdW4zWXBHMkFJNXR2NWVYTVZGbzVOOVwvN0hnQjMiLCJtYWMiOiI0ODQzMzMwMWE1OGIwMjQ2ZTJmYjExZGIyODlmN2RlMDQ5M2Q4NjFmNDk5MjI1OTI5NGIyZjQwMjFjN2VlNjU2In0%3D; expires=Fri, 13-Dec-2019 05:34:01 GMT; Max-Age=7200; path=/
Set-Cookie: laravel_session=eyJpdiI6Ik84SmFleElLaWd4alJvM2NYa2hIdlE9PSIsInZhbHVlIjoic2ZPaW0yd3kwMkVlUWRmZ29rQnBKZlBadTh1N2J2Slpkd3dvcnpYbkE2UU45WkZCXC9vYUNxbXJra0NuMUJYNVYiLCJtYWMiOiJjZmY0NWJlNmQ4ZTQyYTY2MzhjZWRlZWE2MDNmNTI3YTYwOGI3OWQ2NjNjMzU2ZjhlMDgzMzE1NGY2YmVjY2ZhIn0%3D; expires=Fri, 13-Dec-2019 05:34:01 GMT; Max-Age=7200; path=/; httponly
But on the mac os the clone came down, not in this section**
Please help me. Thank you.
Steps To Reproduce:

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Remove unsafe and Unpin

This PR replaces the unsafe code with its safe equivalent.
Mutating operations on *mut Router<B, E> assume a single unique mutable reference, which presumably was guaranteed in some way before this PR. This PR replaces the unsafe implementation with a shared mutable reference whose semantics are enforced by the compiler.
Additionally the Unpin constraints that were bounding many of the generics in this library are no longer necessary.

Bumping this thread again as I'd like to discuss your concerns with the soundness of the current unsafe code. The original author of the code has not provided any guarantees (or the typical /// SAFETY: ... code comment explanations) as to the soundness and safety of the current usages of unsafe...


Improve docker documentation

I made some changes to the documentation with regards to Docker to make things a bit more clear.

Instruct the user to load the ip_tables/ip6_tables instead of defaulting to the SYS_MODULE capability. Added instructions about running with SYS_MODULE if needed.

This seems like the more proper/safe way to run the container, so I think this should be the default recommendation.

Change docker-compose.yml in accordance with above.

Also removed the top-level named volume. The volume driver should be local by default, so I don't think this is needed.

Added IPv4-only docker-compose example.
Add warning to Docker section in README about SYS_MODULE.
Moved the Running on Kubernetes section in the README after the Docker-Compose section.

ERROR: Named volume "wg-access-server-data:/data:rw" is used in service "wg-access-server" but no declaration was found in the volumes section.

Even local volumes need to be declare in the volumes section of the compose file: https://docs.docker.com/compose/compose-file/compose-file-v3/#volumes

Ah, right. I'm using a path based volume so I wasn't running into that.
Would it not be better to use/suggest a path based volume though? e.g.:
volumes:
      - "/path/to/wg-access-server-data:/data"

I suppose it doesn't really matter, but based on my somewhat limited Docker experience that it seems that doing so is the "standard".

No, I'd stick to a named volume. I wouldn't consider any of them more standard than the other, it's just two different things.
Bind mounts make sense if you want to access the data on the host, or have a custom storage structure preference. But we don't need the data somewhere specific on the host, and I wouldn't know a path where we should mount it to. A named volume works just fine, and if someone needs a bind-mount in their deployment they can configure it accordingly.

Gotcha, that makes sense, thanks.

Looks good. I'm going to add another little commit that fixes a link from #104 so the site builds successfully again.


Which docker image to use (needs bash etc)

I tried using an alpine image (which of course doesn't contain bash), but it also fails on the bigger amazonlinux:

FROM   alpine
FROM   frolvlad/alpine-bash
FROM   amazonlinux:2

I get error's like "bash not found" or "no such file":

[ERROR] An error occurred during execution of command [app-deploy] - [RunAppDeployPostDeployHooks]. Stop running the command. Error: Command .platform/hooks/postdeploy/00_ssl_setup_certbot.sh failed with error fork/exec .platform/hooks/postdeploy/00_ssl_setup_certbot.sh: no such file or directory

I would like to have an as minimal image as possible (no php etc) since I only need to host a golang executable.

@andremussche I just deployed this on an AWS Elastic Beanstalk Docker app (running Haskell), so I was in a similar situation as you where I didn’t want to use one of the specific platforms, e.g. PHP, Node.js, etc.
FWIW, I originally included .platform and .ebextensions inside my application Docker image, but that was a mistake! The EB runtime didn’t find the hooks and never ran them. I realized I have to package .platform and .ebextensions inside a ZIP file alongside Dockerrun.aws.json.
This means these hooks will run on Amazon Linux 2 which I confirmed works.
If you need a real-world example, check out: https://github.com/zoomhub/zoomhub/pull/151
@HausCloud On that note, consider your scripts to be officially tested with Docker as well! 👏
One remaining issue I ran into was that setting the cron tab didn’t work. I did some research and using crontab is more suitable for interactive / human use. I adapted your script to drop a file into /etc/conf.d which was easy to make idempotent without having to check the existence of the command using grep, etc.
Thanks for putting this together. As someone else said, I almost had tears of joy at 2:55am when the lock icon appeared after hours and hours trying to get this to work! 😂
Code: https://github.com/zoomhub/zoomhub/pull/151

@gasi Glad I could help! You're welcome to make a pull request and implement your adaptation :).
@andremussche Was gasi's answer help you fix your issue?

@andremussche I'll assume you found your solution in a couple days and close accordingly. I encourage you to share your solution, thanks.

I copied the changes done by @gasi so it works now!
https://github.com/HausCloud/AWS-EB-SSL/pull/11
(mainly bash and LF fixes)


Understanding GPIO Configuration

The book doesn't go into much depth on GPIO configurations. I think it deserves more attention, I have a pretty good grasp of it if you'd like to hear more when we meet. Reference Guide pg 228-244.

Something I didn't follow here was:

We are interested in the register that's at an offset of 0x18 from the base address of the GPIOE peripheral.

I was sort of with it until the 0x18. Where does that come from?

Yeah so the 0x18 is telling us what we are trying to do with the GPIOE peripheral.
For example: Page 237 11.4.1 is telling us that GPIOx_MODER can be set with an address offset of 0x00. These bits are written by software to configure the I/O mode.
00: Input mode (reset state)
01: General purpose output mode
10: Alternate function mode
11: Analog mode
Keep scrolling down and you see that 11.4.7 GPIO port bit set/reset register (GPIOx_BSRR) (x = A..H) with Address offset: 0x18, is how we can set the actual value of the pin with Sets (set to high voltage) and Resets (reset to low voltage).
GPIO port output data register (GPIOx_ODR) (x = A..H) with Address offset: 0x14, is essentially doing the same thing as BSRR allowing you to do a Set or Reset on each pin.

gotcha. and each of the GPIO{A,B,C,D,E,F} work in the same way, and are just hooked up to different things? And where I've hooked up the SWD pin to PB3 with the female-female wire, PB3 corresponds to GPIOB pin 3?

Exactly. The LEDs on our board just happen to be connected to GPIO port E.


Wrong or incomplete information about --parameters inline format

Hello,
As stated in a github issue:
https://github.com/Azure/azure-xplat-cli/issues/2070
Using Azure CLI with PowerShell, --parameters inline format should be (only one working):
'{\"ParameterName\":{\"value\":\"ParameterValue\"}}'
Each inner double-quote being preceded by a back-slash (may not be displayed above).
Documentation should be updated accordingly.
[Enter feedback here]

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

ID: 472d54cf-aef8-32eb-7ac2-e2999109b8bc
Version Independent ID: 9b6aa223-a71b-e2ad-962b-9535abd536c4
Content: Deploy resources with Azure CLI and Bicep files - Azure Resource Manager
Content Source: articles/azure-resource-manager/bicep/deploy-cli.md
Service: azure-resource-manager
Sub-service: bicep
GitHub Login: @mumian
Microsoft Alias: jgao

@QuiteNewbieButImproving Thanks for your comment. We will review the issue and get back to you shortly.

@QuiteNewbieButImproving - thanks for your feedback. I have confirmed that the documented syntax works. You might be seeing the error if you are using an older version of Azure CLI. It looks like the parsing of parameters was improved in 2.0.12.

Hi Tom, thanks for the feedback. I agree with you, BUT...
I just verified I am using Azure CLI 2.26.0 which is more recent than the mentioned change in parsing parameters.
I noticed there is a difference when entering inline parameters directly on command line, or through a PowerShell variable (considering roles of and escaping quote:' and double-quote:")...
For example, in my case:
$DestResGrp = "Eval-InfraAsCode"
$BicepTempl = ".\POC_Datalake.bicep"
$paramstr = '{ \"isDev\": {\"value\":true}, \"custPrefix\": {\"value\":\"mycus\"} }'
az deployment group validate -g $DestResGrp -f $BicepTempl -p $paramstr
Evaluates and operates as expected...
Changing the variable $paramstr to comply with the syntax in the documentation:
$paramstr = "isDev=true custPrefix='mycus'"
I am prompted for a value for custPrefix whereas it is provided...
Clearly the parameters are not understood...
Not using a variable for parameters to stick furthermore to documentation, I tried:
az deployment group validate -g $DestResGrp -f $BicepTempl --parameters isDev=true custPrefix='mycus'
I agree it does evaluates and operates as expected, but I desperately require than my parameters are specified via a variable since there is a global surrending context when deploying my application..
Thanks for your time...

@QuiteNewbieButImproving - thanks for that info. I have added an example that shows using a variable for parameters. It should get published later today.
#please-close


[BUG]: Assign Role Flow Failing on Security check

Describe the bug
I have given myself every possible security role available and still fails saying that I do not have the correct permissions.  Error code is as follows.
RetrievePrivilegeForUser: The user with id 254b25f8-12d3-eb11-bacc-0022481eac35 has not been assigned any roles. They need a role with the prvReadUser privilege.
Component (please tell us which flow or app you are experiencing issues with):

Solution Power Platform GitHub ALM
Version <IP_ADDRESS>
App or Flow Assign Role Flow

To Reproduce
Steps to reproduce the behavior:

Create Project
Approve project via approval email
Fails one you get to assign role flow.
See error

Expected behavior
Project environment should be created and sandbox enabled for development
Screenshots

Additional context
I have given the user account all security roles trying to find correct level of privilege with no avail.

We have moved to a new dedicated repository for the CoE Starter Kit, and issues here will no longer receive attention. Please raise your issues here from now on:
https://github.com/microsoft/coe-starter-kit/issues


Ignore clangd index

Ignore files generated by clangd when it is launched with the source root as
current working directory.

@swift-ci please smoke test

⛵


Enable exponents for scientific notation

We could expand the factor parameter, or simply add a new parameter for the integer exponent.

Featured in 1.0.1

Featured in 1.0.1

Fixed in #5

Fixed in #5


Allow uploads of files bigger than 2GiB

This PR corrects the use of Int in prisma to be used as BigInt. This PR creates the needed migration (pretty much as @the-P1neapple states in #459).
This PR also corrects the types and introduces what I would call required jank in index.ts. This is a similar approach to what Prisma recommends developer do when working with BigInt's: https://www.prisma.io/docs/concepts/components/prisma-client/working-with-fields#serializing-bigint
The only problem is that next doesn't know how to deal with these BigInt's too so I resorted to that jank.
I tested this with my own image (ghcr.io/kashalls/zipline:trunk-3.7.5-test.2) and was able to verify a iso upload of 3GiB would go through. I have not been able to test larger files as I lack the memory it requires to store and combine these files at the same time. (When uploading it stores it in memory unless you have a tmp folder override, it also needs to combine these chunks into the end file which essentially means: File Size x 2 = Memory Requirement?) Idk its late and I don't know why i decided to do this now.
This fixes #459.

@kashalls update branch to upstream

@kashalls update branch to upstream

👍🎉


Reduce number of roles?

Is this feature request related to a new or existing Amplify category?
api
Is this related to another service?
No response
Describe the feature you'd like to request
I notice that Amplify creates a lot of roles. My project has already 50 roles. Amplify creates for example a role per function and per graph table with IAM. If we should deploy the app to multiple domains/environments then we could hit the limit of 1000 roles (expandable by request to 5000).
Describe the solution you'd like
For GraphQL API I can not see the need for a role per table with IAM auth. There should be possible to have a common role with a resource array with each table arn?
Function roles is more tricky, but I think you should see if there is possible to combine them?
Describe alternatives you've considered
Common role for API with tables with IAM
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

Hi, I am suggesting you create different AWS accounts for each environment. So it will be better isolation for each environment and you will have less trouble regarding limits. Of course your cost will increase if you are using additional services opensearch, EC2, RDS database

Hey @bergmorten, thank you for reaching out. marking this as feature-request for the Amplify team to evaluate the improvement.


Add MKL documentation

Description
Add a documentation for MKL integration
Checklist
Essentials

[x] Passed code style checking (make lint)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] docs --> How to --> build_mxnet_with_intelmkl.md

Comments

What happens with MKL_README.md?

This is an effort to add MKL instructions into the official documentations. It has a little different purpose from readme file.

@ykim362 not sure if I follow. Given that both MKL_README.md and the added content in your PR have build instructions, should MKL_README.md be deleted?
Also, MKL is one of many other build options available in mxnet. Thus, I'd suggest that the corresponding build instructions be provided in the existing "build from source" instructions, so that it's easier for the users to find and follow.

@szha I got your point. I will have an internal discussion and make a new PR to address your concerns.


⚠ ClamAV has degraded performance

In 935789f, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 71 ms

Resolved: ClamAV performance has improved in 9814ca5 after 25 minutes.


chore: create commit hooks for eslint and prettier using pre-commit

Now that we have the working PR checks, I guess this is not necessarily needed any longer. Even if so, it would probably be done using a different approach (npm package). Closing this for now.


dependency "URIjs": "~1.12.0" has been renamed to urijs

Causing npm warning in adapt authoring tool:
npm WARN deprecated<EMAIL_ADDRESS>package renamed to "urijs" (lower-case), please update accordingly

Also see https://github.com/adaptlearning/adapt_authoring/issues/1121


Investigate K8s-go-client caching/load implications

Flagd is designed to watch K8s CRD changes and update flag configurations on CRD changes (ex:- updates, removals). This is performed by K8s ISync implementation [1]
The Focus of this task is to know the impact of on-demand CRD fetching on the K8s API. This knowledge is a pre-requisite to remove any caching in-between sync providers and flag evaluations/grpc streams.
Research:

Does K8s API cache its responses
The impact of K8s API overloading (ex:- throttling, performance impact and stability)

Outcome:
Whether we require a cache OR whether we can rely on K8s API for high load scenarios
[1] - https://github.com/open-feature/flagd/blob/main/pkg/sync/kubernetes/kubernetes_sync.go

Currently used K8s client of the K8s ISync implementation is not backed by a cache [1]

// New returns a new Client using the provided config and Options.
// The returned client reads and writes directly from the server
// (it doesn't use object caches).  It understands how to work with
// normal types (both custom resources and aggregated/built-in resources),
// as well as unstructured types

Source [2]

Next step, consider a caching client if exist.
[1] - https://github.com/open-feature/flagd/blob/main/pkg/sync/kubernetes/kubernetes_sync.go#L155
[2] - https://github.com/kubernetes-sigs/controller-runtime/blob/main/pkg/client/client.go#L90-L99

One option is to rely on the store backing the informer that we already use for eventing [1]. The downside is that we could be reading outdated changes.
[1] - https://github.com/open-feature/flagd/blob/main/pkg/sync/kubernetes/kubernetes_sync.go#L168

Good reading resources
[1] https://kubernetes.io/docs/concepts/cluster-administration/flow-control/
[2] https://cloud.google.com/kubernetes-engine/quotas#limit_for_api_requests
Next steps, investigating improvements in our ISync implementation to reduce API impact and reuse resources.

PR #443 improves K8s Sync provider internals to utilize the informer store. However, we will still have a fallback to API get if we have a cache mismatch.
This will allow us to avoid a caching layer for flagd server


Update README.md

Fix issue certificate.

In many cases with some VPS, it will ask to bypass checking certificate, you should add an optional on this in the installation. This is not a bug, it just adds usability.

--no-check-certificate was there some years ago, when many OpenVZ templates didn't include the ca-certificates package by default.
Nowadays, it is expected that any system will have proper SSL support with a list of trusted CAs, and the script installs the ca-certificates if not already present.
This is a non-issue in my opinion and will not change.


Model training progress

When training a model, the executor should report the loss of the latest iteration. This loss should be visualized in the newly created node.

This is blocked by https://github.com/webgme/webgme/issues/686


patch advanced networking tested with 1.20

*Issue # n/a
Description of changes: Testing with EKS v1.20
- Suggested changes for module: ADVANCED VPC NETWORKING WITH EKS
- Tested with v1.20 and v 1.17. Updated command outputs.
- Replaced several manual steps with bash commands to make it more cut-n-paste friendly.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Applied new changes as suggested by @buzzsurfr . Please review and approve if all looks good.


buildx is missing from docker:20-dind images

Description

Docker 20-dind images are shipped with docker cli which seems to be missing buildx entirely.. which means support for buildx build --cache-from is not available.
Launching docker buildx build --help on my Macbook shows --cache-from available. However launching the same in container instance of docker:20-dind does not show --cache-from as valid option to buildx build.
Steps to reproduce the issue:
$ docker pull docker:20.10.7-dind
$ docker run -it --rm -e DOCKER_CLI_EXPERIMENTAL=enabled docker:20.10.7-dind sh -c 'docker --help | grep buildx && echo SUCCESS: buildx is available || echo ERROR: buildx is not available'
$ docker run -it --rm docker:20.10.7-dind sh -c 'docker --version; docker buildx build --help | grep cache-from || echo "ERROR: buildx build --cache-from is not supported"'

Describe the results you received:
ERROR: buildx is not available
Docker version 20.10.7, build f0df350
ERROR: buildx build --cache-from is not supported

Describe the results you expected:
SUCCESS: buildx is available
Docker version 20.10.7, build f0df350
      --cache-from stringArray   External cache sources (eg. user/app:cache, type=local,src=path/to/dir)

Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
from docker:20.10.7-dind docker image
Client:
 Version:           20.10.7
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        f0df350
 Built:             Wed Jun  2 11:51:04 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Output of docker info:
from docker:20.10.7-dind docker image
Client:
 Context:    default
 Debug Mode: false

Server:
ERROR: error during connect: Get http://docker:2375/v1.24/info: dial tcp: lookup docker on <IP_ADDRESS>:53: no such host
errors pretty printing info

Additional environment details (AWS, VirtualBox, physical, etc.):
Launching docker run -it --rm docker:20.10.7-dind sh -c ... on macOS 10.14.6 running Docker Desktop 3.4.0 (<IP_ADDRESS>23)

Duplicate of #243, #156

For reference, https://github.com/docker-library/docker/issues/156 includes discussion and clarification on why buildx plugin is not included in docker images. However, the PR (https://github.com/docker/docker-ce-packaging/pull/415) is open to include base plugins in official docker images.

I created an image here: maniator/dind-buildx exactly for this use :-(


Marking packages commands as deprecated

Issue https://github.com/aws/eks-anywhere-internal/issues/2270
Description of changes:
As described in the issue we want to mark packages commands as deprecated. For release v0.20.0 the commands are still present and in the next release we would remove the commands themselves.
Documentation added/planned:
Will update the docs and call out that these commands are not supported.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve

/lgtm
/approve


how to start a timer/Interval in use_effect scope?

somehow i need start a Interval when document is ready, and the callback will access  variable in use_state, seems no way to do that now？！hope get your comments!

For targeting web, you can have a look at https://crates.io/crates/gloo-timers
This seems to work on 0.2.4 as well as on master.
fn app(cx: Scope) -> Element {
    let interval_started = use_state(&cx, || false);
    let state = use_state(&cx, || 0);

    let (is, s) = (interval_started.clone(), state.clone());
    if !*interval_started.get() {
        is.set(true);
        gloo_timers::callback::Interval::new(1_000, move || {
            s.with_mut(|s| *s+=1);
        }).forget();
    }

    cx.render(rsx! {
        div {
            "{state}"
        }
    })
}

cool, that's what i need! Thank you budy!

hi,guys,
it works when only one Interval. but seems like to create two Interval, one is 1_1000 and the other is 300, it will not work, complain the cx escapes the function body, how to fix it?

I guess because you need to clone the state (reference) a second time for the new closure, which moves it in:

if !*interval_started.get() {
    interval_started.set(true);
    let state = state.clone();
    let state2 = state.clone();
    gloo_timers::callback::Interval::new(1_000, move || {
        state.with_mut(|s| *s+=1);
    }).forget();
    gloo_timers::callback::Interval::new(1_000, move || {
        state2.with_mut(|s| *s+=1);
    }).forget();
}

morning,budy,yeah. it fixed like you say!


Add tests for command

Init tests with Click and add tests for the generate command.

https://click.palletsprojects.com/en/8.1.x/testing/


Delete awareness.rb

Seems to no longer exist.

Found a git repo at https://github.com/dvdsgl/awareness but seems like source only, probably safe to tombstone

Yep, seems like they must’ve open-sourced it before giving up on the domain, or something.

Thank you for the contribution. It was merged directly as 3fbfd117fa7505a43fa6bea1ad1afe7866bb8b09 to keep commit history cleaner. Your contribution is still credited to you.

Huh? Just saw the exclamation mark, I am actually using this tool from time to time to keep in mind to get away from keyboard ;)
The website is up and running: http://iamfutureproof.com/tools/awareness/
Please have a 2nd look at this.

@winkelsdorf Good to know. This appeared to be completely dead, before (I also used it).

@vitorgalvao You're welcome! Haha, I noticed before that we have a lot in common. btw love your Alfred workflows, too. Small world ^^

Thank you. Always good to hear (well, read) from people who use them.


improve domain delegation docs and deploy an example and expose it on a custom domain

can use any of
refit.earth
co30.org

and run python http server on ubuntu based container.

https://github.com/threefoldfoundation/info_gridmanual/blob/development_testnet/src/6_develop/code/web/code_web.md


While making outgoing call : authenticate() | challenge without Digest nonce, authentication aborted

Describe the bug
While making a outgoing sip call through Web or Android, it is showing an error as :  Level.error digest_authentication.dart:92 ::: authenticate() | challenge without Digest nonce, authentication aborted.
To Reproduce
Steps to reproduce the behavior:

Execute flutter run command.
Go to Account on Dart Sip UA Demo, enter your details and press register.
After successful registration. Make a sip call.
Call doesn't execute, it shows the error as described.

Expected behavior
It should make a sip based outgoing call. Incoming call is working fine but on outgoing call it is showing this issue.
System Infomation()
Flutter SDK Version: 1.26.0-1.0.pre
Target OS and Version: Windows 10
Host OS and Version: Linux 16.04

@rakeshkhetwal Based on this error log:
Level.error digest_authentication.dart:92 ::: authenticate() | challenge without Digest nonce, authentication aborted

You need to check whether the nonce parameter is included in the digest information during the authentication process.

@rakeshkhetwal Based on this error log:
Level.error digest_authentication.dart:92 ::: authenticate() | challenge without Digest nonce, authentication aborted

You need to check whether the nonce parameter is included in the digest information during the authentication process.


[quick-start-widget] Design proper global hover state

Currently there is no interaction state developed on the.

Create:

[ ] Hover State
[ ] Active State

@hirsch88 how could we tokenize for example, a card hover for a global use? Otherwise this component has a individual hover?

https://baloise-design-system.vercel.app/?path=/docs/components-card--basic#card-variations

move to https://github.com/baloise/design-system/issues/788


CASSANDRA-19830 Use default commitlog settings in test YAMLs

patch by Caleb Rackliffe; reviewed by David Capwell for CASSANDRA-19830

See https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-5/46/

Second run to confirm: https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-5/48/

Committed as https://github.com/apache/cassandra/commit/47fe3a12cff44c10efed584b70f6b43318a82b91


Fix(ingestion): Snowflake Table to View lineage

This PR eliminates the old heuristic based logic(which has later been replaced with a more deterministic one)  which needed removing false edges from a table to a view, and fixes incorrect lineage when there is an upstream table UT, a view V, and a downstream table DT with edges UT->V, UT->DT and V->DT (UT->DT would be missing without this fix).
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

lgtm


Build OpenMM 7.7.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

The Windows Python 3.9 builds are failing with this error:
Traceback (most recent call last):
  File "D:\bld\openmm_1640119062043\test_tmp\run_test.py", line 2, in <module>
    import openmm
  File "D:\bld\openmm_1640119062043\_test_env\lib\site-packages\openmm\__init__.py", line 19, in <module>
    from openmm.openmm import *
  File "D:\bld\openmm_1640119062043\_test_env\lib\site-packages\openmm\openmm.py", line 13, in <module>
    from . import _openmm
ImportError: DLL load failed while importing _openmm: The specified module could not be found.

They worked just a week ago when I built the release candidate, and no code changes have happened since then.  Does anyone know what is causing this?

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Non noarch packages should have python requirement without any version constraints.
Non noarch packages should have python requirement without any version constraints.

@conda-forge-admin, please rerender

I tried making the change suggested in https://github.com/openmm/openmm/pull/3390#issuecomment-999775752, but that causes all the builds to fail.  Any suggestions for the correct way to fix it?

The Python version is controlled through the .ci_config/* files, so my first try would be modifying  the Windows 3.9 YAMLs. Or maybe with some Jinja in meta.yaml and run_constrained?

Do you mean put the python <3.9.9 # [win] into the run_constrained section?

In a way. The thing is that that constrain should only apply to the py39 branch. Rerendering with those constrains on host/run removed all the python matrix entries. You need to undo that change and try with the run_constrained trick but within a Jinja if check against the python version. Something like:
run_constrained:
{% if py == 39 %}
run_constrained:
  - python <=3.9.9
{% endif %}

I don't remember the syntax well but that's the idea.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

All builds passed!  Shall I merge it?

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

All builds are passing, so I'm going to merge this.  Then we need to add the same constraint to older releases to get them working on Windows again.  And then we can finish debugging https://github.com/openmm/openmm/pull/3390 which is the long term fix, but there's no rush about that.  Thanks everyone!

I don't see any sign of it rebuilding.  Do I need to do something else to force it to build?

Hm, it wasn't triggered. Try sending an empty commit to master.

Thanks!  That seems to be working.


How to discover the dependency list prior to running a security-only update

I'm trying to convert tinglesoftware/dependabot-azure-devops over to CLI, which currently uses the dry-run.rb and updater scripts to perform updates.
Everything works well so far using the CLI, except for security-only updates.
I've run in to a "chicken or the egg" situation where you need to list the [vulnerable] dependency names in input.yaml, but you don't know what the dependencies are until you've already run a dependabot update first and parsed the dependency list from output.yaml.
For example:
job:
    package-manager: npm_and_yarn
    security-updates-only: true
    dependencies:
      - express # how would I know this is a dependency before executing `dependabot update`?
    security-advisories:
      - dependency-name: express
        affected-versions:
          - <5.0.0
        patched-versions: []
        unaffected-versions: []

Do you have any advise on how I could solve this problem?
It would be ideal if there was a command like dependabot fetch --run-discovery, that was able return the "dependency_list" output, but skip the actual updates. Assuming I'm not missing something obvious, would you be open to me submitting a pull request to add this command?
The only way I can currently work around this issue is to do two "updates"; First with security-updates-only: false so I can parse the discovered dependency list, then a 2nd update with security-updates-only: true and the dependencies list populated.

It looks like @jakecoffman proposed something similar to what I'm looking for in https://github.com/dependabot/cli/pull/325.
Is there anything I could do to help with this? It sounds like a change might be needed to dependabot-core first which is maybe why this has stalled?

If anybody stumbles across this before it is resolved, I worked around this issue by running a "fake" update job containing ignore: { dependency-name: '*' }. This makes Dependabot discover all dependencies, but update none of them. Once the job has finished, the "update_dependency_list" can be parsed and used to build a new job that performs the security-only update. Not ideal, but it works.
See: https://github.com/tinglesoftware/dependabot-azure-devops/pull/1394


Accessibility of icons

Hey there!
Alright, let’s talk about accessibility. Most of what I know comes from Florens Verschelde. He wrote a fantastic article about working with SVG icons and I highly suggest anyone to read it: https://fvsch.com/code/svg-icons/#section-html.
Here is a summary of the things that are necessary for accessible icons:

The SVG element should have focusable="false" to avoid a double-focus issue on Internet Explorer and Edge.

The SVG element should have aria-hidden="true" even when used as a standalone icon. The associated text should be passed alongside the icon, not within it.

To provide context without displaying it visually, you can use a combination of CSS rules. Refer to https://hugogiraudel.com/2016/10/13/css-hide-and-seek/ for more information.

In case the icon is used a standalone icon, it should have a title attribute to provide a tooltip on hover.

It should be possible to pass the role and aria-live attributes.

Here is how we implemented it at N26 (I inlined and simplified the styles for the sake of the explanation):
// 1. The default vertical-align is `baseline`, which leaves a few pixels of
//    space below the icon. Using `middle` prevents this.
// 2. Hide paths and strokes overflowing the viewbox.
const styles = {
  display: 'inline-block',
  height: '1em',
  width: '1em',
  color: 'inherit',
  fill: 'currentcolor',
  verticalAlign: 'middle', /* 1 */
  overflow: 'hidden' /* 2 */
}

// Hide content while keeping it accessible for users of assistive technologies.
// See: http://hugogiraudel.com/2016/10/13/css-hide-and-seek/
// See: https://github.com/twbs/bootstrap/pull/25197
const visuallyHidden = {
  border: '0 !important',
  clip: 'rect(1px, 1px, 1px, 1px) !important',
  height: '1px !important',
  overflow: 'hidden !important',
  paddingTop: '0 !important',
  paddingRight: '0 !important',
  paddingBottom: '0 !important',
  paddingLeft: '0 !important',
  position: 'absolute !important',
  whiteSpace: 'nowrap !important',
  width: '1px !important'
}

const Icon = props => {
  if (!props.icon) {
    return null
  }

  const SVG = (
    <svg
      styles={styles}
      viewBox='0 0 32 32'
      aria-hidden='true'
      focusable='false'
    >
      <use xlinkHref={`#icon-${props.icon}`} />
    </svg>
  )

  if (!props.label) {
    return SVG
  }

  // The `role` and `aria-live` attributes might be useful in case the icon
  // needs to provide further information to the accessibility tree such as
  // for a loading spinner.
  // See: https://codeburst.io/how-to-create-a-simple-css-loading-spinner-make-it-accessible-e5c83c2e464c
  return (

      {SVG}
      {props.label}

  )
}

And then we can use it like this:
// Icon used alongside with text
<Icon icon='cogs' /> Settings

Or like this:
// Standalone icon
<Icon icon='cogs' label='Settings' />

Or like this:
// Standalone icon with extra contextual information
<Icon icon='loader' label='Loading…' role='alert' aria-live='assertive' />

I hope it helps. :)

Thank you for fixing the possible focus bug on Internet Explorer and Edge, that’s already better!
Here is the thing about the title element: this is not the correct way to provide meaning to an icon. The title element is supposed to describe the graphics itself, hence why it is used for charts, diagrams or other imagery like this. For an icon, one does not want to describe the icon itself, but its meaning related to its usage.
This is why the correct approach is to hide the icon from the accessibility tree, add visually hidden text next to it, as well as the title attribute for usability. I understand the hesitation on wrapping icons with a span, but unfortunately unless you do that, the accessibility layer will stay suboptimal at best.

I'm going to close this issue for now, though I may revisit at some future point.  For now, this library provides raw access to the <svg> element, and there's a note in the README about wrapping.  But some future backwards-incompatible version might have built-in span-wrapping.


[Feature Request] Assign ServerData.serverName when using connectToServer action.

I've had several people bring up the issue to me.
Details and solution can be found here.
https://github.com/TeamJM/journeymap/issues/149#issuecomment-565826418

Oops, closing.
Duplicate of https://github.com/lumien231/Custom-Main-Menu/issues/372


added language file for Vietnamese

I'm hoping to update this file later this week.

@phucduong86  I will close this PR for now, send a new one when the translation is finished.
Thank you very much :)


Request to add description of call backs that ends subscription of old release, if new-application is of same release and same application name for /v1/bequeath-your-data-and-die service

Problem Description:
Scenario : Same Release of application but deployed in different address and port.
When a same release but deployed in different address and port of existing application is registered , it will update the http-c ,
tcp-c of old Release in config file of New application with the preceding application information provided in request body.
Once the application is approved and receives “embed-yourself” , a callback will be triggered to the old application’s “/v1/bequeath-your-data-and-die” .
When /v1/bequeath-your-data-and-die is executed,it will update the NewRelease http-c,tcp-c with the new application details.
Then during series of call backs following callbacks should not be sent

PromptForBequeathingDataCausesRequestForDeregisteringOfOldRelease

As, it will lead to end of subscriptions of same application .
Solution:
To add description for callbacks mentioned below :

PromptForBequeathingDataCausesRequestForDeregisteringOfOldRelease

As ,
callback will not be sent, if new-application-name == application name in *-http-s-000 and new-application-address == address in *-http-s-000

Closing the issue, based on the decision made in the issue https://github.com/openBackhaul/ExecutionAndTraceLog/issues/260


Implementation of #81, #83, and #92

Updated implmentation of the FtpTrace class to use a TraceSource instead of directly writing to TraceListeners.
Implemented "Log Levels" on the FtpTrace class that translate to builtin levels that can be issued via a the TraceSource.  Resolves #81
Implemented user-defined error handling for Multi-File Upload / Download methods.  Resolves #83
Implemented verification and verification failure handing for File based Uploads & Downloads (not implemented on uploads/downloads that function directly on a stream object).  This needs some additional testing because I do not have access to an FTP server that has supports HASH functionality currently.  Should resolve #92
Updated XML documentation for all changes
Updated XML documentation to correct spelling & grammar, as as well as creating some links to correctly reference other classes/methods.
Depreciated the following methods:  FtpListParser.LogWarn(), FtpListParser.LogDebug(), FtpTrace.Write(string msg), FtpTrace.WriteLine(string msg/object msg)
Updated Multi-File Upload/Download method signatures to use IEnumerable<string> instead of string[] or List<string> to eliminate unnecessary overloads since these all implement IEnumerable<T>
Corrected bug introduced in commit 20caf4b2ae13608fa0525f66647f28418a23f5c8

Warning: This introduces breaking changes to the API

Don't pull this yet.  I just realized I needed to add something.

Ok, now it's ready

Wow. That's an amazing amount of work. I'll review it tomorrow and merge at the earliest. Thank you!

And what was the bug introduced in commit https://github.com/hgupta9/FluentFTP/commit/20caf4b2ae13608fa0525f66647f28418a23f5c8?

And what are the breaking changes in the API? You mean the extra args to the Upload/Download methods?

@hgupta9  BeginFileExists() had infinite recursion since it was calling return BeginFileExists(), but the overload it previously used was removed.
Yes the extra args to the upload/download method is the breaking change.

Great work so far. Thanks for the heavy investment of your time and effort. Its appreciated :)

Can you help me update the FAQ? Is this correct? Any more relevant questions regarding the new tracing method you built?
How do I trace FTP commands for debugging?
Do this ONCE at program startup (since its static it takes effect for all current FtpClient instances.)
FtpTrace.AddListener(new ConsoleTraceListener());
How do I log critical errors to a file?
Do this ONCE at program startup (since its static it takes effect for all current FtpClient instances.)
FtpTrace.AddListener(new TextWriterTraceListener("log_file.txt"));

And I've simplified the hashing API, by omitting the FtpVerify.Checksum option. So users don't have to do FtpVerify.Checksum | FtpVerify.Delete instead you can just do FtpVerify.Delete. As far as I can tell I've not broken anything but can you check? https://github.com/hgupta9/FluentFTP/commit/b3fbd8635ef9648cfc901f001629e793292db857

Readme improved to include error handling/hashing functionality. New FAQ entry for hashing.

@hgupta9 You actually wouldn't need to do FtpVerify.Checksum | FtpVerify.Delete.  Only having FtpVerify.Delete would be sufficient to make it do verification with deletion.  Having only FtpVerify.Checksum would just cause the function to return false if there was a verification failure.  I could see this functionality being useful if the end-user doesn't want any specific action taken by the library, but I can also see how it might seem a bit confusing.  Essentially FtpVerify.Checksum | FtpVerify.Delete == FtpVerify.Delete in terms of behavior (not actual value).  The reason being is that I do verification as long as verifyOptions != FtpVerify.None.  However, with that being said I can see how this could be confusing to end-users.  With that being said I looked at the code and no, that should not have broken anything.

I could still keep the Checksum option and call it ReturnFalse or something, indicating that the user can take any action he wants.
Can you help me update the FAQ regarding tracing since I don't know how to use the new functionality you built? And how does one use the FtpTraceLevel setting?
How do I trace FTP commands for debugging?
Do this at program startup (since its static it takes effect for all current FtpClient instances.)
FtpTrace.FlushOnWrite = true;
FtpTrace.AddListener(new ConsoleTraceListener());

How do I log critical errors to a file?
Do this at program startup (since its static it takes effect for all current FtpClient instances.)
FtpTrace.FlushOnWrite = true;
FtpTrace.AddListener(new TextWriterTraceListener("log_file.txt"));

Personally, I'd prefer it as Checksum because ReturnFalse would seem more like this flag is required for it to return false upon failed verification, which isn't currently true as any set handling assumes Checksum/ReturnFalse.  If it would make more sense to make that a requirement I can update the implmeentation to prevent it from assuming a return false upon failed verification without the flag explicitly set.  However, as long as it's documented it doesn't matter as much.  Since you're the owner of the library I'll let you make that call.
Regarding updating the FAQ, you are correct that should enable it & yes it needs to be done at application start..  However, hold off on documentation it because although it was working when I submitted my PR it isn't functioning as expected on my system.  I'm going to make sure there's no bugs with using the TraceSource and setting up a few configurations to make sure it's fully functional.  I'll update the FAQ with my demo configs once it works to demonstrate how it's configured.

For the flag, how about these other names :

FtpVerify.Manual
FtpVerify.OnlyCheck
FtpVerify.OnlyChecksum
FtpVerify.OnlyReturn

It we have proper docs saying that nothing will be done based on the checksum, and the method will return false upon failure.
Please update when the tracing is functioning. I will then push changes to nuget.

I have it fixed on my end, but I'm writing the documentation now.  I would avoid the word "Only" because it's a flag so it can be combined with others.  I'd recommend "Check" and then in the documentation say that using "Retry", "Delete", or "Throw" assumes "Check"

Submit the PR whenever you want to, I'll make the change after. And if you can get .NET core support its beneficial. Adding an extra dependency won't be a problem. Anyways I'm using the latest .NET standard (1.6) so all modules are available.

@hgupta9 I was waiting on your call regarding the the additional enum value for FtpVerify before I submit the second push.

@jblacker I prefer FtpVerify.OnlyChecksum as it indicates its a special use case and you don't need to consider it for normal usage (similar to FtpExists.NoCheck). I think calling it Checksum implies that you NEED that property to enable hashing and then you have to explain that Reply = Checksum | Reply and all that stuff which brings in unnecessary complication. And oh I tried to simplify the usage as much as possible. See the FAQ entry - I've filled in "all" the possible combinations to help users set the flags correctly.

Sounds good.


Design doc for CP-DOTO improvements and downside risk protection

Expected Behavior
There should be a design doc about additional mechanism in the CP-DOTO related smart contracts that mitigate downside risk.
Current Behavior
First ideas around additional downside protection mechanisms were discussed but never formalized.

@albertclabs This basically is the initial step towards Mento 2.0 and I suggest we keep it around unless Mento 2.0 work is captured somewhere else already.

@rcroessmann do you feel like we should track this instead on the Economics Research board topics? Seems like some longer term research before Mento 2.0

Yes definitely a research topic!


Change Beneficiary ID

Beneficiary ID confuses users. Change to Beneficiary and update hint messaging to detail that it is best practice to use a non personally identifiable ID.

 General refinement


Enable logging during bootstrap phase

Right now the only way to access the kubelet logs and logs of the static pods in the bootstrap control plane on the bootstrap node is to ssh into the node!
It would ideal if we could deploy something like a static fluentd pod on the bootstrap node to upload all the logs to something like a s3 bucket for debugging purposes.
/cc: @aaronlevy @yifan-gu @diegs

fluentd is a good option for extracting logs as it have various configurable input & output options, esp output to s3 bucket.
fluentd needs a fluent.conf to configure sources & outputs
Some ways we can implement is

static pod during bootstrap
** fluentd.conf is shipped in asset-dir
** bake fluentd.conf in a custom fluentd-image
non static pod after api-server is up.

At the first glance, a custom fluentd image seems cleaner than shipping config file in the asset-dir given that it hides the details and the config file should be pretty stable. The cons are that if we do want to make a change on conf file or fluentd image, we need to bake a new image.
Non-static pod might be a less ideal option as it will depend on api server to be running before it can be deployed. However, "why api server is NOT running" is the exact problem we want to debug with the logging.

It seems like there are 2 main areas we want to address.
(1) Issues during bootstrap, e.g. the boostrap control plane doesn't come up.
(2) Issues with the self-hosted control plane and downstream operations (this is not bootkube-specific and is more relevant to tectonic-installer, various operators, and test frameworks).
For (1) I think a static fluentd pod that can hook up to something easily accessible on the bootstrap node (e.g. journal logs) would suffice and actually be preferable. Bootkube requires you to ssh to that node anyway to run it. I don't think it's within the scope of the bootkube project to add more dependencies on logging sinks, such as S3 buckets. Currently the bootkube e2e tests fetch the journal logs at the end of the test--that's a simple command to run which we could publish in docs.
For (2) I think we should just recommend that people to deploy a more permanent fluentd dameonset as part of the asset-dir/manifests directory. But again, I think this is environment-specific and doesn't belong in the bootkube project, except perhaps as an example in the hack-scripts.
So to summarize, I think doing something simple for (1) that doesn't add external infrastructure dependencies sounds good, and I think it would be sufficient to just make sure the pod logs are aggregated in a place that's easy to extract.

Current logging code in the pluton e2e tests uses the package: github.com/coreos/mantle/network/journal to stream the journal logs as the test runs and then picks back up at the last cursor during reboots. Might be overkill for bootkube needs, but it could be re-used in the current (non-pluton) framework. Just need to dump pod logs at the end as well. You can see use of the package here
Agreed that having external platform dependancies like s3 might make things a little complicated. I like the ergonomics of having logs dropped locally when running tests on dev machines.
On the other hand our current ability to SSH into the external IPs of nodes is not a feature that will likely be kept as a more common framework emerges since many tectonic platforms will not have nodes with external IPs exposed. If we find a way to SSH to nodes through the API via special pod that tunnels out SSH access then we could rely on this transport for our logging needs.


Add TurboSnap for Chromatic

https://www.chromatic.com/docs/turbosnap/

Chromatic package needs to be update to >= v10.0
https://www.chromatic.com/docs/setup-turbosnap/#prerequisites


Allowing gradle to use checkstyle 6.8+

Fixes: https://issues.gradle.org/browse/GRADLE-3314

+1

Thanks for the PR. I've added some comments, but in general it looks pretty good.

Thanks for the feedback. I have made those changes. Let me know if theres anything else that needs to be done.

Having given this a bit more thought, it will need some rework to ensure it works with versions of Checkstyle supplied via the checkstyle configuration as well. This means not relying on the toolVersion to determine the ant task name.

Alright. I'll work towards doing it more like the PMD task.

Alright, this should "just work" now

Thanks Ethan. This PR has been merged and will be in Gradle 2.7.

Thanks!

@bigdaz can you close https://issues.gradle.org/browse/GRADLE-3314 ?

Done. Thanks for the reminder.


[ADAM-1093] Move to support Spark 2.0.0.

Relies on https://github.com/bigdatagenomics/utils/pull/78. Resolves #1093:

Clean up logging in VariantContextRDD
Add move_to_spark_2.sh script and CI hooks

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1403/Build result: FAILUREGitHub pull request #1123 of commit e4a539ca3ea2b8f7f4b9bdef243e7498347bb4bf automatically merged.Notifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-05 (centos spark-test) in workspace /home/jenkins/workspace/ADAM-prb > /home/jenkins/git2/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /home/jenkins/git2/bin/git config remote.origin.url https://github.com/bigdatagenomics/adam.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/adam.git > /home/jenkins/git2/bin/git --version # timeout=10 > /home/jenkins/git2/bin/git -c core.askpass=true fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/:refs/remotes/origin/pr/ # timeout=15 > /home/jenkins/git2/bin/git rev-parse origin/pr/1123/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a --contains 21b7ba24c1c10df6180d3744623bc081123c0aaf # timeout=10 > /home/jenkins/git2/bin/git rev-parse remotes/origin/pr/1123/merge^{commit} # timeout=10Checking out Revision 21b7ba24c1c10df6180d3744623bc081123c0aaf (origin/pr/1123/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 21b7ba24c1c10df6180d3744623bc081123c0aafFirst time build. Skipping changelog.Triggering ADAM-prb ? 2.6.0,2.10,1.5.2,centosTriggering ADAM-prb ? 2.6.0,2.11,1.5.2,centosTouchstone configurations resulted in FAILURE, so aborting...Notifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Rebased. Once this passes tests, @heuermh or I can cut a release of bdg-utils, and then I'll update this PR with the non-snapshot coordinates.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1467/
Test PASSed.

Hooray! I'll cut utils-0.2.8 upstream.

Jenkins, retest this please.

Just realized that Jenkins didn't run the 2.0.0 tests. Updated Jenkins, and kicked those off now!

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1468/
Test PASSed.

utils 0.2.8 artifacts are available from Maven Central.

We also need a move_to_spark_1.sh script and need to have this called near the end of release.sh.
I don't know what the spark packages zip file is, does that also need Spark 1.x and 2.x versions?

Updated with the final release version for utils.

We also need a move_to_spark_1.sh script and need to have this called near the end of release.sh.

Actually, we don't! (That's what I like about the release scripts here.) We do all of the releases from maintenance branches, and only update the versions on the master branch, so the POMs on the master branch don't get touched.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1470/
Test PASSed.

the POMs on the master branch don't get touched

Ah, ok.  LGTM then.

Thank you, @fnothaft!


set build name using groovy system script

build-name-setter does not seem to work

Refined in a2607e4f46


Regex search does not work with \n or \r

VSCode Version: 0.10.11
OS Version: Win 7 , SP 1

Steps to Reproduce:
Assume you have a document with the following lines:
// 1
// 2
// 3

Open search window (ctrl+f) and activate search with regex ( alt+R)
type in search box : //\s1
Expected Result : One match
add \n or \r to the end of search regex (now search regex will be : //\s1(\n|\r)
Bug: No Result!!

Duplicate of https://github.com/Microsoft/vscode/issues/313


OSProcess and LSP Servers

Hi all,
I was pointed this way by the Squeak mailing list (see this thread).
So far, I have been unable to launch the typescript-language-server from within Squeak, using OSProcess, and I am looking for some pointers. In my case, it appears that I need to be loading node and a bunch of other things first, but the examples in this repository seem to be doing nothing of the sort, so I'm wondering if there is some different strategy.
For reference, I am using macOS 12.6

Hi @darth-cheney! Our code, too, relies on a lot of node things to be available. To be more precise: you will have to have installed typescript-language-server as directed by their README via npm install -g typescript-language-server typescript. Afterwards, it needs to be within your PATH. For example, in my case, nvm (node version manager) added /home/tom/.nvm/versions/node/v16.16.0/bin to my PATH, which is an addition that occurs in my bashrc only. Fortunately, I'm also always running squeak via bash, so no troubles here.
In every other case, you will likely have to ensure that both node and typescript-language-server executables can be run without the additions to your PATH (e.g. by placing symlinks in /usr/local/bin), or that squeak knows about those additional directories, too.

Closing for now, please follow up with any more questions if needed :)


MessageChannel send method is returning true if brokers are down.

MessageChannel send method is returning true evwn if the brokers are down as kafka publishes to the buffer at first.
Tried to set the acknowledgement property to all with the below properties
spring.kafka.producer.acks = all/-1
and
spring.cloud.stream.kafka.binder.requiredAcks = - 1
We are opting to get the acknowledgement from the broker, but the kafka publisher is still returni g true when the brokers are down

You can also get the error asynchronously, by setting the errorChannelEnabled common producer binding property.

Hi @garyrussell thanks for the early reply. Will test with the property you suggested and reply back asap

Hi @garyrussell i tried setting the ync propert to true, still messagechannel.send is returning true on brokers being down
spring:
cloud:
stream:
default:
content-type : avro/bytes
kafka:b
default:
producer:
sync: true
binder:
requiredAcks: -1
brokers: localhost:9092,localhost:9093
zkNodes: localhost:2181
autoCreateTopics: false
zkConnectionTimeout: 36000
configuration:
security.protocol: protocol
ssl.truststore.location: truststoreLocn
ssl.truststore.password: truststorePass
ssl.endpoint.identification.algorithm:
I connected to brokers running in my local machine.

I just tested it and it works as expected:
@SpringBootApplication
@EnableBinding(Source.class)
public class Kbgh1976Application {

	public static void main(String[] args) {
		SpringApplication.run(Kbgh1976Application.class, args);
	}

	@Bean
	public ApplicationRunner runner(MessageChannel output) {
		return args -> {
			try {
				System.out.println("Hit enter after stopping broker");
				System.in.read();
				output.send(new GenericMessage<>("foo"));
			}
			catch (Exception e) {
				e.printStackTrace();
			}
		};
	}

}

spring.cloud.stream.kafka.default.producer.sync=true
spring.cloud.stream.kafka.default.producer.configuration.max.block.ms=5000

org.springframework.messaging.MessageHandlingException: error occurred in message handler [org.springframework.cloud.stream.binder.kafka.KafkaMessageChannelBinder$ProducerConfigurationMessageHandler@de88ac6]; nested exception is org.springframework.kafka.KafkaException: Send failed; nested exception is org.apache.kafka.common.errors.TimeoutException: Topic output not present in metadata after 5000 ms., failedMessage=GenericMessage [payload=byte[3], headers={contentType=application/json, id=7ebab7f9-1816-63de-2fd3-a1cccdb2faa6, timestamp=1591106421784}]
	at org.springframework.integration.support.utils.IntegrationUtils.wrapInHandlingExceptionIfNecessary(IntegrationUtils.java:192)
	at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:79)
	at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder$SendingHandler.handleMessageInternal(AbstractMessageChannelBinder.java:1035)
	at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:69)
	at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:115)
	at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:133)
	at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:106)
	at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:72)
	at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:570)
	at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:520)
	at com.example.demo.Kbgh1976Application.lambda$0(Kbgh1976Application.java:26)
	at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:786)
	at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:776)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:322)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1237)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226)
	at com.example.demo.Kbgh1976Application.main(Kbgh1976Application.java:17)
Caused by: org.springframework.kafka.KafkaException: Send failed; nested exception is org.apache.kafka.common.errors.TimeoutException: Topic output not present in metadata after 5000 ms.
	at org.springframework.kafka.core.KafkaTemplate.doSend(KafkaTemplate.java:570)
	at org.springframework.kafka.core.KafkaTemplate.send(KafkaTemplate.java:385)
	at org.springframework.integration.kafka.outbound.KafkaProducerMessageHandler.handleRequestMessage(KafkaProducerMessageHandler.java:410)
	at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:134)
	at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:69)
	... 15 more
Caused by: org.apache.kafka.common.errors.TimeoutException: Topic output not present in metadata after 5000 ms.

Hi @garyrussell, just wanted to check if it has something to do with the springboot and springcloud version.
The version i am using is
Springboot  - - 1.5.19.RELEASE
spring-cloud - - Edgware.SR4

@DevD08 you are using very old and no longer supported version of both boot and cloud dependencies.
he most current release of spring-cloud is Hoxton.SR5

Hi @garyrussell, i know the versions are very old, but sadly I am not in a position to change the versions.
Is there anyways out to implement acknowledgement in kafka with these versions

I don't know what you mean by

implement acknowledgement

but the sync property was supported in those old versions too. You should use a debugger to figure out why the property is not being set.

Closing due to no activity.

Why do we need to set sync Kafka producer binding property when spring.kafka.producer.acks = all/-1 is already defined. Will this property being ignored then? The primary task of acks = all is same as sync=true right? Is this the expected behaviour?
And also if i use kafka clients without cloud stream where did I need to do both acks= all and also future.get() to achieve sync send?

They are different - acks=all means we don't get the async ack until all replicas have received the record.
sync simply means to block the sending thread until the async ack is received.
If sync is false, you can receive the ack asynchronously instead.


The .wheel command has broken odds.

You have an average change of 2.4 * 1.7 * 1.5 * 1.2 * 0.5 * 0.3 * 0.2 * 0.1  = 0.022032 of coming out ahead. As you notice this is very low. To balance out the 0.1 odds, we'd have to have 10x in there. To balance out 0.2, we'd need 5x, etc, etc.

🤦♂


ArgumentError: bundle_identifier is missing

Describe the bug
Encountered the error ArgumentError: bundle_identifier is missing upon running bin/setup
To reproduce
Steps to reproduce the behavior:

Run bin/setup for the first time (in case you already have existing database setup, run first rails db:drop)
See example logs

...
== Preparing database ==
Created database 'railsdevs_development'
Created database 'railsdevs_test'
Seeding development database...
Seeded admins
Seeded developers
Seeded businesses
rails aborted!
ArgumentError: bundle_identifier is missing
... /app/models/concerns/messages/notifications.rb:16:in `send_recipient_notification'
... /app/models/concerns/messages/notifications.rb:5:in `save_and_notify'
... /lib/seeds_helper.rb:45:in `block in create_message!'
... /lib/seeds_helper.rb:44:in `create_message!'
... /db/seeds/conversations.rb:5:in `<top (required)>'
... /db/seeds.rb:4:in `load'
... /db/seeds.rb:4:in `seed'
... /db/seeds.rb:16:in `<top (required)>'

Expected behavior
No error will be encountered while running bin/setup specifically in seeding the database
Actual behavior
Encountered the error ArgumentError: bundle_identifier is missing specifically after the seed for businesses
Additional context
macOS Big Sur
non-Apple M1

Thanks for documenting this, @xmarlox! Can you please give #671 a try and let me know if that fixes the issue for you?

Oh I was having this issue also (on both WSL2 and M1), I got around it by running these 2 manually in rails c:
seed "businesses"
seed "conversations"

I tested #671 and it works for me 👍

@joemasilotti yeah #671 fixed this issue
thanks!

Excellent, thanks for the feedback folks. I'll merge that in.

Closed via #671.


Add Dockerfile

Signed-off-by: Mike Zaccardo<EMAIL_ADDRESS>

I was curious as to what this explorer repo was about, but wasn't sure how it fitted in with the rest of sawtooth. Glad to find a dockerfile to help jump in and testing this out. Could you add a docker-compose.yml file as well to see how this integrates with the rest of the sawtooth stack? Any other environment variables that need to be handled other that what I see with SAWTOOTH_REST_API in the entrypoint, or startup service dependencies before launch?

Hey Mike, we've got some docker goodness in this branch: https://github.com/hyperledger/sawtooth-explorer/tree/version-1-relayout , also, it's been setup to work with version 1 (master only works with 0.8)

@kidrecursive Thanks for the update! I needed to run Explorer in a Docker container without relying on Docker Compose, so I created these files and figured I might as well contribute them to the community. However, #7 certainly makes sense from a normal user's ease-of-use perspective so I'm closing this PR.


get rid of the Copy trait for K and V

Somehow Vec and HashMap work with keys and values that don't implement Copy. We should do the same. I'm not sure exactly how this can be done, but it should be possible.

I am not sure this would have great value for micromap: it is meant to use the stack whereas Vec and HashMap are intended to use the heap. Using micromap with types that do not implement Copy would probably be an unusual case.
Also depending on how far you want to take this issue (concretely: remove Clone as well), this would have an impact on the current API as e.g. .into_iter(&self) really cannot do without this.

@WiebeCnossen I'm not really an expert in this area. Help me understand. Now, when we put a pair into the array, we do memcpy. If we use Clone, we will put pointers into our array? Is this your concern?

we don't use Copy anymore


Property/environment variables don't see to work. How to check venv is correctly set up?

The system variables "jna.library.path", "scalapy.python.library" and "scalapy.python.programname" don't seem to have any effect. ScalaPy seems to work no matter what I set.
I am testing SacalPy using Scala 3. I use Mill as a build tool. I copied and pasted the code used in SBT from installation section. A quick test using these code snippets works correctly.
I then tried setting different values for (I set the last 2 of these in the object initializer that has the main function, see below):

"jna.library.path"
"scalapy.python.library"
"scalapy.python.programname"

Whether or not I set them incorrectly, the system still works. 8-) Here is an example:
I use javaOption = -Djna.library.path=/usr/lib/python3.8/config-3.8-x86_64-linux-gnu
and I get py.module("sys").executable = /usr/bin/python3. This seems to be correct.
If I set scalapy.python.programname = "/home/user/VSCodeProjects/rl-airegio/venv/bin/python" I
get py.module("sys").executable = /home/user/VSCodeProjects/rl-airegio/venv/bin/python.  But if I change this to a non-existant binary, its still works.
Same happens when I set the python version to a non-existant version.
One thing that does seem to work is if I activate the virtual environment and run the Mill script
then I get py.module("sys").executable = /home/user/VSCodeProjects/rl-airegio/venv/bin/python
as expected without setting anything.
So what is the best way to check that I am pointing to the correct environment? Save for the virtual
environment, when/why do I need to set these variables? It seems like I can set two of these to incompatible versions, then shouldn't it fail?
TIA
object FFIPythonHello:

  // No effect
  val pythonVersionProperty = "scalapy.python.library"

  // No effect
  val venvPythonProperty = "scalapy.python.programname"

  val venvPython = "/home/user/VSCodeProjects/rl-airegio/venv/bin/python"
  val pythonVersion = "python3.18"

  //System.setProperty(venvPythonProperty, venvPython)
  //System.setProperty(pythonVersionProperty, pythonVersion)

  def main(args: Array[String]): Unit =

    println("FFIPython")

    val exec = py.module("sys").executable
    println(s"exec = $exec")

    // https://docs.python.org/3/library/sys.html
    val platform = py.module("sys").platform
    println(s"platform = $platform")

    // https://docs.python.org/3/library/sys.html (only in 3.9)
    //val lib = py.module("sys").platlibdir

    val listLengthPython = py.Dynamic.global.len(List(1, 2, 3).toPythonProxy)
    // listLengthPython: py.Dynamic = 3
    println(s"listLengthPython = $listLengthPython")

    val listLength = listLengthPython.as[Int]
    // listLength: Int = 3
    println(s"listLength = $listLength")

end FFIPythonHello

In the current release version of ScalaPy, if the scalapy.python.library you manually set is invalid ScalaPy will try some generic option e.g. python, python3, python3.7, ... This has been disabled in a recent PR #270.
You seemed to ask about scalapy.python.programme though. That option is passed into the Python C API function Py_SetProgramName during initialization. Python then use it to set the executable path. My guess is if it's invalid, Python will just disregard it and use the default one?

One thing that does seem to work is if I activate the virtual environment and run the Mill script
then I get py.module("sys").executable = /home/user/VSCodeProjects/rl-airegio/venv/bin/python
as expected without setting anything.

If you don't set any option then ScalaPy will just use python in the current environment. So it makes sense that if you activate your venv then it would just work.

@kiendang Thanks for the feedback. I think #270 is a good option.


feat(monorepo): move react-virtual-select to package and add docs

This moves everything in root to a packages/react-virtual-select folder.
Then adds a package.json in root to handle yarn workspaces.
And add another folder docs/ within root to handle another package inside monorepo for docusaurus template.
Closes #2

Great idea using a monorepo.
Just a comment, what do you think about using the same docusaurus template with typescript? Do you think it will be worth it?

Great idea using a monorepo. Just a comment, what do you think about using the same docusaurus template with typescript? Do you think it will be worth it?

Without having much experience with it, I think we will be using markdown most of the time and use our component(s) from there. Let's see if just the JS version fits our needs.


[BUG] account_edit with email have no effect

Describe the bug
Doing account_edit with email seems to be not working. It didn't change and no error msg return
To Reproduce
cl.ccount_edit(email =<EMAIL_ADDRESS>Traceback
No error msg
Expected behavior
Upon printing cl.account_info(), email field is still empty
Desktop (please complete the following information):

OS: MacOS
Python version 3.8.8
instagrapi version 1.16.11

With further investigation, it happened when the account already have a phone number attached

@ennis214 try instagrapi 1.16.13 and new methods: cl. send_confirm_email and cl.send_confirm_phone_number
https://adw0rd.github.io/instagrapi/usage-guide/account.html


Sha1 did not match data received

Receiving a lot of these, 2016/06/18 09:33:11 2013-08-10/001.JPG: Failed to copy: Sha1 did not match data received (400 bad_request).

What is your rclone version (eg output from rclone -V)

rclone v1.29

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Debian Etch x86_64 (ReadyNAS Ultra 4)

Which cloud storage system are you using? (eg Google Drive)

B2

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone sync /c/pictures b2:mejje-pictures -v --dump-headers

A log from the command with the -v flag (eg output from rclone -v copy /tmp remote:tmp)

With headers (excluding Authorization)
https://gist.github.com/mejje/c608f2bfba0b6aff1fe913927d6a1434
And it looks like this with regular logging
2016/06/18 21:20:12 2015-05-05/IMG_0361.JPG: Received error: c001_v0001030_t0037 is too busy (503 service_unavailable) - low level retry 1/10
2016/06/18 21:20:16 2009-06-27/DSC_0040.JPG: Received error: c001_v0001030_t0021 is too busy (503 service_unavailable) - low level retry 1/10
2016/06/18 21:20:23 2015-05-05/IMG_0361.JPG: Failed to copy: Sha1 did not match data received (400 bad_request)
2016/06/18 21:20:26 2009-06-27/DSC_0040.JPG: Failed to copy: Sha1 did not match data received (400 bad_request)
2016/06/18 21:20:40 2009-06-27/DSC_0088.JPG: Received error: c001_v0001030_t0037 is too busy (503 service_unavailable) - low level retry 1/10
2016/06/18 21:20:49 2009-06-27/DSC_0088.JPG: Failed to copy: Sha1 did not match data received (400 bad_request)

Will try 1.30 with a new bucket

Same issue with 1.30, log with headers:
https://gist.github.com/mejje/87c1629ac270d26aa859fc2e938d7cb6
file is IMG_9129.JPG

Excellent bug report - thanks :-)
Thanks for those logs - I can see that there is a problem with the retries...  The sha1 changes for the second retry which is very strange since assuming you are reading from the local filesystem then it should be cached in the object at that point.
I tried to simulate the problem by forcing a retry but I didn't manage to so there must be something else going on.
2016/06/18 23:41:23 POST /b2api/v1/b2_upload_file/c8995750732968595c560516/c001_v0001030_t0001 HTTP/1.1
Host: pod-000-1030-08.backblaze.com
User-Agent: rclone/v1.30
Content-Length: 3459189
Authorization: removed
Content-Type: image/jpeg
X-Bz-Content-Sha1: 0d6507aa7623230e21691a79c03a329975fab584
X-Bz-File-Name: 2009-07-27/IMG_9129.JPG
x-bz-info-src_last_modified_millis:<PHONE_NUMBER>666
Accept-Encoding: gzip

And on the first retry it looks like this
2016/06/18 23:41:24 POST /b2api/v1/b2_upload_file/c8995750732968595c560516/c001_v0001030_t0001 HTTP/1.1
Host: pod-000-1030-08.backblaze.com
User-Agent: rclone/v1.30
Content-Length: 3459189
Authorization: removed
Content-Type: image/jpeg
X-Bz-Content-Sha1: 597831486f9228ad26ff522058d275512f6bb8f9
X-Bz-File-Name: 2009-07-27/IMG_9129.JPG
x-bz-info-src_last_modified_millis:<PHONE_NUMBER>666
Accept-Encoding: gzip

Can you check the sha1 of that file for me both with sha1sum and rclone?
sha1sum /c/pictures/2009-07-27/IMG_9129.JPG
rclone sha1sum /c/pictures/2009-07-27/IMG_9129.JPG

Could you run those commands several times and make sure they give the same answer each time!
Some other questions for you

Is it always that file which is a problem?
What type of file system is /c/pictures

mejjeNAS:~# sha1sum /c/pictures/2009-07-27/IMG_9129.JPG
0d6507aa7623230e21691a79c03a329975fab584  /c/pictures/2009-07-27/IMG_9129.JPG
mejjeNAS:~# rclone sha1sum /c/pictures/2009-07-27/IMG_9129.JPG
0d6507aa7623230e21691a79c03a329975fab584  IMG_9129.JPG

Ran them several times, no diff.
The file was uploaded without issue in the next rclone run.
/dev/c/c on /c type ext4 (rw,noatime,nodiratime,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1)

Bam, found it!
If the file is closed without having the entire body consumed, the hash is updated to the partial value. We need to keep track of the consumed bytes in the reader above, and only update hashes if the consumed size matches the expected size.

Well spotted @klauspost - excellent sleuthing!
I'm just trying to think through the sequence of events

local.Object.Open() is called in fs.Copy()
b2.Fs.Update() is called
This then calls local.Object.Hash(fs.HashSHA1)
This calculates the sha1 and sets it in the object
We try the PUT but it is rejected.
b2 must reject it without reading the whole stream as we aren't using Expect: 100-continue
local.Object.Close() is called by fs.Copy() and overwrites the correct hash it with a corrupt hash

So that indicates that your patch is doing the right thing :-)
It also indicates that we should probably not overwrite the hash in the local.Object.Close if it is already set.  Actually re-reading your patch I see you've done exactly that :-)

@mejje here is a beta for you to try with @klauspost fix.
Please re-open the ticket if it doesn't work!
Thanks
http://pub.rclone.org/v1.30-2-ge0aa4bbβ/

It works fine now! Thanks for the speedy fix :).
Curiously, the files that were retried (with the b2_hide_file 400 response) are still hidden in the b2 web UI. They are present in rclone ls though so I guess it's an issue on their end.

Thanks for testing!
It is probably a caching thing on the website - that would be my guess.

This issue is closed but I'm seeing this exact problem with v1.33 backing up to b2. "Failed to copy: Sha1 did not match data received" over and over again, and no file ever gets successfully uploaded.

@DavidCWGA I'm also seeing this when backing up to b2. I'm not sure this is entirely fixed.

@DavidCWGA @bittylicious I conjecture you are using crypt with b2 and this is
#644 - here is a beta which should fix the problem:
http://pub.rclone.org/v1.33-6-g2eaac80β/
If not can you open a new issue please with full info and a log with -v please?

The sha1 issue seems to be resolved but nothing is copied when using the crypted destination. See #686 for the new issue report.


unique symbol incorrectly widens to symbol when assigning to a const or readonly property

Search Terms:
unique symbol, literal, widen, reassign, const, readonly
Code
const t1 = Symbol("t1")
const t1Copy = t1
const result1: typeof t1 = t1 // no error
const result2: typeof t1 = t1Copy // error: type symbol not assignable to unique symbol

class T2 {
    static readonly sym = Symbol("T2")
    readonly kind = T2.sym
}

const inst = new T2()
const result3: typeof T2.sym = T2.sym // no error
const result4: typeof T2.sym = inst.kind // error: type symbol not assignable to unique symbol

declare function genericIdentity<T>(arg: T): T
const unexpectedError: typeof t1 = genericIdentity(t1)

declare function genericSymbolNested<T extends symbol>(arg: T): { prop: T }
const unexpectedError2: { prop: typeof t1 } = genericSymbolNested(t1)

Expected behavior:
No errors. t1Copy and inst.kind should retain their respective literal unique symbol types the same way string literals would because they are declared with const and readonly.
Actual behavior:
Errors on result2 and result4 because t1Copy and inst.kind are widened to symbol. When assigning a unique symbol variable to a new variable the type is always widened to symbol unless an explicit type annotation is added.
Playground Link:
Link
Related Issues:
Did not notice any similar bug reports, but the design notes from #17501 seem to confirm that the current behavior is a bug:

Like literal types, these types contain "freshness" which can be widened away to produce a "regular" type.
When you alias a symbolic const with another const, it has the type typeof [[that original variable]].

Which implies they should work like other literal types which would not be widened in the example above.

Additional cases with generics:
declare const sym: unique symbol

declare function genericIdentity<T>(arg: T): T
const unexpectedError: typeof sym = genericIdentity(sym)

declare function genericSymbolNested<T extends symbol>(arg: T): { prop: T }
const unexpectedError2: { prop: typeof sym } = genericSymbolNested(sym)

// Compare with the following equivalent code using literal strings:

declare const literalString: "literal"
const noErrorWithString: typeof literalString = genericIdentity(literalString)

declare function genericStringNested<T extends string>(arg: T): { prop: T }
const noErrorWithString2: { prop: typeof literalString } = genericStringNested(literalString)

Playground link

Type of a unique symbol is widened unless it is of the form const sym = Symbol(). the intent here is not clear. this was also done to avoid breaking changes.

You don't have any reason to widen the type here. This change never breaks any valid code. Then this is pure improvement. You don't have any reason to avoid this improvement.

the intent here is not clear.

The intent is that unique symbols should work the same way as string literals. They are conceptually the exact same thing: a type that has exactly one possible value. The use cases for the behavior I described are the same as the use cases for string literals.
I agree with @falsandtru that I don’t understand what cases you are concerned about where this would be a negative breaking change.
Also I just want to say that it’s very frustrating to go through the effort of putting together a very clear, minimally reproducible bug report only to have it apparently glanced at for a few seconds and assumed invalid. When I ran into this issue it wasn’t remotely clear what the root cause was. It took a decent amount of effort to narrow it down to the very straightforward example I posted here. It also took time to do the research to try to confirm my feeling that this was an unintentional bug, which the design notes from #17501 did seem to explicitly confirm.
I realize you have many issues to go through and that most of them are invalid or duplicates which is why I try as much as possible to ensure that my issues are both valid and not duplicates. I try to respect your time but frankly I feel that respect is not always returned.

Now we can define unique symbol properties by changes of language design.