Use buf-action in CI

This updates CI to use the new buf-action replacing buf-setup, buf-lint, buf-breaking and buf-push unifying these tasks as one. The behaviour tries to keep consistent with the old CI behaviour. Push is only done on merge to main. This is enforced by the env production. However the CI now runs checks in the pull_request event for PRs and then on push events once merged to main. Breaking change detection is kept to the BSR remote. Added is format as an additional check.
Tasks remaining:

[ ] replace lint and breaking status checks for the buf checks job.

The behaviour tries to keep consistent with the old CI behaviour.

I don't think this should be our goal as we are migrating to the new action. I think when migrating toward the new action, we should assume by default we want to have the default behavior the GitHub action provides, unless there is a specific reason to deviate.

@nicksnyder behaviour here is enforced by the environment: https://github.com/bufbuild/knit-proto/actions/runs/9391209655
Secrets are guarded to the production environment on the main branch. I've taken this as a requirement for this repository.

@jhump can you share context on how/why we are using GitHub environments in this repo?

@nicksnyder, I'm afraid that I have no idea. Strangely, that line in .github/workflows/buf.yaml is from the very first commit in this repo, yet it does not exist in its predecessor (an internal-only repo that has since been archived: https://github.com/bufbuild/knit-api-archive). Maybe Infra did something here to constrain the push action or to make it work? I don't actually know how environments work or what exactly that was intended to do. And unfortunately, I am not able to find any threads in Slack where this was discussed. Sorry 🤷.

Ok, thanks for the context @jhump.
@emcfarlane can you update this PR to be your original commit https://github.com/bufbuild/knit-proto/pull/8/commits/30c25e99a34e1afcff67c69fecd17a99c84a173b and then we can work on making whatever environment changes to make it green.
@rubensf @DMarby can you help fix the configuration on this repo so we can either push to "production" environment from branches or just not have/use environments at all? (If we need an environment, maybe we should be clear that the environment is actually called "BSR" or "buf.build")

@nicksnyder switched to default behaviour.


error while producing the *_SJ.out.tab file

Hi,
I encountered the following error during the alignment step while finder was outputting the *_SJ.out.tab file
cat Finder.output
Traceback (most recent call last):
File "/usr/local/bioinfo/src/Finder/finder-113203c/finder", line 640, in
main()
File "/usr/local/bioinfo/src/Finder/finder-113203c/finder", line 601, in main
orchestrateGeneModelPrediction(options,logger_proxy,logging_mutex)
File "/usr/local/bioinfo/src/Finder/finder-113203c/finder", line 385, in orchestrateGeneModelPrediction
alignReadsAndMergeOutput(options,logger_proxy,logging_mutex)
File "/usr/local/bioinfo/src/Finder/finder-113203c/scripts/findGenesFromExpression.py", line 313, in alignReadsAndMergeOutput
selectHighConfidenceSpliceJunctions(options,1,condition)
File "/usr/local/bioinfo/src/Finder/finder-113203c/scripts/findGenesFromExpression.py", line 105, in selectHighConfidenceSpliceJunctions
condition,junctions_to_be_discarded,junctions_to_be_retained=selectHighConfidenceSpliceJunctionsPerCondition([condition,options,round])
File "/usr/local/bioinfo/src/Finder/finder-113203c/scripts/findGenesFromExpression.py", line 46, in selectHighConfidenceSpliceJunctionsPerCondition
chromosome,j_start,j_end,strand,intron_motif,annotated,uniq_reads,mm_reads,max_overhang=line.strip().split()
ValueError: not enough values to unpack (expected 9, got 8)
What should I do?

Hello @chklopp,
Thank you for reporting this issue. Could you please attach the metadata file and the *_SJ.out.tab files? Please attach all the *_SJ.out.tab files. It will help to figure out the problem faster.
Thank you.

metadata.tsv file
http://genoweb.toulouse.inra.fr/~klopp/Finder/metadata.tsv
*_SJ.out.tab file
http://genoweb.toulouse.inra.fr/~klopp/Finder/SRR1025320_round1_SJ.out.tab

Hello @chklopp,
I ran the entire program from my end but it did not produce the error you reported. Could you please remove the output directory and run it again?
Thank you.

This did not work.
Do you know the command line run to generate *_SJ.out.tab from *_Aligned.sortedByCoord.out.bam ?
I would like to check if there is something wrong in my bam file.

Hello @chklopp,
Thank you for checking it out. It is STAR that generated the *SJ.out.tab files during the alignment step. FINDER reads in that information and attempts to understand if the splice junctions are valid and also seen in other RNASeq samples. Could you please tell me the genome which you are annotating? During my test run I downloaded it from ensembl. I did notice that there was one line in the SJ.out.tab file which did not have 9 columns. Could you please send me the Log.out file for the RNASeq sample alignment? Also which version of STAR are you using? I will try to solve this from my end but I might have to get in touch with the developers of STAR to sort this out.
Thank you.

Hello @chklopp,
Thank you for sending me the log file. I see that the execution has completed without any obvious error. I will post on STAR's github to see if they can help us out.
Thank you.

Hi @chklopp,
I think you have checked out Ales's reply about the issue you are facing. Will it be possible for you to run finder on a different system?
Thank you.


DRILL-6953: EVF-based version of the JSON reader

Reimplements the JSON reader on top of the EVF. Does not yet
handle a provided schema. New JSON parser does not yet reflect
any changes made to the "V1" JSON parser in the last year.
Does not yet handle the Union and List-of-union types.
Enabling those encountered many issues elsewhere in Drill.
Provides more robust (but still limited) handling of JSON
type ambigutities. Handles runs of nulls before the first
non-null value (within the first batch.) Handles runs of
empty arrays before the first non-empty array (again, within
the first batch.) Handles the case where a null value turns out
to be an object or array. Handles reasonable conversions between
types.
Handling ambiguities makes the new parser more complex than
the "V1" version. The new one uses explict states for each
kind of JSON object, where as the old one used implicit states
expressed via if-statements, which can be a bit hard to follow
as the states get more complex.
The new "V2" JSON scan is controlled by a new option:
store.json.enable_v2_reader, which is false by default in this
PR.
Adds a "projection type" to the column writer so that the
JSON parser can receive a "hint" as to the expected type.
The hint is from the form of the projected column: a[0],
a.b or just a.
Reimplements a number of JSON tests to test both the original
"V1" and the new "V2" versions of the JSON reader. Adds many
new tests for the new features of the "V2" parser.
Jira - DRILL-6953.

Some background: this PR includes work completed about two years ago as part of the "row set" (EVF) project. We had to first get the EVF itself reviewed and merged, then we added provided schema support. The first attempt to merge the JSON reader uncovered many issues with batch, record and vector counts. Those have been fixed over the last couple of months. This time, the unit tests pass with the new JSON reader.
This PR leaves the old "V1" reader enabled by default. More testing is required before we enable the "V2" reader by default.
Because this work pre-dated the "provided schema" work, it does not yet support the provided schema. Let's get this version merged, then we can add the additional work needed to support a provided schema.
Also, any work done in the "V1" JSON reader in the last two years is not yet reflected in the "V2" version. We make any such changes after this PR.
JSON is a surprisingly complex and tricky format. Suggestions for further tests or improvements are welcome.

@vvysotskyi bested the review, we need to run tests on test cluster with enabled new JSON reader to see if there are any regressions.

@paul-rogers, looks like TestComplexTypeReader tests fail with enabled v2 reader. Failing tests check obtaining nested array value. There are some other unit tests failures, but most of them are connected with the features which weren't reflected in v2 reader. I think we should fix most of them since in most cases they require just passing additional configs into Jackson.
Also, there are issues with duplicated values in JSON, for example, the following query returns the incorrect result:
select rownum, kvgen(varcharcol) from `json_kvgenflatten/kvgen2.json`

returns
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| rownum<BIGINT(OPTIONAL)>                                                                            | EXPR$1<MAP(REPEATED)>{$offsets$<UINT4(REQUIRED)>,key<VARCHAR(OPTIONAL)>,value<VARCHAR(OPTIONAL)>}   |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 1                                                                                | [{"key":"varchar_1","value":"abc"},{"key":"varchar_2","value":"def"},{"key":"key","value":"value"}] |
| 2                                                                                | [{"key":"varchar_2","value":""}]                                                                    |
| 3                                                                                | [{"key":"varchar_2","value":"hellohow"}]                                                            |
| 2                                                                                | []                                                                                |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Data file content:
{
  "rownum": 1,
  "varcharcol": {
    "varchar_1": "abc",
    "varchar_2": "def",
    "key": "value"
  }
}
{
  "rownum": 2,
  "varcharcol": {
    "varchar_1": null,
    "varchar_2": ""
  }
}
{
  "rownum": 3,
  "varcharcol": {
    "varchar_1": null,
    "varchar_2": "",
    "varchar_2": null,
    "varchar_2": "hello",
    "varchar_2": "how"
  }
}
{
  "rownum": 2,
  "varcharcol": {
  }
}

Previous reader just uses the last value.

@vvysotskyi, thanks for running the tests with V2 enabled. My original thought was to get the basics in with V2 disabled by default in order to reduce the work required. But, since you went ahead and did the full testing, I agree we should include those fixes in the PR as well.

Turns out that the v1 JSON reader will ignore all-null columns. In the test TestStarQueries.testSelStarOrderBy, we execute the following query:
select * from cp.`employee.json` order by last_name

Against the Foodmart file customer.json which has records like this:
{"employee_id":53,...","end_date":null,"salary":...}

The test is written to exclude end_date from a SELECT * query.
In V2, however, end_date is included in the query. One can argue that 'SELECT *' means "return all columns", not "return all columns except those that happen to be null in the first batch."
See DRILL-7522.
Modified the test to expect the old result for the V1 reader, the correct result for the V2. reader.

This PR has grown too large. It will be replaced by a series of smaller, more focused PRs. Will leave this open for now to allow use of this PR as a reference for the new, smaller PRs.

New PRs are posted for some of the reworked way to submit this code. So, closing this one.


Added game Laser Darts

PR Description 📜
Added a new game 'LaserDarts'
Fixes #3654 <your_issue_number>

Mark the task you have completed ✅

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

📸

Thank you soo much for contributing to our repository 💗

Thank you  @VijaySamant4368 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Add in Oracle logo

I have been in touch with Jason Grout and Terry Foor over email about adding the Oracle logo to the Jupyter webpage.  I am a product manager at Oracle.  We use Jupyter in our product. Here is a link to our public documentation that shows we use JupyterLab https://www.oracle.com/data-science/service/?intcmp=:ow:evp:cpo:::RC_WWMK200518P00300:OER400068407&elqaid=39909&source=:ow:evp:cpo:::RC_WWMK200518P00300:OER400068407&elqTrackId=c4e47c3f128041058db997e701a2a82d.  I would like to add our logo to the list of companies that use Jupyter on the website.  Thanks!

I looked through the lighthouse audit, and it seemed that nothing this PR affected changed.


Switch to a new testing system

Frameworks

Framework
Simultaneous Testing
Multiple Processes For Multiple Files
Global Error Handling
Builtin Babel
NPM Downloads/Month

Mocha (current)

✓

Ava
✓
✓

✓

Jest
✓
✓

✓

Request Libraries

Request Library
Uses Promises
Builtin Response Testing
Response Testing Covers Common Use Cases
Reasonable Defaults For Testing
NPM Downloads/Month

Superagent

✓

Supertest (current)

✓

✓

Supertest-As-Promised
✓
✓

✓

Assert-Request
✓
✓
✓
✓

Request

✓

Request-Promise
✓

Node-Fetch
✓

✓

Requisition
✓

✓

Notes

(current) indicates that Koa currently uses it.
If we use a framework with builtin babel support, we can easily use async/await in place of builtin response testing if the library supports promises.
If a request library doesn't have reasonable defaults, we can easily create a wrapper that does.
If the response testing doesn't cover common use cases, a custom helper assertion function can be used instead.

If anybody has any more columns or rows to add to either table, please leave a comment.

feature matrixes don't work for software, as apple so well demonstrates. what sucks about current tests?

I'm skeptical of stuff like this because the ecosystem will be completely different in a few months.

what sucks about current tests?

For one thing, you can't easily detect that there isn't a header (that's the lack of "Response Testing Covers Common Use Cases"). Also in rare situations it would be useful to have a .then to assert something set elsewhere rather than a custom end method. Another thing is that as tests grow speed matters more, and with how split up tests are multiple processes for multiple files will be very important. Lastly, if we do switch our request library to something without builtin request testing, having async/await will be very nice (builtin babel will be required as that isn't in the near future for node).

the ecosystem will be completely different in a few months

I'm not sure it will change that much, given that libraries take time to accumulate popularity. Also, if we find a toolset that works well for the job, there's little reason to change.

feature matrixes don't work for software

I think that in the case of these libraries, they make sense. If you have anything to add that doesn't fit in the table, I can make a note.

In mocha
request(server)
.get('/')
.expect(418)
.expect('Content-Type', 'text/plain; charset=utf-8')
.expect('Content-Length', '4')
.end(function(err, res){
  if (err) return done(err);

  res.headers.should.not.have.property('vary');
  res.headers.should.not.have.property('x-csrf-token');

  done();
})

should be written as
request(server)
.get('/')
.expect(418)
.expect('Content-Type', 'text/plain; charset=utf-8')
.expect('Content-Length', '4')
.expect(shouldNotHaveHeader('Vary'))
.expect(shouldNotHaveHeader('X-CSRF-Token'))
.end(done)

with the helper
function shouldNotHaveHeader(header) {
  return function (res) {
    assert.ok(!(header.toLowerCase() in res.headers), 'should not have header ' + header)
  }
}

@dougwilson Makes sense, I've added a note about that.

This changes feels larger than it probably is, but I'd keep things as they are until v3 and to further analyse tools when ecosystem stabilises post native v8 async/await.

For scale, it took me 1.5 hours to change supertest to assert-request. Changing the testing framework as well would be much larger.

This change feels larger than it probably is, but I'd keep things as they are until v3 and to further analyse tools when ecosystem stabilises post native v8 async/await.

@fl0w :+1: i've been writing my latest tests w/ async and it's been a lot easier
it('should do something', async () => {
  const response = await request('http://...')
  assert.equal(200, response.status)
})

i think it's worth waiting until then

another note: i HATE using should. i prefer if we stopped using anything but require('assert').

@jonathanong +1 on stopping using should, I think that es6 array functions covers pretty much everything it's needed for. What request library are you using with async/await? Also, ava has builtin babel support but IDK if that would slow things down. It also can test files simultaneously, which might result in a speed up.

What request library are you using with async/await?

Take a look at thenables/requisition :)

@coderhaoxin Looks neat. I've added it to the table. Comments from skimming through it:

I like the chaining API
The Readme.md seems to be somewhat broken in parts
Making response.text a promise is interesting, personally I don't think it's necessary
You seem to be handling content-encoding yourself, I don't mind that but you do it in two places (you might want to make a function)
I think memoizing everything is excessive, and a waste of memory
You have "TODO: use lodash" in your code, but only once. I'd highly recommend against that
You have this code twice in index.js, replace it with Object.assign({}, defaults, opts)

@jonathanong How do you transpile your tests? Babel require hook? node -r?

have an entry point like the following:
// index.js
require('babel-register') // or whatever entry point it is now
require('./test1')
require('./test2')

then run it like:
mocha test

ava seems pretty cool just from a simplicity perspective. i don't really like the t argument, though.
the only issue i have with supertest is that it doesn't support promises. not sure if there is any really solid rooms for improvement there

@jonathanong Slightly off-topic, but I wrote and use https://github.com/blakeembrey/popsicle with https://github.com/blakeembrey/popsicle-server to replicate the basic behaviour of superagent while using a promise-based API. The middleware of Popsicle is actually pretty much identical to Koa-2.x now (I actually wanted to use Koa-compose, but I support node 0.10 and the const wouldn't allow me to).

Once Node v7 comes along with async/await support, will we still be testing Koa v2 on earlier versions?

@jonathanong you can hack around with supertest and do something like this
import Test from 'supertest/lib/test';

const {end} = Test.prototype;

Test.prototype.end = function(cb) {
  const self = this;

  if (isFunction(cb)) {
    return end.call(self, cb);
  }

  return new Promise((res, rej) => {
    end.call(self, (err) => {
      if (err) return rej(err);

      res();
    });
  });
};

then
it('should run a basic route', async () => {
  await agent.get('/')
    .expect(200)
    .end();
});

@dtothefp It still has the problem of .expect being confusing/complicated/missing some functionality due to it's design. Still though, better than a callback IMO.

Would it be terrible to start a koa@3-prealpha-branch and start rewriting tests using async/await, requisition and remove should?
Allowing that branch to use async/await as if they're native and a babel as devDependency (effectively just remove babel as dep when native async/await hits the shelves?)

yes，i write 64 tests in two days using ava+supertest-as-promised, port express-graphql to koa v2...
https://github.com/bidanjun/koa-graphql-next.  it's  easy to use...and seems ,not hard work..

Already landed in https://github.com/trekjs/engine/tree/master/test.
trek-engine inspired by koa. Thanks to Koa Team.

I'm always surprised by how many forks Koa has inspired.
I think we'll just rewrite our tests in async once it lands in all supported versions of Node.

maybe consider jest. lol. looked better than ava to me at a glance.

Jest looks like the best I've seen so far.

vote for jest.

yes,use jest...
im use it in an graphql/relay/koa project...and I've been use ava in koa-graphql-next....using jest,could simplely test react and server side,for now,it's faster than ava.js.....
im using jest+supertest-as-promised at current project,no trouble....

we should switch to jest. it would remove the need for the makefile options as a lot of it is just to list the files. the only problem I see is should as I don't think jest can easily inject it.
anyone want to convert the test framework to jest?

[ ] make the current tests work

https://github.com/koajs/koa/issues/559

@jonathanong Would you be okay with tests using async-await (i.e. only support node 7.6+) or is that a leap made to early?

jest look good :)

I'll start working on that.
@fl0w jest comes with babel support. I'll stick with that for now.

Actually, it looks like Travis is currently set to only 7.6. I'll not use the babel plugin for now.

@PlasmaPower alright, I'll hold off then. Let me know if you need/want to off load.
README also updated to 7.6 only support so I would assume using async-await to be fine?

@fl0w it says that only for async/await though.

Actually I guess I misread it. I thought it required a new node if you want async/await, but I think in reality it requires a new node so it has async/await.

For the request library, I think we should use node-fetch. With async/await it looks like the best option.

@PlasmaPower considering https://github.com/koajs/koa/commit/0c2d881b671c0d36c2a944bb525013c61bc1829b I would assume it's ok! :)

I've setup the basis for network tests this way: https://gist.github.com/PlasmaPower/57d361a6d0a90c7a5a6aac890cd2322d
Look good?

yes, we dropped babel from tests and only support node v7.6+ to make life easier! feel free to use async functions in tests

there should be minimal changes in tests though. only moving around test files to make them jest-like and require('should') where appropriate.

One problem I'm having is jest seems to break test-console. I'll look into why and alternatives or fixes.

I fixed that with a custom console.error handler. More problems have arisen though. It seems jest overrides more than I thought.

I haven't really experienced jest breaking anything. Have you tried setting the environment to node?

I'm assuming you meant setting the node environment to test, but jest does that automatically.
The problem I'm currently encountering is that this assertion fails for this test. I have no idea why, the error is quite odd:

Error: non-error thrown: Error: ENOENT: no such file or directory, open 'does not exist'

I'll do some more investigation into that error object.

More information:
process.stderr.write(err + '\n');
process.stderr.write((typeof err) + '\n');
process.stderr.write(err.constructor + '\n');
process.stderr.write(Error + '\n');
process.stderr.write((err instanceof Error) + '\n');

gives
Error: ENOENT: no such file or directory, open 'does not exist'
object
function Error() { [native code] }
function Error() { [native code] }
false

Very odd. JS objects are confusing. I'm also not sure why Jest causes this, it doesn't seem to be messing with the Error object as I initially thought.

@PlasmaPower I think jonathanong was referring to omit jest to mock a browser environment by having following in package.json:
{
  "jest": {
    "testEnvironment": "node"
  }
}

@fl0w Oh, I didn't know jest did that. I'll try changing that and see if it does anything.

The error type problem is still maintained, but I'll keep it in the config of course.

I've pushed my work to this branch if anyone's interested: https://github.com/PlasmaPower/koa/tree/jest-tests

I'm getting more and more wary of jest. It's breaking stuff knows no bounds. The basic problem is that Node's native libraries (fs, http) will have a different version of objects than JS. This causes numerous problems:

in Koa: err instanceof Error fails with a Node fs error + jest
in node-fetch: headers[prop] instanceof Array fails for values in a Node header object (particularly nasty as it only manifests when a header has multiple values, like set-cookie)

facebook/jest#2549

See also: bitinn/node-fetch#220

Why are you switching from supertest though? It's maybe easier to just upgrade to v3 which supports promises.

keep supertest is ok for me, no need to replace it.

IDK, I'd prefer to do it all at once. There's little point in async/await without node-fetch. Switching to node-fetch hasn't been too much of an issue, and the headers issue is gone with an upgrade to the v2 alpha.


Throws error in Chrome: Uncaught SyntaxError: Unexpected token :

I am creating an external sourcemap and referring it in my index.html file. The minified script is running fine. But the sourcemap file throws the below error in Chrome(47).
Uncaught SyntaxError: Unexpected token :

Here is how I am referring the source map in my index.html page
 <script type="text/javascript" src="/ccg/resources/js/build/main.min.js"></script>
 <script type="text/javascript" src="/ccg/resources/js/build/main.min.js.map"></script>

I am using this configuration in my gulpfile.js.
gulp.task('ccgscripts', function() {
  gulp.src(['resources/js/vendor_scripts/jquery-1.11.3.js',
  'resources/js/vendor_scripts/jquery-ui-1.10.4.js',
  'resources/js/vendor_scripts/underscore.js',....])
    .pipe(sourcemaps.init())
    .pipe(concat('ccgScript'))
    .pipe(stripDebug())
    .pipe(uglify())
    .pipe(sourcemaps.write('./'))
    .pipe(rename({suffix: '.min.js'}))
    .pipe(gulp.dest('resources/js/build/'));
});

Can anyone provide some insight on this?

You are trying to include the source map as javascript:
<script type="text/javascript" src="/ccg/resources/js/build/main.min.js.map"></script>.
The browser finds the source map based on the special comment in the javascript source file, you are not supposed to include it like this.


Fix Docker Compose ftdetect

This upgrade simplifies the Docker Compose file type detection down to
one regex. It also prevents that ftdetect from detecting itself.
Finally, it adds support for .yaml extensions and drops support for
docker-compose files without an extension, as that is madness.
I also changed all the setfs to set ft because it wasn't working in
Neovim for some reason.

Thanks!


Bates2020 FAFB olfactory system

https://doi.org/10.1101/2<IP_ADDRESS>1453
soon to be out in current biology

related to https://github.com/VirtualFlyBrain/Management/issues/165

see also https://github.com/VirtualFlyBrain/Management/issues/249


gofumpt format

What this PR does:
gofumpt format

Codecov Report

Merging #150 (1f411d7) into develop (d5f6407) will not change coverage.
The diff coverage is 30.00%.

@@           Coverage Diff            @@
##           develop     #150   +/-   ##
========================================
  Coverage    40.60%   40.60%
========================================
  Files           35       35
  Lines         1692     1692
========================================
  Hits           687      687
  Misses         903      903
  Partials       102      102

Impacted Files
Coverage Δ

pkg/client/dubbo/dubbo.go
22.01% <0.00%> (ø)

pkg/client/dubbo/option.go
0.00% <ø> (ø)

pkg/client/http/http.go
60.31% <ø> (ø)

pkg/client/http/response.go
0.00% <0.00%> (ø)

pkg/common/yaml/yaml.go
90.90% <ø> (ø)

pkg/config/api_config.go
10.60% <ø> (ø)

pkg/config/config_load.go
53.94% <ø> (ø)

pkg/filter/accesslog/access_log.go
4.08% <ø> (ø)

pkg/filter/plugins/plugins.go
33.33% <ø> (ø)

pkg/filter/recovery/recovery.go
77.77% <ø> (ø)

... and 4 more

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 d5f6407...1f411d7. Read the comment docs.


FancyZones locked position

Description of the new feature / enhancement
Hello,
i liked to locked the position from the windows that i drop into a zone. because sometimes i pan a windows but i don´t want it. maybe with a automatical lock after the drop.
greetings
Scenario when this would be used?
after i droped i window into a zone.
Supporting information
No response

You are saying you don't want the window to be moveable once it is dropped onto a Zone? /needinfo

Yes. Maybe i want scroll in browser window with a mouse click (left click an hold), then it happens, that i change the window size and dont scroll.Mit freundlichen Grüßen Am 26.09.2023 um 15:55 schrieb Joseph Finney @.***>:
You are saying you don't want the window to be moveable once it is dropped onto a Zone? /needinfo
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Wrong version number displayed

I downloaded plex-rich-presence-setup.exe version 1.7 but the setup displays version 1.6 ..

...and so does the program after installing.

Hello ! Thank you for reporting this issue. It should not impair the features of the app. It will be fixed with the 2.0 version which i'm working on.


when I enter the command in terminal it return comand not found even though I have resently download the file

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/hello-world-tutorial/install
Operating System: macos
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

It might be an issue with PATH.
Check the output of the where.exe dotnet command and if your system is x64 and the x86 path returns first, please follow the steps at https://github.com/dotnet/core/issues/5962#issuecomment-780084535 to fix the issue
Let us know if this helps.


Enable convolution_test_cudnn_frontend_disabled test for ROCm.

This test was most likely added for TFRT BEF reasons.
It was initially specified with a no_rocm tag but after discovering that it actually works on ROCm, the no_rocm tag was removed in this PR.
/cc @deven-amd

jenkins: retest Ubuntu-CPU please

jenkins: retest Ubuntu-GPU-single please

jenkins: retest Ubuntu-CPU please

jenkins: retest Ubuntu-GPU-single please

jenkins: retest Ubuntu-CPU please

I'm not sure we even need this PR since I now believe that the unit test in question was intended to be CUDA only.
The test is specified with the --xla_gpu_enable_cudnn_frontend flag which is used in a CUDA only function.
Do not merge until I check with G.

Closing this since it the test is CUDA only.


Feat: Implement the function in the Router contract.

Description
Implement the plugin_transfer function in the Router contract.
File: src/router/router.cairo.
Function signature:
    /// Transfer the specified amount of tokens from the account to the receiver.
    /// # Arguments
    /// * `token` - The token address to transfer.
    /// * `account` - The account to transfer from.
    /// * `receiver` - The address of the receiver.
    /// * `amount` - The amount of tokens to transfer.
    fn plugin_transfer(
        ref self: TContractState,
        token: ContractAddress,
        account: ContractAddress,
        receiver: ContractAddress,
        amount: u128
    );

Acceptance criteria

Function is implemented and well commented.
Associated unit tests (nominal and failure) are implemented and passing.

Resources

https://github.com/gmx-io/gmx-synthetics/blob/77a2ff39f1414a105e8589d622bdb09ac3dd97d8/contracts/router/Router.sol#L26

Hey, can I take this one please?

Sure! Assigned 🔥


[Caching] Do not mix swift modules built from CAS vs. from FileSystem

Use a different context hash for modules built from caching using CAS vs. normal swift modules. They should not be mixed since those cannot be loaded as a dependencies for a module which is setup to build with a different method.
rdar://122814823

@swift-ci please smoke test

So the contents of of two PCH built with and without caching will be different?

The lookup method for external contents are different when using caching. The dependencies with caching have casid inside for dependencies modules which will not work if the compiler instance is not setup with a CAS.


Missing information on edit method modifier

I was not able to find any additional information for edit / display methods that applies to D365? (for example on the caching behaviour) Where can i find that in the documentation?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 51bd2787-887e-c0b8-176e-1fb26c7de95b
Version Independent ID: 1cd60a0e-3def-e4b0-7abe-4b36bec753a2
Content: X++ language reference
Content Source: articles/fin-ops-core/dev-itpro/dev-ref/xpp-language-reference.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @RobinARH
Microsoft Alias: rhaertle

@RobinARH, please review this feedback. Thanks!

Bug 422221 logged to track this issue.

There is nothing new about edit and display methods in F&O. The semantics (as described here: https://docs.microsoft.com/en-us/dynamicsax-2012/developer/using-the-display-method-modifier) are identical from 2012 to now,

Thanks for the info! I know about the AX 2012 documentation, but as a developer you cannot safely know at the moment what applies to D365 and what not. Maybe the "Applies to" information at the top should be updated to include that information.
The link also does not include any information about the caching behavior of edit methods, only the display modifier is described here:
https://docs.microsoft.com/en-us/dynamicsax-2012/developer/caching-display-methods
But there is no information about the new SysClientCacheDataMethod attribute which should be used instead of cacheAddMethod on the form.

Forwarding to @Haytham<EMAIL_ADDRESS>who may now those details.
From: Kevin Eck<EMAIL_ADDRESS>Sent: Friday, February 28, 2020 12:01 AM
To: MicrosoftDocs/dynamics-365-unified-operations-public<EMAIL_ADDRESS>Cc: Peter Villadsen<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-unified-operations-public] Missing information on edit method modifier (#2116)
Thanks for the info! I know about the AX 2012 documentation, but as a developer you cannot safely know at the moment what applies to D365 and what not. Maybe the "Applies to" information at the top should be updated to include that information.
The link also does not include any information about the caching behavior of edit methods, only the display modifier is described here:
https://docs.microsoft.com/en-us/dynamicsax-2012/developer/caching-display-methodshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdynamicsax-2012%2Fdeveloper%2Fcaching-display-methods&data=02|01|Peter.Villadsen%40microsoft.com|50cc73225e66434e81c808d7bc244d6a|72f988bf86f141af91ab2d7cd011db47|1|0|637184736413347618&sdata=4h9pPs8mcrtJO7INgoEK%2F5DxT5zgfY%2BJqSmMx%2F54Qjk%3D&reserved=0
But there is no information about the new SysClientCacheDataMethod attribute which should be used instead of cacheAddMethod on the form.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-unified-operations-public%2Fissues%2F2116%3Femail_source%3Dnotifications%26email_token%3DACYNH7ME5V5V67FTETKAUHTRFDACPA5CNFSM4KWQ3AO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENHUAXQ%23issuecomment-592396382&data=02|01|Peter.Villadsen%40microsoft.com|50cc73225e66434e81c808d7bc244d6a|72f988bf86f141af91ab2d7cd011db47|1|0|637184736413347618&sdata=gO%2FHKK%2BvhcfJgMmz6x4xviYuHHDssMjoKVATzqYuTgE%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYNH7KWXJSV4OYCNVOL4B3RFDACPANCNFSM4KWQ3AOQ&data=02|01|Peter.Villadsen%40microsoft.com|50cc73225e66434e81c808d7bc244d6a|72f988bf86f141af91ab2d7cd011db47|1|0|637184736413357615&sdata=91BNWl6KH5ChJgdys7zzFsakUuUmY1lvr7lAYJqfLzg%3D&reserved=0.

Any news on that? The D365 documentation is still lacking any information about the SysClientCacheDataMethod attribute or its usage.


v6 preview: OData addroutecomponents with the current version

Hi!
I finally had a slot to start fiddling with the new release. Looks good so far!
My app is using a routing convention like "api/v{version:apiVersion}/odata" but this doesn't seem to work straight away in AddRouteComponents since I'm getting
System.ArgumentNullException: Value cannot be null. (Parameter 'type')
   at Asp.Versioning.OData.TypeExtensions.SubstituteIfNecessary(Type type, TypeSubstitutionContext context)
   at Asp.Versioning.ApiExplorer.ODataApiDescriptionProvider.UpdateModelTypes(ApiDescription description, IODataRoutingMetadata metadata)
   at Asp.Versioning.ApiExplorer.ODataApiDescriptionProvider.OnProvidersExecuted(ApiDescriptionProviderContext context)

I debugged enough to find out that the library hits the version parameter it cannot parse the type and leaves it as null, leading to the exception.
Is such a naming scheme possible with the new version? We are housing both OData and "normal" routes in the app and would like to have these separate:
/api/v1/odata/ODataEntities
/api/v1/NormalEntities

Yes, the two can live together. Have you looked at the new Advanced Example, which shows the two mixed? As always, if you have a repro to share, I can help look into it.

@commonsensesoftware After I fixed my package references by the other issue, this magically fixed itself too. I can't believe endpoint routing actually works ❤
@dxynnez I believe there is some magic involved but as long as you define your IModelConfigurations they get automatically added and configured. See the advanced example above for a minimal setup

@dxynnez EDMs are created by implementing IModelConfiguration instances. All of the OData examples should have a /Configuration folder with one or more implemented configurations. If you don't want to use that approach, you can also define a ODataApiVersioningOptions.ModelBuilder.DefaultModelConfiguration callback function. These two approaches are mutually inclusive.
The DI extensions know to look for IModelConfiguration automatically, so you don't need to do any additional registration; they are discovered automatically. A model configuration is required because it will be called for each API version and route prefix combination. The configuration decides what, if anything, is configured for that particular EDM. This is much more complex than the default OData configuration. Since a sequence of IModelConfiguration is always processed, you don't even have to call API Versioning variant of AddRouteComponents because this will implicitly be done with the prefix of / as long as the configuration creates a non-empty EDM.
Do not attempt to call the native OData  AddRouteComponents; it will be ignored. Despite some talks with the OData team in the early design phase of 8.0, there was no concessions made to make the setup/configuration of OData more flexible for API Versioning. I tried to make the API Versioning variant feel as natural as the built-in OData method, even though you have to configure it a different way.
I hope that help clear it up.

@dxynnez EDMs are created by implementing IModelConfiguration instances. All of the OData examples should have a /Configuration folder with one or more implemented configurations. If you don't want to use that approach, you can also define a ODataApiVersioningOptions.ModelBuilder.DefaultModelConfiguration callback function. These two approaches are mutually inclusive.
The DI extensions know to look for IModelConfiguration automatically, so you don't need to do any additional registration; they are discovered automatically. A model configuration is required because it will be called for each API version and route prefix combination. The configuration decides what, if anything, is configured for that particular EDM. This is much more complex than the default OData configuration. Since a sequence of IModelConfiguration is always processed, you don't even have to call API Versioning variant of AddRouteComponents because this will implicitly be done with the prefix of / as long as the configuration creates a non-empty EDM.
Do not attempt to call the native OData AddRouteComponents; it will be ignored. Despite some talks with the OData team in the early design phase of 8.0, there was no concessions made to make the setup/configuration of OData more flexible for API Versioning. I tried to make the API Versioning variant feel as natural as the built-in OData method, even though you have to configure it a different way.
I hope that help clear it up.

Thanks so much for the explanation! I like the auto-discovered magic more than the AddRouteComponents of configuring the edm model. It's much more compact / clean than the native way IMO as we finally can separate the verbose configuration out of the app startup code.
Just want to confirm one thing - can we expect that whatever supported in the native AddRouteComponents API, should be supported by the IModelConfiguration? Or at least that is the ultimate goal?


Design&navigation

More or less a draft:
Possible to navigate to any date with animation (to the right or to the left)
Everything is synced to DayHeader
Basic events layout (non-overlapping with each other, like in iOS calendar)
DynamicColor to programmatically generate tints, and later, colors for specific input (i.e. different kinds of events).
Quite inefficient performance-wise because there is no cell reuse right now, but scrolls smoothly if less than 15 events per day on iPad 3.

Right now it aligns events properly, shows Now sign only for today view.
Navigation on top bar works fine, but there are few flaws and navigation bugs when swiping the content.


Tweaked controller provider configuration

This PR adjusts the environment variables used to configure the provider to avoid conflicts with the existing Juju CLI. Any non-conflicting environment variables have been moved to internal/provider/provider.go so that if a conflict arises in the future it only needs to be adjusted in a single location.
It also adds destroy functionality to data_source_model_test.go to compliment the existing model add functionality and allows the test to clean up after itself.

 Tweak controller provider configuration

I've left a comment regarding the parsing, I think we should be able to avoid this.

We discussed this offline, keeping it as a string is simpler and convenient for configuration and sufficient for the mvp. Implementing as a list didn't seem as trivial as it first appeared.


Add collections page

Description
Adds a collections page that pulls collection info from Airtable. The decks are linked to the collections. The Collection component copies a lot from Decks (the homepage). We could reuse code here but we will likely change the homepage in the near future so I'm thinking it's alright for now.
Screenshots

~ good to go ~


Tag a release

I was going to make this into a Homebrew formula, but they require that there be a tagged version. I'd suggest v1.0.

Oooh, good point! Yeah, 1.0 works for me too.
https://github.com/holman/spaceman-diff/releases/tag/v1.0

:+1:


[I/O Site SSR] Search field is slow to return results

Summary
When adding input to the search query using SSR, loading the results takes a long time. This may be due to querying nerdgraph after each keystroke.
Steps to reproduce:

Navigate to the I/O SSR Feature Site
Search for a quickstart in the search input
Quickstart results populate after multiple seconds

Acceptance Criteria

[ ] https://github.com/newrelic/instant-observability-website/issues/78
[ ] https://github.com/newrelic/instant-observability-website/issues/82
[ ] Wait to query the search input after a certain number of keystrokes (TBD)
[ ] Wait to query the search input after a specified amount of time has elapsed before querying (TBD)

we wanted to confirm if there is any improvement we can make on the front end or if this is a service issue.

We decided to not launch the SSR feature at this time.
REASONS:

The performance issues we are seeing with category and page data and search results is too severe for a marketing site. Load times are anywhere from 1 - 5 seconds before caching  and spending time to optimize that doesn’t seem worth it at the moment
We are seeing large UI deviations in the internal and external catalogs UI  which is making this service less of a value add to the external site now
Due to our change in direction internally, our original goal of having parity isn’t valid anymore
As we learned from our GA releases: Our approach to the site has changed a lot in the past several months, to be strictly marketing focused and not something that needs to be a direct parity of the internal catalog, thus reducing the complexity.
This site is transitioning to a team focused on marketing website development, and SSR and an integration with the catalog service is extra complexity that offers little end user value, for just a marketing site


power_domain: gpio: raw follower GPIOs

Extra list of GPIOs that 'follow' the state of the power domain. These GPIOs are set to physical level '0' when the domain transitions to SUSPENDED, and set to physical level '1' when the domain transitions to ACTIVE. The logical levels (ACTIVE_HIGH/ACTIVE_LOW) are not modified by this action (through gpio_pin_configure).
This behaviour is intended to be used when an SPI device is on a power domain and the CS pin is explicitly driven high and low by the SoC, instead of having an external pull-up to the voltage rail. The idle state of the CS pin needs to be high, but when the power domain goes down the CS pin needs to go low to avoid back-powering the device.
This property is NOT needed when the CS pins have an external pullup to the voltage rail that is being switched.
The BMI270 sensor on the Nordic Thingy53 is an example of this hardware setup.
Alternate solutions were considered:

Device drivers handles the problem.

Would require modification in every single SPI device driver to properly handle this, even if abstracted with a spi_handle_power_down/up() helper function.

Handling in SPI drivers

SPI drivers have no link to the devices, only devices link back to the SPI drivers. Even if such a link is added, the SPI drivers have no reason to be notified of power domain transitions of arbitrary devices, and don't store CS pin configuration in any case.

Automatic handling in the power domain driver

While the power domains end up with a list of devices on them, this is only populated at link-time, not compile-time. As a result, the power domain would need some way to query the CS pin configuration at runtime, for arbitrary devices which may or may not be SPI devices. This sounds like a thorny problem.

Design better hardware without this problem

Sadly the Thingy53 already exists in the world and is a Zephyr supported platform.

The proposed solution looks good to me, my only concern is if spi drivers start to handle it in their side.

The proposed solution looks good to me, my only concern is if spi drivers start to handle it in their side.

As mentioned in point 2, AFAICT any attempt to have SPI drivers handle this would require them doing a lot more work and integrating with several other API's, to handle what is a power domain problem. I don't think it's likely anyone want to pollute their SPI driver with all that.

Could you provide an example of this being used in-tree? some board which needs it perhaps?

From the PR description: The BMI270 sensor on the Nordic Thingy53 is an example of this hardware setup.

Also not getting why the follower ones ignore the polarity flag?

Ignoring the polarity is sort of the point. CS by default is active-low, but when the device on the bus literally has no power, the CS pin being high is a bad thing.

I'm finding it hard to follow why enable-gpios could not just be extended like this:

It probably could, but the solution would basically end up looking like this PR anyway. I added it as a separate property to hopefully make it clearer when the property should be used. Having N enable GPIOs for a power domain doesn't really make sense from the hardware perspective.

Could you provide an example of this being used in-tree? some board which needs it perhaps?

From the PR description: The BMI270 sensor on the Nordic Thingy53 is an example of this hardware setup.

I meant using follower GPIOs as part of this PR, for example, adding it to the Thingy53.

Also not getting why the follower ones ignore the polarity flag?

Ignoring the polarity is sort of the point. CS by default is active-low, but when the device on the bus literally has no power, the CS pin being high is a bad thing.

My thinking is the SPI peripheral and power domain use the same GPIO, but the configuration/flags are not the same:
pd {
        enable-gpios = <gpio0 1 GPIO_ACTIVE_HIGH> /* Switch pin */
                       <gpio0 0 GPIO_ACTIVE_HIGH> /* CS pin */
};

spi {
        power-domain = <&pd>;
        cs-gpios = <gpio0 0 GPIO_ACTIVE_LOW> /* same CS pin */
};

And when the power domain is suspended, the SPI must already be suspended, so there is no contention for ownership of the CS GPIO, same goes the other direction, PD is resumed before SPI, and SPI takes ownership over the CS pin when its resumed.

I'm finding it hard to follow why enable-gpios could not just be extended like this:

It probably could, but the solution would basically end up looking like this PR anyway. I added it as a separate property to hopefully make it clearer when the property should be used. Having N enable GPIOs for a power domain doesn't really make sense from the hardware perspective.

I would describe what this PR is doing as doing that in spirit:
pd {
        enable-gpios = <gpio0 1 GPIO_ACTIVE_HIGH>; /* Switch pin */
        follower-gpios = <gpio0 0 0>; /* CS pin */
};

just with one of the properties ignoring the polarity.
I believe the best option is to have drivers manage their GPIOs, and not share ownership of pins between PD and device drivers. It provides full flexibility to device drivers and its clear for users to understand I think.

I believe the best option is to have drivers manage their GPIOs, and not share ownership of pins between PD and device drivers. It provides full flexibility to device drivers and its clear for users to understand I think.

It sounds like you are proposing alternate solution 1 from the PR description. The problem here is completely unrelated to individual device drivers since it is a PCB design problem. Providing a way to solve this issue for all the devices that it could affect would therefore require modifications to every SPI device driver in tree. That sounds unreasonable to me. The problem is restricted to certain power domain setups, which is why I have attached the solution to the power domain.

I believe the best option is to have drivers manage their GPIOs, and not share ownership of pins between PD and device drivers. It provides full flexibility to device drivers and its clear for users to understand I think.

It sounds like you are proposing alternate solution 1 from the PR description. The problem here is completely unrelated to individual device drivers since it is a PCB design problem. Providing a way to solve this issue for all the devices that it could affect would therefore require modifications to every SPI device driver in tree. That sounds unreasonable to me. The problem is restricted to certain power domain setups, which is why I have attached the solution to the power domain.

The problem of back powering is quite common in many devices, like interrupts pins from sensors and RTCs, any IO pin really, and the optimal GPIO state after powered off can be quite varied, disconnected? pulled down, set to 1 for I2C bus pins?
See this addition from an input driver:
https://github.com/zephyrproject-rtos/zephyr/blob/302683ef7f21284c3ea90b8a24723ff56d536823/drivers/input/input_gpio_keys.c#L228-L249
I don't believe adding the follower-gpios is a flexible enough solution to add compared to the larger problem I believe CS pins hall into. What if we wanted to disconnect the CS pin rather than set it low for example?
If we really want to solve this in a generic way, which I think we do, we need something akin to pinctrl states, to define how each pin should be configured when a device is suspended and/or powered off. It would make sense to have it be part of the power domain infrastructure given the states follow the power domain as this PR proposes, but I think we need to ability to configure the pins behaviors.

The problem of back powering is quite common in many devices, like interrupts pins from sensors and RTCs, any IO pin really, and the optimal GPIO state after powered off can be quite varied, disconnected? pulled down, set to 1 for I2C bus pins? (and definately varied by the specific board/hw the device is on)

Correct, and all of these pins you mention (except the I2C bus pins) are specific to the driver, and can (and should!) be set to GPIO_DISCONNECTED inside the PM_DEVICE_ACTION_TURN_OFF action.

So are CS pins? Why move logic specific to them to the power domain, but not others?

I don't see the provided snippet as being relevant as it has nothing to do with power domains (suspended vs active is separate from on vs off).

The important part of that snippet is the option: no-disconnect added to the devicetree to specify how to configure the pins from the driver. Necessary since GPIO pins vary in features and optimal pin states vary by hardware layout.

set to 1 for I2C bus pins

That is already the default idle state of the bus, nothing needs to be done.

What if we wanted to disconnect the CS pin rather than set it low for example?

That sounds like a standard CS configuration (e.g. cs-gpios = <&gpio0 21 (GPIO_ACTIVE_LOW | GPIO_OPEN_DRAIN)>;), in which case the pin will naturally return to 0V when the power domain the pull-up is connected to is turned off.

These are valid configurations of a CS pin:

The GPIO pin is on the other side of a level shifter which inverts the signal
The GPIO pin is inverted
The GPIO pin supports disconnect, but not open-drain
The GPIO pin supports open-drain, but not disconnect
The GPIO pin supports open-drain and disconnect, but for this specific hardware, disconnect is more efficient than open-drain.

Simply setting it low is not nearly enough to cover ll of these cases.

If we really want to solve this in a generic way, which I think we do, we need something akin to pinctrl states, to define how each pin should be configured when a device is suspended and/or powered off.

I don't see that solution as being possible. If dev A requests pin X to be high when its off, and dev B requests pin X to be low when off, and both are off...

Do you have an example where this is the case? devices don't usually share the same GPIO, and if they do, it requires quite a bit of synchronizing between the two drivers.
The reason PD is a good place to put alternate configurations is that when devices are off, they don't control the GPIOs, so the PD can take ownership and configure them.


Fix ContextualNetAddress parsing

add-peers expects an array so it would be
add-peers = ["<IP_ADDRESS>", "<IP_ADDRESS>"]

or single value ["<IP_ADDRESS>"]
Maybe ini format is closer to what you're expecting, I'll check the library aspect mentioned

the perf-meters issue is because of an issue with the log-level,
@callid0n should be working now, any more sneaky options I might have missed?
TODO
[ ] - align Args struct names with CLI arg names

Perhaps serde rename should be applied to:
inbound_limit -> maxinpeers
outbound_target -> outpeers
And perhaps others I'm missing. Ideally we find a way to avoid maintaining these multiple renames (both on args definition and serde attributes), but that can be a future fix


Add Mastercard 3DS card (take #2)

Reference: https://docs.adyen.com/development-resources/testing/test-card-numbers/#enrolled-in-3d-secure-2

Rebased on top of master and squashed my commits.

Looks great, thank you!


ocamlPackages.mimic: init at 0.0.1

Motivation for this change
New package which is required for git >= 3.0.0, but is versioned independently from git.
https://github.com/mirage/ocaml-git/releases/tag/mimic-v0.0.1
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build ocamlPackages.mimic ocaml-ng.ocamlPackages_4_08.mimic

@GrahamcOfBorg build ocamlPackages.mimic ocaml-ng.ocamlPackages_4_08.mimic


new Gosund SP1 EU

I´m trying to flash a Gosund SP1 EU device and I encounter a problem: When I start the flashing procedure, after around 5-10 seconds I can here the device switch and the blinking blue LED turns red or turns off. I don´t get any error or success message on my raspi. Any idea?

Duplicate, please check existing issue threads


Restructuring and reconnection improvement

This restructures the connector to make the operations reuse common connectivity code.

Enable reconnection by using ConnectionException for OAuth token expiration. This was found when incorporating the connector in long running processes.
Move errors to internal package, and other updates found in Error Handling best practices
Extract common code for Azure Key Vault API requests and responses to AzureKeyVaultClient and KeyVaultRequest classes.

Resolves #23


Do not Force Auto Increment

If a field is a primary key and a int, gorm forces the field to be a auto_increment field. This breaks down when you have multiple primary keys, or simply the int field is not suppose to be auto_incrementing.
Since gorm has support for the AUTO_INCREMENT tag, it is not needed to be forced.

Still prefer it is auto increment. and auto incrementing multiple primary keys is supported by some databases, but not mysql.

In this case though it is impossible to use gorm on tables that have multiple integer primary keys. Making it optional would solve it and allow flexibility. The default gorm.Model was modified so existing behavior would be unchanged.
As an alternative implementation, would you be apposed to a patch set that implements an opt-out tag? Something like NO_AUTO_INCREMENT ? Then the existing behavior does not change but someone could opt-out of forcing auto increment keys, especially where things like mariadb/mysql don't support it.

Hi @Shelnutt2
You could set the sql type with tag for multiple integer primary keys.

@jinzhu That works well and is a good workaround. Thanks for the support.

You could set the sql type with tag for multiple integer primary keys.
@jinzhu Got same trouble. Could you show how to do this?

Got it. thanks.

@liaoliaopro Can you tell us what your solution was?


Move pylibmc behaviors into sub behaviors key

Related to https://github.com/gusdan/django-elasticache/issues/18.
@gusdan Any thoughts on this change?
Also I would be willing to up the base supported version of django if you were interested given their deprecation/support schedule.

👍

@gusdan Any chance this will be merged soon? We are having the same issue with Django 1.11.

guys sorry for delay. I just merged pull request, created new version 1.0.2 and pushed it it pypy.
@adepue thank you for pull request :+1:

Thanks for the merge!

Thanks!


Horizontal line on fraction is not rendered

I use Mathjax to render latex formula.
Here is my my configuration looks like this
tex2jax: {
    displayMath: [["[[", "]]"]],
}

I want to render the formula : \( x = {-b \pm \sqrt{b^2-4ac} \over 2a}. \)
It renders correctly, except for the \overtag. The horizontal line is not rendered. Here is an image of the result : image
The formula is correctly rendered at first (here is an image), then processing Math and Typesetting Math are runned and the line disappears.
What could be the problem ?
Edit : The problem came from my side, closing the issue

@AntoineGrandchamp How did you solve the problem? I have the same exact issue


Try Cobra framework for testing Solidity programs

https://github.com/cobraframework/pytest-cobra

The features do not look very attractive.


Unable to query heap information

Brief description of your issue
Sometimes, it is not possible to display process' heaps information.
Steps to reproduce (optional)
Start computer. Start SystemInformer. Do a lot of work for long period of time including development of an C application. From time to time, query heaps information of an application I'm developing. After some time, SystemInformer is no longer able to query heaps information of my app.
SystemInformer is able to query other apps. My app is built as release and launched by double-click from TotalCommander, not debug launched from ViualStudio. It is not running under any debugger.
Restarting SystemInformer solves the issue, but it appears again after few days. Sorry, I don't know the steps to reproduce.
Expected behavior (optional)
No response
Actual behavior (optional)
[Window Title]
System Informer
[Main Instruction]
Unable to query heap information.
[Content]
Attempt to send a message to a disconnected communication port.
[Close]

Environment (optional)
Nightly build, x64. Windows 10.0.20348.1668.

query heaps information of an application I'm developing

Is the program 32bit or 64bit?

Nightly build, x64

What version of SI?

Is the program 32bit or 64bit?

32bit

What version of SI?

3.0.6550


Simulation is extremely slow

Thanks for creating this wonderful challenge.
I find the simulation to be extremely slow, with each step in the simulation taking roughly around 1-2 secs. I'm running transport_challenge-v0 environment on a server with 8 x RTX 2080s.
Is there a way to speed up the simulation for transport challenge?

It usually runs much faster than that (see benchmark documentation).

Can you make sure that the simulation is actually utilizing a GPU?
Can you please attach your Player log to this thread?

Hi @alters-mit, I ran the benchmark scripts from magnebot api on my machine and found the performance to be slightly lower compared to what you had reported.
benchmark.py
turn_by(): 0.44959707260131837
move_by(): 0.24055161476135253

Skipped frames
Time elapsed

0
0.6450610041618348

5
0.24371663331985474

10
0.21520087718963624

15
0.2193888783454895

20
0.2253703474998474

floorplan_benchmark.py

Test
Time elapsed

Default
0.48365660905838015

Without reflection probes
0.4828155279159546

Without post-process
0.49377440214157103

Without post-process and without reflection probes
0.6591026067733765

nvidia-smi shows TDW.x86_64 build running on the GPUs
Current Player.log when I was trying to train a policy. I'm running 8 simulator builds on 8 GPUs to fetch data simultaneously.

Mono path[0] = '/home/ma/sriram/tdw_build/TDW/TDW_Data/Managed'
Mono config path = '/home/ma/sriram/tdw_build/TDW/TDW_Data/MonoBleedingEdge/etc'
Preloaded 'libflexUtils.so'
Unable to preload the following plugins:
	libaudiopluginresonanceaudio.so
Display 0 '0': 1024x768 (primary device).
Display 1 '1': 1024x768 (secondary device).
Display 2 '2': 1024x768 (secondary device).
Display 3 '3': 1024x768 (secondary device).
Display 4 '4': 1024x768 (secondary device).
Display 5 '5': 1024x768 (secondary device).
Display 6 '6': 1024x768 (secondary device).
Display 7 '7': 1024x768 (secondary device).
Plugins: Couldn't open /home/ma/sriram/tdw_build/TDW/TDW_Data/Plugins/libaudiopluginresonanceaudio.so, error: /home/ma/sriram/tdw_build/TDW/TDW_Data/Plugins/libaudiopluginresonanceaudio.so: symbol __google_auxv, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference

Plugins: Couldn't open /home/ma/sriram/tdw_build/TDW/TDW_Data/Plugins/libaudiopluginresonanceaudio.so, error: /home/ma/sriram/tdw_build/TDW/TDW_Data/Plugins/libaudiopluginresonanceaudio.so: symbol __google_auxv, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference

Desktop is 1024 x 768 @ 0 Hz
Initialize engine version: 2020.2.7f1 (c53830e277f1)
Plugins: Couldn't open OculusXRPlugin, error: OculusXRPlugin: cannot open shared object file: No such file or directory

[Subsystems] Discovering subsystems at path /home/ma/sriram/tdw_build/TDW/TDW_Data/UnitySubsystems
[Subsystems] No descriptors matched for  examples in UnitySubsystems/OculusXRPlugin/UnitySubsystemsManifest.json.
[Subsystems] 1 'inputs' descriptors matched in UnitySubsystems/OculusXRPlugin/UnitySubsystemsManifest.json
[Subsystems] 1 'displays' descriptors matched in UnitySubsystems/OculusXRPlugin/UnitySubsystemsManifest.json
[Subsystems] No descriptors matched for  meshings in UnitySubsystems/OculusXRPlugin/UnitySubsystemsManifest.json.
[Subsystems] No descriptors matched for  examples in UnitySubsystems/WindowsMRXRSDK/UnitySubsystemsManifest.json.

Default vsync count 0
requesting resize 256 x 256
resizing window to 256 x 256
Desktop is 1024 x 768 @ 0 Hz
UnloadTime: 3.115934 ms
Setting up 16 worker threads for Enlighten.
   Try running this build
Also run pip3 show tdw and if the version isn't 1.8.7, then pip3 uninstall tdw and pip3 install tdw==<IP_ADDRESS>

Hi @alters-mit, I tried running the above build with tdw==1.8.7 but still found an average simulation time per step to be around 1.5 seconds

In that case, the simulation might be slow just because the Magnebot is running into walls or getting stuck on furniture. Try adding a third person camera to review what's going on, or check the action status at the end of each action.
Let me know if that helps.

Thanks @alters-mit  for your response. I see general benchmark(here, here) documentation in tdw show the simulator to be operating at more than 100 FPS in many cases. But the magnebot api (benchmarks)[https://github.com/alters-mit/magnebot/blob/main/doc/benchmark.md] show actions generally take around ~0.2 secs per simulation step. Do you know why this difference occurs and is there any way that we can get higher simulation steps per second in the transport challenge? Such as requesting less data from the simulator or some other optimizations or trade-offs that we can make for the quality of data.

@nnsriram97 There are many factors that could be slowing down the Magnebot. See my previous comment.
The Magnebot could be traveling further per action (which would make it slower). It could be colliding with objects or getting caught on furniture. etc. You should check your simulation to see whether any of these or other possible factors are occurring.


device_info plugin to get information about the device and OS

Provides platform-specific information about the device and operating system a Flutter application is running on. This information is useful when reporting app crashes.

Added a container class. PTAL: https://github.com/flutter/plugins/pull/158/commits/433958ae60e6c040f47085780195440b1765bfe2

(unable to locate the comment on github, so replying by email)
I still think it would be bad to recommend two separate crash tracking

solutions for one app.

Depends on how you count. I count one solution, sentry.io.

Could we build a plugin for sentry itself using
https://sentry.io/for/cocoa/?code=objc and
https://sentry.io/for/android/ and still get stable fp for dart
stacktraces?
We can certainly try and reuse their HTTP transport utilities, which
presumably handle offline and retries, if that stuff is exposed at all.
However, I don't see value in duplicating Dart stack trace parsing and
encoding into a Sentry request.

If not, we should at least build a plugin for registering the native
platform with Sentry and recommending a path for full integration (both for
native and dart crashes)? Ideally under the same app id (dsn?).

That's the idea. For Java, NDK, Objective-C and Swift you'd use Sentry's
existing ways of setting up crash reporting. I'm not sure Flutter can add
much here, except remove any blockers, if there are any.


BUG FIX: Charging info from ENABLE_SHOW_CHARGE_LEVEL doesn't show up

first part:
gEeprom.VfoInfo[gEeprom.RX_CHANNEL].AM_mode && gSetting_AM_fix this can be true but the line doesn't have to be used because rx is false
second part:
gCurrentFunction changes to FUNCTION_POWER_SAVE when powersave activates then the line disaapears

Thank you !
Done that.


Plex API

As a user I would like to use a Plex client to access music on Roadie.
I am not able to find much documentation and I think this would involve some sort of unique authorization for the server itself.

Found this PHP file but it looks like Ampache has a Plex API layer implementation.


Uncaught Exception while stopping flows (during deploy)

Current Behavior
Node-red crashed with this dump (while deploying)
20 Dec 16:57:05 - [red] Uncaught Exception:
20 Dec 16:57:05 - [error] ConnectionError: Cannot close a pool while it is connecting
at ConnectionPool._close (S:.node-red\node_modules\mssql\lib\base\connection-pool.js:538:30)
at S:.node-red\node_modules\mssql\lib\base\connection-pool.js:521:12
at new Promise ()
at ConnectionPool.close (S:.node-red\node_modules\mssql\lib\base\connection-pool.js:520:12)
at node.connectionCleanup (S:.node-red\node_modules\node-red-contrib-mssql-plus\src\mssql.js:335:42)
at node.disconnect (S:.node-red\node_modules\node-red-contrib-mssql-plus\src\mssql.js:459:22)
at mssql. (S:.node-red\node_modules\node-red-contrib-mssql-plus\src\mssql.js:834:21)
at Node.close (S:\AppData\Roaming\npm\node_modules\node-red\node_modules@node-red\runtime\lib\nodes\Node.js:340:26)
at stopNode (S:\AppData\Roaming\npm\node_modules\node-red\node_modules@node-red\runtime\lib\flows\Flow.js:745:31)
at Flow.stop (S:\AppData\Roaming\npm\node_modules\node-red\node_modules@node-red\runtime\lib\flows\Flow.js:387:35)
Expected Behavior
Node-red must not crash for this unacaught exception, as I see at this line (see link below) there is a try catch
https://github.com/node-red/node-red/blob/0e8d3127944a91f39fb49bcb4b388b184ce11edd/packages/node_modules/%40node-red/runtime/lib/flows/Flow.js#L388C39-L388C39
Steps To Reproduce
In my nodered I had a flow that 1 time a second do an update to some tables in sql server (on localhost), maybe this cause the exception (Cannot close a pool while it is connecting) but the problem is that node-red does must not crash with an exception, only report.
Environment

Node-RED version: 3.1.0
Node.js version: 18.18.2
npm version: 10.2.1
Platform/OS: Windows Server 2012 R2 x64

Node-RED must exit on an uncaught exception, because we have no way of knowing what state it has left any 3rd party node. It is up to the authors of those 3rd party nodes to catch all exceptions from their code (or dependencies).

Yes, going deeper there was a problem in node-red-contrib-mssql-plus (see https://github.com/bestlong/node-red-contrib-mssql-plus/issues/91)

closing as issue is with contrib node.


A question about export line features

Sorry, I am a rookie and I am very interested in your project.I have a question that how  can I  use the model to export line features (segments and descriptor maps) as follows:
ppython -m sold2.export_line_features --img_list  --output_folder  --checkpoint_path <path to your best checkpoint,>
what is the "-img_list  -"  and "--checkpoint_path <path to your best checkpoint,>"? And how can get "-checkpoint_path <path to your best checkpoint,>".
Looking forward to your reply,thank you very much!

Hi, first download the pre-trained model as explained in the ReadMe. Then replace <path to your best checkpoint,> with the path that leads to this pre-trained model.

I am closing it now, feel free to reopen it if you have more issues.


external_uri is not used in proxy mode

Karma v0.55 running in Docker-compose and exposed with nginx as http://<IP_ADDRESS>/karma
alertmanager:
  servers:
    - name: local
      uri: http://alertmanager:9093
      proxy: true
      external_uri: http://<IP_ADDRESS>/alertmanager/
      readonly: false

Browser show existing alerts and silences as well, but when I try to edit existing silence with Karma, browser ignores external_uri variable and tries to POST to http://<IP_ADDRESS>/proxy/alertmanager/local/api/v2/silences

Since proxy is enabled all POST requests will be proxied via karma backend. external_uri value will be used for links in the UI.
https://github.com/prymitive/karma/blob/master/docs/CONFIGURATION.md#alertmanagers
If you scroll down to 4. Proxy mode is enabled and external_uri is set: you'll see what links are used for what.

@prymitive, thank you, I saw that, just not understand "Karma internal URI" from first time.
I do not specified http://<IP_ADDRESS>/proxy/alertmanager URL in any variables.
I expect that Karma will use URL like <base_url>/proxy/alertmanager/local/api/v2/silences (in my case - http://<IP_ADDRESS>/karma/proxy/alertmanager/local/api/v2/silences).
Could I achieve it any way?

You mentioned that karma is under ‘ http://<IP_ADDRESS>/karma’, did you also set ‘listen.prefix’ ? Without that karma will assume everything is hosted under ‘/‘

Oh, thank you, my bad! I was looking for all variables contains 'uri' in its names, and do not found listen.prefix before your notice. All works like a charm now!


Add org logos #166

This could use some quick code review from @tmaybe
It lets people give their organization a logo. They can point to one in the Brigade Information sheet or it will use their avatar from GitHub.
I have some questions about:

GitHub throttling
The orgs in the tests come back in a random order, but I dont know why.

Still needs documentation and to be added to the examples.


[WIP]feat(region): add cloudpods

What this PR does / why we need it:

[ ] Smoke testing completed

If yes, write the release branches name in the below format and submit the related cherry-pick PR:
None
/area region
/cc @zexi

Create issue https://github.com/yunionio/cloudpods/issues/11740 of this feature.


FLIR PTU Bumblebee mounting bracket not part of model

The mounting bracket connecting the Bumblebee2 to the PTU isn't part of the Dual Arm Husky URDF and the centre of rotation thus offset by the height of the bracket. Could you please add the bracket to the model/repository/URDF?
Thanks
Cf. https://github.com/husky/husky/tree/dual_ur5_husky/husky_description/meshes/accessories and https://github.com/husky/husky/tree/dual_ur5_husky/husky_description/meshes/

Actually, self-observing with a camera mounted atop the rear end the whole mounting appears to be off, shifted for both the base of the PTU and the bracket for the bumblebee (this is after adding a 2cm offset for the bracket):

It's off both in X and Y because the base_link has an offset from the mount_link due to the morphology of the PTU, cf:

I've proposed a fix to this in #39.

@wxmerkt @TheDash I am going to close this since it part of the Dual Arm Husky URDF.


Error selecting "Open recent workspace" from "File" menu or "Workspace" from "View menu on Windows 7

The error:

Text of the error:
[Window Title]
Error

[Main Instruction]
A JavaScript error occurred in the main process

[Content]
Uncaught Exception:
Error: Calling a callback of released renderer view
    at ret (C:\@GitHub\LightTable\builds\lighttable-0.8.0-alpha-windows\resources\atom.asar\browser\lib\rpc-server.js:112:21)
    at MenuItem.click (C:\@GitHub\LightTable\builds\lighttable-0.8.0-alpha-windows\resources\atom.asar\browser\api\lib\menu-item.js:44:20)
    at Function.delegate.executeCommand (C:\@GitHub\LightTable\builds\lighttable-0.8.0-alpha-windows\resources\atom.asar\browser\api\lib\menu.js:127:69)

[OK]

The "Open recent workspace" item in the context menu of the workspace tree works fine.

I couldn't reproduce this just now. I'll re-open if I re-encounter.


'npm run dev' fails silently using node version 10 after initial install, MacOSX, Mojave

Bug report
Describe the bug
'npm run dev' fails silently using node version 10 doing the initial setup on the next.js website.
Terminal produces:
><EMAIL_ADDRESS>dev /Users/antonionogueras/port-proj
> next

Compiling

● client

● server █████████████████████████ compiling (0%)
✔ success server compiled in 202ms

No listening occurs.
To Reproduce
mkdir hello-next
cd hello-next
npm init -y
npm install --save react react-dom next
mkdir pages
npm run dev
Expected behavior
Hot reload, server running
System information

OS: macOSX, Mojave
Browser: Chrome
Version of Next.js: 7.0.2

Additional context
This worked fine on my Windows 10 machine

I think this was solved 🤔 If not try installing next@canary and trying again, if it still hangs we'd be happy to take a look!

@timneutkens Hey there! So, I got it working with a blank project, but then I have issues with a pre-existing project.
I get
{ [Error: EACCES: permission denied, mkdir '/Users/my-directory/next-js-prac/node_modules/.cache']
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/Users/my-directory/next-js-prac/node_modules/.cache' }```

This is my project. I did `sudo npm run dev` and it worked. Just posting this for anyone who is having trouble like I was.

Thanks!


All com.android.support libraries must use the exact same version specification

Hello, I got the following error in build.gradle (module:app):
All com.android.support libraries must use the exact same version specification (mixing versions can lead to runtime crashes). Found versions 25.3.1, 23.0.0. Examples include com.android.support:animated-vector-drawable:25.3.1 and com.android.support:support-v13:23.0.0 less... (Ctrl+F1)
There are some combinations of libraries, or tools and libraries, that are incompatible, or can lead to bugs. One such incompatibility is compiling with a version of the Android support libraries that is not the latest version (or in particular, a version lower than your targetSdkVersion.)
I tried searching online but I could not find any suitable resolutions. Any help would be greatly appreciated.
Thanks,
Al

This is fixed in v4.0.

I think the build tools version should be 27.0.2. I'll update the readme.

Hi, awesome fast response! :)
I tried 27.0.2 and also (android studio recommended it) 27.0.3
Still the same message

Can you post your build.gradle files?

These are the minified gradle files (closed source) which still trigger the message (I also changed the appcompat-v7 version to 27.0.2 to match the compileSdkVersion):
############ Top level gradle file ############
buildscript {
     repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:2.3.3'
        classpath 'com.google.gms:google-services:3.1.0'
    }
}

allprojects {
    repositories {
        jcenter()
    }
}

############ App module gradle file ############
apply plugin: 'com.android.application'

// https://plus.google.com/u/0/+MarcReichelt/posts/BX2he4vSJaM
def getNumberOfGitCommits() {
    return 'git rev-list --count HEAD'.execute().text.trim().toInteger()
}

// https://plus.google.com/u/0/+MarcReichelt/posts/BX2he4vSJaM
def getCurrentGitHash() {
    return 'git rev-parse --short HEAD'.execute().text.trim()
}

android {
    compileSdkVersion 27
    buildToolsVersion "27.0.2"

    defaultConfig {
        applicationId "com.secret.appname"
        minSdkVersion 17
        targetSdkVersion 27
        versionCode getNumberOfGitCommits()
        resValue "string", "app_git_hash", getCurrentGitHash()
        versionName "1.0.0"
    }
}

repositories {
    maven { url "http://dl.bintray.com/chat-sdk/chat-sdk-android" }
    maven { url "https://maven.google.com" }
    maven { url "https://jitpack.io" }
}

dependencies {
    compile 'com.android.support:appcompat-v7:27.0.2'
    compile 'co.chatsdk.chatsdk:chat-sdk-core:4.0.8'
    compile 'co.chatsdk.chatsdk:chat-sdk-ui:4.0.8'
    compile 'co.chatsdk.chatsdk:chat-sdk-firebase-adapter:4.0.8'
    compile 'co.chatsdk.chatsdk:chat-sdk-firebase-file-storage:4.0.8'
}

apply plugin: 'com.google.gms.google-services'

Go to project/.idea/libraries folder on your file system and see which libraries are different.
You will have to manually include these libraries with the same version in your build.gradle file.
Then, sync your project.
Example Here


fix openstack conversion for volumes

What this PR does / why we need it:
Altering an openstack  shoot via v1beta1 version is not possible because

the conversion from internal -> v1beta1 did not set the volume information in the migration annotation (for no shoot- no its properly set)
conversion from v1beta -> internal now sets the volume information from the migration annotation.

This happened because Openstack is a special case & did not include Volume information in the v1beta1 Worker. Needs the information from the migration annotation.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Thanks, can you please write a test for this scenario as well?


Boot Fail Issue

I've had to re-install home assistant multiple times because I get this error seemingly at random when I reboot my vm. Sometimes the reboot works but most times it doesn't. I've gotten better at avoiding this by just using the ha command line and restarting by using core restart. Any pointers at what my issue may be?

I've experienced the same issue, had to restore a backup and when I stop the machine and start it again the error appears

Seems to happen when I do a HA version update from the web frontend. I'll wait 10 min or so and check the logs which make it look like the system is running, there's just no frontend. This is where I use to manually reboot the vm the and pretty much kill it.
To get around this i go to the console on proxmox and issue a core stop (multiple times if necessary), rename my config so the system can start fresh, then i do a core start and usually it'll start back up. Then I place my configuration.yaml file back in the config folder and start it back up and that usually works.
@robgardien Do you use tensorflow by chance? I have a feeling it might be this that is causing some issues for me initially.

@eracknaphobia No I don't use tensorflow, it happens after an upgrade of home assistant. The systems resources are very high and it looks like the system is running, there's just no frontend as you described. A reboot seems to work, a stop and start seems to cause the error

Ok thanks, maybe tensorflow has nothing to do with it.
I just updated from 109.4 to 109.5 strictly from console commands.

core stop
core update
core start - no frontend after 10 minutes, log file grows with no apparent errors just normal log traffic
core restart - system comes up fully 🤷♂

I'm currently in limbo mode after trying to update to 109.6. can't stop / start core I noticed ram is maxed out. memory leak issue?

I've updated proxmox using apt-get dist-upgrade from the pve shell and I haven't had the problem since, maybe it's worth trying?

Thanks, I'll give it a shot.

Updating proxmox didn't solve my issue. I'm currently stuck in limbo trying to update Home assistant to 0.110.1

Still having issues. Usually when I try to do anything with restarting / updating when my memory usage is 90% or more.

I'm also still having issues. Works fine while running but the error occurs when restarting. I have to restore a backup when this problem occurs

I'm having same issue, but it occurs randomly, meaning that for some dasys all is working well, then suddenly if I do a shutdown or reboot of the VM I get this error.
I noticed that it has started after upgrading Proxmox to 6.2.x
If I restore a snapshot, the error is still there, only if I restore a backup of the entire VM the error does not show anymore, until next one.
It seems to be related to the UEFI disk.
I tried to follow this guide, but after "elect 'Add Boot Option':" I don't have nothing to select and I'm stuck

@woody4165  Thanks for the info about the backups. I was using snapshots and noticed they wouldn't boot either. I will look into making Stop backups instead for now. Should save me time as I've been re-creating the vm from scratch and importing my homeassistant snapshot when things go south.

Anyone know if it is normal to have the link becomes ready message pop up so many times? I'm currently trying to update to 0.110.6 and the frontend is down but the console is running.

BTW, proxmox is running on a nuc i7 (5th gen) with an nvme ssd, so i would think boots would be much faster than what they are currently.

Yeah I'm having this same issue since Proxmox updated itself.
I re ran the script and it works until I restart the VM, then it wont boot. Seems like there is some kind of UEFI issue. Haven't been able to get the boot menu to work correctly either like mentioned on the Proxmox forums.

I too am having this issue. Glad I'm not going crazy.

I ended up following this guide: .
After I got it up and running I just loaded my latest full snapshot backup from HA and I was up and running again.

I have not had this error reappear in a long time. So whatever was the cause must have been patched some where along the way.


Update request: pnpm v7.29.1 → v8.1.0

Package name: pnpm
Latest released version: 8.1.0
Current version on the unstable channel: 7.29.1
Current version on the stable/release channel: v7.14.
[x] Checked the nixpkgs pull requests

Notify maintainers
@tjni

I have a PR for this, but with version 8.1.1. Since 8.1.0 and 8.1.1 are solely differentiated by patch version, I presume my PR will resolve this issue. Is that alright?


Chart viewer - Copy as image pastes black background

SQL Operations Studio Version: 0.23.6, x64

Steps to Reproduce:

Run query that produces numerical results (e.g. SELECT a = 1, b = 2)
Click 'View as chart'
Click 'Copy as image'
Open Paint
Paste

The result: image with black background
'Save as image' saves with no problems.
OS Version: Windows 7 Enterprise (6.1.7601)
[EDIT] I'm using "Light SQL Operations Studio (default light)" color scheme.

Cleaning up old issues.  I'm going to close this as "won't fix" for now since we don't plan to address in the next few milestones.


Code Review

Final Pipeline Files:
WDLs:

downsampling_pipeline_part1.wdl
downsampling_pipeline_part2.wdl

Inputs:

downsampling_pipeline_part1.json
downsampling_pipeline_part2.json

Scripts:

calcRD.sh
count_fastq.sh

I need help with scaling disk and memory size for the large steps like cram to bam, bam to fq, and realign steps


Supported leaflet versions

The bower.json and package.json files define Leaflet 0.7 as a depencency (BTW having two different version identifiers). As the release of Leaflet 1.0 is nearly final now:
Maybe you could add a note to the README which leaflet versions currently are supported by your plugin. That would help users who plan to update from Leaflet 0.7.x to 1.0

I just released 2.0.0 which bumped the leaflet dependency to 1.x.  I'll add a note in the readme in just a minute

It should be good to go!

Thanks! Nice :)


Bug: fold signs do not show up at all

not sure how to check for the cause of this, but apparently, fold icons do not show up at all, even though they are included in signs_on_startup. They are apparently also the only sign group (that I use) that does not work, the rest works completely fine.
I am using nvim-ufo, in case that matters? 🤔

Thanks for reporting the issue @chrisgrieser. The plugin uses foldclosed() and foldclosedend(). Do those work as expected for you? The example below can be used for testing.
" Open a help window
:help
" Create a fold for the first line
zfj
" Check the output of calling foldclosed and foldclosedend
:echo foldclosed(1)
:echo foldclosedend(1)

The output should be 1 for foldclosed and 2 for foldclosedend. Is that what you're seeing?

If that works as expected, can you also try under the scenario where you noticed nvim-scrollview fold signs not working? In that case, the argument to both foldclosed and foldclosedend would be the line number where a fold starts. The output should be something other than -1 in both cases.

I have updated the plugins from Lazynvim and noticed the same thing, the folding icons are no longer displayed, and before updating they were displayed without any errors.
I have also noticed that the icons can no longer be overwritten, that is, I customized the icons and now only the default icons are shown, for example in the search icon, the equals symbol makes the bar look too messy when you do a search and there are many results, so I looked for some icons that were a little more subtle to display the results, the same with the diagnostic icons, but now does not show the ones I customized but the ones that bring by default the plugin.
What is the correct way to change the icons? Because I have followed the instructions you give in the documentation.

@Fausto-Korpsvart, for the search symbols and diagnostic symbols, those can be customized with configuration variables.
For example, in Vimscript:
let g:scrollview_search_symbol = ['1', '2', '3', '#']
let g:scrollview_diagnostics_error_symbol = 'X'

Or in Lua:
-- Using configuration variables
vim.g.scrollview_search_symbol = {'1', '2', '3', '#'}
vim.g.scrollview_diagnostics_error_symbol = 'X'

-- Using a setup() call
require('scrollview').setup({
  ...
  search_symbol = {'1', '2', '3', '#'},
  diagnostics_error_symbol = 'X',
  ...
})

For the search setting, a list was used instead of a string so that the symbol will depend on the number of matches.

"Because I have followed the instructions you give in the documentation."

Further details, like the specific parts of documentation, would be appreciated, so I can make any necessary corrections.
If the above examples don't resolve the problem for you, can you create a separate issue? I think that the search and diagnostics issue you're encountering are separate from the fold sign issue.

@Fausto-Korpsvart, the symbol customization must be done prior to the plugin loading; changing afterwards won't work. The custom settings would have to be inserted in your Neovim configuration (e.g., init.vim or init.lua).

@Fausto-Korpsvart, for the search symbols and diagnostic symbols, those can be customized with configuration variables.
For example, in Vimscript:
let g:scrollview_search_symbol = ['1', '2', '3', '#']
let g:scrollview_diagnostics_error_symbol = 'X'

Or in Lua:
-- Using configuration variables
vim.g.scrollview_search_symbol = {'1', '2', '3', '#'}
vim.g.scrollview_diagnostics_error_symbol = 'X'

-- Using a setup() call
require('scrollview').setup({
  ...
  search_symbol = {'1', '2', '3', '#'},
  diagnostics_error_symbol = 'X',
  ...
})

For the search setting, a list was used instead of a string so that the symbol will depend on the number of matches.

"Because I have followed the instructions you give in the documentation."

Further details, like the specific parts of documentation, would be appreciated, so I can make any necessary corrections.
If the above examples don't resolve the problem for you, can you create a separate issue? I think that the search and diagnostics issue you're encountering are separate from the fold sign issue.

@dstein64, The way I had configured the plugin was with the setup() call:
            'dstein64/nvim-scrollview',
            event = 'BufReadPre',
            config = function()
                require('scrollview').setup {
                    winblend = 60,
                    column = 1,
                    signs_on_startup = { 'search', 'diagnostics', 'folds' },
                    diagnostics_error_symbol = '·',
                    diagnostics_hint_symbol = '·',
                    diagnostics_info_symbol = '·',
                    diagnostics_warn_symbol = '·',
                    folds_symbol = '',
                    search_symbol =  '·',
                }
                require('scrollview.contrib.gitsigns').setup()
            end,

but since the update it stopped working, so as you suggested I tried putting the configuration variables in the init.lua file and that has worked.
I also noticed that when I put BufReadPre in the Lazynvim event, the diagnostic icons it displayed were the ones I have set in the LSP file.

Further details, like the specific parts of documentation, would be appreciated, so I can make any necessary corrections.

And I should have expressed myself better, the documentation is well explained, I followed it step by step and before the update it worked very well, but after updating the icons were the only ones that stopped working, the rest kept working.
I think it might be necessary mentioning those changes in the documentation, maybe many use the default icons and that's why they haven't noticed that setting them from the setup() call doesn't work, and suggesting these changes in the documentation would be good.
Either way, thanks for the answer and solution, it's a very useful plugin.

@dstein64 okay, this is weird, after updating scrollview, the folds now show up just fine. I guess one of the commits done since yesterday unintentionally also fixed this issue? 🤔
Well, bugs that fix themselves are the best bugs I guess, so I'll close this, and re-open in case the issue re-occurs.
Thanks for the quick fixes!

@chrisgrieser, I'm glad to hear it works. Perhaps the fix for #99 addressed the problem. I guess my earlier comment to @Fausto-Korpsvart was incorrect: "I think that the search and diagnostics issue you're encountering are separate from the fold sign issue."