Yes.

python
reader = neo.RawIO()
reader.parse_header()

in this example the reader will have the memmap for all streams, but to actually pull out the data you need to specify which stream of data you want. I would actually say that spikeinterface is nicer in that it can be fed with name, whereas all the functions at the rawio level expect the stream index. So you run into the issue that if you don't know the IO it isn't clear how to get what you want

ie how do you get digital data for intan -> you need stream_index = 3. So you basically need to look in the header to see which stream goes where. Again Intan has good names in the header, but it seems like Plexon says streams are Signal 0 and Signal 1 which aren't super helpful.


Yes, we probably should have better signal streams in plexon but I we will need someone who actually has experimental experience with the format to venture in that direction.


Thanks, I wonder if the values of the bandpass are fixed or something that people decide at run time.


Adding support for this as well. This would be a great addition!


Followed this ticket and now it works in Browser but not in JMP... Weird, maybe it just needs time to update?


能否支持Win11新版右键菜单的系统分享？
Can the system sharing of the new right-click menu of Win11 be supported?
image


Hi @Tienisto
I believe that this issue was fixed and is part of v1.15.0
However, I do not see the context menu entry


@tahayparker you need to start the app at least once, optionally there is a setting hidden under the "advanced" toggle where you can enable context menu.
Also, LocalSend is available under "Send to" not as an share option in Windows 10/11


POC for the interim solution: URL This will make it possible for anyone to implement a solution in a way that accommodates their unique `keyFormat` syntax without having to modify the actual code.

I plan to join the community call tomorrow to hear from Google about the proposed target-state solution of storing logs as output artifacts.


i see, i had disabled the "send to" as i didn't need it
would it be possible to create the entry in the "main" context menu rather than in the "send to" submenu?


Thanks for reporting this. I shared the issue on the mailing list: URL

We reached the quota limit on PyPI and I am waiting for the quota to be increased in order to upload the missing wheels for 3.8, 3.9 and source distribution. The issue on PyPI to track the quota increase is this one: URL


I have the same issue staring from Vscode release 1.86.2 and for all releases after that.
Unfortunately my issue #205440 has been closed without fix.

BUT ISSUE STILL EXISTS.


Hello @raulcd :wave:
I've set the project limit for `pyarrow` to 40 GB on PyPI. Please be mindful of the frequency of releases at that size.
Have a nice week! :snake:


The missing wheels and source distribution have been uploaded to PyPI.


I am very happy to finally close this issue as all the PRs mentioned here have finally been merged!
I would like to thank @adjs and everyone who contributed to this enormous effort!
Feel free to open new issues and PRs with further synthesis algorithms for MCX with or without ancilla qubits if you think that they may be better than the current code.


If this happens because of UniTask, another way to handle this is to convert it `ToUniTask`, and then `Forget` it , like `myGameObject.transform.DOLocalMoveY(1, .5f).SetEase(Ease.InBack).ToUniTask().Forget();`


Possibly related to the new tests introduced in URL Do you know if these tests should be disabled or same changes are needed for them to work on Apple mobile targets? @stevejgordon @tarekgh ?


Similarly to URL likely related to the new tests introduced in URL affecting only x86 Android emulator at the moment. Do you know if these tests should be disabled or same changes are needed for them to work on x86 Android emulators? @stevejgordon @tarekgh ?


@matouskozak I'd say it's best and safe to disable these on the affected platforms.


@matouskozak I think we can safely skip this platform in the runtime metrics tests.


Thank you, would you like to open a PR to disable them or should I take a look?

Do you know if this is an issue that should be fixed on the Mono runtime side or is it by design of the test? It looks like only a few tests are failing so I suppose the `RuntimeMetricsTests` suit isn't CoreCLR specific.


Unfortunately we didn't have time for this in 7.3.0 either -- @tjgq has been occupied by other work. This may need to wait until 7.4.0 or even 8.0.

We do have rolling releases, which are cut every ~2 weeks. But I'm not sure if this feature in particular is ready for even preliminary testing.


Just to add a +1 to the tailscale discussion - I did not have this issue at all prior to installing tailscale, and now have it any time a rebuild needs to restart NetworkManager.


As background, ollama API calls (and CLI prompts via `ollama run`) that don't specify a context length, use a context length of 2048 tokens. If you need more context, you either need to specify that in the API call or change the default. `options = {"num_ctx": 120000}` is the canonical way to do that, if it's not working that's a bug and it would be great if you could send server logs demontrating this issue. Adding `{"role": "user", "content": "/set parameter num_ctx 120000"}` to an API call will not change the context window because `/set parameter` is interpreted by the CLI (`ollama run`), which is not involved in inference during an API call.

To change the default context window of a model and so do away with having to add `options` to an API call, you need to create a new model. This is easy to do and if you follow the instructions, does not require more disk.

First, get a copy of the current modelfile:

ollama show --modelfile mistral-nemo > Modelfile

Now edit the file and do two things:
1. Where it says `FROM` and a long file path, change the file path to the name of the model.
 eg, `FROM /root/.ollama/models/blobs/sha256-b559938ab7a0392fc9ea9675b82280f2a15669ec3e0e0fc491c9cb0a7681cf94`
 becomes `FROM mistral-nemo`
2. Create a new line in the file and add `PARAMETER num_ctx 120000`

Create the new model:

ollama create -f Modelfile mistral-nemo-120k

Verify the change in default context length, check num_ctx under paramaters:

 $ ollama show mistral-nemo-120k
 Model
 arch llama
 parameters 12.2B
 quantization Q4_0
 context length 1.024e+06
 embedding length 5120

 Parameters
 num_ctx 120000
 stop "[INST]"
 stop "[/INST]"

This should solve your context problem, if it persists please follow up with server logs.


The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.

Happy Coding!


this should be mentioned somewhere in the documentation, if not already.


You also set a context length for a model in open-webui. Go to Workspace > Models > Create a model, choose the base model, scroll down to Model Params and under Advanced Params, set the context length.


Thank you for your response! I've also discovered another bug. When I add "options": {"num_ctx": 32000} to the `/v1/chat/completions` endpoint, it doesn't take effect and the context length remains at 1k. This option works correctly on the `/api/chat` and `/api/generate endpoints`.


Probably because the OpenAI API doesn't support specifying the context window, just `max_tokens`. So yes, that would be an appropriate feature request for ollama.


@clyring unless there is some progress by the end of August, I'll have to close the proposal as abandoned.


A bit more information is needed. If you supply a server log (`docker logs `) it can be checked for truncation messages. It would also be useful to see the actual HTTP request that open-webui is sending. Unfortunately that's not logged, so a tool needs to be installed to capture that:

$ docker exec -it apt install -y tcpflow
$ docker exec -it tcpflow -c 'src port 11434 or dst port 11434' > ollama-open-webui.log

Run this, use open-webui for a long context conversation, ^C tcpflow, remove any PII from the log, and add it here.


Bumping this. It's been over a year since this last message:

How's the looking going?


@jstjoe With the current limit that we have in place (stack=30) most of the use-cases should not be having this issue. But if you have this issue occurring where even for a property that is not very nested and you receive this error, let us know and we can look into it.

As for exposing this option in App, It seems allowing this option could cause many potential issues due to sheer amount of collection size that few definitions that are imported can generate. We've seen collections getting generated that are more then 500 MB to even 1 GB in such cases. Due to this, we've made decision to allow such generation only from usage of module directly.


Here is a user-submitted solution for fixing the community rating value. We normally expect a float, but some models will send an int. URL


@JosielSantos16 Além de criar uma nova página para redirecionamento individual de cada horóscopo de signo a partir da página principal de horóscopo, é necessário corrigir os espaçamentos entre os componentes e ajustar as fontes.


Fiz a implementação dessa tela e das outra e subi os commits, estou esperando a revisao


If GraphRAG start's using Microsoft's own agent library AutoGen, supporting different model providers would not need to be re-implemented here.

LLM Configurations docs for AutoGen


Optimistically marking this ticket as resolved. We've since moved to Alloy and URL indicated a similar issue has been resolved.

Feel free to re-open if there are still outstanding issues or alternatively open a new ticket that is specific to your situation.


@JosielSantos16 Revisei os o código puxando para meu ambiente dev, esta muito bom as correções. Um ponto de atenção seria colocar mais detalhes de onde foi corrigido na tarefa, tipo imagens mostrando a correção e o erro de estilização referentes a cada pagina corrigida.


@JosielSantos16 a revisão dessa tarefa esta na tarefa de integração #32


Correção de estilo concluída e integrada à branch develop.
feature da tarefa: Feature/correcao estilo


Marking as `resolved` as I think it is likely resolved or, if not, will be handled by other tickets detailing specific issues with individual chains or configurations

Feel free to re-open if this is still an issue we should address


I put up a PR (#49) to support SSO auth using the new method. It works on my machine :tm:


Hi @sudomain I am working on allowing users to configure key layout. Instead of a file, I have added a small UI to customize keys.

Test APK: URL
Go to `Settings => Input => Virtual Keys => Customize keys` to make changes.


For the UnoCSS part, a similar solution to this one, URL used in Slidev could be used? This could help to simplify the DX and the starter.


@chris-31337 , "prompt_eval_count" refers to the actual length of the processed prompt, which is 934 in your ollama-open-webui.log, meaning only the last 934 tokens were used as the prompt. Didn't you modify the modelfile as suggested? It worked for me after I made the changes. Also, is this screenshot from openwebui? I haven't seen this option before.


From ollama-docker.log:

INFO [update_slots] input truncated | n_ctx=2048 n_erase=19335 n_keep=4 n_left=2044 n_shift=1022 tid="133210613727232" timestamp=1722942601

From ollama-open-webui.log:

have ever known."}],"options":{},"keep_alive":"15m","sess

There's no `num_ctx` in the `options` field, so the input text of ~21k tokens is being whittled down to 2048 by throwing away 19335 of them. What version of open-webui are you using? I'll fire up a docker container with it and see if I can replicate.


how about using a single node and pp size 2 ( so that it uses multiprocessing backend)? does it still have this issue?


I just tested it, but the bug appears there as well:
Setup C) one docker container with 2 GPUs (pipeline-parallel, no ray)

docker run ... vllm/vllm-openai:v0.5.4 --model "meta-llama/Meta-Llama-3.1-70B-Instruct" --tensor-parallel-size 1 --pipeline-parallel-size 2 --max-model-len=4096

again the incomplete response:

{
 "id": "chat-28622b0c3d074caead37fb5441ca2407",
 "object": "chat.completion",
 "created": 1722964614,
 "model": "meta-llama/Meta-Llama-3.1-70B-Instruct",
 "choices": [
 {
 "index": 0,
 "message": {
 "role": "assistant",
 "content": "",
 "tool_calls": [
 {
 "id": "chatcmpl-tool-9dfa147ec16245d7a8efd67ddfc6012f",
 "type": "function",
 "function": {
 "name": "get_current_weather",
 "arguments": "{\"location"
 }
 }
 ]
 },
 "logprobs": null,
 "finish_reason": "stop",
 "stop_reason": null
 }
 ],
 "usage": {
 "prompt_tokens": 251,
 "total_tokens": 254,
 "completion_tokens": 3
 }
}


I really appreciate everyone who looking into this, and I left comments in the design doc.

I am in a similar boat as @ittaiz and trying to help a 100-person company improve their build infrastructure. Having a default local cache, with GC, enabled by default, is all very valuable for Bazel in this environment. I was also surprised that it doesn't already work this way.


I solved this, as you only need to add "min_tokens": **. I set it to 50 due to my completion length.


@Lyndon-Li I don’t understand; there’s nothing related to my current issue.


Here is the error associated to the partially failed backup:
`"message": "found a dataupload velero/media6-fj8fl with expose error: Pod is unschedulable: 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.. mark it as cancel",`


@Lyndon-Li You have no idea

`"message": "found a dataupload velero/media6-fj8fl with expose error: Pod is unschedulable: 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.. mark it as cancel",`

 why this issue occurred, and the error message displayed does not provide a solution. The issue #7898 lacks any description for resolution. Is it possible that the problem lies in my installation steps or elsewhere? Any guidance to help resolve this issue would be appreciated.


There is no resolution/workaround, you have to wait the release of 1.14.1 or you need to downgrade to 1.13.x


@Lyndon-Li This means that the issue

`"message": "found a dataupload velero/media6-fj8fl with expose error: Pod is unschedulable: 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.. mark it as cancel"`,

did not occur in version 1.13.x, and my backup process was executed using the --snapshot-move-data flag, correct?


@Lyndon-Li Following your suggestion, I used version 1.13.2. After installing it and attempting to back up with the --snapshot-move-data flag, the backup status completed without any errors. However, the snapshot data was not moved as expected. I also checked the MinIO S3 bucket, and there was no Kopia folder created for the snapshot backup. In short, this is not meeting my requirements. Do you have any solutions related to this issue?

Screenshot_754
Screenshot_755
Screenshot_756
Screenshot_758
Screenshot_757
Screenshot_759
Screenshot_760
Screenshot_761

Here is the related bundle file:
bundle-2024-08-07-15-23-09.tar.gz


For Velero prior to 1.14, you need to add CSI plugin in installation if you want to use data mover feature.


@Lyndon-Li I'm encountering this error related to volume snapshots and classes, even though I've already defined them in my namespace.

Screenshot_762
Screenshot_763
Screenshot_764
Screenshot_765

Here is the related bundle file:
bundle-2024-08-07-17-03-56.tar.gz


@jayrajmeh0 You're using version 0.1.1 of the CSI plugin. For Velero 1.13 you need 0.7.x.


If you know the zigbee command it would be doable via the console. Sadly i don't know the command.


@Barbapapazes Thanks for the pointer! This `mergeConfigs` function from `unocss` seems to be what we're looking for 👀


I did some investigation, the problem is quite deep. In the case of guided decoding we are using _stateful_ logits processors. However, in PP, the logits processors will get cloned when sent to the workers other than the driver workers. This is ok for the TP use cases since the logits processor is not cloned and the state lives as long as the sequence group does. This is an issue for beyond PP however, and will affect anything SPMD. For those cases though, one solution might be to have the logits processor live on the worker. Pinging @njhill as this is quite similar to the seed issue and he might have some suggestions on the best way to resolve it.

MP GPU Executor, [ ]
Rank: 0, [ ]
(VllmWorkerProcess pid=2199329) Rank: 1, [ ]


How can I acquire the command? What was your method for decoding the Zigbee data? Thank you very much.


Should we implement:

 URL

instead of still using Pelican's metadata? Or should we mark this as blocked until #291 is done?


I wouldn't say this is a bug - it was documented to behave this way: URL


Yes, I agree. Feel free to categorize it appropriately.

Overall to me, it seems to just sort of defy the normal idea of scope. Top level scope is a different thing. Like I said above, I don't think it is that unusual to have more than one app in the same package.

I like the typed arguments but I'm wondering if this will cause others troubles too, when the whole idea was to make things easier with less boilerplate.


I think we need to overhaul logits processor part. it should not be a part of sampling parameter.

sampling parameter should just store the constraint, like regex or json schema. and the constraint decoding state (i.e. FSM state) should live in each sequence. The FSM itself, with masks for every state, should be retrieved from some cache that maps from regex to FSM.


Yes exactly

Yup agreed

We can keep the FSM as part of logits processor but map from sequence to FSM in the worker similar to torch Generator. Ideally this is done in a clean and future-proof way.

@rkooo567 You mention support for guided decoding in URL Is this something you're looking into?


not exactly, but to make it work with SPMD, I believe we need exactly the same solution. So I may look into it soon. URL


We can do this without doing #291. Doing this is very easy. Doing #291 is much more work.


also totally agreed with @youkaichao. I think that's the direction we should go (and what we wanted to achieve with URL


Yes @rkooo567 I think a lot of the stuff from SPMD is basically directly the same for PP.


I'm not sure if we want to change this behaviour, effectively breaking backwards compatibility... And I'm not even convinced if having multiple functions annotated as `@main` in a single codebase is even a good idea. But I see what you mean, there definitely would be a usecase.

As a middleground what I'm thinking is, maybe it'd be sufficient to improve the warnings to make this predictable?
What I mean is, for this example:

scala
package baz

object Bar {
 @main def main(): Unit = println("main Bar")
 @main def bar(): Unit = println("bar Bar")
}

We currently (3.6.0-RC1-bin-20240807-54344a1-NIGHTLY) warn like this:

scala
[warn] ./repro.scala:3:8
[warn] Generated class baz.Bar differs only in case from baz.bar.
[warn] Such classes will overwrite one another on case-insensitive filesystems.
[warn] object Bar {
[warn] ^

The warning about generated classes doesn't explain the core issue to the user, maybe we could warn specifically for the duplicated `@main` here?


**@Lyndon-Li & @sseago Thank you both for your guidance and assistance with the backup process. I was able to take a snapshot backup using the flag --snapshot-move-data , which proves that I successfully completed this task.**

Screenshot_773
Screenshot_774
Screenshot_775
Screenshot_776
Screenshot_777
Screenshot_783

**The backup process has been successfully completed. However, when I removed the namespace associated with the backup shown in the screenshot above, I encountered an issue during my next task, which is restoring using Velero. The details of the issue are as follows:**

Screenshot_778
Screenshot_780
Screenshot_781

Here is the related bundle file:
bundle-2024-08-08-12-08-27.tar.gz


My students have made all sorts of unaniticipated usages of @main-funcs over the last semesters with Scala 3 -- I try to solve this by saying that the should not name their @main `main` and have unique name. **A good warning with good hints of how to solve the issue would be nice.** (We use top-level @main almost always now, but the story on the legacy with actual main with string array in relation to what the JVM requires needs to be told eventually when they have gotten a bit further, so that students now how to interpret what a main actually is and how to get out of strange edge cases like this...)


Realistically, you can't have 2 mains (functions with the same signature) at any scope level so if `@main` is at the top level, it makes sense that you can't have 2 `main`s. At a different level, like scope inside an `object` we could always have a `main` per object. Now that we are having the annotation for main, we should just allow that to continue. In the end, generating a main or not, the semantics of what is written as a function, should really just act like a function. How the code is generated should not really alter the concept of the code that is written.

In this case it is just a warning but otherwise I can run this in VSCode and Metals.

scala
package baz

object Bar {
 @main def main(): Unit = println("main Bar")
 @main def bar(): Unit = println("bar Bar")
}

What concerns me about this is I have written `baz.Bar.bar` and `baz.Bar.main` so without the annotation this seems like normal code. How that works I have no idea - I haven't looked at the generated byte code. If that isn't allowed I understand but it works - not sure why the `bar` function is lifted so the compiler sees the `object baz.Bar` and then the function `baz.Bar.bar` becomes `baz.bar` so then there is a warning. A child or beginner is unlikely to understand the file system case insensitive issue.

The following example works perfectly fine. Maybe I wasn't clear. My objection was that I couldn't have 2 `main` with the same signature inside different `object`s in the same package - I can rewrite those as a normal `main`s and have as many as I want but then I can't take advantage of the `@main` functionality.

scala
object Foo {
 @main def main(args: String*): Unit = println("Foo")
}

Perhaps I should have put my first example that works - but with the warning. I even get like `run` lenses so I can run them all.

scala
package baz

package foo {
 object Foo {
 @main def main(): Unit = println("Foo")
 }
}

object Bar {
 @main def main(): Unit = println("main Bar")
 @main def bar(): Unit = println("bar Bar")
}

The 2 `main`s are ok because they are in different packages. That was a modification from my original try with 2 `object`s with `main`s in the same package that didn't convert directly across from actual code in the wild.

I am unclear on the compatibility issue of the generated mains unless it is tool or TASTY related.


@ugur99 we've seen no reports on this before. On a quick search this looks like some (caching) issue in the kubernetes apiserver (ref e.g. URL You could try restarting the apiserver and see if the problems goes away(?)


yep you are right! Also found this; sorry for my quick reaction. I should have done more research before creating the issue. Thanks for the fast support.


There is already as a PR to make the stateful logit processor shareable

 URL

The idea is as described; pass around logit_processor factories instead of instantiation, and then each Sequence has its own instantiation of logit_processor


To make URL work with URL I think the `SequenceDataDelta` will leave the `SequenceData.logit_processors` untouched, and logit_processor will obtain the state from `SequenceData` as per usual once it has been updated with `SequenceDataDelta`

Meaning to say, probably minimal changes are required.


Absolutely, this has been planned for some time - a larger overhaul of how logits processors work is planned e.g. URL but is stalled a bit given how it needs to fit with other changes. I feel we can make some incremental improvements in the meantime, potentially starting with #5329 that @jon-chuang referenced.

Re needing the state to be in the worker for PP etc, I know it's also required for SPMD but imo should just be part of making the batches stateful (same for the torch.Generators).


By checking the logs I found following error messages:

time="2024-08-08T06:25:44Z" level=info msg="BackupStorageLocations is valid, marking as available" backup-storage-location=velero/default controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:126"
time="2024-08-08T06:25:53Z" level=error msg="fail to get DataDownload: fail to list DataDownload: etcdserver: leader changed" Action=PVCRestoreItemAction Namespace=velero OperationID=dd-4703bc72-cbef-4a31-a0bf-8a3ad433d90f.be3cfbe8-fe0a-41d7f03b9 cmd=/plugins/velero-plugin-for-csi logSource="/go/src/velero-plugin-for-csi/internal/restore/pvc_action.go:240" pluginName=velero-plugin-for-csi
time="2024-08-08T06:25:53Z" level=info msg="Marking restore mongo-20240808115503 FinalizingPartiallyFailed" logSource="pkg/controller/restore_operations_controller.go:186" restore=velero/mongo-20240808115503

So it seems a random issue in etcd, if the problem is highly reproducible, you may want to check if there's any resource or perf issue in your cluster.


Is it difficult to enable pcre2 as backend for this package? sjshuck/hs-pcre2.git is interesting with its compile-time checks, but it misses `regex-base` compatibility.


I imagine this could be a problem since naming is difficult and a lot of people will just do `@main def main =...` everywhere :sweat_smile:

Would it be possible to automatically resolve such conflicts? I see two options:
- if we have the same named methods with `@main` annotation then add some synthetic number to the name?
- or if leave the second method inside it's current scope, generate the object inside the current object where the method is defined

This should be largely compatible, since currently this is an error, but I am not sure if it's doable?


I just discovered this setting in open-webui. My version is v0.3.11, and it's actually working. I had no idea about it before... @chris-31337
1723208848023


This question has been asked before.
read here and
to get an idea how the reversed-engineering went, read here

In short: Someone with an official ECU needs to sniff the communication ecu inverter.


Thanks @chineidu I will make sure the product team sees this in the weekly community feedback report.


Is it possible to get this merged? This would be really useful for my project (it's not really checking links that use absolute paths from the repo root) when running `remark`.


Having this feature would be extremely useful, especially in monorepos where some markdowns reference other projects. Any news on this? 👀


Adding trailing numbers 1.. to disambiguate sounds like a simple and useful enhancement. (Similar to scala-cli and the sbt shell when you run and there are multiple mains)


@anrgct interesting issue. As it is solved. Could you please close it to reduce the number of open issues?


Thank you for your patient replies! @igorschlum @rick-github


localsend_2024-08-11_09-28-25
i enable it, but Shortcuts in the "Send To" folder not appearing in the menu.


@reasonerjt
I have checked all the pods, and everything looks good without any errors during the restore process. Can you help me resolve the issue in more detail?

**@Lyndon-Li @sseago @reasonerjt**
**Additionally, I have another question related to Velero and Ceph storage. Currently, I have a three-node Kubernetes cluster with Ceph storage. If any of these three nodes were to be destroyed and my database backup is stored in the cloud using Velero, can I restore it to a new Kubernetes environment? What are the prerequisites for this, particularly concerning Ceph storage pools and OSDs? Do I need to set up the same names or configurations for Velero to restore everything correctly?**


I extracted the warning for 2 `@main` annotations for differently named methods in a single object to #21365, as that seems like a separate, reporting issue.

The requirements for this is to:
- try to support `@main` annotation for multiple methods under the same name
- not break backwards compatibility

Methods to achieve this have been discussed above, we're not sure what (and if anything) would turn out feasible. It may turn out we end up not supporting this, but it may be worth a try.


@amigalemming ultimately I ended up writing my own package as needed subset of pcre2 capabilities. It is only as complete as I needed for my personal project needs and I was much worse at Haskell back then so very beginner stuff, but you can find it here hpcre2. I found the foreign function interface in Haskell a lot easier than I was concerned about. Ultimately it was not as difficult as I thought to follow the pcre2 docs and code against them as a C library interface. I'm sure if I was writing it now I would have done very differently now I'm more experienced in Haskell but I had a problem to solve and got it done.

I did try to get this added to hackage at some point but it was too time consuming to do. Now it is largely present as a reference for if others need to do the same thing.


@jon-chuang , I've been focusing on other issues in the past couple of weeks, but if this can be an incremental step on the way of a broader refactoring as @njhill mentioned, I'll sync this PR with main again.


This issue was picked for the Scala Issue Spree of tomorrow, August 13th. @EugeneFlesselle @bracevac @jan-pieter and @nmcb will be working on it. If you have any insight into the issue or guidance on how to fix it, please leave it here.


Hello,

We can no longer reproduce this issue. Please try a clean installation by removing any leftover data ( URL

Additionally, you might want to refresh your Firefox profile (instructions here: URL

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center ( URL

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums ( URL

The issue here will be closed.

Thanks!


@EugeneFlesselle @jan-pieter @nmcb we will use the following Zoom link for today:
 URL


The issue has nothing to do with multiple `@main` annotations. As the warning correctly points out, the naming will cause issues with non-casesensitive filenames. So there is nothing to be done here.


This is starting to look like the most likely explanation given what I learned in URL

So a possible fix would be to make sure Agroal shuts down after Vertx... that probably means the Vertx extension needs to use `ShutdownEvent`. We'd need to check if that's already the case; if so, then the problem is elsewhere.


Not sure why but seems to be caused by spreading `...unoCSSConfig` instead of using the variables from `import { rules, shortcuts, theme } from "@tutorialkit/theme";`

The UnoCSS config could also be made into a preset if that's easier:

`presetTutorialKit.ts`

ts
import { definePreset } from "unocss"
import { rules, shortcuts, theme } from "@tutorialkit/theme";

export default definePreset(() => {
 return {
 name: 'presetTutorialKit',
 rules,
 shortcuts,
 theme
 }
})

`uno.config.ts` (removing `...unoCSSConfig`)

ts
 presets: [
 presetUno({
 dark: {
 dark: '[data-theme="dark"]',
 },
 }),
 presetTutorialKit(),


I think this is happening when `unocss` imports the `uno.config.ts`, and that file imports `'@tutorialkit/astro'` that has imports for Astro stuff. Not sure why `unocss` decides to use CJS here.

We are planning to move most, if not all (?) `uno.config.ts` inside `@tutorialkit/*` packages so that end-users wouldn't have to maintain that file. Ideally tutorials wouldn't even have to create `uno.config.ts` unless they explicitly wanted to extend that. There's some discussion on URL


URL was just merged 🎉 . It might make make sense to keep this issue open to continue discussion about wether or not to / how to surface driver and executor logs as explicit outputs in the GUI.


@Lyndon-Li
**I successfully backed up one cluster and used the --snapshot-move-data flag to restore the backup on a second cluster. The restore process completed without any issues, and all statuses showed as successful. However, when I checked the MongoDB pod in the namespace of the new cluster, it was not functioning properly and encountered some issues.**

Screenshot_822
Screenshot_823
Screenshot_827
Screenshot_828
Screenshot_824
Screenshot_825

Here is the related bundle file:
bundle-2024-08-16-16-45-06.tar.gz


To remind myself: MNE python relies on URL for their (somewhat limited, i.e. it does not support a round trip in reading and writing) Brainvision IO


@Mxk-1 has found chunking settings that help resolve issues with create_base_entity_graph with Ollama:


The symmetry detection code in PySCF 2.0 and older versions incorrectly assigns the axes for C2v molecules. It was fixed in #1201. I don't know which convention NWChem follows. I'm sure the symmetry irreps in PySCF 2.1 and newer versions are consistent with the C2v character tables from various sources, such as URL , URL . See also the discussion in the issue #1430 .

I'll mark this issue as solved for the moment. Feel free to reopen the issue to continue the discussion


Using the testing script from #1464 , it's not hard to see that the px orbitals of the oxygen atom is assigned to B1 symmetry, and py orbitals are assigned to B2 symmetry. I believe the irreps are correctly labelled. I'll mark this issue as solved for the moment. Feel free to reopen the issue to continue the discussion.


Vert.x should be the last to shut down. Otherwise, many things would not be functional.

We can imagine an SPI indicating when Vert.x has been shut down (it's an async operation so after completion) for the cases where things must happen after (it should be rare and used with a lot of caution)


As the problem describe here, we cannot fail earlier, but we still need to preserve as more info as possible to help the troubleshooting when prepare timeout happens. Opened an issue #8125 for this.


Hey @ChrsMark! Thanks for the feedback. Yes, exactly the leader is responsible for enabling a sub-receiver (such as `k8sclusterreceiver` and `k8sobjectsreceiver`) if the collector is running as a DaemonSet or a Deployment.

Yes, I fully agree with the concerns about resource limits/requests. However, as you said, it should be properly documented. Not sure if there is a way to workaround it.

Regarding putting some extra load on the k8s API - do you mean querying/updating leases?


That sounds a bit as though Frontend hasn't yet "seen" data from the Recorder API...

On the top right of Frontend is a selector for users & devices: do you see any data populated there?

And if a bit further on the left you select an older time range?


ownTracks_Frontend_info
that's all I see. Maybe some issues with user permissions? Version is never displayed owntracks/recorder **(Loading version...)** when clicking on "information"
ownTracks_Frontend_info


Can you please verify that the Recorder is actually running?

$ ps ax | grep recorder

and can you see if you can query it from the command line of your Raspi?

$ curl URL

As to the configuration you created in `configuration.yaml`: did you originally add an email address for Let's Encrypt to be activated?


- yes, recorder is running
- curl URL -> {"version":"0.9.8","git":"0.9.8-0-g488eabe3e3"}
- yes, I originally added an email-address; Let's encrypt SSL certificate is present.


Please check whether the content of Frontend's configuration makes sense, particularly the `baseUrl` value:

$ cat /usr/share/nginx/html/owntracks/frontend/config/config.js

(no need to paste that here, for privacy; if you're unsure, please send us the file to `support@owntracks.org` and we'll look at it)

If the file does make sense, and the URL is accessible *from* your Raspi to your Raspi (`curl` will tell you that), then I'm going to do something unusual and ask you to please reboot the Raspi ...


To clarify: the `baseUrl` must be accessible from your Web browser.


Thank you very much for your hints. Finally I fixed the issue. 🤗

Problem was: I had to open another port than 443 at my ISP router forwarded to raspi 443.

I had to add the opened WAN port to `baseUrl` to get OpenStreetMaps working on Frontends page.

Maybe a feature for quicksetup would be to choose the local port at setup.


Glad you got it working!

So in essence, your ISP offered you, say, TCP port `1009` which you are redirecting into `443`, so you've configured your `baseUrl` to be ` URL for an _nginx_ on the Quicksetup machine running on 443.

I'll make a mental note to consider your feature request. However, one of the ideas behind _quicksetup_ was to keep it as simple (and thus configuration-free) as possible...

Please keep in mind for your own installation, that whenever you re-run `./bootstrap.sh`, say to add a friend, or reconfigure something, that your Frontend's `config.js` will be overwritten.


@jayrajmeh0

As for the latest issue, it seems the infrastructure where you restore the mongo DB does not meet the requirement of mongoDB.
I suggest you read the links in the error message to understand why it failed. IMO it is beyond the scope of velero.


yes, absolutly correct and I keep in mind that each time I do a re-run of `./bootstrap.sh`, I will have to reconfigure `config.js` to fit my needs regarding ISP WAN/LAN forwarding. Thanks again for pointing me to the problem!


It seems currently the switching script (the Perl version) doesn't have such mechanisms, neither does the Rust version. For the Perl script, it just `systemctl restart`s and then `systemctl start`s. Meanwhile the Rust version seems to be waiting all `restart` threads to finish before starting the `start` threads.

A probable solution to this is to use combine these two commands into one `systemctl restart`, as stopped services will just get started on `systemctl restart`, and systemctl/systemd should be able (?) to resolve these Before/After relations if we invoke the command in one go. For the rust version, maybe removing that `block_on_jobs` and changing accordingly will be sufficient.

—— in case this is really the cause of the problem.


This is fixed in main and will be available in next Insiders (tomorrow) and the next Stable.


Nothing is listening on the MQTT TLS port (`0.0.0.0:8883`) because you disabled Let's Encrypt and we can thus not configure it for the Mosquitto broker which is now listening on `:1883` as you've already determined.

If you configure your devices to use non-TLS MQTT to that port, and your firewall is correctly configured to redirect to your OwnTracks server you should see data, also log entries for Mosquitto.


OK that works. I see the data in the mosquitto broker now after I reconfigured the mosquito config to listen on 0.0.0.0:1883.
There is also an option to use WebSockets. Would that help? My expectation would be, that in that case the data is send via https to the server, which would be my reverse proxy. That one will "unpack" the https and forward the http to the OwnTracks server. Does it works that way (in theory)? Because in practice this is not working the same way I do it for a couple of regular websites.


Our OwnTracks Recorder can also have positions sent to it via HTTP (not Websockets), and our apps (iOS and Android) support HTTP as well.

Do note, however, that a) support for multiple Friends is more difficult with HTTP and b) many of us think MQTT (over TLS) is the more reliable protocol to use with our apps.


I'm just thinking about the best method I have that is in best case encrypted.
I cannot use let's encrypt behind the reverse proxy because the reverse proxy is already doing it and is handling all of that requests. So the let's encrypt handling will never reach the OT server.
If I would use HTTP(S), the reverse proxy can handle the SSL certificate.

Another thing is: Should the position be visible in realtime in the "Frontend"-map? I see my position in the live map (if something is sent since I opened it). At the moment it is empty for me.


when Frontend loads new data, the positions will be visible, but it doesn't refresh by itself.

I see my position in the live map (if something is sent since I opened it). At the moment it is empty for me.

that's unclear to me: what is empty?

Verify that data is being received and stored by Recorder by checking files in /var/spool/owntracks/recorder/store/rec/ / /YYYY-mm.rec

That's the data the Recorder API uses to populate the maps.


OK, that was a bit confusing:
I see myself on the live map but I see nothing on the "Frontend" map - even after refresh.
In the file of the recorder are several coordinates with the current timestamp.


Please check the following:
1. that you've selected a generous timeframe in Frontend
2. also that you see a list of users / devices (right hand top of Frontend)
3. do you see a version number of owntracks/recorder in Frontend? What does it say?


I have the same issue but, the error appears also immediately after the "Configuring DAP" message.

Neovim version (nvim -v)
v0.10.1

Operating system/version
Arch Linux


I didn't describe it well, it's possible to drag a link into a new tab, followed by no response to left mouse click anywhere in chromium.


Happening for me as well on brave since yesterday. After dragging something on the page or even dragging toolbar elements like extensions, the browser gets stucked with a hand symbol in place of the cursor.

See this:
- URL
- URL

drag-and-drop loop when dealing with misbehaving/buggy or malicious
Wayland compositors.

as described in the linked crbugs.


Happening for me as well on brave. After dragging something on the page or even dragging toolbar elements like extensions, the browser gets stucked with a hand symbol in place of the cursor.

See this:
- URL
- URL

drag-and-drop loop when dealing with misbehaving/buggy or malicious
Wayland compositors.

as described in the linked crbugs.


Hey ye,

do I understand this correctly, the only way this plugin works is by manipulating the `index.html` of Jellyfin?

I'm hosting Jellyfin via Docker in the most common setup, i.e. with individual UID/GID.
In this setup, manipulating the file won't be allowed for the user running Jellyfin with the container's default file permissions.
I think this a reasonable security feature and I'd rather not change the permissions of files inside a readily provided container.

There is no configurable list of scripts that the Jellyfin frontend loads etc. or other means to inject this button?


Hi,
1. I use the standard timeframe (1 month from now to the past)
2. In the right combobox I just have "Show all"
3. It says

[owntracks/frontend] (2.15.3)
[owntracks/recorder] (Loading version...)

4. When I open the Frontend page, the page is always fully zoomed in the sea at the south of Ghana. I think this is just the "middle" of the map and the default if there is nothing else to focus on?


Sorry you're having trouble with this. I fear that during our last release of the Recorder we got the startup script wrong, at least that's what it's looking like.

Please start reading the steps in this issue and see whether they apply to your situation as well. In particular:

1. is the Recorder actually running and providing data
2. is the `baseUrl` in Frontend's config correct?


Hi,
1. Yes, it is running
2. Yes and no. The URL was http:// but it actually is https:// due to the reverse proxy. If you access http:// you will automatically redirected to URL But the Reverse Proxy itself is talking with HTTP (no S) to the OwnTracks server.
It was like `baseUrl: " URL and I added the `s` and restarted the server after. I don't know if that should be enough.


Similar issue: URL

This issue started appearing again on the newer versions (nightly/unstable) of the browsers.


I have this issue with Brave and Google Chrome, but no with Chromium.

Brave: Version 1.69.153 Chromium: 128.0.6613.85 (Official Build) (64-bit)
Google Chrome: Version 128.0.6613.84 (Official Build) (64-bit)
Chromium: Version 127.0.6533.99 (Official Build) Fedora Project (64-bit)

 System/Version info

sh
Hyprland, built from branch at commit 918d8340afd652b011b937d29d5eea0be08467f5 (flake.lock: update).
Date: Tue Jun 25 12:06:02 2024
Tag: v0.41.2, commits: 4886

flags: (if any)

System Information:
System name: Linux
Node name: fedora
Release: 6.10.6-100.fc39.x86_64
Version: #1 SMP PREEMPT_DYNAMIC Mon Aug 19 14:35:32 UTC 2024

GPU information:
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])

os-release: NAME="Fedora Linux"
VERSION="39 (Workstation Edition)"
ID=fedora
VERSION_ID=39
VERSION_CODENAME=""
PLATFORM_ID="platform:f39"
PRETTY_NAME="Fedora Linux 39 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:39"
DEFAULT_HOSTNAME="fedora"
HOME_URL=" URL
DOCUMENTATION_URL=" URL
SUPPORT_URL=" URL
BUG_REPORT_URL=" URL
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=39
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=39
SUPPORT_END=2024-11-12
VARIANT="Workstation Edition"
VARIANT_ID=workstation


@hdm9527 I know, but for some reason Brave and Google Chrome have the issue and Chromium doesn't.


Since this issue has been open for quite some time without recent activity, I'm curious if anyone is still experiencing this problem. If the issue persists, please share any updated details. Thanks, everyone, for your contributions and feedback!


Yes, it seems it's happening again for me as well

Hyprland, built from branch at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259 (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069

flags: (if any)


I see, and yes I understand, as Hibernate Reactive for example would no longer work after vertx shut down. And may not be able to shut down, as shutdown in Hibernate Reactive may imply executing SQL statements...

Could we perhaps have an event after vertx has stopped accepting new incoming requests and finished processing existing requests? That's more or less what we need here: the guarantee that nothing external will attempt to initiate use of datasources.

Though I suppose other components unrelated to vertx (Cron? other servers with more exotic protocols?) could be triggering something similar. We may want a different form of synchronization... a two-step shutdown perhaps?


@gmr458 I have the same issue in the most updated Chromium 130.0.6681.0


I've personally not experienced this in months. Seems fixed to me.


I have not experienced this in a while. Appears to be fixed. Thank you!Sent from my iPhoneOn Aug 26, 2024, at 9:12 AM, Oliver Pearmain ***@***.***> wrote:

Since this issue has been open for quite some time without recent activity, I'm curious if anyone is still experiencing this problem. If the issue persists, please share any updated details. Thanks, everyone, for your contributions and feedback!

I've personally not experienced this in months. Seems fixed to me.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>


Same problem here, with Brave and Chromium

Hyprland, built from branch at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259 (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069

flags: (if any)


Got the same issue on Brave. I think it started after nvidia 560 drivers.

 System/Version info

sh
Hyprland, built from branch at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259 (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069

flags: (if any)

System Information:
System name: Linux
Node name: karamanliev
Release: 6.10.6-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Mon, 19 Aug 2024 17:02:39 +0000

GPU information:
26:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX x86_64 Kernel Module 560.35.03 Fri Aug 16 21:39:15 UTC 2024

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL=" URL
DOCUMENTATION_URL=" URL
SUPPORT_URL=" URL
BUG_REPORT_URL=" URL
PRIVACY_POLICY_URL=" URL
LOGO=archlinux-logo


The Plasma/KWin people had a similar problem. Perhaps related?
 URL


From my testing, it seems likely that a regression occurred on Chromium side between version 127 and 128 and @gmr458 message seems to point to the same direction.


URL

Mhm, so looks like a bug in chromium that could be somewhat alleviated on our side


Same here, Jellyfin-web is installed from Gentoo ebuild (package) and I don’t wish to have to remember to modify the file for each update.


Just switched to `hyprland-git` on Arch and I can confirm issue is solved with the fix :+1:


I have updated the clusters to opa 0.66.0. Things were quite for a few weeks. The issue has resurfaced though. I tried asking in the community slack channel, but so far no response.

The decision logger we use does not return the admission review when the response from OPA is nil. When the response is nil, should be possible to get the admissionReview? I would like to be able to provide more specifics, but I am having trouble getting any information at the time of the issue. I do know that doing a rollout restart of the opa deployment alleviates the issue for a time hours/a couple days. The issue seems more prevalent in certain clusters.


If you could provide some details that help repro the issue that would be really helpful.


If only I could reproduce the issue :-)

We use OPA as and admission webhook in multiple k8s clusters. We load our policies using kube-mgmt. We have a decision logger configured to log OPA policy success/fail with some details to aid in troubleshooting. If OPA returns a true/false response, we can see the k8s admissionReview just fine. But, if OPA returns a nil response, the admissionReview is also nil.

Given that the decision logger does not return any useful information when the response from OPA is nil, there is not much to go on.

Does OPA expose the k8s admission review details when OPA response is nil? Or is there some other recommended way to get useful information to help

From our decision logger..

type DiagnosticsResponseElementV1 struct {
 Revision string `json:"revision,omitempty"`
 DecisionID string `json:"decision_id,omitempty"`
 RemoteAddr string `json:"remote_addr"`
 Query string `json:"query"`
 Path string `json:"path"`
 Timestamp string `json:"timestamp"`
 Input v1beta1.AdmissionReview `json:"input,omitempty"`
 Result *v1beta1.AdmissionReview `json:"result,omitempty"`. <====
 Error *types.ErrorV1 `json:"error,omitempty"`
 Explanation types.TraceV1 `json:"explanation,omitempty"`
 Metrics types.MetricsV1 `json:"metrics,omitempty"`
}

We are not running into any issues when we run the unit tests on our policies. We alert when OPA returns a nil response, as it impacts the users submitting to the cluster. Performing a k8s rolling restart of the OPA deployment temporarily resolves the issue. Jobs submitted that encounter the `OPA response is nil`, submit fine after OPA is restarted.


I have only looked at the decision-logger side-car when the issue has surfaced. I will make a point to examine OPA logs to see if there are any clues there.

Thank you for confirming that! I will update the decision logger to spew.Dump to the console and see what that gets me


I would suggest that the `random` argument should be removed completely from this way of creating arrays as it is not obvious that this is uniform distribution between 0 and 1.
Creating random arrays should be done using `nm.core.random. `. This would make is explicit what kind of random is being created and allow for parameters to be set, like `nm.core.random.randn(mean=1.0, std=2.0)` or `nm.core.random.randint(min=10, max=100)` etc etc.
What do you think @MadAlex1997 ?


@sandstromviktor It would be better aligned with NumPy that way. Admittedly most of the data structure and initialization stuff was @forFudan and @shivasankarka, I have handled the math and numerics backend part more. Perhaps they would be able to give their reasoning for it being that way?

The randomly generated scalar/array part of NuMojo is currently pretty limited maybe we could put that on the list for V0.3 along with the many changes for the upgrade to Mojo 24.5.


Happening to me as well. When setting the ozone platform to X11 it goes away but you get those big gaps around the modal windows.

Hyprland, built from branch at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259 (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069

flags: (if any)


Closing as abandoned, feel free to reopen when there are resources to continue.


@sandstromviktor I agree with that. Initially we added it to default constructors as mojo `random` module is quite limited. I am implementing some functions for random number generators right now. I will move these random array constructors to that.

@MadAlex1997 what other changes do you have in mind for the randomly generated arrays for NuMojo v0.3?


I have created a PR #98 with some basic changes for the `random` and `ndarray` module. If you all have any suggestions to improve the random module, please share here or in the PR. Thanks!


Assigning back to @benenright for a review of how we can tweak the designs to complete this, based on my notes above. Here are specific problem scenarios that might warrant design changes.

## Footer actions with warning message

footer actions with warning text

## Bulk actions

bulk actions

## Bulk actions with "Select all" link

bulk actions select all


I think that we should keep the background indigo, as I don't think there is much value in trying to make a light background work behind these actions, and the potential usability issues outway the original intention...

The original intention was to reduce the visual weight of the form footer actions - being something that sticks on the browser bottom edge, it felt like this was worth trying. But in the context of the bulk actions, that only appear once triggered by selecting a checkbox, the dark background helps users to notice it, and if we move to a lower contrast background, it risks them not being noticed (some usability testing we did a while back showed that some users expected these bulk actions to appear at the top of the listing (as per Gmail for eg), but since the indigo bg was high contrast with the page bg, people did notice it at bottom).

I do think it would be worth revisiting how we ensure good contrast for this type of panel specifically in dark mode (as the low contrast means we likely have that usability issue where people don't notice it appear):

image


@joaquimrocha Hi!
Any updates on this issue?
App is great, but this really useful feature is missing :)


Is this the prometheus plugin? On my local env I see:
image


@JoniJnm Sorry, I wasn't clear, my question was about pods requests/limits info (and maybe % of utilization from real time use).


@benenright I forgot one other variation on footer actions, which is used when viewing a past version of a page:

footer actions past revision

This is testable on this past revision demo page. Could you give us design guidance for that as well?

---

re bulk actions, anecdotally we received related feedback from low-vision users (though it’s low on details so I’m following up):


yes because it's a chromium regression that can be alleviated if hyprland better responds to invalid protocol usage


@rick-github thanks for the awesome explanation! Will close this for now. @rodolfo-nobrega @anubhav-agrawal-mu-sigma feel free to follow up if things still aren't working..


Yea, seems like this is happening to me too

$hyprctl version
Hyprland, built from branch at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259 (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069

flags: (if any)

Uploading 2024-09-04 19-17-10.mp4…


@sandstromviktor Your suggestion is nice.

@MadAlex1997 @shivasankarka, Another reason why we did not have a better `random` module was that the built-in `random` module is imported by default (which is actually a known issue URL This leaking polluted the naming space and caused importing `random` from `numojo` to fail in many cases.

With this issue fixed, we can improve the `random` module soon.


IT IS FIXED IN GIT PLEASE STOP POSTING THAT IT HAPPENS IN 0.42


Can confirm this is still an issue. My instance occurred while running a script aimed at optimism sepolia. I second that it does apply to any regular function call that occurs in a script after contract creation as @simplyoptimistic offered. I also used `--with-gas-multiplier` to resolve the issue.


I am working on gathering more information to help diagnose this issue.


Agree, this is very useful information.
It's in the Grafana dashboard if you have that installed, but would be simpler for our less experienced users if it were in Headlamp too.
Example from Grafana
image
And from k9s
image


@juliomuhlbauer added to the project that comes after paraglide js 2.0 (metaframework overhaul) URL


This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the `triage/accepted` label.

The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.

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-sigs/prow repository.


Resident Evil 2 (2019) - CUSA09171

[Debug] memory.cpp:operator():568: Assertion Failed!
Mapping cannot fit inside free region: size = 0xce000000


of course now i see a ton of test errors i cannot reproduce locally.


Caused by: java.lang.Error: Unresolved compilation problem:
 SANITY CHECK: Invalid opcode -88 at pc 162 for stackmap table attribute for method foo()

 at foo.Test.foo(Test.java:7)
 ... 59 more


You mean 4.33? The option there is **always true** independently what is set. In 4.34 the option is gone.


Try changing this IP address

{
"general": {
"objectName": "tb-gateway",
"address": "**0.0.0.0**:47808",

To be the IP address of the network interface of your TBGW.

Harv


Hello,

thank you for your message.
Still there is no answer of the Bacnet-Device.
Looks like something is wrong with the request itself. In Wireshark I can see the request sent to bacnet-device, but nothing is sent back:
grafik
Some flags look differnet in yabe-request:
grafik


Hey, I noticed the PR is already included in the `2.3.0`. I'm trying to run some tests but I get the following error and I'm not able to get the logs from the Pod Step. I'm having two issues:

The `ml-pipeline-ui` Pod is exiting the main process with the following error:

/server/node_modules/node-fetch/lib/index.js:1491
 reject(new FetchError(`request to ${request.url} failed, reason: ${err.message}`, 'system', err));
 ^
FetchError: request to URL failed, reason: getaddrinfo ENOTFOUND metadata
 at ClientRequest. (/server/node_modules/node-fetch/lib/index.js:1491:11)
 at ClientRequest.emit (node:events:517:28)
 at Socket.socketErrorListener (node:_http_client:501:9)
 at Socket.emit (node:events:517:28)
 at emitErrorNT (node:internal/streams/destroy:151:8)
 at emitErrorCloseNT (node:internal/streams/destroy:116:3)
 at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
 type: 'system',
 errno: 'ENOTFOUND',
 code: 'ENOTFOUND'
}

In the short period of time when the `ml-pipeline-ui` is responsive before it's exiting with the above mentioned error code, I'm getting this error:

Could not get main container logs: Error: Unable to retrieve workflow status: [object Object].

Do you know what might be causing the issue?


FYI, I was testing with kubeflow/manifests 1.9.0 and only changed the container images tags for pipeline components to `2.3.0`.


@kromanow94, someone in the (deprecated) Kubeflow slack workspace recently DMed me reporting what looks like a very similar error and a corresponding solution:

 WF manifest lookup -> artifact store lookup) is defined here. Note that the third step only executes if `archiveLogs` is true.


The referenced issue ( URL ) points to a user recreating the bug with "anaconda's default channel". We do not use "anaconda default channel" packages.

If you can recreate with conda-forge only channel:

please provide all the requested outputs from the issue template. they are critical when troubleshooting this.

conda create --name pt python=3.11 pytorch scikit-learn --channel conda-forge --override-cannels

then we can start to investigate.


I also worked on a similar issue 2 months ago
 URL

so getting the full output from you would really help troubleshoot things.


Looks like the issue we are seeing is the same as URL

OPA is getting restarted on our AWS cluster, possible dues to Karpenter. kube-mgmt does not reload the policies. The response we get back just contains the decision-id and nothing else.

We are planning on adding a livenessProbe to the `mgmt` side-car


The BrainVision code is now on PyPi at URL

I implemented an automatic release "action" following the instructions at URL


I also run another scenario with one of the default pipelines. Using the `Run of [Tutorial] DSL - Control structures` will create a set of Pods with the following names:

tutorial-control-flows-gbjpn-system-dag-driver-1941995042
tutorial-control-flows-gbjpn-system-dag-driver-2529298331
tutorial-control-flows-gbjpn-system-container-driver-3821465773
tutorial-control-flows-gbjpn-system-container-driver-467613593
tutorial-control-flows-gbjpn-system-container-impl-2018360503
tutorial-control-flows-gbjpn-system-dag-driver-3793006146
tutorial-control-flows-gbjpn-system-container-driver-1781539373
tutorial-control-flows-gbjpn-system-dag-driver-1653906037
tutorial-control-flows-gbjpn-system-dag-driver-477249553
tutorial-control-flows-gbjpn-system-dag-driver-3564565339
tutorial-control-flows-gbjpn-system-dag-driver-511401279
tutorial-control-flows-gbjpn-system-container-impl-1647980155
tutorial-control-flows-gbjpn-system-container-driver-133111245
tutorial-control-flows-gbjpn-system-container-impl-902191899
tutorial-control-flows-gbjpn-system-dag-driver-2964226956
tutorial-control-flows-gbjpn-system-dag-driver-820485803
tutorial-control-flows-gbjpn-system-container-driver-2311769198
tutorial-control-flows-gbjpn-system-container-impl-3092937256

With the pipeline above, I confirm the mechanism works and I was able to get to the logs through the artifacts when the Pod was no longer available on the cluster.

For my other test I used pipeline created with the following script:

from kfp import dsl
import kfp

client = kfp.Client()

experiment_name = "my-experiment"
experiment_namespace = "glo-k8s-admin"

@dsl.component
def add(a: float, b: float) -> float:
 """Calculates sum of two arguments"""
 return a + b

@dsl.pipeline(
 name="Addition pipeline",
 description="An example pipeline that performs addition calculations.",
)
def add_pipeline(
 a: float = 1.0,
 b: float = 7.0,
):
 first_add_task = add(a=a, b=4.0)
 second_add_task = add(a=first_add_task.output, b=b)

try:
 print("getting experiment...")
 experiment = client.get_experiment(
 experiment_name=experiment_name, namespace=experiment_namespace
 )
 print("got experiment!")
except Exception:
 print("creating experiment...")
 experiment = client.create_experiment(
 name=experiment_name, namespace=experiment_namespace
 )
 print("created experiment!")

client.create_run_from_pipeline_func(
 add_pipeline,
 arguments={"a": 7.0, "b": 8.0},
 experiment_id=experiment.experiment_id,
 enable_caching=False,
)

Which creates Pods with following names (the name differs from example in previous comment because it's a new run):

addition-pipeline-8fbx5-1329381822
addition-pipeline-8fbx5-2476489665
addition-pipeline-8fbx5-2909346888
addition-pipeline-8fbx5-579177391
addition-pipeline-8fbx5-822281223

If I understand correctly, this is because of how the Workflow Name is being provided by formatting the pod name:

 URL

 URL

Is this because of the difference in how the KFPv1 and KFPv2 works?


Also, in case it's related, please make note of this issue: URL


That being said, continuing to do some extra validation on my end to see if I can repro the error.


I would recommend using bundles for policy and data distribution. Here's an example tutorial.


**Related Issues and Documentation**

 - cmd/go: "package?go-get=1 404 not found" errors occurs when go get private project in internal private gitlab repository #64223 (closed)
 - cmd/go: get fails on gitlab subgroups due to go-import meta tags referring to nonexistent repos #34094 (closed)
 - cmd/go: get fail with private and subdirectory repo in module mode #29470 (closed)
 - cmd/go: "no go-import meta tags" when fetching from a private GitLab repo #37504 (closed)
 - cmd/go: GO111MODULE=on go get -v -insecure gitlab.com/xxx/xxx failed #32569 (closed)
 - go get -u all is attempting to find a VCS repository for a module path that is replaced with a local directory #40326 (closed)
 - Go modules issue with gitlab groups and sub-groups #34469 (closed)
 - x/tools/gopls 410 on private repository (not default branch) #39569 (closed)
 - cmd/go: "unknown revision" error is misleading if the entire repo can't be found #47028
 - Can't import package from non-github repo #43251 (closed)

 (Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For questions please refer to URL


Turned out it's a gitlab bug with access levels using tokens from `.netrc`, so techincally, the issue could be closed.

However, I see it as a big problem that you cannot debug `go mod` or `go get` behavior.
If anyone could suggest any ways to debug `go mod` that would be AMAZING, because I've spent hours trying to find a problem with no result. It refuses to use `http_proxy` env variable, it has nothing like curl `SSLKEYLOGFILE` functionality to read it's requests with wireshark. It's a total pain to debug it.

The final solution that helped me was `strace` that showed all the files read by `go mod`. That's how I found .netrc file with credentials and detected this gitlab access problem.

I wanted just a simple thing: add more verbosity to the way request is built by go, but I'm afraid there is no way to do it, and that's a problem.


Hello @CertainPassenger,

Sorry to heare you are experiencing an issue.

There might be some securities policies in place on the browser you are using that prevent opening an iframe to a non https location. It's the case for Safari. So I display this message.

What web browser are you using by default, on which OS?

Mabe try with chrome and let me know if it work.

Also try to see if you can access ` URL


@garronej

Thanks! Your comment helped me narrowing down the issue! I am using Microsoft Edge on Linux (Ubuntu 24.04), however the issue was the addon uBlock Origin. After disabling the addon the redirect worked without any problems.


Thank for reporting back, I've added a notice on the my-theme app: URL


Anyone got a working example on how to do cross builds and deploys?
I am looking for all combination of:

**Host**:
x86_64-linux
aarch64-darwin

**Target**:
aarch64-linux
x86_64-linux


@tcurdt The solution I found is switch to colmena, which supports custom `nixpkgs` instance by its `meta.nixpkgs` & `meta.nodeNixpkgs` parameters.


@GRbit These are good issues to bring up in a forum, rather than the issue tracker. See URL Thanks.


Note that this issue was duplicated in #31 and has been implemented with pull request #32


I collected several comments scattered across different issues and created a monkey patch script along with a working setting for Ollama. It has been tested on version 0.3.2 and works properly. I’m sharing it for those who might need it: URL

I’m not sure if it’s appropriate to comment here, so if the reviewers think it’s not, I'll delete this comment and post it in a more suitable place. Thank you in advance!


yes, can recreate with c-f channel. will provide more shortly


Thank you for the detailed installation and recreation.

So from your experiments I can see that:

* Pytorch 2.4.0 no issue
* Pytorch 2.3.0 issue

Can you try to see if

python -c "import numpy; import torch; torch.zeros((1024, 1024), dtype=torch.uint8)"

recreates things with pytorch 2.3.0 build 0.

I think I hit this issue with: URL

We fixed it in 2.3.1 build 1 URL

I'm honestly not sure how far back to mark the pytorch M1 builds as broken.

If you do the investigation, all with the conda-forge channel channel only, and show your work, I can try to merge in a PR that you make
 URL

I unfortunately do not have an OSX arm machine, so it isn't easy for me to test.


ok, cool. I can do this if you feel it's useful to your users? I maintain the pytorch recipe at anaconda, so this wouldn't be work that benefits me directly - I just thought making you aware of it might be helpful. But I'm happy to do it if you feel it's valuable. If it's low-priority and it's just making more work for you then no worries. Let me know :)


And in general, let me know to what extent collaboration would be welcome from you.


its not low priority as much as "I can't really test it".

it is, but it might not be worth your time.

Generally speaking, i miss the days where the recipes were similar between conda-forge and anaconda. sharing ideas was much simpler. However, with things diverging, i'm not sure the extent that it is possible. Where is your pytorch recipe stored today?

My general understanding was that collaboration was still happening on the `python-channel` which introduced some small compatibility shims:
 URL

I'm open to adding such shims. We have been having trouble with the aarch64 builds and that has been weighing me down.

Help there would be greatly appreciated! See URL


Progress is halted until the message format plugin, which most paraglide users use, is updated to v3 URL While updating the message format to v3, the data model showed inconsistencies, see URL

Number 1 prio is to resolve the data model problems. Work on paralglide 2.0 will continue afterward


Our recipe is here. It diverges a fair amount but there's some stuff in common too (I want to pull across the single building of libtorch stuff).
It'd be great to collaborate on v2.5.0 of pytorch, and I can have a look at the aarch issue if I get time before then.


@LorenzoBettini wonder if we can archive the screenshots somehow if swtbot takes any


at least locally i see 2 launch configs for the xtend anno example. no idea why


=> looks like the workaround transitive dependeny does not work for some reason?


@cdietrich Yes, see for example URL

To be honest, I thought we already archived screenshots in Xtext itself, but maybe we never needed to.


@cdietrich when it happened in the past in my projects, that was due to some changed transitive/re-exported dependencies. Explicitly adding the dep used to work for me.


@skhalash yes, but this is something that can also be properly documented along with some perf tests results so as users be aware of any possible impact to their clusters.


@polybiusproxy Should we move the remaining crash logs from #601 here? All the remaining ones are the same type of error as this. It would make testing easier since we wont need to test on a month old build.


java.lang.IllegalArgumentException: Java code compiled with errors:
Pb(0) SANITY CHECK: Invalid opcode -88 at pc 156 for stackmap table attribute for method doStuff()

Code was:
import org.eclipse.xtext.xbase.lib.Procedures.Procedure1;
import org.eclipse.xtext.xbase.lib.util.ToStringBuilder;

@SuppressWarnings("all")
public class Foo {
 public Foo() {
 }

 public Foo(final Procedure1 initializer) {
 initializer.apply(this);
 }

 public Object doStuff() {
 String _xtrycatchfinallyexpression = null;
 try {
 _xtrycatchfinallyexpression = "MyString";
 } finally {
 "bla".length();
 }
 return ((String) _xtrycatchfinallyexpression);
 }

 @Override
 public String toString() {
 String result = new ToStringBuilder(this).addAllFields().toString();
 return result;
 }
}

 at org.eclipse.xtext.xbase.testing.OnTheFlyJavaCompiler2.compileToClass(OnTheFlyJavaCompiler2.java:92)
 at org.eclipse.xtext.example.domainmodel.tests.XbaseIntegrationTest.invokeXbaseExpression(XbaseIntegrationTest.java:59)
 at org.eclipse.xtext.xbase.testing.evaluation.AbstractXbaseEvaluationTest.assertEvaluatesTo(AbstractXbaseEvaluationTest.java:5346)
 at org.eclipse.xtext.xbase.testing.evaluation.AbstractXbaseEvaluationTest.testCastedExpression_06(AbstractXbaseEvaluationTest.java:2967)
 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:569)
 at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
 at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
 at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
 at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
 at org.eclipse.xtext.testing.XtextRunner$1.evaluate(XtextRunner.java:50)
 at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
 at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
 at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
 at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
 at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:93)
 at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:40)
 at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:529)
 at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:756)
 at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:452)
 at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:210)


wonder why the patch for
 URL
is not working. maybe we cannot determine version :(


java.lang.NullPointerException: Cannot invoke "org.eclipse.core.runtime.Plugin.getBundle()" because the return value of "org.eclipse.jdt.core.JavaCore.getPlugin()" is null
 at org.eclipse.xtext.xbase.testing.InMemoryJavaCompiler.findInlineJsrBytecode(InMemoryJavaCompiler.java:226)
 at org.eclipse.xtext.xbase.testing.InMemoryJavaCompiler. (InMemoryJavaCompiler.java:223)
 at org.eclipse.xtext.xbase.testing.OnTheFlyJavaCompiler2. (OnTheFlyJavaCompiler2.java:52)
 at org.eclipse.xtext.xbase.testing.OnTheFlyJavaCompiler2. (OnTheFlyJavaCompiler2.java:48)
 at org.eclipse.xtext.xbase.testing.OnTheFlyJavaCompiler2$$FastClassByGuice$$11bb94bc.GUICE$TRAMPOLINE( )
 at org.eclipse.xtext.xbase.testing.OnTheFlyJavaCompiler2$$FastClassByGuice$$11bb94bc.apply( )
 at com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:82)

of course this CRAPPPPPPPPP
does not work in standalone mode
=> no version check possible.

=> check if setter is there. if yes invoke it :(


Moreover, we should have a test for the on the fly compiler.
I thought we had some...


@virginiabalducci that error doesn't come from our side, it's from the network. Not sure what we can do there.

During the sending process if any network error occurs the transfer processor will display it as `WPP-025` error, but the description may differ, it reflects a real error.

Also I see that you got this error: `WPP-025 - status-proxy-O.error: insufficient funds for gas * price + value: address 0x3212fD7C2C7984DD6de153691D901445fC8AA07 have 27830378928767798 want 159078669589875316`
but no chain we support has a positive balance for the used address `0x3212fD7C2C7984DD6de153691D901445fC8AA07`
so the error is expected, not sure what's wrong?


I think we do have tests but those are often executed as plugin tests, no?


But that should be the case for domainmodel as well, during a Maven build.
But maybe, @cdietrich, you're referring to the case when running from Eclipse as a plain JUnit test, aren't you?


yes this is what the swt bot tests in xtext-reference-projects/integrationtests do.
they create projects and do eclipse interactions with it


Hi

In this view, I don't know the history as to why the button is orange, but to me it feels like the top banner is doing enough to alert people this is a previous version of this page. I feel like for that reason we _could_ just revert the buttons to be teal here...

However, maybe it's likely that people who have become used to seeing the buttons orange will get confused if they go back to teal). So for that reason it's prob safer just to address the fact that the white text on orange is not high enough contrast... and we should change it to use the same text colour as in the alert banner.

Image

----

While we're here. could we fix this UI glitch where the button loses it's top left and top right border radius after you open then close the options:

Before:
Image

After:
Image


I’m interested in using this feature as well and noticed that a solution is already available above URL .

With that in mind, would it be possible to make this a default feature and include a reference to it in the documentation at Code Blocks Reference?

Many thanks for your consideration!


Sure! We're working on much bigger things right now, but we will very likely consider this again at a later point.


That's great to hear! All the best for your next development steps!


Hi @epage, as a daily user of `cargo-script`, I really want to help advance and stabilize this feature. (Thank you all for working on this feature.) What can I do to help? Is there anything you would suggest for me to get started?


@Rustin170506 any of the tasks in the task list without a PR is good for grabbing.

Some clarifications

The use case for this is that we allow `cargo Cargo.toml` but putting a `#!` in `Cargo.toml` only works well if you symlink it into `path` with the name of the bin.

I had wondered if we should do just always resolve symlinks but that breaks some use cases. Instead, when determining whether its embedded or not and there is no extension, we should resolve it to see what the

 URL

When we talked about this as a Cargo team, we decided this need to reload to cargo home, like `cargo install` does, to avoid downloading a script and being subject to spurious files in your `~/Downloads`, at the cost of losing the config from your repo.

This might require an RFC but likely a trivial one

This will be messy. We'll likely need to change `SourceId` to include the file name if it has an embedded manifest.


One thing that occurred to me while just reading this is:

Should cargo check for a Mark of the Web when running/building scripts on Wwindows/NTFS-drives?


From discord URL

**End to end import, CRUD, export achieved**

Milestone achieved. We are now entering the phase of taking the observations from an end to end workflow to fix bugs and do adjustemnts where useful/required

Uploading CleanShot 2024-09-18 at 19.00.29.mp4…


I have to report that this issue appeared to resurface, but there may be more to it. I have been using V127 of Firefox, up until yesterday, when I was told that Bitwarden was updated and needed me to "log in" to give the extension permission in FF. I found this suspicious, so I decided to finally upgrade FF to the latest (v130.0), which I did yesterday. Bitwarden did not originally appear in the FF upper right side toolbar, so I went to extensions, Bitwarden, Manage, and noticed that the Allow in Private Windows was not selected (which I always have selected - the update must have reset it). I don't know why these settings were reset. I changed it and Bitwarden then appeared top right as it should. Subsequently, I noticed that Bitwarden DID NOT LOCK anymore as it did in the previous version. Going into settings in the extension top right, Account Security, I see that the Vault Timeout is set to Browser Restart. I NEVER have used that setting, yet that is what it was set to after all of this, and is probably the reason why I was not seeing BW lock anymore. I changed the timeout to my standard setting and it now locks as it should. Although this issue has not actually resurfaced, it appeared to, because all of my settings following an update had been reset to defaults. I don't think that is wise and was definitely NOT expected. Just an FYI.


you can simply use the `maturin-action` like pydantic does: URL


I saw you use python scripts to upload as release assets.

in constrast, pydantic uses github artifacts for uploading the wheels, and downloads them again in the publish step.

then, you can upload them as release assets and to pypi using dedicated actions (example) too. you won't need PyGithub or your python scrips anymore. 100% yml :)

this example ^ uses pypi trusted publishing (no user/pass). all you need to do is add oconnor663/blake3-py as trusted publisher here and add the `permissions` in the github action as per the example.


Hello,

any news on this topic?
I have the same issue.
TB-Gateway is sending "Unconfirmed-REQ who-Is"-Messages to 'Room Control Simulator'.
But nothing more happens.
grafik
I opended another case a few weeks ago, because I can`t access data from other bacnet-devices as well.
( URL
I can access all the data witch Yabe (of room simulator and bacnet end-device).

Is anyone here using bacnet-connector of tb-gateway successfully?

Kind regards.


i was able to send snt just 2 days ago. i dont have any context besides that. maybe something got broken recently

@virginiabalducci can you pls check?


thanks @virginiabalducci
@saledjenic @dlipicar do you know the root cause?


@virginiabalducci I was able to reproduce your case with `0x32e12fd7c2c7984dd6de153691d901445fc8aa07` address.

So let's analyze it:
- you want to send 1 SNT from the `0x32e12fd7c2c7984dd6de153691d901445fc8aa07` from any of the supported chains (mainnet, opt, arb) to the recipient address to any chain (mainnet, opt, arb)
- what are possible options (since you have a positive balance for SNT only on mainnet):
 1. mainnet -> mainnet (transfer)
 2. mainnet -> optimism (bridge)
 3. mainnet -> arbitrum (bridge)
- let's look now at how the router sees that request since all chains are available on both from and to sides:
 1. check transfer for mainnet -> mainnet -> this returns `insufficient funds for gas * price + value: address 0x32e12fD7C2C7984DD6de153691D901445fC8AA07 have 16773029697747188 want 235096461785385998`
 2. check transfer optimism -> optimism (transfer) -> `execution reverted: ERC20: transfer amount exceeds balance` cause you have 0 SNT on optimism
 3. check transfer arbitrum -> arbitrum (transfer) -> `execution reverted: ERC20: transfer amount exceeds balance` cause you have 0 SNT on arbitrum
 4. check bridge `mainnet` -> `optimism` -> `not available for chainID` means there is no contract for bridging SNT
 5. check bridge `mainnet` -> `arbitrum` -> `not available for chainID` means there is no contract for bridging SNT
 6. check bridge `optimism` -> `mainnet` -> `not available for chainID` means there is no contract for bridging SNT
 7. check bridge `optimism` -> `arbitrum` -> `not available for chainID` means there is no contract for bridging SNT
 8. check bridge `arbitrum` -> `mainnet` -> `not available for chainID` means there is no contract for bridging SNT
 9. check bridge `arbitrum` -> `optimism` -> `not available for chainID` means there is no contract for bridging SNT
- now looking at the previous point we confirmed that there is no route that can be made, which is correct, that's what the router says, but a question is about the error, which one of those is the most meaningful for you? You cannot choose one, but the right way would be to return all of them, right? Displaying all of them was rejected as an idea in one of my PRs and then we had to choose one to display. There is some logic for selecting the most meaningful error which is working quite well, but in case like this one where all chains are in play on the "from" and "to" side is hard to select one (especially when we have different processor orders among router runs) cause all are valid errors.

**To summarize and conclude, there is no error in the router logic.**
@virginiabalducci @anastasiyaig @pavloburykh @alwx


@virginiabalducci to get a better understanding about router's logic, please have a look at this comment URL


Thank you for the comment @saledjenic

I have couple of questions here:

1. Regarding insufficient funds error: we have an open issue URL Could you please leave a comment in that issue summarising your findings regrading this problem. I remember that recently there have been much discussions in different Discord channels, but unfortunately there is no summary in the ticket. Currently we are not able to perform L1-L1 transactions in Status app, at the same time I am able to perform same transaction with the same account using Metamask.

2. At which point do we understand that token is available only on L1 and thus there is no sense to try building any routes except L1-L1? Can we prevent from trying to perform
mainnet -> optimism (bridge)
,
mainnet -> arbitrum (bridge)
 etc steps if we know that only mainnet-mainnet is available? To be honest, this is very confusing that we are showing user the irrelevant errors like
transfer amount exceeds balance
 or
not available for chain ID
 while app UI shows that we are trying to build L1-L1 route and both errors have nothing to do with L1-L1 in this case. Why we are not showing
insufficient funds
 here which is related to L1-L1 route building?


I guess yes, that's what we're going to do with the new Send modal design.


@itstamimi @nhoizey how do you think the approach would work with media choosers or re-used images?

I sometimes re-use images on multiple pages, I may have list and detail pages that re-use imagery although often at different sizes. Some times I just want to open a media browser and pick an image to use. It's easy with a git backend to list a folder and a few children, it's harder when the media browser has to look all over the repo to build it's collection.


FWIW it appears this issue was fixed in .NET. Here's the .NET issue and here's the PR that fixes it.


Thanks for finding this.

This build should resolve your issue while I am adding features and bug fixes for the next release.

 URL


Yes keep it open for now in case anyone else has the same issue, thanks!


Thank you for this observation - adding `systemd.services.tailscaled.after = ["NetworkManager-wait-online.service"]` seem to have solved the issue for me


Hey @droctothorpe , were you able to have a closer look here?

TBH, I'm not exactly sure if the Pipeline I created using the script from URL is KFP v1 or KFP v2. I deployed it using `kfp==2.8.0` so I assumed it's KFP v2. Do you know if I should change anything in the script to explicitly configure it for KFP v2?


Just to re-clarify, as noted in #21365, having multiple `@main` methods with different names _is_ already supported:

scala
// ~/scala-snippets-6/multi_main.scala
object Bar {
 @main def main1(): Unit = println("main 1")
 @main def main2(): Unit = println("main 2")
}

➜ ~/scala-snippets-6 scala multi_main.scala --main-class main1
Compiling project (Scala 3.5.0, JVM (17))
Compiled project (Scala 3.5.0, JVM (17))
main 1
➜ ~/scala-snippets-6 scala multi_main.scala --main-class main2
Compiling project (Scala 3.5.0, JVM (17))
Compiled project (Scala 3.5.0, JVM (17))
main 2
➜ ~/scala-snippets-6 scala --version
Scala code runner version: 1.4.0
Scala version (default): 3.5.0

However, as each `@main` method results in a class with the method's name, this name must be different than other objects or classes. This is not the case for `object Bar` and `@main def bar` in the example above: ignoring case, these are the same.


What does _not_ work is other have two `@main` methods with the same name:

scala
object Foo {
 @main def main(): Unit = println("main 1")
}

object Bar {
 @main def main(): Unit = println("main 2")
 // error: main is already defined as class main

This is expected and spec'd that way: `class main` thus is already defined by the first `@main` so cannot be redefined.

To circumvent this issue, we would need to follow one of @tgodzik suggestions:

However:

- Synthetic numbers seem confusing to me: if there are several main methods, the user will ultimately need to specify which one to run using `--main-class`, so it better not be a generated name.
- Conditionally leaving the method in an inner scope seems hard to specify. Would that be done only if the method name would result in a clash in an outer scope?

All in all, it seems to me that the current behavior is probably okay.

Whatever we decide, it needs to be spec'd before someone can tackle this issue during an issue spree.


Sarebbe coerente mantenere lo stesso approccio ogni qual volta ci siano allegati da caricare, vedi #240 e #229


When I ran that same pipeline, my pods had different names (i.e. they adhered to the v2 nomenclature):
<img width="657" alt="image" src=" URL

Are you positive that you submitted the run with v2?


@W95Psp @paulmure what's the state here? It looks to me like the PR only needs a review?


I'd invite everyone to try this out on their machines and report back.

If this works, that'd be a quick and easy one-line patch to the tailscale NixOS module; fixing this for everyone.


So this is a bug still going on. I though I was going crazy because each time I hit ctrl-v or paste something in the chat it duplicate the last cell of my jupyter notebook


I think Jupyter causes it. It's more like a Jupyter notebook bug.


FYI an easier fix to this is adding the following env var to the ml-pipeline-ui:

yaml
- name: DISABLE_GKE_METADATA
 value: "true"

Shout out to @boarder7395 for sharing it.


@kromanow94 I think you might be having the same issue I did.

The two changes required for everything to work are
* Update environment variable ARGO_KEYFORMAT on deployment ml-pipeline-ui to any format you want (we include {{workflow.namespace}} to ensure separation of tenant data assets).
* Update the workflow-controller configmap value of keyFormat to be the same format as above.

What I missed was the second item which resulted in the issues you had above.


Can confirm this fixes it. @Atemu +1 for including the fix in the tailscale module


The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity, `lifecycle/stale` is applied
- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied
- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed

You can:
- Mark this issue as fresh with `/remove-lifecycle stale`
- Close this issue with `/close`
- Offer to help out with [Issue Triage][1]

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[1]: URL


Work on paraglide 2.0 continues. Might have a pre-release by the end of the day!

* the inlang sdk v2 is stable
* the message format plugin supports variants (!)


CC @julianwiedmann @joestringer who are also involved in the issues mentioned.


Just wanted to add, I'm happy to take a stab at adding a new mode to netkit if it would help.


Hi @jrife I've pushed a patch here which I think could be acceptable. Do you have a chance to help testing whether that looks good on your side? URL I can run this by Martin and Nik in the meantime. Thanks for your help!


We could try asking for stable backport once this lands. I can add a Fixes tag just in case.


Cool, I'll give it a try locally under the two scenarios mentioned.

That would be great. It looks like we'd need to backport a fix to all supported Cilium versions to use `NETKIT_SCRUB_AFTER` if supported by the current kernel. I wonder if there should be any logic in Cilium to block a user from using endpoint routes with netkit on an unpatched kernel? Then again, maybe a known issue is enough since affected users could just switch to `veth` until they update their kernel.


Logical tests are passing. TypeSafety is still a todo. Hence, no pre-release today and no prerelease until mid October. The team is meeting in Rome for an onsite next week which I a) have to attend and b) I have to prep :)


I changed Cilium locally to set `IFLA_NETKIT_SCRUB` to `NETKIT_SCRUB_AFTER`.

* I tested the scenario in #34042 (liveness probes + `NetworkPolicy`) with the kernel patch and it seems to fix the issue. Switching to `NETKIT_SCRUB_BEFORE` this breaks again as expected.
* The scenario in #33875 does not work still unless `NETKIT_SCRUB_NONE` is used. I believe this is related to the fact that `skb->mark` is immediately reset after running `cil_to_container()` which sets it in `__ctx_redirect_to_proxy`.

c
 ctx->mark = MARK_MAGIC_TO_PROXY | proxy_port unknown state unknown ifindex eth0 orig-ip 0.0.0.0: 10.244.0.156:53 -> 10.244.1.246:36813 udp
 -> proxy flow 0x0 , identity 10388->26256 state reply ifindex lxc7b7ce9de2500 orig-ip 10.244.0.156: 10.244.0.156:53 -> 10.244.1.246:36813 udp
 unknown state unknown ifindex eth0 orig-ip 0.0.0.0: 10.244.0.156:53 -> 10.244.1.246:36813 udp
 -> proxy flow 0x0 , identity 10388->26256 state reply ifindex lxc7b7ce9de2500 orig-ip 10.244.0.156: 10.244.0.156:53 -> 10.244.1.246:36813 udp


I just think an option should be added to not open the panel. I don't think it's a matter of re-thinking the side bar philosophy.


As discussed with @CPernet we need to come up with a few thought-through meaningful scrambling options for MEEG data, beyond time series scrambling. Let's reopen this issue to bounce ideas back and forth.

We probably need to have 2 or 3 additional ways to break the spatio/temporal/spectral structure in the data.

I am currently thinking about a combination of spatial filtering and blockwise scrambling. For ERP'ish application this probably also would need to take the structure of the events into account.

Specifically, using spatial unmixing (based on 'some' heuristic), then a scrambling step (e.g. scrambling the order of the latent components and/or blockwise scrambling (i.e. keeping the overall spectral structure in the data, and/or time-locked to event stuff), then again a spatial mixing step, would be a flexible framework that allows for a mixture of spatiotemporal scrambling, preserving aspects of the overall structure in the data


Hah, okay, thanks for testing and taking a look. I presume NETKIT_SCRUB_NONE generally could be enough as an option anyway and if needed BPF prog could zero the data. I'll finalize and add a BPF selftest (next week) so that this can be submitted & merged then.


Status update: Bazel 8 is going to ship with built-in garbage collection, with knobs to set a maximum size in bytes, a maximum age for cache entries, or both.

However, contrary to previously announced plans, we're going to provide an **offline** implementation, whereby garbage collection occurs in the background while the Bazel server is idle. It therefore remains possible for the set limits to be exceeded during the course of a build, which is a necessary tradeoff to preserve build performance. We will also provide an official tool to run a garbage collection manually, for users who prefer to have more control. The documentation page at URL will soon be updated with the details.

The more sophisticated **online** implementation described in URL is, unfortunately, extremely challenging to implement across all supported operating systems, while providing hard size guarantees, allowing multiple Bazel processes to share the same disk cache, and preserving current build performance in all scenarios. It's unclear to me at this point that all of these goals can be simultaneously fulfilled.


Thanks for the update.
As a B plan, can we have a suggested way to handle a hard disk space constraint?
A documentation like:

If you have a hard disk space contraint of size X, setting bazel max cache sizes of X-Y% should be safe if your binary size is under Z bytes.

And maybe document what will happen if the sizes isn't set right. Hopefully something like, "he current upload will be lost, but there won't be any curruption and nothing will crash. So the only consequence is the recomputation of some entry".


I think the best rule of thumb we can give is: prior to starting a build, you must have enough disk space to fit the entirety of the build outputs twice (one time for the contents of `bazel-out`, another for the copies uploaded to the disk cache). That's obviously an overestimation, and obviously dependent on what your build does; the actual number can't be computed except by actually running the build.

If you do run out of space during a build, it's always safe to retry it after you have (manually) recovered some space. Bazel is designed to produce a correct build result regardless of the starting conditions.