[ADD] Bahasa Indonesia translation.

add Bahasa Indonesia translation.
thanks,
-andria

@andria009 Thank you very much for your translation! It is activated, please check it here: id.wttr.in
(I will make an announcement on twitter soon)
I noted that we have many queries from Indonesia in the last time, the service became quite popular there, so I hope that your translation will be really helpful


It There a way to check voice without specifying commands?

Hello!
I'm using with success the voice commands but I wanted to use speech recognition without having to specify commands.
Is it possible to easily modify HoloJS for that?
Thanks!

Like an unrestricted speech recognizer?

Yes, without having to set a dictionary (limited array of words)

That should work, with the speech recognizer in dictation mode. I'll add it to develop/next as an option to a
new SpeechRecognizer API.

This is fixed in develop/next. Use it like this:
speechRecognizer = new SpeechRecognizer();
speechRecognizer.onresult = function (result) {
    console.log(result.text);
}
speechRecognizer.start();

See the https://github.com/Microsoft/HoloJS/wiki/SpeechRecognizer for more details.


Schematic Viewer should allow moving components like PCB Viewer

[ ] Add new edit event for moving a schematic component to manual-edit-events https://github.com/tscircuit/manual-edit-events
[ ] Support layout function when schematic components are moved https://github.com/tscircuit/layout
[ ] Send edit event to CLI server inside the tscircuit cli frontend
[ ] Update the builder to support the new layout engine
[ ] Capture the edit event and edit the manual-edits file inside the CLI edit event watcher

I might do this after schematic-viewer is fixed


Older docker images

Why were the older docker images removed? They worked perfectly fine.

Would really appreciate it if the old docker images like 0.6.7 are restored since they worked for me.

The same here :( can't rebuild old version
will try to keep old images now.
Thanks.


PoshCode in Invoke-PSInject too long

Empire Version
1.6
Target
Windows7 64-bit
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
When data/module_source/management/Invoke-PSInject.ps1 is generated, sometimes the PoshCode argument exceeds 1200 characters and injection fails (line 44):
[ValidateLength(1,1200)]
If this is changed to something like 2000 characters, injection is successful.

This has been fixed in the 2.0_beta branch and now 1.6.


Not obvious CPU card in database diagnostics

DB diagnostics CPU card shows max cpu usage among user and system pools. It's not obvious, metric "used cores / total db cores" is expected here
https://github.com/ydb-platform/ydb-embedded-ui/blob/main/src/store/reducers/tenants/utils.ts#L46

I'm going to run several experiments causing problems this widget is supposed to highlight.
Let's discuss the results and decided then

Proposal after experiments and discussion with Oleg

Remove number of cores indication
Leave percentage utilisation for max of (user, system, ic) pools. Let's don't include utilisation of batch pool, since we can't remember a case when it helps
Add detailed CPU consumption infos when CPU toggle is pressed (below the charts). Detailed infos must include:

utilisation indicator (bar)
percentage
available cores
used cores

this page must have a link to the docs with explanation of thread pools and actor system configs.

https://ydb.tech/docs/en/deploy/configuration/config#actor-system

How it should look like? We have these pools indicators on Node page. Should it be something similar, but with additional progress bar with cores used?

@antonkovalenko @adameat

Another version:

So, we did an UX-test with users from our chat and random people from a service that does such researches.
Several options of how to display diagnostics about consumption were tested.
After internal discussion we have chosen the one with horizontal bars

Let's redo all circles to horizontal bars, if users like them bars.

@antonkovalenko
Version with numbers on Progress bars. We don't have current and limit values for pools, so there are just percents.
I used our Progress bars, that are used everywhere in the UI. Also I used the same icons, that we have to HC.
How is it?

@antonkovalenko
Version with numbers on Progress bars. We don't have current and limit values for pools, so there are just percents.

Okay.
But it sounds weird
@adameat don't we really have core used / core limit in absolute numbers?

I used our Progress bars, that are used everywhere in the UI. Also I used the same icons, that we have to HC.
How is it?

Nice!

I don't like icons. The ones used at mockups were way better. With exclamation sign and triangles. Can we use them?
Bars without captions look orphaned. Let's discuss tomorrow how we will display different storage types and what lable is appropriate for memory

@antonkovalenko
Version with numbers on Progress bars. We don't have current and limit values for pools, so there are just percents.

Okay. But it sounds weird @adameat don't we really have core used / core limit in absolute numbers?

of course we have.


PR: Fix updating of plugins

Description

Fixes https://github.com/napari/napari/issues/3251
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References

How has this been tested?

[x] example: the test suite for my feature covers cases x, y, and z
[x] example: all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas

@psobolewskiPhD could you give it a spin and check if it works as expected :) ?

Thanks!

Thanks to @jni tip, i used:
gh pr checkout 3288
to get it locally!
I see skimage-regionprops being offered to update.
62 Available plugins. 4 installed
I can see napari-plot-profile just fine.
NB: In 4.10 I see 60 available, 8 installed (if I'm counting right)

@psobolewskiPhD thanks for checking. The way napari displayed installed plugins in 4.10 is different from 4.11
Now we display packages on top and bottom.
The only way to compare that amounts match is to make sure no plugins are installed. Then the available number of plugins should match

Just installed 4.11rc3.
I am offered updates to plugins (yay!), but still not seeing the napari-plot-profile plugin:

Showing 54 available.
(BTW I love the [filter....] at the top!)

Thanks for testing @psobolewskiPhD

@tlambert03 any thoughts on why that particular package is not appearing napari-plot-profile ?

I see it on mine, not sure if there is platform specific stuff happening (i'm on mac)

I think we can release without more changes and then monitor if issue persists.

I also see it now:

Note that Available shows 62 and before was 54.
Not sure what's changed: same conda, same way to launch, same IP.


Publishing app on f-droid

Hey George,
F-droid is known to have pretty strict inclusion policy, and Dir satisfies it perfectly. Having app in f-droid is a proof of app having noble intents. I think seeing Dir in f-droid would be awesome, right?
Links that might help:
Docs has all links listed, still I'm listing some imp ones.

Inclusion Policy
Inclusion How-To
Submitting to F-Droid: Quick Start Guide
Build Metadata Reference

My main issue is that we'd lose control over apk signing, and I'm not sure I trust F-Droid enough - especially not seeing much of a point in being exposed.
That being said, I'll leave this issue open in case someone's interested in setting it up and/or knows more around what it would involve.

I think you can trust F-Droid since they build FLOSS apps for years and for free!
They just compile apps from repositories.
They are all volunteers and it's a small team. Everything is not perfect (even with GAFAM lol) but we can definitively trust them.
As said by email I submitted Dir: https://gitlab.com/fdroid/rfp/issues/394
Feel free to post questions or cancel my submission if you want.
F-Droid is widely used by Android users who care about their privacy and security. It's also a useful platform to download app udpates or discover new FLOSS apps.

Thanks for providing more details and going through the submission process! Let's not cancel, afaict this won't do any harm :)

Seems like the work for the rfp is done, so I'm closing this ticket. fwiw I still can't see it inside the fdroid app but I trust their processes

I've seen it listed under latest, but there isn't an icon for it.

Wow, it's up now indeed. For some reason the version is reported as 1.5.1,
does it just build on every master push? :|
On Tue, 26 Dec 2017, 8:35 pm Alex Disibio<EMAIL_ADDRESS>wrote:

I've seen it listed under latest, but there isn't an icon for it.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/veniosg/Dir/issues/50#issuecomment-353999097, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABmcZIFJH0VwCBnZuu5Kdx9k5dKWtPIcks5tETxYgaJpZM4OyLwv
.


Add more llvm intrinsics

This adds more llvm intrinsics, in the spirit of those already there, and fixed #17 for me.
I'm not familiar with llvm intrinsics, and this is surely not complete, but it helps. Comments welcome if there is a better solution.

Thanks for the PR. I have merged it as par of PR #19.


Update beautifulsoup4 version

Conda requirements is trying to install beautifulsoup4 on version 4.4.1 and that is giving out an error while running the setup:

right now an appropriate version would be 4.5.3

thanks to @sergiomario this one can be closed!


Laser/lamp state available on NZ series projectors?

On the NX series, the lamp state of off/reserved/on/cooling was super helpful for automations when starting up/shutting down, and knowing when the projector was ready to receive inputs (lamp was on).
Is a similar thing available with the lasers?

Yes it is part of the PowerStates class in this library. Its not part of the laser state for NZ models. It can be accessed with the _get_power_state function.
What are you trying to do? When the NZ reports on, it should be ready to accept commands. In HA, I have a wait template to wait until the state of the NZ is 'on'
{{ is_state('remote.nz7', 'on') }}

I had automations to do things like slowly dim lights when the projector is warming up, or bringing them back up as it cools. Honestly the warming up bit is most valuable to me.

I am.

Okay the NZ series only expose "cooling" but takes only a few seconds to actually cool. There is no warming state. It basically goes from off to on to off. I would suggest triggering lights based on a script which is activated by your remote.turn_on/off actions since there is no way to see if the PJ is warming and cooling might not be reliable.

Fair enough.  I have a challenge using the ha component, but I'll cover that in the right project. Thanks for the help!

Okay if you want help with the HA please feel free to open an issue there and I can try to help you

I had automations to do things like slowly dim lights when the projector is warming up, or bringing them back up as it cools. Honestly the warming up bit is most valuable to me.

 :)


Option to show only the failing tests

Does it make sense to have an option to show only the failing tests? As you can see, sometimes is hard to navigate between the tests

The broader problem is that if you have negations in the tree, some passing tests may responsible for the definition to fail.

I see, so it would have to handle these special cases with negations as well. But it should be still doable.


Css is not loading properly in build

🐛 Bug Report
I want to deploy the build folder, but the build folder css is all messed up. The pages has no styling. When I'm running in development mode the pages are loading fine, but in build mode, pages are not loading properly. Please see attached photos
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Clone the repo
git clone https://github.com/react-native-bootstrap/react-native-bootstrap
cd into website folder
cd website
Start development server and see website is working fine
yarn start
Not build the static website & open index.html in build folder
yarn build

Expected behavior
The website should have looked like this

Running index.html file from build folder should have worked fine, so that I can deploy it on github pages
Actual Behavior
Website looks like this after deploying build folder in gh-pages

Your Environment

Docusaurus version used: 2.0.0-alpha.56
Firefox 76.0.1 (64-bit)
Node.js v10.15.3
Operating system and version (desktop or mobile): Ubuntu 18.04

Reproducible Demo
The entire code is present here https://github.com/react-native-bootstrap/react-native-bootstrap/tree/master/website

Make sure the baseUrl in docusaurus.config.js is not empty if your website
has one.
On Mon, Jun 1, 2020, 2:24 AM Sanjeev yadav<EMAIL_ADDRESS>wrote:

🐛 Bug Report
I want to deploy the build folder, but the build folder css is all messed
up. The pages has no styling. When I'm running in development mode the
pages are loading fine, but in build mode, pages are not loading
properly. Please see attached photos
Have you read the Contributing Guidelines on issues
https://github.com/facebook/docusaurus/blob/master/CONTRIBUTING.md#reporting-new-issues
?
Yes
To Reproduce

Clone the repo
git clone
https://github.com/react-native-bootstrap/react-native-bootstrap
cd into website folder
cd website
Start development server and see website is working fine
yarn start
Not build the static website & open index.html in build folder
yarn build

Expected behavior
The website should have looked like this
[image: Screenshot_2020-05-31 React Native Bootstrap React Native
Bootstrap(1)]
https://user-images.githubusercontent.com/13250741/83359643-2e47c280-a399-11ea-90eb-b7bda24b21df.png
Running index.html file from build folder should have worked fine, so
that I can deploy it on github pages
Actual Behavior
Website looks like this after deploying build folder in gh-pages
[image: Screenshot_2020-05-31 React Native Bootstrap React Native
Bootstrap]
https://user-images.githubusercontent.com/13250741/83359639-212ad380-a399-11ea-8a53-3585d355e984.png
Your Environment

Docusaurus version used: 2.0.0-alpha.56
Firefox 76.0.1 (64-bit)
Node.js v10.15.3
Operating system and version (desktop or mobile): Ubuntu 18.04

Reproducible Demo
The entire code is present here
https://github.com/react-native-bootstrap/react-native-bootstrap/tree/master/website
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/2853, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKBCHOUMOFDGXGNFXES64LRUKOEFANCNFSM4NPIQJOQ
.

Hi @yangshun I don't have a website, I just want to deploy the website on github pages at url react-native-boostrap.io, could you help me with configuration

You need a CNAME file as well in static with the contents react-native-boostrap.io

@yangshun I ran yarn deploy it created a build folder at my local computer, I'm trying to run index.html file from that local build folder, that is also not rendering properly, you can see yourself, i have provided the repo.
Also I tried, creating a CNAME file in static folder, and redeploying it, still same effect

Are you using a local webserver to run the files? You can start one using Python. If you just double click and open the files it would not work.

No I just opened the index.html file on browser
Ok I understand it won't work without local server, but why it is not working on github pages, I have created a CNAME file in static folder whose content is react-native-bootstrap.io
and this is my docusaurus.config.js
module.exports = {
  title: 'React Native Bootstrap',
  tagline: 'Bootstrap components built for React Native',
  url: 'https://react-native-bootstrap.github.io',
  baseUrl: '/',
  favicon: 'img/rnb.png',
  organizationName: 'react-native-bootstrap', // Usually your GitHub org/user name.
  projectName: 'react-native-bootstrap', // Usually your repo name.
  themeConfig: { ...}
};

Did you enable GitHub pages from your repo settings?

Just FYI, I couldn't touch the CNAME so I resolved this by setting --out-dir in docusaurus build. The command was
yarn build --out-dir build/<subdirectory>

You need to use CNAME file only if you have custom domain linked to your website. If there is no such thing, then configuring package.json file would work fine.

Hi @sanjeevyadavIT ,
I have the same issue as you,
Have you got any solution to it?
Also Just want to know, After running yarn build can we run a static website through a browser without running any server?

Hi @sanjeevyadavIT ,
I have the same issue as you,
Have you got any solution to it?
Also Just want to know, After running yarn build can we run a static website through a browser without running any server?

Hello @iamadityac
yes, it is possible to run a static website through a browser.
Also mention your problem clearly so we can help u

I am also facing the same issue. When I use npm start or box docusurus start the localhost:3000 shows the css rendering. However, when I do nom run build followed by nom run serve the css is not rendering. Could you please help with this?

It is impossible to help without seeing your live site with the exact URL it's being served on.
As stated above it is likely a baseUrl configuration issue, but can be many different things in practice

I have the same problem


Suited players shouldn't drown if your latex is an aquatic type

Would make it more beneficial to transporting people and such.

and also maybe make it a choice whether the suit should absorb or not


Implement additional contribution to acceptance probability

Attempting to address #77.  NCMC switching now returns a potential energy that can be used in computing this additional contribution.
Currently, this contribution is essentially uniformly unfavorable, leading to universal rejection.  This might be a real problem, or might be a dumb mistake.
Very experimental.

On further reflection, I think this contribution is correct, but I don't think it should be biasing the simulation toward rejection quite as much as it seems to.
The overall contribution comes from
P(old | new) P(new)
--------------------
P(new | old) P(old)

If we assume there is only one particle being deleted and another being inserted, we have
P(r_old, theta_old, phi_old | x_core) J(r_old, theta_old, phi_old) exp[-u_core(x_core)] exp[-u_new(r_new, theta_new, phi_new | x_core)]
---------------------------------------------------------------------------------------------------------------------------------------
P(r_new, theta_new, phi_new | x_core) J(r_new, theta_new, phi_new) exp[-u_core(x_core)] exp[-u_old(r_old, theta_old, phi_old | x_core)]

The exp[-u_core(x_core)] contributions obviously cancel.
The contributions involving old atoms are
P(r_old, theta_old, phi_old | x_core)
-----------------------------------------------    J(r_old, theta_old, phi_old)
exp[-u_old(r_old, theta_old, phi_old | x_core)]

Now we can see why we use the valence energy of these atoms to draw the positions.  This should be almost exactly
exp[-u_old(r_old, theta_old, phi_old | x_core)] / Z_old
-------------------------------------------------------    J(r_old, theta_old, phi_old)
exp[-u_old(r_old, theta_old, phi_old | x_core)]

where Z_old is the normalizing constant for that old atom, which should be approximately proportional to the number of atoms being added or deleted for larger transformations.  This simplifies to
J(r_old, theta_old, phi_old)
---------------------
Z_old

Putting it all together, we should end up with this contribution being something like
J(r_old, theta_old, phi_old)   Z_new
------------------------------- * ------
J(r_new, theta_new, phi_new)   Z_old

The left term should be of order unity, and the right term has something to do with the net change in the number of atoms.
We should be able to compute this factor in the geometry engine and see how close the geometry_logp + switch_logp comes to this.  They should be of the same order of magnitude and sign.  (switch_logP is given by -(u_new - u_old).)
If not, there might be a bug either in NCMC---where the nonbonded interactions aren't being correctly switched off for the energy evaluations---or in the geometry engine where either the normalizing constants Z aren't correctly computed or an insufficient number of valence terms are being accounted for in drawing the new atom positions.

Looking through geometry.py, one issue might be that the normalized torsion probability is actually a probability mass function and not a probability density function on the space of [0,2*pi), so when we compute
P(r_old, theta_old, phi_old | x_core) J(r_old, theta_old, phi_old)
------------------------------------------------------------------
P(r_new, theta_new, phi_new | x_core) J(r_new, theta_new, phi_new)

the left-most ratio ends up depending on n_divisions if the net number of atoms in the transformation is changing.
I see now why you wanted to focus on validating/testing the geometry engine separately---there are a lot of subtle details in there that we will need to get right!

Thought experiment: If we had a set of linear alkanes (methane, ethane, propane, n-butane) where there were only valence forcefield terms (bond, angle, torsion), what do we expect the sampler to do?  Should it sample each one of these equally, or should it spend most of its time in the longest or shortest chain?
I'm not quite sure if it should naturally equally sample all of these molecules (the dimensionality is different for each one, but the partition functions are factorizable).
These per-atom issues may not actually matter if we use the extra recursion step with SAMS to do optimization---any intrinsic biases would get evened out by adjusting the weights in the unbound states.

Let's consider a simpler RJMC experiment: Sampling X = {x_1, x_2, ..., x_N} where the number of 1D components N is variable from 1 to N_max.  If our likelihood function is factorizable:
p(X) = \prod_{n=1}^N (2*pi)^{-1/2} \exp[-x_n^2 / 2]

then I believe we should see uniform sampling of N over 1..N_max because the likelihood is factorizable.
I think our simple alkane example above should be factorizable in this way too as long as there are no rings, where the probability density function of the new atom being added can capture all contributions from valence energy components.  In that case, we should have uniform sampling over chemical species if we get the RJMC right.
If we have nonbonded interactions or rings being created/destroyed, I think that's no longer the case and we need to apply some iteratively-determined weights to make sampling uniform over chemical species (if so desired).  But we can probably use this as a validation test (cc: #79).

I think this should be good to merge once tests pass.
I'll look into whether we can move the energy evaluation to the initial and final fully-interacting molecules as we discussed yesterday, but we can do that in a separate PR.

This is ready to merge unless you have incorporated the changes into the other PR already.

Can we merge this?

Hm, the test_sampler.py changes will cause a conflict now. I guess we can merge, if you're finished here.

Shoot.  How do you want to do this---I can wait until after #83 and then pull in your changes to my PR, or vice-versa....

Might as well just merge and then I'll deal with it.


Add default slot template

Users will be able to customize the content of the snackbar with that PR.

Thanks for the PR!
I was not super happy with the way you did the getDistance so I did it differently. See v3.1.0!

@Aymkdn I wasn't happy with it either, i knew that you're going to change it but i thought you'll do it on that pull request. I think that would be better, anyway thank you.


Cleaning up TestFilter tests.

There were some uncaught consequences due to PR #1739.  This PR improves TestFilters by removing some cruft.

LGTM. It might be a good idea to measure test coverage as we go through the refactoring. What do you think?

Code coverage is usually best in the same project with Unit tests.  We're pretty bad at unit tests.


app launch crashes on "[XYZModeTabBarController _viewWillAppearTimestamp]: unrecognized selector sent to instance"

Describe the bug
per the title, i cannot get my .app to boot successfully from detox, and it crashes with:
 -[XYZModeTabBarController _viewWillAppearTimestamp]: unrecognized selector sent to instance 0x7f85a180f600
launching my .app into the simulator from the CLI and xcode otherwise works great!
To Reproduce

[x] I have tested this issue on the latest Detox release and it still reproduces

i would love to produce a viable reproduction.  unfortunately i'm POC'ing detox on proprietary code, and my ios-fu is ~nil.  with that said, here is a snippet from detox -l trace test where the stack goes wild.  our app is listed as XYZ in the below logs.  i talked with some peers, and we're not sure where/who emits _viewWillAppearTimestamp--we are supposing it's originating from within whatever detox provides?
 -[XYZModeTabBarController _viewWillAppearTimestamp]: unrecognized selector sent to instance 0x7f85a180f600
(
	0   CoreFoundation                      0x00000001031086fb __exceptionPreprocess + 331
	1   libobjc.A.dylib                     0x00000001026acac5 objc_exception_throw + 48
	2   CoreFoundation                      0x0000000103126ab4 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132
	3   UIKitCore                           0x0000000119210c3d -[UIResponder doesNotRecognizeSelector:] + 287
	4   CoreFoundation                      0x000000010310d443 ___forwarding___ + 1443
	5   CoreFoundation                      0x000000010310f238 _CF_forwarding_prep_0 + 120
	6   UIKitCore                           0x00000001192aaef4 -[UIActivityViewController viewWillAppear:] + 36
	7   EarlGrey                            0x0000000138b512a5 -[UIViewController(GREYAdditions) greyswizzled_viewWillAppear:] + 1077
	8   UIKitCore                           0x0000000118b0f2d3 -[UITabBarController viewWillAppear:] + 250
	9   UIKitCore                           0x0000000118be8437 -[UIViewController _setViewAppearState:isAnimating:] + 687
	10  UIKitCore                           0x0000000118be8ba2 -[UIViewController __viewWillAppear:] + 131
	11  UIKitCore                           0x0000000118bea38d -[UIViewController viewWillMoveToWindow:] + 696
	12  EarlGrey                            0x0000000138b50c0b -[UIViewController(GREYAdditions) greyswizzled_viewWillMoveToWindow:] + 379
	13  UIKitCore                           0x000000011969b195 -[UIView(Hierarchy) _willMoveToWindow:withAncestorView:] + 656
	14  UIKitCore                           0x00000001196ac069 -[UIView(Internal) _addSubview:positioned:relativeTo:] + 456
	15  EarlGrey                            0x0000000138b8909b -[UIView(GREYAdditions) greyswizzled_addSubview:] + 107
	16  UIKitCore                           0x000000011921afbc -[UIWindow addRootViewControllerViewIfPossible] + 1027
	17  UIKitCore                           0x000000011921bbe3 -[UIWindow setRootViewController:] + 432
	18  EarlGrey                            0x0000000138ba9ec2 -[UIWindow(GREYAdditions) greyswizzled_setRootViewController:] + 290
	19  XYZCore                             0x0000000107c2e8a9 -[XYZAppDelegate application:didFinishLaunchingWithOptions:] + 1785
	20  XYZCore                             0x0000000107c84bb7 $s10CoreMainUI0aB8UIPluginC7startupyy9ELMaestro10SupervisorCF + 423
	21  XYZCore                             0x0000000107c856fc $s10CoreMainUI0aB8UIPluginC7startupyy9ELMaestro10SupervisorCFTo + 60
	22  XYZCore                             0x000000010adb5da4 $s9ELMaestro10SupervisorC5start33_2A95525A899514A38F1599EA35E5B94ELL6pluginyAA9Pluggable_p_tF + 372
	23  XYZCore                             0x000000010adb5720 $s9ELMaestro10SupervisorC7startupyyF + 240
	24  XYZ                                 0x0000000100998389 $s7XYZ11AppDelegateC11application_29didFinishLaunchingWithOptionsSbSo13UIApplicationC_SDySo0j6LaunchI3KeyaypGSgtF + 4345
	25  XYZ                                 0x000000010099a004 $s7XYZ11AppDelegateC11application_29didFinishLaunchingWithOptionsSbSo13UIApplicationC_SDySo0j6LaunchI3KeyaypGSgtFTo + 196
	26  Detox                               0x0000000100b47093 -[DetoxAppDelegateProxy application:didFinishLaunchingWithOptions:] + 152
	27  UIKitCore                           0x00000001191dc311 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 280
	28  UIKitCore                           0x00000001191ddcad -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 3932
	29  UIKitCore                           0x00000001191e30c6 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1617
	30  UIKitCore                           0x0000000118a286d6 __111-[__UICanvasLifecycleMonitor_Compatability _scheduleFirstCommitForScene:transition:firstActivation:completion:]_block_invoke + 904
	31  UIKitCore                           0x0000000118a30fce +[_UICanvas _enqueuePostSettingUpdateTransactionBlock:] + 153
	32  UIKitCore                           0x0000000118a282ec -[__UICanvasLifecycleMonitor_Compatability _scheduleFirstCommitForScene:transition:firstActivation:completion:] + 236
	33  UIKitCore                           0x0000000118a28c48 -[__UICanvasLifecycleMonitor_Compatability activateEventsOnly:withContext:completion:] + 1091
	34  UIKitCore                           0x0000000118a26fba __82-[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:]_block_invoke + 782
	35  UIKitCore                           0x0000000118a26c71 -[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:] + 433
	36  UIKitCore                           0x0000000118a2b9b6 __125-[_UICanvasLifecycleSettingsDiffAction performActionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:]_block_invoke + 576
	37  UIKitCore                           0x0000000118a2c610 _performActionsWithDelayForTransitionContext + 100
	38  UIKitCore                           0x0000000118a2b71d -[_UICanvasLifecycleSettingsDiffAction performActionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:] + 223
	39  UIKitCore                           0x0000000118a306d0 -[_UICanvas scene:didUpdateWithDiff:transitionContext:completion:] + 392
	40  UIKitCore                           0x00000001191e19a8 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 514
	41  UIKitCore                           0x0000000118d98dfa -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 361
	42  FrontBoardServices                  0x0000000114717125 -[FBSSceneImpl _didCreateWithTransitionContext:completion:] + 448
	43  FrontBoardServices                  0x0000000114720ed6 __56-[FBSWorkspace client:handleCreateScene:withCompletion:]_block_invoke_2 + 283
	44  FrontBoardServices                  0x0000000114720700 __40-[FBSWorkspace _performDelegateCallOut:]_block_invoke + 53
	45  libdispatch.dylib                   0x000000010686ed02 _dispatch_client_callout + 8
	46  libdispatch.dylib                   0x0000000106871d41 _dispatch_block_invoke_direct + 295
	47  FrontBoardServices                  0x0000000114752146 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 30
	48  FrontBoardServices                  0x0000000114751dfe -[FBSSerialQueue _performNext] + 451
	49  FrontBoardServices                  0x0000000114752393 -[FBSSerialQueue _performNextFromRunLoopSource] + 42
	50  CoreFoundation                      0x000000010306fbe1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	51  CoreFoundation                      0x000000010306f463 __CFRunLoopDoSources0 + 243
	52  CoreFoundation                      0x0000000103069b1f __CFRunLoopRun + 1231
	53  CoreFoundation                      0x0000000103069302 CFRunLoopRunSpecific + 626
	54  GraphicsServices                    0x00000001148802fe GSEventRunModal + 65
	55  Detox                               0x0000000100b438d8 __detox_UIApplication_run + 365
	56  UIKitCore                           0x00000001191e4ba2 UIApplicationMain + 140
	57  XYZ                                 0x0000000100996c6e main + 174
	58  libdyld.dylib                       0x00000001068dc541 start + 1
)

Expected behavior

no crash with error [XYZModeTabBarController XYZModeTabBarController]: ....  we own XYZModeTabBarController, but it's generally had no concern of _viewWillAppearTimestamp

Screenshots

the simulator generally hasn't opened by this point.  i can open it and observe my app hung with the loading screen painted

Environment (please complete the following information):

Detox: 14.0.2
React Native: 0.59 (albeit, not relevant yet!)
Node: 10.12.0
Device: iphone x
Xcode: 10.2
iOS: 12.0
macOS: 10.14.5

Device and Verbose Detox Logs
Provide the device and "trace" Detox logs so we can understand what happened. You can obtain them by passing the loglevel param: detox test --loglevel trace
https://gist.github.com/cdaringe/784851ea0299b08625dfa9a06cfba2f6
iOS Framework Build Logs
If you are seeing a build problem (e.g. during npm install), provide the log found here: ~/Library/Detox/ios/{...}/detox_ios.log
...i'm not, but here it is anyway 😄 : https://gist.github.com/cdaringe/93477324283f5e8915f5d7646139da3f

Hmm
What is _viewWillAppearTimestamp?

exactly :). it's not from our source, that's for sure!  Google seems to suggest it's apple internal?

It looks like a method of UIActivityViewController, and that is somehow called from a tab bar.
Could be a bug in Earl Grey swizzling; could be a bug in your code that is triggering the swizzle issue; could be a combination of both. Unless you can provide a reproduction project (not your proprietary code), there is nothing I can do, as I've never seen this issue before. Ask your iOS guys to try and create a clean project where this issue reproduces.


mwc-select does not work properly inside a mwc-dialog

I'm submitting a:

[x] bug report
[ ] feature request

What OS are you using?
Kubuntu
What browser(s) is this bug affecting:
Current Chrome
Current behavior:
mwc-select does not work inside a mwc-dialog. It's menu displays inside the dialog's content pane and makes it grow / show scrollbars.
Expected behavior:
the menu should display above the dialog
Steps to reproduce:
Open a dialog with a select with lots of items in it.
Related code:
      <mwc-dialog id="dialog" title="Dialog">
        <form>
          <mwc-select>
            <mwc-list-item>01</mwc-list-item>
            <mwc-list-item>02</mwc-list-item>
            <mwc-list-item>03</mwc-list-item>
            <mwc-list-item>04</mwc-list-item>
            <mwc-list-item>05</mwc-list-item>
            <mwc-list-item>06</mwc-list-item>
            <mwc-list-item>07</mwc-list-item>
            <mwc-list-item>08</mwc-list-item>
            <mwc-list-item>09</mwc-list-item>
            <mwc-list-item>10</mwc-list-item>
            <mwc-list-item>11</mwc-list-item>
            <mwc-list-item>12</mwc-list-item>
            <mwc-list-item>13</mwc-list-item>
            <mwc-list-item>14</mwc-list-item>
            <mwc-list-item>15</mwc-list-item>
            <mwc-list-item>16</mwc-list-item>
            <mwc-list-item>17</mwc-list-item>
            <mwc-list-item>18</mwc-list-item>
            <mwc-list-item>19</mwc-list-item>
          </mwc-select>
        </form>
        <mwc-button slot="primaryAction" @click=${this._save}>Speichern</mwc-button>
      </mwc-dialog>

Other information:

@aomarks I'm interested in fixing this one!
for what I could see, the dialog has overflow: auto in two places, this also happens when i try to put a select inside of a mwc-top-app-bar-fixed for the moment i got around it, but what would be your aproach, change the dropdown/menu behaviour or remove the overflows from the dialog and top bar ?

Same problem with mwc-menu in a dialog. I think mwc-menu-surface might need to be absolute-positioned in a dialog by default.

I ran into this as well. Anyone have a temporary hack to make it work in the mean time?

moved up in priority. Actively investigating solutions now. Thanks for the input and activity on this issue

Update: this is still being worked on both upstream in MDC and in this repo. Unfortunately no PRs to track for now. This issue is still a good place to track

We can use an <mwc-menu fixed> inside an <mwc-dialog> without encountering this issue, the menu renders correctly above the dialog that triggered it.
Seeing as <mwc-select> uses a Menu internally, could you maybe expose the fixed property through the Select API as a solution?

Unfortunately using fixed casues another host of behavioral problems. We are yet still working on a fix for this which is to implement an element hoisting system. It's just unfortunately stuck behind some upstream internal work

Thanks for the update, while waiting for your internal work to complete we'll work around the issue by subclassing Select as you suggest and using natural menu width together with fixed.

@e111077 thanks for the updates. Am I understanding you correctly that in the canary workaround, a select inside a dialog opened on top of a document that has been scrolled will open its menu off-screen, while the scrim prevents the user from then scrolling up far enough to see it?

Hello, this should not be happening. In the workaround where you set fixedMenuPosition on the mwc-select, it should appear on the screen correctly when interacted with. If the Dom is scrolled or the window resized whilst the select's menu is open, then the menu will remain in its current position.
If the menu is closed, and the select opens it again, the menu should be correctly positioned again.
This is a big difference between fixed and absolute positioning.
The behavior you're describing seems to describe an absolute positioned menu

Periodic update that we haven't forgotten about this issue and still expect to have a solution down the line for this before 1.0.0

Is there an update on this please?

Internally at Google I have modified select, menu, and menu surface to make it easy to subclass and replace the menu surface with a native  element which has the power to render above everything.
I'll work on trying to externalize those changes so that y'all can do the same until the native browser popup proposal is adopted

Due to the feature freeze on MWC, I've only been able to do a code refactor on mwc-select, mwc-menu, and mwc-menu-surface just released as MWC @0.27.0.
With this refactor it should make it easier to subclass and replace mwc-select's mwc-menu, and subsequent mwc-menu-surface to use a native <dialog> element with HTMLDialogElement.showModal() which taps into a browser's special ability to hoist dom to the top layer.
Here is an example implementation of this:
https://lit.dev/playground/#gist=f740bdff9ea4e62a64fae47bbdf5797e
Some caveats:

when the menu is open, the rest of the DOM is inert (on mac voiceover, it seems to announce the same as before)
when the menu is open, it will always scroll the menu
scrolling the page horizontally while the menu is open will behave similar to fixedMenuPosition behavior

Due to the Material Web team's focus on M3 and the feature freeze on MWC, I'm going to close this issue as "wontfix" in favor of the dialog workaround linked above. In the future, when the popup proposal is available in browsers, this subclass method should still work and allow you to migrate to that which is the true answer to menu-surface's issues.

Just wrap it with  and it will work:

item 1
item 2
item 3
item 4
item 5


whitespace between unqoatedName and colon(:) causes ParseException

The bug can be reproduced by "{x :1}" as following:
String js = "{x :1}"; //{123, 120, 32, 58, 49, 125}
org.hjson.JsonValue jv = org.hjson.JsonValue.readHjson(js);
ParseException: Found ' ' where a key name was expected (check your syntax or use quotes if the key name includes {}[],: or whitespace) at 1:2

jackson with ALLOW_UNQUOTED_FIELD_NAMES correctly parses "{x :1}" ({123, 120, 32, 58, 49, 125}).

This seems to be a duplicate of #1 issue.

#1 & this is now fixed and should be in maven soon.


Support Materialized Views

We've discussed supporting materialized views. I'd like to target this for 0.3.0 (with 0.2.0 being a pretty minimal iteration on the generators we ended up shipping in 0.1.0), but we need to carefully think out how this should work. I see a couple of options:

create_view accepts a materialized option which changes the view creation to CREATE MATERIALZED VIEW. This is really simple conceptually, but and immediate downside springs to mind: We currently have no way to remember how a view was created. This means every update and drop of the materialized view (drop must be done with DROP MATERIALIZED VIEW...) would have to also include the materialized option or we'd have to look into the schema on every update and drop and use the appropriate syntax from what we derive there.

We add create_materialzed_view, drop_materialized_view, and update_materialzed_view as schema statements. This is likely a bit more work but it has the advantage that the schema statements themselves mirror the SQL statements made to create them.

I think I still favor the first option, and think it's worth pursuing that API to at least see what the code ends up looking like. It might make more sense to refactor to the database-specific adapter pattern beforehand so we can get a better idea of how much the mostly-proprietary materialized view (oracle supports it too but has different trailing options) would effect the implementation there.

CLosing in favor of #51


Cannot add GMStepper to a TableViewCell nib

When I add this to a .xib file for a UITableViewCell, it does not show up. It does show up when I add it to a view in a storyboard. It is odd that the stepper will not show when added to a contentView in a UITableViewCell xib. The xib file uses size classes and auto layout, just like storyboards. I do not understand why this is not working...

:+1: same problem over here

@ArtworkAD let me know if you figure anything out and I'll do the same..

@ArtworkAD have you had any luck?

@mommyme nope


Docutils 0.18 issue fixes

Fixes #1322 (forked from and blocked by #1304)
We take the same approach as @pradyunsg did with Furo and add additional styling for the new <aside> structure. The new DOM elements are harder to structure as a grid to match the former structure.
I'm quite happy with the new setup, as it allows easier mobile friendly setup and longer labels without causing issues with wrapping in a grid setup.
How footnotes look with docutils 0.18 and new SASS code:

I'd put preference on retaining the same styling as docutils 0.17, there is a lot of vertical space in the list now. Also, this would be a 3rd style implementation to footnotes as html4/html5 also have differing styles to footnotes.

I can try to match the styling from html5writer <dl> but will still be a 3rd implementation :)
Whenever I look at the SASS code and the setup I get a feeling that it's all gonna get refactored/rewritten anyways, so I automatically try to keep the effort minimal. I agree that the final result can improve visually (the current <dl> version also has a few glimpses btw).

FWIW, if you find a way to avoid having the additional vertical whitespace, I'd like to borrow that back to Furo. I know those issues are closed, but I've not had the bandwidth to investigate the footnotes changes in detail -- whether they fixed my needs. It definitely doesn't help that docutils is maintained on SourceForge which... I find fugly. :)
I believe docutils hasn't figured out a way to stylise this in the manner we want either: https://docutils.sourceforge.io/docs/user/rst/demo.html#footnotes

FWIW, two things have happened:

Furo has better CSS for footnotes.
I better understand CSS grids. :)

This also made me have to look at CSS grids :smiling_face_with_tear: However, I did not find a way to create a grid, since the variable DOM structure with label, definition or label, backrefs, definition was too hard a nut to crack for me. @pradyunsg I was looking at https://github.com/pradyunsg/furo/pull/576 and guess you also went with float: left finally?
I tried to make the floats work like this...
before:

after:

I think that the result is acceptable. If there are several long paragraphs for a single footnote, the wrapping will not align. But I think that will belong to an absolute edge case :shrug:

Notice also that the : is gone.. I don't think we can bring it back in a nice way, and the former way wasn't perfect, neither.

I think there's a sudden bug in Circle CI as py39-sphinx17 is not supposed to be run. The defaults for sphinx-version clearly do not specify this, so I'm not sure why that tox environment is called.

This also made me have to look at CSS grids

CSS grid is the best way to solve this, and avoids making a third implementation of the citation list -- html5 writer current uses CSS grid and html4 doesn't need floating/grid as it's a table.

Notice also that the : is gone

There is a selector that we can use (:has()), but it's not supported on Firefox, so I'd say that's a no go. It's fine to drop these for now.

We could use the :before declaration on something like > p:first-of-type

This wouldn't quite work, it would be grouped with the p instead of the span.backrefs. CSS3 features are fine as long as they are implemented. first-of-type has good enough support it's usable otherwise.
https://caniuse.com/?search=first-of-type

On #1322 I mentioned I'd jump in to solve this and wanted an approach that uses CSS grid, similar to our current approach for the HTML5 writer in docutils < 0.18. I have a PR I'll put up with the fix but it could probably use some more back testing.

I'll close this PR and move the test fixes.
@agjohnson great work on the CSS grid!
Regarding :, I think that the footnotes lists look better without colons + the colon is unnecessary + the previous solution with : looked weird, especially with backrefs included.

Yeah the colon came from the html4 implementation, so was just added for parity. I agree that it looks unnecessary though, I'm also :+1: on dropping it

Superseded by #1383 and #1381

FWIW, if you find a way to avoid having the additional vertical whitespace, I'd like to borrow that back to Furo.

@pradyunsg sounds like you poked around with CSS grids a bit, but if you are still looking for an example:
https://github.com/readthedocs/sphinx_rtd_theme/blob/1d2351567c889941e20d79f9c7c766d924789b5c/src/sass/_theme_rst.sass#L327-L343
I would really have preferred docutils output more wrapping elements to make styling this easier. There's only so much you can do with the existing output structure, even with grids.


lyxal: Watch sanantoniospecial.com

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

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

Approved by Jeff Schaller in Charcoal HQ


TechDocs: Binary file is not showed up with awsS3 publisher

I am trying to using awsS3 as publishser, and found that binary file such png image cannot be showed up at frontend. I've done some debug and found out that if remove the toString() function in the following code, png image file is displayed normally.
https://github.com/backstage/backstage/blob/54faa6fa8d32da6568ff8cf073328352e7881b2a/packages/techdocs-common/src/stages/publish/awsS3.ts#L189

I tried your suggestion and it worked. :) PR is up at https://github.com/backstage/backstage/pull/3991
Thank you for reporting @jizg, this is a great contribution!

I tried your suggestion and it worked. :) PR is up at https://github.com/backstage/backstage/pull/3991
Thank you for reporting @jizg, this is a great contribution!


Cant talk in radio when other UI is open

Did you read the README?: Yes
Describe the bug
I'm having a problem where I cant talk when most UI stuff we have it open (For example like lockpicking or in a qb-menu)
Is there a way to enable the radio when you are in such menus
Expected behavior
I was expeting to be able to talk in the radio when the menu,.. is open
I have the latest script version
Server Info:

Server Version: latest
Client Build: latest
Game: FiveM

Not a bug, nor a pma-voice issue, if you want to still be able to use regular key binds when in a menu you have to use SetNuiFocusKeepInput


[Help wanted] Add search function for Media Library

Short description
The goal of this PR is to add  search funcionality for media library so users can look for directories and files that match key words.
So far keyword search of items is functioning, but the result is shown as Json string not properly displayed.
At the moment the chanes are applied only for admin media library but we can add the changes also to non-admin media library once everything is done.
I appreciate your help and advice!
What already done

Search box and button
Search suggestion by ajax call
Search for directories and media files that much the keyword

What not yet functioning

Display of searched items

Resolved issues

Fixes: #931

The goal of this PR is to add search funcionality for media library so users can look for directories and files that match key words.
So far keyword search of items is functioning, but the result is shown as Json string not properly displayed.

Looks great to me so far, could you please make a rebase to the current develop branch followed by a clean install?
That would make it easier for us to step into your branch and help you, because the current develop branch has a different project structure

Thanks for your support, @timoludwig, as far as I can see everything works flawless. Thanks also for the detailed comments!


Substitute 'Clone' for 'Fork' in the image; fix #59

Preview of suggestion:

Ah, description in the image needs editing perhaps: "Fork and clone one of your colleagues repository".

Is it easy for you to edit the description? Because I agree that it can read confusing now.

I will correct the figure. (fork, clone etc...)
On Mon, Jun 8, 2020 at 4:51 PM Radovan Bast<EMAIL_ADDRESS>wrote:

Is it easy for you to edit the description? Because I agree that it can
read confusing now.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/coderefinery/testing/pull/61#issuecomment-640678831,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDB3MYDW5G6HLEWGZJ6YA3RVT3HJANCNFSM4NSN7MBQ
.

.. made a  PR with update figure.
On Mon, Jun 8, 2020 at 5:39 PM Bjørn Lindi<EMAIL_ADDRESS>wrote:

I will correct the figure. (fork, clone etc...)
On Mon, Jun 8, 2020 at 4:51 PM Radovan Bast<EMAIL_ADDRESS>wrote:

Is it easy for you to edit the description? Because I agree that it can
read confusing now.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/coderefinery/testing/pull/61#issuecomment-640678831,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDB3MYDW5G6HLEWGZJ6YA3RVT3HJANCNFSM4NSN7MBQ
.

But where is the updated figure or the other pull request?

This is marked as draft. I am unsure whether something is left to do. Something I can do to unblock this?

What is the plan with this one? Should I pick it up from here?

I am closing this PR since it's conflicting and stalled and the repo has moved on. @juholehtonen are the sources somewhere? How did you change the text? Or was it changed in a bitmap way?


Request for new release

It'd be super helpful to be able to get a new release of bazelisk 😄
cc @fweikert @philwo whenever you get a chance 🙏

Done: https://github.com/bazelbuild/bazelisk/releases/tag/v1.11.0


Buffer copy without checking size of input (CWE-120)

Prerequisites

[x] Can you reproduce?
[x] Are you running the latest version of SoftEtherVPN?

SoftEther version:
Component: [Server, Client, Bridge, etc.]
Operating system: [Windows, Linux, BSD, macOS, etc.]
Architecture: [64 bit, 32 bit]
[In case it's a computer with known specs, such as the Raspberry Pi, you can specify it omitting the details.]
Processor: [Specify brand and model. Example: AMD Ryzen 7 1800x]
Description
Not a feature bug, source code bug.
Potential format string problem (CWE-134). Format string problems may lead to buffer overflow attacks.
LABEL: Bug
SEVERITY: Major
SOLUTION: Make format string constant.
Instances found in the GitHub repository:

[ ] src\vpnweb\vpnwebdlg.c:338
[ ] src\vpnweb\vpnwebdlg.c:318
[ ] src\vpnweb\vpnwebdlg.c:301
[ ] src\vpnweb\vpnwebdlg.c:272
[ ] src\vpnweb\vpnwebdlg.c:228
[ ] src\vpnweb\vpnwebdlg.c:201
[ ] src\vpnweb\vpnwebdlg.c:172
[ ] src\vpnweb\vpnwebdlg.c:101
[ ] src\vpnweb\vpnwebdlg.c:64
[ ] src\vpninstall\vpninstall.c:94

Does not check for buffer overflows (CWE-120).
LABEL: Bug
SEVERITY: Major
SOLUTION: Use sprintf_s, snprintf, or vsnprintf.
Similar vulnerability hotspots:

[ ] src\SeLow\SeLow.c:248
[ ] src\SeLow\SeLow.c:247
[ ] src\Neo6\NDIS6.c:627
[ ] src\Neo6\NDIS6.c:623
[ ] src\Neo6\NDIS6.c:601
[ ] src\Neo6\NDIS6.c:599
[ ] src\Neo6\NDIS6.c:325
[ ] src\Neo\NDIS5.c:540
[ ] src\Neo\NDIS5.c:538
[ ] src\Neo\NDIS5.c:222

Possible race condition (CWE-362). This accepts filename arguments; if an attacker can move those files, a race condition results. (CWE-362).
LABEL: Bug
SEVERITY: Major
SOLUTION: Use fchmod( ) instead.

[ ] src\Mayaqua\Unix.c:820

Thank you for documenting these. What is CWE?
Could you please create a separate issue per CWE id(?)?

CWE is Common Weakness Enumeration; An initiative to organize common vulnerability roots/practices/functions. For more info refer here

CWE™ is a community-developed list of software and hardware weakness types. It serves as a common language, a measuring stick for security tools, and as a baseline for weakness identification, mitigation, and prevention efforts.

Other issues created are #1397 and #1398.


Fix the multigate adapter fix for old and new checkpoint files

I think this fix https://github.com/Lightning-AI/lit-llama/pull/297#issuecomment-1555976464 made the new multigating in the Adapter compatible with old checkpoint file, but it then broke the new checkpoint files via this dicussion here: https://github.com/Lightning-AI/lit-llama/commit/67c1e95176928ca149ebfcb016269a401fd3ba0b#commitcomment-115733970.
This PR hopefully fixes it for both new and old checkpoint files. What do you think @awaelchli ?

Btw if you still have that old checkpoint, can you test it there before merging? I only have a "new" checkpoint 😅 (the fix definitely works with the new checkpoint)

Yes, already tested that as part of the review here. Still works 👍


[OTHER] db.json contains repeatative data

What would you like to share?
db.json file contains repeattive data, see from line 172 to line 332 (as of now).
Additional information
No response

Nice spot Rupali! Thank you SO much for this. I have managed to clear the duplicates, but take a look now and tell me if you can catch something I haven't. If not, will close this issue as solved.


Expose proxy setting from cli-search.js

Need a command-line switch, to set proxy for the search command (it gets passed as options in the initialize() call on the engine).

This was added, closing.


Remove organization switch cc grant

Purpose

Reverts https://github.com/wso2-extensions/identity-oauth2-grant-organization-switch/pull/30
Set user type as APPLICATION to tokens switch requests of client credentials grant.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7606549248

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7606549248
Status: failure


Detect spaces moved to another display using Mission Control

Bug report
This came up during the testing of #112.
Imagine the following scenario:

Displays A (spaces A1, A2), B (space B1)
Focus A2 and drag A1 to B using Mission Control

yabai now no longer recognises A1. If the displays had different sizes, windows moved with the display would not get resized at all. Opening new windows on A1 moves them to and tiles them on A2.

I have no idea how we can detect this. A bad solution would be to just invalidate spaces after exiting mission-control.

Keep a cache of space ids in order per display. When leaving Mission Control, check if any space id moved to another display. If any moved, act as if the space was moved by yabai -m space <sel> --display <sel>.
Note that only spaces that are not currently visible can be moved to another display using Mission Control.

Might as well just mark all views invalid then, as I think that is less (or equal) work for the system, yet currently a one-liner to implement.


Potential CWE-113 vulnerability in OdataToEntity.AspNetCore

So I've run a SAST scan with a certain tool against OdataToEntity source code and it uncovered the following issue: CWE-113 in OdataToEntity.AspNetCore MoveNext() method.
It probably originates in some foreach but I couldn't pinpoint the exact location. It can probably can also be fixed by a filter/middleware that would clean the inputs.
Thoughts?
Cheers,
Dmitry

I need more information, I can not find the MoveNext method.


Simplify API for users declaring their own halo mass completeness cut

As pointed out by @nickhand, there were several awkward aspects of how the halo completeness cuts were applied during HOD mock generation. This PR addresses this by allowing the user to declare two arguments that may be passed either to the HodMockFactory constructor, or equivalently to the populate_mock function:

Num_ptcl_requirement
halo_mass_column_key

These two arguments together permit the user to make more customizable initial halo completeness cuts with a simpler and more transparent interface.
This PR also prompted a much-needed syntax cleanup for the populate_mock method, which had become very cluttered with nested control flow.
@nickhand - since you discovered this awkwardness and will be using this feature in short order, would you mind providing some feedback on this implementation? I will wait to merge this PR until you've had a chance to weigh in.
Also, fyi, I added in a dedicated test to demonstrate that application of this feature is handled correctly: see TestHodModelFactory.test_Num_ptcl_requirement

This is exactly what I had in mind for the interface. I think the added transparency is especially useful for new users for the scenario when the completeness cut is applied by accident -- it should now be easy to find the cause via documentation if the low-mass HOD is missing

Great, thanks for the feedback, I'll go ahead and merge this in. Do let me know if you encounter other problems or nuisances.


near validators shows wrong numbers of seats

Run a test network on mocknet (or localnet)
$ NEAR_ENV=local near validators current
Loaded master account 1j02-load-test.near key from /home/ubuntu/.near/validator_key.json with public key = ed25519:76NVkDErhbP1LGrSAf5Db6BsFJ6LBw6YVA4BsfTBohmN
Validators (total: 3, seat price: 5,089,930):
.-------------------------------------------------------------------------------------------.
|    Validator Id     |   Stake    | # Seats | % Online | Blocks produced | Blocks expected |
|---------------------|------------|---------|----------|-----------------|-----------------|
| jlk4-load-test.near | 10,179,860 | 1       | 100%     |              89 |              89 |
| 969c-load-test.near | 7,634,895  | 1       | 100%     |              44 |              44 |
| wq7s-load-test.near | 5,089,930  | 0       | 100%     |              45 |              45 |
'-------------------------------------------------------------------------------------------'

Expected behavior is to get the numbers of seats: 2 + 1 + 1 = 4
Got numbers of seats: 1 + 1 + 0 = 2

@nikurt Have you tried to use RPC Call? I'm wondering if it's on the CLI level.
Also, I'm not sure how to set up a local node with several validators, maybe we can pair and work on it someday.

Good point about the RPC call. Let me try it later and get back to you.

I assume you mean this RPC endpoint: https://docs.near.org/docs/api/rpc/network#validation-status
The response only has stakes and doesn't have seats: rpc.txt

@nikurt This is the function that is getting executed: https://github.com/near/near-cli/blob/7dd821cde1b0875ce61e5ea53847d5efbfef927f/utils/validators-info.js#L17
result.current_validators.length is used there.
This is the call to get this result: https://github.com/near/near-cli/blob/7dd821cde1b0875ce61e5ea53847d5efbfef927f/utils/validators-info.js#L11

This issue is already outdated, as 1.23 is going to limit seats to just 1 per validator. Which needs a different code change in near-cli.

Ok, closing this one then. Should we just delete the seats column?

Delete the seats column?

Sounds good.

@nikurt I noticed that # of seats can be 0 or 1. Maybe we still need that column. Not sure.


Formula for calculateCheeseCubeCoverage in pizza-pi is misleading

The formula given is
pizzas = (cheese_dimension^3) / (thickness * PI * diameter)

It should be:
pizzas = (cheese_dimension^3) / (thickness * PI * (diameter/2)^2)

The formula given produces wildly incorrect results. However, if it's changed now it will invalidate all of the existing community solutions. Instead, I suggest a note be added to the instructions explaining that the formula needs to be used as-is rather than being corrected by the programmer.
I think it would also be helpful for beginners if the formula used ** rather than ^, since ^ is a valid operator in PHP but produces very unexpected results that are very hard to figure out if you don't already know PHP. Alternatively, the formula could use a superscript-3 Unicode character:
pizzas = (cheese_dimension³) / (thickness * PI * diameter)

@neilmayhew Even if the use of PI in that equation resembles calculating the area of the pizza, the exercise does not make that claim. "Lilly calculated an equation to determine [...] of some diameter (d)" in my eyes clearly enough says, that the formula is made up by Lilly.
Regarding the choice of characters: I will re-write the exercise soon and focus it on the use of floating point numbers, not the use of arithmetic operators. That means, I will provide a copy&paste formula and not use ^ (bitwise XOR) but ** as you suggest.

Even if the use of PI in that equation resembles calculating the area of the pizza, the exercise does not make that claim. "Lilly calculated an equation to determine [...] of some diameter (d)" in my eyes clearly enough says, that the formula is made up by Lilly.

Technically, you're correct, but unless someone is playing very close attention they could easily miss this (as I did) and have a very hard time understanding what they did wrong (despite the fact that I've been programming for many years). It seemed natural to me to "fix" the formula, thinking that it was a typo. The instructions say the function should "return the number of pizzas that can be made" and so I tried to do that.
Perhaps these slight changes to the wording would help:

Lilly decided to use the following formula to determine …

And uses Lilly's formula to return the number of pizzas that can be made while rounding down.


ACF posts now return as TimberPosts

Ticket: #944
Reviewer: @jarednova
Issue

ACF fields that container a post would return as WP_Post, not Timber\Post
Solution

If get_field returns an array, we run through each array element to see if it's either an array(1) or is an instance of WP_Post(2)

We run $this->convert again recursively till $ele is no longer an array
We pass the WP_Post into Timber\Post

Impact

None that I know of, if someone already has done this manually, it will just end up passing Timber\Post into Timber\Post
Usage

There is less usage as you won't have to cast WP_Post to TimberPost anymore
Considerations

Performance I think should be good, I don't think instanceof or gettype are expensive?
Testing

No tests added, may add some after namespacing is merged.

looks good, let's add it to the namespace PR!


Add a geographical README.md file to mm list

As per this discussion: https://social.afront.org/@kwf/111722503132136572 this is geographical list of each MM location from what could be garnered through sponsor's websites or peeringDB. Some locations cannot be determined and some that have been documented maybe slightly incorrect.

fork systems is in ashburn but my website sucks so I'd leave it off

I'm not merging this. We do need to add geo info to the hostvars, but we should do it in the actual yaml files themselves and I was thinking of matching the Alma mirror data structure https://github.com/AlmaLinux/mirrors/blob/master/mirrors.d/forksystems.mm.fcix.net.yml#L11-L15

I like that proposal. The Alma mirror content works well. Is there anyway then to push the geo data to a single .md file to avoid having to open each up?
Doing it the Alma way, will that allow mirror networks to temporarily take mirrors offline in the event of maintenance or faults to avoid having to get you guys involved?

@warthog9 this: 'our own "generate a map for our own website" which I've still got that website part on my todo plate somewhere'.
This came about through the discussion on the link I originally posted. I thought it was a good idea too. But if it isn't or too hard then that is fine, resources probably can be better used elsewhere.


Release rayon 1.4.0 / rayon-core 1.8.0

Implemented a new thread scheduler, RFC 5, which uses targeted wakeups for
new work and for notifications of completed stolen work, reducing wasteful
CPU usage in idle threads.
Implemented IntoParallelIterator for Range<char> and RangeInclusive<char>
with the same iteration semantics as Rust 1.45.
Relaxed the lifetime requirements of the initial scope closure.

Full comparison: https://github.com/rayon-rs/rayon/compare/v1.3.1...cuviper:release-1.4.0

bors r+


Bad practice with assert in codebase

assert is fine for tests, but you can got some troubles in main codebase like this:
slav0nic@pc:/tmp$ cat ooops.py
assert(1<0)
slav0nic@pc:/tmp$ python ooops.py
Traceback (most recent call last):
  File "ooops.py", line 1, in <module>
    assert(1<0)
AssertionError
slav0nic@pc:/tmp$ python -O ooops.py
slav0nic@pc:/tmp$ python -OO ooops.py
slav0nic@pc:/tmp$

afaik in Debian py modules compiled to pyc after installation, and your will got some troubles with asserts
https://github.com/tavendo/AutobahnPython/search?utf8=✓&q=assert+NOT+test
https://github.com/crossbario/crossbar/search?utf8=✓&q=assert+NOT+test&type=Code

duplicate of https://github.com/tavendo/AutobahnPython/issues/99

@slav0nic slightly unrelated rambling: I don't care much about distro Python packaging - it's simple: don't use it. There is no value in distro packaged Python packages.

@slav0nic pls see here .. we are gonna change it: https://github.com/tavendo/AutobahnPython/blob/master/DEVELOPERS.md#use-of-assert-vs-exceptions


Revert "Use latest 0.12.0 of mobile-center-cli (#5775)"

This reverts commit fa5d8906443469cfba0fb44b29dffc680a296f71 since it broke out canary builds

Don't you need to bump the version of the task too?


✘ [ERROR] Plugin "vike-esbuild" returned a path in the "file" namespace that is not an absolute path:

Description
From PM:

it seems like vike-esbuild can't transpile the imports, which in our ESM monorepo setup point to a file in the framework (taproot) workspace:

14:25:59 [vike][config] Failed to transpile /src/renderer/+passToClient.js because:
✘ [ERROR] Plugin "vike-esbuild" returned a path in the "file" namespace that is not an absolute path: @ecosia/taproot/renderer/server/passToClient.js

also tried to change +passToClient.js into +config.js and export { passToClient: […] } config object; no luck, the import is still not processed.

@LostCrew Active the debug logs with DEBUG=vike:pointer-imports npm run ... and report back the logs.

Setup: yarn v1 with workspaces (yes, we are aware that, at this point, any other more modern package manager is better 😢), ESM, Node v20.2.x.
Output:
11:31:54 [vike][config] Failed to transpile /src/renderer/+passToClient.js because:
✘ [ERROR] Could not resolve "redacted_path_to_framework/renderer/server/passToClient.js" [plugin vike-esbuild]

    src/renderer/+passToClient.js:1:25:
      1 │ ...assToClient from 'redacted_path_to_framework/renderer/server/passToClient.js';
        ╵                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Also:
11:31:54 [vike][Warning] Update to the new V1 design to get rid of Vite's warning: The glob option "as" has been deprecated in favour of "query". See https://vike.dev/migration/v1-design for how to migrate.
The glob option "as" has been deprecated in favour of "query". Please update `as: 'extractExportNames'` to `query: '?extractExportNames'`.

From yarn.lock, maybe useful package versions:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-> version "0.21.5"
<EMAIL_ADDRESS>-> version "0.17.19",
<EMAIL_ADDRESS>|| ^0.20.0 || ^0.21.0 || ^0.22.0 || ^0.23.0": -> version "0.23.1"

Error does not occur for imports in other Vike-handled files (+onRenderHtml.js, +onRenderClient.js).
Exporting hardcoded values, thereby renouncing to importing them from a common place and repeat this across all projects that use Vike, circumvent the issue but it is not ideal in terms of points of mantainance.
Thanks for advising 👍🏻

Your last output is a different error than the error I quoted in my original post, and it seems unrelated to Vike.
Also, the debug logs (DEBUG=vike:pointer-imports) are missing. You should get logs like the following:
vike:pointer-imports code, no transformImports() (/renderer/+config.ts)
vike:pointer-imports transpile<EMAIL_ADDRESS>vike:pointer-imports code, post esbuild<EMAIL_ADDRESS>
The best would be that you reproduce the original error and share the debug logs.

True, the state of the imports when running the above command was transitional and I thought the flag was set for the session, but wasn't. Here is the output with the import pointing to an existing file in the workspace of the framework that encapsulate Vike (once again, real framework npm package name redacted to @ecosia/framework for privacy and security):
vike:pointer-imports transpile /src/renderer/+passToClient.js
vike:pointer-imports onResolved()
                     {
                       "args": {
                         "path": "@ecosia/framework/renderer/server/passToClient",
                         "importer": "/Users/emanuele/Code/core/search/settings/src/renderer/+passToClient.js",
                         "namespace": "file",
                         "resolveDir": "/Users/emanuele/Code/core/search/settings/src/renderer",
                         "kind": "import-statement",
                         "with": {}
                       },
                       "resolved": {
                         "errors": [],
                         "warnings": [],
                         "path": "/Users/emanuele/Code/core/framework/renderer/server/passToClient.js",
                         "external": false,
                         "sideEffects": true,
                         "namespace": "file",
                         "suffix": ""
                       },
                       "importPathTranspiled": "@ecosia/framework/renderer/server/passToClient",
                       "isPointerImport": false,
                       "isExternal": false
                     }
09:39:36 [vike][config] Failed to transpile /src/renderer/+passToClient.js because:
✘ [ERROR] Plugin "vike-esbuild" returned a path in the "file" namespace that is not an absolute path: @ecosia/taproot/renderer/server/passToClient

    src/renderer/+passToClient.js:1:25:
      1 │ ...t passToClient from '@ecosia/taproot/renderer/server/passToClient';
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

@ecosia/framework for privacy and security

Can you PM me the real one? This may very well be the issue.

@ecosia/framework for privacy and security

Can you PM me the real one? This may very well be the issue.

Or, alternatively, publish a reproduction.

You now have a new PM

Can you try<EMAIL_ADDRESS>I believe that should fix it.

Fix released in 0.4.196.


Update baseline profile

Goal

Testing

Release Notes

WHAT:
WHY:

#1014  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite


Asserting interactions with react native mocks

Hi,
I'm new to React Native so excuse me if this question has an obvious solution but I couldn't find it.
I'm trying to verify interactions with React Native components. In my case I have a Navigator passed to my component and I use it as so:
class BackText extends Component {
  render() {
    return (
      <Text onPress={() => this.props.navigator.pop()}>back</Text>
    );
  }
}

I'm trying to build my unit test around this component but I'm not sure which Navigator to pass to my component.
I tried importing the Navigator from either react-native or react-native-mock and initiate them in my tests but neither had a pop method (or other Navigator methods).
Of course I can bypass the problem by setting up my own class with one pop method that I will be spying on but I'm trying to avoid re-mocking the RN API.
What's the preferred way of verifying interactions with the RN mocked components?
Thank you

When in a unit test, you should have set up the mock by requiring react-native-mock/mock. then any requires from react-native are mocked by react-native-mock. The mocks are designed to be shallow, and so don't have this functionality (yet). The best solution would be to mock your pop function with a library like sinon, and spy on that to check it was called

Sorry I forgot to mention I required react-native-mock/mock and I'm able to test my own functionality smoothly.
I'll take your suggestion on how to verify RN components.
Thanks you for your answer.


Improve display of HUI data

Fixes https://github.com/aqualinkorg/aqualink-app/issues/978
This PR:

Adds source to charts' tooltip label
Displays one year of data if there are extra sensors (instead of 1 month)
Fixes graphs not showing lines due to date being spaced out in months
Adds an option to adapt timestamp to site's timezone in data uploads
Fetches and show raw HUI data, not hourly
Adds min max dates per site for uploads

hello @ericboucher @Caesarh97
A deployed version of these changes can be found here: https://aqualink-app-programize.web.app/sites/1704
I have included a copy of all affected sites. Here is the modified version of the uploads CSV i used.
reefs-for-programize-hui.csv

hello @ericboucher @Caesarh97 A deployed version of these changes can be found here: https://aqualink-app-programize.web.app/sites/1704 I have included a copy of all affected sites. Here is the modified version of the uploads CSV i used. reefs-for-programize-hui.csv

Hello @echaidemenos and @ericboucher,
Good job on this request! I have a couple of comments.

The start date and end date when clicking on "VIEW UPLOAD" are still fixed at 2016-06-14 and 2023-12-07. Is this correct? If so, would it be possible for it to automatically adjust depending on when the first and last data points were added?

Additional questions:

It looks good when you added "NOAA" on the graph for surface temperature. However, I'm wondering if people still understand that it's satellite data from NOAA. Do you think it might be better to change it to "NOAA satellite data" or NOAA satellite"? Or would that be too long?
A new question: In the image below, you can see that the box with data is slightly to the right of the point that you want to look at. Would it be possible to change it so that it hovers straight above the point and not to the right? This would be for all sites and not just HUI.

Hello @Caesarh97 @ericboucher
I have updated it so we keep the min and max date, of an upload, per site as well. The upload must be re done, for this to take effect:
https://aqualink-app-programize.web.app/sites/1704

Hello @Caesarh97 @ericboucher I have updated it so we keep the min and max date, of an upload, per site as well. The upload must be re done, for this to take effect: https://aqualink-app-programize.web.app/sites/1704

@echaidemenos Sorry, I haven't seen the comment until now. Good job, and thank you! I can see that you changed the location of the box when hovering over the data in the graphs as well.  Would it be possible to keep the circle and have the box appear above the circle instead (maybe 10-15px above)? That would make it easier when looking at the data. Please only do this change if it's a relatively quick fix.

@Caesarh97 do you remember when you saw that circle? I don't remember seeing it recently?

@ericboucher It's a little bit sensitive, but it still appears.
https://github.com/aqualinkorg/aqualink-app/assets/113801743/88bf8e07-e126-44e0-b62c-cf863f692654

@Caesarh97 I tried to make it a bit less sensitive, can you give it a go? https://aqualink-app-987.surge.sh/

@ericboucher It's perfect! Thanks, Eric.


Update requests dependency

@regbers-viktor @MSlootwegVIKTOR @GliderGeek
Please update request and also implement #23. Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potential
forwarding of Proxy-Authorization headers to destination servers whenfollowing HTTPS redirects. : https://github.com/psf/requests/releases/tag/v2.31.0

Should be fixed in v0.2.10


Typo in the last paragraph

There is a typo in the last paragraph (marked bold): "...network buffer list pointed to by metBufferList must be freed by a call..."
Obviously there should be "netBufferList"

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

ID: eb9207f1-e8ca-b5f5-d3d6-0dfdfef96084
Version Independent ID: 98670c48-c67e-01ef-e10a-a7a97c2ec108
Content: FwpsStreamInjectAsync0 function
Content Source: wdk-ddi-src/content/fwpsk/nf-fwpsk-fwpsstreaminjectasync0.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

I once met a netBufferList in a vTable.....
Thanks for the catch, @baton. Fixed in source. Should be live soon. Feel free to make edits and commit in the future. We spent a lot of money on this open publishing stuff, and we'd really like our friends to use it. :-)


luci-app-ddns displays error on load

Upgrading OpernWRT on my TP-Link 1043ND v1 and completely clearing the configurations due to some weird behavior and instability.
I Installed luci-app-ddns version 2.4.9-3 and when navigating to the "Services" > "Dynamic DNS" menu item, I am confronted with the following error message:
Failed to execute cbi dispatcher target for entry '/admin/services/ddns'.
The called action terminated with an exception:
/usr/lib/lua/luci/controller/ddns.lua:107: attempt to index field '?' (a nil value)
stack traceback:
	/usr/lib/lua/luci/controller/ddns.lua:107: in function 'service_version'
	/usr/lib/lua/luci/controller/ddns.lua:117: in function 'service_ok'
	/usr/lib/lua/luci/model/cbi/ddns/overview.lua:20: in function 'func'
	/usr/lib/lua/luci/cbi.lua:66: in function 'load'
	/usr/lib/lua/luci/dispatcher.lua:845: in function </usr/lib/lua/luci/dispatcher.lua:839>

The ddns-scripts package is version 2.7.8-1 and the configuration file is the default one generated upon install.
Release Info:
root@OpenWrt:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="18.06.5"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 18.06.5"
VERSION_ID="18.06.5"
HOME_URL="http://openwrt.org/"
BUG_URL="http://bugs.openwrt.org/"
SUPPORT_URL="http://forum.lede-project.org/"
BUILD_ID="r7897-9d401013fc"
LEDE_BOARD="ar71xx/generic"
LEDE_ARCH="mips_24kc"
LEDE_TAINTS=""
LEDE_DEVICE_MANUFACTURER="OpenWrt"
LEDE_DEVICE_MANUFACTURER_URL="http://openwrt.org/"
LEDE_DEVICE_PRODUCT="Generic"
LEDE_DEVICE_REVISION="v0"
LEDE_RELEASE="OpenWrt 18.06.5 r7897-9d401013fc"

Installed Packages:
root@OpenWrt:~# opkg list-installed
base-files - 194.2-r7897-9d401013fc
busybox - 1.28.4-3
ddns-scripts - 2.7.8-1
dnsmasq - 2.80-1.4
dropbear - 2017.75-7.1
firewall - 2018-08-13-1c4d5bcd-1
fstools - 2019-03-28-ff1ded63-5
fwtool - 1
hostapd-common - 2018-05-21-62566bc2-8
ip6tables - 1.6.2-3
iptables - 1.6.2-3
iw - 4.14-1
iwinfo - 2018-07-31-65b8333f-1
jshn - 2018-07-25-c83a84af-2
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 4.9.198-1-2b8f9dfe583e5c09aadd9474da55137f
kmod-ath - 4.9.198+2017-11-01-10
kmod-ath9k - 4.9.198+2017-11-01-10
kmod-ath9k-common - 4.9.198+2017-11-01-10
kmod-cfg80211 - 4.9.198+2017-11-01-10
kmod-gpio-button-hotplug - 4.9.198-2
kmod-ip6tables - 4.9.198-1
kmod-ipt-conntrack - 4.9.198-1
kmod-ipt-core - 4.9.198-1
kmod-ipt-nat - 4.9.198-1
kmod-lib-crc-ccitt - 4.9.198-1
kmod-mac80211 - 4.9.198+2017-11-01-10
kmod-nf-conntrack - 4.9.198-1
kmod-nf-conntrack6 - 4.9.198-1
kmod-nf-ipt - 4.9.198-1
kmod-nf-ipt6 - 4.9.198-1
kmod-nf-nat - 4.9.198-1
kmod-nf-reject - 4.9.198-1
kmod-nf-reject6 - 4.9.198-1
kmod-nls-base - 4.9.198-1
kmod-ppp - 4.9.198-1
kmod-pppoe - 4.9.198-1
kmod-pppox - 4.9.198-1
kmod-slhc - 4.9.198-1
kmod-usb-core - 4.9.198-1
kmod-usb-ehci - 4.9.198-1
kmod-usb-ledtrig-usbport - 4.9.198-1
kmod-usb2 - 4.9.198-1
libblobmsg-json - 2018-07-25-c83a84af-2
libc - 1.1.19-2
libgcc - 7.3.0-2
libip4tc - 1.6.2-3
libip6tc - 1.6.2-3
libiwinfo - 2018-07-31-65b8333f-1
libiwinfo-lua - 2018-07-31-65b8333f-1
libjson-c - 0.12.1-2
libjson-script - 2018-07-25-c83a84af-2
liblua - 5.1.5-1
liblucihttp - 2019-07-05-a34a17d5-1
liblucihttp-lua - 2019-07-05-a34a17d5-1
libmbedtls - 2.16.3-1
libnl-tiny - 0.1-5
libpthread - 1.1.19-2
libubox - 2018-07-25-c83a84af-2
libubus - 2018-10-06-221ce7e7-1
libubus-lua - 2018-10-06-221ce7e7-1
libuci - 2019-05-17-f199b961-1
libuclient - 2018-11-24-3ba74ebc-1
libustream-mbedtls - 2018-07-30-23a3f283-2
libxtables - 1.6.2-3
logd - 2018-02-14-128bc35f-2
lua - 5.1.5-1
luci - git-19.309.48729-bc17ef6-1
luci-app-ddns - 2.4.9-3
luci-app-firewall - git-19.309.48729-bc17ef6-1
luci-base - git-19.309.48729-bc17ef6-1
luci-lib-ip - git-19.309.48729-bc17ef6-1
luci-lib-jsonc - git-19.309.48729-bc17ef6-1
luci-lib-nixio - git-19.309.48729-bc17ef6-1
luci-mod-admin-full - git-19.309.48729-bc17ef6-1
luci-proto-ipv6 - git-19.309.48729-bc17ef6-1
luci-proto-ppp - git-19.309.48729-bc17ef6-1
luci-ssl - git-19.334.34552-3a3d8f4-1
luci-theme-bootstrap - git-19.309.48729-bc17ef6-1
mtd - 23
netifd - 2019-01-31-a2aba5c7-2.1
odhcp6c - 2018-07-14-67ae6a71-15
odhcpd-ipv6only - 1.15-3
openwrt-keyring - 2018-05-18-103a32e9-1
opkg - 2019-06-14-dcbc142e-1
ppp - 2.4.7-12
ppp-mod-pppoe - 2.4.7-12
procd - 2018-03-28-dfb68f85-1
px5g-mbedtls - 6
rpcd - 2018-11-28-3aa81d0d-2
rpcd-mod-rrdns - 20170710
swconfig - 11
uboot-envtools - 2018.03-1
ubox - 2018-02-14-128bc35f-2
ubus - 2018-10-06-221ce7e7-1
ubusd - 2018-10-06-221ce7e7-1
uci - 2019-05-17-f199b961-1
uclient-fetch - 2018-11-24-3ba74ebc-1
uhttpd - 2018-11-28-cdfc902a-3
usign - 2019-08-06-5a52b379-1
wireless-regdb - 2017-10-20-4343d359
wpad-mini - 2018-05-21-62566bc2-8

rpcd info:
root@OpenWrt:~# ps ww | grep rpcd
  835 root      1528 S    /sbin/rpcd -s /var/run/ubus.sock -t 30
14684 root      1200 S    grep rpcd

board info:
root@OpenWrt:~# lua -lluci.util -lubus -e 'luci.util.dumptable(ubus.connect():call("system", "board", {}))'
board_name      tl-wr1043nd
hostname        OpenWrt
release table: 0x431cb0
        distribution    OpenWrt
        revision        r7897-9d401013fc
        version 18.06.5
        target  ar71xx/generic
        description     OpenWrt 18.06.5 r7897-9d401013fc
model   TP-Link TL-WR1043N/ND v1
kernel  4.9.198
system  Atheros AR9132 rev 2

ubus Login:
root@OpenWrt:~# ubus call session login '{ "username": "root", "password": "********" }'
{
        "ubus_rpc_session": "08c797a0968473e16845b11bbe1b1760",
        "timeout": 300,
        "expires": 299,
        "acls": {
                "access-group": {
                        "uci-access": [
                                "read",
                                "write"
                        ],
                        "unauthenticated": [
                                "read"
                        ]
                },
                "ubus": {
                        "session": [
                                "access",
                                "login"
                        ]
                },
                "uci": {
                        "*": [
                                "read",
                                "write"
                        ]
                }
        },
        "data": {
                "username": "root"
        }
}

@Ansuel any opinion? I think the root cause of the problem is this line https://github.com/openwrt/luci/blob/openwrt-18.06/applications/luci-app-ddns/luasrc/controller/ddns.lua#L117
@shirogitsune Could you change this line and return always true?

problem is that for some reason
ver = IPKG.info(srv_name)[srv_name].Version
IPKG.info can't find srv_name (ddns_scripts) and fail to access the key with index srv_name
A bug in IPKG.info ? Or the module was different in 18.06 ?

The module.ipkg class is extremely expensive, isn't there some more lightweight way to obtain the installed version?

Well i think use the os.popen is equally expensive... Should we use it and remove ipkg module ?

@Ansuel any opinion? I think the root cause of the problem is this line https://github.com/openwrt/luci/blob/openwrt-18.06/applications/luci-app-ddns/luasrc/controller/ddns.lua#L117
@shirogitsune Could you change this line and return always true?

@feckert. I tried that along with verifying that the helper script returned a valid version number.

you need to clear luci cache
rm -r /tmp/luci-*

@Ansuel I was going to try what you suggested once I got home from work. However, I clicked on the "Dynamic DNS" and it has apparently decided to begin working. I checked the lua script and it was unmodified so I cleared the luci cache as you suggested and it's still working. One of three things has apparently happened:

You used some sort of quantum mechanics to realign the bits so it is working on my router.
I have gone completely mad. (Not ruling this one out).
The an extended power outage bled the electrons out of RAM and unstuck whatever was broken.

I suspect #3 is what fixed it, but I'm not going to rule out 1 or 2. Thanks everyone.

Slightly related to this, I'm getting the following error, and I suspect it is because I don't have opkg installed at all (I build my own image with all I need). Should opkg be optional somehow, or at least specified as a package dependency?
Failed to execute cbi dispatcher target for entry '/admin/services/ddns'.
The called action terminated with an exception:
/usr/lib/lua/luci/controller/ddns.lua:116: attempt to index field '?' (a nil value)
stack traceback:
	/usr/lib/lua/luci/controller/ddns.lua:116: in function 'service_version'
	/usr/lib/lua/luci/controller/ddns.lua:126: in function 'service_ok'
	/usr/lib/lua/luci/model/cbi/ddns/overview.lua:20: in function 'func'
	/usr/lib/lua/luci/cbi.lua:66: in function 'load'
	/usr/lib/lua/luci/dispatcher.lua:943: in function </usr/lib/lua/luci/dispatcher.lua:937>

(this is on 19.07-HEAD)

you need to clear luci cache
rm -r /tmp/luci-*

yes, It works


[ZT] - add optional linux os version fields - os-version.md

Added new linux version fields, how they are derived, and how to use them.

When will the Linux option become available in the ZT dashboard?

merging in #6191


Update node-gyp to 10.0.1

Hi @staltz ,
Creating this PR to update the base version of nodejs-mobile-gyp to match node-gyp 10.0.1 (latest release). Main motivator is really that nodejs-mobile-gyp doesn't work with Python3, that's shipped by default everywhere now. node-gyp upstream has that fixed for ages, it seems.
I've tested this nodejs-mobile-gyp for Android in nodejs-mobile-cordova, but I'm on an Android only scenario for now and don't really have the means to test iOS. Is there some change you can test for your iOS use cases as well? Thank you.
I've been consuming this updated version by overriding a dependency of a dependency as needed. I assume the same can be done for testing it with nodejs-mobile-react-native as well.
Here's what I'm adding to package.json.
  "overrides": {
    "nodejs-mobile-cordova": {
      "nodejs-mobile-gyp": "github:JaneaSystems/nodejs-mobile-gyp#merge-node-gyp-10.0"
    }
  },

For seeing actual differences between upstream 10.0.1 and this new branch, https://github.com/JaneaSystems/nodejs-mobile-gyp/compare/upstream-v10.0.1...merge-node-gyp-10.0 is a better way of seeing those.
If all is well, thinking it'd be nice upping the nodejs-mobile-gyp version to 0.4.0 and releasing to npm. (or 10.0.1, really, since it's mirroring that one)
Thoughts?
For merging, it's best for a merge commit, to facilitate future updates.

Weird, is this only occurring when testing with this override?

Yes. I can try on another nodejs-mobile project for iOS that I have locally.

I've just given a nodejs-mobile-react-native a try, with the nodejs-mobile-gyp override and a nodejs-project running sqlite3 (with a node-pre-gyp override as well). I've been able to run this well on android and confirmed sqlite3 is running on Android. (did have to delete a folder named "root" from one of the node_modules in nodejs-project because it doesn't work well copying on Android runtime, but that was the only weird hack to get it to not fail at runtime).
Didn't get any linter errors.
I've got no iOS device to test, though :(
But looks like the linter errors are not related directly to the nodejs-mobile-gyp update itself, unless it's forcing some other version elsewhere.
Regarding nodejs-mobile-react-native experience, WOW, I don't remember ever having such a pleasant experience with this beast 😄 You really did a number here. Great work!

Will do. For some reason I saw your message only now, that's why there was silence.

Confirmed it's working. Thanks for the patches and the patience!


Node program flow broken after two close() call

I assume you agree that the snapDb can be closed more than one time because you had merged my unit test for that (allow call close() twice).
However, I found when I call the close twice, the program flow had been broken.
The following code will demonstrate that, we can expect we get the following output message:
before close1
before close2
after close 1&2

However, what we get will be:
$ ./t.ts
before close1
before close2
undefined

The re-produceable code:
#!/usr/bin/env ts-node

import {
  SnapDB,
}               from 'snap-db'

async function main () {
  const db = new SnapDB({
    dir: '/tmp/xx',
    key: 'string',
  })
  console.info('before close1')
  await db.close()
  console.info('before close2')
  await db.close()
  console.info('after close 1&2')
}

main()
  .catch(console.error)

1.1.3 has been released on NPM and resolves this issue.  Feel free to comment if you find anything further!

Nice!


MediaQuery is required for Chips but there's no documentation about it?

See https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/material/chip.dart#L1396 and https://docs.flutter.io/flutter/material/Chip-class.html

CC @HansMuller @gspencergoog


RL crashes on linux, illegal access warning

Type
Incorrect behavior
Operating System
None
OS Version
Debian GNU/Linux 11 (bullseye)
Bug description
Trying to launch RuneLite this morning and i receive this error code
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by net.runelite.client.util.ReflectUtil (file:/home/username/.runelite/repository2/client-<IP_ADDRESS>.jar) to field java.lang.reflect.Executable.declaredAnnotations
WARNING: Please consider reporting this to the maintainers of net.runelite.client.util.ReflectUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Client will not launch.
Screenshots or videos
No response
RuneLite version
RL version 2.6.4
Logs
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by net.runelite.client.util.ReflectUtil (file:/home/username/.runelite/repository2/client-<IP_ADDRESS>.jar) to field java.lang.reflect.Executable.declaredAnnotations
WARNING: Please consider reporting this to the maintainers of net.runelite.client.util.ReflectUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

UPDATE: randomly got an message asking to restart linux. Problem occured for 2-3 hours previous to this. Solved!


fixed sqlite bug

Fixes #336

@jaredwray workspaces do not have an option to exclude a package. If I exclude a package it gives a module not found  error in other packages which are using that particular package.

@alphmth - thanks for looking at this and I am wondering if at this point we should switch to npm workspaces as we are seeing very little value in using yarn. Here is what would need to happen to make this work:
Docs: https://docs.npmjs.com/cli/v8/using-npm/workspaces
[ ] update the mono repo package to use npm workspaces. Example:
  "scripts": {
    "test": "npm run test --workspaces"
    "test:services:start": "docker-compose -f ./docker-compose.yaml up -d",
    "test:services:stop": "docker-compose -f ./docker-compose.yaml down -v",
    "coverage": "npm run coverage --workspaces",
    "clean": "rm -rf node_modules && rm -rf package-lock.json &&  npm run clean --workspaces"
  }

[ ] update the tests.yaml to use npm moving forward
      - name: Start Services
        run: npm run test:services:start

      - name: Install Dependencies
        run: npm install

      - name: Test [keyv]
        run: npm run test --workspace=packages/keyv

      - name: Test [test-suite]
        run: npm run test --workspace=packages/test-suite

      - name: Test [etcd]
        run: npm run test --workspace=packages/etcd

      - name: Test [memcache]
        run: npm run test --workspace=packages/memcache

      - name: Test [mongo]
        run: npm run test --workspace=packages/mongo

      - name: Test [mysql]
        run: npm run test --workspace=packages/mysql

      - name: Test [offline]
        run: npm run test --workspace=packages/offline

      - name: Test [postgres]
        run: npm run test --workspace=packages/postgres

      - name: Test [redis]
        run: npm run test --workspace=packages/redis

      - name: Test [sqlite]
        run: npm run test --workspace=packages/sqlite

      - name: Test [tiered]
        run: npm run test --workspace=packages/tiered

      - name: Generate Code Coverage Report
        run: npm run coverage

This should help.

@jaredwray Its not working in Node 12, 14

@alphmth - it looks like NPM is not working under Node 12 and 14. Can we try to install the latest NPM in the workflow to get it to do what we need?

@alphmth - was able to get this to work on yarn but still with the same issue on sqlite. Going to close this down.


Scanning super slow for DataMatrix

Environment: iPhone 6S with iOS 9.2.1
Plugin version : phonegap-plugin-barcodescanner 4.1.0
I try to scan dataMatrix with the plugin and it is super slow and hard to scan the code. With QRCode no problem.
With the version 1.2 and 2.0 the DataMatrix Scan is super fast.

+1

+1


Question about memory length

Thank you for your outstanding work. I have a question about the memory length. In Figure 5, as the length increases, the model’s accuracy first increases and then decreases. Why the model's accuracy will decrease ultimately? It seems like that more information is preserved with a larger memory.

MovieChat is a training-free method based on VideoLLaMA. Since VideoLLaMA is trained on relatively short videos, it makes it hard to understanding extremely long video for MovieChat too.

Thank you for your reply. Have you ever tried to train the VideoLLaMa on Movie-chat dataset?

Since there was no high-quality long video QA dataset last year, we didn't train VideoLLaMA


support sync generator

As discussed in #3 , I rewrite ProcessJob.run to support sync generators.
Please review if this approach is appropriate, we can rewrite other Job.run methods and support async generators too.
example code:
import typing as t
import asyncio

from executor.engine import Engine, ProcessJob

def func(n: int) -> t.List[int]:
    import time

    time.sleep(1)
    return list(range(n))

def gen(n: int) -> t.Generator[int, None, None]:
    import time

    for i in range(n):
        time.sleep(0.5)
        print(f"sync yield from executor: {i}")
        yield i

async def gen_async(n: int) -> t.AsyncGenerator[int, None]:
    import asyncio

    for i in range(n):
        await asyncio.sleep(0.5)
        print(f"async yield from executor: {i}")
        yield i

async def main():
    with Engine() as engine:
        job1 = ProcessJob(func, (5,))
        engine.submit(job1)
        engine.wait()
        print(job1.result())

        job2 = ProcessJob(gen, (5,))
        engine.submit(job2)
        engine.wait()
        for x in job2.result():
            print(f"main received: {x}")

        job3 = ProcessJob(gen_async, (5,))
        engine.submit(job3)
        engine.wait()
        async for x in job3.result():
            print(f"main received: {x}")

if __name__ == "__main__":
    asyncio.run(main())

Thank you for your contribution, it's a very clever implementation.

Thank you for your contribution, it's a very clever implementation.

Glad to contribute.
I have been searching for useful concurrent frameworks for quite some time, and this is the lightest and most practical one I have seen.
I will create another PR later to make ThreadJob support generators too. I'm not familiar with Dask, it's implementation need more research.

I am trying to support generators at the base class level of Job, making the implementation of process a special case.

OK, expecting official implementation.
I tried LocalJob and ThreadJob, it seems the generator job works well. The generator object could be returned directly from them without pickle.

I have defined the run_generator method in the base class of Job and made the implementation of ProcessJob a specific case of it.
https://github.com/Nanguage/executor-engine/blob/389af29e7c0e4322a652e289697c3888825da3be/executor/engine/job/base.py#L289-L306
I think you can build upon this and incorporate your implementation of LocalJob and ThreadJob.
Additionally, some management of the lifecycle has been added. Currently, the status of the corresponding job will only be set to done after completing the iteration. like this:
https://github.com/Nanguage/executor-engine/blob/389af29e7c0e4322a652e289697c3888825da3be/tests/test_job.py#L191-L216
More details see https://github.com/Nanguage/executor-engine/commit/389af29e7c0e4322a652e289697c3888825da3be

Ok, I would like to try it.