Cloud Spanner throw Auth error:Error: read ECONNRESET intermittently

I have a cloud function deployed on GCP which is triggered by Cloud Pub/Sub topic. It connects to cloud spanner to insert the pub/sub event data. It is a high volume pub/sub topic and make simultaneous insert requests in different cloud spanner table. However, it keep giving below errors intermittently. Application Default Credentials are used to do authentication of Cloud Spanner.
ERROR: { Error: Getting metadata from plugin failed with error: read ECONNRESET at /user_code/node_modules/@google-cloud/spanner/node_modules/grpc/src/client.js:554:15 code: 16, metadata: Metadata { _internal_repr: {} }, note: 'Exception occurred in retry method that was not classified as transient' }
Below are the dependencies in package.json
 "dependencies": {
      "safe-buffer": "5.1.1",
      "@google-cloud/spanner": "1.0.3",
      "google-gax": "^0.14.5"
}

Environment details

Node.js version:  v8.5.0
npm version: 5.3.0
@google-cloud/spanner version:  1.0.3

It sounds like you might need to write some retry logic around the code that's causing problems. But to be sure there's not anything we can do, can you show the code that calls the method which is returning the error?

But this does not look like an error that users should be seeing. We do not want users to be retrying operations. If the error is retryable, then the library should retry it.

@manasi99 could you put together a minimal amount of code that reproduces this issue for us? That should help us resolve this issue for you quickly.

@stephenplusplus: This is the simple version of actual code where the error is caught in catch block:
const Spanner = require('@google-cloud/spanner');

const spannerClient = new Spanner({
	projectId: config.PROJECT_ID
});

const spannerInstance = spannerClient.instance(config.INSTANCE_ID);

const spannerDatabase = spannerInstance.database(config.DATABASE_ID);

exports.upsertRows = function(tableName, rows) {
return new Promise((resolve, reject) => {
	try {
		const spannerTable = spannerDatabase.table(tableName);
		spannerTable.upsert(rows)
			.then(() => {
				console.log('Upserted data.');
				resolve(true);
			})
			.catch(err => {
				console.error(`Upsert `, err);
				reject(err);
			});
		});
	} catch (err) {
		console.error(`upsertRows `, err);
		reject(err);
	}
};

This has been addressed by a dependency, google-auth-library: https://github.com/google/google-auth-library-nodejs/issues/283. It won't be pulled in automatically, however, we are still determining our game plan to get it out (https://github.com/stephenplusplus/google-auto-auth/issues/39).
I'll mark this as blocked, but hopefully not for long.

We are also seeing these "Auth error:Error: read ECONNRESET" errors in our Cloud Function environment which utilizes Spanner. Since our setup is too complex we were running different narrowed down versions of our code and trying this patch to understand if it is caused by something on our part or a more general Cloud issue. Now that we noticed this issue, at least let me show some of our logs. All of the below logs belong to the same function execution_id but we have a similar pattern in many other calls:
10:20:48.771 Function execution started
10:20:48.875 {... "runId":"SygFY--vIM", "respCode":200, "ALL":98....}
10:20:48.875 Function execution took 104 ms, finished with status code: 200
11:10:28.435 Auth error:Error: read ECONNRESET
11:10:28.734 Auth error:Error: read ECONNRESET
11:10:28.834 Auth error:Error: read ECONNRESET
11:10:28.834 Auth error:Error: read ECONNRESET
11:10:28.934 Auth error:Error: read ECONNRESET
11:10:35.635 Auth error:Error: read ECONNRESET
11:10:35.636 Auth error:Error: read ECONNRESET
11:10:39.034 Unhandled rejection
11:10:39.134 Error: Getting metadata from plugin failed with error: read ECONNRESET
    at /user_code/node_modules/grpc/src/client.js:554:15
11:10:42.035 [runId: S1SwZWv8M] Unhandled promise rejection: 'Error: Getting metadata from plugin failed with error: read ECONNRESET'

What is interesting is that we are getting these Auth errors 30 minutes after the original request is already completed successfully. Although console.log reports them with the same function execution_id, our own corresponding runId (on 2nd and last logs) shows that the error was logged while another request was handled. @stephenplusplus, do you think we have the same issue discussed here or shall we continue digging in our code? Thanks.

Thanks. We'll test it immediately.


Translation support for Site Map, mundo

Requires https://github.com/parameter1/base-cms/pull/497 and a dependency upgrade

 Mundo site translations needed


Move @types/sortablejs to dependencies

Issue: https://github.com/Nerimity/solid-sortablejs/pull/2#issuecomment-1839366493
Solution: https://stackoverflow.com/questions/45176661/how-do-i-decide-whether-types-goes-into-dependencies-or-devdependencies
Test:
pnpm add github:tennox/solid-sortablejs

Oh interesting, thanks


Suggestion: Night mode

Thanks to your efforts fixing my earlier issue (can't find it now) with high resource usage, I've started to use classeur regularly for writing posts for my blog, switching over from Stackedit. It's been a great experience so far (love the side by side preview, although I can't figure out what "Zen Mode" does).
When I take too long over writing a blog post, since I've got natural light at the moment due to it being summer up here in the north, the sky has this awful habit of going dark. Apart from being midly annoying, this also has the added side effect of making classeur.io appear way too bright, even with my monitor brightness turned way down. Since I'm usually in the middle of a paragraph, I don't want to get up and turn the light on, so it would be really helpful if classeur had a night, or dark, mode that could be toggled via a keyboard shortcut.

Dear @sbrl,
Thanks for your request!
Closing this in favour of [1].
Please feel free to follow-up there.
And I will make sure to create an article in the FAQ [2] to explain what Zen Mode ist. Thanks!
[1] https://github.com/classeur/classeur/issues/11
[2] https://classeur.zendesk.com/hc/en-us/sections/201884219-FAQ

Thanks @orschiro :smile:


Add composer support

It would be great if you could add composer support, providing correct requirements and using component-installer to provide the required JS, CSS and Image files.
Use Case: Many projects use composer, and it is annoying to manage libraries which are used via composer, and manually installed libraries. Thanks!

I'm a bit tight on time lately and haven't made a non-php package composer compatible yet.
Do you think you could create a pull request for that?
Would be awesome!

Hi. Sure, no problem. I have created a composer.json file with the required directives to install JS and CSS files to component folder. Hopefully I did not forget anything. Created a pull request for the changes.

Cool thx :)
I will make a small change but then it's fine.

Perfect, thank you! And sorry for providing the wrong mail address, was my best guess based on the available information :)
One last thing, though: would you mind to publish the package on Packagist? This is the default repository for composer users, hence one could avoid adding another repository to composer.json.

Sure, forgot that. Just added it.

Package is now available. Thanks!


LightSlider with LightGallery?

It is possible to use combine LightSlider with LightGallery?
Popup main image of the LightSlider by LightGallery popup plugin? Many thanks for answer! :)

Hi,
http://sachinchoolur.github.io/lightslider/examples.html
Here you will find one example.

http://sachinchoolur.github.io/lightGallery/


Add more polynomial tests

Added some more tests, fresh from gpt
Also fixed a bunch of things along the way

These are awesome.
Just a suggestion from the perspective of another contributor, can you please open an issue before tackling something so that it's easy to coordinate, and prevent duplicate work.

Whoops, I'll do that. The plan was to only write tests but the gpt translation turned out surprisingly great, so I just added everything


terminal needs to stay open for undot to work

it seems terminal needs to stay open/active, is there another way to run this? preferably using a menu bar app to turn the function on/off when a user wants?
other than that, it works brilliantly, stupid dot finally gone when I don't want it in full screen
haha... if I read the script right, the dot is not gone but undot merely moves its position outside of the screen real-estate :_) Amazing!

You could probably execute
while :
do
     /usr/local/bin/undot
     sleep 1
done

as a shell script, and run that shell script with a macOS LaunchAgent, setting the agent to: run at load & always keep alive.

ok

I've since built two AppleScript apps, one to start undot and one to stop it and the bash background process, I'm in the process of refining them, at which point I will for this repo and include those scripts and apps

You could also create a shell script for xbar: https://github.com/matryer/xbar … that way you'd have undot with menu bar functionality.

Gosh bless you m#ther f$#ker! thanks!

I personally added this script in Preferences > Users > Login items
#!/bin/bash
SCRIPT_DIR="$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )"
nohup bash -c "while :; do $SCRIPT_DIR/undot/undot; sleep 1; done" </dev/null >/dev/null 2>&1 &

I personally added this script in Preferences > Users > Login items
#!/bin/bash
SCRIPT_DIR="$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )"
nohup bash -c "while :; do $SCRIPT_DIR/undot/undot; sleep 1; done" </dev/null >/dev/null 2>&1 &

Stupid question, but how do I add a script to Login items?

Create a file name yourscript.sh somewhere (I put mine in ~/Scripts), then in login items you can click the + arrow to add the shell script to be launch at login.
Don't forget to chmod +x yourscript.sh in a terminal to allow it to be executed.
Also sometimes .sh file are set to open with text editor by default, so you can also right-click yourscript.sh (or cmd + i), then click Get Info and set the file to actually be opened by the Terminal app.
The only downside to my script is that it'll show a terminal at boot for a very short time.

I used the script with automator to create an app. Give the app accessibility privileges and set to startup on login. Works perfectly!

I've made a few changes so that:

Undot keeps running and hides the window right away.
Undot is a real application, so you can add it to your login items.

Give it a shot and let me know how it works! I'm going to close this bug, but feel free to keep commenting, and I'll reopen it if it doesn't resolve the issue.

thank you so much @s4y !!!


Issue/5842-dont-run-cleanup-jobs-halted-environment-iso5

The server runs many cleanup jobs in the background. This issue should make sure that no cleanup jobs are run on halted environments.
Closes https://github.com/inmanta/inmanta-core/issues/5842
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[ ] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[x] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches iso5 in 6b9ecc88f08ab1a0e9dafed05f5df99f1018911f


Need to pass only args to evaluate callback

Hi Team - In the current version of the evaluate API, there is no provision to send only args to the callback, we need to pass an element along with the args param, is there any way where we can pass only arguments to the callback function?
Example:
await evaluate( (args) => { }, options)

I agree with you. I faced this issue as well. The way I got around it is by passing a dummy select like this:
const dummyDiv = $("div");
await evaluate(dummyDiv, function (x) { });


Ensure helm test --logs only gets logs from pods

What this PR does / why we need it:
Partially fixes https://github.com/helm/helm/issues/11236#issuecomment-1332554000 by ensuring that helm test --logs only tries to get logs of a hook of kind Pod.
Of course, a more comprehensive fix would be nice but perhaps someone is already working on it as the issue is labelled in-progress.
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

The PR only seems to prevent the error being thrown rather than outputting the logs from the pods. Perhaps an improvement might be, in the case of a job, to fetch the pods associated with the job and then get the logs of those pods
I have found the following to work to get the pods from the jobs, but perhaps there is a better way (Im relatievly new to helm so others may have better ideas)
ctx := context.Background()
job, _ := client.BatchV1().Jobs(r.Namespace).Get(ctx, h.Name, metav1.GetOptions{})
listOptions := metav1.ListOptions{
LabelSelector: "job-name=" + job.Name,
}
				pods, _ := client.CoreV1().Pods("").List(ctx, listOptions)

It does seem like we should be getting logs from any of the application types, but that's out of scope for this PR. Since we're only getting logs from pods, it seems reasonable to gate the fetch on it being an actual pod.
@akshaymankar if you could shortcut the for loop as suggested and rebase this PR, it's good to merge.

Sorry, I don't need this anymore. Please feel free to create a separate PR with the branch in this PR.


Add Support for Configuring a JHipster App

JHipster uses Spring Boot, but not the Okta Spring Boot starter. Nevertheless, it'd be cool if we could configure a JHipster app with this plugin.
Here's what's required:

Create ROLE_ADMIN and ROLE_USER groups if they don't exist
Create a roles claim to include the groups
Create a new Web app, set the redirect URI to end in /oidc rather than /okta, and set a logout redirect URI to http://localhost:8080

More details at https://www.jhipster.tech/security/#oauth2.

Love it!  Is there an easy way to detect if the project is a JHipster project? check if there is a .jhipster/ dir?
I'm guessing we could move to using type-specific goal names like:

mvn okta:spring-boot-setup
mvn okta:jhipster-setup

(it would still be nice to auto detect this though)

I think the easiest way currently is to look for a .yo-rc.json file. That has the answers to the all the question answers when you create a new project.

Or we could look for a package.json and generator-jhipster dependency in it. This could be useful if we want to use the plugin with Node projects.
Other steps that need to happen for JHipster:

Create a ROLE_USER and ROLE_ADMIN group (if they don't exist)
Create a new Web app with a login redirect URI of http://localhost:8080/login/oauth2/code/oidc
Add a groups claim to the ID token

I'm not sure that we want to replace the default Keycloak values in application.yml. It might be more secure to create an okta.env file with environment variables in it.
export SPRING_SECURITY_OAUTH2_CLIENT_PROVIDER_OIDC_ISSUER_URI="https://{yourOktaDomain}/oauth2/default"
export SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_OIDC_CLIENT_ID="{client-id}"
export SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_OIDC_CLIENT_SECRET="{client-secret}"

I tried running okta apps create today when I wasn't in a JHipster project. I encountered a stack trace.
Type of Application
> 1: Okta Spring Boot Starter
> 2: Spring Boot
> 3: JHipster
> 4: Other
Enter your choice [Other]: 3
Redirect URI
Common defaults:
 JHipster - http://localhost:8080/login/oauth2/code/oidc
 Spring Security - http://localhost:8080/login/oauth2/code/okta
Enter your Redirect URI [http://localhost:8080/login/oauth2/code/oidc]:
java.lang.NullPointerException
	at com.okta.cli.common.config.EnvFilePropertiesSource.lambda$getProperties$1(EnvFilePropertiesSource.java:85)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:176)
	at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
	at java.util.Iterator.forEachRemaining(Iterator.java:133)

We're going to be pulling out the hardcoded platform support and instead rely on meta information provided by sample projects from a new samples org. We have yet to create any of this yet, but I am sure we will be bugging you @mraible when the time comes!

I tried this today and discovered a couple of issues:

The ROLE_ADMIN and ROLE_USER groups are not created. Ideally, both are created and the current user is added to both. You'll be able to log in without these groups, but you won't be able to do anything after than unless you have at least one.
The groups claim is added to the access token. It should be added to the ID token.


JsonParser::assignProperties error when getting item using Browse Service

Hello,
First of all, thanks for your work on this project!
I have some problems with BrowseService::getItem() method. Usually it works well but for one specific id 'v1|122185519308|422430345674' it crashes:

Catchable fatal error: Argument 2 passed to DTS\eBaySDK\Parser\JsonParser::assignProperties() must be of the type array, string given, called in /home/xxx/public_html/vendor/dts/ebay-sdk-php/src/Parser/JsonParser.php on line 99 and defined in /home/xxx/public_html/vendor/dts/ebay-sdk-php/src/Parser/JsonParser.php on line 16

Here is the code:
$id = 'v1|122185519308|422430345674';
$browseService = getBrowseService();

$request = new GetItemRestRequest();
$request->item_id = $id;
$browseService->getItem($request);

If this helps, I already dumped variables right before error (JsonParser::actualValue, $propertyMeta and $value):
object(stdClass)#902 (6) {
  ["propertyName"]=>
  string(7) "taxType"
  ["phpType"]=>
  string(32) "DTS\eBaySDK\Browse\Types\TaxType"
  ["repeatable"]=>
  bool(false)
  ["attribute"]=>
  bool(false)
  ["elementName"]=>
  string(7) "taxType"
  ["strData"]=>
  string(0) ""
}

string(3) "VAT"

Same for me. Seems like "DTS\eBaySDK\Browse\Types\TaxType" constructor expects an array, but the string is passed as value

This one fixes the issue temporarily:
/dts/ebay-sdk-php/src/Browse/Types/Taxes.php
change string 52
from 'type' => 'DTS\eBaySDK\Browse\Types\TaxType',
to  'type' => 'string',

can it be resolve in future?

@davidtsadler any news about your new process creating these files?

@michabbb Work on the new process is going slowing because I'm struggling to find the time to work on development. In addition it looks like I'm going to have to drop support for Enum classes in the Restful API as this information can't be generated from the OpenAPI files that eBay provide. This means that files such as https://github.com/davidtsadler/ebay-sdk-php/blob/master/src/Browse/Enums/AvailabilityStatusEnum.php will no longer be in the SDK once I switch to using the OpenAPI.
I've created an issue over here https://github.com/davidtsadler/ebay-api-sdk-php/issues/8 regarding the new OpenAPI code generation.


EVA-3033 - detect project needing clustering

This script is intended to assert with some confidence (but not full) if step such as the accessioning, remapping and clustering have been performed on one of many projects.

@apriltuesday Since this PR script looks like it has already been run, I have addressed only the low hanging fruits in the review comments.


security/acme-client: implement cloudflare token

solves  #1477 #1614
I've tested this with mutiple domains on a testing env and my home environment, both 19.7.7. Seems to be functional.
Please do an honest review though, I feel this is dodgy at best. Esp. the hack in security/acme-client/src/opnsense/scripts/OPNsense/AcmeClient/certhelper.php would need some attention.

@Alphakilo Merged, thanks!


chore: use eslint modules

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[x] Refactoring

Context

[x] Use eslint-modules. and unify eslint config. ref: https://eslint.nuxt.com/

will fix reviewdog in seperate PR

I've seen that you have used biome in one project, isn't it more suitable?

I've seen that you have used biome in one project, isn't it more suitable?

afaik biome still doesn't fully support some front-end frameworks
At the moment, for vue project -> eslint
for non-vue project -> biome. But I'm okay with switching to eslint so that we can use eslint in all our repos if you prefer eslint. Since biome config still not merged yet: https://github.com/kodadot/private-workers/blob/feat-dyndata/services/dyndata/biome.json

But I'm okay with switching to eslint so that we can use eslint in all our repos if you prefer eslint

I am ok with both, just seen on twitter that @biomejs is faster ;D

Is it possible to auto-fix these warnings related to eslint ?

mostly able to auto-fix that: https://github.com/kodadot/nft-gallery/pull/10630
but some of them need manual fixes: https://github.com/kodadot/nft-gallery/issues/10631

c @Jarsen136


Submissions/validation

[ ] Check file format, bounding box, and resolution
[ ] minioclient package to transfer from submission to forecast directory
[ ] Wrap in a GutHub action triggered by a new submission

Is this what you had in mind @cboettig? Anything else?

examples of GH actions and submit script
https://github.com/eco4cast/tern4cast/blob/main/.github/workflows/submissions.yaml
https://github.com/eco4cast/tern4cast/blob/main/R/submit.R

yup right on!

Couple very initial commits here: https://github.com/eco4cast/modis-lai-forecast/tree/submission-workflow
First I modified spat4cast_submit() to add some validation steps. It's a work in progress as I have a few questions:
a) I believe we discussed in the last call that we are enforcing bounding boxes and resolution? In that case, we probably need to modify ingest_planetary_data() to enforce these arguments on a per-site basis. Then the submission checks would be to confirm that the user did not modify any metadata.
b) To perform these checks, I assume we'd need a template. Could we do this with the targets file?
c) Are we only allowing .tif files?
d) How should each submission be tracked if they are all being added as ensembles to the same directory?
I also made a very simple processes_submissions.R file to move the submissions from the submissions directory to the forecasts directory. I don't have EFI credentials so I wasn't able to check if it worked. Anything else we would need to include here? The examples from tern4cast have a lot of user-friendly messages so we can definitely add that.

This looks great, can you open a PR and I'll do a quick code review?


chore(deps): untangle dependencies

What this PR changes/adds
Avoid spi modules refer to core ones
Why it does that
spis should stay on top and not depend from core or extension modules
Further notes

introduced data-plane-common library module, that contains utility classes like ParallelSink and OutputStreamSink

Linked Issue(s)
Closes #2033
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

I might have overlooked it, but could you point out which SPI modules depended on core ones before?

Sorry, I forgot to report them from the issue:
spi/common/core-spi/build.gradle.kts
37:    implementation(project(":core:common:util"))

spi/data-plane/data-plane-spi/build.gradle.kts
24:    implementation(project(":core:common:util"))

spi/data-plane-selector/data-plane-selector-spi/build.gradle.kts
22:    implementation(project(":core:common:util"))

spi/control-plane/transfer-spi/build.gradle.kts
30:    api(project(":core:common:policy-evaluator"))

(the last one actually was already fixed before)

Codecov Report
Base: 64.73% // Head: 64.69% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (17cb9f5) compared to base (499bb46).
Patch coverage: 66.66% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2098      +/-   ##
==========================================
- Coverage   64.73%   64.69%   -0.04%
==========================================
  Files         792      792
  Lines       16881    16883       +2
  Branches     1090     1089       -1
==========================================
- Hits        10928    10923       -5
- Misses       5497     5504       +7
  Partials      456      456

Impacted Files
Coverage Δ

...rolplane/defaults/InMemoryStatefulEntityStore.java
97.61% <ø> (ø)

...olplane/defaults/ReflectionBasedQueryResolver.java
100.00% <ø> (ø)

...actdefinition/InMemoryContractDefinitionStore.java
92.30% <ø> (ø)

...tiationstore/InMemoryContractNegotiationStore.java
93.10% <ø> (ø)

...lts/policystore/InMemoryPolicyDefinitionStore.java
100.00% <ø> (ø)

...lane/selector/core/DataPlaneSelectorExtension.java
0.00% <0.00%> (ø)

...tor/strategy/DefaultSelectionStrategyRegistry.java
0.00% <ø> (ø)

...taplane/framework/DataPlaneFrameworkExtension.java
80.95% <ø> (ø)

...or/dataplane/common/sink/OutputStreamDataSink.java
63.63% <ø> (ø)

...plane/common/sink/OutputStreamDataSinkFactory.java
100.00% <ø> (ø)

... and 19 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


store: Make sure query generation doesn't fail

We had a few places were query generation could fail because of an unknown
table or column. That then makes it impossible to print the failed query
for debugging purposes.
This commit changes things so that these errors are detected before we
construct QueryFragments.

Rebased on top of latest master


isBetween not working correcly with hermes engine

Describe the bug
Using isBetween with hermes engine in react native returns false with default moment configurations.
To Reproduce
Steps to reproduce the behavior:

['2019-06-06',  '2019-06-07].filter(d => moment(d).isBetween('2019-06-05',  '2019-06-08', null, '[]'));

Expected behavior
Expected: returns both dates from the array
Result: returns an empty array
Moment-specific environment
react-native
android
hermes engine
Additional context
When i turn off hermes the method works fine so i cant really decide if the problem is with moments default locale or timezone or hermes itself.

@tankpower1 did you find a solution for this? I am having this issue for moment.diff() as well. moment(date).diff(Date.now()) > 0 always returns false on Android(w/hermes) but works fine on iOS.

I haven't found a solution, just disabled hermes for now until its fixed.

Based on https://github.com/facebook/hermes/issues/136 and https://github.com/facebook/hermes/issues/175, I think it is related to Hermes's date processing (or perhaps processing of / characters?)
I do not think this is a Moment.js problem. I'd recommend opening an issue with Hermes if someone still has a problem.


fix: only fills defaults for plugins config schemas

A few issues (here and here) have been opened
on decK that suggest we sometimes parse wrongly the plugins defaults
coming from their schema, merging into the config object fields
that are not part of the config schema itself.
This makes sure that we only merge together the right attributes.

Codecov Report

Merging #145 (8f9f88c) into main (ef7e9a5) will decrease coverage by 0.95%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##             main     #145      +/-   ##
==========================================
- Coverage   45.42%   44.47%   -0.96%
==========================================
  Files          44       44
  Lines        3949     3962      +13
==========================================
- Hits         1794     1762      -32
- Misses       1820     1872      +52
+ Partials      335      328       -7

Flag
Coverage Δ

2.0.5
39.67% <71.42%> (-0.03%)
:arrow_down:

2.1.4
39.50% <71.42%> (-0.03%)
:arrow_down:

2.2.2
39.50% <71.42%> (-0.03%)
:arrow_down:

2.3.3
39.50% <71.42%> (-0.03%)
:arrow_down:

2.4.0
39.50% <71.42%> (-0.03%)
:arrow_down:

2.5.1
39.50% <71.42%> (-0.03%)
:arrow_down:

2.6.0
39.50% <71.42%> (-0.03%)
:arrow_down:

2.7.0
39.50% <71.42%> (-0.03%)
:arrow_down:

community
39.67% <71.42%> (-0.03%)
:arrow_down:

enterprise
43.86% <71.42%> (-1.14%)
:arrow_down:

enterprise-<IP_ADDRESS>
?

enterprise-<IP_ADDRESS>
43.86% <71.42%> (-0.05%)
:arrow_down:

enterprise-<IP_ADDRESS>
43.86% <71.42%> (-0.05%)
:arrow_down:

enterprise-<IP_ADDRESS>
43.86% <71.42%> (-0.05%)
:arrow_down:

enterprise-<IP_ADDRESS>
43.86% <71.42%> (-0.05%)
:arrow_down:

enterprise-<IP_ADDRESS>
43.86% <71.42%> (-0.05%)
:arrow_down:

enterprise-<IP_ADDRESS>
43.86% <71.42%> (-0.05%)
:arrow_down:

enterprise-<IP_ADDRESS>
43.86% <71.42%> (-0.05%)
:arrow_down:

integration
44.47% <71.42%> (-0.96%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

kong/utils.go
77.36% <71.42%> (-2.64%)
:arrow_down:

kong/workspace_service.go
32.75% <0.00%> (-20.69%)
:arrow_down:

Continue to review full report at Codecov.

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


Insulated redstone conduit and advanced computer from computercraft

i am using an extended version of dw20's reactor program which allows 16 turbines (due to redstone color api limitation). however, the insulated redstone conduit always exhibit 2 problems.

after i restart my server (private with friends), the conduit always outputs a high signal level from the advanced computer,
it always fails to transmit a redstone signal on a 4th color.

ref:http://www.computercraft.info/forums2/index.php?/topic/24495-bigreactors-control-script-up-to-16-turbines-extension-of-direwolf20s-script/
info:i am using tesseracts to control the steam flow instead of using the railcraft tanks. so the conduits are attached to the tesseracts to control whether they turn on or not.

Duplicate of #2658


Multiple Triggers Are Not Working in Combination With Workflow Dispatch

Short Description: If a pipeline contains the trigger “workflow_dispatch” and "push", the pipeline is not executed for push events.
Expected behavior: I would expect the pipline to be executed for both events. For a simple push as well as a manual execution.
Incorrect behavior: The pipeline does not react to push-trigger.
Current behavior: Only the manual execution works.
Reproduction: The following example contains two triggers. On the one hand the new “workflow_dispatch” as well as a simple "push". With this definition only the manual execution works. The pipeline is not executed during a push.
name: default

on:
  workflow_dispatch:
    inputs:
      profile:
        description: 'The environment in which the application is to be installed.'
        required: true
        type: choice
        options:
        - dev
        - sys
        - prod
  push:

env:
    PROFILE: dev

jobs:
  compile:
    runs-on: ubuntu-latest
    steps:
      - name: preparation
        id: evaluate
        run: |
          if [ "$GITHUB_EVENT_NAME" = "workflow_dispatch" ]; then
            export USE_ENVIRONMENT=${{ inputs.profile }}
          else
            export USE_ENVIRONMENT=${{ env.PROFILE }}
          fi
          echo "Determined Environment: $USE_ENVIRONMENT"

Workaround: Two independent workflows can be created as a workaround. The first deals with the “workflow_dispatch” and the second with the "push" event. The common logic is outsourced to a "workflow_call" and used by the previous workflows.
Gitea Version
1.23.0+dev-526-g3269b04d61
Can you reproduce the bug on the Gitea demo site?
No, because there are no runners available.
Log Gist
No response
Screenshots
No response
Git Version
2.30.2
Operating System
Debian 10.7
How are you running Gitea?
Gitea is running with two act_runners and an act_runner cache within Docker on a Debian system.
Database
SQLite

I created a pull request to allow parse workflow_dispatch in act fork project. https://gitea.com/gitea/act/pulls/118

That's great news! Thank you so much for the quick turnaround and helpful feedback!

Just got gitea 1.22.3, above issue is still there.

I cannot reproduce it. Can you post your workflow file?

This is the head of the file
name: Articles build & deploy
run-name: Deploy to GCP Cloud ${{ gitea.actor }}
on:
  push:
    branches:
      - "release/production"
      - "release/testenv1"
      - "release/testenv2"
      - "release/testenv3"
      - "release/testenv4"
  workflow_dispatch:
    inputs:
      environment:
        description: "Environment to run tests against"
        type: environment
        required: true
        default: "environment value"

env:
  SERVICE_NAME: ${{ fromJson(vars.branch_service_mapping)[gitea.ref_name] }}
  ENVIRONMENT: ${{ contains(fromJSON('["staging", "production"]'), inputs.environment) && inputs.environment || (contains(gitea.ref_name, 'production') && 'production' || 'staging') }}

defaults:
  run:
    shell: bash

jobs:
  deploy:
    runs-on: ubuntu-22.04
    steps: ...


Aws::InitAPI(options)

Describe the bug
aws-sdk-cpp/crt/aws-crt-cpp/crt/aws-c-io/source/s2n/s2n_tls_channel_handler.c:195: 0 && "s2n_init() failed"
Expected Behavior
I want to initialze Aws API success.
Current Behavior
When I use Aws::InitAPI(options), s2n_init() failed: 402653236 (Error initializing trust store)
Reproduction Steps
I use aws-sdk-cpp-s3 library and openssl librarys
Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
1.9.339
Compiler and Version used
4.8.5
Operating System and version
centos 7.6

Are you making sure to set it up correctly as shown here?
#include <aws/core/Aws.h>
...

Aws::SDKOptions options;
Aws::InitAPI(options);

//use the sdk

Aws::ShutdownAPI(options);


Auto import not use alias then move root project in subdirect

VSCode Version: 1.27.2
OS Version: macOS mojave

Steps to Reproduce:
I moved the project with the client to the "client" folder and I broke "auto imports"
Before i move files to client folder

After

and how auto imports work

My jsconfig
{
  "exclude": [
    "node_modules",
    "dist"
  ],
  "include": [
    "src/**/*",
    "tests/**/*"
  ],
  "compilerOptions": {
    "lib": [
      "es2018",
      "es2017",
      "es2016",
      "es2015",
      "dom",
    ],
    "baseUrl": "./",
    "paths": {
      "src/*": ["src/*"]
    }
  }
}

@dimensi are you using typescript or javascript?

@bpasero sorry, i missclick and send report too early. Wait please

@bpasero i use javascript in project and set jsconfig.json in root.

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

@mjbvz some problem on insider

The same happens for typescript.

@dimensi Please share a small example project that demonstrates this problem


Added verbose to Test-DscConfiguration

Not adding this to the CHANGELOG.md as there is already an item that covers this. This was missed in the previous PR.

This change is

@PlagueHO Small one, can you review this too?  😃

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Pathways game added

PR Description 📜
This is simply a Maze game where you have to start from one point and go to the finish point as fast as you can!
There are 5 levels in total & each new level increases the difficulty!
Fixes #4162

Mark the task you have completed ✅

[X] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[X] I have added screenshot for website preview in assets/images
[X] I have added entries for my game in main README.md
[X] I have added README.md in my folder
[X] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Pujan-sarkar ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@kunjgit hello sir could you tell why you giving the pending label for this pr so i can work on it if there is no problem with this issue , can you merge this pr please sir .

@kunjgit please give a reply or something

@kunjgit sir i have solved the conflicts and it is fully working please will reply or merge this pr ,i have send this 3 days ago

@kunjgit  why are not you merging my pr , you are merging all others pr why you have gave  me the pending label , explain me ?

@kunjgit why are not you merging my pr , you are merging all others pr why you have gave me the pending label , explain me ?

Your pr is being reveiwed currently the labels will soon be updated!! Thank you for your patience.

@kunjgit  you are merging other requests and not mine why , for this it has been showing conflicts every time, please merge my pr.

Please try to resolve conflicts!!

@ishita-43  I have done it please check

Resolve arising merge conflicts


Better oid->relname resolution.

I've found that on CockroachDB the driver executes many relname request, for the oid=0. Instead of handling that specific use case, I've decided to make the resolution a bit more robust (e.g. handling the edge case where the lookup of the oids succeeds only partially).

This was abandoned in favour of https://github.com/stablekernel/postgresql-dart/pull/60


evaluation.m

Hi, I didn't find evaluation.m?

In occludingBoundaryVertices.m file,the last statement
occludingVertices = intersect(occludingVertices,visiblevertices(FV, eye(3)));                                     why the transform maxtrix is eye(3)  rather than R which was caculated in program above.

same problem here,you found file or not?

it also gives an error at end
Error using flipud (line 19)
X must be a 2-D matrix.
can you please guide me about this error
thanks

For now, demo.m provides a run through of the whole pipeline. We will add an evaluation script some time in the future which also shows how to run some evaluations.

@waps101  Can you share the evaluation script now? Thanks!


'ThalnetModule' object has not attribute 'logger'

Describe the bug
models/thalnet/thalnet_module.py is the source of the error, on line 131. Trying to log an error to logger causes this.
To Reproduce
Steps to reproduce the behavior:
Happened as I'm testing changes for #58 - I suspect just feeding in an incorrect sized data as described on the if statement on line 130 should trigger it.
Expected behavior
Should properly log to logger.
Desktop (please complete the following information):

OS: Ubuntu
OS version 18.04
Python version 3.5
PyTorch version 0.4.1

So this happens because miprometheus.models.thalnet.ThalnetModule inherits from torch.nn.Module and not miprometheus.models.Model, which is the base Model class and defines the logger as a class attribute:
https://github.com/IBM/mi-prometheus/blob/develop/miprometheus/models/model.py#L117-L118
This is common to the way some models are implemented in mip, when they are constituted from several classes that inherit from torch.nn.Module (to access autograd, and only have their main class inheriting from Model.
Having them access a logger would then require to add the following lines in each file where there are defined:
https://github.com/IBM/mi-prometheus/blob/develop/miprometheus/models/encoder_solver/mas_cell.py#L25-L27
Perhaps there is a better way to do this? @tkornut Do you have an idea?


Switch tests to run in isolated dummy steam installations

This change refactors how tests are run to setup dummy steam installations (well only the bits we need) that each test can run against in isolation. This is exciting for a number of reasons and it opens the door to a lot more testing related changes

With that out of the way it's time to switch to updating all the docs


[Question]: how to fit the chinese when use the "SemanticSplitterNodeParser "?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
it will show error when I load the doc which is filled by Chinese content,but it work well in English.
So, How can i custom the regex to make the chinese doc work?

as you told me ,but the line "from llama_index.packs.node_parser_semantic_chunking.base import SemanticChunker" is error,how can i use pip to solve? @dosu


Use isstream for more robust stream.Readable detection

See https://github.com/request/request/issues/1949 for the original issue description.
In short, helpers.isReadStream is overly restrictive in what it deems to be a readable stream. Specifically, only streams created via fs that stream file data from disk pass the test of this function. However, it is entirely valid to have a non fs stream that contains valid file data (e.g. streams generated from file data contained in multipart/form-data requests.
This pull request updates helpers.isReadStream to use the .Readable method contained within the existing dependency isstream. However, isstream.isReadable on its own is not restrictive enough to detect the kinds of readable streams that request needs to detect, as the http.IncomingMessage and its sub-classes are also readable streams, yet they need to be rejected by our test.
So, the combination of isstream.isReadable and instanceof http.IncomingMessage should be sufficient to successfully detect non http readable streams that may contain file data.

Hmm, while the tests pass, this change appears to break with FormData streams when I test it in my app.
I'll debug and come back when I know more.

Well, upon further debugging, it appears that the original problem encountered in #1949 is not, in fact, a bug within request. It turns out to be a side effect of the form-data package and how it determines the length of streams when building multipart/form-data objects.
In short, the lack of a .path property on file streams built by skipper causes this return statement to fire without the FormData.prototype._trackLength function ever calling next(), which in turn caues the entire request to fail.
While I believe that there may be an improvement to request in refining the isReadStream helper, I no longer believe it's the bug that I originally suspected it to be.

I'm closing this PR as it's no longer valuable in my mind. To wrap up my personal story here, it turns out that request and form-data already support my use-case; I had to specify the formData.file.options.knownLength property with the byteCount value of the stream created by skipper. Once I added this value, everything works as expected.

I found this issue belatedly because multipart/form-data requests were failing with S3 stream although both Content-Length and Content-Type were exposed via CORS configuration.
To workaround form-data's seemingly unnecessary check for path, I set a bogus path value like this:
let stream; // stream from s3.getObject
stream.path = 'bogus/path/for/form-data';

It's a nutty hack but works and seemingly has no side-effect. Hope form-data removes unnecessary path check soon.


Anchoring is unreliable

I need to revisit scaling because it's not reliable when you rescale the resolution. See gif below:

Okay so I have anchoring working somewhat decently, but I have some more use cases to account for after seeing some of the anchors not working when resizing the resolution. This is really due to how Unity decides to handle anchoring which is unfortunate.

Here's a look at the current anchoring in the primary scene im testing in.
https://github.com/InitialPrefabs/UGUIDOTS/issues/19#issuecomment-716081578

Anchoring is currently generally reliable, for positive scales, it still needs work with negative scales.


Why 999 must be multiplied when calculating score?

Hi,
I have some question on your code.
https://github.com/yang-song/score_sde_pytorch/blob/1618ddea340f3e4a2ed7852a0694a809775cf8d0/models/utils.py#L146-L159
When computing the score matching loss, it seems that you post process the output of model(A score model). But it doesn't make sense for me to multiplying 999 to t and doing scaling score = - score / std while you use the output of model on reverse(sampling) process.
https://github.com/yang-song/score_sde_pytorch/blob/1618ddea340f3e4a2ed7852a0694a809775cf8d0/sde_lib.py#L95-L97
Am I missing something?

I did those just to make sure it matches the implementation of DDPM. They are by no means natural, and are also not necessary though.


Sending InsightsUpload file to Ingress API

Now working only for "Default" schema.

[ ] depends on #10

Issue #9

@slemrmartin This is looking good. Want to rebase now that https://github.com/ManageIQ/topological_inventory-sync/pull/10 is merged?

@gtanzillo rebased, ready to review
cc @agrare @Ladas


style(docz-components): fix live preview background

Description
I noticed a minor UI glitch with the live preview background and the radius. I moved the CSS property from the inner wrapper to the outer one.
Screenshots

Before
After

Thanks for fixing that ! I couldn't stop seeing it once I noticed it 😄


Create consumer in real-time

I'm building a custom authentication plugin based on api keys, and I was wondering if there's a way to create consumers once I get an 'OK' from my internal authentication system. This would allow me avoiding syncing Kong db with my auth system.
One idea was to use the kong.db and create consumers manually, but there's no api for db on kong-js-pdk.
A possible solution would be to add a postgreSQL client like https://node-postgres.com/ to my plugin and do queries directly.
Is there a more elegant solution for this?
Thanks

@akira28 I don't immeditately see a way to do it without touching DB directly (or admin API), and that could be ugly. However
i can see this usage being common, actually plugins like openid, oauth2 does the same. But instead of actually create a consumer
you can use kong.client.authenticate to tell Kong the credential it mapped to. And plugins like rate-limit also honors
credential without the need to lookup consumer.

ah, nice to know. But how can I create the 'credential' object? And can I call kong.client.authenticate(undefined, credential) (undefined consumer)?

Yes you can. On Lua PDK I think credential is just an table of { id = "the credential value" }, it would work with
proper Js syntax, though i didn't try for myself.

by 'the credential value' you mean the 'api key'?

credential in this context means an abitrary identitifer that your internal auth system returns, that can uniquely
identifier a user.

cool, perfect! This simplify things A LOT!
Thanks


Update to ring 0.9.4.

Before ring 0.9.3, it was possible to link multiple versions of ring into a program, e.g. if one version depended on ring 0.6 and another dependend on ring 0.9. Unfortunately, this doesn't work, because the linker doesn't know to how to link ring's C/asm code correctly in that kind of situation. ring 0.9.3 added a flag to its Cargo.toml to tell the Rust toolchain to stop allowing multiple versions of ring to be linked into the same program, to prevent any problems this may cause.
ring 0.9.4 was released with an update to make some crates easier to update to 0.9.x.
Note that this requires cookie-rs 0.8.0 to be released, because the previous version of cookie-rs depended on ring 0.7.6, which would cause exactly the kind of multi-linking problem that this is trying to (in the end) prevent. See https://github.com/alexcrichton/cookie-rs/pull/89.

Blocked by https://github.com/alexcrichton/cookie-rs/issues/90

@briansmith I think you are missing SecureRandom from some of the imports here.

Merging in light of Travis errors since cookie = 0.8.0 is definitely out and alive. Not sure why the beta and nightly channels can't find it. I'm attributing this to strange Travis container caching.

Could you publish a new version on crates.io? Thanks!

@briansmith I've been getting this error on rust-csrf that I need to resolve before I can release this. I'm going to open an issue there to remind myself to fix it.
heartsucker@pythagoras:~/code/heartsucker/rust-csrf (develop)$ c test
    Updating registry `https://github.com/rust-lang/crates.io-index`
error: failed to select a version for `lazy_static` (required by `ring`):
all possible versions conflict with previously selected versions of `lazy_static`
  version 0.2.2 in use by lazy_static v0.2.2
  possible versions to select: 0.2.8, 0.2.7, 0.2.6

@briansmith Published

Great, thanks!


Windows Node Group Pattern

Issue #, if available:
Description of changes:
Windows Node Group Pattern
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@shapirov103 Could we merge this.

@shapirov103 Could we merge this.

@elamaran11 will gladly merge, let's address the feedback but the PR is quite ripe for merging.

@shapirov103 All issues are addressed and fixed, please review and Merge.

Please see my comment.

@shapirov103 Yes you are right. ClusterRole is what i was talking. This one is not required, didnt remove it.

All Lint issues fixed, Please check .


fix Grayscale release Item Value length limit can not be synchronized…

I have read the CLA Document and I hereby sign the CLA
fix Grayscale release Item Value length limit can not be synchronized with its main version
What's the purpose of this PR
upgrade the capacity of gray release
Which issue(s) this PR fixes:
Fixes #
Brief changelog
update ItemService.checkItemValueLength() method with logic of find parentNamespace's info.
recheck

recheck

I have read the CLA Document and I hereby sign the CLA


Build fails

I get a build failure when I try to use build.cmd.
The error is The value "" of the "Project" attribute in element <Import> is invalid. Parameter "path" cannot have zero length.
Here's the full build log:
build
* bootstrapping paket package manager...
Checking Paket version (downloading latest stable)...
Version 4.1.7 not found in cache.
Starting download from https://www.nuget.org/api/v2/package/Paket/4.1.7
Done.
* restoring build dependencies...
Paket version 4.1.7
Downloading dolly22/FAKE.Gitsemver:475e2a1ce8ab6d8d4c2ec7858270c4e654bd9b1a Gitsemver.fsx to C:\Projects\FAKE.Dotnet\paket-files\dolly22\FAKE.Gitsemver\Gitsemver.fsx
Downloading FAKE 4.25.5
Downloading FSharp.Data 2.3.0
Downloading FSharp.Formatting.CommandTool 2.14.2
Downloading NuGet.CommandLine 3.4.3
Downloading FAKE.Lib 4.25.5
Downloading Zlib.Portable 1.11.0
10 seconds - ready.
* starting FAKE build...
Semver file prefix is: 2.0.0
C:\Program Files\Git\mingw64\bin\git.exe log -G"2.0.0" --reverse --max-count=1 --format=format:%H -- .semver
5274abaa1f82e46eef6c0ec98c6845685c7ad873
C:\Program Files\Git\mingw64\bin\git.exe rev-list --count 5274abaa1f82e46eef6c0ec98c6845685c7ad873..HEAD
10
Building project with version: LocalBuild
Shortened DependencyGraph for Target Default:
<== Default
   <== GenerateDocs
      <== NugetPack
         <== BuildProjects
            <== UpdateVersion
               <== Clean

The resulting target order is:
 - Clean
 - UpdateVersion
 - BuildProjects
 - NugetPack
 - GenerateDocs
 - Default
Starting Target: Clean
Finished Target: Clean
Starting Target: UpdateVersion (==> Clean)
Using local build versioning
C:\Program Files\Git\mingw64\bin\git.exe rev-parse HEAD
e503597323b50b460652820d7aa74778942fe44b
Created AssemblyInfo file "src/SolutionInfo.fs".
Using version: {Major = 2;
 Minor = 0;
 Patch = 0;
 PreRelease = null;
 Build = "";}
Finished Target: UpdateVersion
Starting Target: BuildProjects (==> UpdateVersion)
Building project: C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj
  C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe  C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj /t:Build /m      /p:RestorePackages="False" /p:Configuration="Release" /p:OutDir="C:\Projects\FAKE.Dotnet\./artifacts/build" /logger:Fake.MsBuildLogger+ErrorLogger,"C:\Projects\FAKE.Dotnet\packages\FAKE\tools\FakeLib.dll"
C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe  C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj /t:Build /m      /p:RestorePackages="False" /p:Configuration="Release" /p:OutDir="C:\Projects\FAKE.Dotnet\./artifacts/build" /logger:Fake.MsBuildLogger+ErrorLogger,"C:\Projects\FAKE.Dotnet\packages\FAKE\tools\FakeLib.dll"
Microsoft (R) Build Engine version 14.0.23107.0
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 2017-04-06 18:03:58.
     1>Project "C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj" on node 1 (Build target(s)).
     1>C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj(51,3): error MSB4102: The value "" of the "Project" attri
       bute in element <Import> is invalid. Parameter "path" cannot have zero length.
     1>Done Building Project "C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj" (Build target(s)) -- FAILED.

Build FAILED.

       "C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj" (Build target) (1) ->
         C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj(51,3): error MSB4102: The value "" of the "Project" att
       ribute in element <Import> is invalid. Parameter "path" cannot have zero length.

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.02
Running build failed.
Error:
Building C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj failed with exitcode 1.

---------------------------------------------------------------------
Build Time Report
---------------------------------------------------------------------
Target          Duration
------          --------
Clean           00:00:00.0040284
UpdateVersion   00:00:00.0870338
Total:          00:00:01.6451140
Status:         Failure
---------------------------------------------------------------------
  1) Building C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj failed with exitcode 1.
  2) MSB4102: C:\Projects\FAKE.Dotnet\src\Fake.Dotnet\Fake.Dotnet.fsproj(51,3): The value "" of the "Project" attribute in element <Import> is invalid. Parameter "path" cannot have zero length.
---------------------------------------------------------------------

It seems like c:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\FSharp\ is missing. Do you have Visual F# selected in your Visual Studio installation?

I do have F# language support installed. But this looks like it's looking for Visual Studio 2015 in particular, and I only have Visual Studio 2017.

I have a similar issue. I guess the solution is to install Visual Studio 2015 and then Visual Studio 2017? Maybe the solution is somewhere inside https://github.com/Microsoft/visualfsharp/issues/2340/?


Requesting add of GEMIN token.

Add of GEMIN Flare token logo image, and of GEMIN to list of tokens.

Can you verify the source code of the Gemin smart contract on the Flare explorer?
Has the project a website?

Thank you for reaching out to me.
I've had some difficulty verifying the source code on Flare explorer,
despite having the original source code. It was very simple, just an
openzeppelin ERC20 token with default settings.
I will attempt to do what I can to get verified, but I am new to the
process.
The project does have a website. It is a project of my company, YuLabs
Entertainment.
https://yulabs.org
The cryptocurrency information is listed further down on the homepage. It
is a single page website.
[image: image.png]
On Tue, Feb 28, 2023 at 1:56 AM Alex Dupre @.***> wrote:

Can you verify the source code of the Gemin smart contract on the Flare
explorer?
Has the project a website?
—
Reply to this email directly, view it on GitHub
https://github.com/blazeswap/default-lists/pull/1#issuecomment-1447675542,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVKKUIJ3WMGCVNFR2WPFLLWZWOR7ANCNFSM6AAAAAAVJ6MQ3Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sorry for the repeat messages.
There is also a wiki.
https://keygemin.fandom.com/wiki/Keygemin_Wiki
On Tue, Feb 28, 2023 at 4:46 AM Shawn Fluhr @.***> wrote:

Thank you for reaching out to me.
I've had some difficulty verifying the source code on Flare explorer,
despite having the original source code. It was very simple, just an
openzeppelin ERC20 token with default settings.
I will attempt to do what I can to get verified, but I am new to the
process.
The project does have a website. It is a project of my company, YuLabs
Entertainment.
https://yulabs.org
The cryptocurrency information is listed further down on the homepage. It
is a single page website.
[image: image.png]
On Tue, Feb 28, 2023 at 1:56 AM Alex Dupre @.***>
wrote:

Can you verify the source code of the Gemin smart contract on the Flare
explorer?
Has the project a website?
—
Reply to this email directly, view it on GitHub
https://github.com/blazeswap/default-lists/pull/1#issuecomment-1447675542,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVKKUIJ3WMGCVNFR2WPFLLWZWOR7ANCNFSM6AAAAAAVJ6MQ3Q
.
You are receiving this because you authored the thread.Message ID:
@.***>


Flyouts sometimes will not close

I'm sorry in advance. I know it is never a fun issue when it happens randomly. I cannot narrow down what is causing this to happen. I will try my best to explain what's happening.
I have a flyout that has its IsOpen property bound to a boolean property in my ViewModel. My flyout let's the user enter in information to search my database. Once the user hits the button to search the database, I disable the controls in the flyout and show a MetroProgressBar inside of the flypout. Once all the data is pulled fine, I enable the controls,  hide the progressbar, and then set the property bound to IsOpen to False. Most of the time, this will close the flyout and everything is fine.
I am using this app on what I would call sub-par tablets. They just don't have a lot of CPU power so they can be kinda laggy. Anyway, maybe 1 out of 1000 times I do this action, the flyout is still visible, but the internal software thinks it is closed. In other words, the overlay of the main window is no longer there and when I click the arrow to close the flyout, it does nothing. It is basically drawn on the window but all the internal code (your DLL and my app) thinks it is closed.
If I were to force the IsOpen property to true in this situation, it would do the flyout animation and do what it is supposed to, but once I close the "new" flyout, the "old" flyout is still shown. It seems like some sort of drawing issue but I have no clue on how to fix it.
Is anyone else running into this issue? Does anyone have a suggestion on how to resolve this?
When I get it to happen again, I will try to get some screenshots.

@TravyDale Which version are you using?

<IP_ADDRESS>

I will add this. I hope it helps.
I noticed that the process of the flyout closing is to remove the gray background from the window the flyout is covering. Then slide out of view. When my flyout freaks out, imagine that it removes the gray background but it doesn't slide out of view. It will look exactly like that. I am just unable to close the flyout in this situation.

@TravyDale Can you try the alpha release (latest source)? it's also available through NuGet.

I will. I will report back in a week or so if things improve.

@TravyDale :+1:

Version <IP_ADDRESS> does not fix the issue. Just had it happen today where the flyout did not close.

@TravyDale Please try the latest pre-release, I changed some for the Flyouts close button

Will do. Thanks for the update.

@TravyDale Any news?

So far no issues. Let's call this closed and if I see it, I will let you know. Thanks!


🐛 BUG: Svelte optional props: code works but vscode complains

What version of astro are you using?
v1.0.0-beta.40
Are you using an SSR adapter? If so, which one?
no
What package manager are you using?
npm
What operating system are you using?
linux
Describe the Bug
Using typescript this complains on vscode, it tells you that the signature doesn't mach and you're missing a prop.
Component1.astro
---
import Component2 from "./Component2.svelte";
---
<Component2 />

Component2.svelte
<script lang="ts">
  export let optional: string = "none";
</script>

<h1>{optional}</h1>

Link to Minimal Reproducible Example
NA
Participation

[ ] I am willing to submit a pull request for this issue.

By the way confirming that the code works 100%, it's just vscode showing an error:
(alias) function Component2(_props: typeof Props): any
import Component2
Type '{ "client:load": true; }' is not assignable to type 'IntrinsicAttributes & { optional: string }'.
  Type '{ "client:load": true; }' is missing the following properties from type '{ optional: string }': optional ts(2322)

It seems like the type that Svelte gives us doesn't properly include that a certain props might be optional (notice no ? after the prop inside the error message)
It might be something on our end but I'm feeling like this could be an upstream issue

I ported this component from sveltekit + svelte and it works fine there

It seems like the type that Svelte gives us doesn't properly include that a certain props might be optional (notice no ? after the prop inside the error message)
It might be something on our end but I'm feeling like this could be an upstream incompatibly, I'll have to check how Svelte handle this

I believe Svelte checks if props have a defined value. If it does then it marks it as optional?
I can also confirm this is an issue on OS X.
Also, I noticed that if you use a union type, for example: export let prop: string | undefined = "", the reported type for prop when using the component is just string. It seems that undefined is just dropped (which could be something on Svelte or Astro's end).

It seems like the type that Svelte gives us doesn't properly include that a certain props might be optional (notice no ? after the prop inside the error message)
It might be something on our end but I'm feeling like this could be an upstream incompatibly, I'll have to check how Svelte handle this

I believe Svelte checks if props have a defined value. If it does then it marks it as optional?

Yeah, this is how it works in Svelte itself, if a prop has a default value it's considered optional
I investigated a bit and the issue here is that due to how we get props for Svelte components (just taking the props parameter used in the render function), we don't get if a prop is optional or not, just a list of the props with no real information
The way the Svelte tooling handle this is through a function that takes two parameters, the optional props and the required ones and return a list with the proper types / optional markers through some TS trickery.
I think we should be able to implement that fairly easily into our tooling too (famous last words)

Also, I noticed that if you use a union type, for example: export let prop: string | undefined = "", the reported type for prop when using the component is just string. It seems that undefined is just dropped (which could be something on Svelte or Astro's end).

This could be a separate issue on our end but I know that the Svelte tooling had some issues with this in the past too. Maybe this will be fixed by fixing the main issue


[react-redux] Remove export keyword from declarations

Avoiding any export declarations means that all declared modules are available as properties on the default export. The version of this libdef before the revamp didn't have any export keywords, presumably for that reason.
Why not use named imports, you say? I have a specific case where I can't use named imports: the new module support in Node.js 9.3 can't handle named imports on commonjs modules. And since I'm not able to use the ESM version of react-redux because it relies on a named import from react (which doesn't have an ESM version), I have to use the commonjs version.
Regardless: as react-redux does indeed have a default export, the libdef should be declared accordingly.

What about explicitly defining default export for the module? Current libfdefs has private types which should not be needed to be exposed. Also, rect-redux actually does not have default export: https://github.com/reactjs/react-redux/blob/master/src/index.js

My apologies, you are totally correct. I assumed there was a default export because I was able to import a default export from what was actually a CommonJS module. But that's the CommonJS version, not the ESM version... which is the source of the trouble here.
Sadly it doesn't seem like Node.js will ever support named imports from CommonJS modules:

With CommonJS, on the other hand, the shape of a module is not known until after the code is evaluated. What this means is, without making significant changes to the ECMAScript language spec, it will not be possible to use Named Imports from a CommonJS module.

I guess this implies that we want to support ESM in Node.js, we're stuck with declaring default exports in all libdefs for the foreseeable future. At least until major libraries like React start distributing ESM versions, and the community standardizes on a way of a declaring ESM versions.
I'll update this PR to explicitly declare the default export.

LGTM. @villesau?

Also, build is still failing, but it seems like that's probably unrelated? Would be nice to get confirmation there, and figure out what the heck is causing react-redux libdef to be so angry.

It appears that the build has been broken since #1731 due to test errors. The tests in the react-redux_v5.x.x/flow_v0.54.x-v0.61.x folder weren't updated (though the libdef was), so they have been failing since #1731.
There are additionally some failures in react-redux_v5.x.x/flow_v0.62.0- that don't appear to have been occurring when #1731 was merged. I'm not entirely sure what's going on there, as they are occurring on 0.62.0, which was tested by the CI (but didn't fail) at the time at merge.

LGTM! The errors are unrelated and some sort of test suite glitch. Not sure why it matches also older versions of the libdef.


SQL DB embedded in HTML export doesn't work when a documentation field contains newlines

Shame on me!
Related to #400
The escape method used to export information from the model to the Embedded SQL DB doesn't escape newlines and, at best, makes the SQL DB unusable, and at worst makes the default model page (not the whole export though) unreadable.
I have to double check escape methods used by StringTemplate...
JB

Do you mean "Documentation" field?
Escaping can be tricky, we had problems before now with links and other issues.

Do you mean "Documentation" field?

Yes, title changed

Is this a problem with the export of the report or the SQL DB code?

The issue lies in frame.stg on lines 46 and 53: they use description:decodeURL("^c.Documentation;format="xml-encode"^"). decodeURL is a javascript function which "url-decodes" a string that has previously been encoded by StringTemplate using the format="xml-encode".
In this case, format="xml-encode" doesn't encode newline, this is the problem. I have to read the StringTemplate doc to see how to to this.

format="xml-encode" was added some years ago because of problems (can't remember what). So we have to be careful of regressions.

format="xml-encode" was added some years ago because of problems (can't remember what). So we have to be careful of regressions.

This is not related. In this case this should be url-encode instead of xml-encode. This was what was used in previous version but this led to a null string (thus the comment on previous issue about documentation being empty). Using xml-encode works.. unless there is some newline, and unfortunately my quick tests has been done with a model containing small documentation fields without newlines.

I've found. In fact in previous version the issue was not cause by url-encode but by the fact that I used the field Description instead of Documentation. So If I use Documentation together with url-encode it seems to work: I can see the whole documentation content, but the newline gets removed. I will now check the javascript decodeURL() function.

Fixed in this commit
Sorry for having introduced this silly bug :-(

Sorry for having introduced this silly bug :-(

Well, it happens, doesn't it? ;-) What would software be if it didn't have silly bugs? I'm sure we'll find more silliness...

is it the same reason alasql does not return any result for a bigger model( possibly with newline characters in description) but works fine for a smaller model with do documentation ? I am using 4.3.3

Yes, as soon as there's at least one documentation field with a new line it screws the DB. You can fix it be manually replacing .st files by the one in the commit linked before.

Wonderful . When is it expcted to release ? ( as new version).
I somehow got by with replacing the CRLF characters for the.archimate with blank. :) . It works also.
btw , I think it would be kind of  cool to allow some HTML tag documentation ( instead of simple text) - is it posible in any later version ?

Hi,
I have a model with multi-line strings in the element's documentation field. When exporting it to an HTML report and opening it in the browser, I am getting the following error on the browser's console:
SyntaxError: "" string literal contains an unescaped line break
I believe this error is responsible for not being able to execute alasql queries on the model.
Could you please confirm that this is the same issue as the one discussed in this thread?
If so, do you have a date in mind for when the update will be released?
Thank you,
Nuno

Could you please confirm that this is the same issue as the one discussed in this thread?

I can't confirm anything if you don't provide enough details (like the version of Archi you are using).
This issue is solved in latest version of Archi (still in beta at writing time). So check latest 4.4.0 beta and see if you bug is fixed.

Closing as this is solved in Archi 4.4.0


Simplified JoltBodyImpl3D::get_principal_inertia_axes

I was going through the TODO(mihe) tags and noticed this one. The calculation that's there currently is quite expensive (GetMassProperties does quite a lot of things) and I think the calculation is quite trivial since Jolt also splits the inertia in a diagonal matrix and a rotation matrix.
Note: Code is totally untested as I don't know how to test it!

Oh yeah, I've been meaning to ask you about that one.
I couldn't at the time quite see what that whole circus with Godot's Basis::diagonalize would map to with Jolt, but I suppose that is in fact just a roundabout way of getting the inertia rotation, which you of course have readily available in Jolt.
I'll give it a try tomorrow!
(You also prompted me to check out my TODO comments, and I'm realizing now I really need to implement face collection for the ray shape, given that InternalEdgeRemovingCollector depends on it, but it should just be about using GetSupportingFace I guess?)

Yes,
// TODO(mihe): Implement face collecting

should be something like:
p_shape2->GetSupportingFace(hit.mSubShapeID2, ray_direction2, p_scale2, p_center_of_mass_transform2, result.mShape2Face);

(and you'll need to remove the const from result).


[docs] add Key_shared subscription type

Motivation
with pip-34 since 2.4.0 add add Key_shared subscription type
Modifications
add Key_shared subscription type

1: whether releases 2.4.0 and its minor releases need to be updated?

the 2.4.x doesn't contain the Configure consumer doc.

2: whether this parameter in other client docs (such as go) need to be updated?

Go & Python & C++  doesn't contain  this parameter, Node.js and websocket updated . thanks


Error in cli_service.go: argument 1 has incompatible type (missing method 'Deadline')

Hi.
Here is what I got:
$ go build -i -v -x
WORK=/tmp/go-build219060932
github.com/bippio/go-impala/sasl
mkdir -p $WORK/b035/
cd $WORK
/home/oceanfish81/gollvm_dist/bin/llvm-goc -fgo-importcfg=/dev/null -c -x c - -o /dev/null || true
github.com/bippio/go-impala/services/cli_service
mkdir -p $WORK/b035/importcfgroot/github.com/apache/thrift/lib/go
mkdir -p $WORK/b033/
ln -s /home/oceanfish81/go/pkg/gccgo_linux_amd64/github.com/apache/thrift/lib/go/libthrift.a $WORK/b035/importcfgroot/github.com/apache/thrift/lib/go/libthrift.a
cd /home/oceanfish81/go/src/github.com/bippio/go-impala/sasl
/home/oceanfish81/gollvm_dist/bin/llvm-goc -c -O2 -g -m64 -fdebug-prefix-map=$WORK=/tmp/go-build -gno-record-gcc-switches -fgo-pkgpath=github.com/bippio/go-impala/sasl -o $WORK/b035/go.o -I $WORK/b035/importcfgroot ./client.go ./plain.go ./sasl.go ./transport.go
mkdir -p $WORK/b033/importcfgroot/github.com/apache/thrift/lib/go
ln -s /home/oceanfish81/go/pkg/gccgo_linux_amd64/github.com/apache/thrift/lib/go/libthrift.a $WORK/b033/importcfgroot/github.com/apache/thrift/lib/go/libthrift.a
cd /home/oceanfish81/go/src/github.com/bippio/go-impala/services/cli_service
/home/oceanfish81/gollvm_dist/bin/llvm-goc -c -O2 -g -m64 -fdebug-prefix-map=$WORK=/tmp/go-build -gno-record-gcc-switches -fgo-pkgpath=github.com/bippio/go-impala/services/cli_service -o $WORK/b033/go.o -I $WORK/b033/importcfgroot ./GoUnusedProtection__.go ./cli_service-consts.go ./cli_service.go
echo '	.section .go.buildid,"e"' >> $WORK/b035/_buildid.s
echo '	.byte 0x65,0x5a,0x48,0x72,0x6e,0x6f,0x37,0x55' >> $WORK/b035/_buildid.s
echo '	.byte 0x38,0x6d,0x50,0x79,0x2d,0x5a,0x55,0x67' >> $WORK/b035/_buildid.s
echo '	.byte 0x62,0x74,0x65,0x35,0x2f,0x65,0x5a,0x48' >> $WORK/b035/_buildid.s
echo '	.byte 0x72,0x6e,0x6f,0x37,0x55,0x38,0x6d,0x50' >> $WORK/b035/_buildid.s
echo '	.byte 0x79,0x2d,0x5a,0x55,0x67,0x62,0x74,0x65' >> $WORK/b035/_buildid.s
echo '	.byte 0x35' >> $WORK/b035/_buildid.s
echo '	.section .note.GNU-stack,"",@progbits' >> $WORK/b035/_buildid.s
echo '	.section .note.GNU-split-stack,"",@progbits' >> $WORK/b035/_buildid.s
echo '' >> $WORK/b035/_buildid.s
cd /home/oceanfish81/go/src/github.com/bippio/go-impala/sasl
/home/oceanfish81/gollvm_dist/bin/llvm-goc -xassembler-with-cpp -I $WORK/b035/ -c -o $WORK/b035/_buildid.o -D GOOS_linux -D GOARCH_amd64 -D GOPKGPATH=github.x2ecom..z2fbippio..z2fgo..z2dimpala..z2fsasl -m64 $WORK/b035/_buildid.s
ar rcD $WORK/b035/pkg.a $WORK/b035/go.o $WORK/b035/_buildid.o
/home/oceanfish81/gollvm_dist/tools/buildid -w $WORK/b035/pkg.a # internal
cp $WORK/b035/pkg.a /home/oceanfish81/.cache/go-build/6c/6c13564ac1673b97012d5556cd1ad55e6d447aed60c32985670182c34e830221-d # internal
mkdir -p /home/oceanfish81/go/pkg/gccgo_linux_amd64/github.com/bippio/go-impala/
mv $WORK/b035/pkg.a /home/oceanfish81/go/pkg/gccgo_linux_amd64/github.com/bippio/go-impala/libsasl.a
rm -r $WORK/b035/
github.com/bippio/go-impala/services/cli_service
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:721:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:727:42: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:739:30: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:739:24: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:749:30: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:749:24: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:754:28: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:754:22: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:758:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:762:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:769:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:778:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:790:55: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:790:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:796:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:798:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:805:45: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:805:56: error: argument 2 has incompatible type (cannot use type int as type string)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:805:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:807:30: error: argument 1 has incompatible type (type has no methods)

../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:807:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:809:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:817:48: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:817:59: error: argument 2 has incompatible type (cannot use type int as type string)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:817:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:819:33: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:819:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:821:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:849:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:856:42: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:869:30: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:869:24: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:874:28: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:874:22: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:878:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:882:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:892:27: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:900:23: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:911:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:918:51: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:918:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:923:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:925:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:931:45: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:931:56: error: argument 2 has incompatible type (cannot use type int as type string)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:931:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:933:40: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:933:63: error: argument 3 has incompatible type (cannot use type int as type thrift.TType)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:933:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:937:33: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:937:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:943:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:946:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:986:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:993:42: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1006:30: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1006:24: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1016:30: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1016:24: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1021:28: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1021:22: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1025:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1029:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1039:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1057:55: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1057:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1063:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1065:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1071:39: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1071:50: error: argument 2 has incompatible type (cannot use type int as type string)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1071:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1073:28: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1073:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1075:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1082:51: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1082:62: error: argument 2 has incompatible type (cannot use type int as type string)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1082:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1087:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1115:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1122:42: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1135:30: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1135:24: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1140:28: error: argument 1 has incompatible type (missing method 'Deadline')
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1140:22: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1144:20: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1148:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1158:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1168:51: error: argument 1 has incompatible type (type has no methods)

../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1168:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1173:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1175:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1181:48: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1181:59: error: argument 2 has incompatible type (cannot use type int as type string)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1181:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1183:28: error: argument 1 has incompatible type (type has no methods)
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1183:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1185:18: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1218:21: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1226:42: error: not enough arguments
../../go/src/github.com/bippio/go-impala/services/cli_service/cli_service.go:1239:30: error: argument 1 has incompatible type (missing method 'Deadline')

I am using

$ go version
go version go1.15.2 gollvm LLVM 12.0.0git linux/amd64

under Ubuntu 20 x86_64

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/oceanfish81/.cache/go-build"
GOENV="/home/oceanfish81/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/oceanfish81/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/oceanfish81/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/oceanfish81/gollvm_dist"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/oceanfish81/gollvm_dist/tools"
GCCGO="/home/oceanfish81/gollvm_dist/bin/llvm-goc"
AR="ar"
CC="/usr/bin/clang"
CXX="/usr/bin/clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build333483145=/tmp/go-build -gno-record-gcc-switches -funwind-tables"

Can you please post the version of Thrift in your build environment. You may find this information in the file $GOPATH/src/github.com/apache/thrift/README.md
The go-impala library has been tested till Thrift version 0.12.0

Can you please post the version of Thrift in your build environment. You may find this information in the file $GOPATH/src/github.com/apache/thrift/README.md
The go-impala library has been tested till Thrift version 0.12.0

@shaloi ,
I am seeing this:
Status

| master |  |  |  | |  |
| **0.13.0** |  | | | | |
| **0.12.0** |  | | | | |

Okay. It seems like you are on Thrift 0.13.0. Lets try with Thrift version 0.12.0. Depending on the package management tool your project uses, the way of getting a specific version of a package will be different. So. lets try it the naive way:
$ cd $GOPATH/src/github.com/apache        # go to the Apache Thrift package directory in the system GOPATH
$ mv -f thrift thrift.0.13.0        # take a backup of the existing thrift directory
$ wget https://github.com/apache/thrift/archive/v0.12.0.tar.gz       # download Thrift version 0.12.0
$ tar -zxf v0.12.0.tar.gz && mv -f thrift-0.12.0 thrift        # extract the downloaded Thrift version 0.12.0 tarball

Now try building your project and let us know the outcome.

I just did as you proposed.
It looks like the files where compiled:

$ go build -i -v -x
WORK=/tmp/go-build047381096
github.com/apache/thrift/lib/go/thrift
mkdir -p $WORK/b007/
cd $WORK
/home/oceanfish81/gollvm_dist/bin/llvm-goc -fgo-importcfg=/dev/null -c -x c - -o /dev/null || true
cd /home/oceanfish81/go/src/github.com/apache/thrift/lib/go/thrift
/home/oceanfish81/gollvm_dist/bin/llvm-goc -c -O2 -g -m64 -fdebug-prefix-map=$WORK=/tmp/go-build -gno-record-gcc-switches -fgo-pkgpath=github.com/apache/thrift/lib/go/thrift -o $WORK/b007/go.o -I $WORK/b007/importcfgroot ./application_exception.go ./binary_protocol.go ./buffered_transport.go ./client.go ./compact_protocol.go ./context.go ./debug_protocol.go ./deserializer.go ./exception.go ./field.go ./framed_transport.go ./http_client.go ./http_transport.go ./iostream_transport.go ./json_protocol.go ./memory_buffer.go ./messagetype.go ./multiplexed_protocol.go ./numeric.go ./pointerize.go ./processor_factory.go ./protocol.go ./protocol_exception.go ./protocol_factory.go ./rich_transport.go ./serializer.go ./server.go ./server_socket.go ./server_transport.go ./simple_json_protocol.go ./simple_server.go ./socket.go ./ssl_server_socket.go ./ssl_socket.go ./transport.go ./transport_exception.go ./transport_factory.go ./type.go ./zlib_transport.go
echo '	.section .go.buildid,"e"' >> $WORK/b007/_buildid.s
echo '	.byte 0x33,0x39,0x4d,0x30,0x6c,0x2d,0x65,0x56' >> $WORK/b007/_buildid.s
echo '	.byte 0x31,0x65,0x68,0x70,0x56,0x76,0x66,0x38' >> $WORK/b007/_buildid.s
echo '	.byte 0x49,0x57,0x5f,0x49,0x2f,0x33,0x39,0x4d' >> $WORK/b007/_buildid.s
echo '	.byte 0x30,0x6c,0x2d,0x65,0x56,0x31,0x65,0x68' >> $WORK/b007/_buildid.s
echo '	.byte 0x70,0x56,0x76,0x66,0x38,0x49,0x57,0x5f' >> $WORK/b007/_buildid.s
echo '	.byte 0x49' >> $WORK/b007/_buildid.s
echo '	.section .note.GNU-stack,"",@progbits' >> $WORK/b007/_buildid.s
echo '	.section .note.GNU-split-stack,"",@progbits' >> $WORK/b007/_buildid.s
echo '' >> $WORK/b007/_buildid.s
/home/oceanfish81/gollvm_dist/bin/llvm-goc -xassembler-with-cpp -I $WORK/b007/ -c -o $WORK/b007/_buildid.o -D GOOS_linux -D GOARCH_amd64 -D GOPKGPATH=github.x2ecom..z2fapache..z2fthrift..z2flib..z2fgo..z2fthrift -m64 $WORK/b007/_buildid.s
ar rcD $WORK/b007/pkg.a $WORK/b007/go.o $WORK/b007/buildid.o
/home/oceanfish81/gollvm_dist/tools/buildid -w $WORK/b007/pkg.a # internal
cp $WORK/b007/pkg.a /home/oceanfish81/.cache/go-build/7e/7e8375f896cdf023bae13fb205df78939a214d65a673ec967729cecfbac4a342-d # internal
mkdir -p /home/oceanfish81/go/pkg/gccgo_linux_amd64/github.com/apache/thrift/lib/go/
mv $WORK/b007/pkg.a /home/oceanfish81/go/pkg/gccgo_linux_amd64/github.com/apache/thrift/lib/go/libthrift.a
rm -r $WORK/b007/
/home/oceanfish81/go_projects/go-impala/sasl
mkdir -p $WORK/b001/
mkdir -p $WORK/b001/importcfgroot/github.com/apache/thrift/lib/go
ln -s /home/oceanfish81/go/pkg/gccgo_linux_amd64/github.com/apache/thrift/lib/go/libthrift.a $WORK/b001/importcfgroot/github.com/apache/thrift/lib/go/libthrift.a
cd /home/oceanfish81/go_projects/go-impala/sasl
/home/oceanfish81/gollvm_dist/bin/llvm-goc -c -O2 -g -m64 -fdebug-prefix-map=$WORK=/tmp/go-build -gno-record-gcc-switches -fgo-pkgpath=/home/oceanfish81/go_projects/go-impala/sasl -fgo-relative-import-path=/home/oceanfish81/go_projects/go-impala/sasl -o $WORK/b001/go.o -I $WORK/b001/importcfgroot ./client.go ./plain.go ./sasl.go ./transport.go
echo '	.section .go.buildid,"e"' >> $WORK/b001/_buildid.s
echo '	.byte 0x31,0x71,0x53,0x74,0x48,0x57,0x47,0x4a' >> $WORK/b001/_buildid.s
echo '	.byte 0x44,0x6e,0x34,0x56,0x6e,0x43,0x53,0x43' >> $WORK/b001/_buildid.s
echo '	.byte 0x55,0x43,0x4c,0x49,0x2f,0x31,0x71,0x53' >> $WORK/b001/_buildid.s
echo '	.byte 0x74,0x48,0x57,0x47,0x4a,0x44,0x6e,0x34' >> $WORK/b001/_buildid.s
echo '	.byte 0x56,0x6e,0x43,0x53,0x43,0x55,0x43,0x4c' >> $WORK/b001/_buildid.s
echo '	.byte 0x49' >> $WORK/b001/_buildid.s
echo '	.section .note.GNU-stack,"",@progbits' >> $WORK/b001/_buildid.s
echo '	.section .note.GNU-split-stack,"",@progbits' >> $WORK/b001/_buildid.s
echo '' >> $WORK/b001/_buildid.s
/home/oceanfish81/gollvm_dist/bin/llvm-goc -xassembler-with-cpp -I $WORK/b001/ -c -o $WORK/b001/buildid.o -D GOOS_linux -D GOARCH_amd64 -D GOPKGPATH=..z2fhome..z2foceanfish81..z2fgo_projects..z2fgo..z2dimpala..z2fsasl -m64 $WORK/b001/_buildid.s
ar rcD $WORK/b001/pkg.a $WORK/b001/go.o $WORK/b001/_buildid.o
/home/oceanfish81/gollvm_dist/tools/buildid -w $WORK/b001/pkg.a # internal
cp $WORK/b001/pkg.a /home/oceanfish81/.cache/go-build/5f/5fbbd08d478407e9ca8b6863b52cc3bfa684ebcbb22632a3cf1d7ee1398093ec-d # internal

Great. I will update the documentation about the supported Thrift versions. Shall I close the issue as resolved?

Please open an issue, for migrating to Thrift 0.13 - and provide a patch, so v0.12 would be obtained automatically (as for now).
As for this issue - this surely might be closed.
I think tests for go-impala are working - but I will search for end-user use cases, in the future.
Thanks

Currently this project uses dep as the package management tool where the dependency on Apache Thrift 0.12 is specified. We have plans to move to using go modules soon.


TBI - Enhance the --cloud-service-key flow to support UAA credentials

Description (include screenshots)
When running the ABAP deploy comamnd;
npx fiori deploy --name ZJLONG0205 --package '$tmp' --transport '' --url 'https://server.exmaple' --cloud true --cloud-service-key './service.json'

a new window tab is opened and I have login to authenticate the session. I would like to use the existing service.json file with my credentials to automate the flow, for example ina ci/cd pipeline flow.
The following slimmed down version of a service.json file has been appended with a username and password;
{
 "uaa": {
  "username"<EMAIL_ADDRESS>  "password": "MyPassword",
  "clientid": "abapcp-test!b2274",
  "clientsecret": "JveKNuBq7WA",
  "url": "https://server.exmaple"
 },
 "url": "https://1304ac32-36df-4308-ae73-831943ee6763.server.exmaple"
}

There should be enough information provided to retrieve the access and refresh token without having to open a new browser window to authenticate the session and a allow a successful ABAP deployment of my Fiori UI app.
This will provide an automated way for ci/cd pipelines jobs as well and this is existng behaviour in Fiori Tools.
Value
Improved way of deploying to a ABAP cloud.
Architecture Elaboration
Does it requires architecture elaboration?
Notes
Tasks

[ ] Update axios-extension to handle the UAA credentials if present in the service.json file
[ ] Update test cases

@longieirl @cianmSAP is this one done?

Hi @longieirl ,
Is this still open? I'm trying to deploy Fiori app to ABAP BTP environment from CI/CD pipeline and cannot configure it to bypass the browser popup.


Correctly report cancelled for ChronosTaskLauncher

We don't keep track of cancelled jobs, how would we know this task was "cancelled" when creating status? haven't seen a cancel API call either, we just delete the job for now