Request: User selectable button colors

With the default (black) color and dark theme buttons are almost invisible. I modified deco-theme.cpp line 210 to draw the the lines in white and looks great for now, almost matching my GTK Adwaita-Dark. It would be awesome for users to be able to assign the color in wayfire.ini (other useful options: width of a stroke and space between icons).

Here's a WIP patch. If it works, we might be able to consider some variant of it. The main thing that could use attention is the line width of the minimize and maximize buttons don't always match the close button, apparently because close uses diagonal lines while the others use straight ones.

This patch adds the three options you requested. Apply it with curl https://termbin.com/d9lf | git apply from the pixdecor source directory.

Oh man that was quick! I just tried to apply that patch, but I'm getting an error (see screenshot). I deleted and cloned the git again and tried on a fresh one with the same result...

This is because I made the patch against the track-wlroots-0.18 branch. You would have to apply it manually for the master branch.

Got it. Compiled just fine and works very well! Thank you. Btw I see what you mean with the width of the close button, small detail, I can live with that.

I've found an issue with that patch, and it's not visual but in performance. There's a significant lag and "choppiness " while resizing windows.  The master branch build is perfectly smooth when resizing windows.

Thanks for the report. I think it's due to the added resize() call which is a bit of a hack to get the buttons to refresh immediately when options are changed.

I've found an issue with that patch, and it's not visual but in performance. There's a significant lag and "choppiness " while resizing windows. The master branch build is perfectly smooth when resizing windows.

This version should fix that particular issue.
This wayfire pull request might interest you as well.

Can confirm the latest patch fixed that resizing lag. It is as smooth as the master branch. Thanks again!

Maybe the disconnect between the button line widths isn't such a sin, I'll consider adding the patch. I almost think we should render the buttons with GL directly instead of cairo, but this would require further developments.

Is this patch available somewhere still? I don't see it anywhere in the repo, and the termbin links no longer exist.

Is this patch available somewhere still? I don't see it anywhere in the repo, and the termbin links no longer exist.

Hi, I have updated the temporary link. For what it's worth, pixdecor patches are being held up by the fact that wayfire track-wlroots branch is still not merged. Please ping @ammen99 for more information.

Thanks. Side question for @soreau or @ammen99, if I were to contribute code to the repo at this point, should I base it on the wlroots 0.18 or master branch, or just wait? I've added title font customization, addressing #13, and also made the title respect the text-scaling-factor gsetting.

Thanks. Side question for @soreau or @ammen99, if I were to contribute code to the repo at this point, should I base it on the wlroots 0.18 or master branch, or just wait? I've added title font customization, addressing #13, and also made the title respect the text-scaling-factor gsetting.

You can submit a PR at any time to the master branch, but I'm not pushing anything to the master branch until track-wlroots-0.18 is merged, which depends on wayfire track-wlroots branch being merged. I don't want to push anything to track-wlroots-0.18 pixdecor branch that is unrelated to tracking wlroots. So there's a chance you might have to rebase the PR in the future. The other option is to wait, as you said. This might make more sense.

Well here's a patch containing my changes for now. Been using it all day and haven't ran into any issues, except for:
- Dynamic changing of the font size being a bit sloppy, requiring interacting with a window for the change to properly apply.
- The titlebar rendering weird if you make the font size very small or very large, but I'm pretty sure that issue existed already.
No idea where to begin with addressing those, and they're too minor for me to consider looking into them immediately.

The dynamic changing is probably related to an optimization, where the title is only updated when key properties are changed. See i.e. https://github.com/soreau/pixdecor/blob/master/src/deco-subsurface.cpp#L66-L70
I'm not sure about the 'weird' titlebar rendering if font size is small or large, though I haven't tested your changes nor looked into them in any depth.
Another thing is, pixdecor prefers wayfire settings that gsettings but for this particular case, I think it might make sense, because the setting is presumably integrated with gtk.
And since you have the patch, please go ahead and make a PR against master so we don't forget about it. 👍


Support for Kotlin Multiplatform

Hi there, this is my first time contributing to this project, but I hope I can add some value 👋
Introduction
Here at The Guardian we have a tool called Ophan to which we send analytics data using Thrift. I've recently been working on a research-heavy project where I've been trying to write a cross-platform client library for this tool, Ophan, using Kotlin Multiplatform.
I have been able to do this 👉 multiplatform-ophan 👈 and Thrifty, with some important modifications, was an important part of the solution. I'd like to investigate whether there's a way we can incorporate those modifications back into this repo so that Thrifty can be used in other Kotlin Multiplatform projects.
Requirements
Briefly, Kotlin Multiplatform projects consist of some "common" code which can be compiled for, and run on, any of the supported platforms, as well as platform-specific portions of code which are only used on a single platform. Common code is Kotlin, but with only acces to the "common" parts of Kotlin's standard library and none of the Java standard library (for example there is no java.util.LinkedList) because it must be able to run in non-JVM environments. This obviously limits not only the code you can write yourself, but what your common code can depend upon.
If we consider Thrifty specifically, there are two key requirements for making it usable in this situation:

The Thrifty compiler must output Kotlin code which does not import any classes which are not available in the common Kotlin standard library, and
The Thrifty runtime must abide by the same restrictions.

Proposed solutions
Requirement 1
This is actually really easy to solve with the existing compiler options!
java -jar thrifty-compiler.jar
    --lang kotlin
    --omit-generated-annotations
    --list-type=kotlin.collections.ArrayList
    --set-type=kotlin.collections.LinkedHashSet
    <other options/params>

I've used this successfully in multiplatform-ophan here:
https://github.com/guardian/multiplatform-ophan/blob/master/build.gradle.kts#L86
My only question here is whether it's worth adding a new --lang kotlin-multiplatform option which sets some of those other values automatically?
Requirement 2
This is trickier. Essentially you have to take the existing thrifty-runtime source and modify it to first of all be Kotlin and secondly, use only valid common Kotlin dependencies.
I have done this, here:
https://github.com/guardian/multiplatform-ophan/tree/master/src/commonMain/kotlin/com/microsoft/thrifty
but I have only included the CompactProtocol and I have not created tests for this code. However, I hope this does provide a solid basis for a thrifty-runtime-ktx-multiplatform module in this repo.
Next steps
Really up to you as the project maintainers to decide the best way to proceed. I hope this can be of some use to this project and I look forward to hearing from you.

Oooh, this is interesting!  Thank you for sharing what seems to be a considerable amount of good work.  At first blush, multiplatform seems like a clear win.  I've never used kotlin multiplatform, so I'll need to dig in to the code.
In theory as long as the transports (the only real platform-dependent types we have) are good, then the rest of the protocols should just work as-is.
The only reservation I have is backwards-compatibility - I'd prefer not to break existing Java consumers.  I've been reluctant to push a kotlin dependency on the Java runtime, but given that okio already does, we may as well follow suit.  Given a port to Kotlin, it seems like the only remaining questions are: how to achieve code reuse between
It feels like we could integrate multiplatform and preserve Java consumers by putting your code into the thrifty-runtime-ktx module.  Ideally we wouldn't have to duplicate implementations of tricky things, but given that the protocols are basically stable it wouldn't be the end of the world to have two copies of the runtime.
TL;DR I'd want to see (or see a path leading to) the following before we ship this:

[ ] Backwards-compatibility for Java-based consumers;
[ ] Integration testing (could probably just be another conformance test module for the runtime, but I'm not sure how we'd handle the Android and especially iOS bits.  Note that we're constrained to use Travis CI here, for various reasons)

Despite the wall of text, I want to stress that this is exciting work that I would like to see land in the project - the only questions are "how to", not "should we".


fix(lastfm): Listening report page overhaul

fixes #463
themes new listening report page

Sorry, forgot to ask you to bump the version number, other then that its all good.


Error in browser: process is not defined

When calling `path.resolve("tmp", ".."), this branch is triggered, causing an error in the browser (line 124 in index.js):
if (cwd === undefined)
  cwd = process.cwd();
path = cwd;

Uncaught ReferenceError: process is not defined

I think this error should be caught.

1

安装process
yarn add process -S
vite.config.ts中配置注入process
安装@rollup/plugin-inject
yarn add @rollup/plugin-inject -D

plugins里面加入
import inject from '@rollup/plugin-inject'
inject({
  process: 'process/browser'
})

我的那个 is

When calling `path.resolve("tmp", ".."), this branch is triggered, causing an error in the browser (line 124 in index.js):
if (cwd === undefined)
  cwd = process.cwd();
path = cwd;

Uncaught ReferenceError: process is not defined

I think this error should be caught.

我的那个issue  已经解决了 ， 可以去看看

When calling `path.resolve("tmp", ".."), this branch is triggered, causing an error in the browser (line 124 in index.js):
if (cwd === undefined)
  cwd = process.cwd();
path = cwd;

Uncaught ReferenceError: process is not defined

I think this error should be caught.

我的那个issue  已经解决了，可以去看看
https://github.com/browserify/path-browserify/issues/34

I believe the solution is the following, fixing what has been mentioned above:
pnpm add process path-browserify

import { defineConfig } from "vite"
import inject from "@rollup/plugin-inject"

// https://vitejs.dev/config/
export default defineConfig(async () => ({
  plugins: [
    // `path-browserify` uses global `process`,
    // which we need to replace with a browser module.
    inject({
      include: ["path-browserify"],
      modules: {
        process: "process/browser",
      },
    }),
  ]
}))


Export styles in a way that can be easily consumed in LitElement based views/components

See https://github.com/vaadin/vaadin-lumo-styles/issues/90

Fixed by #102


"Tests" with a capital "T" in README.md

This PR changes "tests" to "Tests" in the README.md.

Hi @Ein-Tim Thanks! Enjoy Sunday evening!

@dsarkar Thanks, you too!


alpha removal seems not work

at the end, log says Could not remove transparency of generated screenhots.. But didn't use skip_alpha_removal.
Why?

What's the complete output?
It should be
Helper.log.info "Could not remove transparency of generated screenhots.".yellow
Helper.log.info "This will cause problems when trying to manually upload them to iTC.".yellow
Helper.log.info "You can install 'imagemagick' using 'brew install imagemagick' to enable this feature.".yellow

Did you install imagemagick?

Got it! Thank you!
But localisation for ja-JP still not working. Could you help take a look?

What do you mean by

it's not working

Doesn't your app run with snapshot on the given language?

On my end, after a couple of tuning, `snapshots works for me, tested English, Deutsch, etc.
But when using ja-JP, the screenshots captured are default language (English). Tested zh-CN also, got same problem as ja-JP.

Updates:
Tested ja-JP and ja in snapfile, snapshot can works for both of them.
zh-CN in snapfile, not work.
zh in snapfile, works.

So what you're saying, I should replace sh-CN with zh in the list of available languages?

The original issue about alpha_removal is fixed. Please create a separate issue for your language problem.


Audios have poor quality when captured for sending on WhatsApp

We are using the send-audio-rec-file plugin, from [flex-project-template](https://www.twilio.com/en-us/blog/introduzindo-the-flex-project-template-developed- by - twilio-professional-services) for sending WhatsApp audio messages. At certain times, some of the operators' audio is randomly of low quality (slow, robotic voice or choppy sound).
The problem can be replicated as follows: while the operator records the audio to send, the customer must send messages.

Thanks for the report @samuelgomesrosa! This appears to be a known issue with the library we are using for the recording; we should be able to improve things with some refactoring. I will look into it!


After last VS Code update, something doesn't works fine

I'm using this extension from 8 months, but I think from last VS code version 1.37.1 my macro doesn't work anymore.
${CLIPBOARD} is not replaced anymore from selected text. In some case all snippet is pasted replacing all document text instead insert it after the newline.
Anyone can help me?
settings.json
`
"macros": {
    "printr": [
        "editor.action.smartSelect.grow",
        "editor.action.clipboardCopyAction",
        "editor.action.insertLineAfter",
        {
         "command": "editor.action.insertSnippet",
            "args": {
                "name": "customprintr",
                "langId": "php",
            }
       },
       "editor.action.insertLineAfter",
       "editor.action.clipboardCopyAction",
    ]
},

`
snippets/php.json
`
 "customprintr": {
	"prefix": "customprintr",
 	"body": [
		"\t",
		"\t    echo '
';",
		"\t    \\$printMe = ${CLIPBOARD}; print_r(\\$printMe);",
		"\t    echo '
';",
		"\t    die;",
		"\t",
		"\t"
 	],
 	"description": "Insert custom print_r"
},
"br": {
	"prefix": "br",
	"body": ["
"]
}

`

@geddski are you supporting this extension?
According with vs code team the problem is that now clipboard is async.

vscode.commands.executeCommand which returns a promise but that extension isn't awaiting those promises, see https://github.com/geddski/macros/blob/master/extension.js#L34. Reading from the clipboard is now async and mostly like a command is started before the previous command is done.

Probably it can be fixed add 'await' param before vscode.commands.executeCommand. https://code.visualstudio.com/api/references/commands

@jeff-hykin has made a fork of this extension:  macro-commander, and it's available in the marketplace.  It appears to handle this problem and has been working for me in the current version of VSCode.

Yeah I had issues with async commands so I added an await to all of them. Although I don't have time at the moment to add more features, I do plan on actively maintaining the extension in terms of bugs and merging pull requests.


Update Status.md

While looking for places to contribute to I noticed the status doc was out of date. I updated only the entries that were clearly incorrect, so there are bound to be more that need updating

@swift-ci please test and merge

Looks like we hit some CI issue while merging. The swift build has gone through.

@swift-ci please test and merge

I'll just force merge this. No need for the test on a markdown change.

👍 thank you!


Standardize Dapps guides for Truffle, Hardhat & Fodunry

Solved some of the issues described in #1059
Same structure for all guides:

Introduction
Recommended Knowledge
Requirements (incl. reference to AvalancheGo and Avalanche Network Runner)
Getting Started

Move all guides to own folder Developer Toolchains
Separate guides for toolchains from general smart contract guides. Separate the README.md in two
Add Foundry to Developer Toolchain Overview
Foundry was missing in the Smart contract Overview README.md

Closing in favor of https://github.com/ava-labs/avalanche-docs/pull/1090. Thank you!


Use more conventional key name in Cargo.toml

It is intended that - is used in multi-word Cargo.toml keys. _ was historically accepted and is not going away, but let's use - just in case :)
See https://github.com/rust-lang/cargo/pull/3771

Thanks!


Allow ComputedPairs processors to pass metadata to destructors

A relatively simple feature request - it may be useful to allow processor functions to pass extra information to destructors to aid in the cleanup of values in ComputedPairs.
For example, adding a second return value (omitted from the output array) would work:
ComputedPairs(myTable, function(key, inValue)
    local outValue = workspace:FindFirstChild(inValue)
    local meta = {
        conn = outValue.Changed:Connect(...)
    }
    return outValue, meta -- only outValue is included in the output array
end, function(outValue, meta) -- but both are passed to the destructor
    meta.conn:Disconnect()
end)

I don't see any reason why this shouldn't be added - seems to be the most elegant solution and shouldn't break anyone's code unless you're doing funky variadic stuff.

There was mention of allowing a Variant to be passed as metadata. Which would look something like:
ComputedPairs(myTable, function(key, inValue)
    local outValue = workspace:FindFirstChild(inValue)
    local conn1 = outValue.Changed:Connect(...)
    local conn2 = outValue.AncestryChanged:Connect(...)
    return outValue, conn1, conn2 -- only outValue is included in the output array
end, function(outValue, conn1, conn2) -- but both are passed to the destructor
    conn1:Disconnect()
    conn2:Disconnect()
end)

I'm personally against this but thought I'd open it to discussion. The reason I'm against this is for future-proofing. If we want to add additional return data, or additional data that gets passed to the destructor, it would result in a breaking change. Also I like how metadata is all put into 1 table, it looks nicer IMO.

Very fair point. I think it's probably best to limit it to one return value, at least for now.


Investigate flaky hello-pepr-alias test

Environment
Device and OS: CI
App version: main
Kubernetes distro being used: k3d
Steps to reproduce

Examine failed workflow tests for hello-pepr-alias

Expected result
Test passes
Actual Result
Test occasionally fails
Visual Proof (screenshots, videos, text, etc)
5 hello-pepr-alias tests have failed on main within the last 200 runs of E2E tests as of 21 Oct 2024.
Severity/Priority
Low
Additional Context
Generate a list of recently-failed E2E tests in CI with this command:
 gh run list --workflow "E2E - Pepr Excellent Examples" --limit 200 --json workflowName,headBranch,conclusion,databaseId --jq '.[] | select(.conclusion == "failure" and .headBranch == "main") | .databaseId' | xargs -I {} gh run view {} --json jobs --jq '.jobs[] | select(.conclusion == "failure") | .name' > ci-failures.log && sort ci-failures.log | uniq -c | sort -r

closed in PEXEX PR


Body Track v1.1.0 frame::get_body() has wrong exception declaration

In body track v1.1.0 the api k4abt::frame::get_body() is declared noexcept. However, that is invalid given the code. That api can throw because it calls get_body_skeleton() which can throw. All below found with MSVC code analyzer -- I recommend you include it in your build pipeline too 😉
Setup

Body Tracking SDK v1.1.0

Repro

Code review Azure-Kinect-Body-Tracking-SDK\sdk\include\k4abt.hpp

Result
Line 205 is invalid:  k4abt_body_t get_body(uint32_t index) const noexcept
because in that function is the call get_body_skeleton(index, body.skeleton);
and that function throws.
Expected
API exception signature to match its actual exception behavior.
Fix
Somewhat trivial and multiple options. I prefer option 1.

Change signature to k4abt_body_t get_body(uint32_t index) const
Surround call to get_body_skeleton() with try/catch

Sidebar
MSVC code analyzer also found 6 lines where your variables can be const since they are declared only one and never changed.
warning C26496: The variable 'xxxxxx' does not change after construction, mark it as const (con.4).

Fixed

@qm13, Fixed in what version? For customers to verify unseeable code changes, we need to know the exact version in which is was potentially fixed so that customers can verify, escalate non-fix, etc.


[release-4.15] OCPBUGS-25355: setting TLSSecurityProfile with no minTLSVersion crashes controller

bump library-go to get the fix in commit dc28c15393c9990e5ba0cd7612892bb88b6653cd

/lgtm

/label backport-risk-assessed

Did pre-merger on AWS-EBS-CSI-Driver-Operator in https://github.com/openshift/csi-operator/pull/90, test result looks good. Other Drivers should have the same behavior.
/label qe-approved
/label cherry-pick-approved


The UI of the read a shlok can be modified ,the New quote button is placed over the shlok lines.

I'm a gssoc'23 contributor , please give me a chance to modify it

some are working on the same


(Fix) 'End date' modifiable after crwodsale was finalized

Closes #617

Pull Request Test Coverage Report for Build 1533

0 of 4 (0.0%) changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.009%) to 8.76%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/manage/index.js
0
4
0.0%

Totals

Change from base Build 1522:
-0.009%

Covered Lines:
254

Relevant Lines:
1963

💛  - Coveralls

@vbaranov I missed that condition, fixed.
BTW, is Ok the description for Distribute Tokens?

Reserved tokens distribution is the last step of the crowdsale before finalization.
You can make it only after the end of the last tier [...]

Shouldn't it state something about minimumGoal too?

@fernandomg
yes, maybe, something like this "You can make it in two cases: after the end of the last tier or if hard cap is reached"?


automatically determine channel when you're currently in a voice channel

it's annoying to have to specify the channel name when you're in a voice channel. it should assume you want the invite to be generated for the channel you're currently in

duplicate of #2


pkg/scheduled_test: mixing unittest and scheduled_test in the same runner causes problems with throws

 Issue by kevmoo
Originally opened as dart-lang/sdk#17090

See attached
Running each test separately works fine.
Running 'test.dart' which includes both results in an error

Attachment:
code.tar.gz (601 Bytes)

 Comment by kevmoo

Could we have warnings/exceptions when:
   1. A unittest test is in a scheduled_test group?
   2. When a scheduled_test test is in a unittest group?
If something is not supported, we should blow up early instead of having
weird behavior

 Comment by nex3

I can make scheduled_test and unittest play together a little more nicely. In order to be completely safe you should run them in separate groups so that scheduled_test's [setUp] functions don't step on unittest's toes, but you should be doing that even when combining pure-unittest libraries anyway.

 Comment by nex3

unittest doesn't know about scheduled_test's existence, and scheduled_test doesn't have any way of telling whether it's in a unittest group -- nor is that actually an issue, really. Besides, the more likely failure case is when both tests are defined at the top-level.

 Comment by nex3

Fixed in dart-lang/sdk@49f5bfa8256a58a155ed5dc6d0bb7dee70f7277e.

Added Fixed label.


[BE] proxy automatically reconnects to Email server in case of a disconnect

I case the Proxy lost the connection to the Email server, reconnect it.
Acceptance criteria

[ ] I case of lost connection proxy reconnects
[ ] tests were conducted, somehow cut connection and connect again.

Definition of done (DoD)

Added only after week 5
The same for all features
Here goes the project specific part

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

The CI Output:


Highlight in char sheet only disappears if sheet is closed

If i open a char sheet on the player and the gm side and highlight a button on the top of it, the highlight isnt disappearing. Only if the player closes the sheet.
Foundry: 9.249
System: Das schwarze Auge/The Dark Eye (5th Edition): v3.2 Beta
Remote-highlight-ui: 1.0.1

I can't reproduce this - works fine for me.

Wait maybe I didn't understand the function correct. The highlight disappeares when the GM clicks somewhere else? Oder when the player clicks?
Maybe a conflict with window controls or an other module. I will dig deeper into this. Thanks for testing 👍

The highlight should disappear when one of the three things happen:

three seconds pass
a new highlight occurs somewhere else (if the player can't see that highlight, it will just stop and nothing new will appear)
the player opens a new foundry window (e.g. an item)

Thanks, then it works as intended, ticket can be closed


shane-hhu-thesis:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

Description: Unofficial Hohai University Undergraduate Thesis (Design) Template.
I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does

[x] added a typst.toml file with all required keys

[x] added a README.md with documentation for my package

[x] have chosen a license and added a LICENSE file or linked one in my README.md

[x] tested my package locally on my system and it worked

[x] excluded PDFs or README images, if any, but not the LICENSE

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Could it be possible to not copy the fonts folder in this repository, and add a link in the README pointing directly to this folder on your GitHub repo? Having it in this repository doesn't make it particularly easier to access, and all these files are quite heavy.
Also, unless you are part of the university staff, could it be possible to change the name of the package to something less canonical please?

Could it be possible to not copy the fonts folder in this repository, and add a link in the README pointing directly to this folder on your GitHub repo? Having it in this repository doesn't make it particularly easier to access, and all these files are quite heavy.
Also, unless you are part of the university staff, could it be possible to change the name of the package to something less canonical please?

sure, thanks!

There is still an error in the template could you please fix it?

There is still an error in the template could you please fix it?

sure, I have fixed it. thank you!

Thanks!


Make services work and trust LE staging certificates, when letsencrypt_environment is set to "staging"

Hi,
I've set cert_manager/letsencrypt_environment to staging for testing purposes. The services are not working, because they don't trust oauth, presenting an LE staging certificate:
[2020/12/15 10:04:26] [oauthproxy.go:798] Error redeeming code during OAuth2 callback: Post "https://my-domain.com/auth/realms/BKPR/protocol/openid-connect/token": x509: certificate signed by unknown authority

Please let the services trust LE staging, when staging is used, for testing.
Thanks,
Floek

Hi,
oauth2-proxy has a setting for allowing insecure ssl validation. --ssl-upstream-insecure-skip-validation. Would this work for your case? Right now, for testing purposes, could you try editing the oauth2-proxy pod an add this argument to it?

Hi,
yes, setting this to true works for me. A least a jsonnet override snippet and some doku would be fine.

Thanks for the feedback! Yes, it would be interesting adding a small section in our documentation to cover this use case. I will forward this information for evaluation.


How to preprocess similar sentences before translation?

広大の海にぽつりと浮かぶ東洋の小さな島国、<voffset=1.0em><size=50%>
『大和<space=-1.75em><voffset=1.0em><size=50%>やまと<space=0.25em>』と呼ばれる国の話――<voffset=1.0em><size=50%>
Remove phonetic notation and parameters
広大の海にぽつりと浮かぶ東洋の小さな島国、『大和』と呼ばれる国の話――

try my server local server with cache system for translation
https://github.com/bbepis/XUnity.AutoTranslator/issues/396
use my local
server for translations (uses google api for translations but processes html tags before translation)
I have a built-in system for ignoring html tags and restoring
and if you tweak a little, you can generally exclude html tags from the translation
if you understand the code, then you will succeed)
Even so, I do not advise you to remove html tags, since in some games icons are transferred to the text in this way or let's make a link to the information window about the subject in question when hovering


Add open api  spec for genome details

Description

Added a schema for genome details payload to support this design

Its typescript equivalent (might be easier to read) is:
type GenomeDetailedInformation = {
  genome_id: string;
  genome_tag: string | null;
  taxonomy_id: string;
  species_taxonomy_id: string; // to be able to retrieve a list of related assemblies
  common_name: string;
  scientific_name: string;
  type: {
    kind: string;
    value: string;
  } | null;
  is_reference: boolean;
  assembly: {
    accession_id: string;
    name: string;
    url: string;
  };
  assembly_provider: {
    name: string;
    url: string | null;
  };
  assembly_level: string;
  assembly_date: string; // ISO date string in YYYY-MM format
  annotation_provider: {
    name: string;
    url: string | null;
  };
  annotation_method: string;
  annotation_version: string | null;
  annotation_date: string; // ISO date string in YYYY-MM format
  image_url: string | null;
  related_genomes_count: number; // 0 if there are none
}

Changed path for another endpoint: /api/metadata/popular_species/{group_id} -> /api/metadata/genomes; because the mechanism to get a list of genomes based on species taxonomy id is generic and not restricted to popular species.

Related Jira ticket
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-2025

@kamaldodiya
There are two endpoints in question here.

One returns detailed information about a genome given its id. It is what this PR is mostly about. The payload is in part similar to what is returned for Compare this XD (genome details) with this XD (a row in the table). I do not know whether you will prefer to store the data for details query in EBI search as well. My assumption was that you won't.
The other endpoint will return a list of genomes associated with a species taxonomy id. This is the one whose path I fixed here (/api/metadata/genomes). The data for this one you probably will want to keep in EBI search. I can create a separate PR in EBI search and move that part of the schema there; but it is not what the bulk of this PR is about.

Also, notice that some parts of the schema of the response for these two endpoints is the same. I don't know whether it will be more appropriate to copy these parts to the search hub repo as well, or to put a reference in that repo to the relevant parts of the schema in this one. It is all very confusing.

@azangru  Yes I was talking about the second endpoint only  /api/metadata/genomes Sorry for the confusion.
Yes,  /api/metadata/genomes  should be moved to ensembl_search_hub.

@kamaldodiya Done. I've submitted a PR to ensembl_search_hub; but there are some things there that will need discussing.


used import alias

The documentation added the import alias do without using it. So made little edit to the underlying golang code.

you're welcome
On Thu, Feb 24, 2022 at 3:03 PM Paul Stack @.***> wrote:

@.**** approved this pull request.
Thanks so much for this!
—
Reply to this email directly, view it on GitHub
https://github.com/pulumi/registry/pull/669#pullrequestreview-892482165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIUKTHFZOIDI2TZIP256NLDU4Y3EHANCNFSM5PHNKLSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


zeebe helm does not work on openshift

Hi i have tried to install zeebe-full on openshift environment but i got following error:
[FATAL tini (6)] exec /usr/local/bin/startup.sh failed: Permission denied
Has somebody tried it already on openshift enviroment?

Hi @milanhorvath that rings some bells.. we are not actively testing on Openshift but it will be great to support it, so we appreciate your report.
It sounds like Openshift needs to you authorize Zeebe containers for privileged use, as there might be some security constraints stopping Zeebe containers to start. I know that Openshift distributions are way more strict than cloud providers, so you might need to relax those configurations or find a way to allow the container to run the startup.sh script.

Hi @salaboy, do you have plans to support OpenShift?

@andrejpetras this is a community project.. but yeah.. totally.. I think that the problem reported by @milanhorvath is just privileged containers that can get working by configuring OpenShift correctly. Just to be clear.. by support I mean that Helm charts run inside OpenShift, did you mean the same?

for reference: https://github.com/zeebe-io/zeebe/issues/3584

@salaboy yes, thank you for your prompt action.

I mean that Helm charts run inside OpenShift, did you mean the same?

Hi @salaboy yes. it would be great if the dockerimage can be updated to be run as non root user as this should then help to run it under openshift environment as it is more restrictive on users and groups

@milanhorvath @andrejpetras Guys, can you please try with this docker image: camunda/zeebe:0.23.1-non-root  in Openshift?
If you can please let me know how it goes.. so we make that image the default one.

@milanhorvath @andrejpetras did you guys managed to give that a try? Also it is kinda important to let us know which version of openshift are you using? or which ones we should support? I think that between 3 and 4 are big differences, and supporting both is double the work.

@salaboy i will try to do the evaluation of the new image today. We are using openshift 4.2.0
Will let you know when i have som new info

@milanhorvath I would love to see which commands are you running and what values file are you using.. if you are using one.. so I can try to reproduce the problem.

@salaboy i was able to deploy the non-root image to openshift and deploy a process there.
i have used these two commands
helm install zeebe-cluster zeebe/zeebe-cluster -n zeebe -f zeebe-cluster.yaml
helm install zeebe-operate zeebe/zeebe-operate -n zeebe -f zeebe-operate.yaml
zeebe-cluster.yaml
i had to change the file extension of the files to txt as otherwise i was not able to append it
zeebe-cluster.txt
zeebe-operate.txt

I have also seen another issue regarding the zeebe-operate helm chart. not sure if i should open another issue or i can write it here. The issue is that the resource part from the values.yaml is not taken as it is hardcoded in the deployment.yaml

@milanhorvath please create the issue for operate in the operate chart repository.
Also.. which ElasticSearch version are you using? are you using the provided one with the charts?
I am looking at your values file, but I still don't know which version of openshift are you using.

@milanhorvath can you please share the logs for the brokers when you install the zeebe-cluster helm chart with those values? so I can understand what is going on.

@salaboy ok i used the standard helm charts from zeebe helm repo (https://helm.zeebe.io) like is written in documentation. i made the test on openshift 4.2. We are now upgrading to openshift to version 4.4.3 so till end of the week i will also try it there.
But now it is working so everything is OK. do you still need the logs?

if it is working in Openshift 4.x we can closet this.. and mention in the docs that Openshift 3.x is not supported.

ok i will close this issue and you will update the docs


"7 GM seed" required

Probably a good idea to specify in the README that if your xcode-install list looks like this:
➜  Dev  xcode-install list
7 GM seed
7.1 beta

The correct install command would be: xcode-install install "7 GM seed" or "7.1 beta" and not xcode-install 7.1 as specified in the current README

Good point, I have added this info to the README.

thank you @neonichu


[replay] generate network visualization replay

The replay filename is otns_<PORT_OFFSET>.replay
The replay output is pure text.
The implementation takes advantage of the gRPC service which has already constructed protobuf message for each visualization event by marshaling event protobuf messsages to strings.
Example replay file content.
timestamp:28536 event:{set_speed:{speed:1}}
timestamp:28568 event:{set_network_info:{commit:"master"}}
timestamp:1894844 event:{add_node:{node_id:1 x:194 y:790 radio_range:160}}
timestamp:1900008 event:{on_ext_addr_change:{node_id:1 ext_addr:9426503932554449306}}
timestamp:1900575 event:{set_node_rloc16:{node_id:1 rloc16:65534}}
timestamp:1908102 event:{set_node_rloc16:{node_id:1 rloc16:65534}}
timestamp:1908244 event:{set_node_role:{node_id:1 role:OT_DEVICE_ROLE_DETACHED}}
timestamp:2353328 event:{send:{src_id:1 dst_id:-1 mv_info:{channel:11 frame_control:55361 seq:188 dst_addr_short:65535}}}
timestamp:2915263 event:{advance_time:{ts:1000000 speed:0.9996850991937539}}
timestamp:3113440 event:{send:{src_id:1 dst_id:-1 mv_info:{channel:11 frame_control:55361 seq:189 dst_addr_short:65535}}}
timestamp:3465867 event:{add_node:{node_id:2 x:242 y:807 radio_range:160}}
timestamp:3473095 event:{on_ext_addr_change:{node_id:2 ext_addr:1021973091034100516}}
timestamp:3473244 event:{set_node_rloc16:{node_id:2 rloc16:65534}}
timestamp:3477150 event:{set_node_rloc16:{node_id:2 rloc16:65534}}
timestamp:3477633 event:{set_node_role:{node_id:2 role:OT_DEVICE_ROLE_DETACHED}}
timestamp:3850769 event:{send:{src_id:2 dst_id:-1 mv_info:{channel:11 frame_control:55361 seq:215 dst_addr_short:65535}}}
timestamp:3923156 event:{advance_time:{ts:2000000 speed:0.9992984924582943}}
timestamp:4372915 event:{set_node_rloc16:{node_id:1 rloc16:14336}}
timestamp:4375407 event:{set_node_role:{node_id:1 role:OT_DEVICE_ROLE_LEADER}}
timestamp:4375495 event:{set_node_partition_id:{node_id:1 partition_id:762265344}}
timestamp:4376564 event:{send:{src_id:1 dst_id:-1 mv_info:{channel:11 frame_control:55361 seq:190 dst_addr_short:65535}}}
timestamp:4614281 event:{send:{src_id:2 dst_id:-1 mv_info:{channel:11 frame_control:55361 seq:216 dst_addr_short:65535}}}
timestamp:4686521 event:{send:{src_id:1 dst_id:2 mv_info:{channel:11 frame_control:56417 seq:191 dst_addr_extended:1021973091034100516}}}
timestamp:4934641 event:{advance_time:{ts:3000000 speed:0.9998680174217003}}
timestamp:5093500 event:{send:{src_id:1 dst_id:-1 mv_info:{channel:11 frame_control:55361 seq:192 dst_addr_short:65535}}}

Other replay utilities (e.g. replay playing) to be implemented.

How could this feature be used?

How could this feature be used?

Good question.
I think the replay file can be used in many ways:

Replays can be played as demos.
Replays (together with PCAP) can be used for debugging network issues.
Replays can be used as an extra log file (since it's of text format)

If you are asking about implementation. The replay files can be played by an OTNS Replay Player (to be developed).
Thoughts? @wgtdkp

@simonlingoogle So this file actually remembers all events in a test and we can reproduce a failure by redo those events, right?

events in a test and we can reproduce a failure by redo those events

Yes, but only visualization related events. For example, you can see nodes become Routers or nodes RLOC16 changes.
It basically exactly the same thing you saw when running the simulation on OTNS.


Test conn establishment & denied peers

This PR refactors the existing muxrpc go tests slightly (cleaning up names & moving util functions to the util file).
Primarily, though, it attempts to verify that banned peers can't successfully establish a connection with the room.

@cryptix i think this is ready for review now! ^_^

yay! :D


vis.py shell subprocess generates file permissions error

Setup:
Linux sgbasestation 5.15.0-89-generic #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:    Ubuntu 22.04 LTS
Release:        22.04
Codename:       jammy
Python 3.10.12
4 cores/4GB VM xen
Problem:
cmdfile save function doesn't work in web interface. cmdfile file permissions access error displayed.
Fix:
vis.py  lines 1126 1128
cmd modified by adding sudo command
cmd = f"sudo -u pilot {sys.path[0]}/{validator[which]} -d {path} -q -i -f {file.name} -u {tU}"

Finally resolved. Problem was in service config file, removed DynamicUser.


Present an ACDC from a multisig AID to a non-issuee recipient

Describe the bug
We created a multisig AID with 3 members and a threshold of 2/3. We were trying to present a LE vLEI credential to the vLEI reporting API (Sally) using the "Present" button in the Issue tab.
However, when one of the members clicked “Present” to Sally’s AID, who is not the issuee of the LE vLEI credential, the other two members did not receive any message in their mailboxes and were not able to join the presentation, i.e., signing the grant message to Sally. As a result, Sally could not receive a grant message with a sufficient number of signatures (2/3).
To Reproduce
Steps to reproduce the behavior:+

Create a mutisig AID with 3 members nad a threshold of 2.3
Issue an ACDC
Present the issued ACDC to an AID that is not the issuee of the ACDC.

Expected behavior
Once an ACDC is presented (i.e. granted) from a multisig AID to another AID, who may or may not be the issuee of the ACDC, /multisig/exn messages should be sent to other members' mailbox so that they could join the presentation by signing the same grant message.

[from twin in jira]
This issue is being tracked in jira at https://eipi.atlassian.net/browse/DF-2548.
To send new comments there, start them with 'Tell jira:'.
The issue is assigned in jira to Arshdeep Singh.
As of 2024-10-16T12:08Z, the status of the issue in jira is 'to do'.
At 2024-10-16T12:08Z, Daniel Hardman said: we are looking at this

[from twin in jira]
As of 2024-10-18T05:43Z, the status of the issue in jira is 'doing'.
At 2024-10-18T05:43Z, Arshdeep Singh said: When we click on the "Present" option, we initiate credential presentation by sending a grant using an exn message to the recipient we select in the popup that opens. The sender of the grant message is the identifier selected in the dropdown just above the table of credentials. If the selected identifier is a multisig identifier, the sender of the grant message is actually the local single-sig member identifier of the multisig identifier. As a result, the other members of the multisig identifier will not receive a notification to join the grant.


Remove prose scope

We don't have confidence that the prose scope is well understood – without further research / better documentation it's safer to remove it for now.
If you are currently using prose-scope, you should revert to applying classes to individual headings, lists and hr elements.
In version 0.0.29-alpha release we have added the option to enable global link and paragraph styles. If you're using a recent version of the Private Beta Prototype kit, this is enabled by default.
Trello ticket: https://trello.com/c/v7tR99UO/955-remove-prose-scope

Looks like there's still a few references to the prose scope in app/__test__/app.test.js and in files in src/core.

good spot. updated

FWIW, I thought this was a really neat feature. There are similar, generic classes in other css frameworks. I thought these were fairly well understood. e.g. bulma.
A single class to handle WYSIWYG generated content, where only HTML tags are available is a common use case .
+1 for it's return!

Thanks for the feedback @davidjamesstone – that's really useful to know. We've not ruled out adding prose scope or at least something very similar back in in the future. It's also good to see examples of how this works in other systems, like in the Bulma documentation you linked to.


Revert "Cryoxadone and doxarubixadone now work on the dead"

About
Reverts space-wizards/space-station-14#23558
Making cyrox and doxa able to heal damage off of dead players has transformed cryo from a niche method of chemical administration into a revival powerhouse. The main issues are thus:

Cryo allows for administering some of the most potent healing chemicals in the game while simultaneously preventing rotting with no limit or restriction. It even applies to cellular damage via doxa, which means you can literally heal a dead body to 0 damage in all groups with no risk or time pressure.
The changes still don't make cryo useful for it's intended purpose, only for the new purpose of healing unrevivable dead bodies. It essentially just serves as a budget cloner with somehow even less material balance than the biomass-based system.
Because of how the supply of chemicals are unlimited, cryox/doxa completely outclass all of the more limited options for repairing damage on dead bodies (ointment, sutures, bruise packs, etc)

None of these changes in the original PR should even be considered until we have a better system for overall chemical balance. Chemicals are precariously balanced on overdoses and relative healing numbers. The fact that none of these factors are relevant for cryo healing dead bodies AND it nullifies all rot mechanics makes this a blatantly overpowered combo.
For a final piece, death is an important part of the game. Being able to kill players and them staying dead is important for antagonist balance as well as round flow. Players should be able to die and choose ghost roles without having to worry about being revived out of the blue 20 minutes later. We already have an abundance of mechanics that halt rotting (body bags, morgues, stasis bed, temperature, etc) as well as decently-balanced physical healing items that can be used to heal bodies reasonably damaged bodies.
Cloning was intentionally removed for a reason: it is not conducive to a system where healing and balancing different options matters. We shouldn't be encouraging a stale meta that is just cloning in a (slightly taller) skin.
Changelog
:cl:

remove: Cryoxadone and Doxarubixadone no longer work on the dead.

Atleast on Salamander I've mostly seen Cryo being used for healing high amounts of damage. You may say "Oh, this is terrible" but the reality is we've been doing that BEFORE this PR was merged by getting like... 20-30 people and all applying Ointments and Bruise Packs to a dead body as if that makes any Roleplay sense whatsoever. Cryogenics being used for this purpose makes far more sense and also takes a very long time and uses up a loooot of Cryoxadone (It's healing is not actually all that powerful... for burn victims it's as good as Derma, and it only heals twice as fast as Bicar for Brute, which is notoriously terrible for Brute).
I would rather see Cryo Chem balance tweaked around this mechanic rather than just removing the mechanic after 1 day, especially when it's been EXTREMELY well-received by the player base. You could make Cryoxadone more resource intensive! Perhaps make it consume the Plasma it uses in the reaction as just one idea to start with, thus making it require a lot of material to mass produce, and a relatively rare one at that compared to steel/plastic/glass spam of topicals which is what we currently do without much issue.
It does not completely outclass limited methods of damage recovery atleast in convenience. Sometimes it is more time-sensible to apply 5 brute packs then pull someone all the way to the Cryo Pod, unsuit them, wait for them to freeze, and then Cryox them to a level they can be revived at. Sometimes it isn't! There are trade-offs and points where both are good.
I'm not really sure what niche Cryo's intended purpose even was before? It really didn't seem like it had any besides for Roleplay purposes.

If we had a larger selection of ghost roles (and a lottery system), people wouldn't try cheating death to begin with
In addition, aside from cryo, halting rot or healing are mutually exclusive - whilst intended, it's infuriating seeing patient rot while being actively healed by topicals without warning indicators.
Reading through your main three points, would post-death chem be okay if both:

Poisons and damaging chems also apply after death
Cryoxadone and Doxarubixadone no longer work on the dead, but a specifically limited and difficult-to-make chem can

What would cryo be used for, if not for healing dead people? Sure you can heal alive people, but people gravitate towards whatever is best/meta so you need a totally new feature to incorporate.

What would cryo be used for, if not for healing dead people? Sure you can heal alive people, but people gravitate towards whatever is best/meta so you need a totally new feature to incorporate.

cryo has been useless since it's inception in SS14. This was a pretty consistent concern. I think that having limited chemical amounts will make people gravitate towards it since it's more potent, but it's not really going to be able to compete with anything in our current system unless you make it work in a whole different manner.

What would cryo be used for, if not for healing dead people? Sure you can heal alive people, but people gravitate towards whatever is best/meta so you need a totally new feature to incorporate.

cryo has been useless since it's inception in SS14. This was a pretty consistent concern. I think that having limited chemical amounts will make people gravitate towards it since it's more potent, but it's not really going to be able to compete with anything in our current system unless you make it work in a whole different manner.

Cyro working on the dead as it currently stands functionally turns cyro into cloning. I'd support removing it's functionality on the dead in general based on that alone.

Cryogenics being used for this purpose makes far more sense and also takes a very long time and uses up a loooot of Cryoxadone

time and chemicals are both functionally infinite in this scenario. The body is at no risk of rotting at any point and the chemicals can be produced infinitely in its current state.

I would rather see Cryo Chem balance tweaked around this mechanic rather than just removing the mechanic after 1 day,

I mean it's not like it's that deep to warrant a deep exploration of it. It's just healing dead bodies with chemicals, something that hasn't been in the game for a long time for reasons that probably look quite similar to this.

it's been EXTREMELY well-received by the player base

this is a meaningless statement. any buff or strong mechanics is going to have people liking it.

Perhaps make it consume the Plasma it uses in the reaction as just one idea to start with, thus making it require a lot of material to mass produce

Plasma is hardly a difficult or hard to acquire resource. We simply do not have the infrastructure to support any kind of resource-based chemistry and, even if we did, putting a material limit on reviving dead bodies is just going to make people hard focus it (like how people forced sci to hard focus cloning when it was in the game). Even if it's a more rare option, it shouldn't really invalidate other existing options completely.

It does not completely outclass limited methods of damage recovery atleast in convenience. Sometimes it is more time-sensible to apply 5 brute packs then pull someone all the way to the Cryo Pod, unsuit them, wait for them to freeze, and then Cryox them to a level they can be revived at. Sometimes it isn't! There are trade-offs and points where both are good.

I agree, but I think this is better suited to future balance where efficiency is more relevant. Nothing in the medical system really makes efficiency a valuable trait, especially regarding dead bodies.

In addition, aside from cryo, halting rot or healing are mutually exclusive - whilst intended, it's infuriating having a patient rot while actively healed by topicals without warning indicators.

Worth noting that stasis beds block rot now, so that should provide better body management gameplay.

Reading through your main three points, would post-death chem be okay if both:

Poisons and damaging chems also apply after death
Cryoxadone and Doxarubixadone no longer work on the dead, but a specifically limited and difficult-to-make with weird mechanics chem can

Maybe? At that point, it might just make sense to have it occur outside of chemicals with some external resource or process. That way, regular MD players can be more involved. Chemical mixing is really not in their repertoire of average activities.

Cyro working on the dead as it currently stands functionally turns cyro into cloning. I'd support removing it's functionality on the dead in general based on that alone.

Except it's not fully cloning. The rot still consumes and you can't revive rotted people with Cryo. This just makes it so there's an RP-sensible way to heal 1000 burn that takes a long time instead of the NoRP way of mass rubbing of ointment for 2 minutes and reviving them. I'd support removing Toxin healing from Cryox though if we want poison to stay unrevivable for whatever reason.

Rip cryo
Stasis beds prevent rot now at least, I had no idea

What are the plans for a better cryo system?

As far as I know there is nothing in store for Cryo besides the hope that removing Chem Dispensers and the overall Chem rework makes people use them more to avoid the resource crunch.

Is this really bad that players can have a chance to play back after dying? At this point, why doctors trying to safe anyone from being ghosted, due of circumstances that can occur?
But i understand it, cause people dont want to spent a lot of time to just use oitments and brush packs on dead people, that might be ssd/rotten long ago.
But that change come from poison-gib damage, that no one likes though, maybe we need corpse poison cleaning someday, just poison.

There isn't any point for medics to place someone in the cryopode and babysit the temperature, health, the beaker

This isn't true at all, currently cryo can make 1 person handle way more patients than they could've handled without.  If you prepare a bit people inside the cryomachine won't be able to die for at least 100 seconds(the beaker gets empty). If you have 2 cryotubes and 4 crit people get dragged in, you can just plop 2 of them in the cryotubes while you heal the other 2 by hand. Whenever I setup cryo the only reason it isn't used is because 5 doctors are eagerly waiting for a patient, and me just treating all the patients wouldn't really be that fun for them.

and me just treating all the patients wouldn't really be that fun for them.
That's basically what I am talking about. I'm sure that cryoxadone is the best medicine in the game, but it's infinitely boring. For medbay, reviving a person under 200 damage is basically no deal: zap, epinephrine, bruizine, derma, done, go to the next patient. This process gameplay-wise just doesn't need some alternatives. Maybe reworks, yes, but definitely not a thing that is "1 press to heal anything".

I believe that functionality of cryo and regular administracion of medicine should be separated, preferrably giving some complexity for cryo as well. They need to work together, not replace one another. Honestly, for the day cryoxadone worked on the dead, I wasn't comfortable about the fact that it works on living. I want some interesting gameplay and RP as a medical worker, not just one-click-cloning, one-click-cure-everything, spend minutes mindlessly applying bruise packs, you get it.

Stasis beds now stop rotting so you should treat dead bodies on one of those.
Didn't know that, fair.

Bruh


use prettier defaults rather than a globally defined indent size/style

follow up of https://github.com/nushell/nana/pull/39
just .editorconfig was modified, everything else is prettier applying default formatting for each supported file type (html, md, json, css...).

Thanks again @knoopx.


Update DCM samples to work with API v3.0

Update the createAdvertiserAndCampaign example to insert an advertiser landing page after creating the advertiser. Campaigns must now reference an existing advertiser landing page on insert.
See: https://developers.google.com/doubleclick-advertisers/rel_notes#known-issues

LGTM!


Maarten/update to django 1 11

This PR updates the code to work with Python 3.5 and Django 1.11

Thanks @mnieber!
I'm going to check it out in detail.

@mammuth Can you merge this?


Configure team settings and organisation owners

This will work with the upcoming release of github-org-manager

Overriding approval chain as this doesn't change anything, just documents the current settings which is possible in github-org-manager >=0.5.0


[In Progress] Modify LightCurve class to allow creation of feature extractor classes

New feature extractor classes can be added using LightCurve base class
Feature extractor class should implement necessary methods. Please check BazinFeatureExtractor or BumpFeatureExtractor for reference
class NewFeatureExtractor(LightCurve):
    def __init__(self):
        super().__init__()

    def evaluate(self):
        """
        Evaluate the Bazin function given parameter values.
        """

    def fit(self):
        """
        Extracts features for one filter.
        """

    def fit_all(self):
        """
        Performs fit for all filters independently and concatenate results.
        """

    def plot_fit(self):
        """
        Plots data with fitted function.
        """

Todo:

[ ] Bump extractor headers are missing
[ ] Verify the implementation with different datasets

I think I more or less understood what is the idea, of separating the LightCurve object from the fitting part, which it seems a good thing to me.
Just a few points:

having files with the same name in different folders is confusing. There are resspect/bazin.py and resspect/feature_extractors/bazin.py  I would name them slightly different

I tried to load the BazinFeatureExtractor but I got

TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_452408/3030310545.py in
1 lc1 = LightCurve()
----> 2 bfe_test = bfe(lc1)
TypeError: init() takes 1 positional argument but 2 were given

I understood that a LightCurve object should be given, but maybe I got that wrong

@emilleishida

I'll rename the files 👍

Bazin and Bump feature extractor classes have been defined can be accessed as below

# bazin
bazin_lc = BazinFeatureExtractor()
bazin_lc.load_snpcc_lc(path_to_feature_file)

#bump
bump_lc = BazinFeatureExtractor()
bump_lc.load_snpcc_lc(path_to_feature_file)

A new feature extractor class can be added as described in the first comment. Let me know if you have further questions

@utthishtastro this is great, thanks!
apologies for taking so long, but I looked at this and it seems to be working fine!
I also tried with plasticc data and it is ok. Do not worry about RESSPECT light curves, that will probably be removed.
when I tried to plot the bump light curve I got an error
`---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_227509/1149545446.py in
----> 1 bump_lc.plot_fit()
/media/emille/git/COIN/RESSPECT_repo/rupesh/rupesh-env/lib/python3.7/site-packages/resspect-0.1-py3.7.egg/resspect/feature_extractors/bump.py in plot_fit(self, save, show, output_file, figscale, extrapolate, time_flux_pred, unit)
155             if plot_fit:
156                 xaxis = np.linspace(min(time), max(time), 500)[:, np.newaxis]
--> 157                 fitted_flux = np.array(self.evaluate(xaxis)[self.filters[i]]) * self.features[i * 5 + 4]
158                 if unit == 'flux':
159                     plt.plot(xaxis, fitted_flux, color='red',
/media/emille/git/COIN/RESSPECT_repo/rupesh/rupesh-env/lib/python3.7/site-packages/resspect-0.1-py3.7.egg/resspect/feature_extractors/bump.py in evaluate(self, time)
42                         bump(item, self.features[0 + k * 5],
43                              self.features[1 + k * 5],
---> 44                              self.features[2 + k * 5]))
45             else:
46                 flux[self.filters[k]].append(None)
TypeError: 'module' object is not callable`

I do need this, so I will merge now and we fix the plot issue latter
I will comment the plot function -- I know this is not correct, but it is necessary

so coming back to this, the error can be reproduced by:

`from resspect.feature_extractors.bump import BumpFeatureExtractor
path_to_feature_file = '/media/RESSPECT/data/SNPCC/raw/SIMGEN_PUBLIC_DES/DES_SN729076.DAT'
bump_lc = BumpFeatureExtractor()
bump_lc.load_snpcc_lc(path_to_feature_file)
bump_lc.fit_all()
bump_lc.plot_fit()`


Invalid E0432 when using Docker build cache layers

Problem
For convenience, a repository reproducing this bug can be found here: https://github.com/jennydaman/rust_in_docker_bug
A common pattern with using Dockerfile and Rust is to leverage layer caching like this:
FROM rust:1.71.0-slim-bullseye

WORKDIR /app
COPY Cargo.lock Cargo.toml ./
RUN mkdir src && touch src/lib.rs  # dummy project
RUN cargo build
COPY src src
RUN cargo build

In past projects, this worked for me if src does not contain a lib.rs. However, I am currently working on a project with both main.rs and lib.rs. Using the Dockerfile pattern above causes cargo to emit an invalid E0432 error.
main.rs
use owo_colors::OwoColorize;
use rust_in_docker_bug::add_one;

fn main() {
    println!("Number is {}", add_one(12344).cyan());
}

lib.rs
pub fn add_one(x: u32) -> u32 {
    x + 1
}

Build
podman build .
STEP 1/7: FROM rust:1.71.0-slim-bullseye
STEP 2/7: WORKDIR /app
--> 958baf24a72b
STEP 3/7: COPY Cargo.lock Cargo.toml ./
--> f038ed695fa8
STEP 4/7: RUN mkdir src && touch src/lib.rs
--> 1fc0beaa5a68
STEP 5/7: RUN cargo build
    Updating crates.io index
 Downloading crates ...
  Downloaded owo-colors v3.5.0
   Compiling owo-colors v3.5.0
   Compiling rust-in-docker-bug v0.1.0 (/app)
    Finished dev [unoptimized + debuginfo] target(s) in 0.58s
--> d9535e0aa0fa
STEP 6/7: COPY src src
--> 8530d262ea49
STEP 7/7: RUN cargo build
   Compiling rust-in-docker-bug v0.1.0 (/app)
error[E0432]: unresolved import `rust_in_docker_bug::add_one`
 --> src/main.rs:2:5
  |
2 | use rust_in_docker_bug::add_one;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `add_one` in the root

warning: unused import: `owo_colors::OwoColorize`
 --> src/main.rs:1:5
  |
1 | use owo_colors::OwoColorize;
  |     ^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

For more information about this error, try `rustc --explain E0432`.
warning: `rust-in-docker-bug` (bin "rust-in-docker-bug") generated 1 warning
error: could not compile `rust-in-docker-bug` (bin "rust-in-docker-bug") due to previous error; 1 warning emitted
Error: building at STEP "RUN cargo build": while running runtime: exit status 101

Same error happens for Podman and Docker, so I assume it's a problem with cargo not buildah nor buildx.
The problem does not happen if not using Dockerfile:
# this works!
docker run --rm -v $PWD:/src:ro rust:1.71.0-slim-bullseye sh -ec '
mkdir /app
cd /app
cp -v /src/Cargo.lock /src/Cargo.toml .
mkdir src && touch src/lib.rs
cargo build
cp -rvf /src/src src
cargo build
'

A workaround is to create the dummy project with a main.rs instead:
FROM rust:1.71.0-slim-bullseye

RUN cargo new --bin /app
WORKDIR /app
COPY Cargo.lock Cargo.toml ./
RUN cargo build
COPY src src
RUN cargo build

Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
No response

Thanks for the report. I believe this is due to docker COPY not preserving mtime, while Cargo's build cache system currently relies on mtime.
As a workaround, touching src/lib.rs works:
  FROM rust:1.71.0-slim-bullseye

  WORKDIR /app
  COPY Cargo.lock Cargo.toml ./
  RUN mkdir src && touch src/lib.rs
  RUN cargo build
  COPY src src
+ RUN touch src/lib.rs
  RUN cargo build

Personally I may recommend some third party plugin at this moment if you have a complex project with docker (cargo-chef specifically). Some prior discussions and tracking issues:

https://github.com/rust-lang/cargo/issues/2644
https://github.com/rust-lang/cargo/issues/7150

I'll close this in favor of the above issues. Let us know if it is wrong to close this.


duplicate and/or invalid ID checks

Another audit I would like to port from aria-toolkit, HOWEVER I wanted to check with the team first.
The primary purpose of this audit is to ensure that IDs are unique in the DOM.
I also had a check for invalid IDs (which in HTML5 simply means no whitespace).
The reason I ask about this one is because it is not strictly speaking an accessibility audit - it is more of an HTML validation task.
I felt the duplicate ID check in particular was essential to ARIA (because of IDREFs) and therefore worthy of being part of accessibility tools.
Should I add ID audits?

Closing this because it's complete.


CloudFront - Alternate domain names

Hi,
If I try to add only a cname or alias on Route53 it will not redirect properly to my CloudFront Domain. If I add an aliases and viewer_certificate info it works fine.
However I was not able to keep this changes in future "terraform applies". I tried changing the tfstate and inserted cloudfront_external_arn and cloudfront_external_id pointing to the created CF in main.tf, but it is always overwrited.
How is it possible to direct my domain to the cloudfront distribution and keep it automated in future deploys?
Thank you,
Rodrigo

Hi,
let me quickly recap the problem, to see if I understand the situation correctly:

You have a domain (example.com) and it's CNAME is pointing to the CloudFront distribution (xyz.cloudfront.net)
You want to redirect incoming requests to example.com to xyz.cloudfront.net
The domain example.com is not added as alias to the CloudFront distribution

From my understanding CloudFront will only accept incoming traffic from external domains when the alias is set correctly.
Without an code example it is very difficult to see why your setup is failing.
We created a custom domain example, that is tested and is working fine with external domains.
Could you tell where your setup is different from the example code?

Hi,
That's exactly it.
After following this example it worked fine. Thank you very much for your help.


Unpin Pytest on master branch

The pytest plugin was "temporarily" pinned many months back. Given that this is not pinned on the stable branch we should be able to remove it here.
There are likely a few other changes required to get the nightly build working, since it appears as though pytest broke during the release of Python 3.8.0a4.

Looks like Coverage is just broken in Python 3.8 and they aren't immediately addressing it: https://github.com/nedbat/coveragepy/commit/e26a9237bae636635440061094cd65ffc40c3cf6

We need to add nightly to the allowed failures. Preferrably, we need to migrate to Azure like Flask did.


Control the animation effect speed?

Is there a way to control the animation effect speed when changing traitlets like in the example below? It appears to take ca. one second now.
import time
import ipyvolume as ipv
import numpy as np

fig = ipv.figure()
x, y, z = np.random.random((3, 100))
s = ipv.scatter(x, y, z, size=5)
ipv.show()

time.sleep(2)
s.x, s.y = s.y, s.x

Yes, try https://ipyvolume.readthedocs.io/en/latest/api.html#ipyvolume.widgets.Figure.animation

Obviously... but thanks, anyway!


Degrade with Ubuntu 22.04 while printing

With latest ubuntu 22.04 jobs are printing with default PageSize as "Letter"
irrespective of the job document size(A3/A4/11x17...)
Ubuntu 20.04:Same job when printed from 20.04 honors document size of the job(A3/A4).
LPR behaviour: Take a PDF document of size(A3/A4/11x17...) and print using "LPR" command. e.g.: lpr -P ~/Desktop/3Pages_A3_Landscape.pdf
OBSERVATIONS: Ubuntu 20.04:The job is printed with size A3. Ubuntu 22.04:The job is printed with size Letter(PPD Default).
Ubuntu 22.04 is using cups version = 2.4.1
Ubuntu 20.04 is using cups version = 2.3.1
is it degrade in Ubuntu 22.04 against 20.04 ?

Hi @chennasudhakar94 ,
thank you for reporting the issue!
It would be great if you enabled the CUPS debug logging, printed the documents and attached /var/log/cups/error_log as a .txt file from both machines here.
IMHO we always honor the PPD default unless the application sends a different choice - we should be able to see this from debug logs.
Additionally please report this to Ubuntu as well.
Thank you in advance!

Hi @zdohnal ,
Thanks and please find the attachments for cups debug logs(/var/log/cups/error_log).for both ubuntu 20.04 and 22.04.
And I created ticket On Ubuntu also below link is the ticket link.
Link: https://askubuntu.com/questions/1414130
If it is not right Link please let me know the URL where I can create the ticket.
Thanks & Regards,
C.Sudhakar
cups_error_log_ubuntu22.04.txt
cups_error_log_ubuntu_20.04.txt

From logs at 22.04:
64 D [21/Jun/2022:16:05:10 +0530] [Job 25] pdftopdf: \"print-scaling\" IPP attribute: auto
 65 D [21/Jun/2022:16:05:10 +0530] [Job 25] pdftopdf: Page 1 too large for output page size, scaling pages to fit.
 66 D [21/Jun/2022:16:05:10 +0530] [Job 25] pdftopdf: Page 2 too large for output page size, scaling pages to fit.
 67 D [21/Jun/2022:16:05:10 +0530] [Job 25] pdftopdf: Page 3 too large for output page size, scaling pages to fit.
 68 D [21/Jun/2022:16:05:10 +0530] [Job 25] pdftopdf: Print scaling mode: Scale to fill page and crop
 69 D [21/Jun/2022:16:05:10 +0530] [Job 25] After Cropping: 1190.640015 841.919983 1089.543507 841.919983
 70 D [21/Jun/2022:16:05:10 +0530] [Job 25] After Cropping: 1190.640015 841.919983 1089.543507 841.919983
 71 D [21/Jun/2022:16:05:10 +0530] [Job 25] After Cropping: 1190.640015 841.919983 1089.543507 841.919983

it looks like pdftopdf from cups-filters scales the pages to the requested page size, which, if not set, is the default from PPD.
IMHO it is a desired behavior unless we have a way how to detect the page size beforehand and turn the logic into use auto-detection unless there is defined page size in options, but I will turn it to cups-filters for review.


Feature/jenkins example

Report generation for Dockerfile tests and Parameter File tests on Jenkins.

Coverage decreased (-14.8%) to 24.928% when pulling 8f68258160d4f7eb229dc6eff333117396e28500 on feature/jenkins_example into 610106971caaf9560fc45688bc2c5bd2017efbed on develop.

Coverage decreased (-16.5%) to 23.229% when pulling 7bf80c1b160382441cc499d97ef26493069fcffc on feature/jenkins_example into 610106971caaf9560fc45688bc2c5bd2017efbed on develop.

Coverage decreased (-39.7%) to 0.0% when pulling 4f5ce5a044e21d10b0d0eaebc6e71f45235d2a1a on feature/jenkins_example into 610106971caaf9560fc45688bc2c5bd2017efbed on develop.

Coverage decreased (-39.7%) to 0.0% when pulling 75574c7837c1c0b8fedb9e26719ad2d6469b860d on feature/jenkins_example into 610106971caaf9560fc45688bc2c5bd2017efbed on develop.


Improve mobile experience

Add disclaimer to the templates page that this page not optimized for mobile.
Use modals to show templates on desktop and mobile

If the user is on mobile, add some text indicating that it the page will look awful on mobile.
The user should be able to use the templates page

Also obfuscate aws key and secret


File size limitation not work on IOS

Hi ,
I met a issue , I set maxFileSize to limit file size, it works when I use Chrome on PC , but it does not work when I use my phone to visit web site, I do not know why , is it a issue ? or could you tell me how to handle this ?
thanks

oh,  I forgot that I also use Chrome on my phone

Hi @YswNG, if you set it via https://github.com/blueimp/jQuery-File-Upload/wiki/Options#maxfilesize option, it should work as expected, including on iOS.
There is even a unit test for it: https://github.com/blueimp/jQuery-File-Upload/blob/ea641dd81c65b21af5f70a0415cfab5e51a97c49/test/unit.js#L927-L944
(side note: Chrome on iOS is just Safari with a different UI)

Closing this for now, please post further information if you can provide a reproducible test case.


flutter 2.8.0-3.2.pre, No top-level getter 'devMain' declared.

[✓] Flutter (Channel beta, 2.8.0-3.2.pre, on Ubuntu 20.04.3 LTS 5.4.0-54-generic, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 4.1)
[✓] Android Studio (version 2020.3)
[✓] Connected device (3 available)

E/flutter (23784): [ERROR:flutter/shell/common/shell.cc(94)] Dart Unhandled Exception: NoSuchMethodError: No top-level getter 'devMain' declared.
E/flutter (23784): Receiver: top-level
E/flutter (23784): Tried calling: devMain, stack trace: #0      NoSuchMethodError._throwNew (dart:core-patch/errors_patch.dart:218)
E/flutter (23784):
E/flutter (23784): [ERROR:flutter/runtime/dart_isolate.cc(718)] Could not resolve main entrypoint function.
E/flutter (23784): [ERROR:flutter/runtime/dart_isolate.cc(202)] Could not run the run main Dart entrypoint.
E/flutter (23784): [ERROR:flutter/runtime/runtime_controller.cc(384)] Could not create root isolate.
E/flutter (23784): [ERROR:flutter/shell/common/shell.cc(574)] Could not launch engine with configuration.
dart code:

@pragma('vm:entry-point')
void devMain() {
  envType = ENV_DEV;
  main();
}

void main() {
  runApp(MyApp());
}

android code:

 val flutterEngine = FlutterEngine(context)
        // Start executing Dart code to pre-warm the FlutterEngine.
        val flutterLoader : FlutterLoader = FlutterInjector.instance().flutterLoader()
        if (!flutterLoader.initialized()) {
            throw AssertionError(
                    "DartEntrypoints can only be created once a FlutterEngine is created.")
        }
        val point = DartExecutor.DartEntrypoint(flutterLoader.findAppBundlePath(), if(isProduct) "main" else "devMain"  )
        flutterEngine.dartExecutor.executeDartEntrypoint(point)
        // Cache the FlutterEngine to be used by FlutterActivity or FlutterFragment.
        FlutterEngineCache
                .getInstance()
                .put(ENGINE_ID, flutterEngine)

In debug mode,code is run well,but run on release mode,it always show this error

Same problem in iOS

@lzhAndroid
There's similar open issue describing your case, https://github.com/flutter/flutter/issues/91841
Please follow-up in it for further updates.
Closing this as a duplicate.


Dbmohit patch 2

just for hactoberfest, sir i made change in it before 1 oct and you merged it , i made just very small change in doc please merge it.

Done

thank you sir


Fix celery worker

to: @mistercrunch
When I said the other PR wasn't tested, I was telling the truth.

Coverage remained the same at 69.315% when pulling 9e90974e58d6ca1a60bd263b599c285b16c06403 on saguziel:aguziel-fix-celery-2 into 08b7e891a7dd65616aef4177b72b1e8770310d98 on apache:master.


have a straight-forward user interface that enables simulation both on a local machine and on hpc

HPC simulation has been implemented for some time in ridepy-extras


feat: add graduation Hat

Fixes Issue

Closes #757
Changes proposed

Created a new file to add SVG of Graduation Hat , Added the SVG Component to the milestone.js

Actually, never mind, just read the issue properly. 😅

Thanks all 👍
We should not add images to the project.
We will move to using another Icon library that will have more icons available

Considering the recent developments and because this was added in the PR which integrated react-icons, we would have to close this PR. Thanks for opening the PR and contributing to LinkFree!


call_completion_callbacks crash

What happened?
The application crashed.
Repro steps
We are not sure.
Version
3.10.5
What Atlas Services are you using?
Both Atlas Device Sync and Atlas App Services
What type of application is this?
Flutter Application
Client OS and version
iPhone 14 Pro, 16.5.0
Code snippets
No response
Stacktrace of the exception/crash you're getting
Crashed: io.flutter.1.ui
0  libsystem_pthread.dylib        0x3024 pthread_mutex_lock + 12
1  libc++.1.dylib                 0x14f78 std::__1::mutex::lock() + 16
2  realm_dart                     0xbe288 realm::Realm::call_completion_callbacks() + 84
3  realm_dart                     0xc4680 realm::util::UniqueFunction<void ()>::SpecificImpl<realm::Realm::end_current_write(bool)::$_6::operator()()::'lambda'()>::call() + 32
4  realm_dart                     0x129be4 realm::util::InvocationQueue::invoke_all() + 80
5  App                            0x7e6c kDartVmSnapshotInstructions + 5356
6  App                            0x68af4 kDartIsolateSnapshotInstructions + 378484
7  App                            0x13eab8 kDartIsolateSnapshotInstructions + 1254968
8  App                            0x13ea50 kDartIsolateSnapshotInstructions + 1254864
9  App                            0x13e9e0 kDartIsolateSnapshotInstructions + 1254752
10 App                            0xa58d8c kDartIsolateSnapshotInstructions + 10799372
11 App                            0x2ecac kDartIsolateSnapshotInstructions + 141356
12 App                            0x9bd0 kDartVmSnapshotInstructions + 12880
13 Flutter                        0x61c590 (Missing UUID 4c4c441655553144a141563ec5008ebf)
14 Flutter                        0x626b08 (Missing UUID 4c4c441655553144a141563ec5008ebf)
15 Flutter                        0x62d334 (Missing UUID 4c4c441655553144a141563ec5008ebf)
16 Flutter                        0x40285c (Missing UUID 4c4c441655553144a141563ec5008ebf)
17 Flutter                        0x2e3134 (Missing UUID 4c4c441655553144a141563ec5008ebf)
18 Flutter                        0x2e6460 (Missing UUID 4c4c441655553144a141563ec5008ebf)
19 CoreFoundation                 0xcb624 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32
20 CoreFoundation                 0x88f4c __CFRunLoopDoTimer + 940
21 CoreFoundation                 0x2e71c __CFRunLoopDoTimers + 288
22 CoreFoundation                 0x7a4d4 __CFRunLoopRun + 1852
23 CoreFoundation                 0x7f3ec CFRunLoopRunSpecific + 612
24 Flutter                        0x2e654c (Missing UUID 4c4c441655553144a141563ec5008ebf)
25 Flutter                        0x2e603c (Missing UUID 4c4c441655553144a141563ec5008ebf)
26 libsystem_pthread.dylib        0x16b8 _pthread_start + 148
27 libsystem_pthread.dylib        0xb88 thread_start + 8

Relevant log output
No response

@ahmdaeyz What version of realm was in use?

When I created the issue it was '1.2.0'.

How often do you see this? And have you seen it with other versions of realm?

Hello @nielsenko,
Sorry for my late response. Sentry shows that this issue happened 6 times. First time was 21 June. We don't have realm on a fixed version. And we don't commit our pubspec.lock and are using codemagic. So surely it is always at the latest version. On 21st June, the version was: 1.2.0. It also happened with 1.3.0 because we have an event with that.

@ahmdaeyz I have not been able to recreate this, but I did find an issue regarding client reset callbacks and a the livetime of a mutex that will be fixed in the next version. However, I'm not confident it is the issue you see.
Please keep us posted if you see it again, especially after next release.


Ambiguous use of 'attributedPlaceholder'

I want to add attributed placeholder to textView which if type GrowingTextView. But it shows error "Ambiguous use of "attributedPlaceholder".

I guess the name of the placeholder attribute should be changed to something different as UItextView already has placeholder attribute.

The same issue... I fixed it like:
"textView.placeholderTextView.text = "Placeholder...""


chore(deps): update esbuild to 0.15.18

Description
https://github.com/evanw/esbuild/blob/master/CHANGELOG.md

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

/ecosystem-ci run

For some reason CI is taking a long time, but vite-ecosystem-ci is showing the same greens as without this PR. I think this should be safe to merge.


Model cascading (models including other models)

I'm using the same example on the web
OrderModel.h
@protocol ProductModel
@end

@interface ProductModel : JSONModel
@property (assign, nonatomic) int id;
@property (strong, nonatomic) NSString* name;
@property (assign, nonatomic) float price;
@end

@implementation ProductModel
@end

@interface OrderModel : JSONModel
@property (assign, nonatomic) int order_id;
@property (assign, nonatomic) float total_price;
@property (strong, nonatomic) NSArray<ProductModel>* products;
@end

@implementation OrderModel
@end

But when I build the project I face one issue "Duplicate symbols"
duplicate symbol _OBJC_CLASS_$_OrderModel
ld: 576 duplicate symbols for architecture arm64
clang: error: linker command failed with exit code 1

This issue is not related to JSONModel. There is most likely something wrong with how you're defining and/or importing these classes.


proposals/ RPn_R101_fpn_lvis_train.pkl

Hello, thank you very much for your work!
I have a question. How can I use code to generate 'proposals/ RPn_R101_fpn_lvis_train.pkl 'if you don't give them? Or are there detailed code instructions?
Thank you so much!

I have provided the training code of RPN in Readme, just follow the instructions of mmdetection to train RPN. Regards

Hi, I've tried the code of RPN you provided and work on building a more generalized rpn. Thanks for sharing the code and model. However, I have the following issues and would appreciate your help :

I test the epoch20.pth you provide on lvis_1 dataset. I get<EMAIL_ADDRESS>far from the AR given by ViLD paper, Table 1<EMAIL_ADDRESS>Why does this happen? I understand that ViLD tests on the lvis novel data and you test the whole data. Shouldn't the epoch_20.pth perform much better than the ViLD rpn?
I don't get the same performance when training RPN using your code. I use the config rpn_r101_fpn_1x_lvis.py (training 12 epoch, no 20epoch config is provided) and only get<EMAIL_ADDRESS>I follow the mmdet instructions and simply use bash tools/dist_tran.sh configs/rpn/rpn_r101_fpn_1x_lvis.py 2 to train the RPN, why do I get such low performance?
I can only test the RPN model using proposal_fast mode. When I use bash tools/dist_test.sh configs/rpn/rpn_r101_fpn_1x_lvis.py models/epoch_20.pth 1 --out work_dirs/result.pkl --eval proposal , I get all zero results.


Tutorial - get started with registration using deep learning

Describe the basics in training registration:

unsupervised learning
weakly supervised learning
combininig unsupervised loss and weak supervisions
conditional segmentation

with data loader and links to demos

merged


Fix: Mayachain

Fix: Mayachain's client tests are still using thorchain consts.

[ ] Synths don't work
[ ] Synths decimals are wrong

Anyone able to tackle this in upcoming updates?


Apply multi-stage build in Dockerfile

Multi-stage builds won't require golang environment to build the kube-applier. It will build the go binary inside Docker containers.
This needs Docker 17.05 or higher which is why I updated Docker's version requirement on README.md

Closing due to a by-mistake force push.


adding coordination place visits to the transform history

Two patch files attached for testing:
Test 1, simple coordination place:
coordination_xform.patch.txt
Test 2, coordination place that calls coordination places:
coord_x_coord_xform.patch.txt

Notes:

Appending to the transform history is turned off by default for backwards-compatibility.
I don't indent or add anything to the front of the place by default because of spacing issues when calling coordination places from coordination places. I did add a config item if you want to indent or add anything to the front of the output.
I purposely left expense off of the output because it does not make sense in the context of coordination.

Sample output:
filename: README.md
   creationTimestamp: Mon Jun 06 10:49:01 GMT 2022
   currentForms: []
   filetype: null
   transform history (6) :
     UNKNOWN.FILE_PICK_UP.INPUT.http://localhost:8001/FilePickUpPlace$5050
     UNKNOWN.UNIXFILE.ID.http://localhost:8001/UnixFilePlace$2050
     UNKNOWN.TO_LOWER_UPPER_COORDINATION.TRANSFORM.http://localhost:8001/ToLowerUpperCoordinationPlace$1010
       UNKNOWN.TO_LOWER.TRANSFORM.http://localhost:8001/ToLowerPlace
       LOWER_CASE.TO_UPPER.TRANSFORM.http://localhost:8001/ToUpperPlace
     FINI.DROP_OFF.IO.http://localhost:8001/DropOffPlace$9990


example evaluation queries failing [spider2-lite]

Hi,
Two queries out of 3 in example_submission_folder are failing.
Query bq026_2 return this error:
Error occurred while fetching data:  403 Access Denied: Table spider2-public-data:patents.publications: User does not have permission to query table spider2-public-data:patents.publications, or perhaps it does not exist.; reason: accessDenied, message: Access Denied: Table spider2-public-data:patents.publications: User does not have permission to query table spider2-public-data:patents.publications, or perhaps it does not exist.
Query bq207 error:
Error occurred while fetching data:  403 Access Denied: Table spider2-public-data:patents.publications: User does not have permission to query table spider2-public-data:patents.publications, or perhaps it does not exist.; reason: accessDenied, message: Access Denied: Table spider2-public-data:patents.publications: User does not have permission to query table spider2-public-data:patents.publications, or perhaps it does not exist.

please add your service account in this form

thanks for access. I can access the databases.
However, evaluating example_folder queries. I get
{'bq026_2': 0, 'bq117': 1, 'bq207': 0}
Is this the expected result? Only one successful query (bbq117) from the examples.
thanks.


Multi compiler

Is it possible to have a multi compiler configuration with this module?

Yes, see #9

How is this supposed to work?
I included this plugin for each of my configs, which are exported as an array to the webpack multicompiler. When webpack runs, I see logs for each config, sometimes a mix of success and error depending on the compiler results.
This can be extremely confusing if clearConsole: true since there's a possibility that I could see nothing but a [DONE] Compiled successfully in XXXms message for one config when there could be an error in another.
webpack.config.babel.js
import clientConfig from './webpack.config.client.babel';
import serverConfig from './webpack.config.server.babel';

export default [clientConfig, serverConfig];

webpack.config.base.babel.js
import FriendlyErrorsPlugin from 'friendly-errors-webpack-plugin';

export default {
  stats: 'none',
  module: {
    rules: [
      {
        test: /\.js?$/,
        use: 'babel-loader',
        exclude: /node_modules/
      }
    ]
  },
  plugins: [
    new FriendlyErrorsPlugin({
      clearConsole: false
    })
  ]
}

webpack.config.client.babel.js
import path from 'path';
import webpackMerge from 'webpack-merge';
import baseConfig from './webpack.config.base.babel';

export default webpackMerge(baseConfig, {
  target: 'web',
  name: 'client',
  entry: {
    client: './client/client.js'
  },
  output: {
    path: path.resolve('./build/assets'),
    filename: 'scripts/[name].bundle.js'
  }
});

webpack.config.server.babel.js
import path from 'path';
import webpackMerge from 'webpack-merge';
import nodeExternals from 'webpack-node-externals';
import baseConfig from './webpack.config.base.babel';

export default webpackMerge(baseConfig, {
  target: 'node',
  name: 'server',
  externals: [nodeExternals()],
  entry: {
    server: './server/server.js'
  },
  output: {
    path: path.resolve('./build'),
    filename: '[name].bundle.js'
  }
});


add libcsptr?

https://github.com/Snaipe/libcsptr

Thanks for the suggestion, but I am not interested in including this
library. In general my focus is distributing tools, not libraries (beyond
Mingw-w64 as a foundational C runtime). I considered including zlib, one
of the most widely-used general purpose libraries, but ultimately decided
against it. That establishes baseline for inclusion.
First, I don't want to be in involved in supplying dependencies. Which
version should I include? How should it be built? Since they're linked in
arbitrary contexts, I have to consider security ramifications. I'm likely
to patch it just as I patch the tools in w64devkit, so it will diverge
from expectation, which will be more noticeable with libraries than tools,
and may require support.
Second, developers can mostly build these dependencies themselves. They
have the very tools for it in their hands! Then they can answer all the
above questions as they wish. For example, they can produce a debug build
of the library — debug symbols, UBSan, assertions, etc. — which I wouldn't
supply. (Very relevant in this case as I'll discuss in a moment.) For
example, despite the overly-complicated CMake build in the libcsptr
repository, it's trivial to build in w64devkit without CMake. These
commands build both a shared and static library (release build):
$ touch include/csptr/config.h
$ cc -c -g3 -DNDEBUG -Os -Iinclude/csptr src/*.c
$ cc -shared -s -o csptr.dll *.o
$ ar r csptr.a *.o
Many libraries like, zlib and SQLite, are even easier to build. A few are
quite a bit harder, such as SDL, and you'll probably just need to download
an official build.
If I included such libraries in w64devkit, they'd be on the include path
and linkable with "-l". You could get the same by copying the headers and
build artifacts under w64devkit, though that's fragile and will get wiped
out by upgrades. Instead I suggest creating a "library root" and pointing
GCC there with C_INCLUDE_PATH, CPLUS_INCLUDE_PATH, and LIBRARY_PATH (i.e.
set them in your .profile.) On my primary system I have zlib "installed"
this way. It would also work with libcsptr.
Third, w64devkit is in large part capturing my personal preferences and
workflows. I use it a lot and I use nearly every tool in one way or
another. (If there's something I don't recognize, I learn how to use it,
and then either it's useful or I delete it!) And I hardly use libraries
beyond system-provided DLLs. I mentioned zlib, but I don't even use that
enough to justify distributing it in w64devkit.
With that out of the way I have some specific libcsptr criticisms. Even if
I was distributing libraries I still wouldn't include libcsptr.  My favorite links on
this topic:
https://www.youtube.com/watch?v=f4ioc8-lDc0&t=4407s
https://www.rfleury.com/p/untangling-lifetimes-the-arena-allocator
Additionally, the library doesn't meet my quality standards. The tests and
the "smart array" example in the README trigger UBSan due to passing null
to memcpy. If you make a UBSan debug build of libcsptr (see the w64devkit
README for details) — which is what I would use during development — this
will show up the moment you create a smart array. Easy to fix, but nobody
noticing it all these years despite being easy to catch is a red flag.
Perfect example of something I would patch. Also, it uses a VLA/alloca
temporary — another red flag — and so you can't safely allocate a smart
pointer for any object larger than a MB or so without it blowing the
stack. That's something else I would patch. I found those in the first few
minutes, and if I spent more time on it I expect I'd find more.

I'm just a little curious as to why you seem to prefer C over CPP?

There's little in C++ worth using that isn't already in C. Most features
are either junk or not worth the trade-offs. When I say "Modern C++" below
I mean typical template-heavy, smart pointers C++11 (or later). Going
through C features I particularly value:

Very fast builds.

I like quick iterations and fast turnaround, not wasting my time waiting
on tools. GCC 12, at -O0, compiles C at ~20,000 lines per second, and MSVC
is about double this. I can build entire programs from scratch without any
incremental or parallel configuration (e.g. unity builds) in the blink of
an eye. Modern C++ compiles at ~200 lines per second. Literally two orders
of magnitude difference. Even linking C++ is slower due to the presence of
many more symbols from templating.

Fast debug binaries.

Debug binaries of C programs are nearly as fast as release. In most cases
you'd need to look closely to notice the difference. In fact, a C debug
binary is typically faster than the equivalent Modern C++ release build.
(I demonstrated this in my MSI hash table article.)
In contrast, C++ templates bloat up into mountains of code and rely on
optimization to clean it up. Debug builds are painfully slow, and the
difference between debug and release is vast.

Transparency and simplicity.

Step through a Modern C++ program in a debugger and you will find yourself
jumping in and out of the C++ standard library and other runtime and
template gunk that glues everything together. There are overloads all over
the place and it's difficult to reason about exactly what's happening.
This is especially true for debug builds which hasn't optimized some of
this away.
Debuggers, GDB especially, struggle with displaying and expressing complex
C++ types built from layers of templates.
I might like function overloading, but the cost is name mangling even when
unused. Most of the time tools know how to demangle C++ symbols, but not
always. When they don't, it's a lot of friction. Name mangling is just too
high a cost, and a persistent thorn even when I'm writing C-styled C++.
I wish C had even simpler syntax. I'd happily give up const in exchange
for more simplicity. It's not doing much anyway. C++ goes exactly the
opposite direction.

So what does C++ have? declspec is nice. Not needing to typedef structs
is nice, especially for recursive fields. I like that bitwise operators
don't overflow; it's a mistake for C to treat them like arithmetic. I like
empty initializer lists for default-initializing anything, and I like the
option to choose default initialization for fields. (Honestly, C and C++
should have been defined to default-initialize all variables by default,
with some special keyword to disable initialization when the performance
matters. That was an early design mistake.) Though beyond this, C++
initialization is insane.
I'm not totally against type deduction, but outside of templates it's not
important. Lambdas could have been neat, but weren't defined tightly
enough (might allocate, too opaque). Namespaces could be useful, but
aren't worth the cost of name mangling. Destructuring is neat in theory
but disappointing in practice.
That's about it for useful C++ features. Exceptions are bad. Templates are
a disaster. I still do not understand even the syntax of Concepts after
hours of study. Smart pointers conflate allocation and lifetime, and
resolve details at run-time that ought to be known at compile time
(previously discussed). I dislike OOP (inheritance, virtual functions,
access specifiers, etc.). Just like C, the C++ standard library is poor
and best avoided. (Fortunately, also like C, it's easy to do so.)
My review of the C standard library in practice
https://nullprogram.com/blog/2023/02/11/
C++ containers aren't salvageable because allocation is broken. In Modern
C++ you now get to supply a custom allocator — a process that is hideously
complicated — but the allocator is part of the container type, making it
practically useless.
I think that's about it. Looks like I can count the things I like about
C++ (versus C) on one hand, and these aren't worth the entry cost. That
being said, the tooling, especially debugging, for C and C++ is still
best-of-class by a huge margin, and if it was C++ versus anything else
except C, I'd choose C++ then write it like C. :-)