rework browser optimizeDeps

Current heuristics of optimizeDeps.entries: ["routes/**"] turns out to be a bit erroneous since it tries to pre-bundle entire server dependency and causes issues (warning?) for examples

@node-rs/argon2 in https://github.com/hi-ogawa/lucia-auth-examples/pull/1#discussion_r1675537887
bcrypt in https://github.com/hi-ogawa/next-learn/pull/1

It's not so critical since it shouldn't be that hard to manually identify such "server heavy" deps and configure by themselves, but the error message looks quite shocking at first for new users, so probably need to do something.

Simplest heuristic would be to crawl only local files (e.g. under app/) and find "use client" on our side, then use it as optimizeDeps.entries.

See https://github.com/hi-ogawa/vite-plugins/pull/560#issuecomment-2228078019


Sample Pages should link to their folders on GitHub

Is this a totally new sample, an addition to an existing sample page, or a modification of an existing sample page?

[ ] New sample
[ ] Addition to existing sample
[x] Modification to existing sample

If this is an addition/modification to an existing sample page, which one?
All Sample Pages
Additional context
There's a lot of samples that have additional code that's not always shown on the page, or helper classes. It'd be great if the Documentation section also provided a link to GitHub for that sample; so that it's easier to access and view those, since that code isn't always visible in the application.
E.g. the VariedImageSizeLayout.cs link for ItemsRepeater

We're closer to this via #392 but it sounds like even with that, there are pages that could use more links? Or do you think #392 gets us "close enough"?

Thanks @stmoy, I must have missed the previous issue as it is closed now. #392 should be most of the way. I know for ItemsRepeater there are more 'helper' classes that are involved, so links to those would be useful. Maybe they are just links inline with the samples that they appear in? Not sure... 🤔

I don't think that currently, there are samples where any helper code is not inside the page's code. The only items needed for the samples, that are not on the sample page are a few mock sample pages, which we use to show navigating.

@michael-hawker Is there any specific controls besides ItemsRepeater where you would have expected more things to be linked?

@chingucoding I think it's for any helper in samples that's not bubbled up. For instance ItemsRepeater uses the ActivityFeedLayout but that's not shown how to get the code for that example anywhere: https://github.com/microsoft/WinUI-Gallery/blob/winui2/WinUIGallery/Common/ActivityFeedLayout.cs


Following camera doesn't clear screen outside of the 128x128 area

Was just trying to do pico8.camera(self.x - 56, self.y - 56); which works in pico8 but here it stops clearing screen when you're outside of the 128x128 coordinates.
Btw what is append_camera for?

On top of that I'm not sure why the 2nd sprite is already being drawn 3 times on the map, it's supposed to be just the latter half of the spritesheet.

Can you provide a fully reproducible example?

Btw what is append_camera for?

It's a convenience function I use in the editor, it adds a camera offset to the current one.
https://github.com/jjant/runty8/blob/cbb1d15a497afffe3930512b183b38cc4cf980ce/src/runty8-core/src/draw_data.rs#L39-L41

Thank you! Your repro helped me find the issue, this will be fixed by #66 😄


Contract ext_dispatch_call refactor

Restoration mechanism has been implemented as an extrinsic call that contract can call using ext_dispatch_call. Even though that this extrinsic is technically available to be called by any user, it can only be meaningfully called by a contract (i.e. it bails out if called by an account without code).
We could refactor into the following architecture:
enum Delayed {
    DispatchCall(call)
    SendEvent(event)
    RestoreTo(...)
}

and merge events and calls fields of ExecutionContext into a delayed field.
CC @pepyakin

This is also related to suicide/selfdestruct.


Routes not rewrited if LocalizeRouterService wasn't inject somewhere

Not sure what you want to say, but did you initialise the LocalizeRouterModule correctly?
Can you provide some example what you did so far?

I've initialize module like this
in main module:
LocalizeRouterModule.forRoot([], {
  provide: LocalizeParser,
  useFactory: (LocalizeParserFactory),
  deps: [TranslateService, Location]
})

and in app module
LocalizeRouterModule.forChild(routes)

But I've errors like Error: Cannot match any routes. URL Segment: ...
until I've inject LocalizeRouterService in any module
now routes works correct, but I think it is a bug

@meeroslav did you publish 0.6.3 version correct? because I have old module file and service as well

@thebarada I seems that package was not published correctly. Please use version 0.6.4. Thanks for the information.

@meeroslav thnx a lot! I appreciate your help)


refactor: fetch languages from Crowdin API

This PR removes the hardcoded languages array from exportPattern.ts and fetches them once they're used and caches them (if cache isn't disabled). Resolves #32

All requests have been addressed, could you re-review? I also made sure to test a bunch of scenarios and I can confirm the languages API is only fetched once with cache enabled!

Thanks! Will take a look later on. Probably will release it this weekend. Thanks


Add NOGZIP variable to be able to switch off gzip

Hi @kbaum,
Thank you for the solution, it is very helpful.
In our setup, we found that to restore backups using heroku pg:backups:restore it is better to have unzipped dump on S3. I'm adding that function by using $NOGZIP variable.

Good point, thanks! I've DRYed the condition.


Move all download code into one place

Move all download code into ubuntu-install-requirement.sh
Move all download into one bash file, and source this file from both ubuntu and centos installation requirement scripts.
Add a OS checks in host_cleanup.sh

Can one of the admins verify this patch?


Use sbt-coursier and cache its dependencies

Cuts our build times by about 150 seconds per cross build.

Cool. :+1:

Current coverage is 59.87% (diff: 100%)

Merging #687 into master will decrease coverage by 0.13%

@@             master       #687   diff @@
==========================================
  Files           199        199
  Lines          4404       4404
  Methods        4098       4098
  Messages          0          0
  Branches        304        304
==========================================
- Hits           2643       2637     -6
- Misses         1761       1767     +6
  Partials          0          0

Powered by Codecov. Last update 7f838ba...a3c261a

Looks good to me, though I've not seen coursier. What does it do better than the stock dependency resolver?

https://github.com/alexarchambault/coursier#why
tl;dr it drastically cuts the time of sbt update, which is especially great when you're switching branches and reloading the build.

And not a reason we should use it, but in a neat bit of symmetry, it uses us.

Very sad halfway through a flight when SBT decides to evict your SNAPSHOTs :-/

Wait, it uses http4s-blaze?!? I'm totally sold.

I'm not entirely sure what it's used for yet, but it made me smile to find it. :)


Pytest does not find pygemmes on branch ShouldMerge

Done a library was loaded as pygemmes.utils and not .utils


fullscreen mode

Is it possible to set a max-height/-width on the element, so that we don't show a vertical scrollbar if the screen has a wider resolution than the grid?

Is it possible to set a max-height/-width on the element, so that we don't show a vertical scrollbar if the screen has a wider resolution than the grid?

I think it's possible, but then it won't be "fullscreen" isn't it? We might limit by height and width and there will be empty areas at those places that do not fit the screen. One of the options here might be to maximize the window, that is to fit all of it into one window and it'll work for smaller grids, but then if the topic map is large it will just shrink too much based on height and/or width.

Is it possible to set a max-height/-width on the element, so that we don't show a vertical scrollbar if the screen has a wider resolution than the grid?

I think it's possible, but then it won't be "fullscreen" isn't it? We might limit by height and width and there will be empty areas at those places that do not fit the screen. One of the options here might be to maximize the window, that is to fit all of it into one window and it'll work for smaller grids, but then if the topic map is large it will just shrink too much based on height and/or width.

Ok, let's save it for another day.  My worry is that the user doesn't want to scroll within the fullscreen view, but let's ask them before assuming 🌼


[BUG] ios building errors with drawing shapes

using the latest git kha version
building a simple application that just prints touchs & multi touch works fine. but when drawing a simple made block that would follow a finger on the x/y on screen does bring errors on trying to run it on a device.
does not make it past the build phase

Can you get me the actual compiler output or upload a sample project?

TOUCHINPUT.zip

Figured it out, but can't fix it, it's rather fancy. There is an internal header called Block.h inside Xcode/iOS. Having a Haxe class called Block creates another Block.h which is then included instead of Apple's Block.h and messes everything up. I can't seem to change Xcode/clang's include priorities and hxcpp uses global header paths - you could open an hxcpp issue to maybe get that changed. Meanwhile just rename your Block class.

hmm that is pretty fancy. cheers. will not name as Block in future ;)


Rangy error

I got this error in my console:
rangy-core.js:80 [Deprecation] The behavior that Selection.addRange() merges existing Range and the specified Range was removed. See https://www.chromestatus.com/features/6680566019653632 for more details.
(anonymous) @ rangy-core.js:80
api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js:4 Uncaught TypeError: Cannot read property 'src' of null
at HTMLDivElement. (api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js:1543)
at Function.each (api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js:4)
at jQuery.fn.init.each (api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js:4)
at Object.constructions (api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js:1541)
at HTMLDocument. (api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js:6673)
at l (api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js:4)
at c (api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js:4)
I suspect those two things are related? Line 4 in the api.4425ff5e7335cfe97cd3183aa30517<IP_ADDRESS>.js file is a minimised jquery.

The issue still seems to exist:
rangy-core.js:80 [Deprecation] The behavior that Selection.addRange() merges existing Range and the specified Range was removed. See https://www.chromestatus.com/features/6680566019653632 for more details.
(anonymous)	@	rangy-core.js:80


ror: fix dump modified date comparison

Requires https://github.com/inveniosoftware/invenio-rdm-records/pull/1798 to be merged and deployed on Zenodo (so that the JSON-LD export format includes the dateCreated field)

Rebased, but will probably have to cherry-pick and release as a patch under a maint-4.x branch, since we're planning to release the search mappings as a a major bump.


compute and store histogram at [auto] ingest?

@kunallillaney @Aeusman @randalburns @jovo
Topic for discussion Monday. (hit enter too soon)

i think yes, ndingest would auto-launch propagate and ndhist?
On Sat, Aug 20, 2016 at 10:35 AM, Alex Baden<EMAIL_ADDRESS>wrote:

@kunallillaney https://github.com/kunallillaney @Aeusman
https://github.com/Aeusman @randalburns https://github.com/randalburns
@jovo https://github.com/jovo
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/ndstore/issues/344, or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjcjPa51yna3Z8qVyq5a5MWFSOixnuks5qhxCmgaJpZM4JpFk5
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York

That's one option. But I was thinking the histogram would be computed on cuboid creation before the cuboid is stored in the DB. This would solve the problem of computing a histogram for big datasets on MySQL, allow us to do arbitrary histograms of ROIs super fast, and best of all let us compute "anchors" on ingest that show us where data is likely to be. Plus, we would know the histogram matched the dataset because it would be updated on each re-ingest.
I think the numpy histogram function is pretty fast, but there's always the possibility this slows down ingest a little bit. Also, we would need to discuss the optimal place to store the histogram.
If we did this, the ingest + viz workflow for 16-bit data would be much smoother. We could auto-window and auto-locate data with fewer steps. Just post your images and we do the rest. 👍

ah i see.
yes, my "auto-launch" was meant colloquially :)
i trust your judgement on the guts
On Sun, Aug 21, 2016 at 1:03 PM, Alex Baden<EMAIL_ADDRESS>wrote:

That's one option. But I was thinking the histogram would be computed on
cuboid creation before the cuboid is stored in the DB. This would solve the
problem of computing a histogram for big datasets on MySQL, allow us to do
arbitrary histograms of ROIs super fast, and best of all let us compute
"anchors" on ingest that show us where data is likely to be. Plus, we would
know the histogram matched the dataset because it would be updated on each
re-ingest.
I think the numpy histogram function is pretty fast, but there's always
the possibility this slows down ingest a little bit. Also, we would need to
discuss the optimal place to store the histogram.
If we did this, the ingest + viz workflow for 16-bit data would be much
smoother. We could auto-window and auto-locate data with fewer steps. Just
post your images and we do the rest. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/ndstore/issues/344#issuecomment-241269019,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjcmOfUM79O9g2-gv6JCyPY91CCektks5qiITRgaJpZM4JpFk5
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York


EL-378: Refactor screen sequencing

Link to the Jira ticket

Removed the current logic to mix-and-match partial arrays with a short config file that lists each screen and the conditions in which each is skipped.

Checklist
Before you ask people to review this PR:
Tests and rubocop should be passing
Github should not be reporting conflicts; you should have recently run git rebase main.
There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
The PR description should say what you changed and why, with a link to the JIRA story.
You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
You should have checked that the commit messages say why the change was made.

@starswan I'd love your take on this, because I know you've given it some thought. My reasoning is this:
I want the following to be easily human-readable:

What the screens are
What order they go in
In what circumstances things are skipped

The current StepsHelper isn't providing that for me - trying to bring the property and property_entry screens into a single save group earlier this week cost me half an hour of cursing with nested arrays.
To me, this yml file is really easily readable, but I appreciate readability is very subjective.
There's definitely a risk around defining branching logic as config. On balance I'm happy with it, because I believe that all the logic around whether to show/hide certain screens can be made to hinge on a series of boolean attributes of the Estimate model, in which case all we need are these fairly intuitive skip_if and skip_unless lines. If I'm wrong, we may end up getting kludgy.

@exonian it would be great to get your thoughts on this too. There's a piece of broader context, which is that knowledge of what screens to show in what circumstances is essentially knowledge of the eligibility ruleset, so the sort of thing that we want to keep reasonably separate from most of the rest of the codebase and potentially reasonably close to other bits of the codebase that contain other sorts of knowledge about the eligibility ruleset, but we've not as yet made a hard decision about where eligibility-ish knowledge sits in the architecture.

@starswan that's a really good point. If the question is "given the current state, what's the next screen?", it feels indirect to ask "given the current state, what are all valid screens?", and then work out next screen from that.
The only counter-argument I can think of is this: In #88 it's really useful to access the list of valid screens for a given state in order to populate the right sections of the check answers screen. Since it's useful to have a method to work out all valid screens, we might as well use the work done in that method to work out the next/previous screen. But maybe  all that work should be within the service layer, rather than half being in a service and half being in a helper.
I'll try shifting some stuff around and see if that makes things nicer.

Closing this. We're moving in a slightly different direction - see #116 .


Dart issue

Analyzer Feedback from IntelliJ
Version information

IDEA AI-191.8<IP_ADDRESS>77832
2.7.0-edge.4b9638aaa17203b4e4f9ceb8492faf6a11301999
AI-191.8<IP_ADDRESS>77832, JRE 1.8.0_202-release-1483-b03x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1676x943

Exception
Dart analysis server, SDK version 2.7.0-edge.4b9638aaa17203b4e4f9ceb8492faf6a11301999, server version 1.27.4, FATAL error: Failed to handle request: {id: 5, method: analysis.setAnalysisRoots, params: {included: [C:\fproject\flutter_app], excluded: [C:\fproject\flutter_app\.idea, C:\fproject\flutter_app\.dart_tool, C:\fproject\flutter_app\.idea, C:\fproject\flutter_app\.pub, C:\fproject\flutter_app\build]}, clientRequestTime:<PHONE_NUMBER>851}
FileSystemException: Directory watcher closed unexpectedly, path = 'C:\fproject\flutter_app'
#0      _FileSystemWatcher._listenOnSocket.<anonymous closure> (dart:io-patch/file_patch.dart:309:11)
#1      _ExpandStream._handleData (dart:async/stream_pipe.dart:248:23)
#2      _ForwardingStreamSubscription._handleData (dart:async/stream_pipe.dart:164:13)
#3      _rootRunUnary (dart:async/zone.dart:1136:13)
#4      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#5      _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
#6      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#7      _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#8      _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
#9      _StreamController._add (dart:async/stream_controller.dart:640:7)
#10     _StreamController.add (dart:async/stream_controller.dart:586:5)
#11     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1384:35)
#12     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:890:18)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#15     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#16     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

For additional log information, please append the contents of
file://C:\Users\BOSKOV~1\AppData\Local\Temp\report.txt.

Thanks for reporting the issue! This was previously reported  #39180, please follow along there

Duplicate of  #39180


Add missing definitions for Kernel

No signatures.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_HOWNhbwGneZnaa

@elliottt sorry, I rebased this one by mistake.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_HOWUZKCLap8Y9U

@Morriar the stripe build passed, but the sorbet CI is failing. Could you take a look at the errors?

@elliottt I fixed the test.
When autocompleting x.me, "Pathname" is now also returned in the condidates.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_HOro289DD6jzxK


Mismatch between exercise and solution notebooks

In https://inria.github.io/scikit-learn-mooc/python_scripts/trees_ex_01.html

ax.set_xlabel(feature_names[0])
ax.set_ylabel(feature_names[1])

Those two lines of Python from the function plot_decision_function do not appear in the solution notebook, so I guess they are useless and we could remove them, right ?

I am wondering if there could be some way to put together some quick test for discrepancies. Basically the solution file cells should contain all the exercise file cells (maybe without a "Write your code here" lines). Maybe also a script that generate exercise from solution. We could reuse a similar idea as what we do for quizzes and solutions.
As always maybe this is over-engineering at this point and we should focus on the content instead.


Moveplottests

remove graphic tests in favour of numerical tests for testing other parts of the code base
assertCML (where already in use) is left as sufficient test coverage
otherwise, data operations are tested using statistics of the data array

interestingly, given my aim to reduce version dependency, there are 4 numerical check failures, compared to a local platform (where all these pass) which tries to mimick the travis environment

:+1: for removing extraneous graphics tests!
Some thoughts on the strategy proposed here...

There are still a number of cases of testing for CML equality. This will of course be open to the same issues in many ways as the graphics tests: a small change in the CML leads straight to a test failure.
I like the approach of checking for near equality of mean & stdev of the data arrays, but I wonder whether these provide enough information to test equality of the two data arrays?
What this of course means is that we need a different approach for equality testing. As has been discussed, for graphics tests we could check that multiple items of the two matplotlib graphics (e.g. the extents of the x and y axes, presence of colorbar, ...) are equal or near-equal.

@bjlittle I understand, this seems like a useful pattern.
I have implemented assertArrayShapeStats for IrisTest

@bjlittle @marqh like it! :+1:

@marqh LGTM :+1:

near equality of mean & stdev of the data arrays, but I wonder whether these provide enough information to test equality of the two data arrays?

Anscombe's quartet says no.


add soft-fail flag

Hello,
We'd like to run tfsec in CI without breaking the build. This PR adds the --soft-fail flag to ensure that the exit code always returns 0. Reports are otherwise unchanged.

Thanks! :rocket:


Add RK IDs to RK files, add individual/sample IDs to all metadata

All good except the one comment! :)

Merging this since we can clean up the very slight code duplication at a later time. :)


Fix: Apply Flag Preset When Creating Bound GeometryBVH

This PR ensures that the selected flag preset is automatically applied when creating a new Bound GeometryBVH object, matching the behavior of converting objects to bounds. Previously, flag presets were not applied during creation.
Fix for: https://github.com/Sollumz/Sollumz/issues/1000

So how it works currently is, if "Apply Default Flag" is enabled, the "Convert to Composite" applies the preset at index 0 ("General (Default)", not the selected preset!) to all converted objects. So this doesn't really match the behavior of the convert operator. And why only do it for the BVH type? Surely it should be done when creating bounds of any type.
I guess the proper workflow would be to rename "Apply Default Flag" to "Apply Selected Flag" (or even remove this checkbox and always apply them, why is this an option? When is no flag needed? Can always remove them later anyways). Then both "Convert to Composite" and "Create Bound" apply the selected flag preset, for all bound types.
@ook3D opinions? Since you opened the issue.

@ook3D opinions? Since you opened the issue.

It should always apply selected preset the only time you don't want any bvh flags is for something like ma@ collisions but you can just clear these if you have to

Made an update and applied suggestions


Cowell method fails to converge with small perturbation accelerations

🐞 Problem

This code converges normally:
from astropy import units as u

from poliastro.twobody import Orbit
from poliastro.bodies import Earth
from poliastro.twobody.propagation import cowell

r0 = [-2384.46, 5729.01, 3050.46] * u.km
v0 = [-7.36138, -2.98997, 1.64354] * u.km / u.s

initial = Orbit.from_vectors(Earth, r0, v0)

def accel(t0, state, k):
    v_vec = state[3:]
    norm_v = (v_vec * v_vec).sum() ** .5
    return 1e-5 * v_vec / norm_v

print(initial.propagate(3 * u.day, method=cowell, ad=accel))

But changing to 1e-6 * v_vec / norm_v fails to converge:
$ python ex0.py
/home/juanlu/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/scipy/integrate/_ode.py:1095: UserWarning: dop853: larger nmax is needed
  self.messages.get(istate, unexpected_istate_msg)))
Traceback (most recent call last):
  File "ex0.py", line 20, in <module>
    print(initial.propagate(3 * u.day, method=cowell, ad=accel))
  File "/home/juanlu/Development/poliastro/poliastro-library/src/poliastro/twobody/orbit.py", line 271, in propagate
    return propagate(self, time_of_flight, method=method, rtol=rtol, **kwargs)
  File "/home/juanlu/Development/poliastro/poliastro-library/src/poliastro/twobody/propagation.py", line 209, in propagate
    r, v = method(orbit, time_of_flight.to(u.s).value, rtol=rtol, **kwargs)
  File "/home/juanlu/Development/poliastro/poliastro-library/src/poliastro/twobody/propagation.py", line 103, in cowell
    raise RuntimeError("Integration failed")
RuntimeError: Integration failed

🖥 Please paste the output of following commands
pip freeze | grep astropy
astropy==3.0.2
pip freeze | grep poliastro
-e git+git@github.com:Juanlu001/poliastro.git@34a9e2c83cd77e918feb0182d2fa162ba06cbd07#egg=poliastro
🎯 Goal

I would expect a zero perturbation acceleration to be equivalent to a keplerian orbit.
💡 Possible solutions

📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #<put issue number here>
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

The current API fails with this case:
def accel(t0, state, k):
    v_vec = state[3:]
    norm_v = (v_vec * v_vec).sum() ** .5
    return 0.0 * v_vec / norm_v

Can you add a corresponding test to #368 to see if the new solvers pass?


Attempt to refresh credentials if we get access exceptions

Which issue this PR addresses:
Fixes https://issues.redhat.com/browse/ARO-2978 maybe
What this PR does / why we need it:
Force refreshes the token if we hit the authorization errors that are due to caches. We no longer need to refresh the token ourselves for normal uses, but since the first token might have a lifetime of 3600s and there's no external interface to force a token refresh, we just rebuild the authoriser to try again.
Test plan for issue:
I'm not sure?
Is there any documentation that needs to be updated for this PR?
fixes have docs in them

/azp run e2e

/azp run e2e

/azp run e2e


Ability to tile tabs

Description of the new feature/enhancement

This one is a "nice to have", but I'd love to be able to stack tabs and tile them side-by-side (ex. a powershell tab on one half, and a WSL tab on the other half). This'd help my efficiency when I need to be testing my work on Windows and Linux at the same time.
Proposed technical implementation details (optional)

Effectively, I'd like something akin to Vivaldi's tab tiling at a minimum, but control on the tier of say, i3wm would be amazing. I should be able to drag a tab over another, and have them drop into a stack.  I should then be able to (in some context menu) be able to set up the layout of the windows in the stack.

I think most of these are covered in #1000, actually, with a little bit of "select multiple things" and "predefined layouts". What do you think about #1000?

Looks good to me. I'll close this since the same general idea is already tracked.


[Bug][Projects] Projects API POST endpoint does not create blueprint connections

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
When I try to create a new project with the POST /api/projects endpoint, then even if I include the blueprint field in the JSON body, then it doesn't correctly create the blueprint connections.
I was able to do a workaround where I create the project using the POST endpoint, fetch the blueprint ID from the response, and then use the PATCH /api/blueprints/{blueprint_id} to correctly set the connections.
What do you expect to happen
I expect that when putting a complete Project payload with a Blueprint field, that it will fully create the blueprint and it's dependencies as well.
How to reproduce
Create a new Project using the POST /api/projects endpoint with a a blueprint containing connections.
Anything else
The following issue exists, but is not classified as a bug: https://github.com/apache/incubator-devlake/issues/7610
Version
v1.0.0-rc1
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Weird, it has been tested. Would you share your request in curl or any other executable format to reproduce the problem?

It should be working according to https://github.com/apache/incubator-devlake/pull/7449

When attempting to create a new blueprint, I'm unable to proceed because I must specify the project name at that point. If I create the project first, the blueprint is automatically generated and attached to the project, preventing me from creating a blueprint specifically for that project afterward.
When trying to PATCH an existing blueprint, the Swagger API provided is:
curl -X 'PATCH' \
  'https://xxxxx/api/blueprints/{blueprint_id}' \
  -H 'accept: application/json'

However, this command does not allow me to specify which project to attach the blueprint to.
What is the purpose of the PATCH /blueprints/{blueprint_id} command?
I need clarification on how to specify the project to which the blueprint should be attached.

@klesh I just did another test with the API using v1.0.0-rc1, and same issue on endpoint POST /api/projects
Example body:
{
  "name": "B2B3",
  "description": "",
  "metrics": [
    {
      "pluginName": "dora",
      "pluginOption": null,
      "enable": true
    }
  ],
  "blueprint": {
    "name": "B2B3-Blueprint",
    "projectName": "B2B3",
    "mode": "NORMAL",
    "plan": [
      "**REDACTED**"
    ],
    "enable": true,
    "cronConfig": "0 0 * * *",
    "isManual": false,
    "beforePlan": null,
    "afterPlan": null,
    "labels": [],
    "connections": [
      {
        "pluginName": "circleci",
        "connectionId": 2,
        "scopes": [
          {
            "scopeId": "1"
          },
          {
            "scopeId": "3"
          },
          {
            "scopeId": "4"
          }
        ]
      },
      {
        "pluginName": "github",
        "connectionId": 2,
        "scopes": [
          "**REDACTED**"
        ]
      }
    ],
    "skipOnFail": false,
    "skipCollectors": false,
    "fullSync": false
  }
}

It created the project fine, but the blueprint is missing the connections. I was still able to patch it afterwards using the PATCH /api/blueprints/{blueprint_id} endpoint.

There are no errors in the backend container either. Just got this log entry: lake time="2024-06-28 07:29:15" level=info msg="added blueprint 20 to cronjobs, cron id: 4, cron config: 0 0 * * *"

When attempting to create a new blueprint, I'm unable to proceed because I must specify the project name at that point. If I create the project first, the blueprint is automatically generated and attached to the project, preventing me from creating a blueprint specifically for that project afterward.
When trying to PATCH an existing blueprint, the Swagger API provided is:
curl -X 'PATCH' \
  'https://xxxxx/api/blueprints/{blueprint_id}' \
  -H 'accept: application/json'

However, this command does not allow me to specify which project to attach the blueprint to.
What is the purpose of the PATCH /blueprints/{blueprint_id} command? I need clarification on how to specify the project to which the blueprint should be attached.

I have resolved the issue by including the request body in the PATCH /api/blueprints endpoint.
Thank you for your assistance.


App association file for iOS production app

This restores the state from before the launch of the new homepage last week.
See: https://web.archive.org/web/20221229230859/https://safe.global/.well-known/apple-app-site-association
And this will hopefully fix: https://github.com/safe-global/safe-ios/issues/2951

I have read the CLA Document and I hereby sign the CLA

recheck

@biafra23 could you try adding your username to the cla.yml file?


[BUG] Unable to access LLM studio using Docker from a nightly build

I am a newbie. Likely a user error. Unable to access LLM studio on http://localhost:10101/ .
Running Windows 11. Ubuntu installed using wsl2.
I tried to install H20 LLM studion following https://docs.h2o.ai/h2o-llmstudio/get-started/set-up-llm-studio#run-using-docker-from-a-nightly-build

sudo docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi
[sudo] password for jponsa:
Wed Jan 31 19:28:55 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.40.06              Driver Version: 551.23         CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4050 ...    On  |   00000000:01:00.0 Off |                  N/A |
| N/A   56C    P3             11W /   35W |       0MiB /   6141MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+

Docker Logs
2024-01-31 19:29:22 2024/01/31 19:29:22 #
2024-01-31 19:29:22 2024/01/31 19:29:22 # ┌────────────────┐ H2O Wave
2024-01-31 19:29:22 2024/01/31 19:29:22 # │  ┐┌┐┐┌─┐┌ ┌┌─┐ │ 0.26.3<PHONE_NUMBER>2251
2024-01-31 19:29:22 2024/01/31 19:29:22 # │  └┘└┘└─└└─┘└── │ © 2021 H2O.ai, Inc.
2024-01-31 19:29:22 2024/01/31 19:29:22 # └────────────────┘
2024-01-31 19:29:22 2024/01/31 19:29:22 # ┌──────────────────────────────────────┐
2024-01-31 19:29:22 2024/01/31 19:29:22 # │  Running at http://localhost:10101/  │
2024-01-31 19:29:22 2024/01/31 19:29:22 # └──────────────────────────────────────┘
2024-01-31 19:29:22 2024/01/31 19:29:22 # {"address":"download/","source":"/workspace/output/download","t":"private_dir"}
2024-01-31 19:29:22 2024/01/31 19:29:22 # {"address":":10101","base-url":"/","t":"listen","web-dir":"/home/llmstudio/.local/share/virtualenvs/workspace-dqq3IVyd/www"}
2024-01-31 17:44:15 [2024-01-31 17:44:15,992] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-01-31 17:49:33 /home/llmstudio/.local/share/virtualenvs/workspace-dqq3IVyd/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cpu.so: undefined symbol: cadam32bit_grad_fp32
2024-01-31 18:19:19 [2024-01-31 18:19:19,713] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-01-31 18:52:22 /home/llmstudio/.local/share/virtualenvs/workspace-dqq3IVyd/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cpu.so: undefined symbol: cadam32bit_grad_fp32
2024-01-31 18:52:30 [2024-01-31 18:52:30,435] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-01-31 19:03:29 /home/llmstudio/.local/share/virtualenvs/workspace-dqq3IVyd/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cpu.so: undefined symbol: cadam32bit_grad_fp32
2024-01-31 19:29:27 [2024-01-31 19:29:27,582] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-01-31 19:29:28 /home/llmstudio/.local/share/virtualenvs/workspace-dqq3IVyd/lib/python3.10/site-packages/bitsandbytes/cextension.py:34: UserWarning: The installed version of bitsandbytes was compiled without GPU support. 8-bit optimizers, 8-bit multiplication, and GPU quantization are unavailable.
2024-01-31 19:29:28   warn("The installed version of bitsandbytes was compiled without GPU support. "
2024-01-31 19:29:28 Error loading keyring: No recommended backend was available. Install a recommended 3rd party backend package; or, install the keyrings.alt package if you want to use the non-recommended backends. See https://pypi.org/project/keyring for details.. Disabling keyring save option.
2024-01-31 19:29:28 INFO:     Started server process [1]
2024-01-31 19:29:28 INFO:     Waiting for application startup.
2024-01-31 19:29:28 2024/01/31 19:29:28 # {"host":"http://<IP_ADDRESS>:8756","route":"/","t":"app_add"}
2024-01-31 19:29:28 2024-01-31 19:29:28,566 - INFO: STARTING APP
2024-01-31 19:29:28 INFO:     Application startup complete.
2024-01-31 19:29:28 INFO:     Uvicorn running on http://<IP_ADDRESS>:8756 (Press CTRL+C to quit)

Hi @JPonsa, sorry for the late reply. From the logs it seems there is not isssue w.r.t. starting the app, so hard to debug.
Just to confirm, you are using the docker start command from the docs, in particular -p 10101:10101?
To check issues with 10101 specifically, you could try forwarding to another port, e.g. use -p 10102:10101 within the docker command and then using http://localhost:10102/; although I doubt this will solve the issue.

Sorry, user error not knowing how to use dockers and dockers desktop. Starting dockers from the command provided in the documentation works. User error trying to run it from docker desktop and not specifying the port when creating the container


On-the-fly compilation for addons that are not precompiled

If we encounter an addon during the build process that is not precompiled, we should compile it on the fly, optionally adding a watch to recompile on changes.
Possible reasons precompiled might not be available:

npm linking
git dependency

We should roll this together with the inDevelopment flag used for watching and recompiling addons.

This is now working


"Show Desktop Button" can't be clicked fully

Describe the bug
When trying to click the show desktop button on the lower right, it can't be clicked. Only the upper and middle part of the small rectangle is functional, not the lower part.
To Reproduce
Steps to reproduce the behavior:
Use Taskbarx
Expected behavior
I expect to fix this bug by clicking the show desktop button in the lower portion of the small rectangle
Screenshots
none
Desktop (please complete the following information):
OS: Windows 10
Version <IP_ADDRESS>

Same bug as #717 which seems more active.

it's sad that ppl here are opening soo many duplicates :(

even though #717 seems more active, but taking a bird eye skimming through that, the discussion there didnt seem to go into much else depth other than mentioning the older working version.

I'm havind this problem too! It's really annoying. The "Show Desktop Button" can't be clicked on the extreme lower right corner. And the problem persists after unninstalling.

@juninholiveira i have moved over the input from other issue which contains the fixing step. try those :)

@yashpalgoyal1304 Yes, your steps indeed solved the problem for now! I'll stay in 1.6.9 for now, but I'll wait for a proper fix on 1.7.3 cause I really don't like using out of date software :S But thank you!

it's sad that ppl here are opening soo many duplicates :(
#785
#782
even though #717 seems more active, but taking a bird eye skimming through that, the discussion there didnt seem to go into much else depth other than mentioning the older working version.

That was my bad, I opened #717, although I did search through existing issues and at that time didn't find a similar one. Apologies

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


Spec should discourage abuse of initializationOptions and didChangeConfiguration

I'm working on having Eclipse IDE adopting some language servers.
I see a possible bad trend for Language Servers to heavily rely on initializationOptions and didChangeConfigurations to enable/disable features. The issue with those is that they are unspecified placeholders and that whatever usage is made of it requires all clients to write code specific to this language server to support those options.
The main example I have in mind right now is RLS that, by abusing those settings is progressively, and most likely without really willing it, breaking rich compatibility with other IDEs: https://github.com/rust-lang-nursery/rls/issues/1047
Abuse of those properties should be deprecated in the spec, with some disclaimer explaining how relying on those make the LS integration less likely to be trivially portable from an editor to another.

Interesting. I use workspace/didChangeConfiguration as that's what was there but did not consider this case.
At what point would you consider the use of this "abuse" though?

As an adopter of LS I don't develop, I consider any usage is abuse, as long as it requires to create a specific UI or workflow to interact with it in the client ;) But I hope this discussion can lead to a more flexible definition.

As I see it, a server initialized without initializationOptions should just work in any editor. If the editor allows servers to be started by custom extensions with possible deeper integration (like VSCode or Atom for example), then initializationOptions can be used to enable specific features that can't be used in other editors.

@LaurentTreguier: so your proposal is that the settings should be limited to only client-specific configuration? I think it'd be fair.

This is how I understood it. The spec describes it as User provided initialization options, which can be misleading; it makes it sound like the user should change it themselves when it should be up to a specific client to do this.

IMO the spec should encourage all server providers to spec the following to things:

the initialization options it supports. I agree with @LaurentTreguier that a server should work with an empty literal as well and simply assume a set of defaults.
which workspace/configuration request it sends.

Having a push model for configurations was a mistake and got basically replaced by the pull model where the server sends workspace/configuration requests.
The client should still send workspace/didChangeConfiguration notification so that the server can clear caches if it caches configurations. But it should not send any values since values can differ based on the scope used in the workspace/configuration request.

the initialization options it supports. I agree with @LaurentTreguier
https://github.com/LaurentTreguier that a server should work with an
empty literal as well and simply assume a set of defaults.

Just to give examples and food for thought, VSCode CSS language server
requires explicit enablement for sass, scss and so on; and VSCode JSon
language server doesn't pre-load a typical list of JSon schema. Both assume
client discover this settings by reverse engineering VSCode and repeat the
same settings. The question is what drove the developers of those LS to
rely on those options instead of making them default? It'd be interesting
to get their POV on this question.

Having a push model for configurations was a mistake and got basically
replaced by the pull model where the server sends workspace/configuration
requests.

Still, the expected type is any[] which means that it's some LS specific
settings that require specific integration.
I don't think the flow of the operation was the issue here (while it's
still good to know it was improved), it's really than any any leads to
the unspecified world and specific effort of integration between client and
LS, which is the opposite of LSP goal.
I believe instead of specifying some operations with any, it's better to
leave these as extensions. For clients, it's a similar effort to support
one or the other, and it's not reusable between LS, so the protocol should
remain strictly made of specified, portable, reusable operations, and
whenever there is any, consider deprecating the operation basically
because it's not specified enough to be useful by most tools.

One pattern I saw emerge is that many language servers interpret initializationOptions as containing user configuration, i.e. the same that is sent in workspace/didChangeConfiguration or in response to workspace/configuration. But LSP doesn't actually really say this, it is very vague on what initializationOptions actually means:

User provided initialization options.

It doesn't use the term "configuration", but it does say "user provided" (not client provided).
The reason why language servers use it for configuration is because there is otherwise no way to read configuration in initialize. workspace/didChangeConfiguration is only sent after initialize returned (if at all), and
workspace/configuration is not among the whitelisted requests allowed during initialize.
The problem is that since initializationOptions is not clearly defined, most clients do not send configuration in it.
Could LSP just be clearer about what initializationOptions is intended to be used for (maybe with an example in the spec)? And could workspace/configuration be whitelisted to be used during initialize?

I will clarify the spec in a way that the initializationOptions is typically something that could be passed on the command line when starting the server. It shouldn't be user configurations.
I am actually against whitelisting workspace/configuration. If a server needs the configuration to register providers it should use dynamic registration instead of static registration which allows to mix workspace/configuration with registration calls.

Please ping if you think dynamic registration is not the right path to go.

I will clarify the spec in a way that the initializationOptions is
typically something that could be passed on the command line when starting
the server. It shouldn't be user configurations.

I disagree with that. The initializationOptions can be a good way to
guarantee that user settings are passed immediately to the LS before to
starts up. I think that basically, the initializationOptions have to be a
super-set of the didChangeConfiguration as there are case where we want the
configuration immediately.
From a client perspective, the didChangeConfiguration is over-used, hard to
maintain and is semantically often used with wrong semantic since several
LS use it even to retrieve a default configuration. Eclipse Corrosion had
an important discussion with RLS on that matter, and the resolution that
initializationOptions can contain a mirror of didChangeConfiguration
improved things a lot: https://github.com/rust-lang/rls/issues/1026

I am actually against whitelisting workspace/configuration. If a server needs the configuration to register providers it should use dynamic registration instead of static registration which allows to mix workspace/configuration with registration calls.

@dbaeumer I agree for determining whether a provider should be registered or not, but a server might need configuration during initialisation for a lot of reasons. For example, a loglevel or logfile, whether file watchers should be set up with polling or OS events, the HTTP endpoint of a service that needs to be contacted, whether dependencies should be installed, if yes an access token for that, the path of an external tool that needs to be shelled into, something like JAVA_HOME or GOPATH, ...
Requiring to delay all of these after initialize complicates a lot of things for no apparent reason. Also not every client supports dynamic registration.

@felixfbecker the list you provided don't seem to be user configuration which is something that should come through workspace/configuration anyways. For example a logLevel or an access token is something that you usually would pass as a command line option and therefore I have no problem if something like this comes through the initialize options. I want to makes sure that the initialize options are static.

Could you explain why a user-defined access token should come through a command line option and not user settings? Lots of VS Code extensions configure access tokens through settings, or JAVA_HOME/GOPATH, ... It seems like an arbitrary distinction if the extension had to filter out specific settings to pass them through initializationOptions (and prevent the server from reacting to their changes) while other settings go through didChangeConfiguration?

that should come through workspace/configuration anyways.

Multiplying the entry-points for configuration/options is making harder and harder to adopt the protocol.
For example, see how current VSCode CSS language server requires enablement for SCSS, SASS and so on in initializationOptions. Are those user config or not? (a user could decide to disable SASS)
The line between user config and initializationOptions is IMO way to blurry to be specified and pragmatically, initializationOptions are also very good to pass some user settings and should be spec'd as being deprecated for this case.

@dbaeumer dynamic registration is not always available, as clients aren't forced to implement it. Atom, with its official atom-languageclient for example, doesn't support any dynamic registration; so right now initializationOptions is actually the only reliable way to get any kind of configuration at server startup.

This is exactly what I want to avoid by making it more clear. The initializationOptions should be static in the sense of a server run (e.g. like command line parameters). User settings should come through workspace/configuration.
@felixfbecker if the user token is a user setting then it should come through workspace/configuration. If we have more such configuration I am open to rethink to white list it in the initialize call. But that would be something clients need to opt in.

@LaurentTreguier I am not against having initializationOptions. But as others pointed out this should not be used to pass user configuration since this is something a server needs to handle dynamically anyways.

@felixfbecker if the user token is a user setting then it should come through workspace/configuration. If we have more such configuration I am open to rethink to white list it in the initialize call.

I think me and others gave a lot of examples of this kind of config in this thread - it really is a very common use case.

But that would be something clients need to opt in.

The server could just make the request and if it returns an error fall back to a different mechanism. But the whole whitelist could also be announced in ClientCapabilities.

But as others pointed out this should not be used to pass user configuration since this is something a server needs to handle dynamically anyways.

static vs dynamic is not absolute and depends a lot on the client and the server. Some clients tend to allow/encourage a lot of user configuration, some others using similar LS would prefer providing a pre-defined config and not let user tweak it. As such, I don't think using the static vs dynamic distinction is reliable here.

@felixfbecker and @mickaelistria can you both please write what you would like to see written in the spec. I have to say I get puzzled here since it is not clear to me what kind of settings you want to allow and what kind of settings you want to forbid. The original idea of the initializationOptions option was to pass parameters that are usually parameters pass on the command line to ease that.
I will revert the changes and wait for you to make concrete wording proposals.

I would like to see specified something like
It's recommended that initializationOptions can read a superset of didChangeConfiguration parameters, and interpret them as default/initial values.

and/or the other way round
parameters of didChangeConfiguration should also be valid as input to initialization, where they would be interpreted as default/initial values.

and also something like

initializationOptions and didChangeConfiguration can receive any values. This flexibility increase the difficulty for clients to adopt the Language Servers as they need to learn about the Language Server specific value that can be set there and implement support for them. It's recommended to rely on those as less as possible to ease integration.

It's recommended that initializationOptions can read a superset of didChangeConfiguration parameters, and interpret them as default/initial values.

I thought this is exactly what we don't want. We shouldn't push server developers in updating a configuration using didChangeConfiguration. Configuration should always be pull from the client and didChangeConfiguration should only be used to signal a change. So may be in a first step I will clarify this.
In my opinion to make this easier for clients to handle we should say:

no configuration / setting in initializationOptions
settings should be fetch using workspace/configuration and a server needs to spec which configuiration settings it expects and can handle.
didChangeConfiguration should only be used to signal a change in configuration not to push data.

I agree that they shouldn’t be in initialisationOptions, and the docs should clarify that. The term used for user-defined settings is “configuration”, not “options”.
I am proposing to whitelist workspace/configuration during initialize.
This seems like the simplest solution to me to solve the use case and without any drawbacks.

I will look into white listing workspace/configuration

Perhaps a simpler option is to just add initial configuration to initialize response?

@matklad  Why would that be any different than initializationOptions Or do you simply suggest a different name. Typing wise it would still be any.

For two reasons:

it will guarantee to submit the same values as the workspace/configuration
clients would be able to automatically populate it from settings, instead of needing custom per-language code to constuct initializationOptions

I guess we can just reuse existing initializationOptions key, and just make sure that it automatically gets populated from the settings.

It is possible to send getConfiguration requests in the initialized notification.

The current spec says

In addition the server is not allowed to send any requests or notifications to the client until it has responded with an InitializeResult, with the exception that during the initialize request the server is allowed to send the notifications window/showMessage, window/logMessage and telemetry/event as well as the window/showMessageRequest request to the client.

Which seems to contradict what you said, @dbaeumer ?

No this contradicts nothing.

initialize is a request sent from client to server.
initialized is a notification from the client. Clients are expected to send this notification after receiving a response to the initialize request.

A server can therefore do a workspace/configuration request in its handler for initialized notifications.

Gotcha, thanks!

I will look into white listing workspace/configuration.

It is possible to send getConfiguration requests in the initialized notification.

@dbaeumer The latest solution doesn't seem sufficient and I think workspace/configuration should be allow-listed during initialize.
Good servers should pull relevant workspace settings by namespace, for each workspace folder if interested, and incorporate that before they start processing normal document notifications/requests. Currently you can only do that in the initialized handler. This means every server must have a boilerplate initializer lock which blocks out other message handling until that part of the initialized handler is completed.
Is that the basic recommended approach? Or are servers supposed to initialize once with default settings, initialize again with pulled config slightly later while possibly receiving doc info in between? I don't see any other interpretation.
Well, extension authors have avoided this and are still heavily relying on initializationOptions for startup workspace settings despite using pull-based config when it comes to receiving workspace/didChangeConfiguration. IMO that should only be a fallback for clients that don't support pull-based config, if they're worth the effort. My problem is that initializationOptions has no convention for per-workspace-folder settings.
Is there a good reason to not allow-list workspace/configuration?

Is that the basic recommended approach? Or are servers supposed to initialize once with default settings, initialize again with pulled config slightly later while possibly receiving doc info in between?

This is what we're doing in HLS. In fact we do all of what you said:

Start with default config
Take the config from intializationOptions if it's there
Fire off workspace/configuration in the initialized handler

I agree that this is not very good, and it certainly seems that if you do the recommended thing you can start getting sent requests before you have your config set up.

good

Is there a good reason to not allow-list workspace/configuration?

In general I try to keep the message that can be sent to the client in initialized as small as possible to make the initialization phase on the client simple.

Currently you can only do that in the initialized handler

I usually do that when actually processing a request and then cache the result of the workspace/configuration. When I receive a workspace/didChangeConfiguration I simply clear the cache.

I usually do that when actually processing a request and then cache the result of the workspace/configuration.

This is not a good candidate for lazy init because:

workspace/configuration generally is behind an async binding, and accessing config shouldn't need to be.
It spreads to other structures that depend on config. Now everything must be computed lazily and asynchronously.
Lazy computation is used to make things more responsive. In this case it's less responsive compared to acting on workspace/didChangeConfiguration.

In general I try to keep the message that can be sent to the client in initialized as small as possible to make the initialization phase on the client simple.

I think that would mean just storing the initialize params and returning server info and capabilities, since technically everything else can be done lazily. But server authors won't use it that way.
A more meaningful differentiation is that initialize is the request that all other requests are blocked on, hinting that it should get up-to-date everything required for handling textDocument/* notifications. That makes more sense so server authors are using it that way (but relying on initializationOptions).
Please reconsider allow-listing workspace/configuration during initialize.


Fixed DJ Console MK4 support

This is a simple fix that we were able to get with the col·laboration of an user that had such a controller.

Thanks!


Path specified is not a war file | Azure App Service

Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: Error
Error Message: Path specified is not a war file
Version: 0.19.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.47.0
Language: en

Call Stack
Object.<anonymous> extension.bundle.js:225:3759192
extension.bundle.js:225:3758965extension.bundle.js:225:3758965
i extension.bundle.js:225:3758651
Object.deployWar extension.bundle.js:225:3759119
Object.<anonymous> extension.bundle.js:225:3758180
extension.bundle.js:225:3755824extension.bundle.js:225:3755824
i extension.bundle.js:225:3755510
extension.bundle.js:225:3757682extension.bundle.js:225:3757682
t.ExtHostProgress._withProgress extensionHostProcess.js:578:963
t.ExtHostProgress.withProgress extensionHostProcess.js:578:717
Object.withProgress extensionHostProcess.js:918:395
Object.<anonymous> extension.bundle.js:225:3757614
fulfilled extension.bundle.js:225:3755578
processTicksAndRejections task_queues.js:85:5

Please provide repro steps.

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


Default number is based on Usage Location and not Country

Default number is based on Usage Location and not Country. So have changed this. Tested a user - set the UsageLocation to IE and Country to blank and the Default number was USA. Assigned user a licence and they got an Irish phone number = UsageLocation

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@tonysmit PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

Ping'ing PM Neeraj Jain.

Pinging Nakul Madaan.

This is correct now.


Add generated documentation

Documentation enhancements: The following two documentation enhancements would be nice to have. Both require setting up of some sort of documentation generator:

It would be nice to auto-generate the commandline usage. A quick research about tools that we could use for this:

shinx-argparse which has recent commits, or
https://pythonhosted.org/sphinxcontrib-autoprogram/

It would be nice to replace the hand-written example (in the README file, section "programmatic usage") with code from a test case... the test case would ensure that the example keeps up to date.

Tooling: Both enhancements require some sort of documentation generator such as sphinx. The generator should run locally and in github ci. Updates to the master branch should automatically update the documentation. Documentation for tagged commits should also be available. Documentation generators such as sphinx are probably able to do these jobs nicely out of the box... we just need to set things up.

documentation generator:

sphinx? pdoc3?
sphinx doctest could maybe validate that example code works correctly

runtime:

locally, a simple poetry run sphinx-build ... or tox run -e docs sphinx-build ... should do the job
on github ci, we could use the same call. alternatively, we could use the github actions as documented by sphinx under publishing your html documentation

Update, I started working on this.

I added sphinx-doc
I found a way to include the main README file into the sphinx documentation
I added pre-commit hooks to make sure the python code is well-documented (and I consequently added a lot of missing docstrings).
I used sphinx-argparse to automatically document commandline usage

Todos:

the programmatic usage example is still handwritten. we are still missing automated tests to ensure the example stays functional. we could maybe use sphinx doctest for this.
it only runs locally for now, I have not added any github ci yet.


Fix brackets in colored messages

Short Description: Fix couple bugs in logging
Changes:

Fixed #49
Fixed transfer not using log

@OpenPoGo/maintainers

Please rebase with master

:+1: can squash when we merge.

:+1: if that's the case

👍


$eq shortcut nested inside $or not supported

This does not work in pouchdb-find, while it works against the http adapater in CouchDB 2.0:
$or: [
    {"name.first": "Nancy"},
    {"name.first": "Mick"}
]

See https://github.com/jo/pouchdb-find/commit/46e4454324749bf5e97f73027cd29814f7d983f0 for failing test.

I don't believe $or is supported. There should be an open issue but I didn't find one.

Actually, it does work (afaict), you just have to explicitly use $eq:
$or: [
    {"name.first": {"$eq": "Nancy"}},
    {"name.first": {"$eq": "Mick"}}
]

According to the readme $or was added in 0.6.0.

Actually. It helps to read. This issue is precisely about $eq being required here... Thanks for reporting it @jo. Sorry for the noise...

This issue was moved to pouchdb/pouchdb#6261


Support label matchers in labels API

Signed-off-by: Ben Ye<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Fixes #3351
Add match[] param for LabelNames and LabelValues queries.
Now this is implemented via the Series matching. We can do matchers push down to improve this later.
TODO: query frontend also needs matchers type for Label names and label values query. Will add them in the next pr.
Verification

Add unit tests and E2E tests for this feature.

E2E is flaky #3570


A11y_VisualStudioCodeClient_Customizations and settings_Changing of the Theme_Screenreader:Once the theme was updated, NVDA/Narrator did not announce any status messages.

GitHub Tags:
#A11yMAS; #A11yTCS; #A11ySev2; #DesktopApp; #Win32; #Visual Studio Code Client; #BM-VisualStudioCodeClient-Win32-Aug2022; #WCAG4.1.3; #NVDA; #ScreenReader; #Narrator;
Environment and OS details:
Visual Studio Code Version: 1.70.2 (user setup)
Windows 11 Pro version 21H2 (OS Build 22000.856)
Repro Steps:

Turn on NVDA
Open Visual studio code editor.
Open the command Pallet by pressing "F1" key and type "Theme" and enter
Verify that screen reader announcing status message once theme got changed or not.

Actual Result:
Once the theme was updated, NVDA/Narrator did not announce any status messages.
Expected Result:
NVDA/Narrator should announce status message for example, theme updated
Attachment:

@isidorn I wonder if the quick pick dialog should narrate that an item has been accepted.
Otherwise, all quick pick users have to do this.
What do you think?
If you think the theme code should do this, how would this be done (API wise)?

This should not be done. We currently do not confirm that an action has been completed. This is a design decision.
Closing as invalid. 0 users requested this.
@aeschli though if we were to do this it should be for all commands. Which does not make sense


Compiler does not catch typing error in pattern matching when using literals

When literals are used in pattern matching there is no check that the subsequent expression/pattern argument list is empty, e.g.
module Color =
    let [<Literal>] Yellow = "Yellow"

let isRed inp =
    match inp with
    | Color.Yellow arg ->   // should get an error here
        failwith "Don't know this color"

nor that the right arrow in the pattern match is not missing, e.g.
let isRed = function
    | Color.Red ->
        true
    | Color.Yellow               /// Notice the missing -> here
        you can insert what you want here like booleans false "strings" _and numbers 42. Yes it still compiles
    | _ ->
        failwith "Don't know this color"

As a side effect the match on Color.Yellow never holds.
For reference when using discriminated unions instead of literals you get the expected behavior:
module Color =
    type Y = | Yellow | Green

let isRed inp =
    match inp with
    | Color.Yellow arg -> // we do get an error here
        failwith "Don't know this color"

Fix is now ready for this

Thank you! I confirm that it works with branch fix-528. I now get the expected error:
D:\sources\visualfsharp\Release\net40\bin>fsc c:\Users\wiblum\Documents\test.fs
Microsoft (R) F# Compiler version (private)
Copyright (c) Microsoft Corporation. All Rights Reserved.

c:\Users\wiblum\Documents\test.fs(6,7): error FS3190: This literal pattern does not take arguments

Reopening until the pull request is committed :) thx


Edit the command before running

https://github.com/murarth/linefeed

This probably isn't needed for now.


Can't use within iframe

I'm using React Frame component to wrap my entire app in an iframe as I'm building a widget.
I'm getting the following errors when I try to use Tippy
index.js:159 Uncaught TypeError: instance.set is not a function
index.js:148 Uncaught TypeError: instance.destroy is not a function
index.js:1437 The above error occurred in the <Tippy> component:     in Tippy (created by ForwardRef(TippyWrapper))     in ForwardRef(TippyWrapper) (at ItemDetail/index.js:84)…
I assumed the issue was that Tippy was trying to inject itself to the document body instead of the iframe's document body, so I used React Frame's context consumer and passed its document to my component and added it to appendTo.
<FrameContextConsumer>
  {
  ({ document, window }) => {
    return (
      <Tippy appendTo={document.body} content="Text" >
        <button>Button</button>
      </Tippy>
    )
  }}
</FrameContextConsumer>
)

I tried console.logging the instance in the onCreate prop and it just returned an empty array, so that'd explain why there's no methods on instance
Digging into Tippy's code, it appears the creation of the Tippy div is hardcoded to the main document
export function ssrSafeCreateDiv() {
  return isBrowser && document.createElement('div')
}

Is there something I'm missing to allow usage within an iframe? Or am I correct that ssrSafeCreateDiv would need to be refactored to allow passing in a different document?

I'm seeing this randomly in an Electron environment, but pretty frequently. I recently updated from 2.2.0 to 2.2.3.
Can we change the title to reflect that the issue affects more than just iframes.

I tried console.logging the instance in the onCreate prop and it just returned an empty array, so that'd explain why there's no methods on instance

Means an invalid targets argument (the button ref was not defined) was being passed to tippy() core which seems odd

Found the issue in tippy core:
value instanceof Element (value === <button> node) this is returning false.
So somehow the button node within the frame's context is not an instanceof Element

Run:
npm i @tippy.js/react@latest

iframes should be supported now

Awesome! 🎉 Got temporarily pulled onto a different project, but I'll try to check it out sometime this week. Thanks @atomiks!


EventHub - Log Analytics

So this is really great and thanks for sharing. I started using this is there a way to send these logs to Log Analytics? I discovered this article would something like this be possible? Any recommended ways to set this up?
https://docs.microsoft.com/en-us/azure/azure-monitor/platform/collect-activity-logs-subscriptions

Looking further into this if traffic analysis is enabled then these are already in Log Analytics


Moved CustomCache to utils

Codecov Report

Merging #24 (6fcb1b2) into master (b000b19) will increase coverage by 0.18%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
+ Coverage   61.48%   61.66%   +0.18%
==========================================
  Files          42       42
  Lines         527      527
  Branches       17       17
==========================================
+ Hits          324      325       +1
+ Misses        203      202       -1

Impacted Files
Coverage Δ

.../panda/user/token/AuthenticatorBasedOnHeader.scala
0.00% <ø> (ø)

...pandafolks/panda/utils/cache/CustomCacheImpl.scala
100.00% <ø> (ø)

...pandafolks/panda/user/token/TokenServiceImpl.scala
100.00% <100.00%> (ø)

...github/pandafolks/panda/user/UserServiceImpl.scala
90.90% <0.00%> (+4.54%)
:arrow_up:

Continue to review full report at Codecov.

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


Warning in pixReadMemJpeg

I got a new issue after installation and specified tessdata directory:

localhost $ > tesseract /scratch/NBS/code/captcha/test.jpeg hahaha
Tesseract Open Source OCR Engine v3.05.00dev with Leptonica
Warning in pixReadMemJpeg: work-around: writing to a temp file

pixReadMemJpeg, what is that? How to solve it?

The warning comes from the used leptonica library. You can find a copy of the leptonica source with the file that logs the warning here:
https://github.com/peirick/leptonica/blob/8498455d4bbc9df94f767bb030df1f6c37071c69/leptonica/src/jpegio.c
As far as I see its just because the leptonica library is built without the HAVE_FMEMOPEN definition. So It uses a temporary file instead of memory maped files. This is not tragic.

Thanks for this information. I have just installed tesseract with pip install pytesseract, then everything seems fine.


fix hanging w/ fullscreen check in 1.19+

1.16-1.18.2 all update options.txt accordingly when fullscreen is toggled
mojabg broke it aaigain in 1.19 ,.


Add ~BH~ Hell's Maw (Low pitch) by Blackhole12

Song Name
~BH~ Hell's Maw (Low pitch)
Artist Name
Blackhole12
Source
Youtube
Youtube Link
oDqZ-U1LQrs
Direct File Link
No response
Song ID
120376
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 13183849

accept
On Sat, Jul 20, 2024, 12:53 PM auto-nong[bot] @.***>
wrote:

Thanks for contributing!
Someone will soon review your request.
Here is the JSON result for the reviewer:
{
"name": "~BH~ Hell's Maw (Low pitch)",
"artist": "Blackhole12",
"source": "youtube",
"startOffset": 0,
"yt-id": "oDqZ-U1LQrs",
"songs": [
120376
]
}
To accept the request, a reviewer needs to write "accept".
—
Reply to this email directly, view it on GitHub
https://github.com/FlafyDev/auto-nong-indexes/issues/1613#issuecomment-2241205306,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJSK7HEU3OVF46EQO2IOJP3ZNKIXPAVCNFSM6AAAAABLGCLU7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGIYDKMZQGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

reject
already accept the same submission


Summarizer is Broken

I am opening a summary issue (sorry could not resist) here for the fact, that the summarizer is broken. This is a shame because the summaries could be very helpful for debugging.
See also the issues #396 and #350 created earlier this year. @AlexKuhnle mentioned, that tf.contrib.summary is the way to go but then two days later was not sure any more after seemingly failing to quickly do the port.
So I tried the same and also failed :-) but maybe somebody else wants to continue my half-done work? Feel free to grab my feature branch if it helps. Unfortunately I do not have the time to continue on that right now.
Some pointers if you decide to go this route:

Code (including documentation which is not readable in the official tensorflow web page rendering) for tf.contrib.summary
Code (and documentation) for session hooks.
When you look into my feature branch you can see that I mostly just renamed tf.summary to tf.contrib.summary where it applies and I am using the UpdateSummarySaverHook in util.py to set up the summary system. It does not crash (but also does not produce any output) for the inputs and gradients labels and crashes as soon as the losses label is enabled.

Hi, any update on this? Many of us are expecting a solution, thanks for the help!

Nope :-( still did not get around to look deeper into it. Just view it as a black box and optimize the hyperparameters using SMAC or hyperopt ;-)

This was not meant to be taken too serious. Basically what I meant is: instead of looking into your system internals (using the summaries) and look what is wrong with it to decide what parameters and settings to change, just randomly play around with them until it works. This random playing around with settings is called hyperparameter optimization and there exist toolkits do do that. SMAC and hyperopt are two popular ones.

Please, please fix summarizer! Unfortunately without it tensorforce mostly useless piece :( By the way, as I understood,  summarizer was starting crashing after new version tensorflow was rollout, but  what exactly last know tensorflow version still able to run summarizer?

Hehe, @madpower2000, that's quite a harsh judgement. ;-)   The problem is that the old TensorFlow summarizers struggle with control flow stuff, which TensorForce makes extensive use of, and while the new summarizer framework is supposed to work better, it still seems to struggle with some bits. I want to assess the new situation soon and will let you know.

Sorry for harsh judgement, I didn’t mean it. I just was excited, when I discover yours excellent framework, guys! Thanks a lot! Awesome!
I just hoped if I will downgrade TensorFlow version then Summarizer will back to work.
But any way, is it another way control DNN convergence?

Was joking with the "harsh judgement" ;-)  it would definitely be a great feature, and it's really annoying that it seems to be TensorFlow which causes problems here (it definitely did with the old summarizer framework). Downgrading doesn't help here, things are supposed to be better now. Downgrading TensorForce would potentially help, but that's not really adviseable either. I sometimes work with tf.Print, but that requires modifying internal code, so not really useful. So unfortunately I don't have good advice right now, and just hope that I will get summarizers to work in the next days.

Sorry I am not fixing it after all. I think the work done here is awesome, and I wouldn't mind contributing but seeing that I am not getting a whole lot of support (it took 3 weeks before getting any reply on my message listed above) I have decided to switch to rllib for now. Perhaps it is of interest to you too @madpower2000

Sorry for that, @gerardsimons, I wasn't active in support for some months for various reasons. I am in the process of looking into the unanswered issues that built up over the time. If you are interested in getting involved again, let me know.

This is another treat! Thanks for link @gerardsimons!
But I will be keep eye at reinforce with working summarizers anyway, @AlexKuhnle! ;)

@all, the summarizers should work again with the latest commit, and the code now uses the new tf.contrib.summary framework. It's now relatively easy to add own summarizers in the code, just decide for a tag to be added to summary_labels and add the corresponding tf.contrib.summary command, as is done, for instance, here:
if 'losses' in self.summary_labels or 'total-loss' in self.summary_labels:
    tf.contrib.summary.scalar(name='total-loss', tensor=loss)

I haven't thoroughly checked existing labels, but preliminary tests worked well. Let me know if you encounter any problems.


Update zigbee2mqtt to 2.9.0

Please update my adapter ioBroker.zigbee2mqtt to version 2.9.0.
This pull request was created by https://www.iobroker.dev c0726ff.

2.9.0 created 21.7.23
User 72 (5%)
Ok


Why is the CSS so messed up?

Why is the CSS so messed up? I did everytihng the tutorial said, found here - https://github.com/BanManagement/BanManager-WebUI#preperation
https://gyazo.com/c8ec88c3d1df1fc9103424abbdee390c

Looks like an issue with the language file, do you have en.json in the folder l10n?
And in the config, is the value $settings['language'] set to en?

Yes I do have language set to en

And when I go into the Admin CP: https://gyazo.com/524696959664bfff487d0c15b8e5df93

Can you open the developer console in your browser and check for any errors?

Google Chrome
https://gyazo.com/b46056b718ff82cbe9ac844395f8391d

Nevermind, guess I'll just have to use an older version of BanManager which works.

Duplicate of #95
@IceRaider Using an outdated version is not really a solution for this. I think I just found the bug
Stay tuned for updates regarding this issue in #95.


Dark mode

Description
Dark mode makes its return to BloodHound!
We are working on solidifying our design system and making styles more uniform throughout BloodHound. Updating our palettes and using them in a consistent way enables us to apply different themes to the application. As such, we begin this endeavor with introducing new styles and palettes for both light and dark themes.
The dark mode feature will be hidden behind a feature flag that can be enabled via the Early Access Features page. Enabling this feature will allow one to toggle dark mode on and off from within the popover menu that opens when clicking on the gear icon in the header of the application.
This setting is persisted and loaded in from local storage so that it remains between logging in and out as well as refreshing the page or closing it and returning to the site.
Big thanks to @rvazarkar , @benwaples , and our UX Designer Ryan Robin for help with the implementation and design.
Motivation and Context
This PR addresses: BED-2566
How Has This Been Tested?
Unit test was added for the logic of persisting the setting in between logins but otherwise most of the changes are style changes.
Screenshots (optional):

Types of changes

New feature (non-breaking change which adds functionality)
Database Migrations

Checklist:

[x] I have met the contributing prerequisites

Assigned myself to this PR
Added the appropriate labels
Associated an issue: https://github.com/SpecterOps/BloodHound/issues/672
Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing

[x] I have ensured that related documentation is up-to-date

Open API docs
Code comments (GoDocs / JSDocs)

[x] I have followed proper test practices

Added/updated tests to cover my changes
All new and existing tests passed

🎉 🍾

I'm scared but I am ready!


Can't navigate to the same route twice in the Demo app

I only just cloned the project - so I will investigate myself.
I'll just keep adding whatever I stumble on if you don't mind! :)

Good idea. The same route twice is not working yet because the back button is not wired up to pop routes, and the new view stack is not compared to the current view stack when calculating actions.

I might have a solution ready in a few hours. Will update accordingly

I'll hack away at it tomorrow. There are some things I didn't account for.
However, the question is whether you want to encourage users NOT to use the default back button?
The problem with it is, that the only way to detect a back event is:
public override func viewWillDisappear(animated: Bool) {
        super.viewWillDisappear(animated)

        if (self.isMovingFromParentViewController()){
            // Your code...
            print("I am going back");
        }
    }

The way to make this easy to use for the user - is to subclass uiviewController - and the equivalent in Appkit - and make users of the router use this instead of normal uiviewcontrollers. However, this bypasses your normal routing logic, since it pops the controller from the stack for you. You could notify the router of the change from in here, and have it update the path segment - but it'll need a popFromStack method rather than using the setStack method - and then it needs to NOT popFromViewController when this happens, since the viewController is already popped.
Furthermore, the viewController needs access to the router - which get rather messy, since you instantiate the presenters before the router is instantiated.
I haven't thought it completely through yet - but it might be much more clean to remove the back button by default - and provide a custom implementation (that looks exactly the same) to users instead.
Let me know and I'll hack away at it on the plane tomorrow :)
(I'm missing doing this with reduxKit btw :D - but I do get why it has to be decoupled completely ;) )

Cheers for the dismiss view controller fixes. We can refactor it in the future. The demo is working correctly now. Fixed in #6 #7.

I've change the location where dismiss get called from in #9 to didMoveToParentViewController because if a user only half swipes a view away and decides to cancel the action, then this is the only function that reliably gets called only after the actions completes.
Also move the dismiss calls to a protocol (DismissEmitter) to be able to remove dismiss from needing to be passed into every presenter and view controller. Path is still passed in as it likely contains critical state information like ids.


[BUG] EWW_NET is all 0

Checklist before submitting an issue

[X] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[X] I have specifically verified that this bug is not a common user error
[X] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Description of the bug
EWW_NET magic variable return 0 for all interfaces, despite btop showing traffic and ping explicitly run to create traffic on target interface.

Reproducing the issue
Just updated to the most recent version of eww.
Expected behaviour
EWW_NET should be populated.
Additional context
No response

Can confirm, updated to version 0.5.0 and got this bug, same for the latest git commit

This seems like an issue with the sysinfo crate. I tried logging the old_rx_bytes and rx_bytes the crate keeps track of to find the number of bytes received since the last refresh and they were equal. Can anyone confirm whether this is true so we can open an issue in the upstream repo?
In the meantime, we can keep track of the total bytes received (which is correct), and calculate the difference in eww. The total bytes could also be exported in the EWW_NET magic var this way.

Another workaround would be to get the total bytes before and after running the networks.refresh().

I had a look at the source code of the sysinfo crate.
It seems both the refresh and refresh_list functions on the Networks struct update the data.
eww (via https://github.com/elkowar/eww/blob/d1fde927d2799211f791e7ea01cffb667c4f2b60/crates/eww/src/config/system_stats.rs#L211) calls both right after each other.
The fix would be deleting one of those function calls.
refresh_list also updates the list of interfaces. Those rarely change on a typical system, but keeping refresh_list would be closer to the behaviour pre 0.5.0.
refresh only updates the data for the currently known interfaces, which might perform slightly better, but probably only negligible.


Fix handling of MAC-only Downlink (#570)

This PR ensures that MAC-only downlinks (empty FRMPayload) do not contain an FPort field.
This PR additionally includes:

a refactor of LoRaWAN conversion in the Handler
a small change in LoRaWAN-Protobuf conversion that keeps pointers intact

Note that this PR focuses on the Handler (application layer) and therefore does not add support for encrypted MAC commands (in FRMPayload, port 0)

Coverage increased (+0.03%) to 74.507% when pulling aca8f1b219da566b8c3321dc4b89cf5b7dd6097e on issue/570-downlink-fport into ac9aa64f9132aa53fff181441d6de8c4ee112763 on develop.


Yatin: Watch dlldownloader.com

Yatin requests the watch of the watch_keyword dlldownloader\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

dlldownloader\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

dlldownloader\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Rejected by Cody Gray in Charcoal HQ. Reason: 'Far too many false positives, unfortunately. See the Stack Exchange search for url:dlldownloader.com.'

Rejected by Cody Gray in Charcoal HQ. Reason: 'Far too many false positives, unfortunately. See the Stack Exchange search for url:dlldownloader.com.'


KAFKA-9295: increase start stream timeout

Since we need to wait for 3 streams reach RUNNING state, it makes sense to increase the waiting time to make the test reliable.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ableegoldman , please take a look. :)

Just ping me when the build passes, you know the drill 🙂
By the way, even if it does fail at another point later on in this test, I'd like to go ahead and merge this anyways. Hopefully increasing the timeout will at least reduce the number of failures, of which there have been quite a few, and will make it easier to investigate the remaining problems. But let me know if you'd prefer that I wait in case that does happen. Though I'm feeling optimistic it won't 🤞

This should be merged soon, and I'm confident increasing the timeout will reduce the number of failure a lot. 🤞 Let's wait for the jenkins build. :)

@ableegoldman , the failed tests are all flaky. (3 RaftClusterTest, and 1 testMetricsDuringTopicCreateDelete traced in KAFKA-9009). And most importantly, no failed shouldInnerJoinMultiPartitionQueryable test!
    Build / JDK 8 and Scala 2.12 / kafka.server.RaftClusterTest.testCreateClusterAndCreateAndManyTopicsWithManyPartitions()
    Build / JDK 11 and Scala 2.13 / kafka.integration.MetricsDuringTopicCreationDeletionTest.testMetricsDuringTopicCreateDelete()
    Build / JDK 11 and Scala 2.13 / kafka.server.RaftClusterTest.testCreateClusterAndCreateAndManyTopics()
    Build / JDK 15 and Scala 2.13 / kafka.server.RaftClusterTest.testCreateClusterAndCreateAndManyTopicsWithManyPartitions()

Merged to trunk -- let's hope these good results continue. I'm going to close the ticket again so people are more likely to report it if they see things to continue to break.
Merged about 9:58pm PST on May 5th, so please disregard any test failures on builds kicked off prior to that time (and raise any new failures by reopening the ticket)


Expose the interface to get the client name

expose the interface to get the client name
What's the problem?
On the server side, I want to get the client's name after receiving the service ticket.

New Feature

@dotnet-policy-service agree [company="{your company}"]

@dotnet-policy-service agree [company="citrix"]

@JeremyDamon-qiw the command you issued was incorrect. Please try again.
Examples are:
@dotnet-policy-service agree

and
@dotnet-policy-service agree company="your company"

@dotnet-policy-service agree


Fix NOT expression for invalid type

Fixes https://github.com/src-d/go-mysql-server/issues/726

So, when bar will give you a false condition? Only if it's literally FALSE or NULL?
What if bar is a non empty array of nils ([]interface{nil, nil, nil, ...})?

@kuba-- idk, whatever MySQL does. I don't know exactly how boolean type coercion works in MySQL, but we should do the same MySQL does.


MSYS2 instead of Cygwin

Cygwin's GCC creates dependency on cygwin-1.dll. MSYS2 with MINGW64 doesn't.
To compile on MSYS2 MINGW64, on Makefile of cish remove -ldl and on Makefile of Capote add -mconsole
Everything compiled fine, but cish is unable to compile any examples.
The error message:
$ cish -c -s fib.cish -o fib
in fib.cish: row 1, col 26
        ;
Syntax error(cannot open file).

The guide on release page said copy stdlib directory into either cish or Capote working directory. But I found this directory are already there on both directories. I overwrote it with my downloaded stdlib anyway. Doesn't work. The last resort, I copied stdlib directory into examples directory where fib.cish is placed. Still doesn't work!
I'm out of ideas.

When you include a library from the standard library, you have to include the standard library directory (ie include "stdlib/io.csh"). Some of the examples are broken tho.

It's also fail with the same error on the MSYS2 GCC (which is essentially just a fork of Cygwin GCC, it's different from MINGW64 GCC).

@TheRealMichaelWang Your Makefiles are problematic. I tried compiling with this command: cd src && gcc -c *.c && gcc -o cish *.o and magically it worked. The same is true for Capote.

@TheRealMichaelWang Your Makefiles are problematic. I tried compiling with this command: cd src && gcc -c *.c && gcc -o cish *.o and magically it worked. The same is true for Capote.
Update: it's with the MSYS2 GCC, not MINGW64 GCC.

Update: it's also work with the MINGW64 GCC. Please, @TheRealMichaelWang, fix your Makefiles.

Note: my comments are about building of cish and Capote themselves, not related to the OP's problems that his cish can't compile any examples.

When you include a library from the standard library, you have to include the standard library directory (ie include "stdlib/io.cish"). Some of the examples are broken tho.

stdlib.zip still uses .csh extension. The included stdlib of cish uses .cish extension. But I followed your guide on release page so I overwrote the included stdlib with stdlib.zip. I should use the source on release page but not clone from github as this caused the mismatch. BTW, you should make the transition from .csh extension to .cish extension complete and make a new release.

@TheRealMichaelWang The new release should be based on MSYS2 MINGW64 though. Your code is very portable, you don't need Cygwin GCC. That's the whole point of this thread. Unable to compile examples is just a minor problem.

This was fixed.

This was fixed.

I don't think so. There is no new PRs, no new commits. This means there is no code change. This was not fixed.

The stdlib.zip was fixed.

Just download the new one for 1.1.1. I fixed it.


Option to mute webhook

I have originally made this request on Trello Enthusiasts Club Discord server.
The current way to accomplish completely muting the webhook is by pinning the command to set (add/remove) custom webbits configuration and another one to remove all the webbits then just copy/pasting them to act like control on/off switches. However this is not an ideal approach.
Having custom webbit presets which users could create, edit and remove with use of bot commands would be a really great addition to the bot and would increase the level of configuration possibilities the software holds.

Mute commandsadded in #19 :+1:

Also see Trello-Bot-Community/TrelloWebhookAPI#2


google/gemma-7b：Why sometimes nothing is output in Chinese, but I see that the official demo can output it.

curl --location 'http://ip/v1/chat/completions' \
--header 'authorization: [secure]' \
--header 'Content-Type: application/json' \
--data '{
    "model":"google/gemma-7b",
    "messages":[
        {
            "role":"user",
            "content":"讲个笑话"
        }
    ],
    "temperature":0.1,
    "stream":true,
    "stop":["<|im_end|>","<|im_start|>"],
    "skip_special_tokens":false
}'
data: {"id":"cmpl-09824a3e1b9d4674aac1d11c14a42317","object":"chat.completion.chunk","created":2540668,"model":"google/gemma-7b","choices":[{"index":0,"delta":{"role":"assistant"},"finish_reason":null}]}

data: {"id":"cmpl-09824a3e1b9d4674aac1d11c14a42317","object":"chat.completion.chunk","created":2540668,"model":"google/gemma-7b","choices":[{"index":0,"delta":{"content":"<"},"finish_reason":null}]}

data: {"id":"cmpl-09824a3e1b9d4674aac1d11c14a42317","object":"chat.completion.chunk","created":2540668,"model":"google/gemma-7b","choices":[{"index":0,"delta":{"content":"|"},"finish_reason":null}]}

data: {"id":"cmpl-09824a3e1b9d4674aac1d11c14a42317","object":"chat.completion.chunk","created":2540668,"model":"google/gemma-7b","choices":[{"index":0,"delta":{"content":"im"},"finish_reason":null}]}

data: {"id":"cmpl-09824a3e1b9d4674aac1d11c14a42317","object":"chat.completion.chunk","created":2540668,"model":"google/gemma-7b","choices":[{"index":0,"delta":{"content":"_"},"finish_reason":null}]}

data: {"id":"cmpl-09824a3e1b9d4674aac1d11c14a42317","object":"chat.completion.chunk","created":2540668,"model":"google/gemma-7b","choices":[{"index":0,"delta":{"content":"end"},"finish_reason":null}]}

data: {"id":"cmpl-09824a3e1b9d4674aac1d11c14a42317","object":"chat.completion.chunk","created":2540668,"model":"google/gemma-7b","choices":[{"index":0,"delta":{"content":""},"finish_reason":"stop"}],"usage":{"prompt_tokens":27,"total_tokens":33,"completion_tokens":6}}

data: [DONE]

Gemma only supports English: https://huggingface.co/google/gemma-7b#description

But for the same question, I asked the official model online service, and it seems that I can reply in Chinese.

@zouhuigang The model you utilized is a base model. You can try using v1/completions instead.
For the chat API interface, it's preferable to use an instructed model. In your case, the recommended model is gemma-7b-it.

ok


use it must have ffmpeg and ffprobe? i am windows user.

Q
A

Bug?
no

New Feature?
no

Version Used
Specific tag or commit sha

FFmpeg Version
FFmpeg or AVConv and version

OS
Your OS and version

Actual Behavior
How does PHP-FFMpeg behave at the moment?
Expected Behavior
What is the behavior you expect?
Steps to Reproduce
What are the steps to reproduce this bug? Please add code examples,
screenshots or links to GitHub repositories that reproduce the problem.
Possible Solutions
If you have already ideas how to solve the issue, add them here.
Otherwise remove this section.

Yes, it needs it. it's just a wraper.


Fixed the container name

Since I'm the culprit ... I'll take full responsibility on this act of treason

Maybe you should take the opportunity to change the readme too :)