Release Candidate for RELEASE4

Please download the artifcats from the latest AppVeyor builds in Release mode and help testing all features for the next RELEASE4. Please report all bugs you find.
I think the current status of the master-branch is stable, some minor bugs only I hope.

Other than the little bugs that were recently fixed, Reverse Proxy in context menu has no icon! XD
I'll continue to try and break things, but everything seems stable!

Gonna add one. :D

We need to also test these features for multiple clients. I doubt most of us are testing many of these features using more than one client.

@MaxXor :)
Remote Shell issue
Problem:
Server tells client to execute commands with the word "exit" in certain ways that are not ordinary, causing behavior that is not very desirable.
Reproduction of the issue:
Examples of offending text:
1. exit exit
3. start exit exit

afaik xrat is stable but in win10 the remote desktop does not start sometimes when start button is clicked. (at least for me). probability of not starting is 20 of 100 . and file manager download isnt sorking for me

afaik xrat is stable but in win10 the remote desktop does not start sometimes when start button is clicked. (at least for me). probability of not starting is 20 of 100 . and file manager download isnt working for me

@rabbitsmith, i'll be doing some testing with win10.  What is your build of win10 is you don't mind me asking?

9879 64bit

@rabbitsmith, Thank you.  I'm using the Windows 10 Pro Insider Preview (Build 10074 32bit) and everything seems to be working fine for me.  If I recall correctly, you had mentioned your uplink was slow.  Perhaps this could be a factor?

Do you have any other OS's you could test this on?

my isp bans uploading of files. i have a data plan only on my phone. i test xrat only on lan with two pcs running win10 9879

the file manager transfer is really fast but on my pc the integrity of files isnt assured. i transferred a 7mb file with no errors and hashes matching. the problem still persists for files larger than 15 mb.
i mentioned my uplink was slow because i couldnt upload the xrat binaries and the screenshot.

Thank you for the information.  I will try and emulate this problem you are having.

@MaxXor I apologize if this is a foolish question, but would it be possible to add me as a contributor?

@yankejustin You are doing a great job here for the project, but I would add only reluctantly somebody. I hope you understand this. :)
@rabbitsmith You have a pretty scary ISP if it bans uploading of files. :o Is this restricted to all kinds of files? You should upgrade your Windows 10 to the latest preview version, maybe there's the problem.

@MaxXor Yes I understand. Unfortunately adding contributors is a huge jump in power since it is a public repository.
I think we really should fix Remote Shell before we release the next version of xRAT. The input it accepts is still very lenient, such as  exit (simple trimming of the command, then checking). It also doesn't provide error output of the client's shell yet. I almost have it working, though. :)

Ok. :)
I have just added the trimming.

Please do some more tests, the last commits changed a lot of things.

Nice changes! I'm having trouble breaking things now! :'(

There is a noticeably large memory leak in the server.
To reproduce: Launch 50-100 clients.  Select all -> Send reconnect command -> watch xRAT.exe in taskmgr -> repeat sending reconnect commands when clients reconnect

Updated the client & server a bit again, added some more locks & fixed the documentation. The Server.cs documentation is complete, the Client.cs 50% each.
Gonna work on this memory leak now.

Does the memory leak fix work reliable for you?

It is working fine for me.  Memory is being reallocated, and I haven't noticed too much of a performance issue.

Would you be able to provide a rough estimate of the cpu cost? It is nice to know it isn't as big of a hit as I thought.

@MaxXor Also, thanks for the "green apple"! x)

Surprisingly, the only significant CPU usage that occurs is when the server is allocating the resources for each client.  My i7 2600k jumps from 0% idle to ~25-35% when the clients are connecting.  When I sent a command to reconnect 100 clients, my CPU usage jumped up to ~7%

@d3agle I would appreciate if you would check the performance change on my experimental branch to see if what I did helps out with the CPU usage.

Could anyone help me test the branch dev-buffer? I think I'm done improving the buffer management.
Changes: https://github.com/MaxXor/xRAT/pull/263#issuecomment-109762339

@MaxXor Think we could add an #if DEBUG at the builder to allow the creation of multiple clients at one time for easier testing of many clients? It would certainly save some time!
Perhaps add a little TextBox for numeric input at initialization of the Builder Form in DEBUG mode to generate that many clients. :)
I will help you test it tonight.

What I do while testing is replacing the setting MUTEX with public static string MUTEX = Guid.NewGuid().ToString();

Hmmm. Perhaps I could do a bit of changes to make a new Configuration for testing multiple clients by imitating the RELEASE setting. Would you suppose such an addition would be beneficial?

That is a nice point about the MUTEX. Thank you for the reminder.

@d3agle @MaxXor Would you please help me test my new configuration that I made for testing multiple clients please? The only part that does not work is the client. The client just crashes and I am not quite sure why. After starting all the clients, they just stop working.
Perhaps I set a setting for the client incorrectly...

Oh wait. I take that back. The client doesn't work for me on the MaxXor/dev-buffer branch at all. I'm going to open an issue for it: it likely is not the fault of my code on the new configuration. We shall see...

@yankejustin, @MaxXor changed the namespace for the networking part of the client/server to xCore.Client.Networking but forgot to add it in the Build/Renamer.cs.
That should fix it

Sorry, I meant xClient.Core.Networking

Oh, good. Thank you! :)

@d3agle Would you mind sending me a pull request please? I would like to test my new configuration. :)

I think it would help you out quite a great deal.

I'm sorry I don't understand, what would I be sending a pull request for?  I'll pull your branch and test it out. :D

I did notice I forgot to exclude the Label for configurations other than MULTI_CLIENT... I will fix it in a minute. :)

How would I go about creating multiple clients?  I changed both Build options for Client/Server but I don't see anything where I can select how many Clients to create.

If you select the "Multi-Client Release" Configuration, re-build the server and run it. You should see it on the bottom-right corner of the Builder Form.

Make sure you restart Visual Studio because adding the new configuration meant I had to modify the project files.

@d3agle Sorry to bug you again but I am unable to see the reason why my yankejustin/NewConfiguration branch still won't build functional clients... Is there any change you can see that could be the cause of this?

@yankejustin, No worries, I'm hardly ever bugged. :)  I can take a look tonight when I'm free.

@d3agle Would you like to also test the new client & server from dev-buffer in Release mode? :)

@MaxXor, Sure thing.  I've already played with it a little bit, and everything seemed good.  Memory usage was down dramatically, as well as CPU usage.  I believe that there was one instance where only some of the clients connected out of all 100, however I'm unsure if it was a fault on my part with testing or if there is a bug somewhere.  I can look into it as well! :)

@d3agle Yea, that would be great if you can find the cause for it mayb. :)

@d3agle In my case, I can get no clients to connect correctly. Any that I try to start will crash on this configuration...
More Information
1. Operating System
    - Windows 7 Home Premium
    - Service Pack 1
2. System
    - Processor: Intel(R) Core(TM) i7 CPU    -    920 @ 2.67 GHz 2.67 GHz
    - RAM: 16 GB
    - System type: 64-bit Operating System
3. Connection
    - Local Connection to the server -(<IP_ADDRESS>)-
    - Default port -(4282)-
4. Client
    - Default Settings
    - No administrator privileges (I have tried, still doesn't work)
    - Keylogger is not enabled
Starting the Client
1. Double-Click the client
2. Nothing happens for (~15)-(~30) seconds, then a message from Windows will pop up stating that the program has stopped working.
3. As one can guess, by then the program can not recover and it will cause the client to crash.
Final Notes
1. This is likely an issue with the Settings for the client. I have tried debugging to see what is causing this issue but it will function correctly. There are no problems. When I use the RELEASE configuration, the clients built only crash.

@yankejustin, when the client crashes it should leave a metadata file in %temp% and it should show what exception is being thrown runtime.  Could you try to get the client to crash again?  Instead of closing the dialog that pops up, allow it to collect the information and it will display another dialog with a path to the .dmp file and an .xml file (the xml file will contain the info)

@d3agle A client from earlier this morning was used, so it works to some extent. My current issue is having the client show up in the GUI using the latest dev branch. While the client does connect successfully (and is stored in _clients), the client is not shown in the ListView. I cannot also do things like show the Statistics (states that there are no connected clients). Again, they are in _clients and ObjectDisposedExceptions are thrown when I attempt to stop listening on the server for each of the clients, but they are not fully connected. I do know that the ObjectDisposedException is thrown when we disconnect the client and call to close the socket (if (_handle != null) _handle.Close(); etc...... Not sure what is preventing the client from calling Process... It is not getting past here and it must for the server to update the GUI and do further processing...

The ObjectDisposedException is normal when clients are connected and the server stops listening, because at this line it can't receive anymore from the socket. :)
Well, I've tested this now with multiple clients using the RELEASE mode and it's working fine, with enabled/disabled startup and installtion.. :disappointed:
Please completely rebuild your solution in RELEASE mode and re-build your client and test it again.
Also try disabling your windows firewall for this.

This issue should be gone now, can you confirm this with the latest commit? :)

@MaxXor, good work!  I apologize but I won't be able to participate for ~3 weeks.  I have a lot of work to do in school, and I need to concentrate on this work instead.  Keep up the good work guys! :+1:

@d3agle Thanks. No problem! =)

Yeah I have been pretty busy these last few days. I will test tonight if I can.


Integrate Witness, Falco, Tracee, Cilium, etc. for demo of runtime visibility

SSF is an implementation of Secure Software Factory Ref Arch as shown above. A gap we currently have is in runtime visibility space. We should explore various runtime visibility (tracing, eBPF) tools to see how we could integrate them into SSF.
Common ones to explore are:

Witness
Falco
Tracee
Cilium

SSF is intended to abstract out underlying implementations but we do want to explore which ones might be easiest to integrate for the default.

I would like to have a better understanding of how were can interrogate Cillum and Falco to generate attestations.
witness knows the PID and all of the metadata for the CI process

We can look at pulling information from cilium and Falco and use them in the attestation process. Normalize, correlate, and sign the information gathered.
e.g. should be possible to capture network policy configuration, connection information, and other relevant info and correlate with the information traced by witness.
Would need some work to gather and perform the correlation, but would give us the ability to look for anomalies.

We can look at pulling information from cilium and Falco and use them in the attestation process. Normalize, correlate, and sign the information gathered.

Option 1
Falco has a GRPC API that we can connect to over UDS.  This seems like a good fit.
I think we can hack in some code to connect to the Falco API to listen to events happening in the system when the commandrun attestor is working.
Another thing worth looking at is the Source Plugin.
Option 2
I'm not sure if this will work, but may fit in better with witrness' model.
Create a Falco source plugin that filters events we care about for witness.  We can then communicate these events to witness using a postrun attestor.

Hi everyone! This is awesome :) I was in the process of trying to build a Kubernetes tool that can create 'Falco Attestations' in a similar way to what is discussed here. I would love to talk about this more and understand how Tracee, Witness and Cilium all ties in.

https://github.com/cilium/tetragon seems like a good fit for integration with witness.  I added an issue here: https://github.com/testifysec/witness/issues/186


fix: tag list linking to wrong service

Change how TagList auto-links to detail views for kuma.io/service annotations. Since we no longer have one dedicated detail view for all service types, we can’t unconditionally link to them anymore. Instead, we need to make TagList is contextually aware of the corresponding dataplane type or service type.
Signed-off-by: Philipp Rudloff<EMAIL_ADDRESS>

I’ve put this back in draft because I’m not sure this will work.
What we want is to be able to link to the correct detail view whenever a kuma.io/service annotation appears in a TagList. But I’m not sure that’s possible: the kuma.io/service determines the name of a corresponding ServiceInsight object, but this is not generally the same as the name of an ExternalService or MeshGateway resource (the name can be the same, but it doesn’t have to).
For example, an ExternalService named external-service-1 with kuma.io/service tag service-1 will have a corresponding ServiceInsight object named service-1 (crucially, the two names are not the same).
This means that it’s only really possible to link to the correct detail view if we can determine that a kuma.io/service annotation belongs to either a ServiceInsight object of either serviceType internal or gateway_delegated (because those detail views query /meshes/:mesh/service-insights/:name).
@lahabana, does that sound correct to you?


[Feature Request] Run vm from external storage (USB)

I would love the ability to run my VM img from from an external USB drive rather than having to import to the local iPad storage.  This would greatly expand the number of VM’s that can be maintained as well as reduce the overall wear and use of the iPad flash itself.  I assume the VM profile file has to live in the App container, but could the storage pointer access the external storage for the img?
This may be a duplicate of #123 but the way it reads it is not completely clear this would be the same use case.

Sorry, I believe the duplicate may be defect/enhancement #132

Sorry, I believe the duplicate may be defect/enhancement #132

#123

Duplicate of #410


model generating bad random images

I trained my diffusion model in tensorflow based on this implementation and and after training for 450 epochs(on landscape dataset) ,my loss was around 0.015 (mse) and I generated a few samples and generated ones were very bad or random. Below are the generated images for 1000 time steps .
I just want to know is this a training issue , does my model need more training to further reduce the loss (currently : 0.015) OR is the problem in sampling technique.Can anyone help me please?

Hi, I encountered the same issue.

def sample(self, model, n):
        logging.info(f"Sampling {n} new images....")
        model.eval()
        with torch.no_grad():
            x = torch.randn((n, 3, self.img_size, self.img_size)).to(self.device)
            for i in tqdm(reversed(range(1, self.noise_steps)), position=0):
                t = (torch.ones(n) * i).long().to(self.device)
                predicted_noise = model(x, t)
                alpha = self.alpha[t][:, None, None, None]
                alpha_hat = self.alpha_hat[t][:, None, None, None]
                beta = self.beta[t][:, None, None, None]
                if i > 1:
                    noise = torch.randn_like(x)
                else:
                    noise = torch.zeros_like(x)
                x = 1 / torch.sqrt(alpha) * (x - ((1 - alpha) / (torch.sqrt(1 - alpha_hat))) * predicted_noise) + torch.sqrt(beta) * noise
        model.train()
        x = (x.clamp(-1, 1) + 1) / 2
        x = (x * 255).type(torch.uint8)
        return x

Make sure you use the same variable (I am talking about the variable x here) name in these lines:
x = torch.randn((n, 3, self.img_size, self.img_size)).to(self.device)
predicted_noise = model(x, t)
noise = torch.randn_like(x)
noise = torch.zeros_like(x)
x = 1 / torch.sqrt(alpha) * (x - ((1 - alpha) / (torch.sqrt(1 - alpha_hat))) * predicted_noise) + torch.sqrt(beta) * noise
x = (x.clamp(-1, 1) + 1) / 2
x = (x * 255).type(torch.uint8)
return x

If you don't, then you will get noise instead of meaningful images.


Project file templates

Put project file templates (Premiere Pro, Ableton, ...) in a certain folder and you can select them in the init dialogue.

With my current skill level, integrating a template selector is getting messy.
I'll temporarily close the issue for now.


more tests

Codecov Report

Merging #44 (5bcc388) into main (32c6137) will increase coverage by 8.67%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #44      +/-   ##
==========================================
+ Coverage   70.53%   79.20%   +8.67%
==========================================
  Files           4        4
  Lines         224      202      -22
==========================================
+ Hits          158      160       +2
+ Misses         49       32      -17
+ Partials       17       10       -7

Impacted Files
Coverage Δ

app/blizz/client.go
66.12% <100.00%> (+11.33%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #44 (5bcc388) into main (32c6137) will increase coverage by 8.67%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #44      +/-   ##
==========================================
+ Coverage   70.53%   79.20%   +8.67%
==========================================
  Files           4        4
  Lines         224      202      -22
==========================================
+ Hits          158      160       +2
+ Misses         49       32      -17
+ Partials       17       10       -7

Impacted Files
Coverage Δ

app/blizz/client.go
66.12% <100.00%> (+11.33%)
:arrow_up:

Continue to review full report at Codecov.

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


Milestone 8: Popup Window

##Milestone 8: Popup Window
In this milestone, my coding partner @41hulk and I:

Stored all the data in JS objects
Created mask hover for each card to follow the design
Developed popup window and open and close logic
Updated the main page so that the projects section is created dynamically

[ ] [OPTIONAL] I think your pop up window buttons should link your live version and project source code. It will be nice if you could please take a look at it.


Blockscout and celocli signed-blocks do not match signers list

Expected Behavior
Blockscout and celocli validator:signed-blocks should report the exact same signers for any particular block.
Current Behavior
Blockscout doesn't report the same signatories for any given block that the celocli does. May have a 0 or 1 based index issue when determining the signers.
Example
Consider block 794402: https://baklava-blockscout.celo-testnet.org/blocks/794402/signers
For the signer 0x8c517B3BaB0e2d65D5cdF3750CA360ff05B3fc1D, Blockscout reports downtime.

Using celocli validator:signed-blocks --signer 0x8c517B3BaB0e2d65D5cdF3750CA360ff05B3fc1D --at-block 794410 --lookback 10 --width 10
Result:
 794400 ✘.........

This implies the missed block should be 794401, not 794402

A simplified JS version using istanbul.parseBlockExtraData;

const contractkit = require("@celo/contractkit");
const istanbul = require("@celo/utils/lib/istanbul");

const signedParent = async (signer, blockNumber) => {

	const kit = contractkit.newKit("https://baklava-forno.celo-testnet.org");
	const block = await kit.web3.eth.getBlock(blockNumber);
	const election = await kit.contracts.getElection();
	const electedSigners = await election.getValidatorSigners(blockNumber);

	const isSigner = (element) => element === signer;

	const signerIndex = electedSigners.findIndex(isSigner);
	const bitmap = istanbul.parseBlockExtraData(block.extraData).parentAggregatedSeal.bitmap;

	const signed = istanbul.bitIsSet(bitmap, signerIndex);
	console.log(`Signer ${signer} signed blockNumber ${blockNumber} (${block.hash}) == ${signed}`);
	return signed;
}

const run = async () => {

	const signer = "0x8c517B3BaB0e2d65D5cdF3750CA360ff05B3fc1D";
	const blocksToCheck = [794399, 794400, 794401,794402];
	const results = [];

	for(let i = 0; i<blocksToCheck.length;i++){
		results.push(await signedParent(signer, blocksToCheck[i]));
	}
};
run();

Result:
Signer 0x8c517B3BaB0e2d65D5cdF3750CA360ff05B3fc1D signed blockNumber 794399 (0x3a607cd697cfb25dc1467c31f1af62f41bac6eb595d6db854db14bff03c04513) == true
Signer 0x8c517B3BaB0e2d65D5cdF3750CA360ff05B3fc1D signed blockNumber 794400 (0xa49e21e358e0e67c55a2327f09b72eeb16b006638d979179a18b3d2f188d05b2) == true
Signer 0x8c517B3BaB0e2d65D5cdF3750CA360ff05B3fc1D signed blockNumber 794401 (0xf8d2f1daeea8bdbecc275d6420d155bcb0514b190975f1dce2618d4d9fed7ecd) == false
Signer 0x8c517B3BaB0e2d65D5cdF3750CA360ff05B3fc1D signed blockNumber 794402 (0xfe50195c7f2c4f3eecb96f78858ea28cae48af774e3ca30b53182b25f8a7d2c7) == true

This also implies the missed block should be 794401

This should be fixed already, looks like baklava blockscout hasn't been upgraded for a while. Note that the missed block is 794400 (parent of 794401).

@mrsmkl So for clarification, when calling celocli validator:signed-blocks what's reported is always actually a missed signature on block-1 ?


Which linux version or SONiC version will the first version of DASH be based on

Hi, community
Which linux version or SONiC version will the first version of DASH be based on?

Upvoting
I do have a similar query regarding SONIC-DASH?

It's a good bet that DASH would use sonic-buildimage as the basis, which is debian-based. Vendors would simply define new platform targets, provide a binary of libsai (and other collaterals for platform-specific purposes).
Perhaps @lguohan can answer this more definitively?


AVCaptureVideoDataOutputSampleBufferDelegate ?

Is it possible to get AVCaptureVideoDataOutputSampleBufferDelegate running ?

Yes !
You have a completion block for that :
public var blockCompletionBuffer: blockCompletionOutputBuffer? {
        didSet {
            self.cameraOutput.blockCompletionBuffer = self.blockCompletionBuffer
        }
    }

usage :
self.cameraEngine.blockCompletionBuffer = { buffer in

}


Retry several times the installation of an integration in the e2e tests

What does this PR do?

Retry several times the installation of an integration in the e2e tests
Motivation

See the comment in the function. This is what we ask customers to do
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


bug: fzf-lua file selection for quickfix list does not work with

Did you check docs and existing issues?

[x] I have read all the LazyVim docs
[x] I have updated the plugin to the latest version before submitting this issue
[x] I have searched the existing issues of LazyVim
[x] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2
Operating system/version
MacOS 15.1.1
Describe the bug
Hey,
fzf-lua has the default behaviour to select files with <tab>, which can then be send to the quickfix list. However, within LazyVim, the tab key causes to toggle the .gitignore filter.
Since I did not find any documentation about this behaviour in the LazyVim documentation, nor any options in fzf-lua to configure the selection key, I guess this behaviour is not intended.
Steps To Reproduce

Open fzf-lua with <leader>fg
press <tab>

Expected Behavior
The file should be selected instead of toggling the gitignore filter.
Repro

Works as intended for me. I can select files with <tab>. What does :verbose tmap <tab> show? Can you try with a default LazyVim installation with only fzf Extra enabled? My guess is you have some conflicting keymap in your personal configuration or from some plugin that you installed.

hm, unfortunately there is no other mapping on tab.
:verbose tmap <tab> returns no mapping found.
Ok, if its works for you ... I am on a relatively clean setup, but will do what you supposed.


Verify cache support works

@bfulton @nahiluhmot
Will fix #269
Pulls in the rubygems code that builds each file in the tar.

:100:

When is it possible that we will have release with this feature?
It is a real to pain to use serverspec with docker without proper cache.

Released in v1.21.3

Great :+1:
Thanks for quick response.


Fix warning in processor.py.

Description

Thanks @libeiheng feedback in #1099.
Motivation and Context

Fix the warning in processor.py.
How Has This Been Tested?

[x] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[x] Fix bugs
[ ] Add new feature
[ ] Update documentation

@you-n-g
Fix the annoying warning.

Thanks so much!
It looks much better now!


feat: Scalar Types Reference

Proof of concept of an idea to split out the scalar types details into its own page that is just linked from the schema reference instead.
Relevant previews:

/docs/reference/api-reference/prisma-schema-reference#model-field-scalar-types
/docs/reference/api-reference/prisma-scalar-types-reference

I still think this is a good idea and we should do that.

Maybe turn this into an issue instead if we need to redo the PR anyways?

Tracking this in an issue: https://github.com/prisma/docs/issues/5496


Qt 5.5 qtmultimedia has missing plugins (gstreamer)

These are the mediaservice plugins in Qt 5.5:
$ nix-build -A qt55.qtmultimedia -Q && ls -1 result/lib/qt5/plugins/mediaservice/
/nix/store/ji28da47s9ib8ysg7ns7f88awglqz6vh-qtmultimedia-5.5.0
libqtmedia_audioengine.so

It lacks a few libraries compared to Qt 5.4:
$ nix-build -A qt54.multimedia -Q && ls -1 result/lib/qt5/plugins/mediaservice/
/nix/store/0anpmz654yfsaz5ygjv8x4xp3ghkd2rs-qtmultimedia-5.4.2
libgstaudiodecoder.so
libgstcamerabin.so
libgstmediacapture.so
libgstmediaplayer.so

I thought adding pkgconfig to qtmultimedia buildInputs would fix it, similarly to 449b6028a64fae427fdce4abf126825bd8aaf260 ("qt5.multimedia: fix gstreamer support"). But that didn't add more libraries to the mediaservice/ directory.

CC @ttuegel, @gebner.

Looking at the build log. Qt 5.4 says:
Checking for openal... no
Checking for gstreamer... yes
Checking for gstreamer_photography... no
Checking for gstreamer_encodingprofiles... yes
Checking for gstreamer_appsrc... yes
Checking for linux_v4l... yes
Checking for resourcepolicy... no

Whereas Qt 5.5 says:
Checking for openal... no
/tmp/nix-build-qtmultimedia-5.5.0.drv-0/qtmultimedia-opensource-src-5.5.0/qtmultimedia.pro:28: Variable GST_VERSION is not defined.
Checking for resourcepolicy... no

Adding pkgconfig to buildInputs doesn't change the qt55 build log (still complains about missing GST_VERSION).

Relevant snippet from qtmultimedia-opensource-src-5.5.0/qtmultimedia.pro:
    isEmpty(GST_VERSION) {
        contains(QT_CONFIG, gstreamer-0.10) {
            GST_VERSION = 0.10
        } else: contains(QT_CONFIG, gstreamer-1.0) {
            GST_VERSION = 1.0
        }
    }
    cache(GST_VERSION, set)
    !isEmpty(GST_VERSION):qtCompileTest(gstreamer) {
        qtCompileTest(gstreamer_photography)
        qtCompileTest(gstreamer_encodingprofiles)
        qtCompileTest(gstreamer_appsrc)
        qtCompileTest(linux_v4l)
    }

I'm not sure yet the proper way to set either GST_VERSION (directly) or via QT_CONFIG. It doesn't look like we have "qmakeFlags" in nixpkgs.

@bjornfor qmake will respect configureFlags.

Doh! Thanks! :-)
Passing "GST_VERSION=1.0" to qmake fixes it. Will send PR soon.

PR: https://github.com/NixOS/nixpkgs/pull/10916


Memory settings

When exporting trace information:

What's the high/low watermark for heap usage, if any?
If the heap usage hits a certain threshold, does the exporter become blocking at that point?
Is there a way to configure high watermarks for the client?

We were able to verify heap usage increased steadily as we added backpressure to our ingest service. This can become a big issue if we had actual latency issues or if our ingest service was down.

I can confirm this behavior when the ingest service becomes overloaded/slow the heap steadily increases and eventually causes memory pressure leading to an OOM event in the application.
I havn't found the same behavior when the ingest service is completely down but perhaps I need to test that case more thoroughly.
I'm attaching a few screenshots from a heap dump I was able to capture...

This issue seems different than https://github.com/census-instrumentation/opencensus-java/issues/1813 where spans that aren't closed properly will cause an OOM event (?)

It seems https://github.com/census-instrumentation/opencensus-specs/issues/262 and https://github.com/census-instrumentation/opencensus-java/pull/1837 are related to this issue.

@dmichel1 by any chance can you take dump the thread stacktrace as well?

Based on the picture the attach the memory is hold by the SpanExporterImpl thread.
The current design is this:
ThreadExecutesRequest -> DisruptorThread -> SpanExporterImplThread -> Exporter (usually no thread here, executed from the span exporter impl thread)
Keep in mind that threads are passed to the SpanExporterImplThread only when they end, so clearly not related to this https://github.com/census-instrumentation/opencensus-java/issues/1813.
For me this does not correlate with the  blocking queue issue. May still be a correlation if the Disruptor thread bursts the Spans into the SpanExporterImplThread but probably that is not the issue.
I think the issue is that if one of the exporter code blocks (for this explanation I would pretend that you use exporterX). Lets assume that backend for exporterX is not reachable for few seconds, the SpanExporterImplThread will block so the spans to export are growing unbounded during this time. This also can happen if only pushing to exporterX is just slow (or slower than the rate of spans get produced). I think we need to do few things here:

Set a deadline for all exporters requests to ensure that we don't block for a long time, also make sure that they don't have a retry logic (double check if Stackdriver for example has retry logic enabled). For example if Stackdriver is used and a quota error is hit (this is possible because the volume of spans as suggested by this issue is high) the problem will be very bad.
Make all exporter requests async, analyze if making them multi-threaded will help.
Consider to start dropping Spans when the exporter cannot keep up with the amount of spans produced by the application.
Consider to suggest users to use the oc-agent to deal with retries and maybe a higher deadline.

Can we make the async operation non blocking so that it's fire and forget. Don't want the endpoint that'll accept the spans to slow down the application.
Also, would be interesting to offer an option to batch, so rather than emitting an array of spans, maybe we send multiple arrays with a new line delimiter or allow configuration of batch size to reduce network overhead

@bogdandrutu
Here's the stacktrace from the exporter thread. I got this from the hprof of the JVM that crashed.
ExportComponent.ServiceExporterThread-0
  at io.opencensus.implcore.trace.RecordEventsSpanImpl.toSpanData()Lio/opencensus/trace/export/SpanData; (RecordEventsSpanImpl.java:252)
  at io.opencensus.implcore.trace.export.SpanExporterImpl$Worker.fromSpanImplToSpanData(Ljava/util/List;)Ljava/util/List; (SpanExporterImpl.java:165)
  at io.opencensus.implcore.trace.export.SpanExporterImpl$Worker.run()V (SpanExporterImpl.java:194)
  at java.lang.Thread.run()V (Thread.java:834)

Set a deadline for all exporters requests to ensure that we don't block for a long time, also make sure that they don't have a retry logic (double check if Stackdriver for example has retry logic enabled). For example if Stackdriver is used and a quota error is hit (this is possible because the volume of spans as suggested by this issue is high) the problem will be very bad.

That is an interesting example with the Stackdriver quota issue. We encountered exactly this issue a few months ago without reaching a conclusion on what went wrong.

Make all exporter requests async, analyze if making them multi-threaded will help.

+1 to making this async and maybe even fire and forget. That is a similar to how we publish metrics, although in the metrics use case dropping some metrics will often only cause resolution differences vs having incomplete trace data.

Consider to start dropping Spans when the exporter cannot keep up with the amount of spans produced by the application.

+1 here too

Consider to suggest users to use the oc-agent to deal with retries and maybe a higher deadline.

I would prefer not to have a side car for deploying tracing and keep everything internal to the library or the vendor exporters.
@bputt i've seen exporter implementations handle the batching of the span data. I believe the stackdriver exporter does this already. The lightstep exporter does something similar as well, https://docs.lightstep.com/docs/lightstep-client-buffer.

First step to make things more deterministic. We will schedule batches of a maximum size to the exporters:
https://github.com/census-instrumentation/opencensus-java/pull/1882

@dmichel1: oc-agent can be deploy like a workload (service) in your cluster, so that all applications will initially send data to this then the oc-agent forwards everything to the backend. This way we can configure some queuing and retries, etc to deal with backend not being available for some time.
This is definitely not requirement (more like a suggestion), but can help if the backend is not in the same cluster or cloud region.


Instascale panic: runtime error: index out of range [0] with length 0

When running the MCAD scale test in the CI, we observe the following panic of instascale:
I0629 09:35:38.640517       1 appwrapper_controller.go:225] Found Appwrapper named aw004-300s that has status Pending
I0629 09:35:38.640534       1 appwrapper_controller.go:283] The instanceRequired array: []
E0629 09:35:38.640595       1 runtime.go:78] Observed a panic: runtime.boundsError{x:0, y:0, signed:true, code:0x0} (runtime error: index out of range [0] with length 0)
goroutine 401 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x1a7dfe0?, 0xc0001cc438})
	/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.23.0/pkg/util/runtime/runtime.go:74 +0x86
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc0001ac0c0?})
	/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.23.0/pkg/util/runtime/runtime.go:48 +0x75
panic({0x1a7dfe0, 0xc0001cc438})
	/usr/lib/golang/src/runtime/panic.go:838 +0x207
github.com/project-codeflare/instascale/controllers.discoverInstanceTypes(0xc000a38000)
	/workspace/controllers/appwrapper_controller.go:286 +0x370
github.com/project-codeflare/instascale/controllers.onAdd({0x1b57f40?, 0xc000a38000?})
	/workspace/controllers/appwrapper_controller.go:228 +0x10e
k8s.io/client-go/tools/cache.ResourceEventHandlerFuncs.OnAdd(...)
	/opt/app-root/src/go/pkg/mod/k8s.io/client-go@v0.23.0/tools/cache/controller.go:231
k8s.io/client-go/tools/cache.FilteringResourceEventHandler.OnAdd({0x1ca2a28?, {0x1e4ce70?, 0xc000438510?}}, {0x1b57f40, 0xc000a38000})
	/opt/app-root/src/go/pkg/mod/k8s.io/client-go@v0.23.0/tools/cache/controller.go:264 +0x64
k8s.io/client-go/tools/cache.(*processorListener).run.func1()
	/opt/app-root/src/go/pkg/mod/k8s.io/client-go@v0.23.0/tools/cache/shared_informer.go:787 +0xaf
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x0?)
	/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.23.0/pkg/util/wait/wait.go:155 +0x3e
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc00058af38?, {0x1e38020, 0xc000494b10}, 0x1, 0xc00018ed80)
	/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.23.0/pkg/util/wait/wait.go:156 +0xb6
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0001b2000?, 0x3b9aca00, 0x0, 0xf1?, 0xc00058af88?)
	/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.23.0/pkg/util/wait/wait.go:133 +0x89
k8s.io/apimachinery/pkg/util/wait.Until(...)
	/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.23.0/pkg/util/wait/wait.go:90
k8s.io/client-go/tools/cache.(*processorListener).run(0xc000206800?)
	/opt/app-root/src/go/pkg/mod/k8s.io/client-go@v0.23.0/tools/cache/shared_informer.go:781 +0x6b
k8s.io/apimachinery/pkg/util/wait.(*Group).Start.func1()
	/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.23.0/pkg/util/wait/wait.go:73 +0x5a
created by k8s.io/apimachinery/pkg/util/wait.(*Group).Start
	/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.23.0/pkg/util/wait/wait.go:71 +0x85
panic: runtime error: index out of range [0] with length 0 [recovered]

instascale is running  from quay.io/project-codeflare/instascale-controller:v0.0.4, deployed by these two ODH Kfdef:
  - https://raw.githubusercontent.com/opendatahub-io/odh-manifests/master/kfdef/odh-core.yaml
  - https://raw.githubusercontent.com/opendatahub-io/distributed-workloads/main/codeflare-stack-kfdef.yaml

The issue might be linked with this MCAD ticket.
The Appwrapper mentioned in the log is certainly this one. Its status is visible in this file. The resource is expected not to run, because no GPU is made available for it.

Thanks @kpouget
I feel this may be related to #96

good catch @VanillaSpoon, I agree that it's related:
I0629 09:35:38.640534       1 appwrapper_controller.go:283] The instanceRequired array: []

so of course
instanceName := instanceRequired[idx+id]

this will crash :)
Now I see this above:
	for k, v := range aw.Labels {
		if k == "orderedinstance" {
			instanceRequired = strings.Split(v, "_")
		}
	}

and I'm wondering where this is documented, to better understand this orderedinstance label 🤔

In terms of documentation we are quite limited, but have plans to further add machinepool, and machineset documentation that will hopefully provide further information on orderedInstances soon.
I will also bring @dimakis  to this discussion as he may have more information.

@VanillaSpoon  do we know if this issue is resolved with one of your merged PRs?

Hey @asm582,
Yes, this has been resolved. I have left the conversion open in regards to providing documentation on Machinepools/machinesets.
However, there is another ticket open for documenting these. This issue can be closed.


scrollbar for suggestions

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue.
Fix: https://github.com/maheshmnj/searchfield/issues/33
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing using flutter test

If you need help, consider pinging the maintainer @maheshmnj

published v0.7.5


Add libraries property to both SubmitRun and CreateJob Databricks tasks

Not sure why this hasn't been included initially, but it's a useful property to run Python jobs on Databricks.
API reference with the libraries property: https://docs.databricks.com/api/workspace/jobs/submit
best to also include other missing properties incl.:

git_source
idempotency_token
queue
access_control_list

Syntax for the libraries:
id: test
namespace: dev
tasks:
  - id: submitRun
    type: io.kestra.plugin.databricks.job.SubmitRun
    authentication:
      token: <your-token>
    host: <your-host>
    runTasks:
      - existingClusterId: <your-cluster>
        taskKey: taskKey
        libraries:
          - pypi:
              package: simplejson
          - jar: dbfs:/mnt/databricks/library.jar
          - maven:
              coordinates: "org.jsoup:jsoup:1.7.2"
        sparkPythonTask:
          pythonFile: /Shared/hello.py
          sparkPythonTaskSource: WORKSPACE
    waitForCompletion: PT5M

None of these properties can be added via the Java SDK:

git_source
idempotency_token
queue
access_control_list

Note that there is additional parameters that can be passed to some task, I don't know if those properties can be set this way.


Class mismatch during evaluation

Hello,
I seem to have found a bug in the evaluation scripts. When I save my formatted predictions, everything is correct (classes are assigned correctly). However, when I use the classwise evaluation and visualization scripts (following the instructions you provided precisely) some of the classes are incorrectly assigned. I noticed that only classes with similar characters are incorrectly assigned. For example, I have a class called 'personal_mobility' and 'person' of which all predictions get grouped as 'personal_mobility' in both the classwise and visualization results. This also happened in 'bicycle_rack' and 'bicycle' for which all predictions were assigned 'bicycle_rack'. All other classes are correct. Again, my formatted json outputs do not have this problem.
I did not use the bug template because I currently dont have time to produce the proper documentation of the issue, but wanted to bring this to your attention. I can add the error info later when I have more time (although it may not be necessary).
Is this something mmdetection is aware of?

Hi @pcicales Thanks for the feedback, I will check it immediately.

Hello,
I seem to have found a bug in the evaluation scripts. When I save my formatted predictions, everything is correct (classes are assigned correctly). However, when I use the classwise evaluation and visualization scripts (following the instructions you provided precisely) some of the classes are incorrectly assigned. I noticed that only classes with similar characters are incorrectly assigned. For example, I have a class called 'personal_mobility' and 'person' of which all predictions get grouped as 'personal_mobility' in both the classwise and visualization results. This also happened in 'bicycle_rack' and 'bicycle' for which all predictions were assigned 'bicycle_rack'. All other classes are correct. Again, my formatted json outputs do not have this problem.
I did not use the bug template because I currently dont have time to produce the proper documentation of the issue, but wanted to bring this to your attention. I can add the error info later when I have more time (although it may not be necessary).
Is this something mmdetection is aware of?

@pcicales In order to facilitate the reproduction, can you use the issue template?

@pcicales Sorry for the late response,  PR #5227 involves a serious bug that can make class mismatches during evaluation and the training performance seems better. And you can find the reason is that PR #5243, you can pull the master and fix it.
I am really sorry for such a serious bug.


Fully mutating linear solver

At the moment, AbstractDifferentiation does not have a fully mutating API, and benchmarks show allocations are non-negligible when multiplying by A and B. Opening this to track https://github.com/JuliaDiff/AbstractDifferentiation.jl/issues/14 and see what we can do

The problem is that most AD packages don't actually support mutation.

Yeah I know, it would be useless for ChainRules, but not for ForwardDiff?

Trying to solve this with https://github.com/gdalle/DifferentiationInterface.jl

This is now possible with DifferentiationInterface but

it won't work with every outer backend
it requires a mutating version of the conditions conditions!(c, x, y)

I hope to make it part of v0.7


Uncaught SecurityError: Failed to read the 'frameElement' property from 'Window'

I built an SFX bundle using the builder.buildStatic()API but when I try this bundle it in production, it fails on some websites because systemjs tries to read a cross origin iframe property from the 'window' object (the bundle is embedded in an iframe).
It fails within the function linkDynamicModule(entry) { } of the compiled bundle. At some point the following code within this function is executed:
// don't trigger getters/setters in environments that support them
if (typeof exports == 'object' || typeof exports == 'function') {
  if (getOwnPropertyDescriptor) {
    var d;
    for (var p in exports)
      if (d = Object.getOwnPropertyDescriptor(exports, p))
        defineProperty(entry.esModule, p, d);
  } else {
    var hasOwnProperty = exports && exports.hasOwnProperty;
    for (var p in exports) {
      if (!hasOwnProperty || exports.hasOwnProperty(p))
        entry.esModule[p] = exports[p];
    }
  }
}

It fails on the Object.getOwnPropertyDescriptor(exports, p) where exports is referring to the window object of the iframe and p is 'frameElement' which leads to the cross origin property lookup.
I used<EMAIL_ADDRESS>and my project is configured using<EMAIL_ADDRESS>

It happens when it is linking the core-js/modules/$.global.js module, because this one will return the global object, which in a browser will equal to the window object.

Ok, I found out that this issue is already flagged and that it will be fixed with esmExports support for static builds. So I'll close this one.


Update fault-tolerance-and-automated-repair.md

Corrected errors found while doing tutorial for onboarding.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/da92bc7b37e38d7a7f0374d8ef0cdcafbd82a785/
Edited pages:

v19.2/training/fault-tolerance-and-automated-repair.md


loosen the package version for torch 2.0

When installing this package through  pip install clip-video-encode , it can be observed that the package is compatible with pytorch 2.0 as
clip-video-encode 1.3.0 depends on torch<2 and >=1.7.1

@imliuruiqi yeah sounds good. I'm super busy these days, if you could submit a PR I'd be happy to merge it

I check the setup.py and it seems that it will get the the install_requires from requirements.txt and it turns out that the torch version is fine:
torch>=1.7.1,<=2

maybe you just need to release a new version with the current requirements

ah yeah, I'm planning on doing a release soon, in the mean time you can just git clone and pip install -e .

unfortunately, I was unable to install it by that way, got error with ERROR: Failed building wheel for pyarrow mainly blames to the cmake. But nevermind i will wait the release as i am not in a hurry.
Thanks a lot for your time and take care.


Read issue after polling characteristics

Hi @adabru,
Thank you a lot for this repo. I have a little problem, I am not a developer at first but for my project I have to increase my knowledge sorry if there is any approximation.
I am trying to connect an arduino through the BLE to a Unity game.
When I use the demo just to test if it's working, I can connect to my device, I found the service and the characteristic but I can't read the value. Nothing happens.
I tried with the Microsoft's Bluetooth Low Energy sample. Which works until I reach the same step. When I read, I get a status saying : "Read Result : Unknown format". So I understand that there is no problem with the reading in itself but more with the variable inside the characteristic.
I am already able to read the Characteristic with another arduino so I think that the Characteristics is updating well.
On the arduino side, I tried by simply put in the main loop :
int level = 10;
MyChar.writeValue(level);
I know that the writeValue() method automatically convert level into unsigned char.
Do you think it is a problem ?
Do you have any idea on how to handle this format with BleWinrtDll ?
Thank you a lot !!

Hi @Sobattan :),
ReadCharacteristic is not implemented in this dll, just SubscribeCharacteristic. You can add it yourself or use the subscription.
I think you are getting the error message from this line: https://github.com/microsoft/Windows-universal-samples/blob/0db108e/Samples/BluetoothLE/cs/Scenario2_Client.xaml.cs#L295 . It is inside the ReadCharacteristic function. You can use that function from the cpp part https://github.com/microsoft/Windows-universal-samples/blob/0db108e/Samples/BluetoothLE/cppwinrt/Scenario2_Client.cpp#L370 and port it over to BleWinrt .
Or you can take tufeixp's code by following this discussion: https://github.com/adabru/BleWinrtDll/issues/45#issuecomment-1479295183
Good luck :)

Hi @adabru ,
Thank you for your answer !
Really helpful, it is very difficult for me as i'm not a developer. So, for now, I'm trying to compile a dll with the tufeixp's code (already 2 days on it 🥲 )
I put his function :
fire_and_forget ReadDataAsync(BLEData data) {
	{
		lock_guard lock(dataQueueLock);
	}
	auto characteristic = co_await retrieveCharacteristic(data.deviceId, data.serviceUuid, data.characteristicUuid);
	GattReadResult result = co_await characteristic.ReadValueAsync();
	if (result.Status() == GattCommunicationStatus::Success) {
		auto dataReader = DataReader::FromBuffer(result.Value());
		auto output = dataReader.ReadString(dataReader.UnconsumedBufferLength());

		BLEData data;
		wcscpy_s(data.characteristicUuid, sizeof(data.characteristicUuid) / sizeof(wchar_t), to_hstring(characteristic.Uuid()).c_str());
		wcscpy_s(data.serviceUuid, sizeof(data.serviceUuid) / sizeof(wchar_t), to_hstring(characteristic.Service().Uuid()).c_str());
		wcscpy_s(data.deviceId, sizeof(data.deviceId) / sizeof(wchar_t), characteristic.Service().Device().DeviceId().c_str());

		data.size = output.size();
		memcpy(data.buf, output.data(), data.size);
		{
			lock_guard queueGuard(dataQueueLock);
			dataQueue.push(data);
			dataQueueSignal.notify_one();
		}
		//saveError(L"%s:%d read done: %s", __WFILE__, __LINE__, output.c_str());
	}
}

I compiled it into a dll following your README.md and put the resulting dll into the Unity project (same place as the previous dll).
I added the following lines in the BleApi.cs :
[DllImport("BleWinrtDll.dll", EntryPoint = "ReadDataAsync")]
public static extern bool ReadDataAsync(in BLEData data);

And finally simply modified the Subscribe function as follow :
public void Subscribe()
    {
        // no error code available in non-blocking mode
        // BleApi.SubscribeCharacteristic(selectedDeviceId, selectedServiceId, selectedCharacteristicId, false);
        // isSubscribed = true;
        BleApi.BLEData data = new BleApi.BLEData();
        BleApi.ReadDataAsync(in data);
        subcribeText.text = data.ToString();
    }

From your point of view, does it look the right way to do it ?
Like this, I have an error :
EntryPointNotFoundException: ReadDataAsync assembly: type: member:(null)
Thank you so much for your help !

I think you're missing the entry in the BleWinrtDll.h file for ReadDataAsync.
Concerning the ReadDataAsync function:

The first lock_guard seems redundant, you should be able to remove it.
There is no error reporting for the case that it fails.
If the data is not a string, it might not work. I would do the string decoding in Unity.

I can't see how subscribeText is defined and passed to Unity. It might be easiest to use the dataQueue.
You can add an accompanying ReadData function to ReadDataAsync. Like SubscribeCharacteristic uses SubscribeCharacteristicAsync and like SendData is using SendDataAsync.
If you want you can fork this repo, make your changes and create a pull request. I can then comment on your code directly and when it's working and kinda matching the rest of the code we can merge it.


[ContextPure] Fix broken style property

Fix component using the ContextPure mixin.
Implement the new shouldComponentUpdate suggeseted by shaurya947.
We now rerender correctly when the current theme and the next theme are both undefined
Follow https://github.com/callemall/material-ui/pull/1718.

@chrismcv What do you think?

This looks good to me. Thanks @oliviertassinari and @chrismcv. This should also hopefully take care of #1719


Compile failed for Hello_World

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Discord first?

[X] This is not a support question.

Description of bug
.cargo/registry/src/github.com-1ecc6299db9ec823/ahash-0.8.11/src/random_state.rs:463:5
multiply:     |
multiply: 463 | /     fn hash_one<T: Hash>(&self, x: T) -> u64 {
multiply: 464 | |         RandomState::hash_one(self, x)
multiply: 465 | |     }
multiply:     | |_____^
multiply:     |
multiply:     = note: see issue #86161 https://github.com/rust-lang/rust/issues/86161 for more information
multiply:     = help: add #![feature(build_hasher_simple_hash_one)] to the crate attributes to enable
multiply:
multiply: For more information about this error, try rustc --explain E0658.
multiply: error: could not compile ahash (lib) due to 1 previous error
multiply: warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for hello-world-methods v0.1.0 (/Users/yongxin.yao/bitlayer/risc0/examples/hello-world/methods)
Steps to reproduce
reproduce step by step

cd risc0/examples/hello-world
cargo build

Build ENV

rustc --version
rustc 1.77.2 (25ef9e3d8 2024-04-09)

cargo --version
cargo 1.77.2 (e52e36006 2024-03-26)

cargo risczero --version
cargo-risczero 1.0.5

@ludete have you tried running cargo run --release?

Is there an existing issue?
* [x]  I have searched the existing issues

Experiencing problems? Have you tried our Discord first?
* [x]  This is not a support question.

Description of bug
.cargo/registry/src/github.com-1ecc6299db9ec823/ahash-0.8.11/src/random_state.rs:463:5 multiply: | multiply: 463 | / fn hash_one<T: Hash>(&self, x: T) -> u64 { multiply: 464 | | RandomState::hash_one(self, x) multiply: 465 | | } multiply: | |_____^ multiply: | multiply: = note: see issue #86161 rust-lang/rust#86161 for more information multiply: = help: add #![feature(build_hasher_simple_hash_one)] to the crate attributes to enable multiply: multiply: For more information about this error, try rustc --explain E0658. multiply: error: could not compile ahash (lib) due to 1 previous error multiply: warning: build failed, waiting for other jobs to finish... error: failed to run custom build command for hello-world-methods v0.1.0 (/Users/yongxin.yao/bitlayer/risc0/examples/hello-world/methods)
Steps to reproduce
reproduce step by step
1. cd risc0/examples/hello-world

2. cargo build

Build ENV
1. rustc --version
   rustc 1.77.2 (25ef9e3d8 2024-04-09)

2. cargo --version
   cargo 1.77.2 (e52e36006 2024-03-26)

3. cargo risczero --version
   cargo-risczero 1.0.5

hey, sorry about the late response - it looks like you're trying to use an older guest compiler. Could you run cargo risczero install --version r<IP_ADDRESS> and build the program again to see if this fixes the issue?

@ludete have you tried running cargo run --release?

This error occurs after the command is run.

hey, sorry about the late response - it looks like you're trying to use an older guest compiler. Could you run cargo risczero install --version r<IP_ADDRESS> and build the program again to see if this fixes the issue?

have fixed by the below command:
cargo risczero build-toolchain --version v2024-04-22.0.

Oh, a notice that the link with discord has been invalid in the official website.


Value of getCurrentSelectionCfi() is showing null. How to integrate highlighting feature in ReadiumSDK ?

Is that with fixed-layout EPUBs? Or reflowable?
Could you please have a look at
https://readium.firebaseapp.com/?epub=epub_content%2Faccessible_epub_3
to see how selection highlights work?

Your SDK supports only fixed-layout i guess! I'm using your SDK only. For integration of highlight feature do i have to purchase your license? Or is it possible to use highlight feature without purchasing your license? If yes, then please let me know the procedure to use the annotations.

The Readium SDK (i.e. C++ source code) is available under the following terms:
http://readium.org/membership/license-readium-sdk
The code known as "Readium JS" can be used any way you like, under permissive license terms.

There are issues with selection+highlighting in fixed-layout EPUBs. This feature ; still at experimental stage ; works more reliably in reflowable documents.
Both ReadiumSDK and ReadiumJS share a common library, see the source code in the "readium-shared-js" repository. This is where selection and highlighting is implemented, see this plugin: https://github.com/readium/readium-shared-js/tree/develop/plugins/highlights
...and see how it is integrated in "readium-js-viewer" (keyword search "plugins.highlights"): https://github.com/readium/readium-js-viewer/blob/develop/src/js/EpubReader.js#L824
        // Set handlers for click events
        $(".icon-annotations").on("click", function () {
            readium.reader.plugins.highlights.addSelectionHighlight(Math.floor((Math.random()*1000000)), "test-highlight");
        });

            ReadiumSDK.on(ReadiumSDK.Events.PLUGINS_LOADED, function () {
                Globals.logEvent("PLUGINS_LOADED", "ON", "EpubReader.js");

                console.log('PLUGINS INITIALIZED!');

                if (!readium.reader.plugins.highlights) {
                    $('.icon-annotations').css("display", "none");
                } else {

                    readium.reader.plugins.highlights.initialize({
                        annotationCSSUrl: readerOptions.annotationCSSUrl
                    });

                    readium.reader.plugins.highlights.on("annotationClicked", function(type, idref, cfi, id) {
        console.debug("ANNOTATION CLICK: " + id);
                        readium.reader.plugins.highlights.removeHighlight(id);
                    });
                }

            });


visualize/visualize_freeform giving a 302 error (labs)

I'm trying to paste the output of http://geoffrey.crbs.ucsd.edu:9000/scigraph/graph/neighbors/UBERON:0001831?depth=1&blankNodes=false&direction=both
into
http://amigo2.berkeleybop.org/amigo/visualize_freeform
Found

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.```

Hrm. No immediate obvious answer. Various subgraphs of the given example work, but not the whole. The differences between working and non-working subsets doesn't make any sense yet. Odd.

In case we lose the test data at the URL:
{

    "nodes":

[

{

    "id": "UBERON:0001065",
    "lbl": "parotid duct",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "200px-Illu_quiz_hn_02.jpg",
    "lbl": null,
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "UBERON:0010314",
    "lbl": "structure with developmental contribution from neural crest",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "UBERON:0003419",
    "lbl": "mesenchyme of parotid",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "UBERON:0001831PHENOTYPE",
    "lbl": "parotid gland phenotype",
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "UBERON:0000409",
    "lbl": "serous gland",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "UBERON:0004119",
    "lbl": "endoderm-derived structure",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "Parotid_Gland",
    "lbl": null,
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "UBERON:0001567",
    "lbl": "cheek",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "OBO:uberon/core#efo_slim",
    "lbl": null,
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "OBO:uberon/core#uberon_slim",
    "lbl": null,
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "Parotid_gland",
    "lbl": null,
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "C0030580",
    "lbl": null,
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "UBERON:0011847",
    "lbl": "acinus of parotid gland",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "Illu_quiz_hn_02.jpg",
    "lbl": null,
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "UBERON:0001829",
    "lbl": "major salivary gland",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "181234002",
    "lbl": null,
    "meta":

    {
        "category": [ ]
    }

},
{

    "id": "UBERON:0003360",
    "lbl": "epithelium of parotid gland",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "UBERON:0001831",
    "lbl": "parotid gland",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "UBERON:0012102",
    "lbl": "buccal salivary gland",
    "meta":

{

    "category":

        [
            "anatomical entity"
        ]
    }

},
{

    "id": "UBERON:0008801",
    "lbl": "parotid gland primordium",
    "meta":

{

    "category":

            [
                "anatomical entity"
            ]
        }
    }

],
"edges":
[

{

    "sub": "UBERON:0001831",
    "obj": "UBERON:0000409",
    "pred": "subClassOf",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "UBERON:0012102",
    "pred": "subClassOf",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "Illu_quiz_hn_02.jpg",
    "pred": "depicted_by",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "181234002",
    "pred": "hasDbXref",
    "meta": { }

},
{

    "sub": "UBERON:0003419",
    "obj": "UBERON:0001831",
    "pred": "BFO_0000050",
    "meta": { }

},
{

    "sub": "UBERON:0001065",
    "obj": "UBERON:0001831",
    "pred": "BFO_0000050",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "UBERON:0001567",
    "pred": "BFO_0000050",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "Parotid_gland",
    "pred": "hasDbXref",
    "meta": { }

},
{

    "sub": "UBERON:0001831PHENOTYPE",
    "obj": "UBERON:0001831",
    "pred": "UPHENO_0000001",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "200px-Illu_quiz_hn_02.jpg",
    "pred": "depicted_by",
    "meta": { }

},
{

    "sub": "UBERON:0011847",
    "obj": "UBERON:0001831",
    "pred": "BFO_0000050",
    "meta": { }

},
{

    "sub": "UBERON:0003360",
    "obj": "UBERON:0001831",
    "pred": "BFO_0000050",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "UBERON:0010314",
    "pred": "subClassOf",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "C0030580",
    "pred": "hasDbXref",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "Parotid_Gland",
    "pred": "hasDbXref",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "UBERON:0008801",
    "pred": "RO_0002202",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "OBO:uberon/core#efo_slim",
    "pred": "inSubset",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "OBO:uberon/core#uberon_slim",
    "pred": "inSubset",
    "meta": { }

},
{

    "sub": "UBERON:0001831",
    "obj": "UBERON:0001829",
    "pred": "subClassOf",
    "meta": { }

},

        {
            "sub": "UBERON:0001831",
            "obj": "UBERON:0004119",
            "pred": "subClassOf",
            "meta": { }
        }
    ]

}

Started guessing that this might have something to do with input length and the server rather than the client software (also, the CLI attempts seem to mostly work okay). Got an interesting message from the production server that has different settings:
 Error message:
malformed header from script. Bad header=0%20%20%22sub%22%3A%20%22UBERO: amigo

Playing around to the point that I can make a set pass or not by playing with labels, which would seem to imply something really weird or server setting kinds of issues.

Pretty sure it's not directly AmiGO, CLI of same thing gives:

Given that what happens is that the initial POST goes to /amigo/visualize (HTMLClient.pm), which then turns it into a redirect to /visualize (VisualizeServer.pm). Redirects cannot POST, so it is converted into a GET and becomes a URL with length 15404 (measured). The typical server limit is like north of 8k or something, so I'm guessing there is a setting issue.
The "best" fix would be re-working the code to not have redirects. Likely, I'd fold the visualize client into VisualizeServer.pm so there are no redirects, only POSTs. I'm guessing that would be a fix.
Short-term, maybe an apache setting could be found to up the limit sufficiently. A few tries and nothing so far.
Likely quite low priority as it is a labs server setting issue with no current "real" use case. Unless you need this for something @cmungall?

No need for hacky fixes. Testing the viability of driving AmiGO widgets from SciGraph. The final product would be a widget that consumes the bbop/amigo lib and calls SG directly, so the json would come in directly from an api call, not as a get/post param

Sorry, I can't do that, Dave.
This /is/ actually an issue, so I'll keep this open until resolved.
This isn't the first time we've had trouble with the redirect mechanism--I thinking that for everything it papers over, it's probably better to avoid it altogether (for example, it took a lot more digging to find the problem, which is likely caused by the system in the first place).

Should be fixed with the completion of #185.

@cmungall This should now work on labs. Please not that the URLs for visualize components have changed, so access them from the software_list page. A little more work for #185 to be finished, but I'll leave it for now.


[NUMI] ... Querying Numi CLI doesn't work

Extension
https://www.raycast.com/andresmorelos/numi
Description
When I check the "Use numi-cli" checkbox, quering Numi doesn't work. It says that numi-cli is not installed, when in fact it is. It is installed with Homebrew as suggested on the Numi Github page, and the path to the numi file (a symbolic link) is correct. The symbolic link is at
/opt/homebrew/bin/numi-cli
Here are a couple of screenshots of the setting and the result.

I tried uninstalling/installing the extension, the numi-cli, Numi itself, but nothing changed.
Steps To Reproduce

Check the "use numi-cli" option in the extension
Try to query Numi

Current Behaviour
It says that numi-cli is not installed, which is not correct. If I query the numi-cli directly in Terminal, it works fine.
Expected Behaviour
It should work with the numi-cli.

I just tested this and downloaded it from brew too, no errors. What does which numi-cli in the terminal gives you?

I just tested this and downloaded it from brew too, no errors. What does which numi-cli in the terminal gives you?

That is weird. Here you go:

BTW, does it matter that Numi itself is installed? Could that somehow impact the numi-cli? I tried uninstalling Numi the application too, but still getting the error.

No that should be more than fine, do you know how to debug an extension by forking it? If so I'd like to check it with you 🙂

Unfortunately not. Are there instructions how to do that somewhere? Also, could it be a permissions problem of some kind maybe?

If you know just a little bit of coding, then you can use the Fork action like this

That will guide you a bit, let me know if that files, then you can open the forked extension and add console.logs to the code and run the code with npm run dev

OK, I figured it out. I ran the extension from Raycast, and it worked like that. It turns out there was an error in my .bashrc file which was causing the problem. After correcting that, it started working fine.
Sorry to bother you and glad that we were able to work this out. Thanks!

@alexbet could you please share your .bashrc to replicate it? I also have Starship prompt but with ZSH, and, it works without issues.
Probably, it's related to https://github.com/starship/starship/issues/5816

BTW, I see here (https://github.com/raycast/extensions/issues/10986#issuecomment-1967358099) that you use ZSH too
Why not use a .zshrc file instead of .bashrc and add
eval "$(starship init zsh)"

The code use is:
eval "$(starship init bash)"
I have no idea why this would be a problem. Anyway, switched to ZSH instead.

The code use is:
eval "$(starship init bash)"
I have no idea why this would be a problem. Anyway, switched to ZSH instead.

I'm not sure why this happened, but it also with the VSCode integrated terminal when it tried to source the .bashrc file, probably something related to the starship prompt for the bash environment.
Now that you switched to ZSH, is all working as expected?
Let me know to close this issue.

@alexbet I'll close this issue, feel free to reopen if the issue persists
@raycastbot close this issue

@AndresMorelos @pernielsentikaer I’ve encountered the same issue for some weird things in my .bashrc file.
Since I use zsh daily, could you consider use --norc arg to bash?

@kevinm6 let me verify this option

Thanks! You should get it free using /bin/sh, but maybe in some machine/configuration it doesn't load the PATH and in that case can't find the numi-cli binary.


Homebridge keeps shutting down due to Error

Homebridge was working great until today when I restarted my pi. Everytime I start it up it shows the same error message:
[2019-8-27 14:29:10] Error: listen EADDRINUSE :::44593
at Server.setupListenHandle [as _listen2] (net.js:1345:14)
at listenInCluster (net.js:1386:12)
at Server.listen (net.js:1474:7)
at EventedHTTPServer.listen (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:60:19)
at HAPServer.listen (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:158:20)
at Bridge.Accessory.publish (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:616:16)
at Server._publish (/usr/local/lib/node_modules/homebridge/lib/server.js:132:16)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:101:10)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:59:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
[2019-8-27 14:29:10] Got SIGTERM, shutting down Homebridge...
I've tried reinstalling homebridge and nodeJS but nothing has changed.
I'm using node v9.9.0

The port you have chosen in your config is already in use. Trying a different port might help


Create a User Exception pathway

Also modify the system exception endpoints that are actually reporting on user exceptions to use the new pathway instead.

[Cameron is going to look at this]

Shane, what did you want to happen when UserExceptions are thrown? Currently, SystemExceptions are just logged to the console and rethrown in arc-exceptions.ts. Did you want UserExceptions to be handled differently?


[Renderer] Known issue : Changing gl_texturemode in game won't affects most textures.

glTexParameter (GL_TEXTURE_MIN_FILTER or GL_TEXTURE_MAG_FILTER) doesn't work for bindless textures.
Adding -nobindless to launch parameters should temporarily fix this issue.

Not a thing anymore thing there is no bindless mode now.


Decrease the number of GWT workers

the project should sucessfullly compile
on a machine with 8GB RAM (even that can be
seen as quite a lot). Running 4 parallel
workers on 8GB resulted in OOMEs.

+1


0.7 release - guns are semi transparent / faces seem inverted

after upgrading from 0.64 to 0.7, the guns are not rendering properly anymore. I just did an extract with replace all
Valve index
RTX 4090
let me know if you need any more detail

Oops, when reworking the rendering behind the scenes I forgot to re-adjust the near clip plane (distance from the camera at which things stop rendering). Fixed in 0.7.1


support for changing url when a component renders ?

Version
4.1.1
Test Case
https://codesandbox.io/s/n55VljYk7
Steps to reproduce
Expected Behavior
Actual Behavior
this is no a bug ..
Hi Team,
I have a componentA which renders different component on some conditions till here all is good.I just want a little support , Is there a way in react-router-dom to change the url if some component renders.
for example : let us suppose my current url is somedomain.com/someUrl
and My component is something like this
         class Counter extends React.Component {
               constructor(props) {
                super(props);
               this.state = {count: props.initialCount};
            }
          render(){
          if (somecondtion){
           render some otherComponentB // component gets render but url does't change
          // i use window.history.pushState('', '', '/otherComponentB') in render function of     `otherComponentB`
         // is there a better way to acomplish in the router itself , is there a function passed in the router
          which can change a url
          }

          }
      }

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux. Thanks!


Better String Interpolation Highlighting

TS and JS Grammar Extension version:  0.4 / latest
Code
console.log(`Running a server at http://localhost:${port}${baseUrl}`)

It would be better if the $ and { were different colors than the string and variable

This is tracked by Microsoft/vscode#13166 and something vscode theme needs to handle.


App immediately closes on Android 5.0.1

First of all, thanks for the great app!
Since version 0.7.6, however, the app immediately closes again after launch. Installing an older version (e.g. 0.7.5) of the app allows it to open again. Due to the API changes in the Cookbook server, however, this is sadly not a proper workaround anymore, as recipes can't be displayed.
The tablet is running Android 5.0.1.

Are you still able to reproduce this on 0.7.9 with the cookbook version 0.10.2 ?
If no I'd close this as outdated. I sadly can't reproduce this.

Yes, I'm still able to reproduce this with the app on version 0.7.9 and the NC coobook app at 0.10.2.
I can help with debugging, if you let me know what information is helpful to you. :)

A logcat would be great :)

Sure. Here is a logcat created with adb shell logcat | grep "cookbook" > logcat.txt:
D/ActivityManager(  529): startActivity intent packagename com.nextcloud_cookbook_flutter
V/ActivityManager(  529): send smart intent for new activity com.nextcloud_cookbook_flutter Where 1
V/MultiWinService(  529): startActivityMayWait >>> com.nextcloud_cookbook_flutter;com.nextcloud_cookbook_flutter.MainActivity
I/ActivityManager(  529): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.nextcloud_cookbook_flutter/.MainActivity bnds=[626,969][859,1113] (has extras)} from uid 10021 on display 0
V/WindowManager(  529): Set focused app to: AppWindowToken{20be4870 token=Token{cf90ab3 ActivityRecord{1ce63022 u0 com.nextcloud_cookbook_flutter/.MainActivity t217}}} old focus=AppWindowToken{b59e5fe token=Token{159d8db9 ActivityRecord{d6a6380 u0 com.lenovo.olauncher/com.android.launcher3.Launcher t213}}} moveFocusNow=true
V/WindowManager(  529): findFocusedWindow: Reached focused app=AppWindowToken{20be4870 token=Token{cf90ab3 ActivityRecord{1ce63022 u0 com.nextcloud_cookbook_flutter/.MainActivity t217}}}
D/WindowManager(  529): addWindowToListInOrderLocked: win=Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter} Callers=com.android.server.wm.WindowManagerService.addWindow:2502 com.android.server.wm.Session.addToDisplay:167 android.view.ViewRootImpl.setView:532 android.view.WindowManagerGlobal.addView:272
I/hack_camera(  529): resumed activity packageName:com.nextcloud_cookbook_flutter,prev resumed activity packageName:com.lenovo.olauncher
V/WindowManager(  529): Adding window Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter} at 4 of 10 (after Window{21c46e24 u0 com.android.settings/com.android.settings.deviceinfo.lenovousb.UsbPicker})
V/WindowManager(  529): Looking for focus: 4 = Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
V/WindowManager(  529): Relayout of Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter}: focusMayChange=true
V/WindowManager(  529): Looking for focus: 5 = Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
V/WindowManager(  529): Looking for focus: 5 = Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
I/hack_camera(  529): hackForCameraGone Visible window packageName:com.nextcloud_cookbook_flutter,Gone window packageName:com.lenovo.olauncher
I/ActivityManager(  529): Process com.nextcloud_cookbook_flutter (pid 2284) has died
W/ActivityManager(  529): notify app switch quit packageName=com.nextcloud_cookbook_flutter
D/ActivityManager(  529): notifyAppSwitch resumed: false; pkg:com.nextcloud_cookbook_flutter
I/ActivityManager(  529): Start proc com.nextcloud_cookbook_flutter for activity com.nextcloud_cookbook_flutter/.MainActivity: pid=2671 uid=10096 gids={50096, 9997, 3003} abi=armeabi-v7a
V/WindowManager(  529): Looking for focus: 5 = Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
V/WindowManager(  529): Looking for focus: 5 = Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
I/ActivityManager(  529): Process com.nextcloud_cookbook_flutter (pid 2671) has died
W/ActivityManager(  529): notify app switch quit packageName=com.nextcloud_cookbook_flutter
D/ActivityManager(  529): notifyAppSwitch resumed: false; pkg:com.nextcloud_cookbook_flutter
I/ActivityManager(  529): Start proc com.nextcloud_cookbook_flutter for activity com.nextcloud_cookbook_flutter/.MainActivity: pid=2693 uid=10096 gids={50096, 9997, 3003} abi=armeabi-v7a
V/WindowManager(  529): Looking for focus: 5 = Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
V/WindowManager(  529): Looking for focus: 5 = Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
I/ActivityManager(  529): Process com.nextcloud_cookbook_flutter (pid 2693) has died
W/ActivityManager(  529): notify app switch quit packageName=com.nextcloud_cookbook_flutter
W/ActivityManager(  529): Force removing ActivityRecord{1ce63022 u0 com.nextcloud_cookbook_flutter/.MainActivity t217}: app died, no saved state
D/ActivityManager(  529): notifyAppSwitch resumed: false; pkg:com.nextcloud_cookbook_flutter
V/WindowManager(  529): Remove Window{3b977b9c u0 Starting com.nextcloud_cookbook_flutter} client=296f9f0f, surface=Surface(name=Starting com.nextcloud_cookbook_flutter) Callers=com.android.server.wm.AppWindowToken.removeAllWindows:262 com.android.server.wm.WindowManagerService.removeAppFromTaskLocked:4763 com.android.server.wm.WindowManagerService.removeAppToken:4820 com.android.server.am.ActivityStack.removeActivityFromHistoryLocked:3215
V/WindowManager(  529): Removing focused app token:AppWindowToken{20be4870 token=Token{cf90ab3 ActivityRecord{1ce63022 u0 com.nextcloud_cookbook_flutter/.MainActivity t217}}}
D/ActivityManager(  529): startActivity intent packagename com.nextcloud_cookbook_flutter
V/ActivityManager(  529): send smart intent for new activity com.nextcloud_cookbook_flutter Where 1
V/MultiWinService(  529): startActivityMayWait >>> com.nextcloud_cookbook_flutter;com.nextcloud_cookbook_flutter.MainActivity
I/ActivityManager(  529): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.nextcloud_cookbook_flutter/.MainActivity bnds=[626,969][859,1113] (has extras)} from uid 10021 on display 0
D/WindowManager(  529): addWindowToListInOrderLocked: win=Window{cdce69b u0 Starting com.nextcloud_cookbook_flutter} Callers=com.android.server.wm.WindowManagerService.addWindow:2502 com.android.server.wm.Session.addToDisplay:167 android.view.ViewRootImpl.setView:532 android.view.WindowManagerGlobal.addView:272
V/WindowManager(  529): Adding window Window{cdce69b u0 Starting com.nextcloud_cookbook_flutter} at 8 of 15 (after Window{d999184 u0 org.fdroid.fdroid/org.fdroid.fdroid.views.AppDetailsActivity})
V/WindowManager(  529): Set focused app to: AppWindowToken{3f339a38 token=Token{30d4995 ActivityRecord{15ee754c u0 com.nextcloud_cookbook_flutter/.MainActivity t219}}} old focus=AppWindowToken{b59e5fe token=Token{159d8db9 ActivityRecord{d6a6380 u0 com.lenovo.olauncher/com.android.launcher3.Launcher t213}}} moveFocusNow=true
V/WindowManager(  529): findFocusedWindow: Reached focused app=AppWindowToken{3f339a38 token=Token{30d4995 ActivityRecord{15ee754c u0 com.nextcloud_cookbook_flutter/.MainActivity t219}}}
I/hack_camera(  529): resumed activity packageName:com.nextcloud_cookbook_flutter,prev resumed activity packageName:com.lenovo.olauncher
V/WindowManager(  529): findFocusedWindow: Reached focused app=AppWindowToken{3f339a38 token=Token{30d4995 ActivityRecord{15ee754c u0 com.nextcloud_cookbook_flutter/.MainActivity t219}}}
V/WindowManager(  529): Relayout of Window{cdce69b u0 Starting com.nextcloud_cookbook_flutter}: focusMayChange=true
I/ActivityManager(  529): Start proc com.nextcloud_cookbook_flutter for activity com.nextcloud_cookbook_flutter/.MainActivity: pid=2805 uid=10096 gids={50096, 9997, 3003} abi=armeabi-v7a
V/WindowManager(  529): Looking for focus: 9 = Window{cdce69b u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
V/WindowManager(  529): Looking for focus: 9 = Window{cdce69b u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
I/hack_camera(  529): hackForCameraGone Visible window packageName:com.nextcloud_cookbook_flutter,Gone window packageName:com.lenovo.olauncher
V/WindowManager(  529): Looking for focus: 9 = Window{cdce69b u0 Starting com.nextcloud_cookbook_flutter}, flags=25362712, canReceive=false
D/houdini ( 2805): [2823] Added shared library /data/app/com.nextcloud_cookbook_flutter-2/lib/arm/libflutter.so for ClassLoader by Native Bridge.
I/ActivityManager(  529): Process com.nextcloud_cookbook_flutter (pid 2805) has died
W/ActivityManager(  529): notify app switch quit packageName=com.nextcloud_cookbook_flutter
D/ActivityManager(  529): notifyAppSwitch resumed: false; pkg:com.nextcloud_cookbook_flutter
I/ActivityManager(  529): Start pr

I don't see anything obvious but will have a deeper look.
Thanks.


Clang fix-es

Solves two compilation issues on clang for Mac OS X.
@jlecoeur how long should the git_hash be at most?
It seems that the commit hash is 8 character long but if you add the tag (2.0.0-alpha), it's getting longer. I set it to 16, but I guess it should be decided how long we want it to be.

The hash has to be 8 characters long to be sent over mavlink, I applied a commit from dev/ins_kf where I remove the tag from GIT_HASH.


WIP: New Theme

DO NOT MERGE, EVEN IF IT IS PASSING
This is the feature branch for the new Bootstrap4 layout. In addition to RSpec, we'll need to also do a manual test of the main user-flows to ensure there isn't any weird behavior.

yeeeeaaaah
going to go ahead and close this one. We can revisit later.


Improve a few property definitions

The properties for stripDir and parent used the name 'parent' as a
variable.
The properties for filename and dirname seemed to be wrong and also used
'parent' as a variable.

Sweet, nice improvements, thanks for reviewing these properties.
--
A fun thing to try in the future would be to automatically prove these properties with HERMIT and add it as a test-suite or embed proofs next to the declarations with template-haskell. :smile:

Updated the docs on Hackage.


Macro expansion error recovery

This PR introduces a very basic macro expansion error recovery strategy. If none of the macro rules matches it just returns the tokens which were passed in. Long term I doubt this is the ideal solution, but in the short term it seems to significantly improve completions within macros.
It also allows completion in macros without a closing paren, which is especially handy.
Notes to reviewers:

I don't fully understand why it was necessary to set the delimiter to None on the returned token tree in expand
I don't fully understand the implications of changing the >= to > in completion_context
The test change in expand_macro.rs seems like perhaps this is a regression? But I did some manual testing in an actual editor and I can't see any issues with the new behavior.
The test_expand_bad_literal test was deleted because it checks for errors during the expansion process, but the expansion process no longer returns errors. Again here I'm not sure what practical implication this could have.
The expand method still returns a Result, although it cannot fail (at least for now). I left it this way because it seemed like leaving the Result as part of the public API would allow more flexibility in perhaps solving this problem differently in the future. But I'd be happy to remove it if you'd prefer.
The completion in macros without a closing paren works with a locally defined macro, but for some reason it does not work for std lib macros

I think this overlaps with #3580.

I think this overlaps with #3580.

Oops I didn't see that, thanks for pointing it out. That approach certainly seems very thorough.
I don't have time at the moment to really dig into that PR, but it looks like perhaps in the short term the approach proposed here provides some additional improvements. I'm just basing that on the number of completion test files which changed (to add completions) in that PR vs this one, so it could be that @flodiebold just hasn't finished updating the tests.

r? @flodiebold here :)

Hmm I don't know, I have to say I like my approach more, and it's working as far as I can see now. I copied your new test to my branch, and it works as well. My branch does need a bit of refactoring still though.

Closing this in favor of #3580.
Thanks all for the feedback, and especially thanks to @flodiebold for the work on #3580.


fix: delete s3 buckets and keep state-store bucket on deletion #309

I started https://github.com/kubefirst/kubefirst/issues/309 , but I realised the certs bucket is not stored in the kubefirst file.
The backupSSL and restoreSSL uses creates a new bucket following the pattern k1-<hosted zone name> and doesn't store it in the kubefirst file.
This also remove the confirmation(user input) to delete buckets.
Signed-off-by: João Vanzuita<EMAIL_ADDRESS>

nice ux detail work


Phase out old nom macros

Went through all of the old nom style macros implemented and took a nom 5 approach, using only functions. Some fall out from that included simplifying our error reporting, I'm not even sure why we were differentiating parse from incomplete errors in the first place...
Another part of these changes is tackling a bunch of stuff clippy warned about. The most significant change there was removing the weirdness where I was implementing FromStr for each object as well as a from_str in each object's impl. Now instead of seeing let x = Object::from_str("..."), we're using let x: Result<Object,_> = "...".parse()

Coverage decreased (-0.6%) to 92.257% when pulling d4d85f68598daa7ca7b2280b19b0edb54fe3bd79 on phase-out-old-nom-macros into 78d25a6e8b4adfc74652bc77549cdcd2fb04ed3a on master.


Installation fails due to conflicting Werkzeug version

Hi, users are unable to run jawfish due to dependency conflict with Werkzeug package.
As shown in the following full dependency graph of jawfish, jawfish requires Werkzeug==0.11.11，while flask>=0.12.3 requires Werkzeug>=0.15.
According to pip’s “first found wins” installation strategy, Werkzeug==0.11.11 is the actually installed version. However, Werkzeug==0.11.11 does not satisfy Werkzeug>=0.15.
Dependency tree
jawfish-master
| +-flask(version range:>=0.12.3)
| | +-click(version range:>=5.1)
| | +-itsdangerous(version range:>=0.24)
| | +-jinja2(version range:>=2.10.1)
| | | +-markupsafe(version range:>=0.23)
| | +-werkzeug(version range:>=0.15)
| +-flask-sslify(version range:==0.1.5)
| | +-flask(version range:*)
| | | +-click(version range:>=5.1)
| | | +-itsdangerous(version range:>=0.24)
| | | +-jinja2(version range:>=2.10.1)
| | | | +-markupsafe(version range:>=0.23)
| | | +-werkzeug(version range:>=0.15)
| +-itsdangerous(version range:==0.24)
| +-jinja2(version range:>=2.10.1)
| | +-markupsafe(version range:>=0.23)
| +-markupsafe(version range:==0.23)
| +-werkzeug(version range:==0.11.11)
| +-wtforms(version range:==2.1)

Thanks for your help.
Best,
Neolith

Solution

Fix your direct dependency to be Werkzeug>=0.15.
I have checked this revision will not affect your downstream projects now.

Remove your direct dependency Werkzeug, and use Werkzeug transitively introduced by flask.

Which solution do you prefer, 1 or 2?
@gingeleski  Please let me know your choice. I can submit a PR to solve this issue.

2 - thanks.


Update to mention path style variable

Added reference to path style variable use_path_style_endpoint in AWS SDK for PHP

Updated, PTAL.


feat: add js_run_devserver rule

Also tested in downstream repos as well:

with webpack devserver https://github.com/aspect-build/rules_webpack/pull/58
with next.js devserver https://github.com/aspect-build/bazel-examples/pull/121

Example output from e2e/js_run_devserver:
$ ibazel run //src:serve_alt
iBazel [8:23PM]: You are using an experimental filesystem watcher. If you would like to disable that, please set the environment variable
	IBAZEL_USE_LEGACY_WATCHER=1
iBazel [8:23PM]: Querying for files to watch...
iBazel [8:23PM]: Running //src:serve_alt
...
iBazel [8:23PM]: Launching with notifications
...
iBazel [8:23PM]: Starting...
...

Starting js_run_devserver //src:serve_alt
Syncing...
4 files synced in 6 ms
Running './node_modules/.bin/http-server src/http_root' in /var/folders/0w/2qdthbhd3lqd1p96g4r99h2m0000gn/T/js_run_devserver-eT8u65/__main__

Starting up http-server, serving src/http_root

http-server version: 14.1.1

http-server settings:
CORS: disabled
Cache: 3600 seconds
Connection Timeout: 120 seconds
Directory Listings: visible
AutoIndex: visible
Serve GZIP Files: false
Serve Brotli Files: false
Default File Extension: none

Available on:
  http://<IP_ADDRESS>:8080
  http://<IP_ADDRESS>:8080
Hit CTRL-C to stop the server

on a change to source file:
iBazel [8:25PM]: Changed: "/Users/greg/aspect/rules/js/rules_js/e2e/js_run_devserver/src/index.html". Rebuilding...
iBazel [8:25PM]: Running //src:serve_alt
iBazel [8:25PM]: Notifying of changes
IBAZEL_BUILD_STARTED
...
iBazel [8:25PM]: IBAZEL BUILD SUCCESS
IBAZEL_BUILD_COMPLETED SUCCESS
Syncing...
2 files synced in 6 ms

Another example output of a next.js devserver with more files synced
...
Starting js_run_devserver //:dev
Syncing...
21 files synced in 20 ms
Initial sync done
Running './node_modules/.bin/next dev' in /var/folders/0w/2qdthbhd3lqd1p96g4r99h2m0000gn/T/js_run_devserver-QW4kUl/__main__

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
event - compiled client and server successfully in 1635 ms (173 modules)

and after a change
iBazel [8:29PM]: Changed: "/Users/greg/aspect/rules/bazel-examples/next.js/pages/index.tsx". Rebuilding...
iBazel [8:29PM]: Running //:dev
iBazel [8:29PM]: Notifying of changes
IBAZEL_BUILD_STARTED
...
iBazel [8:29PM]: IBAZEL BUILD SUCCESS
IBAZEL_BUILD_COMPLETED SUCCESS
Syncing...
2 files synced in 13 ms
wait  - compiling...
event - compiled client and server successfully in 106 ms (173 modules)


Provide an AppImage for Linux

Providing an AppImage for distributing application has, among others, these advantages:

Applications packaged as an AppImage can run on many distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)
One app = one file = super simple for users: just download one AppImage file, make it executable, and run
No unpacking or installation necessary
No root needed
No system libraries changed
Works out of the box, no installation of runtimes needed
Optional desktop integration with appimaged
Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
Can optionally GPG2-sign your AppImages (inside the file)
Works on Live ISOs
Can use the same AppImages when dual-booting multiple distributions
Can be listed in the AppImageHub central directory of available AppImages
Can double as a self-extracting compressed archive with the --appimage-extract parameter

In other terms, you wouldn't need to make a version for each Linux distributions, and it would be easier to launch. I think that, this is the kind of time-saving tool that you guys need!
LibreOffice, Krita and other projects already use it, see the full list here: https://appimage.github.io/apps/

This repo is depreciated, did you mean to open this issue in OpenBazaar-Desktop?
@hoffmabc can answer questions about how he handle releases.


Implement Sisimai::Rhost::ExchangeOnline

https://technet.microsoft.com/en-us/library/bb232118

https://technet.microsoft.com/ja-jp/library/bb232118(v=exchg.150).aspx


use tendermint.rs conversion methods for headers

I noticed that we are converting to tendermint headers ourselves. We should rely on their upstream impls to save some work: https://docs.rs/tendermint/0.30.0/tendermint/block/header/struct.Header.html#impl-TryFrom<Header>-for-Header:
https://github.com/astriaorg/sequencer-relayer/blob/442a1723a61ab0aec5e44626a1bb8c74b12f76f3/src/types.rs#L125-L126

Hi, I'd like to take this on. Any suggestions would be highly appreciated. A doubt that I have is if the currently used Header type should be completely replaced by the tendermint::Header because they seem to have the same fields but some types differ.

@xeno097 hey, thank you for the interest! I think @itamarreif might be working on this already, can you confirm?

Oh ok, thank you for letting me know that!


akkoma: update tzdata 1.1.1 -> 1.1.2

tzdata 1.1.1 contains a bug that prevents updating the timezone data
https://github.com/lau/tzdata/issues/148
[info] tzdata release in place is from a file last modified Fri, 22 Oct 2021 02:20:47 GMT. Release file on server was last modified Thu, 05 Sep 2024 18:47:42 GMT.
[error] GenServer :tzdata_release_updater terminating
** (ArgumentError) errors were found at the given arguments:

  * 2nd argument: not a tuple

    :erlang.element(1, :error)
    (tzdata 1.1.1) lib/tzdata/util.ex:223: Tzdata.Util.to_int/1
    (tzdata 1.1.1) lib/tzdata/parser.ex:38: Tzdata.Parser.process_rule/1
    (tzdata 1.1.1) lib/tzdata/parser.ex:24: Tzdata.Parser.process_tz_list/1
    (tzdata 1.1.1) lib/tzdata/parser.ex:86: Tzdata.Parser.process_zone/5
    (tzdata 1.1.1) lib/tzdata/parser.ex:24: Tzdata.Parser.process_tz_list/1
    (tzdata 1.1.1) lib/tzdata/parser.ex:86: Tzdata.Parser.process_zone/5
    (tzdata 1.1.1) lib/tzdata/parser.ex:24: Tzdata.Parser.process_tz_list/1
Last message: :check_if_time_to_update
State: []

Things done

Built on platform(s)

[x] x86_64-linux
[x] 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
[x] 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

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354228

x86_64-linux

:white_check_mark: 1 package built:

akkoma

I have run the module tests successfully.

This set contains a number of whitespace‐only changes to mix.nix. You could try to avoid these with git add -p, but considering that it is automatically generated by mix2nix, I suspect that they would be introduced in a future commit anyway.