Dependencies of plugins are not updated

Using the following example recipe:
type: specs.openrewrite.org/v1beta/recipe
name: com.my.group.Example
displayName: Example
description: Example
recipeList:
  - org.openrewrite.maven.ChangePluginGroupIdAndArtifactId:
      oldGroupId: com.my.group
      oldArtifactId: app-plugin-artifact
      newGroupId: com.my.group.subgroup
  - org.openrewrite.maven.ChangeDependencyGroupIdAndArtifactId:
      oldGroupId: com.my.group
      oldArtifactId: app-plugin-artifact
      newGroupId: com.my.group.subgroup
  - org.openrewrite.maven.ChangeManagedDependencyGroupIdAndArtifactId:
      oldGroupId: com.my.group
      oldArtifactId: app-plugin-artifact
      newArtifactId: app-plugin-artifact
      newGroupId: com.my.group.subgroup

This fails to update the dependencies of plugins. For example:
<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>com.app.myapp</groupId>
  <artifactId>awesome-app</artifactId>
  <version>1.0.0</version>

  <build>
    <plugins>
      <plugin>
        <groupId>com.app.plugins</groupId>
        <artifactId>cool-plugin</artifactId>
        <version>1.0.0</version>
        <dependencies>
          <dependency>
            <groupId>com.my.group</groupId>
            <artifactId>app-plugin-artifact</artifactId>
            <version>1.1.0</version>
          </dependency>
        </dependencies>
      </plugin>
    </plugins>
  </build>
</project>

I would expect at least one of these recipes to update the groupId of the plugin dependency. If there is a recipe that can do this, it's not clear to me which one it would be.

hi @jonblack ! Long time no see; hope you're well! Had a brief look at the above; indeed looks like we do not yet change plugin dependencies; we'd need a similar change as was done here:

https://github.com/openrewrite/rewrite/pull/3481

Of the options above, ChangeDependencyGroupIdAndArtifactId seems the best candidate. Would you be open to getting that started on a draft PR by copying this test to include your example above?
https://github.com/openrewrite/rewrite/blob/637266ba89ac00f693881549a1e0960411d0a947/rewrite-maven/src/test/java/org/openrewrite/maven/ChangeDependencyGroupIdAndArtifactIdTest.java#L29-L99

Hey @timtebeek! Small world! I'm good; very busy. How are you?
I've created the pull request with the test case that reproduces the issue. Sadly, I don't have time to work on a fix at the moment. Hopefully, this will help someone who can pick it up.

All is well here, thanks! Still working at Papendorpsweg? I know some colleagues of your were active as well. Hope the automations help your save time.
Thanks for the runnable exmaple! Indeed makes this easier to take on. Can't fit it in today but I'll try to find some time for this.

Fixed in https://github.com/openrewrite/rewrite/pull/4798


Underlines are invisible in integrated shell under Fedora 26

VSCode Version: 1.17.1
OS Version: Fedora 26

Steps to Reproduce:

Set  "terminal.integrated.fontSize": 14 (14 seems to be the default value)

Set  "terminal.integrated.fontSize" = 16 and the underlines are visible again.

Reproduces without extensions: Yes

I tried 12, 13, 14, 15, 16, and it happened only when font size = 14.

Same on Fedora 25 and yes, happens only with font size 14

Same on Ubuntu 16.04.3 LTS and only with font size 14

Duplicate https://github.com/Microsoft/vscode/issues/35901


Set-Timezone not working

I have installed ish-config, have executed Set Time Zone (US, Eastern), but alpine "date" utility puts out UTC.  I've done this several times.
iSH is 1.3.3 (574)
Alpine is v3.18

I did notice that the install procedure was missing the curl install step, so I added that.
I also updated set-timezone.sh to hopefully make it more stable.
I tried it on a fresh Alpine 3.18.5 miniroot filesystem selected US-Eastern. Once back at the prompt
date used the timezone EST
Let me know if it still doesnt work for you, and I will try to see if I can come up with something

Thank You,
I installed your latest code, set-Timezone to US/Eastern,
and
It's working now but it did require me to change one thing here:
I'm booting to bash, my .bashrc file had this:
export TZ=5
which made my local time correct in older versions of iSH + alpine.
I commented that line out,
rebooted,
and "date" now returns my local time.
cheers,
cwpfDUMMIES-7

On Feb 3, 2024, at 12:02, Jacob Lundqvist @.***> wrote:

I did notice that the install procedure was missing the curl install step, so I added that.
I also updated set-timezone.sh to hopefully make it more stable.
I tried it on a fresh Alpine 3.18.5 miniroot filesystem selected US-Eastern. Once back at the prompt
date used the timezone EST
Let me know if it still doesnt work for you, and I will try to see if I can come up with something
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


Added norwegian bokmål translation, and updated toki pona for lasted

Theres a huge rewrite happening, will merge after rewrite

Need to update for language rewrite

Updated toki pona and norwegian bokmål for  {{ . }}


How to pass random values for certain parameter in taskcat file

When I am creating multiple resources through AWS codepipeline, all the builds will trigger at same time and only one build succeeds and other fails with error the resource already exist.
I have only one .taskcat.yml file which is in the same folder as cloudformation template. And I have multiple .json parameters file in a different folder to create multiple resource.
Is there any way to pass random values for a parameter like resourcename(can be a s3 bucket, dynamodb table, rds, iam role etc)?
Let me know if there is a workaround.

In infrastructure as code (IaC), naming is best implemented through tags/metadata rather than resource names to avoid situations like that, but there are ways to accomplish what you want, such as using taskcat pseudo parameters like $[taskcat_random-string] and/or appending either all or part of the stack ID (using CloudFormation intrinsic functions like sub, split, join, et cetera).


how to set the receive mode to "RECEIVEANDDELETE" in spring cloud stream service bus binder

I see from the log that the default value of the receiver is PeekLock.
c.m.azure.servicebus.MessageReceiver     : Creating MessageReceiver to entity 'xxx-topic/subscriptions/xxx-subscription', ReceiveMode 'PEEKLOCK'
how to set the receiver to "ReceiveMode.RECEIVEANDDELETE" ?

Currently, setting ReceiveMode.RECEIVEANDDELETE is unsupported. But I want to understand the reason why you want to explicitly set this. From functional point, using this mode might cause message loss.

@warrenzhu25 Our company intends to replace RabbitMQ with Service Bus in the production environment, so we used the Service Bus SDK and Spring Cloud Stream Binder for some performance tests, but using PeekLock mode found that the performance is much worse than RabbitMQ, so I want to try the RECEIVEANDDELETE mode again.

hello, could you see how to create the queue in "ReceiveMode.RECEIVEANDDELETE"?
I'm using an azure function developed with .net, from there it can be changed to "ReceiveMode.RECEIVEANDDELETE"?

@pablosguajardo sorry for the late response. We've deprecated this repo, so I created an issue there.


Do not automatically include sources with all dependencies (lihaoyi#763)

Every dependency can include classifiers (tests, javadoc, sources). The line .addClassifiers(Classifier.sources) forces the inclusion of sources with every dependency.
Removing this line prevents the automatic inclusion of sources that is causing strange issues (such as Hadoop libraries not functioning properly).
If you want sources with a dependency they'll need to be explicitly specified.

Looks like I get to go fix some tests now.


make IQuesionnaireSchema match questionnaire.schema.json

-- haven't pushed packages yet

this was taken care of in another PR


HARP-7517: Partial support for rgba[..] and "rgba(..)" expressions in style.

Gives compatibility for themes using 4 channel colors in styling with
attributes expressions like:

color: rgba[255, 255, 255, 0.5]
backgroundColor: "rgba(255, 255, 255, 0.5)"

Although those styling attributes will be parsed and read, the alpha
channel component will be silently ignored. Full support for alpha channel
need to be implemented.
TODO:

support RGBA/ARGB colors internally in engine,
alpha channel mapping to THREE.js opacity and transparent material
properties,
support four channel color interpolation,
more unit tests.

Signed-off-by: Krystian Kostecki<EMAIL_ADDRESS>Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

Codecov Report

Merging #1010 into master will increase coverage by 0.14%.
The diff coverage is 89.58%.

@@            Coverage Diff             @@
##           master    #1010      +/-   ##
==========================================
+ Coverage   45.12%   45.27%   +0.14%
==========================================
  Files         236      249      +13
  Lines       22112    22351     +239
  Branches     5025     5071      +46
==========================================
+ Hits         9978    10119     +141
- Misses      12134    12232      +98

Impacted Files
Coverage Δ

...atasource-protocol/lib/operators/ColorOperators.ts
100% <100%> (ø)
:arrow_up:

@here/harp-mapview/lib/DecodedTileHelpers.ts
44.54% <100%> (+0.9%)
:arrow_up:

...rp-datasource-protocol/lib/StringEncodedNumeral.ts
57.14% <33.33%> (-4.93%)
:arrow_down:

...rp-datasource-protocol/lib/InterpolatedProperty.ts
72.29% <66.66%> (-0.31%)
:arrow_down:

@here/harp-materials/lib/Utils.ts
20% <0%> (-80%)
:arrow_down:

@here/harp-materials/lib/IconMaterial.ts
44.44% <0%> (-55.56%)
:arrow_down:

@here/harp-map-controls/lib/Utils.ts
46.15% <0%> (-23.85%)
:arrow_down:

@here/harp-omv-datasource/lib/OmvTiler.ts
50% <0%> (-16.67%)
:arrow_down:

@here/harp-utils/lib/ObjectUtils.ts
83.33% <0%> (-10.22%)
:arrow_down:

@here/harp-utils/lib/UrlResolver.ts
91.66% <0%> (-8.34%)
:arrow_down:

... and 31 more

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 6247cec...a0d3701. Read the comment docs.


chore: add a GitHub PR template

Includes a checklist of things to be verified by authors and reviewers.
Fixes: MODELIX-796

:tada: This PR is included in version 8.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use a hash set for the closed state list

The A* library uses a closed list which is slow to look up if a state has been visited. I've changed to a hash set via the unordered_set which speeds up search.
In my use case, this took the mean search time from 0.0141 seconds to 0.0016 seconds and the max search time from ~2.8 seconds to ~0.34 seconds.
I updated the examples to also use the hash. If there is a better way to handle the has function let me know. I had trouble using the hash template specialization with the other templating in the library, and this way became easier.

Thanks for the PR, will need some time to review it and let you know

Hi @btdubs thanks again for the PR. I reviewed it today.  I have a couple of reservations:

It requires users of the library to add a hash function for their state
We need to restrict the users to use c++11 or later since auto, hash and unordered_set are new since c++98/03

However I think it's a valuable change because it's faster. I have also been considering moving to a more recent c++ standard and c++11 provides lambdas, auto, range iteration and various smart pointers that would improve the current code somewhat.
I think the best solution for my users would be something like this:

Cut a release of the current branch and share the tag in the documentation so that if users cannot upgrade to C++11 (although I think this is quite a small number of users by now), they can revert to that release
Create a new release with your changes and the build files updated to specify c++11 is required
Make the use of the unordered_set optional. If the user does not want to provide a hash function we can fallback to a simple list with some performance loss

I think it would be okay to provide a preprocess flag so that the use of the set instead of the list is opt-in and zero cost if you do not use it.
I think the way you handled adding the Hash function is easy to use and I have no problem with it.
Anyway just wanted to share my thinking with you. I have not decided the best way to move forward but would appreciate any ideas.

Thank you again for this contibution. I closed the PR rather than merging as I made some changes and merged it manually.


Add nvFuser support for thunder.torch.randn

🐛 Bug
import thunder
import torch

@thunder.jit
def normal(shape, device):
    return torch.randn(tuple(shape), device=device)

shape = [1, 4, 40, 84, 84]
t1 = normal(shape, device="cuda:0")
print(thunder.last_traces(normal)[-1]) # should have nvFusion0 there!

def computation():
  t6 = torch.randn((1, 4, 40, 84, 84), device=torch.device("cuda:0"), dtype=torch.float32)  # t6: "cuda:0 f32[1, 4, 40, 84, 84]"
    # t6 = ltorch.randn((1, 4, 40, 84, 84), generator=None, dtype=torch.float32, device=torch.device("cuda:0"), layout=torch.strided, requires_grad=False, pin_memory=False, out=None)  # t6: "cuda:0 f32[1, 4, 40, 84, 84]"
      # t6 = prims.randn((1, 4, 40, 84, 84), device=devices.Device("cuda:0"), dtype=dtypes.float32)  # t6: "cuda:0 f32[1, 4, 40, 84, 84]"
  return t6

cc @tfogal

triage review –

this is a note for coverage, this is not known to be a performance issue in any model we're targeting today

From Kevin : There are no plans to support this at the moment. We can revisit if there is a model that has this requirement.


restricting eval body to subset of Expression variants

Hi Martin, first thanks so much for this library!
I have a question--
I would like to restrict a property on an HCL body to a subset of hcl::Expression variants during hcl::from_body(body) schema validation.
The body schema is:
pub struct CallBlock {
    base_url: hcl::Expression,
    path: Option<hcl::Expression>,
    headers: Option<hcl::Expression>,
    body: Option<HclObject>,
    after: Option<Vec<HclObject>>,
    outputs: Option<Vec<hcl::Traversal>>,
}

I can encapsulate the Expression::Object variant--
pub type HclObject = hcl::Object<hcl::ObjectKey, hcl::Expression>;

However, rather than the general hcl::Expression, I want to restrict headers to be either--
pub enum ObjectOrVariable {
    Object(HclObject),
    Variable(hcl::Variable),
}

(e.g. user HTTP headers can either be an object with a key or a general expression, or a variable. If the user screws up the header value its their problem, but we validate that its not a )
When I use this ObjectOrVariable enum as the header schema-- Option<Vec<ObjectOrVariable>> --  I get this error with correct HCL-- "unknown variant 'my-key', expected 'Object' or 'Variable'", where my-key was the header key passed.
Thanks in advance for any help, and apologies if I've missed something obvious.

Hi @iamjoncannon, could you provide me with a minimal reproducer for the issue? With the context you provided so far it seems like this could solved using the #[serde(untagged)] attribute on the ObjectOrVariable enum: https://serde.rs/enum-representations.html

Hi @martinohmann, thanks for following up!
I wrote some unit tests to describe my ideal behavior to evaluate blocks during an initial parsing.
My suspicion is that I'm unable to define the types of these variants properly-- e.g. defining a list as a vec instead of the hcl::Expression::Array variant.  Granted I'm not a Rust expert, but I wrestled with this enough to conclude that I might not be able to do this because the variant types are private?
Being able to define and restrict user inputs for my app would be really, really helpful, so again thank you so much for any time you can spend on my issue.
// [dependencies]
// hcl-rs = "0.16.7"
// serde_json = "1.0.114"
// serde = "1.0.197"

use serde::{de::DeserializeOwned, Deserialize, Serialize};

#[derive(Deserialize, Serialize, Debug)]
#[serde(untagged)]
pub enum HeaderKey {
    Identifier(hcl::Identifier),
    Traversal(hcl::Traversal),
}

pub type HeaderObject = hcl::Object<hcl::ObjectKey, HeaderKey>;

#[derive(Deserialize, Serialize, Debug)]
#[serde(untagged)]
pub enum HeaderObjectOrVariable {
    Object(HeaderObject),
    Traversal(hcl::Traversal),
}

#[derive(Deserialize, Serialize, Debug)]
#[serde(untagged)]
pub enum ValidHeaderCases {
    Traversal(hcl::Traversal),
    String(String),
    Array(Vec<HeaderObjectOrVariable>),
}

#[derive(Deserialize, Serialize, Debug)]
pub struct IdealRestrictedCallBlock {
    pub headers: ValidHeaderCases,
}

#[derive(Deserialize, Serialize, Debug)]
pub struct UnrestrictedCallBlock {
    pub headers: hcl::Expression,
}

pub fn evaluate<T: DeserializeOwned>(input: &str) -> Result<T, hcl::Error> {
    let call_block_body: hcl::Body = hcl::from_str(input).unwrap();
    let block = call_block_body.into_blocks().next().unwrap().body;
    let call_block_res: Result<T, hcl::Error> = hcl::from_body(block);
    call_block_res
}

fn main() {}

#[cfg(test)]
mod tests {
    use std::fmt::Debug;

    use crate::{evaluate, IdealRestrictedCallBlock, UnrestrictedCallBlock, ValidHeaderCases};

    #[test]
    fn test_trivial_string() {
        // this is just to test untagged solution with a trivial case
        let test_block: &str = r#"
            get "example" {
                headers = "trivial case"
            }
        "#;

        run_unrestricted_and_ideal(test_block, "test_trivial_string");
    }

    #[test]
    fn test_header_block_as_variable() {
        let test_block: &str = r#"
            get "example" {
                headers = my.headers.var
            }
        "#;

        reporter(
            "test_header_block_as_variable UnrestrictedCallBlock",
            &evaluate::<UnrestrictedCallBlock>(test_block),
        );

        let res = evaluate::<IdealRestrictedCallBlock>(test_block);

        match res {
            Ok(res) => match res.headers {
                ValidHeaderCases::Traversal(_var) => assert!(true),
                ValidHeaderCases::String(str) => {
                    // the variable is evaluated as a string template
                    println!("variable evaluated as string: {str}");
                    assert!(false)
                }
                _ => assert!(false),
            },
            Err(err) => {
                eprintln!("test_header_block_as_variable err {err:?}");
                assert!(false);
            }
        }
    }

    #[test]
    fn test_headers_defined_as_variable() {
        let test_block: &str = r#"
            get "example" {
                headers = [
                    my.header.variable
                ]
            }
        "#;

        run_unrestricted_and_ideal(test_block, "test_headers_defined_as_variable");
    }

    #[test]
    fn test_headers_defined_as_string() {
        let test_block: &str = r#"
            get "example" {
                headers = [
                    { "authorization" : "let me in" }
                ]
            }
        "#;

        run_unrestricted_and_ideal(test_block, "test_headers_defined_as_string");
    }

    #[test]
    fn test_individual_headers_as_variables() {
        let test_block: &str = r#"
            get "example" {
                headers = [
                    my.header.variable
                ]
            }
        "#;
        run_unrestricted_and_ideal(test_block, "test_individual_headers_as_variables");
    }

    #[test]
    fn test_individual_headers_values_as_variables() {
        let test_block: &str = r#"
            get "example" {
                headers = [
                    { "authorization" : my.auth.var }
                ]
            }
        "#;
        run_unrestricted_and_ideal(test_block, "test_individual_headers_values_as_variables");
    }

    fn run_unrestricted_and_ideal(test_block: &str, test_name: &str) {
        reporter(
            &format!("{} UnrestrictedCallBlock", test_name),
            &evaluate::<UnrestrictedCallBlock>(test_block),
        );

        reporter(
            &format!("{} IdealRestrictedCallBlock", test_name),
            &evaluate::<IdealRestrictedCallBlock>(test_block),
        );
    }

    fn reporter<T: Debug>(name: &str, result: &Result<T, hcl::Error>) {
        match result {
            Ok(res) => {
                println!("result {name}: {res:?}");
                assert!(true)
            }
            Err(err) => {
                println!("err {name} {err:?}");
                assert!(false)
            }
        }
    }
}


Rename the --outline-... CSS variables to --treeitem-... instead (PR 11077 follow-up)

Given that the outlineView/attachmentsView/layersView all share a common base-class and CSS rules, see PRs 12169 and 12170, the names of the CSS variables in question feels slightly strange now.

/botio-linux preview

Looks better!


Add a general function to compare string content between source and target for all DVT connection types

Make the function available to all DVT connection types.

Comparing string content with row validation will be extended to SQL Server (#560) and Oracle (#556) next. We have created separate Issues to track each.


Reproducible crash with regexp

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.74.3
OS Version: macOS 12.6

Steps to Reproduce:

Open large file with JSX
Search file for regexp: \((?:[^<]|\n)+<

Copy & Paste in search

On Mac get message application is not responding

Probably related to #30874 even if proveded example doesn't contain obvious backtracking.
However https://github.com/microsoft/vscode/issues/171514#issuecomment-1385811810 sounds promising.

Likely a duplicate of https://github.com/microsoft/vscode/issues/30874


fix broken link: http://kubernetes.io/docs/home/contribute/page-templ…

…ates/

@CriaHu Many thanks for fixing the 404 problems.
Please consider consolidate the many extra-small (XS) changes into batches when proposing PRs. For example, I see no reason why this one cannot be combined with #21679.

ok, I got it.

Hi @CriaHu . Thanks for fixing the link to the site's information about page content types.
/lgtm

/approve


I can export a file to .pdf but OneDrive browser does not show .pdf files

[x ] I agree to follow the Code of Conduct that this project adheres to.
[ x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
I can export to .pdf, but I cannot try to open a .pdf file from OneDrive.
To Reproduce
Steps to reproduce the behavior:

Open from > One Drive.
Find a .pdf file.

Expected behavior
I can see all files, the usual system browser is being used.
Actual behavior
File browser shows only some file extenstions:

draw.io version (In the Help->About menu of the draw.io editor):

draw.io version 24.2.7

Desktop (please complete the following information):

OS: Win11
Browser chrome
Browser Version 123.0.6312.123

I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:

Yes.

Additional context
The usecase is that I do not have an ability to download files from sharepoint, but drawio has access to them.

Try using 24.2.9.

It seems to be working, but notice what happens to breadcrumbs when you
click "refresh", it multiplicates the last entry in the path. Thank you!
[image: image.png]
śr., 24 kwi 2024 o 12:40 David Benson @.***> napisał(a):

Try using 24.2.9.
—
Reply to this email directly, view it on GitHub
https://github.com/jgraph/drawio/issues/4339#issuecomment-2074648564,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDQD4FKC3TH7OYLOEZI6BMDY66DYXAVCNFSM6AAAAABGSX5BJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUGY2DQNJWGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Worker crashing on RpcException

Investigative information

Timestamp: 193 failed operations between 11/24/2020, 11:27:20 AM and 11/24/2020, 11:49:47 AM
Invocation ID: 6e9924ae-d470-4bfc-939a-65e41c3a3030 (first occurrence) and 6ba54e62-c877-4be2-bddb-acaab5577d41 (last occurrence)
Region: West US 2

Repro steps

Invoke the function

Expected behavior

After invoking the function I expect it to run and ideally finish successfully.

Actual behavior

Function fails with RpcException and the following error:

Exception while executing function: Functions.db_writer Result: Failure
Exception: Worker was unable to load function db_writer: 'Error: UNKNOWN: unknown error, lstat 'D:\home''
Stack: Error: UNKNOWN: unknown error, lstat 'D:\home'
    at Object.realpathSync (fs.js:1615:7)
    at toRealPath (internal/modules/cjs/loader.js:363:13)
    at Function.Module._findPath (internal/modules/cjs/loader.js:654:24)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:953:27)
    at Function.Module._load (internal/modules/cjs/loader.js:842:27)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at FunctionLoader.load (D:\Program Files (x86)\SiteExtensions\Functions\3.0.14916\workers\node\worker-bundle.js:20979:22)
    at WorkerChannel.functionLoadRequest (D:\Program Files (x86)\SiteExtensions\Functions\3.0.14916\workers\node\worker-bundle.js:18439:38)
    at ClientDuplexStream.<anonymous> (D:\Program Files (x86)\SiteExtensions\Functions\3.0.14916\workers\node\worker-bundle.js:18343:30)

Known workarounds
After waiting 22 minutes, the issue appeared to resolve on its own.
Related information
The function normally runs successfully, but we want to investigate the root cause of this downtime today. We upgraded this function from v2 to v3 3-4 weeks ago, and this is the first time we have seen this issue since then.

Programming language used - LTS Node v12
Bindings used - EventHub Trigger
Function version - v3

@anthonychu We were seeing this consistently from Wednesday until about 7AM PST this morning
Timestamp: About ~32,000 failures as early as 12/15/2021, 9:09:55.306 PM PST and as late as 12/20/2021, 6:55:20.638 AM PST
InvocationID: 5a4af4a4-58ab-4359-a959-363839b36aa7  (for 12/15 failure) and 149f0a41-bbc2-4fce-a5cc-5986753fb04b (for most recent failure)
Region: West US 2

Dupe of https://github.com/Azure/azure-functions-nodejs-worker/issues/693


Can I use Radium with Material UI?

I see that Radium is a set of tools to manage inline styles on React elements so can I use it with Material UI? Recently, I want to make a hover effect with Material UI but I don't know how to make it. I have tried this solution but I cannot make it work. Therefore, can Radium help me solved it easily?
const styles = {
    card: {
        height: 200,
        width: 200,
        margin: 10,
    },
    cardHover: {
        backgroundColor: "rgba(98, 252, 105, 0.65)",
    },
        ...
        ...
}

How to give Card component a hover effect?
export default class Project extends React.Component {
    render() {
        return (
            <Card style={styles.card}>

                    XXX

YYY

ZZZ

            </Card>
        );
    }
}

Yep, you'll need to use the :hover pseudo-class selector to make that work.
const styles = {
    card: {
        height: 200,
        width: 200,
        margin: 10,
        ":hover": {
            backgroundColor: "rgba(98, 252, 105, 0.65)"
        }
    }
};

Here is more information in the documentation:
https://github.com/FormidableLabs/radium/tree/master/docs/guides#browser-states

I am trying to use Paper component and style it with radium , but the hover styles are not being applied when hovering.
<Paper style={{ backgroundColor : 'red' , ":hover" : {backgroundColor:'green' } }}>

 Hi

</Paper>


Disaggregations: Distribute existing disaggregations into portfolio and program buckets

This issue is part of Epic #1206
This issue depends on the completion of #1208
After we update the disaggregations database model (see #1208), we need to link existing disaggregation types to the correct portfolio or program bucket, so that the correct options appear when a user is setting up disaggregations for an indicator.
Tasks

Run a database query to figure out which disaggregations have not only been configured but are actually in use -- meaning, they are not just configured, but also linked to indicators and results.
Identify any disaggregation types in use that are program specific.
For each program-specific disaggregation type, identify the correct program and link the disaggregation to it.

Acceptance criteria

[ ] 1. For any program to which existing disaggregations are reassigned: When I open any of the program's indicator setup forms, I see the expected program-specific disaggregation options on the Performance tab.
[ ] 2. For any Result form that has disaggregated values, where the disaggregation type has been reassigned: Values are preserved.

Testing

No longer needed. See closed #1208.


Université Assane Seck de Ziguinchor

I want to get the free licence Student

@sndour3960 lib/domains/sn/univ/zig: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@sndour3960 I have to close this request without merging, because you request does not have essential information about the school and the school email domain. Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Horrible debugging hell

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:13:05.928Z)
OS Version: Darwin x64 16.6.0
Extensions:

Extension
Author
Version

aurelia
AureliaEffect
0.3.4

vscode-docker
PeterJausovec
0.0.16

vscode-theme-onelight
akamud
2.0.2

vscode-npm-script
eg2
0.2.0

task-master
ianhoney
0.1.39

quicktask
lkytal
2.8.1

Go
lukehoban
0.6.62

debugger-for-chrome
msjsdiag
3.1.6

Material-theme
zhuangtongfa
2.9.3

Steps to Reproduce:

Have a go program
Run a goroutine
Block the main routine
Break in the goroutine
Try to step through the goroutine

When the main routine is blocked and I try to step through a 'worker' goroutine, on EVERY SINGLE BLEEPING STEP VSCode switches the currently viewed frame to the main routine. So on every step I have to reselect the worker goroutine in the 'call stack' panel. It's quite painful.
Maybe this is an issue with delve? Not sure.

Update: since the main thread is blocked, I can step twice and it goes back properly to the goroutine. So at least there's that.

This issue was moved to Microsoft/vscode-go#1091


Parent link customfield support

The Parent Link customfield enables linking from Epic upto Features/Themes.
The logic for re-linking after a push is currently a bit dumb; it assumes only epics and issues exist.
When Issue.parent_link is added, rewrite the push logic as follows:

Gather new
From this list, find all which are parents
Send those first

After a new_issue, all parent links to the replaced issue should be updated

Closed in 1118fc3aca82beea86c04899d2e92faa30dbf616


add redis-compatible HSCAN/SSCAN/ZSCAN commands

As far as I could see these commands were already (roughly) compatible, except for:

the name difference (prefix x);
the fact that the initial and last cursor is "" instead of "0";

I know that there are more differences, such as the fact that the cursor is the key instead of an index, but I don't think that matters for the user.
The aim of this PR is not to make ledisdb's scan commands equal to redis's scan commands. Rather it is to be able to use commands like HSCAN with a ledis-server as if it were a redis-server.
Let me know if there are bigger issues, but as far as I've tested manually with my own projects, this PR seems to make it work for me (note that I only manually tested HSCAN, as I don't use SSCAN or ZSCAN in my projects).

@siddontang I addressed your remarks.

Let me know if something else has to be done @siddontang :)

Thanks @GlenDC


add datetime property at links of the monthly level catalog.json

Please add datetime property at links if a link is item. this can help client to get datetime information without fetching further item.json again
https://undpgeohub.blob.core.windows.net/stacdata/nighttime-lights/2023/09/catalog.json
{
   "type":"Catalog",
   "id":"nighttime-lights-2023-09",
   "stac_version":"1.0.0",
   "description":"VIIRS DNB nighttime lights nightly mosaics in 2023-09",
   "links":[
      {
         "rel":"root",
         "href":"../../../catalog.json",
         "type":"application/json",
         "title":"UNDP STAC repository"
      },
      {
         "rel":"item",
         "href":"./11/SVDNB_npp_d20230911.json",
         "type":"application/json",
         "datetime": "2023-09-11T00:00:00Z" <- you can add datetime property here.
      },
      {
         "rel":"item",
         "href":"./12/SVDNB_npp_d20230912.json",
         "type":"application/json"
      },
      {
         "rel":"item",
         "href":"./09/SVDNB_npp_d20230909.json",
         "type":"application/json"
      },
      {
         "rel":"item",
         "href":"./10/SVDNB_npp_d20230910.json",
         "type":"application/json"
      },
      {
         "rel":"parent",
         "href":"../catalog.json",
         "type":"application/json",
         "title":"Nighttime lights in 2023"
      }
   ],
   "title":"Nighttime lights in 2023-09"
}

closed by #11


Release 0.10.0

Release to account for input ID refactors - incremented minor version because changes break dependent test kits.

@Jammjammjamm, FYSA I updated inferno_core as you requested and also added FI-3129 Add access token outputs and FI-3156 Loosen scope checks to this release, since those were merged into main before I completed the release.


Using Variables after "Create Table"

I'm having trouble using variables after a Create Table statement. The code below throws a syntax error on : but works without the  Create Table statement. I'm using Vertica and DBeaver 5.2.3
Thanks
@set start_date='2018-10-15 00:00:00'
CREATE TABLE IF NOT EXISTS my_table AS
select :start_date

By default parameters in DDL queries are disabled. They can be re-enabled by turning special prfs option on:

However, I think we can enable variables usage in DDL.
So you can run query like
@set start_date='2018-10-15 00:00:00'
CREATE TABLE IF NOT EXISTS my_table AS
select ${start_date}

This feature wuill be enabled in 6.2.4


Treat junit @Parameter same way as allure @Parameter annotation

Now we need to use both this annatotaions. First - to tell junit there is a parameter, and second - to tell allure the same.

Junit 4 sets parameter fields via reflection, I don't think we can easily implement it with aspectj.


feat: add Member.role_icon property to display rendered role icon

Summary
adds Member.role_icon which shows the member's rendered icon
Checklist

[x] If code changes were made, then they have been tested

[x] I have updated the documentation to reflect the changes
[x] I have formatted the code properly by running task lint
[x] I have type-checked the code by running task pyright

[ ] This PR fixes an issue
[x] This PR adds something new (e.g. new method or parameters)
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

discord seems to be adding some sort of system icons that display on members. Naming this icon may interfere with that.
Perhaps this could be named role_icon?

Unsure if this should be called role_icon (or just icon?) instead of display_icon, to avoid confusion with avatars

Solved in https://github.com/DisnakeDev/disnake/pull/485/commits/7a130e7bc9cf77d0b2755d8312b5326da67331f8

Just noticed something.

Should be fixed now.


French Create User Test

Overview
All our testing is currently in english and we want to ensure our other site languages are working. This need came from an incident where a bug happened on all browser languages except for english and the cypress tests did not catch it.
Action Items

[ ] Get Cypress tests up and running. See Cypress Readme
[ ] Create your own branch
[ ] Take a look at this german example of the test
[ ] Duplicate this test in French and name it create-user.fr.cy.tsx. Note that you will have to update some of the test assertions to match the spanish version of the site. Take a look at bloom.chayn.co/fr for the french version of the site to find the equivalent text.
[ ] See notes below for helpers
[ ] Commit and push your changes and create a PR.
[ ] Tag @eleanorreem  for a review

Resources/Instructions

Cypress readme
Ensure you create a custom visitFrenchPage that replicates the behaviour of visitGermanPage in this file
You will also have to update the type file

Hi @eleanorreem I can take this if you want, it will be my first contribution in a open source project 😄

Hey @LucasVermersch, thank you for your interest! I have assigned you this issue.
Be sure to check out our Contribution Guidelines. 🙂


Removing meaningless line from kubefed.md

There is a line accidentally added in kubefed.md:' ###### Auto-generated by spf13/cobra on 26-Mar-2019'. This is meaningless so removing this from the page.
This also fixes #13755

@jimangel @Rajakavitha1 Can you please have a look at this PR?

Merging this because it is actually fixing an obvious bug.
/lgtm
/approve


Problems when both rubyzip and zipruby installed

I've been using rubyzip in a rails application to create custom XLSX files by compressing an expanded XLSX document tree and using ErB to replace the contents of one xml file. However, I've been experiencing a number of issues with Excel complaining about errors with the resulting XLSX file, and so tested expanding and compressing a simple XLSX file to see what happens. I also tried using rubyzip just to replace the contents of one of entries in a zip archive.
It seems that rubyzip is compressing the file in a subtly different manner from that expected by Excel, and the only solution I've found is to use zipruby instead just to modify the contents of the files I want to edit. This works fine.
However both rubyzip and zipruby define Zip::File, and other areas of the application that use other dependent gems, eg roo, have issues with Zip::File.exists? which is defined in both zip gems.
I've tried using Bundler to load gems specific to a given method, but this doesn't seem to work, and so the only other solution that works for me is to explicitly specify the namespace for any ::File method invocations.
This seems to work fine, with tests passing as well.
If you know of any other solutions I'd be interested to know, otherwise I'd request that the changes be pulled.

Is there a reason not to merge this?

This would be very useful to merge in, rather than more of us needing to fork and modify rubyzip with this change. Also, it could also be fixed with zipruby changing the module namespace to ZipRuby::* instead of the same Zip::*.
Why not merge it in? Zipruby is useful for manipulating word docx files in memory.

This also addresses a conflict with selenium webdriver. For now I'm just using the mezza fork but it would be nice to see this  merged in.

I cannot merge this pull automatically.
But I can fix ::File conflict and close this pull request.

Thanks for merging this in! Could you publish a new release of the gem please?


Format function SegFaulting at Runtime when negative width string is specified

While attempting to use the Format package on a U128, I managed to create a run-time segfault, by accidentally passing in a negative width value.  I was using position-based arguments when this occurred, but it also occurs with named arguments, as shown below.
use "format"

actor Main
  new create(env:Env) =>
  let n: U128 = 42

  env.out.print("Regular output. n="+n.string())
  env.out.print(Format.int[U128](where x=n, fmt=FormatBinaryBare, prefix=PrefixDefault,
    prec=1, width=20, align=AlignRight,fill='0'))

  env.out.print("Before runtime fault.  Segment fault 11 on Mac OS X.")
  env.out.print(Format.int[U128](where x=n, fmt=FormatBinaryBare, prefix=PrefixDefault,
    prec=1, width=-1, align=AlignRight,fill='0'))
  env.out.print("This is never executed because the above line crashes at runtime.")

Building builtin -> /usr/local/Cellar/ponyc/0.14.0/packages/builtin
Building . -> /Users/thomasjohnson/Projects/pony/FormatStringSizeCrash
Building format -> /usr/local/Cellar/ponyc/0.14.0/packages/format
Building collections -> /usr/local/Cellar/ponyc/0.14.0/packages/collections
Building ponytest -> /usr/local/Cellar/ponyc/0.14.0/packages/ponytest
Building time -> /usr/local/Cellar/ponyc/0.14.0/packages/time
Generating
Reachability
Selector painting
Data prototypes
Data types
Function prototypes
Functions
Descriptors
Optimising
Writing ./FormatStringSizeCrash.o
Linking ./FormatStringSizeCrash
Regular output. n=42
00000000000000101010
Before runtime fault.  Segment fault 11 on Mac OS X.
/bin/bash: line 1: 31076 Segmentation fault: 11  ./FormatStringSizeCrash
[Finished in 4.0s with exit code 139]
[shell_cmd: ponyc && ./FormatStringSizeCrash]
I've confirmed this issue on both Mac OSX and on the Pony Playground.
0.14.0 [release]
compiled with: llvm 3.9.1 -- Apple LLVM version 8.1.0 (clang-802.0.42)
0.14.0 [release]
compiled with: llvm 3.9.1 -- cc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

Possibly relevant comments from the 2017-JULY-07 IRC follow:
[15:20] <@jemc> the cause is that USize(-1) == USize.max_value()
[15:39] <@jemc> no worries - I was trying to think if there's something that could be done as a sanity check in Format against very large values of width, but it seems that width is used for padding, and I'm not sure where to draw a "sane" limit for padding a string
[15:42] <@Praetonus> jemc: There's a bug in String.reserve too. If the reserved size is USize.max_value, the function will add 1 for the null terminator and overflow, resulting in a String that thinks it has lots of memory available but actually didn't allocate anything
[15:42] <@Praetonus> That's the reason of the crash here
[15:44] <@jemc> that darn null terminator

I've confirmed this on 0.14.0-8781b65.
$ ponyc --version
0.14.0-8781b654 [release]
compiled with: llvm 3.9.1 -- Apple LLVM version 8.1.0 (clang-802.0.42)

[15:42] <@Praetonus> jemc: There's a bug in String.reserve too. If the reserved size is USize.max_value, the function will add 1 for the null terminator and overflow, resulting in a String that thinks it has lots of memory available but actually didn't allocate anything

The segfault is happening within the while loop here
What's happening is that the pre variable has overflown from 0 to the max usize and is being slowly decremented.
Changing the code to this:
while pre > 0 do
  Debug.out(pre)
  s.append(fills)
  pre = pre - 1
end

...results in this:
18446744073709528348
18446744073709528347
18446744073709528346
18446744073709528345
18446744073709528344
18446744073709528343
18446744073709528342
18446744073709528341
18446744073709528340
18446744073709528339
18446744073709528338
18446744073709528337
...

I'm not sure what the proper response to a negative width should be though 🛩 🍐

@charlesetc - as you've noted USize(-1) is equivalent to USize.max_size(), which is not really a bug, but a reasonable shorthand.
I think the only consistent thing we can do is to assume they meant USize.max_size(), and make a string of the maximum length.

Interesting - so is the segfault here from allocating too much memory?

@charlesetc According to @Praetonus' comment above, the issue is that the string is allocating an extra byte for the null terminator, leading it to allocate not USize.max_value() bytes, but USize.max_value() + 1, which comes out to zero bytes.
The allocation logic needs to be special-cased to not add + 1 for the null terminator if the size is USize.max_value().

Gotcha - does the segfault in the while loop that I'm seeing go along with that?

The allocation logic needs to be special-cased to not add + 1 for the null terminator if the size is USize.max_value().

This certainly is a good solution for this particular edge case, but I think we need to discuss on a way to handle the general issue of "overflowing" collections, i.e. what should happen when one tries to add more elements to a collection than logically possible.
Since these are very uncommon edge cases, one possible way to handle the issue could be to take the "performance over safety" route and not handle it at all, similar to how we're currently not handling memory exhaustion. This would also raise the issue of whether USize(-1) really is a "reasonable shorthand" for a really big number, since it can easily lead to an overflowing collection as demonstrated in this issue.
@charlesetc Yes. It's segfaulting because the String is writing to memory that it thinks it owns, but actually doesn't since it didn't allocate any memory.

@Theodus – I get the exact opposite: 129 is fine, 128 results in SEGFAULT.

The issue is not in String.reserve but rather in the pool size adjustment logic.
However, the fix shown below reveals a bigger issue here which is that pool_alloc_size(size) then fails to allocate a pointer (this time of the correct size) since there is no block which is large enough.
On my system pool_block_header.largest_size is 134167552. This is obvious larger than USize.max_value() - 1.
--- a/src/libponyrt/mem/heap.c
+++ b/src/libponyrt/mem/heap.c
@@ -416,6 +416,8 @@ void* ponyint_heap_alloc_small_final(pony_actor_t* actor, heap_t* heap,
 void* ponyint_heap_alloc_large(pony_actor_t* actor, heap_t* heap, size_t size)
 {
   size = ponyint_pool_adjust_size(size);
+  if(size == 0)
+      size = (size_t) - 1;

   chunk_t* chunk = (chunk_t*) POOL_ALLOC(chunk_t);
   chunk->actor = actor;
diff --git a/src/libponyrt/mem/pool.c b/src/libponyrt/mem/pool.c
index c89b743a5..2f2436782 100644
--- a/src/libponyrt/mem/pool.c
+++ b/src/libponyrt/mem/pool.c
@@ -914,6 +914,8 @@ void* ponyint_pool_alloc_size(size_t size)
     return ponyint_pool_alloc(index);

   size = ponyint_pool_adjust_size(size);
+  if(size == 0)
+      size = (size_t) - 1;
   void* p = pool_alloc_size(size);

   return p;


Maven assembly doesn't keep 0755 attributes for .sh files when built on macos

Retest after move to Gradle.

I think it should be:
0750 for all dirs
0750 for *.sh files
0640 for all other files


Create Test Minutes

Declining because these are not real minutes, but thanks for testing. I appreciate it. :)


PulseAudio: Disable flat volume?

Flat volume is enabled by default. I think we should disable it because this option could damage speakers/ears. What do you think?
Here is the relevant reddit post: http://www.reddit.com/r/linux/comments/2rjiaa/horrible_decisions_flat_volumes_in_pulseaudio_a/

Why not provide a well-documented pulseaudio.flatVolumes that defaults to upstream's true? There are good reasons for that, too.
The "damage" agument is, well, at least it's original.

Do you read all hardware docs and kernel help before you configure your kernel? Do you read all wiki pages before you use a Linux distro? I guess not.  Because it can possibly CAUSE PHYSICAL DAMAGE!
If someone doesn't read the doc, and his system crashes, it's his fault.
If someone uses your OS and he doesn't read the doc, and he's dead, it's your fault.
If you don't want to take any responsibility for this, simply say that in your disclaimer.

I don't think it's that clear. Note that high volume is a problem regardless of having flat setting.
Besides, I believe having per-application volume can be too complex/confusing for many users. https://www.reddit.com/r/linux/comments/2rjiaa/horrible_decisions_flat_volumes_in_pulseaudio_a/cnh4r3u

Alright. If many major distros decide to follow the upstream default there must be a persuasive reason. Now we know how to change the settings we can live with that. (Plus I think I have only ever had this issue with KDE system notification).

ArchLinux doesn't follow upstream.

PA flat volumes are especially a problem with software that are kind of buggy, like uzbl (where audio jumps to a random volume in some cases). AFAIK, most distros doesn't follow upstream and disable flat volume by default. (Ubuntu, Arch, OpenSUSE, apparently, even Fedora disabled flat volumes) as it is considered a broken-by-design feature.

Just got bit by this. Spotify spontaneously jumped to 100% and nearly blew my ears out.

Adding the following to ~/.config/pulse/daemon.conf seems to have fixed things:
flat-volumes = no

I too think we should disable flat volumes by default. I would like move forward and implement a flatVolumes option that defaults to false if nobody objects.

(triage) status of this?

Could we disable flat-volume by default ? When I use my headphone after using my main speaker (where I raise the volume), my headphone volume is too much loud.

@mikefaille: I believe "flat-volume" is about per-application volume.

@vcunat I just begin my tests. Although, I'm asking myself why others pretend that disabling "flat-volume" could help on this case https://github.com/NixOS/nixpkgs/issues/5632#issuecomment-351437293 ? Maybe, I must be more skilled in english to understand..

(well, English isn't my mother tongue)

For me the master-volume gets switched according to headphones being plugged in.   I'm fairly confident I haven't overridden any defaults around sound.  (English as mother-tongue is in minority in the NixOS community; most people seem to be European.)

For me too PulseAudio automatically does everything right.
This issue needs an example that demonstrates the effect of disabling "flat volume": I could not find an application that changes the global volume when it is supposed to change its own volume.

Here is my espectation (no surprise here) :
1a- we always manage global volume by default.
2a- if we change volume on specific sink, it would be relative on global volume
3- if a sink disappear and reappear (hotplug on headphone ?), pulse audio must remmember the last value according sink identity (hardware id ?)
An alternative way to do :
1b,2b- ignore global volume. By default, if we manage volume, we just manage sink volume.
My trouble :
https://github.com/NixOS/nixpkgs/issues/5632#issuecomment-351437293

FWIW, I've had the exact same sort of experience as mentioned here. On my big JBL LSR305 studio monitors it's merely embarassing (e.g having to explain to my neighbors why my speakers blasted some auto-playing web ad and subsequently woke them and their child at 3 in the morning thanks to PulseAudio defaults). But when I have my headphones on, it's much more of a problem, because I then risk having irreparable hearing loss (or at least ringing, aching ears for several hours).
Other distros/OSes seem to be split on the issue, so I'm not going to press any further. Sadly, this seems to be one of those scenarios where you have to choose between the user's experience and the user's safety.

zoom-us on nixos definitely sets system volume to 100% and blows out my eardrums with flat volumes.  Skype used to do it too, but I haven't used it in a long time.  I think anything making ALSA assumptions behaves poorly.

@mikefaille Your issue does not fit the description of what "flat volume" feature does. You can test if disabling it helps by doing https://github.com/NixOS/nixpkgs/issues/5632#issuecomment-233253203
@bdimcheff Thank you, I'll check it.

zoom-us on nixos definitely sets system volume to 100% and blows out my eardrums with flat volumes. Skype used to do it too, but I haven't used it in a long time. I think anything making ALSA assumptions behaves poorly.

I have the same issue with zoom-us - it always turns up the volume to 100% when joining a call.  The experience is jarring to say the least.
@cstrahan's suggestion of adding flat-volumes = no to ~/.config/pulse/daemon.conf solves this issue for me but I think this setting should be the default (just like in ArchLinux).
It saves :ear:s :)

Let's do it by default, then.

I hope this doesn't derail the discussion, but even after setting flat-volumes, I was sometimes getting ridiculous volume changes.  It turned out to be pulse "merging" volume controls.
Specifically, for historical reasons (an old laptop where having either Master or PCM volumes at 100% resulted in clipping), I manage my volume with an script wrapping amixer that adjusts PCM up or down a notch, and then sets Master to a matching volume. (E.g., if PCM is at 62%, volume-down nudges PCM down to 60%, and sets Master to 60%).  But with this "feature", pulseaudio will, at apparently random times, merge the volumes and set PCM up to 100% and Master to, say 27% to balance it out, resulting in no (perceptible) change to volume.  The next time I adjust my volume manually, PCM is at 100%, so Master is also set to 100% or thereabouts, resulting in unpleasant loudness.
I don't know if anyone else is running into this, but the only documentation I could find is the above-linked pulseaudio FAQ, a stack overflow post and similar one-offs.  It turns out there's also decent documentation in the source, but it's not too easy to find.
I couldn't get any of the config fixes to work; I don't know if I'm using them wrong, they're broken, or I just didn't do the configuration right starting from NixOS's minimal setup.  But since I had the workaround to just use Master in my own volume adjustments, that's much easier.
But if other people are running into this, it may be worth adding some configuration options or examples in nixpkgs to support this use case.  (And if so, discussion should probably move to its own issue, not here...)


Fix #17755: the bug of Request class

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues
#17755

i have lauched another pull request.


Expose remix request object to getLoadContext

This patch updates server.ts to add a third argument to getLoadContext which is the transformed Remix Request object. This is helpful for us at my company as we're switching from Cloudflare Workers to a NodeJS based Remix architecture and much of our existing getLoadContext is based off of a Request object being available.
I also think this will help others write more portable code as well.

the remixRequest would be the request available to your loader and action functions already.
export async function loader({ request }) {
  //
}

are you seeing something different?

Hi @mcansh sorry for the massive delay. The issue is not in the loaders, but in the getLoadContext callback. Right now I have to turn the Fastify req object into a Request object in that callback to be compatible with the construction we do in other runtimes (i.e. Cloudflare). It would be great if I could just get access to the one that this library already made rather than doing it a second time.

hey @vstreame sorry for my delay 😅,
do you have any code examples for this change?


Adding Pluralsight course to listing

Hi @FionaHolder
would you mind resolving the merge conflict w/your PR, and then we can get this in?
thanks!

Sorry, didn't notice the conflict originally @scottaohara, should be sorted now

Thanks!  merged it in.


Adding a policy to S3 state bucket to enforce TLS

This policy will ensure all access to the state bucket is via
a connection secured by TLS.

Thanks for the review, I have resolved all of the issues raised.

Updated what I think is all the relevant documentation. Let me know if I have missed anything. Sorry for missing the docs before.

Tests passed! Merging now.

https://github.com/gruntwork-io/terragrunt/releases/tag/v0.24.4


Update messaging.

PTAL.
cc: @jwngr

Coverage remained the same at 100.0% when pulling 6a9fc4b2b7f91438bd8345c2d375e0d8962d5c0c on tml-platform into 7c3225c6216907a93220e4132f27cfbd0e246090 on master.

I see several other places in this README where we reference the "Firebase database" as just "Firebase." We should update them all.

Closing, as this has been covered by @startupandrew's commit here


Merging client SDK work

Description
PR containing the client SDK work.
Motivation and Context
This pull request contains all of the client sdk work, including all updated unit tests, Makefile updates, and documentation updates.
How Has This Been Tested?
This pull request introduces or updates three unit test files: registrar.js, chain-test.js, asset-mgmt.js. chain-test.js and asset-mgmt.js may be run in development or network mode for deployment. All tests were automated with the "make node-sdk-unit-tests" command.
Checklist:

[x] I have added a Signed-off-by
[x] Either no new documentation is required by this change, OR I added new documentation
[x] Either no new tests are required by this change, OR I added new tests
[x] I have run goimports, go vet, and golint. I have cleaned up all valid errors and warnings in code I have added or modified. These tools may generate false positives.  The goal is clean, consistent, and readable code.

Signed-off-by: Anna Derbakova<EMAIL_ADDRESS>

That's a good question... These are auto-generated files and I'm not 100% sure how that ends up in there. But I see your point. I'll look into into this and see what can be done.

Hi @angrbrd, how did you test deploy in network mode? In particular, how did you setup the fabric network? Actually, I'm having trouble in setting up the fabric using vagrant. Nodejs, npm and typings versions are old.
BTW, I have seen that there are some dependencies missing in the file package.json like protobujs and lodash. Am I missing something?

@adecaro The sdk/node/bin/run-unit-tests.sh script runs tests in both network mode and dev mode.  You can look at that script to see how to set up the directory structure for deploy in network mode.  See the prepareExampleForDeployInNetworkMode function.  Maybe we should provide that as a standalone script to make it easier for users to set up other examples for deploy.

@adecaro I should have mentioned that setting up the directory structure is described in the README.md

@smithbk Sorry, I'm confused. run-unit-tests.sh is not mentioned in the README file.
I got how to prepare the folder structure to deploy a chaincode in network mode. That's fine.
Anyway, even before that, when I run make node-sdk from a clean vagrant instance, it just fails with the following message:
vagrant@ubuntu-1404:/opt/gopath/src/github.com/hyperledger/fabric$ make node-sdk
cp ./protos/*.proto ./sdk/node/lib/protos
cp ./membersrvc/protos/*.proto ./sdk/node/lib/protos
cd ./sdk/node && npm install && sudo npm install -g typescript && sudo npm install typings --global && typings install
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No license field.
npm ERR! Linux 3.13.0-86-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! path ../har-validator/bin/har-validator
npm ERR! code EPROTO
npm ERR! errno -71

npm ERR! EPROTO, symlink '../har-validator/bin/har-validator'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Linux 3.13.0-86-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! path npm-debug.log.b14eda52099085229a86ec264b001337
npm ERR! code ETXTBSY
npm ERR! errno -26

npm ERR! ETXTBSY, rename 'npm-debug.log.b14eda52099085229a86ec264b001337'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /opt/gopath/src/github.com/hyperledger/fabric/sdk/node/npm-debug.log
make: *** [node-sdk] Error 185

Any idea on what I'm missing?

@adecaro the run-unit-tests.sh script is what gets triggered by the make node-sdk-unit-tests command. That command is described in the README.md. If you take a look at that run-unit-tests.sh script, it will run through chaincode deployments in both network mode as well as development mode.
I am setting up a clean vagrant environment right now based on my branch with these changes. I will touch base shortly.

Thanks @angrbrd :)

@angrbrd: Travis builds are failing with npm command not found error message as the npm is not installed in travis. Updated below npm command and it worked:
cd ./sdk/node && sudo apt-get install -y npm && sudo npm install -g typescript && sudo npm install typings --global && typings install.
I could see an issue with membersrvc failed to start: Below is the error message:
Documentation generated at /home/travis/gopath/src/github.com/hyperledger/fabric/sdk/node/doc ERROR: member services failed to start; see /tmp/node-sdk-unit-test/membersrvc.log
Travis Build for reference:
"https://travis-ci.org/rameshthoomu/fabric/builds/137870434"

Regarding this issue: membersrvc image is not created before run node-sdk-tests. We have create membersrvc image first and then run node-sdk-tests. Reference Makefile: unit-test: peer-image gotools node-sdk-unit-tests. We have to update above command to run make membersrvc and peer-membersrvc-image.

@adecaro I just pushed another change should hopefully address any issues you are seeing. The things you need to do in a clean vagrant environment to run the unit tests from this branch are below. Please give this a try and let me know if it works for you.
cd $GOPATH/src/github.com/hyperledger/fabric/membersrvc
go build
cd $GOPATH/src/github.com/hyperledger/fabric/peer
go build
cd $GOPATH/src/github.com/hyperledger/fabric
make node-sdk-unit-tests

reverify jenkins

reverify jenkins

reverify jenkins

CI is still failing here?  Is anyone investigating?

@angrbrd is looking these issues.

@binhn and I discussed and agreed that we will merge this without Travis running at this time. The issue with Travis is not obvious and all the unit tests are passing locally. I have created another branch that contains identical changes, but removes the Travis CI integration. Therefore, I will now close this PR and open a new one from that new branch.


code for evaluation

great work!
can you share the preprocess code for 3DPW?
thank you very much

Thanks for your interest!
We adopt the preprocess code for 3DPW from pw3d
And then convert to 16 joints definition with a similar procedure as  prepare_data_3dhp .
Hope this helps.

Thank you very much for your great work!


Proposal: make it possible to observe chunk delimiters.

Motivation: urllib3's stream method allows users to request that they be streamed each chunk as it arrives. This is very difficult to do with h11 as it currently stands, because while h11 will try to emit one Data event per chunk, if the buffer contains a partial chunk h11 will prefer to emit that Data event and empty the buffer than to sit on it.
This is an entirely defensible design decision: while urllib3's users seem to want to be able to receive the chunks as they come in, chunk delimiters are not supposed to be semantic. However, for better or worse there are some use-cases where it is very helpful to know where chunk delimiters are.
There are three ways I can see of doing this:

Change h11's behaviour to emit NEED_DATA when a partial chunk is in the buffer, rather than a Data event for that partial chunk. This is probably inefficient in the case where people don't care about the chunk sizes, and also allows for pernicious behaviour where the user just keeps shoving data into h11's buffer without h11 ever being able to emit it.
(I should note that this is basically what h2 does with DATA frames: it emits one DataReceived event per frame. This is less problematic for h2 because of SETTINGS_MAX_FRAME_SIZE, which limits the total memory cost of buffering an entire frame.)

Add a flag to swap between the current mode and the mode described in (1), which defaults to the current mode. I think this is a bad idea, but I did want to bring it up for completeness' sake. This has all the downsides of (1) plus an extra bit of interface complexity and testing surface to go with it. Not recommended.

Add a flag to Data events that signal whether they mark the completed end of a chunk: otherwise keep the current behaviour the same. This would allow tools like urllib3 that want to care about where the chunk boundaries are basically just do a tight loop on recv() until they see a Data event with end_chunk=True. Because of h11's current semantics, any prior Data events that don't have that flag set are part of the same chunk as the one that does, and any subsequent Data events are part of a new chunk.
This has the advantage of being the smallest logical change, it's likely pretty easy and preformant to implement, and it is extremely unobtrusive to users that don't care about this concept. Altogether I think this is the best of the three possibilities in terms of giving tools that care about this (and, to be clear: as much as possible tools should try not to care about this) the ability to get what they need, while keeping that unusual use-case as far away from affecting other users as possible.

Thoughts?

So, my first response is going to be to push back and ask if urllib3 really needs this? ...Are you sure? :-)
Looking at the docs, I can't see any mention of this "give me one encoded chunk at a time" behavior, or chunk boundaries at all? Indeed it looks like the stream method takes a mandatory max-size argument which must mean that stream silently chops at least large chunks into multiple pieces, no? Or am I looking in the wrong place?
Also note that proxies are explicitly allowed to mangle chunk boundaries ("The chunked encoding is specific to each connection and is likely to be removed or recoded by each recipient (including intermediaries)" -- RFC 7230), so even if the API is there then this can hardly be reliable in the general internet...
That said...

allows for pernicious behaviour where the user just keeps shoving data into h11's buffer without h11 ever being able to emit it.

Right, h11 guarantees that it never uses unbounded memory, so option (1) is definitely out. And I don't like (2) for the same reason -- having an bounded-memory guarantee isn't very useful if the first thing popular wrappers like urllib3 do is disable it. (Presumably urllib3 will do whatever it's going to do even for callers who don't care about chunk boundaries, i.e. all of them.) Also, I don't see how this would allow stream to implement the amt argument anyway?

Add a flag to Data events that signal whether they mark the completed end of a chunk

If we're going to do this, then probably the thing to do would be to bite the bullet and start supporting chunk extensions at the same time. These are an extremely obscure feature, where each chunk can have some arbitrary key/value metadata attached to it. Right now we just throw away this metadata (which is a totally compliant option -- even proxies are allowed to do this!). Since this metadata appears at the beginning of chunks, probably the thing to do would be to instead of flagging the end of chunks, add a field to Data that means something like "this is the beginning of a new chunk, and here's the chunk extension metadata".
But again, I'd rather not do it at all :-)

Looking at the docs, I can't see any mention of this "give me one encoded chunk at a time" behavior, or chunk boundaries at all? Indeed it looks like the stream method takes a mandatory max-size argument which must mean that stream silently chops at least large chunks into multiple pieces, no? Or am I looking in the wrong place?

You're misreading that doc. amt is not mandatory, it just has a default value. And if that value if overriden to None, it will stream in chunk sizes.
The relevant work-trail is kennethreitz/requests#2449 and shazow/urllib3#550, and the documentation for the feature while not present in urllib3 is present in the Requests documentation.
So while I note that the feature cannot be reliable (indeed, I basically said as much above), that doesn't seem to me to be a compelling reason not to surface the meta-data and allow implementations to make the decision about whether to care. In this case, requests and urllib3 received feature requests to allow this feature which were implemented, and that means that we cannot remove the feature short of a full deprecation cycle. That turns out to be a pain in the neck.
As to your suggestion about supporting chunk extensions: I suspect that you really don't need to do that. Certainly, if it's on your list of features you'd like to support then by all means while we're messing about in the code it's worth adding. But you already have the data I'm asking for: you're just choosing to throw it away, where I'd like it surfaced to the user. Getting chunk extensions requires additional parsing code, which rather changes the workload of the feature. ;)

While I'm here, let me ask a follow-on. If the position of h11 were that chunk boundaries are non-semantic and cannot be relied up (a reasonable and intellectually consistent position, by the way), it seems odd that the Data event would reflect the boundaries at all. Why not just eagerly parse the entire stream and return a single Data event?

In this case, requests and urllib3 received feature requests to allow this feature which were implemented, and that means that we cannot remove the feature short of a full deprecation cycle.

Reading that history, it's not clear to me that the user even cared about chunk boundaries really -- it sorta looks like the amt=None feature snuck in alongside the implementing of chunked decoding in general, without anyone noticing that this sub-feature was arguably a bad idea and pushing back. (And the referenced blog post seems dangerously confused about the extent to which they're relying on undefined behavior.) Oops. But I guess now it is what it is. Ugh. Fine.
(It might make sense in any case to update the requests docs to emphasize that one really should set chunk_size=<int> and maybe even outright deprecate chunk_size=None? It's not a huge thing but recommending people do something that's unreliable and might trigger unbounded memory use seems suboptimal.)

As to your suggestion about supporting chunk extensions: I suspect that you really don't need to do that. Certainly, if it's on your list of features you'd like to support then by all means while we're messing about in the code it's worth adding. But you already have the data I'm asking for: you're just choosing to throw it away, where I'd like it surfaced to the user. Getting chunk extensions requires additional parsing code, which rather changes the workload of the feature. ;)

Well, parsing them isn't terrible hard -- just a regexp match, and we're already isolating them from the stream to discard them. But yeah, it's not crucial. My point was more that, given there is this other feature that potentially might make sense to support, and that other feature prefers treating chunk starts specially instead of chunk ends, then we should probably follow that here as well. (AFAICT if the goal is just to detect chunk boundaries then either approach is equally good, right?)

Why not just eagerly parse the entire stream and return a single Data event?

Because the "read a (partial) chunk" state machine was much simpler than the "read one or more complete chunks + a trailing partial". The current parser structure is stupid-simple and I don't like writing code when I can skip it :-).

Oops. But I guess now it is what it is. Ugh. Fine.

This collection of sentences describes like 90% of my opinions about software.

(AFAICT if the goal is just to detect chunk boundaries then either approach is equally good, right?)

Yep, I certainly have no objection to reversing the logic. It requires a bit more out-of-h11 buffering but urllib3 is going to have to do loads of out-of-h11 buffering anyway so we can probably tolerate it.

Because the "read a (partial) chunk" state machine was much simpler than the "read one or more complete chunks + a trailing partial". The current parser structure is stupid-simple and I don't like writing code when I can skip it :-).

That's interesting, I'd have expected that the second is basically just "keep doing the first until we get a partial match". Anyway, not important. ;)

Actually it looks like implementing flags for chunk start, or chunk end, or both, is all pretty simple -- see #20 for a non-working proof of concept. (I'll leave you to turn it into a real patch? :-))

Fixed by #20.


您好，数据能够提供下吗？

The paper author doesn't make their code public, this repository just implement the code in tensorflow, and still unfinished.


yarn start crashes because pm2 ecosystem file needs script property

Current behavior

If I currently start my VSF build using yarn start, I'll get the error No script path - aborting like:
yarn run v1.19.1
$ cross-env NODE_ENV=production TS_NODE_PROJECT="tsconfig-build.json" pm2 start ecosystem.json $PM2_ARGS
[PM2] Spawning PM2 daemon with pm2_home=/home/ubuntu/.pm2
[PM2] PM2 Successfully daemonized
[PM2][WARN] Applications server not running, starting...
[PM2][ERROR] No script path - aborting
┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬─────┬──────┬──────────┐
│ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
└──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴─────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
Done in 0.89s.

This is caused by the missing script property in ecosystem.json – it's a required one.
So, if you change the file to the following, it's working again and uses the args for the interpreter:
{
  "apps": [
    {
      "name": "server",
      "max_memory_restart": "1G",
      "instances": "4",
      "exec_mode": "cluster",
      "env": {
        "TS_NODE_PROJECT": "tsconfig-build.json",
        "NODE_ENV": "production"
      },
      "interpreter": "./node_modules/.bin/ts-node",
-      "args": "-P ./tsconfig-build.json ./core/scripts/server.ts",
+      "interpreter_args": "-P ./tsconfig-build.json",
+      "script": "./core/scripts/server.ts",
      "node_args": "--max_old_space_size=1024",
      "log_date_format": "YYYY-MM-DD HH:mm:ss",
      "ignore_watch": [
        "core/build/config.json",
        "node_modules"
      ]
    }
  ]
}

Steps to reproduce the issue

Run yarn
Run yarn build
Run yarn start
The No script path - aborting message should appear

Repository

Caused by: 9c4f55f998ed3a74f3d39ee6df58c5d20de74933 and  noticed in latest release/v1.11 - 5c73791cefcb6fc990d864cd5437e4793ac0725c
Can you handle fixing this bug by yourself?

[x] YES
[ ] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[x] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser: None
OS: All
Node: 10 LTS
Code Version: Latest release/release/v1.11 5c73791cefcb6fc990d864cd5437e4793ac0725c

PR is open: #3871

@cewald already fixed, but thanks for report!


FF: Add Include-All toggle to the Include Table all header

This story is to position that switch in the include table header and wire up the basic functionality.
The user will be able to toggle the FILTER_MODE property of the flag itself by toggling an 'Include All' switch in the include table header. By default, a newly created flag will have FILTER_MODE.EXCLUDE_ALL, so it will be in the off position.
When Include-All toggle is enabled, we will pop a confirmation modal that should give a pretty clear message about what the effect will be to the include lists.
@zackcl @amurphy-cl will need a design and some word-smithing for the confirmation modal for include-all confirmation modal and the exclude-all confirmation modal
When the toggle is confirmed and we will send a PUT request to /featureflags/:id with the value FILTER_MODE.INCLUDE_ALL for on, and FILTER_MODE.EXCLUDE_ALL.
Latest design:

I like the message that it sends when collapsing that we are clearly switching to "Include All" mode. But this design makes it look like we are still 'freezing' their ability to manage their lists when include all is selected, I couldn't tell from the video if there was any way for the user to still view and edit things.
@amurphy-cl for refinement tomorrow, can we answer some true or false for the user scenarios we want to support
When Include All is selected:

The user cannot add a list: TRUE/FALSE
The user cannot view their lists: TRUE/FALSE
The user cannot edit a list's name and description: TRUE/FALSE
The user cannot edit a list's enabled state: TRUE/FALSE
The user cannot delete a list: TRUE/FALSE
The count by "Include Lists" should go to zero: TRUE/FALSE

QA: passed as per images provides in this issue


Future expansion:  Winston?

So, traditionally I use debug for console logging (which ololog could replace, if it had the filters) and winston for centralized logging.
What's your plan for how ololog will expand going forward?

@drmikecrowe Thanks for looking into ololog. To be honest, I don't have any far-reaching plans with this particular project. But I am certainly open to any suggestions/contributions!


fullscreennotificationincomingcall.R not found

file:///home/syahioo/Pictures/Screenshots/Screenshot%20from%202024-09-30%2016-08-09.jpg
-43:-96:85:32
react-native version: 0.69.0,
I am trying to upgrade react-native-full-screen-notification-incoming-call from 0.1.12 to 1.0.1 but I got this error, does anyone know why?
shoud I upgrade my react-native to 0.74.0 to use react-native-full-screen-notification-incoming-call 1.0.1?

and this is the error I get

#67

Released


dev: remove redundant ruff target version

dev: remove redundant ruff target version
dev: remove redundant ruff target version

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #53

PR #55

PR #56

PR #57

PR #63   👈
PR #59

PR #60

PR #61

This stack of pull requests is managed by Graphite.

Merge activity

Jan 8, 8:13 PM: @MartinBernstorff merged this pull request with Graphite.


Dropdown styling changes

Adds control variables and mixins
Replaces css icon with svg (sorry @jishaal I know you spent a lot of time on it)
Tidies up padding/colours in dropdown

Replaces css icon with svg (sorry @jishaal I know you spent a lot of time on it)

@finnclark yo all good. I was just using as a means to play around 😉

NIce finn thanks for tidying this up. Could prob use the same focus ring on the dark mode button


/feed/home how get more records than 10

Hi,
When I access to /feed/home I can only get the 10 last records even if hasMore is set to true.
I tried to add offset parameter to 10 without success.
Is there something I missed ?
Thanks
Franck

feed/home uses cursor based pagination, so you use the cursor from the response to fetch more items:
https://www.deviantart.com/developers/pagination
Hope that helps

Yes, thank you !


⚠ ClamAV has degraded performance

In a65447e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 446 ms

Resolved: ClamAV performance has improved in 297028f.


Fix components scan doc

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

v6.114.4
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.0.0-beta.13 :tada:
The release is available on:

v7.0.0-beta.13
GitHub release

Your semantic-release bot :package::rocket:


FFmpeg convert error

System OS
Windows
Python Version
3.11 (CPython)
Install Source
pip / PyPi
Install version / commit hash
4.2.1
Expected Behavior vs Actual Behavior
Expected Behaviour:
To download all my songs on my playlist
Actual behaviour:
I'm new to all of this it showing a ffmpeg failed to convert error and is showing the location of the error file and one of the error files looks like this
ffmpeg_error_2023-10-19-17-01-29.txt
Cn anybody help me out here?
Steps to reproduce - Ensure to include actual links!
Just the normal process of downloading my playlists lead to the ffmpeg error

for context i have everything upto date including ffmpeg and pytube
Traceback
FFmpeg error: failed to covert

Other details
No response

can you upload the log file

no response


Enable DB seeding upon deployment to OpenShift

Talk to Dan. (Almost certainly very low priority, since we are not doing net-new deployments regularly at all.)


Added a ton of checks from the Dev Rob fork

Spent a lot of time adding more locations to the tracker. Changes include:
added checks for scarecrow song
minor tweaks to location alias'
added treasure chest game keys
added empty pots and crates
added grass
added enemy drops
added wonderitems
added gossip stone drops
icons for pots and crates
also added new settings to the menu for all the new options

Thanks a bunch for putting this together! I'll take a look over the weekend and likely merge next weekend after the standard tournament qualifiers are complete.
For timeline on the larger architectural changes, I'm targeting end of S7 brackets. Historically this has been around April/May each year. It'll address all open issues except #12 and maybe #17. I'm around 80% done, just keeping it under wraps until everything is done.

awesome. yeah this started as a personal project for use in my own runs cause I was testing out new mods like shuffle grass and enemy drops and nobody seemed to have all the checks for those marked down anywhere. both features are still in development, so more changes will probably need to be made as I'm doing testing. i already have a notepad filled with a few things i plan on tweaking. anyway i realized what i was doing would probably actually be pretty helpful to the community at large so i decided to fork your repository and here we are. One of the big changes i know already i want to make is reorder the lists to better integrate new checks into old areas. it's a little tedious having to scroll down to where all the grass and enemy drops are then back up to the other stuff in that part of the dungeon. anyway cheers

i need to force myself to take a break from this for a little while, i went down a rabbit hole of being pretty obsessed over this for a few weeks and want to get back to other stuff. will come back to it during the new year to work on those requested changes

No worries, take care of yourself! Happy holidays and hopefully see you around next year!

alright i think i addressed all the requested changes. took a little figuring out to implement multi checkboxes for child and adult trading settings. under the hood i made some edits to make it easier to make more settings into multi checkboxes in the future.

Thanks again for all the work on this! Feel free to revert my commit in your branch to undo the ordering/naming changes made.
New version is live on my side.


azure-ai-contentsafety needs linting updates for pylint version 3.2.5

ACTION NEEDED: This version of pylint will be merged on 2024-10-14. The build will begin to fail for this library if errors are not fixed.
Library name: azure-ai-contentsafety
Pylint version: 3.2.5
Pylint errors: Link to build (2024-10-05)
How to fix: Run the next-pylint tox command at the library package-level and resolve the linting errors.

../azure-ai-contentsafety>pip install "tox<5"
../azure-ai-contentsafety>tox run -e next-pylint -c ../../../eng/tox/tox.ini --root .

See the Pylint Guide for more information.

Can I work on this issue?


[BUG] JSQLParser 4.7: Postgresql: select nextval parse error

Failing SQL Feature:

Example: SELECT nextval ('client_id_seq'); can't be parsed

SQL Example:

Query Example
SELECT nextval ('client_id_seq');

Software Information:

JSqlParser version 4.7
PostgreSQL

Parse of query SELECT nextval ('client_id_seq'); throws exception:
ParseException: Encountered unexpected token: "SELECT" <K_SELECT>
    at line 4, column 1.

Was expecting one of:

    "WITH"
    <ST_SEMICOLON>

PS This sql query has been parsed fine in jsqlparser 4.6 version.

Greetings!
Confirmed, thank you for reporting.
I will look into this immediately.

Thank you for reporting. Rather embarrasing, that 3000plus tests did not contain 1 single unit for the Postgres NextVal() function.
I have added and fixed this and you can test it online here.
Latest Snapshot from here: http://manticore-projects.com/download/jsqlparser-4.7/JSQLParser-4.8-SNAPSHOT.jar

Thank you!


Custom YAML tag processors

Currently the YAML parser handles a static set of tags.  I propose to allow custom handlers to be registered to allow for handling custom tags.
This would also allow the stdlib to register some utility tags, like env: !crystal/env APP_ENV for example.
EDIT: Add example
export APP_ENV=prod
require "yaml"

# Something like this. Design TBD.
YAML.add_handler "!env" do |value|
  ENV[value]
end

yaml = <<-YAML
foo: bar
env: !env APP_ENV
YAML

YAML.parse yaml # => {"foo" => "bar", "env" => "prod"}

This should be pretty easy, just needs to hook into process_tag/process_scalar_tag.
But I'm not sure whether tags should be registered globally or specific to a YAML::Parser instance. Maybe even both?

Globally would not be necessary, you might want to parse two different kinds of tagged YAML in a single program & should not have to scratch your head to do that :)

@ryanprior Yeah, but that doesn't mean you wouldn't like to have some (inheritable?) defaults.

This is easy to implement is the handler creates one of the types supported by YAML.parse, like int, string, time, etc., but I have no idea how it would work with custom types...

But I'm not sure whether tags should be registered globally or specific to a YAML::Parser instance. Maybe even both?

Is there a reason I'm not seeing that would make it better to not have it global?

Globally would not be necessary, you might want to parse two different kinds of tagged YAML in a single program & should not have to scratch your head to do that :)

I would assume that if a YAML document doesn't have any of a registered tag, it just doesn't do anything like now.  Unless you mean processing the same tag differently in different files?

This is easy to implement is the handler creates one of the types supported by YAML.parse, like int, string, time, etc., but I have no idea how it would work with custom types...

It should also ideally work with YAML::Serializable.  I want this feature for some Athena stuff so I'll work on coming up with some implementation options.

Is there a reason I'm not seeing that would make it better to not have it global?

If application loads YAML config from trusted source (and can use env tag there) and then use YAML to parse some untrusted info (and env shouldn't be allowed there).

Based on what I learned from making the prototype and the information from https://github.com/crystal-lang/crystal/pull/8616#issuecomment-568629481, here's my proposal:

Do not provide anything custom processors by default
Have a way to define processors that would handle all documents
Have an option that would allow you to pass the processors you wish to use to YAML.parse or Type.from_yaml

These processors could override/be merged with (TBD) the global ones.
A processor could be a concrete type, like a struct that implements a #process method or something.

MyTagHandler.new

Processors could also just be a proc like it is now

Or support both?

Ex.
record MyTagHandler < YAML::TagHandler do
  def tag : String
    "!myTag"
  end

  def process(value : String)
    # Do your logic here
  end
end

\cc @lbguilherme

Actually maybe a !crystal/regex would be a good tag. Would allow parsing a string as Regex, which currently isn't possible. Has to be a tag to prevent non regex strings from being converted to regex as well.

@Blacksmoke16 Having such in stdlib - sure! Havin' it on by default - plz, no, see https://github.com/crystal-lang/crystal/pull/8616#issuecomment-568629481

Let's postpone the discussion about whether and which tags to ship with stdlib and/or enable by default. That's only the second step. We should focus on the general implementation first.

A benefit of using a custom handler type per tag is that this could probably be used with YAML::Any. We could add a module to YAML::Any::Type and tag types would need to implement that module. Procs won't work for that.
In order to keep this as small as possible, I'd consider to maybe not even use procs at all.

You could also take a look at Psych.add_tag and .add_domain_type` from Ruby's stdlib which would be pretty similar to what you're suggesting. Looking at implementations in other languages could be useful, too.

tags and their meanings should surely be bound to a YAML::ParseContext.
Figure out the core abstracton before worrying about Any or any of the things built on top of the raw parser.


Migrate from JCenter

Hello 👋  Will this project be migrated from JCenter? Thanks!

Migrated to JitPack ;)


azure storage type descriptions

On the section "Azure Storage data services", The "Azure Disk" shouldbe called "Asure managed disk", because all over the rest of Azure documentation, it is named this way. Even the hyperlink from "Azure Disk" points to a page that has title "Azure managed disk"

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 2550031e-4cf6-8d15-84e3-1c2b58951f80
Version Independent ID: 1a927119-0540-dfd9-9435-5c29c014daff
Content: Introduction to Azure Storage - Cloud storage on Azure
Content Source: articles/storage/common/storage-introduction.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@alexmbastos
Thanks for your feedback! We will investigate and update as appropriate.

@roygara - Could you please verify that this change aligns with our naming practices?

@tamram Thanks for bringing this to our attention. This doesn't align with our naming practices. @SaibabaBalapur-MSFT Please revert every change. Our only proper service name is Disk Storage.


€ code fixed on line 168

fixed typo on paragraph 55
updated URL on paragraph 217
url proposed on line 237
updated URL on paragraph 229
minor proposal on paragraph 249

Thanks!  I am, sadly, a sloppy human being.


Add Org Mode icon support

This pull request adds support for the org icon (unicorn) for *.org files.
References:

http://orgmode.org/
https://github.com/jsonreeder/vscode-org-mode

Ensure that the icon is of size 32x32 with a 2px margin.

@JimiC, I'll take care of that and revise tonight.

@JimiC, I ran into some issues with getting SVG to work correctly (I don't have access to photoshop), and so I've swapped it out for a png instead. Is that acceptable?

No worries. We'll do it for you.

@zacherybohon Please rebase your changes on a branch other than master.

@zacherybohon So here what I need from you.

Revert the changes you made and re-support SVG.
Move changes to a branch other than master.
Squash all commits into one.

I have generated the SVG icon to comply with our art guidelines. Once you've done the above I'll commit the icon on that branch.
Changing branch will require that you close this PR and create another.

@JimiC I've already pushed to his master and the change is here in the PR. If it's ok for you I'll merge it.

I don't want to sound like a prick but the proper way to submit a PR is from a branch other than master. Never the less...

@robertohuertasm Just FYI here is the setting.

Require status checks to pass before merging
Choose which status checks must pass before branches can be merged into master. When enabled, commits must first be pushed to another branch, then merged or pushed directly to master after status checks have passed.

If it's enabled then there must be some kind of bug in the GitHub flow.

@JimiC, we have not pushed directly to our master and his master is, indeed, a foreign branch. The Github check basically assures that you cannot force push, that before merging some checks are passed and that you cannot delete the branch. This can be applied to master or to whatever other branch you have in your repo.
There's no restriction regarding the foreign branch (the one bringing the PR changes). It can be named with whatever name you want. The changes happening in @zacherybohon's master are only there, not in our master, so... nothing to worry about about how we merge things. The status checks are still in place and working as expected. As you said:

When enabled, commits must first be pushed to another branch, then merged or pushed directly to master after status checks have passed.

And that's exactly what I've done. Commits were pushed to another branch zacherybohon/master and then merged into our master (which is the part of the process that still lefts to accomplish).
Hope it's clearer now. 😉

In case you wonder how the protection settings are set:

That figures, but still, I prefer a cleaner branching flow. But that's just me.

@robertohuertasm Apparently you miss ticked the checkboxes when checking the settings.
appveyor CI should be Required too.

Done!


fix for webpack/snashot builds

I've just stumbled on a similar problem to #26. Took me sometime to figure out what was going on, since I was also using snapshots and there the error is simply that java cannot find the class for the custom activity. So this PR resolves those problems. Note that there are still required changes to the user's app files which I've outlined in the README.

I've never used the snapshot feature actually, so really grateful you took the time to create this PR to help out folks who do! Great job!


It seems that the alpha and beta in config file will not be passed into the "get_sde_loss_fn".

Hi,
I just noticed that alpha and beta in config file will not be passed into the "get_sde_loss_fn", which means that the default code will only run in the mode of vanilla score-based models.
https://github.com/sony/fp-diffusion/blob/dea704eb5ae11ad26342f3610dc667cfc9813534/losses.py#L199

Hi,
Thanks for checking.
The loss https://github.com/sony/fp-diffusion/blob/dea704eb5ae11ad26342f3610dc667cfc9813534/losses.py#L199 has been corrected.


fix odps record data type error

check row type(bytes or int or str) before decoding bytes

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


5.9: [IRGen] Cast dynamic alloca to appropriate type.

Description: Stop emitting invalid LLVM IR when emitting pack metadata, witness tables, and values when stack allocating packs in async and coroutine code.
To allocate stack space for these packs, emitDynamicAlloca is called from GenPack.  The calling code expects the type of the returned llvm::Value * to be Metadata **/WitnessTable **.  In synchronous contexts, the value was indeed typed thus.  In asychronous contexts, however, it was typed i8 **.  Fix the callee to fulfill the callers' expectations by bit casting the value returned from emitDynamicAlloca to the type indicated by the caller.
Risk: Low.  There are only 9 callers of that function and of them the only callers (of which there are 3) that will see a change in behavior are in GenPack.  For the remaining 6, this change is NFC because no bitcast is inserted when the source (i8 *) and destination types are the same, and those all request i8 *.
Scope: Narrow.  Only affects variadic generic IR generation, and only changes its behavior in async and coroutine contexts.
Original PR: https://github.com/apple/swift/pull/66014
Reviewed By: Slava Pestov ( @slavapestov )
Testing: Added test case that previously triggered assertion failure.
Resolves: rdar://109540863

@swift-ci please test


Will there be more Self-Practice-Exercises after Recess Week?

Curious if there will be more Self-Practice-Exercises after Recess Week 🤔🤔🤔

Sorry. Didn't catch this lol.