drivers: i2c: stm32 driver V2 new timing calculation

This PR is implementing a new formula to calculate the I2C timing value from the I2C clock source and the bit rate.
Algorithm coming from https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_STM/i2c_api.c
Fixes https://github.com/zephyrproject-rtos/zephyr/issues/55535
Signed-off-by: Francois Ramu<EMAIL_ADDRESS>

stm32 I2C V2 FAST bitrate

stm32 I2C V2 STANDARD bitrate

Fixing compilation errors

a second commit, to fix the compliance check warning and retrieve the original (correct) function

Rebase, fix macro to get the same timing value
STANDARD : 0xb0c03e40
FAST : 0xc041090f

Please cleanup second commit message. Otherwsie LGTM

done

Add a sample to calculate the I2C V2 timing value and then report to the I2C node in the Device Tree
The i2C V2 driver do not embed the timing calculation code.
Only when the CONFIG_I2C_STM32_V2_TIMING=y is set by the samples/boards/stm32/i2c_V2_timing/  is the timing value output on the console.
Rebase on 68365d5b67057c8e960a5168c2cf99f4b8c457c1

Includes the https://github.com/zephyrproject-rtos/zephyr/pull/64422
Change the sample

rebase on 482416db01e5b8d3e8b91c52bb9daa6eb3d8cddd
after merge of https://github.com/zephyrproject-rtos/zephyr/pull/64422

Running the samples/boards/stm32/i2c_config/ on the b_u585i_iot02a :
*** Booting Zephyr OS build zephyr-v3.5.0-785-g6d149c663d59 ***
I2C timing value, report to the DTS :
timings = <160000000 I2C_BITRATE_FAST  0xC041090F>;
I2C config: I2C_BITRATE_FAST

I'am curious what happened to this merge request ? This will fix error https://github.com/zephyrproject-rtos/zephyr/issues/55535.

@erwango should have been assinged

rebase on<PHONE_NUMBER>ff7394f9004457ade321d7fc3bf240
Renaming the samples"I2C timing"
Availability is I2C V2 only,  setting CONFIG_I2C_STM32_V2_TIMING=y in the prj.conf

@gautierg-st PTAL

Needs CI fixes

rebase on 2efc447c1b41efd23447ea180731d673114f06d8
Version with LOG_INF instead of printk in the driver
--> change the  sample.yaml
--> add the LOG_INF to the prj.conf
*** Booting Zephyr OS build v3.6.0-5746-ge94cfcf43a1c ***
[00:00:09.192,000] <inf> i2c_ll_stm32: I2C timing value, report to the DTS :
[00:00:09.192,000] <inf> i2c_ll_stm32: timings = <32000000 I2C_BITRATE_FAST 0xB01626>;
I2C freq. I2C_BITRATE_FAST


event.pointing not filled

The container event.pointing does not seem to be filled when reading simtel files.
I might take care of it later but I can't right now.
from ctapipe.io import event_source
from ctapipe.utils import get_dataset

source = event_source(get_dataset('gamma_test_large.simtel.gz'))
event = next(iter(source))
event.pointing[0].altitude, event.pointing[0].azimuth

returns
(<Quantity nan rad>, <Quantity nan rad>)

Probably we need to rethink this anyhow, since events do not have pointing information, rather each telescope does (and there is no guarantee all telescopes point in the same direction). Therefore, we should only store the pointing per telescope.

I see, you are right, this is certainly not where pointing should be stored.
Then maybe plainly removing this container would be better, it is a bit confusing to users I think.

I'll close this -I added another issue to remove the pointing structure, as suggested


Changes to make capture resolution adjustable

Per your request, camera resolution is now set using raspiCamCvSetCaptureProperty.
Important: I have not been able to test this because of a fried Pi, so please try this out once before you pull. Sorry! As far as I can tell, everything should work great, but my hardware's out of commission at the moment so I can't verify it myself.

PR https://github.com/robidouille/robidouille/pull/13 which has been merged to master made capture resolution configurable


Start-PSBootstrap failure doesn't fail the CI step

In https://github.com/PowerShell/PowerShell/pull/15548 and https://github.com/PowerShell/PowerShell/pull/15491, Start-PSBootstrap fails but does not cause the particular CI step to fail. Instead the next step fails in a less specified way, since its failure is due to the bad state from the previous step.
We should fix the build task so that a failure in Start-PSBootstrap causes its own build step to fail.

Maintainer review:   could not find the repro, so closing this until new occurrence happens.

I think this can be closed because the issue lies with the AZ/GH PowerShell action step.  See https://github.com/Azure/powershell/issues/39


Gephi Importing

Using https://github.com/Yomguithereal/gexf

Alternately https://github.com/raphv/gexf-js?


Inspect args fix

Block number and rpc are now correctly listed as separate arguments.  Added shorthands for optional args as well i.e., -b for --block-num

had updated the inspect specific poetry script call but a more general pass through to docker script is preferred.


It would be nice to update the title of move dialog from 'Move Files' dialog to 'Move'

Storage Explorer Version: 1.15.0-dev
Build: 20200804.6
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Expand one ADLS Gen2 storage account -> Blob Containers.
Create one blob container -> Upload one file to the blob container.
Create a new folder.
Select the uploaded file and the created folder -> Click 'Move' button.
Check the title of the popped dialog.

Expect Experience:
It would be nice to display 'Move' as the title.
Actual Experience:
Display 'Move Files' as the title.

Won't fixing.


state for inputValue is already defaulted correctly and does not need…

… to get dateTime.
My use case is as follows
I have 2 datepickers on the same page.  They default to defaultText = 'Select date.'
If I change the date for the first date picker, the 2nd will show today's date instead of continuing to show 'Select date.'  This pull request fixes that.
Thanks,
Theresa

If your 2 datepicker's props depend on different props / state using one shouldn't impact the other one. I think your issue is that they are couple.
Also by removing the line you're removing, what happens when an higher order component of the DateTimeField changes it's dateTime prop ? Then the input wouldn't get updated.

I have modified the example to show the use case.
I think two things that are confusing are

if defaultText is defined, then if a date is not selected, shouldn't defaultText take precedence over dateTime
because dateTime has a default value (ie moment().format("x")), then you can't really tell if it was empty or not

If you select a date in the first date picker, then the second will show today's date.

Hrmm, I just loaded your PR, ran npm run examples  and I don't get that behavior : https://www.dropbox.com/s/nupzqetkbyl154b/PR87.mov?dl=0
also I slighlty modified the code and added a test that shows why updating inputValue on componentWillReceiveProps is important : https://github.com/quri/react-bootstrap-datetimepicker/commit/8468f024922ccfc20ef491e50a67b8e045ae756a

I can see where you're coming from regarding the confusing part though, that's a reason why i'm trying to slowly add tests and enhance documentation so that we can spot check the expected behavior.

In my PR, it also includes the fix, so you won't see the behavior I described (my bad).
Just take out the following line from componentsWillReceiveProps, or I can update the PR if you prefer.
inputValue: moment(nextProps.dateTime, nextProps.format, true).format(nextProps.inputFormat)
I agree and appreciate your comment on tests and docs.  Your test should work with my change as well.

I'm closing this PR, and creating a new one with a test to demonstrate the issue.


Reuse MediaRecorder when recording several videos

Hello,
According to the documentation about MediaRecorder:

Once recording is stopped, you will have to configure it again as if it has just been constructed.

This does not seem to be the case in Camera2Video. As far as I understand, the MediaRecorder object is not configured again each time after stop() and before start().
Am I missing something?
Thanks!
Best regards,
Chao

Thanks for flagging this. What I think you are missing is that the recorder is being configured every time before recording begins. Here's where that happens: https://github.com/android/camera-samples/blob/9c9c581d43d6e1239d80a2f449ef678d5042b2c5/Camera2Video/app/src/main/java/com/example/android/camera2/video/fragments/CameraFragment.kt#L270
Since the app exits the activity after recording finishes, the recorder is disposed and never reused because the recorder will be recreated when a new activity is created.

@owahltinez do you have an example where recorder is reused without closing activity? Preferable even without closing preview session?


Actions.pop() with data is not working

Action.Actionname(data) is working but Actions.pop(data) is not working.
Here is my code
      <RedButton
        style={styles.buttonStyle}
        buttonTextStyle={styles.buttonTextStyle}
        onPress = { () => Actions.pop({ refresh: {data: 'dads'}}) }
        >
        Add
      </RedButton>

I have added lot of life cycles methods in parent screen and added log inside them but non of them are getting called.

    componentWillUpdate() {
      console.log('componentWillUpdate');
    }

    componentWillMount(){
        console.log('componentWillMount');
    }

    componentWillUnmount(){
      console.log('componentWillUnmount');
    }

    componentWillReceiveProps(nextProps){
      console.log(nextProps);
    }

I am not even getting undefined. There is no reflection in debug console.
Please check might be the issue with React Native updates. I am using following dependencies.
"dependencies": {
    "react": "16.0.0-alpha.12",
    "react-native": "^0.46.3",
    "react-native-router-flux": "^4.0.0-beta.12"
  }

Thanks, I will add it to 'migration' section. Use Actions.pop();Actions.refresh({..})

Actions.pop();Actions.refresh({..}) this is work around only right?

Actually it is not workaround but much better syntax. v3 just was not able to support it.

However it is not difficult to add old syntax for backward compatibility. Feel free to submit PR.

In navigationStore.js the pop is written like this
 pop = () => {
    this.dispatch(NavigationActions.back());
  };

It is even not taking any params. Is it the cause of this problem?

Is this fix live now?

Yes, master branch. Will publish beta.13 soon.


HTTP probe failed with statuscode: 500 Back-off restarting failed container

Hi having this yaml file
https://github.com/politrons/Akka/blob/master/CloudState/src/main/resources/cloudstate.yaml
And this Main and EntityService class
https://github.com/politrons/Akka/tree/master/CloudState/src/main/java/io/cloudstate/shopping
Once that I create a Docker image and I publish in my docker hub, when I deploy using command
kubectl apply -n cloudstate -f src/main/resources/cloudstate.yaml
When I see in Kubernetest Dashboard,  my shopping-cart-deployment  fail with error
Readiness probe failed: HTTP probe failed with statuscode: 500
Back-off restarting failed container

Any idea what could be wrong?
Those are the events that I can see in Kubernetes
Successfully assigned cloudstate/shopping-cart-deployment-6764bdd9f9-5nc2n to docker-desktop
default-scheduler
-
1
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC
Pulling image "politrons/shopping-cart:latest"
kubelet docker-desktop
spec.containers{user-container}
3
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC
Successfully pulled image "politrons/shopping-cart:latest"
kubelet docker-desktop
spec.containers{user-container}
3
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC
Created container user-container
kubelet docker-desktop
spec.containers{user-container}
2
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC
Started container user-container
kubelet docker-desktop
spec.containers{user-container}
2
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC
Container image "cloudstateio/cloudstate-proxy-native-no-journal:0.4.3" already present on machine
kubelet docker-desktop
spec.containers{akka-sidecar}
1
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC
Created container akka-sidecar
kubelet docker-desktop
spec.containers{akka-sidecar}
1
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC
Started container akka-sidecar
kubelet docker-desktop
spec.containers{akka-sidecar}
1
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC
warning
Readiness probe failed: HTTP probe failed with statuscode: 500
kubelet docker-desktop
spec.containers{akka-sidecar}
149
2019-10-28T21:29 UTC
2019-10-28T21:34 UTC
warning
Back-off restarting failed container
kubelet docker-desktop
spec.containers{user-container}
2
2019-10-28T21:29 UTC
2019-10-28T21:29 UTC

Regrds

Cheked the logs?

If you mean the console logs when I run the Kubectl, everything is fine, and said that operators and service were created successful. Sorry I’m new in k8s so if there’s any other logs that I can paste here from the k8s dashboard let me know.
I’m using the yaml version 4.3 could you check in the link that I pasted if everything is fine?
Thanks a lot

@politrons See the conversation here: https://gitter.im/CloudState-IO/community?at=5db7fd2714d55a3785966c84


Ability to customize serving paths

Polymer starter kit is laid out like

app/

elements/

my-element.html

bower_components/

The default server is configured with bower_components served over HTTP as though it were inside of the app directory. As a result, the HTML imports in my-element only go up by one ../ but polylint can't find any files at e.g. app/bower_components/polymer/polymer.html.
It would be useful if we could specify how the directories in the filesystem will be served out over HTTP. Simple strawman:
.polylintrc
{
  "servingPaths": {
    "/bower_components/": "./bower_components/",
    "/": "./app/"
  }
}

+1

+2

I would rather configure Bower where /bower_components/ should be located:
.bowerrc
{
  "directory": "app/bower_components"
}

resulting in
├── app
│   ├── bower_components
│   ├── elements
│   │   ├── my-element.html

Discussed here earlier this year: PolymerElements/polymer-starter-kit#635
Still need to upgrade my project to check, but this was probably fixed late last year when bower_components was moved into app to make vulcanizing easier: PolymerElements/polymer-starter-kit#568.


add mysql install step to contrib doc

this was needed to get past a bundle install error

- Create and seed database
`rake db:setup`

I'm assuming the above rake command is ran as part of rake setup...this is just a subset if the only thing you need to do is setup the db?  It doesn't run for me because:
Database 'alonetone_development' already exists which is why I'm thinking that.
if so, I think this step could probably be removed from the contrib.

dev env setup success!

if so, I think this step could probably be removed from the contrib.

You are right rake db:setup is redundant!

if so, I think this step could probably be removed from the contrib.

You are right rake db:setup is redundant!

removed

thanks for the feedback, I added those.


Improve contributors charts

In many projects only maintainer(s) has rights to merge. Which means for each contribution there will be +1 merge commit by a maintainer. Often it produces strange results that don't reflect the reality.
I see 2 options:

Remove merge commits from current charts
Keep current charts but add similar charts without merge commits

I believe the first option is better to make the charts less distorted.
The query we currently have for "Number of contributors per email" and "Email wordcloud" is
SELECT committer_email, COUNT(*) as n
FROM commits
WHERE committer_email <><EMAIL_ADDRESS>GROUP BY committer_email
ORDER BY n DESC

To exclude merge commits from the query we should exclude commits with 2 parents (that's what marks a merge commit on gitbase)
So, the new query would be
SELECT committer_email, COUNT(*) as n
FROM commits
WHERE committer_email <><EMAIL_ADDRESS>AND ARRAY_LENGTH(commit_parents) < 2
GROUP BY committer_email
ORDER BY n DESC

I analyzed the results for bblfsh and src-d repos and found out that the majority of merge commits are done under<EMAIL_ADDRESS>but this doesn't mean that the same happens for other organizations. I believe the addition of this conditional WHERE [...] AND ARRAY_LENGTH(commit_parents) < 2 is great to avoid duplicities on commits that are both commits and merge commits.

@gomesfernanda actually it is better to use author_email for this charts. The name of the chart is Number of contributors not Number of committers.

So we should change the queries to:
For "Number of contributions per organization" and "Organization wordcloud"
SELECT REPLACE(JSON_EXTRACT(SPLIT(commit_author_email, '@'), '$[1]'),'"', '') as domain, COUNT(*) as n
FROM commits
WHERE commit_author_email LIKE '%%@%%' and commit_author_email NOT LIKE<EMAIL_ADDRESS>AND ARRAY_LENGTH(commit_parents) < 2
GROUP BY domain
ORDER BY n DESC

For "Number of contributions per email" and "Email wordcloud"
SELECT commit_author_email, COUNT(*) as n
FROM commits
WHERE commit_author_email <><EMAIL_ADDRESS>AND ARRAY_LENGTH(commit_parents) < 2
GROUP BY commit_author_email
ORDER BY n DESC

Is it ok? And we're changing the "Row limit" parameter on the UI to 50 (following discussion on #195) on all charts for better visualization purposes.

I updated the charts with queries above but without filtering github out. There shouldn't be any<EMAIL_ADDRESS>as authors (only committers) and removing github domain isn't correct too. People from github do a lot of open source.


⚠ PrivateHD has degraded performance

In 72bce67, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 3377 ms

Resolved: PrivateHD performance has improved in a423c72.


Added UI toggles, Local Storage functionality, remove text option

Also supersedes #48

Tested this, works properly (all options do what they are supposed to) and options box fits in screen as it should.


FFMPEG not found

Bug description
When building a project using WebGL it does not install ffmpeg
How to reproduce
Build a project with an Audio File targeting WebGL then search the logs for 'ffmpeg' it will say it's not found
Expected behavior
Ffmpeg to be installed
Additional details

GitHub actions CI:

From a quick look at the /editor/Dockerfile I believe the problem is within the [webgl] section
The grep -v 'webgl' should be grep -v WebGL I think as that is the case required by the unity-builder script.

https://github.com/game-ci/docker/blob/a0c1017d01fa11c9c9adc277f750bac0a578b047/editor/Dockerfile#L162-L170
I'm not sure the grep -v 'webgl' is the bug here. the module used here is the one from the image name and not what is provided by unity itself.
Truth is this was solved in https://github.com/game-ci/docker/pull/89
It's just not released yet ;) It will be part of version 0.11.
https://github.com/game-ci/docker/releases

I'm closing this, but once 0.11 is out, if it still doesn't work, don't hesitate to open a new issue. Also make sure you have a wonderful day 🙌

Ah thank you for the quick response!

V0.11 fixed it! Thanks! :smile: :fire:


Bug: fix windows paths

See this bug report: https://github.com/metarhia/metarhia.com/issues/105

OS: Windows X
Node.js version 15.x
Impress version 2.x

Problem: path.sep === '\\' in windows

Problem: path.sep === '\\' in windows


Update quickjs-jni.cpp

Added missing macro

Hmm why wasn't this failing in the tests? How can we prevent this in the future?

It might be compiler issue. I use msvc instad of gcc.

Thankfully these methods shouldn't change much so I guess it's not worth worrying about figuring out some kind of validation of this at this time.


Changes to introduction

Modify the text and resources in the Get Started Page to be more relevant.
Add Quickstart guide link to Download page.
Remove line "Grin does not support nor endorse any of the listed projects" from Download page. (Grin itself can't endorse nor support anything).
Change home page link to the Mimblewimble introduction in the new docs.

Also there is merge conflict to fix too.


Simplifying WP Invocation

Currently, if a user wants to run WP on a pair of binaries, they have to perform multiple steps:

Save each binary project using the save_project pass. If the binary contains a symbol table, they should specify no-byteweight.
Invoke WP while specifying the .bpj files via the file1 and file2 flags.

This makes it difficult to get started on running WP. We should figure out a way to use BAP such that:

We don't need to save the projects anymore, or have a wrapper around saving the projects
The user only needs to go through one step when invoking WP

Closed with #220


CFE_FS_Decompress infinite loop on truncated gzip file

If CFS_FS_Decompress is given a truncated gzip file, it will enter an infinite loop in which it attempts to read more data from the file, gets nothing, and tries again. Discovered by accidentally attempting to have ES load a new compressed application (which we didn't know had been truncated), which led to ES getting stuck and an eventual watchdog reset.
The problem seems to be that running out of bytes in a gzipped file before decompression is finished is not considered an error. I can see how this might be intentional if it is expected that the file handle might be a stream that could present data after being emptied, but for the normal file use case I think it is a bug. Suggested fix by combining the two checks at line 309 of cfe_fs_decompress.c:
if ( State->insize == 0 ) return EOF;
if ( len == OS_FS_ERROR )
{
State->Error = CFE_FS_GZIP_READ_ERROR;
return EOF;
}
into one:
if ((State->insize == 0) !|| (len == OS_FS_ERROR)) {
State->Error = CFE_FS_GZIP_READ_ERROR;
return EOF;
}
Recommend investigation if insize might temporarily hit 0 during a normal decompression.
Reported via email from Mike Stewart<EMAIL_ADDRESS>

Imported from trac issue 267.  Created by jhageman on 2019-03-26T11:07:06, last modified: 2019-07-03T12:48:08

Trac comment by jhageman on 2019-07-03 12:48:08:
Moved unfinished 6.6.1 issues to next minor release

Hi, Mike here! I can't send the file that originally caused this problem for us (EAR...) but I've made another one that causes the same issue. Starting with this image:

If I compress and the truncate the image as follows:
gzip corgi.jpg
dd if=corgi.jpg.gz of=corgi2.jpg.gz bs=2048 count=1

This gives me this file: corgi2.jpg.gz
If I uplink this to our flight computer and then try to extract it via FM_DECOMPRESS, ES_START_APP, etc., whatever app tries to do the decompression gets stuck in an infinite loop.
Let me know if this file is able to reproduce it for you!

Won't fix, deprecated


upgrade aws-ebs-csi-controller to 1.0.0

Replaces #212

38a04a9 addresses test failure

but we should fix the kubebench checks properly  in #186

Because of the way that we apply the configs here kubectl apply it looks like this change will leave behind a number of service accounts that are removed or renamed, perhaps we need to mention them in the upgrade notes.

Because of the way that we apply the configs here with kubectl apply it looks like this change will leave behind a number of service accounts that are removed or renamed, perhaps we need to mention them in the upgrade notes.

Ah thanks good point - I'll add to the notes on the release


Add new file

dd

#sign-off

:warning: PRMerger: Sign off requires successful build

You signed off, but the build has not completed or there are outstanding validation warnings. Please wait for the build to complete, and address any outstanding validation warnings. Then, you can sign off on the pull request.


Feature request: --date column

As I love trashy output I need sometimes more specific time when I put file/folder in trash.  If two days ago something was deleted, then what time it was exactly?
---------------------------------------------------------------------
|  i  | Time            |  Date             |     Path              │
|-----|-----------------|-------------------|-----------------------|
|  2  | 2 days ago      | 2022/09/13 16:45  |  /home/user/blablabla |
|  1  | 2 days ago      | 2022/09/13 16:40  |  /home/user/blablabla |
|  0  | 43 minutes ago  | 2022/09/15 12:01  |  /home/user/blebleble |
---------------------------------------------------------------------

This seems pretty useful. I wonder if we could add an option to choose how preciese the Time column is. For example, something like --time precise or --time imprecise


No bug, just feedback

Hi,
beside that bug #633 i've reported earlier today i'm quite happy using restic now.
We manage about 25 servers that actually need a backup, most of our server don't have application-data that needed to be backed up, and they can bei re-bootstraped within minutes.
We used to use the backup-gem, which seems to be quite popular in the chef-world.
It does full-backups every time.
We managed, in the same infrastructure, to get our first backup done 25 times faster with restic than with the backup gem.
Followup-backups, depending on the amount of changed date again 10 to 20 times faster.
Thank you.

you should consider open sourcing your chef integration code for restic, might be useful for others too

I've thought about that today.
At the Moment the integration takes some shortcuts, matching our environment, and some dirty-ones too.
The dirty-ones will be fixed soon for sure.
I'm not sure about the company-open-source-policy, but i will investigate.

Great, thanks for the feedback! The restore process at the moment is single-threaded and therefore quite slow, although it seems that this is already fast enough for you ;)
"Incremental" backups will be much faster once there's a client-side metadata cache...

The measured timings are for backup, not restore.
we had only one accident that needed restore in the last 3 years, so restore-performance only really affects the restore-tests which are also automatically.
Also, restoring the backup-gem way is faster than backup, since you can pipe things together, but its far from fast. So, everything is fine :)

Yeah, for smaller restores (just a few files or dirs) you can also use the fuse mount, I don't know if you've discovered that already, but it's really handy!

Yes, that's what i've checked first after i've discovered #633 to prove the repository is integer.
That's really sweet, a fast way to see what that file looked like last week.

While speaking of fuse-mount, is there a way to get the folder-name somewhere near the output of restic snapshots? having multiple directories with different schedules in one repository and to have only timestamps as identifier is hard :)

If you have a good idea on how to improve the structure of the fuse mounted directories, please feel free to open an issue! At the moment I don't have a good idea ;) It's just a matter of implementing it.

i'm not sure either, maybe something like
$host/$directory/timestamp,
but that would imply replacing / with something else or getting confused if there are backups that are subfolders of another.
like
/var
and /var/www
that would result in
/myhost/var/timestamp
and
/myhost/var/www/timestamp
so having $timestamp AND www in /var/
Having a format-string for fusemount on the other hand seems like a overkill.
That's why i've asked, maybe someone else had a brilliant idea beforehand.

Thanks for the suggestions. It also bugs me that the fuse mount is a rather ugly list of timestamps, so I'm looking for ideas to improve thaht.

At the very least, tags (as lexicographically-sorted list) could be added to the name structure, like this: tag1,tag2,tag3:timestamp (possibly replace the semicolon with something for better compatibility).

Let's continue this in #636, please add your ideas there.


Running the code with pre-train step gives lower performance

Running the pre-train code results in lower accuracy.
Running python R-GMM-VGAE/main_cora.py  with the supplied model.pk gives
100% 199/200 [01:01<00:00,  3.70it/s]ACC=0.750369, f1_macro=0.729495, precision_macro=0.750872, recall_macro=0.746598, f1_micro=0.750369, precision_micro=0.750369, recall_micro=0.750369, NMI=0.554135, ADJ_RAND_SCORE=0.551637
However, if I try to do my own pre-training  ( by adding
def pretrain(self, adj, features, adj_label, y, weight_tensor, norm, epochs, lr, save_path, dataset):         ........         torch.save( self.state_dict(), save_path + dataset + '/pretrain/model.pk' )
I seem to be getting lower performance as shown below.
Loss=14.6272
100% 199/200 [01:10<00:00,  3.67it/s]ACC=0.658050, f1_macro=0.617192, precision_macro=0.625855, recall_macro=0.623322, f1_micro=0.658050, precision_micro=0.658050, recall_micro=0.658050, NMI=0.488975, ADJ_RAND_SCORE=0.465233
Whats the process to produce my own model.pk ?

The pretraining phase is very important for reproducing the article results. So, I generally select the best accuracy during pretraining, similar to previous methods. For Cora, I get an accuracy around 69% as a pretraining result. You may have to repeat the pretraining phase 2 or  3 times.  I also make sure that R-GMM-VGAE and GMM-VGAE use the same pretraining file for fairness of comparison.
if acc > acc_best:
   acc_best = acc
   torch.save(self.state_dict(), save_path + dataset + '/pretrain/model_' + str(self.m) + '.pk')

Thank you for the clarification.
I am still a bit confused how you would compute the acc. DO you use the labels? Wouldn't that mean you need annotations to obtain the optimal model during pre train?
Perhaps you can share your full pretrain model creation code. This may clarify the approach.

Previous methods use this technique to select the best pretraining results, so it was necessary to use the same technique to reproduce the results of GMM-VGAE for example. Added to that, the labels are not used for performing pretraining, which is vanilla reconstruction. But, we can use the labels to select when to stop the pretraining phase, instead of repeating the pretraining phase several times and taking the best result. Nothing wrong with that. This technique is commonplace and is used by most if not all graph auto-encoder models that I have seen.
Furthermore, the aim of this work is not to beat the sota results. It is rather to show  the trade-off between FR and FD, and the experiments are conducted in a way that both models (R-GMM-VGAE and GMM-VGAE) start from the same pretraining level. I am already sharing the pretraining code, you can add the provided two lines to save the best pretraining weights, that's all.