Slider ticks stacked when first loaded

I've implemented the slider in a modal in Angular, but the slider ticks are stacked one upon the other when the modal is first loaded. Once I click anywhere near or on it, it displays the distributed ticks as it should.

I use a directive to load the modal content dynamically.
value: number = 5;
options: Options = {
    floor: 0,
    ceil: 5,
    showTicksValues: true,
    ticksValuesTooltip: (v: number): string => {
        return 'Tooltip for ' + v;
    },
    stepsArray: [
        {value: 1, legend: 'None'},
        {value: 2, legend: 'Low'},
        {value: 3, legend: 'Average'},
        {value: 4, legend: 'Important'},
        {value: 5, legend: 'High'}
    ]
};

<ng5-slider [(value)]="value" [options]="options" style="width: 100%;">
Thanks.

If you display content dynamically, you should use manualRefresh to update the slider.

using manualRefresh  solved the issue for me.

I documented this problem more clearly as a known issue. Closing ticket.


Return the transaction fee in the  mempool response

Motivation
ZIP-401 weights transactions by their transaction fee:
https://zips.z.cash/zip-0401#specification
Design
This function already calculates the transaction fee - it can be easily modified to return it.
https://github.com/ZcashFoundation/zebra/blob/1ccb2de7c7049feebf41e03b1243939158817317/zebra-state/src/service/check/utxo.rs#L224-L227
Sub-Tickets
remaining_transaction_value needs the UTXOs spent by the block:

[ ] #2440

Hey team! Please add your planning poker estimate with ZenHub @conradoplg @dconnolly @jvff @oxarbitrage @upbqdn

This ticket's dependencies conflict with the NU5 block validation code freeze, so it needs to be done after NU5 testnet activation in sprint 19.


Improve psgpass support

Support for localhost, empty host
Support for password of dot (.)
See PasswordFromFile at fe-connect.c from libpq sources for reference.

+PGPASSFILE env variable https://www.postgresql.org/docs/9.3/static/libpq-envars.html


1581086, update image filenames part two 10-13 PM

Updates related to User Story 1581086.

@mairaw, this PR related to User Story 1581086 is ready for review.
There was a pretty big issue that cropped up in the CATs report: https://contentqacats.azurewebsites.net/CheckResults/2019101300007/Report/
You'll see these stats:

Test Case
Failed

Missing Alt text for image
47

Image file name without hyphen
6

Image file name length
40

All of those failures are coming from the index.md file in the root directory of the project. As expected, the entire MD file of the HubPage is written in HTML. My instinct is to leave all of those errors alone because this MD file is unlike any other in the project that I worked on and may not fit into the scope of the project.
Would you like me to address those failures? If so, would you like me to address them as part of this PR or shall I create a new PR dedicated to fixing the errors that are reported in the index.md file?

@BillWagner  I have incorporated your feedback. Please have a look. If everything looks good, feel free to sign-off.
If you notice anything else you'd like me to change,  please let me know.

Thanks @john-par This is ready, and I'll :shipit: now.


Update redis binaries

This PR includes up-to-date redis binaries. It also adds support for Mac OS on ARM. And it drops support for Mac OS on x86 and Windows on x86. Because I couldn't find any up-to-date binaries for Windows/Mac OS x86. But I can re-add the old 2.8.19 binaries for this if you want.
I tested the changes on several platforms to ensure the new binaries work as expected. Test results can be found here. As Mac OS on ARM isn't supported by Github actions, I tested it on codemagic.io:

I downloaded all the files from the original sources and checked them against the versions in the pull-request (not that I don't trust you or anything :))
$ sha256sum redis-server-6.2.7-linux-386
7439d339751e396cef7205a3169c96f1c53661f65d473b8d086e2d1826f48145  redis-server-6.2.7-linux-386
$ sha256sum ../plr_source/redis-server-6.2.7-linux-386
7439d339751e396cef7205a3169c96f1c53661f65d473b8d086e2d1826f48145  ../plr_source/redis-server-6.2.7-linux-386

$ sha256sum redis-server-6.2.7-linux-arm64
036a23aa65bfb31d2a048aa96c170b38c2fbd4f1de68ef0f9c3133dd4b1474cd  redis-server-6.2.7-linux-arm64
$ sha256sum ../plr_source/redis-server-6.2.7-linux-arm64
036a23aa65bfb31d2a048aa96c170b38c2fbd4f1de68ef0f9c3133dd4b1474cd  ../plr_source/redis-server-6.2.7-linux-arm64

$ unzip -j redis-stack-server-6.2.6-v5.catalina.x86_64.zip "bin/redis-server" -d .
$ mv redis-server redis-6.2.6-v5.catalina.x86_64
$ sha256sum redis-6.2.6-v5.catalina.x86_64
7a4eb450d90a6ce9a2c651cfc4a0613b980a270c6426cbb6fa42d6c3beec9ce8  redis-6.2.6-v5.catalina.x86_64
$ sha256sum ../plr_source/redis-server-6.2.6-v5-darwin-amd64
7a4eb450d90a6ce9a2c651cfc4a0613b980a270c6426cbb6fa42d6c3beec9ce8  ../plr_source/redis-server-6.2.6-v5-darwin-amd64

$ tar -zxvf redis-stack-server-6.2.6-v5.jammy.x86_64.tar.gz ./redis-stack-server-6.2.6-v5/bin/redis-server
$ sha256sum redis-stack-server-6.2.6-v5/bin/redis-server
1f716094e08a25faee2bc7626feb9e13464ed89018ac5c376c5e9cff06bdcf52  redis-stack-server-6.2.6-v5/bin/redis-server
$ sha256sum ../plr_source/redis-server-6.2.6-v5-linux-amd64
1f716094e08a25faee2bc7626feb9e13464ed89018ac5c376c5e9cff06bdcf52  ../plr_source/redis-server-6.2.6-v5-linux-amd64

$ unzip -j redis-stack-server-6.2.6-v5.monterey.arm64.zip "bin/redis-server" -d .
$ mv redis-server redis-server-6.2.6-v5.monterey.arm64
$ sha256sum redis-server-6.2.6-v5.monterey.arm64
c523aec5a9b6f565cff0271ef67f5c51fa83e1180e3e954ab5251b3cf6282b76  redis-server-6.2.6-v5.monterey.arm64
$ sha256sum ../plr_source/redis-server-6.2.6-v5-darwin-arm64
c523aec5a9b6f565cff0271ef67f5c51fa83e1180e3e954ab5251b3cf6282b76  ../plr_source/redis-server-6.2.6-v5-darwin-arm64

$ unzip -j Redis-x64-<IP_ADDRESS>.zip "redis-server.exe" -d .
$ mv redis-server.exe redis-x64-5.0.14.exe
$ sha256sum redis-x64-5.0.14.exe
79cd623a9999d75e944e8d2509547ddeee67a2c6c7b88d11d1137eb57fec10a0  redis-x64-5.0.14.exe
$ sha256sum ../plr_source/redis-server-<IP_ADDRESS>-windows-amd64.exe
79cd623a9999d75e944e8d2509547ddeee67a2c6c7b88d11d1137eb57fec10a0  ../plr_source/redis-server-<IP_ADDRESS>-windows-amd64.exe

And then I ran virus scans against them all with virustotal. Results here. Only windows binary shows 1 scanner complaining. I think thats a false positive.

Thanks!

Google says Microsoft stopped supporting 32bit on May 13, 2020. Not extremely long ago but 32bit still feels ancient to me. Whats your opinion on leaving 2.8.19 in for 32bit x86 windows only?

Hard to decide. But I'd probably not add the old binary. It looks like it's a security risk. And it should not be required by most users. And those who need it can still provide their own binary.

I downloaded all the files from the original sources and checked them against the versions in the pull-request (not that I don't trust you or anything :))

Good to see maintainers aware of security implications and double-checking things. :)

I ran dependency check and it also reports CVEs for the current version. But it's still better than 2.8.19. I'm going to leave it out.


Snowplow CLI: INTERNAL_ERROR should be recoverable

This kind of job status:
Snowplow data pipeline: TERMINATING [INTERNAL_ERROR] ~ elapsed time n/a [ - ] - 1. Elasticity S3DistCp Step: Shredded HDFS -> S3: CANCELLED ~ elapsed time n/a [ - ] - 2. Elasticity Scalding Step: Shred Enriched Events: CANCELLED ~ elapsed time n/a [ - ] - 3. Elasticity S3DistCp Step: Enriched HDFS _SUCCESS -> S3: CANCELLED ~ elapsed time n/a [ - ] - 4. Elasticity S3DistCp Step: Enriched HDFS -> S3: CANCELLED ~ elapsed time n/a [ - ] - 5. Elasticity Scalding Step: Enrich Raw Events: CANCELLED ~ elapsed time n/a [ - ]):

should be treated as a bootstrap failure (i.e. automatically restarted).

done, closing


Added support for all documented attributes for protecting a repository branch

Example use case:
$projectId = "47037290"
$Name = "main"
$PushAccessLevel = "40"
$MergeAccessLevel = "30"
$UnprotectAccessLevel = "30"
$AllowForcePush = $true
$CodeOwnerApprovalRequired = $true

$hash1 = @{
    user_id = 22882083
}
$hash2 = @{
    user_id = 1264703
}
$hash3 = @{
    user_id = 6204519
}
$AllowedToPush = @($hash1,$hash2)
$AllowedToMerge = @($hash2)
$AllowedToUnprotect = @($hash3)

$protectParams = @{

    ProjectId                 = $projectId
    Name                      = $Name
    PushAccessLevel           = $PushAccessLevel
    MergeAccessLevel          = $MergeAccessLevel
    UnprotectAccessLevel      = $UnprotectAccessLevel
    AllowForcePush            = $AllowForcePush
    CodeOwnerApprovalRequired = $CodeOwnerApprovalRequired
    AllowedToPush             = $AllowedToPush
    AllowedToMerge            = $AllowedToMerge
    AllowedToUnprotect        = $AllowedToUnprotect
}

Protect-GitlabBranch @protectParams

In favor of the change, but I don't like exposing the raw API mechanics (enum literal values, hash structures, etc)
In other parts of the API, we've accepted access level by name (with a ValidateSet for autocomplete/input-validation)
As for the AllowedTo properties -- a little harder to model as there are 3 possible shapes and 3 different fields -- let me 🤔 about that for a bit

the granular/specific allowances feels like an uncommon scenario (in fact it was moved to Premium edition in 13.9), I know personally, I've always done role-based access (not specific user/groups)
as such, I'm inclined to go with the approach you had.
I'll keep an eye out for the integer -> string commit and will merge.
thanks again for contributing!

OK, understood. I actually need the granular levels for an automation requirement at work, hence the need for this contribution.....
Have updated with a more friendly way to supply the access levels. Based the approach on work you've done elsewhere in the project.

This is now published
NOTE: I made a modification to allow the input objects to be PascalCase as that is more idiomatic / consistent with the rest of the CmdLets in this library


[bug 1071044] Initial travis setup.

If I did things right, this just might trigger a Travis build.

Looks good initially. I'm excited about this!

Feedbacked so far :point_up:
Right now it's peep installing compiled.txt, requirements.txt and dev.txt. I don't know if that has precedence over vendor or vice-versa. Maybe I should just peep install compiled.txt and dev.txt in the default build?

This looks great. Can you squash these? Then let's land it and tell jenkins to bugger off!

yay travis is happy!

The bug for travis was bug 1079357 #fail :sob:


Deliver ICU via dynamic delivery on Android API 21+

Might require https://github.com/flutter/flutter/issues/22102
See https://developer.android.com/guide/app-bundle/dynamic-delivery
We could also probably come up with a way to do this for iOS.
We should be able to split ICU so that it only contains individual locales in it, and then only ship those to users with those locales on their system.  This could reduce base APK size.
/cc @xster @goderbauer @jason-simmons @blasten @matthew-carroll

@dnfield how much saving do you estimate this feature will have?

Also related to: https://github.com/flutter/website/issues/2215

I don't have hard numbers.  @goderbauer has a doc with the sizes of various locales - it ranges from 50kb to 100kb per locale.  We've also trimmed out some locales to save size, which we could presumably add back under a scheme like this.
I'm also not sure that dynamic delivery is the best way to achieve this, since it's very specific to Android. It may be better to come up with a more generic solution in which there is some storage bucket you can opt in to using that has the ICU data, and Flutter knows how to use it.

Are these locales shipped with the Framework, or are they defined by the app developer, or both?

They're part of ICU, shipped in the image

I'm going to close this. I don't think this is the best approach.
We probably want to support dynamic loading for other reasons, but I'm going to file a different bug for ICU.

https://github.com/flutter/flutter/issues/50292


Build wheels for Apple Silicon

Follow-up from #354, #365

Closing through #365 , ARM64 wheels are now built for Python 3.8 and 3.9.

It seems that it is not working yet, there are no GEOS libraries inserted by delocate. Reopening.


[PE-D][Tester A] Misleading error message when extra fields are provided

Adding extra fields not required for the command leads to unexpected error messages as it becomes part of the previous field. This may lead the confusion for the user if they do not realize they have put an extra field, as error message is indicating that the value of a certain field is invalid.
I think a particurly plausible scenario is when the user uses addentry as addlog, adding the l/ field and being confused by the error message.
Suggestions:

Check for extra fields within the command and display invalid format if found.

Examples:
addentry i/T1355313G d/29 Feb 2022 l/asd

addentry i/T1355313G l/asdf d/29 Feb 2022

Labels: severity.Low type.FunctionalityBug
original: Airiinnn/ped#10

Perhaps we could specifically mention it in the UG (anything after d/ will be viewed as date), since this is just how AB3 works, we dont really have a way to fix it atp


Using Vite with custom Accessor classes

Recently I migrated a Typescript app from CRA to Vite that contained some classes that used Accessor decorators as described  here. The problem, was that Vite failed to serve those classes, because Accessor decorators must be transpiled by typescript.
As solution, I have created a simple configurable Vite plugin, which allows to transform classes with custom Accessor decorators on the fly using typescript. I thought this might be useful for someone else in the future, so I wanted to share this plugin here:
vite-arcgis-plugin.ts
import tsc from 'typescript';
import type { Plugin } from 'vite';

function getCompilerOptions(tsconfig: string | undefined) {
  if (!tsconfig) {
    return {};
  }
  const { config } = tsc.readConfigFile(tsconfig, tsc.sys.readFile);
  return config.compilerOptions;
}

export interface ArcGISConfig {
  transpile: (id: string) => boolean;
  tsconfig?: string;
}

export function arcgis(config: ArcGISConfig): Plugin {
  const { transpile, tsconfig } = config;
  const compilerOptions = getCompilerOptions(tsconfig);

  return {
    name: 'arcgis',
    async transform(code, id) {
      if (transpile(id)) {
        const transpiledCode = await tsc.transpileModule(code, {
          compilerOptions,
        });
        return {
          code: transpiledCode.outputText,
          map: transpiledCode.sourceMapText ?? null,
        };
      }
      return null;
    },
  };
}

Inside vite.config.ts the plugin can used in the following way:
import { defineConfig } from 'vite';
import { arcgis } from './vite-arcgis-plugin';

export default defineConfig({
  plugins: [
    // other plugins
    arcgis({
      transpile: (id) => /packages\/arcgis/.test(id),
      tsconfig: './tsconfig.json',
    }),
  ]
});

Thanks @sebastianfrey. I was able to get Accessor decorators working in a test app by adding the following to the tsconfig.json using Vite 5.3.4 and TypeScript 5.5.3:
    "experimentalDecorators": true,

I'll add a note to that SDK documentation page you mentioned above. I didn't see it mentioned anywhere that the core API is currently using legacy decorators.
For reference, in case others come across this thread, the error message will be similar to this: Expression expected (Note that you need plugins to import files that are not JavaScript).

Hi @andygup, thanks for your feedback on this.
Some additional notes:
For me the  error message Expression expected only occurred when using @arcgis/core with @vitejs/plugin-react-swc.
When using @vitejs/plugin-react for transpiling React and JSX the error message is: [plugin:vite:react-babel] /path/to/file/which/useses/decorators.ts: Support for the experimental syntax 'decorators' isn't currently enabled
For @vitejs/plugin-react-swc it is enough to set tsDecorators to true in the react swc plugin options. No plugin for processing is required here.
import reactSwc from "@vitejs/plugin-react-swc";

export default defineConfig({
  plugins: [
    reactSwc({
      // Requires experimentalDecorators in tsconfig
      tsDecorators: true,
    }),
  ]
});

Note: It's required, as stated out by @andygup, to set experimentalDecorators to true in tscofnig.json.
But for @vitejs/plugin-react things are different. The error message suggests, to add @babel/plugin-syntax-decorators to solve the issue, but unfortunately @arcigs/core requires that decorators are transpiled with typescript.

For more details see   https://github.com/Esri/feedback-js-api-next/issues/169#issuecomment-1197333777.

So when someone uses @vitejs/plugin-react, the shared arcgis plugin from this thread can be leverage when using Accessor decorators.


Evaluation scripts

Hi,
thanks for the interesting work. Could you maybe share the evaluation scripts as well? Thanks a lot!

Hi SnowdenLee,
Thank you for your interest to our work! We directly used the detection code from detrex repo (https://github.com/IDEA-Research/detrex) to do the object detection and evaluations. We will release these scripts soon, please stay tuned.

Hi SnowdenLee,
Sorry for the late reply; we have updated the repository. You can find the evaluation code in ``attention_optimization/stable-diffusion/evaluation''. The README also include how to install environment for the evaluation script. Thank you.


The model scored poorly after annotating the "detection adjustment" code

Hi, this is an amazing job.
Here I come across a small problem.
On MSL dataset, the model performed good, looks like:
======================TEST MODE====================== Threshold : 0.0017330783803481142 pred:    (73700,) gt:      (73700,) pred:  (73700,) gt:    (73700,) Accuracy : 0.9853, Precision : 0.9161, Recall : 0.9473, F-score : 0.9314
But after  I annotated the "detection adjustment" code, the score was poorly, looks like:
======================TEST MODE====================== Threshold : 0.0017330783803481142 pred:    (73700,) gt:      (73700,) pred:  (73700,) gt:    (73700,) Accuracy : 0.8866, Precision : 0.1120, Recall : 0.0109, F-score : 0.0199
And I'm sure only the "detection adjustment" code was annotated.
Can you help me out of this problem?
thx.

Thanks for your interest.

We have especially clarified this in the paper (Section 4 Implementation details).

It is notable that the adjustment operation is widely used in previous papers. Thus, we adopt this for a fair comparison with other methods.

Sure, all the comparing methods adopt this adjustment strategy for evaluation.

That's good. Thx.


[VSCode] Section 1 - Setup of Java JDK

Currently most online tutorials use a coding pack to download the JDK, extensions.
However, CS2103T uses Java 11, hence the versions may cause an issue via the automated install. which may install Java 17.
We can break this down into

Download JDK manually from Oracle
Download the extensions (may not include Gradle, as I was thinking of putting it in separate section)
Setup a main project (just for completion and running) using the VSCode java commands

@UdhayaShan1 We are moving to Java 17 from the coming semester. However, Mac users still need to install a specific Zulu JDK+FX distro, as they did for Java 11.

Noted, I think using the coding pack will make it alot easier in this case

Noted, I think using the coding pack will make it alot easier in this case

Perhaps it is still good to describe how to install/use a JDK that is not the one included in coding pack? Especially given that the latest Java LTS version is 21.

The coding pack installs Java 17 by default however I am not sure if this might change in the future.
I will continue with a manual installation guide instead


Nested populate timeline?

  I think it has potential to be the best ORM for node.js.
I see some work is currently being done to allow nested populate/joins.  Any rough time estimates on when this would be ready?

+1

People have been requesting this for over a year now.

I just moved back to Sequelize.

Hi, AFAIK there is no timeline for this yet. From what I can gather this is a rather difficult change due to waterline associations supporting associations across different adapters/databases. That challenge is what has been holding this. For more on this please refer to #308 and continue the discussion there.
Closing this as a duplicate.


Regex conditional

I was trying to create my own algorithm to parse user's mathematical equations, and falling into RegExp features, found that it doesn't support conditional, I think JavaScript, for example, doesn't have that, but I really think this could be a great feature.
Here is a page that explains what this feature would do with many details.
Transcribing this part about group conditionals for a simple explanation
If we have ^(START)?\d+(?(1)END|\b)
Here is how this works:

The ^ anchor asserts that the current position is the beginning of the string
The parentheses around (START) capture the string START to Group 1, but the ? "zero-or-one" quantifier makes the capture optional
\d+ matches one or more digits
The conditional (?(1)END|\b) checks whether Group 1 has been set (i.e., whether START has been matched). If so, the engine must match END. If not, the engine must match a word boundary.

The net result is that the pattern matches digits that are either embedded within START…END at the beginning of the string, or standing by themselves at the beginning of the string.
To achieve the same effect without a conditional, we could use ^(?:START\d+END|\d+\b), which forces us to repeat the \d+ token.

I was able to implement your example in my use case. Closing this


Last release was in 2017, will there be a new one?

Hello
It seems that the last release into maven repositories was in 2017. Will there be a new one?
I just noticed that I'm still using my own internal FixtureExtension on my private projects and would like to use one published publicly.
Thank you!

Yes, this is long overdue. I'll try to get a release together during next week.

Hello, just a little bump on that issue to know if it would be possible to publish a new version.

Interesting, @philipwhiuk I'm not sure what the current status of these projects are from Flextrade's perspective, but I'm more than willing to help out with things like releases if you're short on resources.

Hi. A new release would be great, since there are fixes that would be valuable to be able to use, like generic circular extension handling etc.


fixes #1

Sir, this is my first time on GitHub please guide me through any error I make, Thank you.

Hi there, can you please sync and do the changes again. Sorry for the trouble, there are many conflicts .
Thanks. There is no error though . Keep up the good work :+1:


Functions requiring number coordinates give incorrect error if given numbers as strings

If you pass coordinates as strings, you get an incorrect error message:
import pyautogui
pyautogui.moveTo('1', '2')
FileNotFoundError: [Errno 2] No such file or directory: '1'

Functions that require numbers should either try to convert the input to a number or give a correct error message.

I have made a commitment fixing your issue here is my approach  #795


Is this effectively the power curve?

Hi @ptrbortolotti ,
I was looking at this schema from a wind analyst point of view and I am wondering if this section is effectively the power curve of the turbine?

Cheers,
Stephen

Hello Stephen,
thank you for working with windIO.
Among my late to-dos, there is updating the windIO schema. Some sections are out of date and have been updated elsewhere, for example in the WISDEM repository (here)[https://github.com/WISDEM/WISDEM/blob/master/wisdem/inputs/geometry_schema.yaml]. The control section is one of them, so those fields are no longer up to date with our workflow. This said, a few months ago the team of IEA Wind Task 37 agreed that we should have outputs listed in the schema, not just inputs (as it is done today), so we will work to add the power curve.
A long answer to say that the power curve field is not yet provided in the turbine ontology windIO. This said, if you're looking for a specific power curve of a reference wind turbine I can try to help.
Best regards,
Pietro

Hi Pietro,
Thanks for the quick response. I am aware of three different work streams that have or are looking at producing a wind turbine power curve schema. These are Octue, TimWind and IEC. I will be working to try and merge them all together to get a consistent single digital power curve most likely and hopefully using the Octue as the foundation for the other two. This Task 37 came up in conversation in something completely different so I checked it out and thought this might have something already. There would be no point reinventing the wheel if this could do what would be required from a wind analyst point of view. From the sounds of it Task 37 doesn't quite have it but you will need something so maybe we can work together to make sure we develop something that satisfies both.
To give you some context about myself I work with @Dynorat on Task 43.
Cheers,

Hi Stephen,
In the plant ontology, not yet merged into master, there's a representation of a wind turbine more aligned with your perspective, which has power curve etc defined:
https://github.com/IEAWindTask37/windIO/blob/feature/plant_ontology/windIO/plant/turbine.yaml

Hi @fzahle ,
That is most definitely more like it. Thanks for pointing me in that direction!
It looks good. It doesn't look like it can handle more than one power curve though e.g. turbine OEMs are providing power curves for various air densities and then for different noise modes. There could be 10 to 20 power curves for the different air densities and then ~6 noise modes making up 60 to 120 power curves that we need to transfer/store.
When something starts moving with one or all of those 3 work streams I'll reach out. I found the Octue digital power curve in case you are interested https://refs.schema.octue.com/windpioneers/power-curves/0.0.1.json This and the WindIO are great starting points.
Thanks,

I think the FLORIS team, and co-developer of the farm simulation ontology, is actively wrestling with this issue.  Tagging @bayc in case he has an elegant solution already.

Thanks @gbarter for looping me in here. I am working on supporting a multiple Cp/Ct definition for FLORIS, but don't have anything released yet, and would need to work it back into the ontology. I can update here when I do have something. In the mean time, @fzahle pointed to the most current version of a power curve schema.

Thanks all.
Sounds like we will all revert back.
Looking forward to it.

Hi @fzahle ,
That is most definitely more like it. Thanks for pointing me in that direction!
It looks good. It doesn't look like it can handle more than one power curve though e.g. turbine OEMs are providing power curves for various air densities and then for different noise modes. There could be 10 to 20 power curves for the different air densities and then ~6 noise modes making up 60 to 120 power curves that we need to transfer/store.
When something starts moving with one or all of those 3 work streams I'll reach out. I found the Octue digital power curve in case you are interested https://refs.schema.octue.com/windpioneers/power-curves/0.0.1.json This and the WindIO are great starting points.
Thanks,

As an update, the candidate for the IEC61400-16 power curve schema has been released. Expect some changes over hte coming 18 months but it's pretty well consolidated at this point:
https://github.com/octue/power-curve-schema/releases


As a user, I can update the application status of candidates

...so that I can advance a candidate to another status.

Completed through edit command.


[CT-1254] [Bug] Unable to install via pip on Ubuntu

Is this a new bug in dbt-snowflake?

[X] I believe this is a new bug in dbt-snowflake
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Following the steps on this page to install dbt-snowflake on Ubuntu does not work as of 26 September: https://docs.getdbt.com/dbt-cli/install/pip. It returns errors when installing the dependencies when executing the command pip install dbt-snowflake.
The errors relate to deprecations caused by the release 22.1.0 of the module pyOpenSSL.
This happens for dbt-snowflake version 1.0.0 and for subsequent versions.
Expected Behavior
A newer version of pyOpenSSL was released (22.1.0), which has breaking changes. Because snowflake-connector-python is requiring a version <23.0.0 this update is used now. I would expect that the requirement is 22.0.0 to not install the version containing the breaking changes or that the deprecated functions are not being used.
Steps To Reproduce

Run the following command according to the dbt documentation on an Ubuntu machine to install Python and other dependencies:

sudo apt-get install git libpq-dev python-dev python3-pip
sudo apt-get remove python-cffi
sudo pip install --upgrade cffi
pip install cryptography~=3.4

Next install dbt-snowflake=1.1.0 (or another version)

python3 -m venv dbt-env
source dbt-env/bin/activate
pip install dbt-core==1.1.0
pip install dbt-snowflake==1.1.0

This should reproduce the failing installation.
Relevant log output
File "/usr/share/python-wheels/urllib3-1.25.8-py2.py3-none-any.whl/urllib3/contrib/pyopenssl.py", line 46, in <module>
  File "/home/vsts/work/1/s/dbt-env/lib/python3.8/site-packages/OpenSSL/__init__.py", line 8, in <module>
    from OpenSSL import SSL, crypto
  File "/home/vsts/work/1/s/dbt-env/lib/python3.8/site-packages/OpenSSL/SSL.py", line 19, in <module>
    from OpenSSL.crypto import (
  File "/home/vsts/work/1/s/dbt-env/lib/python3.8/site-packages/OpenSSL/crypto.py", line 3224, in <module>
    utils.deprecated(
TypeError: deprecated() got an unexpected keyword argument 'name'

Environment
- OS: Ubuntu 20.04
- Python: 3.8.10
- dbt-core: 1.1.0
- dbt-snowflake: 1.1.0

Additional Context
Workaround is available:
Run pip install pyOpenSSL==22.0.0 before running pip install dbt-core==1.1.0.

Confirming that this is impacting other adapters such as dbt-redshift as well, and that the workaround addresses them.
Thank you for posting this, @cverhoef !

Thanks for posting @cverhoef, and sorry for the delay following up!
Am I right in thinking that this is really an issue in snowflake-connector-python, since that's where the pyOpenSSL requirement is defined, and where the deprecated methods are being called?
@r-moctezuma I'm less sure why this would be cropping up in dbt-redshift as well. It doesn't look like pyOpenSSL is a dependency of boto3, or of dbt-core. Could you include the stacktrace of the error you've been seeing?

Am I right in thinking that this is really an issue in snowflake-connector-python, since that's where the pyOpenSSL requirement is defined, and where the deprecated methods are being called?
That seems to be indeed the case.

Closing as this is not on our side. Please comment below if need be and I'll open it again.


Catch and handle InvalidAuthenticityToken errors

I am so very, very tired of receiving these emails and I'm sure users are equally tired of losing the replies they're writing.

Does not presently handle literally anything other than replies. Should probably someday be extended to handle posts, but I vote that waits on the post-to-replies stuff.

Note: will have trouble with two tabs of replies being submitted at the same time if both are invalid. Shouldn't happen often. User can use "back" to get their reply back, as they always could before, so this should be a pretty clear improvement.
(Thank you :D Finally getting rid of these!)


[recorder] Add tests for full schema migration

Description:
It doesn't contain any assertions based on inspecting the modified schema, but it will at least confirm the migration logic executed without errors.

This PR is ready for review now. It should ideally be picked onto 0.38, since it has a small change to the migration logic. It shouldn't affect the final db structure either way, but it would be good to make sure.

Will make sure to cherry pick it.

cherry-picked


AABB::Grow incorrect doc or code

Operating system or device - Godot version:
All
Issue description (what happened, and what was expected):
AABB.grow_by increase double amount https://github.com/godotengine/godot/blob/a895e2e372c9df2a9972f38134ae0ea9c8bf45a8/core/math/aabb.h#L389-L391
Documentation version

Return a copy of the AABB grown a given amount of units towards all the sides.

Steps to reproduce:
Link to minimal example project (optional but very welcome):

yes, that's exactly what it does, and the code is fine
On Tue, Aug 9, 2016 at 6:14 PM, Dima Granetchi<EMAIL_ADDRESS>wrote:

Operating system or device - Godot version:
All
Issue description (what happened, and what was expected):
AABB.grow_by increase double amount https://github.com/
godotengine/godot/blob/a895e2e372c9df2a9972f38134ae0e
a9c8bf45a8/core/math/aabb.h#L389-L391
Documentation version
http://docs.godotengine.org/en/latest/classes/class_aabb.html#class-aabb-grow
Return a copy of the AABB grown a given amount of units towards all the
sides.
Steps to reproduce:
Link to minimal example project (optional but very welcome):
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/6092, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z2w7aq3dcQEB00oPBg0-_HY7agIsXks5qeO2egaJpZM4Jgh0X
.

Hm, my bad. Thanks

@profelis The trick is that you are pushing each side by a given amount, so you have to move the start and the end respectively. But since it is size, not end, you would move it by twice the amount, to account for the changed position.


Updated version of conda to 4.12.0

The main reason for this update is that this version supports M1 mac (MacOSX-arm64).

Cool, thanks for the PR.
What about updating it even further to the newest version, 22.9.0 (latest after version numbering change) or 4.14.0 (latest before version numbering change)?

@spietras
It seems Miniconda is only advertising 4.12.0 in its homepage. That's why I thought that version was the latest one. Also, in the conda channel, the latest version of conda is still 4.12.0. So I wonder if we should keep 4.12.0 for now.
I updated Miniforge version to match Miniconda's (4.12.0-2 , which is the latest 4.12.0 according to the conda-forge channel: https://conda-forge.org/miniforge/).

@spietras does it make sense to push a new release to include this change?

Sure, I will do it soon

@sfc-gh-zpeng Done: https://github.com/spietras/rules_conda/releases/tag/0.2.0


Fyle 1x0eqtg : Approve Report Popup design

fix lint issues and change the policy violation info icon to the yellow triangle one, this icon is information, let us change it to a warning


Serve static

If you write npm run start:front, Script in package json should remove current build in /server, create a new one in /client, move it into /server, then launcher server on :3000 with the folder build loaded in module servestatic
I create init:front to generate build the first time since you can't remove the old one ( it doesn't exists)

Added server/build to gitignore.
Added a fixed "homepage" parameter to tell React where the root for all resources is located on the server.


Make specifications for the valve object

Do we want to use a two state solenoid valve, analog valve, etc.?
Define the specifications (parameters, etc.)

I'd start with a 2 state valve and keep analog for a next module/object

Specifications, parameters, and data item definitions need to reference an existing standard (or alternatively a real valve that was built to a standard). There are lots of standards for valves and none of them are open access as far as I can tell, so the primary concern here is not to invent a new, one-off definition or data model for a valve.
Could also use an off the shelf valve model from a scada vendor or spec sheet from a valve manufacturer.

The definition of the inputs, outputs and UDTs will come back a couple of times (specs, code, documentation, ...).
Would it make sense to define this part in a machine-readable format? (csv, json, ...)
So then we only need to manage one source, and everything else gets updated automatically.

I agree that we should define the valve information in a central location in machine-readable format and have that used for the areas of the project that require the information. I am good with using json but let's see what others think?

+1 to start with JSON

Ok let's use json

... or yaml?
I took the example from @durinwinter:
https://github.com/Open-Mobile-Robotics/open-process-library/blob/ontology/ontology/extend_ontology.md
And applied it to the DMC valve:
namespace: process_automation
entities:
  - name: TwoStateSolenoidValve
    description: "A function block for controlling a two-state solenoid valve."
    fields:
      - name: tInTimeout
        type: time
        description: "The amount of time before an error condition triggers an error."
      - name: iInMode
        type: int
        description: "Device mode input."
      - name: bInOpen
        type: bool
        description: "Open input."
      - name: bInClose
        type: bool
        description: "Close input."
      - name: bInReset
        type: bool
        description: "Reset input."
      - name: hwInAddress
        type: hardware_address
        description: "Hardware address input."
      - name: bInSimulate
        type: bool
        description: "Enables software simulation of device."
      - name: udtHMI_ValveControl
        type: udtHMI_ValveControl
        description: "HMI control parameters."
      - name: bOutOpen
        type: bool
        description: "Output indicating valve is open."
      - name: bOutClose
        type: bool
        description: "Output indicating valve is closed."
      - name: bOutError
        type: bool
        description: "Output indicating an error condition in the valve."
      - name: udtError_Valve
        type: udtError_Valve
        description: "Error UDT with one bit for every type of error."

Error UDT:
namespace: process_automation
entities:
  - name: udtError_Valve
    description: "User Defined Type for valve error states."
    fields:
      - name: ValveStuckOpen
        type: bool
        description: "Valve is stuck open."
      - name: ValveStuckClosed
        type: bool
        description: "Valve is stuck closed."
      - name: NoFeedbackSignal
        type: bool
        description: "No feedback signal from valve."
      - name: GeneralFault
        type: bool
        description: "General fault in valve."
      - name: HardwareFailure
        type: bool
        description: "Hardware failure detected."

HMI UDT:
namespace: process_automation
entities:
  - name: udtHMI_ValveControl
    description: "User Defined Type for HMI control of valve."
    fields:
      - name: iMode
        type: int
        description: "Current mode of the valve."
      - name: iErrorCode
        type: int
        description: "Error code for the valve."
      - name: bOpenCommand
        type: bool
        description: "Command to open the valve from HMI."
      - name: bCloseCommand
        type: bool
        description: "Command to close the valve from HMI."
      - name: bResetCommand
        type: bool
        description: "Command to reset the valve from HMI."
      - name: bFeedbackOpen
        type: bool
        description: "Feedback indicating valve is open."
      - name: bFeedbackClosed
        type: bool
        description: "Feedback indicating valve is closed."
      - name: bError
        type: bool
        description: "Overall error state of the valve."

How about this approach?


Improve acceptance rules

Feature request
It would be beneficial to add new rules to the acceptance tests. Currently, two rules are tested:

Does the validator that uses the new code contribution generate more new errors than allowed?
Were there too many corrupted sources/datasets during validation?
Although these rules are fundamental to the acceptance tests, other aspects are not considered: disappearing errors or warnings, unusual info notices, etc.

Is your feature request related to a problem? Please describe.
Specifically in #1188, the acceptance tests passed, even though the initial implementation prevented the validator from checking most of the validation rules. The reports generated did not contain any errors or warnings. Also, the reports contained the unknown_file info notice for required files such as stop_times.txt. Although the acceptance tests were not originally designed to cover this use case, it would be nice if they did.
Proposed solution
First, I think adding two new rules would be helpful:

Are too many errors disappearing?
Are too many warnings disappearing?

Another potential additional rule would be

Do the reports contain the unknown_file notice for the required files?
since this is an indicator of a problem, but it is very specific.

Thanks for opening this!
There is another issue about a next iteration on the acceptance tests: #1076. This one isn't a duplicate, both flag different improvements to be made.

I was looking at the acceptance test implementation and I noticed that there is apparently code in the acceptance_test.yml to post a comment to the pull request with acceptance test status.  I've never actually seen this in action before.  Does it actually work?
Asking because I was taking an initial stab at improving the logic here and was thinking of refactoring some things, but I wanted to make sure I understood the existing behavior first.

Oh, it looks like it's working when PRs are made from this repo (see here and here), but not from forks.
Looking more closely to the run logs, it looks like the problem is related to the GitHub token. Here (from our repo) vs here (from a fork).
This is because the token is accessed via a secret. To the best of my knowledge, GitHub disables using secrets in workflows originating from forks. @isabelle-dr How valuable do you think the comment is? Could we refactor the acceptance tests without it?

Well, we can definitely improve the acceptance test without fixing the comment issue.
That said, I was looking at this method in the comparator and I think it could definitely be improved a bit.  I was also thinking of combining the acceptance_report.json and sources_corruption_report.json into one combined report (not sure why they need to be separate?).  This would have some implications for the commenting code but i'm sure I could keep it working the same either way (even if it doesn't actually work for me :)

I agree with you - I thought the same thing looking at the checkRuleValidity method. About combining the reports. I don't think they need to be separate, that's how it was before I started working on the validator, so merging them works for me. @isabelle-dr do you have any objection?

How valuable do you think the comment is?

I'd say pretty valuable, the initial idea was to have something user-friendly to see the impact of a PR, and how this impact might change as the contributor is sending commits. It makes it easy to trace stuff back. See it kind of in action in #1083.
The scope of this test changed as we were working on it (see this comment that followed a discussion with @asvechnikov2) and I see value in having in this validator:

tests to make sure everything is working properly
the ability to analyze the impact of a new piece of code - this is more functionality to me whereas the above is about safety & stability.

These two "tests" might contain similar checks (e.g. see if many additional / disappearing errors) but we won't want to run them at the same time, and their output might not be used in the same way.
The first one is simply blocking a merge, whereas the second could be used ad-hoc by the developer, and the results would be looked at in the review process with follow-up actions (inform agencies and consumers concerned, make it a major release, etc).
No strong opinion on combining the report, this seems like a good idea.

This answer is also related to https://github.com/MobilityData/gtfs-validator/issues/1233


Cargo update hangs with a specific configuration of dependency crates

It appears to be a some kind of a livelock. It never prints anything after Updating registry https://github.com/rust-lang/crates.io-index, but if I enable the tracelog, it seems to be doing copious amounts of... something. Eventually I stopped it with ctrl-c. Here's a gist of the tracelog: https://gist.github.com/golddranks/3c8bfb3dfe7b8e26b8052cdfd02af7da
Here's a repository that triggers the behaviour for me. I tried it on two networks, but unfortunately I haven't been able to try it on multiple computers. I also tested it on the latest nightly, latest stable (1.20) and the stable before that (1.19). They all seem to trigger it. I'll be curious to see if it hangs on other people's computers too. https://github.com/golddranks/cargo_test
This affects my daily work so hopefully this gets resolved soon. First of all, I'm curious to hear whether it happens on other computers too!

I got a confirmation that it happens on other people's computers too. It seems that it happens with the combination of the crates rust-s3 and postgres in the dependencies. Updated the demo repository.

Sounds like #4066

Looks like this is caused by the update of rust-s3 from 0.6.1 to 0.6.2. I'm experiencing the same issue with the aws-sdk-rust crate which hasn't been updated for some time. My guess is that they have some dependency in common that causes the issue.
You may want to explicitly use rust-s3 0.6.1 for now:
rust-s3 = "=0.6.1"

@golddranks I looked at it a bit closer, the generic-array crate appears to cause the issue. Looks like postgres 0.15 depends on 0.7 which conflict with some of the other dependencies.
Generic-array has been updated and the next release should fix the issue.
You can directly use the git repository from Cargo.toml if you want:
postgres = { git = "https://github.com/sfackler/rust-postgres" }

It seems that rust-s3 0.6.2 contained breaking changes. I reported the issue: https://github.com/durch/rust-s3/issues/18
Some takeaways:

A re-affirmation that https://github.com/rust-lang/rfcs/pull/1977 is a very valuable RFC to have :)
Also having tooling that helps reasoning with API changes and version bumps would be valuable.
I don't understand why mismatching versions of generic-array often break the build even though any types of it are not exposed in the API. I'd be happy if someone could enlighten me.
Cargo should try and have some heuristic to fix https://github.com/rust-lang/cargo/issues/4066

Closing this issue.

I encountered another breaking change with crates updating to generic-array 0.8 which brought me to reopen this issue.
Is there a some reason that cargo can't find compatible versions of the crates? generic-array seems to induce the breakage, but it isn't a public dependency of the crates as far as I know, yet cargo seems to consider it as such. Why?

This is likely https://github.com/rust-lang/cargo/issues/4066

Closing this since it sounds like it will be solved by solutions to #4066 and/or implementing public/private dependencies.

For the record, this was caused by generic-array having a needlessly strict dependency constraint: https://github.com/fizyk20/generic-array/issues/49#issuecomment-329170351


⚠ Bofrost.at has degraded performance

In cb9e353, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1465 ms

Resolved: Bofrost.at performance has improved in dcee78e after 19 minutes.


feat(v2): allow hiding docs table of contents

Motivation
I want to be able to hide the table of contents for Infima docs where the main content width is not wide enough. Example: https://facebookincubator.github.io/infima/docs/layout/grid
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

In fact, I moved hide_title in my docs versioning PR which includes major performance gain on metadata processing. https://github.com/facebook/docusaurus/pull/1983/files https://github.com/facebook/docusaurus/blob/31255fffb1dfde6e235a190b4f49cdfa8c406869/packages/docusaurus-theme-classic/src/theme/DocItem/index.js#L66-L68
Currently, our metadata has a lot of dynamic object construction like using delete.
Example:
In the below example, delete o.x does a lot more harm than good behind the scenes, as it changes o’s hidden class and makes it a generic slow object.
var o = { x: 1 };
delete o.x; // true
o.x; // undefined

It's better to do


Update README.md

Files associated with bugs
There's no suspicious file found
Files associated with tickets
FilenameTicketsREADME.md988255

Files associated with bugs
There's no suspicious file found
Files associated with tickets
There is no previous tickets found

Files associated with bugs
There's no suspicious file found
Files associated with tickets
There is no previous tickets found

Files associated with bugs
There's no suspicious file found
Files associated with tickets
There is no previous tickets found


x/yRot vs pitch/yaw

for describing rotation, mojang likes x/yRot while we mostly use pitch and yaw. i believe that we should move to match mojang here

hm i prefer pitch and yaw

I'm going to drop my two cents here and agree with Oro. It makes more technical and intuitive sense to use yaw and pitch to describe axes of rotation, because one could reasonably confuse xRot for yaw (which is around the y-axis but moves on the same plane as the x-axis and z-axis), zRot for pitch (which is actually around the x-axis but moves on the same plane as the z-axis and y-axis), and yRot for roll (which is actually around the z-axis but moves on the same plane as the y-axis and x-axis). Here's an illustration of what I'm trying to demonstrate:

I'd also like to add that with such unique names, it's hard to confuse them when debugging issues. x/y/zRot all being one letter away from each other can add confusion, especially when you aren't paying attention.

these are good points -- i agree with sticking to pitch/yaw
i'll make a PR to convert existing x/yRot (all unchanged records) to pitch/yaw


Can you bind include .js extension files?

if the file extension is .jsx it works fine .
but I need the file name extension is js.

Needed the same and ended up using the language-babel apm package. Works like a charm.

You can enable .js files from the plugin settings.
On Tuesday, 23 August 2016, nmaro<EMAIL_ADDRESS>wrote:

Needed the same and ended up using the language-babel apm package. Works
like a charm.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/orktes/atom-react/issues/193#issuecomment-241787730,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlAi8xJrpcxPuc2-xP3K0I5lv-nruu9ks5qixxWgaJpZM4Jqhv8
.

--
Ystävällisin terveisin,
Jaakko Lukkari


grovewater: Initial implementation

This module implements support for the Grove Water sensor.
Signed-off-by: Jon Trulson<EMAIL_ADDRESS>Signed-off-by: Zion Orent<EMAIL_ADDRESS>

Thanks!  Merged and closing.


Photos App Won't Open (New Update?)

Not sure if this is caused by a new update as I've had this working for at least a year now, but just recently (today or yesterday), the photos app just won't open. When I disable lsposed module it seems to work fine.

Update your LSPosed to a maintained fork, seems like it stopped working past a certain Android (security?) update.

Thank you for your help. I actually did this before and it started working again. Appreciate it.


Update scalafmt-core to 2.2.2

Updates org.scalameta:scalafmt-core from 2.2.1 to 2.2.2.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: semver-patch

Superceded by #128


feat: expose core db connection settings

Allow to change core.spec.database.maxIdleConnections and core.spec.database.maxOpenConnections in harborcluster.

Please don't merge yet (hopefully some of the checks will break). It's missing at least charts/harbor-operator/templates/crds.yaml

@MarcelMue @wy65701436 @chlins should we merge it now ? Or do we wait to recreate 1.4 release branch first ?

@MarcelMue @wy65701436 @chlins should we merge it now ? Or do we wait to recreate 1.4 release branch first ?

I think it's fine to merge now. Also why is CI stuck so weirdly? I am uncertain why github actions are not running.

@MarcelMue @wy65701436 @chlins should we merge it now ? Or do we wait to recreate 1.4 release branch first ?

I think it's fine to merge now. Also why is CI stuck so weirdly? I am uncertain why github actions are not running.

I just asked me the same question in another PR, I don't understand neither... @wy65701436 @chlins do you have an idea ?

Gentle ping @chlins @holyhope. Looks like I need an approval from a maintainer to trigger the workflows.

The PR failed at test the following test:
Test Case - Tag Immutability                                          Filesystem      Size  Used Avail Use% Mounted on
overlay          84G   76G  7.4G  92% /
tmpfs            64M     0   64M   0% /dev
shm              64M     0   64M   0% /dev/shm
/dev/root        84G   76G  7.4G  92% /drone
none            3.4G     0  3.4G   0% /tmp
| FAIL |
1 != 0

I don't think this failure is related to my change, right? Is it possible to re-run the test or merge it?

@LiuShuaiyi congrats on merging your first PR here!


docs: readthedocs is stuck on v0.18.0

The latest available release on readthedocs is v0.18.0, but the latest stable release is v0.20.0.

Fixed partially in d7d7f660a81336c65bd4a49bdfc1dc2e5b3f7abb and on readthedocs.org.
Link to latest stable (v0.20) docs: https://docs.l7mp.io/en/stable/


Link text could not be selected

Attach (recommended) or Link to PDF file here:
hyperlink_text_selection.pdf
Configuration:

Web browser and its version: Chrome Version 126.0.6478.62
Operating system and its version: windows 11
PDF.js version: pdf.js-4.3.136
Is a browser extension: no

Steps to reproduce the problem:

Open the attached pdf file named hyperlink_text_selection.pdf
Try to select the text "Microsoft"

What is the expected behavior? The text "Microsoft" should be selected
What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

I'm not sure about this but I have a suspicion of what's going on here. If I'm correct, the root issue actually goes beyond links. Try selecting any text in a PDF in pdf.js, starting your selection from a decent margin away from the letters so that you are beyond the bounds of the  holding the text in the text layer that pdf.js generates. Your selection will end up starting at the beginning of the page, regardless how far down you start! This is already an annoying behavior but you can normally get around it by starting your selection close enough to the text that you want to select that it ends up within the bounds of the  holding the text.
The issue with the links in this PDF when viewed in PDF.js is that the  in the annotation layer containing the link completely overlaps the  that contains the text so that it's not possible to start a selection from inside the text  without triggering the link.

Oddly, while the microsoft link can't be selected by itself in either the version of PDF.js in Firefox 127.0.2 or the latest code in master, the thing that anchors the selection and causes it to start at the top of the page seems to be different. In Firefox 127.0.2 the selection is anchored on the text layer and on the latest code in master it is anchored on the annotation layer.

I was thinking about how to solve this: adding user-select: none to links in the annotation layer significantly improves the situation. However I believe that the best fix would be to move the links to the .textLayer itself. By doing so, the links are in the right place and we don't need any workaround in the first place.
Any opinion?

However I believe that the best fix would be to move the links to the .textLayer itself. By doing so, the links are in the right place and we don't need any workaround in the first place.

To me that sounds potentially quite "messy", since at a PDF specification level the annotations are completely separate from the text.Furthermore, there's
Furthermore, it's possible to disable the various layers independently of each other and this way

However I believe that the best fix would be to move the links to the .textLayer itself. By doing so, the links are in the right place and we don't need any workaround in the first place.

To me that sounds potentially quite "messy" and thus undesirable, since at a PDF specification level the annotations are completely separate from the text-content.
It may also be further complicated by the fact that some PDF documents don't contain any text and consequently there's no textLayer, and it's also possible to disable the various layers independently of each other (which is functionality we should keep).


Add Username Prefix Enforce for DynamicFile mode

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/retest

/retest

/retest

Looks good, although it looks like a unit test is failing.

/retest

/lgtm
/approve


Version tags?

For users of grpc, matching versions between the grpc support package and protoc-gen-go is important. Would you consider tagging releases? Right now on the letsencrypt/boulder project, we check out a specific commit id to make sure we are using a compatible version. It would be nicer to check out a semantically versioned tag.
Thanks,
Jacob

I agree it would be valuable to have semantic release tags every so often. However, the authors seem to have closed 3 prior issues asking for this as well.

Thanks for pointing that out! Hopefully release tags are more appealing now, since https://github.com/golang/protobuf/issues/264 has demonstrated a concrete use case where versioned releases are important. That issue was my motivation for filing this issue: We were unable to upgrade our protoc-gen-go and grpc packages in Boulder for several months because of an incompatibility at HEAD.

With go dep arriving soon in every gopher's toolbox, a semver versioning for protobuf (git tag -a v1.0.0 -m 'v1.0.0') would be awsome!
Related issues:

https://github.com/golang/protobuf/issues/384
https://github.com/golang/protobuf/issues/260
https://github.com/golang/protobuf/issues/389
https://github.com/golang/protobuf/issues/161
https://github.com/golang/protobuf/issues/69


Announce change in governance procedures for OpenEBS org

When project team made decision to re-apply to CNCF, we recognized we needed to archive a number of repos, plus revise the project governance for the project. We "turned off" the existing governance procedures, to make these changes.

@edrob999  This deliverable is moving towards becoming STALE. - This needs an update or action please.


access_logs: Fix crash due to uninitialized bytes meter

Opening this to get others' thoughts.  Not sure if this is how it should be handled or if there should be safety checks in the callbacks themselves.
Signed-off-by: Brian Sonnenberg<EMAIL_ADDRESS>Commit Message:  call setDownstreamBytesMeter in the case that no filter chain matched to avoid crashing due to uninitialized bytes meter.
Additional Description:
Risk Level:  Low
Testing: Manual only
Docs Changes:
Release Notes: TBD
Platform Specific Features:
[Optional Fixes #Issue] #22335
[Optional Fixes commit #PR or SHA]

We had a brief offline discussion with @KBaichoo and @jstraceski and decided to move the bytes meter to the network filter chain manager, so that we fix it for all network filters, and not just missing filter chain.


contraption does not turn into blocks

Describe the Bug
In many ininstances, I've made a contraption and it wont turn into blocks or interact with the bearing it is attached to. /kill doesnt work, and I dont know what to do ;/
Reproduction Steps

make a bearing contraption with another bearing somewhere on the axis the original one is facing, so the blocks on the second bearing will stay in place while being a contraption

...
Expected Result
It should continue rotate 90˙ and then place again,
Screenshots and Videos
https://user-images.githubusercontent.com/125825271/219968638-b3c6dac8-95c7-467e-b97e-ee7d42dce9db.mov
Crash Report or Log
No response
Operating System
MacOS Ventura 13.0
Mod Version
0.5.0i
Minecraft Version
1.19.2
Other Mods
oh the biomes youll go, minimap mod
Additional Context
This is used in a cobblestone farm inspired by TangoTek's.

Bearings on contraptions are stabilized and will not rotate with their parent contraption. You can see here that the first bearing rotates and rotates the second one, but the second one keeps its structure level to the ground.
Just remove the 2nd bearing.


[fix bug 847911] Create a view with all vouched mozillians

Probably get_vouched_mozillians should be in other place or it should be done in a different way. I am open to discussion.

Coverage increased (+0.03%) to 89.849% when pulling 298d1e8dce3d5ab8edad34723e1f98721fa5f7bd on fxa90id:Bug_847911 into d731c3d1782325373354032db9e6f6f5009c69fe on mozilla:master.

Coverage decreased (-0.2%) to 88.889% when pulling f4c631bfaa363c86eb7e6dc4596b086c9ab6c083 on fxa90id:Bug_847911 into 3fa15c874307bd36c131773650dcc2ea1a43d275 on mozilla:master.


Icon Request: SoundCloud

Icon Request

Icon name: SoundCloud
Tags of this icon: logos
Use case: an unified icon with other Remix Icons
Screenshots of similar icons: can be seen on https://soundcloud.com/

https://remixicon.com/#icon-soundcloud-line
https://remixicon.com/#icon-soundcloud-fill


[IR] Dropping getLoadOpResultType since it is no longer used

After PR #3587, LoadOp's build methods have been altered and no longer use getLoadOpResultType. This is a cleanup change.

LGTM.


Tutorial - Getting start - suggestion

I've found "generate-factory-for-class" very usefull, but executing it on Windows was a small problem at first.
If I could suggest a small change in this tutorial, I recomend adding a comment saying that correct syntax of this command would be:
.\vendor\bin\generate-factory-for-class "App\Action\TemplateTestAction" > src/App/src/Action/TemplateTestActionFactory.php
The biggest problem was that classname shouldn't be App\\Action\\TemplateTestAction but App\Action\TemplateTestAction. Well, at least in my environment.

This repository has been closed and moved to mezzio/mezzio; a new issue has been opened at https://github.com/mezzio/mezzio/issues/15.


Release v2.1.0

Release v2.0.1

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


New home needed for debian package

Bintray is no longer available since JFrog shut it down in May of 2021. See this article here for more details. If and when another home is found for binary hosting the install guide will need to be updated to reflect this change.
This project is really cool, BTW!

might be a suitable alternative to Bintray https://www.getbalto.com/signup?plan=opensource


Add feature flags for heavy dependancies

At least criterion is an heavy dependency which should have a feature flag to be disabled, it makes this crate unreasonably long to compile for someone who is not interested in this.
Maybe some clap features could also be disabled for a very slight improvement.
I'm not sure what should be enabled by default or not though ^^'

Fixed by #9


How should I compute the original TF tensor?

If I have a TF tensor computed by torchvtk.utils.tex_from_pts, is there any way I can compute the original tensor?
It's just like the tensor parameter of tex_from_pts, so you know intensity,r,g,b,a from this data.
Looking forward to your answer.

Hi, sorry I missed that for some time :D
torchvtk does not have this functionality.
Depending on how the TF texture looks like it may be non-trivial to reconstruct the underlying piece-wise linear representation. How I would approach this is probably by filtering the 1D TF texture using a central differences or sobel filter which should give you the first derivative for each channel. Then I would look for the places where this is 0 (or changes sign). At the interpolated sections of the texture the derivative should be constant. In fact by filtering this derivative once more, to get the 2nd derivative, you should get a "texture" that is non-zero at all the points of the piece-wise linear function. If you find the texture position of those, call them "imtensity", and sample the original texture for RGBA at those places, you should be able to reconstruct the point for. There may be some edge cases I have not thought about here.
Hope this is still helpful to you.
Cheers


DE23223 Improved contrast of focus state on overflow and change image buttons

code LGTM

I'll do the test thing.

LGTM


fix(plugin-webpack): add missing debug level for webpack-dev-middleware

[x ] I have read the contribution documentation for this project.
[x ] I agree to follow the code of conduct that this project follows, as appropriate.
[x ] The changes are appropriately documented (if applicable).
[x ] The changes have sufficient test coverage (if applicable).
[x ] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
This is a one line add to the WebpackPlugin.js, to add the debug method to the logger. Without it projects created with webpack template can't be launched as the "debug" method on the loggert is required.
I have not made the change myself, but noticed someone did and that there is no pull request with the change, so since it made work again I figured it might be a good idea to fix it on the master branch.

Thanks for the PR, but this was fixed in #1131 and released in beta 45.


tiup list shows components that cannot run independently

Bug Report
Please answer these questions before submitting your issue. Thanks!

What did you do?

tiup list

What did you expect to see?
only the components that can run independently

Available components (Last Modified: 2020-02-27T15:20:35+08:00):
Name        Installed           Platforms                             Description
----        ---------           ---------                             -----------
tidb        YES(v3.0.1)         darwin/amd64,linux/amd64,linux/arm64  TiDB is an open source distributed HTAP database compatible with the MySQL protocol
playground  YES(v0.0.9)         darwin/amd64,linux/amd64              Bootstrap a local TiDB cluster
client      YES(v0.0.6)         darwin/amd64,linux/amd64              A simple mysql client to connect TiDB
package     YES(v0.0.9)         darwin/amd64,linux/amd64              A toolbox to package tiup component
cluster     YES(v0.4.9,v0.6.0)  darwin/amd64,linux/amd64              Deploy a TiDB cluster for production
mirrors     YES(v0.0.2)         darwin/amd64,linux/amd64              Build a local mirrors and download all selected components
bench       YES(v0.0.1)         darwin/amd64,linux/amd64              Benchmark database with different workloads
ctl         YES(v4.0.0-rc.1)    darwin/amd64,linux/amd64,linux/arm64

What did you see instead?

It includes many components that cannot run independently, like grafana, cdc. etc.

What version of TiUP are you using (tiup --version)?

tiup version v0.0.5 tiup
Go Version: go1.13
Git Branch: master
GitHash: aab3add
Build Time: 2020-04-24 18:10:05 +0800

When package the components that cannot run independently, we should add the --hide flag for tiup package


Optax with multiple optimizers

Optax has a function multi_transform, which is nice for using multiple optimizers. See here for a working example.
How should Equinox interact with multi_transform?
Suppose, for instance, I want to freeze the last layer of my network and I want to use optax's set_to_zero function. NB: I'm aware of this example, but it's less general than my question because it only addresses the case where you want to freeze a set of parameters (by excluding them from the differentiable set) and doesn't address the case where we want to apply a different optax optimizer to different sets of parameters.
My code might look something like:
def create_param_labels(model):
    # initialize everything with "train"
    param_labels = jax.tree.map(lambda x: "train", model)
    # set the mask for the last layer's weight to "freeze"
    param_labels = eqx.tree_at(lambda tree: tree.layers[-1].weight, param_mask, replace="freeze")
    return param_labels
...
model_params, model_structure = eqx.partition(model, eqx.is_inexact_array)
param_labels = create_param_labels(model)
optimizer = optax.multi_transform({"train": optax.sgd(learning_rate=lr), "freeze": optax.set_to_zero()}, param_labels=param_labels)
optimizer_state = optimizer.init(model_params)

This results in an error because param_labels is a PyTree just like the model and the model has a __call__ method implemented, which makes it callable. So then under the hood optax will check if the mask (i.e., the param_labels) is callable. Since it is callable, it ends up calling param_labels(model_params), which isn't what we want.
We can't just delete the __call__ method from the param_labels object because it's a frozen dataclass. So it seems like the only way forward is to make param_labels a callable function that somehow labels PyTree nodes appropriately. I'm not enough of a PyTree pro to know if there's an easy way to manipulate PyTrees to easily target the weight matrix of the last layer. Does anyone have a sense for how to do this?

I'm looking for the same functionality. Did you find an elegant solution in the mean time?


Sources block

As a user I want to see sources of information which was used on a StreetCode page so I will know where did this information come from
Description
This block will allow the user to review the attached sources of information used for specific StreetCode. This will allow the user to know the place of origin of information, as well this will allow the user to understand which books/articles.. can be used to get more information about StreetCode
Acceptance Criteria

Title "Джерела" is displayed.

Separate card for each type of source is displayed.
Click on the source card opens a modal window with a list of used sources. (sources can be clickable or not clickable).
If there are more than 3 cards - a navigation arrow appears and allows the user to scroll cards + "Дивитися всі" button appears and clicking on it opens a modal window with a full list of sources' categories.

Epic link
(Epic) StreetCode page

UPD to acceptance criteria

Title "Джерела" was changed to "Для фанатів"

UPD to acceptance criteria
4. If there are more than 3 cards - a navigation arrow appears and allows the user to scroll cards + "Дивитися всі" button appears and clicking on it opens a modal window with a full list of sources' categories.
button is not expected in this block
(NEW)
5. In opened modal window subcategories should be written in bold

NEW item:
7. The layout of the StreetCode page must be adaptive: desktop (1920px, 1600px, 1025px), tablet (768px), mobile (360px).


More summary improvements.

This PR contains series of commits to improve upon #119.
With additional info about filtered test262 tests provided with changes in #119, this PR puts them inside Summray.scala.

I think it would be best to squash and rebase for merge. If needed, I wll rebase and tidy up commits.


Embedding default HTTP links for non pro users

I think for people with no pro account generated embedding links should be HTTP by default, for now, they are HTTPS
https://i.imgur.com/WKtEeF1.png

It picks up the protocol from the URL you're currently on. So if you open the share box when on https, it'll give you an https url.
I've taken note, but this UI is being dropped in v5 so it's not worth making any changes right now. Thanks for the heads up.


build: respect CC and CFLAGS in Makefile

This change allows for the Makefile to respect the $CC and $CFLAGS variables on platforms where those are usually set.

Thank you for the PR! Unfortunately, it does not work on Windows.

OK, reverted changes for Windows specifically.

Thank you!

Thank you!

Much appreciated 🙏🏾


Support for free-for-all/IPNCT format

Would be useful to be able to just have a field of n players without teams and record scores

In theory this should be possible already, although only as a component (pass in players with different teams). Some things wouldn't work or would look messy (New Game only assumes 2 teams, bouncebacks don't work, buzz menu would be clunky with each person listed under their own team), but I think it'd be playable.

There are some existing gaps though, specifically around calculating if protests matter. There may be a few more places that assume that only two teams are playing.


Add ppc64le & aarch64

Checklist

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

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

@conda-forge-admin, please rerender

Tests are passing just fine. Should I increase the build number?

Tests are passing just fine. Should I increase the build number?

No need to increase the build number in this case b/c we don't want new packages for the currently available builds, only the new ones. Thanks!


[Question] What is the process to contribute?

Hello,
I am planning to add support for .Net 5 in my projects some time soon and I am considering to make a PR to your project with the .Net5 support.
Do you have recommendation about the way or the process to contribute to your project?
Regards,

Do you have any plane about adding new features to Kledex?

Hi!
First of all, yes I'm planning to add more features to Kledex and I'm going to start from January.
This year I've been very busy with work and Master's Degree but I'm going to submit my dissertation by the end of the year!
Your question reminded me that I need to add a proper contribution guidelines, thanks for that.
First thing I'll do with the new year is to migrate to .NET5 and update the version to 3.0.

Ok thanks for that!
I'am looking forward! 👍


deposit form: add sharing of drafts

closes https://github.com/inveniosoftware/invenio-app-rdm/issues/2667
closes https://github.com/zenodo/zenodo/issues/151

Updated dropdowns:

Share button on the deposit form:
enabled:

disabled:

The view goes blank if I try to share metadata only unsaved draft
while granting access:


Single person Pose estimation

Hi,
I wanted to know, what changes should I do in order to estimate the pose for only one person in a frame?

Hi! Does #96 contain the answer?

Hope, it helped.


Vertically aligned middle for social icons. (_base.scss/.svg-icon)

This particular fix is referenced to the issue #259.
I basically changed vertical-align: text-top; to vertical-align: middle; to align the icons properly.

Feel free to report if this doesn't fix, I'll try and fix them.

@DirtyF, I think when we remove vertical-align property completely, it's is not centering the icons but rather baselining them. As you can see the base of the icon and the span are the same when you removed the vertical-align property as a whole. middle argument in vertical-align centers it well.
In addition, text-bottom value for vertical-align property makes it look vertically centered as well.


Any plans for CLI support?

I just used the online generator and it was really good. But I think using an import map generator in the CLI which automatically generates import map from package.json would be very handy. I'm wondering if there are any plans to support this approach, too.

Yes, a CLI will come handy and also we can also add npm scripts based on it to install, re-install or update the import maps.
Some time back I created this CLI to generate project scaffolds based on import maps with various cdns
https://github.com/rajasegar/unpack
May be I can give a shot for the CLI if we are clear with the MVP requirements

This is being developed at jspm/jspm, closing for now.


Stars don't match

From https://github.com/explore -- Today at around 11:40-50 EST:

Notice that "the art of the command line" appears with 3.6k stars.
Then...

It really has 44.2k!

The rest of the projects that appeared in Trending Repositories also displayed mis-matched stars.

Thank you for bringing this to our attention!

A fix for this was just deployed. Thanks again for bringing it to our attention, @servusDei2018 !


remove  duplicate integrate cases

Fixes #ISSUSE_ID.
Changes proposed in this pull request:

Pull Request Test Coverage Report for Build 522

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

Totals

Change from base Build 439:
0.0%

Covered Lines:
10987

Relevant Lines:
16484

💛  - Coveralls


Use the old setup logic to work around failing builds

Description of the change:
Move back to manual set up of /etc/passwd
Motivation for the change:
/etc/passwd is no longer being properly created

/retest

@fabianvf I think this fixed the permissions error with the ansible test.
But we're hitting another issue with the e2e-aws-go which seems to be related to #1932 which is the issue with controller-tools not promoting the version specific fields (subresources, schema, and additionalPrinterColumns) to the top level version.
time="2019-09-23T19:31:05Z" level=info msg="Testing operator locally."
time="2019-09-23T19:31:05Z" level=debug msg="Running []string{\"go\", \"test\", \"./test/e2e/...\", \"-namespacedMan\", \"/tmp/namespaced-manifest.yaml335172055\", \"-globalMan\", \"/tmp/global-manifest.yaml120439114\", \"-root\", \"/tmp/tmp.yYLZYf8SBS/memcached-operator\"}"
go: downloading github.com/prometheus/prometheus v1.8.2-0.20190525122359-d20e84d0fb64
go: extracting github.com/prometheus/prometheus v1.8.2-0.20190525122359-d20e84d0fb64
time="2019-09-23T19:31:13Z" level=fatal msg="Failed to create resource(s) in global resource manifest: CustomResourceDefinition.apiextensions.k8s.io \"memcacheds.cache.example.com\" is invalid: [spec.versions: Invalid value: []apiextensions.CustomResourceDefinitionVersion{apiextensions.CustomResourceDefinitionVersion{Name:\"v1alpha1\", Served:true, Storage:true, Schema:(*apiextensions.CustomResourceValidation)(0xc009a8d140), Subresources:(*apiextensions.CustomResourceSubresources)(0xc00f33f0c0), AdditionalPrinterColumns:[]apiextensions.CustomResourceColumnDefinition(nil)}}: per-version schemas may not all be set to identical values (top-level validation should be used instead), spec.versions: Invalid value: []apiextensions.CustomResourceDefinitionVersion{apiextensions.CustomResourceDefinitionVersion{Name:\"v1alpha1\", Served:true, Storage:true, Schema:(*apiextensions.CustomResourceValidation)(0xc009a8d140), Subresources:(*apiextensions.CustomResourceSubresources)(0xc00f33f0c0), AdditionalPrinterColumns:[]apiextensions.CustomResourceColumnDefinition(nil)}}: per-version subresources may not all be set to identical values (top-level subresources should be used instead)]"

I'm going to bump the SDK to use the latest controller-tools to include the fix #322 for this.

/test e2e-aws-go

@fabianvf This will probably need a rebase once #1961 is merged to fix the CRD per-version error in e2e-aws-go.
On the bright side since the underlying issue with CRIO seems to be fixed for now, we don't need this as urgently so this can wait until we clear the CI for this.

I'm seeing this issue again on #1961 so it doesn't seem like it was fixed.
So I've added the changes there to fix e2e-aws-ansible and the other CI issues all together.

I think this changes are applied here: https://github.com/operator-framework/operator-sdk/pull/1961.
could we not close this one in prol of this PR?

Closing in favor of #1961


Fix day tooltip format in chartjs adapter

Hey @ankane,
First of all, thanks for the work you've put into Chartkick! I've been using it with Chart.js and it was really helpful 👍
I've noticed this small issue related to the day date format in tooltips, I've looked into the commit history and it feels that it was a just typo that happened during the migration to the version 4.

Please let me know if this was not a typo/issue, maybe this change was intended and the problem is on my side.
Best,
Mário Balça

Hey @mariobalca, thanks for the PR, but I'm not able to reproduce. Make sure you're on Chart.js 3 and using the date-fns adapter.

Interesting! I'm using Chart.js ^3.7.0, but I'm not using the date-fns adapter, I went with the moment adapter instead.
But if this only happens in my setup I'll just keep using the forked version 👍
Sorry for the trouble and thanks for answering so quickly!


Allow setting source_identity in provider configuration

Describe the outcome you'd like
With release v4.29.0 of the Terraform AWS Provider you can set source_identityon the provider configuration. source_identity can be used to enhance the auditability when assuming roles, as the source_identity remains the same throughout the session.
AFT should support setting the attribute source_identity so that all actions can be tracked in CloudTrail easily.
Is your feature request related to a problem you are currently experiencing? If so, please describe.
With assumed roles it can be tricky to find all relevant logs in CloudTrail currently. With source_identity there will be one attribute that can be used for tracking all relevant  API calls.
Additional context
Using source_identity requires modification of the trust policies of assumed roles. This blog post describes the necessary steps. This change might break compatibility with previous version.

Thanks @wlami for the request, I've gone ahead and created a backlog regarding this enhancement with the team.


Deadlock in agent found during load test

During a load test we uncovered a situation where an application may become blocked by the funnel agent.
The working theory is as follows:

The flask becomes very slow due to very frequent key queries (this has since been fixed)
The agent is performing blocking writes to the stream requests.  Since the consumer is not consuming, they end up essentially blocked.
The operation to add a metric performs a compareAndSet, which blocks the current thread while waiting for reads to complete.

Copying a large stack trace here:
stack_trace.txt

submitted PR https://github.com/oncue/funnel/pull/51


marina/nanoplot

Nanoplot example was added to Interactive Charts tutorial

def ch = new Crosshair(color: new Color(255, 128, 5), width: 2, style: StrokeType.DOT)
def pp = new NanoPlot(useToolTip: true, showLegend: true, crosshair: ch, omitCheckboxes: true,
                  legendLayout: LegendLayout.HORIZONTAL, legendPosition: LegendPosition.TOP)
pp << new Line(displayName: "Line", x: [1, 4, 6, 8, 10], y: [3, 6, 4, 5, 9], width: 3)
pp << new Bars(displayName: "Bar", x: (1..10), y: [1, 2, 3, 4, 3, 2, 1, 2, 3, 4],
               color: new Color(0, 0, 128, 160), outlineColor: Color.black, width: 0.5)
pp << new Points(displayName: "", x: [1, 4, 6, 8, 10], y: [3, 6, 4, 5, 9],
                 color: new Color(128, 0, 0, 160), outlineColor: Color.black, size: 10) // not show in the legend box

this example from the plotting tutorial i changed to a nanoplot, and then the graphics are mangled and there's a warning about unordered data.

:+1:

merge please

done


Memory issues when using large numbers of 'rois'

I would like to obtain gene expression values for an atlas where each voxel is labelled as a separate ROI (the roi*gene matrix will therefore be very sparse)
The issue is that this seems to require over 100GB of RAM
What I am doing is similar to  https://github.com/rmarkello/abagen/issues/46 (except the mask is the entire cortex)
Is there any recommendation  as to how to reduce the memory requirements?
Thank you!
Rob

Hi @robmcc10—thanks for your interest in, and welcome to, abagen !
Yikes! 100GB is certainly a lot of memory, so that's not ideal... This is likely due to the creation of the output (n_voxels x genes) matrices that get concatenated when aggregating across donors, which in the current workflow is unavoidable, though I'd have to check that this is indeed where the issue is arising.
To make sure I'm understanding, effectively you want the original ~3,700 samples assigned to voxels in your image, but preprocessed according to all the steps in the get_expression_data() pipeline? That seems like something that should be feasible, but the current workflow isn't really set up for this. (Also, the current pipeline is not optimized for speed in this instance, either! Apologies if it took ages to run before raising a MemoryError 😬)
I don't think any quick combination of functions in abagen will resolve this for you, unfortunately, but you could pull out (most of) the internals of the get_expression_data() pipeline to do it. I recognize that's not something that's super appealing, so I'll take a look at maybe creating a "preprocessing" function that will just return the preprocessed microarry data. It would be relatively straightforward to match that up to voxels in your using the MNI coordinates provided by the AHBA annotation files!
I haven't had much time to work on this lately (as you can likely tell from the history), but I'll try and take a whack at this soon to see if I can get something working in short order. Let me know if my interpretation of your goal is accurate, though!

Yes the issue is the creation of the output, the error message is:
MemoryError: Unable to allocate 26.7 GiB for an array with shape (15633, 229007) and data type float64
effectively you want the original ~3,700 samples assigned to voxels in your image, but preprocessed according to all the steps in the get_expression_data() pipeline?
Yes that's right - so preprocessed according to the pipeline (including assignment to the improve MNI coordinates), but there is no 'aggregation within an ROI' step as each ROI will have max one sample. This work easily if you are using a smallish mask - but you get this issue when the mask gets too big.
Thanks again for putting together such a useful tool!

Hey @rob-mccutcheon ! I realize that this probably isn't super helpful since I'm about a month late (apologies! grad school is busy...), but I just added a new change that should hopefully address your use case. If you update abagen by installing directly from github (pip install --upgrade https://github.com/rmarkello/abagen) you should have access to a new function: abagen.get_samples_in_mask().
By default, running this function with no parameters will return expression data for all available samples (that haven't been discarded due to e.g., bad spatial normalization) as well as the MNI coordinates of those samples:
>>> import abagen
>>> expression, coordinates = abagen.get_samples_in_mask()
>>> print(expression.shape, coordinates.shape)
(3466, 15633) (3466, 3)

This function accepts (almost) all the keyword arguments that abagen.get_expression_data() does, so you can simply provide those as parameters and they should work:
>>> expression, coordinates = abagen.get_samples_in_mask(gene_norm='zscore', corrected_mni=False)

(Exceptions are noted in the doc-string of the function.)
Alternatively, if you only want, say, cortical samples, you can provide a cortical mask and it will return only those samples that fall within tolerance mm of the bounds of that mask:
>>> expression, coordinates = abagen.get_samples_in_mask(mask=my_cortical_mask, tolerance=2)

I've added some documentation on this function here, but feel free to let me know if anything is unclear about this!

I know that this isn't exactly what you'd hoped for, so I wanted to explain my reasoning a bit: there are a few tissue samples that are very close to one another, so if you provided, say, a 1mm isotropic atlas to abagen.get_expression_data() (and avoided memory errors) you would end up having these samples aggregated into the same voxel. While you could use return_counts=True to check for which voxels this was the case, I figured providing all the samples + their corresponding coordinates would allow more flexibility: if you want to aggregate samples within 1mm voxels, go for it; if not, you have the "processed" sample-level data so you can do whatever you'd like.
Assuming you do have a 1mm atlas, you can get the corresponding ijk values of the sample expression coordinates in your atlas space with:
>>> import nibabel as nib
>>> import numpy as np
>>> affine = nib.load(my_atlas).affine
>>> ijk = np.asarray(np.floor(nib.affines.apply_affine(np.linalg.inv(affine), coordinates)), dtype='int')

If your atlas is a slightly different resolution you'll have to replace the np.floor call with something else (np.around(coordinates * (1 / resolution)) / (1 / resolution), where resolution is e.g., 1 for 1mm isotropic, 2 for 2mm isotropic, etc.), but hopefully that's not the case 🤞
As said before, let me know if you have any questions about this, and thanks for raising the issue in the first place—I'll work on beefing up the documentation further to hopefully help people avoid these sorts of memory errors in the future.

Thank you so much for taking the time @rmarkello ! That looks like a great solution


Fix initializing database

@matiszz glad this helped! Just merged this into main to it make the stake deploy turnkey like we want it in the blog post.


Include token metadata for zero-balance ValueViews of delegation tokens

Previously we weren't rendering any balance for delegation tokens that the user doesn't hold any of. That's because there wasn't any metadata for those tokens, so ValueViewComponent rendered nothing for them.
Before

After

In this PR

Fetch asset metadata based on the validator's delegation token name, and use it to render the zero balances.
Remove customizeSymbol from the block processor

Would especially like @grod220's thoughts on this. I made two changes to customizeSymbol: 1) I made it a pure function, returning a new copy of the Metadata with the symbol customized, rather than mutating the existing one; and 2) I moved it to ValueViewComponent, so that the customizing happens at the render stage rather than the block processing stage. This means that:

The webapp, rather than the extension, is now responsible for accurately displaying the type of token. This could be a downside if we are worried that other web apps won't realize that validator names could be spoofed. However, I think the benefits outweigh the downsides.
If/when we want to change the rendering of the symbol, we don't have to blow away all the IndexedDB data and rebuild. Rather, we can just change the ValueViewComponent's rendering logic. Another way of saying this: The concern of how to render a symbol rests within the rendering layer (where it belongs, I'd argue), rather than the processing layer.

Punting for now

I'd love to build out the ValueViewComponent a bit in the future so that it has a tooltip that shows much more information. Then, we could make the symbol much shorter, and show which validator the token is for on hover.

Closes #617

customizeSymbol... moved it to ValueViewComponent, so that the customizing happens at the render stage rather than the block processing

The symbol being set within the extension came from https://github.com/penumbra-zone/web/pull/558 by @hdevalence. Perhaps he can weigh in here. I have a feeling that we want to keep this in the extension because:

Security implications. In this case, it's a bit sensitive because validators could make up any name. If web apps, make the wrong call and show the validator created name as the token symbol, the user could be vulnerable to impersonation.
Convenience. Web apps ideally can just request metadata and display it without having to add additional logic.

Yes, we need the symbol to come from the asset metadata registered in the extension's asset database.
The only part of the self declared validator data we can actually rely on is the validator identity. So we can either have some "known delegation tokens" (as experimented with in that PR) or uniformly generate a symbol from the validator identity.

OK @grod220, requesting re-review now that I've moved symbol customization back to the extension (and copied that logic in the staking fetcher). Commit here.


fix #5298

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #5298
[ ] Requires deployment <>

Before submitting pull request, please make sure:

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

Optional

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

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot 📸

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

pay 15 usd

pay 15 usd

@vikiival no payout?

oops
EfmnRhHaQqfT3phm4cUCHCU3gFVDoSPR1U9WXzMRQBMqZ4L

pay 15 usd

pay 15 usd

😍 Perfect, I’ve sent the payout
💵 $15 @ 34.45 USD/KSM ~ 0.435 $KSM
🧗 EfmnRhHaQqfT3phm4cUCHCU3gFVDoSPR1U9WXzMRQBMqZ4L
🔗 0x558edac21b935fa320dab3e0ffc147fb5be407aeadad3387e75776bc5f6f5f51
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Update test.log

If the message below is truncated, see https://ci.appveyor.com/project/yihui/latex-pass/builds/44295915 for the full version.
The missing packages identified from the LaTeX log are:
ifplatform

If you are an R user using TinyTeX, you may install these packages via:
tinytex::tlmgr_install(c('ifplatform'))

If you use TinyTeX, including LaTeX for Manim (https://chocolatey.org/packages/manim-latex), you may install these packages via command line:
tlmgr install ifplatform

If you do not use TinyTeX (https://yihui.org/tinytex/), you need to figure out how to install them by yourself.