Performance evaluation for Julia v1.11

As discussed at yesterday's meeting, LoopVectorization.jl, Octavian.jl, and JuliaSIMD in general will be deprecated for Julia v1.11. That is, code is likely to continue to work for the time being, but bugs might not get fixed anymore. It is also to be expected that we will see a performance hit in areas where we heavily rely on LV.jl & friends, especially with the @turbo macro.
Some parts of Trixi.jl that are likely to be adversely affected by this have already been identified:

multiply_dimensionwise! for mortar and AMR projections/interpolations (see interpolation.jl)
Computation of metric terms for P4estMesh/StructuredMesh (e.g., here)
DGMulti solver: Several areas where Octavian.jl's matmul! (see also #1906), some explicit uses of @turbo
Manual SIMD optimizations for the EC performance paper (these might not work at all anymore, e.g., here)

The decision yesterday was to first proceed with switching CI testing to Julia v1.10 (#1562 - @DanielDoehring is on it!), and to continue monitoring CI testing with v1.11 (#1904 will help). Once v1.11.0 is released, we will revisit this issue and benchmark the aforementioned cases, before we make decisions on how to proceed.

LoopVectorization.jl has been updated but performance regressions like https://github.com/JuliaLang/julia/issues/55009 still remain in Julia v1.11.0


Fix notification name from Firebase 7 rename.

Is there a way to fix to work for both Firebase 6 and 7?

Is there a way to fix to work for both Firebase 6 and 7?

Not that I'm aware of - the type itself was renamed. I suppose we could use the raw string value but that won't help.

One hack would be to check for the existence of the FIRVersion class. Otherwise, we might need to hold off on this PR and disable the quickstart test until Firebase 7 releases.

Replaced by #1062 and #1063


[semantic-dom-diff] better error handling

Currently semantic dom diff throws incoherent errors when passing incorrect input. During tests it's sometimes hard to find out what you did wrong.

This also ties into chai-dom-equals

This has since been implemented.


Pulling a docker image from a different pipeline

Not sure how to ask this without creating an issue.
Is is possible to Pre-build/cache an image on one pipeline, say one that runs on master whenever a commit is added, and pull that cached image on another pipeline without having to declare it in the same set of steps?
So something like this:
Pipeline 1 yml - build and push docker image (runs on master)
steps:
  - label: ':docker: Build & Push Image'
    plugins:
      - docker-compose#v4.12.0:
          config: 'my-compose.yml'
          build: 'myapp'
          image-repository: 'repo.com'
          image-name: '$DOCKER_IMAGE_TAG'
          cache-from:
            - 'myapp:repo.com:$DOCKER_IMAGE_TAG'
            - 'myapp:repo.com:latest'

pipeline 2 yml - tests - run on each PR
  - label: 'test 1'
    command: 'test.sh'
    plugins:
      - docker-compose#v4.12.0:
          run: 'myapp'
          config: 'my-compose.yml'

  - label: 'test 2
    command: 'test2.sh'
    plugins:
      - docker-compose#v4.12.0:
          run: 'myapp'
          config: 'my-compose.yml'

I have tried this approach but it is trying to build the image each time on the tests pipeline.

Hey @amit-nayar! No worries, you can create a new issue with questions/doubts 🙂
Nope 😔 that's not possible with the docker-compose plugin, and would be out of the scope of plugins.


support for azureADTokenProvider in AzureChatOpenAI

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
Is there a chance to start supporting the azureADTokenProvider value?
Based on this update for v4.41.1 it is available to be used with the AzureOpenAI class.
Error Message and Stack Trace (if applicable)
Not specified, the element is not present to be used.
Description
The request is to add support for the azureADTokenProvider value provided by AzureChatOpenAI; this example from Ms doc on how to use it, it is python but just as an exaple on its usage.
System Info
langchain: 0.1.37

CC @sarangan12 I think your last PR added this?

I believe this was added in latest, please reopen if not!


use github version instead of the apt-version

the idea is to compile forked-daapd from scratch so that spotify, lastfm and mpd support are available

thanks. for the suggestions. I did not actually check the config file yet.
anyways after I did this the maintainer of
https://github.com/linuxserver/docker-daapd
contacted me and basically what I was trying to do already exists...
So I will not put more effort in my docker container


Bug 2099695: Update CAPG after rebase

Update CAPG after the latest rebase, all manifests are generated automatically using make assets command.

/bugzilla refresh

/lgtm


mod charts display

Hi can you describe what this PR is doing, do you have screenshot ?

http://serwer.hyzne.com/temp/serposcope/ SEO3.rar - need another modyfed files
my mod its more complicated - use admin/ user/etc
if admin full acces in nice charts on index.php if user only project charts /view?id/
not finished yet index.php need request from database for line - actually random data set
unpack all file - log admin - admin or change pass for difrent project in .htpasswd

Hello St-a-ch, I'm wondering from January which point reached by your fork.
The screenshots are really interesting, but I've tried to test the forked files (from patch 2 to 7) and didn't succeded in making them work (some files are missing in the repos)
regards

wiev my panel live clientside http://seo.hyzne.com/ user:wideofilmowanie
pass:p@ss im not using GitHub if you want to prepare rar from all files in
my modding system
2015-04-26 11:50 GMT+02:00 Laurent<EMAIL_ADDRESS>
Hello St-a-ch, I'm wondering from January which point reached by your fork.
The screenshots are really interesting, but I've tried to test the forked
files (from patch 2 to 7) and didn't succeded in making them work (some
files are missing in the repos)
regards
—
Reply to this email directly or view it on GitHub
https://github.com/serphacker/serposcope/pull/26#issuecomment-96357683.


Make the FixedTarget.from_name method easier to discover

Here I rearrange the docs to make it easier to discover the FixedTarget.from_name method.
This is partially in response to a thread on astropy-dev where it seems some users aren't aware of the method, probably because the docs tutorials don't use FixedTarget.from_name much.
Closes #226.
cc @bsipocz @cdeil

Sounds like a good idea to me. 👍

Looks good. Thanks @bmorris3.

Cool :)
You should make the coord argument optional in there:
https://github.com/astropy/astroplan/blob/master/astroplan/target.py?highlight=#L83
so that, when name only is provided, it calls from_name straight.
Never under-estimate the laziness of the user ;)

@ceyzeriat We chose to err on the side of forcing users to be precise about what they intend to input, so users know what output to expect without much going on under the hood.

Alright, I don't want to force you guys. I chose to err on the "user is king" side.

@ceyzeriat - When you develop a library to be used by many, you meet all kind of users, and what is convenient, usual and logical for one is the opposite for the other. Thus it's desirable to stick to the principles e.g "Explicit is better than implicit." and "There should be one-- and preferably only one --obvious way to do it", etc. (from import this)

For this example, I also don't see the advantage, since from_name is available and doesn't require an extra line of import or creating objects before calling.
But @ceyzeriat , I know you have other gripes with the verbosity of the astroplan API, specifically having to create objects and have extra lines before being able to call certain functions / methods, instead of accepting simpler inputs like strings for convenience.
I sometimes feel the same way, too for some functions / classes in Astropy.
Can you please open a new issue in the Astroplan tracker with one or a few code snippets where you think astroplan is too verbose?
This PR is closed, and usually closed issues and PRs are just forgotten, whereas open issues and PRs get considered regularly (e.g. maintainers go throught them before a release) or get deliberately accepted or rejected after discussion.

@ceyzeriat and others interested in discussions on more convenient use of Astropy and affiliated packages: for me this would be a big improvement: https://github.com/astropy/astropy/issues/5245
(could have downsides I didn't consider and get rejected of course)


Add flag for disabling link and text dragging

Implementation of https://github.com/ungoogled-software/ungoogled-chromium/discussions/2055#discussioncomment-3494020 through feature flag thanks to help from @Ahrotahn and @networkException.
This allows selecting text from within a link and also allows starting the selection without clearing the existing one.
This is a long link, that I'll use for demonstration of what it is. They say a picture video is worth a thousand words.
And here is some more text for demonstration purposes only :)
With the flag enabled following becomes possible:
https://user-images.githubusercontent.com/10319700/188681263-9bc37892-a980-4cf9-ac66-7f199f43a325.mp4
PS: I also reordered --force-punycode-hostnames to be in alphabetical order.

I tested the changes (before the dedoublespacing) and it worked as expected.  The only thing I noticed is that you still have the commandline flag in the docs instead of adding DisableLinkDrag in the feature flag section.

The only thing I noticed is that you still have the commandline flag in the docs instead of adding DisableLinkDrag in the feature flag section.

Good point! I'll force-push this whole thing once again and start building again to be sure nothing broke.

Ready to merge?

So after some time having this flag enabled it seems to me that some of my clicks get ignored. This never happens without this flag.
My suspect is that I have a habit of not stopping my mouse specifically for a click, rather continue it to where I need it next and it is probable that on a hidpi screen this amounts to a "selection mode" for a couple of pixels between mouse DOWN and UP, which makes the click event consumed in "selection". Maybe this could be fixed by adding a condition on selection length or click time. 🤔


chore: snake case

Change field names to snake case. Use naming strategy to transform to / from camelCase

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

Project coverage is 75.00%. Comparing base (3b3f165) to head (f624d5c).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #714      +/-   ##
==========================================
- Coverage   75.10%   75.00%   -0.11%
==========================================
  Files         261      261
  Lines       11546    11492      -54
==========================================
- Hits         8672     8619      -53
+ Misses       2874     2873       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Bug: Node18/ES2022 triggers objects to have keys with undefined values: breaks spread

Bug Report

🔎 Search Terms
typescript
nodejs
spread
es2022

🕗 Version & Regression Information

This changed between versions @tsconfig/node16 and @tsconfig/node18 with node 18.16.0

⏯ Playground Link

I was not able to reproduce this on the bug workbench, I suspect there's some interaction going on with node18 here.  But I did set up a very simple repo that reproduces the problem reliably.
https://github.com/pvogel1967/ts-node18-spread-bug
Using node 18.16.0 (I didn't try other versions of node18)
git clone https://github.com/pvogel1967/ts-node18-spread-bug.git
npm install
npm build
npm test
Will print FAILED at the end...
➜  ts-bug-report git:(main) ✗ npm run test

><EMAIL_ADDRESS>test
> node dist/src/test.js | grep pass || echo FAILED

FAILED

Note, there is also a tsconfig.willpass.json file in there.  If you build with that file, the test will pass.  The only difference is the reference to @tsconfig/node18/tsconfig.json instead of @tsconfig/node16/tsconfig.json which, in turn means the only diff is to the target and lib settings from es2021 to es2022.
💻 Code

class TestDataDTO {
    b?: string;
    legacyB?: string;
}

class TestData {
    a?: string;
    b?: string;
}
const bar: TestDataDTO = { legacyB: 'pass' };
const barTest = new TestDataDTO();
// this next line simulates what you typically get from an API layer which is receiving a DTO
// with many optional fields via JSON and, after validating the DTO content, spreads it into an
// "empty" object created via new.
const { legacyB,...restDto } = {...barTest, ...bar};
// This next line is what causes the problem.  We successfully spread { b: legacyB } into the result
// but then the spread of what _should be_ an empty restDto overwrites the b property with undefined.
const result3: TestData = {
    ...(legacyB ? { b: legacyB } : {}),
    ...restDto
}
console.log(JSON.stringify(result3, null, 2)); // should be { "b": "pass" }
console.log(`restDto keys`, JSON.stringify(Object.keys(restDto))); // should be [] but is [a, b]
console.log(`barTest keys`, JSON.stringify(Object.keys(barTest))); // should be [] but is [a, b, legacyB]
console.log(`result3 keys`, JSON.stringify(Object.keys(result3))); // should be [b] but is [b, a]

🙁 Actual behavior
Spread of an empty object into a literal object after spread of a non-empty object in that same literal object results in the empty object (well, not quite empty, all keys have the value undefined).
🙂 Expected behavior
The empty object spread into a literal object should not cause properties already added to the literal object to be overwritten with undefined.

It should be noted this also breaks Jest's toMatchObject() method as the expected object may have several properties left intentionally undefined so that those properties are not inspected on the actual object.  Instead, the expect fails with the expected object having several
properties that are undefined causing a mismatch to the received object which does not have those properties or has those properties with actual values.

Assuming the spreaded objects in question have properties explicitly set to undefined (as opposed to just omitted entirely), then this is the expected behavior per the ES specification.

As far as I can tell this is working as intended. Targeting ES2022 instead of ES2021 changes the default value for useDefineForClassFields and causes your classes to use ECMAScript standard compliant class fields. That means your class fields are always defined with an explicit undefined.
Depending on useDefineForClassFields your class TestData compiles to:
class TestData { } // not ECMAScript standard compliant, properties are missing
class TestData { a; b; } // ECMAScript standard compliant, properties are defined

Classes are a poor choice for DTO structures. You should use interfaces instead.

Classes allow for decorators on properties, particularly important for swagger.

You can also see this in any compliant JS engine (with no Typescript involvement).
This code will print ["a"] in Javascript, and ["a"]when transpiled by Typescript with useDefineForClassFields enabled, but [] in Typescript without useDefineForClassFields enabled:
console.log(Object.keys({ ...new (class { a; })}))

Yeah.  I get what's going on (thanks for the pointer to useDefineForClassFields) and I do see the update to the ES class standard where fields are always present even if undefined in a class.
That said, the implication to spread semantics and object comparison is interesting...


FC when selecting "Show on Map"

NB 2310 -ab0e4b1:
If I am in compass mode and select "Show on map" c:geo crashes and goes back to cache-details.
It is reproducible on my device. If it not reproducible on your side, I can provide a log later.

My hardware is SLOW :) I know
In about 10 minutes a new nightly will be on page. I managed to update. Can you try again.

Should be the same as #703 (already fixed but no new nightly since then due to SDK change)

OK...its the same.
Now I will go and write down "You have to use the search before creating a new issue" 100 times.


Jupyter Notebooks are completely blank

Whenever I open an existing Jupyter Notebook on my WSL via VS Code, it just shows up completly blank. No lines to input, just fully blank. Like it cannot connect to the Jupyter Server or something. Hard to troubleshoot.

The same happens to me on daily channel and the following error is displayed
Unable to open 'test.ipynb': Cannot read property 'Rich' of undefined.

Hi @JakobRohrhirsch, are you using VS Code Insiders? Are you having the same issue as @godsic? That issue is a known issue that should be fixed in our next Jupyter insiders release.

Hi!
I'm attaching a screenshot from the blank jupyter notebook. I think I'm using VC Code stable.
Thanks!

Looks like a dupe of https://github.com/microsoft/vscode/issues/105536. Should be fixed in next month's release of VS Code (stable)


x/pkgsite: remove package from go dev website

What is the URL of the page with the issue?
https://pkg.go.dev/mod/github.com/ZiyaoQiao/oci-go-sdk
What is your user agent?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36 Edg/84.0.522.58
Screenshot

What did you do?
What did you expect to see?
Remove this package, it's not supposed to be visible
What did you see instead?

/cc @julieqiu

@jba @jamalc

Fixed.


CI: Flowey update to support conditional step evaluation

There are a couple places where it would be nice to support making various pipeline jobs support conditions. This might be a little interesting because GitHub and ADO handle conditions a little differently.
https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/using-conditions-to-control-job-execution
https://learn.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops
This would be uesful in a handful of places, for example: Updating guide building / publishing to only happen on main branch.

We have some of this already (see https://openvmm.dev/rustdoc/linux/flowey/node/prelude/struct.NodeCtx.html#method.emit_ado_step_with_condition), but there's certainly more to flesh out here.


New WT^(s) should start with a work score of 1

Currently in the code new WT^(s) start out with a work score of 0. They are supposed to start with a work score of 1.
Update SidechainDB and related unit tests to fix this error.

To be clear, as a new WT^ is added inside of a block with PoW that means that it has 1 work score as soon as it is added.


The types path in package.json is missing a /

After seeing a talk from @eladb during the CDK Day I created a test project to see projen in action. And during some exploring I noticed the types path in the package.json file is missing a / between the lib dir and the entrypoint file name when using the TypeScriptProject template.
Steps to reproduce
Initialize a project with the following .projenrc.js:
const { TypeScriptProject } = require("projen");

const project = new TypeScriptProject({
  name: "test-project"
});

project.synth();

Version
projen: 0.3.77
Possible solution
I think adding the /  between ${path.dirname(this.entrypoint)} and ${path.basename(this.entrypoint, '.js')} seems like it enough to make this work.
By modifying the compiled output, I tested this fix and it seems to work as expected. There do not seem to be any tests yet for the TypeScriptPoject, so not really sure how to continue there. I can already create a PR for the changes: https://github.com/bartcallant/projen/commit/39e9da0aeff7269809190d3b136bef6fd653ecd1

PR is welcome


npm run build not updating app.css neither editor.css

doing a
npm run build
can't see most recent changes inside dist/assets/css/ files get stuck in previous stage.
in ordert to have a more recent app.css I have to do
npm run package
and then upload the packaged to wordpress site.
I wan't to produce changes locally and upload only the files that need to be updated, not all the theme.
please, any sugestion
thanks.
$ npm -v
6.9.0
$ node -v
v10.16.3
$ npm run build

><EMAIL_ADDRESS>build ~/Documents/green.elglobus/greenballon-fp
> gulp build --production

[14:30:19] Failed to load external module @babel/register
[14:30:19] Requiring external module babel-register
[14:30:20] Loading config file...
[14:30:20] config.yml does not exist, loading config-default.yml
[14:30:20] Using gulpfile ~/Documents/greenballon-fp/gulpfile.babel.js
[14:30:20] Starting 'build'...
[14:30:20] Starting 'clean'...
[14:30:20] Finished 'clean' after 7.39 ms
[14:30:20] Starting 'sass'...
[14:30:20] Starting 'webpack:build'...
[14:30:20] Starting 'images'...
[14:30:20] Starting 'copy'...
[14:30:20] Finished 'copy' after 666 ms
[14:30:25] Finished 'sass' after 4.94 s
[14:30:25] gulp-imagemin: Minified 6 images (saved 55 kB - 27.7%)
[14:30:25] Finished 'images' after 5 s
[14:30:27] Version: webpack 3.12.0
 Asset    Size  Chunks                    Chunk Names
app.js  372 kB       0  [emitted]  [big]  app
[14:30:27] Finished 'webpack:build' after 7.52 s
[14:30:27] Finished 'build' after 7.53 s

npm_list.txt

Even tho it seems like the file has not been changed it indeed has so, see stat -x app.css http://b3.ms/yYLn75VKZ9Gg
When you deploy via git, git will recognize the file difference and upload the changed files accordingly. How do you run your deploys at the moment?


I can whyml and ..

https://why3.lri.fr/doc/whyml.html

https://discord.com/channels/@me/1082663985716924436/1096507775414190261

"how can I write an analyser that could tell me if my theorem is exactly the same as the program.""
That's a veeeery good point!
A lot of the work in certification (like in cybersecurity, railway, avionics, etc.) is precisely to ensure that and even more: how do you ensure that whatever you have proven is really what has been compiled and is running.

There are several main choices that have been used in the industry:

Use your "theorem" as spec. It's a proven specification so now your job is only to ensure that whatever you develop, it meets the spec.  One caveat is that, usually, in order to manage to prove things, you need to include some assumptions in your proof. Those assumptions needs to be checked, and maybe even monitored at run time to ensure that your proof still holds. There have been formal methods (such as B method: https://en.wikipedia.org/wiki/B-Method) where you build this high level spec, that you prove. Then you refine the spec into something that is closer to an implementation. You prove that this refinement is a real one which implies that your refinement still satisfy the spec. You then refine the refinement, while proving that it is a valid refinement, and so on until you get to a real implementation. Doing so ensures that your implementation at the end meets the very high level spec! It's been used extensively in Railway application

You extract your code from your theorem, the Curry-Howard correspondence takes care of the correction of the program for you. For example: https://coq.inria.fr/refman/addendum/extraction.html

Build the "theorems" from your code by hand. This has been done many times in certification, even at the highest level of cybersecurity certification, believe it or not. You trace your code and your model in order to ensure that you are really working on the same thing. You do so much tracking of what implements which spec, which spec has been implemented where, which type in the model has become which type in the code, and so on that by the end you're very confident that your theorem and your code are the same. Spoiler: they usually aren't. One ref could be this one: https://www.labri.fr/perso/ly/publications/using_coq_to_verify_javacard.pdf

Using a tool to automatically translate your program into the one of a theorem prover. For example: https://bahr.io/pubs/files/bahr08nicta-report.pdf but there are many other like this. You end up with your theories and then needs to work the theorems and proofs yourself. This works usually fine if you take the time to do the proofs yourself. It will require some time to do that and you will think twice before changing something in your code because it will mean you probably have to rework some of your proofs. This also require you to trust the translator. In certification, a loooot of focus would be put into the translator because a bug here could mean you're proving things that are not related to your code.

Using a tool to automatically translate your program into one of an automated theorem prover. This is a more modern approach (refs: https://nikolai-kosmatov.eu/publications/djoudi_hk_fm_2021.pdf for a real life application of this approach, https://hackage.haskell.org/package/sbv for a tool that works on Haskell but there are many others). Basically you translate your code and its specification (written in a specification language) into the language of automated solvers (usually SMT solvers or SAT solvers) and you let the solvers do the work for you. Well almost, because you will need to help them if the programming language is complex or you will need to help them with lemmas (that they will prove) in order for them to see how to prove your theorems. This is my preferred approach in everything I did. You need to be careful about the translator (same as before) and in the automated solvers (you don't want one to say TRUE if it's FALSE). The good thing about this is that you can use multiple solvers so you can more easily diversify and remove your trust in one particular solver.

Any of those solutions works, I just personnaly prefer 5) because if you manage to translate to a language such as WhyML or Dafny you can now use the full power of automated solver and not have to do the work by hand. If you know C, a tool I really like is CBMC: https://github.com/diffblue/cbmc. You can see how automated Formal verification works on some small examples.

To address some of your points:
If you’re aiming at formal verification of source code there are three main paths. First one is you build a formal model of your code in a formal language like Coq, Isabelle, PVS and you prove its correction. Then you have (or build) a code extractor that automatically extract the code from your model and proof. If the extractor is correct, you now have a formally verified code! In some standards (e.g Common Criteria) it was accepted to have the formal model proven, your code written by hand and to manually show that your code was a correct implementation of the model, which acted as a spec. Personally I’m not a fan of this approach.
Second one is to have a translator from your code to a formal language. It means that you are able to formalise the semantics of the language. It doesn’t matter too much if it’s purely functional, if it’s pure. All that matters is being able to translate it into a language (and a theory) that can deal with that. If you look at languages like C, which is not functional at all and king of not being pure, there is a framework called Frama-c that will allow to prove the correction of your code. ACSL is the specification language for it and it allows to say “I’ll modify a global variable and this is the spec of this modification” or “I’ll modify some parts of the memory and this is what will be inside”. One thing that is almost a prerequisite is strongly typed so you can easily express what the semantics of an operator is without relying on dynamic typing.


Calling cleanup code in JestEnvironment::teardown() still causes test to hang

🐛 Bug Report
I have some code that needs to be cleaned up after my Jest test runs, i.e.
const Redis = require("ioredis");
const redis = new Redis();

// Need to call
redis.disconnect();

If this cleanup code is called in afterAll, things work fine.
However, if I create a custom test environment (that extends NodeEnvironment) and call redis.disconnect() there instead, the test hangs.
I'm not sure why there is this behavior difference, or what you're supposed to put in JestEnvironment::teardown(). I thought it would be a good place to put this kind of clean up code so I don't have to repeat it across tests.
To Reproduce
Run this test https://repl.it/repls/SnarlingBluevioletTranslations#sum.test.js.
Expected behavior
If I put redis.disconnect() in my teardown() function, I expect the test not to hang.
Link to repl or repo (highly encouraged)
https://repl.it/repls/SnarlingBluevioletTranslations#sum.test.js

For afterAll is often useful if you want to clean up some global setup state that is shared across tests and it available in block.
For teardown is clean up for the test environment, and from setup to teardown have many process doing, here, it was not created to replace afterAll. Explain more, you can do something such as binding globals in the test environment setup, after run all tests and you doing clean up for binding globals before in teardown.


SAT segmentor is not accessable

the baidu yun link is not accessible , can you give me a new link?
my email is<EMAIL_ADDRESS>thanks a lot!

done

<EMAIL_ADDRESS>thanks, sat

Could you give me a link of SAT segmentor<EMAIL_ADDRESS>thanks a lot!

can you please publish a new link for it? thanks

can you please publish a new link for it? thanks

@shiragit  the google drive link is here https://drive.google.com/open?id=1UXshq4k9WKx4hNkdpOagJLXPR57ZkBkg

Closed as no further discussion. Feel free to reopen it again.


Add support for java.nio.HeapByteBuffer to ArrayBuffer conversion

Please, provide the details below:
When I tried to use ArrayBuffer.from([java.nio.HeapByteBuffer]) I got a native exception like 'Direct ByteBuffer expected)', this function only support direct byte buffer conversion, how to convert a heap byte buffer without data copy?
Did you verify this is a real problem by searching the NativeScript Forum and the other open issues in this repo?
Yes
Tell us about the problem

ArrayBuffer.from() can't convert java.nio.HeapByteBuffer to ArrayBuffer
Please provide the following version numbers that your issue occurs with:

CLI: 4.0.0
Cross-platform modules: 4.0.0
Runtime:  4.0.1

Did the error happen while the app was being constructed? (buildtime error)

No
Did the error happen while the app was executing? (runtime error)

Yes
Please tell us how to recreate the issue in as much detail as possible.

Consider using the playground to provide the code you have issues with.
Easy to reproduce with js code like
var bb = java.nio.ByteBuffer.allocate(12);
var ab = ArrayBuffer.from(bb);  //error

The WebSockets library returns HeapByteBuffers; I'm not sure when this changed, but I just recently got reports that NativeScript-WebSockets no longer works properly because of this issue, so I would love to see it fixed.

@NathanaelA can you check with the next wether the issue still exists?

@vtrifonov -  I used both 4.0 and the current @rc (2018-05-28) and I attempted to test this; but I am still just getting a java.nio.ByteArrayBuffer.   This is fine; I have updated my own code base tocatch all the "Buffer" types in my code and deal with it in JS, which eliminates the main issue that people were seeing with my NS-websockets and 4.x.    So I'm good; but this change I can't really test.

Ah, looks like I totally misread this issue.   I was under the impression that NS 2.x & 3.x actually returned a ArrayBuffer when it detected a ByteBuffer as part of its auto-conversions; but apparently it must have been my code doing the conversion all along.    However, what did break is it looks like the underlying websocket library is now sending binary over the standard callback.  My new version detects this and then redirects it back to the proper path.  So I'm good.

@NathanaelA yes, I think this is not the issue of your nativescript-websocket plugin, this fix just make the ArrayBuffer.from work for the HeapByteBuffer. This fix should work, I will test it with the new version.


tf.cast zeroes out input tensor when GPU does not have any free memory

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution: Linux Ubuntu 16.04
TensorFlow installed from (source or binary): tf-nightly-gpu binary from 10/31/2017
TensorFlow version (use command below): ('v1.3.0-rc1-4007-gc44f67a', '1.5.0-dev20171031')
Python version: 2.7.12
Bazel version (if compiling from source): N/A
CUDA/cuDNN version: CUDA v8, cuDNN v6
GPU model and memory: 1080 Ti (11 GB)
Exact command to reproduce:

x = tf.cast(tensor, tf.float32)
x = tf.to_float(tensor)
Above commands return a tensor with all values of tensor set to zero WHEN:
The gpu is in full use by another tensorflow process. I'm trying to cast the tensor from dtype=tf.uint16 to tf.float32, using above commands, but whenever this runs while the gpu is in full use (i.e. I get a CUDA out-of-memory error), the program completes execution normally but the casting commands set the tensor to zeros.
I upgraded from an older nightly-gpu binary to the current one, but didn't help. User should not try to use an already in-use gpu, but this error should at least be communicated to the user.
If I set the gpu to a different gpu with available memory, or if I hide all gpus to force it to use CPU, I do not observe this issue.

Thanks for the report,
@yzhwang and @zheng-xq have been investigating some issues with multiple processes and the GPU memory allocator and might have some more detail to share.
In the mean time, if possible, could you package up detailed instructions to reproduce the problem - ideally a .py  file that we could run (perhaps twice, one for each process) that reproduces the issue?
Thanks.

Hi @mmuneebs Thanks for reporting the issue. See my comment for another issue here: https://github.com/tensorflow/tensorflow/issues/14169#issuecomment-342256834

It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.


2 more builtins.

Damn.  Sorry.  Just this morning I wrote up export and readonly this morning along with some general cleanup for the environment package in general.  I'm going to take my version since I also implemented the -p option that the standard mentions.

Oh, okay, never mind. set might be useful, though.

Just pushed a commit that implements the no-arguments version of set.  Now it also prints unexported variables!


[FEATURE] auto-language switching

I am always frustrated when i cannot change a language in an app especially for non native english speaker, although there is a manual way to change the wiki link through the config file, i would like to see an automated system which let you choose the language of Wikipedia you want, and change the link in the config file instead of you .
thanks for considering this feature, i really like wiki-tui .

Hey @akito-sama, thank you for your feature request!
You're right, we currently have no way of quickly changing the configured language of the articles! Because the toml file format which we use for configuration has many ways of representing the data (basically, you can write them differently in the file and it is interpreted the same for the program), we, unfortunately, cannot write data to the configuration file after it was created (it would ruin the file format).
Could a cli argument satisfy your needs? Something like this:
# change the language to german
wiki-tui github -l de
wiki-tui github --language de

That way we can still change the language on the fly and we wouldn't ruin the custom format of the configuration file.

sure, this would be awesome, and if i may, i would suggest to also having a command to change the language in runtime too, if possible, this would make searching infos much easier, rather than closing and reopening the programme .

Yes, that would totally be possible and I agree that having the option to change these configs on the fly would make it much easier. What would you think about having a popup that lets you change the language that can be opened by pressing a certain key? Or would your rather like having a little "configure" button below the search bar?

i guess having a popup would be better than having a configure button in the entry points, it would make much more sense than having a configure button except if there would be more option than language to choose from, in that case i would suggest having both a popup for language and a configure button for the other option.
thank you soo much for your work on this project .

Great, I'll start implementing this feature as soon as possible! If you have any further suggestions, let me know!

Just letting you know that this feature will take a bit longer to implement because, with this, we (finally) can't use global variables anymore and have to pass the config down everywhere it's needed.


Unable to fetch offers of a subscription using In_App_Purchase package.

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Create a Auto-renewable subscription in Google play console
Add a base plan
Create multiple offer inside the base plan
Now using flutter in_app_purchase package, try to fetch the product(subscription) with offers.
Actual results
Should get the details of the Offer and upon calling purchase method, the Google Play Purchase Popup should show the offer to the user.
Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output

Doctor output

<!-- Paste your output here -->

flutter doctor --verbose
[✓] Flutter (Channel stable, 3.7.6, on macOS 13.2.1 22D68 darwin-arm64, locale
en-IN)
• Flutter version 3.7.6 on channel stable at
/Users/utgupta27/Programs/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 12cb4eb7a0 (8 days ago), 2023-03-01 10:29:26 -0800
• Engine revision ada363ee93
• Dart version 2.19.3
• DevTools version 2.20.1
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
• Android SDK at /Users//Library/Android/sdk
• Platform android-33, build-tools 33.0.1
• Java binary at: /Applications/Android
Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build
11.0.15+0-b2043.56-8887301)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 14C18
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2022.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build
11.0.15+0-b2043.56-8887301)
[✓] VS Code (version 1.76.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.60.0
[✓] Connected device (3 available)
• M2873Y36 (mobile) • UCXOMZSCDGVDELN • android-arm    • Android 10 (API
29)
• macOS (desktop)    • macos            • darwin-arm64   • macOS 13.2.1
22D68 darwin-arm64
• Chrome (web)       • chrome           • web-javascript • Google Chrome
110.0.5481.177
[✓] HTTP Host Availability
• All required HTTP hosts are available
• No issues found!

Hello @utgupta27. Could you provide a complete and minimal, reproducible code sample so that I can verify this issue?


fix: perf test relative import from state-transition

Motivation
Fixes small bug stopping perf test from running

:tada: This PR is included in v1.22.0 :tada:


Download sources

In Section "Running instructions" ( https://github.com/yizhak-lab-ccg/RNA_MUTECt_WMN#running-instructions ) the download source for 'call_stats_capture_paper_v1_3.tsv', 'maf_file_rna_final_paper_v1_3.tsv', the pon binary files and reference files is unclear. Providing direct links or further description of download procedure would be useful.

Added


Flaky

moved over from #37

Coverage increased (+0.9%) to 40.854% when pulling a8e2530938cba832a96fa18518dc03645a823baf on jameshiew:flaky into 9149c828856f20d94cb6d92889506281ff4ff218 on aschn:master.

Coverage increased (+0.9%) to 40.854% when pulling a8e2530938cba832a96fa18518dc03645a823baf on jameshiew:flaky into 9149c828856f20d94cb6d92889506281ff4ff218 on aschn:master.

Hey @jameshiew, I wonder now how accurate are the results between a production and tests with flaky. Do you know a bit more about it ?

@jameshiew Thanks again for contributing the library integration to the unit test suite.


Switching chat topic before the current chat response is finished, the last entry completely disappears

Open WebUI Version: 0.4.8
Ollama Version: 0.5.1
OS: Windows 11
RAM: 192GB
GPU: 2x4090 RTX
Reproducibility: Always
Model: Any model
Installation: Docker CUDA version (Docker Desktop v4.37)
When the answer is pretty long (and thus takes some time) in a chat topic, and I switch to another chat topic and return, the last entry (and the partial answer) was gone. Yet, my computer is still busy churning the answer. When it is done working with that answer and I return to that chat topic, it appears that the entry was completely gone.
Expected behavior: The entry should still be there. I expect to see the answer continues to stream.
This happens since 0.4.x.

Actively being worked on, #2647


Not mobile-first

What are your thoughts on changing the algorithm to be mobile-first (i.e. take font size on mobile as the argument and use min-width in the output)?
Ultimately the effect could be the same, but readability could be better for those accustomed to writing for mobile-first (of which there are many).
Or another option might be to just add a mixin for mobile-first sizing.
See: Precise control over responsive typography

Hi @garrettw,
The main reason it wasn't designed mobile first is that browsers without vw-unit support will correctly render there font-size.
If we use the mobile-first approach, we get this:
SCSS:
.title {
  @include rfs(62);
}

CSS:
.title {
  font-size: calc(23.6px + 3.2vw);
}

@media (min-width: 1200px) {
  .title {
    font-size: 62px;
  }
}

For older browsers with a screen-width smaller as 1200px the font-size will not be set.
However it might be interesting to add an option like $rfs-mobile-first (default value: false) which switches to mobile first rendering?

@garrettw, I just added an option for mobile-first rendering, you can enable it by setting $rfs-mobile-first true.

The article I linked above does it in a slightly different way. Thoughts?
.title {
  font-size: 12px; /* base, mobile-first size */
}

@media (min-width: 400px) {
  .title {
    /* scaling size for viewports between 400px-800px */
    font-size: calc( 12px + (24 - 12) * ( (100vw - 400px) / ( 800 - 400) ));
  }
}

@media (min-width: 800px) {
  .title {
    font-size: 24px; /* largest size for viewports wider than 800px */
  }
}

The purpose of RFS is to make font-resizing as easy as possible, you only need one font-size, resizing is done automatically.
For the method you mention, you will need a minimum and maximum font-size for each element where you want to set the font-size for. Aside from that, you will need to make sure you never cross-size texts (for example a text with a minimum of 14px and a maximum of 18px and an other text with a minimum of 15px and maximum of 17px).

True, you would have to know the min and max for each element. But what do you mean about cross-sizing texts? I don't understand the issue.
I understand that your mixin is focused on ease-of-use with only one parameter. In that case, it might make more sense to me to specify only the smallest font size in the parameter, and then scale up infinitely, based on some $rfs-factor - because there is a practical limit to how small screens can get, but not much limit on how large they can get.
Do you think that could be at least as user-friendly as your way (if not more so)?

If you have a project where a lot of font-sizes are used, you need to remember which minimum/maximum pairs you have combined. If you have a text element with a font size of 14px on mobile and 18px on desktop and you have another element which has a font-size of 15px on mobile, you need to remember to use at least a font-size of 19px on desktop so that the importance of the text-elements remain in relation with each other. If that's not totally clear, don't mind, my point was that RFS is a bit easier to use because it only has one parameter.
I'm starting to understand where you want to go with the mobile-first approach. However, I do think there really is a need for a maximum font-size and not the minimum font-size.
For example, let's take Github. It has a container-width of 980px, if the sizes would scale up infinitely, I would definitely have a problem with bigger titles on my 2560px wide screen.
If you're used to work as a mobile-first developer RFS would indeed feel a bit strange, because it actually works the other way around. However, you need to see the value that is passed to the mixin more as a number that indicates the font-size, rather than an exact font-size. When I was working with RFS for mobile devices, I never know exact how big the font-size of an element was, but I did know what value it is. (this was by far the most vague explanation I gave on Github, but I hope you somehow know what I mean)

If you have a text element with a font size of 14px on mobile and 18px on desktop and you have another element which has a font-size of 15px on mobile, you need to remember to use at least a font-size of 19px on desktop so that the importance of the text-elements remain in relation with each other.

Ah ok, that is clear now. The relation between the sizes is what you were talking about. That makes sense.

For example, let's take Github. It has a container-width of 980px, if the sizes would scale up infinitely, I would definitely have a problem with bigger titles on my 2560px wide screen.

That certainly would be a problem, but the cause is the fixed px-sized container width. Why size it in px at all? Why not percent, rem, or vw? The whole layout should be built on one principle or the other - fluid or not.

However, you need to see the value that is passed to the mixin more as a number that indicates the font-size, rather than an exact font-size.

I do understand that. If I were using a version of rfs that was mobile-first, I would probably specify my minimum font sizes using the Modular Scale library and then let rfs scale it up - rather than specifying a lot of rem sizes with decimals. That way you keep the ease of use factor and the size relations without having to use a bunch of small decimal numbers.

Why size it in px at all? Why not percent, rem, or vw? The whole layout should be built on one principle or the other: fluid, or not.

I think the main idea is to prevent the text from stretching over wider screens making the text less readable.

I do understand that. If I were using a version of rfs that was mobile-first, I would probably specify my minimum font sizes using the Modular Scale library and then let rfs scale it up - rather than specifying a lot of rem sizes with decimals. That way you keep the ease of use factor and the size relations without having to use a bunch of small decimal numbers.
You can use px if you like, rem-sizes with a lot of decimals are not needed.

If you really want to stick with the mobile-first approach, I don't think RFS-technique will be suitable for you. It's just not designed like that. However, feel free the fork RFS or make something from scratch that's more like what you want.
Anyway, thanks for taking your time to figure out how RFS works and for the given feedback. @garrettw.


Feature/hotfix pack for beta(vol.1)

Pull Request Test Coverage Report for Build 515118980

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.007%) to 19.44%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/templates/IndexPage/IndexPageAnalytics.tsx
0
2
0.0%

Totals

Change from base Build 514431890:
-0.007%

Covered Lines:
406

Relevant Lines:
2111

💛  - Coveralls

Pull Request Test Coverage Report for Build 515118980

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.007%) to 19.44%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/templates/IndexPage/IndexPageAnalytics.tsx
0
2
0.0%

Totals

Change from base Build 514431890:
-0.007%

Covered Lines:
406

Relevant Lines:
2111

💛  - Coveralls


Multivariate polynomials

This collects all proposals to integrate multivariate polynomials in Spire.
Note: we should be careful about handling (non-?)commutativity, and which polynomial ring is obtained depending on the coefficient type.

#159 Proposal by @jamesthompson in 2013
#560 Update by @zmre in 2016
#562 Update by @denisrosset in 2016

After discussion with @non, we currently think that multivariate polynomials should wait that univariate polynomials are at a sufficient level of quality (mathematical soundness, code coverage).


Block Proof CI

This PR adds a small script to generate a proof from a known witness:
https://etherscan.io/block/19240705
The idea is to have some checks to catch regressions before they make their way into develop and testing branches.

Awesome that we finally have some CI for this, thanks!


XSRF-TOKEN expire workflow is shitty

Laravel Version: 5.4.23
PHP Version: PHP 7.0.18
Database Driver & Version: MySQL 5.7

Description:
I use the Laravel Auth/Login Process. If i use the remember me function. Than the XSRF-TOKEN is expired next day.
The logic how XSRF-TOKEN will created conjunction remember me function is not really cool .
Steps To Reproduce:

login process with the function Remember me
after 2 hours submit a Post (be sure doesn't use the website)
i became \Illuminate\Session\TokenMismatchException.

Debuging:
I started to debuging this Website and i found:
config: session.lifetime = 120 minutes
and
https://github.com/laravel/framework/blob/v5.4.23/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php#L158

My workaround is now config.session:
'lifetime' => 525600, // 60 min * 24 hours * 365 days = 525600

Maybe it is my issue, i don't use the .... return response($html, 200); function


Fortune Cookie Generator

Project title
Fortune Cookie Generator
Project Description
A web-app based fully responsive Fortune Cookie Generator.
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x] JavaScript

/assign

Hi @khushi-purwar @meinhoonharsh I would like to let you know that this project has been plagiarized from the Fortune Cookie generator project I submitted to Arpit Jain's Amazing Js Projects. Here is the link: https://github.com/arpit456jain/Amazing-Js-Projects/pull/447
You can compare the code, the layout is also the same.


Computation of document order needs to be cached

This program causes intense performance usage. Ultimately, it's because Value::into_string is being called repeatedly, which triggers the computation of nodes in document order. "Thankfully", I realized this problem when adding it:
https://github.com/shepmaster/sxd-xpath/blob/350c51e89bccd0271898b46caa9c074f4ef31927/src/nodeset.rs#L349

extern crate sxd_document;
extern crate sxd_xpath;

use std::fs::File;
use std::io::Read;
use std::collections::HashMap;
use std::borrow::Cow;
use sxd_document::dom::{Document, Element};
use sxd_xpath::{Context, Factory, Value};
use sxd_xpath::nodeset::Node;
use sxd_document::parser;

type DynResult<T> = Result<T, Box<::std::error::Error>>;

fn main() {
    let filename = "radlex.owl";
    println!("Reading file");
    let mut f = File::open(filename).unwrap();
    let mut data = String::new();
    f.read_to_string(&mut data).unwrap();
    let package = parser::parse(&data).unwrap();
    build_rid_index(&package.as_document()).unwrap();
}

/// Build a dictionary of an RID to its respective XML element
fn build_rid_index<'d>(
    radlex: &'d Document<'d>,
) -> DynResult<HashMap<Cow<'d, str>, Element<'d>>> {
    let root = radlex.root();

    let mut ctx = Context::new();
    ctx.set_namespace("xsp", "http://www.owl-ontologies.com/2005/08/07/xsp.owl#");
    ctx.set_namespace("xsd", "http://www.w3.org/2001/XMLSchema#");
    ctx.set_namespace("rdf", "http://www.w3.org/1999/02/22-rdf-syntax-ns#");
    ctx.set_namespace("rdfs", "http://www.w3.org/2000/01/rdf-schema#");
    ctx.set_namespace("owl", "http://www.w3.org/2002/07/owl#");
    ctx.set_namespace("swrl", "http://www.w3.org/2003/11/swrl#");
    ctx.set_namespace("swrlb", "http://www.w3.org/2003/11/swrlb#");

    println!("Building query");
    let factory = Factory::new();
    let xpath = factory.build("/rdf:RDF/*[starts-with(@rdf:ID, 'RID')]")?;
    let xpath = xpath.expect("No XPath was compiled");

    println!("Evaluating query");
    let value = xpath.evaluate(&ctx, root)?;

    println!("Building dictionary");
    if let Value::Nodeset(nodeset) = value {
        let dict: HashMap<_, _> = nodeset
            .into_iter()
            .filter_map(|x| match x {
                Node::Element(e) => Some(e),
                _ => None,
            })
            .map(|e| {
                let rid = e.attributes()
                    .into_iter()
                    .find(|x| x.name().local_part() == "ID")
                    .unwrap()
                    .value();
                (rid.into(), e)
            })
            .collect();

        Ok(dict)
    } else {
        panic!()
    }
}

Source file
/cc @Enet4

It was also pointed out that we can have a "short cut" if the nodeset only has a single node. In that case, the computation of document order can be avoided entirely.

Using the short cut does fix this case 👍
real	0m2.409s
user	0m2.168s
sys	0m0.221s

I also cleaned up the original code a bit:
    let root = radlex.root();

    let mut ctx = Context::new();
    ctx.set_namespace("rdf", "http://www.w3.org/1999/02/22-rdf-syntax-ns#");

    let factory = Factory::new();
    let xpath = factory.build("/rdf:RDF/*/@rdf:ID[starts-with(., 'RID')]")?;
    let xpath = xpath.expect("No XPath was compiled");

    let value = xpath.evaluate(&ctx, root)?;

    if let Value::Nodeset(nodeset) = value {
        let dict = nodeset
            .into_iter()
            .filter_map(|node| node.attribute())
            .map(|a| (a.value().into(), a.parent().unwrap()))
            .collect();

        Ok(dict)
    } else {
        panic!()
    }

What's painful about caching in the full case is that there's nowhere really good to store the cache. The closest place right now would be something like the Context, but it feels really awkward to require passing a Context to methods like Value::string.
The best alternative within the current structure I can think of would be some ugly hidden thing inside of a Document. That leads to issues around staleness of the cache if the document gets updated.

A pragmatic compromise could be to have a pair of functions, such as fn string(&self) and fn string_with_cache(&self, DocOrder). This would allow the library to use the optimized version, but not force end users to deal with it unless they needed it.


Unit test for JS platform don't work

See https://github.com/Kotlin/kotlin-frontend-plugin/issues/131 and https://github.com/Kotlin/kotlin-frontend-plugin/issues/24.

They work in the current version.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_07risvb5sp/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_07risvb5sp/clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_07risvb5sp/clone/recipe/meta.yaml:43: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_07risvb5sp/clone/recipe/meta.yaml:43: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_07risvb5sp/clone/recipe/meta.yaml:43: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_07risvb5sp/clone/recipe/meta.yaml:43: missing_description: The recipe is missing a description
Errors were found


Set default log level to 'info'

I believe that the default choice should provide the user with enough output to get an understanding of what's going on in the tool at the moment, which the info level provides. I suggest we make this level the default.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #279   +/-   ##
=========================================
  Coverage     80.18%   80.18%
  Complexity      510      510
=========================================
  Files            66       66
  Lines          1509     1509
  Branches        233      233
=========================================
  Hits           1210     1210
  Misses          208      208
  Partials         91       91

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 6584c96...14ddb95. Read the comment docs.


How should look config for the exchange Bitfinex?

I also need to use bitfinex ... apparently GDAX is only available in USA.
I made the following changes at the config.js files:
I just installed the program, s0 I'm not sure if anything else is required ... but I get some logs about transactions and data from bitfinex and so far it looks working
in config.js put your api key/secret into the  fileds:
c.gdax_key = 'YOUR_BITFINEX KEY'
c.gdax_secret = 'YOUR_BITFINEX SECRET'
c.gdax_passphrase = '' // leave empty for bitfinex
c.trade_log = true // log new trades as they come in.

// watch these exchanges
c.watch_exchanges = [
  "bitfinex",
  //"gdax",
  //"kraken",
  //"poloniex"
]

is the above configuration correct ? if somebody can confirm, it will be helpful for others

That config looks OK, but I have issues with the trading logic config that seems to only work with GDAX. Anyone else have that problem?

@nullprobe, Support for other exchanges is ongoing. What exchange are you trying to use?

@JFD3D , I'm trying to use it for Bitfinex, like OP.

Added bitfinex key,secret...
tarding log monitoring SELL only
btc-usd_1      | 01/13/2017 11:20:35 AM UTC [    bitfinex]    m24738220      20 trades. 01/13/2017 07:40:33 AM UTC SELL        39.750 at       $777.40 BTC/USD
btc-usd_1      | 01/13/2017 11:20:56 AM UTC [    bitfinex]    m24738220      18 trades. 01/13/2017 07:40:56 AM UTC SELL        11.894 at       $777.13 BTC/USD
btc-usd_1      | 01/13/2017 11:21:16 AM UTC [    bitfinex]    m24738221       4 trades. 01/13/2017 07:41:07 AM UTC SELL         2.182 at       $777.26 BTC/USD
btc-usd_1      | 01/13/2017 11:21:36 AM UTC [    bitfinex]    m24738221       5 trades. 01/13/2017 07:41:35 AM UTC SELL         6.275 at       $777.29 BTC/USD
btc-usd_1      | 01/13/2017 11:21:56 AM UTC [    bitfinex]    m24738221      14 trades. 01/13/2017 07:41:55 AM UTC SELL        18.373 at       $777.19 BTC/USD

hi to all. I'm new of this website. I've just configured zenbot to trade with bitfinex. someone have correct settings of conf.js to trade on bitfinex?
thank you
Stefano


Some out of date screenshots - ribbon, conditional formatting, visualisation icons

Ribbon screenshot for accessing selection pane is out of date
Ribbon screenshot for switching theme is out of date
Accessing conditional formatting for alt text screenshot is out of date
Icons in screenshots of visualisation pane are out of date (particularly relevant as part of the goal of updating them was to improve contrast)

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

ID: 762701ab-7066-612d-cdc2-a729ba1b5483
Version Independent ID: 8a64d563-9737-16d3-d83e-fb56e8d3d95c
Content: Creating accessible reports in Power BI - Power BI
Content Source: powerbi-docs/create-reports/desktop-accessibility-creating-reports.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi, @PeterGrahamJersey -- thanks for your comment! Referring it to the author to add to his backlog.

Hi @PeterGrahamJersey ,
I see that this Git issue is a bit old, so I'm going to close it.  I hope that you were able to get your questions answered. If not, please revisit the article since it has been updated several times since this Git Issue was submitted.  Another option is to submit your question to the Power BI community (community.powerbi.com).
All the best,
the DOCS team


Reopening explorer opens the file under the cursor on a preview editor.

VSCode Version: 1.17.0 be377c0faf7574a59f84940f593a6849f12e4de7
OS Version: macOS Sierra 10.12.6

Steps to Reproduce:

Close all editors.
Show explorer (shift+cmd+e) and move the cursor to a file.
Hide sidebar (cmd+b).
Show explorer again (shift+cmd+e). Then, the file under the cursor is opened on a preview editor.

Reproduces without extensions: Yes

I acknowledge this issue and the explorer has always behaved like this.
The problem here is that the explorer get focus due to the newFile action and whenever explorer gets focus it always opens the focused element here
I think this is a limiation we can live with.
fyi @bpasero

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


Router should not throw an error for malformed URI params

Coverage increased (+6.3%) to 98.413% when pulling 6dadc6f53cf9594187e89dbe7f41e87a5e04ae21 on frenzzy:params-decode into 2954864c5db917a2373b1f10795ef6f3dd82df90 on kriasoft:master.

Coverage increased (+6.3%) to 98.333% when pulling 4feda8a4aa4df6a5ebbe78f8603989993ffe9fb1 on frenzzy:params-decode into 2954864c5db917a2373b1f10795ef6f3dd82df90 on kriasoft:master.

Coverage increased (+6.3%) to 98.333% when pulling c30d5d4e9b789ac1fa6b9446fb7e8604eb77425b on frenzzy:params-decode into 2954864c5db917a2373b1f10795ef6f3dd82df90 on kriasoft:master.

Coverage increased (+6.3%) to 98.333% when pulling 85005f0094abaa4626009fa1f758fdce0da43e3a on frenzzy:params-decode into 2954864c5db917a2373b1f10795ef6f3dd82df90 on kriasoft:master.

Coverage increased (+6.3%) to 98.333% when pulling bfad69d09ff413c882f93eac487c67491665ada8 on frenzzy:params-decode into 2954864c5db917a2373b1f10795ef6f3dd82df90 on kriasoft:master.

Coverage increased (+7.9%) to 100.0% when pulling 6e2a56384e024a4da47e151bc17c25c0acedf715 on frenzzy:params-decode into 2954864c5db917a2373b1f10795ef6f3dd82df90 on kriasoft:master.

Coverage increased (+7.9%) to 100.0% when pulling 2e30e71849dd3e07c880f07798758e45d0c12543 on frenzzy:params-decode into 2954864c5db917a2373b1f10795ef6f3dd82df90 on kriasoft:master.


Add IstellaBot I believe it is an Italian search engine - to the bots list

See github issue: https://github.com/WhichBrowser/Parser-PHP/issues/568
istellabot/t.1.13 (current)
istellabot/t.1.13

Dead bots (not going to get added to this pr)
istellabot/t.1
istellabot/t.1

istellabot
istellabot/Nutch-1.11
istellabot/Nutch-1.10
istellabot-nutch/Nutch-1.10

IstellaBot/1.23.15
Mozilla/5.0 (compatible; IstellaBot/1.23.15 +http://www.tiscali.it/)

IstellaBot/1.18.81
Mozilla/5.0 (compatible; IstellaBot/1.18.81 +http://www.tiscali.it/)

IstellaBot/1.10.2
Mozilla/5.0 (compatible; IstellaBot/1.10.2 +http://www.tiscali.it/)

IstellaBot/1.01.18
Mozilla/5.0 (compatible; IstellaBot/1.01.18 +http://www.tiscali.it/)

Link: http://www.tiscali.it/

Coverage increased (+0.02%) to 99.97% when pulling 0192eb5f65e71f2cef101aca8a023584be7d4b3d on ayumi-cloud:IstellaBot into 880b9fa797401d14b28956442944c3daa70240ff on WhichBrowser:master.

Fixed by 1cf9b598ed238af6203f20a735a09f637130daef

Fixed by 1cf9b598ed238af6203f20a735a09f637130daef


impl std::fmt::Debug for diesel::pg::PgConnection

Feature Description
impl std::fmt::Debug for diesel::pg::PgConnection {
    // ...
}

Possible solution
My idea would be to just store the database_url on PgConnection::establish(database_url) in the PgConnection and use it as the debug message.
But I am open to include additional information.
Happy to implement it myself 😁

What is your actual usecase for this? Printing out the connection url is likely not a good idea as it can contain potential secret credentials.

Thank you for coming back to be @weiznich
You are right, I didn't think about the credentials getting potentially exposed.
My usecase is mainly convenience (😬). What I'd like to do is:
pub static DB: OnceCell<PgConnection> = OnceCell::new();
// actually a `r2d2::Pool<...>`, but let's ignore that

fn main() {
    let conn = PgConnection::establish("conn_str").unwrap();
    DB.set(conn).unwrap(); // this is not possible
}

In the system I am working on we are using a global database connection in a OnceCell. I am not able to call OnceCell::set(conn).unwrap(), since it wants to print the debug message of PgConnection in the error case. I am very sure that it won't fail, so I am fine with calling unwrap instead of explicitly handling it.

The potential gain is just one or two lines less code, but since I though the effort is also low we could still do it. What do you think about only dropping the password in the stored string and saving the rest?
E.g.:
"postgres://user:password@<IP_ADDRESS>:5678/db_name" -> "postgres://user@<IP_ADDRESS>:5678/db_name

"Just" dropping the password/username there would mean that you have to parse the url. That's quite a lot of complexity for such a simple feature. Additionally I'm not sure that the password field is the only potential confidential field there. What's for example with ssl based authentication?

I was thinking, that there actually shouldn't be too much of a security problem with giving the whole conn_str as debug message, because only the application establishing the PgConnection will ever see the string.
Thereby it is no secret to it, right?

We don't need to implement this because you can use expect instead of unwrap. You can see an example here, https://github.com/pksunkara/reign/blob/master/reign_model/src/plugin.rs#L32-L38

We don't need to implement this because you can use expect instead of unwrap. You can see an example here, https://github.com/pksunkara/reign/blob/master/reign_model/src/plugin.rs#L32-L38

Thank you for your input @pksunkara :D
But as far as I understand both .unwrap() and .expect() require the error to implement std::fmt::Debug (see core/result.rs#910).
And in your example you are still doing:
if DB.set(pool).is_err() {
    panic!("Unable to store the database connection");
}

But I'd like to have it as:
DB.set(pool).unwrap();
// OR
DB.set(pool).expect("Unable to store the database connection");

@Urhengulas Both require that the Error type implements Debug, not the Ok type. (https://doc.rust-lang.org/std/result/enum.Result.html#method.expect), so either of those solutions already work today.

If you still want to use it something like that, DB.set(pool).map_err(...).unwrap()

@Urhengulas Both require that the Error type implements Debug, not the Ok type. (https://doc.rust-lang.org/std/result/enum.Result.html#method.expect), so either of those solutions already work today.
Closed as I consider the underlying problem to be solved.

@weiznich I wouldn't consider it solved.
You are right that the error type needs to implement Debug, BUT in case of OnceCell::set(PgConnection) the PgConnection is the Error type! (see https://docs.rs/once_cell/1.5.2/once_cell/sync/struct.OnceCell.html#method.set).

Alternative, DB.set(pool).map_err(...).unwrap()

@pksunkara Thanks for the workaround.

Ok then let me word it that way: I would be happy to merge a PR implementing Debug for all connection types as long as it does not reveal potentially confidential information. I consider database url's to be potential confidential here.

Ok then let me word it that way: I would be happy to merge a PR implementing Debug for all connection types as long as it does not reveal potentially confidential information. I consider database url's to be potential confidential here.

That sounds good 😄
Let me think what other valuable information one could put in there. Most straight forward would be a static "Connection to [postgres, mysql, sqlite] database", but maybe we can include a bit more.

@Urhengulas maybe you can use a wrapper on the connection type that implements Debug + Error?

@Urhengulas maybe you can use a wrapper on the connection type that implements Debug + Error?

@Mingun That would work. Thank you for the input.
Nevertheless I am looking for a more general upstream solution which simplifies the code of multiple people, because I think the OnceCell<Pool<ConnectionManager<PgConnection>>> is a common pattern.

You would need to change r2d2 too and forward the debug IIUC

You would need to change r2d2 too and forward the debug IIUC

Pool and ConnectionManager already implement Debug.

fyi: with #2572 the debug message of Pool<ConnectionManager<PgConnection>>> now looks like:
Pool {
    state: State {
        connections: 10,
        idle_connections: 10,
    },
    config: Config {
        max_size: 10,
        min_idle: None,
        test_on_check_out: true,
        max_lifetime: Some(
            1800s,
        ),
        idle_timeout: Some(
            600s,
        ),
        connection_timeout: 30s,
        error_handler: LoggingErrorHandler,
        event_handler: NopEventHandler,
        connection_customizer: NopConnectionCustomizer,
    },
    manager: ConnectionManager {
        database_url: "postgres://postgres:password@localhost",
        _marker: PhantomData,
    },
}

The debug message of the connection actually gets omitted and just says PhantomData, but is required to be implemented nevertheless.

I would personally still not recommend to do expect or unwrap because ConnectionManager has the database url with all the secrets.

And If we can update ConnectionManager in r2d2 and implement a Debug for it manually, then we don't need Debug for these connections here in diesel.

I would personally still not recommend to do expect or unwrap because ConnectionManager has the database url with all the secrets.

@pksunkara I see that one should keep the database_url secret, but the application having the ConnectionManager did establish the connection and thereby already knows about the database_url.
So I don't see the issue.

It's not about the application knowing the database_url but about the secrets being logged because of unwrap or expect

It's not about the application knowing the database_url but about the secrets being logged because of unwrap or expect

True, Then I would suggest to change the debug message of ConnectioManager in a 2nd PR.

Yeah, we do that by implementing a custom Debug for ConnectionManager which means we can skip the Connection debug there which means there is no reason for this PR to exist.

Yeah, we do that by implementing a custom Debug for ConnectionManager which means we can skip the Connection debug there which means there is no reason for this issue and related PR to exist.

I agree that we should have a custom Debug for ConnectionManager<T> which doesn't need T: Debug. Thereby we enable easier use of static DB: OnceCell: Pool<ConnectionManager<PgConnection>>>.
But static DB: OnceCell<PgConnection> would not work. If this isn't a common pattern we can drop #2572, but I am unsure about that. Need your experience here..


Update README to describe .tflite and edge TPU model generation steps

It would be great if README also showed how the quantized graph (tflite) was generated.
This will also help people with their own custom trained models and with other versions of PoseNet (MobileNet 050, 100).

In principle the quantized graph was created using quantization aware training (https://github.com/tensorflow/tensorflow/tree/r1.13/tensorflow/contrib/quantize) but with respect to PoseNet specifically, unfortunately the training data and training scripts have not yet been released by the PoseNet team, so until they do so we're unable to offer these here for Coral either.


[Feature Request]: Allow passing in environmental variables

Describe why this change is needed
Currently you can not set ENV parameters for the helm chart.
Allowing such setting would enable customers to set required settings such as corporate proxy settings via https_proxy/no_proxy, so they can reach ACM API endpoints.
Describe solutions and alternatives considered (optional)
I tried to contribute the below method a few months ago, but you needed tests writing and I don't have IAM access within our corperation to create PCA resources.
values.yaml
env:
  #var1: myvar1
  #var2: myvar2

deployment.yaml
          env:
          {{- range $key, $value := .Values.env }}
          - name: {{ $key }}
            value: "{{ $value }}"
          {{- end }}

example values
env:
  http_proxy: http://corpproxy:3128
  https_proxy: http://corpproxy:3128
  no_proxy: "localhost.<IP_ADDRESS>,instance-data,<IP_ADDRESS>/8,<IP_ADDRESS>,<IP_ADDRESS>/10,.corptld.plc"

### Is there anything else you would like to add?

We've been using this method for months now without issues and the application appears to honour the proxy env parameters.

Thank you for submitting the feature request to AWS Private CA Issue plugin. We will review the request and get back to you

Hello! We have just posted a PR for your feature request: https://github.com/cert-manager/aws-privateca-issuer/pull/82


Fix for SNAP-3234

Added fix for SNAP-3234 (referring the PR https://github.com/groupon/spark-metrics/pull/24)
Added code changes for deleting table metrics if table gets deleted

Also, we need to add build targets to publish the artifacts on Maven.


EASUN iGrid IV 5.6 issue

Hi all, I am currently trying to integrate my EASUN iGrid IV 5.6. As far as I know, it is a clone of an InfinSolar inverter.
Unfortunately it does not work for me yet.
I did a little search and flashed esp8266-test-protocols on the esp.
I found out that I have to send ^P005GSX\r to the inverter to get a response.
According to different forums the inverter uses the protocol P18.
as an answer I got the following.
[11:46:09][D][uart_debug:158]: <<< "^D1062310,500,0000,000,0000,0000,000,547,000,000,000,039,065,029,000,000,2404,0000,2603,0000,0,2,0,0,1,2,2,0'\xF9\r"
The values would need to include the following information.
500 = 50,0 Hz
039 = 39A Akku loading
065 = 65% Akku Capacity
2404 = 2404 Watt Solar Power
2603 = 260,3V Solar Voltage
547 = 54,7 V Battery
would it be possible to include this in the code? or can someone tell me how to customize this myself.
Thanks in advance
Christian

OK, I've found that this is https://github.com/syssi/esphome-pipsolar/issues/54 exactly the same topic. I therefore close this request


Extend netsniff.js example to support passing Headers, element timing an...

...d catch page errors

Closing this due to lack of response after > 1 year.


Uptake Enum-driven visibility

This PR is for validation of the uptake of https://github.com/microsoft/typespec/pull/4825
It masks some no-deprecated lint errors that result from the deprecation of getVisibility

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/typespec-autorest
:x:@azure-tools/typespec-azure-core
:x:@azure-tools/typespec-azure-resource-manager
:x:@azure-tools/typespec-client-generator-core

Show changes

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Fix for all whitespace within json being trimmed

@weierophinney V1.0.6 trims all whitespace in the json body including in strings that contain internal spaces. I don't see why trim wouldn't work in this case, but if not, the suggestion @steverhoades mentioned on the commit with adding the $ anchor on the 2nd regex works too.
As a side note, the testOnFinishWillRemoveAnyUploadFilesUploadedByTheListener test fails on mac. This is because in the listener that should remove the uploaded files, the $fileinfo['tmp_name'] starts with /private/var whereas the uploadTmpDir in the listener starts with /var. I think this mapping is just a mac thing but it makes the listener skip the removal of the file.

@dstockto I've tested with our app, this fix looks good.

Closing in favor of #39.


m_proxy is missing

Hey. While trying to use CEF I found your post about not using that monster and rather have this minimalistic approach.
Thanks for your work!
When I try to compile according to your introduction, I get the compiler error that "m_proxy is not defined", first used in "void wxWebViewMiniBlink::SetProxy(const wxString& proxy)"
I use wxWidgets 3.1.0 on msWindows 10 x64. I also tried my self compiled wxWidgets from 1st of November 2018. And I use the precompiled Node.dll from your download.
I checked the online repository from wxWidgets and wxWebCiewBlink for m_proxy, but it is nowhere to be found. Where is it supposed to be defined?
Thank you.
Natulux

Fixed

Wow, I never estimated a response as fast as yours. Thanks, it compiles fine now! :-)


new(libscap): add gVisor scap engine

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
This PR continues the work required to get gVisor events into Falco. This PR adds a C++ class that can be used to manage the state, connections and required memory for the engine that can connect to gVisor seccheck. In order to be complete it will require the additions in https://github.com/falcosecurity/libs/pull/213 , but I'm publishing it already so maintainers can start to take a look at it if they wish.
This code has been written along with @loresuso and help from @fvoznika from the gVisor team. I will add appropriate Co-Author to the commits when it's out of WIP.
Which issue(s) this PR fixes:

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

new(libscap): add gvisor engine

Hi @LucaGuerra. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

Needs approval from an approver in each of these files:

OWNERS

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

Nice to see this taking shape! 🎉

/ok-to-test

@LucaGuerra: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
9d552fef0d93f63153c4ff969807d2a1d30f9b81
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@LucaGuerra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
9d552fef0d93f63153c4ff969807d2a1d30f9b81
link
true
/test build-libs-minimal

build-libs-arm
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-arm

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@LucaGuerra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
9d552fef0d93f63153c4ff969807d2a1d30f9b81
link
true
/test build-libs-minimal

build-libs-arm
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-arm

build-libs-bundled-deps
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-bundled-deps

build-libs
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs

build-libs-with-chisels
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@LucaGuerra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-arm

build-libs-bundled-deps
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-bundled-deps

build-libs
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs

build-libs-with-chisels
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-with-chisels

build-libs-minimal
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@LucaGuerra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-bundled-deps
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-bundled-deps

build-libs
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs

build-libs-with-chisels
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-with-chisels

build-libs-minimal
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-minimal

build-libs-arm
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-arm

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@LucaGuerra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-bundled-deps
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-bundled-deps

build-libs-with-chisels
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-with-chisels

build-libs-arm
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-arm

build-libs
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs

build-libs-minimal
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@LucaGuerra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-with-chisels
4b945452fa3ec3c6885d32e5c8ebc210185a9a78
link
true
/test build-libs-with-chisels

build-libs-arm
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-arm

build-libs
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs

build-libs-minimal
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-minimal

build-libs-bundled-deps
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@LucaGuerra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-arm

build-libs
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs

build-libs-minimal
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-minimal

build-libs-bundled-deps
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-bundled-deps

build-libs-with-chisels
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@LucaGuerra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs

build-libs-bundled-deps
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-bundled-deps

build-libs-with-chisels
cdd6404b365e510aef07dc305e77068990d2237b
link
true
/test build-libs-with-chisels

build-libs-minimal
fb957dc03aa353d397e33fcfa782bb43a8f3765b
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@gnosek @FedeDP addressed all your comments!

LGTM label has been added.  Git tree hash: e87bcbba2e3ceb1f79524a557981738adfe5b6b4

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

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

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

New changes are detected. LGTM label has been removed.

LGTM label has been added.  Git tree hash: 730f8da9d7aa10b75160ac11c15a376a5525a352

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

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

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

/retest

New changes are detected. LGTM label has been removed.

/retest

/approve

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

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

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

LGTM label has been added.  Git tree hash: 22f36235d7fb7e05e18688796fbc0dcedede7bf7

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

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

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

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

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

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


Audit SAML (SSO) Certs expired dates through Powershell.

Is it possible to use PowerShell (AzureAD) to expose the expiration dates of SSO SAML certs? I would identify apps with expiring certs so they can be renewed in a timely fashion. Or is there a report or something else in Azure that can be run to expose this?

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

ID: 431fee33-ba1b-2d89-0fb5-64c49eecfbd0
Version Independent ID: ec2993d0-bf2d-30f7-80c6-78fe7ab869b4
Content: Manage federation certificates in Azure AD
Content Source: articles/active-directory/manage-apps/manage-certificates-for-federated-single-sign-on.md
Service: active-directory
Sub-service: app-mgmt
GitHub Login: @msmimart
Microsoft Alias: mimart

@Ashok103606 Closing this one as duplicate of #48662