Addresses additional issues with #9

Improvements:

Don't hardcode to https but detect if it is an onion or i2p URL.
Add HttpClient as an optional parameter to Validate, though still dispose if we create our own. Otherwise leave it to the caller.

I don't really have a good example of a NIP-05 identifier that satisfies "dont hardcode to https but detect if it is an onion or i2p URL", do you happen to know of at least one?

I don't really have a good example of a NIP-05 identifier that satisfies "dont hardcode to https but detect if it is an onion or i2p URL", do you happen to know of at least one?

<EMAIL_ADDRESS>

woof, sorry @Kukks - mangled the pull request a bit.


Fixed travis build

Fixed travis build for both JDK7 and JDK8

Fixed travis build (#5)
Now Travis-CI correctly runs tests on Chino.io Java SDK using both JDK8 and JDK7.
The testing is done with stages (travis-ci/travis-stages@82f1f9e15f021794af270e9f573aa3c51cbd6d8c), a beta feature of Travis-CI


Cannot find symbol Error

hello! ive been getting this "Cannot find symbol" error (but it works when I upload my files codecrunch and I managed to clear the level?) in this case, i had to keep submitting without being able to test the cases myself. is there any way i could fix this or am i doing something wrongly? thanks in advance:-)

hello, did you set your classes to public?

Having the same issue.

Hi Eve, I agree with @shanernigans, did you remember to set your methods to public? Hope this helps!

Hey there, agree with @shanernigans.
You may also want to take a look if you packaged the Customer in the simulator as well. Hope this helps!

ohh i see thanks everyone for ur help:-)


AWS Lambda with Single Subsegment Not Sent

Lambdas automatically come with a root segment that can be captured with
const segment = new AWSXRay.Segment('Root Segment);
AWSXRay.utils.LambdaUtils.populateTraceData(segment, process.env._X_AMZN_TRACE_ID);

If you add a single subsegment to that root subsegment (and any number of sub-subsegments to that subsegment), nothing gets sent to Xray.
For example:

Root Segment (automatically created)

subseg Subsegment

sleep Subsegment
sleep Subsegment
sleep Subsegment

I think this is due to the code in Subsegment.close():
  if (this.parent)
    this.parent.decrementCounter();

  if (root && root.counter > SegmentUtils.getStreamingThreshold()) {
    if (this.streamSubsegments() && this.parent)
      this.parent.removeSubsegment(this);
  }

Note that in lambda, the streaming threshold is set to 0.
At the moment that all three sleep subsegments are closed, the root has a counter of 1. When subseg.close() is called, the parent/root's counter gets decremented to 0, and therefore this.streamSubsegments() is never called for this subsegment.
This is only a problem on lambda since Segment.close() does nothing. On non-lambda environments, the last subsegment is sent along with the root segment during flush().
Here is my sample application:
AWSXRay.enableManualMode();

const sleep = (parentSegment) => {
  return new Promise(resolve => {
    const subsegment = parentSegment.addNewSubsegment('sleep');
    setTimeout(() => {
      subsegment.close();
      resolve();
    }, 200);
  })
}

module.exports.withSubsegment = async (event, context, callback) => {
  context.callbackWaitsForEmptyEventLoop = true;

  const segment = new AWSXRay.Segment('multi-no-async');
  AWSXRay.utils.LambdaUtils.populateTraceData(segment, process.env._X_AMZN_TRACE_ID);

  const subsegment = segment.addNewSubsegment('subseg');

  await sleep(subsegment);
  await sleep(subsegment);
  await sleep(subsegment);

  subsegment.close();

  segment.close();

  callback(null, 'done')
};

I'm not sure what the right fix is here. Do we modify aws_lambda.js Segment.close() to add a call to flush(), or do we reorder the operations in subsegment.close() to decrement the parent counter only after the call to streamSubsegments()?

Hi timtrinidad,
Sorry for the issues, let me help clear up some confusion.

Lambdas automatically come with a root segment that can be captured with
const segment = new AWSXRay.Segment('Root Segment);
AWSXRay.utils.LambdaUtils.populateTraceData(segment, process.env._X_AMZN_TRACE_ID);

While this is technically true, the SDK is configured to automatically create a facade segment when the it detects it's running in Lambda. The Lambda segment as seen on the X-Ray console is created in the Lambda's runtime start-up code, and is sent asynchronously and independent from the X-Ray SDK. Thus, the facade segment is a placeholder, which only contains the trace it/parent id/sampling decision that Lambda created. It is never meant to be sent. In this way, the X-Ray backend recompiles the full segment via the subsegments sent from the customer code together with the segment sent independently by Lambda. This facade is set on the CLS context, hence why manual mode is disabled on Lambda.
By creating the segment manually in this fashion, you are introducing a conflict. The facade segment created with populateTraceData sets the parent ID to be the ID of the segment, because it's supposed to be a fake copy of the Lambda segment, and never actually be sent.
The Lambda segment sent asynchronously, and the newly created segment decorated with populateTraceData() share the same ID and thus the manually created segment is being rejected by the X-Ray backend due to this ID conflict.

This is only a problem on lambda since Segment.close() does nothing.

This is only true for the instance of the facade segment, not all manually created segments.
If you manually create a new segment with a new ID (but sharing the trace ID and the sampling decision), you'll be able to send a new segment.
So, you have two options, simply create subsegments which will create a single AWS::Lambda::Function node on the X-Ray service map:
const segment = new AWSXRay.getSegment();     //returns the facade segment automatically created
const segment.addNewSubsegment('subseg');

Or, there's a workaround - create a new segment with a new ID, but this will display your segment as a separate node in the service map (AWS::Lambda::Function -> multi-no-async).
const traceData = AWSXRay.utils.LambdaUtils.processTraceData(process.env._X_AMZN_TRACE_ID);
const segment = new AWSXRay.Segment('multi-no-async', traceData.Root, traceData.Parent);
AWSXRay.middleware.resolveSampling(traceData, segment);

Hope this helps,
Sandra

Sandra,
Thanks for the info! Unfortunately, we're using async/await/promises we we're on manual mode and therefore getSegment() won't work. With the second method, we noticed that the separate document sometimes ends up above the AWS::Lambda::Function, making the trace in the console more difficult to parse.

The Lambda segment sent asynchronously, and the newly created segment decorated with populateTraceData() share the same ID and thus the manually created segment is being rejected by the X-Ray backend due to this ID conflict.

Is this actually the case? When I enable debugging logs, I see that the Segment is sent successfully, since as far as I know you can send a segment multiple times to update things like in progress or end time.

Hi timtrinidad,
Promises are supported via the X-Ray SDK out of box, and async/await structures are supported via the experimental branch.
As mentioned before, manual mode is disabled on Lambda so I am curious as to how you are using the constructs to achieve that effect. The segment resolution logic for any capture* function (AWS, HTTP/S and other patchers) relies on the CLS context being present.
Keep in mind, you can use the SDK in automatic mode but use manually created segments and subsegments - there is no conflict there. You should be able to use getSegment to grab the initial Lambda segment, and manually create subsegments and manually pass them around, if you are not using the capture* functions.
The segment is sent successfully, but is being rejected by the X-Ray backend, as it is asynchronously sent via the X-Ray Daemon present on the Lambda instance. If a Segment is incorrectly formatted, or has a conflict, this will not appear on the Lambda console. When a segment is sent, it is sent via UDP packet to be picked up by the Daemon. This message is that the packet sent successfully, useful for diagnosing when a segment or subsegment is dangling or failed to close.

As per your recommendation, we gave the experimental branch with automatic mode a try, and it works well. Thank you!


Issue #134 merge partitions with inconsistent grids amongst partitions

Fix #134 and #86,
Add support for merging partitions with different grids in each partition, for example 1D grid in one partition and 2D grids in each. Quite some refactoring was required:

groups grids, data_objects, and other_vars by gridname
all partitions with a certain grid should have the same variables, this is validated
connectivity dims are padded to maximum size if not occurring
add property to AbstractUgrid to get connectivity dimension names

Tested with both examples from #134 and #86 and they both work. However, I do notice odd behaviour. When using xu.open_mfdataset the merging takes 0.3 seconds. When using xu.open_dataset the merging takes >200 seconds:
import glob
import xugrid as xu
import datetime as dt

file_nc = r'p:\1230882-emodnet_hrsm\GTSMv5.0\SO_NHrivGTSM\computations\BD014_fix_mapformat4\output\gtsm_model_0*_map.nc'
file_nc_list = glob.glob(file_nc)
partitions = []
for iF, file_nc_one in enumerate(file_nc_list):
    uds_part = xu.open_mfdataset(file_nc_one)
    partitions.append(uds_part)
dtstart = dt.datetime.now()
uds = xu.merge_partitions(partitions)
print(f'merging took: {(dt.datetime.now()-dtstart).total_seconds():.2f} sec')

I guess you can also try loading the datasets with just xr.open_dataset, then turning them into UgridDatasets, then merging them.
That will give the same result, I'm fairly sure. The xugrid.open_mfdataset just adds the data_vars kwarg then calls xr.open_mfdataset.
Is there maybe a difference between the eagerness? If you call .compute() in the timing, are the timings the same?

@Huite, thanks for your suggestions. Indeed, the combination of ds=xr.open_dataset() and xu.UgridDataset(ds) behaves the same. And your second suggestion, to call .compute() significantly increases the performance indeed (0.8 sec). This also triggered me to remember the importance of the chunks argument (chunks={"time":1} is the default in dfm_tools), this also worked as a charm (0.5 sec). So I guess we can conclude there was no additional problem introduced with this PR, and the PR also provides working additional functionality

Great job!


Features/limit order bot

Background
Limit order bot smart contracts in Rust.

@webelf101 & @wc117 What's the delay blocking getting this into production?


Design exploration for VS Code Integration

Follows #571
Includes exploration + execution

Update 10/09/2022
Moved into To be scheduled/prioritized until Savannah has more time to flesh out requirements.

Closing for now!


Enabling shoulds crashes

instantiating 'Array(Redis::RedisValue)#should(Spec2::Matchers::Eq(Array(String)))'
in spec/spec_helper.cr:4: expanding macro

Spec2.enable_should_on_object
^

in macro 'enable_should_on_object' /home/faust/Projects/tele-broadcaster/lib/spec2/src/should.cr:2, line 3:

   1.     class Object
   2.       def should(matcher)
>  3.         ::Spec2::Context.expect(self).to matcher
   4.       end
   5.
   6.       def should_not(matcher)
   7.         ::Spec2::Context.expect(self).not_to matcher
   8.       end
   9.     end
  10.

undefined method 'expect' for Spec2::Context:Class

crystal 0.23.1

Just started to use spec2, and also encountered this problem.
I added the following to spec2/src/next/context.cr
to get things going
def self.expect(actual)
  Expectation.new(actual)
end

Crystal 0.26.1 [391785249] (2018-08-27)


Instaling dependnices

I am trying to installing the dependencies by running
conda create --name <env> --file requirements.txt
However, since I don't have many of the required channels, my conda cannot install all of them. Moreover, my conda also cannot file the pip packages (pypi_0) from my current channels, even though I have pip. Can you please provide the .yml file of your environment, which contains the full description of the environment, including the conda channels?
Thanks!

Could you please also mention how did you install spacy and scispacy? And how en_core_sci_md was downloaded?
This is how I installed them:
pip install spacy==2.0.18
pip install scispacy==0.1.0
pip install https://s3-us-west-2.amazonaws.com/ai2-s2-scispacy/releases/v0.4.0/en_core_sci_md-0.4.0.tar.gz

Apologies for the huge delay! Yes, that should work.

Thanks!


Embeddings with StableLM?

Is it possible to get embeddings from the model for my input text?
I.e. could I replace GTP3 calls from OpenAI with some python code and this model?

I would recommend taking a look at https://www.sbert.net/ . To my best knowledge the OpenAI models are not outstanding at all for embeddings (https://huggingface.co/spaces/mteb/leaderboard) but it is convenience to use the API of them - at least for us.

If it helps, I have successfully used: sentence-transformers/all-mpnet-base-v2 as an alternative to the OpenAI text-embedding-ada-002

Hello, i am able to extract the embeddings from the model.
checkpoint = "path/to/the/model"
config = AutoConfig.from_pretrained(checkpoint)
model = AutoModelForCausalLM.from_config(config)
tokenizer = AutoTokenizer.from_pretrained(checkpoint)
inputs = tokenizer.encode('Stability AI democratised AI by open sourcing large models', return_tensors="pt")
outputs = model(inputs)
hidden_states = output[1]
now hidden states has  output of all the layers.

These models are multi-lingual?

If you are looking for another convenient API might consider embaas. They offer a similiar structure to openai and you can use the MTEB leaderboard top members. They have some mutlilingual models as well and integrate wiht langchain or have an easy to use python client


python312Packages.ocrmypdf: 16.4.2 -> 16.4.3

Description of changes
Diff: https://github.com/ocrmypdf/OCRmyPDF/compare/v16.4.2...v16.4.3
Changelog: https://github.com/ocrmypdf/OCRmyPDF/blob/v16.4.3/docs/release_notes.rst

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 332214 run on x86_64-linux 1

5 packages built:

ocrmypdf (python312Packages.ocrmypdf)
ocrmypdf.dist (python312Packages.ocrmypdf.dist)
paperless-ngx
python311Packages.ocrmypdf
python311Packages.ocrmypdf.dist


Support delegation.

We could/should supported delegations. This means letting a msg.Service (msg.Delegation probably) insert NS and DS records to delegate a domain to a different set of nameservers.

This would need issue #47 support, but still be dynamic: i.e. how does skydns know it is authoritative for a domain. OR all delegation must fall under the top-level domain for which skydns is configured. The latter makes more sense, and is dynamic because everything is stored in the backend. For multiple delegations and being able to do it issue #47 (once fixed) would give us that.

Or another thing/use-case would be special a Forward service, which if specified would instruct SkyDNS to go query the remote servers by itself and return the results. Sort of Auth to Auth forwarding.

Of course this is harder than it looks. Specifically SkyDNS gets a query for this.machine.in.this.domain.skydns.local for which it should forward to the domain.skydns.local machines. Currently this will just result in NXDOMAIN or whatever because that name does not exist in the backend (the Forward message is stored in domain.skydns.local). So how would SkyDNS know it should look there....
This can work if there is a separate part of the tree in which we store these Forward messages. We already hijack dns.skydns.local under which we could hang these. Read the list on startup (add a Watch go get updates (needs to be added to the Backend interface)).
So ones stores something under bar.skydns.local.dns.skydns.local so say that the bar.skydns.local domain should be forward to somewhere else. We could store these in a map and before actually going to our local backend. (Maps needs mutex, should use RCU there as well).

We can just re-use msg.Service for this. To support multiple services you need to register multiple services, i.e. under bar.skydns.local.skydns.local you add one under the name x1, x2. etc.
Added benefit: each server could run on a different port can be be updated independently.
Downside: the rule for looking up the nameservers needs to take into account that it should drop one part of the keyspace to know the actual domain. Still doable.

stubzones branch has the proto implementation that will make this work.

Stubzones is good enough for now (also lack time to implement such a feature)


Fix agreements_package_content_item

Closes #633

The query has been adapted to the new data schema.

[ ] Pull request has a complete description
[ ] Query runs without errors
[ ] Query output is correct
[ ] Query logic is clear and well documented
[ ] Query is readable and properly indented
[ ] Table and column names are in all-lowercase
[ ] Quotation marks are used only where necessary
[ ] Query begins with user documentation in comment lines
[ ] File name is listed in runlist.txt after dependencies
[ ] All columns have indexes
[ ] Table is vacuumed and analyzed

PR is blocking #618


Restore FireAndForget method to notify subscribers about the event

Purposes:

Do not repeat the code
Do not call Task.Run() if there are no subscribers

PS: rollback the following commit https://github.com/IdentityModel/IdentityModel2/commit/f56ef26c878b0c5d42f0cf72a5bd8a929504c796

I will remove this class altogether - not happy with the design.


Add bash completion for DNS settings in services

Ref: #27567
please schedule for 1.13.0
ping @sdurrheimer for zsh completion

LGTM


Translation to spanish of jslingo.json

Closes #6999

Just a couple of suggestions here and there. Great job @vtamara!

@vtamara updated the pull request.

Thanks for corrections @justinian336.  Ready for merging.

:+1:


On OSX overtime you run yubioath it succeeds but prints error message "Failed to execute script yubioath-script"

Using version 3.0.1 installed using the OS X package, when you run the yuioath cli client (any command) the command itself works but it always displays the error message 'Failed to execute script yubioath-script'

Possibly related to this, will look into it.

Yes building the bootloader manually for PyInstaller as suggested seems to resolve this issue. Will do this (if the issue is not fixed in PyInstaller) for the next release.


Add JIRA feature branch provider

Feature request
A JIRA extension should be provided to connect to different JIRA instances and return feature-branches based on the tickets.

Requires #13


removed configsync dependency

Removed the dependency to configsync namespace, but we need to see if the namespace is to be set.

So this PR adds 2 changes to make it independent on configsync.

the syncApp should be changed from configsync to tobeinstalledonremotecluster
the remoteNamespace can be set. For Configsync this has to eb set.

@henderiw If I understand correctly I still have to create the secret in the management cluster right? Only then Nephio-Controller will act on it. In this case is it possible to add a possibility to populate the secret in the multiple clusters?

@arora-sagar I added logic to add the secret to a multiple clusters.

/lgtm
/approve

/approve


error after running '/opt/intel/mediasdk/bin/vainfo'

environments:

OS:ubuntu18.04
kernel:Linux version 5.4.0-52-generic (buildd@lcy01-amd64-022) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020
CPU:Intel® Core™ i7-4790 CPU @ 3.60GHz
openvino:2020.1

i have successfully installed openvino2020.1, but after running /opt/intel/mediasdk/bin/vainfo got errors as follows
libva info: VA-API version 1.6.0
libva info: va_getDriverName() returns 0
libva info: User requested driver 'iHD'
libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_6
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
libva error: /opt/intel/mediasdk/lib64/iHD_drv_video.so init failed
libva info: va_openDriver() returns 18
vaInitialize failed with error code 18 (invalid parameter),exit

Hi @niuwenju what media driver version you used?

i7-4790 is HSW. It is not supported neither by mediasdk nor by iHD driver.
You might get HW acceleration support thru i965 driver by installing (mediasdk won't work however):
apt-get install i965-va-driver

If you will continue to use vainfo and libva from openvino installation (but I would advice not doing that and rely on system version), you might need to expose:
export LIBVA_DRIVER_NAME=i965
export LIBVA_DRIVERS_PATH=/usr/lib/x86_64-linux-gnu/dri


Update Tests to match 3D Refactor

Update Tests to Include New Code from 3D Refactor
Old tests fail miserably. Fix this.

lol need to actually add some new tests after this big boi got merge in on #10


SymIntify roi_align

This is one step in making it possible to trace through roi_align in PT2 with dynamic=True; the other missing piece is a meta function.
The duplication of the C++ signatures is a bit of a chore.  In PyTorch core we have a codegen that can handle it, but we don't have that here unfortunately.
Signed-off-by: Edward Z. Yang<EMAIL_ADDRESS>

@NicolasHug I'm going to try to stand up some sort of shared testing infrastructure across the repos to do it, so yeah, separate PR would be appreciated


[Event Request] table 81 "Gen. Journal Line" - OnGetCustLedgerEntryAfterCalcRemainingAmount

Describe the request
Hello, can you please add a new Event OnGetCustLedgerEntryAfterCalcRemainingAmount in table 81 "Gen. Journal Line"?
    procedure GetCustLedgerEntry()
    var
.
.
.
            Validate("Account No.", CustLedgEntry."Customer No.");
            OnGetCustLedgerEntryOnAfterAssignCustomerNo(Rec, CustLedgEntry);

            if Amount = 0 then begin
                CustLedgEntry.CalcFields("Remaining Amount");
                OnGetCustLedgerEntryAfterCalcRemainingAmount(CustLedgEntry);

                if "Posting Date" <= CustLedgEntry."Pmt. Discount Date" then
                    Amount := -(CustLedgEntry."Remaining Amount" - CustLedgEntry."Remaining Pmt. Disc. Possible")
                else
                    Amount := -CustLedgEntry."Remaining Amount";

                if "Currency Code" <> CustLedgEntry."Currency Code" then
                    UpdateCurrencyCode(CustLedgEntry."Currency Code");

    [IntegrationEvent(false, false)]
    local procedure OnGetCustLedgerEntryAfterCalcRemainingAmount(var CustLedgerEntry: Record "Cust. Ledger Entry")
    begin
    end;

Additional context
We have additional values to calculate the Remaining Amount and need to recalculate it to get the correct Amount for the Gen. Journal Line.
Internal work item: AB#546851

Availability update: We will publish a fix for this issue in the next update for release 25.
Build ID to track: 26357.


update SDK to track2 in ensureGatewayCreate

Which issue this PR addresses:

Fixes a part of https://issues.redhat.com/browse/ARO-4665 and https://issues.redhat.com/browse/ARO-7316
This is blocked by #3594
What this PR does / why we need it:

This PR makes ensureGateway action use track2 SDK.
Test plan for issue:

unittest for ensureGateway.
e2e
Is there any documentation that needs to be updated for this PR?

tech debt cleanup N/A
How do you know this will function as expected in production?

cluster installation test

/azp run ci,e2e

/azp run ci,e2e

/azp run e2e

/azp run ci,e2e

Waiting for https://github.com/Azure/ARO-RP/pull/3579 to be released because it had a bug about tenant ID settings, and want to confirm it works first.

/azp run ci,e2e


Cannot figure how to make it work

Following your directories structure, I partially managed to create my templates, while mixing some .chezmoiexternal.$FORMAT files.
After running chezmoi apply, here's what the ~/.config/firefox directory looks like:
❯ tree -L 4 .config/firefox
.config/firefox
└── profiles
    └── default-release
        ├── chrome
        │   ├── Firefox-Mod-Blur-chrome.css
        │   ├── Firefox-Mod-Blur-content.css
        │   ├── Firefox-UI-Fix-chrome.css
        │   ├── Firefox-UI-Fix-content.css
        │   ├── css
        │   ├── icons
        │   ├── image
        │   ├── userChrome.css
        │   ├── userContent.css
        │   └── window
        ├── prefsCleaner.sh
        ├── updater.sh
        └── user-overrides.js

The dirs/files structure is fine in the sense that it's exactly how it should be if the Firefox profile was in ~/.mozilla/firefox/default-release. However, I don't understand how ~/.config/firefox is supposed to interact with ~/.mozilla/firefox/$PROFILE_DIR.

dot_mozilla/firefox/profiles.ini.tmpl:

{{- template "firefox/profiles.ini" . -}}

.chezmoitemplates/firefox/profiles.ini (slightly modified since I'm only using Linux):

{{- /* Final profile path */ -}}
{{- $releasePath := joinPath .chezmoi.homeDir "/.config/firefox/profiles/default-release" -}}

{{- /* ID */ -}}
{{- $releaseId := "0" -}}

{{ if eq .distro "archlinux" }}
{{- $releaseId = mozillaInstallHash "/usr/lib/firefox" -}}{{- /* "????????????????" */ -}}
{{ end }}

{{ if eq .distro "gentoo" }}
{{- $releaseId = mozillaInstallHash "/usr/lib64/firefox" -}}{{- /* "????????????????" */ -}}
{{ end }}

[Profile0]
Name=default-release
IsRelative=0
Path={{- $releasePath }}

[General]
StartWithLastProfile=1
Version=2

[Install{{- $releaseId -}}]
Default={{- $releasePath }}
Locked=1

I guess the issue is with this profile.ini template. I noticed you added the profile hash (which I replaced with "?" characters), are these actually required when using mozillaInstallHash function?
When I run chezmoi apply -v, I don't have any output. ~/.config/firefox is created but ~/.mozilla/ is not, so there's no ~/.mozilla.firefox/profiles.ini file generated either.
As a result, when I run Firefox, a new profile is generated in ~/.mozilla/firefox/xxxxyyyy.default-release and none of the ~/.config/firefox/profiles/default-release is applied.
I tried to remove the if statement in the template just in case I made a mistake but it doesn't make any difference:
{{- $releaseId = mozillaInstallHash "/usr/lib/firefox" -}}{{- /* "????????????????" */ -}}

I'm doing tests in an Arch Linux VM so I'm 100% sure the /usr/lib/firefox path is correct.
Many thanks in advance for your help.

I guess the issue is with this profile.ini template. I noticed you added the profile hash (which I replaced with "?" characters), are these actually required when using mozillaInstallHash function?

These are just comments showing what the output of mozillaInstallHash <path> should be. I should really remove them.

When I run chezmoi apply -v, I don't have any output. ~/.config/firefox is created but ~/.mozilla/ is not, so there's no ~/.mozilla.firefox/profiles.ini file generated either.

Interesting. Do you have .mozilla in .chezmoiignore by any chance?
Is there any chance you could link your dotfiles repo? Or copy it to a sample repo?
Also, you don't have to put your profiles in .config/firefox. I just chose that because it works on all of the platforms I use. You can put them in .mozilla and use relative paths and set IsRelative to 1 if you want.

I ignore .mozilla/ on Windows, because profiles.ini is stored in AppData/ on Windows.
The .chezmoiignore conditional can be tricky because it's basically a double negative, but it's essentially...

If we are on any platform except Windows (Linux, macOS etc.), ignore AppData/
If we are on Windows, ignore .mozilla/

...maybe I should add a comment to clarify.
If you only use Linux you can just delete the AppData directory and you no longer need to ignore any of the files from this repo within .chezmoiignore.

One last question about if you don't mind since I couldn't really find an answer in the chezmoi documentation.
For now, I manually created all the templates /externals dirs and files in chezmoi source dir.

This is what I do. I navigate to the source directory in my editor and create directories and files in there, then run chezmoi diff and chezmoi apply.

Is there anything wrong tracking them with chezmoi add? I'd like to keep them under version control but I'm not sure if this is a proper way to do it, of even if it's recommended to do.

There isn't really a proper way to do it. At the end of the day you're just putting files in the source directory and then committing them to a version control repo. How they get put there is up to you.
That said, I will mention that chezmoi add works best for files which are not templates. For templates you're much better off creating them manually in the source directory.
If chezmoi has created ~/.zshrc as a regular file, you can either edit ~/.local/share/chezmoi/dot_zshrc and run chezmoi apply, or you can edit ~/.zshrc and run chezmoi add ~/.zshrc.
Hope that helps.

Definitely, that's easier and that's what I did. However, when added manually, the templates and the .chezmoiexternals files aren't under version control. For example (~/dotfiles is my source dir):

If the files are in your source directory, they should be under version control.

Is there something wrong running chezmoi add ~/dotfiles/.chezmoitemplates ; .chezmoi.yaml.tmpl ; dot_mozilla and so on to keep these templates and .chezmoiexternal files under version control?
I've just tried and everything seems just fine after another chezmoi apply. Asking because we usually run chezmoi add for dirs and files from $HOME, not from the source directory.

The paths you provide to chezmoi add and chezmoi edit should be from the destination directory ($HOME). If you provide a path from the source directory you can end up adding it back to the source directory. It's easier to see with the default source directory:
~/.local/share/chezmoi/private_dot_local/share/chezmoi etc.
This is the primary reason I create everything manually, I don't want to deal with anything like that.
You can also run chezmoi cd; nvim .chezmoiignore etc. if you prefer.

What are you referring to when you say version control? To me, version control is git. The source directory should already be a git repo. You can verify this with chezmoi git status or chezmoi cd; git status.

> chezmoi edit .chezmoiignore
chezmoi: .chezmoiignore: not in source state

This isn't an exact explanation, but chezmoi edit is essentially looking for ~/.chezmoiignore, which doesn't exist in the source directory (e.g. ~/dotfiles/dot_chezmoiignore), nor should it.
I don't believe it's possible to edit .chezmoi* files with chezmoi edit.
If you create a file e.g. ~/.a, then run chezmoi add .a, chezmoi will create ~/dotfiles/dot_a. Now you can either edit ~/.a and run chezmoi add .a again, or you can edit ~/dotfiles/dot_a and run chezmoi apply.
chezmoi does not automatically commit and push new files by default, so you will still need to git add/git commit/git push the files eventually.

Maybe I should ask on chezmoi page instead since it's not related to the Firefox template stuff.

You might get some better answers.


Two questions about the implementation

Thanks for your great job! I really appreciate the detailed experiments. However, I find some differences between the implementation and the paper:

As in https://github.com/klauscc/VindLU/issues/1, the MVM loss is not used. Does MVM really help?
In the original paper, Temporal Attention is inserted before spatial attention as in TimeSformer. But in the code, the temporal attention seems to be inserted after FFN. Is it better?
https://github.com/klauscc/VindLU/blob/30465487e8314fa1df45b1457b0313f25649e054/models/backbones/beit/st_beit.py#L744-L755

Since I'm not familiar with this area, another question is that, does the text encoder forward/backward twice for VTM/VTC and MLM loss?
I see that when calculating the MLM loss, the text encoder will take video embedding as keys/values, and forward/backward the text encoder again.
https://github.com/klauscc/VindLU/blob/30465487e8314fa1df45b1457b0313f25649e054/models/criterions.py#L228-L248
But in the code, the first 9 Attention Layer is Self-Attention, and the last 3 is Cross-Attention. If the model is reused, the dimension of video embedding should be the same as the text embedding. If not (e.g., BeiT-L for visual encoder), should we add another projection layer to downsample the video embedding?
Thanks for your help!

Thanks for your answer!


time.IsZero() is not suitable for use

Describe the bug
The time.IsZero() function checks to see if it matches January 1, 1, 00:00:00 UTC.
https://pkg.go.dev/time#Time.IsZero
The zero value in the queued is 0000-00-00 00:00:00.000000, so it is not judged correctly.
https://github.com/cybozu-go/moco-agent/blob/f414f81b0e024b8bb37c384d8e4e3476992d156d/server/mysqld_health.go#L94-L96
mysql> SELECT MAX(LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP) FROM performance_schema.replication_connection_status;
+--------------------------------------------------------+
| MAX(LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP) |
+--------------------------------------------------------+
| 0000-00-00 00:00:00.000000                             |
+--------------------------------------------------------+
1 row in set (0.00 sec)

mysql>

Expected behavior
Can correctly determine that 0000-00-00 00:00:00.000000 is a zero value.

As far as I tested, TIMESTAMP(6) value 0000-00-00 00:00:00.000000 is converted to time.Time value 0001-01-01 00:00:00 +0000 UTC. So the code you mentioned works as expected.
However, this behavior is not intuitive, though.


URL list for managment workstation

[Enter feedback here]
The document lists the following for The management machine where the Azure Portal is running must meet the following networking requirements:
Outbound internet access over port 443
if using a PAW device where the outbound access is restricted using a sinkhole proxy as in Microsoft example, this does not work, it appears we need to add *.Waconazure.com to the proxy exceptions as it uses domain arc.waconazure.com and not the *services.waconazure.com as listed for the hybrid server
It would be beneficial to include the domains required so PAW devices could be used to manage hybrid servers by WAC, currently in testing I have seen no other URL's required it would be good to know if this is going to change or I am missing something.
thanks
T

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: ea6a63ae-7b79-ebb4-375c-0e9702a1f2c4
Version Independent ID: ea6a63ae-7b79-ebb4-375c-0e9702a1f2c4
Content: Manage Azure Arc-enabled Servers using Windows Admin Center in Azure preview
Content Source: WindowsServerDocs/manage/windows-admin-center/azure/manage-arc-hybrid-machines.md
Service: windows-server
Sub-service: windows-admin-center
GitHub Login: @prasidharora
Microsoft Alias: praror

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


New linting rule - Description metadata

I'd like the linter to provide warnings where;
Parameters have been declared with no description metadata
This would help ensure quality of the bicep code that is produced. It doesn't obviously guarantee good quality descriptions, but as a linting warning it is a good prompt for bicep rookies.
As a natural extension, the other objects that support description metadata should also be able to have this linting rule specified.
Modules/Variables/Resources have been declared with no description metadata

When we have a public registry, we are going to require all params to have descriptions and we will check this (and other aspects of the module) with a module validation tool (#5580), which will be externally available as well. It makes sense to also make this available as a built-in linter rule (or set of rules), but I'm not sure it should be turned on by default if the code is not going to be made available as an external module.


Fix name of LocalCurrency scalar type

Fixes #5369
This is kind of a breaking change, so I've milestoned it as v13, but feel free to retarget it wherever.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@benmccallum  cool thanks for the pr! :)
Regarding your comment in #5369:
Do you want to fix this behaviour?
https://github.com/ChilliCream/hotchocolate/blob/b8e3bd10f9c6a8247c602f8c52f0e14dadc3e361/src/HotChocolate/Core/src/Types.Scalars/LocalCurrencyType.cs#L38
Description = description ?? ScalarResources.LocalCurrencyType_Description;

@PascalSenn we drop the description deliberately. When you change the name of a scalar you often do so to change semantics.
Think about the string scalar where you now give it a meaning like EmployeeName .... now this scalar does no longer have the semantical meaning it had before and needs a new description.


SAS URLs for disk images

looks great :+1: just the minor issue with the man page docs I mentioned


add instructions to readme for running dev environment

Quick PR that adds dev environment instructions.

Merging with admin privilege.


Swap StakingPower and VotingPower, and modify from StakingPower to VotingWeight

Description
Keeping tendermint's interface(abci, rpc, etc.) swap StakingPower and VotingPower.
And modify from StakingPower to VotingWeight
Here is the summary of the usage:

Tendermint
Ostracon (Before)
Ostracon (After)

Proposer
One of ValidatorSet
One of ValidatorSet
One of ValidatorSet

Select a Proposer by
Validator.ProposerPriority
Validator.StakingPower
Validator.VotingPower

Voters
ValidatorSet
VoterSet (Part of ValidatorSet)
VoterSet (Part of ValidatorSet)

Select VoterSet by
-
Validator.StakingPower
Validator.VotingPower

Voting
Validator.VotingPower
Validator.VotingPower
Validator.StakingPower => Validator.VotingWeight

DuplicateVoteEvidence TotalVotingPower
ValidatorSet.TotalVotingPower
VoterSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

DuplicateVoteEvidence ValidatorPower
Validator.VotingPower
Validator.StakingPower
Validator.VotingPower

DuplicateVoteEvidence added Power
-
Validator.VotingPower
Validator.StakingPower => Validator.VotingWeight

LightClientAttackEvidence TotalVotingPower
ValidatorSet.TotalVotingPower
VoterSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

ValidatorSet TotalXxxPower
ValidatorSet.TotalVotingPower
VoterSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

Validator VotingPower
Validator.VotingPower
Validator.StakingPower
Validator.VotingPower

Validator added Power
-
Validator.VotingPower
Validator.StakingPower => Validator.VotingWeight

VoterSet TotalXxxPower
-
VoterSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

Proto Type DuplicateVoteEvidence TotalVotingPower
ValidatorSet.TotalVotingPower
VoterSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

Proto Type DuplicateVoteEvidence Power
Validator.VotingPower
Validator.StakingPower
Validator.VotingPower

Proto Type DuplicateVoteEvidence added Power
-
Validator.VotingPower
Validator.StakingPower => Validator.VotingWeight

Proto Type LightClientAttackEvidence TotalVotingPower
ValidatorSet.TotalVotingPower
VoterSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

Proto Type ValidatorSet TotalXxxPower
ValidatorSet.TotalVotingPower
VoterSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

Proto Type Validator Power
Validator.VotingPower
Validator.StakingPower
Validator.VotingPower

Proto Type Validator added Power
-
Validator.VotingPower
Validator.StakingPower => Validator.VotingWeight

Proto Type SimpleValidator Power
Validator.VotingPower
Validator.StakingPower
Validator.VotingPower

Proto Type VoterSet TotalXxxPower
-
VoterSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

Proto ABCI Validator Power
Validator.VotingPower
Validator.StakingPower
Validator.VotingPower

Proto ABCI Validator added Power
-
Validator.VotingPower
Validator.StakingPower => Validator.VotingWeight

Proto ABCI ValidatorUpdate Power
Validator.VotingPower
Validator.StakingPower
Validator.VotingPower

Proto ABCI Evidence TotalVotingPower
ValidatorSet.TotalVotingPower
VoteSet.TotalVotingPower
VoterSet.TotalStakingPower => VoterSet.TotalVotingWeight

RPC ValidatorInfo VotingPower
RPC ValidatorInfo VotingPower == Validator.VotingPower
RPC ValidatorInfo StakingPower == Validator.StakingPower
RPC ValidatorInfo VotingPower == Validator.VotingPower

Tendermint.Validator.VotingPower  ==

Ostracon(Before).Validator.StakingPower == Ostracon(After).Validator.VotingPower

Tendermint.Validator.VotingPower  !=

Ostracon(Before).Validator.VotingPower == Ostracon(After).Validator.StakingPower == Caluculated power value

Tendermint.Evidence.TotalVotingPower  ==  Tendermint.ValidatorSet.TotalVotingPower !=

Ostracon(Before).VoterSet.TotalVotingPower == Ostracon(After).VoterSet.TotalStakingPower  == Caluculated power value

Relates:

https://github.com/line/ostracon/pull/83
https://github.com/line/ostracon/pull/102
https://github.com/line/ostracon/pull/108
https://github.com/line/ostracon/pull/110
https://github.com/line/ostracon/pull/124
https://github.com/line/ostracon/pull/129
https://github.com/line/ostracon/pull/194
https://github.com/line/ostracon/pull/312
https://github.com/line/lbm-sdk/pull/317

I'd like to change the name of Validator.StakingPower since it's a bad name.

I'd like to change the name of Validator.StakingPower since it's a bad name.

I decide to use VotingWeight instead of StakingPower

VotingPower: Voting power based on deposited tokens of validator.
VotingWeight: Randomly allocated voting power when elected by VoterSet.

@tnasu, Is it right?

@zemyblue Right.

Randomly allocated voting power when elected by VoterSet.

To explain it a little more carefully, the randomly selected Validator is the VoterSet from ValidatorSet, and when it is selected, the VotingWeight is calculated at the selection by using the VotingPower that the Validator has and the winning-point as a coefficient.


tests: re-asses the use of a local registry server to build and install the operator

The operator developers guide says it is required an account on a registry server in order to build the operator. See https://github.com/confidential-containers/operator/blob/main/docs/DEVELOPMENT.md#prerequisites
On CI, dealing with an external registry is unwanted as this can be error prone and subject to security management. Thus, we do:

Start on localhost a registry server where the a built image is pushed/pulled to  (https://github.com/confidential-containers/operator/blob/main/tests/e2e/operator.sh#L84)
export IMG=localhost:5000/cc-operator

However that approach makes the bootstrap of the test environment a little bit more complicated. I'm opening this issue to investigate if there is a better solution, more precisely, check if we can build and install the operator without the necessity of a registry server.

One option is to use a Kind based K8s cluster for operator testing. Kind allows local loading of container images without requiring any external registry.
Ref: https://kind.sigs.k8s.io/docs/user/quick-start/#loading-an-image-into-your-cluster
I use this for local development and testing.
However there is a caveat. Currently CoCo + Kind works only with cloud-hypervisor (both TEE and non-TEE) and not with Qemu. Fixing it will make spinning up test environments very easy.
CoCo + Kind test reference: https://docs.google.com/document/d/1im_LXuI_NHp_xnQ2S38zTjDWOkIDdPEQ0OTWaYbLJ7E/edit

@wainersm you can use a similar approach like cloud-api-adaptor and as described above

local operator install w/ kind is already covered:
https://github.com/confidential-containers/operator/blob/cf6a4f38114f7c5b71daec6cb666b1b40bcea140/.github/workflows/e2e.yaml#L27:L45


Refactoring

TODOS
Render by returning {ast, context} instead of Context.value

maybe even w/o context ever changingn by extracting what is needed, that would be (out of memory, needs some checking)
{ast, referenced_footnotes_set, messages, context}
and only at the very end we will update  context with messages.


How to have events with different color indicator on calendar?

Im looking at DelegateApparenceExample but can't find the code related

https://github.com/WenchaoD/FSCalendar/blob/master/FSCalendar/FSCalendar.h#L186


Compiler warnings

Add compiler warnings and fix all warnings accordingly to the compiler output.
This can be done easily like this:
bezier_library/CMakeLists.txt

add_library (bezier_library_obj OBJECT src/bezier_library.cpp)
set_property(TARGET bezier_library_obj APPEND_STRING PROPERTY COMPILE_FLAGS -Wall)
add_library (${PROJECT_NAME} $<TARGET_OBJECTS:bezier_library_obj>)

Do the same for the bezier_application package!

Fixed via #24


Get Model and Data Sizes

Hi,
I'm a student and I'm trying to use MuJoCo for robotics simulation. When looking for ways to get the total size allocated by mujoco when we load an xml file, I came across the mj_sizeModel() function that returns the size of model. Is there a similar way to return the total size of mjData?
My intention is to know how much cache memory we have for allocation of data intended for storing the states of the robot at each timestep...

Contex:
For large and small models, I get:
std::cout<< "model: "<< mj_sizeModel(m) << "\n";
std::cout<< "data: "<< sizeof(*d) << std::endl; // Is this the correct way for measuring size of data?

model: 12099 // Small Model
data: 41288

model: 46694613 // Large Model
data: 41288

Is the data supposed to be same across all models?

PS: ...and if anyone has suggestions for laying out buffers per thread in memory, followed by concatenation of chunks of per thread memmory back to main memory.

Are you looking for the total memory footprint occupied by mjData? If so then it's sizeof(*d) for the mjData itself, plus d->nbuffer for the amount of memory allocated for d->buffer, plus d->nstack * sizeof(mjtNum) for the amount of memory allocated for d->arena.

Thank you for the reply.
Yes, I was looking for the Total size of mjData(+buffer+arena) .
I was wondering, why do both the small and the large models have the same mjData size?

I presume you mean to ask why sizeof(mjData)+buffer+arena is the same, since sizeof(mjData) is constant for obvious reasons.
The answer is that MuJoCo allocates mjData very generously, by default (about 13MB, IIRC). You can see how much of this memory is actually used by loading your model in simulate and looking at the info panel (F2). In order to decrease or increase the allocation, use <size memory>, as documented here and here.

Thanks this is just what I was looking for!


🐛 Sway session start is no reliable

branch
stable
Architecture
x86_64
Description
Logging into a session is quite instable since I had to switch to sway user service session after upgrading to manjaro-sway-settings 16.18.0 from 16.15.x (I didn't even notice it until today in greetd).
The "old" sway session starts without any issues, but there is no waybar and some hotkeys (e.g. ctrl-enter) do not work. I assume that this is related to the new systemd services introduced by the update.
It takes some attempts to login and I see systemd service errors in the logs:
Mär 15 15:56:47 galileo systemd[90170]: Reloading finished in 79 ms.
Mär 15 15:56:47 galileo systemd[90170]: Current sway user session is inactive.
Mär 15 15:56:47 galileo systemd[90170]: Dependency failed for Automatically mounts removable media.
Mär 15 15:56:47 galileo systemd[90170]: pcmanfm.service: Job pcmanfm.service/start failed with result 'dependency'.
Mär 15 15:56:47 galileo systemd[90170]: Dependency failed for Auto Manages Your Wayland Displays.
Mär 15 15:56:47 galileo systemd[90170]: way-displays.service: Job way-displays.service/start failed with result 'dependency'.
Mär 15 15:56:47 galileo systemd[90170]: Dependency failed for Renames workspaces to the icons configured.
Mär 15 15:56:47 galileo systemd[90170]: sworkstyle.service: Job sworkstyle.service/start failed with result 'dependency'.
Mär 15 15:56:47 galileo systemd[90170]: Dependency failed for Highly customizable Wayland bar for Sway and Wlroots based compositors..
Mär 15 15:56:47 galileo systemd[90170]: waybar.service: Job waybar.service/start failed with result 'dependency'.
Mär 15 15:56:47 galileo systemd[90170]: Listening on foot-server.socket.
Mär 15 15:56:47 galileo systemd[90170]: Started Window switcher for Sway.
Mär 15 15:56:47 galileo systemd[90170]: Reloading requested from client PID 104097 ('systemctl')...
Mär 15 15:56:47 galileo systemd[90170]: Reloading...
Mär 15 15:56:47 galileo systemd[90170]: Reloading finished in 75 ms.
Mär 15 15:56:48 galileo systemd[90170]: Current sway user session is inactive.
Mär 15 15:56:48 galileo systemd[90170]: Dependency failed for Foot terminal server mode.
Mär 15 15:56:48 galileo systemd[90170]: foot-server.service: Job foot-server.service/start failed with result 'dependency'.
Mär 15 15:57:06 galileo systemd[90170]: Reloading requested from client PID 104424 ('systemctl')...
Mär 15 15:57:06 galileo systemd[90170]: Reloading...
Mär 15 15:57:06 galileo systemd[90170]: Reloading finished in 80 ms.
Mär 15 15:57:06 galileo systemd[90170]: Reloading requested from client PID 104477 ('systemctl')...
Mär 15 15:57:06 galileo systemd[90170]: Reloading...
Mär 15 15:57:06 galileo systemd[90170]: Reloading finished in 79 ms.
Mär 15 15:57:06 galileo systemd[90170]: Current sway user session is inactive.
Mär 15 15:57:06 galileo systemd[90170]: Dependency failed for Renames workspaces to the icons configured.
Mär 15 15:57:06 galileo systemd[90170]: sworkstyle.service: Job sworkstyle.service/start failed with result 'dependency'.
Mär 15 15:57:06 galileo systemd[90170]: Dependency failed for Auto Manages Your Wayland Displays.
Mär 15 15:57:06 galileo systemd[90170]: way-displays.service: Job way-displays.service/start failed with result 'dependency'.
Mär 15 16:00:14 galileo swayrd[104336]: [2024-03-15T15:00:14Z WARN  swayr::daemon] Error while receiving events: failed to fill whole buffer
Mär 15 16:00:17 galileo swayrd[104336]: [2024-03-15T15:00:17Z WARN  swayr::daemon] Resetting!
Mär 15 16:00:17 galileo swayrd[104336]: [2024-03-15T15:00:17Z WARN  swayr::daemon] Error while receiving events: failed to fill whole buffer
Mär 15 16:00:20 galileo swayrd[104336]: [2024-03-15T15:00:20Z WARN  swayr::daemon] Resetting!
Mär 15 16:00:20 galileo swayrd[104336]: [2024-03-15T15:00:20Z WARN  swayr::daemon] Error while receiving events: failed to fill whole buffer
Mär 15 16:00:23 galileo swayrd[104336]: [2024-03-15T15:00:23Z WARN  swayr::daemon] Resetting!
Mär 15 16:00:23 galileo swayrd[104336]: [2024-03-15T15:00:23Z WARN  swayr::daemon] Error while receiving events: failed to fill whole buffer
Mär 15 16:00:24 galileo systemd[90170]: Reached target Session services which should run early before the graphical session is brought up.
Mär 15 16:00:24 galileo systemd[90170]: Reached target Session services which should run early before the sway session is brought up.
Mär 15 16:00:24 galileo systemd[90170]: Reached target Session services which should run early before the wayland session is brought up.
Mär 15 16:00:24 galileo systemd[90170]: Starting sway - SirCmpwn's Wayland window manager...
Mär 15 16:00:24 galileo sway[105389]: 00:00:00.002 [ERROR] [wlr] [backend/wayland/backend.c:592] Could not connect to remote display: No such file or directory
Mär 15 16:00:24 galileo sway[105389]: 00:00:00.002 [ERROR] [sway/server.c:137] Unable to create backend
Mär 15 16:00:24 galileo systemd[90170]: sway.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: sway.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo systemd[90170]: Failed to start sway - SirCmpwn's Wayland window manager.
Mär 15 16:00:24 galileo systemd[90170]: Reached target Current sway user session.
Mär 15 16:00:24 galileo systemd[90170]: Reached target Current wayland user session.
Mär 15 16:00:24 galileo systemd[90170]: Foot terminal server mode was skipped because of an unmet condition check (ConditionEnvironment=WAYLAND_DISPLAY).
Mär 15 16:00:24 galileo systemd[90170]: Started Automatically mounts removable media.
Mär 15 16:00:24 galileo systemd[90170]: Started Renames workspaces to the icons configured.
Mär 15 16:00:24 galileo systemd[90170]: Started Auto Manages Your Wayland Displays.
Mär 15 16:00:24 galileo systemd[90170]: Started Highly customizable Wayland bar for Sway and Wlroots based compositors..
Mär 15 16:00:24 galileo sworkstyle[105395]: 2024-03-15T15:00:24.304Z WARN  [sworkstyle::config] No fallback set using default: <U+F24D>
Mär 15 16:00:24 galileo way-displays[105396]: ERROR: environment variable $WAYLAND_DISPLAY missing
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo pcmanfm[105394]: Anzeige kann nicht geöffnet werden:
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo waybar[105426]: cannot open display:
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo sworkstyle[105424]: 00:00:00.048 [ERROR] [wlr] [libseat] [libseat/backend/logind.c:317] Could not activate session: Unknown object '/org/freedesktop>
Mär 15 16:00:24 galileo sworkstyle[105424]: 00:00:00.048 [ERROR] [wlr] [libseat] [libseat/libseat.c:58] Backend 'logind' failed to open seat: Invalid request descriptor
Mär 15 16:00:24 galileo sworkstyle[105424]: 00:00:00.048 [ERROR] [wlr] [backend/session/session.c:83] Unable to create seat: Invalid request descriptor
Mär 15 16:00:24 galileo sworkstyle[105424]: 00:00:00.048 [ERROR] [wlr] [backend/session/session.c:248] Failed to load session backend
Mär 15 16:00:24 galileo sworkstyle[105424]: 00:00:00.048 [ERROR] [wlr] [backend/backend.c:79] Failed to start a session
Mär 15 16:00:24 galileo sworkstyle[105424]: 00:00:00.048 [ERROR] [wlr] [backend/backend.c:359] Failed to start a DRM session
Mär 15 16:00:24 galileo sworkstyle[105424]: 00:00:00.048 [ERROR] [sway/server.c:137] Unable to create backend
Mär 15 16:00:24 galileo sworkstyle[105395]: 2024-03-15T15:00:24.366Z ERROR [sworkstyle] Invalid argument (os error 22)
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Scheduled restart job, restart counter is at 1.
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Scheduled restart job, restart counter is at 1.
Mär 15 16:00:24 galileo systemd[90170]: Started Automatically mounts removable media.
Mär 15 16:00:24 galileo pipewire-media-session[90662]: spa.alsa: can't open control for card hw:4: No such file or directory
Mär 15 16:00:24 galileo systemd[90170]: Started Auto Manages Your Wayland Displays.
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Scheduled restart job, restart counter is at 1.
Mär 15 16:00:24 galileo systemd[90170]: Started Highly customizable Wayland bar for Sway and Wlroots based compositors..
Mär 15 16:00:24 galileo (displays)[105433]: way-displays.service: Referenced but unset environment variable evaluates to an empty string: XDG_VTNR
Mär 15 16:00:24 galileo pipewire-media-session[90662]: spa.alsa: Card can't get card_name from card_index 1
Mär 15 16:00:24 galileo way-displays[105433]: ERROR: environment variable $WAYLAND_DISPLAY missing
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo pipewire-media-session[90662]: spa.alsa: can't open control for card hw:1: No such file or directory
Mär 15 16:00:24 galileo pipewire-media-session[90662]: spa.alsa: Card can't get card_name from card_index 3
Mär 15 16:00:24 galileo pipewire-media-session[90662]: spa.alsa: can't open control for card hw:3: No such file or directory
Mär 15 16:00:24 galileo pipewire-media-session[90662]: spa.alsa: Card can't get card_name from card_index 5
Mär 15 16:00:24 galileo pcmanfm[105432]: Anzeige kann nicht geöffnet werden:
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo pipewire-media-session[90662]: spa.alsa: can't open control for card hw:5: No such file or directory
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo waybar[105438]: cannot open display:
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Scheduled restart job, restart counter is at 2.
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Scheduled restart job, restart counter is at 2.
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Scheduled restart job, restart counter is at 2.
Mär 15 16:00:24 galileo systemd[90170]: Started Automatically mounts removable media.
Mär 15 16:00:24 galileo systemd[90170]: Started Auto Manages Your Wayland Displays.
Mär 15 16:00:24 galileo systemd[90170]: Started Highly customizable Wayland bar for Sway and Wlroots based compositors..
Mär 15 16:00:24 galileo (displays)[105443]: way-displays.service: Referenced but unset environment variable evaluates to an empty string: XDG_VTNR
Mär 15 16:00:24 galileo way-displays[105443]: ERROR: environment variable $WAYLAND_DISPLAY missing
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo pcmanfm[105442]: Anzeige kann nicht geöffnet werden:
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo waybar[105448]: cannot open display:
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Scheduled restart job, restart counter is at 3.
Mär 15 16:00:24 galileo systemd[90170]: waybar.service: Scheduled restart job, restart counter is at 3.
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Scheduled restart job, restart counter is at 3.
Mär 15 16:00:24 galileo systemd[90170]: Started Automatically mounts removable media.
Mär 15 16:00:24 galileo systemd[90170]: Started Auto Manages Your Wayland Displays.
Mär 15 16:00:24 galileo systemd[90170]: Started Highly customizable Wayland bar for Sway and Wlroots based compositors..
Mär 15 16:00:24 galileo (displays)[105453]: way-displays.service: Referenced but unset environment variable evaluates to an empty string: XDG_VTNR
Mär 15 16:00:24 galileo way-displays[105453]: ERROR: environment variable $WAYLAND_DISPLAY missing
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: way-displays.service: Failed with result 'exit-code'.
Mär 15 16:00:24 galileo pcmanfm[105452]: Anzeige kann nicht geöffnet werden:
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:24 galileo systemd[90170]: pcmanfm.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo waybar[105458]: cannot open display:
Mär 15 16:00:25 galileo systemd[90170]: waybar.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:25 galileo systemd[90170]: waybar.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo systemd[90170]: way-displays.service: Scheduled restart job, restart counter is at 4.
Mär 15 16:00:25 galileo systemd[90170]: waybar.service: Scheduled restart job, restart counter is at 4.
Mär 15 16:00:25 galileo systemd[90170]: pcmanfm.service: Scheduled restart job, restart counter is at 4.
Mär 15 16:00:25 galileo systemd[90170]: Started Automatically mounts removable media.
Mär 15 16:00:25 galileo systemd[90170]: Started Auto Manages Your Wayland Displays.
Mär 15 16:00:25 galileo systemd[90170]: Started Highly customizable Wayland bar for Sway and Wlroots based compositors..
Mär 15 16:00:25 galileo (displays)[105463]: way-displays.service: Referenced but unset environment variable evaluates to an empty string: XDG_VTNR
Mär 15 16:00:25 galileo way-displays[105463]: ERROR: environment variable $WAYLAND_DISPLAY missing
Mär 15 16:00:25 galileo systemd[90170]: way-displays.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:25 galileo systemd[90170]: way-displays.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo pcmanfm[105462]: Anzeige kann nicht geöffnet werden:
Mär 15 16:00:25 galileo systemd[90170]: pcmanfm.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:25 galileo systemd[90170]: pcmanfm.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo waybar[105468]: cannot open display:
Mär 15 16:00:25 galileo systemd[90170]: waybar.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:25 galileo systemd[90170]: waybar.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo systemd[90170]: sway.service: Scheduled restart job, restart counter is at 1.
Mär 15 16:00:25 galileo systemd[90170]: waybar.service: Scheduled restart job, restart counter is at 5.
Mär 15 16:00:25 galileo systemd[90170]: pcmanfm.service: Scheduled restart job, restart counter is at 5.
Mär 15 16:00:25 galileo systemd[90170]: way-displays.service: Scheduled restart job, restart counter is at 5.
Mär 15 16:00:25 galileo systemd[90170]: pcmanfm.service: Start request repeated too quickly.
Mär 15 16:00:25 galileo systemd[90170]: pcmanfm.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo systemd[90170]: Failed to start Automatically mounts removable media.
Mär 15 16:00:25 galileo systemd[90170]: Starting sway - SirCmpwn's Wayland window manager...
Mär 15 16:00:25 galileo systemd[90170]: way-displays.service: Start request repeated too quickly.
Mär 15 16:00:25 galileo systemd[90170]: way-displays.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo systemd[90170]: Failed to start Auto Manages Your Wayland Displays.
Mär 15 16:00:25 galileo systemd[90170]: waybar.service: Start request repeated too quickly.
Mär 15 16:00:25 galileo systemd[90170]: waybar.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo systemd[90170]: Failed to start Highly customizable Wayland bar for Sway and Wlroots based compositors..
Mär 15 16:00:25 galileo sway[105504]: 00:00:00.002 [ERROR] [wlr] [libseat] [libseat/libseat.c:58] Backend 'logind' failed to open seat: No such device or address
Mär 15 16:00:25 galileo sway[105504]: 00:00:00.002 [ERROR] [wlr] [backend/session/session.c:83] Unable to create seat: No such device or address
Mär 15 16:00:25 galileo sway[105504]: 00:00:00.002 [ERROR] [wlr] [backend/session/session.c:248] Failed to load session backend
Mär 15 16:00:25 galileo sway[105504]: 00:00:00.002 [ERROR] [wlr] [backend/backend.c:79] Failed to start a session
Mär 15 16:00:25 galileo sway[105504]: 00:00:00.002 [ERROR] [wlr] [backend/backend.c:359] Failed to start a DRM session
Mär 15 16:00:25 galileo sway[105504]: 00:00:00.002 [ERROR] [sway/server.c:137] Unable to create backend
Mär 15 16:00:25 galileo systemd[90170]: sway.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:25 galileo systemd[90170]: sway.service: Failed with result 'exit-code'.
Mär 15 16:00:25 galileo systemd[90170]: Failed to start sway - SirCmpwn's Wayland window manager.
Mär 15 16:00:26 galileo swayrd[104336]: [2024-03-15T15:00:26Z WARN  swayr::daemon] Resetting!
Mär 15 16:00:26 galileo swayrd[104336]: [2024-03-15T15:00:26Z WARN  swayr::daemon] Error while receiving events: failed to fill whole buffer
Mär 15 16:00:26 galileo systemd[90170]: sway.service: Scheduled restart job, restart counter is at 2.
Mär 15 16:00:26 galileo systemd[90170]: Starting sway - SirCmpwn's Wayland window manager...
Mär 15 16:00:26 galileo sway[105517]: 00:00:00.002 [ERROR] [wlr] [libseat] [libseat/libseat.c:58] Backend 'logind' failed to open seat: No such device or address
Mär 15 16:00:26 galileo sway[105517]: 00:00:00.002 [ERROR] [wlr] [backend/session/session.c:83] Unable to create seat: No such device or address
Mär 15 16:00:26 galileo sway[105517]: 00:00:00.002 [ERROR] [wlr] [backend/session/session.c:248] Failed to load session backend
Mär 15 16:00:26 galileo sway[105517]: 00:00:00.002 [ERROR] [wlr] [backend/backend.c:79] Failed to start a session
Mär 15 16:00:26 galileo sway[105517]: 00:00:00.002 [ERROR] [wlr] [backend/backend.c:359] Failed to start a DRM session
Mär 15 16:00:26 galileo sway[105517]: 00:00:00.002 [ERROR] [sway/server.c:137] Unable to create backend
Mär 15 16:00:26 galileo systemd[90170]: sway.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:26 galileo systemd[90170]: sway.service: Failed with result 'exit-code'.
Mär 15 16:00:26 galileo systemd[90170]: Failed to start sway - SirCmpwn's Wayland window manager.
Mär 15 16:00:27 galileo systemd[90170]: sway.service: Scheduled restart job, restart counter is at 3.
Mär 15 16:00:27 galileo systemd[90170]: Starting sway - SirCmpwn's Wayland window manager...
Mär 15 16:00:27 galileo sway[105535]: 00:00:00.002 [ERROR] [wlr] [libseat] [libseat/libseat.c:58] Backend 'logind' failed to open seat: No such device or address
Mär 15 16:00:27 galileo sway[105535]: 00:00:00.002 [ERROR] [wlr] [backend/session/session.c:83] Unable to create seat: No such device or address
Mär 15 16:00:27 galileo sway[105535]: 00:00:00.002 [ERROR] [wlr] [backend/session/session.c:248] Failed to load session backend
Mär 15 16:00:27 galileo sway[105535]: 00:00:00.003 [ERROR] [wlr] [backend/backend.c:79] Failed to start a session
Mär 15 16:00:27 galileo sway[105535]: 00:00:00.003 [ERROR] [wlr] [backend/backend.c:359] Failed to start a DRM session
Mär 15 16:00:27 galileo sway[105535]: 00:00:00.003 [ERROR] [sway/server.c:137] Unable to create backend
Mär 15 16:00:27 galileo systemd[90170]: sway.service: Main process exited, code=exited, status=1/FAILURE
Mär 15 16:00:27 galileo systemd[90170]: sway.service: Failed with result 'exit-code'.
Mär 15 16:00:27 galileo systemd[90170]: Failed to start sway - SirCmpwn's Wayland window manager.
Mär 15 16:00:29 galileo swayrd[104336]: [2024-03-15T15:00:29Z WARN  swayr::daemon] Resetting!
Mär 15 16:00:29 galileo swayrd[104336]: [2024-03-15T15:00:29Z WARN  swayr::daemon] Error while receiving events: failed to fill whole buffer
Mär 15 16:00:29 galileo systemd[90170]: sway.service: Scheduled restart job, restart counter is at 4.
Mär 15 16:00:29 galileo systemd[90170]: sway.service: Start request repeated too quickly.
Mär 15 16:00:29 galileo systemd[90170]: sway.service: Failed with result 'exit-code'.
Mär 15 16:00:29 galileo systemd[90170]: Failed to start sway - SirCmpwn's Wayland window manager.
Mär 15 16:00:29 galileo systemd[90170]: Stopping Window switcher for Sway...
Mär 15 16:00:29 galileo systemd[90170]: Stopped Window switcher for Sway.
Mär 15 16:00:29 galileo systemd[90170]: Stopped target Current sway user session.
Mär 15 16:00:29 galileo systemd[90170]: Stopped target Session services which should run early before the sway session is brought up.
Mär 15 16:00:29 galileo systemd[90170]: Stopped target Current wayland user session.
Mär 15 16:00:29 galileo systemd[90170]: Stopped target Session services which should run early before the wayland session is brought up.
Mär 15 16:00:29 galileo systemd[90170]: Stopped target Session services which should run early before the graphical session is brought up.
Mär 15 16:00:47 galileo pipewire-media-session[90662]: spa.alsa: Path Mic ACP LED is not a volume or mute control
Mär 15 16:02:58 galileo systemd[90170]: Reached target Session services which should run early before the graphical session is brought up.
Mär 15 16:02:58 galileo systemd[90170]: Reached target Session services which should run early before the sway session is brought up.
Mär 15 16:02:58 galileo systemd[90170]: Reached target Session services which should run early before the wayland session is brought up.
Mär 15 16:02:58 galileo systemd[90170]: Starting sway - SirCmpwn's Wayland window manager...
Mär 15 16:02:59 galileo systemctl[106930]: Environment variable $XCURSOR_THEME not set, ignoring.
Mär 15 16:02:59 galileo systemd[90170]: Started sway - SirCmpwn's Wayland window manager.
Mär 15 16:02:59 galileo systemd[90170]: Reached target Current sway user session.
Mär 15 16:02:59 galileo systemd[90170]: Reached target Current wayland user session.

Is the following user service configuration expected
[Dec  1 22:45]  .
├── [Dec 11 09:42]  default.target.wants
│   ├── [Nov 29 00:03]  appimagelauncherd.service -> /usr/lib/systemd/user/appimagelauncherd.service
│   └── [Dec 11 09:42]  idlehack.service -> /usr/lib/systemd/user/idlehack.service
├── [Jan  9 10:38]  graphical-session.target.wants
│   ├── [Dec  1 22:45]  foot-server.service -> /usr/lib/systemd/user/foot-server.service
│   ├── [Dec  1 22:45]  foot-server.socket -> /usr/lib/systemd/user/foot-server.socket
│   └── [Dec  1 22:45]  poweralertd.service -> /usr/lib/systemd/user/poweralertd.service
├── [Nov 28 23:54]  sockets.target.wants
│   └── [Nov 28 23:54]  gcr-ssh-agent.socket -> /usr/lib/systemd/user/gcr-ssh-agent.socket
└── [Mar 15 10:15]  sway-session.target.wants
    ├── [Mar 15 10:15]  foot-server.service -> /etc/xdg/systemd/user/foot-server.service
    ├── [Mar 15 10:15]  pcmanfm.service -> /etc/xdg/systemd/user/pcmanfm.service
    ├── [Dec  1 22:45]  swayrd.service -> /usr/lib/systemd/user/swayrd.service
    ├── [Mar 15 10:15]  sworkstyle.service -> /etc/xdg/systemd/user/sworkstyle.service
    ├── [Feb 20 00:44]  waybar.service -> /etc/xdg/systemd/user/waybar.service
    └── [Mar 15 10:15]  way-displays.service -> /etc/xdg/systemd/user/way-displays.service

Reproduction steps
Try to login from greetd into sway user service.

Screenshots
No response
Logs
No response

Maybe the dependencies could be tuned to be much more efficient. Will have a look later...

I am experiencing the same behaviour after upgrading to 16.19.0: it takes several attempts to log into the sway service session, and way-displays does not start after logging in.

way-displays does not start after logging in.

I think way-displays never started earlier. From their docs:

Start the way-displays server by running once with no arguments after your wayland compositor has been started.

The "old" sway session starts without any issues

manjaro-sway-settings-git should now start the waybar in the session again.

manjaro-sway-settings-git should now start the waybar in the regular session again.

Not for me :/ I'm also experiencing random freezes with sway user service which is why I went back to starting the sway session via sway in the first place. What logs would be the most useful to debug this?

The "old" sway session starts without any issues

manjaro-sway-settings-git should now start the waybar in the regular session again.

No effect for me.
I see this issue is very similar from the Forum: https://github.com/manjaro-sway/manjaro-sway/issues/733#issuecomment-2001921041
Hope to get it fixed. Now I am living without swaybar so-to-say.

You referenced this very same issue. But I think I know that issue you reference too.

You referenced this very same issue. But I think I know that issue you wanted to reference to.

Sorry. I did a wrong copy-paste. Now the forum link is update: https://forum.manjaro.org/t/waybar-fails-to-load-after-system-update/157276

After updating upgraded manjaro-sway-settings (16.19.1-7 -> 16.19.2-7)
the issue is gone.
Thanks.

Nice! I wasn't sure, as it never has been a real problem on my machines. Happy it worked!

After updating upgraded manjaro-sway-settings (16.19.1-7 -> 16.19.2-7) the issue is gone. Thanks.

Are you using the service-session or the regular one?

After updating upgraded manjaro-sway-settings (16.19.1-7 -> 16.19.2-7) the issue is gone. Thanks.

Are you using the service-session or the regular one?

How to check it? I just updated and rebooted.

I'm not sure if it's related to the changes or just co-incidence, but since that Friday update my sway session crashed already three times after several hours of working - there was no sway core dump before last Friday since I installed it.
This happening with the service session; I'll check the regular one now with 16.19.2 settings.


Testing only *-test.js files

It is possible create a config for the jest test only *-test.js files? Current, it test all files inside test folder include the factories. My fear is that when many files are created the test becomes very slow.
PASS  app/bundles/Supernova/test/components/Table/Cell/Data/Main-test.js (4.812s)
PASS  app/bundles/Supernova/test/components/Table/Body-test.js (4.82s)
PASS  app/bundles/Supernova/test/components/HelloWorld-test.js (4.913s)
PASS  app/bundles/Supernova/test/components/Table/Cell/Head-test.js (0.155s)
PASS  app/bundles/Supernova/test/components/Table/Cell/Data/Title-test.js (0.251s)
PASS  app/bundles/Supernova/test/components/Table/Head-test.js (0.205s)
PASS  app/bundles/Supernova/test/components/Table/Main-test.js (0.07s)
PASS  app/bundles/Supernova/test/components/Table/Row-test.js (0.067s)
PASS  app/bundles/Supernova/test/factories/components/base-factory.js (0.052s)
PASS  app/bundles/Supernova/test/factories/components/table-factory.js (0.053s)

Yes, see the testRegex config option.

I test this in my package.json
"jest": {
"testDirectoryName": "tests",
"testRegex": "*-test.js$",
but not work..

Because that's not a valid regex. Try (.*)-test.js$

@cpojer the -factory.js file are called yet :/
PASS  app/bundles/Supernova/tests/components/Table/Body-test.js (4.868s)
PASS  app/bundles/Supernova/tests/components/Table/Cell/Data/Main-test.js (4.88s)
PASS  app/bundles/Supernova/tests/components/HelloWorld-test.js (4.981s)
PASS  app/bundles/Supernova/tests/components/Table/Cell/Data/Title-test.js (0.224s)
PASS  app/bundles/Supernova/tests/components/Table/Cell/Head-test.js (0.268s)
PASS  app/bundles/Supernova/tests/components/Table/Head-test.js (0.232s)
PASS  app/bundles/Supernova/tests/factories/components/base-factory.js (0.057s)
PASS  app/bundles/Supernova/tests/components/Table/Main-test.js (0.113s)
PASS  app/bundles/Supernova/tests/components/Table/Row-test.js (0.118s)
PASS  app/bundles/Supernova/tests/factories/components/table-factory.js (0.037s)

you should specify testDirectoryName when you are using testRegex.

@cpojer thanks. It works!


Update test.ring

Thanks Gal
It would be better to set initial values for the variables a1 and a2 and avoid using the give command so the test can work more quickly (or without the need of input redirection).


fix flutter packages

ivi-homescreen is the suggested embedder variant as long as the AGL compositor is not used.
package groups in meta-flutter have been renamed.

Unfortunately this is broken again. I'll create a feature request for a stable recipe name that can be used here.

Updated with meta-flutter maintainer's suggestion.


Test drag & drop in integration test

Coverage remained the same at 26.384% when pulling acfcde0fea5ee8c543a2ec92201b6ffb904e2e36 on ci-test-drag-drop into 83672c72c51880b66e43a45ba745d2d05416506b on master.


Ravedude can't resolve port on MS Windows 10

I have an arduino uno connected to port COM3 and ravedude can't find it, I tried setting the RAVEDUDE_PORT environnement variable to COM3 but still don't work. The arduino IDE can find it and I'm  running windows 10. I tried all USB ports and manually changed the port from device manager.
Error:
PS C:\Users\Baptiste\Documents\code\Rust\arduino\tests> cargo run
    Finished dev [optimized + debuginfo] target(s) in 0.16s
     Running `ravedude uno -cb 57600 target\avr-atmega328p\debug\tests.elf`
       Board Arduino Uno
Error: no matching serial port found, use -P or set RAVEDUDE_PORT in your environment

Caused by: Serial port not found.
error: process didn't exit successfully: `ravedude uno -cb 57600 target\avr-atmega328p\debug\tests.elf` (exit code: 1)

I don't understand what is expected from the people behind this project.
I think it waits for another Microsoft Windows user saying something
like:
It works for me.  That is:

MS Windows 9
with the foo extension
configured COM2
avrdude version 7

Regards
a happy Linux user
P.S.
I challenge Original Poster to state

Windows version number
if needed / if installed   which extension (and their version number)
which COM ports have been tried
which COM ports the system besides "the AVR" has
avrdude version number
successes with avrdude with ravedude

P.P.S.
The title should change from
Ravedude can't resolve port (Issue #246)
to
Ravedude can't resolve port on MS Windows version ... (Issue #246)

Hey @Baptistemontan,

Ravendude don't bubble up errors from avrdude, and I have no Idea on how to debug without them.

Ouch, yeah, this is a valid point.  But please do not repurpose existing issues for reporting related problems - can you open a new issue about this specifically instead?
Note that I cannot give support for Windows systems, maybe search through the other Windows related issues here (also closed ones) to see if you can piece together what the story is.  I'll gladly take patches to make it work on MS systems as well if you find anything.

On Tue, Feb 08, 2022 at 02:02:44AM -0800, Baptistemontan wrote:

... and I have no Idea on ...

Please share with us the things you have more then just idea about.
Like:

Version of avrdude
WSL2  or  WSL1 or whatever environment being used
comport number

Groeten
Geert Stappers
P.S.
It would be nice if
Subject: Re: [Rahix/avr-hal] Ravedude can't resolve port on MS Windows version (Issue #246)
gets
Subject: Re: [Rahix/avr-hal] Ravedude can't resolve port on MS Windows 10 (Issue #246)
Yeah, I'm telling that the github.com email interface truncates issue titles.
Silence is hard to parse

I don't know much about WSL 1 vs WSL 2, I just know it worked by switching beetween them.
I don't think that comport number are relevant as I tried a bunch of them and the result were the same.
I'm sorry it is my first time doing github issue, I don't know the "rules", I'have renamed this on to the first issue and will open a new one for ravedude errors

Will looking for the avrdude version I found that I was missing "libusb0.dll", I have been hable to resolve this problem by installing WinAVR wich look like the Windows version of avrdude. Making the switch I now have errors appearing from ravedude:
PS C:\Users\Baptiste\Documents\code\Rust\arduino\tests> cargo run
    Finished dev [optimized + debuginfo] target(s) in 0.21s
     Running `ravedude uno -cb 57600 target\avr-atmega328p\debug\tests.elf`
       Board Arduino Uno
 Programming target\avr-atmega328p\debug\tests.elf => COM6
avrdude.exe: invalid file format 'e' in update specifier
avrdude.exe: error parsing update operation 'flash:w:target\avr-atmega328p\debug\tests.elf:e'
Error: avrdude failed

error: process didn't exit successfully: `ravedude uno -cb 57600 target\avr-atmega328p\debug\tests.elf` (exit code: 1)

which make me think that ravedude does transfer the error, but why does'nt it transfer them before ?

I don't know much about WSL 1 vs WSL 2, I just know it worked by switching beetween them.

Yeah, others have reported this as well in the past.

I don't think that comport number are relevant as I tried a bunch of them and the result were the same.

Agreed, I do not think it should make a difference.  But again, I don't have a clue about windows...

I'm sorry it is my first time doing github issue, I don't know the "rules", I'have renamed this on to the first issue and will open a new one for ravedude errors

You're not doing anything wrong, nothing to be sorry about.  I just requested a separate issue because it helps with keeping a better overview over ongoing topics.

avrdude.exe: invalid file format 'e' in update specifier
avrdude.exe: error parsing update operation 'flash:w:target\avr-atmega328p\debug\tests.elf:e'

Okay, in absolutely most cases this means your version of avrdude is too old.  Actually, ravedude now learned to check the avrdude version to notify people of this but I just noticed that this feature is not yet part of a ravedude release... I need to take care of that.

I've updated to 6.3 and it went further in the process but still failed:
PS C:\Users\Baptiste\Documents\code\Rust\arduino\tests> cargo run
    Finished dev [optimized + debuginfo] target(s) in 0.17s
     Running `ravedude uno -cb 57600 target\avr-atmega328p\debug\tests.elf`
 Programming target\avr-atmega328p\debug\tests.elf => COM6

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude.exe: Device signature = 0x1e950f (probably m328p)
avrdude.exe: erasing chip
avrdude.exe: reading input file "target\avr-atmega328p\debug\tests.elf"
avrdude.exe: can't handle ELF file target\avr-atmega328p\debug\tests.elf, ELF file support was not compiled in
avrdude.exe: read from file 'target\avr-atmega328p\debug\tests.elf' failed

avrdude.exe: safemode: Fuses OK (E:00, H:00, L:00)

avrdude.exe done.  Thank you.

Error: avrdude failed

error: process didn't exit successfully: `ravedude uno -cb 57600 target\avr-atmega328p\debug\tests.elf` (exit code: 1)

ELF file support was not compiled in

Hm, that version also does not support the features we need :/ Maybe you can find another one somewhere else or compile avrdude yourself?  Not sure where the people in the other issues got their avrdude binary from...

[...] but I just noticed that this feature is not yet part of a ravedude release... I need to take care of that.

Done, ravedude 0.1.4 is available now.

I've uninstalled WinAVR and installed a windows clone of avrdude from https://github.com/mariusgreuel/avrdude, AND IT WORK

Great news!  And thanks for that pointer, that fork is something we can recommend to other people as well.

Appart from avrdude I have not needed to install anything else to make it work on windows, maybe some requirement were already installed with the arduino IDE.

I've tried with my old board and it still don't auto find it, but If I pass the port as argument it work.
To be fair even the arduino IDE don't find it, it juste say that there is something connected to the port, but don't say what board it is


[Issue] Standardisation of error messages

E.g., settlePerson (invalid positive index) shows a different error message format as compared to addTransaction n=Self d=Potato c=18.abc
Perhaps we should standardise this if we are planning to add this into the FAQ of our UG as suggested by Prof

Fixed by updating the UG (FAQ section)


[Fluent] Artist on friend activity bugged

Describe the bug
Artist on friend activity bugged.
Screenshots

Specifics (please complete the following information):

OS: Windows 11 (Latest)
Spotify version 2.7.2
Spicetify version <IP_ADDRESS>0.gc21c3367
Fluent

Same issue here.

found another css bug,

Is this still happening @nanchaara?

sorry for late response,
yes it's still happening
both bug

any update on this bug? @afonsojramos
the other one has been fixed

Fluent is now being developed here. Thank you!


add support for lookup_type parameter for BooleanFilter

has been rebased

Ok. Cool. We'll have this. Thanks.


Fatal error: Allowed memory size of 268435456 bytes exhausted

I try to upload my backup files to local flywheel wordpress site. In case of big type files such as "uploads" (~4GB size) and "others" (~3GB size) appears information such as that one:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 386216136 bytes) in /app/public/wp-admin/includes/file.php on line
1190

All picture: https://drive.google.com/file/d/1Ww-pza_M6gkHR7Kq8U3NLRNE2N23OvkX/view?usp=sharing
Virtual server info:
Web Serwer: nginx
PHP Version: 7.0.3
MySQL Version: 5.5.55
WordPress Version: 4.9.6
Two questions:

What should I do to solve this problem?
All of it I do to check if my site will be working on 7.0 PHP version. Can I verify this if I only test my site basing on it what I've manages to upload?

I'll be greatful for your help :)

Unfortunately, this doesn't seem to be an issue with the Bugsnag Laravel integration. Perhaps this was intended for a different repository? Closing for now but feel free to reopen if this is a misunderstanding.


New version: PtFEM v1.0.1

Registering package: PtFEM
Repository: https://github.com/PtFEM/PtFEM.jl
Created by: @goedman
Version: v1.0.1
Commit: e326cad2d2dc549074a8b7cb4f30ff9fe1c34c05
Reviewed by: @goedman
Reference: https://github.com/PtFEM/PtFEM.jl/issues/11#issuecomment-559984270

Please delete this merge request, have updated the merge request to v1.1.0.

Please delete this merge request, have updated the merge request to v1.1.0.

Done.


Fix README.md gradlew typo

As the title says :)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


open *pak.files

Hi
how can i open .*pak files with UAssetGUI ?
or do i need another tool for it ?
thx 4 answers
greets

you can use quick bms for games like ace combat 7

UAssetGUI only operates on individual .uasset files


RX1214 expansion unit in combination with RS2421+

Hello, I have a RS2421+ with a RX1214 expansion unit connected.
When I execute the script it says it cannot find the expansion unit:
synoadmin@STOR004:/$ sudo /volume1/test/Synology_HDD_db-3.5.98/syno_hdd_db.sh
Synology_HDD_db v3.5.98
RS2421+ DSM 7.2.1-69057-5
StorageManager 1.0.0-0017

rs2421+_host_v7 version 8037

Running from: /volume1/test/Synology_HDD_db-3.5.98/syno_hdd_db.sh

HDD/SSD models found: 2
WD60EFRX-68L0BN1,82.00A82,6000 GB
WD60EFRX-68MYMN1,82.00A82,6000 GB

No M.2 drives found

No M.2 PCIe cards found

No Expansion Units found

WD60EFRX-68L0BN1 already exists in rs2421+_host_v7.db
WD60EFRX-68MYMN1 already exists in rs2421+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already enabled.

Drive db auto updates already enabled.

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.

It is detected by DSM:

As a test, there are currently 3 disks in the expansion unit.
They show up as eSATA devices but are unusable:

I didn't realise that Inifiniband expansion units show up in DSM as eSATA devices.
Give me a few hours and I'll add the RX1214 and other old inifiniband expansion units to my https://github.com/007revad/Synology_enable_eunit script.

I've released a new version, v3.0.14, that supports the RX1214.
https://github.com/007revad/Synology_enable_eunit/releases

Can you tell what the following command returns:
sudo syno_slot_mapping

I tried v3.0.14 but the message remains, even after a reboot. I tried RX1214 & RX1214RP. (I have an RX1214RP)
The script ran fine and added the rx1214 expansion unit though.
Synology_enable_eunit v3.0.14
RS2421+ DSM 7.2.1-69057-5

StorageManager 1.0.0-0017

Running from: /volume1/test/Synology_enable_eunit-3.0.14/syno_enable_eunit.sh

Connected Expansion Units:
RX1214

RX1217rp is enabled in /etc/model.dtb
RX1217rp is enabled in /etc.defaults/model.dtb
RX1217 is enabled in /etc/model.dtb
RX1217 is enabled in /etc.defaults/model.dtb
RX1214rp is enabled in /etc/model.dtb
RX1214rp is enabled in /etc.defaults/model.dtb
RX1214 is enabled in /etc/model.dtb
RX1214 is enabled in /etc.defaults/model.dtb

1) DX517       5) RX418      9) RX1217    13) RX1211    17) Restore
2) DX513       6) RX415     10) RX1214rp  14) DX1215II  18) Quit
3) DX213       7) RX410     11) RX1214    15) DX1215
4) DX510       8) RX1217rp  12) RX1211rp  16) DX1211
Select your Expansion Unit: 10
You selected RX1214rp

RX1214rp already enabled in model.dtb

Finished
synoadmin@STOR004:/$ sudo /volume1/test/Synology_enable_eunit-3.0.14/syno_enable_eunit.sh
Synology_enable_eunit v3.0.14
RS2421+ DSM 7.2.1-69057-5

StorageManager 1.0.0-0017

Running from: /volume1/test/Synology_enable_eunit-3.0.14/syno_enable_eunit.sh

Connected Expansion Units:
RX1214

RX1217rp is enabled in /etc/model.dtb
RX1217rp is enabled in /etc.defaults/model.dtb
RX1217 is enabled in /etc/model.dtb
RX1217 is enabled in /etc.defaults/model.dtb
RX1214rp is enabled in /etc/model.dtb
RX1214rp is enabled in /etc.defaults/model.dtb
RX1214 is enabled in /etc/model.dtb
RX1214 is enabled in /etc.defaults/model.dtb

1) DX517       5) RX418      9) RX1217    13) RX1211    17) Restore
2) DX513       6) RX415     10) RX1214rp  14) DX1215II  18) Quit
3) DX213       7) RX410     11) RX1214    15) DX1215
4) DX510       8) RX1217rp  12) RX1211rp  16) DX1211
Select your Expansion Unit: 11
You selected RX1214

RX1214 already enabled in model.dtb

Finished

This is what I get after running sudo syno_slot_mapping
synoadmin@STOR004:/$ sudo syno_slot_mapping
System Disk
Internal Disk
01: /dev/sata1
02:
03:
04:
05:
06:
07:
08:
09:
10:
11:
12:

Esata port count: 1
Eunit port 1 - RX1214

USB Device
01:
02:

Okay. So now I'll have a look at the syno_hdd_db script to see why it's not finding your RX1214
Does the following commands find the RX1214?
sudo syno_disk_data_collector record
file=$(ls /var/log/diskprediction | tail -n1)
grep -Eowi "([FRD]XD?[0-9]{3,4})(rp|ii|sas){0,2}" "/var/log/diskprediction/$file" | uniq

It doesn't return anything:
synoadmin@STOR004:/$ sudo syno_disk_data_collector record
Password:
synoadmin@STOR004:/$ file=$(ls /var/log/diskprediction | tail -n1)
synoadmin@STOR004:/$ grep -Eowi "([FRD]XD?[0-9]{3,4})(rp|ii|sas){0,2}" "/var/log/diskprediction/$file" | uniq
grep: /var/log/diskprediction/data-2024-08-17.json: Permission denied
synoadmin@STOR004:/$ sudo grep -Eowi "([FRD]XD?[0-9]{3,4})(rp|ii|sas){0,2}" "/var/log/diskprediction/$file" | uniq

Do you have any drives in the RX1214?

Yes, there are 3 WD Red 6TB drives in it. It shows them in the DSM UI as external devices on top but they can't be used in storage manager:

In storage manager I can only see the 1 disk in the RS2421+:

Have you rebooted since you ran Synology_enable_eunit?

Yes, on the first run the script asked to reboot, which I did.
2nd run it didn't ask to reboot.

Has the "incompatible expansion unit" warning gone in storage manager?

no

not sure if it matters but it says RX1214-1

RX1214-1 in storage manager is normal. It's because the RS2421 has 2 expansion ports and the RX1214 is connected to expansion port 1.
Have you tried connecting it to expansion port 2?

There's only 1 port on both the rs2421 as the rx1214.

Ah yes, the 24 in RS2421+ means "12 bay NAS + one 12 bay expansion unit".

Are you able to copy the following 4 files, zip them, then attach the zip file to your reply.
Change "/volume1/test" to a volume and shared folder on your RS2421+
cp /var/run/model.dtb /volume1/test/var_run_model.dtb
cp /etc/model.dtb /volume1/test/etc_model.dtb
cp /etc.defaults/model.dtb /volume1/test/etcdefaults_model.dtb
cp /etc.defaults/model.dtb.bak /volume1/test/etcdefaults_model.dtb.bak

And tell me what these commands return:
ls -l /var/run/model.dtb
ls -l /etc/model*
ls -l /etc.defaults/model*

I've attached the requested files
files.zip
This is the output of the commands:
synoadmin@STOR004:/$ ls -l /var/run/model.dtb
-rw-r--r-- 1 root root 6459 Aug 18 13:00 /var/run/model.dtb
synoadmin@STOR004:/$ ls -l /etc/model*
-rw-r--r-- 1 root root 6459 Aug 17 13:02 /etc/model.dtb
synoadmin@STOR004:/$ ls -l /etc.defaults/model*
-rw-r--r-- 1 root root 6459 Aug 17 13:02 /etc.defaults/model.dtb
-rw-r--r-- 1 root root 5567 Sep 23  2023 /etc.defaults/model.dtb.bak

I tried RX1214 & RX1214RP. (I have an RX1214RP)

Do you mean you tried connecting the RX1214 & then the RX1214RP and neither worked?

The script ran fine and added the rx1214 expansion unit though.

Your model.dtb files only contain RX1214RP and not RX1214

RX1214 is enabled in /etc/model.dtb
RX1214 is enabled in /etc.defaults/model.dtb

I think this from the script is incorrect, when the model.dtb already contains RX1214RP. The script is looking for "RX1214" but matching on the RX1214 in "RX1214RP".
Can you run this version with the --check option to confirm that it correctly shows that RX1214RP is enabled and does not show that RX1214 is enabled: https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.0.15-RC
If it does not show:
RX1214 is enabled in /etc/model.dtb
RX1214 is enabled in /etc.defaults/model.dtb

then run it without the --check option and enable RX1214

Do you mean you tried connecting the RX1214 & then the RX1214RP and neither worked?

Sorry for the confusion, I have and RX1214RP. At first I selected RX1214RP, when that didn't work after a reboot I tried RX1214. But that didn't work either after a reboot.
I'll try the new release now.

Synology_enable_eunit v3.0.15
RS2421+ DSM 7.2.1-69057-5

StorageManager 1.0.0-0017

Using options: --check
Running from: /volume1/test/Synology_enable_eunit-3.0.15-RC/syno_enable_eunit.sh

Connected Expansion Units:
RX1214

RX1217rp is enabled in /etc/model.dtb
RX1217rp is enabled in /etc.defaults/model.dtb
RX1217 is enabled in /etc/model.dtb
RX1217 is enabled in /etc.defaults/model.dtb
RX1214rp is enabled in /etc/model.dtb
RX1214rp is enabled in /etc.defaults/model.dtb

enabling rx1214

Synology_enable_eunit v3.0.15
RS2421+ DSM 7.2.1-69057-5

StorageManager 1.0.0-0017

Running from: /volume1/test/Synology_enable_eunit-3.0.15-RC/syno_enable_eunit.sh

Connected Expansion Units:
RX1214

RX1217rp is enabled in /etc/model.dtb
RX1217rp is enabled in /etc.defaults/model.dtb
RX1217 is enabled in /etc/model.dtb
RX1217 is enabled in /etc.defaults/model.dtb
RX1214rp is enabled in /etc/model.dtb
RX1214rp is enabled in /etc.defaults/model.dtb

1) DX517       5) RX418      9) RX1217    13) RX1211    17) Restore
2) DX513       6) RX415     10) RX1214rp  14) DX1215II  18) Quit
3) DX213       7) RX410     11) RX1214    15) DX1215
4) DX510       8) RX1217rp  12) RX1211rp  16) DX1211
Select your Expansion Unit: 11
You selected RX1214

Added RX1214 to model.dtb

The Synology needs to restart.
Type yes to reboot now.
Type anything else to quit (if you will restart it yourself).
yes
Terminated

It did not show RX1214 as enabled with the --check option.
After enabling it again with option 11 it shows the drives in Storage Manager and they can be used!

It seems like DSM sees the RX1214RP as RX1214 but that doesn't really matter as the only difference is the redundant PSU.
Thank you very much!

Excellent.
I'll change the script so when someone selects an RP model the scripts adds both the RP and non-RP models.
I noticed the original model.dtb file contains both RX1217 and RX1217RP. Maybe RX1214RP identifies itself as a RX1214 and the RX1217RP identifies itself as a RX1217RP.