Web - New group - Console error when creating new group

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to URL https://staging.new.expensify.com/
Log with any account
Click on FAB button/New Group
Select multiple users
Click "Create group"

Expected Result:
There should not be any errors in the console
Actual Result:
An error appears in the console
Workaround:
unknown
Platform:

Where is this issue occurring?

Web

Version Number: v1.2.20-1
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

https://user-images.githubusercontent.com/43996225/198358301-bfe4789c-0d80-499b-a051-06aaafef1273.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub

I can reproduce this. This is most likely an issue coming from the server, I will investigate this more when I'm done with an API refactor.

This is most likely an issue coming from the server

Does that mean internal in this case? Let's get the appropriate label assigned so Adele can help drive it forward per this process to keep the pressure on to find a contributor and get this one closed out

PS all bugs should be daily

@michaelhaxhiu I just added the internal label. Unassigning myself as I'm busy with an API refactor.

internal now - @youssef-lr what are next steps to add an engineer to this issue?

Adding demolition per this thread.

Issue not reproducible during KI retests. (First week)

That's good it's not reproducible this week. But this doesn't have a BZ assigned and it should 🤔 .

@michaelhaxhiu - I'm confused with this one. Do I need to create a job in Upwork? I see it's internal, so I don't think creating a job is the right step. Any feedback will help!

Ok, confirmed this is an Internal one. @Gonals flagging that this one looks similar to this GH:
#12637
One difference is the other GH is for inviting members instead of creating a group. If yes, I think we should close one and merge them together. Thoughts?

They seem different to me. The displayed error is not the same, so the underlying cause (and the fix) is likely different.
I'll take a look and see if we can still reproduce this. If we can, I'll fix it. Otherwise, I'll just go ahead and close it


brew bundle check for any version

Is it possible to configure a Brewfile so that bundle check is satisfied when any version of a  dependency is installed?
i.e. say you have postgresql@11 installed locally and brew "postgresql" in a Brewfile.

Unfortunately, no. Versioned formulae are technically different formulae.


Reword weave proxy intro

Tried to make it clearer to someone coming to this completely fresh.
Also linked to Docker docs in case they haven't heard the specific terms used.

LGTM


Running C and C++ Files using different compilers.

Issue Type: Feature Request
Team VS Code,
I have compilers for C and C++, that being gcc and g++ respectively. I know that I can use g++ for both the types of files, but I want to set commands such that I can run C files using gcc and C++ files using g++ using my own custom command. It would be very useful if someone guided me on how to do that,
VS Code version: Code 1.58.2 (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:10:15.214Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

Nope. But thanks for the suggestions.
On Tue, Jul 20, 2021 at 2:38 PM vscodebot[bot] @.***>
wrote:

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already
covered by an existing one, like:

VSCode adding /d and /c arguments to task command on execution?
(#93437) https://www.github.com/microsoft/vscode/issues/93437
TS Server fatal error: Cannot read property 'length' of undefined
(#125473) https://www.github.com/microsoft/vscode/issues/125473
TS Server fatal error: Cannot read property 'length' of undefined
(#127914) https://www.github.com/microsoft/vscode/issues/127914

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/129036#issuecomment-883231048,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQIDX7AQXL6HYQEGHEICXT3TYU4IFANCNFSM5AVMBBTA
.


Fix ServiceAssemblyContent for symbols from modules with auto added "Module" suffix

This fixes https://github.com/Microsoft/visualfsharp/issues/4101

@dotnet-bot test Windows_NT Release_ci_part1 Build please

@TIHan done.

it’s ready


Crash-like report.

I would like to think about some kind of ability, when a traceback is not caught and bubble at user level (and has been tagged by lib authors) to get some way to collect it too.
It would give some stats of what user are not understanding. I can imagine that we can on the HTML traceback, on a per-module basis record wether or not to submit these kind of TB to collection.
For version 5.0 of course, but just want to log my though while it's fresh post-flight.
You can see that as a "crash-like" reporter, the tricky bit is to distinguish error actually comming from miss-using the code from something different. Though, miss-using the code is a pattern that might point of some unclear API.
Thoughts ?

The way I understood the design we were talking about in Austin, it would
be up to the calling library to shove the information into the (name, key,
count) storage format. That is, the calling library would collect the tb
and classify it, and then add that to the count of that class of tbs. This
kind of classification is probably better done at the level of individual
libraries anyway, or?
On Mon, Jul 13, 2015 at 8:36 PM, Matthias Bussonnier <
<EMAIL_ADDRESS>wrote:

I would like to think about some kind of ability, when a traceback is not
caught and bubble at user level (and has been tagged by lib authors) to get
some way to collect it too.
It would give some stats of what user are not understanding. I can
imagine that we can on the HTML traceback, on a per-module basis record
wether or not to submit these kind of TB to collection.
For version 5.0 of course, but just want to log my though while it's fresh
post-flight.
You can see that as a "crash-like" reporter, the tricky bit is to
distinguish error actually comming from miss-using the code from something
different. Though, miss-using the code is a pattern that might point of
some unclear API.
Thoughts ?
—
Reply to this email directly or view it on GitHub
https://github.com/njsmith/sempervirens/issues/15.

I was thinking
raise SVExcepionClass
with
class MyEx(SVExceptionClass)

    def __init__(self):
        self.project = 'numpy'
        ...

Then IPython kernel can say, "Hey I see a subclass of SvExcpetionClass (as ex) that bubble to main : I can do increment(ex.project, ex.key, ex.value)". Or something like that, we can just ducktype.
Then you only count Exception that bubble up to users (name == 'main'), and not exception that are actually triggered (and handled) by other libraries.


Feature/article edition bug

What
Two bugs existed existed:

Articles were being forced to have an edition in the create screen
If a space was added in the creator and then removed in the editor the 'articles' path would be removed, saving the page in an invalid location.

How to review
Attempt to create a bulletin, article and article download with and without titles to test they give the expected result. Delete the editions in those and check the page type isn't removed from the path.
Who can review
@robchamberspfc if you could check this one please in terms of functionality? I'll do the merge once you've given it the thumbs up

@Crispioso Looks good locally, merge away


Issue with Anomaly Detection

I have this config:
checks for retail_orders:
  - anomaly score for row_count < default

It results in this output:
(soda-cl-v3.0.0-rc3) $soda
Usage: soda [OPTIONS] COMMAND [ARGS]...

  Soda Core CLI version 3.0.0rc3

Options:
  --help  Show this message and exit.

Commands:
  scan        runs a scan
  update-dro  updates a DRO in the distribution reference file
(soda-cl-v3.0.0-rc3) $soda scan -d aws_postgres_retail uploaderror.yml
Soda Core 3.0.0rc3
Anomaly Detection Frequency Warning: Coerced into daily dataset with last daily time point kept
Evaluation of check anomaly score for row_count < default failed: error() got an unexpected keyword argument 'exc_info'
  | error() got an unexpected keyword argument 'exc_info'
  +-> line=2,col=5 in uploaderror.yml
Scan summary:
1/1 check NOT EVALUATED:
    retail_orders in aws_postgres_retail
      anomaly score for row_count < default [NOT EVALUATED]
        check_value: None
1 checks not evaluated.
1 errors.
Oops! 1 error. 0 failures. 0 warnings. 0 pass.
ERRORS:
Evaluation of check anomaly score for row_count < default failed: error() got an unexpected keyword argument 'exc_info'
  | error() got an unexpected keyword argument 'exc_info'
  +-> line=2,col=5 in uploaderror.yml
Sending results to Soda Cloud
INFO:cmdstanpy:deleting tmpfiles dir: /var/folders/l3/jgrj3m_544b09yfky3ph702c0000gn/T/tmpgmlqc1qi
deleting tmpfiles dir: /var/folders/l3/jgrj3m_544b09yfky3ph702c0000gn/T/tmpgmlqc1qi
INFO:cmdstanpy:done
done
(soda-cl-v3.0.0-rc3) $

@albinkjellin  Can you please try with latest version and reopen if this is still an issue?


Better serialization and deserialization for parsers and rules

@kgromadzki what did you mean by that? What in current implementation of serialization can be improved?

this was later found to be an outdated requirement


Cse/remove templates pr branches

test

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-nodejs-mongo
Remote: azure-samples
Branch: pr/4
You can initialize this project with:
azd init -t kaizentm/todo-nodejs-mongo -b pr/4

View Changes | Compare Changes

Project: todo-python-mongo
Remote: azure-samples
Branch: pr/4
You can initialize this project with:
azd init -t kaizentm/todo-python-mongo -b pr/4

View Changes | Compare Changes


Table overflows the white container in the views.

When the model has too many attributes the table get wider and overflows the white panel as shown in the picture below.
Any suggestion to fix it?

Hello,
I have no idea how to resolve this but you can custom your index to remove useless column :
https://activeadmin.info/3-index-pages.html

@cle61 Thanks for your answer, but I think all my columns are important to be shown.
Anyway, I think I have kind of fix for this, all make a PR in order for you yo check this out, ok?

yeah no problem !


icu: enable updateAutotoolsGnuConfigScriptsHook

Description of changes
Continuation of https://github.com/NixOS/nixpkgs/pull/313496
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[x] x86_64-freebsd

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Oh dear, this is a mass rebuild. I'm going to try to rebase it as per CONTRIBUTING, let's cross our fingers...

If upstream regenerates the configure script with a gnu-config that postdates https://git.savannah.gnu.org/cgit/config.git/commit/?id=e4786449e1c26716e3f9ea182caf472e4dbc96e0 then it will be fine. Until then we get errors from /usr/bin/uname not found.


Update use of the old DNS role throughout our Terraform

We have a bunch of Terraform stacks that refer to DNS records in the old account, with role arn:aws:iam::250790015188:role/wellcomecollection-assume_role_hosted_zone_update
We should update them to use the new role ID arn:aws:iam::267269328833:role/wellcomecollection-assume_role_hosted_zone_update
Follows https://github.com/wellcomecollection/platform/issues/4561

This search highlights uses of the old role: https://github.com/search?type=Code&q=arn%3Aaws%3Aiam%3A%3A250790015188%3Arole%2Fwellcomecollection-assume_role_hosted_zone_update

Also places where we hard-coded the old Zone ID: https://github.com/search?type=Code&q=Z3THRVQ5VDYDMC

Done.


React 0.14

Hey, I'm using this in my project and since I'm updating to react 0.14 made some changes for this to comply, check it here: https://github.com/relax/react-colorpicker
I think it's only missing the documentation and examples, if you want make some changes there and then I can PR to merge here :)

@bruno12mota
Maybe create straight PR, so the diff, and comments are all in one place.
Did you get your version working with React 0.14 ?
I am getting:
Uncaught Error: Invariant Violation: ColorPicker.render(): A valid ReactComponent must be returned. You may have returned undefined, an array or some other invalid object.


Add Red Hat OpenJDK8

This pull request adds the manifest for Red Hat OpenJDK 8.
While the substance of this pull request should be good to merge, I do want to bring up the subject of how Java implementations should be packaged going forward:

There are multiple versions of Java that are supported (Java 8, Java 11, and Java 14 in the case of Red Hat's builds)

Should they be packaged RedHat.OpenJDK8, RedHat.OpenJDK.8, or all under the RedHat.OpenJDK with just their versions differentitating them (please no)
Do we just want to distribute the JDK, or should the JRE be packaged too?

For other implementations there are multiple distributions that may need to be considered (I will bring this up in a future issue though)

edit: I'm a numpty - the URL used here doesn't actually work, jumped the gun on this PR somewhat, forgot that you need to log in first :S Will check whether there are any public downloads, else - apologies for wasting anyone's time.
Either way - the debate about how to package JDK implementations still stands.
Microsoft Reviewers: Open in CodeFlow

I don't believe there are public links for Red Hat's distribution :(
Closing.


MPS classifier

An implementation of DMRG style optimization of a linear MPS classifier

looks like one of your tests is failing because it doesn't have the training data. Can you mock the data in the test instead?

Oh I missed that one! I'll remove it now

oh damn, yes forgot the data ...

should be fixed


Unable to access ecrire from an external access.

I am not able to access to the ecrire application from an external computer.
For example, when I access localhost:3000 I get the content.
However, when I access xxx.xxx.xxx.xxx:3000 where xxx.xxx.xxx.xxx is the IP of my machine, the access is not allowed.
I know that it's not a problem with the configuration of the ports of my server, because when I run something else on port 3000, it works just fine.
Answer from @pothibo in #130 : "Yes, this is a known issue which is somewhat low priority as I don't really need that feature. I'm pretty sure it's very easy to fix however as I believe Rails does it out of the box, so it's just a matter of bridging Ecrire to Rails."

Alright, so I believe that Rails support this feature. My take is that there is an option that is not passed down to Rails when loading the server.
As a reference, ecrire server is a method that wraps around rails server
Maybe the reverselookup option is not set... Not sure if it's there from Rails 5 (Master is Rails 5).

From what I understand by looking quickly, if we bind the -b parameter of rails server to the IP of the machine it should work.

The -b parameter is also required when using a docker container so this might be important to fix.


ACCUMULO-4498 Remove vestigial security permission stuffs

https://issues.apache.org/jira/browse/ACCUMULO-4498

@joshelser I was particularly interested in having the removal of that doPrivileged block reviewed. I really have no idea why it was there in the first place, and I can't imagine any time where it would actually be useful.

I was particularly interested in having the removal of that doPrivileged block reviewed

Yes, I did notice that removal. I'm not super familiar with the AccessController outside of the context of my messing around Kerberos/JGSS. I couldn't venture a guess as to why we wouldn't want to remove the privileged execution call.

From what I can tell, this class came from Hadoop TFile, which does not have it. I checked the pre-ASF history, and there's no explanation for it, so I guess I'll include the removal of that block with these custom permissions.


Route prefix support?

Hi, currently we have an issue eg.
Normally when we request to Monitoror we using something like
http://localhost:8080/?configPath=./config.json
Is there any possible way that we can set up a route prefix? eg
http://localhost:8080/test-prefix/?configPath=./config.json
Thank you.

What's the usecase?

Currently, we have internal infrastructure that defines by a prefix.
We host integration environment on something like
https://int.development.internal/service1
https://int.development.internal/service2
And we found that this monitoring tool can help us on monitoring our service.
It will be something like https://int.development.internal/monitoring/?configPath=./config.json
But we try a lot of ways to use it with this route prefix eg. reverse proxy but no luck.
Would be possible or any suggestion for us on this?

Hello!
After a simple test with Nginx:
  location /monitoror/ {
    proxy_pass http://localhost:8080/;
  }

Monitoror UI try to load assets in / and not /monitoror/.
We will fix this for the next release ^^

Hello!
After a simple test with Nginx:
  location /monitoror/ {
    proxy_pass http://localhost:8080/;
  }

Monitoror UI try to load assets in / and not /monitoror/.
We will fix this for the next release ^^

That exactly what we met, We can get Monitoror page but it load assets in / without prefix
Thank you for adding this to the next release.
great job guys!


Initial auto-instrumentation of NestJS

Superseded by https://github.com/signalfx/signalfx-nodejs-tracing/pull/4.


Refactors in round.go

Closes #181

Simplified round struct a lot:

removed unnecessary channels,
simplified state, removed duplication,
found and fixed a few bugs in state persistence

Added unit tests and cleaned the existing ones for better readability

@fasmat I changed accordingly to your comments. Please, take a look again.


do not carry out insert/remove in out-of-sync links

Scope & Purpose
Backport of https://github.com/arangodb/arangodb/pull/17046
do not carry out insert/remove in out-of-sync links, in case we want queries to fail on out-of-sync links. otherwise, carry out these operations.

[x] :hankey: Bugfix
[x] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[x] Tests

[ ] Regression tests
[ ] C++ Unit tests
[x] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[x] Backports

[x] Backport for 3.10: this PR
[ ] Backport for 3.9: (Please link PR)
[ ] Backport for 3.8: (Please link PR)

Related Information

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket:
[ ] Design document:

Unrelated failure in Jenkins.


Move assertJavascriptVariables from STDcheck to FlexibleMink

Various methods were added to STDcheck's WebContext instead of adding them to FlexibleMink. This is one of many PRs that will move these methods so that all projects using FlexibleMink can utilize them.

Testing file changes were not found.
Paging @johnnie502 to review the back-end work in this pull request!
Paging @ramsey-medology to review the testing work in this pull request!

@ramsey-medology I'll be adding thorough testing as I start to extract the functionality to better architected/documented/tested packages such as BehatRetryExtension and BehatNounStoreExtension.


fix JS exception about missing fonts in open/save dialogs #2634

path '../components/bootstrap/fonts/' was hardcoded in the core/src/main/web/app/styles/ipython/style/style.min.css. It is replaced to the correct path in the gulp file now

:+1:


swift package add-dependency-to-target command

Description
Would be nice if there was also a command to add a dependency to a target of a package.
Expected behavior
A command like swift package add-dependency-to-target would be optimal (with a better name maybe).
It can work like:
swift package add-dependency-to-target --target MyAppTarget --name DiscordHTTP --package DiscordBM

Actual behavior
No such commands.
Steps to reproduce
Feature Request - No steps to reproduce.
Swift Package Manager version/commit hash
Swift Package Manager - Swift 6.0.0-dev
Swift & OS version (output of swift --version && uname -a)
swift-driver version: 1.109.2 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.300 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0
Darwin ---.local 24.0.0 Darwin Kernel Version 24.0.0: ---; root:xnu-11<IP_ADDRESS>1.3~1/RELEASE_ARM64_T6000 arm64

Hello @MahdiBM! Thanks for publishing this feature request - I was taking a look at the current available commands for SwiftPM and noticed the following existing command:
swift package add-target-dependency --help
OVERVIEW: Add a new target dependency to the manifest

USAGE: swift package add-target-dependency <dependency-name> <target-name> [--package <package>]

ARGUMENTS:
  <dependency-name>       The name of the new dependency
  <target-name>           The name of the target to update

OPTIONS:
  --package <package>     The package in which the dependency resides
  --version               Show the version.
  -h, -help, --help       Show help information.

Is this the behaviour you were looking for?

Yes. Apparently it got added at some point. I just tested with the latest main snapshot and it does work as expected.


0.25.0 - identityValueTransformer being removed incorrectly when assigning a custom date formatter.

I've been pulling my hair out trying to debug RestKit and understand what is going on.
Running Xcode 7.0, iOS 9, OS X 10.11 (15B17c)
In my scenario a single string cart_id in my JSON is refusing to be mapped to an NSString in my local object.
Digging deeper into the inner workings of RestKit and RKValueTransformers I've managed to identify that the identityValueTransformer is being removed from the compound transformer before the method valueTransformersForTransformingFromClass:toClass is called. Therefore the mapping fails to find any value transformer to map the String to NSString because the identityValueTransformer is missing.
Having put a break point on the removeValueTransformer: method I see that the identityValueTransformer is being removed by the callee [RKObjectMapping setDateFormatters:].
Looking at what the [RKObjectMapping setDateFormatters:] method does and it looks like it removes the default date formatters before adding the custom ones. Printing out what RestKit thinks is a Date Value Transformer reveals the following transformers to be removed:
<RKBlockValueTransformer: 0x141011710, name: identityValueTransformer>,
<RKBlockValueTransformer: 0x141012c50, name: nullValueTransformer>,
<RKBlockValueTransformer: 0x14100e070, name: iso8601TimestampToDateValueTransformer>,
<RKBlockValueTransformer: 0x141012df0, name: timeIntervalSince1970ToDateValueTransformer>,
<NSDateFormatter: 0x141012cc0>,
<NSDateFormatter: 0x1410134a0>,
<NSDateFormatter: 0x141013830>,
<NSDateFormatter: 0x141013ac0>,
<NSDateFormatter: 0x141013d50>

The identityValueTransformer and nullValueTransformer look suspicious here, neither are date formatters or date value transformers and it looks like RestKit is incorrectly removing them.
My RKObjectMapping looks like this:
    NSDateFormatter *dateFormatter = [[NSDateFormatter alloc] init];
    [dateFormatter setLocale:[[NSLocale alloc] initWithLocaleIdentifier:@"en_US_POSIX"]];
    [dateFormatter setDateFormat:@"MM/dd/yyyy HH:mm:ss"];

    RKObjectMapping *cartMapping = [RKObjectMapping mappingForClass:[ShoppingCart class]];
    [cartMapping addAttributeMappingsFromDictionary:@{
        @"created_stamp": @"cart_date",
        @"cart_id": @"cart_id",
        @"total_offer_price": @"total_offer_price"
    }];
    cartMapping.dateFormatters = @[dateFormatter];

JSON looks like:
{
  "cart": {
    "created_stamp": "09/30/2015 10:48:00",
    "cart_id": "50034262",
    "products": [],
    "promos": [],
    "total_offer_price": 7.03
  }
}

The cart_id won't map and is just is set to nil. I get the usual message that RestKit failed mapping.
I know the dateFormatters method on RKObjectMapping is deprecated but I was unsuccessful at getting RestKit to accept my custom NSDateFormatter using the valueTransformer property.
If I set the custom NSDateFormatter using the valueTransformer property of RKObjectMapping then nothing but the date is mapped, all the other properties are nil and fail mapping.

Ah that's no good :(
Can you try coming up with a PR to make sure the identity and null value transformers aren't removed?

I did manage to sort out the mapping issue by using the valueTransformer instead of the deprecated dateFormatters property of RKObjectMapping. I did not realise that you had to cast the current valueTransformer to add the additional NSDateFormatter e.g.:
[(RKCompoundValueTransformer *)cartMapping.valueTransformer addValueTransformer: dateFormatter];

This above seems to work as expected but using the legacy dateFormatters property does not so it seems like there is a bug surrounding the deprecated API.
I'll dig deeper and try and work out why the legacy API is not working as expected.

Ah don't bother, I should probably just remove the deprecated api. Thanks for digging in!

The issue came about because we updated an old project that was using 0.20.0 to 0.25.0. I guess there could be more people doing this so it's probably worth removing the old date API. The deprecation message in the Ccocadocs just said use the valueTransformer property instead, which led me to believe I could just assign a NSDateFormatter to the valueTransformer property.
Can I suggest the documentation is updated because I found it unclear how to apply a NSDateFormatter using the newer API.  Thanks.


Application previously using this gem has several issues trying to upgrade

The migration barfed when a migration already existed with the same class name.
-- Suggest adding Otp to the migration class name.
The migration assumed second_factor_attempts_count does not exist. This is an issue for apps that already have this column name from previous use of this gem.
Ability to define "login_code_random_pattern" seems to have gone away even though docs still state ability to control login pattern.
Table "valid_mfa_tokens" no longer is necessary (from 0.2 code).
Putting has_one_time_password before "devise :two_factor_authenticatable" causes start up errors
-- Using Thin 1.6.2; Rails 4.0.4
Documentation still mentions ":second_factor_pass_code" (README.md)
When trying to get access to the otp_code in the model's send_two_factor_authentication_code implementation method, the following gets thrown.
-- undefined method `scan' for nil:NilClass

Using the new remember_otp_session configuration.  Had to manually go into the gem's directory to update. Works locally but trying to build to production (jenkins), and new configurations aren't there. Have you worked out how to migrate the changes?


Script not found error message when running Prisma commands in Bun

Bug description
When running the commands below in a Bun Docker container (e.g. oven/bun:1.0.30-slim), the output shows
error: Script not found "/home/bun/app/hello-prisma/node_modules/prisma/build/child"

I cannot pinpoint this issue to an exact location in Prisma’s source code, but there is a line in the minified bundle that reads
childPath=path__default.default.join(eval("__dirname"),"child");

Changing child to child.js there removes the error message.
This is reported in https://github.com/oven-sh/bun/issues/9237 as well – not sure if this is an issue with Prisma or with Bun’s module resolution.
How to reproduce
mkdir hello-prisma
cd hello-prisma
bun init -y
bun install prisma
bun prisma init

Expected behavior
No error message.
Prisma information
Not relevant at this point.
Environment & setup

OS: debian:bullseye-slim-based Docker container
Database: N/A
Node.js version: Bun revision 1.0.30+1424a196f

Prisma Version
# bun prisma -v
Environment variables loaded from .env
prisma                  : 5.10.2
@prisma/client          : Not found
Computed binaryTarget   : linux-arm64-openssl-1.1.x
Operating System        : linux
Architecture            : arm64
Node.js                 : v21.6.0
Query Engine (Node-API) : libquery-engine 5a9203d0590c951969e85a7d07215503f4672eb9 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 5a9203d0590c951969e85a7d07215503f4672eb9 (at<EMAIL_ADDRESS>Schema Wasm             : @prisma/prisma-schema-wasm 5.10.0-34.5a9203d0590c951969e85a7d07215503f4672eb9
Default Engines Hash    : 5a9203d0590c951969e85a7d07215503f4672eb9
Studio                  : 0.499.0
error: Script not found "/home/bun/app/hello-prisma/node_modules/prisma/build/child"

Ah – there it is again.

This was indeed an issue in Bun, not Prisma, and has been fixed in oven-sh/bun#9237.


Update libraries-and-tools.md

Add cetcd as a C library

looks pretty nice. could you update the commit message to docs: add cetcd into libraries-and-tools.md? so the commit history could be more readable.

NP

I did a force update (I think no one has pulled shafreeck/etcd) but  failed the travis-ci's checking. I don't know why.

travis may fail in low ratio because sometimes it has rather slow IO or halt for a while.
lgtm

Thanks for the contribution!


Add menu functionality

In this branch i:

Added JS files
Added mobile menu functionality with JS
Style open mobile nav menu
Add eslint files


RWIB Mission 2: Community Page

Link.
Today the navbar is overrun by 'community' links, but still there is more
info to disseminate. Create a new page, to be linked from a single new
'Community' navbar link. This page needs to be a friendly and
accessible intro to the world of Rust.
Subjects covered should include:

The importance of the COC (with link) and diversity
Team structure (with link)
The community and moderation teams in particular
The RFC process, with link to RFC readme
Subteam reports and TWiR
Forums, IRC and other communication venues
It should explicitly explain how to get help
Calendar. Try to embed a combination of the event calendar and the release calendar.
List of meetup groups
blog
twitter

Think about how to organize this by audience. Some community members
are devs and some are users. Consider that the primary audience for
this page is mostly users, for the contributing page is mostly devs.
Come up with a design that conveys all of this information, either
directly or through additional links, without being overwhelming. This
will be one of the most important newbie resources.
I'm most worried here about conveying a dedication to diversity, as we
don't have a lot of existing material to crib off of, there's overlap
with the CoC, and anything we say needs to be worded artfully.
Adapt material from [the current
docs](file:///home/brian/dev/rust2/build/doc/index.html#community-&-getting-help).

#117 re: the calendar point in the list above.

I'd like to take on Mission 2.

@efindlay You got it! Keep be updated on your progress!


kernel version: use the debian stable version (6.6)

We do not need to use the backported version anymore. 6.6 contains all the features we need + it's LTS.

Which features were required? The default Kernel version in Debian 12 stable is 6.1 not 6.6

You are right, my mistake.
The use of the backported version was when we were still in debian 11, running 5.10. I can't remember exactly what was missing at that time.
The thing is, with debian12, kernel 6.1 is a appropriate default.
The seapath user can still choose to upgrade to bookworm-backport if he needs (for hardware support reasons maybe?), the point is that 6.1 for a default version is enough.


some NHK Vods are currupt (?) or not fully downloading.

Have a folder of around 10 or so various random episodes that for some reason do not decide to play in anything, despite having returned no errors whilst downloading. Have repeated the downloads many times and always the same, they just don't play or open in anything, even various video tools apps.
What's strange is the Vods play as expected on the website, so the source is fine. It's also random, maybe 1 out of a season will not play.
Here's an example (which also downloads only half the file size)
https://www3.nhk.or.jp/nhkworld/en/ondemand/program/video/10yearshayaomiyazaki
episodes 2 and 4 do not play after downloading, and only downloads around 1.4GB, despite showing that the 'best' is around 3.6GB.
Episodes 1 and 3 do download fully and are around 3.6GB.
also note the odd random numbers at the end of the filenename...
http-10262   mp4        1920x1080  10262k video@9765k, audio@497k, 3.60GiB (best)
youtube-dl -f best https://www3.nhk.or.jp/nhkworld/en/ondemand/video/3004581/
[download] Destination: 10 Years with Hayao Miyazaki - Ep. 2 Drawing What's Real -eb67a418.mp4
[download] 100% of 1.43GiB in 06:38
if anyone can figure this out or have any pointers let me know! thx

Tested Ep. 2:
youtube-dl -v https://www3.nhk.or.jp/nhkworld/en/ondemand/video/3004581/
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://www3.nhk.or.jp/nhkworld/en/ondemand/video/3004581/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] exe versions: ffmpeg 3.4.8, ffprobe 3.4.8, rtmpdump 2.4
[debug] Proxy map: {}
[NhkVod] 3004-581: Downloading JSON metadata
[Piksel] p0MjdqaDE6aSAVsRCNY5hpOxhjkcE3Wx: Downloading webpage
[Piksel] p0MjdqaDE6aSAVsRCNY5hpOxhjkcE3Wx: Downloading JSON metadata
[Piksel] p0MjdqaDE6aSAVsRCNY5hpOxhjkcE3Wx: Downloading JSON metadata
[Piksel] eb67a418: Downloading m3u8 information
[Piksel] eb67a418: Downloading SMIL file
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on u'http://mz-nhk10.mzpf.webcdn.stream.ne.jp/www60/mz-nhk10/media/mm/flvmedia/5905/m/F/m/mF_mp4file10249964-3714035.mp4?cid=5905&aid=3714035&afid=7841762&assetid=3714035'
[download] Destination: 10 Years with Hayao Miyazaki - Ep. 2 Drawing What's Real-eb67a418.mp4
[download]   1.1% of 1.43GiB at  1.72MiB/s ETA 14:00^C

curl -v 'http://mz-nhk10.mzpf.webcdn.stream.ne.jp/www60/mz-nhk10/media/mm/flvmedia/5905/m/F/m/mF_mp4file10
249964-3714035.mp4?cid=5905&aid=3714035&afid=7841762&assetid=3714035'
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to mz-nhk10.mzpf.webcdn.stream.ne.jp (<IP_ADDRESS>) port 80 (#0)
> GET /www60/mz-nhk10/media/mm/flvmedia/5905/m/F/m/mF_mp4file10249964-3714035.mp4?cid=5905&aid=3714035&afid=7841762&assetid=3714035 HTTP/1.1
> Host: mz-nhk10.mzpf.webcdn.stream.ne.jp
>
< HTTP/1.1 200 OK
< Date: Mon, 01 Feb 2021 12:33:31 GMT
< Content-Type: video/mp4
< Content-Length:<PHONE_NUMBER>
< Connection: keep-alive
< Keep-Alive: timeout=3
< Last-Modified: Thu, 15 Aug 2019 06:12:11 GMT
< Via: JSTCDN
< X-Cache: HIT/S
< X-Cache-Age: 10/300
< X-Origin-Date: Mon, 01 Feb 2021 12:33:21 GMT
< Accept-Ranges: bytes

Given that the CDN is giving Content-Length:<PHONE_NUMBER> I suspect some of the videos uploaded to there are corrupt. Hence not an issue with youtube-dl per se.

Hi, I recently ran into this and used this workaround.
It's very likely the best quality VOD is corrupt.  Instead, find out the next lower quality file with the -F flag and download after with the -f command.
In my case, the 1080p (best) quality was corrupt so I settled for the 720p file instead.

I happened to notice an update to this issue report, so I thought I'd mention it.

also note the odd random numbers at the end of the filenename...

It's a video id and if you don't like the default filename, use -o option. Read OUTPUT TEMPLATE.

Continued in #30931.


[Add] Developer Roadmaps

Site URL
https://roadmap.sh/
Description of the above provided site
roadmap.sh is a community effort to create roadmaps, guides and other educational content to help guide developers in picking up the path and guide their learnings.
Category
Other
Sub Category
other resources
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[ ] I am a GSSoC'23 contributor

Hello @${author}! Thank you for raising this issue! 😊 Your contribution is valuable to us! 😊

@CBID2 I think there's some typo in greetings yml as its supposed to say the author name instead of showing the syntax.

Hello @${author}! Thank you for raising this issue! 😊 Your contribution is valuable to us! 😊

@CBID2 I think there's some typo in greetings yml as its supposed to say the author name instead of showing the syntax.

I can look into this issue

Hello @${author}! Thank you for raising this issue! 😊 Your contribution is valuable to us! 😊

@CBID2 I think there's some typo in greetings yml as its supposed to say the author name instead of showing the syntax.

I can look into this issue !


An error occurred during processing; checking has been aborted.

Bug Description
When running the phpcs, I keep getting this error:
 1 | ERROR | An error occurred during processing; checking has been
   |       | aborted. The error message was: trim(): Passing null to
   |       | parameter #1 ($string) of type string is deprecated in
   |       | .../vendor/wp-coding-standards/wpcs/WordPress/Sniffs/WP/I18nSniff.php
   |       | on line 194 (Internal.Exception)

Error Code
Error code is coming from I18nSniff.php
Environment
PHP 8.2.2
PHP_CodeSniffer version 3.7.1
Composer version 2.4.1

Closing as duplicate of something which was fixed a while back. Please search the issues in the repo before opening an issue.

@jrfnl Thank you, I used develop branch and the error is gone


Add Textedit

@brianwatling Used the rows system you put together for a textedit widget and it's looking pretty good! A few things I think we could improve...

I updated some of the structure of nk_console to include a void* data. We may be able to leverage that for nk_console_row's nk_console_row_data to simplify the structure
There is nk_console_row_child::columns. Could we re-purpose nk_console::columns for that?

Overall, the rows worked really well! Thanks so much for the help on it.

I updated some of the structure of nk_console to include a void* data. We may be able to leverage that for nk_console_row's nk_console_row_data to simplify the structure
This would definitely be great. What I did on nk_console_row was non-standard compared to the other widgets and I think it'd be great to make rows in line with the new style you've introduced. I did it that way in the first place mainly as a kludge because I was working on it outside this repo as an extension

There is nk_console_row_child::columns. Could we re-purpose nk_console::columns for that?
nk_console_row_child::columns records the original 'columns' count of the child widgets so  we can set columns = 0 for all the children in a row and nk_console_row_render can be in charge of setting the row layout. I don't see an easy way to use nk_console::columns for that but definitely interested to see any ideas you have

What I did on nk_console_row was non-standard compared to the other widgets

What you did with the data structure inspired the change, so I can't take credit, and you definitely took the correct approach. Thanks a lot.
I'll go through another round of review before merging.


BUG: Issue with subspace_angles

Fixes #9020

@c-meyer Do you mind adding a line break at
https://github.com/c-meyer/scipy/blob/1a31755b243a52bad9d86a2519b77903602ad184/scipy/linalg/decomp_svd.py#L408
just to keep the PEP8 in order. I don't know why Circle CI didn't complain about it. Other than that I think it is good to go.

Now the only thing left I think is to update
https://github.com/scipy/scipy/blob/master/doc/release/1.2.0-notes.rst
To say that the n_col // 2: values were wrong before and have been fixed.
@rgommers we are supposed to update the release notes with each PR with substantial changes, right? Or is that information outdated in https://github.com/scipy/scipy/blob/master/HACKING.rst.txt?

Shall I update the Release notes in my branch such that the line is added by merging the pull request directly or is it up to you (main contributors/maintainers)?
To which section will the bugfix be added? "New features" or "Other changes" ... ?

@c-meyer could you edit https://github.com/scipy/scipy/wiki/Release-note-entries-for-SciPy-1.2.0? Under "other changes" sounds right to me.

@rgommers we are supposed to update the release notes with each PR with substantial changes, right? Or is that information outdated in https://github.com/scipy/scipy/blob/master/HACKING.rst.txt?

good catch, that's outdated.

Probably "Backward incompatible changes" because it does change the results (but this is justified as it's a bugfix). Or are those supposed to live in "Other changes"?

ah yes. "Backward incompatible changes" would be the best place

LGTM, merging. Thanks @c-meyer and all!


Add support for API paging with limit and continue

Implement API chunking support as specified in
https://kubernetes.io/docs/reference/using-api/api-concepts/#retrieving-large-results-sets-in-chunks
Add limit and continue as parameters to get_entities and add continue as an optional attribute (default to nil) to EntityList.
Sample usage:
continue_token = nil
begin
  options = {:limit => 100}
  options.merge!(:continue => continue_token) unless continue_token.nil?

  entities = connection.get_pods(options)
  break if entities.nil?

  continue_token = entities.continue

  # do something with the chunk of entities returned
end until entities.continue.nil?

Fixes: https://github.com/abonas/kubeclient/issues/283

cc @cben @Ladas

Add limit and continue as parameters to get_entities and get_entities

I guess you meant get and watch? :)

I guess you meant get and watch? :)

Yes thank you!

https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.10/#watch-list-65 :
continue — .... This field is not supported if watch is true. ...
limit — .... This field is not supported if watch is true. ...
so not relevant for watch.

Watch? What does chunking mean in context of watch? Also, I don't see changes related to watch.

Ah okay they shared the same arguments as get ref so I thought that was always true.  I'll split those up then so limit/continue aren't possible args for watch

@cben fixed

@cben as for the higher-level vs lower-level interface, I actually like being able to process the chunks rather than just getting an iterator because I want to save the smaller chunks as well.
I can definitely see the benefit of a "nicer" iterator though where the caller doesn't have to worry about it, but this is closer to how the API is implemented.

@cben I pushed a version which always uses paging and handles the continue internally, either yielding the batches or returning the full list if no block is given.  This makes it easier on the callers but I haven't found a nice way of cleanly handling the format_response since it parses the body and I had to parse the JSON to get the continue out of the payload.

I now lean towards the low-level version, which does the job, is 100% opt-in, and has no open questions.

Yeah I agree, it is simple and lets us get this functionality in without changing the default behavior.
I'll work on the docs/changelog/tests now, thanks @cben !

docs (with usage example; mention risk of 410 Gone; mention servers may ignore it). changelog if possible.

Added, please check that they meet with what you expected.  I added an Unreleased section to the changelog similar to how we handle per-sprint manageiq changelogs, when you cut another release you can just replace that with the release number.

some tests? I'd include both responses from server supporting limit/continue, and a server that ignores limit.

I added a simple test where two pages are returned.  I am going to add a test for 410 Gone condition as well.  I'll need to try to find a pre-1.9 cluster to test a server that doesn't support chunking though, any hints?

@cben can you take another look?  I updated the readme and added tests for 410 gone

LGTM :100:

Thanks so much @cben!


Prepare v3.10.4

Upgrade CRDs and secondary resources to v1 to support Kubernetes v1.22+ / OpenShift 4.9+

@vmanley @Bobbins228 would you mind giving this version a try? You can use the included deploy/operator.yaml and the CRDs in deploy/crds.

@pb82, v1beta1 is still used by ingresses, I think we also want to change these to networking/v1
W0928 11:39:08.323960  871709 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

@HubertStefanski yes, definitely. I thought I had updated Ingress. Will look for remaining v1beta resources.

@HubertStefanski updated now :+1:

I just tested it out there a second time and these are the errors I am getting
W0928 13:21:29.940911   16854 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0928 13:21:30.277193   16854 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
The CustomResourceDefinition "grafanas.integreatly.org" is invalid: spec.preserveUnknownFields: Invalid value: true: must be false in order to use defaults in the schema

I'm seeing similar issues on my brand new 1.22 kind cluster.
We also need to update: https://github.com/grafana-operator/grafana-operator/blob/master/deploy/role.yaml and
https://github.com/grafana-operator/grafana-operator/blob/50ab03d9e6f49cd78204460dedd56c05a47d3bbd/deploy/roles/role.yaml#L68-L71
instead of saying extensions, it should say networking.k8s.io

@Bobbins228 how are you deploying the CRDs? Are you applying manually from deploy/crds?

Looks that you found the last of the old ingress versions, nice job! :1st_place_medal:
I will verify first thing tomorrow morning.

@NissesSenap Thanks! Let me know if everything works for you. If it does, I'll create the release PR.

LGTM, great job once again!


Support standard npm git tag conventions

If I do bower install foo#1.2.3, it will check foo's git repo for the 1.2.3 tag. However, npm modules, via convention and the npm version command, would have a tag v1.2.3.
It would be ideal if bower worked automatically with that tag naming convention, so that I can stick with the "v" prefix - that should reduce friction with npm modules that want to add a bower.json. Otherwise, I have to create two parallel tags with each new version, which is just messy.
See https://github.com/es-shims/es5-shim/pull/171 for some context.

In the latest version I get this:
bower not-cached    git://github.com/joallard/fb-login.git#0.1.0.alpha
bower resolve       git://github.com/joallard/fb-login.git#0.1.0.alpha
bower ENORESTARGET  Tag/branch 0.1.0.alpha does not exist

Additional error details:
Available tags: v0.1.0.alpha, v0.1.0a
Available branches: master


Update to the latest API schema.

We're in need of the peering information in Terraform. https://github.com/terraform-providers/terraform-provider-heroku/pull/57 adds support to the Heroku provider. This in turn can be used to automate the configuration of peering connections with AWS VPCs.

🎉


Add TMA FOV validation functions for user sanity checking

What is the purpose of this PR?
Closes #16 (and closes #18). Users may need some guidance as to which FOVs are the most likeliest that need remapping. This includes:

User-proposed FOVs that are far away from their auto-generated FOV
User-proposed FOVs mapping to the same auto-generated FOV
User-proposed FOV names that don't match their corresponding auto-generated FOV names.

We want a way to display these to the user on the initial visualization, as well as update them on the fly when the user remaps FOVs.
How did you implement your changes
We allow the user to specify which combination of the 3 issues stated above they wish to validate in autolabel_tma_cores.ipynb. Each of these issues is handled in a separate validation function that builds a list of mappings that do not pass the specified tests. These non-passes will be displayed in a text box right above the slide image display.

Ok everything should be updated per our standup now. The validation text box is now just half of the original width.
I've also added tests for the dropdown menu functionality (finally).

NOTE: now that we're running a lot of tests for certain functions randomizing order, need to start moving away from simple != testing for randomization (the branch is failing again because of this, it'll happen more often than usual if we're running a double-digit amount of tests on these functions). I think the best way to handle this is to start using a random seed for these functions, although I'm open to other ideas.

More along the lines of setting consistent random seeds, looks like the pytest-randomly library may allow us to do this fairly seamlessly: https://github.com/pytest-dev/pytest-randomly.

After some thought, I've decided to do some major restructuring to the pipeline:

assign_closest_fovs will now be a hidden call in tma_interactive_remap...this cell was looking more and more unnecessary by the day and it'll help address the issue of the function being too involved.
We'll have assign_closest_fovs return the original manual_to_auto_map and the numpy.nparray distance matrix (in microns) between each FOV. Having a lookup table for the distances between FOVs in microns will greatly reduce the number of conversion calls we'll need to make when  remap_manual_to_auto_display is called. It also removes the need for a convert_pixels_to_microns function when recalculating distances for validation purposes, preventing inconsistent results (due to floating point precision/rounding errors converting from microns to pixels and back won't yield the same results).

Let me know your thoughts @ngreenwald.

Sure thing, if you think it'll simplify things go for it


Almost all tests fail

Here is the output I get from cabal test:
Running 1 test suites...
Test suite ConstraintTests: RUNNING...
Simple:
  tc1: [Failed]
tc1
expected: [5(),6()]
 but got: []
  tc2: [Failed]
tc2
expected: [5()]
 but got: []
  tc3: [Failed]
tc3
expected: [5(),6()]
 but got: []
  tc4: [Failed]
tc4
expected: [0(),1(),2(),3(),4(),5(),6(),7(),8(),9(),10(),11(),12(),13(),14(),15(),16(),17(),18(),19(),20()]
 but got: []
  tc5: [Failed]
tc5
expected: [0(),1(),2(),3(),4(),5(),6(),7(),8(),9(),10(),11(),12(),13(),14(),15(),16(),17(),18(),19(),20(),21(),22(),23(),24(),25(),26(),27(),28(),29(),30(),31(),32(),33(),34(),35(),36(),37(),38(),39(),40()]
 but got: []
  tc6: [Failed]
tc6
expected: [5(),6(),7(),8()]
 but got: []
  tc7: [Failed]
tc7
expected: [5(),6(),7(),8()]
 but got: []
  tc8: [OK]
  tc9: [Failed]
tc9
expected: [11()]
 but got: []
  tc10: [Failed]
tc10
expected: [5(),6(),7(),8(),11()]
 but got: []
  tc11: [OK]
PointsTo:
  pt1: [Failed]
pt1
expected: ["ref"("b"(), "Xb", "Xb")]
 but got: []
  pt2: [Failed]
pt2
expected: ["ref"("x"(), "Xx", "Xx"),"ref"("z"(), "Xz", "Xz")]
 but got: []

         Test Cases   Total
 Passed  2            2
 Failed  11           11
 Total   13           13

Test suite ConstraintTests: FAIL

I was trying to get the andersen analysis from llvm-analysis to work, but it turns out that the problem is in ifscs. I will investigate this further.
Edit: I guess the bug fixes did not work :P

Here's the fix:
dfs :: (Ord c, Ord v) => IFGraph v c -> SetExpression v c -> Set (SetExpression v c)
dfs g = go mempty
  where
    go !visited v
      | S.member v visited = visited
      | otherwise =
          case M.lookup v g of
            Nothing -> S.insert v visited -- We should still insert it here!
            Just Edges { predecessors = ps } ->
              F.foldl' go (S.insert v visited) ps

With the new alterF function we can even write it like this:
dfs g = go mempty
  where
    go !visited v
      | not b, Just Edges { predecessors = ps } <- M.lookup v g = F.foldl' go visited' ps
      | otherwise = visited'
      where
        (b, visited') = S.alterF (\x -> (x, True)) v visited

Thanks for looking at this!


Refactor codebase

currently have a single large mainwindow class
most non-gui logic is in other classes
but mainwindow still contains some SBML and other non-gui logic

todo

separate non-gui logic (meshing, SBML, etc) into a separate library
refactor each tab in the GUI mainwindow into a separate class with its own .ui file
use model views to further separate logic from GUI #11

resolved by #136


MQTT problem

Hi,
Im not getting the mqtt to work. My setup is latest HA with zigbee2mqtt-addon. When i connect to mqtt through the mqtt-explorer i have to include the password and username for my HA user, can that be the problem?
MQTTLights:
  - lights:
      - zigbee2mqtt/Livingroom Window 1
    automations:
      - time: "07:00:00"

2024-11-02 08:32:30.668784 WARNING Livingroom: ------------------------------------------------------------
2024-11-02 08:32:30.669081 WARNING Livingroom: Unexpected error running initialize() for Livingroom
2024-11-02 08:32:30.669307 WARNING Livingroom: ------------------------------------------------------------
2024-11-02 08:32:30.670621 WARNING Livingroom: Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/appdaemon/app_management.py", line 162, in initialize_app
    await utils.run_in_executor(self, init)
  File "/usr/lib/python3.11/site-packages/appdaemon/utils.py", line 304, in run_in_executor
    response = future.result()
               ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/apps/lightwand.py", line 186, in initialize
    light = MQTTLights(self,
            ^^^^^^^^^^^^^^^^
  File "/config/apps/lightwand.py", line 1685, in __init__
    self.mqtt.mqtt_subscribe(light_topic)
    ^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'mqtt_subscribe'

2024-11-02 08:32:30.670888 WARNING Livingroom: ------------------------------------------------------------

If you are running zigbee2mqtt inside HA as addon there is probably no advantages to my knowledge to call mqtt since the calls would go thru HA anyway. Addons is a bit unfamiliar territory for me so I might be wrong.
NoneType is probably because there is no light at "zigbee2mqtt/Livingroom Window 1". Have you configured MQTT in appdaemon?
If you are running Appdaemon as a addon there might be some documentation in HA on how to set up MQTT. Or check Appdaemon documentation: https://appdaemon.readthedocs.io/en/latest/CONFIGURE.html#mqtt

Of course, my bad. MQTT wasn´t configured in Appdaemon, thanks.


Allow Site ID to be more Generic

It would be nice if Site ID was not limited to u32 as a datatype, and instead could be anything that implements the traits needed to function.  (I.e, Serde traits + Eq and Hash).  I'm not sure how tightly coupled the implementation is to u32 at the moment.
This would allow a more decentralised approach at Site IDs, by using something such as a Random UUID to be used in place of a u32

Site IDs are limited to compact types like u32 because they are included in the UID of each CRDT element (i.e. a List with 100 elements requires 100 site IDs). Larger site IDs like UUIDs create more overhead per element (4 bytes vs 16 bytes).
One workaround may be to use u32 internally and another value (like a UUID or even a generic hashable type) externally, and maintain a map between them. This would add complexity to the codebase but if it's a popular need I could see adding it.

I was thinking have it generic, so you could use u32, usize, u64, i64, etc.. whatever you felt the need to be, but I guess a simple mapping may work.

I think the use case here would be randomly assigned site IDs with low probability of collision. A u64 allows for 1 billion users with a collision probability on the order of 5e-10.
I understand what you're saying about the overhead problem but I took a look at the implementation and because you used a newtype it seems like it would be very straightforward to add a cargo feature for which type you want to use using conditional compilation.
For the simplicity tradeoff of using u64 to randomly assign site ids I think decentralized software coders would happily take the memory tradeoff then optimize later with raft etc if need be.


[FLINK-28950][HBase] Disable HBase2 version check in hbase-default.xml

What is the purpose of the change
With the version check enabled, hbase connector can write to hbase 2.2.3 only. Disable the version check to support hbase 2.X.
Brief change log
Update the default value of  hbase.defaults.for.version.skip in
flink-connectors/flink-sql-connector-hbase-2.2/src/main/resources/hbase-default.xml
Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is already covered by existing tests, such as (please describe tests).
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

The failed test seems to have nothing to do with this fix.

@flinkbot run azure

@xicm thanks for your contribution
The Flink HBase connector resides in it's own repository nowadays, if this code change is still relevant, please open the PR in https://github.com/snuyanzin/flink-connector-hbase


Styling create challenge

To test:

Run code as normal, go to create a challenge.
Style should look better and similar to login page, but work the same.

What I did:

Wrote CSS for the create a challenge page.

 Add CSS styling


Component tree not supported

Version
6.0.0-beta.1
Browser and OS info
google chrome latest, windows 10
Steps to reproduce
load page and see Component tree not supported
What is expected?
show the vue components
What is actually happening?
nothing show, i dont see my vue components

I've got the same issue.

Same here

Same here

Same here

My issue was I was using the beta & Vue 2 which is no longer supported. Maybe this helps someone here too https://github.com/vuejs/vue-devtools/issues/1241#issuecomment-662074495

A very ridiculous version push, it's a completely separated version from before!

same here

My issue was I was using the beta & Vue 2 which is no longer supported. Maybe this helps someone here too #1241 (comment)

Yet! :cat2:

A very ridiculous version push, it's a completely separated version from before!

Hence the major version bump and the separate beta version.

My issue was I was using the beta & Vue 2 which is no longer supported. Maybe this helps someone here too #1241 (comment)

Yet! :cat2:

A very ridiculous version push, it's a completely separated version from before!

Hence the major version bump and the separate beta version.


lnwallet+lnd: support watch-only initialization for lnd nodes

This issue is related to this on going btcwallet PR which adds watch-only support to btcwallet as well as our issue tracking PSBT integration within lnd, and finally #3929 . Once those items are carried out lnd will be able to operate in a mode wherein it requires no private key material to be accessed within the main process. As a result, we'll need a slightly different initialization mode for lnd in order to support this new operating mode. As is, when creating a new lnd instance you need to either provide raw entropy which is used to derive a master private key, or an aezeed. What we need instead, is a new more which accepts a series of xpubs, which are them imported into the internal wallet.
Steps to Completion

[x] Add a new set of RPC calls to the WalletKit sub-server that allows a user to export a given xpub based on a target key family.

[ ] Extend the existing InitWalllet RPC call to support importing a set of base xpubs: one for each of our currently used active key families. Note that we need to import each xpub rather than a single one derived from the main seed as each key family or account uses hardened derivation for everything "above" it.

[ ] This new watch-only variant will then need to interact with each of the yet-to-be-finalized APIs in the btcwallet PR referenced above to import each of the xpubs for each key family into the wallet.

Note that we'll need to complete #3929 before this issue can be fully implemented.

https://github.com/btcsuite/btcwallet/pull/667 has been merged now, which unblocks this PR once #3929 is in, although they can be worked on concurrently.

Keeping this open for now as the second point to extend InitWallet to allow the relevant key families ti be passed in isn't yet resolved. This is the missing gap that would allow stuff like lnd just having the raw account xpubs for the multi-sig keys with signing being done in a remote/detached manner.

Closing this as the final item is being tracked in a new issue now.


Documentation Error on Wallet API "Decode an Invoice", incorrect Body

It appears the documentation for the lnbits wallet api "decode an invoice" (POST /api/v1/payments/decode) is wrong.
Under Body (application/json), it lists {"invoice": <string>}, while the curl example uses '{"data": <bolt11/lnurl, string>}'.
Body (application/json) should list '{"data": <bolt11/lnurl, string>}' to match the correct curl example.

That's just the way curl works, i think... If you're using fetch/axios whatever, you don't do {data: ...}


Adding alerts stream in OpsGenie Connector

Description

Provide description here

Type of change

[X ] New feature

Extra info

Adding Alerts stream in OpsGenie connector

Test Results
➜  opsgenie-source git:(mudasir/adding_alerts_stream_opsgenie) npm test

><EMAIL_ADDRESS>test
> jest --verbose --color

 PASS  test/index.test.ts
  index
    ✓ spec (2 ms)
    ✓ check connection (1 ms)
    ✓ check connection - incorrect config (1 ms)
    ✓ streams - incidents, use full_refresh sync mode (2 ms)
    ✓ streams - incidents, paginate
    ✓ streams - teams, use full_refresh sync mode (1 ms)
    ✓ streams - users, use full_refresh sync mode (1 ms)
    ✓ streams - users, paginate
    ✓ streams - alerts, use full_refresh sync mode (1 ms)
    ✓ streams - alerts, paginate (1 ms)

Test Suites: 1 passed, 1 total
Tests:       10 passed, 10 total
Snapshots:   0 total
Time:        0.45 s, estimated 5 s
Ran all test suites.
➜  opsgenie-source git:(mudasir/adding_alerts_stream_opsgenie)

I have read the CLA Document and I hereby sign the CLA

recheck


Added ACME integration to create new certificates

What does this PR (Pull Request) do?

[x] This PR is not related to any Issue

Which Traffic Control components are affected by this PR?

Documentation
Traffic Ops
Traffic Portal

What is the best way to verify this PR?

Set up an ACME account with a provider.
Go to a Delivery Service that has HTTPS enabled, go to manage SSL Keys, Generate SSL Keys
Click on the Use ACME slider
Choose your ACME provider from the drop down
Generate keys and verify that you got a new certificate from your ACME provider
Verify that the Let's Encrypt functionality still works as before
Verify that the /acme_accounts/providers endpoint returns all ACME providers in the cdn.conf file as well as Let's Encrypt
If this is a bug fix, what versions of Traffic Control are affected?

The following criteria are ALL met by this PR

No tests added since this all depends on 3rd parties

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

Closing and replacing with https://github.com/apache/trafficcontrol/pull/5728 due to case sensitivity issues


[BUG] AssertionError

This is a :bug:
Version Info

Version of Majestic: 0.2.0
Version of Jest: 22.2.1
Version of Node: v8.11.2
Operating System: OS X

AssertionError {
  name: "AssertionError",
  actual: "",
  expected: true,
  operator: "==",
  message: "missing path"…
}
at Module.require (module.js:496:3)↵    at require (internal/module.js:20:19)↵    at a (file:///Applications/Majestic.app/Contents/Resources/app.asar/renderer.js:1:774)↵    at t.c (file:///Applications/Majestic.app/Contents/Resources/app.asar/renderer.js:1:1893)↵    at s (file:///Applications/Majestic.app/Contents/Resources/app.asar/renderer.js:1:4076)↵    at We.loadTestFiles (file:///Applications/Majestic.app/Contents/Resources/app.asar/renderer.js:3:7612)↵    at y.then (file:///Applications/Majestic.app/Contents/Resources/app.asar/renderer.js:3:8287)↵    at <anonymous>"__proto__: Error

Also tried this on the new alpha build, no success there either
Majestic v1.0.6
Zero config UI for Jest
visit http://localhost:3005
Killing the runner before exit
events.js:183
      throw er; // Unhandled 'error' event
      ^

RangeError: Invalid WebSocket frame: invalid status code 23982
    at Receiver.controlMessage (/usr/local/lib/node_modules/majestic/node_modules/ws/lib/receiver.js:441:18)
    at Receiver.getData (/usr/local/lib/node_modules/majestic/node_modules/ws/lib/receiver.js:329:42)
    at Receiver.startLoop (/usr/local/lib/node_modules/majestic/node_modules/ws/lib/receiver.js:133:22)
    at Receiver._write (/usr/local/lib/node_modules/majestic/node_modules/ws/lib/receiver.js:69:10)
    at doWrite (_stream_writable.js:397:12)
    at writeOrBuffer (_stream_writable.js:383:5)
    at Receiver.Writable.write (_stream_writable.js:290:11)
    at Socket.socketOnData (/usr/local/lib/node_modules/majestic/node_modules/ws/lib/websocket.js:795:35)
    at emitOne (events.js:121:20)
    at Socket.emit (events.js:211:7)

Hey @Neglexis,
I published a new version of the new alpha build. Could you please try again and let me know if you run into any issues again?

@Raathigesh Appears to work, awesome! Looking good as well!

Please feel free to report anything that needs to be looked into.


Use bindgen on docs.rs

Currently, the build on docs.rs fails with the following error (ref: build log). This is because the precomputed bindings for the version of R that docs.rs uses, R 3.6, doesn't contain the graphics-related objects because the file was generated long ago.
We have several options to avoid this error (see https://github.com/extendr/extendr/issues/415#issuecomment-1186461753), but I believe this is the best; we cannot expect what version of R docs.rs will use, but using bindgen should make the build success with arbitrary version.
[INFO] [stderr]  Documenting extendr-api v0.3.1 (/opt/rustwide/workdir)
[INFO] [stderr] error[E0432]: unresolved imports `libR_sys::DevDesc`, `libR_sys::R_GE_gcontext`
[INFO] [stderr]   --> src/graphics/mod.rs:83:20
[INFO] [stderr]    |
[INFO] [stderr] 83 | pub use libR_sys::{DevDesc, R_GE_gcontext};
[INFO] [stderr]    |                    ^^^^^^^  ^^^^^^^^^^^^^ no `R_GE_gcontext` in the root
[INFO] [stderr]    |                    |
[INFO] [stderr]    |                    no `DevDesc` in the root
[INFO] [stderr]
[INFO] [stderr] error[E0412]: cannot find type `DevDesc` in this scope
[INFO] [stderr]   --> src/graphics/device_driver.rs:82:32
[INFO] [stderr]    |
[INFO] [stderr] 82 |     fn activate(&mut self, dd: DevDesc) {}
[INFO] [stderr]    |                                ^^^^^^^ not found in this scope
[INFO] [stderr]
[INFO] [stderr] error[E0412]: cannot find type `R_GE_gcontext` in this scope
...snip...

First of all, can we agree on this direction? As commented on #415, there are many possible solutions.

Thanks!


LCMAPS VOMS plugin tests

This adds testing of the LCMAPS VOMS plugin to the nightlies, replacing the gridmap auth we were testing before. Other things to note:

The suite still tests edg-mkgridmapand glexec individually.
Force GSI auth in HTCondor-CE to ensure that the LCMAPS auth gets exercised. Before it would just fallback to FS auth.
I'm not sure if XRootd + LCMAPS auth gets exercised (my guess is it doesn't) but added the env variables anyway

Test results here:
http://vdt.cs.wisc.edu/tests/20170611-1818/results.html
http://vdt.cs.wisc.edu/tests/20170612-0909/results.html


Issue with update titles

Hi! Thanks for nice library. Please look in my example and take me information about this way for update titles - maybe am i doing something wrong?
I want update titles, but after reload with 'reloadData()' i have got old and new cells.
UpdateTitles.zip

That definitely looks like a bug 😕 It seems to be an issue with reloading data when you are not updating the view controllers as well. If you try to create some new view controllers and update self.tabControllers before reloading it works just fine.
I will get that fixed as soon as possible!

thanks for answer. waiting for fix

i have it as well, waiting for fix, i hope you have time to make it asap

This should be fixed in #201 now! @NBibikov can you target the master branch and double check that it's working for you as well?

Closing this as it seems to be working fine now. Please re-open if you're still seeing any issues!


Include a version in python mleap module

For governance purposes and following https://www.python.org/dev/peps/pep-0396/
can you include a version for your module? It would make things much easier to track, thanks!

We have this here https://github.com/combust/mleap/blob/master/python/mleap/version.py, does this need updating or something?

@ancasarb Sorry for the late reply. This is why I've brought up the issue.

I see the version in the code, but something about its format isn't correct as I cannot access it.

Yeah, at the moment, it seems you need to do
from mleap.version import __version__ as mleap_version
print(mleap_version)

I'll see if we can improve this.

Merged PR to master, will include in next release. Closing this.


Load/store options builder

Description

Use the builder patttern for load/store options.

Instead of public struct fields + Default.
Options { foo: true, ..Default::default }

This also makes the API more consistent with the ones where we use the C API of builder pattern directly from Rust.

e.g. OperationPrintingFlags

References

The use of builder patterns in std.

https://doc.rust-lang.org/std/thread/struct.Builder.html
https://doc.rust-lang.org/std/fs/struct.OpenOptions.html

@edg-l FYI


Fix $generateJSONFromSelectedNodes with a custom selection passed in

Fixes #3745
Previously, passing in a Selection into $generateJSONFromSelectedNodes would result in the wrong JSON because the the main selection from $getSelection() was being used instead. We should be using the target selection that was passed in instead of the main editor selection.

@acywatson Friendly bump — is there anything else I need to do to merge this PR?


element.forEach is not a function

When upgrade TypeScript to 2.2.0 I get the following error.
bash-3.2$ ts-node utility/extractStrings.ts
TypeError: element.forEach is not a function
    at find (/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/typescript-react-intl/index.ts:48:25)
    at findFirstJsxOpeningLikeElementWithName (/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/typescript-react-intl/index.ts:38:5)
    at main (/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/typescript-react-intl/index.ts:84:14)
    at /Users/mdentremont/Projects/REACT/ApolloX.Builder/utility/extractStrings.ts:29:25
    at Array.forEach (native)
    at /Users/mdentremont/Projects/REACT/ApolloX.Builder/utility/extractStrings.ts:27:15
    at f (/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/once/once.js:25:25)
    at Glob.<anonymous> (/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/glob/glob.js:151:7)
    at emitOne (events.js:96:13)
    at Glob.emit (events.js:188:7)

When I attempted to debug the problem. I get the following error when yarn start
bash-3.2$ yarn start
yarn start v0.19.1
$ tsc
index.ts(63,34): error TS2339: Property 'text' does not exist on type 'PrimaryExpression'.
error Command failed with exit code 2.

@cramhead Could you show me the code ts-node utility/extractStrings.ts or provide a repro repo would be fine.

Sure.

import * as fs from 'fs';
/* Role: Utility function that extract ids and defaultMessages from FormattedMessages and defineMessages into i18n/en.tsx */
import * as glob from 'glob';
// tslint:disable-next-line:no-var-requires
const parser = require('typescript-react-intl').default;

interface ParsedString { id: string; defaultMessage: string; };
type ParsedStrings = [ParsedString];

// Visits all files as defined by the pattern. When complete calls the back with results.
function visit(pattern, callback: (parsedStrings) => void) {
    let results: ParsedString[] = [];

    pattern = pattern || 'src/**/*.@(tsx|ts)'; // defaults to searching through tsx and ts files
    // visit all files defined by the pattern and extract the internationalized strings

    // tslint:disable-next-line:only-arrow-functions
    glob(pattern, function (err, files) {
        if (err) {
            throw err;
        }

        files.forEach(f => {
            const contents = fs.readFileSync(f).toString();
            const res = parser(contents);
            results = results.concat(res);
        });

        // tslint:disable-next-line:no-unused-expression
        callback && callback(results);
    });
}

// tslint:disable-next-line:only-arrow-functions
visit(null, function (res: ParsedStrings) {
    const locale = {};
    const indentation = 4; // indent the output file by 4
    const comment = '/* Role: Main source localization extracted from the codebase */\n/* tslint:disable */\n'; // Put a comment at the top of the file

    res.forEach(r => {
        locale[r.id] = r.defaultMessage;
    });

    // save file to disk。you can save as a json file,just change the ext and contents as you want.
    fs.writeFileSync(`src/i18n/en.tsx`, `${comment} export default ${JSON.stringify(locale, null, indentation)};\r`);
});

Could you try it again,Thanks .

Sure.
The new error is:
TypeError: element.forEach is not a function
at find
(/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/typescript-react-intl/index.ts:48:25)
at findFirstJsxOpeningLikeElementWithName
(/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/typescript-react-intl/index.ts:38:5)
at main
(/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/typescript-react-intl/index.ts:85:14)
at
/Users/mdentremont/Projects/REACT/ApolloX.Builder/utility/extractStrings.ts:30:25
at Array.forEach (native)
at
/Users/mdentremont/Projects/REACT/ApolloX.Builder/utility/extractStrings.ts:28:15
at f
(/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/once/once.js:25:25)
at Glob.
(/Users/mdentremont/Projects/REACT/ApolloX.Builder/node_modules/glob/glob.js:151:7)
at emitOne (events.js:96:13)
at Glob.emit (events.js:188:7)
On Mon, Feb 13, 2017 at 6:52 PM, 邦<EMAIL_ADDRESS>wrote:

Could you try it again,Thanks .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bang88/typescript-react-intl/issues/4#issuecomment-279592747,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXj88fT8uOVrFme7z-ava105YZ3YnQhks5rcRb8gaJpZM4L8i56
.


Docker compose

Any chance to add a docker compose file for whole stack? Thanks

I personally wasn't planning on it right now. But, feel free to put in a PR if you get something going.

I agree. I would love this in docker.

There was an example here: https://github.com/konstk1/helium-dashboard/pull/9
My current production config (using my fork) looks like this:
  helium-poller:
    build:
      context: ./helium-dashboard
      labels:
        - autoheal=false
    image: helium-dashboard:latest
    depends_on:
      - influxdb
    environment:
      INFLUX_HOST: ${MONITORING_HOST}
      INFLUX_PORT: 8086
      INFLUX_BUCKET: helium
      INFLUX_ORG: kntinternet
      INFLUX_TOKEN: ${INFLUX_WRITE_TOKEN}
      HELIUM_WALLET: ${HELIUM_WALLET}
      HELIUM_HOTSPOT: ${HELIUM_HOTSPOT}
      HELIUM_ACTIVITY_LOOKBACK_HOURS: 8
      #DEBUG_TO_CONSOLE: 1
      TZ: Europe/Berlin


Fix unigene URI pattern for organism+clusterId

http://ops2.few.vu.nl/QueryExpander/dataSource/U
says:
primary UriPattern
    http://www.ncbi.nlm.nih.gov/UniGene/clust.cgi?UGID=1548618&SEARCH=$id
URI Pattern
    http://purl.uniprot.org/unigene/$id
idExample
    Hs.553708

but this URL only works for the example id, as http://www.ncbi.nlm.nih.gov/UniGene/clust.cgi?UGID=1548618&SEARCH=whatever will still show UGID:1548618 and just put whatever into the search box.
http://www.ncbi.nlm.nih.gov/UniGene/clust.cgi?ORG=Hs&CID=656875 does work correctly - but is not possible to use in BridgeDb as we don't support split identifiers.
The pattern http://purl.uniprot.org/unigene/Hs.553708 is valid and used internally by Uniprot, but does not resolve to anything meaningful ("Can't handle namespace: unigene").
Note that confusingly there is also the "Unigene number" - http://ops2.few.vu.nl/QueryExpander/dataSource/unigene which uses UGID - e.g. http://www.ncbi.nlm.nih.gov/UniGene/clust.cgi?UGID=$id

A few notes:

The OPS BridgeDb policy has been to support all known URI patterns regardless if the currently resolve or not.  After all they may be used in data and by users.

The "primary" UriPattern was picked by the following rules
a. Use the one already used by BridgeDb
b. Pick the one suggested by OPS

Split  identifiers is something not yet faced by the IMS.
If would probably have to be handled in the same way that xref prefixes are handled.
Ie by a layer on top of standard BridgeDb

See:
https://github.com/bridgedb/BridgeDb/blob/OpenPHACTS/master/org.bridgedb.rdf/src/org/bridgedb/rdf/pairs/RdfBasedCodeMapper.java
Changing IdSysCodePair  to handle the split/
Then change:
https://github.com/bridgedb/BridgeDb/blob/OpenPHACTS/master/org.bridgedb.uri.sql/src/org/bridgedb/sql/SQLUriMapper.java methods
toUris(IdSysCodePair ref)
toIdSysCodePair(String uri)
And any underlying database ect!

Thanks for the pointers, @Christian-B! I think adding support for split identifiers is a bit overkill (unless we know of other such cases), and rather we can keep just http://purl.uniprot.org/unigene as the primary - which is what is needed to match the Uniprot linksets anyway.
I seriously don't hope the old format of http://www.ncbi.nlm.nih.gov/UniGene/clust.cgi?UGID=1548618&SEARCH=$id is used anywhere - as it would always return that Olfactory receptor.
I must admit I don't understand why Unigene has two sets of their own identifiers at all - the clusterId is not even consistent across organisms, so it's not like I can check at the mouse by changing to ORG=Mm.
See also http://www.ncbi.nlm.nih.gov/UniGene/help.cgi?item=FAQ#q12 - sadly the split clust.cgi format is the official link format here.
We can always request Uniprot if they could consider a redirect to UniGene's clust.cgi rather than the current 400 Bad Request after redirecting to http://www.uniprot.org/?query=purl:unigene/Hs.553708.

I have asked Uniprot if they would consider redirect.
I have asked Unigene if they could add a ?ORGCID=Hs.12337 form.

Just a note:
See below for feedback from NCBI - suggesting to traverse their API (they don't have any linksets) to get the mapping between UGID and Species/Cluster.
A quick check showed ~ 130.000 records (e.g. about 66 API calls) for generating the linkset for Human.
We don't currently have a link between the Unigene and Unigene Number dataset - but I think that's not really needed as the Unigene Number (sadly?) is not so commonly used as the split Unigene "id"?
It might be needed in inverse though, if we want to include good outgoing links to Unigene, which I guess is valuable. I will let the domain experts within Open PHACTS chip in on this in a separate entry.
Theoretically - Without adding support for the split identifier we would then either create that linkset directly to the uniprot style URIs, or also have a second linkset from the ?split&format to the uniprot links..

The work around is to parse out the mapping information (cluster accession to uid, for only the active entries) from summary.
For example, you can get the uid for a specific cluster by esearch:
http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=unigene&term=Hs.2
The summary provides the mapping:
http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esummary.fcgi?db=unigene&id=130645,310646
For all human records, you may want to do the following:

esearch:
http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=unigene&term=human[orgn]&usehistory=y&retmax=0
summary in batch of 2000:
http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esummary.fcgi?db=unigene&WebEnv=NCID_1_299790388_<IP_ADDRESS>_9001_1438361135_65762357_0MetA0_S_MegaStore_F_1&query_key=1&retstart=0&retmax=2000
loop through the set increment the retstart value by 2000. Second iteration would be:
http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esummary.fcgi?db=unigene&WebEnv=NCID_1_299790388_<IP_ADDRESS>_9001_1438361135_65762357_0MetA0_S_MegaStore_F_1&query_key=1&retstart=2000&retmax=2000
do so until Count from the first search step is reached
parse the output to get the  and  value

If you are doing this from linux, you can install edirect package and do the whole task from a set of chained command (replaced the query with "human[orgn]":
esearch -db unigene -query "human[orgn]" |esummary |xtract -pattern DocumentSummary -element Id -sep "\t" -element CLUSTERID -sep "\n" >hs_ug_mapping_table
More information on eutils and edirect are at:
http://www.ncbi.nlm.nih.gov/books/nbk25501
A webinar is listed here:
https://www.youtube.com/user/NCBINLM

The search pattern
http://www.ncbi.nlm.nih.gov/unigene?term=Hs.725124 also kind of works - but ?term=$id  was already used by the Unigene number entry:
http://ops2.few.vu.nl/QueryExpander/dataSource/unigene
I will swap around so the ?UGID is primary.
Would it work to have two sources both with ?term= ? but non-overlapping regexes, as they have now ?
Then that could be a secondary pattern for the Unigene and remain for backward compat on Unigene Number.

Please be aware that the choice of primary URI was first based on backward compatibility to previous BridgeDb DataSource definitions, This could of course be broken if the current project people feel that is the best.

As for the same URI with non overlapping regex patterns this is handled well by the OPS branches of BridgeDb.
See:
https://github.com/bridgedb/BridgeDb/blob/OpenPHACTS/master/org.bridgedb.uri.sql/src/org/bridgedb/sql/SQLUriMapper.java
public IdSysCodePair toIdSysCodePair
And methods called from that.
There is even some support for the same uri pattern and overlapping or even the same regex pattern
This would also be the place to add new rules if required.


OS commands are seen as unresolved dependencies.

knip version: 1.6.1
A little funny thing about running knip after using npm init -y is that it sees the generated script
"scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
}

as unresolved dependencies:
Unlisted or unresolved dependencies (2)
echo  package.json
exit  package.json

I have little idea about operating systems, but I think it will react the same way with other OS commands.

Yeah, this should be documented better.
The problem here is that Knip does not know what is an npm package and what is an OS binary. While for echo and exit this may sound obvious, it's hard to draw a line here. Currently only these binaries are ignored: https://github.com/webpro/knip/blob/main/src/constants.ts#L20
Perhaps I should just add exit and echo to the list, since these packages are 9 and 12 years old, respectively.
For now you could add ignoreBinaries: ["echo", "exit"] to the Knip config.

I think it would be useful to add the most commonly used Linux, CMD and PowerShell commands as I think these are very commonly included in scripts across plattforms. And to point out on the README if they are OS commands.
Links:
https://kinsta.com/blog/linux-commands/
https://www.digitalcitizen.life/best-cmd-commands/
https://www.educba.com/powershell-commands/
It's not the end of the world, but it's important to have heard of it.

Thanks for your input! I've added a few binaries to the ignore list (1.7.0) and a small section in the readme.

I am going to close this, as it now covers these os commands.
Thank you for your blazingly fast response and keep up the good work!


Better errors

Hi! This PR fixes #265. It doesn't fully handle all the errors in the list yet, but I thought it would be nice to create a draft PR already to get some opinions on the current work. Let me know any thoughts!

I'm in favor of a merge.


VirtualBox error - UID not running as root

Potential FIx:
In terminal run the following:
for bin in VirtualBox VirtualBoxVM VBoxNetAdpCtl VBoxNetDHCP VBoxNetNAT VBoxHeadless; do
    sudo chmod u+s "/Applications/VirtualBox.app/Contents/MacOS/${bin}"
done

This is a bug with Virtualbox. Leaving this here to document. Will close.


Effect refactor fixes

various fixes, i.e. size modifires, area effect radius, weapon post to chat, unofficial grimoire
compatibilty with Terrain Mapper module (added check for type == 'base')
minor formatting
additional rules implemented for endround checks (Poisoned, Stunned, Broken).

There will probably be some conflicts with some of my uncommitted changes, and if you can remove some of the code formatting that would be helpful

In this case, i guess it will be easier if you would just check if there are any bugs you haven't spot and just abondon the PR. In future i would create other PRs with dedicated changes.


Make token-tracking work more like a receipt

This is related to https://github.com/tarasglek/chatcraft.org/issues/59 should make token-tracking function more like a receipt that tells you how much it cost to generate the message near the model details.
This will be more useful once we add claude.
Furthermore current token-tracking is misleading:

it's undercounting as it simplify reflects cost if all currently visible messages were produced by gpt. Instead it should be updated every time we get a response back and stored in local storage.
It's overcounting gpt-4 price by not differentiating different input/output costs

Found this code to track token usage. This is also the key to tracing langchain agents. https://github.com/hwchase17/langchainjs/issues/1079#issuecomment-1532315417

Started to look into this, but ran into https://github.com/hwchase17/langchainjs/issues/1682


Add a GitHub action that will automate closing duplicate issues

Make a GitHub Action that allows us to leave a comment that will automatically add a duplicate issue comment and close the issue.  The comment we leave could look like Duplicate of #1234.  Then, the workflow would leave the following comment and close the issue:
Hey <user>. this looks like a duplicate of <issue>, would you mind upvoting (👍) the linked issue?  We will close this one out as a duplicate.  Thank you.

Cancelling this - instead, I added a saved reply:
Hey <user>,

This issue appears to be a duplicate of:

- <issue_url>

Would you mind upvoting the linked issue with a thumbs up (👍) so that we can keep all the votes in one place? I'll close this one out as a duplicate. If this is a mistake, please reopen this issue with a comment explaining the difference.


Fixed componentWillReceiveProps warning

Fixed componentWillReceiveProps warning
Issue #355

Coverage remained the same at 97.368% when pulling d722086c6c6f96b17338f48a7b209e47161a751d on alexnaiman:fix_for_react_warning into 2a209bd4f11a84ff4543fbde930fed60dcbc0f68 on xgfe:master.

Please merge this, want to get rid of the warning message.

+1 to merge this PR

@feyy
Is it possible to make a new release including this merge request? Package hasn't received any release since April 2018 while there are a lot of open merge requests with good code.

@feyy

If you don't have the time to maintain the library, please try to find someone who does.
I really agree with you and I will be really grateful if I can do that or at least be a part of that

This looks like a dead project without maintainer :( I think it is time to either:

look for an alternative, e.g. https://github.com/react-native-community/react-native-datetimepicker
fork this repo and publish it under new name in npm registry

@mieszko4 at our company we went to the react-native-community version as well. Way better maintained.

This looks like a dead project without maintainer :( I think it is time to either:

look for an alternative, e.g. https://github.com/react-native-community/react-native-datetimepicker
fork this repo and publish it under new name in npm registry

did you do it? If yes, then please share the new npm-package.

This looks like it might be a good and maintained alternative, that solves the same issue as this project originally did: wrapping the core ios and android datepicker components from react native in a nice crossplatform api:
https://github.com/mmazzarolo/react-native-modal-datetime-picker
It is wrapping the extracted versions in https://github.com/react-native-community/datetimepicker/issues rather than the deprecated ones that ship with react native core that this library does.

I made this package https://www.npmjs.com/package/react-native-datepicker-yaya only to solve the warning of the componentWillReceiveProps. Everyone is welcomed to use it instead of this package.

PLEASE MERGE!

I tried https://github.com/mmazzarolo/react-native-modal-datetime-picker, and It has some fundamental issues:

you can't use 24H format in iOS
to set a simple time you need to set the full format of "yyyy-MM-dd HH:mm:ss" as a value. (doesn't make sense)

So, this alternative won't work for everyone.
This react-native-datepicker that we are using, also have another issue:
Warning: DatePickerIOS has been merged with DatePickerAndroid and will be removed in a future release.
Someone with enough knowledge needs to fork this and fix these issues.


Associations upload memory leak?

During a large pipeline run (https://dev.pipeline.vast-survey.org/piperuns/70) I managed to crash vast-data at the association upload step (https://github.com/askap-vast/vast-pipeline/blob/159816940e7afe745bbd4d39e9c808ca8e8f727e/vast_pipeline/pipeline/loading.py#L223)
2024-02-16 16:44:52,155 finalise DEBUG related_df memory after upload: 17.64984MB
2024-02-16 16:44:52,156 finalise DEBUG Current memory usage: 15.524GB
2024-02-16 16:45:06,674 finalise DEBUG sources_df memory after srcs_df merge: 11053.352438MB
2024-02-16 16:45:06,674 finalise DEBUG Current memory usage: 21.095GB
2024-02-16 16:45:06,674 loading INFO Upload associations...
2024-02-16 16:45:09,239 loading DEBUG associations_df memory usage: 11053.352438MB
2024-02-16 16:45:09,240 loading DEBUG Current memory usage: 21.099GB
2024-02-16 16:45:09,240 model_generator DEBUG Building 20815521 association generators

Grafana memory usage for the run is here - things go pear shaped almost immediately.

Possible solutions here?
<EMAIL_ADDRESS>


[Bug] Potential memory leaks?

Dev machine crashed due to potential memory leak. Need to investigate ways to profile code for leaks.

same issue as: https://github.com/dibbs-vdc/ccql/issues/8

Notes from Chuck:
2017-10-4
I think we may have a memory leak.
Here’s what free says:
              total        used        free      shared  buff/cache   available
Mem:        8045240     3775368      142124       99436     4127748     3887840
Swap:       4194300           0     4194300

Plenty of space, you’d think. When the oom killler runs, it puts a “ps” into /var/log/messages. The process it killed was a ruby process, with size 1430950. There’s a factor of 4 difference between that and what shows on “ps aux.” Currently there are no ruby processes with anywhere near that memory usage. The largest is puma (which I believe shows as ruby in /var/log/messages). But remember the factor of 4 difference. The listing in messages is much larger.
I’m going to start a background job that does ps aux to a file, to see if we can see something growing. If we have a multi-GB memory leak, no expansion of memory or swap will prevent problems. As a workaround, we could restart whatever it is nightly.

Some potential tools to try:
http://edgeguides.rubyonrails.org/debugging_rails_applications.html#debugging-memory-leaks


fixed p3 3.2 and added the notebook to submenu

This branch has conflicts that must be resolved
Use the web editor or the  to resolve conflicts.
Conflicting files
_notebooks/CSP/big-ideas/big-idea-3-part-1-fundamentals/Period2/2024-9-22-big-idea-3-2.ipynb


update README.md and CONFIGURATION.md

described the list of metrics exposed with labels and updated the configuration file description

This change is

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

You can have a look on help message in code, and make sure they are consistent with the description you give in the README

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


retraining diffpack

Hi, I am very interested in Diffpack and hoping to know if there is any script that I can retrain Diffpack with?

Hi @linbc-73, thanks for pointing this out. We're working on reformating and updating the training code, and we expect to have this update ready within the next month.

Hi, I am also interested in DiffPack and wonder when would you release the training code. Thank you for your hard work.

+1

Hi, sorry for the delay! I've written a demo training code and put it in the branch (https://github.com/DeepGraphLearning/DiffPack/tree/training). You can use this for reference. The official version will be released soon.

Hi
I still have several questions about training DiffPack. After training 400 epochs using the script you provided in the training branch with the same configuration, I got unexpected chi4(chi3 as in the codes) deg results on the validation set. The chi4(chi3 as in the codes) deg was around 90 through the whole time while the deg for other chi id decreased. Then I  printed the loss for each chi id during training and found the loss for chi4(chi3 as in the codes) fail to converge.

There could be several reasons that lead to the problem and I am hoping you could help me get some clues about that.

The data I used for training could have some mistake, I collected the protein data from bc40 by myself and changed the codes for data loading. Is it possible that you could share the .pkl format data that you used with me? So that I can make sure there is nothing wrong with my data.
I changed a few places in the training branch. Except the data loading process, I changed line 181-182 of generate() of class TorsionDiffusion in /diffpack/task.py as the dimension of pred_score had been incorrect. And I wonder if there are other little mistakes in the codes that could cause upper-mentioned problems.
During debugging, I also checked using teacher-forcing during inference, which means I set the atoms of chi1-chi-i in ground-truth positions when generating chi-(i+1). And I found the deg of all 4 chi dihedral to be almost zero. So I guess the problem could also resulted from the inconsistency between training and testing because of teacher-forcing training. But it doesn't explain why the diffusion loss of chi-3 didn't converge.
And I noticed there is a comment mark says rotamer.set_chis() might have bugs in line 108 task.py, and I used this function when I used teacher-forcing in inference.
Thanks for your help in advance!


wip: Bump k8s.io/* to 1.15.3 🚀

Changes
Bump to latest k8s. Initially I wanted to bump to 1.14, but knative.dev/pkg depends on 1.15.3 and it's kinda a dependency hell to figure out…
Depends on #1412, so marked as WIP for now. Also I think it is going to be red at the first run :sweat_smile:
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Bump k8s.io/* dependencies to 1.15.3

/close
I'll re-work on that a little bit later (next week or so)