Plugin versions not upgraded

Describe the bug
Plugin support via plugin.<pluginId> works, but versions are not refreshed.
Expected behavior
For instance, if the previous version file is:
plugin.org.xtext.xtend=2.0.7

version.org.eclipse.xtend..org.eclipse.xtend.lib=2.19.0

by running ./gradlew refreshVersions I'd expect (at the time of writing)
plugin.org.xtext.xtend=2.0.7
##                                   # available=2.0.8

version.org.eclipse.xtend..org.eclipse.xtend.lib=2.19.0
##                                   # available=2.21.0

I get instead:
plugin.org.xtext.xtend=2.0.7

version.org.eclipse.xtend..org.eclipse.xtend.lib=2.19.0
##                                   # available=2.21.0

To Reproduce
clone this project at this exact commit
run ./gradlew refreshVersions
Note that several plugins could be upgraded (according to a search in https://plugins.gradle.org/) but no update proposal is provided by refreshVersions.

Version 0.9.5 fixes this issues -- also, it looks like it accumulated quite a number of upgrades on that project :rofl: :
## suppress inspection "SpellCheckingInspection" for whole file
## suppress inspection "UnusedProperty" for whole file
##
## Dependencies and Plugin versions with their available updates
## Generated by $ ./gradlew refreshVersions
## Please, don't put extra comments in that file yet, keeping them is not supported yet.

plugin.com.github.spotbugs=4.0.5
##             # available=4.0.6
##             # available=4.0.7
##             # available=4.0.8
##             # available=4.1.0
##             # available=4.2.0
##             # available=4.2.1
##             # available=4.2.2
##             # available=4.2.3
##             # available=4.2.4
##             # available=4.3.0
##             # available=4.4.0
##             # available=4.4.1
##             # available=4.4.2
##             # available=4.4.3
##             # available=4.4.4
##             # available=4.4.5
##             # available=4.5.0

plugin.org.danilopianini.git-sensitive-semantic-versioning=0.1.0
##                                             # available=0.2.1-dev00+03a632e
##                                             # available=0.2.1-dev00+ceeb3fe
##                                             # available=0.2.1-dev00+3bf70f1
##                                             # available=0.2.1-dev00+a929cc4
##                                             # available=0.2.1-dev00+91bc4c6
##                                             # available=0.2.1-dev00+514baf8
##                                             # available=0.2.1-dev00+f2e41d8
##                                             # available=0.2.1-dev00+9f9a8d9
##                                             # available=0.2.1-dev00+428ac38
##                                             # available=0.2.1-dev00+c085c53
##                                             # available=0.2.1-dev00+d54ff87
##                                             # available=0.2.1-dev00+5284013
##                                             # available=0.2.1
##                                             # available=0.2.2

plugin.org.danilopianini.javadoc.io-linker=0.1.4

plugin.org.danilopianini.publish-on-central=0.2.0
##                              # available=0.2.1-dev01+86ce856
##                              # available=0.2.1
##                              # available=0.2.2-dev01+82f26b0
##                              # available=0.2.2
##                              # available=0.2.3

plugin.org.jlleitschuh.gradle.ktlint=9.0.0
##                       # available=9.1.0
##                       # available=9.1.1
##                       # available=9.2.0
##                       # available=9.2.1
##                       # available=9.3.0

plugin.org.xtext.xtend=2.0.8

version.com.google.guava..guava=29.0-jre

version.junit.junit=4.13

version.org.apache.commons..commons-collections4=4.4

version.org.eclipse.xtend..org.eclipse.xtend.lib=2.23.0.M2

Is the behaviour (pick all versions, only the latest, exclude betas or versions with some regex) configurable yet?

The release notes don't mention that it is configurable, so it's not.
You'll see it there once it is.


Add line number support in the sabberworm CSS parser

AMP HTML is a restricted subset of HTML (See https://www.ampproject.org/ for more details) and the AMP PHP Library provide validation and HTML to AMP HTML conversion utilities. We're using the masterminds/html5-php library to parse HTML5 and we're using sabberworm/php-css-parser to parse the CSS in the AMP PHP Library
After parsing the CSS parse we report any problems in the CSS (for e.g. !important is disallowed in the AMP dialect of HTML, we use the sabberworm parser to find all the uses of !important for instance)
Now the CSS supplied by the user could be hundreds / thousands of lines long. So its not useful to simply say that !important was used and is not allowed. We should be able to say which line the problem occurred.
This pull request adds support for line numbers. Here is how we're using this https://github.com/Lullabot/amp-library/pull/80#issuecomment-222695630
Notice the line numbers reported in the validation errors which coming from code submitted in this PR.
Would greatly appreciate if you had a look and merge it if you believe this feature would be useful. Hopefully the code changes have not missed anything out.
Thanks for this useful library BTW.

Wow, thanks for your work. I will review soon…
Maybe you could add a unit test dealing specifically with line numbers and refactor the one you changed to ignore the line numbers so it doesn’t break when we change the source?

Add the getLineNum method declaration to the Renderable interface.
And name it either getLineNo or getLineNumber.
The CSSList class should also implement Renderable, I forgot to do that.

Thanks. I do have one minor nitpick: the Renderable interface should not declare the setter for the line number, only the getter because in order for something to be renderable, the line-number need not be state, it could also be computed upon calling.

Some notes:

The OutputException and UnexpectedTokenException exception classes now have line number information (see the throws) but I think there are 4 places where you're just throwing new \Exception -- it would logical to add line numbers there too -- but I'm not sure if should create another custom exception class or re-use the UnexpectedTokenException (please let me know what params one must use)
CSSList implements Renderable now. In addition Rule also implements Renderable now

Thanks. I do have one minor nitpick: the Renderable interface should not declare the setter for the line number, only the getter because in order for something to be renderable, the line-number need not be state, it could also be computed upon calling.

Its a good idea to have setLineNo generally, mainly for testing purposes where you want to reset the stored line number to 0. What is your alternate suggestion?

Regarding the exceptions:
I used the generic Exception class when we encounter state we can’t possibly recover from. Maybe we should add a class SourceException (exception in source code) which has a line number and use it in place of Exception. We could then let OutputException and UnexpectedTokenException inherit from that. This should even be backwards-compatible unless someone explicitly uses get_class to get the type of an exception instead of using instanceof.
Regarding the line number setter: I would have suggested just removing it from the interface. I was fine with leaving it in the implementations. But seeing the setters are only used in the unit test, I’m thinking we should get rid of them altogether and change this
$oColor->setLineNo(0);
$this->assertEquals(array('r' => new Size(35.0, null, true), 'g' => new Size(35.0, null, true), 'b' => new Size(35.0, null, true)), $oColor->getColor());

into this:
$this->assertEquals(array('r' => new Size(35.0, null, true, $oColor->getLineNo()), 'g' => new Size(35.0, null, true, $oColor->getLineNo()), 'b' => new Size(35.0, null, true, $oColor->getLineNo())), $oColor->getColor());

@sabberworm

We pass in the line number as suggested so that the assertEqual has the correct value for the color test
Removed setLineNo() from everywhere
Added new class SourceException

Do you want to add unit tests for line numbers or shall I? I can do it next week and then release. Does that work for you?

@sabberworm If I add the test myself in sometime would the timelines be earlier? When might you merge to master? When might you create a release tag? (I'm asking because I would need to change some composer.json dependencies accordingly for the AMP PHP Library)
No hurries, of course, but I just wanted to know your plan...

If you don’t add unit tests, I will merge to master now and add the unit tests next week. If you intend to add unit tests now, I will wait with merging until you’re done and release immediately afterwards.

@sabberworm OK -- I'll add a test now... (Thanks for being super responsive on this PR -- Appreciate it)

@sidkshatriya With any luck we can drop PHP 5.3 somewhere in the next year…

[ ] Add some tests for exceptions, e.g.:

/**
* @expectedException Sabberworm\CSS\Parsing\UnexpectedTokenException
*/
public function testUnexpectedTokenExceptionLineNo() {
	$oParser = new Parser("\ntest: 1;", Settings::create()->beStrict());
	try {
		$oParser->parse();
	} catch(UnexpectedTokenException $e) {
		$this->assertSame($e->getLineNo(), 2);
		throw $e;
	}
}

Ideally there would be a test for every place in the parser where we throw an exception.

@sabberworm Hopefully things are now looking good. Let me know if you have any other suggestions (thanks for your really responsive help on this!).
BTW My contributions on this pull request are on behalf of https://github.com/Lullabot
I'll pick up with this tomorrow (or later tonight if I get the chance)

@sabberworm Ah you merged! Great! Thanks so much!

On 30.06.2016, at 16:41, Sidharth Kshatriya<EMAIL_ADDRESS>wrote:
@sabberworm Ah you merged! Great! Thanks so much!

Thank you for your great work! Now I only need someone like you to implement selector and media query parsing…
How do you prefer to be listed under contributors, as individual or as Lullabot?

as Lullabot
re:  selector and media query parsing -- I could look at it in my spare time. If you make a ticket chalking out the details on whats incomplete / what needs to be done etc. it would be awesome. What happens with media queries right now? Does the parser choke or simply not get the finer structure?

The selector parsing is really rudimentary, it just searches for the next { and splits by comma. So it has trouble parsing a selector like a[href*=","] .complicated\{selector.
Media query parsing is even worse. It was only designed to handle @media print {} and chokes on more complex stuff. See #75 and its duplicates (#85, #104) for examples.

Fixing media queries should be a lot simpler than fixing selectors because there are fewer cases to consider and since the current selector parsing works well enough for real-world, non-contrived examples, it’s also the bigger pain point.

@sabberworm
Is your parser hand built or have you consulted something like https://drafts.csswg.org/css-syntax-3/ for your tokenizing/parsing algorithm?
I don't really need media query parsing or selector parsing for the AMP library at the moment (may need it in future) -- but I'm concerned if the parser will abort and issue an exception. Its OK for instance to not do an accurate job of parsing for things like selectors/media queries but aborting the whole parse is not so good... What happens in such cases?

@sabberworm sorry for persisting but I just want to be aware of any parse related aborts due to syntax the parser does not understand. Like I mentioned, it's ok if you don't parse the complex selectors into its fine components or even get media query parsing correct. I just want the parser to skip over those things (or even do a bad job with them). What is problematic is the whole parse getting aborted due to unrecognised (but valid) css syntax.

Some well-defined exception states are recoverable. But because the parser does not know how media queries are supposed to be structures, it can’t recover and throws a SourceException. But I will try to implement correct media query parsing soon since it’s long been one of the major shortcomings of this library.

@sabberworm Thanks for responding and eagerly look forward to some basic media query parsing.
Also to my previous question: is your parsing algorithm hand built or you have consulted something like https://drafts.csswg.org/css-syntax-3/ ? IIRC that there may be general strategies in that link where you can prevent yourself from aborting a parse when you encounter syntax that you don't know about. Basically you should simply skip over to the next at-rule or declaration block that you do understand.

The goal of the parser was always to parse valid CSS. Handling invalid CSS and being fault-tolerant was a feature added later on and does not exactly follow the way the specification demands of browser vendors.
However, for valid CSS (for everything the parser supports, which, currently, does not include media queries) the goal was always to be compliant with the specs, even if the resulting data structure does not adhere to CSSOM.


fix: turning log level down to warn when fallback is available

This will allow the binary to still function if the output is captured.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vbehar
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [vbehar]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Set AXES_WIDTH and AXES_HEIGHT using environment variables

This addresses issue https://github.com/chriscave/mpl_ascii/issues/7
Now AXES_WIDTH and AXES_HEIGHT are set by environment variables if they exist and can be overwritten in the python program. If they don't exist then it's the same behaviour as before.

It's working as expected, thanks!


Build error in Form1.Designer.cs (dlgOpen_FileOk not defined)

I downloaded and built the updated application  I used the code downloaded from the archive rather than walking through the gh-pages manually.   I was able to build but I get an error due to one line (error below).  Commenting out the line (which didn't exist int the ECB version) resolves the issue.
Error	1	'WindowsFormsApplication1.MainForm' does not contain a definition for 'dlgOpen_FileOk' and no extension method 'dlgOpen_FileOk' accepting a first argument of type 'WindowsFormsApplication1.MainForm' could be found (are you missing a using directive or an assembly reference?)	d:\MyProjects\SignXML\SignXML\Form1.Designer.cs	309	88	SignXML

I think there was an empty method created for dlgOpen_FileOK. The empty method was not included on the form so that is why the designer form is barking. I removed that line from Form1.Designer.cs and updated the code.


Two player war

This is going off of #16 (woof archery / angry birds).
The mechanics are like angry birds -- click and drag to aim, release to shoot.
I haven't added this to woof/index.html yet because I'm not sure what level it belongs in. I really wanted it to be accessible at a lower level, but I think it's quite challenging despite looking simple.
Maybe we could make a basic version that's controlled with the keyboard, and this is the more advanced version?

Fun game! It took me a little while to get the hang of the game mechanics until I read the instructions. I assumed that it worked by "drawing a line" from where I clicked to where I dragged, and the angle of that line determined the angle of projectile and the length of the line determined the speed.

Oh, that makes a lot of sense. I'll work on that.

Now that the Line angle issue has been addressed, I was able to finish up this tutorial.
I erred on the side of caution by putting it in level four instead of level three.


Problem while building tpu-image

I got this problem while building tpu-image:
ERROR: Skipping 'cc/selfplay': no such target '//cc:selfplay': target 'selfplay' not declared in package 'cc' defined by /app/cc/BUILD
I check that the file cc/selfplay was deleted. The Dockerfile-tpu might be not updated. Please check and help.

I change cc/selfplay to cc/concurrent_selfplay and build the image, but the following error occur: error: 'google::cloud::bigtable::bigendian64_t' has not been declared. The cause of the problem is because bigendian64_t has been removed in this PR: https://github.com/googleapis/google-cloud-cpp/pull/2068

Another problem: ```
cc/tf_bt_utils.cc:94:24: error: 'Model' has not been declared
Model::FeatureType feature_type, const Game& game) {

Yeah, sorry :(
Unfortunately the TPU code is a little stale and we don't have the bandwidth at the moment to work on it.
If you're not planning on using Cloud BigTable, you can try disabling support, with something like bazel build  -c opt  --define=board_size=19  --define=bt=0 ...

Yeah, sorry :(
Unfortunately the TPU code is a little stale and we don't have the bandwidth at the moment to work on it.
If you're not planning on using Cloud BigTable, you can try disabling support, with something like bazel build  -c opt  --define=board_size=19  --define=bt=0 ...


add <projectDir>/build.gradle with indextoc task

This works
$ cd $projectDir
$ cd docs
$ ./adoc2md.sh -t

but requires a bit of typing. Shorter is beter. I want to do the same as follows:
$ cd $projectDir
$ gradle indextoc

done at v0.1.1


Task startServer Hangs

Build is hanging at startServer.
It is not going ahead to execute remaining tasks.
build.gradle:-
apply plugin: 'com.wiredforcode.spawn'
task startServer(type: SpawnProcessTask, dependsOn: 'assemble') {
command  "startApplication.bat"
ready  'Started.Application'
pidLockFileName ".new.pid.lock"
}
task stopServer(type: KillProcessTask)

cmd Output:-

gradle clean startS stopS
:clean
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:war
:assemble
:startServer
gradlew jettyRunWar
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:war
Building 75% > :startServer

+1 seeing the same issue, and no lock file is being created.

@georgepapas and @brookslyrette - I'm facing the same issue. Did you find any solution for it? thanks

I had the same issue and I think I found out why it is happening. The "ready" directive means it is waiting for the string that you pass to it to appear on standard out. So you will have to specify something your "startApplication.bat" is printing on standard out when it is finished starting. For example, if you have a program which prints "I am a server, I run now on port 8080", you will have to use
ready 'I am a server, I run now on port 8080'
in the task. You can also just use
ready 'I am a server, I run now on port'
since it will do a "contains".
At leas that was what I did wrong and once I fixed it the plugin worked like a charm.
Here is the relevant code from the plugin itself:
    private boolean waitUntilIsReadyOrEnd(Process process) {
        def line
        def reader = new BufferedReader(new InputStreamReader(process.getInputStream()))
        boolean isReady = false
        while (!isReady && (line = reader.readLine()) != null) {
            logger.quiet line
            runOutputActions(line)
            if (line.contains(ready)) {
                logger.quiet "$command is ready."
                isReady = true
            }
        }
        isReady
    }

HTH

I also have a similar issue.  When using 0.6.0 my tests continue after Spring Boot has started.  Using 0.8.0, it just hangs for some amount of time between 2 and 8 minutes, then will continue.  No changes other than the version.


[Bug]: 2.4.0 contains breaking changes

Testcontainers version
2.4.0
Using the latest Testcontainers version?
Yes
Host OS
n/a
Host arch
n/a
.NET version
n/a
Docker version
n/a

Docker info
n/a

What happened?
The version for 2.4.0 release should be 3.0.0. This is breaking the NuGet (and SemVer) versioning rules: https://learn.microsoft.com/en-us/nuget/concepts/package-versioning#version-basics
Relevant log output
No response
Additional information
I think that the package should be released as 3.0.0 to avoid confusion as well as unlist the 2.4.0 package.

I have not seen

we have flagged all upcoming breaking changes as obsolete

We fail the build when there is a warning. Sorry for false negative.

Reopening as e.g. the change of IWaitUntil is breaking.

Reopening as e.g. the change of IWaitUntil is breaking.

Yes, it is mentioned here. We will keep the version and not unlist it.


Node16 update

I tried to manual edit node12 to node16 in action.yml and it seems to kinda work.
Only wrong think i see while uploading in log is not correct progress
Upload release.zip -> /test/release.zip: 175672527 Bytes
Uploaded NaN% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Uploaded Infinity% release.zip
Success undefined

Thank you for PR!
Can you please fix this Uploaded Infinity% release.zip too?

I quickly looked at code and found
this.logger?.info(Uploaded ${(uploaded / total) * 100}% ${file})
,maybe division with zero?


Request Feature

Hi, Adding admin panel with upload feature like https://streamaserver.org will be helpful.

How's the Android version coming along?

Hi @ridhwaans! Is it project deprecated? is it maintained? Maybe you should update Readme

readme is updated

👍


SAK-29033 add .ics extension to opaque subscription URLs

so Google will import it.
Also remove text that says "should definitely work" because we can't make promises
about a huge range of clients
I learned about iCal "gotchas" here:
https://www.marcus-povey.co.uk/2012/11/14/ical-gotchas/

There's another call to calendarOpaqueUrlReference in org.sakaiproject.tool.summarycalendar.ui.SubscribeBean#getUrl() which should also have the .ics extension.
I'd be temped to just append the .ics in the service instead.

Okay, thanks for the review. I moved the modification to the service and then squashed the commits into one

LGTM


[COVAX demo app] Add patient search

[x] Implement patient search by filtering patient results on the Patient View Model.
[x] Filter the collection based on searched values or we filter the patient list

Is this (or the logic for it) something that we can store in a syncable configuration file?

No. The generic and ideal implementation is blocked by work on the Google FHIR SDK on issues https://github.com/google/android-fhir/issues/431, https://github.com/google/android-fhir/issues/376 and   https://github.com/google/android-fhir/issues/292

Is this (or the logic for it) something that we can store in a syncable configuration file?

No. The generic and ideal implementation is blocked by work on the Google FHIR SDK on issues google/android-fhir#431, google/android-fhir#376 and google/android-fhir#292

ok understood


Sanitize strategy not working

I have set the sanitize strategy using $translateProvider.useSanitizeValueStrategy('sanitize'). It is not working when i use the translate directive. When I am using the translate filter, all works as expected. Do I miss an option?
Your environment

version of angular-translate: 2.18.1
version of angular: 1.5.5
Chrome: 75

Steps to reproduce

{{ 'HEADLINE' | translate }}

  Not working

  Working

{{text | translate}}

var app = angular.module('myApp_escaped', ['pascalprecht.translate', 'ngSanitize']);

app.config(['$translateProvider', function ($translateProvider) {
  $translateProvider.translations('en', translations);
  $translateProvider.preferredLanguage('en');
  // Enable escaping of HTML
  $translateProvider.useSanitizeValueStrategy('sanitize');
}]);

app.controller('Ctrl', ['$scope', function ($scope) {
  $scope.text = 'Test HACKED';
}]);

http://plnkr.co/edit/fypR6SxqNp2CyPKgw8hy?p=preview
Expected behaviour
HTML is only visible as text
Actual behaviour
HTML is in the dom

Hey, I have this same issue. I'm interested in finding a way to sanitize using the directive so I don't have to change a lot of code to use the filter instead.

Hey, in your plunker, I change the sanitization strategy from sanitize to escape and that achieves the expected behavior.

Hello, I have tested your statement but I can't reproduce it. When I change the strategy to escape like this: $translateProvider.useSanitizeValueStrategy('escape');, the text "Test HACKED" is still shown. Can you check it again please? Or post a working plunker? Thanks

Ah... nevermind. I misread the output of that change.

Well, escaping the translation works as you already pointed out. But the translation key will not be modified, which in this case is the "hacked" text.
Originally, we see a translation key as an internal (and therefor trustful) information/string. Eventually you can intercept this behavior with a custom handler: https://angular-translate.github.io/docs/#/api/pascalprecht.translate.$translateProvider#methods_usemissingtranslationhandler


Issue with YAML parsing

Hello,
after syncing the last commit and updating, I have the following error using either ethd update or ethd stop or ethd up :
yaml: line 168: did not find expected key
I'm not sure to identify where it comes from and the logs are not very verbose. Any hint to start debugging ?

Hey sorry for breaking things! Please give me your COMPOSE_FILE from .env and I will see that I can reproduce this!
Does it tell you more around that, like which yaml file?

The only two yml files that even have that many lines are lighthouse.yml and prysm.yml. I cannot reproduce with either.
Maybe you have local changes to files? What does git status show you?

Yes I do have some changes which I re-apply at every release from the main branch.
This time there was an issue apparently. so I removed several YAML files, and git restore them.
The error has disappeared now but it's quite strange because I didn't change anything to my process. Maybe a yaml file didn't sync well. I'll close the issue. thanks for your quick answer.

One thing I'll point out is that CL_EXTRAS, EL_EXTRAS and VC_EXTRAS exist in .env and cover a lot of use cases that might otherwise be handled by yml changes.
Where you do need changes, if you commit them, they should merge automatically with the next update


promptfoo 0.60.0 --share not working

I am upgrading to promptfoo 0.60.0 and run my test again with --share flag.

It failed both in CI/CD and local. Looks like a bug.
Could you reproduce this on your side?

Thanks for the report.  This should be fixed now.  Could you please confirm on your side?

@typpo Thanks!! It works!


How to add costum sites to geosite.db?

How can I append some new sites to geosite.db file?

https://github.com/bootmortis/iran-hosted-domains#create-dat-file-manually-tutorial


Binding geiser-eval-last-sexp in the REPL

It would be nice if geiser-eval-last-sexp was bound to C-x C-e in the REPL. SLIME binds its version in its REPL.

we are moving the project to gitlab. so please, follow-up there as needed. sorry for the inconvenience!
http://gitlab.com/jaor/geiser/issues/155


query remote clickhouse instance

Suppose I would want to read foreign Clickhouse data.
If I typed the following:
select * from remote('database:port','database.table','user','password')

If I understand correctly, it just returns "Ok". and doesn't process the query
Did I do something wrong? It seems like potentially desirable behavior to be able to read directly from Clickhouse instances.

Hello @alanpaulkwan I can perform remote queries to clickhouse servers just fine using the latest release:
# python3 -m chdb "select * from remote('XXXXXXXX:9000','system.disks','default','XXXXXXXXXXX')"

"backups","/backups/",3505403396096,3910140764160,3505403396096,0,"local",0,0,0,0,0,""
"default","/var/lib/clickhouse/",3505403396096,3910140764160,3505403396096,0,"local",0,0,0,0,0,""
"s3","/var/lib/clickhouse/disks/s3_disk/",18446744073709551615,18446744073709551615,18446744073709551615,0,"s3",0,0,0,1,0,""

Same goes for the libchdb bindings, for example in go:
# ./chdbgo -query "select * from remote('XXXXXXXX:9000','system.disks','default','XXXXXXXXXXX')"

"backups","/backups/",3505439924224,3910140764160,3505439924224,0,"local",0,0,0,0,0,""
"default","/var/lib/clickhouse/",3505439924224,3910140764160,3505439924224,0,"local",0,0,0,0,0,""
"s3","/var/lib/clickhouse/disks/s3_disk/",18446744073709551615,18446744073709551615,18446744073709551615,0,"s3",0,0,0,1,0,""

Could you confirm your running environment and installed version?

I was using the demo version on Github. My fault, can try in Python later.

I was using the demo version on Github. My fault, can try in Python later.

Thanks @alanpaulkwan which demo version are you referring to? This should work from everywhere, including the public demo (which I used above, too) as long as credentials are fine. Perhaps this was a secure connection? if so remoteSecure should be used instead of remote

ch.fly.dev

I entered your query which obviously shouldn't run, since I don't know the IP or real pw

Here's a working query you can try using the public clickhouse play server:
select count(*) from remoteSecure('play.clickhouse.com:9440','default.covid','play','play')

Let's close this - I got it working on my latest pip install!

Thanks @alanpaulkwan I understand the report now: the web demo does NOT return full error messages (the library does) and perhaps this was the confusing bit all along. Glad you got this working, and welcome to our community!


[Bug Report]: aks-run-command does not fail on error

Module path
/modules/deployment-scripts/aks-run-command
Bicep version
0.9.1
Describe the bug
When running commands to AKS, if the command fails, this step continues as if it succeeded. This can lead to surprising outcomes in a deployment process. It is difficult to determine this step is responsible in a large pipeline when it finishes as "Succeeded".
To reproduce
Running an AKS command which raises an error. (I have some branches to repro)
Code snippet
No response
Relevant log output
...
Installing it now.
Error: execution error at (workload-identity-webhook/templates/azure-wi-webhook-config-configmap.yaml:4:22): A valid .Values.azureTenantID entry required!
", "provisioningState": "Succeeded", "reason": null, "startedAt": "2022-10-03T22:39:26+00:00" }

It's an interesting problem. Depending on the commands sent will change your measure of success.
Technically the deployment script worked great, but the objective of the users script was not met.
We won't be able to fail the deployment because of an error, but we could create a new output to try to indicate success. I just wonder if that will be useful.

So, my original statement wasn't completely accurate, it seems the task does sometimes fail on error. I'm not sure why it fails for some issues but not others.
The Script task fails with the error: "Unable to evaluate template outputs: 'commandOutput'. Please see error details and deployment operations. Please see https://aka.ms/arm-debug for usage details."
This is possibly caused by a bug, where we should check to see if outputs exist before calling it. But it has a nice side effect of failing the task right now.
https://github.com/Azure/bicep-registry-modules/blob/03478531a2971aa819a0c232c1e79ac6bdbf5693/modules/deployment-scripts/aks-run-command/main.bicep#L136
I am able to reproduce this pretty easily trying to setup a workload identity on a subscription which has not set the following.
While having the task fail is desired, would still like to have some errror output that is a bit more meaningful.
az feature register --namespace "Microsoft.ContainerService" --name "EnableWorkloadIdentityPreview"

az provider register --namespace Microsoft.ContainerService

Dear @dciborow , Azure Verified Modules (AVM) will become the single Microsoft standard for Bicep modules. Transitioning to AVM, requests for new features or bug fixes will need to be submitted against the appropriate AVM module via AVM Module Issues.
For bugs or new features with existing modules in the /modules directory of this repository, we encourage you to first try the AVM equivalent module if available and if the module is lacking any features, you can file an AVM Module Issue. If the module is not available yet, you can file a new AVM Module Proposal.
See this informational notice for more details on the upcoming changes.
Thank you for your understanding!


heat-generator: fix default value for tagged-vlan

The False default tagged-vlan value used by the heat generator did
not correspond to the default tagged-vlan value used in the
input models (True). This is causing external network connectivity
issues when the std-min input model is used.

Looks good to me.


Unsubscribe not working

I've been debugging some issues in one of my apps, and drilled down to the most likely cause being apollo subscription cancels not flushing to the absinthe socket.  To reproduce, I simply called a subscribeToMore for one of my queries and immediately called the cancel callback function after, and observed no unsubscribe event pushed to the socket.
I'm using a newer version of apollo, so this might be a regression (and i seem to remember seeing this working with older versions of apollo's react client). Here are the versions:
"@absinthe/socket": "^0.2.1",
"@absinthe/socket-apollo-link": "^0.2.1",
"@apollo/react-hooks": "^3.1.5",
"apollo-boost": "^0.4.7",

hey! I think i have the same issue. I'm using "@absinthe/socket": { "version": "0.2.1" }
I'm following the approach described on the documentation: creating an Observable, calling subscribe on it and afterwards calling unsubscribe on the subscription it returns.
I'm doing this on some tests on Jest and unsubscribing on the afterAllcallback, but in the end Jest keeps complaining with: Jest did not exit one second after the test run has completed and it keeps running, which leds me think the connection wasn't closed correctly

Does anyone have a solution to this? Apparently, the issue was also discussed here, but the solution did not work for me.


Repo sync for protected CLA branch

The pull request is created from master637328516085555619 to master to fix git push error for protected CLA branch

@Taojunshen : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add install_manifest.txt to gitignore

install_manifest.txt gets created when running make install and it
should be ignored by the vcs

Thanks!


Add slice method to collections

Adds slice method to collections. If someone else gets to a solution for proxying enumerable methods to Array and lodash first, great. But this would be helpful too.

We originally had Collection extend [], but that cause problems (bc you can't really do that), but now that it's not a fake subclass I think it makes sense to start adding these methods back in.
Maybe we can look at how Backbone collections proxy methods to lodash.


User notification before closing Office apps

Hi,
integration of ServiceUI would be great, so the user gets informed about closing the other office apps and saving their work, before e.g. Visio is installed.
Based on:
https://365bythijs.be/2019/09/19/installing-visio-onto-an-existing-office-installation-with-psadt-and-intune/
Thomas

It should be fairly easy for those who needs so to intergrate what we are doing here with PSADT and or using ServiceUI on their own. Will not be our focus for now at least.


fix: add service summaries

:tada: This PR is included in version 1.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[20.09] pkgs/mariadb: Fix when running without aliases

Backport of #100413

shouldn't the commit be mariadb: ... ?

np, it's still "close enough"


aiohttp - local variable 'resp' referenced before assignment

Home Assistant 0.37.1
Python 3.4.2
aiohttp
After crtl+C I got error: UnboundLocalError: local variable 'resp' referenced before assignment

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/mnt/hdd/python/.homeassistant/deps/aiohttp/server.py", line 261, in start
yield from self.handle_request(message, payload)
File "/mnt/hdd/python/.homeassistant/deps/aiohttp/web_server.py", line 88, in handle_request
resp._task = None
UnboundLocalError: local variable 'resp' referenced before assignment

This seems to be a bug in the aiohttp itself. I've looked on their github and this seems to be already fixed on their master branch. No release with the fix yet unfortunately.

@omcdr @yawor are you able to reproduce this on 0.38?

No, I don't have exception with aiohttp.
But I have another one:

Exception in thread Thread-10:
Traceback (most recent call last):
File "/var/python3.4.2/lib/python3.4/threading.py", line 921, in _bootstrap_inner
self.run()
File "/mnt/hdd/python/lib/python3.4/site-packages/homeassistant/components/recorder/init.py", line 212, in run
self._setup_run()
File "/mnt/hdd/python/lib/python3.4/site-packages/homeassistant/components/recorder/init.py", line 408, in _setup_run
for run in query('RecorderRuns').filter_by(end=None):
File "/mnt/hdd/python/lib/python3.4/site-packages/homeassistant/components/recorder/init.py", line 157, in query
_verify_instance()
File "/mnt/hdd/python/lib/python3.4/site-packages/homeassistant/components/recorder/init.py", line 488, in _verify_instance
raise RuntimeError("Recorder not initialized.")
RuntimeError: Recorder not initialized.


Continue parsing on illegal value if default is present?

Is there any way to continue parsing the rest of the file if one of the values is of wrong type but the class contains default value for it?
For example when some enum is misspelled
code example:
enum class EnumTest { A, B, C }
@Serializable
data class Foo(
    val a: Int = 5,
    val b: EnumTest = EnumTest.A,
    val c: String = "hello"
)

TOML:
a = 8
b = "D"
c = "world"

Expected result of parsing would be
Foo(a = 8, b = EnumTest.A, c = "world")
Current behavior:
Value <D> is not a valid enum option. Permitted choices are: A, B, C
My current workaround is to catch the exception, remove the line with specified value and try to parse again. But even that fails if that wrong value is correctly used in another place in the file.

Hm, very unusual case for us, but probably we need to think about such an option to have non-strict parsing in case when the default value is already provided


[Feature] Add types to useResults file

Is your feature request related to a problem? Please describe.
The useResults test file does not have types
Describe the solution you'd like
Change the file type from .js to .tsx
Add types inside the file
Additional context
https://github.com/eduardconstantin/azure-cloud-exams/blob/main/profilerFunctions/useResults.js

Hey! Can you assign me this issue? The js file needs to have type safety and hence converted to ts, right? Is my understanding correct?

yes, that's right

@sushant0709 are you still working on this issue?

@eduardconstantin yes, would complete it by this weekend.


TypeError: str.replace is not a function

Updated to use latest fixes to v0.2.1 and not i'm getting this:
/home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:51
      str = str.replace(this._trimRegex, "");
                ^

TypeError: str.replace is not a function
    at HTMLExtractor.module.exports.HTMLExtractor._trim (/home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:51:17)
    at HTMLExtractor._trim (/home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:3:59)
    at /home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:111:31
    at Object.htmlparser.Parser.onend (/home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:248:13)
    at Parser.onend (/home/user/javascript/website/node_modules/html-extractor/node_modules/htmlparser2/lib/Parser.js:310:32)
    at Tokenizer._finish (/home/user/javascript/website/node_modules/html-extractor/node_modules/htmlparser2/lib/Tokenizer.js:838:12)
    at Tokenizer.end (/home/user/javascript/website/node_modules/html-extractor/node_modules/htmlparser2/lib/Tokenizer.js:829:25)
    at Parser.end (/home/user/javascript/website/node_modules/html-extractor/node_modules/htmlparser2/lib/Parser.js:338:18)
    at HTMLExtractor.module.exports.HTMLExtractor._extract (/home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:256:14)
    at HTMLExtractor._extract (/home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:3:59)
    at HTMLExtractor.module.exports.HTMLExtractor.extract (/home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:94:12)
    at HTMLExtractor.extract (/home/user/javascript/website/node_modules/html-extractor/lib/html_extractor.js:3:59)
    at site_crawler.on (/home/user/javascript/website/search.js:212:22)
    at emitThree (events.js:116:13)
    at emit (events.js:194:7)
    at emitFetchComplete (/home/user/javascript/website/node_modules/simplecrawler/lib/crawler.js:1065:17)
App stopped unexpectedly

@mpneuried already working on the fix. A PR will land soon. It is related to the list: true  when using reduce

Thanks for the hint and pull request with the trimming in combination with the list feature.
I optimized your push and published it as 0.2.2


Missing / Incorrect Tags and Cards

While putting my collection in the site I noticed a couple of small things which I've listed below.

Lillymon EX1-039, Agumon ST1-03, Numemon BT2-056, Gammamon BT8-008, Terriermon EX2-025 are all improperly tagged as alt-art
Silphymon BT8-015 is tagged as Red and Green while all stamped variants of Paildramon ST9-05 aren't tagged with any color
Both versions of The Ray of Victory BT2-096 are missing the uncommon tag
"Reinforcement Plug-In O" BT10-109 is misnamed "Upgrade Plug-In O"
The english alternate art versions of WarGrowlmon EX2-010, Taomon EX2-023, and Rapidmon EX2-027 from Tamer Party Vol. 6 are missing

I have links to images of the cards listed above if needed.

WarGrowlmon EX2-010
Taomon EX2-023
Rapidmon EX2-027

Also i found that:
ST8-08 is missing (sec attack +1) keyword tag.
ST9-07 is missing blocker keyword tag.
BT11-076 is wrongly tagged as having DigiXros special requirement.

Thanks guys, just added all the missing stuff and fixed the errors <3


[Release 4.1] Bug 1767846: Manual approval strategy ignored for subsequent releases

For an subscription with manual approval, only the initial installplan
respects the approval requires. Subsequent installplans ignore the
fact the approval status is still false and install the operator
regardless. This issue is due to catalog incorrectly transitions
the installplan into install phase without checking for approval
condition.
Signed-off-by: Vu Dinh<EMAIL_ADDRESS>
Description of the change:
Motivation for the change:
Cherry-pick to 4.1
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/retest

/retest

/test e2e-aws-olm

@operator-framework/patch-managers Would like to ask for an approval on this cherry-pick PR. PTAL. Thanks

/lgtm


Is there any library to generate Swagger.json from a .net core console application and store it in a specific location?

I was wondering if there is a way to generate Swagger.json manually instead of loading it from http://host:port/swagger/v1/swagger.json.

This is not an issue, please close it.
You might want to post this question in StackOverflow

Closing it as it is not related. Thanks!


Vagrant/Ansible Run Tests Failure

I am attempting to run mull on CentOS using the vagrant up debian command. I get an error when running the tests step.
TASK [Run Tests (Debug)] *******************************************************
fatal: [debian]: FAILED! => changed=true
  cmd:
  - /opt/build.mull.debug.dir/tests/mull-tests
  delta: '0:00:00.008273'
  end: '2019-09-18 17:01:22.821453'
  msg: non-zero return code
  rc: -11
  start: '2019-09-18 17:01:22.813180'
  stderr: ''
  stderr_lines: <omitted>
  stdout: ''
  stdout_lines: <omitted>

PLAY RECAP *********************************************************************
debian                     : ok=12   changed=10   unreachable=0    failed=1    skipped=0    rescued=0                             ignored=0

Full Log

Full Log
$ vagrant up debian
Bringing machine 'debian' up with 'virtualbox' provider...
==> debian: Importing base box 'debian/stretch64'...
==> debian: Matching MAC address for NAT networking...
==> debian: Checking if box 'debian/stretch64' version '9.9.1' is up to date...
==> debian: Setting the name of the VM: mull-debian
==> debian: Fixed port collision for 22 => 2222. Now on port 2200.
==> debian: Clearing any previously set network interfaces...
==> debian: Preparing network interfaces based on configuration...
    debian: Adapter 1: nat
==> debian: Forwarding ports...
    debian: 22 (guest) => 2200 (host) (adapter 1)
==> debian: Running 'pre-boot' VM customizations...
==> debian: Booting VM...
==> debian: Waiting for machine to boot. This may take a few minutes...
    debian: SSH address: <IP_ADDRESS>:2200
    debian: SSH username: vagrant
    debian: SSH auth method: private key
==> debian: Machine booted and ready!
==> debian: Checking for guest additions in VM...
    debian: No guest additions were detected on the base box for this VM! Guest
    debian: additions are required for forwarded ports, shared folders, host only
    debian: networking, and more. If SSH fails on this machine, please install
    debian: the guest additions and repackage the box to continue.
    debian:
    debian: This is not an error message; everything may continue to work properly,
    debian: in which case you may ignore this message.
==> debian: Configuring proxy for Apt...
==> debian: Configuring proxy environment variables...
==> debian: Installing rsync to the VM...
==> debian: Rsyncing folder: /home/dangrahn/mull/infrastructure/ => /vagrant
==> debian: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.4).

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

    debian: Running ansible-playbook...
PYTHONUNBUFFERED=1 ANSIBLE_FORCE_COLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserK                         nownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s' ansible-pla                         ybook --connection=ssh --timeout=30 --limit="debian" --inventory-file=/home/dangrahn/mull/infrastructu                         re/.vagrant/provisioners/ansible/inventory --extra-vars=\{\"llvm_version\":\"6.0.0\"\} -v debian-playb                         ook.yaml
Using /home/dangrahn/mull/infrastructure/ansible.cfg as config file

PLAY [Setup Debian Machine] ****************************************************

TASK [Gathering Facts] *********************************************************
ok: [debian]

TASK [Prepare Working Directory (/opt)] ****************************************
ok: [debian] => changed=false
  gid: 0
  group: root
  mode: '0755'
  owner: root
  path: /opt
  size: 4096
  state: directory
  uid: 0

TASK [Change ownership of working directory (/opt)] ****************************
changed: [debian] => changed=true
  gid: 0
  group: root
  mode: '0755'
  owner: vagrant
  path: /opt
  size: 4096
  state: directory
  uid: 1000

TASK [Install Required Packages] ***********************************************
 [WARNING]: Updating cache and auto-installing missing dependency: python-apt

 [WARNING]: Could not find aptitude. Using apt-get instead

changed: [debian] => changed=true
  cache_update_time:<PHONE_NUMBER>
  cache_updated: false
  stderr: |-
    Extracting templates from packages: 47%Extracting templates from packages: 95%Extracting templates                          from packages: 100%
  stderr_lines: <omitted>
  stdout: |-
    Reading package lists...
    Building dependency tree...
    Reading state information...
    The following additional packages will be installed:
      bc binutils cmake-data cpp cpp-6 fish-common gcc gcc-6 git-man icu-devtools
      javascript-common libarchive13 libasan3 libatomic1 libc-dev-bin libc6-dev
      libcc1-0 libcilkrts5 libcurl3 libdpkg-perl liberror-perl
      libfile-fcntllock-perl libgcc-6-dev libgomp1 libicu-dev libicu57 libisl15
      libitm1 libjs-jquery libjsoncpp1 liblsan0 libmpc3 libmpfr4 libmpx2
      libpcre2-32-0 libquadmath0 libtinfo-dev libtsan0 libubsan0 libuv1
      linux-libc-dev lynx lynx-common make manpages-dev patch vim-common
      vim-runtime vim-tiny xsel
    Suggested packages:
      binutils-doc codeblocks eclipse cpp-doc gcc-6-locales doc-base gcc-multilib
      autoconf automake libtool flex bison gdb gcc-doc gcc-6-multilib gcc-6-doc
      libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan3-dbg
      liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libmpx2-dbg
      libquadmath0-dbg git-daemon-run | git-daemon-sysvinit git-doc git-el
      git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn apache2
      | lighttpd | httpd lrzip glibc-doc debian-keyring icu-doc liblzma-doc
      ncurses-doc sqlite3-doc libstdc++-6-doc make-doc ed diffutils-doc ctags
      vim-doc vim-scripts indent
    The following NEW packages will be installed:
      bc binutils cmake cmake-data cpp cpp-6 fish fish-common gcc gcc-6 git
      git-man icu-devtools javascript-common libarchive13 libasan3 libatomic1
      libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libcurl3 libdpkg-perl
      liberror-perl libfile-fcntllock-perl libgcc-6-dev libgomp1 libicu-dev
      libisl15 libitm1 libjs-jquery libjsoncpp1 liblsan0 liblzma-dev libmpc3
      libmpfr4 libmpx2 libncurses5-dev libpcre2-32-0 libquadmath0 libsqlite3-dev
      libstdc++-6-dev libtinfo-dev libtsan0 libubsan0 libuv1 libxml2-dev
      linux-libc-dev lynx lynx-common make manpages-dev ninja-build patch
      pkg-config uuid-dev vim vim-runtime xsel zlib1g-dev
    The following packages will be upgraded:
      libicu57 vim-common vim-tiny
    3 upgraded, 60 newly installed, 0 to remove and 40 not upgraded.
    Need to get 79.2 MB of archives.
    After this operation, 340 MB of additional disk space will be used.

    Fetched 79.2 MB in 20s (3824 kB/s)
    Selecting previously unselected package cmake-data.
    (Reading database ...
    Preparing to unpack .../00-cmake-data_3.7.2-1_all.deb ...
    Unpacking cmake-data (3.7.2-1) ...
    Selecting previously unselected package libarchive13:amd64.
    Preparing to unpack .../01-libarchive13_3.2.2-2+deb9u1_amd64.deb ...
    Unpacking libarchive13:amd64 (3.2.2-2+deb9u1) ...
    Selecting previously unselected package libcurl3:amd64.
    Preparing to unpack .../02-libcurl3_7.52.1-5+deb9u9_amd64.deb ...
    Unpacking libcurl3:amd64 (7.52.1-5+deb9u9) ...
    Selecting previously unselected package libjsoncpp1:amd64.
    Preparing to unpack .../03-libjsoncpp1_1.7.4-3_amd64.deb ...
    Unpacking libjsoncpp1:amd64 (1.7.4-3) ...
    Selecting previously unselected package libuv1:amd64.
    Preparing to unpack .../04-libuv1_1.9.1-3_amd64.deb ...
    Unpacking libuv1:amd64 (1.9.1-3) ...
    Selecting previously unselected package cmake.
    Preparing to unpack .../05-cmake_3.7.2-1_amd64.deb ...
    Unpacking cmake (3.7.2-1) ...
    Selecting previously unselected package bc.
    Preparing to unpack .../06-bc_1.06.95-9+b3_amd64.deb ...
    Unpacking bc (1.06.95-9+b3) ...
    Selecting previously unselected package libjs-jquery.
    Preparing to unpack .../07-libjs-jquery_3.1.1-2+deb9u1_all.deb ...
    Unpacking libjs-jquery (3.1.1-2+deb9u1) ...
    Selecting previously unselected package fish-common.
    Preparing to unpack .../08-fish-common_2.4.0-1_all.deb ...
    Unpacking fish-common (2.4.0-1) ...
    Selecting previously unselected package lynx-common.
    Preparing to unpack .../09-lynx-common_2.8.9dev11-1_all.deb ...
    Unpacking lynx-common (2.8.9dev11-1) ...
    Selecting previously unselected package lynx.
    Preparing to unpack .../10-lynx_2.8.9dev11-1_amd64.deb ...
    Unpacking lynx (2.8.9dev11-1) ...
    Selecting previously unselected package libpcre2-32-0:amd64.
    Preparing to unpack .../11-libpcre2-32-0_10.22-3_amd64.deb ...
    Unpacking libpcre2-32-0:amd64 (10.22-3) ...
    Selecting previously unselected package fish.
    Preparing to unpack .../12-fish_2.4.0-1_amd64.deb ...
    Unpacking fish (2.4.0-1) ...
    Selecting previously unselected package liberror-perl.
    Preparing to unpack .../13-liberror-perl_0.17024-1_all.deb ...
    Unpacking liberror-perl (0.17024-1) ...
    Selecting previously unselected package git-man.
    Preparing to unpack .../14-git-man_1%3a2.11.0-3+deb9u4_all.deb ...
    Unpacking git-man (1:2.11.0-3+deb9u4) ...
    Selecting previously unselected package git.
    Preparing to unpack .../15-git_1%3a2.11.0-3+deb9u4_amd64.deb ...
    Unpacking git (1:2.11.0-3+deb9u4) ...
    Preparing to unpack .../16-vim-tiny_2%3a8.0.0197-4+deb9u3_amd64.deb ...
    Unpacking vim-tiny (2:8.0.0197-4+deb9u3) over (2:8.0.0197-4+deb9u1) ...
    Preparing to unpack .../17-vim-common_2%3a8.0.0197-4+deb9u3_all.deb ...
    Unpacking vim-common (2:8.0.0197-4+deb9u3) over (2:8.0.0197-4+deb9u1) ...
    Selecting previously unselected package binutils.
    Preparing to unpack .../18-binutils_2.28-5_amd64.deb ...
    Unpacking binutils (2.28-5) ...
    Selecting previously unselected package libisl15:amd64.
    Preparing to unpack .../19-libisl15_0.18-1_amd64.deb ...
    Unpacking libisl15:amd64 (0.18-1) ...
    Selecting previously unselected package libmpfr4:amd64.
    Preparing to unpack .../20-libmpfr4_3.1.5-1_amd64.deb ...
    Unpacking libmpfr4:amd64 (3.1.5-1) ...
    Selecting previously unselected package libmpc3:amd64.
    Preparing to unpack .../21-libmpc3_1.0.3-1+b2_amd64.deb ...
    Unpacking libmpc3:amd64 (1.0.3-1+b2) ...
    Selecting previously unselected package cpp-6.
    Preparing to unpack .../22-cpp-6_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking cpp-6 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package cpp.
    Preparing to unpack .../23-cpp_4%3a6.3.0-4_amd64.deb ...
    Unpacking cpp (4:6.3.0-4) ...
    Selecting previously unselected package libcc1-0:amd64.
    Preparing to unpack .../24-libcc1-0_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libcc1-0:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libgomp1:amd64.
    Preparing to unpack .../25-libgomp1_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libgomp1:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libitm1:amd64.
    Preparing to unpack .../26-libitm1_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libitm1:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libatomic1:amd64.
    Preparing to unpack .../27-libatomic1_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libatomic1:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libasan3:amd64.
    Preparing to unpack .../28-libasan3_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libasan3:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package liblsan0:amd64.
    Preparing to unpack .../29-liblsan0_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking liblsan0:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libtsan0:amd64.
    Preparing to unpack .../30-libtsan0_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libtsan0:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libubsan0:amd64.
    Preparing to unpack .../31-libubsan0_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libubsan0:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libcilkrts5:amd64.
    Preparing to unpack .../32-libcilkrts5_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libcilkrts5:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libmpx2:amd64.
    Preparing to unpack .../33-libmpx2_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libmpx2:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libquadmath0:amd64.
    Preparing to unpack .../34-libquadmath0_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libquadmath0:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libgcc-6-dev:amd64.
    Preparing to unpack .../35-libgcc-6-dev_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libgcc-6-dev:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package gcc-6.
    Preparing to unpack .../36-gcc-6_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking gcc-6 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package gcc.
    Preparing to unpack .../37-gcc_4%3a6.3.0-4_amd64.deb ...
    Unpacking gcc (4:6.3.0-4) ...
    Preparing to unpack .../38-libicu57_57.1-6+deb9u3_amd64.deb ...
    Unpacking libicu57:amd64 (57.1-6+deb9u3) over (57.1-6+deb9u2) ...
    Selecting previously unselected package icu-devtools.
    Preparing to unpack .../39-icu-devtools_57.1-6+deb9u3_amd64.deb ...
    Unpacking icu-devtools (57.1-6+deb9u3) ...
    Selecting previously unselected package javascript-common.
    Preparing to unpack .../40-javascript-common_11_all.deb ...
    Unpacking javascript-common (11) ...
    Selecting previously unselected package libc-dev-bin.
    Preparing to unpack .../41-libc-dev-bin_2.24-11+deb9u4_amd64.deb ...
    Unpacking libc-dev-bin (2.24-11+deb9u4) ...
    Selecting previously unselected package linux-libc-dev:amd64.
    Preparing to unpack .../42-linux-libc-dev_4.9.189-3_amd64.deb ...
    Unpacking linux-libc-dev:amd64 (4.9.189-3) ...
    Selecting previously unselected package libc6-dev:amd64.
    Preparing to unpack .../43-libc6-dev_2.24-11+deb9u4_amd64.deb ...
    Unpacking libc6-dev:amd64 (2.24-11+deb9u4) ...
    Selecting previously unselected package libdpkg-perl.
    Preparing to unpack .../44-libdpkg-perl_1.18.25_all.deb ...
    Unpacking libdpkg-perl (1.18.25) ...
    Selecting previously unselected package libfile-fcntllock-perl.
    Preparing to unpack .../45-libfile-fcntllock-perl_0.22-3+b2_amd64.deb ...
    Unpacking libfile-fcntllock-perl (0.22-3+b2) ...
    Selecting previously unselected package libstdc++-6-dev:amd64.
    Preparing to unpack .../46-libstdc++-6-dev_6.3.0-18+deb9u1_amd64.deb ...
    Unpacking libstdc++-6-dev:amd64 (6.3.0-18+deb9u1) ...
    Selecting previously unselected package libicu-dev.
    Preparing to unpack .../47-libicu-dev_57.1-6+deb9u3_amd64.deb ...
    Unpacking libicu-dev (57.1-6+deb9u3) ...
    Selecting previously unselected package liblzma-dev:amd64.
    Preparing to unpack .../48-liblzma-dev_5.2.2-1.2+b1_amd64.deb ...
    Unpacking liblzma-dev:amd64 (5.2.2-1.2+b1) ...
    Selecting previously unselected package libtinfo-dev:amd64.
    Preparing to unpack .../49-libtinfo-dev_6.0+20161126-1+deb9u2_amd64.deb ...
    Unpacking libtinfo-dev:amd64 (6.0+20161126-1+deb9u2) ...
    Selecting previously unselected package libncurses5-dev:amd64.
    Preparing to unpack .../50-libncurses5-dev_6.0+20161126-1+deb9u2_amd64.deb ...
    Unpacking libncurses5-dev:amd64 (6.0+20161126-1+deb9u2) ...
    Selecting previously unselected package libsqlite3-dev:amd64.
    Preparing to unpack .../51-libsqlite3-dev_3.16.2-5+deb9u1_amd64.deb ...
    Unpacking libsqlite3-dev:amd64 (3.16.2-5+deb9u1) ...
    Selecting previously unselected package libxml2-dev:amd64.
    Preparing to unpack .../52-libxml2-dev_2.9.4+dfsg1-2.2+deb9u2_amd64.deb ...
    Unpacking libxml2-dev:amd64 (2.9.4+dfsg1-2.2+deb9u2) ...
    Selecting previously unselected package make.
    Preparing to unpack .../53-make_4.1-9.1_amd64.deb ...
    Unpacking make (4.1-9.1) ...
    Selecting previously unselected package manpages-dev.
    Preparing to unpack .../54-manpages-dev_4.10-2_all.deb ...
    Unpacking manpages-dev (4.10-2) ...
    Selecting previously unselected package ninja-build.
    Preparing to unpack .../55-ninja-build_1.7.2-1_amd64.deb ...
    Unpacking ninja-build (1.7.2-1) ...
    Selecting previously unselected package patch.
    Preparing to unpack .../56-patch_2.7.5-1+deb9u2_amd64.deb ...
    Unpacking patch (2.7.5-1+deb9u2) ...
    Selecting previously unselected package pkg-config.
    Preparing to unpack .../57-pkg-config_0.29-4+b1_amd64.deb ...
    Unpacking pkg-config (0.29-4+b1) ...
    Selecting previously unselected package vim-runtime.
    Preparing to unpack .../58-vim-runtime_2%3a8.0.0197-4+deb9u3_all.deb ...
    Adding 'diversion of /usr/share/vim/vim80/doc/help.txt to /usr/share/vim/vim80/doc/help.txt.vim-ti                         ny by vim-runtime'
    Adding 'diversion of /usr/share/vim/vim80/doc/tags to /usr/share/vim/vim80/doc/tags.vim-tiny by vi                         m-runtime'
    Unpacking vim-runtime (2:8.0.0197-4+deb9u3) ...
    Selecting previously unselected package vim.
    Preparing to unpack .../59-vim_2%3a8.0.0197-4+deb9u3_amd64.deb ...
    Unpacking vim (2:8.0.0197-4+deb9u3) ...
    Selecting previously unselected package xsel.
    Preparing to unpack .../60-xsel_1.2.0-2+b1_amd64.deb ...
    Unpacking xsel (1.2.0-2+b1) ...
    Selecting previously unselected package zlib1g-dev:amd64.
    Preparing to unpack .../61-zlib1g-dev_1%3a1.2.8.dfsg-5_amd64.deb ...
    Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-5) ...
    Selecting previously unselected package uuid-dev:amd64.
    Preparing to unpack .../62-uuid-dev_2.29.2-1+deb9u1_amd64.deb ...
    Unpacking uuid-dev:amd64 (2.29.2-1+deb9u1) ...
    Setting up libquadmath0:amd64 (6.3.0-18+deb9u1) ...
    Setting up libgomp1:amd64 (6.3.0-18+deb9u1) ...
    Setting up libjs-jquery (3.1.1-2+deb9u1) ...
    Setting up libatomic1:amd64 (6.3.0-18+deb9u1) ...
    Setting up git-man (1:2.11.0-3+deb9u4) ...
    Setting up libcc1-0:amd64 (6.3.0-18+deb9u1) ...
    Setting up make (4.1-9.1) ...
    Setting up libasan3:amd64 (6.3.0-18+deb9u1) ...
    Processing triggers for mime-support (3.60) ...
    Setting up liberror-perl (0.17024-1) ...
    Setting up libcurl3:amd64 (7.52.1-5+deb9u9) ...
    Setting up libarchive13:amd64 (3.2.2-2+deb9u1) ...
    Setting up libcilkrts5:amd64 (6.3.0-18+deb9u1) ...
    Setting up libuv1:amd64 (1.9.1-3) ...
    Setting up libubsan0:amd64 (6.3.0-18+deb9u1) ...
    Setting up libtsan0:amd64 (6.3.0-18+deb9u1) ...
    Setting up linux-libc-dev:amd64 (4.9.189-3) ...
    Setting up libdpkg-perl (1.18.25) ...
    Setting up libtinfo-dev:amd64 (6.0+20161126-1+deb9u2) ...
    Setting up cmake-data (3.7.2-1) ...
    Setting up libicu57:amd64 (57.1-6+deb9u3) ...
    Setting up liblsan0:amd64 (6.3.0-18+deb9u1) ...
    Setting up libfile-fcntllock-perl (0.22-3+b2) ...
    Setting up pkg-config (0.29-4+b1) ...
    Setting up libmpx2:amd64 (6.3.0-18+deb9u1) ...
    Setting up libisl15:amd64 (0.18-1) ...
    Setting up patch (2.7.5-1+deb9u2) ...
    Processing triggers for libc-bin (2.24-11+deb9u4) ...
    Setting up vim-common (2:8.0.0197-4+deb9u3) ...
    Setting up libmpfr4:amd64 (3.1.5-1) ...
    Processing triggers for man-db (<IP_ADDRESS>-2) ...
    Setting up xsel (1.2.0-2+b1) ...
    Setting up vim-runtime (2:8.0.0197-4+deb9u3) ...
    Setting up fish-common (2.4.0-1) ...
    Setting up libmpc3:amd64 (1.0.3-1+b2) ...
    Setting up binutils (2.28-5) ...
    Setting up cpp-6 (6.3.0-18+deb9u1) ...
    Setting up icu-devtools (57.1-6+deb9u3) ...
    Setting up libc-dev-bin (2.24-11+deb9u4) ...
    Setting up liblzma-dev:amd64 (5.2.2-1.2+b1) ...
    Setting up javascript-common (11) ...
    Setting up bc (1.06.95-9+b3) ...
    Setting up libpcre2-32-0:amd64 (10.22-3) ...
    Setting up lynx-common (2.8.9dev11-1) ...
    Setting up manpages-dev (4.10-2) ...
    Setting up libc6-dev:amd64 (2.24-11+deb9u4) ...
    Setting up ninja-build (1.7.2-1) ...
    Setting up git (1:2.11.0-3+deb9u4) ...
    Setting up libitm1:amd64 (6.3.0-18+deb9u1) ...
    Setting up lynx (2.8.9dev11-1) ...
    update-alternatives: using /usr/bin/lynx to provide /usr/bin/www-browser (www-browser) in auto mod                         e
    Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-5) ...
    Setting up libjsoncpp1:amd64 (1.7.4-3) ...
    Setting up vim-tiny (2:8.0.0197-4+deb9u3) ...
    Setting up cpp (4:6.3.0-4) ...
    Setting up libgcc-6-dev:amd64 (6.3.0-18+deb9u1) ...
    Setting up libstdc++-6-dev:amd64 (6.3.0-18+deb9u1) ...
    Setting up fish (2.4.0-1) ...
    Setting up libsqlite3-dev:amd64 (3.16.2-5+deb9u1) ...
    Setting up vim (2:8.0.0197-4+deb9u3) ...
    update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vim (vim) in auto mode
    update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vimdiff (vimdiff) in auto mode
    update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/rvim (rvim) in auto mode
    update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/rview (rview) in auto mode
    update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vi (vi) in auto mode
    update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/view (view) in auto mode
    update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/ex (ex) in auto mode
    Setting up uuid-dev:amd64 (2.29.2-1+deb9u1) ...
    Setting up libicu-dev (57.1-6+deb9u3) ...
    Setting up gcc-6 (6.3.0-18+deb9u1) ...
    Setting up libxml2-dev:amd64 (2.9.4+dfsg1-2.2+deb9u2) ...
    Setting up libncurses5-dev:amd64 (6.0+20161126-1+deb9u2) ...
    Setting up cmake (3.7.2-1) ...
    Setting up gcc (4:6.3.0-4) ...
     Any error output should be
visible above. Please fix these errors and try again.

Last time I run tests on Debian several weeks ago, there could be a breaking change since then because we do not run Debian as part of our CI process.
Did you try this setup with Ubuntu? It is being CI-ed heavily, so I would expect it to work.

That's not working for me, because I'm behind a proxy, and I can't figure out how to resolve this error. I was able to convert all the HTTPS calls to HTTP, but this remains.
fatal: [ubuntu18]: FAILED! => changed=false
  msg: 'Failed to connect to github.com at port 443: [Errno 110] Connection timed out'
  status: -1
  url: http://github.com/Kitware/CMake/releases/download/v3.12.4/cmake-3.12.4-Linux-x86_64.sh

Unfortunately, I do not have experience working with Ansible and proxies. Maybe this document (or any other) will help https://docs.ansible.com/ansible/latest/user_guide/playbooks_environment.html ?

I don't think this one is actionable, so I'm closing it.

I don't think this one is actionable, so I'm closing it.


[Statistics/Overall Season/UI] Use the Service Functions to Dynamically Update the Aggregated Seasonal Stats

Feature Request

As a user uses OpenTracks to collect more data, the stats that are calculated via the service functions change over time. When the user goes to check their All-Time stats, this fact is an expectation by the user and so should be represented on the aggregated seasonal stats page.

Proposed Solution

When using the callback functions to render the page, the service functions developed should be called to get the data to then pas it along to the page.

Alternatives

Create some variables that store the calculated values and are simply reused onto the page when it must be rendered. This may allow for the numbers to be calculated after the completion of a new run but this form of eager loading may cause increased complexity & effort and could waste some computational time as the user may/may not actually view the all-time stats.

Completeness Requirements

The service functions meant to calculate the aggregated seasonal stats are called when rendering the page
The rendered numbers are accurate to the calculation
When adding in new tracks, the stats are updated and changed

Additional context
#7

Since the other groups have yet to establish what kinds of functions and data are available to us, mockup data used here to illustrate the idea for overall stats. I will close down this issue and any further work should be carried out onto a new issue once all the details have been ironed out.


Appointment end date can be earlier than start date

See pic
Command was: appointment add --p 2 --s 2023-01-03 1120  --e 2023-01-02 1130 --v Mordena

@nusE0726844 do u want to take a look @ this?


Provide standalone binary download

Is it possible to install this with cargo?

Perhaps not cargo, but we have been thinking of having a plain binary download. Could you explain your usecase?

I don’t like using node. It’s complicated, I don’t fully understand it, and this is the only reason I have to use it on my project.

Hi there, would this be up for grabs?

I'm going to close this for now—we're not likely to do it anytime soon, and it's at odds with the current development focus of Wrangler. Additionally, with the recent inclusion of the open source workerd in the Wrangler package, the download size of a standalone binary would likely be prohibitive


SDL_Log() not working

SDL_Log() could be used for rudimentary debugging via EKA2L1.
A respective implementation is pending.
This can be used as a reference:
https://github.com/ngagesdk/dbgprint

SDL_LogSetOutputFunction() can be used to replace the default output function.


Could 'x should be < 250' be made to work when 'x' is Double?

This is a small thing, but I'm reporting it for opinions since the compiler errors don't really help one much if facing this.
My code (using ScalaTest 2.2.1, FlatSpec and Matchers):
...
val avg: Double = (times_ms.sum : Double) / times_ms.size
avg should be < 250.0     // ScalaTest note: needs '.0', otherwise does not find right matche
...

I first had just 250 which gives the following compiler errors:
[error] /Users/...: overloaded method value should with alternatives:
[error]   (endWithWord: org.scalatest.words.EndWithWord)(implicit ev: <:<[Double,String])RestAPITest.this.ResultOfEndWithWordForString
[error]   (startWithWord: org.scalatest.words.StartWithWord)(implicit ev: <:<[Double,String])RestAPITest.this.ResultOfStartWithWordForString
[error]   (includeWord: org.scalatest.words.IncludeWord)(implicit ev: <:<[Double,String])RestAPITest.this.ResultOfIncludeWordForString
[error]   (notExist: org.scalatest.words.ResultOfNotExist)(implicit existence: org.scalatest.enablers.Existence[Double])Unit
[error]   (existWord: org.scalatest.words.ExistWord)(implicit existence: org.scalatest.enablers.Existence[Double])Unit
[error]   (containWord: org.scalatest.words.ContainWord)org.scalatest.words.ResultOfContainWord[Double]
[error]   (haveWord: org.scalatest.words.HaveWord)RestAPITest.this.ResultOfHaveWordForExtent[Double]
[error]   (beWord: org.scalatest.words.BeWord)RestAPITest.this.ResultOfBeWordForAny[Double]
[error]   (inv: org.scalactic.TripleEqualsSupport.TripleEqualsInvocationOnSpread[Double])(implicit ev: Numeric[Double])Unit
[error]   [U](inv: org.scalactic.TripleEqualsSupport.TripleEqualsInvocation[U])(implicit constraint: org.scalactic.Constraint[Double,U])Unit
[error]   (notWord: org.scalatest.words.NotWord)org.scalatest.words.ResultOfNotWordForAny[Double]
[error]   [TYPECLASS1[], TYPECLASS2[]](rightMatcherFactory2: org.scalatest.matchers.MatcherFactory2[Double,TYPECLASS1,TYPECLASS2])(implicit typeClass1: TYPECLASS1[Double], implicit typeClass2: TYPECLASS2[Double])Unit
[error]   [TYPECLASS1[_]](rightMatcherFactory1: org.scalatest.matchers.MatcherFactory1[Double,TYPECLASS1])(implicit typeClass1: TYPECLASS1[Double])Unit
[error]   (rightMatcherX1: org.scalatest.matchers.Matcher[Double])Unit
[error]  cannot be applied to (org.scalatest.matchers.Matcher[Int])
[error]       avg should be < 250
[error]           ^
[error] one error found
That's a pretty long error for essentially "hey, we cannot convert your integer to a double".
If you deem this use is fairly common (I think it is), and if you know a way to make it just work, it'd be delightful. :)

I think this will be useful, and it is something we will look at in 3.0 once we have the cooperative equality classes in.

Does closing this mean it's "in" in 3.0 SNAP versions?
Also, where could I find a summary of 3.0 features? Google gave https://skillsmatter.com/skillscasts/6021-scalatest-and-scalactic-3-0 and https://gist.github.com/bvenners/f038d946adab18b9cb78
Would love to see how 3.0 compatible my test suites are.


xPowerShellExecutionPolicy: This resource is missing an integration test

The resource xPowerShellExecutionPolicy is missing an integration test.

This was added in PR #15


Update from elastic search to open search my query don'work

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.1.0
What operating system are you using?
windows 10
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
I have update from elastic search to open search
Describe the bug
After update from elastic search to open search , all my query of appsync don't work , they retrive only old data from s3 and dynamo db.
opensearch version OpenSearch_2_7_R20230706
type FileManager {
id: ID!
key: String!
category: String!
subCategory: String!
elab: Int!
state: Int!
consulenza: Boolean
value: Float
durata: Int
rata: String
npagine: String
uploadedBy: String
quietanza: String
createdAt: AWSDateTime!
updatedAt: AWSDateTime!
}
Expected behavior
Query retrive all data
Reproduction steps
nothing
Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @jcacu, Thank you for bringing this to our attention. This problem is a duplicate of issue #1297. Please consult the comments in #1297for a workaround and any upcoming developments.


coco.npy file location

I am interested in your repo :)
Is there a J_regressor_coco.npy file uploaded?
I can't find the file.

Hi :)
It's in ./data/COCO/J_regressor_coco.npy

Thanks :)


buildbox-casd error "Insufficient storage quota", Not propagating to frontend properly

See original issue on GitLab
In GitLab by [Gitlab user @DouglasWinship] on Jul 2, 2020, 17:07
Summary
At least two CI build jobs have failed, on the libreML project, due to buildbox-casd failures. The logs show an OutOfSpaceException.
If the buildstream job genuinely did use up too much storage, then the expected behaviour is a better error message and a more graceful response. It's also possible that buildbox-casd itself caused the issue, in which case the expected behaviour is for the process not to fail at all, and the buildstream job should continue.
This issue is tracked on the buildbox-casd repo:
https://gitlab.com/BuildGrid/buildbox/buildbox-casd/-/issues/75

In GitLab by [Gitlab user @DouglasWinship] on Jul 2, 2020, 17:09
changed the description

In GitLab by [Gitlab user @DouglasWinship] on Jul 2, 2020, 17:09
changed the description

In GitLab by [Gitlab user @willsalmon] on Jul 2, 2020, 17:13
changed title from {-errMsg "Insufficient storage quota", causing CI build jobs to fail-} to {+buildbox-casd error "Insufficient storage quota", Not propagating to frontend properly+}

In GitLab by [Gitlab user @willsalmon] on Jul 2, 2020, 17:13
changed title from {-errMsg "Insufficient storage quota", causing CI build jobs to fail-} to {+buildbox-casd error "Insufficient storage quota", Not propagating to frontend properly+}


Write requests to deleted objects and deleted parents

Writes to objects with deleted parents are supported to ease writes by different clients. But why writing allowed to deleted objects?

Also, if an object is moved to a deleted parent (which is possible with a manual request), a syncing client has no way to notice it. It is not reported in the regular listing (because it filters out deleted parents) or in the deleted list (because the parent is again filtered out, and also the object is not itself deleted).

Moved to library project.


Add positional embeddings

Currently, the only positional embeddings that can be handled are those that take place before passing embeddings to the transformer blocks. It would be nice to have positional embeddings that can be utilized within the transformer blocks.
Need to look through positional embedding papers to see which ones are compatible with Infini-Transformer.

Added basic RoPE class (https://arxiv.org/abs/2104.09864). It still needs to be modified to handle MoD and integrated into CompressiveMemory.
Once that's done, I'll implement YaRN (https://arxiv.org/abs/2309.00071). After that, I'll add in PoSE (https://arxiv.org/abs/2309.10400).
If anyone knows of other techniques for positional embedding that can be added, feel free to link me to the papers.

Just modified the RoPE class to be compatible with Mixture-of-Depths and Infini-Attention. Still need to refactor some before moving on because I mistakenly call it in the wrong place, causing it to be very memory-inefficient.

RoPE has been fully implemented.

YaRN has been fully implemented.

Re-read the PoSE paper and realized it either doesn't work with infini-attention or I had some clever idea to make it work that I've since forgotten. Either way, I'm closing this issue out. If I figure out a way to add PoSE, I'll re-open it.


SOLR-15501: GCSBackupRepository operations without credentials

https://issues.apache.org/jira/browse/SOLR-15501

Description
Given that access to GCS buckets from within Google Cloud Platform can be configured based on roles and not on passwords, it is now possible to use GCSBackupRepository plugin to work also in case when no credentials are given.
This works 'automatically' given that google libraries are used and they support this 'out of the box'
Solution
Simply allow no credentials to be given.
Tests
A test to run 'without credentials' is added.
I have also built this and manually tested within GCP environment a BACKUP and RESTORE calls (after obviously configuring the plugin) and they do work as expected.
Checklist
Please review the following and check all that apply:

[X] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[X] I have created a Jira issue and added the issue ID to my pull request title.
[X] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[X] I have developed this patch against the main branch.
[X] I have run ./gradlew check.
[X] I have added tests for my changes.
[X] I have added documentation for the Reference Guide

a 'branch 8.11' commit is here: https://github.com/apache/lucene-solr/pull/2634

CC: @gerlowskija  (as a Ticket assignee)

Hey guys, sorry for the delay - the code here looks great.  I'm going to test this out as a part of my own workflow in GKE and then I'll merge.


Change from 24 hour time to AM/PM

I know this is kinda small, but I was wondering if there is a way for vim-auto-save to tell you what time it auto-saved in AM/PM time.

Hello, @pavanscoding! I no longer maintain this plugin. Sorry!
You're right that AM/PM time feature seems to be a very small improvement. You can try to implement it yourself. It won't be hard because the source code of the plugin is very small and simple. You will need to learn Vim scripting language a little of course. Use Learn Vimscript the Hard Way or any other book from internet.
Good luck and best wishes!

Hi @pavanscoding 👋🏾
Ideally, you'd want to change "%H:%M:%S" to "%I:%M %P" in the line below
https://github.com/907th/vim-auto-save/blob/2e3e54ea4c0fc946c21b0a4ee4c1c295ba736ee8/plugin/AutoSave.vim#L93


Regenerate gameservices client

This PR was generated using Autosynth. :rainbow:
Here's the log from Synthtool:
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/google-cloud-clients/google-cloud-gameservices/synth.py.
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:6929f343c400122d85818195b18613330a12a014bffc1e08499550d40571479d
Status: Image is up to date for googleapis/artman:latest
synthtool > Cloning googleapis-private.
synthtool > Running generator for google/cloud/gaming/artman_gameservices_v1alpha.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis-private/artman-genfiles/java.
synthtool > Running java formatter on 46 files
synthtool > Running java formatter on 5 files
synthtool > Running java formatter on 108 files
synthtool > Cleaned up 1 temporary directories.
synthtool > Wrote metadata to synth.metadata.

Combined into a single pull request #6022


[kegmgr] KMAC side load timing diagram

@tjaychen
As discussed, it's helpful to have a timing diagram for KMAC side load interface (kmac_data_i/o and kmac_key_o) in the keymgr spec.

added through #4624
let me know if it's enough info and we can close this one.

added through #4624
let me know if it's enough info and we can close this one.

Thanks Tim. Closing this.


Dev/tsweeney/docfix/2

Second chunk of manpages.  I think they're all up to current changes, but several need more/better examples.  I've also included a new common routine that will check to see if a string is a prefix in one or more strings within a slice.  My thinking is we can use that for the delete (or other commands) to do short name checking.  It's currently not as efficient as I'd like, but thought I'd get the general concept approved before trying to make the search faster.  It is not currently being called by any other function.

bot, add author to whitelist

You need to rebase your patches and merge them together, then do a force push.
git rebase -i origin
git push twsweeney --force

You meed to update the Makefile to install convert and install these man pages.

Checking with Nalin about the test errors.

LGTM now after tweaking per Nalin's suggestions.

@rh-atomic-bot r+ b179ead

@rh-atomic-bot r+ b179ead

@rh-atomic-bot retry

@rh-atomic-bot r+ b179ead947c7a07e97ff3ac0ea2dc049c64cccd2

@rh-atomic-bot retry

@rhatdan FWIW, Nalin and I were both not able to get the homu test to re-run last week.

@rh-atomic-bot retry


time zone command

I was wanting to know if it would be possible to add a command that tells a user what time it is in a time zone he requests like ~time pst

no


Fix VocPrez queries not working on GraphDB

It looks like the SPARQL queries that are currently used for VocPrez to retrieve the top concepts and narrower concepts do not work in GraphDB.
I've re-written the queries to ensure that they now work with both Fuseki and GraphDB.
This bug was found by Engineers Australia where they were setting up an instance of VocPrez. Inform them once this fix has made it into a release.

Discussed in person - approved, will not test thoroughly as changes are subsumed in new version w/ rdframe.


fix: links in header when on CoC

Fix the links on the header when we are not on the root page

Thank you! My bad 😅

That was fast 😆
I love the design and simplicity of the website

Thank you! That was my intention building the website. I was afraid that people thought that the simplicity wasn't intentional 😬

It has everything it needs 👌


Evidence item revisions not working

I made some dropdown changes and edited the summary for a single evidence statement for BRAF V600E. When I go to Evidence Talk the revision is in the Log tab but nothing appears in the Revisions tab. My edits to the summary text are there. Drug ID which was N/A and I didn't change appears as "[{"id":1,"name":"N/A","pubchem_id":null}]". Maybe that is related to the issue.

Actually, I see now that all evidence items have the first "Revision Applied" by admin so my revision is not being listed in either the Log or Revision tab. But the displayed text in the Evidence Talk page does reflect some of the changes I proposed.

Playing around more. It looks like this is only occurring when I use the "Apply" option rather then "Submit Revision for Review". These should still be logged and appear as revisions. They should just go directly to an 'applied' status. The issue with drug name being displayed weird on the Talk->Revisions page persists no matter how the revision is made.

Ah, yeah - the admin apply function works differently than the normal user's submit suggested revision. The admin apply just directly updates the entity's record in the db, bypassing the whole revisions workflow, so no revision is generated. I agree this is confusing and either we should shoehorn it into the revisions flow to generate a revision event or make it clear in the UI what is going on.
I will look into the drug display bug. The client gets an array of drug names which I transform into a list string, looks like it's getting skipped somewhere.

I created a new question issue on civic-server (genome/civic-server#52) to address the current somewhat confusing admin apply action.


Nested struct weirdness in travesty

In travesty, this sort of pattern is seen sometimes.
struct v3_plugin_base {
	struct v3_funknown;
	v3_result (V3_API* initialize)(void* self, struct v3_funknown** context);
};

The declaration of the inner struct is without effect on the structure contents.
It hints at the inheritance, which is OK I guess, but has an ill effect as well: it creates an inner struct v3_plugin_base::v3_funknown which collides with the top-level v3_funknown declaration.
The function pointer initialize picks up the inner declaration of v3_funknown for its argument, which creates a problem when one tries to interact with the API.
The problem would be resolved by commenting all of the inner structs.

The API is meant to be C-compatible first, then helpers added for C++ compat as needed.
Because of differences between C and C++, that struct v3_funknown does the inheritance of methods in C, but nothing in C++.
For now I simply declare C++ friendly versions when needed, such as in https://github.com/DISTRHO/DPF/blob/develop/distrho/src/travesty/audio_processor.h#L244

This means, so these structs get different layout depending from which language they are included?
Surely then, it must be ok to get rid of the struct statement by #ifndef __cplusplus directives.
Also for info, I was not using any of these c++ helpers, because of preference the conciseness of c-style struct initializer.
Hence, I was building my v-tables on the basis of these "non-inheriting" structures.

This means, so these structs get different layout depending from which language they are included?
Surely then, it must be ok to get rid of the struct statement by #ifndef __cplusplus directives.

What do you mean layout changes?
It looks weird for sure and can lead to confusion, plus v3_funknown becomes a type on a bunch of other structs.
I have cleaned it up a bit in 48fc694c31f709d4a46f727795917fd3371eb0da

What do you mean layout changes?

I've pushed the code in progress, that can give you an idea.
https://github.com/jpcima/claptrap/blob/master/sources/v3/v3_component.hpp

I feel like that gets the API in a way that is too similar to the original, something I am purposefully trying to avoid.
Feel free to report issues with the core headers, but I prefer to keep my distance from that clap c++ higher level stuff.
I do know quite a few v3_cpp_obj specializations are missing, but most are related to the host side.
Whenever I start implement this in Carla I will add those, but most are not needed for now.


multi-occur is not very comfortable with selectrum

If I am using selectrum-mode and call M-x multi-occur it asks me to select multiple buffers and finish with "RET". Since selectrum already preselects the first choice, I have to move the cursor up to finish, which is not very comfortable. Probably selectrum should not preselect in that case? Furthermore after selecting one buffer it should not appear again in the list of choices.
I am not sure if something like this could be fixed in selectrum, since it is a special case. Maybe some custom wrapper could be written around multi-occur? Maybe someone had the same issue and there is already a good solution for the problem?

Thanks for your input! I agree that the problem is more with the command itself than with selectrum. This is a great candidate for completing-read-multiple:
(defun my-multi-occur ()
  (interactive)
  (let ((bufs
         (mapcar #'get-buffer
                 (completing-read-multiple "Buffer: "
                                           #'internal-complete-buffer))))
    (apply #'multi-occur (cons bufs (occur-read-primary-args)))))

To exit with a single buffer you exit with RET, to select multiple add more with TAB until you want to exit with RET. If you pressed TAB to often just delete the final comma and afterwards exit with RET.

@clemera Thank you for your response! I wonder - why is multi-occur not using completing-read-multiple already internally? Should this potentially be fixed in emacs upstream? As far as I underatnd completing-read-multiple is part of the Emacs api, which is enhanced by selectrum?

@clemera After looking at multi-occur, I think it should just be replaced by the following:
(defun multi-occur (bufs regexp &optional nlines)
  (interactive (cons
                (mapcar #'get-buffer
                        (completing-read-multiple "Buffer: "
                                                  #'internal-complete-buffer))
                (occur-read-primary-args)))
  (occur-1 regexp nlines bufs))

or alternatively
(defun my-multi-occur (bufs regexp &optional nlines)
  (interactive (cons
                (mapcar #'get-buffer
                        (completing-read-multiple "Buffer: "
                                                  #'internal-complete-buffer))
                (occur-read-primary-args)))
  (multi-occur regexp nlines bufs))

This should probably go to the wiki or we should consider upstreaming the improved multi-occur?

Yes, please add it to the wiki. M-x report-emacs-bug is also a good idea, though looking at the ido variables I guess it needs to be updated in a way that still supports calling it with ido and I think it doesn't support completing-read-multiple but not sure about that.

@clemera Thank you - I will add this to the wiki for now! Regarding upstreaming - I will look into this when I have time, but I cannot make any promises here.

Great, thanks!

Just in case you didn't know, you can also use selectrum-submit-exact-input (bound by default to C-j in the minibuffer) to exit with the empty string, rather than using the up arrow to select the prompt area and pressing RET. This might be more convenient for dealing with situations like these.

Any conclusions if this should be reported as a bug in Emacs that multi-occur doesn't use completing-read-multiple?


Conversion to data.frame error

There are several functions that send me an error when I try to convert them to data.frame (using sapply(RObject, as.data.frame). Here's a link to one example, in case it helps. The issue occurs when I'm trying to return a page of resources, and the error is "arguments imply differing number of rows: 1, 0". My understanding is that this indicates that the lists being passed into the data.frame are of different lengths, but it's stumping me because from what I'm able to tell, that's not the case with list of lists that I'm providing...
If you have any suggestions of things to try, let me know. I'm still working on the tests (i.e. test_that) for the functions that are working/not throwing errors.

You're almost certainly correct about what you think the error is. I would
advise you to very carefully take a look at the str of the input data...
On Wed, 23 Oct 2019 at 11:11, Austin Koontz<EMAIL_ADDRESS>wrote:

There are several functions that send me an error when I try to convert
them to data.frame (using sapply(RObject, as.data.frame). Here's
https://github.com/pearselab/Symbiota2/blob/4646c2ba27996be1e07053c98b8755106d8f9138/R/Symbiota2.R#L2610
a link to one example, in case it helps. The issue occurs when I'm trying
to return a page of resources, and the error is "arguments imply
differing number of rows: 1, 0". My understanding is that this indicates
that the lists being passed into the data.frame are of different lengths,
but it's stumping me because from what I'm able to tell, that's not the
case with list of lists that I'm providing...
If you have any suggestions of things to try, let me know. I'm still
working on the tests (i.e. test_that) for the functions that are
working/not throwing errors.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pearselab/Symbiota2/issues/2?email_source=notifications&email_token=AAJNYUTXDKUPGLK4M2LF2J3QQCAUVA5CNFSM4JEE5YYKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HT4IJZQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJNYUUYEF35XBB2R3TK623QQCAUVANCNFSM4JEE5YYA
.

Do that for now.
On Tue, 29 Oct 2019 at 11:00, Austin Koontz<EMAIL_ADDRESS>wrote:

You're right: examining this more closely, I found the (sub)lists that are
of varying lengths. Of course, the question now is what I should do about
it...my thinking is to instead return a list rather than a data.frame,
the downside being that this makes the returns structurally inconsistent
between functions. But I don't see an alternative with data.frame, so
that's my plan going ahead.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pearselab/Symbiota2/issues/2?email_source=notifications&email_token=AAJNYUUXH7VAX6FXX34RCLLQRBT2BA5CNFSM4JEE5YYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECRJMWQ#issuecomment-547526234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJNYURKGRPS5MXCH5JCZ53QRBT2BANCNFSM4JEE5YYA
.


envision-unwrapped: 1.1.1 -> 2.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for envision-unwrapped is: UI for building, configuring and running Monado, the open source OpenXR runtime
meta.homepage for envision-unwrapped is: https://gitlab.com/gabmus/envision
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.1 with grep in /nix/store/m4gdhd2jyk21rf75962mdyapdwcylqwr-envision-unwrapped-2.0.1
found 2.0.1 in filename of file in /nix/store/m4gdhd2jyk21rf75962mdyapdwcylqwr-envision-unwrapped-2.0.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

envision
envision-unwrapped

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/m4gdhd2jyk21rf75962mdyapdwcylqwr-envision-unwrapped-2.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A envision-unwrapped https://github.com/r-ryantm/nixpkgs/archive/c7361140e847588ba2e5c0b99012a38b98b260d2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c7361140e847588ba2e5c0b99012a38b98b260d2#envision-unwrapped

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/m4gdhd2jyk21rf75962mdyapdwcylqwr-envision-unwrapped-2.0.1
ls -la /nix/store/m4gdhd2jyk21rf75962mdyapdwcylqwr-envision-unwrapped-2.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 2 packages built:

envision
envision-unwrapped

Maintainer pings
cc @Pandapip1 @Scrumplex for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Other than an amusingly large cursor on KDE plasma, LGTM!

@NixOS/nixpkgs-merge-bot merge


Tab Labels are/really/quite/long

I'd expect the tab to just have the basename but it seems to include the entire path.

Closing as a duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/952


Revert "Uplift CAPI to v1.9.0-beta.0"

/label acknowledge-critical-fixes-only
(not used anywhere, so safe to land)
/lgtm