Issues & Suggestions

So glad there's updates for this again. By far the best front end I've tried.
Not sure to what level you're working on this and I'm sure you're aware of this issue:
Vita games don't open in Vita3k. It launches the app but doesn't launch the game, it just returns to game list in Daijisho.
One thing I really like the look of in ES-DE is the Custom Game Collections. Like the favorites you have but can group games together under any header. So I could for example have a Zelda collection that has all Zelda games from all consoles in one place.
Thanks again for building such a great app/front end!

There was a small change in the Daijishou update to correct the issue from #222
Update the PS Vita platform for the latest Vita3k am start argument

I've done this but it still just opens Vita3k but doesn't launch any games. Am I missing something really obvious here?

Just tested on my end and it works.
Did you update the PS Vita platform? If yes, what is your am start for Vita3k?

I did.
{
"databaseVersion": 8,
"revisionNumber": 4,
"platform": {
"name": "Sony PS Vita",
"uniqueId": "vita",
"shortname": "vita",
"description": null,
"acceptedFilenameRegex": "^(?!(?:\._|\.).).$",
"scraperSourceList": [
"LIBRETRO:Sony - PlayStation Vita",
"DSESS:BOX_ART:TAGS(scraperKeyword):https://thegamesdb.net/search.php?name={scraperKeyword}&platform_id[]=39&dsess_selector=img.card-img-top&dsess_attribute=src&dsess_replacer=images\%2F.*\%2Fboxart&dsess_replacer_value=images%2Foriginal%2Fboxart",
"DSESS:GENRES:TAGS(scraperKeyword):https://thegamesdb.net/search.php?name={scraperKeyword}&platform_id[]=39&dsess_target_site_selector=div.col-6+a&dsess_target_site=.*\%2Fgame.*&dsess_selector=div.col-lg-8+div.card-body&dsess_extractor=.*<p>Genre\(s\)%3A(.*)<\%2Fp>",
"DSESS:BOX_ART:TAGS(scraperKeyword):https://www.mobygames.com/search/quick?q={scraperKeyword}&p=105&search=Go&sFilter=1&sG=on&dsess_target_site_selector=div.searchTitle+a&dsess_target_site=^https%3A\%2F\%2Fwww\.mobygames\.com\%2Fgame\%2Fmsx\%2F.*%24&dsess_selector=div%23coreGameCover+img&dsess_attribute=src&dsess_replacer=\%2Fs\%2F&dsess_replacer_value=%2Fl%2F"
],
"boxArtAspectRatioId": 0,
"useCustomBoxArtAspectRatio": true,
"customBoxArtAspectRatio": "256:327",
"screenAspectRatioId": 0,
"useCustomScreenAspectRatio": true,
"customScreenAspectRatio": "5:3",
"retroAchievementsAlias": null,
"extra": ""
},
"playerList": [
{
"name": "vita - vita3k",
"description": "Supported extensions: dpt.",
"acceptedFilenameRegex": "^(.*)\.(?:dpt)$",
"amStartArguments": "-n org.vita3k.emulator/org.vita3k.emulator.Emulator\n --esa AppStartParameters -r(?<!\\),{tags.game_id}",
"killPackageProcesses": false,
"killPackageProcessesWarning": true,
"extra": ""
}
]
}

I'm having trouble launching Vita3k games from daijisho too. Ive updated the platform just now and changed the am start parameters for Vita3k as sugested. Using your dpt files too, but when I click to launch the games, the vita3k app just flashes and then ir returns to games list inside daijisho. Probably doing something wrong, could you help me?

Not sure what else to say but make sure your on the latest Daijishou (1.4.69) and have updated the platform.
https://github.com/user-attachments/assets/b96868c4-05e7-480b-828d-f3aa44186254

I also love the idea of having Custom collections, it could be something like a group in the widgets tabs

Not sure what else to say but make sure your on the latest Daijishou (1.4.69) and have updated the platform.
file.1.mp4

I'm on Daijishou 1.4.69 (update via Obtanium so have got the most recent 2 updates)
Downloaded json file from : https://github.com/TapiocaFox/Daijishou/blob/main/platforms/SonyPSVita.json which says it was updated 18 hours ago.
Imported via library settings
Created 2 dpt files so games show in frontend.
Games are installed in vita3k and show in list and can be launched direct from vita3k.
But still get result in video...
https://github.com/user-attachments/assets/39d23707-bc17-44c0-8d5c-21698a8ff0f6

Hmm, are you using the correct dpt files? You can double-check by opening the dpt file with a notepad editor. Make sure the contents match the games title id. You can check the games title id via Vita3k.

https://github.com/user-attachments/assets/4665efb3-e48c-4bbe-89da-dea4f500cd26
Checked the ID, apparently it's right

@banzaibill7 what device & what version of Daijishou your using?

Daijishou > Settings > About

The problem was the version. I was at 1.4.68, updated to 1.4.69 and now it's working. Using Odin 2 btw

Checked version: 1.4.69 (401)
Checked game number.
Checked dpt file matches game number.
Checked platform.
Still same issue.
I'm at a loss, especially as other people are getting this working! :((
https://github.com/user-attachments/assets/a884065e-45a5-4d43-8235-9afd448e70c6

Sorted it! Finally got it working!
Although the dpt file looked right. There must have been an odd character or something. Deleting it and re-typing sorted it!
Thanks for the help!


Edit and move pyproject.toml

Need to finalize pyproject.toml contents and move to the top level opentowork folder

#101


[BUG] Check for updates error

Please make sure you've tried the latest version of Fritter first, as the F-Droid version is sometimes out of date!

Describe the bug
Fritter shows error when checking for updates.
To Reproduce
Steps to reproduce the behavior:

Go to Settings
Click on Check for updates
See error when opening Fritter

Screenshots

Device
Fritter:
3.0.0-beta4 (20220923)
Android version:
12
Kernel build information:
Linux localhost 4.14.113-24706840 #1 SMP PREEMPT Thu Jul 21 14:53:58 KST 2022 aarch64 Android
Device manufacturer:
samsung
Device model:
SM-G973F

This was caused by an outage in the update checking script. It should be fixed now!

Oh, it was checking for the latest release.
I'm using the latest pre-release.


Include documentation/sources of CEF in pandomium?

Is this possible?
I know its possible if u add this to your pom.xml file:
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-source-plugin</artifactId>
                <version>3.2.1</version>
                <executions>
                    <execution>
                        <id>attach-sources</id>
                        <goals>
                            <goal>jar</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-javadoc-plugin</artifactId>
                <version>3.0.0</version>
                <executions>
                    <execution>
                        <id>resource-bundles</id>
                        <phase>package</phase>
                        <goals>
                            <!-- produce source artifact for main project sources -->
                            <goal>resource-bundle</goal>

                            <!-- produce source artifact for project test sources -->
                            <goal>test-resource-bundle</goal>
                        </goals>
                        <configuration>
                            <doclint>none</doclint> <!-- Remove this, if you want to get build errors when there is an issue with a comment/documentation. -->
                            <detectOfflineLinks>false</detectOfflineLinks>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

        </plugins>

I've attached docs & sources of Pandomium. At this moment I don't think I'll be able to attach CEF sources and docs as I may need to do it during the process of building their artifacts which I don't have time to right now.


Merging development into master

Coverage decreased (-0.3%) to 43.678% when pulling d7dc3806c37b63e57d54c3ff219b0499e181c5b1 on development into 8e484e5ed0ea9726fe2ae9d402c8eb333edb8245 on master.


Server is down...

Can you please take a look?

I noticed this over the weekend as well and checked this AM to see if it may still be down.  @josesimoes I saw your post and figured I'd post too.
@madskristensen if there's anything I can do to help, let me know.

I noticed this over the weekend as well and checked this AM to see if it may still be down.  @josesimoes I saw your post and figured I'd post too.
@madskristensen if there's anything I can do to help, let me know.

I restarted the server. Thanks for the heads up

I restarted the server. Thanks for the heads up

@madskristensen server is down again
HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit
Common solutions to this issue:
ANCM failed to start after 120000 milliseconds

Thanks for the heads up @MagicAndre1981. I restarted the server instance

I restarted the server instance

thanks, works now again

the server is down again @madskristensen
The page cannot be displayed because an internal server error has occurred.


Problem using Appveyor build cache

Description
Even when packages and paket-files are successfully restored from cache, paket restore is restoring (or at least downloading) all packages again. Problem reported here
The same happen if you test this manually with RDP to the AppVeyor build VM before paket restore is called. Subsequent call to paket restore does not trigger dependencies download.
Probably something else should be cached, cannot figure out what. Or maybe the fact that every new build is happening in new VM affects something...
Repro steps
It can be reproduced by forking the repository from original post and creating AppVeyor build against it.
Expected behavior
Dependencies should not be downloaded again
Actual behavior
Dependencies which are already restored from cache are being downloaded.
Known workarounds
Not aware of

So you are talking about https://www.appveyor.com/docs/build-cache/?
I actually didn't know this exists. Can you tell us what directories you have tried to set (ideally a ready to use yml file)? It would help if we could reproduce this locally (and a yaml file might give a hint).

Sure this is ready to use YAML from our customer who reported the issue. I forked that repo and was able to reproduce it myself. I tried to cache paket.lock itself, but that did not help. Must me something else in file system (or somewhere else) which makes paket restore to download dependencies which were restored from the cache. As I already mentioned, subsequent attempt to run paket restore (with YAML or in RDP) behaves better - it does not download anything.

@IlyaFinkelshteyn Thanks! Yes currently it's not enough to only save the packages folder. This only works when using the paket caching feature.
So you either want to use the caching feature or (appveyor) cache the nuget packages folders

v3: C:\Users\<user>\.nuget\packages
v2: C:\Users\<user>\AppData\Local\NuGet\Cache

See https://docs.microsoft.com/en-us/nuget/consume-packages/managing-the-nuget-cache
Let me know if that works (or doesn't work)
BTW: It's best practive to checkin the paket.lock file into the repository, so there shouldn't be a need to cache that.

Maybe we should add that appveyor caching feature to the paket documentation, once we have figured out the best way to use it.

I have a similar issue but with gitlab-ci.  They have no plans to allow caching outside the build folder. However they have suggested this work around https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/97#note_3429931

Thanks folks. I was able proceed a bit more with the following in my
appveyor.yml.
I have a question for both Matthias/Jimmy (paket) and Ilya (appveyor)
Question for Ilya: I am unable to specify the paket.lock dependency in
the first 3 lines, yml validation fails.
If I remove them, the cache works however at the end of the build we still
checksum + verify if the cache is upto date. That takes up sometime as the
cache is ~600mb.
I was expecting if I specify paket.lock even cache validation wont happen.

'%USERPROFILE%.nuget\packages' -> packet.lock
'%LocalAppData%\NuGet\Cache' -> packet.lock
'%LocalAppData%\NuGet\v3-cache' -> paket.lock
paket-files -> packet.lock

Question for Matthias/Jimmy:
I see paket-files still get downloaded even after they have been restored
from the cache. Any idea why?
Thanks!
On Wed, Jun 14, 2017 at 2:01 AM, Jimmy Byrd<EMAIL_ADDRESS>wrote:

I have a similar issue but with gitlab-ci. They have no plans to allow
caching outside the build folder. However they have suggested this work
around https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/
97#note_3429931
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/2395#issuecomment-308165357,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACCpLOWO4MlOfQglZDONloGpzW1neOdGks5sDrJkgaJpZM4NwotT
.

I've noticed the download again too, not sure why.

I'm struggling a bit with this. I have been caching %LocalAppData%\NuGet\Cache for a while and everything worked. I've noticed this has now stopped working (though I don't know when): Paket now reports it's downloading all the packages.
If I change to cache %USERPROFILE%\.nuget\packages, then this seems to fix the problem (Paket no longer reports anything is downloaded). The downside here is that that folder contains all the nupkgs and all the unzipped content of those packages. So I'm caching twice as much as I need to (which slows down the build time).
I've read the additional caches part of the docs and thought I could alleviate this by setting the NuGetCachePath environment var and caching that folder. From my testing, it seems that the only files that get put in here are .json and .nupkg.sha512 files, the nupkgs themselves still get downloaded to %LocalAppData%\NuGet\Cache and then extracted to %USERPROFILE%\.nuget\packages.
Am I doing something wrong or is there a bug here?

I'm currently working around this by adding a cache .nupkgs versions: current in my paket.dependencies file. So now I can cache the .nupkgs folder in AppVeyor, which contains only what's needed for a restore.

The issue with caching appears to have been logged - I've debugged and added my comments to #2841.


[Feature Request] Filter reports by INSTALLATION_ID

ACRA assigns unique UUID for each app instance, see ReportField.INSTALLATION_ID. In Acrarium these IDs are shown in the report as "User". But we haven't found any way to view all reports from specific user.
Motivation: we're using ACRA for monitoring not only crashes, but also other abnormal situations. There may be thousands of reports. Having this filter would be very helpful in a number of cases, for example:

investigate how often a problem occurs for a specific user
perform a cross-check between ACRA reports and user complaints through other channels

Firebase Crashlytics has this functionality for a long time.
BTW, many thanks for ACRA & Acrarium! :)

It might be even better to generalize this somehow, for example to be able to search/filter by "custom data" from ACRA.getErrorReporter().putCustomData(). In our specific case that would be more convenient (we put our own ID there), but not a deal-breaker. :)

Copying my just-about-perfectly-duplicate use case over here:

I checked the API class and I tried just constructing a URL but I can't see how to get all reports for a given ACRA install id, and this is actually my most common use case:
1- user logs an issue in our tracker, with debug info including their install ID
2- I want to go to acrarium or hit a URL/API via script with their install ID and pull stack traces
We have for example https://ankidroid.org/acra/app/1/bug/2651/report/3df33eb7-af8b-422a-b4c5-88a4ffa83c37
and in there, we have user 98814994-580a-48ca-b76d-4a40ea9ea6fa
But I don't see anything like https://ankidroid.org/acra/app/1/user/98814994-580a-48ca-b76d-4a40ea9ea6fa
Is this possible? Is this a feature request that's interesting for you and a PR would be welcome?
PRs appear to be welcome, with a simple addition to the API being a pretty easy start apparently

@F43nd1r you added this and released this while I was traveling so I did not have a chance to try it right after release. Today I had a request for user crash lookup by installation UUID though, so I thought it would be faster to drop the new jar in place and restart vs scrolling the old way and sure enough, this was fantastically easy to use. It Just Worked(tm). Thank you for adding this, it is now the most useful feature for us (other than accepting / warehousing the reports to begin with) :bow:


400 Bundle is invalid. Empty bundle

I thought this was related to Issue #28 but I can reproduce it with the example code without my for_each mess.
Terraform Version
Terraform v0.12.13

provider.apigee (unversioned)
provider.archive v1.3.0

Apigee provider 0.0.17
Affected Resource(s)

api_proxy

Error text
...
apigee_api_proxy.helloworld_proxy: Creating...
apigee_developer.helloworld_developer: Creating...
apigee_company.helloworld_company: Creating...
apigee_target_server.helloworld_target_server_testing: Creating...
apigee_company.helloworld_company: Creation complete after 1s [id=7c1dafd2-634b-4a47-9b17-7b1872450d70]
apigee_developer.helloworld_developer: Creation complete after 1s [id=da5244de-0ab6-4e11-be72-a4c01f93291e]
apigee_target_server.helloworld_target_server_testing: Creation complete after 3s [id=afe85c40-4074-430e-8b04-27b8e56f8fba]

Error: [ERROR] resourceApiProxyCreate error importing api_proxy: POST https://api.enterprise.apigee.com/v1/o/<env>/apis?action=import&name=helloworld-terraformed: 400 Bundle is invalid. Empty bundle

  on builder.tf line 11, in resource "apigee_api_proxy" "helloworld_proxy":
  11: resource "apigee_api_proxy" "helloworld_proxy" {

Terraform Configuration Files
Just copypaste the example
Expected Behavior
Expected proxy files to be written to ~/proxy_files, and an appropriate archive created in ~/proxy_files_bundle
Actual Behavior
Nothing was created in ~/proxy_files and so an empty zip file was created in ~/proxy_files_bundle
Steps to Reproduce

copypaste example code into a repo (fix the reference to var.env instead of testing)
fill out access_key or whatever
terraform apply

@tibers you have to have a bundle defined. The invalid bundle error is coming back from Apigee as the bundle is invalid.
The example assumes you have created a proxy bundle already.  See the data archive_file block below:
# This is a normal terraform offering and serves as an example of **how you might create a proxy bundle**.
data "archive_file" "bundle" {
   type         = "zip"
   source_dir   = "${path.module}/proxy_files"
   output_path  = "${path.module}/proxy_files_bundle/apiproxy.zip"
}

Note that the proxy simply uses this bundle:
# The API proxy
resource "apigee_api_proxy" "helloworld_proxy" {
   name  = "helloworld-terraformed"                         # The proxy name.
   bundle       = "${data.archive_file.bundle.output_path}" # Apigee APIs require a zip bundle to import a proxy.
   bundle_sha   = "${data.archive_file.bundle.output_sha}"  # The SHA is used to detect changes for plan/apply.
}

If you use the bundle that is under apigee/textfixtures it should work as a test for you:
resource "apigee_api_proxy" "foo_api_proxy" {
   name                 = "foo_proxy_terraformed"
   bundle       = "apigee/test-fixtures/helloworld_proxy.zip"
   bundle_sha   = "${filebase64sha256("apigee/test-fixtures/helloworld_proxy.zip")}"
}

For more information on how Apigee deploys proxies or for any questions about the APIs you can look at the Apigee API doc as well.  The terraform provider essentially wraps these APIs:
https://apidocs.apigee.com/management/apis/post/organizations/{org_name}/environments/{env_name}/apis/{api_name}/revisions/{revision_number}/deployments
If you haven't already done so, I would recommend that you create a test proxy in Apigee using the console so you understand how bundles work, get everything working, then apply terraform to the problem to automate deployments going forward.

OK thanks for the clarity. So is there a way to deploy an apiproxy with this module without having to create this godawful xml bundle? Is this an apigee limitation?

Apigee is a powerful tool for writing proxies and doing many other things.  You will need to have some experience with it in order to automate it with this Terraform provider or any other automation tool.
Similar to a lambda function the bundle is the proxy as code and yes, this is an Apigee thing.  I would recommend you do some tutorials using Apigee and learn how to write, export, and import a basic reverse proxy looking at the bundle that is created to understand how Apigee works.  This will help illuminate why this Terraform provider does what it does.
If you think the helloworld bundle is bad, you should see a real production proxy. :smile:


use io.open() and specify encoding utf-8 to fix python3/windows encod…

Description

Fixes the windows/python3 decoding error when installing setup.py . This issue is caused by the differences in how Python2/Python3 handle data. The fix is compatible with Python 2 and 3 on windows and linux.
more info on this error:
https://ncoghlan-devs-python-notes.readthedocs.io/en/latest/python3/text_file_processing.html#what-changed-in-python-3
GitHub Issues

https://github.com/Miserlou/Zappa/issues/809

Coverage remained the same at 71.961% when pulling 59626162e479eb6a17cb6db546e8d3712480e8f1 on dazcode:master into bc95a5547413639d9688eca4ce6d40cc56ace78a on Miserlou:master.

Tusen takk.


feat: implement path module on android

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information
closes #6054
For more information on well-known directories on Android see https://developer.android.com/training/data-storage/app-specific

@JonasKruckenberg what do you think of doing this "the plugin way"? https://github.com/tauri-apps/plugins-workspace/pull/259
It also includes a Rust API (tied to tauri::App, similar to the current .path_resolver() API).

Hello, I'm just wondering if there is any projected timeline for this to be done?

This work was moved to https://github.com/tauri-apps/tauri/pull/6339. We'll likely add it to the next release, hopefully this weekend @eddycurrently


Research Permit Resource Model edits

[ ] Under Research Location, at bottom of page, add a multi-pick option "within Provincial Park" and "within other parks"
[ ] Under Research Location, at bottom of page, add a large freeform textbox to accommodate a list of up to 12 names, called "First Nations Consultation Areas"
[x] Under Research Permit Assessment Criteria, change "on park" to "in a park"
[x] On Final Research Report FMO Assessment page – final header should say “FMO Report Response”

Questions:

[x] Can we create multiple Communication Logs – one for each First Nation?
[x] Will First Nations Contact be associated with all information as entered as Contributor? - Yes

@LeannePyle  - Just wondering to simplify things - can we just change the Research Assessment criteria from "in a park" to within Provincial Park" and "within other parks" so we don't have to add another pick list?


Extend convolution layer to support padding

References:

http://deeplearning.net/software/theano/tutorial/conv_arithmetic.html
https://adeshpande3.github.io/A-Beginner's-Guide-To-Understanding-Convolutional-Neural-Networks-Part-2/
http://cs231n.github.io/convolutional-networks/

It's not actually needed because we can construct and generalize Residual Networks without padding.


Clarify the ansible collection path

In the getting started guide it is recommended to create an ansible.cfg file in the extension directory.  I don't believe this is ever used.
A new ansible.cfg file is built in each ephemeral directory and used for each step.
I think the best approach here is to suggest the following entry in each scenario/molecule.yml file:
provisioner:
  name: ansible
  config_options:
    defaults:
      collections_path: ${ANSIBLE_COLLECTIONS_PATH}

and then have the user set the ANSIBLE_COLLECTIONS_PATH environment variable at the command line prior to running molecule
export ANSIBLE_COLLECTIONS_PATH=/home/user/working/collections

We might also consider adding this to the molecule.yml file that is templated out during init.
This leaves a hard coded path out of the code, but does require the next user to set the var after cloning.
(Note: The tox-ansible plugin sets this environment variable for the user, so if the molecule scenarios are being run with pytest or tox this should be taken care of. This can be seen here using all three in a collection here ansible.scm
Feedback welcome.
Brad

@ajinkyau Can you look into this?  ping me if more info is needed

@cidrblock I'm in favour of adding the provisioner entry to the molecule.yml file during initialisation.

Hi, @cidrblock and @ajinkyau! I have tried the approach @cidrblock mentioned in the comment, but it didn't work out for me.
I can see that molecule was able to identify and correctly populate both the ansible.cfg and molecule.yml in the ephemeral directory, but when I run molecule converge, it still thinks that it should have the collection's path alongside the extension's folder.

My ansible.cfg generated inside ~/.cache/molecule/extensions/default:
# Molecule managed

[defaults]
ansible_managed = Ansible managed: Do NOT edit this file manually!
display_failed_stderr = True
forks = 50
retry_files_enabled = False
host_key_checking = False
nocows = 1
interpreter_python = auto_silent
collections_path = /home/r0x0d/Workspace/infra/
[ssh_connection]
scp_if_ssh = True
control_path = %(directory)s/%%h-%%p-%%r

and my molecule.yml, also generated inside ~/.cache/molecule/extensions/default:
# Molecule managed

---
dependency:
  command: null
  enabled: true
  env: {}
  name: galaxy
  options: {}
driver:
  name: vagrant
  options:
    managed: true
  provider:
    name: libvirt
  safe_files: []
  ssh_connection_options: []
platforms:
  - box: eurolinux-vagrant/centos-7
    cpus: 2
    default_box: eurolinux-vagrant/centos-7
    hostname: infra.convert2rhel
    memory: 2048
    name: instance
prerun: true
provisioner:
  ansible_args: []
  children: {}
  config_options:
    defaults:
      collections_path: /home/r0x0d/Workspace/infra/
  connection_options: {}
  env: {}
  inventory:
    group_vars: {}
    host_vars: {}
    hosts: {}
    links: {}
  log: true
  name: ansible
  options: {}
  playbooks:
    cleanup: cleanup.yml
    converge: converge.yml
    create: create.yml
    destroy: destroy.yml
    prepare: prepare.yml
    side_effect: side_effect.yml
    verify: verify.yml
role_name_check: 0
scenario:
  check_sequence:
    - dependency
    - cleanup
    - destroy
    - create
    - prepare
    - converge
    - check
    - cleanup
    - destroy
  cleanup_sequence:
    - cleanup
  converge_sequence:
    - dependency
    - create
    - prepare
    - converge
  create_sequence:
    - dependency
    - create
    - prepare
  destroy_sequence:
    - dependency
    - cleanup
    - destroy
  name: default
  test_sequence:
    - dependency
    - cleanup
    - destroy
    - syntax
    - create
    - prepare
    - converge
    - idempotence
    - side_effect
    - verify
    - cleanup
    - destroy
verifier:
  additional_files_or_dirs: []
  enabled: true
  env: {}
  name: ansible
  options: {}


new property endSessionText

Text on tab when session expired

If you want to submit a new property, that's fine, but you've pushed a ton of changes here. Mostly things that are very specific to your implementation like updating the logout url and such. Please create a new pull request with ONLY the new property.


Dev for lazarus?

hello , thanks for  the nice work , could this be used in lazarus?

Hello @alas82
We've been getting a lot of requests to add support for Lazarus, and we're interested. However, it's not on our roadmap in the short term, there are other demands up front such as C++Builder support and static linking (no dll) on Windows.

If you want, you can continue the discussion in topic #119


pallet-staking: Add extrinsic force_apply_min_commission

This PR adds the extrinsic force_apply_min_commission. The extrinsic can only be called by root and will increase any commission that is less than the MinCommission.

/benchmark runtime pallet pallet_staking

Generally these kinds of unbounded loops are an anti-pattern for the runtime.
I get that it is a root function and all, but I don't see why this has to be this way.
You could just as easily make a function which updates just a single validator, and let it be called by anyone. Then someone can write a batch script, or ping old validators one by one to update them.

Generally these kinds of unbounded loops are an anti-pattern for the runtime.
I get that it is a root function and all, but I don't see why this has to be this way.
You could just as easily make a function which updates just a single validator, and let it be called by anyone. Then someone can write a batch script, or ping old validators one by one to update them.

fwiw we generally assume that we can absolutely iterate over all validators all over the staking system, which is why I recommended this PR this way for the sake of simplicity.
But I see your point: Let's not build more on top of a bad assumption. Batching a transaction that sets a single validators is also easy enough.

Generally these kinds of unbounded loops are an anti-pattern for the runtime.
I get that it is a root function and all, but I don't see why this has to be this way.
You could just as easily make a function which updates just a single validator, and let it be called by anyone. Then someone can write a batch script, or ping old validators one by one to update them.

fwiw we generally assume that we can absolutely iterate over all validators all over the staking system, which is why I recommended this PR this way for the sake of simplicity.
But I see your point: Let's not build more on top of a bad assumption. Batching a transaction that sets a single validators is also easy enough.

In the scenario the community wants to set the min commission and and force apply it in the same batch call, setting single validators is sub optimal. Once the call is crafted and proposed, validators who previously had higher commissions can reduce their commission to below the min, effectively circumventing the force apply. You could specify every validator knowing it would be a no-op if their commission was high enough, but I am not sure that approach would scale if the number of validators becomes very large.
My plan is to change this so the number of iterations is bounded by the weight input param.

/benchmark runtime pallet pallet_staking

effectively circumventing the force apply

But in this case they already increased their commission and the objective is achieved.
I think a batch call is less of the evil and simple enough.
It is not that we are going to do this every hour, so we don't need to care too much about it being the most efficient.

But in this case they already increased their commission and the objective is achieved.

What I was trying to say is that they can lower their commission after the call has been put up as a referenda. However I do think the approach of specifying a single validator is more extensible in the long term.
I update the impl in 4077606 to only take 1 stash as an arg, so needs a re-review @kianenigma @shawntabrizi

/benchmark runtime pallet pallet_staking

/benchmark runtime pallet pallet_staking

/benchmark runtime pallet pallet_staking

/benchmark runtime pallet pallet_staking

/benchmark runtime pallet pallet_staking

@shawntabrizi

doc wording update 0d90a92
extrinsic change to return dispatch error if stash doesn't exist https://github.com/paritytech/substrate/pull/10786/commits/0d90a92a052acbfe69fba0ffcbb0806aeb24e410

bot merge


Automatically enable tax plugins when configured

Currently, users have no idea how to enable vatlayer/avatax. The set the keys as said in the documentation but are not told to update the PLUGINS = [] settings.
I suggest we do the following:
DEFAULT_PLUGINS = []

if VATLAYER_ACCESS_KEY:
    DEFAULT_PLUGINS.append("saleor.extensions.plugins.vatlayer.plugin.VatlayerPlugin")

if "PLUGINS" in os.environ:
    PLUGINS = get_list(os.environ.get("PLUGINS"))
else:
    PLUGINS = DEFAULT_PLUGINS

Saleor-docs contains information on how to append new plugin. Personally, I think that modifying settings.py is a bigger effort than benefit.  If someone wants to use avalara or vatlayer, she/he will need to check documentation no matter if we have this if, else.

Closed since it's described in the docs.


New format with different endianess for better performance

During today's review of the code we noticed that we read codes using a MSB to LSB order which implies the need to use big-endian words. Since most modern computers are little-endian we might want to add backends to support LSB to MSB order, thus little-endian order, which might result in better performance.
We will discuss this further in the future as it might lead only to marginal improvements and needs to be accurately benchmarked.

Yes, let's make this more explicit. When we had the first meeting I had a completely twisted memory of how the bitstream is implemented, and I now believe that it is fundamental to change the bit endianness of the current format, which was conceived around Java's inherently big-endian design.
The modifications are as follows:

Instead of bit k of the stream being the bit of index 7 - k mod 8 of byte k div 8, bit k of the stream should be the bit of index k mod 8 of byte k div 8. That is, we are reversing bit endianness at the byte level. With this change, we can indeed read files (on little-endian architectures) with words of arbitrary size. That is true of big-endian architectures in this moment, and it's not good.
However, all fixed-size read or write of bit blocks should happen with the bits reversed, because this is the "natural" order with small-endian bits. That is, reading bit blocks from the bit buffer or writing to the bit buffer should happen with a couple of logical operations; writing fixed-size bit blocks in a true small-endian order would be prohibitively slow.

This has the consequence that we will not be able to convert between the two formats just by reversing the bits in each byte, and in particular that no reasonably fast on-the-fly conversion will be possible (but I might be wrong on this).
More precisely: if we write the ɣ code for 4, namely 00101, in a bit stream presently we get the byte 00101000. We would like to switch to a format where writing the same code is written 00001100. Note that the unary part is reversed, but the "payload" of ɣ code is always written in the same direction, which is essential for quick insertion and extraction.
@zommiommy, please correct me if I'm wrong.

It's great that you have designed a new/better format. YAY for fresh looks at old problems!
About this (emphasis mine):

This has the consequence that we will not be able to convert between the two formats just by reversing the bits in each byte, and in particular that no reasonably fast on-the-fly conversion will be possible (but I might be wrong on this).

We can still have a batch and slow conversion tool from the current webgraph-java format to the new upcoming webgraph-rs format, correct?
Because if not that would force us to postpone experimenting with the current compressed Software Heritage graph (which uses the previous webgraph-java format) to the point we also have an implementation of compression in webgraph-rs, which would be unfortunate.

Yes. I was thinking about this issue this morning.
I think that the correct thing to do is to work on readers and writers in parallel and for both formats. It is a bit more work initially, but we have the advantage of having the possibility of unit-testing since the start reading and writing in both formats, and in particular converting graphs. (I'm not saying to develop compression now, just bit-writing code, even a not particularly efficient one).
An alternative is to write the conversion software in Java. But I think that it would also be useful to have a big-endian Rust version as people would be able to use (more slowly, if my intuition is correct) the current graphs.
So I would suggest that @zommiommy starts in parallel a reader and writer for big and little endian formats. For the WordReader, I guess a const template parameter is sufficient. In the end, the only difference is a single call to the byte-rearrangement function if the native endianness and the format of the file disagree. We will have to add an endianness field to the graph .properties file, and assume that it is big if not specified.
For the bit reader, code is slightly different—in the big-endian case we keep the bit buffer filled "at the top" (i.e., the most significant bits are correct), whereas in the little-endian case we keep the bit buffer filled "at the bottom" (i.e., the least significant bits are correct). In the big-endian case, to read a unary code we count the number of leading zeros, whereas in the little-endian case we count the number of trailing zeros. In the big-endian case, to extract k bits we take the k most significant bits of the bit buffer, whereas in the little-endian case we take the k least significant bits of the bit buffer.
But this is where the difference end. All other codes can be read using unary codes and bit blocks, so the rest of the code would be common (including minimal binary codes, albeit in the end the sequence of written bits would be different in the two cases—Tommaso, we can talk about this).
Note that the weird lack of symmetry between little and big endianness of my previous message is due to the same lack of symmetry at the hardware level—big-endian architectures and small-endian architectures orders bits in a byte in the same way, and that's essentially a small-endian way: bit 0 is the least significant bit.

Ok implemented both readers, note that I explicitly use to_be, and to_le so these should work on both big endian and little endian machines. Of course, you will have better performance if the format and machine endianess matches. Now I think I'll proceed implementing the writers, if you agree.
Something I'm not sure yet is if we should have a single struct with a generic const to set the endianess, or have two different structs.
My concerns are the followings:
Two structs: Code duplication
Generic Const: Currently rust supports only integers, char, and bool as generic consts. The most explicit way would be to have an enumeration with two variants, but that requires the generic_const_exprs feature which is instable and incomplete.

Maybe having a macro for the time being, hoping that generic_const_exprs becomes stable? Or having 0/1 as const and we replace them later with a nice enumeration (0 is smaller, so little endian, 1 is bigger, so big endian)?
I'd say that a reasonable immediate target to is arrive at a point where we have unit tests writing and reading ɣ codes in both formats. Then the rest should be relatively easy. And at that point we can also do some benchmarking.

In code the alterantives I see are:
Generic const enum:
#![feature(adt_const_params)]

#[derive(PartialEq, Eq)]
enum Endianess {
    Big,
    Little,
}

struct Reader<const E: Endianess>;

fn main() {
    let r = Reader::<{Endianess::Big}>;
}

Generic const bool:
struct Reader<const LittleEndian: bool>;

Two structs:
struct ReaderLittleEndian;
struct ReaderBigEndian;

Define two types as genercis. As bitvec does
struct LittleEndian;
struct BigEndian;

struct Reader<E>(std::marker::PhantomData<E>);

fn main() {
    let r = Reader::<LittleEndian>;
}

te target to is arrive at a point where we have unit tests

Sure, let's start with anyone, and then, once the proof of concept works, migrate the code to the format we hope is the best.

I'd follow the bitvec path. Good point. If possible, maybe we can use the same structs of bitvec—certainly we will need it at some point.


Remove {documentName} from route

I simply want my swagger.json endpoint without v1 showing in the url.
This https://localhost:44310/swagger.json instead of this https://localhost:44310/v1/swagger.json
Is it possible?

I think the authors have good reason not to include this feature, given that API versioning is important  to the long-term maintainability of both the API and consuming apps. That's probably why the configuration helpfile is explicit about requiring {documentname} in the path.
There's a simple workaround, however: if you absolutely need this, e.g. to offer a permalink for the "current version", or just because it looks prettier, you could always add a rewrite rule to your app that would silently return the response from the configured url to users requesting your chosen path.

I would provide the same response as @FearNotDaniel

I would provide the same response as @FearNotDaniel


Argentina Mobile and SMS

We're using the library to validate SMS phone numbers, and Argentinian SMS has a wrinkle - it doesn't support the leading 9, per http://en.wikipedia.org/wiki/Telephone_numbers_in_Argentina#Inbound_SMS
Also, it looks like Argentinian numbers can be 6, 7 or 8 digits long.  I'm curious about the 10 in the code:
country_code: "54", country_name: "Argentina", mobile_begin_with: ["9"], phone_number_lengths: [10]
Would you entertain a pull request that removes the mobile_begin_with 9 requirement and replaces the 10 with 6, 7, 8, 9 (to cover whether or not the leading 9 is present).  Or is there a better approach to fix this?

:+1: struggling with the same problem

I'm having the same issue as well

+1


Inputs get reset when @Published value is updated if AuthenticatorTheme is used

Every time the value of a @Published property is updated, all the inputs get reset. (see video)
When removing the AuthenticatorTheme there is no problem.
Example code is attached.
https://github.com/aws-amplify/amplify-ui-swift-authenticator/assets/30449693/cf8bcbf9-bbb3-43d1-96ec-962209da155e
import SwiftUI
import Authenticator
import Amplify
import AWSCognitoAuthPlugin
import CoreLocation

class LocationDelegate: ObservableObject{
    @Published var location: CLLocationCoordinate2D = CLLocationCoordinate2D(latitude: 10.0, longitude: 10.0)

    init() {
        Timer.scheduledTimer(withTimeInterval: 1, repeats: true) { timer in
            self.location = CLLocationCoordinate2D(latitude: self.location.latitude + 0.01,
                                                   longitude: self.location.longitude)
        }
    }
}

@main
struct AuthTestApp: App {
    @StateObject private var locationManager = LocationDelegate()

    init() {
         do {
             try Amplify.add(plugin: AWSCognitoAuthPlugin())
             try Amplify.configure()
         } catch {
             print("Unable to configure Amplify \(error)")
         }
     }

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environmentObject(locationManager)
        }
    }
}

struct ContentView: View {
    @EnvironmentObject private var locationManager: LocationDelegate

    var body: some View {
        TabView {
            AuthViewTheme()
                    .tabItem{
                        Image(systemName: "person.3")
                        Text("not ok (with theme)")
                    }.clipped()
            AuthViewNoTheme()
                    .tabItem{
                        Image(systemName: "person.3")
                        Text("ok (no theme)")
                    }.clipped()
        }
    }
}

struct AuthViewNoTheme: View {
    var body: some View {
        Authenticator { state in
        }
    }
}

struct AuthViewTheme: View {
    private let theme = AuthenticatorTheme()

    var body: some View {
        Authenticator { state in
        }
        .authenticatorTheme(theme)
    }
}

Hi @steefeen, thanks for opening this issue.
As your LocationDelegate is being set as an environment object on the root ContentView, having its published property updated will trigger an update in all your views. This causes AuthViewTheme to be redrawn each time as its identity changes due to the theme property being re-created.
To address this, you can annotate the theme with a @StateObject:
struct AuthViewTheme: View {
    @StateObject private let theme = AuthenticatorTheme()

    var body: some View {
        Authenticator { state in
        }
        .authenticatorTheme(theme)
    }
}

Or you can move its initialization to your AuthTestApp file and set it as another environment object.
@main
struct AuthTestApp: App {
    @StateObject private var locationManager = LocationDelegate()
    private var theme = AuthenticatorTheme()

    init() {
         do {
             try Amplify.add(plugin: AWSCognitoAuthPlugin())
             try Amplify.configure()
         } catch {
             print("Unable to configure Amplify \(error)")
         }
     }

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environmentObject(locationManager)
                .environmentObject(theme)
        }
    }
}

struct AuthViewTheme: View {
    @EnvironmentObject private var theme: AuthenticatorTheme

    var body: some View {
        Authenticator { state in
        }
        .authenticatorTheme(theme)
    }
}

Please let me know if any of these address your issues. Thanks!

Hi @ruisebas
replacing:
private let theme = AuthenticatorTheme()

with:
 @StateObject private var theme = AuthenticatorTheme()

in my original example, resolves my issue.
Thanks

Great to hear! I'm closing this issue, feel free to open a new one if something comes up.
Thanks!


fix: bad contrast color for link on footer 🛠

Description

This PR is about fixing the bad contrast color applied for link on footer, the color applied during the hover state also seems to be have a bad contrast.
I have updated the colors with good contrast which matches the footers background as well, take a look at below table

NORMAL STATE
HOVER STATE

$\textcolor{yellow}{\textsf{Imagine-AI}}$
$\textcolor{#2cceff}{\textsf{Imagine-AI}}$

Fixes #636
Screenshots
https://github.com/SurajPratap10/Imagine_AI/assets/92252895/c87c6f55-2bcb-4084-a82e-714cc1ea607c
Checklist

[x] Tests have been added or updated to cover the changes
[x] Documentation has been updated to reflect the changes
[x] Code follows the established coding style guidelines
[x] All tests are passing

Hey there @SurajPratap10 👋🏻
Please make sure to review this PR.
Thank you..!

Resolve Conflicts

@SurajPratap10 the Conflicts are resolved 🎉

Why you have changed so many lines?

@SurajPratap10 I formatted the code to maintain code consistency.

@SurajPratap10, Yeah i forget to mention that I have also formatted the code with best practices to maintain code consistency.
Can you provide level2 for the changes i done, because i refactored the code.

OK


[Java] Type-ids in UnionVector are erroneously coupled to the Arrow types of the underlying vectors

Describe the bug, including details regarding any error messages, version, and platform.
re: https://lists.apache.org/thread/z89xlvw7v1rwq89gknflhsj3c65x20kd
It seems that the UnionVector implementation (particularly initializeChildrenFromFields (#29848), getVector, getVectorByType, setSafe etc) assumes that the type-id is always based on the ArrowType, but the Schema.fbs spec is more lenient - users have the choice to use whatever type-ids they require.
For example, in XTDB, we're trying to represent an algebraic data type (ADT) of 'put', 'delete' and 'erase' events as a sparse union. Delete and erase have the same type, so UnionVector currently expects them to be the same type-id (whereas, in DenseUnionVector, we can use type-ids 0, 1 and 2).
Would there be an appetite for (potentially relatively significant) changes to UnionVector to make it behave this way? We could perhaps consider bringing it more in line with DenseUnionVector which seems closer to the spec. Would be happy to work on it if so.
Cheers,
James/Finn (@FiV0)
Component(s)
Java

Would there be an appetite for (potentially relatively significant) changes to UnionVector to make it behave this way? We could perhaps consider bringing it more in line with DenseUnionVector which seems closer to the spec.

+1. It would of course be better if a way of doing this without breaking compatibility with existing Java code is found.
cc @lidavidm @vibhatha @jduo

Are you speaking of significant API changes, or significant implementation changes? The latter is fine so long as existing tests pass.

I think there need to be significant (breaking) API changes if you want to make it spec compliant.

+1 for implementation changes preserving compatibility and current test coverage.
Any idea on the maginitude of this change?

If this is spec compliant, meaning it changes the existing spec, would it require a vote on ML?

This may sound harsh, but for me the current UnionVector API is broken in the light of the mailing list discussion above. Even looking at the first test of UnionVector, a line like
https://github.com/apache/arrow/blob/41a989c81616aea103e554521fa6d6209ffa248d/java/vector/src/test/java/org/apache/arrow/vector/TestUnionVector.java#L78
doesn't make sense. You could probably make a lot of the methods that exist work with only internal changes, but I would still argue for deprecation to discourage future use.

Any idea on the maginitude of this change?

A significant rewrite of UnionVector. I might even start from scratch basing it more on the DenseUnionVector implementation.

@pitrou I agree with that. Would it be possible to introduce a new API (as required by the discussed change) and leave the older API in deprecate mode and eventually let the migration happen at user end?

That's what I'm suggesting, yes.


Inject  viewport tag to  if missing

Add support to injecting <meta name="viewport"> tag if missing.
If the whole head is missing also inject a minimal <head> block with the <meta> tag.
Refactored the injection pipeline to be more flexible, so it's easier to add more injectable stuff if necessary.
Review Checklist

[x] All changes are described in the PR description
[ ] New feature and breaking changes have documentation
[x] New endpoints have API tests
[x] New frontend features have Enzyme tests
[x] No unnecessary or debugging code
[x] Questionable code is clearly marked with comments
[x] Manually tested with latest Firefox, Safari and Chrome

Added docs.
Rendered: https://github.com/ktk-2005/Feedbacker-Forum/blob/3ef6cdb015e6da2e226066dbf847a43aeb00f2fb/docs/container-proxy.md#injection-details


[iomgr] Restrict TCP read allocations to 8kb or 64kb

Builds on #30610 which should probably be landed first if we've got any hope of debugging this... and I'll likely put it behind a flag before trying to ship it.

Added a flag with ~old behavior as default... PTAL


feat: add tracepoint for light record

Description

ros2:dispatch_subscription_callback trace point is replaced with ros2:rmw_take by https://github.com/tier4/CARET_trace/pull/113.
This PR adds ros2:rmw_take to light option filter

Related links
https://tier4.atlassian.net/browse/RT2-725
Notes for reviewers

This PR can be merged prior to https://github.com/tier4/CARET_trace/pull/113
Confirmation results: https://github.com/tier4/CARET_trace/pull/113#pullrequestreview-1452073035

Pre-review checklist for the PR author

[x] I've confirmed the contribution guidelines.
[x] The PR is ready for review.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR has been properly tested.
[ ] The PR has been reviewed.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@nabetetsu
Could you review this PR?

@ymski
Could you review this PR?


xds: define empty config protos

Description: define empty config protos for all filters expecting google::protobuf::Empty
Risk Level: medium (change of config type)
Testing: unit
Docs Changes: done
Release Notes: define config protos for all extensions

I am wondering why there is a fallback in translateOpaqueConfig that does JSON round-tripping to convert a proto into another proto. While that helps here to convert Empty to an empty proto, it seems a bit unsafe to allow arbitrary Any to Any conversion.

@kyessenov can you give an example of how the unsafe conversion could be an issue? I think usually we should expect that in an opaque config, the intent is to describe the type that belongs to the filter. If it's untyped config, it's fine to JSON convert. For typed config, we probably could be a bit stricter on the fallback; only allow the existing or previous types of a specific message to be converted, but that seems a nice-to-have safety improvement, not a particularly dangerous thing as is.

@htuch It's odd because going through JSON loses type information, so if you have two Anys with different types for the same field, it's unclear what happens. It also means we cannot use the type as the primary way to identify the extension (what if you use one extension type as Any for another extension).


Add Kotlin Gradle plugin to the Gradle plugin portal

Tracking issue for https://youtrack.jetbrains.com/issue/KT-5756.

@yole, you mentioned you might be willing to take care of this? The instructions are at https://plugins.gradle.org/docs/submit, and of course we'd be happy to help with anything you need along the way.

@yole wrote:

regarding putting our plugin into the plugin portal. the instructions make a (very reasonable) assumption that Gradle plugins are built with Gradle, but ours isn’t - it uses Maven. can I use the plugin publishing plugin to publish an artifact that wasn’t built with Gradle?

@yole, @tomdcc will get back to you as soon as possible on how to do this.

FYI It looks like this was fixed according to the tracking issue.

Thanks for the info, @nesl247.


UI: Job is cancelled as it has been blocking others for too long

ISSUE TYPE

Bug Report

COMPONENT NAME

UI

CLOUDSTACK VERSION

4.19

CONFIGURATION

Advanced Networking
KVM
SharedMountPoint
OS / ENVIRONMENT

CentOS 7
SUMMARY

After upgrade to 4.19, UI report Unable to serialize: Job is cancelled as it has been blocking others for too long frequently for each operation, such as start VM, stop VM, taking snapshot..etc
STEPS TO REPRODUCE

Just perform random VM operation, 1/3 chance will get this error message, however the operation are  executed successfully no wonder it is real success or error.

EXPECTED RESULTS

Should report correct state of the job, and job queue and tasks timeout should respect the ACS timeout configurations.
ACTUAL RESULTS

Random error message regardless the actual task status.

Unable to serialize: Job is cancelled as it has been blocking others for too long

suspecting this issue is related to time sync between two management server, the problem significantly reduced after time correction.

suspecting this issue is related to time sync between two management server, the problem significantly reduced after time correction.

So we can close this issue?

@DaanHoogland yes, i dont have further input on this issue at this moment.


Destination balance changes: Issuer ?

So I am looking at TX:
5B6D93935862E393DFCCB0267A0BC77D2D10600ADBCF724C1C927FD061CBE341
If I look at the following:
["payment"]["destination_balance_changes"][0]["issuer"]
The issuer here might be the Market Maker that enabled the tx, where XRP was converted to CAD to be sent to the destination Ripple address. But the issuer is actually Bluzelle.
So question then is -- how do we, looking at this tx, get the actual issuer of the currency (CAD) being sent?
Incorrect issuer:
rQE5Z3FgVnRMbVfS6xiVQFgB4J3X162FVD
Correct issuer:
raBDVR7JFq3Yho2jf7mcx36sjTwpRJJrGU
Indeed, this tx refers to "raBDVR7JFq3Yho2jf7mcx36sjTwpRJJrGU" as the recipient, but we need to validate the issuer as being raBDVR7JFq3Yho2jf7mcx36sjTwpRJJrGU in the destination balance changes.

I noted that the field is being renamed to "counterparty" but I am unsure this relates to this issue -- right now, the counterparty field is undefined anyways in my copy of ripple-rest.

Here is a quick way to see the ripple-rest output:
https://api.ripple.com/v1/accounts/raBDVR7JFq3Yho2jf7mcx36sjTwpRJJrGU/payments/5B6D93935862E393DFCCB0267A0BC77D2D10600ADBCF724C1C927FD061CBE341

The balance changes should use counterparty instead of issuer, but issuer has been kept for backwards compatibility. See this blog post for more information: https://ripple.com/dev-blog/calculating-balance-changes-for-transaction/#counterparty-vs-issuer


Editor Shenanigans

Latest 'few' editor tweaks left me with odd behaviour in the editor. Certain broken cursor positions or input/output behaviour.
[HTML] Uncaught TypeError: Cannot call method 'setScrollSpeed' of undefined
This is causing the editor to be completely unusable. Treating insert as a copy/paste selection, then a copy/paste selection in multiple places. Unable to backspace. Ugh, it's a nightmare :c @Jazzelhawk ^^

Getting this too now.


There are some problems with compilation

Did you update he git submodules?

The problem is solved .I directly cloned the project and compiled it. I found that the godot-cpp folder was empty.


Add Motoko counter example

This implements the Motoko counter example found here: https://github.com/dfinity/examples/tree/master/motoko/counter.

Note: Because void types aren't yet implemented I had the update calls return the value of counter. This should be changed after #8 is implemented.

Resolves #52

Yes. I ran dfx deploy and ran through the  dfx canister call examples in the motoko readme. I also stopped dfx and restarted it to make sure that the state persisted, which it did.
The only difference was the return values because of the lack of a void type.


Weird characters showing up in Windows Powershell

I have written a simple test and I run it this way:
busted simple_test.lua

This is the lua file:
describe("This is the test", function()
    it("It part: ", function()
        local instance = game(false)
        instance:add_player("1", 10)
        instance:add_player("2", 10)
        assert.are.equal(#instance.user_ids, 2)
    end)
end)

and this is the output:
ΓùÅ
1 success / 0 failures / 0 errors / 0 pending : 0.0 seconds

What is the ΓùÅ part?

it is probably the default output formatter; which prints colored dots. I think it is not properly recognizing the powersehll terminal as not supporting those.
try another formatter like gtest for example;
busted -o gtest simple_test.lua

Once you find one that works for you you can add a .busted config file with those as a default.

see here: https://github.com/Olivine-Labs/busted/tree/master/busted/outputHandlers
(note that base is a base-class, the other ones can be used by specifying their file names, without the .lua part)


Backlight?

Hi.
I have a small question to you.
Is there a way to turn on/off the backlight on the display?
In my display I have both a white, green and a red backlight option.

Solved.
My fault.

This will not included because there are different backlights which are not part of the display itself and can controlled simply by analogRead():


naming

question for @IEvangelist - "Aspiregregator" (i'm giving some love to my old-school favorite RSS reader, Newsgator, which appeared before Google Reader, which was everyone's favorite RSS reader prior to the team killing the product and almost killing RSS adoption in the process) or "Aspire Reader?"

I'm good with the name, it's something that stands out and tips its imaginary hat to an old fav. Besides naming things is hard! 😄


added my name and github profile

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Updated 👍

We use capital letters for first name and last name, Kindly ask you to add the suggestion. 😁 Please let us know if you need any help!

Updated 👍


Migrate compiler validations for separate data model definition in persist directory

Description:
Sample data model, https://github.com/sameerajayasoma/bal-persist-design-prototypes/blob/main/rainier-sample/persist/rainier.bal

The latest compiler validations are tracked in https://docs.google.com/spreadsheets/d/1GIQJ_34AkFF0pmfGnUGPh78KwWkM_U8rYpPy17xiDiM/edit#gid=0

Closing as this is implemented

Reopening as optional assocaitations are not validated

Reopening for additional validations,

Identifier fields should be non-nullable field
Identifier field should be of SimpleType


Android issue when progress is 0

There is an issue in android when progress value is 0, because of react-native issue when transform scaleX value is 0. The workaround would be to set progress to 0.001 value, it would be great if you put that in documentation.

+1

Is this still a problem in react native 0.45.1? I cannot reproduce myself.

Anyway, duplicate of https://github.com/oblador/react-native-progress/issues/56


feat(ivc): accum errs in verify

Motivation
We only know about the first error that occurred during verify execution, but all of them may be important for us.
Overview
Collect of verification errors into vec

Made paralellization of different is_sat got 6 GB of logs with panics, so I canceled this logic for now.
Of course, debugging is insanely long, but it takes longer to download stacktrace

Without parallel, How large is the log now?  If it too large, we'd better leave it for personal debug only.

Made paralellization of different is_sat got 6 GB of logs with panics, so I canceled this logic for now.
Of course, debugging is insanely long, but it takes longer to download stacktrace

Without parallel, How large is the log now? If it too large, we'd better leave it for personal debug only.

With your new cs - it works fast even with err-aggregation. If it becomes a problem, we can hide it under cargo-feature or separate method, but for now this approach is much more logical, as I will remind you that this class is analogous to MockProver


raftstore: add a new tick to renew lease in advance

ref #11579
What have you changed?
Currently, the read lease of a leader is renewed after proposing a write or executing a read request with read index.
In some situations, a client may always try to read data after the read lease expired, read requests would be handled with read index, then the duration of read request could be higher than expected.
This PR introduces following changes:

Solve this problem by renewing the read lease in a tick.
Fix the metrics of awaken hibernated regions

What is the type of the changes?

New feature (a change which adds functionality)
Improvement (a change which is an improvement to an existing feature)
Bugfix (a change which fixes an issue)
Engineering (engineering change which doesn't change any feature or fix any issue)
Misc (other changes)

How is the PR tested?

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No
Benchmark result if necessary (optional)
TODO
Release note
renew lease on a new tick to cover lease till next tick

/bench

This work is delayed, close this PR temporarily.

/rebuild

PTAL @5kbpers @overvenus @nolouch

/bench

/bench

I have an idea to renew the leader lease even when hibernate region is used at the same time: instead of renewing lease in raft tick, we can do it when handling read request, that is, besides check the current time, we also check if the leader lease is gonna expired in near future if so we renew lease.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: 5kbpers:x: NingLin-PYou have signed the CLA already but the status is still pending? Let us recheck it.

what need to do if I want this merge this PR? @5kbpers

I come up with an idea to keep compatible with this PR and hibernate region which is to let regions that have read requests recently not go into hibernate state.
More specially, let call last_read_time + 10s as an active lease (10s just a random pick), when the local reader handle a read request it also extend the active lease by updating last_read_time with the current timestamp. And (in raftstore) the leader shouldn't become hibernated if the active lease is not expired  (by checking now() < last_read_time + 10s) so that the leader lease will be seamlessly extended by raft tick as long as there are read requests.
Although https://github.com/tikv/tikv/pull/9307 could also solve this lease extend problem with less raft tick and raft heartbeat, I think extending leader lease with raft tick is more intuitive and simple to implement.

Local read can't extends lease as it doesn't check quorum.

Local read can't extends lease as it doesn't check quorum.

Local read reqeust itself won't extend lease, but it keeps the leader from hibernating and then raft tick will trigger lease extend (by broadcast heartbeat).

Local read reqeust itself won't extend lease, but it keeps the leader from hibernating and then raft tick will trigger lease extend (by broadcast heartbeat).

So by saying "the local reader handle a read request it also extend the active lease by updating last_read_time with the current timestamp.", you mean local reader prevent leader from sleeping in next ready and force it to renew the lease instead of extends the lease immediately??
I don't think it's a good idea to rely on heartbeat ticks as users can change the heartbeat to arbitrary value.

So by saying "the local reader handle a read request it also extend the active lease by updating last_read_time with the current timestamp.", you mean local reader prevent leader from sleeping in next ready and force it to renew the lease instead of extends the lease immediately??

That is not what I mean, the proposal can be split into two part. Part 1 is the current PR, which will extend lease in on_raft_base_tick if the lease will be expired in near future. Part 2 is to make sure the leader will not become hibernated when there are still read requests so that there will always have raft tick to extend lease. And the implement is as simple as adding one more check now() < last_read_time + 10s when the leader decides whether become hibernated.
And it didn't rely on heartbeat tick but raft tick instead.

And it didn't rely on heartbeat tick but raft tick instead.

Then it's an even worse idea. I have seen it's set to hundreds of mills in production.

Then it's an even worse idea. I have seen it's set to hundreds of mills in production.

Rely on raft tick don't mean extend lease on every raft tick, we just add a check on on_raft_base_tick like lease_expired_time < now() + tick_interval * 2 (or other configurable interval) to see if the lease is gonna expire, and extend the lease if so. And there won't be any duplicated extend lease requests because we will check the read-queue to see if there are any ongoing requests first.

Don't put all things to a tick that's not design for. #9307 has already implemented a clean way that can extends lease with low cost.
In the long term, the lease should be extended by an independent polling ticks which should relay on the lease span itself instead of any other configurations.

Have restarted this work and ran a sysbench read_only benchmark, turns out with this PR we can reduce the tail latency of async snapshot (The first graph below is master, the second is this PR):

I found test_storage::test_before_propose_deadline was always failed, could you please take a look? @sticnarf

I found test_storage::test_before_propose_deadline was always failed, could you please take a look? @sticnarf

Emm, the error type now is what I wanted. I think previously the request was blocked at getting snapshot (due to no lease), so the deadline error is thrown when getting snapshot.
But the test actually wants to test dropping a request that is expired at proposing. It seems this PR makes getting snapshot work and let the test work properly.
@5kbpers Can you help fix the error type?

Any test to cover the change?

Modified test_renew_lease to cover it.

/run-all-tests

What's the resource overhead?

Has only 1~2% more cost of CPU:

/LGTM

LGTM

/merge

/hold

/unhold

/merge

/merge

/merge


select/ngOptions fails to update model after keyboard selection

See here:
http://plnkr.co/edit/9VymegmYt3tZPTH65Gj8?p=preview
Follow these steps:

Enter the first input
Tab to select
Press a
Press down

See that foo is now incorrect. If you use the mouse to select another and then reselect the same one, it then updates correctly.
Seems a rather odd, specific issue so im not entirely sure where in the chain this is occurring.

I just closed some duplicates of this issue, so here's a quick recap:
Chrome (Blink) / Safari (webkit) has a bug not firing change when an option is removed. Bug filed as https://code.google.com/p/chromium/issues/detail?id=415505
Firefox basically follows the "spirit of the spec" by not firing change when the select value is changed via keyboard, but Chrome and IE do it, so it coud be considered a bug. Tracked as https://bugzilla.mozilla.org/show_bug.cgi?id=126379.
As a workaround, you can add a directive that fires the change event on keyup (thanks to @gkalpak for this):
directive('changeOnKeyup', function changeOnKeyupDirective() {
  return function changeOnKeyupPostLink(scope, elem) {
    elem.on('keyup', elem.triggerHandler.bind(elem, 'change'));
  };
});

Fixed plnkr

@Narretz Isn't that a memory leak? You need a $destroy handler to remove the .on event handler.

The Chrome has been fixed: https://code.google.com/p/chromium/issues/detail?id=415505

Wrt the Firefox behavior, we have to accept that this is a browser quirk that must be fixed by Firefox, or worked around as specified. I have added a note in the select docs (https://github.com/angular/angular.js/commit/dcc57f1718b1b52a22ad833de4d093bcb418064b) and will close this issue.

sdsa


Move to iOS 13 navigation bar appearance API?

I gave a shot at the new iOS 13 appearance API. For the moment I could not manage to animate solid color changes (the background color does not change, while the foreground color changes as expected).
For the moment I will keep the old approach for iOS 13+. I've wasted enough time.
Some articles:

A great overview and another one.
Removal of the separator.
A two part article: 1 and 2.
Another article.

Assigned to version 3.2.0. Will probably be made as part of hero stage implementation, now that our deployment target has been set to iOS 14.

Updating the navigation bar appearance immediately (i.e. without forcing the navigation to reappear) requires a trick to force the navigation controller to consider applying appearance settings again.
Moreover there is no API to customize the foreground icon color. The old tintColor still works.

Available for review on feature/modern-navigation-bar.

Required for #180 and implemented on the dedicated branch.

Done.


Fix Marker leak

before

after

Description please? What kind-of leak is it?

The markers weren't getting cleaned up correctly.

@AsaAyers I still have no idea, but would you mind testing and merging it in and adding a changelog entry?


Bubble

Huh?

Sorry you’re going to be seeing a lot of changes.  I’m using zenhub to integrate with github for project management.  This issue is of type “epic” meaning a collection of issues, or a theme.  Any bugs, updates, additions, etc. that have to do with the bubble view will be linked to this issue/epic.
From: Tony Boyles @.>
Sent: Tuesday, March 23, 2021 11:28 AM
To: CDCgov/MicrobeTrace @.>
Cc: Moscoso, Evan (CDC/DDID/NCHHSTP/OD) (CTR) @.>; Author @.>
Subject: Re: [CDCgov/MicrobeTrace] Bubble (#323)
Huh?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/CDCgov/MicrobeTrace/issues/323#issuecomment-804997167, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATFBT2X632ICULKR2CCMNVDTFCXPHANCNFSM4ZTH32YQ.

Ah, gotcha. Thanks for clarifying!


How are props passed to the page?

Because I need to use navigation push in the page

Because I'm using this, I don't know how to pass it
IMPORTANT: Do not pass inline functions to SceneMap, for example, don't do the following:

SceneMap({
  first: () => <FirstRoute foo={this.props.foo} />,
  second: SecondRoute,
});

renderScene = ({ route, jumpTo }) => {
  switch (route.key) {
    case 'first':
      return <FirstRoute jumpTo={jumpTo} foo={this.props.foo} />;
  }
};

@satya164 Thank you very much ~!!


Make project cost as mandatory

https://tracker.micro-labs.in/project-tracker
Project Costs as mandatory. Put usual validation like costs as the number
Change the label name to Cost in Rs.

Done added Decimal validation too

Done


CocoaPods support

it would be cool to add CocoaPods support

Thanks for suggestion I will surely work on it.


RFP - nheko-reborn

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://github.com/Nheko-Reborn/nheko
Direct download URL for the software / installer : https://github.com/Nheko-Reborn/nheko/releases/download/v0.8.2/nheko-v0.8.2-installer.exe
Software summary / short description: live updated fork for https://community.chocolatey.org/packages/nheko/<IP_ADDRESS>4-nightly

A package nekho-reborn has been pushed and is going through review.

nheko-reborn package is now available.

@dgalbraith thank you.,

ERROR: Running ["C:\ProgramData\chocolatey\lib\nheko-reborn\tools\nheko-v0.8.2-installer.exe" --accept-licenses --confirm-command install ] was not successful. Exit code was '1'. See log for possible error messages.
The upgrade of nheko-reborn was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\nheko-reborn\tools\chocolateyInstall.ps1'.
See log for details.

logger.txt

Hi @AdmiringWorm  @BrandonKMLee,
I took a look at this issue, and the following Chocolatey package, maintained by @dgalbraith, is available and seems up to date with the releases of nheko. :slightly_smiling_face:

Thanks @Xav83 for updating this and letting us know!


Ability to filter columns of Vaults section

Add a way for users to click on column names (on https://yearn.finance/vaults) to filter them by ascending or descending order. Use case: filter vaults by the highest Growth first.

This was addressed in PR #181


Invalid server response (expected JSON, got garbage) for some API calls with Firefox/Chrome

v2.2.2-rc8
What kind of request is this (question/bug/enhancement/feature request):
Bug
Note: This doesn't really seem to hurt anything in the UI; however, it may be worth looking into at some point to identify the nature of the problem
This issue only shows an example with OpenLDAP but ALL other auth providers are affected. In order to keep this issue short we only included an example with OpenLDAP since these all appear related we get basically the same results for each area
Use Firefox only for all tests and keep dev tools open watching http, other browsers are ALSO AFFECTED but do not provide the same issues as seen in screenshots
For example Chrome will just mention "Failed to load response data" for invalid json server response payloads
Steps to reproduce (least amount of steps as possible):

Enable OpenLDAP Auth
Disable access control

Result:
When Enable OpenLDAP you will see these headers and this bad response from the server:
(happens in all, v2.1.8, v2.2.2-rc7 and v2.2.2-rc8)
This is presumably happening because we are sending application/json but with a Content-Length of zero however we don't see that issue when we disable auth as seen in the below screenshots

When Disable OpenLDAP you will see these headers and this non-json response from the server:
We get this for v2.1.8 and v2.2.2-rc7:
(notice response is null with content-length of zero)

and we get this for v2.2.2-rc8:
(notice response is not null with content-length of 23)

Other details that may be helpful:
These differences between v2.1.8/v2.2.2-rc7 and rc8 are due to #19490
Again, nothing in the UI seems to break and we don't see errors in the UI this is just something we thought was odd when testing rancher/rancher#19490  and rancher/rancher#19508  by smoke testing the UI in various areas.

Based on a discussion in Slack this is probably out of scope and should be moved out, but it is only happening in v2.2.2-rc8 - essentially what has changed is our server response when we disable auth and change passwords but it doesn't seem to break anything or hurt the UI.
It may be worth investigating later.

A separate issue has been created to track pwd change having incorrect Content-Type: #19553

@davidnuzik could this be closed?

@cjellick If we do not wish to fix the issue then yes. I do not consider it a priority or a must-fix.
It's more of an inconvenience and inappropriate way of sending a server response, but doesn't seem to hurt anything other than possibly in very edge cases with testing/troubleshooting.

Version: Master (v2.3) (6/7/19)
I can confirm that a proper Content-Type header is now sent in server response when disabling auth. This resolves the issue. Reference https://github.com/rancher/rancher/pull/19526


unsupported operand type(s) for -: 'list' and 'frozenset'

Hello.
I got this exception when I set 'include' option  (ex. include: ['tap', 'brew', 'cask']).
Without this option, it works correctly.

@brownerk please, send help 😄
PRs are welcome.


How can i use two redis Client in one handdler?

How to do it? The Map() function just map one *redis.Client
   app.Group("/detail", func(r martini.Router) {

        r.Get("", binding.Form(controllers.DetailForm{}), controllers.Detail)

    })

you can make something like:
type RedisClients struct {
       Foo *redis.Client
       Bar *redis.Client
}

and then map an instance of that type instead

Thank you， is't useful!


Node images become invisible on certain zoom levels

Here is one difficult to reproduce bug, I think. I got this bug report in StreetComplete.
In a nutshell: Images for nodes (with collision on) turn invisible on certain zoom levels even though there doesn't seem to be anything in the way that would warrant a collision.
https://files.natenom.com/public/cs/a_1.png
https://files.natenom.com/public/cs/a_2.png
(More images and GPS positions in the linked ticket)
The markers in this app are just another data layer, their theme is declared here:
https://github.com/westnordost/StreetComplete/blob/master/app/src/main/assets/streetcomplete.yaml
The reporter uses a Samsung Galaxy S5. I cannot reproduce it with a Sony Xperia Z1 Compact, Android 5.1.1

The user had the courtesy to make a screencast to better illustrate the problem:
https://files.natenom.com/public/cs/cs.mp4

Hmm, I am getting feedback from quite a few users that they have the same problem as the original bug reporter. Here is the link of the original ticket again: https://github.com/westnordost/StreetComplete/issues/50
Do you acknowledge that this is a bug in tangram-es?

Hi @westnordost, I'll take a closer look at this. Which version(s) of tangram-es are you seeing this with, and on what devices?

Have you tried to set the quest-icons priority to zero so that they don't get blocked by other labels?

@matteblair Hmm, I think I get this independent of the device
@hjanetzek Oh, no, I haven't used the priority at all yet. I also just read this note in the docs

[JS only] Only points and text elements from the same datasource will collide with each other, so priority values only apply within a single datasource.

I will try this and report back.

@westnordost just tried building StreetComplete with priority: 0 set for the streetcomplete_quest layer. Seems to give much better results, as the the quest icons are not colliding with other street labels.
streetcomplete_quests:
        filter: { $zoom: { min: 14 } }
        data: { source: streetcomplete_quests }
        draw:
            quest-icons:
                interactive: true
                priority: 0
                size: 64px
                sprite: function() { return feature.kind }
                sprite_default: quest
                offset: [-16px, -64px]

I also tested it myself now. This does the trick. Cool, thank you for your help and pointing out that it was in fact not a problem of tangram-es but of my style :-)
One point though: The style of quest-icons includes
blend: overlay
blend_order: 1

Is it expected behavior that this does not influence collision? If yes, feel free to close this ticket.

@westnordost Also I noticed in the cinnabar-style-4.0.0.yaml you are importing is an old one which explicitly specified an API key (key is not assigned to StreetComplete, and might get deprecated soon), can you update cinnabar-style-4.0.0.yaml to remove this api key?

Sure, I will do it for the next update.

@westnordost blend_order will affect ordering of features drawn using styles using overlay blending. This is because we can not rely on z buffer ordering for feature drawn with overlay blending.
As an example you can refer to how we use it in here.
Also closing this issue.


Panic occurred at runtime.

System Info
System:
OS: Windows 10 10.0.19045
CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Memory: 4.15 GB / 15.95 GB
Binaries:
Node: 16.20.2 - C:\Program Files\nodejs\node.EXE
npm: 8.19.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 120.0.6099.110
Edge: Spartan (44.19041.3636.0), Chromium (120.0.2210.77)
Internet Explorer: 11.0.19041.3636
npmPackages:
@rspack/cli: ^0.4.3 => 0.4.3
@rspack/core: ^0.4.3 => 0.4.3
@rspack/plugin-html: ^0.4.3 => 0.4.3
@rspack/plugin-node-polyfill: ^0.4.3 => 0.4.3
Details
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: httpscom/web-infra-dev/rspack/issues
Message:  byte index 382 is not a char boundary; it is inside '色' (bytes 380..383) of  e,t,a)=>{Object.defineProperty(t,"__esModule",{value:!0}),t.ProgressPlugin=void 0;var n=a9756),i=a(9933),o=a(9547),r=function(e){function t(){var t=null!==e&&e.apply(this,argumenreturn t.rendererName="progress",t.$schema="/sc[...]
Location: C:\Users\Administrator.cargo\registry\src\index.crates.io-6f17d22bba15001f\mie\src\handlers\graphical.rs:640
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1: napi_register_module_v1
at
2: napi_register_module_v1
at
3: napi_register_module_v1
at
4: napi_register_module_v1
at
5: napi_register_module_v1
at
6: napi_register_module_v1
at
7: napi_register_module_v1
at
8: node::Stop
at
9: v8::internal::Builtins::code_handle
at
10: v8::internal::Builtins::code_handle
at
11: v8::internal::Builtins::code_handle
at
12: v8::internal::Builtins::code_handle
at
13: v8::internal::SetupIsolateDelegate::SetupHeap
at
14: v8::internal::SetupIsolateDelegate::SetupHeap
at
15: v8::internal::SetupIsolateDelegate::SetupHeap
at
16: v8::internal::SetupIsolateDelegate::SetupHeap
at
17: v8::internal::SetupIsolateDelegate::SetupHeap
at
18: v8::internal::SetupIsolateDelegate::SetupHeap
at
19: v8::internal::SetupIsolateDelegate::SetupHeap
at
20: v8::internal::SetupIsolateDelegate::SetupHeap
at
21: v8::internal::SetupIsolateDelegate::SetupHeap
at
22: v8::internal::SetupIsolateDelegate::SetupHeap
at
23: v8::internal::SetupIsolateDelegate::SetupHeap
at
24: v8::internal::SetupIsolateDelegate::SetupHeap
at
25: v8::internal::SetupIsolateDelegate::SetupHeap
at
26: v8::internal::SetupIsolateDelegate::SetupHeap
at
27: v8::internal::SetupIsolateDelegate::SetupHeap
at
28: v8::internal::SetupIsolateDelegate::SetupHeap
at
29: v8::internal::SetupIsolateDelegate::SetupHeap
at
30: v8::internal::SetupIsolateDelegate::SetupHeap
at
31: v8::internal::SetupIsolateDelegate::SetupHeap
at
32: v8::internal::Execution::CallWasm
at
33: v8::internal::Execution::Call
at
34: v8::Function::Call
at
35: napi_call_function
at
36: node_module_register
at
37: node_module_register
at
38: uv_async_send
at
39: uv_loop_init
at
40: uv_run
at
41: node::SpinEventLoop
at
42: cppgc::internal::Marker::visitor
at
43: node::Start
at
44: RC4_options
at
45: v8::internal::compiler::RepresentationChanger::Uint32OverflowOperatorFor
at
46: BaseThreadInitThunk
at
47: RtlUserThreadStart
at
Reproduce link
No response
Reproduce Steps
havnt found which file trigger this

0.3.14 is ok  0.4.0 not work

Would you please try this version 0.4.5-canary-b3497fe-20231227113840?

works fine in v0.5.1

Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message: Module(/Users/doorgod/Desktop/www/AbcPc/node_modules/sax/lib/sax.js) should be added before using
Location: crates/rspack_core/src/chunk_graph/chunk_graph_module.rs:75
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
Accidental phenomena, why?

Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message: Module(/Users/doorgod/Desktop/www/AbcPc/node_modules/sax/lib/sax.js) should be added before using
Location: crates/rspack_core/src/chunk_graph/chunk_graph_module.rs:75
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
Accidental phenomena, why?

This issue has been resolved. Please file a new one instead.


type may not be an array

The documentation states:
You can also set the schema key to an array of some type:
{ friends: [String], }
but lib/SimpleSchema.js [737] contains:
if (Array.isArray(type)) {
  throw new Error(`Invalid definition for ${fieldName} field: "type" may not be an array. Change it to Array.`);
}

Are typed arrays only allowed for shorthands in 2.x? I'm using SimpleSchema.oneOf and one of the options is a typed blackbox array.

I have the same problem... is this planned to be fixed soon? We are currently attempting to migrate from the Simple Schema meteor package to the npm  module...

Types can be an array. The syntax has changed.
It's now
// long hand
const arraySchema = new SimpleSchema({
  imAnArray: {
    type: Array
  },
  'imAnArray.$': {
    type: String
  }
})

// short hand
const arraySchema = new SimpleSchema({
  imAnArray: Array,
  'imAnArray.$': String
})

having same issue, using bracket "[]" in type is not working.

Did you read my comment?

The syntax hasn't changed, but the type: [Type] shorthand that worked in v1 has been removed. It caused way too much confusion. Forcing everyone to be explicit about what they are defining seems the better approach. I did add the even shorter shorthand for arrays, as documented, but maybe that will turn out to be too confusing for people, too. :)

Hi @clayne11 , i did read your comment, the new way force us to add in a lot of codes.
Hi @aldeed, new shorthand is great and easy to understand.
And v1 was great too and it doesn't confusing for me. It saved me a lot of time when i want to reference or extend Array type.
eg what i can do on v1
company : {
  branches: [branchSchema]
}

instead of now we have to do
company : {
  branches: Array,
  "branches.$": branchSchema
}

+1 @chongwang87
@aldeed the square bracket notation was very straight forward for me as well.
Btw, @aldeed BIG thx for all your hard work on these open source projects!

here is it.
import SS from 'simpl-schema'

SS.extendOptions(['autoform']);
SimpleSchema = class extends SS {
	constructor(schema) {
		Object.keys(schema).forEach(k => {
			if(schema[k].type instanceof Array) {
				const type = schema[k].type[0];
				schema[k].type = Array;
				schema[k+'.$'] = {type}
			}
		})
		super(schema);
	}
}

I'm running into an issue when I attempt to import a Schema and use it as a type for an array field:
Inside my project.js file:
import TestSchema from './tests.js';
...
tests: Array,
"tests.$": TestSchema,

Returns
Error: tests.$ key is missing "type"

I can get past this problem by putting the TestSchema within the project.js file. Is there a way I can make this import work. It seems to be working for the following field:
import TemplateSchema from './templates.js';
....
template: {
		type: TemplateSchema
	},

But then I ask you to update the documentation ... https://github.com/aldeed/node-simple-schema#more-shorthand still states:

You can also set the schema key to an array of some type:
{
  friends: [String],
}

is equivalent to:
{
  friends: { type: Array },
  'friends.$': { type: String },
}

@aldeed Please update the documentation
Because when I switch from v1, I've lost a lot of time to find and fix!

@zhanbst, @sebastianconcept Please vote for it: https://github.com/aldeed/node-simple-schema/pull/167

Sincerely and with all my respects for this AWESOME package (including collection2 and AutoForm):

Upgraded my project.
Got lots of errors reffered to [Object], [String] and any [*] declarations in my schemas.
Found this issue.
Fixed errors using this (IMHO, horrible) syntax.
Found problems with optional: true not working with this syntax. Doesn't matter if I set the option in the parent (i.e: books) field, in the child (i.e: books.$) field or both. It always fails with an Errror: 1 is required (not even showing the field name!).
Gave up and downgraded my project back to old versions.

It's easier to remain in the old versions and have only critical fixes than moving to the new versions. Even if you're starting a new project.
Also, having some dependencies as NPM packages and others as Meteor packages gives you that weird feeling that something is going to break at any moment.

I agree the [] notation for array types was incredibly straight forward.
This new approach is less appealing IMO.
@aldeed Would you accept a pull request to support both? I have not looked at it so I do not know if these is event possible, but I would personally would like this new version to be backward compatible ideally if that is at all possible.

I completely understand the frustration, but it's not feasible or wise to get back the old behavior. Its simplicity masked a lot of potential for confusion. We will all get used to the new way eventually.
As for general complaints about the trickiness of upgrading, (1) I could create a schema upgrade tool to do some of it automatically, and (2) specific individual issues about confusion you are having would be more helpful than general complaints.


Refine upload, network and add subtrack feature

:pushpin: References

Issue: Closes Refine upload, network and add subtrack feature

:memo: Implementation

Just some small stylistic things to make all the forms consistent: making labels bold, marking all required fields instead of just showing optional, increase Dropzone height, error message styling, popup title should only be capitalized for the first letter, homogenous error messages, clearing errors when going between annotation toggles

:art: Screenshots

:fire: How to test it? (If there is any special consideration or the reviewer does not know how to test it)
:bookmark_tabs: Others

[ ] Any change in the API repo? If so, what branch/PR?
[ ] Any change in the GUI library? If so, what branch/PR?

Thanks @jvfdunkley! Everything looks good. I am merging this into the other branch so @tokland just review everything in a single branch


Legal: Check the right to distribute

Hi,
I believe that you need to check the legality of what you are attempting to do here.
The author of a software must have given you the permission to (re)distribute it for you to be allowed to do that. Independent of your intention, I believe that the Zoom license does not contain such permission.

There are many unofficial projects which redistribute Zoom such as the snap, the flatpak, and the AUR package. I asked them about it in 2022 and they were very supportive.
The Pop! OS nonfree repo does a cool thing where they redirect to original download links instead of serving the files themselves. I could pivot to that if Zoom changes their stance.