Semihosting

Replace the semihosting console implementation with a faster one, taken from #9864 and updated to work with the latest master.
~This one also has the ability to provide everything semihosting handles in the future if needed.~ not anymore, simplified so it's not bloated.

@stephanosio Ah, it wasn't mentioned anywhere in the previous PR.
In this case I'll check if simply using SYS_WRITE0 will suffice - it would make the code much shorter and simpler since it won't use any files.

@stephanosio fyi I updated this PR to be more in line with what you asked about.

cc @atx @LuoZhongYao

What is the status of this MR?
The improvements in https://github.com/zephyrproject-rtos/zephyr/pull/9864#issuecomment-634273224 really look great!
Would it be possible to also get this working on a real board (eg. a nucleo STM32)?

Ping
p.s. needs a rebase :)

@stephanosio ping received, rebased and fixed + responded :p

@stephanosio ping

When using the timer, there may be a kernel crash, the log cannot be output, and it may even cause a second crash.

@LuoZhongYao huh, I'll try to figure something out, but if you have any suggestions let me know.


Issues I encountered while replicating

Hi there! Thank you for this great work! I am trying to replicate the main result of the paper (0.372 AP using UTAE with the vegetation features only). I encountered a few issues I thought would be helpful to share here:

When trying to convert the downloaded data from .tif to .hdf5 using CreateHDF5Dataset.py, dataset = FireSpreadDataset() requires specifying a tuple for stats_years, which I set to (2018, 2020). While this is not used anyway here, it is needed to instantiate the FireSpreadDataset object.
Under get_generator_for_hdf5(), lnglat = ds.lnglat() crashes with error code:
rasterio.errors.CRSError: The EPSG code is unknown. PROJ: internal_proj_create_from_database: /home/sl636/miniconda3/share/proj/proj.db lacks DATABASE.LAYOUT.VERSION.MAJOR / DATABASE.LAYOUT.VERSION.MINOR metadata. It comes from another PROJ installation.
I installed rasterio using the requirements.txt file and tried reinstalling it and updating it, but I still faced the same error.
To the best of my knowledge, no .yaml file under the cfgs folder includes a script to replicate the main result experiment. As such, I made the following changes:

a. all_features.yaml:

data:   features_to_keep:       - [0, 1, 2, 3, 4, 38, 39] # VIIRS observations + NDVI + EVI2

b. data_monotemporal_full_features:

n_leading_observations: 5 features_to_keep: [0, 1, 2, 3, 4, 38, 39]

c. trainer_single_gpu.yaml:

strategy: ddp devices: NUM_GPUS sync_batchnorm: true

If these files match the configuration used to train the winning model, it might be helpful to add them (and the others used for the experiments in Table 5) to the repository.

When setting do_test to True, the script crashes inside on_test_epoch_end() on line 260 in src/models/BaseModel.py when it tries to do fig, ax = self.test_pr_curve.plot(score=True) with AttributeError: 'BinaryPrecisionRecallCurve' object has no attribute 'plot'. I fixed it by replacing that line with precision, recall, thresholds = self.test_pr_curve.compute(), moving the tensors to CPU and then plotting them using matplotlib.

Many thanks again!

Thanks for the effort, and sorry for the late answer, it seems like I'm not receiving email notifications for this repo.

When trying to convert the downloaded data from .tif to .hdf5 using CreateHDF5Dataset.py, dataset = FireSpreadDataset() requires specifying a tuple for stats_years, which I set to (2018, 2020). While this is not used anyway here, it is needed to instantiate the FireSpreadDataset object.

stats_years was introduced after I write that script, that's why it's missing here. Has been fixed now.

Under get_generator_for_hdf5(), lnglat = ds.lnglat() crashes with error code:
rasterio.errors.CRSError: The EPSG code is unknown. PROJ: internal_proj_create_from_database: /home/sl636/miniconda3/share/proj/proj.db lacks DATABASE.LAYOUT.VERSION.MAJOR / DATABASE.LAYOUT.VERSION.MINOR metadata. It comes from another PROJ installation.
I installed rasterio using the requirements.txt file and tried reinstalling it and updating it, but I still faced the same error.

I used a fresh install with requirements.txt to test this and it does work for me without any error. I assume that either your or my local environment has some side effects that we aren't aware of and causes this issue. I would guess it's your environment, because your error message says:

It comes from another PROJ installation.

Maybe there's a different package that installs PROJ and interferes?

To the best of my knowledge, no .yaml file under the cfgs folder includes a script to replicate the main result experiment. As such, I made the following changes:

For Logistic Regression,  ConvLSTM and UTAE, the wandb sweep configs for table 5 were called wandb_cross_val.yaml and were already in the repository. I renamed them to wandb_table5.yaml, which should make it a lot easier to identify what they're for.
For the UNet, I added the respective file with the same naming scheme. I also renamed the ablations configs to the tables that they are represented by in the paper. I hope that makes it easier to figure out which numbers come from where.

When setting do_test to True, the script crashes inside on_test_epoch_end() on line 260 in src/models/BaseModel.py when it tries to do fig, ax = self.test_pr_curve.plot(score=True) with AttributeError: 'BinaryPrecisionRecallCurve' object has no attribute 'plot'. I fixed it by replacing that line with precision, recall, thresholds = self.test_pr_curve.compute(), moving the tensors to CPU and then plotting them using matplotlib.

This seems to be an issue with torchmetrics versioning. I updated the requirements.txt to use a newer version, and with a small update to the code, it now successfully logs the image to wandb in my setup.


Use <kbd> in documentation

Preview can be found here: https://github.com/Meakk/f3d/blob/kbd-html/doc/user/INTERACTIONS.md

I'll merge it but I'm not sure "just the docs" have the proper css styling for it.

"just the docs" have the proper css styling for it.

You can merge and fix it after if needed, or you can deploy the website on your fork if you want.

or you can deploy the website on your fork if you want.

How can I do that?

That looks bad on the live website

I'll see if I can change the CSS later. I'm putting this PR on hold for now.

I have added a custom css file picked up automatically by just-the-docs.

@snoyer please take another look.
Deployed page is here: https://meakk.github.io/f3d/doc/user/INTERACTIONS.html

Looks good! not sure the li:hover is useful but it's fun
The only thing that I find not amazing now is that the arrow keys looks tiny compared to the others :( is it just me?
Unicode has a few bigger ones but I don't know if that's asking for compatibility issues: 🡨 🡪 🡩 🡫 (comparison: 🡨←)

🤣

@mwestphal I'm sure glad I qualified my statement twice then!
So... my suggestion () does fail bad at compatibility! but it is not just me, that arrow looks tiny on your setup too

Let's stick for regular HTML ampersand aliases, using HTML is asking for troubles.


Minor bug: Float returned by listThreads

In line 208:
listThreads = args.maxthreads / 3
can return a float value which causes an error
For example:
INFO: Starting 66.66666666666666 delete threads...
Modify listThreads to force an integer value and it will work:
listThreads = int(args.maxthreads / 3)

this helped me

updated my PR to use  listThreads = args.maxthreads // 3 which does the same with less brackets ;)


Docs improvement: Docs version matching CLI version.

My experience when learning how to use M365 cli is to go directly to your documents to understand how the commands work. So today for example I went to https://pnp.github.io/cli-microsoft365/cmd/login/ to understand different ways you could log in. I didn't realise until I raised an issue, that I was viewing commands that were only available for the latest beta version of M365 CLI.
Benefit of having versioned docs:

The latest release matches the documents.
People who cannot always upgrade to the latest can switch to the version they are using to ensure the commands they want to use matches the version of the M365 CLI that they have installed.

Can you please look into adding a version switch to your docs with MKDocs Material.
@garrytrinder stated in previous comment on issue #1995

It's not quite a simple as upgrading MkDocs, we also have to think about our integration with MarkShell which we use to display the docs in the CLI --help command, certainly not impossible though.

Thank you for raising this @pmatthews05 👍🏻
@pnp/cli-for-microsoft-365-maintainers any thoughts on this?

Thanks for the suggestion @pmatthews05 and I agree that it would be a great addition.
Since we already maintain our docs along with versions and our versions are tagged, the only question left is if MkDocs, which we use for generating docs, supports this. Let us have a look at what's possible and get back to you as soon as we know more.

This package seems promising and inline with what I had in mind thinking about how we could address this issue: https://github.com/jimporter/mike. I'm not sure if we should offer separate docs for all preview versions or limit docs to latest and next and the previously released versions that we'd need to backfill manually.
One challenge that I see though is with this approach is, that if there is a typo/issue/anything, we won't go back and fix it in all past versions, which might/might not make sense.

To me, it make sense having docs for each release and @next version only. As you publish a release @next would just become the latest version number, and the new @next would be for the new beta stuff.
Typos would be like bugs, in that version it was a bug/typo then in later version its fixed.
With the Url it's a shame its not a parameter at the end of the url. That would just be passed as you click through docs, keeping you on same version until you switch.

The way mike works is that it adds the version or alias as the second segment of the URL, so you would stay in the selected version when clicking around until you choose another version

I'm not sure if we should offer separate docs for all preview versions or limit docs to latest and next and the previously released versions that we'd need to backfill manually.

I agree, I don't think we need docs for every version, just the @latest & @next releases.

One challenge that I see though is with this approach is, that if there is a typo/issue/anything, we won't go back and fix it in all past versions, which might/might not make sense.

A typo I can live with, but if we stick to @latest and @next releases then the typo will only be around for a few days for @next or month for @latest.

One more thing to keep in mind: if we switched to using mike, all our doc links will be broken, because the URL will be extended with version numbers/alias which we currently don't have.

This could be quite painful, could we setup a redirect?

I agree, I don't think we need docs for every version, just the @latest & @next releases.

I think we'd need to take it a bit further. For the setup to be beneficial to users, we'd need @latest and @next but also each release, eg. v3.2.0, v3.1.0. There is plenty of folks using older versions and just @latest and @next would add little value.

This could be quite painful, could we setup a redirect?

Since we're talking about a static site, the only way to setup a redirect would be to create an HTML file at the old URL and have it point to latest which isn't trivial.

I think we'd need to take it a bit further. For the setup to be beneficial to users, we'd need @latest and @next but also each release, eg. v3.2.0, v3.1.0. There is plenty of folks using older versions and just @latest and @next would add little value.

Ah yes, good point, this does the bring back the headache of fixing typo issues going forwards in older versions of the docs, but I'm thinking that this isn't a showstopper, more of an annoyance.

Since we're talking about a static site, the only way to setup a redirect would be to create an HTML file at the old URL and have it point to latest which isn't trivial.

Noted, something to investigate further then, trivial is not impossible right? 😄
I still think that despite the above pains, this is worth pursuing as it is a gap, as @pmatthews05 has highlighted, which as we grow will only become more noticeable.

Noted, something to investigate further then, trivial is not impossible right? 😄

It would come down to getting paths of all files we currently have and creating html files with a redirect to the new URL. The trick is that all that needs to be done on the gh-pages branch to which we commit from CI/CD rather than manually.

With that I think we have identified an action plan:

[ ] verify that mike works with our theme
[ ] verify that we can integrate mike with our CI/CD pipe
[ ] verify that we can combine static redirects from old docs to /latest/page when using mike for publishing versioned docs
[ ] create redirects to /latest/page for all existing pages so that we don't break existing links
[ ] extend CI/CD pipe to include mike so that we support automated building of latest (based on the publish build) and next (based on the publish_next build)
[ ] using mike, manually publish latest for the currently released version

In the future, we could manually backfill last v2 version and other frequently used versions.
Does this capture everything that needs to be done?

With that I think we have identified an action plan:

[ ] verify that mike works with our theme
[ ] verify that we can integrate mike with our CI/CD pipe
[ ] verify that we can combine static redirects from old docs to /latest/page when using mike for publishing versioned docs
[ ] create redirects to /latest/page for all existing pages so that we don't break existing links
[ ] extend CI/CD pipe to include mike so that we support automated building of latest (based on the publish build) and next (based on the publish_next build)
[ ] using mike, manually publish latest for the currently released version

In the future, we could manually backfill last v2 version and other frequently used versions.
Does this capture everything that needs to be done?

As this has become a bit of a stale issue it could be worth to pick up again. The suggestion here looks very interesting to implement into our docs. @pnp/cli-for-microsoft-365-maintainers any thoughts? 😄

Certainly a good enhancement. Certainly now our docs show the V6 docs which is full of breaking changes which are not available in the current v5.9 stable version.


Official checkbox in list or menu item

Is there an official/sanctioned/blessed/Bootstrap best practices solution for having checkboxes (natural or custom) in a menu like list of items, wrapped in a collapsible drop down (see screen shot)? Clicking anywhere on the item toggles the checkbox. There are various implementations around but all seem a bit kludgy and bloated - including mine that stuffs everything in the checkbox label to preserve their click relationship.
https://jsfiddle.net/dragontheory/78aj5dhr/
Is it possible to create a new feature that demonstrates best practices for implementation? Any guidance would be appreciated. Thank you!
BTW, your hard work has improved UX for millions of users. No pressure! Doing great!

Can't provide any helpful response, but just wanted to say that your own solution works really well, so thank you for sharing 👍


Fix conformance report missing tests

What type of PR is this?

/kind bug
/kind conformance
What this PR does / why we need it:
Reports generated by the conformance framework are missing information about tests that are using features that are not part of the core profile. For example, generating the report for istio, running with --all-features:
Before this PR:
apiVersion: gateway.networking.k8s.io/v1alpha1
date: "2023-10-27T12:59:28-04:00"
gatewayAPIVersion: TODO
implementation:
  contact:
  - '@istio/maintainers'
  organization: istio
  project: istio
  url: github.com/istio/istio
  version: 1.20-preliminary
kind: ConformanceReport
profiles:
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 2
      Skipped: 0
    summary: ""
  name: MESH
- core:
    failedTests:
    - GatewayWithAttachedRoutes
    result: failure
    statistics:
      Failed: 1
      Passed: 28
      Skipped: 0
    summary: ""
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 0
    summary: ""
  name: HTTP
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 10
      Skipped: 0
    summary: ""
  name: TLS

After this PR:
apiVersion: gateway.networking.k8s.io/v1alpha1
date: "2023-10-27T12:53:33-04:00"
gatewayAPIVersion: TODO
implementation:
  contact:
  - '@istio/maintainers'
  organization: istio
  project: istio
  url: github.com/istio/istio
  version: 1.20-preliminary
kind: ConformanceReport
profiles:
- core:
    failedTests:
    - GatewayWithAttachedRoutes
    result: failure
    statistics:
      Failed: 1
      Passed: 28
      Skipped: 0
    summary: ""
  extended:
    result: partial
    skippedTests:
    - GatewayObservedGenerationBump
    - GatewayStaticAddresses
    statistics:
      Failed: 0
      Passed: 14
      Skipped: 2
    summary: ""
  name: HTTP
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 10
      Skipped: 0
    summary: ""
  extended:
    result: partial
    skippedTests:
    - GatewayObservedGenerationBump
    - GatewayStaticAddresses
    statistics:
      Failed: 0
      Passed: 0
      Skipped: 2
    summary: ""
  name: TLS
- core:
    result: success
    statistics:
      Failed: 0
      Passed: 2
      Skipped: 0
    summary: ""
  extended:
    result: partial
    skippedTests:
    - MeshFrontendHostname
    statistics:
      Failed: 0
      Passed: 3
      Skipped: 1
    summary: ""
  name: MESH

Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

NONE

Added work-in-progrss label because I see there are still more problems with the reporting. For example, there are only 4 TLS conformance tests but the framework is associating 10 (before this PR) and now 12 with the TLS profile, since the checking doesn't really confirm that the key feature (TLSRoute) is part of the test.

Turns out there is a bigger issue with how the report generator associates tests with conformance profiles. It currently decides based on the test.Features - if they are all part of a profile, it associates the test with that profile. There are 2 problems with this approach: 1) the tests are using the features to indicate what it needs to run the tests, not exactly what they're trying to test, 2) some tests are not correctly listing the features they use anyway. The result is that the same test run sometimes appear as a "passed/failed/skipped test" in more than one conformance profile, sometimes in profiles where they don't belong at all.
Fixing the above will require more significant changes in the framework including probably a way for tests to declare their conformance profile, not just the features they're using.
Since this PR fixes a different issue, i.e., adding missing tests that rightfully belong in the report plus a couple of other minor fixes, I suggest we merge this now and look at fixing the duplicate reporting issue in a future followup.

making sure the merged commit title/sub title are a bit more specific about what exactly is being fixed would be great

This PR started by adding HTTPRouteExtendedFeatures to the MESH profile, because several of the mesh tests weren't showing up in the report as they should. I then added GatewayExtendedFeatures to both the TLS and HTTP profiles, but that just seemed kind of confusing because it ended up reporting on tests that really aren't testing HTTP or TLS specific things. As I said in my previous comment, I think that identifying the profile that a test is for is a bigger issue that we need to work on in a future PR, so I removed the GatewayExtendedFeatures part from this PR so now it simply fixes the missed MESH tests plus a couple of other small things.
I'll update the title and description to say exactly what it's fixing now.

/cc


Page token coingecko_id update

Added coingecko_id to ethereum, gravitybridge, and osmosis assetlists
Removed ".grv" from symbol on osmosis (was being duplicated in frontends)

Please only add the cgid to the original asset listed under Ethereum, but not any others

Please only add the cgid to the original asset listed under Ethereum, but not any others

I've removed the other commits and added the symbol update for osmosis


Use explicit accept list for highway values

So far we used VehicleTagParser#getAccess to determine whether an OSM way shall be accepted when parsing the OSM file. With this PR there will be only one global list of accepted highway values. It is still up to the vehicle tag parsers (and in the near future only up to the access tag parsers) whether a given way is used for the route calculations. Not accepting a highway value in the global list is therefore mostly a performance optimization. So far this happened automatically by only using certain vehicles. For example if we used only profiles with the car profile footways were rejected automatically. With the new global list this needs to be done manually, but at the same time the mechanism becomes more powerful and easier to understand IMO.
See more comments inline.
Related: https://github.com/graphhopper/graphhopper/issues/2463#issuecomment-1174205767

I did not take a look at the failing tests yet, but will fix them of course once there is agreement for this PR @karussell

We also need to accept ways tagged as route=ferry or route=shuttle_train. There are also some tagged as route=hiking,mtb etc. but I think we can assume that these will be included because they carry a highway tag as well.

@karussell I just realized that the RoadsTagParser did not use the getAccess method in handleWayTags. So prior to this change it did not accept ways tagged with route (like ferries) so they weren't accessible. Unless there was another vehicle that accepts ferries, of course.
So this PR changed the behavior in case we use only the roads vehicle: Before ferries were not used, but now they are.


Enhanced data validation to address YSA-2020-01

Any thoughts on this thread?

Okay, @yubico, what the hell.
https://yubico.com/support/security-advisories/ysa-2020-01/
SQL injection. In a product by a security vendor. In 2020. And you fixed it with "data validation"?!?! Not prepared statements?!? Not even just escaping the params‽‽‽‽
This is downright criminally irresponsible code.


W5500 is broken due to enforced version check  (IDFGH-10054)

Answers checklist.

[x] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1-dev-4528-g420ebd208a
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
Custom board
Power Supply used.
USB
What is the expected behavior?
Some W5500 chips may return 0 for version, and just works and connects to the ethernet in ESP-IDF 5.0 (or anything before this commit bb2f346e55f484edc50f68cb26d164d8a79bcf39)
What is the actual behavior?
Broken with error:
E (3645) w5500.mac: w5500_verify_id(234): invalid chip version, expected 0x4, actual 0x0
E (3655) w5500.mac: emac_w5500_init(703): vefiry chip ID failed

...and apparently, no ethernet connection can be established after this error.
Steps to reproduce.
I've tried commenting out this line, the issue can be fixed: https://github.com/espressif/esp-idf/blob/bb2f346e55f484edc50f68cb26d164d8a79bcf39/components/esp_eth/src/esp_eth_mac_w5500.c#L234
Debug Logs.
No response
More Information.
I've sourced our W5500 module from here: https://99tech.com.au/product/mod-w5500-t2/
It seems to be a genuine chip, at least the engraved mark on the chip package is identical to the one on Wiznet's official Raspberry Pi Pico dev W5500 HAT module. It might be just in a different version, and both versions are working fine with ESP-IDF's W5500 driver anyway.

Interestingly, according to W5500's datasheet, the VERSIONR should be always 0x04:

I don't know now, maybe the module bought from 99tech is with a fake chip or engineering sample chip? But it does work fine with the W5500 driver if that line of code is removed.

Linking the discussion in https://github.com/espressif/esp-idf/pull/10554#issuecomment-1512821151

Linking the discussion in #10554 (comment)

Oh sorry, I haven't seen this earlier. I will close this issue for now. I'll try putting in a 100ms delay tomorrow and see will that helps or not.

Hi @kostaond , I've implemented a poll here: https://github.com/huming2207/esp-idf/commit/6e5e2c7344aaea3add65395849cfd282f6ae572c
I'm awaiting my colleagues to test that out. If that works for us, I will submit a PR soon.

We've tested the fix and it works for us. I will submit a PR.

PR submitted, waiting for review now! @igrr @kostaond @espzav @reinismu

Needs backport to release/v5.1.

Needs backport to release/v5.1.

Good catch!

Is there a way to override the W5500_CHIP_VERSION or the whole w5500_verify_id function?
It seems i have a fake or broken chip which working totally fine with 4.4 but not with 5.1 because the version is not detected 0x0.

Is there a way to override the W5500_CHIP_VERSION or the whole w5500_verify_id function? It seems i have a fake or broken chip which working totally fine with 4.4 but not with 5.1 because the version is not detected 0x0.

Could you please try to upgrade to v5.1.1. The version check function in this version performs multiple attempts to read the version. It was observed that some chips return 0x0 when it is read right after the reset.


Convert P3HT.martini3.itp to P3HT.martini3.ff

I am encountering some issue when doing this conversion, namely:

"i-j-k" bonded terms, i.e., bonded terms spanning across 3 repeat units: connections between monomer N and N-1 won't get printed after the last N-2--N-1--N connection gets printed; don't know if I'm doing something wrong here.?
The line responsible is commented out:

;  V4  +V4 ++V4    1       158      180  {"comment": "i-j-k"}

[ exclusions ] are not handheld by the .ff format --> https://github.com/marrink-lab/polyply_1.0/issues/134;
Lines are commented out:

;[ exclusions ]
;; between nearest-neighbor thiophenes
;   S1  +S1  +C2  +C3                    {"comment": "connection"}
;   C2  +S1  +C2  +C3                    {"comment": "connection"}
;   C3  +S1  +C2  +C3                    {"comment": "connection"}

3. [ virtual_sitesn ]: in the [ virtual_sitesn ] section, also the function type is shifted by N_monomer_atoms.
I'm gonna comment about it in this issue: https://github.com/marrink-lab/polyply_1.0/issues/120
This is the correct output for an hexamer: https://github.com/marrink-lab/polyply_1.0/blob/master/polyply/tests/test_data/library_tests/martini3/P3HT/polyply/P3HT.itp

@ricalessandri exclusions and VS I answered about in the relevant issues. I also put the tag FAQ. I think those will be very valuable to add to the FAQ section.
Regarding the N and N+2 links. Basically that is what I outlined when you were asking about why I split angles, dihedrals and bonds into separate link for gromos. In order for a link to apply the entire fragment has to be present. That means when you have an angle that spans three residues the entire link will only apply when all three residues are present. That means towards the end of your polymer you will not have any links because when there are only two residues left. As a rule of thumb each interaction in the same link should span the same residues

Great, now I understood the need for re-defining the link - that's pretty OK.
I also updated the reference itp for the tests (and now all the checks pass - I guess that was the reason the checks were breaking).

@ricalessandri looks good to me. There is just one thing I don't understand. How is the reference file you have now different from the one that is generated by P3HT.martini3.itp? Shouldn't they be the same?

Well, you can see the differences:
https://github.com/marrink-lab/polyply_1.0/pull/135/files#diff-f6f68e6a69bc3649043d658f6c7e005e562187bf8d522c2e547d4906836cd8ec
namely:

now the command is printed on the first line (; /Users/riccardo/miniconda3/envs/polyply/bin/polyply gen_itp -lib martini3 -name P3HT -seq P3HT:6 -o P3HT_n6_M3.itp) and there's the ; Please cite the following papers: bit
I added a comment to the i-j-k connection (; connection i-j-k)
changed the function type of the VS from 2 (-> COM) to 1 (->COG) (but it doesn't really matter)
the lines in the [exclusions] are printed in a different order

Ready to go - unless you want to include via this PR also the versions with
different side chain lengths and the "reversed" monomer which is needed to
create regiorandom P3HT (which btw "solves" issue
https://github.com/marrink-lab/polyply_1.0/issues/91). If not, please merge
this PR and I will open a dedicated PR for those.
On Tue, May 11, 2021 at 2:09 AM fgrunewald @.***> wrote:

@.**** approved this pull request.
Should be ready to go or are we still in the need of optimizing something
here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/marrink-lab/polyply_1.0/pull/135#pullrequestreview-656353798,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACREAS4KKWF7K5TKT7SBIQ3TNDJ25ANCNFSM436R7XYQ
.

@ricalessandri let's merge this first. We add the other topologies when the test-case is done. Perhaps we'll have to adjust those anyways to improve the test case. No harm in having more than 1 PR.


Precautions consultation in running

Hi! I would like to ask you if there are any cautions in running this project. I always have some small errors in the process of running. For example, in openai_llm.py, line 94, in _replenish self.throughput = self.total / (curr_time - self.start_time) * 60 ZeroDivisionError: float division by zero. And some data type errors. Was there something I didn't notice?Thanks!

I haven't seen this before but you can just comment out this line to unblock yourself (or add a small epsilon to curr_time). This isn't required logic and only there to track how many llm calls are made per minute.


Mockserver UI not available

Mockserver UI can not be reached over http://localhost:8080/mockserver/dashboard

@alx-kpk, this is another project. Suppose, you are talking about this project https://github.com/mock-server/mockserver.

Ah, thanks for the hint. I thought this is a fork of the other project.


Startup performances

Optimizations or support for optimizing the startup performances of the CamelContext.
For reference, the optimized camel context is implemented here:
https://github.com/gnodet/openwhisk-camel/tree/master/openwhisk-runtime-camel/proxy/src/main/java/openwhisk/camel/action/support
It's not fully functional, so can't be included at this point.
I'll run a full build first and fix any remaining issues before, so the PR is not ready yet to be merge.

If it works for everybody we can defer this after 2.22.0 release cut, that should be this weekend. I think we are in a good shape now and maybe we need a bit more time to test this good stuff. @davsclaus @lburgazzoli @aldettinger @onderson @nicolaferraro and others what do you think?

Np, and as I said, I need to run a full build before anyway.

Great, I'll keep an eye on this for sure :-)


linear regression issues

Thank you for sharing your fine work on regression-js.  I just wanted to point out 2 issues that caused my linear best-fit to miscompute the gradient:

after pushing my actual data points onto bfSeries (see MAIN excerpt below), numeric coords were sometimes being interpreted as string within the regression.js linear function for some unknown reason, throwing off the gradient computation.  To prevent this, I call parseFloat() before pushing any of the points.
after pushing my 2 trend-setting points  (having null y-coord) onto bfSeries, the linear function in regression.js was trying to use these points when computing gradient & intercept. To avoid this, I introduced var N (see below).

MAIN JAVASCRIPT:
<script type="text/javascript" src="/includes/regression.js"></script>
var bfSeries = []; //define empty array to hold each actual data point plus 2 trend-setting points.

//Prepare a data series for Best Fit (bfSeries), based on an existing series of actual data points.
bfSeries.push([parseFloat(1), null]);   //First push the left trend-setting point; the null tells regression() to compute the y coordinate of this point on the trend line.
for (i=0; i < series.length; i++) {    //push each point of actual data. Only the actual data points are used to compute the trend line.
    bfSeries.push([parseFloat(series[i][0]), parseFloat(series[i][1])]);   //Bug: string coords were observed to be pushed here, causing the regression to miscompute slope.  Fix: convert coords to float prior to pushing.
}
bfSeries.push([parseFloat(100), null]);  //Finally, push the right trend-setting point; the null tells regression() to compute the y coordinate of this point on the trend line.
var myRegression = regression('linear', bfSeries);

REGRESSION.JS (excerpt):     I introduce var N to fix forecasting issue 2:
            linear: function(data) {
                var sum = [0, 0, 0, 0, 0], n = 0, results = [];
                var N = 0;  //the actual number of x,y points participating in the regression (excludes forecasted points, i.e., those having a null y-coordinate).

                for (; n < data.length; n++) {
                  if (data[n][1]) {
                    sum[0] += data[n][0];
                    sum[1] += data[n][1];
                    sum[2] += data[n][0] * data[n][0];
                    sum[3] += data[n][0] * data[n][1];
                    sum[4] += data[n][1] * data[n][1];
                    N++;
                  }
                }

             // var gradient = (n * sum[3] - sum[0] * sum[1]) / (n * sum[2] - sum[0] * sum[0]);
             // var intercept = (sum[1] / n) - (gradient * sum[0]) / n;
             // var correlation = (n * sum[3] - sum[0] * sum[1]) / Math.sqrt((n * sum[2] - sum[0] * sum[0]) * (n * sum[4] - sum[1] * sum[1]));

                var gradient = (N * sum[3] - sum[0] * sum[1]) / (N * sum[2] - sum[0] * sum[0]);
                var intercept = (sum[1] / N) - (gradient * sum[0]) / N;

                for (var i = 0, len = data.length; i < len; i++) {
                    var coordinate = [data[i][0], data[i][0] * gradient + intercept];  //this plots all data points (including forcasted points)
                    results.push(coordinate);
                }

                var string = 'y = ' + Math.round(gradient*100) / 100 + 'x + ' + Math.round(intercept*100) / 100;
             // var string = 'y = ' + gradient + 'x + ' + intercept;   //actual equation
                return {equation: [gradient, intercept], points: results, string: string};
            },

when all the x values are the same, the NaN error is coming again!!!! for example, regression('linear', [[parseFloat(1),parseFloat(1)],[parseFloat(1),parseFloat(1)],[parseFloat(1),parseFloat(1)],[parseFloat(1),parseFloat(1)],[parseFloat(1),parseFloat(1)],[parseFloat(01),parseFloat(1)]]);

Fixed in #59


[Docs]: add Markdown validation GitHub Action

add Markdown validation GitHub Action when documentation PR to ensure valid Markdown for doc generation

It was done before we moved to 2.1 Docusaurus changes, now we need to fix it, but there's an issue for that.


Bump sources to latest available (05/10/2022)

Incorporate the latest changes from upstream

usb networking does not work with this kernel: apparently two usb interfaces are created and the udhcpd runs on the wrong one.
Previously only one usb interface existed.
I might have to update my software version for this to work properly (I am on<PHONE_NUMBER>4022).
Someone testing on RM1 and/or other software versions could be helpful.

I traced the usb issue down to https://github.com/reMarkable/linux/commit/6a394b204c06a8df11493f9160948cafd561966b: CDC ECM and CDC EEM behave differently.
The latest version supported on toltec is<PHONE_NUMBER>4022 (i.e. <IP_ADDRESS>9) and the kernel shipping with this version does not have this commit merged in: it is built from https://github.com/reMarkable/linux/tree/RM1XX_5.4.70_v1.2.5.
I guss this PR will have to wait.

@Etn40ff the reMarkable linux repo has been updated recently. Does it have what you need?

I am not sure, it looks like all the changes are related to the new pogo module that handles the keyboard folio.
I will have to test this.

@Etn40ff have you had a chance to look closer?

@Etn40ff poke again

@Etn40ff poke

This is now #742

@Etn40ff so should this be closed?

I guess so


[Bug][JNI] Parse JNI functions in native layer

Describe the bug
Fail to parse C code when a JNI function returns a non-JNI type
To Reproduce
The C Code:
#include <string.h>

#include "engine.h"
#include "input.h"
#include "math.h"
#include "renderer.h"
JNIEXPORT void JNICALL Java_com_termux_x11_XrActivity_init(JNIEnv *env, jobject obj) {

    // Do not allow second initialization
    if (xr_initialized) {
        return;
    }

    // Set platform flags
    memset(&xr_engine, 0, sizeof(xr_engine));
    xr_engine.PlatformFlag[PLATFORM_CONTROLLER_QUEST] = true;
    xr_engine.PlatformFlag[PLATFORM_EXTENSION_PASSTHROUGH] = true;
    xr_engine.PlatformFlag[PLATFORM_EXTENSION_PERFORMANCE] = true;

    // Get Java VM
    JavaVM* vm;
    (*env)->GetJavaVM(env, &vm);

    // Init XR
    xrJava java;
    java.vm = vm;
    java.activity = (*env)->NewGlobalRef(env, obj);
    XrEngineInit(&xr_engine, &java, "termux-x11", 1);
    XrEngineEnter(&xr_engine);
    XrInputInit(&xr_engine, &xr_input);
    XrRendererInit(&xr_engine, &xr_renderer);
    XrRendererGetResolution(&xr_engine, &xr_renderer, &xr_params[4], &xr_params[5]);
    xr_initialized = true;
    ALOGV("Init called");
}

Steps to reproduce the behavior:

Run joern: ./joern
joern> importCode("path/to/c","name")
joern> cpg.method.name.l

Expected behavior
Joern should correctly recognize the function Java_com_termux_x11_XrActivity_init and list it in the output of cpg.method.name.l.
Output
val res3: List[String] = List("<global>", "<global>", "<operator>.assignment", "<operator>.arrayInitializer")

joern cannot recognize function: Java_com_termux_x11_XrActivity_init()
Desktop (please complete the following information):

Debian 5.16.18-1kali1
Joern Version: 4.0.67
Java Version: 17.0.10

Additional context
Other non-JNI type such as primitive data types will get similar results

You need to give c2cpg the path to the included files (--include ) and/or you system header files location (--with-include-auto-discovery). Otherwise, definitions like JNIEXPORT and such can not be resolved.

But joern can resolve JNI functions whose return value is JNI type without giving c2cpg any path to the included files:
#include <string.h>

#include "engine.h"
#include "input.h"
#include "math.h"
#include "renderer.h"

JNIEXPORT jfloatArray JNICALL Java_com_termux_x11_XrActivity_getAxes(JNIEnv *env, jobject obj) {
    XrPosef lPose = XrInputGetPose(&xr_input, 0);
    XrPosef rPose = XrInputGetPose(&xr_input, 1);
    XrVector2f lThumbstick = XrInputGetJoystickState(&xr_input, 0);
    XrVector2f rThumbstick = XrInputGetJoystickState(&xr_input, 1);
    XrVector3f lPosition = xr_renderer.Projections[0].pose.position;
    XrVector3f rPosition = xr_renderer.Projections[1].pose.position;
    XrVector3f angles = xr_renderer.HmdOrientation;

    int count = 0;
    float data[32];
    data[count++] = XrQuaternionfEulerAngles(lPose.orientation).x; //L_PITCH
    data[count++] = XrQuaternionfEulerAngles(lPose.orientation).y; //L_YAW
    data[count++] = XrQuaternionfEulerAngles(lPose.orientation).z; //L_ROLL
    data[count++] = lThumbstick.x; //L_THUMBSTICK_X
    data[count++] = lThumbstick.y; //L_THUMBSTICK_Y
    data[count++] = lPose.position.x; //L_X
    data[count++] = lPose.position.y; //L_Y
    data[count++] = lPose.position.z; //L_Z
    data[count++] = XrQuaternionfEulerAngles(rPose.orientation).x; //R_PITCH
    data[count++] = XrQuaternionfEulerAngles(rPose.orientation).y; //R_YAW
    data[count++] = XrQuaternionfEulerAngles(rPose.orientation).z; //R_ROLL
    data[count++] = rThumbstick.x; //R_THUMBSTICK_X
    data[count++] = rThumbstick.y; //R_THUMBSTICK_Y
    data[count++] = rPose.position.x; //R_X
    data[count++] = rPose.position.y; //R_Y
    data[count++] = rPose.position.z; //R_Z
    data[count++] = angles.x; //HMD_PITCH
    data[count++] = angles.y; //HMD_YAW
    data[count++] = angles.z; //HMD_ROLL
    data[count++] = (lPosition.x + rPosition.x) * 0.5f; //HMD_X
    data[count++] = (lPosition.y + rPosition.y) * 0.5f; //HMD_Y
    data[count++] = (lPosition.z + rPosition.z) * 0.5f; //HMD_Z
    data[count++] = XrVector3fDistance(lPosition, rPosition); //HMD_IPD

    jfloat values[count];
    memcpy(values, data, count * sizeof(float));
    jfloatArray output = (*env)->NewFloatArray(env, count);
    (*env)->SetFloatArrayRegion(env, output, (jsize)0, (jsize)count, values);
    return output;
}

Result:
val res1: List[String] = List(
  "<global>",
  "Java_com_termux_x11_XrActivity_getAxes",
  "<global>",
  "<operator>.assignment",
  "XrInputGetPose",
  "<operator>.addressOf",
  "XrInputGetJoystickState",
  "<operator>.fieldAccess",
  "<operator>.indirectIndexAccess",
  "<operator>.alloc",
  "<operator>.postIncrement",
  "XrQuaternionfEulerAngles",
  "<operator>.multiplication",
  "<operator>.addition",
  "XrVector3fDistance",
  "memcpy",
  "<operator>.sizeOf",
  "<operator>.pointerCall",
  "<operator>.indirectFieldAccess",
  "<operator>.indirection",
  "<operator>.cast"
)

So I suppose maybe it isn't an issue with the include-path？

We simply use Eclipse CDT as a parser. If CDT is not able to parse it there is nothing we can do unfortunately.

I tried a c2cpg standalone run with --log-problems and found the following issue:
2024-09-18 22:42:25.906 INFO ParseProblemsLogger: Parse problem 'CASTProblem' occurred!
  Code: 'JNIEXPORT void JNICALL Java_com_termux_x11_XrActivity_teardown(JNIEnv *env, jobject obj) {
    if (!xr_initialized) {
        return;
    }

    XrRendererDestroy(&xr_engine, &xr_renderer);
    XrEngineLeave(&xr_engine);
    XrEngineDestroy(&xr_engine);

    memset(&xr_engine, 0, sizeof(xr_engine));
    memset(&xr_input, 0, sizeof(xr_input));
    memset(&xr_renderer, 0, sizeof(xr_renderer));
    xr_initialized = false;

}'
  File: '/home/kali/桌面/cfgtool/cfgtool/cfgtool_new/cfgtool_fix/c_termux-x11-master/android.c'
  Line: 8

It is too general to locate the bug. And I try to find information on 'CASTProblem' in joern's document but fail.  I apologize for any inconvenience, but I would greatly appreciate it if you can provide some guidance.

I am pretty sure the parser can't find the definitions for JNIEXPORT and JNICALL.
What happens if you place these definitions directly into the file?


Save editor contents locally upon leaving an exercise

Closes #144, thanks for the suggestion.

oops, duplicate


NB5 named scenarios revamp

Covers initial nb5 updates for supporting new structures of scenarios for blocks, ops, schema, main, etc.
Addressing binding additions for stargate token and http scenarios as part of #975 as PR#985

@jeffbanks Is this ready for review?

Tracking list of adapter scenario changes:
cql

/activities/baselines/cql-iot-dse.yaml
/activities/baselines/cql-iot.yaml
/activities/baselines/cql-keyvalue-astra.yaml
/activities/baselines/cql-keyvalue.yaml
/activities/baselines/cql-tabular.yaml
/activities/baselinesv2/cql-keyvalue2-bulky.yaml
/activities/baselinesv2/cql-keyvalue2.yaml
/activities/baselinesv2/cql-tabular2.yaml
/activities/baselinesv2/cql-timeseries2.yaml
/activities/examples/cql-rowops.yaml
/activities/baselines/incremental.yaml
http-rest

/activities/baselines/http-rest-keyvalue.yaml
/activities/baselines/http-rest-tabular.yaml
/activities/baselines/http-rest-timeseries.yaml
dynamodb

/activities/baselinesv2/dynamodb-keyvalue2.yaml
/activities/baselinesv2/dynamodb-tabular2.yaml
/activities/baselinesv2/dynamodb-timeseries2.yaml
mongodb

/activities/baselinesv2/mongodb-keyvalue2.yaml
/activities/baselinesv2/mongodb-tabular2.yaml
/activities/baselinesv2/mongodb-timeseries2.yaml
/activities/mongodb-basic-uuid.yaml
/activities/mongodb-basic.yaml
/activities/mongodb-crud-basic.yaml
/activities/mongodb-crud-dataset.yaml
/activities/mongodb-search-basic.yaml
http docs-api

/activities/documents-api/http-docsapi-crud-basic.yaml
/activities/documents-api/http-docsapi-crud-dataset.yaml
/activities/documents-api/http-docsapi-keyvalue.yaml
/activities/documents-api/http-docsapi-search-advanced.yaml
/activities/documents-api/http-docsapi-search-basic.yaml
graph

/activities/baselines/graph-wheels.yaml
/activities/graphql-cql-first/http-graphql-cql-keyvalue.yaml
/activities/graphql-cql-first/http-graphql-cql-tabular.yaml
/activities/graphql-cql-first/http-graphql-cql-timeseries.yaml
/activities/graphql-schema-first/http-graphql-keyvalue.yaml
/activities/graphql-schema-first/http-graphql-tabular.yaml
/activities/graphql-schema-first/http-graphql-timeseries.yaml

@jshook Additional updates added for PR feedback.  Ready for an additional review.


 I'd appreciate, if you take a look :)
I am looking forward to merge more of Neetcode solutions in Go.

Looks good, thanks for reaching out!

Make sure your approach is not too different from the one's explained in NeetCode videos as some people complain about solutions that are completely different. All the best solving more problems!

@felivalencia3 @chetannada @mdmzfzl @sujal-goswami Hey guys! I'd appreciate, if you take a look :) I am looking forward to merge more of Neetcode solutions in Go.

Great. Keep posting good solution.


fix(64) added option "updateEndpoint" to OpcUaClient

Motivation
It can happen quiet often that a OPC UA server returns a (by the client) not resolvable hostname and/or port.
Resolves #64
Changes
Added option "UpdateEndpoint" to the OpcUaClient. It will update the URI from the server with the configured hostname and port. It's optionally in the configuration page of the OpcUaClient connection.

ACK - thank you, will be reviewed.

@cla-bot check

How can I sign the Contributor License?

Ok. Done.

@cla-bot check

@cla-bot check

A unit test (OpcUaEndpointFilterTest) fails because of a NPE. The problem is that a null uri is handed over to the update method. Two places need to be adapted:
  line 86:   .map(policyUri -> new EndpointDescription("opc.tcp://<IP_ADDRESS>:49320", null, null, null, policyUri, null, null, null))
and
 line 104:  config.setTls(new OpcUaAdapterConfig.Tls(true, new OpcUaAdapterConfig.Keystore("path", null, null), null));
As the URI is mandatory I think it is safe to assume it is not null. Still a null check would not hurt.

@vogler75 is it OK with you if we take this over and do the proposed changes ourselves to get it merged ?
We will keep your commits and attribution.

Sure, it is ok for me.

I close this PR as we take it over in https://github.com/hivemq/hivemq-edge/pull/198


Cds 49945 servicev1 eol notice

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[x ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/CDS-49945

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-362

Preview environment: https://ci.pr.harness.io/pr-362


Was not successfully self-verified.

I'm running this image on a server with a valid domain, yesterday I ran the tests on my VPS and it worked normal using Dmitry's docker-compose, but today doing the same test again, is returning the log down:
letsencrypt                          | 2017-08-03 17:41:28,175:INFO:simp_le:1213: Generating new account key
nginx-proxy                          | nginx.1    | b.suadieta.net <IP_ADDRESS> - - [03/Aug/2017:17:41:30 +0000] "GET /.well-known/acme-challenge/5emB8QeqwEjNy58-CfclrAnPII4sC36qzYf4XyLxfEI HTTP/1.1" 302 0 "-" "python-requests/2.18.1"
nginx-proxy                          | nginx.1    | b.suadieta.net <IP_ADDRESS> - - [03/Aug/2017:17:41:30 +0000] "GET /wp-admin/install.php HTTP/1.1" 200 3824 "-" "python-requests/2.18.1"
letsencrypt                          | 2017-08-03 17:41:30,697:WARNING:simp_le:1304: b.suadieta.net was not successfully self-verified. CA is likely to fail as well!
letsencrypt                          | 2017-08-03 17:41:30,809:INFO:simp_le:1314: Generating new certificate private key
nginx-proxy                          | nginx.1    | b.suadieta.net <IP_ADDRESS> - - [03/Aug/2017:17:41:31 +0000] "GET /.well-known/acme-challenge/5emB8QeqwEjNy58-CfclrAnPII4sC36qzYf4XyLxfEI HTTP/1.1" 302 0 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"
nginx-proxy                          | nginx.1    | b.suadieta.net <IP_ADDRESS> - - [03/Aug/2017:17:41:31 +0000] "GET /wp-admin/install.php HTTP/1.1" 200 3824 "http://b.suadieta.net/.well-known/acme-challenge/5emB8QeqwEjNy58-CfclrAnPII4sC36qzYf4XyLxfEI" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"
letsencrypt                          | 2017-08-03 17:41:35,259:ERROR:simp_le:1272: CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Is there a warning log entry about unsuccessful self-verification? Are all your domains accessible from the internet? Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/m1PeM5lIcMjgwY5DafWViebIpfgKB2ouGIDJYaHQ5nA
letsencrypt                          | Challenge validation has failed, see error log.
letsencrypt                          |
letsencrypt                          | Debugging tips: -v improves output verbosity. Help is available under --help.
letsencrypt                          | Sleep for 3600s

I get the same error I do not know how to debug it and start looking what is wrong.  I DO expose the proper ports and everything but I still get the same error... :(

The same happens here in an installation that was working before.
Upgraded both nginx-proxy and letsencrypt-nginx-proxy-companion to the respective latest versions, still the same.

Same here. Could be a problem with LE.

Just tried and it worked out of the box on a fresh host.
Ubuntu 16.04
Docker 17.06
docker-compose 1.15.0
Creating Diffie-Hellman group (can take several minutes...) Generating DH parameters, 2048 bit long safe prime, generator 2 This is going to take a long time ............+............++*++* Sleep for 3600s 2017/08/07 14:03:50 Generated '/app/letsencrypt_service_data' from 3 containers 2017/08/07 14:03:50 Running '/app/update_certs' 2017/08/07 14:03:50 Watching docker events 2017/08/07 14:03:50 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/update_certs' Reloading nginx proxy (7b26f73a05f7634a2c8a30e4e7185b1d11fbbf146bf0782f8f90592af7ad856c)... Q2017/08/07 14:03:51 Generated '/etc/nginx/conf.d/default.conf' from 3 containers ;2017/08/07 14:03:51 [notice] 43#43: signal process started Creating/renewal testle.domain.tld certificates... (testle.domain.tld) 2017-08-07 14:03:52,633:INFO:simp_le:1213: Generating new account key 2017-08-07 14:03:58,047:INFO:simp_le:1306: testle.duuu.ch was successfully self-verified 2017-08-07 14:03:58,310:INFO:simp_le:1314: Generating new certificate private key 2017-08-07 14:04:03,565:INFO:simp_le:393: Saving account_key.json 2017-08-07 14:04:03,566:INFO:simp_le:393: Saving key.pem 2017-08-07 14:04:03,566:INFO:simp_le:393: Saving chain.pem 2017-08-07 14:04:03,567:INFO:simp_le:393: Saving fullchain.pem 2017-08-07 14:04:03,567:INFO:simp_le:393: Saving cert.pem Reloading nginx proxy (7b26f73a05f7634a2c8a30e4e7185b1d11fbbf146bf0782f8f90592af7ad856c)... 2017/08/07 14:04:03 Generated '/etc/nginx/conf.d/default.conf' from 3 containers 2017/08/07 14:04:03 [notice] 55#55: signal process started Sleep for 3600s

Hmm. Thanks for confirming that @buchdag
Could you please have a look and see if there is anything obvious about why my configuration isn't working?
docker-compose.yml:
services:

  nginx:
    restart: always
    image: nginx
    container_name: nginx
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - "/etc/nginx/conf.d"
      - "/etc/nginx/vhost.d"
      - "/usr/share/nginx/html"
      - "./volumes/proxy/certs:/etc/nginx/certs:ro"
    volumes_from:
      - creativeopportunities
    depends_on:
      - creativeopportunities

  nginx-gen:
    restart: always
    image: jwilder/docker-gen
    container_name: nginx-gen
    volumes:
      - "/var/run/docker.sock:/tmp/docker.sock:ro"
      - "./volumes/proxy/templates/nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro"
    volumes_from:
      - nginx
    entrypoint: /usr/local/bin/docker-gen -notify-sighup nginx -watch -wait 5s:30s /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf

  letsencrypt-nginx-proxy-companion:
    restart: always
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt-nginx-proxy-companion
    volumes_from:
      - nginx
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock:ro"
      - "./volumes/proxy/certs:/etc/nginx/certs:rw"
    environment:
      - NGINX_DOCKER_GEN_CONTAINER=nginx-gen

  creativeopportunities:
    image: karimtabet/papusa:0.2.77
    container_name: creativeopportunities
    volumes:
      - "./volumes/nginx-creativeopportunities/conf.d/:/etc/nginx/conf.d"
      - /srv/logs
      - /srv/papusa
    expose:
      - "8000"
    environment:
      - VIRTUAL_HOST=www.creativeopportunities.co.uk,creativeopportunities.co.uk
      - LETSENCRYPT_HOST=www.creativeopportunities.co.uk,creativeopportunities.co.uk
      -<EMAIL_ADDRESS>
nginx.conf:
upstream creativeopportunities {
  ip_hash;
  server creativeopportunities:8000;
}

# portal
server {
    listen 8000;
    server_name localhost;
    location / {
        proxy_pass http://creativeopportunities/;
    }
    location /static {
        alias /srv/papusa/static;
    }
}
server {
    listen 80;
    server_name creativeopportunities.co.uk;
    location / {
        proxy_pass http://creativeopportunities/;
    }
    location /static {
        alias /srv/papusa/static;
    }
}

Am I missing something here?

I recently got this too. I added DEBUG=true which revealed the actual error: SERVFAIL looking up CAA. I don't have a solution yet.
See https://community.letsencrypt.org/t/caa-servfail-changes/38298

I had a similar problem SERVFAIL looking up A for ...com
There were some misconfigurations with the DNS Servers. I am using namecheap and disabled the DNSSEC. Now the certification process finally works again! yay!
This post helped me: https://community.letsencrypt.org/t/dns-problem-servfail-looking-up-a-for-sub-domain-tld/19864
Hopefully this helps you too!

Self verification is no longer relevant (it was unreliable and consequently removed from simp_le) and a note on CAA was added to both the README and project's wiki, so I'm closing this issue.


IllegalArgumentException: Invalid schemaType: 'Uuid'

Hi there,
I have noticed that the shorthand function for creating a payload index asynchronously is missing a case statement. Therefore, I get an IllegalArgumentException when I try to create an index with the payload schema type UUID.
java.lang.IllegalArgumentException: Invalid schemaType: 'Uuid'
	at io.qdrant.client.QdrantClient.createPayloadIndexAsync(QdrantClient.java:2163)

I can confirm that manually creating the builder creates the index as intended.
Regards,
canleon

Hey @canleon.
Thanks for pointing out. Will update the helper.


Fix SWDIO for J-Link

For the swdio command, it seems that the max_mem_block_size is actually useful.
This should probably be coordinated with the JTAG I/O, so it's still marked as draft.
@bugadani I think you looked into the mem block size for JTAG, what exactly was the problem there?

what exactly was the problem there?

I don't remember exactly what the symptom was but I was never able to use the entirety of the memory reported by max_mem_block_size

It annoys me a bit, but it's probably best to keep this separate for now. This fixes an issue I had where a transfer would file because it was too big, and it seems to exactly match with the value reported by max_mem_block_size.

If you want to experiment and implement the same for JTAG, I am happy to give it a try. It's possible that I just did something wrong. SWD working is a good enough indicator for that, I think.

Does this impact performance in any way?

No, it just fails without this.

I had a quick look at openOCD / libjaylink and they seem to trait buffer sizes for swd and jtag completely differently. So I think searching for common ground between them is probably wasted effort.


Flatten resource packs at runtime.

This is needed because group resource packs require a lot of patches to work properly, and this is becoming a maintenance burden.
Additionally this was raised because of a feature Continuity needed and flattening the packs make this work much easier.

The FCP has began with the duration of 3 days!


system-loadsave.c: Protect state file from world-readable

The state file might include user-sensitive data, we should prevent accessing it from others than owner.

@michaelrsweet thx, I'll look into it!

I have found more files which can be protected, so I've added them as well.

[master bf52117] Specify restricted permissions for the state file.
The cert/key/csr code is getting overhauled to use the new CUPS X.509 APIs... (#366)


prometheus metrics

It would be great if metrics could be exposed in prometheus format for things like active users, how long it takes to spin up a users container, etc.

Hi @kfox1111
ShinyProxy 2.5.0 is now able to expose Prometheus metrics! You can find all information here https://shinyproxy.io/documentation/usage-statistics/#micrometer .
Although we tried to design and test this feature in a good way, we are looking for some feedback on it. Please open an issue when you have some feedback on it.


How do I make this

Hi, I wanna make my bot respond to a command with a google image search. I know about the google search api but I don't know how to put that into the bot. Also, the thing with clicking the emote to go to the next image and stuff

you cannot do this with such simple bot language

you can do that. but you need to learn the google search api :). if you have any problem join the official discord.io discord https://discord.gg/eMVpmVx

Use the request NPM module found here


Expose stable gamepad UUID

Objective
Expose a stable gameped identifier trackable across app restarts. This is particularly useful with serialization, to save user preferences related to a particular gamepad for example.
Solution
Expose the stable gamepad UUID from gilrs.
Unfortunately it's somewhat unusable at the minute due to the limited platform implementations.
https://gitlab.com/gilrs-project/gilrs/-/issues/153
However I already wrote the change by the time I realized this, so might as well open a PR for it to not lose the work.

Changelog
Added

Added GamepadInfo::uuid, a unique gamepad identifier stable across application restarts.

Added the "S-Controversial" label as I'm not sure about adding a feature that's partially broken? It's nice that it works on some platforms, and that an upgrade to a later gilrs version might make it work across more (if gilrs adds implementations). But at the same time it's a half-broken feature. However I believe the Warning in the docs is enough to prevent users shooting themselves in the foot.
Open for discussing.

Concerning the fact the feature is half-broken. We could potentially implement this in an experimental module, as an extension trait, and have users explicitly import it.

Maybe having a list of plateform on which this works would be more useful.

This is hard to maintain, as this depends on the version of gilrs used, and chances are whoever will update it next will not know/remember to update such a comment.

Due to the limitations highlighted in https://gitlab.com/gilrs-project/gilrs/-/issues/154, this PR is actually wrong, in the sense it's at best over-promising on the uniqueness aspect across reboots, which as far as I can tell from searches in the past 24h is probably impossible in the first place. The best you can get I think is uniqueness while plugged in, which is of limited use. So I think instead a better API would be individual {product ID / vendor ID / bus} triplet, where:

vendor ID / product ID allows identifying the kind of device, for example "Xbox One S Wireless Controller". This is I believe the most common need / most useful feature for most developers.
bus allows identifying where a device is plugged on the machine, for semi-persistent tracking of gamepads while plugged in. This offers a partial mitigation to identifying across application restart 2 identical gamepad models connected to the same machine, while they're not disconnected. However this won't work if the devices are unplugged and replugged, so is of limited use. I believe this is a more niche feature (and harder to implement in gilrs.

https://gitlab.com/gilrs-project/gilrs/-/issues/154 is proposing all of this.


Docker容器内不支持clear 清屏命令

Issue Type
Bug
Source
binary
Secretflow Version
0.8.2b1
OS Platform and Distribution
secretflow/secretflow-anolis8:latest
Python version
3.8.15
Bazel version
/
GCC/Compiler version
/
What happend and What you expected to happen.
容器内不支持Linux常用命令clear，清理终端之前的输出
[root@b1b25a9ca36d ~]# clear
terminals database is inaccessible
[root@b1b25a9ca36d ~]#

Reproduction code to reproduce the issue.
[root@b1b25a9ca36d ~]# clear

clear is not a necessary command tool for SecretFlow but just an optional helper for some users.E.g., For me, I have never used this command -). , and we can even list many commands like clear.
One principal for docker image is to include only necessary content. So I think it's unnecessary to include these in the Dockerfile.

Thank you for  your feedback.


Can I get values from store directly?

Is there anyway to get values from store, not from onSubmit?

Your component is given a values prop with all of them.

What if I want to get values out of the component? For example:
const FormCreatedByRedux = reduxForm({
  form: 'simple',
  fields
})(SimpleForm);

class ParentComponent extends Component {
  render() {
    return (
      <FormCreatedByRedux/>
    );
  }
}

// action creator
export function submitForm() {
  return (dispatch, getState) => {
    // Can I get values here?
  }
}

That is not currently supported, no, but it might be in the future.

Thanks for answering me, I have written an util function to do this, paste here if someone need.
/**
 * A tool to get values from store directly.
 *
 * Warning, currently not support Deep Forms format.
 * For more information, visit https://github.com/erikras/redux-form/issues/372
 *
 * @param {Object in Store} the form object in store,
 * usually use `getState().form.formName` to get it.
 *
 * @returns {Object} the form values, same format with redux-form's values.
 *
 */
export default function getFormValues(form) {
  if (!form) return {};
  return Object.keys(form).filter((key) => !key.startsWith('_')).reduce((prev, key) => {
    prev[key] = form[key].value;
    return prev;
  }, {});
}

Published in v3.1.7.

@erikras it is droped in v6, correct?

Since this is dropped in v6 what is the v6 way of previewing things on the client? I have a form that accepts html I render the html on client (side by side). I don't want the client to submit everytime, get it straight from the store?

@erikras - I have a huge form which needs a custom auto complete component.  Since docs states that the formValueSelector forces the entire form to re-render I looked for an alternative. A work-around I found for this is creating an inputCurrentValue property in the container's state. This is fed down,  through the form and to the auto complete component. The input's normalize function updates inputCurrentValue.
Can you see any issue with this approach?

This can be done. Check out my answer here in stackoverflow.

@ravindraranwala solutiomns worked for me :)

Guys I've used the following solution when needed to get values without direct accessing to store: https://gist.github.com/finom/909e1162003e6b1214d907e04143d56f

If you are worried about unnecessary re-renders you can get the form values like so.
...
import { getFormValues } from 'redux-form'
...

class MyComponent extends Component  {
  // Access store by defining context types
  static contextTypes = {
    store: PropTypes.object,
  }

  // Getter function
  get values() {
    // Get the redux store from context
    const { store } = this.context
    const state = store.getState()
    // Get the form values using the redux-forms getFormValues selector function
    return getFormValues('form-id')(state)
  }

  render() {
    const formValues = this.values
    // Do what you want with the values
    ...
  }
}

I have only tested this using v7 of redux-form

@ravindraranwala     I am trying to access the value of my form in another component, any idea how to do that? https://stackoverflow.com/questions/49591409/how-to-access-redux-form-values-in-another-component


Export-SnipeItCredentials Documentation

It is mentioned about using Export-SnipeItCredentials function, but not where we can get this function from?

Hi @blighter,
Sorry I'm a bit late responding! Export-SnipeItCredentials is the first function contained in SnipeIt-Sync-PS.ps1, as mentioned under Main Functions in SnipeIt-Sync-PS.ps1 in the Readme. You'll have to source the script before you're able to use any of the functions, like so:
. .\SnipeIt-Sync-PS.ps1
All functions have documented help. Example (after dot sourcing SnipeIt-Sync-PS1.ps1):
Export-SnipeItCredentials -?


k8s federation support

k8s federation support, e.g. to be able to deploy to GCE/AWS/Azure

should that not be easier implemented with hosted juju controller?

ICYMI: https://medium.com/@ktsakalozos/federated-k8s-with-on-prem-clusters-and-juju-wip-5d2022379818


Ignore sensor state unavailable on startup generic_thermostat

Breaking Change:

Description:
Everytime i move one of my nodes to ESPHome, i get errors on startup like:
2019-10-07 22:09:34 ERROR (MainThread) [homeassistant.components.generic_thermostat.climate] Unable to update from sensor: could not convert string to float: 'unavailable'
2019-10-07 22:09:39 ERROR (MainThread) [homeassistant.components.generic_thermostat.climate] Unable to update from sensor: could not convert string to float: 'unknown'

See also closed issue https://github.com/home-assistant/home-assistant/issues/20210 where i fixed this for the trend binary sensor.
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Will also solve #22535

Okay, if tests are added

Now you have caught me.
I have absolute no clue how to add tests to this integration.
If someone could take over, please, otherwise it can be closed.

Look to exists tests, I think you see the way after that ;)


Dependency conflict using serde with chrono together

Hello !
I have a project that depends on chrono.If i add the serde dependency with the derive feature, cargo check fails with:
error: failed to select a version for `syn`.
    ... required by package `serde_derive v1.0.152`
    ... which satisfies dependency `serde_derive = "=1.0.152"` of package `serde v1.0.152`
    ... which satisfies dependency `serde = "^1.0.145"` (locked to 1.0.152) of package `serde_spanned v0.6.1`
    ... which satisfies dependency `serde_spanned = "^0.6.1"` (locked to 0.6.1) of package `toml v0.7.2`
    ... which satisfies dependency `toml = "*"` (locked to 0.7.2) of package `twin-commander v0.1.0`
versions that meet the requirements `^1.0.104` are: 1.0.109, 1.0.108, 1.0.107, 1.0.106, 1.0.105, 1.0.104

all possible versions conflict with previously selected packages.

  previously selected package `syn v1.0.103`
    ... which satisfies dependency `syn = "^1.0.95"` (locked to 1.0.103) of package `cxx-build v1.0.82`
    ... which satisfies dependency `cxx-build = "^1.0.34"` (locked to 1.0.82) of package `iana-time-zone-haiku v0.1.1`
    ... which satisfies dependency `iana-time-zone-haiku = "^0.1.1"` (locked to 0.1.1) of package `iana-time-zone v0.1.53`
    ... which satisfies dependency `iana-time-zone = "^0.1.44"` (locked to 0.1.53) of package `chrono v0.4.23`
    ... which satisfies dependency `chrono = "*"` (locked to 0.4.23) of package `twin-commander v0.1.0 `

failed to select a version for `syn` which could resolve this conflict

Could you update the syn crate ? or provide a serde version that works with crhono together? Thank you.

That seems odd. We support the latest syn, so it must be something else restricting the dependency. Have you tried running cargo update?

After running cargo update the project now compiles., thank you.


Update http4s-client, http4s-dsl, ... to 0.23.9

Updates

org.http4s:http4s-client
org.http4s:http4s-dsl
org.http4s:http4s-server

from 0.23.6 to 0.23.9.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #228.


Support for writing multiple documents

@darkfrog26 do you think this syntax will be possible for batch writing multiple documents ?
lucene.docs().fields(
    (id("id1"), email("email1@email.com")),
    (id("id2"), email("email2@email.com"))
  ).index()

From lucene documentation
public long addDocuments(Iterable<? extends Iterable<? extends IndexableField>> docs)
                  throws IOException

What is the reasoning behind this?  From what I've seen, as long as you don't have autoCommit enabled, the performance is quite fast even if inserting millions of documents.

The documentation says
Atomically adds a block of documents with sequentially assigned document IDs, such that an external reader will see all or none of the documents.
I'm assuming that it's similar to LevelDB's batch write operation where all succeed or none incase there is a bad shutdown.

What do you think about syntax like:
lucene.index(
  lucene.doc().fields(id("id1"), email("email1@email.com")),
  lucene.doc().fields(id("id2"), email("email2@email.com"))
)

This would allow you to create multiple documents and batch index them allowing for additional functionality like facet support per document.

Yep. That's much better :)

Okay, any other suggestions before I push a release? :)

That's it. Thank you very much :)


Code cleanup and speedup

Code cleanup

remove unused code
use undefined consistently, short-circuiting, existing functionality, computed values, ...
clean structure of some conditions

Code speedup

optimize zeroFill by ~20%, benchmark added

Looks good. We're in the middle of a big refactoring now, so you'll have to rebase this patch onto the new code once it is merged.

Rebased on top of current develop. @ichernev

@Gobie, thank you! Will merge in next release.

Merged in 49f88864ff411003bfe0550c36defcc75f30d93e


[Feature Request] Custom feature extractor instead of the whole policy

🚀 Feature
In SB3, users can customize the feature extractor solely by setting the sub-parameter feature_extractor_class and  feature_extractor_kwargs of the parameter policy_kwargs, which enables the separating customization of the feature extractor and the net_arch of the full-connected net. I noticed that recently support for using a custom policy was added, but with this feature, we can only customize the whole policy net. So I'm wondering can support for the aforementioned feature, i.e., the separate setting, be added to be consistent with the structure of SB3?
Motivation
No response
Pitch
No response
Alternatives
No response
Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

Hello,
I guess you are referring to https://github.com/DLR-RM/rl-baselines3-zoo/issues/300
We actually discussed that with @ernestum and the correct way to do it would be allow .py instead of .yaml files.
Otherwise, you need a custom SB3 and rl_zoo3 version.

Thanks for your suggestion, I've implemented the whole network and it works well now.


CONTRIBUTING.md needs to be updated

I wanted to start translating but https://github.com/lightsats/lightsats/blob/main/CONTRIBUTING.md is outdated as it still mentions: We use Weblate for Translations: https://hosted.weblate.org/projects/lightsats/

@Wenze thank you! are you ok to submit the translations as a github PR?

@Wenze thank you! are you ok to submit the translations as a github PR?

Yes, I will do so! I will work on the Dutch (Netherlands) translation.


Add Option to Lock theme into certain color or pick color for theme using color picker.

Is your feature request related to a problem? Please describe.
I like to have 3 options called Color Lock , Color Picker and Reset to Defualt-
1.Color Lock-
Use to a lock theme to certain one color picked by album art without changing it per song.
2.Color Picker with Hex code Support-
Manually pick wanted color using color picker and keep that color.
3.Reset to Defualt-
Remove all Color Locking And Picking Settings.
Describe the solution you'd like
1.Color Lock-
When I using this theme it will match color to the current album art Automatically which is awesome,  but think when it does user finds a very beautiful color user wants to set as fixed color in spotify and keep it without changing it's color again when next song starts...So for that Can you add a Color Lock Function?(I Upload some pictures for better understanding..)
(Please Add this option to both player menu and theme menu!)
2.Color Picker with Hex code Support-
Think user needs a custom color (Ex-Orange) So using this user can pick orange color or type relevant hex code and make it fixed color on Spotify as long as he/she wants -
(Please use https://github.com/yairEO/color-picker - Open Source Javascript Minimal Color Picker So it will save some time!😉
3.Reset to Defualt-
Revert all Color Locking And Picking Settings and make theme settings to default So theme will again starts to match color to the playing song Automatically.
        ♦.Color Lock Deactive-

        ♦.Color Lock Active-

        ♦.Menu Normal-

       ♦.Menu  Expanded-

       ♦.Menu with Color Picker-

Is it a feature you would like to work on and open a PR?

I'm Sorry, but I'm not good with javascript (still learning basics of programming! 😅) so I can't do PR  anyhow what i mean is if you can bring this feature to Dynamic Theme it would be awesome! Please try!Thank you!

I'm sorry I currently have zero time I can allocate to new features.

I understand,Thank you anyway for this theme it's awesome...
BTW is it hard to create color lock function without color picker?after all this theme already support changing color so why not to
lock into one already there?


vagrant nfs

We've been using vagrant / virtualbox to develop our websites before pushing them to a live server also running dokku.
We access our development websites through an nfs share allowing us to update the code without restarting the container. We've been using dokku v0.2.3.
I've recently started updating our projects to the latest versions of everything and now get this error.
chown: changing ownership of '/app/public_html': Operation not permitted

It would appear dokku now uses a new user per container and chowns the folder at start, which is fine, but doesn't appear to work with NFS.
Has anyone got any ideas how I can either:

Override this functionality in the dev environment, ie revert to root in each container
Get NFS to play nice with this setup.

For reference this is the line in my vagrant file which sets up the share
  # nfs added
  config.nfs.map_uid = Process.uid
  config.nfs.map_gid = Process.gid

  #websites
  config.vm.synced_folder "/websites/", "/websites",
  type: "nfs",
  mount_options:['actimeo=2']

Interesting. I don't use dokku under nfs. Would rsync maybe be a better option in your case?

Thanks for the very promt response, that's worked, the share folder is 4gb, so it took an eternity to start up the first time, should hopefully be quicker on restart. New settings are
  #websites
  config.vm.synced_folder "/websites/", "/websites",
  type: "rsync",
  rsync__exclude: ".git/",
  rsync__chown:false,
  rsync__auto:true

Closing as this isn't a feature we support and there is an answer available now :)

Just as a note to anyone else having this issue. Rsync is really slow. NFS has file permission issues, but these can be got around with this plugin https://github.com/gael-ian/vagrant-bindfs
I'm sharing a root folder on my mac called /websites/ inside the vagrant box with the following addition to my vagrant file.
  #websites
  config.vm.synced_folder "/websites", "/websites-nfs",
  type: "nfs",
  mount_options:['actimeo=2']
  config.bindfs.bind_folder "/websites-nfs", "/websites",
  perms: "u=rwx:g=rwx:o=rwx",
  options:"nonempty",
  chown_ignore: true,
  chgrp_ignore: true

The fixes the above issue without any loss in performance. Hopefully this will help others who are both developing and deploying with dokku.

That's weird. Rsync has actually been faster for me than nfs. I wonder if the docker aufs setup is screwing around with the local vm performance.
Glad you got to the bottom of this though :)


Support drawing image borders

Hey,
This is super WIP and draft, but I just wanted to see if there is interest to support drawing border as images through kitty's graphic protocol? This is a draft of what it could look like, and uses my fork of hologram.nvim, but it's a working proof of concept.

The border and shadow here are drawn using the cairo API.
Thanks.
edit: update screenshot

The screenshot looks great! 😃
I skimmed through the codes a bit, here's some thoughts:
border is very coupled with the popup component, that's why I think it should be in the popup directory.
Since this is very experimental and heavily tied to Kitty terminal, I'm actually hesitant add first-class support for it. But I absolutely get that Kitty terminal users will be will be delighted to have this. So here's an alternative idea, provide an way to override the built-in border class.
local popup = Popup({
  ...
  border = {
    class = AlternativeBorder,
    ...
  }
  ...
})

That way you're not constrained to the built-in border implementation. As long as you implement the interface (mount, unmount, reposition, resize, _open_window, _close_window, get methods), you're good to go. The properties from popup's border options will get passed to the class you provide, so you're not even constrained by the built-in border options.

Sounds fair! A way to override would work. One thing though, this is meant as a library used by other plugins right? It would be nice if users could set this override in their config once, instead of it being defined on every call to components.

It would be nice if users could set this override in their config once, instead of it being defined on every call to components.

Multiple installed plugin can use nui.nvim. Say one of them uses image border class and it's options. But the others relies on the default border options. So setting them in config once will break some of those plugins. Global config makes sense for plugins, not much for libraries.
But when you're building a plugin using nui.nvim, you can encapsulate your default config in a separate function, for example:
local function create_popup(options)
  local popup = Popup(
    vim.tbl_deep_extend(
      "force",
      { --[[ your default config goes here ]] },
      options
    )
  )
  return popup
end

So that you won't need to write the options for default popup style of your plugin multiple times.


fix: consolidate script tags to fix ts build error

fixes the issue described in https://github.com/cpsoinos/nuxt-svgo/pull/91#issuecomment-1507034145
Problem reproduced locally; with this change, build succeeds.

yes I had done it in two tags because the second one runs on every instance of component while the first tag runs only once

Makes sense - will close this PR and wait for yours. Tag me when ready please?


Client Ugrade Command Not Working in v0.14.1

Summary of Bug
The command hermes tx raw upgrade-client is failing in v0.14.1, but working in v0.14.0.
I believe it's due to this issue: https://github.com/informalsystems/ibc-rs/pull/2021
The command tries to fetch the upgraded consensus state from the last block of the old chain but fails to find it, because it uses the wrong block height.
Previously it used the last block as reported by /status rpc, but now uses another method. When the chain halts, the two methods differ: /status returns the uncommited halted height (listed in the upgrade plan), the other returns the last commited height (one before the upgrade plan).
Note, although technically the last commited consensus state is for one block before the upgrade height, the cosmo-sdk upgrade querier stores it under the upgrade height.
Version
v0.14.1
Steps to Reproduce

Acceptance Criteria

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Hmm, this is an interesting corner-case. Thanks for bringing it to our attention!


added code to send sms using sms_using_python.py

craete proper description and follow rules( star+follow+fork)

Added code used to send SMS using python, a user needs to create credentials on Twilio and the script starts working.

will merge soon :)


LANG-1146 Add helper method to SystemUtils.java for zOS identification

@britter Could you review? Thanks

Hello @gliptak,
sorry for the delay. There are a lot of pending PRs but I don't have time for OSS at the moment :-( I'll have a look as soon as I have more time again.
Benedikt

@garydgregory The one reference i'm seeing is at
http://public.dhe.ibm.com/common/ssi/ecm/zs/en/zsl03071usen/ZSL03071USEN.PDF
The system property os.arch for IBM SDK for z/OS, version 1.4.2 (31-bit)
versions and earlier had a value of 390. From Java 5.0 onwards, the value of
os.arch is s390.
I'm not sure of the "z/os" reference as described at:
http://www.java2s.com/Tutorial/Java/0120__Development/ConditionthatteststheOStype.htm

Benedikt, would this be still of interest? Thanks

Can we come up a check that works on all version of z/OS?

I do not have access to Java running on various mainframes. If somebody is able to list out the combinations, I'm open to code it.

Here are some sys props from one of our z/OS systems:
Start system properties (71):
awt.toolkit = sun.awt.X11.XToolkit
com.ibm.cpu.endian = big
com.ibm.jcl.checkClassPath =
com.ibm.oti.configuration = scar
com.ibm.oti.jcl.build = 20150630_255633
com.ibm.oti.shared.enabled = false
com.ibm.oti.vm.bootstrap.library.path = /rsusr/java/IBM/J8.0_64/lib/s390x/compressedrefs:/rsusr/java/IBM/J8.0_64/lib/s390x
com.ibm.oti.vm.library.version = 28
com.ibm.packed.version = 2
com.ibm.system.agent.path = /rsusr/java/IBM/J8.0_64/lib/s390x
com.ibm.util.extralibs.properties =
com.ibm.vm.bitmode = 64
com.ibm.zero.version = 2
file.encoding = IBM-1047
file.encoding.pkg = sun.io
file.separator = /
ibm.signalhandling.rs = false
ibm.signalhandling.sigchain = false
ibm.signalhandling.sigint = true
ibm.system.encoding = IBM-1047
java.awt.fonts =
java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
java.awt.printerjob = sun.print.PSPrinterJob
java.class.path = ***
java.class.version = 52.0
java.compiler = j9jit28
java.endorsed.dirs = /rsusr/java/IBM/J8.0_64/lib/endorsed
java.ext.dirs = /rsusr/java/IBM/J8.0_64/lib/ext
java.fullversion = JRE 1.8.0 IBM J9 2.8 z/OS s390x-64 Compressed References 20150630_255633 (JIT enabled, AOT enabled)
J9VM - R28_jvm.28_20150630_1742_B255633
JIT  - tr.r14.java_20150625_95081.01
GC   - R28_jvm.28_20150630_1742_B255633_CMPRSS
J9CL - 20150630_255633
java.home = /rsusr/java/IBM/J8.0_64
java.io.tmpdir = /tmp
java.library.path = ***
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = pmz6480sr1fp10-20150716_01 (SR1 FP10)
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.8
java.util.prefs.PreferencesFactory = java.util.prefs.FileSystemPreferencesFactory
java.vendor = IBM Corporation
java.vendor.url = http://www.ibm.com/
java.version = 1.8.0
java.vm.info = JRE 1.8.0 z/OS s390x-64 Compressed References 20150630_255633 (JIT enabled, AOT enabled)
J9VM - R28_jvm.28_20150630_1742_B255633
JIT  - tr.r14.java_20150625_95081.01
GC   - R28_jvm.28_20150630_1742_B255633_CMPRSS
J9CL - 20150630_255633
java.vm.name = IBM J9 VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.8
java.vm.vendor = IBM Corporation
java.vm.version = 2.8
line.separator = 0x15
os.arch = s390x
os.encoding = ISO8859_1
os.name = z/OS
os.version = 02.02.00
path.separator = :
platform.notASCII = true
sun.arch.data.model = 64
sun.boot.class.path = ***
sun.boot.library.path = ***
sun.cpu.endian = big
sun.io.unicode.encoding = UnicodeBig
sun.java.command = ***
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = IBM-1047
sun.security.policy.utf8 = false
user.country = US
user.dir = ***
user.home = ***
user.language = en
user.name = ***
user.timezone = GMT-05:00
user.variant =

@garydgregory This above is covered by this pull request.

See Git master for an alternate solution. You can close https://issues.apache.org/jira/browse/LANG-1146 and this issue if you like the solution and/or can test on z/OS.


on H2 after 2.0 don't need column type workaround (H5)

Apparently H2 correctly reports column types via JDBC metadata since 2.0, so this workaround is unnecessary.
Also add a default mapping for DECIMAL in superclass, just for completeness.
cc @famod WDYT? Does this look good?

Thanks!


chore: Fix test failures

Description

Fix Junit tests failing on local machine as CI is buggy and somehow not detecting tests failures.

Fixes #13296
Type of change

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

How Has This Been Tested?

Locally ran

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=90d97d6

/ok-to-test sha=2fb1144

/ok-to-test sha=a2593ac


The 'AWSToolkitPackage' package did not load correctly

Computer (please complete the following information):

Windows Version: Windows 11
Visual Studio Version: Visual Studio 2022 17.7
AWS Toolkit for Visual Studio Version:  <IP_ADDRESS>

Install log
The installation is successful in vsix but when running, it encounters this warning:

Here are the contents of the ActivityLog: https://github.com/mikiwijiki/storage/blob/c151b3b139a4976caaca635a8f84a514cc522eb6/ActivityLog.xml
Any other information
I tried this https://github.com/aws/aws-toolkit-visual-studio/issues/138 but it didn't work on my end. I think this is another case.

Hi @mikiwijiki thanks for reaching out,
It does look like you are encountering the same problem: System.MissingMethodException: Method not found: 'Amazon.Runtime.Internal.Settings.IPersistenceManager Amazon.Runtime.Internal.Settings.PersistenceManager.get_Instance()
Can you try following the instructions from this comment and share your corresponding screenshots?


Display python debug configurations in launch.json

For #7304

Codecov Report

Merging #7403 into master will decrease coverage by 0.79%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #7403     +/-   ##
=========================================
- Coverage   58.47%   57.68%   -0.8%
=========================================
  Files         493      493
  Lines       21782    21430    -352
  Branches     3494     3489      -5
=========================================
- Hits        12738    12362    -376
- Misses       8257     8277     +20
- Partials      787      791      +4

Impacted Files
Coverage Δ

src/client/debugger/extension/serviceRegistry.ts
100% <ø> (ø)
:arrow_up:

...nt/datascience/jupyter/invalidNotebookFileError.ts
0% <0%> (-75%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
0% <0%> (-66.67%)
:arrow_down:

...science/jupyter/jupyterKernelPromiseFailedError.ts
0% <0%> (-50%)
:arrow_down:

...ent/datascience/jupyter/jupyterWaitForIdleError.ts
0% <0%> (-50%)
:arrow_down:

src/client/api.ts
60% <0%> (-27.5%)
:arrow_down:

src/client/common/utils/platform.ts
64.7% <0%> (-23.53%)
:arrow_down:

src/client/language/characters.ts
12% <0%> (-21.34%)
:arrow_down:

src/client/testing/codeLenses/main.ts
60% <0%> (-17.78%)
:arrow_down:

src/client/datascience/cellFactory.ts
72.34% <0%> (-17.32%)
:arrow_down:

... and 34 more

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 40a1d04...35c96cc. Read the comment docs.


remove salesforce DMP from salesforce list

Proposed changes
Salesforce DMP is in private beta, and was built 4+ years ago for Fox specifically. No customers should be using this destination, and StratConn is investigating deprecating it. In the meantime, I would like to remove it from the Salesforce nav in our docs, so customers cannot find the doc. It is already hidden but is still appear in the left-hand column:

I think this is because the strat = salesforce. If there's another reason it is still appearing, please update this PR to remove that. I don't see it when I'm searching so I think it is unindexed already.
Merge timing

ASAP once approved

Related issues (optional)

@kdaswani Should we just unpublish this completely?

Good question! Let's keep it unindexed for now just in case Fox still needs to reference it. In my JIRA to eventually deprecate, I've added a note to make sure we unpublish upon deprecation: https://segment.atlassian.net/browse/STRATCONN-1151. Thank you!


Implication is that you can use if to detect when a resource exists, but example on if page doesn't do that.

Text says "Use the if function to make sure the function is only evaluated when the resource exists." but the example shows only how to do it when you are conditionally creating the resource, the example does not test for existence of a previously created resource. Is it possible to test for the existence of a previously created resource or not?

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

ID: 85bba21f-ef02-381c-48bd-0ced44cc513f
Version Independent ID: c56b631f-e9f4-39ea-c2b2-a46132e5c286
Content: Azure Resource Manager template functions - resources
Content Source: articles/azure-resource-manager/resource-group-template-functions-resource.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@IanMercer Thanks for the Comment. We are actively investigating and will get back to you soon.
@tfitzmac Could you please review this request and provide expert suggestions on the same?

@IanMercer - I have submitted a change to clarify that the if function is used to test whether the resource is being deployed, rather than whether it exists. There is not a way to test if a resource exists. Typically, you would pass in a parameter that indicates the state of the resource, but it is there something about your scenario that makes it difficult to know before deployment if the resource exists?

@tfitzmac Yes, we are deploying multiple environments (dev, test, stage, ...) into a single ASE but the App Gateway needs to know about all of them so it can configure itself to route traffic to each environment that has been installed. So currently there is no way to do this using ARM templates. App Gateway cannot be used in an additive fashion to add rules/back end pools, but must install all of them in one go. Our workaround for now is to have two parameters: the name of the environment you are installing and an array listing all of the environments that have ever been installed. It works, but it's fragile.


Provide updated version of demo app to use .NET 7 instead of .NET 5

Hello,
.NET 5 has reached end of life and has security vulnerabilities: https://dotnet.microsoft.com/en-us/download/dotnet/5.0
Is it planned to provided an updated version of the VC demo app that works on .NET 7 ?
Thank you,

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

ID: e85be67f-8375-6229-18aa-d687463991f9
Version Independent ID: c494773d-9fcc-d733-6ddb-935a8e545abd
Content: Tutorial - Issue Microsoft Entra Verified ID credentials from an application - Microsoft Entra
Content Source: articles/active-directory/verifiable-credentials/verifiable-credentials-configure-issuer.md
Service: decentralized-identity
Sub-service: verifiable-credentials
GitHub Login: @barclayn
Microsoft Alias: barclayn

@khbafl
I've delegated this to @barclayn, a content author, to review and share their valuable insights.


Unknown webpack Warning while building

> phenomic build

⚡ Hey! Let's get on with it
(node:7127) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
Warning: %s 9:12-34 Critical dependency: the request of a dependency is an expression
📦 Webpack server side done 19576ms
📝 Got your content 110ms
📃 Pre-rendering done 298ms
📦 Webpack built 51224ms

It's a webpack warning.


Imbalanced Stoichiometry/ Missing Atom Mapping

Hi all, I was hoping to get some help/ information with regards to mapping reactions which are imbalanced. I have a pipeline which utilises rxnmapper for AAM, downstream a template is extracted and then validated. On a private dataset there is an unacceptable amount of failed validations.
For reproducibility in this issue I have checked for the same validation failures on USPTO. For USPTO these failures appear to relate back to: mapping where the reaction is imbalanced / there is implied stoichiometry and atom map numbers are not repeated on the RHS / missing.
Some examples:
example_n,original_uspto,pre_mapping,post_mapping
0,[C:1](#[N:4])[CH:2]=[CH2:3].[NH3:5]>>[C:1]([CH2:2][CH2:3][NH:5][CH2:3][CH2:2][C:1]#[N:4])#[N:4],C=CC#N.N>>N#CCCNCCC#N,[CH2:2]=[CH:7][C:8]#[N:9].[NH3:1]>>[N:1]#[C:2][CH2:3][CH2:4][NH:5][CH2:6][CH2:7][C:8]#[N:9]
1,[CH2:1]([C:4]#[N:5])[CH2:2][OH:3]>O>[C:4]([CH2:1][CH2:2][O:3][CH2:2][CH2:1][C:4]#[N:5])#[N:5],N#CCCO.O>>N#CCCOCCC#N,[N:1]#[C:2][CH2:3][CH2:4][OH:5]>>[N:1]#[C:2][CH2:3][CH2:4][O:5][CH2:6][CH2:7][C:8]#[N:9]
2,[CH2:1]([NH2:4])[CH2:2][NH2:3].[CH:5]([CH:7]=O)=O>>[NH:3]1[CH:2]2[NH:3][CH2:5][CH2:7][NH:4][CH:1]2[NH:4][CH2:1][CH2:2]1,NCCN.O=CC=O>>C1CNC2NCCNC2N1,O=[CH:1][CH:7]=O.[CH2:2]([NH2:3])[CH2:4][NH2:5]>>[CH2:1]1[CH2:2][NH:3][CH:4]2[NH:5][CH2:6][CH2:7][NH:8][CH:9]2[NH:10]1

it appears that there should be 2x "C=CC#N" and maybe that atom maps 2, 7, 8 and 9 should be repeated on the RHS?
2x "N#CCCO" are required, 1-4 "  "
2x "NCCN" are required, 2-5 "  "

Is it realistic of me to expect that rxnmapper should handle imbalanced reactions in the manner I've described or should these be balanced prior to mapping? Please let me know if any further information or examples are required.
Appreciate your assistance with this.
Other information
This is using rxnmapper 0.2.0, outcome is the same irrespective of canonicalize_rxns=False or True.
Note that SMILES in 'pre_mapping' have undergone a standardisation process and those in 'post_mapping' have had molecules with no atom mapping removed.

Thanks, @avaucher. At present this is sufficient information. However, in future, it would be excellent to see this introduced as a new feature. I will re-raise this in future if I can obtain sufficient justification and more examples including output from other AAM tools re-using reactants.