Assign value of classnames of test results to relative path of spec file

Hi,
We are creating Sonar reports based on the data generated by karma-junit-reporter. We recently upgraded to Sonar 4.5.1 and It is not able to generate report based on the TEST-results.xml file generated. It is expecting the classnames to be relative paths of the corresponding spec files. It will be of great help if you can implement this feature or provide guidance on how to achieve it.

It will be of great help if you can implement this feature or provide guidance on how to achieve it.

@vojtajina @btford @pkozlowski-opensource It is really sad that no one is looking into the issues logged in this project and the project is not actively developed since October 2014. At the least, we expect a response from the authors clarifying if the issue would be taken care.

@sravikiran can you provide example of how it's look now and how you expect it should look
Thanks

@maksimr Thanks for responding. Give me a day, I will get back to you with the right data.

+1 for this.
need a different reporter type that corresponds to js-test-driver.
See below:http://docs.sonarqube.org/display/SONAR/Unit+Test+results+import

@maksimr Sorry for the delay in responding. I was off for a few days and was too busy at work after that so I almost missed responding to your question.
Following is an instance of testcase that gets generated by the Karma JUnit Reporter:
<testcase name="should coordinate the bootstrap functions" time="0" classname="PhantomJS 1.9.7 (Windows 7).Activator Factory run">
Following is what Sonar expects:
<testcase name="should coordinate the bootstrap functions" time="0" classname="src/js/tests/mytestfile.js">

@sravikiran thanks!
Hm... I don't think we have file path in reporter on success

@maksimr Yeah, we don't have. Karma Jasmine Adapter is not sending file path in the event object.

Hi,
have you any news on possibility to be compatible with sonar ?
thanks

@mathilde-pellerin I don't have any update. I am still waiting to hear from @maksimr.

We have the same problem, Sonar does not accept classnames that look like this:
classname="PhantomJS 1.9.8 (Linux).LodashHelpers"

It logs this error
[Step 4/4] 21:26:55.162 WARN  - Test result will not be saved for test class "9.8 (Linux).LodashHelpers", because SonarQube associated resource has not been found using file name: "9/8 (Linux)/LodashHelpers.js"

+1 :)

All of us are waiting for an answer and I think the authors are still busy with something.
@vojtajina @btford @pkozlowski-opensource @maksimr Please update here if any work is started on this issue. If you keep us updated, we will try to help you as well!

@sravikiran does this https://github.com/karma-runner/karma-junit-reporter/pull/36 actually solve the issues, or would it at least help towards a solution?

@Dignifiedquire Thanks for letting me know this. I will try it out.

@Dignifiedquire The fix #36 does not solves the problem because the expectation is classname should be path to file as:  classname="src/js/tests/mytestfile.js",  but its not, still it is as: classname="PhantomJS_1_9_8_(Linux).models.AnalyticsModule_test" that is not accepted by sonar.
@sravikiran what do you think? Did you get any other fix?

@irfanraza I had written a grunt task that runs after karma-junit-reporter to replace class names with a static string. But it solved only half of the problem. Sonar build is passing after making this change, but Sonar fails to show report of individual files.
I didn't try #36 and I won't be able to try it now.

you will need to go through each spec file and use reg ex to extract test case names against each spec file.
then once coverage xml is created, read the xml and replace the classname by mapping spec file name against test case name ...
We did above to publish valid unit test report xml to SonarQube.

Any news on that? We have the same exact problem. #36 does not fix this issue here.

Any further updates we are using the new https://github.com/tornaia/karma-sonarqube-unit-reporter, and we require the file path to be the correct classname not some english text...  SonarQube generic plugin rejects the tests without it

I have custom function transforming the report to what sonar is expecting...

Can you share the custom function or explain your methodology ?
Thanks

below is the gulp task i am using to fix junit results xml to support sonar xml format.
Note: all our spec files are using same name as js file.
Ex:
js file - xyz.js
spec file - xyz.spec.js
`gulp.task('replace-sonar-utest', ['clean-tmp', 'replace-sonar-coverage', 'test-for-sonar'], function (done) {
var xmlEntities = new (require('html-entities').XmlEntities)();
var XmlDocument = require('xmldoc').XmlDocument;
var JASMINE_TESTCASE_REGEX = /[^\w]x?it\s?('"['"]/g;
var JASMINE_SUITE_REGEX = /[^\w]x?describe\s?('"['"]/g;
var specs = [];
glob.sync('./app/' + pkg + '/**/*.spec.js').forEach(function (file) {
var tests = [],
content = fs.readFileSync(file, 'utf8');
var matches = content.match(JASMINE_TESTCASE_REGEX);
if (matches !== null) {
  // #3
  for (var i = 0, len = matches.length; i < len; i++) {
    tests.push(xmlEntities.encode(matches[i].replace(JASMINE_TESTCASE_REGEX, '$1')).replace(/\\/g, '')); // remove escaped characters
  }

  var suiteMatches = content.match(JASMINE_SUITE_REGEX);
  var suites = [];
  for (var j = 0, len1 = suiteMatches.length; j < len1; j++) {
    suites.push(xmlEntities.encode(suiteMatches[j].replace(JASMINE_SUITE_REGEX, '$1')).replace(/\\/g, '')); // remove escaped characters
  }

  specs.push({
    'name': path.basename(file, path.extname(file)),
    'tests': tests,
    'suites': suites
  });
}

});
var content = new XmlDocument(fs.readFileSync('./log/test-results.xml')),
testsuites;
if (content.name === 'testsuite') {
testsuites = [content];
} else {
testsuites = content.childrenNamed('testsuite');
}
for (var i = 0; i < testsuites.length; i++) {
testsuites[i].eachChild(function (testcase) {
if (testcase.name === 'testcase') {
var name = xmlEntities.encode(testcase.attr.name);
var className = xmlEntities.encode(testcase.attr.classname);
var matchingSpecs = (_.filter(specs, function (spec) {
var s = _.find(spec.suites, function (suite) {
return suite === className || xmlEntities.encode(suite) === className;
});
      if (s) {
        return _.find(spec.tests, function (test) {
          return test === name || xmlEntities.encode(test) === name;
        });
      }
    }));

    var matchingSpec = matchingSpecs[0];
    /*if (matchingSpecs.length > 1) {
      var m = _.find(specs, function (spec) {
        return spec.name === matchingSpec;
      });
      m.tests = _.without(m.tests, name);
    }*/
    testcase.attr.name = name;
    testcase.attr.classname = matchingSpec.name.replace(/\./g, '_');
  }
});

}
// #5
var PREFIX = '',
SUFFIX = '',
resultContent = PREFIX;
resultContent = resultContent.concat(testsuites);
fs.writeFileSync('./.tmp/sonar/results/TESTS-xunit.xml', resultContent.concat(SUFFIX), 'utf8');
done();
});`


Plotting aborted

I always get the following errors or similar and the plotter aborts:
chia_plot: /home/paolo/chia-plotter/include/chia/bitfield_index.hpp:45: std::pair<long unsigned int, long unsigned int> bitfield_index::lookup(uint64_t, uint64_t) const: Assertion `bitfield_.get(pos) && bitfield_.get(pos + offset)' failed.
./madmax.sh: line 2:  3504 Aborted                 (core dumped) ./chia_plot -n 10 -r 8 -u 256 -t /media/paolo/P2/ here -d /media/paolo/EXOS2/ -c .... -f .....
terminate called after throwing an instance of 'std::runtime_error'
what():  thread failed with: input not sorted
Aborted (core dumped)
What could be the cause and how can I solve this?
Thanks!

Unstable OverClock, Faulty Memory and XMP can cause this. Run a Memtest.
Also Check #775 , #732

Thanks for the tip! I'm not overclocking, but I ran a memtest and found a faulty RAM bank... Now i'm with only 2x16GB left. it looks as if it will take two times as much to complete a plot... Is this possible?

Unstable OverClock, Faulty Memory or XMP can cause this. Run a Memtest.
Also Check #775 , #732

Thanks for the tip! I'm not overclocking, but I ran a memtest and found a faulty RAM bank... Now i'm with only 2x16GB left. it looks as if it will take two times as much to complete a plot... Is this possible?

1- If you use ramdisk 110GB, set -v 8 (bucket 256)
2- Check temp 1,
I had this problem on temp1 3sas HDD on raid0, HDDs are not same brand and size

I have the same Issue since the last update for madmax plotter on 3 different plotting systems.
Plotting randomly stops. I have also one system with old madamax, and its working fine.
System 1: i9 10900F 64gb DDR4
System 2: 2x XEON 2698v4 64gb DDR4
System 3: Ryzen 5950x 64gb DDR4
Old madmax, without problems:
System 4:  i9 10900F 64gb DDR4
Before update, I plotted about 5000 plots without any problems or crash.


remove manual install instructions now that we have MSI

now that we have an MSI we can remove the manual install steps in the readme - to make it less likely that users have multiple copies of bicep (and in the path) and have trouble figuring out which is being used and from where.

Just had a thought on this - rather than deprecating the PowerShell install instructions entirely, why not just have them run the installer in a non-interactive mode.
That way you don't have to worry about conflicting versions / paths, but still have the ease of just running an install script.


Merge changes from upcoming_0.12.x branch

dependency upgrades
minor code-smells fixed
check for filesystem-layout first

:+1:

👍

Codecov Report

Merging #109 into master will increase coverage by 0.47%.
The diff coverage is 83.33%.

@@             Coverage Diff              @@
##             master     #109      +/-   ##
============================================
+ Coverage      72.2%   72.68%   +0.47%
- Complexity      238      242       +4
============================================
  Files            48       48
  Lines           842      842
  Branches         40       39       -1
============================================
+ Hits            608      612       +4
+ Misses          211      207       -4
  Partials         23       23

Impacted Files
Coverage Δ
Complexity Δ

...in/java/org/zalando/stups/tokens/FileSupplier.java
85.71% <70%> (-8.74%)
9 <5> (+3)

.../org/zalando/stups/tokens/AccessTokensBuilder.java
74.04% <92.85%> (+0.23%)
44 <12> (+2)
:arrow_up:

.../tokens/JsonFileBackedUserCredentialsProvider.java
100% <0%> (ø)
3% <0%> (ø)
:arrow_down:

...g/zalando/stups/tokens/CloseableTokenVerifier.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...okens/JsonFileBackedClientCredentialsProvider.java
100% <0%> (ø)
3% <0%> (ø)
:arrow_down:

...org/zalando/stups/tokens/AccessTokenRefresher.java
83.58% <0%> (+1.22%)
17% <0%> (-1%)
:arrow_down:

...rg/zalando/stups/tokens/CloseableHttpProvider.java
87.5% <0%> (+2.08%)
6% <0%> (ø)
:arrow_down:

...in/java/org/zalando/stups/tokens/util/Objects.java
91.66% <0%> (+7.05%)
7% <0%> (ø)
:arrow_down:

src/main/java/org/zalando/stups/tokens/Tokens.java
81.81% <0%> (+12.58%)
3% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


License will expire on TLS branch

Problem description
License expired
Extra information
elasticsearch_1  | {"type": "server", "timestamp": "2021-10-15T23:14:47,975Z", "level": "ERROR", "component": "o.e.x.s.a.f.SecurityActionFilter", "cluster.name": "docker-cluster", "node.name": "b75d7c7a50b9", "message": "blocking [cluster:monitor/nodes/stats] operation due to expired license. Cluster health, cluster stats and indices stats \noperations are blocked on license expiration. All data operations (read and write) continue to work. \nIf you have a new license, please update it. Otherwise, please reach out to your support contact.", "cluster.uuid": "l6Sld-zwTASMTwV4nLRhEw", "node.id": "OGZ70chtQIOu89uzBphQeA"  }
Stack configuration

Docker setup

$ docker version

[OUTPUT HERE]

$ docker-compose version

[OUTPUT HERE]

Container logs

$ docker-compose logs

[OUTPUT HERE]

It says:
After this license expires, you can continue using the free features
seamlessly, without losing any data.
*However Kibana won't start at all.  So the readme should state that you
need to get off the trial license and move over to basic, early on. *
On Fri, Oct 15, 2021 at 7:18 PM Antoine Cotten @.***>
wrote:

I think that's exactly what the very first part of the README states?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_deviantony_docker-2Delk_issues_628-23issuecomment-2D944801921&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=bNGYvrQaLXxaelhZ3_MDlReGckp71DWj2X3rWmhenkQ&s=iDbFuHUkGNVmY3RVAhoT7gM2krMf3COrRANhzurJyy0&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMNB64A343PI4NHHFGRXH2TUHCZDXANCNFSM5GC5UNKA&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=bNGYvrQaLXxaelhZ3_MDlReGckp71DWj2X3rWmhenkQ&s=aMPOUsz_XmmKsDKhN-8Cpi80-8sLa3CwwXNW7v9VOyM&e=
.
Triage notifications on the go with GitHub Mobile for iOS
https://urldefense.proofpoint.com/v2/url?u=https-3A__apps.apple.com_app_apple-2Dstore_id1477376905-3Fct-3Dnotification-2Demail-26mt-3D8-26pt-3D524675&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=bNGYvrQaLXxaelhZ3_MDlReGckp71DWj2X3rWmhenkQ&s=YRxpbK4iPluZnMz_byrxGpq0zEYzLnu_g9yVuBZUAaw&e=
or Android
https://urldefense.proofpoint.com/v2/url?u=https-3A__play.google.com_store_apps_details-3Fid-3Dcom.github.android-26referrer-3Dutm-5Fcampaign-253Dnotification-2Demail-2526utm-5Fmedium-253Demail-2526utm-5Fsource-253Dgithub&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=bNGYvrQaLXxaelhZ3_MDlReGckp71DWj2X3rWmhenkQ&s=P5cFVmibsa-XLHwGyQ2CgQn1IB9A3vPgqEQZMu9LS3o&e=.

--
Erik Witkop  |  DOD Systems Engineer | PCNSE CISSP GPEN
Palo Alto Networks  |  Boston, MA |  USA
Mobile:<PHONE_NUMBER>  | www.paloaltonetworks.com
https://www.paloaltonetworks.com/
https://www.paloaltonetworks.com/
https://www.linkedin.com/company/palo-alto-networks
https://www.facebook.com/PaloAltoNetworks/
https://twitter.com/PaloAltoNtwks
The content of this message is the proprietary and confidential property of
Palo Alto Networks, and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by e-mail.
Any unauthorized use or distribution of the content of this message is
prohibited.

These instructions are pretty cool.
https://ospaarmann.medium.com/tidbits-solving-the-elasticsearch-x-pack-license-issue-in-docker-d15bb22d82fd
On Fri, Oct 15, 2021 at 7:37 PM Erik Witkop @.***>
wrote:

It says:
After this license expires, you can continue using the free features
seamlessly, without losing any data.
*However Kibana won't start at all.  So the readme should state that you
need to get off the trial license and move over to basic, early on. *
On Fri, Oct 15, 2021 at 7:18 PM Antoine Cotten @.***>
wrote:

I think that's exactly what the very first part of the README states?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_deviantony_docker-2Delk_issues_628-23issuecomment-2D944801921&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=bNGYvrQaLXxaelhZ3_MDlReGckp71DWj2X3rWmhenkQ&s=iDbFuHUkGNVmY3RVAhoT7gM2krMf3COrRANhzurJyy0&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMNB64A343PI4NHHFGRXH2TUHCZDXANCNFSM5GC5UNKA&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=bNGYvrQaLXxaelhZ3_MDlReGckp71DWj2X3rWmhenkQ&s=aMPOUsz_XmmKsDKhN-8Cpi80-8sLa3CwwXNW7v9VOyM&e=
.
Triage notifications on the go with GitHub Mobile for iOS
https://urldefense.proofpoint.com/v2/url?u=https-3A__apps.apple.com_app_apple-2Dstore_id1477376905-3Fct-3Dnotification-2Demail-26mt-3D8-26pt-3D524675&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=bNGYvrQaLXxaelhZ3_MDlReGckp71DWj2X3rWmhenkQ&s=YRxpbK4iPluZnMz_byrxGpq0zEYzLnu_g9yVuBZUAaw&e=
or Android
https://urldefense.proofpoint.com/v2/url?u=https-3A__play.google.com_store_apps_details-3Fid-3Dcom.github.android-26referrer-3Dutm-5Fcampaign-253Dnotification-2Demail-2526utm-5Fmedium-253Demail-2526utm-5Fsource-253Dgithub&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=bNGYvrQaLXxaelhZ3_MDlReGckp71DWj2X3rWmhenkQ&s=P5cFVmibsa-XLHwGyQ2CgQn1IB9A3vPgqEQZMu9LS3o&e=.

--
Erik Witkop  |  DOD Systems Engineer | PCNSE CISSP GPEN
Palo Alto Networks  |  Boston, MA |  USA
Mobile:<PHONE_NUMBER>  | www.paloaltonetworks.com
https://www.paloaltonetworks.com/
https://www.paloaltonetworks.com/
https://www.linkedin.com/company/palo-alto-networks
https://www.facebook.com/PaloAltoNetworks/
https://twitter.com/PaloAltoNtwks
The content of this message is the proprietary and confidential property
of Palo Alto Networks, and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by e-mail.
Any unauthorized use or distribution of the content of this message is
prohibited.

--
Erik Witkop  |  DOD Systems Engineer | PCNSE CISSP GPEN
Palo Alto Networks  |  Boston, MA |  USA
Mobile:<PHONE_NUMBER>  | www.paloaltonetworks.com
https://www.paloaltonetworks.com/
https://www.paloaltonetworks.com/
https://www.linkedin.com/company/palo-alto-networks
https://www.facebook.com/PaloAltoNetworks/
https://twitter.com/PaloAltoNtwks
The content of this message is the proprietary and confidential property of
Palo Alto Networks, and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by e-mail.
Any unauthorized use or distribution of the content of this message is
prohibited.

OK the fact that Kibana doesn't start at all is unexpected and worth mentioning. Some features are disabled but all components should be able to run.
Is there any error message in the logs of the Kibana container? Something that could help me figure how to assist and what to document?

concurrent.FutureTask.run(FutureTask.java:264) [?:?]",
elasticsearch_1  | "at
org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:673)
[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
[?:?]",
elasticsearch_1  | "at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
[?:?]",
elasticsearch_1  | "at java.lang.Thread.run(Thread.java:831) [?:?]"] }
elasticsearch_1  | {"type": "server", "timestamp":
"2021-10-15T23:54:32,475Z", "level": "ERROR", "component":
"o.e.x.s.a.f.SecurityActionFilter", "cluster.name": "docker-cluster", "
node.name": "8bd79f150dae", "message": "blocking
[cluster:monitor/nodes/stats] operation due to expired license. Cluster
health, cluster stats and indices stats \noperations are blocked on license
expiration. All data operations (read and write) continue to work. \nIf you
have a new license, please update it. Otherwise, please reach out to your
support contact.", "cluster.uuid": "l6Sld-zwTASMTwV4nLRhEw", "node.id":
"OGZ70chtQIOu89uzBphQeA"  }
elasticsearch_1  | {"type": "server", "timestamp":
"2021-10-15T23:54:32,475Z", "level": "ERROR", "component":
"o.e.x.m.c.n.NodeStatsCollector", "cluster.name": "docker-cluster", "
node.name": "8bd79f150dae", "message": "collector [node_stats] failed to
collect data", "cluster.uuid": "l6Sld-zwTASMTwV4nLRhEw", "node.id":
"OGZ70chtQIOu89uzBphQeA" ,
elasticsearch_1  | "stacktrace":
["org.elasticsearch.ElasticsearchSecurityException: current license is
non-compliant for [security]",
elasticsearch_1  | "at
org.elasticsearch.license.LicenseUtils.newComplianceException(LicenseUtils.java:27)
~[?:?]",
elasticsearch_1  | "at
org.elasticsearch.xpack.security.action.filter.SecurityActionFilter.apply(SecurityActionFilter.java:88)
~[?:?]",
elasticsearch_1  | "at
org.elasticsearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:171)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:149)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:77)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.client.node.NodeClient.executeLocally(NodeClient.java:86)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.client.node.NodeClient.doExecute(NodeClient.java:66)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:402)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:390)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.client.support.AbstractClient$ClusterAdmin.execute(AbstractClient.java:689)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.client.support.AbstractClient$ClusterAdmin.nodesStats(AbstractClient.java:786)
~[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.xpack.monitoring.collector.node.NodeStatsCollector.doCollect(NodeStatsCollector.java:81)
~[x-pack-monitoring-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.xpack.monitoring.collector.Collector.collect(Collector.java:85)
[x-pack-monitoring-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.xpack.monitoring.MonitoringService$MonitoringExecution$1.doRun(MonitoringService.java:252)
[x-pack-monitoring-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)
[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[?:?]",
elasticsearch_1  | "at
java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]",
elasticsearch_1  | "at
org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:673)
[elasticsearch-7.13.4.jar:7.13.4]",
elasticsearch_1  | "at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
[?:?]",
elasticsearch_1  | "at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
[?:?]",
elasticsearch_1  | "at java.lang.Thread.run(Thread.java:831) [?:?]"] }
elasticsearch_1  | {"type": "server", "timestamp":
"2021-10-15T23:54:32,479Z", "level": "ERROR", "component":
"o.e.x.s.a.f.SecurityActionFilter", "cluster.name": "docker-cluster", "
node.name": "8bd79f150dae", "message": "blocking [indices:monitor/stats]
operation due to expired license. Cluster health, cluster stats and indices
stats \noperations are blocked on license expiration. All data operations
(read and write) continue to work. \nIf you have a new license, please
update it. Otherwise, please reach out to your support contact.",
"cluster.uuid": "l6Sld-zwTASMTwV4nLRhEw", "node.id":
"OGZ70chtQIOu89uzBphQeA"  }
elasticsearch_1  | {"type": "server", "timestamp":
"2021-10-15T23:54:32,479Z", "level": "ERROR", "component":
"o.e.x.m.c.i.IndexStatsCollector", "cluster.name": "docker-cluster", "
node.name": "8bd79f150dae", "message": "collector [index-stats] failed to
collect data", "cluster.uuid": "l6Sld-zwTASMTwV4nLRhEw", "node.id":
"OGZ70chtQIOu89uzBphQeA" ,
The fix is to exec into the container and run:
curl  -k  -XPOST -u elastic '
https://localhost:9200/_license/start_basic?acknowledge=true' -H
"Content-Type: application/json"
On Fri, Oct 15, 2021 at 7:44 PM Antoine Cotten @.***>
wrote:

OK the fact that Kibana doesn't start at all is unexpected and worth
mentioning. Some features are disabled but all components should be
able to run.
Is there any error message in the logs of the Kibana container? Something
that could help me figure how to assist and what to document?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_deviantony_docker-2Delk_issues_628-23issuecomment-2D944811097&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=C04OxWX74jFKm_XpRq5NMli93L-_KPNo_KtWYeEcyHo&s=sv1L8egTLiBMF42kwOiYqz9VbAFDZQIRvj7_SWxEGAs&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMNB64FXOSR3Z7XT3ELTEFLUHC4FDANCNFSM5GC5UNKA&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=C04OxWX74jFKm_XpRq5NMli93L-_KPNo_KtWYeEcyHo&s=qkioUC5EzbPgNnGoTgIYc9FXoDn5nq0R7rtHS_WMnYA&e=
.
Triage notifications on the go with GitHub Mobile for iOS
https://urldefense.proofpoint.com/v2/url?u=https-3A__apps.apple.com_app_apple-2Dstore_id1477376905-3Fct-3Dnotification-2Demail-26mt-3D8-26pt-3D524675&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=C04OxWX74jFKm_XpRq5NMli93L-_KPNo_KtWYeEcyHo&s=pHk4tgT3BBE61K_NpYtCw8o6DEQVnDX_x5-f5JIaSDA&e=
or Android
https://urldefense.proofpoint.com/v2/url?u=https-3A__play.google.com_store_apps_details-3Fid-3Dcom.github.android-26referrer-3Dutm-5Fcampaign-253Dnotification-2Demail-2526utm-5Fmedium-253Demail-2526utm-5Fsource-253Dgithub&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=C04OxWX74jFKm_XpRq5NMli93L-_KPNo_KtWYeEcyHo&s=z7oQBZByQddgENZpA5zqz5Ch7gzwrMCCM1ktKXZXDgM&e=.

--
Erik Witkop  |  DOD Systems Engineer | PCNSE CISSP GPEN
Palo Alto Networks  |  Boston, MA |  USA
Mobile:<PHONE_NUMBER>  | www.paloaltonetworks.com
https://www.paloaltonetworks.com/
https://www.paloaltonetworks.com/
https://www.linkedin.com/company/palo-alto-networks
https://www.facebook.com/PaloAltoNetworks/
https://twitter.com/PaloAltoNtwks
The content of this message is the proprietary and confidential property of
Palo Alto Networks, and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by e-mail.
Any unauthorized use or distribution of the content of this message is
prohibited.

@ewitkop-panw I tried to reproduce this issue by forcing my trial license to expire (essentially by deleting it so it switches to basic before the expiry date), but I wasn't able to.
Here is the detail of what I did:
$ curl -D- -X DELETE localhost:9200/_license -u elastic:changeme

HTTP/1.1 200 OK
X-elastic-product: Elasticsearch
content-type: application/json
content-length: 21

{"acknowledged":true}

$ curl -D- localhost:9200/_license -u elastic:changeme

HTTP/1.1 200 OK
X-elastic-product: Elasticsearch
content-type: application/json
content-length: 371

{
  "license" : {
    "status" : "active",
    "uid" : "1e15e9f9-5ca4-4309-9903-04b4453c6a8e",
    "type" : "basic",
    "issue_date" : "2021-10-30T15:53:53.031Z",
    "issue_date_in_millis" :<PHONE_NUMBER>031,
    "max_nodes" : 1000,
    "max_resource_units" : null,
    "issued_to" : "docker-cluster",
    "issuer" : "elasticsearch",
    "start_date_in_millis" : -1
  }
}

Then I restarted the stack. Kibana started just fine, and I was able to log in:
kibana_1         | [2021-10-30T15:58:59.687+00:00][INFO ][status] Kibana is now available (was degraded)
kibana_1         | [2021-10-30T16:05:08.964+00:00][INFO ][plugins.security.routes] Logging in with provider "basic" (basic)

Side note:
I see you didn't fill in any information in your original issue description, although we clearly indicate that it is difficult for us to provide guidance without knowing anything about the runtime environment and the configuration of the stack.
Therefore I am closing the issue for the two following reasons:

Can't reproduce with the default config
No information about the user's environment and config


CS0012	The type 'IEnumerable' is defined in an assembly that is not referenced.

I tried to replace X.PagedList from PagedList. But then there are many errors in the cshtml in my project although the project could be compiled and execute without any error. The error is as the following,
Error	CS0012	The type 'IEnumerable' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
How do we resolve it? I already target the project to .NET 4.6.1 and the version of X.PagedList is <IP_ADDRESS>00
And my web.config already has added the following,
<system.web>
    <compilation debug="true" targetFramework="4.6.1" >
      <assemblies>
        <add assembly="System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
      </assemblies>
    </compilation>

Hi! X.PagedList is OK.
You can try to fix your problem in two ways:

Install in your project Microsoft.NETCore.Portable.Compatibility package:
https://www.nuget.org/packages/Microsoft.NETCore.Portable.Compatibility
"Enables compatiblity with portable libraries targeting previous .NET releases like .NET Framework 4.0 and Silverlight.
This package supports retargeting references to classic reference assemblies (mscorlib.dll, system.dll, etc) to new contract assemblies (System.Runtime.dll, System.IO, etc)..."
Change X.PagedList target  profile from PCL to .NetStandard1.0. See my test fork for example:
https://github.com/sashapvt/X.PagedList/tree/net-core


BorderColor support for all widgets

Hello has when borderColor support for widgets ca becomes urgent because for a collectionView by example it's not possible for cells to have border bottom

It's already possible.  Just append a 1px high Composite to the bottom of your cell.

thank you it's work

Closing this for now. Please comment if you have any more issues.


Update lightning-talks-5AHIF.md

Topic is fine, but date has already been taken. Could you choose a new date and send a new pull request?


Fix diffs

I am working towards reproducible results here. First milestone: 50_gatk_PrintReads, since this is what we consider the "BAM" files

at least for Mouse: milestone reached, after

fixing #threads for BWA to a constant number
fixing -nt to 1 for GATK's TargetRealigner


How can I use the angular-screenshot by angular 2.x.x or angular4.x.x?

I hope use in the angular 2.x.x or angular4.x.x, but I don't know what to doing.

@weihanchen  , suggest something on this

Sorry, Angular2+ has not been supported so far, but there are some explanations for the upgraded version:

The part of the Angular directive only handles the dom element specification, style and other related configuration, and passes the screenshot canvas operation to util/dom-process.js.

Design the core dom operation part to util/dom-process.js, and thereby obtain the screenshot block selected by user.

Convert the specified element to svg via dom-to-image and then crop it according to the user's screenshot block, and finally convert to png .

So if you want to move this project to Angular2+, the difference is just the logic of the directive.
However, the author himself did not have a deeper research on Angular2+ and did not have time to upgrade. I hope that someone who is willing to contact me will help upgrade to Angular2+.
Thanks,
Weihanchen

@weihanchen I am willing to upgrade it to Angular4.

@bsingh06 @weihanchen  did you get chance to update it? Or any other library in Angular 4+?

Is there another option today?

I am working on the ng2-screenshot, but it has not been released yet.
Please give me some time to finish.
Thanks.

ng2-screenshot already release v0.1.2
#4

AMAZING! THANKS


Does macOS Big sur 11.0 work?

I accidentally deleted the recovery partition of my macOS 11.0, so im here to ask, does it work with macOS 11.0? thanks.

No.


UX improvements for Radar / Sidebar

The Radar and its sidebar should be completely redesigned. Few things:

The dimension should NOT be defined in pixel, but in Bootstrap rows and columns (for example: col-lg-4 for the sidebar and col-lg-8 for the radar), now it has Bootstrap mixed with vanilla but unresponsive code. Just use the Bootstrap grid to have it responsive and in order to save time. For example:

<template>
  <require from="../radar/radar"></require>
  <require from="../radar/legend"></require>
  <require from="../radar/technologysheet"></require>

Radar

          TechRadar

                Custom

                Trends

            <legend></legend>

          <radar view="trend"></radar>

    <technologysheet></technologysheet>

</template>

Sidebar: the hide / edit visualisation is conceptually wrong; if you want to hide all the sidebar, then we should have a collapsible sidebar (hide all sidebar, not just the inputs: we are still using that space); if you want to hide just the inputs, why still show the legend? I'd remove this option and just leave always the sidebar present for the sake of simplicity
The legend could be added in the Radar with D3 itself or D3 Legend, freeing space in the Sidebar, improving embedding, ...
The legend should be explained well: what is TRL? What is Perez Technological Revolution?
Trends should be buttons

                <button type="button" class="btn btn-primary btn-sm" repeat.for="t of appState.trends" class="${ t == appState.data.activeTrend ? 'radar-trend-item-selected' : 'radar-trend-item' }" click.trigger="selectTrend(t)">
                  ${t.Name}

                </button>

Nav Tabs should be redesigned as proper navigation element following the main style:

                Custom

                Trends

Customisation inputs should be properly formatted with Bootstrap input groups and inputs, not nested divs.

Add filter / Remove filter do not work, their purpose should be clear should, format them as buttons

The Show Trends checkbox should be a button instead

Improve dropdowns with Select2 #20

Make the Radar responsive as well #15

Fix overlap of labels in the Radar

If necessary, use the D3 Annotations plugins, it's very good

In order to improve the visualisation of the radar, d3-zoom might be added for zoom and pan functionalities.

I'm updating the codebase in PR #18


Attributes Sourcemap & AST changes

Added source maps for Attributes
Changed the structure for DataStructure and thus Attributes to be up to date with latest spec.
Serialised Resource, Payload & Action in accordance with the new spec.

Debt: We haven't changed the actual structures of Resource, Payload and Action to represent the exact structures in the latest spec.
For @zdne to review & merge.

@zdne This is ready to go.

@pksunkara well, I am merging this but ... I am scared, ha ha


Some images load, some show load icon, some doesn't

I was reading codes from a project. Then for some reasons, I thought I should be reading .md file offline. Then I came to know about this - MarkdownLivePreview.
Now, when I started reading the .md file I had, I noticed something different.
One picture is being rendered, other is not.
But the link is fresh and live, here
Here is a snap :

And sometimes it shows a loading like image:

The code fetching the images is a bit dodgy... It would need to be re-written. Basically, the image is only updated when the whole preview is updated (basically when you press a key). There is currently no callback which re-renders the preview as soon as the image has finished loading. So, if you wanna see the pictures, you have to type in things (space backspace in repeat would work).
Having a callback is technically possible though, it's just not implemented yet, mainly because the code is quite messy and I don't have a hip of free time right now (I'm passing the HSC), but that should change soon 🙂

@math2001  can you assign me into this issue ?
I'm interested.

Hey, thank you for wanting to contribute :heart:!
Here's probably where you wanna start:
https://github.com/math2001/MarkdownLivePreview/blob/master/image_manager.py#L62
Just to give you my personal opinion: this package is just a stack of bad code, disorganized and unclear. I think everything should be re-written, properly. It's still possible to add in this feature, but don't feel bad if you don't feel like it's going to be worth the effort 🙂

Thanks a lot for assigning me.
My opinion is - why don't we try to fix this thing,
meanwhile we re-write from scratch.

I've unassigned you because I have rewritten MarkdownLivePreview, and this issue is now fixed really cleanly. It turned out to be a lot easier to implement than I original thought, and I probably could now do it in the current code base. The whole package needed to be re-written anyway, just to make it easier for people to contribute.
It's only on my computer for now, but it should arrive soon :slightly_smiling_face:

Its awesome.

This is fixed by v3.0.0 :slightly_smiling_face:
This is how the "image manager" (just a function) is used:
https://github.com/math2001/MarkdownLivePreview/blob/192f61bf0ced21b906bfb98102e556498b9196d4/markdown2html.py#L60-L65
And this is the "image manager"
https://github.com/math2001/MarkdownLivePreview/blob/192f61bf0ced21b906bfb98102e556498b9196d4/markdown2html.py#L99-L138


Values in localStorage are not only strings

The user of the lib can put all types of values into localStorage. So the ILocalStorageService should be a generic.
Any issues regarding this change?

@morphinkf do you have some comments? can I merge this PR?

@m4cx I was concerned about this but I've realized misunderstanding the documentation.  Thanks for the fix.
@vvakame yes.  sorry for the inconvenience.  and i think the user i used to commit was wrong. (@morphinkf == @kenfdev)

@kenfdev you're welcome. stumpled upon this problem during work today ;)

What is needed to have this PR merged?

@kenfdev thanks!
@m4cx sorry, I was late. It merged!


Clean up DynamicWinsockMethods, enums, and small structs.

@stephentoub @davidsh PTAL

Left minor comments, otherwise LGTM.

LGTM


DSA codes added.

these codes were made by me when learned the DSA in my college.
label:hacktoberfest

Please add this label: "hacktoberfest-accepted" to this pull request.


[potential issue] network polling workers do not stop when genome is changed / reset event

When a reset event is called (IE genome change), we should stop all networking polling workers because its most likely what they are polling for is no longer relevant

Noting this issue will be avoided with a migration to websocket events as per https://github.com/feagi/brain-visualizer/issues/26

This issue appears to be resolved


Fix: Renamed bluebanquise_ to bluebqnauise- in bluebaquise and powerman roles

Roles were still referencing old package names.

Dear @thiagocardozo
Thanks a lot for this PR.
There is already a PR regarding this issue. I am fixing molecules tests also : https://github.com/bluebanquise/bluebanquise/pull/653/files

Hello, Ill close this PR then. I didnt check the PRs before.


Update http4s-blaze-client, ... to 0.18.23

Updates

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

from 0.18.22 to 0.18.23.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

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

Codecov Report

Merging #52 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   44.63%   44.63%
=======================================
  Files          31       31
  Lines         289      289
=======================================
  Hits          129      129
  Misses        160      160

Continue to review full report at Codecov.

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


Constraint support animator proxy for osx

Hi, there is a new idea for #272 I submited before.
This would suit SnapKit 3.0 features.

Going to close this for now, I think this has gone a bit stale because I didn't review it and I somewhat feel like this is outside the realm of what SnapKit should support directly.
macOS is moving more towards block based animations that work w/o NSAnimator anyways.


Update all publisher schemas to generic_with_external_related_links

Remove the guard clauses, this PR enables us to republish all Publisher content with the new schema, and in doing so allows publishing-api to manage the routes for these content items.
https://trello.com/c/VV0MJM5u/616-update-publisher-to-manage-routes-with-publishingapi-5

Small style niggle, the first commit message doesn't follow the convention of starting with active verb etc. It might also be helpful to add a small explanation for that commit

Looks good!

I think https://github.com/alphagov/publisher/blob/master/lib/licence_content_importer.rb#L16 can be removed?


Build failure

While building, I faced two problems.
First, the linking of the openssl library failed.
I could solve this by changing the required version in the ´CMakeList.txt´ (line 18) from ´1.0.2p´ to ´1.0.2s´.
The second problem concerns boost. It is also referenced in https://github.com/Microsoft/cpprestsdk/issues/1054 and
https://github.com/zaphoyd/websocketpp/issues/794
for the case at hand it can be circumvented by installing boost 1.60
´brew uninstall boost´
´brew install<EMAIL_ADDRESS>additionally the boost path needs to be set:
´export<EMAIL_ADDRESS>In order for CMake to find it.

Thank you @lucasvsl, that solved my problem! 👍

To fix CMake error in finding openssl on MAC, execute the below command along with the above suggest change:
export OPENSSL_ROOT_DIR=/usr/local/opt/openssl


Remind channel name or nick in input placeholder

Fixes #343.
Result on small device:

I think this is unnecessary clutter on the desktop - maybe hide it there?

Nah, I think it's just as valuable on desktop than mobile. I was kinda not fond of the idea at first, but you get used to it in 5 seconds and it's actually not bad to have it there.
Slack added this fairly recently too, pretty sure some people complained about accidentally messaging the wrong coworkers :D

@MaxLeiter, once this is enabled, if you really don't like it, you can easily hide it with #input::-webkit-input-placeholder { opacity: 0; } (or visibility: hidden), using the prefix you need, in your custom CSS.
It's not possible for someone to display this otherwise though.

That's fine, but sidenote: I really think we should avoid a "you can use custom CSS if you don't like it" mentality, because we shouldn't assume the average user understands CSS (or even knows that box exists).
Can't wait for tabbed-page settings (or some equivalent)...

but sidenote: I really think we should avoid a "you can use custom CSS if you don't like it" mentality, because we shouldn't assume the average user understands CSS

I completely agree with you on this, we should make an app that's optimal and well-thought in the first place, and leave that custom CSS to those of us who have very specific and sometimes weird requirements.
In this case however, I'm with @xPaw and @YaManicKill, I think it makes for a better user experience.


Fix some typos

Fix some typos in comments

unit test fail is because the plugin-api change means the plugin-api hash in plugin-api/build.gradle needs updating
I tried to fix but I don't have perms to push to your repo @GoodDaisy
The instructions to fix --
If this is a deliberate change where you have thought through backwards compatibility,
then update "Expected" for "Calculated" in the appropriate build.gradle as the knownHash for this task.
Expected   : j6NRklFHlG35Pq/t6t/oJBrT8DbYOyruGq3cJNh4ENw=
Calculated : n2U2KHiXul6E/gxE2V5EUntrBdz6Q0qx3zLIFqPnaLU=

unit test fail is because the plugin-api change means the plugin-api hash in plugin-api/build.gradle needs updating I tried to fix but I don't have perms to push to your repo @GoodDaisy
The instructions to fix -- If this is a deliberate change where you have thought through backwards compatibility, then update "Expected" for "Calculated" in the appropriate build.gradle as the knownHash for this task. Expected : j6NRklFHlG35Pq/t6t/oJBrT8DbYOyruGq3cJNh4ENw= Calculated : n2U2KHiXul6E/gxE2V5EUntrBdz6Q0qx3zLIFqPnaLU=

PS in case the hash is modified in the meantime by other PRs, you can verify locally using gradlew plugin-api:checkAPIChanges

@macfarla I have done by gradlew plugin-api:checkAPIChanges. Thanks for your review.


vaibhavsh7

I want to contribute to this project as a part of SWOC.

Sure, Welcome, we will be sending you an invite.

An invitation has been sent. :)


Mutual Aid Wiki entries not showing up

https://mutualaid.wiki/map?kington, ON not showing up
https://mutualaid.wiki/api/group/get

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

As per #1290, I've removed the option to add Mutual Aid Wiki entries for now through the "Mutual Aid Group" option under "Add information". After we resolve the syncing issue between Mutual Aid Wiki, we can alter this code to revert my change: https://github.com/reach4help/reach4help/blob/map/map/src/components/add-information.tsx#L940-L947


Progress bar for downloads / API calls

As per our twitter talk it would be nice to have columns for downloads (speed, size) and API calls (Maybe show current call, share of calls completed). Let me know if I can help.

Closed it by accident sorry.
It's in the pipeline.

Working on it, will come with: https://github.com/FedeClaudi/Term.jl/pull/62

The next release will include a DownloadedColumn which can be used like this:
using Term.progress
using Term
import Term.progress: SeparatorColumn, ProgressColumn, DescriptionColumn, DownloadedColumn

FILESIZE = 2342341
CHUNK = 2048
nsteps = Int64(ceil(FILESIZE / CHUNK))
@info nsteps

mycols = [DescriptionColumn, SeparatorColumn, ProgressColumn, DownloadedColumn]

pbar = ProgressBar(; columns=mycols,  width=140)
job = addjob!(pbar; N=FILESIZE)

with(pbar) do
    for i in 1:nsteps
        update!(job; i=CHUNK)
        sleep(0.001)
    end
end

The docs show how to use the new progress bar API: https://fedeclaudi.github.io/Term.jl/dev/adv/progressbars/
I can ping when the new release comes out in a few days, if you'd like to test this out.

Please install the code under development with
] add https://github.com/FedeClaudi/Term.jl

to test.


Devel

Merging into master for ressources and images to be available through raw.githubusercontent.com. (Version 0.1.6 is stable enough for the master branch.)

Wow :-)


preResolveTypes lose Maybe<> typing

Huge thanks for implementing preResolveTypes, it's beautiful!
It seems to be dropping all supplemental type info (maybe, array, ...anything else?) on primitive types though (strings, numbers, etc).  This data is being retained on the wrappers around nested object types:
export type someFragment = {
  key: string;        # should be `Maybe<string>`
  anotherKey: string; # should be string[]
  finalKey: Maybe<Array<{ key: string }>>;
}

Related to #2159
Environment:

OS: OSX 10.14.5
@graphql-codegen/...: ^0.14.0
NodeJS: 10.16.0

@MarkKahn I think I fixed it, can you please try? 1.4.1-alpha-1998a660.66

LGTM!  from 742 ts errors -> 0

Fixed in 1.5.0 🎉


Replace Verify Address onclick javascript button with visualforce page for LEX compatibility

**lurch: add

Tracking W-009200

Tracking W-009201

Tracking W-009202

Tracking W-009203

Tracking W-009260

Included in beta release version 3.63 (Beta 17) and higher

Included in production release version 3.63


Resource not currently part of this pool

We recently migrated from the old cap/postgres library to the new official version. For the most part it works but there seems to be a problem with the connection pool.
We tried different database providers in the hopes that it would help but we get the same error.
Description of erroneous behaviour
From what i can tell it only happens after the app hasnt been used for a certain amount of time, i image that the connection pool closes some of the connections but im not totally sure.
Once the app gets restarted it all works again.
Here is the error message
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR [cds] - Error: Client has encountered a connection error and is not queryable
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at /home/vcap/app/node_modules/pg/lib/client.js:526:17
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at async Object.run (/home/vcap/app/node_modules/@cap-js/postgres/lib/PostgresService.js:150:24)
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at async Promise.all (index 0)
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at async PostgresService.begin (/home/vcap/app/node_modules/@cap-js/db-service/lib/common/DatabaseService.js:61:7)
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at async PostgresService._begin [as dispatch] (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-tx.js:205:3)
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at async ApplicationService.<anonymous> (/home/vcap/app/node_modules/@sap/cds/libx/_runtime/common/generic/crud.js:67:16)
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at async next (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-dispatch.js:79:17)
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at async ApplicationService.handle (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-dispatch.js:77:10)
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR at async _readCollection (/home/vcap/app/node_modules/@sap/cds/libx/_runtime/cds-services/adapter/odata-v4/handlers/read.js:249:19) {
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR id: '1847353',
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR level: 'ERROR',
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR timestamp:<PHONE_NUMBER>194
2023-09-26T14:34:12.194+0000 [APP/PROC/WEB/0] STDERR }
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR Error: Resource not currently part of this pool
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at Pool.release (/home/vcap/app/node_modules/generic-pool/lib/Pool.js:518:9)
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at Pool.release (/home/vcap/app/node_modules/@cap-js/db-service/lib/common/generic-pool.js:29:22)
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at PostgresService.release (/home/vcap/app/node_modules/@cap-js/db-service/lib/common/DatabaseService.js:105:22)
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at PostgresService.rollback (/home/vcap/app/node_modules/@cap-js/db-service/lib/common/DatabaseService.js:88:14)
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at async PostgresService.rollback (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-tx.js:103:66)
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at async ODataRequest.emit (/home/vcap/app/node_modules/@sap/cds/lib/req/context.js:52:9)
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at async ApplicationService.rollback (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-tx.js:157:7)
2023-09-26T14:34:12.195+0000 [APP/PROC/WEB/0] STDERR at async /home/vcap/app/node_modules/@sap/cds/libx/_runtime/cds-services/adapter/odata-v4/handlers/read.js:503:9

|:------------------|---------------------------------------|
| OData version     | v4                                |
| Node.js version   | v18.x.x                               |
| @sap/cds          | 7.x.x                                 |
| @cap-js/postgres | 1.x.x |

@johannes-vogel do you have an idea what might is going wrong here w.r.t. the connection pooling?

I've seen something similar and I think this https://github.com/cap-js/cds-dbs/pull/243 fixes this already.

new version is released, hence closing. Feel free to re-open if the issue persists.


Custom markers

Is it possible to add custom markers to the map?

Sure, through an addon. https://github.com/SentixDev/Pl3xMap-Marker was just recently added to the ADDONS_INTEGRATIONS.md page that should do what you want.


[Document] Usage of Dart-Define variables in gradle scripts

While creating integration tests for our Flutter application, we're facing a blocking issue:
Following the official flutter documentation for integration testing, in the section to automate the tests on Firebase Test Lab, its stated to build the app with gradle.
pushd android
# flutter build generates files in android/ for building the app
flutter build apk
./gradlew app:assembleAndroidTest
./gradlew app:assembleDebug -Ptarget=integration_test/<name>_test.dart
popd

Unfortuantely, its not stated on how to include --dart-define variables into the script so that the created APK is build with the variable defined.
According to a stackoverflow thread, I've tried setting the variable in gradle.properties, with no effect.
As nothing in this matter is documented, I assume its not possible and therefor file this issue.
If it is possible, how can we pass the dart-define to the gradle build? Adjusting the documentation here might be helpful :)
Expected results:
Integration testable APK with a dart-define variable modified in its source code.
Actual results:
The APK only has default behavior, the variable can't be modified.

Logs

[✓] Flutter (Channel stable, 2.10.3, on Microsoft Windows [Version 10.0.22000.556], locale de-DE)
    • Flutter version 2.10.3 at X:\Flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7e9793dee1 (2 weeks ago), 2022-03-02 11:23:12 -0600
    • Engine revision bd539267b4
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at X:\SDK
    • Platform android-31, build-tools 31.0.0
    • Java binary at: X:\JetBrains\apps\AndroidStudio\ch-0\211.7628.21.2111.8193401\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.11+9-b60-7590822)
    • All Android licenses accepted.

@maheshmnj thank you for your triage! as per your investigation it looks like you think its already implemented, and just not documented.
Could you share the way to include the dart-define in gradle with us?

Could you share the way to include the dart-define in gradle with us?

@Sese-Schneider, I am not sure about it, nor I could find a way to use the dart define constants in Gradle scripts, Lets wait for the secondary triage to take a look at it, They may have a better understanding of it.
cc: @blasten

@Sese-Schneider Did you find a way to do it?
I need to send data on basis of my Android grade flavor to main.dart to set appropriate .env file

@onkarmonks we also had this issue in the past, but failed to find a way to do this.
What we do is to supply --flavor  and a --dart-define in the flutter build step.
However, this question is about injecting the --dart-define in Androids gradlew assembleDebug step.

I found a solution to this.  I inspected the verbose output of flutter build and found that the --dart-define flags get base64 encoded, comma-separated, and passed to a Gradle via a flag called -Pdart-defines. (Note the s at the end of this flag, since it contains all the defines).
So for example, the following dart defines passed to Flutter:
--dart-define myvar=123 --dart-define anothervar=test

turn into the following flag passed to Gradle:
-Pdart-defines bXl2YXI9MTIz,YW5vdGhlcnZhcj10ZXN0

since, myvar=123 is bXl2YXI9MTIz in base64 and anothervar=test is YW5vdGhlcnZhcj10ZXN0 in base64.  Simply pass this flag to your Gradle command, e.g.:
gradlew -Pdart-defines bXl2YXI9MTIz,YW5vdGhlcnZhcj10ZXN0 assembleDebug

This solved the problem for me.

@roblframpton thank you very much, this solved our issues 🚀
/cc @onkarmonks
@maheshmnj given this is documented nowhere, I think the labels are correct as of missing documentation 👍🏼

For anyone else struggling to make the solution provided by @roblframpton , remember to base64 encode just the key=value portion of the --dart-define. This is probably obvious to everyone else but me, but I was encoding "--dart-define=key=value". That definitely does not work! @roblframpton explained it perfectly, just encode the key=value.

@roblframpton & @dustin-graham guys, inside my integration tests I have TEST_ENV var with the default value "develop". When I want to change it to "stage" for the local run via flutter driver - I'm using this:
flutter drive --driver=test_driver/integration_test.dart --target=integration_test/tests/messaging_test.dart --dart-define=TEST_ENV=staging and it is working.
But I need to figure out how to pass it during my Jenkins job, which builds and initiates test run in Firebase Test Lab. Here is my steps:

flutter build apk --debug
./gradlew app:assembleAndroidTest
./gradlew app:assembleDebug -Ptarget="pwd"/../integration_test/smoke_test.dart
I tried the approach, mentioned by you in points 2 & 3 (base64 & usual) but it still uses the default value "develop". TIA!

Hey @ivan-horchakov , I have a similar use case and solved it today :) like this:
./gradlew assembleDebug --info -Ptarget=`pwd`/../integration_test/app_test.dart -Pdart-defines="{base64String}"

Where {base64String} is the encoded key=value pair, in your case "base64("TEST_ENV=staging")"
or directly:
./gradlew assembleDebug --info -Ptarget=`pwd`/../integration_test/app_test.dart -Pdart-defines="VEVTVF9FTlY9c3RhZ2luZw=="

Thanks, @krishnakumarcn - you've made my day!

I'm having a problem with passing dart defines to the app:connectedDebugAndroidTest task, which is needed to run integration tests natively on Android.
./gradlew app:connectedDevDebugAndroidTest \
  -Ptarget=$(pwd)/../integration_test/hsv_test.dart \
  -Pdart-defines="Q1RTX0RJU0FCTEVfTUFQX1BSRUxPQURJTkc9dHJ1ZQo="

but it's spitting out really ugly error message:

error message
> Task :app:compileFlutterBuildDevDebug
-DCTS_DISABLE_MAP_PRELOADING=true%0A: Error: Error when reading '-DCTS_DISABLE_MAP_PRELOADING=true%0A': No such file or directory

> Task :app:compileFlutterBuildDevDebug FAILED

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* Where:
Script '/Users/bartek/fvm/versions/stable/packages/flutter_tools/gradle/flutter.gradle' line: 1159

* What went wrong:
Execution failed for task ':app:compileFlutterBuildDevDebug'.
> Process 'command '/Users/bartek/fvm/versions/stable/bin/flutter'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 7s
1 actionable task: 1 executed


[1.10.2]Crash on server

Hello, can you help me please ? :)
http://pastebin.com/EZ9FDpdX

http://pastebin.com/VQNxm4BD

I'm going to need more info...if you still know it that is. What configurations where you using..what blocks...what dimensions...what type of power etc.


Add slow sync log rolling test in TestAsyncLogRolling.

Detail: https://issues.apache.org/jira/browse/HBASE-28190

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 53s
the patch passed

+1 :green_heart:
compile
0m 46s
the patch passed

+1 :green_heart:
javac
0m 46s
the patch passed

+1 :green_heart:
shadedjars
5m 33s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
216m 23s
hbase-server in the patch passed.

240m  6s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5507/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5507

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f0c06875441f 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 027a119bcf

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5507/1/testReport/

Max. process+thread count
5113 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5507/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 12s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 31s
master passed

+1 :green_heart:
compile
0m 39s
master passed

+1 :green_heart:
shadedjars
4m 49s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 25s
master passed

-0 :warning:
patch
5m 23s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 21s
the patch passed

+1 :green_heart:
compile
0m 41s
the patch passed

+1 :green_heart:
javac
0m 41s
the patch passed

+1 :green_heart:
shadedjars
4m 49s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
224m 22s
hbase-server in the patch passed.

245m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5507/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5507

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 14d8db3d07be 5.4.0-153-generic #170-Ubuntu SMP Fri Jun 16 13:43:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 027a119bcf

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5507/1/testReport/

Max. process+thread count
4711 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5507/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

Gentle ping @Apache9  If u have time, could u help review this? Thanks!

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 49s
Docker mode activated.

TestZooKeeper is known to be flaky sometimes in pre commit.
TestRollbackSCP is tracked by #5563
Let me merge.


Can't edit or make changes to features

![2020-07-30 11 19 35](https://user-images.githubusercontent.com/14807319/88941147-ad9d2980-d256-11ea-802b-c19a2f881a1a.gif)
Severity
Configuration becomes unusable unless you write everything correctly the first time around
Problem
Once you create a feature, you can't edit or remove it
Replication steps

Configure a new instance of moufette on heroku
Add a feature
Try clicking edit feature or more
Nothing happens

Oh, and congrats on HN frontpage :)

Thanks @areibman
I still have a lot to improve :D


New Slack Link?

The slack link in the readme appears to be dead.  Is there a new one?

I too would like to join, working on decoding the RS485 interface.

valid 30 days: https://join.slack.com/t/robotdogs/shared_invite/zt-2s61ukbd3-axxxt1wbirUMrq9I~IobvA

I too would like to join

有效期 30 天：https ://join.slack.com/t/robotdogs/shared_invite/zt-2s61ukbd3-axxxt1wbirUMrq9I~IobvA

New Link... https://join.slack.com/t/robotdogs/shared_invite/zt-2v6tvhy9y-_LVESn4QB2HV3HAnpkYHTg


Fix imaplib 'IMAP' module reference to 'IMAP4'

On IMAP login error: 'imaplib' has no 'IMAP' member; maybe 'IMAP4'

Codecov Report

Merging #604 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #604   +/-   ##
=======================================
  Coverage   62.58%   62.58%
=======================================
  Files          38       38
  Lines        3547     3547
  Branches      557      557
=======================================
  Hits         2220     2220
  Misses       1174     1174
  Partials      153      153

Impacted Files
Coverage Δ

helpdesk/management/commands/get_email.py
70.05% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Help - Types Backward

When I type in Stackedit, the type appears like this...?drawkcab gnipyt siht si yhW
Of course it should read, "Why is this typing backward?"
What am I doing wrong?
Thanks.

I have the same problem. I solved it using Firefox (or Palemoon)

Thanks alot. Any way to make it work with Chrome?
On Thu, Jul 2, 2015 at 3:33 PM, chicchera<EMAIL_ADDRESS>wrote:

I have the same problem. I solved it using Firefox (or Palemoon)
—
Reply to this email directly or view it on GitHub.

--
Bro. Kyle
Sign Up for Blog HERE http://eepurl.com/RhsK1

Did you change the "Right to left" setting?

I did: nothing happens.

Yes. I even went back and forth changing it, thinking that may make it
work. Thanks.
On Thu, Jul 2, 2015 at 4:23 PM, chicchera<EMAIL_ADDRESS>wrote:

I did: nothing happens.
—
Reply to this email directly or view it on GitHub
https://github.com/benweet/stackedit/issues/835#issuecomment-118172138.

--
Bro. Kyle
Sign Up for Blog HERE http://eepurl.com/RhsK1

Oh, by the way, it didn't. I have been using Stackedit for a year or two
jut fine, on this same computer. It just started this yesterday.
On Thu, Jul 2, 2015 at 4:30 PM, Kyle Morris<EMAIL_ADDRESS>wrote:

Yes. I even went back and forth changing it, thinking that may make it
work. Thanks.
On Thu, Jul 2, 2015 at 4:23 PM, chicchera<EMAIL_ADDRESS>wrote:

I did: nothing happens.
—
Reply to this email directly or view it on GitHub
https://github.com/benweet/stackedit/issues/835#issuecomment-118172138.

--
Bro. Kyle
Sign Up for Blog HERE http://eepurl.com/RhsK1

--
Bro. Kyle
Sign Up for Blog HERE http://eepurl.com/RhsK1

Oh, I am so glad: I started using it yesterday. It worked for a short while and then stopped.

This has happened from time to time. As much as it pains me to say it (my Tech Ethics professor is probably frowning), the problem has always self-corrected when the browser was restarted. Also certain browser extensions interact poorly with stackedit.

Thank you.
On Fri, Jul 31, 2015 at 9:48 AM, Marcus Hallett<EMAIL_ADDRESS>wrote:

[image: Boxbe] https://www.boxbe.com/overview Marcus Hallett (
<EMAIL_ADDRESS>is not on your Guest List
https://www.boxbe.com/approved-list?tc_serial=22147953539&tc_rand=844979384&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&token=To%2FwmenbJPZiauWjrWqQBxVEA73ZhaExJDIfgwCSIOL%2Fp5dvJN6o9VtK9q%2FJcuWC&key=O9vqrQTCu6Zb0bP3VmeK495WXE5dOHkKK6TdCOE8dxE%3D
| Approve sender
https://www.boxbe.com/anno?tc_serial=22147953539&tc_rand=844979384&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&token=To%2FwmenbJPZiauWjrWqQBxVEA73ZhaExJDIfgwCSIOL%2Fp5dvJN6o9VtK9q%2FJcuWC&key=O9vqrQTCu6Zb0bP3VmeK495WXE5dOHkKK6TdCOE8dxE%3D
| Approve domain
https://www.boxbe.com/anno?tc_serial=22147953539&tc_rand=844979384&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&dom&token=To%2FwmenbJPZiauWjrWqQBxVEA73ZhaExJDIfgwCSIOL%2Fp5dvJN6o9VtK9q%2FJcuWC&key=O9vqrQTCu6Zb0bP3VmeK495WXE5dOHkKK6TdCOE8dxE%3D
This has happened from time to time. As much as it pains me to say it (my
Tech Ethics professor is probably frowning), the problem has always
self-corrected when the browser was restarted. Also certain browser
extensions interact poorly with stackedit.
—
Reply to this email directly or view it on GitHub
https://github.com/benweet/stackedit/issues/835#issuecomment-126713501.

--
Bro. Kyle
Sign Up for Blog HERE http://eepurl.com/RhsK1

Well, thanks. I've been a programmer for over 40 years and completely empathize...


Consider alerts and metrics for dex-operator

Let's improve observability for the dex-operator
metrics

[x] app info with details about connector and key expiry
[ ] ?

alerts

...

in central grafana

I think  we are good for now


Deep nesting with a variable causes build fail

This ticket was initially filed at: https://github.com/webpack-contrib/sass-loader/issues/502
npm: 5.3.0
node 8.4.0
process.versions

http_parser: '2.7.0',
node: '8.4.0',
v8: '6.0.286.52',
uv: '1.13.1',
zlib: '1.2.11',
ares: '1.10.1-DEV',
modules: '57',
nghttp2: '1.22.0',
openssl: '1.0.2l',
icu: '59.1',
unicode: '9.0',
cldr: '31.0.1',
tz: '2017b'

process.platform linux
process.arch x64
sass-loader 6.0.6
Using sass-loader I ran into an issue where builds would fail when using variables that were deeply nested, though, I'm not sure if this is specifically a sass-loader or libsass issue.
I pulled the code and modified https://github.com/webpack-contrib/sass-loader/blob/master/lib/loader.js#L15 to use the sass.renderSync function which appears to remedy the issue.
While this is a compilation error, I'm filing here since sass.renderSync does appear to work.
The minimal amount of breaking code I've come up with is the following:
fails
$testing: #ff00ff;
body{
  div{
    div{
      div{
        div{
          div{
            div{
              div{
                div{
                  div{
                    div{
                      div{
                        &.a-class{
                          span{
                            color: $testing;
                          }
                        }
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

Yeah... lots of nesting... but when a variable is used at that level webpack fails to build.
However, if you comment out one of the divs, OR, if you use the color #ff00ff directly the build does not fail.
works
$testing: #ff00ff;
body{
  div{
    div{
      div{
        div{
          div{
            div{
              div{
                div{
                  div{
                    div{
                      // div{
                        &.a-class{
                          span{
                            color: $testing;
                          }
                        }
                      // }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

works
$testing: #ff00ff;
body{
  div{
    div{
      div{
        div{
          div{
            div{
              div{
                div{
                  div{
                    div{
                      div{
                        &.a-class{
                          span{
                            color: #ff00ff;
                          }
                        }
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

So, I bumped the Docker file to use node 8.7.0 and it appears to have fixed this issue, so I'll close since it appears to be specific to node 8.4.0 at this moment.


Update to make plugin work with GoCD 17.1 and above

Using the plugin shim to upgrade this plugin, so that it works with 17.1. Without this change, this plugin will stop working from GoCD 17.1 onwards.

I created a Pivotal Web Services account and ran cf push on a sample application and the plugin recognized it. However, even after making a small change to the application and pushing it again, the old and new plugins did not recognize the change and build again. Even looking at the DB, not a lot of the information presumably returned by the cloud foundry client is stored. I put this down to me not understanding how cf works properly, or some missing information. However, it looks like the old plugin and the new look like they are functionally equivalent. So, if you're thinking of accepting this, you should test it with some real repo. Thank you!
This is the configuration I used:
<repository id="50c63334-ca2a-449d-abd9-b75f4ca51f26" name="cf">
  <pluginConfiguration id="CloudFoundry" version="1" />
  <configuration>
    <property>
      <key>REPO_URL</key>
      <value>https://api.run.pivotal.io</value>
    </property>
    <property>
      <key>USERNAME</key>
<EMAIL_ADDRESS>    </property>
    <property>
      <key>PASSWORD</key>
      <encryptedValue>94M1aW0/yFY3Z8bfQe0yIQ==</encryptedValue>
    </property>
  </configuration>
  <packages>
    <package id="a480f30e-dc98-4ce1-b53f-a8085c75621a" name="MyName">
      <configuration>
        <property>
          <key>SPACE</key>
          <value>development</value>
        </property>
        <property>
          <key>APP_NAME</key>
          <value>cf-spring</value>
        </property>
        <property>
          <key>ORG_NAME</key>
          <value>testorg123</value>
        </property>
      </configuration>
    </package>
  </packages>
</repository>

Hi.
I was wondering if someone would be getting in touch about this.
Unfortunately I'm not working with a Cloud Foundry environment these days so I don't have a setup ready to try this out.
I'll see if I can track down a way to test this out.  Given that it has been quite a while since this was first set up I expect there will be a later version of the Cloud Foundry client.

@Sounie: Thank you! That would be good. If I can help in some way, let me know.

I've installed PCF Dev to try to check things out locally ( https://github.com/pivotal-cf/pcfdev ).
I have also grabbed your branch to try building and deploying it into the latest released GoCD - 16.12.0.
Running out of hours today.  I might have some time to get back into it after work tomorrow.
My preference would be to avoid the shim approach if possible, but that might be an okay starting point.

@Sounie: Thanks. What was strange to me, when I set it up was that the plugin did not seem to print out any environment variables (apart from the usual ones) and the label was set to an empty value. The DB (modifications table) also had an empty JSON. So, I'm not sure the latest revision call returned anything. I don't know enough about the plugin to know what is expected of it.

My preference would be to avoid the shim approach if possible, but that might be an okay starting point.

And mine. :) But, since it is close to 17.1, we thought of this to make it easy to port a plugin over for now.

The Cloud Foundry Client library has moved up by a major version, so it may take me a while to get my head around that new API.
I'm starting this process by introducing a new test for interacting with a local PCF Dev environment with default credentials.  This allows for checking the changes in isolation (i.e. without having to build the plugin and deploy it into GoCD).

Ok. If you'd prefer to not use the shim, since you need to redo bigger parts of it, that's ok as well. If I can help, let me know. Thanks!

I've decided to upgrade to v2 of the CloudFoundry API (the latest client lib supports v2 and v3, but the cfdev setup appears to be on v2).
I have created a poorly numbered pre-release version:
https://github.com/Sounie/springer-gocd-cloudfoundry-plugin/releases/tag/3.0.0
Pretty sure some logic in there requires further tweaking to match the desired functionality.  Hopefully I will get some time to find the obvious bug soon.

Ok. Thank you! I'll mention this in the release notes.

Shortly after posting I remembered a key aspect of how the plugin works.  It expects the application name to include a version integer value as suffix.
This probably also explains the missing label that you mentioned in your earlier comment.

@arvindsv Any idea why the GoCD 17.1 release notes mention this plugin will stop working from 17.2 onwards?

@Sounie This PR didn't make it to 17.1. It'll be merged soon, for 17.2.

Ok, but isn't the use of the shim supposed to enable the plugin to continue to work?

Yes, it should work in 17.1, with the shim. Are you saying it's not working??
Even with the support for API plugins not yet removed in 17.1, the shim and your new plugin should continue to work. It just so happens that the old plugin would also work for 17.1, but should stop working from 17.2 onwards, once that PR is merged.
Should I try and rephrase that?

Oh. I see. Sorry! I'll fix the release notes. :(

It should be removed from the release notes in about 10 or 15 minutes (once the edge server caches get refreshed).

Thanks.  It's highlighted that I should update my docs too - technically older versions of my plugin will stop working.


[PE-D][Tester D] Functionality Bug: editCom allows for infinite marks

Marks field does not catch inputs when numbers exceeding MAX_INT is typed in the editCom command
Perhaps the application should throw an error message since infinite marks are not possiible

Labels: type.FunctionalityBug severity.Medium
original: lambraydon/ped#3

Limited editComp to maximum marks, which is at most 10000.


Remove bevy_utils::default() and prefer <_>::default()

Objective
Contributes to #11478
Solution
This has been attempted in a different manner before, but I want to see how this version is liked since it uses a more brief syntax than the previous attempt. I'm also interested to see if minds have changed in the last couple months. Close if unwanted.
Testing
CI
Migration Guide
bevy_utils::prelude and bevy_utils::default are removed. Use <_>::default() instead.

I'm pretty sure Cart added default to reduce the noise in Bevy code, especially in bundles. This PR seems to add more noise (and subjectively more than just using Default::default). It also means more typing since you can't just import default once, but now need to add <_>:: to every call site


Suggestion for a possible enhancement to entity framework documentation page

I'm new to Finbuckle, and also relatively new to ASP.NET Core and dependency injection, so this suggestion may not be helpful. Please let me know!
I am working on implementing multitenant behavior in a web site that uses separate databases for tenant isolation. In the current docs, it is suggested to use the following constructor on the sample EF context class, MyAppDbContext.
public MyAppDbContext(IMultiTenantContextAccessor<AppTenantInfo> multiTenantContextAccessor)
{
   // get the current tenant info at the time of construction
   TenantInfo = multiTenantContextAccessor.tenantInfo;
}

When I tried the sample approach, the dependency injection framework complained about ambiguous constructors. It didn't like that I had this constructor on my class.
public MyAppDbContext(DbContextOptions<MyAppDbContext> options)
    : base(options)
{ }

As I understand EF Core, this is a pretty standard constructor. In my project, the EF Context class is used in multiple projects, and these other projects are using the DbContextOptions constructor.
The solution I found for this situation was to handle the multi-tenant configuration for the connection string while building the services. Between the builder.Services.AddMultiTenant<> line and the app.UseMultiTenant() line, the DbContext is configured like this:
builder.Services.AddDbContext<MyAppDbContext>((serviceProvider, dbContextBuilder)=>
{
    var tenantAccessor = serviceProvider.GetRequiredService<IMultiTenantContextAccessor<AppTenantInfo>>();
    dbContextBuilder.UseSqlServer(
        tenantAccessor.MultiTenantContext.TenantInfo.ConnectionString);
});

I wonder if this is even a good way of handling this situation, given my newbie status to these concepts. If it is a good solution, would this information be useful to be added to the documentation as an alternative to using the IMultiTenantContextAccessor constructor and the OnConfiguring method?

I like this idea. Please feel free to submit a PR with the change or I will add it with the .net 9 release.
Another option is to use:
public MyAppDbContext(IMultiTenantContextAccessor<AppTenantInfo> multiTenantContentAccessor, DbContextOptions<MyAppDbContext> options)
    : base(multiTenantContentAccessor, options)
{ }


Compiler Question: why invert token.Less to token.Greater

in compiler.go: https://github.com/d5/tengo/blob/6fc805399207b1afb7c59aab21dcab07c59b5df7/compiler.go#L144-L153
It seems that < is translated to > when compiling tengo scripts. I wonder why. This makes BinaryOp() in user defined types to never execute LessEq and Less branch.
For example I have a custom defined type Number, and

Number(14)>12 works because it would invoke Number.BinaryOp that I implemented
Number(12)<14 throws a runtime error, because compiler inverts this to 14>Number(12) in compilation process, and it would invoke Int.BinaryOp and fail.

Are there any special design considerations behind this? Can I simply send a PR to remove this piece of logic in compiler?

I have opened a pull request for that:
https://github.com/d5/tengo/pull/391


Add Send SMS With URL

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[ ] I have joined the ZITADEL chat

Describe your problem
Example: http://sms-proivider/get?to=number&text=text here
Describe your ideal solution
Add Send SMS Feature Over URL
Version
latest
Environment
Self-hosted
Additional Context
No response

Hei @tahaghafuri
Can you elaborate a little more on your use case, and what you need.
Why is that a feature you are looking for?

I mean in the following example:
Sending SMS via GET method:
Address: https://example.com/SendMessageWithUrl.ashx
Indicators :
Username: UserName, for example: test123
Password: Password, for example: 123456 / SMS system password
Dedicated number: PhoneNumber, for example:<PHONE_NUMBER>
Message text: MessageBody, for example: SMS sending test
Message receiver number: RecNumber, for example:<PHONE_NUMBER>1
Sending type: Smsclass must be 1
Complete example of the system:
https://example-sms-provider.com/SendMessageWithUrl.ashx?Username=test123&Password=****&PhoneNumber=5000221030&MessageBody=test&RecNumber=09116665601&Smsclass=1
Just copy the above address in the section using the address of the system bar and register and execute your choices.
important points:
If you are identified after sending code 8. This can mean that it does not enable the possibility of using the web service and url for you. To activate this possibility for free, register an activation request in the support section with a ticket or contact the company.
In the image where sending is used with a number greater than 200, it means that your SMS was sent without sending. and otherwise an error has been encountered.

This feature is also available in wso2 identity server, which makes it not limited to one SMS provider

[...] as there is no "standard" SMS protocol like SMTP we use for email [...]
[...] We would need to implement code for each provider specifically [...]

I don't want to talk for OP but this is exactly the anti-goal of the request.
Basically the desire is to be able to specify an HTTP request that shall be send when ever internally a SMS (and/or email/notification etc.) is triggered.
Established providers almost always offer an HTTP API (e.g. SendGrid, Twilio, SMSAPI) and if ZITADEL would allow to send an HTTP request and use variables like {{recipient}}, {{message}} etc. most providers can easily be covered.
I'd argue that this makes sense even beside SMTP for emailing. For example we use SendGrid's HTTP API to send all our emails so we can use its dynamic templates feature.
Some example APIs:

https://www.twilio.com/docs/messaging/api/message-resource#create-a-message-resource
https://docs.sendgrid.com/api-reference/mail-send/mail-send
https://www.smsapi.com/docs/#2-single-sms

[...] which will allow calling webhooks at foreign APIs. This would be a good usecase for custom notification channels [...]

Yes!

@eliobischof you have more knowledge on the notification system in zitadel, I will pass this issue over to you.

I see some benefit if we added the possibility to add an SMS provider (maybe also an Email provider) for arbitrary webhook calls instead of having only Twilio as a requirement.
We already have a webhook channel implemented for milestones. I imagine it gives users much flexibility for a relatively low implementation effort.

@eliobischof For us it would be enough if we could override the SMS endpoint URL and we can replicate the Twilio API ourselves and send the data where we'd like.
This feels like it could be very little effort to change and give most of the benefits to those that really need it?

We have just implemented http as sms provider so you can choose where to send the notification and implement something yourself. https://github.com/zitadel/zitadel/issues/8270
Can we close the issue here?

@hifabienne It looks like exactly what we need.
Did a quick search in the documentation but couldn't find any API spec/schema for what the custom SMS service will receive, do you know where I can find that?
Other than that this issue can be closed based on our needs at least

Hi @karatekaneen
The documentation is in review and will be merged soon.
If you already want to have a look at it you can see it here: https://github.com/zitadel/zitadel/pull/8626
In that case I will close this issue for now, feel free to reopen if you still miss something