HLS Segmenter V2 introduces "boiling" artefacts into the stream, compared to V1

Unsure how to share the file that it is happening to (since I can't scrub to a particular point, and screen-recording will take a while to upload), but all media that I have (downloaded from youtube via yt-dlp), when I select "HLS Segmenter V2" as the mode, it adds "boiling" or "noise" artefacts to my streams (especially noticeable on unmoving or even surfaces, like faces). When I put it back to HLS Segmenter (V1) or MPEG-TS, the artefacts are gone.
Below is my FFMPEG profile, I upped the kbit/s trying to remove the artefacts, but then noticed that they don't exist in V1.

Yeah, this is why V2 hasn't been made default yet. Some context:
V1: Separate normalize + encode process for each playout item, and playlist is modified/appended to make it look like a single continuous stream.
V2: Separate normalize process (child processes), single encode process (parent process) with unmodified playlist. This reduces problems at boundaries and presents opportunities for improved audio normalization (across multiple playout items), but introduces more artifacting when the raw frames are piped from the child processes to the parent process.
Unfortunately I'm not sure how to solve this, but I'll keep experimenting.


fix: avoid range-error

In Node.js, spread operator for large-sized array occurs Range Error:
https://stackoverflow.com/questions/51249561/aws-lambda-rangeerror-maximum-call-stack-size-exceeded
https://github.com/nodejs/node/issues/16870
When I use somewhat large image this problem happens. To avoid this I re-wrote some codes. This doesn't make no change on behaiviors.

Hi @Kanahiro !
Thank you for the PR! I'd like to merge it. So, one thing. Please do denoify and add&commit&push the genereted file.

@yusukebe
Thank you for guidance, it's done!

Okay, I'll merge now!


Run Doctest inside trait implementations in modules fails for some types

When you have a trait implementation for a type inside a module (i.e. not crate root), for some types the Run Doctest lens at the top of doctests for trait methods fails to run any test.
It seems that affected types are primitive types (str, u32, char...) and types with non-alphanumerical characters in them (&T, (T, T), [T; N]...).
Curiously enough, the issue only seems to encounter within modules; when the trait implementation is moved to the crate root, Run Doctest does its job just fine regardless of the type used (as far as I could tell).
Example:
mod hi {
    pub trait Trait {
        fn foo();
    }

    impl Trait for char {
        /// ```rust
        /// assert_eq!(1 + 1, 2);
        /// ```
        fn foo() {}
    }
}

The issue seems to be that the type name is, for some reason, dropped from the path passed to --package.

Yep, we are only handling adt's here currently https://github.com/rust-analyzer/rust-analyzer/blob/master/crates/ide/src/runnables.rs#L302

@Veykril
Just ran into this bug as well, would you be able to leave any sort of mental breadcrumbs for me if I wanted to take a stab at resolving? I see this bug appeared due to a refactoring of this function ( https://github.com/rust-analyzer/rust-analyzer/blob/master/crates/ide/src/runnables.rs#L355 )
What do I need to understand about this adt to start to try to fix?

ADT = Abstract-Data Type, meaning struct, enum and union types.
What we need at that location is the name of the type so that we can emit it for the runnable command, hence why we check if the type is an ADT, since then we can fetch the name of it.
This fails for primitive types since those are not ADTs, so we need an extra if branch here that checks for whether the type is a primitive type. I think there should be a similar function defined like the as_adt for these. Then we just need to fetch the name of the primitive there.

@Veykril Hm, I think I see.
I could add a local helper fn like this:
fn get_name(type: Type) -> Option<Name> {
    if let Some(adt) = ty.as_adt() {
        adt.name(db);
    } else if let Some(builtin) = ty.as_builtin() {
        builtin.name();
    }
    else {
        None
    }
}

And I could update this function to look like:
    let name = ty.get_name()?;

Do you think this helper function belongs better on the Type within hir crate instead?

Mkay, I could do something like
                let name = match ty.as_adt() {
                    Some(adt) => adt().name(db),
                    None => match ty.as_builtin() {
                        Some(builtin) => builtin.name(db),
                        None => None,
                    }
                };

Question, why do I see adt.name(db) taking in db if the HasName trait's name method only has &self?

Are there any docs in this repo that explain how to open a vscode project that uses a local rust-analyzer repo rather than an officially installed rust-analyzer extension? @Veykril

running cargo xtask install --server in the rust-analyzer workspace will build and install the rust-analyzer server in your cargo binaries, which if they are in your PATH can be then executed in VSCode by setting the rust-analyzer.server.path configuration to rust-analyzer.

Ok so if do the following:

run cargo xtask install --server in my rust-analyzer workspace
add "analyzer.server.path": "rust-analyzer"
ensure cargo binaries are in PATH

Then will any workspace I open up with vscode be using my local rust-analyzer instead of official extension?
Do I need to use "Run Extension (Debug build)" with the above 1-3?

Just with your 3 steps running a new VSCode instance should run the self-build server. Running the debug steps shouldnt be necessary. Though using one of the debug server tasks should also work(without the need of the steps I described before, that was just my workflow for these).

Otherwise the only relevant doc I can point you to is https://github.com/rust-analyzer/rust-analyzer/tree/master/docs/dev#launching-rust-analyzer

@Veykril Is there any way to know if vscode is in fact using local rusty-analyzer? For example, if I add println!("visit_file_defs(_) ... !!!"); within the visit_file_defs callback FnMut within runnables.rs, where should I even see that print?

Note sure if we show println, you want to use tracing to log instead and then set the RA_LOG env var to whatever tracing log level you want so info or warn for example(or for more finegrained logging path::to::module=info). The output then appears in Rust Analyzer Langauge Server(not Trace).

Hm... I have done the following:

set RA_LOG=info env var
Added the following to my settings.json in vscode: "rust-analyzer.trace.server": "verbose"
Added tracing::info!("visit_file_defs {:?}", &file_id); to pub fn visit_file_defs
Re-ran cargo xtask install --server
Opened new vscode workspace
Looked in dropdown in OUTPUT tab in my new window: I see only these two Rust Analyzer related options: Rust Analyzer Client or Rust Analyzer Server Trace. The client selection shows same output as before (just displays some configuration), and the Rust Analyzer Server Trace option is now outputting a lot of information, however NOT anything related to the tracing::info statement that I added.

RE: Your last message:

"in Rust Analyzer Language Server (not Trace)" -- There is no option for this, there is only Rust Analyzer Server Trace or Rust Analyzer Client.
_"You can check what r-a server you are running by executing the Rust-Analyzer: Run command as well" -- Doing this seems to have no affect (does nothing)

Any thoughts?

@Veykril Your assumption is correct
RE: RA_LOG, good news is, you were right, adding that caused another selectable option under OUTPUT tab for Rust Analyze Language Server
The weird news is, I cannot see my tracing output still. Even moved it to crates/rust-analyzer/src/bin/main.rs.
It seems I can trigger an error with panic!.. sort of. When I add a panic! instead of tracing::info! and then open another vscode workspace, I end up seeing this error:
ERROR [3/2/2022, 9:14:38 PM]: Bootstrap error [Error: Failed to execute rust-analyzer --version. `config.server.path` or `config.serverPath` has been set explicitly.            Consider removing this config or making a valid server binary available at that path.

However that's in Rust Analyzer Client, and I don't see my actual panic! message, and I also don't see the dropdown options for Rust Analyzer Server and Rust Analyzer Server Traces under the OUTPUT tab.
So... I'm... kind of convinced that I'm using the local rust-analyzer repo for this extension but... I still need to figure out how to see my manual tracing info though.

So I just ran into this issue with types implemented in the standard library.
Here are my repro steps:

Inside src/main.rs include the following:

use std::sync::Mutex;

fn main() {
    let m = Mutex::new(0);
}

Place your cursor (|) in Mutex::ne|w and trigger "Go to definition" (A.K.A. F12).
VS Code will display the code lens option to "Run Doctest" in the library's definition:

After clicking on that action, the output is:

Now, here are some thoughts. Note that I'm a Rust beginner (I encountered this while going though the Rust book hehe) so please take it with a grain of salt <3.

I don't think that code lens inside code that I didn't write myself should be enabled at all, since those feel like "implementor/dev-only" tools, and I don't immediately see why the clients of the APIs would need them. So I wouldn't be upset if this feature is removed (it's not working anyway...).
From the picture included in point 4 above, it seems like cargo test is running inside my current workspace, and not where the code lens is being displayed.

I don't think that code lens inside code that I didn't write myself should be enabled at all, since those feel like "implementor/dev-only" tools, and I don't immediately see why the clients of the APIs would need them. So I wouldn't be upset if this feature is removed (it's not working anyway...).

This might be VS Code's behaviour, since the Debug code lens also happens inside node_modules:

I have a slightly different manifestation of what seems like the same bug, at top level lib.rs:
use std::marker::PhantomData;

pub struct X<'a> {
    field: PhantomData<&'a ()>,
}

impl<'a> X<'a> {
    /// ```
    /// analyzer_bug::X::new();
    /// ```
    pub fn new() -> Self {
        Self { field: PhantomData }
    }
}

The Run Doctest lens attempts
cargo test --doc --package analyzer-bug -- X::new --nocapture

when it should have used "X<'a>::new".
Tested with rust-analyzer 1.68.0-nightly (8a97b48 2022-12-22).


Change License to MIT

Our default license is MIT. Need to update this repository to reflect that.

Created PR #3 for this.

closed with #3


WIP:cleanup envs/test

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

is this still a WIP?

@nirajdp76 :it is not WIP.
By they way, want to make some change on security group but depend on this PR--https://github.com/blueboxgroup/ursula-cli/pull/69

LGTM


Testing a component that is both a DragSource and DropTarget

Are there any examples that show how to test a component that is both a dragSource and dropTarget?

Hi, this test is written using Enzyme, but should get you going :)
You will find wrapInTestContext in the official documentation.
function setup(props) {
    props = props || makeProps()
    const WrapedModule = wrapInTestContext(DragableModules)
    return mount(<WrapedModule {...props} />)
  }

  describe('basic rendering', function() {
    let page

    beforeEach(function() {
      page = setup()
      props = page.props()
    })

 it('should not reorder the module to the same score', function() {
      const manager = page.get(0).getManager()
        // Obtain a reference to the backend
      const backend = manager.getBackend()

      const modules = page.find(DragableModules).get(0)

      // Find the drag source ID and use it to simulate the dragging operation
      const dragableModule = page.find(DragableEditableModule).get(0)
      const sourceId = dragableModule.getHandlerId()

      const targetId = page.find(DragableEditableModule).get(0).decoratedComponentInstance.getHandlerId()

      backend.simulateBeginDrag([sourceId])

      expect(props.reorder.called).to.be.false

      expect(modules.state.modules[0].id).to.equal(123)

      backend.simulateHover([targetId])

      expect(modules.state.modules[0].id).to.equal(123)

      backend.simulateDrop()
      backend.simulateEndDrag()

      expect(props.reorder.called).to.be.false
    })

Greetings!
Thanks for your example!! I followed your code, but my test still failed at the simulateBeginDrag with the Message: "Expected a valid source ID". I can log a sourceId and I tried the hole procedure like described on the React-Dnd Testing site but getting the same result. I run out of ideas so would be very thankfull for any hints

Try swithing the targetId and sourceIds. Which you ge tdepends on the ordering when you connect the components, i.e. Source(Target(Component)) or Target(Source(Component))

Woohooo! It works!!! Thanks a lot!!!

In addition to the above, if you are testing the component in isolation, without the drag-and-drop interaction, you must chain another DecoratedComponent if the component is both a DragSource and DropTarget:
const OriginalBox = Box.DecoratedComponent.DecoratedComponent;

You can't manipulate the state of the inner component using this method.

Hey so I have:

function wrapInTestContext(DecoratedComponent) {
  return DragDropContext(TestBackend)(
    class TestContextContainer extends React.Component {
      render() {

        console.log(this);
        return <DecoratedComponent {...this.props} />;
      }
    }
  );
}

          const PersonContext = wrapInTestContext(Person);

          const wrapper =  mount(<PersonContext person = {testPerson}/>);
;
          const manager = wrapper.get(0).getManager();

but I get
 undefined is not a constructor (evaluating 'wrapper.get(0).getManager()')

the problem is that the .get(0) resolves to:
$$typeof
:
Symbol(react.element)
And not a ReactElement


Commander wreg with peripheral register fix

Fix for wreg when used with a peripheral register. There was a reference to an undefined variable that had moved to an attribute of self.
Fixes #1034

/morph test

/morph test


fix(snippets): ads parenthesis to sqlcreateindex snippet

snippet correction for #7019

Thanks for the fix!


Can a new option be added to use backticks (`) instead of double quotes (")?

Is your feature request related to a problem? Please describe
In Vue JSX, if class appears on multiple lines without using backticks, a module resolution error will occur, and now I have to manually replace double quotes with backticks.
const Callout = ({ children }) => {
  return (
    <div
      class="rounded-xl border border-zinc-400/30 bg-gray-100/50 px-4 py-4 dark:border-neutral-500/30
        dark:bg-neutral-900/50"
    >
      {children}
    </div>
  );
};

Module parse failed: Unterminated string constant (629:15)
File was processed with these loaders:
 * ./node_modules/.pnpm/babel-loader@8.0.6_@babel+core<EMAIL_ADDRESS>You may need an additional loader to handle the result of these loaders.
|     var children = _ref5.children;
|     return h("div", {
>       "class": "rounded-xl border border-zinc-400/30 bg-gray-100/50 px-4 py-4 dark:border-neutral-500/30
|         dark:bg-neutral-900/50"
|     }, [children]);

Describe the solution you'd like
Add a jsxBackquote option to automatically replace quotes with backticks when line breaks occur in attributes such as class, className.
const Callout = ({ children }) => {
  return (
    <div
      class="rounded-xl border border-zinc-400/30 bg-gray-100/50 px-4 py-4 dark:border-neutral-500/30
        dark:bg-neutral-900/50"
    >
      {children}
    </div>
  );
};
// ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ to this ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
const Callout = ({ children }) => {
  return (
    <div
      class={`rounded-xl border border-zinc-400/30 bg-gray-100/50 px-4 py-4 dark:border-neutral-500/30
        dark:bg-neutral-900/50`}
    >
      {children}
    </div>
  );
};

Describe alternatives you've considered
A more advanced use case, automatically wrap the class content with libraries such as clsx, twMerge when there are multiple lines (but it may exceed the scope of this library).
const Callout = ({ children }) => {
  return (
    <div
      class={twMerge([
        'rounded-xl border border-zinc-400/30 bg-gray-100/50 px-4 py-4 dark:border-neutral-500/30 dark:bg-neutral-900/50',
      ])}
    >
      {children}
    </div>
  );
};

Well, the issue doesn't reproduce with Vite template using Vue 3.
What is your development environment like?

This is a very old large Vue2 project of the company, but I have to continue to maintain it 😰.

@gersomvg That's weird. Line wrapping works fine in Astro components too.
Maybe your VS Code is missing the prettier.documentSelectors setting.
If your setup is fine but line wrapping is not working, providing example code and Prettier configuration would be helpful in investigating the issue.

@ony3000 your plugin is wrapping fine, but Astro doesn't compile if  has newlines in the class="" part.

When implementing Astro integration for this plugin, I also saw https://github.com/withastro/astro/issues/4029.
I didn't take any action on this plugin at the time because it seemed to be a problem with the Astro compiler.
But it still doesn't seem to be fixed, so I'll consider adding an option.


Added new term apocrine secretion. Fixes #22291

@raymond91125 This looks Ok to me. Sorry if I missed the PR, let me know if you need help resolving the conflict.


does'nt work in<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Please make sure you have only one version of react-native-root-siblings in your project.
Run
npm list | grep react-native-root-siblings

to check react-native-root-siblings versions in your project dependency tree.

only one version 4.0.4

I run the code in your example，but the effect is not the same as the gif you provided.

Have you imported react-native-root-siblings at the very beginning in your project?
react-native-root-siblings should be imported before AppRegistry.registerComponent be called.

I have imported react-native-root-siblings before AppRegistry.registerComponent, but it does not work.
I have got the answer.  the sibling style add position is ok.
sibling: {
position: 'absolute',
left: 0,
height: 20,
width: Dimensions.get('window').width / 2,
backgroundColor: 'blue',
opacity: 0.5
}

Cool, I'm closing this now.
Basically the sibling elements is added next to the Root component which is registered by AppRegistry.registerComponent. And those siblings elements don't have a default style.


User feedback from PE dry run

Hello W10-4, I tested your product during PE dry run but unfortunately I did not manage to post my feedback on the issue tracker, sorry :( As instructed by Prof Damith, I was suggested to post my user feedback here! I hope it will more or less help you! Below are my user experiences:

I really appreciate your project for the richness of the content and functions. The exploration of the product is really interesting 👍

I wonder if there is any problem with the display of newly added recipe on the recipe panel. When I add a new recipe, it seems that the recipe is not being displayed.

I wonder if my way to add recipe with i/ prefix for instructions is correct, it seems that the instruction as mentioned in user guide does not work very well.

I think there is an inconsistency between the actually implementation and user guide. It seems that edit command for ingredient does not support "_" to link the name that user want to change.

I am not sure if plan command works as expected.

All in all, except for the small exceptions, the product works quite fine and the functions that it supports are really useful! Thank you for your effort!!

@NancyQuris Thanks so much for ur in-depth review. Appreciate that. I think we have more to work on.

Thank you for replying! Wish you test all the best! Jiayou!!

Fixed the issue regarding edit command for ingredient.

Updated the plan meal command usage instructions to specify that dates have to range from the present to the future. Thanks for the feedback!


Article name getting trimmed when you list the articles

Describe the bug
When click on the Playlist, the name of the article is getting trimmed due to the width restriction if the article name is lengthier
To Reproduce

Click on the default Playlist named Work with Posts and messages which is part of Microsoft Teams
You can see that the second article name is trimmed
Based on the design we assume that the width is taken from the current article name
So if you have an article whose name is small and you have an article name which has lengthier name, the width is inconsistent

Expected behavior
Expecting the width to be shown maximum of the listed article so that name will not be cut off
Screenshots
Screenshot which shows Issue

Ideal / Expected Screen

Learning Pathways version number
<IP_ADDRESS>

This bug will be fixed in version 4.

Thanks @juliemturner  for the super quick response. Appreciate all your efforts.

Version 4 has been released, closing this issue.


Update MAINTAINERS

Just for the proof if needed : https://github.com/go-gitea/gitea/pulls?utf8=✓&q=is%3Amerged is%3Apr author%3AMorlinest
😄
LGTM

LGTM

@sapk thx

Make LG-TM work again

@go-gitea/owners please add @Morlinest also to maintainers team in GitHub & discord

@Morlinest Done


Laravel cPanel web server configuration

I have got an Issue with the Linux server configuration, my Website/Application has successfully been deployed on the Sharing LINUX SERVER (the only configuration I have right now is the .htaccess . After two days I got the NGINX issue, after 5 days I got a 500 error, ... Now my website is not accessible,
In Other words, I am looking for a web server configuration of Laravel  5.5 website, Is there anyone who can explain to me clearly? suggestions? Tutorial?,...
Thanks in advance.

Laravel Version: #.#.#
PHP Version:
Database Driver & Version:

Description:
Steps To Reproduce:

Welcome to Laravel! We are glad to have you as part of the community.
Unfortunately GitHub is not an appropriate platform for general application issues. This is only for issues/bugs with the framework code itself.
Please close your issue, and instead try asking your question on one of the many great community support areas that will likely give you a better answer more quickly:
Laravel Slack (https://larachat.co/)
Laravel.io Forum (https://laravel.io/forum)
Laracasts Forum (https://laracasts.com/discuss)
StackOverflow (http://stackoverflow.com/questions/tagged/laravel)
Thanks!


Specify some of the common concepts for Matrix in the index

See https://github.com/matrix-org/matrix-doc/pull/2061
Fixes https://github.com/matrix-org/matrix-doc/issues/1468
Fixes https://github.com/matrix-org/matrix-doc/issues/1528
The section is not referenced by the specifications yet - they do a fairly good job of explaining it over and over. In future, it would be good to point all the references to the index.
Note: This does not attempt to solve trailing slashes for all endpoints, just the one mentioned in #2061. See https://github.com/matrix-org/matrix-doc/issues/2107 for more details.

(will accept a checkmark from either of you btw)


build: C++17 is not enabled on all platforms

Bazel builds have been C++17 since 52c9568; however, Makefile builds remain C++11. Consistent with our webpage documentation and to match TF Lite's language support, it's our desire to support and compile as C++17 on all platforms.

After trying to set -std=c++17 and c17 in PR #2648, the only problem appears to be the age of the Xtensa toolchain. The flatbuffers library includes <optional> when it's being compiled under the C++17 standard. The Xtensa toolchain is happy enough to compile with -std=c++17, but the standard library appears to be incomplete—it doesn't have <optional>. E.g., from the PR's CI run:
https://github.com/tensorflow/tflite-micro/actions/runs/10152485116/job/28074001989?pr=2648#step:3:367
xt-clang++ -std=c++17 [...]
[....]
.../micro/tools/make/downloads/flatbuffers/include/flatbuffers/stl_emulation.h:41:12: fatal error:
'optional' file not found
  #include <optional>
           ^~~~~~~~~~

Perhaps upgrading the Xtensa toolchain, which is quite old, will fix this.
For reference, the current toolchain is identified and invoked here: https://github.com/tensorflow/tflite-micro/blob/6b676567b79053d4d275ae834427b4f1259a710d/.github/workflows/xtensa_presubmit.yml#L35

I tested this out for at least the hifi3 builds and got it to compile with -stdlib=libc++. I think the default stdlib for Xtensa only supports C++14. The downside is that I think that pre-compiled library includes rtti & exception support, so it likely has some bloat. In newer versions of Xtensa toolchain, we can use libc++-re to disable those.

Fixed in #2648.


GitHub Actions 1.3.3 fails to build after updating the calendar dependency from v0.6.0 to v1.0.0

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkAlphaAarMetadata'.
> Could not resolve all files for configuration ':app:alphaRuntimeClasspath'.
   > Could not resolve io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0.
     Required by:
         project :app
      > No matching variant of io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0 was found. The consumer was configured to find a runtime of a component, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha', attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.3.1', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
          - Variant 'debugVariantMavenApiPublication' capability io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0:
> Task :app:checkAlphaAarMetadata FAILED
              - Incompatible because this component declares an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.3.1')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'debugVariantMavenJavaDocPublication' capability io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0 declares a runtime of a component:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.3.1')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'debugVariantMavenRuntimePublication' capability io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0 declares a runtime of a component:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.3.1')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'debugVariantMavenSourcePublication' capability io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0 declares a runtime of a component:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.3.1')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'releaseVariantMavenApiPublication' capability io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0:
              - Incompatible because this component declares an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.3.1')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'releaseVariantMavenJavaDocPublication' capability io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0 declares a runtime of a component:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.3.1')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'releaseVariantMavenRuntimePublication' capability io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0 declares a runtime of a component:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.3.1')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'releaseVariantMavenSourcePublication' capability io.github.boguszpawlowski.composecalendar:composecalendar:1.0.0 declares a runtime of a component:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'alpha'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.3.1')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org/

BUILD FAILED in 1m 26s
3 actionable tasks: 3 executed
Error: Process completed with exit code 1.

@GabrielGircenko Thank you for submitting the issue. Could you provide more details about the problem? E.g. in what context are you using the library, your versions of Compose and Kotlin? It's hard to deduce it from the description, and I was able to add version 1.0.0 to my other project no problem.

Ok, thanks for the info @Andranik-Asilbekyan I will look into it

Unfortunately, I was unable to reproduce the issue. However, I have found that after a bump of publishing plugin in 1.0.0, the structure of the artifact have changed. I will remove unnecessary aars from it and release it in 1.0.1. In the meantime @Andranik-Asilbekyan, @GabrielGircenko if you would be able to create sample project with the issue in order to properly test it, it would be much appreciated.

@boguszpawlowski here are my versions:
kotlinCompilerExtensionVersion '1.2.0'
compose_version '1.3.0-beta02'
gradle_version '7.3.1'
kotlin_version '1.7.0'
If I find time, I will create the test project.

@Andranik-Asilbekyan @GabrielGircenko Please test if it works correctly on 1.0.1

@boguszpawlowski verified!

@boguszpawlowski it works, thank you!


Doesn't work in Chrome or Firefox with HTTPS

You're loading unsecure content. Use protocol agnostic references in your HTML.

It works.


gain offset using control.matlab.c2d using method='matched' ?

Compared results of
sysc = ct.TransferFunction([1, z], [1, p])
sysd = ct.matlab.c2d(sysc, Ts, method='bilinear')
sysd1 = ct.matlab.c2d(sysc, Ts, method='matched')
yields a sysd1 with a gain that is about 10x that of sysd - is that expected?

Hi John great to hear from you and happy holidays. Glad to see you are using or at the very least evaluating the library.
The matched c2d is code I have never used before and it doesn’t look like we have a unit test for it, so there is a decent chance it is just a bug. Thanks for the report!
One q - when you refer to gain, do you mean the DC gain of the two systems?

I did a quick check and I agree there is something wrong in the matched transformation:
import control as ct
sysc = ct.tf([1, 2], [1, 3], name='sysc')
sysd_bilinear = ct.sample_system(sysc, 0.1, method='bilinear', name='sysd_bilinear')
sysd_matched = ct.sample_system(sysc, 0.1, method='matched', name='sysd_matched')
ct.bode([sysd_bilinear, sysd_matched, sysc])

This produces the following plot:

A couple of things to fix:

Zero frequency gain for the 'matched' transformation is incorrect.
The name of the system is lost when doing the 'matched' transformation.
The order of the system names is incorrect in the figure title

Fixed in #951.  New plot:


typo in UDF example

In the following line

func (o *outlierHandler) Snaphost() (*udf.SnapshotResponse, error) {
return &udf.SnapshotResponse{}, nil
}

Snaphost should be Snapshot.
https://github.com/influxdata/kapacitor/blob/master/udf/agent/examples/outliers/outliers.go#L67
I have gone through all the examples in repo and agent.go interface. All of them are defined as Snaphost.

@ZhijieWang  Thanks!


Making thumbnail increases file size

Module worked correctly but not as expected. My 960x960 image made 800x800 but its size increased to 524kbs from 148kbs.

var thumb = require('node-thumbnail').thumb;
// thumb(options, callback);
thumb({
source: 'H:/Desktop/Golden Associates/Golden_Web/Themes/LetsPlay/Node/thumbnail/Abhi2.jpg', // could be a filename: dest/path/image.jpg
destination: 'H:/Desktop/Golden Associates/Golden_Web/Themes/LetsPlay/Node/thumbnail',
concurrency: 4
}, function(files, err, stdout, stderr) {
if(err)
console.log(err);
if (files)
console.log(files);
if (stderr)
console.log(stderr)
console.log('All done!');
});

I hope you can understand what I want :)

That's really strange. I just tested this with the latest master, and I can't reproduce it. :(

@honza
This issue occurred when we upload image of less size like 24kb.

This is happening for me too. width is definitely smaller than my original but the size is bigger. quite strange.


svg icons not here

The svg file is missing. did you delete it?

hello

Yes, it was deleted.

be07cce

the svg file how can i get it?

index.html has finished solution with icons code in it

just go back to the previous commits and the svg file is there


Tidy templates

Move those that aren't used to unused_templates a la unused_apps and unused_scripts.

Done.


typo in configuration key

Describe the bug
The usage example shown here states that the entry for running flake in the workflow is flake8: true. However the actual implementation expects a config key called flask8 as stated below in the docs
To Reproduce
Steps to reproduce the behavior:

Use the action with flake8: true or false
Run it
See warning in the Django aws eb deployment step

[warning]Unexpected input(s) 'flake8', valid inputs are ['entryPoint', 'args', 'flask8', 'flake8_config_file', 'python_version', 'aws_access_key_id', 'aws_secret_access_key', 'django_path', 'unit_testing', 'min_coverage', 'deploy', 'postgresql_required', 'security_check']

Expected behavior
I think that the correct name of the config key should be flake8 instead flask8

Thanks a lot, @jbermudezcabrera for pointing this out. Have fixed it in the PR #22

Thank you for the quick fix 👍


Plexdrive malfunctions with non-standard characters in filename

Recently spent a couple days tracking an issue with Plexdrive. Plexdrive would refuse to load a specific sub-directory in GDrive. Did all the standard troubleshooting I read up in the forums (uninstalling Plexdrive, making sure Google didn't change file format on upload, reauthorizing API, etc). None resolved issue.
Eventually, discovered that a file had used the character | in it's name (not to be confused with lower case L or upper case i). Removing it, and waiting for Plexdrive to update the cache, immediately solved the issue.

I ran into the same issue with a Google Maps file containing a slash character in it's name like "vacation-2019/2020".

I'm not quite sure what to do about that, since the forward slash (/) is reserved as a directory separator in most Unix systems.

What probably could be done is to completely ignore file names with illegal characters and logging a warning. Any form of substitution scheme is prone to conflicting with existing files, so I don't think it is a good idea.

@felixbuenemann I fully agree and think that your proposed solution should be sufficient as having such a file is rather unlikely but would completely block any further indexing. So ignoring it and adding a log entry is in my opinion an acceptable way of handling it. Replacing the / character with something else can also be done and e.g. macOS is doing it with a : but as mentioned by you it could lead to file conflicts so I would rather not risk it for an edge case like this.

Thanks for the attention on this issue. For context: I didn't intend to name any files with "|" in the name. If I remember correctly, it was a pre-existing file I had downloaded. I don't normally use that in my file names when naming a file myself and I don't use any apps which use that as a naming convention. The solution proposed by @disenchant would be the ideal for someone of my (relatively limited) skill-level.


Is there an option for specifying the folder path to share out?

I'd like to include http-server as a dev dependency for a specific package/project, and have it share a folder that is a sibling of the folder that has the package.json.   In this example the static files folder is where I would want to share using http-server.
$/project/package.json
$/project/node_modules/
$/staticFiles/

But since that exists outside of the project folder I have to install it http-server globally. This is not a terrible or difficult thing, but I was looking for a way to designate the folder to use and I dont see a parameter that looks obvious. Is there one that I'm just missing?

Does it work to use http-server ../staticFiles/?

usage: http-server [path] [options]

🤦🏿


fix(cdk/scrolling): support multiple items per row

Add virtual scroll support to multiple columns per row. The viewport will list items with flex-wrap styles, and the width of each item has two types of values: fixed pixel and percentage. For example, {width: 200, height: 50} and {width: '25%', height: 50}.
Fixes #10114

How to fix this checks? https://github.com/angular/components/actions/runs/9988750555/job/27606001968
Is this the file need to be updated as well? https://github.com/reboot25/components/blob/multi-columns-virtual-scroll/tools/public_api_guard/cdk/scrolling.md

You have to run yarn approve-api cdk/scrolling and commit the changed file.

You have to run yarn approve-api cdk/scrolling and commit the changed file.

Thanks, I have updated the file


new feature: would it be possible do select/change the icons on the desktopview plugin

In fact, I'm using often couple of shell scripts . So I've placed them in ~/Desktop and I double click on them when needed.
To better identify them, I would have the possibility to assing different icon to each of them.
Does this is a feature I've missed somewhere ?
Thanks

You just need to give it an "Icon=" line in your *.desktop file.
For example: "Icon=view-task-child" will use the "view-task-child.png" image from the current Icon theme. You can look through the available icons in /usr/local/share/icons////.

OK. Thanks.
Where should I put the .desktop you are talking about ?
Let's say I have ~/Desktop/script1.sh and ~/Desktop/script2.sh.
How can I assign 2 different icons ?
Should I build ~/Desktop/script1.desktop and  ~/Desktop/script2.desktop ?

If I may add an opinion I would put the .sh file elewhere (maybe just you're home, home ~/scripts ?)
And then put the .desktop files in "~/Desktop" and yes you can assingn a diferent icon even if pointing to the same Exec file...
Example, I have "xvt" installed and just ln the .desktop file for /usr/local/share/applications:
% ll |g xvt
lrwxr-xr-x  1 miguelc  miguelc    41B Feb 23 18:08 xvt.desktop -> /usr/local/share/applications/xvt.desktop
And then I can simply clone it and change the icon or something else... but note both point to the same in Exec.
[miguelc@r2d2:~/Desktop ]% cat xvt.desktop
[Desktop Entry]
Type=Application
Version=1.0
Name=xvt
GenericName=xvt terminal emulator
Comment=xvt terminal emulator
Icon=/usr/local/share/pixmaps/xvt.png
Exec=xvt
Categories=GNOME;X-XFCE;X-Xfce-Toplevel;System;Utility;TerminalEmulator;
StartupNotify=false

[miguelc@r2d2:~/Desktop ]% cat xvt2.desktop
[Desktop Entry]
Type=Application
Version=1.0
Name=xvt
GenericName=xvt terminal emulator
Comment=xvt terminal emulator
Icon=Terminal
Exec=xvt
Categories=GNOME;X-XFCE;X-Xfce-Toplevel;System;Utility;TerminalEmulator;
StartupNotify=false

"Icon=Terminal" just uses the "terminal" icon provided by the theme, much like @beanpole135 explained above
Hope this helps

Thanks mike-pt. I understand better now.
In short what I'm looking for is a kind of ".desktop creator".

There might be a couple *.desktop file creators around, but I can't think of any offhand. The spec is not that complicated, and there is a link to the example page within the spec sheet (if you want to browse back through the different sections for additional information).
http://standards.freedesktop.org/desktop-entry-spec/latest/apa.html

I've not found one written wih Qt. In fact it should not be too difficult to build one like the "Launcher" in xfce.
I've try it, and GUI is done :). This is the easy part.
Unfortunately, the Qsettings objects sounds to not able to manage the .desktop files. http://qt-project.org/forums/viewthread/14796
In fact to read .dektop file Lumina is not using Qsettings either.
Maybe I should map it to XDGDesktop and write a "saveDesktopFile" ?
What do you think ?

If you are going to submit your *.desktop creator to be included with Lumina, I would recommend using the libLumina/[LuminaXDG | LuminaUtils] functions to simplify all the backend functionality. For example, you could use the XDGDesktop class as your data storage container, then just write an extension for it which converts it back into a file format (a QStringList with one line per entry), then use LUtils::writeFile() to save the actual file. The only thing you need to be vary careful about with the XDGDesktop class is that when it is filled from a *.desktop file, it is a filtered version of the full information contained in that file (for localization purposes especially, and the special "action" framework is also not used/implemented yet). So if you are trying to create a new *.desktop entry it will work fine, but for editing a current entry it might not be the best choice.

I'll try. But my time is quite limited ... it can take weeks

I've just published the 1st release of the desktop editor for lumina.
some todo to still finalise.
details are here:
https://github.com/william-os4y/lumina/commit/e4b165ed24840e1cc24c45b328a6d2965630cad4
Comments/feedbacks are welcome

I've pushed some changes.
branch is here  https://github.com/william-os4y/lumina/commits/deskEditor
any feedbacks ?

Ok, I finally got some time to look this over (at a conference in Tokyo at the moment). My first impressions are that it is coming along really well, it just needs a bit of cleanup and final touches. Here are a few things I noticed - most of them are just small little things which are easy to change. It is looking good!

General layout is good but you do have quite a bit of "dead" space at the top and bottom of the window. You might want to decrease the default window size and adjust the spacers a bit (I would recommend a single spacer between the "run in terminal" and "cancel/apply" buttons instead of one each at the top/bottom of the window).
You are missing icons on the two file retrieval buttons (might want to add tooltips or status text on them as well so that people know what it does before they click on it).
Spelling error: "stratup notification" -> "startup notification"
When saving the "Type" of the shortcut in the file, make sure to use "Application" instead of "application". While the upper/lowercase difference does not make a difference in Lumina, it might cause problems in other DE's since the standards use an uppercase "A".
I like that you don't change any localized values in the file when saving your changes, but if the base/non-localized value gets changed you should probably remove all the localized values as well (otherwise the localized version won't match up with the new non-localized version).
For example: If I load a file with a ton of translated "Name=" lines ("Name[]="), those localized lines should be removed if I changed the generic Name value from what it was previously - otherwise the user might not actually see the name change because it will use the old localized value instead of the new generic value.
When you cancel the icon selection window - it actually removes the current icon. I think the QFileDialog class has an optional boolian which you can pass to it which lets you know afterwards if the user cancelled the dialog instead of selecting something.
I am not sure what it is causing this, but every time I open one of the file selection dialogs (icon, exec, or path selection dialogs) I always start out in a different directory. You might what to put in particular places to start for each button (LOS::AppPrefix()+"/share/icons" for the icon selection dialog for instance, LOS::AppPrefix()+"/bin" for the Exec selection, etc...)
Finally, just add a window icon and title to the Qt window so that it shows up on the task manager properly.... :-)

Good work!

Thanks for the feedback.
Indeed layout was not my first priority. I was just looking at functionalities.  this WE I'll check your points 4 to 7.
Later I'll  can check layout, icons, ...

here updates:
https://github.com/william-os4y/lumina/commits/deskEditor
my comments:

I'm not against your idea, but as a 1st step, I propose you a better sizing.

done.  As described in LXDG::FindIcon, I'm using Oxygen files

done. (in the .ui file)

Done.

still to do. You are correct !!!. But this concerns several items like Name, Comment, ... I'll check how the others are managing this.

Done.

not corrected. In fact, I'm showing the directory where you were. For example for an icon in /usr/local/share/icons/oxygen/apps/hello.png, I'll open you in /usr/local/share/icons/oxygen/apps.
Same concept for WorkingDir and Command.
Is there an another problem ?

Done.

What about naming convention ? name of button, specific methods, ...
where should I install the config files (desktop-app.template and desktop-link.template) ?
Thanks

I was referring to the case where there is nothing currently selected (such as an empty Path). What I was seeing was that if I clicked on the icon button - it took me where the icon was located (that is fine) but if I then clicked on the path button (with no path selected), it opened the icon directory again (same with the exec button if no exec currently). I think you just need an additional  check for an empty value and put in some default location for each button in that case.

Regarding the template files, depending on how you use them (read only, copy, modify, etc..) you might be able to place them into the Qt resource system (compiling them into the binary itself), and just using them from there instead of worrying about file locations on the system.
You just need to add a Qt Resource file (*.qrc) to the project and add the files to there. Then in your code you prepend the file location with a colon (":") to indicate looking in the resources (it is really easy to manage resources through the Qt Designer UI).
For example: if the file is located in "/templates/mytemplate.template" you would open the resource ":/templates/mytemplate.template" within your code. You just can't make changes to a Qt resource, but it should work fine for just reading a template file into memory before making changed and saving it elsewhere.

I've just pushed a fix concerning the point 7) here above.
Concerning the desktop.template files ...
Thanks for the feedback. Thus I include my proposed template in the binary. But I would allow to users to "play with it". Thus following you, where to push them: in .lumina ? in .lumina/LuminaDE ? in .config ? ... ?
I must still work on 5).

If you want users to be able to change the default template file, then I would save it into the binary through the resource system (as mentioned before), then on application start check if a local template file exists ("~/.lumina/desktop.template" should work fine) and copy the file from the resources to the local location as necessary. This way you can always guarantee that the template file is available on disk (since you put it there on app startup if it is missing), and that the user is able to modify it since it is within the user's home directory (so every user can have their own copy of that template).

I'm nearly there:
https://github.com/william-os4y/lumina/tree/deskEditor/desktop-editor
But what could be the name of this application ?

Hum... how about "lumina-fileinfo"?
I try to keep the names somewhat descriptive of what the utility is/does, and I can foresee adding some more to this utility so that it can view a file's "properties" in addition to providing the ability to edit it's settings (if a *.desktop shortcut). This will make it a much better multi-tasker down the road.

OK. I'll send a pull-request as soon as I have adapted the code to that name.
Thanks

I've made several changes during last week. you can find them here:
https://github.com/william-os4y/lumina/commits/deskEditor
I'll not push it as a "pullrequest" until you give me your "go".

I will take a look at it here soon and let you know. I am a bit swamped with PC-BSD work at the moment, but I think I have an open time slot tomorrow to look through this and see if it it ready.

Ok, I was actually able to make some time sooner than I thought, and I only have a couple recommendations. These are both minor and you could send in a pull request to include it in the main Lumina repo whenever you feel ready.

dialog.cpp -> line 121
Instead of QPixmap(DF.icon), use LXDG::findIcon(DF.icon,"") since the icon listed does not necessary have a full/relative path included in the file. The LXDE routine should parse it out and handle all those other cases - finding the icon on the system if possible.

dialog.cpp ->lines 140 and 142
The "~" abbreviation is a shell shortcut for the user's home dir and does not work in C++/Qt. You should use QDir::homePath() instead.

Overall, it is looking really good! Thanks for working on it!


[feat] Load color votes from Postgres

On the Voting component, load the colors and vote counts from Postgres on init. Sort them by vote count.
This includes creating a backend route to query the colors from Postgres and requesting this route on the frontend component.
References
Frontend voting component
Postgres DB
Backend routes

i'd love to work on this if available

Awesome, I'll assign you @faytey . Welcome to the project!

Hey @faytey , are you actively working on this? I'd like to free it up for someone to take, if not. I'll add more issues in the future, which you can if you haven't had time for this.

Yes sorry I started yesterday but haven’t gone far, you can free it up for the other contributor, I’d wait when you add more issues. Thanks

I will like to work on this

@b-j-roberts I will love to work on this since it is similar to what I did for daily and main quests.

@addegbenga Sorry for the late reply, I'll assign you now if you are still free for the issue.

@faytey No worries, thank you for the update!

@addegbenga Sorry for the late reply, I'll assign you now if you are still free for the issue.

Yeah, i am still availaible to work on it.


Set CODEOWNERS to @AnacondaRecipes/psubs

Set CODEOWNERS to @AnacondaRecipes/psubs
This is a test. If we approve this one, I won't merge (otherwise the package is rebuild and uploaded), I will instead push to master a cherry picked commit https://github.com/AnacondaRecipes/snowflake-connector-python-feedstock/pull/22/commits/2d64f07d7d51ec4ee6259f3ca31d59411a23488c

Closed because the codeowners were added through another PR #23


Switch to using the CachedConnectionManager

Motivation
Resolves #26848
We saw issues with S7 which were (probably) related to restarts/reloads.
Changes
Replace the connection manager with the cached version.
This was outlined in another issue which ran into a similar problem: https://github.com/apache/streampipes/issues/2944

The CachedConnectionManager is actually fully blocking which causes excessive waittime with the way we handle adapters.


Add Async Documentation

At the SAME time

This PR is mostly centered around adding the Async docs to address this issue.
Like many of the other docs added, I took the time to address some legacy error tests that have been providing false positives. Will need to circle back on some of the spec updates for some of the Monoids that have already been documented. TBH I should have done a separate PR to address the specs, and WILL do so in the future to keep review time down. Also corrected a spelling error in the Maybe docs which really should have ALSO been its own PR.

Coverage remained the same at 100.0% when pulling 033bbe815f891f21b2716f365cd36c906c083069 on async-docs-specs into 8fba9fd1c80478e75785174516599c37dd874dc7 on master.

@evilsoft do you think is better to put everything in one single commit?

@HenriqueLimas Not really, what I should have done, to make it easier to review, is put the Specs in its own commit (well really its own PR),
But until a PR is made, I usually keep it to one. This makes rebasing and other branch management tasks easier.
Once I PR it publicly it though, I never amend. That way the:

Reviewer never has to kill their local before pulling down a force push
Easier to review a commit to see what was changed after feedback was addressed.
it gives a nice breadcrumb trail on changes from PR feedback.

But I still rebase if their are merge conflicts during the review cycle.

Okay going to call this done. Merging.


scala3parse

Is there any plan @lihaoyi to extend/fork scalaparse to also handle scala3? The scala3 grammar seems pretty stable now
and it would be nice to have a fast way to check for syntax.
BTW I just finished your "Hands-on-Scala" book. Fantastic book! great job!

apparently there is a PR now, not sure what's the status of it
https://github.com/com-lihaoyi/fastparse/pull/262

#262 is about fastparse. this ticket is about scalaparse, which is a fastparse-based parser for Scala itself

Fixed in #271

Sorry, this is not yet fixed.

Scala 3 syntax changed quite a bit since Scala 2. There is new syntax as well as whitespace sensitivity, so this is a lot of work. Please take the time and present your use cases as a motivation. Offering some help might help too.


text_extraction_with_bert.py model doesn't learn

Hey,
i tried to fine tune the bert model for text extraction with the provided notebook on google colab but the model doesn't learn
Epoch 1/3
WARNING:tensorflow:Gradients do not exist for variables ['tf_bert_model/bert/pooler/dense/kernel:0', 'tf_bert_model/bert/pooler/dense/bias:0'] when minimizing the loss. If you're using model.compile(), did you forget to provide a loss argument?
WARNING:tensorflow:Gradients do not exist for variables ['tf_bert_model/bert/pooler/dense/kernel:0', 'tf_bert_model/bert/pooler/dense/bias:0'] when minimizing the loss. If you're using model.compile(), did you forget to provide a loss argument?
WARNING:tensorflow:Gradients do not exist for variables ['tf_bert_model/bert/pooler/dense/kernel:0', 'tf_bert_model/bert/pooler/dense/bias:0'] when minimizing the loss. If you're using model.compile(), did you forget to provide a loss argument?
WARNING:tensorflow:Gradients do not exist for variables ['tf_bert_model/bert/pooler/dense/kernel:0', 'tf_bert_model/bert/pooler/dense/bias:0'] when minimizing the loss. If you're using model.compile(), did you forget to provide a loss argument?
323/323 [==============================] - 30s 58ms/step
epoch=1, exact match score=0.00
1346/1346 - 434s - loss: 11.8147 - activation_loss: 5.9112 - activation_1_loss: 5.9035 - 434s/epoch - 323ms/step
Epoch 2/3
323/323 [==============================] - 17s 42ms/step
epoch=2, exact match score=0.00
1346/1346 - 278s - loss: 11.9050 - activation_loss: 5.9524 - activation_1_loss: 5.9526 - 278s/epoch - 207ms/step
Epoch 3/3
323/323 [==============================] - 14s 41ms/step
epoch=3, exact match score=0.00
1346/1346 - 275s - loss: 11.9038 - activation_loss: 5.9518 - activation_1_loss: 5.9520 - 275s/epoch - 205ms/step
<keras.callbacks.History at 0x788ecebd5ed0>

@matthiaspetry - Can you provide a sample Colab notebook with a public dataset or the dataset used in the example?


angular2 in-memory-web-api only for a part of an application

I was wondering if is possible to configure angular2 in-memory-web-api only for a part of an application. I want to reach external endpoints for finished components and use in-memory-web-api for components in development stage.
I've tried to do this in the folowing two ways:
1 - Loading the data in the main and changing the XHRBackend in the components that I want to reach in-memory endpoints;
main.ts
bootstrap(AppComponent, [
    ...
    { provide: SEED_DATA, useClass: InMemoryDataService }
]);

inDevelopmentStage.service.ts
@Component({
    providers: [
        { provide: XHRBackend, useClass: InMemoryBackendService }
    ]
})

2 - Loading the data and changing the XHRBackend in the components that I want to reach in-memory endpoints;
inDevelopmentStage.service.ts
@Component({
    providers: [
        { provide: XHRBackend, useClass: InMemoryBackendService }, // in-mem server
        { provide: SEED_DATA, useClass: InMemoryDataService }      // in-mem server data
    ]
})

Is there any way that I can achieve this goal?
Thanks for your help!

Oh sure, you can definitely do this. Each component has it's own injector, which is what resolves providers for itself and all components in that subtree.
Your second example should have worked:
@Component({
    providers: [
        { provide: XHRBackend, useClass: InMemoryBackendService }, // in-mem server
        { provide: SEED_DATA, useClass: InMemoryDataService }      // in-mem server data
    ]
})

As for that component and it's subtree, XHRBackend is InMemoryBackendService instead of the service provided by HTTP_PROVIDERS.
Remember that it also applies to any other components in that subtree however. Maybe that's what was going wrong?

I'm going to test this approach again. I think may be because the DI
strategy that I was using was wrong. I'll give you a reply ASAP. Thank you
very much!
Bruno da Silva João
Front End Developer at Neoprospecta
CEO-Fundador at Feira Orgânica Delivery https://feiraorganica.com/
+55 ( 48 ) 9658-5472
Linkedin http://www.linkedin.com/in//brunojoao
On Wed, Aug 10, 2016 at 11:33 AM, Filipe Silva<EMAIL_ADDRESS>wrote:

Oh sure, you can definitely do this. Each component has it's own injector,
which is what resolves providers for itself and all components in that
subtree.
Your second example should have worked:
@Component({
providers: [
{ provide: XHRBackend, useClass: InMemoryBackendService }, // in-mem server
{ provide: SEED_DATA, useClass: InMemoryDataService }      // in-mem server data
]
})
As for that component and it's subtree, XHRBackend is
InMemoryBackendService instead of the service provided by HTTP_PROVIDERS.
Remember that it also applies to any other components in that subtree
however. Maybe that's what was going wrong?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/in-memory-web-api/issues/15#issuecomment-238885841,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABSosah_je5DZfvVcJC-CUaPkwFDnK42ks5qeeFUgaJpZM4JXM-Z
.

event now in RC5 this will perfectly fit into @NgModule scope :)

I could not get things working by using it inside and child module called Analysis.
Child Module
@NgModule({
  ...
  imports: [
    InMemoryWebApiModule.forRoot(AnalysisData) // in memory here
  ],
  providers: [
    AnalysisService // Service here
  ],
})

Child Service
import { Injectable } from '@angular/core';
import { Http } from '@angular/http';
@Injectable()
export class AnalysisService {

	constructor(private http: Http){}

	getAnalyses(){
		return this.http.get('app/analysis').toPromise();
	}

}

My route to this child module is:
  { path: 'analysis', component: AnalysisListComponent

And in my app.module I load the Analysis module
@NgModule({
    bootstrap: [
        ...
    ],
    declarations: [
        ...
    ],
    imports: [
        ...
        AnalysisModule, // loading the submodule here

Using this approach, when I reach the app/analysis the app return a 404 error. What am I doing wrong here? How can I reach the analysis in memory endpoint?
If I import the in memory module in the App module and call forRoot there, all of my http requests will pass through in memory service and that is not what I want. I want to use in memory only in a specific service, not even in a module scope, only in a service scope. and if its possible, only in a service method scope.
If you think it is better to use SO to find a solution for this, just say the word.
Thanks.

It's not really designed for your scenario. It's a Dev and demo tool and we haven't tried to make it super robust.
It might be nice to add a config option that allows for pass-thru of unrecognized routes (we take PRs).
It is also possible (perhaps easy) to reprovide both in mem web api and http services at a component level and then both will be confined to that component and its sub tree.

This feature will be very useful in case when you have established contract for new feature with api developers but they are behind you with time schedule.
That way you can start work independently on new feature which will use inMemory Api. Rest of App will use regular api.
Everyone is happy :) - especially project manager :D

@wardbell when you said "It is also possible (perhaps easy) to reprovide both in mem web api and http services at a component level and then both will be confined to that component and its sub tree." you are saing that it is already possible or it is only a tip?
I'll try to check your code more deeply to se if I came up with some idea and make a PR.
Feel free to close this issue or leave it open to see how much people need this feature and maybe to get some PR.
Thanks a lot for your help guys!

See duplicate #30. I think PR #31 will meet your needs.

Yes, did meet my needs. I'm already using the passThruUnknownUrl configuration and it is acting like I needed.
Thanks guys!


Auto Attach not working for ESM projects

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

VS Code Version: 1.84.0
OS Version: macOS 14.1 (M1)

Steps to Reproduce:

Enable Auto Attach
Create a simple Node.js ESM file (e.g. test.mjs)
Run node --inspect test.mjs
Auto Attach is not attaching

Investigation:
The leveraged NODE_OPTIONS uses the --require CLI flag to inject the bootloader. Unfortunately, this flag only works for CJS, as documented here: https://nodejs.org/docs/latest-v20.x/api/cli.html#-r---require-module

Only CommonJS modules are supported. Use --import to preload an ECMAScript module.

I tried to inject the bootloader using --import instead of --require and it does fix the issue.
Unfortunately, while using --require with ESM is a no-op, using --import with CJS throws, so specifying both --require and --import won't work to support both CJS and ESM. Maybe there should be a flag to specify if the project is ESM or CJS?

I'm not able to repro this on Node versions 18 through 21, are there additional steps I'm missing?
PS C:\Users\conno\Github\js-debug-demos\node> echo $env:NODE_OPTIONS
 --require "c:/Users/conno/AppData/Roaming/Code - Insiders/User/workspaceStorage/d535178a2a89af05d94987e397d9ab8b/ms-vscode.js-debug-nightly/bootloader.js"

PS C:\Users\conno\Github\js-debug-demos\node> fnm use 18
Using Node v18.17.1
PS C:\Users\conno\Github\js-debug-demos\node> node --inspect .\module.mjs
Debugger listening on ws://<IP_ADDRESS>:9229/e177a508-e4d6-43da-bee7-171b860f5228
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Waiting for the debugger to disconnect...

PS C:\Users\conno\Github\js-debug-demos\node> fnm use 20
Using Node v20.8.0
PS C:\Users\conno\Github\js-debug-demos\node> node --inspect .\module.mjs
Debugger listening on ws://<IP_ADDRESS>:9229/cb3b9dc3-6580-49e5-bbcf-af64b43ced2b
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Waiting for the debugger to disconnect...

PS C:\Users\conno\Github\js-debug-demos\node> fnm use 21
Using Node v21.4.0
PS C:\Users\conno\Github\js-debug-demos\node> node --inspect .\module.mjs
Debugger listening on ws://<IP_ADDRESS>:9229/6db48a0b-c1e2-4d0a-81ec-3181a5c08a64
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

I'm not able to reproduce on 1.85.1, looks like this was fixed, thanks!


to_template

Neat! I wonder if a to_template macro would be useful so that you can use Elixirs EEx to template the resource body?.... just a thought :-)

I am sorry I missed the issue, since 2013 the project is now a complete rewrite of webmachine as a plug, so combine it with any "plug" manager you want (like phoenix) to get this kind of feature.


ghcid.cabal ghc-options

Is there a reason why ghc-options specifies the -main-is flag? Isn't it redundant given the main-is option from cabal itself?

Easiest way to confirm is remove it and see if it still builds. The Cabal main-is lets you say the filename. The GHC main-is lets you say the module name if it's not Main. I think Cabal screwed up by being file name orientated, but hey ho...

Understood. Just tried it with cabal new-build and it fails. So it has to stay.

Thanks for checking


Open search user groups

Description
Usergroups added

Added a usergroups page.
Decision - whether or not to add a usergroups collection. Instead of a collection I created a datafile that holds all of the page content and page images, as well as an array of usergroup groups.
Datafile created for usergroups, as well as all styling and content on the page.
Usergroup images and links extracted from Meetup and used on our site.
Navbar - usergroups link in the community dropdown menu changed to the “/usergroups/’ instead of to the meetup.

Issues Resolved
#3187
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Excellent. Looking at this now