Swift Compiler Error (Xcode): Stored properties cannot be marked potentially unavailable with '@available'

Swift Compiler Error (Xcode): Stored properties cannot be marked potentially unavailable with '@available'
/Users/..../flutter/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.4.3+7/ios/Classes/Types/UserScript.swift:12:5
Uncategorized (Xcode): Command SwiftCompile failed with a nonzero exit code

Same issue here! hope to be fixed soon

I have same issue with Xcode14，but it is normal to use xcode13

For temporary fix update version in Podfile platform :ios, '14.0'

+1

Doesn't seem to work on my end. Do I have to do anything else other than updating the Podfile's platform :ios, to 14.0?

Got the same issue here, for a temporary fix, I used this solution and removed the @available line

For temporary fix update version in Podfile platform :ios, '14.0'

Got the same issue here, for a temporary fix, I used this solution and removed the @available line

For temporary fix update version in Podfile platform :ios, '14.0'

need to fix this soon.. burning here

same issue here , need fix soon please..

+11111111111

+1

is there any update on this issue, I am facing this issue after updating Xcode

Still no fix? 🤦

Just have to Downgrade to 13.. Then it works fine. For fix

Still no update?

Released new version 5.4.3+8 with the fix!
Is there a fix for Dart SDK version is 2.12.2?


Disable tracing of fast resolvers

I want to merge this change because we'd like to reduce the number of traces being collected from fast pieces of code, I've checked all resolvers which were removed and they all take milliseconds to complete but send like 1000 traces per larger request.
ℹ  This is a 3.1 port of https://github.com/saleor/saleor/pull/11031

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: CLOUD-2151 Disable tracing of fast resolvers


Update Gopkg.toml to point to kubernetes-1.12.0

This PR updates Gopkg.toml to point to K8S 1.12.0.

I thought that files were missing from the vendor dir, but I confirmed by running dep ensure.
/lgtm
/approve

/lgtm
/approve


Document logging flags

Users are not aware that they can customize logging we should document the available zap flags.

Hi there @regadas, I'd like to give it a try, however, I have some questions...

Where do I check where all these logging flags are to be documented to ensure I'll document them all?
Will we document them on README?

Thanks in advance!


App not installing on windows 11

I just tried to install the app in windows 11 version 21h2 build 22000.856
and got the following errors. I just took screenshots of everything as it happened.
After all of that a tooltip that says please wait that follows the mouse cursor around and the installer just hangs.

UPDATE: when i run the installer as administrator, the app installed without issue.


Reduce memory usage from inbound packet queue

Currently, the receivedPacket queue has room for 10K packets. That means every connection takes 10K pointers worth of memory (usually 78KiB), even when idle.
It would be really nice if this queue were variable length (or possibly just smaller).

For context on why I care about 78KiB of memory: if all 3K+ connections held by my go-ipfs daemon right now used QUIC, I'd be using 50% more memory (+225MiB).

Yes, that queue is overly large. We once set it equal to the congestion window, and then increased the congestion window by 10x. We can probably get away with a value of 128 or 256 here.

256 or even 1024 is reasonable.


Use preset only on some files

Hi, I couldn't find the info in the docs or the issues.
Until now I've only had in my project one test file with integration tests called calls.test.js. Every test required Chrome so having "preset": "jest-puppeteer" was a good solution.
Now I want to add unit tests in env.test.js, and I want to be able to run it separately from calls.test.js. However, even npm run test env.test always also loads the browser right now, no wonder with that preset.
Is there a way to apply "preset": "jest-puppeteer" only when certain files (in my case calls.test.js) are run?

Hello @georgjaehnig, the best option to do it actually is to have two separated Jest configs and point one or the other. https://jestjs.io/docs/en/cli#config-path

Thank you, that works!


Fix reporting tests

Adapt report config file to CLI11
update dat files to 1.2
Add reportinglib to DYLD_LIBRARY_PATH (MacOS compatibility)

please retest

please retest

please retest


[Bug?]

Is there an existing issue for this?

[X] I have searched the existing issues

Have you updated FilePond and its plugins?

[X] I have updated FilePond and its plugins

Describe the bug
Why does formData contain 2 file fields, one of which is an empty object and 1 binary object, and the File object cannot be obtained?

But function writing can solve this problem
server: {
        process: (fieldName, file, metadata, load, error, progress, abort, transfer, options) => {
          const formData = new FormData();
          formData.append(fieldName, file);
          const request = new XMLHttpRequest();
          request.open('POST', '/api/upload');
          request.upload.onprogress = (e) => {
            progress(e.lengthComputable, e.loaded, e.total);
          };
          request.onload = function () {
            if (request.status >= 200 && request.status < 300) {
              // the load method accepts either a string (id) or an object
              load(request.responseText);
            } else {
              // Can call the error method if something is wrong, should exit after
              error('oh no');
            }
          };

          request.send(formData);

          // Should expose an abort method so the request can be cancelled
          return {
            abort: () => {
              request.abort();
              abort();
            },
          };
        },
      },

Reproduction
20240201174242.webm
Environment
- Device:4.30.6
- OS:windows
- Browser:Google Chrome v120.0.6099.227

You can use a custom process function to upload only the file.
By default FilePond posts a data object (JSON string) with file information and a file object.
See: https://pqina.nl/filepond/docs/api/server/#process


Integrate create IA request with the backend side

Currently, client side sends a request to create an IA as
{title: "", subInterestAreas: [], tags: [], description: "", accessLevel: "public"}
but the backend side expects it as.
{
"accessLevel": 0 | 1 | 2
"name": "",
"nestedInterestAreas": [],
"wikiTags": [""],
"description": ""
}
I'll update the sent values and the request in the client side.

Corresponding PR can be seen here.


Make small fix to tutorial to reduce redundancy

Remove redundancy in docs. Directions to install each of these prereqs starts 1 paragraph below.

I don't like this change as it makes the reader unaware of the fact that some tools, other than a simple Rust install, are needed. There's no other clear indication that trunk must be installed and where to get it.

Are the paragraphs that follow not sufficient? I.e. line 44 on the left? When I was reading through, I didn't realize there were directions on how to install these below, so I went out looking for instructions myself.

Cool, np.


[fallback]: Refactor fallback and use request context

What this PR does / why we need it:
Refactors fallback and use request context

Special notes for your reviewer:
Remaining parts:

[x] Fix nil interface error in tests
[x] Add more tests to cover all fallback types

Not ready for review

Well, I tried to make it more readable but still feels a bit complicated. @stp-ip 	What do you think?

Oh, seems like something is messed up. I don't think a push job supposed to get passed for this PR.

At least the push job failed also no worries one shouldn't pull in latest on container images anyway :)

\o/


Make prompt work in includes

Make prompt work in includes by using same IO in the include handler as in the main handler. Only the statement struct is using the included file IO.
Also, disable password prompts in non-interactive mode.

This breaks output when someone has a .usqlrc file:
$ ./usql
Type "help" for help.

Type "help" for help.

(not connected)=> ^C
(not connected)=> \q
$ rm ~/.usqlrc
$ ./usql
Type "help" for help.

(not connected)=>

I'll look into fixing this to see if there's an easy workaround. Still investigating if this fixes the other issues with the \prompt command.

This breaks output when someone has a .usqlrc file:
$ ./usql
Type "help" for help.

Type "help" for help.

(not connected)=> ^C
(not connected)=> \q
$ rm ~/.usqlrc
$ ./usql
Type "help" for help.

(not connected)=>

I'll look into fixing this to see if there's an easy workaround. Still investigating if this fixes the other issues with the \prompt command.

@nineinchnick I've merged this, and made some quick minor edits to make the output consistent. Additionally, I'll endeavor to try to fix the output issues and make sure \prompt works properly with \i and \ir. Will not cut a new release until this issue is fixed, as it breaks interactive output.

@nineinchnick I'm backing out part of this change. With the upcoming rline implementation, this will end up getting fixed as a side effect. While \prompt now won't work in non-interactive settings, I'd rather have that be the behavior temporarily. After I finish the rline implementation, the next push will aim for psql compatibility. Planning on getting this done before next major release.

@nineinchnick I'm backing out part of this change. With the upcoming rline implementation, this will end up getting fixed as a side effect. While \prompt now won't work in non-interactive settings, I'd rather have that be the behavior temporarily. After I finish the rline implementation, the next push will aim for psql compatibility. Planning on getting this done before next major release.


feat: added example for Crystal language

This change is

Thanks for the pull request!
We usually add an install script that would, in this case, install crystalline somewhere in lsp-examples/crystal/. Would that be feasible?

Thanks for the pull request!
We usually add an install script that would, in this case, install crystalline somewhere in lsp-examples/crystal/. Would that be feasible?

Sure, I think it's possible.

Reviewable status: 0 of 4 files reviewed, 1 unresolved discussion (waiting on @anton7c3)

crystal/install.py, line 86 at r2 (raw file):

try:
    shutil.move("/tmp/crystalline", "/usr/local/bin/crystalline")

Let's not write to /usr. Let's write it to lsp-examples/crystal/bin or something like that, plus a snippet.vim like the ones that exist for other languages. That would be a correct integration with the top level install.py.
And we don't really need the bash script. Windows normally doesn't have a bash shell.

There is a problem with Crystal for Windows. So far it is hardly usable, and no Crystalline version is available at all.
Should I add some kind of stub for windows users?

Reviewable status: 0 of 4 files reviewed, 1 unresolved discussion (waiting on @anton7c3)

crystal/install.py, line 86 at r2 (raw file):
Previously, anton7c3 (Anton) wrote…
if OnWindows():
  sys.exit("Crystalline isn't supported on Windows")

Or something like that should be fine.

I've checked python script, it has an error message for all OSes that don't have Crystalline available, Windows included :)
Everything should be fine now.

Is there anything else I have missed?

I've tested the install script on my machine. Seems to be working. Merging.

@anton7c3 Once again, thanks for the pull request!


NullReferenceException if the CancellationToken already cancelled

Describe the bug
The InvokeImp returns null, if the cancellationToken already cancelled, and it causes a NullReferenceException
To Reproduce
Call the Invoke function with a CancellationToken, which is already cancelled
Expected behavior
It throws an OperationCancelledException or returns null.
Avalonia version
11.0, 11.1
OS
No response
Additional context
No response

Can you provide details about when you hit this issue? What's the use case?

I would like to execute something on the UI thread like this: Dispatcher.UIThread.Invoke(callback, priority, cancellationToken)


Cheerpx docs update review

@Honggeiry @GabrielaReyna For your review, don't take my suggestions necessarily verbatim
@AtibQur For your information, you might find my revisions interesting


Can i get a match details which i had created?

Hello i like your project and using it. I have one question i wanted to use lobby creator. Can i get lobby details which i had created. I am developing website like tournament creator. Thanks for support

Everything you need should be in the dev branch. If you have a specific question feel free to ask it in a new issue, but people probably won't be back to look here until the new year. :)
https://github.com/RJacksonm1/node-dota2/tree/dev


FOIPPA section update crashes  on Redline/OIPC layers if user edit sections on OIPC layer

Describe the bug in current situation
The following issues happening when we edit/update FOIPPA section on OIPC layer

Create a redaction on Redline layer and then go to OIPC layer and edit the section(Make a new section). then switch back to Redline layer and then again come back to OIPC layer. Then we can see two redaction boxes on OIPC layer. Updated one and the previous one

Private Zenhub Image

Also when we select one redaction, it automatically selects two. See the screenshot below

Private Zenhub Image

When we go back to Redline layer and try to edit the FOIPPA section, then default one is showing as the one we recently updated at the OIPC layer( It shouldnot be the one which is updated at OIPC layer)

Link bug to the User Story
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
Chance of Occurring (high/medium/low/very low)
Medium
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Test-marshal
Steps to Reproduce
Steps to reproduce the behavior:

Go to redaction app
Create a redaction on Redline layer.
Switch to OPIC layer and try to edit the redaction that already created on the same page in Redline layer
Switch to redline layer and back to OPIC layer then can see two redactions(Old one and new one)
Select one of the redaction, it automatically selects two(screenshot in description)
Try to edit the same redaction on Reline layer, then on FOIPPA section modal, it shows new one as default one which is updated on OIPC layer(Any changes on OIPC layer should not be reflected on Redline layer)

Actual/ observed behaviour/ results
Expected behaviour
A clear and concise description of what you expected to happen. Use the gherking language.
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

As per business (@lmullane) disable OIPC layer for 9,0 release


New timestamp format using BigDecimal and Instant

@adamsero, looking at your PR, I see that github action does not work as expected.
When error is detected, comments should be added to PR to help you to resolve it. This should like this https://github.com/sbernard31/leshan/pull/12.
I create #1314  to try to resolve it.

@sbernard31 regarding your comment, specifically

Could you not fix the last one about Check Android API Compliance ?

I'm getting a bunch of errors caused by the use of Instant class, since it's not compatible with Android API v19 as defined in build-config/lib-build-config/pom.xml:
<signature>
    <groupId>net.sf.androidscents.signature</groupId>
    <artifactId>android-api-level-19</artifactId>
    <version>4.4.2_r4</version>
</signature>

The fact that we check against API v19 released in 2013 means that we can't use any feature of Java 1.8 (from 2014), so we either have to bump the API version (I don't know what issues could arise from that) or this PR stays useless since I can't use the Instant class.

After discussion at https://github.com/eclipse/leshan/issues/1304#issuecomment-1253939281.
We decide to bump android API level from 19 to 26.
So from
<signature>
    <groupId>net.sf.androidscents.signature</groupId>
    <artifactId>android-api-level-19</artifactId>
    <version>4.4.2_r4</version>
</signature>

to something like
<signature>
    <groupId>net.sf.androidscents.signature</groupId>
    <artifactId>android-api-level-26</artifactId>
    <version>8.0.0_r2</version>
</signature>

We should be good now @sbernard31, waiting for you to bump the API version if you don't have any more issues to fix.

My question is, can we possibly be done with this PR and M9 by the end of the week? It would be really good timing if we could.

We can try.

I think we are good now ?
I let you deal with Maven / Code Check github action and upgrade the Android level API.
Then maybe you could rebase on `master and, squash all commits in one ? (then push force)
Eventually you can Android level API change in a separated commit, if you do that then this android level api change commit should be before the modification. (but again it's ok if you squash all in 1)
Last point, maybe you can refer #1304 issue in your commit header.

Should be good to go. Good to finally see a green checkmark 🙂

Thx for the contribution :pray: !


WASM bindings

Hi,
I'd like to know the requirements for this issue to be completed so I could give it a try as I intend to perform jsonschema validation in a wasm environment an this package would be very helpful in that.

   Compiling jsonschema v0.16.0
error[E0433]: failed to resolve: could not find `blocking` in `reqwest`
  --> github.com-1ecc6299db9ec823\jsonschema-0.16.0\src\resolver.rs:85:45
   |
85 |                     let response = reqwest::blocking::get(url.as_str())?;
   |                                             ^^^^^^^^ could not find `blocking` in `reqwest`

error[E0599]: no method named `to_file_path` found for reference `&Url` in the current scope
  --> github.com-1ecc6299db9ec823\jsonschema-0.16.0\src\resolver.rs:95:43
   |
95 |                     if let Ok(path) = url.to_file_path() {
   |                                           ^^^^^^^^^^^^ method not found in `&Url`

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
error: could not compile `jsonschema` due to 2 previous errors

It would be really powerful to have your json-schema validator available in wasm!

@Stranger6667 It can compile to wasm if you disable the default-feature and only enable structopt in the Cargo.toml
jsonschema = { version = "=0.15.0", default-features = false, features = ["structopt"]}

pure wasm doesn't support IO natively so if we want to add support for the IO ref-resolver then we need to provide custom bindings for that or use WASI if runtime supports that.

I was able to compile it down to the wasm module with the above configuration, I didn't need to parse IO refs so It worked for me.

Closing in favor of #568 Right now jsonschema runs tests on wasm32-wasip1 in CI, and provides some error messages specifically for wasm + there is a docs section about it.
Later on, I'll add JS bindings to use it in a browser (and a demo website!), but that is a separate thing and I'll create a new issue for it.

"+ there is a docs section about it."

Search for "wasm" in  https://docs.rs/jsonschema/latest/jsonschema/ returned nothing and also grep in this source did not anything looking like docs for compiling to WASM

Hey! I haven’t release it yet, you can check it here now - https://github.com/Stranger6667/jsonschema-rs/blob/6b934d55553af4b34340be8e6604fc87c8d70e4b/crates/jsonschema/src/lib.rs#L451
let me know if the section is not enough, I’m happy to expand it


Bug - API Routes do not handle query parameters.

The merge of #99 and #117 has given us support for API Routes in NextJS 🎉
However, I have noticed a bug when sending query parameters.
Here is a copy of my endpoint (apologies for the poor naming conventions but this is a WIP). It simply takes a relative path request and proxies to the fully qualified path on the server. Whether or not this is a best practice at this point is 🤷♂
// pages/api/next/[path]/[endpoint].ts

import { NextApiRequest, NextApiResponse } from 'next';
import request from 'axios';
import qs from 'query-string';

export default async (req: NextApiRequest, res: NextApiResponse) => {
  const {
    query: { path, endpoint, ...rest },
  } = req;

  const queryString = rest ? `?${qs.stringify(rest)}` : '';
  const url = `${process.env.HOST}/${path}/${endpoint}${queryString}`;

  try {
    const response = await request.get(url);
    res.status(200).json(response.data);
  } catch (error) {
    res.status(500).json({ error: error.message});
  }
};

And I call it with this endpoint:
/api/next/classic-api/news-listing.asp?catId=26&skip=9&take=8

When I run this locally, the NextJS convention is that

path resolves to classic-api
endpoint resolves to news-listing.asp
queryString resolves to ?catId=26&skip=9&take=8

When I deploy this to AWS, API Gateway resolves to this

path resolves to classic-api
endpoint resolves to news-listing.asp?catId=26&skip=9&take=8&path=classic-api&endpoint=news-listing.asp
queryString resolves to ?catId=26&skip=9&take=8

The problem seems to be how endpoint is being resolved in AWS.
Instead of forwarding on my request to
https://www.mydomain.com/classic-api/news-listing.asp?catId=26&skip=9&take=8

it instead forwards it on to
https://www.mydomain.com/classic-api/news-listing.asp?catId=26&skip=9&take=8&path=classic-api&endpoint=news-listing.asp?catId=26&skip=9&take=8

If anyone has any ideas of where to get started it would be much appreciated. Ultimately I want the plugin to behave in the same way as NextJS.

@danielcondemarin - any chance this could be something within next-aws-lambda?
I see there's some query string manipulation in compatLayer.js
  if (hasQueryString) {
    req.url += `?${qs}`;
  }

https://github.com/danielcondemarin/serverless-nextjs-plugin/blob/master/packages/next-aws-lambda/lib/compatLayer.js#L38

I encountered this yesterday as well, there's actually a bug with nextjs which incorrectly matches on the last path segment. I'm working on a fix here https://github.com/Deadleg/next.js/commit/5bdcd698bd6aaf1ac1e0d53fd50b94636e17c458 but the long and short of it there is a regex in  packages/next-server/lib/router/utils/route-regex.ts which matches on every non / character, which in turn matches on question marks and everything after.
Note that if you run next dev then it doesn't reproduce, but if you use next build and next start or serverless offline then you can reproduce it since the regex is only applied to the generated serverless functions.
You can apply the below patch which works around the issue, but breaks custom paths. I think if nextjs is fixed then we don't need to do anything in this project.
diff

diff --git a/packages/next-aws-lambda/lib/compatLayer.js b/packages/next-aws-lambda/lib/compatLayer.js
index 7d19fa6..213c7aa 100644
--- a/packages/next-aws-lambda/lib/compatLayer.js
+++ b/packages/next-aws-lambda/lib/compatLayer.js
@@ -10,8 +10,9 @@ const reqResMapper = (event, callback) => {
     multiValueHeaders: {}
   };

+
   const req = new Stream.Readable();
-  req.url = (event.requestContext.path || event.path || "").replace(
+  req.url = (event.path || "").replace(
     new RegExp("^/" + event.requestContext.stage),
     ""
   );
@@ -22,15 +23,15 @@ const reqResMapper = (event, callback) => {
     qs += queryString.stringify(event.multiValueQueryStringParameters);
   }

-  if (event.pathParameters) {
-    const pathParametersQs = queryString.stringify(event.pathParameters);
-
-    if (qs.length > 0) {
-      qs += `&${pathParametersQs}`;
-    } else {
-      qs += pathParametersQs;
-    }
-  }
+//  if (event.pathParameters) {
+//    const pathParametersQs = queryString.stringify(event.pathParameters);
+//
+//    if (qs.length > 0) {
+//      qs += `&${pathParametersQs}`;
+//    } else {
+//      qs += pathParametersQs;
+//    }
+//  }

   const hasQueryString = qs.length > 0;

You can work around it by not using a dynamic file name e.g. change pages/api/next/[path]/[endpoint].ts -> pages/api/next/[path][endpoint]/index.ts.

Ignore the work around, need to use the patch. Created pull request here https://github.com/zeit/next.js/pull/8386

Amazing detail @Deadleg - thanks for raising that PR!

Next.js 9.0.4 has just been released, from my testing APIs are working correctly.

I've updated to Next 9.0.4 and I keep getting a 502 from all endpoints.
This one is from my index page at / but all Next pages have the same behavior.
Syntax error in module 'sls-next-build/index': SyntaxError
} catch {
^

SyntaxError: Unexpected token {
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:616:28)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/var/task/sls-next-build/index.js:2:16)

That doesn't look right, sls-next-build/index should have the contents of lambdaHandlerWithFactory  in https://github.com/danielcondemarin/serverless-nextjs-plugin/blob/7c25b305739b134aff53c83007868022f46adaa8/packages/serverless-nextjs-plugin/lib/getFactoryHandlerCode.js. What's in that file on your lambda?

It is...

  const page = require("./index.original.js");
  const handlerFactory = require("next-aws-lambda");

  module.exports.render = (event, context, callback) => {
    const handler = handlerFactory(page);
    handler(event, context, callback);
  };

Looks like a new feature in ES10 called optional catch binding is causing the syntax error. Upgrading node may fix the issue, I'm building and running with the latest available version on Lambda.

Good catch! I was running Node 8 in AWS so I've bumped it to Node 10 in my serverless.yml and I've got a website again. :)
provider:
  name: aws
  runtime: nodejs8.10

provider:
  name: aws
  runtime: nodejs10.x


waffle.io Badge

Merge this to receive a badge indicating the number of issues in the ready column on your waffle.io board at https://waffle.io/mattstauffer/savemyproposals
This was requested by a real person (user mattstauffer) on waffle.io, we're not trying to spam you.

This issue was moved to tightenco/symposium#32


BNNeck initialization

why there is no shift in your BNNeck initialization?
'self.bottleneck.bias.requires_grad_(False)  # no shift'

Our original intention is to hope that the features can be distributed Gaussianly in the hyper-sphere. But some more experiments show that bias does not influence the performance a lot.

Thanks!


Too short -t (timeout) can lead to false positives.

@funilrys see - https://github.com/mitchellkrogza/The-Big-List-of-Hacked-Malware-Web-Sites/commit/e0a15f6d6b9210da4c9de71ed9965a2b3e8e4652

@funilrys I am not 100% convinced timeout is the cause of this. I think some registries are limiting lookups so on one run I get a positive hit "active" and then then later in the day on same domain I get a negative hit "inactive"

👍  ok gotya. Actually this just proves how accurate funceble and how my brain was working to test why I got one INACTIVE after it was previously ACTIVE. That's because the site http://matchgallery.homeandgardeningarticles.co.uk/6514626a35adfb3fa6f1d3f3c0a10fcf/login.php has been pulled offline 👍  so ...... funceble RULES !!!!

So this is not an issue anymore :smile_cat:
Closing.

100% ..... funceble is doing exactly what it was designed to do .... find dead domains and boy oh boy you have done some amazing work on this.


EN to JP support

Would it be possible to take the JP text and use the app to insert it into the english client? I'd rather read the japanese version of recent chapters but don't have time or the willpower to make a JP account

I don't think there is high enough demand for this to make it worth the time to implement, as it's not trivial to do so.


DE revoked certificates

Expiration date is end of April.

the DCC's appear as VAILD and are not recognised as revoked. Can you please double-check?

Absolutely right, sorry. I revoked on TST. Now its also on ACC.


Test execution failure on Linux

Description
I have a .net core project with some unit tests. The unit test framework fails on Linux.
Steps to reproduce
Given this project file:
<Project Sdk="Microsoft.NET.Sdk">
	<Import Project="..\company.globals.props" />
	<PropertyGroup>
		<TargetFramework>netcoreapp3.1</TargetFramework>
		<OutputPath>$(BuildDir)</OutputPath>
		<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
	</PropertyGroup>

	<ItemGroup>
		<PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.5.0" />
		<PackageReference Include="MSTest.TestAdapter" Version="2.1.0" />
		<PackageReference Include="MSTest.TestFramework" Version="2.1.0" />
		<PackageReference Include="coverlet.collector" Version="1.2.0" />
	</ItemGroup>
</Project>

When run this on Red Hat Enterprise Linux 8.2, from the command line using .net core. I get a runtime exception and the test execution fails.
Execute the following command from the command line:
dotnet test ./foo.csproj -p:Configuration=Debug
Expected behavior
This runs absolutely fine on windows:
Test run for C:\Users\me\source\repos\foo\builds\bin\x64\Debug\netcoreapp3.1\foo.dll(.NETCoreApp,Version=v3.1)
Microsoft (R) Test Execution Command Line Tool Version 16.6.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

A total of 1 test files matched the specified pattern.

Test Run Successful.
Total tests: 28
     Passed: 28
 Total time: 4.6982 Seconds

Actual behavior
Test run for /home/admin/code/foo/builds/bin/x64/Debug/netcoreapp3.1/foo.dll(.NETCoreApp,Version=v3.1)
Microsoft (R) Test Execution Command Line Tool Version 16.3.0-dev+55e7e45431c9c05656c999b902686e7402664573
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

A total of 1 test files matched the specified pattern.

An exception occurred while invoking executor 'executor://mstestadapter/v2': Protocol error

Test Run Failed.

Environment
On Linux I have:
root (/home/admin/code/foo) $ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.1.105
 Commit:    99c9707ea8

Runtime Environment:
 OS Name:     rhel
 OS Version:  8
 OS Platform: Linux
 RID:         rhel.8-x64
 Base Path:   /usr/lib64/dotnet/sdk/3.1.105/

Host (useful for support):
  Version: 3.1.5
  Commit:  65cd789777

.NET Core SDKs installed:
  3.1.105 [/usr/lib64/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.1.5 [/usr/lib64/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.5 [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]
...

On Windows (v10) I have:
.NET Core SDK (reflecting any global.json):
 Version:   3.1.301
 Commit:    7feb845744

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18362
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.1.301\

Host (useful for support):
  Version: 3.1.5
  Commit:  65cd789777

.NET Core SDKs installed:
  2.1.4 [C:\Program Files\dotnet\sdk]
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.400 [C:\Program Files\dotnet\sdk]
  2.1.602 [C:\Program Files\dotnet\sdk]
  2.1.700 [C:\Program Files\dotnet\sdk]
  3.1.201 [C:\Program Files\dotnet\sdk]
  3.1.301 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.19 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Operating system, Build version of vstest.console, Package version of MSTest
framework and adapter

The thing is, I have a few other projects in my particular project, and all of them fail in Linux with the same error:
An exception occurred while invoking executor 'executor://mstestadapter/v2': Protocol error

Install Red Hat 8, and the same dotnet SDK is you do, and it works just fine. Are you able to repro this on multiple machines?

I'm seeing this same issue with Vagrant CentOS. dotnet version is 3.1.401.

This appears to be some kind of directory issue.
By using the -r command if I write my tests results to  /home/vagrant/repos/my-micro/My.Micro.Test/test-results it fails.
Writing to /home/vagrant/test/test-results  succeeds.

This should be a TestHost related error, which version of Microsoft.NET.Test.SDK is your project using? Currently there is 16.7.1 and 16.8.0-preview.

16.7.1 and 16.8.0-preview both have the same error outcome.
I am also using Microsoft (R) Test Execution Command Line Tool Version 16.7.0.
In addition to Protocol Error I'm also getting another error message:
An exception occurred while invoking executor 'executor://mstestadapter/v2': Protocol error
Results File: /home/vagrant/repos/my-micro/My.Micro.Test/test-results/_localhost_2020-08-27_13_16_38.trx

Test Run Failed.
Additionally, path to test adapters can be specified using /TestAdapterPath command. Example  /TestAdapterPath:<pathToCustomAdapters>.
/usr/share/dotnet/sdk/3.1.401/Microsoft.TestPlatform.targets(32,5): error MSB4181: The "Microsoft.TestPlatform.Build.Tasks.VSTestTask" task returned false but did not log an error. [csproj path redacted]

could you run it with --diag:logs/log.txt and share the log files that are written into logs directory please?

Attached are the requested logs files.
logs.zip

@btull89 Thanks, the log says it is caused by Protocol error, probably nothing we can do about that:
TpTrace Error: 0 : 4460, 4, 2020/09/29, 14:59:41.481,<PHONE_NUMBER>99, testhost.dll, BaseRunTests.RunTestInternalWithExecutors:
  An exception occurred while invoking executor executor://mstestadapter/v2.
  System.IO.IOException: Protocol error
   at System.IO.FileSystem.CreateDirectory(String fullPath)
   at System.IO.Directory.CreateDirectory(String path)
   at Microsoft.VisualStudio.TestPlatform.MSTestAdapter.PlatformServices.Utilities.FileUtility.CreateDirectoryIfNotExists(String directory)
   at Microsoft.VisualStudio.TestPlatform.MSTestAdapter.PlatformServices.Utilities.DeploymentUtilityBase.CreateDeploymentDirectories(IRunContext runContext)
   at Microsoft.VisualStudio.TestPlatform.MSTestAdapter.PlatformServices.TestDeployment.Deploy(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle)
   at Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter.Execution.TestExecutionManager.RunTests(IEnumerable`1 sources, IRunContext runContext, IFrameworkHandle frameworkHandle, TestRunCancellationToken cancellationToken)
   at Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter.MSTestExecutor.RunTests(IEnumerable`1 sources, IRunContext runContext, IFrameworkHandle frameworkHandle)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Execution.RunTestsWithSources.InvokeExecutor(LazyExtension`2 executor, Tuple`2 executorUriExtensionTuple, RunContext runContext, IFrameworkHandle frameworkHandle)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Execution.BaseRunTests.RunTestInternalWithExecutors(IEnumerable`1 executorUriExtensionMap, Int64 totalTests).
TpTrace Error: 0 : 4460, 4, 2020/09/29, 14:59:41.482,<PHONE_NUMBER>49, testhost.dll, An exception occurred while invoking executor 'executor://mstestadapter/v2': Protocol error

Sorry to not have any specific solution, but searching for this turns up with a whole range of possible causes, such as no space on the disk, or missing permissions when mounting a volume in VirtualBox https://www.google.com/search?q=cannot+create+directory+protocol+error+dotnet

@danmincu If you are able to reproduce the issue, could you please let us know if the fix in the related PR fixed this issue for you? Thanks

In my case the fix was to run the tests into a Linux folder and to copy the *.trx file in the folder that was mounted on Windows avoiding the cross OS folder name creation problem. However, his commit should fix it https://github.com/microsoft/testfx/pull/1119/files I'll be able to test it soon after I upgrade the testfx framework.

Thank you! I will keep this one open until you confirm it's good.

Hey @danmincu. I don't know if you had time to confirm things are good now?
I'll move forward and close this ticket. If you have a repro of something that still fails, please either ping here or create a new issue.


Update internal timeout to have clearer error message

instead for a timeout from the CI, there will be the list o fall tests
that are failing

failign tests are now reported instead ogf a timeout:
https://app.circleci.com/pipelines/github/camel-tooling/camel-language-server/164/workflows/901bc055-2329-44d5-af76-5c8b6ea3798d/jobs/592

failign tests are now reported instead ogf a timeout:
https://app.circleci.com/pipelines/github/camel-tooling/camel-language-server/164/workflows/901bc055-2329-44d5-af76-5c8b6ea3798d/jobs/592


Don't scroll to top if link was opened in new tab

If user cmd+clicks (or ctrl+clicks) a link in the sidebar, the linked page opens in a new page, and the current tab should not scroll to the top.

@codeclown Make sense, if you don't mind, I'd like to push some end to end tests in this pull request to prevent potential regression in the future.

@codeclown Make sense, if you don't mind, I'd like to push some end to end tests in this pull request to prevent potential regression in the future.

Go for it! Thanks!

On 15. Jan 2021, at 6.29, Sam Chen<EMAIL_ADDRESS>wrote:

@codeclown Make sense, if you don't mind, I'd like to push some end to end tests in this pull request to prevent potential regression in the future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Go for it! Thanks!

On 15. Jan 2021, at 6.29, Sam Chen<EMAIL_ADDRESS>wrote:

@codeclown Make sense, if you don't mind, I'd like to push some end to end tests in this pull request to prevent potential regression in the future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Clarify no-shadowed-variable doc (#4306)

PR checklist

[v] Addresses an existing issue: #4306
[ ] New feature, bugfix, or enhancement

[ ] Includes tests

[v] Documentation update

Overview of change:
Clarify the rationale behind no-shadowed-variable and add some references.
Is there anything you'd like reviewers to focus on?
I couldn't find a way to run documentation locally, so I am not too sure how it would look like on Jekyll. It would be great to have a documentation on running docs locally.
CHANGELOG.md entry:
N/A

Thanks for your interest in palantir/tslint, @aprilrd! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

Thank you for the quick review! 👍


20.3 edit template issue

Summary
  **** test_convert_devices_to_cli_mode ****
[FAIL] "TypeError in test case "test_convert_devices_to_cli_mode" at subtest "device_to_cli_mode"[69]: __init__() missing 2 required positio
nal arguments: 'resource_group' and 'draft_mode'"

Logs and external information
fails with recent code....
Using vmngclient version 0.12.2     http://vip-oldregressdb.cisco.com:8080/regressdb/2503246/
last pass log...
Using vmngclient version 0.9.2.    http://vip-oldregressdb.cisco.com:8080/regressdb/2363360/
Reproduction script
runsuite cluster -n tb -o -b 20.3 -a 753 -f cluster -nu -q
On what platform(s) does it occur?
Not Applicable
Issue Severity
Medium: There is a workaround

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/issues/333


HTTP Basic Auth

Hi,
is it possible to crawl secured pages which are secured by an http basic auth?
This could be a nice feature to be implemented by your crawler.
Thanks

It is already implemented

This issue can be closed


Change FpsComponent as optional parameter to FpsTextComponent

What could be improved
Add optional parameter FpsComponent to FpsTextComponent.
It could reuse the FpsComponent used by outside of the TextComponent.
Why should this be improved
Currently, the FpsTextComponent is creating FpsComponent inside of the constructor.
https://github.com/flame-engine/flame/blob/c175617714e2f15f4379ed8ea412c7cb8bfa1842/packages/flame/lib/src/components/fps_text_component.dart#L17
In some games, FpsComponent is used not only for printing on the screen but also for other functions.
So it should create multiple FpsComponent if the game is using FpsTextComponent and the FpsComponent in the other place.
Any risks?

No
More information

Are you interested in working on a PR for this? Yes

Sounds like a quite specific usecase, but also don't see the harm in adding it as an optional argument.
Should I assign you to the issue?

Sounds like a quite specific usecase

I agree that it's a specific use case.
It's a little different topic but let me introduce my use case.
My use case is interpolating the position of the component which is followed by a camera.
The camera's following behavior is not interpolating because its following component position is assumed as interpolated.
But the dt reported by the update method can be inconsistent if the game is very complicated and large(ex, has a large map).
As dt based on flutter ticker, it could be "jump" value(ex, 0.016 => 0.033).
Inconsistency of dt and jumping a little is OK (like from 0.016 to 0.017~0.018) but jumping twice its value can cause the camera to be literally "shaking".
So I decided to use 1 / FpsComponent.fps instead of dt as it is can report interpolated values and it works perfectly.
This could be a great workaround if someone suffers from the camera shaking.

Should I assign you to the issue?

Yes, I would like to do this.

So I decided to use 1 / FpsComponent.fps instead of dt as it is can report interpolated values and it works perfectly.

This sounds very strange, sounds like we have a bug with how the dt values are reported then.
But FpsComponent.fps is also using dt to calculate the fps, so I really don't get how it can help to use fps. :sweat_smile:

As you can see here, its fps is from an average of 60 frames(by default but I am using 180 as a windowSize)
https://github.com/flame-engine/flame/blob/b69e8d85c77346081d1fc5a2ee5cbf9c204a9edf/packages/flame/lib/src/components/fps_component.dart#L34-L36

Ah, right, that makes sense. I still think it is a bit strange to use the FpcComponent the get a smooth movement here, but if it works, it works. :)
I'll assign you to the issue.

Right, It is weird 🤣 but I don't have any other great idea to get the smooth movement right now...
If I fix the dt as ds=0.016, the low-end devices which have low fps get a lower speed compared with others.

On second thought, this is not enhancement but weakening.
The FpsTextComponent is usually used for debug mode so it does not strongly need to be reused.
And if the optional parameter is exposed to the user API, they could be confused about it at glance.

Closing the issue and reopen it if you don't agree.


chore(release): 0.10.0

Version bump in package.json and package-lock.json for release 0.10.0

:tada: This PR is included in version 0.11.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


If filePickerBeforeShow returns false or an empty table, do nothing

This would be similar to the behavior of onOpenFile, allowing users to handle the event themselves.

@b0o Absolutely right, it's constistent with the other hook now. Thanks!


Bump version to 1.6.3

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


Bug in README.rst

Entering iot-health-cli as command line under path ~/iot-health$ returns "bash: iot-health-cli: command not found"

Fixed at v0.0.4.


Plugin lifecycle and Chain lifecycle #5475

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report
Attention: Patch coverage is 90.47619% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 61.17%.  Consider uploading reports for the commit 4f18036 to get more accurate results

Files
Patch %
Lines

...dmin/controller/ConfigsExportImportController.java
71.42%
0 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5491      +/-   ##
============================================
- Coverage     61.20%   61.17%   -0.04%
+ Complexity     8853     8850       -3
============================================
  Files          1272     1272
  Lines         39506    39515       +9
  Branches       3786     3783       -3
============================================
- Hits          24181    24173       -8
- Misses        13133    13145      +12
- Partials       2192     2197       +5

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


BAU: Change progress endpoint to post

Start posting data as a json body as opposed to query params

Fixes: https://sentry.io/organizations/funding-service-design-team-dl/issues/3850987122/?referrer=slack

Just a note about adding a TODO and tech-debt ticket for post

FYI @harryyo created https://digital.dclg.gov.uk/jira/browse/FS-2161 for addressing this


Performance Test: Rollup & RD Batch Jobs

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

We decided to use a plan-based rather than branch-based strategy.
So I will make a new plan which calls a flow called test_rd_performance_LDV  on your master branch. Please create that flow and merge to master.

Here is how it will work.
On Master, MetaCI will run:

"Performance Tests - LDV" Plan which will run the test_performance_LDV flow -- to do BDI tests.

"Performance Tests - Recurring Donations" Plan which will run the test_rd_performance_LDV flow to do RD2 tests

"Performance Tests - Rollups" Plan which will run the test_rollup_performance_LDV flow to do Rollups Tests tests

This was moved to feature/performance-tests__customizable-rolups


experimental: safe parse NERs from list of dictionaries

Issue: #24493, by default some LLM generations return output + input promt. In this case after json extraction structure can be in format: [[],[], {usefull_data}, ...].
I created new fuction to safe parse unpredictable outputs

cc @tomasonjo
also pr is stil failing lint. to format and lint locally run
cd libs/experimental
poetry install --with lint,typing
make format
make lint

Do I  undestand correctly you just ignore results if they are incorrect? Nothing else is done in this PR?

Do I undestand correctly you just ignore results if they are incorrect? Nothing else is done in this PR?
Avoid errors if data not parsed correctly

I want to propagate errors, maybe we need special parsing for hf models
where we remove input prompt first
V ned., 28. jul. 2024, 12:25 je oseba Otniel @.***>
napisala:

Do I undestand correctly you just ignore results if they are incorrect?
Nothing else is done in this PR?
Avoid errors if data not parsed correctly
—
Reply to this email directly, view it on GitHub
https://github.com/langchain-ai/langchain/pull/24566#issuecomment-2254464703,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEYGGTK3OALPEWNFYQ5TPPTZOTBJ3AVCNFSM6AAAAABLK4WIBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGQ3DINZQGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

cc @tomasonjo
also pr is stil failing lint. to format and lint locally run
cd libs/experimental
poetry install --with lint,typing
make format
make lint

is there easy way to do it on windows? ;)


Prevent ImapConnection reuse

ImapConnection should not be reused after is was closed. So open() now throws an exception when it is called after close() has been called.
This should allow us to find out faster what caused issues like #1297.

Nice. I'll pull the branch this evening and test it :)


[Feature]: Build the Projects Page

Is your feature request related to a problem? Please describe.

We have a dedicated projects page. In this we wish to showcase the projects made by our community members and display details such as:
Project Name
Deployment link
Github link etc
Someone needs to create the template for this page and insert dummy cards, which can be later updated with actual projects. Please ensure the color and theme matches rest of the website
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

please assign this to me.

@Gaurav-Borah sure go ahead. feel free to tag in case of doubts

@pradeeptosarkar I am interested in working on this issue, I will be doing this today itself.
I will add:

Project cards with dummy images and data.
Filter and search functionality that will be beneficial in improving the user experience.

If I am assigned to this, I would start the implementation immediately. I request you to kindly assign.

@iamrishiksahu it's already assigned to @Gaurav-Borah

If I don't deliver this within 24 hours feel free to take this from me @iamrishiksahu.

resolved


kconfig: cpp: Have LIB_CPLUSPLUS depend on NEWLIB_LIBC

The C++ STD library is not compatible with the minimal C library. To
ensure that users do not accidentally enable LIB_CPLUSPLUS while also
enabling a minimal libc library we add a dependency in Kconfig.
Also, use depends instead of select between EXCEPTIONS, RTTI, and
LIB_CPLUSPLUS as use of select is discouraged in this situation.

@galak can this be consider a bug-fix that needs to go to 2.0?

@ioannisg : IMHO this should not be applied in the stabilization period (because it makes things more strict and therefore can destabilize).

@ioannisg : IMHO this should not be applied in the stabilization period (because it makes things more strict and therefore can destabilize).

I am ok with postponing this to 2.1, as long as there is no bug-report related to the fix (then we should merge that now)

Sure, assuming #18315 goes in before this PR.

Blocked by #18315 . Will rebase this after 18315 is merged.

Rebased

Needs rebasing.

Rebased

@galak : This is ready to merge


Upgraded dear imgui and ImGuizmo to the latest version

Upgraded ImGui and ImGuizmo to their lattest version on GitHub.
Fixed the changes on the implementation on "btgui" (some function signature now permit you to pass a `void*  "user context" to functions)
The Gizmo feels a little bit nicer to use in the latest version
Signed-off-by: Arthur Brainville (Ybalrid<EMAIL_ADDRESS>

(I will send you theses changes for NanoSG too)

Mh, don't merge it just yet, there's a little bug I need to squash

This is good to go now

Cool! Merged!


use_raf_fn trying to access disposed signal?

Hi, thanks for this library. I can't seem to get use_raf_fn working correctly, however.
panicked at /home/francis/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos-use-0.10.10/src/use_raf_fn.rs:92:27:
Attempted to get a signal after it was disposed.
signal created here: /home/francis/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos-use-0.10.10/src/use_raf_fn.rs:55:35
warning happened here: /home/francis/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos-use-0.10.10/src/use_raf_fn.rs:92:27

Looking at the referenced lines it's because in the loop_fn this signal is being accessed:
            if !is_active.get_untracked() {
                return;
            }

but I suppose it's after the hosting component goes away, and the RAF function is called once more afterwards.
I thought the lines:
    let pause = move || {
        set_active.set(false);

        let handle = raf_handle.get();
        if let Some(handle) = handle {
            let _ = window().cancel_animation_frame(handle);
        }
        raf_handle.set(None);
    };
    on_cleanup(pause.clone());

would stop the handler in time but I guess not? Or perhaps I'm overlooking something?
thank you.

Thanks for the kind words.
You're definitely on the right track. The piece of code you're referencing is meant to do that but obiously it doesn't. Let me fix it...

amazing, thank you!


Fix regression in CORS header validation

These are not literally headers, they are values that end up inside
cors headers. These can be <header name> || *; we were missing the
star case.
See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Expose-Headers
See https://github.com/istio/istio/pull/51343#issuecomment-2266705080

In response to a cherrypick label: new pull request created: #52626


As a user, I want to have access to a resource list for each assignment.

#126 addresses this issue.


bounded inverse class weighting

In the Towards End-to-End Lane Detection: an Instance Segmentation Approach paper there is mentioned, that to balance the binary training a bounded inverse class weighting is used.
Did you also used that technique?

@gismo07 That technique has not been used in this implementation yet I will release the complete version in the future.

Ok thats nice. Thank you!


ask hewlett for portfolio of open policy resources?

this would be their guidance document for program officers
text for grantee agreements
etc.

diane did it


App Crashes unexpectedly.

Describe the bug
Hy I'm using nativewind with react-native-cli, wix/react-native-navigation. and app crashing unexpectedly and getting the error.
Expected behavior
I'm using nativewind with react-native-cli, wix/react-native-navigation. and app crashing unexpectedly and getting the error.
error: index.js: [BABEL] C:\Users\CYRUS\Documents\work\ux-labs\MyApp\index.js: Unexpected token ',' (While processing: "C:\\Users\\CYRUS\\Documents\\work\\ux-labs\\MyApp\\node_modules\\nativewind\\babel.js")

Screenshots

You are getting this error because babel is having problems transforming one of your files. But without access to your code, I cannot tell which file or why it causes an error.
I"m going to close this issue as I cannot assist further but if your still having problems please create a new issue with a link to your repo so I can debug the problem


About pose estimation results in legacy solutions and new APIs

I am working on pose estimation using video files as input. We are comparing the output results of the legacy solution (mediapipe.solutions.pose.Pose) and the new API (mediapipe.tasks.vision.PoseLandmarker).
When using the new API, the changes in the coordinates obtained from the results are larger than with the legacy solution, and it looks strange when drawing landmarks on the image.
OS: Windows10
mediapipe version: 0.10.0
Solution: Pose
Language: Python
Is there a way to use the new API to get better results (same or better than legacy solutions) when performing inference with video files as input?
Below is the code to reproduce the problem.
Comparisons were made by running legacy_solution() and new_api().
def draw(img, landmarks):
    h,w,_ = img.shape
    for ldm in landmarks:
        x = int(ldm.x * w)
        y = int(ldm.y * h)
        cv2.circle(img, (x,y), 3, (255,0,0), thickness=-1)
    return img

# Load the input video.
video_file = "path_to_video_file"
cap = cv2.VideoCapture(video_file)

def legacy_solution():
    mp_pose = mp.solutions.pose
    with mp_pose.Pose(min_detection_confidence=0.5,
                      min_tracking_confidence=0.5,
                      static_image_mode = False,
                      model_complexity=1) as pose:
        while True:
            ret, frame = cap.read()
            if not ret:
                break
            image = cv2.cvtColor(frame, cv2.COLOR_BGR2RGB)
            image.flags.writeable = False
            results = pose.process(image)
            image.flags.writeable = True
            image = cv2.cvtColor(image, cv2.COLOR_RGB2BGR)
            image = draw(image, results.pose_landmarks.landmark)
            cv2.imshow("image", image)

            if cv2.waitKey(1) & 0xFF == ord('q'):
                break
    cap.release()
    cv2.destroyAllWindows()

def new_api():
    # Create an PoseLandmarker object.
    base_options = python.BaseOptions(
        model_asset_path='pose_landmarker_full.task')
    PoseLandmarker = mp.tasks.vision.PoseLandmarker
    VisionRunningMode = mp.tasks.vision.RunningMode
    options = vision.PoseLandmarkerOptions(
        base_options=base_options,
        output_segmentation_masks=False,
        running_mode=VisionRunningMode.VIDEO)

    with PoseLandmarker.create_from_options(options) as detector:
        while True:
            ret, img = cap.read()
            timestamp = int(cap.get(cv2.CAP_PROP_POS_MSEC))
            if not ret:
                break
            mp_image = mp.Image(image_format=mp.ImageFormat.SRGB,
                                data=img)
            detection_result = detector.detect_for_video(mp_image, timestamp)
            annotated_image = draw(mp_image.numpy_view(),
                                    detection_result.pose_landmarks[0])
            cv2.imshow("image", annotated_image)

            if cv2.waitKey(1) & 0xFF == ord('q'):
                break
    cap.release()
    cv2.destroyAllWindows()

Hi @gitshunsuke119,
Currently, we cannot do much about this issue when comparing the legacy and new task APIs. Our priority is to continually enhance our Task APIs, as we are no longer maintaining the legacy version.
Thank you!!


Automatic testing upon pull request

One can set up a system where all tests are run automatically whenever one tries to push to the master branch. GitHub only supports CPUs, there is a tool called GitLabRunner which needs to be set up at Bielefeld. Have to make sure we can use GPUs. We have to make sure there are no security issues.
Since someone has to look who pulls and who looks at the code to make sure the style is correct, at least for the time being, this someone can run the tests.
A probably helpful site/tool for this: https://gitlab.com/ecp-ci/jacamar-ci

I moved this description to #7


Cherry pick Doctest for PrimitiveArray using from_iter_values. to active_release

Automatic cherry-pick of 38e5d22

Originally appeared in https://github.com/apache/arrow-rs/pull/694: Doctest for PrimitiveArray using from_iter_values.

Codecov Report

Merging #700 (0d80543) into active_release (3c0a8bd) will increase coverage by 0.00%.
The diff coverage is n/a.

:exclamation: Current head 0d80543 differs from pull request most recent head c9dd2d3. Consider uploading reports for the commit c9dd2d3 to get more accurate results

@@               Coverage Diff               @@
##           active_release     #700   +/-   ##
===============================================
  Coverage           82.39%   82.39%
===============================================
  Files                 167      167
  Lines               46568    46568
===============================================
+ Hits                38371    38372    +1
+ Misses               8197     8196    -1

Impacted Files
Coverage Δ

arrow/src/array/array_primitive.rs
94.38% <ø> (ø)

parquet/src/encodings/encoding.rs
94.67% <0.00%> (+0.19%)
:arrow_up:

Continue to review full report at Codecov.

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


⚠ GLDDNS Server (ns2.glddns.com) has degraded performance

In 6a9dd4d, GLDDNS Server (ns2.glddns.com) (ns2.glddns.com) experienced degraded performance:

HTTP code: 200
Response time: 490 ms

Resolved: GLDDNS Server (ns2.glddns.com) performance has improved in 56daf0d after 6 minutes.


service principal added for acs provisioning k8s

kubernetes orchestration was broken because a valid service principal object was missing.

@pothedar thanks for addressing this. One question, why did you add extra fields to azurermconfig.json.tmpl? Why not use the existing appId and appSecret properties?

@gbowerman sorry, i totally missed that. Fixed that, updated Read Me and the test as well.

@pothedar do app_id, app_secret have any purpose if you're creating acs with another orchestrator like DCOS? If not, it may be better if they are optional parameters at the end, e.g.
def create_container_service(access_token, subscription_id, resource_group, service_name,
agent_count, agent_vm_size, agent_dns, master_dns, admin_user, public_key, location,
master_count=3, orchestrator='DCOS', app_id=None, app_secret=None):
....
if app_secret is not None:
sp_profile['Secret'] = app_secret
etc..
what do you think?

@gbowerman agreed.

azurerm-0.7.24 uploaded to pypi. Thanks @pothedar


Pending changes exported from your codespace

yash

👷 Deploy Preview for yash-gadhvi processing.

Name
Link

🔨 Latest commit
ab118bc2698979c38a40f7a08ac4d3b3e54682c9

🔍 Latest deploy log
https://app.netlify.com/sites/yash-gadhvi/deploys/644a5bc7e0f33c0008bec315


Fixed #35502 -- Changed directory name of mysite in tutorial.

35502
There was a ticket #22042 that has already been closed, but maybe this solution will be beneficial.
ticket-35502
Branch description
We have two mysite directories, and we often see users confused by that. If we rename the mysite directory, the confusion would be alleviated.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[ ] I have checked the "Has patch" ticket flag in the Trac system.
[ ] I have added or updated relevant tests.
[ ] I have added or updated relevant docs, including release notes if applicable.
[ ] I have attached screenshots in both light and dark modes for any UI changes.

I think this is a good solution. My two questions:

are we certain that the rest of the tutorial, or even other parts of the documentation, don't refer to e.g. "the outer mysite directory"?
suggest djangotutorial for the outer directory and mysite for inner

@petmetic Would you have some availability to fetch the latest changes I pushed and applied/answer to the feedback that Sarah posted?


Fixed issue with parted tables and NOT on WHERE clause

When executing a query on a partitioned table with a WHERE clause, we try to find out which partitions should be included in the execution plan (collect data from their shards). To achieve this, we break down the query to parts based on the PARTITIONED BY column and the available partitions of the table, and for each one of the parts we replace all references (table columns) with the value TRUE or NULL (pretending that there are indeed values for that column which satisfy the expression)
When NOT predicate is involved there though, we need to just skip it, since a NOT TRUE will lead to false and therefore filter out whole partitions. It's also important that the NOT is skipped and whatever it wraps underneath is returned, only if that wrapped expression can be normalized to a literal.
Fixes: #16614

Why do we need an extra normalization step?

I also wonder about this extra normalization, this looks a bit odd. Why do we need to do this?

Why do we need an extra normalization step?

I also wonder about this extra normalization, this looks a bit odd. Why do we need to do this?

Please check the new version of the test that I pushed.
The issue is that if we don't normalize everything we have a NOT, wrapping the following:
case(true, false, false, true, false, (NULL IS NULL))

and since NOT is just dropped, the above expression is normalized outside the ScalarsAndRefsToTrue and gives false.
If we normalize every expression, then case(true, false, false, true, false, (NULL IS NULL)) is normalized to: case(true, false, false, true, false, true) and hits this: https://github.com/crate/crate/blob/master/server/src/main/java/io/crate/analyze/ScalarsAndRefsToTrue.java#L101 which translates the whole case symbol to true, and then NOT(true), not is dropped -> true`.

We probably need some code comments about normalization.
The shortest I can imagine would be smth like
Without normalization, IS NULL inside an expression turns the whole expression into a Function even if evaluation of the Function theoretically can be resolved to a Literal. Turning into Literal is vital for cases when top level Function is wrapped by the NOT operator.

Without normalization, IS NULL inside an expression turns the whole expression into a Function even if evaluation of the Function theoretically can be resolved to a Literal. Turning into Literal is vital for cases when top level Function is wrapped by the NOT operator.

Added comment, please check.


vscode-server: multi-root workspace fails to open terminal if terminal.integrated.cwd is set

When using vscode-server version 1.77.3, if a multi-root workspace is in use (via a *.code-workspace file). If there are multiple folder listed along with the terminal.integrated.cwd setting any new terminal created fails to open

example workspace file:
{
    "folders": [
        {"path": "dir1"},
        {"path": "dir2"}
    ],
    "settings": {
        "terminal.integrated.cwd": "/home/sfwork/tmp"
    }
}

Version: 1.77.3
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: server-distro

/duplicate https://github.com/microsoft/vscode/issues/189166


Add ability to set environment variables.

It doesn't appear that it's possible to set environment variables.
Having a environment entry that takes a dictionary of name/values like the default mi debugger would be great:
e.g.
            "environment": [
                { "name" : "DYLD_LIBRARY_PATH", "value" : ".:./plugins" },
                { "name" : "LIBRARY_PATH", "value" : ".:./components" },
            ],

Try "env" : { ... } ?

Yes that works. thank you!
Should add that to the doc.
The format is slightly different to the "environment" key used by other configs:
env : {
"key1" : "value1",
"key2" : "value2"
}

I'm confused: it is documented in the readme.

you're right.. my bad... i totally missed it :(

I'm using:
"env": { "DATABASE_URL":"user=admin host=localhost dbname=db" },

and it doesn't seem to be taken into account when I launch (i.e. my program fails to find the DB), while another config (default mac OS launch) using the same string works.
How comes? How to debug?


HelpBox is displayed in odd months

Description
Currently, the HelpBox is displayed in months September and October, which seem odd since course planning doesn't really occur during these months.
    const currentMonthIndex = new Date().getMonth(); // 0=Jan
    const activeMonthIndices = [false, false, false, false, false, false, false, false, true, true, false, false];

    {...}

            {activeMonthIndices[currentMonthIndex] && <HelpBox />}
            <PrivacyPolicyBanner />
        </div>
    );

Brian guessed that it may have been based on recruitment months (?). Regardless the HelpBox is for course scheduling, so it should line up better with which months students plan.

Main Quarters

Based on the quarterly schedule, it would make sense to me for HelpBox to be shown in:

May for Fall courses
November for Winter ourses
February for Spring courses

Summer Session

I am unsure of when Summer Session enrolls... but it most likely would... overlap with May anyways (?). More input needed here!

Freshman // SPOP

Also, regarding freshies, SPOP planning runs from possibly June all the way into August. If we want to display the HelpBox for all of summer, that would also resolve the Summer Session issue but perhaps run the risk of being a little too prominent.
One solution could be to implement a dismiss/close out functionality a lá the ICS major popup and have it close out for some period of time!
Tagging @EricPedley for comment!

I think it should be May, June, August, December, November, December, February, and March. Those are, safely, every month in which you could enroll in normal quarter courses. Add summer enrollment in, and we'll be covering almost every month of the year. Alternatively, we could just keep it up. It doesn't hurt, right?

I think it should be May, June, August, December, November, December, February, and March. Those are, safely, every month in which you could enroll in normal quarter courses. Add summer enrollment in, and we'll be covering almost every month of the year. Alternatively, we could just keep it up. It doesn't hurt, right?

Do you think something along the lines of, show them in these months, but it's dismissible? If dismissed, it'll return on the 1st  of the next "active" month as long as that's 30+ days from dismissal.
That might be a bit over-engineered though... My main reservation with it always being displayed is that it's a little too "loud"/visible on the screen.

For any future good first doers, if it's decided that a dismissible helpbox is the best way forward, a similar implementation in our codebase would be RecruitmentBanner, found in CourseRenderPane.tsx!
Some of the relevant code is here:
const RecruitmentBanner = () => {
    const [bannerVisibility, setBannerVisibility] = useState(true);

    // Display recruitment banner if more than 11 weeks (in ms) has passed since last dismissal
    const recruitmentDismissalTime = window.localStorage.getItem('recruitmentDismissalTime');
    const dismissedRecently =
        recruitmentDismissalTime !== null &&
        Date.now() - parseInt(recruitmentDismissalTime) < 11 * 7 * 24 * 3600 * 1000;
    const isSearchCS = ['COMPSCI', 'IN4MATX', 'I&C SCI', 'STATS'].includes(RightPaneStore.getFormData().deptValue);
    const displayRecruitmentBanner = bannerVisibility && !dismissedRecently && isSearchCS;


Fix #398: Support UUIDs

This PR enables UUIDs support in both ways:

Via Endpoint instance uuid and uuids (tail extractor)
Via DecodeRequest instance for UUID type

So the following works as expected.
val a: Endpoint[UUID] = get("users" / uuid) { id: UUID =>
  Ok(id)
}

val b: RequestReader[UUID] = param("id").as[UUID]

Current coverage is 93.04%

Merging #399 into master will decrease coverage by -1.02% as of 398e6fe

Powered by Codecov. Updated on successful CI builds.


Could not find module ember-pikaday/components/pikaday-input

When I build or run my Ember app with --environment=production then I get the above error. I just re-npm'd the package and ran the generator to be sure, and after having done that, I look in node_modules/ember-pikaday/app/components/pikaday-input.js, which does an import, supposedly from ember-pikaday/components/pikaday-input, but that file doesn't exist. There is a pikaday-input.js in ember-pikaday/addon/components however, but if I add "addon" to the path, then it won't the compile step fails when running ember server.
Is the import statement wrong, or am I looking in the wrong place?
Here's the entire node_modules/ember-pikaday/app/components/pikaday-input.js:
import Ember from 'ember';
import PikadayInputComponent from 'ember-pikaday/components/pikaday-input';

export default PikadayInputComponent;

and the file tree is:
ember-pikaday
|__addon
|    |__components
|         |__pikaday-input.js
|__app
     |__components
          |__pikaday-input.js

When I do ember g ember-pikaday a folder called just "pikaday" is created in bower_components. There is no components folder within that. Is that part of the problem? Is the blueprint creating a folder that's not what's expected?

That's weird. I will take a look and report my findings!

Thinking it might be the plugin, I tried switching to ember-cli-bootstrap-datepicker but that had the same problem. I can run simply ember s and everything works fine, just as with ember-pikaday. But when I do ember s --environment=production then it complains about the missing module. Strange that it's just the datepicker it can't find. I wonder if it's some ember-cli build issue, maybe tied to the fact that my datepickers are within a conditional or something. I really don't know, I'm a relative beginner at all this.

Okay, looks like it had nothing to do with ember-pikaday or my other datepicker. It was due to an upstream error with Ember.Handlebars.compile being used in bootstrap-sass or something else, and when building for production, the Handlebars.runtime.js file doesn't include that function. The fix for this is described on the ember-cli site.
In essence, this could happen with any add-on, if some other one uses a non-precompiled files. So it's really an issue with whatever add-on that is.


1.4 Release

1.4 Project https://github.com/cilium/cilium/projects/11

Release Dates
No release dates were documented as part of this.
Release Checklist

[x] Planning
[x] Development Phase
[x] Feature Freeze
[x] Feature Exception Freeze
[x] Bugfix Freeze
[x] Bugfix Exception Freeze
[x] Branch off v1.4
[x] Final Release
[x] Upgrade & downgrade instructions
[x] Tag Release
[x] Release Blog
[x] Announcement

1.4.0 has been released: https://github.com/cilium/cilium/releases/tag/v1.4.0 , closing this.


runtime-config: Require serial hook execution

Extend #157 to avoid:
hook 1: spawn ---------------> reaped
hook 2:       spawn ----------------> reaped
hook 3:             spawn -----> reaped

and explicitly require:
hook 1: spawn --> reaped
hook 2:                  spawn --> reaped
hook 3:                                   spawn --> reaped

Folks who do want parallel execution are free to use a parallelizing
wrapper:
hook 1: spawn ---------------------------> reaped
              child 1 -----> reaped
                child 2 ---------> reaped
                  child 3 ---> reaped

Although that cuts both ways (with parallel hooks, folks could always
use a single hook with a serializing wrapper).  Still, I'd guess most
current implementations are already taking the serialized approach, so
it makes bundle-author life easier if we are explicit about that.

I understand the scenario, it looks good, just wondering if the phrase "with each hook process being reaped" will make some users think the second hook needs to wait until all processes from the first hook are reaped. Because I do have this question when I first read this, maybe just me?

On Mon, Dec 14, 2015 at 12:38:53AM -0800, Qiang Huang wrote:

I understand the scenario, it looks good, just wondering if the
phrase "with each hook process being reaped" will make some users
think the second hook needs to wait until all processes from the
first hook are reaped. Because I do have this question when I first
read this, maybe just me?

Probably not just you ;).  Would some more polished version of:
“runtimes are just waiting on the hook process they launch, and don't
jump through hoops to track or kill any additional processes spawned
by the hook” help?

Probably not just you ;).  Would some more polished version of:
“runtimes are just waiting on the hook process they launch, and don't
jump through hoops to track or kill any additional processes spawned
by the hook” help?

I don't know, it looks complicated and still not clear enough, and I don't have a better suggestion TBH.
Maybe we can just keep it as it was, the original definition looks good to me, I don't think implementation authors would confuse about how to serialize hooks, as you said, they can be serialized or paralleled anyway. I think on this point, we can keep spec minimal and stable, and enable innovation and experimentation above and around it(quoted from OCI charter).
Let's also wait for other maintainers' options.

On Tue, Dec 15, 2015 at 01:24:01AM -0800, Qiang Huang wrote:

Maybe we can just keep it as it was, the original definition looks
good to me, I don't think implementation authors would confuse about
how to serialize hooks, as you said, they can be serialized or
paralleled anyway.

My issue here is that config authors who need serialized execution
(e.g. for things like this 1) will be forced to use a shell script
or some such for all the steps.  And folks who need parallelization
(maybe their hooks all talk together?) will be forced to use a shell
script or some such to set that up.  So being vague makes life easier
for runtime authors (who get lots of choices) but hard for bundle
authors (who have to work around the ambiguity).

I think on this point, we can keep spec minimal and stable, and enable innovation and experimentation above and around it(quoted
from OCI charter).

If phrasing for serialization is too complicated (and we're
intentionally shooting for per-runtime choices around
serialization/parallelization), then I still think we should just drop
the current “Hooks MUST be called in the listed order” requirement
2.  Without something along the lines of this PR, I don't see how
you'd test for compliance with that requirement.

Honestly, serial is the best guarantee without introducing a syntax like
that of systemd.unit files where services (
http://www.freedesktop.org/software/systemd/man/systemd.service.html) have
a Requires= and After= notation to enforce order, otherwise it is
parallelizable.
On Tue, Dec 15, 2015 at 11:10 AM, W. Trevor King<EMAIL_ADDRESS>wrote:

On Tue, Dec 15, 2015 at 01:24:01AM -0800, Qiang Huang wrote:

Maybe we can just keep it as it was, the original definition looks
good to me, I don't think implementation authors would confuse about
how to serialize hooks, as you said, they can be serialized or
paralleled anyway.

My issue here is that config authors who need serialized execution
(e.g. for things like this 1) will be forced to use a shell script
or some such for all the steps. And folks who need parallelization
(maybe their hooks all talk together?) will be forced to use a shell
script or some such to set that up. So being vague makes life easier
for runtime authors (who get lots of choices) but hard for bundle
authors (who have to work around the ambiguity).

I think on this point, we can keep spec minimal and stable, and enable innovation and experimentation above and around it(quoted
from OCI charter).

If phrasing for serialization is too complicated (and we're
intentionally shooting for per-runtime choices around
serialization/parallelization), then I still think we should just drop
the current “Hooks MUST be called in the listed order” requirement
2. Without something along the lines of this PR, I don't see how
you'd test for compliance with that requirement.
—
Reply to this email directly or view it on GitHub
https://github.com/opencontainers/specs/pull/265#issuecomment-164810859.

On Tue, Dec 15, 2015 at 08:28:55AM -0800, Vincent Batts wrote:

Honestly, serial is the best guarantee without introducing a syntax
like that of systemd.unit files…

That works for me, and it is where I'm going with the changes
suggested by this PR (as of 330223b31).  I think we're on the same
page then (Qiang liked it here 1), but we need to figure out if/how
we want to clarify Qiang's concern about hook-child reaping 1, since
my suggested approach to that 2 seems too confusing 3.  Re-reading
3, it's possible that Qiang's “keep it as it was” was “the current
PR looks good to me” and not “the pre-330223b31 spec is fine as it
stands” which was how I'd read his comment when I wrote 4.

I am in favor of serial execution of plugins. I am confused about the "reaped" language though. It seems like saying "Hooks will be executed in order and the next hook won't be executed until the previous has exited".

On Wed, Dec 16, 2015 at 08:46:16AM -0800, Brandon Philips wrote:

I am confused about the "reaped" language though. It seems like
saying "Hooks will be executed in order and the next hook won't be
executed until the previous has exited".

Reaped is one step past process-exit, when the zombie's entry is
removed from the process table 1.  As far as the spec goes, the
distinction is that after hook-process-exit, there is an exit code,
but until the host-process reaps the hook-process, the host-process
won't know what that exit code is (barring something complicated like
a waitid call with WNOWAIT).

that is the fully implication of the current sentence. The act of waiting on a pid is an implementation detail.

There is no need to tell people that they need to reap processes in the specification.

On Wed, Jan 13, 2016 at 01:50:49PM -0800, Vincent Batts wrote:

that is the fully implication of the current sentence. The act of
waiting on a pid is an implementation detail.

I don't mind if the runtime decides to not collect the PID, but I
don't see how the current “Hooks MUST be called in the listed order”
requires the runtime to wait for a hook to exit before launching the
next one.
Anyhow, I'm fine waiting on compliance testing to bring this back
around, assuming a split create/exec hasn't obsoleted hooks 1 by the
time we get compliance testing for hooks.

Now that we've decided to keep hooks and closed #483, I think we want
to re-open this one.  I think testing it is going to be tricky, but
I'm pretty sure we don't want parallel hook execution (and
@crosbymichael seemed to agree 1).  If we want to leave the PR
closed until ocitools validates hook functionality, I'm happy to float
a Most Egregious Accurate Interpretation of the current spec wording
;) 2.
 Subject: Reviewing the specifications from a compliance perspective and a thought to certification
 Date: Tue, 9 Aug 2016 12:38:33 -0700 (PDT)
 Message-Id<EMAIL_ADDRESS>


Add Soft Manilo theme

I'd like to add a "soft Manilo" theme, similar to the dark catppuccino theme but primarily with a softer dark gray background.

I'll submit a PR for this.

actually, this is overkill. I can get the theme I want with minimal customization of the dark catppuccino theme.

You mind sharing how it looks?

I love it, but the color of everything else looks too sharp (text, functions, the blues). Make the PR and we will improve it :)
Some ideas:

Decrease saturation
Make all colors draw to one color (in this case brown, I suppose)


added ability to show YOLOX demo in live window

This PR adds the possibility to run YOLOX live on web camera - showing the detections in a "live" window. I had to do some minor fixes as it always changed the save-path even it was not intended to save the results. Therefore the PR is somewhat bigger than needed - so it also fix a minor other issue.
 python tools/demo.py webcam -n yolox-l -c yolox_l.pth --camid 0 --conf 0.25 --nms 0.45 --tsize 640 --device cpu
Will now give a result like this (running on a GPU less MacBook):

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

LGTM.


Ensure docker-compose.yml works with Podman Compose

Resolves the following error:
Error: short-name "postgres:15.5" did not resolve to an alias and no unqualified-search registries are defined in
"/etc/containers/registries.conf"

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


CI: doctr runs faster if you don't comment it out

Reverts https://github.com/NSLS-II/ophyd/commit/8e603b0d1fcf83ed2c8c29d3a49ba662b7109046


x/vulndb: suggestion regarding GO-2022-1039

Report ID
GO-2022-1039
Suggestion/Comment
The content of the warning is:

calls regexp.MustCompile, which eventually calls regexp/syntax.Parse

My code does indeed call MustCompile, but all of the non-test call sites pass in a literal string to the regex. As such, the call is trusted. If I undestand this vulnerability report correctly, it effectively means we can't ever use regexes and get a clean bill of health from govulncheck.
package main

import (
	"fmt"
	"regexp"
)

var re = regexp.MustCompile("trusted")

func main() {
	fmt.Println(re.String())
}

I was able to confirm that upgrading to both go1.18.7 and go1.19.2 fixes this.

Hi Yuval, thanks for filing an issue! You're absolutely correct that govulncheck will always surface this vulnerability (unless you update to the latest Go version, as you just did), whether the call is safe or not.
This is a tricky problem because there are so many ways that a certain call could be safe or unsafe, some of which are automatically detectable and some of which are not. So, for now, we mark calls as potentially vulnerable and leave it up to humans to decide if the vulnerability applies to their code.
I've transferred this issue to the main issue tracker, and the team will discuss this further. We're also open to ideas or suggestions.

As @tatianab pointed out, govulncheck will report this vulnerability whenever it concludes that regexp/syntax.Parse is called. It does not have a mechanism for figuring out if the call arguments are trusted.
Would some form of warning suppression help in your case? If so, would that be a code annotation or a config file you'd be willing provide to govulncheck?

Thanks for the quick reply, both!
Yes, warning suppression would be totally fine. I think the easiest from a user's perspective would be an annotation/comment directly in the code.

Thank you for your feedback! This will help us in planning for future iterations of govulncheck.

In case it's helpful (re "we mark calls as potentially vulnerable and leave it up to humans to decide", above): my use case is that I wanted to run govulncheck in a GitHub action for pull requests. So having a human look over the vulnerability once is totally fine (expected, even), but having to do that each time effectively turns the action into a false-alarm generator that we'd quickly learn to ignore.
One option would be for me to get the results as json (which I know govulncheck supports), and then examine that to effectively do my own suppressions. Those would probably have to be at the file level, but it'd be better than nothing. But, having it built into the tool would be better still. :-)
Thanks again!

@gopherbot gh pr checkout 116


load_stac : apply rescale and offset or not?

@ValentinaHutter @GeraldIr @SerRichard
The stackstac library allows to automatically rescale the data if the raster extension is provided and if the scale and offset values are set:
https://github.com/gjoseph92/stackstac/blob/694c68646a685abc8f3455d6b28fe121e18ae775/CHANGELOG.md?plain=1#L4
like here: https://earth-search.aws.element84.com/v1/collections/sentinel-2-l2a/items/S2A_32TPS_20230602_0_L2A
After the latest update, rescale is True by default and therefore it changed the values I was expecting to get.
Would we have better to set rescale=False by default?
@jdries do you apply scale and offset in load_stac at VITO?

The decision is not to apply scale and offset automatically. See discussions here https://github.com/Open-EO/openeo-processes/issues/503 and related PR fixing the process definition here: https://github.com/Open-EO/openeo-processes/pull/512


JavaScript error OS X Catalina

Issue description
Getting the error message below, followed by a blank screen
Wallet version
1.0.0
System specification
OS X Catalina 10.15.7
Is it a repeatable issue?
Yes, happens every time, also on older systems.
Beta version was working fine.
Steps To reproduce the issue
Open Firefly
Expected behaviour
No error
Errors

Closing as duplicate of #1006