Call for maintainers

Hi y'all - I totally missed a ton of issues & PRs, I didn't think ppl were using this!
Would love to add some more people as maintainers - lmk if you're interested <3

@chrisdrackett any chance we could get a release of #66? Trying to spin up @anselmdk as a maintainer; I forgot that you had ownership of the npm package ❤
(also potentially do you wanna give him npm permissions?)

I'll see what I can do on a release, I would need to remember the process as it has been a while. In the meantime I can share the NPM load asap.

@anselmdk what is your npm username?

@chrisdrackett it's https://www.npmjs.com/~anselmdk

@chrisdrackett awesome, thanks!
I guess It's basically running yarn release (see https://github.com/jemgold/figma-js/blob/main/package.json#L37)
@jemgold if you add me as a maintainer (write permissions) to the GitHub repo, I could give it a shot!

if I remember you might have to run prepare-release first.. its been a while. I might be able to get on my computer later today, but at the moment I'm phone only

prepare-release should be part of running yarn release.
yarn release runs the following: yarn prepare-release && yarn publish && git push && git push --tag

@jemgold / @chrisdrackett I'd be happy to give it a try, I'd just need one of you to give me write access to the GitHub repo.

Pinging @jemgold & @chrisdrackett re: @anselmdk's requests for help getting a new npm version published

I don't have any permissions so I think this is fully on @jemgold

missed these notifications, sorry! invited @anselmdk, lmk if there's anything else you need. you have npm access right?
feel free to go wild and do whatever you want with this repo @anselmdk! also i'm open if there's a community organization we could transfer this repo to (maybe even just figma? cc @rogie @jordansinger etc) - i'm not working in tech anymore so i'm very rarely on github or checking the associated inboxes

I can confirm I now have write access and also npm access, thanks @jemgold and @chrisdrackett!
I'll try giving it a shot releasing a new version over the weekend.

Okay, so I just published a pre-release. I hope I did everything well, I apologize in advance, as I've never published anything using yarn before. Also it seems the last publishing has been done on yarn 1.x where the current version of yarn is on 4.x.
I used the latest version of yarn.
Once we can confirm everything works, I propose to clean up dependencies and streamline the release process. For now I've created the following commit and published the pre-release to npm:
https://www.npmjs.com/package/figma-js/v/1.16.1-0
It seems that this is how yarn creates pre-releases, I hope it's not being picked up yet by anyone installing figma-js.
This is what I did to make it work:
#logging into npm
yarn npm login

#creating the pre-release
yarn version prerelease

#running the release
yarn release

#committing and pushing changes
git commit
git tag v1.16.1-0
git push --tag

I'd love for someone to try installing 1.16.1-0 and see if it works. If that's the case, I'll publish an actual release. Probably 1.17.0. I actually wanted to create a pre-release for it, but couln't figure out how to do that using yarn.

@anselmdk It's hard to be 💯 sure, but I believe this worked!
I updated the two places a dependency used figma-js to the new 1.16.1-0, and re-ran npm install. That updated the axios from ^0.21.0 to ^1.6.0. I then re-ran the scripts which use the affected dependency and everything worked as expected
here's the changed package-lock.json

diff --git a/package-lock.json b/package-lock.json
index a870848a..77f20409 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -3831,7 +3831,7 @@
       "dependencies": {
         "@figma-export/types": "^4.8.0",
         "axios": "^1.6.7",
-        "figma-js": "~1.16.0",
+        "figma-js": "1.16.1-0",
         "p-limit": "^3.1.0",
         "p-retry": "^4.6.2"
       },
@@ -3904,7 +3904,7 @@
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "figma-js": "~1.16.0"
+        "figma-js": "1.16.1-0"
       },
       "engines": {
         "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
@@ -16308,24 +16308,17 @@
       "license": "MIT"
     },
     "node_modules/figma-js": {
-      "version": "1.16.0",
+      "version": "1.16.1-0",
+      "resolved": "https://registry.npmjs.org/figma-js/-/figma-js-1.16.1-0.tgz",
+      "integrity": "sha512-4yA1PJOAnFBp8V26nEikzsBz4E6KZtdIGg6EMiqnFr2x5x2ehZy70MadFQOc/wnyPDvorqvN6eH8b7IfmUqIRQ==",
       "dev": true,
-      "license": "MIT",
       "dependencies": {
-        "axios": "^0.21.1"
+        "axios": "^1.6.0"
       },
       "engines": {
         "node": ">=8.9"
       }
     },
-    "node_modules/figma-js/node_modules/axios": {
-      "version": "0.21.4",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "follow-redirects": "^1.14.0"
-      }
-    },
     "node_modules/figures": {
       "version": "3.2.0",
       "license": "MIT",

@Sidnioulz would you like to be a maintainer here to help out?

@chrisdrackett happy to lend a hand with OpenAPI codegen, though, I'm not sure I want to maintain an extra project, as I maintain my own REST client already and have several ongoing projects. I'd like to contribute in a capacity that does not involve recurring work :sweat_smile:
Happy to have a chat about it, though. Are there other people who are currently willing to put in hours in figma-js?

💖💖 thanks for the updates - i haven’t been tracking this project or the figma API for a while. i’m down to do whatever the community feels is best - would it break a lot of things if we deprecated this package?
On Sat, Nov 2, 2024 at 10:39 AM, Steve Dodier-Lazaro @.***(mailto:On Sat, Nov 2, 2024 at 10:39 AM, Steve Dodier-Lazaro < wrote:

@.***(https://github.com/chrisdrackett) happy to lend a hand with OpenAPI codegen, though, I'm not sure I want to maintain an extra project, as I maintain my own REST client already and have several ongoing projects. I'd like to contribute in a capacity that does not involve recurring work 😅
Happy to have a chat about it, though. Are there other people who are currently willing to put in hours in figma-js?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Deprecating in NPM does not break things. People can continue to use the deprecated package, but they get a warning and you can show a message with alternative options. See https://docs.npmjs.com/deprecating-and-undeprecating-packages-or-package-versions.
Now that Figma request versioned APIs, all codegen tools would give you methods like v1.getFiles or v1GetFiles, so you'd need an extra investment in codegen to produce an API that matches the names you currently have. You would also likely have breaking changes in TypeScript types. So, if you do adopt codegen and continue to maintain figma-js, you would probably need to release a major version.
I started my own client because I realised some endpoints around variables were missing for a project I had, and I didn't have the courage to manually scour through the Figma API and find missing methods to offer a PR.
I found it easier to start from a clean slate, and codegen tools are all or nothing; it takea a lot more work to map the API to an existing coding style than to delegate the naming of methods and parameters to the codegen tool.
 I suppose they are the best placed to answer the question of how to proceed :)


[Feature Request]: Breadcrumb component

Is your feature request related to a problem? Please describe
Currently in the Early Childhood Development System portal (Child Care Portal), there are a could different services (accessed through the sidenav) which feature breadcrumbing on their respective pages. Each breadcrumb patter is different. We will soon want all the services in this portal to utilize a consistent breadcrumb component/pattern.
Describe the solution you'd like

Would like to see a GoA breadcrumb component which can go down to at least 5 to 6 page levels
Works on desktop/tablet and mobile breakpoints
Is fully accessible
Accounts for position/padding in relation to page templates or this first item of content below the breadcrumb on a page
All states for the active links and active page in the breadcrumb
Some guidelines around breadcrumb label character length and recommended naming convention if possible (brevity and matching the page title and considerate of the url if possible)

Provide evidence this is a needed component
Currently 3 of 6 Child Care Services in the Early Childhood Development System portal utilize breadcrumbing and all use a different pattern treatment. All services in the portal will use breadcrumbing in early 2024. Consistency is key as this is a single portal for our external users.
The Design System team is already exploring breadcrumb component for their Design System website.
https://www.figma.com/file/Vw1LNUBsNeFkToPTWqXAzR/Component---Breadcrumb?type=design&node-id=1401-3285&mode=design&t=7I1OkZM3WExILE2j-4

Describe alternatives you've considered
Good article which may provide helpful when mapping out the component and it's guidelines: https://www.smashingmagazine.com/2022/04/breadcrumbs-ux-design/
Do you have anything already created for this that we can use?
yes
Are you currently using this proposal inside your own service
yes
Are you able to assist to bring the feature to reality?
yes
Additional context
Here are some live breadcrumb examples from ECDS portal

Hi @ArakTaiRoth do you need more context/info from me? Cheers

Land Titles Office has a component designed and in development for this:
Figma
Design guidelines
Development blueprint
Service designer: @garnison-goa
Development
Developer: Daryl Chiew

@Spark450 Gather the relevant info and convert into a design issue

This needs to have a complete design definition before it can be worked on in development, see Jira Issue to follow its progress. A new issue will be created once the design work has been completed.


Go indexer: Add interface satisfaction edges. [phab:D1422]

Created by fromberger at 2017-03-11 01:50:19:
Pending the outcome of #1822, this change adds X extends Y edges between named
types X and Y such that X is assignable to Y and Y is an interface.
Also: Add an external package rule for the typeutil package.

fromberger wrote at 2017-03-11 01:57:59:

Clean up some leftovers from debugging.

shahms accepted this revision at 2017-03-13 16:14:33

fromberger closed via commit 8c43dc25ad4ff6211116f92cf0d84dad920a874b at 2017-03-13 17:49:05


Iam roles names are added as hardcoded into the main.tf

Description
We have setup a DMS for multiple folders and each folder should deal with different RDS(s) with different DMS endpoints, the first folder apply went successfully as the terrarform create roles in aws with names dms-access-for-endpoint, and dms-cloudwatch-logs-role. while applying the second folder the terraform produced an conflict error that the iam roles are already existing although we're already passing the access_iam_role_name with a value and access_iam_role_use_name_prefix is already equal true
Here the exact error
│ Error: creating IAM Role (dms-access-for-endpoint): operation error IAM: CreateRole, https response error StatusCode: 409, RequestID: f80e800a-673e-4ec2-a7fd-032055c61c73, EntityAlreadyExists: Role with name dms-access-for-endpoint already exists.
│
│   with aws_iam_role.dms_access_for_endpoint[0],
│   on main.tf line 80, in resource "aws_iam_role" "dms_access_for_endpoint":
│   80: resource "aws_iam_role" "dms_access_for_endpoint" {
│
╵
╷
│ Error: creating IAM Role (dms-cloudwatch-logs-role): operation error IAM: CreateRole, https response error StatusCode: 409, RequestID: bd90c51c-6e63-4b75-9de2-7f180b963c69, EntityAlreadyExists: Role with name dms-cloudwatch-logs-role already exists.
│
│   with aws_iam_role.dms_cloudwatch_logs_role[0],
│   on main.tf line 94, in resource "aws_iam_role" "dms_cloudwatch_logs_role":
│   94: resource "aws_iam_role" "dms_cloudwatch_logs_role" {
│
╵
╷
│ Error: creating IAM Role (dms-vpc-role): operation error IAM: CreateRole, https response error StatusCode: 409, RequestID: 5955f20d-a5b3-459c-9fbf-cc9234213fc9, EntityAlreadyExists: Role with name dms-vpc-role already exists.

What is expected
We expected that the IAM Roles should be differ once we're already passing the required inputs such like access_iam_role_name and access_iam_role_use_name_prefix
Steps to reproduce the behavior
We've found that the names are adding as hardcoded and the prefix is not working such like it shows in the below block
resource "aws_iam_role" "dms_access_for_endpoint" {
  count = var.create && var.create_iam_roles ? 1 : 0

  name                  = "dms-access-for-endpoint"
  description           = "DMS IAM role for endpoint access permissions"
  permissions_boundary  = var.iam_role_permissions_boundary
  assume_role_policy    = data.aws_iam_policy_document.dms_assume_role[0].json
  managed_policy_arns   = ["arn:${local.partition}:iam::aws:policy/service-role/AmazonDMSRedshiftS3Role"]
  force_detach_policies = true

  # https://github.com/hashicorp/terraform-provider-aws/issues/11025#issuecomment-660059684
  provisioner "local-exec" {
    command = "sleep 10"
  }

  tags = merge(var.tags, var.iam_role_tags)
}

# DMS CloudWatch Logs
resource "aws_iam_role" "dms_cloudwatch_logs_role" {
  count = var.create && var.create_iam_roles ? 1 : 0

  name                  = "dms-cloudwatch-logs-role"
  description           = "DMS IAM role for CloudWatch logs permissions"
  permissions_boundary  = var.iam_role_permissions_boundary
  assume_role_policy    = data.aws_iam_policy_document.dms_assume_role[0].json
  managed_policy_arns   = ["arn:${local.partition}:iam::aws:policy/service-role/AmazonDMSCloudWatchLogsRole"]
  force_detach_policies = true

  # https://github.com/hashicorp/terraform-provider-aws/issues/11025#issuecomment-660059684
  provisioner "local-exec" {
    command = "sleep 10"
  }

  tags = merge(var.tags, var.iam_role_tags)
}

Don't we need to keep the names in the resources to be variable ?

I would suggest reading through the docs https://docs.aws.amazon.com/dms/latest/userguide/security-iam.html#CHAP_Security.APIRole


Adding MulticastAppDelegate

This will be a feature branch after this PR approval, this PR just mimics the oiginal implementation: https://github.com/google/GoogleUtilities/pull/50.
I will check out subbranch from here to continue work on SceneDelegate support for auth and UNUserNotificationCenterDelegate for messaging

Yep, will do a series of more PRs to the feature branch so this one won't get large.


Velocity Compatibility

Describe the Bug
Loading into a Velocity server network with Create causes an exception in the netty pipeline.
Reproduction Steps

Install the Create mod.
Attempt to load into a Velocity server.
Receive the error.

Expected Result
I expected to load into the proxy server and get redirected to a Paper 1.19.4 server (with ViaVersion). This was not the case.
Screenshots and Videos
No response
Crash Report or Log
https://gist.github.com/UnperishedDev/816525e4d0c5a0d6b1aa75df65f390e5
Operating System
Windows 11
Mod Version
0.5.0i
Minecraft Version
1.19.2
Other Mods
A lot of other mods (77 others).
Additional Context
No response

joining a paper server with Create installed is not going to work, is not supported, and will not be fixed. If there's still an issue when connecting to a fabric one, it may be looked into, but I haven't heard good things about velocity compat with mods.

especially when the server is using 1.19.4 and Create is on 1.19..2


Slider percentage set to NaN% and not working after HA restart

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
**Last working release (if known):N/A
**Home Assistant version :Home Assistant 0.118.4
**Browser and Operating System:edge- W10 and also Safary on IOS mobile with HA app

Description of problem:
Sliders percentage set to NaN% and sliders not working after HA restart

**Javascript errors shown in the web inspector (if applicable):N/A

Additional information:

Did you check if your cover have position attribute after Hass start? Your issue could be related to how Hass not preserve entity's state among restart.

Yes, you’ right, and I’m looking for a solution for this, the problem is if I don’t activate shutters first manually or using standard HA card, the sliders don’t work at all. You can imagine I would not have two cards on my Lovelace. By the way your sliders are perfect for my purpose, even the customizing options. Thank you for supporting.


Scanner Enhanced Logging

Time Tracking: MA-74
This is done when:

[x] Invalid user logged to S3 for Scanner v2
[x] Invalid user logged to S3 for Scanner v3

[ ] ScanData Enhanced Logging Test Plan PASS in QA

Encountered a bug in testing

Scanner not always writing log to S3

Reproduced in production


Add u128_to_reversed_u64s.

This change is

tests/e2e_test_data/libfuncs/u128 line 730 at r1 (raw file):

[ap + 0] = [ap + -5] + [ap + -1], ap++;
[ap + 0] =<PHONE_NUMBER>7927936, ap++;
[ap + 0] = [ap + 0] * [ap + -1], ap++;

@orizi
This seems to be a bug.
it is supposed to be:
[ap + k] = [ap + (k-1)] * ...
for some k (maybe 0).
https://github.com/starkware-libs/cairo/blob/0d05e3b82e4c63714d5580e22aa01103a4087e20/crates/cairo-lang-sierra-to-casm/src/invocations/uint128.rs#L408
Code quote:
[ap + 0] = [ap + 0] * [ap + -1], ap++;

tests/e2e_test_data/libfuncs/u128 line 730 at r1 (raw file):
Previously, ilyalesokhin-starkware wrote…
@orizi
This seems to be a bug.
it is supposed to be:
[ap + k] = [ap + (k-1)] * ...
for some k (maybe 0).
https://github.com/starkware-libs/cairo/blob/0d05e3b82e4c63714d5580e22aa01103a4087e20/crates/cairo-lang-sierra-to-casm/src/invocations/uint128.rs#L408

nvm, the issue is with:
https://github.com/starkware-libs/cairo/blob/0d05e3b82e4c63714d5580e22aa01103a4087e20/crates/cairo-lang-sierra-to-casm/src/invocations/uint128.rs#L421

crates/cairo-lang-sierra-to-casm/src/invocations/uint128.rs line 390 at r2 (raw file):
Previously, orizi wrote…
won't this be just as efficient in user code?

What type would you use for temp?
A felt can't be assigned to bitwise safely, and u251 would add range checks.

Previously, orizi wrote…
this is really little work:
fn foo(mut a: u128) -> (u64, u64) {
let mut v1: u64 = 0;
let b: u64 = a % 256; a /= 256; v1 *= b;
let b: u64 = a % 256; a /= 256; v1 *= 256; v1 += b;
let b: u64 = a % 256; a /= 256; v1 *= 256; v1 += b;
let b: u64 = a % 256; a /= 256; v1 *= 256; v1 += b;
let b: u64 = a % 256; a /= 256; v1 *= 256; v1 += b;
let b: u64 = a % 256; a /= 256; v1 *= 256; v1 += b;
let b: u64 = a % 256; a /= 256; v1 *= 256; v1 += b;
let b: u64 = a % 256; a /= 256; v1 *= 256; v1 += b;
let mut v2: u64 = 0;
let b: u64 = a % 256; a /= 256; v2 *= b;
let b: u64 = a % 256; a /= 256; v2 *= 256; v2 += b;
let b: u64 = a % 256; a /= 256; v2 *= 256; v2 += b;
let b: u64 = a % 256; a /= 256; v2 *= 256; v2 += b;
let b: u64 = a % 256; a /= 256; v2 *= 256; v2 += b;
let b: u64 = a % 256; a /= 256; v2 *= 256; v2 += b;
let b: u64 = a % 256; a /= 256; v2 *= 256; v2 += b;
let b: u64 = a % 256; a /= 256; v2 *= 256; v2 += b;
(v1, v2)
}
of course it is a lot less efficient - but let get to the target before we start implementing stuff that we need to make actual decisions on.

it gives me
error: Unexpected argument type. Expected: "core::integer::u64", found: "core::integer::u128".
--> keccak.cairo:108:18
let b: u64 = a % 256;
^*****^
I might be able to make it work, but I think it is a waste of time.

Previously, orizi wrote…
you'd just need to add .into()

it didn't compile and I don't want to fight with it.
lior said we should add the libfunc.


Set Up Log In

https://dzone.com/articles/login-with-facebook-and-google-using-angular-8

https://medium.com/@fraxool/add-facebook-login-to-your-ionic-3-app-the-step-by-step-guide-88879e391a3b

https://docs.microsoft.com/de-de/aspnet/core/security/authentication/social/facebook-logins?view=aspnetcore-3.1

https://medium.com/@syuraj/how-to-use-facebook-to-login-users-and-authenticate-in-backend-bc26e22c7d45

https://github.com/dotnet/aspnetcore/issues/6486


[Bug]: High CPU usage

OS
Windows
App Version
v0.4.1
Description
Windows 11, CPU i7 7700k , webcam Logitech c925e
The software using the camera and sending VMC is using 65% of my CPU.
Even when webcam and VMC sender is off , the CPU usage this is 18 %.
It does not make sense to me. I have done the handtracking in mediapepi in python and my usage was lower than 10%.
Maybe an option to change de model complexity, mine was 0 and working on the hands.

extras issues:

cannot get nice performance when using webcam with higher resolution than 848x480 (30hz) (becames choppy)
cannot set webcam to use 60 fps.
Bones configuration are lost at restart of program

Logs
No response

I’m currently using model complexity 1 for the tool. This is a feature I really want to add! I can add this for the next version.
This tool performs better with lower camera resolutions (You could even try 140p). I wrote a small optimization guide: https://github.com/Kariaro/VRigUnity/wiki/Optimizing
The webcam fps will be limited by how fast the AI is. Higher resolutions makes the AI really slow.
Bone configuration will be fixed next version. The bone settings was experimental for a while.
One question:

Did you use mediapipe GPU in python or CPU?

Hello there, thank you for the quick response ! And for doing this project.
Just follow the guide, no sucess, this using 50% when tracking and 12% when doing nothing.
Try my code with model_complexity in 1 and still much lower usage.
I used the medipipe CPU. Below there is a zip with my code. Take a look at the section "Ignoring empty camera frame", it might fix the high usage when is not tracking.
HandTracking.zip
this code is almost the example they use on ther website.


Explore PomBase: Protein-coding gene characterisation status (rotation)

image
https://www.pombase.org/assets/gene_characterisation_status_figure.svg
Explore PomBase: Protein-coding gene characterisation status
The protein characterization graph is updated daily  https://www.pombase.org/status/gene-characterisation
Over half of fission yeast proteins are now published in small-scale experiments

That's done and on the main site.

Let's change the text to
Over half of fission yeast proteins are now published in small-scale experiments. 616 of unknown process, of which 356 are conserved outside fission yeast (126 to human)
I know it contains changing numbers but  so does the disease one, and it is date stamped.

How's this: https://desktop.kmr.nz/archive/explore

they are blank ;)

Sorry, that was problem with the dodgy setup on my desktop.  Fixed now although you might need to shift-reload.

Although over half of fission yeast proteins are now published in small-scale experiments, and the roles of a further >1900 can be inferred,  there are still 616 of unknown process, of these 356 are conserved outside the fission yeast, 126 as far as human.
is that better? (if room)

I think that's OK: https://desktop.kmr.nz/archive/explore
We can always tweak it later.

_Yep looks good
Val


Add more memory information

The /1.0/resources endpoint reveals a lot of information about the hardware, would it be possible to extend the memory details with the "version" (I.E "ddr4" / "ddr3") and the clock speed?
Feels abit empty without it;

I don't think that's possible. For the resources API we can only rely on things available in /sys, in this case:

/sys/devices/system/node
/sys/devices/system/memory

The memory type and clock speed isn't something that's directly known by the Linux kernel (or at least not exposed to userspace). On some platforms (those with suitable ACPI tables), you can pull that information through DMI but this won't work on architectures without ACPI and either requires calling out to dmidecode or implementing a binary parser to make sense of the raw DMI tables exposed by the kernel.


cPickle in expand_mnist.py ?!

I don't think cPickle should be imported in expand_mnist.py. Shouldn't it be pickle instead?

yes


Cannot Build for Android

I have a lot of other imports that work fine, but I get the follow error when I import get_ip. Any thoughts?

Error running Gradle:
ProcessException: Process "/Users/***/android/gradlew" exited abnormally:

Configure project :app
WARNING: API 'variant.getAssemble()' is obsolete and has been replaced with 'variant.getAssembleProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getAssemble(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variantOutput.getProcessResources()' is obsolete and has been replaced with 'variantOutput.getProcessResourcesProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variantOutput.getProcessResources(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variantOutput.getProcessManifest()' is obsolete and has been replaced with 'variantOutput.getProcessManifestProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variantOutput.getProcessManifest(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variant.getMergeResources()' is obsolete and has been replaced with 'variant.getMergeResourcesProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeResources(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeAssets(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variant.getPackageApplication()' is obsolete and has been replaced with 'variant.getPackageApplicationProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getPackageApplication(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variant.getExternalNativeBuildTasks()' is obsolete and has been replaced with 'variant.getExternalNativeBuildProviders()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getExternalNativeBuildTasks(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)

Configure project :get_ip
WARNING: API 'variant.getJavaCompile()' is obsolete and has been replaced with 'variant.getJavaCompileProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getJavaCompile(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
*********************************************************
WARNING: This version of connectivity will break your Android build if it or its dependencies aren't compatible with AndroidX.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.
This warning prints for all Android build failures. The real root cause of the error may be unrelated.
*********************************************************
Command: /Users/***/android/gradlew app:properties

Finished with error: Please review your Gradle project setup in the android/ folder.

bad

The problem is because you are migrating to AndroidX, and the Gradle plugin supports only Kotlin Gradle plugin version 1.3.0 and higher meanwhile get_ip is using 1.2.51 version...
We just have to wait for the upgrade. =/

Thanks Roberth.


fix: Don't insert an extra brace in macros with native newlines

Due to format_snippet formatting the input with \r\n the subtraction wouldn't give a length that removed the }
Fixes #2641

Thanks!


Ninja fallback option: use PyPI if known working platform

The fallback could only trigger if we are not on a known platform with binary wheels.
CC @agoose77. Idea from https://github.com/maxbachmann/JaroWinkler/blob/bd014466084ba28d4c9af9a916a21a12bf5ace23/_custom_build/backend.py#LL32

Fixed in #80.


Portrait

It would be nice to also add a portrait to the top right-hand corner. Any chance that this gets implemented, at least for the one column version?

Check this branch's output.

Oh, I didn't check the branches. This is awesome, thanks for the hint!


Release 1.0.25

[Current coverage][cc-pull] is 81.35% (diff: 100%)

No coverage report found for master at c40460b.

Powered by Codecov. Last update [c40460b...d930921][cc-compare]
[cc-base-branch]: https://codecov.io/gh/valor-software/ng2-bootstrap/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/valor-software/ng2-bootstrap/compare/c40460b8439da90b61df24be1a49689833fcbb3a...d930921a6f284a447c6962ab538126c3eb362741?src=pr
[cc-pull]: https://codecov.io/gh/valor-software/ng2-bootstrap/pull/778?src=pr


Bootstrap fails after outdated internals detection

Steps to Reproduce

Install 0.27.0
Run rye self update
Run command to trigger outdated internals detection (I used rye fmt)

Expected Result
Format should work.
Actual Result
❯ rye fmt
Detected outdated rye internals. Refreshing
Bootstrapping rye internals
Found a compatible Python version<EMAIL_ADDRESS>error: tried to symlink python shim (at 'C:\Users\pryerc\.rye\shims\python.exe')

Caused by:
    Cannot create a file when that file already exists. (os error 183)

Version Info
rye 0.28.0
commit: 0.28.0 (c44dc7ec8 2024-03-07)
platform: windows (x86_64)
self-python<EMAIL_ADDRESS>symlink support: false
uv enabled: true

Stacktrace
No response

Test on macos (aarch64):
➜  rye-test git:(main) ✗ rye --version
rye 0.27.0
commit: 0.27.0 (43ee4fce0 2024-02-26)
platform: macos (aarch64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true
➜  rye-test git:(main) ✗ rye self update
Updating to latest
Checking checksum
Updated!

rye 0.28.0
commit: 0.28.0 (c44dc7ec8 2024-03-07)
platform: macos (aarch64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true
➜  rye-test git:(main) ✗ rye fmt
Detected outdated rye internals. Refreshing
Bootstrapping rye internals
Found a compatible Python version<EMAIL_ADDRESS>1 file reformatted

Yep. Can also confirm I cannot repro on Mac. Thanks for checking.

Is the expectation to update another way on Windows machines with symlinks disabled? I have not looked into this much. So I'm not sure if we expect Rye to update differently without symlinks.

From https://rye-up.com/guide/faq/#windows-developer-mode you need to expand the "What happens if I don't enable it?" section for:

All shims will be installed as hardlinks. This can cause issues when upgrading Rye while Python is in use. These hardlinks will also continue to point to older Rye executables creating more hard drive usage.

I'll close this for now, but maybe we can update this to mention that upgrades will actually fail. Not just comment on potential storage bloat.


KeyError: 'USER'

I've seen a few of these errors via Sentry:
KeyError: 'USER'

See traceback below.
Maybe multiple threads are trying to perform the del self.settings_dict['USER'] around the same time?
The code triggering the exception is here: https://github.com/reecetech/django_informixdb_vault/blob/master/django_informixdb_vault/base.py#L172
I suppose it couldn't do any harm to wrap it in a try / catch?
    try:
        del self.settings_dict['USER']
    except KeyError:
        pass

    try:
        del self.settings_dict['PASSWORD']
    except KeyError:
        pass

or use a threading lock?
    import threading
    ...
    self.lock = threading.Lock()

    ...

    if self.lock.acquire(blocking=False):
        del self.settings_dict['USER']
        del self.settings_dict['PASSWORD']

Traceback:
KeyError: 'USER'
  File "rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "rest_framework/generics.py", line 252, in get
    return self.retrieve(request, *args, **kwargs)
  File "rest_framework/mixins.py", line 54, in retrieve
    instance = self.get_object()
  File "rest_framework/generics.py", line 96, in get_object
    obj = get_object_or_404(queryset, **filter_kwargs)
  File "rest_framework/generics.py", line 19, in get_object_or_404
    return _get_object_or_404(queryset, *filter_args, **filter_kwargs)
  File "django/shortcuts.py", line 93, in get_object_or_404
    return queryset.get(*args, **kwargs)
  File "django/db/models/query.py", line 402, in get
    num = len(clone)
  File "django/db/models/query.py", line 256, in __len__
    self._fetch_all()
  File "django/db/models/query.py", line 1242, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "django/db/models/query.py", line 55, in __iter__
    results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
  File "django/db/models/sql/compiler.py", line 1140, in execute_sql
    cursor = self.connection.cursor()
  File "django/db/backends/base/base.py", line 256, in cursor
    return self._cursor()
  File "django/db/backends/base/base.py", line 233, in _cursor
    self.ensure_connection()
  File "django/db/backends/base/base.py", line 217, in ensure_connection
    self.connect()
  File "django/db/backends/base/base.py", line 194, in connect
    conn_params = self.get_connection_params()
  File "django_informixdb_vault/base.py", line 172, in get_connection_params
    del self.settings_dict['USER']

Either approach looks fine to me!  Thanks for looking into it @jwettenhall

Resolved in #7


ci: setup auto release

:tada: This PR is included in version 1.4.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix and improve callback

Contain fixes for:
#7
#8

@blackcoffeexbt , please review and test carefully. In my setup it working fine and I'm going to merge it into my own branch.


change EnvironmentScene.ts

When using the Model viewer with default exposure of 1.0, the 3D assets color visualization looks a bit too hot with over exposure. I prepared a color chart glb with Khronos unlit extension color chart as the baseline, with the medium gray (122,122,122), in the Model viewer it reads as (132,132,132) due to tone mapping I assume.
I then use the same color chart glb with regular PBR as the candidate to tweak the lighting environment to match the target model color, to achieve the same effect.

I'm sorry for waffling, but after looking at this more closely I'm a bit concerned about the amount of difference (breaking change) for our existing users. Consider the before/after of our homepage:

Not only is the result now effectively brighter (I think the front face is probably close, but everything else has brightened a lot), but there's also much less contrast to give the 3D shape a sense of depth. Unfortunately I have the feeling that this is directly at odds with the concept of even lighting, so even with more work there may always be a tradeoff.
I'm thinking of avoiding the breaking change by adding an attribute like default-lighting with options "legacy" and "even", defaulting to the old lighting. And maybe drop the strength on "even" down to where you get RGB parity. How. does that sound? I'm working on a release for next week, so I'd like to close on this quickly.

I'm sorry for waffling, but after looking at this more closely I'm a bit concerned about the amount of difference (breaking change) for our existing users. Consider the before/after of our homepage:

Not only is the result now effectively brighter (I think the front face is probably close, but everything else has brightened a lot), but there's also much less contrast to give the 3D shape a sense of depth. Unfortunately I have the feeling that this is directly at odds with the concept of even lighting, so even with more work there may always be a tradeoff.
I'm thinking of avoiding the breaking change by adding an attribute like default-lighting with options "legacy" and "even", defaulting to the old lighting. And maybe drop the strength on "even" down to where you get RGB parity. How. does that sound? I'm working on a release for next week, so I'd like to close on this quickly.

I like the idea of option to switch lightings. Say from the even lighting it can be for analytical purpose. Therefore it could be named as analytical-lighting or even-lighting.
As discussed, with the even-lighting it is aimed to match the front light of the current default one, and when lower the expected sure to 0.46 seems to match the white balance, which is true for the currently default lighting except the dark would look too dark...which may be for future improvement if the we / users continue to see the need. Happy to have the new lighting included for content creation purpose.
Thomas
Q
Sent from Workspace ONE Boxer
On Jan 12, 2021 7:06 PM, Emmett Lalish<EMAIL_ADDRESS>wrote:
I'm sorry for waffling, but after looking at this more closely I'm a bit concerned about the amount of difference (breaking change) for our existing users. Consider the before/after of our homepage:
[image]https://user-images.githubusercontent.com/1649964/104392527-17547b80-54f7-11eb-988c-5a10743cd2c8.png[image]https://user-images.githubusercontent.com/1649964/104392513-0efc4080-54f7-11eb-970c-835a881e4027.png
Not only is the result now effectively brighter (I think the front face is probably close, but everything else has brightened a lot), but there's also much less contrast to give the 3D shape a sense of depth. Unfortunately I have the feeling that this is directly at odds with the concept of even lighting, so even with more work there may always be a tradeoff.
I'm thinking of avoiding the breaking change by adding an attribute like default-lighting with options "legacy" and "even", defaulting to the old lighting. And maybe drop the strength on "even" down to where you get RGB parity. How. does that sound? I'm working on a release for next week, so I'd like to close on this quickly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/google/model-viewer/pull/1761#issuecomment-759135564, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASB5VZM74IVCCPOY3KIWOE3SZTWXZANCNFSM4UVSB3IA.

I like the idea of option to switch lightings. Say from the even lighting it can be for analytical purpose. Therefore it could be named as analytical-lighting or even-lighting.
As discussed, with the even-lighting it is aimed to match the front light of the current default one, and when lower the expected sure to 0.46 seems to match the white balance, which is true for the currently default lighting except the dark would look too dark...which may be for future improvement if the we / users continue to see the need. Happy to have the new lighting included for content creation purpose.
Thomas
Q
Sent from Workspace ONE Boxer
On Jan 12, 2021 7:06 PM, Emmett Lalish<EMAIL_ADDRESS>wrote:
I'm sorry for waffling, but after looking at this more closely I'm a bit concerned about the amount of difference (breaking change) for our existing users. Consider the before/after of our homepage:
[image]https://user-images.githubusercontent.com/1649964/104392527-17547b80-54f7-11eb-988c-5a10743cd2c8.png[image]https://user-images.githubusercontent.com/1649964/104392513-0efc4080-54f7-11eb-970c-835a881e4027.png
Not only is the result now effectively brighter (I think the front face is probably close, but everything else has brightened a lot), but there's also much less contrast to give the 3D shape a sense of depth. Unfortunately I have the feeling that this is directly at odds with the concept of even lighting, so even with more work there may always be a tradeoff.
I'm thinking of avoiding the breaking change by adding an attribute like default-lighting with options "legacy" and "even", defaulting to the old lighting. And maybe drop the strength on "even" down to where you get RGB parity. How. does that sound? I'm working on a release for next week, so I'd like to close on this quickly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/google/model-viewer/pull/1761#issuecomment-759135564, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASB5VZM74IVCCPOY3KIWOE3SZTWXZANCNFSM4UVSB3IA.

Hey @elalish I'm going to get @bldelgado to take a look at this

Hey @elalish I'm going to get @bldelgado to take a look at this

This same issue came up when we were initially looking at the lighting. I think dropping the strength to where you have RGB parity might be the best move forward, or at least closer. From our side, merchants had used that darker shadowing to help showcase the metal details of their products. But that came at the cost of the colours being slightly off. Fixing that colour issue would at least help to solve one of the problems while we can look at the potential of adding other ways to showcase different materials.

This same issue came up when we were initially looking at the lighting. I think dropping the strength to where you have RGB parity might be the best move forward, or at least closer. From our side, merchants had used that darker shadowing to help showcase the metal details of their products. But that came at the cost of the colours being slightly off. Fixing that colour issue would at least help to solve one of the problems while we can look at the potential of adding other ways to showcase different materials.

I rendered a few mp4s of old vs new. Click to view videos:
Old "hot lighting":
https://user-images.githubusercontent.com/496903/104600866-8e008e80-5647-11eb-8ded-7c104a6e4d02.mp4
New "neutral lighting":
https://user-images.githubusercontent.com/496903/104601156-e2a40980-5647-11eb-930a-927311f071c4.mp4
Old "hot lighting":
https://user-images.githubusercontent.com/496903/104601291-0d8e5d80-5648-11eb-82da-d8561cc4a4ce.mp4
New "neutral lighting":
https://user-images.githubusercontent.com/496903/104601436-3f072900-5648-11eb-86b6-51e712697c2a.mp4

I rendered a few mp4s of old vs new. Click to view videos:
Old "hot lighting":
https://user-images.githubusercontent.com/496903/104600866-8e008e80-5647-11eb-8ded-7c104a6e4d02.mp4
New "neutral lighting":
https://user-images.githubusercontent.com/496903/104601156-e2a40980-5647-11eb-930a-927311f071c4.mp4
Old "hot lighting":
https://user-images.githubusercontent.com/496903/104601291-0d8e5d80-5648-11eb-82da-d8561cc4a4ce.mp4
New "neutral lighting":
https://user-images.githubusercontent.com/496903/104601436-3f072900-5648-11eb-86b6-51e712697c2a.mp4

Thanks for rendering out the video comparison test!
Some observation and thought about the "old-hotter-lighting" and "new neutral lighting":

It depends on what viewing angles we are looking at and what's the purpose
For the original Cube test I posted, the goal is to create even lighting from all 4 sides + top, matching the value from the front side of the  "old-hotter-lighting"
For astronaut: it interprets good description of multi-faceted angle, instead of cube mesh... from the front view astronaut looks overall slightly darker I assume it's because the angle is not 90 degrees but a combination of varied degrees.
For the Mixer example, it looks drastically different at first, but really the fair comparison is the front side of the asset, which is the thin part of the model, where the "V" mark is. If particularly looking at that angle (limited viewing area however), that the color matches, and not surprising having more highlighted spectacular on the new lighting environment.

My thought is, if the new lighting setup is technically sounding and has value for analytical color checking purpose to check the assets from all angles, that's where I see it as beneficial, by adding the new neutral lighting to the repertoire; it is not aiming for replacing the current "old-hotter-lighting" if the merchants already are used to this aesthetics. Side note: a separate topic of improving the current "old-hotter-lighting" as the darker side is too dark...left for debate when it comes to aesthetics however.

Thanks for rendering out the video comparison test!
Some observation and thought about the "old-hotter-lighting" and "new neutral lighting":

It depends on what viewing angles we are looking at and what's the purpose
For the original Cube test I posted, the goal is to create even lighting from all 4 sides + top, matching the value from the front side of the  "old-hotter-lighting"
For astronaut: it interprets good description of multi-faceted angle, instead of cube mesh... from the front view astronaut looks overall slightly darker I assume it's because the angle is not 90 degrees but a combination of varied degrees.
For the Mixer example, it looks drastically different at first, but really the fair comparison is the front side of the asset, which is the thin part of the model, where the "V" mark is. If particularly looking at that angle (limited viewing area however), that the color matches, and not surprising having more highlighted spectacular on the new lighting environment.

My thought is, if the new lighting setup is technically sounding and has value for analytical color checking purpose to check the assets from all angles, that's where I see it as beneficial, by adding the new neutral lighting to the repertoire; it is not aiming for replacing the current "old-hotter-lighting" if the merchants already are used to this aesthetics. Side note: a separate topic of improving the current "old-hotter-lighting" as the darker side is too dark...left for debate when it comes to aesthetics however.

Neutral Lit

Older Lighting

@thomastgt As a test for comparing colour I think we may be overlooking some key factors. When you ask the question of "What is the purpose?" I think more often than not we're talking about 3D models that are meant to be digital representations of their real life counter part. In the two images I posted above I would assume the materials for the mixer to be different.
For the Neutral Lit Mixer I would assume the material is more of a plastic type material. The fact that there's less depth in the colours would make me infer that the material is more akin to a PVC pipe or something. When looking at the grey metal pieces, I would assume that they are more hard plastic in versus brushed stainless steel.
In the case of the Older lighting, I think we fall prey to a problem in the intensity of lighting.
In both cases the issue is having lighting feel more accurate to the materials. It's the combination of the material and the colour that help make it feel real.

Neutral Lit

Older Lighting

@thomastgt As a test for comparing colour I think we may be overlooking some key factors. When you ask the question of "What is the purpose?" I think more often than not we're talking about 3D models that are meant to be digital representations of their real life counter part. In the two images I posted above I would assume the materials for the mixer to be different.
For the Neutral Lit Mixer I would assume the material is more of a plastic type material. The fact that there's less depth in the colours would make me infer that the material is more akin to a PVC pipe or something. When looking at the grey metal pieces, I would assume that they are more hard plastic in versus brushed stainless steel.
In the case of the Older lighting, I think we fall prey to a problem in the intensity of lighting.
In both cases the issue is having lighting feel more accurate to the materials. It's the combination of the material and the colour that help make it feel real.

Okay, I've updated this PR to be non-breaking; you can now get the @thomastgt's new lighting by passing "neutral" to environment-image. I've reverted to baking the 0.46 exposure into the lights, since we no longer need to match anything. I like this quite a lot, and note the new example where you can compare the default to this new neutral. It would be great if someone could verify that my changes still have the RGB color swatches rendering as desired.

Okay, I've updated this PR to be non-breaking; you can now get the @thomastgt's new lighting by passing "neutral" to environment-image. I've reverted to baking the 0.46 exposure into the lights, since we no longer need to match anything. I like this quite a lot, and note the new example where you can compare the default to this new neutral. It would be great if someone could verify that my changes still have the RGB color swatches rendering as desired.


"Dump only" attributes in order to differentiate between validation of inbound data and serialization of outbound data.

Is it possible to add the support of the subj to pydantic models (to Config, perhaps)?
What I'm talking about is the case when I, for instance, have a REST API which allows to POST new users and GET user's info. With a library like Marshmallow, I could define the User schema as follows:
class UserSchema(Schema):
    id = fields.Integer(dump_only=True)
    name = fields.String(validate=validate.Length(min=1, max=128),
                         required=True)
    created_at = fields.DateTime(format='iso', dump_only=True)

    class Meta(object):
        ordered = True
        strict = True

    @decorators.post_load
    def post_load(self, data):
        data['name'] = data['name'].strip()
    return data

With this, it's possible to validate only the user name on POST (and have only the user name in the results returned after the validation) while also dumping id and creation date as JSON on GET.

My instinct is that this is best done outside pydantic.
I would implement (indeed I have) a wrapper class that includes a valididation "Model", but also lost of other data/logic about that data type.
Something like
class UserSchema:
    class PostModel(BaseModel):
        name: str

        @validator('name')
        ...

    get_fields = 'id', 'name', 'created_at'

    async def get_from_db(...)
        pass

You can see something kind of like that here.
Hope that makes sense, let me know if it doesn't suffice.

kind of related to #64, but I decided that was a bad idea.


Japanese Translation

I added a Japanese translation of the website to this branch.
I am planning to create a pull request.
Is this procedure correct to contribute?

Hi @enkatsu,
Regarding website translation, we are rolling out new languages slowly to be absolutely sure that we can support the full translation and maintenance of each language. We want to avoid the situation where we have many languages and it's beyond our means to support. So for this reason, we are holding now with Spanish and Chinese and getting those fully complete before we take on others. When we begin with Japanese I will certainly be in touch.
However, we very much welcome translations that are hosted elsewhere. Please feel free to translate any of the website content and host on an external blog or site. All of the website content is licensed under Creative Commons which makes it possible to reuse this content for non-commercial purposes if it is credited. We would be happy to share links and make connections so others can find and use this material.

Hi @lmccart
Thanks for the reply !
I understand the p5.js community's policy on translating web sites. I'm looking forward to hearing from you :)
p5js.jp is vacant, may I acquire this for hosting ?
If it is difficult, use another domain name.

@enkatsu I think that would be fine and great to acquire p5js.jp and host your translation there :) please keep us updated on progress, I would love to share via social media so others can make use of it when's it ready. thank you for your contribution!

@lmccart I'm glad to hear that!
I acquired p5js.jp and hosting the translation.

hi @enkatsu this is awesome! may I suggest while we still have it hosted at another location, that you remove the language buttons and only host the japanese version there? that way there is no confusion. or perhaps the language buttons could link back to the p5js.org site?

@lmccart Thank you for your suggestions! I agree with you. I removed the language buttons and only hosting the japanese version. How is this?

@enkatsu this is great! I've added a link here please let me know if you'd like me to edit the credit in any way, or you can submit a PR yourself.
I am thinking of other places to link to pages like these if you have suggestions. I think it'd be nice to get some buttons up on the main p5js.org page soon next to the other languages, that somehow indicate that some of them are linking outwards.


Fix README example binding

I tried it as is, and this is not defined in the handClick method. I needed to add this binding to make it work.

You are right indeed @saulshanabrook. Can I ask you to fix the example for the Higher Order and Wrapper methods also please?

@Yomguithereal sorry for the delay, look OK now?

Thanks @saulshanabrook! Merging right now.


Creating and Initializing special accounts variables of the Accounts activity to avoid NullPointerException

Creating and initializing special accounts in the refresh method of the Accounts activity to avoid NullPointerException that can be thrown when the activity is resumed. This error forced the application to close right away and happened because the initialization of the special accounts variables is done in the onCreate method of Accounts activity only when the 'hide special accounts' selection isn't checked.
Scenario that caused the error:

Before starting the application the option 'hide special accounts' is checked
The user starts the application and changes this option in the menu
The user clicks back button 2 times to come back to Accounts screen
NullPointerException forces the application to close

Constant added to represent the number of special accounts to be used in the initialization of the ArrayList that represents the special accounts to be used in the list adapter of the activity.

yay! thought it'd be easy. now can you add a force close feature when k9 is in developer mode? (just kidding!) it is actually useful to do so, though i never used this bug for such, instead just reinstalling the app.
as a side note, i merged this with "curl https://github.com/k9mail/k-9/pull/124.patch | git am" followed later by "git push upstream HEAD:master", without editing the commit in between, and i thought github was supposed to automatically close this pull.


Releases / Downloads?

I've been looking through some of your work and this really caught my eyes. This looks like quite a cool app, but as much as I would like to try it, there's no instructions on how to use it for myself? I would like a download link with an exe or maybe some installation instructions because this seems like a cool idea. Thoughts?

Sounds great! Keep me posted! I found you through the explore tab and your delet bot, but your work seems really cool and I'd like to see what this app can do.

That's pretty cool! delet is one of my main projects so I'm glad you found it.
Version 1.0.0 of TVVC has now been released, and installation instructions can be found in the README file.
If you come across any bugs/issues, feel free to create a new issue.
Thanks again for creating this issue and requesting a release!


[BEAM-2333] Runner API translation renames

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify.
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @tgroh as discussed, adding a more-specific suffix to these utility classes. I peeled these commits off from #3195 to trim it down.

Changes Unknown when pulling 4fa38e2d590cc4472c119b57790f7a724a700e43 on kennknowles:RunnerApiTranslation-renames into ** on apache:master**.

These should not be staged.

Hmm I see.

run dataflow validatesrunner

Great news: The renames do not break anything.


[EventRequest] SalesTaxCalculate.Codeunit.al (codeunit 398 "Sales Tax Calculate")

Hi MS,
Please help us in migrating our verticalized solution by adding below events in SalesTaxCalculate.Codeunit.al codeunit.
Standard Code (Screenshot from DistTaxOverSalesLines)

Modified Code

Event Signature

Thanks
SUD

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Create a new bibliography copy styple

Hi,
I follow your generate_temp_bib.sh to create a new style that only generates the inline citations.
In generate_temp_bib.sh, if you press the button cmd+option+enter, it will return:
Wang, Z., Chen, J., & Zhao, X. (2020). Risk Information Disclosure and Bank Soundness: Does Regulation Matter? Evidence from China*. International Review of Finance, 20(4), 973–981. https://doi.org/10.1111/irfi.12244

In generate_temp_citation.sh, it will return:
Wang, Chen, & Zhao (2020)

You may assign another hotkey combination for this citation style.

hi, thanks for the PR!
However, I am not really what the purpose of this feature is. The intended workflow for using pandoc and markdown is to insert pandoc citations, and to run pandoc on the final document once. The feature to paste the full bibliography is mostly a convenience feature for sending a one-off reference to peers via mail.
How your proposed feature be more useful than just inserting pandoc citations and then running pandoc on the document?

I see, that makes sense, yeah. However, I think your problem can be solved in a simpler way on your end:
You can use pandoc with the options --to=markdown-citations --metadata=suppress-bibliography:true to use pandoc solely as a citation resolver, (while keeping the markdown as input and output format).
So by using a command like this:
pandoc --citeproc --bibliography="$HOME/.pandoc/bibliography.bib" input.md -o output.md --to=markdown-citations --metadata="suppress-bibliography:true"

you will get an output file where all pandoc citations are resolved correctly, but where nothing else is changed, allowing you to use slidev as usual.
As opposed to resolving citations with the Alfred workflow, this has the advantage that your original document is still pure pandoc markdown, meaning that as opposed to resolving citations, your editor can still apply syntax highlighting for the citations, and you can still switch citation style later on with the --csl option from pandoc

I appreciate your suggestion.
But the performance could be better.
The --citeproc will ignore the YAML front matter and also disorganise the HTML code.
For example, the original code is:
<div class="pt-12">
  <span @click="$slidev.nav.next" class="px-2 py-1 rounded cursor-pointer" hover="bg-white bg-opacity-10">
    Press Space for next page <carbon:arrow-right class="inline"/>
  </span>
</div>

After I apply pandoc --citeproc, the HTML division has changed to
::: pt-12
\<span (**click?**)="\$slidev.nav.next" class="px-2 py-1 rounded
cursor-pointer" hover="bg-white bg-opacity-10"\> Press Space for next
page `<carbon:arrow-right class="inline"/>`{=html} `</span>`{=html}
:::

So I think the best way to keep the pure markdown file is only to insert the reference rather than use --citeproc to render the file.

Hmm, I see. Nevertheless, I am still somewhat hesitant about adding a feature whose sole purpose appears to be to deal with the shortcoming of another app.
I assume for the particular case of the unintended html conversion, you can probably prevent that as well with some pandoc option. Could you maybe try asking around in the pandoc google group how to prevent the html conversions? If that also yields no useful help, I'll consider merging this as a feature.

Understand!
Thanks for your link. I will get more information from different resources and update you later.

Hi,
I find an easy way to use pandoc and --citeproc to render the markdown file and keep the content unchanged. It should generate an intermediate json file.
pandoc --citeproc input.md -o intermediate.json -s
pandoc intermediate.json -t gfm -o output.md -s

I try different output formats, but it can only use the gfm. Other formats will ignore the YAML front matter. You also need to use ------------------------ as the pagebreak.
The above process cannot handle the HTML code very well, but it can be used for simple academic slides.


Examples don't show how to provide pagination options

Unless I'm missing something, I don't see how the caller provides the pagination values for the limit and page number. I feel that without this, it's unclear how the user provides the pagination options.
This SO post, however, shows the Pagination Options param. https://stackoverflow.com/questions/60152442/does-fastapi-contrib-has-paginator-for-postgresql/64720717#64720717

Hi @stealthrabbi,
No need to pass params explicitly, it will be done behind the scene.
So this code:
from fastapi import FastAPI
from pydantic import BaseModel

from fastapi_pagination import Page, add_pagination, paginate

app = FastAPI()

class User(BaseModel):
    name: str
    surname: str

users = [
    User(name='Yurii', surname='Karabas'),
    # ...
]

@app.get('/users', response_model=Page[User])
async def get_users():
    return paginate(users)

add_pagination(app)

Is rawly equal to:
from fastapi import FastAPI, Depends
from pydantic import BaseModel

from fastapi_pagination import Page, Params, paginate

app = FastAPI()

class User(BaseModel):
    name: str
    surname: str

users = [
    User(name='Yurii', surname='Karabas'),
    # ...
]

@app.get('/users', response_model=Page[User])
async def get_users(params: Params = Depends()):
    return paginate(users, params)

Docs are outdated, I don't have a time to update them(

Hi @stealthrabbi,
No need to pass params explicitly, it will be done behind the scene.
So this code:
from fastapi import FastAPI
from pydantic import BaseModel

from fastapi_pagination import Page, add_pagination, paginate

app = FastAPI()

class User(BaseModel):
    name: str
    surname: str

users = [
    User(name='Yurii', surname='Karabas'),
    # ...
]

@app.get('/users', response_model=Page[User])
async def get_users():
    return paginate(users)

add_pagination(app)

Is rawly equal to:
from fastapi import FastAPI, Depends
from pydantic import BaseModel

from fastapi_pagination import Page, Params, paginate

app = FastAPI()

class User(BaseModel):
    name: str
    surname: str

users = [
    User(name='Yurii', surname='Karabas'),
    # ...
]

@app.get('/users', response_model=Page[User])
async def get_users(params: Params = Depends()):
    return paginate(users, params)

Docs are outdated, I don't have a time to update them(

Thanks, so does add_pagination only affect rest methods that have a response model that includes a Page?

Yup, exactly.
Basically, it's add additional dependency to road that handles params depending on Page type.

https://uriyyo-fastapi-pagination.netlify.app/first-steps/

https://uriyyo-fastapi-pagination.netlify.app/first-steps/


Fix service resource for CentOS 5.x

Missing /sbin in PATH by default and sudo not in use. Explicitly specifies chkconfig path in this scenario. Verified behaviour locally in test-kitchen and it worked.
I could not come up with a clean way to get spec tests working for this (as it depends on a file existing), and doing test-kitchen tests against specinfra for CentOS 5.x feels a bit Test-ception :) tests pass in their current state, just missing CentOS 5.x coverage specifically.

Your code only works with exec backend and does not work with other backend.
And writing set :path, '$PATH:/sbin' in spec_helper.rb or else is sufficient to solve this.

Yea ok fair call, I'll use set :path instead :) Thanks


Cannot exclude lodash when use it as an external

Bug report

What is the current behavior?
I set the lodash to externals, but it still left some code in my package file.

webpack.config.js
{
   externals: {
    lodash: '_'
  }
}

If I add noParse to webpack.config.js
{
  module: {
    noParse: /lodash/,
  }
}

Then an error happens,
Uncaught ReferenceError: require is not defined

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
lodash code should not be in my file.

Other relevant information:
webpack version:  4.41.2
Node.js version:  10.16.3
Operating System: ios
Additional tools: vs code

{
externals: {
lodash: '_'
}
}

this matches require("lodash") but doesn't work for e.g. require("lodash/throttle"). Use a function to match all of them.

Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks!


Fix no slack chat and double chat bugs

Why can't we have the best of both worlds, revert that, and add another event listening and canceling the old event, doing nothing with it

what do you mean by that?

I'm not at my computer right now, so you can probably merge it as is, and
I'll get to it later
On Sun, 5 Mar 2023, 21:01 polypixeldev, @.***> wrote:

what do you mean by that?
—
Reply to this email directly, view it on GitHub
https://github.com/hackclub/HCCore/pull/151#issuecomment-1455204720, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKGERPE3TVJSURK4BFEIWW3W2T5LPANCNFSM6AAAAAAVQMEHOI
.
You are receiving this because your review was requested.Message ID:
@.***>


SP5 Cookbook: pie chart

This works but isn't documented in the cookbook. Thanks to Trinitium in the Discord (#1966) for noting this.
PieSlice[] slices =
{
    new(6, Colors.Red),
    new(4, Colors.Blue),
    new(3, Colors.Green),
    new(1, Colors.DarkCyan),
};

formsPlot.Plot.Add.Pie(slices);

related to #3215 so I'll close this and follow-up there


732 search

Overview
Resolves
https://github.ibm.com/carbon/issues/issues/732
Deprecated search with icons. Have been removed in react as well.
https://github.com/carbon-design-system/carbon-components-react/pull/929
Removed
Removed search with icons
Changed
Changed close button offset to default 12px because Search with icons is deprecated.

Thank you for working on this @aledavila! One question - Should large/small variants be identical with this change, or are there still some differences?

@asudoh yes. they will be the same but on is smaller than the other.


Fix StarTreeClusterIntegrationTest by not removing the segments

We need to keep the tarred segments for segment metadata push to work

Codecov Report

Merging #6087 into master will increase coverage by 6.57%.
The diff coverage is 59.61%.

@@            Coverage Diff             @@
##           master    #6087      +/-   ##
==========================================
+ Coverage   66.44%   73.02%   +6.57%
==========================================
  Files        1075     1217     +142
  Lines       54773    57377    +2604
  Branches     8168     8449     +281
==========================================
+ Hits        36396    41900    +5504
+ Misses      15700    12730    -2970
- Partials     2677     2747      +70

Flag
Coverage Δ

#integration
45.59% <48.65%> (?)

#unittests
64.16% <37.88%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ot/broker/broker/AllowAllAccessControlFactory.java
100.00% <ø> (ø)

.../helix/BrokerUserDefinedMessageHandlerFactory.java
52.83% <0.00%> (-13.84%)
:arrow_down:

...ava/org/apache/pinot/client/AbstractResultSet.java
53.33% <0.00%> (-3.81%)
:arrow_down:

.../main/java/org/apache/pinot/client/Connection.java
44.44% <0.00%> (-4.40%)
:arrow_down:

.../org/apache/pinot/client/ResultTableResultSet.java
24.00% <0.00%> (-10.29%)
:arrow_down:

...not/common/assignment/InstancePartitionsUtils.java
78.57% <ø> (+5.40%)
:arrow_up:

.../apache/pinot/common/exception/QueryException.java
90.27% <ø> (+5.55%)
:arrow_up:

...pinot/common/function/AggregationFunctionType.java
96.49% <ø> (-3.51%)
:arrow_down:

.../pinot/common/function/DateTimePatternHandler.java
83.33% <ø> (ø)

...ot/common/function/FunctionDefinitionRegistry.java
88.88% <ø> (+44.44%)
:arrow_up:

... and 951 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e303938...e606b94. Read the comment docs.


pull request for e2e test at 12/20/2016 17:26:22

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


paper says smoothing all linear layers, but code seems to smooth only the qkv projection in attention and the first fc in ffn?

In the smooth_lm function that is used to export int8 model, only the qkv projection layer and the first fc layer in FFN module go through the smoothing-based-on-range process, where the scaling of input is merged to the layernom before the linear layer, and the scaling of weights is merged to the weights of the linear layer.
https://github.com/mit-han-lab/smoothquant/blob/be3c4239d21be5eeba7cd425a747c0d9c08804f6/smoothquant/smooth.py#L34
How about for the second linear layer of attention and FFN module? They don't have a layernom before it, how is the scaling of input implemented? Pointer to the code will be appreciated!

Not the author, but looks like they loop through all the FCs? So we at least get the fc2. See here.

Yea exactly, only fc1 and qkv projection. No fc2 or attention output projection

I appreciate your interest in our project! On OPT and BLOOM models, we found that smoothing the QKV and FC1 two layers was sufficient to recover the accuracy. Smoothing out_proj in attention and FC2 in FFN is only necessary on GLM-130B, whose activations are more challenging to quantize. Thus we haven't included the code to smooth them in the current repo.
To smooth the out_proj in attention, you can divide the smoothing factors into the output channels of v_proj. And to smooth the FC2, we need to introduce another per-channel scaling before FC2.

Thank you for the speedy clarification!

Interestingly the query scales are used for all the q_proj, k_proj, v_proj ops (fusing into the layernorm): https://github.com/mit-han-lab/smoothquant/blob/78badc0d975506de9fe44b2fe79d9a35d0fd4914/smoothquant/smooth.py#L40C36-L40C36


Wrong OpenSSL version

The current master requires OpenSSL version 1.1.0, but TLS1_3_VERSION and SSL_CTX_set_ciphersuites seem to be available up from version 1.1.1.

Good catch, I'll look into fixing it, thanks!

Again, thank you for reporting this! :-)

You are welcome :)


GSM Base Location T322 not working When GPS Invalid

When I get GPS Signal Invalid (V), it cannot get location data in LBS.
2015-04-16 03:42:34 DEBUG: [5020 <- <IP_ADDRESS>] - HEX:<PHONE_NUMBER>2c3836323935313032303030363632342c4343432c02013400010000001fd955a2ffe2525f06f1ebc11c0000180000000000000000a9e7050003360200fe010a007a0055000001af8da301ef04000000002a62310d0a
2015-04-16 03:42:34 DEBUG: [5020 -> <IP_ADDRESS>] - HEX:<PHONE_NUMBER>2c3836323935313032303030363632342c4343432c312a30390d0a

What should I do for fix it?

I think it about MCC|MNC|LAC|CI
But, i don't have idea for translate it to coordinat locations.

Traccar does not support LBS yet. To add support we need to find a provider first.

is hard to impossibile to find a good provider, opensource solution is openCell but is not complete.
Any ideea will be great to know

Supporting LBS is greate feature
Maybe something will be usefull:
https://location.services.mozilla.com/api (a bit bigger than openCell ID)
http://unwiredlabs.com/api (cool coverage, has free account)
Secret google API (if it's true) http://www.google.com/glm/mmap?mcc=xxx&mnc=xxx&towerid=xxx (http://stackoverflow.com/questions/1598696/google-maps-cellid-to-location)

LBS locations have been supported for a while now, so closing this.


SYNC Our repo with the original one

This PR is to sync our NR statsd repo with the original one and fix reported security issues.

LGTM. Are there changes in our Repo that should be PRed back to NewRelic?

@bettlebrox not really, actually I am not sure why we are using our own fork instead of the main repo (we could talk about this offline).

@kabute @bettlebrox We used our own fork, because I fixed a bug and created that PR#2 for newrelic, but they were slow to merge it into master. Now it's merged, so you can directly use upstream releases 🤝


[core] Implement orthographic projection for 3D camera

I need an orthographic projection for the game I am currently working on, and as far as I can see this functionality is currently not exposed through the API. I think it would be useful to have this integrated in the current camera system. There could be a separate member in the Camera struct to set the projection, defaulting to perspective. Something along those lines.

Implemented in PR https://github.com/raysan5/raylib/pull/513


Correcting typo on generate-component-config script

Summary
Minor typo change on the README. (compoent -> component)

@cchesser Hey! @StephenEsser pointed out I totally missed you should add yourself as a contributor. Sorry!

No worries, I'm not worthy to be listed as a contributor...for a single word update in a README (regardless of desired process).


Use service monitor

This PR:

uses a servicemonitor instead of old monitoring labels

Checklist

[x] Update changelog in CHANGELOG.md.
[x] Make sure values.yaml is valid.

Tested on golem


fix nacos connection leakage and weight setting for nacos service

Ⅰ. Describe what this PR did
Fixed an error where namingClient was not closed when the nacos registry was deleted, resulting in connection leakage
Added the ability to set weights for nacos services
Ⅱ. Does this pull request fix one issue?

fixes #530
fixes #529

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


QIR Array Slicing does not match spec

Array slicing is supposed to work like copy, where it includes a force parameter and will behave differently based on that and how many alias counts the target array has. In the QIR spec  it has signature %Array*(%Array*, %Range, i1) and describes it as:

Creates and returns an array that is a slice of an existing 1-dimensional array. The slice may be accessing the same memory as the given array unless its alias count is larger than 0 or the last argument is true. The %Range specifies the indices that should be the elements of the returned array. The reference count of the elements remains unchanged.

Meanwhile the runtime currently defines __quantum__rt__array_slice_1d as:
https://github.com/microsoft/qsharp-runtime/blob/c84d56d98ae58bbf99aa980d1a063a81005611f9/src/Qir/Runtime/lib/QIR/bridge-rt.ll#L294
And the implementation always copies.
__quantum__rt__array_slice has the same problem.
@bettinaheim, @kuzminrobin, @alan-geller FYI

Hm, I think it would be reasonable (and more reasonable) to not require the runtime to implement that optimization. I'd leave it up to the runtime to make a judgement on what cases exactly it wants to optimize; this optimization specifically requires  a particular choice regarding representation, which we shouldn't prescribe - full opacity of arrays has been appreciated. Let me transfer this to the spec repo.


Fix typo

📝 Summary

Fixing a typo that triggered my OCD
💡 Motivation and Context

✅ I have completed the following steps:

[x] Run make lint
[x] Run make test
[ ] Added tests (if applicable)

Harsh:


Failing build messages on TravisCI

Just saw these messages on TravisCI for the master:

Hi, that's expected. The VTK install is broken on Ubuntu. We're already testing more than before, where the code wasn't compiled.

I'm reopening this because I saw this error again on Travis. I don't see a reason to keep building propseg on Travis if it always fail, it is just adding more time to the already long building process. A checking can be added to avoid it.

@zougloub is there a reason we want to keep the propseg build on Travis? given that we are shipping the binaries of propseg (which could be different from those that are built within travis), i am wondering if we should maybe move this build test somewhere else because it adds up some travis time.

I agree with you and @perone on this.
I'll remove the build.
FYI I'm also thinking of removing the python3 jobs for now, maybe replacing them by linting (restricted to checking py3k incompatibility), TBD after testing.

Closing, as we no longer build sct_propseg in Travis thanks to #1970.


sign off release 1.2.0

please maintainers help test harbor-operator 1.2.0 rc build, and sign off here

[x] Steven Zou , steven-zou , VMware
[ ] Ziming Zhang , bitsf , VMware
[ ] Weiwei He , heww, VMware
[ ] Canfeng Wang , wangcanfengxs , Netease
[ ] Huijun Zhu , Ghostbaby , Yunmanman
[ ] Xiaoyang Zhu , soulseen , Shoppee
[ ] Chengyu Zhang , chlins , VMware
[x] Xiongxiong Yuan, yxxhero, Qunar:

helm install
docker pull
docker push
docker login
api is ok

[ ] Yinan Li , cndoit18 , Qihu360

Sign off v1.2:
Steps:**
Install harbor-operator v1.2 by kubectl apply -f "k8s apply -f "https://raw.githubusercontent.com/goharbor/harbor-operator/release-1.2.0/manifests/cluster/deployment.yaml""
Deploy full-stack Harbor with the manifest yaml under manifest/samples (with core..nip.io) on kind (k8s 1.22)
Login harbor,
Create project,
Add docker hub registry,
Create replication rule to pull nginx/haproxy latest images to the crated project
Scan images
Check versions
Check cluster pods
Update configurations via CRD:
apiVersion: goharbor.io/v1beta1
kind: HarborConfiguration
metadata:
  name: test-config
  namespace: cluster-sample-ns
spec:
  # your harbor configuration
  configuration:
    robotTokenDuration: 45
    robotNamePrefix: harbor$
    notificationEnable: false
  harborClusterRef: harborcluster-sample

Functions checked

[x] - new k8s
[x] - new storage driver
[x] - bump harbor 2.4.1
[x] - bump redis
[x] - bump minio
[x] - bump psql
[x] - CRD based configuration
[ ] - support ingress class
[x] - support optional component removal
[x] - put registry and registryctl pods in one
[ ] - make portal component optional

Issues found

The day2 CRD doc is not correct - issue created and need to fix
The harbor operator version is not correct (should be v1.2.0 but still dev_master)

Sign off v1.2:
Steps:

install kind cluster (kubernetes v1.21.0)
install cert-manager
install harboer-operaotr(kubeclt apply -f ./manifests/cluster/deployment.yaml)
install harbor (kubeclt apply -f ./manifests/sample/full_stack.yaml)

Functions checked
Issues found


Fixes:#495 - Jashwanth/navlogin

Fixes:#495
This pull request solves abow issue. and also other issue which is closed,

https://github.com/user-attachments/assets/7f2d843f-8e53-447d-ae71-11a5bfdc32a4

Fix conflicts

@Luson045 fixed,

@Jashwanth-rit  checks have failed maybe you made some error during merging the conflicts, please check again. Can't merge until all checks are passed


Historical test data

Hello,
First of all my apologize if I submit this questions to wrong platform, I am pretty new to this.
I am trying to integrate Robot Framework to Allure, and actually managed to do it successfully till some point, however have not found any information how to make historical test data available in the Allure Report (e.g. Trend graph), I can only see the latest test execution result. Is it supported, and if so, can you please advise what to do to make it work?
Thanks,
Akos

I am having the same exact problem...anyone find a solution?

Try this library https://github.com/skhomuti/allure-python/tree/master/allure-robotframework
Works like a charm.

works like a charm in what aspect? I tried it and it fixes nothing. all it does is throw everything into 1 file and keeps compounding them. it doesn't put them in corresponding folders in the right fashion to give you historical runs like we are searching for. That honestly is a worse library/listener from my use so far

Do you want to run tests locally and see the trend? I don't know how it works when you run allure locally, but if you use Jenkins, trend will be available (if you use Jenkins plugin for Allure) without any manual actions.
Also pytest allure plugin works same way - generate new report (xml or json) files every time and allure report doesn't show any trends. But, again, there is trend in Jenkins.


Why drop the ARM version?

Why drop the ARM version?
Hey, @duke7553! In my opinion, it's a stupid idea (No Offence) to drop the ARM Version because ARM and IoT are the future and when I was trying to install Files in my Rasp Pi, I was searching for the ARM version until I read and understood that you stopped support for ARM. I know it's tough for developing a version for ARM and to create new certificates for it but please try to keep the ARM version alive. Just an opinion and would be nice if you start developing again. Thanks and sorry for mentioning it was a stupid idea.

Hey, thanks for your feedback. The new functionality added for running EXEs currently only supports x86 and x64. I plan on eventually compiling this for ARM also, and you can expect a great effort to achieve this before the Store release.

P.S. A raspberry Pi isn’t necessarily the best device to run Windows 10 on either, but the ARM releases are likely being dropped temporarily ;)

@KartSriv I'll bring back the ARM version now, but it may have bugs. Please read the note on this page: https://github.com/duke7553/files-uwp/releases/tag/v0.4.8 .
Download should be up now for ARM

Thanks. @duke7553! It's very nice of you. I have a small tip: Focus mainly on the x86 and x64 Arch for now. Once you've perfected the code then make one for the ARM Arch. It'll make the delivery time quick and you can have a much more stable code for the consumer.


Reducing Setting Up Target Phase?

Hi, I was wondering if there is a way to reduce the amount of overhead when running WA?
I noticed that before the benchmark starts there's a "Setting up target" step, which sometimes take about 30 to 40 seconds.
Each time I run a single benchmark like 5 seconds of Dhrystone, it ultimately leads to about an overhead of 70 seconds.
Could I know where I could go into to reduce this overhead?
I've been looking through devlib and frameworks, but without much luck.
I would also like to skip the steps of compressing the cpufreq folder and pulling it from the device? As I merely just want to set the target device.
Thanks!

Hi,
WA will require some level of overhead as it queries the device at runtime to pull the device configuration and try to ensure that the device is in a "known" state to try and ensure repeated runs start from the same base state as much as possible.
However by default WA/devlib have a set of default modules and Augmentations that are enabled, such as cpufreq so you can try disabling these to see if this reduces the setup time.
An example agenda excerpt to do this would be something like the following and you can manually reenable any you may require for your tests.
config:
    augmentations: ['~~']              # Disable WA Augmentations
    device_config:
        load_default_modules: false    # Disable default devlib modules
        modules: []

Depending on how your setup is configured, another option may be to use a single WA Run to run multiple tests in a single agenda to avoid performing the overhead each time.

Note that some work has been done in that direction here: https://github.com/ARM-software/devlib/pull/634
This PR allows devlib to lazily load (most) modules, although I think WA would still ask for some modules to be eagerly loaded by default.

Also, the async capabilities of devlib could allow loading multiple modules concurrently as long as they don't try to write to the same files. This is not done for now but wouldn't be very hard, as most modules only read files upon loading.


Admins should be able to delete announcements

Added in saarang-api branch

need to update after allen added profile images to announcements

added in saarang-api branch


Feature request: Add additional ways to delete a widget

To delete a widget from the tree window, the user on a full sized keyboard can push the forward delete key. This key isn't available on some laptops, so the convenience of deleting a widget with a single key stroke isn't there. I suggest that the delete key (on a Macintosh) or the backspace key (on a PC) be given the power to delete a widget.
I also request that a menu item be added to the Edit menu called "Delete" what would allow the user to delete a widget as well.
Thank you.

You can always use Ctrl-X. It might be Command-X on the Mac.
The backspace key, at least on Windows, will go up by one in the hierarchy.
I would not want to mask that feature as there are also blind people who are only using the tree for navigation.
Most Windows notebooks seem to have the Delete key anyway, usually at the top right.
What is the situation on Mac Os? Unfortunately I don't have Apple hardware for testing. When looking at a keyboard in the store, there is one "Delete" where a PC has Backspace and one "Delete |x>" where a PC has the Del/Delete key.
The latter seems to be missing from the MacBooks.
What are those keys doing now in the Tree control? In my Mac VM the "Delete"/Backspace does nothing, so on Mac Os it could be assigned for deleting.
I will look into menu and toolbar support for deleting.

All MacBooks lack a 'Forward Delete' key. Pushing the 'Delete' key does nothing in the Tree control or on the Design Window when a widget is selected.

OK, I will look to assign the Delete key on Mac Os.

Could you please try this?
In main.py, around line 513, replace:
    ("",  wx.WXK_DELETE):(_remove, ()),
with
    ("",  wx.WXK_BACK):(_remove, ()),
Does this work for you?

I was not able to find the code. I looked in both the 1.0.0a9 and master repos.

Sorry, it's misc.py, not main.py.

It worked great.

Cool. It's in the repository now.

1.0.0b1 is online.


Include the page title with the content scanned for tag

Hi ! nice work !
I think you are not including the note title in the prompt in order that openAI uses it to generate some extra tags.

Hi! indeed.. 😅 🤦
Will get that sorted by this weekend at the latest 😊  thanks!


Influxdb v1.0.0 beta not paging  (Seen in v0.13 also)

Bug report
System info: [v0.13 & v1.0.0 beta, Ubuntu Trusty, stock AWS AMI no alterations]
Here's a drop of keys and tags from the series:
> show tag keys
name: usage_costs
-----------------
tagKey
assemblyID
lineitem_lineitemtype
lineitem_operation
lineitem_productcode
lineitem_resourceid
lineitem_usageaccountid
lineitem_usageenddate
lineitem_usagetype
product_group
product_instancefamily
product_instancetype
product_operation
product_productname
product_requesttype
resourcetags_user_costcenter

> show field keys
name: usage_costs
-----------------
fieldKey
lineitem_blendedcost
lineitem_blendedrate
lineitem_unblendedcost
lineitem_unblendedrate
lineitem_usageamount

There's some could-be sensitive information so I'd rather not show series.
Steps to reproduce:
Three databases were created: a 100k row series, 500k row series, and 1 million row series. This crash occurs on 500k series and up.
I have a bash for loop sending the query locally with the influx client. Sleeps every 1 second. Normally latency of the request blocks past this, and script is actually running at the speed of query latency.
With three different queries running in the same fashion, I watch application memory fill cache and free, taking almost all memory.
The queries were as follows:
influx -database 'medium_example' -execute 'SELECT sum(lineitem_usageamount) from usage_costs group by lineitem_operation'

 influx -database 'medium_example' -execute 'SELECT sum(lineitem_unblendedcost) from usage_costs group by lineitem_operation'

influx -database 'medium_example' -execute 'SELECT sum(lineitem_unblendedrate) from usage_costs group by lineitem_usageaccountid, lineitem_productcode'

Expected behavior: Influxdb uses all available memory, begins to page out to disk, and handles the load appropriately.
Actual behavior: influxdb uses all available memory, no paging occurs, influx crashes with out of memory issue
Additional info:
Hey guys,
I was stress testing Influxdb today, and I'm 95% certain I found a very repeatable memory leak. I don't have full details on the query but it was is just testing out basic schema and queries. With data sets above 500k points I saw application take over all free and cache ram space. Once it sat there for awhile it finally crashed. I have a monitor called vector collecting stats. I'm also watching vmstat. I see absolutely NO swap in or out, or any evidence of paging.
I deduced that two things are possible:

Influxdb is handling its own memory, which I don't believe is completely possible unless it's doing direct io, and avoiding the page cache (would this even stop paging cron happening??)

The kernel is flushing dirty pages quick enough to allocate more memory to influxdb.
My test is very hacky, I have a specific query that I run which sums up a few tags. I run this on a 100000 row Db, 500000 row Db. And 1000000 row Db.

I have a bash for loop sending the query locally with the influx client. Sleeps every 1 second. Normally latency of the request blocks past this, and script is actually running at the speed of query latency.
With three different queries running in the same fashion, I watch application memory fill cache and free, taking almost all memory.
I DO NOT see any signs of paging to disk, I used vmstat swap in and swap out metric to view.
I launch one more simultaneous repetitive query, and influx crashes- with a memory error message from influx.
I do not seem OOM run, and I see nothing. In dmesg or syslog. Making me think influx is handling all this, and crashes managing it's own memory, making me not want to use influx.

We need more information in order to diagnose what is going on.  Can you update the issue description with the instructions listed in our issue template?

Just confirmed, this behavior is not present in v0.9.6.
Same data, same tests, memory is solid, no steep increase or crash.

Is there any update on this? I am experiencing the same issues

@ctorres92 There is not enough information to diagnose this issue.  Can you run the following and attach them to the issue?
curl -o block.txt "http://localhost:8086/debug/pprof/block?debug=1"
curl -o goroutine.txt "http://localhost:8086/debug/pprof/goroutine?debug=1"
curl -o heap.txt "http://localhost:8086/debug/pprof/heap?debug=1"
curl -o vars.txt "http://localhost:8086/debug/vars"
iostat -xd 1 30 > iostat.txt
influx -execute "show shards" > shards.txt
influx -execute "show stats" > stats.txt
influx -execute "show diagnostics" > diagnostics.txt


Broken source release 0.0.12

The current source release is unbuildable due to missing dependencies:

there is no straightforward way to install or signal the absence of go-bindata (that can be resolved by a go get -u github.com/jteeuwen/go-bindata/... but it's not that immediate
the directory libapps is empty and the make fails, cloning manually from https://chromium.googlesource.com/apps/libapps in libapps solves the problem

how can i help fixing this? i would suggest that for the first problem a simple makefile failure prompting the user to install go-bindata (since she is building from source she must already have a working go env) might suffice.
For the second problem i am not sure you can simply ship the whole libapps dir, so maybe that can be fixed by either shipping the file or adding a git clone https://chromium.googlesource.com/apps/libapps libapps/ step...
let me know what you think!

@yudai any insight on this?

not working for me...

For the second problem i am not sure you can simply ship the whole libapps dir, so maybe that can be fixed by either shipping the file or adding a git clone https://chromium.googlesource.com/apps/libapps libapps/ step...

libapps is listed in .gitmodules, so git submodule update should work, too.
Unfortunately, this advice doesn't work for me either, same error…

Hi, thanks for feedback.
I added go get -u github.com/jteeuwen/go-bindata/... to Make file.
As for libapps, as @eush77 mentioned, you need to checkout the submodule.


Demonstration gif replacement,

Replaced the original pixelated gif demonstrating the cli with a new gif that is clearer and easier to read.

@RushanKhan1 - Post the GIF here in the comments please

@ankingcodes Sure, here you go:

@RushanKhan1 - Check the syntax errors all over the place. They shouldn't be there, there's something wrong with your python distribution,

@ankingcodes  Thanks for pointing that out! I looked into it and found out that the warning that showed up in the gif is a recent addition in python version 3.8, as can be seen in the release notes. Their compiler now checks if is and is not are used with certain types of literals, if found then the compiler raises a SyntaxWarning. They mention that it is better to use equality tests(!= and ==) over identity checks(is, is not) when comparing with literals. The primary problem is that the clint module that you are using used an identity check with a string literal in one of their files(prompt.py) which is the cause of the problem. I fixed that locally and that solved the problem so I thought of fixing that in the source but it seems that the project has been abandoned because the last commit was made 3 years ago. I will be updating the gif, however I suggest you go with an alternative of clint, that is more up-to date, something like: click or Python Fire since people using newer versions of python will face this problem too.

Here is the new gif:

@RushanKhan1 - LGTM ! Thanks !


[BUG] Full screen fails to activate

Describe the bug
Full screen sometimes fails to activate after a tiddler was closed while full screen
Expected behavior
No response
To Reproduce

Create a new tiddler and save it (name "Tiddler1").
Create another new tiddler. In this new tiddler activate full screen. Immediately quit without saving (press escape while in full screen)
Full screen in "Tiddler1" fails to activate.
To reset, recreate a new tiddler, which will be opened on full screen. Then quit the full screen from this new tiddler. You can now activate full screen on "Tiddler1".

Also happens (but maybe not every time) with existing tiddlers. For example on your demo :

Open tiddler "$:/config/AutoFocus". Activate fullscreen. Immediately quit (press escape while full screen)
Open "GettingStarted". Full screen fails to activate.
Open "$:/config/AutoFocus" which will be full screen. Deactivate full screen.
Full screen can now be activated in "GettingStarted"

Screenshots
No response
Configuration
Tested on local with tiddlydesktop 0.0.18
and on your demo : https://oeyoews.github.io/tiddlywiki-codemirror6/ with firefox 128.4.0esr
Additional context
It looks like a full screen state saved somewhere and not reset when quitting a tiddler.
I am not experienced enough to help more.

This is definitely a state issue because when the bug appears, deleting all tiddlers named $:/state/codemirror-6/fullscreen/Draft... solves the problem


import deadlock in pyzmq if used in another thread

If we have the following code
file1.py:
import zmq
from threading import Thread
context = zmq.Context.instance()
socket = context.socket(zmq.PUB)
socket.connect('tcp://localhost:12345')
#socket.send_json('{uncomment_and_work:True}')
class importLock(Thread):
    def run(self):
        socket.send_json('{}')

a = importLock()
a.start()

and run it from file2.py
import file1
This will cause the deadlock in python. If we uncommon send_json before spawning new thread it will not cause deadlock.
This is because of PR #721  and this commit that we import inside the function.
Importing in function is bad practice and not PEP8 , this change can cause the deadlocks to clients and my suggestion is to remove it.
I don't mind to open a new PR that will revert the change, but before that, I wanted to consult here and hear your opinion on the matter.
Cheers

I'm not necessarily opposed, but some of the statements here are inaccurate:

Importing in function is bad practice

I'm not necessarily opposed to the change, but this statement is untrue. Delaying rarely used and/or costly imports until they are going to be used is a common and sensible optimization in Python. That said, these particular rarely-used imports probably aren't costly enough to be worth delaying, so I think it's probably sensible to put them back to simple top-level imports.
The real source of the problem here, though, is triggering the launch of threads on import. That's very strongly recommended against, and the cause of the deadlock. It is absolutely not a valid assumption in Python that calling a function cannot trigger imports. There are lots of ways for nontrivial logic, especially with threads, during imports to cause problems and hangs. The first thing to do is to move the thread-launching code in your file1.py module into a function so that it doesn't get instantiated on import. This is the right thing to do regardless of whether the pyzmq imports change. If your module is also a script, this is the reason the if __name__ == '__main__': idiom exists.

I agree with the most of the parts!
Our specific use-case is that we use pyzmq as logging.handlers module.
We give that handler to other developers to use as they wish and that is beyond my control.
Another solution for this is to check if the import is locked (imp.lock_held()) and throw Exception if it is. But, considering that this is not heavy import, I'll make a PR with imports on top and let's start from there.