With #12303, `.cargo/config.toml` will be used relative to the script and not to the CWD. This mirrors `cargo install --path `.

As for rustup toolchain files, our options seem to be
- Do nothing as that is what `cargo install --path ` does today
- Suggest `#!/usr/bin/env -S cargo +stable` despite not being fully cross platform, it will likely be "good enough"
- Don't use the `cargo` proxy but add a new proxy that is specifically meant for thi workflow (see Pre-RFC for naming considerations and ideas)
- Have the `cargo` proxy evaluate enough of cargo's command-line to detect a "cargo script" is being used and to load the toolchain file relative to that path
 - This would effectively require copying cargo's CLI up-to determining whether this is a "cargo script" (or go through the hassle of trying to design and maintain a lib for that)
 - rustup ships independent of cargo and on much less frequent schedule yet rustup would need to have knowledge of the latest cargo command-line
- The real `cargo` binary could detect its in rustup and re-run itself to cause the proxy to look up the rustup toolchain for the "script"s path
 - The proxy process is already slow as-is and no-rebuild times need to be kept at a minimum
 - Maybe if rustup told cargo if a rustup toolchain file was being used and only re-evaluate then?


@rbtcollins Is that only set if the user set it or if a toolchain file is used or is it always set?


In couple of the threads, a `cargo new --script` has come up

At minimum, it would create a `foo.rs` that has had `chmod +x` run on it and has a shebang and a main.

The question is how much more? I think that depends a lot on who you are and what mindset you take when considering this feature, like if it should have some of the manifest in it.

The other question I have is: "if we need a `cargo new --script`, have we failed?". I see this filling a similar role to the playground for learning and trying things out and if there is enough boilerplate that it needs to be automated, that seems bad.


AFAIK, always. In proxy mode [rustup sets both `RUSTUP_TOOLCHAIN` and `RUSTUP_HOME`][1] for the actual command.

[1]: URL


The application remains unresponsive/laggy and I still get the "The window is not responding" messages on launch. As of now the best solution has been excluding the file from scanning giving no problems.


Seems like this is solved, and the discussion happens in #311

Please tell us if you need anything


But i saw and follow the instructions, it was not implemented even in experimental folder. I do not see a reason to disqualify my contribution.


I guess a flag that forces a GC run after invocation could work for this case.


Alternatively, we could provide a simple script that does disk cache GC following the same algorithm (based on `mtime`) outside of the Bazel process. Then your CI run could call that before or after the build.


A parameter of the bazel clean would already be helpful for a lot of users. A lot of people cares about disk space only when is full but with the current clean you can not clean only what is not being used.


@limdor we also discussed this but don't really like it because we do not want to teach users to run `bazel clean` - this is something they should not need to do.


That is a very good point. I understand and I agree, until now this is the only reason why I have to run bazel clean


I wrote a script like that, feel free to do as you please with it: URL


@belech Awesome stuff. Any chance you open source your solution.


EditorDebuggerPlugin seems to suffer the same issue and the same workaround


@chrisb123 are you trying to run a scene of the plugin? Or just your game? (If the latter it doesn't make any sense)


I'm using the example from the official documentation found here.
[( URL

I cant find any other information on using the editor debug plugin. I get the same error mentioned above and applying the fix found above does result in the debugger getting an the custom debug plugin tab
`_exporter = (GitVersionInjector as Variant).new()`


Oh sorry, I thought you were using the GDScript addon of the same name.


Following up on Louis' last message : we discovered that bucket versioning wasn't turned on and that snapshots seem to work just fine now that we set up versioning

Will run some more tests on our dev instance but looks promising overall :)


So the issue here is that user scripts end up trying to access Editor-only classes at runtime?


It's really good that the discussion has kicked in again, one of our developers posted this today in our Slack and I'm gonna post it here to show the scale of the issue

image


In the past few days, the crash has been extremely severe. If I play Dota2 and turn on VScode, my computer will crash directly after a while


Over 8 years of being a user of these type of build tools I have heard this statement many times from different tool teams/developers. The reality users (not only users but pipelines that do builds in resource constrained environments) won't be taught to use `bazel clean`, they have already learned todo that, the cat is out of the bag folks. I'm not advocating for that idea or saying that its a bad north start to shoot for, but the reality is most tooling has not gotten it right and continue to push the burden onto the user and the user sends up blowing away environments depending on context.

Personally, I'm a huge fan of being able to set a quota here based on hard limits or resource %, I think in practice LRU/accessed purging is probably best if a feature like this is enabled. Using background process daemon to clean up is probably the way to go.

From the context which we have (I'm no longer at twitter) used bazel, a considerable amount of effort and issues where solely around resource clean up depending on the environment (remote execution systems, local laptops, deployment pipelines, ci pipelines), each one having their own thresholds of limitations and SLA to purge/delete data.

A commonly used code repo where a user build a lot of different targets or was building targets with frequent change, could easily amass +500GB of cached objects, we would use some preamble script wrappers to check for such things and schedule background cleaning jobs `bazel clean --async`, sometimes that would fail and leave a huge amount of state we would then do a secondary check to hard GC their sandbox.

Getting a tighter and cleaner caching story (including the situations around remote cache/execution) will be huge for bazel, large companies hit issues in this area every time they reach for bazel and have a considerable large code base.


This is suggested changes to the model which should IMHO facilitate all desired operations for checks more or less efficiently

patch
❯ git diff
diff --git a/datalad_registry/models.py b/datalad_registry/models.py
index 75c0faf..b9748d9 100644
--- a/datalad_registry/models.py
+++ b/datalad_registry/models.py
@@ -15,13 +15,20 @@ class URL(db.Model): # type: ignore
 annex_key_count = db.Column(db.Integer)
 annexed_files_in_wt_count = db.Column(db.Integer)
 annexed_files_in_wt_size = db.Column(db.BigInteger)
- info_ts = db.Column(db.DateTime(timezone=True))
- update_announced = db.Column(db.Boolean, default=False, nullable=False)
 head = db.Column(db.Text)
 head_describe = db.Column(db.Text)
+ head_dt = db.Column(db.DateTime(timezone=True))
 branches = db.Column(db.Text)
 tags = db.Column(db.Text)
 git_objects_kb = db.Column(db.BigInteger)
+
+ #: Last time the DB record was updated
+ last_update_dt = db.Column(db.DateTime(timezone=True)) # former info_ts
+ #: Last time we checked this URL
+ last_check_dt = db.Column(db.DateTime(timezone=True))
+ #: Non-null value means there is a pending check request, with a dt on when it was requested.
+ #: If non-null set, and another request comes in, ignore new request - keep old check_request value
+ check_request_dt = db.Column(db.DateTime(timezone=True), default=None, nullable=True) # former bool update_announced
 #: Whether initial data has been collected for this URL
 processed = db.Column(db.Boolean, default=False, nullable=False)


here is chatgpt produced code:

python
import time
from datetime import datetime
from sqlalchemy import create_engine, MetaData, Table, select
from celery import Celery

# Set up the Celery application
app = Celery('tasks', broker='pyamqp://guest@localhost//')

# Set up the SQLAlchemy engine
engine = create_engine('postgresql://user:password@localhost/dbname')

# SQLAlchemy models
metadata = MetaData()
URLs = Table('urls', metadata, autoload_with=engine)

check_minimal_time = 3600 # seconds -- so no checks for a URL
n_run_in_parallel = 10
sleep_waiting = 60
n_max_failed_checks = 10

@app.task
def check_url(url):
 pass # Implement your task here

while True:
 # Get all running tasks
 inspect = app.control.inspect()
 active_tasks = inspect.active()
 n_currently_running = len([task for tasks in active_tasks.values() for task in tasks if task['name'] == 'tasks.check_url'])

 n_can_run = n_run_in_parallel - n_currently_running
 if not n_can_run:
 time.sleep(sleep_waiting)
 continue

 with engine.connect() as connection:
 # SQLAlchemy query
 query = select([URLs]).where(URLs.c.processed == True)
 urls = connection.execute(query).fetchall()

 urls_to_check = sorted(
 [url for url in urls if url.check_request_dt and url.processed],
 key=lambda url: url.check_request_dt)[:n_can_run]

 if not urls_to_check:
 urls_to_check = sorted(
 [url for url in urls
 if url.processed and url.n_failed_checks check_minimal_time
 ],
 key=lambda url: url.last_check_dt)[:n_can_run]

 if urls_to_check:
 for url in urls_to_check:
 # SQLAlchemy update
 query = URLs.update().where(URLs.c.id == url.id).values(last_check_dt=datetime.now())
 connection.execute(query)
 # Adding tasks to celery
 [check_url.delay(url) for url in urls_to_check]
 else:
 time.sleep(sleep_waiting)


here is the code avoiding while True loop

python
import time
from datetime import datetime
from sqlalchemy import create_engine, MetaData, Table, select
from celery import Celery

# Set up the Celery application
app = Celery('tasks', broker='pyamqp://guest@localhost//')

# Set up the SQLAlchemy engine
engine = create_engine('postgresql://user:password@localhost/dbname')

# SQLAlchemy models
metadata = MetaData()
URLs = Table('urls', metadata, autoload_with=engine)

check_minimal_time = 3600 # seconds -- so no checks for a URL
n_run_in_parallel = 10
sleep_waiting = 60
n_max_failed_checks = 10

@app.task
def check_url(url):
 pass # Implement your task here

while True:
 # Get all running tasks
 inspect = app.control.inspect()
 active_tasks = inspect.active()
 n_currently_running = len([task for tasks in active_tasks.values() for task in tasks if task['name'] == 'tasks.check_url'])

 n_can_run = n_run_in_parallel - n_currently_running
 if not n_can_run:
 time.sleep(sleep_waiting)
 continue

 with engine.connect() as connection:
 # SQLAlchemy query
 query = select([URLs]).where(URLs.c.processed == True)
 urls = connection.execute(query).fetchall()

 urls_to_check = sorted(
 [url for url in urls if url.check_request_dt and url.processed],
 key=lambda url: url.check_request_dt)[:n_can_run]

 if not urls_to_check:
 urls_to_check = sorted(
 [url for url in urls
 if url.processed and url.n_failed_checks check_minimal_time
 ],
 key=lambda url: url.last_check_dt)[:n_can_run]

 if urls_to_check:
 for url in urls_to_check:
 # SQLAlchemy update
 query = URLs.update().where(URLs.c.id == url.id).values(last_check_dt=datetime.now())
 connection.execute(query)
 # Adding tasks to celery
 [check_url.delay(url) for url in urls_to_check]
 else:
 time.sleep(sleep_waiting)


re update: since some evil ppl could do "git push --force" and rewrite history we cannot just use `git pull` or even `git pull --ff-only` since it would not be guaranteed to work. I think the safest strategy would be to

try `git fetch`. If that is ok, means connection is good etc. Do `git pull --ff-only` and if that one fails, then `rm` cached copy, redo cloning from scratch for that URL. If `git fetch` fails -- announce check failed, and let above cron job to retry later.


@boryanah Thanks for reporting this! Yeah, this is a known issue and we are working towards a fix. In the meantime, please follow the comments/steps in #294 - hopefully that will at least let you compile.


In my project, I'm not actually accessing the Editor-only classes during game runtime. However, my scripts are still loaded/parsed, and the compiler complains about it. The script code is never executed.

At least, this is what I believe to be happening, based on the fact that casting the Editor-only class to a Variant fixes the compile error, and there are no further errors during runtime.


URL flag is set here.

i prefer to conform to the language standards but i have some golfs built into having \n exist. so i would be fine either way.


Probably is about the conflict between namerequst and name-examination.
The **[Edit]** button in **Name Request** should not be available when the name state is changed to INPROCESS in Name-Examination.
So do the **[Upgrade Priority]** and **[Cancel and Refund]** buttons in **Name Request**.


@yarikoptic is `head_dt` the `authordate` of the current `HEAD`?


Don't you thing still having centralized files for url (`Tier.yaml`) will still favorized conflicts and so just moving the problem from a file to another ?

Why not having a folder per Tier and then inside having one yaml per project, something like :

bash
ecosystem/resources/members
├── community
│   ├── my_super_project.yaml
│   ├── my_awesome_project.yaml
├── extensions
│   ├── my_super_extt.yaml
│   ├── my_awesome_ext.yaml
├── main
│   ├── qiskit-finance.yaml
│   └── qiskit-nature.yaml
└── index.yaml

The `index.yaml` would contains the list of the tier folders (community, extensions, main, ...). As the tier are static, we would not have any conflict this way.

- Also what the difference between `qiskit` and `main`, from my understanding `qiskit` is purely `main` ?
- I saw `unitaryfund` folder, do we need a folder per organisation or can we have a folder `partners` or something like ? If we create a folder per organization, we need to find a way to reference new folder without re-creating conflict.

---
- About #228, i think we should close it and keep the work on this new one.
- For the `set-output`, the problem is for the function in actions bash script as well. I think we need to review it more generally to have a better management of the vars.


@AbdullahKazi500 & @dhruvshettty if you are still there maybe you both could sync with @frankharkins and pass on the issue #424 to be clear on the new structure


Thanks for your reply!

I'm thinking ahead a bit, but since most uses of the DAO are accessing by URL, my idea was to order the files by URL (the part after `github.com/`). Then file access becomes trivial and we can rid of the DAO in the future. The only other access type is by tier, hence the `Tier.yaml` files. These merge conflicts would just be one line, but it's still not zero-touch, which I agree is a drawback.

In terms of how things currently are, your suggestion makes more sense as that's the way `members.json` is structured. Can I suggest something like this?

└── tier
 └── organisation
 └── repo.yaml

For example:

ecosystem/resources/members
├── community
│   └── unitaryfund
│   └── mitiq.yaml
├── extensions
│   └── qiskit-community
│   └── prototype-qrao.yaml
└── main
 ├── Qiskit
 │   └── qiskit_ibm_runtime.yaml
 └── openqasm
 └── openqasm.yaml

That way there are no problems if two repos have the same name.

***

I'm not 100% sure, but I _think_ tier is just a level of endorsement. I can see that at least the `openqasm/openqasm` repo is considered "main", so main ≠ qiskit.

I think it would be good if filepath was unique to URL (e.g. `github.com/unitaryfund/mitiq`). We can just do an `os.walk` to find files; no index needed.


@AbdullahKazi500 I won't assign just yet as it's not clear what the best solution is.


@frankharkins indeed something like should work fine :)

Just in the community as most of the project doesn't have organization, how do you see them ? Inside a subfolder `toto` or directly inside the `community` mixed with the organizations folders ?


Because, the file `members.json` is gonna disapeared to be split into separated individual folder.


@mickahell After thinking on it a bit, I think the path of least resistance is to go with your original proposal. I think by trying to add more layers I was just making it more complicated.

Let's go with your original idea.

ecosystem/resources/members
├── community
│   ├── my_super_project.yaml
│   ├── my_awesome_project.yaml
├── extensions
│   ├── my_super_extt.yaml
│   ├── my_awesome_ext.yaml
├── main
│   ├── qiskit-finance.yaml
│   └── qiskit-nature.yaml
└── index.yaml


@AbdullahKazi500 what do you have so far? Slack me on the Qiskit workspace (`@frankharkins`) if you prefer.


Yeah, I agree with the original idea. I do not recommend including the GitHub organization. It seems unnecessary. We've never had duplicate project names in the ecosystem and can control for that since we decide who can join or not.

@frankharkins are you still suggesting that we convert all these YAML files into one generated JSON file? So that it stays simple for qiskit.org to consume, and they can deal with JSON rather than YAML. That idea sounded good to me.


@Eric-Arellano thanks! Yep I imagined either nightly or on push to main, an action would compile a JSON in the same form as we currently have, and add it as a release asset. Then qiskit.org can point to one link. I.e.

diff
- URL
+ URL


At this point, I don't think this is worth doing, since it may invalidate solutions that people may not come back to fix. Because Fortran is not one of the most popular languages, I wouldn't want to do something that would reduce the number of solutions.


2 and 3 are pretty much outlined in the changes to the model needed to implement proper (cron or triggered) updates as in URL . Either URL model gets renamed - I don't care much but indeed smth like `RepoUrl` (I think we deal only with datasets ATM but could be regular git repos without UUID I guess in the future) would be more appropriate but not critical to rename, but could be done in conjunction with other changes needing migration. So I will add it to the project along with that #112


We need to find a simple way to stock this file, maybe more using artifact or something like


Probably even simpler is to have the file generated by the user, using a script, and checked in to version control. Then, qiskit.org points to that static URL.

Yes, there will be merge conflicts for the generated file. But the answer is to simply regenerate the generated file -- you should never try to manually fix the merge conflict.

This is how we generate our quite complex GitHub action YAML files for Pantsbuild. It's worked quite well for us! URL It's nice being able to see in the PR how the final rendered asset will look.


Yes, these changes will be done with whatever changes needed in #112.


I've tried to identify the inactive users who could be affected by this change. I've roughly defined "inactive" as anyone who has not submitted a solution in the last six months (ie 2023). But in the end, I define it based on my own observation of their activity. (I include some high scorers like cure-honey and LucaArgentiUCF as inactive. Some like ivan-pi are low-frequency but seem active enough to adjust to the change.)

The holes with inactive players (predominantly "art" but a few others as well):

* 12 Days of Christmas: 3/15
* 99 Bottles of Beer: 5/14
* ASCII table: 0/9
* Cubes: 2/9
* Diamonds: 5/14
* Game of Life: 0/3
* Hexdump: 0/4
* Maze: 0/3
* Number Spiral: 0/11
* Quine: ~10/40? (many inactive, but half are cut-and-paste)
* Sierpinski: 4/12
* Sudoku: 1/3
* Sudoku v2: 1/4
* Tongue Twisters: 3/12

Don't take these numbers too seriously; I didn't script it and I could have overlooked a few holes, and my definition of "inactive" might not reflect their willingness to amend their solutions.

My takeaway is that - with one notable exception - very few of the top scores will be affected, and no hole will be devastated by the change. Worst case is perhaps a loss of ~25% of solutions. Perhaps a bit more of Diamonds and 99 bottles. Practically, I think it will be less.

The loss of cure-honey's scores could be significant.

----

If it were me, I'd pull the trigger and drop backslash support. The longer that it's left in, the harder it will be to change. The absence of backslash characters is somewhat unique to Fortran, and can significantly reshape the form of a solution in some cases. Putting it back in feels like part of this ongoing effort to make Fortran look more like C.

But it's easy for me to say that as a low-effort contributor who doesn't think much about retaining users, so I would leave it in the hands of others to decide.


@JRaspass can you try removing the flag and see how many solutions fail?


Hmm ok, so we need a manual action to generate it. It's too much action for someone to git pull, git checkout and then git push and create a PR to do.

But It can also became the same problem as we have today and we will have so many branchs open (similar to the `batch_check_` branchs)


The action can probably push directly to the `submission-*` branch, maybe triggering on PR approval.


I'm not following why we need a GitHub Action? When you change the YAML files, you are expected to also run a script to update the final JSON file. CI will check if the JSON file is out-of-date and error if so with instructions of how to run the script.

Yeah, that's a little manual. But keep it simple for now.


If we put the generated general file who ref every project we will have conflict as well because every submission gonna edit it with their url :/

User never run any script, they only submitted issue and the Action does the who trick, then someone only need to validate the PR to add the project and so never no-one need to clone and commit anything so can't run any script. That's why we need an action to generated this file

Do you see what I mean ? I'm not sure to be totally clear ^^'


Hi,
How to do this?
Like how to add this code.exe file in excluded file list?


The McAfee app has a section called Real time scanning. If you open that it has a button to add files to exclude from scanning.

The path to code.exe is something like

C:\Users\{UserName}\AppData\Local\Programs\Microsoft\vscode


Note: after further investigation, this error also happens with the Google Translate browser extension which is likely more widely used than the GTranslate plugin.


@bethanylang this one is ready to start moving as soon as we have the capacity.


Use something like:

#pragma warning disable CS4014 // disable warning

private async UniTask DoMagic()
{
 // await logic here
 ...
 // DOTween
 var seq = DOTween.Sequence();
 for (int i = 0; i < n; ++i) {
 seq.Insert(time, transform.DOScale(0.3f, 0.1f); // CS4014
 .Insert(time, transform.DOMove(Vector3.zero, 0.1f);
 }
}

#pragma warning restore CS4014 // restore warning

You could also just use a single pragma at the top of the file.


We added `-fbackslash` because we initially misunderstood how to deal with UTF-8 in Fortran. See #177. It's a bit unfortunate, because I don't think people use Unicode escape sequences in the way that it was originally requested by @ivan-pi. Or if they do, I doubt it is optimal.

I would consider the loss of 25% of the solutions to be very significant, if it affected that many. For example, that would move Fortran from the 28th most popular language on the site to the 44th most popular language, which would make me very sad. I don't think that it would be worth it.

One thing we have done in the past that we could consider doing again, if this issue truly is important to people, is running some one time code to automatically replace as many usages of `\n` as possible, assuming that is the only escape sequence used. We've done this before, when C# enabled top level programs, to strip out the extra boilerplate, for example. In this case, before we disable the flag, before any solutions have broken, we can run through a bunch of replacement rules for `\n` and if the solutions continue to work, we keep the replacements. That increases the chances that the solutions continue to work after removing the flag.

Here are some examples:
Try to replace `\n` with `"//char(10)//"`
Try to replace `\n` with `'//char(10)//'`
Try to replace `'\n'` with `char(10)`
Try to replace `'"n"` with `char(10)`
Try to replace `"\n` with `char(10)//"`
Try to replace `'\n` with `char(10)//'`
Try to replace `\n` with `'/'` (when it's used in a literal string in a format specification).
Try to replace `\n` with `"/"` (when it's used in a literal string in a format specification).

Plus some more variations of the above that add line extension characters automatically in case making the replacement causes the code to hit the line length limit.

There's probably some other cases that I'm missing.

These replacements probably aren't optimal, but at least solutions wouldn't break. It may confuse some people though.

Also, because these replacements are fairly short, they probably wouldn't significantly reshape solutions, unless those solutions contained many instances of `\n`.


Substitution feels a bit awkward, but I'd be ok with it. Harder to say if the recipients would be.


Before: `11 / 1047` fail
After: `146 / 1047` fail

`84 / 146` are @KatieLG or her transpiler so I'm sure she'd be happy to fix her use of backslash in her auto-printer. So that leaves `51` new failures, not too terrible imo. I see a lot of names on that list that are active enough that they'll probably fix their solutions too.

It's less than the stats `1770` because the re-tester groups identical bytes/chars for a given golfer to save on re-testing.


Or I'm wondering, can github Pages generated raw data html page by merging json ?
This way we would not have to store any general json file. And so we would not have any risk of conflict anymore. And no need any manual process to do.


If my point just above is not possible. The solution you refer @frankharkins looks good to me 🙂
Doing that from the main branch in order to stock the general file in the latest tag assets, would allow to not have conflict and to always be up to date with the actual main branch. Only require at most to click on a single button (no script, no git cmd, ...)
We could even schedule the action to be launch every day or every week in order to be fully automatic 🤖


Hi, sorry I could not work on this. I'm removing myself from this issue, however, @AbdullahKazi500 happy to help you if you need it


The previous logs were from ArchLinux. I tried the same on NixOS on my Intel Iris Xe card laptop and I get the exact same error.


Thanks a lot! We managed to install it following the instructions in that thread.


Ohh great - glad at least you could use the workaround and get Corrfunc running. I am closing this issue but please feel free to reopen if you need additional help.


McAfee does real time scanning, and this's probably the reason vs code is running slow (since its scanning vs code too). You can exclude vs code from McAfee scanner.


Hi
I copied the code example from the issue and used it to replace the theme.json in Twenty Twenty-Three.

- 6.2.2 only: No issue
- 6.2.2 and 16.1.0: Additional font sizes as described
- 6.3-beta2-56121: Additional font sizes as described


Thanks @JRaspass! And also to @SirBogman for handing the discussion. Should we now discuss replacement of `getarg()` with `get_commmand_argument()`? (kidding, kidding...)


I know you're kidding, but I think that this kind of thing is not as bad, because people will expect it. They wouldn't expect `-fbackslash`.


I agree, a big difference in my mind is that `get_command_argument()` and `get_command_count()` are almost identical to `getarg()` and `iargc()`, so it's just an offset in count.

On the other hand, removing `\n` support can significant change the structure of a solution (at least in my case!), so I think it's a more interesting change.

I also tested four compilers (GNU, Intel Nvidia, Cray) and it seems like they all support `getarg` without special compiler settings, which surprised me. Nvidia was the only one with default support for backslash escape characters, but all have the ability to toggle them.


Hi! You can open an issue for this. Please refer to the ToDo List Issues instructions.


After trying to implement this, I've realised that we shouldn't have the "tier" information in two places. This is already causing problems: For example, `qiskit-ibm-provider` is "Main" on qiskit.org/ecosystem, but has the "Extension" badge.

In PR #426, I've gone with naming all TOML files the repo name, and having them all the same level.


Which GPU is renderD129? Could you post outputs of `ls -lah /dev/dri/by-path`, `lspci`, as well as `vainfo`? Also, does wf-recorder work in vaapi mode (`wf-recorder -c h264_vaapi -d /dev/dri/renderD129`)?

You cannot use vaapi on integrated nvidia graphics (or, I thought so, I had a hard time finding a reference that proved or disproved this), so I highly suggest you use the intel gpu for encode.


I do not have that machine with me right now so I will provide the above details for the intel Iris Xe card I have. I'll report back with the logs from the hybrid machine when I have it available again.

bash
~
❯ ls -lah /dev/dri/by-path
Permissions Size User Date Modified Name
lrwxrwxrwx@ 8 root 3 Jul 20:57  pci-0000:00:02.0-card -> ../card0
lrwxrwxrwx 13 root 3 Jul 20:05  pci-0000:00:02.0-render -> ../renderD128

bash
[nix-shell:~]$ lspci
00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 01)
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 01)
00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 01)
00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 01)
00:12.0 Serial controller: Intel Corporation Tiger Lake-LP Integrated Sensor Hub (rev 20)
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
00:15.0 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)
00:15.1 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 (rev 20)
00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)
00:1c.0 PCI bridge: Intel Corporation Device a0be (rev 20)
00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
00:1f.5 Serial bus controller: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)
01:00.0 Non-Volatile memory controller: Micron Technology Inc Device 5404 (rev 03)
02:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)

bash
[nix-shell:~]$ vainfo
Trying display: wayland
libva info: VA-API version 1.18.0
libva info: Trying to open /run/opengl-driver/lib/dri/iHD_drv_video.so
libva info: Trying to open /usr/lib/dri/iHD_drv_video.so
libva info: Trying to open /usr/lib32/dri/iHD_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Trying to open /usr/lib/i386-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /run/opengl-driver/lib/dri/i965_drv_video.so
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Trying to open /usr/lib32/dri/i965_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Trying to open /usr/lib/i386-linux-gnu/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

bash
[nix-shell:~]$ wf-recorder -c h264_vaapi -d /dev/dri/renderD128
selected region 0,0 0x0
[AVHWDeviceContext @ 0x7f4524005800] Failed to initialise VAAPI connection: -1 (unknown libva error).
Failed to create hw encoding device /dev/dri/renderD128:


Yeah, so you do not have a functional libva installation--I suggest you follow your distributions documentation on vaapi.


Oh I didn't consider that. Thanks for taking a look. I'll try to setup vaapi, use wf-recorder to check if it's working and then try wl-screenrec again.


I have setup vaapi and wl-screenrec works now. Thanks. However the colors look "washed out" and the overall quality is a little blurry which is odd. I see there's an issue about this in the repo so I will take a look at that.
Thanks for your help.


Do they look overall worse than wf-recorder? Keep in mind the default bitrate is rather low, as this is what I like (I prefer small file sizes over high quality), but feel free to increase it with the `--bitrate` parameter


I'll try that! The colors are actually significantly better than wf recorder but the blurriness remains


@desmondfernando thanks for reply! But it's not the best solution to write pragma everywhere :(


The issue is in shadowing the `uv` variable, causing a segfault


Hey folks 👋🏻.
I would like to work on this issue. Since I'm relatively new to this project and cloud native in general, it would really help if you could tell me from where to get started, as in where particularly I should look for in the code-base?


@rsavage-nozominetworks - can you please try setting `verifyDigest: false` for the `Audit` mode policy rule?


Child-issues:
* #2999
* #2947
* #2948
* #2949
* #2950
* #2951
* #2952
* #2953


I was running into a similar (but unrelated) thing yesterday. The reason is most likely an internal error reported by SPIRVCross, but the error handling in SPIRVCross in release mode and with C++ exceptions disabled just silently aborts:

 URL

TL;DR: I need to find a way to report such internal compiler errors from SPIRVCross - for instance by enabling and then catching exceptions from out of SPIRVCross (at least as first step, the next problem will be that those messages won't be very useful in many cases).


PS: wrote a SPIRCross ticket here, but independently from whether that's fixed or not I'll need to find a workaround.

 URL


PS: this was the problem I was running into, also looked like a "silent crash", but was actually a SPIRCross error:

 URL

...and this ticket is similar:

 URL


Hey @apurva-1403 !
 Thank you for raising an issue 💗
 You can self assign the issue by commenting /assign in comment 😀
 Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
 Don’t Forget to ⭐ our GameZone🎮
 Make sure you join our Discord🕹


The `-p` parameter doesn't work for ui components as I describe in this issue #686. In future releases it will be possibile to change the installation folder.


We have contacted the McAfee team and they acknowledged this issue and are working on a fix. More details in this article with a **workaround** to exclude VS Code from being scanned:
 URL


Before closing this issue, just a quick question @frankharkins how do we manage the submission actually in PR :
- #388
- #390
- #398
- #402

For the #402, I can close it and regenerate it (it's my QAMP project) but for the other do we resubmit them by hand ?


I re-created each submission but I couldn't delete the old branches
Maybe we can also clean the batch branches in order to restarted from this new way to go. What do you think ?

Anyway we can close this issue :)


Hi @AbdullahKazi500, @frankharkins finished the new structured. You can `pull` the evolve and go ahead :)

I think you can integrate `historical_test_results` into the new unitary project `toml` file.

Do not hesitate if you have any question


You cant just exclude files in organizations. Most users in orgs have 0 control over that. Unfortunately.


Also, I can't seem to turn any of the python experiments off, no matter what I do in the config file(s). Not sure if that's by design or a completely separate bug.


Hello! Looking into these bugs you reported, I appreciate all your help! In terms of the experiment does ` "python.experiments.optOutFrom": ["pythonTestAdapter"],` not work for you? Did you reload the window? If that is not working then it is a different issue so let me know. Thanks!


The cmake upgrade to 3.23.3 version was initially setup as a follow up in the al2023 upgrade/nodejs upgrade, tho now it seems like a 2.9.0 dependencies thus it needs to be updated soon.

Thanks.


`optOutFrom` works! Didn't realize that was a thing. Turning off the experiment gets my tests discoverable again, so that's a win. I'll check out the multi-root project on RHEL8 too and comment there if the symlink problem resolves the issue.


Let’s track this in #31. #954 fixed a bit more issues with strings.


Looking into the UUID thing- one issue I have is I have trouble reproing it. Were you able to consistently get the error message `2023-07-10 14:31:48.438 [error] On data received: Error occurred because the payload UUID is not recognized`?


Yep. It comes up every time. I'll see if I can put together an example repo I can share, but not 100% I'll be able to do that easily.


We had a check-in on this experiment during the cargo team meeting. The general feeling that I took from the meeting was that this would be useful enough roughly where we are at, even if we don't have "larger" features like workspaces though those features could potentially help out.

Proposed features to defer out so long as we have a plan for adding them in without breaking compatibility
- Workspaces
 - Currently there is no workspace auto-detection and the proposal is for single-file packages to explicitly opt-in via `package.workspace = true` (currently only takes the path to the workspace)
- `[lib]` support
 - We could distinguish a future `[lib]` single-file package from the existing `[[bin]]` ones via an empty `[lib]` table
- `cargo package` / `cargo publish`
 - Without `[lib]` support, this is limited `cargo install` use cases and the scope of the use cases for scripts to publish and install seems relatively small
 - No compatibility concern present; we would just remove error checks
- Embedded or adjacent `Cargo.lock`
 - We could either add a `workspace.lock` field for controlling this or check for the presence of the content, however it is stored
 - The main constraint is if we want to allow embedding the lockfile, that we leave room for doing so syntactically

Decisions still needing to be made:
- How to embed manifest

Decisions that need to be affirmed
- Handling of `package.edition` (defaults to "stable" but warns every time its parsed)


We also encountered such error and the workaround was adding the following options:

js
 // After updating from `passport-saml` to `@node-saml/passport-saml`,
 // it started throwing `Error: Invalid document signature`
 // when testing SSO using Acadeum's Google SAML server.
 // Turns out that's a common issue and the workaround is to pass
 // `wantAssertionsSigned: false` / `wantAuthnResponseSigned: false` flags.
 // URL
 // URL
 wantAssertionsSigned: false,
 wantAuthnResponseSigned: false,


I asked on a forum that's working on integration of the official ecu. I do hope one has a sniffer...


I created a sample repo you can use. When I run this on my Windows VSCode with a Linux Remote over SSH, I get the UUID errors. When I run it on my MacBook, I don't get the UUID errors but I still get the same behavior; only one project's tests show up in the explorer. Not sure why the error messages aren't showing up on the Mac and haven't tried testing locally in Windows. Hopefully this helps you find a solution!

 URL


Bonjour @baby-scarf ,

Sans retour de votre part je me verrai contraint de fermer cette issue.


Just ran into this after updating powershell on CentOS:

pwsh 7.3.5 (old was 7.3.4)

commands:

# update powershell
sudo yum update powershell

# Set permissions for powershell to run commands
sudo setcap cap_net_raw=eip /opt/microsoft/powershell/7/pwsh # real binary, not symlink

# rename offending config file
 mv /home/user/.cache/powershell/StartupProfileData-NonInteractive /home/user/.cache/powershell/StartupProfileData-NonInteractive.disable


The full message:

It doesn't work with _PR_ numbers.

It's expecting either a GitHub _issue_ number, the lowest such began at 32426, from when we transferred issues over from URL

Or use the other format to specify a BPO ID.

I think the easiest thing is to create a new issue for the PR, and use that issue number.


There was no bpo issue: in the initial message, Ammar said "(Can be marked with skip issue and skip news as it pertains to the build process)" but I decided that a visible addition possibly used by non-core devs (to run coverage) should be mentioned. I opened #106690.


Just checking on this for opinions on whether the new Patterns interface in the Site Editor, and changes in the Block Inserter has resolved this issue - or if user-designated categorisation of patterns would be helpful?


Hi!

I could manage to make the snapshot work using a local MinIO instance and everything works perfectly!

However while trying to connect to a S3 bucket from Scaleway, with the versioning feature enabled, we still have this issue:

And the snapshots don't work anymore.

Do you have any clue of what's going on by chance?
We continue investigating but any help would be much appreciated :pray:.


It is not clear to me whether to backport, so I did not, but this could still be done. Closing now.


assets/images/marketplace/marketplace-transactions.png #187774


@ssefick See also URL and URL Please take urgent steps to resolve this issue. No positive changes appear in the repository. Less than three months remain to retain this package on CRAN


Hello! We have just finished our testing rewrite and are beginning the roll out to users. I have tested this issue with the re-write and I am no longer reproducing the bug! If you would like to try it yourself, you need to add this setting to your users `settings.json` `"python.experiments.optInto": ["pythonTestAdapter"]`. Let me know if it doesn’t work for you and we can re-open this issue. Thanks!


Hi @eleanorjboyd, is there something else we need to do for this setting to take effect?

image


Actually, it looks like it _kind of_ works after putting the setting in my WSL config.

image


You can confirm you have the rewrite enabled by setting `"python.analysis.logLevel": "Trace",` in your user settings then check for `Experiment 'pythonTestAdapter'` is active in your python logs. Do you see that in your logs?


Looks like it is.

image

Here are my observations so far:

- The test extension takes a few seconds to appear on the left. It's the last one to "load."
- When I click on it, I first see this:
image
- A couple seconds later I see what's in my prior screenshot.


I'm actually running into "Error occurred because the payload UUID is not recognized" in a single workspace scenario (`pypa/packaging`).


By the way, I selected to install the pre-release version of the Python extension. I'm not sure whether that's needed to test the `pythonTestAdapter` change. I was running the release version prior to this.


We figured out the root cause- its a problem with when UUIDs are being deleted when the command to the test server is done running but not when the test server is done sending the response back. Therefore the UUID is being deleted pre-maturely. Working on a fix to have the actions to happen in the correct order.


I'm desperate! Using Vscode 1.80.1 and if I put:

"python.experiments.optOutFrom": ["pythonTestAdapter"]

It gets greyed out and I see this message:

<img width="981" alt="Screenshot 2023-07-15 at 12 10 10" src=" URL

What in heaven does it mean!?

I can't access my tests!!!


Well, well, I had to add this line specifically in to remote-server setting.

And added that actually: `"python.experiments.enabled": false,`

This is not great. I really want to centralise all my settings in one place and make exceptions... well, when they are **exceptions**!

Now I need to keep my eyes in **every** remote setup I have!

I simply don't want any experimental stuff! You guys have created the Insider Vscode for what then?


I have the issue on the MacBook Pro 2019 16,1 with t2 patches after switching to iwd, because of network issues.


You might be facing the same issue as #1. Disable the composite clipper then restart ST. If the announcement does not play after 4 hours then it means not all bits for the composite clipper are not being set. I will test various feature masks again to see what stops the announcements.


@sunqm can you comment? Is the new behavior preferred, even though it is inconsistent with previous versions and with NWChem?


Hi! Could you send me your logs? I am wondering if there is an error there about UUIDs and if so would be connected to this: URL


If you ever find yourself in a situation where the latest extension version simply is not working, you can pin to an older version that does work for you until we manage to fix the bug causing you issues.

I wouldn't label this work as experimental. The new testing code passed through pre-release users and internal team testing. It's unfortunate this bug didn't trigger until more people were able to use the new code in more varied scenarios. It's behind an experiment flag so we can control the rollout in case of showstopper bugs, not because we are actively "experimenting" with our stable users (as I said, this code already passed various quality gates to even reach this level of rollout). If we had not used our experiment infrastructure to control this then this would have gone out to all users this release with no possibility for us to do an emergency rollback without pushing a new version of the extension or given you a way to opt out in any way until we made a new release with a fix.

To get early feedback from users willing to help us find bugs early. Obviously this didn't come up from testing with our pre-release users and are now only running across this from wider usage.


I can confirm this as well, that the JSONModel doesn't support indexing boolean fields. Here is my testcase that shows the same thing:

python
"""This file demonstrates that redis_om_python cannot index/search boolean fields"""
from redis_om import Field, JsonModel, Migrator

class MyObjectBroken(JsonModel):
 my_string: str = Field(index=True)
 my_int: int = Field(index=True)
 my_bool: bool = Field(index=True)

class MyObjectWorks(JsonModel):
 my_string: str = Field(index=True)
 my_int: int = Field(index=True)

Migrator().run()

# Add some objects that are broken
object1 = MyObjectBroken(my_string="", my_int=1, my_bool=False)
object1.save()
object2 = MyObjectBroken(my_string="", my_int=1, my_bool=False)
object2.save()

# Add some objects that work
object3 = MyObjectWorks(my_string="", my_int=1)
object3.save()
object4 = MyObjectWorks(my_string="", my_int=1)
object4.save()

objects = MyObjectBroken.find().all()
print(f"Found {len(objects)} MyObjectBroken expected 2")

object_get = MyObjectBroken.get(object1.pk)
print(f"Found {object_get=} MyObjectBroken")

objects = MyObjectWorks.find().all()
print(f"Found {len(objects)} MyObjectWorks expected 2")

object_get = MyObjectWorks.get(object3.pk)
print(f"Found {object_get=} MyObjectWorks")

If you run this, you'll get the following output showing the object with a boolean field doesn't work:

text
$ python boolean_field_search_suppport.py
Found 0 MyObjectBroken expected 2
Found object_get=MyObjectBroken(pk='01H5K85HDADT687Y25Y7BAEWKK', my_string='', my_int=1, my_bool=False) MyObjectBroken
Found 2 MyObjectWorks expected 2
Found object_get=MyObjectWorks(pk='01H5K85HDCCAS49NADBDY39CXQ', my_string='', my_int=1) MyObjectWorks


@simonprickett , any update on native support for boolean fields?


See URL for where it's defined that booleans aren't supported yet, but seem to be supported at some point?


From my sleuthing, since the `bool` class is implemented as a subclass of the `integer` class, we end up getting a numeric index created:

text
"ft.create" ":__main__.MyObjectBroken:index" "ON" "JSON" "PREFIX" "1" ":__main__.MyObjectBroken:" "SCHEMA" "$.pk" "AS" "pk" "TAG" "SEPARATOR" "|" "$.my_string" "AS" "my_string" "TAG" "SEPARATOR" "|" "$.my_int" "AS" "my_int" "NUMERIC" "$.my_bool" "AS" "my_bool" "NUMERIC"

This is coming from this line:
 URL

From the docs of `FT.CREATE` there isn't native support for boolean types, so it likely has to be mapped to `NUMERIC` for this to work, however it's unclear what's going on under the hood here, but I'm guessing that at least a part of it is related to saving actual RedisJSON boolean fields, but telling RediSearch that it's a numeric field.


I found a workaround for this issue. Since the `bool` class is a subclass of the `int` class, you can declare the model field as `int` and then convert between bool/int as necessary.

Here is the code that I tested on redis-om 0.1.3:

python
"""This file demonstrates that redis_om_python cannot index/search boolean fields"""
from redis_om import Field, JsonModel, Migrator

class MyObjectBroken(JsonModel):
 my_string: str = Field(index=True)
 my_int: int = Field(index=True)
 my_bool: int = Field(index=True) # declare as int, but pass in boolean values works

class MyObjectWorks(JsonModel):
 my_string: str = Field(index=True)
 my_int: int = Field(index=True)

Migrator().run()

# Add some objects that are broken
object1 = MyObjectBroken(my_string="", my_int=1, my_bool=False)
object1.save()
object2 = MyObjectBroken(my_string="", my_int=1, my_bool=True)
object2.save()

# Add some objects that work
object3 = MyObjectWorks(my_string="", my_int=1)
object3.save()
object4 = MyObjectWorks(my_string="", my_int=1)
object4.save()

objects = MyObjectBroken.find().all()
print(f"Found {len(objects)} MyObjectBroken expected 2")

objects = MyObjectBroken.find(MyObjectBroken.my_bool == int(False)).all()
print(f"Found {len(objects)} MyObjectBroken with bool as False expected 1")

object_get = MyObjectBroken.get(object1.pk)
print(f"Found {object_get=} MyObjectBroken")

objects = MyObjectWorks.find().all()
print(f"Found {len(objects)} MyObjectWorks expected 2")

object_get = MyObjectWorks.get(object3.pk)
print(f"Found {object_get=} MyObjectWorks")

Here is the output from it:

text
$ python boolean_field_search_suppport.py
Found 2 MyObjectBroken expected 2
Found 1 MyObjectBroken with bool as False expected 1
Found object_get=MyObjectBroken(pk='01H5KBCJMMCY9Z9SY74C87B20N', my_string='', my_int=1, my_bool=0) MyObjectBroken
Found 2 MyObjectWorks expected 2
Found object_get=MyObjectWorks(pk='01H5KBCJMP4RM26QSSVB77YKTQ', my_string='', my_int=1) MyObjectWorks


Hi again. I tested with composite clipper disabled and ST restarted, but the announcement keeps popping up after 4 hours. Maybe one of the other features is to blame, unless it would be caused by the fact that composite clipper is not properly registered, regardless whether it is active or not? Since the announcement litterally plays "_This sound is processed by Stereotool_", one may expect it to be related to one of the sound processing features and not something like FM, Advanced RDS or µMPX.
Licenes
Do you have any ideas for speeding up testing this, as it will take 4 hours for scanning along each of remaining features this way? I already found that the 4-hours timer is not related to the windows clock time, so it can't be tricked that way :-(
Thx!


How to pin?

I apologise for my ton but when one wastes a whole morning, in a weekend with a critical deadline...
I'm not against experiments but, please, make it easier to opt-out.


I've ordered the flex cable, I am having issues where the OSD is occasionally inaccessible. Where can I find the installation instructions? I have a friend who is experienced at soldering, hope he can help.


As has been mentioned, `setAllowedCharPattern` is not intended as a complete replacement for `setPreventInvalidInput`. The main purpose of that was to restrict which characters the user is allowed to type into the field, which `setAllowedCharPattern` does a better job of. We did not introduce an alternative for preventing input if the full value does not match a specific pattern because that has a questionable UX, and we recommend using validation together with showing an error as user feedback instead.

I opened a PR for clarifying the purpose of `setAllowedCharPattern` in the JavaDoc. As this issue was about changing how `setAllowedCharPattern` works, which we do not intend to do, I'll close this as resolved. Feel free to open a new feature request for introducing a separate feature for preventing input if the full input does not match a pattern, as suggested here: URL


Update: I have tested with all features disabled and still the announcement pops up. Now testing again with composite clipper deactivated and unregistered (removed it from the feature mask).


We don't remove Alices anymore and when someone spent we cancel the round.


I wonder if we should block cargo script on #9778. 87be661989788e296c90c4ae835cb92822a1617d is an example of this where a file named `42answer.rs` leads to a `answer[EXE]` when it should be `42answer[EXE]`.


Try using 0x49e508db. I think bit 3 (0x00000004) might be for the event FM license and that is what might be causing the message.


You can change the version in the extension view via "Install Another Version":

image

Now if you want it to update when we push a new stable version, that's all you need to do.

If you want to stay on that version, you can turn off automatic updates for the extension:

image

Otherwise you need to turn off automatic extension updates via the `extensions.autoUpdate` setting (unfortunately it's a global setting).

Apology accepted. We realize hitting any bug is annoying and we obviously do what we can to avoid it; this is why there isn't anything the extension does that you couldn't do manually (e.g., run your test suite from the command-line instead of having VS Code do it). We always strive to make sure there's no lock-in specifically to make sure we are never a complete blocker for one's work or you feel trapped by the extension.


With 0x49e508db ST displays a red message "FM processing used without license".


Just to add to the conversation, I'm using 0xbe27b897 with the command line version of ST and get the message every 12hours.
Only Advanced Clipper, Natural Dynamics, Advanced Dynamics and Dehummer enabled.


I don't get the message with my "Test all license options" preset for some reason. If you can, send me your preset through email and I can try diagnosing further.


That is a strange mask. The program defaults to 0x49e508df. Where did you get that from? (Might be the checksum.)


Is anyone working on the rust-analyzer support? I would like to give it a try.


This is just nitpicking about my statement. You rely too much on correct wording. Let me rephrase it:

In my opinion, a round should be cancelled if
 * there is an Alice that spent her input.

The current state is that a round is cancelled if
 * there is an Alice that didn't confirmed her input _and_
 * there is an Alice that spent her input.


I was holding off until we had settled how we want to embed the manifest in source to avoid extending out the churn to other projects.


ORd the bits manually by the keygen source reference, for testing and passed to the keymaker using "-f". Same thing (audio message everey 12h) happens with the default 0x49e508df.


No, this is not about wording, this is about the scope of the change. The scope of this change is to avoid having inconsistent data structures (Round::Alices and CoinJoinState::Inputs) because that results in all kind of problems. The only way to do it just by not removing alices. That's what #10914 does.

Once we have these two lists onsync we can tackle the next problem: what to do when an alice spends. That's a different discussion, one that we still didn't have. In #10914 we cancel the rounds but that's something that is still under discussion. Finally, the detection of double spending coins participating in coinjoins is something we are working on right now and in case we decide to abort a round when a participating coin is spent that policy should apply not only for connection confirmation but for all the phases, except input registration.


I don't want to be excessively argumentative but the scope was given by the first post in this issue. In this post, I wrote there were _two_ problems. One of them was solved by URL @molnard asked if it was ok to close this issue. I said the other problem hadn't been addressed yet.

Do you understand what I meant by what I wrote here? Do you agree with it?


It would take me some time also to familiarize myself with the `rust-analyzer` internals. 😝

But I guess I could start with just shebang support and no manifest?


I'd recommend starting with an issue in their repo about detecting "cargo script"s and propose a mechanism for how to do it and see where the discussion goes.

Please cc me in that thread.


The changes are apply to namerequest. Hold it for "Way Of Navigating" to be done.


Looks promising for the first 4 hours and 5 minutes so far! I shall further test tomorrow when I will be back home again.
-------- Oorspronkelijk bericht --------Van: Anthony96922 ***@***.***> Datum: 20-07-2023 05:47 (GMT+08:00) Aan: Anthony96922/st-keygen ***@***.***> Cc: SpiderBlocker ***@***.***>, Author ***@***.***> Onderwerp: Re: [Anthony96922/st-keygen] ST announcement still playing (Issue #2)

With 0x49e508db ST displays a red message "FM processing used without license".

Try 0xeff52fff. This enables all unknown bits.

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


@diivi I have implemented the solution can you tell me how can i raise a pr and what all should I include ?


Yes I understand what you say and agree with that. However, we define the scope of our tasks as better suit us and I have explained that we are addressing the second problem as part of a bigger task that is the DoS prevention.


I'm new to NixOS, I have this error as well:

bash
jul 20 19:19:13 nixos systemd[1]: Starting Network Manager Wait Online...
jul 20 19:20:13 nixos systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=1/FAILURE
jul 20 19:20:13 nixos systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'.
jul 20 19:20:13 nixos systemd[1]: Failed to start Network Manager Wait Online.
warning: error(s) occurred while switching to the new configuration

 I put this line in my configuration.nix (`systemd.services.NetworkManager-wait-online.enable = lib.mkForce false;`), but then I get this error:

bash
$ sudo nixos-rebuild switch --upgrade
unpacking channels...
error: undefined variable 'lib'

 at /etc/nixos/configuration.nix:16:56:

 15| boot.loader.systemd-boot.enable = true;
 16| systemd.services.NetworkManager-wait-online.enable = lib.mkForce false;
 | ^
 17| boot.loader.efi.canTouchEfiVariables = true;
(use '--show-trace' to show detailed location information)
building Nix...

And I can't update anymore, so I am stuck and a fairly recent clean NixOS install. Is there a way to force the update for now? What is the best structural solution?

Thank you!


Looks like `nixos-generate-config` adds this in the beginning of /etc/nixos/configuration.nix:

[...snip comment block...]

{ config, pkgs, ... }:

whereas most people eventually modify that to `{ config, pkgs, lib, ... }:`, providing configuration.nix with the missing `lib` argument.

I think nixos-generate-config should be updated to include `lib` by default. Although the default config doesn't need/use `lib`, it quickly becomes something new NixOS users want to use.


For those looking for a working solution: URL
It probably needs to be updated to integrate the updates from URL but it'll work.
Some of the fixes we introduced in the fork are hardcoded and there's a need for matching your project's Kotlin version with the one used by the lib, hence the "kotlin" branch for lack of time adding it via a config plugin.
I'm not currently maintaining this fork since I don't use the library in my project.


Thanx for the quic reply.

I have added { config, pkgs, **lib**, ... }:

In the first line of my configuration.nix, but I get the same error...


Then please open a new issue or post on URL asking for help.


This issue has been mentioned on **NixOS Discourse**. There might be relevant details there:

 URL


Please tell me what version of the stereo tool does this work for ?! I'm new, I'm very interested in this project


Ok, this solved it for me: URL

Just dit `sudo nixos-rebuild boot --upgrade` and rebooted. I left the lib in the `{ config, pkgs, lib, ... }:`.

Thanx for the support!


I think this was fixed by #67664, so it should be fixed in VS 17.7
The missing documentation page is tracked in dotnet/docs#30361


Tested with "0xeff52fff" and got no messages after 24 hours running ST. Solved for me.


this is very good, could you help me install your key? I have raspberry 4, and HiFiBerry dac + adc.i am new to linux.... tnx


Run make-regkey with the name you want to get a registration key.

Example: ./make-regkey 'some name'

Then pass the key with the -k flag.


I have tried two more things;

- With software version 2.6, just for testing i disconnected only the MISO pin between the pcb and the airco.
 Doing this resulted in a MISO readout of zero, a voltage on the MISO pin on the airco side of zero,
 And the data worked only partially. It only send out data from the indoor unit as far as I could see.
- In software version 2.6, I commented out the while(1) so the software wouldn`t reboot, to see if for example MISO would later
 on become zero.
 After this the program seems to work and I get all the data. Also sending commands works. However the MISO does not go
 to zero.
 And also the serial output is clogging with "mhi_ac_ctrl_core.loop error: -4"


Hi!
I have made FM-preset from scratch again in fresh ST 9.92 installment, reg'd with 0xeff52fff flag and ST blocked through firewall. All licenses show green, but still 4h announcement is played through FM-output. I have e-mailed that preset to you (thecube); if you could have a look, would be great!


Removing the while(1) can damage the ac or your board as mentioned in Troubleshooting.md
There is no difference in measuring the pins in 1.4 and 2.6.
If the board is connected to your ac with a cable, maybe it is picking up some noise.


And please re-check your PCB if there is a short between MISO signal and another signal, maybe a bridge due to poor PCB quality or by solder. I suggest a loupe.


Thanks for your responses.
Yes I did read the disclaimer about damaging, I knew it was a bit risky.

Also I did look at #22 which is about the wrong level shifter,
I also looked at #26 and #84, but none seems to display exact behavior to what I am seeing.

So picking up some noise would sound reasonable... However, it does not explain the difference in 1.4 and 2.6.

Also a fault on the PCB would not explain that difference if you ask me.

I have though measured by multimeter,
And the only resistive values I saw where 10k/20k due to the pull/up/down resistors on the level shifter.
Measureable between ground and SCK/MOSI/MISO is some 10k/20k, and between SCK/MOSI/MISO also some 10k/20k.
Between VCC(12V) and SCK/MOSI/MISO it`s all measuring mega ohms.

I do have oscilliscopes and stuff to measure things, but unsure at the moment of what to measure.


If you have a logic analyser this will help.
Otherwise maybe with the oscilloscoop you can monitor the behavior of the MISO line at the board without the esp. It should be steady 0 Volt.
Otherwise strip the program to only measure the frequency repeatly and look with the oscilloscoop.


I don`t have a logic analyser readily available.
When I have some more time I`ll sure hookup a scope to at least look what the signals look like.

I just measured with my multimeter, the MISO pin reads a steady 2,6V when the PCB is connected to the airco. Even without the ESP on it. Without the PCB so measuring just the airco pins it the MISO pin reads 0V.
So at least this voltage must be coming from the on the PCB itself (including level shifter).

Am wondering now if it is due to the resistances on the level shifter.
So measuring with my scope I should be able te verify if it is a voltage diveded copy of SCK and/or MOSI.
Would suspect SCK since that is 5V.
(Although I am wondering why nobody else had the issue)
These are the level shifters I`ve used; URL

I`ll update next when I`ve had time to hook up a scope!


I am also fine with using the default GCP Keychain (cloud-aware) and thought simply annotating the Service Accounts with `iam.gke.io/gcp-service-account=kyverno-service-account@my-registry.iam.gserviceaccount.com` should have been enough. But it is not. Found the following issues/PRs regarding that:

 URL
 URL
 URL

Maybe adding documentation regarding `registryCredentialHelpers` and cloud-aware pull secret extraction is necessary here (or if there is already one, please point me to it).


Passing the manually created `imagePullSecret` to cosign package also works:

golang
package main

import (
 "context"
 "encoding/base64"
 "fmt"

 kauth "github.com/google/go-containerregistry/pkg/authn/kubernetes"
 "github.com/google/go-containerregistry/pkg/name"
 gcrremote "github.com/google/go-containerregistry/pkg/v1/remote"
 "github.com/sigstore/cosign/cmd/cosign/cli/options"
 "github.com/sigstore/cosign/pkg/cosign"
 "github.com/sigstore/cosign/pkg/oci/remote"
 corev1 "k8s.io/api/core/v1"
)

func main() {
 ref, err := name.ParseReference("eu.gcr.io/my-registry/foo:latest")
 if err != nil {
 panic(err)
 }

 // Output of `k get secret/regcred -o json | jq '.data.".dockerconfigjson"' -r`
 secBase64 := "OUTPUT"
 secData, err := base64.StdEncoding.DecodeString(secBase64)
 if err != nil {
 panic(err)
 }

 // Secret itself
 secrets := []corev1.Secret{
 {
 Type: corev1.SecretTypeDockerConfigJson,
 Data: map[string][]byte{
 ".dockerconfigjson": secData,
 },
 },
 }

 // Pull secret to auth keychain
 authsec, err := kauth.NewFromPullSecrets(context.TODO(), secrets)
 if err != nil {
 panic(err)
 }

 // Fetch the manifest using default credentials.
 img, err := gcrremote.Get(ref, gcrremote.WithAuthFromKeychain(authsec))
 if err != nil {
 panic(err)
 }

 // Prints the digest
 fmt.Println(img.Digest)

 ctx := context.TODO()

 var remoteOpts []remote.Option
 ro := options.RegistryOptions{}
 remoteOpts, err = ro.ClientOpts(ctx)
 if err != nil {
 panic(err)
 }
 remoteOpts = append(remoteOpts, remote.WithRemoteOptions(
 gcrremote.WithAuthFromKeychain(authsec),
 ))

 signedPayload, err := cosign.FetchSignaturesForReference(ctx, ref, remoteOpts...)
 if err != nil {
 panic(err)
 }
 fmt.Println(signedPayload)
}


@Akaame Thank you for opening the issue. Is this related to URL

Can you please confirm


@vishal-chdhry Thanks for the quick response. And, no, the second time around it fails with the same error. I do not think the issues are related. Should I still install the tip of main branch and try?


@Akaame That would be great!

Please follow the instructions here to try this out


@Akaame I believe the cause of the issue is `validateFailureAction` being set to `Audit`.: URL
It will be fixed in 1.10.2

To fix it right now, you can set `validateFailureAction` to `Enforce` (Setting it to `Enforce` once and then setting it back to `Audit` will also fix it for now, you won't have to do it in 1.10.2)

Let me know if this fixes the issue


helm uninstall kyverno
kubectl create -f URL

Patched the deployment with `--imagePullSecrets=regcred`
and changed the `ClusterPolicy` to have `Enforce` as failure action. IT WORKED!. Then, reverted it back to `Audit`. It still works for both Policy Failure and Pass cases.

@vishal-chdhry Thanks!


Duplicate of URL
Closed in URL
Will be in the v1.10.2

I am closing this issue.


**I installed this archive on a flash card, and updated it to the latest version via the web interface. How can I run this code?
I'm new. Sorry for such a stupid question.

 URL


I was not able to acquire a crash or coredump, however, we have recently seen this issue occurring on a Redhat server running pwsh version 7.2.7. Removing the write permissions to the cache directory and deleting the cache files resolved the issue.

So this is also seems to be an issue for Powershell 7.2.x


Yes. I consider this closed. We can follow up on other formats if the need arises.


i my case Wifi Problem and D1 mini was a to small Cap on 3.3V on some D1 Mini PCB
got Spikes on 3.3V during WLAN data transfer
so its a good Idea to add a extra minimal 10uF CAP : 3.3V / GND
symptom:: Connect to WLAN fail , loss connection


I think we were still waiting to hear back from some folks about WASM? I'm happy to close this an open a separate ticket for that since the above PR has been merged.


The PR for the wasm columns definition: tc39/source-map-spec#14


Hello,
How does it works please ?
Chocolatey is installed in my Windows 10. Which line of code should I run in Windows powershell ? Is there a tutorial ?
Thank you


Thanks a lot @nosvalds. Would you mind adding the version of the Web-SDK you found the issue on?

Cheers,
Marco


Hello. Who was able to solve this problem? I ran into it and all methods do not help


You can only initialise a single formBuilder instance at a time and need to wait for the promise to resolve before moving onto initialising the next instance.

This can be done either via a recursive function per URL

or via awaiting the promise per the documentation.

The initial code by @Sharad2390 can be rewritten with the ready callback being async and the initialisation await the promise object of formBuilder

js
jQuery(async function($) {
 var fbTemplate = document.getElementById('fb-editor');
 var options = {
 disabledActionButtons: ['data','clear','save']
 };
 var formBuilder = await $(fbTemplate).formBuilder(options).promise;
 document.getElementById('getJSON').addEventListener('click', function() {
 alert(formBuilder.actions.getData('json'));
 });
 var fbTemplate1 = document.getElementById('fb-editor1');
 var options1 = {
 disabledActionButtons: ['data','clear','save']
 };
 var formBuilder2 = await $(fbTemplate1).formBuilder(options1).promise;
 document.getElementById('getJSON1').addEventListener('click', function() {
 alert(formBuilder2.actions.getData('json'));
 });
});


Lets add a warning in documentation of these routines regarding device synchronization


Oh yeah, forgot I switched to the publish plugin that does that for free


I just re-read my question and @tomball's answer and I see that I was unclear about what I was asking exactly.

What I meant to ask was: Can I build J2ObjC with my `JAVA_HOME` environment variable set to JDK 17? I just tried it and the answer right now is: no. The build fails for me with the following error:

shell
...
building cycle_finder jar
building jre_emul archs: iphone64 simulator64 simulator
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
translating jre_emul sources
install -m 0644 build_result/cycle_finder.jar ../dist/lib/cycle_finder.jar
error: internal error translating "/Users/adil/Work/j2objc/jre_emul/openjdk/src/macosx/classes/sun/nio/fs/MacOSXNativeDispatcher.java"
java.lang.IllegalAccessError: class com.google.devtools.j2objc.javac.TreeConverter$1 (in unnamed module @0x1a708820) cannot access class com.sun.tools.javac.parser.Tokens$Comment$CommentStyle (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.parser to unnamed module @0x1a708820
 at com.google.devtools.j2objc.javac.TreeConverter$1. (TreeConverter.java:1477)
 at com.google.devtools.j2objc.javac.TreeConverter.convertInner(TreeConverter.java:280)
 at com.google.devtools.j2objc.javac.TreeConverter.convert(TreeConverter.java:261)
 at com.google.devtools.j2objc.javac.TreeConverter.convertCompilationUnit(TreeConverter.java:232)
 at com.google.devtools.j2objc.javac.JavacParser.parseFiles(JavacParser.java:212)
 at com.google.devtools.j2objc.pipeline.FileProcessor.processBatch(FileProcessor.java:137)
 at com.google.devtools.j2objc.pipeline.FileProcessor.processInputs(FileProcessor.java:67)
 at com.google.devtools.j2objc.pipeline.TranslationProcessor.processInputs(TranslationProcessor.java:84)
 at com.google.devtools.j2objc.J2ObjC.run(J2ObjC.java:127)
 at com.google.devtools.j2objc.J2ObjC.main(J2ObjC.java:176)

Exception in thread "main" java.lang.NullPointerException: Cannot invoke "com.google.devtools.j2objc.ast.CompilationUnit.getSourceFilePath()" because " " is null
 at com.google.devtools.j2objc.javac.JavacParser.parseFiles(JavacParser.java:214)
 at com.google.devtools.j2objc.pipeline.FileProcessor.processBatch(FileProcessor.java:137)
 at com.google.devtools.j2objc.pipeline.FileProcessor.processInputs(FileProcessor.java:67)
 at com.google.devtools.j2objc.pipeline.TranslationProcessor.processInputs(TranslationProcessor.java:84)
 at com.google.devtools.j2objc.J2ObjC.run(J2ObjC.java:127)
 at com.google.devtools.j2objc.J2ObjC.main(J2ObjC.java:176)
make[1]: *** [/Users/adil/Work/j2objc/jre_emul/build_result/Classes/.translate_mark_jre_emul] Error 1
make: *** [jre_emul_dist] Error 2

This is not a blocker for me. Taking @tomball's answer into consideration, I have both JDK 11 and 17 installed on my machine. I have my `JAVA_HOME` environment variable set to JDK 17 except in a small number of isolated processes where I change it to JDK 11. For example, when building J2ObjC and when running the `j2objc` command.


Just wanted to mention that New-PnPUPABulkImportJob works fine with an app registration with Certificate and permissions assigned only in AAD with SharePoint "Sites.FullControl.All" and "User.ReadWrite.All" and no permissions assigned in SPO at /_layouts/15/appinv.aspx , tested it this week in 2 different tenants.


Thanks a lot @jackpoz, will definitely try this out. Glad to get rid of this ACS dependance.


So, to summarise, the actual error seems to be that NM waits for startup of some interfaces it thinks it should manage but they're never communicated as up to NM because NM was never supposed manage that interface?

When I say `nmcli`, NM thinks it does not manage my tailscale0 interface:

tailscale0: unmanaged
 "tailscale0"
 tun, sw, mtu 1280

Why would it be waiting on it then? The other interfaces are up and I'm sending you this message via one of them, so it can't be waiting on those.

I'll try to explicitly add it to `networking.networkmanager.unmanaged` and report back after a few rebuilds in a few weeks.


No, `nm-online` is just weirdly broken and locks up if you try to do it on an already running system. It's probably an easy code fix but I'm not familiar with the codebase at all.


@dumb0002 Thanks for creating this issue. We would need some more information on the gaps that you talk about.

@astefanutti @anishasthana Should the integration step happen through the ADR process?


Yep! We definitely shouldn't start any implementation work until that an ADR is approved.


Thanks, @anishasthana can you help with pointers to ADR to get started?


Hello. Thank you for giving a hint, which helped partially, but now I have encountered another problem in the form, the fields are displayed correctly, but when I want to get data from the form in json format, I have the same code on page 2 and 3. I've been struggling with this code for several days, I don't know what to do anymore.

I have 3 pages now:
1 - Text field
2 - Date field
3 - Header fields

These fields in the form will visually display correctly. There is no error with "actions.getData" now, but when I view the result var json = fb.actions.getData('json', true); then I get

1 - Text field
2 - Header fields
3 - Header fields

After the first it is duplicated

document.addEventListener('DOMContentLoaded', async function() {
 jQuery( function ($) {

 var fbOptions = {...};

 fbInstances.push($(".build-wrap").formBuilder(fbOptions));

 setTimeout(function() {
 $.each(setFormData, function(i, item) {

 if(fbInstances[i]) {
 fbInstances[i].actions.setData(item);
 } else {
 addPageLoading(item);
 }
 });
 }, 2000);

 // add pages form
 async function addPageLoading(data){
 console.log('addPageLoading')
 const tabCount = document.getElementById("tabs").children.length;
 const tabId = "page" + tabCount.toString();
 const newPageTemplate = document.getElementById("new-page");
 const newTabTemplate = document.getElementById("add-page-tab");
 const newPage = newPageTemplate.cloneNode(true);
 newPage.setAttribute("id", tabId);
 newPage.classList.add("build-wrap");
 const $newTab = newTabTemplate.cloneNode(true);
 $newTab.removeAttribute("id");
 const tabLink = $newTab.querySelector("a");
 tabLink.setAttribute("href", "#" + tabId);
 tabLink.innerText = "Page " + tabCount;
 $newTab.append($(" X ")[0])

 newPageTemplate.parentElement.insertBefore(newPage, newPageTemplate);
 newTabTemplate.parentElement.insertBefore($newTab, newTabTemplate);

 fbPages.tabs("refresh");
 fbPages.tabs("option", "active", tabCount - 1);

 if(data.length){
 fbOptions.formData = data;
 }else{
 fbOptions.formData = [];
 }

 var formBuilder_load = await $(newPage).formBuilder(fbOptions).promise;
 fbInstances.push(formBuilder_load);

 }

 // Get JSON and send form
 $(document.getElementById("getJSON")).click(function () {

 const allData = fbInstances.map((fb) => {
 var json = fb.actions.getData('json', true);
 return json;
 });
 $("input[name='json']").val("["+allData+"]");
 $("#design-form").submit();

 });

 });
});


Thanks @dumb000!,

@asm582 , I tagged this one as well with multi-cluster label.


@asm582, I updated the information in this issue - let me know if additional changes are needed. Also, I created issue # #524 to focus on the k8s versioning issue only as suggested by @dmatch01 ,


We have an ADR template (and repository) at URL Can you please raise a PR there? We track any major decisions in that repo.


I can't reproduce :-(
At least not when tested on _Wayland_.
Also tested with AND without a custom key bound to the switching.


@aaronrobertshaw, @kevin940726, @youknowriad, @Mamaduka let me know if you have any thoughts on whether a standard WP custom taxonomy is the best approach for this.


Is that something that has to be fixed upstream? If so, could you create an issue for it?


Reading through those. Are we using the mentioned `-s` flag? If so, maybe we can remove it? Running `nm-online -s` manually hangs for me, while `nm-online` (without `-s`) seems to work correctly.


Alright, I'll stick with my workaround then for now. I would like to contribute a real fix for this or sort it out properly, but don't know how to continue.


Hi @Abacaxi-Nelson here is what I did

coffee
@formBuilder = []
startIndex = 0
 _initMultipleFormBuilder = (startIndex, elements) ->
 if startIndex
 form.element = elements[startIndex]
 @formBuilder.push form
 startIndex++
 _initMultipleFormBuilder(startIndex, elements)
 )

I use a recursive function. I haven't tracked it down why it works this way yet. Let me know if there is still a problem.


Agreed, taxonomies are more suited for this and are more performant when querying the items vs. post meta.

P.S. We should probably drop the `custom` from the name - `wp_pattern_category`. The entities that ship with WordPress are native.


I too think taxonomy is the way to go. The reason is that the template parts area is also registered as a taxonomy and I think the pattern should be able to have a similar design.


Gonna close as this seems stale, and I don't think this is needed any more.

With the new structure, having historical test results in the same file is no longer a problem as they can be easily ignored. Separating them out would most likely make the code more complicated. I'm open to other opinions though.


I had this problem for well over a year, but since I added this to my `configuration.nix` the problem has not reoccurred:

nix
systemd.services.NetworkManager-wait-online = {
 serviceConfig = {
 ExecStart = [ "" "${pkgs.networkmanager}/bin/nm-online -q" ];
 };
};

Nor have I had any other network problems.

Also,

shellsession
$ nm-online -s
Connecting............... 30s [started]
$ journalctl -b -u NetworkManager-dispatcher.service
Jul 10 16:24:41 melchizedek systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 10 16:24:41 melchizedek systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 10 16:24:51 melchizedek systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 11 17:43:59 melchizedek systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 11 17:43:59 melchizedek systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 11 17:44:09 melchizedek systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 14 18:41:15 melchizedek systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 14 18:41:15 melchizedek systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 14 18:41:25 melchizedek systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
...
$ last reboot -1
reboot system boot 5.15.119 Mon Jul 10 16:24 still running

`NetworkManager-dispatcher.service` seems to run at various times that aren't related to reboots or `nixos-upgrade switch`


Spike issue to investigate Solr performance issues and identify specific actions to take. An issue will be created for each action that is identified. (As per 2023/07/30 prioritization meeting).


@neilmayhew what does that exactly do? If I understand the man page correctly, `-q` only omits the output, without changing any functionality


Have made that change on the PR. In my mind I was thinking of `custom` as being the user's custom patterns as opposed to the theme/.org patterns, but I can see how that wording would be confusing.


@pinpox The `-q` was already there, and I'm just removing the `-s`. Sorry I didn't make that clearer.

With the extra configuration:

ini
$ systemctl cat NetworkManager-wait-online.service
# /etc/systemd/system/NetworkManager-wait-online.service
[Unit]
Description=Network Manager Wait Online
Documentation=man:nm-online(1)
Requires=NetworkManager.service
After=NetworkManager.service
Before=network-online.target

[Service]
# `nm-online -s` waits until the point when NetworkManager logs
# "startup complete". That is when startup actions are settled and
# devices and profiles reached a conclusive activated or deactivated
# state. It depends on which profiles are configured to autoconnect and
# also depends on profile settings like ipv4.may-fail/ipv6.may-fail,
# which affect when a profile is considered fully activated.
# Check NetworkManager logs to find out why wait-online takes a certain
# time.

Type=oneshot
ExecStart=/nix/store/r7fwxkxbgmwyrff5n03r9nchzskj59n9-networkmanager-1.40.16/bin/nm-online -s -q
RemainAfterExit=yes

# Set $NM_ONLINE_TIMEOUT variable for timeout in seconds.
# Edit with `systemctl edit NetworkManager-wait-online`.
#
# Note, this timeout should commonly not be reached. If your boot
# gets delayed too long, then the solution is usually not to decrease
# the timeout, but to fix your setup so that the connected state
# gets reached earlier.
Environment=NM_ONLINE_TIMEOUT=60

[Install]
WantedBy=network-online.target

# /nix/store/2ma3yvlqmj94dr6v24nkwmspgxfpfnmq-system-units/NetworkManager-wait-online.service.d/overrides.conf
[Unit]

[Service]
Environment="LOCALE_ARCHIVE=/nix/store/g135laybfk1c7bm2zhrh7x6dv884qxal-glibc-locales-2.35-224/lib/locale/locale-archive"
Environment="PATH=/nix/store/l6jgwxkc3jhr029vfzfwzcy28iyckwsj-coreutils-9.1/bin:/nix/store/gn1s1s5z19cf0wiir2cd38jckcjc6kn6-findutils-4.9.0/bin:/nix/store/pvb117r7fhwb08717ks21a6y>
Environment="TZDIR=/nix/store/z0kg1c0f8fx6r4rgg5bdy01lb2b9izqg-tzdata-2023a/share/zoneinfo"

ExecStart=
ExecStart=/nix/store/r7fwxkxbgmwyrff5n03r9nchzskj59n9-networkmanager-1.40.16/bin/nm-online -q


## 20230801 Update: (AL2023/NodeJS18 on 2.10.0 Release)

### Required Steps

* Update all AMIs to have NodeJS14/16/18 support.
* Update all CI docker images to have NodeJS14/16/18 support.
* Update all Release docker images to use NodeJS18 as the base node version for OSD.
* Deprecate all CentOS7 images in build systems and replace with the RockyLinux8 images (Except client release image as it does not require nodejs18 by default for now).
* Work with OSD team members to ensure all OSD core and plugins are locking to NodeJS 18.16.0 at least on 2.x/2.10 branches. 1.x can pending.
* Since KNN already update the dependencies such as gcc to v7 and cmake to 3.23.3, it is easier for us to bring them onto either Rockylinux8 or AL2023. Starting from now k-NN will not be able to run on OS with glibc version lower than 2.28 (previously 2.17)
* Work with doc team to update the doc compatibility charts to remove CentOS7 support and add AL2023.
* Test all the pipelines on the new servers.

### Optional Steps
* Need to discuss after the 2.10.0 release whether or not 1.x line need to upgrade as well.
* Have separate pipeline to test NodeJS14 bc abilities.


cc @vstinner I sent a PR for this, are you the right person to review it?


+1 to pattern categories via a taxonomy.

The querying performance, consistency with template parts, and leveraging of existing features are all compelling reasons to me.


Hi again!

Finally found which feature causes the 4h announcement. I Have been scanning along more than 30 four-hour runs since July 25th and of course it was the very last possibility left :-)

It is definitely the Advanced Clipper. It's not the Advanced Cipper as a whole, but a subsetting of it. I can further narrow down the exact subsetting if needed; pls advise if I need to.


Glad you find AVNC useful! I have tried to make it as seamless as possible.

There is already an option to automatically open "virtual keys" with the soft-keyboard (`Settings => Input => Virtual keys`). But if you are talking about showing them when connection is started, that can be implemented too.


Update from McAfee: the McAfee release that will tackle this issue is planned for end of August.
Thank you


I do have that option checked, i just would like it on screen by default. Bonus points for an option to have a "show keyboard" button on there too ;)


I will change the `Open with keyboard` option to a list with three options: Open manually, Open automatically, and Open with keyboard.


There's another low hanging fruit-like improvement that can be handled as a compact, self-contained issue: Inside SearchIncludeFragment (the class file that runs the search for the collection page - i.e., where most searches issued by Dataverse originate) every search is literally run twice, in order to obtain the result counts for the object types NOT currently selected by the user. While the second search is necessary in order to obtain these count(s), it can be run in a more economical way, that can reduce the amount of work for solr to perform by up to 50%.
The details are spelled out in a #dv-tech thread and can be copy-and-pasted into an issue once we open it.


@luddaniel I just looked at #8941. If it can be addressed by simply indexing fileCount as another numeric field during indexing, that does sound very straightforward, and I don't know why we haven't implemented it yet/have overlooked it.
Generally, we absolutely need to reduce the number of SQL lookups that are required when we process list of results as they come from Solr. Hopefully we can address it soon.


As I see you have added them to comments here above, they'll be assigned to you automatically🙂


@joshtriplett and I discussed how to handle `package.edition`. This is a draft of what we'd want to do which the rest of the cargo team would need to sign off as part of stabilization (ie doesn't represent the whole team)

## Rough plan

- Perma-warning for now
 - `cargo fix` to address the warning it (not required for first release)
 - If we feel this was a mistake, we can always change this to always being required in a future edition
- In the future, we could also explore having an edition-wrapper binary like `cargo-2018-edition`, depending on feedback
- If we have a `cargo new --script`, it will include a manifest in the file

## Use cases

A user might skip on edition and be fine ignoring the warning
- Bug reproduction (usually can tell from timeframe; ideally short-lived anyways)
- Throwaway scripts

Either always want the edition set or don't want to include code that produces warnings
- Long-term scripts
- Clean documentation that doesn't produce warnings

With the use cases for skipping an edition, that leaned us towards having the warning instead of requiring it.

## Options considered

Default to an edition (the one introducing cargo script) unless specified
- Effectively always requires the edition once people want a new edition
 - Bloats educational material

~~Insert edition on first run~~
- We don't want to be modifying code

~~Edition flag~~
- `/usr/bin/env` portability issues

edition wrapper (cargo-2018)
- Bloated on windows (esp 40 years from now...)
- `cargo 2018` is weird and requires special parsing to not error out
- `car\t` is annoying for completions
 - Already true for third-party commands. (Possibly already true for first-party commands?)
 - Will it be overwhelming though in 40 years

Require an explicit edition

Perma-warning on missing field.
- This effectively makes an explicit edition mandatory (for anything except toys and bug-reproductions)
- If we have a `cargo new --script`, should it always generate the manifest so we get edition?
 - What to call the flag?
 - `cargo new foo.rs` does it based on extension?
 - Doesn't help when people don't want an extension
 - `chmod +x`
 - `#!` block
 - Insert manifest


TLDR: I think the current cargo-script proposal is cutting corners, and I'm fine with cutting corners, but I think it's cutting them in the wrong places. It's cutting corners with the edition, but is overly verbose with regards to manifest inclusions where you have to nest it in two constructs.

Do bug reproductions and throwaway scripts really need the latest edition? The rustc testsuite is still on edition 2015, and many of the tests in the cargo testsuite have edition 2018 (roughly the same number as edition 2021 tests). I think defaulting to edition 2021 wouldn't be that bad as noted.

This has a way nicer "pressure curve" on users than a `rustup update` suddenly breaking some script that started as throwaway script but now is powered by a cronjob: people will eventually notice that they are on an old edition and add the flag.

That was the whole deal of the editions RFC: breakage, but safe, and opt-in. `rustup update` should not cause breakages for anybody.

For the bloat concerns, see my suggestions to reduce the overhead to include Cargo.toml (to just use `/**/` instead of rustdoc markdown code sections) and specify the edition (#12301). That would reduce it from:

`rust
#!/usr/bin/env cargo-script
/*!

Cargo.toml
[package]
edition = "2021"

*/

fn main() {
 println!("Hello, world!");
}

`

to:

`rust
#!/usr/bin/env cargo-script
/*
[package]
edition = 2021
*/

fn main() {
 println!("Hello, world!");
}

`

And that's with the standard Cargo.toml inclusion syntax proposal of mine. But I want to repeat points from earlier discussions on discourse about having custom edition syntaxes. My favourite is parsing a `// edition: 2021` like comment, like it is done for rustc's testsuite.

e.g.:

rust
#!/usr/bin/env cargo-script
// edition: 2021

fn main() {
 println!("Hello, world!");
}

But you can also have `#![edition = "2021"]` if you don't like comments (but there is precedent in both the compiletest test suite, rustdoc comments, and ).

These two ideas would make requiring the edition, or defaulting to a specific one, much easier.

The current way of specifying the edition in Cargo.toml wasn't particularly optimized for brevity, and it didn't have to be because it was designed for use cases where there is a lot of bloat already. The way of specifying the edition is not set in stone and can be evolved. I think the core promises of the edition RFC to deliver opt-in breakage should *not* be subject to change or exceptions however. Even the playground is paying the edition toll by adding it to the URL (and notice how it doesn't use builtin manifests?).


Also, IMO, any way to require less syntax to specify the edition is helpful regardless of the discussion about what cargo should do by default or whether it should require an edition: users will want to specify it one way or another, and if it's easier than the current proposal, they are helped.

Also, a possible idea to lessen the impact of defaulting to the latest edition, one could limit that to cases where no manifest is embedded. If a script has a manifest embedded already, requiring an edition isn't burdening users a lot even with the status quo of specifying the edition, because they just need to add one/two lines in that instance.


@est31 is not decided and has been our biggest open issue on this. Josh and I also talked about it and I need to process the notes and post them but understand that we are still working through this and wanting to have involvement of both T-cargo and T-lang in this.


Hi @takagi @ev-br @andfoy I could really pick your brains here regarding the general-matrix eigensolver. Why isn't it possible to rewrite the algorithms such that you generate a Hermitian matrix? What's special here? (Context: On the cuSOLVER side, I learned that there's great hesitation in adding the general solver because there's no serious use case. A lot of `eigvals` calls were done, in our opinion, only because people either didn't know `eigvalsh` exists or didn't know their matrix is Hermitian/symmetric. Also, `svd` might help for a lot of use cases ( URL We would love to know what's missing in this understanding.)


Thanks @leofang for letting my head up. As for `numpy.roots`, the roots of a polynomial is found as the eigenvalues of its companion matrix, and the matrix is not symmetric/Hermitian.

 URL

I suppose we need eigenvalues themselves, not just decomposition, so svd may not work.

However, yes, we might use another algorithm for root finding on GPU that does not use eigenvalues.

 URL

I’ll look into other lines that use eigvals...


I would argue that Rust's philosophy on explicitness is one of the things that made it successful, and it's certainly one of the things I love about it most.

### Manifest

I'm not particularly a fan of using `/* [...] */` for the manifest, as it looks way too much like an ordinary comment, not just to the developer, but also anything automated examining the code.

The good thing about module-level documentation comments is that developers are already familiar with them, and the code to parse, highlight, and extract them is pretty much in place - albeit only for the `rust` language for now as far as I know.

Another place to put the manifest could just be a documentation comment on `main` itself.

rust
#!/usr/bin/env cargo

use clap::Parser;

#[derive(Parser, Debug)]
#[clap(version)]
struct Args {
 #[clap(short, long, help = "Path to config")]
 config: Option ,
}

///
cargo
/// [dependencies]
/// clap = { version = "4.2", features = ["derive"] }
///

fn main() {
 let args = Args::parse();
 println!("{:?}", args);
}

While this certainly has the drawback of potentially moving the dependencies further down the code, it clearly couples the entry point with everything it needs to start.

### Edition

As for the edition question, and like @poliorcetics has said, I would very much love for `cargo new --script` to generate the manifest with `edition` included, just like `cargo new --lib/bin` does, for the sake of both explicitness and consistency. I don't feel like that extra three lines within the code is going to degrade the developer experience so much that it would ever truly be an issue, not even for beginners.

In fact, someone new to the language might not even know what an edition is, and could have a hard time figuring out why the default value (whatever it may be) doesn't work for them.

rust
#!/usr/bin/env cargo

use clap::Parser;

#[derive(Parser, Debug)]
#[clap(version)]
struct Args {
 #[clap(short, long, help = "Path to config")]
 config: Option ,
}

///
cargo
/// [package]
/// edition = "2021"
///
/// [dependencies]
/// clap = { version = "4.2", features = ["derive"] }
///

fn main() {
 let args = Args::parse();
 println!("{:?}", args);
}

---

I agree with @est31 in that using sane defaults for scripts not containing a manifest at all is a reasonable shortcut for when you just need to get something out quick, and explicitly defining an edition should be required once a manifest _is_ included.


@NickyNL have you managed to solve the issue? I was facing the same issue. I have made a complete different hardware version though (manually soldered with stuff I had laying arround).
Initially I used the same pinning as described in the repository.
I solved the issue by changing the MISO pin to GPIO16 (Seems like internal crosstalk of the ESP).
I have created al sorts of filtering initially that didn't help, changing pin did. You might need some changing when using the PCB version.

Groeten


@SmOeL-swdev thanks for the tip! Will definitely try swapping to that pin soon.

It also was a good trigger that I still had to do something.
As it is "working" as is, it sometimes gets forgotten.

So, hereby at least some captures with a oscilloscope;
Measured straight on the pins on the pcb coming from the AC.
With the ESP on the pcb as well.

Red MISO Blue SCK (2)
Red MISO
Red MISO Blue SCK