Update inf-copyfiles-directive.md

Added some clarity about the necessity of SourceDisksFiles and SourceDisksNames for files specified via CopyFiles

Hi @zlockard, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


Perf improvements

Motivation:
Metrics collecting systems should be efficient enough so that their
impact on the system being instrumented is negligible.
Modifications:

Store PromMetrics in a dictionary keyed by label in
PrometheusClient; this gives fast lookup when checking if a metric
already exists
Remove the metricTypeMap, we can recover the same information from
PromMetric
Remove calls to getMetricInstrumet in PrometheusMetricsFactory
these were redundant as the same check is done in createCounter etc.
In each createCounter (etc.) call we now hold the lock for the
duration of the call to avoid races between checking the cache and
creating and storing a new metric.
The PrometheusLabelSanitizer now checks whether input needs
santizing instead of santizing all input
Sanitizing is done in one step, mapping each utf8 code point to a
sanitized code point rather than lowercasing and then checking the
validity of each character.

Result:

Sanitizing pre-sanitized labels is ~100x faster
Sanitizing non-sanitized label is ~20x faster
Incrementing 10 counters is ~20x faster
Incrementing 100 counters is ~40x faster
Incrementing 1000 counters is ~250x faster
(Similar results for other metrics.)

Checklist

[x] The provided tests still run.
[x] I've created new tests where needed.
[x] I've updated the documentation if necessary.

Released in Alpha 11


Getting XML Response while passing Json Payload

Hi Team,
I am passing input payload as Json and getting Json in response from Postman, but when i tried the same with karate i.e
while passing Json as payload request the response generated is in XMl format.
Is there any this we can do to get this in Json response itself.
As a work around converted the xml to json but curious to know if i am doing anything wrong here.
@ptrthomas could you please help out here
https://stackoverflow.com/questions/tagged/karate

@nngrjg follow this process exactly as described to re-open please: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue

Thanks, but i could share the project as this is completely internal.
Any other way to get support.

@nngrjg use stack overflow. that said I'm pretty sure the solution you need is here: https://github.com/karatelabs/karate/issues/388#issuecomment-386845749

i tried using the accept header but, my issue is that i am expecting json response but getting in xml

@nngrjg I don't think anyone here can help you. all the best !


Update automated-backup-sql-2014.md

Changed the retention period

Docs Build status updates of commit 23c3d44:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-sql/virtual-machines/windows/automated-backup-sql-2014.md
:white_check_mark:Succeeded

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

@bluefooted

Can you review this PR?

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Create a new superuser role

Original report on BitBucket by Maja Dolinar.

In order to distinguish between the roles ADMIN_CONTENT and ROLE_ADMIN, we need to create a new superuser role. ADMIN_CONTENT should have content rights and user management rights in the system, whereas ROLE_ADMIN should have all rights. Need to create a new table for this.

See table: https://docs.google.com/spreadsheets/d/1wLKK0B5SrSsGsOO7PtZW3E7QPBuJUmwzRHV_WtljNSY/edit#gid=0
currently the role ADMIN_CONTENT does not have user management rights in the system (I as a user in CVS need to have now 2 roles assigned: ROLE_ADMIN_CONTENT and ROLE_ADMIN to be able to manage users). In the future I should have only the ROLE_ADMIN_CONTENT
ROLE_ADMIN should have all rights.
See previously closed issue for this https://github.com/cessda/cessda.cvs.two/issues/395: ROLE_ADMIN_CONTENT and ROLE_ADMIN were clashing, because they had the same rights in the system. For release 3.0.0 we will not include User management roles for ROLE_ADMIN_CONTENT, and have ROLE_ADMIN assigned to user that need user management.

So I am little bit confused. The plan is to have only one role admin?
Martin
On Wed, Mar 22, 2023, 14:13 MajaDolinar @.***> wrote:

See table:
https://docs.google.com/spreadsheets/d/1wLKK0B5SrSsGsOO7PtZW3E7QPBuJUmwzRHV_WtljNSY/edit#gid=0
currently the role ADMIN_CONTENT does not have user management rights in
the system (I as a user in CVS need to have now 2 roles assigned:
ROLE_ADMIN_CONTENT and ROLE_ADMIN to be able to manage users). In the
future I should have only the ROLE_ADMIN_CONTENT
ROLE_ADMIN should have all rights.
See previously closed issue for this #395
https://github.com/cessda/cessda.cvs.two/issues/395: ROLE_ADMIN_CONTENT
and ROLE_ADMIN were clashing, because they had the same rights in the
system. For release 3.0.0 we will not include User management roles for
ROLE_ADMIN_CONTENT, and have ROLE_ADMIN assigned to user that need user
management.
—
Reply to this email directly, view it on GitHub
https://github.com/cessda/cessda.cvs.two/issues/472#issuecomment-1479547536,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB23PTS25I6YNS2IY3UP3PTW5L3G5ANCNFSM6AAAAAAWDZLLAU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I am not sure what other rights there are in the system that are connected to maintenance, if any. Maybe @john-shepherdson or @Joshua-cessda-admin can help in this? I think that only the rights of accessing some technical part of the service would separate ROLE_ADMIN_CONTENT and ROLE_ADMIN probably.

That make sense to me. If this is the correct approach I can implement it
like that.
On Wed, Mar 22, 2023, 20:31 MajaDolinar @.***> wrote:

I am not sure what other rights there are in the system that are connected
to maintenance, if any. Maybe @john-shepherdson
https://github.com/john-shepherdson or @Joshua-cessda-admin
https://github.com/Joshua-cessda-admin can help in this? I think that
only the rights of accessing some technical part of the service would
separate ROLE_ADMIN_CONTENT and ROLE_ADMIN probably.
—
Reply to this email directly, view it on GitHub
https://github.com/cessda/cessda.cvs.two/issues/472#issuecomment-1480143213,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB23PTVUQC2WUARZNYMZXB3W5NHSPANCNFSM6AAAAAAWDZLLAU
.
You are receiving this because you commented.Message ID: <cessda/cessda.
@.***>

Nothing to add

@MajaDolinar the roles should be solved. I also solve the problems with TECHNICAL_ADMIN (nobody noticed, that it probably doesn't work). @Joshocan @john-shepherdson I need also to modify the application.yml, where the health section can be accessed only by ADMIN, not TECHNICAL_ADMIN. I don't know, if there are other configurations on the production, but to be sure, the roles are right also on the production. @MajaDolinar I have merged the code with the master, so in few minutes/hours it should be on dev and/or staging and you shpould be able to test it. If not, @Joshocan please check the deployment as it breaks sometimes. Thanks

needs testing

ROLE_ADMIN_CONTENT is working for user management as well. The issue is resolved.


Is this a ongoing project?

I am looking into batch solutions... Are you still developing this?
Is the current state of the code usefull, can i implement and use it?
If so I will figure out how :)

Hi @MrGekko ,
this project is currently stalled, because I do not have too much time to invest in it. I recommend you to check Symfony2 Process Component and the icicle project.


Multiplayer skeleton

I wrote a simple multiplayer server skeleton. All code with the todo! macro should be implemented by students on the webinar.

Let me know if it's ready to be merged please.


[Bug]: IDAKLU solver error

PyBaMM Version
23.4.1
Python Version
3.9
Describe the bug
RuntimeError:C:..\casadi\core\serialization_stream.cpp:355:Assertion"load_version==v" failed:ProtoFunction failed. Object written in version 2 but can only read in version 1.
Steps to Reproduce
import pybamm
import numpy as np
model = pybamm.lithium_ion.SPM()
geometry = model.default_geometry
param = model.default_parameter_values
param.process_model(model)
param.process_geometry(geometry)
mesh = pybamm.Mesh(geometry,model.default_submesh_types,model.default_var_pts)
disc = pybamm.Discretisation(mesh,model.default_spatial_methods)
disc.process_model(model)
t_eval = np.linspace(0,3600,100)
if pybamm.have_idaklu():
     klu_sol = pybamm.IDAKLUSolver(atol=1e-8,rtol=1e-8).solve(model,t_eval)
plot = pybamm.Quickplot(klu_sol)
plot.dynamic_plot()

Relevant log output
No response

Strange, it works at my end (even with version 23.4.1). Could be that when you upgraded to the newer PyBaMM version, casadi didn't. Can you try upgrading both PyBaMM and Casadi to their respective latest versions?

I have upgrade pybamm and casadi to their newest version.(pybamm=23.5 casadi=3.6.3) But the problem still exist. Is that has something to do with the version of c++?

I downgraded  pybamm to version 22.10 and casadi to version 3.5.5, which solved the problem.

Reopening as suggested in https://github.com/pybamm-team/PyBaMM/discussions/3193#discussioncomment-6563103
We need to find out why the newer pybamm or casadi version breaks this

Reopening as the issue has reemerged, including in pip installs of pybamm. See #3193 for related discussion.

Some progress - Given the new information I have managed to recreate the serialisation error on my (working) machine by taking the following actions:

Removed/renamed ~/local to remove any existing (local) casadi installs.
Build casadi from source following their instructions (this required casadi version 3.5.5 which builds libcasadi.3.6.dylib, not version 3.6.0 which actually builds libcasadi.3.7.dylib.
Reinstall PyBaMM using nox (pybamm-requires then dev)
Test the installation using the script provided in #3193

After that I receive the Assertion "load_version==v" failed: DeSerialization of ProtoFunction failed. Object written in version 2 but can only read in version 1. error. This only impacts the new build/install, my previous installation still works fine.
So it seems that this error is in-fact due to a mismatch in the version of casadi used in Python conflicting with the version that IDAKLU uses to link at build time. Removing casadi installs outside of PyBaMM prior to install should resolve this, but I acknowledge that this is not an ideal solution and the installer should instead prioritise the python install over the system install to maintain synchrony. Further, it is not clear to me how or why this is impacting the wheels (did the wheel itself build using two casadi versions?). Now that we have a reprodicuble testbed for examining the issue we should be able to make further progress.

@jsbrittain @agriyakhetarpal The CMakeLists.txt fix works for me too!

@agriyakhetarpal Removing the registry definitely sounds like the most maintainable solution going forwards. I took a quick look at the error from your Windows wheel build with python-casadi and, comparing it to the PyPI package listings, it looks as though there may be a misreferenced file in the casadi cmake targets (libcasadi.lib is requested, but only casadi.lib exists); I'll need to get hold of a Windows machine to see if this actually resolves the build issue, but even if it does that would mean an upstream change in the casadi codebase (we might be able to hotfix it at our end in the meantime, but that wouldn't be stable for subsequent releases). Have you tried this with the latest casadi release (3.6.4)?

I haven't tried it with the latest casadi release yet since they don't seem to provide any minor version compatibility of sorts (based on the many, many changes between 3.6.3 and 3.6.4 as noted in the release notes); but there should be no harm in trying that—I will update my fork of the registry again, try both the Python and vcpkg casadi and get back to this—maybe they fixed this on their end. I had chosen 3.6.3 specifically to synchronise the versions for the build-time and run-time dependencies, but I suppose pip downloads the latest version anyway unless we don't pin them.

@agriyakhetarpal Thanks a lot for your efforts to solve this issue! I have tested both wheel files in separate virtual environments on Windows for python version 3.9. I am glad to say that in both cases the serialization error disappeared.
I am not able to follow your discussions above, but I hope it is ok that pip show prints the casadi version 3.6.4 in both cases.

Thanks for confirming! Yes, pip show casadi displaying 3.6.4 as the output is fine. I guess the gist is that the casadi has to be 3.6.X for the serialisation to work properly and a difference between the patch versions at runtime should be okay, but linking and running with different minor versions (say, 3.5.X vs 3.6) might cause issues as has been the case here.
Tagging @martinjrobins to request for write access to the casadi vcpkg registry (I think merging a PR from my end there will require a further, redundant update to the git-trees so it would be great to directly push) and then this issue can be closed with an update to the baseline commit in the vcpkg configuration file.
P.S. I will open a new, separate issue to explore the possibility of moving away from the registry and getting back to using the Python casadi again. It looks like it can be fixed with a patch on our end, but I don't have enough experience to comment about that procedure haha


WIP: feature/consoleBuildNg

#51
Needs cloneRepository for successful testing

Currently buildNg will always compile in the folder dist, because of the usage of 'ng build --output-path dist' and the will ignore the outputPath in angular.json, because assertion will always look for dist. Alternatively, i would need to get the outputPath key from angular.json to control successful compilation. Which way would be better? @GuentherJulian

Currently buildNg will always compile in the folder dist, because of the usage of 'ng build --output-path dist' and the will ignore the outputPath in angular.json, because assertion will always look for dist. Alternatively, i would need to get the outputPath key from angular.json to control successful compilation. Which way would be better? @GuentherJulian

Currently buildNg will always compile to the folder dist, because of the usage of 'ng build --output-path dist' and will ignore the outputPath in angular.json, because the assertion will always look for dist directory. Alternatively, i would need to get the outputPath key from angular.json to control successful compilation. Which way would be better? @GuentherJulian

We can pass the output folder as a second optional parameter. If the user pass the paramter to the function we can simply check in the assertion if this directory exists. If no output parameter is given then we use the normal output path specified in the angular.json file. Is there a simple way to extract this path from the file?

Currently buildNg will always compile to the folder dist, because of the usage of 'ng build --output-path dist' and will ignore the outputPath in angular.json, because the assertion will always look for dist directory. Alternatively, i would need to get the outputPath key from angular.json to control successful compilation. Which way would be better? @GuentherJulian

We can pass the output folder as a second optional parameter. If the user pass the paramter to the function we can simply check in the assertion if this directory exists. If no output parameter is given then we use the normal output path specified in the angular.json file. Is there a simple way to extract this path from the file?

Currently buildNg will always compile to the folder dist, because of the usage of 'ng build --output-path dist' and will ignore the outputPath in angular.json, because the assertion will always look for dist directory. Alternatively, i would need to get the outputPath key from angular.json to control successful compilation. Which way would be better? @GuentherJulian

We can pass the output folder as a second optional parameter. If the user pass the paramter to the function we can simply check in the assertion if this directory exists. If no output parameter is given then we use the normal output path specified in the angular.json file. Is there a simple way to extract this path from the file?

Currently buildNg will always compile to the folder dist, because of the usage of 'ng build --output-path dist' and will ignore the outputPath in angular.json, because the assertion will always look for dist directory. Alternatively, i would need to get the outputPath key from angular.json to control successful compilation. Which way would be better? @GuentherJulian

We can pass the output folder as a second optional parameter. If the user pass the paramter to the function we can simply check in the assertion if this directory exists. If no output parameter is given then we use the normal output path specified in the angular.json file. Is there a simple way to extract this path from the file?

Currently I'm not able to find out why the ng build command is executed succesfully in linux pipeline but not on windows.

Currently I'm not able to find out why the ng build command is executed succesfully in linux pipeline but not on windows.


Updated instructions in readme

@krook @narengan @mrodrise : please see updated instructions to install MariaDB in docker and IKS.

@krook it needs intro section, but the steps are all complete.


Visualization script is missing

Hi,
Awesome work! I'm curious to know if you can share the activation map or visualization script.

Unfortunately, the visualization script is missing, you can re-implement it with Grad-CAM .

@JiaweiZhao-git Thanks solved this issue.


Backport 2.16: Fix CMake build error on Cygwin and minGW platforms

Backport of #2473

Rebased to address @RonEld's comment on the parent PR.


Compatibility with Twitch 3rd-party addons

With this change, Twitch 3rd-party addons like this one will be compatible with this auto-clicker.

Hey! Any updates on this?

Sorry! This slipped by me. Thanks :+1:


504: Gateway Timeout when trying to add .gitignore behind proxy

The 'Add gitignore' command does not seem to work when behing a proxy : it generates a 504: Gateway Timeout error message.
The following environment variables http_proxy and https_proxy are set.
And VScode is respecting them since i could download the extension.

Thank you for reporting this issue. I will take a closer look at this.

I just asked the Visual Studio Code team what would be the recommended way to support proxy from an extension other than writing everything from scratch or copy&paste code from Visual Studio Code code base. As soon as I receive feedback I will post an update here and start with the implementation.

I too am hitting this issue

I think the proper way would be to pull the proxy information from the configurations.  If i understand the documentation correctly the workspace.getconfig command actually pulls a merged Global config with settings in workspace config overwriting the globals.
Then i guess since code is available on github you might be able to extract the http request they use when it uses the proxy.  I believe it's in the extensions code section.

@ibigpapa: Thanks for your research. I came up with almost the same solution when I was looking for a solution. As the implementation is already part of Visual Studio Code, I asked them if they could expose the proxy settings through an API (see https://github.com/Microsoft/vscode/issues/12588). So far I have no information if the node package has been published.
As I have some time this weekend, I plan to implement proxy support this weekend by copy&paste the vscode implementation and publish it as version 0.5.0.

I just completed the proxy support implementation and tested it with a proxy set by Visual Studio Code settings.
@ibigpapa @LaurentChardin I would very much appreciate if you find some time installing the alpha version at the end of this comment and verify if this versions works with your proxy setup. Thanks a lot.
Alpha version: https://drive.google.com/open?id=0B6-NC49ru2VGMTdSYjZ2dV96STg

I have tested the 0.50-alpha version and it works with my proxy settings!
I had previously also the problems as described by @ibigpapa .
Thanks!

Tested on my system without a proxy and works just fine.  Turned on the proxy and tested again and it still works 👍

Thank you @jeedev0815 and @ibigpapa for the feedback. I will release the new version within the next days.


normalize placeholder fonts

this will prevent placeholder text from being bold / italic / underlined randomly (if the font styles are applied to the item it's a placeholder for)

Coverage remained the same at 87.782% when pulling 4ba090ae0fda42b1bfacb6c3be79883a26b15ea3 on normalize-placeholder into 364eaa7544a02f066dde137841dbcd62fb666282 on master.


Change scrolling approach for Table component

Feature Request
The Table component has quite an annoying problem - it doesn't allow horizontal scrolling. I think a lot of people got into the trap due to this issue.
Even though the Table is not designed to be horizontally scrollable, developers don't believe that it's indeed not scrollable at all. That's a big surprise to find out later that it's really not horizontally scrollable, even 1 px - no. Personally I thought that the Table simply doesn't support column virtualization, but not really ability to scroll horizontally.
I checked how the Table's scrolling works. It appears that the scollable area includes only data rows, but doesn't include the header row.
Ok, I tried to add a horizontal scrollbar in the scrollable area, but obviously this won't work, because header won't scroll. Well, we can try to subscribe to scrolling events and programmatically scroll the header area, but that won't work well, because the header will have a scrolling lag (as in the MultiGrid with fixed rows).
Then I tried to add a horizontal scrollbar to a parent (which contains the Table) container. But this also doesn't work, because the inner vertical scrollbar obviously gets out of the visible parent area if there's something to scroll horizontally.
So, I suggest changing the Table's scrolling approach so that the scrollable area includes the header, and make the header sticky (with position:sticky).
With this change, we can enable the horizontal scrollbar right in the scrollable area of the Table.
Probably there was a reason why this wasn't done in the first place, but still I dared to add this feature request :)
We can use MultiGrid instead of Table, but hey... doesn't it look ironic that we should use MultiGrid to simulate Table? :)

Assign me this issue


Updated bower.sh

After this change, the new version of CartoDB.js wasn't being calculated correctly. This (hopefully) fixes it.
cc/ @matallo

cool, I feel confident of your changes (my bad as they worked for the first version :disappointed: )

Thanks! :+1:


[ST4] Upgrade from ST3 required reinstall of this package

With ST4 officially out, I tried setting SCCS syntax on a couple of files, and it wasn't coming up as an option in my list of syntax(es).
I uninstalled the package and reinstalled using Package Manager -- the version I had installed was 2.5.0, and on reinstallation it was still 2.5.0.
Unfortunately I'm not sure I can replicate this process to see why it wasn't initially working. I had quit and restarted ST after the upgrade and before I tried using this package, so I know it wasn't that. And other packages I had did make the upgrade in working order. But I thought I'd report it in case you wanted to investigate the upgrade path.
Thanks for maintaining this!

Hm, I'm afraid that upgrade path is a bit out of my hands. I think what happens is that the st3 version is registered as incompatible with st4 and package control therefore unloads it... not sure if it does that actually. Anyway, when you restart st4, it should pick up the latest st4 version of this package and all is good again. It should be "self healing" in that way, and I wonder why that didn't happen for you. Although I would not be surprised if it took 1 restart to go from 3 to 4, then another restart to upgrade all packages, and then a third one to properly reload all packages and dependencies.
I'll keep an eye out for similar reports, there are more packages out there with separate st3 and st4 releases like this one.


Properly deal with .hic files with missing normalization vectors

Dealing with missing weights in .hic files is a bit tricky, because weights are stored individually for each chromosome, and it is not guaranteed that all chromosomes have balancing weights for a given method.
This PR implements a check that results in an exception being thrown when attempting to open a normalized Hi-C chromosome-chromosome matrix with a normalization method that is not available in any chromosome.
Closes #160

Codecov Report
Attention: Patch coverage is 75.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 84.79%. Comparing base (64cd410) to head (475224b).

Files
Patch %
Lines

...tk/hic/include/hictk/hic/impl/file_reader_impl.hpp
75.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #162      +/-   ##
==========================================
- Coverage   84.86%   84.79%   -0.08%
==========================================
  Files         117      117
  Lines       10031    10036       +5
==========================================
- Hits         8513     8510       -3
- Misses       1518     1526       +8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Portrait taken images are shown in landscape mode

Hi,
I'm implimenting the Android social media application and it has feed layout which shows high resulution images in ListView. Just after taken the photo i'm uploading image to web service and then application is loading feed screen. The top feed shows latest image that i have taken. For the first time image load the potrait images shows in landscame mode. after refreshing the layout several time the image showing in correct orientation. This is not happening every time. I have set .considerExifParams(true) on the option. Seems like newly loading images from web service are showing in wrong orientation. But after loading it from cache sevaral time it's loading correct oriention. Please tell me what i have missing with implimentation.
Thanks,
Nishantha

Hi,need quick answer for this.i can send you image resolution if you want


From command line - use /noscale switch

Devenv.exe takes /noscale as a command-line parameter to run in 100% scaling mode.

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

ID: a2f87f79-412c-6d45-9a5f-e1690a7dce12
Version Independent ID: 708a3cc0-a8eb-3b23-9d11-737d0060d730
Content: Disable DPI-awareness in Visual Studio - Visual Studio
Content Source: docs/designers/disable-dpi-awareness.md
Product: visual-studio-windows
Technology: vs-ide-designers
GitHub Login: @gewarren
Microsoft Alias: gewarren

@OliaG Should I add this info to the docs page?

@Tanya-Solyanik @merriemcgaw have we tried/tested  /noscale command for CLI to run in 100% scaling mode?

We use that from the Gold Bar to restart VS in 100% scaling mode. I think it would be great to doc it for people that would rather launch devenv.exe from the command line.

@alansingfield We've added a Tip note to the Disable DPI-awareness in Visual Studio page that includes your suggested addition to content. Our thanks to you for helping us improve the documentation!

Thank you!


Need help with query watcher

I have this query
{
  "_index": "watcher",
  "_type": "watch",
  "_id": "new_watcher_illttg8d1",
  "_version": 4,
  "found": true,
  "_source": {
    "title": "watcher_title",
    "disable": false,
    "uuid": "new_watcher_illttg8d1",
    "trigger": {
      "schedule": {
        "later": "every 5 secs"
      }
    },
    "input": {
      "index": "heartbeat-*",
      "query": {
        "query_string": {
          "analyze_wildcard": true,
          "query": "*"
        }
      }
    },
    "condition": {
      "script": {
        "script": "payload.hits.up : false"
      }
    },
    "transform": {
      "script": {
        "script": ""
      }
    },
    "actions": {
      "report_admin": {
        "throttle_period": "0h0m5s",
        "report": {
          "to": "report@localhost",
          "from": "sentinl@localhost",
          "subject": "Sentinl Report",
          "body": "Sample Sentinl Screenshot Report",
          "snapshot": {
            "res": "1280x900",
            "url": "http://<IP_ADDRESS>/app/kibana#/dashboard/Alerts",
            "path": "/tmp/",
            "params": {
              "delay": 5000
            }
          }
        }
      }
    },
    "report": true
  }
}

Can anyone help me how to correct this to run watcher?
Thanks

It's unclear what the issue even is - maybe you could describe the expected vs. actual results as suggested by our template. At first sight, the issue is with your condition - its unclear what you're trying to do there?

Hi @lmangani
I try to set watcher about the up field of heartbeat index.
My expected results is whenever up field of heartbeat is false, tell me in the Alarms page.
Actual results i dont see anything in alarms page
Thanks

We'll need to see what the query responds to give you actual advice as I (at least) have no clue what the payload.hits returns. Run it in SENSE and paste the output here.

Hi @lmangani
Here is my query and result

Alright, so your actual data sits inside payload.hits.hits which is an array. In order to check if any of the returned values for up are false and trigger the screenshot, you need to iterate the elements and return true to the condition if any are found. You could try something as follows (untested):
var status=false; payload.hits.hits.forEach(function(e){ if (e.up == false){ status=true; return status; } }); status;

Hi @lmangani
Thank for your advise, i was curious how can i test my query if the watcher run or not?


fix(Dockerfile): pass same options to test binary

Closes #97.

Updated based on a suggestion by @vdice. I realized I will have to make a separate PR to close #97 however, since the command and options are part of the deis-tests chart.

I see.  I'd definitely be in favor of baking it into the Dockerfile/image if it helped multiple consumers (deis-tests chart being the prime example) and thereby sacrifice a small bit of DRYness here in this repo... whichever is the best way to align how the e2e tests are run.  All said, LGTM3


Avoid a region that was opened by two datanode at the same time.

What type of enhancement is this?
Tech debt reduction
What does the enhancement do?
The Failover Procedure will wait for the 40s if the Datanode is unreachable. If the unreachable Datanode restarts at the 23rd sec, the Datanode will open the old failed region (due to the table route not being updated after the failure occurred); a RegionAliveKeeper will wait for the 20s before the first lease arrives or closes the region (with flush). However, The procedure might step into the next stage, and the failed region will be opened in another Datanode.  It incurs a region opened by two Datanodes, and the newer Datanode will overwrite the existing manifest, which may let us lose the indexes of the flushed files.

Implementation challenges
Maybe we need to introduce Intermediate states.

Remove the failed region in the TableRoute
Deactivate the failed region
Update TableRoute
Activate the region

When a node is not granted permission (the first lease), we should prohibit it from accessing shared resources.
The problem now is that the restarted node accessed the shared resource (region) without permission. This is a  wrong way. The correct approach is to first obtain permission (obtain the first lease), then access the shared resource.


Nightly IT Failure (graalvm-nightly-17): Terraform cleanup error

Stacktrace:
module.java_iam_admin.google_project_service.iam[0]: Creating...
module.java_iam_admin.random_id.id: Creating...
module.java_iam_admin.random_id.id: Creation complete after 0s [id=x24y]
module.java_iam_admin.google_project_service.iam[0]: Creation complete after 3s [id=cloud-java-ci-test/[iam.googleapis.com](https://www.google.com/url?q=http://iam.googleapis.com&sa=D)]
module.java_iam_admin.google_service_account.service_account: Creating...
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ module.java_iam_admin.google_service_account.service_account, provider
│ "provider[\"[registry.terraform.io/hashicorp/google\](https://www.google.com/url?q=http://registry.terraform.io/hashicorp/google%5C&sa=D)"]" produced an
│ unexpected new value: Root resource was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵
cleanup

Fusion Link

Going to downgrade this to a p3 as it seems to have just been a one-off occurrence.

not seen recently. Closing for now.


Add tabs in login - separate for system and non-system logins

Separate source logins into two tabs - system and non-system logins. Since non-system logins cannot be migrated.
Created separate tabs for both.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 41.756%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/services/connection/browser/connectionDialogWidget.ts
1
73.44%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
30826

Relevant Lines:
69082

💛  - Coveralls

Text for system login tab : "Excluded login/s"
Info box for Excluded login/s text: "Below login/s is/are excluded from login migration as they are either local service or system accounts at the source."

Looks good to me, hope you have tested functionality as per the requirements. Approving it with couple comments.

Yes @Ramudaykumar, I have verified it.

Text for system login tab : "Excluded login/s" Info box for Excluded login/s text: "Below login/s is/are excluded from login migration as they are either local service or system accounts at the source."

@abhims14, I did the following changes. Can you verify same in the screenshots attached above?

@krritik are you planning to complete this PR?  Or should we close it as abandoned?

@kburtram, we are planning to complete it in few days. So for now lets keep it open.


"Thread was being aborted"

After following your guide, I am having an error when setting up the GitHub deployment. Some more info
Meteor Version: <IP_ADDRESS>
App-Service: Standard
Web-Socket: On
AAR Affinity: On

I have the script directory contents in my project root folder

I followed the instructions from the deployment link.
I added my web.config with the HTTPS rule and RequestLimits=20000 (for url length)
The deployment works fine, except when I visit the screen it is just a white page with no errors in console.

In the Kudu Logfiles it is saying "Cannot find module './programs/server/boot.js'"

Can you paste the full deployment log?

this is the log from the deployment settings
Command: bash .config/azure/deploy.sh
meteor-azure: Installing Meteor
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

  3  144M    3 5215k    0     0  3404k      0  0:00:43  0:00:01  0:00:42 3404k
  8  144M    8 11.9M    0     0  4852k      0  0:00:30  0:00:02  0:00:28 7072k
 11  144M   11 16.7M    0     0  4869k      0  0:00:30  0:00:03  0:00:27 5992k
 15  144M   15 22.0M    0     0  4991k      0  0:00:29  0:00:04  0:00:25 5802k
 18  144M   18 27.4M    0     0  5084k      0  0:00:29  0:00:05  0:00:24 5728k
 21  144M   21 30.6M    0     0  4803k      0  0:00:30  0:00:06  0:00:24 5232k
 24  144M   24 35.5M    0     0  4834k      0  0:00:30  0:00:07  0:00:23 4825k
 28  144M   28 40.8M    0     0  4907k      0  0:00:30  0:00:08  0:00:22 4934k
 28  144M   28 41.8M    0     0  4364k      0  0:00:33  0:00:09  0:00:24 3826k
 30  144M   30 44.8M    0     0  4358k      0  0:00:34  0:00:10  0:00:24 3555k
 33  144M   33 48.5M    0     0  4313k      0  0:00:34  0:00:11  0:00:23 3673k
 37  144M   37 54.2M    0     0  4430k      0  0:00:33  0:00:12  0:00:21 3820k
 41  144M   41 60.3M    0     0  4567k      0  0:00:32  0:00:13  0:00:19 3987k
 45  144M   45 66.5M    0     0  4690k      0  0:00:31  0:00:14  0:00:17 5367k
 50  144M   50 72.9M    0     0  4809k      0  0:00:30  0:00:15  0:00:15 5760k
 55  144M   55 80.2M    0     0  4971k      0  0:00:29  0:00:16  0:00:13 6489k
 60  144M   60 87.2M    0     0  5098k      0  0:00:29  0:00:17  0:00:12 6774k
 64  144M   64 93.7M    0     0  5179k      0  0:00:28  0:00:18  0:00:10 6835k
 68  144M   68 99.3M    0     0  5208k      0  0:00:28  0:00:19  0:00:09 6713k
 72  144M   72  105M    0     0  5239k      0  0:00:28  0:00:20  0:00:08 6572k
 77  144M   77  111M    0     0  5318k      0  0:00:27  0:00:21  0:00:06 6464k
 81  144M   81  118M    0     0  5384k      0  0:00:27  0:00:22  0:00:05 6387k
 85  144M   85  124M    0     0  5410k      0  0:00:27  0:00:23  0:00:04 6268k
 89  144M   89  129M    0     0  5410k      0  0:00:27  0:00:24  0:00:03 6198k
 93  144M   93  135M    0     0  5451k      0  0:00:27  0:00:25  0:00:02 6323k
 98  144M   98  141M    0     0  5478k      0  0:00:27  0:00:26  0:00:01 6166k
100  144M  100  144M    0     0  5491k      0  0:00:27  0:00:27 --:--:-- 6027k
meteor-azure: Building app
FEMA-SAH-WebApp@ D:\home\site\repository
`--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | |   `--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>
Thread was being aborted.
Thread was being aborted.

Looks like the build process was interrupted for some reason, try redeploying the app and paste the log when that is done (don't worry if this takes a while, it will be much faster after the first build).

How long is 'a while'? Been going for about 45 minutes now.

Sounds pretty normal for a first build (e.g ours took just over 43 minutes) - but it will vary greatly depending on your dependencies, especially atmosphere packages.
Note that future deployments should not reasonably take longer than ~5-10 minutes.

Alright, its still going at about 1.5 hours. I'll just let it run overnight and report back.

Command: bash .config/azure/deploy.sh
meteor-azure: Installing Meteor
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

  0  144M    0 32088    0     0  38706      0  1:05:22 --:--:--  1:05:22 38706
  4  144M    4 6799k    0     0  3717k      0  0:00:39  0:00:01  0:00:38 6768k
  7  144M    7 10.9M    0     0  3953k      0  0:00:37  0:00:02  0:00:35 5576k
 10  144M   10 15.0M    0     0  4036k      0  0:00:36  0:00:03  0:00:33 5141k
 14  144M   14 21.1M    0     0  4479k      0  0:00:33  0:00:04  0:00:29 5400k
 18  144M   18 26.7M    0     0  4707k      0  0:00:31  0:00:05  0:00:26 5481k
 22  144M   22 32.6M    0     0  4899k      0  0:00:30  0:00:06  0:00:24 5331k
 26  144M   26 38.6M    0     0  5053k      0  0:00:29  0:00:07  0:00:22 5676k
 31  144M   31 45.2M    0     0  5248k      0  0:00:28  0:00:08  0:00:20 6176k
 36  144M   36 52.4M    0     0  5464k      0  0:00:27  0:00:09  0:00:18 6416k
 41  144M   41 59.5M    0     0  5627k      0  0:00:26  0:00:10  0:00:16 6700k
 46  144M   46 66.7M    0     0  5776k      0  0:00:25  0:00:11  0:00:14 6976k
 50  144M   50 73.3M    0     0  5855k      0  0:00:25  0:00:12  0:00:13 7110k
 54  144M   54 79.1M    0     0  5863k      0  0:00:25  0:00:13  0:00:12 6950k
 58  144M   58 84.5M    0     0  5838k      0  0:00:25  0:00:14  0:00:11 6572k
 62  144M   62 91.2M    0     0  5900k      0  0:00:25  0:00:15  0:00:10 6489k
 67  144M   67 97.4M    0     0  5930k      0  0:00:24  0:00:16  0:00:08 6294k
 71  144M   71  102M    0     0  5914k      0  0:00:25  0:00:17  0:00:08 6067k
 74  144M   74  107M    0     0  5867k      0  0:00:25  0:00:18  0:00:07 5878k
 78  144M   78  112M    0     0  5827k      0  0:00:25  0:00:19  0:00:06 5797k
 81  144M   81  117M    0     0  5797k      0  0:00:25  0:00:20  0:00:05 5472k
 85  144M   85  123M    0     0  5802k      0  0:00:25  0:00:21  0:00:04 5372k
 90  144M   90  130M    0     0  5868k      0  0:00:25  0:00:22  0:00:03 5702k
 95  144M   95  137M    0     0  5924k      0  0:00:25  0:00:23  0:00:02 6137k
 99  144M   99  144M    0     0  5953k      0  0:00:24  0:00:24 --:--:-- 6451k
100  144M  100  144M    0     0  5960k      0  0:00:24  0:00:24 --:--:-- 6798k
meteor-azure: Building app
FEMA-SAH-WebApp@ D:\home\site\repository
`--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | |   `--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>
Command 'starter.cmd bash .config/az ...' was aborted due to no output nor CPU activity for 900 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this is a WebJob) if needed.\r\nstarter.cmd bash .config/azure/deploy.sh
One or more errors occurred.
Command 'starter.cmd bash .config/az ...' was aborted due to no output nor CPU activity for 900 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this is a WebJob) if needed.\r\nstarter.cmd bash .config/azure/deploy.sh

This is what I got after letting it run for about 4 hours

Increase the value of SCM_COMMAND_IDLE_TIMEOUT to 3600 (1 hour) and rebuild.
What was the reported duration in the portal?

@CCGLTD Did you get a chance to try this ^


Themes documentation?

Hi,
since you removed support for a well working and documented CSS framework and replaced it with something entirely custom, we're wondering you may have some more documentation?
When looking in the new themes now,  its all looking awful named and it's obviously becoming hard to actually build something solid (documentation, extendable,....) on your CSS framework.
it was sooo easy and good with bootstrap for us developers, and users building rich documentation, not any longer....
thanks,
g

Hello,
I think we've already discussed this.
the CSS in place now are based on BEM naming and this conversion was made because it's not needed for a documentation system to embed the full Bootstrap framework for only 5% of its features.
I will provide a documentation on how the theme is built and how to extend on it.

I think I can live with the details of your commit, removing bootstrap support. At the end I need just to create custom theme which mirrors all bootstrap class declarations into your new CSS names. well, at least that's what i hope. I saw some things hard-coded somewhere in non customizable PHP code but I guess i get that covered as well.
Problem with custom CSS frameworks is the absence of references, playgrounds and documentation. With Bootstrap it was easy because the internet is full of it. Very helpful for authors who write advanced docs,...
However, I gonna try loading bootstrap in top of a custom theme and hope to get away with that ;-)
thanks again for the heads up.
g


Enable modules for L2TP

I want to use a Scaleways machine as an l2tp/ipsec VPN server for my android devices.
This requires L2TP support to be built into the kernel (or as a module) PPPoL2TP  (l2tp_ppp / pppol2tp)  module.

Hi @Spindel, the L2TP module is available as a module in all our kernels: https://github.com/scaleway/kernel-tools/search?utf8=✓&q=l2tp
You can checkout live by using "zcat /proc/config.gz | grep -i l2tp"

So, currently this does not work:

xl2tpd[22788]: Not looking for kernel SAref support.
xl2tpd[22788]: L2TP kernel support not detected (try modprobing l2tp_ppp and pppol2tp)

[root@waterspout ~]# systemctl status xl2tpd.service
● xl2tpd.service - Level 2 Tunnel Protocol Daemon (L2TP)
Loaded: loaded (/usr/lib/systemd/system/xl2tpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2015-09-05 19:31:05 EDT; 1s ago
Process: 2668 ExecStartPre=/sbin/modprobe -q l2tp_ppp (code=exited, status=1/FAILURE)
zcat /proc/config.gz |grep L2TP
CONFIG_NETFILTER_XT_MATCH_L2TP=m
CONFIG_L2TP=m
CONFIG_L2TP_DEBUGFS is not set
CONFIG_L2TP_V3 is not set
CONFIG_PPPOL2TP is not set
[root@waterspout ~]# uname -a
Linux waterspout 4.1.6-247 #1 SMP Wed Aug 26 18:05:41 UTC 2015 armv7l armv7l armv7l GNU/Linux

Hi @Spindel L2TP is already available as a module you can load manually, however, one particularity about running Linux on Scaleway is that we don't use the kernel on your rootfs, so we needed to add a script that synchronize current kernel modules to /lib/modules on boot.
I suppose that our init script that syncs the module is maybe loaded after the xl2tpd service.
Can you try to do a reboot then relaunch the script ?
However, we will release a new kernel with more L2TP modules and options: L2TP_IP, L2TP_ETH, L2TP_V3 and PPPOL2TP

It's the PPPOL2TP that is missing in order to run a functional  xl2tpd
server. ( and thus ipsec)
I'll wait for the updated kernel and then set about documenting the setup
for others to use.
Thanks!
On Sun, 6 Sep 2015 11:45 Manfred Touron<EMAIL_ADDRESS>wrote:

Hi @Spindel https://github.com/Spindel L2TP is already available as a
module you can load manually, however, one particularity about running
Linux on Scaleway is that we don't use the kernel on your rootfs, so we
needed to add a script that synchronize current kernel modules to
/lib/modules on boot.
I suppose that our init script that syncs the module is maybe loaded
after the xl2tpd service.
Can you try to do a reboot then relaunch the script ?
However, we will release a new kernel with more L2TP modules and options:
L2TP_IP, L2TP_ETH, L2TP_V3 and PPPOL2TP
—
Reply to this email directly or view it on GitHub
https://github.com/scaleway/kernel-tools/issues/138#issuecomment-138061228
.

@Spindel yes, I'm just waiting for colleagues to approve my PR https://github.com/scaleway/kernel-tools/pull/143


DE3529: When dumping JSON to a file, proactively sync file contents.

Goes along with an xl PR.
We're trying to remove our global sync call, in favor of a more localized fsync or fdatasync call after each of our file writes.
The latter call has to be made when we still have access to a file descriptor, which means we're here in Jansson as opposed to a level above.

How much more expensive would it be to re-open the file to sync it after jansson closes it?

How much more expensive would it be to re-open the file to sync it after jansson closes it?

I could probably do it for twenty bucks.
(I'll give it a shot and rerun the tests, I don't imagine it'd be too prohibitive.)

However... If these queued I/O operations are associated with the file descriptor (and I believe they are), then opening a new file descriptor and flushing its (zero) queued I/O operations might not get us the desired result. I believe we may have to sync the file descriptor that we wrote on.

Ah, yeah. Good point. Just skip it, then.

Hm, it looks like fdatasync syncs all changes to a file, not just ones for a particular file descriptor. In any case, this is probably fine.


Fix typos in spec.serviceTemplates

Deleted duplicate lines and corrected spec.serviceTemplates typos

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Detailed day 1 schedule

08:50 - 09:00 (10 min) Soft start and icebreaker question
09:00 - 09:20 (20 min) Welcome and practical information
Introduction to version control (part 1/2)

09:20 - 09:35 (15 min) Motivation - teaching & demo
09:35 - 09:50 (15 min) Basics - teaching & type-along
09:50 - 10:10 (20 min) Basics - exercises
1. Record changes
2. Optional: Comparing, renaming, and removing - if time allows
10:10 - 10:25 (15 min) :coffee: :walking: :tea: Break
10:25 - 10:45 (20 min) Basics - History, commit log, ignoring - teaching
10:45 - 11:05 (20 min) Branching and merging - teaching/type-along
11:05 - 11:15 (10 min) :coffee: :walking: :tea: Break
11:15 - 11:30 (15 min) Branching and merging - exercises
1. Create and commit to branches Teaching resumed before merging branches.
2. Optional exercies with branches: Fast-forward merge and Rebasing - if time allows
11:30 - 11:45 (15 min) Summarize branching and merging (type along)
11:45 - 12:00 (15 min) Discuss and demo conflict resolution (no exercise room)

12:00 - 12:10 (10 min) :coffee: :walking: :tea: Break
12:10 - 12:25 (15 min) Buffer, Q&A session
12:25 - 12:30 (5 min) Feedback & What will we be doing tomorrow?

One problem that I see: On day 1 we have 3.5 h program but only 2 exercises (20 min and 15 min). Better would be to have 3 exercises.


transactionDate typing conflict with doc

Version of react-native-iap
2.4.4
Version of react-native
0.59.2 (it does not matter)
Platforms you faced the error (IOS or Android or both?)
Both platform
Expected behavior
In the README the documentation says :
transactionDate : The time the product was purchased, in milliseconds since the epoch (Jan 1, 1970).
-- | -- | -- | --

Actual behavior
But in index.d.ts and index.js.flow, transactionDate is typed as string when it should be number.
Tested environment (Emulator? Real Device?)
Steps to reproduce the behavior
Run flow, wrong errors are returned when using transactionDate

Yes you are right. Do you mind give us a fix PR for this?

I believe there is a bug compounded on top of this.  On Android the transactionDate value comes back as a string, on iOS is comes back as a number.  We should change the native code to align with one another as well as the type defs

References
Android:
https://github.com/dooboolab/react-native-iap/blob/master/android/src/main/java/com/dooboolab/RNIap/RNIapModule.java#L295
https://github.com/dooboolab/react-native-iap/blob/master/android/src/main/java/com/dooboolab/RNIap/RNIapModule.java#L341
https://github.com/dooboolab/react-native-iap/blob/master/android/src/main/java/com/dooboolab/RNIap/RNIapModule.java#L441
iOS:
https://github.com/dooboolab/react-native-iap/blob/master/ios/RNIapIos.m#L483
I'm down to put in a fix if folks agree that the android code should also return a number

@phil-flyclops agree

I looked into this and it turns out that underlying react bridge code we're using only has a way to return strings and ints, but no longs
https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/bridge/WritableMap.java
Does somebody who is familiar with the underlying React Native Java code have any guidance on how to handle a case like this?

Hmm one potential solution can include parsing the responses on the JS side of things (like here or here)
Not the ideal solution, but can work as to circumvent this limitation @phil-flyclops


Vote Results

When the votes are revealed, the leader and other users should have an easy way of figuring out what the best/winning vote is.
Nominal Decks
A nominal deck is one in which the card values do not have any intrinsic order. That is to say, a vote for card one and a vote for card three does not imply that card two is a better fit.

Mode will be the measure of central tendency
Scenario:  A single value has the most votes (no ties)
1. 100% - "Unanimous: [Card Value]"
1. >= 75% - "Consensus: [Card Value]"
1. >= 50% - "Majority: [Card Value]"
1. < 50% - "Plurality: [Card Value]"
Scenario: Ties
1. Display "Tie: [Card 1 Value] [Card 2 Value]...[Card N Value]"

Ordinal Decks
An ordinal deck is one where the card values can be ordered or ranked. That is to say, a vote for card one and a vote for card three implies that card two is a better fit.

Median will be the measure of central tendency
Only numeric card values will be considered.
Median will be the higher of the two card values in the case of an even number of votes.
Display: "Best Guess (Median): [Card Value]"
Future enhancement will evaluate the range of vote disparity in relation to the best guess.

Changes for this story available as of revision 4b5eb63.


Rework MaeMolSupplier, fix #2617

This started as a fix for #2617, but I added some more changes. That issue is caused by #2579, but after finding the problem, the MaeMolSupplier does not stop iteration despite it does not get any more structures, and continues returning "None" forever.
Also, this depends on schrodinger/maeparser#46 and schrodinger/maeparser#49, and should not be merged until these changes are accessible to RDKit.
Changes in the PR:

Check the state of the stream after the creation of the Supplier: on construction, the Reader populates the internal buffer, so that, if there aren't any problems, the stream may be left either in a good state, if there was more data available than fits in the internal buffer, or with the failed and eof bits activated if there was less data than the buffer tried to read (both states are ok).

Do not read the next block / structure before it is requested. Before this change, the MaeMolSupplier attempted to read the first structure still inside the constructor, right after constructing the Reader object; the second one when the first was requested, etc. With this mechanism, if a problem was encountered while reading the second structure, the first one would not have been returned.

Catching of exceptions thrown during and after reading of the mae::Block, and rethrowing them as FileParseException so that they can be handled by RDKit (e.g., by preventing further reads, like should happen in #2617).

Changed the way how atEnd() is handled. This depends on schrodinger/maeparser#49.

Provide translation of FileParseExceptions into Python RuntimeErrors. This is the part that would actually prevent an infinite reading loop as in #2617, and also the one I am most interested in, especially because of the comment at:
https://github.com/rdkit/rdkit/blob/01fbec33ff434432d840828b7fb02cc22680fd42/Code/GraphMol/Wrap/MolSupplier.h#L90-L94
I tried to iterate over a MaeMolSupplier, a SDMolSupplier and a ForwardSDMolSupplier after introducing this patch, and did not observe any problems like unexpected RuntimeErrors, e.g. at the end of the iteration).

Updated to parse chirality, pseudochirality and stereo bond properties instead of just copying them to the mol, and updated to current master again.
This adds a new dependence on another maeparser PR, schrodinger/maeparser/pull/50, which adds constants for the prefixes used in stereo properties, and some comment on how these properties are build.

I removed the dependence on the eof() method in maeparser, as we had certain reservations on it.

Merged in current master (after maeparser and coordgen update). This should build fine now, as  schrodinger/maeparser/pull/50 has also been merged

@ricrogz : those build failures on windows look real. Can you look into them?

@ricrogz : those build failures on windows look real. Can you look into them?

Yeah, sorry, I noticed, but something came up before I could look into it, but will do soon.

Ok, now it should finally build and pass tests on all platforms :)

I realized this had become too messy, and have reset the original branch.


🐛 Fixed editor image uploads

closes https://github.com/TryGhost/Ghost/issues/9300

as of https://github.com/TryGhost/Ghost-Admin/commit/74428efd8bf5a3d896dd1c5c549553893bc5aa05 we reset the file input earlier in the actions chain, this was clearing the file references before the editor was triggering the upload. By converting the FileList to an Array before resetting the input we keep hold of the file references and the upload works again.

Changes Unknown when pulling 89e2270b992d441f9f7db80f259eda2d4325be53 on kevinansfield:fix-editor-image-upload into ** on TryGhost:master**.


More compact entity format - DeriveModel, DeriveModelColumn, DeriveModelPrimaryKey, DeriveEntity, DeriveRelation

This PR aims to resolve https://github.com/SeaQL/sea-orm/issues/105.

It adds features to the existing:

DeriveModel
DeriveEntity

And adds new derives:

DeriveModelColumn
DeriveModelPrimaryKey
DeriveRelation

DeriveModel changes
Derive attributes:
#[sea(
    entity = Entity, // Specifies the entity struct for implementing ModelTrait. Default: Entity
)]

Field attributes: none
Summary:
DeriveModel still works the same, but includes an additional attribute entity which allows you to specify the Entity struct incase you've named it something other than Entity.
Example:
#[derive(DeriveModel)]
#[sea(entity = UserEntity)]
pub struct Model {
    pub id: Uuid,
    pub name: String,
}

// Generates
impl sea_orm::FromQueryResult for Model { ... }
impl sea_orm::ModelTrait for Model { ... }

DeriveEntity changes
Derive attributes:
#[sea(
    column = Column, // Specifies the column struct. Default: Column
    model = Model, // Specifies the model struct. Default: Model
    primary_key = PrimaryKey, // Specifies the primary key struct. Default: PrimaryKey
    relation = Relation, // Specifies the relation struct. Default: Relation
    schema_name = "public", // Define the entity's shema name. Optional
    table_name = "users", // Define the table name. If omitted, EntityName will not be implemented and should be done manually
)]

Field attributes: none
Summary:
DeriveEntity still works the same, but also implements EntityName if the table_name is set.
Example:
#[derive(DeriveEntity)]
#[sea(schema_name = "public", table_name = "users")]
pub struct Entity;

// Generates
impl sea_orm::entity::EntityName for Entity {
    fn schema_name(&self) -> Option<&str> { Some("public") }
    fn table_name(&self) -> &str { "users" }
}
impl sea_orm::entity::EntityTrait for Entity { ... }
impl sea_orm::Iden for Entity { ... }
impl sea_orm::IdenStatic for Entity { ... }

DeriveModelColumn added
Derive attributes:
#[sea(
    column = Column, // Specifies the column struct. Default: Column
    entity = Entity, // Specifies the entity struct. Default: Entity
)]

Field attributes:
#[sea(
    column_type = "String(Some(255))", // Specifies the field's ColumnType. Default: detected by the field's type
    column_type_raw = "ColumnDef::String(Some(255)).def()", // Specifies the field's ColumnType with raw code. Optional
    indexed, // Adds .indexed() to the column def. Optional
    null, // Adds .null() to the column def. Optional
    unique, // Adds .unique() to the column def. Optional
)]

Summary:
Generate's the column enum based on the field names.
The column enum implements ColumnTrait, FromStr, Iden & IdenStatic. A method .as_str() is also added to it.
ColumnTrait is implemented on the column enum, and attempts to detect the type from field's Rust type. If the column_type attribute is added, it will use this type instead.
Example:
#[derive(DeriveModelColumn)]
#[sea(entity = UserEntity)]
pub struct Model {
    pub id: Uuid,
    pub name: String,
    #[sea(column_type = "String(Some(255))", null, unique)]
    pub email: Email,
    #[sea(column_type_raw = "ColumnDef::String(None).def()")]
    pub password: String,
}

// Generates
#[derive(Copy, Clone, Debug, EnumIter)]
pub enum Column {
    Id,
    Name,
    Email,
    Password,
}
impl Column { fn as_str(&self) -> &str { ... } }
impl sea_orm::entity::ColumnTrait for Column { ... }
impl std::str::FromStr for Column { ... }
impl sea_orm::Iden for Column { ... }
impl sea_orm::IdenStatic for Column { ... }

Mapping for rust types into ColumnDef types can be found here: https://github.com/SeaQL/sea-orm/pull/122/files#r702886781

DeriveModelPrimaryKey added
Derive attributes:
#[sea(
    column = Column, // Specifies the column struct. Default: Column
    primary_key = PrimaryKey, // Specifies the primary key struct. Default: PrimaryKey
)]

Field attributes:
#[sea(
    auto_increment = true, // Indicated the primary key is auto incrementing. Default: true
    primary_key, // Marks the field as a primary key.
)]

Summary:
Generates the PrimaryKey enum based on the fields marked with primary_key. Implements Iden, IdenStatic, PrimaryKeyToColumn & PrimaryKeyTrait on the enum. Additionally adds a .as_str() method.
PrimaryKeyTrait is implemented and uses the first field marked as primary_key for the ValueType.
If there are multiple primary keys, auto_increment will be false, otherwise true by default with the ability to change this with the auto_increment attribute.
Example:
#[derive(DeriveModelPrimaryKey)]
pub struct Model {
    #[sea(primary_key)]
    pub id: Uuid,
    pub name: String,
}

// Generates
#[derive(Copy, Clone, Debug, EnumIter)]
pub enum PrimaryKey {
    Id,
}
impl sea_orm::entity::PrimaryKeyTrait for PrimaryKey {
    type ValueType = Uuid;
    fn auto_increment() -> bool { true }
}
impl PrimaryKey { fn as_str(&self) -> &str { ... } }
impl sea_orm::Iden for PrimaryKey { ... }
impl sea_orm::IdenStatic for PrimaryKey { ... }
impl sea_orm::PrimaryKeyToColumn for PrimaryKey { ... }

DeriveRelation added
Derive attributes:
#[sea(
    entity = Entity, // Specifies the entity struct. Default: Entity
)]

Field attributes:
#[sea(
    belongs_to = "cake::Entity", // Specifies the entity the field belonds to. Required
    from = "Column::CakeId", // Specifies the from column. Required
    to = "cake::Column::Id", // Specifies the to column. Required
)]

Summary:
Implements RelationTrait on the enum.
Each variant is required to have the field attributes listed above, and generates the RelationTrait based on the variants.
Example:
#[derive(DeriveRelation)]
#[sea(entity = Entity)]
pub enum Relation {
    #[sea(belongs_to = "cake::Entity", from = "Column::CakeId", to = "cake::Column::Id")]
    Cake,
}

// Generates
impl RelationTrait for Relation {
    fn def(&self) -> RelationDef {
        match self {
            Self::Cake => Entity::belongs_to(cake::Entity)
                .from(Column::CakeId)
                .to(cake::Column::Id)
                .into(),
        }
    }
}

Example of all derives
#[derive(Copy, Clone, Default, Debug, DeriveEntity)]
#[sea(schema_name = "public", table_name = "users")]
pub struct Entity;

#[derive(
    Clone,
    Debug,
    DeriveActiveModel,
    DeriveActiveModelBehavior,
    DeriveModel,
    DeriveModelColumn,
    DeriveModelPrimaryKey,
)]
pub struct Model {
    #[sea(primary_key)]
    pub id: Uuid,
    pub name: String,
    pub age: u64,
    pub parent: Uuid,
}

#[derive(Copy, Clone, Debug, EnumIter, DeriveRelation)]
pub enum Relation {
  #[sea_orm(belongs_to = "cake::Entity", from = "Column::CakeId", to = "cake::Column::Id")]
  Parent,
}

Yes it makes sense. It's cleaner and more intuitive to separate the SimpleInput

I've added the SimpleInput feature.
It's usage is dependant on a struct derived with SimpleModel being in the same module, and it checks the types are compatible with the Into trait only at compile time, and ensures there are no unknown fields in the SimpleInput which are not in the SimpleModel.
The following example will not compile:
#[derive(SimpleModel)]
#[table(name = "users")]
pub(crate) struct User {
    #[primary_key]
    pub id: Uuid,
    pub name: String,
}

#[derive(SimpleInput)]
#[input(model = User)]
pub(crate) struct NewSeo<'a> {
    pub name: u64, // Error: the trait bound `String: From<u64>` is not satisfied
}

The checking between types does not cause a compile error if one type is in an Option and the other is not.

I initially started implementing ActiveModelTrait for the SimpleInput, but realised that inserting only uses the ActiveModelTrait::take method, and does not use any others.. and instead of putting a panic! or unimplemented! method for the other methods, I decided to create a new trait called Insertable.

@tyt2y3 @billy1624 I think the PR is done if you want to review it.

Thank you so much for the big contribution. I am going through it.

Thank you so much for the contribution.
I really liked your coding style, especially for using a struct to hold all the parameters.
DeriveModel, DeriveEntity, DeriveRelation these are immensely useful.
As for DeriveModelColumn & DerivePrimaryKey, I prefer #128 's implementation strategy, where instead of impl the traits in-place, we expand it to the existing 'long format', and let the old macros continue expanding it.
This 'layered approach' frees us from having to maintain two sets of impl.
I will merge this to a separate branch, cherry-pick the bits, make some tweaks and integrate things together.
Hopefully after this we will have something desired by everybody.


Dbus sml api

Provide live view to running state machines generically.
Example, using https://github.com/seesleestak/plantuml-previewer-react:

Output from the plantuml is:
@startuml

[*] --> init
init --> stopped #limegreen : set_stopped / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:120:66)
stopped : entry / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:121:54)
stopped : exit / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:122:53)
stopped --> starting : set_starting / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:123:70)
stopped --> starting : run_button / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:124:68)
starting : entry / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:125:55)
starting : exit / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:126:54)
starting --> running : starting_timeout / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:127:75)
starting --> running : starting_finished / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:128:76)
running : entry / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:129:54)
running : exit / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:130:53)
running --> stopping : run_button / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:131:68)
running --> stopping : set_stopped / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:132:69)
stopping : entry / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:133:55)
stopping : exit / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:134:54)
stopping --> stopped #limegreen : stopping_timeout / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:135:75)
stopping --> stopped #limegreen : stopping_finished / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:136:76)
stopped --> cleaning : cleaning_button / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:137:73)
stopped --> cleaning : set_cleaning / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:138:70)
cleaning : entry / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:139:55)
cleaning : exit / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:140:54)
cleaning --> stopped #limegreen : cleaning_button / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:141:74)
cleaning --> stopped #limegreen : set_stopped / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:142:70)
stopped --> emergency : set_emergency / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:144:71)
stopping --> emergency : set_emergency / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:145:72)
starting --> emergency : set_emergency / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:146:72)
running --> emergency : set_emergency / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:147:71)
cleaning --> emergency : set_emergency / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:148:72)
fault --> emergency : set_emergency / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:149:69)
maintenance --> emergency : set_emergency / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:150:75)
stopped --> emergency : emergency_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:152:70)
stopping --> emergency : emergency_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:153:71)
starting --> emergency : emergency_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:154:71)
running --> emergency : emergency_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:155:70)
cleaning --> emergency : emergency_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:156:71)
fault --> emergency : emergency_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:157:68)
maintenance --> emergency : emergency_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:158:74)
emergency : entry / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:160:56)
emergency : exit / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:161:55)
emergency --> stopped #limegreen : emergency_off / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:162:73)
stopped --> fault : fault_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:163:66)
stopped --> fault : set_fault / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:164:67)
running --> fault : fault_on / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:165:66)
running --> fault : set_fault / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:166:67)
fault : entry / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:167:52)
fault : exit / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:168:51)
fault --> stopped #limegreen : fault_off / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:169:65)
fault --> stopped #limegreen : set_stopped / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:170:67)
stopped --> maintenance : maintenance_button / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:171:76)
stopped --> maintenance : set_maintenance / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:172:73)
maintenance : entry / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:173:58)
maintenance : exit / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:174:57)
maintenance --> stopped #limegreen : maintenance_button / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:175:80)
maintenance --> stopped #limegreen : set_stopped / (lambda at /home/jonb/Projects/framework/exes/operations/inc/details/state_machine.hpp:176:73)

@enduml

This is a neat idea :+1:

not ready, forgot to use constexpr name if it exists

Is this something you want on the frontend? If so where would we put it?

Or we could use https://arthursonzogni.github.io/FTXUI/ and display the statemachine with tfcctl

I think that it would be nice to be able to do both honestly. But I am a little nervous about the amount of data we are transmitting over dbus when 99% of the time nobody is viewing. We will need to see how much this effects a running system. if at all.

I think that it would be nice to be able to do both honestly. But I am a little nervous about the amount of data we are transmitting over dbus when 99% of the time nobody is viewing. We will need to see how much this effects a running system. if at all.

We could do something like a heartbeat, where I toggle a parameter on DBus from the frontend every ~30 seconds and if you haven't heard from me in 60, then you can stop transmitting.
This would fail if the window is left open though.

Is this something you want on the frontend? If so where would we put it?

I was thinking that it could be a separate tab, SM debugging
If we could pick running state machines and display their live statemachine in a dialog similarly to the watch IO debugging.
@omarhogni, @SindriTh thoughts on this suggestion?

I like this idea, Could we also show which parameters are needed to proceed to the next state? i.e a red or green circle showing if each requirement needed to proceed is fulfilled?
This could enable us to see why a particular state machine isn't changing state.

We could do something like a heartbeat, where I toggle a parameter on DBus from the frontend every ~30 seconds and if you haven't heard from me in 60, then you can stop transmitting. This would fail if the window is left open though.

I dont think that is a good idea. Could have side affects activating the heartbeat. For now I think we keep this as a consideration and see if it causes any issues when the system gets some real runtime.


Merge RNA polymerase II transcription cofactor activity transcription cofactor activity in parent

GO:0001104 RNA polymerase II transcription cofactor activity: only used in metazoa
merge into: GO:0003712 transcription cofactor activity

GO:0001105 RNA polymerase II transcription coactivator activity: only used in eukaroytes
merge into:  GO:0003713 transcription coactivator activity

GO:0001106 RNA polymerase II transcription corepressor activity: only used in metazoa
merge into:  GO:0003714 transcription corepressor activity

So this has no impact on annotations.
@krchristie @ValWood @RLovering is this OK ?
Thanks, Pascale

Im happy with this
Ruth

So, if you eliminate all of the RNAP II specific terms, how are people going to be able to identify the ones that affect RNAP II, versus some other RNAP? Especially considering that most people only want to know about RNAP II...

Hi @krchristie
There are no other children terms (non-polII). Do you know of examples ?
Pascale

The issue isn't eukaryotic RNA pols I or III. However, cofactors might apply to plant pols IV and V since these are more close related to RNA pol II.
Also, the generic terms are all flagged as being in the prokaryotic subset and I have vague recollections that the bacterial transcription community may indeed refer to transcription coactivators and corepressors. Probably good to get input from @dsiegele and @jimhu-tamu before changing these terms.

So, if you eliminate all of the RNAP II specific terms, how are people going to be able to identify the ones that affect RNAP II, versus some other RNAP? Especially considering that most people only want to know about RNAP II...

Maybe this will become a documentation issue:
Retrieve all genes involved in   "transcription by RNA polymerase II (GO:0006366)"
and then break down by function (GSTF, cofactor, general).
This is kind of what @vanaukenk  was saying on the call (I think?)  were you?
But it could be a moot issue for species where "all" annotations to  "GO:0003712 transcription cofactor activity" are already pol II.

Should I start a new issue?
I am OK with the recommended mergers, but I have a question about the definitions of:
GO:0003712 transcription cofactor activity
GO:0003713 transcription coactivator activity
GO:0003714 transcription corepressor activity
The definitions of all 3 terms include the statement "Cofactors generally do not bind the template nucleic acid, but rather mediate protein-protein interactions."  In prokaryotes, most transcription transcriptional activators and repressors do bind to the genomic nucleic acid and altering the DNA binding sites for the proteins prevents them acting.
Also, at least in E. coli, the terms corepressor and coactivator often refer to the small molecules that modulate the activity of a protein factor.  For example, tryptophan is the corepressor for the TrpR protein: the complex binds to the genomic DNA and represses transcription of the trp operon.
Could something be added to the comments to point out this difference.
I apologize for the late response, but it is near the end of the semester and all my neurons are occupied with grading exams.

Hi @dsiegele
Thanks for your response. In the new organisation this would be considered a 'repressor', not a co-repressor. I understand that the bacterial nomenclature might be different; but in principle does this make sense to you ?
GO:0001217 bacterial-type RNA polymerase transcriptional repressor activity, sequence-specific DNA binding
Yesterday I also added a taxon constraint (never in bacteria) for transcription cofactor activity (there was a single annotation to P69348/yoeB, which I have discussed with the SP curator who made it; she was waiting for more guidance to move it).
Does that sound OK to you ? Will you be at the GOC meeting ?
Thanks, Pascale


Added New Challenges

Added new Trivia Challenges 🚩 Resolves #53

Added new Trivia Challenges 🚩 Resolves #53

quick update

I can provide you with all the trivia questions from the game "Psych" if you wanna import them too :)


Added my GitHub account name link

Sorry, the first one I had auto formatter on, I fixed that, thats why there is two commits


The pipe 'translate' could not be found

I'm submitting a ...  (check one with "x")
[ x] bug report => check the FAQ and search github for a similar issue or PR before submitting
[ ] support request => check the FAQ and search github for a similar issue before submitting
[ ] feature request

Current behavior
Translate does not work on the child components
Expected/desired behavior
Translate does not work on the child components
Reproduction of the problem
I am using translation pipe on the home page it works fine, but when i add it on the child component , it says The pipe 'translate' could not be found
I looked at this issue,
https://github.com/ngx-translate/core/issues/163
but when i import
{provide: PLATFORM_PIPES, useValue: TranslatePipe, multi: true}`
it is not supported with the angular version. How can i solve this issue?
Please tell us about your environment:

**ngx-translate version:**5.0.0

Angular version: 2.4.0

Browser: [all | Chrome XX

How did you import the TranslateModule into your module?
Is the child component in the same module?

This is how i have imported
import './rxjs-extensions';
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { FormsModule } from '@angular/forms';
import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';
import { UsersModule } from './users/users.module';
import { MainModule } from './main/main.module';
import { DiscoveryModule } from './discovery/discovery.module';
import { AppConfigService } from './services/appconfig.service';
import { TranslateModule, TranslateStaticLoader, TranslateLoader } from 'ng2-translate';
import { HttpModule, Http } from '@angular/http';
export function createTranslateLoader(http: Http) {
    return new TranslateStaticLoader(http, './assets/i18n', '.json');
}

@NgModule({
    imports: [
        BrowserModule,
        FormsModule,
        HttpModule,
        AppRoutingModule,
        DiscoveryModule,
        TranslateModule.forRoot({
            provide: TranslateLoader,
            useFactory: (createTranslateLoader),
            deps: [Http]
        })
    ],

    declarations: [
      AppComponent
    ],
    providers: [
      AuthGuard,
      AuthService,
      AppConfigService
    ] ,
    bootstrap: [AppComponent]
})
export class AppModule {}

No child component is in the discovery module

Attaching pipes to the platform pipes like you are trying to do does not work anymore in Angular.
Because it is in a separate module, you will probably have to work with a SharedModule. If you don't want to work with a SharedModule (which is best practice though), just make sure you import TranslateModule in the DiscoveryModule.

only importing would work or do i have to repeat what i did in the app.module.ts?

From the docs

Note: Never call a forRoot static method in the SharedModule. You might end up with different instances of the service in your injector tree. But you can use forChild if necessary.

Thus, only import TranslateModule.
You can find more about the SharedModule approach on the Angular documentation.

forChild is not available in the 5.x version that he's using.
Just importing the module (without calling forRoot on it) should work for the pipe/directive.

@ocombe  @SamVerschueren  how do i change the app module ?
TranslateModule.forRoot({
provide: TranslateLoader,
useFactory: (createTranslateLoader),
deps: [Http]
})

Just keep app module with what you have. It configures ngx-translate and sets up all the services which is fine. And then in your sub-module, just import TranslateModule and it should work.

Ok that worked, i will close this issue with the last question, is there a way we can use translation without adding the pipe |trasnalate in each line?

Yes, by using the translate pipe.

using translate pipe? my question is same , is there a way without using pipe in each line?

Not working!. I am using this plugin, and when I add 'Something' | translate in template of plugin not working

I have one module on my app, and the issue still exist

You should add in child module:
TranslateModule.forChild({...})

For those coming across the pipe translate could not be found, here are the steps you need to do in a nutshell to fix the issue when using in a different module.

Have the translate module logic along with translate loader and translateFactory present in the app.module.ts
TranslateModule.forRoot({ provide: TranslateLoader, useFactory: (http: Http) => new TranslateStaticLoader(http, './assets/i18n', '.json'), deps: [Http] }) ],

In your shared.module.ts (or any other module), import and export the Translate module.
i.e.: Translate module should be a part of both the import and export arrays. Most answers in SO and github mention importing the module but not exporting it.

@NgModule({ imports: [ TranslateModule ], exports: [ TranslateModule]


SCIO 32.1.0 reports conjunctive rather than disjunctive license expression for slint v1.0.0

A recent scan using SCIO v32.1.0 of the code available at https://github.com/slint-ui/slint/archive/refs/tags/v1.0.0.tar.gz reported a declared license expression of gpl-3.0 AND proprietary-license even though the notices state that there is actually a choice of licenses.
from README.md:
## License

Slint is available under either a [proprietary license](LICENSES/LicenseRef-Slint-commercial.md)
or [GNU GPLv3](LICENSES/GPL-3.0-only.txt)

The proprietary license is provided free-of-charge in exchange for (1) consent that we can showcase the application, (2) attribution of Slint in the application and (3) feedback to improve Slint.
Check out our [ambassador program](https://slint-ui.com/ambassador-program.html).

from LICENSE.md
# Slint License

Slint is available under either a [proprietary license](LICENSES/LicenseRef-Slint-commercial.md)
or [GNU GPLv3](LICENSES/GPL-3.0-only.txt).

Third party licenses listed in the `LICENSES` folder also apply to parts of the product.

The either/or construction clearly indicates a disjunctive choice of licenses rather than a conjunctive combination of licenses.  The correct license expression would be:
gpl-3.0 OR proprietary-license

@DennisClark @pombredanne That would be an issue on the ScanCode-toolkit side. SCIO is just storing scan data as returned by the toolkit.

oops, my mistake.  Opened new issue https://github.com/nexB/scancode-toolkit/issues/3316  for this problem and closing this issue.


Better current status information

While debugging an issue in staging, it was hard to tell what the current status of a timeline in the pageserver was.
Let's add a new HTTP API call that returns the following information for every timeline in the pageserver:

loaded locally or remote-only?
state: Active, Idle, Stopping (from TenantState in tenant_mgr.rs)
wal_producer_connstr, from last callmemaybe
WAL receiver thread ID
Current WAL receiver's libpq connection's remote IP / port
timestamp of last message received by WAL receiver msg
LSN of last received piece of WAL
last_record_lsn and prev_record_lsn
disk_consistent_lsn
last GC lsn

Would be nice to get similar status information from each safekeeper, too.

As we already had the GET /v1/tenant/:tenant_id/timeline/:timeline_id API to get the timeline's info, I initially plan to  add more fields into the TimelineInfo struct:
pub struct TimelineInfo {
    #[serde_as(as = "DisplayFromStr")]
    pub tenant_id: ZTenantId,
    #[serde_as(as = "DisplayFromStr")]
    pub timeline_id: ZTimelineId,
    pub local: Option<LocalTimelineInfo>,
    pub remote: Option<RemoteTimelineInfo>,
+   pub tenant_state: ...,
+   pub wal_receiver_thread_id: ...,
+   pub wal_receiver_last_msg_ts: ...,
+   pub wal_receiver_last_msg_lsn: ...,
+   pub wal_producer_connstr: ...,
+   ...
}

This approach requires us to retrieve the additional information even for the POST /v1/tenant/:tenant_id/timeline/:timeline_id API because the TimelineInfo struct is also used to represent the POST API's response. I don't think this behaviour is desirable.
One way to fix this is to add another struct to represent the response of the GET /v1/tenant/:tenant_id/timeline/:timeline_id API.
Or we can try to make our pageserver APIs more "RESTful" 😅 , e.g, only returns minimal information representing the timeline. If users want to get more information about wal receiver, tenant, they can make additional APIs (GET /v1/tenant/:tenant_id/timeline/:timeline_id/wal_receiver, GET /v1/tenant/:tenant_id)
@hlinnaka WDYT?

This approach requires us to retrieve the additional information even for the POST /v1/tenant/:tenant_id/timeline/:timeline_id API because the TimelineInfo struct is also used to represent the POST API's response. I don't think this behaviour is desirable.

Agreed, that's not nice for POST.

One way to fix this is to add another struct to represent the response of the GET /v1/tenant/:tenant_id/timeline/:timeline_id API.

+1. Unless there's some common convention that POST and GET requests should return a response with same structure; I don't have much experience with RESTf APIs.

Or we can try to make our pageserver APIs more "RESTful" sweat_smile , e.g, only returns minimal information representing the timeline. If users want to get more information about wal receiver, tenant, they can make additional API calls (GET /v1/tenant/:tenant_id/timeline/:timeline_id/wal_receiver, GET /v1/tenant/:tenant_id)

That sounds more complicated for the caller collecting the info.


Added Donors Prediction Project

Nice Project @runtime-error2905
PR accepted @runtime-error2905
Successfully merged to  our CART.
Need to Star this repo incase not done.
🚀🚀👍


syncer: support start incremental task without configuring binlog-pos/gtid

What problem does this PR solve?

Issue Number: close #7393
What is changed and how it works?

get newest binlog-pos/gtid from upstream

Check List
Tests

Unit test
Integration test

Release note
support start incremental task without configuring binlog-pos/gtid

/run-all-tests

Codecov Report

Merging #7394 (45cea74) into master (84ef430) will increase coverage by 0.0333%.
The diff coverage is 72.8915%.

Additional details and impacted files

Flag
Coverage Δ

dm
51.9639% <25.9259%> (-0.0073%)
:arrow_down:

engine
60.8666% <85.7142%> (+0.0129%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #7394        +/-   ##
================================================
+ Coverage   59.7990%   59.8323%   +0.0333%
================================================
  Files           801        802         +1
  Lines         91968      92104       +136
================================================
+ Hits          54996      55108       +112
- Misses        32180      32200        +20
- Partials       4792       4796         +4

/run-all-tests

and also test upstream has empty GTID set when GTID is enabled

Does this meet the requirements? https://github.com/pingcap/tiflow/blob/d6dd20f0cc6378b602cda2c486a0396f54e3cd3f/dm/master/server_test.go#L2894
For empty GTID, I think that's same with all mode task like this issue https://github.com/pingcap/tiflow/issues/7037, cc @liumengya94

/merge


Update the documentation

Make the documentation a bit more user-friendly — especially the Definition documents.

Content has been updated