Plug-in Not Responding

I just installed BRAW Toolbox and after importing the BRAW clips into FCP I get the error " The Plug-in BRAWPlugin is not responding.  This plug-in will be disabled"
I do have sound, just no video.
I restarted the Mac and deleted FCP prefs
I tried to uninstall the app using your uninstaller but it failed.  Here are some screen shots

Sorry for the delayed reply, and sorry you're running into issues!
I assume you've installed the Motion Template, etc?
See: https://brawtoolbox.io/installation/
If you haven't already, can you try granting sandbox access to the drive which contains your BRAW files, restart your computer, and see if that helps?
See: https://brawtoolbox.io/collaboration/
If you're still having issues, can you please send across any crash logs and log files?
See: https://brawtoolbox.io/troubleshooting/#ive-run-into-a-bug-where-can-i-find-the-log-files

Closing this issue for now, feel free to re-open if you're still having issues.


Rancher UI shows a non-descriptive error when there is a problem provisioning an AKS cluster

Setup

Rancher version: 2.7.2
Rancher UI Extensions:
Browser type & version:

Describe the bug
When provisioning a downstream AKS cluster from the Rancher UI and there is a problem, there is a non-descriptive error displayed on the screen. See below screenshot:

However, if I look through the Rancher pod logs, I can see the problem:
2023/05/16 22:26:24 [ERROR] [aks-handler] error getting locations: failed to get locations: subscription.SubscriptionsClient#ListLocations: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationFailed" Message="The client '64561ad2-be48-42f1-92a6-0905a31c9977' with object id '64561ad2-be48-42f1-92a6-0905a31c9977' does not have authorization to perform action 'Microsoft.Resources/subscriptions/locations/read' over scope '/subscriptions/1f3b4b77-ea93-4e49-8936-a8ce0d4aabc3' or the scope is invalid. If access was recently granted, please refresh your credentials."
To Reproduce

Add cloud-credential for AKS in Rancher (one that does not have proper authorization as described in the error from the Rancher logs shown in the above description)
Try to provision a downstream AKS cluster in the Rancher UI using the cloud-credential defined in step 1

Result
Unable to proceed to the next step of provisioning and a non-descriptive error is shown in the UI.
Expected Result
Display the actual error that is preventing provisioning (the error that can be seen in the Rancher pod logs)
Screenshots
Added
Additional context

closing as a dupe of https://github.com/rancher/dashboard/issues/7913


User interface for downloading images

Using simple TK , with not advanced desgin.
wtih two prameter
I did not work hard on the UI -
its just a prototype to work on it .

@a0m0rajab thanks for this awesome feature. 😃
I actually did not want to add any external dependencies to this project. But since this is an additional feature and user who choose to use UI can install TK, i think having such a dependency would be fine.
Although this is a good start, could you consider adding all the parameters that we currently have in the command line interface into the UI? That way people can use one or the other and they both would be consistent in what they offer.
Do let me know...

@a0m0rajab closing this PR now. As mentioned above, I really liked the idea for a UI. If you would want to take this up and make UI that caters to all the parameters, then that would be great. Just wanted to have the consistency between CLI and the UI.
Thanks!

For me the UI was just a start for release version of the code for the non-coder people who wants to download from google too.


Project cannot clones by composer

After php composer.phar require --prefer-dist gromver/yii2-platform-core "*" I get
The requested package gromver/yii2-platform-core could not be found in any version, there may be a typo in the package name. error. How should I fix it?

Hello. gromver/yii2-platform-core runs on top of the yiisoft/yii2-app-basic. You must first install the yiisoft/yii2-app-basic application.

Sure. I first installed yii2-app-basic but it cannot installs.

You need to change your composer.json
"minimum-stability": "stable", => "minimum-stability": "dev",

It works, thanks!

I found a bug while testing installation. Now it fixed and command:
php yii core-migrate  works fine.
You should update application (composer update), drop tables and restart php yii core-migrate command.


LDAP authentication server does not support Sub CA

Today, configuring an LDAP server with either TLS or StartTLS will only work when the Root CA can be set directly. It will not work when dealing with an issuing / sub CA as the Auth/LDAP.php script currently only writes the sub CA into the file in /var/run/certs.
A workaround today is to create a single entry in System > Trust > Authorities and put both the Root CA and Sub CA certificates into the Certificate data field. Choosing this particular entry in LDAP server configuration will allow to connect to the server. (Hint: It might be required to reboot your device as the trust store somehow seems to get confused when playing with such configuration too much. Rebooting will give you a clean state before actually testing the LDAP server configuration).
I am not sure about the side effects to the trust store to be honest. One is for example a cosmetic one where it will not show the correct issuer:

If the Auth/LDAP.php script could include all certificates of this particular trust chain, that would be preferred. Maybe this can be considered in one of the next

If you have a 19.7.4 can you try to hardcode LDAP to /etc/ssl/cert.pem ? it should have all the CAs and the default ones now.

Indeed, changing
https://github.com/opnsense/core/blob/7218726f59c39cf6a76b0b2d09aa247d19f066c0/src/opnsense/mvc/app/library/OPNsense/Auth/LDAP.php#L341
to /etc/ssl/cert.pem will make that happen.
That would make quite a lot of stuff obsolete in the code I guess. Also, it would no longer be needed to choose the Peer Certificate Authority in the frontend. Instead, a simple reminder about adding private CAs to the trust store would be sufficient.

@jpawlowski Sounds like a good idea to me, can you confirm that your issue is solved when LDAP_OPT_X_TLS_CACERTFILE points to /etc/ssl/cert.pem ? I'll gladly remove some code here.

I can confirm this, it is working on 4 devices now.

ok, thanks, I'll prepare a patch later.

@jpawlowski can you try https://github.com/opnsense/core/commit/b2affd161dbc3c6e77b335767671162cf97cb964 ?
I've dropped LDAP_OPT_X_TLS_CACERTDIR as well, since it doesn't seem to be required when pointing to a cacert file.

Just applied the patch to one of the machines, deleted the chain certificate from the trust store, and saved the LDAP server configuration (just to ensure the new XML config file structure).
Afterwards, I was still able to connect to the LDAP server as intended so the patch seems to work fine. Many thanks, Ad!

@jpawlowski thanks for confirming, can I close the issue? It will move into a production version later.

will just close it myself, thanks for politely asking ;)

@AdSchellevis just to let you know that there are coming up some warning messages in the reporter:
[04-Oct-2019 21:49:18 Europe/Berlin] PHP Warning:  implode(): Invalid arguments passed in /usr/local/www/system_authservers.php on line 245

Everything is working fine, though.

@jpawlowski not related, but https://github.com/opnsense/core/commit/09c34b272f122bffc4150431b964d850c7166b36 should fix it.

Too bad this didn’t make it into the new minor release (while other LDAP fixes did)

Too bad this didn’t make it into the new minor release (while other LDAP fixes did) @fichtner

Too many changes here... we just pushed it 1 release back to give others the opportunity to test with the package mirror shipped opnsense-devel which is our default policy for backports. Exceptions apply, but it’s good to not forget rules completely. 😊

This was not about the package, it was about the patches to Auth/LDAP and stuff in https://github.com/opnsense/core/commit/b2affd161dbc3c6e77b335767671162cf97cb964


GitHub: Changing repo while creating issue clears all fields

Description
Create Issue and Create Pull Request now remembers the title when switching repository.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@bangerang You need to add an entry to CHANGELOG.md.

@bangerang I believe you have to put your Raycast username into the package.json file and not your GitHub Username.

I merged something in between @bangerang, so there's a small conflict in the CHANGELOG.md 😬

Should be resolved now @thomaslombart


redpanda: 23.1.10 -> 23.1.11; fix build

Description of changes
Update of redpanda to fix the build
The current failure is on seastar compilation.
@yu-re-ka , I'm not very far with this but I thought you might be interested.
@avakhrenev hey thanks a lot for the original PR to build redpanda from source.
I have a compilation failure with seastar and I'm not sure where to get the version number as well. (just in case you have time).
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Hi,
All the versions of external dependencies is specified in cmake/oss.cmake.in.
The last time when the build was broken, I've tried to fix it, but was stuck with a linking error I don't understand. I have "Fix build" item in my ToDo list since then =)
Will try to find time to fix the build this weekend.

@avakhrenev I forgot to say yesterday, but even if you have a PR that is not building completely, feel free to open a draft PR with the issue you are encountering, someone else might be able to help regarding the issue.


Rollback recent changes but accounts for several workarounds that were in place

Changes:

This reverts the changes in #41 as they weren't the appropriate fix and caused more workarounds to have to be put in place.
Reverting #41 and the change for the base __str__ method on a Record object to self.display that fixes the nat_inside/nat_outside not having the correct attributes available is within #42.
This should fix #53 due to reverting the changes and allowing tags to be created as Record objects as prior to #41.

I believe these changes should properly resolve all related bugs.

@thatfatguypat Do you mind testing this PR and make sure it resolves your issue?

@FragmentedPacket just gave this a test with my org's automation and it is working the same as prior to #41.  Thanks for putting this together!


Request for Documentation: Document that Jira mentions need to be turned on by the authenticated  user

Mattermost user aaron.rothschild from https://community.mattermost.com has requested the following be documented:
https://jsoftconnector.atlassian.net/wiki/spaces/JS/pages/765001735/Mattermost+-+Direct+message

End users:  Get notified personally by the Jira bot whenever you are mentioned or an issue that is assigned to you is updated: You need to type `/jira notifications....`

See the original post here.
This issue was generated from Mattermost using the Doc Up plugin.

@aaronrothschild Should this issue be here or in the jira repo?

@hanzei It's going to go into the Jira repo, I made an issue for docup that would address this.... basically add an option to let the user select/type a repo when using docup. But in the meantime, I'll close this out and add to Jira Readme.

@aaronrothschild We can just transfer the issue, if you want


update graylog tarball and hash location

I cloned the 3.0 branch and was having issues building the Docker image. It seems the location of the graylog release and sha256 hash has changed.
Relevant community post
Changing the URL allowed me to properly build the image

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

thank you for this submission. However that change is not needed as https://packages.graylog2.org/ is the correct and working URL.
I verified that over several weeks, providers and servers now and do not see a reason to change this.


bootstrap: "mtimestore -A" to store file's MIN(mtime, author-date).

For bootstrapping, each file's original-mtime was lost (of commits before this extension was in place). Yet we have two pieces of knowledge constraining it:
original-mtime <= current-mtime
original-mtime <= commit-time

True, but I do not like the idea of constraining them because:

'save all' is meant to save the current repository state as it is and leave full responsibility up to the user. I believe that this is the conceptually correct behaviour in situations in which the motivation of use is not clearly given. Adding it would force an assumption on other people's workflow.

I do not see any reason why we should try to 'guess' something which is not correct anyway. Since the user most likely needs exact and correct times , I think we can assume he has a way of obtaining them (e.g., another non-git repository or working tree). I think we can assume that since using commit times (as discussed in the original discussion on http://stackoverflow.com/questions/1964470/whats-the-equivalent-of-use-commit-times-for-git) solves the problem much more elegantly.

Commit times and modification times seem to me as a pretty unrelated functionality. I do not see a reason why someone interested in modification times should want commit times.

I don't know of a fast way of computing commit times. There had been serious performance issues with the bash driven version under cygwin. Since the c++ version aims to be usable even on windows, this means a problem.

If there are good reasons for this, anyone is welcome to fork and tailor for his needs.

Very well, valid points. I'll respond anyway. And thanks for your git extension.
Clear to me there are both camps, folks that: settle for author-date (or commit-time) as a poor alternative, despite wanting mtime; versus those that want exactly commit-time.
"constrain", "force": My poor initial conception of the request. Agreed, keep user choice AND zero impact to existing usage model:
mtimestore -A (new option, to keep -a as-is; and use author-date not commit-time) would provide this new feature. User can CHOOSE to exploit it (therefore also choosing to pay the one-time extra run-time) or not. Recall Linus's mtime-feature objection was all about his single (make) usage model, not willing to give the user a usage model choice.
Agreed possibly other  author-date (or commit-time) solutions can be exploited (prior to user's one-time: mtimestore -a). But it presupposes a good one exists that does so conditionally; my initial review says they don't yet. i.e. Don't touch a file with mtime already older than the author-date. Agreed one of those can be tweaked to do it conditionally; but someone will be first with an integrated solution, and this "best of both work-arounds" would set a new standard... ;)

I am terribly sorry for so late response (I had totally forgotten this email).
My conclusion is that adding the author-date of the last change won't do much harm (is it the use case you are aiming for?). Still, I am afraid I have no idea how to compute this efficiently, so only the bash version will get this functionality atm.


Changes to set default driver for running properites computation

Description
The purpose of the PR is to be able to set a Dataset's default driver to something other than the default "energy".  I was hoping to compute dipole moments with nwchem on my Dataset.  In order to do so, I need to use the "properties" driver.  These changes allow me to do that.  It also allows get_values to return energy values when the driver is "properties".  As a note, I wasn't able to set the default driver using ds.data.default_driver="properties" because the Datamodel class is immutable.
Changelog description
Creates set_default_driver() function to be able to set the default driver on Dataset collections.
Status

[ ] Code base linted
[ ] Ready to go

Datasets have radically changed in v0.50, and most defaults are no longer settable in a singlepoint dataset. I would be happy to talk and go over the new interface if you would like!


Unable to start Safari WebDriver

ERROR - Unable to start a WebDriver session.
/opt/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:113
var template = new Error(this.message);
^
UnknownError: Failed to connect to SafariDriver after 10059 ms
Build info: version: '2.45.0', revision: '5017cb8', time: '2015-02-26 23:59:50'

Sorry if this is obvious, but do you have the latest SafariDriver extension installed? See here.
Not that I will be able to help you troubleshoot beyond what I've already offered, but it may be helpful to include other details like what OS you're using, what version of node, what version of Safari, etc.

yes I have the latest SafariDrivers installed, 2.45

What is the status here?

I can't debug your problem with the information you've provided.  Also, we don't answer questions here, we do that on stack overflow.


Implement unit conversion

This PR implements unit conversion by leveraging the Units.Net library.

@brandonpollett,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


ExecuteStoredProcedureAsync not accepting arguments

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
Arguments passed to the stored proc are always undefined
To Reproduce
var response = await container.Scripts.ExecuteStoredProcedureAsync<object>(
                    storedProcedureId: storedProcId,
                    partitionKey: new PartitionKey(partitionKeyValue),
                    parameters: args.ToArray(),
                    requestOptions: new StoredProcedureRequestOptions()
                    {
                        EnableScriptLogging = true
                    });

args = new List {  currentCount - item.Count, type };
Expected behavior
Expected console.log statements in stored proc to output values instead of undefined
Actual behavior
console.log statements in stored proc output "undefined"
Environment summary
SDK Version: 3.21.0
OS Version (e.g. Windows, Linux, MacOSX) - Windows
Additional context
Add any other context about the problem here (for example, complete stack traces or logs).
Stored Proc:
function deleteNItemsInCreatedState(num, type, additionalArgs) {
    if (!num) {
        throw new Error("Argument num cannot be null or undefined");
    }

    if (!type) {
        throw new Error("Argument type cannot be null or undefined");
    }

    console.log("Trace log");
    console.log(num);
    console.log(type);
    console.log(additionalArgs);
}

@issacnitin Could you please share a more complete example that reproduces the problem?

Issue was because of custom json serializer.


MarkDown Comments appear as texts in the site

In the following page https://beta.reactjs.org/community seems like the content broke.

How?
Seems like the heading id inside of the comment causes this.
https://github.com/reactjs/reactjs.org/blob/0057efa12c1aa2271ef80d7a84d622732bdfa85c/beta/src/pages/community/index.md?plain=1#L23
Tried removing the heading id and seems like it fixed the issue. I also tried commenting that line separately as well (It also breaks).
Shall I remove the ID {/*popular-discussion-forums*/} for now?
But if I do so we might actually run the generate-ids in the pre commit and that will add the Id again.
Or shall I change it as normal text so that we don't generate ID for it?
cc: @wooorm

maybe it works if you for now turn ## Popular Discussion Forums {/*popular-discussion-forums*/} -> Popular Discussion Forums as a quick workaround?

Yep will change it into normal text instead of heading for now. Thanks.


Estimated MMR should only use ranked games and not unranked

Now it works really bad cause it use both, ranked and unranked games to estimate the MMR of players, it should only use ranked games, now it works pretty fine with players than only play ranked, but those who plays both (and even unranked with low mmr friends) its really wrong, like it shows 6k in solo mmr and 3k in estimated mmr.

note @blukai you'll have to make a code change to odota/core for this.
Sounds reasonable to me, although it will mean estimation doesn't work on players who never play ranked.

I am not a programmer, but maybe can make an exception, like only use unranked games if the player never play ranked and it appears in other colour (yellow?) or with a "*" or something and a tooltip that say "estimated mmr is using unranked games, needed ranked games to be more accurate" or something. Thank you for the response.

I am also not a programmer, but looking at this logically - I had always figured "Estimated MMR" was as close to a "Hidden" MMR as you will ever get.
I like it this way - and would ever prefer to see "Estimated MMR" use only UNranked matches to find its value. Does that make sense?

It doesnt work that way, cause the "Estimated MMR" use the MMR (solo ranked) of the people who played with or against you and they show it in their profile, so you are not getting your "Hidden" MMR, you are getting the real mmr of the players you play with, example, if you play with 4 friends (unranked), and they are like 2k and you are 6k, you are gonna get a "Estimated MMR" of 2.8k, what totally false, thats not your "Hidden MMR" (cause you are playing party with low level friends), and its not even close to your real mmr (6k vs 2.8k), maybe and only maybe if it only use your 5 solo vs 5 solo unranked games (no parties in any side) it will be a more accurate "Hidden MMR" but this way its not even close.

It sounds like what this issue is asking for is a measure of uncertainty in the MMR estimate.  That's probably doable, by assigning scores for each type, like:

ranked solo: 1
ranked party: 0.75
unranked solo: 0.5
unranked party: 0.22

then average out the scores for the matches used in the estimate and pass that value down.

likely MMR estimation will be removed.  Can revisit if "medal estimation" becomes a thing.


Added parsing for PAM SLA metrics

Other than those two changes LGTM

Is this still valid anymore?

Closing this PR as it's so old. It's from a story we began but then abandoned, and it's unlikely we will take this approach going forward.


openapi: Add missing init.py; fix type errors hidden by its absence

The absence of __init__.py was preventing mypy from following any of the zerver.openapi imports.  These errors were being silenced by ignore_missing_imports.

Merged, thanks @andersk!


OAuth out-of-band (oob) is deprecated and does not work anymore

Describe the bug
According to Google Developer's blog, OAuth out-of-band (oob) is getting deprecated:

Feb 28, 2022 - new OAuth usage will be blocked for the OOB flow

To Reproduce
Steps to reproduce the behavior:

Download credentials.json from Google Console
Configure credentials on this extension
After selecting the scope, instead of showing a token to copy / paste on the application, an error screen is shown

Expected behavior
The auth should complete.
Screenshots

Please complete the following information:

OS: Ubuntu 20.04
VSCode Version: 1.65.2
Extension version 1.3.2

Congrats @GustavoASC! Very good!! :D

Thank you @gustavosimon! Glad you liked it :smile:


ESP32-HUB75 Graphic design /Effect

How to insert any graphic effects such transactions effect or any type of scrolling effect

This library is not a graphic effects library. Please raise a request with the AdafruitGFX library.


New metric to measure time to establish connections.

Could we have a metric that measures time to establish physical DB connections, this will help us to take a view on the cost of establishing/recycling connections, which will influence decisions as to how we configure the rest of the pool.

I think we can probably consider this a dupe of #518. If we add a historgram type metric it would cover both the count and how long it is taking

Fixed by 1807776.


Could not load text adapter configs from dir 'config/data_sources/nlp'

Executing docker compose up in top-deployment results in the following backend warning:
backend-1   | 2024-02-14 10:47:15.940  WARN 1 --- [nio-8080-exec-4] c.s.t.b.s.nlp.DocumentQueryService       : Could not load text adapter configs from dir 'config/data_sources/nlp'

Is this locally on your machine? This is an example of a text adapter config source:
id: Lucene Data Source
adapter: care.smith.top.top_document_query.adapter.lucene.LuceneAdapter
connection:
  url: http://localhost
  port: 9201
index:
  - test_documents
field:
  - text
batchSize: 30
replaceFields: {'text': 'content'}
graphDB:
  connection:
    url: bolt://localhost
    port: 7687
conceptGraph:
  connection:
    url: http://localhost
    port: 5000

Supposing, you don't have the services running locally, you could forward the ports from top-prod.

elasticSearch (the main connection) runs on 9008
graphDB runs on 7687
conceptGraph runs on 9007

We need to postpone this issue until @ChristophB finishes the restructuring of the backend and how we handle the whole document/concept situation. If Elasticsearch is loaded/connected to within the backend, this warning is hard/not to circumvent as spring will expect an Elasticsearch server. If we handle the whole concept/document situation as an integral part, however, we could load up the Elasticsearch server with an docker compose entry accordingly.

The changes I have implemented so far do not affect this warning. How about we reduce the log level of this message to debug?


Updated connect procedure

Updated API to use rtm.connect instead of rtm.start

https://api.slack.com/changelog/2021-10-rtm-start-to-stop

@jimmycuadra I believe there is something wrong with your CI configuration.


Quick actions crash when app not in background

The quick_actions plugin crashes when the action is tapped after clearing the app from the background (i.e. after killing it).
How to reproduce:
Clone the quick_actions demo, run the main app, then kill it, and tap the "Main view" quick action.
Because the crash needs the app to be killed to reproduce, I have no idea how to obtain a stack trace.
Package version
quick_actions 0.3.0+1
flutter doctor -v
[✓] Flutter (Channel beta, v1.4.9-hotfix.1, on Mac OS X 10.14.4 18E226, locale en-US)
    • Flutter version 1.4.9-hotfix.1 at /Users/joachim/flutter
    • Framework revision 88fa7ea403 (6 days ago), 2019-04-11 14:01:46 -0700
    • Engine revision 4737fc5cd8
    • Dart version 2.2.1 (build 2.2.1-dev.4.0 None)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/joachim/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 2.0.0
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 34.0.2
    • Dart plugin version 183.5901
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] Connected device (1 available)
    • Pixel 3 • 89KX0AW01 • android-arm64 • Android 9 (API 28)

• No issues found!

As per https://github.com/flutter/flutter/issues/13634
Try adding the following to AppDelegate.m:
`- (void)application:(UIApplication )application performActionForShortcutItem:(UIApplicationShortcutItem )shortcutItem completionHandler:(void (^)(BOOL succeeded))completionHandler {
FlutterViewController controller = (FlutterViewController)self.window.rootViewController;
FlutterMethodChannel* channel = [FlutterMethodChannel<EMAIL_ADDRESS>binaryMessenger:controller];
[channel invokeMethod:@"launch" arguments:shortcutItem.type];

}`

I think this issue is related to Android, but I can also confirm that the workaround is working for me (on iOS).

Thank you for your comments!
Indeed the bug appears on Android so this iOS fix won't be enough :(
I managed to isolate the error with adb logcat:
05-12 20:02:09.054  1263  3391 I ActivityManager: START u0 {act=plugins.flutter.io/quick_action flg=0x10000000 cmp=com.dontaskwhy.remind/io.flutter.plugins.quickactions.QuickActionsPlugin$ShortcutHandlerActivity bnds=[440,1280][641,1578] (has extras)} from uid 10324
05-12 20:02:09.061   844   844 D<EMAIL_ADDRESS>LAUNCH ON
05-12 20:02:09.070 25778 25778 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@ca48e34
05-12 20:02:09.076 25778 25778 V FA      : onActivityCreated
05-12 20:02:09.101   636  2392 W SurfaceFlinger: Attempting to destroy on removed layer: AppWindowToken{f006e84 token=Token{27a6c97 ActivityRecord{3921b16 u0 com.dontaskwhy.remind/io.flutter.plugins.quickactions.QuickActionsPlugin$ShortcutHandlerActivity t11328}}}#0
05-12 20:02:09.104   636  2392 E BufferQueueProducer: [Splash Screen com.dontaskwhy.remind#0] queueBuffer: BufferQueue has been abandoned
05-12 20:02:09.104  1263  1659 E Surface : queueBuffer: error queuing buffer to SurfaceTexture, -19
05-12 20:02:09.104  1263  1659 E Surface : queueBuffer (handle=0x719329dab0) failed (No such device)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: Could not unlock surface
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: java.lang.IllegalArgumentException
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.Surface.nativeUnlockCanvasAndPost(Native Method)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.Surface.unlockSwCanvasAndPost(Surface.java:382)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.Surface.unlockCanvasAndPost(Surface.java:363)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:3458)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.ViewRootImpl.draw(ViewRootImpl.java:3346)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:3122)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2481)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1463)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7190)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:949)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.Choreographer.doCallbacks(Choreographer.java:761)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.Choreographer.doFrame(Choreographer.java:696)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:935)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.os.Handler.handleCallback(Handler.java:873)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.os.Handler.dispatchMessage(Handler.java:99)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.os.Looper.loop(Looper.java:193)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at android.os.HandlerThread.run(HandlerThread.java:65)
05-12 20:02:09.104  1263  1659 E ViewRootImpl[remind]: 	at com.android.server.ServiceThread.run(ServiceThread.java:44)

By comparison here's the output when it works (i.e. when the app is running in the background):
05-12 20:16:58.619  1263  2002 I ActivityManager: START u0 {act=plugins.flutter.io/quick_action flg=0x10000000 cmp=com.dontaskwhy.remind/io.flutter.plugins.quickactions.QuickActionsPlugin$ShortcutHandlerActivity bnds=[440,1280][641,1578] (has extras)} from uid 10324
05-12 20:16:58.620   844   844 D<EMAIL_ADDRESS>LAUNCH ON
05-12 20:16:58.624   844   844 D<EMAIL_ADDRESS>LAUNCH ON
05-12 20:16:58.632 25778 25778 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@b30a86b
05-12 20:16:58.644 25778 25778 V FA      : onActivityCreated
05-12 20:16:58.661   636   636 W surfaceflinger: type=1400 audit(0.0:244229): avc: denied { read } for name="u:object_r:vendor_display_prop:s0" dev="tmpfs" ino=24386 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:vendor_display_prop:s0 tclass=file permissive=0
05-12 20:16:58.665   636   636 E libc    : Access denied finding property "vendor.debug.egl.swapinterval"
05-12 20:16:58.676 25778 27866 V FA      : Activity resumed, time:<PHONE_NUMBER>
05-12 20:16:58.678   636   636 W surfaceflinger: type=1400 audit(0.0:244230): avc: denied { read } for name="u:object_r:vendor_display_prop:s0" dev="tmpfs" ino=24386 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:vendor_display_prop:s0 tclass=file permissive=0
05-12 20:16:58.680   636   636 E libc    : Access denied finding property "vendor.debug.egl.swapinterval"
05-12 20:16:58.695   636   636 W surfaceflinger: type=1400 audit(0.0:244231): avc: denied { read } for name="u:object_r:vendor_display_prop:s0" dev="tmpfs" ino=24386 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:vendor_display_prop:s0 tclass=file permissive=0
05-12 20:16:58.697   636   636 E libc    : Access denied finding property "vendor.debug.egl.swapinterval"
05-12 20:16:58.703   844   844 D<EMAIL_ADDRESS>LAUNCH OFF
05-12 20:16:58.876   636  2392 W SurfaceFlinger: Attempting to set client state on removed layer: SnapshotStartingWindow for taskId=11329#0
05-12 20:16:58.876   636  2392 W SurfaceFlinger: Attempting to destroy on removed layer: SnapshotStartingWindow for taskId=11329#0
05-12 20:16:58.958 20212 20212 I KeyboardViewUtil: systemKeyboardHeightRatio:1.200000; userKeyboardHeightRatio:1.000000.
[...]

So it would appear the crash is due to an exception in unlockCanvasAndPost. I tried googling it and found this SO question which sounded similar. Then I tried using their fix, which is to set android:exported=true instead of false in the quick_actions manifest file. But that didn't solve the problem; still seeing the same IllegalArgumentException.
Does anyone know what could cause that?

Hello, i have the same problem in Android.
In iOS I fixed it by adding a piece of code in the AppDelegate file, but in Android I couldn't fix it.
Anyone has the solution?

The problem for Android is located here, in QuickActionsPlugin.java.
When you click on the quick actions item, the plugin opens ShortcutHandlerActivity, and it is a simple one:

    @Override
    protected void onCreate(Bundle savedInstanceState) {
      super.onCreate(savedInstanceState);
      // Get the Intent that started this activity and extract the string
      Intent intent = getIntent();
      String type = intent.getStringExtra("type");
      if (channel != null) {
        channel.invokeMethod("launch", type);
      }
      finish();
    }
  }

So, as you can see, it just opens this activity, sends a message to the channel, and finishes the activity. If this approach is fine if the app is already launched, — you will just see the activity behind ShortcutHandlerActivity, — it doesn't work in the background. Just because after closing the helper ShortcutHandlerActivity you don't have any open activities left. One thing which could help is to open the main launcher activity if it is not open yet.

And one more thing to notice is in quick_actions.dart. As you can see, the call channel.invokeMethod is executed onCreate() of the very first activity, and method handler in quick_actions.dart is set only on initialize(), so, in this case with the background execution, handler is not set at the time when invokeMethod is executed. You have to save the intention to call the quick action somewhere and check later, for example, in shared preferences.

I created POC here, please, check if it works for you and comment.

Thanks a lot for looking into this! That sounds very promising. I am offline until next week but then I can confirm that your fix works and will comment on your PR.

FYI The PR was merged

Wonderful! And I confirmed it fixed the issue. Thanks a lot!


Unable to run tensorboard

Hi all,
I'm trying to use tensorboard but I can't find the tensorboard executable in my path. I installed tensorflow with pip.
When trying to run it from source I got the following error
WARNING:root:IOError [Errno 2] No such file or directory: '/../tensorflow/external/paper-toggle-button/paper-toggle-button.html' on path /.../tensorflow/external/paper-toggle-button/paper-toggle-button.html

I forgot to run --recurse-submodules.


Videos not being saved to NFS share

Hi, I'm probably doing something wrong but please bare with me. I can see files being saved on the NFS share folder. I'm using a windows 10 NFS share by using this command:
winnfsd.exe -id 0 0 -log on -addr <IP_ADDRESS> D:\Camera\Wyze /camera

The camera is Wyze V2 running <IP_ADDRESS> and depending on my luck sometimes I can see SD card memory available as 0MB/ 0MB and sometimes it doesn't detect an sd card. I tried multiple reboots and multiple remote_install (version 0.5.03).
I can see a config.inc file on the windows machine with this information:
# USER CONFIGURATIONS -- TO BE MODIFIED BY USER
# Make your own copy of this file and put it under the root of SD card
# with name "config.inc" when installing the hack.

# You need to modify NFS_ROOT to point to your NFS share. The recordings
# will be stored under $NFS_ROOT/WyzeCams/<MAC_ADDR_OF_YOUR_CAMERA>.
export NFS_ROOT='<IP_ADDRESS>:/camera'

# Some NFS configurations may need special mount options. You can specify
# them here. The default value is verified on my camera with a NFS v3 share
# on my home server.
# export NFS_OPTIONS='-o nolock,rw,noatime,nodiratime'

# Timeout threshold for NFS connectivity check. If the NFS share is not
# available for more than '$NFS_TIMEOUT' seconds, a reboot will be initiated
# trying to resolve the network connectivity. The default value is 15 seconds.
# export NFS_TIMEOUT=15

# Uncomment and modify the AUTO_REBOOT variable to automatically reboot
# the camera at a specific minute. Time is specified in "HH:MM" format
# in local time.
export REBOOT_AT='02:15'

# Uncomment and modify the ARCHIVE_OLDER_THAN variable to automatically
# archive recording clips and alarm images if it's a certain days older.
export ARCHIVE_OLDER_THAN=5

# Uncomment the following variable to sync the console log to the camera
# folder in NFS share. Use with caution as the log contains sensitive
# information and will cause your account compromise if leaked.
# export SYNC_BOOT_LOG=1

# In my setup I noticed at some occasions the camera starts rebooting frequently
# which seems to be a result of dropping wifi connections. Running a "ping"
# command in background seems to be solving this issue. Uncomment this variable
# to enable this fix.
export PING_KEEPALIVE=1

# Uncomment to enable voice notification when NFS network connection lost. The
# value should be in range of 0 and 100
# export NOTIFICATION_VOLUME=80

# Uncomment and update this value to customize the hostname of the camera. By
# default it will be set to <WyzeCam>-<last 4 hex digits of the mac>.
export HOSTNAME='<Garage>'

# Uncomment this to enable automatically updating config.inc file based on file
# <camera_folder>/wyzehacks/config.new. This will be checked every one minute.
export AUTO_CONFIG=1

# Uncomment this to enable automatically updating wyzehacks. To update, you need
# to extract the latest wyzehacks release archive to $UPDATE_DIR and name it as
# "release_?_?_??". The updating script will search for latest version based on
# the folder name every one minute.
export AUTO_UPDATE=1

# By default, variable "UPDATE_DIR" is set to "/mnt/WyzeCams/wyzehacks", which
# is <NFS_ROOT>/WyzeCams/wyzehacks. If auto update is enabled, it will search
# for updates in this directory. The default value allows all cameras share the
# same update. You can customize this directory for a specific camera if you
# want it to use different update (for example, testing dev builds). Some thing
# under "/media/mmc" would be a good candidate because it maps to the camera
# folder.
# export UPDATE_DIR='/media/mmc/wyzehacks'

# Uncomment and update this to run a custom script after the NFS mount finishes.
# The script must already exists and executable. You can always use "/media/mmc"
# to refer the camera folder on the NFS share. Or use "/mnt" to refer the root
# of NFS share. The value of the variable can only contain script file name, no
# command line arguments. The script will be executed in background.
# export CUSTOM_SCRIPT='/media/mmc/scripts/myscript.sh'
# export CUSTOM_SCRIPT='/mnt/WyzeCams/scripts/myscript.sh'

# !!!ADVANCED USER!!!
# This changes the default root password to whatever you specified. To
# generate your own password hash, use the following command from a
# linux environment:
#   openssl passwd -1 -salt <YOUR SALT> <YOUR PASSWORD>
# Use the result to replace sample hash ($1$MYSALT$3Sy1OLRk4kTa7P6fvzwp71)
# export PASSWD_SHADOW='root:$1$MYSALT$3Sy1OLRk4kTa7P6fvzwp71:10933:0:99999:7:::'

In the log folder I see several reboot_XX files but all have 0 kb.
Could you please tell me what I did wrong?

i don't see any problem in your config file, and it seems the camera is correctly mounting the NFS share and storing logs already. Those reboot_XX files are expected to show you when the camera has rebooted. The latest wyze hack is very sensitive to the running firmware version so beta firmwares are not well supported. I'd suggest you reflash your camera firwmare using SD card recovery method and then try it again.

@rfg81 can you sd recover the firmware to latest version (241) and try hack version 0.5.04?

Ok, switched to running a different NFS and that seems to have corrected the constant reboots.
I followed this guide to setup a NFS: https://pimylifeup.com/raspberry-pi-nfs/
However, videos were still not being saved. Only jpgs in the "alarm" folder were being saved. The permissions for the "record" folder were different than the 'alarm' folder. I did a
cd /media/mmc
chmod 755 record
from the camera via telnet and now it saves the mp4s. I have a v2 running WyzeHacks 0.5.06

I confirmed that it is a permissions issue. The permissions are set as drw-r--r-- when the camera makes a new folder for the next hour.

My if I change the permissions via the raspberry pi GUI:

or issue the following commands via telnet to the camera:
cd /media/mmc chmod 777 record

the mp4s are saved as expected.
I thought of running a script on the pi to change the permissions of the newly created folders, but I think it would be a better fix to have the camera create the folder with the drwxrwxrwx permissions.

Might be something issue with the umask. Can you try if the follow command
fixes the issue?
Telnet into your camera
Run "echo 'umask 000' >> /configs/wyze_hack.cfg"
On Fri, May 14, 2021, 08:18 ZuluSpl0it @.***> wrote:

I confirmed that it is a permissions issue. The permissions are set as
drw-r--r-- when the camera makes a new folder for the next hour.
[image: image]
https://user-images.githubusercontent.com/55359362/118290835-7eca0a00-b49c-11eb-8332-edd5b01e4905.png
My if I change the permissions via the raspberry pi GUI:
[image: image]
https://user-images.githubusercontent.com/55359362/118291163-e41dfb00-b49c-11eb-8bb2-0ab6c679225b.png
or issue the following commands via telnet to the camera:
cd /media/mmc chmod 777 record
[image: image]
https://user-images.githubusercontent.com/55359362/118291806-9a81e000-b49d-11eb-9583-55aeaf25c062.png
the mp4s are saved as expected.
I thought of running a script on the pi to change the permissions of the
newly created folders, but I think it would be a better fix to have the
camera create the folder with the drwxrwxrwx permissions.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/HclX/WyzeHacks/issues/91#issuecomment-841309250, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZNWD4LQPXJLVTZSWBJ2WLTNU5NTANCNFSM4YKTMTNQ
.

The permissions are now:

Still not writing mp4s to the NFS until I chmod 777 on the folder

@ZuluSpl0it wait, your directory owner/group is not root but 1000?

My NFS options used are:
/mnt/nfsshare *(rw,all_squash,insecure,async,no_subtree_check,anonuid=1000,anongid=1000)
So the anonymous login from the camera should use pi's UID and GID (1000).

How are others running the NFS server?

I'm not. Like you, it never worked, either via windows NFS or a physical PI that I set up. Gave up...
Given the improved resources on the v3, I'd advocate for adding SMB to the v3 install.

I ran the NFS server on a real raspberry pi 3 (unlike the virtualized Raspberry Pi Desktop for PC above) and the camera records without any permissions issues. The folders and mp4 get created as expected. Does anyone know what causes the difference between the Raspberry Pi Desktop for PC and the armhf version for the real hardware?

I had this issue on a freenas system when I had set export permissions to mapall group and mapall user.  Once I removed those settings at the server, the issue went away.

How are others running the NFS server?

I'm not. Like you, it never worked, either via windows NFS or a physical PI that I set up. Gave up...

I have a post, that I made with info on getting the Hanewin NFS Server working on Windows:
#51


Add tooltips to sandbox playground configs

Is your feature request related to a problem? Please describe.
There is a lot and good documentation about all the properties that users can try in the live examples. It would be awesome to have that information directly available (as well) in the live example.
Describe the solution you'd like
Add information about each one of the properties in graph.config.js to the live sandbox. This information can be extracted from the jsdoc itself with some parse job.

Additional context
Step by step of the approach would be:

Parse jsdoc of graph.config.js into useful text that could be used within tooltips for these properties in the configuration form of the live examples.
Consume this information from some JS/JSON file and bind it to the JSON schema of the configuration form.

Closing with https://github.com/danielcaldas/react-d3-graph/pull/240


remove RangeEnabled entirely

Description
What's the point of having a boolean option on frames for whether or not they're allowed to have BSI fields?
I may be wrong, but as far as I can tell, it adds complexity to the API and codebase for no benefit - please discuss.
Success criteria (What criteria will consider this ticket closeable?)
If there are no clear drawbacks, remove the RangeEnabled option entirely from the codebase and API.

A frame may be created without range fields and they can be added later. If a frame doesn't have rangeEnabled=true it is not possible to add range fields later. As far as I know, that's the only reason that option is required.

Thanks @yuce. Just to be clear, what I'm proposing is allow any frame to have fields added at any time with no way of restricting which frames can or can't have fields.

As there seems to be no dissent, I'm going to start deprecating rangeEnabled. We can remove it after the 0.9 release.


Installation errors

I couldn't install it after two attempts.

Hi @fernandosn1977  sorry to hear you're having installation issues. Please try removing the version constraints in requirements.tx You could also try installing the packages listed in requirements.txt one by one manually. Let me know if that helps.


401 error on login

Ill get a VM24392:1 GET https://trader.degiro.nl/login/secure/config 401 error on login().
`const degiro = new DeGiro({
username: this.username,
pwd: this.pwd,
oneTimePassword: this.oneTimePassword,
});
try {
await degiro.login();
const jsessionId = degiro.getJSESSIONID();
console.log(jsessionId);
} catch (error) {
console.log(error);
}`

Hi @brambekkers,
Unfortunately this is not enough information for us to view this as a bug. The reason for this is that 401 is an "unauthorized" error, which you would get if your credentials are incorrect, and for others (me, in any case) the login function does work.
Can you verify the following:

Using e.g. console.log, verify that this.username, this.pwd and this.oneTimePassword are correct.
Ensure that you did not use this specific oneTimePassword before. Using the same OTP multiple times will cause a 401.
Print the result of await degiro.login().

I just got it working in NodeJS. I can't get it working on the cliend side. It seems to be blocked by Cors policy.

It's good that you mention it, I've ran into the same issue once too. Unfortunately CORS can't (and shouldn't) be circumvented, and as such the readme would be incorrect. Because of this this is not a front-end library...

Sorry guys, when I prepared the code to run in the web browser I was able to log into the platform.
It makes sense for CORS to block access. We just updated Readme.md file

Trying from a backend It works?

Thanks for the update, the backend works perfectly!

Awesome! So we can close this issue. Thank you all for being here adding value to this project!!


Refactor Tellstick sensors to be a sensor platform

Tellstick sensors have been around from before the sensor component was born. It is time to make it a platform of the sensor component.
i don't have my own Tellstick stick + sensor so I will need someone to test it. @Gyran, would you have time to test this?

Just tested it and it works here


Azure KeyVault (cloud based software/HSM signing service) signer support

This is the initial implementation that needs to be merged into the new subcommand based plugin framework. The main files are the two class files:
AzureKeyVaultAuthenticator.java
AzureKeyVaultTransactionSigner.java

and the integration test (as it requires Azure Key Vault credentials to run):
AzureKeyVaultAuthenticatorTest.java

please feel free to build on top of this PR to make it merge-able

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

👍 thanks for making this part of the new command framework and simplifying the key-resolving logic by utilizing the KeyIdentifier class. Looking forward to seeing this be part of EthSigner soon!


How to setup the c_cpp_properties.json to create a local database and look it up for symbol references.

VSCode Version: 1.8.1
OS Version: Mac OS X 10.12.2

My code lives on a NFS mounted partition (linux server). I am launching Microsoft Code on my Mac, and using NFS mount to access the files.
The file search and symbol reference is very slow currently. I want to create a local database, and use that database to do symbol reference and file search. Please let me know if it is possible, and if so, what exactly needs to be configured and where. I tried to search for c_cpp_properties.json documentation, but didn't find anything relevant.
Steps to Reproduce:
1.
2.

There is currently no cache for the file lookup/search, we will investigate adding one as part of #15382. Moving to the cpptools in case there is a cpp specific solution/answer to the symbol cache.

This issue was moved to Microsoft/vscode-cpptools#433

What about the symbol search if not the file search? Is there a cache for it? If so, what is required to create a local cache.

Is there a cscope plugin for Visual Studio code?


bugzilla: modify handling of ON_QA error message

This improves the comment made when a bug is not moved to VERIFIED due
to the bug not being in the correct ON_QA status, which should not
happen, but can occassionally occur if the ART bot does not change the
status of the bug in a timely manner after triggered a new nightly.
Resolves OCPCRT-111.
/cc @bradmwilliams

Since this has a conflict with changes in #345, I will put this PR on hold and rebase after #345 merges.
/hold

/hold cancel

/retest


Generte inline comments

In this PR we change the Language from generating single-line comments to generating multiline, or, more relevantly for us, inline comments.

@armiol, PTAL.
The Scan with Detekt check seems to be broken for a while now (as in "not configured properly"). Since I know that our colleagues are looking into Detekt right now, I decided not to touch it.


Backend: Add sqlalchemy database models

Required db module to be split off to avoid ciruclar dependency.

you're using declarative base, but the imperative style mapping as defined in the docs
https://docs.sqlalchemy.org/en/20/orm/mapping_styles.html#declarative-mapping
if it works, I guess that's fine, but if our project wants to stick to being totally idiomatic we might want to use declarative in it's entirety.

will review after tyler's requested changes are resolved


240 uniform title

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working Documents/2XX.csv

@SitaKB @cspayne @CECSpecialistI  I think 240 was mapped a long time ago and will need a complete overhaul and probably can copy many or all of the mappinngs from 130.  The only question is who has time to do it?  If I'm the only one, it probably won't be until later in the week after the holidays

@lake44me Hi Laura, I have looked at the mapping of 130. I don't see that it is reviewed. Do you mean to add row 2-11 of 130 to 240?

@SitaKB you are right, 130 is not reviewed...  I assumed it was composed in concert with the latest Heading Fields Attribute Mapping.   https://docs.google.com/spreadsheets/d/1k-ZevqjVntyqyGZ89IGma5j71ySLYZabGrn4Ls5GM3E/edit?gid=1796318524#gid=1796318524  .   That document does not mention mapping of 240,  but it does include 130 in the mapping of some  subfields.
130 mapping was last edited Nov. 17 by @pennylenger I think (pengyan sun?)  .  I have a full day, can take a look later at whether it agrees with the Heading Fields spreadsheet.
I think 130 and 240 should be closely aligned in the mappings since they are both uniform title fields, but connecting 240 to the 1xx may be another factor.
@tmqdeborah @CECSpecialistI @cspayne  How can we facilitate the review/completion of 130 and 240 - are we at the point where the Heading Fields Attribute Table is complete and approved?

@lake44me I would base your 240 mapping on the 130 mappings in the attributes mapping spreadsheet, not straight out of the 130 spreadsheet. I am working on going through and editing these spreadsheets to point to the attributes mapping spreadsheet instead of having separate mappings on each one so that any changes we make are all in one spot!


Enable collection rendering

Closes #129.
To explain, I'll use the Membership model.
Vanilla Rails collection rendering
When rendering views from a collection (<%= render @memberships %>), there are three things that Rails does:

Looks for the partial memberships/membership to render.
Takes that partial and renders it per each object (i.e. renders the same partial 3 times if the collection's size is 3).
Gives each iteration of the partial a local called membership.

When using the vanilla Rails scaffolder, it automatically creates this file for us. For example, if we scaffold a model called Foo this file will also be generated: app/views/foos/_foo.html.erb. However, this file doesn't exist for any of our models in Bullet Train.
Bullet Train index page
When scaffolding a model with vanilla Rails, it will generate an index page, but it doesn't generate an _index.html.erb partial like we have in Bullet Train. Instead, we get the memberships/membership partial, or foos/foo partial like I mentioned above which is called from within the index page.
Not only that, but collection rendering renders the same partial for the amount of objects in the collection. This made things a little tricky with the current index page that we have, but after some trial and error I finally came to a solution.
Falling back on original Rails logic
I think there are different ways to approach this, but I thought it would be best to fall back on standard Rails logic. That way, if our developers are already familiar with collection rendering, then it would be natural for them to see the following and change it accordingly.
From app/views/account/memberships/index.html.erb:
Rendering with a String
<% if @memberships.current_and_invited.any? %>
  <%= render 'index' do %>
    <% @memberships.each do |membership| %>
      <%= render 'membership', membership: membership %>
    <% end %>
  <% end %>
<% end %>

Then we'd change it to this with collection rendering
Rendering with a collection
<% if @memberships.current_and_invited.any? %>
  <%= render 'index' do %>
    <%= render @memberships %>
  <% end %>
<% end %>

You can use one or the other in the code from this pull request to see how Memberships are rendered.

If we're okay with this setup, then I'll have to do the following as well:

Enable collection rendering for the remaining standard Bullet Train models (Team, TangibleThing, etc...).
Edit Super Scaffolding so it generates the foos/_foo.html.erb partial.
Edit Super Scaffolding so newly scaffolded index pages/partials render foos/_foo.html.erb.

Since the other views for standard Bullet Train models are in bullet_train-super_scaffolding, I'll mark this one as ready for review and start working on the last two points I mentioned in the last comment.


chore/app/pod-upgrade

Works again. Nice https://github.com/hpi-studyu/studyu/actions/runs/5941775759/job/16113353278


[bug] process.env breaks Vite-based projects in Dev

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
2.1.0
wagmi Version
2.9.2
Current Behavior
Importing RainbowKit in Vite after 2.1.0 causes the app to crash when running in local dev.
https://github.com/rainbow-me/rainbowkit/blob/2d4c86d87c3acf01d9f2a8d5e79cbe14d32a8ca7/packages/rainbowkit/src/core/network/enhancedProvider.ts#L7
This crashes Vite in local
Expected Behavior
env variable call is performed rather with import.meta.env or process.env based on the corresponding environment.
Steps To Reproduce
React + Vite site import rainbowkit and run in development.
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

@mirshko Thanks for raising this issue. We're going to push a fix here in a bit 👍


Start match with selected character

Closes #1000
Works in conjunction with this client PR. Both need to be merged together.
Motivation
Users must be able to select the character they want to play with.
How has this been tested?
To test it is needed to enable one or more characters in the client, since in this PR Muflus is the only one available. This is done by selecting the scripteable object of the character you want to enable and check the "Enabled" option.

To test character selection:

Go to character list scene, choose one and select it in the character info scene.
You will be taken to the main scene and the character model to appear in the middle of the screen should be the one you chose.
Also the selected_character column in your database user should be the character chosen.
When you play a game the character you are assigned should be the one you have selected.

Closes #1000
Works in conjunction with this client PR. Both need to be merged together.
Motivation
Users must be able to select the character they want to play with.
How has this been tested?
To test it is needed to enable one or more characters in the client, since in this PR Muflus is the only one available. This is done by selecting the scripteable object of the character you want to enable and check the "Enabled" option.
* To test character selection:

  * Go to character list scene, choose one and select it in the character info scene.
  * You will be taken to the main scene and the character model to appear in the middle of the screen should be the one you chose.
  * Also the `selected_character` column in your database user should be the character chosen.
  * When you play a game the character you are assigned should be the one you have selected.

Now, to change the enabled / disabled characters we have to edit MainScreenManager.cs


Generate skybrush material

Generate a material for skybrushes and use it with the stencil buffer to prevent material system from rendering stuff over the skybox which would be normally culled by the BSP.
Fixes #1249.

For me it fixes plat23, but introduces a regression on Watah, viewpos -8657 3096 179 177 5:

This is a special map because it has two skyboxes. For now the material system always shows the red one, but that happens to be the correct one at that spot. It shouldn't look like a box though.

Hmm, so there are maps with more than 1 skybox. I think I know how to fix it in that case.

For me it fixes plat23, but introduces a regression on Watah, viewpos -8657 3096 179 177 5:

This is a special map because it has two skyboxes. For now the material system always shows the red one, but that happens to be the correct one at that spot. It shouldn't look like a box though.

This is fixed now.

Hmm, so there are maps with more than 1 skybox. I think I know how to fix it in that case.

Another map with >1 skybox you may wish to test on is tremship.

Another map with >1 skybox you may wish to test on is tremship.

Thanks. It's still a bit broken there, but an improvement over what we had.

Great, now both of the skyboxes can be drawn depending on where you are.
The spot I screenshotted above isn't 100% fixed FWIW. If you look through at an oblique angle, you can see some movers floating in space. But maybe that just needs to wait for other entities to be migrated to the material system.

Yeah, I'm not sure yet what is causing that issue.

I fixed the above issue, but this fix seems to degrade performance considerably.

Something wrong here:
	if ( environmentNoFogDraw && renderSkyBrushDepth ) {
		renderSkyBrushDepth = true;
	}

Ah, right, should be set to false. Still doesn't fix the performance issue however.

I have some ideas on how to fix this without decreasing performance, just need to correctly select which skybox to draw.


💲[Native Checkout] Add New Card View

📲 What
Adds a new PledgeAddNewCardView and appends an instance of this view the stack view that displays cards in PledgePaymentMethodsViewController.
🤔 Why
So a user can add a new card during the pledge flow.
🛠 How
Adds PledgeAddNewCardView and appends an instance of this view to the credit cards array in PledgePaymentMethodsViewController. The PledgeAddNewCardView has an "Add new card button" that triggers the modal presentation of the AddNewCardViewController.
Note that currently you can only display and dismiss the Add New Card screen - actually adding a credit card will be done separately.
👀 See
The new view:

And in action:

♿ Accessibility

[ ] Tap targets use minimum of 44x44 pts dimensions
[ ] Works with VoiceOver
[ ] Supports Dynamic Type

🏎 Performance

[ ] Optimized Blended Layers (screenshots)

✅ Acceptance criteria

[ ] Log into an account. Turn the native checkout feature flag on. Navigate to any project, select any reward. Scroll down to the list of credit cards, then scroll all the way to the end of the credit card list. You should see a new view "Add new card" and tapping the "Add New Card" button should display the add new card screen. Tapping "Close" on the add new card screen should dismiss the screen.

 [Checkout] Pledge Payment Methods Collection View Cell - Add New Card


perf: remove unnecessary codes + better reactivity

PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #6661 and improves on https://github.com/kodadot/nft-gallery/pull/6613#issue-1840929715 & https://github.com/kodadot/nft-gallery/pull/6685#issue-1847845191
[ ] Requires deployment <snek/rubick/worker>

Before submitting pull request, please make sure:

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

Optional

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

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

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

Copilot Summary

🤖 Generated by Copilot at 769abca
Refactored the code for opening the shopping cart modal from the navbar. Moved the logic and configuration from ShoppingCartModalConfig.ts and ShoppingCartButton.vue to Navbar.vue to improve code organization and performance.

🤖 Generated by Copilot at 769abca

ShoppingCartButton
Simpler, no more emit -
Autumn leaves falling

pls check this
https://share.cleanshot.com/ZxRVLGGM

pls check this
https://share.cleanshot.com/ZxRVLGGM

what is the URL of this?
Sorry i am new in this project.

pls check this

https://share.cleanshot.com/ZxRVLGGM

What is supposed to happen with the wallet there?
It looks exactly the same in my end on the latest main branch
https://github.com/kodadot/nft-gallery/assets/3810177/71bc856c-d901-4e16-bd64-a8e6e3da7ba5
I'm not quite sure what you want me to see. Please feel free to create a separate issue, so we can address this further.
Thank you so much

the wallet address should update when the prefix changes

pls check this

https://share.cleanshot.com/ZxRVLGGM

What is supposed to happen with the wallet there?
It looks exactly the same in my end on the latest main branch
https://github.com/kodadot/nft-gallery/assets/3810177/71bc856c-d901-4e16-bd64-a8e6e3da7ba5
I'm not quite sure what you want me to see. Please feel free to create a separate issue, so we can address this further.
Thank you so much

nevermind that was another issue mb

Meanwhile check @stephenjason89

https://github.com/kodadot/nft-gallery/pull/6688

@yangwao btw just curious, what's the practice here if we need to pull changes from main.
Do we rebase then force push or merge changes on top? I just think merging changes on top makes it harder to review changes of the PR

Do we rebase then force push

We don't do a force push here.
So the answer is, merge from the main, is it.

makes it harder to review changes of the PR

ok, close this PR, thank you for your time.

Closing in favor of

fix(chain redirects): Follow up: Changing network in navbar always redirects to Landing page #6688

Good job @hassnian
@exezbcz please close #6661

@stephenjason89 thanks for letting me know sir! Feel free to pick up another issue 🚀


Please release changes

There are some nice changes and bug fixes going back almost a year. Please cut a new release for the Supermarket. :smiley:

@cwebberOps Sorry to ping you directly. Can you or someone else at Chef please take a look at this cookbook and cut a new release? It's been over a year and lots of recent issues have been addressed in master :+1: Thanks in advance.

v.1.8.0 was just released to the Supermarket - http://supermarket.chef.io/cookbooks/users

Thanks @nathanharvey. You rock.


Using "webView2" variable in Spartan WebView doc is confusing

Now that we have MUX WebView2 on Anaheim Edge, we might want to change the sample code here from "webView1" and "webView2" to webViewA and WebViewB or something.

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

ID: bb1e6f48-d57c-65c1-9f05-1d76db94294f
Version Independent ID: d69a866b-7f25-5543-6fa2-fbf9b830548b
Content: WebView Class (Windows.UI.Xaml.Controls) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.UI.Xaml.Controls/WebView.xml
Product: uwp
Technology: winui
GitHub Login: @jwmsft
Microsoft Alias: jimwalk

Thanks for the suggestion. This update was completed some time ago, but this issue didn't get closed. Closing it now.


Make constant offset in qMagnitudeTransform a parameter

The qMagnitudeTransform that I used in ISBI looked like:
def qMagnitudeTransform(q):     return np.log(1e-6 + q ** 2)
But it would be more appropriate for the constant to be tunable.

Investigate whether there are simpler expressions (i.e. not needed motivation) that could be used.


🚀 Feature Request: Override http://placeholder url in miniflare fetch proxy

Describe the solution
I'm not exactly sure how this could be done, but when trying to utilize something like Hono OpenAPI from Miniflare, the context object results in a host-relative incorrect URL:
apiV1.doc('/doc', (ctx) => ({
  openapi: '3.1.0',
  info: {
    version: '1.0.0',
    title: 'Torch',
  },
  servers: [{ url: `${new URL(ctx.req.url).origin}/api/v1` }],
}));

This isn't an issue in Production because the correct URL is present in the request. In the case of local development, we don't have access to the true hostname from the context, so there isn't any way to fixup this URL because we don't know what the original hostname was supposed to be.

Does this happen with Wrangler, or when running Miniflare directly?

This is when running Miniflare directly via unstable_dev for use in a Vite plugin.

unstable_dev only add on http://placeholder if the URL passed to the fetch() function is not absolute. Passing in an absolute URL (including a host) should make this work as expected.
If that doesn't work, would you be able to put together a minimal reproduction with just unstable_dev (omitting Vite) and we can investigate further?

@penalosa
I ended up fixing my issue by doing what you had suggested. I'm not sure if there is any other way to make it work!


✨: Add healthz and metadata collector and metricses

I would start to include the metrics exposed by https://github.com/zolamk/hasura-exporter in a similar fashion as well.
This is still WIP

@zolamk Great idea here (https://github.com/hasura/graphql-engine/issues/6336)
I started this PR and would slowly translate the collectors you developed into rust and integrate them here. I started with two small ones (health and metadata consistency).
Would be great to get your input on this. :)


Generic host: Startup class

From what I can tell the generic HostBuilder currently does not have the same Startup class pattern that the WebHostBuilder uses. Personally I like the separation of concerns there since with the WebHostBuilder all the logic that deals with the host itself is maintained inside Program.cs, while the Startup class deals only with your app. In the HostBuilder model these concerns are intertwined inside Program.cs.
Was this a deliberate choice, or is it still open for discussion?

This is deliberate for two reasons.

Startup is ASP.NET specific, the Configure method builds a http request processing pipeline. It's not clear what a generic version of this would look like.
Startup requires two service containers, one from the host to instantiate it, and a second for the app with the results of ConfigureServices. This dual container model has caused a lot of confusion with the current stack so we want to avoid it in the new stack.

That said, We're not moving web apps over to the generic host for a while yet and we'll likely need at least some compat shims for Startup when we do migrate. Here's the generic web host prototype: https://github.com/aspnet/Hosting/blob/e892ed8bbdcd25a0dafc1850033398dc57f65fe1/samples/GenericWebHost/Program.cs#L26

See https://github.com/aspnet/Hosting/issues/1163 (the Startup section) This was intentional.


"react/prop-types" array length with optional chaining

Hello, when i use optional chaining with array (array?.length), react/prop-types warns that length is missing in props validation, but if i use (array || []).length it does not warn
Type used for array: array?: Array<Entity>
Exact error: ESLint: 'array.length' is missing in props validation(react/prop-types)
Environment:
"typescript": "^3.7.5",
"eslint": "^7.1.0",
"eslint-plugin-react": "^7.30.0",

That’s because it’s an optional type - it could be undefined.

No, the problem was that i had cached lower version of library (about 7.10), i reinstalled node modules with 7.30 and now it does not warn, seems it was fixed between 10 and 30 versions, thats why i closed the issue


Added files via upload

Modal - Nir and Haggai

@nbarel
Please refactor class names to follow SUIT CSS naming convention like required.
https://github.com/suitcss/suit/blob/master/doc/naming-conventions.md


Add a table of hardware requirements for various node types

I've collected info for core, horizon, and rpc nodes. I used the following sources for this info:

core node: https://developers.stellar.org/network/core-node/admin-guide/prerequisites#compute-requirements
horizon: https://developers.stellar.org/network/horizon/admin-guide/prerequisites (includes the api server, and the postgresql server)
soroban rpc: https://github.com/stellar/helm-charts/blob/main/charts/soroban-rpc/values-pubnet.yaml (I tried to use the helm chart and its comments)

Should I include details for anchor platform and sdp?
I'm not entirely sure the best way to evaluate which cloud SKU works best, I took a stab, but I could use some recommendations for how to find the right fit. For example,

many of the cloud vm skus don't include storage, but it can be configured through whatever related service. is that acceptable for some of these workloads?
i tended toward the "general computing" skus, since I didn't know if memory-, cpu-, storage-optimized was better for any of them. Would love some insight on that.

I also added some sidebar config that should be helpful for readers of this page (and perhaps the network overview page, too)

Preview is available here:http://developers-pr568.previews.kube001.services.stellar-ops.com

Here's the relevant preview page: https://developers-pr568.previews.kube001.services.stellar-ops.com/network/requirements

Love it! Question. Is "Node Hardware Requirements" the right language? I associate "Node" with Core Node but not necessarily with Horizon.

Also, there are existing hardware requirements in the Admin Guides for these various services. For example: https://developers-pr568.previews.kube001.services.stellar-ops.com/network/soroban-rpc/admin-guide#hardware-requirements. Should we remove these?


feat(DropdownMenu):Add tag

Add custom tag property to DropdownMenu component, div by default (for bootstrap 3 only)

Following https://github.com/reactstrap/reactstrap/pull/413

Travis does not trigger it as well, I'll try to do with another naming branch


Conditioning on baseline with different representation dimension

Hi !
In paper, in 2.3, you state that:

we again train two probes; each is the concatenation of two representations of size d

And in README, there is written that:

Conditional probing: measure only the aspects of property that aren't explainable by the baseline of your choice.

Just to be 100% sure:
Is it methodologically correct to condition on baseline which has different representation size than main model?
e.g. I would like to have BERT base (d=768) as baseline and BERT large (d=1024) as main model.

Thanks for the question! The sizes can differ.
In Section 2.3 of the paper, we incorrectly indicate that the sizes must be equal; this is true in the paper's experiments but need not be true in general. In Appendix A, we give a formal definition that does not have this requirement; see for example Example 1 as well, in which the different variables have different dimesionalities.

Thanks for answer !


I would like to add Simon Game and TicTacToe Game Web Projects

Pls Assign me this issue

@naveen3011 I have made PR for both Projects. Pls merge them. Thanks


Syscall: project file organisation proposal/discussion

So, about https://github.com/albenik/go-serial/commit/68d334cc615660457c9ca6cf114be691727acd04
My motivation is simple. Currently I very active using go-serial (thanks!) in my current work. I working with many vending devices, where I have often switch read timeouts while single packet read operation. So I have to implement some new methods peeped in the project https://github.com/pyserial/pyserial (it's only for windows yet, I plans to complete work and propose it to you)
While I learning and comparing both pyserial and go-serial and looking for simplest way to port code, it was very difficult for me finding syscall definitions scattered throughout the code. Also It was difficult for me to choose a place for new syscalls.
My be if you project fresh for you, and as author you keep in mind design features it's easy. But for me it was difficult. I talks predominantly windows syscalls of course, not for single unix ioctl
Therefore I propose to consolidate syscall definitions. There is two way:

Put it to one place in serial_* files
Put it to separated files like in syscall package

I choose second way, because I think it's generic apporoach. And it's possible more common for any new people which will want to commit in you prtoject.

I would have accepted the above if the readability gain was substantial, but this doesn't seems the case because, at the moment, the //syscall are near the place where they are effectively used, I think it's a better place that gives more context to understand why those syscall are needed and how they are used. Actually moving them in another file seems to reduce readability IMHO (as well as adding 4 more file to the "mass" of code).

It's true for you — author! Not for me, which have to learn code.
For example:
I look an implementation of some new function in pyserial. I found some syscalls in this implementation. When I read MSDN about found syscalls. When I need to compare exists syscalls in go-serial to check all required syscalls present and it look like expected.
With generic approach, I just find a syscall_* files and read it.
With consolidated placement approach, I have to do a text search on a project files to find //sys entities, when navigate to it and read.
Whith current go-serial approach I have to do text search aganin and again to find concrete syscall. Or at leas I have to scroll code up and down, up and down...

@albenik
sorry for the long delay, free time is always a scarce resource...
Ok you convinced me, we can go with your suggestions, if you care to push a PR.
Thanks!

Pull request ready.

fixed by #24


Use reference point for FlatProjection

In this PR FlatProjection requires reference point instead of just reference latitude. Plus it makes x and y fields in FlatPoint public. This makes it much easier to use this crate in cases when we need a relative offset to a selected zero point, plus this API is closer in spirit with the cited document, in the algorithm described there they also subtract reference latitude and longitude before multiplying them by KPD.

I've also changed code to use latitude, longitude order, which is a standard according to ISO 6709 and used in most of the modern applications.

I've also changed code to use latitude, longitude order, which is a standard according to ISO 6709 and used in most of the modern applications.

I would prefer to do that refactoring in a separate PR once this is merged so that we can discuss it independently

I think both changes are small enough to be discussed in one PR and splitting them will be an unnecessary busy-work. Plus I currently use ref_point branch in my application, so I would prefer to keep it as-is. If you'll decide to keep lonlat order I can revert the change for this PR. (though I will have to use a forked version for my app, which I would like to avoid)


Informatica - Make "marketplaceSubscriptionId" an optional field for "MarketplaceDetails"

…tails"
ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[x] Other, please clarify:

Marking one field under MarketplaceDetails as Optional, as it is not present while sending the API request and it is generated internally

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

/azp run

@almasak - Please don't request merge until the required gates are met. The Next Steps to Merge comment is continually updated to help you through the process. Your PR is currently queued for ARM review.


Update links for GISAID and GenBank accessions

Description of proposed changes
Adds a rule to fetch GISAID and GenBank accession links from UCSC
and uses the output in the transform_genbank and transform_gisaid
rules.
The UCSC file is modified to keep the headers and format exactly the
same as the current source-data/accessions.tsv.gz file so that it can
be directly replaced.
Related issue(s)
Resolves https://github.com/nextstrain/ncov-ingest/issues/484
Checklist

[x] Checks pass
[x] GISAID trial run
[x] GenBank trial run
[x] 2nd GISAID trial
[x] 2nd GenBank trial

Brief look at the trial run output metadata

I subset to the gisaid_epi_isl and genbank_accession columns, only including rows where both are not "?".

zstdcat open-accession-metadata.tsv.zst \
  | csvtk -t cut -f gisaid_epi_isl,genbank_accession \
  | csvtk -t filter2 -f '$genbank_accession != ?'
  | csvtk -t sort -k genbank_accession > open-accessions.tsv

I used daff to compare the trial data with the prod data to get a summary of changes:

GISAID

@@
count

+++
2141069

---
81421

->
755

GenBank

@@
count

+++
1248778

---
7964

->
2424

The number of removals (---) and changes (->) makes me think that we might want to keep the original source-data/accessions.tsv.gz and just append the UCSC file.

Glad you're using the latest now and sorry I fell behind with the manual updates!  Feel free to send me examples of any changes/omissions that look concerning.  When the same sequence has been submitted multiple times to GISAID or GenBank (and especially when it has been submitted multiple times to both), there can be some instability from one run to the next regarding which of multiple possible IDs get paired up, which would explain some changes.  Also, over time, some sequences have updates submitted, or are withdrawn from one repo or the other (or both).

I think it makes sense as you say to have the linkage be the best current attempt at linkage and it's okay if this is not fully stable.

If there's no other feedback, I'll merge this tomorrow morning before the automated run.


Command: vue config implemented

I've wrapped up the new vue config command.
Takeway:
If there is a better way to do a conditional check to only print the config and resolved path when vue config is invoked let me know.
Out of the box Commander doesn't support options with multiple values. My work around for the vue config -s <path> <value> command was to pass an optional argument to the command and do a conditional check if present.
I added the dependency opn  for opening the config file with vue config -e if there is a shared utility for this I couldn't track it down.
Hope everything looks good!

@Akryum how's this look ?

@yyx990803 thanks for the feedback. Can you provide me an example of proposed wording for one of the commands?

Just replacing preset with config should be good for now.

@yyx990803 Changes made and pushed.
Nested path support implemented with dependencies
get-value
unset-value
set-value
commands/logs updated

@beardedpayton

Nested path support implemented with dependencies
get-value
unset-value
set-value

Wouldn't be better to just one dependency for this case? I am thinking https://github.com/sindresorhus/dot-prop

@yyx990803 Do the changes look good to be merged? Or does this PR need more work?


Unable to pass private_hosted_zone attributes

I am currently trying to pass the private_hosted_zone attributes as a schema and i keep getting the following error:
Here is how its defined in my code:
  private_hosted_zone = {     id = var.private_hosted_zone_id     role_arn = var.private_hosted_zone_role_arn   }
Error: Invalid private_hosted_zone attribute assignment │  │   with module.cluster_creation.rhcs_cluster_rosa_classic.rosa_sts_cluster, │   on modules/cluster_deployment/main.tf line 25, in resource "rhcs_cluster_rosa_classic" "rosa_sts_cluster": │   25: resource "rhcs_cluster_rosa_classic" "rosa_sts_cluster" { │  │ Invalid configuration. 'private_hosted_zone.id' and │ 'private_hosted_zone.arn' are required
If the values are hardcoded it works, but passing the values as a variable doesn't work

Hi @hhh0505 ,
Thank you for sharing this information
I also faced with this issue, and its seems not related to the provider
We are investigating this issue
Can you share more info, so we can use it during the investigation:

Terraform cli version
RHCS terraform provider version

Hi @nirarg ,
I'm working with @hhh0505 on this, here's the info you requested:

terraform 1.2.9 x64
terraform-redhat/rhcs v1.4.0

I'll also add that this issue is preventing us from using a resource attribute that is known after apply as the value to private_hosted_zone.id. Therefore my interpretation is that this argument does not handle any type of dynamic value as its input. Here is our resource declaration for rhcs_cluster_rosa_classic:
resource "rhcs_cluster_rosa_classic" "rosa_sts_cluster" {
  name                 = "test-${var.environment}-${var.region_abbreviation}"
  cloud_region         = var.cloud_region
  aws_account_id       = data.aws_caller_identity.current.account_id
  availability_zones   = data.aws_availability_zones.available.names
  replicas             = var.replicas
  autoscaling_enabled  = var.autoscaling_enabled
  min_replicas         = var.min_replicas
  max_replicas         = var.max_replicas
  version              = var.openshift_version
  machine_cidr         = var.machine_cidr
  private              = true
  aws_private_link     = true
  multi_az             = true
  aws_subnet_ids       = var.subnet_ids
  compute_machine_type = var.compute_machine_type
  base_dns_domain      = aws_route53_zone.private.name
  properties = {
    rosa_creator_arn = data.aws_caller_identity.current.arn
  }
  private_hosted_zone = {
    id       = aws_route53_zone.private.zone_id
    role_arn = "arn:aws:iam::<account-id>:role/<role-name>"
  }
  sts                      = local.sts_roles
  wait_for_create_complete = true
}

And here is the error:
│ Error: Invalid private_hosted_zone attribute assignment
│
│   with module.cluster_creation.rhcs_cluster_rosa_classic.rosa_sts_cluster,
│   on modules/cluster_deployment/main.tf line 39, in resource "rhcs_cluster_rosa_classic" "rosa_sts_cluster":
│   39: resource "rhcs_cluster_rosa_classic" "rosa_sts_cluster" {
│
│ Invalid configuration. 'private_hosted_zone.id' and
│ 'private_hosted_zone.arn' are required
╵

I believe this could be an issue with the resource validator, more specifically the function IsStringAttributeEmpty that seems to only accept a value known during validation, thus not accepting variables or resource attributes known after apply.
This is blocking us in automating from beginning to end a deployment of a ROSA cluster that uses a shared VPC, since that requires reserving a DNS domain with the rhcs_dns_domain resource, creating a private hosted zone using that domain and passing its ID to create the cluster.

@nirarg Is there any update when we could expect a fix for this? This is preventing us from creating a Shared VPC.

@hhh0505 I'm not sure what is the root cause but it's not a specific issue for the RHCS provider...
The private_hosted_zone attribute is declared as a SingleNestedAttribute.
In order to set and use variables for private_hosted_zone it should be declared as a variable from the type object. Please try to update the varibale.tf file with that declaration:
variable "private_hosted_zone" {
  type = object(
    {
      id  = string
      role_arn = string
    }
  )
  default = null
}

And then you can pass it in the rosa resource like that:
resource "rhcs_cluster_rosa_classic" "rosa_sts_cluster" {
  name           = var.cluster_name
  ......
  private_hosted_zone = var.private_hosted_zone
}

If you're passing value into from the CLI you can run it like that:
export HOSTED_ZONE_ID=""
export HOSTED_ZONE_ROLE_ARN=""
terraform apply  -var "private_hosted_zone={\"id\"=\"$HOSTED_ZONE_ID\",\"role_arn\"=\"$HOSTED_ZONE_ROLE_ARN\"}"

Please update us if it's working for you.

@bardielle  Thanks for the reply, the only thing is if you create the hosted zone inside the module (which we are) than you reference the resource id to get the hosted zone ID similar to the example that @RelicCornhusk  posted above
private_hosted_zone = {     id       = aws_route53_zone.private.zone_id     role_arn = "arn:aws:iam::<account-id>:role/<role-name>"   }
This doesn't work and fails with error above, I suppose we could try to input these values inside of a local to pass it as an object.

I tried debugging it and it seems that the request looks like this:
req.ConfigValue =  {"id":<unknown>,"role_arn":"arn:aws:iam::<account-id>:role/<role-name>"}:

If I understood it correctly, it means that the output of the aws_route53_zone is not known in the plan step, and the validation is done as part of the plan and check if the value is a valid string
I will update it and release it in v1.4.2

@hhh0505 The v1.4.2 would be released on Dec 06

@hhh0505 Sorry for not updating you...  we found one more bug by the QE team so it took us some time to solve it..

Version v1.4.2 was released today.
Please update/ close the issue.

Issue is fixed, thanks @bardielle


feat(modeling)!: converted code to ES6 import / export

WORK IN PROGRESS DO NOT MERGE
BREAKING CHANGES
The changes move JSCAD from CommonJS to ES6 modules. Summary of progress.

[ ] modeling (INPROGRESS)
[ ] core
[ ] io
[ ] cli
[ ] array utils
[ ] regl-renderer

NOTE: Due to incompatibility of the 'most' libraries, the WEB UI will not be converted. A new WEB UI will be developed as part of V3.
All Submissions:

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Does your submission pass tests?

Technical Notes:

"type": "module" must be added to package.json
all require paths need to be reviewed and changed, ending with *.js module name
all functions are exported by name, as well as exported as default

this is a huge task. Let me know when/if you want me to test something. I am guessing this is in progress currently.

this is a huge task. Let me know when/if you want me to test something. I am guessing this is in progress currently.

@hrgdavor Thanks. I'll let you know when some of the libraries are ready for testing.
There's no way to do this in pieces so ONE HUGE set of changes.

I know you have asked abou changes to jscad for v3, there is one thing that was nagging me
const jscad = require('@jscad/modeling')

and then I need to look into jscad.booleans to get subtract ... and 99% of the functions in to primitives, booleans etc have unique name.
it would be nicer if they were declared on top level instead:
const { cube, subtract, translate} = require('@jscad/modeling')
// or import for es6 ofc
import { cube, subtract, translate} from '@jscad/modeling'

as a bonus, this would also improve current issue I have with vscode that prefers to generate automatic import like this
const {subtract} = require('@jscad/modeling/booleans')

which then breaks the script

I know you have asked abou changes to jscad for v3, there is one thing that was nagging me
const jscad = require('@jscad/modeling')

and then I need to look into jscad.booleans to get subtract ... and 99% of the functions in to primitives, booleans etc have unique name.
it would be nicer if they were declared on top level instead:
const { cube, subtract, translate} = require('@jscad/modeling')
// or import for es6 ofc
import { cube, subtract, translate} from '@jscad/modeling'

Good idea. However, the API changes will have to be completed in another set of changes.
Can you create a new issue for this, and label with V3?

@hrgdavor @platypii @SimonClark the conversion is complete, moving all code (except web) to ES6. here's the state of play...

array-utile converted, all tests pass
modeling converted, all tests pass
io packages converted, all tests pass. HOWEVER deserializers translate objects into CommonJS code
core converted, all tests pass. HOWEVER changes are required support designs with ES6 code bases. It may be possible to support designs with CommonJS code bases as well.
cli converted, all tests fail. Once core is corrected then the CLI should work once again.

can we run tests from root of the monorepo ?
<EMAIL_ADDRESS>test C:\hrg\3dp_dev\OpenJSCAD.v3\packages\io\gcode-deserializer
> ava './test.js' --verbose --timeout 2m

  ✖ Based on your configuration, 1 test file was found, but did not match the CLI arguments:

  * './test.js'

 ELIFECYCLE  Test failed. See above for more details.

I tried and have issue with @jscad/gcode-deserializer

One option for cli to work would be to have a cmdline option to say if it is es6 script that needs to run, or "old" .


Increase char limit on FileAttachment.mimetype

Closes:
DNE
What's Changed
Increase character limit on FileAttachment.mimetype to 255 to allow for all mime types to be used.

Thanks for the PR! You'll need to run nautobot-server makemigrations to generate a migration for the data model change, then run black to apply the correct formatting standards to the migration file, then commit the migration file as well.


Replace bottom link to forum with link to reddit

to clarify, the links at the bottom of surge under MakerDAO currently link to the chat and to the forum, and i think it is more appropriate to link to the chat and the reddit

@apmilen @pimato Ready to be tested on Surge.


Refactor/folder structure

Probably resolving merge conflicts needed.

I merged #543 into this so that you can merge it without merge conflict.

I fixed the merge issues.
@vahidbazzaz I merge this now and it could create some merge conflicts in other PRs. You should maybe merge master in the PRs you are working on.