Implement ActiveSupport::Cache::DalliStore#inspect

Currently, ActiveSupport::Cache::DalliStore#inspect is not implemented, and will show…

the object’s class name, an encoding of the object id, and a list of the instance variables and their values (by calling inspect on each of them).

We are having trouble using the BetterErrors gem in our application, due to the combination of a few things:

DalliStore#inspect calling inspect on all its instance variables,
Rails setting a @middleware variable on the cache object,
Our application doing dependency injection, e.g. def initialize(cache = Rails.cache); @cache = cache, and
BetterErrors calling binding on various objects.

I’m not 100% sure where it happens, but the binding causes #inspect to be called on our DalliStore instance, which returns several megabytes that BetterErrors tries to serialize to JSON and … everything kinda stops working.
Would it be ok to implement a DalliStore#inspect?

So when you say that DalliStore doesn't implement inspect, what you really mean is that DalliStore inherits the verbose version of inspect from somewhere in its parent chain.
Based on the issue you filed, I'm not clear on what you're proposing the method do instead.  The current behavior seems pretty consistent with the intended behavior of inspect.  What would you do differently?

So when you say that DalliStore doesn't implement inspect, what you really mean is that DalliStore inherits the verbose version of inspect from somewhere in its parent chain.

Yes, DalliStore#inspect is inherited from Object#inspect.

Based on the issue you filed, I'm not clear on what you're proposing the method do instead. The current behavior seems pretty consistent with the intended behavior of inspect. What would you do differently?

I’ve worked around it by implementing #inspect to return only
"#<ActiveSupport::Cache::DalliStore>"

and it solved my problem with BetterErrors.
On second thought, I’m not sure that this is something Dalli should be concerned with. Perhaps affected applications should just implement this “hack” to work around Rails’ “pollution” of the cache object.
Feel free to close this issue.


[Suggest]Weight Converted to Knockback Resistance

A hard-core style setting, which makes overweight status no longer a complete burden

such that when hit by another entity you dont fly as far?

yea

ill look into it

TKS


Interacting with RoboJackets SSO applications

We've established that working with the OrgSync API is less than ideal for a variety of reasons; however, our other hosted applications are currently using GRS roles to manage their internal user information.
100% of our authentication middleware is developed internally around the phpCAS library, which simply returns RoboJackets OrgSync group membership as an array (after a nonzero amount of SAML attribute parsing). We could conceivably replace this process with an API call to Apiary, which would enable us to manage user authorizations in real time and without involving OrgSync. Such a call would be made immediately after CAS information is available to the middleware and before the user is logged into the application.
This would be an alternative to performing group updates in OrgSync when a user moves teams in Apiary. If we were to go this route, we'd still need to keep the OrgSync functionality as a fallback for legacy users that haven't onboarded to Apiary for whatever reason.
This would essentially be an API endpoint that would return a JSON array of groups for a given UID. The easiest way to manage authentication would be IP whitelisting, as there are only two or three servers that would need to hit this API.

This should be easily doable once Fractal is implemented. Hit the user.show endpoint and request inclusion of roles and teams relations.

Superseded by #334


improves build.md completeness

I spent some time working through errors while following the steps in docs/build.md. I added the steps I needed to follow to remediate these errors. These extra clarifications should help save new developers time getting their dev environment up and running.
Note: While I'm successfully able to install the app on an iOS simulator, I'm not yet able to run the end-to-end tests using the steps under "Run e2e tests"

Yup I ran into the jq issue when I was setting this up as well, thanks for adding it.


Client Certificates by Environment

Four our team I'm looking for a valid alternative to PostMan.
Bruno looks very clean, reactive and easy to use, thank you!
What I'm missing is the possibility to define client-certificates depending on the environment.
Would it be available in the near future?

Any plans to add support for client certificate functionality?

This looks like a promising approach: https://stackoverflow.com/a/52065387
Unfortunately I'm unable to contribute here since I don't know much about the underlaying programing language :(

HTTP client certificates would be cool to have indeed.

There is PR adding it:
#275

@helloanoop #275 has been merged, so I guess this can be closed :)

Awesome, thank you!


Use sigs.k8s.io/yaml rather than pkg.in/yaml.v2.

What this PR does / why we need it:
Turns out that yaml.v2 unmarshals maps into map[interface{}]interface{} rather
than try to insist on a most narrow possible key type (i.e. string). Such values
are then rejected by sigs.k8s.io/yaml.Marshal that WrapParamValue uses,
because it does a conversion to JSON first, and JSON does not support
non-string keys.
It seems like yaml.v3 works better in that regard. However comments on the
aforementioned issue seem to imply that it's still not all rosy.
Moreover, using the same package for unmarshalling as we do for marshalling
seems like a more stable choice long-term.
This also adds some vlog statements and tidies up go.mod.

Fixes #1437

Also, I'd like to see a test for the #1437

Thanks for the quick reviews. Test added.


Improve documentation

The documentation seems a bit outdated in some places. Other than that I think we can also make some improvements to the overall structure, as some things are explained multiple times at the moment.
Proposed structure

Introduction: The unique selling points and advantages of Baker
Quick start guide: overview of required dependencies and module structure
Tutorial: A short tutorial that can be completed in < 30 minutes. Creating a simple recipe and firing some sensory events. A slimmed down version of what we currently have under "Development Life Cycle"
Core Concepts: A section dedicated fully to the 3 main concepts in Baker. events, ingredients, and recipes.
Cookbook: A collection of things you can do with recipes. Quite similar to what we have under the "Recipe DSLs" section at the moment.
Running in production: Things you might want to know if you consider running Baker in production. Stuff like testing, configuration, monitoring, error handling, and resolving failed recipes.
Reference: This is where we go deep into nitty gritty details for the user who wants to know everything.

Other possible improvements
Type safe code samples
All code samples are written in Markdown files. If we change the actual implementation we might not notice the docs become outdated. Ideally the examples come from compiled snippets. I think we can achieve that via the "snippets" extension.
Register extension:
markdown_extensions:
  - pymdownx.snippets:
      base_path: docs

Load snippet:
  --8<-- "myfile.txt"

More info here: https://facelessuser.github.io/pymdown-extensions/extensions/snippets/#snippets
Tooltips in code samples
Mkdocs has the option to add tooltips to your code samples. I think this looks nicer than the comments we use now. Don't know how well this works in combination with the type safe code samples though.

Will be merged as part of the 4.0.0 release.


ruby-3.0.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:1490:in event_callback': undefined method close' for 9:Integer (NoMethodError)

ruby-3.0.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:1490:in event_callback': undefined method close' for 9:Integer (NoMethodError)
I used the ruby-3.0.0
Rails <IP_ADDRESS>
mailcatcher (0.2.4)

ruby-3.0.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:1490:in event_callback': undefined method close' for 9:Integer (NoMethodError)

This https://github.com/sj26/mailcatcher/issues/62
And this
https://github.com/sj26/mailcatcher#bundler
So you just need to remove mailcatcher from gemfile (for some reason it break everything)
And run
gem install mailcatcher

That version of mailcatcher is very old. It will be limited by interdependencies with your own application.
@CringeDeveloper is spot on — please remove mailcatcher from your Gemfile and install it using gem install mailcatcher.


Properly support both CJS and ESM

Resolves #20

I hope this solves my Problem too, cuz with the newst version i stil get
SyntaxError: The requested module 'discord-webhook-node' does not provide an export named 'Webhook'

My Code
import { Webhook, MessageBuilder } from 'discord-webhook-node';
`try {
let hook = Webhook("TESTURL");
let embed = MessageBuilder()
.setTitle("Test")
.setTimestamp();
        textObjects.forEach(elem => {
            embed.addField(elem.fieldTitle, elem.fieldValue)
        });`

} catch(e) {
console.log(e)
}

hm i still get the error i posted after the update, any idea?

@matthew1232

Alright, nvm. I need to use
import Webhook from 'discord-webhook-node';
import MessageBuilder from 'discord-webhook-node';

Do both webhook and messagebuilder perform as expected though?

Code
import Webhook from 'discord-webhook-node';
import MessageBuilder from 'discord-webhook-node';
let hook = new Webhook(url);
let embed = new MessageBuilder()
.setTitle(title)
.setTimestamp();
hook.send(embed);
results in a "TypeError: Webhook is not a constructor"
if i use
let hook = Webhook(url);
let embed = MessageBuilder()
Then i get "is not a function"
@matthew1232

@C0kkie I've been trying to reproduce the errors you've reported here and those in #16 but been unable to. Could you respond with more details, such as the version of Node you're running, and the versions of any other tools you're using?

I use node version 14

I try to use it within a gtav framework called Alt:V https://altv.mp/#/
We have many other packages installed like mysql2 where it works like a charm

the only thing whats written there that they are using ES6

@C0kkie I've taken a quick look at Alt:V, and it appears to be using Node v12.4.0 internally, which is over a year old. Back then, ESM support in Node was still in early experimental stages, and as such, it doesn't support the exports field that's being used here to support both systems. Trying to import the package with Node v12.4.0 does indeed produce the exact errors you have reported.
Assuming you can't get the devs of Alt:V to upgrade to a newer version of Node, and ignoring solutions such as making a separate version of this package which only supports ESM, I would suggest you just use the default import and manually destructure it:
import discord_webhook_node from "discord-webhook-node";
const { Webhook, MessageBuilder } = discord_webhook_node;

Alright thanks.
import discord_webhook_node from "discord-webhook-node";
const { Webhook, MessageBuilder } = discord_webhook_node;
Solved my problem


Get lineage phenotypes

Modified run for assigning phenotpes to lineages.
papermill -p config_yaml XBB_config.yaml lineage_phenotypes.ipynb results/lineage_phenotypes.ipynb

Added:

lineage_phenotypes.ipnyb (based on SARS2-spike-predictor-phenos.ipnyb)
XBB_configs.yaml (based on config.yaml)
lineage_phenotypes.csv and lineage_phenotypes_randomized.csv
pivot_spike_pseudovirus_DMS_XBB.1.5.csv

Modified:

lineage_phenotypes.ipnyb only outputs the intermediate files and lineage_phenotypes.csv and replaced "clade" to "lineage" throughout notebook and config.
Split the spike pseudovirus DMS input data by region (RBD, S2, NDT, other) and saved intermediate file pivot_spike_pseudovirus_DMS_XBB.1.5.csv.
XBB_configs.yaml selects for spike RBD (region=RBD) and spike non-RBD (region=S2). Should I keep NDT and other as well?
XBB_configs.yaml only uses XBB as reference. Should we eventually create a seperate <variant>_config.yaml for BA2.86 and BA.2? In that case, it would make sense to provide the config in the papermill command rather than in the notebook itself.
Overwrote mutation_phenotypes.csv and mutation_phenotypes_randomized.csv while running lineage_phenotypes.ipnyb. Sorry, I am guessing it would be good to keep the original ones too.

Removed from SARS2-spike-predictor-phenos.ipnyb:

Growth data step
Summary plot step
Removed code to avoid  https://github.com/corneliusroemer/pango-sequences/issues/9.

Results:
Header of lineage_phenotypes.csv
'lineage', 'date', 'parent', 'spike muts from Wuhan-Hu-1',
     'number spike muts from Wuhan-Hu-1', 'spike muts from XBB.1.5',
     'descendant of XBB',
     'spike pseudovirus DMS RBD human sera escape relative to XBB.1.5',
     'spike pseudovirus DMS RBD ACE2 binding relative to XBB.1.5',
     'spike pseudovirus DMS RBD spike mediated entry relative to XBB.1.5',
     'spike pseudovirus DMS S2 human sera escape relative to XBB.1.5',
     'spike pseudovirus DMS S2 ACE2 binding relative to XBB.1.5',
     'spike pseudovirus DMS S2 spike mediated entry relative to XBB.1.5',
     'RBD yeast-display DMS ACE2 affinity relative to XBB.1.5',
     'RBD yeast-display DMS RBD expression relative to XBB.1.5',
     'RBD yeast-display DMS escape relative to XBB.1.5',
     'EVEscape relative to XBB.1.5', 'Hamming distance relative to XBB.1.5'

Missing from Trevor's list in slack:

number of ORF1ab mutations
number of accessory protein mutations

Thanks for your comments!
Good point, I will update the README with the commands and descriptions of the second notebook once I get other people's input on whether this is what we want/need.
And I just changed the config to also include the NTD, thanks!

@plsteinberg and @jbloom --- Is this now ready to merge? Is looks like it might be?


Arbitrum Fork and running scripts containing vm.start/stopBroadcast in test results in failing deployment

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (e9f274d 2022-12-11T00:03:42.968584731Z)
What command(s) is the bug in?
forge test -vvvv
Operating System
Linux
Describe the bug
There seems to be an issue with the vm.start/stopBroadcast instructions used within tests. Removing the fork and select instruction and/or the vm.start/stopBroadcast doesn't produce the issue.
Step to reproduce:

https://github.com/0xCalibur/foundry_arbitrum_fork_issue
forge test -vvvv

Expectation:

test passing

What is actually happening:
➜  hello_foundry git:(main) forge test -vvvv
[⠊] Compiling...
[⠒] Compiling 2 files with 0.8.16
[⠑] Solc 0.8.16 finished in 421.27ms
Compiler run successful
2022-12-11T13:47:21.014261Z ERROR forge::runner: setUp failed reason="EvmError: Revert" contract=0x7fa9385be102ac3eac297483dd6233d62b3e1496

Running 1 test for test/Test.t.sol:CounterTest
[FAIL. Reason: Setup failed: EvmError: Revert] setUp() (gas: 0)
Traces:
  [0] CounterTest::setUp()
    ├─ [0] VM::createSelectFork(https://1rpc.io/arb, 44679129)
    │   └─ ← 0
    ├─ [1851178] → new MyScript@0x5615dEB798BB3E4dFa0139dFa1b3D433Cc23b72f
    │   ├─ [0] VM::rpcUrlStructs() [staticcall]
    │   │   └─ ← []
    │   └─ ← 1841 bytes of code
    ├─ [8937393460516792307] MyScript::run()
    │   ├─ [0] VM::startBroadcast()
    │   │   └─ ← ()
    │   ├─ [241300] → new ProxyOracle@0x5b73C5498c1E3b4dbA84de0F1833c4a029d90519
    │   │   └─ ← 1094 bytes of code
    │   ├─ [8937393460514904257] → new <Unknown>@0x104fBc016F4bb334D775a19E8A6510109AC63E00
    │   │   └─ ← 0 bytes of code
    │   └─ ← "EvmError: Revert"
    └─ ← ()

Test result: FAILED. 0 passed; 1 failed; finished in 446.87ms

Failing tests:
Encountered 1 failing test in test/Test.t.sol:CounterTest
[FAIL. Reason: Setup failed: EvmError: Revert] setUp() (gas: 0)

As a quick fix you can add --sender 0x.... to your command or call vm.startBroadcast(0x... with a specific address.
But the underlying issue seems slightly trickier.
The default foundry sender is creating the TestContract with nonce 1 resulting in the following address: 0x7FA9385bE102ac3EAc297483Dd6233D62b3e1496.
Eventually,  MyScript.run() is called after changing to a fork. This change resets the default foundry sender nonce to 0. It creates the first contract (0x5b73C5498c1E3b4dbA84de0F1833c4a029d90519), and when it tries to create the second contract with nonce 1 it will try to create a contract @ 0x7FA9385bE102ac3EAc297483Dd6233D62b3e1496... which is already taken by the TestContract. I'm not entirely sure why the log is showing 0x104..., but I've debugged it and havae seen it happen.

@joshieDo thanks for looking in to it. As another workaround within my test I have a testingboolean and just skip the broadcasts when it's true. But interesting problem here, just wondering why this specifically happen with Arbitrum forks only.
Another possible linked issue, is when deploying multiple contracts in script for Arbitrum, it seems to cause problem with gas estimation. So I need to deploy the contracts one by one. Maybe that's completely unrelated thought, just wanted to point it out.

after this PR merge, I just ran foundryup, I assumed it will install the latest from master, right?

@0xCalibur  No, it installs the one built by the nightly pipeline.
I'm not sure if when you tried, it had already been built with the fix... so can you try again? (I did, and it worked fine).

I confirm this is now working, I must have ran foundryup before the build was ready. Thanks.


Mistake in Terms

This is different from what we have expressed many times:
http://blog.storj.io/post/160448088948/token-migration-plan-pt2

@frdwrd @barbaraliau


use of undeclared crate or module arbitrary

Hello there!
I am trying to use cargo-fuzz in my project and st up everything like it is described in the book. However for some reason running fuzz tests fails with use of undeclared crate or module arbitrary
Here is my Cargo.toml
[package]
name = "retro-api-fuzz"
version = "0.0.0"
authors = ["Automatically generated"]
publish = false
edition = "2018"

[package.metadata]
cargo-fuzz = true

[dependencies]
libfuzzer-sys = { version = "0.4", features = ["arbitrary-derive"] }
uuid = { version = "=1.1.1", features = ["serde", "v4", "arbitrary"] }

[dependencies.retro-api]
path = ".."
features = ["arbitrary"]

# Prevent this from interfering with workspaces
[workspace]
members = ["."]

[[bin]]
name = "remove_ticket"
path = "fuzz_targets/remove_ticket.rs"
test = false
doc = false

and here is my fuzz target code
#![no_main]
use libfuzzer_sys::{arbitrary::Arbitrary, fuzz_target};

use uuid::Uuid;

use retro_api::experiment::BoardAggregate;

#[derive(Arbitrary, Debug)]
struct Input {
    board_aggregate: BoardAggregate,
    ticket_id: Uuid,
}

fuzz_target!(|input: Input| {
    let Input {
        board_aggregate,
        ticket_id,
    } = input;

    let event = board_aggregate.remove_ticket(ticket_id);

    if let Ok(event) = event {
        assert!(board_aggregate.replay(event).is_ok());
    }
});

This setup produces following error
error[E0433]: failed to resolve: use of undeclared crate or module `arbitrary`
 --> fuzz_targets/remove_ticket.rs:9:10
  |
9 | #[derive(Arbitrary, Debug)]
  |          ^^^^^^^^^ use of undeclared crate or module `arbitrary`
  |
  = note: this error originates in the derive macro `Arbitrary` (in Nightly builds, run with -Z macro-backtrace for more info)

Is it a bug or am I missing something here?

You should import libfuzzer_sys::arbitrary
Unfortunately imports in proc macros are annoying.

@Manishearth thank you, it works now!
I think it is worth updating the book so it is mentioned there as well. Currently the book proposes exactly the code I had before: https://rust-fuzz.github.io/book/cargo-fuzz/structure-aware-fuzzing.html#define-an-allocatormethod-type-and-derive-arbitrary


Send trace origin

:scroll: Description

Sentry trace origin for spans and contexts.
See https://develop.sentry.dev/sdk/performance/trace-origin
:bulb: Motivation and Context

Closes #1420
:green_heart: How did you test it?
Tests
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[x] No new PII added or SDK only sends newly added PII if sendDefaultPii is enabled
[ ] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

@denrase not sure if you looked at but here we go for iOS implementation https://github.com/getsentry/sentry-cocoa/pull/2957/files

Left a few comments, @philipphofmann is OOO but maybe @brustolin can chime in since he reviewed the iOS bits?

@marandaneto I did check out the iOS PR. To what are you referring in "we go with iOS implementation"?

@marandaneto I did check out the iOS PR. To what are you referring with "we go with iOS implementation"? What am I missing? 🤔

Nothing, all good, sorry for the confusion, just wanted to ask because the iOS PR isn't linked to https://github.com/getsentry/sentry-dart/issues/1420 directly.

@denrase I see a failing test:

test/widgets_binding_observer_test.dart: WidgetsBindingObserver lifecycle breadcrumbs (failed)


fix checking for authorized fields if no field is specified

fix #323

I have read the DCO document and I hereby sign-off my contribution


[ACR] Prefix storage account name with registry name

Prefix storage account name with registry name.
Add tags to storage account.
Add registry name validation to avoid creating storage account when registry name is not available.

/cc @SajayAntony

/cc @stevelas
:shipit:

@tjprescott @derekbekoe Can we have this merged if there is no more comment? Thanks.


Can't install - sync.Map

Any idea why I can't install this package?
:gorm_test rando$ go version
go version go1.8.7 darwin/amd64
:gorm_test rando$ go get -u github.com/jinzhu/gorm
# github.com/jinzhu/gorm
../go/src/github.com/jinzhu/gorm/main.go:26: undefined: sync.Map

sync.Map is available since Go version 1.9. Please update your Go version.


Create a stepper component

Add a stepper component which can be used for creating form wizards.
Ref
https://material-ui.com/components/steppers/
https://www.telerik.com/kendo-react-ui/components/layout/stepper/
https://ant.design/components/steps/

Multi-step form React


fix(search): increase size on fullPageWidth viewport

This is the preview size on desktop
https://github.com/jackyzha0/quartz/assets/29749331/5a1576f9-2f47-4346-b24d-6837a9225970

(can u also add a video :'))

(can u also add a video :'))

oui oui updated the title

what's the flashing in the demo? max height being adjusted?


Demographics Banner should be able to be deceased without needing a deceased date.

Description of Issue
Right now, the demographics banner requires that a deceased date is required in order to display a demographics banner as deceased. However, there has been a request to displayed the banner as deceased if there is no deceased date required.
Component Version
demographics-banner - 0.1.0
Browser and Version
All browsers
Expected Outcomes
Have a boolean indicator of deceased that indicates the banner as deceased.

Right now, the demographics banner provided by our previously library expected both a boolean and a date of death to display correctly. Given this, having a boolean in this API is extraneous. Let's close this issue.


#1017 Document test_utils.make_mocked_coro function

What do these changes do?

Added explicit documentation for test_utils.make_mocked_coro function.
Are there changes in behavior for the user?

Better documentation.
Related issue number

#1017
Checklist

[x] I think the code is well written
[x] Unit tests for the changes exist
[x] Documentation reflects the changes

Current coverage is 98.06% (diff: 100%)

Merging #1113 into master will not change coverage

@@             master      #1113   diff @@
==========================================
  Files            28         28
  Lines          6368       6368
  Methods           0          0
  Messages          0          0
  Branches       1070       1070
==========================================
  Hits           6245       6245
  Misses           64         64
  Partials         59         59

Powered by Codecov. Last update 03ca4a3...9d9a57c


Docerina does not support for Ballerina Services  - (API Documentation)

Description:
Docerina does not support for generateing API documentation for Ballerina services. However while executing a "ballerina doc" command API documentation is generated in HTML format but content of that document is empty for Ballerina services.
Steps to reproduce:
Please find the following recreation steps

Create a simple Ballerina service.
Then  insert API documentation annotations for above service.
Run "ballerina doc" command.

Output
API documentation generated successfully. But content is empty.
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

This is also not working with the syntax changes by https://github.com/ballerina-platform/ballerina-lang/pull/10041 and needs to be fixed.

Refer mail: https://groups.google.com/d/msg/ballerina-dev/wK1UPRrE4Hk/TRELPLY7AQAJ


The DNS-rebind check is not triggering when no hostname is supplied.

Describe the bug
It seems that the DNS-rebinding option is not working correctly when no hostname has been supplied. I have set my DNS-rebinding to the host xxx.mydomain.com but visiting from my WAN-ip I can still access the OPNSense-GUI. Visiting from other domains seems to still trigger the DNS-rebinding.
I'm 100% sure this issue was not existing in a previous version of OPNSense.
To Reproduce
Steps to reproduce the behavior:

Enable DNS-rebinding.
Visit your Router from the IP-directly without supplying a hostname.
DNS-rebinding has been bypassed successfully.

Expected behavior
That DNS-rebinding also works when a user did not supply any hostname.
Software version used and hardware type if relevant, e.g.:
OPNsense 24.7.11_2-amd64

These parts haven't been changed in over 2 years, looking at the code, it seems to be doing what it should (ignore ip addresses when validating for hostnames).
https://github.com/opnsense/core/blob/752795a22996eddbe8dcef88298555d83f12ce9b/src/www/authgui.inc#L96-L97


The scanner does not respect the language of the phone

The scanner does not respect the language of the phone.
If a product is available in English and Spanish, with English as the main language, but Spanish as the language of the app, the product will be displayed in English.
The app should display the product in Spanish.

@teolemon Yes, the scanner does not respect the language of the phone, because it's depends on the app language. Whatever the language of the phone is, the app will always follow it's own language. But what we can do is, at the time of first time opening of the app, we run this line "Locale.getDefault().getDisplayLanguage();" to get the device language and set it as default of the app language.
For example when the app is first run in the phone and the phone language is Espanol we get the device language and set the same in the app. Afterwards whatever the user changes the language of the app, it's his/her choice.
And the product is displayed according to the app language. See screenshots.


Conflict between numpy and tetgen

When run the hello Genesis, get the following error:
tetgen._tetgen
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

Following the instructions, the env default numpy and tetgen version is:

tetgen == 0.6.4
numpy == 1.26.4

It seems work when downgrade NumPy to version 1.24.0

Hmm...weird. We tested on the exact same versioning (tetgen==0.6.4 and numpy==1.26.4) and there is no error.  Also, a fresh install of the two packages and no issue (even using different machines ubuntu 22.04 and 20.04). Another random test with a combination of tetgen==0.6.5 and numpy==2.1.1, and it worked (side note: not recommending numpy 2 though as I remember there are some issues -- not 100 positive).
Not sure if this matters but what python version are you using and how did you set up your environment?

Have the same issue.
Distro: Manjaro, kernel 5.10.226
Virtual env manager: mamba 1.5.5, conda 23.11.0
Pip: 24.3.1
Python: 3.12
numpy: 1.26.4, channel pypi
tetgen: 0.6.4, channel pypi
Tried install numpy==1.24.0, but genesis-world requires 1.26.0

Have the same issue.
Distro: Ubuntu 22.04.05
Virtual env manager: conda 24.5.0
Pip: 24.3.1
Python: 3.10
numpy: 1.26.4, channel pypi
tetgen: 0.6.4, channel pypi
Does not work with numpy 1.24.0, error:
Traceback (most recent call last):   File "/mnt/ssd1/ProvingGrounds/genesis/helloworld.py", line 1, in <module>     import genesis as gs   File "/home/user/anaconda3/envs/genesis/lib/python3.10/site-packages/genesis/__init__.py", line 262, in <module>     from .utils.geom import *   File "/home/user/anaconda3/envs/genesis/lib/python3.10/site-packages/genesis/utils/geom.py", line 4, in <module>     from scipy.spatial.transform import Rotation   File "/home/user/anaconda3/envs/genesis/lib/python3.10/site-packages/scipy/spatial/__init__.py", line 110, in <module>     from ._kdtree import *   File "/home/user/anaconda3/envs/genesis/lib/python3.10/site-packages/scipy/spatial/_kdtree.py", line 4, in <module>     from ._ckdtree import cKDTree, cKDTreeNode   File "_ckdtree.pyx", line 11, in init scipy.spatial._ckdtree   File "/home/user/anaconda3/envs/genesis/lib/python3.10/site-packages/scipy/sparse/__init__.py", line 294, in <module>     from ._csr import *   File "/home/user/anaconda3/envs/genesis/lib/python3.10/site-packages/scipy/sparse/_csr.py", line 11, in <module>     from ._sparsetools import (csr_tocsc, csr_tobsr, csr_count_blocks, ImportError: numpy._core.multiarray failed to import

install torch first with pip and pip uninstall numpy, then install gensis. This works for me

install torch first with pip and pip uninstall numpy, then install gensis. This works for me

This works for me as well. My env version is also tetgen==0.6.4 and numpy==1.26.4.

install torch first with pip and pip uninstall numpy, then install gensis. This works for me

Thanks for the reply, maybe the installation order matters, cause my env install genesis first

install torch first with pip and pip uninstall numpy, then install gensis. This works for me

Thanks，it works for me.

install torch first with pip and pip uninstall numpy, then install gensis. This works for me

Yes! Thanks for your answer. This is also work for me.


how to show AtomNumbers and atom symbols in the image?

Configuration:

RDKit Version: 2020.03
Operating system: linux
Python version (if relevant): 3.7
Are you using conda? yes
If you are using conda, which channel did you install the rdkit from? rdkit
If you are not using conda: how did you install the RDKit?

Description:

how to show AtomNumbers and atom symbols in the image?

mol = Chem.MolFromSmiles('COc1ccc(Cn2nc(CN3CCN(c4ccccc4OC)CC3)c3cc(OC)c(OC)cc32)cc1OC')
options = Draw.DrawingOptions()
options.dotsPerAngstrom = 50
max_size=(1000, 1000)
options.includeAtomNumbers=True
img =Draw.MolToImage(mol,size=max_size,options=options,highlightColor=[0,0,0],highlightBonds=list(range(100)))
TrimImgByWhite(img)

atom symbol is  not in the image.
mol = Chem.MolFromSmiles('COc1ccc(Cn2nc(CN3CCN(c4ccccc4OC)CC3)c3cc(OC)c(OC)cc32)cc1OC')
options = Draw.DrawingOptions()
options.dotsPerAngstrom = 50
max_size=(1000, 1000)
options.includeAtomNumbers=False
img =Draw.MolToImage(mol,size=max_size,options=options,highlightColor=[0,0,0],highlightBonds=list(range(100)))
TrimImgByWhite(img)

atom numbers is  not in the image.

Hi @autodataming : you do this by creating a MolDraw2DOptions object and passing that to MolToImage():
dos = Draw.MolDrawOptions()
dos.addAtomIndices=True
Draw.MolToImage(m,options=dos)

Produces:

More about the options is available in a recent blog post:
http://rdkit.blogspot.com/2020/04/new-drawing-options-in-202003-release.html

I'm closing this because it looks like the question is answered. Please reopen if necessary.


Fix Kernel.defaults signature

The current signature defines that the method returns a partial contract while in fact it returns a full contract with only the ID undefined.
Unfortunately this is a major change as it is necessary to change the generic arguments.
Change-type: major
Signed-off-by: Carol Schulze<EMAIL_ADDRESS>

@balena-ci I self-certify!


stan is an (empty) package on PyPI

People may be confused and try to pip install stan. stan was claimed on Nov 18, 2018. But there seems to be nothing there. We might try sending a nice email to the owner asking for the name. The owner's name is in the setup.py of the (empty) package.

There is also a possibility to ask PyPI for that name, but I'm not sure what is the correct procedure in these cases.
pip install stan would allow us to keep pystan (2.x) and pystan3 (3.x) separable, if that is something we want to do.

We can ask for the name stan. Someone just needs to write a nice email
to the package owner.
As for having a different package for PyStan 3, I'm not sure there's a
good reason for this. Package isolation with virtualenv is good and
getting better (see current discussions about pypackage). And I have
no interest in maintaining an older version of pystan for longer than is
strictly necessary. And having two packages would potentially hint that
the two packages would be maintained separately.
On 3/12/19 5:29 PM, Ari Hartikainen wrote:

There is also a possibility to ask PyPI for that name, but I'm not sure
what is the correct procedure in these cases.
|pip install stan| would allow us to keep pystan (2.x) and pystan3 (3.x)
separable, if that is something we want to do.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/pystan-next/issues/58#issuecomment-472188648,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmFA1sR1F7JNPOaXxcxxhMBEl8RCqo25ks5vWBwggaJpZM4ZklUQ.


firebase_admob 0.9.0 crashes Android

verbose flutter run gives only the following cryptic error:
[ +145 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=xxx.xxx.app/.MainActivity (has extras) }
[        ] Waiting for observatory port to be available...

@willvlad what the device do you use to test? Please provide your flutter doctor.
Did you manage to solve it? Does it happen on new projects as well?

Hi @willvlad
for what I can see the issue is related to a FlutterFire plugin,
please open the issue in the dedicated github.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
thank you


Update pom v2

Actually exclude pentaho this time

Pull Request Test Coverage Report for Build 414

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

Totals

Change from base Build 412:
0.0%

Covered Lines:
653

Relevant Lines:
855

💛  - Coveralls


NU5 Tracking: The Spec

This epic will track the tasks that need to happen somewhere in code in order to implement Zcash Orchard and the other NU5 ZIPs in Zebra, as defined by the Zcash Specification.
This may include pieces of code contributed to the https://github.com/zcash/orchard crate or https://github.com/zcash/halo2 crate, by the zebrad team or the zcashd or whomever, but they need to happen by someone.
This tracking issue contains segments for the whole spec that includes Orchard changes for now. A checkbox means that that part of the specification describes something to implement.
A checked box or strikethrough means that we:

have implemented that item
are tracking that item in another Epic, or
have otherwise resolved that item.

Our mandatory Canopy checkpoint significantly reduces the number of features that we have to implement.
Leaf nodes are marked by – and correspond to implementable items. They should be followed by issue references that track the status of that issue, or a short explanation. Some pieces of the spec that pertain to sending or receiving money or blockchain scanning are noted here, but not linked to issues, as we are not doing that work for Zebra for NU5 activation.

~1. Introduction~ – nothing implementable
~2. Notation~ – nothing implementable
[x] 3. Concepts

[x] 3.1. Payment Addresses and Keys – #1864
[x] 3.2. Notes – #1864

[x] 3.2.1 Note Plaintexts and Memo Fields – #1864?

~3.4. Transactions and Treestates~ (covered by #958 which is tracked under #1872)
[x] 3.7. Action Transfers and their Descriptions – #1864
[x] 3.8. Note Commitment Trees – #1864
[x] 3.9. Nullifier Sets – ~#1864~ #2230 #2231

[x] 4. Abstract Protocol

[x] 4.1. Abstract Cryptographic Schemes

~4.1.1. Hash Functions~ – pull as dependencies
~4.1.2. Pseudo Random Functions~ – pull as dependencies
~4.1.3. Pseudo Random Permutations~ - (will be done as part of the zebra-client work)
[x] 4.1.6. Key Derivation -  #2044, #2080 (not required for NU5 validation)
[x] 4.1.7. Signature - #?
[x] 4.1.8. Commitment – #1864?
[x] 4.1.11. Group Hash – ?
~4.1.13. Zero-Knowledge Proving System~

[x] 4.2. Key Components

[x] 4.2.3. Orchard Key Components – #1864?

~4.4. Spend Descriptions~ (covered by ZIP-216/#1798 which is tracked under #1854)
~4.5. Output Descriptions~ (covered by ZIP-216/#1798 which is tracked under #1854)
[x] 4.6. Action Descriptions – #1864?
4.7. Sending Notes

~4.7.2. Sending Notes (Sapling)~ - (will be done as part of the zebra-client work)
~4.7.3. Sending Notes (Orchard)~ - (will be done as part of the zebra-client work)

~4.8. Dummy Notes~ - probably doesn't exist in the wild yet

~4.8.2. Dummy Notes (Sapling and Orchard)~

~4.9. Merkle Path Validity~ (covered by #958 which is tracked under #1872)
~4.10. SIGHASH Transaction Hashing~ (covered by ZIP-244 which is tracked under #1854 )
~4.13. Balance and Binding Signature (Sapling)~ (covered by #1829 which is tracked under #1854)
[x] 4.14. Balance and Binding Signature (Orchard) - pool: #1895,  #1980, #1939, #2102
~4.15. Spend Authorization Signature (Sapling and Orchard)~ - (will be done as part of the zebra-client work)
[x] 4.16 Note Commitments and Nullifiers – ~#1911~ #2230 #2231
[x] 4.17. Zk-SNARK Statements

[x] 4.17.4. Action Statement (Orchard) – #1912

~4.19. In-band secret distribution (Sapling and Orchard)~ (will be done as part of the zebra-client work)

~4.19.1. Encryption (Sapling and Orchard) - #2041~ (will be done as part of the zebra-client work)
~4.19.2. Decryption using an Incoming Viewing Key (Sapling and Orchard) ~ #2231
~4.19.3. Decryption using a Full Viewing Key (Sapling and Orchard)~

~4.21. Block Chain Scanning (Sapling and Orchard)~ nothing to do here?

[x] 5. Concrete Protocol

5.3. Constants
[x] 5.4. Concrete Cryptographic Schemes

[x] 5.4.1. Hash Functions

[x] <IP_ADDRESS>. Merkle Tree Hash Function – #1864
[x] <IP_ADDRESS>. DiversifyHash Hash Function – #1864 ?
[x] <IP_ADDRESS>. Sinsemilla Hash Function –#1864, #2079
~<IP_ADDRESS>. PoseidonHash Function -  #2064~ - (will be done as part of the zebra-client work)

[x] 5.4.2. Pseudo Random Functions - #1864?
~5.4.3. Authenticated One-Time Symmetric Encryption~
[x] 5.4.4. Key Agreement and Derivation

[x] <IP_ADDRESS>. Orchard Key Agreement - #1864? (pull in generic reddsa?)

[x] 5.4.6. RedDSA, RedJubjub, and RedPallas – #1864?

[x] <IP_ADDRESS>. Spend Authorization Signature - #?
[x] <IP_ADDRESS>. Binding Signature - #?

[x] 5.4.7. Commitment Schemes

[x] <IP_ADDRESS>. Homomorphic Pedersen Commitments – #1864
[x] <IP_ADDRESS>. Sinsemilla commitments - #1864, #2079

[x] 5.4.8. Represented Groups and Pairings

[x] <IP_ADDRESS>. Pallas and Vesta - #1864
[x] <IP_ADDRESS> Hash Extractor for Pallas - #1864 ?
[x] <IP_ADDRESS>. Group Hash into Pallas and Vesta - #1864 ?

[x] 5.4.9. Zero-Knowledge Proving Systems

[x] <IP_ADDRESS>. Halo 2 - #1864 (as a wrapping/parsing type) and also tracked under #1853 in #2104

[x] 5.5. Encodings of Note Plaintexts and Memo Fields – #1864
[x] 5.6 Encodings of Addresses and Keys - #1864

[x] 5.6.4 Unified and Orchard Encodings - #1864

~<IP_ADDRESS> Unified Payment Addresses~ - (will be done as part of the zebra-client work)
[x] <IP_ADDRESS> Orchard Raw Payment Addresses - #1864
[x] <IP_ADDRESS> Orchard Incoming Viewing Keys - #1864
[x] <IP_ADDRESS> Orchard Full Viewing Keys - #1864
[x] <IP_ADDRESS> Orchard Spending Keys - #1864

~6. Network Upgrades~ (tracked by #1854)
[x] 7. Consensus Changes from Bitcoin

[x] 7.1. Transaction Encoding and Consensus #1917, #1980, #1981, #2103, #2105

v5 transactions are ZIP-225, which is covered by #1863 and tracked under #1854

[x] 7.3. Spend Description Encoding and Consensus - #1864 ?
[x] 7.4. Output Description Encoding and Consensus - #1864 ?
[x] 7.5. Action Description Encoding and Consensus - #1864 ?

Also remember that consensus ZIPs are part of the spec

@dconnolly @mpguerra where's the ticket that tracks: "Pre-NU5 spec sections still active in Canopy or NU5, which Zebra hasn't implemented yet" ?

@dconnolly I started adding #1864 to some of the spec sections, can you please review these?
Also, do we need to create an "Orchard Key Agreement and KDF" issue similar to #271 and/or an issue to "Implement Orchared shared secret key derivation" similar to #301 ?

For "4.1.6. Signature" do we need to create an issue for Pallas signatures?

For "4.1.10 Group Hash" are we going to pull in as a dependency?

For "4.7.2. Sending Notes (Sapling and Orchard)", do we need to create an new issue to implement Orchard note encryption and decryption similar to #181 and #269?

For "4.7.2. Sending Notes (Sapling and Orchard)", do we need to create an new issue to implement Orchard note encryption and decryption similar to #181 and #269?

We need to do this eventually for when we are sending money via Orchard but not for 'just' Zebra's NU5 chain validation. So yes we need to create the ticket but it does not have to be completed yet.

For "4.1.10 Group Hash" are we going to pull in as a dependency?

I think this is completed in #1864, under the hood it uses the pallas_curves dependency

Do we need to create an issue for " 4.9. Merkle Path Validity" also?

For "4.1.6. Signature" do we need to create an issue for Pallas signatures?

Yes I think so. I am stubbing out similar types to RedJubjub in that branch #1864 just to have the types, but I  not sure yet if we just want to port redjubjub to Pallas, or great a generic RedDSA variant, or what, do I'm delaying the decision 🙈

@dconnolly I don't see any changes for NU5 in  <IP_ADDRESS>. CRHivk Hash Function, but I see them in <IP_ADDRESS> instead.
If that's correct, I will move the work in <IP_ADDRESS> into #1872 for the Pre-NU5 spec work

I think that is correct, yes

For "4.1.6. Signature" do we need to create an issue for Pallas signatures?

Yes I think so. I am stubbing out similar types to RedJubjub in that branch #1864 just to have the types, but I  not sure yet if we just want to port redjubjub to Pallas, or great a generic RedDSA variant, or what, do I'm delaying the decision 🙈

As a reminder, I have already created a (semi-)generic reddsa from the redjubjub crate; it is what I'm using in the orchard crate.

Do we need to create an issue for "4.14. Balance and Binding Signature" ?

Do we need to create an issue for "<IP_ADDRESS>. Halo 2" similar to #305?

Do we need to create an issue for "4.14. Balance and Binding Signature" ?

Pool balance is #1895, but we still need to create (or find) tickets for the rest.

There are a significant number of transaction consensus rules in 7.1 that aren't covered by ZIP-225 or the v5 transaction RFC.
I'd like to track those changes in separate tickets, because the v5 transaction RFC is already quite large, and we need to finish it off soon.

Note that some of the section numbers in the spec changed as a result of inserting section 4.1.3 Pseudo Random Permutations.

Updated section "5.6.4 Unified and Orchard Encodings"  with "<IP_ADDRESS> Unified Payment Addresses"

Added #2064 to section "<IP_ADDRESS> PoseidonHash Function" and Epic

@dconnolly:  Is "4.14. Balance and Binding Signature (Orchard)" fully covered by ZIP-209/#1895 ? If so, we can cross it out from this list

Looks like we are done here 🎉


Update Get-DbaCmObject.ps1 to correct tu/to typo

Update Get-DbaCmObject.ps1 to correct tu/to typo on line 20

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[x] Documentation
[ ] Build system

Purpose

Approach

Commands to test

Screenshots

Learning

looks good 💯  thank you!


markdown support for operator io label, description, and caption

What changes are proposed in this pull request?

Add support for using markdown in operator IO's label, description, and caption
Add support for using markdown is AlertView

How is this patch tested? If it is not, please explain why.
Using a test operator
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[x] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

See above
What areas of FiftyOne does this PR affect?

[x] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Summary by CodeRabbit

New Features

Introduced a new Markdown component to render markdown content with enhanced features like syntax highlighting and custom styling.
Updated AlertView and Header components to render labels, descriptions, and captions using the new Markdown component for improved readability.
Enhanced MarkdownView component to support conditional rendering based on provided schemas and data.

Tested this and all seems well. Note that I had to use textwrap.dedent to get the whitespace right:
outputs.define_property(
            "images",
            types.List(types.String()),
            label="Images `code`",
            description=textwrap.dedent("""
            This is a list of images. The images are displayed as a list!

            - foo
            - bar

            ```ts
            js.blah()
            ```
            Foo"""),
            view=types.ListView(items=types.ImageView()),
        )


Revert "Fix Top left host name display malfunction and Fix style.css"

Reverts xiaoqingfengATGH/luci-theme-infinityfreedom#13

@xiaoqingfengATGH, The original #13 PR was only intended to fix the Host Name problem just as commit 34783ef did, however it seems that GitHub was malfunctioning and thrown a lot of my personal editions for my own use to this PR, and it just ends up like this. Thus I gonna try to address this problem and raise a new PR if you want it.

@xiaoqingfengATGH Okay My bad, I've forgotten to rename the my personal audit branch and mistakes it into the master PR branch, my bad again.


Answer editor is not updated

If I edit an answer the date & author info are not updated
i.e edited question may the 15th que faire

See #18. :)

Oh #18 is about questions. Sorry. :)

Thank you for the submitting this issue.
We plan to add an "history log" of changes made to the question or its answer, by whom and when.
Currently, the user associated should be seen as "The first user who answered this question"


linuxPackages_custom does not compile linux with parallelism

Issue description
Despite of nix.buildCores being set to 16 or 0, kernel make is run with -j1 explicitly when a custom linux kernel is specified.
Steps to reproduce
Set
  boot.kernelPackages = pkgs.linuxPackages_custom {
    version = "4.11.0-rc8";
    src = pkgs.fetchurl {
      url = "mirror://kernel/linux/kernel/v4.x/testing/linux-4.11-rc8.tar.xz";
      sha256 = "acda201845186cb347b036f23f9bea4990f03f4f604e3bf30837284d99567348";
    };
    configfile = /etc/nixos/kernel.config;
  };

  nix.maxJobs = 16;
  nix.buildCores = 0;

and run sudo nixos-rebuild switch. Observe the make -j being run.
Technical details

System: 17.09pre105622.f0fac3b578 (Hummingbird)
Nix version: nix-env (Nix) 1.11.8

ping @thoughtpolice @joachifm
Is it possible to fix commonMakeFlags in manual-config.nix?
It takes so long with the current -j1.

Looks like this was fixed by https://github.com/NixOS/nixpkgs/pull/31887. Please reopen if that is not the case.


(bugfix): reduce frequency of update requests for copied CSVs

Description of the change:
Reduces the frequency of update requests for copied CSVs by:

Adding the olm.operatorframework.io/nonStatusCopyHash annotation to the copied CSVs, populated with a hash of all the non-status fields of the original CSV.
Adding the olm.operatorframework.io/statusCopyHash annotation to the copied CSVs, populated with a hash of all the status fields of the original CSV.
Updating the above annotations as necessary on the copied CSVs when changes are made to the original CSV

This appears to have been the desired behavior of this function, as evidenced by: https://github.com/operator-framework/operator-lifecycle-manager/blob/461018e2e232865d97830b3accad9f1e8a58c7bc/pkg/controller/operators/olm/operatorgroup.go#L829-L830
The problem with the previous implementation was that these annotations were never set on the copied CSVs.
Motivation for the change:

Reduce the frequency of UPDATE requests made to the Kubernetes API Server for copied CSVs

Architectural changes:

Testing remarks:

Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Bug fixes are accompanied by regression test(s)
[ ] e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
[ ] tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
[ ] Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive
[ ] Tests marked as [FLAKE] are truly flaky and have an issue
[ ] Code is properly formatted

Those annotations were set on the CSVs in the informer's cache when the hash comparison was introduced (https://github.com/operator-framework/operator-lifecycle-manager/commit/cf618d3e89a2ba4ade3c50cbb03ff37795a3e5fb). The observation was that CSV copies needed to be written if and only if the copy was out of sync with the original, so caching a pruned object with a hash was much cheaper than caching complete objects while still being able to stomp CSV copies at the appropriate times. This seems to have regressed as part of https://github.com/operator-framework/operator-lifecycle-manager/pull/3003.

@benluddy I think we want to push ahead with this PR for a couple reasons:

reverting #3003 would be difficult at this late date because it had follow-on work AND we need the memory reduction.
there have not been any OLM users noticing the introduced problems from #3003
this PR suppresses sending anything to the API server when annotations appear, which does help out users who have noticed the increased activity.

there have not been any OLM users noticing the introduced problems from https://github.com/operator-framework/operator-lifecycle-manager/pull/3003

You should find with this PR that you can issue a write to a copied CSV that puts it out of sync with the original CSV, and this control loop will not bring the copy back into sync with the original.

there have not been any OLM users noticing the introduced problems from #3003

You should find with this PR that you can issue a write to a copied CSV that puts it out of sync with the original CSV, and this control loop will not bring the copy back into sync with the original.
Edit: I am a little confused by this response. Isn't this PR an attempt to fix a problem that was both reported by a user and introduced by the linked PR?

@benluddy I think what @bentito is trying to say is that we have received no complaints from users about the bug you called out specifically related to writes to a copied CSV, without changing the annotation, would not be reverted.
My understand of the current plan, and I may be a tad out of the loop due to hurricane preparations, is:

Merge this PR to fix a critical bug causing users higher logging costs and load on the API server
If bug reports come in regarding copied CSV writes not being reverted, investigate how to resolve that

I agree that reverting #3003 is the right approach to fix both the critical bug and the bug you called out that was introduced by the use of the PartialObjectMetadata informer. There are folks with concerns about reverting that change because we needed the performance gain to enable folks running on the edge to be able to use OLM. Reverting #3003 is probably still the best thing to do and identify a way to still achieve enough performance gain for the edge use cases, but the priority is being placed on resolving the update 100% of the time ASAP and the consensus of the current maintainers seems to be that this PR is what allows us to achieve that and give us some breathing room to re-assess.
I know it isn't a great answer, but hopefully this gives some insight as to the decisions the team has made re: continuing with this PR.

@everettraven I don't think Ben is suggesting that we revert https://github.com/operator-framework/operator-lifecycle-manager/pull/3003, I think he is suggesting that we don't introduce another regression on top of the previous one as a fix. With this change, I think we are putting ourselves in a situation where we are going to ignore spec changes in the copied csvs, which I'm pretty sure are considered in resolution.

@kevinrizza The regression is technically caused by #3003 . We just would realize it in this PR because we add the annotations back that prevent updating 100% of the time.
That being said, maybe I'm missing that there is a different way to do this?

Thinking about this a bit more, maybe we can remove the hash annotation and always calculate the hash of the copied CSV and compare that?

Seems likely that some of the observed memory reductions over caching pruned CSVs might have come from reducing the high watermark transient allocations from decoding a big list response (unlike CSVs, or any CRD-backed resource, a PartialObjectMetaList can be encoded as Protobuf and not only JSON).

EDIT: This isn't possible without reverting https://github.com/operator-framework/operator-lifecycle-manager/pull/3003 because the lister returns a PartialObjectMeta which doesn't contain spec or status information

Right, without the full object, the copy loop can't see all the fields that might have diverged from the original. The metadata.generation field is automatically incremented for all CRs on updates that change non-metadata fields (https://github.com/kubernetes/kubernetes/blob/d9c46d8ecb1ede9be30545c9803e17682fcc4b50/staging/src/k8s.io/apiextensions-apiserver/pkg/registry/customresource/strategy.go#L185) so you might be able to keep track of the last observed generation per copy with only metadata available. The only problem would be that the status subresource is enabled on the CSV CRD, so status updates don't cause metadata.generation to be incremented.


bug: revision doesn't transition from root to child pom files

I've been getting this bug, which I think happens because, somehow, the property revision doesn't transition from parent to child pom files.
[ERROR] Failed to execute goal fr.inria.gforge.spirals:repair-maven-plugin:1.6-SNAPSHOT:npefix (default) on project commons-collection: Execution default of goal fr.inria.gforge.spirals:repair-maven-plugin:1.6-SNAPSHOT:npefix failed: Plugin fr.inria.gforge.spirals:repair-maven-plugin:1.6-SNAPSHOT or one of its dependencies could not be resolved: Failed to collect dependencies at fr.inria.gforge.spirals:repair-maven-plugin:jar:1.6-SNAPSHOT -> fr.inria.repairnator:repairnator-core:jar:3.3-SNAPSHOT: Failed to read artifact descriptor for fr.inria.repairnator:repairnator-core:jar:3.3-SNAPSHOT: Failure to find fr.inria.repairnator:repairnator-root:pom:${revision} in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

This concrete error is from testing maven-repair on lang304. To reproduce:
❯ cd repairnator/
❯ mvn clean install -DskipTests
❯ cd npe-dataset/lang-304/
❯ mvn clean test -DtrimStackTrace=false
❯ mvn fr.inria.gforge.spirals:repair-maven-plugin:npefix

I've been hard-coding the version and replacing ${revision} as a work-around, but this should not be necessary.
Now comes the interesting part. @cokefh wasn't able to reproduce this bug (nor the one from #1153 ), while both in my laptop and desktop they occur (almost exact environment between both).
I've tried deleting my local .m2 and using a clean git project, but nothing changed. I also didn't find anything online mentioning this bug.
Information about my desktop setup:
❯ uname -a
Linux alan 5.9.11-arch2-1 #1 SMP PREEMPT Sat, 28 Nov 2020 02:07:22 +0000 x86_64 GNU/Linux

❯ java -version
java version "1.8.0_271"
Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)

❯ mvn -version
Apache Maven 3.6.3 (NON-CANONICAL_2019-11-27T20:26:29Z_root)
Maven home: /opt/maven
Java version: 1.8.0_271, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-jdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.9.11-arch2-1", arch: "amd64", family: "unix"

Just tested in a Ubuntu VM and the same error happened.
$ uname -a
Linux ubuntu20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ java -version
java version "1.8.0_271"
Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)

$ mvn -version
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 1.8.0_271, vendor: Oracle Corporation, runtime: /usr/lib/jvm/jdk1.8.0_271/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-42-generic", arch: "amd64", family: "unix"

It's an odd one. I will try with a Ubuntu VM on my mac to run it also.


Ecds config dump recommit

ECDS config dump is initially committed by #23902 .
#23902 is later on reverted by #24354 due to a few lines of code is not tested #24362.
This PR reverted #24354 to reinstall #23902 also added the changes of #24362 in.
Please check the original code review history of #23902 for details.

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/lgtm api
Removing lines of comments to fix coverage seems to be the wrong thing to do, so I'd personally say that reducing the coverage threshold is better. Leaving it up to the senior maintainers to weigh in. Other than that, LGTM!

Agreed.  I think we should modify the CI scripts to fix this line-coverage counting issue on comments.
I removed the comments anyway since those two lines of comments are a little bit unnecessary since the code tells it all.
The real change is the early return in case admin doesn't have value.  BTW, the line coverage report in the failed case is below:
https://storage.googleapis.com/envoy-postsubmit/main/coverage/source/common/filter/config_discovery_impl.h.gcov.html

Thanks for taking care of the coverage.

Thanks for taking care of the coverage.

Thanks for approval!


A car has more than 1 seat usually

Challenge Construct JavaScript Objects with Functions has an issue.
Please describe how to reproduce this issue, and include links to screenshots if possible.
I would change the numbers of seats for the object "car" to 5, as per the previous challenge.
Original text:

var Car = function() {
  this.wheels = 4;
  this.engines = 1;
  this.seats = 1;
};

// Only change code below this line.

var MotorBike = function() {

};

Prefered text:
```javascript

var Car = function() {
  this.wheels = 4;
  this.engines = 1;
  this.seats = 5;
};

// Only change code below this line.

var MotorBike = function() {

};

@JonathanScher agreed. A typical car usually has five seats, unless we're talking about the Tango T600 😆
This line in the seed code, this line in the instructionsand this line in the solution all need to be changed to be this.seats = 5;
To contributors, please first read the contributing guidelines before taking care of this issue. And feel free to visit the Contributors Help chat room if you have any questions about helping. We're there to help.

K just submitted a PR and fixed this.

I am working on this issue.

@astuter unfortunately, someone else had already made a PR after yours. If you're still interested in contributing, you can check out issues with "Help Wanted". Feel free to visit the Contributors Help chat room if you have any questions about helping. We're there to help.


Added A Project Description

-Added description to the top of the file to explain what Amplify does.
-Added a description to the video for the first video to clarify the purpose

Thank you for your guidance, Param!


Use Text.rich rather than RichText

Text.rich handles selection and text scaling for you automatically.
Fixes #70

Hey @amake, was just about to do a PR for this, here is a correction you need to make, RichText and Text.rich are more or less the same and both don't have selection, you should rather change the Text.rich to SelectableText.rich, Cheers👍.

RichText and Text.rich are more or less the same and both don't have selection, you should rather change the Text.rich to SelectableText.rich

Please read my comment on #70. SelectableText.rich is not the right thing to use here.

Should have read the entire issue and not just the title before I commented, it makes sense to make it optional, well thought.
Let's hope they merge it soon, package looks abandoned, how ironic 👀


Blif parsing fixes

This branch fixes 6 crash bugs that were discovered with American Fuzzy Lop, and adds test cases for each bug.
To aid the editing of blif.cc, the tab characters have been substituted with spaces. Would it be possible to replace the tabs with either all tabs, or all spaces throughout the project? The auto-replacement-of-8-spaces-with-tabs convention is quite unusual, and is often difficult to configure editors to conform to the convention.

This is fantastic work, thanks!  I will merge it in as soon as travis finishes.  I agree about spaces vs tabs.  I will convert everything to spaces.

Cool. I started another test run this morning, this time with ASAN built in, and its picked up a couple more bugs. I'll leave it running for a few days and see what else it digs up.

Awesome.  I started a run on the pcf input and found one bug so far.  I committed my afl testcases and a fuzz-pcf make target.  Feel free to submit a pull request for something similar for blif.  Curious, did you create a blif dictionary?

@cseed Ok cool. I was going to test the PCF myself.
I found results were quite slow to obtain in the main application - because the first thing arachne-pnr does on startup is parse the chipdb which takes a large fraction of a second on my PC. Therefore, I've been running the tests with the BLIF parser and data model classes extracted into a test executable - doing this gets the execution speed up to ~500 runs/second. At this rate, bugs come in at a much more reasonable rate - though obviously it's not going to find bugs in the router.
I was thinking it might be a good idea to sequence the chipdb loading after parsing the BLIF, and maybe the PCF parsing - if possible. Failing faster would have benefits for normal users also.

@cseed Also, yes I do use a dictionary; nothing special, just the directives from the BLIF spec - I found it was somewhat beneficial. I think a better dictionary might have more realistic BLIF statements in it.

@jhol I saw remark in the afl perf-tips that the llvm instrumentation had a "persistent" mode for programs with high startup costs.  That might be worth looking into.
Cool.  I thought it might also be worthwhile to include the iCE40 primitive names (SB_DFF, etc.), too.
I agree about loading the chipdb later.  I'll make that change.  Most of the chipdb is the routing tables.  It might be worth loading the main chipdb first and the routing tables just before routing.  Maybe we could find bugs in pack or place that way.
I'm adding support for pnr scritps a bit like Yosys.  That will support things like parsing BLIF and existing without having modify the code.

@cseed - if you're looking at llvm instrumentation, I read that llvm integrated a fuzz testing algorithm inspired by AFL. Maybe both can be used together.

I was referring to this, from docs/perf_tips.txt:
3) Use LLVM instrumentation
---------------------------

When fuzzing slow targets, you can gain 2x performance improvement by using
the LLVM-based instrumentation mode described in llvm_mode/README.llvm. Note
that this mode requires the use of clang and will not work with GCC.

The LLVM mode also offers a "persistent", in-process fuzzing mode that can
work well for certain types of self-contained libraries, and for fast targets,
can offer performance gains up to 5-10x; and a "deferred fork server" mode
that can offer huge benefits for programs with high startup overhead. Both
modes require you to edit the source code of the fuzzed program, but the
changes often amount to just strategically placing a single line or two.

From a quick look at REAME.llvm, looks like we can load chipdb once and then iterate over test cases.


Windows permissions app/core/autoload

Hello!
I just was trying to install it on windows and error rose up.
Error: File core/app/autoload.php permissions are not set to 777. Please change them and refresh.
I think the main problem, is that a file can't be a 777 permission on Windows Systems.
On the core/html/install.html i'vs just change the line 10 just to bypass it.

Yeah, that's just a warning message to the user, but doesn't stop you from installing. Do you know the equivalent on a Windows machine so we can check the file either has 777 permissions or (windows equivalent)?

Hum... I think may you can not get this permission on windows. I think, maybe the right thing is just to check is able to write.
I couldn't continue installation. I had to change /core/html/install.html line 10 to that line

But i think is because another thing I've found. On my developing work machine my MySQL user is root without password. And as the password input was empty, the writer put into the file autoload.php:
$password = 'undefined';
I think this is because for the JS, the empty value is "undefined" and when it was sent to the server, the PHP red "undefined" as string.
To make work the installation I had to put an extra line on the install.php just to test it and finally work:
if ($password == 'undefined') $password = '';
I will continue exploring the cms.

The install.php in Linux does another error. If I put autoload to 777, the fopen do a
"Warning: fopen(core/app/autoload.php) [function.fopen]: failed to open stream: S’ha denegat el permís in /opt/lampp/htdocs/Cosmo/install.php on line 35"
In catalan, mean that have no permissions. Maybe something with PHP version? This is a 5.3.8
Quite strange because don't write nothing at all.

I think I fixed the 'undefined' issue, will be up in beta.4. Will work on the permissions issue next weekend.

Error: File core/app/autoload.php permissions are not set to 777. Please change them and refresh.
I think the main problem, is that a file can't be a 777 permission on Windows Systems.

But i think is because another thing I've found. On my developing work machine my MySQL user is root without password. And as the password input was empty, the writer put into the file autoload.php:
$password = 'undefined';

Confirm the both problems. Dear developers, please fix it.

Fixed the permissions issue too. Now it should just check if the file is writeable. Will make it into beta 4.


#6960 Queries returning Draft Content Items and with more tokens available

I developed this issue https://github.com/OrchardCMS/Orchard/issues/6960

It's changing the interface, it needs to target a major version -> dev branch

If I understand, you want your query filters to be able to use more tokens that the ones that are available in the request object. I don't see any usage of these tokens, does it mean you currently use the query API from your own module?

I call queries from a custom workflow element that I have no problem to share in another PR if you are interested in.
In the following screenshot you can see how I use a field in the current Content of the workflow that executes the query as parameter for that query:

We named the custom activity that executes a query: "Trigger From a Query" it triggers any signal we want for each content returned by the query we set. An example:

In that case we use that query to get the users to which we have to submit an email sending a signal per user. Then a signal activity catch that signal an send that email. In that way we are able to iterate through all the contents of a query to do an action with each result.

Is it interesting then? Do I create a new pull request to target dev branch?

Implemented in #7923 and #8112.


primary-site: update to include changes for ordered bag reading in inbox listener

Changelog

Description

BeforeAfter

I thought we only fixed ordered mcap reading not bag file reading?

🤦 yes, reworded description.


Bootstrap e2e testing

Overview
We need to bootstrap the system (Cypress?) and add a minimal amount of tests that ensures that the application works correctly

I think we need to investigate which library is the most suitable for testing electron apps. I guess we want to do our e2e tests on the dist app and not the browser. A quick glance to the Cypress docs shows that apparently we can use Cypress to test electron apps but in the Electron docs other options are suggested as well.

@pdelboca
@guergana
I don't think we really need to target electron except for a subset of tests (unless it's as easy/performant as for the browser version)
Cupress X Playwrite overview - https://medium.com/@mohsenny/deciding-between-cypress-and-playwright-a-comprehensive-guide-4d883d1be147

So what is your suggestion? Browser tests with Cypress? We just want to collect opinions.

Let's discuss it in the planning. I don't have extensive experience but I have always been thinking about Cypress as a primary option as well

A summary:
We have been playing around with WebdriverIO and a little bit of Selenium but with no success at all. So we should fallback to backend/frontend testing.
Testing WebApp vs Testing Electron
Initially I was hoping on being able to execute E2E testing on the Electron Application mainly for two reasons:

I have noticed several discrepancies in behavior between the browser vs the app.
Even if we can properly test the application, the bundle could not work.

However, we didn't find a way to make it work so we could move towards a more traditional web app E2E testing.
Note: Playright does not support testing AppImages either: https://github.com/microsoft/playwright/issues/14088


Updated SBS output to match Basestation

Updated the SBS socket output on ort 30003 to match the format output by Basestation.
Looking back at some old Basestation data, the SessionId, AircraftId and FlightId fields defaulted to 1 so these have been made consistent. The date fields have also been populated with the current system date and time.

Where is the GitHub Workflow build of this change?

Where is the GitHub Workflow build of this change?

I now see GitHub Workflow ran fine on your repo with the v143 change. I was a bit worried that would break the GW build.

Hi, glad you've seen the Workflow ran successfully; I ran out of time earlier to respond to your comment (I'm on EST this week ). I've only got v143 available right now so bumped the version too when I started working on the changes and it built without issue.
My existing client that consumes the Basestation data format has been running fine for a few days now, so this version of Dump1090 appears consistent with the Linux version output, as well as original Basestation (my client has worked with both over the years).
Thanks for porting it.

Merged. Thanks.


Exam Mode: Error when viewing test run summary

Describe the bug
Clicking on the "Summary" button of a finished Exam Test Run when there is a newly created Test Run causes an Internal Server Error.
To Reproduce

Create an exam
Start a Test Run and participate in it. Make sure to submit it.
Go to the Test Run page
Create a new Test Run
Click on the Summary page of the first Test Run
Get an Internal server error

Expected behavior
The Summary should open normaly, without an error
Screenshots

Which version of Artemis are you seeing the problem on?
7.3.1
What browsers are you seeing the problem on?
Chrome
Additional context
Found during the exam mode testing session
Relevant log output
error:
- detail: "Query did not return a unique result: 2 results were returned"
- message: "error.http.500"
- path: "/api/courses/90/exams/163/student-exams/grade-summary"
- status: 500
- title: "Internal Server Error"
- type: "https://www.jhipster.tech/problem/problem-with-message"

resolved in #8974


Error: need this for create of type Ref!(Image)(in long width, in long height, in bool use_mipmaps, in Format format)

On build, I get this:
"Error: need this for create of type Ref!(Image)(in long width, in long height, in bool use_mipmaps, in Format format)"
The line in question is:
Image image = Image.create(1280, 720, false, Image.Format.formatRgb8);
(Image.createFromData does the same thing)
Any idea what I am doing wrong?
OS: Ubuntu 22.04.3 LTS
Godot 4.1.2
dmd: v2.105.2

Just looked up the extensions API and these two methods are indeed must be static.
It seems we have an issue with static methods in generator right now, I'll try to fix this tomorrow.
As a quick workaround you should be able to use it by manually editing the implementation (classes/godot/image.d around line 468) to something like this (notice the static and and a new temporary field.
This code is not tested though.
static Ref!Image create(long width, long height, bool use_mipmaps, in Image.Format format) {
    if (!GDExtensionClassBinding.method_create.mb) {
        StringName classname = StringName("Image");
        StringName methodname = StringName("create");
        GDExtensionClassBinding.method_create.mb = gdextension_interface_classdb_get_method_bind(cast(GDExtensionStringNamePtr) classname, cast(GDExtensionStringNamePtr) methodname, 986942177);
    }
    godot_object _godot_object;
    return ptrcall!(Image)(GDExtensionClassBinding.method_create, _godot_object, cast() width, cast() height, cast() use_mipmaps, cast() format);
}

I did add that and it fixed the compile time error. However, on running, when it gets to this line in my code:
Image image = Image.create(1280, 720, false, Image.Format.formatRgb8);
It exits at run time with:
src/rt/dwarfeh.d:340: uncaught exception reached top of stack
This might happen if you're missing a top level catch in your fiber or signal handler
core.exception.AssertError@../../github/godot-dlang/src/godot/api/bind.d(191): Method  called on null reference
??:? _d_assert_msg [0x7ffff2674f44]
??:? godot.api.reference.Ref!(godot.image.Image).Ref godot.api.bind.ptrcall!(godot.image.Image, godot.api.bind.GodotMethod!(godot.image.Image, long, long, bool, godot.image.Image.Format).GodotMethod, long, long, bool, godot.image.Image.Format).ptrcall(godot.api.bind.GodotMethod!(godot.image.Image, long, long, bool, godot.image.Image.Format).GodotMethod, in godot.abi.types.godot_object, long, long, bool, godot.image.Image.Format) [0x7ffff4f50508]

Yeah, I discovered that myself too when I was fixing it...
Can you try godot-4.2 branch? Don't mind the name, there is no 4.2 specific features yet so it should work with 4.1 as well, but mind that there was reference counting fixes so it might uncover some issues with memory management or just be buggy.
If you can confirm it works I think we can do a new release with fresh fixes.

The 4.2 branch doesn't seem to exist any more. Looks like maybe it was merged into master?
I tried master and things seem to work now (both compile and run).
Many thanks!

See #132 for where and what versions are now
In basic terms:

master - 4.2 (aka current dev version)
4.1 - 4.1
Etc

And if issue is solved please close it


Documentation improvement: add a working example of createTag

This is a feature request for a minor documentation improvement on the createTag
A common use case is to create a new item via AJAX, and then add it to a list. I was not able to do this after hours of research in the docs, issues and the forum.
Problem
It looks like the documentation is a bit short on how to use the createTag.

There is confusion on why the createTag fires on every keypress, and not when the tag is created.
Related discussion

https://forums.select2.org/t/createtag-fires-before-tag-is-selected/159
https://forums.select2.org/t/create-new-tags/942

Do we also have to add .on("select2:selecting") to check if it was a newTag or an old tag and then decide if it should be created via Ajax? If it is always needed, should it be in the docs?
Should there perhaps be another function for creating new tags?

I have been using a mixture of Select2 and Selectize.js and I would like to stop using Selectize.js -The only reason I was using Selectize.js is because it was really simple to add new tags using their create function which fires when a new tag is created.
Here is a working Selectize.js create function:
create: function(input, callback){
  $.ajax({
    method: "POST",
    dataType: "json",
    url: '/inventories',
    data: {inventory: {name: input}},
    success: function(response){
      callback({value: response.id, text: response.name});
    },
    error: function(err){
      callback()
    }
  })
}

Can we add an example like this for the same use case for Select2?
Solution

Is anyone who knows how to do this easily, and has the time, willing to help improve the documentation on tagging a little bit?

Should there (in the future) maybe be a function that only fires when the tag is being created, instead of asking the user to create a custom newTag property (like the docs recommend), and than having to check for that custom property?
I guess this has been thought of and there might be technical reasons it's not possible at this time.

Tagging this as a documentation request. We're willing to entertain pull requests that improve the documentation in this area.

2. Should there (in the future) maybe be a function that only fires when the tag is being created, instead of asking the user to create a custom newTag property (like the docs recommend), and than having to check for that custom property?

This is something that is not likely to be implemented directly into Select2, just because we know it can be done through event handlers. It's possible that someone might package up the logic that says "attach an event handler, add the 'new tag' flag, and trigger this function when it's added" but it's unlikely to be in the core.


Question: Epoch averaging

Hi,
following the ERPs classification demo and checking the number of epoched used for the stratified 10-fold cross-validation I assume that the training and testing is done on the basis of single-trial i.e. only 1 repetition for each stimulus is taken.
My question is, how epoch averaging is implemented (if it's already programmed) in the toolbox ?

I would suggest not to average the ERPs, but to use single-trials for classification. The averaging can rather be done afterwards on the classifier output. (However, the difference in performance between averaging epochs and averaging classifier outputs is not large.)
Averaging classifier outputs is not implemented in the public toolbox for validation. It is just implemented in the online system (function bbci_control_ERPSpeller.m).

Thanks for the reply and suggestion.


feat: checkLinkNum supports object props & fix spell error

LinkNumLimit props support object type in config of DataMapping.
Fix spell error.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yingjia.lxh seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Sluuuuurp 2.0

Pulling in all of Alioth's changes.

I'm actually going to PR this from within since Alioth is in the org and that makes tests work.


Fixes #407

Fixes #407
Dumped entries:
https://gist.github.com/no1xsyzy/2e34843df5f972ca502ac0646d1d7d43
It seems some of them are meaningless on RPC client or just crazy on RPC client (like enable-rpc or about terminal output). No idea why they are there. Anyway, still added description and options.

What's more, online demo for the HEAD fork at http://webui-aria2.inqb.ga/ (using Github Pages, you can check dig webui-aria2.inqb.ga to see that)

感谢大佬……坐等合并……

Awesome!! makes it very useful @no1xsyzy 🎉 ❤


keystore absolute paths are not supported

I was following the guidelines here:
https://github.com/Microsoft/cordova-docs/tree/master/tutorial-package-publish
build.json setup mentions absolute path: "keystore":"c:\\my-release-key.keystore",
But copying that brings a build error which makes it clear that absolute paths are not supported in keystore item.

For Android I am not able to sign release builds with the Json file. I have to override the keystore property from the Json file on the command line.
This command with the json file as described in the Apache Docs works fine:
cordova build android --release -- --keystore android.keystore
I am using OSX El Capitan and the error I get when I just run cordova build android --release is:
Reading build config file: /Users/gabriel/Desktop/App-Windows/build.json

/Users/gabriel/Desktop/App-Windows/platforms/android/cordova/node_modules/q/q.js:126
                    throw e;
                          ^
TypeError: Object #<Object> has no method 'isAbsolute'

I got it to work by putting the keystore file in the same folder as the project. Then in your build.json don't use any reference to folders, just your keystore file name.

For whoever still being affected by this issue, I'd like to point out that, at least in my case, the problem was the Node version. Works fine for me after upgrading to Node v4.


python312Packages.bimmer-connected: 0.15.3 -> 0.16.1

Changelog: https://github.com/bimmerconnected/bimmer_connected/releases/tag/0.16.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 332037 run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.bmw_connected_drive

4 packages built:

python311Packages.bimmer-connected
python311Packages.bimmer-connected.dist
python312Packages.bimmer-connected
python312Packages.bimmer-connected.dist


tls.cert missing on windows

When i try to create an account using Pool.exe on windows I get this error that the tls.cert can't be found:
[pool] open C:\Users\xxxxxx\AppData\Local\Pool\mainnet\tls.cert: Das System kann die angegebene Datei nicht finden.
the folder does indeed not have such a file.

Same error, on macos. Using testnet though. Have bitcoind and lnd running on testnet.

Did you start the pool daemon (poold.exe which must run in the background the whole time) first, with the correct settings to connect it to lnd?

just tried it and it doesnt make a difference, still same problem.

I am not getting an issue anymore.
Unfortunately I don't have the capacity to reproduce this at the moment, but I believe that I was receiving this error when I tried to start pool while LiT was already running.

@sendbitcoin can you please check if there is a pool.db file somewhere within C:\Users\xxxxxx\AppData? Maybe there is an issue with the data directory on Windows that it somehow expects it to be somewhere else...

@sendbitcoin can you please check if there is a pool.db file somewhere within C:\Users\xxxxxx\AppData? Maybe there is an issue with the data directory on Windows that it somehow expects it to be somewhere else...

I'm having this same problem on Linux. I'm running the latest release of litd on my local machine, but connecting to a v0.11.0 remote lnd node.

I'm having this same problem on Linux. I'm running the latest release of litd on my local machine, but connecting to a v0.11.0 remote lnd node.

Just a heads up that Lightning Terminal is backwards compatible with lnd back to version v0.11.1-beta

Just a heads up that Lightning Terminal is backwards compatible with lnd back to version v0.11.1-beta

@guggero pool.db is in C:\Users\xxxxx\AppData\Local\Pool\mainnet\pool.db
I also had lit running but stopping it doesnt seem to make a difference, tls.cert still can't be found.
I currently can't create an account or use pool at all...
Is there any ETA on integrating pool into LIT so I can just use the GUI?

@guggero pool.db is in C:\Users\xxxxx\AppData\Local\Pool\mainnet\pool.db
I also had lit running but stopping it doesnt seem to make a difference, tls.cert still can't be found.
I currently can't create an account or use pool at all...
Is there any ETA on integrating pool into LIT so I can just use the GUI?

Ah, you are running LiT? Then there is no tls.cert created for pool, you need to use the cert from LiT (and the correct port). See https://github.com/lightninglabs/lightning-terminal/blob/master/doc/config-lnd-remote.md#example-pool-command

Ah, you are running LiT? Then there is no tls.cert created for pool, you need to use the cert from LiT (and the correct port). See https://github.com/lightninglabs/lightning-terminal/blob/master/doc/config-lnd-remote.md#example-pool-command

Closing per https://github.com/lightninglabs/pool/issues/192#issuecomment-756819080
Feel free to re-open if the linked instructions does not work for you.

Closing per https://github.com/lightninglabs/pool/issues/192#issuecomment-756819080
Feel free to re-open if the linked instructions does not work for you.


In this Pr i made all the routes necessary from the landing page , and add some code in the new pages that were empty for initial period , and i made half of the buttons go to their respective routes

Description of Changes
In this Pr i made all the routes necessary from the landing page , and add some code in the new pages that were empty for initial period , and i added some codes in the new pages and make half of the buttons navigate to their respective pages.
in my next pr i will make the other remaining buttons go to their respective button and in half of the buttons , now if you click in the image it will navigate to the respective route . In My next pr i will make the other buttons to work like this too. Will make steady changes and make this project better.
Type of Pull Request

[x] Bug Fix
[x] New Feature
[x] Performance Improvement
[ ] Documentation Update
[x] Code Refactoring
[ ] Security Enhancement
[ ] Other (Specify): _______________

(Please check relevant boxes by entering an "X" inside them)
Screenshots / Demo (if applicable)
In the ss you can see the new routes in next pr i will make all the buttons left to navigate to the their respective route

Checklist for Contributor

[x] I have reviewed my code before submission.
[x] I have read and followed the project's Contribution Guidelines.
[x] I have tested the code thoroughly.
[x] I have attached related issue numbers, screenshots, or videos (if applicable).
[] I have added comments to my code where necessary for clarity.
[x] I have checked the existing code base and my changes do not introduce any breaking changes.
[ ] My PR addresses only one issue; I have created separate PRs for other issues.
[x] I have ensured that the PR does not include unrelated files.
[x] I am mindful of the project's coding standards and best practices.

Contribution Guidelines Reminder
Thank you for contributing to our project! Please ensure you follow the guidelines below:
Contribution Levels

Task Categories:

Basic Tasks: Primarily focused on small changes like minor bug fixes, documentation improvements, and unit testing. Labeled as Easy.
Intermediate Tasks: Moderate-level tasks that involve enhancing existing features, code refactoring, or performance improvements. Labeled as Medium.
Advanced Tasks: Complex tasks like building new features, significant refactoring, or critical bug fixes. Labeled as Hard.

Acknowledging Effort:

Exceptional contributions will be recognized with a higher contribution level if substantial effort and innovation are demonstrated.

Review Process

PRs will be reviewed by the maintainers, and feedback will be provided. Contributors should address feedback promptly and resubmit the PR if necessary.

Contributors are encouraged to participate in the review process of other PRs for community growth.

We appreciate your time and effort in improving this project and look forward to your valuable contributions!

@dhairyagothi  Merge this PR i will then start working on the things i told in the description and thank you for merging My earlier PR.

What is issue no , ?@Raja-Abrar-Khan

ohh, sorry I forgot to make this an Issue , let me make and give you issue number

#152 issue number for this one. Now merge this PR from next time i will make every issue and add issue number

@Raja-Abrar-Khan dont make PR before issue is not assigned to you . there is already same issue

I made routes in app.jsx as well i added code in the new components also . and that issue is 3 days older it doesn't take that long .
And that issue is only adding route to the buttons that i as going to do in next pr i won't do it then if thats the case now please merge this pr the thing i am doing in this pr and that 3 days old issue are not exactly same


#8667 still applies

Issue #8667 still applies in latest
❯ hugo
Start building sites …
hugo v0.121.1-00b46fed8e47f7bb0a85d7cfc2d9f1356379b740+extended darwin/amd64 BuildDate=2023-12-08T08:47:45Z VendorInfo=brew

WARN  calling IsSet with unsupported type "invalid" (<nil>) will always return false.

The fix in #8668 is valid , even if I'd do it this way:
diff --git a/tpl/collections/collections.go b/tpl/collections/collections.go
--- a/tpl/collections/collections.go	(revision 6f13430d4a3b0d8b196f13958fbfb6478be1f3aa)
+++ b/tpl/collections/collections.go	(date<PHONE_NUMBER>068)
@@ -396,7 +396,7 @@
 			return av.MapIndex(kv).IsValid(), nil
 		}
 	default:
-		ns.deps.Log.Warnf("calling IsSet with unsupported type %q (%T) will always return false.\n", av.Kind(), c)
+		ns.deps.Log.Warnf("calling IsSet with unsupported type %q (%T) [Key: %q] will always return false.\n", av.Kind(), c, kv)
 	}

 	return false, nil

This allows to see that a key 'name' is invalid

❯ /Users/hrupp/golang/bin/hugo
Start building sites …
hugo v0.122.0-DEV-6f13430d4a3b0d8b196f13958fbfb6478be1f3aa darwin/amd64 BuildDate=2023-12-08T09:01:24Z
WARN  calling IsSet with unsupported type "invalid" () [Key: "name"] will always return false.

which then allows me to look through my files to see that this is the culprit
                {{if isset .Site.Params.author "name"}}

which then allows me to see that indeed in hugo.toml, there is no section [params.author].
A better fix would be to also show the place of the issue, but with the above, the message can at least be used for debugging.

@pilhuhn Please change the issue title.


Add Pauli X,Y,Z to S=1/2 site type

Codecov Report

Merging #576 (1253289) into master (0887694) will decrease coverage by 0.38%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #576      +/-   ##
==========================================
- Coverage   80.66%   80.28%   -0.39%
==========================================
  Files          42       42
  Lines        4473     4483      +10
==========================================
- Hits         3608     3599       -9
- Misses        865      884      +19

Impacted Files
Coverage Δ

src/physics/site_types/spinhalf.jl
62.96% <0.00%> (-14.31%)
:arrow_down:

src/broadcast.jl
62.98% <0.00%> (-1.95%)
:arrow_down:

src/smallstring.jl
60.00% <0.00%> (-1.67%)
:arrow_down:

src/qn/qn.jl
83.42% <0.00%> (-1.15%)
:arrow_down:

src/tagset.jl
87.41% <0.00%> (-0.70%)
:arrow_down:

src/qn/qnindex.jl
63.10% <0.00%> (-0.54%)
:arrow_down:

src/decomp.jl
89.91% <0.00%> (-0.44%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks for adding this, this is something I have thought about adding in the past.
I was thinking about adding the "Qubit" type as an official ITensors.jl site type (https://github.com/ITensor/ITensors.jl/blob/master/examples/gate_evolution/qubit.jl), however maybe we could just define all of those gates for "S=1/2" and make "Qubit" another alias for "S=1/2".


[feature] Add FPS counter

Currently, the engine supports showing FPS by pressing F3.
But this code is hardcoded in C.
https://github.com/avivbeeri/dome/blob/master/src/engine.c#L874
internal void
ENGINE_drawDebug(ENGINE* engine) {
  char buffer[20];
  ENGINE_DEBUG* debug = &engine->debug;
  // Choose alpha depending on how fast or slow you want old averages to decay.
  // 0.9 is usually a good choice.
  double framesThisSecond = 1000.0 / (debug->elapsed+1);
  double alpha = debug->alpha;
  debug->avgFps = alpha * debug->avgFps + (1.0 - alpha) * framesThisSecond;
  snprintf(buffer, sizeof(buffer), "%.01f fps", debug->avgFps);   // here 2 means binary
  int32_t width = engine->width;
  int32_t height = engine->height;
  int64_t startX = width - 4*8-2;
  int64_t startY = height - 8-2;

  ENGINE_rectfill(engine, startX, startY, 4*8+2, 10, 0x7F000000);
  ENGINE_print(engine, buffer, startX+1,startY+1, 0xFFFFFFFF);

  startX = width - 9*8 - 2;
  if (engine->vsyncEnabled) {
    ENGINE_print(engine, "VSync On", startX, startY - 8, 0xFFFFFFFF);
  } else {
    ENGINE_print(engine, "VSync Off", startX, startY - 8, 0xFFFFFFFF);
  }

  if (engine->lockstep) {
    ENGINE_print(engine, "Lockstep", startX, startY - 16, 0xFFFFFFFF);
  } else {
    ENGINE_print(engine, "Catchup", startX, startY - 16, 0xFFFFFFFF);
  }
}

It would be handy to obtain the current FPS number in Wren.
Example:
Process.fps

Because Window class is more related to the drawing.
Its best to use Window instead of Process to hold this value.


Missing rebar.config

Hello guys,
could you please add rebar.config to your app

It uses erlang.mk build system. No need for that file just hit make.

as you wish, just for your information rebar3 located in top "scope" of erlang https://github.com/erlang/rebar3 in other hand Erlang.mk just @essen's stuff

You can add the following line to the Makefile to generate a rebar.config automatically:
app:: rebar.config

It'll get generated every time the project builds, so just commit it after that.

@essen thanks for hint, good to know!

just did that, thx @essen

Glorious commit https://github.com/softwarejoint/fcm-erlang/commit/02edb5489aec71519ddb4ad1263d2e1d36c49630


Bug : kubectl cp doesn't work when filename contains brackets

What happened:
The "kubectl cp" command doesn't work when a filename contains bracket character.
What you expected to happen:
That it work ^^
or that return warning message (currently, the return code is 0).
How to reproduce it (as minimally and precisely as possible):
Example :  my source filename is : TEST[0]
kubectl cp -c <container> /tmp/TEST\[0\] <namespace>/<pod>:/directory/
Anything else we need to know?:
Environment:

Kubernetes client and server versions (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.1", GitCommit:"3ddd0f45aa91e2f30c70734b175631bec5b5825a", GitTreeState:"clean", BuildDate:"2022-05-24T12:26:19Z", GoVersion:"go1.18.2", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.12", GitCommit:"b058e1760c79f46a834ba59bd7a3486ecf28237d", GitTreeState:"clean", BuildDate:"2022-07-13T14:53:39Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):

kubectl cp has had a few CVE's in the past so we've purposefully limited the functionality. Supporting special characters is not a door we want to open.
/close