text:
Google Drive - uploaded docx files appears as archives

Hi, i have synct a lot of office files with this very useful tool. All the docx files appears as archive/zip file. I thik it is related with setting the mime type.
I have found an similar problem with another sync tool.( https://github.com/odeke-em/drive/issues/154 )
I am using rclone v1.28 - 2016-03-01 on a Windows Server 2012R2
Thank you.

rclone uses the TypeByExtension function to turn an extension into a mime type.
If I try this on my linux machine it works perfectly, setting the correct mime type "mimeType":"application/vnd.openxmlformats-officedocument.wordprocessingml.document"
On windows this uses the registry to work out the mime type.
Does the server that you uploaded the docs from have Word installed on it? I suspect it doesn't know the mime type for docx documents.  Maybe if you installed the free Word viewer that would help?

Yes, you are right. I do not have MS Office installed on that server and i will never have it...expensive shit :-)))
Now, what can i do?
Thank you for your quick reply.

Still no go...
I have installed Libre Office 5.1.1 and have made all the file associations. In the registry they look ok.
What is strange is that some of the uploaded files do have the correct type associated for both .docx and .xlsx. All the doc or xls file are ok. Maybe the query for the file type from registry some time fails?
Thx.

I have a lot of duplicated files....runing dedupe now.

I have figured out what is going on I think - it is when a .docx file gets updated that the mime type gets corrupted.
To verify

upload test.docx
edit test.docx
upload it again - at this point it will change to a zip

Here is a beta with a fix.  It won't fix any files you've uploaded already unfortunately but it should fix the problem in the future.
http://pub.rclone.org/v1.28-23-g6cc9c09β/

Feel free to re-open if this doesn't fix your problem!
Thanks
Nick

Thanks, i will test the beta tomorrow.
The problem is that i have erased everything forom GDrived because of duplicate files problem and uploaded a fresh copy of files using rclone sync. The mime type was unknown for all the docx files. Maybe it is something on my side...but i don't know what.
I will post tomorrow the test result. Thanks again.

I have tested it and the same result ...file type unknown.
I have uploaded a docx file with Google Drive web page from latest Firefox...same result...file type unknown. If i upload the same file from another computer all is ok.
So there is something wrong on my side...if you have any idea how i can address this fell free to tell me. I am pulling my hair out already :-)

Did you try installing the word viewer to see if that gets the mime type correct?
https://support.microsoft.com/en-us/kb/891090
Also there is a small program you can try here which will print the mimetype the same way rclone does it.  Pass it a docx file and see what it prints.
> mimetype.exe z.docx
".docx" is "application/vnd.openxmlformats-officedocument.wordprocessingml.document"

That is what it should print!

Hi
You need to install word / excel and power point viewer.
That solves your issue
Regards

Hi this is my output for mimeype.exe
".docx" is "application/vnd.openxmlformats-officedocument.wordprocessingml" so...missing .document, but in another app like "FileTypesMan" it lists the entry s above but , "percived as document."
That word viewer is for old formats ,doc, not docx.
I am stuck.

Thanks for trying that binary.  Odd result!
You need to install a viewer which can view .docx files I think.
According to https://support.microsoft.com/en-us/kb/891090 you need the word viewer and the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 and later versions' file formats which you can get from here: http://www.microsoft.com/downloads/details.aspx?familyid=941B3470-3AE9-4AEE-8F43-C6BB74CD1466&displaylang=en

Thank you, i can confirm that installing wordviewer and compatibility pack as described by ncw solves my issue. Now, all the files uploads with the correct type. Thank you all for this.
Regards.
Marius.

Great!  I think what I'll do is put this in the FAQ so if anyone has this problem in the future they will know what to do.

authors: dav1303 mdalacu ncw


text:
Installation fails on yosemite

I've been using scm_breeze without issues on OSX Mavericks for many months now. After doing a fresh install of Yosemite, trying to install failed since there was no .bashrc or .bash_profile. In such cases, I would be nice to auto create the file or alert the user. Copying the .bash_profile from Time Machine worked.

It dosen't work even if you have a .bash_profile. I had to create the .bashrc file and add the following line to load the scum breeze scripts:
[ -s "$HOME/.scm_breeze/scm_breeze.sh" ] && . "$HOME/.scm_breeze/scm_breeze.sh"

I came here to report this too.

Same, as per @mitramejia

source: gharchive/issue

authors: adzenith khronnuz mitramejia rgormley

license: mit

license_type: permissive

license_source: bigquery


text:
gpsd: add versioned patch support

PDS patches for GPSd 3.23 and (pending) 3.24 are not compatible. Add two
versions of the patch so that it is possible to test both GPSd versions.
Signed-off-by: Dmitry Baryshkov dmitry.baryshkov@linaro.org

please merge this change as corresponding meta-oe change is in master now.

source: gharchive/pull-request

authors: kraj lumag

repo: ndechesne/meta-qcom


text:
pkg_fauxpi on unofficial repo

Hi, Do you mind if I publish this package under my unofficial pfSense repo?
https://github.com/marcelloc/Unofficial-pfSense-packages

By all means, go for it - thanks for checking in

authors: marcelloc ndejong


text:
Module imports forming a cycle is not detected

I think because this error message isn't associated with a place, so is parsed incorrectly.

Easy example - have a module import itself. Easy example is:
Module imports form a cycle:
   module `General.Timing' (src\General\Timing.hs) imports itself

Fixed, plus a test. Required a fair bit of refactoring in Messages.

repo: ndmitchell/ghcid


text:
WIP: Add tokio async support

This PR will add support for tokio by adding two traits AsyncBorshDeserialize and AsyncBorshSerialize and their respective derive macros to be used in places that we have async reader and writer.
Feature gate = "tokio"
Here is works that needs to be done:

[ ] Update documentation to address new trait and it's usage.
[ ] Fix tests and write them for async pair of traits.
[ ] Organize and rename new trait and modules to be more generic over async runtimes. (e.g. we may want to support async-std too)
[ ] Disable feature gate as a default and make it optional

Anyway, here is the driver code for current working version:
use borsh::tokio::{AsyncBorshDeserialize, AsyncBorshSerialize};
use borsh_derive::{AsyncBorshDeserialize, AsyncBorshSerialize};

#[derive(AsyncBorshDeserialize, AsyncBorshSerialize, PartialEq, Debug)]
struct Custom {
    a: u8,
    b: Vec<String>,
}

#[tokio::main]
async fn main() -> std::io::Result<()> {
    let value = Custom {
        a: 12,
        b: vec!["Hello".to_string(), "From Tokio".to_string()],
    };

    let serialized = value.try_to_vec().await?;

    let expected = Custom::try_from_slice(&serialized).await?;

    assert_eq!(value, expected);

    Ok(())
}

Cargo.toml:
[dependencies]
async-trait = "0.1.68"
borsh = { path = "../../borsh-rs/borsh" }
borsh-derive = { path = "../../borsh-rs/borsh-derive" }
tokio = { version = "1.28", features = ["macros", "rt", "rt-multi-thread"] }

Thank you, yeah exactly, this is what i'm afraid of.

It is going to be really hard to maintain and I fear that it will inevitably drift away, so I would keep it in PR for now to see if anyone will be able to come up with a better plan or maybe Rust async? syntax will mature.

It is going to be really hard to maintain and I fear that it will inevitably drift away, so I would keep it in PR for now to see if anyone will be able to come up with a better plan or maybe Rust async? syntax will mature.

Good idea,
I don't like the current plan tbh.

authors: frol hamidrezakp

repo: near/borsh-rs

license_source: github-api


text:
Wallet Selection page

There are already more than one wallet and the number will be growing that support signing NEAR transactions.
We ideally want to offer users an option when they click "Log in" or trying to sign a transaction.
There is more work on how to add this option on the App side, via some form of wallet selection there.
But for any wallet that supports linking (or later QR codes), we can also offer selection process on the NEAR Wallet side.
E.g. when user presses login, sign transaction or receives a link drop they are presented with the choice which wallet to use.
This can be similar to such page on an invite link site https://matrix.to:

There are questions around how to ensure that listed wallets are secure.
Wallet should also remember if user already selected one and redirect them to it.
It's important that this page is well CDNed so it's quick to load (e.g. way faster than current wallet loading in China), so ideally a static page would be the best.

The wallet selection is definitely a quick win when the number of wallets growth. The wallet selector is commonly used in Ethereum DApps.

@marco-sundsk 's initiative https://github.com/marco-sundsk/near-wallet-selector could help.
The wallet selection solution might also serve as a workaround to the wallet page loading issue in China by providing a CN wallet page as a choice, though I would strongly prefer resolve that issue by enhancing the CDN as suggested here: https://github.com/near/near-wallet/issues/1101

To be as shine as the kickback UI pasted by @think-in-universe , there is still a long way to go. For kickback, it is the dapps responsibility to recognize those wallets. That is to say, kickback as a dapp, it knows how to interact with those different wallets, using different interfaces supported by each wallet. That also means the Select page in kickback is an intrusive one, dapp knows every wallets in its selection, even the whole selection page is an inner part of the dapp.
While our first version of selector page, aims to be a non-intrusive one. That is to say, neither wallets nor dapps need to know each other or aware of the existing of this selector.  This non-intrusive feather comes with a price. That is, dapps and wallets must communicate with each other through a standard interface. For now, it is the interface implied by official web wallet. That means the diversity of wallets supported by this selector is limited, we can not have chrome plugins nor mobile wallets in this version of selector page.
But, no matter what, a selector page is definitely a good start, and all its drawbacks can be resolved by upgrading time by time. For example, with the work of near-wallet-SDK, it may become a new standard that can enable plugins and mobile wallets to be included in the selection page in a near future.

From my point of view, the selector page has three job to do:
First, it should get wallets info from a secure place. For this version, we use on-chain contract as the source of information. And the management of this contract can be restrict to special org, like the Fundation or other intuition. And there may have a whole apply-verify action process behind.
Second, there would be a clear communication interface of accessing wallets, that enables the selector page to relay all requests from wallet users. For this version, we would take the web wallet interface as our standard.
Last, the selector itself must be accessible worldwide and as quick as possible. it can be done with a pure frontend, and more than that, this frontend has a very small index page which put all big static files (images and js) on several CDNs. The index page can automatically inspect the speed to each CDN, and always using the fastest CDN as user open it. Besides all those skills, we may also use different nodes to access on-chain contract due to the user's location, if we can get that kind of information.

There are questions around how to ensure that listed wallets are secure.
Wallet should also remember if user already selected one and redirect them to it.
It's important that this page is well CDNed so it's quick to load (e.g. way faster than current wallet loading in China), so ideally a static page would be the best.

@kcole16 if you are good, this may fall within the SDK workgroup, and have the wallet as a "consumer" of the API.
Feel free to close and link any content if you agree

Closing this as this was created here: https://github.com/near/wallet-selector

authors: agileurbanite ilblackdragon jimmy3dita marco-sundsk think-in-universe

repo: near/near-wallet

license: MIT


text:
Dashboard: Add new desktop layout

Desktop changes:

Split dashboard page into two columns to better handle a long list of fungible tokens while also showing recent transactions in the same view (without having to scroll)

If I had a magic wand, I would switch the "recent activity" and the "tokens" on the page -> recent activity under the total balance, and tokens on the right, under the (collapsible) "explore apps" banner.
I'm worried that most users will squint to find what happened to their account, while almost ignoring the balance of the tokens that won't change.

If I had a magic wand, I would switch the "recent activity" and the "tokens" on the page -> recent activity under the total balance, and tokens on the right, under the (collapsible) "explore apps" banner.
I'm worried that most users will squint to find what happened to their account, while almost ignoring the balance of the tokens that won't change.

@jimmy3dita In thinking ahead, I'd like the main column of this layout to be primarily concerned with assets and asset management. The recent activity pane on this dashboard will again only be for the most recent items. With a dedicated activity feed that includes more than just a few txns and that has a dedicated route, it won't be necessary to give the smaller list of recent txns so much real estate on the dashboard.
If it helps to envision how this might evolve in the future, here's some exploration/anticipatory design I've been doing on the side to try and help ensure the decisions made now are acting as steps towards enabling future iterations:

Love this design direction!


text:
Fix updating state in the running kernels table

Reference Issues or PRs
Fixes #68
What does this implement/fix?
Put a x in the boxes that apply

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[x] Did you test the pull request locally?
[ ] Did you add new tests?

bot please update snapshots

repo: nebari-dev/jupyterlab-launchpad


text:
[ENH] - Add option for output path to nebari init

Feature description
nebari deploy and nebari destroy have the -o / --output flags to work in another directory than the current. nebari init is missing this option.
Value and/or benefit
Consistency with nebari deploy and nebari destroy
Anything else?
No response

I am working on this issue.

Closed as part of https://github.com/nebari-dev/nebari/pull/1833

authors: babueverest dcmcand pmeier

repo: nebari-dev/nebari


text:
[BUG] -TypeError: Object of type KeyValueDict is not JSON serializable

Describe the bug
Attempting to do a nebari deploy on an existing k3s cluster. I had a separate issue with the Traefik CRDs that I will raise separately. But once I get past that, I see this:
[terraform]: After stage=03-kubernetes-initialize kubernetes initialized successfully
╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/subcommands/deploy.py:92 │
│ in deploy                                                                                │
│                                                                                │
│   89 │   │   │   msg = "Digital Ocean support is currently being deprecated and will be remov    │
│   90 │   │   │   typer.confirm(msg)                                                              │
│   91 │   │                                                                                │
│ ❱ 92 │   │   deploy_configuration(                                                               │
│   93 │   │   │   config,                                                                         │
│   94 │   │   │   stages,                                                                         │
│   95 │   │   │   disable_prompt=disable_prompt,                                                  │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/deploy.py:53 in          │
│ deploy_configuration                                                                             │
│                                                                                │
│   50 │   │   with contextlib.ExitStack() as stack:                                               │
│   51 │   │   │   for stage in stages:                                                            │
│   52 │   │   │   │   s = stage(output_directory=pathlib.Path.cwd(), config=config)               │
│ ❱ 53 │   │   │   │   stack.enter_context(s.deploy(stage_outputs, disable_prompt))                │
│   54 │   │   │   │                                                                               │
│   55 │   │   │   │   if not disable_checks:                                                      │
│   56 │   │   │   │   │   s.check(stage_outputs, disable_prompt)                                  │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/contextlib.py:526 in enter_context             │
│                                                                                │
│   523 │   │   except AttributeError:                                                             │
│   524 │   │   │   raise TypeError(f"'{cls.__module__}.{cls.__qualname__}' object does "          │
│   525 │   │   │   │   │   │   │   f"not support the context manager protocol") from None         │
│ ❱ 526 │   │   result = _enter(cm)                                                                │
│   527 │   │   self._push_cm_exit(cm, _exit)                                                      │
│   528 │   │   return result                                                                      │
│   529                                                                                │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/contextlib.py:137 in __enter__                 │
│                                                                                │
│   134 │   │   # they are only needed for recreation, which is not possible anymore               │
│   135 │   │   del self.args, self.kwds, self.func                                                │
│   136 │   │   try:                                                                               │
│ ❱ 137 │   │   │   return next(self.gen)                                                          │
│   138 │   │   except StopIteration:                                                              │
│   139 │   │   │   raise RuntimeError("generator didn't yield") from None                         │
│   140                                                                                │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/stages/base.py:72 in     │
│ deploy                                                                                │
│                                                                                │
│    69 │   │   │   deploy_config["terraform_import"] = True                                       │
│    70 │   │   │   deploy_config["state_imports"] = state_imports                                 │
│    71 │   │                                                                                │
│ ❱  72 │   │   self.set_outputs(stage_outputs, terraform.deploy(**deploy_config))                 │
│    73 │   │   self.post_deploy(stage_outputs, disable_prompt)                                    │
│    74 │   │   yield                                                                              │
│    75                                                                                │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/provider/terraform.py:59 │
│ in deploy                                                                                │
│                                                                                │
│    56 │   │   mode="w", encoding="utf-8", suffix=".tfvars.json"                                  │
│    57 │   ) as f:                                                                                │
│    58 │   │   print("INPUT_VARS:", input_vars)                                                   │
│ ❱  59 │   │   json.dump(input_vars, f.file)                                                      │
│    60 │   │   f.file.flush()                                                                     │
│    61 │   │                                                                                │
│    62 │   │   if terraform_init:                                                                 │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/json/__init__.py:179 in dump                   │
│                                                                                │
│   176 │   │   │   default=default, sort_keys=sort_keys, **kw).iterencode(obj)                    │
│   177 │   # could accelerate with writelines in some versions of Python, at                      │
│   178 │   # a debuggability cost                                                                 │
│ ❱ 179 │   for chunk in iterable:                                                                 │
│   180 │   │   fp.write(chunk)                                                                    │
│   181                                                                                │
│   182                                                                                │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/json/encoder.py:432 in _iterencode             │
│                                                                                │
│   429 │   │   elif isinstance(o, (list, tuple)):                                                 │
│   430 │   │   │   yield from _iterencode_list(o, _current_indent_level)                          │
│   431 │   │   elif isinstance(o, dict):                                                          │
│ ❱ 432 │   │   │   yield from _iterencode_dict(o, _current_indent_level)                          │
│   433 │   │   else:                                                                              │
│   434 │   │   │   if markers is not None:                                                        │
│   435 │   │   │   │   markerid = id(o)                                                           │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/json/encoder.py:406 in _iterencode_dict        │
│                                                                                │
│   403 │   │   │   │   │   chunks = _iterencode_dict(value, _current_indent_level)                │
│   404 │   │   │   │   else:                                                                      │
│   405 │   │   │   │   │   chunks = _iterencode(value, _current_indent_level)                     │
│ ❱ 406 │   │   │   │   yield from chunks                                                          │
│   407 │   │   if newline_indent is not None:                                                     │
│   408 │   │   │   _current_indent_level -= 1                                                     │
│   409 │   │   │   yield '\n' + _indent * _current_indent_level                                   │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/json/encoder.py:406 in _iterencode_dict        │
│                                                                                │
│   403 │   │   │   │   │   chunks = _iterencode_dict(value, _current_indent_level)                │
│   404 │   │   │   │   else:                                                                      │
│   405 │   │   │   │   │   chunks = _iterencode(value, _current_indent_level)                     │
│ ❱ 406 │   │   │   │   yield from chunks                                                          │
│   407 │   │   if newline_indent is not None:                                                     │
│   408 │   │   │   _current_indent_level -= 1                                                     │
│   409 │   │   │   yield '\n' + _indent * _current_indent_level                                   │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/json/encoder.py:439 in _iterencode             │
│                                                                                │
│   436 │   │   │   │   if markerid in markers:                                                    │
│   437 │   │   │   │   │   raise ValueError("Circular reference detected")                        │
│   438 │   │   │   │   markers[markerid] = o                                                      │
│ ❱ 439 │   │   │   o = _default(o)                                                                │
│   440 │   │   │   yield from _iterencode(o, _current_indent_level)                               │
│   441 │   │   │   if markers is not None:                                                        │
│   442 │   │   │   │   del markers[markerid]                                                      │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/json/encoder.py:180 in default                 │
│                                                                                │
│   177 │   │   │   │   return super().default(o)                                                  │
│   178 │   │                                                                                │
│   179 │   │   """                                                                                │
│ ❱ 180 │   │   raise TypeError(f'Object of type {o.__class__.__name__} '                          │
│   181 │   │   │   │   │   │   f'is not JSON serializable')                                       │
│   182 │                                                                                │
│   183 │   def encode(self, o):                                                                   │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯

I hacked the terraform.py module to see what JSON was struggling with; it is this dictionary, with the KeyValueDict objects.
{'traefik-image': {'image': 'traefik', 'tag': '2.9.1'}, 'name': 'k3s', 'environment': 'nebari', 'node_groups': {'general': KeyValueDict(key='kubernetes.io/os', value='linux'), 'user': KeyValueDict(key='kubernetes.io/os', value='linux'), 'worker': KeyValueDict(key='kubernetes.io/os', value='linux')}, 'certificate-service': <CertificateEnum.selfsigned: 'self-signed'>}

Those were generated by nebari init though! Here is the existing section of the config yaml:
existing:
  kube_context: default
  node_selectors:
    general:
      key: kubernetes.io/os
      value: linux
    user:
      key: kubernetes.io/os
      value: linux
    worker:
      key: kubernetes.io/os
      value: linux

Expected behavior
It should make it through this stage without this error.
OS and architecture in which you are running Nebari
centos stream 8
How to Reproduce the problem?
installed a stock version of k3s. In order to get to this stage, I had to remove some of the Traefik CRDs that k3s installs for me, because they conflict with some that Terraform is trying to install. But once I let Terraform handle those, I was able to get to this point
Command output
nebari deploy -c nebari-config.yaml

### Versions and dependencies used.

conda 24.9.2
Client Version: v1.30.3+k3s1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.3+k3s1
Nebari version 2024.7.1

### Compute environment

None

### Integrations

_No response_

### Anything else?

_No response_

I hacked around that particular issue by editing _nebari/provider/terraform.py and creating a simple function to convert Pydantic objects to a dict:
def _to_dict(sd):
    if isinstance(sd, dict):
        return {k: _to_dict(v) for k, v in sd.items()}
    elif isinstance(sd, (list, tuple)):
        return [_to_dict(v) for v in sd]
    elif hasattr(sd, 'model_dump'):
        return sd.model_dump()
    else:
        return sd

Then used that to wrap the input to json.dump:
    with tempfile.NamedTemporaryFile(
        mode="w", encoding="utf-8", suffix=".tfvars.json"
    ) as f:
        json.dump(_to_dict(input_vars), f.file)
        f.file.flush()

That got me farther. However, it ended up failing later in the deployment process with a very similar issue:
╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/subcommands/deploy.py:92 │
│ in deploy                                                                                │
│                                                                                │
│   89 │   │   │   msg = "Digital Ocean support is currently being deprecated and will be remov    │
│   90 │   │   │   typer.confirm(msg)                                                              │
│   91 │   │                                                                                │
│ ❱ 92 │   │   deploy_configuration(                                                               │
│   93 │   │   │   config,                                                                         │
│   94 │   │   │   stages,                                                                         │
│   95 │   │   │   disable_prompt=disable_prompt,                                                  │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/deploy.py:53 in          │
│ deploy_configuration                                                                             │
│                                                                                │
│   50 │   │   with contextlib.ExitStack() as stack:                                               │
│   51 │   │   │   for stage in stages:                                                            │
│   52 │   │   │   │   s = stage(output_directory=pathlib.Path.cwd(), config=config)               │
│ ❱ 53 │   │   │   │   stack.enter_context(s.deploy(stage_outputs, disable_prompt))                │
│   54 │   │   │   │                                                                               │
│   55 │   │   │   │   if not disable_checks:                                                      │
│   56 │   │   │   │   │   s.check(stage_outputs, disable_prompt)                                  │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/contextlib.py:526 in enter_context             │
│                                                                                │
│   523 │   │   except AttributeError:                                                             │
│   524 │   │   │   raise TypeError(f"'{cls.__module__}.{cls.__qualname__}' object does "          │
│   525 │   │   │   │   │   │   │   f"not support the context manager protocol") from None         │
│ ❱ 526 │   │   result = _enter(cm)                                                                │
│   527 │   │   self._push_cm_exit(cm, _exit)                                                      │
│   528 │   │   return result                                                                      │
│   529                                                                                │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/contextlib.py:137 in __enter__                 │
│                                                                                │
│   134 │   │   # they are only needed for recreation, which is not possible anymore               │
│   135 │   │   del self.args, self.kwds, self.func                                                │
│   136 │   │   try:                                                                               │
│ ❱ 137 │   │   │   return next(self.gen)                                                          │
│   138 │   │   except StopIteration:                                                              │
│   139 │   │   │   raise RuntimeError("generator didn't yield") from None                         │
│   140                                                                                │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/stages/kubernetes_keyclo │
│ ak/__init__.py:302 in deploy                                                                     │
│                                                                                │
│   299 │   def deploy(                                                                            │
│   300 │   │   self, stage_outputs: Dict[str, Dict[str, Any]], disable_prompt: bool = False       │
│   301 │   ):                                                                                │
│ ❱ 302 │   │   with super().deploy(stage_outputs, disable_prompt):                                │
│   303 │   │   │   with keycloak_provider_context(                                                │
│   304 │   │   │   │   stage_outputs["stages/" + self.name]["keycloak_credentials"]["value"]      │
│   305 │   │   │   ):                                                                             │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/contextlib.py:137 in __enter__                 │
│                                                                                │
│   134 │   │   # they are only needed for recreation, which is not possible anymore               │
│   135 │   │   del self.args, self.kwds, self.func                                                │
│   136 │   │   try:                                                                               │
│ ❱ 137 │   │   │   return next(self.gen)                                                          │
│   138 │   │   except StopIteration:                                                              │
│   139 │   │   │   raise RuntimeError("generator didn't yield") from None                         │
│   140                                                                                │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/stages/base.py:65 in     │
│ deploy                                                                                │
│                                                                                │
│    62 │   ):                                                                                │
│    63 │   │   deploy_config = dict(                                                              │
│    64 │   │   │   directory=str(self.output_directory / self.stage_prefix),                      │
│ ❱  65 │   │   │   input_vars=self.input_vars(stage_outputs),                                     │
│    66 │   │   )                                                                                │
│    67 │   │   state_imports = self.state_imports()                                               │
│    68 │   │   if state_imports:                                                                  │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/_nebari/stages/kubernetes_keyclo │
│ ak/__init__.py:227 in input_vars                                                                 │
│                                                                                │
│   224 │   │   ]                                                                                │
│   225 │                                                                                │
│   226 │   def input_vars(self, stage_outputs: Dict[str, Dict[str, Any]]):                        │
│ ❱ 227 │   │   return InputVars(                                                                  │
│   228 │   │   │   name=self.config.project_name,                                                 │
│   229 │   │   │   environment=self.config.namespace,                                             │
│   230 │   │   │   endpoint=stage_outputs["stages/04-kubernetes-ingress"]["domain"],              │
│                                                                                │
│ /home/centos/ae5-conda/envs/nebari/lib/python3.12/site-packages/pydantic/main.py:164 in __init__ │
│                                                                                │
│    161 │   │   """                                                                               │
│    162 │   │   # `__tracebackhide__` tells pytest and some other tools to omit this function fr  │
│    163 │   │   __tracebackhide__ = True                                                          │
│ ❱  164 │   │   __pydantic_self__.__pydantic_validator__.validate_python(data, self_instance=__p  │
│    165 │                                                                                │
│    166 │   # The following line sets a flag that we use to determine when `__init__` gets overr  │
│    167 │   __init__.__pydantic_base_init__ = True                                                │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
ValidationError: 1 validation error for InputVars
node_group
  Input should be a valid dictionary [type=dict_type, input_value=KeyValueDict(key='kuberne...s.io/os', value='linux'), input_type=KeyValueDict]
    For further information visit https://errors.pydantic.dev/2.4/v/dict_type

Hi @mcg1969 , thanks for reporting this.
For local deploys, we use Kind and test with it. Using K3s would be essentially the same as using an existing cluster, which is the least tested and documented part of Nebari.
Could you validate that the local deploy with kind does work for you? That would let us narrow this down to the existing provider.
Thanks!

I was indeed using the existing approach, not the local approach. And that choice is deliberate—kind is not an option for the use case being considered here.

@dcmcand Confirming: I do not encounter this with the AWS target.

thanks @mcg1969, that is helpful.

@mcg1969 I was able to reproduce this issue when deploying to k3s from 2024.7.1, but not from the current main branch. There may be other issues, but this error is not occurring.
I believe  this issue is related to https://github.com/nebari-dev/nebari/issues/2767 and was likely fixed by https://github.com/nebari-dev/nebari/pull/2797. We will have a new release here within a couple of days. Once the new release is out, can you retry?
The traefik CRD's are still an issue, but that is essentially a new feature request, where this is a bug.


text:
Enhancement:

Could you make it so you can type the phrase for drunk notes / hivemind in capital letters? My i key doesn't work and I can only put it in capital letters (exept if I use caps lock wich doesn't work in friday night funkin for some strange reason) .
You could also make caps lock work.

Caps lock is weird with haxe
but yea sure I'll do the capital thing tho

authors: nebulazorua rickarockFR

repo: nebulazorua/vsomega


text:
Correct the text style of placeholders in IE

Not sure you get my comments on #571:

At least, if you are not convinced by my comment, you need to set the placeholder color for IE, as it doesn't use the text color by default:
:-ms-input-placeholder {
color: inherit;
}

In Edge placeholders will not show up in relative/absolute positioned inputs with an opacity < 1.
Bug report: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/3901363/
Test case: http://jsfiddle.net/wzmb7enL/
We can solve this in two ways:

Remove the placeholder normalisation altogether and let browsers / frameworks handle it
Set placeholder opacity to 1 (for Firefox) and use an arbitrary color

This meet my comment [https://github.com/necolas/normalize.css/issues/550#issuecomment-208262491]:

[…] i still believe that we have to force the placeholder color to a light grey for the moment, and fix Firefox - the only browser which do it differently - to opacity:1!

Looking at the bug report at https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/3901363/, it is now marked as fixed but there is no indication of when this happened or whether this is shipped or not.
My two cents: normalize.css seems to have opinions where they are necessary. The default might not be as good as the current value it uses, but I'd rather have to pick something else purposefully when I need to than have to deal with this bug if I notice it.

Closed via #587

Why was this issue closed? The way normalize is handling placeholders triggers a bug in Edge (see my previous comment).

I don't understand why this was closed either – #587 is about overriding default styles for consistency's sake, whereas this is about removing/changing the existing normalisation to fix a bug.

@jonathantneal, could we re-open this? So we can check the report made by @slavanga. If by adding a color normalization we are breaking the placeholder feature Edge on certain conditions, it's not a good thing.

This may be another example where normalize.css needs to leave the normalization due to side effects. However, it would be very useful to add a note to documentation. Anyone up for a PR?

@jonathantneal, if there is no way to safely normalize this, I'll be in favour of removing this completely and ASAP.
If anyone is up for a PR go ahead, if not I'll tackle this in a couple of hours.

Looking at the bug report at https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/3901363/, it is now marked as fixed but there is no indication of when this happened or whether this is shipped or not. Edit: trying out in a fresh Edge VM, it does not seem to be fixed yet.

Confirmed as fixed in Edge 16.16299 via Browserstack and in latest (18.18363) on local Windows 10.

authors: ThibWeb Yapaslfeu battaglr jonathantneal marsjaninzmarsa slavanga visicode


text:
Header style

Was trying to figgure out why I couldn't manage to get a header in bold and the message in normal style.
Figgured out that I was testing it in the error case and this css was beeing set as default:
this.$message.css({fontWeight: 'bold'});
Maybe abit confusing that this css is only applied to error and overrides what's beeing set in the text?

Yep, sorry about that. v3 released and js themes are deprecated now. All themes are uses css now.

authors: needim stibay

repo: needim/noty


text:
Separate tests into unit and acceptance tests

Changes

Separate tests into unit and acceptance test subfolders as part of #189:❯ tree TransformerLens/tests -I __pycache__
TransformerLens/tests
├── acceptance
│   ├── test_hook_tokens.py
│   ├── test_tokenizer_special_tokens.py
│   └── test_transformer_lens.py
├── manual_checks
│   ├── manual_checks_type_annotations.py
│   └── manual_checks_typing.py
└── unit
    ├── test_cache_hook_names.py
    ├── test_d_vocab.py
    ├── test_hooks.py
    ├── test_stop_at_layer.py
    └── test_utils.py

Move tests directory to project root
Update github actions to run the unit and acceptance tests separately.

Notes

The final requirement for #189 (namely, branch coverage) will be done in a separate PR
This PR conflicts with #188, since the latter is using the old directory structure

Stats
Local (M1 macbook air)

All tests (prior to changes)

Unit tests (after changes)
Acceptance tests (after changes)

Count
46

33
13

Run duration
60s

11s
50s

Code coverage
66%

51%
58%

Github actions
Sampled from latest checks run on main, and checks run from this PR

All tests (prior to changes)

Unit tests (after changes)
Acceptance tests (after changes)

Run duration
80-160s

14-20s
90-115s

Exceptionally good work! Thanks so much!

authors: jbloomAus rusheb

repo: neelnanda-io/TransformerLens


text:
[GSSOC'23] Add discord bot for spotify recommendations

Added code and Readme for a discord bot which allows users to specify a song they like along with a category. The bot can then try to recommend songs to the user.

This is for issue #49 , under GSSOC'23


text:
Added tests for utilities.ux

Fix issues detecting and outputing new version from PyPI

Checklist

[x] I have run nox and all the pipelines have passed.
[x] I have made unittests according to the code I have added/modified/deleted.

Related issues
#47

Holding off this for a little bit as im about to change these files with a bug fix.

Rebased and fixed tests that failed because of it :+1:

authors: davfsa nekokatt

repo: nekokatt/hikari


text:
可视化规则提取有没有好的框架或者解决方案

类似下面这几种：
在页面上可以通过点击的方式获取提取规则

python中有几个提供了类似的可视化提取的爬虫：
https://github.com/binux/pyspider
https://github.com/scrapinghub/portia

目前没有这个打算，大概以后也不会有..

目前没有这个打算，大概以后也不会有..

我提一下，看谁知道😂，我主要是好奇，那种方式有没有好的方式实现

目前没有这个打算，大概以后也不会有..

我提一下，看谁知道😂，我主要是好奇，那种方式有没有好的方式实现

可以参考这个 https://github.com/t9tio/cloudquery

目前没有这个打算，大概以后也不会有..

接活吗老板，爬虫管理系统

目前没有这个打算，大概以后也不会有..

我提一下，看谁知道😂，我主要是好奇，那种方式有没有好的方式实现

新的参考：https://github.com/NaiboWang/EasySpider

repo: nekolr/slime


text:
Remove the value from Address or public key field when co-signor is added

WTR:

Go to Multisig page
Add cosignor

Result: cosignor address was not removed from Address or public key field

Fixed in 0.13.8

Fixed in 0.13.8

authors: NikolaiB cryptoBeliever

repo: nemgrouplimited/symbol-desktop-wallet


text:
What neo4j data files should be ignored when persisting database in version control?

I have persisted my database by mounting the data volume in my docker-compose file. I am committing the database to git with the idea that as I develop, any changes to my database can be committed as dev data for the next time I start the container, no matter what machine I'm on.
Every time I run docker-compose stop, I notice that the following files have changed.
modified:   data/databases/graph.db/neostore.id
modified:   data/databases/graph.db/neostore.labeltokenstore.db.id
modified:   data/databases/graph.db/neostore.labeltokenstore.db.names.id
modified:   data/databases/graph.db/neostore.nodestore.db.id
modified:   data/databases/graph.db/neostore.nodestore.db.labels.id
modified:   data/databases/graph.db/neostore.propertystore.db.arrays.id
modified:   data/databases/graph.db/neostore.propertystore.db.id
modified:   data/databases/graph.db/neostore.propertystore.db.index.id
modified:   data/databases/graph.db/neostore.propertystore.db.index.keys.id
modified:   data/databases/graph.db/neostore.propertystore.db.strings.id
modified:   data/databases/graph.db/neostore.relationshipgroupstore.db.id
modified:   data/databases/graph.db/neostore.relationshipstore.db.id
modified:   data/databases/graph.db/neostore.relationshiptypestore.db.id
modified:   data/databases/graph.db/neostore.relationshiptypestore.db.names.id
modified:   data/databases/graph.db/neostore.schemastore.db.id
modified:   data/databases/graph.db/neostore.transaction.db.0

Are these the only files I should expect to change even if no changes are made to the database?
Is it safe to add them to my gitignore file or will issues arise as changes to these files further grow out of sync with the rest of the database?
Is there a better way to persist data for development?
What are the best practices if I'm not following them?
Thanks.

The manual recommends against backing up the data directory:

Using copy-and-paste to move the internal data directory, in order to transfer and seed databases is not supported. If you have an existing Neo4j database whose data you wish to use for a new cluster, it is recommended to create an offline backup using neo4j-admin dump. The resulting backup can then be used to seed the cluster by following the instructions in Section 5.3.3, “Seed from an offline backup”.
source
Neo4j did however recently change the compression algorithm of the dump from 3.5.4 to 3.5.5, resulting in a format incompatibility :sob: :astonished: :boom:
So for now, watch your Neo4j versions and I think a data directory would suit most use-cases.
As this practice is not recommended anyway, I think this issue can be closed.

authors: glevine nicorikken


text:
Custom file output format

As per the docs:
A package named helloworld.abstract.v1 will have an output filename of helloworld.abstract.v1.rs.

While this is  a nice readable format  having a dot in the file name makes it incompatible with rust for use directly with mod. The result is we are required to use include macro. But IDE's such as vscode with rust extension are unable to reference the definition for traits etc. This is sort of a big deal for developer UX.
If we allowed the separator to be configurable IE _ helloworld_abstract_v1.rs. would be valid. That would allow the below which also allows visibility into the trait source via IDE.
mod helloworld_abstract_v1;
mod helloworld_abstract_v1_tonic;

#[cfg(feature = "helloworld")]
pub mod helloworld {
    pub use super::helloworld_abstract_vs::*
    pub use super::helloworld_abstract_vs_tonic::*
}

I imagine this would mess with your prost-crate assumptions so perhaps we could gate this an not compatible? Or better yet we could adopt this output? :)

Much of this goes back to how prost-build is set up to generate these files. It makes certain assumptions about the module structure between various elements, and protoc-gen-prost-crate uses those conventions in setting up the includes.
In my case, I regularly use Visual Studio Code with the rust-analyzer plugin, and I don't seem to have the same issue that you appear to be indicating you have. I tried this in two fashions, from within and without the same crate where the definitions are being included, and I had no problems getting VSCode to bring up the trait methods:

Of note, the rust-analyzer plugin filters out functions for traits that aren't in scope. Thus, when I just press . without having prost::Message imported, I only see the following:

But, if I have already imported prost::Message into the file with use prost::Message, then I see this:

If you're more worried about the fact that "Go to definition" leads you to the include!() macro invocation, that is a limitation of rust-analyzer (rust-lang/rust-analyzer#3767 and rust-lang/rust-analyzer#9403). I'm not keen to add and support a new feature just to work around a tooling issue that should be fixed on that side.

While this is a nice readable format having a dot in the file name makes it incompatible with rust for use directly with mod.

Note that if you want this, you can specify the path manually with an attribute:
#[path = "helloworld.abstract.v1.rs"]
mod helloworld_abstract_v1;

Everything for the most part works fine with vscode but if I do [go to definition] I always land on the root include. Which I guess we can't completely blame on the implementation. I appreciate the feedback.

While this is a nice readable format having a dot in the file name makes it incompatible with rust for use directly with mod.

Note that if you want this, you can specify the path manually with an attribute:
#[path = "helloworld.abstract.v1.rs"]
mod helloworld_abstract_v1;

Nice this actually helps me a lot, had not tried that. Will close this as we have a viable workaround. Thanks!

authors: hexfusion neoeinstein

repo: neoeinstein/protoc-gen-prost


text:
ping intersection of groups

Consider implementing this suggestion:
https://www.reddit.com/r/Wumbotarian/comments/u7lwmz/user_pinger_2_test/iaascyn/?context=3

Decided I don't like this idea because it's too complicated


text:
fix #544

remove dash from maker name key

WAIT -- do not merge yet until discussion in #544 resolved

Thanks!
I came up with #547 already, which includes some style fixes, so I am closing this in favor of that.

authors: blueyed davidosomething

repo: neomake/neomake


text:
Revert timescaledb for pg14 and pg15

could not start the compute node: compute is in state "failed": db error: ERROR: could not access file "$libdir/timescaledb-2.10.1": No such file or directory Caused by: ERROR: could not access file "$libdir/timescaledb-2.10.1": No such file or directory

Release notes are not required, Postgres 16 won't support timescaledb yet (it requires changes in control plane)

Thank you for the heads up

authors: bayandin danieltprice vadim2404

repo: neondatabase/neon


text:
added ipam and nf-injector packages

Added spam and nf-injector packages

changed the registry to gcr.io/jbelamaric-public so we need to ensure the images get created in this registry

Nice! Thanks. I haven't built and pushed IPAM images yet or tried out the actual IPAM injection. Will do that first change I get (probably tomorrow morning).

authors: henderiw johnbelamaric

repo: nephio-project/nephio-packages


text:
Allow configuration of an external webhook and its associated certs in the Porch API server

The Porch API server can use a validating webook to check whether delete requests should be allowed or not. If the CERT_STORAGE_DIR environment variable is not set, Porch does not validate deletions. If the CERT_STORAGE_DIR environment variable is set, Porch generates a validating webhook and its associated certs.
Using a webhook ensures that resources are only deleted when the user has authority to do so.
However, the Porch API server cannot today be configured to use an externally configured webhook. In addition, the current self generated webhook has a number of drawbacks:

Access to the deletion commands cannot be controlled by configuration
The generated certificates time out after a year
The service name on which the webhook acts and the configuratino name cannot be controlled by configuration
The namespace on which Porch is installed is hardcoded to "porch-system" {fixed in PR-26}

This issue proposes adding support for externally configured webhooks to the Porch API server.

/assign @Catalin-Stratulat-Ericsson

Triaged

https://github.com/nephio-project/porch/pull/53

authors: efiacor liamfallon

repo: nephio-project/nephio


text:
Enable periodic task execution for OAI End-to-End testing

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test

/kind feature

/kind flake

What this PR does / why we need it:
Until now, OAI e2e execution is done on demand basis. That restriction limits the capability for catching errors on new changes. This change enables the End-to-End test execution for OAI use case.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@electrocucaracha What is the benefit of doing this? Sorry I am not aware why are we doing this?

/approve

@electrocucaracha What is the benefit of doing this? Sorry I am not aware why are we doing this?

This will execute the OAI end-to-end tests on a daily basis

/lgtm

authors: arora-sagar electrocucaracha radoslawc

repo: nephio-project/test-infra


text:
[FEATURE] missing assets (rpm) for 0.55

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
A hopefully small ask: version 0.55 does have pre-built rpm assets available.
yes, the Makefile is right there, but that's not entirely feasible/easy in some contexts. One might have yum but no "allowed" go compiler for instance. Also, thanks for un-deprecating custom namespaces.
Apologies for the unusual request, it isn't done lightly. Appreciate all the work and features.
What might the configuration look like?
No response
Anything else?
No response

Release is out, sorry for the delay.

authors: cristiangreco fabioasdias


text:
[BUG] ApiGateway metrics being skipped "metric":"IntegrationLatency","msg":"skipping metric unmatched by associator"

Is there an existing issue for this?

[X] I have searched the existing issues

YACE version
0.57.1
Config file
apiVersion: v1alpha1 discovery:   jobs:     - type: AWS/ApiGateway       regions:         - us-east-1       period: 300       length: 300       metrics:         - name: 4XXError           statistics: [Sum]         - name: 5XXError           statistics: [Sum]         - name: IntegrationLatency           statistics: [Maximum, Average, p99]         - name: Latency           statistics: [Maximum, Average, p99]
Current Behavior
ApiGateway v1 metrics appear to work correctly and show up in the metrics page and prometheus.
V2 have log messages as follows:
{"account":"redacted","arn":"","caller":"discovery.go:248","dimensions":"ApiName=my-api,Resource=/myenResource,Stage=mystage,Method=POST","job_type":"AWS/ApiGateway","level":"debug","metric":"IntegrationLatency","msg":"skipping metric unmatched by associator","region":"us-east-1","ts":"2024-07-16T21:08:36.186928023Z","version":"0.57.1"}
Expected Behavior
metrics are not skipped and show up in prometheus and are searchable by dimensions that show up on v1 resources
Steps To Reproduce

ensure metrics are visible with dimensions in cloudwatch for given resource
add above configuration to yace
restart yace to ensure config is loaded
read log messages from yace and observe no errors.
add debug flag to log and restart yace to observe skipping messages

Anything else?
We have tried both with and without the enable max dimension association and aws-sdk-v2 features, neither seems to have any impact. It is unclear why these are being skipped and adding required dimension names causes it to find no metrics at all and even the v1 metrics disappear
Additionally we have tried adding dimension requirements which causes ALL apigateway metrics to be skipped

Confirmed this issue also exists in latest release 0.61.2


text:
🛑 keen.nerevar.com is down

In c49299d, keen.nerevar.com (https://keen.nerevar.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: keen.nerevar.com is back up in 20c7cd0.


text:
Depth map when training with nerfacto seams like not actual depth map

Hello,
I am working on custom export from nerfstudio based on render.py, where I need to render "rgb" and "depth" channels into separate images along camera path.
Trying to use output["depth"] image as depth map in OpenGL using perspective projection from camera intrinsics and view from extrinsic(camera path) gives very distorted result, it seams that output["depth"] is not actual depth map but rather range map.
I made this assumption looking at exoporter_utils.py:158, when it used as:
point = ray_bundle.origins + ray_bundle.directions * depth
Is it true? Or am I missing something?
If so, what`s the logic behind it?
Are there any utility functions to convert resulted range map to real depths already implemented?

I think the comment linked below is relevant. Basically, it's just an issue of terminology.
https://github.com/nerfstudio-project/nerfstudio/issues/1028#issuecomment-1331488668

Hello!
Were you able to obtain the actual Depth Map?
I'm working on a project that needs to export the distance from the camera to each pixel in the image, but I don't know how to do it.

authors: VladMVLX decrispell ferphy

repo: nerfstudio-project/nerfstudio


text:
Postshot has better quality splats - due to suboptimal colmap usage/algorithm/both?

TL;DR
I compared the splats of a room generated by Splatfacto and Postshot with the same inputs, and consistently found Postshot to be crisper.
Do we already know if some components (ns-process-data or Splatfacto algorithm) are suboptimal, particularly regarding how ns-process-data uses colmap outputs?
Set up
Inputs (for the same room):

iPhone 14 video, no special setting
Budget android phone: 56 photos, using 1/60s shutter speed + ultrawide. The pictures aren't blurry.

Both Nerfstudio and Postshot were run on Windows.
Nerfstudio
I used ns-process-data video/images to generate inputs for training.

iPhone video: 364 images were extracted for the video, while transforms.json contains 342 frames.
android: transforms.json only contains 25 frames (out of 56), even if I used --matching-method exhaustive.

Postshot
I tried these 2 settings:

Import the raw video/images directly, and let Postshot register the camera poses (Use Best Images for image selection)

For iPhone, it tracked 219 images from the video
For android, it tracked 52/56 images

Use the cameras.bin + images.bin + points3D.bin + images folder generated from  ns-process-data above

For iPhone, it managed to track 362/364 images
For android, it managed to track 47/56 images

Default settings were used for training (Splat MCMC). Subjectively, I found the splat quality of these 2 settings to be pretty similar.
Results
Postshot tend to have crisper results for all cases. All renders are 1920 x 1080.
iPhone
Nerfstudio

Postshot (direct import)

Postshot (colmap)

android
Nerfstudio

Postshot (direct import)

Postshot (colmap)

Questions
As a supporter of open source, I'd love to see Nerfstudio match the quality of Postshot. Asking these questions to better understand where I can possibly contribute:

Postshot matches more images using the same colmap outputs (the *.bin files) as Nerfstudio (transforms.json). Why is that the case?
Would hcol perform better than colmap for ns-process-data? Tried using it but haven't managed to get the pycolmap dependency to install on Windows so far.
Is the Splat MCMC algorithm used in Postshot an improved version of the original GS, or are they comparable? Would like to understand whether the quality difference mainly comes from SfM or the splatting algorithm - seems to be the former based on what I have seen so far.

Your iphone results doesn't look right to me. If you can share cameras.bin + images.bin + points3D.bin + images folder , I might be able to debug a bit.

Thanks for your response! I uploaded them here.
Is there anything else you'd suggest me to look at on my side? Bottom line, given the same inputs, do we expect the quality of Splatfacto to be similar to other implementations?

authors: jb-ye tangfucius


text:
Add PyTorch profiler to support tracing of forward/backward calls

This PR adds the support for PyTorch profiler (https://pytorch.org/tutorials/recipes/recipes/profiler_recipe.html)
It also changes the time_function decorator to act as a context manager - enabling blocks of code to be timed as well.
Trace example:

Hi, such a feature break the PyTorch 2.0 support:
ImportError: cannot import name 'ContextDecorator' from 'torch.autograd.profiler' (/usr/local/lib/python3.8/dist-packages/torch/autograd/profiler.py)

authors: jkulhanek yzslab


text:
Color outside of render view

Currently the inside is colored which is counterintuitive.

Fixes #419


text:
refactor: sets correct typing to inject property

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

The inject property at HttpModuleAsyncOptions was typed as any[], causing some confusion.
Issue Number: N/A
What is the new behavior?
The inject property at HttpModuleAsyncOptions is now typed as InjectionToken that was brought from nest core repository.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
I would also like to suggest adding a section to the module's documentation page about injecting standalone providers since only registering them at extraProviders is not enough. As soon and if this type refactor is merged I will myself open another pr updating the docs.

lgtm

authors: ivanzigoni kamilmysliwiec

repo: nestjs/axios


text:
Whether to support TCPOnly when udp is restricted by the carrier.

Whether to support TCPOnly when udp is restricted by the carrier.

it is possible to support TCP only for connections that require Relay (the case you described), we might need to adjust a bit the agent

@mlsmaycon
Please add it. It would be good a method that work similar way with DERP server. It is the only relay server that work every place that i test it! (i think the reason is the TLS/HTTPS working method)

@iamshiyan
It is out there already! We have a single TCP relay running and listening on port 443, but we will deploy more.
Works with our cloud version at https://app.netbird.io/.
Self-hosted is supported as well.

@iamshiyan It is out there already! We have a single TCP relay running and listening on port 443, but we will deploy more. Works with our cloud version at https://app.netbird.io/. Self-hosted is supported as well.

How can this be self-hosted? I mean, I have a coturn server listening in UDP/TCP and I changed my management.json "Proto" to "TCP" in "Stun" and "Turn" sections, but this doesn't work when I block all UDP traffic with my firewall (it works, however, in unblocked UDP traffic). So, what am I doing wrong?

@fernandoenzo @iamshiyan, Sorry for not getting back sooner. You can configure a TCP relay by adding a setting like the in your management.json Turn config:
        "Proto": "tcp",
        "URI": "turn:turn.example.com:3472?transport=tcp",

I will close this issue for now, please open a new one in case you want further assistance.

@mlsmaycon   Does netbird support  udp relay?
if I set  no-udp and  no-udp-relay in coturn turnserver.conf,  the netbird get error
netbird status -d
Relays:
  [stun:stunserver.stunprotocol.org:3478] is Available
  [stun:stun.freeswitch.org:3478] is Available
  [turn:turn-home.ioth.top:6478?transport=tcp] is Unavailable, reason: allocate: Allocate error response (error 442: UDP Transport is not allowed by the TURN Server configuration)

if I set no-udp, but unset no-udp-relay in coturn turnserver.conf,  the netbird status no error, but I seem that netbird client use udp to connect coturn relay :
netbird status -d
Relays:
  [stun:stunserver.stunprotocol.org:3478] is Available
  [stun:stun.freeswitch.org:3478] is Available
  [turn:turn-home.ioth.top:6478?transport=tcp] is Available

authors: braginini fernandoenzo iamshiyan mlsmaycon vampywiz17 xiaolei0125

repo: netbirdio/netbird


text:
docker setup stuck at login page

Hello,
I followed your docker guide with the self-hosted keycloak and everything went without errors.
On the first load in the browser, after all containers were up, there was only a blank page with this error in the browser console:
Uncaught TypeError: Failed to construct 'URL': Invalid base URL
at LoginError.tsx:54:12
at index.tsx:54:24
As there were no errors in the container logs, I think this is a bug in the frontend javascript. Any idea how to resolve this? :-)

How did you solve it?


text:
Input validation error: inputs must have less than 512 tokens. Given: 1009

Hi,
using huggingface/text-embeddings-inference I have deploy bce-reranker-base_v1 model.
In the info endpoint and in your provided example I can see you are setting max_length=512
could you confirm this model support only 512 tokens only or Is there any way to process long text without truncate ?

Thank you for your interests!

We propose our bce-reranker-base_v1 for reranking long passages (each passage < 32k tokens) by our python package BCEmbedding. You can install it simply by pip install BCEmbedding.
The usage for reranking long can be checked in "https://github.com/netease-youdao/BCEmbedding?tab=readme-ov-file#1-based-on-bcembedding". We must mention that our bce-reranker-base_v1 just supports max length for 512, and the method for reranking long passages is open-source (see "NOTE" in the url above), which is a good balance between efficiency and effectivity (also adopted by other projects).

repo: netease-youdao/BCEmbedding


text:
Is it possible to do server-side rendering on Heroku?

The Deployment doc doesn't mention this scenario explicitly and I've been unable to get this working on my own. My understanding is that Heroku only opens one port, so I'm fearful that this isn't possible, as the Rails application won't be able to communicate with the Node server via HTTP.
In case it's helpful, here's the error I'm seeing: 2016-08-29T02:59:22.994608+00:00 app[web.1]: ActionView::Template::Error (Failed to open TCP connection to localhost:8081 (Connection refused - connect(2) for "localhost" port 8081))
Assuming this is not possible, could anyone suggest an alternative approach? The one that jumps to mind is deploying node_server.js as its own application, but I'm hoping to not have to go down that rabbit hole.

Hi Pete,
I will look into that this week, this is weird thought because as I
remember multiple processes on same Dyno can talk to themselves on any
ports..
On 29 August 2016 at 05:33:51, Pete Doherty (notifications@github.com)
wrote:

The Deployment doc doesn't mention this scenario explicitly and I've been
unable to get this working on my own. My understanding is that Heroku only
opens one port, so I'm fearful that this isn't possible, as the Rails
application won't be unable to communicate with the Node server via HTTP.
In case it's helpful, here's the error I'm seeing: 2016-08-29T02:59:22.994608+00:00
app[web.1]: ActionView::Template::Error (Failed to open TCP connection to
localhost:8081 (Connection refused - connect(2) for "localhost" port 8081))
Assuming this is not possible, could anyone suggest an alternative
approach? The one that jumps to mind is deploying node_server.js as its own
application, but I'm hoping to not have to go down that rabbit hole.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/netguru/react_webpack_rails/issues/124, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AGuMWeB9hYXuDivSn8poiqDjC9RrU1V0ks5qklMfgaJpZM4JvHcP
.

Did you ever get a chance to look into this issue, @rpunkfu?
I'm probably going to take another pass at my integration next week. If I can't get server-side rendering working on Heroku, I was thinking about forking the project (and submitting a PR, if you'd be open to it) and adding an option to specify a render server URI.

Hi @ethagnawl, sorry but I didn't have enough time to investigate this issue, will do it asap :)

@rpunkfu Thanks! :smile:

I just spent literally all day and half the night on figuring this out, and I'm happy to say that I did get it working, and it IS IN FACT POSSIBLE, even though heroku seems to be intentionally hiding that fact from their users (not that I'm bitter /s).
All the docs and all the stackoverflow answers say that it's not possible to run two http processes on the same dyno, but that's not true. I think it's partially a ploy to get you to use their enterprise product, or run more dynos than you need since they all cost money.
OK seriously, I'll try to stop ranting and tell you how I got it to work. The only caveat is that only one process can respond to an external port, but that's ok because you only need one (the rails one) for this SSR setup. The node process can be on an internal firewalled localhost-only port, and in fact that's better for security purposes. We don't want the node process exposed to the real world.
Here's how: since you can only have one "web" process in your Procfile, what you have to do is assign a script of somekind to the "web" heading. I named mine web.sh in the root of the project. So my procfile looks like this:
web: ./web.sh

And the contents of the web.sh script starts up first the node process, then the rails process.  Here's how mine looks:
forevercmd="./node_modules/forever/bin/forever ./app/client/node_server.js"
$forevercmd &disown
bundle exec puma -C config/puma.rb

Running forever like that leaves it in the mode where it "logs" to stdout, so that the normal heroku logs command shows output from it as well as the rails process. You could use the forever start form too, and have it log to a file or whatever, if that is better for your purposes. But it can't block, it has to daemonize or background somehow so that the puma process can start too. And heroku will cut you off after 60 seconds if it takes too long to initialize, so you can't put too much in here (I naively tried putting npm install in here in one of my many missteps).
Anyway, hope that helps.

Looks like @jeffgran has provided the canonical solution.
@rpunkfu, perhaps it's worth mentioning this solution in the deployment docs? I'd be happy to submit a PR.

Note for anyone else experiencing issues with this solution. I was able to get it to work, but ran into a few small errors that needed adjustment for my setup:
- Heroku had permission errors on the web.sh file initially - had to chmod it locally and redeploy.
- The default RWR setup puts the node_server.js file under the react directory. The first line of the web.sh file needed to be changed to
forevercmd="./node_modules/forever/bin/forever ./app/react/node_server.js"
- Heroku threw some unexpected syntax errors when trying to execute the node_server.js file. I had to make some adjustments to the default node_server.js file generated by RWR. I posted the working file in this gist: https://gist.github.com/mattmanske/4fe7915d949de25556c1ee1f7f6a1744

authors: ethagnawl jeffgran mattmanske rpunkfu


text:
Multi filter

Description

Dependencies

n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[ ] Will this change affect NetObserv / Network Observability operator? If not, you can ignore the rest of this checklist.
[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/ok-to-test

/ok-to-test

/ok-to-test

repo: netobserv/flowlogs-pipeline


text:
NETOBSERV-1665: use v1 for conversionReviewVersions

Note we're talking here about versions of ConversionReview (ie. apiextension), NOT versions of our CRDs

Use same versions for flowcollector and flowmetrics
Use just v1 as the only other (v1beta1) was dropped a while ago (kube 1.22 / 2021)

/lgtm

/approve


text:
Help building libwebpdemux.so

Hi, your project is great!
I started to write a wrapper for the animation (demux) but it's been more than a week that I'm trying to build the demux shared library for Android and Ios (libwebpdemux.so), Can you please explain me how to do that ?

@sharedNoob sorrty late reply. in my memory libwebp contains webpdemux. but i'm not sure I will check it later when I have a time.

https://github.com/netpyoung/unity.webp/pull/17

authors: netpyoung sharedNoob


text:
Epoll: Ability to get amount of sent segments

Expected behavior
To calculate the packet loss percentage, it would be possible to do tcpi_lost * 100 / tcpi_data_segs_out.
Sadly, tcpi_data_segs_out is required to get the amount of sent segments, which is not exposed.
Adding it directly might not work either, because not all Linux versions support it.

In other words, you want to be able to query tcp_info from getsocketopt?

A mechanism to do this already exists, it's just lacking some fields

Closed due to glibc not providing an up to date struct.

authors: chrisvest dries-c

repo: netty/netty


text:
When Channel connect failure,Channelbecome invalid;

when Channel connect failure,Channel should give a method to replace the socket,not replace Channel.

I think that's not a good idea.

Same here... Can you explain why you think it makes sense?

Same here, the problem is that this will render lots of handler events useless and ambiguous (like channel active and so forth), since you very often need to bind them to implicit socket events. I'm sure your use case can be handled with our current semantics as well :)

No proper rationale

authors: chzhuo daschl normanmaurer rockagen trustin


text:
Custom ChannelHandlerInvoker doesn't get invoked

According to this comment, starting from Netty 4.1 I can specify my custom ChannelHandlerInvoker in order to emulate legacy thread model. I created a simple echo server in order to demonstrate that the custom ChannelHandlerInvoker isn't used in case the channel pipeline has only one outbound ChannelHandler.
It turns out that my custom ChannelHandlerInvoker isn't used for, let's call them technical channel handler's. There're at least two of them - HeadContext (which is an outbound channel handler) and TailContext (which is an inbound channel handler).
When I call ctx.writeAndFlush, Netty is trying to find an outbound channel handler context, grabs a channel handler invoker and call the according methods.
The problem is Netty doesn't check the current channel handler context, but moves backwards until it finds an outbound one.
As I said previously, 'technical'  channel handlers don't get a custom channel handler invoker that I specify in the channel pipeline. As a result, HeadContext uses DefaulChannelHandlerInvoker instead my custom one.
To reproduce the problem, please do the following:

grab the source code
build the project with maven clean assembly:assembly
run it with java -jar ./target/delivery/cci.jar -c or java -jar ./target/delivery/cci.jar -d
connect to the server via telnet: telnet localhost 8080 and send a random message

If you run an application with a -d flag, you won't see any log messages on the server side if you send a message via telnet. On the other hand, if you run the application with a -c flag, you'll see two log messages on the server side per message that you send via telnet. If you specify the -c flag, the application will be using the redundant OutboundChannelHandlerAdapter in the pipeline which makes the CustomChannelHandlerInvoker work.

@maseev I think what you explained make sense. If you want to have the invoker be used then you should call ctx.channel().writeAndFlush(...). This will dispatch the write via the TailContext and so ensure the invoker is used.

authors: maseev normanmaurer


text:
Http2Codec fails silently when the server tries to send too big headers

When the server tries to send a response with too big headers according to the negotiated SETTINGS_MAX_HEADER_LIST_SIZE, it only half-closes and fails silently.  I think it should instead fireExceptionCaught.

This is easy to reproduce.  Spin up an http/2 server, and have it respond to a request with a header of size 10K.

I'm having an awful time testing this, but I think the solution is simple:
diff --git a/codec-http2/src/main/java/io/netty/handler/codec/http2/Http2MultiplexCodec.java b/codec-http2/src/main/java/io/netty/handler/codec/http2/Http2MultiplexCodec.java
index 8b3ec62..24953c7 100644
--- a/codec-http2/src/main/java/io/netty/handler/codec/http2/Http2MultiplexCodec.java
+++ b/codec-http2/src/main/java/io/netty/handler/codec/http2/Http2MultiplexCodec.java
@@ -388,6 +388,7 @@ public final class Http2MultiplexCodec extends ChannelDuplexHandler {
                 promise.addListener(this);
             } else {
                 frame.streamId(streamId());
+                promise.addListener(ChannelFutureListener.FIRE_EXCEPTION_ON_FAILURE);
             }
             writeFromStreamChannel(frame, promise, false);
         }

@normanmaurer do you have tips for how I should test this?

@mosesn writes usually not results in exceptionCaught(...) calls but should just fail the promise. Let me think a bit about this.

@normanmaurer the problem I'm running into is that the promise isn't accessible.

@mosesn yep which I think is the "core problem" and I think we need to make this happen ;)

@normanmaurer should I post the diff I wrote in a comment before as a PR, or do you have another idea?

@mosesn like I said I need to think a bit more about it. I think we need to refactor the whole child channel thing a bit to make it "better" and so allow to be notified

oof, OK.  I'll just document the bug in our codebase for now.

@buchgr @ejona86 btw if you have any "good" idea let me know

If I understand correctly, this problem is solved by #5914. That is, the promise will be "accessible" on the child channel and fail with the correct error. We introduced ChannelOutboundBuffer#steal and https://github.com/netty/netty/pull/5914/files#diff-1467546ce755a7d28826823167febd0fR370 to fix this.

This was a known deficiency caused by ChannelOutboundBuffer. The issue tracking it is #4941: "If we solve enough to make outbound flow control work, we should naturally end up fixing the premature child promise completion in the child's doWrite due to ChannelOutboundBuffer."
steal() or avoiding ChannelOutboundBuffer allows it to be resolved.

OK, this makes sense to me.  @ejona86 @buchgr what do you think about cherry-picking that fix into netty so we don't have to wait on #5914?

@mosesn I (as the author of that fix) am obviously fine with that :-). I believe @normanmaurer had some concerns about ChannelOutboundBuffer#steal.

this seems to be fixed in 4.1.8, though I haven't looked into the exact mechanism.  anyway my test is no longer failing =).  I'm going to mark this as fixed, although y'all can reopen if you still have a problem with it.

Just some bookkeeping ... The "low level API" now explicitly checks for HPACK encoder errors (mainly because SETTINGS_MAX_HEADER_LIST_SIZE is exceeded) and this is enabled by default. This is a combination of https://github.com/netty/netty/pull/6230 and https://github.com/netty/netty/pull/6284. I'm not sure what your tests look like but it is possible these changes impacted the behavior you observe.

I think I've triggered this in 4.1.8 as well and didn't see problems. But I will note that since SETTINGS_MAX_HEADER_LIST_SIZE is advisory, I was actually surprised that netty enforced it locally. Bugs with HPACK error handling should be fixed, but if this specific problem resurfaces it could be solved by removing the outbound check.

authors: Scottmitch buchgr ejona86 mosesn normanmaurer


text:
Is it ok to discard all the related tasks when a connection is closed ?

Expected behavior
I have come to this case, I have a Handler which invokes RPC calls, and i have used a separate EventLoopGroup for the Handler, but RPC call takes time, and when there are too many requests, all the thread in the EventLoopGroup will be blocked, waiting for RPC responses, so new tasks will be added into the queue.
Till now it is normal, but when a connection is closed, those RPC calls made by the connection are still in the queue waiting to be executed, but in fact, i don't want them to be executed any more.
So i just wonder, is it ok to discard all the tasks made by a connection when the connection is closed but the tasks are not executed yet ?
If it's ok, will netty support this kind of operation ?
Thank you ~

This is an issue tracker... Please use stack overflow for questions.

@normanmaurer Sorry, i just thought maybe it would also be a proposal ~

authors: medusar normanmaurer


text:
Make half-closure a core-concept of Channel

Motivation:
At the moment our half-closure support is kind of weak and hacky. We use various DuplexChannel specific methods which will not traverse the pipeline at all and also use user events. This should be changed to be a "core concept" and so have dedicated methods that can be used and also traverse the pipeline.
What shutdown(...) actually means is a bit transport specific but in general once someone shutdown the output it should not be possible to write anymore. Also when the inbound is shutdown we should not propagate inbound messages anymore. If the shutdown calls are propagated through the network somehow is specific to the protocol itself and so might differ.
Modifications:

Add ChannelOutboundInvoker.shutdown(ChannelShutdownDirection) method
Add ChannelInboundInvoker.fireChannelShutdown(ChannelShutdownDirection) methods
Add Channel.isShutdown(ChannelShutdownDirection) method
Add ChannelHandler.shutdown(ChannelHandlerContext, ChannelShutdownDirection) and ChannelHandler.channelShutdown(ChannelHandlerContext, ChannelShutdownDirection) methods
Refactor code to use the new methods and also add implementations for the different transports

Result:
Half-closure is now a core-concept of netty.

@chrisvest this is still a work in progress as I am not 100 % done yet with adding the correct implementation for all transports etc

This is now ready @chrisvest

This fixes https://github.com/netty/netty/issues/8509

rebased

@chrisvest addressed all comments. PTAL again :)


text:
Remove unused interface

Motivation:
The NioProcessor interface is not used anymore.
Modifications:
Remove dead code
Result:
Cleanup

Noticed this while porting even loop changes to main


text:
Correctly resume wrap / unwrap when SslTask execution completes

Motivation:
fa6a8cb09c9679468a6c2d912ddfbbe885ee0c08 introduced correct dispatching of delegated tasks for SSLEngine but did not correctly handle some cases for resuming wrap / unwrap after the task was executed. This could lead to stales, which showed up during tests when running with Java11 and BoringSSL.
Modifications:

Correctly resume wrap / unwrap in all cases.
Fix timeout value which was changed in previous commit by mistake.

Result:
No more stales after task execution.

test failure was a network problem on the CI... let me trigger a test run again

@netty-bot test this please


text:
Failed to create or update nsm on deploy with custom namespace

Expected Behavior
nsmd-k8s registry stores nsm only for self namespace.
Current Behavior
nsmd-k8s registry stores nsm for all namespaces.
Steps to Reproduce

Deploy nsmgr with the default namespace
Delete nsmgr pod, but not delete custom resources
Deploy nsmgr with a custom namespace

Failure Logs
time="2019-08-19T08:29:56Z" level=info msg="Updating existing NSM: &{{NetworkServiceManager networkservicemesh.io/v1alpha1} {kube-master  default /apis/networkservicemesh.io/v1alpha1/namespaces/default/networkservicemanagers/kube-master 01611f0f-3a03-4e8e-9df9-f8ec64aa7e31 302157 1 2019-08-19 08:14:54 +0000 UTC <nil> <nil> map[] map[] [] nil []  []} {} {2019-08-19 08:14:54 +0000 UTC 10.32.0.4:5001 RUNNING}} with &{{ } {kube-master      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] nil []  []} {} {2019-08-19 08:29:56.056228103 +0000 UTC m=+41.321607540 10.32.0.5:5001 RUNNING}}"
time="2019-08-19T08:29:56Z" level=error msg="Failed to create or update nsm: the namespace of the object (default) does not match the namespace on the request (another-w4c2h)"

by some experiments found that the problem related only to nsm custom resources.

the issue is fixed by https://github.com/networkservicemesh/networkservicemesh/pull/1537

repo: networkservicemesh/networkservicemesh


text:
Issue with Single Quotes on Windows

Hi,
The plugin has worked well on MacOS, running the gradle script on a Windows machine using GitBash, the following error results.   Is this an issue with the use of Single Quotes rather than Double Quotes?  If so, what recommendations do you have for resolving this?
Thanks!
:releaseerror: pathspec 'version.txt' did not match any file(s) known to git.
FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':release'.

Process 'command 'git'' finished with non-zero exit value 1

Please try "chmod 777 version.txt" in git bash on windows.

Hello,
I tried that and I get the same result.
Perhaps your plugin needs to use a cross-platform plugin for the Exec command: https://github.com/jlouns/gradle-cross-platform-exec-plugin [https://github.com/jlouns/gradle-cross-platform-exec-plugin]
On Mon, Nov 13, 2017 at 2:18 AM, Stefan notifications@github.com wrote:
Please try "chmod 777 version.txt" in git bash on windows.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [https://github.com/netzwerg/gradle-release-plugin/issues/38#issuecomment-343844194] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ACL6UbRgGZqkZFMeFTf2PrUkH94Fmt-yks5s1_tBgaJpZM4QbEVL] .

Sorry for not getting back to you earlier – did you have any success in the meantime? Unfortunately, I personally only use the plugin on OSX and Linux, but afaik others are successfully using it on Windows...

authors: djeverson netzwerg stefanleh

repo: netzwerg/gradle-release-plugin


text:
🛑 Neurobagel INDI node (https://indi.neurobagel.org/) is down

In 32ccefc, Neurobagel INDI node (https://indi.neurobagel.org/) (https://indi.neurobagel.org/) was down:

HTTP code: 523
Response time: 3306 ms

Resolved: Neurobagel INDI node (https://indi.neurobagel.org/) is back up in a9d71a9 after 1 hour, 29 minutes.

repo: neurobagel/upptime


text:
Create a global dataclass to hold set-up specific settings

So I was checking the new read_mne_data function, that takes line_noise as do many things around the package. As I mentioned in PR #329 it seems like line_noise is crowding a lot of function parameter lists for a thing that is only actually read in a single line of the entire database.
So far we're sticking to the principle that NMSettings should only hold settings concerning the desired data analysis, and that has the great advantage that these settings are portable and shareable between setups and experiments.
On the other hand, excluding some set-up/recording specific settings from NMSettings makes it so that we have some relevant settings that just float around the code and need to be passed all the time around functions, when in reality is never a necessity to specify them more than just once. Off the top of my head:

sfreq
line_noise
nm_channels: a bit less straight-forward, but the more I think about it, the more sense it makes to me. Channels are set-up with the experiments, as they depend on the equipment available and the number and type of electrodes, EEG sensors or whatever other instrumentation is available at the time of the experiment.

I was thinking we can create some kind of data structure (e.g. a Pydantic dataclass) that holds these kind of variables, and call it ExperimentSettings or similar. If maybe that's overkill, maybe we can just make line_noise global, default to 50 Hz and set up a utility function called set_line_noise.
If this is considered a non-issue and needs no addressing, or if my assumptions are mistaken, feel free to close the issue.

It's definitely a good point @toni-neurosc! I see the reason behind it keeping all those information at a single place. Currently however I would focus on different issues, and keep it in mind for later. We should keep the issue however open imo

Well I just realized that his might be a duplicate of #315 ... it's not exactly the same but deals with the same fundamental issue. Maybe the 2 issues can be merged?

Duplicate of #315

authors: timonmerk toni-neurosc


text:
file format not recognized; treating as linker script !

Hi
Qt Creator Error:
/opt/qtrpi/raspbian/sysroot/lib/arm-linux-gnueabihf/libpthread.so.0:-1: error: file format not recognized; treating as linker script
/opt/qtrpi/raspbian/sysroot/lib/arm-linux-gnueabihf/libpthread.so.0:1: error: syntax error
:-1: error: collect2: error: ld returned 1 exit status
what is the meaning of this errors?!
thanks

Hi @coloop ,
What is the system your machine is running on?
The error seems to indicate an incompatible file format between the qtrpi installation and your computer.

@synapticvoid
Hi
I am using Ubuntu 17.04.
and the error not solved!

authors: coloop synapticvoid

repo: neuronalmotion/qtrpi