Color highlighting comressed javascript

I was writting an script wich removes comments, enters and reduces the extra spaces to one space. When I opend the file, color highlighting stoped somewere in the middle.

My code is vallid following jslint. When i use an beautify extension, highlighting comes back for the whole file.
I am running windows 7 home primium with Brackets 1.1

This is a duplicate of #9007, though that was closed.  This is a performance-based limitation of CodeMirror when lines are more than 10,000 characters long.

@peterflynn
Thank you for your quick repley. I saw on the codemirror site that we can disable the 10,000 characters limitation and set it to infinnety. Maybe we can make an otion in the brackets.json file so that people with an high end computer can set the limitation to another value???
Sven

@svenvNL Notice though that Brackets isn't meant to edit minified files and it can cause strange problems.
It's usually better (both for you and the editor) to edit the development version of the file and then minimize it into the production file. You can do that using a grunt task, for example.

It's probably risky to make the character limit configurable -- usually things like that don't speed up with better hardware as much as you might expect, and then it still feels like a bug.  You could experiment with it by editing the source locally, though.
The best solution is to just fix the issue: make CodeMirror actually highlight long lines fully (just like it highlights long documents), which requires breaking the line processing (highlighting, layout, etc.) into sub-segments.  The CodeMirror maintainer, Marijn, has said this is complex enough that he's not going to do it unless someone specifically funds the effort.  It's a big-ticket item -- hence the 'move to backlog' label.

@peterflynn, @MarcelGerber thank you for your repley, as I read your answer, we can't make it work in Brackets directly, so I'm going to close this issue.


Resolver 2.0 unifying features when doing cargo build

Problem
I have a crate a that depends on crate b.
crate b has a feature flag test.
crate a has the following in Cargo.toml:
[package]
name = "cratea"
version = "0.1.0"
edition = "2021"

[dependencies]
crateb = { path = "../crateb "  }
[dev-dependencies]
crateb = { path = "../crateb ", features = ["tests"]  }

When I do cargo build with 2021 edition,  I expect crateb to be build without the feature tests but it looks like it is still unifying.
Is there a possible workaround?
Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
cargo 1.57.0 (b2e52d7ca 2021-10-21)
release: 1.57.0
commit-hash: b2e52d7cab0a286ee9fcc0c17510b1e72fcb53eb
commit-date: 2021-10-21
host: x86_64-unknown-linux-gnu
libgit2: 1.3.0 (sys:0.13.23 vendored)
libcurl: 7.79.1-DEV (sys:0.4.49+curl-7.79.1 vendored ssl:OpenSSL/1.1.1l)
os: Ubuntu 18.04 (bionic) [64-bit]

Can you provide a complete example, and run with cargo build -v and show the output?  There should not be any --cfg flags passed to crateb.

Thanks for the prompt reply. I found the issue.
I have a workspace, I had to specify the resolver=2 to my workspace and it worked.

Ah, glad it got figured out. I'm going to close this as a duplicate of #10112 then.


Reapply "[ovn-controller] Don't create ovn-controller if nicMappings"

This is the same patch that was merged a couple of days ago (seen on PR#1070).
This commit blocked adoption gates so it got reverted (on PR#1103), more
information about problem on the description.
Recreating PR to be able to test changes done in ovn-operator (PR#352) while
we fix the error uncover with this patch.
Depends-on: https://github.com/openstack-k8s-operators/ovn-operator/pull/352
https://github.com/openstack-k8s-operators/openstack-operator/pull/1070
https://github.com/openstack-k8s-operators/openstack-operator/pull/1103
https://github.com/openstack-k8s-operators/ovn-operator/pull/352

recheck

The patch is ok but we'll need to wait for the ovn-operator part to land first.

/retest-required

Kuttl tests failed with:
logger.go:42: 18:57:46 | ctlplane-tls-custom-issuers/7- | nova-internal.openstack-kuttl-tests.svc:8774 issued by , expected issuer=CN=rootca-internal
It seems a valid error but should not be affected by this patch, will recheck again to see if it was a one-time error (also on previous patches kuttl test didn't fail IIRC).
PS: Since ovn-operator patch was already merged, will try to run an adoption test to make sure it won't break (again) the gate.

/retest-required

FYI ctlplane-tls-custom-issuers is failing quite frequently and probably has nothing to do with your PR per se.

The latest run at https://review.rdoproject.org/r/c/testproject/+/54746 is green and confirms this PR no longer breaks adoption gate (after Arnau moved -config generation to OVNDbCluster controller).

This looks good for me and we should be good to go with it now

/lgtm

/approve

Again, ctlplane-tls-custom-issuers failed

/retest-required

/retest-required


repl server: close socket on shutdown

Calling..
rlpython.embed(bind='localhost:5000')

..multiple times (e.g. when done in a loop) fails with:
rlpython: ERROR: Address already in use

Close the socket on shutdown, so another embed() succeeds.

Great! Thanks for contributing :)


Two fixes for GithubNotifications

Handle errors when polling github API
Expose update() method

Fixes #317

2024-02-07 09:31:23,413 ERROR libqtile githubnotifications.py:_read_data():L148 Unable to connect to Github API.

This looks fine to me :) Thanks @elParaguayo!

I might put some better error handling here so we can check for specific errors. At the moment, this just swallows everything.

I might put some better error handling here so we can check for specific errors. At the moment, this just swallows everything.

I was thinking you might say that xD. Sure, whatever you think is best!

All merged now.


update latest tag to 2.3.2

Hey Alex,
Can you please update the lastest tag to be Magento 2.3.2?
Thank you!!

same problem here ...
@alexcheng1982  can you update the tag?
Thanks ...

Hey,
I do need some fixes from 2.3.2 aswell 👍

The commit is already done 4 month ago: https://github.com/alexcheng1982/docker-magento2/commit/85e91c11e13ba7365d9153352de0bb9fdcff47db
He just did not push the images to docker hub. 😢

/push


Webpack fails to compile after installing a new dependency

I had my webpack building but at some point something broke, and everytime i install a new dependency I get an error when I try to compile.

I tried installing the lib that webpack complains about but it will complain about another dependecy of a dependency i used to solve this issue nuking the node_modules folder and re installing but that doesn't work any more. Any ideas?

It looks like you just deleted/ignored our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.


Simplifies to use only one sidebar filter

Added docpad-plugin-raw
Removed black header
cleans up context

LGTM with hound nits


Readme images are returning 403 forbidden

@xaprb, can you upload the images here so I can hotlink in the README?


Update Facebook /me request for email and remove friend list permission

Facebook /me request need to be updated, and I don't think friend list is needed anymore since it now requires additional permission.

Not sure what makes you think the Facebook friend list isn't being used anymore. I believe we still use that to determine which profile images we show which users.

Because we did not request friend list permission on our current instance
and it seems like things go well hmmm.
Christopher Small<EMAIL_ADDRESS>於 2018年12月27日 週四 下午1:10寫道：

Not sure what makes you think the Facebook friend list isn't being used
anymore. I believe we still use that to determine which profile images we
show which users.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pol-is/polisClientAdmin/pull/20#issuecomment-450075718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQiPFhPCPBwn_euzxj5bNBjJNehTJM1ks5u9FZTgaJpZM4ZiU4i
.

--
Romulus Urakagi Ts'ai

Also discussed here: https://github.com/pol-is/polis-issues/issues/138#issuecomment-624345233
@urakagi are you aware that friend list is used to show people their friends in the visualization? It might not break without that data, but it would fail to have friend info when weighting participants and deciding which to show to a user.
Would you like the option to disable requesting this permission at the server-level, in order to request less personal information from users?

@patcon I would like to have an option to disable that since personal data is super sensitive in many countries, including Taiwan. The requiring permission action results in law issues, whether you really use the data or not.

Ok! Def makes sense to me to make this toggle-able in config. And might make sense to have clear guidance on enabling/disabling this in relation to GDPR.
Does that sound ok @metasoarous @colinmegill?

Yes, agree
On Wed, May 6, 2020, 11:48 PM Patrick Connolly<EMAIL_ADDRESS>wrote:

Ok! Def makes sense to me to make this toggle-able in config. And might
make sense to have clear guidance on enabling/disabling this in relation to
GDPR.
Does that sound ok @metasoarous https://github.com/metasoarous
@colinmegill https://github.com/colinmegill?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pol-is/polisClientAdmin/pull/20#issuecomment-625013030,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANQGGJVV3NLSH3AEKWYPPTRQIVQZANCNFSM4GMJJYRA
.

Closing this is favour of https://github.com/pol-is/polisServer/issues/77 (pls request re-open if desired!)


Rename binaries to strip '-alpha'

Checklist

[ ] make test-all (UNIX) passes. CI will also test this
[ ] unit and/or integration tests are included (if applicable)
[ ] documentation is changed or added (if applicable)

Description of change
As discussed in https://github.com/aelsabbahy/goss/pull/663#issuecomment-743127235; strip the -alpha naming, keep the messaging, keep the --use-alpha flag and env-var.
We're reasonably comfortable with the current situation - nothing seems to be horrendously broken in terms of the ported functionality as exercised by the added macOS & Windows integration tests, and based on Improbable's use (that I am intimately familiar with).
This change allows people to remove edge-cases from their installation, yet retains the clearly-set expectations of support being community-driven.
Fixes #651. Continues #663.

@aelsabbahy I think this is ready to review; I'm just waiting for linux CI to pass. I expect it to, but then, I always expect it to... ;-)

Awesome timing on this.. I'm really really hoping to have v4 released soon.

Quick eyeball check on this looks good.. plus CI passed.
Any idea why codeclimate didn't trigger? I assume none of your changes messed with that.
I'll wait for your answer on codeclimate and merge.. If you didn't change anything, don't worry about why it's not working.. just let me know and I'll merge anyways. =)

Quick eyeball check on this looks good.. plus CI passed.
Any idea why codeclimate didn't trigger? I assume none of your changes messed with that.
I'll wait for your answer on codeclimate and merge.. If you didn't change anything, don't worry about why it's not working.. just let me know and I'll merge anyways. =)

The only thing that springs to mind about codeclimate is maybe it's only configured to trigger against branches aimed at master, or only against branches aimed at protected branches?

The only thing that springs to mind about codeclimate is maybe it's only configured to trigger against branches aimed at master, or only against branches aimed at protected branches?

Yup, that's my guess too.. just wanted to check you didn't knowingly change anything to impact this.
Related note, I may get rid of codeclimate, or at least run it against the official Go codebase and see how many findings come up. If Official Go codebase fails, then I'm not interested in codeclimate. Also, need to actually have golint fail the build and fix all those findings.
Thanks for the PR, love the cleanups!


fix(command): missing PartialEq on CommandError

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

GitHub release
v0.4.8

Your semantic-release bot :package::rocket:


Having some issues using getImage()

Hello, I've been looking at trying to use this image selector for single image selections on Android, and I was having some troubles with getting an ImageSource object out of this plugin.
Using the following imports,
var imageSource = require('image-source');
var imagePickerModule = require("nativescript-imagepicker");

I have the following code which does not work. I can successfully select an image, but I can't seem to get the ImageSource object out of the function call. I have included some very basic alert calls with catch() statements to try to figure out what was going wrong. The first alert was to see what the result of context.present() was, and the JSON stringified result was
[{"_observers":{}, "disableNotifications":{},"_uri":{},"_thumbRequested":false}]

Next, I attempted to get the ImageSource from the first picture in the array using getImage(). However, the neither the then() function nor the catch() function (Error A) ran after getImage(). I did, however, get Error B to show up, although it did not have any error message associated with it.
context.authorize().then(function () {
            return context.present();
         })
         .then(function (pickedPictures) {
            var size = {
               maxWidth: 100,
               maxHeight: 100
            };
            alert("Stringified pictures: " + JSON.stringify(pickedPictures));
           //displays [{"_observers":{}, "disableNotifications":{},"_uri":{},"_thumbRequested":false}]

            return pickedPictures[0].getImage(size)
               .then(function (pickedPicture) {
                  alert('Success - '  + JSON.stringify(pickedPicture));
                  return self.set('picture', pickedPicture);
               })
               .catch(function (error) {
                  alert('Error A: ' + JSON.stringify(error));
                  //This catch function does not appear.
               });
         }).catch(function (error) {
            alert('Error B: ' + JSON.stringify(error));
           //This catch function does appear, showing:
          //Error B: {}
         });;

Is there something I am doing wrong with my implementation of this module?
@KallynGowdy as far as I can tell, it seems like the getImage() function is null in the pickedPictures[0] object. For example, if I replaced getImage() with something nonsensical like getRabbits(), I get the same scenario, where Error A doesn't appear but Error B appears.

@ckhordiasma Can you tell us which version is in your package.json? getImage() was only added in v0.0.5, and I have confirmed that getImage() is present on Android in that version.
Additionally, if you have the latest version, has the thumb property worked for you? Because the Android implementations between thumb and getImage() are almost identical.

@ckhordiasma
You dont need the return statement before pickedPicture[0].getImage()
For example this should work out for your scenario :
	context
		.authorize()
		.then(function() {
			return context.present();
		})
		.then(function(pickedPictures) {
			pickedPictures.forEach(function(selected) {
                console.log("----------------");
                console.log("uri: " + selected.uri);
                console.log("fileUri: " + selected.fileUri);

                selected
                    .getImage({ maxWidth: 100, maxHeight: 100})
                    .then(function(imageSource) {
                        console.log("Retrieved image: " + imageSource);
                        // use the image-source here
                    }).catch(function(e) {
                        console.log("Error: " + e);
                        console.log(e.stack);
                    });

		}).catch(function (e) {
			console.log(e);
		});

At the link below you will find a basic sample app demostrating how to use getImage()
https://github.com/NativeScript/sample-ImageUpload
Hope that will be useful - let me know if you need further assistance!

Hello, thanks @KallynGowdy and @NickIliev for your help! I was successfully able to get thumb earlier, but was hoping to use getImage() for more control over the size of the image received. Looking at versions, I was using the version from the telerik marketplace (v0.4), so I believe that is the issue.


verify succeeds for enveloped signature and fails for enveloping signature

I get OpenSSL.crypto.Error: [('rsa routines', 'int_rsa_verify', 'bad signature')] when I verify a SAML response signed with an enveloping signature and success when the same SAML response is signed with an enveloped signature.   This is with the current latest release, 2.9.0

Hello, thank you for your interest in SignXML. If you need help with an issue, please provide a full, self-contained reproduction of the issue that you are seeing, including a description of the expected and observed behavior.


Harmonise the use of ellipsis ("...") in the GUI

use it in context / main menus, but not on buttons
update some strings to be clearer / more informative

@PaycoinMaster No merge?

@mitchellcash I think he waited to merge this one cause I haven't commented on it yet (I haven't tester it yet either which is why)

I tested this i am bringing it in.


Flatten ops module?

It looks like I was late to comment on #616 so I figured I'd open a new issue to say that I disagree with the "operators"/"representations" dichotomy. At the very least, the naming is quite confusing, because a FermionOperator is a "representation" of a molecular Hamiltonian in the same sense that an InteractionOperator is a "representation". Both can represent the same operator, albeit using different underlying data structures. Besides, not everything in operators inherits from SymbolicOperator (e.g. MajoranaOperator) and not everything in representations inherits from PolynomialTensor (e.g. DiagonalCoulombHamiltonian), further muddying the waters. So I think we should flatten the module, at least until we come up with a more sensible distinction. @ncrubin @obriente

I agree that the naming is a bit confusing at first glance, but I think the distinction is clear. All the objects in 'operators' use a dictionary/hash table structure to store data, but all the operators in 'representations' store data in array form. The former allows for greater flexibility / representation power, but the latter allows for significantly faster manipulation (but is somewhat restricted in what one can represent easily).
I think this distinction between performance and representability is an important one to have going forward (especially as I'd hope one day to look at pushing much of representations into C for further increased performance), so I'd be inclined to keep the submodules. Not so sure about the names though. I had originally suggests 'ops' and 'sparseops', or 'ops' and 'sparse', but I do think that 'representations' is perhaps better than 'sparse' (the idea being that all you're actually storing is an array representation of the operator, the meaning is something you have to implant --- whereas the keys to the hash table contain this meaning to a large extent). I've never been particularly sold on any of them though, but I've also not found any good alternatives.

I disagree that a FermionOperator is a representation of a MolecularHamiltonian.  A molecular Hamiltonian is a particular element of a Fermionic algebra--i.e. things that can be built with FermionOperator.  MolecularHamiltonian contains information about the basis--integrals, mo_coeffs, that inform what the Hamiltonian will be but are not yet tied to ladder operators.  To tie them to ladder operators we need to go to spin-orbitals.  InteractionOperator contains this information which is an index map from spin-orbital index to coefficient.  The indexing in InteractionOperator corresponds to a particular ladder operator.  Therefore it encodes an efficient representation (for basis rotations and other things) of the Hamiltonian.
You are right that not everything in operators inherits from Symbolic. The thinking here was these are base algebra objects for different types of algebras.
Same argument for representations.  PolynomialTensor was an efficient way to store a particular algebra element (that is the sum of a bunch of algebra "monomials").  The idea of things in representation is that objects that do the job of storage and mapping live here.  Thus DiagonalCoulombHamiltonian serves this purpose for a particular collection of fermionic operators.
As for naming, we're always open to suggestions.  representations seemed to fit...but I agree there is potential for improvement.

Looking at the definition of 'representation' in math - https://en.wikipedia.org/wiki/Representation_theory - a representation is a map from an abstract algebra to a set of matrices on a vector space. This maps pretty well to the current distinction, so on retrospection I'm pretty happy with the distinction. Could go with 'abstract' vs 'representation' if we wanted to make the distinction clear, perhaps?

By FermionOperators and InteractionOperators being representations "in the same sense" I simply meant that
FermionOperator('[0^ 1] + [1^ 0]')

and the InteractionOperator with one-body tensor equal to
[[0.0, 1.0]
 [1.0, 0.0]]

both represent the exact same operator, a_0^\dagger a_1 + a_1^\dagger a_0.
If the distinction is that one class of operators is represented using arrays, then I think we can come up with a better name; I don't find the analogy with representation theory very compelling, since these arrays aren't matrices in the usual sense (they can have more than two dimensions, and we don't think of the arrays themselves as linear maps, rather, the represented operator is the linear map). Also note that "sparse ops" would not be accurate to describe the array representations, since the symbolic representations are actually more sparse (the array representations store a bunch of empty array entries).

You are right they represent the same object.  That is my starting point as well.  The InterationOperator representation you have shown imbues a matrix indexing to represent a particular set of FermionOperators.   This format allows for transformations on the operators that get mapped to linear algebra operations on the InteractionOperator or InteractionRDM matrix--i.e wedge, basis transformation, contraction, etc.  you can do the same thing in FermionOperator but the code would be inefficient and you would probably end up implementing an InteractionRDM or InteractionOperator!    You can formally evaluate the energy of a Hamiltonian if I give you a bunch of fermionOperators and another list of the expected values.  But why not have a container that naturally represents these ideas while leaving the algebra manipulation component (which is simpler with FermionOperator and not uniquely defined with InteractionOperator) to the SymbolicOp like objects? I didn't want to use the name containers since that is also a loaded term.  We are open to suggestions on the names of course.

@kevinsung did you have further thoughts on this?

As you agreed, a FermionOperator and an InteractionOperator can both represent the exact same operator, with the only difference being in the underlying data structure. If we are to separate these classes, we should use names that reflect the difference. After all, both are "operators" and both are "representations," so "operator"/"representation" doesn't make sense to me. Perhaps we could use the names "dict" and "array" instead.

I disagree with the conclusion you come to.  FermionOperator is a generalization of InteractionOperator so I still think the name representation is okay. You can do some things to InteractionOperator that you can't to FermionOperator.  That's the price you pay for generalization/abstraction.  "dict" and "array" seem worse, to me, since those are key words and don't carry any meaning with respect to quantum mechanics.

"dict" and "array" seem worse, to me, since those are key words and don't carry any meaning with respect to quantum mechanics.

In the language of quantum mechanics, an InteractionOperator is an "operator" just as much as a FermionOperator is an "operator." I don't think the word "representation" as it's being used here has a meaning in quantum mechanics.

dict is a keyword in python.  we can't use that!  as is array for numpy which we rely on heavily.  Do you have an alternative pair of names to suggest?

How about 'symbolic' and 'sparse'? In the SymbolicOperator and derived classes we are writing down a symbolic form of the operators (quite literally), and I'd say that PolynomialTensor derived classes are supposed to be 2^Nx2^N operators in sparse representations that allow for fast calculations (in the same way that the sparse libraries in scipy allow for faster linear algebra).

@obriente As I pointed out above, the symbolic representations are actually sparser than the array representations, since the arrays contain many zero entries. These arrays are dense Numpy arrays, not Scipy sparse matrices. So if anything, the symbolic representations should be called "sparse."

Maybe we could call them "symbolic" and "dense."

Or maybe just "sparse" (referring to the symbolic operators) and "dense" (for the dense array operators).

There's a pretty strong connection in my mind between 'sparse' and 'optimized for fast calculation', so I would find this definition very confusing. I also definitely wouldn't say 'dense' for the PolynomialTensor class - they're not 2^Nx2^N after all.
How about 'symbolic' and 'tensor' ? That's pretty unambiguous, no?

I'm okay with "symbolic" and "tensor".

closing since inactive


iOS Chrome 119 Beta: When exiting an AR QuickLook session the originating HTML page view is broken

Description
When exiting an AR QuickLook session, the originating HTML page is scrolled back to the top of the page, and the entire viewport is shifted down the screen making it look broken.
When using inspection tools, it appears that the entire HTML element has been shifted down the screen.
This used to work fine in previous versions where web page would not be scrolled and viewport would not be moved.
Chromium Bug Reported:
https://bugs.chromium.org/p/chromium/issues/detail?id=1502773
Live Demo
https://modelviewer.dev/examples/augmentedreality/index.html#ar
Repro steps:

In iOS Chrome, view above link
Tap AR button to open astronaut in ARQL
Exit the ARQL session
Observe, the HTML page has scrolled back to the top and the entire viewport has shifted down

Similar experience when viewing non Model-Viewer ARQL content. For example, viewing any 3D model from:
https://developer.apple.com/augmented-reality/quick-look/

Version

model-viewer: 3.3.0 (any?)

Browser Affected

[x] Chrome, version: 119.0.6045.24 beta
[ ] Edge
[ ] Firefox
[ ] IE
[ ] Safari

OS

[ ] Android
[x] iOS, version: 17.2 Beta 3 (21C5046c)
[ ] Linux
[ ] MacOS
[ ] Windows

AR

[ ] WebXR
[ ] SceneViewer
[x] QuickLook

Screenshots
Before ARQL:

After ARQL:

So this is specific to iOS Chrome, and doesn't repro on Safari? Would you mind filing a bug on Chromium?

So this is specific to iOS Chrome, and doesn't repro on Safari?

Correct. Does not repro in Safari iOS.
I thought it may be a WKWebView issue, but it does not repro in Firefox or DuckDuckGo, which would also be using WKWebView. So it appears to be specific to iOS Chrome.

Partially fixed in iOS Chrome 123.
Viewport no longer shifted down page.
But, page is still scrolled back to top.


[Install] [Agent] client and server don't have same version (client : 1.16, server: 1.15)

Command to register node - node
docker run --rm -it --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent http://MANAGMENT_IP:8080/v1/scripts/FROM_RANCHER_SERVER
also tried:
docker run --rm -it --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent http://MANAGMENT_IP:8080
Error - node
8d2c89aad98e: Download complete
Status: Downloaded newer image for rancher/agent:latest
time="2015-01-29T18:25:05Z" level="fatal" msg="Error response from daemon: client and server don't have same version (client : 1.16, server: 1.15)"
Please ensure Host Docker version is >= 1.4.1 and container has r/w permissions to docker.sock
docker version - server
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8
docker info - server
Containers: 1
Images: 14
Storage Driver: devicemapper
Pool Name: docker-202:1-152213-pool
Pool Blocksize: 65.54 kB
Data file: /var/lib/docker/devicemapper/devicemapper/data
Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
Data Space Used: 730 MB
Data Space Total: 107.4 GB
Metadata Space Used: 1.364 MB
Metadata Space Total: 2.147 GB
Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 3.13.0-36-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 1
Total Memory: 1.954 GiB
Name: ip-10-0-0-70
ID: DEHI:VRO4:JOYE:ZNUS:C7FM:4W6Y:ENYV:Q7LX:IUIU:VHIA:7XJR:EH6K
WARNING: No swap limit support

@brycekottke We've updated the command for registering docker nodes (per https://github.com/rancherio/rancher/issues/267). Please try that and see if you have any issues. If so, please re-open.


"could not read quota" error messages

Describe the bug
When starting oCIS from single binary the first time it clutters the console with error messages like
{"level":"error","service":"storage-users","pkg":"rgrpc","traceid":"00000000000000000000000000000000","error":"no data available","nodepath":"/data/ocis/base/storage/users/spaces/4c/510ada-c86b-4815-8820-42cdf82c3d51/nodes/4c/51/0a/da/-c86b-4815-8820-42cdf82c3d51","time":"2022-11-24T18:08:28.983827677+01:00","message":"could not read quota"}

a lot.
This is probably a pretty useless logging as this is expected.
It gives a bad impression to first-time starters I think, especially with the "no data available" part.
Expected behavior
Just do not print this error message. Maybe make it a warning or debug level.

This is interesting. Is this happening on your linux desktop?

Linux ocishc4 5.15.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.15.51-202207010153~jammy (2022-06-30) aarch64 aarch64 aarch64 GNU/Linux with ext4 file system.
The entire data directory was cleaned before.
Let's fix that - msg "No data available" does not make people trust ;-)

There are some problems with the xattr upsream package on several linux distros. That is why I asked. Specially the "no data available" error comes from the syscall itself.

more logs:
{"level":"error","service":"storage-users","pkg":"rgrpc","traceid":"00000000000000000000000000000000","node":"marshaling error: json: unsupported value: encountered a cycle via *node.Node","node":"marshaling error: json: unsupported value: encountered a cycle via *node.Node","error":"xattr.Remove /data/ocis/base/storage/users/spaces/4c/510ada-c86b-4815-8820-42cdf82c3d51/nodes/4c/51/0a/da/-c86b-4815-8820-42cdf82c3d51 user.ocis.tmp.etag: no data available","time":"2022-11-25T15:24:19.031502314+01:00","message":"could not remove temporary etag attribute"}

more logs:
{"level":"error","service":"storage-users","pkg":"rgrpc","traceid":"00000000000000000000000000000000","node":"marshaling error: json: unsupported value: encountered a cycle via *node.Node","node":"marshaling error: json: unsupported value: encountered a cycle via *node.Node","error":"xattr.Remove /data/ocis/base/storage/users/spaces/4c/510ada-c86b-4815-8820-42cdf82c3d51/nodes/4c/51/0a/da/-c86b-4815-8820-42cdf82c3d51 user.ocis.tmp.etag: no data available","time":"2022-11-25T15:24:19.031502314+01:00","message":"could not remove temporary etag attribute"}

this one is no longer logged in ocis master ...

@dragotin can you recheck with latest master? I did fix a case where we would not return a wrapped error from the cache that would be identified as an IsNoAttr error with https://github.com/cs3org/reva/pull/3482/files#diff-ef948094e548663d1c93409d04b79a775bc8a199488302705a5630bf110ab4f6R106 It is part of the Decomposedfs propagate diff


Setting a limit value param that is greater than the total record count result in an error

Error: No value defined: {}
Fix: https://github.com/sensedeep/dynamodb-onetable/pull/25

For the record. Can you give a few more details to capture this issue more fully?

sure...
const items: Paged<UserMessage[]> = await UserMessageModel.find(
   { userId: 'abc' }, { limit: 5, metrics: {} }
)

if I user abc only has 2 messages but I set the limit to 5, I get the error.
if I user abc has 5 or more messages and I set the limit to 5,  it works fine.
I believe the unmarshall fails when the value of the LastEvaluatedKey is {}

Thanks, appreciated.
Pull request applied and released.

👍


[MRG] MAINT: move neuron -> neuron_network

@blakecaldwell I was having trouble doing import of "from neuron import h" in the same folder as hnn_core because there was this file with the same name. I think this name is clearer and avoids this problem. Let me know what you think.

Sure. Rename to NetworkBuilder in this PR? I can do that if you want.

yeah I can do that too

discovered the problem in #150

okay I think I'm done here. Please feel free to merge once CIs come green.

okay I'm gonna self-merge since it's a pretty straightforward PR and got one review. Feel free to complain @rythorpe if you see anything amiss, I can fix it later too

thanks for the reviews @blakecaldwell


Lint upstream as a normal unit test

This removes the last job in extraTests by making it a standard unit test.
Currently the job runs without caching and takes upwards of 30-40 minutes because it re-compiles everything from scratch. This makes it the long poll when sharding is turned on.
By running with the rest of our tests it can benefit from caching. Locally the test takes only ~20s.
This is run during unit tests, which still take about ~5 minutes before and after this change. They're actually slightly faster because I parallelized some of them while I was in here.

Assuming the upstream waf tests are unrelated.


client.bin

There is no client.bin file and i cant figure out how to get it so it will not run

build Release Quasar.Server , you can get the 'Quasar.exe'
build Release Quasar.Client , you can get the 'client.bin'

you can use the release version here
https://github.com/quasar/QuasarRAT/releases

There is no client.bin file and i cant figure out how to get it so it will not run


New feature: add login with google option

Please assign me the task to add login/signup option with google option via choosing google account.

Go ahead @bhaskarkumar1 , make sure to fetch the repo before making a PR

thank you @AtriSukul1508, for asssigning this task  I will work  on it.

@bhaskarkumar1 what's the update?

anyone not working on this issue please assign me this issue i want to work in this issue

@AtriSukul1508 ,please assign it to me.I will update you on my progress every 2weeks.I already created an issue on it,#170.Here is the link,https://github.com/AtriSukul1508/Njack_Hack_It_Out-Tur1ng-/issues/170


Module ignored/skipped if EntityFramework enum with default value is used in method

I made a repo showing the error: https://github.com/Harvzor/coverlet-enum-test
How to reproduce:

clone https://github.com/Harvzor/coverlet-enum-test
run dotnet build
run coverlet ./Tests/bin/Debug/netcoreapp2.1/Tests.dll --target "dotnet" --targetargs "test ./Tests/Tests.csproj --no-build" --format opencover

Expected output:
+--------+--------+--------+--------+
| Module | Line   | Branch | Method |
+--------+--------+--------+--------+
| Source | 0%     | 100%   | 0%     |
+--------+--------+--------+--------+

+---------+--------+--------+--------+
|         | Line   | Branch | Method |
+---------+--------+--------+--------+
| Total   | 0%     | 100%   | 0%     |
+---------+--------+--------+--------+
| Average | 0%     | 100%   | 0%     |
+---------+--------+--------+--------+

Actual output:
+--------+--------+--------+--------+
| Module | Line   | Branch | Method |
+--------+--------+--------+--------+

+---------+--------+--------+--------+
|         | Line   | Branch | Method |
+---------+--------+--------+--------+
| Total   | 100%   | 100%   | 100%   |
+---------+--------+--------+--------+
| Average | ∞%     | ∞%     | ∞%     |
+---------+--------+--------+--------+

In the actual input, there's no module! No warnings are shown.
The issue appears because of this code:
public void SimpleMethod(EntityState entityState = EntityState.Added)
{

}

If the entityState var does not have a default value, then everything works as expected:
public void SimpleMethod(EntityState entityState)
{

}

Versions
coverlet: <IP_ADDRESS>
dotnet: 2.1.505

Can you try with last version 1.5.2 https://www.nuget.org/packages/coverlet.console/?

Updated my dotnet version to 2.2 and updated coverlet to 1.5.2, I'm getting a useful message from the report now:
λ coverlet ./Tests/bin/Debug/netcoreapp2.1/Tests.dll --target "dotnet" --targetargs "test ./Tests/Tests.csproj --no-build" --format opencover
Unable to instrument module: .\Tests\bin\Debug\netcoreapp2.1\Source.dll because : Failed to resolve assembly: 'Microsoft.EntityFrameworkCore, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'

Calculating coverage result...
  Generating report 'D:\Dev\Code\coverlet-enum-test\coverage.opencover.xml'
+--------+------+--------+--------+
| Module | Line | Branch | Method |
+--------+------+--------+--------+

+---------+------+--------+--------+
|         | Line | Branch | Method |
+---------+------+--------+--------+
| Total   | 100% | 100%   | 100%   |
+---------+------+--------+--------+
| Average | ∞%   | ∞%     | ∞%     |
+---------+------+--------+--------+

The issue looks related to https://github.com/tonerdo/coverlet/issues/21.

@Harvzor I found the issue...at the moment Cecil resolver does not search on "nuget package" cache.
Update you test project with <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp2.1</TargetFramework>
    <IsPackable>false</IsPackable>
    <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.EntityFrameworkCore" Version="2.1.11" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\Source\Source.csproj" />
  </ItemGroup>

</Project>

So Microsoft.EntityFrameworkCore libs will be copied in output folder and correctly loaded by cecil(we add "test lib path" as probing path).
I advice to exclude also microsoft/xunit lib from instrumentation
C:\git\coverlet-enum-test (master -> origin)
λ coverlet ./Tests/bin/Debug/netcoreapp2.1/Tests.dll --target "dotnet" --targetargs "test ./Tests/Tests.csproj --no-build" --format opencover  --verbosity detailed --exclude [Microsoft*]* --exclude [xunit*]*
Excluded module filter '[Microsoft*]*'
Excluded module filter '[xunit*]*'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.EntityFrameworkCore.Abstractions.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.EntityFrameworkCore.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Caching.Abstractions.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Caching.Memory.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Configuration.Abstractions.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Configuration.Binder.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Configuration.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.DependencyInjection.Abstractions.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.DependencyInjection.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Logging.Abstractions.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Logging.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Options.dll'
Excluded module: '.\Tests\bin\Debug\netcoreapp2.1\Microsoft.Extensions.Primitives.dll'
Instrumented module: '.\Tests\bin\Debug\netcoreapp2.1\Source.dll'

Calculating coverage result...
Hits file:'C:\Users\Marco\AppData\Local\Temp\Source_9abb458b-019a-4a50-8399-14eab4bf251f' not found for module: 'Source'
  Generating report 'C:\git\coverlet-enum-test\coverage.opencover.xml'
+--------+------+--------+--------+
| Module | Line | Branch | Method |
+--------+------+--------+--------+
| Source | 0%   | 100%   | 0%     |
+--------+------+--------+--------+

+---------+------+--------+--------+
|         | Line | Branch | Method |
+---------+------+--------+--------+
| Total   | 0%   | 100%   | 0%     |
+---------+------+--------+--------+
| Average | 0%   | 100%   | 0%     |
+---------+------+--------+--------+

No coverlet correctly tell you that coverage file for Source.dll lib isn't found because you don't have any test so no code has got covered.
Let me know if we can close this.

Thanks I can confirm that adding <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies> worked:
https://github.com/Harvzor/coverlet-enum-test/commit/64e6d2beecb27826936da7786409906a87e1c6e3
Thanks for the extra advice too!


Issue-13-Create-Table-of-Content-component

Description
This PR adds a Table of Content component.
Fixes Issue
Closes #13
Acceptance Criteria

[x] Create an accessible open/close widget (maybe using details/summary tag).
[x] Use dummy text, like title, heading 1, heading 2, heading 3, ...
[x] The widget should be visible on the right side of the page.
[x] Create a dummy content page with headings and paragraphs.
[x] When clicking on a heading in the widget it should bring me to the section of the page.
[x] Use only essential CSS, focusing primarily on functionality.

Type of Changes
:sparkles: New feature
Before
After

Testing Steps / QA Criteria

Wow, amazing work done here, @Chizycodes 😮 Thank you for contributing to the project 🚀


xxhash

does the mod use xxhash? I noticed an improvement when installing the library.

No, I had not even heard of xxhash before. Since it seems to be a file hashing library and FC does not do anything related to file hashing, I do not see how they would be related. Installing the library system-wide should certainly not affect FC behavior.


ICGCtoMAF error

Appears writing the esad data to maf forms an incorrect file, the script is below.
esad.maf <- icgcSimpleMutationToMAF(icgc = "/home/*****/ICGC/simple_somatic_mutation.open.ESAD-UK.tsv", MAFobj = TRUE)                                                                                |--------------------------------------------------|

==================================================

==================================================

--Removed 30371749 duplicated variants

--Found  7229646  variants with no Gene Symbols

--Annotating them as 'UnknownGene' for convenience

--Non MAF specific values in Variant_Classification column:

NA

--Non MAF specific values in Variant_Type column:

NA

Summarizing..

-Processing clinical data

--Missing clinical data

read.maf(esad.maf)
-Reading
Error in file.info(file) : invalid filename argument

Hi,
Sorry for the delay in responding. icgcSimpleMutationToMAF with MAFobj = TRUE will already return the data as an MAF object. You don't have to read it again with read.maf.

Hi,
Sorry for the delay in responding. icgcSimpleMutationToMAF with MAFobj = TRUE will already return the data as an MAF object. You don't have to read it again with read.maf.

Hi Poison, the issue is that I've had to do this work on a supercomputer as the icgc esad tsv is 15gb, I'm looking for a way to export the maf so I can process it on my work PC.

Hi Poison, the issue is that I've had to do this work on a supercomputer as the icgc esad tsv is 15gb, I'm looking for a way to export the maf so I can process it on my work PC.

Hi,
In that case you could try to get rid of unwanted columns which should reduce the object size significantly.
Example on a 1M rows of your ESAD file
#zcat simple_somatic_mutation.open.ESAD-UK.tsv.gz | head -n 1000000 > simple_somatic_mutation.open.ESAD-UK_1Mentries.tsv

> ic = maftools::icgcSimpleMutationToMAF(
  icgc = "~/Downloads/simple_somatic_mutation.open.ESAD-UK_1Mentries.tsv",
  removeDuplicatedVariants = F,
  addHugoSymbol = T
)

> print(object.size(ic), units = 'Mb')
3352.8 Mb

#Keep only required fields
> ic_min = ic[, .(
  Hugo_Symbol,
  Chromosome,
  Start_Position,
  End_Position,
  Reference_Allele,
  Tumor_Seq_Allele2,
  Tumor_Sample_Barcode,
  Variant_Classification,
  Variant_Type,
  aa_mutation
)]

> print(object.size(ic_min), units = 'Mb') #From 3.35G to 729M
729.5 Mb

> ic_m = read.maf(maf = ic, removeDuplicatedVariants = F) #Convert to MAF
> print(object.size(ic_min), units = 'Mb')
729.5 Mb

Hi,
In that case you could try to get rid of unwanted columns which should reduce the object size significantly.
Example on a 1M rows of your ESAD file
#zcat simple_somatic_mutation.open.ESAD-UK.tsv.gz | head -n 1000000 > simple_somatic_mutation.open.ESAD-UK_1Mentries.tsv

> ic = maftools::icgcSimpleMutationToMAF(
  icgc = "~/Downloads/simple_somatic_mutation.open.ESAD-UK_1Mentries.tsv",
  removeDuplicatedVariants = F,
  addHugoSymbol = T
)

> print(object.size(ic), units = 'Mb')
3352.8 Mb

#Keep only required fields
> ic_min = ic[, .(
  Hugo_Symbol,
  Chromosome,
  Start_Position,
  End_Position,
  Reference_Allele,
  Tumor_Seq_Allele2,
  Tumor_Sample_Barcode,
  Variant_Classification,
  Variant_Type,
  aa_mutation
)]

> print(object.size(ic_min), units = 'Mb') #From 3.35G to 729M
729.5 Mb

> ic_m = read.maf(maf = ic, removeDuplicatedVariants = F) #Convert to MAF
> print(object.size(ic_min), units = 'Mb')
729.5 Mb


ion-input nested within ion-item doesn't respect --padding-end

Bug Report
Ionic version:
[x] 4.x
Current behavior:
Creating a floating label ion-input and adding this style
ion-item {
  --padding-start: 0px;
  --padding-end: 0px;
}

or this one
ion-item {
    --padding-start: 0px;
    ion-input {
      --padding-end: 0px;
    }
}

will results in changing only the "start" side.
Expected behavior:
Both padding should follow the padding variable setted
Steps to reproduce:
Add a simple IonInput component:
<ion-item>
  <ion-label position="fixed">Floating Label</ion-label>
  <ion-input></ion-input>
</ion-item>

with the following CSS:
ion-item {
    --padding-start: 0px;
    --padding-end: 0px;
}

Other information:
Ionic info:
Ionic:
   ionic (Ionic CLI)             : 4.10.2
   Ionic Framework               : @ionic/angular 4.0.1
   @angular-devkit/build-angular : 0.12.4
   @angular-devkit/schematics    : 7.2.4
   @angular/cli                  : 7.2.4
   @ionic/angular-toolkit        : 1.3.0

System:
   NodeJS : v10.15.0
   npm    : 6.4.1
   OS     : Linux 4.18

Thanks for the issue! Item is structured in the following way:
<ion-item>
  <slot name="start"></slot>

      <slot></slot>

    <slot name="end"></slot>

</ion-item>

So when you are styling --padding-start and --padding-end you are changing the padding on the host element ion-item. I believe the padding you are seeing is coming from the default padding on the .item-inner which allows us to pad the items in the end slot without losing the bottom border that stretches all of the way to the right.
What you're looking for is the following:
ion-item {
  --padding-start: 0;

  --inner-padding-end: 0;
}

See the CSS Custom properties for item here: https://ionicframework.com/docs/api/item#css-custom-properties

Thank you and sorry for the useless issue, I already found it lookin at the inspector but this should be better documented because I was looking at the ion-input page where there is no reference to the ion-item. It wasn't neither logical to think that, looking at a document page I need to look in another page to fully access all the options of those component without reference.

@Takkuz Thanks for the suggestion! Please open an issue on our ionic-docs repository with any ideas for how we can improve the documentation. 🙂

@brandyscarney
Hi! Sorry to jump on the end of this conversation. I've been messing with ionic for a few days and I'm still learning styling using a shadow dom so please forgive me if I'm missing something obvious. After digging into the repository I've found where the original styling for the ion-item is set (core/src/components/item/). As shown below, ionic adds a start padding and then an inner end padding, however it doesn't have complementing end padding and inner start padding to default centering items.
core/src/components/item/item.ios.scss
 --padding-end: #{$item-ios-padding-end};
 --inner-padding-start: #{$item-ios-padding-start / 2};

I wish I had seen this thread before I dug so far into this as your suggestion below would have solved my problem.
variable.scss
ion-item {
  --padding-start: 0;
  --inner-padding-end: 0;
}

Just to test, I followed the same pattern and imported the css variables into my variables.scss and used this to see what happens and it centers and is padded perfectly. I'm just curious as to why this isn't the default behavior for ion-items? (Or vice-versa to force user to set )
Default Padded Solution In variable.scss
ion-item {
    --padding-start: #{$item-ios-padding-start};
    --inner-padding-end: #{$item-ios-padding-end / 2};
    --padding-end: #{$item-ios-padding-end};
    --inner-padding-start: #{$item-ios-padding-start / 2};
}

Thank you very much for your time and great work to the whole team, so far Ionic is awesome!

Hi @KGMaxey! No worries. I understand it's a bit confusing without seeing the structure or inspecting the element, which is complex because of shadow DOM. We really do want to make this better documented and as easy to use as possible.
So I am not sure that I 100% understand your question so please correct me if I'm misunderstanding, but using your CSS gives me the following item:

Notice how the line on the right doesn't extend to the edge of the screen? The reason is because the border for an item with inset lines is actually applied on the inner item div and not the host ion-item. This is a problem because we need to be able to pad the border on the left to account for any elements in the start slot and not be under those, while remaining extended to the edge on the right.
Basically the problem is that in order to provide the inset lines and match the spec, we need to be able to have inner padding on the left, but we don't want the content to be on the right edge of the screen so we add some padding on the host element. Here's an example of the MD spec so you can better see what I mean (notice the divider lines):

We try to follow the iOS and MD spec as much as possible out of the box, but still allow for customizations if desired.
Please let me know if you have questions, thank you!


Setup bronbro.io autodeploy

setup ws hook at repo and re-deploy at hosting node for landing
https://github.com/adnanh/webhook

Autodeploy added. Waiting for changes to ensure it works properly.

Git pull should be used instead of fetch.
Website has been updated automatically.


feat: better popup ui closes #1

I have added a UI button for dismiss action, so when we add that feature we can just hook it up. #1
The "Check it out" button does not take you anywhere at the moment as the schema does not have link stored separately (the reason for Issue #9 ). If this is not needed, I can remove it.
Preview:

It might be better to have a design where we can show multiple alternatives for a service?

Yes, I thought about it. It can always be added later on if needed :)
My main concern is that having a SINGLE CTA ("recommended alternative") reduces friction for the user. When presented with multiple alternatives, I almost always end up with neither and stick to my existing way of life (the paradox of choice maybe?).

That is fair, having a single CTA definitely reduces friction.
My only concern is that the schema currently allows multiple alternatives, and so showing only one (the first match) just feels a bit weird.
But before we update the UI to account for this, we should decide on the schema (#9) and if we want to show multiple alternatives. But this looks like a good start!

Based on the discussions in #1 and #9
I've made the schema changes, and updated the UI. It now looks like this:

I've made the schema changes in this PR itself, and the code is kind of a spaghetti but it works! We can always improve it later on?


Presentation: 'START button does not work

For now, you can make a simple replacement with HTML button and I can try to figure out a reason

closed with #02c4898


DForce need a Fantom subgraph

We are missing a DForce Fantom subgraph. There is also the Kava network, but that is not supported by the graph.

@dmelotik we can backlog this till after all the rewards are done

Actually it is not supported on DForce's dapp. I think it should be turned off since we don't even get data for it form defillama


Handle JSON encoding Pydantic UndefinedType

Fixes #9920.
Pydantic recently added new field input to the validation error details. The FastAPI JSON encoder wasn't able to encode the input field when the value was PydanticUndefined, such as the case shown in #9920.
Fix is to encode PydanticUndefined values as None.

Thanks @arjwilliams! I would love to get that fix!

Great, thank you @arjwilliams! :rocket:
I added a couple of extra tests for that specific use case from the issue. :nerd_face:
Thanks all for the feedback and conversation here everyone! :coffee:
This will be available in FastAPI version 0.110.2 in the next few hours. :rocket:


Logistic normalization for S1 Metric

After the discussion today and seeing the examples @iebert was sharing, I am thinking it may be worth removing the logistic normalization that is the final step in computing $S_1$.
As a reminder from the paper, S1 is computed by:

Computing the power spectrum
Taking the log-log transformation of that spectrum
Computing the line of best fit and its slope
Returning the negative of that slope, $\alpha$

In the paper, this is followed by a logistic-type curve, where the actual value returned by $S_1$ is given by
S_1 = 1 - \frac{1}{1 + e^{-3(\alpha - 2)}}.

This transformation is specifically tuned so that all "blurry" images (as $\alpha$ increases) collapse to values of S1 near 0, as shown in Figure 1 of the Vu et al. paper:

My feeling is that because we are looking at satellite information, this final processing step is actually obscuring information that we'd want to keep, so my suggestion is that we just return $\alpha$ instead of the processed $S_1$.
I wanted to put this up here to gather feedback before I change the way $S_1$ works, as this would dramatically change the values returned.

After some off-line discussions, the plan is as follows: $S_1$ will have its normalization removed, and we will now return the true slope of the line of best fit rather than its negative; this will mean that $S_1$ will return negative values, but that larger (i.e., closer to 0) values will indicate a sharper image, which is more consistent with the other metrics we're using.

Made these changes as of commit c309b30ff4e3543bbdf60114bfa8a8c6ddcd1b31. Closing for now.


xDisk module is missing

We need to add missing module from https://gallery.technet.microsoft.com/scriptcenter/xDisk-Module-PowerShell-6b7870ed and double check that all modules are present.

Fixed per #4


Change Versions to the latest Bootstrap since now

I've changed versions to the latest Bootstrap till now.
Also this

site/assets/js/src/search.js

was showing instead of this

site/static/docs/4.4/assets/js/src/search.js

Thanks, but this is taken care of in #29925


Flag Evaluation Lifecycle: An Extensibility Proposal

There's been a few questions and thoughts around integrations and extensibility, especially around telemetry, visibility, custom parsing, validation, and logging. OpenTelemetry support, for instance has been a goal from the start. To maintain flexibility, and keep our API dependencies as low as possible (preferably none) I propose a model for extensibility that defines a "life-cycle" for feature flag evaluation, and exposes life-cycle "hooks" for the purposes of extensibility and customization.
"Hooks" might be classes/functions that implement a SDK-defined interface, perform arbitrary logic at well-defined points during flag evaluation, which can be "registered" by the first party feature flag API consumer. For example, Open Telemetry implementation might look something like this, in psuedocode:
class OpenTelemetryHook implements OpenFeatureHook {

private Tracer tracer;

...

  before(Context context, FlagId flagId): Context {
    // optionally handle actions to do before the flag value is retrieved in this life-cycle hook, such as initializing traces/logging.
    // this might not be the API we want, we want to consider the risk associated with mutating the context
    context.span = tracer.startSpan(flagId);
    return context;
  }

  after(Context context, FlagId flagId, FlagValue flagValue): FlagValue {
    // optionally handle actions to do after the flag value is retrieved in this life-cycle hook, such as parsing, validation, etc.
    // this could be a good place for custom parsing of the flag response, validation, etc
    context.span.end();
    return FlagValue;
  }
}

  error (Context context, FlagId flagId, Error err) {
    // optionally handle errors with flag resolution in this life-cycle hook.
  }

}

Then, in the OpenFeature API, the first party application author would register this hook (note: they did not WRITE the OpenTelemetryHook, they are just consuming it and adding it to the flag evaluation life-cycle):
openFeatureClient.registerHook([ new OpenTelemetryHook() ]);

When the flag is evaluated, the API internals might run the defined hooks within the context of that flag evaluation:
class OpenFeatureClient {

  private Provider provider;

  getFlagValue(FlagId flagId, Context context) {

    // perform "before" life-cycle hooks
    Context mergedContext = this.hooks.reduce((accumulated, hook) => merge(accumulated, hook.before(context, flagId)));
}

    // call the provider abstraction to actually get the feature flag value
    var flagValue = this.provider.getFlagValue(flagId, context);

    // perform "after" lifecycle hooks
    flagValue = this.hooks.reduce((accumulated, hook) => hook.after(context, flagId, accumulated)));
    this.hooks.each(hook => hook.after(context, flagId, flagValue));

    return flagValue;
  }
}

I think that an optional configuration object with optional before and after callbacks having the same method signature, could also be added to feature flag evaluation calls, so that we could implement hooks on a per-flag basis as well:
getFlagValue('my-flag', context, { before: (Context context, FlagId flagId) => { // do stuff } })

Considerations like thread-safety, mutability of objects, sync vs async, and error handling as well as the overall API should all be carefully considered here.

I think this makes lots of sense. The only thing that comes to mind that you might have missed here is that in a version of implementation where we have a local cache of the rules that are evaluated, having some hook for when the rules update may be interesting. Like, I would certainly want to log that it happened and maybe emit some relevant metrics.
Just thinking through examples of things I might want to use to do extensibility, I didn't come up with much aside from what's listed above.

observability (tracing/logging/metrics)
packing the context with properties (environment, data center, etc)

The only thing that comes to mind that you might have missed here is that in a version of implementation where we have a local cache of the rules that are evaluated

Excellent point. One thing I'm not sure of is how much of that concern we want to expose to the 1st party consumer, and how much should be abstracted by the provider. It seems like in some recent discussions, it's been made clear that having control and visibility over fetching locally cached values versus forcing a pull from the server might be useful. Do you have any ideas with regards how we might want that to look to the application author?

having some hook for when the rules update may be interesting.

I agree this isimportant. I dont know if it's part of the flag evaluation life-cycle perise. I wonder if it would make sense to also have some events available on the client that callbacks could be registered to. This way, arbitrary logic could be applied when the fetch happens, which might be totally independent of a flag evaluation (polling).

I like this.
One addition I would suggest is a good for when the SDK is ready to operate. Usually means (and depending to the provider) that the flag definitions are all loaded or parse. I said loaded or parse as different providers may operate differently.
Some of our customers like to log or report when the SDK is "ready" (that is how we called it at Split) or when the loading timeout (in which case they want to report that too).

Excellent point. One thing I'm not sure of is how much of that concern we want to expose to the 1st party consumer, and how much should be abstracted by the provider. It seems like in some recent discussions, it's been made clear that having control and visibility over fetching locally cached values versus forcing a pull from the server might be useful. Do you have any ideas with regards how we might want that to look to the application author?

Control and visibility over fetching flags, in what context are we referring, for the provider or consumer?
I generally think of the flag evaluations, including the type of delivery, would fit more in a provider configuration. The consumers would want to be concerned that their flags are evaluating correctly but the underlying how of that evaluation is happening would be left to the providers.

Do we want to allow these hooks to modify the flag evaluation pipeline, or not. In other words, are they hooks which are purely observing the flag evaluation without having any effect on it, or are they middleware that could potentially effect the evaluation of the flag as they are called.
IMHO it'd be a lot simpler to start with the pure observer hook semantics, at least for now, just because nailing down the semantics for a middleware approach would be pretty tricky. We could come back at a later stage and introduce a distinct middleware-style extension point, if it ends up being needed.

@moredip I think manipulating the context (altering properties before evaluation, as well as storing state therein, such as OTel spans) would be required for even basic use cases. Manipulating the response however, might not be required.
When you ask about "pure observer" hooks, do you consider alterations to the context to be a violation of that?
Also - in the even that an hook throws, in your model, I assume that wouldn't impact flag evaluation. Is that right?

ah yeah, I guess you're right that you'd need to have somewhere to store that state. The Otel span is a great example.
I was starting to say that I still think we should prohibit modifying the direct inputs and outputs (i.e. the Context coming in, and the evaluated value coming out), but now that I think about it I agree with you that there'd likely be use cases where we want to use a before hook to inject additional context into a flagging decision. So now I'm re-considering my "pure observer" stance 😆
I don't think I have a well-formed opinion on what the semantics should be for a hook throwing an error. My gut feel is that that shouldn't cause the evaluation to fail, but I'm not really sure TBH

Should the error function be a part of OpenTelemetry hook? It can be a part of a separate diagnostics hook as described here since client developers typically should not have be exposed to the telemetry details (which should be handled by the provider) but needs the diagnostics data for troubleshooting.

Should the error function be a part of OpenTelemetry hook?

OTel has semantics around errors. We have a basic implementation here, which adds standard OTel error information in the error() handler: https://github.com/open-feature/sdk-research/blob/main/packages/openfeature-extra/src/lib/hooks/open-telemetry-hook.ts#L52
Since this deals specifically with OTel semantics, I think the OTel hook is the appropriate place.

I'm going to close this since it's captured in the current spec. Feel free to open PRs or further discussions if needed.


Correction for raw affiliation EA 4294, AGIR, Jules Verne Picardy University, Amiens, France; Respiratory and Intensive Care Unit, University Hospital Amiens, Amiens, France

Correction needed for raw affiliation EA 4294, AGIR, Jules Verne Picardy University, Amiens, France; Respiratory and Intensive Care Unit, University Hospital Amiens, Amiens, France
raw_affiliation_name: EA 4294, AGIR, Jules Verne Picardy University, Amiens, France; Respiratory and Intensive Care Unit, University Hospital Amiens, Amiens, France
new_rors: 01gyxrk03;010567a58
previous_rors: 01sjmsj73;01gyxrk03;010567a58
works_examples: W3038160084
contact: da159b68d95c1ba75818b5f47621cc81:97b13e7c0e8191705159adaf1d5beed3 @ u-picardie.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Unknown error retrieving IP.

Hello,
When I try to create a new vm I get this error:
Traceback (most recent call last):
  File "./examples/create_pro_vm.py", line 20, in <module>
    ip = i.purchase_ip()
  File "/usr/local/lib/python2.7/site-packages/ArubaCloud/PyArubaAPI.py", line 251, in purchase_ip
    raise Exception('Unknown error retrieving IP.')
Exception: Unknown error retrieving IP.

Here is the command I typed:
python ./examples/create_pro_vm.py -d 4 -u my_login -w my_password -t 35 -n aruba-vps-0004 --vmpassword vmpass

Hi @juliensnz,
In order to debug the problem I need to add more verbosity to the method, I'm going to do it now, but meanwhile could you check if you have enough credit to buy a new IP or if you have a total of 15 IP per vm? Because there is this limit: if you have 1 vm you can buy up to 15 ip, 30 in case of two vm and so on...
Furthermore, the template with ID 35 within datacenter 4 should be a Windows 2003, it's not possible to create a Windows 2003 VM anymore, since Microsoft ended the support. Actually this is not visible in the template object, I'm going to add the "enabled" field tomorrow.

Hello,
I made the changes, please try running it with parameter debug=True in purchase_ip (already in the example), and let me know what is the error message returned.


SwarmSaveImageWS.py:49: RuntimeWarning: invalid value encountered in cast

Fresh installed on RunPod
Stable Diffusion 3.5 FP8 Scaled works fine
After restart of the machine here verbose logs
https://paste.denizenscript.com/View/127464
2024-10-23 21:16:23.956 [Debug] [ComfyUI-0/STDERR] /workspace/SwarmUI/src/BuiltinExtensions/ComfyUIBackend/ExtraNodes/SwarmComfyCommon/SwarmSaveImageWS.py:49: RuntimeWarning: invalid value encountered in cast
2024-10-23 21:16:23.956 [Debug] [ComfyUI-0/STDERR]   img = Image.fromarray(np.clip(i, 0, 255).astype(np.uint8))

as said on discord, i'm pretty sure that just means the model NaN'd

hat just means the model NaN'd

the model works on windows and massed compute with RTX 3090 and A6000 - also model is from comfyui org


About Tab - Team Member

As a Team Member
I want a place for all the information about a Work and attached Project
so that I am able to see all the information related to my Work in one place
Acceptance Criteria
Scenario 1:
GIVEN I am on the Work Page for an Assessment or Earlier Worktype
WHEN I click on the About tab
THEN I see the following:

Details (default)
Calendar (not active. to be added later)

on Details:

Project panel
Work panel
Resources

Project Panel:

Project Creation Date
Proponent
Project Description (ability to Read More/Read Less)
Type
Subtype
Location Description (ability to Read More/Read Less)
ENV Region
NRS Region
Abbreviation

Work Panel:

Work Start Date
Anticipated Referral Date
Current Milestone (truncated)
Next Milestone (truncated)
Work Description (ability to Read More/Read Less)
EA Act
Federal Involvement
Federal Act
Responsible Ministry
Decision Makers (title of decision maker, not the name)

Scenario 2:
GIVEN I am on the Work Page for a Post Assessment Worktype
WHEN I click on the About tab
THEN I see the following:
Project Panel:

Certificate Number
Certificate Issued

Scenario 3:
GIVEN I am on the About tab
WHEN I look at the Resources panel
THEN I see the following:

Link to EPIC.Public (contextual to jump to the page about this Work)
Link to eGuide
EA Act (2018) (contextual to act this work is under)

Project Panel:

Certificate Number
Certificate Issued

link to prototype - https://www.figma.com/file/E92XoEegK2fLQ3odMeyWBD/Development-(Issues_Status_Dashboard)?type=design&node-id=28-5340&mode=design

@jadmsaadaot
a couple of bugs:

[ ] there should be left and right margins of 24px. Now there are multiple divs with their own margins.

[ ] same for the top padding - should be just 16 px.

[ ] All font should be the same
color: rgb(49, 49, 50);
font-size: 0.875rem;
line-height: 1.2rem;
font-weight: 400;

Now for Project Type, Subtype, Env Region, NRS Region have letter spacing 0.39px
Now for Work Current/Future Milestones, EA Act, Federal Involvement, Federal Act have letter spacing 0.39px

Work Panel is Missing Work Description

Work Description Added


Update Robot version 22.4.4 and Lambda python runtime to 3.9

Description of changes:
Version bumps:

Robot version 22.4.4
Lambda python runtime bump

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/do-e2e-tests

/do-e2e-tests


Custom margins

No version bump :cry:

I know it is outside the scope of this ticket, but please add this CSS Reset

Create a cssReset.scss file with the css code in the article
Put it inside react-components-for-you/src/styles/scss/
Import that file in index.scss with comment CSS Reset from https://www.joshwcomeau.com/css/custom-css-reset/

Original issue


"PowerToys Run ran into an issue" when trying to open Edge browser

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce

Had powertoy running.
PC went to standby (screen went black but did not go to sleep) while AFK
Jigged mouse to lit the screen and enter user password to log back in.
Hit custom key bind ALT+Z to activate powertoy run.
Entered .edge to start Edge browser.
Got an error prompt asking me to file a bug report.
2023-01-16.txt

✔ Expected Behavior
Edge loads without error.
❌ Actual Behavior
Edge did not load; got an error.
Other Software
Microsoft Edge
Version 109.0.1518.52 (Official build) (64-bit)

This is fixed with 0.69.1 or better.  Please upgrade


Button Text changes should not be animated

When setting the view, nothing gets animated (correctly) except Button.Text gets animated (incorrectly). This creates several visual distractions including:

Appearance of an ellipsis if the new title is shorter
A quick fade out and fade back in (on iOS) that looks like a flicker
Text moving if the text length changes

This is especially bad if your UI has a lot of buttons because now everything is flickering.
For comparison, note how Label and Entry text is not animated.

TBH, I'm worried this might be a bug with Forms. Need to find out what's triggering the animation.

It's not an issue in Fabulous itself. I reproduced it in both Fabulous and C# Xamarin.Forms.
Fabulous
// Copyright 2018-2019 Fabulous contributors. See LICENSE.md for license.
namespace TestPraeclarum

open System.Diagnostics
open Fabulous
open Fabulous.XamarinForms
open Xamarin.Forms

module App =
    type Model =
      { Toggled: bool }

    type Msg =
        | Toggle

    let fullText = "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean tempus vestibulum justo eu porttitor."
    let smallText = "Lorem"

    let init () = { Toggled=false }

    let update msg model =
        match msg with
        | Toggle -> { model with Toggled = not model.Toggled }

    let view (model: Model) dispatch =
        View.ContentPage(
          content = View.StackLayout(padding = 20.0, verticalOptions = LayoutOptions.Center,
            children = [
                View.Button("Toggle", command = (fun () -> dispatch Toggle))
                View.Button(if model.Toggled then fullText else smallText)
                View.Label(if model.Toggled then fullText else smallText)
                View.Entry(if model.Toggled then fullText else smallText)
            ]))

    let program = Program.mkSimple init update view

type App () as app =
    inherit Application ()

    let runner =
        App.program
        |> XamarinFormsProgram.run app

Xamarin.Forms
<?xml version="1.0" encoding="utf-8"?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             xmlns:d="http://xamarin.com/schemas/2014/forms/design"
             xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
             mc:Ignorable="d" x:Class="TestAnimationCSharp.MainPage">
    <StackLayout Padding="20" VerticalOptions="Center">
        <Button x:Name="ToggleButton" Text="Toggle" />
        <Button x:Name="TestButton" Text="Lorem" />
        <Label x:Name="TestLabel" Text="Lorem" />
        <Entry x:Name="TestEntry" Text="Lorem" />
    </StackLayout>
</ContentPage>

using System;
using Xamarin.Forms;
using Xamarin.Forms.PlatformConfiguration.iOSSpecific;

namespace TestAnimationCSharp
{
    public partial class MainPage : ContentPage
    {
        const string FullText = "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean tempus vestibulum justo eu porttitor.";
        const string SmallText = "Lorem";

        bool _toggled = false;

        public MainPage()
        {
            InitializeComponent();
            On<Xamarin.Forms.PlatformConfiguration.iOS>().SetUseSafeArea(true);
            ToggleButton.Clicked += ToggleButton_Clicked;
        }

        private void ToggleButton_Clicked(object sender, EventArgs e)
        {
            _toggled = !_toggled;
            TestButton.Text = _toggled ? FullText : SmallText;
            TestLabel.Text = _toggled ? FullText : SmallText;
            TestEntry.Text = _toggled ? FullText : SmallText;
        }
    }
}

Looks like it's the native behavior. Tested it on Xamarin.iOS C# and same result.

It’s not native behavior, it’s a bug.
I would recommend doing a custom renderer to fix it.
Just because you didn’t write the bug, doesn’t mean it’s not a bug and I don’t appreciate this issue being closed.
Sent from my iPhone

On Jul 12, 2019, at 9:23 AM, Timothé Larivière<EMAIL_ADDRESS>wrote:
Closed #308.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

From the Twitter thread, I'm trying to explain how this isn't an issue about what Forms does by default because Forms doesn't have to solve the problem Fabulous is solving: resource reuse.

It's not how "Forms works". We are not using Buttons the way Forms intends. From one frame to the next, the button role, style, size, etc can dramatically change because it is representing a whole different button model. It's a raw resource we reuse.
Our job is to manipulate so it appears to become another button. Forms does not do this and therefore its little animation is fine/makes sense. But Fabulous is different. There is a fundamental misunderstanding on what's going on here, and that scares me a bit.

Ok, I think there was a misunderstanding here.
I thought you were saying that changing an existing button's title (same role, same style) shouldn't ever trigger an animation and ellipsis.
So that's what I tested and said

Looks like it's the native behavior.

And it is.
That's what Swift / Xamarin.iOS / Xamarin.Forms do out of the box on iOS (setTitle("xxx", Normal)).
But you're right.
In the case Fabulous determines that the button can be reused, it will do so and on iOS this will play the animation, even if this doesn't make sense for the user.
This is a problem.
So reopening the issue.
Now the thing is:

How can we determine that the reused button is the "same" (animation vs no animation)?
How should we remove this "animation"? Disabling button reuse on iOS only? Writing a custom renderer that developers could unintentionally replace and make the bug come back when writing their own?
Should we completely remove the animation?

In the recently released v0.55, we introduced the concept of keyed nodes.
It lets you assign a key string to your controls so you can give hints to Fabulous on how to reuse the controls.
See more here: https://fsprojects.github.io/Fabulous/Fabulous.XamarinForms/views-perf.html#views-differential-update-of-lists-of-things
It helps with this issue by letting you ensure Fabulous won't accidentally trigger the fade-in/fade-out animation by reusing a button when you were expecting a new button.
So by setting keys to your buttons, the iOS animation will only trigger when you actually want to reuse the same button. (default iOS behavior)
UI controls whose keys are not present on the next update will be destroyed.
If you don't set any key, Fabulous will reuse all buttons as it did previously.
NOTE: Don't use this key only has a way of disabling the animation. This is not the intended use case for it.
If you want to get rid of the iOS animation, please look for an official iOS way of doing this.
Changing the keys all the time will prevent Fabulous from optimizing the UI when it can.
View.Button(
    key = "same_key",
    text = sprintf "Same key: %i" model.Count
)

View.Button(
    key = sprintf "new_key_%i" model.Count,
    text = sprintf "New key: %i" model.Count
)


Set tooltip color

Since the tooltip is in the DOM just under the body, it inherits the body color. However, we may want the tooltip color to be consistent with the bqplot font color instead.
I think we should maybe mirror the bqplot element background/font colors at https://github.com/bloomberg/bqplot/blob/837f8192b42a692de3b493dfc5e8cad04a5e939a/js/src/bqplot.less#L17-L19 in the tooltip section around https://github.com/bloomberg/bqplot/blob/837f8192b42a692de3b493dfc5e8cad04a5e939a/js/src/bqplot.less#L54 (instead of hardcoding that background color to black) and use those colors here for the tooltip:
https://github.com/bloomberg/bqplot/blob/837f8192b42a692de3b493dfc5e8cad04a5e939a/js/src/bqplot.less#L248

For the 0.11 branch, probably we just need to add a color: white; or something to the dark theme: https://github.com/bloomberg/bqplot/blob/3d4bf69a13099c168eec4738d7b0dfe75849c3bb/js/src/bqplot.less#L296


upgrade docs build system

this repo uses the old Crate docs build system. we should update it to use the new build system (https://github.com/crate/docs)
for instructions, see here: https://github.com/crate/crate-howtos/issues/163

I am interested in this

@infoverload please feel free. however, note: this is one of the projects I left until last because crash itself is a Python project. so the Python that exists to package and test crash itself needs disentangling from the Python (Sphinx, etc.) that builds the docs
so I would see this as a three-stage process:

[ ] modify the existing build/setup infrastructure so that it is completely unaware of anything in the docs/ directory
[ ] gut any existing docs build infrastructure
[ ] drop in the new docs build system

I am not sure whether crash actually uses the docs for testing. I know that crate/crate makes extensive use of doctests within the docs. this is one of the reasons I chose to leave crate/crate until last. because figuring out how to tease all that apart is going to be a challenge

fixed by https://github.com/crate/crash/pull/341


snekim: init at 1.2.0

Description of changes
Added the snekim  package and one of it's dependencies, nimraylib-now.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

This is my follow up pr to https://github.com/NixOS/nixpkgs/pull/194822#event-7655616423

The snekim executable gives this error tho:
> ./result/bin/snekim
INFO: Initializing raylib 4.2
INFO: Supported raylib modules:
INFO:     > rcore:..... loaded (mandatory)
INFO:     > rlgl:...... loaded (mandatory)
INFO:     > rshapes:... loaded (optional)
INFO:     > rtextures:. loaded (optional)
INFO:     > rtext:..... loaded (optional)
INFO:     > rmodels:... loaded (optional)
INFO:     > raudio:.... loaded (optional)
WARNING: GLFW: Error: 65542 Description: GLX: Failed to load GLX
WARNING: GLFW: Failed to initialize Window
FATAL: Failed to initialize Graphic Device

when not run with ``steam-run`

It runs without issues with steam-run ./result/bin/snekim

It with steam-run ./result/bin/snekim, tho the nim's std/appdirs thinks the home directory is at /homeless-shelter?

That was fixed by not determining the home directory path at compile time.

The snekim executable gives this error tho:
> ./result/bin/snekim
INFO: Initializing raylib 4.2
INFO: Supported raylib modules:
INFO:     > rcore:..... loaded (mandatory)
INFO:     > rlgl:...... loaded (mandatory)
INFO:     > rshapes:... loaded (optional)
INFO:     > rtextures:. loaded (optional)
INFO:     > rtext:..... loaded (optional)
INFO:     > rmodels:... loaded (optional)
INFO:     > raudio:.... loaded (optional)
WARNING: GLFW: Error: 65542 Description: GLX: Failed to load GLX
WARNING: GLFW: Failed to initialize Window
FATAL: Failed to initialize Graphic Device

when not run with steam-run

This was fixed by using raylib from nixpkgs (dynamic lib instead of static).

Oops, didn't mean to commit structorizer there, fixed it.


Purge unittest?

🚀 Pull Request
Description

I learned of these tools to help convert unittest tests to pytest-style tests

unittest2pytest
pytestify

So obviously I wanted to see what happens if you point them at cf_units!  The udunits tests needed a little manual intervention, because the pattern
with pytest.raises(SomeError) as thing:

gives you a different thing to
with self.assertRaises(SomeError) as thing:

Otherwise, this was remarkably painless.
The final commit just gets rid of the pattern import cf_units as unit from one test module.  I assume that was a hangover from when cf_units was taken out of the iris.unit module.

Thanks @pp-mo, I've addressed your comments.  I'm at a loss what to do about Codacy's objection though.

I tried removing that method entirely, and I couldn't see any change in the test output.  🤷♀

Thanks @rcomer.
Not fun work, but very needed !


Replay a stream

Use case

As a user, I would like to replay a stream or several streams at the speed when the events were generated.
For example for query like below, we rewind the data to one day ago and replay the events in stock_prices stream at the (relatively) same speed when the events got generated. When the replay catches up to the live events, handle the events at the live speed.
SELECT * FROM stock_prices WHERE _tp_time > now() - 1d settings replay_speed=1;

Describe the solution you'd like

We probably need introduce something like a RateLimitTransform to plugin into the pipeline after SourceReader or a direct RateLimitReader to control the replay speed. The RateLimitTransform can buffer some events and control the replay speed according to the _tp_append_time of events.
Describe alternatives you've considered

Additional context

(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint.

Phase 1: #224, support replay a stream. Done
Phase 2: Enhancement: disable replay when reached latest data
@lizhou1111

(Jove Github Bot) assuming it is not done, deferred this ticket to the next sprint.


Misleading role descriptions for Virtual Machine Contributor and Disk Snapshot Contributor roles

Hi Everyone,
The description of the RBAC role Virtual Machine Contributor implies that anyone holding this role can create/manage snapshots:

[...] manage disks and disk snapshots [...]

However, there is no corresponding action associated with this role. Instead the role Disk Snapshot Contributor holds the appropriate actions:
"Microsoft.Compute/snapshots/delete",
"Microsoft.Compute/snapshots/write",
"Microsoft.Compute/snapshots/read",
"Microsoft.Compute/snapshots/beginGetAccess/action",
"Microsoft.Compute/snapshots/endGetAccess/action",

Furthermore the description of the Disk Snapshot Contributor role states:

Provides permission to backup vault [...]

Which is not accurate.
I believe the two role descriptions need to be updated.
best regards
Holger

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

ID: 99581afb-7950-6daa-7227-055d04446b7e
Version Independent ID: f1a5bf89-9e54-aede-3a9a-70788a95927b
Content: Azure built-in roles - Azure RBAC
Content Source: articles/role-based-access-control/built-in-roles.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@shwetamathur7 Thank you for your feedback . We will investigate and update the thread.

@holgjat
I have updated the description for Virtual Machine Contributor and sent the changes to author for review.
For Disk Snapshot Contributor,
"Assign the Disk Snapshot Contributor role to the Backup vault’s managed identity on the Resource group where backups are created and managed by the Azure Backup service. The disk snapshots are stored in a resource group within your subscription. To allow Azure Backup service to create, store, and manage snapshots, you need to provide permissions to the backup vault."
Ref : https://docs.microsoft.com/en-us/azure/backup/backup-managed-disks


Docs: Text design guidelines

Added design guidelines to the Text component

@ponori Are we splitting this upgrade in 2: design guidelines + engineering part? As they are, I would expect another round of changes to get them finished. See prop table for instance.


Remove Composer Auth

Removes reliance on the COMPOSER_AUTH secret from workflows so actions triggered from forks will still run.

Pull Request Test Coverage Report for Build 836439349

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 72.131%

Totals

Change from base Build 836101677:
0.0%

Covered Lines:
44

Relevant Lines:
61

💛  - Coveralls


Handle new BadConversion exception from abt lib

RedPRL/sml-typed-abts#78 adds a generic conversion error. This PR handles that error in RedPRL. The two PRs should be merged at the same time; neither is backwards compatible.
I also added a test demonstrating the new error message when arities don't match.
../../test/failure/bad-op.prl:3.22-3.31 [Error]:
  Arity mismatch for operator foo{}

I've updated this branch to reflect the recent changes to the parser.
@jonsterling I'd appreciate a review on this (and RedPRL/sml-typed-abts#78) when you get a chance! Thanks!

Just to be clear, the build is failing because travis builds against the master branch of RedPRL/sml-typed-abts.

looks good! I've merged your PR to the abt library. I think you will need to update the submodule to point at the latest commit. (And in the future, if you want Travis to test your library changes, you can just temporarily change the submodule to point at them, and then update to master once the dependency PR is merged.)
Thanks for doing this!!

Oh, I see, that makes sense. Thanks!
I just updated the submodule, so it should build now.


Add scores for the sonar models

Had issues getting them to work on ucloud.

Added in latest release


update dependencies management instruction in CONTRIBUTING.md

Updated dependencies instruction in CONTRIBUTING.md:

The packagement tool has changed from go dep to go module.
Kubernetes documents has moved to new repository, so the link should be updated. See https://github.com/kubernetes/kubernetes/pull/39120

/assign @mrhohn


Refactor with configure snapshots

Replaces  https://github.com/wix/eyes.it/pull/26` (rebased on migrate to yoshi)
Testing

[x] Unit tests - pass when ran locally (PR CI not set up yet)
[ ] Tested using a  PR in WSR - which passed all eyes tests.
https://github.com/wix/wix-style-react/pull/2317
[ ] e2e - real eyes test within eyes.it - not set up yet

Status
I think we can merge this, and add a real eyes test later.
The test using a PR on WSR gives enough confidence for now.

@shlomitc @argshook Can we merge this?


Update word-list.md

Master user has been renamed to Sponsor user (announcement will happen soon)

Thanks for contributing, @htadashi! It would be good to sweep through our Dev Portals and Help Center to update the word in those spots as well, if you're not doing that already.


Feature/pmg 184 sidebar improvements

Description

Navbar fixed
Sidebar fixed
Improved responsiveness for mobile view
Motivation and Context

How Has This Been Tested?

Manual Testing
Do you have any tests?

[ ] Yes
[x] No

@joseiba: we need to resolve conflicts before merging the pull request.

@joseiba: we need to resolve conflicts before merging the pull request.

Okay, it's solved


Generate message codecs at runtime

There is a huge amount of boilerplate code used to encode/decode messages. This should be done using some sort of DSL.

Current syntax (which may change) looks like:
downstream magic_on_player {
    opcode: 249

    data {
        index: u16,
        spell: little u16,
    }
}

update on this? @Major-

Parser is done but slightly hacky, code generation doesn't exist. Will push to a branch later today (10th), probably

Are you talking about: https://github.com/Buroa/Eryna/tree/master/data/plugins/_decoders, https://github.com/Buroa/Eryna/tree/master/data/plugins/_encoders

No, that's just defining them in ruby. You can see the branch that has some of this work in here.

Not worth the effort, may revisit in future


fix(ListItem): remove aria-current from legacy ListItem

This PR is simply to change the legacy ListItem to not add the aria-current attribute when the item has focus.  Adding aria-current causes the screen reader to read each item with "current" added to the label, which is redundant.
Before:

After:

Testing notes:

yarn start
go to Legacy > ListItem
open dev tools on (A Center Button)
ensure the aria-current attr is not present on the anchor

Since there is already a way to suppress/disable the aria-current attr, I will just use that in cantina


Image Resolution Stage 1

This is the stage 1 effort for an image library that can be eventually used by buildah and
podman alike.  In eventuality, the main goal of the library (package) is to:

provide a consistent approach to resolving image names in various forms (from users).
based on the result of the above, provide image methods that in a singular spot but separate from the runtime.
reduce the cruft and bloat in the current podman runtime.

The goal of stage 1 is to demonstrate fast, accurate image resolution for both local and remote images resulting in an image object as part of the return.
Signed-off-by: baude<EMAIL_ADDRESS>

make sure everyone looks hard at the tests to make sure we are covering all the use cases we want.

and make sure everyone reads the commit message to understand the goals of this PR.

All tests are failing?

@umohnani8 is this better for you?

@baude yup! LGTM

Happy green tests lights.  +1 on the due time @baude

Ugh, false alarm on the green test lights,  Hit comment and travis ci popped up as in progress.


Tri 3 indiidual seed

I believe that I should get (3.0/3.0) for my individual seed:

( I ended the tri with 93.4%)
Collaboration
Me, Nandan, Torin, and Sergi often contributed togethers often to work together in figuring out our CPT project and the spotcheck. We talked often on slack for the spotcheck and called on discord to integrate all
Ap preparations:
I took notes an all teach teaches and and regularly updated my lab notebook. This includes notes from tri 1 and tr2  and these notes contain important notes that are going to help me review for the ap test.
https://varunm532.github.io/varun2/
planning/progress
My team and I  had issues  documing progress and problems with our code:
https://github.com/varunm532/varun2/issues/12
https://github.com/TDWolff/AtlasIndex/issues/9
https://github.com/TDWolff/AtlasIndex/issues/10
https://tdwolff.github.io/NAVTFrontend/2024/01/10/Ideation_A.html
https://tdwolff.github.io/NAVTFrontend/2024/01/19/Ideation_B.html
Contribution and coding:

(after merging frontend)

(backend after merging)

(

Student has proven proficiency in general coding, individual and team management + contribution, and progress documentation in relation to utilizing skills and preparing for real AP assessments of knowledge (Canvas outline). Student ended with above 93% in previous Trimester class.
Ideation may lack some formatting and content clarification/more specific descriptions of ideas, but is sufficient in providing initial planning and fostering group organization and collaboration. Issues also demonstrate organized progress tracking.
Varun has proven his status in qualifying for a 3.0/3.0 (100%) Individual Seed.


How to run without "privileged"

Hello!
I'm trying to use this image in a CI system to do integration testing, however, I'm forbidden to use the privileged flag because it is a security hazard.
Do you know whether it's possible to run the stand-alone container without it, even if it means less performance/features?

+1


[ITA-958] Add missing features to Web-WebView

I forked the original react-native-web-webview repository and fixed / added a couple things:

Better implementation for injectedJavaScript prop which shouldn't inject the JS code multiple times in case the HTML source changes.
The method field in the source prop object defaults to GET in the original package, changed the implementation here as well to behave the same way.
Implement the injectJavascript method on the component.
Add support for the onLoadEnd prop.
react-native-webview on its supported platforms injects the ReactNativeWebView variable on the window inside the WebView. Replicated this behaviour here as well.

Would you extend the README to specify support of onLoadEnd?

Oh, right, I forgot to do that. Here it is: d6dde94