Prefer not to use collisionObjects

After playing around with hpp-fcl and pinocchio, I spent quite some time trying to figure out why collision checking was not working.
It was due to the fact the I modified a collision geometry in the model, with create a new geometry data. Thus the pointer stored in the collision object of geometry data was not pointing to the same object as the collision geometry in geometry model. I don't know if I was clear...
Anyway, the API of hppfcl allow to bypass completely the collision object class. As it avoids duplicating a pointer, I believe it is better not to use it. I don't think removing it completely is a good idea neither. So I open the debate.

Ok, I will remove it.

Do you understand CI failure ? I can't access the logs...

As it seems not an output of the geometry algorithms, we can remove it without impacting end-users.

after double thinking, it is the output of the updateGeometryPlacements and we would be breaking the API. I have no idea whether it is actually used... This is the drawback of having only public attributes :)

Maybe, before merging this PR, we may need to deprecate collisionObjects in GeometryData. The good thing is that this quantity has not been exposed in Python yet, making things easy. @jmirabel Can you handle it?

Maybe, before merging this PR, we may need to deprecate collisionObjects in GeometryData.

I tried to avoid deprecation warning (and think I succeeded) at the cost of having to overwrite the default copy constructor... Deprecating a class attribute is very painful in C++.

Unrelated questions:

isn't there a CI duplication between the github CI 16.04 (python 2.7) and one of the travis run (16.04, python 2.7) ?

The Github CI is in Debug mode with CppAD tests.


Display "Cancel Upload" instead of "Begin Upload" button while uploading

Maybe you could show a "Cancel Upload" which replace the "Begin Upload" while it is uploading files?

Nice idea! I've already prepared some things for that. So probably soon.


Feature Request: Add support for a testing set.

Can you add support to test on a test set as well? Not only validation and training?
Thanks!

@aymuos15
Actually, it has support for that. In the dataset YAML file you can give the path to the test images and labels as well. If that happens, executing train.py will use the training and validation set whereas executing eval.py will use the test set. Here is an example if such a YAML file.
# Images and labels direcotry should be relative to train.py
TRAIN_DIR_IMAGES: '../input/trash_icra_xml/images/train'
TRAIN_DIR_LABELS: '../input/trash_icra_xml/labels/train'
VALID_DIR_IMAGES: '../input/trash_icra_xml/images/valid'
VALID_DIR_LABELS: '../input/trash_icra_xml/labels/valid'
TEST_DIR_IMAGES: '../input/trash_icra_xml/images/test'
TEST_DIR_LABELS: '../input/trash_icra_xml/labels/test'

# Class names.
CLASSES: [
    '__background__',
    'plastic', 'bio', 'rov'
]

# Number of classes (object classes + 1 for background class in Faster RCNN).
NC: 4

# Whether to save the predictions of the validation set while training.
SAVE_VALID_PREDICTION_IMAGES: True

Apologies that it's not clear right away from the README. I will update this.

Sounds Perfect. Thank you!


I have a few bugs

This could be a potential security issue
I am using the secret identity setting on the account. So naturally I checked to make sure that I was using Orbot.
Here are the issues:
-After leaving the app alone for several hours, the encryption of messages stops working periodically. I know this due to an encryption error message that I receive after I receive a supposed encrypted message. sometimes corrected by stopping encryption and restarting encryption on both sides.
-Cannot create a group chat on any server, and it would be useful to be able to add contacts through it using a multi-select feature on the contact list.
-Connectivity issues. after people are added onto the contacts list, they can show up as offline, more often than not. everyone that is involved has to restart their device, or force stop the app and start over again.
Again, all of this was only tested on my end as a secret identity. As of now, I have not been able to test the functions of the other account types.

I don't think there are any security issues here, just bugs that we have hopefully solved.
Which version of ChatSecure are you using?

I am using version. 14.1.1-RC-3.
As for security I meant my own security issues without encrypyion as information that would be passed is sensitive I do apologize for the confusion.
As a simple request, would it be possible to add an optional password to the encryption so if you don't have the password you cannot read the encrypted data? I just want as much informational security as possible.


[Coffee] Countdown

Extension
https://www.raycast.com/mooxl/coffee
Description
Would love to see a countdown of the remaining time that ones device will be caffeinated for.
I'll frequently caffeinate for the day (say 7.5 hours) but then leave my machine for one reason or another (finish early) and understanding how much time is left would be super useful. Yes, I could decaffeinate, but I might come back so sometimes I don't want to... 😅
Who will benefit from this feature?
No response
Anything else?
No response

So you want the number of time left in the menubar?

Yes, that's correct, the amount of time left for caffeination.

This is a great idea! I was just going to submit this.


No code example which allows to use tensorflow lite immediately in iOS

System information

TensorFlow version: 1.12.0
Doc Link:
https://www.tensorflow.org/lite/tfmobile/ios_build

Most iOS developers use Swift and Objective C. But tensorflow is written in C++ and "examples" require strong C++ knowledge too. In the same time that code contains a lot of hardcoded data and it is very hard to understand how to use it in general!
A lot of time passed. Why not to write a class-wrapper over tensorflow to hide C++ code from developers? For example, code should convert UIImage to NSString or array of strings

We recently improved the iOS demo document and added more explanation.
We're also working on adding more language binding support. Stay tuned.

Thanks @miaout17. I am closing this as I don't see a reason to keep this open. Thanks!


New Debian/Ubuntu/pip release please ...

I just installed this via apt on a Debian based system and it fails to run. I reinstalled it with pip and still fails to run. Turns out the reason is here:
https://github.com/django-extensions/django-extensions/commit/f3d80be6964b8498e15e40e8348c4398cf7439a5
As in a fix made in Jan 2016 is needed for Django 1.11 the current Django release but the .deb and pip packages don't work with it. It's way time for new packages to be put into the distros.

I'm not totally sure what you mean from this ticket nor the action to be taken but I will try to respond as best as I can.
The latest pip release was a couple of weeks ago and should work according to the Django versions policy. (If there is an issue with that people open a specific ticket per issue with reproducible test case and even better PR and tests for fixing it 👍 )
The version in Debian packaging is relatively old.  I cannot quickly see an easy way to nudge the python modules team for updating to a newer version in unstable. If you want it would help if you could add an issue there to update to a newer version.
https://packages.qa.debian.org/p/python-django-extensions.html
https://packages.debian.org/unstable/python3-django-extensions
Thanks !

Sorry for the lack clarity, but I tried installing from the ubuntu repository and and the extension di not work because of the issue fixed in Jan 2016 described above. To wit concluded the Ubuntu repository had not had a new package update since the fix well over a year ago.
The suggested action is to update the ubuntu repositories with a package that works with the current version of Django there (1.11).
The pip repository I assumed was also dated because I installed it with pip and also did not work. But it may be that this was because I had the dated ubuntu.deb package installed already. I wasn't looking too closely. The fix I made locally was to fully remove the ubuntu package then download from git here and install and I'm rolling. So it might be the pip repository has the update already and I bungled the install.
All I was observing was if on Ubuntu you install django and django-extensions then django extensions does not work. But the break was fixed in Jan 2016 and the ubuntu repository not updated yet.

Thanks for the reply !
I have not found an easy way yet (in the limited time I had available) to nudge the maintainers and ask them to update. I did see that the Ubuntu/Debian development system automatically nudges them when new versions become available and that it shows newer versions are indeed available.
If the versions of Django and Django-Extensions in the Ubuntu/Debian package list are out of sync it's probably best to raise a ticket with them so they can update Django-Extensions.
Would be very happy with a closer relationship with those maintainers to make sure something like this does not happen in the future or that packages like ours can be updated more frequently.


Go: allow several clients to share the same connection

When a client uses multiple services for the same API, it should only need to have one connection.
One way to support this would be to provide a way to get the connection from a client and pass it to another. E.g.
c1 := vkit.NewClient(...)
c2 := vkit.NewConfigClient(gax.WithConnection(c1.Connection()))

Oh yeah, thanks for reminding me


OPC Publisher could not issue a valid certificate without deleting PKI folder

Describe the bug
The OPC publisher could not connect to the OPC UA server because the client certificate has expired and did not renew automatically. After manually removing the PKI folder and restarting Publisher, it forced to create a new folder and issue a valid client certificate for OPC server.
Log with error.
opc-Publisher.log
Expected behavior
We expected the OPC publisher to issue a OPC client certificate automatically after one year, which would ensure that we would continually send OPC data to the Azure center.
Additional context
Our deployment configuration for OPC Publisher attached as well
Deployment-config.txt

fixed with #451. Please test it using :preview tagged container


Make "Date of recording" field actually show capture date instead of upload date

Right now the Date of recording field on the picture detail page actually shows the date the picture was uploaded, not the date it was recorded. This field should display info from the EXIF timestamp. I think Date/Time Original but I see several date fields in the EXIF tags so you might need to fall back to other fields if that one is blank.
For bonus points, the date shown on the sequence from the user profile page could also be set to the time of the first picture in the sequence instead of the upload date. This one is more of UI design question of what that field should display though.
I am currently uploading pictures taken in 2015 but the date on all of them shows as August 2016.

This could be checked via exif data, and if not available you could default to upload date

Please fix this issue. I want to be able fo find photo sequences by date of recording, not by date of upload.... cc @martijnv-telenav

Re-ping on this as well. The double upload bug in the upload script has me needing to find sequences by date of recording as well so I can track down which ones were affected.

https://twitter.com/KSUToeBee/status/927992121017151489

We provide a field on each photo that is the recording date called shot_date. I will close this since it was addressed if you consider otherwise please reopen it with updated details.

Please DO NOT CLOSE this issue until the problem is fixed!!!
NO, this was not addressed, just discarded!!!
I did a demonstration to try and explain the problem in more detail:
First i deleted all my uploaded sequences to remove confusion.
Then 3 random sequences were selected for this demonstration purposes, one from 2014. one from 2016. and one from 2018., and they were uploaded in random order.
They were all reported as from  today/yesterday.
Try to guess which sequence is from which year!!!
Here is a screenshot

and a link to the web: https://openstreetcam.org/user/hbogner
Now imagine what will happen when few more thousand sequences(waiting on the local drives) are added!!! Try and find a sequence then...
As I stated before, and as I stated to your team at SotM 2018, I'll won't upload my sequences until you fix this problem.

There is no way for me to reopen this issue so please be kind and reopen this not fixed issue.

I can provide those 3 sequences for download, as they are, if needed.
But please fix the date field.
Date of upload is of no importance to users, at least to me.
Date of sequence creation is what is important, and it should be sorted that way.

@hbogner Sorry for the misunderstanding. We addressed this issue for sequences that are recorded with our apps but for sequences recorded with third party cameras we currently do not a solution.
I could try to generate a OSC metadata file from your images having exif and upload them with a metadata file, this would solve your issue.

I have images from before OSC, so they could not be taken with the default app :)
They are action camera images or mapillary images, both having exif data.
Would this generation of OSC metadata be a part of https://github.com/openstreetcam/upload-scripts ?
No problem, I plan to delete them and re upload everything when this issue is fixed.
PS. Do you know does upload-scripts split sequences based on time&distance data?

Would this generation of OSC metadata be a part of https://github.com/openstreetcam/upload-scripts ?
Yes

I see the web UI has been changed to say Date of upload for action camera tracks. So you didn't change the data being shown, just the label. For mapping purposes I really don't care when an image was uploaded, just when it was captured. This affects iD and JOSM as well. JOSM doesn't show any date for action camera tracks and iD shows the upload date, not the capture date. Seeing cyclists in shorts and mid-summer greenery in Wyoming with the only date visible being "November 2" is definitely doing to confuse someone at some point :) https://openstreetcam.org/details/1303627/4/track-info


Update docs to clarify how events data is sent through $emit

Add each event separately (add to TOC)
Define what is passed through each

Added docs: https://github.com/benjamincharity/angular-flickity/releases/tag/v1.1.2


feat: estimates for the complex logarithm

This PR adds estimates for the difference of the complex logarithm log (1+z) and its nth Taylor polynomial in terms of ‖z‖ when ‖z‖ < 1.
See this thread on Zulip.

Thanks! :tada:
bors merge


add ResBlock Sub-module of YoloV4

To implement the functional resBlock sub-module of Yolov4.
reference torch model: here

Draft PR: #7121


#6197 Hotfix for fall through [6197]

Build status:

Linux
Mac
Windows

Failing test seems unrelated. Merging.


Incorrect word boundary in VI mode

Platform Ubuntu 20.04
Terminal software gnome-terminal
Version Reedline from Nushell 0.77.0
The word boundary (used in b and e) allows too many characters.
In VI mode a word should "consists of sequence of letters, digits and underscores" according to VIM docs, this is also how classic Readline works.
Steps to reproduce

Run Reedline in VI mode.
Type abc.def or abc:def
Use b and e motions and notice that the dot and colon are treated as parts of word

I've had a look at this as I keep getting caught out by dw and cw not doing what I expect in nushell :grin:. I'm totally new to the reedline code base and am relatively new to Rust so bear with me.
The way unicode-segmentation splits words is super nuanced. It might be a shame to lose the "correct" handling of unicode words that it does.  It also doesn't look like there's any way to influence unicode-segmentation's word splitting behaviour from the outside.
I can see a few possible solutions to fixing word splitting in reedline to better match what Vi and Emacs do:

Continue using unicode-segmentation for word splitting but then add an extra step which splits the words it generates further by looking through them for additional characters we want to split on. This is a bit clunky but at least we wouldn't be throwing away all the subtle handling of unicode that unicode-segmentation does. This might work because unicode-segmentation's concept of words tends to be broader than what we want in reedline.
Implement independent word splitting in reedline by walking through the line's graphemes and applying our own rules. Treat all/most characters beyond ASCII as word characters. This should work fine in many cases but there's probably all sorts of unicode edge cases we'd be ignoring that would cause odd behaviour for people not working in straight ASCII.
Vendor/fork unicode-segmentation  and add support for customising word splitting.

I'm tempted to try option 1 first as it's the least invasive but I'm open to other ideas / dissenting opinions.

Thanks for looking into it!
Yeah 1.) seems pretty reasonable as a starting point. The vim documentation feels a bit sparse to parse out the rules for a 2.) that would behave sensibly with more complex Unicode characters/graphemes.
With a bit of effort this should be doable as well, but unicode-segmentation has certainly done some of the heavy lifting already. We certainly don't need to do all the look-up-table work unicode-segmentation has done for ultimate performance.


is this project working?

Hi mate I am developing something similar and I've used lots of your code as inspiration. But now i am wondering whether you forgot to commit some stuff?
Will try to pull your project and run it to see if it actually works

The code works. Clone the repository and run
On Wed, Mar 27, 2019, 09:42 Kristjan Grm<EMAIL_ADDRESS>wrote:

Hi mate I am developing something similar and I've used lots of your code
as inspiration. But now i am wondering whether you forgot to commit some
stuff?
Will try to pull your project and run it to see if it actually works
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/juliuskrah/jasper-html-mail/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AJeOvf4hXHG2U6JSMCiOiaBg0gEvqIz5ks5vazz7gaJpZM4cNWFz
.

how to run?

@lyankyaw28 From the root of the project, run the following command mvn clean spring-boot:run. This assumes that you have Maven installed


@vercel/nft does not pick up platform-specific binaries

Related:

https://github.com/lovell/sharp/issues/3870
https://github.com/getsentry/sentry-cli/issues/1849

@vercel/nft does not pick up platform-specific binary files while tracing dependencies.
For example<EMAIL_ADDRESS>depends on @img/sharp-{arch} package, but the traced result only contains below paths.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
This currently breaks every build on Vercel and any deployments that uses @vercel/nft as its tree shaking library.

The logic used for esbuild should solve this:
https://github.com/vercel/nft/blob/37811197975fef8a3cda7d17e436d217a510398c/src/utils/special-cases.ts#L32-L41
I guess it might be worth extracting this logic as a common helper function as the use of optionalDependencies for native binaries is an increasingly common pattern.

Indeed, the quickest path forward is to add a special case for sharp like the one for esbuild in special-cases.ts.

A proper fix would be updating the static analysis to handle the dynamic require.
We already support simple dynamic requires, such as:
const path =<EMAIL_ADDRESS>const sharp = require(path);

Ideally, we could update that static analysis to handle the case of a for-loop, such as:
const paths =<EMAIL_ADDRESS>for (const path of paths) {
  const sharp = require(path);
}

Source: https://github.com/lovell/sharp/blob/c80e92fa16b90a05ca604df17a3d58a87238b3ec/lib/sharp.js#L13-L30

From my understanding, this is causing all app deployments that require sentry to fail on Vercel. Is there any workaround for this issue?

I just ran into this issue. For anyone stuck, downgrading to 0.32.6 works.

I see that this issue was renamed to be sharp specific. The issue isn't specific to sharp, and is breaking every Sveltekit app on Vercel using Sentry as mentioned above.

It's breaking all Astro deployments as well.. I had to downgrade sharp..

I see that this issue was renamed to be sharp specific. The issue isn't specific to sharp, and is breaking every Sveltekit app on Vercel using Sentry as mentioned above.

Building onto this comment, considering this issue was renamed should we open a separate issue for the Sentry CLI issue? IMO it would be a step in the wrong direction since this issue affects pretty much all packages that ship their binaries in optional dependencies. It would probably even affect swc.

As a Vercel and Sentry customer, this affects us.
Can someone from Vercel come up with an expected date for fixing this issue? We are debating whether we should rollback, or wait for the fix 🤓

@styfle This seems to have been closed because the sharp special case PR was merged. This issue is still much larger than sharp.

If you create a new issue with the steps to reproduce, I'll take a look, thanks!

For users of SvelteKit, I believe that setting runtime: 'edge' in adapter-vercel would avoid this issue and related issues by avoiding invoking @vercel/nft
https://kit.svelte.dev/docs/adapter-vercel#deployment-configuration

For users of SvelteKit, I believe that setting runtime: 'edge' in adapter-vercel would avoid this issue and related issues by avoiding invoking @vercel/nft
https://kit.svelte.dev/docs/adapter-vercel#deployment-configuration

Sentry doesn't currently work with vercel edge functions because of another vercel issue related to source maps.

@styfle Would you be able to respond to these comments from @lforst? There's a bigger issue here than what you've acknowledged. We can create a reproduction, but I'm concerned that's only going to lead to another special case that doesn't address the underlying issue.

I'd like to understand what's going on here. From my understanding @vercel/nft will only strip dependencies that are not used during runtime. During build-time, everything should be there.
We are seeing people having issues with our platform-specific binary on Vercel: getsentry/sentry-cli#1849 However, this binary is only used during build-time. What is going on here? Is there something we can do from our end? Special casing sounds kinda dangerous to me because we need to avoid having the binary deployed because of size concerns.

I see that this issue was renamed to be sharp specific. The issue isn't specific to sharp, and is breaking every Sveltekit app on Vercel using Sentry as mentioned above.

Building onto this comment, considering this issue was renamed should we open a separate issue for the Sentry CLI issue? IMO it would be a step in the wrong direction since this issue affects pretty much all packages that ship their binaries in optional dependencies. It would probably even affect swc.

@knd775 I mentioned an idea for proper fix in my previous comment: https://github.com/vercel/nft/issues/371#issuecomment-1835148920
Without seeing the code causing sentry to fail, its hard to know if this will also solve it too. But ultimately, every failure of @vercel/nft is a dynamic require somewhere.
If you could create a new issue with the steps to reproduce, I could answer the question but right now I don't know what is going on without more information.
(looks like someone created without steps to reproduce here https://github.com/vercel/nft/issues/382)

Posting this here for visibility: We introduced a workaround in the latest version of the @sentry/cli package. See https://github.com/getsentry/sentry-cli/issues/1849#issuecomment-1873970001.

@styfle Nft is not doing anything wrong or buggy I believe. In my opinion, it is just not a good idea to let nft operate before the build has completed. During build we need particular entries in optionalDependencies, however during runtime they can be wiped. I don't fully understand why nft even needs to run before building except for maybe to optimize storage cost (?).

@lforst nft runs during the build to know which files need to be compiled and ignore the others

@styfle It appears though that optionalDependencies are not available at the time of compilation. Maybe this is entirely unrelated then?

Again, its hard to know what the root cause is without steps to reproduce the issue

I'll see if I can whip up a simple repro in the upcoming days!


🎨 Remove configureClusterDeploymentAzureRBACRule and all associated code/constants

Summary
Some palette-specific Azure defaults were missed during cleanup. Start with configureClusterDeploymentAzureRBACRule and drill down.

Closing in favor of https://github.com/validator-labs/validatorctl/issues/84.


Info

Blurb:
The UMass+ Trapped Ions and Photonics lab develops integrated technologies like photonics for trapped ion QPUs. Developing trapped ion QPUs with integrated photonics may enable the next generation of quantum hardware towards large scale quantum computers and portable operation of quantum sensors like optical clocks.
Sponsors: NSF
Curriculum:
ECE 550/650 - Intro to Quantum Computing
Quantum Optics → Qubits → Quantum Algorithms
Introduction to quantum computing starts with a basis in quantum optics using the Mach Zehnder Interferometer as a foundation. We then survey various qubit technology modalities such as trapped ions, photonics and Transmons as well as sources of decoherence for each. In weekly Python labs students program simulations of single qubit operations such as Rabi and Ramsey pulse sequences as well as two qubit manipulations for Bell state generation to construct quantum circuits from fundamental quantum mechanical interactions. Finally, these labs will culminate in programming simulations of quantum algorithms by Grover and Shor using quantum computing Python libraries such as Qiskit and QuTiP and executing them on the cloud with real quantum computers.

fixed in #5


[7313] Upload new schools list from Get information about schools

Context
Upload new schools list from Get information about schools
Changes proposed in this pull request
Updated the csv in use
Guidance to review
Needed for production as well as source of truth,
https://github.com/DFE-Digital/register-trainee-teachers/blob/main/docs/setup-development.md#import-schools-from-csv-dataschools_giascsv
Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?
[ ] Do we need to send any updates to DQT as part of the work in this PR?
[ ] Does this PR need an ADR?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 Upload new schools list from Get information about schools


Update to Vue 3 and add Typescript definition

Wow.  Thanks.
I assume Vue 2 isn't going anywhere though, so now we have to figure out how to support both...

Do we just need a new branch and Vue 2 becomes "deprecated"?
Can this be made compatible with both 2 and 3?
Should both be provided side by side (as sep source files) in this repo and maintained?
Two repos?

How are most other Vue plugins handling this?

Most plugins just use a major version release bump so npm/yarn updates won't introduce breaking changes e.g. Vuex 3 supports Vue 2, Vuex 4 supports Vue 3 (awkward numbering)
Vue 2 users should also be able to use this plugin if they use @vue/composition-api that basically pollyfills the Vue 3 API into Vue 2

Can this please be rebased to pull in the small change from https://github.com/highlightjs/vue-plugin/pull/4?
Sorry for the delay.  After that I'll find the time to get this merged and make a new release.

Rebased with current HEAD


Tracer error with eqx.jit, jax.grad and dfx.diffeqsolve

I'm experiencing an exception in a code which tries to backpropagate through diffeqsolve, the whole thing being wrapped in eqx.filter_jit. The context is essentially an extension of your score-based diffusion example to calculate likelihoods as shown here. This works correctly, however when I try to take jax.grad of the log-likelihood w.r.t. sample (image), I get an error about a leaked tracer; indeed the leak location does look like it stores something in a struct. The reproducing code along with the error message are here. I hope this is not too difficult to understand, it's mostly refactored code of yours :)

Unfortunately the repro is far too large for me to be able to dig into! (Even if it is derived from some of my code.) There's a lot that can be removed here to make it smaller and more readable: the dimchecked annotations, the training etc. happening in the middle; the iterations using tqdm; lines like pt = pt - 0.01 * grad which whilst mathematically appropriate probably aren't the cause of the software error; etc.
(On a side note -- I'm very interested to see a reference to torch-dimcheck, which wasn't something I was previously aware of. I wrote TorchTyping, which does very something similar.)

Sure, I thought the repro may be enough to diagnose what's going wrong. I created a new version, can't guarantee it's truly minimal but certainly shorter to read. Would this be enough for you to see what's going on?

Yep, with this version it's immediately clear what the issue is!
When you have def ode_fun then self.eq.weight is being sneakily included via closure. Most of the time this will work without issue: JAX just sees the closed-over value when the closure is eventually evaluated and life proceeds as normal.
Meanwhile, when you have ode_func = self.eq then terms is a PyTree containing self.eq, which in turn is a PyTree containing self.eq.weight: this whole structure is visible to diffeqsolve -- and importantly, it is visible to BacksolveAdjoint.
The specific purpose of BacksolveAdjoint is to override how autodiff is performed, and in particular it will change how gradients are handled with respect to terms, y0, and args. When terms is a PyTree then it can see self.eq.weights, and there are no "implicit" inputs into the calculation. But when the PyTree structure is broken then we do have such an "implicit" input sneaking in to the calculation -- and we get the tracer error that you then see.
Various comments:

A related error to this is stated in the FAQ here but (a) this is obviously a slightly different issue, and (b) I don't think it's actually stated in the BacksolveAdjoint docs, which should probably be fixed. (Open a PR?)
Fixing this "once and for all" (in a robust hard-to-accidentally-write-errors way) will require changes to how custom_vjp works in core JAX.
At the moment you're doing grad-jit. I'd recommend doing jit-grad instead. A general principle for using JAX is that it's worth having a single JIT at the top level, wrapping everything else. (And in this particular case, it will actually also avoid raising an error -- we don't get an escaped tracer error because the JIT is outside the custom gradient handling, but conversely because self.eq.weight isn't visible to the custom gradient handling then if you were to try and compute a gradient with it then you'd get a zero gradient.)

Great, thanks :)


Add preview headers to NFT

See #45

Done in https://github.com/macterra/artx-market/commit/ec5123a44db89bd29d9410a240ca0aa1217db416


AllegroBasic

Hello Markus
I lost on old hdd your Allegro Basic
is there any chance you can publish it here or give me link for download?
Aurel

Hello...


Deprecated selector in particle-dev\styles\particle-dev.less

In particle-dev\styles\particle-dev.less:
Starting from Atom v1.13.0, the contents of atom-text-editor elements are no longer encapsulated within a shadow DOM boundary. This means you should stop using :host and ::shadow pseudo-selectors, and prepend all your syntax selectors with syntax--. To prevent breakage with existing style sheets, Atom will automatically upgrade the following selectors:

atom-text-editor::shadow .password-lines .line span.text:before => atom-text-editor.editor .password-lines .line span.syntax--text:before

atom-text-editor::shadow .password-lines .line span.text => atom-text-editor.editor .password-lines .line span.syntax--text

Automatic translation of selectors will be removed in a few release cycles to minimize startup time. Please, make sure to upgrade the above selectors as soon as possible.

Quick little issue to fix the pesky "Depreciated" link.

Closing this as a duplicate of #176 but thank you for adding more info!


fix: remove undefined from input class

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


Fix Typo in Contributing File

Overview
For new to open-source volunteers - the word "sustainable" in the Contributing Docs under the Issue Limit Policies header is misspelled and needs corrected. This issue is best for contributors new to open-source because it does not require local development. However we recommend contributors still clone the repo locally and follow all the steps in the Contributing file.
Action Items

[ ] Read and follow the directions in the Contributing file.
[ ] Correct the typo: sustainble -> sustainable.
[ ] Open a pull request.

Hello, I'd like to work on this.

Hey @jasonmokk This task is currently reserved for volunteers with Chayn. Please check back in 3 weeks for more issues like this to contribute. Thanks!

Hiya! I'd like to work on this issue :)

This issue should be completed, but I would appreciate any feedback.

Hey @GrannyYetta I do not see a pull request for this issue. Sent you a message on Slack.

The pull request should be available now in the following link: (https://github.com/chaynHQ/bloom-backend/pull/512)


Any way to prevent site scroll on drag-start?

Hi,
Is there any way to prevent the page from scrolling when you initiate a drag?
On mobile when trying to flip through the different slides, I find myself scrolling up and down a lot.
Thanks!

This is a fix https://github.com/akiran/react-slick/issues/1240#issuecomment-396484553
No official fix for the library yet.


fix examples.md to match the correct modern APIs

Proposed changes
I was trying to get started with docker client development, one of the examples didn't work with due to using old APIs I guess.

Deploy preview for docsdocker ready!
Built with commit a57a672af3c350c978ebbedd69820c1c94aa9187
https://deploy-preview-9876--docsdocker.netlify.com


Cut Falco 0.33.1 release

Type
This is a patch release.
As proposed in the Nov 16th 2022 community call, I will be the release manager for this version.
This version will fix:

CLBO issues identified on Minikube and GKE when gVisor support is enabled (see: https://github.com/falcosecurity/falco/issues/2287 )
Regression identified that made Falco crash when using eBPF when CPUs are disabled (see: https://github.com/falcosecurity/libs/issues/720 )

Current Artifacts

x86_64

https://output.circle-artifacts.com/output/job/edddb39a-2da7-4f38-8acc-101f869ae4a6/artifacts/0/packages/falco-0.33.0-5+e507eee-x86_64.deb
https://output.circle-artifacts.com/output/job/edddb39a-2da7-4f38-8acc-101f869ae4a6/artifacts/0/packages/falco-0.33.0-5+e507eee-x86_64.rpm
https://output.circle-artifacts.com/output/job/edddb39a-2da7-4f38-8acc-101f869ae4a6/artifacts/0/packages/falco-0.33.0-5+e507eee-x86_64.tar.gz

ARM Aarch64

https://output.circle-artifacts.com/output/job/8a6e3c9e-f389-4a43-a16a-3f270c6474c8/artifacts/0/packages/falco-0.33.0-5+e507eee-aarch64.deb
https://output.circle-artifacts.com/output/job/8a6e3c9e-f389-4a43-a16a-3f270c6474c8/artifacts/0/packages/falco-0.33.0-5+e507eee-aarch64.rpm
https://output.circle-artifacts.com/output/job/8a6e3c9e-f389-4a43-a16a-3f270c6474c8/artifacts/0/packages/falco-0.33.0-5+e507eee-aarch64.tar.gz

Date
Nov 24th, 2022
Release Versions

libs 0.9.2 https://github.com/falcosecurity/libs/releases/tag/0.9.2
drivers https://github.com/falcosecurity/libs/releases/tag/3.0.1%2Bdriver (same as 0.33.0, no driver changes are expected in this patch)

Release Steps
Read the release process for a detailed explanation.
Release Blocking PRs

https://github.com/falcosecurity/falco/pull/2299
https://github.com/falcosecurity/falco/pull/2300

Action Items

[x] Pre-Release

[x] Update milestones of relevant PRs to 0.33.1
[x] Changelog https://github.com/falcosecurity/falco/pull/2301

[x] Release

[x] Tag
[x] GitHub Release

[x] Website

[x] Bump Falco version to 0.33.1 https://github.com/falcosecurity/falco-website/pull/744

[x] Post-Rlease

[x] Helm Charts https://github.com/falcosecurity/charts/pull/428/commits/52d8281fac0159038f9aee80d672a9a12432571a

/assign @LucaGuerra
/kind documentation

Release completed (incl. Helm charts)


Translation update for Pods

/lgtm

Hi @feloy
We've stopped using capture shortcodes
I recommend that you rebase the changes in this PR to match the recently-updated English language original; it should be a straightforward update.

Fixed, thanks

/lgtm

/approve


RVIZ-1.13.1 crashed with OGRE-1.10.11-4

Arch Linux with ROS Melodic.
LOG:

[ziokuroi@zeta ~]$ rosrun rviz rviz
[ INFO] [1529071253.148222721]: rviz version 1.13.1
[ INFO] [1529071253.148245000]: compiled against Qt version 5.11.0
[ INFO] [1529071253.148256770]: compiled against OGRE version 1.10.11 (Xalafu)
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[ INFO] [1529071253.474469837]: Stereo is NOT SUPPORTED
[ INFO] [1529071253.475217752]: OpenGl version: 3 (GLSL 1.3).
[ERROR] [1529071253.475333574]: ItemIdentityException: Resource with the name BaseWhiteNoLighting already exists. in ResourceManager::add at /home/ziokuroi/ogre/repos/community-x86_64/src/ogre-1.10.11/OgreMain/src/OgreResourceManager.cpp (line 158)
terminate called after throwing an instance of 'Ogre::ItemIdentityException'
what():  ItemIdentityException: Resource with the name BaseWhiteNoLighting already exists. in ResourceManager::add at /home/ziokuroi/ogre/repos/community-x86_64/src/ogre-1.10.11/OgreMain/src/OgreResourceManager.cpp (line 158)
Aborted (core dumped)

I believe this was already reported and fixed in https://github.com/ros-visualization/rviz/pull/1105. I'll close this, comment if you do not believe this is the case.


Cab 3476

Get maxSize instead of size of result items for search, when maxSize is set and is more than size.
Add a new test case.

Coverage increased (+0.02%) to 83.474% when pulling 4e71dbdd32f9bd61a80dbe79800338b51af94ffc on CAB-3476 into 576d1441e9afe4814135ac1f694d6270bfcd797a on develop.


Add exclude_columns to DropDuplicateTransformer

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (0753375) to head (d6e4583).
Report is 20 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #296   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           41        41
  Lines         1071      1071
  Branches        41        41
=========================================
  Hits          1071      1071

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Use tomllib on python 3.11

This pr tries to solve the following issue: Python3.11, we can use the stdlib toml library #60.
I tried to modify the code as little as possible, hope it helps :)

Thanks. I don't understand the failures here. I guess some esoterica about the requirement syntax?

Sorry, as per the setuptools docs on the setup.cfg, I wrote the python version for the extras with the commas:
[options]
zip_safe = False
include_package_data = True
packages = find:
install_requires =
    requests
    importlib-metadata; python_version<"3.8"

but it seems they are not expected with commas:
[options.extras_require]
pdf = ReportLab>=1.2; RXP
rest = docutils>=0.3; pack ==1.1, ==1.3

Running tox before:
scriv on  stdlib-toml [?] via 🐍 v3.11.0 (.venv) on ☁  (us-east-1)
❯ python -m tox -e py311
GLOB sdist-make: /home/agustin/github_repos/scriv/setup.py
py311 create: /home/agustin/github_repos/scriv/.tox/py311
py311 installdeps: -r/home/agustin/github_repos/scriv/requirements/test.txt
py311 inst: /home/agustin/github_repos/scriv/.tox/.tmp/package/2/scriv-1.0.0.zip
ERROR: invocation failed (exit code 1), logfile: /home/agustin/github_repos/scriv/.tox/py311/log/py311-2.log
================================================ log start =================================================
Processing ./.tox/.tmp/package/2/scriv-1.0.0.zip
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Requirement already satisfied: attrs in ./.tox/py311/lib/python3.11/site-packages (from scriv==1.0.0) (22.1.0)
Requirement already satisfied: click in ./.tox/py311/lib/python3.11/site-packages (from scriv==1.0.0) (8.1.3)
Requirement already satisfied: click-log in ./.tox/py311/lib/python3.11/site-packages (from scriv==1.0.0) (0.4.0)
Requirement already satisfied: jinja2 in ./.tox/py311/lib/python3.11/site-packages (from scriv==1.0.0) (3.1.2)
Requirement already satisfied: requests in ./.tox/py311/lib/python3.11/site-packages (from scriv==1.0.0) (2.28.1)
Requirement already satisfied: tomli in ./.tox/py311/lib/python3.11/site-packages (from scriv==1.0.0) (2.0.1)
ERROR: Could not find a version that satisfies the requirement python_version<"3.11"; extra == "toml" (from scriv[toml]) (from versions: 0.0.2)
ERROR: No matching distribution found for python_version<"3.11"; extra == "toml"

================================================= log end ==================================================
_________________________________________________ summary __________________________________________________
ERROR:   py311: InvocationError for command /home/agustin/github_repos/scriv/.tox/py311/bin/python -m pip install --exists-action w '/home/agustin/github_repos/scriv/.tox/.tmp/package/2/scriv-1.0.0.zip[toml]' (exited with code 1)

and after the change:
scriv on  stdlib-toml [?] via 🐍 v3.11.0 (.venv) on ☁  (us-east-1)
❯ python -m tox -e py311
GLOB sdist-make: /home/agustin/github_repos/scriv/setup.py
py311 inst-nodeps: /home/agustin/github_repos/scriv/.tox/.tmp/package/2/scriv-1.0.0.zip
py311 installed: attrs==22.1.0,certifi==2022.9.24,charset-normalizer==2.1.1,click==8.1.3,click-log==0.4.0,coverage==6.5.0,exceptiongroup==1.0.4,freezegun==1.2.2,idna==3.4,importlib-metadata==5.1.0,iniconfig==1.1.1,jedi==0.18.2,Jinja2==3.1.2,MarkupSafe==2.1.1,packaging==21.3,parso==0.8.3,pluggy==1.0.0,pudb==2022.1.3,Pygments==2.13.0,pyparsing==3.0.9,pytest==7.2.0,pytest-mock==3.10.0,python-dateutil==2.8.2,PyYAML==6.0,requests==2.28.1,responses==0.22.0,scriv @ file:///home/agustin/github_repos/scriv/.tox/.tmp/package/2/scriv-1.0.0.zip,six==1.16.0,toml==0.10.2,tomli==2.0.1,types-toml==<IP_ADDRESS>,typing_extensions==4.4.0,urllib3==1.26.13,urwid==2.1.2,urwid-readline==0.13,zipp==3.11.0
py311 run-test-pre: PYTHONHASHSEED='789014312'
py311 run-test: commands[0] | python -V
Python 3.11.0
py311 run-test: commands[1] | coverage run -p -m pytest -Wd
=========================================== test session starts ============================================
platform linux -- Python 3.11.0, pytest-7.2.0, pluggy-1.0.0
cachedir: .tox/py311/.pytest_cache
rootdir: /home/agustin/github_repos/scriv, configfile: setup.cfg
plugins: mock-3.10.0
collected 162 items

tests/test_changelog.py .......

tox seems to run fine.

Thanks!


Fix lock hang on Windows

Solves an issue where FileLock and SoftFileLock could hang sit in an infinite loop if PermissionError or OSError is encountered on Windows while trying to lock the file.
Originally mentioned on #147.
On Windows, if the name of the file given is invalid, such as forgetting to to double backspace on windows, the EINVAL message is not accounted for in the error handling.
import filelock

filename = "C:\path\to\lock\but\backslash\is\not\escaped"
with filelock.FileLock(filename):
    pass # waits forever and never completes

If you had just tried to open the file, you would see the following message:
filename = "C:\path\to\lock\but\backslash\is\not\escaped"
f = open(filename)

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 22] Invalid argument: 'C:\\path\to\\lock\x08ut\x08ackslash\\is\not\\escaped'

The issue that is being danced around is it seems PermissionError will randomly occur on os.open() when trying to open the lock file. I have been unable to figure out why Windows raises PermissionError, but that seems somewhat a mute point.
https://github.com/tox-dev/py-filelock/blob/dceb9e5b7e4edd232435521f20efe189fe88f71b/src/filelock/_windows.py#L24-L28
The problem is any error raised, other than the one explicitly handled, ignoring other errors.
This is corrected by ignoring some explicit errors, but allowing other errors to be raised.
This also adds a check for if the path of the lock file is a directory. On Windows, trying to open a path that is a directory as a file would raise a PermissionError that can't be differentiated from the exception that is sometimes raised from just trying to open the file in the middle of a bunch of locking and unlocking.
Renamed utils.raise_on_exist_ro_file(filename) to utils.raise_unwritable_file(filename) to better describe what is does, now that the directory check has been added to it.

Yes, flake. "unwritable" is a word...

I'm actually not sure why I'm getting the flake8 error
tests/test_filelock.py:137:2: PT006 wrong name(s) type in @pytest.mark.parametrize, expected tuple

Anyone have suggestions?


Longest Palindromic Subsequence

@lo-0l  Can you remove the include bits/stdc++.h  because this header is quiet Linux specific and slow down the compilation process.


Fix small typo in seq2seq

Can one of the admins verify this patch?

I signed it!

Jenkins, test this please


Importing rdkit.Chem still loads Qt libraries into memory

Even after applying #3659 rdmolops.so is still linking to Qt libraries, at least on Linux.
It seems like these are transitive dependencies brought in by MolDraw2D: even if rdmolops itself doesn't make use of Qt, it defines MolToSVG(), which adds a dependency on MolDraw2D, so that it gets loaded whenever rdmolops is, and this also brings in the Qt libraries. As mentioned in #3658, this causes problems in systems where Qt is not available.
The best way I can think of to solve this issue is moving MolToSVG() to rdkit.Chem.Draw. I don't love that, because all the "MolTo..." functions are collected together in rdkit.Chem, but it would solve the issue, and since SVG is not really a structure file format (i.e. we cannot import a molecule back from it, there's no "MolFromSVG()"), it kind of makes sense to put it together with the rest of the drawing stuff.
Does that make sense?

Yeah, I'm fine with this being moved to rdMolDraw2D. It shouldn't have ended up in MolOps in the first place.

Yeah, I'm fine with this being moved to rdMolDraw2D. It shouldn't have ended up in MolOps in the first place.


Add support for LLVM 16

Starting with the build changes, lots of assertions due to opaque pointer usage. It still compiles, but taking the type is now a runtime error (which seems like an annoying way to do it).

The great pointer type purge begins - so far, not awful, though there are a few places where there might be some confusion. We have 77 instances of getPointerElementType() left.

Superseded by #658 .


It seems to require an undocumented wrapper

In comparison with react-router-scroll-4, it seems that react-router-scroll-memory comes with some artificial constraints such as requiring a <div> (or similar) wrapper.
To be perfectly clear, this works using react-router-scroll-4:
import React from 'react';
import { BrowserRouter, Switch, Route } from 'react-router-dom';
import { ScrollContext } from 'react-router-scroll-4';

const App = () => (
	<React.Fragment>
		<BrowserRouter>
			<ScrollContext>
				<Switch>
					<!-- routers here -->
				</Switch>
			</ScrollContext>
		</BrowserRouter>

		<Notifications />
		<SnackBar />
	</React.Fragment>
);

render(App, document.getElementById('my-app'));

Similar code does NOT work using react-router-scroll-memory (it renders absolutely nothing):
import React from 'react';
import { BrowserRouter, Switch, Route } from 'react-router-dom';
import ScrollMemory from 'react-router-scroll-memory';

const App = () => (
	<React.Fragment>
		<BrowserRouter>
			<ScrollMemory>
				<Switch>
					<!-- routers here -->
				</Switch>
			</ScrollMemory>
		</BrowserRouter>

		<Notifications />
		<SnackBar />
	</React.Fragment>
);

render(App, document.getElementById('my-app'));

react router scroll memory is not a HOC, for use, place just  in  for catch location. If it is out , location is always '/'.

Thanks, but I'm not sure I understand your comment. Also, not sure how it's related to the <div> container requirement I told about.

yes, the div is required for encapsulate the children's

yes, the div is required for encapsulate the children's

Thanks. And may I know why? As said above react-router-scroll-4 does not require any artificial container and works fine.

Ok, thanks.


Not able to connect to Service Bus after upgrading to the latest version

I am getting the below error while connecting to a service bus using the connection string. It was working fine before upgrading to the latest version. I mainly want to connect to the topics.

<13:03:06> The file C:\Users\Vivek.Nuna\AppData\Roaming\Service Bus Explorer\UserSettings.config is used for the configuration settings.

<13:03:55> The application is now connected to the sb://sb-eu-ci-prem-defaul-0x1.servicebus.windows.net/ service bus namespace.
<13:03:55> MessagingFactory successfully created.
<13:04:08> Failed to retrieve Service Bus queues. Exception: System.TimeoutException: The operation has timed out.
          at ServiceBusExplorer.ServiceBusHelper.GetQueues(String filter, Int32 timeoutInSeconds) in D:\a\ServiceBusExplorer\ServiceBusExplorer\src\Common\Helpers\ServiceBusHelper.cs:line 1594

          at ServiceBusExplorer.Forms.MainForm.<ShowEntities>d__361.MoveNext() in D:\a\ServiceBusExplorer\ServiceBusExplorer\src\ServiceBusExplorer\Forms\MainForm.cs:line 4615

<13:04:08> Failed to retrieve Service Bus topics. Exception: System.TimeoutException: The operation has timed out.
          at ServiceBusExplorer.ServiceBusHelper.GetTopics(String filter, Int32 timeoutInSeconds) in D:\a\ServiceBusExplorer\ServiceBusExplorer\src\Common\Helpers\ServiceBusHelper.cs:line 1749

          at ServiceBusExplorer.Forms.MainForm.<ShowEntities>d__361.MoveNext() in D:\a\ServiceBusExplorer\ServiceBusExplorer\src\ServiceBusExplorer\Forms\MainForm.cs:line 4656

I have upgraded using chocolaty.
https://github.com/paolosalvatori/ServiceBusExplorer?tab=readme-ov-file#upgrading
@SeanFeldman

@paolosalvatori @SeanFeldman @ErikMogensen Could you please help on this?

I'm on 6.0.3 and see no issues. Have you tried a different environment & ASB namespace?

Yes, I have tried different environments and ASB namespaces. It was working fine before upgrading.

I cannot troubleshoot someone else's environment, @viveknuna.
You can try downgrading to the previous version and verifying it's working. If it doesn't see the differences. Try installing a brand new copy in a clean setup and see if that's working for you.
If the build was broken, you'd see many voicing the problem. I'm not saying there's not a chance something is off, but historically, it's usually a local issue rather than the build itself.

It wasn't solved by reinstalling the latest version, But by lowering down to 5.0.18. May be someone may investigate the root cause.

I'm not entirely sure what's causing it, @viveknuna. If there were multiple reports of the same problem, we'd try to help troubleshoot the root cause. But this was the only raised concern. If you have the cycles to look for what could cause the issue on your end between 5.0.18 and 6.0.3, please re-open the issue and share your findings.
Sorry, I don't have a better option now - the reality of a FOSS project.

@viveknuna , have you compared the servicebusexplorer.exe.config file in the release to the one you have? There are some references to assemblies in it that must match the version of service bus explorer that is used.
Another thing that may cause trouble is if you have Microsoft.Service.dll in your GAC. Then it will interfere with Service Bus Explorer. It is possible that there may be another assembly that is in the GAC that interferes.


[iOS] Add spell check suggestions toolbar on tap

Add iOS spell check toolbar to show spell check suggestions, as part of https://github.com/flutter/flutter/issues/34688. Fixes https://github.com/flutter/flutter/issues/119537.
This PR will cause the following to occur on single tap (touch only) if the word tapped is misspelled:

The word will be highlighted.
The toolbar will appear once (after this, the text selection toolbar will be toggled on/off).
If a suggestion in the toolbar is clicked, the misspelled word will be replaced with that suggestion, and the word edge will be selected.

The toolbar shows on single tap up if the word tap is misspelled. Otherwise, the normal behavior takes precedent.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

The actual setting of the updated TextEditingValue is what seems to cause this strange test failure.  All the suspicious things from postFrameCallbacks etc. didn't seem to fix it though.  I'll take a closer look if I have time.


Error in gzfile(file, "rb") : invalid 'description' argument

Hi Garrick,
This is amazing app. I tried run in my pc (Linux) and gave following error:
Using tweets from: NA
Getting Tweet oembed HTML, this may take a minute...
Using {furrr} to speed up the process
Error in gzfile(file, "rb") : invalid 'description' argument
It seems to be in the function
 tweets <- import_tweets(
    TWEETS_FILE,
    tz_global   = tz_global(),
    topic_terms = TOPIC$terms,
    start_date  = TWEETS_START_DATE,
    blocklist   = BLOCKLIST
)

>
> 15.
> gzfile(file, "rb")
> 14.
> readRDS(file)
> 13.
> eval(lhs, parent, parent)
> 12.
> eval(lhs, parent, parent)
> 11.
> readRDS(file) %>% mutate(created_at = lubridate::with_tz(created_at,
>     tz_global())) %>% tweets_since(TWEETS_START_DATE) %>% tweets_not_hashdump() %>%
>     tweets_block(blocklist$status_id, blocklist$screen_name) %>%
>     arrange(desc(created_at)) %>% is_topic_tweet(topic_terms) at functions.R#10
> 10.
> import_tweets(TWEETS_FILE, tz_global = tz_global(), topic_terms = TOPIC$terms,
>     start_date = TWEETS_START_DATE, blocklist = BLOCKLIST)
> 9.
> eval(lhs, parent, parent)
> 8.
> eval(lhs, parent, parent)
> 7.
> import_tweets(TWEETS_FILE, tz_global = tz_global(), topic_terms = TOPIC$terms,
>     start_date = TWEETS_START_DATE, blocklist = BLOCKLIST) %>%
>     filter(is_topic) %>% tweet_cache_oembed() at global.R#57
> 6.
> ..stacktraceon..({
>     library(shiny)
>     library(shinydashboard)
>     library(forcats) ...
> 5.
> eval(exprs, envir)
> 4.
> eval(exprs, envir)
> 3.
> sourceUTF8(file.path.ci(appDir, "global.R"))
> 2.
> appParts$onStart()
> 1.
> runApp()

Just one question what mean %||%? ( I never saw nothing like this).
I found in %||% <- function(x,y)

Do you have a collection of tweets stored in data/tweets.rds? It seems like you might not have collected tweets yet, which the app in the master branch of this repo doesn't do for you.
The %||% is called a null coalescing operator and x %||% y returns y is x is NULL.

Thanks


dlmalloc is larger on wasip1 target than unknown-unknown

Hi, I am just curious about the reason behind this behavior: https://users.rust-lang.org/t/code-size-of-wasip1-larger-than-unknown-unknown/122789
For wasi, is that we should include our own allocator?

I believe what's happening there is that the Rust wasm32-wasip1 target is using wasi-libc by default for malloc, not this crate. You can still use this crate though with #[global_allocator] instead.


fix error when request params contains number

hello
I found that RequestValidation has invalid process when query params contains number.
so I fixed it.
Could you please merge this pull request?
thank you.

We can't distinguish string from integer/float in URL query parameters, so rack-json_schema always assumes them as strings. If you need to validate number-like strings in URL query parameters, you can use pattern property of JSON Schema.

oh, I see.
thank you for your advice!


Create fazeID.md

Project Abstract
Faze ID is bringing privacy-preserving face recognition to the browser. The primary applications of Faze ID are Sybil resistance and authentication. The grant proposal encompasses research, model evaluation, and deployment.
Grant level

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x ] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

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

Thanks for the application @jettblu, I was a fan of your previous Distributed Key Management grant. However, it's not immediately clear to me what Polkadot tech is involved for this project.

Are you storing hashes on-chain, or how else are you leveraging substrate tech here?
Also, I'm curious as to why you are waiting until Milestone 3 to do the research part? Wouldn't it be more helpful to do the research first before building it?
It sounds like the tech will be fully automated, so what kind of verifications can be done to guard against false positives and that sort of thing?
Will other wallet projects be able to reuse the product for their wallets?

Hi @keeganquigley! Thanks for the quick response. I've included responses to your concerns below.

Overall, this project does not use the Polkadot tech stack but is intended to serve as infrastructure for Polkadot projects. Many wallet and defi projects built on Substrate would benefit from a Sybil resistance solution. That's what we are trying to provide with Faze.
I believe the paper would benefit from being released as the final milestone. This will allow us to include our implementation in the paper and reference evaluation metrics collected in milestone two. I also expect that our final implementation will diverge from our initial ideas. By doing the paper last, we will have more flexibility with our implementation, hopefully leading to a more useful result.
False positives are a concern. The evaluation phase will allow us to quantify and improve the error rate. However, we don't expect the model to have 100% accuracy. And in fact, we don't need perfection. Most projects (including our own wallet) would benefit from a probabilistic guarantee that some percentage of users are not bots.
Yes! One of our primary goals is to make a Sybil resistance system that can be used across the ecosystem. We will run a hosted version of the backend service (free and open source) and provide instructions for projects to set up their own backend validation system.  As mentioned in the proposal, we would like this to be a plug-and-play system where developers can benefit from Sybil resistance by dropping in a React component and including a few lines of verification logic.

I know this was a long response. Please let me know if you have any questions. I am open to any feedback or modification requests. For more info, you can also view the Faze website.

Thanks for the answers @jettblu much appreciated. I will mark the application as ready for review and share it with the committee. Normally we ask for our tech stack to be used somehow but considering the price, it's possible the committee might be willing to make an exception. A couple more questions:

Who would be the main user base for the product? I don't see that in the application.
We only fund the tech development itself, so I don't think that paying research participants can be covered by the grants program. Would you be willing to remove this? Also, if you are willing to lower it to a level 1 grant only two approvals will be needed.

The main user base of the platform would be application developers. In the application, I mention an example use case of the Nova wallet airdropping users 'seed money' and using Faze to mitigate bot attacks. I can also imagine Polkadot Defi protocols or social networks using Faze to help with Sybil resistance.
And yes! I did not realize the research request was out of bounds. I'll update the pr/amounts and denote the grant as tier one.
Let me know if I've missed anything. Thanks again for helping to clarify the scope.

Thanks @jettblu one last question, have you done any temperature checks anywhere to see if this is needed by the community?

Hi, @keeganquigley; thanks for updating the PR. I also updated the application itself to reflect our conversation above. And yes, I have spoken to several developers and teams. For example, at EthDenver in March, a central theme was the lack of decentralized sybil resistance solutions outside Gitcoin Passport. In addition, several CMU alums I have spoken to are also building projects/companies that need a clear way to filter low-quality participants and prevent spam. If successful, Faze will provide this solution (free and open source).

Hi @jettblu !
Thank you for this super interesting grant application.
Will the AI/ML model(s) used in the frontend be released as well in an open source repo?
And will the model building pipeline and code also be released in open source?
Also, can you elaborate more on how the "hashing" works? Is it some kind of internal model embedding?
If it's the latter, will it be possible for someone with access to the model to get an approximation of the face image using the hash?
I am super curious about this use case, can you please share links and infos to educate me as much as possible?
Thank you!

Hi @randombishop !
The model pipeline and fitted weights will all be open-source. You can view some initial modeling here. Of note, the first 20 or so principal components account for over 90% of the variance in facial landmarks. This metric was obtained by running tests on the 'Faces in the Wild' dataset. However, PCA alone is not sufficient for production recognition. Our initial testing showed too many false positives. The final model will likely be a custom NN inspired by industry standards like Facenet.
Locality-sensitive hashing (LSH) tries to maximize hash collisions for similar values. I've created a simple library for core methods like minhash, which can be found here. In general, LSH allows you to compute the similarity between two pieces of data efficiently. In addition, LSH minimizes the amount of data that must be transferred from the client and stored on the authentication server. Minhash is insufficient for our recognition task as we deal with non-overlapping face landmark values. I am currently exploring alternatives like neighbor-sensitive hashing.
I am still exploring the privacy implications of face encodings. The exact privacy details will likely depend on the encoding method. However, all encoding computation is done on the client, so the server can never access the original image/video feed.
Most of the work/research I mentioned above has been done in the last few weeks, so there is still a lot to explore and refine. I'm happy to provide more details, but I hope this clarifies some of your questions.

Hi @jettblu !
My opinion is that this is a great line of research worth pursuing; but the core part of it is the model encoding the face information; the guarantees of privacy, deep fake and collision resistance, etc. And these are not directly related to the Polkadot ecosystem.
Once you have a POC solving all these problems, I guess integrating the technology into a Polkadot wallet, building a parachain to manage the data, or other decentralization approach could make sense to be funded by W3F.
But in its current state, it feels like a ML/AI R&D project, and I personally won't approve it.

Hi @semuelle and @randombishop; I appreciate your skepticism—however, a few clarifying points.

No encodings are being stored on the blockchain. The first implementation will run on a private authentication server. We will provide a public endpoint, but projects can also set up their own backend.
The primary application is sybil resistance. An example I cited in the grant is protecting airdrops. In this case, Faze would provide a probabilistic guarantee that, say, 85% of the claimers are unique humans. This is an incredibly valuable use case for decentralized ecosystems like Polkadot, where there are few ways to protect against spam/bots.
There will be integrations. AI is the tool, but again, we are focused on tangible impact within the ecosystem. By the end of the grant period, we will integrate Faze within the open-source Kryptik wallet (to verify initial airdrops to users). We will also release a plug-and-play React component that can be used by other wallets/defi projects through the Polkadot/Kusama space.  Note that while there has been substantial research on modeling techniques, there is not yet a single implementation available for web3/browser-based applications.

This is a research project, and, as such, there is no guarantee of success. However, I disagree with the claim that R&D on privacy & model characteristics has little relation to the ecosystem. A strong sybil resistance scheme relies on these properties. In addition to providing the authentication component itself, we need to provide performance metrics that can only be obtained by R&D.
Please let me know if there are any further modifications I can make or use cases you're interested in. I believe strongly in providing a privacy-first sybil resistance scheme, and I think Faze would be a big step in that direction.

You make good points @jettblu ; but just to clarify what I meant by "not directly related to the Polkadot ecosystem" because I probably didn't phrase it correctly.
I agree that it's a great innovation for the blockchain space in general, but I meant that it also works for Ethereum or any other blockchain; and solves sybil resistance in general, not specifically for Polkadot ecosystem.
The frontend and models can be re-used across all blockchains, while our program focuses on contributions to the polkadot/kusama ecosystem and codebase in particular.

@randombishop You and the reviewers know the mission of the Web3 Foundation better than anyone else. However, I would say that the extensibility of Faze or any other cross-chain solution is a plus, not a minus.
The primary requirement is that grants interoperate with the Polkadot/Kusama ecosystem. Faze does this. And as the proverbial 'sprinkles on the top,' it also can integrate with any other protocol.
The bottom line is that Faze seeks to solve a fundamental problem (Sybil resistance) in the Polkadot ecosystem.
Just to be clear, I am not trying to quibble over the purpose of the grants program; I am just trying to clarify the 'value add' that Faze would provide.

@takahser, thanks for sharing your concerns. I've addressed your points below.
1) Privacy
Correct. We want to use client-side feature calculation and locality-sensitive-hashing to help protect user privacy. As mentioned in one of the comments above, the full privacy implications of this approach will depend on the precise implementation. However, we can guarantee that no raw video or images will be sent to the server for processing. This is already a big step for privacy. As for compliance, our solution will be open source. That means anyone can run a hosted version of the auth server. While that doesn't remove all compliance considerations, it provides more flexibility for each provider to set up policies.
2) Security
Both camera spoofing and the lack of a trusted execution environment are part of the challenge. Liveness detection will help with the spoofing vector. In addition, we are developing Faze primarily as a Sybil-resistance tool. The system will not be perfect, but if we can guarantee that 80% of users who pass validation are human, that is a big win for apps that struggle with spam and bots.
3) Program Fit
You are correcting that the primary technical challenge is related to machine learning (and privacy). In addition, we are committed to building a one-line react-based auth plugin for developers, hence the npm and react-related deliverables. However, Faze is specifically meant to benefit permissionless networks like blockchains. Since most applications and potential users are decentralized protocols, it makes sense (in our mind, at least) to apply for a W3F grant.
If you have any more questions or concerns, please don't hesitate to let me know. Faze would be a valuable tool for many applications, including our own wallet, and we would deeply appreciate support from the foundation.

Hey @keeganquigley, I reviewed the RFP list and found a project (proposed. by @randombishop) I'm excited about. However, I have a few questions. What do you think is the best way to communicate on open RFPs? Thanks for your help!

Hi @jettblu glad to hear you are interested in this RFP! Email works fine at<EMAIL_ADDRESS>or we can start a private chat room in Element as well, either works! Just let me know.

Ok, thanks for letting me know. I prefer to use Element. My username is 'jettblu'. I have already joined the W3F Grants Community room.


Add RecordSet support for route53 controller

Issue:
https://github.com/aws-controllers-k8s/community/issues/1545
Description of changes:
Adds support for RecordSets in Route53 and corresponding E2E tests. This includes support for all record types and routing policies.
Some previous conversations for how to implement this were discussed here:

https://kubernetes.slack.com/archives/C0402D8JJS1/p1694054604699869
https://kubernetes.slack.com/archives/C0402D8JJS1/p1695030078194489

Changes made to following files/directories (other changes are all code-gen'ed):

generator.yaml
pkg/resource/record_set/hooks.go
templates/hooks/record_set/
test/e2e/

Generator results:
make build-controller SERVICE=route53
building ack-generate ... ok.
==== building route53-controller ====
Copying common custom resource definitions into route53
Building Kubernetes API objects for route53
Generating deepcopy code for route53
Generating custom resource definitions for route53
Building service controller for route53
Generating RBAC manifests for route53
Running gofmt against generated code for route53
Updating additional GitHub repository maintenance files
==== building route53-controller release artifacts ====
Building release artifacts for route53-v0.0.8
Generating common custom resource definitions
Generating custom resource definitions for route53
Generating RBAC manifests for route53

E2E results:
[gw1] [ 25%] PASSED tests/test_hosted_zone.py::TestHostedZone::test_create_delete_private
[gw0] [ 50%] PASSED tests/test_hosted_zone.py::TestHostedZone::test_create_delete_public
[gw2] [ 75%] PASSED tests/test_hosted_zone.py::TestHostedZone::test_crud_tags
[gw4] [100%] PASSED tests/test_record_set.py::TestRecordSet::test_crud_simple_record

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/ok-to-test

@kunhwiko I opened aws-controllers-k8s/pkg#23 - awaiting for another ACK maintainer to ship it and we'll have in code-gen soon

Looks like it got merged!

@PT-GD Oh yeah, you're right - I'll look to regenerate code for this PR shortly

@PT-GD Oh yeah, you're right - I'll look to regenerate code for this PR shortly :)

Any update?

@PT-GD Hey there, I didn't get the chance last week since I was traveling - will get to this hopefully by Monday

/test all

Expecting to merge this week. Just want to figure out if there is a way we can omit the RecordChange type from the Spec...

/unhold


headers ending in "id" are displayed correctly

I had problems with headers, ending with "id". Function titleize cuts "id".

Weird, thanks for catching this.


pycurl_manager testHeadRequest unit test fails in both py2/py3

Impact of the bug
WMCore in general
Describe the bug
As mentioned in this GH issue: https://github.com/dmwm/WMCore/pull/10501
the test
WMCore_t.Services_t.pycurl_manager_t.PyCurlManager:testHeadRequest

fails in both python2 and python3 unit tests
How to reproduce it
Run the unit test above
Expected behavior
Investigate and fix this unit test for both python stacks and/or provide a real fix (src/python) if it's buggy over there.
Additional context and error message
These will vanish in 30 days from now, but here is their jenkins output in both py2 and py3:
https://cmssdt.cern.ch/dmwm-jenkins/job/DMWM-WMCore-PR-test/11794/testReport/junit/WMCore_t.Services_t.pycurl_manager_t/PyCurlManager/testHeadRequest/
https://cmssdt.cern.ch/dmwm-jenkins/job/DMWM-WMCore-PR-test/11794/testReport/junit/WMCore_t.Services_t.pycurl_manager_t/PyCurlManager/testHeadRequest_2/

@mapellidario Dario, I suspect this issue has already been solved. Could you please self-assign this issue and check what's the current status? Feel free to close it if already resolved. Thanks


Update Docker config.

Resolves #697
Things updated:

Docker Compose file
Env File
Reduced image sizes without quality degradation
Updated readme to reference repo images rather than external, making loading quicker
Added healthchecks to images + postgres in compose
Changed postgres to use alpine version, resulting in a smaller image size.
Added Dependabot. This will assist with version updates and vulnerability scans.

It seems like the force push caused a lot of file changes, and now the branch has too many unrelated changes compared to main. Could this be redone so the PR can be reviewed properly?
Also, changing the base docker image is something that requires a lot of testing to ensure playwright runs correctly. I tried a lot too, to reduce the size, but playwright kept failing to run. Have to be careful about this, but a welcome change for sure.

It seems like the force push caused a lot of file changes, and now the branch has too many unrelated changes compared to main. Could this be redone so the PR can be reviewed properly?
Also, changing the base docker image is something that requires a lot of testing to ensure playwright runs correctly. I tried a lot too, to reduce the size, but playwright kept failing to run. Have to be careful about this, but a welcome change for sure.

Sure thing! I'll resubmit the PR from a fresh pull so it's clean!
In regards to the base image, it's purely on postgres, and not touching server or client in this case.

@modem7 No, we could do it all in one PR to save time :) I don't have a lot of time to manual test the app as well, but we can take our time and merge this over the weekend maybe to get more confidence.


Set default units (length, angle...) when building GDML object

It would be useful to choose the default units (mm for length etc.) when building the Gdml.

A simple option without violating the gdml structure is to add some kind of export options like this:
gdml.encodeToString{
  defaultlUnit = LUnit.MM
}

Would it suffice?

yes, that is exactly what I wanted.

Fixed in dev, see https://github.com/mipt-npm/gdml.kt/blob/e01cd969ae621ba4661ef8d51fcb72e0a28efc1e/src/commonMain/kotlin/space/kscience/gdml/GdmlShowCase.kt#L424

And default units were wrong after all.  I fixed that as well.

Good to know, this will solve the discrepancies between the exported gdml and the renderer I was observing.


fix prun pod with container

fix #4346
This PR sets c.Force to true if user reply 'y' to system prune confirmation question.
Signed-off-by: Qi Wang<EMAIL_ADDRESS>

@mheon @TomSweeneyRedHat PTAL.
I am confused by the man page --force Do not prompt for confirmation. This cli value has been used not only to control the prompt of the confirmation.

This seems VERY dangerous. We're only supposed to be removing unused containers and pods - setting force is directly counter to that.

I think the original suggestion - removing containers before pods - might be more suitable here. We want to prune unused containers, then prune any pod with no containers but the infra container, then prune unused images.

(Would need to make sure we don't accidentally prune infra containers when we prune the containers, though)

The use of --force to set force for pruning pods and containers also seems concerning... I don't think we should be doing that.

We don't prompt, the way that Docker does, So we should just add this as a no-op.
If you run docker image prune
It prompts you to say "Are you sure"  The --force gets rid of the prompt.
So Just add the flag so that we can work with existing scripts.


An exception should be thrown if SetRelativeLayout detects a Pos.View with Target == this.Superview

Describe the bug
Running this unit test will fail because the ContentBottomRightCorner isn't draw.
	[Fact, AutoInitShutdown]
	public void ContentBottomRightCorner_Draw ()
	{
		var size = new Size { Width = 20, Height = 10};
		var sv = new ScrollView {
			X = 1,
			Y = 1,
			Width = 10,
			Height = 5,
			ContentSize = size
		};
		string text = null;
		for (int i = 0; i < size.Height; i++) {
			text += "*".Repeat (size.Width);
			if (i < size.Height) {
				text += '\n';
			}
		}
		var view = new View { Width = size.Width, Height = size.Height, ColorScheme = Colors.ColorSchemes ["Error"], AutoSize = true, Text = text };
		sv.Add (view);
		Application.Top.Add (sv);
		Application.Begin (Application.Top);

		TestHelpers.AssertDriverContentsWithFrameAre (@"
 *********▲
 *********┬
 *********┴
 *********▼
 ◄├──┤░░░► ", _output);

		var attrs = new Attribute [] { Colors.ColorSchemes ["Toplevel"].Normal, Colors.ColorSchemes ["Toplevel"].Focus, Colors.ColorSchemes ["Error"].Normal };

		TestHelpers.AssertDriverAttributesAre (@"
000000000000
022222222210
022222222210
022222222210
022222222210
011111111110
000000000000", null, attrs);

	}

Changing the code in the ScrollBarView as following the test pass and I will fix in the #3181.
-			_contentBottomRightCorner.X = Pos.Right (Host) - 1;
-			_contentBottomRightCorner.Y = Pos.Bottom (Host) - 1;
+			_contentBottomRightCorner.X = Pos.AnchorEnd (1);
+			_contentBottomRightCorner.Y = Pos.AnchorEnd (1);

-	void ContentBottomRightCorner_DrawContent (object sender, DrawEventArgs e) => Driver.SetAttribute (Host.HasFocus ? ColorScheme.Focus : GetNormalColor ());
+	void ContentBottomRightCorner_DrawContent (object sender, DrawEventArgs e)
+	{
+		Driver.SetAttribute (Host.HasFocus ? ColorScheme.Focus : GetNormalColor ());
+		// I'm forced to do this here because the Clear method is
+		// changing the color attribute and is different of this one
+		Driver.FillRect (Driver.Clip);
+		e.Cancel = true;
+	}

What surprises me is that Pos.Right(Host) - 1 should be the same as Pos.AnchorEnd(1). I also tried it with just Pos.Right (Host) without success. I noticed that the ClipToBounds method sets the Driver.Clip to the correct location but with an empty size (0,0). I could be wrong but something is strange here, perhaps with the call Driver.Clip = Rect.Intersect (previous, BoundsToScreen (Bounds));.
In the v1 this was working.
https://github.com/gui-cs/Terminal.Gui/blob/fcad17853e78bc537650c40e8e273462a963ca0a/Terminal.Gui/Views/ScrollBarView.cs#L114-L115
I would appreciate your opinion on this please.

I'm confused. The test just tests ScrollBar. ScrollBar has no dependencies (that I'm aware of) on ScrollBarView. How can changing code in ScrollBarView make a test that never references ScrollBarView pass/fail?
I suggest you focus exclusively on ScrollBar and ignore ScrollBarView (unless I misunderstood you).

The test use a ScrollView which also use ScrollBarView. I didn't understanded about the ScrollBar.

The test use a ScrollView which also use ScrollBarView. I didn't understanded about the ScrollBar.

My bad. I got ScrollBarView and ScrollView backwards. Nevermind.
Here's some thoughts:

this is the ScrollView; this.SuperView is Application.Top. Host == Application.Top.
Host.SuperView.Add(this) adds the ScrollView to Application.Top
_contentBottomRightCorner is a subview of this (_contentBottomRightCorner.SuperView is this).

Pos.Right(Host) - 1 should be the same as Pos.AnchorEnd(1)

Perhaps it should be but I don't think it is today. There's no code in SetRelativeLayout that factors in the fact that Host may have Adornments.
Right?

Perhaps it should be but I don't think it is today. There's no code in SetRelativeLayout that factors in the fact that Host may have Adornments.
Right?

I'm not sure. It is not a problem with SetRelativeLayout because it returns the correct dimension (1,1). The BoundsToScreen (Bounds) method is also returning the right location and the dimension remains as (1,1,). The Rect.Intersect method returns the same correct location and the empty dimension (0,0). Therefore, my question is, if the correct location is found in the superview area, then the Rect.Intersect method, which in turn calls the Rect.FromLTRB method, should return the dimension of (1,1). Am I mistaken?

FWIW, here's a version of your test that does not depend on Application and is a bit simpler. It passes/fails just as the one you described.
	[Fact]
	[SetupFakeDriver]
	public void ContentBottomRightCorner_Draw ()
	{
		((FakeDriver)Application.Driver).SetBufferSize (30, 30);

		var top = new View {
			Width = 30,
			Height = 30,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Blue, Color.Yellow)
			}
		};

		var size = new Size { Width = 20, Height = 10 };
		var sv = new ScrollView {
			X = 1,
			Y = 1,
			Width = 10,
			Height = 5,
			ContentSize = size,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Red, Color.Green)
			}
		};

		var view = new View {
			Width = size.Width,
			Height = size.Height,
			ColorScheme = top.ColorScheme
		};
		sv.Add (view);

		sv.AutoHideScrollBars = false;
		sv.ShowVerticalScrollIndicator = true;
		sv.ShowHorizontalScrollIndicator = true;

		top.Add (sv);
		top.BeginInit ();
		top.EndInit ();

		top.LayoutSubviews ();

		top.Draw ();

		TestHelpers.AssertDriverContentsWithFrameAre (@"
          ▲
          ┬
          ┴
          ▼
 ◄├──┤░░░► ", _output);

		var attrs = new [] { Attribute.Default, new Attribute (Color.Red, Color.Green), new Attribute (Color.Blue, Color.Yellow),
		};

		TestHelpers.AssertDriverAttributesAre (@"
00000000000
02222222221
02222222221
02222222221
02222222221
01111111111", null, attrs);
	}

I think the issue is related to the fact that Pos objects cannot reference a superview (or, in this case the superview's superview). Dim is ok. But Pos is not because Frame != Bounds.
We need a focused Pos unit test that proves/disproves this.

This unit tests doesn't depended of the ScrollView and I think it's better to debug. When two rectangles touch each other, the last one that draws is the one that prevails when the latter is not a subview of the first, I think. But reducing one unit from right to left is still within the previous rectangle, that is, within the superview and should have a dimension of 1.
	[Fact]
	[SetupFakeDriver]
	public void AnchorEnd_Equal_Right ()
	{
		((FakeDriver)Application.Driver).SetBufferSize (30, 30);

		var top = new View {
			Width = 30,
			Height = 30,
			ColorScheme = new ColorScheme { Normal = Attribute.Default }
		};

		var super1 = new View {
			Id = "super1",
			X = 1,
			Y = 1,
			Width = 4,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Red, Color.Green)
			},
			Text = "123"
		};
		var view1 = new View {
			Id = "view1",
			X = Pos.AnchorEnd (1),
			Width = 1,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Blue, Color.Yellow)
			},
			Text = "4"
		};
		super1.Add (view1);
		var super2 = new View {
			Id = "super2",
			X = 1,
			Y = 2,
			Width = 4,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Red, Color.Green)
			},
			Text = "123"
		};
		var view2 = new View {
			Id = "view2",
			X = Pos.Right (super2) - 1,
			Width = 1,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Blue, Color.Yellow)
			},
			Text = "4"
		};
		super2.Add (view2);

		top.Add (super1, super2);
		top.BeginInit ();
		top.EndInit ();

		top.LayoutSubviews ();

		top.Draw ();

		TestHelpers.AssertDriverContentsWithFrameAre (@"
 1234
 1234", _output);

		var attrs = new [] {
			Attribute.Default, new Attribute (Color.Red, Color.Green),
			new Attribute (Color.Blue, Color.Yellow)
		};

		TestHelpers.AssertDriverAttributesAre (@"
000000
011120
011120
000000", null, attrs);
	}

This unit tests doesn't depended of the ScrollView and I think it's better to debug. When two rectangles touch each other, the last one that draws is the one that prevails when the latter is not a subview of the first, I think. But reducing one unit from right to left is still within the previous rectangle, that is, within the superview and should have a dimension of 1.
	[Fact]
	[SetupFakeDriver]
	public void AnchorEnd_Equal_Right ()
	{
		((FakeDriver)Application.Driver).SetBufferSize (30, 30);

		var top = new View {
			Width = 30,
			Height = 30,
			ColorScheme = new ColorScheme { Normal = Attribute.Default }
		};

		var super1 = new View {
			Id = "super1",
			X = 1,
			Y = 1,
			Width = 4,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Red, Color.Green)
			},
			Text = "123"
		};
		var view1 = new View {
			Id = "view1",
			X = Pos.AnchorEnd (1),
			Width = 1,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Blue, Color.Yellow)
			},
			Text = "4"
		};
		super1.Add (view1);
		var super2 = new View {
			Id = "super2",
			X = 1,
			Y = 2,
			Width = 4,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Red, Color.Green)
			},
			Text = "123"
		};
		var view2 = new View {
			Id = "view2",
			X = Pos.Right (super2) - 1,
			Width = 1,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Blue, Color.Yellow)
			},
			Text = "4"
		};
		super2.Add (view2);

		top.Add (super1, super2);
		top.BeginInit ();
		top.EndInit ();

		top.LayoutSubviews ();

		top.Draw ();

		TestHelpers.AssertDriverContentsWithFrameAre (@"
 1234
 1234", _output);

		var attrs = new [] {
			Attribute.Default, new Attribute (Color.Red, Color.Green),
			new Attribute (Color.Blue, Color.Yellow)
		};

		TestHelpers.AssertDriverAttributesAre (@"
000000
011120
011120
000000", null, attrs);
	}

The issue should be reproducible using just three views (maybe just two). You are way over complicating this by using colors etc...
Let's think about this a bit.
What does view.X = Pos.Right (superView) - 1 mean?

Have the X Pos of view to track the right side of the superView minus 1 column.
The "right side" is defined as superView.Frame.Right which is superView.Frame.X + superView.Frame.Width.  - The  -1 is odd because if superView.Frame.X = 0 and superView.Frame.Width = 1  then superView.Frame.X + superView.Frame.Width = 1, so subtracting 1 would give 0, which is NOT the right side of the superView.

In the face of Adornments, given there's no existing code (it would be in SetRelativeLayout) that deals with GetAdornmentsThickness using Pos.Right (superView) (with a  - 1 or not) makes no sense.
But, I'm still not sure where the bug is here, because if my thinking above is correct, this would work, but it doesn't:
var view2 = new View {
			Id = "view2",
			X = Pos.Right (super2),
			Width = 1,
			Height = 1,
			ColorScheme = new ColorScheme () {
				Normal = new Attribute (Color.Blue, Color.Yellow)
			},
			Text = "4"
		};
		super2.Add (view2);

Here's a set of minimal tests:
	[Theory]
	[SetupFakeDriver]
	[InlineData (0, 0)]
	[InlineData (1, 1)]
	public void Pos_AnchorEnd_1_Offset_Super (int offsetX, int offsetY)
	{
		var super = new View {
			Id = "super",
			X = offsetX,
			Y = offsetY,
			Width = 2,
			Height = 2,
		};
		var view = new View {
			Id = "subView",
			X = Pos.AnchorEnd (1), // Pos.Right(super) - 1,
			Width = 1,
			Height = 1,
		};
		super.Add (view);

		super.BeginInit ();
		super.EndInit ();

		Assert.Equal (new Rect (offsetX, offsetY, 2, 2), super.Frame);
		Assert.Equal (new Rect (1, 0, 1, 1), view.Frame);
	}

	[Theory]
	[SetupFakeDriver]
	[InlineData (0, 0)]
	[InlineData (1, 1)]
	public void Pos_Right_Minus_1_Offset_Super (int offsetX, int offsetY)
	{
		var super = new View {
			Id = "super",
			X = offsetX,
			Y = offsetY,
			Width = 2,
			Height = 2,
		};
		var view = new View {
			Id = "subView",
			X = Pos.Right (super) - 1,
			Width = 1,
			Height = 1,
		};
		super.Add (view);

		super.BeginInit ();
		super.EndInit ();

		Assert.Equal (new Rect (offsetX, offsetY, 2, 2), super.Frame);
		Assert.Equal (new Rect (1, 0, 1, 1), view.Frame);
	}

super.Frame = {(1,1,2,2)}
super.Frame.Right = 3 (X + Width/1 + 2 = 3)
Thus view.X, which is Pos.Right - 1 is PosView.Anchor(10) - 1 (10 because FakeDriver defaults to 10,10).
PosView.Anchor(10) is therefore 3. Thus PosView.Anchor(10) - 1 is 2, which is the Actual above.

There's no way for a Pos object to know that the Target view is a Superview. Thus:

Pos.View does not support Target being Superview.

It is unclear why this worked in v1. But it will not work in v2.

The new title is concerning.
Property getters are typically not supposed to throw exceptions unless there is a really really good reason for doing so.
From the property design guidelines:

❌ AVOID throwing exceptions from property getters.
Property getters should be simple operations and should not have any preconditions. If a getter can throw an exception, it should probably be redesigned to be a method. Notice that this rule does not apply to indexers, where we do expect exceptions as a result of validating the arguments.

I implemented a POC:
case Pos.PosView posView:
	if (posView.Target == SuperView) {
		throw new InvalidOperationException ();
	}
	newLocation = pos?.Anchor (superviewDimension) ?? 0;
	newDimension = Math.Max (GetNewDimension (dim, newLocation, superviewDimension, autosizeDimension), 0);
	break;

The good news is the only library code that appears to violate this is ScrollBarView. The bad news is a BUNCH of unit tests violate it.  And some Scenarios.

I implemented a POC:
case Pos.PosView posView:
	if (posView.Target == SuperView) {
		throw new InvalidOperationException ();
	}
	newLocation = pos?.Anchor (superviewDimension) ?? 0;
	newDimension = Math.Max (GetNewDimension (dim, newLocation, superviewDimension, autosizeDimension), 0);
	break;

The good news is the only library code that appears to violate this is ScrollBarView. The bad news is a BUNCH of unit tests violate it. And some Scenarios.
That code all function correctly because, by accident, the SuperViews in question have .X == .Y == 0.

Hm.
Maybe a good idea to tag those tests with a TODO or a [Trait] or whatever, if they are still otherwise valid tests, so they can be tackled when I make the pass over the unit tests?

Unless, of course, you intend to fix it now or otherwise before that.

Unless, of course, you intend to fix it now or otherwise before that.

They should be fixed as part of whatever PR is created to fix this Issue.

They should be fixed as part of whatever PR is created to fix this Issue.

@ tig do you want I fix this on the #3181 with a commit referencing this issue?

They should be fixed as part of whatever PR is created to fix this Issue.

@ tig do you want I fix this on the #3181 with a commit referencing this issue?

I already fixed the ScrollBarView in this commit https://github.com/BDisp/Terminal.Gui/commit/e95f50b3c544276d6ec0a540b017c9aa10f12fd1.
It can be up to you to throw the exception if you don't mind, thank you.

Let's do it separately. This PR is already "epic" enough ;-)

Let's do it separately. #3181 is already "epic" enough ;-)

Now you've given me flashbacks of dealing with Jira. 😨

@tig do you have intentions of throwing the exception or this issue can be closed?

Yes I do. Please leave it open.

This is no longer relevant. Closing.


Error count is not showing up in the status bar when building TypeScript node.js project.

VSCode Version: 0.10.12-alpha
OS Version: WIndows10

Steps to Reproduce:

Create a TypeScript->Node.js->BlankConsoleApp in Visual Studio.
Launch VSCode and open project folder.
Configure tasks.json by selecting typescript setting.
Keep the default setting for tasks.json and compile the project with: CTRL+SHIFT+B.
Verify error message in the output window and status bar.

Actual: Status bar is showing 0 error.

There aren't any compile errors reported from the task that's why the count is still 0. The error comes from starting the compiler. If this happens we open the console. In your example you are simply missing the tsconfig.json file.


Documentation: PR template points to wrong documentation

Problem
the PR template points to https://nixos.org/manual/nixpkgs/unstable/#reviewing-contributions-package-updates instead of
https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#reviewing-contributions

Add a :+1: reaction to issues you find important.

#298333
I kindly ask you to just create the PR with this really trivial change instead of creating an issue.

it's only trivial if you have experience with how github works.  i had no idea the template was controlled by a file within the repo and not some option in the settings.


[BUG] Live timing recording stops after 2 hours

Describe the issue:
When recording live timing data with the fastf1.livetiming save command, the recording stops every time exactly after 2 hours with the message Timeout - received no data for more than 60 seconds!. The data stream doesn't actually stop though - as by restarting the same command you can immediately see new messages.
Maybe this could be a timeout on their server side and FastF1 should send a heartbeat of some sorts, or it should "renew" the signalr connection? I'm not too familiar with the signalr protocol :/
Reproduce the code example:
python3 -m fastf1.livetiming save livetiming.txt

Error message:
# After 2 hours
WARNING: Timeout - received no data for more than 60 seconds!
WARNING: Exiting...

That's not a bug really, it's documented in the "Important Notes" here https://docs.fastf1.dev/livetiming.html#important-notes
Yes, that is some kind of server side disconnect. I don't know of any way to send a keep-alive message to prevent this. Therefore, the solution currently is to start overlapping recordings. The duplicate messages in the overlapping data will be automatically be dealt with when loading the data.

it's documented in the "Important Notes" here https://docs.fastf1.dev/livetiming.html#important-notes

Oops, sorry, I didn't pick that up. I guess there's nothing we could do to solve the issue then. Feel free to close this issue if you want.

Not saying that there isn't a way to implement some way to keep the connection alive. The problem is, this is kind of low priority as there are barely any sessions each year where this is relevant. Furthermore, it's a bit of a niche feature. And few sessions where this is relevant means few opportunities to test it.


Add note for (Check available types with _$ resin devices supported)

Moved from https://github.com/resin-io/docs/pull/403

Fixes ages ago, closing.


Wrong layout in 'Order List'.(Company)

Describe the bug
Wrong layout , spelling mistake(spelling of 'Type' is written as 'Tpye' ) in 'Order List' and no space between colon(:) and text in Order Transaction History.(See the attached fig.)
To Reproduce
Steps to reproduce the behavior:
1.Enter in the address bar-pulseptt.com
2.Login With Id and Password.
UserName-titan
Password-123456789
3.Click on "Order List"  and then  Order Transaction History.
Expected behavior
A proper alignment with correct layout must be present and spelling of 'Type' is written as 'Tpye' must be corrected.
Desktop (please complete the following information):
OS: Windows 10
Browser: Version 100.0.4896.60 (Official Build) (64-bit)
Version: [<IP_ADDRESS>]
Order Transaction History-

Order List-

please give a detail description of the issue.

In order list , It is written 'S. No' like S.
No