The Recommendation for Training Big Image Data that Cannot Fit into Memory

Summary
Right now if we try to train a folder of image data that cannot fit into memory of a single machine, lightgbm is not an available option. We can see some distributed solutions for lightgbm but each of them requires one partition of the data to fit into memory in a single node.
Do we have a solution to train the data that cannot fit into memory on a single node with lightgbm?
Motivation
Train large dataset on a single node.

Thanks for using LightGBM!
I have a few suggestions below for "train a model on a larger-than-memory dataset on a single node". This question is also making me realize we should have a dedicated section in the documentation for this.
1. Use lightgbm's new Sequence API
In #4089, lightgbm took on a new API in the Python package that allows the creation of a LightGBM Dataset object from multiple files.
You might find that this interface allows you to accomplish training on a single node when the raw data is larger than memory on that node, since it constructs a Dataset incrementally from multiple files.

examples: https://github.com/microsoft/LightGBM/blob/master/examples/python-guide/dataset_from_multi_hdf5.py
API docs: https://lightgbm.readthedocs.io/en/latest/pythonapi/lightgbm.Sequence.html?highlight=Sequence
tests (for more examples):

https://github.com/microsoft/LightGBM/blob/29857c8adb3c879268cddc23037e0651c2ec4df6/tests/python_package_test/test_basic.py#L94
https://github.com/microsoft/LightGBM/blob/29857c8adb3c879268cddc23037e0651c2ec4df6/tests/python_package_test/test_basic.py#L135

When this could work: If you are able to upgrade to lightgbm 3.3.0, and can partition your data into multiple files that will work with the Sequence access pattern.
2. Try using lightgbm.dask
Depending on where in the process you're running out of memory, you might be able to avoid such problems by using lightgbm.dask. You can see the docs at https://lightgbm.readthedocs.io/en/latest/Parallel-Learning-Guide.html#dask-examples.
At high levels of memory usage, Dask workers will start spilling to disk. This can make processing much slower, but allows you to work on larger-than-memory data. http://distributed.dask.org/en/latest/worker.html#memory-management. Dask will work on a single machine if you use a LocalCluster, as all of the examples at https://github.com/microsoft/LightGBM/tree/5c8a331bf5966f1df546f154f64ed9b8856a90ee/examples/python-guide/dask do.
If you do this, it's important to partition your data in a way that allows Dask to not need to hold all of it in memory at the same time. For example, you might create a partitioned directory of Parquet files and use dask.DataFrame.read_parquet() (https://docs.dask.org/en/latest/generated/dask.dataframe.read_parquet.html).
When this could work: If your training data all fits in memory on one node after feature engineering / feature selection / sampling.
3. Train a smaller model
If you have sufficient memory to load the data and create a lgb.Dataset, but then hit memory issues during training (as the model object grows), most of the strategies at https://lightgbm.readthedocs.io/en/latest/Parameters-Tuning.html#for-faster-speed can also be used to reduce the memory footprint of the model. For example, decreasing num_leaves / max_depth or increasing min_gain_to_split, min_data_in_leaf, or min_sum_hessian_in_leaf will lead to smaller models.
When this could work: If your training data all fits in memory on one node but you see out of memory errors once training begins, due to the memory footprint of the model. And if you are able to confirm that the statistical performance of the smaller model is good enough for your use case.
4. Use Training Continuation
LightGBM offers the ability to start the boosting process from an existing trained model. See https://github.com/microsoft/LightGBM/blob/c6199311dece08e6ac08778f60d7fc9c3d796b11/examples/python-guide/advanced_example.py#L102-L112.
So I think you could partition your data into multiple files, then do something like the pseudocode below.
import lightgbm as lgb

first_file = "some_file.csv"
data, label = get_raw_data_from_csv(first_file)
first_dataset = lgb.Dataset(first_file, params={"label_column": "y"}, free_raw_data=True)
first_dataset.construct()

# train a model on this first chunk of data, for a few rounds
booster = lgb.train(
    train_set=first_dataset,
    num_boost_round=10,
)
booster.save_model("model.txt")
del booster

# for each additional file, create a Dataset and train a few more rounds
for next_file in rest_of_the_files:
    dataset = lgb.Dataset(
        next_file,
        params={"label_column": "y"},
        free_raw_data=True,
        reference=first_dataset
    )
    dataset.construct()
    booster = lgb.train(
        train_set=dataset,
        num_boost_round=10,
        init_model="model.txt"
    )
    # overwrite model file
    booster.save_model("model.txt")
    # free memory before next file
    del dataset, booster

This will be much slower than training with all of the data in memory at once, and you'll have to be very careful about how the data is partitioned. The distribution of features and the target should be roughly similar across the partitions. See https://github.com/microsoft/LightGBM/issues/4555#issuecomment-924533600 for a bit more information.
When this could work: If you can tolerate much slower training and are comfortable carefully managing the partitioning of the input data.


PDF Export Error

Hello, I have a situation similar to this bug reported here:
https://github.com/benweet/stackedit/issues/1206
I am not able to export my document as PDF, per the issue reported here.  So far as I can tell, my PDF template reads https://stackedit.io but when I attempt a conversion I just get:
HTTP error 400
Console says:
Failed to load resource: the server pdfExport?idToken= responded with a status of 400 ().
I should mention I paid for sponsorship last week, I believe it should still be valid (and I have an actual token showing in my console).
Any help would be appreciated.

I should mention I paid for sponsorship last week, I believe it should still be valid (and I have an actual token showing in my console).

After trying several times, I noticed that for whatever reason an image link in my (rather long) document was broken.  Removed the offending item and retried this morning - seemed to work just fine.  That's actually probably expected/desired behavior.
Closing due to this new info.


Make default credentials configurable

We will have to use pipeline job for review to get a good support for reading credentials id from env


Can't login with 2-Factor Authentication

Hello,
i had activate 2-Factor Authentication and can't login. It worked since months until today.
On my smartphone i use the Microsoft Authenticatior App.
So i removed the 2-Factor Authentication in my user configuration and configure it again and its still not working. (Regenerate)
I checked my PHP and Grav time settings noticed that nothing is configured in Grav so configured like the settings in php. (see Screenshots)

I configured it again but its not working. The twofa_secret was saved but it does not seems to saved correct it looks like:
twofa_secret: 'XXXXXXXX XXXX XXXX XXXX XXXX XXXX XXXX '
Is this the problem?
PHP 7.4.14
Grav v1.7.10
Admin Panel v1.10.10

Update admin plugin. It was released a couple of minutes ago.

The update fixed the problem, Thank you. Grav is a great CMS!


NameError: name 'g_policy' is not defined         BrokenPipeError: [Errno 32] Broken pipe

❓ Questions and Help
When I trained on the 2xRTX3090,the error occurred  after 01d 02h 15m 29s.
Is there a problem with my Settings？
The file sh_train_mp3d.sh is as follows.
export GLOG_minloglevel=2
export MAGNUM_LOG="quiet"

python main.py --auto_gpu_config 0  -n 4 \
    --sem_gpu_id_list "1"  --policy_gpu_id "cuda:2"  --sim_gpu_id "1" \
    --split train  --backbone_2d "rednet"  \
    --task_config "tasks/challenge_objectnav2021.local.rgbd.yaml"  --dataset "mp3d" \
    --num_sem_categories 22 --deactivate_entropymap \
    --print_images 1  -d ./tmp  --exp_name exp_kl_goal  --save_periodic 10000

The Error occurs
[swscaler @ 0x73b0d80] Warning: data is not aligned! This can lead to a speed loss
Time: 01d 02h 15m 15s, num timesteps 260720, FPS 2,
        Rewards: Global step mean/med rew: 0.2068/0.1116,  Global eps mean/med/min/max eps rew: 1.868/1.459/-0.000/5.760, ObjectNav succ/spl/dtg: 0.331/0.123/5.455(0),
        Losses: Policy explore Loss value/action/dist: 0.535/-0.005/1.033, Policy identify Loss value/action/dist: 0.545/-0.007/1.406,
IMAGEIO FFMPEG_WRITER WARNING: input image is not divisible by macro_block_size=16, resizing from (1165, 800) to (1168, 800) to ensure video compatibility with most codecs and players. To prevent resizing, make your input image divisible by the macro_block_size or set the macro_block_size to 1 (risking incompatibility).
[swscaler @ 0x6f6cd80] Warning: data is not aligned! This can lead to a speed loss
Time: 01d 02h 15m 29s, num timesteps 260760, FPS 2,
        Rewards: Global step mean/med rew: 0.2068/0.1116,  Global eps mean/med/min/max eps rew: 1.868/1.459/-0.000/5.760, ObjectNav succ/spl/dtg: 0.332/0.124/5.432(0),
        Losses: Policy explore Loss value/action/dist: 0.535/-0.005/1.033, Policy identify Loss value/action/dist: 0.545/-0.007/1.406,
Traceback (most recent call last):
  File "main.py", line 1029, in <module>
    main()
  File "main.py", line 960, in main
    torch.save(g_policy.state_dict(),
NameError: name 'g_policy' is not defined
Exception ignored in: <function VectorEnv.__del__ at 0x7efb8002dd40>
Traceback (most recent call last):
  File "/mnt/A/amax/3DAwareNav/envs/habitat/utils/vector_env.py", line 560, in __del__
    self.close()
  File "/mnt/A/amax/3DAwareNav/envs/habitat/utils/vector_env.py", line 427, in close
    write_fn((CLOSE_COMMAND, None))
  File "/mnt/A/amax/anaconda3/envs/ObjectNav/lib/python3.7/multiprocessing/connection.py", line 206, in send
    self._send_bytes(_ForkingPickler.dumps(obj))
  File "/mnt/A/amax/anaconda3/envs/ObjectNav/lib/python3.7/multiprocessing/connection.py", line 404, in _send_bytes
    self._send(header + buf)
  File "/mnt/A/amax/anaconda3/envs/ObjectNav/lib/python3.7/multiprocessing/connection.py", line 368, in _send
    n = write(self._handle, buf)
BrokenPipeError: [Errno 32] Broken pipe

Oh,"g_policy"and"g_policy_3d" are not defined in the main.py.
Is this a bug?
    # Save best models
        if (step * num_scenes) % args.save_interval < \
                num_scenes:
            if len(g_episode_rewards) >= 1000 and \
                    (np.mean(g_episode_rewards) >= best_g_reward) \
                    and not args.eval:
                torch.save(g_policy.state_dict(),
                           os.path.join(log_dir, "model_best_explore.pth"))

                torch.save(g_policy_3d.state_dict(),
                           os.path.join(log_dir, "model_best_identify.pth"))
                best_g_reward = np.mean(g_episode_rewards)

Sorry for the mistake. It looks like a bug remained during the finalization. The code is revised here


Directly open the mesos console for a task instance

To start: The direct links to download the logs files are a really nice addition! :-)

I'd like to suggest a little tweak though: Visually, keep it exactly like this! :-)
Functionally: Point the file icon to the download url of the output and the name of the output (stdout or stderr) to the url which directly opens the mesos console.
When an app is unhealthy the first thing you want to do is to check the console output. to see what's going on at that moment.

@crucidal there is already an issue ( #3244 ) requesting direct (in the browser) log access and we even have a first design. I'd like to close this issue as it kinda duplicates #3244, hope you don't mind.


Moving through rows using pk or limit/offset

This was a way rough test but there didn't seem to be any meaningful difference between the two
with pout.p("cursor"):
    user_id = 0
    while True:
        users = User.query.gt_pk(user_id).asc_pk().get(5000)
        if users:
            for u in users:
                user_id = u.pk
                print user_id
        else:
            break

with pout.p("all"):
    for u in User.query.asc_pk().all():
        user_id = u.pk
        print user_id

The new Iterator code that uses cursors exclusively makes this moot


Support Conan 1.22

Description of Problem, Request, or Question
Prepare Conan Package Tools for Conan 1.22

Fixed by #445


Delete unnecessary spaces

When copying from the web page, there is an unnecessary space after the code.

@changeworld @mikejo5000 - We're in the process of pulling these commits to the private repo, so we can verify the content on staging. We'll post a new PR # shortly and then close this PR.

@changeworld : Thanks for your contribution! The author, @mikejo5000, has been notified to review your proposed change.

moved to https://github.com/MicrosoftDocs/visualstudio-docs-pr/pull/3838.


Bump 0.1.7-2

Pull Request Test Coverage Report for Build 276

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

Totals

Change from base Build 350:
0.0%

Covered Lines:
460

Relevant Lines:
685

💛  - Coveralls

Pull Request Test Coverage Report for Build 354

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

Totals

Change from base Build 350:
0.0%

Covered Lines:
460

Relevant Lines:
685

💛  - Coveralls


Create json files to be used as backend data for different pages

Create an assets folder to contain JSON files  containing json data for
users, employers, jobs, candidates

Json files added to asset folder and is merged wih main branch


Add warning screen when PSBT change can not be detected because of legacy script type

When the input script type is unable to be detected, then change outputs and amounts is unable to be calculated. So instead of showing a no change warning, this message will be shown instead: "PSBT has unsupported input script type, please verify your change addresses."

attached is PSBT example (regtest network)
legacy multisig p2sh 1in 2 out (1 change).psbt.txt
.

Outstanding issue
PSBT Math screen is wrong. No input amount.

Outstanding issue
PSBT Math screen is wrong. No input amount.

resolving this issue by just skipping this math screen for p2sh multisig (not nested segwit) and p2pkh.

Appreciate you catching this and figuring out the best way to handle it.


[Bug]: Custom Toolbar Problem

What happened?
i am trying to implement some custom toolbar in this and following the described process in documentation
https://ngx-editor-codemirror.stackblitz.io/
here you have implemented the coremirror funcnality which is not working on this stalkblitz can you please provide me a solution or working demo so that i can implement more features according to my need
thanks in advance
Version
v14.0x
Angular Version
v14.0x
What browsers are you seeing the problem on?
Chrome
Link to reproduce
No response
Relevant log output
No response
Willing to submit a PR?
None

can anyone please respond to this ?

Yeah its broken for some reason. Will check and update this weekend.
Meanwhile you can try running the project locally, it was working fine last time i checked.
See here for how to run locally https://github.com/sibiraj-s/ngx-editor/blob/master/.github/CONTRIBUTING.md

i checked your project locally and its running fine on local but when i try to diagnose the issue by checking the ngx-editor version installed in your local project then i am unable to find it.
can you please help me with the version or if possible please resolve it

The setup is now fixed ngx-editor-codemirror.stackblitz.io


Allow axon-carrying-denrite with fork axon subtrees

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

Project coverage is 100.00%. Comparing base (94951b8) to head (3bbe21c).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #1127   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           34        34
  Lines         2669      2669
=========================================
  Hits          2669      2669


Point to NWP latest.zarr instaed of latest.netcdf

The former should be faster.

Codecov Report

Merging #42 (d5d4f0a) into main (d016312) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   92.61%   92.61%
=======================================
  Files          10       10
  Lines         271      271
=======================================
  Hits          251      251
  Misses         20       20

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


atob error when using PNG images with ex plugin

Failed to execute 'atob' on 'Window': The string to be decoded contains characters outside of the Latin1 range.
I'm trying to use the ex plugin feature to mock an android app flow. But i can't use png due to the below error and conversion to SVG doesn't give high quality image. I don't get this error with svg. This happens on Safari and Chrome 60.0.3112.113

Working as of now with google drive publishing. Using that.


Implement basic STUN server

This is an alternative to https://github.com/firezone/firezone/pull/1602 that implements the server using a library I've found called stun_codec.
It already has support for parsing a variety of attributes.
The following is a nice website to test some of the functionality: https://icetest.info/
The server is still listening on: ec2-3-89-112-240.compute-1.amazonaws.com:3478.

From my end, this is good to go in and @conectado seems like it too :D
Can somebody merge this so the PR doesn't get too big? Initially I was gonna remove the ALLOCATE testing I had in there but there will be lots of churn on the code anyway in this phase so I think it doesn't matter.


Node.js 4 support

Working on issue #35 I've realized that our package doesn't support Node.js 4 (at least it doesn't correctly tested under this version). But Jest supports it, so we have to provide our users with such compatibility.

I've changed our test cases a little bit. We can't target ES6 there, because node.js 4.x doesn't fully supports its syntax.
May be we have to add some more test-cases to check that it works and improve our docs with mentioning that our users can't use ES6 target while using node.js 4.x.
This probably will also lead to checking ts-jest working with babel-jest together.
But I don't know how to separate test cases for different node versions. @kulshekhar, any thoughts?
P.S.
I'm using nodist for local testing.

The way I look at it, node 4.x will stop being maintained in about 5 months, So I don't see any point in supporting it.

Due to LTS Plan v4 will be maintained until 2018-04-01, so I guess we have to support it unless Jest will stop doing this.

In that case, it might be helpful to update the README with the status of support for various versions.
btw, this can get complicated very fast. I spent a few hours yesterday all because some tests were failing on 6.6. If this is the case between 6.x versions, I shudder to think what's in store if we are going to support 4.x  :cold_sweat:

Ok, build on travis was failed due to not latest npm package. Original Jest seems to have same issue on travis, so I've used their workaround.
I guess we have to show status for different versions of node and will try to find out how it could be accomplished with travis.

Thanks for fixing the issue so fast.
Please make a npm publication, I'm looking forward to use the compatible version.

@Igmat  Is this good to publish? Maybe node 4 can be removed from the allowed failures list in travis.


Random hunger at roundstart is now controlled by adjustable amounts.

About the PR
The random hungerComponent and thirstComponent in newly spawned entities is now controlled by two adjustable numbers separate from the hunger thresholds, and can be made to be a specific number instead.
Why / Balance
Some mobs, such as mice, already use this functionality, however it has been nonfunctional. It also seems helpful for in the future if say, someone wanted to make rat king have a specific variation for it's starting hunger, or something similar.

The mouse hungerComponent uses currentHunger, which was not able to be set manually with the previous version
Technical details
hungerComponent and thirstComponent now have two new variables which act as the minimum and maximum for random hunger. These numbers default to 110 min/150 max and 310 min/449 max for hunger and thirst respectively, and can be specified in the prototype or modified before mapinit. If a prototype has a specified currentHunger equal to or above 0 (defaults to -1 to allow this), it will entirely skip the random hunger variation and just use that number instead.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
Some entities may have extremely high or extremely low starting hunger with the default variation, cockroaches come to mind, but I think they're parented to mice so I'm not sure.
Changelog
I don't think this needs a changelog

somewhat out of this scope but would this be applicable to all crew who join the server/spawn in having random chances of hunger levels?


No latitude longitude found in dashboard example

Hi
Currently i attached a gps receiver with linux server but it doesnt shows the gps data

It actually gets data, but it doesn't have a fix. It's either a https://en.wikipedia.org/wiki/Time_to_first_fix issue, which means u just have to wait more time or you have a really poor signal. Seeing only 6 satellites could also be this. Having a strong GPS signal indoors, is quite unusual.


The integration suddenly stopped working

Hello,
My Eify Security integration stopped working a few days ago or so. I just found some time to investigate and nothing comes to my mind as an obvious reason. I haven't changed anything about it except installing the new HA updates. I removed the integration and tried to re-add it without success.
I'm running HA Home Assistant 2022.12.7. The Eufu add-on is version 1.1.0.
This is the message:

And the log file:
2022-12-19 11:26:17.055 WARNING (MainThread) [custom_components.eufy_security] eufy_security - no devices available yet
2022-12-19 11:26:17.061 WARNING (MainThread) [homeassistant.config_entries] Config entry '<IP_ADDRESS>' for eufy_security integration not ready yet: Start Listening was not completed in timely manner; Retrying in background
2022-12-19 11:26:36.749 WARNING (MainThread) [custom_components.eufy_security] eufy_security - no devices available yet
2022-12-19 11:27:00.038 WARNING (MainThread) [custom_components.eufy_security] eufy_security - no devices available yet
2022-12-19 11:27:32.854 WARNING (MainThread) [custom_components.eufy_security] eufy_security - no devices available yet
2022-12-19 11:28:25.676 WARNING (MainThread) [custom_components.eufy_security] eufy_security - no devices available yet
2022-12-19 11:29:58.504 WARNING (MainThread) [custom_components.eufy_security] eufy_security - no devices available yet
I noticed the port has been changed automatically and I didn't notice that but it was working okay. Now, after I re-added it, it changed the port again. I tried with the port that was there and then I changed it to 3000 but it didn't work with either of them.
Thanks,
Daniel
P.S. I just noticed, after typing the add-on version, that it's way outdated but I don't see an option to update it. I tried with Auto-update with no success.

I am also experiencing this issue after the most recent HA core update.

I also have this problem after HA updates

can you please explain more what do you mean by "Fixed after setting TRUSTED_DEVICE_NAME in the settings to Eufy?"

Go to settings -> Add-ons -> Eufy Security Addon -> Settings
There you find a TRUSTED_DEVICE_NAME field that was empty.
I typed Eufy in that field and after a restart it worked.

Thanks for that. I just tried it but it still doesn't work!!

Changing TRUSTED_DEVICE_NAME to Eufy worked for me.

What's your version of the Add-on? Mine is 1.1.0 and not updating.

I experience the same issue after upgrading to HA 2022.12.7 and Eufy integration v2.9.0 today. Setting TRUSTED_DEVICE_NAME to Eufy also worked for me...whatever that setting does(?).

Eufy

Thanks a lot!
That worked for me too

Changing that setting got rid of the error message but all my eufy devices
are still unavailable.
On Wed, 21 Dec 2022 at 7:39 am, aAbdman @.***> wrote:

Eufy
Thanks a lot!
That worked for me too
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/eufy_security/issues/579#issuecomment-1360166694,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AITSGGBRTFOIRXEP7YHBI7LWOIKR7ANCNFSM6AAAAAATDJ2QUM
.
You are receiving this because you commented.Message ID:
@.***>

--
Kent Boehm
M - 0488 787 140

This is the error in seeing my logs for the add on

Same error in my case! Even after adding Eufy in settings

I had previously added the trusted device and it worked. I am now getting the 403 on device_list.

Similar to others. I had added the trusted device to the YAML and all was working until about 24 hours ago. I'm getting the same 403 error shown above. Any ideas on how to solve?

Same. Error 403.

Might be related to the dependent addon integration. Looks like they're getting a 403 with a deprecated API: https://github.com/bropat/eufy-security-client/pull/282

Might be caused by some measures Eufy/Anker took after the recent security/privacy concerns: https://community.security.eufy.com/t/to-our-eufy-security-customers-and-partners/3568215

Having exactly same issue for a few days.  Just upgraded Eufy Security to latest release, and no effect on error.  Running 2022.12.7 (and don't think xx.8 has any Eufy security content).  Here's screenshot of error.  Have tried reloading multiple times.  Also - from above comments - have tried adding a different name in 'trusted device name' field - no change to error (I had a name in there anyway).  Any other ideas anyone ?  or @fuatakgun ??

Please see main thread in home assistant about open issues.

Can you help me - I don't understand where you are suggesting I look.  I clicked the link in home assistant "known issues" to get here... so where else should I look ?   can you provide a link or set of mouse clicks.... ?

Seeing the trusted device in the add on removes the error of the integration, but as others already pointed out, the integration doesn't provide any entities anymore

Setting the trusted device in the add on removes the error of the integration, but as others already pointed out, the integration doesn't provide any entities anymore

@kongo09 I have all entities back and working after adding the trusted device name. That change as well as restarting HA was the only things I did to fix all my Eufy devices in HA. I don't know why and how, all I know is that it did fix it in my case. I haven't rebooted or anything else since the change, as I'm awaiting further information regarding what the real issue and corresponding fix is.

Please see main thread in home assistant about open issues.

@fuatakgun Can you perhaps provide a link to this main thread? I'm unable to find any relevant open issues in the Home Assistant Github or 2022.12 changelog. Thanks.

That's interesting. I added the trusted devices and that made the integration error disappear. But in the add on log I still see errors and all entities are unavailable, with or without restart

@kongo09 I should rephrase my last message into: "I have all entities that I use in HA back and working". When I look at one of my Eufy devices in HA, all Controls and Sensors are working, while half of the entities within the Diagnostic section are "Unavailable" - but I don't know if they were also unavailable before the update.

I am also experiencing this issue. @fuatakgun you could attempt to be a little more helpful than to just say "Please see main thread in home assistant about open issues". like @kenni I also cannot find any reference to this issue in the "main thread".

Guys, on home assistant thread, on the main post, i had post 3 issues impacting everyone. Since these issues started i am receiving tons of emails, home assistant notifications and messages. I am one person here and you are many and instead of I am replying you one by one, you can follow the thread.
It is broken as of now, everywhere, se are waiting a solution from @bropat.
Many people had already explained the problem on home assistant, me repeating it won't add any value.
Similarly, commenting identical information to open issues wouldn't contribute too. Github have reactions, just put your reaction and let's wait all together.
Lastly, keep in mind that, this is a free time activity, no commitment from any party to either answer or solve the issues.

@fuatakgun I'm pretty sure everybody here understands that your great work on this is done in your free time. However some of your responses such as "see the main thread" are just unhelpful. It would take little effort to actually post a link to the main thread to make it easier for some people. Just saying...

Here it is: https://community.home-assistant.io/t/eufy-security-integration/318353?u=fuatakgun

Here it is: https://community.home-assistant.io/t/eufy-security-integration/318353?u=fuatakgun

That's helpful, thank you! This is the link we were all looking for. I had no clue either but now we get it 😊

It is broken as of now, everywhere, we are waiting a solution from @bropat.

I assume the URL is offline due to all the recent security articles. Eufy mentioned they were removed a significant number of browser based access points.

I think Bropat has fixed the issue.
Below the latest changelog https://github.com/bropat/eufy-security-client
2.4.0 (2022-12-24)
(bropat) Implemented new encrypted cloud API communication (v2)

Everyone, please uninstall previous version of addon, install the new version 1.3.0. It is very important to uninstall it because we need to get rid of previous login data which is not compatible anymore.
After installing and starting the add-on with new version, enable the integration. I jave confirmed that p2p, rtsp, motion detection are working fine.
This is about to fix login issues but not about missing thumbnails, so please set your expectations

Everyone, please uninstall previous version of addon, install the new version 1.3.0. It is very important to uninstall it because we need to get rid of previous login data which is not compatible anymore.
After installing and starting the add-on with new version, enable the integration. I jave confirmed that p2p, rtsp, motion detection are working fine.
This is about to fix login issues but not about missing thumbnails, so please set your expectations

Mines just updated and connected fine. I only use the door bell ringing notification. Do you recommend uninstalling and re-installing anyway?

I keep seeing this my add-on logs :
2022-12-25 17:46:25.885  INFO  Client disconnected with ip: <IP_ADDRESS> port: 53430 code: 1000 reason: Normal Closure
2022-12-25 17:47:06.363  ERROR Response data is missing
{
code: 0,
msg: 'Succeed.',
data: undefined
}
it does not matter what login & pwd I use, so it seems the add-on is not even trying to connect. What did I miss ?

it does not matter what login & pwd I use, so it seems the add-on is not even trying to connect. What did I miss ?

Similar message here:
2022-12-26 15:23:47.843  INFO  Eufy Security server listening on host <IP_ADDRESS>, port 3000
2022-12-26 15:23:48.009  ERROR Response data is missing
{
  code: 0,
  msg: 'Succeed.',
  data: undefined
}

I am still having problems with starting the Eufy Security add on.
Logs says its killed…
I have changed the Trusted_Device_Name many time with different stings but it still does not work.
Verizon is the latest (1.3.0).

Just wanted to confirm the integration is working for me now. I only am using it for my lock with wifi base station, however.

Just wanted to confirm the integration is working for me now. I only am using it for my lock with wifi base station, however.

Tried it again but still won’t work… is there any steps to fix it?
It was working up till yesterday

Same here - working for my wireless doorbell via WebRTC (entity:camer.doorbell)and C24 model via WebRTC and generic camera (setting either entity or rtsp URL), not able to connect to my three pan cam models however “ERROR: RTSP Client unauthorized 401”

https://github.com/fuatakgun/eufy_security/issues/588#issuecomment-1365477750


I cant visualize the output of an intermediate layer

when I try to visualize the output of an intermediate layer which is mentioned in http://keras.io/getting-started/faq/#how-can-i-visualize-the-output-of-an-intermediate-layer, I get a mistake
 I don‘t know what caused the problem. Maybe the instruction is not suitable for non-sequential model because it works well  on others' sequential model. Does any one encounter the same problem?

Are you sure you meant "get_3rd_layer_output = K.function([mode.layers[0].input], model.layers**[-1]**.output)"?
If that's not the problem, please show what you are trying to run.

@jonasrla Thank you for your answer.
Yes, you're right. I build a neural network, but the train loss, train accuracy, validate loss and validate accuracy are always unchanged. So I decided to use the function to see the output.
get_3rd_layer_output = K.function([model.layers[0].input],[model.layers[-1].output]); output = get_3rd_layer_output([X_train])[0];
But it still print the error, so I can't get this.
I build a two-input neural network. The output after merging these two network will be input into a CNN and then use Softmax to do classification.

I've already solved the problem. (●'◡'●) I use the wrong layer of my model.


Find in Project doesn't work in Google Drive File Stream folders

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Whenever I attempt to Find in Project on an Atom editor opened on a Google Drive File Stream (GDFS) folder, it fails to find anything.
Steps to Reproduce

Install GDFS
Put some files in it
Open Atom on the GDFS folder
Attempt to Find in Project for some text known to be in the files.

Expected behavior: Get a list of files containing the text.
Actual behavior: Get nothing
Reproduces how often: 100%
Versions
MacOS High Sierra: 10.13.5
Google Drive File Stream: 25.252.289.1612
Atom    : 1.28.1
Electron: 2.0.4
Chrome  : 61.0.3163.100
Node    : 8.9.3
Additional Information
I can move one of the folders out of GDFS and to any location on my disk and Find In Project works fine. Perhaps it has something to do with the fact that GDFS uses a Volume and performs some intelligent syncing. However, I have been able to confirm that the grep command works perfectly fine.

/move to atom/find-and-replace


Validate CRDs with a Validating Admission Controller

We need a kubebuilder webhook for validation logic.

/assign @ellis-bigelow

implemented by #45 (?)

Yep


dual display AKA multimon AKA dualmon support

Hello!,
Great job guys! I have a question, is dual display supported?
Grepping the code I can see support for it (multimon):
./xorg/X11R7.6/rdp/rdpup.c:static int g_do_multimon = 0; /* multimon - turn on or off */
./xorg/X11R7.6/rdp/rdpup.c:            LLOGLN(0, ("  client can do multimon"));
./xorg/X11R7.6/rdp/rdpup.c:            g_do_multimon = 1;
./xorg/X11R7.6/rdp/rdpup.c:            LLOGLN(0, ("  client can not do multimon"));
./xorg/X11R7.6/rdp/rdpup.c:            g_do_multimon = 0;
grep: ./xorgxrdp: Is a directory
grep: ./xrdp: Is a directory
./xrdp/xrdp.ini:allow_multimon=true
./xrdp/xrdp_login_wnd.c:        else if (g_strncmp(n, "allow_multimon", 64) == 0)
./xrdp/xrdp_login_wnd.c:            globals->allow_multimon = g_text2bool(v);
./xrdp/xrdp_login_wnd.c:    g_writeln("allow_multimon:          %d", globals->allow_multimon);
./xrdp/xrdp_login_wnd.c:    g_writeln("allow_multimon:          %d", globals->allow_multimon);
./xrdp/xrdp_types.h:    int  allow_multimon;

However I do not see any traces in /var/log/xrdp-sesman.log nor /var/log/xrdp.log suggesting that the client I am using to connect with (windows RDP client with multimon flag set) "can do multimon". Is there anything I should do get information about the multimon negotiation?
Thanks,

Nestor

Hello,
Multimon should work with Xorg driver for now.
X11rdp / xvnc not supporting dual mon for now.
בתאריך יום ד׳, 14 באוק׳ 2015 ב-23:17 מאת Nestor Urquiza <
<EMAIL_ADDRESS>
Hello!,
Great job guys! I have a question, is dual display supported?
Grepping the code I can see support for it (multimon):
./xorg/X11R7.6/rdp/rdpup.c:static int g_do_multimon = 0; /* multimon - turn on or off */
./xorg/X11R7.6/rdp/rdpup.c:            LLOGLN(0, ("  client can do multimon"));
./xorg/X11R7.6/rdp/rdpup.c:            g_do_multimon = 1;
./xorg/X11R7.6/rdp/rdpup.c:            LLOGLN(0, ("  client can not do multimon"));
./xorg/X11R7.6/rdp/rdpup.c:            g_do_multimon = 0;
grep: ./xorgxrdp: Is a directory
grep: ./xrdp: Is a directory
./xrdp/xrdp.ini:allow_multimon=true
./xrdp/xrdp_login_wnd.c:        else if (g_strncmp(n, "allow_multimon", 64) == 0)
./xrdp/xrdp_login_wnd.c:            globals->allow_multimon = g_text2bool(v);
./xrdp/xrdp_login_wnd.c:    g_writeln("allow_multimon:          %d", globals->allow_multimon);
./xrdp/xrdp_login_wnd.c:    g_writeln("allow_multimon:          %d", globals->allow_multimon);
./xrdp/xrdp_types.h:    int  allow_multimon;
However I do not see any traces in /var/log/xrdp-sesman.log nor
/var/log/xrdp.log suggesting that the client I am using to connect with
(windows RDP client with multimon flag set) "can do multimon". Is there
anything I should do get information about the multimon negotiation?
—
Reply to this email directly or view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/289.

Yes, as Speidy says, we only got it working in the Xorg driver.
It's really nice, you can connect from MSTSC in full screen and when you maximize apps in the session, they only maximize on the monitor, not the whole desktop.
It used RandR in X11.  The monitors show up as rdp0, rdp1, ...
This can be merged to X11rdp.
It was done first in Xorg driver because I thought we would need some of the monitor helper functions in the XFree86 libs but we didn't.

X11rdp is unfortunately the only option I have seen that works for ubuntu 14.04 (http://scarygliders.net/x11rdp-o-matic-information/). Any plans to do the merge into X11rdp? Thanks!

I am glad to see multi-monitor is in progress!
I am trying to test with Xorg but not having success.  I've got MSTSC configured for multiple monitors as well as in xrdp.ini.  What's a valid xorg.conf look like for dual monitors however?
Thanks!

Leaving it default will work.

Hmmm.  I always see "client can not do multimon" in the Xorg log.  If MSTSC has the checkbox selected to use all monitors & xrdp.ini has multimon enabled, where should I look first for the problem?

Hi,
Can you paste your xrdp output ?
בתאריך יום א׳, 10 באפר׳ 2016 ב-20:15 מאת coredump4<EMAIL_ADDRESS>
:

Hmmm. I always see "client can not do multimon" in the Xorg log. If MSTSC
has the checkbox selected to use all monitors & xrdp.ini has multimon
enabled, where should I look first for the problem?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/289#issuecomment-208019414

If I leave xrdp in the foreground, attached is what I get on the console when a multimon client connects.  The client connects through an SSH tunnel.
xrdp-no-daemon-console-output.txt

Rebuild xrdp with ./configure --enable-xrdpdebug and get the output of xrdp running in foreground.
It gives us more verbose log.
Like this.
processing monitors data, allow_multimon is 1
monitorCount= 2
got a monitor: left= 0, top= 0, right= 1919, bottom= 1199, is_primary?= 1
got a monitor: left= 1920, top= 0, right= 3519, bottom= 899, is_primary?= 0

Thanks for this tip.  I now see more detail logged to the console, but nothing having to do with the client's monitor configuration.  All I can see is "item allow_multimon value yes" as it parses the xrdp.ini.
I have LogLevel=DEBUG right now; is another value required to see the extra debugging output?

The multimon bits are in the Xorg driver but not X11rdp.  Some are there but not all.
Everything else is done(xrdp, libxrdp).
I'll merge them.

ok, in devel branch now with 473f3dc

I'd prefer to stick with Xorg if possible...

Ok, I think X11rdp is multimon ready now with 5e398e0
Of course, you need to use a desktop manager that is multimon aware.
I tested with xfce4 and ubuntu 14.04 amd64.

@metalefty what else could I try in order to get the extra debugging information?  I'd really like to see what Xrdp reports for monitorCount so I can make sure it and mstsc are agreeing on the configuration.

You've been built xrdp with --enable-xrdpdebug, right?
For example,
./configure --enable-xrdpdebug --enable-other-else-your-configuration
make && make install

and run xrdp and sesman with -ns flag.  You should be able to see very verbose logs.
With information you gave us so far, your xrdp setup looks already support multimon.
However, mstsc is not telling xrdp that have client can do multimon for some reasons.
Seeing verbose log with --enable-xrdpdebug will clarify that.

Yes, this is confirmed.  In the debug output, I can see in the "client mcs data received" dump, there's no CS_MONITOR PDU.  I'm investigating the client end of things now.

OK, I tracked down the cause.
In xrdp_iso.c, xrdp_iso_negotiate_security() sets rdpNegData=0 if the security protocol is rdp.  This causes xrdp_iso_send_cc() not to send a Connection Confirm PDU with the EXTENDED_CLIENT_DATA_SUPPORTED flag.  This was why my clients were not sending the CS_MONITOR PDU to the server.
For testing, I just forced rdpNegData=1 and it worked, but the real solution is probably a different test in xrdp_iso_send_cc() in order to de-couple setting ECDS from the security protocol.

Which rdp client do you use ? (What version?)
It seems like it doesn't do security layer negotiation
בתאריך יום ו׳, 22 באפר׳ 2016 ב-23:59 מאת coredump4<EMAIL_ADDRESS>
:

OK, I tracked down the cause.
In xrdp_iso.c, xrdp_iso_negotiate_security() sets rdpNegData=0 if the
security protocol is rdp. This causes xrdp_iso_send_cc() not to send a
Connection Confirm PDU with the EXTENDED_CLIENT_DATA_SUPPORTED flag. This
was why my clients were not sending the CS_MONITOR PDU to the server.
For testing, I just forced rdpNegData=1 and it worked, but the real
solution is probably a different test in xrdp_iso_send_cc() in order to
de-couple setting ECDS from the security protocol.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/289#issuecomment-213586669

There is a rdp file parameter called "security layer negotiation"
Look in "my documents\Default.rdp" if it's turned off
בתאריך שבת, 23 באפר׳ 2016 ב-0:23 מאת Idan Freiberg<EMAIL_ADDRESS>
Which rdp client do you use ? (What version?)
It seems like it doesn't do security layer negotiation
בתאריך יום ו׳, 22 באפר׳ 2016 ב-23:59 מאת coredump4 <
<EMAIL_ADDRESS>
OK, I tracked down the cause.
In xrdp_iso.c, xrdp_iso_negotiate_security() sets rdpNegData=0 if the
security protocol is rdp. This causes xrdp_iso_send_cc() not to send a
Connection Confirm PDU with the EXTENDED_CLIENT_DATA_SUPPORTED flag. This
was why my clients were not sending the CS_MONITOR PDU to the server.
For testing, I just forced rdpNegData=1 and it worked, but the real
solution is probably a different test in xrdp_iso_send_cc() in order to
de-couple setting ECDS from the security protocol.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/289#issuecomment-213586669

https://technet.microsoft.com/en-us/library/ff393719(v=ws.10).aspx
בתאריך שבת, 23 באפר׳ 2016 ב-0:25 מאת Idan Freiberg<EMAIL_ADDRESS>
There is a rdp file parameter called "security layer negotiation"
Look in "my documents\Default.rdp" if it's turned off
בתאריך שבת, 23 באפר׳ 2016 ב-0:23 מאת Idan Freiberg<EMAIL_ADDRESS>
Which rdp client do you use ? (What version?)
It seems like it doesn't do security layer negotiation
בתאריך יום ו׳, 22 באפר׳ 2016 ב-23:59 מאת coredump4 <
<EMAIL_ADDRESS>
OK, I tracked down the cause.
In xrdp_iso.c, xrdp_iso_negotiate_security() sets rdpNegData=0 if the
security protocol is rdp. This causes xrdp_iso_send_cc() not to send a
Connection Confirm PDU with the EXTENDED_CLIENT_DATA_SUPPORTED flag. This
was why my clients were not sending the CS_MONITOR PDU to the server.
For testing, I just forced rdpNegData=1 and it worked, but the real
solution is probably a different test in xrdp_iso_send_cc() in order to
de-couple setting ECDS from the security protocol.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/289#issuecomment-213586669

I'm using regular mstsc.exe, patched up to RDP 8.1.  I actually do have "negotiate security layer:i:1" in my config file.

Do non-xrdp RDP servers works with multimon for you ?
בתאריך שבת, 23 באפר׳ 2016 ב-0:38 מאת coredump4<EMAIL_ADDRESS>
I'm using regular mstsc.exe, patched up to RDP 8.1. I actually do have
"negotiate security layer:i:1" in my config file.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/289#issuecomment-213596367

Is it possible that you build the master branch? It seems broken in that
case.
Did you test devel branch ?
בתאריך שבת, 23 באפר׳ 2016 ב-1:49 מאת Idan Freiberg<EMAIL_ADDRESS>
Do non-xrdp RDP servers works with multimon for you ?
בתאריך שבת, 23 באפר׳ 2016 ב-0:38 מאת coredump4<EMAIL_ADDRESS>
I'm using regular mstsc.exe, patched up to RDP 8.1. I actually do have
"negotiate security layer:i:1" in my config file.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/289#issuecomment-213596367

Yes, multimon sessions are fine when connecting to Windows systems.  And sorry, I should've mentioned I was working with Master.

I can test Devel but I need stability...

That was a bug iv'e fixed a long time ago in devel branch.
Unfortunately we didn't merge it to master yet.
Anyway, I think you can cherry pick this change from devel.
On Sat, Apr 23, 2016 at 2:26 AM coredump4<EMAIL_ADDRESS>wrote:

I can test Devel but I need stability...
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/289#issuecomment-213623332

I've been testing Devel branch using multimon with Xorg, and so far, so good.
I've encountered one issue that's more nuisance than problem; I'll open a new issue for that.

Seems to be solved.


Fix minor typo in error message for missing imports

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


When closing a native window, we sometimes get a touch event related error

For example, this just appeared when closing a Playground:

fixed


Add a warning on non-test analysis w/o foundry_success checking

Related: https://github.com/runtimeverification/kontrol/issues/312
In Kontrol, we only check foundry_success predicate (and, therefore, report the test as failing) if the name of the test starts with test, check, or prove (https://github.com/runtimeverification/kontrol/pull/249). Once https://github.com/runtimeverification/kontrol/issues/312 is fixed, we'll be able to also check hevm_success predicate.
However, right now, if the test doesn't start from one of these three prefixes, it is being symbolically explored, but does not get reported as failing even if the test reverts. As reported by @dwightguth, it is confusing and looks like a bug, so we should probably emit a warning that informs the user that the test is not being checked for failures.

This is intended behavior though for methods without test_ prefix, so that the user can create a summary to be used in running other tests/functions (via the --include-summary ... option). So a warning seems too strong here, maybe some documentation, or an INFO log.


[QA] Goerli - Validate Player Authenticity (80, -8): wrong validations are taking place when interacting on scene and getting messages in both Alpha and old explorer

Explorer Alpha build version:
0.3.477-g5ad20358
Issue Description:
Validate Player Authenticity (80, -8): no proper validations are taking place when interacting on scene and getting messages  in both Alpha and old explorer
Always the negative message is displayed, even when this message shouldn't be triggered. Proper validations aren't taking place.
Notice this in Alpha:

Notice this also in old explorer:

Steps to reproduce:

Go to 80, -8 in goerli
Click to interact on scene

Expected behaviour:
Proper messages should be triggered when interacting on scene
Current behaviour:
Always negative message is triggered, even when it is not supposed to
Reproduction rate:

[ ] < 10%
[ ]  < = 25%
[ ]  50%
[ ]  < = 75%
[x ]  100%

Severity:

[ ] Cosmetic
[ ] Minor
[x ] Medium
[ ] High
[ ] Critical
[ ] Blocker

Priority:

[ ] High
[x ] Medium
[ ] Low

Platforms / OS:

[x ] Windows 11
[ ] Windows 10
[ ] Mac Sonoma
[ ] Mac (specify the version on Additional Notes)

@nearnshaw says we should ignore this scene for now.


Fix the url-map and backend creation conflict attempt 2

Related https://github.com/grpc/grpc/pull/26713.
In previous attempt, the BackendService URL was not returned but merely the BackendService's name. That wasn't sufficient to be used in the url-map body.
This PR moved any url-map content related  logic behind BackendService creation, and load the URL map directly from GCP API (this is needed to adapt Prod vs. Staging).
Manually tested with --strategy=keep.

Known failures: https://github.com/grpc/grpc/issues/26595


Backport 2.7: AES test dependencies and CMAC robustness

Backport of the test dependency fixes from #1331.
Manual testing done: make check in the default configuration minus MBEDTLS_AES_C and MBEDTLS_CTR_DRBG_C, and in the full configuration minus MBEDTLS_AES_C and MBEDTLS_CTR_DRBG_C.

The 2.7 branch has reached its end of life, so I am closing this pull request.


Adjust tree interfaces

Codecov Report

Merging #1099 (f45bb1c) into master (8281b8d) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #1099   +/-   ##
=======================================
  Coverage   47.08%   47.08%
=======================================
  Files         173      173
  Lines       13766    13766
=======================================
  Hits         6482     6482
- Misses       6447     6449    +2
+ Partials      837      835    -2

Impacted Files
Coverage Δ

graveler/committed/tree/apply.go
60.46% <0.00%> (ø)

config/logger.go
64.28% <0.00%> (-10.72%)
:arrow_down:

catalog/mvcc/cataloger_create_entry.go
94.73% <0.00%> (-5.27%)
:arrow_down:

pyramid/tier_fs.go
61.90% <0.00%> (+2.72%)
:arrow_up:

catalog/mvcc/cataloger_commit.go
80.00% <0.00%> (+2.85%)
:arrow_up:

catalog/mvcc/cataloger_create_repository.go
62.96% <0.00%> (+3.70%)
:arrow_up:

Continue to review full report at Codecov.

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


Update GeoWave CLI to be more user-friendly.

Coverage decreased (-0.8%) to 48.088% when pulling 5291cb6e2813787a256fa812a2f01b3dcd5c99d1 on jdgarrett:cli-revamp into cbc3d9545aa5d7cca25758ec121b8017a49d8335 on locationtech:master.


Update C++ Standard to C++20

Since the C++20 standard has been published in December 2020 piston should use it.
This could be as easy as changing -std=c++17 to -std++20 in https://github.com/engineer-man/piston/blob/0f8350b6da6786ae140e79806e1ff92d1047f3bd/lxc/executors/cpp#L4
but I'm not sure if the installed g++ compiler supports C++20

Just checked, GCC needs to be updated in order to do this

Just checked, GCC needs to be updated in order to do this

im going to assume this is solved in v3 since gcc is compiled from scratch and will likely be the latest version


Set stores from previous years to zero

Biomass and biogas is overestimated when doing myopic optimization. This is due to stores from previous time steps (years) being available in the subsequent ones. It seems that this is only an issue with regard to biomass+biogas, but as this is a more "general issue", I impose this change for all stores that are named with a year, e.g. "EU biogas-2030".

Hi @ebbekyhl @martavp  , thanks for spotting the bug! I think, the error was introduced by the new default values (PyPSA release 0.18) where the lifetime has a default value np.inf (previous default np.nan). When filtering which assets should be duplicated for each investment period in function add_build_year_to_new_assets (see here) it does not filter out anymore the biogas/biomass stores.
I guess it is better to filter for the new default values than setting all stores e_nom_opt to zero, since there are certain stores (like e.g. "H2 Stores") where you want to keep an asset for each investment period.
Could you check out the PR #217 if that would solve the problem as well?

Hi @lisazeyen,
Yes it works. Changing the "n/a" to "inf" in the lifetime attribute seemed to do the trick (y).


Forgot Password with JWT

[ ] Frontend
[x] Backend

hi, i would love to collaborate, if this issue is open, could you give a description of what needs to be done?

Hey @iamrahulrnair , Great to see you are interested in our project. Let me clarify what the problem statement is.
[ Description ] As of now in our app, there is no option to forget a password where if someone forgot password then they can't reset it. although there is a google option where you don't need any password. [ Technical Part ]  what we will do is we add one more column in the user modal for forgot password and we generate one tokenized link. That link will send via email ( NodeMailer) to users and when they click on the link they redirect one page with jwt argument where they can reset their password. also, we can modify further for JWT token valid for 48h/60h.
This is my approach, If you have a better approach in terms of security & User reliability then it would be appreciable!

This seems the standard approach, user clicks on link in mail with a valid time limit and redirects to a password reset page.
any constraints do i have to worry about like the token length and all?

Cool, Short token length will preferable.

is there any client side endpoint for reset_password? i mean if the user recieves the mail where should the user go when he clicks the link?

@iamrahulrnair There is no route for forgot passwords. You want to build this feature from scratch. If you need any help let me know.

Yeah the thing is after getting the private url in mail, the user need a view for typing  the password and confirm password, then checking that and the jwt payload only the user can continue further, i was asking about that endpoint,
:-)

@iamrahulrnair No there is not an endpoint, You can create reset_password/:JWT for filling password. After update the password, you need to redirect them to the /login route so that they can log in with a new password. Hope you got it.

hey @codewithvk , may i change the password hashing to a utility function, seems the code is repetitive and that too needed in the reset functionality, it will be better if this the case, lemme know your thought :-)

@iamrahulrnair Can describe broadly, What do you want to do?

Move To Jira 💯
Automated Close

@iamrahulrnair Can you please describe broadly? What do you want to do?
See in here the hashing is  reused everywhere like , importing bcryptjs and doing hashing, when code base gets larger it will get complicated, so its better to create a utility function which returns a hash when password is given, so we don't have worry about the hash length and all, now we don't have to worry about this, will raise another issue for code refactoring and have discussion on that. :-)

I am done with server code for reset functionality, will raise a PR now.

@iamrahulrnair Yup, You can create functions separately but functionality should be the same. And go ahead and rise a PR! 🥇

[ ]  Frontend
[x]  Backend

Hey, i will work on the front end :-)

Hey guys is this enough, since the feature is on low priority i haven't looked into it much  :-), and am not sure how the reset password page should be rendered, if a define a function component then everyone can access it right, so any idea how i should implement it?

am not sure how the reset password page should be rendered, if a define a function component then everyone can access it right

@iamrahulrnair According to me, You can create separate component for Reset Password, and anyone can access it.mentioned screen-shots looks good for me, I will be change some UI after Your PR merged.

am not sure how the reset password page should be rendered, if a define a function component then everyone can access it right, so any idea how i should implement it?

Hey, @iamrahulrnair . I am not getting your question? did you ask about render from loginpage.js? or something else.

since the feature is on low priority i haven't looked into it much

No worries brother, We are also busy in other stuff so that we can't do many contributions as of now :)

am not sure how the reset password page should be rendered, if a define a function component then everyone can access it right, so any idea how i should implement it?

Hey, @iamrahulrnair . I am not getting your question? did you ask about render from loginpage.js? or something else.

No, After clicking on the link in mail, the user should go to a reset page, how should i render that page? What are things that i should consider ? If it is public everyone can access the route like '/reset_password/:JWT_KEY' , should i continue with this approach?

@iamrahulrnair You can make it public no worries Because we handle update password conditions by the backend. You can create /reset_password for sending the password to email and '/reset_password/:JWT for reset password and update. Hope you got my point.


Fix detecting an existing Map/Set

This didn't affect compilation to CJS since that sets exports.Map
instead of creating a global.

The point of the declare const Map on the preceding line is to force the lookup of Map to look at the globally scoped Map (rather than ts.Map due to namespace merging). How did this become an error for CJS emit?

The problem is not in the CJS output.  If I set module to es6, the resulting code is:
var NativeCollections;
(function (NativeCollections) {
    function tryGetNativeMap() {
        return typeof Map !== "undefined" && ...;
    }
    ...
})(NativeCollections || (NativeCollections = {}));
export var Map = getCollectionImplementation("Map", "tryGetNativeMap", "createMapShim");
```

@rbuckton, does that make sense?


[Feat] Floor Controls  |  AdvancedMarkers & Building Floors

Target Use Case
Creating/Viewing custom Advanced Markers spread across a multi-floor buildings like SFO Airport, San Francisco Centre Mall, etc.
Proposal
Currently using { lat, lng } to place markers at specific coordinates but do not have access to Floor controls.
Adding the ability to access Floor Controls (like how zoom, street view, etc. currently exist) would be very useful and potentially as an added feature to the AdvancedMarker an optional floor value.
It looks like the Floor Controls feature exists on iOS & Android so adding this accessibility to Web only seems natural.

I would love to see that as well, but as of now, there is no way to control the indoor-maps in the Maps JavaScript API.
Looking at the map, it seems that it will already correctly show the ground-level of a building that has indoor-maps instead of the outer shape of the building, but there is no way to control the level.
The issue for that is 12 years old by now and has >130 upvotes (which is a lot): https://issuetracker.google.com/issues/35819848


Code might actually be doing something.

I tried to run this, and then windows 10 restarted so that it could update. I have not been able to reproduce this, but the coincidental timing makes me believe this code might have caused the update.

I've get that error and i fix it with this lines

This is actually a valid point, (I guess).  In some languages writing nothing actually does something


"prefix" not found

when we are try to use,
import Textify from "textify.js;

const alternatesAnimations = new Textify({
    selector: ".dynamic_text"
});

console make error like :
ERROR in ./node_modules/textify.js/src/components/Animation.js 1:0-28
Module not found: Error: can't resolve 'prefix' in "D:\works.............................
```"

update, devDependecies or reCheck src's all js file

thanks for the inform bug, we start working on it...

prefix not found
or
can't resolve prefix
both error come in next.js

prefix not found  or
can't resolve prefix
both error come in next.js

working on this !!!!

prefix not found  or
can't resolve prefix
both error come in next.js

download prefix dependency in your project and restart your web-servers. may that works

prefix not found  or
can't resolve prefix
both error come in next.js

download prefix dependency in your project and restart your web-servers. may that works

it's work, but all time we can't use it like this way.
that error make big trouble for next.js project

error was fixed... :100:


proper root device mapping for eks worker

Should this work?

EKS images are /dev/xvda, Amazon scripts refer to root device via /dev/xvda literal. Se no reason to overengineer.


Create test.yml

Test action

Hi @zickau ! I guess we can remove this PR, right? It is anyway based on the old version of the repo (before the history re-write to add sign-off comments). Please open a new one based on the current version if necessary.


Create TMP Tables issue fix

Signed-off-by: alfredlu<EMAIL_ADDRESS>
What problem does this PR solve?
Parser related fix for tidb#28530
What is changed and how it works?
Create Tmp Table should be DB level
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to be included in the release note

/cc @morgo

/merge


Allow viewing issues and PRs that match a rule

I should be able to view a list of issues and pull requests that match each rule -- see #2. Clicking an issue or PR should take me to its page on github.com.

I was thinking about having a static "mentions me" rule to start and using this issue to start implementing the redux store.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 990 ms

Resolved: Bofrost.at performance has improved in a9772bd.


[MM-14571] Add e2e to test @mentions notifications

Summary

Added e2e test to test at-mention notification
Add plugin to cypress to use Mattermost Client4 for sending messages from other users
Added id to unread mentions badge, updated snapshot
Added axios package for use in Cypress plugin, updated package-lock.json

Ticket Link
JIRA Ticket
Fixes https://github.com/mattermost/mattermost-server/issues/10441
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed

Something I'm still playing with is the usage of the Client4. Ideally, I'd like to get an instance of it inside the tests themselves so we can do something like the following (which does not work):
cy.task('getClient4', {user}).then(async (client4) => {
            await client4.createPost({
                channel_id: channelId,
                message,
                type: '',
            })
        })

or
cy.task('getClient4', {user}).as('Client4');
        cy.get('@Client4').invoke('createPost', {
            channel_id: channelId,
            message,
            type: '',
        });

That said, what is in this PR works for now :)

@thekiiingbob re: Client4 that sounds a good plan.  However, I'm more incline to directly connect to API via cy.request. I'll submit some of those, probably next week.

@saturninoabril Done with the requested changes!


how to use in unbuntu,i build in unbuntu ， i put the URL in windows browser and I can’t find the visual interface。

You need to start a web server (using python for example) in the viewer folder:
python -m http.server
Then you can access the URL.

Hi @yuqilol ,
If the screenshot you shared is what you see in the browser, then just select reconstruction.json and press Submit.
If you have problems with the viewer, take a look at this issue #829
Good luck,
Fabian

Or is it because the web page dependencies are not installed?


Cluster dns should survive etcd restart

We can either give dns etcd its own volume or restart kube2sky as well so it repopulates records if the  etcd restarts @thockin @ArtfulCoder

I believe if we give etcd container an emptydir in the podspec, then a restart should give etcd the same dir again. If this is true , it should be a 5 line fix in the pod spec.

Yeah, I think an emptyDir is exactly the right fit.  Abhishek, do you have
time?
On Wed, Jul 8, 2015 at 9:20 AM, Abhi Shah<EMAIL_ADDRESS>wrote:

I believe if we give etcd container an emptydir in the podspec, then a
restart should give etcd the same dir again. If this is true , it should be
a 5 line fix in the pod spec.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/10926#issuecomment-119646548
.

sure, I will do it.

Dawn is helping out. Thanks Dawn!

Dawn, do you actually have time for this?

I will do it by tomorrow.

Feel free to assign it to me, I already have it tested locally for my other change

This needs to be in ASAP  Like before 10am
On Thu, Jul 9, 2015 at 7:24 PM, Prashanth B<EMAIL_ADDRESS>wrote:

Feel free to assign it to me, I already have it tested locally for my
other change
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/10926#issuecomment-120204952
.

No priority on this one.  p1?

P1 assigned, fix is in flight.

IIUC - #11055 was a fix for this. Can we close this issue now?

This is fixed.


Fix relative path being relative to install location and not requesting file

Given the following project layout:
projectA/
  node_modules/
    include/
    projectB/
      src/
        index.js
  src/
    index.js

If projectB also uses include to include file relative to the project root, when evaluating include, projectB will use projectA's root instead since npm installs the common module at the top-most level instead of each child directory. As a result, all calls to include pull from the root of the top-most instead of the one for the calling file.
Since no method exists to determine the path of the requesting file from within the module, the path must be provided up front. While some other solutions attempt to do this, they rely on static passing of ../../../../ et cetera into the function returned by the require (i.e., require-root).
This could be resolved by allowing include to function like the following:
var include = require("include")(__dirname);

var data = include("fixtures/data");
var method = include("src/method");

Hey @jlmorgan thanks for bringing this up - It has been a while since I looked at this project and it's about time to bring it up to speed with everything else going on with the Node / NPM world as of late.
I could totally be wrong, but I think NPM 3 in Node 5 has flattened out the module directory structure, so something like this is necessary to get everything rewired correctly. I'm going to take a look into things later this afternoon and possibly write some tests against it to make sure things are working as desired.
Expect further communication and / or merging your pull request in later. Thanks again for your contribution!

Sure thing. We use this extensively in our projects at work for all project references.

Sorry for the delay in getting around to this - between a birthday and Blizzcon, I have been super busy and distracted. I'll be updating things this week!


Makefile: fix inconsistent builds and help running scripts locally

I hope this fixes failing PR tests as there was an inconsistent use of yarn and npm ?!

making this consistent makes sense I guess, but the real problem seems to be known upstream
https://github.com/cmfcmf/docusaurus-search-local/issues/214#issuecomment-2286192361
which can be avoided like done in this PR - not using yarn at all ;-) )


make Token[Token[String]] just Token[String]

Coverage decreased (-0.2%) to 52.562% when pulling da5567fa1e7317d4275e5f668bfcf7b5a803a3ab on tylersouthwick:fix-api-gateway into fa05312a8e2725cd29090e60669610060b804c97 on MonsantoCo:master.

Coverage decreased (-0.2%) to 52.562% when pulling db4e6aac06e3384455d6a3c4a41ffee566c3f9f8 on tylersouthwick:fix-api-gateway into fa05312a8e2725cd29090e60669610060b804c97 on MonsantoCo:master.


NavigationDrawerCategory does not support subheaders

The initial implementation does not include them.

Made irrelevant when NavigationDrawerCategory was done away with NavDrawer rework in 12f428d.
Users are recommended to roll their own OneLineListItem.


Jest not running tests in src/node_modules

Bug Report
What is the current behavior?
Jest reports "No tests found" even when there are tests
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal repository on GitHub that we can npm install and npm test.
Example repo.
What is the expected behavior?
Tests in src/node_modules are run
Run Jest again with --debug and provide the full configuration it prints. Please mention your node and npm version and operating system.
jest version = 16.0.2
test framework = jasmine2
config = {
  "moduleFileExtensions": [
    "jsx",
    "js",
    "json"
  ],
  "moduleNameMapper": [
    [
      "^.+\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$",
      "/Users/justinfalcone/work/modernserf/test-jest/config/jest/FileStub.js"
    ],
    [
      "^.+\\.css$",
      "/Users/justinfalcone/work/modernserf/test-jest/config/jest/CSSStub.js"
    ]
  ],
  "setupFiles": [
    "/Users/justinfalcone/work/modernserf/test-jest/config/polyfills.js"
  ],
  "testPathIgnorePatterns": [
    "/Users/justinfalcone/work/modernserf/test-jest/(build|config|node_modules)/"
  ],
  "preprocessorIgnorePatterns": [
    "/Users/justinfalcone/work/modernserf/test-jest/node_modules"
  ],
  "testEnvironment": "/Users/justinfalcone/work/modernserf/test-jest/node_modules/jest-environment-jsdom/build/index.js",
  "rootDir": "/Users/justinfalcone/work/modernserf/test-jest",
  "name": "-Users-justinfalcone-work-modernserf-test-jest",
  "testRunner": "/Users/justinfalcone/work/modernserf/test-jest/node_modules/jest-jasmine2/build/index.js",
  "scriptPreprocessor": "/Users/justinfalcone/work/modernserf/test-jest/node_modules/babel-jest/build/index.js",
  "usesBabelJest": true,
  "automock": false,
  "bail": false,
  "browser": false,
  "cacheDirectory": "/var/folders/q8/zlh7b1ms7fg2r3cqx6sgbrrr0000gn/T/jest",
  "clearMocks": false,
  "coveragePathIgnorePatterns": [
    "/node_modules/"
  ],
  "coverageReporters": [
    "json",
    "text",
    "lcov",
    "clover"
  ],
  "globals": {},
  "haste": {
    "providesModuleNodeModules": []
  },
  "mocksPattern": "__mocks__",
  "moduleDirectories": [
    "node_modules"
  ],
  "modulePathIgnorePatterns": [],
  "noStackTrace": false,
  "notify": false,
  "preset": null,
  "resetModules": false,
  "testPathDirs": [
    "/Users/justinfalcone/work/modernserf/test-jest"
  ],
  "testRegex": "(/__tests__/.*|\\.(test|spec))\\.jsx?$",
  "testURL": "about:blank",
  "timers": "real",
  "useStderr": false,
  "verbose": null,
  "watch": false,
  "cache": true,
  "watchman": true,
  "testcheckOptions": {
    "times": 100,
    "maxSize": 200
  }
}
No tests found
  12 files checked.
  testPathDirs: /Users/justinfalcone/work/modernserf/test-jest - 12 matches
  testRegex: (/__tests__/.*|\.(test|spec))\.jsx?$ - 0 matches
  testPathIgnorePatterns: /Users/justinfalcone/work/modernserf/test-jest/(build|config|node_modules)/ - 5 matches

Node v6.5.0
npm v3.10.3
See https://github.com/facebookincubator/create-react-app/issues/1042 and https://github.com/facebookincubator/create-react-app/issues/607 for related issues.

I think this is the offending section: https://github.com/facebook/jest/blob/cd4d97b30d73dbb2350dc77a409e39d8b8caca90/packages/jest-haste-map/src/index.js#L681-L692

Hey @modernserf
I ran into the same issue and adding the following to my Jest config helped.
For Jest v0.17.4 all you seem to need is:
"testPathIgnorePatterns": ["<rootDir>/node_modules"]

before that I had to use:
  "haste": {
    "providesModuleNodeModules": [".*"]
  }

Yes, Jest excludes node_modules by default. You can adjust testPathIgnorePatterns for your use case: http://facebook.github.io/jest/docs/configuration.html#testpathignorepatterns-array-string
@shanewilson's configuration option should not be used for this.

@cpojer did you look at the example repo? I'm using
  "testPathIgnorePatterns": [
    "<rootDir>/(build|config|node_modules)/"
  ]

and its still ignoring src/node_modules.

I believe this is because haste ignores files in all node_modules directories, so files in src/node_modules don't even make it to where testPathIgnorePatterns is used

Ahh, I'm sorry, yeah you are right! I didn't realize this before, but yes, what @shanewilson says should work for now. I believe to fix this without changing the "haste" config, you'd have to turn this switch to true: https://github.com/facebook/jest/blob/master/packages/jest-haste-map/src/index.js#L207 – if @shanewilson's workaround doesn't work, can you try turning this option to true and reporting back? If that works, we can probably expose it as well as part of the "haste" object – you could send a PR for that :)
I also encourage you to give lerna a try: https://github.com/lerna/lerna – it has worked really well for us!
Are you using Jest at Buzzfeed?

Thanks! -- the haste config works for now, as does manually setting retainAllFiles, though when I was testing this earlier it seemed like that was generating a lot of warnings? I'll try this out again and report back.
Regarding BuzzFeed: Each team has a fair amount of control over their own stack, but many of the newer internal tools (including the ones I work on) are using React/Jest/Webpack/Babel; some of our prototypes are even built with create-react-app.

Ok I see, yeah that makes sense. I encourage you to just go with @shanewilson's workaround then.
Also, cool that you are using Jest! :)

Discussion continued here: https://github.com/facebookincubator/create-react-app/pull/1081#issuecomment-264351297

Related, you need to make sure that files in ./src/node_modules are processed:
I had the same issue, as I'm trying to use ./src/node_modules for internal libs.
Fix:
// .jestrc
 "transformIgnorePatterns": [
    "<rootDir>/(node_modules)/"
  ]

The default regex should have <rootDir> in it:

https://github.com/facebook/jest/blob/e6495647112781b98ff194fe34952a8139f045df/packages/jest-validate/src/__tests__/fixtures/jestConfig.js#L16

Here is an example repo that demonstrates https://github.com/kirkstrobeck/jest-issue-5039

Original CRA issue was closed, because using src/node_modules is not a standard that community is embracing. Shall we close this as well or do something about it?

I have a problem with that too.
We have a package core, which is used by 6 other packages as a framework. core has its own jest tests, but each packageX (where X is from 1 to 6) also has its own test. We want to yarn add --dev each package to our core package, and run all pacakgeX tests in our core CI. So, we could be sure, we didnt break any backward compatibility for any of packageX.
Not sure how "standard" that approach is, but packageX tests are located in node_modules (of course).

This issue prevents some decoupling that proves useful when building integration tests that can be shared across multiple of my node services.
The approach I took was to write my integration tests in a new project, and npm install it into each service that would use it, placing the jest installation along with the relevant tests into each respective node_modules folder. Sadly jest refuses to locate any of the tests since node_modules would always exist in the directory path of its parent directory.
The work around I have in place requires rsyncing the installation out of node_modules, which isn't ideal.

It would be really nice to have this supported properly. For me neither the workaround nor any other suggestion made it working. :roll_eyes:
What I'm trying to do:
having directory tree
+ monorepo root
| + apps
  | - app1
  | - app2
  | + node_modules
    | + a-package
       | - package.json
       | - index.js
       | - a-test-for-index.test.js

a-package.json
{
  ...
  scripts: {
    test: "jest"
  },
  "dependencies": {
    ....
  },
  "devDependencies": {
    "jest": "^24.7.1",
     ....
   }
}

running jest
what I do simply:
$ cd monorepo-root/apps/node_modules/a-package
$ npm run test

results

No tests found, exiting with code 1

results using the workaround
set as part of a-package/package.json jest config
...
  "devDependencies": {
    "jest": "^24.7.1",
     ...
  },
  "jest": {
    "haste": {
      "providesModuleNodeModules": [".*"]
    }
  }
...

... a lot of jest-haste-map warnings ...
jest-haste-map: Haste module naming collision: source-map
The following files share their name; please adjust your hasteImpl:

/node_modules/snapdragon/node_modules/source-map/package.json
/node_modules/source-map/package.json

No tests found, exiting with code 1

results using the workaround & testPathIgnorePatterns
ie I have the following jest config within a-package/package.json:
...
  "devDependencies": {
    "jest": "^24.7.1",
     ....
  },
  "jest": {
    "testPathIgnorePatterns": ["<rootDir>/(node_modules)/"],
    "haste": {
      "providesModuleNodeModules": [".*"]
    }
  }
...

Still without any luck. This time the test has been found and properly loaded however:

FAIL a-test-for-index.test.js
● Test suite failed to run
The name source-map was looked up in the Haste module map. It cannot be resolved, because there exists several different files, or packages, that provide a module for that particular name and platform. The platform is generic (no extension). You must delete or blacklist files until there remains only one of these:
  * `...{full path removed privacy<EMAIL_ADDRESS>(package)
  * `...{full path removed privacy<EMAIL_ADDRESS>(package)
  * `...{full path removed privacy concerns}.../node_modules/snapdragon/node_modules/source-map/package.json` (package)
 * `...{full path removed privacy concerns}.../node_modules/source-map/package.json` (package)

 at ModuleMap._assertNoDuplicates (node_modules/jest-haste-map/build/ModuleMap.js:280:11)

Test Suites: 1 failed, 1 total

I'm reporting all the above just to add more context/info on the problem and its possible cause. I have a ton of dependencies within a-package.json (obviously omitted) and seems jest-haste-map gets confused :)
why
I'm sharing common modules across apps within a monorepo and I cant use symlinks to do the job (thus Lerna isnt an option). The native nodejs require/resolve process works just fine for directory trees as described above, thus I'm able to require/import common modules into apps without 'magic' tricks.
All fine until the point which I needed some tests for the common modules of mine which of course are placed within the common modules rendering them under node_modules path which seems is causing problems.
what I think I need
Jest to be able to run as it runs normally - excluding ./node_modules subdirectory relative to the current working directory and be able to do that when the path of the current working directory contains 'node_modules' in it :)

Adding all of these items to my jest.config.js apears to be working for me:
module.exports = {
  haste: {
    providesModuleNodeModules: ['.*']
  },
  testPathIgnorePatterns: ['<rootDir>/node_modules/'],
  transformIgnorePatterns: ['<rootDir>/node_modules/'],
  modulePathIgnorePatterns: ['<rootDir>/node_modules/']
};

Not working on 26.0.1, even with mentioned workarounds.
It seems that haste field is deprecated now and thus Jest refuses to run tests correctly.
Is there any plans to fix this?
It is very strange that Jest ignores tests when the package is places inside node_modules. I think it would be better to check if the test is placed inside the local node_modules rather than just checking if the path includes it.

To work around it now, I made a wrapper file:
const Runtime = require('jest-runtime');

const origCreateHasteMap = Runtime.createHasteMap;

Runtime.createHasteMap = function(...args) {
  const ret = origCreateHasteMap.call(this, ...args);
  ret._options.retainAllFiles = true;
  return ret;
};

module.exports = require('jest/bin/jest');

And I run that file instead of the main Jest executable. I'd much rather have a config option if the maintainers are amenable to a pull request...

xandris solution works fine, but I would like to know, if this is a bug and this suppose to work in near future or these tests are excluded by design.

xandris solution works fine, but I would like to know, if this is a bug and this suppose to work in near future or these tests are excluded by design.

@kuka-radovan I stopped using that style of monorepo and now recommend npm 7 or yarn workspaces to do inter-module linking rather than relying on the node_modules resolution quirk. As far as Jest is concerned, maybe it shouldn't make assumptions about node_modules directories. There could be a default heuristic, and Jest could allow the user to override it, but I don't think it's worth the effort given the alternatives. 🤷♀

The workaround is use is creating a JS file.
const  { default: HasteMap } = require("jest-haste-map");

class CustomHasteMap extends HasteMap {
  _ignore(filePath) {
    const ignorePattern = this._options.ignorePattern;
    const ignoreMatched =
      ignorePattern instanceof RegExp
        ? ignorePattern.test(filePath)
        : ignorePattern && ignorePattern(filePath);
    return ignoreMatched;
  }
}

module.exports = CustomHasteMap;

Then I configure haste.hasteMapModulePath to point to that file. (As well as set testPathIgnorePatterns to empty array.)

https://github.com/facebook/jest/releases/tag/v28.0.0-alpha.5


Colours are incorrect

Hello,
It seems to have a problem for the colours in the css:
What I should have

What I got:

Even if I'm using either of the three theme files.

Latest version: 2.1.9

The cache has been removed -- the code is not even cached --, the plugins is loaded properly as indicated in linked you have provided, as we are using the same code in both development environments, but the problem is not fixed.
However, in the first image I have sent, the version 2.1.6 is used:

and in the second image, it is the version 2.1.9:

I cannot reproduce this issue.
Maybe mixed styles with your page styles.
elFinder version? I only tested with the latest elfinder, theme should be compatible with the older elfinder, but I didn't test it.
Any additional screenshot?
The problem is manifested only in a light theme?

The version of elFinder is 2.1.49, the latest one.

The problem is manisfested only when i'm usign any of themes from "RobiNN1/elFinder-Material-Theme"

Did you edit CSS?
That looks like mixed light/gray theme together or not properly loaded css.
// Use options themes and theme. In setting you can toggle theme
themes : {
    // You can specify a manifest.
    default : 'https://cdn.jsdelivr.net/gh/RobiNN1/elFinder-Material-Theme/manifests/material-default.json',
    gray : 'https://cdn.jsdelivr.net/gh/RobiNN1/elFinder-Material-Theme/manifests/material-gray.json',
    light : 'https://cdn.jsdelivr.net/gh/RobiNN1/elFinder-Material-Theme/manifests/material-light.json',
},
theme : 'default',

// or load theme directly with cssAutoLoad option
cssAutoLoad: ["themes/Material/css/theme.min.css"],

Yes I did, I used cssAutoLoad option, but it doesn't work

Got it. It's elFinder issue.
Default elfinder theme must be loaded first and then own theme.

Thanks
I will wait for elFinder update

I also had this issue today updating to elFinder v2.1.49
The fix appears to work (putting in a bind on 'cssloaded').
Thank you.


Block IO Aligned Buffers

Add a flags field inside bdev_t
Allow devices to mark themselves as requiring cache aligned buffers
[STM32F7 Spiflash] require cache aligned buffers
[STM32F7 Spiflash] use default implementation for bio_read
Don't allocate on the stack for bio dump since this blows the stack

looks pretty good, with a few nits and assuming it passes tests.

LGTM

Merged.


Update LICENSE & NOTICE

The major code change in the UI(#5684) removed all the bundled
javascript/css files. This change removed bunch of copied js/css files
but the pr did not correctly address the license.
This PR is the effort for cleaning up licenses.

Cleaned up LICENSE, LICENSE-binary
Cleaned up licenses/, licenses-binary/
Cleaned up NOTICE-binary

#6785

@felixcheung @olamy @kishoreg
Pinot mentors, can you review the license change above? Thank you!

Codecov Report

Merging #6944 (9082a02) into master (9becc57) will decrease coverage by 8.03%.
The diff coverage is 45.30%.

:exclamation: Current head 9082a02 differs from pull request most recent head 71db3be. Consider uploading reports for the commit 71db3be to get more accurate results

@@             Coverage Diff              @@
##             master    #6944      +/-   ##
============================================
- Coverage     73.41%   65.37%   -8.04%
  Complexity       12       12
============================================
  Files          1431     1432       +1
  Lines         70689    70854     +165
  Branches      10232    10258      +26
============================================
- Hits          51897    46322    -5575
- Misses        15344    21203    +5859
+ Partials       3448     3329     -119

Flag
Coverage Δ
Complexity Δ

integration
?
?

unittests
65.37% <45.30%> (-0.07%)
12.00 <0.00> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Add Azure pipeline definition

Add a build pipeline definition for moving the build from CircleCI to Azure Devops.
Microsoft Reviewers: Open in CodeFlow

Never mind, looks like I have to do the branch creation via ADO.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Fix paging by using Continuation Object

At the moment the inlinecount gets queried to calculate the amount of pages. Furthermore the paging is implemented so that for every page the next X entries (X is the page size and is configurable) get loaded. Since the pageabke entity filter is active the UI has to honour the OData next link instead of implementing a "static" paging. With the pageable entity filter it's not possible to get the inlinecount. Because of that the paging has to be modified to not show all pages in the navigation anymore but for exaple only two navigation buttons like previous and next.

@oliverluethi this one has highest prio

@rufer7 @dfch Implemented paging for PageEntityFilter for all views. This has to be tested carefully with sample data for every scenario (Searching, Nodes, Permissions, Paging, AjaxPaging).
But first, Appclusive.Core has to be changed that every controller implements PageEntityFilter or at least every controller which Application.UI needs.
Keep in mind that the attribute [EnableQuery(PageSize = Constants.ODATA_ENABLEQUERY_PAGESIZE)] has to be removed when using PageEntityFilter in Appclusive.Core, because it executes the query with the changed OData url at the very end of the pipeline.

@rufer7 how is the progress here? might this be a future task for @stevenpi ?

@dfch this is already implemented but not yet merged as we first have to switch to the PageableEntityFilter in every controller. See comment above

@rufer7 ok, thx for the clarification


Boolean operator complexity

I believe Boolean operators aren’t being counted correctly. The paper states each similar operator sequence should increment the expression complexity by 1.
It seems like the implementation here will increment per operator usage regardless of whether it’s on a chain. So if I understood the paper idea:
a && b && c +1
a && b +1
but currently crate gives a higher n# for the first.
I’ll reproduce and give a better definition/look into a fix.

Invalid issue; this is correctly handled


chore: connect mv downloads 2 - LESQ-84

Description
-Connects downloads mv 2
-Fixes no unitvariant programe factor programes

List of changes

How to test

Go to https://deploy-preview-1747--oak-web-application.netlify.thenational.academy

/beta/teachers-2023/programmes/history-secondary-ks4-aqa/units/historic-environment-normans/lessons/lesson-35-in-historic-environment-normans/downloads
/beta/teachers-2023/programmes/english-secondary-ks4-aqa/units/power-and-conflict-poetry/lessons/lesson-26-in-romeo-and-juliet-part-1/downloads
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner

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


Starting / Ending whitespace now being sent to Interactive Window

Pretty sure this was not the case before.
Noticed it as I usually put a space between cells, and now a one line cell will get a ... with an expander which can be expanded to show and extra line. On the interactive window I've run a cell with empty lines before and after a print statement.

The main issue is resolve, but the trimming seems to have a side effect.
The following source example:

Both create a cell with only one line. But the line has an expander, and when you press the expanded it doesn't show anything more:

Moving back to backlog, but we could also close and open a new issue.

Validated the cleanup fix.


Add descriptions to NodeNorm

Some descriptions are now being generated in Babel (https://github.com/TranslatorSRI/Babel/issues/109). We should add support for ingesting descriptions into the Redis database behind NodeNorm, and then presenting them in the API.

@YaphetKG has implemented this, and it's up and running on RENCI Dev (e.g. https://nodenormalization-sri.renci.org/1.4/get_normalized_nodes?curie=MESH%3AD014867&curie=NCIT%3AC34373&conflate=true&drug_chemical_conflate=false&description=true). Closing.


Homepage items Display

This branch introduces the following features:

Homepage items displayed from API.
display of the comments button.
display of like button and like count without functionality

Hi @Obimbo07
Your project is complete!  There is nothing else to say other than... It's time to merge it 👍
STATUS: APPROVED 🟢
Congratulations! 🎉
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me @tasnimchy96   in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Unable to run UI console for OLM

When running latest run_console_local.sh get the following error
$ ./run_console_local.sh
latest: Pulling from openshift/origin-console
Digest: sha256:ade20a34050642da950275a88a096c4e3f057119a96a939755f3a4f0d44285a6
Status: Image is up to date for quay.io/openshift/origin-console:latest
Using https://<IP_ADDRESS>:8001
Unable to run the console locally. May this port is in usage already.
Check if the OLM is not accessible via web console at: https://localhost:9000/.
If I revert back to prior version of  run_console_local.sh, git commit 37a12b9855e758e83eb537ebb7b0337067af713d from Sept 5th, it works fine.
@camilamacedo86

Hi @jdockter,
I am not sure why you ping me. However, did you Check if the OLM is not accessible via web console at: https://localhost:9000/. already?
I am not able to face any problem with male run-console-local

Ah okay the documentation I had, which I can't seem to find now, didn't have the use of a make command.  Everything is working fine now, thanks.


[Performance] Store State always returns a new reference

The useStoreState(state => state.nodes) returns a new reference on every render. I am trying to implement grouping behaviour where a node needs to access "sibling" nodes.
"That's fine, I can just do a nodes.filter() and memoize it..."
Except because the reference is new on every render, the memoization runs on every render :(.
I understand that this may be due to the underlying state management, but for now I'm having to use crude workarounds to not have it update on every render.

I might have to open a separate issue for this, but it would be even better if the Elements were stored in a Map with index by the provided id. This would when fetching specific nodes we don't need to loop through the entire list each and every time a la:nodes.find(n => n.id === id).
If there's anything I can do to assist with this, please let me know. Willing to assist and contribute under guidance.

Hey @justrhysism
thanks for the input! We are also not super happy with the element state handling right now.
We will look into other possibilities and if a Map works for us.

@moklick I've had a couple of iterations with grouping. Originally I was manually shifting each node with updateNodePosDiff. See: https://codesandbox.io/s/magical-heisenberg-nty4i
However, that broke when upgrading to v7, so I switched to a (much simpler) method of adding all the nodes of the group to the selection via addSelectedElements when the group is "selected".
With respect to how I was grouping, I just pass (via data) a parentId for the "parent" node, and the "parent" node has an array of ids for it's children.

The other feature I've had to disable for performance reasons is the resizing of the group node (see above codesandbox, and drag around the nodes within a group). As the tree grew, the number of loops, and the length of the loops got longer resulting in some sort of Big O notated issue I can't be bothered to figure out—but it slowed down a lot.
Obviously I'm pushing the boundaries outside of the original design intentions, so for now I've just disabled some of those features.

Hey!
This looks pretty impressive! We will think about how we can make it easier to implement things like custom grouping.
Do you have an idea what you need in order to simplify the grouping?
We changed the updateNodePosDiff so that all selected elements get updated (we need that for the multi selection).

@moklick to be honest, I don't really have an opinion on an "easy" grouping method. I am quite happy to handle it myself, but yeah as stated on the outset, the issue I have is with the new array reference on every render. I thought it might be just because it's computed, but unfortunately, when I switched to using the elements directly I had the same issue.

We changed the updateNodePosDiff so that all selected elements get updated (we need that for the multi selection).

Yeah that makes sense. As I mentioned, I found a workaround by adding all the "siblings" to the selected elements so the group is moved "natively" with respect to the library.
It was a little annoying, but it was a breaking change haha, so all good 😄

We split up elements into nodes and edges in the new v10 but we will stay with arrays.


[wrt] Update manual test steps for coreshell

Impacted TCs num(approved): New 0, Update 5, Delete 0
Unit test Platform: Android
Android test result summary: Pass 5, Fail 0, Block 0

LGTM