BLUE REFLECTION [PCSG00987]

App summary

App name: BLUE REFLECTION　幻に舞う少女の剣
App serial: PCSG00987
App version: 1.00

Vita3K summary

Version: v0.1.5
Build number: 2789
Commit hash: https://github.com/vita3k/vita3k/commit/[0cc549e1]
CPU backend: Dynarmic

Test environment summary

Tested by: nishinji
OS: Windows 10
CPU: Ryzen 9 3950x
GPU: RTX 3060ti
RAM: 32 GB

Issues
maybe too bright?
Screenshots

Log
vita3k.log
Recommended labels
Playable

overexposure fixed by turning off disable surface sync
Recommended labels

playable

Vita3K summary

Version: v0.2.0
Build number: 3621
Commit hash: https://github.com/vita3k/vita3k/commit/781e7064
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary
Tested by: Dibs
OS: Android 13
CPU: Helio P35 MediaTek MT6765
GPU: Mali-G52
RAM: 4 GB
Screenshots

Recommended labels

Playable


Default Workflow seems like a bit of a hand grenade for juniors

preface: I had a little look into the history of the default workflow after writing this issue and why it came about through the issues, so I sort of understand if there's reluctance to go back to screenshot commit and diff testing rather than this git workflow, possibly what I want isn't right for the project (in which case I might tend towards a fork). Close this if you think it's not applicable, but I need to get it off my mind as it's my main roadblock in bringing huxley as a core piece of my front-end workflow right now. The search for a good screenshot regression testing workflow continues I guess.

Hey there, this might seem a bit critical but it's only because huxley is, for me, so close yet just a little too cumbersome for use in a design heavy project where I'd like to screenshot every design component, possibly with a number of permutations.
The main problem for me is the default workflow, which is enough of a hand grenade for juniors that if it messes up their repository state, they can get confused about the correct steps to recover their work. I really believe the only tools that should mess with git should be version control tools, which this isn't, and I shouldn't have juniors thinking twice about running huxley because their repo wasn't in the right state. IMO the default should instead be something completely non-destructive, I'd think the best default would be a simple fill in the gaps approach where:
if there are tests without a recorded set of actions or screenshots missing, the CLI lists them out and then asks if you'd like to fill them out:
$ hux project/Huxleyfile.json

The following tests are missing recordings or screenshots:
InputLockup
SearchPanel
WidgetList

Do you wish to record and write screenshots for them now [Y/n]

...and if the recordings and screenshots ARE in place, runs through the lot with a less verbose output, grouped by Huxleyfiles, ie:
$ hux project/Huxleyfile.json

./project/Huxleyfile.json
  InputLockup  1 ✔  2 ✔
  SearchPanel  1 ✔  2 ✔  3 ✔
  WidgetList  1 ❌  diff at project/Huxleyfile/WidgetList.hux/firefox-1-diff.png

The only other thing I'd potentially want here would be an 'update' mode, where you can run through the entire set of tests, and if the test fails, have a chance to look at the result and see whether you want to replace the existing screenshots or not.

You know what, this is a good point. I myself don't like the default workflow this much. We should change it.
Currently the repo's still maintained but I got annoyed enough by selenium that I'm just leaving this here, lol. Once I get the time (and if you deem this important enough), I should restart working on this actively.

@chenglou I understand that... it feels like the tools aren't ready yet. Just wanted to say, that I'm still watching this repo (and hoping for progress) :grinning:

Hey @chenglou, if you feel this is a reasonable mode to work on, I'm happy to have a crack in a fork and then send up a pull request. I'll set it up so it's a mode option, ie hux --shot-capture, hux --shot-update, then you the ball can be in your court regarding when, how, if you want to bring it in.

@MalucoMarinero do you happen to use babel? I was wondering whether I should convert the codebase to use it. If not, feel free to work on the existing codebase. If so I should upgrade it first so that it doesn't look too messy.

Yeah, I use babel, but I can get by in es5 or 6, makes no never mind to me.

Alright then, go ahead =).
If you feel like it, remove the default workflow too! That was an interesting experiment to say the least.


Allow to send command val

Proposal:
Enter teleoperation mode and display it, e.g. press t from normal mode
Staying normal mode but enable sending command val:
Start sending while a button is pressed (e.g. x)
Send 0 on all directions while x i s pressed
accelerate by pressing  wsqe (forward backwards left right) and ad (rotate) each press increments the speed
if x is released, send 0

How about:

The default is view mode: wasd move the view with no effect on the robot
t enters teleop mode, the view is centered on the robot and wasdqe drive the robot. 0 is sent  if nothing is pressed for safety
e (I don't think we need to rotate the map, so it's probably free) enters send pose mode, the view centers on the robot and wasdqe move a "ghost" robot. Enter confirms and sends the pose, while esc resets the ghost (I wanted to implement this hopefully today as #8 if you and @carzum agree)

I like the idea to move the ghost robot, but we would probably also need to move the lasers to give direct feedback for alignment.
I think it would be best reserve  qe for teleop of omnidrive robots. Not moving when nothing is pressed is best and one could use an exponential curve mapped to the duration of a key being pressed for the velocity. (needs some experimenting)
Maybe m to toggle between the 3 modes? We can use the titlebar to show which mode is currently active


Wasting Outputs

After fixing a bug in the code, the calibration has slightly changed (see attached). We need to add some new plots but also re-work on the existing calibration
To do:

[x] Add new plots on wasting prevalence
[ ] Rework on the existing plots
wasting-plots-new.docx

Hi @timcolbourn and @andrew-phillips-1. Kindly find attached for wasting plots following our discussion on adding two plots on wasting prevalence. Thanks
population : 20,000
simulation period : 2010 - 2030
wasting-plots-em.docx

Good morning @mnjowe   This is good to see and exactly what I had in mind.  I will let Tim comment on how closely he thinks it reflects the data.

Thanks @mnjowe the plot looks good - the prevalence should be around 3% so it is close enough, but we can work on it more as part of the paper - it's interesting to see that it goes up slightly to 2030 rather than staying the same - any ideas why this might be?

Hm, a good observation. I'm not sure as to why yet. Could it be caused by the risk factors of wasting? I will have test different scenarios to be sure about this

These are the output figures with current version of the code:
wasting_all_figures__2024-10-11T232204Z.pdf

In previous versions, the incidence was recorded as follows:

Each month within Wasting incidence polling event, it was decided who among non-wasted will become moderately wasted, but then all who were non-wasted before the polling event are recorded as the incidence cases of moderate wasting or normal WHZ.
When a child progresses to severe wasting it is recorded as incidence of severe wasting.
Annual incidence counts are then logged, hence those who would not become wasted at all in the year, would be recorded as non-wasted incidence case each month.

In current version:

Each month within Wasting incidence polling event, it is decided who among non-wasted will become moderately wasted, but only those who became moderately wasted are recorded as the incidence cases of moderate wasting.
When a child progresses to severe wasting it is recorded as incidence of severe wasting.
Annual incidence counts are then logged.

Therefore, current version records only incidence cases of moderate and severe wasting. But we would like to know what proportion of the children becomes wasted (moderately, and severely). So we need to also know how many children were not included as an incidence case.
Also, I'm not sure how correct is this recording of the incidence. The natural progression/recovery from moderate wasting occurs in only 81 days, and possible recovery from severe wasting to MAM (which could lead to moderate wasting) due to treatment can occur in 3 or 4 weeks. Hence, theoretical example of wasting incidence recorded for one child within one year by months:

moderate
x
x
severe
moderate
x
x
severe
moderate
x
x
severe

But I think we only want one recording per child per year, so I would say the last information?
So we could have an attribute un_WHZ_category_last_year and at the end of the year compare it to un_WHZ_category_current, for which we could define:

incidence of moderate wasting as if worsen from non-wasted,
incidence of severe wasting as if worsen from non-wasted or moderate wasting,
no wasting incidence if none of the previous cases.

@timcolbourn, what do you think?

The wasting prevalence per year is quite different from the previous version. I’m not sure which of the changes exactly led to this; see the figure on page 2 in the wasting_all_figures__2024-10-11T232204Z.pdf.

@timcolbourn, As we discussed earlier, the prevalence proportions within age groups were calculated as
number of wasted children in the age group  / total number of children younger than the high bound of the age group,
which was corrected to
number of wasted children in the age group  / total number of children in the age group
Hence, different outcome in figure on page 3 in the wasting_all_figures__2024-10-11T232204Z.pdf.

On page 4 in the wasting_all_figures__2024-10-11T232204Z.pdf, Model output against Global Burden of Diseases (GDB) study data, all seems fine, except deaths for females between 2015 and 2019.

@timcolbourn, However, all these outcomes are based only on one run. I think, the analysis script should be updated to be based on multiple runs, don't you think?

Thanks @EvaJanouskova - please can you check that Figures 2 and 3 are actually prevalence (a cross sectional snapshot at one timepoint) rather than cumulative incidence (due to the theoretical example you give above).
If they are prevalence, then the recovery rate (and treatment rate) need to be increased so the prevalence is roughly constant over time from 2010 to 2029.
For Figure 3, if it is prevalence, we might expect it to go up a bit as children get older, but not to 25% - maybe to something like 5% so the average prevalence across the all ages 6-59 months is ~3%.  Though would also be good to check the data on that (In Stata you can ssc install zanthro to caculate z-scores etc).

Ok - please add an HSI event to detect MAM.
I'm not sure about natural recovery from SAM, I think that is unlikely (though I guess could happen with better food at home if the family circumstances improve) so would need treatment. But we have SAM treatment as highly likely in the model?
How long are children staying SAM? I think if they are SAM for a long time they would die without treatment (and I think there is a parameter for that?) but they shouldn't stay SAM that long as should be nearly all treated?

the death from untreated SAM is not currently in the model, we could also add that (it is one of future TODOs: https://github.com/UCL/TLOmodel/issues/1481)
there is only death after care, so only if treated
if treated, they will die/recovery to MAM/fully recover in 3 or 4 weeks, see figure 4 in the wasting write-up, depending on presence of complications (with complications 4 weeks of treatment, without 3 weeks)
I'm not sure what is the care-seeking rate, but once they seek the care due to SAM symptoms, the coverage for outpatient care is 0.82, and for inpatient care (if complications present) is 0.98.

ok, so maybe the care seeking is too low? as most should be treated

Seems that care_seeking_odds_ratios of 'weight_loss', the SAM symptom, is always 1.0. If  I understand it correctly, it means that it has no influence on care_seeking rate, and it it then given by other characteristics (age, urban/rural, region of residence, and wealth quintile) or other symptoms.
I have printed some probabilities of seeking care for the children under 5 with SAM:
743     0.639365
1696    0.482696
dtype: float64
prob_seek_care=person
939     0.511020
1798    0.697783
dtype: float64
prob_seek_care=person
1798    0.941607
dtype: float64
prob_seek_care=person
894     0.821993
1099    0.704299
1283    0.620194
1537    0.639365
dtype: float64
prob_seek_care=person
73      0.697783
804     0.646503
1465    0.576455
1795    0.639365
1849    0.639365
dtype: float64
prob_seek_care=person
1093    0.482696
2006    0.697783
dtype: float64
prob_seek_care=person
587     0.511020
1520    0.665063
dtype: float64
prob_seek_care=person
319    0.482696
dtype: float64
prob_seek_care=person
232    0.819018
720    0.639365
dtype: float64
prob_seek_care=person
1911    0.791558
dtype: float64
prob_seek_care=person
453     0.511020
527     0.639365
1262    0.665063
dtype: float64

In previous versions, the incidence was recorded as follows:

Each month within Wasting incidence polling event, it was decided who among non-wasted will become moderately wasted, but then all who were non-wasted before the polling event are recorded as the incidence cases of moderate wasting or normal WHZ.
When a child progresses to severe wasting it is recorded as incidence of severe wasting.
Annual incidence counts are then logged, hence those who would not become wasted at all in the year, would be recorded as non-wasted incidence case each month.

In current version:

Each month within Wasting incidence polling event, it is decided who among non-wasted will become moderately wasted, but only those who became moderately wasted are recorded as the incidence cases of moderate wasting.
When a child progresses to severe wasting it is recorded as incidence of severe wasting.
Annual incidence counts are then logged.

Therefore, current version records only incidence cases of moderate and severe wasting - see figure on page 1 in wasting_all_figures__2024-10-11T232204Z.pdf. But we would like to know what proportion of the children becomes wasted (moderately, and severely). So we need to also know how many children were not included as an incidence case.
Also, I'm not sure how correct is this recording of the incidence. The natural progression/recovery from moderate wasting occurs in only 81 days, and possible recovery from severe wasting to MAM (which could lead to moderate wasting) due to treatment can occur in 3 or 4 weeks. Hence, theoretical example of wasting incidence recorded for one child within one year by months:

moderate
x
x
severe
moderate
x
x
severe
moderate
x
x
severe

But I think we only want one recording per child per year, so I would say the last information? So we could have an attribute un_WHZ_category_last_year and at the end of the year compare it to un_WHZ_category_current, for which we could define:

incidence of moderate wasting as if worsen from non-wasted,
incidence of severe wasting as if worsen from non-wasted or moderate wasting,
no wasting incidence if none of the previous cases.

@timcolbourn, what do you think?

This is actually not true. We actually only log incidence if it is incidence of moderate wasting from non-wasted, or if it is progression to severe wasting scheduled during incidence of moderate wasting. So, if the child's wasting status improves from severe to moderate after treatment it won't be logged as incidence. On the other hand, such a child is not send for MAM treatment, and no natural recovery or progression back to severe wasting is scheduled, so the example above would actually look as follows:

moderate (incidence)
x
x
severe (incidence)
moderate after treatment, stays like that for good
x
x
x
x
x
x
x

I think we could start there. Send children recovered from SAM to MAM following the treatment for MAM treatment, or schedule natural recovery or progression back to severe wasting. Without logging as incidence, or?

Hi @timcolbourn, What data/information do we have on prevalence/incidence to calibrate the module? Do we know the prevalence by severity and/or by age group? Do we know anything about incidence per year, or any other relevant data/information? And what is the source for the prevalence being approximately constant around 3%?

The data is from the Malawi 2015-2016 DHS (the latest one): https://dhsprogram.com/publications/publication-fr319-dhs-final-reports.cfm
see Figure 11.1 on Page 161 (4% in 2010, 3% 2015-6).  Table 11.1 on Page 170 does actually have a breakdown by age group and interstingly it goes up from 6-8 months old to 9-11 months, and then down through to 36-47 month but up again in 48-59 month olds.
Actually also the Malawi MICS 2019-2020: https://microdata.worldbank.org/index.php/catalog/4286/related-materials
has data on Wasting: 2.6% prevalence, and also provides detail in Table TC.8.1 on page 233 of the report

ok - I think maybe what was intended was that ~100% with SAM seek care so if the parameter is an odds ratio that should be set really high at like 20 or 50 or something?

if the odds are set to 20, the probs of seeking care are as follows:
prob_seek_care=person
304     0.964565
359     0.954341
412     0.972571
1342    0.985815
1922    0.975438
1999    0.993118
dtype: float64
prob_seek_care=person
412    0.979081
dtype: float64
prob_seek_care=person
1999    0.990197
dtype: float64
prob_seek_care=person
1922    0.976376
dtype: float64
prob_seek_care=person
1999    0.987557
dtype: float64
prob_seek_care=person
359    0.9572
dtype: float64
prob_seek_care=person
304    0.965903
dtype: float64
prob_seek_care=person
304    0.951992
dtype: float64

Hi @timcolbourn, With current version, the prevalence is lightly lower (maybe even too low in 2010), but then is growing up to 10% in 2030. :/
wasting_all_figures__2024-12-11T003745Z.pdf

ok, so looks like there's still an issue with cases not recovering or dying? i.e. too many continue to be wasted?
are you able to quickly see how long children are wasted for on average in the output?
could it be as simple as ensuring wasting is turned off when kids reach their 5th birthday?

are you able to quickly see how long children are wasted for on average in the output?

Unfortunately not.

could it be as simple as ensuring wasting is turned off when kids reach their 5th birthday?

We can test that.

Hi @timcolbourn, With current version, the prevalence is lightly lower (maybe even too low in 2010), but then is growing up to 10% in 2030. :/ wasting_all_figures__2024-12-11T003745Z.pdf

Also the deaths here were too high. Therefore, I've updated the prob_death_after_SAMcare according to what I found in a paper (substantially lower), hence also increased prob_mam_after_SAMcare.
Also, I didn't find any use of gender as predisposition to wasting or any other gender-based assumption in wasting module. Hence I joined the deaths F+M together and now we actually have more closer look to GBD data I would say. (Of course, the growing prevalence still needs to be fixed.)

could it be as simple as ensuring wasting is turned off when kids reach their 5th birthday?

We can test that.

Well, we calculate the proportions only in children under 5, so even if they stayed wasted after 5, they won't be counted in. These are all proportions of wasted children under 5 among all children under 5.

@mnjowe, @thewati, I think the module even only works with children under 5, isn't it? Would you know where/how it is done? (Where to find it in the code?) Thanks!

@mnjowe, @thewati, I think the module even only works with children under 5, doesn't it? Would you know where/how it is done? (Where to find it in the code?) Thanks!

Hi Eva, So the code is polling then logging children under 5. All children above 5 are ignored/left out. This is done in the Wasting_IncidencePoll. At line 739 as seen below, we selected only those under 5.
not_wasted_or_treated = df.loc[df.is_alive & (df.age_exact_years < 5) & (df.un_WHZ_category == 'WHZ>=-2') &                                        (df.un_am_tx_start_date != pd.NaT)]
I hope I haven't messed your question.

@mnjowe, @thewati, I think the module even only works with children under 5, doesn't it? Would you know where/how it is done? (Where to find it in the code?) Thanks!

Hi Eva, So the code is polling then logging children under 5. All children above 5 are ignored/left out. This is done in the Wasting_IncidencePoll. At line 739 as seen below, we selected only those under 5. not_wasted_or_treated = df.loc[df.is_alive & (df.age_exact_years < 5) & (df.un_WHZ_category == 'WHZ>=-2') & (df.un_am_tx_start_date != pd.NaT)]
I hope I haven't missed your question.

What I meant is that any time population.props is loaded, there are no alive individuals over 5 in it. I looked at all of them within the wasting module, and every time we save df = population.props, all the alive are under 5.

Hi @EvaJanouskova . Perhaps you were running a test that's configured to work with under 5's only? I tried running it and I can see individuals alive and over five as well. What script were you running?

@mnjowe, @thewati, I think the module even only works with children under 5, doesn't it? Would you know where/how it is done? (Where to find it in the code?) Thanks!

Hi Eva, So the code is polling then logging children under 5. All children above 5 are ignored/left out. This is done in the Wasting_IncidencePoll. At line 739 as seen below, we selected only those under 5. not_wasted_or_treated = df.loc[df.is_alive & (df.age_exact_years < 5) & (df.un_WHZ_category == 'WHZ>=-2') & (df.un_am_tx_start_date != pd.NaT)]
I hope I haven't missed your question.

You couldn't know what I meant because itis not true. There was just a bug in calculation of under5s in logging, and when I used the same to calculate above5s it always told me it is empty, hence I supposed there are no individuals over 5 used in the module, because it seemed there are no in the whole population df.
Thanks anyway, @thewati.


dehhlflfdndv

Nice issue. :stuck_out_tongue: :smile:

I'm having this issue too

God sorry guys :) accidentally touched my yubikey while on the page which was interpreted by github as a hot key to create an issue, enter text and submit. :)

Alex

On Mar 1, 2016, at 3:33 PM, Luís Rudge<EMAIL_ADDRESS>wrote:
I'm having this issue too
—
Reply to this email directly or view it on GitHub.


further improvement of Lazy.get()

thx @jbgi for the hint!

Current coverage is 96.98% (diff: 100%)

Merging #1571 into master will increase coverage by <.01%

@@             master      #1571   diff @@
==========================================
  Files            88         88
  Lines         10642      10642
  Methods           0          0
  Messages          0          0
  Branches       1813       1813
==========================================
+ Hits          10320      10321     +1
  Misses          179        179
+ Partials        143        142     -1

Powered by Codecov. Last update 63e7872...3b8171e

?

Aargh, sorry @paplorinc. I've overseen the comments. Will apply your comments soon and send a new PR.


react-step-5

Step 5 check for the Carbon tutorial.
Thanks!
Edit:  Here's the bluemix link
https://carbon-tutorial-mcronk.mybluemix.net/#/

Missed that!  Here is the link: https://carbon-tutorial-mcronk.mybluemix.net/#/


Philippemiron readme

Fix #106

I need to be reminded: how do we update the documentation to have this function listed in the API reference?


one 👋 ?

It's a nice, simple coding. But as a matter of fact, "one ();" function must be added, It will be very handsome :)

                        var one = function (types, selector, callback) {
				on(types, selector, function callbackWrapper(e){
					callback(e);
					off(types, selector, callbackWrapper);
				});
			}

Added under the name once(): https://github.com/cferdinandi/events#once


Updating pods to Latest Version

Fixes #283
Changes: Pods are updated to Latest Version 1.5.2.

@chashmeetsingh please review the pr!


Split non-default themes to separate assemblies

The original theme based design a few years ago was aiming to separate the themes to individual assemblies. In this commit the split is finally carried out, 567cfde23a51d35b05723e8b9a52ddbe5a01104f
It should demonstrate how to create a new theme (VS 2013 Blue) from another theme (VS 2012 Light) gradually, as currently many elements are borrowed directly (while the final work might fully use its own elements, who knows).

@roken what's your feedback on this?

I generally oppose using assemblies for purely organizational purposes, but it seems quite reasonable that an application would only package a single theme (not that these assemblies will have a very large footprint).  I can get behind this.

Merged vs2013blue branch via cb4182b4b6184416a8004201d485a1dc064cbef8. Closed this now.


bug: return to supporting quote inside unquoted field of client audit.

We used to support that case, but it was unintentionally removed in 62df8a770b05a87e8d20e686d86d28db540f0d68.

oops oops i knew there was something else i was supposed to do


Menu - Make menu changes visible without a reboot of the app.

Menu - Make menu changes visible without a reboot of the app.

Not as easy as it seems will have to look further into this.

Will be available in V<IP_ADDRESS>. Will look into this in the future for better cleanup or a better solution altogether.


Collections Fold task should be changed

I can't think of any scenario where I would solve the Collections Fold task using fold efficiently. I think it should be changed to showcase a realistic scenario for fold. This task could be reused as an example for reduce though. Here is a solution I think is good for this task.
    val customerProductSets = this.customers.map {
        it.orders.flatMap { it.products }.toSet()
    }

    if (customerProductSets.isEmpty()) {
        return emptySet<Product>()
    }

    return customerProductSets.reduce { acc, products -> acc.intersect(products) }

Or an even more optimized solution:
    if (this.customers.isEmpty()) return emptySet<Product>()

    return this.customers.asSequence()
            .map { it.orders.flatMap { it.products }.toSet() }
            .reduce { acc, products ->
                acc.intersect(products)
            }

Also, the function name in N22Fold.kt is getSetOfProductsOrderedByEachCustomer which is confusing to the actual test testGetProductsOrderedByAllCustomers.
I inferred code to get all products ordered and test to get common product ordered by all customers.


less strict decoding?

is there a way to use non-strict JSON, allowing for final commas?

Not currently. What do you need it for @mattvonrocketstein? Have a good example?

I'm also needing to relax the decoding. MongoDB convetion for ObjectIds is "$oid": string, but the decoder reports $ as invalid character.


Scala 2.12 version?

Any rough idea if this will be hard?

I should communicate more. This is actually already done and available as a snapshot release. I still have a few bits and bobs to tidy up (mostly documentation to write) before an official release, but if you want to have an early taste, you can update to version 0.1.8-SNAPSHOT.
If you don't already have the sonatype snapshot resolver in your build, you'll also need to add the following line to your build.sbt file:
resolvers := Seq(Resolver.sonatypeRepo("snapshots"))

Note that for this kind of question, you're probably going to get better / faster answers on the gitter channel.

Official artifacts for 0.1.8 have been published and should make their ways to maven central within the hour.


Moving the repo to an organization

Dear colleagues,
I'm planning to move this repository to an organization. I would still like to retain control of merges for now (to maintain consistency and style as we grow), but I think we have enough content in the package where it's important to signal to the community and prospective users that this is now a team effort.
I've reserved "TidierOrg" for now on GitHub. "Tidier" is already taken, and its owner hasn't replied to my outreach. This would be similar to "MakieOrg" and would help distinguish the organization from the underlying packages. We could ask to join an existing organization as well but I think we will be wrapping packages across the ecosystem and thus it may make sense to keep this as a separate (but parallel) effort.
Thoughts on TidierOrg?
Cc: @pdimens @lazarusA @camilogarciabotero @rdboyes @pitmonticone @zhezhaozz

I'm anticipating we will have at least 3 packages in the near future:

Tidier.jl (meta-package)
TidierData.jl (all the DataFrame-oriented macros/functions in one place)
TidierPlots.jl (all the AoG-based plotting functions in one place)

And potentially... TidierTools.jl, which would make it easier for other folks to write Tidier-style macros.

Honestly, I think it should be part of JuliaData where also DataFrames.jl currently lives in. I feel that having another org will split the Julia Ecosystem ever further. But, that's just my opinion.

Appreciate the idea, @lazarusA. My main hesitations re: this are:

The package is likely to expand into plotting, which currently lives outside of JuliaData
The package uses a non-idiomatic coding style, which I think may be better co-located in a separate org

I personally view this package as a front-end to a number of other packages (and thus interdependent w/ other packages), not something intended to split the community further.

The package is likely to expand into plotting, which currently lives outside of JuliaData
The package uses a non-idiomatic coding style, which I think may be better co-located in a separate org

Agree with @kdpsingh, Tidier is not only about data manipulation in the future, and it's more a front-end to a number of other packages. I just feel that it would be a little strange to co-locate with other packages that have completely different coding style and design philosophy.

I think a separate organization is OK. TidierOrg makes sense. I guess we would make it explicit that the ecosystem is meant to make it easy for R users to make transition to Julia in as frictionless way as possible. Right?

Thanks @bkamins. Yes, the explicit intent of the org would be to make it easier for R users to transition to Julia.
We will make sure to place a spotlight on the underlying packages we are wrapping to ensure that folks can make the transition to idiomatic Julia packages.

folks can make the transition to idiomatic Julia packages

I see it as opt-in. I think many folks will be happy enough with focusing on learning TidierOrg only.

Hi everyone, welcome to TidierOrg!


🐜  Multiplatform AST parser

While the runtime is 100% multiplatform, the tooling is still mostly JVM. The most important JVM dependencies are Moshi, KotlinPoet and Antlr.
Moshi could be replaced with kotlinx.serialization. KotlinPoet is only used for codegen. Having Antlr multiplatform (either by writing a manual parser like other projects are doing or by investigating Antlr Kotlin support) would unlock a bunch of use cases for GraphQL document manipulation at runtime or shipping a K/N cli.

Done in https://github.com/apollographql/apollo-kotlin/pull/5047


Use UID instead of manually set names

I don't think we need to rework the Get/Create logic here. At least for now.

Oh, yes, I used the wrong UID 🙈

Working 🚀


[Question] is Parse Server using any memcache, global variable?

as titled. Just curious as if I store some configuration on server, is that means everytime when i want to call cloudcode and I want to access the config, Parse Server will need to re-create the variable or fetch it from database in order to process the logic? This is important since we are planning to do some logic calculation online soon.

I'm not sure what you are asking here. Parse does not use memcache, but does have some global variables. If you are accessing your Parse Config from inside your Cloud Code, that is safe. If you have some other question, please clarify.

Hi,
Thank for your information, Clarification for my questions:

It's to make sure that if every time i make a cloud function call, is Parse server will generate an instance that process that query, and shutdown once the query is completed? or Parse Server will reserved such instance for the next query?

If I make a List of array stored in Global Variable and when there is a query, the List of array will pop a variable to be fetched. will that variable accessible by all query?

Hopefully i make this clear, sorry for my poor english.
Thank you.

Parse Server stays running between queries. If you have a global variable in your cloud code, it will be accessed by all queries.

That means Parse Server doesn't keep anything in between queries except we put it on global variables?

There is some caching built in, with a default TTL of 5 seconds. You can change that or disable caching entirely if you want.

@drew-gross how can it be changed? Thanks.

@sambarboza you can try setting cacheAdapter: { ttl: 3600 } in your initialization code for enabling a cache of 1h for roles and users


Disable borders/shadows

It would be nice if there were an easy way to disable the borders / box shadow of the pickers in cases where you want to use the pickers inside your own popover component, etc.

I am adding this to the 3.0.0 milestone to make sure it makes it into the next major release we are working on!


Can we remove tap from hook？

var hook = new SyncHook(['param'])
var fn = param => console.log(param)

hook.tap('example', fn)
hook.call('frist')
// frist

setTimeout(() => {
   hook.remove(fn)
}, 3000)

Why? I can't undestand, also it is internal module for webpack, what is use case using this without webpack?

Because I using it in my Vue  Component,
When I need to notify multiple components，
I need to add a tap when each component is mounted，
and need to remove a tap when each component is destroyed，
But I can't find anything as good as tapable for handling the flow of events.
I wanted to submit PR, but the 'lib/ hookcodefactory.js' file seemed too hard to understand.

How are you using this with Vue components?

How are you using this with Vue components?

const hook = new SyncHook()

// After a while
hook.call()

// dialog-a.vue
export default {
  methdos: {
     someMethod(){}
  }
  created() {
    hook.tap('If the dialog appears', this.someMethod)
  }
  destroyed() {
      // I want to remove it...
  }
}

https://github.com/webpack/tapable/issues/71#issuecomment-419377713
@wangzongxu

Due to internal optimizations done which depends on the taps called, it would be very inefficient to remove plugins. Therefore it it's not in the API. Avoid removing plugins.
Note that tapable is optimized for a call flow like: 1. attach to hooks, 2. call hooks at lot.
It's not an general purpose event emitter.
You could still handle your use case this way:
const hook = new SyncHook()

// After a while
hook.call()

const hookMethods = new Set();
hook.tap("dialog-a", () => for(const m of hookMethods) m());

// dialog-a.vue
export default {
  methdos: {
     someMethod(){}
  }
  created() {
    hookMethods.add(this.someMethod);
  }
  destroyed() {
    hookMethods.delete(this.someMethod);
  }
}

@sokra Actually this is a real shame.  tapable has a great API that's useful outside webpack.  Lacking the ability to remove a tap really diminishes it's value.

why don't you use event hub?
const eventHub = new Vue()

export default {
    created() {
        eventHub.$on('some-action', this.addTodo)
    },
    destroyed() {
        eventHub.$off('some-action', this.addTodo)
    },
    methods: {
        addTodo() {},
    },
}

why don't you use event hub?
const eventHub = new Vue()

export default {
    created() {
        eventHub.$on('some-action', this.addTodo)
    },
    destroyed() {
        eventHub.$off('some-action', this.addTodo)
    },
    methods: {
        addTodo() {},
    },
}

why don't you use event hub?
const eventHub = new Vue()

export default {
    created() {
        eventHub.$on('some-action', this.addTodo)
    },
    destroyed() {
        eventHub.$off('some-action', this.addTodo)
    },
    methods: {
        addTodo() {},
    },
}

因为当应用变得复杂的时候，tapable覆盖的场景更全面

why don't you use event hub?
const eventHub = new Vue()

export default {
    created() {
        eventHub.$on('some-action', this.addTodo)
    },
    destroyed() {
        eventHub.$off('some-action', this.addTodo)
    },
    methods: {
        addTodo() {},
    },
}

因为当应用变得复杂的时候，tapable覆盖的场景更全面

need this feature

need this feature

@wangzongxu I find a method to remove tap:
var hook = new SyncHook(['param'])
var fn = param => console.log(param)

hook.tap('example', fn)
hook.call('frist')
// frist

setTimeout(() => {
   removeTapFromHook(hook, 'example');
}, 3000)

// remove
function removeTapFromHook(hook, tapName) {
    const index = hooks.taps.findIndex(tap => tap.name === tapName);
    if (index > -1) {
        hooks.taps.splice(index, 1);
    }
}

We only need remove the tap from the private variable taps.

That's private.
But anyway if you do that call hook._resetCompilation() to update the generated code.


Add huffman coding (encode and decode file), add tests for huffman coding.

…ding
(Put an X inside the [ ] to denote check mark [X].)

[x] If creating a new file :

[x] added links to it in the README files ?
[x] included tests with it ?
[x] added description (overview of algorithm, time and space compleixty, and possible edge case) in docstrings ?

[ ] if done some changes :

[ ] wrote short description in the PR explaining what the changes do ?
[ ] Fixes #[issue number] if related to any issue

[ ] other

Pull Request Test Coverage Report for Build 900

221 of 242 (91.32%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 75.282%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tests/test_compression.py
26
27
96.3%

algorithms/compression/huffman_coding.py
195
215
90.7%

Totals

Change from base Build 898:
0.5%

Covered Lines:
5811

Relevant Lines:
7719

💛  - Coveralls


[All hosts] (community call) Add link to June blog post

Docs Build status updates of commit 052d4cf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-ins-community-call.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Document renaming of supported org.gradle.unsafe.configuration-cache options to their finalized forms

From #24406:

Also those .unsafe.s need to be removed from every project that's using it now, please help in the upgrade guide to notice.

We should document renaming of supported org.gradle.unsafe.configuration-cache options to their finalized forms in the upgrade guide.

@bot-gradle test BD


Colour commit text when characters exceed 50

I found this feature quite helpful whilst using the git plus package. So I thought I would have a go at implementing it in git-control.

I agree that this is a good change but I have a minor issue with it:
You change the color in an RGB value, this might cause problems with different themes in Atom. I would favor it if @text-color-error was used.
The best way to do this as far as I can tell is to add something like
.warning {    color: @text-color-error   }
to the dialog.less and then add and remove it like so:
colorLength: ->     if @msg.val().length > 50       @msg.addClass('warning')     else       @msg.removeClass('warning')
Please let me know if you agree with this or if you have a better suggestion!

Yes this did cross my mind, I think I went against doing like that because I didn't want to class it as an error or warning, but in retrospect I think that having it follow the the theme is a better way to do it. Ill change it and the re-commit.
Thanks

Sounds good to me :+1:

Thanks for the contribution :+1:


Wrapped share button shows even if sharing would not work

Unfortunately navigator.share has pretty bad browser compatibility, so on some platforms, the share button at the bottom of the wrapped page has no effect. Could a workaround be implemented for platforms that do not have navigator.share or fail navigator.canShare?

I'll see if I can gate it behind whether navigator.share is present, the main compatibility issue seems to be desktop firefox though, all the mobile and other desktop browsers support it in latest versions

related: #10

Fixed by f6ee6f4


Loop with ubuntu user[BUG]

When i run it with this command on my server which is not  root user by default, it falls in to a Loop.
sudo bash< <(curl -s https://raw.githubusercontent.com/hawshemi/Linux-Optimizer/main/linux-optimizer.sh)
It give me this error and contiue showing the menu.
[*] ----- Wrong input!

OS: Ubuntu
Version: 22

If i switch to root user with  sudo -i it works ok.

The script is updated.
You should run sudo -i first and then the bash command.
Thanks for your feedback.


As part of CI build docker image based on the -SNAPSHOT jar and publish it to DockerHub

As part of CI build docker image based on the -SNAPSHOT jar and publish it to DockerHub

tag image with maven versions (ex. 1.2.0-SNAPSHOT)
make sure to NOT assign the latest tag to it
only keep 3 days worth of snapshots (configurable?)

publish image as skills-service-ci to keep clearly separated from released versions

as per discussions with sudo-may, instead of skills-service:version-snapshot, we are pushing a separate skills-service-ci image.

verified image!  latest tag is present, but that is obe now that it was decided to pubish to a separate skills-service-ci repo.
also, note that this image is not showing up (as of now) when doing a search for "skilltree", but that may be b/c it was so recently published?


Submit VCell <IP_ADDRESS>

id: vcell
version: <IP_ADDRESS>
specificationsUrl: https://raw.githubusercontent.com/virtualcell/vcell/<IP_ADDRESS>/biosimulators.json
specificationsPatch:
version: <IP_ADDRESS>
image:
url: ghcr.io/virtualcell/biosimulators_vcell:<IP_ADDRESS>
validateImage: true
commitSimulator: true

@moraru Rerun of #440 with test suite corrected from pyyaml 6.0

The specifications of your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!
Future submissions of subsequent versions of VCell to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.


[sil-ownership-verifier] Fix a few bugs and add a few tests.

I originally thought that I could get away with just using the verifier straight up, but my hubris got the better of me.
This PR contains the beginning of some simple filecheck tests for the verifier. It also fixes a few bugs that I found along the way.

@swift-ci Please smoke test and merge

@swift-ci Please smoke test os x platform

The failure was not mine.

it was a weird linker failure.


Added environment as a kubernetes resource definition

This fixes #168

@xiekeyang could you review this change?

@erwinvaneyk
This provides the workflow environment solution via helm chart installation. However, general customer have no permission to use helm install, which need kube admin privilege (like open shift platform).
So customer might like to use command fission spec apply --specdir <workflow-env-dir>, or kubectl spec apply -f <env.yaml> to create a workflow env.
What is more, customer might want to fill more parameters like resource setting, self-defined environment variables, etc, which is not involved in currant template. If we paste all possible parameters in template, it will be too long-winded.
So, IMO, we can provide:
a) Just address this PR. And we supply some doc, let reader know they can follow this template, and fill their own parameters in it. And suggest customers to create workflow env via fission or kubectl command.
b) Provide a simple workflow-env yaml sample file, with filling the necessary parameters, instead template. Put the yaml file to dir like hack/env/specs/ or example/env/specs... Let customer know they can create it by fission or kubectl. And customer will do this according to their user cases.
I think the above ways are both OK.

charts/fission-workflows/templates/deployment.yaml is an available environment spec, and removing all variables. I feel we need not to use helm command (inhack/codegen-helm.sh) any more, fission spec apply is better?

@xiekeyang -- agreed, with the directory change. It might be better to move this to the example dir to indicate that it is just an example of a workflow env definition. The codegen script is just for me/developers to keep the helm templates in sync with the example specification. Users should not need it or helm to use the spec


Improve zh-Hans translation

There is some error and improvements to be made to the zh-Hans translation. The text is a little bit much so I'm doing this in parts.

Thank you very much for your contribution!


Serviceinjection

Motivation
Service registry, followup to #30 and #26
JIRA: https://issues.jboss.org/browse/AEROGEAR-{}
Description
This PR includes the service registry and a working exmaple via Android.
Progress

[x] Service Registry
[x] Android updates
[ ] iOS updates

Additional Notes
The iOS updates require annotating the iOS classes with assemly attributes to make then not get pruned by the ios linker.  See https://developer.xamarin.com/guides/ios/advanced_topics/linker/

@ziccardi I might need a Mac's eye to help get the linker working correctly.

oh, can we add some documentation to explain how this works so that we have something we can reference to in the future?

@secondsun @ziccardi actually, the ios app works for me as well in the simulator. Does it mean this solution works for ios too?

@wei-lee No. The reason it works is because in the Example.iOS project there is the AuthenticateOptionsProvider class that has an hard dependency on the Auth.Platform.iOS project.
If you remove that, it won't work anymore because the Auth.Platform.dll assembly won't be loaded.

@ziccardi I am not sure I get you. The Example.iOS app should have a hard dependency on (or line to) the Auth.Platform.iOS. That's how the auth sdk is designed to work? Do you mean the AuthenticateOptionsProvider is actually reference a class from the Auth.Platform.iOS project, and if we remove the reference to the class (but keep the dependency), it will not work?

@wei-lee yes, that's exactly what I mean

Created a PR with a different approach on the injection. It works on both iOS and Android and we don't have to care about the linked behaviour: #36

We've decided to shelve this for now.


Layers don't play after Chapter 1 in Stories

As a user, I expect that layers in my stories will "play". Currently (staging.mapstory.org) when I advance to any chapter after chapter 1 and hit play, the data in my layers don't seem to advance.
Example - https://staging.mapstory.org/story/jacks-and-spades/.
Advance to Chapter 2 and hit play.

Multi-chapter stories only show the 1st chapter in the viewer when hitting play.
See stories created using admin account & personal account

@goudine I'm having a similar issue where changing chapters doesn't update the storypins: #121 .


How to display house_num, addr:house_num?

It's any information about style that can display house number?
Any help please?

It's any information about style that can display house number?

See the Liberty style - on  http://osm2vectortiles.org/maps/

https://github.com/lukasmartinelli/osm-liberty
http://osm-liberty.lukasmartinelli.ch/#18.22/47.07453/8.27978

Thanks @ImreSamu.
I also get from modified MapboxStreet-v7.
Easily is add new sections on your stylesheet.json, example: my modified one:
        {
            "id": "housenum-label",
            "type": "symbol",
            "source": "mapbox",
            "source-layer": "housenum_label",
            "interactive": true,
            "filter": [
                "all",
                [
                    "has",
                    "house_num"
                ],
                [
                    "in",
                    "$type",
                    "Point"
                ]
            ],
            "layout": {
                "text-font": [
                    "Open Sans Regular"
                ],
                "text-field": "{house_num}",
                "text-size": {
                    "base": 0.8,
                    "stops": [
                        [
                            18,
                             8
                        ],
                        [
                            20,
                            10
                        ]
                    ]
                }
            },
            "paint": {
                "text-color": "#633",
                "text-halo-color": "rgba(255,255,255,0.8)",
                "text-halo-width": 1.2
            }
        },

hope that help others :-)


libmemcached

It would be helpful if you mentioned in the docs that libmemcached is required. I was able to install it with this command:
sudo apt-get install libmemcached-dev

libmemcached-dev is actually a requirement of pylibmc - the documentation should be updated there: http://sendapatch.se/projects/pylibmc/


Could it run on Windows？

I have see mamba-ssm's offical page: Other requirements: Linux.  so could I run it on Windows？
Here is the page：https://pypi.org/project/mamba-ssm/1.1.4/

I think No.


refactor task components in fleet adapter

This is a broken down pr from this feedback https://github.com/osrf/rmf_core/pull/302#issuecomment-786484813

Previously the task summary msg is not fully populated, as task information (taskprofile) is missing. this is addressed here.
Refactor work in taskManager and fleetupdatehandle

Note: let me know if the refactoring work makes sense in making the implementation clearer. The expected behavior is that this won't break the existing demo scenarios.
Signed-off-by: youliang<EMAIL_ADDRESS>

@tanyouliang95 could you explain the motivation behind the refactoring of TaskManager and FleetUpdateHandle along with a summary of the changes?

This PR is mainly on refactoring work, along with changing some public fn in TaskManager, and removing some of the redundant vars. Also, some change is made to make it supportable for future task revival (without ignoring submitted bidding task).

Will close this. According to review, features in this PR will be further cherry-picked to separate chucks of pr.


MudInput inside MudChip ignore space and backspace keys

Things to check

[X] I have searched the existing issues for this bug
[X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type
Component
Component name
MudChip
What happened?
If you nest MudInput (or MudTextField) inside MudChip component, then you cannot press space or the backspace keys. However if you shift-space or shift-backspace it works...
It looks like that keyboard input is intercepted by something and those keys are filtered out.
Expected behavior
I expect that I can press space or back-space keys, and they will function properly
Reproduction link
https://try.mudblazor.com/snippet/cYQePwuoLhbbvvUf
Reproduction steps
1.Add code that looks:
<MudChip T=string Style="color: white;background-color: red">
    <MudInput Style="color: white" T="string" @bind-Value=value />
</MudChip>

@code {
 string value;
}

Relevant log output
No response
Version (bug)
7.xx and 8.xx
Version (working)
6.xx
What browsers are you seeing the problem on?
Chrome, Safari
On which operating systems are you experiencing the issue?
macOS
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

you can try using stopPropagation like this
<MudChip T=string Style="color: white;background-color: red">
    <div onkeydown="keydownhandler(event)">
        <MudInput Style="color: white" T="string" @bind-Value=value/>
    </div>
</MudChip>

<script>
   function keydownhandler(e) {
       if (e.code === "Space") {
           e.stopPropagation();
       }
   }
</script>

@code {
    string value = "";
}

Thank you for the hack. It solved the problem
However, this is a hack, and this behavior is still unexpected and should be fixed...

I think the root problem is that MudChip intercepts this keys:
https://github.com/MudBlazor/MudBlazor/blob/50d93b947b895712104524fb9910ef3d2750ff29/src/MudBlazor/Components/Chip/MudChip.razor.cs#L357-L364
If I remember correctly to prevent the scroll going down on space and instead to call a OnClick event.
@henon any ideas?

Chip was never meant to contain an input field. I guess we'd have to add a parameter to MudChip that toggles the keyinterceptor.  I guess that would be hard to do because KeyInterceptor is not built to be dynamically toggled on and off, so it would require deep changes. I'd say in this case a workaround is good enough.

Chip was never meant to contain an input field. I guess we'd have to add a parameter to MudChip that toggles the keyinterceptor. I guess that would be hard to do because KeyInterceptor is not built to be dynamically toggled on and off, so it would require deep changes. I'd say in this case a workaround is good enough.
PS: I guess you are only temporarily displaying a text field inside the chip to edit it's content? You could also (temporarily) replace the chip with a div that only looks like a chip when it contains a text field i.e. by applying the mud-chip class or whatever classes we are applying to the chips top-level to style it

Example of styling it by borrowing the chip classes: https://try.mudblazor.com/snippet/QEQSlwGuFbrEEDdL


Add class decorator ruby project module 4

In this project,

I use the Decorator design pattern to correct the names of people.
I understand the concept of inheritance and composition in deep.

Thank you for reviewing my project!!!!.

Hi @juaryimami
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that does not follow proper Gitflow
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification @prolajumokeoni.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Google maps integration and images from maps

Feature Description

Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

(Related upstream issue: https://github.com/ampproject/amphtml/issues/12209)

Closing in favor of the upstream issue.


HF push fixes

This PR fixes:
Pushing of tokenizer to HF. Due to the following line, the tokenizer was pushed in a weird state, leading to different tokenization after reloading it.
tokenizer.sep_token = " "
https://github.com/h2oai/h2o-llmstudio/issues/30
The issue is that LORA cant be merged into 8bit states
So we need to load it in float16, and then merge
Additionally bitsandbytes needs to be updated to fix an issue with weights being pushed differently to state_dict

There is still another fix missing for download of weights. Will merge main in tomorrow.

I'm getting an issue in the chat dialog using 8 bit:
  File "/media/max/3tbdrive/PycharmProjects/llm_studio/./app_utils/handlers.py", line 314, in handle
    await experiment_chat(q)

  File "/media/max/3tbdrive/PycharmProjects/llm_studio/./app_utils/sections/experiment.py", line 1196, in experiment_chat
    output["predicted_answer_ids"] = model.generate(inputs, cfg).detach().cpu()

  File "/media/max/3tbdrive/PycharmProjects/llm_studio/./llm_studio/src/models/text_causal_language_modeling_model.py", line 147, in generate
    output = generation_function(

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/peft/peft_model.py", line 716, in generate
    outputs = self.base_model.generate(**kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/transformers/generation/utils.py", line 1524, in generate
    return self.beam_search(

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/transformers/generation/utils.py", line 2810, in beam_search
    outputs = self(

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/transformers/models/gpt_neox/modeling_gpt_neox.py", line 662, in forward
    outputs = self.gpt_neox(

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/transformers/models/gpt_neox/modeling_gpt_neox.py", line 553, in forward
    outputs = layer(

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/transformers/models/gpt_neox/modeling_gpt_neox.py", line 320, in forward
    attention_layer_outputs = self.attention(

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/transformers/models/gpt_neox/modeling_gpt_neox.py", line 116, in forward
    qkv = self.query_key_value(hidden_states)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/peft/tuners/lora.py", line 539, in forward
    result = super().forward(x)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/bitsandbytes/nn/modules.py", line 242, in forward
    out = bnb.matmul(x, self.weight, bias=self.bias, state=self.state)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/bitsandbytes/autograd/_functions.py", line 488, in matmul
    return MatMul8bitLt.apply(A, B, out, bias, state)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/torch/autograd/function.py", line 506, in apply
    return super().apply(*args, **kwargs)  # type: ignore[misc]

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/bitsandbytes/autograd/_functions.py", line 320, in forward
    state.CxB, state.SB = F.transform(state.CB, to_order=formatB)

  File "/home/max/.local/share/virtualenvs/llm_studio-3NY290ou/lib/python3.10/site-packages/bitsandbytes/functional.py", line 1698, in transform
    prev_device = pre_call(A.device)

AttributeError: 'NoneType' object has no attribute 'device'


docs(kgo): add PodDisruptionBudget guide

Description
Adds a guide explaining how to define PodDisruptionBudget for DataPlane deployments.

Part of https://github.com/Kong/gateway-operator/issues/142.
Testing instructions
Preview link: https://deploy-preview-7729--kongdocs.netlify.app/gateway-operator/unreleased/customization/pod-disruption-budget/
Checklist

[x] Review label added
[x] Conditional version tags added, if applicable.

Rebased on main after merging https://github.com/Kong/docs.konghq.com/pull/8083.


feat(osmoutils): ClaimRewards and NewPosition foundations

Closes: #XXX
What is the purpose of the change
Outlines initial logic for NewPosition and ClaimRewards. Makes other pass-through changes such as:

change accumulators to sdk.DecCoins. This is done so that we can distribute and track rewards in multiple denominations
changes num_shares to be a Dec instead of an Int. This allows for future flexibility to have non-int shares if needed. Also, simplifies calculations ClaimRewards since we can multiply DecCoins by a Dec directly
remove sendKeeper from ClaimRewards API

it is counter-cohesive to pass in a keeper to an accumulator. Accumulator logic should just handle the computation logic while the caller can perform the bank send

remove accum_name from AccumulatorContent. There is no practical need for storing that in store
implement store prefixes

a prefix for accumulators
a prefix for positions

Testing and Verifying
To be added upon acceptance of changes
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (no
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? no
How is the feature or change documented? not applicable

Discussed offline. Going to merge as is to unblock further work. The tests for these methods are to be added in a subsequent PR.


Data grid not scrolling with mouse wheel

Package name(s)
Data Grid (@salt-ds/data-grid)
Package version(s)
Current
Description
Can't scroll data grid using the mouse wheel, only by finding the scroll bar on the edge
Steps to reproduce
Attempt to scroll data grid using mouse wheel
Expected behavior
Scroll using the mouse wheel
Operating system

[X] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

Browser

[X] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

Are you a JPMorgan Chase & Co. employee?

[X] I am an employee of JPMorgan Chase & Co.

Bug ranking score: 45 (using rubric v3)
Priority: high
========== BEGIN BUG RUBRIC SCORE DATA ===========
eyJ2YWx1ZXMiOnsiYWZmZWN0ZWRQZW9wbGVPcHRpb25zIjoyNS
wiYWZmZWN0ZWRDb21wb25lbnRzT3B0aW9ucyI6NywiZnJlcXVl
bmN5T3B0aW9ucyI6MTksImltcGFjdE9wdGlvbnMiOjExLCJhZm
ZlY3RlZERzT3B0aW9ucyI6MTcsInVyZ2VuY3lPcHRpb25zIjox
OSwieEZhY3Rvck9wdGlvbnMiOjE4fSwicnVicmljVmVyc2lvbi
I6M30=
=========== END BUG RUBRIC SCORE DATA ============

This is when the grid doesn't have a scroll bar or if you scroll to the end of the grid. Scrolling is blocked

So, is this not a bug then? Just wondering if it can be rejected

Discussed with @joshwooding, and the fix for this should only handle the scenario where the DataGrid has no scrollbar.
A separate issue has been created to cover the scenario where the Data Grid does have a scrollbar: #2156


Add two more targets, ros1 and pde10

I'll review; will ask for two other folks to give targets a look as well.

From @ppxasjsm: ideally we want to know that the systems are runnable with an MD engine, such as a minimization on each. Probably not possible to do direct visualization of each structure.
From @IAlibay: just being able to pass PDB files through OpenMM PDBFile could help us here. Can point you to an MDAnalysis snippet that does some sanity-checks.
From @dotsdl: we may need to run these through the same solution used for solving #20. I will identify problem cases from @IAlibay's suggestion, then loop in @bobym for those problem cases.

Further from today's meeting @dotsdl here's what I'm using to quickly look for clashes in the structures (mixing RDKit loading into MDA etc... [can send the full script off-github]): https://github.com/IAlibay/CheckStructure


Method to get just the me-card?

Can you guys introduce a method (e.g. getMe or getProfile) that allows us to fetch just the 'me' contact? This would be a really useful way to get some of the user's information and use it for e.g. pre-filling forms. 🙏🏼

cc @morenoh149


problem installing on esp8266

I am trying to install this on esp8266.
The esp was not connecting to router, so I disconnected from the Heatpump and connected to the serial monitor over usb.
I am getting the following:
 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v00053a10
~ld

fixed by removing PROGMEM from code


Qaoa example

Added doc walking through Qaoa example using mps

Merged from main into this branch - should be good now. Only thing - the doctest fails because it is trying to run the qaoa notebook which takes longer than the max timeout period of 300 seconds (as expected). I am not sure if we could disable the timeout or how else to address this.

Notebook looks great, thanks! Nice way to show off run_sweep functionality. Just a few minor comments to address.
It looks like the doctest on push finished in time and the doctest on pull_request timed out, so I'd guess it's right near the limit. I'd say it's fine to increase the execution timeout for now, it it's not too bad. Once we get tired of waiting there's better solutions we can do - substitute parameters when running on CI or, if possible, decrease runtime without sacrificing example quality.


reproduce result

Thank you for your great work!
In mv3d/lightningmodel.py, there is no loss for updating weights of  self.refine_quarter,  self.refine_half,  self.refine_full .
   # starting size --> 1/4
depth_pred = F.interpolate(depth_pred.unsqueeze(1), feats_quarter.shape[-2:], mode='nearest').squeeze(1)
depth_pred = self.refine_quarter(feats_quarter[ref_idx], depth_pred.unsqueeze(1)).squeeze(1)
# 1/4 supervision
depth_gt_quarter = F.interpolate(batch.depth_images.unsqueeze(1), depth_pred.shape[-2:], mode='nearest').squeeze(1)
loss_refine_quarter = self.mae_loss(depth_pred, depth_gt_quarter, self.hparams.depth_test['depth_interval'])
metrics = calc_2d_depth_metrics(depth_pred, depth_gt_quarter)
metrics['loss_2d'] = loss_refine_quarter
out['quarter'] = metrics

Could you please release the compelte code for training the pretrianed model ?
Thanks.

Hey, thanks for your interest!
Great catch. I was experimenting with a surface normal loss prior to uploading the code and must have accidentally removed the refinement loss when I removed the surface normal loss.
Basically you just need to add loss += loss_refine_* after each refinement step. I'll push an update soon that will fix this.
Let me know if you have any other issues
-Alex

Just pushed the fix
-Alex

Thanks a lot!!!


Update style for crrel_gipl_outputs ingest

Currently tracked style isn't valid, will re-ingest based on EDS dev style.

Closed by #72


ESP-IDF v5.x support

First of all, thanks for making your work public. Seems like it's the only repo providing some support for the WT32-SC01 dev board family.
I cannot build it with the latest ESP-IDF v5.0 though. Don't know if LVGL has the same problem, but at least LGFX does have: https://github.com/lovyan03/LovyanGFX/issues/282
Could you work it out? I'm ready to test it from my side.
Also, have you tried poring the native esp_lcd component? It's worth a try, and I see other people have tried it as well: https://github.com/esphome/feature-requests/issues/1084#issuecomment-842239946. If it's similar to ST7789 (esp_lcd provides built-in support for ST7789), then it should be ported without problems, shouldn't it?
Also, is it possible not to use LGFX?

First of all, thanks for making your work public. Seems like it's the only repo providing some support for the WT32-SC01 dev board family.
I cannot build it with the latest ESP-IDF v5.0 though. Don't know if LVGL has the same problem, but at least LGFX does have: lovyan03/LovyanGFX#282
Could you work it out? I'm ready to test it from my side.
Also, have you tried poring the native esp_lcd component? It's worth a try, and I see other people have tried it as well: esphome/feature-requests#1084 (comment). If it's similar to ST7789 (esp_lcd provides built-in support for ST7789), then it should be ported without problems, shouldn't it?
Also, is it possible not to use LGFX?

Thank you for the appreciation.
The latest released version of ESP-IDF is v4.3.4
https://github.com/espressif/esp-idf/releases/tag/v4.3.4
If you use pre-release version there are chances of broken builds all the time. I used to take master branch and after wasting time earlier chasing the bugs, I decided to stick to released build.
I will update the sample once ESP-IDF v5 is released.
In the mean time, please use this updated sample for your work. Read the README.md for all the details.
https://github.com/sukesh-ak/ESP32-LVGL8x-SDSPI
Espressif had several attempts to create display driver and all the previous efforts have been missing all the required drivers. Thus I decided to use LovyanGFX which is similar in architecture and has all the drivers already available. The other benefit is that, LovyanGFX drivers work with both Arduino & ESP-IDF which make life easier for quick testing with Arduino and then on to ESP-IDF.
Some reference from earlier.
https://github.com/lvgl/lvgl_esp32_drivers/issues/176

Thanks for the detailed feedback.
Unfortunately, I've already ported everything to the pre-release ESP-IDF v5.x. I often fire issues on their github and therefore require building their master branch to check if the problem is still there. I've tried making two copies of ESP-IDF on my machine, but it's a headache. Let me see if I can come up with a solution.
It seems you have multiple repositories with shared payloads, it's not easy to understand which one I need. Does SD SPI means it's been developed to support SD cards with SPI interface? WT32-SC01 does not have a slot for SD cards (extension boards do have, but I don't own one).

Good news!
Your project works with the latest LovyanGFX "develop" branch and ESP-IDF v5.1-dev-96-gafc6fba7f5-dirty. Both the screen drawings and the touches.

@dizcza Glad you got it working.
https://github.com/sukesh-ak/ESP32-LVGL8x-SDSPI
This is an ESP-IDF sample you can use as a template for your UI projects using LVGL with ESP-IDF & ESP32 / ESP32-S3.
3 sample configuration included already with just a header file to show how its done easily.

Unexpected Maker FeatherS3 (ESP32-S3) + Adafruit 2.4" TFT Featherwing
Unexpected Maker TinyS3 (ESP32-S3) + 1.3" TFT - ST7789 240x240
Wireless Tag WT32-SC01 (3.5" TFT Touch Display)

Some features included

Support for updating UI from different tasks lvgl_acquire/lvgl_release
UI code separation into gui.hpp
Same UI code which adapts to different resolutions
Supports shared SPI bus for SD Card
Readme explains how to have same project target different ESP32 controller.
Switch between devices using just a header file inclusion
Add your own controller/display with just a header change.
Shows battery meter animation using timer
Shows SD card status change with icon
Switch theme between Light & Dark
Scrolling long message in footer

@sukesh-ak
This looks wonderful but I am missing support for 2 additional dev boards:
ESP-WROVER-KIT with 320x240 SPI without touch
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-wrover-kit.html
Makerfabs ESP32-S3 with 480x320 parallel 3.5"
https://www.makerfabs.com/esp32-s3-parallel-tft-with-touch-ili9488.html
Any help to get the same demos working on these will be much appreciated.

@sukesh-ak
This looks wonderful but I am missing support for 2 additional dev boards:
ESP-WROVER-KIT with 320x240 SPI without touch https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-wrover-kit.html
Makerfabs ESP32-S3 with 480x320 parallel 3.5" https://www.makerfabs.com/esp32-s3-parallel-tft-with-touch-ili9488.html
Any help to get the same demos working on these will be much appreciated.

Please open an issue on this repo and I will check later today.
https://github.com/sukesh-ak/ESP32-LVGL8x-SDSPI/

@sukesh-ak Do you have by chance the correct pinout for WT32-SC01? Seems the datasheet has gotten it wrong... damn it.
Blind engineering won't take me far.

@dizcza
This is the sample which is thread safe
https://github.com/sukesh-ak/ESP32-LVGL8x-SDSPI
Check the readme for details about lvgl_acquire/lvgl_release

@dizcza
Hope to make a walkthrough video of the sample soon.


Contributor page redesigned

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #(issue no.)
Description
[Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.]

Type of PR

[ ] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Before
https://github.com/user-attachments/assets/d32eec34-6649-4d54-bc88-0c4905b471af
After
https://github.com/user-attachments/assets/2ce80cb4-1862-40b3-9d9e-5646f915caba
Checklist:

[x] I have made this change from my own.
[ ] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@PriyaGhosal Please merge this PR

@anuragverma108 Please merge this PR.

@PriyaGhosal Please merge this PR.

@anuragverma108

@Son7c This was already done before. I guess you didn't pull all the latest changes before pushing your feature/bug fixes to the main branch.

@PriyaGhosal Ya my mistake sorry.


Only write base array of a view when explicitly requested

From #989, the current ASDF behavior of writing the underlying base array of a Numpy view can lead to unexpected results, like a file being much bigger than anticipated when the view is a small portion of the base array.  Of course, this behavior can lead to space savings when multiple views of the base array are in the ASDF file.  But rather than try to infer whether to enable this behavior based on expected space savings, the simpler behavior is to make this opt-in, probably via an arg to write_to or the ASDF config.

Agree.  It would be nice to not try to infer intentions, but make intentions explicit in a kwarg.
So is the suggestion to then make a copy before writing out, and only keep the base/view if explicitly asked?  That seems sane to me.


can't use option + scroll down and option + scroll up simultaneously

OS
macOS 14.0 (Build 23A344)
LinearMouse
v0.9.5
Describe the bug
I mapped option + scroll up to increase volume and
option + scroll down to decrease volume
if i increase vol with the mapping i can't simply scroll down to decrease volume
i tried to even release the option key and try again, but it simply doesn't work
To reproduce
No response
Expected behavior
No response
Anything else?
No response

I couldn't reproduce this issue. Would you mind reproducing it and then exporting the logs from General settings?
https://github.com/linearmouse/linearmouse/assets/3000535/8b95354c-57be-4c7a-970f-6d88eda84e6d

somehow, it works now, however it's kinda laggy, is there a way to make it more responsive?
here's the log you asked for, hope this helps
LinearMouse.log


Make an existing token (e.g. WebUI, Android) not to expire

Describe the solution you'd like
On the page you can see all your tokens, you could add an "edit" or "change expiration" button to be able to change that date (to a specific one, "immediately" or "never").
That is because on WebUI and Android, it expires after ~1 month and that is a little inconvenient.
Type of feature
User Interface (UI)
Additional context
No response

Are you referring to login or manual token create on the website or android app
website user logins last for 100 years

and website manual token creation already have a never expire or you can delete for immediate expiry

Feel free to reopen this if you still have some questions

Note on why the shorter re-login time was experienced
During initial setup and host account auth token creation the expiry date is set to 7 days in the future
https://github.com/usememos/memos/blob/317cf065794df117998568f9536878c9b8751200/server/router/api/v1/auth_service.go#L224
Subsequent logins set the auth token expiry date is set to 100 years in the future
https://github.com/usememos/memos/blob/317cf065794df117998568f9536878c9b8751200/server/router/api/v1/auth_service.go#L73-L77
AccessTokenDuration = 7 days


Vagrant: HHVM errors during provisioning

Getting the following errors during VM provisioning. I'm also unable to reach the VM at heroku.local on my local machine, even after making the suggested host entry.
==> herokuwp: Unpacking hhvm (3.5.1~trusty) ...
==> herokuwp: dpkg: dependency problems prevent configuration of hhvm:
==> herokuwp:  hhvm depends on libboost-filesystem1.54.0; however:
==> herokuwp:   Package libboost-filesystem1.54.0 is not installed.
==> herokuwp:  hhvm depends on libboost-program-options1.54.0; however:
==> herokuwp:   Package libboost-program-options1.54.0 is not installed.
==> herokuwp:  hhvm depends on libboost-system1.54.0; however:
==> herokuwp:   Package libboost-system1.54.0 is not installed.
==> herokuwp:  hhvm depends on libboost-system1.54.0; however:
==> herokuwp:   Package libboost-system1.54.0 is not installed.
==> herokuwp:  hhvm depends on libboost-regex1.54.0; however:
==> herokuwp:   Package libboost-regex1.54.0 is not installed.
==> herokuwp:  hhvm depends on libc-client2007e; however:
==> herokuwp:   Package libc-client2007e is not installed.
==> herokuwp:  hhvm depends on libmcrypt4; however:
==> herokuwp:   Package libmcrypt4 is not installed.
==> herokuwp:  hhvm depends on libmemcached10; however:
==> herokuwp:   Package libmemcached10 is not installed.
==> herokuwp:  hhvm depends on libonig2; however:
==> herokuwp:   Package libonig2 is not installed.
==> herokuwp:  hhvm depends on libtbb2; however:
==> herokuwp:   Package libtbb2 is not installed.
==> herokuwp:  hhvm depends on libjemalloc1 (>= 3.0.0); however:
==> herokuwp:   Packa
==> herokuwp: dpkg: error processing package hhvm (--install):
==> herokuwp:  dependency problems - leaving unconfigured
==> herokuwp: Processing triggers for ureadahead (0.100.0-16) ...
==> herokuwp: Errors were encountered while processing:
==> herokuwp:  hhvm

Then...
==> herokuwp: Cannot create cache directory /root/.composer/cache/repo/https---wpackagist.org/, or directory is not writable. Proceeding without cache
==> herokuwp: Cannot create cache directory /root/.composer/cache/repo/https---wp-cli.org-package-index/, or directory is not writable. Proceeding without cache
==> herokuwp: Cannot create cache directory /root/.composer/cache/repo/https---packagist.org/, or directory is not writable. Proceeding without cache
==> herokuwp: Cannot create cache directory /root/.composer/cache/files/, or directory is not writable. Proceeding without cache
==> herokuwp: Loading composer repositories with package information
==> herokuwp: Installing dependencies (including require-dev) from lock file
==> herokuwp: Your requirements could not be resolved to an installable set of packages.
==> herokuwp:
==> herokuwp:   Problem 1
==> herokuwp:     - This package requires php ~7.0 but your HHVM version does not satisfy that requirement.

I have not gotten a chance to update the vagrant install for PHP7 yet after changing this repo over from using Nginx/HHVM.

Hi xyu, great work putting this project together. I'm seeing the same problem on "vagrant up". Do you have a workaround? Thanks!

Unfortunately not, I'm working off and on in getting a new vagrant config setup but been busy with other things. However because this is Heroku you can actually just spin up another app and push to that development / staging app instead of your production app.
It's not as great as vagrant because you need to wait for a slug to rebuild but it's a more accurate testing environment.

Great point, I'll give the Heroku pipeline workflow a go.

Hi there!,
I'm a newbie to linux, vagrant.;however, it does seem that an easier way to setup the vm is to use vagrant with puphet. Let me know what you guys think! Thank you!

I fixed vagrant up problem for hhvm dependency for my setup by adding the --ignore-platform-reqs flag to install.sh. It should be used by composer update anyway.
Another bug after successful provisioning is that nginx config is not correctly referenced within herokuwp.conf. I will try to prepare a push request. Missing is https configuration for vagrant. Besides that vagrant wordpress is running fine atm.

I'm going to mark this thread as closed, with the changes that @quasivivo made in #80 based on comments from @tomas-st and a bunch of changes I made in https://github.com/xyu/heroku-wp/commit/af3cd22f3eb1059f0a7140551722f5d88843b1d6 the Vagrant local dev env should be working again. This time with Nginx and PHP7 which is what this repo is deploying to Heroku by default now.


Modified layout at 100% view

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


Blink Extraction Hangs

Hello,
I have done an editable install on Windows 10.
I was able to get the EAR scores output to a csv file in the facial extraction tab. Moving to the Blinking Extaction tab I was able to import the EAR scores, but then clicking Extract Blinks resulted in the processing freezing at 40%. I tried a few times and it consistently froze at 40%.
I'm not sure if I'm failing to configure the settings in the appropriate way or if the data I'm providing is sufficient (about 10 seconds of me blinking on camera). Any guidance is appreciated.
Thanks!
Mac

Hi @mprib,
I investigated the issues and pushed some fixes into the development branch of the tool. If you could switch to the branch, checkout the latest commit, and rerun the extraction, it should work now (or at least give a more helpful error message ^^)
Additionally, I updated the interface to include a button to inform the user about recommended settings for 30FPS and 240FPS.
Furthermore, each setting now has its help button to access a more detailed description and the recommended setting again (access by clicking or hovering).
Lastly, I added a 30 FPS EAR score file in the examples repo folder.
More video files for testing are available in the tests folder for automatic testing.
In the attached screenshot, you can see the interface changes.

If there is any issue please let new know :) You can also send your EAR score file, and I can investigate further issues.

Happy to report that I was able to process some video I recorded myself and get successful output on the development branch. The specific domain knowledge is well outside my wheelhouse, but I'm willing to  believe the results given my attempts at asymmetrical and partial blinking:


fbe up

@rultor release, tag is 0.0.16

@rultor release, tag is 0.0.16

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.16

@yegor256 Done! FYI, the full log is here (took me 7min)


Add remote address into debug log for TLS error

When we migrate the current traffic from others to envoy, we always found that TLS errors because of the TLS version/cipher mismatch. But current log did not tell us the client IP. This PR can help find the client IPs which have issues so that we can change the TLS configuration for the clients.
Commit Message:
Additional Description:
Risk Level: low
Testing:
Docs Changes: No
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

/retest


Bump Blazored.LocalStorage from 4.1.5 to 4.2.0

Bumps Blazored.LocalStorage from 4.1.5 to 4.2.0.

Release notes
Commits

updated-dependencies:

dependency-name: Blazored.LocalStorage
dependency-type: direct:production
update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

commit


Rename tool to f

Rational:

The new name will help the tool get better adoption
The new name can be officially short for "fix", while we old timers all know what it really stands for :)
f is a one letter name that is easy and fast to type, and about impossible to get wrong

As explained in the README, you can use whatever you want as the alias:
eval "$(thefuck --alias)"
# You can use whatever you want as an alias, like for Mondays:
eval "$(thefuck --alias FUCK)"

Or, in your case :smile::
eval "$(thefuck --alias f)"

WHY do you want to change the name of the whole project when you can change it to suit your own needs??? The name is part of its appeal!  For shame.

When you can't actually say "fuck" and are saying "the f word" instead, perhaps he has a point?

We're not playing "marketing department" here. This software is open source. We don't have a target audience nor do we have any need to push its use in more serious corporate environments, or to kids learning how to sysadmin.
I must admit that for me, most of the appeal of this software is in its name. A more polite but much much less cathartic "fix" instead of "FUUUUUUCK" wouldn't just be as stupidly funny.
You don't like it? Fork it, can call it "fix". I stand by "fuck"

I think current name is ok =)
Also f isn't a good name for the project, it isn't googleable.

You don't like it? Fork it, can call it "fix".

 I said it that way for yours and @kim0 's benefit, but after that smart-ass remark I don't think I will any more.
Thank you @icovada ! I think both the package and name are brill! :+1:

As a non-native English speaker, I find “fuck” is such a common English word that it's not a problem to use it in such circumstances. The name is funny, easy to remember, easy to type, not as likely to be typed by a cat sleeping on your keyboard as f would and it expresses your feeling at the moment you'd use it. It's a good name.
And come on, why would you care being polite to your terminal?

Actually, no, you can't. I'll let you search for it as this is not the place to discuss about it. Also the Internet is not the U.S., there are some other countries in the world that can access it.

O rly? That's why three other people in this thread used it as well? No make that four. One has it in their code. Don't like it? Don't use it or alias it.

@mcarton From your own search:
"Nevertheless, the court’s free speech jurisprudence does not allow government-sanctioned punishment of speech solely because the message may be offensive. Rather, it allows regulation of speech only if there are objective indications of harm, such as threats, fraud or violence. The court protects offensive speech because speech on matters of public concern is valuable even when it is delivered in an offensive manner and because punishing offensive speech can lead to censorship of unpopular views. In doing so, the court has implicitly recognized the inherent tensions created by our psychological responses to offensive speech and the importance we place on the free exchange of ideas."
http://www.apa.org/monitor/2011/01/jn.aspx

I think the project name is OK - it describes the situation when the command applies (utter astonishment).  Even the command name thefuck is OK!

The situation is, that I made a mistake and I am asking for easy help!
I would prefer saying "please, fix it for me".
I would prefer if the default, documented alias name would be the magic word please.
Please, reconsider this issue!

I would prefer if the default, documented alias name would be the magic word please.

There are the people that are okay with it. And then there are the people that will get offended, not want to use the software, and possibly start flame wars.

people get offended too much these days and there workaround or just don't use the tool

@ronanamsterdam - There's no need to bump a three year old, closed, ticket just to complain about how offended people are.

I think current name is ok =)
Also f isn't a good name for the project, it isn't googleable.

I mean, you're right, but try googling 'fuck', you aren't going to find it that way either...
(obviously 'theFuck' does turn up the expected result)

I think current name is ok =)
Also f isn't a good name for the project, it isn't googleable.


upload trivy result to github security

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
upload trivy result to github security
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer

coverage: 80.804% (+0.08%) from 80.724%
when pulling 42ddfe8bd96f3587ad14f99f873ac0427178b027 on dependabot/MartinForReal-patch-1
into 8543b4bb06c4cc62d14072f9c8c0030c9e57e446 on main.


⚠ Bofrost.at has degraded performance

In ead6e08, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1050 ms

Resolved: Bofrost.at performance has improved in 9b42680.


“new() missing 1 required positional argument: 'task'” in my python code on linux

Hello, I followed the instructions in your README file to run your code step by step, but I encountered a bug at the "python train_ce.py -c config/train_ce.yaml" step. The error message says "new() missing 1 required positional argument: 'task'".
This bug appears to be occurring at line 260 of common.py, specifically at the line "self.train_acc = torchmetrics.Accuracy()". Could you please help me understand what this error message means and how I can resolve it? Any assistance would be greatly appreciated. Thank you. :)

It seems like that torchmetrics updated the constructor of torchmetrics.Accuracy, and now require a task parameter.
The benchmarks in OpenSRH is a multi-class classification task. You need to add a task="multiclass" in the constructor torchmetrics.Accuracy. Note that this applies to torchmetrics.AveragePrecision as well.


Remove organization from superuser edit/index of users

Summary
You currently have to add an organization if you edit a user as a superuser.   We don't need the link to the organization on the user at all anymore -- it's handled through the user's roles.
Why fix?
Outdated.  This is not a high priority item, as it the function it is on is very rarely used.
Details
Note:  Although this is ranked beginner,  it does need some familiarity with the system.  Please don't take this as your first issue.
Now that we have roles, users are no longer tied to organizations directly.  The organization field can, therefore, be removed from the user entirely.
User in the superadmin interface is affected by this
Edit.
Remove the user-level organization from this view.
Index.
The organization column was good information to have for the organizations that have it -- can we list the organizations and partners that the user belongs to, through their roles, here instead?  Rename the column "Banks and Partners"
New:  Analagous changes to new are being handled with a different issue.
Sanity check.
We're pretty sure that's the only remaining place that User.organization is used.  However,  please do check.  (If we're wrong, existing tests should fail, we hope.)
Criteria for completion

[ ] functionality as described
[ ] tests added and/ or modified to support the new functionality
[ ] tests work!
[ ] Please include screenshots in your PR

I can take this one!

There is an abandoned PR for this one.


Added CSS for interactivity warning option

Quite ugly right now but this is just to show that the PR on nbsite for adding a floating interactivity warning works.

Oops wrong repo! Can we archive this one and point to https://github.com/pyviz-dev/sphinx_holoviz_theme instead?


May I ask how to migrate and backup (especially daily backup, this is very important)

Describe the solution you'd like
My current VPS has expired, and I plan to move my memos to another machine. How do I migrate, and what is the daily backup like? Is there a scheduled backup function? Can each memo be exported separately in markdown format?
Type of feature
Other
Additional context
No response

how to migrate

Copy and paste your database files to your new machine.


Merge multiple word documents?

I've been playing around with this package to see if it's possible to combine multiple word documents with a simple script. It seems like it should be possible given the objects, but I can't find an intuitive way to do this.
Basically, I have a folder with .docx files like 01.docx, 02.docx, 03.docx etc. I'd just like to join these together in a single document as if I had "copy/pasted" each one in succession.
I've tried appending the paragraphs attribute of one to another, but this doesn't seem to work, and add_paragraph only accepts a string, not a Paragraph object. Any idea on the best way to accomplish this?
ps: if this works then I am eternally grateful...this is a pretty nice package for people who are writing a dissertation, but whos advisor won't let them use Latex ;-)

I sort-of got this working by looping through paragraph objects and running add_paragraph(p.text, p.style) over and over. This got the text (more or less) there, but all of the images were removed and table formatting was also stripped. I'm starting to sense this is asking more of this package than it was designed for...is that true ;-)

Well, maybe not more than it was designed for, but more than it's built for so far :)
You could probably get as far as getting the tables copied over with just what's available, but the images would take a bit of digging into the internals.
If you're keen to keep going, this will give you an idea how to get the tables out in the order they appear:
http://stackoverflow.com/questions/42093013/processing-objects-in-order-in-docx
Basically I'd take the same approach you mentioned. Go through the block items (paragraphs + tables) start to finish, and add a facsimile to the target document. There are other possible approaches, but I think keeping it straightforward is a good place to start. Then it's just a case of decomposing each object "copy" far enough to suit the API and your purposes.

hmmm, methinks this will be more trouble than it's worth for this one particular use-case :) I'm going to pass on this for now but I'll reopen the issue if I try doing this in the future so that I can post whatever solution I come up with. Thanks for the help!

I have a workaround solution, the following is an example to merge doc1 and doc2:
doc1 = docx.Document('1.docx') doc2 = docx.Document('2.docx') doc_new = docx.Document() for element in doc1.element.body:     doc_new .element.body.append(element) for element in doc2.element.body:     doc_new .element.body.append(element) doc_new.save('new.docx')

@xlhu19
It works actually,
but header and footer has gone in the doc1 or doc2,
I would  recommend
doc1 = docx.Document('1.docx')
doc2 = docx.Document('2.docx')
for element in doc2.element.body:
    doc1 .element.body.append(element)
doc1.save('new.docx')

that would be useful In case doc1 or doc2 has the same template

Those approaches won't copy the images from one document to the other. Any fix for that?

Those approaches won't copy the images from one document to the other. Any fix for that?

When I use this method I got broken word file. You the same?

I created a fork of python-docx that provides easy access to images when
r eading a DOCx file.  It might help you figure out what you need.
https://github.com/DKWoods/python-docx

@Jesse-Back Your method works great for combining documents with the same headers/footer.
Does anyone know of a work around for documents with different headers/footers?


flash attention

Hello and thank you for your amazing work!
I am wondering that will enabling flashattention reduce the model performance or not?
Thanks for your reply!

Hi, typically not. During our research, we initially did not support flash attention and enable RPE in our model. A significant performance improvement occurs when we enlarge the patch size from 16 to 128. Then we ablated disabling RPE and found that it has an ignorable influence on the final performance (except S3DIS). Then we support FlashAttention (which needs to disable RPE) and further enlarge the patch size to 1024 or higher, which is impossible when disabling FlashAttention, and leading to a better performance.
So in conclusion, enabling flash attention will make a larger patch size available which is typically good for the model performance (except a few cases need RPE, yet the gap, in my opinion, is not so important compared with the efficiency gain)

Thanks for giving so many details, It helps me a lot!

May I ask a question? How to disable the flashattention? My server doesn`t have a new version GPU

May I ask a question? How to disable the flashattention? My server doesn`t have a new version GPU

Never Mind, I found it in the configure file