text:
BUGFIX: Allow arbitrary objects in the FormState

This fixes a regression introduced with #101 that prevented
objects like images and documents to be persisted in the
Form State, leading to exceptions in multi step forms.
Fixes: #143
Related: #126 #135

@bwaidelich I just realized, that the fix is not yet in the 5.2.* release. 5.2.2 still has the old code. Are there plans to release 5.2.3?

@bwaidelich I just realized, that the fix is not yet in the 5.2.* release.

Thanks, good call.. I fixed the description for https://github.com/neos/form/releases/tag/5.2.2 and added https://github.com/neos/form/releases/tag/5.2.3

repo: neos/form


text:
can :LspInfo (:checkhealth lspconfig) show more detailed info?

Description
https://github.com/neovim/nvim-lspconfig/pull/3375 removes an undocumented config.lspinfo extension point that was intended to allow config-specific augmentation of the LspInfo report. Can information such as tool versions be derived from LSP client info and/or server responses instead?
Example use case: https://github.com/neovim/nvim-lspconfig/pull/1693 which wants to report the "project file".
Proposal

✅ print the <cmd> --version result. 3375,  3383 3388
The client has workspace/configuration, so it knows its own configuration. Why can't LspInfo ask the cient for this kind of info?
The client can ask the server for workspace/workspaceFolders, which sounds related to
the Nvim client can store info from initialize, workspace/didChangeConfiguration, etc. If that info is available via e.g. vim.lsp.get_clients(), then LspInfo can use it. If info isn't available via vim.lsp.get_clients(), then question is why, and should it be?

suggested by @glacambre :

Could a new field be added to language server configurations listing additional workspace/executeCommand requests that would be nice to perform on :LspInfo? Then the als' configuration could have als-project-file in that field, and Neovim could display the result of that request as a string in LspInfo's buffer.

Maybe vim.lsp.Client could have a statusCmds: string[] field which defines how "status" can be reported by a server.

Can information such as tool versions be derived from the LSP server response instead?

No way lsp spec doesn't have a method to get information of server instead :!clangd --version not enough ? the only usage of config.lspinfo is in hls..so i think you don't worry about there..

updated proposal. clangd --version requires config-specific stuff and doesn't address things like https://github.com/neovim/nvim-lspconfig/pull/1693 which wants to report the "project file".

aha okay so can we add a health field instead of lspinfo in configs ?  this can lead more users to pay attention to checkhealth . default use info level is enought  health_info(table.concat(configs.health()), '\n')

so why can't checkhealth use root_dir to say which pattern matched, then report that?

Because there could be multiple *.gpr files in a same root directory, so root_dir isn't enough to know which one is being used by the ada language server. In such a case, clients will often use workspace/didChangeConfiguration to select a .gpr file, but storing and re-displaying that information would not work in cases where the client let the server choose a .gpr file.

instead :!clangd --version not enough ?

Maybe I misunderstood your suggestion. I think LspInfo could just do this automatically, by running [cmd, '--version'].

The output for checkhealth looks pretty bad when the current buffer is attached to gopls since it ends up printing a very large 'help' page (that gopls spits out) as the version for gopls.
gopls only reports the version if you run gopls version.
Is there a way to override how the version check occurs? Or maybe just "version" can be added to the list of options in try_format_version.

Or maybe just "version" can be added to the list of options in try_format_version.

yes, that is the idea :) PR welcome...

Added version for gopls. #3386
Probably need to add status command to each config.

Probably need to add status command to each config.

No.

Could :LspInfo also list root_dir? I have this situation:
pyproject.toml
a.py
test/
  test_a.py
  ruff.toml

ruff.lua lspconfig has this (but also mentions .git in the description, is that a general default?):
local root_files = {
  'pyproject.toml',
  'ruff.toml',
  '.ruff.toml',
}

and I currently don't understand if I'm supposed to see on or two ruff LSP servers launched when I open both a.py and test_a.py

Something I'd like to see is whether an LSP has document formatting support. I have a BufWritePre hook that will format the buffer using all available LSPs. Sometimes that doesn't behave in the way I want (e.g. conflicting styles) so I'd like to know which LSPs are being triggered.
I'm not sure this should be included in lspconfig or if a new API should exist to allow end-users to configure additional status functions to be ran for all language servers.

No way lsp spec doesn't have a method to get information of server

https://github.com/neovim/nvim-lspconfig/issues/3509#issuecomment-2548005376 mentions serverInfo.version

source: gharchive/issue

authors: WhoIsSethDaniel glacambre glepnir justinmk kaddkaka nogweii spenrose

repo: neovim/nvim-lspconfig

license_type: permissive

license_source: github-api


text:
Update init.py

Corrected docstrings

@SiddhantSadangi Let's also update the changelog before merging

source: gharchive/pull-request

repo: neptune-ai/neptune-sklearn


text:
fix declare statement at end for Mac

I ran bash www.sh and it returned:
www.sh: line 111: declare: -A: invalid option
declare: usage: declare [-afFirtx] [-p] [name[=value] ...]

For context, I'm running a macOS Mojave.

Turns out the issue has to do with the fact that Apple provides bash version ~ 3.0 by default, so you have to update with Homebrew in order for it to read the declare command.

Yup. Thanks for the readme commit :)


text:
Status of this project

Hey @nerdvegas,
What's the status of this project? There was no commit or accepted PR for over 5 months. I can see that you actively reply on some issues and google group. Do you have any big picture for the future?
Thanks,
Adrian

I've been busy on something else but should have a few months' development
time coming up, in the next month or two.
Thx
A
On Tue, Jun 19, 2018 at 12:51 AM, Adrian Krupa notifications@github.com
wrote:

Hey @nerdvegas https://github.com/nerdvegas,
What's the status of this project? There was no commit or accepted PR for
over 5 months. I can see that you actively reply on some issues and google
group. Do you have any big picture for the future?
Thanks,
Adrian
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/515, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABjqSoCENfBQJ6tqY4hghgiQqwdXkWQyks5t975wgaJpZM4Ur5wl
.

cool,
I did notice the absence of code changes/merges.  was a little worried it was getting abandoned.
What can be done to help?

authors: adriankrupa nerdvegas purestvfx

repo: nerdvegas/rez

license_source: bigquery


text:
log4net 2.0.10/11 support

Hello there
Is there planned support for log4net 2.0.10 and/or 2.0.11?
thank you

log4net 2.0.12 is out. This needs to be updated.

I prepared a PR: #187
However, I'm not sure how to run the CI, publish the NuGet package, etc. I'm not one of the maintainers.

Hi all,  @tompazourek  any news on this one?

@CrazedBear No, I'm not a maintainer of this repo, and nobody has looked at my PR contribution yet. There's not much more I can do.
For the project where I needed it, I ended up just copying the relevant code and I'm not using the library part Common.Logging.Log4NetXXXX anymore.

authors: CrazedBear DoomerDGR8 christo-djambov-axway tompazourek

repo: net-commons/common-logging


text:
Environment customization (towards intanceset)

Description
This PR adds a mode to the template CRD, inside the environment struct. Such mode changes the current behavior of instances based on templates with mode different than Default. By setting mode: Exam or mode: Exercise the following behaviors change:

custom hostname (mainly thought to ease LDB whitelisting), respectively exam.$baseHostname and exercise.$baseHostname
restrict interaction (mainly to avoid deploying unnecessary resources)
disable authentication

How Has This Been Tested?

[x] Locally
[x] Staging

/rebase

/deploy-staging

/merge

repo: netgroup-polito/CrownLabs


text:
TypeError: Cannot read properties of undefined (reading 'path')

Describe the bug
To Reproduce
Expected behavior
Screenshots
Applicable Versions:

Netlify CMS version: netlify-cms@2.10.192
Git provider: git-gateway
Browser version: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36

CMS configuration
backend:
  name: git-gateway
  branch: master
media_folder: static/img
public_folder: /img
collections:
  - name: pages
    label: Page Content
    files:
      - label: About Us Page
        name: about
        file: assets/content/about.json
        fields:
          - label: Title
            name: title
            widget: string
          - label: Header
            name: intro
            widget: markdown
          - label: Mission
            name: mission
            widget: markdown
          - label: Vision
            name: vision
            widget: markdown
          - label: More about GRDC
            name: moreInfo
            widget: markdown
    publish: true
    type: file_based_collection
    sortable_fields:
      - commit_date
      - commit_author
    view_filters: []
    view_groups: []
  - name: housing-locations
    label: Home page - Housing Locations
    format: json
    folder: assets/content/housinglocations
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    editor:
      preview: false
    fields:
      - label: Housing Location Title
        name: title
        widget: string
        required: true
      - label: Project Status
        name: status
        widget: select
        required: true
        default: Completed
        options:
          - Completed
          - Ongoing
      - label: Exact Location/Address
        name: location
        widget: string
        required: true
      - label: Starting Price
        name: startingPrice
        widget: number
        required: true
      - label: Thumbnail Description (Short)
        name: shortDescription
        widget: text
        required: true
      - label: Description (Full)
        name: description
        widget: markdown
        required: true
      - label: Thumbnail Image
        name: thumbnail
        widget: image
        required: true
      - label: Description on Commute Instructions
        name: commute-description
        widget: text
        required: true
      - label: Location Image
        name: housingLocationImage1
        widget: image
        required: false
      - label: Location Image
        name: housingLocationImage2
        widget: image
        required: false
      - label: Location Image
        name: housingLocationImage3
        widget: image
        required: false
    publish: true
    type: folder_based_collection
    sortable_fields:
      - commit_date
      - title
      - commit_author
      - shortDescription
    view_filters: []
    view_groups: []
  - name: housing-projects
    label: Projects page - Projects
    format: json
    folder: assets/content/projects
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    editor:
      preview: false
    fields:
      - label: Housing Project Title
        name: housingProjectTitle
        widget: string
        required: true
      - label: Status
        name: status
        widget: select
        default: For Sale
        options:
          - For Sale
          - For Rent
          - For Reservation
      - label: Exact Location
        name: location
        widget: string
        required: true
      - label: Housing Location
        name: housingLocation
        widget: relation
        default: Antipolo Residences
        collection: housing-locations
        valueField: title
        searchFields:
          &a1
          - title
        required: true
        value_field: title
        search_fields: *a1
      - label: Thumbnail Description (Short)
        name: shortDescription
        widget: text
        required: true
      - label: Description (Full)
        na
...

Hi @GoldstarWeb, we believe that you have a problem, but in order for anybody to help you, you need to provide as much detail as possible. The issue template contains the bare minimum of what is required (how to reproduce, expected behaviour, screenshots, etc..).
I'm closing this issue for now. If the problem persists, please open a new issue with all of the details filled out. Also, before posting a new issue, please verify that everything is all right with your environment (computer, internet, browser) and verify whether this issue was already reported by someone else. For general help, please turn to our Slack.

authors: GoldstarWeb martinjagodic

repo: netlify/netlify-cms

license: MIT


text:
feat(remix-edge-adapter)!: update default config

See https://github.com/remix-run/remix/pull/6650

@nickytonline It seems like the GitHub release was made, but it wasn't published to npm for some reason 🤔

Hi @MichaelDeBoey! Was away last week. It looks like the lock file was not right, so it didn't publish when running npm ci. We have a new version coming soon, so I'd suggest waiting for that one. Should land this week.

authors: MichaelDeBoey nickytonline

repo: netlify/remix-compute


text:
Added plot_fslr() function and a yerkes19 fetcher

I added a plot_fslr() function, which basically is a generalization of the plot_conte69() function. This function asks the user which surface atlases he wants to use. For human brains, this atlas will more often than not be the conte69 atlas. For macaque, however, other atlases exist. One of these atlases is the Yerkes19 atlas (Donahue et al., 2016, J. Neurosci.).
I also added a fetcher function: fetch_yerkes19() to download this Yerkes19 atlas.

Codecov Report

Merging #103 (5b98263) into master (79936ea) will decrease coverage by 6.00%.
The diff coverage is 10.00%.

@@            Coverage Diff             @@
##           master     #103      +/-   ##
==========================================
- Coverage   73.17%   67.16%   -6.01%
==========================================
  Files          26       26
  Lines        1838     1855      +17
==========================================
- Hits         1345     1246      -99
- Misses        493      609     +116

Impacted Files
Coverage Δ

netneurotools/datasets/__init__.py
100.00% <ø> (ø)

netneurotools/datasets/fetchers.py
84.61% <8.33%> (-4.68%)
:arrow_down:

netneurotools/plotting.py
32.58% <12.50%> (-33.83%)
:arrow_down:

netneurotools/tests/test_plotting.py
81.08% <0.00%> (-18.92%)
:arrow_down:

netneurotools/modularity.py
59.55% <0.00%> (-4.50%)
:arrow_down:

netneurotools/utils.py
82.69% <0.00%> (-3.85%)
:arrow_down:

Continue to review full report at Codecov.

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

Actually, I also found a bug in the plot_fsaverage() function, which is linked to when we added the plot_fsvertex() function. Since I was working on the plotting.py files, I thought I might as well add here in this pull request. Basically, in plot_fsaverage(), we reordered the data so that it is 'lr'. So when we call plot_fsvertex(), we should always have order=='lr'.

Nice catch!! Thanks so much for doing this. Looks good to me so I'm gonna go ahead and merge :raised_hands:

authors: VinceBaz codecov-commenter rmarkello

repo: netneurolab/netneurotools


text:
Offer mechanism to select most appropriate transport (native)

A common pattern I've seen across many libraries using Netty is to select the "best" EventLoop; where an attempt to use the native EventLoop transport is available.
public EventLoop createEventLoop() {
  if (Class.forName("io.netty.channel.epoll.EpollEventLoop") != null)
       return new io.netty.channel.epoll.EpollEventLoop(...);
   }
   // same check for kqueue
   ....
   // default
   return new DefaultEventLoop(..);
}

It might be good to offer these factories as part of netty-transport

Agree with the motivation, but one thing to consider here is that it may be dangerous for some use cases to fall-back onto something like NioEventLoopGroup. Some use cases may prefer to fail outright if one of the preferred native transports could not be found. So we may want to consider offering some type of "require native transport" form, possibly in addition to some type of "get me the best default".

See #9764, #6873, #7302, #8901 :-)

@njhill @Bennett-Lynch @fzakaria PTAL https://github.com/netty/netty/pull/10091

authors: Bennett-Lynch fzakaria njhill normanmaurer

repo: netty/netty


text:
关于netty的ByteBuf与protobuf的序列化零拷贝

你好，我在实践中使用netty+protbuf进行通信，但是每次我encode或者decode的时候，我需要将byte[]从ByteBuf读出，然后交给protobuf进行decode，或者我需要将对象由protobuf encode为byte[]后再写入ByteBuf。
这额外的一次拷贝让我有点困扰，我发现protoBuf有writeTo和readFrom函数，不知道netty是否对此有支持，或者有什么合适的方案可以告诉我呢。
非常感谢

@LinHuiG This is an issue tracker and you can ask question in Discussions, btw, please use English not Chinese.

authors: He-Pin LinHuiG


text:
Connection stay in CLOSE_WAIT

Hi,
I'm using netty 3.10.1, to communicate with devices (GPS), and in a certain time, connection are not closed (netty didn't call close connection) and leave CLOSE_WAIT status. Here is a wireshark capture for a case of it:

As you can see, the server didn't send FIN to device.

Did you call close in your codes?

I did this code :
    @Override
    public void channelDisconnected(ChannelHandlerContext ctx, ChannelStateEvent e) {
        Log.info("Closing connection by disconnect");
        e.getChannel().close();
    }
    @Override
    public void exceptionCaught(ChannelHandlerContext ctx, ExceptionEvent e) {
        Log.info("Closing connection by exception");
        e.getChannel().close();
    }
    @Override
    public void channelIdle(ChannelHandlerContext ctx, IdleStateEvent e) {
        Log.info("Closing connection by timeout");
        e.getChannel().close();
    }

@wahisoufiane how have you configured your IdleStateHandler?

of course I did it, I add in my pipeline :
pipeline.addLast("idleHandler", new IdleStateHandler(GlobalTimer.getTimer(), resetDelay, 0, 0));
and also, in the last pipe, I add a class who extends from  IdleStateAwareChannelHandler  it is where I call channelIdle(... like I said before.

Hi again,
I did a Log in netty to find out why it didn't close connection, and I found that timeout call fireChannelIdle but it is like the runnable in pipeline are not called. (wich means channelIdle is not called)

Not sure I understand correctly. Can you give more details?

    @Override
    public void channelClosed(ChannelHandlerContext ctx, ChannelStateEvent e)
            throws Exception {
        System.out.println("DESTROY || CTX : " + String.format("%08X", ctx.getChannel().getId()));
        destroy(ctx);
        ctx.sendUpstream(e);
    }

    private void fireChannelIdle(
            final ChannelHandlerContext ctx, final IdleState state, final long lastActivityTimeMillis) {
       ctx.getPipeline().execute(new Runnable() {

            public void run() {
                try {
                    channelIdle(ctx, state, lastActivityTimeMillis);
                } catch (Throwable t) {
                    fireExceptionCaught(ctx, t);
                }
            }
        });
    }

    protected void channelIdle(
            ChannelHandlerContext ctx, IdleState state, long lastActivityTimeMillis) throws Exception {
        System.out.println("IDLE FROM ISH || CTX : " + String.format("%08X", ctx.getChannel().getId()));
        ctx.sendUpstream(new DefaultIdleStateEvent(ctx.getChannel(), state, lastActivityTimeMillis));
    }

    private final class ReaderIdleTimeoutTask implements TimerTask {

        private final ChannelHandlerContext ctx;

        ReaderIdleTimeoutTask(ChannelHandlerContext ctx) {
            this.ctx = ctx;
        }

        public void run(Timeout timeout) throws Exception {
            if (timeout.isCancelled() || !ctx.getChannel().isOpen()) {
                return;
            }
            State state = (State) ctx.getAttachment();
            long currentTime = System.currentTimeMillis();
            long lastReadTime = state.lastReadTime;
            String chId = String.format("%08X", ctx.getChannel().getId());
            System.out.println("COUNTER || CTX : " + chId + " TMO : " + (currentTime - lastReadTime));
            long nextDelay = readerIdleTimeMillis - (currentTime - lastReadTime);
            if (nextDelay <= 0) {
                // Reader is idle - set a new timeout and notify the callback.
                System.out.println("TIMEOUT TRIGGER || CTX : " + chId);
                state.readerIdleTimeout =
                    timer.newTimeout(this, readerIdleTimeMillis, TimeUnit.MILLISECONDS);
                fireChannelIdle(ctx, IdleState.READER_IDLE, lastReadTime);
            } else {
                // Read occurred before the timeout - set a new timeout with shorter delay.
                state.readerIdleTimeout =
                    timer.newTimeout(this, nextDelay, TimeUnit.MILLISECONDS);
            }
        }
    }

and the log I get is:
COUNTER || CTX : 6CABCAE7 TMO : 60037
TIMEOUT TRIGGER || CTX : 6CABCAE7
COUNTER || CTX : 6CABCAE7 TMO : 120137
TIMEOUT TRIGGER || CTX : 6CABCAE7
COUNTER || CTX : 6CABCAE7 TMO : 180237
TIMEOUT TRIGGER || CTX : 6CABCAE7
COUNTER || CTX : 6CABCAE7 TMO : 240337
TIMEOUT TRIGGER || CTX : 6CABCAE7
COUNTER || CTX : 6CABCAE7 TMO : 300436
TIMEOUT TRIGGER || CTX : 6CABCAE7
COUNTER || CTX : 6CABCAE7 TMO : 360536
TIMEOUT TRIGGER || CTX : 6CABCAE7

knowing that the timeout I give is 60 second, and after that log I have CLOSE_WAIT status, till i stop my app. but in the normal case I have:
COUNTER || CTX : 6CABCAE7 TMO : 60037
TIMEOUT TRIGGER || CTX : 6CABCAE7
IDLE FROM ISH || CTX : 6CABCAE7

I went little deeper in the code, and found something that helped me but not sure that is the best solution, or if it would generate some problems somewhere.
I changed the AbstractNioChannelSink.execute(Runnable task) function from:
 @Override
    public ChannelFuture execute(ChannelPipeline pipeline, final Runnable task) {
        Channel ch = pipeline.getChannel();
        if (ch instanceof AbstractNioChannel<?>) {
            AbstractNioChannel<?> channel = (AbstractNioChannel<?>) ch;
            ChannelRunnableWrapper wrapper = new ChannelRunnableWrapper(pipeline.getChannel(), task);
            channel.worker.executeInIoThread(wrapper);
            return wrapper;
        }
        return super.execute(pipeline, task);
    }

To:
 @Override
    public ChannelFuture execute(ChannelPipeline pipeline, final Runnable task) {
        return super.execute(pipeline, task);
    }

Like it is not override, so it will execute the channelIdle immediatly.
I don't know why the IOThread is full and get the channelIdle thread waiting for some other things to be done, and didn't know what this things could be.
Another thing I found is that in the newer version of Netty, you don't create a thread in the IdleStateHandler on timeout, you call immediatly the channelIdle instead. Was that creating thread before created you a problem like in my case, that is why you change it now?

Netty 3 is EOL. Please upgrade to 4.x

authors: johnou normanmaurer wahisoufiane windie


text:
Is there a decoder like LengthFieldBasedFrameDecoder here, but LengthField is a String type?

Expected behavior
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
4.1.9
JVM version (e.g. java -version)
OS version (e.g. uname -a)

No there is not.. You can hand-roll one if you need it tho

authors: king-john normanmaurer


text:
Make use of relaxed*() in Recycler when possible

Motivation:
We should be able to make use of MessagePassingQueue.relaxed*() methods in Recycler to reduce the overhead.
Modifications:
Use MessagePassingQueue.relaxedOffer(...) / MessagePassingQueue.relaxedOffer(...)
Result:
Less overhead

/cc @nitsanw

@chrisvest it just implies that isEmpty could be false but relaxed poll still return null, adding a new semantic to null ie a new element is not available "yet"
From the JMM pov it still correctly ensure happens before relationship of consuming vs offering and it acts as a load acquire action in JMM 9 parlee.
The sole difference in term of progress guarantees is that due to relaxed poll the queue offering is serializable but not linearizable (see more info on http://psy-lob-saw.blogspot.com/2015/04/porting-dvyukov-mpsc.html comments included) and wait-free instead of lock-free

@franz1981 awesome, thanks for clarifying!

@franz1981 @chrisvest any more comments ?

authors: chrisvest franz1981 normanmaurer


text:
Fix native library packaging when cross-compile on m1 for intel

Motivation:
We did have a few build configuration problems when cross-compile which resulted in un-usable native libraries.
Modifications:

Fix native lib naming
Fix OSGI config

Result:
Fixes https://github.com/netty/netty/issues/12861

/cc @violetagg


text:
Deprecate disabling HTTP header validation

Motivation:
HTTP request/response splitting is a serious vulnerability, which is mitigated by enabling HTTP header validation. We already do header validation by default, but we have many constructors in our HTTP codec that permit turning it off. We should discourage all our down-stream users from turning header validation off.
Modification:

Deprecate all constructors in our HTTP codec, that allow header validation to be turned off.
Offer alternative constructors to all the newly deprecated ones, where header validation is enabled.
Trailer validation in DefaultLastHttpContent is now enabled by default in the DefaultLastHttpContent(ByteBuf, HttpHeaders) constructor (Behavioral change!)
Add better constructors, and more guidance in the javadocs, for DefaultHttpHeaders for those who want to use custom header validators.

Result:
We hopefully encourage integrators to validate headers. And we hopefully get fewer issues reported about disabled header validation when people run security scanners on their code.

@vietj too
Any concern?

My sole concern is not the deprecation but if there's a plan for removal at some point. Sometimes, one side, typically the client one, has zero control over the other side and if it's buggy, it has to live with.

No plans to remove the ability to opt out. I think we'll always need a way to control that aspect. Would be nice to have fewer constructors, though. Maybe we can use s builder pattern. Either here or Netty 5 only.

I'm exploring the builder idea to see if the number of constructors can be cut down a bit.

@idelpivnitskiy @slandelle With a combination of factories, builders, and configs, I think we now have a much nicer API for both guiding people toward better defaults, and offering all the knobs advanced users might need. Please take a look.

@slandelle @normanmaurer @idelpivnitskiy Rebased this. Are we happy with it?

@idelpivnitskiy Addressed all your comments

authors: chrisvest franz1981 slandelle


text:
Ability to specify matcher certificate & address

Added the ability to specify a parameter for the certificate on the matcher logic.
Added the ability to specify the address and port for the matcher.
Previously MBEDTLS3 #158

Matcher is really not meant to be used in production code? It's just sort of an example...

I would expect that most people write their own matcher, in a high level language, like golang, or node js in the backend...

Understood, and I agree, however it's provided in the core yojimbo.cpp and not an example, so the code would be included (and likely stripped) in any production build.
I'd recommend splitting out the matcher functionality from the yojimbo.cpp if it's not expected to be production ready.  However, it's the only way of using the 'connectToken' style approach.
I have just been the matcher you provided as a way of proving out the connection token code path.  I felt like the modifications made the library more development friendly even if a final shippable version would likely be modified.

OK I'll take a look at it

Hi folks, I have actually removed the matcher entirely from the latest version of Yojimbo. It really doesn't belong with the core library, and it creates a dependency on mbedtls, which ultimately, forces the usage of a very large library on the user, who may not even want to use that for https!

authors: gafferongames onehundredfeet

repo: networkprotocol/yojimbo


text:
TestXconMonitorSingleNodeHealFailed is failed

Expected Behavior
TestXconMonitorSingleNodeHealFailed is failed but should pass on CI.
Current Behavior
TestXconMonitorSingleNodeHealFailed failed sometimes.
Failure Information (for bugs)
Failed logs:
failed-024-TestXconMonitorSingleNodeHealFailed-run.log.txt
Success logs:
success-026-TestXconMonitorSingleNodeHealFailed-run.log.txt

Steps to Reproduce

Step 1
Step 2
You get the idea...

Context

Kubernetes Version:
etc.

Failure Logs

Seems working fine now.

repo: networkservicemesh/networkservicemesh


text:
checking for errors

a lot of linting issues happening and not even from my implementation code

Need to fix more prettier issues


text:
export types as types in order to work with deno 1.4

This fixes #62. All Tests are still passing despite of this change.

Thanks!

authors: fieteboerner moshest

repo: neuledge/computed-types


text:
Add example IPython notebook for 1+1 dim Burgers problem

Migrate the example file fourier_1d.py from the old master branch to main:examples as fourier_1d.ipynb [1]. Reshape the old data for the newest version of the library, and add support to layers/ for float64 and complex128 numbers.
Additionally, reformat touched files with autopep8 and update some comments.
my commits: https://github.com/neuraloperator/neuraloperator/pull/186/files/e5812a4ef0940f4e0b3e78dfb65e29d74c2017df..95f965d8a20939159e923aa2f1f6e5bf41b6cbeb
[1] Notebook

@JeanKossaifi @zongyi-li This is mostly ready for review, but I'm debugging clamping behavior after rebasing onto the latest commit in neuraloperator/neuraloperator:main.

Closed in favor of https://github.com/m4e7/neuraloperator/pull/6

repo: neuraloperator/neuraloperator


text:
[joss][sec] possible injection and data leakage

Part of: https://github.com/openjournals/joss-reviews/issues/6336
Loading a malicious JSON file can execute code and leak MRI data (or worse). A simple validation for numeric values during loading can prevent such scenario.
{"points":[[100,164,"0\"><script>window.alert('hey jude')</script><br style=\"display: none;\" data-close=\""]],"values":[10]}

Thank you for the note. We hadn't thought about this as usually the user themselves is the producer of the json file they'll later load. We'll integrate a sanitizer.

A check for numbers only has been implemented in # 6bdaf8c. Thank you @r03ert0 .

authors: anibalsolon katjaq

repo: neuroanatomy/thresholdmann

license: ISC


text:
[TST] Implemented e2e tests

Closes #18

Checklist

[ ] PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see https://neurobagel.org/contributing/pull_requests for more info)
[x] PR links to GitHub issue with mention Closes #XXXX
[x] Tests pass
[x] Checks pass

For new features:

[ ] Tests have been added

For bug fixes:

[ ] There is at least one test that would fail under the original bug conditions.

Oh and let's add a prefix for the title, probably [TST]

Thanks, almost forgot.

:rocket: PR was released in v0.1.0 :rocket:

authors: rmanaem surchs

repo: neurobagel/query-tool


text:
Ability to view older versions of the presentation

Current status
The idea is that we generate one repository per project using this repo as a template. Each time we make a new presentation on that project, we update that repo and tag a new release, triggering the website build (via Quarto) and deployment on gh-pages.
Problem
According to the above workflow, the website will always display the latest version of a presentation. The only way to view an older version would be to check out an old release/commit and build it with Quarto locally.
Vision
It would be nice to have multiple versions of a presentation deployed, navigable with some sort of version switcher dropdown.

See related issue for our Sphinx websites.

One semi-solution could be to also export the presentations as standalone HTML pages with embedded resources and archive all the older versions somewhere. The HTML file may get too large for Git over time, but we could perhaps push them to a GIN repo. All of this would be automated with gh actions, i.e:
Every time a new version is deployed on gh-pages, it is also exported as <name>_<tag>.html and pushed to the archive.

Maybe calling decktape in the deployment action could help?
See e.g. top example of a pdf for a reveal.js demo.

authors: alessandrofelder niksirbi


text:
Preprint preview service: build fail, no error description

Following up on: https://github.com/neurolibre/docs.neurolibre.org/issues/13
Kiril was able to update the T1 book to use version 0.10.x of Jupyter Book (repo, site).
I forked and converted the repo in a branch to match the format in the docs, and tried a preview submission (https://roboneuro.herokuapp.com).
I am still encountering this error, with no accompanying messages.

Any clue @agahkarakuzu ?

Alright so after some investigations:

The binder build is successfull (when triggered manually via binder.conp.cloud), this includes the soft env build and session spawning. But the execution in the interactive environment does not seems successfull (figures are empty), same behaviour for the public mybinder.org (so you should definitively check your code). You should also check this section https://mybinder.readthedocs.io/en/latest/tutorials/dockerfile.html if you definitively need Dockerfile (which is not the recommended way to have a binder environment).
The jupyter-book build is correctly triggered when I call the API manually, BUT it cannot execute the jupyter-book build command. This is because you forgot to add it as a dependency as explained here: https://docs.neurolibre.org/en/latest/SUBMIT.html#runtime
FYI: this is the command on the backend:
docker run -v /DATA:/home/jovyan/data binder-registry.conp.cloud/binder-registry.conp.cloud/binder-qmrlab-2dt1-5fbook-5fupdate-145d0a:0a148bc97a8799fe4599e99f9168555df1aeb42f jupyter-book build --path-output /home/jovyan/data/book-artifacts/qMRLab/github.com/t1_book_update/0a148bc97a8799fe4599e99f9168555df1aeb42f content
I don't know why the front-end does not correctly trigger the book build on our API, this is something @agahkarakuzu should be able to check (it could be because you are using a branch). When fixed, you will have access to the jupyter book build like http://neurolibre-data.conp.cloud/book-artifacts/qMRLab/github.com/t1_book_update/0a148bc97a8799fe4599e99f9168555df1aeb42f/book-build.log

The jupyter-book build is correctly triggered when I call the API manually, BUT it cannot execute the jupyter-book build command. This is because you forgot to add it as a dependency as explained here: https://docs.neurolibre.org/en/latest/SUBMIT.html#runtime
FYI: this is the command on the backend: 2. docker run -v /DATA:/home/jovyan/data binder-registry.conp.cloud/binder-registry.conp.cloud/binder-qmrlab-2dt1-5fbook-5fupdate-145d0a:0a148bc97a8799fe4599e99f9168555df1aeb42f jupyter-book build --path-output /home/jovyan/data/book-artifacts/qMRLab/github.com/t1_book_update/0a148bc97a8799fe4599e99f9168555df1aeb42f content

This point isn't clear to me. 1- I do have a content/ folder in my branch (see here: https://github.com/qMRLab/t1_book_update/tree/neurolibre/content), 2- I do have a binder/ folder in my branch (see here:https://github.com/qMRLab/t1_book_update/tree/neurolibre/content), however I use Dockerfile instead of requirements.txt, and since Binder skips requirements.txt if a Dockerfile is present, I didn't think I needed to add it, and 3- I don't see that docker run command anywhere discussed in the NeuroLibre documentations, so how could I have figured that out by myself to test?

Should I just add a requirements.txt file with only
jupyter-book
jupytext

as dependencies? Will this still work with my Dockerfile present in the folder? I'll try and see

I just tried, and still got the same error immediately with no details:

Is it possible it's just incompatible with the RoboNeuro test servers? Should I try and submit my T1 book as-is and see if it will work on the live servers?

Do we have any live demos of a repository that RoboNeuro was tested on that I can try and duplicate the settings for my own with?

@mathieuboudreau jupyter-book and jupytext won't be installed via requirements.txt as Dockerfile is not using that file. Can you add the minimal pip requirements of neurolibre to the pip list in the Dockerfile?
If works, we can have additional instructions or even base docker images for neurolibre.

Ahh gotcha; though, RoboNeuro fails for me within a fraction of a second, so I doubt it even has time to run the Dockerfile. I'll update it regardless, but I don't think that's the only problem I'm encountering.

Done, and as expected, got the same error:

Is roboneuro maybe not compatible with Dockerfiles?

OK, the issue was caused because of a type casting bug, mostly because I am not a savvy ruby programmer :) The new deployment resolved the problem, now you can use the service for this repo/branch.
The image built was successfull, but the book build failed, here's the log:
[FATAL tini (6)] exec jupyter-book failed: No such file or directory

Great, thanks Agah!
1- Is there a way to test RoboNeuro using a continuous integration? If so, it would be great to add this exception as a test.
2- I did get further with your change, I encountered this screen now:

However, clicking the link I get a new error:

Here is the link written out: http://neurolibre-data.conp.cloud/book-artifacts/qMRLab/github.com/t1_book_update/b720a326569f289a828b391bf174bba969da0cd7/_build/html/
It appears to be trying to get the _build/html/ folder of that repo, however _build is actually contained within a parent folder called content/ (see: https://github.com/qMRLab/t1_book_update/tree/neurolibre/content/_build/html) per what I understood from your guidelines in the readthedocs (see: https://docs.neurolibre.org/en/latest/SUBMIT.html#preprint-repository-structure).
Any clue?

@mathieuboudreau interesting, unless you fixed the book build error, it should be displaying that the book build fails. Do you have logs mailed to you indicating that the builds were successful?
So far I did not run into a directory problem, when the book build is complete, the links worked.

@mathieuboudreau here is the error log that the API should have return to you:
http://neurolibre-data.conp.cloud/book-artifacts/mathieuboudreau/github.com/t1_book_update/668f1f29a48661c4983df194ca2707bd972a99ae/book-build.log
Looking into the log, it seems that the image does not exists locally.

The latest successfull binder build was at 13h43 Sept 2d:
[I 210902 13:43:06 build:321] Started build build-qmrlab-2dt1-5fbook-5fupdate-145d0a-1dc-1f
[I 210902 13:43:06 build:323] Watching build pod build-qmrlab-2dt1-5fbook-5fupdate-145d0a-1dc-1f
[I 210902 13:43:13 build:355] Watching logs of build-qmrlab-2dt1-5fbook-5fupdate-145d0a-1dc-1f
[I 210902 13:45:45 build:385] Finished streaming logs of build-qmrlab-2dt1-5fbook-5fupdate-145d0a-1dc-1f
[I 210902 13:45:46 builder:518] Launching pod for https://github.com/qMRLab/t1_book_update: 1 other pods running this repo (2 total)
[I 210902 13:45:46 launcher:166] Creating user qmrlab-t1_book_update-ogjaoz6o for image binder-registry.conp.cloud/binder-registry.conp.cloud/binder-qmrlab-2dt1-5fbook-5fupdate-145d0a:1dc82c7a86129e974859642e6349cb8267c2df62
[I 210902 13:45:47 launcher:213] Starting server for user qmrlab-t1_book_update-ogjaoz6o with image binder-registry.conp.cloud/binder-registry.conp.cloud/binder-qmrlab-2dt1-5fbook-5fupdate-145d0a:1dc82c7a86129e974859642e6349cb8267c2df62
[I 210902 13:46:12 builder:603] Launched https://github.com/qMRLab/t1_book_update in 26s
[I 210902 13:47:12 log:140] 200 GET /build/gh/qMRLab/t1_book_update.git/1dc82c7a86129e974859642e6349cb8267c2df62 (anonymous@206.12.95.164) 246033.80ms

So I tried to build your environment yesterday and today. I tried to launch the build manually on https://binder.conp.cloud/
and it takes forever.
Unfortunately I have no clues why it is taking so long, you will need to reduce and optimize the Dockerfile (make sure you are not re-installing softwares that already exists in jupyter/base-notebook:8ccdfc1da8d5 for ex.). Again, I want to re-emphase that using Dockerfiles is not the preferable way to spawn a neurolibre instance, exactly because of this kind of issues.
On July 29th, the build was successful so something is wrong with your newest updates:

Alright so after some investigations:
1. The binder build is successfull (when triggered manually via https://binder.conp.cloud/), this includes the soft env build and session spawning. But the execution in the interactive environment does not seems successfull (figures are empty), same behaviour for the public mybinder.org (so you should definitively check your code). You should also check this section https://mybinder.readthedocs.io/en/latest/tutorials/dockerfile.html if you definitively need Dockerfile (which is not the recommended way to have a binder environment).

Again, I want to re-emphase that using Dockerfiles is not the preferable way to spawn a neurolibre instance, exactly because of this kind of issues.

Hi @ltetrel,
Thanks for that heads up. While I understand, it's impossible to configure the environment for this notebook with only requirements/env/wtv other files. Also, as more and more people are adopting Docker and Singularity, I think this will be a necessary service for NeuroLibre to provide, in my opinion.

I'll try again, but I'm fairly certain that this dockerfile built on MyBinder, I'll try again

I'm wonder if this recent feature (and/or bug) in pipy might be the cause of the much longer build time now:
https://github.com/pypa/pip/issues/10201
https://pip.pypa.io/en/stable/user_guide/#dependency-resolution-backtracking
As I'm experiencing something similar in the MyBinder build log:

It's not stuck here, but I've been downloading different versions of the attrs pip packages for like 20 minutes now.

(no idea why it's taking 5+ minutes for 40kb packages though)

Here's some tips on how to deal with the new pip dependency resolver: https://stackoverflow.com/questions/65122957/resolving-new-pip-backtracking-runtime-issue

I'm wonder if this recent feature (and/or bug) in pipy might be the cause of the much longer build time now:
pypa/pip#10201
https://pip.pypa.io/en/stable/user_guide/#dependency-resolution-backtracking
As I'm experiencing something similar in the MyBinder build log:

It's not stuck here, but I've been downloading different versions of the attrs pip packages for like 20 minutes now.

Good catch! I think for this current submission, the best advice would be to reduce the complexity of the dependencies https://pip.pypa.io/en/stable/user_guide/#audit-your-top-level-requirements

Yeah I saw that; the pip dependencies that we explicitly specify in the Dockerfile are the minimum ones required for us, so I might try using the legacy resolver since we're in a rush a the moment.

I will add a note on that issue in the docs, since it could happen to other people with complex submission as well.

So, by adding this line to the Dockerfile,
https://github.com/qMRLab/t1_book_update/blob/bc68bec6de695b85473e2a2e9bf2644668c3f45b/binder/Dockerfile#L45
the image built much quicker on MyBinder and executed correctly,

However, when making the same change in the neurolibre branch (which my MyBinder branch forked out of),
https://github.com/qMRLab/t1_book_update/blob/ceee653c23f2f07012f9841e0ab086be210adff7/binder/Dockerfile#L45
RoboNeuro immediately failed without building again, and did not send me a log.

@agahkarakuzu how did you resolve this the other day?

@mathieuboudreau I gave it a try
qmrlab/t1book_upate neurolibre branch, is this the one?
If so, @ltetrel  I receive 409 as response to that request.

yup, I tried twice

@mathieuboudreau I gave it a try
qmrlab/t1_book_upate neurolibre branch, is this the one?
If so, @ltetrel I receive 409 as response to that request.

Yes, there is a lock file that I just deleted manually because of the previous on-going build (still need to better manage them).  Can you re-try now?
Also I think it would be important to propagate all the errors (that the API returns) to the user @agahkarakuzu, as well as the build log. From the user perspective, receiving something empty is really frustrating :crying_cat_face:

@ltetrel I agree! I will need to deal with that 409 case, it is a bit tricky, I will sit down and think about it :D
Now it is running without 409, will let you know.

@ltetrel what should we say to the user in case 409 by the way? Something like You run out of tests allowed for this user/repo, get in touch with us ? What would be the solution in this case?

@ltetrel what should we say to the user in case 409 by the way? Something like You run out of tests allowed for this user/repo, get in touch with us ? What would be the solution in this case?

You are not allowed to run more than one submission per repository, please re-try when the previous request finished. ?

And a message saying that if the submission is taking too long (what happened here), then they should get in touch with us by e-mail.

It may have terminated because of the front-end worker:
 SidekiqStatus::Container::StatusNotFound: 5eadb14e27a4c7ebfdda9346

Do you emit something specific when the build is timed out on your end?

No I don't manage that, I don't have control over that this info is on the binderhub cluster.
The only thing I can do is to stream back the binder build logs (which says at the end that the build timed-out).

Now that the image is correctly built on the server, I found that:

Your binder environment does not have jupyter-book installed which is mandatory for the submission to work.
The repository layout is not correct since you are changing it in your Dockerfile (in ~/work/t1_book_update), and pulling the repo form github (https://github.com/qMRLab/t1_book_update/blob/ceee653c23f2f07012f9841e0ab086be210adff7/content/Dockerfile#L64). I would advice you to use the COPY docker command to copy directly from the repo into the image ex:

COPY . ~/work/t1_book_update

@mathieuboudreau Also be carefull with this line, basically all your data will be saved into the image, which makes it really large.
Large docker images makes the spawn time really long, impact your computing performance in the environment, and takes an incredible amount of space in our servers (data length x number of versions you push).
You should use a data requirement for this type of behaviour: https://docs.neurolibre.org/en/latest/SUBMIT.html#data

@mathieuboudreau Also be carefull with this line, basically all your data will be saved into the image, which makes it really large (currently 3.4G).
Large docker images makes the spawn time really long, impact your computing performance in the environment, and takes an incredible amount of space in our servers (data length x number of versions you push).
You should use a data requirement for this type of behaviour: https://docs.neurolibre.org/en/latest/SUBMIT.html#data

Thanks for the tip Loic. I don't think we're actually downloading any data using repo-2-docker in this instance; the build size is due to our dependencies, but I'll double check. I think we just added that line once upon a time for testing purposes, while testing out your package.

@mathieuboudreau Now that the image is correctly built on the server, I found that:
The repository layout is not correct since you are changing it in your Dockerfile (in ~/work/t1_book_update), and pulling the repo form github (https://github.com/qMRLab/t1_book_update/blob/ceee653c23f2f07012f9841e0ab086be210adff7/content/Dockerfile#L64).
as a consequence the jupyter-book build on our backend fails:
Usage: jupyter-book build [OPTIONS] PATH_SOURCE
Try 'jupyter-book build -h' for help.

Error: Invalid value for 'PATH_SOURCE': Path 'content' does not exist.

I would advice you to use the COPY docker command to copy directly from the repo into the image ex:
COPY . ~/work/t1_book_update/

Hmmmm, I understand the problem. However I don't think I can just copy the repo either, because I need to run the commands below it in the same "session" (i.e. different RUNs don't "see" each other, as far as I understand it if I copy the repo that way a run below it won't be able to execute:
https://github.com/qMRLab/t1_book_update/blob/ceee653c23f2f07012f9841e0ab086be210adff7/content/Dockerfile#L66-L75
, but maybe @agahkarakuzu can correct me).

Documentation will need to be added, as when I read the NeuroLibre doc I wasn't informed of this limitation re: Dockerfiles and how to configure it correctly.

Documentation will need to be added, as when I read the NeuroLibre doc I wasn't informed of this limitation re: Dockerfiles and how to configure it correctly.

Yep, I made lot of changes these days. Can you check it now to see if it is more clear ?

@ltetrel do we have a demo repo that builds on RoboNeuro that you guys tested and validated the service on, so that I can go in and explore the directory structure inside the Docker image and see how it should look like for the Jupyter Book to work correctly?

I'd like to avoid too many RoboNeuro builds, and am afraid that blindly debugging the Dockerfile to get the correct setting can will several tries.

You can check this one: https://github.com/ltetrel/nha2020-nilearn
Agah may have others I think.

@mathieuboudreau Now that the image is correctly built on the server, I found that:
The repository layout is not correct since you are changing it in your Dockerfile (in ~/work/t1_book_update), and pulling the repo form github (https://github.com/qMRLab/t1_book_update/blob/ceee653c23f2f07012f9841e0ab086be210adff7/content/Dockerfile#L64).
as a consequence the jupyter-book build on our backend fails:
Usage: jupyter-book build [OPTIONS] PATH_SOURCE
Try 'jupyter-book build -h' for help.

Error: Invalid value for 'PATH_SOURCE': Path 'content' does not exist.

I would advice you to use the COPY docker command to copy directly from the repo into the image ex:
COPY . ~/work/t1_book_update/

The principal solution to this issue was resolving a bug where I was checking out a repo after cloning it, but before opening the directory.
See: https://github.com/qMRLab/t1_book_update/commit/3bb10c9dc2bb434f5674d2dadd807b888a0dd74a

I then encountered another issue,
Traceback (most recent call last):
  File "/opt/conda/lib/python3.6/site-packages/jupyter_book/cli/main.py", line 244, in build
    parse_toc_yaml(toc)
  File "/opt/conda/lib/python3.6/site-packages/sphinx_external_toc/parsing.py", line 82, in parse_toc_yaml
    return parse_toc_data(data)
  File "/opt/conda/lib/python3.6/site-packages/sphinx_external_toc/parsing.py", line 88, in parse_toc_data
    raise MalformedError(f"toc is not a mapping: {type(data)}")
sphinx_external_toc.parsing.MalformedError: toc is not a mapping: <class 'list'>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/conda/bin/jupyter-book", line 8, in <module>
    sys.exit(main())
  File "/opt/conda/lib/python3.6/site-packages/click/core.py", line 1137, in __call__
    return self.main(*args, **kwargs)
  File "/opt/conda/lib/python3.6/site-packages/click/core.py", line 1062, in main
    rv = self.invoke(ctx)
  File "/opt/conda/lib/python3.6/site-packages/click/core.py", line 1668, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/conda/lib/python3.6/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/conda/lib/python3.6/site-packages/click/core.py", line 763, in invoke
    return __callback(*args, **kwargs)
  File "/opt/conda/lib/python3.6/site-packages/jupyter_book/cli/main.py", line 247, in build
    f"The Table of Contents file is malformed: {exc}\n"
  File "/opt/conda/lib/python3.6/site-packages/jupyter_book/utils.py", line 48, in _error
    raise kind(box)
RuntimeError:
[91m===============================================================================[0m

The Table of Contents file is malformed: toc is not a mapping: <class 'list'>
You may need to migrate from the old format, using:

	jupyter-book toc migrate /home/jovyan/work/t1_book_update/content/_toc.yml -o /home/jovyan/work/t1_book_update/content/_toc.yml

[91m===============================================================================[0m

Running Jupyter-Book v0.11.3

which was resolved by reverting jupyter-book to exactly the version 0.10.0 (the version that it was initially built for). Any versions above, it did not work due to 1- a weird SoS issue during build and/or 2- mismatch in how the ToC needs to be formatted with the newer versions.

After a lot of back and forth due to my repo's RoboNeuro files being locked after each build, no logs being sent to me when errors occured, and no UI messages to me on the web,  and a lot of help by @ltetrel, I was finally able to successfully build a book using RoboNeuro!

Before submitting officially, I'll have to do a little bit of cleanup in the book due to some of the transition needed from the old jupyter book format to the current one (the equations, figures aren't centered anymore), but that should be quick I'd say.
Here's some other things of note:
When my book finished building, it didn't alert me in the browser. Instead, it showed:

But if I went back and built again, it said it found the book and opened it.
Also, while RoboNeuro allows me to give a branch or git ref, the submission doesn't:

Congrats for the submission!

RoboNeuro files being locked after each build

I tried "manually" to submit your repo (calling the API via command line instead the website or RoboNeuro) and the lock file is correctly being deleted. I suspect that what happened is that when the user (you) close his session (the submission page), the API call is somehow canceled. As a result the submission building is canceled and the lock file stays on the server (so the API treat the submission as currently active).
I added a mechanism where the lock file would automatically be deleted after 30min, so it should prevent user to be locked in the future. But @agahkarakuzu you should check how RoboNeuro manage user closing their session.

You pinged https://github.com/pypa/pip/issues/10201 so I took a quick look at the docker file: https://github.com/qMRLab/t1_book_update/blob/neurolibre/binder/Dockerfile#L45
And I build an independent requirements file based on this in which I was able to reproduce the long backtracking issue:
octave_kernel
sos==0.17.7
sos-notebook==0.17.2
sos-python==0.9.12.1
sos-bash==0.12.3
sos-matlab==0.9.12.1
sos-ruby==0.9.15.0
sos-sas==0.9.12.3
sos-julia==0.9.12.1
sos-javascript==0.9.12.2
sos-r==0.9.12.2
scipy
plotly==3.10.0
flask
ipywidgets
nbconvert==5.4.0
jupyterlab==2.2.0
jupyter-book==0.10.0
jupytext
repo2data

I tested it using the optimized version of backtracking I have proposed here: https://github.com/pypa/pip/issues/10479
It quickly produce this error, hope it helps you build a better dependency file in the future:
ERROR: Cannot install -r .\reqs.txt (line 18), -r .\reqs.txt (line 3), jupyter-book and nbconvert==5.4.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested nbconvert==5.4.0
    sos-notebook 0.17.2 depends on nbconvert>=5.1.1
    jupyter-book 0.10.0 depends on nbconvert<6
    myst-nb 0.11.1 depends on nbconvert~=5.6

In my testing if I loosen the user nbconvert requirement from nbconvert==5.4.0 to nbconvert I am able to install the requirements even on regular Pip 21.2.4.

authors: agahkarakuzu ltetrel mathieuboudreau notatallshaw

repo: neurolibre/neurolibre


text:
Refactor Feature setup

feaures now all inherit from nm_features_abc.py
the loop for channels is put inside the respective calc_feature function -> this shuts of the possibility to run multiprocessing across channels, but unifies the feature pipeline (also for features e.g. coherence that are not estimated channel wise)
nm_settings.json are updated and segregated into preprocessing, features and postprocessing
it's now possibly to define the preprocessing order:

 "preprocessing": {
        "raw_resampling": true,
        "raw_normalization": true,
        "re_referencing": true,
        "notch_filter": true,
        "preprocessing_order": [
            "raw_resampling",
            "notch_filter",
            "re_referencing",
            "raw_normalization"
        ]
    },
    "features": {
        "raw_hjorth": true,
        "return_raw": true,
        "bandpass_filter": true,
        "stft": true,
        "fft": true,
        "sharpwave_analysis": true,
        "coherence": true,
        "fooof": true,
        "nolds": true
    },
    "postprocessing": {
        "feature_normalization": true,
        "project_cortex": true,
        "project_subcortex": true
    },

KalmanFiltering is supported only for oscilaltory features, and can be switched on in the fft, stft or bandpower settings

I think this setup makes it cleaner to add new features, and especially parametrization in the nm_features.py became thus more decoupled.

@richardkoehler just wanted to notify about those changes, but absolutely no pressure for reviewing it. The required changes were across many files.


text:
Upgrade gatsby deps

Description
Upgrades Gatsby deps to bring us up-to-date with all the latest goodies

Closing for now. There are too many issues

repo: newrelic/developer-website


text:
[Product-Partnerships] Added AWS Entity chatbot

Relevant information
This PR is to increase AWS Integrations under Project Northstar
Checklist

[X] I've read the guidelines and understand the acceptance criteria.
[X] The value of the attribute marked as identifier will be unique and valid.
[X] I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: newrelic/entity-definitions


text:
[I/O Site SSR] Cannot toggle light/dark mode after navigating to quickstart details page

Relates to #80, #81
Summary
This issue may be resolved once we get caching in place with SSR. Currently, when a user navigates to the quickstart details page, the toggle button for dark/light mode does nothing.
Steps to reproduce:

Navigate to SSR Feature site
Click on any quickstart (some may be broken. If it is, select a different quickstart)
Click on the toggle icon in the global header
Clicking the toggle should switch between dark/light mode, and it doesn't do anything.

Acceptance Criteria

[ ] Locate the issue that disables the toggle button on a quickstart's details page
[ ] Ensure that a user can toggle light/dark mode anywhere on the I/O Site

We decided to not launch the SSR feature at this time.
REASONS:

The performance issues we are seeing with category and page data and search results is too severe for a marketing site. Load times are anywhere from 1 - 5 seconds before caching  and spending time to optimize that doesn’t seem worth it at the moment
We are seeing large UI deviations in the internal and external catalogs UI  which is making this service less of a value add to the external site now
Due to our change in direction internally, our original goal of having parity isn’t valid anymore
As we learned from our GA releases: Our approach to the site has changed a lot in the past several months, to be strictly marketing focused and not something that needs to be a direct parity of the internal catalog, thus reducing the complexity.
This site is transitioning to a team focused on marketing website development, and SSR and an integration with the catalog service is extra complexity that offers little end user value, for just a marketing site

authors: josephgregoryii jpvajda

repo: newrelic/instant-observability-website


text:
Use a single gql query in ComponentDidMount

There are currently 3 queries in ComponentDidMount, and they could all be collapsed into a single GraphQL query to improve performance.

:tada: This issue has been resolved in version 0.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: cirne devfreddy


text:
Added proper millisecond time stamp calculation in nrTimestamp()

Probem
Current implementation of nrTimestamp() depends on external flow to update the milliseconds value which is bound to be wrong values for total time in milliseconds.
Solution
Use the Roku OS method GetMilliseconds() to get the current millisecond and append to the returned timestamp value.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: newrelic/video-agent-roku


text:
normalize.css as npm package

Added normalize.css as dependency.
It would be more great: require('normalize.css/normalize.css');

@Semigradsky yep, that should be added for sure.

authors: Semigradsky newtriks

repo: newtriks/generator-react-webpack

license: mit


text:
DNATするときにMASQUERADEしてるせいでクライアントのIPが消滅する

外からの通信をDNATするときはMASQUERADEしてはいけない
MASQUERADEせずにDNATする方法が分からん

一応マスカレードせずにSNATするようにしたけどパケットが永遠に返ってこない

DNAT要らないし廃止したい（暴論）

https://github.com/nexryai/lance-light/commit/55e7f113ae1a120894b5752ed88d5c899b997909#diff-8f11d2880d850c8fdc34735a665b83b8c88a1f390d6784cb4e7f776cf70c9377R247

repo: nexryai/lance-light


text:
WIP: Feature/add backup role

Adds backup role as discussed in https://github.com/nextcloud/ansible-collection-nextcloud-admin/discussions/228

Hello there!
I remember the discussion in #228  about the backup role.
Thank you @staticdev  for the initiative. As discusted, this will need probably more refinement before GA
also, on a pure Git perspective, it would be great to keep the commit history for the role.
Regards.

We may need to revert update to the CI with dependabot as latest broke our CI :
https://github.com/nextcloud/ansible-collection-nextcloud-admin/actions/runs/4767463169/jobs/8475717509?pr=260#step:7:68
or fix it for main

We may need to revert update to the CI with dependabot as latest broke our CI : https://github.com/nextcloud/ansible-collection-nextcloud-admin/actions/runs/4767463169/jobs/8475717509?pr=260#step:7:68 or fix it for main

About the errors we get, they are related to molecule 5. I created a new PR https://github.com/nextcloud/ansible-collection-nextcloud-admin/pull/261 improving test running that also fixes the error (I tested before on some other roles).

Hello there!
I remember the discussion in #228 about the backup role. Thank you @staticdev for the initiative. As discusted, this will need probably more refinement before GA also, on a pure Git perspective, it would be great to keep the commit history for the role.
Regards.

I feel we can add the role and do the improvements here as we go. As for the commit history, you can archive the other repo as history for investigation and we can point to a link in the docs so it is available in case of need. What do you think?

Hi! As this collection become official Nextcloud role I would opt for releasing backup into it when fully finished and tested. So now we could go one of 2 ways - first way: develop on @aalaesar's repo and then on some level move it or second way: move it here, but not to main branch, but to some "dev", "nc-backup-rc" or similar. Then test it here and release to GA when ready.
That's just my suggestions.
I've started using this role some time ago and backup works like charm :) I've tested only partial manual restore, so it also need to be covered in some way before release.
Btw, it's possible to "merge" one repo into another without loosing any history and commits, I've done it once in the past. I could try again tomorrow if we decide which approach we want to take :)

Hello there !
I'm very busy at the moment so I can't response quickly  to you. I thank you for keeping the repo active.

Then test it here and release to GA when ready. That's just my suggestions. I've started using this role some time ago and backup works like charm :)

Ok. What would be the list of features making the backup role worthy  of being released ?

I've tested only partial manual restore, so it also need to be covered in some way before release.
Yep potentially adding an install from backup option in Install nextcloud ? Or a new role ? Or inside the backup roles ?

Btw, it's possible to "merge" one repo into another without loosing any history and commits, I've done it once in the past. I could try again tomorrow if we decide which approach we want to take :)

Yes I would  prefer this approach.  😃
Regard.

Hi @aalaesar!

Ok. What would be the list of features making the backup role worthy of being released ?

For my opinion some testing and documentation or maybe even test task in Molecule would be sufficient for now. I'm also quite busy right now, so when I will find some time I will definitely add my two cents and contribute.

Yep potentially adding an install from backup option in Install nextcloud ? Or a new role ? Or inside the backup roles ?

I would opt for adding backup role next to nextcloud_install as separate role in collection. It would be probably easier to maintain and will give more flexibility.

Yes I would prefer this approach.

Ok, so I will try to make PR for that when have some time ;)

Hi @aalaesar @staticdev!
I've added whole role with commit history from: https://github.com/aalaesar/backup_nextcloud in #268
@staticdev please take a look if you can push your commits to this PR, so whole feature will be available to merge, when we decide it's ready ;)

Probably will be able to do throughout the week or latest next weekend.

Done @wiktor2200 @aalaesar, closing this one in favor to #268

authors: aalaesar staticdev wiktor2200


text:
Empty select values

Summary
Empty select values
Reproduction Steps

Add TextINput and Select to Modal

Minimal Reproducible Code
class Casino(nextcord.ui.Modal):
    def __init__(self):
        super().__init__(
            "Казино",
            timeout=5 * 60,
        )

        self.bet = nextcord.ui.TextInput(
            label="Ставка",
            min_length=2,
            max_length=50,
            required=True,
        )
        self.add_item(self.bet)

        option1 = nextcord.SelectOption(
            label="Красный",
            emoji="🟥",
            value="красный",
        )

        option2 = nextcord.SelectOption(
            label="Зеленый",
            emoji="🟩",
            value="зеленый",
        )

        option3 = nextcord.SelectOption(
            label="Черный",
            emoji="⬛",
            value="черный",

        )

        self.select = nextcord.ui.Select(
            options=[option1, option2, option3],
            min_values=1,
            max_values=1,
            placeholder="Выберите цвет, на который хотите поставить"
        )

        self.add_item(self.select)

    async def callback(self, interaction: nextcord.Interaction) -> None:
        await block_functions.validate_registration(interaction)

        print(self.select.options)
        print(self.select.values)
        color = self.select.values[0]
        coins_count = self.bet.value

Expected Results
values[0] = selected selectOption value
Actual Results
Empty array in select values
Intents
nextcord.Intents
System Information

Python v3.8.10-final
nextcord v2.0.0-alpha

nextcord pkg_resources: v2.0.0b3

aiohttp v3.8.1
system info: Linux 5.14.0-1038-oem #42-Ubuntu SMP Thu May 19 05:03:08 UTC 2022

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.

Additional Context
No response

Select menus in modals did not exist when these were implemented.
I can work on adding the support.

repo: nextcord/nextcord


text:
metatdata: Use --mesage-format instead of  --format

Closes https://github.com/nextest-rs/nextest/issues/846

Thank you so much!

repo: nextest-rs/nextest


text:
MAINT, ENH, TST: Butler.Memory

This request provides two items:

better connection for butler.memory
more complete interface to butler.memory
cleans the Memory API

The "better connection" means that it does not rely on constants.MINIONREDISHOST. For me that failed. Instead, uses StrictRedis(host='minionredis_1'), which is (as @dconathan mentioned) a somewhat old docker feature that we're not up to date on. @liamim did constants.MINIONREDISHOST work for you?
This also adds the functions increment, append, get_many, set_many and pipeline to Butler.Memory. It also refactors set and get to use ast.literal_eval to return the stored objects.
It cleans the API by using function wrappers to ensure the connection and catch exceptions. Before, all of these were coded in every function.
This implementation can be tested in the docker container with
$ sudo docker exec -i -t local_nextbackenddocker_1 /bin/bash
# logs into docker container
$ cd next/apps/tests
$ py.test test_memory.py

All tests pass.

The connection change seems independent from what this PR tries to implement, which is why I'm holding off.

repo: nextml/NEXT


text:
🛑 /getMusicFeed - Get music feed by URL or ID is down

In 6a360a6, /getMusicFeed - Get music feed by URL or ID (https://tiktok.nextpost.tech/getMusicFeed?query=7129970471625362182&cache_timeout=0&license_key=$API_KEY) was down:

HTTP code: 400
Response time: 7481 ms

Resolved: /getMusicFeed - Get music feed by URL or ID is back up in 4abc608 after 5 minutes.

repo: nextpost-tech/tiktok-status


text:
[Feature Request] Add destroyInactiveTabPanel prop for Tabs component

Is your feature request related to a problem? Please describe.
In some cases, I hope that when switching tabs, the previous TabPanel will not be destroyed in order to preserve their state and avoid re-rendering.
Describe the solution you'd like
We can add a destroyInactiveTabPanel prop with a default value of false.
The inactive TabPanel can be hidden using display: none.
If the user wants to destroy the previous TabPanel every time they switch tabs, they can simply add it to the Tabs component.
Describe alternatives you've considered
Now can also achieve the same effect by yourself, but each time you need to write additional code or encapsulate it again.
const [selectedKey, setSelectedKey] = useState<TabKey>('basic');
const [canRenderTabs, setCanRenderTabs] = useState([selectedKey]);

const setSelectedTab = (key: TabKey) => {
  if (!canRenderTabs.includes(key)) setCanRenderTabs([...canRenderTabs, key]);
  setSelectedKey(key);
};

{canRenderTabs.map((key) => {
  const Content = tabsMap[key];
  const isSelected = key === selectedKey;

  return (
    <div className={twMerge(styles.panel, !isSelected && 'hidden')} key={key}>
      <Content />
    </div>
  );
})}

Screenshots or Videos
No response

when creating a brand new project with nextui 2.4.0 the property "destroyInactiveTabPanel" is not recognized (yet) :-/
// package.json
...
"dependencies": {
		"@nextui-org/react": "^2.4.0",
...

@Softwaremanufaktur destroyInactiveTabPanel should be a prop for Tabs instead of Tab. The doc is incorrect. I'll update it.

Hi, I updated NextUI to 2.4.0 but the prop is not changing anything, my tab and the component within it keep being re rendered each time we switch tabs. Any idea why it could be the case?
I made sure to put the prop in Tabs as indicated above.
Thanks

@Neuro8 can u setup a minimal reproducible stackblitz project for us to investigate?

any update here? Setting destroyInactiveTabPanel to false does not prevent tab destruction.

@drewdearing the fix has been deployed to 2.4.2. Are you using the latest version?

@drewdearing the fix has been deployed to 2.4.2. Are you using the latest version?

Oh I didn't realize there was a fix based on this thread. I'll give it a try.

repo: nextui-org/nextui


text:
Broken Links to design files

https://nf-co.re/atacseq/1.2.1/assets/design_pe.csv
and
https://nf-co.re/atacseq/1.2.1/assets/design_se.csv
return a 404. They referenced at the end of this section:
https://nf-co.re/atacseq/1.2.1/usage#--input
https://nf-co.re/chipseq/1.2.1/assets/design_pe.csv
and
https://nf-co.re/chipseq/1.2.1/assets/design_se.csv
return a 404. They referenced at the end of this section:
referenced at the end of this section:
https://nf-co.re/chipseq/1.2.1/usage#--input

Probably it would be safest to use Fully Qualified URLs here @drpatelh - that should resolve these issues?

Sorry, I missed this. Yup I suspect it's because of the recent changes to the website. Which branch would we point to in the full URLs? With relative URLs that doesn't matter. Or am I missing something? Ping @ewels @mashehu

Relative has the benefit that it stays up2date no matter when there is a new release. If we remove links like this in an upcoming release (and thus subsequently from master) a previous link to master will be gone too - so maybe we should link to a specific tag instead? Not sure how to achieve this though...

We have a full link to the master branch for the igenome confs, as resolved here: https://github.com/nf-core/tools/pull/691/files. Since the docs on the website are available for different version, it might actually be good to reparse these kind of links and replace blob/master with blob/$version.

Yes, I think we should somehow point/redirect to the version of a file stored under a particular tag. Maybe replace both blob/master and blob/dev with blob/$version for any release tagged docs on the website? There will be instances where certain files are added to dev first and so may not be on master until release - at which point the pipeline author may forget to update dev -> master in the links.
I guess the problem with relative URLs is that the file can be deleted in a new release but the link from older releases will still point to master where it no longer exists.

Also, is this something we can lint for? I think it is something that can be easily missed and will only be updated on new release 🤔

you mean linting for relative urls or for occurences of /blob/dev?

I think that it would be better to just make the relative URLs work. I'm going to have a quick play.

Ok, try #517 - should basically make these links work properly again.

I can confirm the changes introduced in #517 have now fixed this issue 🚀

authors: alaincoletta apeltzer drpatelh ewels mashehu


text:
Feat/implement-ci-nf-tests

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs- [ ] If necessary, also make a PR on the nf-core/rnaseq branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

I notice that all the pre-fetching of the test data has been removed.
:crying_cat_face:
I would very like that to stay.
We had many issue with Nextflow/GHA interaction when getting these files, and that was a very efficient way to solve this issue.
We (Edmund, Phil and I) started doing that in other pipelines as well (methylseq first, sarek obviously).

Will be completed in https://github.com/nf-core/rnaseq/milestone/20

authors: drpatelh maxulysse sateeshperi

repo: nf-core/rnaseq


text:
The Docker build are failing

Hi,
I have started looking into this repository and tried to build the dev and prod without success.
This  Dev step generated the following error:
[~/projects/mlstr/metadata-annotation-workbench] main
>docker compose --env-file dev.env up prediction
[+] Running 0/1
 ⠿ prediction Error                                                                                1.4s
Error response from daemon: Get "https://gitlab.zbmed.de:5050/v2/": dial tcp 134.95.56.228:5050: connect: connection refused

And when I tried the Prod steps to build and load the containers had this error:
[~/projects/mlstr/metadata-annotation-workbench] main
>docker compose --env-file dev.env build
[+] Building 1.1s (15/20)
 => [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/backend:dev internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 347B                                                                                0.0s
 => [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 374B                                                                                0.0s
 => [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev internal] load metadata for docker.io/library/nginx:alpine                                                                         0.5s
 => [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/backend:dev internal] load metadata for docker.io/library/python:3.8                                                                            0.5s
 => [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev internal] load .dockerignore                                                                                0.1s
 => => transferring context: 3.88kB                                                                                0.0s
 => [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/backend:dev internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev internal] load build context                                                                                0.1s
 => => transferring context: 2.39kB                                                                                0.0s
 => CANCELED [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev 1/6] FROM docker.io/library/nginx:alpine@sha256:a5127daff3d6f4606be3100a252419bfa84fd6ee5cd74d0feaca1a5068f97dcf          0.2s
 => => resolve docker.io/library/nginx:alpine@sha256:a5127daff3d6f4606be3100a252419bfa84fd6ee5cd74d0feaca1a5068f97dcf                                                                                0.1s
 => => sha256:a5127daff3d6f4606be3100a252419bfa84fd6ee5cd74d0feaca1a5068f97dcf 9.07kB / 9.07kB                                                                                0.0s
 => => sha256:074604130336e3c431b7c6b5b551b5a6ae5b67db13b3d223c6db638f85c7ff56 2.50kB / 2.50kB                                                                                0.0s
 => => sha256:c7b4f26a7d93f4f1f276c51adb03ef0df54a82de89f254a9aec5c18bf0e45ee9 11.21kB / 11.21kB                                                                                0.0s
 => CANCELED [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/backend:dev 1/6] FROM docker.io/library/python:3.8@sha256:ecd06b59ae52c021ae58b8fea0957bf5b0f4568783cb0240b56e06ed1720cc19             0.4s
 => => resolve docker.io/library/python:3.8@sha256:ecd06b59ae52c021ae58b8fea0957bf5b0f4568783cb0240b56e06ed1720cc19                                                                                0.2s
 => => sha256:ad4a9aed1d241d025af20a3abb37c4adc6084a13ea1c33391ab55a737b578faa 2.52kB / 2.52kB                                                                                0.0s
 => => sha256:f5c5013453fab04241dca0dc61a4629a2cfe731e7411e6b5f81af77d70798c3d 7.32kB / 7.32kB                                                                                0.0s
 => => sha256:ecd06b59ae52c021ae58b8fea0957bf5b0f4568783cb0240b56e06ed1720cc19 10.35kB / 10.35kB                                                                                0.0s
 => => sha256:8cd46d290033f265db57fd808ac81c444ec5a5b3f189c3d6d85043b647336913 0B / 49.56MB                                                                                0.1s
 => [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/backend:dev internal] load build context                                                                                0.1s
 => => transferring context: 481.25kB                                                                                0.0s
 => CACHED [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev 2/6] COPY nginx.conf /etc/nginx/templates/default.conf.template                                                             0.0s
 => CACHED [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev 3/6] COPY nginx-server.conf /etc/nginx/nginx.conf                                                                           0.0s
 => CACHED [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev 4/6] COPY setVariables.sh /docker-entrypoint.d/50-insert-runtime-variables.sh                                               0.0s
 => CACHED [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev 5/6] RUN chmod +x /docker-entrypoint.d/50-insert-runtime-variables.sh                                                       0.0s
 => ERROR [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev 6/6] COPY build /usr/share/nginx/html                                                                                0.0s
------
 > [gitlab.zbmed.de:5050/km/nfdi4health/annotation-workbench/frontend:dev 6/6] COPY build /usr/share/nginx/html:
------
failed to solve: failed to compute cache key: failed to calculate checksum of ref LRU2:AC73:O6ET:327Y:2BOT:WPUG:WB6N:2IN3:IKBI:JXD6:XMHE:WGG3::qvacx99mpnh2j2xdvg00i5hvv: "/build": not found
[~/projects/mlstr/metadata-annotation-workbench] main

Here are more info:

Python 3.9.2
Docker version 27.2.1, build 9e34c9b
NPM: v18.17.1 (lts/hydrogen)

Thanks for the great effort building this, I would love to learn more about and try it locally.
Any help is greatly appreciated.

Thanks for reporting. The projects moved and I updated the image paths accordingly. This should fix the issue with the dev setup.
Before doing the Docker build, a local build step is needed. I updated the README. This should fix the production setup.

Hi,
I still have access issue for creating the container:
>docker compose --env-file dev.env up prediction
[+] Running 0/1
 ⠿ prediction Error                                                                                0.5s
Error response from daemon: Head "https://ghcr.io/v2/nfdi4health/workbench-ai-
model/backend/manifests/e57e38ff84b682be298d936ab7338f0fb9502825": denied: denied

Are there also any tutrial or documentation on how to use the tool to get the a beginner start?
Best,

You can find a tutorial/documentation at https://mda.nfdi4health.de/tutorial. It's not quite up to date, but it's a good place to start.


text:
Fix typo

Removes extra semicolon in for loop example

You absolute madman.

Is there such a thing as a commit of the year award? Because I think I'd win it with this epic contribution.

authors: alexpls nfour

repo: nfour/node-structures


text:
c/C command variable indexes flipped

The curve command has the first control point in x2/y2 instead of x1/y1 and vice-versa. The expected naming is the same as the SVG standard ( https://www.w3.org/TR/SVG/paths.html#PathDataCubicBezierCommands ). It's not even consistent with the smooth curve command where the second control point is (correctly) in x2/y2.

Probably due to the way it is parsed and the fact the definition set x and y at the end of the C commands.
https://github.com/nfroidure/SVGPathData/blob/master/src/SVGPathDataParser.js#L233-L248
I have nothing against changing this to fit the standard naming and would merge a PR doing so. It would require a major version bump though.

Fixed by commit https://github.com/nfroidure/SVGPathData/commit/0ea315275a25006eceb18423c7ceb756f92cc793 .

authors: NaridaL nfroidure

repo: nfroidure/SVGPathData


text:
Alert: self-close on timeout

It will be trivial to implement as soon as we've got #206

This one is not blocked any more. The implementation should be easy and should consist of adding a new input (dismissOnTimeou) to the NgbDismissibleAlert directive. When specified it should call the close() method on the alert. Make sure that timeout is cleaned up correctly, especially when a component is destroyed.
Test are mandatory and should use fake async (check carousel tests fr an example of using fake async).

This just fixed in 57dd814bdd2c197ed7076761d8f8ea9a769b4de5. We just need to add demo for this new feature.

repo: ng-bootstrap/core


text:
MapFeatureTiles is missing ?

Hi guys, I was trying the example you put on the home page, and after importing all the packages I have only one class that cannot be resolved: "MapFeatureTiles". I saw that there is a FeatureTiles abstract class and has an implementation in a class called "DefaultFeatureTiles". Is it ok to use that one or I'm missing some packages/dependencies ?
I'm using this lib version:
implementation "mil.nga.geopackage.map:geopackage-android-map:3.0.2"
Thanks.

You are correct, DefaultFeatureTiles replaced MapFeatureTiles (in geopackage-android 1.3.1) and the geopackage-android-map README example did not get updated.  Fixed now, thanks for finding.

authors: bosborn leonard-abusaa

repo: ngageoint/geopackage-android-map


text:
Allow link-active to react to linkTo input changes

Proposal to fix #119

No tests are broken. Didn't add tests for feature yet as am waiting to know if implementation is acceptable.

A test has been added but it fails - as discussed in Gitter, I'd appreciate some help on why it fails.

@brandonroberts the changes have been implemented, but the test is still not done correctly, and I would appreciate some help.
Previously it failed because the @Query subscriptions fired after the expectations ran. This was solved with fakeAsync, but now the issue is the Router is read directly (and not through the Observable), so doing router.next() doesn't work..

Using router.go() updates LocationStrategy, which makes the tests behave properly. Any reason for the spec to use router.next() that I might not be aware of?

LGTM. Will you rebase on top of master?

I believe I did, can you check?

Merged. Thanks for your work and patience!

Is this implemented in 1.0.0-beta.1?

No. It will be released with the next beta.
On Jun 19, 2016 4:33 AM, "David Beljan" notifications@github.com wrote:

Is this implemented in 1.0.0-beta.1?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ngrx/router/pull/120#issuecomment-226985997, or mute
the thread
https://github.com/notifications/unsubscribe/AACk47C1sBZNtmJTrNMd1aCnnjWXLqHQks5qNP7wgaJpZM4IrfVq
.

authors: beljand brandonroberts tiagoroldao

repo: ngrx/router


text:
CORS

Støtte konfigurerbare CORS headere slik at tjenesten kan brukes fra et kontrolert sett andre websider. Nå settes CORS til *, men denne saken går på å gjøre dette konfigurerbart.

@bgrotan hvordan tenker du at denne bør konfigureres? I den properties-fila eller i databasen? Og så en verdi som er det vi bruker som CORS header verdi? I tillegg må vi vel støtte OPTIONS request for de POST-requestene for sånn CORS preflight greier.
Står endel om dette på https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS

Om CORS bare skal gjelde for GET er det mye enklere, men vi trenger jo POST for ordrekjøring. Vil POSTene gå via Kartverket sine servere eller rett fra nettleseren? Trenger vi CORS til POST også?

https://kartkatalog.test.geonorge.no/search kobler rett til test.geonorge.ecc.no uten noe serverside proxy. Klientene kjører første en OPTIONS https://test.geonorge.ecc.no/api/v2/order for å hente CORS headere og så en POST til samme URL med bestillingen.

Skal vi gjøre noe med denne, @bgrotan eller bare beholde det som det er nå?

La oss gjøre cors default * (men bør dokumenteres!), men kan overstyres fra konfigurasjonsfil.

CORS defaulter nå til *, men kan konfigureres med 'cors'-parameter. Har lagt inn konfigurasjonseksempler i README.md.

Fikset i commit 1a08fe251d4b67f80b0ae995fc7ddf2fef4c4ed2

authors: bgrotan halset

repo: ngu/geonorge-nedlastingapi


text:
Migrate the Lumberjack schematics e2e test to the Nx Monorepo now using Cypress

Use end-to-end tests as generated by Nx similar to what we have been doing in branches in the nxworker monorepo.

Descoped for Lumberjack v14.0.

repo: ngworker/lumberjack-next


text:
MissingTranslationHandler inside Translate Service

Current behavior
At the moment we use code for missing translation in the module initialization.
Expected behavior
Would be allot better to have it inside the service, in this way we could manage it better, with other code for translation handling.
What is the motivation / use case for changing the behavior?
More like the flexibility it provides.
How do you think that we should implement this?
Would be best to have it on both places, just service to have option to have atleast an callback with word that is missing.

@ocombe can you check this?

repo: ngx-translate/core


text:
Create module to release a kt1.1 artifact

This should generate another artifact that includes the 1.1.x version of Kotlin, and fix issues like #156, #162 and #163.

@nhaarman Why not just avoiding to expose kotlin-stdlib and kotlin-reflect dependencies in the Maven dependencies by using a scope like compileOnly and compileTestOnly,
That would avoid creating specific artifact for Kotlin 1.1, 1.2, 1.3 ...

While the stdlib will probably always be included by the client, reflect might not.

I agree and I don't say the approach I propose is perfect but I think this is the one adapted by very well known project like Jackson Kotlin and I am really not a fan of seeing a project that propose mockito-kotlin-kt1.1, mockito-kotlin-kt1.2 and mockito-kotlin-kt1.3 artifact in less than a year.
I will ask on Kotlin Slack if somebody has a better solution to this issue.

I have created https://youtrack.jetbrains.com/issue/KT-18398 to try to find a better outcome than Kotlin version specific artifacts.

authors: nhaarman sdeleuze

repo: nhaarman/mockito-kotlin


text:
extract text from ogg audio file (Text extractor tool)

OGG format is supported by openai whisper but when I try to extract text from the audio file with the textgenerator plug-in, the OGG files are missing.
Why do we need ogg format (can bring more ideas...):
OpenAI Whisper is limited to processing audio files up to 25 MB, and although it supports many formats including OGG, Obsidian can only record audio in one file format, WebM, which isn't optimized enough. For instance, an hour of audio amounts to about 40 MB in the WebM format. However, if we compress it into an OGG format, using a command like "ffmpeg -i audio.webm -vn -map_metadata -1 -ac 1 -c:a libopus -b:a 12k -application voip audio.ogg" , the file size significantly reduces, going down to about 10% of its original size in my case.

this should be added in version 0.5.28-beta

repo: nhaouari/obsidian-textgenerator-plugin


text:
Mac default keybinding issue

Along the same lines of #23 Text Generator: Template Packages Manager uses alt + 3 by default. This is how you type a # on a mac obviously this is used a lot when writing markdown.

I had to uninstall the plugin because of this. Please remove!

Along the same lines of #23 Text Generator: Template Packages Manager uses alt + 3 by default. This is how you type a # on a mac obviously this is used a lot when writing markdown.

Thank you for bringing this to my attention!
Do you have any suggestions for alternative hotkeys that we could use?

authors: MatthewAlner jasecoop nhaouari


text:
Investigate performance hit from the ability to assign element within the definition.

Please describe your feature request.
There is a performance hit (especially with long text) due to the required translation taking place whenever an element is moved (dragged). Element field access and assignments via $[] and &[] were introduced but required some changes to optimizations.
Describe the solution you'd like
Investigate alternative ways to provide the same functionality but keep dragging optimized by using the definition cache for a given element.

Added toggle to turn off translations for strings when elements are moved. Most normal use cases won't need this on.
Up next will be to evaluate the regex logic (I'm no expert so they are probably trrrrrrrible)

repo: nhmkdev/cardmaker


text:
summary tag being removed

Describe the bug
I have customized rendering of markdown using customHTMLRenderer.
customHTMLRenderer.htmlBlock = {
    details(node){
        return [
                { type: 'html', content: node.childrenHTML }
            ];
    }
}

MD

  Epcot Center

Epcot is a theme park at Walt Disney World Resort featuring exciting attractions, international pavilions, award-winning fireworks and seasonal special events.

Output HTML

Epcot is a theme park at Walt Disney World Resort featuring exciting attractions, international pavilions, award-winning fireworks and seasonal special events.

summary tag is being removed

@ats1999
Our incremental mark-down parsing now does not support this grammar properly. I think this feature should be developed by adding it as a separate plug-in later on. It's a little bit of a future story, but I want you to wait.

I'm waiting!


text:
bold? becomes bold?

Describe the bug
While in WYSIWYG edit type and changing text to bold followed by question-mark will make it change to strong-tag instead.
These changes will also follow if you switch from WYSIWYG to Markdown.
Using: @toast-ui/editor 3.2.1
To Reproduce
Steps to reproduce the behavior:
**Test-text**?  becomes Test-text?
**Test-text** ? becomes **Test-text** ?
**Test-text?** becomes **Test-text?**
Expected behavior
**Test-text**?  becomes **Test-text**?
Screenshots

Desktop (please complete the following information):

OS: [osx]
Browser [chrome]
Version [Version 106.0.5249.119 (Official Build) (arm64)]

It seems to have something to do with one of the tasks we did.
I'll check it out later.

I have the same behavior with the last version of vue-editor.

This feature makes many problem. Due to the structure of the current editor, it is difficult to deal with it. so we'll rollback commit over this issue soon. @jajugoguma takes this issue.

That’s cool @freegroup! This does not consider markdown code blocks and inline code, right?

We forgot to create a release, see related issues (v3.2.2)

It was actually deployed to npm last week. we missed writing the release notes.

3.2.2 seems to fix this. At least in my case.

authors: MoritzGiessmann cgiuliani jwlee1108 thojoh


text:
Copy a html document to TUI save to server, after edit contents issue

Summary
I tried several times to write and edit the content on TUI there were issues with the code block
it didn't map to a code tag correctly so I got this issue on my next.js project
Screenshots
If applicable, add screenshots to help explain your question.

Version
"@toast-ui/react-editor": "^3.2.2",
Additional context
Add any other context about the problem here.

Can you tell me what form of HTML you copied?

@jwlee1108  I tried to copy HTML contents like blog articles to toast UI editor, I found the problem was when I tried to copy the contents which included code block or inline code things caused error


text:
fix: Select events by using mobile(#26)

#26

모바일일 경우 touchend 이벤트만 사용. 아닐 경우 click 이벤트 사용

ok to test


text:
add ability to specify custom scripts, and ignore either the layout css or theme css

I needed the ability to specify custom scripts to include in each layout

Thanks!
I'll see asap :)
sorry for the delay

awesome - i know i could have simply add css with more specificity, however, simply disabling the aesthetic specific css while keeping the structural css intact is far easier for a consumer, albeit more work for maintainers

authors: minkyu-yi noahehall


text:
Why remove origin: ENV.AUTH_SERVER_URL  from utils.ts??? Oauth can't work

Same as

#452

I still don't know how to solve this problem.
024258c do some wrong thing, it remove ENV.AUTH_SERVER_URL
If I set AUTH_API_PREFIX="/v1/auth",  oauth set redirect_uri is right, but the other auth url changed from example https://api.entube.app/v1/auth/v1/auth/signin/provider/github/, it need two '/v1/auth' to access.
If not set, oauth redirect_uri miss /v1/auth, code can't pass

Could you provide steps to reproduce so we can help? I.e. a sample docker compose file triggering the issue you are reporting. Thanks!

I forked the source and made modifications to the commit https://github.com/bigzhu/hasura-auth/commit/2b0bd0795ac8b781929d239d6ec340522fbf8c96. Now, using my self-built image, everything works fine.
The Docker Compose file does not have any special specific configurations.
Use Cloudflare to provide HTTPS.
Use Nginx to proxy  pass.

authors: bigzhu dbarrosop

repo: nhost/hasura-auth


text:
extend OAuth to other providers

Grant proxies 200+ Oauth providers. I should not require lots of efforts to plug it into Hasura-auth.

shipped in 0.16


text:
🛑 Core is down

In 860c17e, Core ($CORE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Core is back up in 0e7f741 after 27 minutes.

repo: nhs-work/test-upptime


text:
Filters sometimes return blank results

Filters sometimes return blank results. Relevant to private and community edition. This is due to fact that more customization and configuration was done for some vendors and open source projects compared to others in prototyping stage.
Search Quality is primary focus over pure code tasks for CW46. Filter templates are also going to be extended to factor in some of my own requirements in the personal edition.

This is been worked on all this week with new vendors and open source projects. Closing as it's a core part of the development task for the coming 6 weeks.

repo: niallguerin/vendelligence