libs/libc/wqueue/work_usrthread.c: Correct time calculation in work_p…

…rocess
This fixes busylooping in work_usrthread, due to incorrect time spec given to sem_timedwait
_SEM_TIMEDWAIT works on absolute time stamps, using CLOCK_REALTIME
Signed-off-by: Jukka Laitinen<EMAIL_ADDRESS>Summary
The implementation of sem_timedwait has changed in 33ec242caf3
It calls  sem_clockwait(sem, CLOCK_REALTIME, abstime), which expects absolute time stamp for wakeup, using CLOCK_REALTIME.
This patch provides the proper timespec in work_usrthread.
Impact
This fixes busylooping in work_usrthread; it never sleeps in the semaphore.
Testing
This has been tested on STM32F7 (Pixhawk 4 flight controller), using NuttX PROTECTED_BUILD.

If there is a more reasonable way to just sleep N ticks in user space, please point that out; it would make much more sense to use something line nxsem_tickwait in here, but that is not available in user space...

@xiaoxiang781216 @gustavonihei I wonder if this is an acceptable way to implement this?

argh. this doesn't of course build for KERNEL builds, since sched is not linked against libc there.
Would it make sense to move those timespec functions under libc/sched, as they are pure math?

It's better to merge the first and the third patch into one.

The only issue with moving these functions into libc is that it modifies the OS interface definition and violates the portable POSIX interface.
We normally keep non-standard helper functions like under apps/ so avoid contaminating the OS interface.with non-standard functions.

The only issue with moving these functions into libc is that it modifies the OS interface definition and violates the portable POSIX interface.
We normally keep non-standard helper functions like under apps/ so avoid contaminating the OS interface.with non-standard functions.
I think the fact that they are prototyped in nuttx/c;lock.h does at least make their non-standard nature clearer (but doesn't help with portability).

Thanks for your advice!
I am of course willing to re-work this if you can advice how to nicely implement the change in libs/libc/wqueue/work_usrthread.c
One obvious way is of course to duplicate the tick->timespec calculations locally in there (where I actually started at...). I was trying to avoid doing that, since it turns out to be a bit more complex than I first thought, considering all the different platforms, supported data-types etc.


Read me install instructions

Add Install instructions we need to provide detailed information on how to set up the front end app. ie. cd into client, then npm install and so on..

dependency information

add app status badges

@motosharpley Bryan,
Within the README.md, Could I create a short video intro about what this project is about?
Here is resource on how to add to README.
https://stackoverflow.com/questions/4279611/how-to-embed-a-video-into-github-readme-md
First, I need to understand what this app is suppose to do.  Could we chat on Slack?

Yes @heggy231 that would be great. If you would like I can add you to the UI/UX Design team and you could reach out to the team members there to work on a prototype on invision.


Add Common Errors to codegen

As seen in https://github.com/rusoto/rusoto/pull/561 our codegen makes everything work except "Common Errors" that aren't included in the service definition.
This comment has links to AWS docs that describe the errors that can be returned.  The tests generated by codegen include a couple of tests that include those errors.  Those sample return payloads from AWS can be used to verify the work is done.  cargo test --features ses will run those if you're on the branch in PR #561 .

I couldn't see us actually using any response errors in tests? I only see generate_response_parse_test which tests parsing non-error/valid responses. botocore does have sample error responses though (https://github.com/boto/botocore/tree/develop/tests/unit/response_parsing/xml/errors) so perhaps this would be a good thing to add in general...

This issue mentions SES, but this would likely be a more general issue - right? Is this where work on handling SQS/SNS common errors would live?

Changed the title. Common Errors are, well, common, so they're the same for all services. 😁
Looks like you've got the right docs @insanitybit. I think we'd probably want to have the common errors in rusoto_core so they could be shared between all services, something like:
pub enum AWSError {
    ...
}

As far as I can tell, there's no definition for them in botocore, so no generation. The enum will just have to be written manually.
In the error type generator, each error type could then be generated with an additional variant like Common(AWSError).
I think the hard part here will be to get the errors transformed from the body correctly. Should just require extending the generated from_body method to support the new common errors as well (I think :).
Another alternative is to just generate the additional variants along with every error type, but (a) that feels like a lot of duplication and (b) it won't be possible (or at least, east) to have a function that handles a common error from any service (e.g. a generic retry handler).

I don't know the structure of the project yet - but the problem I would see with having them in boto core is that the common errors appear to be different between services. Or, well, they actually don't but the API docs are separate so it makes me think they could be?
Regardless, that's some good info and I can start having a look at that code in the next week or so if no one else gets around to it (I'm in the middle of moving or I'd start sooner).
I agree with the Common(AwsError) method you've suggested so long as the common errors are actually common across services.
Thanks for all the info so far.

Yeah, I'm not sure why they're documented in each individual service, but they are shared across all services.
From the common errors doc from one service:

This section lists the errors common to the API actions of all AWS services.

I have created a proof of concept https://github.com/jhinch/rusoto/commit/9aed164ea7e16f821bb453a9ae5624f5faa0b2e7 of how this might look. Before I spend time getting to a stage which it would be ready for PR, I wanted to get some feedback as to whether this is the right approach.


Cron command doesn't work

I'm a newbie so I could be doing something wrong or maybe I shouldn't even be submitting this but the README guide provides an example cron command which doesn't work:
0 5 * * * root /opt/google-compute-snapshot/gcloud-snapshot.sh >> /var/log/cron/snapshot.log 2>&1
Again, as a newbie I'm not even sure I belong here. I Googled a while and tried -u root but that also produced an error in the log.

You'll need to use the exact command that works via SSH. Personally I created a .sh bash script and I call it using: sh /path/to/script.sh
Make sure you have the correct shebang in your file and that permissions are set correctly if you use my method.

No worries - we were all newbies once!
Does it work when you just run the command by itself?
(/opt/google-compute-snapshot/gcloud-snapshot.sh)
Also, how are you doing the CRON? Is it via crontab? If so, you'll need to
remove the "root".
I do my crons via /etc/cron.d so i have to specify which user the command
should be run by.
On Sat, 18 Mar 2017, 04:29 Brad Baker<EMAIL_ADDRESS>wrote:

You'll need to use the exact command that works via SSH. Personally I
created a .sh bash script and I call it using: sh /path/to/script.sh
Make sure you have the correct shebang in your file and that permissions
are set correctly if you use my method.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jacksegal/google-compute-snapshot/issues/22#issuecomment-287515607,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI6PPo8hvLLotDB0S4H4RfHxi8sSc_bpks5rm12PgaJpZM4MhR5o
.

Thank you both. I did get it working.
I had never setup a cron job before without doing it through some kind of web interface or something so when I googled how to do it I found the crontab -e method and just copied the command into that which of course didn't work. It is working great now that I removed the root and -u root variations I had tried.

Great, glad it's working for you!


Allow to use GitHubAPI.getiter with the GitHub search API

Currently, if we try to use GitHubAPI.getiter with the GitHub search API we get strange results because of the data returned by GitHubAPI._make_request is actually a dictionary that looks like this:
{
  "total_count": 7,
  "incomplete_results": false,
  "items": [
    {
      "name": "classes.js",
      "path": "src/attributes/classes.js",
      "sha": "d7212f9dee2dcc18f084d7df8f417b80846ded5a",
      "url": "https://api.github.com/repositories/167174/contents/src/attributes/classes.js?ref=825ac3773694e0cd23ee74895fd5aeb535b27da4",
      "git_url": "https://api.github.com/repositories/167174/git/blobs/d7212f9dee2dcc18f084d7df8f417b80846ded5a",
      "html_url": "https://github.com/jquery/jquery/blob/825ac3773694e0cd23ee74895fd5aeb535b27da4/src/attributes/classes.js",
      "repository": {
        "id": 167174,
        "node_id": "MDEwOlJlcG9zaXRvcnkxNjcxNzQ=",
        "name": "jquery",
        "full_name": "jquery/jquery",
        "owner": {
          "login": "jquery",
          "id": 70142,
          "node_id": "MDQ6VXNlcjcwMTQy",
          "avatar_url": "https://0.gravatar.com/avatar/6906f317a4733f4379b06c32229ef02f?d=https%3A%2F%2Fidenticons.github.com%2Ff426f04f2f9813718fb806b30e0093de.png",
          "gravatar_id": "",
          "url": "https://api.github.com/users/jquery",
          "html_url": "https://github.com/jquery",
          "followers_url": "https://api.github.com/users/jquery/followers",
          "following_url": "https://api.github.com/users/jquery/following{/other_user}",
          "gists_url": "https://api.github.com/users/jquery/gists{/gist_id}",
          "starred_url": "https://api.github.com/users/jquery/starred{/owner}{/repo}",
          "subscriptions_url": "https://api.github.com/users/jquery/subscriptions",
          "organizations_url": "https://api.github.com/users/jquery/orgs",
          "repos_url": "https://api.github.com/users/jquery/repos",
          "events_url": "https://api.github.com/users/jquery/events{/privacy}",
          "received_events_url": "https://api.github.com/users/jquery/received_events",
          "type": "Organization",
          "site_admin": false
        },
        "private": false,
        "html_url": "https://github.com/jquery/jquery",
        "description": "jQuery JavaScript Library",
        "fork": false,
        "url": "https://api.github.com/repos/jquery/jquery",
        "forks_url": "https://api.github.com/repos/jquery/jquery/forks",
        "keys_url": "https://api.github.com/repos/jquery/jquery/keys{/key_id}",
        "collaborators_url": "https://api.github.com/repos/jquery/jquery/collaborators{/collaborator}",
        "teams_url": "https://api.github.com/repos/jquery/jquery/teams",
        "hooks_url": "https://api.github.com/repos/jquery/jquery/hooks",
        "issue_events_url": "https://api.github.com/repos/jquery/jquery/issues/events{/number}",
        "events_url": "https://api.github.com/repos/jquery/jquery/events",
        "assignees_url": "https://api.github.com/repos/jquery/jquery/assignees{/user}",
        "branches_url": "https://api.github.com/repos/jquery/jquery/branches{/branch}",
        "tags_url": "https://api.github.com/repos/jquery/jquery/tags",
        "blobs_url": "https://api.github.com/repos/jquery/jquery/git/blobs{/sha}",
        "git_tags_url": "https://api.github.com/repos/jquery/jquery/git/tags{/sha}",
        "git_refs_url": "https://api.github.com/repos/jquery/jquery/git/refs{/sha}",
        "trees_url": "https://api.github.com/repos/jquery/jquery/git/trees{/sha}",
        "statuses_url": "https://api.github.com/repos/jquery/jquery/statuses/{sha}",
        "languages_url": "https://api.github.com/repos/jquery/jquery/languages",
        "stargazers_url": "https://api.github.com/repos/jquery/jquery/stargazers",
        "contributors_url": "https://api.github.com/repos/jquery/jquery/contributors",
        "subscribers_url": "https://api.github.com/repos/jquery/jquery/subscribers",
        "subscription_url": "https://api.github.com/repos/jquery/jquery/subscription",
        "commits_url": "https://api.github.com/repos/jquery/jquery/commits{/sha}",
        "git_commits_url": "https://api.github.com/repos/jquery/jquery/git/commits{/sha}",
        "comments_url": "https://api.github.com/repos/jquery/jquery/comments{/number}",
        "issue_comment_url": "https://api.github.com/repos/jquery/jquery/issues/comments/{number}",
        "contents_url": "https://api.github.com/repos/jquery/jquery/contents/{+path}",
        "compare_url": "https://api.github.com/repos/jquery/jquery/compare/{base}...{head}",
        "merges_url": "https://api.github.com/repos/jquery/jquery/merges",
        "archive_url": "https://api.github.com/repos/jquery/jquery/{archive_format}{/ref}",
        "downloads_url": "https://api.github.com/repos/jquery/jquery/downloads",
        "issues_url": "https://api.github.com/repos/jquery/jquery/issues{/number}",
        "pulls_url": "https://api.github.com/repos/jquery/jquery/pulls{/number}",
        "milestones_url": "https://api.github.com/repos/jquery/jquery/milestones{/number}",
        "notifications_url": "https://api.github.com/repos/jquery/jquery/notifications{?since,all,participating}",
        "labels_url": "https://api.github.com/repos/jquery/jquery/labels{/name}"
      },
      "score": 0.5269679
    }
  ]
}

So the items returned by GitHubAPI.getiter are the keys of this dictionary (total_count, incomplete_results and items). The ones that we want are in items. Just returning this value works because pagination is automatically managed by the sansio component using the associated headers:
Status: 200 OK
Link: <https://api.github.com/resource?page=2>; rel="next",
      <https://api.github.com/resource?page=5>; rel="last"
X-RateLimit-Limit: 20
X-RateLimit-Remaining: 19

Of course there's a special pagination requirement for searching. 😝
I don't think I have any specific issue with this. @Mariatta , do you have an opinion?
@pablogsal could you also include a real-life sample to test against? See the gidgethub/test/samples directory to see what I mean (and the code that uses it).

I have added a real word sample in gidgethub/test/samples and a new test in test_sansio. I hope I did not miss anything :)

I think this is useful feature! Thanks for adding this. I could use it in check_python_cla project 🙂

Thanks @pablogsal ! I've added a changelog entry for this and also tweaked the version number to reflect that we now have a new feature for the next release!
I'm a bit tied up right now with the governance model voting stuff ATM, but hoping next week or at worst the week following I can cut a new release.


[FR] - There is no way to delegate based on pool_id

Internal/Exernal
Internal   if an IOHK staff member.
Describe the feature you'd like
For the public stake pools, we have only their pool_ids but for the moment we don't have any way of delegation using the pool_id.
Describe alternatives you've considered
There aren't any.
Additional context / screenshots
There is a CLI command but it is not implemented yet.
cardano-cli shelley stake-address delegate \
    --signing-key-file pool_owner_stake.skey \
    --pool-id 2e78fd03436440cd494dc9445d2a1cb7f174de990935029d0939543e \
    --delegation-fee 200000
runStakeAddressCmd: StakeKeyDelegate (PrivKeyFile "pool_owner_stake.skey") (PoolId "2e78fd03436440cd494dc9445d2a1cb7f174de990935029d0939543e") (Lovelace 200000) (NodeAddress {naHostAddress = Nothing, naPort = 0})

You should be able to create a stake address delegation certificate using the cardano-cli shelley stake-address delegation-certificate command.
This can accept either a --cold-verification-key-file or a --cold-verification-key-hash (a stake pool ID).

Yeah, we can do better on the flag names and help description to make this more obvious. We should also make the poolid flag accept the new bech32 rendering for pool ids.

Interesting. I was able to give a pool_id as value for the --cold-verification-key-hash argument but my initial expectation was to see the new delegation into the output of cardano-cli shelley query stake-address-info right after the next tip (after the certificate was submitted through a tx), but that was not the case. I am waiting for next epochs...
cardano-cli shelley stake-address delegation-certificate \
    --stake-verification-key-file pool_owner_stake.vkey \
    --cold-verification-key-hash ece9c1424344714ef2b9294f56b6dfd655e952f65a28cc39b6814ec4 \
    --out-file stake_delegation_pool_id.cert

cardano-cli shelley query stake-address-info --testnet-magic 3 --address stake_test1uzep3545macvp0mjafnks5s906qx2rct5d2sajp7g4zn6js7hrekl --cardano-mode
{
    "e0b218d2b4df70c0bf72ea676852057e80650f0ba3550ec83e45453d4a": {
        "delegation": "4fbc00ab9baca6f9847b84ad22df1a85c7e4773e427acceb6bc1199c",
        "rewardAccountBalance": 0
    }
}

So even after a new epoch, the delegation value of the stake pool is not updated.


Android 11 (Target SDK 30) not able to open generated Pdf file

Location: Documents
Pdf file name: test.pdf
Not able to open the  pdf file
Android 10 (Target SDK 29) I'm able to open the pdf file.
Any help for this issue?
thanks in advance

Any update or fix for this issue?


TypeError: this.detailsOpen is undefined when clicking "Toggle Details"

Another TypeError as one gets with events now.
Tried several browsers and different OS's. Some browsers respond differently.
When clicking Toggle Details on any contract, nothing happens, but an error is logged, in Firefox the error comes out as

TypeError: this.detailsOpen is undefined  -  app.js:105063:65

in Chrome it's

Uncaught TypeError: Cannot read property 'Ballot' of undefined  -  app.js:105063

As you can see, in the Chrome error it specifies the contract as being undefined.
EDIT: Chriseth's old page does not have this issue.

fixed by https://github.com/ethereum/browser-solidity/pull/184


What should the website have?

Off the top of my head:

Information about the group (link to meetup, twitter)
Upcoming event
Past events with slides (+ videos?)
Projects (link to projects that the group is working on, collaboration 🚀)
How to join this group/github org

I would like to vote for projects 🙂. I feel It would Great learning that way.

@VenkateshKatabathula For now, I have started adding them to ReactBangalore/projects.
Feel free to look around/add your own 😄

adding sponsors
speakers info/links


IOS local build fail - ARCHIVE FAILED

Build/Submit details page URL
No response
Summary
When I run "eas build --platform ios --local --clear-cache" I get this error at the end:
Error: Unable to resolve module /tmp/eas-ios/build/node_modules/expo/AppEntry.js from /private/tmp/eas-ios/build/.:
None of these files exist:

../../../../tmp/eas-ios/build/node_modules/expo/AppEntry.js(.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx|.ios.mjs|.native.mjs|.mjs|.ios.js|.native.js|.js|.ios.jsx|.native.jsx|.jsx|.ios.json|.native.json|.json|.ios.cjs|.native.cjs|.cjs|.ios.scss|.native.scss|.scss|.ios.sass|.native.sass|.sass|.ios.css|.native.css|.css)

If I skip dir cleanup I can see the file node_modules/expo/AppEntry.js is present so it should be fine.
Live development work with no issues.
Two weeks ago I managed to successfully build an .ipa file, now it's not working. :(
Managed or bare?
bare
Environment
expo-env-info 1.2.0 environment info:
System:
OS: macOS 14.5
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.14.0 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.8.1 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.15.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
IDEs:
Android Studio: 2023.3 AI-233.14808.21.2331.11926650
Xcode: 15.4/15F31d - /usr/bin/xcodebuild
npmPackages:
@expo/webpack-config: ^19.0.1 => 19.0.1
expo: ^51.0.13 => 51.0.13
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.2 => 0.74.2
react-native-web: ~0.19.11 => 0.19.12
npmGlobalPackages:
eas-cli: 9.2.0
Expo Workflow: managed
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✖ Check Expo config (app.json/ app.config.js) schema
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
Detailed check results:
Error: Problem validating fields in /Users/vtiplea/Public/Projects/mobile/app.json. Learn more: https://docs.expo.dev/workflow/configuration/
• Field: android - should NOT have additional property 'useNextNotificationsApi'.
Error output
From terminal:
(1 failure)
[RUN_FASTLANE] ** ARCHIVE FAILED **
[RUN_FASTLANE]
[RUN_FASTLANE]
[RUN_FASTLANE] The following build commands failed:
[RUN_FASTLANE]  PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/vtiplea/Library/Developer/Xcode/DerivedData/Mobile-bxregnhwofiiuqadqaxzzwveacvs/Build/Intermediates.noindex/ArchiveIntermediates/Mobile/IntermediateBuildFilesPath/Mobile.build/Release-iphoneos/Mobile.build/Script-00DD1BFF1BD5951E006B06BC.sh (in target 'Mobile' from project 'Mobile')
[RUN_FASTLANE] (1 failure)
[RUN_FASTLANE] Exit status: 65
From logs:
Starting Metro Bundler
warning: Bundler cache is empty, rebuilding (this may take a minute)
/private/tmp/eas-ios/build/.:0: error: Unable to resolve module /tmp/eas-ios/build/node_modules/expo/AppEntry.js from /private/tmp/eas-ios/build/.:
Error: Unable to resolve module /tmp/eas-ios/build/node_modules/expo/AppEntry.js from /private/tmp/eas-ios/build/.:
None of these files exist:

../../../../tmp/eas-ios/build/node_modules/expo/AppEntry.js(.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx|.ios.mjs|.native.mjs|.mjs|.ios.js|.native.js|.js|.ios.jsx|.native.jsx|.jsx|.ios.json|.native.json|.json|.ios.cjs|.native.cjs|.cjs|.ios.scss|.native.scss|.scss|.ios.sass|.native.sass|.sass|.ios.css|.native.css|.css)

Reproducible demo or steps to reproduce from a blank project
eas build --platform ios --local --clear-cache

I am also facing this issue, posted about it in the discord and had only seen 2 people post about it in the discord and received no response.

I am also facing this issue, posted about it in the discord and had only seen 2 people post about it and received no response.

Hi!
I updated the expo package to 51.0.14 and I tried again the build.
Luckily it worked just fine now.

Hi!
I updated the expo package to 51.0.14 and I tried again the build.
Luckily it worked just fine now.

Good to hear it! @ahmad-elafify-pci did it also help you?

Hi!
I updated the expo package to 51.0.14 and I tried again the build.
Luckily it worked just fine now.

Good to hear it! @ahmad-elafify-pci did it also help you?

Same here! Today I did an expo-doctor and an npx expo install --fix which installed these dependencies:
<EMAIL_ADDRESS>- expected version: ~51.0.14
<EMAIL_ADDRESS>- expected version: ~15.0.11
<EMAIL_ADDRESS>- expected version: ~4.0.18
<EMAIL_ADDRESS>- expected version: ~1.12.12
<EMAIL_ADDRESS>- expected version: ~0.25.17

After that completed, I was able to finally build for ios again using eas build --local!  🎉

Awesome!


fix file uploads for new api

This provides a fix for #23. Have tested locally and integrated into one of my pipelines. No unit tests yet.

I think most of these errors are coming from my lack of handling multiple file uploads. I hadn't given such wrappings much thought.


revise readme doc

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/kind documentation

What this PR does / why we need it:
revise readme doc for OpenYurt v1.0
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/lgtm


add kubernetes go getting started

Tested locally, works around https://github.com/pulumi/pulumi-azure/issues/530
fixes https://github.com/pulumi/docs/issues/2967
Last PR that fixes https://github.com/pulumi/home/issues/767

Tested locally, works around pulumi/pulumi-azure#530

How is this related?

@mikhailshilkov the second step hits the bug that is linked (it's actually a bug in the kubernetes SDK, not the azure SDK). I have to write a few manual .Apply calls instead of using the kubernetes SDK builtins to work around. We should remove the apply calls from the example when the bug is fixed/released.


What does UserErrorUnableToOpenMount mean?

I could not found any solution on this page (or anywhere) for the following error:
error code: UserErrorUnableToOpenMount
error message:  Some mount point is not accessible.
recommended action: Check if all mount points of fstype Ext3/4, ReiserFS, JFS, XFS are accessible.
(this occurs on a centos 7 machine)

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

ID: 7f030558-66a5-d963-54a2-3f71643c5ef0
Version Independent ID: 2cdf6775-5ee9-83b6-3a1b-b87a682c1b1c
Content: Troubleshoot backup errors with Azure VMs - Azure Backup
Content Source: articles/backup/backup-azure-vms-troubleshoot.md
Service: backup
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

@w0ut0 we'll review your feedback and get back to you shortly. Thanks.

@w0ut0 Thanks for reaching out! Error code "UserErrorUnableToOpenMount" is typically observed when some mount point is not accessible or when mount points are not cleaned up. Recommendation action is to check if all mount points of fstype Ext3/4, ReiserFS, JFS, XFS are accessible.
Example: If you use file recovery option to RESTORE file and folders and if this operation does not cleanup mountpoints and still available on the VM, then the next backup might fail. Ideally the item level recovery script should have cleaned up the mountpoints and disconnected the iscsi initiators. To resolve this issue, use script again using clean parameter to remove the mountpoints (python 1.py clean) and then the backup should complete successfully. Also, to verify if the above failure is caused by this specific root cause, and to resolve the issue, there are various recommended steps / approaches.
Assigning @dcurwin for visibility, review and to consider enhancing the referred Azure document by adding the error code "UserErrorUnableToOpenMount" along with additional details.

Thank you @KrishnaG-MSFT, this was exactly what happened (a file and folder restore mount that was not unmounted well).
It would be great to have your remarks in the documentation/FAQ.

#reassign:GeethalakshmiG

@GeethalakshmiG - please let me know how to incorporate this into the documentation.

#reassign:pvrk

Thanks all for the good feedback. I have details of the error in the file recovery documentation. The troubleshooting document is for more common errors. If further evidence is found that this error is happening more frequently, will update the troubleshooting doc too.
Closing this since the documentation is updated.
#please-close


loading model camvid

Hi,
If I want to load the trained model for camvid, do I have to choose latest.pth zipped file as the checkpoint file or the data.pkl inside this file as the checkpoint??
in eval.sh, CHECKPOINT="${WORK_DIR}/latest.pth" while latest.pth is a zippped file, so I leave it like that or I unzip the file and I put CHECKPOINT="${WORK_DIR}/data.pkl", where data.pkl is inside latest.pth??
If leave latest.pth in eval.sh, I am getting this error: RuntimeError: [enforce fail at inline_container.cc:197] . file not found: archive/tensors/94018778419408
Thank you for considering my question

You should leave latest.pth in the checkpoint folder. Maybe the file is corrupted, download it again.

Thank you . I found that the problem was using pytorch 1.4.0 instead of pytorch 1.6.0. I upgraded pytorch and the problem was resolved.

@LeilaMaria Sorry to respond so late. It is recommended that first downloading the pre-rained model from camvid_weight (latest.pth), then put it on this path: "./work_dirs/tmanet_r50-d8_769x769_80k_cityscapes_video/latest.pth", finally run "sh eval.sh configs/video/cityscapes/tmanet_r50-d8_769x769_80k_cityscapes_video.py" to evaluation. Hope it is helpful for you.

@wanghao9610 Thank you for you reply. Yes, it works. The problem was that I was using pytorch 1.4.0, so it wasn't able to load the model.
Now, it is fine :)
Thank you :)


Fix import bug

The wrong import cause the isMatch function to be undefined. This was caused by a version upgrade a few commits back.

Hi @Romanitho ,
Your releaseType parameter is prerelease so its generating prerelease version number. Try with releaseType: patch

Hi, thanks for your help. But it doesn't seem to work. In fact, I would thought that I could have a nightly build release with incremental prerelease number by default, except if I specify another type in commit message. But it's a nice to have, I handle that with another github action task today, so I'm ok with that.
Anyway, thanks for your action, it helps ;)


QueuedInterceptor is flawed, which causes dead lock by design.

New Issue Checklist

[x] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Dio Version
dio 4.0.6.

Issue Description and Steps
I uses QueuedInterceptor to handle access token, very standard scenario:

Add Authorization header in onRequest
Refresh accessToken if server responds 401 in onError
Give up if server kept responding 401 after retried.

Code is very similar to official example: https://github.com/flutterchina/dio/blob/develop/example/lib/queued_interceptor_crsftoken.dart
As the code performs an retry as following code shown:
  @override
  Future<void> onError(
    DioError err,
    ErrorInterceptorHandler handler,
  ) async {
    // ... check whether should refresh token, if not return
    // ... refresh token
    // ... check whether should retry, if not return

    _logger.info('Retry request');
    final retryRequestOptions = error.requestOptions._createRetryRequestionOptions();
    await dio.fetch(retryRequestOptions).then(
          handler.resolve,
          onError: (error) => handler.reject(error as DioError),
        );
  }

Unfortunately, this code won't work, and it naturally causes dead lock by design:

It calls fetch on the same dio instance before onError is finished.
Due to how QueuedInterceptor works, calls to onError will be queued, next one won't be called until current one finished.
If a new error is raised during "retry", it would trigger an new onError requests, but it won't be processed because current onError is still running.
And the same time, current onError won't finish, as it depends dio.fetch to return, which requires onError returns first.
Dead lock!

I might be wrong, but it seems there is no solution to this bug, and InterceptorLock is marked as deprecated, so no idea how this would be done properly.

Find a workaround by separating the retry logic to a following normal interceptor:
So after the change, the onError become
  @override
  Future<void> onError(
    DioError err,
    ErrorInterceptorHandler handler,
  ) async {
    // ... code unrelated ...

    _logger.info('Schedule retry');
    requestOptions._markNeedRetry(retryRequestOptions);
    handler.next(err);

    // Code causes deadlock

    //  _logger.info('Retry request');
    // dio.fetch(retryRequestOption).then(
    //       handler.resolve,
    //       onError: (error) => handler.reject(error as DioError),
    //     );
  }

So the helper methods and RetryInterceptor:

const _retryRequestOptionKey = 'retryRequestOption';

extension RequestOptionsExtension on RequestOptions {
  void _markNeedRetry(RequestOptions retryRequestOption) {
    extra[_retryRequestOptionKey] = retryRequestOption;
  }

  RequestOptions? _checkNeedRetry() {
    final result = extra[_retryRequestOptionKey] as RequestOptions?;
    extra.remove(_retryRequestOptionKey);
    return result;
  }
}

class AuthRetryInterceptor extends Interceptor {
  final Dio dio;

  AuthRetryInterceptor(this.dio);

  @override
  void onError(DioError err, ErrorInterceptorHandler handler) {
    final retryRequestOptions = err.requestOptions._checkNeedRetry();

    if (retryRequestOptions == null) {
      return handler.next(err);
    }

    _logger.info('Retry request');
    dio.fetch(retryRequestOptions).then(
          handler.resolve,
          onError: (error) => handler.reject(error as DioError),
        );
  }
}

And this is dio setup:
dio.addInterceptors([
  authInterceptor,
  AuthRetryInterceptor(dio),
]);

Usually this is solved by using another (plain) instance of the Dio client which does not have the same interceptor to do the token refreshing or whatever calls you need to do before you exit the QueuedInterceptor.

Yes. A proper solution was like @kostadin-damyanov-prime mentioned using another Dio instance only for token updates.

Hey @kostadin-damyanov-prime @AlexV525, it seems you get the issue wrong:
The dead lock DOESN'T happen on the token refreshing but on RETRYING.
So using another Dio instance to refresh token WON'T prevent the deadlock.
Because it happens on ANY kind of error on RETRYING, such as server returns 500 or simply network timeout.

@timnew I see. I think the issue is caused by the following:

QueuedInterceptor is blocking by design. This means that if a request is executing code in the interceptor then the other requests are blocked and waiting for the current request to exit the interceptor.
You are using await in the retry error case. This adds a new request to the dio instance, which is currently blocked because it is waiting for the await call to return.

If you take a look at this code posted by the PRs author you will see they use then instead of await to retry the current call after the refreshing is done. This way the current call will set up a callback and exit the interceptor so the retry call can be executed next.
Note: I think the linked code example has another isue, which is tha tit ONLY uses then and no await at all. This is problematic in the case where there are multiple requests at once and the token needs to be refreshed. In this case the queue will not be blocked at all and the token will be refreshed the same number of times as the number of requests we have. I believe this will be solved by using in onError():

Use await to refresh the token. This will block the request queue and make the other requests wait for the refreshing to be done. This requires you to use another dio instance because the current one will be blocked.
After the refreshing is done just use then to retry the request that caused the 401 error. You may reuse the same dio instance because the queue will not be blocked.

@kostadin-damyanov-prime Thanks for the detailed explanation, I see what you mean.
For the code sample it might be better to written in a way as following:
 @override
  Future<void> onError(
    DioError err,
    ErrorInterceptorHandler handler,
  ) async {
    // ... code unrelated ...
    final requestOptions = error.requestOptions;

    // do things requires look
    final newToken = await _refreshToken(); // Await to block this method.
    ]

    // retry in a unblock way
    _retryRequest(requestOptions._markAsRetry(), handler).ignore(); // Retry in a new microtask and mark it as ignored.
  }

  Future<void> _retryRequest(
    RequestOptions retryRequestOption,
    ErrorInterceptorHandler handler,
  ) async {
    _logger.info('Retry request');
    await dio.fetch(retryRequestOption).then(
      handler.resolve,
      onError: (error) => handler.reject(error as DioError),
    );
  }

To be honest, I feel QueuedInterceptor is a overkill:

It doesn't prevent human mistake, instead it actually leads to human mistake, as people would tends to await the async functions
With this level of complexity, I just need to simply wrap the _refreshToken with a lazy completer, then I would have a parallel lock. It is much easier to be used, and less error prone, and we don't need to the complexity of the QueuedInterceptor introduced.
Dio instance have to differentiate QueuedInterceptor from normal interceptors, as it has to call some different private method to ensure the task is created in queue, rather than get executed immediately, which seems not to be a good design.

Something like this would be enough to prevent the parallel call.
Completer<String>? _refreshTokenCompleter;
Future<String> refreshToken() {
  if(_refreshTokenCompleter != null) return _refreshTokenCompleter!.future;

  final completer = _refreshTokenCompleter = Completer();

  try {
    final token = await _refreshToken();
    completer.complete(token);
    return token;
  } catch (ex, stacktrace) {
    completer.completeError(ex, stacktrace);
    rethrow;
  }
}
Future<String> _refreshToken() {
  // do actual refresh token logic here
}

Hello @kostadin-damyanov-prime, you mentioned
Note: I think the linked code example has another issue, which is that it ONLY uses then and no await at all. This is problematic in the case where there are multiple requests at once and the token needs to be refreshed.
I am not sure steps mentioned in the note will still work in case of multiple requests. Once say 3 concurrent requests get queued in the QueuedInterceptor on token expiry, & first one using await for refreshToken & .then for retry.
As handler.resolve or handler.next is called on success of retry, interceptor will queue in the 2nd requests onError and same process will repeat again? How will the 2nd request know in OnError to go for retry instead of refreshToken?
`class RefreshTokenInterceptor extends QueuedInterceptor {
final Dio dio;
AccessTokenStorage tokenStorage = AccessTokenStorage();
RefreshTokenInterceptor(this.dio);
@override
Future onError(DioError err, ErrorInterceptorHandler handler) async {
if (err.response?.statusCode == 401) {
await refreshToken(err, handler);
} else {
handler.next(err);
}
}
Future refreshToken(DioError err, ErrorInterceptorHandler handler) async {
String? refreshToken = await tokenStorage.getRefreshToken();
if (refreshToken == null) {
  handler.reject(err);
  return;
}

var tokenDio = Dio();
// setup headers, base urls & request for tokenDio
try {
Response response =
await tokenDio.post('/${path}', data:requestBody);
  if (response.statusCode == 201) {
    AccessTokenStorage.setRefreshToken(response.data['refresh_token']);
    AccessTokenStorage.setAccessToken(response.data['access_token']);

    await retryCurrent(tokenDio, err.requestOptions, handler);
  } else {
    handler.reject(err);
  }
} catch (error) {
  handler.reject(err);
}

}
Future retryCurrent(Dio tokenDio, RequestOptions requestOptions,
ErrorInterceptorHandler handler) async {
await tokenDio.fetch(requestOptions).then(
handler.resolve,
onError: (error) => handler.reject(error as DioError),
);
}
}`
I just started flutter 1 month ago and spent last week writing/looking for the right solution for this.
@timnew

I am still facing the same issue while making retry. any update on how its done??? @timnew

I just simply give up the QueuedInterceptor, it doesn't bring much value in but cause lots of trouble.
I can achieve similar lock mechanism inside of a normal interceptor with a Completer

@timnew workaround with the completer made the trick for me.
I spent a long time figuring out issues with QueuedInterceptor

@timnew would you mind sharing you're full refresh implementation ? Why do you think QueuedInterceptor has drawbacks ?


allowCollisions from ModifyPlanningScene doesn't update the ACM of ComputeIK

I recently realized that when attempting to allow the collision of an object using a ModifyPlanningScene stage and having a ComputeIK stage within it, collisions are not allowed. It seems this occurs because ComputeIK receives a monitored stage that doesn't have the AllowedCollisionMatrix updated with the changes made by the ModifyPlanningScene stage.
As a more pragmatic example of this issue, let's consider a scenario where we have a vacuum gripper end effector, and we want to allow the tool to partially intersect with the object to be picked. I suppose anyone new to MTC would write something like this:
CurrentState
Connect
ModifyPlanningScene (allow collisions between tool and object)
MoveRelative (linear approach towards the object)
ComputeIK
  GeneratePose
ModifyPlanningScene (attach object)
MoveRelative (raise the object)
ModifyPlanningScene (forbid collisions between tool and object)

However, this setup doesn't work. We need to add more ModifyPlanningScene stages to correctly disable collisions:
CurrentState
Connect
ModifyPlanningScene (allow collisions between tool and object)
MoveRelative (linear approach towards the object)
ModifyPlanningScene (forbid collisions between tool and object)
ComputeIK
  GeneratePose
ModifyPlanningScene (attach object)
ModifyPlanningScene (allow collisions between tool and object)
MoveRelative (raise the object)
ModifyPlanningScene (forbid collisions between tool and object)

Yet, ComputeIK still detects a collision. Even trying something like this doesn't work either:
...
ModifyPlanningScene (allow collisions between tool and object)
MoveRelative (linear approach towards the object)
ComputeIK
  GeneratePose
ModifyPlanningScene (forbid collisions between tool and object)
...

As far as I'm concerned, the current workaround, as explained here, is to use setIgnoreCollisions(true) to disable all collisions in ComputeIK. However, this can lead to unexpected results as it disables ALL collisions, making it difficult to debug because other parts of the scene might be colliding.
Our current workaround involves modifying the ComputeIK stage by adding an allowCollisions method, enabling us to manually set the pairs of links we want to allow collision for (without needing to allow ALL collisions). I can prepare a PR if you find it useful.
Nevertheless, I believe this behavior is very unintuitive, and it took me quite a while to realize what was wrong. I was thinking that perhaps one solution could be to individually add an allowCollisions method in each stage (similar to what we did with ComputeIK), so we wouldn't need to use ModifyPlanningScene to allow/forbid collisions anymore. This would address the ComputeIK issue, the need to use more ModifyPlanningScene stages than expected, making the list of stages cleaner, and simplifying the logic of allowing/forbidding collisions depending on the stage direction which might be tricky to understand and was a common problem looking back at the issues of this repo.
Let me know what you think about this or if there is any current fix to this issue. Thanks!

For grasping we use the following pipeline:

Here ComputeIK generates a grasp pose with fingers still open, then collision with fingers is allowed, and finally fingers are closed. In your case, the problem is indeed that ComputeIK attempts to find the grasp pose with the suction cup on/in the object, working on the PlanningScene inherited from CurrentState, which doesn't yet have collisions allowed.
You would need the following structure:
CurrentState
ModifyPlanningScene (allow collisions between tool and object)     --|
ModifyPlanningScene (disallow collisions between tool and object)    |
Connect                                                              |
ModifyPlanningScene (allow collisions between tool and object)       |
MoveRelative (linear approach towards the object)                    |
ComputeIK                                                            |
  GeneratePose                                                    <--|
ModifyPlanningScene (attach object)
MoveRelative (raise the object)
ModifyPlanningScene (forbid collisions between tool and object)

It would be simpler, if ComputeIK would compute a non-collision pose, and enable collisions and approach afterwards.

That actually works! I've never thought about using two ModifyPlanningScenes altogether to disable collisions of the monitored stage. It's a bit of boilerplate, in my opinion, but a feasible way to accomplish it at the moment.
However, when executing the task, a contact is found between the tool and the object, despite the planning being successful. I thought this might be corrected with your fix (https://github.com/moveit/moveit_task_constructor/issues/561), but it looks like there is still a problem.
I've prepared a simple repro to show the issue here. This is the log:
[move_group-4] [INFO] [1715174528.203091420] [moveit_collision_detection_fcl.collision_common]: Found a contact between 'object' (type 'Object') and 'panda_leftfinger' (type 'Robot link'), which constitutes a collision. Contact information is not stored.
[move_group-4] [INFO] [1715174528.203094460] [moveit_collision_detection_fcl.collision_common]: Collision checking is considered complete (collision was found and 0 contacts are stored)
[move_group-4] [INFO] [1715174528.203097992] [moveit_ros.plan_execution]: Trajectory component '7/10' is invalid after scene update
[move_group-4] [INFO] [1715174528.203099870] [moveit_ros.plan_execution]: Stopping execution because the path to execute became invalid(probably the environment changed)
[move_group-4] [INFO] [1715174528.203113053] [moveit.simple_controller_manager.follow_joint_trajectory_controller_handle]: Cancelling execution for panda_arm_controller
[ros2_control_node-5] [INFO] [1715174528.203299931] [panda_arm_controller]: Got request to cancel goal
[move_group-4] [INFO] [1715174528.203532894] [moveit_ros.trajectory_execution_manager]: Stopped trajectory execution.
[move_group-4] [INFO] [1715174528.246139697] [moveit.simple_controller_manager.follow_joint_trajectory_controller_handle]: Controller 'panda_arm_controller' successfully finished
[move_group-4] [INFO] [1715174528.246198979] [moveit_ros.trajectory_execution_manager]: Completed trajectory execution with status PREEMPTED ...

Friendly ping @rhaschke

I filed a backport of it: moveit/moveit2#2850. As soon as this gets merged, we can drop the corresponding MTC code reversion and it should work. (Your example works in MoveIt1).

Thanks a lot for your effort, Robert. As soon as the PR is merged, I will try it on my setup and close the issue if it is also resolved on my end.

Apart from that, your pipeline is not very meaningful: While you can disable collision checking during planning and execution (while approaching the object with closed fingers), the actual execution will surely move or topple the object due to a collision. Are you sure, you really want to do that?

The main reason for this is that our setup involves planning with objects that have many contact points, such as screwing a bolt into a nut. We could use collision meshes with a higher polygon count, but this significantly increases the planning time. To mitigate this, we use low-poly meshes, which requires us to have the final picking stage in collision.
Picking the cylinder with the gripper closed was the simplest way I found to illustrate a ComputeIK stage in collision within the pick/place demo.


Non-use issue

From @micheal-w-wells's email:
"Sarah has had this one for awhile, 2 things (may or may not be related):

Animals say as not provided when she selected 0
It doesn't let her recommend ready and says there is a problem with the schedule, the only anomalous bit other than above is that they are non use years, and I'm wondering if there is some funny javascript math going on, playing in the browser console i wonder if this is a hint:

She has had this for awhile and bad on me i lost it in the woodwork and lost track of it, but she has a good point that a lot of other non use agreements would have the same issue so we should get the guys to look at it if that makes sense to you also."

Having trouble reproducing this one. I'm setting # of Animals to 0 and my non-use is also 0.

@micheal-w-wells Can you check what's in the database for this RAN?

@micheal-w-wells Just going to ping you here again.

Closing as duplicate of #888


Added radioReset()

Required for BresserWeatherSensorLW

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
215

Relevant Lines:
215

💛  - Coveralls


Pubs 1589 - Reimplement Pubs Warehouse header navigation

Agree with the comment about the usa-banner. Will change that.


Error with certain characters in password

Hi, as shown in Porchetta-Industries/CrackMapExec#725 the RDPConnectionFactory throws an error if a password contains the symbol #. As you can see in the stacktrace from the issue, the method urlparse, used in commons->target.py line 68, uses the # character as seperator for "<fragments>", therefore not parsing the url correct and leading to not be able to return a port.
Here is a screenshot, that hopefully helps understanding the problem (this is output from the target.py def from_url function):

Yes, the URL format has this well-known problem with special characters, which can be easily mitigated by not using the URL format with string formatting. Looking at you @mpgn .
@NeffIsBack quick workaround could be to apply URLencoding to the password password%23freswa until the core issue is solved

Actually, scrap that it won't work like that either :/
That part will need some improvements, in the meantime you can hex-encode the password and use ntlm-pwhex auth method.

i will rewrite the code to use asyauth directly :)

Closing, as this code doesn’t exist anymore👍🏼


PRL-4981 - Test party names population in COS for hearing data

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the enable_keep_helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRL-4981
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

https://github.com/hmcts/prl-ccd-definitions/pull/1839


FilamentPHP filter not updating the record count

Package
filament/filament
Package Version
2.0
Laravel Version
10
Livewire Version
2.11
PHP Version
8.1
Problem description
The Laravel FilamentPHP filter query not updating the records.
I've UserResource and a column which is some of the entries of another table. I added the from and until filter in the table and when I try to update the counts, it's not updating.
public static function table(Table $table): Table
    {
        return $table
            ->columns([
                Tables\Columns\TextColumn::make('name')
                    ->sortable()
                    ->searchable()
                    ->toggleable(),
                Tables\Columns\TextColumn::make('email')
                    ->sortable()
                    ->searchable()
                    ->toggleable(),
                Tables\Columns\TextColumn::make('hospital.name')
                    ->sortable()
                    ->toggleable()
                    ->searchable(),
                Tables\Columns\TextColumn::make('contact_number')
                    ->sortable()
                    ->toggleable()
                    ->toggledHiddenByDefault()
                    ->searchable(),
                Tables\Columns\TextColumn::make('alliedHealthProfessional.designation')
                    ->label('Designation')
                    ->enum(FilamentFormHelper::getDesignations())
                    ->sortable()
                    ->toggleable()
                    ->searchable(),
                Tables\Columns\TextColumn::make('surgeries_count')
                    ->label('Entries')
                    ->counts('surgeries')
                    ->sortable()
                    ->toggleable()
            ])
            ->filters([
                Filter::make('created_at')
                    ->form([
                        Forms\Components\DatePicker::make('created_from'),
                        Forms\Components\DatePicker::make('created_until'),
                    ])
                    ->query(function (Builder $query, array $data): Builder {
                        return $query->withCount([
                            'surgeries as surgeries_count' => function (Builder $builder) use ($data) {
                                if ($from = $data['created_from'])
                                    $builder->where('surgeries.date', '>=', $from);
                                if ($until = $data['created_until'])
                                    $builder->where('surgeries.date', '<=', $until);

                                return $builder;
                            }
                        ]);
                    })
            ]);
    }

Expected behavior
The Entries column should update the count according to the filter. here is the demo.
Steps to reproduce
Add the from and until date filter in the filament resource table with the counts of relation 1:N table.
Reproduction repository
https://github.com/Umar-Farooq-Shafi/filament-filter-issue
Relevant log output
No response

The constraints from the filter aren't applied to the relationship count.
Make sure to add the relationship query constraints to the counts() method like so:
counts(['surgeries' => function (Builder $query) {
    // ...
}])

@zepfietje I don't want to apply constraints on the counts(). I want update the counts base on the date filter

why is this close? any solution or workaround? @zepfietje

You should access the active filters and apply the constraint to the counts() method as I explained above. That's the solution. 🙂

sorry, what is the sentence to access the active filter?

Something along those lines:
function (Builder $query, HasTable $livewire) {
    $livewire->getTableFilterState('created_at');
}

getting error
Too few arguments to function App\Filament\Resources\UserResource::App\Filament\Resources\
{closure}(), 1 passed in /Users/dev/Desktop/Personal/PMU/pmu-
ahp/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php on line 1603 and
 exactly 2 expected

Tables\Columns\TextColumn::make('surgeries_count')
                    ->label('Entries')
                    ->counts(['surgeries' => function (Builder $query, HasTable $livewire) {
                        dd($livewire->getTableFilterState('created_from'));
                    }])
                    ->sortable()
                    ->toggleable(),

Could you share more context of the error using a Flare exception link?

https://flareapp.io/share/B5ZAWWp7

Ah right, $livewire is probably not injected there.
Since this question isn't really a bug, could you ask for help in the #help channel in the Filament Discord server?
https://discord.gg/filament
I'm too busy working on finishing v3 at the moment, sorry.

I do not have permission to create a post. can you please help me?

click the button at the top to complete onboarding first

thanks @danharrin

@Umar-Farooq-Shafi did you find an answer for this?

Yes, on the ListRecord class. I added the following function
protected function getTableQuery(): Builder
    {
        if (is_null($this->tableFilters)) {
            return parent::getTableQuery()->withCount('patients');
        }

        $data = data_get($this->tableFilters, 'date', []);

        return parent::getTableQuery()->withCount([
            'patients as patients_count' => function (Builder $builder) use ($data) {
                $from = data_get($data, 'from');
                $until = data_get($data, 'until');

                if (! is_null($from) && $from !== 'null') {
                    $builder->where('patients.date', '>=', $from);
                }

                if (! is_null($until) && $until !== 'null') {
                    $builder->where('patients.date', '<=', $until);
                }

                return $builder;
            },
        ])
            ->withoutGlobalScopes([
                SoftDeletingScope::class,
            ]);
    }


-m switch fails

Hi,
On both server and client, when specifying the method, with -m, the following error is given:
./exfil.py -s IP -p 5353 -d "TEST" -m dns_lookup
usage: exfil.py [-h] [-d string | -f filename] (-l | -s server) [-p port]
                module_name
exfil.py: error: unrecognized arguments: -m

Details:
pip show dpkt
---
Name: dpkt
Version: 1.9.0
Location: /usr/local/lib/python2.7/dist-packages

pip show dnslib
---
Name: dnslib
Version: 0.9.7
Location: /usr/local/lib/python2.7/dist-packages

Since it works without the switch, but it's just a matter of removing it from the documentation?
Thank you!

Fixed documentation: https://github.com/averagesecurityguy/exfil/commit/992e3f7d27ff6fb264ed99cac1fcdfd85a22f9aa


Add support for debugging of MacOS apps

I've managed to get debugging working in VS Code with a little bit of work.

Fixed in 3043eb10a81fd4843d9b9eaa79dfff26c369bf90


Ghc 8.6.1

@itkovian this does not need a version bump somewhere?

@itkovian this does not need a version bump somewhere?


Broken dragging of grid panes

Describe the bug
We used to be able to drag grid panes. Now we cannot.
To Reproduce
Try to drag a component using its title as the drag handle.
Expected behavior
You would expect the background to turn light red and the component to move with your mouse until it snaps into a new position.
Environment:

Release or git hash: e77a35d
Browser: Firefox Developer Edition
Browser version: 69.0b7

I suspect it is the change to css classes that came with the css modules


[NEW ADDON] Sonarr Text Logo with 4K

[x] I have read the contributing guideline and understand that I have made the correct modifications

PR's are done against the develop branch.

Description:

Adding a new text version of the logo with the 4K mention on it, requested on #426
Benefits of this PR and context:

Being able to have radarr and sonarr look more alike.
How Has This Been Tested?

Same code as other logo replacement, just another image.
Source / References:

Sorry, still don't know how to choose which files are included in PR.

Sorry, still don't know how to choose which files are included in PR.

You have to checkout develop when making PR's against develop.

Base you PR on the develop branch


chore(sequencere_infra): add component client trait for remote

Stack:

#2079 ⬅
#2078

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.


module conflict

numpy1.11.2 and matplotlib are found to be conflict when installing.

Hi there,
I no longer have time to maintain this, feel free to file pull requests with any improvements/fixes.
Thanks.


Credentials could not be decrypted

Receiving following error when running a workflow with prior created credentials:

Error: Error: Error: Credentials could not be decrypted.
    at buildLangchain (/usr/local/lib/node_modules/flowise/dist/utils/index.js:230:19)
    at async App.processPrediction (/usr/local/lib/node_modules/flowise/dist/index.js:843:44)
    at async /usr/local/lib/node_modules/flowise/dist/index.js:559:13

Using Version 1.3.0 on docker with ENV PASSPHRASE and a 64 character random string

I noticed when I delete the credentials it takes to attempts the first attempt gets following error:
SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at decryptCredentialData (/usr/local/lib/node_modules/flowise/dist/utils/index.js:804:39)
    at async /usr/local/lib/node_modules/flowise/dist/index.js:420:45

on the second attempt the credentials can be deleted.
When then recreating them they can be used.
BUT
When the service is restarted then the same error it happening again:

Receiving following error when running a workflow with prior created credentials:

Error: Error: Error: Credentials could not be decrypted.
    at buildLangchain (/usr/local/lib/node_modules/flowise/dist/utils/index.js:230:19)
    at async App.processPrediction (/usr/local/lib/node_modules/flowise/dist/index.js:843:44)
    at async /usr/local/lib/node_modules/flowise/dist/index.js:559:13

Using Version 1.3.0 on docker with ENV PASSPHRASE and a 64 character random string

Also noticed the same problem with and without using the PASSPHRASE and when I want to edit a Credential its not opening and only this is showing:

Merged a fix - https://github.com/FlowiseAI/Flowise/pull/641 and pushed to v1.3.1
Try upgrade to v1.3.1, and delete the previous credential, create a new one

@HenryHengZJ is this really needed to generate a file containing the encryption key, as it seems it's build on the PASSPHRASE env variable? Keeping it in memory is not sufficient?

@HenryHengZJ  Ok just tried in 1.3.1 (by the way the Version on about did not change I just could verify over my docker service)
The same thing happens like here, but now the service craches afterwards:

Also noticed the same problem with and without using the PASSPHRASE and when I want to edit a Credential its not opening and only this is showing:

And also when recreating the credentials (with and without passphrase used as env. After the service gets reloaded they cannot be decrypted:

Error: Error: Error: Credentials could not be decrypted.
    at buildLangchain (/usr/local/lib/node_modules/flowise/dist/utils/index.js:230:19)
    at async App.processPrediction (/usr/local/lib/node_modules/flowise/dist/index.js:843:44)
    at async /usr/local/lib/node_modules/flowise/dist/index.js:559:13

@HenryHengZJ is this really needed to generate a file containing the encryption key, as it seems it's build on the PASSPHRASE env variable? Keeping it in memory is not sufficient?

the reason for having an encryption.key is to ensure the key is persistent, so you can decrypt/encrypt credentials, just like AWS KMS key.

@prononext i'd suggest delete all existing credentials you had there, and also make sure you have similar docker-compose.yml and .env file as here


Enhance documentation: Use 'this' return type for chainable methods

The polymorphic this type makes it clear that when using these methods on an instance of a
subclass, you get the same instance of that subclass back (instead of a
possibly different instance of the parent class).

Thanks! Merged, and attached patch adjusts the documentation builder to actually allow that type.

Okay, attaching didn't work again because I referenced the wrong repository — I meant patch https://github.com/ProseMirror/website/commit/1e69184c9d2af7237448aa6f71d643dbf9f1b900


Feature request - command to create a new address

There is wallet delete_addr but there's no way to create a new address with in neo-python.
neo-cli has such a command
 create address [n=1]
The command can be handy for testing smart contract interaction between multiple addresses. e.g. NEP-5 transfers.
Thank you!

#529


unable to span Windows into narrow box in Fancy Zone running Windows 10

Microsoft PowerToys version
v0.57.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
It has never worked properly, I've reloaded the program and downloaded the latest updates, but it does not work.
✔ Expected Behavior
I expected the windows to put multiple windows vertically on a custom screen, however the snap element is not working on narrow boxes within the custom design. My minimised window will snap into a larger box, so I think that illustrates it is partly working.
Running as administrator
Windows default snap is switched off
❌ Actual Behavior
When I try to snap a Windows into a narrow custom box, it just aligns one edge to the box selected but does not reduce the width of the windows and the Window ends up over lapping the next section.
Other Software
No response

Some windows have minimal width and height, we can't violate that, I'm sorry.


Do we support different audio files and subtitles ?

Describe the bug
We have a requirement to support a video with different audio and subtitles.
Do we have any way through which we can support this feature with Amazon-ivs-react-native-player?
If not, do we have any plan to develop this feature?

Hi @bhupendra-cvent: Is the video you are attempting to play generated through IVS? The IVS player only supports IVS content. We cannot guarantee compatibility/performance when playing 3P content.

Yes, video is generated through IVS, and multiple audios are embedded along with the video streaming URL. But subtitles are not embedded. They are fetched from different URLs.
Do we know how, if you guys have any plan to provide these features to support different audios and subtitles?


feature(cli): login flow fixes and improvements

What does this PR do?
This PR fixes issues with the CLI login flow and enables headless CLI login mode.
Does your PR introduce any breaking changes? If yes, please list them.
No.
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @borda

I have validated that this works against prod.


Creating a GPU-only buffer trips IsMappingAllowed VMA_ASSERT when using VMA_DEBUG_INITIALIZE_ALLOCATIONS

We recently migrated to v3.0.0 along with the new API for selecting preferred memory types.
We use VMA_DEBUG_INITIALIZE_ALLOCATIONS in our debug builds to help identify memory corruption issues.
Following https://gpuopen-librariesandsdks.github.io/VulkanMemoryAllocator/html/usage_patterns.html we create GPU-only buffers with vmaCreateBuffer as follows:
Setup VmaAllocationCreateInfo:
VmaAllocationCreateInfo allocCreateInfo = {};
allocCreateInfo.usage = VMA_MEMORY_USAGE_AUTO;
allocCreateInfo.flags = VMA_ALLOCATION_CREATE_DEDICATED_MEMORY_BIT;
Setup VkBufferCreateInfo with buffer usage flags:
VK_BUFFER_USAGE_STORAGE_BUFFER_BIT | VK_BUFFER_USAGE_TRANSFER_SRC_BIT | VK_BUFFER_USAGE_TRANSFER_DST_BIT
In combination VmaAllocation_T::IsMappingAllowed returns false for the resulting dedicated allocation which trips a VMA_ASSERT in VmaAllocation_T::BlockAllocMap() when attempting to call FillAllocation which seems wrong to me.
We can workaround the issue by removing VMA_DEBUG_INITIALIZE_ALLOCATIONS for now so its not a huge issue for us.
Please let me know if you need anymore information relating to this issue.

Thank you for reporting this issue. I confirm it was a bug. Please let me know if the fix I committed works for you.

Thanks for the swift fix! I can confirm that fixes the issue I was seeing


Feature/news api

Added News Feature using api of newsapi.org

Can get # of articles from given source and in provided order (latest, popular etc)
Can get list of sources for given language, country and category

Screenshots:

Waiting for review.

@Samy-33 Hi, reviewed your a PR, thanks! nice one! but I left a couple of comment;)

Yes, removed unnecessary parentheses and made is more readable. :)

@Samy-33 Thanks;) I'll check in 2-3 hours

@Samy-33 Merged;) add your name into CONTRIBUTORS.md file


Add custom headers to tile requests

I'm trying to connect to a secure tile server that requires passing authentication details in the header of each tile request. I can't for the life of me find any way to append customer header values to the tile requests.

I think you'd need to override the fetch method of the imageTile class to do this.  It uses an HTMLImageElement to fetch the actual tile (see src/imageTile.js).
HTMLImageElement doesn't support setting custom headers.  I think you'd have to switch to fetching the image via an XMLHttpRequest where you can set headers, and, once that returns, set the HTMLImageElement's src to a URL.createObjectURL of the returned data.

I think you'd need to override the fetch method of the imageTile class to do this.  It uses an HTMLImageElement to fetch the actual tile (see src/imageTile.js).
HTMLImageElement doesn't support setting custom headers.  I think you'd have to switch to fetching the image via an XMLHttpRequest where you can set headers, and, once that returns, set the HTMLImageElement's src to a URL.createObjectURL of the returned data.

Thanks. I managed to figure out how to get this working. In my case I'm leveraging osmLayer, and need to override the _getTile function. I'm going to create a new class that extends the osmLayer and overrides this function so that I don't change how the osmLayer works when used normally.

Thanks. I managed to figure out how to get this working. In my case I'm leveraging osmLayer, and need to override the _getTile function. I'm going to create a new class that extends the osmLayer and overrides this function so that I don't change how the osmLayer works when used normally.


Where are you using this?

I'm curious about the meta plans for this repo. :)

I'm planning on using this in all of my libraries to encourage people to contribute and remind them that not all contributions are code. And to thank those who have contributed in any way to the project. Thanks for asking!

Cool! Good luck.


Not working

It look dead,  0 views
sh: 1: title: not found
sh: 1: title: not found
sh: 1: sh: 1: sh: 1: title: not found
title: not found
title: not found
sh: 1: sh: 1: title: not found
title: not found
and just get it, zero views tried with socks5 and http proxies but still 0 views
@Wizz1337

im fixing rn


Fail when kubectl apply returns non-zero status

Previously, when kubectl apply returned non-zero status we've been only printing the warning. This caused issues like https://github.com/Shopify/kubernetes-deploy/issues/20. We should raise an error and stop the deploy in this case.
review @KnVerey @sirupsen @wfarr

Closes https://github.com/Shopify/kubernetes-deploy/issues/20

@wfarr here is the config I tried:
apiVersion: extensions/v1beta1
kind: ThirdPartyResource
description: "Redis Third"
metadata:
  name: "redis.shopify.io"
versions:
  - name: v1

The script prints this since we don't have a third party resource handler:
[WARN]  Don't know how to monitor resources of type thirdpartyresource. Assuming thirdpartyresource/redis.shopify.io deployed successfully.

and after the successful deploy I could verify that it was created:
$ kubectl get thirdpartyresources
NAME               DESCRIPTION   VERSION(S)
redis.shopify.io   Redis Third   v1

Ah word, I didn't look at this carefully enough. This should be safe yeah.


@addTagHelper fails when attempting to reference an assembly from the GAC

The @addTagHelper directive fails when attempting to reference an assembly that is in the Global Assembly Cache with the error message:
Cannot resolve TagHelper containing assembly '<AssemblyName>'. Error: Could not load file or assembly '<AssemblyName>' or one of its dependencies. The system cannot find the file specified. @addTagHelper "*, <AssemblyName>"

@rickandersen could you try and Assembly.Load the assembly in question in a console application? That's all TagHelper resolution is doing at its core.

The Assembly.Load works when I provide the full name of the assembly (ie , Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=), but I am unable to specify the full name in the @addTagHelper directive as that throws a compilation error.
I am using the assembly in other areas of the app so I am sure it is referenced properly in the project.

It does not work if you use the non fully qualified name though?

Correct.  Without the fully qualified name I receive this exception:
An exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll but was not handled in user code

/cc @DamianEdwards @Eilon

I don't think we intend to support loading tag helper assemblies from the GAC.


Parallel tests

Parallelize Alpaca tests: (https://github.com/Islandora-CLAW/CLAW/issues/712)
What does this Pull Request do?
Parallelizes the tests in alpaca/islandora-indexing-fcrepo by route.
What's new?
Splits tests up into classes by route being tested and runs them in parallel.
An additional commit is included showing a possible shortening of test setup patterns. If it looks attractive, I can use it more widely.
How should this be tested?
This PR should not change the functional behavior of Alpaca at all. It should speed up build time by some small amount.
Interested parties
@Islandora-CLAW/committers

@ajs6f After pulling this down and running a ./gradlew clean build I'm getting java.lang.IllegalStateException: ProducerTemplate has not been started for every islandora-indexing-fcrepo test.

Hm, weird. I never saw anything like that. What's your setup? (OS, JDK, etc)

@ajs6f it is my understanding that, if you use Camel's AdviceWith mechanism, you need to manually run Context::start in the route tests. See here for more information: http://camel.apache.org/advicewith.html In particular:

From Camel 2.9: it's recommended to override the isUseAdviceWith() method and return true to tell Camel you are using advice with in your unit tests. Then after you have done the adviceWith(), then you must start CamelContext manually.

@acoburn What is odd is that I specifically took the context.start()s out, because the context is getting started in the (Camel) superclasses and because the adviceWith calls on the RouteDefinitions restart those routes (which is actually annoying, but they do). So I don't understand why this works on my box and Travis but not on @dannylamb's.
I'd like to get to the bottom of this, but I'm actually not at work today, so I won't be doing much with this today.

@acoburn @ajs6f That's interesting.  And it's certainly not a pressing issue.
FYI I'm on ubuntu 16.04 with openjdk version 1.8.0_131.  I also wiped my repo and re-cloned just to make sure there wasn't any caching shenanigans and hit the errors again.

@ajs6f it has been a while since I really dug into the details of how camel does this -- but as I recall, the camel superclasses do start the context, but they do so before the routes are "patched" with adviceWith. And that's why one needs to call context.start() again after these changes, though (IIRC) I've also seen variability in the specific behaviors of test routes w/r/t manually calling context.start(). I'll try running this on my machine (JDK 9)

JDK 8 seems to work fine for me, but JDK 9 doesn't work so well with the tests (lots of NoClassDefFoundErrors, which isn't entirely surprising). At some point, it might make sense to enable JDK 9 tests on travis, given that JDK 9 will be released today. Here is an example -- you can even configure it so that Travis permits test failures. Also, (and this is orthogonal to the discussion here), you may also want to enable Windows-based tests using AppVeyor: it's just another angle to test your code in a different environment. See here for an example.

@acoburn I think those are good ideas-- can you open two tickets for them, because I have two toddlers and by the time I get to the end of this sentence I will have already forgotten what the two good ideas were. What two good ideas?

@ajs6f thanks for the nudge. Here are the tickets: https://github.com/Islandora-CLAW/CLAW/issues/715 and https://github.com/Islandora-CLAW/CLAW/issues/714

Okay, so I'm going to add in a bag of context.starts() to see if that helps @dannylamb . Before I do that, are there opinions about the second commit? Think optometry-- is it better or worse?

@ajs6f I think the parallelism is what's important here.  The utility functions are great, but I wouldn't get too wrapped up in improvements to these tests.  Now that Api-X installs and claw-playbook is settling down, I can finally issue PRs for Islandora-CLAW/CLAW#640, including https://github.com/dannylamb/Alpaca/tree/issue-640, which significantly reduces the scope of islandora-indexing-fcrepo and its tests.

K, for expediency I'll back out that last commit, put in the context.starts(), and we can try it again.

@dannylamb That should do it, I hope. Give 'er a try!

@ajs6f Travis seemed to hiccup there.  I restarted it.
Getting 1 test failure now due to a java.util.zip.ZipException, so I'm going to retry those too and see what happens.  Seems weird just one of those would pop.

Weird, yeah. Every once in a while I've seen a ZipException from a corrupted JAR file.

Seems like we're running more tests now?  islandora-indexing-fcrepo just ran 97 tests and took 18 minutes to complete locally.  I don't recall the exact amount, but I though the number of tests was more like 50, not 100.

TBH, I don't understand how Gradle is counting tests at all-- @Test annotations?

@ajs6f yes, it uses the @Test annotation

daniel@daniel-Latitude-3560:~/Code/Java/Alpaca$ grep "@Test" islandora-indexing-fcrepo/src/test/java/ca/islandora/alpaca/indexing/fcrepo/*.java | wc -l
49

Looks like we're almost doubling up?

Travis seems to have failed at git checkout?

@dannylamb @acoburn I have no idea about the "doubled" tests. Let me check and see if my test suite setup is running them, and then they are running by themselves. I should be able to fix that.

@ajs6f you may also find some clues if you look at the Gradle test report.

@acoburn++ I just dug through mine and can confirm the tests are getting run twice.

k, I'll rework the test execution to fix that.

Now I'm using Gradle's forking ability to run in parallel. Let's see how that goes.

@ajs6f I'm running it now and it behaves like it's running in parallel.  It's exhibiting long pauses followed by 4-5 successes at once.

And is running exactly 49 tests.  Think you got it this time.

Good, although that's what it was doing before for me, so now

Indeed


Unit test coverage for DeleteRepo and upsertRepo functions in repository reconciler

/assign @vjayaramrh @rravindran123 @efiacor @lapentad
Unit test coverage for a small function as a starting point.

/lgtm @liamfallon overall, the approach looks good to me, We may also want to do a POC using https://pkg.go.dev/github.com/stretchr/testify/mock to generate mocks and see if it could be better. I have used it and found it useful to create mocks and write unit tests. We may have to come up with training material to make it easy for community members to adopt this if we think it is good. Also, does it make sense to rename the directory from repository to gitea-repository as the code is specific to gitea?

Yes, we should also try to do a POC to try the mock generation.
It probably would be a good idea to rename this to gitea-repository but maybe let's discuss this in the community and take it in another PR

Can I have some reviews on this PR please?

/approve
/lgtm


Testnet NFT minting doesn't work

Description
I am facing this issue for last 5 days at Testnet Mintbar
1 - Blade wallet not connecting at all. When I click on Connect Blade wallet, it automatically gives following error -

2 - Hashpack connects and goes to final screen to mint collection but NFT preview fails with txn fee error (PS. I have 1000 HBARS in the testnet account)
Steps to reproduce
For Hashpack error -
1 - Connect Hashpack
2 - Upload NFT image and fill name, description
3 - Click on next and go to final "Confirm screen"
4 - After confirming, my hashpack wallet gets following txn -

This txn gets approved and immediately following it, I get another NFT mint txn as shown below -

This 2nd txn fails with following error -

{ "name": "StatusError", "status": "INSUFFICIENT_TX_FEE", "transactionId"<EMAIL_ADDRESS>"message": "transaction<EMAIL_ADDRESS>failed precheck with status INSUFFICIENT_TX_FEE", "contractFunctionResult": null }
Additional context
No response
Hedera network
testnet
Version
v9.1.0 - Hashpack
Operating system
Windows

Hi there, thank you for reporting both of these issues.

Blade wallet incompatibility.
This is a known issue. The Blade wallet SDK introduced breaking changes recently and we haven't yet updated Mintbar to re-support Blade wallet. Instead, we are waiting to integrate with Hedera Wallet Connect once it's ready. For now, please use Hashpack.

Transaction fee error when using Hashpack v9.10
Are you able to reproduce this? I was unable to as you can see with tx_id https://hashscan.io/testnet/transaction/1696342693.661191701.  Also, I looked at your testnet account https://hashscan.io/testnet/account/0.0.3434367 and it does seem that you have plenty of testnet hbar to cover the tx.

I see you are also able to create the NFT Collection, but not mint NFTs into it. Very strange.

Hi there, thank you for reporting both of these issues.

Blade wallet incompatibility.
This is a known issue. The Blade wallet SDK introduced breaking changes recently and we haven't yet updated Mintbar to re-support Blade wallet. Instead, we are waiting to integrate with Hedera Wallet Connect once it's ready. For now, please use Hashpack.
Transaction fee error when using Hashpack v9.10
Are you able to reproduce this? I was unable to as you can see with tx_id https://hashscan.io/testnet/transaction/1696342693.661191701.  Also, I looked at your testnet account https://hashscan.io/testnet/account/0.0.3434367 and it does seem that you have plenty of testnet hbar to cover the tx.

I see you are also able to create the NFT Collection, but not mint NFTs into it. Very strange.

Yes, i am able to reproduce it. It's happening everytime. The first NFT collection txn succeeds but not 2nd txn. Actually i have around 9000 hbars in my testnet account as shown below -

on failure, can you check the browser's console and post any error messages thrown by Mintbar?
We've had multiple people try to reproduce this and not able to (yet). It could be a Hashpack issue, but let's check the browser console.

So, I uninstalled and installed hashpack, cleared mintbar site data, then tried and got same error.

The logs below comes like 4-5 secs after the txn fails

ok thank you, we're looking into it.

hey @SkillerChampion can you try with incognito enabled? The hashpack team also tested this without issues.
I know you said that you've cleared the mintbar cache, but it looks like an issue identifying your active wallet. Maybe something with the Blade attempt has confused how we check for the active wallet.

hey @SkillerChampion can you try with incognito enabled? The hashpack team also tested this without issues.
I know you said that you've cleared the mintbar cache, but it looks like an issue identifying your active wallet. Maybe something with the Blade attempt has confused how we check for the active wallet.

So, I tried in incognito but unable to connect wallet because the icognito mode is missing hashpack extension, but I changed my google account profile on chrome. Added testnet account in hashpack and tried and got same error.
How in the world is this working for you guys ?? I am getting same error everytime

I uninstalled and installed hashpack
Does this mean that you re-imported the private key into a new hashpack installation?

we encountered other issues (still haven't been able to reproduce yours) but deleting the account from hashpack and re-importing it via private key seemed to resolve the issues.

hi again @SkillerChampion ....i spoke with the Hashpack team and they are pushing a new version with a few fixes regarding signing issues. I believe this will resolve your issue, but we need to wait on them.


[Bug]: ng-tsparticles load engine with [particlesInit] gets called everytime

Contact Details
<EMAIL_ADDRESS>What happened?
Just started today with this awesome library and after some struggling and digging through the documentation I eventually found an issue or I misunderstood something.
The following use case: I have two <ng-particles [particlesInit]="init"> components placed on a page.
The init function is the following and does partial loading of what I need.
  async init(engine: Engine): Promise<void> {
    if (
      engine.domArray.some((dom) => dom.id === (this as any).id)
    ) {
      // FIXME bugfix!
      return;
    }

    // see full: https://github.com/matteobruni/tsparticles/blob/main/bundles/full/src/index.ts
    // see slim: https://github.com/matteobruni/tsparticles/blob/main/bundles/slim/src/index.ts
    await loadBaseMover(engine);
    await loadParallaxMover(engine);
    await loadParticlesCollisionsInteraction(engine);
    await loadTextShape(engine);
    await loadLifeUpdater(engine);
    await loadOpacityUpdater(engine);
    await loadSizeUpdater(engine);
    await loadAngleUpdater(engine);
    await loadColorUpdater(engine);
    await loadOutModesUpdater(engine);
    await loadEmittersPlugin(engine);
  }

So this functions gets called two times and it works.
But one <ng-particles [particlesInit]="init" *ngIf="condition"> has a ngIf which is used to toggle visibility (not always needed).
Whenever I toggle it, the init function gets executed.
This will fill the engine.plugins.movers map for example with many entries of the same id.
My bugfix to check if the domArray has already the id will fix this issue.
I just noticed it by accident, because whenever I toggle and loadABC(engine) the other ng-particles does emit for some and places an particle on the canvas. (the particle count is 0 when I check it, but I would need to call container.canvas.clear(); to remove it) After further investigation it seems to be in relation with the multiple loading.
Am I misunderstanding something or is this a bug?
If the issue is still not clear, let me know. I try to create an example project.
I know documentation is probably the last thing, but it took me while to figure out everything I want.
Eventually I find some time to contribute where I can. ❤
tsParticles Version
2.0.6
Which library are you using?
Angular (ng-particles)
tsParticles Configuration
export const conficParticlesDefault: IParticlesProps = {
  fpsLimit: 60,
  detectRetina: true,
  pauseOnBlur: true, // Pauses the animations when the page isn't on foreground
  pauseOnOutsideViewport: true, // Pauses the animations when the element is out of the viewport
  motion: {
    disable: true, // If set to true, disables animations for users with prefer-reduced-motion enabled
  },
};

export const configCookiesBackground = Object.assign(
  {},
  conficParticlesDefault,
  {
    interactivity: {},
    particles: {
      opacity: {
        value: 0.6,
      },
      move: {
        direction: MoveDirection.outside,
        enable: true,
        outModes: {
          default: OutMode.bounce,
        },
        random: true,
        speed: {
          min: 2,
          max: 4,
        },
        straight: false,
      },
      number: {
        limit: 10,
        value: 10,
      },
      rotate: {
        direction: RotateDirection.random,
        random: true,
        animation: {
          enable: true,
          speed: 5,
        },
      },
      collisions: {
        enable: true,
        mode: CollisionMode.bounce,
        overlap: {
          enable: true, // prevent placing issue and warning spam
        },
      },
      shape: {
        type: 'character',
        character: {
          value: '🍪',
        },
      },
      size: {
        value: { min: 20, max: 50 },
      },
    },
    responsive: [
      {
        maxWidth: 520,
        mode: ResponsiveMode.canvas,
        options: {
          autoPlay: false,
          particles: {
            life: {
              count: 0,
              duration: 0,
            },
          },
        },
      },
      {
        maxWidth: 1000,
        mode: ResponsiveMode.canvas,
        options: {
          particles: {
            number: {
              limit: 5,
              value: 5,
            },
          },
        },
      },
    ],
  } as IParticlesProps & RecursivePartial<IEmitterOptions>
);

export const configCookiesCrumble = Object.assign({}, conficParticlesDefault, {
  autoPlay: false,
  motion: {
    disable: false, // override, because we want to show it
    reduce: {
      value: true,
    },
  },
  particles: {
    number: {
      value: 0,
    },
    collisions: {
      enable: false,
    },
  },
  duration: 5000,
  emitters: {
    rate: {
      delay: {
        max: 0.0001,
        min: 0.0001,
      },
      quantity: {
        max: 1,
        min: 1,
      },
    },
    life: {
      count: 2,
      duration: 0.1,
    },
    direction: MoveDirection.top,
    domId: 'cookie-spawn',
    fill: false,
    particles: {
      collisions: {
        enable: true,
        mode: CollisionMode.bounce,
        overlap: {
          enable: true, // prevent placing issue and warning spam
        },
      },
      number: {
        value: 0,
      },
      life: {
        duration: {
          value: 5,
          sync: true,
        },
      },
      move: {
        collisions: true,
        bounce: true,
        direction: MoveDirection.bottom,
        enable: true,
        outModes: {
          default: OutMode.bounce,
        },
        random: true,
        speed: 1,
        straight: false,
        gravity: {
          enable: true,
          acceleration: 10,
        },
      },
      shape: {
        type: 'character',
        character: {
          value: '🍪',
        },
      },
      size: {
        value: 15,
      },
    },
  },
} as IParticlesProps & RecursivePartial<IEmitterOptions>);

What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

It's definitely a bug, thanks for reporting that

Yeah probably, I went a bit through the source code and also created as promised a tiny example:
https://stackblitz.com/edit/ng-particles-load-engine-bug?file=src/app/app.component.ts
If you click the visible button, you notice that there appears a dolphin (but it shouldn't) and it also freezes / stutters a bit (I assume due to loading the engine multiple times)
If you enable the flag PREVENT_ENGINE_LOAD_BUG it won't happen and only load the engine once.
My fix in the bug report is therefore also garbage - validating the id if it exists already is wrong. It must be only loaded once as far as I understood. Otherwise the bug appears.
The issue with movers filling is another bug. It must be related in the way the container is created and handled
In Plugin.ts the map is initialized at this.movers = new Map<Container, IParticleMover[]>(); (https://github.com/matteobruni/tsparticles/blob/main/engine/src/Core/Utils/Plugins.ts#L92)
I assume the container reference changes, etc. because after debugging it, it will always set a new entry in the map.
https://github.com/matteobruni/tsparticles/blob/main/engine/src/Core/Utils/Plugins.ts#L92
    getMovers(container: Container, force = false): IParticleMover[] {
        let res = this.movers.get(container);
        if (!res || force) {
            res = [...this.moversInitializers.values()].map((t) => t(container));
            this.movers.set(container, res); // <<<---- container is always a different reference and will constantly set because it won't be found or through force flag
        }

        return res;
    }
´´´

Easy solution would be to use a key string (the id), idk if that would break the backwards compatibility though ;)


Draft setup-gh not working

Encountered below error while setting up Draft with VS Code DevX etension
Command Name
az aks draft setup-gh Extension Name: aks-preview. Version: 0.5.97.
Errors:
The command failed with an unexpected error. Here is the traceback:
Binary check was NOT executed successfully
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "C:\Users\DTSANDKUMA\.azure\cliextensions\aks-preview\azext_aks_preview\custom.py", line 1884, in aks_draft_setup_gh
    aks_draft_cmd_setup_gh(app, subscription_id, resource_group, provider, gh_repo, path)
  File "C:\Users\DTSANDKUMA\.azure\cliextensions\aks-preview\azext_aks_preview\aks_draft\commands.py", line 48, in aks_draft_cmd_setup_gh
    file_path, arguments = _pre_run(download_path,
  File "C:\Users\DTSANDKUMA\.azure\cliextensions\aks-preview\azext_aks_preview\aks_draft\commands.py", line 136, in _pre_run
    raise ValueError('Binary check was NOT executed successfully')
ValueError: Binary check was NOT executed successfully

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks draft setup-gh

Expected Behavior
Environment Summary
Windows-10-10.0.17763-SP0
Python 3.10.5
Installer: MSI

azure-cli 2.39.0

Extensions:
aks-preview 0.5.97
ssh 1.0.1

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

route to CXP team

Same error for az aks draft create as well. see below reported issue.
https://github.com/Azure/azure-cli-extensions/issues/5336

Should be a bug of aks-preview on windows, can be reproduced with older versions. The following screenshot is captured with an extra --debug option to the command.
The binary check tried to download the binary of aks-draft from https://github.com/Azure/draft/releases/download/v0.0.22/draft-windows-amd64 and met 404. The correct url should be https://github.com/Azure/draft/releases/download/v0.0.22/draft-windows-amd64.exe.

A workaround is to download the binary (for aks-preview >= 0.5.99, please choose v0.0.22, for aks-preview <= 0.5.97, please choose v0.0.23, aks-preview 0.5.98 won't work) in advance, rename it to remove the .exe suffix and move it to the directory where this command is used.

Fix is on the way, will release a new version of aks-preview to fix it.

@skazure Did you check with the new version if this has been fixed.

@skazure We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Steps Controller Not working

Hi,
Each steps, controller not working ( Am setting $rootScope value from the ctrl ,its not functionalable)
app.controller('Step1Ctrl', function ($scope, multiStepFormInstance,$rootScope) {
$rootScope.isJoinStep = false;
});

What is not working?

Sorry, the problem was, i had created multiple Ctrl with same name


Feat/intindy 2216 create trigger terraform provider

Updating the handling of the event_ttl_seconds field to allow for it to be optional. neeeded to update to string so that terraform UI did not show a bad response that would confuse users on gets when event ttl was not included.
Adding validation for event_ttl_seconds.

The schema.ResourceData that we use to return the values does not allow us to remove a field from it even when the field is null from the backed API. This resulted in us showing bad information when running the terraform apply from cli. It would show that event ttl was set to 0, even though it really was null in the backend. In order to avoid the confusion for the time being we decided to use a string to represent what is in the backend, and an empty string means that it is not set.
It seems that if there was a remove on the schema.ResourceData then before we returned this result if it does not exist in backend, we could remove it.
From documentation of https://github.com/hashicorp/terraform-plugin-sdk:
In the meantime, some providers have found success in using strings instead of numbers, which is a confusing user experience, but unlocks the ability to use "" to detect “unset” and "0" for 0. This is far from ideal, but again, is another option that can unblock you immediately.

Everything should be good to go for this now. I also fixed a bug i ran into with attempting to update the topic name. Our API does not allow updates to this field so i failed throw an error when someone tries to update it.