Docs: add release management process to the maintainers guide

As a follow-up to the maintainers guide that was started in #5876 it would be good to include the rest of the release process that is a bit hard to infer
I think it looks like this:

npm run increment-version
npm run update-version # this runs in postversion but should probably be done before the npm install
npm install # make sure the package-lock.json is in the right state
npm run extract-codes # I don't see any other time this is called and it seems necessary for a release
npm run prepare-release # not strictly necessary but probably a good idea to make sure everything at least builds before tagging
git commit -a # I think that npm run postversion wouldn't work if there are any pending changes
npm run postversion
npm run release
npm run publish-extension

I included the extra steps between update-version and postversion because I think there might be a subtle bug or two in npm run postversion:

npm install && npm run update-version may leave package-lock.json in a state where it references some older versions.
It also seems like a the right time to run npm run extract-codes?

Pretty sure this is sufficiently covered by https://lexical.dev/docs/maintainers-guide#release-procedure


Play local video

Can we play local video from bundle or can we play video from URL like this: http://clips.vorwaerts-gmbh.de/big_buck_bunny.mp4 (not youtube URL)

maybe can use like this?
let myVideoURL = NSURL(string: "https://www.youtube.com/watch?v=wQg3bXrVLtg")
videoPlayer.loadVideoURL(myVideoURL!)

@encikpulasan  I have already mentioned that not youtube URL

@ibhavin Hi there! Thanks for your interest in this library. Unfortunately, I have no plans to add that functionality, as this is specifically for playing YouTube videos, and playing local videos would require a completely different approach. Sorry about that!


fix: Remove build:id in generic examples

In this case I'd label them, yes, because it's otherwise hard to parse visually. BUT: I'd suggest taking the steps out of the comments entirely and having them in regular text, followed by the code example for that step. That way it's very clear (visually) to the user what the steps are when glancing over the docs, and they're only copying code comments into their system that are descriptive info reminding them of what the code does.

So you mean something like the following:

Step 1: add bla to your code

uses<EMAIL_ADDRESS>

Step 2: add bla 2 to your code

jobs:
  id: bla

So you mean something like the following, instead of inlining the comments in the code:

Step 1: add bla to your code

uses<EMAIL_ADDRESS>

Exactly.

So you mean something like the following, instead of inlining the comments in the code:

Step 1: add bla to your code

uses<EMAIL_ADDRESS>

Exactly.

I've made the changes. Thank you both for the feedback.

Thanks @olivekl !


Rewrite to Typescript

This is work in progress
not to be merged yet!
Formidable (IncommingForm)

[ ] Done?

My main concern here is that a log of variables is not defined before the parse method is called. From my understanding, the idea is that one Formidable instance can be parsing one request at a time, but can be reused after it has completed reading the form. (Why is it that it can be reused, what is the point?)
I would propose, that the parse would return a subclass, that would only live until the parsing is complete, then it would be a frozen object/class instance. The parse method then could:

Accept new parameters like expected booleans that would automatically convert and/or add missing boolean values ("on" and "true" to true and the rest to false).
Accept the JSON reviver function

Plugins

[ ] Done?

I still have more to read through.
Parsers

[ ] Done?

I still have more to read through.
Misc

[x] Files - I have made them a common class they both extend from, and unified most of the API. This might be a breaking change!
[ ] Helpers - How about replacing them with the subclass from Formidable.parse? It could return a Promise<ParsedForm>, where ParsedForm is:

class ParsedForm<
  // Setting this is unsafe, but is normal practice to allow developers to defined expected output
  Fields extends Record<string, string | string[]> | string[],
  Files extends Record<string, FormidableFile | FormidableFile[]>
>{
  readonly files: Files;
  readonly fields: Fields;

  readFirstOf<K extends keyof Files>(key: K): Files<K>;
  readFirstOf<K extends keyof Fields>(key: K): Fileds<K>;
}

I have a few questions for now:

Formidable.js:409 - variable results is created and returned via emitter from this function, but it is never referenced and thus could not be filled with data.
How does a plugin return anything? How does the binding of class into self work?
Formidable.js:548 - This line is rightfully highlighted with the error This condition will always return true since this function is always defined. Did you mean to call it instead?. The function that is being tested for existence is the same as the one that is being called and the function is statically defined, thus it should never be missing either.

Converting to Typescript is already a huge task. You refactoring the code at the same time reduces the likelihood of this PR being merged fast. Because it creates opportunity for disagreement.

Correct , https://github.com/node-formidable/formidable/blob/64f32c2d5486918b2b8afdc2c6cc994d5f9a4a61/src/Formidable.js#L442 add this line back
A plugin does not really return , instead it attaches properties to the formidable instance (this._parser = parser;)

I don't know where but if it is always true then maybe it is a leftover from before a refactor where it wasn't the case

Maybe in a future PR we will make .parse return a Promise so try to not change too much in this PR

Correct , https://github.com/node-formidable/formidable/blob/64f32c2d5486918b2b8afdc2c6cc994d5f9a4a61/src/Formidable.js#L442
add this line back
A plugin does not really return , instead it attaches properties to the formidable instance (this._parser = parser;)

My point is, that since the plugin does not return (only modifies this), and the results variable is not used it is redundant and should be removed.

Converting to Typescript is already a huge task. You refactoring the code at the same time reduces the likelihood of this PR being merged fast. Because it creates opportunity for disagreement.

You are right, rewrite to TS is huge in itself, but in order to make usage of TS sensible, some parts might need to be rewritten.

Maybe in a future PR we will make .parse return a Promise so try to not change too much in this PR

Well, the point was not to make it a promise. The current implementation of the parse function has a critical flaw.
Take the code below:
// Create parser (mistake but a sensible assumption to make
const form = formidable({});
const server = http.createServer((req, res) => {
  if (req.url === '/api/upload' && req.method.toLowerCase() === 'post') {
    form.parse(req, (err, fields, files) => {
      // Process result
    });

    return;
  }
});

Since the form will clean up itself after the request is parsed, one could assume, that creating a global form with common options is the right way and it would work most of the time. But once 2 requests come at the same time:

Parse will accept the request and save it internally along with a callback and some more variables.
It will start the first part of the stream synchronously
Then once the first async thing comes, the second request can come in and override defined variables and since the this variable is shared, it will create a total hawoc.

This could be fixed using a simple if statement in parse, or it could be fixed by making the parse create a new instance of parsing entity.
This would also make the IncommingForm initialization class from:
export class IncomingForm<
  // Setting this is unsafe, but is normal practice to allow developers to define expected output
  Fields extends Record<string, string | string[]> | string[],
  Files extends Record<string, FormidableFile | FormidableFile[]>
> extends EventEmitter {
  readonly options: FormidableOptions<Fields, Files>;

  error?: Error;
  headers?: IncomingHttpHeaders;
  type?: string;
  ended = false;
  bytesExpected = 0;
  bytesReceived = 0;
  readonly openedFiles: FormidableFile[] = [];

  private req?: IncomingMessage;
  private parser: undefined;
  private flushing = 0;
  private fieldsSize = 0;
  private totalFileSize = 0;
  private plugins: Transform[] = [];
}

into
export class IncomingForm<
  // Setting this is unsafe, but is normal practice to allow developers to define expected output
  Fields extends Record<string, string | string[]> | string[],
  Files extends Record<string, FormidableFile | FormidableFile[]>
> extends EventEmitter {
  readonly options: FormidableOptions<Fields, Files>;

  private readonly headers = this.getHeaders(this.req);
  private readonly type = this.getType(this.headers);
  // ended = false;  // Redundant, once it is done, the parse method returns and all cease activity, can be kept thought...
  // error?: Error; // Same as above
  private readonly bytesExpected = this.getExpectedBytes(this.headers);
  bytesReceived = 0;
  readonly openedFiles: FormidableFile[] = [];

  private flushing = 0;
  private fieldsSize = 0;
  private totalFileSize = 0;
  private plugins: Transform[] = [];
  constructor(
    private readonly req: IncomingMessage,
  ) {}
}


Crafting with dictionary in storage actuator duplicates dictionary

Applies to similar "container" items too

See https://github.com/klikli-dev/occultism/issues/143#issuecomment-770326282

See https://github.com/klikli-dev/occultism/issues/143#issuecomment-770326282


Multiple window problems

When multiple windows are opened, the listen event in the previous window is invalid.

I have the same problem.
launch(Application.class, MainStageView.class, args);
Main.showView(ListStageView.class, Modality.NONE);
Stage stage = GUIState.getStage();
stage.widthProperty().addListener((observable, oldValue, newValue) -> System.out.println(newValue));

How to get the monitor of the ListStageView after it displays?

This got not answered for a long time. I ran into similar issues while trying to create my own integration and finally realized that since Spring beans are singletons by default, you must specify them as scope = prototype to create a new instance of the controller every time a component is being created.


Update CI

CI not copied from gitlab. Need to modify/replace nf-core template defaults in .github/workflows/.
See also #1

Not needed: (not yet run)

.github/workflows/awsfulltest.yml
.github/workflows/awstest.yml

Modified and should keep:

.github/workflows/branch.yml  (working)
.github/workflows/ci.yml (failing due to lack of test config)

Maybe keep, but probably should not:

.github/workflows/fix-linting.yml
.github/workflows/linting.yml
.github/workflows/linting_comment.yml

Need to add lighter linting workflow.

Modified and should keep:
.github/workflows/branch.yml (working)
.github/workflows/ci.yml (failing due to lack of test config)
Needs updating

Need to add a linting workflow, but deleted them all for now.


Discrepancy of maps in state message

While the state.schema in the repository contains a maps object, the pdf version of the VDA 5050 V2.1.0 does not.

Thank you for the important information, we have investigated it accordingly. Both the state.schema and the Markdown document on GitHub contain this entry. The PDF will be adapted accordingly, as this is the only way to achieve the behavior described in the maps chapter.


Making entrypoint optional for Java Actions

With https://github.com/apache/incubator-openwhisk-runtime-java/issues/14 the Java Actions will be able to infer the entrypoint via Main-Class attribute of the jar. Hence the check https://github.com/kameshsampath/incubator-openwhisk-cli/blob/master/commands/action.go#L512 could be made optional for Java Actions

@csantanapr  am not sure we can add this issue to java-runtime improvements epic

The dependent PR in the Java runtime is not merged.

@kameshsampath sorry this sat for so long - looking through https://github.com/apache/incubator-openwhisk-runtime-java/pull/20 i think it's orthogonal to the proposed change here. I haven't looked deeper to see if we can implement this already, and you might know faster.

@rabbah am totally lost here.. been very long. If you still see it makes sense to merge please go ahead otherwise knock it off


Add support for limiting HTTP responses in httpcommon.ReadAll

What does this PR do?
It's generally unsafe to always read the entire response from an untrusted server. The server might set a very high Content-Length or serve an endless stream of data to crash its clients.

Why is it important?

Due to security considerations we should limit the response from an untrusted server.
Checklist

[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works

Benchmarks
goos: darwin
goarch: arm64
pkg: github.com/elastic/elastic-agent-libs/transport/httpcommon

BenchmarkReadAll/size:_1024/unknown_length/io.ReadAll-10         	     	    1000	      3117 ns/op	    2912 B/op	       9 allocs/op
BenchmarkReadAll/size:_1024/unknown_length/bytes.Buffer+io.Copy-10         	    1000	      2564 ns/op	    1168 B/op	       8 allocs/op

BenchmarkReadAll/size:_1024/known_length/io.ReadAll-10                     	    1000	      2542 ns/op	    2912 B/op	       9 allocs/op
BenchmarkReadAll/size:_1024/known_length/bytes.Buffer+io.Copy-10           	    1000	      2040 ns/op	    1120 B/op	       7 allocs/op

BenchmarkReadAll/size:_102400/unknown_length/io.ReadAll-10                 	    1000	     57221 ns/op	  514405 B/op	      24 allocs/op
BenchmarkReadAll/size:_102400/unknown_length/bytes.Buffer+io.Copy-10       	    1000	     10470 ns/op	  106640 B/op	       8 allocs/op

BenchmarkReadAll/size:_102400/known_length/io.ReadAll-10                   	    1000	     51872 ns/op	  514403 B/op	      24 allocs/op
BenchmarkReadAll/size:_102400/known_length/bytes.Buffer+io.Copy-10         	    1000	      9677 ns/op	  106592 B/op	       7 allocs/op

BenchmarkReadAll/size:_1048576/unknown_length/io.ReadAll-10                	    1000	    417455 ns/op	 5241195 B/op	      33 allocs/op
BenchmarkReadAll/size:_1048576/unknown_length/bytes.Buffer+io.Copy-10      	    1000	     73337 ns/op	 1048722 B/op	       8 allocs/op

BenchmarkReadAll/size:_1048576/known_length/io.ReadAll-10                  	    1000	    410043 ns/op	 5241201 B/op	      33 allocs/op
BenchmarkReadAll/size:_1048576/known_length/bytes.Buffer+io.Copy-10        	    1000	     73711 ns/op	 1048674 B/op	       7 allocs/op

PASS
ok  	github.com/elastic/elastic-agent-libs/transport/httpcommon	1.465s

Related issues

Relates to https://github.com/elastic/beats/issues/36151
Follow up to https://github.com/elastic/elastic-agent-libs/pull/183

:green_heart: Build Succeeded

Buildkite Build
Commit: 39e2bf9ef727b954766f405ababfb54ccd14414e

cc @rdner


Migrate to jsonschema>=4.21.0 and python 3.8-3.12

Issue #, if available:
Fixes Issue #34
Description of changes:

unpin and update jsonschema dependency to most recent version
Migrate tests that broke due to differently worded error messages in the new jsonschema version.
Explicitly use validator for Jsonschema Draft 2019 to keep the behaviour stable.
run and test on supported python version range 3.8 to 3.12
Resolve a DeprecationWarning for unittest.TestCase.assertEquals that broke with python 3.12

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mluttrell This fixes a lot of problems with using this great tool operationally. Can we please get this merged and released?

Thank you @theister and @scolebrook for the contribution.

@theister deserves all the credit. I just slapped a comment on the PR to draw some attention since it'd obviously slipped through the cracks for a couple of months.


Travis: cache ~/.luarocks

Codecov Report

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

@@          Coverage Diff           @@
##           master    #108   +/-   ##
======================================
  Coverage    91.4%   91.4%
======================================
  Files          11      11
  Lines        2152    2152
======================================
  Hits         1967    1967
  Misses        185     185

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 3f797af...a148794. Read the comment docs.

I wasn't aware that this was even a thing but Travis gave it a green checkmark so it must be good.


Bundling styled-components in an isomorphic app bundle crashes on the server at styled-components several instance check due to no window object

Environment
System:

OS: Windows 10 10.0.19041
CPU: (8) x64 Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
Memory: 2.59 GB / 15.60 GB

Binaries:

Node: 14.15.3 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - C:\Program Files\nodejs\yarn.CMD
npm: 6.14.9 - C:\Program Files\nodejs\npm.CMD

npmPackages:

styled-components: ^5.0.0 => 5.2.1

Reproduction
Bundling styled-components via webpack to an isomorphic bundle in development mode crashes due to webpack using styled-components.browser.esm.js, which references window["styled-components-init"]. window being undefined causes this to crash when the bundle is run in a non browser environment.
These are the lines where this happens (cc @probablyup):
https://github.com/styled-components/styled-components/blob/master/packages/styled-components/src/base.js#L41-L55
from this commit:
https://github.com/styled-components/styled-components/commit/f12b943658a9731ab6af6548a780019f696a09cb
Looking back in the history of that file, it looks like the typeof window !== 'undefined' check has been removed. Adding this check back should fix this issue for isomorphic bundled apps with no repercussions. This issue was introduced in >5.2. Downgrading to 5.1 does not have this issue.
Using webpack.DefinePlugin to set NODE_ENV to "production" also fixes this issue as the above lines gets removed from the output code, however this isn't an ideal fix for development.
For context, we are bundling this to run in a .NET Core app, server rendering React components via ReactJS.NET, and an issue has been created there (https://github.com/reactjs/React.NET/issues/1232) about it.
Other solutions like replacing the module in webpack with a different variant sprang to mind, however looking at the dist files, it seems that all dist files have the window["__styled-components-init__"] check (which i'm not sure is intended).

Possible related issue: after updating to 5.2.1 (5.2.0 as well), typescript compiler reports an error.
TS2322: Type 'Timeout' is not assignable to type 'number'.

I'm getting the same error from HtmlWebpackPlugin after upgrading from 5.1.1 to 5.2.3


fix: show projects only on desktop devices

Description
fix ZEN-271

Do we need another lib for this? ChatGPT says we can use something like this:
function isMobileDevice() {
    return /Android|webOS|iPhone|iPad|iPod|BlackBerry|IEMobile|Opera Mini/i.test(navigator.userAgent);
}

I guess that's a philosophical question. This library is pretty tiny and does a bit more of a check than what ChatGPT told you but we could definitely just copy this part:
https://github.com/rozek/svelte-device-info/blob/517210b3ec8caa65606f066572cfb85a03841728/src/svelte-device-info.ts#L10-L15
Problem then is that we have to maintain this in case this list ever changes.

SGTM!


Add advise for all functions in an object

Would it make sense to add a method which will be able to add the different advice's for all the methods/function of an object. A use case that comes to mind immediately is to log the error thrown by function.

Hi @nitinkcv.  I don't think there's a single definition of "all methods" in current JavaScript.  It probably means different things to different people in different use cases.  For example, there are owned and inherited properties (including methods inherited by all objects, like hasOwnProperty), enumerable/non-enumerable, writable/non-writable, configurable/non-configurable, etc.  So, there's a large number of possibilities for what "all methods" means.
Meld provides the ability to advise methods of an object matching a predicate.  The predicate can be a single string, array of strings, regex, or function.  For the particular definition of "all methods" fits your use case, you can write your own helper function to collect (using Object.keys, getOwnPropertyNames, getOwnPropertyDescriptor, or by doing prototype chain traversal with getPrototypeOf, etc.) those names into an array, and use it with the with meld's existing API.
meld.afterThrowing(myObject, myFindAllMethodNamesHelper(myObject), function(thrownError) { ... })

So, rather that build in a notion of "all methods", I think it makes sense for meld's core API to remain flexible and allow callers to determine the set of methods that fit their use case.  I could certainly see someone writing another helper package that provides some convenience functions for common cases.

Closing due to lack of activity.  If there's a need to reopen, please do.


Error with WebUI and new retiarii Experiment

Background: I installed nni from source (so the latest version from github). When trying to run an experiment(locally as well as remote) I can not start up the experiment due to some failure with the webui/node modules. I get an error reading: "time out" and "connection refused" or "No connection adapter".
This brought me to investigate my networking and port infrastructure as well as all possible involved modules from my side for 3 striaght days, however I could not identify any issues. To check my sanity I installed the stable version from pip and everything worked perfect. All experiments run on the version with pip. However this version does not include oneshot strategy yet which I really need (I am working on an adaption of DARTS (and beta-darts)).
So I have three questions:
Will there be a stable version including the oneshot strategy soon avilable via pip?
Can you think of anything that would explain why in the "old/stable" version from pip experiments run fine but with the latest version the webui can not be setup and constantly fails?
Is there a way to use ValueChoice with the old DartsTrainer interface as there is an option in the new lightning version of the tuner? And if not how would this be possible to implement?
The last question is really the most important one for me as I depend on using Darts with ValueChoice option and ideally would need it as soon as possible. Any help on this would be very highly appreciated.
To reproduce my error:
I download the repo via git clone. Install from source as outlined in the tutorial and than create a file such as in the hello_nas tutorial (https://nni.readthedocs.io/en/stable/tutorials/hello_nas.html) when trying to start the experiment on my ubuntu machine the server fails to start and the experiment shuts down before it started.
Thank you for any help!

Additional note: Sometimes (although not always) I also get the following error indicating a missing package:
"Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /data/s2965003/Thesis/nni/ts/nni_manager/node_modules/sqlite3/lib/binding/napi-v6-linux-glibc-x64/node_sqlite3.node)"

Will there be a stable version including the oneshot strategy soon avilable via pip?

Depending on the release schedule. Although the planned release date is next week, I think it will probably be delayed (again) for one or two weeks.

Can you think of anything that would explain why in the "old/stable" version from pip experiments run fine but with the latest version the webui can not be setup and constantly fails?

Maybe your build didn't succeed in the first place. NNI's build could still show success state despite errors in the typescript building process. You should notice warnings (as well as errors of course) shown in setup.py develop.
Two more reminders (you probably already have known):

If you have built a very-legacy version, try python setup.py clean first because building a new one.
Don't use python setup.py install or pip install .. They are not compatible with NNI.

Is there a way to use ValueChoice with the old DartsTrainer interface as there is an option in the new lightning version of the tuner? And if not how would this be possible to implement?

I think that's not easy. That's one of the reasons why we have this new lighning version.

"Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /data/s2965003/Thesis/nni/ts/nni_manager/node_modules/sqlite3/lib/binding/napi-v6-linux-glibc-x64/node_sqlite3.node)"

Looks like some dependency issue. Have you googled it?
One more thing, you don't really need all the typescript stuff to run a one-shot experiment. I know this sounds confusing. But all the typescript thing (including nni manager, webui) are only available when you run a multi-trial experiment. If you are struggling to get the typescript env setup, try skip hello_nas tutorial, and directly try a one-shot strategy.


Disable Line Wrap in Code Blocks

It would be great to have the option to disable line wrap when using code blocks

Closed in Minimal 6.1.0


[WIP] fixing CI issue for older julia with version dep code

Codecov Report

Merging #198 (beaf4a2) into master (a47c211) will decrease coverage by 0.15%.
The diff coverage is n/a.

:exclamation: Current head beaf4a2 differs from pull request most recent head 21aefb0. Consider uploading reports for the commit 21aefb0 to get more accurate results

@@            Coverage Diff             @@
##           master     #198      +/-   ##
==========================================
- Coverage   67.83%   67.68%   -0.16%
==========================================
  Files          13       13
  Lines        1679     1677       -2
==========================================
- Hits         1139     1135       -4
- Misses        540      542       +2

Impacted Files
Coverage Δ

src/blended_cg.jl
50.52% <0.00%> (-0.80%)
:arrow_down:

src/types.jl
64.44% <0.00%> (-0.40%)
:arrow_down:

src/active_set.jl
79.20% <0.00%> (+0.62%)
:arrow_up:

Continue to review full report at Codecov.

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

run-all-examples

run-all-examples


recordings JSON file for website: should include computed info

@elovero , this is now complete. The recording records now have more info, for example:
{
    "name": "001_synth",
    "study": "magland_synth_noise10_K10_C4",
    "directory": "kbucket://15734439d8cf/groundtruth/magland_synth/datasets_noise10_K10_C4/001_synth",
    "description": "One of the recordings in the magland_synth_noise10_K10_C4 study",
    "computed_info": {
        "samplerate": 30000.0,
        "num_channels": 4,
        "duration_sec": 600.0
    },
    "plots": {
        "timeseries": "sha1://cd0958b1f58faed6764e703deb3b70e59b2f1d27/timeseries.jpg",
        "waveforms_true": "sha1://70925b4a481ba6119623a6a487429fe898e18e54/waveforms.jpg"
    },
    "firings_true": "kbucket://15734439d8cf/groundtruth/magland_synth/datasets_noise10_K10_C4/001_synth/firings_true.mda",
    "true_units_info": "sha1://eec30f7c5e1d97ff6078110427e2f397c117790c/true_units_info.json"
}


Open source licensing?

Have you considered giving the project an open source license so people know the implications of using/distributing this code?

:tada: This issue has been resolved in version 1.1.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update 17723.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/release-notes/Insider/17723.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


/query enhancement: show permissions

Currently query only shows payment related information. We should display all the info we have on the user, which at least includes the permissions for them to be able to set labels on the repository.

/start

/query @Keyrxng

/stop

/start

???


UI adjustments and fixes

This are some basic changes. Generalized company names, fixed text color to no longer be the same as the background and navigation buttons no longer show up when it is the last/first page anyways.

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

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


Fireworks ai chat model

#1401
Add support for Fireworks AI chat model and manually test its functionality.

thank you! are you planning to work on the chat model as well ? https://js.langchain.com/v0.1/docs/integrations/chat/fireworks/

I think it supports streaming as well, can we try to add the name of this new component here

I think it supports streaming as well, can we try to add the name of this new component here

Sure, added the name. Thanks for your reply!


release 1.0

do the release process for 1.0 today, 2020-07-15 in prep for public release on 2020-07-16

[x] await #155 merge, hopefully
[x] update capa/version.py with version 1.0.0 1066707fdd4eea79e0ce50f7aca052a781e36195
[x] push to master
[x] tag release in gh, "draft release"
[x] pull from master with --tags
[x] pyinstaller build and attached to release page

[x] linux @williballenthin
[x] windows @williballenthin
[x] macOS @Ana06 #139

[x] publish release in gh (remove "draft")
[x] mark capa public
[x] mark capa-rules public
[x] mark capa-testfiles public

released.


QoL Survey

Changes
Creates the full Qol survey for the first-time onboarding and for the repeated monthly Qol survey. Does not implement or support weekly/daily check-ins.
Requirements
Requires: The work in this PR relates to the work in this PR. Must clone the updated persona repo. This is already included in setup.bash - see script for details.
PR Dependencies
Depends on: #26.
Merged Branches and Other Dependencies
Merged branch(es): None
Other dependencies: None
Subtasks / Progress

[x] switch out testBackendController with the real one and test
[ ] testing on different screen sizes on a real device (I tried to make the UI dynamic but it wasn't a primary focus so there may be some minor edits to be done)
[ ] The monthly check-in prompt should show up every 28 days, and it uses settings in the localSettings in firestore to do this. I noticed it wasn't working when I last ran the app (prompt was showing all the time). It had been working consistently earlier this week when I demoed so I'm not sure where the bug is and didn't have time to look into it :(
[x] refactor the tertiary trigger used in ./mobile/src/stateMachine/views/home.tsx to another trigger because the health auth PR uses tertiary on the home screen [Okay to leave in -Aidin]
[ ] the linked PR above should also probably be merged, and the setup script should be edited to clone the now merged persona branch.

Preview
TODO
Testing
Manual
Old:
TODOS/Notes for this PR that I didn't have time for: (fyi: @wynnset)

[Resolved - Rowan] Note: there is an error in the setup script (doesn't affect functionality). Error is documented and fixed in PR #31.
TODO: Remove the "Qol Survey" button on the home screen, unless this task is being completed in this PR

Need to check screen size and monthly prompt

@Mapleia Could you test this on Android when you gat a chance? Specifically going through and submitting the QoL Survey.

the linked PR above should also probably be merged, and the setup script should be edited to clone the now merged persona branch.

@MarkDavies0 is this todo done? It's not checked off in the list above.

@wynnset If I'm not mistaken that is leftover from Cara and yes it is complete by now

@wynnset I have completed renaming 'mags' in the persona repo but do not have access to that repository on GitHub. Could you add me so I can publish my branch?

@wynnset I have completed the renaming of 'armMags' in the persona repo but do not have access to that repository on GitHub. Could you add me so I can publish my branch?


💄 Internship page style changes

As per my conversation with @hveraus, the following design changes need to be made to the internship page.
### Tasks
- [x] Font | Body should be Open Sans
- [x] Font | Headings should be Helvetica Neue
- [x] Buttons | Buttons should all with rounded corner
- [x] Hero Image | “Apply Now” button, please change to rounded corner without arrow icon
- [x] Hero Image | Tagline is too bold, please change to semi-bold, also check the library, H1 set to medium weight
- [x] Hero Image | Piers photo should be smaller and should not cut his elbow off
- [x] Hero Image | we might not need the paragraph under tagline
- [x] Hero Image | when scale down the page, Piers should be still visible
- [x] Who What When | Double check the bottom padding, seems too small
- [x] Who What When | the three red icons and grey checks seems not high res, and grey checks are too big
- [x] Who What When | Text under Who and What should be bold and use Helvetica
- [x] Who What When | More padding between “Starts every Monday” and “Next program”
- [x] Who What When | Figures on counter down should be Helvetica
- [x] What will you learn | logos needs to be updated
- [x] Popular courses | the video cards should be rounded corner
- [x] Popular courses | “Watch More Videos” button should be rounded corner
- [x] Popular courses | Play button should have a rounded corner triangle
- [x] Popular courses | titles should be Helvetica
- [x] What do people say | missing 5 stars
- [ ] https://github.com/SSWConsulting/SSW.Website-v3/issues/604
- [x] Trusted by… | title should be H2 instead of H1

Everything is done or moved to a new issue


Pretrained Model with voxel  = 0.05

Thanks your work! I change the code like below, but i cannot get the same result like voxel  = 0.03.
I want to know if something else should be changed. Thanks!
## The release weight is pretrained on 3DMatch dataset, where we use a voxel downsample with 0.03m.
## If you want to test your own point cloud data which have different scale, you should change the scale
## of the kernel points so that the receptive field is also enlarged. For example, when testing the
## generalization on ETH, we use the following code to rescale the kernel points.
`        for v in my_vars:             if 'kernel_points' in v.name:                 rescale_op = v.assign(tf.multiply(v, 0.05 / 0.03))                 # print('kernel_points', rescale_op)                 self.sess.run(rescale_op)

Hi @BiaoBiaoLi
Could you specify which dataset you are using? Basically, if you want to test the release model on another dataset, you need to 1) use the hard selection strategy by uncommenting here. 2) change the voxel size and the scale of the kernel points according to the scale of your new dataset

Thanks! I use the redwood dataset. According to your suggestion, i change the code like below, but i cannot get the same result like voxel = 0.03.

I use the hard selection strategy like below. It only change the score  of each point, Whether I modify this or not, if voxel = 0.03,  the model can get a good result.
local_max = tf.reduce_max(neighbor_features, axis=1)
is_local_max = tf.equal(features, local_max)
is_local_max = tf.Print(is_local_max, [tf.reduce_sum(tf.cast(is_local_max, tf.int32))], message='num of local max')
detected = tf.reduce_max(tf.cast(is_local_max, tf.float32), axis=1, keepdims=True)
score = score * detected
I change the voxel size and the scale of the kernel points according to the scale of the new dataset by these code in demo.
Initiate dataset configuration

dataset = MiniDataset(files=point_cloud_files, voxel_size=0.05)
for v in my_vars:
if 'kernel_points' in v.name:
rescale_op = v.assign(tf.multiply(v, 0.05 / 0.03))
self.sess.run(rescale_op)

Hi, according to you description D3Feat should work quite well since redwood is also an indoor RGBD dataset which is similar to our training set. Could you please send some failure cases to me for debugging? BTW, I also think there is no need to change the voxel size and scale for redwood.

Thanks!
I am also confused about this. When the voxel = 0.03, the results are good.
I test the fragment 13 and 14 of loft with voxel = 0.05, while voxel = 0.03, the result is good.
http://redwood-data.org/indoor_lidar_rgbd/download.html
I just want to test the results of different resolution of the model.

Hi,  the voxel size is indeed one of the most critical hyper-parameter for our method because it affects the receptive field of our descriptors and the sparsity of input point cloud. And for some fragments, 5cm is too big for some thin structures in the indoor scene. I have seen the fragment 13 and 14, which contains a large surface and relatively few geometric-distinguishable regions, so using 5cm might also result in too few useful keypoints thus too few inlier correspondences for registration.

Oh, Thanks! when I change the voxel = 0.05, the results of whole redwood dateset are so bad, but voxel = 0.03 can get satisfactory results with the demo strategy using ransac.
Do you test the model in redwood dateset with voxel = 0.05? In the section 6.3. Outdoor settings: ETH Dataset, Do you train model with the different voxel size to experience or use the hard selection strategy and change the voxel size and the scale of the kernel points?
and
in the section 6.1. Indoor Settings: 3DMatch dataset, for FCGF, do you use the model trained on 5cm voxel size or 2.5cm voxel size?
Thanks!

In section 6.3, we evaluation the generation ability of D3Feat, so we use the model trained on 3DMatch (with 3cm voxel size) and evaluated under different voxel size and scale to get the numbers in Table 5. For FCGF, we use FCGF with 2.5 cm voxel size.

Thanks! in section 6.1 and 6.2, I want to know how to choose the keypoints of FCGF and other methods?

Since other methods do not have a keypoint dector, we select keypoints randomly for them.
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: BiaoBiaoLi @.>
发送时间: Thursday, March 25, 2021 1:08:31 AM
收件人: XuyangBai/D3Feat @.>
抄送: Xuyang BAI @.>; Comment @.>
主题: Re: [XuyangBai/D3Feat] Pretrained Model with voxel = 0.05 (#31)
Thanks! in section 6.1 and 6.2, I want to know how to choose the keypoints of FCGF and other methods?
―
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/XuyangBai/D3Feat/issues/31#issuecomment-806002466, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADTWVCJCHRKSZIRJTNWPDH3TFIMA7ANCNFSM4ZNDAE2Q.

Thanks!
In in your experience,  Do you use a RANSAC with 50,000 max iterations like the demo code ? or repalce the 4000000 to 50,000 500 the same and the distance_threshold = 0.05?
result = open3d.registration_ransac_based_on_feature_matching(
src_keypts, tgt_keypts, src_desc, tgt_desc,
distance_threshold,
open3d.TransformationEstimationPointToPoint(False), 4,
[open3d.CorrespondenceCheckerBasedOnEdgeLength(0.9),
open3d.CorrespondenceCheckerBasedOnDistance(distance_threshold)],
open3d.RANSACConvergenceCriteria(4000000, 500))

Yes I use RANSAC with 50000 max iterations for both 3DMatch and KITTI.

Thanks!
In general, what are the methods for selecting the distance_threshold  = 0.05 ?

You mean why I choose 0.05 as the distance_threshold?  This is a hyperparameter for RANSAC you may play with, you should consider the voxel size, the sensor noise, the scale of the scene, etc.  I think there is no golden criterion for selecting this distance threshold.

Thanks!!!
I want to know how to get the ground truth in line 288 KITTI.py about these code?
M = (self.velo2cam @ positions[0].T @ np.linalg.inv(positions[1].T)
@ np.linalg.inv(self.velo2cam)).T
Why not be np.linalg.inv(self.velo2cam @ np.linalg.inv(positions[0] ) @ positions[1]?
Thanks!!!

M = (self.velo2cam @ positions[0].T @ np.linalg.inv(positions[1].T) @ np.linalg.inv(self.velo2cam)).T
<==>
M = inv(velo2cam).T @ inv(pos[1].T).T @ pos[0] @ velo2cam.T
<==>
M = inv(pos[1] @ velo2cam.T) @ (pos[0] @ velo2cam.T)
If you change your computation to np.linalg.inv(positions[0] @ self.velo2cam.T) @ positions[1] @ self.velo2cam.T then you will get the inverse of our result (which is the reversed transformation), currently your computation got nothing meaningful I think.  Note that there is a transpose operator when constructing the velo2cam matrix. I mainly borrow the conversion from FCGF.

Thanks!!
I get it, there is a transpose operator when constructing the velo2cam matrix.
Is self.velo2cam.T the transformation of coordinate system?


Running multiple fastOptJS causes java.lang.NoClassDefFoundError: jdk/internal/reflect/MethodAccessorImpl

Symptom:

MethodAccessorImpl NoClassDefError happens with Scala.js 1.0.0-RC2, when compiling multiple Scala.JS projects. We have no such issue with Scala.js 0.6.x
After rerunning fastOptJS, the compilation eventually succeeds.
I'm using sbt 1.3.6 and JDK11. The same error happens with JDK8.

CI log: https://github.com/wvlet/airframe/runs/385008133

It might be an issue of sbt-scalajs plugin and sbt-1.3.x's new classloader.  I'll work on reproduction of this issue.
It seems the reflection call of PathOutputFile in the LinkerImpl is failing:
    private val outputFileMethod =
      loadMethod("PathOutputFile", "atomic", classOf[LinkerOutput.File], classOf[Path])

This is used here:
            val out = LinkerOutput(linkerImpl.outputFile(output.toPath))
              .withSourceMap(linkerImpl.outputFile(sourceMapFile.toPath)) <--------
              .withSourceMapURI(relURI(sourceMapFile.getName))
              .withJSFileURI(relURI(output.getName))

A workaround is splitting an aggregated project into a smaller set of projects and running fastOptJS individually.

Thanks for the report.
If I read that stack trace right, the call to invoke on the Method is failing, not the lookup. Looks like a thread safety issue on first sight, but all my Googling so far says java.reflect.Method is thread safe :-/


⚠ Bofrost.lu has degraded performance

In 09b0ee7, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 3146 ms

Resolved: Bofrost.lu performance has improved in 9e969f5 after 50 minutes.


Compatibility break in minor 0.14.3

Before it is not too late to change version number to 0.15.0. =)
https://github.com/genuinetools/reg/commit/298ecf151071650603378f25cf44636d227e2b4f removes reg-server command and replaces it with reg server. If I am right, then that means scripts like https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/files/reg-server/cron-prod will break after upgrade.

done https://github.com/genuinetools/reg/releases/tag/v0.15.0

I still think about if long options should start with a double slash..

thats a go default you would have to PR the standard library :)
On Mon, Jul 16, 2018 at 5:31 AM Anatoli Babenia
<EMAIL_ADDRESS>wrote:

I still think about if long options should start with a double slash..
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu

double dashes work, but the printing is the default...
On Mon, Jul 16, 2018 at 5:34 AM Jess Frazelle<EMAIL_ADDRESS>wrote:

thats a go default you would have to PR the standard library :)
On Mon, Jul 16, 2018 at 5:31 AM Anatoli Babenia
<EMAIL_ADDRESS>wrote:

I still think about if long options should start with a double slash..
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3
pgp.mit.edu
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/genuinetools/reg/issues/108#issuecomment-405193930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYNbI4UQ5WUm0viXX_7JGOfdWubPp1hks5uHF4igaJpZM4VQrF9
.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

With this go behaviour it is impossible to group options like in tar -xzvf.

it's the std lib :) im not saying i approve i am just saying that is
what is doing it
On Mon, Jul 16, 2018 at 5:44 AM Anatoli Babenia
<EMAIL_ADDRESS>wrote:

With this go behaviour it is impossible to group options like in tar -xzvf.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu

I see. :) So is there a way to change help output? (I am running out of the depth of my task tree for today to research this one).

I would take it upstream :) or you can write your own flag library :)
On Mon, Jul 16, 2018 at 5:48 AM Anatoli Babenia<EMAIL_ADDRESS>wrote:

I see. :) So is there a way to change help output? (I am running out of
the depth of my task tree for today to research this one).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/genuinetools/reg/issues/108#issuecomment-405197351,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYNbC2ez0jQmNoNdKwuN-ZHE92MCmSGks5uHGGIgaJpZM4VQrF9
.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3


npm ERR! code ELIFECYCLE

someone know how fix it in vue-storefront-api?
npm run dev
><EMAIL_ADDRESS>dev /mnt/_/dev/base/production.dpl/storefront/vue-storefront-api
> nodemon -w src --exec "babel-node src --presets es2015,stage-0"
[nodemon] 1.12.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: /mnt/_/dev/base/production.dpl/storefront/vue-storefront-api/src/**/*
[nodemon] starting `babel-node src --presets es2015,stage-0`
[nodemon] Internal watch failed: watch /mnt/_/dev/base/production.dpl/storefront/vue-storefront-api/src ENOSPC
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>dev: `nodemon -w src --exec "babel-node src --presets es2015,stage-0"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!  Also this may help
https://github.com/remy/nodemon/issues/239

@patrykpiston
Linux stackup 4.13.8-1-ARCH #1 SMP PREEMPT Wed Oct 18 11:49:44 CEST 2017 x86_64 GNU/Linux
node -> v8.5.0
npm -> 5.3.0

Could you attach the content of log file mentioned above?

yes, here 2017-10-27T15_18_30_622Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/home/jujes/.nvm/versions/node/v8.5.0/bin/node',
1 verbose cli   '/home/jujes/.nvm/versions/node/v8.5.0/bin/npm',
1 verbose cli   'run',
1 verbose cli   'dev' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /home/jujes/.nvm/versions/node/v8.5.0/lib/node_modules/npm/bin/node-gyp-bin:/mnt/_/dev/base/pr$
duction.dpl/storefront/vue-storefront-api/node_modules/.bin:/home/jujes/.nvm/versions/node/v8.5.0/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin$
site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /mnt/_/dev/base/production.dpl/storefront/vue-storefront-api
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c',
10 silly lifecycle   'nodemon -w src --exec "babel-node src --presets es2015,stage-0"' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec dev script
13 verbose stack Error<EMAIL_ADDRESS>dev: `nodemon -w src --exec "babel-node src --presets es2015,stage-0"`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/home/jujes/.nvm/versions/node/v8.5.0/lib/node_modules/npm/lib/utils/lifecycle.js:289:16)
13 verbose stack     at emitTwo (events.js:125:13)
13 verbose stack     at EventEmitter.emit (events.js:213:7)
13 verbose stack     at ChildProcess.<anonymous> (/home/jujes/.nvm/versions/node/v8.5.0/lib/node_modules/npm/lib/utils/spawn.js:40:14)
13 verbose stack     at emitTwo (events.js:125:13)
13 verbose stack     at ChildProcess.emit (events.js:213:7)
13 verbose stack     at maybeClose (internal/child_process.js:927:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /mnt/_/dev/base/production.dpl/storefront/vue-storefront-api
16 verbose Linux 4.13.8-1-ARCH
17 verbose argv "/home/jujes/.nvm/versions/node/v8.5.0/bin/node" "/home/jujes/.nvm/versions/node/v8.5.0/bin/npm" "run" "dev"
18 verbose node v8.5.0
19 verbose npm  v5.3.0
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>dev: `nodemon -w src --exec "babel-node src --presets es2015,stage-0"`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

@pkarw @patrykpiston I think this issue come from npm...
if I use yarn all work properly..
one more think about Performance and PWA the attached capture come from chrome audit, in the case for for production this values average are the same?

thanks in advance,

Thanks! On production we do have quite better results but still many things need to be optimized:

offscreen images
service worker tunning
image sizes - particularly on home page

Category and product pages are much faster (yesterday I got something around 75 of performance on category - still should be better)
Also - we have issue for preparing PWA manifest so this also is to be done
Right now we’re focusing on checkout functionality to open public demo. Then we’ll work continuously on performance

thanks @pkarw!!!
Please think about essential and easy deploy using all in one docker-compose.yml I work with traefik as proxy and put here some ideas:
version: "3"

networks:
  comp_proxy:
    external: true
  internal:
    external: false

services:
  demo.vuestorefront.io:
    container_name: demo.vuestorefront.io
    restart: always
    image: vuestorefront/vue-storefront:latest
    environment:
      ROOT_URL: "https://demo.vuestorefront.io"
      STORE_EMAIL<EMAIL_ADDRESS>      STORE_USER: "demo"
      STORE_AUTH: "aasd(/)Asa8d811"
    labels:
      - "traefik.backend=vuestorefront.io"
      - "traefik.frontend.rule=Host:vuestorefront.io"
      - "traefik.docker.network=comp_proxy"
      - "traefik.port=3000"
    networks:
      - internal
      - comp_proxy
    links:
      - es.vuestorefront.io:es1
    depends_on:
      - es.vuestorefront.io

Cool! That's what we're trying to achieve in #171
Cezerin - never heard of it before, seems quite promising, but not so active?

@pkarw seems to be not so active but the production audit show high values, but I hope this project go ahead ;)

Me too! :)


updates to load method

@blackwer this is the PR to adjust the load method to locally load the model outside of flatiron resources.

Merging since this seems to be working. Addresses #139


endpoint: have controller which attempts regeneration if past builds failed

Summary

This controller would check what state the endpoint was in, and if the state is any state indicating the endpoint needs to be regenerated, try to regenerate the endpoint. If the endpoint is in a good state, do not regenerate it.
Controller would be marked as failed when an endpoint is failing

Metrics

At what point did we have to retry a regeneration based on a policy change (i.e., conflicting protocols on same port, too many prefix lengths)

For discussion, what types of problems are likely to be resolved by trying again and again?
Failure to regenerate due to BPF compilation or complexity issues are unlikely to ever recover, this really says that developers haven't put good enough safeguards around the datapath code generation.
Perhaps L7 proxy configuration? Temporary outage or failure to configure a proxyport?

Do you intend that there should be this "endpoint regeneration watcher" controller always running, or would it be started when a regeneration first fails and remove itself when it causes a good regeneration?

@joestringer I don't know of exact cases where this may remediate the issue - say we have an intermittent error connecting to the proxy, or some PolicyMap plumbing operation goes wrong (not sure entirely whether this is possible). I think at least trying again with some form of a backoff is better than sitting there without attempting to realize the desired state if the desired state was unable to be realized before.
What would be ideal, is if in the controller, we checked not just the state of the endpoint, but whether the realized state does not match the desired state. I think that to start, checking the state of the endpoint is a good starting point.

This is blocked by the state machine changes for the endpoint which @tgraf is working on.

Removing this from v1.4 since this wasn't completed in v1.4.

Fixed by https://github.com/cilium/cilium/pull/9203


pacman subscription refers to branch that DNE

https://github.com/open-cluster-management/application-samples/blob/main/subscriptions/pacman/subscription.yaml#L10
indicates apps.open-cluster-management.io/github-branch: pacman-sample
Results:
$ oc apply -k subscriptions/channel
$ oc apply -k subscriptions/pacman

$ oc describe subscriptions/pacman-sample -n pacman-sample
...
Status:
  Last Update Time:  2021-08-16T23:53:35Z
  Phase:             PropagationFailed
  Reason:            failed to initialize Git connection, err: Failed to clone git: https://github.com/open-cluster-management/application-samples.git branch: refs/heads/pacman-sample err: couldn't find remote ref "refs/heads/pacman-sample"

The same bad reference also exists in subscriptions/subscribe-all/subscription.yaml


Consider tagging "releases" to help us make sense of PCB and firmware revs

I have v1 of the PCB and was getting ready to assemble with my daughter and see now that you have a V2 of the PCB and firmware has changed etc. It isn't clear to me which commit to checkout to have a working, coherent "v1" repository that should mostly just work if I follow directions in the READMEs.

All the demos work with the firmware as it is. The PCB mainly has cosmetic changes, there are just two functional changes related to voltage monitoring and speed sensing. Neither are currently used the app. I did not get a chance yet to update the code for the Arduino. But it will have a flag for PCBv1 and PCBv2.

Thanks for responding, @thias15 To be clear, I'm not talking about build flags etc, I'm talking about commit tagging in git.
I think you have an amazing project here that likely has legs (1.4k stars already!).  I think you and the community around this will have fewer headaches over time with a sensible versioning and release tagging strategy sooner rather than later.  Imagine a future where you are on the 7th rev of the PCB and there are 1000 commits in source, and my arduino breaks... I just want to be able to checkout v1.0.0 (the release that I build my bot from, as opposed to 7.1.8 or whatever you happen to be on at that time) and have 100% confidence that the firmware and source will work. :-)
In any case, keep up the awesome work, this is a fantastic project. I'm hoping to complete my first build of it with my daughter today.

@DiggidyDave Yes, I understand and there will be tagged releases in the future for sure. However, there are still a few small things I'm working on which I wanted to iron out before tagging the first release. I want to make sure at least a few people were able to complete all steps in the project. The challenge is also to find a good release strategy across the different components (e.g. people may have the old PCB, but still like new features in the firmware, the Android app, etc.) Ideally, each component could be tagged seperately, but I guess the only way to achieve this would be seperate repos and then add them as submodules. Then, it could be that releases of submodules will not be compatible with each other. I guess, in addition there could be releases across the repo with the submodules. If you have some suggestions, please let me know. As I mentioned, for now my plan was to add build flags to the Arduino code to support different PCBs.

Agreed, I almost mentioned having independently versioned "projects" but that felt heavy for the current young state of the project. Cool, thanks for your responses! If I have any lightweight ideas/suggestions in the near term I'll pass them along.

Just for your info, we just released v0.1.0.


Support nuking elasticache replication groups

Description
Fixes #333
These changes introduce support for nuking elasticache clusters that are members of a replication group. The single nuke method has been extended to handle both cases:

Cache cluster is not a member of a replication group, and so can be deleted directly
Cache cluster is a member of a replication group, which itself must then be deleted, because attempting to delete the member cache cluster itself will fail as long as the replication group exists.

In testing against a deployed Ref Arch, these changes resolve the issue observed in #333.

TODOs
Read the Gruntwork contribution guidelines.

[x] Update the docs.
[x] Run the relevant tests successfully, including pre-commit checks.
[x] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[x] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide

@yorinasub17 Thanks for reviews! Looks like the tests are finally passing, so this one is ready for another look when you have a moment.

Thanks for reviews! Going to merge this in now.


How to write Method if a request has both GET and POST method?

example , if .zen has both GET and POST how to write?
public var path: String {
        switch self {
        case .zen:
            return "/zen"
        }
    }
public var method: Moya.Method {
        switch self {
        case .zen
          return       //return what ?
        }
    }

The solution is to use two different enum cases that return the same path. Maybe fetchZen and createZen.

OK，it seems a good idea ~


Notify users of auto-import or make it more obvious (ES6)

Issue Type: Feature Request
I accidentally imported a package after typing a function name that exists in a package that isn't part of our build. The webpack build started failing but I didn't notice right away.
The import was added to the very top of the file above our license comment which made it difficult to see. I spent 30+ minutes trying to find what could possibly cause the issue.
I'm not actually sure what key sequence I made to auto-import that package, but it must have been a typo on my part.
VS Code version: Code 1.49.2 (e5e9e69aed6e1984f7499b7af85b3d05f9a6883a, 2020-09-24T16:29:41.983Z)
OS version: Windows_NT x64 10.0.18362

Auto imports are added when you accept a suggestion. Here's an example of what we show for them:

They should always start with Auto import. The added import will also show in source control if you are using that
Any suggestions on making them more obvious?

A few ideas:

A confirmation banner that gets focus. It could use the same UI element as the command palette. "Are you sure you want to add foobar package" (Yes/No)?
Place auto imports below the first comment if a comment exists at the top of the file.

I have a similar issue. Vscode is auto importing packages that aren't even a part if the current project.
What's the point of that? type 'expect' hit enter and it imports Chai.
Am I doing something stupid?

The import being added above the comment sounds like a bug. Can you please open a separate issue for that with some example code
Regarding a notification: we've had auto imports for something like three years now and have not see other requests for making them more obvious. I am very hesitant to introduce confirmations or notifications or anything else that could slow user down or make the editor feel like it's getting in the way of the programmer.
If there's a specific case where you feel auto imports are being incorrectly added, it may be a configuration issue with your project. If you've tried that but still are running into problems, open another issue with a small example and we can investigate further

@mjbvz I think the main issue is the context menu is too fast in some cases.
Whatever I typed brought up the menu faster than I realized and I had already pressed Enter or Tab without seeing what change I was accepting. That's great when you're typing something and you know exactly which item is going to be selected before-hand, but if it's something unexpected, then you'll run into the problem I had.
By the way, this doesn't only happen for auto-imports, this happens to me for other auto-complete options as well. Since the auto-complete actions replace text in-line it's obvious that you did something wrong. You will see the change immediately. In the case of the auto-import, it wasn't obvious and hard to find what I accepted.
I shouldn't have to stop and read the context menu. I know it's a tricky UX problem. Of course we want things to be fast, but it also shouldn't interfere with what I'm typing.


use redirects written from wordpress

This PR makes changes required to utilize the live set of redirects written from wordpress by the updated publishing plugin.

It changes the build process to run the deploy redirects script at the end of the S3 interaction process
Deletes the old manually uploaded redirects file
Updates redirect creation script to pull from new redirects file
Augments endpoints file to include new redirects endpoint to be pulled from WordPress
Removes the legacy github pages deploy step

I like it.
Throwaway idea: moving the assign.js script into a published GitHub Action might be a fun project for the future.


Adds form field font weight variable

User agent stylesheet defaults to a font weight of 400.

Creating a setting for this is fine but I think inherit should also be part of the reboot.
https://github.com/freshheads/maatcss/blob/develop/generic/_reboot.scss#L139

Fixed 👍🏻


About the medal in the corner

For me it appear when i toggle the scorebard during the freezecams, maybe put medal_width to 0 may fix it ?

Has this happened to you recently? I haven't seen it happen in a long time, but that is an interesting theory. I'll try that out when I next play.

Yes everytime on casual

I'll close this for now since it's a duplicate of #307. I haven't been able to replicate the toggle scoreboard thing as of yet, but I'll keep messing with it. thanks for the tip :D


Extensions have no chance to clean up on close

VSCode Version: 1.49.0-insider
OS: Linux x64 5.7.17-200.fc32.x86_64

Steps to Reproduce:

Clone and open in VS Code: https://github.com/zawys/deactivate-test
vsce package
Install manually
→ "activate" is written everywhere as expected
Disable extension
→ "Reload required"
Reload (or Close)

Actual result
$ cat /tmp/deactivate-test/fs_log
init
22217.216092680 activate A
22217.216092680 activate C
22217.216092680 activate E
22223.367494563 deactivateInstant A
22223.367494563 deactivateInstant C
22223.367829940 dispose A
22223.367829940 dispose C

$ grep deactivate-test "$HOME/.config/Code - Insiders/User/settings.json"
    "deactivate-test.deactivate-test-activate": "22217.216092680",
    "deactivate-test.deactivate-test-deactivateInstant": null,
    "deactivate-test.deactivate-test-deactivateEarly": null,
    "deactivate-test.deactivate-test-deactivateLate": null,
    "deactivate-test.deactivate-test-dispose": null,

$ cat /tmp/deactivate-test/tee_log
22217.216092680 activate

Comment out the function call to vscode.workspace.getConfiguration in log and the output is:
$ cat /tmp/deactivate-test/fs_log
init
22109.498115667 activate A
22109.498115667 activate C
22109.498115667 activate E
22133.232153312 deactivateInstant A
22133.232153312 deactivateInstant C
22133.232153312 deactivateInstant E
22133.232600389 dispose A
22133.232600389 dispose C
22133.232600389 dispose E
22133.283829548 deactivateEarly A
22133.283829548 deactivateEarly C
22133.283829548 deactivateEarly E

$ grep deactivate-test "$HOME/.config/Code - Insiders/User/settings.json"
    "deactivate-test.deactivate-test-activate": null,
    "deactivate-test.deactivate-test-deactivateInstant": null,
    "deactivate-test.deactivate-test-deactivateEarly": null,
    "deactivate-test.deactivate-test-deactivateLate": null,
    "deactivate-test.deactivate-test-dispose": null,

$ cat /tmp/deactivate-test/tee_log
22109.498115667 activate

Observations:

(1) Terminal processes are killed before extensions have any chance to do it themselves (more properly).
(2) Setting configurations on exit/reload is not possible.
(3) Trying to set configurations on exit/reload somehow stalls setTimeout handlers afterward.
(4) The extension host process seems to be terminated instantly on reload when debugging an extension.
(5) When not debugging, it seems to have around 5s of time until forcibly terminated, so the deactivateLate part is never executed.
(6) Disposing and deactivate are executed in parallel.

Expected result

(1) & (2). Give extensions time to do finishing operations on the UI, like closing windows, exiting terminal process, changing configuration.
(3). Operations should fail with an expressive exception when not available.
(4). Maybe ok, but that leads to workspace pollution while debugging.
(5). Ok, but should be documented.
(6). (Sync) disposing should be executed before (async) deactivate.

Remarks
I need it for an extension’s cleanup tasks, else some temporary files will pollute the repository.

Did you verify that your extension was actually activated?

Hi!

Did you verify that your extension was actually activated?
Now yes. I created a test extension and updated the description.

The current workaround for my extension is to use ExtensionContext.globalState to keep continuously stored what should be cleaned up under what circumstances and do that when VS Code starts. However, that does only limitedly work for terminal processes and requires that the extension is activated at startup.

@zawys Your observations are correct, but the behaviours you have noticed are as designed.
A VS Code window is backed by a renderer process and an extension host process. Terminal processes are spawned from the renderer process via the extension host API (vscode.d.ts). Most of the extension host API is actually serviced by the renderer, so for example when an extension wants to create a new terminal, a message is sent to the renderer and the renderer does it. Or when an extension wants to write to the user settings.json, a message is sent to the renderer and the renderer does it, etc.
When closing the window, the renderer process goes down immediately. The extension host process becomes orphaned and has 5 seconds to go down. The renderer process does not wait for extensions in any way.
This is an intentional design decision we took. When we designed this, we have suffered multiple times as operating systems would not shut down, especially when needing to leave and catch a train, etc. Always the reasons appear to be important: an update had to be applied, an application would veto the shutdown, etc. But in comparison with missing the train, that is not so important at that time. We have decided that VS Code should not be like that. As a user, if I close VS Code, it must go down ASAP.
This requirement hits extensions and it means that extensions must be authored with this constraint in mind. Deactivate is not a time to write to user settings. To be honest, the reason we have deactivate is for e.g. cleaning up costly things, like e.g. suppose a server is up and running somewhere and must be shut down, a quick http request can be made, etc. All the rest of the things must be resilient to crashes anyway, so spawned processes must be ready that the extension host process is brutally killed anyways.

Thank you very much for your detailed reasonable explanations!
Now I found createTerminal(options: ExtensionTerminalOptions): Terminal, which allows to spawn the "fragile" process on the extension host and forward in and output between the renderer and the fragile process (via the extension host). I think, that should do it.
The documentation on the exit procedure could be extended, though.

@alexdima Could you please remote the “needs more info”?


Added pending keyword to crypto-square test

Work on #133 (@Trevoke)

Hey @ErikSchierboom ,
I accidentally merged your two CryptoSquareTest changes out of order. So, now there is a merge conflict with this one.
Do you mind resubmitting with the corrected CryptoSquareTest filename?
Thanks

@ricemery Of course! I will resubmit later.

@ricemery Rebased!


nccl buildig failed without specifying NVCC_GENCODE

What's the issue, what's expected?:
nccl building failed if we don't specify NVCC_GENCODE. According to nccl documentation, specifying NVCC_GENCODE only speeds up the compiling. It should not fail even we don't pass NVCC_GENCODE.
How to reproduce it?:
git clone https://github.com/Azure/MS-AMP.git
cd MS-AMP
git submodule update --init --recursive
cd third_party/nccl
make -j src.build

Log message or shapshot?:

Additional information:

We change from nccl to msccl now. It will hang when building msccl without specifying NVCC_GENCODE. The latest msccl has solved this problem. Let's wait for the new release of msccl.

We change from nccl to msccl now. It will hang when building msccl without specifying NVCC_GENCODE. The latest msccl has solved this problem. Let's wait for the new release of msccl.

Hi, to clarify, it's not hanging but due to build time very long (hours). It should succeed eventually. And the long build time issue is not solved in latest msccl.

Got it. Then this issue can not be reproduced with MSCCL. So close it.


Submitted HL7 full ELR reports are validated as HL7 batch or messages

User Story:
As ReportStream, I want to validate incoming HL7 full ELR reports, so I it can be determined if they are valid HL7 reports.
Description/Use Case
We need to validate the incoming payload submitted by a sender to ensure it is a valid HL7 batch or message.  This will also result in rejection of the report if it does not pass the validation.  Note that more detailed validation could be added in the future.
Risks/Impacts/Considerations

If we do not validate the incoming files, they may cause errors downstream

Dev Notes:

Use the HAPI HL7 library functionality to validate the structure of incoming files
We will have to use this same initial validation in the HL7 parsing portion too.

Acceptance Criteria

The reports/waters API returns a successful response if the HL7 payload is validated.
The reports/waters API returns a BAD_REQUEST response if the HL7 payload is invalid.
The reports/waters API returns errors as part of the JSON response when an HL7 payload is invalid (similar of how it is done with COVID).

All AC met accordingly.


Combine Kepler/K2 and Gaia DR2 large datasets

Description
The vast Gaia DR2 data release will dramatically improve our knowledge of distances to, and space motions of, Kepler/K2 targets.  This enhanced astrometric information has broad applications for science projects from young stars to planetary system parameters and more.  From a practical standpoint, the revised positional information can be used to inform scene modeling for point spread function photometry, resulting in accurate photometry in crowded fields.  The project would include opportunities to visualize interactively the large Kepler/K2 and Gaia datasets with dask and holoviews, two cutting-edge python libraries.
Simplest deliverables are:

EPIC to GAIA id cross-match table
EPIC ids associated with more than one source in Gaia

Bonus Deliverables:

3D visualizations of the Kepler/K2 fields

Benefits

Reduce replicated effort from many folks doing the same thing
Getting to learn and apply dask or similar tools to handle such large datasets

Costs

Having to learn and apply dask or similar tools to handle such large datasets
Computational limitations of cross-matching

Dan Huber has a funded NSF proposal to combine the GAIA DR2 and KIC (and already has some results out using DR1). I don't know if he is planning on tackling EPIC as well, but it wouldn't surprise me if he is --- worth asking him and coordinating if so.

Asked Dan about plans on EPIC and GAIA, and he says "Yes this is on our Gaia todo list, but in practice the Kepler targets will take priority and it'll depend on how quickly my grad student Travis will plow through the data. I expect that the impact will be smaller though since most observed K2 targets are M dwarfs, for which radius is mostly controlled by Teff and metallicity."

Megan Bedell recently released a cross-match of the gaia/kepler/k2/nexsci catalogs:
http://gaia-kepler.fun/


how to config if use metadata version v12 ?, which version  is support metadata  v12?

generally, I suggest to use git blame, which will tell you which is the latest commit that uses V12


Hotkey to toggle

Adds a hotkey to toggle the detailed tooltips.  By default, the detailed tooltips are on and the hotkey is F2.  Will not affect existing users or new installs.
The Detailed Card Progress is a fantastic mod.  I wanted to only know about one thing that I was curious about and wanted to discover the rest of the mechanics myself.  Currently the only way to do this is to exit the game, disable the mod, run the game, check the result, and then undo that process.
This will not affect existing installs.
From the change log:

Adds a hotkey to enable/disable the enhanced tooltips.
By default the tool tips are enabled and the hotkey is F2.

.gitignore

Modified to ignore Publish.ps1 for local file publishing.
Ignores VS .user configurations.

CstiDetailedCardProgress.csproj

Uses an optional GameAssemblyPath variable to allow machine
specific install directories.

Settings table formatted for NexusMods:
[font=Courier New]
| Name    | Default | Description                                    |
| ------- | ------- | ---------------------------------------------- |
| Enabled | true    | If set to true, will show the details tooltips |
|         |         |                                                |
| HotKey  | F2      | The key to enable and disable the tool tips    |
[/font]

A nice feature, thanks!

Thanks!  And thank you for the mod.  It is really nice.


hssi: Fix RHEL_8.2 build issue

Fix hssi port changes to make backward compatible
with old CLI11 versions
Signed-off-by: Nikhil Rane<EMAIL_ADDRESS>

Coverage decreased (-0.03%) to 64.457% when pulling 2b34299812219a412b4602626d38f10f4c52664d on ranenikhil19:nrane/fix_rhel_8.2_build into 720790926ce8cbf3c22ac03c570a4d440dfd3d11 on OPAE:master.

@tswhison @anandaravuri i made this change to make hssi code compile on RHEL 8.2 and fix the issue reported.
Also attached is the test report with this patch
log_rev1_june_16.txt
log_rev2_june_16.txt
.
I have verified with this patch on bhawans build system which is centos 8 and build was success.
Request to approve and merge this PR  to fix  RHEL 8.2 build issue .

CI got hung.  Force merging the change.


make stylish-haskell and hlint available inside nix-shell

Description
make stylish-haskell and hlint available inside a nix-shell
Linked issue

Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[X] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

Great! works for me too.


Support scrypt kdf with non-default params

! @erikd-ambiata @olorin

Code seems fine, but I seem to be missing some context on this.
Where is will this be called from? Looking at that rest of the code, it looks like it would be possible to do something like scryptParams 1 1 1 which would almost certainly result in very poor crypto properties. Is it worth guarding against this?

Context explained IRL.

I'm not sure this is the right way to do this. One of the goals of tinfoil is to present a simple, unified interface with the properties that a) there is an obvious way to do everything that tinfoil can do and b) the obvious way is also the correct way (aka, make it really hard to shoot yourself in the foot). As I understand it, the motivation for this change is to be able to use two different workfactors for different applications with differing requirements; if this is the case I think the right way to expose this in tinfoil is to have two different KDF instances, {high,low}WorkFactorScrypt or something like that.

(Separately from the interface issue, this implementation incorrectly uses the same MCF prefix as defaultScrypt, which will result in verification failures when the resulting KDF instance is used.)

Sorry we didn't get a chance to catch up when planned @charleso. Free whenever you are.

👍


Add support for Django 4.2

I'm confused about why PyPy tests are failing? 🤔

I'm confused about why PyPy tests are failing? 🤔

probably https://github.com/django/asgiref/issues/393

Maybe we could temporarily put a upper bound on asgiref during testing?

@vinnyrose Thanks for tracking down the CI issue!

@vinnyrose Your changes look good to me. Anything else needed to merged this PR? Thanks.

@vinnyrose Your changes look good to me. Anything else needed to merged this PR? Thanks.

Thanks for the reminder, I meant to get to this in the last few days. Hope to have this in by the weekend.


Lifecycle events for rendered components sometimes don't fire

Hey guys, so I don't know if I'm doing something wrong or maybe it's a bug. So, for the following code (which I cut from the README and only added lifecycle event handlers):
const Home = () =>
 console.log("home created")} ondestroy={el => console.log("home destroyed")}>Home

const About = () =>
 console.log("about created")} ondestroy={el => console.log("about destroyed")}>About

const Topic = ({ match }) =>
{match.params.topicId}

const TopicsView = ({ match }) => (

 console.log("topics created")} ondestroy={el => console.log("topics destroyed")}>

Topics

        <Link to={`${match.url}/components`}>Components</Link>

        <Link to={`${match.url}/single-state-tree`}>Single State Tree</Link>

        <Link to={`${match.url}/routing`}>Routing</Link>

    {match.isExact &&
Please select a topic.
}

    <Route parent path={`${match.path}/:topicId`} render={Topic} />

)

The rest is exactly the same. When the page loads at /, I get home created as expected. When I switch from Home to Topics, I get home destroyed and topics created as expected. However, when I switch from Home to About, I get nothing. If I switch from About to Home, also nothing. Am I missing something?

Hi, @jlfgomes. The routes are returning similar elements, so they are being recycled. To avoid this, you can use a key in the root element of each route to uniquely identify it within its siblings.

Yep, that works! Thanks for the reply!

@jlfgomes If that fixes it, can you please close? :)

Sorry, I got so excited I forgot to close, lol. Thanks again!

how to use a key ?

@willin Did you read this part of the documentation https://github.com/hyperapp/hyperapp#keys ?
If this is unclear do not hesitate to ask further questions on Hyperapp issues or Slack.

oh  i did not notice the readme file updated


pipeline_stream_insert assumes columns are properly ordered

If tuples aren't in the same order as the columns of the stream being written to, we need to reorder them.

I don't think is a bug. There's no way to specify a header of column names when calling pipeline_stream_insert, so it's up to the user to ensure that the tuple being inserted matches the descriptor of the stream being written to.

Currently it's fairly easy to crash a worker with "bad" ordering, so we need to at least prevent that from being possible. It should behave the same as:
create table t (x integer, y text);
insert into t values ('text', 42);
ERROR:  invalid input syntax for integer: "text"

We should probably just make sure that the tuple desc of the continuous transform is equal to the tuple desc of the stream being inserted into.


Problem on display of the GPS track

Describe the bug
There's a strange issue in the displaying of the GPS track, it shows a direct path to the starting point. It should be added that this gpx file is a concatenation of several paths, and it appear that if a path's ending point isn't the same as the start point, it will show a path to the starting point of the complete path.
Screenshots (optional)

the should be only one path from Faroe to Iceland on this map
used path
islande.zip
The issue doesn't show on any GPS editing software
Environment (please complete the following information):

OS: Docker
Browser : brave and firefox

Used app version:

docker-nightly-bullseye

That is a feature. The app draws an arch of two points are far away from
eachother. You can costumize it in tbe settings
-- Sorry for being brief, sent from my phone.
On Sat, 26 Aug 2023, 18:39 lythandas, @.***> wrote:

Describe the bug
There's a strange issue in the displaying of the GPS track, it shows a
direct path to the starting point. It should be added that this gpx file is
a concatenation of several paths, and it appear that if a path's ending
point isn't the same as the start point, it will show a path to the
starting point of the complete path.
Screenshots (optional)
[image: image]
https://user-images.githubusercontent.com/90504445/263476291-1b78b2cf-c4d7-4a5c-b5f1-99877431560c.png
used path
islande.zip
https://github.com/bpatrik/pigallery2/files/12446093/islande.zip
Environment (please complete the following information):

OS: Docker
Browser : brave and firefox

Used app version:

docker-nightly-bullseye

—
Reply to this email directly, view it on GitHub
https://github.com/bpatrik/pigallery2/issues/703, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZKA5SI4FALF53M76EDZXLXXIRFPANCNFSM6AAAAAA37WK2GQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Yes I saw that. The problem isn't the arched path, it's that there shouldn't be a path at all at that place.
Here's how it shows without the arch, on v1.9.5

and here how it shows on any GPS editing software.

That is also a gpx compression issue. You can disable it while it's broken.
( you might need to delete the compressed files in the temp folder)
-- Sorry for being brief, sent from my phone.
On Sat, 26 Aug 2023, 19:31 lythandas, @.***> wrote:

Yes I saw that. The problem isn't the arched path, it's that there
shouldn't be a path at all at that place.
Here's how it shows without the arch, on v1.9.5
[image: image]
https://user-images.githubusercontent.com/90504445/263483485-ec1b7325-fc7c-4b09-9a55-ff5dd46c6905.png
and here how it shows on any GPS editing software.
[image: image]
https://user-images.githubusercontent.com/90504445/263484277-d25be2c1-3e10-4151-8555-9d2c8cff29af.png
—
Reply to this email directly, view it on GitHub
https://github.com/bpatrik/pigallery2/issues/703#issuecomment-1694418044,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZKA5TPUVXGHG4LEQJYPT3XXIXITANCNFSM6AAAAAA37WK2GQ
.
You are receiving this because you commented.Message ID:
@.***>

Hey again.
I tried disabling the GPX compression, and used the new jobs to delete the compressed files and clean the temp folder.
However, now the map either doesn't load at all or makes the tab crash after loading for +30s.
I also tried disabling an re-enabling gpx handling in the parameters and resetted the db, but still no difference.
I also tried disabling the GPX compression in v1.9.5 and I still have the problem.

Can you please check server logs and send a gpx track that causes the issue.

Sorry, last comment was from my work account.
The gpx track is zipped and available in my first comment, as for server logs, here's all that I have :
8/28/2023, 10:24:06 AM[WARN_] Handled error:
ErrorDTO {
  code: 5,
  message: 'credentials not found during login',
  details: TypeError: Cannot read properties of null (reading 'password')
      at UserManager.findOne (/app/src/backend/model/database/UserManager.js:13:81)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async login (/app/src/backend/middlewares/user/AuthenticationMWs.js:148:46),
  request: { method: '', url: '' },
  detailsStr: "TypeError: Cannot read properties of null (reading 'password')"
}
/app/src/backend/model/fileprocessing/GPXProcessing.js:82
            const timeDelta = (Date.parse(list[i].time[0]) - Date.parse(list[i - 1].time[0])); // mill sec.
                                                      ^

TypeError: Cannot read properties of undefined (reading '0')
    at gpxEntryFilter (/app/src/backend/model/fileprocessing/GPXProcessing.js:82:55)
    at Array.filter (<anonymous>)
    at GPXProcessing.compressGPX (/app/src/backend/model/fileprocessing/GPXProcessing.js:87:51)
    at async compressGPX (/app/src/backend/middlewares/MetaFileMWs.js:24:30)

Node.js v18.13.0

The last commit should fix.
yes on v1.9.5 the compression does not work and fails as fix was done later.

Hey again, I confirm this is working great since your last commit. Thank you very much !
However I cannot get rid of the bend now. It ends up breaking the browser when opening the map or just not working. I tried to remove the compressed GPX files and nothing changed. When the map is broken, I have to remove config.json.
I setup a test instance with only the gpx file and it behaved the same. Then again, nothing showed in the logs.

You can disable bending if you put this number to a high value:

Although the issue should not be with the bending. It only adds a few more points. I think your problem that your gpx file is just huge for the app. Yours is 6MB. I usually have only a few hundred KB.
You can try making the compression stronger by making these numbers bigger:

You wont see anything in the logs because the issue is in the browser as it cannot render the file. The server works without an issue.

Hello, I'm sorry I misunderstood those values, and put smaller values instead of higher, that's why it was always crashing...
It's all working great now and I'm down to a 1Mb file with heavier compression.
The bend is also gone now, I just had to empty the browser cache after setting a high value. What is the unit of the bend value ?
Thank you again for your time


(FireFox) Child Window doesn't close after test run, causing next test to launch inside it

What is your Test Scenario?

Test Sharing a Petition to Facebook
What is the Current behavior?

Using FireFox, it looks like (intermittently) the child window / Facebook popup doesn't close at the end of the test. This then causes the next test to be ran in the child window, resulting in a different behaviour (website treats it as a mobile / tablet device, rather than desktop).
When trying to close this pop-up window, I occasionally get:
Cannot close the window because it does not have a parent. The parent window was closed or you are attempting to close the root browser window where tests were launched.

What is the Expected behavior?

Any / All child windows are automatically closed, at the end of a test.
What is your web application and your TestCafe test code?

 I would say it happens 1 in 5 times.
import { Selector, ClientFunction } from 'testcafe';

const getCurrentUrl = ClientFunction(() => window.location.href);

fixture('Petition Share - Child window doesn\'t always close')
  .page('https://www.change.org/?country_code=NZ&lang=en-AU')
  .beforeEach(async t => {
    await t.navigateTo('p/testcafe-for-testcafe-to-investigate-64b3ad13-9a19-4535-8986-fdcf98fee9fc/psf/share');
  });

test('Can share via Facebook on desktop if already signed', async t => {
  await t.click(Selector('.js-facebook-share-dialog'));
  await t.expect(getCurrentUrl()).contains('https://www.facebook.com/login.php');
});

test('Can share via Twitter on desktop if already signed', async t => {
  await t.click(Selector('.js-twitter-share-button'));
  await t.expect(getCurrentUrl()).contains('twitter.com/intent/tweet');
});

Your complete configuration file (if any):

{
  "src": "./tests/**/*.js",

  "assertionTimeout": 10000,
  "pageLoadTimeout": 30000,
  "selectorTimeout": 10000,

  "quarantineMode": false,
  "skipJsErrors": true,

  "disablePageCaching": true,

  "reporter": [
    {
      "name": "xunit",
      "output": "artifacts/test-results/results.xml"
    },
    {
      "name": "spec"
    }
  ],

  "screenshots": {
    "fullPage": true,
    "takeOnFails": true,
    "pathPattern": "${TEST_ID}/${RUN_ID}_${FILE_INDEX}.png",
    "path": "artifacts/screenshots"
  },

  "videoOptions": {
    "singleFile": false,
    "failedOnly": true,
    "pathPattern": "${TEST_INDEX}/${RUN_ID}_${FILE_INDEX}.mp4"
  },
  "videoPath": "artifacts/recordings"
}

Your complete test report:

It hangs after the 2nd test completes, never writing back to the console.
testcafe firefox
Using locally installed version of TestCafe.
The "browsers" option from the configuration file will be ignored.
 Running tests in:
 - Firefox 79.0 / macOS 10.15

 Petition Show Action Panel
 ✓ Can share via Facebook on desktop if already signed

Screenshots:

![Screenshot 2020-08-13 at 2 29 04 PM](https://user-images.githubusercontent.com/37812673/90190587-25e60d80-dd74-11ea-82e7-8e37c6403a3f.png)

Steps to Reproduce:

Go to my website ...
Execute this command...
See the error... If not... re-run the tests (seems to occur around 50% of the time

Your Environment details:

testcafe version: 1.9.0
node.js version:   12.14.1
command-line arguments:
browser name and version: Firefox 79.0
platform and version:  Mac OS 10.15.6
other:

Hi Rob,
Thank you for contacting us. We reproduced the issue. We need some time for investigation, please bear with us.
By the way, we noticed that the issue can be reproduced only if video recording is on. As a workaround, you can try to switch it off. Also, you can try to run tests with the --disable-multiple-windows option.


Multi Region Config

Is this feature request related to a new or existing Amplify category?
No response
Is this related to another service?
No response
Describe the feature you'd like to request
Options for multiple regions, to protect from outages, to allow for ensuring data is stored or sync'd depending on different rulesets (ie. for ensuring data is stored in the users region, or ensuring it is available during outages in other regions etc.)
Describe the solution you'd like
amplify region add
? Please pick region: us-east-1, us-west-1, etc.
? Please choose load balancing type: By Location, Round-robin, etc.
? Should user information be stored in only their local region, or should it be sync'd
? Please choose syncing for S3 deployments: automatic, manual
? Cognito syncing: [options]
? DynamoDB syncing: [options]
Describe alternatives you've considered
Manually doing this is a pain.
Additional context
AWS Datacenter seem to go have outages fairly frequently recently....
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request
[ ] ⚠ This feature might incur a breaking change

This could potentially be expanded to create the ability for api's to be protected by region, or to have alternate implementations in different regions in the graphql [ie. @auth({region:us-east1, group:admin, access:[region:us-east-1,allow:[read,write]]},{region:eu-west-1, group:admin, access:[region:eu-east-1,allow:[read,write]]}) would only let admins in us modify data stored in the us, and eu admins to only let admins in the eu...


Refactor/core modules

[X] Have you provided a meaningful PR description?

The PR is an initial set of changes to clean up and for modularization of the existing compiler front end to ease of development of next set of major functionalities in numba_dpex. The changes in the PR are pretty limited as I intend to do the work incrementally.
The changes included are:

Move the numba_dpex.codegen.py file to numba_dpex.core module. The core module will hold all files related to the compiler front end.

Add a new numba_dpex.core.dpex_exceptions module to have all custom exceptions  in one place. Right now dpex exceptions are a mishmash of ValueError, TypeError, etc. that lead to a bad user experience (e.g. see #777).

As a template for a custom exception, create a new KernelHasReturnError class that replaces the previousassert_no_return function that used to raise a TypeError.

Renamed the examples/sum.py to examples/vecadd.py.

[X] Have you added a test, reproducer or referred to an issue with a reproducer?

[X] Have you tested your changes locally for CPU and GPU devices?

[X] Have you made sure that new changes do not introduce compiler warnings?

[ ] If this PR is a work in progress, are you filing the PR as a draft?

Most of the changes are now in main. I will open separate PRs for the larger kernel API refactor work.


[RESOLVED] Unavailable by ICMP ping

Problem started at 21:34:14 on 2022.08.10
Problem name: Unavailable by ICMP ping
Host: ZO-FG
Severity: High
Operational data: Down (0)
Original problem ID: 3450
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23123&eventid=3450

Problem has been resolved in 2m 0s at 21:36:14 on 2022.08.10
Problem name: Unavailable by ICMP ping
Host: ZO-FG
Severity: High
Original problem ID: 3450


Split apk decompilation error

Information

Apktool Version - 2.4.1
Operating System - Windows
APK From? - for example, combined from parts https://apk.support/download-app-ru/com.garmin.android.apps.connectmobile/1588057200_vs-4.30

https://ru.files.fm/u/f5ckhbew
after decompilation, the apk part is lost, you can see the rebuilding apk

after recompilation:

used BatchApktool + plugin https://4pda.ru/forum/dl/post/19526276/AntiSplit-G2_2020-04-25.zip

Apktool don't support multiple package in resources.arsc

Split apks and resource packages with more than 1 default package are not supported. Apktool is currently hardcoded to pull only package.
You are looking for this feature request - https://github.com/iBotPeaches/Apktool/issues/2218

Information

Apktool Version - 2.4.1
Operating System - Windows
APK From? - for example, combined from parts https://apk.support/download-app-ru/com.garmin.android.apps.connectmobile/1588057200_vs-4.30

https://ru.files.fm/u/f5ckhbew
after decompilation, the apk part is lost, you can see the rebuilding apk

after recompilation:

used BatchApktool + plugin https://4pda.ru/forum/dl/post/19526276/AntiSplit-G2_2020-04-25.zip

can you please share this BatchApktool + plugin. The link is not valid anymore.

Information

Apktool Version - 2.4.1
Operating System - Windows
APK From? - for example, combined from parts https://apk.support/download-app-ru/com.garmin.android.apps.connectmobile/1588057200_vs-4.30

https://ru.files.fm/u/f5ckhbew
after decompilation, the apk part is lost, you can see the rebuilding apk

after recompilation:

used BatchApktool + plugin https://4pda.ru/forum/dl/post/19526276/AntiSplit-G2_2020-04-25.zip

can you please share this BatchApktool + plugin. The link is not valid anymore.

@Ratul-Learner
Link works for users registered on 4pda, I did not take this into account when I provided the link. It is clear that no one is going to register there, since the forum is Russian-speaking and there will be problems with registration and login, based on the impossibility of reading the captcha. I can provide a link to a newer version, but that won't change anything: issue closed.

@Ratul-Learner
Link works for users registered on 4pda, I did not take this into account when I provided the link. It is clear that no one is going to register there, since the forum is Russian-speaking and there will be problems with registration and login, based on the impossibility of reading the captcha. I can provide a link to a newer version, but that won't change anything: issue closed.


client.connected_ig_accounts or client.ig_business_accounts  response empty []

I use App mode dev with account evaluate instagram
client.connected_ig_accounts or client.ig_business_accounts
response empty []

@ZephiroRB May be you will have to check if the access_token has correct permission to view those data.

@ZephiroRB
Hi.ZephiroRB.
Maybe, Maybe, your app unsupported
yet, that some scope must valid to execute connected_ig_accounts or ig_business_sccounts.
For Example...
config/initialize/devise.rb(this is sample file, its support for facebook oauth via devise)
  config.omniauth :facebook, Settings.facebook.client_id,
                  Settings.facebook.client_secret,
                  scope: "pages_show_list, instagram_basic",
                  callback_url: Settings.facebook_oauth2_callback,
                  client_options: {
                    site: 'https://graph.facebook.com/v7.0',
                    authorize_url: "https://www.facebook.com/v7.0/dialog/oauth"
                  }