Spec: SR-IOV forwarder Device Plugin

User configures Forwarder with the list of PF -> service matches.
0000:00:01.0:
  capabilities:
  - intel
  - 10G
  services:
  - service-a
  - service-b
0000:00:02.0:
  capabilities:
  - mlx5
  - 10G
  services:
  - service-b
  - service-c

Forwarder creates all available VFs for the given PFs and generates tokens.
0000:00:01.0 -> 32 VF -> 32 * { service-a/intel, service-a/10G, service-b/intel, service-b/10G }
0000:00:02.0 -> 16 VF -> 16 * { service-b/mlx5, service-b/10G, service-c/mlx5, service-c/10G }

Total:
- 32 * service-a/intel
- 32 * service-a/10G
- 32 * service-b/intel
- 16 * service-b/mlx5
- 48 * service-b/10G
- 16 * service-c/mlx5
- 16 * service-c/10G

In the terms of Device Plugin - token is a device. Forwarder advertise tokens. In the beginning all tokens are in free state.
Client pod requests tokens.
resources:
  limits:
    service-a/intel: "1"
    service-b/10G: "1"

Device Plugin selects 2 tokens for the client, sets them in allocated state and injects theirs IDs into the Client pod via environment variables.
NSM_SRIOV_TOKENS=service-a/intel:c2024bf1,service-b/10G:ad6167d6

Client requests connection using token ID.
Request.MechanismPreferences = []{
    {
        Cls: cls.LOCAL,
        Type: vfio.MECHANISM,
        Parameters: {
            tokenID: "ad6167d6",
        },
    },
}

Forwarder filters available PFs by token and selects VF for the connection. For the selected VF Forwarder sets passed token in in use state and sets 1 token for the other supported by VF token types in closed state and marks them as unhealthy for the Device Plugin. Tokens to become closed first are selected from the free tokens, if there is no free, tokens are selected from the allocated tokens.
token: service-b/10G{ad6167d6}
PFs supported:
- 0000:00:01.0
- 0000:00:02.0
VF selected: 0000:00:02.4
token state changes:
- service-b/10G{ad6167d6} -> in use
- service-b/mlx5{b6ce9dc3} -> closed + unhealthy
- service-c/mlx5{a529b8ef} -> closed + unhealthy
- service-c/10G{5fbffeb4} -> closed + unhealthy

When client closes connection, in use token becomes allocated and all related closed tokens become free and healthy for the Device Plugin.
When client disconnects from the Forwarder, allocated token becomes free.

Question... if we are statically configuring services to PFs... how does that link up with the real registry for the network service registry domain?
If we are configuring multiple capabilities for each PF... how does that map to the Device Plugin scheduling URL that has one capability?

My fault - it is not a service but serviceDomain. We can make some assumption that there is some set of Endpoints over the PF labeled as serviceDomain=... and there is at least one of them registered with the service we need. If not, request will fail on discovery stage.

PF provides multiple token names: { service/intel, service/10G }. After client selects VF using one of the tokens, all the other tokens are marked as closed and set unhealthy for Device Plugin so it stops scheduling them to clients and reschedules clients for which those devices has been allocated.

PF = 2 * { service: intel, 10G } -> []{
    service/intel{1} - free,
    service/10G{2} - free,
    service/intel{3} - free,
    service/10G{4} - free
}
client-1  -allocate->  service/intel{1} - allocated
client-2  -allocate->  service/intel{3} - allocated
client-3  -allocate->  service/10G{2} - allocated
client-1    -use->    service/intel{1} - inUse, service/10G{4} - closed (first close free, then allocated)
client-3    -use->    service/10G{2} - inUse, service/intel{3} - closed (don't close inUse)
* * * reschedule client-2 to another node * * *


Implement CSS4 hex notation

As seen in https://github.com/kivy/kivy/pull/3963, the current hex implementation does not handle alpha correctly.
https://github.com/kivy/kivy/blob/b72d1735a91b5cabad8343e8d63f84c840df1a96/kivy/utils.py#L90-L114
Luckily CSS4 comes with a hex notation that supports alpha, it would be great to follow that specification, supporting the 6 (already implemented) and 8 digit notation should be enough.
https://drafts.csswg.org/css-color/#hex-notation

Hm, the util functions already return the correct values, the incorrect markup alpha must be coming from somewhere else.


Make server streaming functions suspending

Currently RPCs which return a single value are suspend functions, it probably makes sense to be consistent, making all service functions suspend. This also allows certain natural implementations other than using the produce function. In my case, my service function is calling to another suspend function which returns a ReceiveChannel, map is then used to transform the results from that channel into gRPC response objects.

👍


cudf-udf integration test against python3.9 [skip ci]

To fix https://github.com/NVIDIA/spark-rapids/issues/7773
RAPIDS 23.06 drops python 3.8 packages and supports python3.9 and 3.10

as it touchs testing scripts, we cannot skip ci here

build

Going to merge this one. Lets keep monitoring nightly runs status


Improve API behavior, add top-level prefetching

api: use a client-side mapping for travel advice
We only get travel advice from the map layer and full forecast API, not
the fragment API, which makes relying on that field problematic. It
looks like the extant web application is simply using a client-side
mapping, anyway, instead of the API fields, so we can do that as well.
Signed-off-by: Steve Kuznetsov<EMAIL_ADDRESS>
hooks: cache ~static data forever
The avalanche center metadata and map layer contain relatively static
data (like the name of the avalanche center and where it is in the
country), so we can cache these values for the lifetime of our app and
re-fetch them infrequently.
Signed-off-by: Steve Kuznetsov<EMAIL_ADDRESS>
*: pre-fetch all data for the forecasts
On app load, we will now be fetching the center metadata, map layer, all
forecasts that pertain to our zones, and all media in all of the
forecasts. This will allow us to make sure that all data is present for
the user regardless of whether they've looked at all the forecasts
before going out of service.
Signed-off-by: Steve Kuznetsov<EMAIL_ADDRESS>
AvalancheTab: add a key to the collapsible cards
Signed-off-by: Steve Kuznetsov<EMAIL_ADDRESS>
Partially addresses #54

@floatplane attempted to address all of your comments!


[language-rust-bundled] Syntax highlighting does not support "raw identifiers"

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Rust has a syntax to escape reserved keywords, to use them as identifiers.
See: https://doc.rust-lang.org/edition-guide/rust-2018/module-system/raw-identifiers.html
Using this syntax breaks the syntax highlighting in atom.
Steps to Reproduce

Create a file with the following content:

// example rust file

use r#type::Type;

fn match() {}

fn main() {
    println!("Hello World");
}

remove the r# from type and it should highlight the code correctly.

Expected behavior:

Actual behavior:

Reproduces how often:
100%
Versions

atom --version
Atom    : 1.50.0
Electron: 5.0.13
Chrome  : 73.0.3683.121
Node    : 12.0.0

apm --version
apm  2.5.0
npm  6.14.7
node 14.9.0 x64
atom 1.50.0
python 3.7.4
git 2.28.0

uname -rsm
Linux 5.8.5-arch1-1 x86_64

Additional Information
This syntax can be used everywhere, where an identifier can be used. For example, it will happen with
struct r#enum {}

enum r#enum {}

fn r#macro(r#macro: String) {}

Seems to happen when using proc macros with arguments too:

$ atom --version
Atom    : 1.50.0
Electron: 5.0.13
Chrome  : 73.0.3683.121
Node    : 12.0.0

$ uname -rsm
Linux 5.4.0-39-generic x86_64

Looking into it some more, it seems that in certain contexts, raw identifiers parse fine, so I imagine that this is largely an issue of precedence. For example:
let r#not_keyword = 0;

parses fine, but:
let r#crate = 0;

gives priority to the keyword, rather than treating it as a raw identifier, and as mentioned earlier, in other places, breaks parsing entirely.
As @Askaholic mentioned, parsing also breaks on attribute macros with arguments. I have an idea for why this might be, but I need to do some more testing before I can be certain.


Update A Simple Game

Updated the A Simple Game example to match the new version of the tutorial after following the feedback from the team. Added a preloader to prevent long load times.

This is more engineered than I was expecting. Excluding music via the preload filter is enough, in which case the usual newMusic() and play() results in the browser commencing playback once a few seconds have buffered (in theory instantaneously if the music is created in create() then played on user interaction). It's almost impossible to go wrong - libGDX just pipes an Audio into Web Audio, which isn't that far removed from a plain old <audio>.

I dunno, this stuff isn't documented well. I'm just glad it works at all. Thanks for the suggestion.

It really isn't. Blatantly false wiki excerpt when it comes to music, that I don't remember if I've changed in a fork:

From 1.9.12 on, you can decrease your preload time a lot if you use asset manager to load your assets later. [...] Make sure these files are only loaded via AssetManager, otherwise your game will freeze when using such assets.

By all means, there can be reason to AssetMan your music, but for the most part it just clogs up your download queue.


Not working with ion-content inside ion-tab

Please check this codepen, it's not working when I place ion-content inside ion-tab.
See the Pen wGqoKe

i confirme this issue.


Extension host terminated

Type: Bug
Extension host terminated unexpectedly 3 times within the last 5 minutes.
Extension version: 0.12.0
VS Code version: Code 1.86.0 (05047486b6df5eb8d44b2ecd70ea3bdf775fd937, 2024-01-31T10:28:19.990Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz (8 x 1995)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: unavailable_offvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.89GB (1.42GB free)

Process Argv
--crash-reporter-id 2540450f-fdba-4fa7-8c54-b8c63b3a24e1

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019bcf:30953938
3ef8e399:30949928

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Please diagnose the root cause of the issue by running the command F1 > Help: Troubleshoot Issue and following the instructions. Once you have done that, please update the issue with the results.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


OData $batch returns 404

Hi @commonsensesoftware ,
This may be a configuration issue, or something I am completely spacing on, but I am struggling to get $batch queries to work for dotnet core.
In my startup I have:
app.UseODataBatching();
app.UseMvc(routes =>
{
routes.Select().Expand().Filter().OrderBy().MaxTop(1000).Count();
var models = modelBuilder.GetEdmModels();
routes.MapVersionedODataRoutes( "odata", "v{version:apiVersion}/odata", models );
});
On a side note . . . I realize I am not passing through DefaultODataBatchHandler, and suspect this is the issue, but was not able to get that to work when configuring MapVersionedODataRoutes.  Is there a sample for dotnet core?
Anyways, back to the issue, everytime I try and post using fiddler or postman using the following I get a 404:
POST  https://localhost:44321/v2.1/odata/$batch  HTTP/1.1
Host: localhost:44321
OData-Version: 4.0
OData-MaxVersion: 4.0
Content-Type: multipart/mixed; boundary=batch_6f7e1cb3-701e-45fe-bd22-25cc6a27c52a
Accept: multipart/mixed
Accept-Charset: UTF-8
Content-Length: 1522
Expect: 100-continue
--batch_6f7e1cb3-701e-45fe-bd22-25cc6a27c52a
Content-Type: application/http
Content-Transfer-Encoding: binary
Content-ID: 1
GET /v2.1/odata/Components HTTP/1.1
Host: localhost:44321
--batch_6f7e1cb3-701e-45fe-bd22-25cc6a27c52a
Content-Type: application/http
Content-Transfer-Encoding: binary
Content-ID: 2
GET /v2.1/odata/GeographicAreas HTTP/1.1
Host: localhost:44321
--batch_36522ad7-fc75-4b56-8c71-56071383e77b--
Any ideas?


libRDKitMolStandardize.so.1.2020.09.3 doesn't have a SONAME

====> Running Q/A tests (stage-qa)
Warning: /usr/ports/science/rdkit/work/stage/usr/local/lib/libRDKitMolDraw2D.so.1.2020.09.3 doesn't have a SONAME.
Warning: pkg(8) will not register it as being provided by the port.
Warning: If another port depend on it, pkg will not be able to know where it comes from.
Warning: It is directly in /usr/local/lib, it is probably used by other ports.
Warning: /usr/ports/science/rdkit/work/stage/usr/local/lib/libRDKitMolStandardize.so.1.2020.09.3 doesn't have a SONAME.
Warning: pkg(8) will not register it as being provided by the port.
Warning: If another port depend on it, pkg will not be able to know where it comes from.
Warning: It is directly in /usr/local/lib, it is probably used by other ports.
Warning: /usr/ports/science/rdkit/work/stage/usr/local/lib/libRDKitMolEnumerator.so.1.2020.09.3 doesn't have a SONAME.
Warning: pkg(8) will not register it as being provided by the port.
Warning: If another port depend on it, pkg will not be able to know where it comes from.
Warning: It is directly in /usr/local/lib, it is probably used by other ports.

Version: 2020_09_3
OS: FreeBSD 12.2

@yurivict: this seems odd. you only get the warning for those three libraries?

Yes, only for these libraries.

Hmm, this doesn't happen for me on Ubuntu and I don't have a FreeBSD machine to test on, so it's going to be tricky to track down.
This is a pretty strange problem given that all the libraries are built the same way.
Here's the cmake command to create the Substruct library:
https://github.com/rdkit/rdkit/blob/master/Code/GraphMol/Substruct/CMakeLists.txt#L2
rdkit_library(SubstructMatch
              SubstructMatch.cpp SubstructUtils.cpp
              LINK_LIBRARIES GraphMol RDGeneral)
target_compile_definitions(SubstructMatch PRIVATE RDKIT_SUBSTRUCTMATCH_BUILD)

and the same thing for MolEnumerator:
https://github.com/rdkit/rdkit/blob/master/Code/GraphMol/MolEnumerator/CMakeLists.txt#L1
rdkit_library(MolEnumerator
              MolEnumerator.cpp PositionVariation.cpp LinkNode.cpp
              LINK_LIBRARIES FileParsers ChemReactions ChemTransforms
              SubstructMatch GraphMol RDGeneral)
target_compile_definitions(MolEnumerator PRIVATE RDKIT_MOLENUMERATOR_BUILD)

I guess you could try touching one cpp file in SubstructMatch/ and one in MolEnumerator/ and then building the libraries like this: VERBOSE=1 make SubstructMatch MolEnumerator and then we can look at the specific link commands issued to see if there's an obvious difference.

Closing because this is likely no longer relevant


Excalidraw

https://excalidraw.com/

it's seem that by policy we can't install a PWA by command line, for now...


google STT - use the baseclass resampler

From https://cloud.google.com/speech-to-text/docs/speech-to-text-requests#sample-rates:

If you have a choice when encoding the source material, capture audio using a sample rate of 16000 Hz. Values lower than this may impair speech recognition accuracy, and higher levels have no appreciable effect on speech recognition quality.
However, if your audio data has already been recorded at an existing sample rate other than 16000 Hz, do not resample your audio to 16000 Hz. Most legacy telephony audio, for example, use sample rates of 8000 Hz, which may give less accurate results. If you must use such audio, provide the audio to the Speech API at its native sample rate.

16Khz may be the right choice


pkg/runcfanotify: Search runc in some directories if not in runcPaths.

If runc binary was not found in runcPaths, we will search it by walking some directories.
This is inefficient but permits Inspektor Gadget to work on distro where runc is stored in custom places.
Moreover, the idea is to then add the custom path to runcPaths by encouraging people to open a PR.

Ref https://github.com/inspektor-gadget/inspektor-gadget/pull/1867

Perhaps a middle ground if to implement an option to add paths to the list. Then this error message could be extended with:

Suggest to use such option to manually specify the path of the binary
Report an issue so we can add that path if it's a standard location

That seems good to me.
I wonder about using an environment variable instead of an CLI flag. That would be easier because the pkgs could be used in different programs:

ig
gadgettracermanager
third-party tools using pkg/runcfanotify or pkg/container-hook.


SynthID doesn't work correctly in "non-distortionary" mode with "ngram_len"=1

Hi, I just evaluated the TPR @ 0.01FPR of different SynthID configurations. I found that when I set ngram_len=1 and watermark_mode="non-distortionary", I get 0.016 TPR, whereas I get 0.996 for other configurations (see screenshot, where cw indicates ngram_len).

Is this expected behavior? If so, I believe you should warn the user or even throw an error when initializing SynthID with ngram_len=1 and watermark_mode="non-distortionary". If not, you might want to fix this.
Here is my exact SynthID configuration for the run with 0.016 TPR. I used meta-llama/Llama-3.2-3B for text generation.
"algorithm_name": "SynthID",
"ngram_len": 1,
"keys": [
    654, 400, 836, 123, 340, 443, 597, 160, 57, 29,
    590, 639, 13, 715, 468, 990, 966, 226, 324, 585,
    118, 504, 421, 521, 129, 669, 732, 225, 90, 960
],
"sampling_table_size": 65536,
"sampling_table_seed": 42,
"watermark_mode": "non-distortionary",
"num_leaves": 2,
"context_history_size": 1024,
"detector_type": "mean",
"threshold": 0.52,

Thank you!

This is a normal behavior. In the non-distortionary mode, to ensure unbiased multi-step watermarking, repeated context masking is implemented. When encountering identical context sequences of length (ngram_len - 1), the system automatically skips watermarking at those positions. During detection, positions with repeated contexts are also excluded from statistical analysis. When ngram_len=1, it represents a globally fixed hash with context length of 0, which means the non-distortionary mode will only apply watermarking at the first position. Therefore, if you wish to use a globally fixed hash, you can set ngram_len=1 and use the distortionary mode. While this ensures detectability, it's important to note that globally fixed hashes cannot guarantee unbiasedness.
When ngram_len is set to 1, it represents a globally fixed hash, with a context length of 1. Therefore, using the non-distortionary mode results in the watermark being applied only at the first position. If you wish to utilize a globally fixed hash, you can set ngram_len to 1 and the mode to distortionary (no repeated context masking), which will ensure detectability. However, please note that a globally fixed hash cannot guarantee unbiasedness.

Thank you for the clarification, that's very helpful. I think giving a warning when using ngram_len=1 with watermark_mode="non-distortionary" would make sense then. Feel free to close this issue.

Thank you for your suggestions. We will add a warning soon. 😊


Duplicate dataelements du to raceconditions when autoCreate is set to true

Description of the bug
It is possible to end up with multiple dataelements in an instance when instantiating and uploading a dataelemnt via the api when autoCreate is set to true.
Steps To Reproduce

Create an application with a autoCreate=true
Instantiate a new instance and create a dataelement in a loop
Some instances could end up with multiple dataelements leaving it in a erroneous state

Additional Information
Workaround: disable autoCreate

Seems like the root of this problem is eventual consistency in storage. We need to handle this in the correct place

Backend is endring up with validating errors against the wrong dataelement (empty).

After migration of database in core we cannot reproduce this. Closing as not reproducable


Remove ember-cli-shims

Closes #131

@alexlafroscia could you rebase to restart CI now that #135 is merged?


Change all exercises to use Swift package manager

Related #233 #142

Could you update the xcode project so that travis can run the tests?
Could we make one package that contains all packages so we can run tests on linux?
This is great!

we could also eliminate the xcode project and just use a genratec xcode project to run the test. i am going to create a new branch to merge this PR so we can test this before merging into master.

I tested all exercises with swift test on my macOS.
Only testIgnoreBadlines in tournament is failed.

Let me know when it is ready and we can merge this part and I'll fix travis later.

Thanks

Thank you!


Completed the Chinese translation of README

Hey there,I'm interested with this project and I made a Chinese translation of README.
(I'm a Chinese college student and I have just learned how to make pr with GitHub, hoping that there is no mistake with my submission.

Thank you! this is super cool :)
Would you be interested in translating parts of the app?

Sure, I definitely want to do that, but I'm sorry for that I think I don't have enough skill to modify the code(Svelte is too foreign for me >_<)
I can only commit some basal translation works such as adding a Chinese version of the JSON file in ./frontend/locales.  XD


KSP support for Kotlin?

The current Kotlin integration requires kapt which is working well but has issues and is in maintenance mode (see https://youtrack.jetbrains.com/issue/KT-48661).
Are there any plans to move to KSP ?

Hi @martinbonnin thanks for raising this.
I was not aware of KSP.
For kapt, there is not much that picocli actively does, people can just configure picocli's java-based annotation processor in picocli-codegen and it just works. So from my point of view I just needed to document how people could use kapt with picocli.
As far as I can tell after a very brief glance, KSP unfortunately is a completely parallel API to the java annotation processing API and is not compatible. So that would mean developing and maintaining a KSP version of the picocli-codegen module.
Given how little time I have for picocli recently, that is not an attractive proposition...
Still thinking about this.

Thanks for the quick reply!
As you found out, the KSP API is completely different so it might require some work indeed. The main difference is that kapt generates Java stubs to run the java codegen on it so it adds to the build time by adding this intermediate step.
It also has limitations. One that comes to mind is interfaces nested in interfaces with the same name. This is legal in Kotlin but not in Java (Youtrack issue) but I'm pretty sure there are others.
I unfortunately don't have much time to work on this either but was curious if this was ever considered. I'll keep watching this issue in case this gets some traction one day :)

I am going to close this for now. I don't see myself working on this, and I am not sure that I would accept a contribution that implements the equivalent of the current picocli-codegen annotation processor using the KSP API...
I may change my opinion if annotation processors completely stop working for Kotlin.

I think in the future kapt may not be feasible: https://kotlinlang.org/docs/kapt.html
they're keeping it only in maintenance mode now, an all new functionality is going into ksp.

I think in the future kapt may not be feasible: https://kotlinlang.org/docs/kapt.html
they're keeping it only in maintenance mode now, an all new functionality is going into ksp.

@dkowis Understood, so that has not really changed.
I would be more open to a KSP contribution from contributors:
again, I will not be able to work on this myself, so if it breaks or if any bugs are found, I would have to rely on the contributors or wider community to help fix/improve such issues.


Docs: Safari does not allow to use Tab to pick one of the search results

The tab button in Safari Version 18.2 (206<IP_ADDRESS>.8) just moves the focus to the whole search window

Let's rewrite Safari in Rust Tact then


Overly strict "Python tag" handling for "abi3"-tagged wheels

https://peps.python.org/pep-0384/ defines the "Stable ABI" for CPython.  It claims that all subsequent CPython 3.x releases will support this ABI.
Then https://peps.python.org/pep-3149/ and https://peps.python.org/pep-0425/ expand on this to define the "abi3" "ABI Tag" as referring to the "Stable ABI" - ie, says that wheels with an "ABI Tag" of "abi3" are built against the "Stable ABI".
Then https://discuss.python.org/t/python-tags-specific-version-of-interpreter-or-minimum-version/7831/27 suggests that inference on any of this is silly, just compare a wheel's tags to the elements of packaging.tags.sys_tags() and if there's a match, you've got a wheel you can use.
mach-nix will only use a wheel with a "Python tag" that exactly matches the version of Python it is using though.  Compared to what pip will do, this excludes many wheels (for example, all cryptography wheels released in over a wheel).
Should mach-nix do something differently so it can consume more wheels?

Oh thanks for that. This should definitely be fixed in mach-nix.

Do you have any sense of whether it makes sense to try to use packaging.tags.sys_tags() in mach-nix to fix this?

I don't think that doing this is a good idea, as it would exclude wheels which are built against a later python version than the one of the current interpreter.
Though #471 should fix the problem. Could you check?

#471 was reverted in 552d4caa73722b262204319526f9e77f9370f702 due to regression reported in #475 so this issue should be open, I think (and it seems like #475 could be closed).


Opening the mutator dialog on a function changes parameters

Drag function definition
Variable name is x
Open mutator dialog
Variable name is y

It does more than that, it entirely resets the previous argument names.

Fixed in b0f37366449001fb2973e4977c17c732b72b63dd


use another formatting tool since eslint formatting rules are deprecated?

See https://eslint.org/blog/2023/10/deprecating-formatting-rules/#what-you-should-do-instead
The most pragmatic move might be to do nothing, though.

Yes. Or even don't change anything since they promise not to remove the old rules anyway (they are just unmaintained)
-------- Message d'origine --------
Le 08/11/2024 22:27, Kenny Daniel  a écrit :

Yea I'm not a huge fan of eslint. The migration to 9.x was painful. The fact that they want to move away from formatting and require you to use a 2nd tool is also annoying. But I don't know that anything else is better? I am open to suggestions though. Eslint with sytlistic packages seem like okay compromise for now?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Closing for now. We can reopen if needed.

If we reopen at some point, https://github.com/eslint/config-inspector can help: it's a GUI to inspect the ESLint rules. It shows the deprecated rules, for example.


Is there a way to show a spinner or loading... while it's waiting for the wasm to finish loading?

Specific Demand
Show spinner while waiting for wasm to load.
Implement Suggestion
I think it's possible with Trunk, but I'm not sure. Any pointers would be helpful.

There are two approaches you can take here:

Use SSR + Hydration to hydrate a loading spinner (see this example for hydration)

// run with:
// cargo run # to create index.html
// dioxus serve # to run in browser

use std::io::Write;

use dioxus::prelude::*;

fn main() {
    #[cfg(target_arch = "wasm32")]
    dioxus_web::launch_cfg(app, dioxus_web::Config::new().hydrate(true));
    #[cfg(not(target_arch = "wasm32"))]
    {
        let template_pre = r#"<!DOCTYPE html>

  <title>Evan Almloff</title>
  <meta content="text/html;charset=utf-8" http-equiv="Content-Type" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <meta charset="UTF-8" />
  <link rel="stylesheet" href="/output.css" />

"#;
        let template_post = r#"

"#;
        let mut file = std::fs::File::create("index.html").unwrap();
        let mut vdom = VirtualDom::new(app);
        let _ = vdom.rebuild();
        let renderered = dioxus_ssr::pre_render(&vdom);
        file.write_fmt(format_args!("{template_pre}{renderered}{template_post}"))
            .unwrap();
    }
}

fn app(cx: Scope) -> Element {
    let loading = use_state(cx, || true);
    // this will force a re-render on the client
    if **loading {
        loading.set(false);
        render! {
            "loading..."
        }
    } else {
        render! {
            Counter {}
        }
    }
}

fn Counter(cx: Scope) -> Element {
    let count = use_state(cx, || 0);
    render! {
        div {
            button {
                onclick: move |_| {
                    count.set(**count + 1);
                },
                "Increment",
            }
            "Count: {count.get()}"
        }
    }
}

You wouldn't actually need a server here, you could just use ssr to generate the html with the spinner that then is swapped out immediately for the real page
2) Use use_eval with getElementById to remove a specific element after the wasm has loaded


Crash when using the "Avaritia Fabric" Infinity Hammer (Pickaxe)

Mod Name
Avaritia Fabric
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/avaritia-fabric
Describe the bug
crash
Steps to reproduce
1.take an infinity pickaxe
2. shift right click with it
3.get the hammer
break block in survival
crash
...
Logs
https://crashy.net/013fbef7-1823-4c26-bd69-a0c9f95e6685
Additional context
https://bytebin.lucko.me/KUVwikJYLK

The version of Forge you're using is too new. Please downgrade to 47.1.3 as instructed in the README

thanks


feat: generate REST API client code with OpenAPI Generator typescript-fetch

Link to ticket
https://github.com/nemtus/symbol-sdk-openapi-generator-typescript-fetch/issues

No ticket

What you did
What did you do with this pull?

Generate REST API client automatically with OpenAPI Generator typescript-fetch
Implement dummy test
Implement CI/CD with GitHub Actions

CI ... build and unit test with Jest
CD ... build and unit test with Jest and npm publish

What you will not do
What you will not do with this pull request? (If any. If not, "none" is OK) (If not, state when you will do it or create the issue will be remained.)

I will not implement utilities to convert some data to get info. https://github.com/nemtus/symbol-sdk-openapi-generator-typescript-fetch/milestone/2
I will not implement utilities to convert some data to send transactions. https://github.com/nemtus/symbol-sdk-openapi-generator-typescript-fetch/milestone/3
I will not implement appropriate test. I wanna ask to community to what kind of test is necessary before implementation.

What developers will be able to do (from the developer's perspective)
What will developers be able to do? (If any. (If not, "none" is OK.) ## What developer will be able to do (from the developer's perspective)

Developers can access Symbol blockchain's REST API with this package except sending transactions.

What will not be possible (from the developer's perspective)
What will be impossible to do? (If available. If not, "None" is OK.) * What will be impossible to do? (If no, then "None" is OK.)

Developers can't convert response's value to appropriate format data.
Developers can't convert transaction data to appropriate format data to send transactions.

Operation check
What kind of operation checks were performed?　What are the results?

I debug with the bundled file for CDN in the following html file( examples/cdn/index.html ) and I confirm it works.

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script src="../../dist/index.min.js"></script>
  </head>
  <body>
    <script>
      (async () => {
        const symbolSdk = window.symbolSdkOpenAPIGeneratorTypeScriptFetch;
        const configurationParameters = {
          basePath: 'http://symbol-sakura-16.next-web-technology.com:3000',
        };
        const configuration = new symbolSdk.Configuration(configurationParameters);

        const nodeRoutesApi = new symbolSdk.NodeRoutesApi(configuration);
        const responseNodeInfo = await nodeRoutesApi.getNodeInfo();
        console.log(responseNodeInfo);

        const accountRoutesApi = new symbolSdk.AccountRoutesApi(configuration);
        const requestParameters = {
          accountId: 'NCSIOEWE2364XXP65426W3RUGBRYOAGR3KMMCIA',
        };
        const responseAccountInfo = await accountRoutesApi.getAccountInfo(requestParameters);
        console.log(responseAccountInfo);
      })();
    </script>
  </body>
</html>

I also debug with Jest in the following file. ( Create src/index.spec.ts and execute npm run test )

import { Configuration, ConfigurationParameters, NodeRoutesApi, FetchAPI } from '.';
import * as symbolSdk from '.';
import fetch from 'node-fetch';

describe('nodeRoutesApi', () => {
  it('getNodeInfo should return expected response', async () => {
    expect.hasAssertions();
    const configurationParameters: ConfigurationParameters = {
      basePath: 'https://symbol-sakura-16.next-web-technology.com:3001',
      fetchApi: fetch as unknown as FetchAPI,
    };
    const configuration: Configuration = new Configuration(configurationParameters);
    const nodeRoutesApi = new NodeRoutesApi(configuration);
    const response = await nodeRoutesApi.getNodeInfo();
    console.dir(response, { depth: null });
    expect(response).toBeTruthy();
  });

  it('getNodeInfo should return expected response with bundled file', async () => {
    expect.hasAssertions();
    const configurationParameters: symbolSdk.ConfigurationParameters = {
      basePath: 'https://symbol-sakura-16.next-web-technology.com:3001',
      fetchApi: fetch as unknown as FetchAPI,
    };
    const configuration: symbolSdk.Configuration = new symbolSdk.Configuration(configurationParameters);
    const accountRoutesApi = new symbolSdk.AccountRoutesApi(configuration);
    const request: symbolSdk.GetAccountInfoRequest = {
      accountId: 'NCSIOEWE2364XXP65426W3RUGBRYOAGR3KMMCIA',
    };
    const response = await accountRoutesApi.getAccountInfo(request);
    console.dir(response, { depth: null });
    expect(response).toBeTruthy();
  });
});

But I did not debug with CommonJS or ES Module output files with another apps. (ex. with npm link )

Others
Reference information for reviewers (describe any implementation concerns or cautions)

https://github.com/nemtus/symbol-sdk-openapi-generator-typescript-axios
https://github.com/symbol/symbol-openapi
https://openapi-generator.tech/
https://openapi-generator.tech/docs/generators/typescript-fetch
https://github.com/cosmos-client/cosmos-client-ts
https://blog.cybozu.io/entry/2020/10/06/170000

I will merge this without a review at this time.


deviceready event not triggered when running --livereload

running ionic run --device, deviceready is triggered.
running ionic run --device -l, deviceready is NOT triggered.
This seems like it's a bug.
± ionic info

Your system information:

Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.3
Ionic CLI Version: 2.1.14
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.45
ios-deploy version: 1.9.0
ios-sim version: 5.0.12
OS: macOS Sierra
Node Version: v6.9.1
Xcode version: Xcode 8.1 Build version 8B62

It might not be deeper than not triggering device ready. The code below works just fine with ionic run --device but when you use ionic run --device -l nothing happens.
import { StatusBar, Keyboard } from 'ionic-native'

setTimeout(function () {
  if (window.StatusBar) {
    Keyboard.disableScroll(true)
    StatusBar.overlaysWebView(false)
  }
}, 300)

So it's both things, deviceready is never triggered and ionic-native doesn't work.

For me, deviceready is not triggered regardless of livereload. I have realized that cordova platform is not available even on an actual device, when you update ionic-app-scripts to version 0.0.42 and above.


Query timer starting early?

Dbeaver 5.2.5: When executing a query with a bind variable, the 'Initializing' timer popup appears as soon as the window prompting for the variable value appears. Once the variable value is set the timer text changes to 'Execute query'. I feel this tends to give a misleading impression of how long the query is acutally running for.

Thanks for the bug report


Move off of gogo/protobuf to e.g. vtproto

Proposal
In current implementation, protobuf files used by remote storage API import gogo.proto
https://github.com/prometheus/prometheus/blob/2ce94ac19673a3f7faf164e9e078a79d4d52b767/prompb/remote.proto?_pjax=%23js-repo-pjax-container%2C div[itemtype%3D"http%3A%2F%2Fschema.org%2FSoftwareSourceCode"] main%2C [data-pjax-container]#L20
https://github.com/prometheus/prometheus/blob/2ce94ac19673a3f7faf164e9e078a79d4d52b767/prompb/types.proto?_pjax=%23js-repo-pjax-container%2C div[itemtype%3D"http%3A%2F%2Fschema.org%2FSoftwareSourceCode"] main%2C [data-pjax-container]#L19
But https://github.com/gogo/protobuf is already deprecated, and we only use nullable  options, which I think is not a must.
Also other languages besides Go can use those protobuf files easier if we remove it.

I have written a Rust library to wrap Prometheus remote API by copying protos in prompb, and remove gogo.proto by hand, it would be simpler if this issue is fixed.

Hi, sorry this has gone without comment.
It’s a reasonable objective to make the definitions more portable.
However I would not want to see a noticeable performance cost. Google’s proto3 has added a number of fields to generated structs, and in Prometheus remote write every label and sample is a struct.

At https://github.com/prometheus/prometheus/issues/10371 it is suggested to use the Buf registry; would that help your case?

This is still a valid request, given gogo is deprecated.
See the detailed discussion here: https://groups.google.com/g/prometheus-developers/c/uFWRyqZaQis/m/1OOGT7s5AwAJ
We consider this to be part of GSoC mentorship project, if anyone would be interest to mentor or be mentored.

Hey everyone, I'm a third year software engineering student from Toronto, Canada. I initially heard from a friend that was part of the Kubernetes shadow program and I came over GSOC when looking for a reason to contribute my first time! I used Promethues before so I am familiar with it just on a very surface level. This issue feels like a good fit and I think it'll be very fun doing optimization and hopefully I can contribute and learn a thing or two.
Currently, I'm just reading over https://contribute.cncf.io/contributors/getting-started/ and looking through the Promethues  codebase to get started (If there are any  other resources I'd appreciate the guidance!). I am also currently working on my GSOC proposal and had a question.
Was there any idea of what we want the benchmarks to be other than memory utilization for for remote write and scraping? In other words, is there anything else tested like throughput, latency? From my initial look-over it looks like there is a test or two involving memory here https://github.com/prometheus/prometheus/tree/main/scrape. Sorry if this is lazy question, I am trying to find current benchmarks cause it mentions they are the standard.
@cstyan @macxamin @bwplotka @TheSpiritXIII (Also, is pinging okay, it seems to depend on the issue so I'm not quite sure)

Thanks for your interest @HikaruSadashi. Just be aware that this migration, off of gogoproto and onto something else like csproto or vtproto, is definitely not as easy as it sounds. It will involve quite a bit of optimization work using structures specific to those pacakges or just go in general sync.Pool that a) can be hard to use correctly and b) might be hard to wrap your head around if you don't already have a lot of go/protobuf experience.
As for the benchmarks, the most relevant would be in the remote storage package. There's some in the queue_manager tests:
queue_manager_test.go
1210:func BenchmarkSampleSend(b *testing.B) {
1247:func BenchmarkStoreSeries(b *testing.B) {
1298:func BenchmarkStartup(b *testing.B) {
1766:func BenchmarkBuildWriteRequest(b *testing.B) {
1813:func BenchmarkBuildMinimizedWriteRequest(b *testing.B) {

There's also prometheus/scripts/remotewrite11-bench which well help run multiple versions of prometheus/with different config options + metrics collection so those can easily be compared.

I'm currently doing an experiment with the official Protobuf compiler and Go library. If you are interested you can find it here. I don't really get how to compare the benchmarks just yet but I expect this to be a little bit worse because of cache misses (more pointer following than previously).

Unless something in the official compiler and library has changed fundamentally in the last years, we can be pretty sure that the results will be prohibitively expensive.
Note that a bunch of people are tackling this issue right now. I saw recent activities by @mircodz @Clement-Jean @HikaruSadashi (on the dev mailing list or here in this issue). Maybe you should all talk to each other and see what can be done. Maybe a new channel #prometheus-protobuf-dev on the CNCF Slack would be a good collection point for interested contributors?

@beorn7 @HikaruSadashi @mircodz I created the channel, you guys can join.

Moving off of gogoproto is listed as a GSOC project: https://github.com/cncf/mentoring/blob/main/programs/summerofcode/2024.md#move-out-of-gogoprotobuf-to-protobuf-with-vtproto-implementation

Sorry for the late reply I just finished finals
@cstyan  Yeah I am expecting to have to dig deep with vtproto or csproto. I have protobuf experience but not directly with Go and so I've been playing with both packages and sync.Pool in general so I'm more familiar. Also thanks for the guidance / pointing me to the benchmarks I have been looking over those too.
Also thanks for creating the channel @Clement-Jean


Google Chrome as method not working

I just switched to the newest commit in the master branch (86feeac) and I noticed that using Google Chrome as the chat method in the settings does not work correctly.
Instead of opening the Chat inside an app/minimal Chrome window, a normal Chrome Window with an empty tab is being opened.
Using the command line to open an app window with chrome.exe "--app=http://twitch.tv/CHANNELNAME/chat" works as intended.
I'm on Windows 10 and using Version 50.0.2661.102 m (64-bit) of Google Chrome.

Also when looking at the command line arguments passed to Chrome, the argument is listed as --app=\h\t\t\p\s\:\/\/\w\w\w\.\t\w\i\t\c\h\.\t\v\/\ [...]

Thanks!


Add HMAC signature support.

Defined types, objects, and methods for working with HMAC signatures.

Codecov Report

Merging #440 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #440      +/-   ##
==========================================
- Coverage   54.44%   54.42%   -0.03%
==========================================
  Files         342      343       +1
  Lines       58450    58486      +36
==========================================
+ Hits        31825    31831       +6
- Misses      26625    26655      +30

Impacted Files
Coverage Δ

src/lib/support/crypto/HMAC.cpp
55.84% <0%> (-44.16%)
:arrow_down:

src/lib/support/crypto/HMAC.h
0% <0%> (ø)

src/lib/profiles/security/WeaveCASEEngine.cpp
93.33% <0%> (+0.23%)
:arrow_up:

src/lib/profiles/security/WeaveToX509.cpp
88.17% <0%> (+0.25%)
:arrow_up:

src/lib/profiles/security/WeaveCert.cpp
88.96% <0%> (+0.45%)
:arrow_up:

src/lib/support/ASN1Writer.cpp
87.39% <0%> (+0.86%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0875967...77277a9. Read the comment docs.


Display Eco Mode not working on T-Beam Supreme

The display does not turn off automatically on the T-Beam Supreme, although the eco mode was enabled, no matter what timeout is configured.

@tobiasschwalm it should be available and running now, please update all firmware code and it should run without any issue


Fix reaction adds to RFR messages if reacting with a unicode emoji

Summary

close #245
Fixes bug where RFR messages break when having a unicode emoji
Checklist

[x] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

[x] Have you tested the changes? (pytest & dpytest)
[x] Have you followed PEP-8 for naming and styling?
[x] Has your code been properly documented with RestructuredText docstrings?
[x] Have you added your changes to CHANGELOG.md under the [Unreleased] heading?
[x] If your code added new bot commands, have you updated documentation.json?

[x] All of this code is your own, or follows the author repo's licence.

Coverage needs increasing, then we can merge @Unknownlocal

@JayDwee This good now?


fix: host should not return a redirect source file from getSourceFile

I'm submitting a...
[x] Bug Fix
[ ] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

[x] Commit Messages follow the Conventional Commits pattern

A feature commit message is prefixed "feat:"
A bugfix commit message is prefixed "fix:"

[x] Tests for the changes have been added

Description
This fix is basicilly because of recursive node_modules when you do npm link or using lerna
https://www.typescriptlang.org/docs/handbook/module-resolution.html#path-mapping
closes: #473
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Can be solved by using ng-packagr api

@alan-agius4 how can this be solved using ng-packagr api

@gmfun are you using a mono repo by any chance? i solved mine by providing a tsconfig with paths for build.
I have a skeleton repo with an example of this.
https://github.com/alan-agius4/ng-mono-repo-starter/blob/master/tsconfig.build.json
https://github.com/alan-agius4/ng-mono-repo-starter/blob/master/tools/tasks/build.ts
If you can provide an example of your problem maybe i can help you out a bit better.

@alan-agius4 https://github.com/hypertrack/js-sdk this the repo where I am using angular with lerna (packages/angular-components). Currently stuck at typescript 2.4 as upgrading gives the error. Will also look into the repo you have shared and try to understand how you fixed, it. I first glance it looks like you are using ng-packagr api to override tsconfig.

Yes, indeed I am using the API to override the tsconfig.
Ill try to have a look at your repo in the coming days, as at the moment I
am on a short trip.
On Sun, 11 Feb 2018 at 10:12, Gaurav Mukherjee<EMAIL_ADDRESS>wrote:

@alan-agius4 https://github.com/alan-agius4
https://github.com/hypertrack/js-sdk this the repo where I am using
angular with lerna (packages/angular-components). Currently stuck at
typescript 2.4 as upgrading gives the error. Will also look into the repo
you have shared and try to understand how you fixed, it. I first glance it
looks like you are using ng-packagr api to override tsconfig.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dherges/ng-packagr/pull/501#issuecomment-364735957,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQv-Wul2ie8QXlPUoB-2xFZ0_O7LYnUuks5tTq70gaJpZM4RhhHD
.

When i try to run build under angular-components I am getting a bunch of error like;

BUILD ERROR
src/app/pipes/time-string.pipe.ts(2,26): error TS2307: Cannot find module 'ht-utility'.
src/app/pipes/date-string.pipe.ts(3,26): error TS2307: Cannot find module 'ht-utility'.
src/app/pipes/name-case.pipe.ts(2,24): error TS2307: Cannot find module 'ht-utility'.
src/app/pipes/dot.pipe.ts(2,25): error TS2307: Cannot find module 'ht-utility'.
src/app/pipes/date-humanize.pipe.ts(2,28): error TS2307: Cannot find module 'ht-utility'.
src/app/pipes/distance-locale.pipe.ts(2,30): error TS2307: Cannot find module 'ht-utility'.
src/app/pipes/hm-string.pipe.ts(2,24): error TS2307: Cannot find module 'ht-utility'.
src/app/ht/ht-map.service.ts(2,37): error TS2307: Cannot find module 'ht-maps'.
src/app/users-container/users-container.component.ts(8,21): error TS2307: Cannot find module 'ht-ut
....
...


How to auto parsing?

I run the benchmark.pu with the following warnings.
python benchmark.py --arch resnet18 --device cuda:0
Parsing Computation Graph with torch.jit failed, revert to manual parse_graph function

Hi,
Can you remove the "try" at https://github.com/lordfjw/OptimalGradCheckpointing/blob/main/benchmark.py#L167 and paste the error message?
Can you share the pytorch version? It might also be pytorch version too old
Thanks


Code not properly colorized in Typescript with conditional return types

VSCode Version: 1.33.1 & 1.34.0 (Insiders)
OS Version: Windows 10 x64

Steps to Reproduce:
Write the following code in a new Typescript file:
type X = A | B;
type A = string;
type B = number;
function foo<T extends X>(arg: T): T extends B ? number : string {
  if (arg === "A") return <T extends B ? number : never>111;
  return <T extends B ? never : string>"returning a string";
}
foo("A");
foo(1);

In my project, I need to use a function with the typing described in the code above. This is of course a simplified version of my code. The code passes the Typescript 3.4.3 without errors, and also works at run time.
However, the colorization of the code bugs after the if statement.

If I remove the parameters from the return statements, then the colorization works. But the code doesn't pass the type-check anymore.

I get the same result with and without extensions. Also with the latest insiders build of VS Code.

I confirmed this using the latest grammar version


refactor: use Checkpoint ORM

Depends on: https://github.com/checkpoint-labs/checkpoint/pull/253
Depends on: https://github.com/checkpoint-labs/checkpoint/pull/252

@Sekhmet We need generate in the build script too otherwise server fail to deploy on DO
[2023-09-22 13:29:48] │ Running custom build command: yarn build
[2023-09-22 13:29:49] │ yarn run v1.22.19
[2023-09-22 13:29:49] │ $ tsc -p tsconfig.build.json
[2023-09-22 13:30:03] │ src/ipfs.ts(5,8): error TS2307: Cannot find module '../.checkpoint/models' or its corresponding type declarations.
[2023-09-22 13:30:03] │ src/utils.ts(8,46): error TS2307: Cannot find module '../.checkpoint/models' or its corresponding type declarations.
[2023-09-22 13:30:03] │ src/writer.ts(5,45): error TS2307: Cannot find module '../.checkpoint/models' or its corresponding type declarations.
[2023-09-22 13:30:03] │ error Command failed with exit code 2.

Also it seem to miss this, weird I was thinking you already added somewhere
if (process.env.CA_CERT) {
  process.env.CA_CERT = process.env.CA_CERT.replace(/\\n/g, '\n');
}

@bonustrack this should be handled there:
https://github.com/checkpoint-labs/checkpoint/blame/27a74fa68174d1542e9ee77993df7d71d42949c9/src/knex.ts#L57-L61

@Sekhmet You mean we should change Checkpoint to parse CA_CERT rather than doing it here?

Ah, I see that's DO specific to convert it to multiline.

Ok deployment works but I got this error now on indexing 2nd space:
error: insert into "spaces" ("authenticators", "controller", "created", "id", "max_voting_period", "metadata", "min_voting_period", "proposal_count", "proposal_threshold", "strategies", "strategies_metadata", "strategies_params", "tx", "validation_strategy", "validation_strategy_params", "vote_count", "voting_delay", "voting_power_validation_strategy_strategies", "voting_power_validation_strategy_strategies_params") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, $19) - duplicate key value violates unique constraint "spaces_pkey

Not sure if it's related to Postgres

@bonustrack we don't have multiple containers using/multiple deployments using single DB?

Nope just re-verified

But 2 instances of the same deployment might be living in same time when an update happen, maybe with a sleep(20e3) before checkpoint.reset() it wont happen?

We can try that.

Same error

On the original instance with MySQL it works

I can reproduce the issue locally with a different database (but still with Postgres)

I will take a look.

This is still happening for me:
https://github.com/snapshot-labs/sx-api/issues/188

@bonustrack this PR isn't supposed to handle this.


Processing multiple Images and calculating number of dark and white pixels. [SLOW]

Expected Behavior
It reads a folder with multiple images (706) and calculates the dark and white pixels and convets the number of white pixels into a percentage.

Current Behavior
The code does what I need it to do except it's very slow. I have noticed that it tries to open all images at once and just then proceed to the calculations. I have a 8gb ram laptop. While the code reads the images the ram peaks up to 6gb and the program freezes for about 10min before it proceeds with the calculations.

var Jimp = require("jimp");
var fs =require('fs');

fs.readdir("./unZipped/", function(err, filenames) {
    if (err) {
      onError(err);
      return;
    }
    filenames.forEach(function(filename) {
        if (filename.indexOf('.png')>-1){
            //console.log(filename)
            processimage(filename)
        }
        else{
        var x=0;

        }
    });
  });
var processimage=function (imageFile){
    Jimp.read('./unZipped/'+imageFile, (err, lenna) => {
        console.log("in read");
        if (err) throw err;
        var iwidth = lenna.bitmap.width ;
        var iheight = lenna.bitmap.height ;
        //console.log("image width: "+ iwidth);

        //console.log("image height: "+ iheight);
    var darkcount =0;
        for (var i =0; i<iwidth;i++){
            for (var j=0; j<iheight;j++){

                var col = lenna.getPixelColor(i, j);
                //console.log ("i "+ i + " j " +j+ "col: "+ col);

                if (col===255)
                {
                    darkcount++;

                }
            }
        }
        var totalSize=i*j
        var percentlight2Dark= (totalSize-darkcount)/totalSize;
        console.log (imageFile+" darkcount "+ darkcount + " total count  " +i*j+ " %age light dark : "+percentlight2Dark*100);
    });
}

maybe someone could help me to read the images one at a time and do the calculation and carry on with the rest of the images in the folder so that it doesn't fill up the memory.
Thanks

Hi, this isn't really an issue with JIMP as much as it is just a coding issue. You are correct in your assumption that the program you wrote will by processing all the files at the same time, and this is likely the cause of your memory and CPU issues. What you want to do is instead of calling processimage inside the readDir function, instead add them to an array. Once the directory has been read and the files all found, start work on the image processing - call processimage on the first file in the array, and do not call again until the process is complete (simple way to do this would be to have some flag variables set when the process starts and ends, and maybe just have a setInterval checking the flags. A nicer way is to use a loop and async.
This will still take a long time as using getPixelColor is not incredibly fast, but this will at least allow the program to not hog all your laptops memory so you can at least do other stuff in the mean time. I also understand that if you opened this 25 days ago, you probably have resolved this or moved past this issue!


Add Download to Grief Prevention addon.

I ended up compiling the plugin myself and making a download for it. This should hopefully be help to alot of people (including myself).

@NeumimTo is updating that addon himself. It would be redundant to link towards a version that will most likely not be maintained in the future.


[Angular 10] modal dialog service doesn't render component

Environment

CLI: 6.8.0-rc.4
Cross-platform modules:
Android Runtime: 6.5.3
iOS Runtime: 6.5.1
Plugin(s):
NativeScript-Angular: 10.0.0
Angular: 10.0.0

Describe the bug
ModalDialogService just shows backdrop and doesn't render provided component.
To Reproduce
Just create a simple component and try to show it in a modal.
Expected behavior
The service should render the component.

@mohammadrafigh I setup a modal example project here which you can clone and run to see modals working. Have a look and let me know if you have something different on your end that may be causing you an issue.
https://github.com/NathanWalker/ns-angular10-modal-sample

Thanks @NathanWalker for answering. Ok it seems the problem just occurs on Android. I ran your example on Android and here is the result.

Okay got it, good clarification, investigating this thank you 👍

@mohammadrafigh we really appreciate the community updating to Angular 10 using the core rc's as it is making {N} 7.0 preparations so much better. Indeed the Frament Dialog needed to be decorated with the new NativeClass decoration in @nativescript/core. We just published an update to fix this in 7.0.0-rc.51 which is the latest rc tag so just clearing and rerunning will see it working 👍  - I pushed up one tweak to help the android layout on that sample so can pull latest and npm run clean to try it.

It's working now, thanks for your wonderful work at nativescript.

Still not working for me in 7.0.0-rc.58 :(.

Please use the latest stable releases. @nativescript/angular: 10.1.3 and
@nativescript/core: 7.0.3
On Mon, 21 Sep 2020, 16:25 Philipp Staudt<EMAIL_ADDRESS>wrote:

Still not working for me in 7.0.0-rc.58 :(.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NativeScript/nativescript-angular/issues/2209#issuecomment-696094989,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTM4ZBRDELAD7FJ53RPY5TSG5EKNANCNFSM4PSC3VMA
.

Please use the latest stable releases. @nativescript/angular: 10.1.3 and @nativescript/core: 7.0.3
…
On Mon, 21 Sep 2020, 16:25 Philipp Staudt, @.***> wrote: Still not working for me in 7.0.0-rc.58 :(. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2209 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTM4ZBRDELAD7FJ53RPY5TSG5EKNANCNFSM4PSC3VMA .

Updated to the following dependencies:
"dependencies": {     "@angular/animations": "10.1.2",     "@angular/common": "10.1.2",     "@angular/compiler": "10.1.2",     "@angular/core": "10.1.2",     "@angular/forms": "10.1.2",     "@angular/http": "~7.2.16",     "@angular/platform-browser": "10.1.2",     "@angular/platform-browser-dynamic": "10.1.2",     "@angular/router": "10.1.2",     "@nativescript-community/ui-image": "^4.0.6",     "@nativescript-community/ui-share-file": "^1.2.0",     "@nativescript/angular": "10.1.3",     "@nativescript/core": "^7.0.3",     "@nativescript/email": "^2.0.0",     "@nativescript/firebase": "^11.0.0",     "@nativescript/geolocation": "^7.0.0",     "@nativescript/imagepicker": "^1.0.0",     "@nativescript/local-notifications": "^5.0.0",     "@nativescript/localize": "^5.0.1",     "@nativescript/social-share": "^2.0.0",     "@nstudio/nativescript-cardview": "^2.0.0",     "@proplugins/nativescript-install-referrer": "^1.2.1",     "nativescript-appversion": "^1.4.4",     "nativescript-calendar": "^2.2.1",     "nativescript-carousel": "^7.0.1",     "nativescript-cscreenshot": "^1.0.2",     "nativescript-facebook": "^4.2.1",     "nativescript-gif": "^5.0.0",     "nativescript-theme-core": "~1.0.6",     "nativescript-toasty-ns-7": "^14.0.0",     "nativescript-ui-calendar": "^7.0.2",     "nativescript-ui-dataform": "^7.0.2",     "nativescript-ui-listview": "^9.0.2",     "reflect-metadata": "~0.1.13",     "rxjs": "^6.6.3",     "zone.js": "^0.11.1"   },   "devDependencies": {     "@angular/cli": "~10.1.2",     "@angular/compiler-cli": "10.1.2",     "@nativescript/android": "7.0.0",     "@nativescript/ios": "~7.0.0",     "@nativescript/schematics": "^10.1.0",     "@nativescript/tslint-rules": "~0.0.5",     "@nativescript/types": "^7.0.3",     "@nativescript/webpack": "3.0.4",     "@ngtools/webpack": "10.1.2",     "@types/node": "^12.12.62",     "codelyzer": "^6.0.0",     "node-sass": "^4.14.1",     "tslint": "~6.1.3",     "typescript": "3.9.7"   },
I am still getting only a black faded screen on android.
Using CLI version: 7.0.9-rc.0

Have you tried to clean your project by removing node_modules and platforms folder and npm install then run again?

Running ns clean and ns run android --bundle --env.sourceMap --env.dev yields the same behaviour.
I am using the dialog service e.g. in:
 this._modalService.showModal(MyViewComponent, {
                context: {
                    options
                },
                ios: {
                    presentationStyle: UIModalPresentationStyle.OverCurrentContext
                },
                animated: false,
                viewContainerRef: vcRef
            }).then((element) => {});

Everything seems to be correct, weird. Can you please provide a simple example project?

@PhilippS93 could you try @nativescript/angular 10.1.4 just released moment ago.

Also when bumping package dep’s make sure you use ‘ns clean’ to wipe project before building again.

@NathanWalker , @mohammadrafigh, thanks for the tips.
I found the reason for the dialog bug.
It is related to this https://github.com/mukaschultze/nativescript-windowed-modal/issues/34.
The forked NS7 plugin seems to be not 100% compatible with NS7.


Cannot use Chinese input method

Cannot use Chinese input method

Sounds like a duplicate of #2213.

CJK IME (#2213) is not a well known notion, I suggest keep this issue to prevent more duplicate ones

You really don't need to know what CJK or IME mean to find that issue. The moment you try and open a bug report with the subject "chinese input method", the system will immediately point out three closed issues (now four) with very similar titles, all marked as duplicates of #2213.

Thanks @j4james, and thanks @zwn19910807 for the bug report. /dup #2213.


Typings for this package

Hi, I've been using this package for some time and I've made the typings for those who want to use it in a TS project.
Can I make a pull request for this package and to DefinitelyTyped to include this plugin into @types list ?
It would help my team a lot, but I don't want to go without properly asking you

Feel free to create a PR with the typings :slightly_smiling_face:

Nice! Sorry for the delay
I'll send the PR tonight. I'm not very good at it tough, but it is working in my project. I'll send the PR for this package and DefinetelyTyped too


remove replaces line

completely unnecessary.
chef-client uses this because we changed the name of the RPM from
"chef-full" to "chef" back in history.  replacing the package you
are trying to install is wrong and confuses RPM and hurts upgrades.

Closing in favor of #70 @lamont-granquist


Allow to configure SslHandler to wait for close_notify response before closing the Channel and fix racy flush close_notify timeout scheduling.

Motivation:

SslHandler closed the channel as soon as it was able to write out the close_notify message. This may not be what the user want as it may make sense to only close it after the actual response to the close_notify was received in order to guarantee a clean-shutdown of the connection in all cases.

Beside this closeNotifyFlushTimeoutMillis is volatile so may change between two reads. We need to cache it in a local variable to ensure it not change int between. Beside this we also need to check if the flush promise was complete the schedule timeout as this may happened but we were not able to cancel the timeout yet. Otherwise we will produce an missleading log message.

Modifications:

- Add new setter / getter to SslHandler which allows to specify the behavior (old behavior is preserved as default)
- Added unit test.
- Cache volatile closeNotifyTimeoutMillis.
- Correctly check if flush promise was complete before we try to forcibly close the Channel and log a warning.
- Add missing javadocs.

Result:

More clean shutdown of connection possible when using SSL and fix racy way of schedule close_notify flush timeouts and javadocs.

@Scottmitch PTAL again buddy

@Scottmitch @trustin I will merge this later today... thanks!

Cherry-picked into 4.1 (640ef615be1bbf48f8506151518c0c55065e7f99) and 4.0 (95f47a44ee33a761d13bfb5b06ecea8829b4d05d)

(branch deleted)

Thx

Am 24.01.2017 um 18:27 schrieb Scott Mitchell<EMAIL_ADDRESS>(branch deleted)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Trying to use PlacesService

Hi, Thanks for this plugin
Looking at the geocode example
plugin.google.maps.Geocoder.geocode(request, function(results) {
, I tried using google PlacesService  like
           var request = {
                    location: center,
                    radius: 8000,
                    type: ['store']
                };
            plugin.google.maps.PlacesService.radarSearch(request, function(results) {
                alert(results.length);
            });

Should I do something in the config file or am I missing something in code?
PS. I'm using PhoneGap Build
**Sorry, I had not seen the code, I guess PlacesService or AutoComplete are not implemented
Is there a possibility of getting this?**

The only way you can get PlacesService to work would be to instantiate a map using google mapsjavascript libraries, not this plugin.  While Google recently released native API's for places, I don't believe that it is in the scope of this project to implement them.

Yes thank you
But again is it possible to call the placeservice from JS and use the results on this map
If so, this will increase the JavaScript API quota, wouldn't it?

It is possible to call placeService from js and use the results on the plugin map.  I believe the placeServices api has it's own quota separate from any map calls, but you are correct using a javascript map with the plugin map will increase the calls.

Thank you
I hope this plugin gets an upgrade
Thanks again

Could you make it? 'cause the service is attached to the map var service = new google.maps.places.PlacesService(map);

I decided to start fundraising for creating another plugin of Google Places API.
https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1888


When Session.StoreChanges is called on a document multiple times with OptimisticConcurrency enabled, a ConcurrencyException is thrown

Ex.
            var doc1 = new CoffeeShop();
            using (var session = theStore.OpenSession())
            {
                session.Store(doc1);
                session.Store(doc1);
                session.Store(doc1);

                // concurrency exception gets thrown on SaveChanges
                session.SaveChanges();
            }

From my testing, the document appear to be duplicated in the PendingChanges in the _updates field, when I put a watch on it. However calling UpdateFor<Document>().Count() is only giving me a single document. I think the PendingChanges is contributing to the ConcurrencyException, but I could be wrong.


Update controller-runtime and dependencies

This change updates the controller-runtime and associated dependencies. We fix the webhook function signatures, the Watches() implementations and the webhook declaration when the manager is initialized to comply with the latest CR standards.
Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/954
Depends-On: https://github.com/openstack-k8s-operators/install_yamls/pull/730

This will fail go vet because of the million dependencies. But it might just be a case of overriding each of them until we can get all of this merged.

Github check failing because it's still running go 1.19:
go: go.mod file indicates go 1.20, but maximum version supported by tidy is 1.19

recheck

Running the make bundle locally to check the kuttl error. But skopeo works:
❯ skopeo copy docker://quay.io/openstack-k8s-operators/placement-operator-bundle:12812f6d9604fd781a593590c8250eb8a481fec6 dir:tmp/bundle_extract/tmp
Getting image source signatures
Copying blob 472bb3aeebd9 done   |
Copying config 32e06924d1 done   |
Writing manifest to image destination

I guess the Error in this string is actually the problem, but I don't immediately see where that come from:
+ for BUNDLE in $(hack/pin-bundle-images.sh | tr "," " ")
+ skopeo copy docker://quay.io/openstack-k8s-operators/placement-operator-bundle:12812f6d9604fd781a593590c8250eb8a481fec6Error: dir:tmp/bundle_extract/tmp
time="2024-02-15T02:03:09Z" level=fatal msg="Invalid source name docker://quay.io/openstack-k8s-operators/placement-operator-bundle:12812f6d9604fd781a593590c8250eb8a481fec6Error:: invalid reference format"

Reproduced:
❯ for BUNDLE in $(hack/pin-bundle-images.sh | tr "," " "); do echo $BUNDLE; done
quay.io/openstack-k8s-operators/barbican-operator-bundle:c2163adf7b2dbe486f6ae14b0e17a8ba85a8dac9
quay.io/openstack-k8s-operators/cinder-operator-bundle:8d723e605478f874ba6fa764b7011c01662f1a0d
quay.io/openstack-k8s-operators/dataplane-operator-bundle:56156b3ceaa2b719ea6deafb14b3060f4b8dd073
quay.io/openstack-k8s-operators/designate-operator-bundle:ae268f19ceffa2636f87a1289181cab75eef1419
quay.io/openstack-k8s-operators/glance-operator-bundle:457fe24ee6ff347f6479bed2f5f1c72306105824
quay.io/openstack-k8s-operators/heat-operator-bundle:b1c60ab46d1f3b40e3142d99034113faaebf1c04
quay.io/openstack-k8s-operators/horizon-operator-bundle:e28d5c7d95a88a57a91ada568aab9ea2af59a006
quay.io/openstack-k8s-operators/infra-operator-bundle:179defb96a3363bc3684f080ea30f8e59de68017
quay.io/openstack-k8s-operators/ironic-operator-bundle:c87a0c959dc803827927f99a414ed0ae82fc4f71
quay.io/openstack-k8s-operators/keystone-operator-bundle:55af8e58473d6311c7a645b8ae87d8c9bc5b01f8
quay.io/openstack-k8s-operators/manila-operator-bundle:c4857b427c2d590ee49cdf419eb514e22f237cb1
quay.io/openstack-k8s-operators/mariadb-operator-bundle:3b28b9d3d09ba3587644f828281bb2241ecedef2
quay.io/openstack-k8s-operators/neutron-operator-bundle:985ddd95c48be5268b815ca9601a3c799b927c86
quay.io/openstack-k8s-operators/nova-operator-bundle:a1f8067ef5c629e24886de382cb1d3da53da16ba
quay.io/openstack-k8s-operators/octavia-operator-bundle:c57a33f4e98ad612c3b8a685a6928e00ee9821c3
quay.io/openstack-k8s-operators/openstack-ansibleee-operator-bundle:9bf047b38c40affa213b4d7ef1ef5b99799ef095
quay.io/openstack-k8s-operators/openstack-baremetal-operator-bundle:80b4f87cfc2b9519f2eb7b05f48ae897b1eeb56f
quay.io/openstack-k8s-operators/ovn-operator-bundle:93933dc002b7f19d094b3004aab48b29095509a0
quay.io/openstack-k8s-operators/placement-operator-bundle:12812f6d9604fd781a593590c8250eb8a481fec6Error:
SHA
is
empty
Could
not
find
container
with
tag
9615ae5dbf3c
in
https://quay.io/api/v1/repository/openstack-k8s-operators

Added some debugging here, seems to be the Swift image with problems:
hack/pin-bundle-images.sh

,quay.io/openstack-k8s-operators/barbican-operator-bundle:c2163adf7b2dbe486f6ae14b0e17a8ba85a8dac9,quay.io/openstack-k8s-operators/cinder-operator-bundle:8d723e605478f874ba6fa764b7011c01662f1a0d,quay.io/openstack-k8s-operators/dataplane-operator-bundle:56156b3ceaa2b719ea6deafb14b3060f4b8dd073,quay.io/openstack-k8s-operators/designate-operator-bundle:ae268f19ceffa2636f87a1289181cab75eef1419,quay.io/openstack-k8s-operators/glance-operator-bundle:457fe24ee6ff347f6479bed2f5f1c72306105824,quay.io/openstack-k8s-operators/heat-operator-bundle:b1c60ab46d1f3b40e3142d99034113faaebf1c04,quay.io/openstack-k8s-operators/horizon-operator-bundle:e28d5c7d95a88a57a91ada568aab9ea2af59a006,quay.io/openstack-k8s-operators/infra-operator-bundle:179defb96a3363bc3684f080ea30f8e59de68017,quay.io/openstack-k8s-operators/ironic-operator-bundle:c87a0c959dc803827927f99a414ed0ae82fc4f71,quay.io/openstack-k8s-operators/keystone-operator-bundle:55af8e58473d6311c7a645b8ae87d8c9bc5b01f8,quay.io/openstack-k8s-operators/manila-operator-bundle:c4857b427c2d590ee49cdf419eb514e22f237cb1,quay.io/openstack-k8s-operators/mariadb-operator-bundle:3b28b9d3d09ba3587644f828281bb2241ecedef2,quay.io/openstack-k8s-operators/neutron-operator-bundle:985ddd95c48be5268b815ca9601a3c799b927c86,quay.io/openstack-k8s-operators/nova-operator-bundle:a1f8067ef5c629e24886de382cb1d3da53da16ba,quay.io/openstack-k8s-operators/octavia-operator-bundle:c57a33f4e98ad612c3b8a685a6928e00ee9821c3,quay.io/openstack-k8s-operators/openstack-ansibleee-operator-bundle:9bf047b38c40affa213b4d7ef1ef5b99799ef095,quay.io/openstack-k8s-operators/openstack-baremetal-operator-bundle:80b4f87cfc2b9519f2eb7b05f48ae897b1eeb56f,quay.io/openstack-k8s-operators/ovn-operator-bundle:93933dc002b7f19d094b3004aab48b29095509a0,quay.io/openstack-k8s-operators/placement-operator-bundle:12812f6d9604fd781a593590c8250eb8a481fec6Base = swift ImageBase = \n
Error: SHA is empty, Could not find container with tag 9615ae5dbf3c in https://quay.io/api/v1/repository/openstack-k8s-operators

Looks like it failed to merge with some go.sum issues:
https://github.com/openstack-k8s-operators/swift-operator/actions/runs/7908400561
pre-commit doesn't raise any concerns now. Submitting a test PR to swift to test things.

recheck

recheck

recheck after node hold

recheck

@bshephar current failure at make bundle_build
podman build -f custom-bundle.Dockerfile -t <IP_ADDRESS>:5001/openstack-k8s-operators/openstack-operator-bundle:906d62d1eb6c5e918eca95c28c0cc7d6dbbcd135 .
[1/3] STEP 1/9: FROM golang:1.19 AS builder
Error: creating build container: short-name resolution enforced but cannot prompt without a TTY
make: *** [Makefile:271: bundle-build] Error 125

we need to update GOLANG_CTX to 1.20 here https://github.com/openstack-k8s-operators/openstack-operator/blob/main/custom-bundle.Dockerfile#L1

Looks like telemetry bundle is still missing.. It's there in quay now...

/test openstack-operator-build-deploy-kuttl

I still had a replace for telemetry-operator still. I've dropped that now.

recheck ci-framework PR needed a rebase

/override rdoproject.org/github-check


IPCs / Machine People

About the PR

Adds IPCs based on the works of Ekrixi and Sirena. Thanks to Eclips and Router for their work so far.
In addition, I ported more screens from Paradise Station in addition to the beestation ones it included. I also ported optics as an additional customisation level. Tweaked how the markings worked as well to force colour on some of them and better organised the markings.
Will be additional changes and balance to make but opening the PR for now.
Why / Balance

Technical details

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

why this keeps PRing upstream I don't know.


Can't start Portall

Hello. I'm trying to get Portall up and running for the first time.
If I have a docker-compose.yml file with contents identical to the example provided:
version: '3'
services:
  portall:
    image: need4swede/portall:latest
    container_name: portall
    ports:
      - "8080:8080"
    environment:
      - SECRET_KEY=myKeyGoesHere
    volumes:
      - ./instance:/app/instance

The container appears to be loaded, and it shows up as "healthy" in Portainer. However, loading http://<IP_ADDRESS>:8080 results in a 404 error. Ditto https.
There is nothing in the logs other than a message saying "don't use this in production".
If instead I use the docker run command, again identical to the example given:
docker run -p 8080:8080 \
  -e SECRET_KEY=myKeyGoesHere \
  -e PORT=8080 \
  -v ./instance:/app/instance \
  Portall
[1] 97478
bash: qr: command not found
david@docker1:~/dockerfilesNotOnNAS/portall$ "docker run" requires at least 1 argument.
See 'docker run --help'.

Usage:  docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

Create and run a new container from an image
^C
[1]+  Exit 1                  docker run -p 8080:8080 -e SECRET_KEY=myKeyGoesHere

...and that's it. Nothing loads.
Any suggestions please?
Thanks in advance.

try git cloning the repo and changing your docker compose to build: . instead of the image line

also your docker run does not include the image at all

try git cloning the repo and changing your docker compose to build: . instead of the image line

Thanks for your reply. I've never had to do this before so have no idea what I'm doing, but I gathered I need to install gh using apt install gh, then log in to GitHub (which I managed), then run gh repo clone need4swede/Portall.
This resulted in files being downloaded to /home/david/dockerfilesNotOnNAS/portall/Portall (e.g. your app.py, Dockerfile, etc. files are all inside that directory). For reference, my docker-compose.yml file is located the directory above, i.e. at /home/david/dockerfilesNotOnNAS/portall/
I'm not sure if that's the right thing to have done.
In any case, that didn't work.

also your docker run does not include the image at all

I have no idea how to fix that, either. I tried a bunch of things after reading the Docker run command documentation, but I couldn't figure it out.
I eventually noticed that /home/david/dockerfilesNotOnNAS/portall/Portall/docker-compose.yml exists. I opened that and my own docker-compose.yml side-by-side and they are identical, but nonetheless I added my secret key and then ran docker up on your docker-compose.yml file (rather than my own), and bingo! All working.
I have no idea why my docker-compose.yml file wouldn't work and yours did, but ...shrug, it's working now.
Thanks.


[BUG] Azure GPT 4o is limited to maximum 4096 output tokens even though model supports 16,384

Description
Cannot set it higher than 4096 even though model supports it.
Device and browser
Linux
Screenshots and more
No response
Willingness to Contribute

[ ] 🙋♂ Yes, I would like to contribute a fix.

Closing as support was provided and Azure doesn't provide the context windows.


Develop FL example based on Clara FL

Is your feature request related to a problem? Please describe.
(originally from https://github.com/Project-MONAI/MONAI/issues/498 )We can use MONAI to build many FL examples based on different FL architectures, this issue is to track the development of an example based on NVIDIA Clara FL.

addressed by https://github.com/Project-MONAI/tutorials/pull/189


audioclips wont play in audioplayback track in animationplayer when loaded node in autoload

Godot version:
beta 1 3.1
OS/device including version:

Issue description:
I am trying to make a global musicplayer that can play animations with different music loops through the use of audio playback tracks. I loaded the Node2d scene, and now AudioStreamPlayer into autoload and am communicating via script to the musicplayer scene. However, the audioplayback tracks aren't playing back the streams. Plus when using regular play keyframes, instead of the new audioplayback tracks the audio starts and restarts at random instead of playing back the track.
Steps to reproduce:
call from script to play animation, however audiotracks not playing :(
Minimal reproduction project:
MusicPlaybackBug.zip

I have a similar issue, though I don't think autoload matters.

Export a model with animations (I'm using godot-blender-exporter)
In the import settings, choose Animation.Storage=Files and Animation.KeepCustom=true
Inherit the scene
Add an AudioStreamPlayer3D
Add an "Audio Playback Track" to an animation
Set the animation to autoplay
Start the scene

The animation will play, but no sound will play. If I instead add a call method track to call AudioStreamPlayer3D.play(), it works.
example.zip
Play the example, notice there is no sound. Then disable the audio track and enable the function call track and play again. The sound will play.
The sound used in the example is https://freesound.org/people/d00121058/sounds/390757/ (CC0).

@robertarnborg  what do you mean by "regular play keyframes"?

Yo!
Thank you very much, @rcorre, looks like I ran into the same issue. For me, it's when I attempt to play a sound using an Audio Playback track that the sound doesn't play. If I use the Call Method track to run play() on the AudioStreamPlayer, it plays the sound fine.

Glad it helped, @SolarLune! It is worth noting the drawback to using the call method track is that it won't play in the editor, so you can't preview how the sound syncs with the animation.

I can't seem to get function calls or sounds to play when using an exported animation in 3.1.1.  If I add my own animation player node, they work, but that's not very helpful for syncing sounds to a character animation.

Can anyone fix this bug? same problem here

I just tested my scenario and it is now working in 3.2.2.
@robertarnborg I opened your example project and I noticed that your audio track started at a time before 0. When I moved it up to 0 playing the animation in the editor played the music.
@jitspoe and @neowoods: can you elaborate on your problem? Also double-check this:
In the import settings, choose Animation.Storage=Files and Animation.KeepCustom=true

Otherwise any edits to an imported animation won't be saved.

I suppose this could still be a bug, as if you pause the animation, drag the playhead to a different spot, and start it, the music will pick up at the right spot, but if the start of the stream is before 0 it will never play. Nice music BTW :)

I checked the project from the OP and it plays fine. At least when you fix the audio clip which starts with negative time (it can't).
The second project has no stream set in the animation, so if it was imported like that, it's unrelated issue.
Looks to me like a wrong usage of audio tracks. Feel free to comment if you have a MRP with an actual engine bug.


ingter and intra membrane transfer

I think these might be the wrong way around:

so
intramembrane lipid transporter is
Enables the transport of a lipid from a region of a membrane to a different region on the same membrane.
this implies that the other branch (transfer activity) is intermembrane?
it is defined
Removes a sterol from a membrane or a monolayer lipid particle, transports it through the aqueous phase while protected in a hydrophobic pocket, and brings it to an acceptor membrane or lipid particle. PMID:20823909 PMID:24220498 PMID:25797198
I ask for confirmation becasue I  an annotating  OSH gene orthologs.
If this is correct, can we add "intermembrane transport/ transfer as synonyms"

Its probably obvius so I closed. It took me a while to figure it out but I had some internal confounding annotations)

OK. Let me know if we can clarify somehow.


kubeproxy-free setup on dualstack cluster with IPv6 as primary fails

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
What I wish to achieve: https://docs.cilium.io/en/stable/gettingstarted/kubeproxy-free/
I spent 4 days trying to get this to work with dualstack using IPv6 as the primary IP stack and either I'm doing something wrong or it does not work with IPv6 as the primary IP stack.
Environment:
3 Ubuntu 20.04 nodes with HWE kernel (5.13), kubeadm/kubelet/kubectl 1.23.6
/etc/sysctl.d/k8s.conf:
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 1

/etc/modules-load.d/k8s.conf:
br_netfilter

kubeadm.yaml:
---
apiVersion: kubeadm.k8s.io/v1beta3
kind: ClusterConfiguration
clusterName: cilium-test
controlPlaneEndpoint: cilium1.example.com:6443
controllerManager:
  extraArgs:
    node-cidr-mask-size-ipv4: "24"
    node-cidr-mask-size-ipv6: "96"

networking:
  dnsDomain: cluster.local
  serviceSubnet: 2a02:db8:a::/112,<IP_ADDRESS>/24
  podSubnet: 2a02:db8:b::/80,<IP_ADDRESS>/20

Important to note: When IPv6 is listed first for podSubnet/serviceSubnet, it will be the primary and therefore default IP stack for SingleStack services e.g. the "kubernetes" service in the default namespace
kubeadm init:
kubeadm init --config kubeadm.yaml --upload-certs --skip-phases=addon/kube-proxy

Followed by the following helm install command:
helm install cilium cilium/cilium --version 1.11.5 --namespace kube-system --set kubeProxyReplacement=strict --set k8sServiceHost=cilium1.example.com --set k8sServicePort=6443 --set ipv6.enabled=true --set enableIPv6Masquerade=false --set ipam.mode=kubernetes

The problem
The above environment results in 3 running cilium containers and a running cilium operator.
However CoreDNS cannot speak/resolve the "kubernetes" service
~
root @ cilium1 # k logs -n kube-system coredns-64897985d-bnqr8
[INFO] plugin/ready: Still waiting on: "kubernetes"
[INFO] plugin/ready: Still waiting on: "kubernetes"
[WARNING] plugin/kubernetes: starting server with unsynced Kubernetes API
.:53
[INFO] plugin/reload: Running configuration MD5 = db32ca3650231d74073ff4cf814959a7
CoreDNS-1.8.6
linux/amd64, go1.17.1, 13a9191
[INFO] plugin/ready: Still waiting on: "kubernetes"
[INFO] plugin/ready: Still waiting on: "kubernetes"
[...]

~
root @ cilium1 # k get svc --all-namespaces
NAMESPACE     NAME         TYPE        CLUSTER-IP            EXTERNAL-IP   PORT(S)                  AGE
default       kubernetes   ClusterIP   2a02:xxxx:xxxx:a::1   <none>        443/TCP                  10m
kube-system   kube-dns     ClusterIP   2a02:xxxx:xxxx:a::a   <none>        53/UDP,53/TCP,9153/TCP   10m

As you can see the cluster-IP of all singlestack services are an ipv6 address.
Everything works right away when I recreate the cluster using IPv4 as the primary IP stack by modifying my kubeadm.yaml as such:
-serviceSubnet: 2a02:db8:a::/112,<IP_ADDRESS>/24
-podSubnet: 2a02:db8:b::/80,<IP_ADDRESS>/20
+serviceSubnet: <IP_ADDRESS>/24,2a02:db8:a::/112
+podSubnet: <IP_ADDRESS>/20,2a02:db8:b::/80

~
root @ cilium1 # k get svc --all-namespaces
NAMESPACE     NAME          TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
default       kubernetes    ClusterIP   <IP_ADDRESS>     <none>        443/TCP                  141m
kube-system   hubble-peer   ClusterIP   <IP_ADDRESS>   <none>        4254/TCP                 139m
kube-system   kube-dns      ClusterIP   <IP_ADDRESS>    <none>        53/UDP,53/TCP,9153/TCP   141m

~
root @ cilium1 # k get pods -n kube-system -l k8s-app=kube-dns
NAME                      READY   STATUS    RESTARTS   AGE
coredns-64897985d-7dcpw   1/1     Running   0          146m
coredns-64897985d-gv6sc   1/1     Running   0          146m

~
root @ cilium1 # k logs -n kube-system coredns-64897985d-7dcpw
.:53
[INFO] plugin/reload: Running configuration MD5 = db32ca3650231d74073ff4cf814959a7
CoreDNS-1.8.6
linux/amd64, go1.17.1, 13a9191

👍 🥇
I can launch the nginx application as suggested in the guide and it works.
Also I can run an ubuntu container and it will have full ipv4/ipv6 connectivity (To confirm IPv6 actually works on the host)
root@ubuntu:/# ip a show eth0
32: eth0@if33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ca:2e:0e:a5:4d:73 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2a02:xxxx:xxxx:b:0:2:0:ca92/128 scope global nodad
       valid_lft forever preferred_lft forever
    inet6 fe80::c82e:eff:fea5:4d73/64 scope link
       valid_lft forever preferred_lft forever
root@ubuntu:/# curl ifconfig.co -6
2a02:xxxx:xxxx:b:0:2:0:ca92
root@ubuntu:/# curl google.com -6
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE>

301 Moved

The document has moved
here.

root@ubuntu:/#

To debug further I have created a new cluster again, with IPv6 as the primary IP stack, ran the helm install command as mentioned earlier.
Then I have modified my kubernetes service to use Dualstack:
-ipFamilyPolicy: SingleStack
+ipFamilyPolicy: PreferDualStack

Unfortunately this still leaves my coredns containers "waiting for kubernetes".
I hope my description is clear. I have supplied you with all the data/commands I used to create the cluster and I can most definitely recreate the issue.  Unfortunately GitHub refuses the sysdump zip file with a HTTP 422. Any questions or log files you may need I'll try to supply them asap.
Cilium Version
Helm chart version 1.11.5
Kernel Version
Linux cilium1 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
1.23.6
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.6", GitCommit:"ad3338546da947756e8a88aa6822e9c11e7eac22", GitTreeState:"clean", BuildDate:"2022-04-14T08:49:13Z", GoVersion:"go1.17.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.6", GitCommit:"ad3338546da947756e8a88aa6822e9c11e7eac22", GitTreeState:"clean", BuildDate:"2022-04-14T08:43:11Z", GoVersion:"go1.17.9", Compiler:"gc", Platform:"linux/amd64"}

Sysdump
The zip file refuses to upload with a HTTP 422 Unprocessable Entity :(
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@vosdev Could you check whether the CoreDNS pod is able to establish a communication to the kube-apiserver? For instance,  you could timely use nsenter to enter its netns and then try curl -vvv https://[2a02:xxxx:xxxx:a::1].

Yes, cilium1.example.com resolves to the control-plane's ipv6 address.
I have just recreated a cluster with the "broken" config by stating IPv6 first and IPv4 second to try and contact the kube-apiserver based on the service ipv6 address as requested.
root @ cilium1 # k get svc
NAME         TYPE        CLUSTER-IP            EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   2a02:abcd:3cc4:a::1   <none>        443/TCP   5m46s

~
root @ cilium2 # pidof coredns
8972

~
root @ cilium2 # nsenter -t 8972 -n curl -vvv 'https://[2a02:abcd:3cc4:a::1]'
*   Trying 2a02:abcd:3cc4:a::1:443...
* TCP_NODELAY set
* connect to 2a02:abcd:3cc4:a::1 port 443 failed: Connection timed out
* Failed to connect to 2a02:abcd:3cc4:a::1 port 443: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to 2a02:abcd:3cc4:a::1 port 443: Connection timed out

To debug further I have just recreated the cluster again with the change that makes everything work, so specifying IPv4 before IPv6 like such:
-serviceSubnet: 2a02:db8:a::/112,<IP_ADDRESS>/24
-podSubnet: 2a02:db8:b::/80,<IP_ADDRESS>/20
+serviceSubnet: <IP_ADDRESS>/24,2a02:db8:a::/112
+podSubnet: <IP_ADDRESS>/20,2a02:db8:b::/80

The coredns containers come up seconds after the cilium containers and I have a functional cluster
~
root @ cilium1 # k get pods --all-namespaces -o wide -w
NAMESPACE     NAME                               READY   STATUS    RESTARTS   AGE    IP               NODE      NOMINATED NODE   READINESS GATES
kube-system   cilium-68lnn                       0/1     Running   0          7s     <IP_ADDRESS>   cilium1   <none>           <none>
kube-system   cilium-cv8tx                       0/1     Running   0          7s     <IP_ADDRESS>   cilium3   <none>           <none>
kube-system   cilium-fsf7c                       0/1     Running   0          7s     <IP_ADDRESS>   cilium2   <none>           <none>
kube-system   cilium-operator-5c6bc58879-5784d   1/1     Running   0          7s     <IP_ADDRESS>   cilium3   <none>           <none>
kube-system   cilium-operator-5c6bc58879-662f9   1/1     Running   0          7s     <IP_ADDRESS>   cilium2   <none>           <none>
kube-system   coredns-64897985d-42j9k            0/1     Pending   0          117s   <none>           <none>    <none>           <none>
kube-system   coredns-64897985d-kgxk9            0/1     Pending   0          117s   <none>           <none>    <none>           <none>
kube-system   etcd-cilium1                       1/1     Running   18         2m5s   <IP_ADDRESS>   cilium1   <none>           <none>
kube-system   kube-apiserver-cilium1             1/1     Running   0          2m5s   <IP_ADDRESS>   cilium1   <none>           <none>
kube-system   kube-controller-manager-cilium1    1/1     Running   0          2m5s   <IP_ADDRESS>   cilium1   <none>           <none>
kube-system   kube-scheduler-cilium1             1/1     Running   38         2m5s   <IP_ADDRESS>   cilium1   <none>           <none>
kube-system   coredns-64897985d-kgxk9            0/1     Pending   0          118s   <none>           cilium3   <none>           <none>
kube-system   coredns-64897985d-42j9k            0/1     Pending   0          118s   <none>           cilium3   <none>           <none>
kube-system   coredns-64897985d-kgxk9            0/1     ContainerCreating   0          118s   <none>           cilium3   <none>           <none>
kube-system   coredns-64897985d-42j9k            0/1     ContainerCreating   0          119s   <none>           cilium3   <none>           <none>
kube-system   cilium-cv8tx                       0/1     Running             0          28s    <IP_ADDRESS>   cilium3   <none>           <none>
kube-system   cilium-fsf7c                       0/1     Running             0          28s    <IP_ADDRESS>   cilium2   <none>           <none>
kube-system   cilium-fsf7c                       1/1     Running             0          28s    <IP_ADDRESS>   cilium2   <none>           <none>
kube-system   cilium-cv8tx                       1/1     Running             0          28s    <IP_ADDRESS>   cilium3   <none>           <none>
kube-system   cilium-68lnn                       0/1     Running             0          30s    <IP_ADDRESS>   cilium1   <none>           <none>
kube-system   cilium-68lnn                       1/1     Running             0          31s    <IP_ADDRESS>   cilium1   <none>           <none>
kube-system   coredns-64897985d-42j9k            0/1     Running             0          2m34s   <IP_ADDRESS>     cilium3   <none>           <none>
kube-system   coredns-64897985d-kgxk9            0/1     Running             0          2m35s   <IP_ADDRESS>      cilium3   <none>           <none>
kube-system   coredns-64897985d-42j9k            1/1     Running             0          2m35s   <IP_ADDRESS>     cilium3   <none>           <none>
kube-system   coredns-64897985d-kgxk9            1/1     Running             0          2m35s   <IP_ADDRESS>      cilium3   <none>           <none>
^C

However, when I the nsenter to the coredns process's network namespace and attempt to curl the kube-api-server on 6443 it still doesn't work via the IPv6 address
~
root @ cilium3 # pidof coredns
13857 13771

~
root @ cilium3 # nsenter -t 13857 -n curl -vvv 'https://[2a02:abcd:3cc4:1:216:3eff:feaf:fe95]:6443'
*   Trying 2a02:abcd:3cc4:1:216:3eff:feaf:fe95:6443...
* TCP_NODELAY set
* connect to 2a02:abcd:3cc4:1:216:3eff:feaf:fe95 port 6443 failed: Connection timed out
* Failed to connect to 2a02:abcd:3cc4:1:216:3eff:feaf:fe95 port 6443: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to 2a02:abcd:3cc4:1:216:3eff:feaf:fe95 port 6443: Connection timed out

~
root @ cilium3 # nsenter -t 13857 -n curl -vvv 'https://<IP_ADDRESS>:6443'
*   Trying <IP_ADDRESS>:6443...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 6443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
[..]

I run v6 primary, v4 secondary dual stack with kubeproxy-free cilium in production. Here's a minimal version of our kubeadm config that seems to work...
---
apiVersion: kubeadm.k8s.io/v1beta3
featureGates:
  IPv6DualStack: true
kind: ClusterConfiguration
networking:
  podSubnet: <v6>,<v4>
  serviceSubnet: <v6>,<v4>
---
apiVersion: kubeadm.k8s.io/v1beta3
kind: InitConfiguration
skipPhases:
  - addon/kube-proxy
localAPIEndpoint:
  advertiseAddress: "<v6>"
  bindPort: 6443
nodeRegistration:
  kubeletExtraArgs:
    node-ip: <v6>,<v4>

and then here's a minimal version of our Helm chart values that seems to work...
kubeProxyReplacement: strict
k8sServiceHost: "<v6>"
k8sServicePort: 6443
operator:
  replicas: 1
bpf:
  masquerade: true
ipam:
  mode: kubernetes
ipv6:
  enabled: true
ipv4:
  enabled: true
k8s:
  requireIPv6PodCIDR: true
  requireIPv4PodCIDR: true
enableIPv6Masquerade: false
hubble:
  relay:
    enabled: true
  ui:
    enabled: true
ingressController:
  enabled: true

Although just as a word of unsolicited advice: don't do this yet. I have patched versions of pretty much every component of my cluster to get other things to work (I'll upstream them eventually!). Even after you get CoreDNS to work it will still be pain 😭

Issue still present


[DNM] nrf: remove dependency for device.h in soc.h

Experimental; do not merge.
The PR investigates the issue of having soc.h headers including kernel.h (via device.h).
This is not required in principle, so we should try to remove it.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1765d75). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #8494   +/-   ##
=========================================
  Coverage          ?   64.61%
=========================================
  Files             ?      421
  Lines             ?    40296
  Branches          ?     6803
=========================================
  Hits              ?    26037
  Misses            ?    11126
  Partials          ?     3133

Impacted Files
Coverage Δ

include/kernel.h
95.16% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1765d75...810e1b1. Read the comment docs.