Hitting "Enter" in the taxon chooser on Identify deletes taxon

Using Safari 12.1.2. Seems to break https://github.com/inaturalist/inaturalist/issues/2101
Currently if you add an ID in the Identify modal (search for a taxon and then select it) and, while the cursor is still in the search box, you press enter. The chosen taxon disappears and results in:

I believe this is fixed. Would you mind trying it yourself to confirm?

Yup, looking good. Thanks!


Update localmedia version in package-lock to match riff-rtc

Summary
Updating this fixed screensharing for me in Linux/Ubuntu/Chrome.
Ticket Link
https://trello.com/c/QALL1fUK/229-bug-echo-is-screen-sharing
https://trello.com/c/GBx6UsgX/213-screen-sharing-add-feature-to-riff-edu

 Screen sharing: Add padding and text correction to Riff Edu.

rebased to head of develop


Game Page refactor

Ikay, i know i have way too many changes on single PR, but bear with this one please :) I had an avalanche of changes coming from trying to get the main game page back into shape.

fixes simulation performance regression by separating simulation from vue reactivity
some improvements were made to the game page layout and it's responsiveness

this includes general support for media query breakpoints in the layout attribute styles

app menu no longer refreshes the page when clicking on links
refactored speech bubbles to not require measuring the wrapping DOM node size

uses css instead, by assuming the relevant wrapper is an offset parent (position relative or absolute)

win condition logic is more stable and doesn't trigger again after clicking "go back"

win is now shown only after all simulation frames were shown (instead of stopping at randomly chosen fate in classical view)

soundtrack works again and doesn't layer itself multiple times on module hot reloads
fixes #141

Just checked your code, nice work with the CSS also the performance issues seem to be fixed.

It seems your rewrite of the "victory" gameState doesn't trigger the confetti / overlay when winning conditions are met. (ie: level 6, level 9)
The confetti animation doesn't stop sometimes
In encyclopedia, the top board doesn't allow cell rotation
In encyclopedia, the bottom board doesn't react to matrix mouseover and doesn't allow cell rotation.


Merge Test Branch jcw/upgrade_to_19 into Feature Branch feature/upgrade_to_19 for Integration Validation

Purpose
This pull request merges the changes from jcw/upgrade_to_19 into the feature/upgrade_to_19 branch. The goal is to test the integration of the feature updates in a staging environment before merging into the main (production) branch.
By merging into the test branch (feature/upgrade_to_19), we can:

Validate that the changes made in jcw/upgrade_to_19 are compatible with the current state of the production code (represented by the feature/upgrade_to_19 branch).
Run all CI/CD pipeline tests and verify build stability before moving these updates into production.

Changes Included
The key changes from jcw/upgrade_to_19 include:

Updates from the Azure TRE Deployment repo template
Updates to available workspace services - see v0.19.0 tag or .CHANGELOG.md for detail.

Process Overview

Merge jcw/upgrade_to_19 into feature/upgrade_to_19 to align the staging branch with the latest feature changes.
Run automated tests and perform any manual integration testing as needed. This will include manual testing from the UI to ensure user resources can be deployed successfully. As well as running through any TRE v19 breaking changes.
Once the tests pass and the merge is validated, feature/upgrade_to_19 will be merged into main for production deployment.

Considerations

Ensure that no conflicts arise during the merge.
Monitor the CI/CD pipeline for any issues in testing or integration.
Perform a thorough review of the changes to ensure everything works as expected before final deployment.

Action Required
Please review the changes, monitor the CI/CD results, and ensure all tests pass. This is a crucial step before merging the tested changes into main and deploying them to production.

Upgrading to v19.1 to pull in all required fixes.
All updates from v19 will be picked up and the merge from 18.7 to 19.1 will be tested


Extensions seem to get confused re Trusted Workspace

Type: Feature Request
So a couple of things that I think VS Code isn't so good at that perhaps it should be:

Per Workspace trust folders. The extensions seem to get confused on which workspaces they need to be poking around in if they think there are 'files of type' in the project because those files are found in one of the trusted directories under Workspace Trust. - This really sould reset for each Workspace, a saved workspace should know its folders and trust settings, and an unsaved workspace should be cleared of any and all folders excet those that are fairly explicitely shown to hold files pertaining to the current working project. (Perhaps even warn (or open in a new window) if the user is about to open a document outside of the workspace folders.

I feel like it would be fairly easy to allow the extension makers to add an informational field that VS Code could read and determine if that extension sould be active at all. (Yes, this can be abused, and yes, the user isn't always going to agree with the extension maker; however, you can still keep the existing override options.

Maybe I'm missing something but I can't seem to get source control to temporarily or otherwise disable. Sometimes it is quite annoying to have it running there. Say when you're using ng or npm update commands, it gives you a 'dirty git' error and doesn't let you proceed until you clear changes either by merge, stash, or push.

VS Code version: Code - Insiders 1.72.0-insider (a829fbb91cbae44afb6a389341a0763fb3a6ac6f, 2022-09-20T05:17:31.528Z)
OS version: Windows_NT x64 10.0.25201
Modes:
Sandboxed: Yes

@eshoberg, thank you very much for your feedback.

I have to admit that I am having difficulties trying to wrap my head around this feedback. This seems to be that it is being targeted towards specific behaviour from a specific extension. If that is the case, have you tried reaching out to the extension authors to provide them with this feedback?

Extension authors already have the capability to declaratively state their capabilities as documented in the extension authoring guide. Users are also able to override the extension capabilities using their user settings.

Source control is currently only enabled in trusted workspaces. If you would like to disable source control in a trusted workspace, you can open the "Extensions" view, search for "@builtin" and disable globally/per workspace the "Git" extension.


Bump vulnerable "cryptography" library version

Hi everyone,
We've started using your awesome lib, but getting issues with vulnerability checks for cryptography = "^41.0.5", as stated in here.

NULL pointer deference with pkcs12.serialize_key_and_certificates when called with a non-matching certificate and private key and an hmac_hash override (link)
Bleichenbacher timing oracle attack (link)

To resolve it cryptography version must be at least cryptography = "^42.0.4".
If anyone could bump it in pyproject.toml and poetry.lock files.
Thanks

Thanks, released in v1.8.2 :tada:
https://github.com/mblackgeo/flask-cognito-lib/releases/tag/v1.8.2


Set rootDir in tsconfig-base.json

Fixes #25810
The problem was that we copy src/services/tsconfig.json to build/local/typescriptServices.tsconfig.json. But when compiling from built/local, we'll get compile errors because the paths aren't in rootDirectory which defaults to options.configFilePath. These compile errors only happen when calling getCommonSourceDirectory, explaining why the change to utilities.ts uncovers it.
Note that when the change to utilities.ts is made but not the change to tsconfig-base.json, the error message is just Error: ENOENT: no such file or directory, open 'built/local/typescriptServices.out.d.ts' with no compile errors shown; but I've verifeid that removing the programDiagnostics.add call in checkSourceFilesBelongToPath made it work again.

@weswigham That extends tsconfig-base so it should inherit it?

Relative paths in the config are resolved relative to the config they were found in, though, right?


Sink/source verification during a global placement seems to fail on nets connected to pins

When running a global placement on my design, I get an error message (when fastroute is invoked apparently):
Initializing nets...
Checking pin placement...
Checking pin placement... Done!

----Checking sinks/source...
[ERROR] Net CLKIN has invalid sinks/source distribution
#Sinks: 0; #sources: 1
[ERROR] Net DBG0 has invalid sinks/source distribution
#Sinks: 0; #sources: 0
[ERROR] Net DBG1 has invalid sinks/source distributio

....
A testcase is available at https://github.com/rbarzic/issues-openroad. directory replace1. It should be self contained
I'm using Openroad, branch openroad  sha1 811dc2ff

Apparently it seems to be a regression as I was able to try the same example with an openroad version from April  (sha1 : 9183af4f) and I don't have error (It looks like some extra checks were added after this date)

Might be related to #395 (@MarceloDanigno ?)

I don't think this is related- #395 seems to be about TritonCTS. Here there is a check that has been added to check for partially connected nets but it seems to not take in account the case of a net connected to the pad window of an  I/O cell - Net will have only one connection to an instance in this case

@rbarzic Could you move this issue to FastRoute repository? It seems to be a wrong verification in FastRoute

@eder-matheus - Apparently, according to https://docs.github.com/en/github/managing-your-work-on-github/transferring-an-issue-to-another-repository, I may not have the right to transfert the issue myself


Set Leverage/Margin

Hey, interesting project! I've digged into it but i couldnt make it work with setting the leverage on the follower accounts... it should be actually just
    @authentication_required     def isolate_margin(self, symbol, leverage, rethrow_errors=False):         """Set the leverage on an isolated margin position"""         path = "position/leverage"         postdict = {             'symbol': symbol,             'leverage': leverage         }         return self._curl_bitmex(path=path, postdict=postdict, verb="POST")
right?
Would you be interested in adding this? Maybe with a LEVERAGE setting per follower individual?

im also interested in this

it is interesting to me too. Has anyone decided?

I solved it myself

how to solve it? Help me please

A calculator is needed so that trading transactions are copied in proportion to the balance.

Can I contact you in Telegram?

Can I contact you in Telegram?

@denisvk717

Can I contact you in Telegram?

How to find you in telegram?

@thiagob9
let me know also, how to find you on telegram


TimerError when using tokio-retry 0.2 with old tokio-core crate

Hi,
When running the second example (for the old tokio_core crate) in the documentation (https://docs.rs/tokio-retry/0.2.0/tokio_retry/#using-the-tokio_core-crate) I get a TimerError and no retries:
result Err(TimerError(Error(Shutdown)))

I don't really understand enough about tokio-timer to understand the error. Is there a step missing from the example?

Hi @df5602, what‘s the exact version of tokio-core that you‘re seeing this problem with?

I can reproduce locally now. It looks like this might be related to https://github.com/tokio-rs/tokio/issues/305, will investigate further later today!

I raised https://github.com/tokio-rs/tokio-core/pull/320 that should fix this problem!

Great, thanks a lot!

tokio-core 0.1.17 was just released which includes the fix, so I'm going to close this now. Please let me know how it works for you!
I've also added a test for the compatibility with tokio-core, to make sure we don't regress here.

Hi, works like a charm now, thanks a lot!


Install NodeJS (and NPM) before any NPM packages

This simple resource ordering statement makes sure that all NPM packages are installed after the whole NodeJS class finishes its work.

@tkocheran-chromeriver Out of interest can you provide some example code that would reproduce this problem? I'm surprised that this is happening, but then again I haven't written some beaker acceptance tests yet so...

class nodepackages {
    include ::node

    package { 'bower':
        provider => 'npm'
    }
}

Something like that ought to break it. What should get installed first? I don't think that Puppet automagically determines that it should install the provider (ie Class[node]) before the package with that provider. It could be that smart, but my experiences serve otherwise.

Clever idea, but I'm uncomfortable with the possible side effect that virtual packages are getting realized without intent nor any means of circumvention on the user's side.

I may be wrong, but shouldn't [pluginsync] (https://docs.puppetlabs.com/guides/plugins_in_modules.html) already do this automatically?

Only half of it. The provider will be there, yes, but it won't become suitable on the system until the node class has done its work.

Right but don't puppet resources defer if they provider isn't yet suitable? I agree with Frank that using a collector like this is not something a library should do because it will realize the virtual resources.

@ffrank What are virtual packages and why is this a bad practice?
As a user, with the following class:
class nodepackages {
    include ::node

    package { 'bower':
        provider => 'npm'
    }
}

I'd expect that since Class[node] provides the 'npm' provider, Puppet would install everything from that class first. A collector would ensure that this happens. What other options do I have? Should I as the user have to write a collector which should be provided by the provider?

@nibalizer good point about defered resources. @tkocheran-chromeriver can you provide an example that breaks without this patch?
Virtual resources:
class nodebase {
    include ::node

    @package { 'bower': provider => 'npm' }
}

Here the package is declared as virtual thanks to the leading @. This way, the different profiles that use the nodebase class can choose wether the bower package should be realized or not. One way of realizing it is the collector. If it's part of the node module though, this does not work because the virtual package is always realized.

Felix, I'm realizing that I don't have a good blog post or documentation to this exact issue. Do you know of anything or should I go ahead and write it up?

Could you? That would be splendid!

@ffrank, @nibalizer: also: refreshonly

I HAVE AN IDEA. HOW ABOUT MY PUPPET IN ANGER TALK BECOMES A LITTLE BOOKLET ON WORSE PRACTICES, ANTIPATTERNS, AND THE PAIN OF DEBUGGING

We're digressing, but yes, antipattern talks are always great.
Spencer, I'm not sure anymore what you are referring to. Will you write about resources defering themselves and how that works? I'll gladly do a bit about refresonly.
@tkocheran-chromeriver how would you feel about making this a README change, advising users to add the before override in their own manifests?

@igalic I ALSO HAVE ANGER IN PUPPET.
@ffrank That's fine. I probably just need to learn about all the new features in Puppet. Virtual packages, Hiera, all the new Puppet 3 stuff is still not known to me. I still just write hierarchies of classes, classes for roles, classes for profiles, defined types in Puppet lang, etc. This is probably largely my problem for not knowing more about all these new features.

Cool. What I also meant was - would you care to change your branch accordingly? I'd feel good about merging that then.

Is there anything to be contributed? My understanding thus far is that my pull request is unnecessary.

The manifest statement is useful for users, but shouldn't be part of the module code.
If you could at it to README.md as an advice to users, that would be most helpful.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116988

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117213

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117224

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117246

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117550

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117739

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117772

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118201

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119645


Jupyter kernel restarts when the ipynb file is renamed

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
When I rename a notebook I'm working in (by right-clicking the file in the left pane) the Jupyter server restarts. In JupyterLab you can rename a ipynb file while working on it and I expected the same behaviour in VSCode.
VS Code Version
1.69.2
Jupyter Extension Version
v2022.6.1201981810
Jupyter logs
No response
Coding Language and Runtime Version
Python 3.9.2
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Thanks for the bug.
Do you mean the kernel is restarted?
That would make sense the way VS code is structured. The kernel is tied to the document, renaming the document destroys the old one, hence killing the kernel.
We should probably (at least in the rename case), not kill the old kernel.
This is related to #1378

Yes, the kernel restarts.
I really like the way VSCode ties kernels to files, since this makes my workflow much easier (I don't have to start a server to to write a quick notebook that I'll delete soon afterwards). But the renaming scenario should be handled in a better way. A warning message would probably suffice.

The problem here is, the active kernel is not switched from one notebook to the other, hence the old kernel id destroyed and a new one started for the newly renamed notebook.

Duplicate of https://github.com/microsoft/vscode-jupyter/issues/8215

Blocked on https://github.com/microsoft/vscode-jupyter/issues/9517 as we need a way to connect a notebook to an active notebook kernel.

@roblourens @rebornix  do you think we can have some kind of event that would help Jupyter extension determine whether the user renamed a notebook from x.ipynb to y.ipynb, once we have that we can try to keep the same instance of the kernel for the user.

Can you use vscode.workspace.onDidRenameFiles for this?

Closing again as I agree with the duplication of #8215. I'll transfer over the info in the comments.

@IanMatthewHuff I'd like to keep this open and sepearate from #8215
They are different.

With #8215, we want to ensure the same kernel is selected,

E.g. assume you have kernel A selected with notebook X.ipynb.
Now the notebook is closed, and you rename the file.
We need to ensure when you open the renamed file the kernel points to A.
Similar even if the notebook is opened (but user has not executed any cells)

This issue pertains to keeping the active kernel session insteaad of disposing it

That requires a bit more work, its not the same as selecting the right controller.
We need to ensure we select the same active kernel session, not just the controler, as selecting the controller will not address this issue, as the kernel state would be lost.
& this requires work to be done in the kernel layer to ensure we can transfer the kernel from one resource to another. Today a kernel and a notebook have a 1-1 relationship and changing that requires a bit of work, that can be done completely independant of the first issue (i.e. independant of issue#8215)

I've assigned this to you and me, as we'll need to work on this together. As it touches both kernel picker as well as kernel state/execution layers.
THis PR https://github.com/microsoft/vscode-jupyter/pull/10573 will be required to resolve the problem described in this issue

Closing this issue for now as this hasn't been reported anyone else for over a year,
Closing as out of scope for now.

Is this issue truly fixed? I still lose my section when the file is renamed.

Hey, I have been having the same issue and just found this thread. Usually it is a minor problem, but sometimes when I decide to turn a quick and dirty notebook into something more permanent (thus renaming it) and when having cells with longer computations, the workflow gets broken and re-running everything can be a bit of a waste of computational resources

Reopening as @minsa110  has been running into this a few times


There is a problem during fine tunning.

I made the data in the same format. and try fine-tunning
using below code
python train.py  --gradient_clip_val 1.0 --max_epochs 50 --default_root_dir logs  --gpus 1 --batch_size 4 --num_workers 4
However, at about 10% of the training, I got the below error.
and On the second try, it happened at 5%.
Is it a data problem?
The data contains the text string in ['news'] and the summary string in ['summary'].
Traceback (most recent call last):
File "train.py", line 233, in
trainer.fit(model, dm)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 552, in fit
self._run(model)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 917, in _run
self._dispatch()
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 985, in _dispatch
self.accelerator.start_training(self)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 92, in start_training
self.training_type_plugin.start_training(trainer)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 161, in start_training
self._results = trainer.run_stage()
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 995, in run_stage
return self._run_train()
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1044, in _run_train
self.fit_loop.run()
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 111, in run
self.advance(*args, **kwargs)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/loops/fit_loop.py", line 200, in advance
epoch_output = self.epoch_loop.run(train_dataloader)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 111, in run
self.advance(*args, **kwargs)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/loops/epoch/training_epoch_loop.py", line 118, in advance
_, (batch, is_last) = next(dataloader_iter)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/profiler/base.py", line 104, in profile_iterable
value = next(iterator)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/supporters.py", line 672, in prefetch_iterator
for val in it:
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/supporters.py", line 589, in next
return self.request_next_batch(self.loader_iters)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/supporters.py", line 617, in request_next_batch
return apply_to_collection(loader_iters, Iterator, next_fn)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/utilities/apply_func.py", line 96, in apply_to_collection
return function(data, *args, **kwargs)
File "/opt/conda/lib/python3.8/site-packages/pytorch_lightning/trainer/supporters.py", line 604, in next_fn
batch = next(iterator)
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 435, in next
data = self._next_data()
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1085, in _next_data
return self._process_data(data)
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1111, in _process_data
data.reraise()
File "/opt/conda/lib/python3.8/site-packages/torch/_utils.py", line 428, in reraise
raise self.exc_type(msg)
TypeError: Caught TypeError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 198, in _worker_loop
data = fetcher.fetch(index)
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 44, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/opt/ml/git/KoBART-summarization/dataset.py", line 43, in getitem
label_ids = self.tok.encode(instance['summary'])
File "/opt/conda/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2104, in encode
encoded_inputs = self.encode_plus(
File "/opt/conda/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2420, in encode_plus
return self._encode_plus(
File "/opt/conda/lib/python3.8/site-packages/transformers/tokenization_utils_fast.py", line 455, in _encode_plus
batched_output = self._batch_encode_plus(
File "/opt/conda/lib/python3.8/site-packages/transformers/tokenization_utils_fast.py", line 382, in _batch_encode_plus
encodings = self._tokenizer.encode_batch(
TypeError: TextEncodeInput must be Union[TextInputSequence, Tuple[InputSequence, InputSequence]]

There was a problem with the data!


[Issue]: trying to run Ollama docker on WSL2 with 7900XTX but no "/dev/kfd" folder

Problem Description
I can confirm that I have installed the ROCm and PyTorch on WSL correctly (according to the official document and this: https://github.com/ROCm/ROCm/issues/3563), as all post install checks are passed (rocminfo command works and pytorch retuen "True" for checking CUDA). but when I run "docker run -d --device /dev/kfd --device /dev/dri -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama:rocm
", it says "ERROR:  /dev/kfd no such file or directory".
However I have came across this issue: https://github.com/ROCm/ROCm/issues/3734, so I substitute "--device /dev/kfd" to "--device /dev/dxg", it still cannot recognize the GPU and run the model on CPU. But if I just installed the .exe from Ollama official website, that one does utilize the GPU.
And I have also came across to this: https://github.com/ollama/ollama/issues/5275, which it basically says it is expected to have no directory called "/dev/kfd" by following the instructions, but I haven't try the poster's method for fear that the system would break. So is this a recognized issue and will be fixed in future or I am doing something wrong?
P.S. I am sorry that I have deleted all the setups because it got me frustrated, but I will do this again and post the log of not finding the GPU here shortly after.
Operating System
Ubuntu 22.04.5 LTS (WSL2) / Ubuntu 24.04.1 LTS (WSL2)
CPU
Ryzen R7-7700X
GPU
AMD Radeon 7900XTX
ROCm Version
ROCm 6.2.3 / ROCm 6.1.3
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response

I will try to provide as much information as possible, so here is the results of step 1 in the official document:

Hi @Henry715, thanks for reaching out! Getting Ollama working in WSL docker is going to be a little bit complicated.
First, please follow Option: B of this guide to get docker with ROCm running on WSL. In addition to mapping /dev/dxg, the instruction also helps you to map a couple core ROCm libraries.
However, this does not fully help with getting Ollama to run because it stills looks for kfd explicitly under the hood. Hence, You might want to follow these instructions in order to override this behavior.
Hope this helps. Please do not hesitate to reach out if you have any additional questions.
Cheers!

Hi @Henry715, thanks for reaching out! Getting Ollama working in WSL docker is going to be a little bit complicated.
First, please follow Option: B of this guide to get docker with ROCm running on WSL. In addition to mapping /dev/dxg, the instructions also helps you map a couple core ROCm libraries.
However, this does not fully help with getting Ollama to run because it stills looks for kfd explicitly under the hood. Hence, You might want to follow these instructions in order to override this behavior.
Since the modifications are mainly going to be focused on the Ollama code, I wouldn't be too worried about breaking anything in the system.
Hope this helps. Please do not hesitate to reach out if you have any additional questions.
Cheers!

Sure, I will definitely try those. If I installed the docker container with Pytorch, does that mean I should run Ollama in that Pytorch Docker container rather than using that Ollama:ROCm official docker image?

Sure, I will definitely try those. If I installed the docker container with Pytorch, does that mean I should run Ollama in that Pytorch Docker container rather than using that Ollama:ROCm official docker image?

First of all, Ollama doesn't depend on PyTorch. The error occurred because it expected the normal AMD driver to be installed, which in WSL is not.
ROCm (and CUDA) in WSL use custom tricky libraries (a.k.a. libdxcore.so) to redirect instructions to the host, which is why Docker --device=/dev/dxg -v /usr/lib/wsl/lib/libdxcore.so:/usr/lib/libdxcore.so -v /opt/rocm/lib/libhsa-runtime64.so.1:/opt/rocm/lib/libhsa-runtime64.so.1 will enable (PyTorch in) ROCm in Docker in WSL. As a result, there is no driver running in WSL, which provides the files needed by Ollama.
There is a temporary but simple solution (I don't know when they will merge this):

https://github.com/ollama/ollama/pull/6201

Just build and run it like this:
# clone
git clone https://github.com/evshiron/ollama
cd ollama
git checkout rocm-wsl-support

# build
go generate ./...
go build .

# when building is completed

# start service
./ollama serve

# start client
./ollama run phi3


flink cdc sqlserver全量+增量不锁表

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

加1

Follow this pr https://github.com/ververica/flink-cdc-connectors/pull/1222

我需要全量这部分数据，只增量不会锁表的

增量快照目的就是为了全量阶段无锁，并且可以并行读取
具体原理可浏览文档以及相关博客
https://ververica.github.io/flink-cdc-connectors/master/content/connectors/mysql-cdc(ZH).html#a-name-id-001-a

source = sqlserver  不是mysql

cc @GOODBOY008

只是增量也会锁表的吧 @zjialin

这个逻辑在全量跟增量的时候都会走这段逻辑

This is duplicated to #1570 and #1212 . Let's discuss in these issues.
Close this issue.


feat: create save search mutation

The type of this PR is: Feature
This PR resolves FX-2971
Description
As an admin,
When I toggle the on/off switch on the saved search banner
A new searchCriteria and userSearchCriteria are created in Gravity
With the exact combination of filters I have selected in the UI
Acceptance criteria:

Toggling the switch "on" executes the mutation
For the purposes of this ticket, it's sufficient to check that the searchCriteria and userSearchCriteria were created using a console
Not in scope: handling failure
Not in scope: preserving banner "on" state on reload/reapplication of same filters
Not in scope: deletion of previously saved searchCritera on toggle off

Demo
https://user-images.githubusercontent.com/3513494/120678920-4917b000-c4a1-11eb-8042-5fb55b7ee6b3.mp4
https://user-images.githubusercontent.com/3513494/120678945-50d75480-c4a1-11eb-9afb-42cd2a8044d5.mp4

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

Do you think we should convert the input to the new format (nested under attributes / attribution > attributionClasses) within this PR?

Converted input to a new format

#squashongreen

Thank you 😀✌


Dynamically changing debugFreezeFrame can cause issues on large tilesets

What happened?

I wrote a sandcastle to illustrate the logic of what I'm doing, but I don't have access to a large model so this sandcastle may not reproduce the problem, it's just to illustrate what I'm doing
Reproduction steps
Since large models will reload distant tiles when the camera moves, this will cause serious FPS drops and cause the model to move lags, so I enable frame froze when the mouse is pressed and disable frame froze when the mouse is released. However, this error appeared when I moved the model repeatedly many times.
Sandcastle example
https://sandcastle.cesium.com/#c=xVTbitswEP0VEfoggyunZJdCmoQuubCBtLs06ebF0JXlSSIqS0aSHZIl/175lngvfSgUVi/2jGbOnDnSiClpLMo57EGjIZKwR2MwPEvIQ+nDYYeV9lhJS7kEHXZ89BRK5JYFrZ2v36SsKptstErWSou4dmDPD+XJ+xLKUFp9aNJZWdtyAQasK073lNsGq/r0Jqtqu8ScK3ljnDGP8efr3lXvTKRYIGkkYAJRtl1zDRtNE+gjqzPwq6CSQPFTdUsMAwkk1TzhludgCI1jXLNpQmuTxAXsWAml+RFKSo5vgV321AI9KpWsFL7QqhH8i6el8S3QmMvtPbds94PKLeAu6froY5dc++fakcpkEbVMd6CBaJeSGRSgK9L1aljvTKPSdEdlLF4e6JJpALlMKYNpDtLeVkH4mRyMypyaC16NRArVZZrZG2a5khh7aDhqq/9MqJkrdIRZcQIXmcoj8P9GZnVIgSyms9Wvyd36+3+tv6HC/AuBn/fv1P63+WSymL6rADWFRoITYtRdTYTdHCvttQdXCSBCbfHjtNhCQpU3uaHRRx+eypzTY4F06vidgbEHAaOG8VeepEpblGmBCQksJKmgFkwQZey364MZ0wzhIGinDmKeIx4P33iYEBPUGLezyYRYukkNO6NB4OJfpdZ073LQgh6KsN2n0aJyEkIGgTPfzrRKiYjqF8h/AA
Environment
Browser: electron 25.2.0
CesiumJS Version: 1.120
Operating System: win11

Hi @BlockCnFuture, thanks for the report!
This property is for debugging only; it is not optimized for production use.
Strictly speaking, yes, this is a bug. But since it appears to be a corner case of a debugging feature, we are unlikely to provide a fix ourselves so I'm going to close the issue.
However, if you are interested in contributing a fix, we would be happy to review a PR!


Helper

Trading the framework's easy config() method for this service plus method plus parameters seems a downgrade. I would like to see a helper that could also handle dot syntax:
setting('App.baseURL', 'http://example.com');
echo setting('App.baseURL');

While I don't think that config('App')->baseUrl is all that different than setting('App', 'baseUrl'), I think dot syntax would be welcome. Only potential problem is that then users would want to be able to do config('App.baseUrl') :)


Asterics symbol not allowed in function args

When running refactor over the following code:
    def __init__(self, *, foo):
        self.foo = foo

I get:
AttributeError: 'NoneType' object has no attribute '_fields'

Can you share the Rule for this?

Yes, sorry.
This is the rule. And this is the file I am trying to "refactor".

@feluelle Could you try adding assert node.decorator_list below line 20?

Hey, @isidentical I found the bug, I'll open a PR.


Put Handler in the CoroutineContext

See AuthUser example behind the link below:
https://github.com/Kotlin/kotlin-coroutines/blob/master/kotlin-coroutines-informal.md#coroutine-context

Done


Add txt partition table parser

Summary
A text format partition table stored in last eraseblock.
The 1st line must be "Magic+Version", current is "TXTABLE0".
The 2nd (and belows) is/are partition entry/ies, in format: "%s %zx %zx"(means name, size and offset(byte)(in hex))
Size or offset can be default zero(means zero(only for 1st entry) or caculate), and will be caculated ref to previous and next entries.
The last eraseblock will be registered as pseudo partition named "txtable".
To avoid problems of PTABLE: In case of multiple NuttX binary, partition table maybe out of sync.
And is more eaiser:

Text format with simple rules(name + size + offset).
Size or offset can be default(caculated refs to previous and next entries).
Support backup table(eg. /etc/txtable.txt in ROMFS)

Size / Offset can be automatically calculated, case:

The offset of the first entry is zero, and the offset of other entries is zero: automatic calculation;
The size of the last entry is zero: fill to the end of the entire Flash (keep the last eraseblock); the size of other entries is zero: automatically calculated(next.offset - current.offset);
Typical case 1: The size of all entries is zero (calculated automatically), and the offset is non-zero;
Typical case 2: The size and offset of a certain entry are all zero, but the size and offset of two adjacent entries are all non-zero;

Impact
Disabled by default.
Testing
1. Both size and offset are zero, and not reserve last eraseblock
txtable.txt
TXTABLE0
partition1 0x6C000 0x4000
partition2 0x10000 0x70000
partition3 0x80000 0x80000
partition4 0x80000 0x100000
partition5 0x280000 0x180000
partition6 0x80000 0
partition7 0x10000 0x480000
data 0xb00000 0x500000

Parsed
Reserved last eraseblock, and gap between partition7 and data is kept.
（name + offset + size:)
 > /dev/partition1, 0x4000, 0x6c000
 > /dev/partition2, 0x70000, 0x10000
 > /dev/partition3, 0x80000, 0x80000
 > /dev/partition4, 0x100000, 0x80000
 > /dev/partition5, 0x180000, 0x280000
 > /dev/partition6, 0x400000, 0x80000
 > /dev/partition7, 0x480000, 0x10000
 > /dev/data, 0x500000, 0xaff000

2. More than one not set size or offset
txtable.txt
TXTABLE0
partition1 0x6C000 0x4000
partition2 0 0x70000
partition3 0 0x80000
partition4 0 0x100000
partition5 0x280000 0x180000
partition6 0x80000 0
partition7 0x10000 0x480000
data 0 0x500000

Parsed
Size of partition[2,3,4,6] and data are caculated, and gap between partition7 and data is kept.
 > /dev/partition1, 0x4000, 0x6c000
 > /dev/partition2, 0x70000, 0x10000
 > /dev/partition3, 0x80000, 0x80000
 > /dev/partition4, 0x100000, 0x80000
 > /dev/partition5, 0x180000, 0x280000
 > /dev/partition6, 0x400000, 0x80000
 > /dev/partition7, 0x480000, 0x10000
 > /dev/data, 0x500000, 0xaff000

3. Only one partition entry, and size not spec
txtable.txt
TXTABLE0
partition1 0x0 0x4000

Paresd
The last eraseblock was kept, and size is correct.
 > /dev/partition1, 0x4000, 0xffb000

4. Blank line && New line delim
txtable.txt
New line: CR + LF  /  LF
TXTABLE0
partition1 0x6C000 0x4000
partition2 0 0x70000
partition3 0 0x80000
partition4 0 0x100000
partition5 0x280000 0x180000
partition6 0x80000 0x400000
partition7 0x10000 0x480000
data 0 0x500000

Parsed
Blank lines are ignored, and new line of both "LF" or "CRLF" are parsed.
 > /dev/partition1, 0x4000, 0x6c000
 > /dev/partition2, 0x70000, 0x10000
 > /dev/partition3, 0x80000, 0x80000
 > /dev/partition4, 0x100000, 0x80000
 > /dev/partition5, 0x180000, 0x280000
 > /dev/partition6, 0x400000, 0x80000
 > /dev/partition7, 0x480000, 0x10000
 > /dev/data, 0x500000, 0xaff000

@JianyuWang0623 please move the content of your Summary to some documentation at Documentation/
It will be more useful there because here it will be "lost" after the PR is merged :-)

@JianyuWang0623 please create a new PR for documention.


Add test to ensure that .NET spec stays in sync with JSII spec

Json.NET supports generating json schemas from .NET types.
We should write a test that generates a json schema from Amazon.JSII.JsonModel.Spec, and compares it to the schema generated by jsii-spec.

While we're at it, we should move Amazon.JSII.JsonModel.Api into Amazon.JSII.Runtime (because it isn't used by Amazon.JSII.Generator), and rename jsii-dotnet-jsonmodel/Amazon.JSII.JsonModel to jsii-dotnet-spec/Amazon.JSII.Spec.

@RomainMuller how does this fit into the current work on the JSII spec and the compliance suite. Seems like we could do this in addition but most of what it verifies would already be covered. Seems like another relatively inexpensive to implement layer of verification though.

To be frank it might be sweet to get that code-generated from the JSON Schema or something. Manually keeping in sync is busy work that does not add much value.

Lets link this to development of the greater DotNet compliance suite. We can look into automating this with the rest of the compliance tool set we build.


[Question] how to use wave with cert-manager for http certs

How can i use the wave operator in order to use it to renew the letsencrypt certs generated by cert-manager?
I currently deploy cert-manager using helm, so if i add the annotation wave.pusher.com/update-on-config-change: "true" on the deployments will that be sufficient for wave to restart the pods of the deployment?

I currently deploy cert-manager using helm, so if i add the annotation wave.pusher.com/update-on-config-change: "true" on the deployments will that be sufficient for wave to restart the pods of the deployment?

If that deployment uses the certificate then probably yes. Cert-manager will renew the cert and your deployment will be restarted with the new cert. If you are using any ingress controller (such as nginx-ingress) this is likely not needed at all.


Add fields required to support self-managed certificates

Description
When programmatically managing self-managed certificates, i.e. by requesting the /verify endpoint in code, the caller needs needs to know the values of the origin domain name and the cname-api-key header to set up the reverse proxy correctly. This change simply adds those two fields to the CustomDomain struct.
References

auth0/terraform-provider-auth0#118

Testing

[ ] This change adds test coverage for new/changed/fixed functionality

Checklist

[x] I have read and agreed to the terms within the Auth0 Code of Conduct.
[x] I have read the Auth0 General Contribution Guidelines.
[x] I have reviewed my own code beforehand.
[x] I have added documentation for new/changed functionality in this PR.
[x] All active GitHub checks for tests, formatting, and security are passing.
[x] The correct base branch is being used, if not main.

Tests will fail cuz this is coming from a fork but they pass locally:

We'll try to open these for forks as well soon, but there's some work we need to do first.


Unmarshal empty strings as strings instead of null

Empty string values ('s:0:""') within an array are being unserialized to null, this change will unserialize them to "" instead.

recreated at https://github.com/leeqvip/gophp/pull/18/commits due to an extra commit getting included in this pr.


custom 'updatedAt' ignored

sails version: 0.11.0
i configured in the model:
updatedAt: {
type: 'datetime',
defaultsTo: function (){ return Math.round(new Date().getTime() / 1000); }
}
but its continue insert json date value.

Try with this model setting:
autoUpdatedAt: false

More info here: http://sailsjs.org/#!/documentation/concepts/ORM/model-settings.html

Now it's not updated because its disable the auto action.

in the model.js file:

beforeUpdate: function(values, next){
     values.updatedAt = Math.round(new Date().getTime() / 1000);
     return next();
}

Does this help? http://stackoverflow.com/a/24562385/291180

It's just the same solution that I said. It works fine, I think that we can close this issue.


Shrinking for choose and chooseNum considers invalid values

For a property like
property("chooseNum") = forAll(chooseNum(0, 10))(n => 0 <= n && n < 10)

Shrinking will settle on -1 instead of 10, and it even considers several out-of-range values during shrinking.  From my gut feeling I'd think this is a bug.

Please see the discussion here: http://groups.google.com/group/scalacheck/msg/b563f24c81b22291
This is a known pitfall, and I intend to do something about it in issue #8, if possible.


Refactor of ApiCompat Task

Changes

Add build script.
Add eslint as prebuild script.
Add TypeScript as devDependency.
Change the structure of project to use ./src folder for .ts files and ./lib folder for .js files.
Fix lint issues.
Fixes in the format of some files.

Test

NOTE: I use this guide to debug the task.

I debugged the code with VSCode and use:

./Tasks/ApiCompat/source as a root directory.
The following launch.json configuration.

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "program": "${workspaceFolder}\\lib\\index.js",
            "env": {
                "INPUT_CONTRACTSROOTFOLDER":"C:\\Projects\\southworkscom\\SOUTHWORKS-azure-pipelines-tasks\\Tasks\\ApiCompat\\tests\\4.2.2",
                "INPUT_IMPLFOLDER":"C:\\Projects\\southworkscom\\SOUTHWORKS-azure-pipelines-tasks\\Tasks\\ApiCompat\\tests\\4.3.1",
                "INPUT_CONTRACTSFILENAME":"Microsoft.Bot.Builder.dll",
            }
        }
    ]
}

And I got the following results

Thank you for these changes @enzocanoo.
I just tested it on Azure Pipelines and it works, :shipit:

@enzocanoo can you change your PR base to the ApiCompat/release/0.2 branch, please?

@ParadoxARG done!


Workaround for Nim's moveFile() issues on MacOS

Nim's os.moveFile() would fail to move files on MacOS Big-Sur 11.2 and
fail with the "operation not permitted" error. There are two underlying
issues:

Big-Sur's extended file attributes like the followings that mark
files downloaded from the internet:

com.apple.quarantine
com.apple.metadata:kMDItemWhereFroms

As long as these attributes are there, MacOS 11.2 prevents
moveFile() to function properly. This is worked around by invoking
xattr -d on the attributes mentioned above.

However it seems even after the extended attributes are removed,
moveFile() still tends to fail. This is worked around by using the
POSIX compatible "mv" utility.

This patch was tested on two separate machines both running MacOS 11.2
with the Firefox Nightly 87.0a1 and Tridactyl 1.20.4pre5209-34b0fce4,
and everything seems to work on MacOS 11.2 so far.
Hope this helps. Thank you.

Sat Feb  6 09:05:32 GMT 2021
Hi - don't forget to update the  version.

@rprimus
Just sent a new PR #26 with bumped version to 0.2.3.
I see that you have #24 with 0.2.2. Hopefully both can be merged. Thanks.


use with feathersjs

Hello,
I would like to use this plugin with feathersjs.
the connection with feathers works, but when using it with the @feathersjs/authentication-client plugin, I run into the following issue.
At some point it calls the following function:
const socketUpgradeHandler = () => {
      socket.io.engine.on('upgrade', () => {
        debug('Socket upgrading');

        // If socket was already authenticated then re-authenticate
        // it with the server automatically.
        if (socket.authenticated) {
          const data = {
            strategy: this.options.jwtStrategy,
            accessToken: app.get('accessToken')
          };

          this.authenticateSocket(data, socket, emit)
            .then(this.setJWT)
            .catch(error => {
              debug('Error re-authenticating after socket upgrade', error);
              socket.authenticated = false;
              app.emit('reauthentication-error', error);
            });
        }
      });
    };

But then it says "TypeError: Cannot read property 'engine' of undefined"
So I guess,  the engine is not defined at  socket.io.engine.on.
Any clue?

Simply put an empty eventemitter to fix it
(<any>socket).io = {
    engine: new EventEmitter()
}

socket.on('connect', function() {
    (<any>socket).io.engine.emit('upgrade')
})


TestContainers 1.6 is not using the dockerImageName in the code

Hi,
I'm trying to use TestContainers to test a NodeJS application in a docker container. I have created a container for it and I'm trying to use it in my test as this:
@ClassRule public static GenericContainer redis = new GenericContainer("css/ldap-server:latest")                     .withExposedPorts(1389);
If I run docker images I get this:
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
css/ldap-server     latest              b31725ccf479        19 hours ago        681MB
node                carbon              46f2857af80b        32 hours ago        673MB
bsideup/moby-ryuk   0.2.2               a27283338f1b        8 weeks ago         9.31MB

But the image that I get running is the bsideup/moby-ryuk   0.2.2 one. This is in the logs:
POST /containers/create?name=testcontainers-ryuk-44f26548-e88d-4585-ac6c-1e76540fa2db HTTP/1.1
Any clue what I'm doing wrong here?
Thanks a lot

Hi @csigueros,
This is a special container we start to keep watching your containers and kill them once you stop your tests. It is super thin and doesn't add too much to your resources consumption. Both LDAP server and ryuk will stop shortly after your tests' execution.
FYI next TC version will use quay.io/testcontainers/ryuk image :)

Thanks, but I still can't see my container running...
Anything else I should check?

Forget it....I have it working now. I found some complete usage examples and it seems I wan't calling the start method on the container in the beforeTest method.
It works great now!!!

@csigueros 👍
yes, you have two call .start() if you're not using the JUnit Framework and it's Rule/ClassRule integration.
Happy to know that it works for you 🎉
I'll close the issue since it's solved, but feel free to report if you discover something else :)


Don't fire CNI installer watch events unless Istio binaries are changed.

The CNI agent copies CNI binaries to well-known paths on the node, where the CNI subsystem in use will invoke them, if configured.
It then starts a file watch on those paths, and re-copies the binaries if changes are detected, as a self-healing mechanism.
However, the current code watches the entire destination directory for change events, not just the Istio-owned files that are copied there - this makes the Istio CNI plugin slightly poorly behaved if other CNI plugins are in the chain, in that Istio's watcher will uselessly fire if non-Istio binaries are copied to the same spot, causing it to redeploy the binaries even if they are unchanged.
This PR changes that behavior so that the watcher only watches the binaries it actually installs in the destination path, rather than everything in the destination path, which is arguably bugged behavior.

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
1b395cdf2d6a46b82499fcab1e1d4d57cf2f2a31
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
1b395cdf2d6a46b82499fcab1e1d4d57cf2f2a31
link
true
/test integ-ambient

gencheck_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
1b395cdf2d6a46b82499fcab1e1d4d57cf2f2a31
link
true
/test integ-ambient

gencheck_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test gencheck

unit-tests-arm64_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
1b395cdf2d6a46b82499fcab1e1d4d57cf2f2a31
link
true
/test integ-ambient

gencheck_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test gencheck

unit-tests-arm64_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests-arm64

lint_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test lint

unit-tests_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test gencheck

unit-tests-arm64_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests-arm64

lint_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test lint

unit-tests_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests

integ-ambient_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test gencheck

unit-tests-arm64_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests-arm64

lint_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test lint

unit-tests_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests

integ-ambient_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-ambient

integ-operator-controller_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-operator-controller

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test gencheck

unit-tests-arm64_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests-arm64

lint_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test lint

unit-tests_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test unit-tests

integ-ambient_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-ambient

integ-operator-controller_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-operator-controller

integ-cni_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test gencheck

integ-ambient_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-ambient

integ-operator-controller_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-operator-controller

integ-cni_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-cni

unit-tests-arm64_istio
3b8ccc51e76f8ce1548fd16af965b6588df1594f
link
true
/test unit-tests-arm64

unit-tests_istio
3b8ccc51e76f8ce1548fd16af965b6588df1594f
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
a49701ae9525dbb085b7fe425fc9889f3e13ce50
link
true
/test integ-cni

unit-tests-arm64_istio
3b8ccc51e76f8ce1548fd16af965b6588df1594f
link
true
/test unit-tests-arm64

unit-tests_istio
3b8ccc51e76f8ce1548fd16af965b6588df1594f
link
true
/test unit-tests

integ-ambient_istio
3b8ccc51e76f8ce1548fd16af965b6588df1594f
link
true
/test integ-ambient

integ-operator-controller_istio
3b8ccc51e76f8ce1548fd16af965b6588df1594f
link
true
/test integ-operator-controller

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-pilot

integ-security_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-pilot

integ-security_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-security

integ-pilot-multicluster_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-pilot

integ-security_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-security

integ-pilot-multicluster_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-pilot-multicluster

integ-security-istiodremote_istio
e9966ffb92a8959a7b88b9624dfc2b4a806145d2
link
unknown
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


question

what is collapse key as you have mentioned in the example?

collapse key is used to "collapse" an older notification of the same collapse key.
For example, if I have a package tracking app and a package status is modified to IN TRANSIT, then, DELIVERED. The only information that matters to be in a notification is the last one. I can use the same collapse_key for both, so when the DELIVERED notification arrives, if the user haven't seen the IN TRANSIT the OS will replace the older notification with the newer one.

Additionally, this lib is becoming strongly deprecated and I do not intend to keep the support for it any further, please use the official firebase sdk for node.


Fix failing com.fsck.k9.mail.MessageTest

I've just started looking at the K-9 source, and it looks like a recent commit (e3593a1) breaks the class com.fsck.k9.mail.MessageTest in k9mail-library/src/androidTest.
Here's my fix, to remove the static modifier on MimeMultipart.generateBoundary() that was added in that commit.

Thanks! I ended up using a slightly different approach to fix the issue.
https://github.com/k9mail/k-9/commit/8b99095aff11462b395f12be53b82f9b4b3bb314


getLeavesWithProofsByNamespace:could not retrieve node

Celestia Node version
v0.9.2
OS
mac/linux
Install tools
No response
Others
No response
Steps to reproduce it
This is from running a rollup and the full logs can be found here
Expected result
shares are retrieved, no error
Actual result
ERROR   ipld    ipld/namespace_data.go:216  getLeavesWithProofsByNamespace:could not retrieve node  {"nID": "\ufffd\ufffd\ufffdy\ufffdq\u0016\ufffd", "pos": 0, "err": "context canceled"}
Relevant log output
No response
Notes
No response

Seeing this occur on v0.11.0-rc1 of node:
ERROR	ipld	ipld/namespace_data.go:216	getLeavesWithProofsByNamespace:could not retrieve node	{"nID": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0008\ufffd\ufffdy\ufffdq\u0016\ufffd", "pos": 0, "err": "context canceled"}

@walldiss, @distractedm1nd, seems like we cancel ShrexND and move to IPLD and then it also gets canceled

cc @tuxcanfly


df: remove obsolete "show_listed_fs" options field

The field show_listed_fs in the Options struct seems to be obsolete as it is always set to false (except in a test).

Makes sense!


Require opt-in for subdomain matching

This fixes #998.  An argument can be made that this should actually land in
Werkzeug instead.  Question is if we want a new release for this or not.
Can be worked around in Flask for now.

Rebased against master, squashing commits. Overall looked good, I mostly just moved things around.

Use subdomain arg in url_map.bind_to_environ rather than resetting it afterwards.
Rename the new test to be more descriptive.
Parametrize the new test instead.
Test the use case described in the issue, which was allowing subdomains when server name is set. (Still tests IP too.)
Add subdomain_matching param to docs, add some references, add version changed to create_url_adapter.


[Release] sdk/resourcemanager/netapp/armnetapp/0.1.0

…spec commit: 4cda81c5daed78441aa8043dd32ae00b02899c36

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run prepare-pipelines

/azp run go - armnetapp - ci

/check-enforcer override


First character in terminal output is displaced sometimes

I'm on Debian Stretch, using rxvt-unicode as my terminal.
In certain situations, the first character of a line gets displaced - it ends up at the far right of my terminal, on the previous line. Look at the right edge of this screenshot:

we're aware

Ref #1574 so people searching for that issue can find this one.


chore: release main

:robot: I have created a release beep boop
0.4.0
0.4.0 (2024-07-23)
⚠ BREAKING CHANGES

deps: bump github.com/linode/linodego from 1.36.0 to 1.37.0 (#78)

Bug Fixes

deps: bump github.com/linode/linodego from 1.36.0 to 1.37.0 (#78) (55483e1)
deps: bump google.golang.org/grpc from 1.64.0 to 1.65.0 (#77) (1c0f21e)
deps: bump the otel-dependencies group with 7 updates (#75) (a46020b)

Miscellaneous Chores

updated license notice (#83) (ee38174)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/linode/linode-cosi-driver/releases/tag/v0.4.0 :sunflower:


Sign out doesnt work with Remember me

Hi!
At first I want to thank you for wonderful admin panel, MotorAdmin is really the best!
Though, I have small issue with logging out users with enabled devise rememberable option.
After adding Rememberable option to AdminUser, sign out button doesn't actually sign out, just redirecting to main page.
And then when I visiting /motor_admin again Devise doesn't ask for password (I presume that it restore session from remember_me token).
It looks not secure as user may think that he logged out, but actually he left active AdminUser session.
Without Rememberable it works perfectly though.
For now I will just not use "remember me" option for AdminUser, but it would be handy to have it and be able to have control on AdminUser sign out.

@Napishite thanks for reporting this - it has been fixed in the latest release:
https://rubygems.org/gems/motor-admin/versions/0.3.17


Milestone: Project setup

In this milestone:
I have setup webpack and linters

Approved project! ✅ 🥳 🎈 🎉🎉🎉🎉🎉🎉🎉🎉
Hi there,
Your project is complete! There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.


pwsh as a dotnet global tool doesn't accept any parameter

Steps to reproduce
On Linux, install PowerShell global tool as per the blog post from the PowerShell team:
https://devblogs.microsoft.com/powershell/introducing-powershell-as-net-global-tool/
dotnet tool install --global PowerShell

Then run, from bash:
pwsh -c Get-ChildItem
pwsh --version

Expected behavior
The global dotnet tool works as a regular pwsh install, so, to run a command, you would run:
pwsh -c Get-ChildItem

And the output would be successful.
Actual behavior
Both will fail. AFAIK any command with an argument will fail. This is what I get when I run the first one:
-Command : The term '-Command' is not recognized as the name of a cmdlet, function, script file, or operable program.

And the second one:
Missing expression after unary operator '--'.                                                                                At line:1 char:3                                                                                + --version                                                                                +   ~~~~~~~                                                                                Unexpected token 'version' in expression or statement.

Also, if you run without -C (or -Command), it works, which is not expected:
pwsh Get-ChildItem

Environment data

Name                           Value
----                           -----
PSVersion                      6.2.2
PSEdition                      Core
GitCommitId                    6.2.2
OS                             Linux 4.4.0-18362-Microsoft #1-Microsoft Mon Mar 18 12:02:00 PST 2019
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

This is running on WSL on Ubuntu 19.04.

I believe this is a broader issue from #10301.

/cc @adityapatwardhan


Get the php-cs-fixer.phar per release

Hi!
Is there a way of getting the php-cs-fixer.phar per release? I've seen in the releases page we have the source code, which is nice, but It would be nicer If we could also have the phar built in the release, a unique url to the php-cs-fixer.phar file to download.
Thank you!

You can download the newest stable version from site.
If you want specific version use composer.

@keradus I can't just use composer If I want to package It for Nixpkgs.
What would be the best solution then?

@keradus a solution could be to attach the phar as an additional file in the github releases. This is what we do in Behat for instance

That's the solution in phpcs and how I created the package for It.
It might not seem a big deal, but It could be helpful since the installation process would be faster and well versioned.


Styling individual elements in a GridMatrix is ignored by datashade operation

The following code tries to set the background and frame colors of one plot in a GridMatrix:
def modify_frame(plot, element):
    print('modify_frame')
    plot.state.outline_line_color = 'blue'

some_dataset = hv.Dataset(np.random.normal(size=(10000, 3)), [chr(65+i)+'_dimension' for i in range(3)])
gd = gridmatrix(some_dataset)
gd['A_dimension', 'B_dimension'].options(finalize_hooks=[modify_frame], bgcolor='lightyellow', clone=False)
gd.map(datashade, hv.Scatter)

but there's no color changes, and no output from the print() in modify_frame. It seemed that modify_frame was not called. If the last line was gd or gd.map(decimate, hv.Scatter), the code worked as expected. Somehow datashade 'eats' the options?

I think this is a specific case of the issue in https://github.com/ioam/holoviews/issues/2637 .  I agree it's confusing, and I'd really like to find a solution.

As @jbednar points out this is a duplicate of #2637, so I'll close. For now the correct thing to do is to apply the plot options after datashading.

@philippjfr Applying the plot options after datashading still has no effect:
gd = hv.operation.gridmatrix(some_dataset).map(hd.datashade, hv.Scatter)
gd['A_dimension', 'B_dimension'].options(finalize_hooks=[modify_frame], bgcolor='lightyellow', clone=False)
gd

Interestingly, the plot options are set and can be seen if only that plot is shown:
gd['A_dimension', 'B_dimension'].options(finalize_hooks=[modify_frame], bgcolor='lightyellow', clone=False)

will show a plot with lightyellow background and blue frame. But when the plot is shown together with other plots in a GridMatrix with gd, the plot options are lost.

It's possible to use these tools without having to think deeply about how it all works, and we try to facilitate that where practical, but sometimes you have to appreciate all of the details, especially if you want to control them.  Here., Datashader returns transparent images, which will reveal the background color of the plot the same as if you hadn't used datashader.  But datashade() controls the foreground color, so you have to pass that to the datashade() operation if you want to change that.  And datashade() also changes the plot from being a point plot to an RBG plot, so options that apply to points aren't relevant after datashade().  You can use more of the usual styling mechanisms if you use rasterize() instead of datashade(), where Bokeh controls the assignment of colors and Datashader is only responsible for the rasterizing/aggregating step. If you do use rasterize(), and are aware that it turns the data into an hv.Image() and apply options suitable for an Image, you'll probably be able to achieve what you want.

Thanks @jbednar. The same issue happens when I use rasterize(). I played with the code a bit more and the result is even more puzzling.
I understand I'm dealing with RGB elements after datashade(), and should apply options for RGB. RGB elements have the bgcolor and finalize_hooks options, and those options are indeed applied (see picture in my last comment) if I only show that RGB element by
gd['A_dimension', 'B_dimension'].options(..., clone=False) # works

The plot options are not set when I try to set the options of one plot and then show the whole gridmatrix in one cell:
gd['A_dimension', 'B_dimension'].options(..., clone=False) # doesn't work
gd # doesn't work

The modify_frame function I passed to finalize_hooks is not even called in this situation (because no output from the print() in the function).
More puzzling is if I put the following three lines in three separate cells, everything is fine, the plot options are applied

gd['A_dimension', 'B_dimension'].options(..., clone=False)
gd['A_dimension', 'B_dimension']
gd

But if I put 1) and 2) in the same cell, and 3) in a separate cell, then the plot options are not applied at all

Hmm.  That doesn't sound like it's behaving properly, to me.  @philippjfr?

Might be hard to test without a runnable reproducing example.

@jbednar This is the code I used in the screenshots, run in jupyter lab or notebook environment.
def modify_frame(plot, element):
    print(element)
    plot.state.outline_line_color = 'orange'
    plot.state.outline_line_width = 8

some_dataset = hv.Dataset(np.random.normal(size=(10000, 3)), [chr(65+i)+'_dimension' for i in range(3)])
gd = hv.operation.gridmatrix(some_dataset).map(hd.datashade, hv.Scatter).map(hd.dynspread, hv.RGB)

gd['A_dimension', 'B_dimension'].options(finalize_hooks=[modify_frame], bgcolor='lightyellow', clone=False)
gd['A_dimension', 'B_dimension']
gd

Thanks, that makes it much easier. That is indeed strange behavior.


networking.go tweak iptables functions

Took duplicated code and merged it into the helper function so only a single
exec was executed.
Signed-off-by: baude<EMAIL_ADDRESS>

LGTM

@rh-atomic-bot r+

Gitvalidation errors on Homu

@rh-atomic-bot retry

@rh-atomic-bot r+

@rh-atomic-bot r+


Unable to create or list functions in Minikube

minikube version
minikube version: v0.20.0
kubectl version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"clean", BuildDate:"2017-05-19T18:44:27Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"dirty", BuildDate:"2017-06-22T04:31:09Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
kubeless function deploy get-python --runtime python27 --handler test.foobar  --from-file test.py
--> FATA[0000] the server could not find the requested resource
kubeless function list
--> FATA[0000] the server could not find the requested resource
However on the k8s dashboard, kafka, zk and kubeless controller have been started. Function also appears as a thirdpartyresource.

@fouadsemaan I commented on #192 Please check to see if it solves the problem

@fouadsemaan I just made a new release. Please upgrade  https://github.com/kubeless/kubeless/releases/tag/0.0.16

Thank you @ngtuna
I didn't expect the quick turnaround!


NBD connection disconnected during upgrade

You can replicate the same error. The steps to producing this error is -

Start up a server with debian 7.8 image
Login via ssh
perform apt-get update
perform apt-get upgrade

The system never successfully completes the apt-get upgrade but always ends up with a fatal error.
Setting up libxml2:armhf (2.8.0+dfsg1-7+wheezy4) ...
Setting up ntp (1:4.2.6.p5+dfsg-2+deb7u4) ...
[ ok ] Starting NTP server: ntpd.
Setting up ntpdate (1:4.2.6.p5+dfsg-2+deb7u4) ...
Setting up nbd-client (1:3.2-4~deb7u5) ...
Stopping NBD client process:
umounting filesystem from /dev/nbd0...
umount of /dev/nbd0 failed! Data loss may occur! will continue in 10 seconds...9 8 7 6 5 4 3 2 1 ok, going on...
/dev/nbd0
Disconnecting /dev/nbd0
Disconnecting /dev/nbd1
Disconnecting /dev/nbd10
Disconnecting /dev/nbd11
Disconnecting /dev/nbd12
Disconnecting /dev/nbd13
Disconnecting /dev/nbd14
Disconnecting /dev/nbd15
Disconnecting /dev/nbd2
Disconnecting /dev/nbd3
Disconnecting /dev/nbd4
Disconnecting /dev/nbd5
Disconnecting /dev/nbd6
Disconnecting /dev/nbd7
Disconnecting /dev/nbd8
Disconnecting /dev/nbd9
libkmod: ERROR ../libkmod/libkmod-module.c:1802 kmod_module_get_holders: could not open '/sys/module/nbd/holders': No such file or directory
Error: Module nbd is in use
nbd-client.
Starting NBD client process: Connecting...Activating...
nbd-client.
insserv: fopen(.depend.stop): Read-only file system
debconf: DbDriver "config": could not write /var/cache/debconf/config.dat-new: Read-only file system
dpkg: error processing nbd-client (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up openssl (1.0.1e-2+deb7u17) ...
dpkg: unrecoverable fatal error, aborting:
unable to flush updated status of `openssl': Read-only file system
E: Sub-process /usr/bin/dpkg returned an error code (2)

Probably fixed with https://github.com/scaleway/image-debian/commit/6bb08d29d6c14f503e74e1d96f071e2a3aa6072c but not yet in production
I will try to add something to block the xnbd-client package to be installed to avoid this kind of problem

Hello, same problem on ubuntu wordpress image. How you can upgrade to new  image when image is already setup ?

This issue should be fixed with the new initrd, @aimxhaisse can you test and validate ?

Yes, this is fixed in recent distribution, we don't ship the NBD client anymore.


Importing single icon to a project adds 227kb of overhead in a build

Do you want to request a feature or report a bug?
Seems like a bug but could be user error with how it is being imported.
What is the current behavior?
When an icon is imported into a project, all icons are being included in the build. This adds approximately 227kb of total overhead to a project even when only 1 icon is being used.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

What is the expected behavior?
To only include the icons that are imported.
Which versions of MDL, and which browser / OS are affected by this issue? Did this work in previous versions of MDL?
"@masonite/svg-icons": "1.2.0"

I don't know the exact solution, but it is related to tree-shaking https://webpack.js.org/guides/tree-shaking/
When doing a production build, webpack should remove unused imports. We use CRA for most things and while I need to do more research, I don't think CRA eliminates dependencies of dependencies.
You can see someone has the same approach as we do here. Not sure if solved, need more research:
https://github.com/facebook/create-react-app/issues/6943#issuecomment-565860478
I am in favor of making multiple SVG packages if the combined approach of the CRA method and our/FA method nullifies tree-shaking in CRA

I am pretty sure the problem is because the project is bundled. The bundle exports all of the icons as strings, but the strings are in the bundle. I think if this were to be packaged with the index.js referencing the dist/svg would solve it. Thinking back, this may have been what I was trying to do, but wasn't able to achieve it.
I think we would need to remove svg-inline-loader and use 'file-loader'. I may have a fix soon.


Clarification on the format of input data

Hi,
Thank you for this awesome software! I am recently exploring peakVI. One thing came to my mind and I wish to clarify this with you. I am aware that the input data is AnnData format, and it is a sparse matrix. My question is: is this constantly a sparse matrix even when it is processed and inputted into the neural network and outputted from the decoder?
Yours sincerely,
Siqi Shen

No. We convert it into dense data before passing it into the network (see AnnTorchDataset for the source code).
The output of the networks is a matrix of distribution parameters estimated by the network. It is not sparse.

Just to add to what Valeh said, only minibatches of data are dense, so not all the data at once is made dense.


What would it take to bundle ffprobe?

I'm just familiarizing myself with go-astilectron, sorry if this is an easy question. Thanks for doing this project! I'm looking forward to using it and contributing.

@TableMountain There are 2 difficulties regarding ffmpeg and ffprobe in this project:

We have to make sure it's present in the execution environment
We have to make sure our app point to the right path

Your question is clearly 1) but 2) shouldn't be ignored in this case.
Now back to your question. There are 2 options:

either we bundle it outside of go-astilectron. Which means the binaries are not embedded in your final GO binary and we simply add a download step before running the bootstrap that will download the proper binary based on the OS/arch couple and place it where it should be.
either we find a way to adapt the bundler so that this step is part of its process and the binaries are embedded based on the OS/arch couple

Does that make sense?


C# wrapper does not have a wrapper for DialogueResponsesMenu

Describe the bug
The DialogueResponsesMenu from the GDScript version does not have a C# wrapper.
Affected version

Dialogue Manager version: v2.41.4]
Godot version: N/A

To Reproduce
Steps to reproduce the behavior:
Open a C# file in a project that has the addon enabled. Notice that there is no "DialogueResponsesMenu" when using the DialogueManagerRuntime.
Expected behavior
The C# wrapper contains a class for DialogueResponsesMenu.
Screenshots
N/A

I'm happy to write and submit a PR for this if there are not already plans for it. I wanted to write an issue first to make sure there aren't any specific reasons for it not being there yet.

Closing this since it seems more like a feature request based on my reading of the C# example balloon. It would be nice to have C# equivalents, but at least for myself I'll probably write some helper functions or my own components.


Go to definition problem.

Type: Bug
Issue Description
I know, this issue was reported so many times  and I had look others but can not resolve my issue so please help me.
I work on some framework project, which has several big cs project in an single solution.
my working environment is ubuntu 20.04
Solution load very well. I can see all the projects in the solution.
go to defintion works very well in an single csproject.
but they cannot find the definition out of their project even though it is in the same solution.
Funny part is,
It cannot find the definition of System classes such as Dictionary, List, etc.
I tried latest version and pre-released version but both have same problem.
when we use Omnisharp, this was works very well, but after Dev Kit, it all broken.
Steps to Reproduce
After Load Solution,
Go to Definition only works in single csproj,
others can not find the definition.
Expected Behavior
should find definition well in same solution classes, or system classes.
Actual Behavior
Not works.
Logs

C# log
Post the output from Output-->C# here
C# LSP Trace Logs
Post the output from Output-->C# LSP Trace Logs here.  Requires `dotnet.server.trace` to be set to `Trace`
Environment information
VSCode version: 1.88.1
C# Extension: 2.26.13
Using OmniSharp: false
Dotnet Information
Host:
Version:      8.0.4
Architecture: x64
Commit:       2d7eea2529
RID:          linux-x64
.NET SDKs installed:
No SDKs were found.
. If so, can you please update the issue description with the C# log from the Output pane?

Ive got the same issue on Windows 10

Unfortunately this isn't actionable without the additional requested information.  Closing this issue.  If you're still having problems, please reopen this issue and include the following details:

Check that the solution explorer shows the solution with the expected projects.
Set dotnet.server.trace to Trace in vscode settings, reload the window, then Attach the 'Projects' output window logs and 'C#' output window logs so we can diagnosis what is going wrong.


Create CODEOWNERS

cc @Etiene @mcalhoun

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.


Drop Kubernetes 1.19 and add 1.22

Proposed Changes

Drop k8s 1.19 and add 1.22

Release Note

Drop support for Kubernetes 1.19.

/kind removal
/assign @matzew

/hold

/retest

Blocked by https://github.com/knative-sandbox/knobots/pull/108

/retest

/retest

/unhold

/lgtm
/hold
Feel free to unhold it if anyone from eventing side feels it is good to go.

/unhold


Functionality for Explainable Graph Neural Networks?

Hi!
Are you going to add functionality for the interpretation of GNN models to torchdrug?
There are benchmarks datasets Benchmarks for interpretation of QSAR models
and there is a whole bunch of different methods Explainability in Graph Neural Networks: A Taxonomic Survey.
Unfortunately, I haven't seen a method which directly combines explainability and uncertainty quantification (like evidential deep learning).
That would be really helpful for our medicinal chemists to understand why a decision was made by a model und how certain the model is about the decision.
Thanks

Hi! We are aware of the importance of explainable models in biomedicine, and we have considered it as a part of our future plan. Unfortunately, due to the limited manpower we have now, such feature may not be realized very soon. Thanks for your understanding.


feat(uip-editor): store editor state (POC)

Closes: #617

There are three small but critical points to accept this feature:

As a consumer (Dev) I should be able to disable the feature
As a user I expect to have a saved state for the exact playground instance (it will be very inconvenient if I found an example of lately opened component A when I open a page for component B that utilizes UIP as well)
As a user (without deep knowledge) I should be able to reset to the snippet state (especially when there is no uip-snippet plugin)

To resolve mentioned problems I recommend the following action items:

Rework model to use store ONLY IF the store-key declared on uip-root
The store uses key store-key to identify the instance (it prewets any inconsistent sharing of the state)
(Optional) We can propose a special keyword for user (e.g. PAGE) to use current full page pass to be used as a store key
TECH NOTE: the exact browser storage root key should still be identified with uip- prefix
Implement a reset button (for the plugin heading section) available for the editor plugin


Problem with \MT@maybe@textcmd

Building some (not all) known-good documents may generate an error, stating that \MT@maybe@textcmd is undefined. If I persist with build, the resulting PDF looks OK.
Engine: lualatex. Texlive 2022, all up-to-date. Issue happened with MT 3.1, also 3.1a from here.
It seems that \MT@maybe@textcmd is defined within the \leftprotrusion macro. Does not seem to matter whether or not I turn protrusion off. I can fix the problem by placing this code immediately after \begin{document}:
\makeatletter
\let\MT@maybe@textcmd\@firstofone
\makeatother

Since the problem does not occur for all documents in my document class (novel), I cannot write a "minimal" document illustrating the issue. However, if you have novel with its docs, look in doc/lualatex/novel/extras for document novel-testsuite.tex. It built without problem two months ago, but generates the MT error now.

As you say, \MT@maybe@textcmd is defined within \leftprotrusion, and it is only called by commands that \leftprotrusion itself calls, so I don't see how it could possibly be undefined.
Anyway, this is impossible to debug without a MWE (which is always possible to create) or at least more info: what is the exact error message? what is in the line the error message refers to? could you double-check whether microtype.sty and microtype-luatex.def have the same version? could you post the log file?

PS: I've just compiled your novel-testsuite.tex and did not get any errors.

Ah. Thanks for compiling novel-testsuite.tex. Now I know that the problem does not lie with my document class or with that file, or with microtype. I do get the error with that file, even if I remove the images and other frills. Yet I do not get the error on some files using novel, and do not get the error with another custom document class that loads many fewer packages than does novel.
About two days ago, while updating via tlmgr, it told me to use a different repo. So I did. Everything now says it is up to date. My suspicion is that there may have been a cross-repo incompatibility in some other package. Evidently I had the bad luck to update just as TeX was freezing 2022. So, this look like I need to do a TeX system debug on my device.
Or, as they say in the world of TeX error messages, Expected a number. You entered 0. If you continue, will substitute 0.
In expl3 syntax, that is __aw_foo_bar.
I will shortly close this issue.

Today, I removed and reinstalled texlive 2022 (the parts I use) from scratch. Now all is good. I conclude that, as I guessed above, there was a repo sync problem when I updated. Whatever package was incorrect, did not emerge from its cage until it interacted with microtype, and only under some circumstances. Such is TeX.
Over at tex.stackexchange.com, user egreg looked at this yesterday, but could not discern anything. I removed that post.


[IOTDB-3796] Throw exception while using without null clause in MPP

see IOTDB-3796.

Coverage decreased (-0.02%) to 44.967% when pulling 75a6917749cfa13a56d245b1747b81c13adac61b on lmh/removeWithoutNull into 1b81a2b41e6b3bf15829de2d6fb7fe27fd7b248d on master.

Before:

After:


Allow Cargo.toml as configuration source

Due to a GitHub mishap in #754, this is a new PR containing the same commits (rebased by @Emilgardis). Just for reference, it still addresses #657.

can you squash the commits also?


risc-v/esp32c3: fix pwm driver bug

wrong offset sign and pwm multichan bug
Summary
Impact
Timer0 6 channel output works now, but other timers still do not.
Testing

The macOS is failing for all PRs, I will ignore it and merge your PR


Add 'New File' to dashboard

Hi :) I like your plugin a lot, sometimes I need to quickly get a clean buffer, so I added this small change.

Thanks . merged.