What are setName and setShortName supposed to do?

BLEDevice::init("Jack's Server4");
BLEServer* pJackServer = BLEDevice::createServer();
BLEAdvertising* pJackAdvertising = pJackServer->getAdvertising();
BLEAdvertisementData jacksAdData;
jacksAdData.setFlags(ESP_BLE_ADV_FLAG_GEN_DISC | ESP_BLE_ADV_FLAG_BREDR_NOT_SPT);
jacksAdData.setName("2nd Server");
jacksAdData.setShortName("4th Server");
pJackAdvertising->setAdvertisementData(jacksAdData);
pJackAdvertising->start();
Here I initialize a device as "Jack's Server4"
Later, I use advertisement data to set the name and shortname in the advertising data.  What are these supposed to accomplish????
No matter what I enter, the device always shows up as Jack's Server4
So what are they for?

My guess is due to your total advertising packet being longer than 32 bytes. Try reducing the overall size of your advert packet and use different name/short name and see what that does.

I got it. Names, short or long in advertisement packet data units have nothing to do with the name of the device.  It is just advertising data.


Doesn't play well with candle

I am fairly new to leptos so please correct me if I am doing anything wrong but when running cargo leptos build on a project with candle-core as a dependency, the build fails even though a regular cargo build works just fine.
System:

ubuntu (WSL2)
rustc 1.82.0-nightly (730d5d409 2024-08-10)

Stacktrace:
cargo leptos build
Compiling cudarc v0.11.6
error[E0433]: failed to resolve: could not find `Library` in `libloading`
      --> /home/diwank/.asdf/installs/rust/1.79.0/registry/src/index.crates.io-6f17d22bba15001f/cudarc-0.11.6/src/cublas/result.rs:146:37
               |
        146 |         .get_or_init(|| libloading::Library::new(libloading::library_filename("cublas")).unwrap());
               |                                     ^^^^^^^ could not find `Library` in `libloading`
               |
note: found an item that was configured out
      --> /home/diwank/.asdf/installs/rust/1.79.0/registry/src/index.crates.io-6f17d22bba15001f/libloading-0.8.5/src/lib.rs:50:22
               |
         50  | pub use self::safe::{Library, Symbol};

Is there an easy workaround for this until this gets addressed?

I am going to guess that this is a "this dependency can't be compiled for WASM" kind of issue. It's not really possible to tell without a reproducible example.

hmm

I just followed the tutorial from the README for leptos. Here's my Cargo.toml file, the only thing that's changed is the addition of candle-core dependency, the rest of the codebase is the same as from the template repo:
[package]
name = "thoughtpad"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["cdylib", "rlib"]

[dependencies]
actix-files = { version = "0.6", optional = true }
actix-web = { version = "4", optional = true, features = ["macros"] }
console_error_panic_hook = "0.1"
http = { version = "1.0.0", optional = true }
leptos = { version = "0.6", features = ["nightly"] }
leptos_meta = { version = "0.6", features = ["nightly"] }
leptos_actix = { version = "0.6", optional = true }
leptos_router = { version = "0.6", features = ["nightly"] }
wasm-bindgen = "=0.2.92"
candle-core = { git = "https://github.com/huggingface/candle.git", version = "0.6.0", features = ["cuda"] }

[features]
csr = ["leptos/csr", "leptos_meta/csr", "leptos_router/csr"]
hydrate = ["leptos/hydrate", "leptos_meta/hydrate", "leptos_router/hydrate"]
ssr = [
  "dep:actix-files",
  "dep:actix-web",
  "dep:leptos_actix",
  "leptos/ssr",
  "leptos_meta/ssr",
  "leptos_router/ssr",
]

# Defines a size-optimized profile for the WASM bundle in release mode
[profile.wasm-release]
inherits = "release"
opt-level = 'z'
lto = true
codegen-units = 1
panic = "abort"

[package.metadata.leptos]
# The name used by wasm-bindgen/cargo-leptos for the JS/WASM bundle. Defaults to the crate name
output-name = "thoughtpad"
# The site root folder is where cargo-leptos generate all output. WARNING: all content of this folder will be erased on a rebuild. Use it in your server setup.
site-root = "target/site"
# The site-root relative folder where all compiled output (JS, WASM and CSS) is written
# Defaults to pkg
site-pkg-dir = "pkg"
# [Optional] The source CSS file. If it ends with .sass or .scss then it will be compiled by dart-sass into CSS. The CSS is optimized by Lightning CSS before being written to <site-root>/<site-pkg>/app.css
style-file = "style/main.scss"
# Assets source dir. All files found here will be copied and synchronized to site-root.
# The assets-dir cannot have a sub directory with the same name/path as site-pkg-dir.
#
# Optional. Env: LEPTOS_ASSETS_DIR.
assets-dir = "assets"
# The IP and port (ex: <IP_ADDRESS>:3000) where the server serves the content. Use it in your server setup.
site-addr = "<IP_ADDRESS>:3000"
# The port to use for automatic reload monitoring
reload-port = 3001
# [Optional] Command to use when running end2end tests. It will run in the end2end dir.
#   [Windows] for non-WSL use "npx.cmd playwright test"
#   This binary name can be checked in Powershell with Get-Command npx
end2end-cmd = "npx playwright test"
end2end-dir = "end2end"
#  The browserlist query used for optimizing the CSS.
browserquery = "defaults"
# The environment Leptos will run in, usually either "DEV" or "PROD"
env = "DEV"
# The features to use when compiling the bin target
#
# Optional. Can be over-ridden with the command line parameter --bin-features
bin-features = ["ssr"]

# If the --no-default-features flag should be used when compiling the bin target
#
# Optional. Defaults to false.
bin-default-features = false

# The features to use when compiling the lib target
#
# Optional. Can be over-ridden with the command line parameter --lib-features
lib-features = ["hydrate"]

# If the --no-default-features flag should be used when compiling the lib target
#
# Optional. Defaults to false.
lib-default-features = false

# The profile to use for the lib target when compiling for release
#
# Optional. Defaults to "release".
lib-profile-release = "wasm-release"

Steps to reproduce:

cargo leptos new --git https://github.com/leptos-rs/start-actix
cargo add --git https://github.com/huggingface/candle.git candle-core --features "cuda"
cargo leptos build --release  (Same error without the --release flag)

hmm lemme dig into this a bit more but then shouldn't cargo build also fail? @gbj

No, but cargo build --target=wasm32-unknown-unknown should fail.
That said, I cannot even get an extremely simple, Leptos-less version to build:
cargo add --git https://github.com/huggingface/candle.git candle-core --features "cuda"
cargo build

fails for me during a build script.
I don't think this has anything to do with Leptos. It is most likely an issue with some combination of features (CUDA?) not working with WASM.

Gotcha. Lemme try that and report back

yup. my bad, cuda of course won't work on wasm. I got blindsided by cargo build just kinda working. thanks for the tips @gbj


Lookup repo details inside settings.xml via its id. (get id based on name from pom.xml)

FEATURE REQUEST:
What you expected to happen:
Follow-up from https://github.com/kiwigrid/helm-maven-plugin/issues/128 to support repo resolution based on name from pom.xml.
In order to have smaller/cleaner pom.xml it will be more convenient to resolve repository from settings.xml by repo-id.
Repo id <=> repo name from pom.xml

Are you still working on this?

Yeah, but it is mostly "nice to have" :-)

Closing as stale, please reopen when pr is ready.


@azure/identity vulnerability in v3.1.3-alpha.20230103.2

Question, Bug, or Feature?
Type: Bug
Enter Task Name: In @azure/msal-node, jsonwebtoken package needs to be upgraded
In @azure/identity v3.1.3-alpha.20230103.2 jsonwebtoken has been upgraded to 9.0.0 version but the @azure/identity package has dependency with @azure/msal-node which still has vulnerable jsonwebtoken version 8.5.1. Please fix the @azure/msal-node  jsonwebtoken version in @azure/identity.

# npm audit report

jsonwebtoken  <=8.5.1
Severity: high
jsonwebtoken unrestricted key type could lead to legacy keys usage  - https://github.com/advisories/GHSA-8cf7-32gw-wr33
jsonwebtoken has insecure input validation in jwt.verify function - https://github.com/advisories/GHSA-27h2-hvpr-p74q
jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC - https://github.com/advisories/GHSA-hjrf-2m68-5959
jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify() - https://github.com/advisories/GHSA-qwph-4952-7xr6
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/jsonwebtoken
  @azure/msal-node  *
  Depends on vulnerable versions of jsonwebtoken
  node_modules/@azure/msal-node
    @azure/identity  >=1.2.0-alpha.20200903.1
    Depends on vulnerable versions of @azure/msal-node
    node_modules/@azure/identity

3 vulnerabilities (2 moderate, 1 high)


Use of  without css``

Subject
Using Fonts Documentation
Description
Hi,
On this page of the docs: https://chakra-ui.com/docs/styled-system/recipes/using-fonts#option-2-using-font-face
You have
const Fonts = () => (
  <Global
    styles={`
      /* latin */
      @font-face { ...

This does not work for me. I have to add Emotion's css method for it to work:
 styles={css`
        @font-face {

Hey @rossmawd,
this works as expected for me. Check out this csb example https://codesandbox.io/s/mystifying-dirac-cgl5gz?file=/src/index.tsx
Closing this issue.


continent code for country

I find that for mapping purposes I'd like to do a drilldown from continent to country to region/state. Would you be open to incorporating continent codes? (e.g., a pull request)
ISO 3166 Continent Members
Update; Actually, I'm not sure what to do with Russia, Turkey, Cyprus, Georgia, Kazakhstan, Azerbaijan, Armenia that border Europe and Asia.

There are some outliers, hey?
I don't mind adding the info at all - seems very relevant. Though if we did, I think I'd want to tweak the data structure to nest everything into the continent grouping.

OK, this is not a priority for me so I'll hold off for now. Thanks!


Add support for mu-law audio data

The June 23, 2016 update added support for audio/basic (8-bit u-law) data:

The list of supported audio formats now includes audio/basic, which provides single-channel audio encoded using 8-bit u-law (or mu-law) data sampled at 8 KHz. For more information, see Audio formats.

Complete with b358bc7ddde30c6681afa82ce5035982635da93b.
Developed in Swift 2.2 then merged into Swift 2.3 and Swift 3.0.


Disabling batch saving for VmOrTemplate because of needed hooks

Disabling batch saving for VmOrTemplate because of needed hooks

@miq-bot assign @agrare
@miq-bot add_label enhancement
@agrare we have some weird hooks on VmOrTemplate for manipulating User, that we need now for passing specs, should be refactored later.


Collate all files modified by Caijun7

Collate all files modified by Caijun7

Refer to issue #133

Pull Request Test Coverage Report for Build 334

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

Totals

Change from base Build 331:
0.0%

Covered Lines:
2325

Relevant Lines:
2673

💛  - Coveralls


Fix memory explosion when passing large-ish python objects

It is often convenient to pass around large-ish objects to python apps. Currently, for workflows with large numbers of tasks, this causes a memory explosion for the main Parsl process. This probably has to do with keeping args/kwargs in the DFK internal dict, but it's not immediately obvious to me why-- inspecting the ids of the args in the DFK match the original one, so that's not where the copy is happening.
import sys

import numpy as np
import pandas as pd
import parsl
from parsl.configs.htex_local import config
import tqdm

dfk = parsl.load(config)

data = pd.DataFrame(np.random.rand(10000, 1000))
print('created dataset with size {:.2f} MB and id {}'.format(sys.getsizeof(data) / 1e6, id(data)))

@parsl.python_app
def foo(data):
    return True

futures = []
for i in tqdm.tqdm(range(1000)):
    futures += [foo(data)]
    args = sum([x['args'] for x in dfk.tasks.values()], [])
    print('current unique ids: {}'.format(set([id(x) for x in args])))

yields:
created dataset with size 80.00 MB and id<PHONE_NUMBER>52648
current unique ids: {139770018452648}
current unique ids: {139770018452648}
...

Does the memory performance change using local thread executor? Htex will serialise (= copy) more than local thread executor.

🤦♀ Thanks Ben!! You're right, it's instantaneous with the local thread executor. This is definitely happening in ipyparallel.serialize.serialize_object.

What is the actual parsl issue here, after that change? That parsl should make it easier to move this stuff around? That we should be clear that in the case of big objects you need to do something like serialize them yourself and use eg file staging?

The issue is that, if the user would rather take the performance hit of sending the same large object to all their workers (until we have something more sophisticated like worker-side caching) than dealing with doing their own serialization (and any associated filesystem issues), they should be able to do so without the main process memory blowing up.
If I serialize the large object as usual but then replace the args in the message with a fake empty args list before putting it in the outgoing queue, the memory doesn't blow up (as expected-- the refcount goes to zero when the submit block ends). I think the issue is that a ref or copy is being kept around somewhere even after the message is sent.
         big_message = pack_apply_message(func, args, kwargs,
                                     buffer_threshold=1024 * 1024,
                                     item_threshold=1024)
         fn_buf = pack_apply_message(func, [], kwargs,
                                     buffer_threshold=1024 * 1024,
                                     item_threshold=1024)

         msg = {"task_id": task_id,
                "buffer": fn_buf}

         # Post task to the the outgoing queue
         self.outgoing_q.put(msg)

This looks related: zeromq/pyzmq#1261


Jest fails because of outdated jsdom dependency in jest-environment-jsdom

Attempts to run formerly cleanly running tests now throw errors due to api changes. A more recent jsdom is needed to compensate.
For further detail see: https://github.com/jsdom/jsdom/issues/1782#issuecomment-458396371

Duplicate of #7926 et. al.
tl;dr - upgrading requires node 8 and we're not ready to drop node 6

Ok, poking at the other tickets learned there is this now for more recent node version:
https://www.npmjs.com/package/jest-environment-jsdom-thirteen


nixos: remove duplicate wrapperDir PATH addition

Motivation for this change
Duplicate wrapperDir PATH addition should be removed. Correct PATH addition is already defined here.
Things done

Built on platform(s)

[x] Linux

[x] Fits CONTRIBUTING.md.

Bjørn Forsman<EMAIL_ADDRESS>writes:

@0xABAB, That's unrelated to this patch. But if in a separate commit, I don't care. (Although my personal preference is to quote too much than too little.)

Agreed, leave the quotes, someone might have a space in $HOME, it's not prohibited.

@oxij What would happen if there was a space? (This is a rhetorical question, since you clearly have no idea how to write a shell script.  (This is a rhetorical question, since you clearly have no idea how to write a shell script.

I expected it to perform normal substitution like
X="echo test"
$X
does in bash. But it doesn't. It most certainly did the last time I
checked in 1998 on RedHat. I'm not complaining, though. F*ck
substitutions like that.

@oxij So, now you are saying that tooling which is as old as UNIX itself has changed semantics as opposed to the simpler explanation that in 1998 you didn't know what you were doing (something which is ostensibly true in 2017)? Bold, very bold.

0xABAB<EMAIL_ADDRESS>writes:

@oxij So, now you are saying that tooling which is as old as UNIX
itself has changed semantics as opposed to the simpler explanation

... except, its not. And bash does change semantics. Why do you think
autoconf scripts "check shell", i.e. run bash snippets? To check and
work-around old bash behavior.

that in 1998 you didn't know what you were doing (something which is
ostensibly true in 2017)? Bold, very bold.

Maybe, maybe not. I got bitten by not having enough quotes in bash
enough times to prefer adding more than strictly required. Now I'm
mildly optimistic about the future of variable assignment in bash.
But how exactly does it hurt to have quotes in there?
Either way, does this has anything to do with this PR?
Can we stop the bikeshedding now and merge?

@oxij You should learn to recognize a superior force when you meet one.
From 1996: http://www.fnal.gov/docs/products/bash/bashref.htm, we read:
If value is not given, the variable is assigned the null string. All values undergo tilde expansion, parameter and variable expansion, command substitution, arithmetic expansion, and quote removal (detailed below). If the variable has its `-i' attribute set (see the description of the declare builtin in section Bash Builtin Commands), then value is subject to arithmetic expansion even if the $((...)) syntax does not appear (see section Arithmetic Expansion). Word splitting is not performed, with the exception of "$@" as explained below. Filename expansion is not performed.

Sure, I know that bash semantics changes over time, but you are just using that to hide your mistake from other ignorant people who do not understand this is irrelevant in this case.
I understand why autoconf does what it does; you apparently do not. I am not going to give another free lecture, btw.
When will you figure out that it's better to just not say anything, because of the difficulty you have with producing true statements?

@tk-ecotelecom thank you

0xABAB: Why do you respond like that?  It seems completely uncalled for.

Jeez... Let's all be adults and move on...

@bjornfor Persistent insistence on sharing incompetence can elicit such a response.

0xABAB<EMAIL_ADDRESS>writes:

@oxij You should learn to recognize a superior force when you meet one.

Yes, master!

So, now you are saying that tooling which is as old as UNIX itself has
changed semantics

Sure, I know that bash semantics changes over time

Okay. I forgive.

that in 1998 you didn't know what you were doing (something which is
ostensibly true in 2017)? Bold, very bold.

Maybe, maybe not.

Wasn't okay? No forgiveness?

But how exactly does it hurt to have quotes in there?

[a wall funny text that dosn't answer the question]

You are always welcome to 4chan!


Build a subgraph for the BrightID-EthereumAddressService

If we build a subgraph for the BrightID-EthereumAddressService, we can probably offload to The Graph any computation involved with filtering poll results based on BrightID accounts. This way, the client would only get a list of valid votes.
Better still, we may even be able to have The Graph compute the current state of the poll. So the client just receives percentages for and against.
What are your thoughts @Tomasvrba?

Didn't see the issue in this repo until now. Probably an outdated response, but anyway:
Building the subgraph is related to the Burn Signal app, not the BrightID-EthereumAddressService. Since all this service does is link addresses to BrightID, without any smart contract interaction, so The Graph would have no events to listen for.
I would either close this issue or move to the Burn Signal repo along with a spec of all the information we want to get from the subgraph.


Update macOS-Development-Setup.rst

add Xcode App Store link
BASH -> ZSH (default)
make homebrew paths generic

@mergifyio rebase

@PhDittmann I retargeted this PR to rolling and tried rebasing it since there were a bunch of unnecessary commits. Can you fix this, maybe by cherry-picking your commit onto rolling and then pushing to this branch? Otherwise, I can do it, but I may be slower to get to it.

I stashed my commit, pulled the latest official rolling and put it on top of it.


V1.9.x

The purpose of this PR is to merge anything useful from the v1.9.x branch into master so that we can delete the branch. After resolving merge conflicts there is nothing to merge.


Errors in the bug-mining process

Hello，
I tried to add bugs in Defects4j by following step bug-mining. However, when I reached the step of Reviewing and isolating the bugs, I checked the diff for each fault, typed yes, and then looped the previous commands. I don't know how to solve this problem.
The specific steps are as follows.
./minimize-patch.pl -p Csv -w /home/laughtale/defects4j/bug-mining-test -b 43
Checking out 65883aa4 to /tmp/minimize-patch.pl_112389_1606718356/Csv-43f.. OK
Init local repository...................................................... OK
Tag post-fix revision...................................................... OK
Copy generated Ant build file.............................................. OK
Run post-checkout hook..................................................... OK
Excluding broken/flaky tests............................................... OK
Initialize fixed program version........................................... OK
Apply patch................................................................ OK
Initialize buggy program version........................................... OK
Diff 65883aa4:081b0702..................................................... OK
Apply patch................................................................ OK
Tag pre-fix revision....................................................... OK
Check out program version: Csv-43f......................................... OK
Apply patch................................................................ OK
Back up original patch..................................................... OK
Has the patch been minimized? [y/n] > y
1 file changed, 24 insertions(+), 26 deletions(-)
diff --git a/src/main/java/org/apache/commons/csv/CSVFormat.java b/src/main/java/org/apache/commons/csv/CSVFormat.java
index a7432b9..319c861 100644
--- a/src/main/java/org/apache/commons/csv/CSVFormat.java
+++ b/src/main/java/org/apache/commons/csv/CSVFormat.java
@@ -804,8 +804,8 @@ public final class CSVFormat implements Serializable {
             throw new IllegalArgumentException("The comment start marker character cannot be a line break");
         }
         return new CSVFormat(delimiter, quoteCharacter, quoteMode, commentMarker, escapeCharacter,
-                ignoreSurroundingSpaces, ignoreEmptyLines, recordSeparator, nullString, headerComments, header,
-                skipHeaderRecord, allowMissingColumnNames);
+                ignoreSurroundingSpaces, ignoreEmptyLines, recordSeparator, nullString, null, header, skipHeaderRecord,
+                allowMissingColumnNames);
     }

     /**
@@ -822,8 +822,8 @@ public final class CSVFormat implements Serializable {
             throw new IllegalArgumentException("The delimiter cannot be a line break");
         }
         return new CSVFormat(delimiter, quoteCharacter, quoteMode, commentMarker, escapeCharacter,
-                ignoreSurroundingSpaces, ignoreEmptyLines, recordSeparator, nullString, headerComments, header,
-                skipHeaderRecord, allowMissingColumnNames);
+                ignoreSurroundingSpaces, ignoreEmptyLines, recordSeparator, nullString, null, header, skipHeaderRecord,
+                allowMissingColumnNames);
Has the patch been successfully minimized? [y/n] > y
Running ant (compile)...................................................... OK
Running ant (compile.tests)................................................ OK
Running ant (run.dev.tests)................................................ OK
Triggering test cases now fail due to other reasons:
--- org.apache.commons.csv.CSVPrinterTest::testHeaderCommentExcel
junit.framework.AssertionFailedError: expected:<[# Generated by Apache Commons CSV 1.1
# Sat Nov 28 05:28:08 PST 2020
]Col1,Col2
A,B
...> but was:<[]Col1,Col2
A,B
...>
--- org.apache.commons.csv.CSVPrinterTest::testHeaderCommentTdf
junit.framework.AssertionFailedError: expected:<[# Generated by Apache Commons CSV 1.1
# Sat Nov 28 05:28:07 PST 2020
]Col1	Col2
A	B
...> but was:<[]Col1	Col2
A	B
...>	D
vs
--- org.apache.commons.csv.CSVPrinterTest::testHeaderCommentExcel
junit.framework.AssertionFailedError: expected:<[# Generated by Apache Commons CSV 1.1
# Sun Nov 29 22:39:35 PST 2020
]Col1,Col2
A,B
...> but was:<[]Col1,Col2
A,B
...>
--- org.apache.commons.csv.CSVPrinterTest::testHeaderCommentTdf
junit.framework.AssertionFailedError: expected:<[# Generated by Apache Commons CSV 1.1
# Sun Nov 29 22:39:35 PST 2020
]Col1	Col2
A	B
...> but was:<[]Col1	Col2
A	B
...>	D
Checking out 65883aa4 to /tmp/minimize-patch.pl_112389_1606718356/Csv-43f.. OK
Init local repository...................................................... OK
Tag post-fix revision...................................................... OK
Copy generated Ant build file.............................................. OK
Run post-checkout hook..................................................... OK
Excluding broken/flaky tests............................................... OK
Initialize fixed program version........................................... OK
Apply patch................................................................ OK
Initialize buggy program version........................................... OK
Diff 65883aa4:081b0702..................................................... OK
Apply patch................................................................ OK
Tag pre-fix revision....................................................... OK
Check out program version: Csv-43f......................................... OK
Apply patch................................................................ OK
Back up original patch..................................................... OK
Has the patch been minimized? [y/n]

Always ask me Has the patch been minimized? [y/n] this question repeatedly.
What should I do to make this step successful?
Thank you!

Hi @joonzzh,
It looks like your minimization changed the results of execution. The trigger tests now fail for different reasons than they originally did. Selecting N should have restored the previous version of the patch.
If it didn't, I'd recommend reperforming bug mining for that revision specifically just to restore the files. In general, it may be a good idea to keep a backup of everything while you perform the minimization process so you can restore back to the unminimized version if you make a change that is not good.

Feel free to open a new issue (or reopen this one) if you have additional questions.

Feel free to open a new issue (or reopen this one) if you have additional questions.


Could not intercept Android view method call. What I am doing wrong?

Suppose I have a student class like below
`class Student {
String firstName;
String lastName;

public Student(String firstName, String lastName) {
    this.firstName = firstName;
    this.lastName = lastName;
}

public String getFullName() {
    return firstName + " " + lastName;
}

}`
Now I have created the transformation to intercept getFullName method call like below
`@Transformation
class StudentTransformation(
private val logger: Logger
) :
Plugin {
override fun apply(
    builder: DynamicType.Builder<*>,
    typeDescription: TypeDescription,
    classFileLocator: ClassFileLocator
): DynamicType.Builder<*> {
    logger.lifecycle("Transforming ${typeDescription.name} with StudentTransformation")

    return builder.method(ElementMatchers.named("getFullName"))
        .intercept(MethodDelegation.to(StudentClassInterceptor::class.java))
}

override fun matches(target: TypeDescription): Boolean {
    return true
}

override fun close() {
    // Nothing to close
}

}`
and here is the interceptor
`object StudentClassInterceptor {
@JvmStatic
fun intercept(@Origin m: Method, @SuperCall originalMethodCall: Runnable): String  {
    Log.i("myTag", "Intercepted Student Class getFullName ${m.name}")
    return "John Doe"
}

}`
It is working fine when I am calling getFullName on a student object and I am getting "John Doe" as it has been intercepted.
But same thing I want to do for android View.class. Inside View class there is a method named "getHeight()" which return the height. I want to intercept this method call. When I call this method on a button I want to return a fixed value. But it is not intercepting. Here is the code for ViewTransformation
`@Transformation
class ViewTransformation(private val logger: Logger) : Plugin {
override fun apply(
    builder: DynamicType.Builder<*>,
    typeDescription: TypeDescription,
    classFileLocator: ClassFileLocator
): DynamicType.Builder<*> {
    logger.lifecycle("Transforming ${typeDescription.name} with ViewTransformation")
    return builder.method(ElementMatchers.named("getHeight"))
        .intercept(MethodDelegation.to(ViewMethodInterceptor::class.java))
}

override fun matches(target: TypeDescription): Boolean {
    return target.isAssignableTo(View::class.java)
}

override fun close() {
    // Nothing to close
}

}`
Here is the interceptor
`object ViewMethodInterceptor {
@JvmStatic
fun intercept(@Origin m: Method, @SuperCall originalMethodCall: Runnable): Int  {
    Log.i("myTag", "Intercepted View Class getHeight")
    return 500;
}

}`
Now I am calling getHeight() inside onCreate of MainActivity likhe this
btn.getHeight()
But getHeight is not intercepting. What's I am doing wrong? @LikeTheSalad

Hi @souravpalitrana
You're not doing anything wrong, no worries, the issue is that, unfortunately, none of the Android SDK classes (listed here) can be transformed because of the way Android works. So what happens is that, the Android OS comes with these classes built in, so in the end your app makes use of the classes in each device instead of the classes of the android library that we see in our code.
So in other words, the Android SDK classes that we see in our code, are only some sort of "mocks" if you will... Those won't go into the app because the ones that you'll app will use when it's running are the ones built into the Android devices.
The only Views that your transformation can affect would be custom ones from your project, so for example, if you create a custom Button that extends the Android's SDK Button View class, and then you use that in your layout, then you'll see the transformation applied at run time, to your custom View only.

Thanks, @LikeTheSalad for the detailed explanation. However, could we do this transformation for the third-party library? I think we could not. For example, I want to rebase a class of Volley library. I could not do that too.

Hi @souravpalitrana - By default Android Buddy doesn't transform third party dependencies, but you can configure it to do so by following the steps mentioned here: https://github.com/LikeTheSalad/android-buddy#configuration-to-enable-dependencies-transformations
This configuration for transforming third party dependencies is quite new, so it's prone to errors. At the beginning I didn't add this support because of some Android build plugin limitations (which I've listed in the readme) and also because of build performance concerns, however I've been thinking lately about some ways to add this support by default without affecting the performance too much and making it easy to use as well, and I'm pondering about maybe making it to support third party transformations by default on version 2.0.0.
So please take a look at the configuration, let me know if something's wrong or somehow not working as expected so that I could address that in the version I mentioned :)
Thanks,
Cesar

Closing due to inactivity, please reopen if you still have the same issue.


Include additional AMQP elements in Message

https://apiview.dev/Assemblies/Review/b5d7e3304000449c859c2016f718db52

AbsoluteExpiryTime
ContentEncoding
CreationTime
DeliveryAnnotations
Footer
GroupId (same as SessionId)
GroupSequence
Header

Durable
Priority
Ttl (this should also be top level property)
FirstAcquirer
DeliveryCount (this should also be top level property on received message)

MessageAnnotations
ReplyToGroupId (same as ReplyToSessionId)
Rename Label to Subject
UserId

Motivation for this change:
A desire to allow reading and writing of the different parts of an AMQP message as described by the AMQP spec. See "Message Format" in section 3.2 of the AMQP spec
Guiding factors:

Existing users used to accessing either AMQP properties like messageId or AMQP message annotations like partitionKey or AMQP message header like deliveryCount should continue to have these as top level entities
All inner details of AMQP message should be accessible to the advanced user. But, since these do not matter to the rest of the user base, we would like to hide the "complete" AMQP message (header, footer, message annotations, deliver annotations, properties) in a nested field. This model can be replicated in Event Hubs in the future
We do not want to introduce any new AMQP message detail as a top level entity at this moment in time to avoid increasing the surface area and confusing the normal users. If the service team determines that any new AMQP message entity from header/footer/message annotations/delivery annotations deserve to get a spot on the top level, it should be do-able incrementally in a non breaking fashion

Revised proposal:

Keep all the top level entities that exist today (like body, messageId, sessionId, partitionKey etc)
Rename label to subject (to match what AMQP nomenclature)
Rename userProperties to applicationProperties (to match what AMQP nomenclature)
Add a field for "AMQP message details" (this sooo needs a better name)

header
footer
message annotations
delivery annotations
properties


[EBPF-419] Allow testing against KMT VMs of different architecture

What does this PR do?
This PR has several improvements for KMT testing, centered around the testing in macOS against VMs of the same and remote architectures. Changes:

Compiler images are now architecture dependent. We take advantage of the ability to run x86_64 Docker images on macOS to have a x86 and ARM compiler image.
In code, the compiler image is now represented by a class instance, reflecting the fact that we now have different images running.
SSH keys to connect to microVM are now taken from a local, constant path instead of from the stack.output file, as the path in that file refers to a file inside of the instance. In the case of remote instances launched from macOS, the path differs and we have connection failures for KMT commands.
To have uniform path naming and to avoid mistakes, KMT paths have been defined in a KMTPaths class instance that allows using variables for the paths, with the architecture and stack name being filled automatically. The paths returned are of type Path which makes it easier to manipulate them in Python.
The test, build, prepare and build_dependencies jobs now properly take into account the architecture of the target VMs, and will generate dependencies appropriately.
The test job accepts an empty vms list, which indicates it needs to use all VMs.

Motivation
https://datadoghq.atlassian.net/browse/EBPF-419
Additional Notes
Possible Drawbacks / Trade-offs
The cross-compile support is preliminary and has certain downsides. The system-probe build process does not really support cross-compilation, which means that the build artifacts for the different architectures are located in the same place and overwritten. This means that if the stack we're using has machines with different architectures, the build artifacts will need to be rebuilt each time we target a different architecture.
Describe how to test/QA your changes
Locally tested.

/merge

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on

/merge


Needs examples in documentation

+1 (sub)

With guidance of @garlicnation , I will try to come up with some examples to show the basics. Once I can get a grasp of the functionality, we could improve from there.

1

Even some basic examples as guidance would be very helpful.

Any way to run it under gulp ?

@christophe-g
You could try gulp-web-component-shards,
again, documentation is a little thin.
I'm using this atm.
var gulp       = require('gulp');
var wcs = require('gulp-web-component-shards');

gulp.task('shard', function() {
    return gulp.src('src/build/*.html', { base: 'src', read: false })
      .pipe(wcs({
        root: 'src',
        shared: 'shared.html',
        bower_components: 'bower_components',
        work: 'tmp/web-component-shards',
      }))
      .pipe(gulp.dest('./dist'));
});

My build folder contains several html files that are just lists of imports, the dependencies for my various endpoints...


Could the procedure SetSumLinesFilter in table 5767 "Warehouse Activity Line" be set to external?

In table 5767 "Warehouse Activity Line" procedure SetSumLinesFilter is [Scope('OnPrem')].
Could this be removed?
Thanks

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


database: use preset random password for pg12

Previously the bitnami/postgresql helm template was picking a random password.  That password ends up on the persistent data volume and can fall out-of-sync in circumstances where helm resets the k8s secret.  When that happens, the backup jobs will fail because their  password from the k8s secret is no longer honored.
Avoid the out-of-sync condition by just generating a password and manually creating the k8s secret.

bors r+


chore: add perf improvements

Thanks for this, but I'd rather not be adding even more dependencies to the project just now. I'm sure our CSS could be better, but a full review of our compilation process is probably a better time to add these steps.

Thanks for this, but I'd rather not be adding even more dependencies to the project just now. I'm sure our CSS could be better, but a full review of our compilation process is probably a better time to add these steps.

I think User experience should be in favor instead of developer experience. If we manage to ship less code to the user, that is always a plus. I ask you to reconsider


Template typescript-webpack does not startup correctly

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Forge Version:

6.0.0-beta.47

Electron Version:

7.1.7

Operating System:

macOS 10.14.6

Last Known Working Electron Forge version::

n/a

Expected Behavior
After a fresh install with the typescript-webpack template the application should start without error.
Actual Behavior
The app does not start, only showing an alert box. The CLI shows:
$ electron-forge start
✔ Checking your system
✔ Locating Application
✔ Preparing native dependencies
✔ Compiling Main Process Code
⠋ Launch Dev ServersStarting type checking service...
Using 1 worker with 2048MB memory limit
✔ Launch Dev Servers
✔ Compiling Preload Scripts
✔ Launching Application

Webpack Output Available: http://localhost:9000

App threw an error during load
Error: Module parse failed: Unexpected token (2:8)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import { app, BrowserWindow } from 'electron';
> declare const MAIN_WINDOW_WEBPACK_ENTRY: any;
|
| // Handle creating/removing shortcuts on Windows when installing/uninstalling.
    at Object../src/index.ts (/Users/fs/Workspaces/playground/electronforge-typescript-webpack/.webpack/main/index.js:97:7)
    at __webpack_require__ (/Users/fs/Workspaces/playground/electronforge-typescript-webpack/.webpack/main/index.js:21:30)
    at /Users/fs/Workspaces/playground/electronforge-typescript-webpack/.webpack/main/index.js:85:18
    at Object.<anonymous> (/Users/fs/Workspaces/playground/electronforge-typescript-webpack/.webpack/main/index.js:88:10)
    at Module._compile (internal/modules/cjs/loader.js:880:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:892:10)
    at Module.load (internal/modules/cjs/loader.js:735:32)
    at Module._load (internal/modules/cjs/loader.js:648:12)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
webpack built 8864fef2c8c472658968 in 3507ms

To Reproduce
The project was built via yarn create electron-app electronforge-typescript-webpack --template=typescript-webpack
Additional Information
n/a

I can't reproduce this on Linux, although I'm running yarn start instead of electron-forge start because otherwise you're using the globally installed version instead of the locally installed version, which may differ.

Thanks for reaching back. I just saw that there was something missing from the pasted output:
➜ yarn start
yarn run v1.21.1
$ electron-forge start
...

so I'm also running this via Yarn.
I made a yarn global upgrade before running the scaffolding. The Webpack config does also look OK. Unfortunately I wasn't able to find a way to dump what loaders are registered with Webpack.
The globally installed packages are:
➜ yarn global list
yarn global v1.21.1
info<EMAIL_ADDRESS>has binaries:
   - create-electron-app
info<EMAIL_ADDRESS>has binaries:
   - esy
✨  Done in 0.81s.

I tried to set it up multiple times to no success so far. I will test it on a fresh Linux install though to verify further.

I ran it on a VM with Ubuntu 19.04.
$ yarn global list
yarn global v1.17.3
Done in 0.15s.

No global stuff installed.
$ yarn create electron-app electronforge-typescript-webpack --template=typescript-webpack
yarn create v1.17.3
[1/4] Resolving packages...
warning create-electron-app > @electron-forge/cli > @electron-forge/core > nugget > progress-stream > through2 > xtend ><EMAIL_ADDRESS>
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
warning Your current version of Yarn is out of date. The latest version is "1.21.1", while you're on "1.17.3".
info To upgrade, run the following command:
$ curl --compressed -o- -L https://yarnpkg.com/install.sh | bash
success Installed<EMAIL_ADDRESS>with binaries:
      - create-electron-app
✔ Initializing Project Directory
✔ Initializing Git Repository
✔ Locating custom template: "typescript-webpack"
✔ Copying Starter Files
✔ Initializing NPM Module
✔ Setting up Forge configuration
✔ Setting up TypeScript configuration
✔ Installing Template Dependencies
✔ Installing NPM Dependencies
Done in 131.37s.

$ yarn global list
yarn global v1.17.3
info<EMAIL_ADDRESS>has binaries:
   - create-electron-app
Done in 1.45s.

$ yarn start
yarn run v1.17.3
$ electron-forge start
✔ Checking your system
✔ Locating Application
✔ Preparing native dependencies
✔ Compiling Main Process Code
⠋ Launch Dev ServersStarting type checking service...
Using 1 worker with 2048MB memory limit
✔ Launch Dev Servers
✔ Compiling Preload Scripts
✔ Launching Application

Webpack Output Available: http://localhost:9000

App threw an error during load
Error: Module parse failed: Unexpected token (2:8)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import { app, BrowserWindow } from 'electron';
> declare const MAIN_WINDOW_WEBPACK_ENTRY: any;
|
| // Handle creating/removing shortcuts on Windows when installing/uninstalling.
    at Object../src/index.ts (/home/fs/Workspaces/electronforge-typescript-webpack/.webpack/main/index.js:97:7)
    at __webpack_require__ (/home/fs/Workspaces/electronforge-typescript-webpack/.webpack/main/index.js:21:30)
    at /home/fs/Workspaces/electronforge-typescript-webpack/.webpack/main/index.js:85:18
    at Object.<anonymous> (/home/fs/Workspaces/electronforge-typescript-webpack/.webpack/main/index.js:88:10)
    at Module._compile (internal/modules/cjs/loader.js:880:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:892:10)
    at Module.load (internal/modules/cjs/loader.js:735:32)
    at Module._load (internal/modules/cjs/loader.js:648:12)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Module parse failed: Unexpected token (2:8)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import { app, BrowserWindow } from 'electron';
> declare const MAIN_WINDOW_WEBPACK_ENTRY: any;
|
| // Handle creating/removing shortcuts on Windows when installing/uninstalling.
    at Object../src/index.ts (/home/fs/Workspaces/electronforge-typescript-webpack/.webpack/main/index.js:97:7)
    at __webpack_require__ (/home/fs/Workspaces/electronforge-typescript-webpack/.webpack/main/index.js:21:30)
    at /home/fs/Workspaces/electronforge-typescript-webpack/.webpack/main/index.js:85:18
    at Object.<anonymous> (/home/fs/Workspaces/electronforge-typescript-webpack/.webpack/main/index.js:88:10)
    at Module._compile (internal/modules/cjs/loader.js:880:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:892:10)
    at Module.load (internal/modules/cjs/loader.js:735:32)
    at Module._load (internal/modules/cjs/loader.js:648:12)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
webpack built 8864fef2c8c472658968 in 5931ms


MUMUP-2057 : Fix loading forever issue if you have help in your layout

Fixed loading forever
Fixed mock data for weather icons as my-test.doit.wisc.edu no longer exists

:+1:


Time to event pretraining support

MOTOR uses time to event prediction, this can get rid of the issue of rare events being ignored and prevalent events dominating the autoregressive loss.

This is basically addressed by the triplet and eic autoregressive models


[otexplorer] Panic when accessing COLR.version

$ cargo r /Users/drott/dev/color-fonts/build/test_glyphs-glyf_colr_1.ttf -q COLR.version
     Running `/Users/drott/dev/fontations/target/debug/otexplorer /Users/drott/dev/color-fonts/build/test_glyphs-glyf_colr_1.ttf -q COLR.version`
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', read-fonts/src/tables/../../generated/generated_colr.rs:275:42

While for example
$ cargo r /Users/drott/dev/color-fonts/build/test_glyphs-glyf_colr_1.ttf -q post.version
$ cargo r /Users/drott/dev/color-fonts/build/test_glyphs-glyf_colr_1.ttf -q hhea.version

work fine.

Hmm, it looks like the problem is related to the fields on the COLR table that are both versioned and allowed to be null, and the otexplorer code is assuming that if the version matches then the field is present.
The code that underpins this traversal business is a bit nasty; it worked for a demo but I'm going to need to figure out a more principled (and more maintainable) approach if it's going to be actually useful in the long term.

Low priority IMHO, unless ... would one need the traversal bits to walk the COLR graph? Or would the recommended approach be to just code that directly?

I would code that directly, and if it starts to feel onerous we can explore some more general approach.

I'm inclined to think this suggests deletion of the traversal code then?

I would lean in that direction, but I think for the time being at least the otexplorer tool is genuinely useful, so I would hold off deleting until we make some change to codegen that breaks everything.


Layout Issue - Header is Hidden

I've got an issue with the page layout:
In Safari 8.0.3, I navigate to Services for example, I get the list of services, however if I scroll up I can see a header with "Services" and an add button to the right side. I cannot get it to show completely however, I "rubber bands" back up below the top bar.
In Chrome 40.0.2214.111 and Firefox 35.0.1 the content doesn't scroll so that section isn't displayed at all. The section is the dom though but it's covered by the bar.
I'm using OS X Yosemite.

I can't replicate this, sorry. Maybe there's some issue with the build process on your instance and the less file (static/arachnys/css/base.less) isn't getting compiled by django-compressor?

I checked and the file is in the static folder where the files get compressed.
The rest of the layout is fine, it's just this small issue that is happening.


stm32/stm32_spi: Add SPI register definitions for STM32G47xxx

Summary
arch/arm/src/stm32/hardware/stm32_spi.h:

Handle register variations for STM32G47xxx.
Handle STM32G47xxx in conditional logic.
Make conditional logic for I2S and TI frame format mode more self-documenting by creating HAVE_SPI_I2S and HAVE_SPI_TI_MODE defines.
Fix nxstyle errors.

Impact
Allows STM32G47xxx MCUs to gain SPI support.
Testing
nxstyle.

On Wed, Nov 11, 2020 at 7:27 AM David Sidrane<EMAIL_ADDRESS>wrote:

@davids5 requested changes on this pull request.
What is value in having this in Kconfig?
In arch/arm/src/stm32/Kconfig
https://github.com/apache/incubator-nuttx/pull/2273#discussion_r521322607
:

@@ -2417,6 +2417,22 @@ config STM32_HAVE_IP_DMA_V2
bool
default n

+config STM32_HAVE_IP_SPI_V1
These are data sheet dependent and invariant. Why not encapsulate it in
the chip.h? Leaving it up the the end user requires them to do work that
was already done when an new SoC is added.

The end user does not have to do anything. For all the STM32 chips,
peripheral IP versions are selected in Kconfig. See the similar
automatically-selected configs for other peripherals' versions. Putting
this one in chip.h would be a departure from how it is already being done
for all other peripherals.

putting this one in chip.h would be a departure from how it is already being done
for all other peripherals.

Just like removing all the ifdef rash, departures form incorrect are a good thing. Putting invariant in Kconfig is not a proper use for it. The Chip file describes the number and version of IP. It is invariant.  The IP on a chip does not change.
It makes sense for the Device subfamily,  Flash memory size, and Package etc.

It does not make sense for the IP on the die.

putting this one in chip.h would be a departure from how it is already being done
for all other peripherals.

Just like removing all the ifdef rash, departures form incorrect are a good thing. Putting invariant in Kconfig is not a proper use for it. The Chip file describes the number and version of IP. It is invariant. The IP on a chip does not change.

Fair enough. Since this PR is for the stm32-spi.h file, I will move the SPI IP version from Kconfig to chip.h. Those for other peripherals will need to be refactored in separate PRs.

@hartmannathan  Looking good! how about a squash and force push before we review it?

@hartmannathan Looking good! how about a squash and force push before we review it?

Yes. As soon as the tests finish I'll squash it

@davids5 Ok it's squashed and force pushed... Give it one last lookover and if it looks good, do the honors!

I don't think we can move all IP version configurations to chip.h. Peripherals functionality depends on the IP version and this information is needed in Kconfig (eg. the number of PWM channels or ADC DMA mode). If we can't move everything to chip.h, does that still make sense ?

I don't think we can move all IP version configurations to chip.h. Peripherals functionality depends on the IP version and this information is needed in Kconfig (eg. the number of PWM channels or ADC DMA mode). If we can't move everything to chip.h, does that still make sense ?

I think so. One is a user choice for configuration. I have a board that use 2 PWM or I want to use the ADC DMA in XXX mode.
There other is invariant it is the version of IP on the die. The users choice does can not change the IP version in the the chip.

There other is invariant it is the version of IP on the die. The users choice does can not change the IP version in the the chip.

You have to know the IP version first and then expose the available resources to the user in Kconfig. If Kconfig doesn't know the IP version, it cannot show the user the available options.
eg.
config STM32_TIM1_CHANNEL5
	bool "TIM1 Channel 5 (internal)"
	default n
	depends on STM32_HAVE_IP_TIMERS_V2
	---help---
		Enables channel 5 (no available externaly)

@raiden00pl - Got it. Thank you for the example.   I think the register case is different.

@davids5 @raiden00pl I have the pre-squashed version where I was setting the IP version in Kconfig. If it's better to reinstate that code, let me know and I'll open a separate PR.

@hartmannathan - Do you envision the SPI IP version will enable a user choice? As the roll up of CONFIG_HAVE_TIMER5 into STM32_HAVE_IP_TIMERS_V2 does?

@hartmannathan - Do you envision the SPI IP version will enable a user choice? As the roll up of CONFIG_HAVE_TIMER5 into STM32_HAVE_IP_TIMERS_V2 does?

The only one I can think of is whether you want to use the SPI block as I2S. It has a mode like that in the newer IP versions. I don't know if we even handle or support that.
The larger concern for me is consistency and maintenance. I'd rather avoid having some IP versions defined in one location and others defined in another location, if feasible to keep the logic in one place.
But I don't have a strong opinion. I'm okay with it as it is now, or back in Kconfig. Either option is fine by me.

I agree that the main problem with the current solution is consistency. But the next problem I see is less flexibility.
If in the future ST introduces some new functionality to SPI which must be configurable in Kconfig, then we have a problem.
Therefore, I believe that it is better to keep all IP versions in Kconfig, even it it is not a perfect solution.

@raiden00pl - theses are all good arguments.  On the consistency aspect: Shall we do away with chip.h and move all the information to Kconfig? (remember that Kconfig was added later in the nuttix time line.)

@davids5 It could be good. I think we already have almost all the necessary information in Kconfig, directly or indirectly.
The only problem here is the STM32_NGPIO definitions. Moving these to Kconfig will add a lot of new lines to a file that is already quite large.


Attempt to call field 'get_clients' (a nil value)

Hi!
I'm getting the following error when trying to change the scheme (amongst others).
I did some googling and apparently this might not be xcodebuild-related, but I was hoping that you might have some pointers anyway?
Updating project settings...
...lazy/xcodebuild.nvim/lua/xcodebuild/integrations/lsp.lua:47: attempt to call field 'get_clients' (a nil value)
stack traceback:
^I...lazy/xcodebuild.nvim/lua/xcodebuild/integrations/lsp.lua:47: in function 'restart_sourcekit_lsp'
^I....nvim/lua/xcodebuild/integrations/xcode-build-server.lua:32: in function <....nvim/lua/xcodebuild/integrations/
xcode-build-server.lua:31>
Project settings updated

Huh. vim.lsp.get_clients does indeed seem to be missign on my side. I'm using Neovim 0.9.5, i.e., the current Homebrew version. Seeing nothing suspicious in :checkhealth either.

It turns out that actually, it's available in the new version of Neovim (nightly build). I thought it's also available in 0.9.5. Weird that nobody reported it :D I will have to migrate it to something that is available in 0.9.5

It's a pitty that the documentation doesn't mention in which version the specific function is available:
https://neovim.io/doc/user/lsp.html#vim.lsp.get_clients()

I was going to say that it works with Homebrew's HEAD version of Neovim! 😄
Apparently, vim.lsp.get_clients() is supposed to replace vim.lsp.get_active_clients()and vim.lsp.buf_get_clients()anyway:
https://neovim.io/doc/user/deprecated.html
I'll stick with the nightly for now. Maybe you can avoid a change if 0.1.0 becomes the stable version soon - don't know what Neovim's release plan's are ...

Ah, Neovim version 0.10 is due on May 7: https://github.com/neovim/neovim/milestone/36

I think I should support at least 0.9.5, so I will provide the fix  :). It shouldn't be a big problem :).

Brilliant! Thanks for your help on this!


Move JvmVersionDetector down into global client services and Gradle home services

Context

Contributor Checklist

[ ] Review Contribution Guidelines.
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[ ] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test QFL

@bot-gradle test QFL

I've triggered the following builds for you. Click here to see all build failures.

Quick Feedback - Linux Only (Trigger) (Check)

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)

@bot-gradle merge

The merge queue build has failed. Click here to see all failures.

The merge queue build has failed. Click here to see all failures.

@bot-gradle test RfN

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)

I've triggered the following builds for you. Click here to see all build failures.

Ready for Nightly (Trigger) (Check)

@bot-gradle merge

The merge queue build has failed. Click here to see all failures.

@bot-gradle merge

@bot-gradle merge


the "plugins" field in presets need to be an object

When i am migrating from eslintrc to flat config, i got the following error
> eslint .

Oops! Something went wrong! :(

ESLint: 9.2.0

A config object has a "plugins" key defined as an array of strings.

Flat config requires "plugins" to be an object in this form:

    {
        plugins: {
            import-x: pluginObject
        }
    }

Please see the following page for information on how to convert your config object into the correct format:
https://eslint.org/docs/latest/use/configure/migration-guide#importing-plugins-and-custom-parsers

If you're using a shareable config that you cannot rewrite in flat config format, then use the compatibility utility:
https://eslint.org/docs/latest/use/configure/migration-guide#using-eslintrc-configs-in-flat-config

 ELIFECYCLE  Command failed with exit code 2.

After some research, i found the "plugins" key is defined in recommended preset:
https://github.com/un-ts/eslint-plugin-import-x/blob/8b53954f94f528b20e810f26cc562442761cf85d/src/config/recommended.ts#L7
Is it supposed to be a virtual plugin or a module? I'm glad to help improving it.

Full code example
import pluginImportX from "eslint-plugin-import-x";

export const imports = [
  pluginImportX.configs.recommended,
  pluginImportX.configs.typescript,
  {
    plugins: {
      import: pluginImportX,
    },
    rules: {
      "import-x/no-named-as-default": "off",
      "import-x/no-unresolved": ["error", { ignore: ["^virtual:"] }],
      "import-x/order": [
        "error",
        {
          groups: [
            "builtin",
            "external",
            "internal",
            "parent",
            "sibling",
            "index",
          ],
          pathGroups: [
            { pattern: "vue", group: "builtin", position: "before" },
          ],
          pathGroupsExcludedImportTypes: [],
          "newlines-between": "always",
          alphabetize: {
            order: "asc",
          },
        },
      ],
    },
  },
];

export default [
  ...imports
];

The configs does not support flat config yet, see also #29
But you can config it manually by not using the configs
import pluginImportX from "eslint-plugin-import-x";

export default [
  {
    plugins: {
      import: pluginImportX
    },
    rules: {
      "import/order": ["error"] // make sure to use same prefix as you defined above in `plugins`
    }
  }
]


Ability to reduces charges on armor upgrades such as jet pack.

Currently you can put a jetpack or haste circuit under the armor. I see no way to click it through the various usage options to get it to drain the charge count outside of opening the item and then reducing the number manually.
Ideally you can just click the nestled jetpack icon and it reduces the charge by the specified amount in the item usage.

This would be a great addition to using the item to reduce the charges instead of opening the item to reduce the charges.


[shell] feat: close event on child process

it could be awesome if this plugin get an event on closed child.
https://doc.rust-lang.org/std/process/struct.Child.html#method.wait

The command does emit a close event: https://v2.tauri.app/reference/javascript/shell/#example-1
Is that what you're asking for?

Not at all, close event for spawned child process, not command

https://github.com/tauri-apps/plugins-workspace/pull/1947


I miss NodeGit.Odb.prototype.addDiskAlternate

We're using NodeGit.Odb.prototype.addDiskAlternate in https://github.com/twosigma/git-meta.  Until this is replaced, we can't upgrade to 0.24.
Thanks.

I'll make sure this gets back in. Thanks for letting me know.

Any word on this?

Thanks for the reminder! I've opened a branch for fixing this in 0.25.0.

Woot, thanks!


Spotify Update Shuts Down Skin

I've installed Spotio but the auto update on Spotify keeps getting rid of the skin. I've tried methods of stopping Spotify's auto update but to no avail.

Yeah, I'm not even sure if it's auto-update at this point, as I receive the message to restart to actually perform the update after Spotio force-closes (which happens maybe < 30 seconds into the first open). Tried patching with a script to prevent auto-updates, which stopped the message from appearing, but the app still crashed and re-opened to the original dark color scheme.

Is there any chance to get the Skin work again? I really like the design of the Spotio App. I hope there will be any solution very soon.

Hey everyone —
Spotify does auto-update; they broke the vulnerability I was using to inject Spotio no more than a week after Spotio was originally released. I still don't have the time to get Spotio up and running again (it is doable, and I have a lot of good ideas for what to do with it once it's working again), though.
If any of you have spare time and want tot take a crack at re-injecting Spotio reliably through some script or installer, that's the first major roadblock to getting Spotio up and running again.

FYI,
Spotio still works with arch. I'm running it now.

I was having the same issue - and I partially fixed it. I used this script to try and fix it, then I went into "Get Info" (I'm using Mac OSX) and Locked the app. Now it crashes every 30 seconds or so, but it doesn't revert to the old spotify skin.
I love this project and would really like to have a working version - It looks amazing.

I'd still like to get this project working again, but definitely don't have the time to do this myself.
If any of you technical users who like Spotio and want to see it working again would like to submit a pull request to help fix this issue, that would be extremely appreciated.


Allow running appleseed.studio unit tests from the command line

appleseed.studio has a few unit tests. The only way currently to execute them is from appleseed.studio's Tests dialog. It would be useful to be able to run those tests from the command line, for instance for AppVeyor builds.

I can try tackle this one for macos and linux builds.


feat: Add switzerland UID validation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


#31 change repr for symbol to class(id, name, parent expression)

Description
Fixes #31  (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Key checklist:

[x] No style issues: $ flake8
[x] All tests pass: $ python run-tests.py --unit
[x] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works
[ ] Any dependent changes have been merged and published in downstream modules

Codecov Report

Merging #41 into master will increase coverage by 2.7%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master      #41     +/-   ##
=========================================
+ Coverage   68.38%   71.09%   +2.7%
=========================================
  Files          27       27
  Lines         737      851    +114
=========================================
+ Hits          504      605    +101
- Misses        233      246     +13

Impacted Files
Coverage Δ

pybamm/expression_tree/symbol.py
95.23% <100%> (+2.38%)
:arrow_up:

pybamm/discretisations/finite_volume_meshes.py
100% <0%> (ø)
:arrow_up:

pybamm/parameters/base_parameter_values.py

pybamm/parameters/parameters.py
86.07% <0%> (ø)

pybamm/parameters/functions_lead_acid.py
50% <0%> (+5.88%)
:arrow_up:

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 182c3f1...320d709. Read the comment docs.


fix: something if you want to do

#30  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @IWANABETHATGUY and the rest of your teammates on  Graphite


OracleDatabase: Data persistence does not work.

here are the steps to reproduce the issue
docker run --name oracle19c -p 1521:1521 -p 5500:5500 -e ORACLE_PDB=orcl -e ORACLE_PWD=PssW0rd -e ORACLE_MEM=4000 -v /mnt/d/Docker/volumes/oracle:/opt/oracle/oradata -d oracle/database:19.3.0-ee
Wait until the database is fully created.  then, run a test connection from the host machine.
sqlplus SYS/PssW0rd@localhost:1521/ORCLCDB as Sysdba
alter session set container="ORCL";
everything works as expected.
then shut the container down; then remove it.
docker container stop oracle19c
docker rm oracle19c
now run the container again
docker run --name oracle19c -p 1521:1521 -p 5500:5500 -e ORACLE_PDB=orcl -e ORACLE_PWD=PssW0rd -e ORACLE_MEM=4000 -v /mnt/d/Docker/volumes/oracle:/opt/oracle/oradata -d oracle/database:19.3.0-ee
now try to run a test in the host  machine again.
sqlplus SYS/PssW0rd@localhost:1521/ORCLCDB as Sysdba
ERROR:
ORA-01017: invalid username/password; logon denied
Why is the sys password not persisted after the first run?

First time using this and I accidentally close the issue.

First time using this and I accidentally close the issue.

I believe your issue is you removed the docker container rather than just stopping it.
To maintain persistence you would need to use;
docker stop oracle19c

Same issue here. I removed the container (I wasn't needing it but needed the disk space). Then when I re-created the container, all of my pluggable databases were gone, incl. the XEPDB1 pluggable database that came with the image:
The Oracle base remains unchanged with value /opt/oracle
#####################################
########### E R R O R ###############
DATABASE SETUP WAS NOT SUCCESSFUL!
Please check output for further info!
########### E R R O R ###############
#####################################
The following output is now a tail of the alert.log:
Crash Recovery excluding pdb 2 which was cleanly closed.
2021-05-12T09:20:43.043896+00:00
Errors in file /opt/oracle/diag/rdbms/xe/XE/trace/XE_ora_111.trc:
ORA-01157: cannot identify/lock data file 26 - see DBWR trace file
ORA-01110: data file 26: '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_DATA.DBF'
2021-05-12T09:20:43.074219+00:00
Errors in file /opt/oracle/diag/rdbms/xe/XE/trace/XE_ora_111.trc:
ORA-01157: cannot identify/lock data file 26 - see DBWR trace file
ORA-01110: data file 26: '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_DATA.DBF'
ORA-1157 signalled during: ALTER DATABASE OPEN...
2021-05-12T09:20:44.352713+00:00
Errors in file /opt/oracle/diag/rdbms/xe/XE/trace/XE_mz00_134.trc:
ORA-01110: data file 26: '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_DATA.DBF'
ORA-01565: error in identifying file '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_DATA.DBF'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2021-05-12T09:20:44.566950+00:00
Errors in file /opt/oracle/diag/rdbms/xe/XE/trace/XE_mz00_134.trc:
ORA-01110: data file 27: '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_INDEX.DBF'
ORA-01565: error in identifying file '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_INDEX.DBF'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2021-05-12T09:20:44.733097+00:00
Errors in file /opt/oracle/diag/rdbms/xe/XE/trace/XE_mz00_134.trc:
ORA-01110: data file 28: '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_TRACE.DBF'
ORA-01565: error in identifying file '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_TRACE.DBF'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
2021-05-12T09:20:44.908035+00:00
Errors in file /opt/oracle/diag/rdbms/xe/XE/trace/XE_mz00_134.trc:
ORA-01110: data file 29: '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_TRACE_INDEX.DBF'
ORA-01565: error in identifying file '/opt/oracle/product/18c/dbhomeXE/dbs/MCL_TRACE_INDEX.DBF'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
Checker run found 4 new persistent data failures
2021-05-12T09:24:07.973357+00:00
XEPDB1(3):ALTER PLUGGABLE DATABASE XEPDB1 REFRESH
XEPDB1(3):ORA-65261 signalled during: ALTER PLUGGABLE DATABASE XEPDB1 REFRESH...
2021-05-12T09:24:19.951737+00:00
XEPDB1(3):ALTER PLUGGABLE DATABASE XEPDB1 OPEN READ WRITE
XEPDB1(3):ORA-65054 signalled during: ALTER PLUGGABLE DATABASE XEPDB1 OPEN READ WRITE...

Moreover, I stored the database file at the volume share /opt/oracle/oradata. Why does Oracle Database 18c XE now claim they were stored somewhere else?

I would say that this limitation is rather annoying in case of docker-compose - if you forget to --no-recreate in the query, it may decide to recreate the container by default.
Is this just a matter of file hierarchy - i.e. could this be fixed by making some other folders in /opt/oracle persistent?

Unfortunately there's no progress here. My Docker Desktop installed an update today, and afterwards the Oracle container won't come up. So I have to drop the volume and create everything from scratch.

I have the same issue with image container-registry.oracle.com/database/enterprise:<IP_ADDRESS>.
I use the following command:
docker run -d -p 1521:1521 -e DB_PASSWD=password123456% -e ENABLE_ARCHIVELOG=true -v /c/oracleDb:/opt/oracle/oradata --name OracleDb container-registry.oracle.com/database/enterprise:<IP_ADDRESS>

When I create a new database instance, it shows up in the specified folder C:\OracleDB. I can also connect to the created database instance. However, after the container is restarted, I am not able to reconnect to the created database instance. Then, I manually delete the database instance from C:\OracleDB and start from scratch.

@hschink DB_PASSWD is not the correct env var. It is ORACLE_PWD

@hschink DB_PASSWD is not the correct env var. It is ORACLE_PWD

@yunus-qureshi This is currently working on my machine. As written above, the setup works but loses the connection to the database instance as soon as the container is restarted.

Is there any fix for this? I currently have a volume filled with data that I cant use because the recreated container thinks my schemes are in his local /opt/oracle/product/19c/dbhome_1/dbs. Would really like to get around setting it all up again.

@TheUltragon paste the full docker cmd line and the entire docker log output

Docker Log:
https://gist.github.com/TheUltragon/316beb76bbaa47edd07c2bfa3d7639b9
Docker Command:
docker run --name OracleDbContainer -p 1521:1521 -p 5500:5500 -e ORACLE_SID=ORCLCDB -e ORACLE_PDB=ORCLPDB1 -v OracleDbVolume:/opt/oracle/oradata oracle/database:19.3.0-ee

Same Log for me. I'm using docker-compose like this:
version: '2.4'
services:
  devdb:
    image: oracle/database:19.3.0-ee
    mem_limit: 2G
    environment:
      - ORACLE_SID=ORCL
      - ORACLE_PDB=MYPDB
      - ORACLE_PWD=123_myPass
      - ORACLE_EDITION=enterprise
    volumes:
      - oradata:/opt/oracle/oradata
      - d:\docker\oracle19\dumps:/ORCLDMP
    ports:
      - 11521:1521
      - 15500:5500
volumes:
  oradata:
    external: false

Any updates on this?

It might be the ownership problem, so look at https://github.com/oracle/docker-images/blob/main/OracleDatabase/SingleInstance/FAQ.md#cannot-create-directory-error-when-using-volumes and https://medium.com/oracledevs/making-oracle-database-persistent-with-docker-bb186a08e965
For me the problem was, that I built non-CBD database (with changed configuration in dbca.rsp.tmpl file: createAsContainerDatabase=false and numberOfPDBs=0 and build using the buildContainerImage.sh script). Apart from the directory ownership problem, the Oracle prebuild image (CBD) seems to be working fine.

Problem still exists with 23C FREE when you remove the container. Stopping/Starting work fine. As soon as the container is removed and recreated again, the container will run indefinitely as unhealthy and oracle will fail to start properly.
Run command:
podman run --name oradb -p 1521:1521 \
    -v /var/lib/oracledb/test:/opt/oracle/oradata:Z \
    --user 54321:54321 \
    -e ORACLE_PWD=Testpa$$word \
    -e ORACLE_CHARACTERSET=AL32UTF8 \
    container-registry.oracle.com/database/free:<IP_ADDRESS>

Host perms for mounted dir:
# ls -al /var/lib/oracledb/test
total 0
drwxr-xr-x. 2 54321 54321  6 Sep 21 10:58 .
drwxr-xr-x. 4 root  root  30 Sep 21 10:58 ..

Error in container after removing (podman stop; podman rm) and recreating the container with the same run command:
The Oracle base remains unchanged with value /opt/oracle
#####################################
########### E R R O R ###############
DATABASE SETUP WAS NOT SUCCESSFUL!
Please check output for further info!
########### E R R O R ###############
#####################################
The following output is now a tail of the alert.log:

XDB initialized.
ALTER PLUGGABLE DATABASE FREEPDB1 SAVE STATE
Completed: ALTER PLUGGABLE DATABASE FREEPDB1 SAVE STATE
2023-08-02T07:04:05.971617+00:00
ALTER SYSTEM SET control_files='/opt/oracle/oradata/FREE/control01.ctl' SCOPE=SPFILE;
2023-08-02T07:04:06.004362+00:00
ALTER SYSTEM SET local_listener='' SCOPE=BOTH;
ALTER PLUGGABLE DATABASE FREEPDB1 SAVE STATE
Completed: ALTER PLUGGABLE DATABASE FREEPDB1 SAVE STATE

Error from client:
ORA-12514: Cannot connect to database. Service FREE is not registered with the
listener at host REDACTED port 1521

Deleting the contents of the host mount (/var/lib/oracledb/test), allows for the container to start properly after creating the DB for the first time again and files are populated in (/var/lib/oracledb/test)

My initial thought was use of the :Z option was uniquely labeling the volume and preventing subsequent containers from accessing it, but I'm unable to reproduce this on OEL8. Perhaps try it with the :z option instead and see if that works? Maybe an SELinux setting?
Create the data directory:
sudo mkdir -p /oradata/test
sudo chown -R opc:154320 /oradata/test
sudo chmod 774 /oradata/test

The group ID assigned above is the subgid used by the container process:
# cat /etc/subuid
opc:100000:65536
# cat /etc/subgid
opc:100000:65536

Create the container (run as a detached process and without the port mapping or environment variables for simplicity):
# podman run -d --name oradb \
>     --user 54321:54321 \
>     -v /oradata/test:/opt/oracle/oradata:Z \
>     container-registry.oracle.com/database/free:<IP_ADDRESS>
# podman logs -f oradb

Last lines of the log show the database created successfully:
SQL> SQL> Disconnected from Oracle Database 23c Free Release <IP_ADDRESS>.0 - Develop, Learn, and Run for Free
Version <IP_ADDRESS>.09
The Oracle base remains unchanged with value /opt/oracle
The Oracle base remains unchanged with value /opt/oracle
#########################
DATABASE IS READY TO USE!
#########################
The following output is now a tail of the alert.log:
FREEPDB1(3):ALTER DATABASE DEFAULT TABLESPACE "USERS"
FREEPDB1(3):Completed: ALTER DATABASE DEFAULT TABLESPACE "USERS"
ALTER PLUGGABLE DATABASE FREEPDB1 SAVE STATE
Completed: ALTER PLUGGABLE DATABASE FREEPDB1 SAVE STATE
2023-09-25T21:02:08.974224+00:00
ALTER SYSTEM SET control_files='/opt/oracle/oradata/FREE/control01.ctl' SCOPE=SPFILE;
2023-09-25T21:02:08.999944+00:00
ALTER SYSTEM SET local_listener='' SCOPE=BOTH;
ALTER PLUGGABLE DATABASE FREEPDB1 SAVE STATE
Completed: ALTER PLUGGABLE DATABASE FREEPDB1 SAVE STATE

All files are present:
# sudo ls -la
total 8
drwxrwxr--. 4 opc    154320   55 Sep 25 21:02 .
drwxrwxr--. 3 opc    opc      18 Sep 25 20:42 ..
drwxr-xr-x. 3<PHONE_NUMBER>20   18 Sep 25 21:02 dbconfig
drwxr-x---. 4<PHONE_NUMBER>20 4096 Sep 25 20:57 FREE
-rw-r--r--. 1<PHONE_NUMBER>20   26 Sep 25 21:02 .FREE.created
# sudo ls -la dbconfig/
total 0
drwxr-xr-x. 3<PHONE_NUMBER>20  18 Sep 25 21:02 .
drwxrwxr--. 4 opc    154320  55 Sep 25 21:02 ..
drwxr-xr-x. 2<PHONE_NUMBER>20 117 Sep 25 21:02 FREE
# sudo ls -la dbconfig/FREE/
total 24
drwxr-xr-x. 2<PHONE_NUMBER>20  117 Sep 25 21:02 .
drwxr-xr-x. 3<PHONE_NUMBER>20   18 Sep 25 21:02 ..
-rw-r-----. 1<PHONE_NUMBER>20  448 Sep 25 21:02 listener.ora
-rw-r-----. 1<PHONE_NUMBER>20 2048 Sep 25 20:57 orapwFREE
-rw-r--r--. 1<PHONE_NUMBER>20  779 Sep 25 21:02 oratab
-rw-r-----. 1<PHONE_NUMBER>20 2560 Sep 25 21:02 spfileFREE.ora
-rw-r-----. 1<PHONE_NUMBER>20   69 Sep 25 21:02 sqlnet.ora
-rw-r-----. 1<PHONE_NUMBER>20  690 Sep 25 21:02 tnsnames.ora
# sudo ls -la FREE
total 2362192
drwxr-x---. 4<PHONE_NUMBER>20       4096 Sep 25 20:57 .
drwxrwxr--. 4 opc    154320         55 Sep 25 21:02 ..
-rw-r-----. 1<PHONE_NUMBER>20   18759680 Sep 25 21:04 control01.ctl
-rw-r-----. 1<PHONE_NUMBER>20   18759680 Sep 25 21:04 control02.ctl
drwxr-x---. 2<PHONE_NUMBER>20        104 Sep 25 21:02 FREEPDB1
drwxr-x---. 2<PHONE_NUMBER>20         85 Sep 25 20:57 pdbseed
-rw-r-----. 1<PHONE_NUMBER>20  209715712 Sep 25 21:04 redo01.log
-rw-r-----. 1<PHONE_NUMBER>20  209715712 Sep 25 21:01 redo02.log
-rw-r-----. 1<PHONE_NUMBER>20  209715712 Sep 25 21:01 redo03.log
-rw-r-----. 1<PHONE_NUMBER>20  587210752 Sep 25 21:01 sysaux01.dbf
-rw-r-----. 1<PHONE_NUMBER>20<PHONE_NUMBER> Sep 25 21:01 system01.dbf
-rw-r-----. 1<PHONE_NUMBER>20   20979712 Sep 25 21:01 temp01.dbf
-rw-r-----. 1<PHONE_NUMBER>20   47194112 Sep 25 21:01 undotbs01.dbf
-rw-r-----. 1<PHONE_NUMBER>20    5251072 Sep 25 21:01 users01.dbf

Remove the container and recreate it:
# podman ps -a
CONTAINER ID  IMAGE                                                 COMMAND               CREATED         STATUS                                PORTS       NAMES
1279eb7e38d9  container-registry.oracle.com/database/free:<IP_ADDRESS>  /bin/bash -c $ORA...  10 minutes ago  Exited (130) 5 seconds ago (healthy)              oradb
# podman rm -f oradb
oradb
# podman run -d --name oradb \
>     --user 54321:54321 \
>     -v /oradata/test:/opt/oracle/oradata:Z \
>     container-registry.oracle.com/database/free:<IP_ADDRESS>
8d7c382dda151301b794855790293a2266f10385067d24c8c34cde5d265e4952
# podman logs -f oradb
Starting Oracle Net Listener.
Oracle Net Listener started.
Starting Oracle Database instance FREE.
Oracle Database instance FREE started.

The Oracle base remains unchanged with value /opt/oracle
#########################
DATABASE IS READY TO USE!
#########################
The following output is now a tail of the alert.log:
QPI: qopiprep.bat file present
2023-09-25T21:13:35.127227+00:00
PDB$SEED(2):Opening pdb with Resource Manager plan: DEFAULT_PLAN
FREEPDB1(3):Autotune of undo retention is turned on.
2023-09-25T21:13:36.069822+00:00
Using default pga_aggregate_limit of 2048 MB
2023-09-25T21:13:36.158657+00:00
FREEPDB1(3):Opening pdb with Resource Manager plan: DEFAULT_PLAN
Completed: Pluggable database FREEPDB1 opened read write
Completed: ALTER DATABASE OPEN
2023-09-25T21:13:37.882422+00:00
===========================================================
Dumping current patch information
===========================================================
No patches have been applied
===========================================================

The database starts as expected.
podman info etc. from the system:
$ podman info
host:
  arch: amd64
  buildahVersion: 1.29.0
  cgroupControllers: []
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: conmon-2.1.6-1.module+el8.8.0+21045+adcb6a64.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.6, commit: 31a72124adb6095b6be85b27e3e481313a1cea96'
  cpuUtilization:
    idlePercent: 69.12
    systemPercent: 3.74
    userPercent: 27.14
  cpus: 2
  distribution:
    distribution: '"ol"'
    variant: server
    version: "8.8"
  eventLogger: file
  hostname: podman
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.15.0-<IP_ADDRESS>.el8uek.x86_64
  linkmode: dynamic
  logDriver: k8s-file
  memFree:<PHONE_NUMBER>
  memTotal:<PHONE_NUMBER>8
  networkBackend: cni
  ociRuntime:
    name: runc
    package: runc-1.1.4-1.0.1.module+el8.8.0+21119+51f68ed8.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.1.4
      spec: 1.0.2-dev
      go: go1.19.10
      libseccomp: 2.5.2
  os: linux
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_SYS_CHROOT,CAP_NET_RAW,CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.0-2.module+el8.8.0+21045+adcb6a64.x86_64
    version: |-
      slirp4netns version 1.2.0
      commit: 656041d45cfca7a4176f6b7eed9e4fe6c11e8383
      libslirp: 4.4.0
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.2
  swapFree:<PHONE_NUMBER>
  swapTotal:<PHONE_NUMBER>
  uptime: 0h 28m 26.00s
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - container-registry.oracle.com
  - docker.io
store:
  configFile: /home/opc/.config/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 0
    stopped: 1
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/opc/.local/share/containers/storage
  graphRootAllocated:<PHONE_NUMBER>4
  graphRootUsed:<PHONE_NUMBER>6
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 1
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /home/opc/.local/share/containers/storage/volumes
version:
  APIVersion: 4.4.1
  Built:<PHONE_NUMBER>
  BuiltTime: Fri Sep 22 09:47:59 2023
  GitCommit: ""
  GoVersion: go1.19.10
  Os: linux
  OsArch: linux/amd64
  Version: 4.4.1
# podman ps
CONTAINER ID  IMAGE                                                 COMMAND               CREATED         STATUS                    PORTS       NAMES
f006d2ea6011  container-registry.oracle.com/database/free:<IP_ADDRESS>  /bin/bash -c $ORA...  48 seconds ago  Up 48 seconds (starting)              oradb
# podman images
REPOSITORY                                   TAG         IMAGE ID      CREATED      SIZE
container-registry.oracle.com/database/free  <IP_ADDRESS>    39cabc8e6db0  3 weeks ago  9.19 GB
# uname -a
Linux podman 5.15.0-<IP_ADDRESS>.el8uek.x86_64 #2 SMP Fri Aug 18 20:16:10 PDT 2023 x86_64 x86_64 x86_64 GNU/Linux

No luck with :z, but that led me to running it without relabeling: podman run --security-opt label=disable ..., so something with SELinux on Fedora CoreOS to dig into:
# podman info
host:
  arch: amd64
  buildahVersion: 1.31.2
  cgroupControllers:
  - cpuset
  - cpu
  - io
  - memory
  - hugetlb
  - pids
  - rdma
  - misc
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.7-2.fc38.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.7, commit: '
  cpuUtilization:
    idlePercent: 83.57
    systemPercent: 4.13
    userPercent: 12.3
  cpus: 2
  databaseBackend: boltdb
  distribution:
    distribution: fedora
    variant: coreos
    version: "38"
  eventLogger: journald
  freeLocks: 2047
  hostname: hostname
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 6.4.15-200.fc38.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree: 482484224
  memTotal:<PHONE_NUMBER>
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns-1.7.0-1.fc38.x86_64
      path: /usr/libexec/podman/aardvark-dns
      version: aardvark-dns 1.7.0
    package: netavark-1.7.0-1.fc38.x86_64
    path: /usr/libexec/podman/netavark
    version: netavark 1.7.0
  ociRuntime:
    name: crun
    package: crun-1.8.7-1.fc38.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.8.7
      commit: 53a9996ce82d1ee818349bdcc64797a1fa0433c4
      rundir: /run/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt-0^20230823.ga7e4bfb-1.fc38.x86_64
    version: |
      pasta 0^20230823.ga7e4bfb-1.fc38.x86_64
      Copyright Red Hat
      GNU Affero GPL version 3 or later <https://www.gnu.org/licenses/agpl-3.0.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
  remoteSocket:
    path: /run/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: false
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.1-1.fc38.x86_64
    version: |-
      slirp4netns version 1.2.1
      commit: 09e31e92fa3d2a1d3ca261adaeb012c8d75a8194
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.3
  swapFree:<PHONE_NUMBER>
  swapTotal:<PHONE_NUMBER>
  uptime: 0h 4m 50.00s
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  configFile: /usr/share/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 1
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev,metacopy=on
  graphRoot: /var/lib/containers/storage
  graphRootAllocated:<PHONE_NUMBER>0
  graphRootUsed:<PHONE_NUMBER>
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 1
  runRoot: /run/containers/storage
  transientStore: false
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 4.6.2
  Built:<PHONE_NUMBER>
  BuiltTime: Mon Aug 28 12:39:48 2023
  GitCommit: ""
  GoVersion: go1.20.7
  Os: linux
  OsArch: linux/amd64
  Version: 4.6.2

# podman ps
CONTAINER ID  IMAGE                                               COMMAND               CREATED        STATUS                  PORTS       NAMES
30600ccd8aa7  container-registry.oracle.com/database/free:latest  /bin/bash -c $ORA...  5 minutes ago  Up 5 minutes (healthy)              oracledb

Thanks @oraclesean


BUG-Notebook link is dead GUI tutorial

On this page:
https://docs.taipy.io/en/latest/knowledge_base/tutorials/understanding_gui/#using-notebooks
This link is dead:

This was discussed with @FlorianJacta yesterday.
This problem is due to the migration of the legacy Getting Started into the Knowledge Base structure that forgot about regenerating the notebook document.
I recommend that this generation is performed manually, once, and that the resulting file be stored in the doc repository itself, where it belongs. When the code is updated in the future, so should the notebook.
The generation script, if generic enough, could be stored in the tools directory for the doc for future use.

So I manually created that notebook file, so a minimum of visitors would be impacted.
To me this will be closed at the end of the sprint, unless anyone complains.


Unable to find service media_player/play_media

Hi
Thank you for your addons.
I've installed your picotts_remote and the mopidy addon as well.

http://raspi:8123/developer-tools/service
select tts/picotts_remote_say
message: 'bla'
send

Failed to call service tts/picotts_remote_say. Unable to find service media_player/play_media
I've read through the mopidy readme though can't see what part I missed
Running hass.io on raspi pi

Can you give me more information?
I tried replicate your scenario with following settings:

Installed PicoTTS Plugin Version 1.0-3
Installed Remote PicoTTS Component (copied the folder to config folder)
Installed Mopidy (P-Version) Version 1.1.0 with following config

Add picoTTS to config

- platform: picotts_remote
    host: localhost
    port: 59126

Restart
Executed:

After executing I'm hearing "blabla" through the connected speakers.

Installed PicoTTS Plugin Version 1.0-3

Can you please eloborate a bit? How would I install that (alongside mopidy and picotts_remote).


Unable to select a different song from a playlist that is playing

@hufman Hi there, you helped resolve the issue I logged earlier this week with the library not displaying playlists or albums in the car. Whilst the playlist and albums are now available to select there is another problem I am experiencing. If I load a playlist, i cannot select another track from that playlist via the car.. If I do, the first song starts again. This is the same with albums too. The only option i have is to select next.
BMW 520D (2018)
OnePlus 12R, Android 14
Spotify version <IP_ADDRESS>2

Unfortunately, AAIdrive just sends the "skipToIndex" command to Spotify, and Spotify is very buggy about this. The "playing first track" behavior you describe is a known problem when skipping through Liked Songs and Artist playlists and podcasts, and there isn't any solution from AAIdrive's perspective.

@hufman I've been using AAIdrive for over 2 years and this is the first time I'm experiencing this issue.
Is there anything that can be done as it's making Spotify useless via AAiDrive

@hufman I did some further testing yesterday and found that the track select does work in the following situations.

Albums - If i play an album, I can go to any track on the album that i want
Playlist - If i have basic shuffle off or on, I can browse to any track on that playlist. If i have the new smart shuffle on (Spotify tries to match your listening style and randomly insert track it thinks you might like into your playlist) then i defaults back to the first track in the playlist if you try to select a track manually.

I hope that help offer a bit more insight.

Thank you for your investigation!
Unfortunately, there isn't anything that AAIdrive can help with. If there was a way to detect if Spotify is in Smart Shuffle mode, it would be possible to disable the Select Track feature, but I'm not sure the Smart Shuffle option is even provided through the API.


Adding highlights of the movie like the short teaser

we can add highlights of the movie by using python that means converting the very long duration video to short video by taking highlights from the video like when the pitch is high consider it as highlight and combine them to get a short highlights video
can you assign me to add the new feature as a button

i would like to know more about the legality of this and also how are we going to create this for all the movies , wouldnt that be an extreme burden on the database?.


[hold]Add new permission flags for tagging, changing sidebar groups, creating new field for similarity search

What changes are proposed in this pull request?
(Please fill in changes proposed in this fix)
How is this patch tested? If it is not, please explain why.
(Details)
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.
[ ] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)
What areas of FiftyOne does this PR affect?

[ ] 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

Enhanced user permissions for more granular control over sidebar groups, field creation, sample tagging, custom color editing, and saved view modifications.
Introduced new states and conditions to manage read-only access based on user permissions and snapshot status.

Refactor

Updated the handling of read-only conditions across various components to improve consistency and clarity.
Restructured state management imports for better maintainability.

Bug Fixes

Adjusted disabled states in UI components to respect new permission checks, ensuring appropriate user interactions.

@coderabbitai review

Outside of the scope of this PR, so feel free to follow-up or defer:

Can we add support for restricting renaming sidebar group?
Can we add support for restricting deleting sidebar group?

I updated the flag name to canModifySidebarGroups to encapsulate the permission to change sidebar groups, including renaming, creating and deleting.

Can we move the business logic to the internal App?
The below doesn't need to be in OSS. The fos.canTagSamplesOrLabels session atom can capture the condition
const isReadOnly = readOnly || !canTag;

This is still following the same pattern as before. We decoupled "!canEdit" from readOnly, so readOnly right now refers to "isSnapshot" (but will likely expend in future per @imanjra ).


this is my logs after using the headless forge. The file Server.json did no show up so I created it and filled it but it did not work.
this are some more logs before the last ones

this is what it says

Originally posted by @italoaa in https://github.com/3arthqu4ke/PingBypass/issues/33#issuecomment-820751733

got it to finally work it needed a restart but now when entering a server it gets stuck in loading PingBypass

is this normal?

I assume that you didn't use an Accountmanager? Headlessforge doesn't support loging in by default. You most likely get disconnected for an invalid session. Use the click and gui commands to log in with that Accountmanager.
For the Server.json: make sure that you build from the latest commit, since that fixes the Server.json not being created. You can fill the Server.json with this:
 {
"Bind": "NONE",
"IServerIP": "<internal ip of your vps>",
"Port": <port>,
"NoRender": false,
"Hidden": false,
"Enabled": false,
"Name": "PingBypass"
}

would logging in through a vnc connection work?

I just tried to use the account manager but when using the session command my Account is not displayed but a random player name.

In the main menu:

gui command -> you are going to see that theres a button with id 20
click 20,
gui command again, you see a button with id 0 (addacount),
click 0,
gui command again, you see theres 2 textfields.
text 0 email of account
y
text 1 password
y
click 2 (add account)
you are now in the previous gui
click 1 (login)
session

Thank youuuuu worked perfectly

Nice!


Support source path that has no valid yaml files in.

Support source path that has no valid yaml files in. This is required to support the scenario where all HelmReleases have been moved to other layers but this layer still needs to be processed in order to perform prune processing.

work to implement this https://github.com/fidelity/kraan/pull/167

Workarounds, add a yaml file to create some object that is not a HelmRelease or HelmRepository custom resource. It will allow Kraan to process the subdirectory but will not be applied because Kraan only applies HelmRelease and HelmRepository objects.


Handle not found error

Sometimes got the error
2021/02/13 05:00:47 failed to get workflow insights: failed to parse response body: invalid character ':' looking for beginning of object key string

Maybe if the api returns not fount, response body is {message: not found}

[x] handle error by response status
[x] print response body when this error happens

Addressed by #3


Add HOME environment var to god config

Have god start resque workers with the $HOME environment variable
correctly set.
I noticed that my workers in my development VMs were not able to start
without this being set.  There were errors in
/opt/heidrun/log/worker.log indicating:
ArgumentError: couldn't find HOME environment -- expanding `~'

:+1: