Fixed ordering when using FisherBarFigure

Fixes #45. Also added tests for it.

Codecov Report

Merging #46 (0e58953) into master (465816a) will increase coverage by 0.08%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master      #46      +/-   ##
==========================================
+ Coverage   99.24%   99.33%   +0.08%
==========================================
  Files          12       12
  Lines        2378     2394      +16
==========================================
+ Hits         2360     2378      +18
+ Misses         18       16       -2

Impacted Files
Coverage Δ

fitk/graphics.py
98.08% <100.00%> (+0.35%)
:arrow_up:

tests/test_graphics.py
100.00% <100.00%> (ø)

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


Support ForceAuthn attribute of AuthnRequest

Our organization has a need to use the ForceAuthn attribute along with Okta's support for it for some of our applications, but it looks like this support is missing from OneLogin_Saml2_AuthnRequest.
Any chance this can be added?
ref: https://spaces.internet2.edu/display/InCFederation/2013/12/08/ForceAuthn+or+Not
$ grep -rn ForceAuthn .
./lib/Saml2/schemas/saml-schema-protocol-2.0.xsd:163:                <attribute name="ForceAuthn" type="boolean" use="optional"/>
./tests/data/requests/authn_request.xml:1:<samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="_ONELOGIN103428909abec424fa58327f79474984" Version="2.0" IssueInstant="2014-11-13T11:39:34Z" ForceAuthn="false" IsPassive="false" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" AssertionConsumerServiceURL="http://example.com/acs">

Hi  mattzuba,
I decided not supporting the ForceAuth parameter since no many IdPs handle it because I don't don't want to add more parameters to the login / AuthNRequest constructor.   I wanted to keep the toolkit simple.
I will review your case.

Thanks, we'd appreciate a review of it.  I could work around it by extending the OneLogin classes and overloading the login method if needed since I've already created a Laravel Service Provider for it, but if this could be an undocumented feature, that'd be awesome!

I implemented your required feature.

Fantastic!  You're awesome!


Fix app bar title overflow with centerTitle:true

Simplified AppBar title layout. The title only gets the horizontal space between the app bar's leading widget and the (trailing) action widgets.
Also: AppBar.copyWith() wasn't copying the centerTitle property.
Fixes: #5212

Thanks!

LGTM.

Does this mean that title won't be centered in the full app bar if there are a different number (or differrently sized) icons on the left and right?

I agree. Will write a custom multi-child layout.

LGTM modulo comment issue


Update version to 1.8.0-dev, update g word to 'generous'

Yeah, whomever changed it to 5.0.0-dev in build.yaml forgot to update BUILD.
On Mon, Oct 2, 2017 at 5:37 PM, Michael Lumish<EMAIL_ADDRESS>wrote:

@murgatroid99 commented on this pull request.
In BUILD https://github.com/grpc/grpc/pull/12792#discussion_r142289996:

@@ -34,11 +34,11 @@ load(
)

This should be updated along with build.yaml
-g_stands_for = "gambit"
+g_stands_for = "generous"
core_version = "4.0.0-dev"
I didn't change it in either file, and yet they have different numbers.
Are you sure 5.0.0-dev is the correct value?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/12792#discussion_r142289996, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG8bpph9MDCFTqjUJqQYVX5SWZ4IPiI0ks5soYHfgaJpZM4Prb0i
.

[trickle] No significant performance differences

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[microbenchmarks] No significant performance differences


fix(search): fix mapping builder bug

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

There is a failure here that is still not fixed, investigating (not the lint errror)


[improve][broker] Introduce resourcegroup rate limit on topic and geo

Motivation

Modifications

Add dispatch rate limit on topic and geo
Add resource group bindings to the topic

Documentation

[ ] doc
[x] doc-required
[ ] doc-not-needed
[ ] doc-complete

Ping @liudezhi2098


Spam Domain Submission

Duplicate Domains

[X] Yes, I checked that the domain is not currently in the list
[X] I read the wiki explaining each different categories and examples before submitting

(Required) Spam Comment Direct Link
https://www.youtube.com/watch?v=6l3Q9DjbQ7A&lc=UgzNxEsRmNH_9N-cktd4AaABAg
https://www.youtube.com/watch?v=6l3Q9DjbQ7A&lc=UgwSb9S-Tj3qXdfmgDl4AaABAg
(Optional) Screenshot of comments using the domain

(Required) List of the spam domains
von.monster
savilaa.uno

Deals with the new comments mentioned in https://github.com/ThioJoe/YT-Spammer-Purge/issues/868#issuecomment-1162088672


AuthServerAllowlist policy is set and can not be removed

Issue:
The chrome policy AuthServerAllowlist policy is set to "*", and while there might be a reason for it (allowing proxy-authentification without being on the intranet), it also sets ungoogled-chromium to "managed by your organisation", disabling settings (for example secure DNS configuration).
Deleting the policy json file in /etc/opt/chrome/policies/ does not disable the policy and reload policies in chrome://policy/ also does not reload the policies in /etc/opt/chrome/policies
Expected behaviour:

Being able to remove this policy and get rid of "managed by your organisation" to allow setting secure DNS configuration.
Manually deleting the policy in /etc/opt/chrome/policies should remove the policy and the "Reload policies" button in chrome://policy should work.

Reproduce:

Install ungoogled-chromium in Fedora using this package
The policy is enabled by default (I did not find any reference that this was caused by packaging)

Could it be ungoogled-chromium-fedora issue?

Found out that is a chromium issue as well. It happens upstream already. This can be closed.

FYI: https://src.fedoraproject.org/rpms/fedora-chromium-config/c/2a4303ccd7577c1878fa62b6e81019bf984734ae?branch=rawhide
The AuthServerAllowlist policy is no longer set for Fedora.


Fix: may cause UAF problem in get_size_from_segDBs

fix #NO_ISSUE_NUMBER

Change logs
nope
Why are the changes needed?
In function get_size_from_segDBs, If the cdb result returned from segment is not as expected. Then we will clear up the cdb call the ereport. But in this cause the value in cdb result have been freed. We should keep a cdb result before cleanup it.
Does this PR introduce any user-facing change?
nope
How was this patch tested?
nope
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:

[ ] Make sure your Pull Request has a clear title and commit message. You can take git-commit template as a reference.
[ ] Sign the Contributor License Agreement as prompted for your first-time contribution(One-time setup).
[ ] Learn the coding contribution guide, including our code conventions, workflow and more.
[ ] List your communication in the GitHub Issues or Discussions (if has or needed).
[ ] Document changes.
[ ] Add tests for the change
[ ] Pass make installcheck
[ ] Pass make -C src/test installcheck-cbdb-parallel
[ ] Feel free to request cloudberrydb/dev team for review and approval when your PR is ready🥳

LGTM.

Pushed, thanks.


how to compile the project

I downloaded the project, but it doesn't compile. how can I configure it to solve?

I get the answer.

I get the answer.

yes, README section D


configuration-reload-test: wait for the new worker to get ready

After sending a SIGHUP, wait for the new worker process with the
new configuration to handle further requests, or else the tests
running after that might get confused when the new worker becomes
active with fresh shared mem statistics and shared mem cache.

This looks great!  I think this might fix the intermittent cache_flush test error we've seen.
(Specifically, we'd see the cache flush properly, but the stat wouldn't get bumped.  That could be explained by the fresh stats coming online at exactly the wrong time, so that the flush happened on the old stats and the query to the stats url happened on the new stats.  This was especially likely because that test has some sleeps.)

@jeffkaufman "I think this might fix the intermittent cache_flush test error we've seen."
That sounds like something this could very well fix. I've only seen that flake one or two times in the past weeks, so it's hard to be sure.

LGTM!

@jeffkaufman Ugh. With this merged, the sanity check for error.log starts failing when running the tests in a loop under valgrind. Inspecting error.log, it looks like somehow the old worker process isn't able to finish up all queued requests in the timeout period. However, it does not look like that happens because it's short on time. Some requests from ab just seem to stall, so I think I need to look at if there's an edge case that I missed.


Firestore integer simple fields

Closes #4320
Diff base is #4851

Is the diffbase necessary?

not necessary, but create_if_missing should be removed anyway.

If it can be done without it, please do. You can graft your commit onto master by using git rebase -i  master and dropping the unrelated commits.

that was bad, wait a minute


HybrisControllerHtmlUsageCheck Run on all the classes

HybrisControllerHtmlUsageCheck should check if the class under check is a controller on not.

fixed #13


Static site hosting and location functionality

I made some modifications to the proxy hosts flow which adds a static toggle which switches between proxying and static root/alias/try_files based locations.
I've modified the base proxy_hosts form and the locations one so you can mix and match between proxy hosts and locations and static hosts and locations.
There's a little bug because I'm not so experienced with Backbone marionette and I used the static toggle to change the required fields on the form from forward_host and forward_ip to index_file and root_dir. And to rerender the form to show that update I ran a this.render call which seems to break the location items rendering so you have to save the root config for a proxy host before clicking edit again to do the locations.
Here's an album of visual changes
https://imgur.com/a/qgxzYFu
You can see the template changes in _location.conf _listen.conf and proxy_host.conf
I had some trouble with the booleans either being 0 or 1, because in the listen forms the model values are used but in the proxy_host form the actual HTML form values are used which is integer on the checkbox's.
I think this pull request will open up nginx proxy manager to a lot more people, as SSL static hosting is one of the most sought after things on the web.
Needs a bit of polishing but that's why I pulled it into the develop branch.

Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-558

Thanks for doing all this work! I agree backbone and marionette is dated and won't be my choice for version 3.
Where this PR falls short is that a Proxy host should not deliver static content. It would be better to separate this static stuff into a new Host type. Hopefully this would avoid confusion and would definitely make validation rules nicer.
If you want to, I can create a new branch in this main project for this static feature, merge this PR to it and build on it from there?

Thanks for doing all this work! I agree backbone and marionette is dated and won't be my choice for version 3.
Where this PR falls short is that a Proxy host should not deliver static content. It would be better to separate this static stuff into a new Host type. Hopefully this would avoid confusion and would definitely make validation rules nicer.
If you want to, I can create a new branch in this main project for this static feature, merge this PR to it and build on it from there?

True true.
I don't know how much time I'll have to do more work on it, I opted to just do my nginx stuff manually since it was only for a couple of simple projects.
Yes a frontend framework like quasar/vue or react would help I think, the backend is bloody solid though good job on it and easy to develop and debug :)
If I get time I'll split the static logic into a separate host, I was just being lazy to be honest haha. But the foundation is now there :) And I know what libraries are used for templating and etc.. so can contribute quicker now :)
Sure if you make the branch for static that'd be awesome :)

I'm working on this in my own fork to make this a separate option as suggested by @jc21


On Android phones, the bottom of the text in the long-press prompt box is cropped a little

As is shown in：

Hello @152dyn ,
Could you please post the output of flutter doctor -v and a minimal reproducible code sample
Thank you!

@152dyn
Please provide above requested details that shows the issue.
Thanks.

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.22.1, on Mac OS X 10.15.6 19G2021, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0)
[✓] Android Studio (version 3.6)
[✓] Connected device (2 available)
• No issues found!

This scenario occurs in TextField, when long pressing the prompt box
The prompt box is not my custom
In Android, this is going to happen to all textfields in my app

@darshankawar @sidrao2006
I just found out that only when it's set to Chinese will it be cropped
This is what I set up for the MaterialApp：
         MaterialApp(
              title: 'Demo',
              theme: themeConfig,
              navigatorObservers: [
                routeObserver,
              ],
              onGenerateRoute: widget._router.getRoute,
              localizationsDelegates: [
                GlobalMaterialLocalizations.delegate,
                GlobalWidgetsLocalizations.delegate,
                GlobalCupertinoLocalizations.delegate,
                DefaultCupertinoLocalizations.delegate
              ],
              supportedLocales: [
                const Locale('zh', 'CH'),
              ],
              home: SplashPage()
          )

@binqiiyuenan the glyph's cropped or is the box cropped?


Error thrown when provided config with scenarioLevelReporter: true

Environment (please complete the following information):

Node.js version: [12.16.3]
Yarn - 1.22.4
webdriver.io version: [6.1.22]
@wdio/cucumber-framework version: [6.1.22]
wdio-cucumberjs-json-reporter version: [2.0.2]

Config of webdriver.io and the reporter
cucumberOpts: {
// <string[]> (file/dir) require files before executing features
require: [
"./src/step_definitions/.steps.js",
"./src/support/hooks/.hooks.js",
],
//  show full backtrace for errors
backtrace: false,
// <string[]> ("extension:module") require files with the given EXTENSION after requiring MODULE (repeatable)
requireModule: ["@babel/register"],
//  invoke formatters without executing steps
dryRun: false,
//  abort the run on first failure
failFast: false,
// <string[]> (type[:path]) specify the output format, optionally supply PATH to redirect formatter output (repeatable)
format: ["pretty"],
//  hide step definition snippets for pending steps
snippets: true,
//  hide source uris
source: true,
// <string[]> (name) specify the profile to use
profile: [],
//  fail if there are any undefined or pending steps
strict: false,
//  (expression) only execute the features or scenarios with tags matching the expression
tagExpression: "",
//  timeout for step definitions
timeout: 60000,
//  Enable this config to treat undefined definitions as warnings.
ignoreUndefinedDefinitions: false,
//  Add cucumber tags to feature or scenario name.
tagsInTitle: false,
scenarioLevelReporter: true
},
Describe the bug
When added with cucumber option  scenarioLevelReporter: true, then the following error is thrown
To Reproduce
Just add scenarioLevelReporter: true and run the test
[Include code or an example repository that can easily be set up]
Expected behavior
A clear and concise description of what you expected to happen.
Snapshots
If applicable, add snapshots to help explain your problem.
Additional context
Add any other context about the problem here.

I'm running into the same issue.


Migrate build-rs to the Cargo repo

What does this PR try to resolve?
Fixes #12432
How should we test and review this PR?
This pulls in https://github.com/cad97/build-rs at eb389d1104dae2dc2eb4eafa9d6e821a7dcb45a7 with the following changes:

Cargo.toml metadata
Removal of .github, .gitignore, Cargo.lock

We'll need to integrate test-lib into our processes but that seemed more invasive, so I wanted to leave that for a future PR.
Additional information
Infra changes are being coordinated in https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Transfering.20.60build-rs.60.20crate.20to.20rust-lang/near/480779960
Context: per Cargo's charter, we approved this transfer in an FCP.

FYI I didn't see this had been created already and finally added some cleanup and items I had missed in the v0.2 refactor that will want to be pulled into this as well.
build-rs-test-lib is just a package that hosts a buildscript that can smoke test invoking the API in a build script context; I don't think it should need anything special.
The changes from v0.1 to  v0.2 are a simplification of implementation, removal of the glob reexports, and basic integration of how the crate can do whatever version smoothing is considered desirable.

Since the FCP was completed. Going to merge this now.
@bors r+

@weihanglo: :key: Insufficient privileges: Not in reviewers


Bitcoin testnet is 6F, not 6E

http://cryptocoinjs.com/modules/currency/coinstring/#list-of-common-crypto-currency-versions
It says that testnet is version 0x6E, but it's actually 0x6F, or 111.

Eeeks! Thanks for reporting! Fortunately I got it correct here: https://github.com/cryptocoinjs/coininfo/blob/master/lib/coins/btc.js#L62 I'll leave this open as a note to correct.

This was fixed, close?

It was just a documentation error. I left this open to remind me to update the docs.

Hi! Have problem with validation testnet address with this script:
var CoinKey = require('coinkey')
var ci = require('coininfo') ///*****
var ck = new CoinKey.createRandom()

console.log("Private Key (Wallet Import Format): " + ck.privateWif)
//KxHycPBUTeWkAuxcG1jzyEogwGFmfVmj3i49i4t4hmfyWkXbujRn
console.log("Private Key (Hex): " + ck.privateKey.toString('hex'))
//20082f69484c00d1c49da31bfe3a700aae0b3218210475d1ede6070063bdc159
console.log("Address: " + ck.publicAddress)
//1Fagh1DKUAZ39EmE6fv6cRHAzUqDK42nAV
//change to Testnet ******
ck.versions = ci('BTC-TEST')
console.log("Testnet Address: " + ck.publicAddress)
//Fagh1DKUAZ39EmE6fv6cRHAzUqDHDw3eD

This site (testnet faucet) say  what address not valid -->
https://testnet.coinfaucet.eu/en/ Fagh1DKUAZ39EmE6fv6cRHAzUqDHDw3eD
Why? Maybe I do something wrong?

@goshva In the future, please open a new issue in the proper module. coinstring and coinkey are different modules.
Also, sorry, I see that you referenced the docs, which are incorrect (http://cryptocoinjs.com/guide/getting-started/)
To answer your question:
var CoinKey = require('coinkey')
var ci = require('coininfo')
var ck = CoinKey.createRandom(ci('BTC-TEST'))

console.log('Private Key (Wallet Import Format): ' + ck.privateWif)
console.log('Private Key (Hex): ' + ck.privateKey.toString('hex'))
console.log('Testnet Address: ' + ck.publicAddress)


Admin front end must make available date and all number data types supported by velocypack/arangodb

Admin ui Document editor data types dropdown is confusing. Admin front end must make available date and all number data types supported by velocypack/arangodb.

We all know this. This is a design issue which we have to address further down the road. I don't see any use of keeping this issue open stealing the sight to important issues.


Settings to configure warnings and errors

Right now, the linter is creating warnings. Is there some way to make them errors or even better, can we define which issues should be errors and which should be warnings?

Yes, by custom rule set, just like you do with the MS code rules

Didn‘t know that works for custom linters too. Thanks and case closed

pragmas do also work ;)


run program

can I use Docker to run the program

I think it should be fine, but we haven't tried it before.


Inconsistent Vars.addAll

The Vars.addAll method has a default implementation, but is also implemented (overridden) in AbstractVariables.
The interface and class implementations do not match, which can be misleading. Also, the actual implementation in AbstractVariables can behave differently depending on the runtime type of the given argument. In our case it always behaves the same because we only have one class that implements both (Val and Var), although this is misleading.
But a real problem I think we have is this:
Vars<String> vars = Vars.of("a", "b", "c");
Vals<String> vals = Vals.of(Val.of("d"), Val.of("e"), Val.of("f"));

vars.addAll(vals);

vars.at(0).set("x"); // ok
vars.at(3).set("x"); // UnsupportedOperationException

Another related inconsistency is that when vals is created via Vals.of("d", "e", "f") it works and the properties in vals are mutable.
Vars<String> vars = Vars.of("a", "b", "c");
Vals<String> vals = Vals.of("d", "e", "f");

vars.addAll(vals);

vars.at(0).set("x"); // ok
vars.at(3).set("x"); // ok

This is because the properties are created through Var.of (sprouts/impl/AbstractVariables.java:54)

I think we should decide what the addAll method should do. I suggest that we stick to the behavior of the other add methods.

When we get a property (var), we add it.
When we get a value, we wrap it in a property and add it.
And no method for adding val's.

For addAll<Vals> it would make sense to add the values wrapped in new properties, but this is not possible because Vals is a sup type of Vars.

I agree with your assessment!
The fact that a call to set may only work sometimes despite the API
claiming that it works is a really big problem.

For addAll it would make sense to add the values wrapped in new properties, but this is not possible because Vals is a sup type of Vars.

Hmm, well it is the other way around. Vals is a supertype.
But I get your point here!
Either we do not user Vals as parameter, or we introduce 2 types of overloaded methods,
one for Vars and one for Vals.

Yes, my last sentence is incorrect. But I think we should not rely on the runtime type to decide what to do, we should rely on the declared type instead.
So we should at least have an addAll(Vars) to be consistent with the other add methods.
And if we decide to have an addAll(Vals) method, we should rely on the declared type:
Vars<String> vars = ...

Vars<String> vars1 = ...
Vals<String> vals1 = ...
Vals<String> vals2 = vars1;

vars.addAll(vars1); // adds the properties
vars.addAll(vals1); // adds the values wrapped in new properties
vars.addAll(vals2); // adds the values wrapped in new properties

And also, if we decide to have an addAll(Vals), why don't we have other add(Val), setAt(int, Val), ..., methods? Would it not be consistent to have them as well? (but maybe that would be too much?)

So I would definitely second the first two of your previously made points.

When we get a mutable property (Var) to a mutable property list (Vars), we simply add it.
When we get an immutable property (from Val.of...), we wrap it in a new mutable property (Var.of..) and add it.

But I do not fully understand what you mean by:

And no method for adding val's.

So as you summarized clearly:
vars.addAll(vars1); // adds the properties
vars.addAll(vals1); // adds the values wrapped in new properties
vars.addAll(vals2); // adds the values wrapped in new properties

I would ensure that the addAll method here has the signature addAll(Vals) and internally
there is a check for which type of property list it is and then it acts accordingly...
And so I don't think it is necessary to have a addAll(Vars) method.
Consequently I would also expect there to be support for Val parameters and implicit conversion...
...as you suggested in your last sentence:

And also, if we decide to have an addAll(Vals), why don't we have other add(Val), setAt(int, Val), ..., methods? Would it not be consistent to have them as well? (but maybe that would be too much?)

The thing we have to acknowledge here is that with the introduction of addAll(Vals)
then we do have to do this kind of implicit conversion pf immutable properties to mutable properties.
So if we do this, then it follows naturally that there are implicit conversions done for single properties...
So I think we should think really hard about the consequences here to a consumer of the API
and if there are pitfalls. I personally do not see any pitfalls or unexpected behaviour.
In a sense Vars.of("a","b","c").addAll(Vals.of("d","e","f")) seems to be a less boilerplaty
variant of Vars.of("a","b","c").addAll(Vals.of("d","e","f").toVars()), which is not at all confusing
or ambiguous...
So in summary, I agree.


wip verbose grounding exporter

@zupon do you know the status of this?

I'm not sure if we still need this? We didn't end up doing anything with it for the ontology augmentation exercise. Alternatively, it might still be good to have another exporter as an option for debugging in the future. If we do want it, I can make sure my other edits/updates are pushed before merging this in. What do you think?

yes, go ahead and push your edits and we should merge for future usage
On Tue, Jun 8, 2021 at 10:16 AM zupon @.***> wrote:

External Email
I'm not sure if we still need this? We didn't end up doing anything with
it for the ontology augmentation exercise. Alternatively, it might still be
good to have another exporter as an option for debugging in the future. If
we do want it, I can make sure my other edits/updates are pushed before
merging this in. What do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/1019#issuecomment-856948136, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCP7YWFZTPNCOBJ7KR3TRZF4ZANCNFSM45DXJZTA
.

Actually, it looks like the most recent update was your print topk commit, so it should be good to merge! All I did after that was run it on some docs to test it out.

@kwalcock I guess my next steps will involve seeing why this can't be built

You may have the wrong language.  I think it is trim() in Scala.
[info] compiling 152 Scala sources to /var/jenkins_home/workspace/eidos_grounding_exporter/target/scala-2.11/classes ...
[error] /var/jenkins_home/workspace/eidos_grounding_exporter/src/main/scala/org/clulab/wm/eidos/exporters/GroundingInsightExporter.scala:56:71: value strip is not a member of String
[error]         pw.println(s"Sentence $i:\t${doc.sentences(i).getSentenceText.strip()}\n\n")
[error]                                                                       ^
[error] one error found
[error] (Compile / compileIncremental) Compilation failed

hahahaha NICE! yay me!
On Wed, Jun 9, 2021 at 4:44 PM Keith Alcock @.***>
wrote:

External Email
You may have the wrong language. I think it is trim() in Scala.
[info] compiling 152 Scala sources to /var/jenkins_home/workspace/eidos_grounding_exporter/target/scala-2.11/classes ...
[error] /var/jenkins_home/workspace/eidos_grounding_exporter/src/main/scala/org/clulab/wm/eidos/exporters/GroundingInsightExporter.scala:56:71: value strip is not a member of String
[error]         pw.println(s"Sentence $i:\t${doc.sentences(i).getSentenceText.strip()}\n\n")
[error]                                                                       ^
[error] one error found
[error] (Compile / compileIncremental) Compilation failed
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Adding an exporter to the collection now...


Support numbers as words in SnakeCaseNamingStrategy and KebabCaseNamingStrategy

Existing implementation does not treat numbers in any special way. They're treated most closely
to lowercase characters. This change provides an options 'numbersAsWords' that permits viewing
numbers as capable of starting and stopping a word.
Closes JamesNK/Newtonsoft.Json#2251

As a note, the generated property names for things such as an ISO timestamp with this option enabled is straight up hideous :) -- I didn't make an attempt to make it look pretty, nor do I think it should be changed. As is, the property is explicit as to how it impacts member name generation and doesn't try to do anything fancy to prevent absurd results. Also, providing these cases via the tests provides tests as documentation so at least it's obvious as to what the expected behavior is, despite how unlikely someone would actually desire such an output.


Photo QA

Just a few missing. No duplicates
dir_project <- 'sern_lchl_necr_fran_2023'
form_pscis_photos_raw <- sf::st_read(
  dsn = paste0('../../gis/', dir_project, '/data_field/2023/form_pscis_2023.gpkg')) %>%
  arrange(site_id)
dir_photos_mergin_raw <- paste0("~/Projects/gis/", dir_project, "/ignore_mobile/photos/")

qa <- fpr_photo_qa_df(
  dat = form_pscis_photos_raw,
  dir_photos = dir_photos_mergin_raw
)

> qa %>% pull(site)
[1]  9900446  5400019  5400028  5400181 15600057 15600467

[ ] Fixed site 15600057, added upstream and inlet no_photos because unable to get those photos due to construction at site, says comments.

No missing photos anymore.

here are the missing photos for the simpc dataset

looks like a rushed a bit and may have deleted 6 photos from the qgis project

some of these photos may have been the photos from above but I wouldn't think so.    These are likely due to some other nuance (ex. extra photos that had no tags so they didn't get added to the directories maybe?)
At any rate, all the photos should also be here .
~/Library/CloudStorage/OneDrive-Personal/Projects/2023_data/fraser/photos
For now - makes sense to look on onedrive for the missing photos above and I will make separate issue to find those 6 photos and restore to the qgis project by downloading the old version of that project (if possible), and rerun the 01_photos.R script to before I nuke the unsorted directory

looks like 9900446 are in mw directory but didn't make it into mergin so didn't show up in Q sort directories. have added and renamed manually.  Was able to track them down by date created in photo details as we know the time the site data was entered into mergin (apparently a few minutes after the photos were taken)

something very odd here.  0ne of these is in the QGIS mergin project but didn't copy to onedrive. can't think of why but a bit concerning...
22200067
Plus - there are 10 photos in the Q project but only 6 made it to onedrive. bizarre

linking to https://github.com/NewGraphEnvironment/fpr/issues/43

mmm... not sure what happened there


.carousel-indicators overlaps navbar-fixed-top dropdown.

in the Carousel Example, I replaced the .navbar-static-top to fixed and I notice when I scroll down the carousel indicator overlaps the dropdown.

This worked for me:
.carousel{
 z-index: 0
 }


feat(2022-12-21): Update SDK to use API generated on 2022-12-21

Signed-off-by: Sunitha Gudisagar<EMAIL_ADDRESS>New Features:
Backup policy jobs

:tada: This PR is included in version 0.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ AZ-Launcher has degraded performance

In 036a7fa, AZ-Launcher (https://az-launcher.nz/) experienced degraded performance:

HTTP code: 200
Response time: 2052 ms

Resolved: AZ-Launcher performance has improved in 1454f54 after 1 hour, 28 minutes.


YARD Type Parser site is down

Steps to reproduce

Open browser to (https://yardoc.org/types.html)
Enter any YARD type syntax and click "Parse"
Observe 502 error indicating back-end is entirely down

[x] I have read the [Contributing Guide][contrib].

@lsegal I hate to bug you, but just wondering is fixing the YARD Type Parser site something that we might be able to help you with?

Thanks for opening this. I've resolved the issue with some server configuration and it should be working now!


Added simulate mode in Hive JDBC Connector to simulate query execution

Added simulate mode in Hive JDBC Connector to simulate query execution

@pcadabam Please review

LGTM apart from that one comment

Thanks for the review


SAS error parsing is largely duplicated between XGA and DAXA

The SAS parsing method from BaseProduct in XGA has basically been copied over, and the lists of SAS errors and warnings have also been copied over.
Probably would be best to just put it all in DAXA, and have XGA import what it needs.

Don't care - this is fine


request failing after a while.

Hi , i use this module in my web scraper and it works fine for a while but then all requests start failing,
i first thought it may be that the host is blocking but i tried and i could still access the same url that is failing with sync-request. hear is the error i get:
TypeError: Cannot read property 'toString' of null     at doRequest (/home/ubuntu/testdir/tvguide/node_modules/sync-request/index.js:27:31)

Looks like spawnSync is returning a stderr of null.  I can't find anything in the docs that says it should do that (https://nodejs.org/api/child_process.html).  In any case, this must be hiding some underlying error.

i found the real problem not related to your module sorry, closing it

If there's something that could have been done in our module to make the error more obvious/easier to spot, we'd love to hear about it.

After profiling i basically found that system ran out of memory due to memory leak in loadash that was used in cheerio.

Thanks, probably not much we can do about that.


Rendering font error

Attach (recommended) or Link to PDF file here:  test.pdf
Configuration:

Web browser and its version: chrome 87.0.4280.88
Operating system and its version: windows10
PDF.js version: 2.6.347
Is a browser extension:

Steps to reproduce the problem:

just open

What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

first page renders fine; other pages fail on fonts

It's weird: when I read the file with firefox nightly using the above url I've the same issue.
But if I use qpdf --stream-data=uncompress a94a8fe5ccb19ba61c4c0873d391e987982fbbd3_1616477914120_83.pdf foo.pdf and then open foo.pdf the fonts are rendered correctly.
So probably something is wrong with the stream decompression.

I think I understand the issue.
In a compressed stream we get object numbers and we just check that we've an offset in stream:
https://github.com/mozilla/pdf.js/blob/ba76dd4000c0efa570558dd56d551b773bb4e856/src/core/obj.js#L2168
but this offset is unused.

For example:
qpdf --show-object=87,0 foo.pdf
<< /BaseFont /#cb#ce#cc#e5 /DescendantFonts [ 88 0 R ] /Encoding /GBK-EUC-H /Name /FSec_song /Subtype /Type0 /Type /Font >>

offset in stream for 87 is 7566
next entry is 105 at offset 7952
qpdf --show-object=105,0 foo.pdf
<< /Ascent 1125 /AvgWidth 500 /CIDSet 106 0 R /CapHeight 1125 /Descent -313 /Flags 14 /FontBBox [ -165 -313 1202 1125 ] /FontFile2 107 0 R /FontName /YWYCMW+E-FZ /ItalicAngle 0 /StemV 86 /Style << /Panose <0a0703000509000000000000> >> /Type /FontDescriptor >>

but in the stream there is an extra object between 87 & 105:
<< /ExtGState << /GSSec_80 32 0 R >> /Font << /F44 33 0 R /F45 40 0 R /F46 47 0 R /F47 52 0 R /F48 58 0 R /F49 63 0 R /F50 69 0 R /F51 76 0 R /F52 81 0 R /FSec_song 87 0 R >> /ProcSet [/PDF /Text /ImageC /ImageB /ImageI] /XObject << /Im2 90 0 R /Im33 91 0 R >> >>

and so this one is seen as object 105.
So the fix is to take into account the offset.
@timvandermeij, @Snuffleupagus do you know if we don't use the offset on purpose or if it's just a mistake ?

Specs say that the N objects must follow the list of pairs (number, offset):
https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#page=54
So I guess this pdf is not conform but there are no issues neither in Chrome nor in Evince.

In poppler:
https://gitlab.freedesktop.org/d1saster/poppler/-/blob/848091f4568436cab321ec4571f5f45833692c0f/poppler/XRef.cc#L197-202
the length of the stream used to get the object is set thanks to the offsets and then the stream is consumed until its and so the extra object is skipped.

do you know if we don't use the offset on purpose or if it's just a mistake?

Well, in the ten years history of this project, this is (to the best of my knowledge) the first time that we've seen this kind of error. Hence it's safe to say that it's a) extremely uncommon, and b) suggests that this particular PDF document has a corrupt XRef-stream.
Based on my experience fixing bugs in the XRef-parsing code, you always need to be very careful since it's too easy to fix one thing and break (loads of) others; don't ask me how I know that :-)
At this point in time we should hopefully have decent test-coverage of the XRref-code, but I'd highly recommend running all tests locally when writing the patch.

Fixed by the PR above. Thank you for reporting this!

There are still missing parts. Here is page 2 of the attached document:

.js 2.8.335
ium 4505


add shift and alt as stash scrolling modifier keys

Description
Fixes #109
Adds Shift and Alt as Scroll Modifier Keys for Stash Navigation
Replication Steps
Navigate to Misc Settings and change Modifier from CmdOrCtrl to Shift or Alt. Hit save and use that modifier with scroll to navigate stash tabs.
Screenshots/Video

How Has This Been Tested?

[x] ran npm run ng:lint
[x] ran npm run format
[ ] ran npm run ng:test
[ ] added unit tests
[ ] manually tested

this branch contains about 2 dozen files that aren't related to the feature that needed linting fixes.


Overwriting the aHrefSanitizationWhitelist

It seems your overwriting the global aHrefSanitizationWhitelist to be more accepting to files which has meant that other link protocols such as mailto: have been broken.
ng-file-upload overwrite
/^\s*(https?|ftp|local|file|data|blob):/

angular default
/^\s*(https?|ftp|mailto|tel|file):/

A better way to append the new whitelist should be found perhaps just allowing for mailto and tel protocols.
Suggestion
/^\s*(https?|ftp|mailto|tel|file|data|blob):/

Fixed at version 7.2.2

Thank you!

This was reverted in https://github.com/danialfarid/ng-file-upload/commit/9f5c4697bc5fa6b3f84bcfd3292b00053615e679. ngFileUpload does overwrite the whitelists, which creates an XSS risk for its users (data: protocol is on the whitelist).

Hey, any update on this? Why was the change reverted?


chore: add some title options for PR lint

Now there are only the semantic PR title options: feat, fix, and chore.
So this PR adds some options to match the aws-cdk.
see<EMAIL_ADDRESS>

LGTM but maybe we want to define when to use what in our contrib guide if we provide so many options?

@hoegertn
How about changing the document a bit?


Compilation error: zpiv/accumulatorcheckpoints.cpp:6:10: fatal error: accumulatorcheckpoints.json.h: No such file or directory

Received the following compilation error noted below.  System is Ubuntu 18.04.
Code used was the latest from https://github.com/beaconcrypto/beacon/archive/v3.4.tar.gz
zpiv/accumulatorcheckpoints.cpp:6:10: fatal error: accumulatorcheckpoints.json.h: No such file or directory
 #include "accumulatorcheckpoints.json.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:5082: recipe for target 'zpiv/libbitcoin_common_a-accumulatorcheckpoints.o' failed
make[2]: *** [zpiv/libbitcoin_common_a-accumulatorcheckpoints.o] Error 1
make[2]: Leaving directory '/tmp/BECN-v3.4.0/src'
Makefile:9482: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/BECN-v3.4.0/src'
Makefile:748: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Update:
Do a
git clone https://github.com/beaconcrypto/beacon.git
will pull an updated version of the source code.  Compiling from there works on Ubuntu 18.04.
Recommendation:
Update the https://github.com/beaconcrypto/beacon/archive/v3.4.tar.gz file appropriately.


Can't receive different Registration Tokens to manage pushes for different users on the same device/app.

Please fill in the following fields:
Unity editor version: 2019.1.14f
Firebase Unity SDK version: 6.2.2
Firebase plugins in use (Auth, Database, etc.): Messaging, Analytics, DynamicLinks and Crashlytics
Additional SDKs you are using (Facebook, AdMob, etc.): None
Platform you are using the Unity editor on (Mac, Windows, or Linux): Mac
Platform you are targeting (iOS, Android, and/or desktop): iOS and Android
Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
I have a project which supports multiple user accounts. I would like to retrieve new tokens after logging in again so the pushes would be specific to the user that just logged in.

Initialize Firebase Messaging as per example (FirebaseApp.DefaultInstance)
Register for messages and token
Confirm you received the token
Unregister for messages and token
Call Dispose on the FirebaseApp instance
Repeat from the beginning and confirm that now no token is received

Please answer the following, if applicable:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?

The gihub project doesn't support this.

Hi @fliperamma are you saying it doesn't work or you don't know how to do it?
I'm assuming the latter, you need to clear the token for the user using the InstanceId API then you can fetch a new token.  https://stackoverflow.com/questions/40315345/change-update-firebase-notification-token-or-instance-id-forcefully-via-code
The thing is this will have pretty nasty side-effects on other parts of Firebase, like Remote Config since it also uses the same token for targeting users.
Typically for this sort of thing, especially since notifications are outside of the app where the user isn't logged in, developers tell users to use multiple accounts on their device rather than supporting multiple sign-in in the application.

Hey @stewartmiles, thanks for getting back to me :)
We basically need to support an old version of this project, which was built using multiple accounts. Migrating everything is out of the table, for now at least.
Do we have access to the InstanceId API in the Unity plugin? I found it here but it doesn't seem to be available in the 6.2.2 version, at least.


Ability to change the execution environment between design and live on shortcut.

We should save the current execution environment in the project's model and assign a shortcut to switch between the design and live modes.
The IDE should assume that design environment is enabled when opening a project.
QA Acceptance Criteria
GIVEN a project opened
THEN I can see a current execution mode in the devtools logs
WHEN I press a shortcut to switch the mode
THEN I can see the changed execution mode in the devtools logs

Implemented in #6341


Please describe the issue in the Readme

I found this plugin in the OctoPrint new plugins list, and have an Ender printer, but I am unsure what the issue is that this plugin serves to resolve. Please add a brief description of the issue to your Readme, so that people who find your plugin in the future will know if they need to install it or not.

The readme has been updated here on GitHub. Will update the plugin repository later :)


Make it easier to provide your own list of autocompletions

To change the prefix autocompletion list to a static one, now requires the following code:
YASQE.Autocompleters._prefixes = YASQE.Autocompleters.prefixes;
YASQE.Autocompleters.prefixes = function(yasqe, completerName) {
  var completer = YASQE.Autocompleters._prefixes(yasqe, completerName);
  completer.async = false;
  completer.get = ["rdf: <http://bla>"];
  return completer;
};

This should be simplified.

This became easier now. Yasqe provides a forkAutocompleter setting. For the above, it would work like this:
Yasqe.forkAutocompleter('prefixes', {
  async: false,
  get: ["rdf: <http://bla>"]
})

(see https://github.com/TriplyDB/Yasgui and https://yasgui.triply.cc)


'pex ' doesn't actually work unless an .egg-info is already there

It turns out that pex for some reason generates an .egg-info missing setup.py, which causes 'pex .' to fail in a fresh clone.
mba=flask=; ~/clients/pex/dist/pex -v -v -v -v -v .


Control which effects play

There should be "modes" or "intensities" where certain effects don't run
Low intensity should only ever do slow fades - no blinks or flashes or instant changes

Done - by default tubes are Chill, but energy level sets which patterns and effects will run


Test Kuadrant with GWAPI v1 rc1

Just noting rc2 has been released - https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.0.0-rc2

I think we are now good #286


VLAZ: Watch \bfreedom.net

VLAZ requests the watch of the watch_keyword \bfreedom\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

\bfreedom\.net has been seen in 1 true positive, 2 false positives, and 0 NAAs.

Rejected by cigien in Charcoal HQ. Reason: 'While the bookending helps, it still detects domains like your-freedom.net, which we want to avoid'


Update crun to 1.17

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Update crun to the latest release.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

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

Project coverage is 41.85%. Comparing base (11d77f4) to head (c85e856).
Report is 418 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2444      +/-   ##
==========================================
- Coverage   45.50%   41.85%   -3.65%
==========================================
  Files          79      109      +30
  Lines        7782    16013    +8231
==========================================
+ Hits         3541     6702    +3161
- Misses       4099     8814    +4715
- Partials      142      497     +355

CI fails with cat: /proc//attr/current: No such file or directory, which comes from here:
https://github.com/kubernetes-sigs/security-profiles-operator/blob/474af83f88d8950548c5dcc54352e31f6504e87b/hack/ci/e2e-apparmor.sh#L85-L89
No idea why this is failing though. 🙈

@mhils the container creation fails with:
Container creation error: write file `/proc/thread-self/attr/apparmor/exec`: No such file or directory

We need to dig deeper into the AppArmor issue. Let's get this in to unblock the CI.
@kubernetes-sigs/security-profiles-operator-maintainers PTAL


Allow users to encrypt their backup

I figured out backups were a plain json file. IMO it should be better to leave the user encrypting the file before exporting it.
I added 2 routes offering an encryption method:

POST /all/export/encrypted expects a JSON body with a passphrase key.
POST /all/import/encrypted expects a JSON body with all and passphrase keys.

If you wonder why I use POST, it's only to avoid to log the passphrase (it's still a bit confusing).
I'm so sorry but I can't deal with React. And even if I tried, I think you'll do better than me!
Cheers

Thanks for the PR! It's an interesting feature. In particular, we currently don't save the accesses' passwords because the password would appear in clear in the export file. Although when you start encrypting the backups, you could put every sensible information in there.
What do you think about having the password in the encrypted export? That would mean changing cleanData so that it accepts a parameter savePassword, but it should be pretty straightforward.
Also, it feels like encrypted could just be a boolean passed in the request's body (in terms of UI, we could then have a checkbox saying "encrypted export"). That would also reduce code dup/boilerplate (and the savePassword could just set with respect to this encrypted boolean).
Otherwise, code looks nice. I need to learn a bit more about the crypto module, but that shouldn't refrain this PR from being landed.
What do you think? Are you willing to update the PR, or should I :-)?

As long as the user is notified that its credentials might be stored and consequently the password must be strong enough to keep them safe, I do not see any cons :-) The drawback of CTR algorithm is its bandwidth which is slightly higher than some other algorithms which cause Bruteforce attacks to be better at cracking the password. That's why strong passwords are mandatory !
Well, I'm going to remove my new routes and include my changes in the existing ones. I leave the UI changes to you since I'm not the right guy for this kind of stuff :-)
I'll try to update my PR within the next days !

I just updated my PR.

POST /all : encryptedand passphrase (both optional) can be passed in the request's body. I update a little your code because if you
GET /all/exportis now deprecated. I leave this route (with the code behind) to avoid breaking UX but it should be removed as soon as UX has been updated.
POST /all/export:

Looks nice, thanks! If you want to update your PR, please do so (and don't forget to rebase, just in case). Otherwise, I'll rebase, address the unique comment and merge tomorrow. Cheers!

Fixed

Thanks for the update! Will merge.


fix: Adjust return value from delete function (#9)

closes #9
Adjusted return-object from delete-Function as proposed in #9

Thanks for the PR! I'm going to merge it, add a couple of tests and then cut a release.

Sure, thank you!


Cellpose Trackmate ImageJ ingtegration not working

I have GFP fluorescence cells which are segmenting in the website of cellpose, but does not function when given in the Fiji-TrackMate plugin with cellpose detector. Can someone help me with the issue

sorry I do not know how the TrackMate plugin works, please open an issue in TrackMate, keep in mind you need to set the diameter in Cellpose to the diameter of your cells in pixels


kube-proxy support

Checkpointing k8s services so they can be self hosting is fascinating.
Rather then doing it with saving off iptables, (which might stop working after stuff like ipvs support lands,
could kube-proxy be modified to checkpoint/restore services similar to the way kubelet does with pods?
If kube-proxy was checkpointed, it should come up, then the checkpointed networks could come up before kube-proxy could talk to the apiserver, establishing a service for the apiserver from the last known statefile, then allowing both kube-proxy/kubelet to talk to the apiserver through the svc.

@kfox1111
Isn't this kube proxy issue? We can't do anything in this repo :)
Can you move to an kubernetes upstream issue?

I guess there are two sides to the coin.
one that applies here, would the devs of kenc be interested in working on this proposed alternate approach? The other side is if the kube-proxy folks were willing to accept the idea?
I can file an issue with the kube-proxy folks too to answer the second question.

@kfox1111
If upstream also wants this feature, we should merge the effort there, and get rid of kenc.

I filed an upstream issue here:
https://github.com/kubernetes/kubernetes/issues/54306


recycle rep to pass data.table 1.12.2

Dear Charles,
Thanks for your email reply last month supporting this change.
I've checked metagene and it's just this one line.
Best, Matt
Rdatatable/data.table#3310
Rdatatable/data.table#3347

Thank you for the pull request!
Have a nice day,
Charles.


Support Synology-NAS-Format

Ive got some error while trying to use your Node with my Synology NAS.

My configuration is as follows:

Did I do something wrong? Ive heard, that maybe the Tag is missing from Synology? Would it be possible for you to rename the Tag to None or something that I can use your node?

Yes, the problem is the missing tag field.  I may have time to fix this so that its a little more forgiving.  Let me see what I can do.
Damo.


Bash-only APT replacement

Now with support local .deb files

prebuild AppImage

Tested recipes:

Scribus
Leafpad
Firefox
Spotify

Nothing short of magic. :+1:  Thank you
However it seems to fail on Bitwig-Studio:
./pkg2appimage-x86_64.AppImage Bitwig-Studio
Error: no such file or directory: ./Bitwig-Studio.AppDir/

Do you have an idea why? It does seem to download the debs just fine...

Do you have an idea why?
Apparently appimagetool is called generating  outside "working" dir

Note to self, a couple of changes will be needed, and while we are at it we may want to use the Go-based appimagetool as well... but that one doesn't have the Bintray stuff yet. So I need to think about how to best integrate this...
note-to-self.zip

This commit fixes it https://github.com/sudo-give-me-coffee/pkg2appimage/commit/b2ea4253151937dc536d0e9cce1076cf07434aa1

It's working now

Thank you very much @sudo-give-me-coffee

@sudo-give-me-coffee why did you close this? It is still very high up on my TODO list. The reason it was not merged so far is that I still have the scripts that build and upload AppImages to Bintray, and this change does not play well with that stuff yet. So it's still some work on my side to make it play well.
In any case, this PR is highly welcome, hence I am reopening it. Thanks a lot!

Getting
+ apt-get.update
./pkg2appimage: line 282: apt-get.update: command not found

Do you have any idea why this might be @sudo-give-me-coffee?

Tried to make a Spotify AppImage on Manjaro Linux which does not use apt -- it is working for me:
wget -c "https://github.com/sudo-give-me-coffee/pkg2appimage/releases/download/no-apt-experimental-build/pkg2appimage-x86_64.AppImage"
chmod x+ ./pkg2appimage-x86_64.AppImage
./pkg2appimage-x86_64.AppImage Spotify # Turn Spotify into an AppImage
./out/Spotify-*.AppImage # Run the Spotify AppImage

The resulting Spotify AppImage runs just fine e.g., on Manjaro Linux :+1

Hi! This merge broke our (Collabora Productivity Release Team) AppImage chain today:
we are using pkg2appimage like this on a ubuntu 18.04 lxc container:
./pkg2appimage Collabora_Online.yml
This is the output where the error occurs :
...
++ readlink -e /home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online
+ echo 'deb file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./'
+ INSTALL=collabora-online
+ '[' '!' -z '' ']'
+ '[' '!' -z loolwsd ']'
+ INSTALL=
+ '[' '!' -z loolwsd ']'
+ INSTALL='loolwsd code-brand collaboraoffice6.2-dict-de collaboraoffice6.2-dict-en collaboraoffice6.2-dict-es collaboraoffice6.2-dict-fr collaboraoffice6.2-dict-it collaboraoffice6.2-dict-nl collaboraoffice6.2-dict-pt-br collaboraoffice6.2-dict-pt-pt collaboraoffice6.2-dict-ru collaboraofficebasis6.2-de collaboraofficebasis6.2-en-gb collaboraofficebasis6.2-en-us collaboraofficebasis6.2-es collaboraofficebasis6.2-fr collaboraofficebasis6.2-it collaboraofficebasis6.2-nl collaboraofficebasis6.2-pt-br collaboraofficebasis6.2-pt collaboraofficebasis6.2-ru'
+ apt-get.update
./pkg2appimage: line 278: apt-get.update: command not found
Build step 'Execute shell' marked build as failure
Finished: FAILURE

And this is the last known successful output with the same stage:
...
++ readlink -e /home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online
+ echo 'deb file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./'
+ INSTALL=collabora-online
+ '[' '!' -z '' ']'
+ '[' '!' -z loolwsd ']'
+ INSTALL=
+ '[' '!' -z loolwsd ']'
+ INSTALL='loolwsd code-brand collaboraoffice6.2-dict-de collaboraoffice6.2-dict-en collaboraoffice6.2-dict-es collaboraoffice6.2-dict-fr collaboraoffice6.2-dict-it collaboraoffice6.2-dict-nl collaboraoffice6.2-dict-pt-br collaboraoffice6.2-dict-pt-pt collaboraoffice6.2-dict-ru collaboraofficebasis6.2-de collaboraofficebasis6.2-en-gb collaboraofficebasis6.2-en-us collaboraofficebasis6.2-es collaboraofficebasis6.2-fr collaboraofficebasis6.2-it collaboraofficebasis6.2-nl collaboraofficebasis6.2-pt-br collaboraofficebasis6.2-pt collaboraofficebasis6.2-ru'
+ apt-get -o Acquire::AllowInsecureRepositories=true -o Acquire::Languages=none -o Acquire::AllowDowngradeToInsecureRepositories=true -o Debug::NoLocking=1 -o APT::Cache-Limit=125829120 -o Dir::Etc::sourcelist=./sources.list -o Dir::State=./tmp -o Dir::Cache=./tmp -o Dir::State::status=./status -o Dir::Etc::sourceparts=- -o APT::Get::List-Cleanup=0 -o APT::Get::AllowUnauthenticated=1 -o Debug::pkgProblemResolver=true -o Debug::pkgDepCache::AutoInstall=true -o APT::Install-Recommends=0 -o APT::Install-Suggests=0 update
Get:1 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ InRelease
Ign:1 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ InRelease
Get:2 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Release
Ign:2 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Release
Get:3 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Packages
Ign:3 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Packages
Get:3 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Packages
Ign:3 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Packages
Get:3 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Packages
Ign:3 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Packages
Get:3 file:/home/collabora/jenkins/workspace/package_appimage_4.2_online_snapshot/collabora-online ./ Packages [20 B]
...

I honestly could not get this patch is worth for.
Should we expect this much major breakage from master branch ?

@yunusem thanks for letting us know, will check once I have some time. As a quick fix, Please use the https://github.com/AppImage/pkg2appimage/tree/legacy-with-apt to get the old behavior. No major changes are expected in that branch anymore. Sorry for the inconvenience!

@probonopd Thanks for quick response! , i did implement a workaround to our chain (had needed urgent care), so no problems on my side, just wanted to let you know guys. Have a good hacking day :smile:

By the way, let me not forget to thank you very much again @sudo-give-me-coffee for this PR and sorry it took so long for me to merge it.

I honestly could not get this patch is worth for.

We can finaly ship pkg2appimage as an AppImage and it will also run on non-deb based systems like Manjaro Linux (where I have tested it). Quite the improvement imho :100:

I too get an error pkg2appimage: line 278: apt-get.update: command not found
I simply wget -N https://raw.githubusercontent.com/probonopd/AppImages/master/pkg2appimage. I found a function.sh in my $app sub-directory. I removed it, reran pkg2appimage, and it succeeded.


Reuse ID policy support for Dapr workflow

This PR is a follow-up PR for https://github.com/microsoft/durabletask-go/pull/46. It include some updates to support reuse ID policy in dapr workflow

tag @ItalyPaleAle , @RyanLettieri for review.


powershell.exe not recognized

https://imgur.com/0nvHkKp.jpg
I'm new to python and all this. Can anyone help how to solve this issue. I installed the Visual Studio 2019 but still it shows this error.

Sounds like you're missing an environment variable.
Add this to your Path environment variable:
%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\


 I have tried many times and get the poor displays. I have even start a new project (test7 as shown below) and get the ugly display, and the boldface one becomes even uglier.
Steps to Reproduce
Start a new project (the increment counter) and run on a real iPad Pro.
Logs
/var/folders/q0/2kd3g8dd42l2ffydw07y4l440000gn/T/_fluttter_toolVBU5J9/app.dill
0
[        ] Updating files
[  +90 ms] DevFS: Sync finished
[        ] Syncing files to device iPad (2)... (completed in 5,642ms, longer than expected)
[        ] Synced 0.9MB.
[        ] Sending to VM service: _flutter.listViews({})
[   +1 ms] Result: {type: FlutterViewList, views: [{type: FlutterView, id: _flutterView/0x108815e20, isolate: {type: @Isolate,
fixedId: true, id: isolates/3929202075474799, name: main.dart$main-3929202075474799, number:<PHONE_NUMBER>474799}}]}
[        ] <- accept
[        ] Connected to _flutterView/0x108815e20.
[   +1 ms] 🔥  To hot reload changes while running, press "r". To hot restart (and rebuild state), press "R".
[        ] An Observatory debugger and profiler on iPad (2) is available at: http://<IP_ADDRESS>:1027/DH5Yn5bhBRQ=/
[        ] For a more detailed help message, press "h". To detach, press "d"; to quit, press "q".

Analyzing test7...
No issues found! (ran in 2.3s)

[✓] Flutter (Channel master, v1.10.7-pre.78, on Mac OS X 10.14.6 18G95, locale en-HK)
    • Flutter version 1.10.7-pre.78 at /Users/chanraymond/development/flutter
    • Framework revision 839fdbd2ed (8 hours ago), 2019-09-29 21:32:06 -0700
    • Engine revision 5b952f286f
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 6ff8d2199d)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/chanraymond/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.0, Build version 11A420a
    • CocoaPods version 1.8.0

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 39.0.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.38.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.4.1

[✓] Connected device (3 available)
    • Pixel 3 XL        • 8A9Y0G17J                            • android-arm64 • Android 9 (API 28)
    • iPad (2)          • 00008027-0001504C2E85002E            • ios           • iOS 13.1
    • iPhone 11 Pro Max • 55D3FBC2-D1EB-4723-917F-B93A13B91072 • ios           • com.apple.CoreSimulator.SimRuntime.iOS-13-0
      (simulator)

• No issues found!

@justinmc - Can you check to see if there's a regression for iOS 13.1 here?

Here's a side by side screenshot of two simulators, iPad Pro 9.7" iOS 11.3 on the left, and iPad Pro 11" iOS 13.0 on the right.  I don't see any boldness, @wnchan2000 do I need to use a physical device?

it says "run on a real iPad Pro"

The boldfacing problem occurs in physical device only. It displays perfectly with simulator. Also, there is no boldfacing problem when displaying Chinese characters, both in physical device and simulator.

https://github.com/wnchan2000/misc/blob/master/IMG_1EDB242D5763-1.jpeg

Same here. Screenshot attached for iOS 13.1 on iPhone X (real phone)

Screenshot using iPad Pro 11" ios 13.1

Saw this happen on iPhone X after iOS 13 update. Possible solution: add custom font to the app (e.g. Roboto).

This is probably related to https://github.com/flutter/flutter/issues/41101.  It seems something in iOS 13 has caused Flutter's font to change.

I can confirm it happens on iPhones too, not just iPad. Things that were perfectly fine, are broken (totally uglyfied) since the update from iOS 12 to 13, even without installing an updated version of our app.

Is this fixed with https://github.com/flutter/flutter/issues/41101?

Fixed with #41101


LANDING_UI_URL misspelled in on premise template

LANDING_UI_URL is misspelled (as LANDING_UI_ULR) in
openness-experience-kits/roles/openness/onprem/master/templates/.env.js

Hi @idirect-dev, This has been identified and fixed. Will be available in 20.03 release. Thanks for reporting it.


(PUP-2744) Always use RedHat service provider instead of init

This commit ensures that for init-based services on RedHat
platforms, the RedHat service provider is used to properly
handle them rather than its more general parent the init provider.

Note: this is a work in progress around what I believe is at least part of the solution for PUP-2744, which describes an issue where on newer redhat platforms, legacy init services are being managed by the init provider rather than the redhat provider.
IIRC, the actual problem under the hood is that Puppet sees both the systemd and redhat providers as system-wide defaults. Systemd is chosen first as the most specific, but for these legacy services Puppet discovers that it can't use this provider. We then have to fall back to another suitable provider, of which there are several in a list.
Although the redhat provider is also a 'default', because it wasn't chosen first it's simply added to the suitable list along with the init provider. Ordering is not guaranteed in this list, and init happens to be element [0], and so is chosen.
Clearly, the real problem here is multiple-default ordering of providers. We've had discussions before about this, and the consensus has always been that allowing multiple defaults would be insane and defeat the purpose of a 'default'. That still leaves us in a bind, since it doesn't allow us to specify a priority ordering of the remaining suitable providers.
An easy way out of this in this particular scenario is to just disable the init provider for redhat systems, as the redhat provider is tailored for the peculiarities of init-based services in the redhats. This is exactly what we did for the Debians.

So, the issues with systemd vs initd are VERY real and not to be taken lightly. In particular, in some versions of RH7, auditd must be managed via init.d otherwise it fails. In theory, any discrepancy that is identified should be pushed upstream to Red Hat, Inc. but that doesn't really help in the short term.
Outside of that, there could be a list of known services with issues that are hard coded into the Red Hat type to switch the provider at the type level until something better can be done. This should be relatively easy even if it's an awful practice.
I would definitely vote for making systemd the default but I would like to see specific services that we know don't work dropped back to initd (there shouldn't be many).
In terms of your specific issue, you may be hitting something in systemd where the service isn't allowed to be enabled due to masking or something like that. I haven't investigated this to any level.

@trevor-vaughan Thanks! This is an interesting problem.
Are you aware that systemctl reload auditd will issue a SIGHUP to the auditd which will caused auditd to reconfigure. Are there situations that you are aware of where reconfiguring auditd is not sufficient?
Perhaps a exec { 'auditd-restart':  command => 'service restart auditd' } would be appropriate in such cases?

@pyther I am indeed aware of both of these solutions. However, this does not address the issue at hand which is that there is one core, and may be other, services which natively do not support systemd as expected.
Now, I'm certainly aware that we can simply say "do X for auditd" and go on our way but that's not exactly a seamless solution for the omnipotent service resource.
And, yes, I can change the restart command in the service resource to say systemctl reload auditd. But again, in theory, the service resource should "just work" since it has a provider that is handling Red Hat explicitly and differentiating between systemd and non-systemd systems.
I guess my argument is; if we know about an edge case, why not handle it?

@trevor-vaughan I don't necessarily disagree with you. I think there are two situations at play here.
The first situation - auditd is a systemd service (/usr/lib/systemd/system/auditd.service). It does not have a init script, but it does have some initscript helpers/actions (/usr/libexec/initscripts/legacy-actions/auditd) which are used by the service command.
The most ideal situation here is to

manage enable/disable state with systemd
manage ensure state (running/stopped) with the service command
manage the restart/reload action using the service command

The second situation - there are services files that have an init script, but do not have systemd unit file. In rhel, systemd will correctly detect the init scripts and issue the appropriate start/stop/reload/enable/disable commands. Note, in debian systemctl enable/disable does work with init scripts. Logic has been added to fallback to their init tools. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/systemd.rb
Example:
$ systemctl enable netconsole
netconsole.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig netconsole on
$ systemctl disable netconsole
netconsole.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig netconsole off
$ systemctl start netconsole
Job for netconsole.service failed because the control process exited with error code. See "systemctl status netconsole.service" and "journalctl -xe" for details.
$ systemctl status netconsole
● netconsole.service - SYSV: Initializes network console logging
   Loaded: loaded (/etc/rc.d/init.d/netconsole)
   Active: failed (Result: exit-code) since Thu 2016-03-10 16:15:48 EST; 45s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 79110 ExecStart=/etc/rc.d/init.d/netconsole start (code=exited, status=6)

Note: netconsole failed to start due system configuration.
Based on this, I don't think anything special needs to be done for legacy init scripts on rhel.
Are there other packages like auditd that ship and use a systemd unit file, but rely on legacy init functionality? I suspect not, but I don't know. If this can be implemented elegantly that would be great, but I would hate to see over complicated code to handle this one situation - for what is essentially an operating system bug.
I'll see if I can parse some RHEL/Centos repo metadata and figure out which packages install files in /usr/libexec/initscripts/legacy-actions/. This should help better answer my question.

I did a quick search with yum and it looks like iptables and auditd are the only packages that provide files in /usr/libexec/initscripts. Iptables only has hooks for 'save' and 'panic'.
[root@gyurgyik-desktop ~]# yum whatprovides /usr/libexec/initscripts/legacy-actions/*/* | grep 'x86_64 : ' | sort | uniq
audit-2.4.1-5.el7.x86_64 : User space tools for 2.6 kernel auditing
iptables-services-1.4.21-16.el7.x86_64 : iptables and ip6tables services for

Any update here?

CLA signed by all contributors.

Based on testing for PUP-6140, I'm :+1: on this.


Update for playground equipment presets

Additional equipment types according to wiki:

activity panel
aerial rotator
climbing wall
excersise
hopscotch
playhouse
sledding
splash pad
teen shelter
trampoline
water

Additional description fields for playground equipment:

blind
sitting_disability
walking_disability
min_age
max_age
theme

Hi FelisPimeja, I am a big fan of mapping playground equipment.

Additional equipment types according to wiki:

…

Personally, I used many of those manually in the past. Sounds good to me to add them.
Some are more used than other, though.
I wonder if there should be a cut to add them only if they are used at least 100 times?
Eg aerialrotator is used only 56 x, yet.

https://taginfo.openstreetmap.org/keys/playground#values

Additional description fields for playground equipment:

However, I am very unsure about the following key. Most of them don't even have a wiki page. They are not used a lot.
I know they are all "officially" from the proposal, but in my opinion they should be used more widely to be added to the preset.

blind

No wiki page. No info on the "Blind"-Wiki-Collection. Only 141 usages.

https://wiki.openstreetmap.org/wiki/Key:blind
https://taginfo.openstreetmap.org/keys/blind
https://wiki.openstreetmap.org/wiki/OSM_for_the_blind

sitting_disability
walking_disability

Same as blind.
I never saw them in use. And would not know how to use them.

No wiki https://wiki.openstreetmap.org/wiki/Key:sitting_disability, https://wiki.openstreetmap.org/wiki/Key:walking_disability
used 90x only https://taginfo.openstreetmap.org/search?q=walking_disability
used 80x only https://taginfo.openstreetmap.org/search?q=sitting_disability

min_age
max_age

I always wondered what to do with those keys on playground structures. There is no sign on such structures that I saw which would help me with this. I could make something up, but thats bad mapping IMO. I understand the usecases the wiki shows outside of playground cases, I just dont see why one would add them to a playground element.

https://wiki.openstreetmap.org/wiki/Key:min_age

used only 496 times in combination with playground https://taginfo.openstreetmap.org/keys/min_age#combinations

https://wiki.openstreetmap.org/wiki/Key:max_age

used ~400 times in combination with playground https://taginfo.openstreetmap.org/keys/max_age#combinations

theme

I tried using this key for playground but it never felt helpful. I kind of makes sense to me on the leisure=playground, but not on playground=trampoline and such. And again, nearly no one uses it:

16x theme + leisure https://taginfo.openstreetmap.org/keys/theme#combinations
16x theme + playground https://taginfo.openstreetmap.org/keys/theme#combinations

Personally, I would skip all the additional tags and just go with the most used playground=* values. And review all this in a year or two to see how mapping evolved in the meantime.

PS: The whole area of playground mapping would get an even bigger boost IMO, if we got OSM-Carto to render the equipment on the higher/highest zoom level. The github discussion about this got stuck a while back, unfortunately.

Ok, @tordans, thank you for detailed explanation. I see your point of view and it makes sence to me. Almost agree about playground values count and mostly about description fields. Except for those:

min_age/max_age isn't popular with playground equipment yet (though it's 522/482 times already used - good dynamics). And children usually better deside themselves what they want to play with : ). But where I live (Moscow, Russia) we have information sings on lots of new playgrounds telling what equipment for what ages is designed (see the image). So that information may be helpfull in some way.

theme tag isn't so helpfull, as for me. But it may be used to describe stylization for lots of playground structures (castle, tower, ship, etc) and spring riders (cars, motorcycles, horses and lots of other animals). And it's funny!

Anyway I'll close this PR and open a new one to make it cleaner. Just tell me what do you think about my suggestions above.

Hi!

min_age/max_age (…) But where I live (Moscow, Russia) we have information sings on lots of new playgrounds telling what equipment for what ages is designed (see the image).

Great example. Looks like a good reason to me to keep the tags.

theme (…)

Yes, and maybe I would use it more, once more values are suggested due to more usage after the preset.

Anyway I'll close this PR and open a new one to make it cleaner.

Maybe wait for some feedback by Bryan and Quincy, first.

Ok. Thank you! Looking for further suggestions.

Lacking further work on this, I just went ahead and manually picked out the most salient changes. Thanks for getting this started, @FelisPimeja, and sorry I couldn't merge it directly!

Is it intentional effect that playground:theme=playground got wildly popular?
See https://github.com/openstreetmap/iD/commit/8a6fa241df1b32a4fe32ebd33dfa256b04483c18 that appears to result in wild growth of playground:theme, mostly playground:theme=playground
See https://taginfo.openstreetmap.org/tags/playground%3Atheme=playground#chronology https://taginfo.openstreetmap.org/keys/playground%3Atheme#chronology that now accounts for over half of uses of this tag.
See https://taginfo.openstreetmap.org/keys/playground%3Atheme#values
If anyone knows what this tag means they are welcome to answer at https://wiki.openstreetmap.org/wiki/Talk:Key:playground:theme
(from quick review it seems to be used mostly by newbie confused mappers due to prominent display in iD presets inviting to fill something there, with playground given as an example - so I expect that this data is meaningless)

8a6fa241df1b32a4fe32ebd33dfa256b04483c18 just added a plain combo field for playground:theme but no hard-coded options, so the field suggests the most common values for that key from taginfo. Most likely the playground value was already near the top, so at best this field contributed to a feedback loop. One solution would be to define well-known values of that key in the field in id-tagging-schema, which will make those values look more legitimate than the ones pulled straight from taginfo.

https://taginfo.openstreetmap.org/tags/playground%3Atheme=playground#chronology https://taginfo.openstreetmap.org/keys/playground%3Atheme#chronology indicate that playground value was unused before iD started to request to fill theme.
Maybe it would be better not as a field available for every single playground? Most playgrounds have no theme. Maybe playground value should be interpreted as "no theme here for this playground".

The id-tagging-schema repo would be a better place to discuss our options for resolving this issue. As far as I can tell, though, it’s a complete mystery as to how this value became more popular than castle, which was the most popular at the time this PR was released.


orthac configuration for helm chart

There are only a few configuration items in orthanc.json. To use helm chart, what configuration items need to be customized? What configuration items are included by default? For example, to use DICOMweb, what configuration items do I need to add?
Thanks.

For orthanc configuration, it is specified in the orthanc.json file. When you first deploy it with Helm, Helm creates a ConfigMap entry named orthanc-app in the orthweb namespace, using this json file. The orthanc pods maps the ConfigMap entry to its container file system.


Added english localization

I am not a native speaker so there are probably some mistakes but I think it will be easier for native English speaker to fix my mistakes than translation from French.

I've cherry-picked the accents fix. It's now merged in incoming, which means it is going to be in the next released version (probably out in September). Thanks a lot for this contribution!

For the record, I am not taking the entire PR, as the English version is already implemented, and the English translations are directly written in raw in the code. That might change in the future, as I'd like to move to Transifex or any other equivalent translation platform.


Update xkcdpwgen dependency.

German wordlist removed in the depencency as it includes non-inclusive / racist terms.

It would be nicer if you had a mod.go file and a release v0.0.1, would you take a PR implementing it?

@AnomalRoil sure. Feel free to create a PR. I'm happy to merge it.


Feature/proxy deploy

zenith proxy deployment for staging environment (staging kubernetes cluster)
this PR contains:

zenith proxy helm chart deploy task in CircleCI
values file for zenith proxy that automatically creates AWS NLB with DNS start.stage.zenith.tech
proxy mgmt will be available from console at zenith-proxy:7000 within Kubernetes

close #951

LGTM, but maybe try deploy from this branch before merging to main?
(set branch filter to feature/proxy-deploy, check and switch back to main)

@ololobus
Yes, I did it before raised PR - link to CircleCI job


Added option to disable internal keyboard handling

Added a boolean which allows users to choose if they want the popup controller to handle the keyboard internally. This allows users to roll their own keyboard implementation or use this library together with other libraries that handle the keyboard such as https://github.com/hackiftekhar/IQKeyboardManager.

I want this change too


Publish 8.10.1-20240906013952+0000

Publish 8.10.1-20240906013952+0000

@bot-gradle test and merge

The merge queue build has failed. Click here to see all failures.


Add ability to register runners under repository for individual accounts

This PR adds the ability to register runners for a repository of an individual account.
To be able to distinguish between runners for an organization and for repository of an individual account a new GitHubRunnerScope is added.
The "GitHub" tab in the settings is updated so both scope types can be configured, but only one scope can be active at the time (the style of the form page is a little bit changed, to try grouping together informations)

This changes are backward compatible as the default runner scope is organization; unfortunately I'm not able to test this changes on a real organization so a real test should be performed.
Fixes #5

(If this PR gets merged, maybe the "Configuring Tartelet" section of the wiki should be updated but I don't think it can be done via a PR)

@mattia Thanks for making these changes and opening a PR!
I'm in the process of reviewing the changes and just wanted to make a note for myself and anyone else seeing this that it seems the permissions needed in the GitHub App are:

Repository Permissions: Administration (Read and Write)
Repository Permissions: Metadata (Read-only)

I have verified that the changes work for repositories owned by an individual and that the existing functionality still works for organization accounts 🎉


Updating to a new version fails

Hello,
I'm getting the following error when trying to push an update, any suggestions?
Thank you!
se***@sk-***-mbp mynightscout-**** % git push heroku main:main
Enumerating objects: 107, done.
Counting objects: 100% (107/107), done.
Delta compression using up to 8 threads
Compressing objects: 100% (42/42), done.
Writing objects: 100% (107/107), 50.43 KiB | 50.43 MiB/s, done.
Total 107 (delta 59), reused 107 (delta 59), pack-reused 0
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Building on the Heroku-22 stack
remote: -----> Using buildpack: heroku/python
remote: -----> Python app detected
remote: -----> Using Python version specified in runtime.txt
remote:  !
remote:  !     A Python security update is available! Upgrade as soon as possible to: python-3.9.15
remote:  !     See: https://devcenter.heroku.com/articles/python-runtimes
remote:  !
remote: -----> Using cached install of python-3.9.13
remote: -----> Installing pip 22.3.1, setuptools 63.4.3 and wheel 0.37.1
remote: -----> Installing dependencies with Pipenv 2020.11.15
remote:        Installing dependencies from Pipfile.lock (c372f1)...
remote:        error in Flask-APScheduler setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; super(type, obj): obj must be an instance or subtype of type
remote:  !     Push rejected, failed to compile Python app.
remote:
remote:  !     Push failed
remote:  !
remote:  ! ## Warning - The same version of this code has already been built: c6aaf50fad1df018236210377a633642b3cb442d
remote:  !
remote:  ! We have detected that you have triggered a build from source code with version c6aaf50fad1df018236210377a633642b3cb442d
remote:  ! at least twice. One common cause of this behavior is attempting to deploy code from a different branch.
remote:  !
remote:  ! If you are developing on a branch and deploying via git you must run:
remote:  !
remote:  !     git push heroku <branchname>:main
remote:  !
remote:  ! This article goes into details on the behavior:
remote:  !   https://devcenter.heroku.com/articles/duplicate-build-version
remote:
remote: Verifying deploy...
remote:
remote: !	Push rejected to mynightscout-*****.
remote:
To https://git.heroku.com/mynightscout-*****.git
 ! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/mynightscout-******.git'

Something must have broken in Flask-APScheduler. I'll take a look -- thanks!

I updated tconnectsync-heroku with new package versions and didn't notice this problem, if you're still experiencing it you can use the latest version. Going to close this issue unless it happens again.


Rest API: client side CL

At the time of this ticket the CL is hardcoded as LOCAL_QUORUM for the REST service.
Some use cases need a higher CL than LOCAL_QUORUM (LOCAL_SERIAL and SERIAL come to mind as common ones when paired with LWT). More advanced users maybe fine with LOCAL_ONE.
I suggest a default CL in the server config and a per request override option. The names don't have to be the existing CLs this is a good opportunity to have something like Dynamo or CosmosDB style consistency levels using the CosmosDB example herehttps://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels
STRONG == LOCAL_SERIAL
CONSISTENT == LOCAL_QUORUM
EVENTUAL == LOCAL_ONE

When it comes to working with Cassandra, how would different guarantees work then?  For instance LWT - is that just implicit in the call like "if exists" or "if val=3"?  I'm just wondering if these sorts of things are considered across all APIs.  I see it's listed specifically in the graphql doc, but didn't know if lwt (for example) works in the REST and the document APIs similarly.  https://docs.astra.datastax.com/docs/using-the-astra-graphql-api#generated-mutation-types

When it comes to working with Cassandra, how would different guarantees work then?  For instance LWT - is that just implicit in the call like "if exists" or "if val=3"?  I'm just wondering if these sorts of things are considered across all APIs.  I see it's listed specifically in the graphql doc, but didn't know if lwt (for example) works in the REST and the document APIs similarly.  https://docs.astra.datastax.com/docs/using-the-astra-graphql-api#generated-mutation-types

LWTs are not currently supported in the restapi nor docsapi but please correct me if I'm wrong @EricBorczuk.

Hi,
Regarding configuring Stargate when you build it you could edit the application.conf file
As the consistency level is defined per request could we add an optional Header parameter CONSISTENCY_LEVEL (after all this is meta Data).

The purpose of the HTTP APIs is to allow users to work with data and abstract away C*.

In my opinion, the Data portion of the API (RowResource) is really close to C* and this one is easy


[FEATURE REQUEST] Add license details to readme

May be helpful to add a License section to the readme with a link to the license file

Pull request #31 would resolve this if merged