text:
faf rename

I want to postpone this until we do a new release when this change will be visible on retrace.fedoraproject.org/faf/

I guess this is relevant now with https://github.com/abrt/faf/commit/c0671b80d9b95f3fa66f62f7a5cd2cd59fffb001

Opps, I kind of forgot about this one. Updated and rebased. Please take a look.

Updated.

The blog post is published on March 29th 2019, so pretty much buried.
Not visible on front page of https://abrt.github.io/ nor http://fedoraplanet.org/

authors: mkutlak xsuchy


text:
Fix ABSL_RANDOM_RANDEN_COPTS setting on FreeBSD

The error message is as follows:
CMake Warning at absl/copts/AbseilConfigureCopts.cmake:30 (message):
  Value of CMAKE_SYSTEM_PROCESSOR (amd64) is unknown and cannot be used to
  set ABSL_RANDOM_RANDEN_COPTS
Call Stack (most recent call first):
  CMake/AbseilHelpers.cmake:18 (include)
  CMakeLists.txt:57 (include)

Thanks!

source: gharchive/pull-request

repo: abseil/abseil-cpp

license_type: permissive

license_source: bigquery


text:
Cats needs to be GPL v3.0 licensed to distribute mmd tools

mmd tools is licensed GPL v3.0 since Apr 5, 2020 https://github.com/UuuNyaa/blender_mmd_tools/blob/main/LICENSE, which is a copyleft license that requires that any works that include it in distribution to be under the same license. This means that Cats must also be licensed GPL v3.0 if it is to include any of mmd tools (or any other copied or modified GPL v3.0 code) in its distribution. However, Cats is currently MIT licensed, thus violating the copyleft aspect of the GPL v3.0 license.
There's also https://github.com/absolute-quantum/cats-blender-plugin/blob/master/tools/fbx_patch.py which is GPL v2.0 or newer and thus requires Cats to be GPL v2.0 or newer.
There shouldn't be any issues with changing Cats' license to GPL v3.0, since the existing MIT license is compatible with it. Similarly, distributing Immersive Scaler as GPL v3.0 with Cats would be fine too, since it's MIT licensed.
To quote wikipedia on GPL compatibility https://en.wikipedia.org/wiki/License_compatibility#GPL_compatibility

Many of the most common free-software licenses, especially the permissive licenses, such as the original MIT/X license, BSD licenses (in the three-clause and two-clause forms, though not the original four-clause form), MPL 2.0, and LGPL, are GPL-compatible. That is, their code can be combined with a program under the GPL without conflict, and the new combination would have the GPL applied to the whole (but the other license would not so apply).

Done and done!

source: gharchive/issue

repo: absolute-quantum/cats-blender-plugin

license: MIT

license_source: github-api


text:
🛑 Portfolio is down

In a4eeb7d, Portfolio (https://absozero.github.io) was down:

HTTP code: 404
Response time: 176 ms

Resolved: Portfolio is back up in 71b69e1.

repo: absozero/uptime


text:
evaluate

hello,how to use map to evaluate this model

Hi.
Sorry, I don't exactly understand what you're asking for. It's possible to either evaluate model on COCO validation set or to obtain mask for any image. It's all described in the readme.

The best way to do it is to store predictions in COCO format and use official scripts for evaluation. Unfortunately, I didn't implement it, but it's not hard to do.
You can modify the _run_validation method or add a similar one, which calculates predictions (self.score_predictions/self.refinement_prediction for SharpMask) in the session run instead of metric calculation. Then store predictions in COCO format and use COCO evaluation tools to calculate AP - https://github.com/cocodataset/cocoapi/blob/master/PythonAPI/pycocotools/cocoeval.py

Ok, I will try it, thank you very much.


text:
AxiosError: Request failed with status code 400

Running site throws up this Unhandled Runtime Error: AxiosError: Request failed with status code 400

Shouldn't that be a const from the .env like INFURA_IPFS_GATEWAY= ?

during transaction defined url is hardcoded on chain. Also tried with cid but public domain is no longer working. If you find any solution please let me know or create pull request :)

Not sure how one would instantiate or bypass a previous hardcoded address. Is there any way to avoid infura, option to use other cloud providers like https://www.pinata.cloud?


text:
ContentType.FormData no longer sets the correct boundary

This PR: https://github.com/acacode/swagger-typescript-api/pull/168/commits/29d89ec74bfc1598c3b05a624efdd9f109051eb4
breaks the boundary setting for FormData.
Right now the header will look like this: Content-Type: multipart/form-data instead of something like Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryUAzmDsnaGSk1qaI3

Hello @Styn !
Thanks for this issue, can you fix that problem and create PR ?

Or if not, don't worry I'll fix that but I need a bit more time

I'll have a PR up soon

@Styn fixed in 5.1.5, thank you!

repo: acacode/swagger-typescript-api


text:
Update _config.yml

lyc.png

It looks like you are attempting to push a change to the part repository, for help with deploying please start a new thread in the discussions.

authors: rjzupkoii thelychen

license: mit


text:
fix(template) Adjust current time handling in API

Signed-off-by: Jerome Simeon jeromesimeon@me.com
Changes

Clean up / adjustment to current time handling in API and parser manager

Coverage decreased (-0.004%) to 91.506% when pulling 7f1b5635e187920eafd6879b276d58b6f759763d on parserv2 into 029c3edf9fe21b2ed28aafb9866a816ab9b39637 on master.

authors: coveralls jeromesimeon

repo: accordproject/markdown-transform


text:
🛑 accubits.com is down

In 931452c, accubits.com (https://accubits.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: accubits.com is back up in 1c86a3e after 6 minutes.

repo: accubits-nightswatch/upptime


text:
Publish new version

Hi,
I am in need of the change done in #136, which was merged last month and not yet published. If possible, could you please publish the changes?
Thanks.

https://github.com/acdlite/redux-actions/releases/tag/v0.13.0
https://github.com/acdlite/redux-actions/commit/4b6a9805f76063f6c8e93f864ad74279c55874a6
👌 ✌ 🍻

Thanks!

authors: TimothyGu yangmillstheory

repo: acdlite/redux-actions


text:
implement FSA errors by setting error to true if payload is an Error obj

Noticed this spec of FSA wasn't yet implemented, and there's an issue for it.
This sets action.error to true if the payload is a direct instance of Error. This is the faintest touch of magic, but if it's documented, it makes sense.
Also fixes a possible error where we're trying to set action.meta even though action is a const.
r? @acdlite

Not sure about this... Feels like it's outside the scope of the module. if the payload is an error, that means someone caught the error and placed it there. Shouldn't it be up to them to set error to true?

But there doesn't seem to be a way to set error to true with createAction. The only thing that can be set by the user is type and payload.

Oh duh I see what you mean. I was thinking about handleAction() for some reason — actually I dunno what I was thinking.
This seems reasonable then.

Updated to use instanceof

+1

+1

+1

+1

+1, please can you consider releasing this, @acdlite?

+1

I'm running into this issue now as well. Is this issue expected to be resolved soon?

+1

I've also had the same issue, I hope it's gonna be released soon!

@ngokevin this is awesome, thanks for submitting! Can you update the README to document your change?
Does this change look like it will be a breaking change? I can't think of any scenarios where this would cause existing code not to work but if anyone can then we will need @acdlite's input before merging.

@lukewestby thanks for checking it out, updated.

:+1:

@ngokevin
seems we can't customize the error object by payloadCreator.
maybe we can do in this way
export default function createAction(type, actionCreator, metaCreator) {
  const finalActionCreator = typeof actionCreator === 'function'
    ? actionCreator
    : identity;

  return (...args) => {
    const payload = finalActionCreator(...args)
    const action = {
      type,
      payload,
      error: (payload instanceof Error)
    };

    if (typeof metaCreator === 'function') {
      action.meta = metaCreator(...args);
    }

    return action;
  };
}

Huzzah! I finally got off my ass and merged this! Thanks!

@acdlite
I've create a PR to set error to true when payloadCreator return Error object.

authors: Strate acdlite bravewick cappslock danilotorrisi jonny-improbable kpaxqin krasnoperov lukewestby ngokevin pbomb ricardofbarros tkqubo tokenvolt


text:
integrate weapp auth backend into this project

As title.
Integrate with python-weixin

run_pipeline *args, **out and signature of the func

pipeline
backend
remark

social_core.pipeline.social_auth.social_details
get_user_details
Get the information we can about the user and return it in a simple format to create the user instance later. In some cases the details are  already part of the auth response from the provider, but sometimes this could hit a provider API.

social_core.pipeline.social_auth.social_uid
get_user_id
Get the social uid from whichever service we're authing thru. The uid is the unique identifier of the given user in the provider.

social_core.pipeline.social_auth.auth_allowed
auth_allowed
Verifies that the current auth process is valid within the current project, this is where emails and domains whitelists are applied (if defined).

social_core.pipeline.social_auth.social_user
nothing to control
Checks if the current social-account is already associated in the site.

social_core.pipeline.user.get_username
need social_details return  username and email
Make up a username for this person, appends a random string at the end if there's any collision.

social_core.pipeline.user.create_user
nothing to control
Create a user account if we haven't found one yet.

social_core.pipeline.social_auth.associate_user
nothing to control
Create the record that associates the social account with the user.

social_core.pipeline.social_auth.load_extra_data
extra_data
Populate the extra_data field in the social record with the values  specified by settings (and the default ones like access_token, etc).

social_core.pipeline.user.user_details
nothing to control
Update the user record with any changed info from the auth service.

In order to be consistent across all the  Service Account, Subscription Account and Mini Program (weapp), we need an option named SOCIAL_AUTH_WEIXIN_WEAPP_UNIONID_AS_USERNAME_FIELD
Please refer to
https://zhuanlan.zhihu.com/p/63203979

login method
admin dashboard
OAuth

App (Android/iOS)
open.weixin.qq.com - mobile app
Yes

QR Code Web
open.weixin.qq.com - web app
Yes

WX App embedded web link
mp.weixin.qq.com - Service/Subscription account
Yes

mini program (weapp)
mp.weixin.qq.com - weapp
No

weapp is a special type of OAuth. So it could inherit from social_core.backends.oauth.BaseOAuth2 without do_auth.redirect_uri


text:
Redirect errors with valid cookies

Using the latest release (0.4.2) like this:
$ edge-gpt-image --prompt "A funny cat" --cookie-file /tmp/cookies.json

Results in:
Traceback (most recent call last):
  File "/nix/store/6xycw16a59gf3wlpbs7cpabayz10q40w-python3.10-edge-gpt-0.10.11/bin/.edge-gpt-image-wrapped", line 9, in <module>
    sys.exit(main())
  File "/nix/store/5h6j028kglkpysjpsp517dvcb1a6w703-python3.10-bing-image-creator-0.4.2/lib/python3.10/site-packages/BingImageCreator.py", line 467, in main
    asyncio.run(
  File "/nix/store/6qk2ybm2yx2dxmx9h4dikr1shjhhbpfr-python3-3.10.11/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/nix/store/6qk2ybm2yx2dxmx9h4dikr1shjhhbpfr-python3-3.10.11/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/nix/store/5h6j028kglkpysjpsp517dvcb1a6w703-python3.10-bing-image-creator-0.4.2/lib/python3.10/site-packages/BingImageCreator.py", line 394, in async_image_gen
    images = await image_generator.get_images(prompt)
  File "/nix/store/5h6j028kglkpysjpsp517dvcb1a6w703-python3.10-bing-image-creator-0.4.2/lib/python3.10/site-packages/BingImageCreator.py", line 299, in get_images
    raise Exception("Redirect failed")
Exception: Redirect failed

Full error:
errors.txt
The same cookie works in edge-gpt:
edge-gpt --prompt "A funny cat" --cookie-file /tmp/cookies.json

        EdgeGPT - A demo of reverse engineering the Bing GPT chatbot
        Repo: github.com/acheong08/EdgeGPT
        By: Antonio Cheong

        !help for help

        Type !exit to exit

Initializing...
Enter `alt+enter` or `escape+enter` to send a message

You:
A funny cat

Bot:
Searching the web for: `funny cat`
...

When opening saving the response as html, it will result in the following:
There was a problem creating your images
We're working to resolve this issue and your boost won't be used. Please try creating again later.
In the meantime, [Explore other creations](file:///images/create?FORM=GERRLP) on the Image Creator homepage.

Upgrade BingImageCreator and try python3 -m BingImageCreator --cookie-file ./cookies.json --prompt "creepy Microsoft"

Upgrade to what? I am already using the latest code: https://github.com/acheong08/BingImageCreator/commit/c43e9a291ab6026ddfaf5eec522ebe6b10b39f03

$ python3 -m BingImageCreator --cookie-file ./cookies.json --prompt "creepy Microsoft"
Sending request...
ERROR: <!DOCTYPE html><title>creepy Microsoft - Image Creator from Microsoft Bing</title><meta content="text/html; charset=utf-8" http-equiv="content-type" /><meta name="referrer" content="origin-when-cross-origin" /><meta property="og:description" content="Intelligent search from Bing makes it easier to quickly find what you’re looking for and rewards you." /><meta property="og:site_name" content="Bing" /><meta property="og:title" content="creepy Microsoft - Bing" /><meta property="og:url" content="https://www.bing.com/images/create?q=creepy Microsoft&rt=3&FORM=GENCRE" /><meta property="fb:app_id" content="570810223073062" /><meta property="og:image" content="http://www.bing.com/sa/simg/facebook_sharing_5.png" /><meta property="og:type" content="website" /><meta property="og:image:width" content="600" /><meta property="og:image:height" content="315" /><meta content="text/html; charset=utf-8" http-equiv="content-type" /><meta name="referrer" content="origin-when-cross-origin" /><link href="/sa/simg/favicon-trans-bg-blue-mg.ico" data-orighref="" rel="icon" /><link href="/sa/simg/Roboto_Regular.woff2" rel="preload" type="font/woff2" as="font" crossorigin="anonymous" /><link href="/sa/simg/Roboto_Semibold.woff2" rel="preload" type="font/woff2" as="font" crossorigin="anonymous" />
Traceback (most recent call last):
  File "/nix/store/6qk2ybm2yx2dxmx9h4dikr1shjhhbpfr-python3-3.10.11/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/nix/store/6qk2ybm2yx2dxmx9h4dikr1shjhhbpfr-python3-3.10.11/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/tmp/agitated-kapitsa-VVjWIV/BingImageCreator/src/BingImageCreator.py", line 481, in <module>
    main()
  File "/tmp/agitated-kapitsa-VVjWIV/BingImageCreator/src/BingImageCreator.py", line 464, in main
    image_generator.get_images(args.prompt),
  File "/tmp/agitated-kapitsa-VVjWIV/BingImageCreator/src/BingImageCreator.py", line 139, in get_images
    raise Exception(error_redirect)
Exception: Redirect failed

Yeah. Hard to tell if the actual error is only server side. Will try to see if I can replicate this with a different account later.

Also having this error

@Mic92 @mak448a
Please, try so set the env var :
BING_URL=https://cn.bing.com
despite, i'm in France ... I've don't need this error using chineese bing
perhaps it could work better for you ...
I'm pretty sure it could help you too

I tried cn.bing.com without success. I can see it's beeing used from the error message containing cn.bing.com

I was able to use it now with a different account...
The new account I created also didn't work, but another old one did.

license: Unlicense


text:
feat: ios preprocessing page (url metadata)

Summary
on iOS we can use a JavaScript file to preprocess the webpage before the share extension is called (cf Accessing a Webpage). This is useful if we want to extract data directlty from the webpage and avoid to scrap the url in a second time.

Custom configuration example
    "plugins": [
      [
        "expo-share-intent",
        {
          "iosActivationRules": {
            "NSExtensionActivationSupportsWebURLWithMaxCount": 1,
            "NSExtensionActivationSupportsWebPageWithMaxCount": 1,
          },
          "preprocessorInjectJS": "metas['og\\:image'] = metas['og\\:image'] || document.querySelector('img#main-image')?.getAttribute('src')"
        }
      ],

Todo

[x] Add generic preprocessing script
[x] Auto extra all page header metadata (open graph) in share extension
[x] send all metadata to application
[x] add plugin configuration to add a custom rule to extract content
[x] Update README.md

Issue
Fixes https://github.com/achorein/expo-share-intent/issues/142

This would be an awesome feature to test!

@ansh now available ;)

You're an absolute legend.
Thank you!

authors: achorein ansh

repo: achorein/expo-share-intent


text:
Fiziki durum hakkında bilgi detay sayfasında gelmiyor

Describe the bug
Fiziki durum hakkında bilgi detay sayfasında gelmiyor
To Reproduce
Steps to reproduce the behavior:

Isınmaya ihtiyacım var formunu doldurdum
Tüm alanları doldurdum
Formu başarı ile gönderdim

Expected behavior
Doldurduğumuz form bilgileri görüntülenmeli. Fiziki durum bilgisi de gelmeli
Screenshots

Düzelttim

authors: Corepany onuruci

repo: acikkaynak/deprem-io-frontend


text:
prod deploy

Description
discord username: afetharita#0001
closes #issue
Please describe your changes. Also describe your aim and content. Do not forget to list the dependencies required caused by those changes.
## Things to check before creating a PR

[ ] I have inspected my topic, checked.
[ ] If it is a core feature, executed detailed tests.

Creating PR rules

[ ] PR must be created for an issue with approved tag. Otherwise PR will be rejected.
[ ] Relevant issue number: The issue number related to PR must be attached to head of PR header, after prefix after prefix # must be attached in parenthesis. A header like this could be used "prefix(#issue_number): PR header" .
[ ] A descriptive and understandable title: The PR title should clearly describe the nature and purpose of the changes. The PR title should be the first thing displayed when the PR is opened. And it should follow the semantic commit rules. For example, a title like "docs(#issueId): Add README.md" can be used.
[ ] Related file selection: Only relevant files should be touched and no other files should be affected.
[ ] Format and Lint Suitability : The code should be made in accordance with a certain format standard and examined according to the lint rules.
[ ] Clean commit history: The commits where the changes are made should be clear and organized.
[ ] Opening PR when job is completed: PR should be opened when job is completed and sent for review by other team members.

Changes

[ ] A new feature (a change that adds a new feature, not a breaking change)
[ ] A new refactor (a change that is not a breaking change, that improves the readability or performance of the code)
[ ] A breaking change
[ ] Documentation change

How were these changes tested?
Please describe the tests you did to test the changes you made. Please also specify your test configuration.
Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

tested by the team, things work

repo: acikkaynak/deprem-yardim-frontend


text:
The general package

This looks like a really interesting package. I have a similar methodology for air emissions in a package carbonr. The use of the latitude and longitude is a great addition that you have included! I notice you haven't updated the emissions since the 2019 report. I was wondering if this is still being actively used? Or, if you were interested in any level of collaboration?
Would be great to hear from you.
Thanks.

Hi. I'll take a look at your package.
I have been meaning to update the GHG emissions and include an argument for year, but have not gotten the time to do so. So, for now, everything is based on 2019.
I'd be interested in collaboration. Contact me via email and we can discuss.

authors: acircleda lilyclements

repo: acircleda/footprint


text:
Non-portable printf() in examples/dump-lines.cc

The printf() statement in examples/dump-lines.cc try to print a uint64_t value using %lx.  This do not work on all architectures. I worked around the issue by changing %lx to %llx and casting the value to long long, but suspect it isn't the best solution.  What is your view on this?
The Debian patch can be found in https://anonscm.debian.org/cgit/pkg-coz/libelfin.git/tree/debian/patches/0002-portable-uint64-print.patch .

The portable way is to include inttypes.h and use "%"PRIx64 as the printing format. More info: http://en.cppreference.com/w/c/types/integer

Just to be clear, the "do not work" statement mean the build fail when the default compiler flags are used in Debian.  https://buildd.debian.org/status/fetch.php?pkg=libelfin&arch=mipsel&ver=0.2-4&stamp=1479216536 show the kind of build failure we got on some autobuilders:
dump-lines.cc: In function 'void dump_line_table(const dwarf::line_table&)':
dump-lines.cc:16:55: error: format '%lx' expects argument of type 'long unsigned int', but argument 4 has type 'dwarf::taddr {aka long long unsigned int}' [-Werror=format=]
                                line.line, line.address);
                                                       ^
cc1plus: all warnings being treated as errors

As a bonus, I just cleaned up all of the places where I was lazy and cast arguments to printf to unsigned long so they now use the inttypes.h macros.

authors: aclements llvilanova petterreinholdtsen

repo: aclements/libelfin


text:
[Doc] 补充线程池替换 Hippo4J 文档

补充 JDK 线程池、Spring 线程池替换为 Hippo4J 动态线程池文档教程

官网 Link：https://hippox.cn

repo: acmenlt/dynamic-threadpool


text:
Acorn service resolution not working propely

In order to expose all the ports exposed in all the containers on the acorns as a single cohesive service, we have this "router" functionality that should create a daemonset in the acorn-system namespace and a couple services in the user namespace. It is currently only creating the DS, not the services.
When this is functioning properly, there should be a service that matches the name of the acorn that exposes all the ports from the containers in the acorn.
Note: we DO already create a service per container. This is a meta service that aggregates all the containers' ports.

Using this file:
containers: {
     web: {
         image: "nginx"
         ports: "web-app:80/http"                                                                   }
     web2: {
         image: "nginx"
         ports: "web-app:80/http"
     }
}

You can run acorn run -p "web-app:80/http" $(acorn build .) and both containers will be put into a single web-app service.

authors: cjellick cloudnautique

repo: acorn-io/acorn


text:
Library Alpha Discussion: Use Chai or Ava library for assertions?

Hey AoG Devs!
Now that the alpha version of the testing library has been out for a few weeks, we'd like to get feedback on the behavior and API design of the library.
Ava has built in assertions as part of its framework. Right now we use the Chai library. If we use Ava for all assertions there are fewer dependencies. This question is primarily geared toward the example code that we will have for this library as well as tests that may appear in other samples.

I think that we should keep this library more simple. Therefore, +1 to drop the chai dependency. I think that users of this library have the option of whether using the chai or not.

authors: Fleker yoichiro


text:
Cache misses due to path-based versioning and its normalization

This run using actions/cache@v2 shows how a cache created by the update-deps job is not hit by the jobs in the test matrix that depend on update-deps and use the same key. This works in actions/cache@v1, so it looks like a regression to me.
What's more peculiar, each of the three test jobs reported to have successfully stored its cache state under this same key.
In the next run, all jobs hit the cache, but which state did they get?

Hey @mzabaluev, thanks for spotting this.  Can you please enable step debugging, change the key, and re-run the workflow?  This will provide some more output so we can see what's going on.

@dhadka Here you are
I see that the 'Post Cache cargo registry index' step in the producer job gets to write its cache first:
Resource Url: https://artifactcache.actions.githubusercontent.com/SwZ48ggH2fmptrBol7q4o6DwD74REZ2KvEjuDiE8Jb9dgsMc8M/_apis/artifactcache/caches/58

Then the 'Post Cache cargo registry' step allocates at the same resource:
Resource Url: https://artifactcache.actions.githubusercontent.com/SwZ48ggH2fmptrBol7q4o6DwD74REZ2KvEjuDiE8Jb9dgsMc8M/_apis/artifactcache/caches/59

There is also intra-action state CACHE_KEY which is set by the caching steps prior to the above, but in the opposite order:
2020-05-27T02:11:21.4628234Z ##[debug]Save intra-action state CACHE_KEY = cargo-registry-debug1-39f2b8d68761c35ef5f7317c495a2e84f0aed5d34a5d724b2144d58bf6ed66b3
...
2020-05-27T02:11:22.0139963Z ##[debug]Save intra-action state CACHE_KEY = cargo-index-debug1-5d9c7f87b512b22e0543a050c81e91b650b44aff

A consumer job queries and fails with:
Resource Url: https://artifactcache.actions.githubusercontent.com/SwZ48ggH2fmptrBol7q4o6DwD74REZ2KvEjuDiE8Jb9dgsMc8M/_apis/artifactcache/cache?keys=cargo-registry-debug1-39f2b8d68761c35ef5f7317c495a2e84f0aed5d34a5d724b2144d58bf6ed66b3&version=55646160c9f2cc2a37adf24b94db1ec7546d85f0e81c7dde1c978bdca39a013e

Then in the 'Post Cache cargo registry' step, it saves a new value:
Resource Url: https://artifactcache.actions.githubusercontent.com/SwZ48ggH2fmptrBol7q4o6DwD74REZ2KvEjuDiE8Jb9dgsMc8M/_apis/artifactcache/caches/60

@mzabaluev I think I see what's going on.  @v2 introduced a version field, which is used to detect when the configuration of the cache action changes.  This includes what kind of compression it's using (gzip vs zstd) and the path.  From what I see, update-deps is using the path
  with:
    path: ~/.cargo/registry
          !~/.cargo/registry/src

whereas the test step is using:
  with:
    path: ~/.cargo/registry

If you make the path identical in both, you should see it behave as expected.
This was intended to prevent a user from changing the path but using the same key, since the existing cache entry (if any) wouldn't have the right content.  However, in your particular case where you're just excluding a path, it's less helpful.

@dhadka

If you make the path identical in both, you should see it behave as expected.

On Linux and Mac it does, on Windows it doesn't: https://github.com/mzabaluev/github-actions-playground/actions/runs/116588403
I'm guessing that CRLF line endings screw up the version hash.
Consider making the normalization function invariant to whitespace separating the paths, including any line ending characters. The path parameter really could help accepting a list, but I gather that https://github.com/actions/toolkit/issues/184 is preventing that.

For more fun with cache key normalization across OSes, see https://github.com/actions/runner/issues/498

Any updates on this?
I'm trying to decide which actions/cache version is a less buggy fit for our needs, between this and v1 somehow failing to hit the primary key and going for a truncated key it has somehow stored at some point, despite not being given any restore-keys to try prefix searching.

@mzabaluev I don't think this is related to newlines, since both Windows and Linux are reading from the same file, so the line endings wouldn't be changing.  Your issue about new lines and hashFiles is valid, however, since the newlines are being changed by Git.
I suspect this is the result of https://github.com/actions/cache/issues/301.  There's an issue with Windows bsd tar and zstd causing it to hang, so it falls back to gzip compression.

@mzabaluev I've created this PR to trim any leading and trailing whitespace from the path and restore keys, which would also remove any leftover Windows newline characters (\r) after the split - https://github.com/actions/cache/pull/343.  However, as I mentioned in the previous comment, I don't think newlines are causing the issue you see since the yml files don't change across OSes.

@mzabaluev Agreed.  I meant to say that #343 will fix any newline differences in the path which would cause a different version hash, but you'll likely still see Windows creating a different cache because it uses a different compression method.
The version hash includes the compression method, but we fall back to using Gzip on Windows due to bug #301.

The version hash includes the compression method, but we fall back to using Gzip instead of Zstd on Windows due to bug #301.

I hope in the end state it would be possible to share cache state no matter which runner created it, with the restore action being able to adapt to a possibly different archival format; or maybe this and other tar-related issues will be solved by settling on a single flavor of tar that works across all OSes. The disparate cache entries for Windows and Unix would increase our cache pressure twofold and duplicate the dependency fetching work for Windows jobs without a good reason for it.

Yes, we still need tar in the cache action to be fixed.

👋 @mzabaluev we are currently looking into this. For now you could try this approach if it works for you.

I created this repo to illustrate the issue i'm having which is related to this bug.
https://github.com/y-nk/cache-in-container/actions/runs/3427866818
The problem being that an action building outside of a container has a certain path, and so that path cannot be restored once inside a container (bc the context of the container is different)

@mzabaluev @y-nk we are tracking this issue in #984. Please check the current proposal there and provide comments/feedback if any. Closing this as duplicate.

@mzabaluev @y-nk We have released a new beta release which should fix this issue. Try tag: actions/cache@3.1.0-beta. Head over to discussion for feedback: https://github.com/actions/cache/discussions/1019

With actions/cache@v3, a cache key is hit on Windows after being created on Linux.
As evidenced in this workflow (it still fails, but due to an evident problem with the installation of Cargo): https://github.com/mzabaluev/github-actions-playground/actions/runs/3783738410/jobs/6432524102

authors: Phantsure dhadka mzabaluev pdotl y-nk

repo: actions/cache


text:
Adding ARM64 support for Ubuntu to resolve encountered issue on actions/setup-python

Hey,
I have created a pull request (PR) to address an issue I encountered on Ubuntu related to the ARM64 architecture. The issue details can be found here: python/issues/678#issuecomment-1564392289.
In this PR, I have added support for ARM64 in the build step, aiming to fix the problem. However, due to the usage of the repository's registry in the test phase, I'm unable to validate the change at the moment.
I kindly request your review and consideration of this PR. I would greatly appreciate any feedback or guidance you can provide on how to validate the effectiveness of this modification.
Thank you for your time and attention. I look forward to working with you to resolve this issue and improve compatibility for Ubuntu users on ARM64.
Best regards,
Joeri

Hello @Joeri-Abbo. Thank you for your pull requests. But for now we can't approve it because we do not have hosted runners on ubuntu with arm64 architecture.

@dmitry-shibanov Can we somehow use QEMU to build it in github actions?

@dmitry-shibanov Can we somehow use QEMU to build it in github actions?

Should be possible to use QEMU for it, yes.

Hello there,
this PR would be amazing for us because we would like to use action/setup-python with linux arm64 runners, and for now it is not possible. Would you be able to use the same runner as @hussein-awala to try this out (summerwind/actions-runner:v2.306.0-ubuntu-20.04)?

it's not necessary to use arm64 hosted runners to build python interpreter - we can use cross-compilation.

Hey, would be interested in that too. Can this be merged?

Hi,
Can't you run that build on a Github provided arm runner? This is an important part of the whole Github Actions ecosystem so you should get everything what you need to bring this to life.
Can you please explain again what holds you of merging this and start to support Linux/arm64 based runners?
I'm happy to help with whatever is needed.
Thanks for your work!

Same. Would love to use BuildJet as hosted ARM runner, but thwarted by this issue.

Looks like this was recently addressed in https://github.com/actions/python-versions/pull/274 so this PR can now be closed

authors: Joeri-Abbo Maleware V0lantis atwoodjw chris-griffin dmitry-shibanov harryzcy ilya-lavrenov inka samip5

repo: actions/python-versions


text:
Run Stuck at "Complete job"

Description
I have a run that has finished but is still showing up as running.
This doesn't happen very often (it only happened 3 or 4 times to me over the past 6 months)
This issue was resolved while I was writing this ticket, but it would still like to have it documented.

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
version: 2.301.1
I don't have a public example
Is it regression?
No
Expected behavior
It should report its status.
Actual behavior
Stuck.
Repro steps
Run build.
Wait.

Please report to the https://github.com/actions/runner repo, this repo only maintains image specs only.

authors: aqeelat mikhailkoliada

repo: actions/runner-images


text:
how do i use the "install-multiple-jdks" in the Github action

Description:
How do i use the new version of java in the github action
https://github.com/actions/setup-java#install-multiple-jdks
    steps:

        uses: actions/setup-java@v4
        with:
          distribution: '<distribution>'
          java-version: 17
      - run: java HelloWorldApp.java

      - name: Sonar scan
        env:
          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
        run: ./gradlew build sonar --info
working-directory: ./my-app/HelloWorldFunction

Justification:
i dont know how to use it
Are you willing to submit a PR?

Hello @angold5
Thank you for reporting this issue, We will investigate it and come back to you as soon as we have some information.

repo: actions/setup-java


text:
Java build breakage with MacOS 10.14 (version: '20210413.1')

Description
After yesterday's upgrade to 20210413.1 all our java builds have started failing with 'net.rubygrapefruit.platform.NativeException: Could not query file systems: could not determine file system attributes (errno 5: Input/output error)'
We suspect that the Gradle 7.0 was the reason of the failure, the previous image version 20210405.1 where the build can finish, has Gradle 6.8.3
Error messages
2021-04-16T08:35:48.1371460Z To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.0/userguide/gradle_daemon.html#sec:disabling_the_daemon.
2021-04-16T08:35:48.1431220Z Daemon will be stopped at the end of the build
2021-04-16T08:35:48.1436420Z > Task :spotlessJava UP-TO-DATE
2021-04-16T08:35:48.1486680Z > Task :compileJava UP-TO-DATE
2021-04-16T08:35:48.1538510Z > Task :processResources NO-SOURCE
2021-04-16T08:35:48.1619970Z > Task :classes UP-TO-DATE
2021-04-16T08:35:48.1644260Z > Task :generatePomFileForMavenPublication
2021-04-16T08:35:48.1688500Z > Task :allJar
2021-04-16T08:35:48.1722270Z > Task :javadoc
2021-04-16T08:35:48.1793070Z > Task :javadocJar
2021-04-16T08:35:48.1815330Z > Task :sourcesJar
2021-04-16T08:35:48.1836160Z > Task :cmakeBuild
2021-04-16T08:35:48.1841610Z
2021-04-16T08:35:48.1903990Z BUILD SUCCESSFUL in 52s
2021-04-16T08:35:48.1940010Z 8 actionable tasks: 6 executed, 2 up-to-date
2021-04-16T08:35:48.1953310Z Unable to watch the file system for changes
2021-04-16T08:35:48.2003490Z net.rubygrapefruit.platform.NativeException: Could not query file systems: could not determine file system attributes (errno 5: Input/output error)
2021-04-16T08:35:48.2032890Z 	at net.rubygrapefruit.platform.internal.PosixFileSystems.getFileSystems(PosixFileSystems.java:32)
2021-04-16T08:35:48.2043290Z 	at org.gradle.internal.watch.vfs.impl.DefaultWatchableFileSystemDetector.detectUnsupportedFileSystems(DefaultWatchableFileSystemDetector.java:64)
2021-04-16T08:35:48.2137430Z 	at org.gradle.internal.watch.registry.impl.WatchableHierarchies.removeUnwatchableFileSystems(WatchableHierarchies.java:113)
2021-04-16T08:35:48.2147300Z 	at org.gradle.internal.watch.registry.impl.WatchableHierarchies.removeUnwatchableContent(WatchableHierarchies.java:82)
2021-04-16T08:35:48.2242030Z 	at org.gradle.internal.watch.registry.impl.HierarchicalFileWatcherUpdater.buildFinished(HierarchicalFileWatcherUpdater.java:98)
2021-04-16T08:35:48.2255710Z 	at org.gradle.internal.watch.registry.impl.DefaultFileWatcherRegistry.buildFinished(DefaultFileWatcherRegistry.java:146)
2021-04-16T08:35:48.2343290Z 	at org.gradle.internal.watch.vfs.impl.WatchingVirtualFileSystem$2.lambda$call$0(WatchingVirtualFileSystem.java:199)
2021-04-16T08:35:48.2363220Z 	at org.gradle.internal.watch.vfs.impl.WatchingVirtualFileSystem.withWatcherChangeErrorHandling(WatchingVirtualFileSystem.java:320)
2021-04-16T08:35:48.2450250Z 	at org.gradle.internal.watch.vfs.impl.WatchingVirtualFileSystem.access$1000(WatchingVirtualFileSystem.java:53)
2021-04-16T08:35:48.2458140Z 	at org.gradle.internal.watch.vfs.impl.WatchingVirtualFileSystem$2.call(WatchingVirtualFileSystem.java:199)
2021-04-16T08:35:48.2473980Z 	at org.gradle.internal.watch.vfs.impl.WatchingVirtualFileSystem$2.call(WatchingVirtualFileSystem.java:179)
2021-04-16T08:35:48.2570700Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
2021-04-16T08:35:48.2575270Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
2021-04-16T08:35:48.2581160Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
2021-04-16T08:35:48.2673670Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
2021-04-16T08:35:48.2678830Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
2021-04-16T08:35:48.2694480Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
2021-04-16T08:35:48.2781270Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
2021-04-16T08:35:48.2800710Z 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
2021-04-16T08:35:48.2832450Z 	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
2021-04-16T08:35:48.2883710Z 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
2021-04-16T08:35:48.2903120Z 	at org.gradle.internal.watch.vfs.impl.WatchingVirtualFileSystem.lambda$beforeBuildFinished$5(WatchingVirtualFileSystem.java:179)
2021-04-16T08:35:48.2988250Z 	at org.gradle.internal.vfs.impl.VfsRootReference.update(VfsRootReference.java:40)
2021-04-16T08:35:48.3004240Z 	at org.gradle.internal.watch.vfs.impl.WatchingVirtualFileSystem.beforeBuildFinished(WatchingVirtualFileSystem.java:179)
2021-04-16T08:35:48.3048980Z 	at org.gradle.tooling.internal.provider.FileSystemWatchingBuildActionRunner.run(FileSystemWatchingBuildActionRunner.java:93)
2021-04-16T08:35:48.3106400Z 	at org.gradle.launcher.exec.BuildCompletionNotifyingBuildActionRunner.run(BuildCompletionNotifyingBuildActionRunner.java:41)
2021-04-16T08:35:48.3123240Z 	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:49)
2021-04-16T08:35:48.3151730Z 	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:44)
2021-04-16T08:35:48.3155410Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
2021-04-16T08:35:48.3209240Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
2021-04-16T08:35:48.3255190Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
2021-04-16T08:35:48.3318280Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
2021-04-16T08:35:48.3326970Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
2021-04-16T08:35:48.3358950Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
2021-04-16T08:35:48.3425390Z 	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
2021-04-16T08:35:48.3462970Z 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
2021-04-16T08:35:48.3465040Z 	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
2021-04-16T08:35:48.3467560Z 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
2021-04-16T08:35:48.3533510Z 	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:44)
2021-04-16T08:35:48.3551170Z 	at org.gradle.launcher.exec.InProcessBuildActionExecuter.lambda$execute$0(InProcessBuildActionExecuter.java:59)
2021-04-16T08:35:48.3569000Z 	at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:86)
2021-04-16T08:35:48.3638020Z 	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:58)
2021-04-16T08:35:48.3651670Z 	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30)
2021-04-16T08:35:48.3679880Z 	at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.lambda$execute$0(BuildTreeScopeLifecycleBuildActionExecuter.java:34)
2021-04-16T08:35:48.3695710Z 	at org.gradle.internal.buildtree.BuildTreeState.run(BuildTreeState.java:53)
2021-04-16T08:35:48.3747070Z 	at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.execute(BuildTreeScopeLifecycleBuildActionExecuter.java:33)
2021-04-16T08:35:48.3762200Z 	at org.gradle.launcher.exec.BuildTreeScopeLifecycleBuildActionExecuter.execute(BuildTreeScopeLifecycleBuildActionExecuter.java:28)
2021-04-16T08:35:48.3792970Z 	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:104)
2021-04-16T08:35:48.3858780Z 	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:55)
2021-04-16T08:35:48.3886590Z 	at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:64)
2021-04-16T08:35:48.3895460Z 	at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:37)
2021-04-16T08:35:48.3967910Z 	at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.lambda$execute$0(SessionScopeLifecycleBuildActionExecuter.java:54)
2021-04-16T08:35:48.3999440Z 	at org.gradle.internal.session.BuildSessionState.run(BuildSessionState.java:67)
2021-04-16T08:35:48.4027290Z 	at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.execute(SessionScopeLifecycleBuildActionExecuter.java:50)
2021-04-16T08:35:48.4106640Z 	at org.gradle.tooling.internal.provider.SessionScopeLifecycleBuildActionExecuter.execute(SessionScopeLifecycleBuildActionExecuter.java:36)
2021-04-16T08:35:48.4129890Z 	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36)
2021-04-16T08:35:48.4214720Z 	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25)
2021-04-16T08:35:48.4232410Z 	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:59)
2021-04-16T08:35:48.4250620Z 	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:31)
2021-04-16T08:35:48.4321790Z 	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:58)
2021-04-16T08:35:48.4352560Z 	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:42)
2021-04-16T08:35:48.4426710Z 	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:47)
2021-04-16T08:35:48.4453490Z 	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:31)
2021-04-16T08:35:48.4529940Z 	at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:65)
2021-04-16T08:35:48.4555620Z 	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
2021-04-16T08:35:48.4657300Z 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
2021-04-16T08:35:48.4658830Z 	at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:39)
2021-04-16T08:35:48.4759440Z 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
2021-04-16T08:35:48.4760980Z 	at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:29)
2021-04-16T08:35:48.4861790Z 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
2021-04-16T08:35:48.4962100Z 	at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:35)
2021-04-16T08:35:48.4971830Z 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
2021-04-16T08:35:48.4989530Z 	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:78)
2021-04-16T08:35:48.5073420Z 	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:75)
2021-04-16T08:35:48.5074840Z 	at org.gradle.util.Swapper.swap(Swapper.java:38)
2021-04-16T08:35:48.5080740Z 	at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:75)
2021-04-16T08:35:48.5178220Z 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
2021-04-16T08:35:48.5280440Z 	at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:50)
2021-04-16T08:35:48.5284590Z 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
2021-04-16T08:35:48.5392420Z 	at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:63)
2021-04-16T08:35:48.5480470Z 	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
2021-04-16T08:35:48.5495910Z 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
2021-04-16T08:35:48.5527100Z 	at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:84)
2021-04-16T08:35:48.5598500Z 	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
2021-04-16T08:35:48.5629500Z 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
2021-04-16T08:35:48.5647100Z 	at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:52)
2021-04-16T08:35:48.5660010Z 	at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:297)
2021-04-16T08:35:48.5713560Z 	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
2021-04-16T08:35:48.5731740Z 	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
2021-04-16T08:35:48.5764010Z 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2021-04-16T08:35:48.5816960Z 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2021-04-16T08:35:48.5868190Z 	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
2021-04-16T08:35:48.5939930Z 	at java.base/java.lang.Thread.run(Thread.java:834)
2021-04-16T08:35:48.5971590Z Starting a Gradle Daemon (subsequent builds will be faster)
2021-04-16T08:35:48.6074540Z > Task :preBuild UP-TO-DATE
2021-04-16T08:35:48.6077360Z > Task :preDebugBuild UP-TO-DATE
2021-04-16T08:35:48.6146640Z > Task :compileDebugAidl NO-SOURCE
2021-04-16T08:35:48.6254840Z > Task :compileDebugRenderscript NO-SOURCE
2021-04-16T08:35:48.6357110Z > Task :checkDebugManifest FAILED
2021-04-16T08:35:48.6382380Z
2021-04-16T08:35:48.6400820Z FAILURE: Build failed with an exception.
2021-04-16T08:35:48.6461740Z
2021-04-16T08:35:48.6489530Z * What went wrong:
2021-04-16T08:35:48.6565110Z A problem was found with the configuration of task ':checkDebugManifest' (type 'CheckManifest').
2021-04-16T08:35:48.6628860Z   - Type 'CheckManifest' property 'manifest' has @Input annotation used on property of type 'File'.
2021-04-16T08:35:48.6648760Z
2021-04-16T08:35:48.6677420Z     Reason: A property of type 'File' annotated with @Input cannot determine how to interpret the file.
2021-04-16T08:35:48.6730990Z
2021-04-16T08:35:48.6787760Z     Possible solutions:
2021-04-16T08:35:48.6826050Z       1. Annotate with @InputFile for regular files.
2021-04-16T08:35:48.6838690Z       2. Annotate with @InputDirectory for directories.
2021-04-16T08:35:48.6932880Z       3. If you want to track the path, return File.absolutePath as a String and keep @Input.
2021-04-16T08:35:48.6936450Z
2021-04-16T08:35:48.6941070Z     Please refer to https://docs.gradle.org/7.0/userguide/validation_problems.html#incorrect_use_of_input_annotation for more details about this problem.
2021-04-16T08:35:48.7034500Z
2021-04-16T08:35:48.7037790Z * Try:
2021-04-16T08:35:48.7048000Z Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
2021-04-16T08:35:48.7087750Z
2021-04-16T08:35:48.7138440Z * Get more help at https://help.gradle.org
2021-04-16T08:35:48.7143830Z

Area for Triage:

Java
Question, Bug, or Feature?:

Bug
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019
[X] macOS 10.14

Image version

20210413.1
Expected behavior
Passing building java on MacOS
Actual behavior
java builds have started failing with 'net.rubygrapefruit.platform.NativeException: Could not query file systems: could not determine file system attributes (errno 5: Input/output error)'
Repro steps
A description with steps to reproduce the issue. If your have a public example or repo to share,
please provide the link.
Failure Example, https://dev.azure.com/onnxruntime/onnxruntime/_build/results?buildId=359586&view=logs&j=5bc85223-5fed-55e3-d6db-7543b894f171&t=ab98c327-2cb1-5e11-6f8b-ce6abbe034d3

Is there any way to downgrade in the pipeline run to using Gradle 6.x?

Hi @gwang-msft!
Could you please try the following steps to downgrade gradle in runtime?
wget https://services.gradle.org/distributions/gradle-6.8.3-all.zip
unzip gradle-6.8.3-all.zip
ln -sf $(pwd)/gradle-6.8.3/bin/gradle /usr/local/bin/gradle

@miketimofeev the build passed after adding your steps to downgrade gradle to 6.8.3

@gwang-msft good to hear!
Unfortunately, we can't downgrade the Gradle on the images since our strategy is to install the latest version. Please consider using gradlew to stick to the exact Gradle version for your project https://docs.gradle.org/current/userguide/gradle_wrapper.html
I'm going to close the issue, but feel free to contact us if you have any concerns.
Thank you!

@miketimofeev
I tried Gradle wrapper to use Gradle version 6.8.3
Here is something interesting, even running gradle wrapper will throw the exception, even it will not cause the pipeline to fail, you may want to reconsider downgrade the gradle until it is more stable? Since gradle 7.0 is newly released 7 days ago.
https://dev.azure.com/onnxruntime/onnxruntime/_build/results?buildId=359900&view=logs&j=5bc85223-5fed-55e3-d6db-7543b894f171&t=a7a8be79-50fb-5d0f-16a9-1440a41df19b
https://dev.azure.com/onnxruntime/2a773b67-e88b-4c7f-9fc0-87d31fea8ef2/_apis/build/builds/359900/logs/10

authors: gwang-msft miketimofeev

repo: actions/virtual-environments


text:
Fail to create the Windows2019 image

Description
Fail to cerate the Windows2019 image on a new created VM(clean).
Unsuccessful exit code returned by the installation process: 2003.
Steps follow on this:https://github.com/actions/virtual-environments/blob/main/docs/create-image-and-azure-resources.md
Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[X] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Windows Server 2019
Is it regression?
No response
Expected behavior
No response
Actual behavior
No response
Repro steps
Local machine or Azure VM can be used as a build agent.
Download packer from https://www.packer.io/downloads, or install it via Chocolately.
choco install packer
Install the Azure Az PowerShell module - https://docs.microsoft.com/en-us/powershell/azure/install-az-ps.
Install-Module -Name Az -Repository PSGallery -Force
Install Azure CLI - https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-windows?view=azure-cli-latest&tabs=azure-cli.
Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi
Download Virtual-Environments repository.
Set-Location c:
git clone https://github.com/actions/virtual-environments.git
Import GenerateResourcesAndImage script from /helpers folder, and run GenerateResourcesAndImage function via Powershell.
Set-Location C:\virtual-environments
Import-Module .\helpers\GenerateResourcesAndImage.ps1
GenerateResourcesAndImage -SubscriptionId {YourSubscriptionId} -ResourceGroupName "myTestResourceGroup" -ImageGenerationRepositoryRoot "$pwd" -ImageType Ubuntu1604 -AzureLocation "East US"
Where:
•	SubscriptionId - The Azure subscription Id where resources will be created.
•	ResourceGroupName - The Azure resource group name where the Azure resources will be created.
•	ImageGenerationRepositoryRoot - The root path of the image generation repository source.
•	ImageType - The type of the image being generated. Valid options are: "Windows2016", "Windows2019", "Ubuntu1604", "Ubuntu1804", "Ubuntu2004".
•	AzureLocation - The location of the resources being created in Azure. For example "East US".
The function automatically creates all required Azure resources and kicks off packer image generation for the selected image type.
Please, check synopsis of GenerateResourcesAndImage for details about non-mandatory parameters.

Hello @jiaweis2021!
Could you please the entire build log of yours?

@mikhailkoliada Hello, this image is created by CMD, this is the entire log. Not build in DevOps pipeline.

@jiaweis2021 please provide packer log. You can enable it as described here if it is not
https://www.packer.io/docs/debugging#debugging-packer

@mikhailkoliada Hello, this image is created by CMD, this is the entire log. Not build in DevOps pipeline.

It looks like you forgot to modify your GenerateResourcesAndImage.
You're trying to build Ubuntu 16.04 instead of Windows Server 2019.

@jiaweis2021, I am planning to close this thread. If you have any concerns feel free to open one.

authors: ItzLevvie al-cheb jiaweis2021 miketimofeev mikhailkoliada


text:
Initialize Visual Studio Experimental Instance on the correct user

The Visual Studio Experimental Instance initialization needs to happen in the user where the GA workflow will run (runneradmin), not on the installer user which is currently the case due to https://github.com/actions/virtual-environments/blob/c161416ac88327a4362f4fb8b3413fea4fe9289b/images/win/windows2022.json#L165.
See my previous pull request https://github.com/actions/virtual-environments/pull/4143 why this is needed.

@josetr Thank you for your contribution! The changes will be deployed next week.

authors: josetr miketimofeev


text:
pub.dev page says that package has Mac OS support

Why does it say so?
https://pub.dev/packages/activout_firebase_options_selector

Why shouldn't it? all of the firebase packages work on Mac OS
https://pub.dev/packages?q=firebase

Hittar dock inget om det på https://firebase.google.com/docs :)

authors: GabrielHilding twogood


text:
next app does not build

Build error occurred
Error: Export encountered errors on following paths:
/
/404
/500
/components/WeatherTable
/forecast
/login
at /usr/lib/node_modules/next/dist/export/index.js:487:19
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Span.traceAsyncFn (/usr/lib/node_modules/next/dist/telemetry/trace/trace.js:60:20)
at async /usr/lib/node_modules/next/dist/build/index.js:833:17
at async Span.traceAsyncFn (/usr/lib/node_modules/next/dist/telemetry/trace/trace.js:60:20)
at async /usr/lib/node_modules/next/dist/build/index.js:707:13
at async Span.traceAsyncFn (/usr/lib/node_modules/next/dist/telemetry/trace/trace.js:60:20)
at async Object.build [as default] (/usr/lib/node_modules/next/dist/build/index.js:77:25)

npm run build output:
> react-next-app@0.1.0 build
> next build

info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info  - Checking validity of types
error - ESLint: Failed to load config "next/babel" to extend from. Referenced from: D:\Files\Front-End\Study\hackademy\hackademy-week-5\react-next-app\.eslintrc.json
info  - Using external babel configuration from D:\Files\Front-End\Study\hackademy\hackademy-week-5\react-next-app\.babelrc
info  - Creating an optimized production build
info  - Compiled successfully
info  - Collecting page data
info  - Generating static pages (6/6)
info  - Finalizing page optimization

Is the problem workspace specific?

authors: actpohabtNS dnfd


text:
⚠ Processors has degraded performance

In feb1288, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 49 ms

Resolved: Processors performance has improved in b31bcde.

repo: acumenlabs/status-page


text:
⚠ Processors has degraded performance

In d28c7aa, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 62 ms

Resolved: Processors performance has improved in 628ab3f.


text:
⚠ Processors has degraded performance

In 6a1abf3, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 78 ms

Resolved: Processors performance has improved in 3d073c8.


text:
Switch to Manifest v3

https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3

Implemented in PR #870

authors: AlexWayfer adam-p amacfie

repo: adam-p/markdown-here


text:
Additional warning type checks.

Description
Hey @adamchainz — not sure if this is a feature request per se... more a query... 🙂
See https://forum.djangoproject.com/t/deprecation-of-default-file-storage-can-we-easen-the-migration/34284/20
Looking at Tim's objections, I don't really disagree. There IS a certain Grrr to adding a forever warning there to Django core. (The trade-off being trying to help folks dropping off end of the deprecation period of course, so it's not monotonic.)
I wonder if having a home for such in django-upgrade might fit with the scope of the package? It's not fixers per se, but Maybe you missed this...?
How does that feel to you?
I would like to push for django-upgrade to become a featured or even official package during the next cycle. If that comes to pass  — and using django-upgrade is just part of what folks do — then such warnings Not being in Core™ (for whatever that means) wouldn't be such an issue.
🤔

It feels okay. I think we could add a "linter" pass after applying fixers, and have a few built-in checks like this "old settings" one, and for other outdated constructs. For example, last year, I saw a model class with an internal class Admin to configure the admin, which dates back to Django <1, IIRC).
Setting file detection is heuristic, this being an AST-based tool, so it won't catch all the cases that a system check would. For example, for settings files without the word "settings" in their path or for alternative settings structures like django-configurations.
I would still prefer to see this in core myself, but happy to implement here instead. There's definitely an argument that folks skipping the recommended path and jumping multiple Django versions are more likely to reach for django-upgrade, so it's not such a bad home.

Thanks for the reply @adamchainz.

… so it won't catch all the cases that a system check would.

That's a good point. 🤔
OK, let's just hold this as a possibility, pending the discussion around the Django PR.
🤞

I'll close as Not Planned for now. We can always reopen if needed.

authors: adamchainz carltongibson

repo: adamchainz/django-upgrade


text:
Is it possible to divide windows with specified width and length?

Hi, Adam
I appreciate for your work on this useful tools.
While using this toolbox, I found that sometimes I need to divide images with specified width and length or specified number of windows.
Does this toolbox include related functions to do these work ?
If not, I would like to make a pull request for it.

At the moment windows can only be generated by setting a maximum window size, and the window generation logic automatically adapts to the dataset size in order to achieve 100% coverage. If there are use cases where the specific window size or count is important and you'd like to contribute an appropriate implementation then I'd certainly be happy to accept a pull request. My suggestion would be to add one or more new functions at the bottom of SlidingWindow.py with appropriate names (e.g. generateForWindowSize(), generateForNumberOfWindows(), etc.)

@adamrehn
I have just created pull request adding the functions that I mentioned. As far as I tested, the functions had no errors, but I think you may want to fix few lines so that it can look clean.
If any error occurs, please let me know about it.
Thanks!

Thanks for contributing your implementation in #4, I've now merged that into the project. Looking through your code, there was more duplication than strictly necessary, so I've refactored it in commit c3e3481, which adds some small non-breaking API changes to the existing functions and streamlines the new functions. I've also renamed the new functions to generateRectanglarWindows() and generateForNumberOfWindows() to make their purpose a little clearer, and updated their docstrings to provide a more detailed description of their use and parameters.

authors: StringBottle adamrehn

repo: adamrehn/slidingwindow


text:
appointment model: clean() and save() improvements

because of the >= in if self.start_time >= self.end_time:, the if self.start_time == self.end_time: can never be reached
ValueError is not the right error to raise, It's ValidationError. Raising ValueError throws a 500
The date field already checks for date validity

Nit: all the checks in the save() should be removed, they are already done in clean() (except one but I can move it into clean). In Django, all checks are done clean, and not in save. The way it's done is contrary to the django philosophy (yes theoretically a silly dev could call save with invalid data because he did not call clean()` but django is clear on it:  that's his fault).
If you are OK with this proposal, I will do this.

@deronnax, you're right about everything said. I merged the pull request and the change wil be in the next release. Thanks a lot for that.

Cool, thank you. Sorry, I did not notice I broke tests because they did not run on the MR. But I will know for next time.

authors: adamspd deronnax

repo: adamspd/django-appointment


text:
🛑 relay.c.im is down

In 1323ff6, relay.c.im (https://relay.c.im/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.c.im is back up in ba2bddd.


text:
🛑 mastodon-relay.moew.science is down

In fb5ab25, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mastodon-relay.moew.science is back up in 249ad19 after 1 hour, 42 minutes.


text:
🛑 relay.c.im is down

In 6604abb, relay.c.im (https://relay.c.im/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.c.im is back up in 8da8b9a.


text:
🛑 relay.pissdichal.de is down

In 94caa5b, relay.pissdichal.de (https://relay.pissdichal.de/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.pissdichal.de is back up in c83d59b.


text:
🛑 IRC SSL is down

In 52c2841, IRC SSL ($SECRET_SITE_IRC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: IRC SSL is back up in 69e18cd after 16 minutes.


text:
update subtechniques

also fixing other mistakes

LGTM. Thanks a lot!

authors: SaschaDietsch adanalvarez

repo: adanalvarez/TrailDiscover


text:
IndexError: pop from empty list

Hi,
I tried to crawl texts from a list of 100 URLs experimentally. Every time it's stopped at the 40th with the error as follows:
$ trafilatura --inputfile linkliste-gefiltert.txt --outputdir ausgabe/ --backup-dir html-quellen/
Traceback (most recent call last):
  File "/home/anaconda3/bin/trafilatura", line 8, in <module>
    sys.exit(main())
  File "/home/anaconda3/lib/python3.7/site-packages/trafilatura/cli.py", line 151, in main
    process_args(args)
  File "/home/anaconda3/lib/python3.7/site-packages/trafilatura/cli.py", line 166, in process_args
    url_processing_pipeline(args, input_urls, SLEEP_TIME)
  File "/home/anaconda3/lib/python3.7/site-packages/trafilatura/cli_utils.py", line 306, in url_processing_pipeline
    multi_threaded_processing(domain_dict, args, sleeptime, counter)
  File "/home/anaconda3/lib/python3.7/site-packages/trafilatura/cli_utils.py", line 254, in multi_threaded_processing
    bufferlist.append(domain_dict[domain].pop())
IndexError: pop from empty list

Anyone also run into this problem?
My list is like this (a subset of corona-corpus at DWDS):
http://schmid.welt.de/2020/03/18/corona-gesammelte-apercus-3
http://schmid.welt.de/2020/04/04/krieg-und-virus-corona-apercus-5
http://www.bmz.de/de/themen/corona/index.html
http://www.chiemgauseiten.de/2020/04/15/zirkus-corona-tag-33-wann-wird-s-mal-wieder-richtig-schule
http://www.chiemgauseiten.de/2020/04/19/zirkus-corona-tag-38-der-hasenpalast
http://www.chiemgauseiten.de/2020/04/23/zirkus-corona-tag-42-die-hoffnungs-profis
http://www.chiemgauseiten.de/2020/04/27/zirkus-corona-tag-45-leo-allein-zu-haus
http://www.chiemgauseiten.de/2020/05/01/zirkus-corona-tag-50-das-große-wiedersehen
http://www.chiemgauseiten.de/2020/05/04/zirkus-corona-tag-53-das-corona-paradox
http://www.chiemgauseiten.de/2020/05/08/zirkus-corona-tag-57-tage-der-befreiung
http://www.chiemgauseiten.de/2020/05/11/zirkus-corona-tag-60-zwischenzeit
http://www.klimareporter.de
http://www.klimareporter.de/deutschland/der-corona-rollback
http://www.klimareporter.de/finanzen-wirtschaft/finanzhilfen-nur-mit-1-5-grad-standards
http://www.klimareporter.de/gesellschaft/der-klimawandel-ein-planetarisches-virus
http://www.klimareporter.de/protest/das-klima-in-der-hand-der-aktionaer-innen
http://www.klimareporter.de/protest/die-vermeintlich-unpolitischen-krisen
http://www.klimareporter.de/verkehr/corona-zwingt-luftfahrt-zu-mehr-klimaschutz
http://www.liebesleben.de/corona/corona-hiv-und-andere-sti
http://www.liebesleben.de/corona/corona-sexualitaet-und-wohlbefinden
http://www.liebesleben.de/corona/corona-und-beziehungen
http://www.liebesleben.de/corona/corona-und-dating
http://www.liebesleben.de/corona/corona-und-fragen-zu-sexualitaet
http://www.liebesleben.de/corona/corona-und-sex
http://www.literaturhaus-graz.at/die-corona-tagebuecher-1
http://www.literaturhaus-graz.at/die-corona-tagebuecher-teil-2
http://www.literaturhaus-graz.at/die-corona-tagebuecher-teil-3
http://www.literaturhaus-graz.at/die-corona-tagebuecher-teil-5
http://www.literaturhaus-graz.at/die-corona-tagebuecher-teil-6
http://www.literaturhaus-graz.at/ie-corona-tagebuecher-teil-8
http://www.marlenestreeruwitz.at/werk/so-ist-die-welt-geworden
http://www.ortheil-blog.de/2020/04/15/exit-und-zwar-sofort
http://www.ortheil-blog.de/2020/04/20/stationen-eines-corona-tages-1
http://www.ortheil-blog.de/2020/04/21/stationen-eines-coronatages-fuer-kinder
http://www.ortheil-blog.de/2020/05/02/nachrichtenueberdruss
http://www.tichyseinblick.de/daili-es-sentials/aemter-ignorierten-empfehlungen-der-who-und-einer-hygiene-kommission
http://www.tichyseinblick.de/daili-es-sentials/agitation-oder-trost-muezzine-rufen-zum-gebet
http://www.tichyseinblick.de/daili-es-sentials/altmaier-sollte-etwas-tun-oder-den-mund-halten
http://www.tichyseinblick.de/daili-es-sentials/ausstieg-aus-der-quarantaene-nach-ostern-neue-daten-stuetzen-die-forderung
http://www.tichyseinblick.de/daili-es-sentials/berlin-kirche-nein-revolutionaere-1-mai-demo-ja
http://www.tichyseinblick.de/daili-es-sentials/bund-arbeitet-an-impfpflicht-durch-die-hintertuer
http://www.tichyseinblick.de/daili-es-sentials/cdu-verschiebt-parteitag-auf-unbestimmte-zeit
http://www.tichyseinblick.de/daili-es-sentials/china-coronavirus-abschottung
http://www.tichyseinblick.de/daili-es-sentials/corona-abstimmung-buerger-protestieren-trotz-demonstrationsverbot
http://www.tichyseinblick.de/daili-es-sentials/corona-bringts-an-den-tag-deutschland-ohne-mass-und-ordnung
http://www.tichyseinblick.de/daili-es-sentials/corona-ein-kurzer-laendervergleich
http://www.tichyseinblick.de/daili-es-sentials/corona-hilfe-fuer-nachbarn-solidaritaet-ist-eine-einbahnstrasse
http://www.tichyseinblick.de/daili-es-sentials/corona-in-suedostasien-wie-thailand-auf-die-pandemie-reagiert
http://www.tichyseinblick.de/daili-es-sentials/corona-kommunikation-schlechte-noten-fuer-bundesministerien
http://www.tichyseinblick.de/daili-es-sentials/corona-schattengesetze
http://www.tichyseinblick.de/daili-es-sentials/corona-und-co2-jetzt-kommen-die-engfuehrer
http://www.tichyseinblick.de/daili-es-sentials/corona-update-3-mai
http://www.tichyseinblick.de/daili-es-sentials/corona-update-um-18-april-die-maskenpflicht-kommt
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-1-mai-kein-tanz-dafuer-presseerklaerungen
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-10-april-eine-studie-aus-dem-kreis-heinsberg
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-12-april-die-gier-der-vermoegenden
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-14-april-anwaeltin-bahner-in-psychiatrie
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-15-april-die-leopoldina-und-die-wirtschaft
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-16-april-die-bundesregierung-fordert-zum-maskentragen-auf
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-2-mai-gerichte-werden-aktiv
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-20-april-die-lockerungen-im-ueberblick
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-22-april-spahn-fordert-toleranz-fuer-fehler-der-politik
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-24-april-eine-merkelsche-regierungserklaerung
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-25-april
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-26-april-china-uebt-druck-auf-die-eu-aus
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-27-april-spd-will-recht-auf-homeoffice-und-strichweibchen
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-27-oktober-das-parlament-stiehlt-sich-aus-der-verantwortung
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-29-april-die-bundesregierung-bekaempft-ihre-eigenen-fake-news
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-30-maerz-soziale-folgen-draengen-nach-vorne
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-4-april-wie-raus-aus-dem-kontaktverbot
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-8-april-mundschutzmasken-aber-woher
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-1-april-flacht-die-kurve-ab
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-19-maerz
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-20-maerz-anstieg-der-infektionen
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-23-maerz-deutsche-amtsstuben-und-italienische-aerzte
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-26-maerz-wer-wird-behandelt-wer-nicht
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-27-maerz
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-28-maerz-das-rki-taucht-ab
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-29-maerz-ein-vertrauliches-strategiepapier
http://www.tichyseinblick.de/daili-es-sentials/corona-update-zum-morgen-des-4-april-beschlagnahmte-schutzmasken-und-hoffnung-fuer-italien
http://www.tichyseinblick.de/daili-es-sentials/corona-vermoegensteuer-zwei-reichen-solis-und-eine-mauer-fuer-reiche
http://www.tichyseinblick.de/daili-es-sentials/corona-verschleiert-spanien-das-ausmass-der-pandemie
http://www.tichyseinblick.de/daili-es-sentials/corona-virus-ueberlebensplan-bis-zum-impfstoff
http://www.tichyseinblick.de/daili-es-sentials/coronavirus-in-deutschland
http://www.tichyseinblick.de/daili-es-sentials/coronavirus-in-europa-angekommen
http://www.tichyseinblick.de/daili-es-sentials/coronavirus-oesterreich-ist-im-krisenmanagement-deutschland-weit-voraus
http://www.tichyseinblick.de/daili-es-sentials/coronavirus-was-wir-von-der-spanischen-grippe-lernen-koennen
http://www.tichyseinblick.de/daili-es-sentials/covid-19-warum-die-aktuelle-sterberate-wenig-aussagt
http://www.tichyseinblick.de/daili-es-sentials/der-corona-wortschatz
http://www.tichyseinblick.de/daili-es-sentials/deutschland-war-auf-corona-vorbereitet-aber-nur-auf-dem-papier
http://www.tichyseinblick.de/daili-es-sentials/die-hoffnung-stirbt-zuerst-merkel-zieht-neuen-corona-gipfel-vor
http://www.tichyseinblick.de/daili-es-sentials/dritter-fdp-bundestagsabgeordneter-positiv-auf-covid-19-getestet
http://www.tichyseinblick.de/daili-es-sentials/ein-nachtrag-zu-systemtest-coronavirus-berlin-redet-wien-und-andere-handeln-un-und-eu-finden-nicht-statt
http://www.tichyseinblick.de/daili-es-sentials/endlich-die-fdp-wacht-aus-ihrem-tiefschlaf-auf
http://www.tichyseinblick.de/daili-es-sentials/engtanz-in-zeiten-von-corona
http://www.tichyseinblick.de/daili-es-sentials/erste-ergebnisse-der-heinsberg-studie-koennen-die-einschraenkungen-gelockert-werden
http://www.tichyseinblick.de/daili-es-sentials/fdp-abgeordneter-marcel-luthe-wir-oeffnen-die-buechse-der-pandora
http://www.tichyseinblick.de/daili-es-sentials/fluege-aus-dem-iran-kommen-weiter-in-deutschland-an
http://www.tichyseinblick.de/daili-es-sentials/hamburg-party-senator-bricht-corona-regeln-der-eigenen-behoerde
http://www.tichyseinblick.de/daili-es-sentials/hamsterkaeufe-sorge-vor-coronavirus-und-leere-supermarktregale

Thank for the bug report, there was indeed on a problem in URL list processing, just fixed in f86e4606b32dc9e9de56f181e428b4dc1b06a4f4.
The downloads should now work if you use the newest version from the repository:
pip install -U git+https://github.com/adbar/trafilatura.git

It works now! Thank you!
Another thought: will it be possible to crawl the missing websites from Internet Archive? I'm considering whether it's a good idea to archive all pages on Internet Archive automatically at the stage when crawling them for the first time. This will make it possible to rebuild exactly the same corpus. Just a thought, don't take it so seriously ;)

Good idea, I'll think about fetching dead links directly from archive.org.
Considering the interaction with web archives several Python libraries
are of interest:

https://github.com/jjjake/internetarchive
https://github.com/webrecorder/pywb
https://github.com/oduwsdl/archivenow
https://github.com/pastpages/archiveis
https://github.com/pastpages/savepagenow
https://github.com/agude/wayback-machine-archiver

Referenced in #40, closing this issue for now.

authors: adbar t-duan

repo: adbar/trafilatura


text:
Encoding and blank list filtering

I have added some logic to xml.py and utils.py, which helps with filtering unusual encodings and blank tables. This could help with improving the accuracy of the application.

Hi @immortal-autumn, apparently you didn't use the latest version of the repository or didn't perform a merge before sending your PR. This makes your actual changes difficult to spot...

If I understand correctly you added two regexes in order to better filter the output?
Can it be that you added an evaluation file but there is no corresponding evaluation?

Codecov Report

Merging #198 (5fe222f) into master (146506a) will decrease coverage by 0.35%.
The diff coverage is 85.71%.

:exclamation: Current head 5fe222f differs from pull request most recent head dab59df. Consider uploading reports for the commit dab59df to get more accurate results

@@            Coverage Diff             @@
##           master     #198      +/-   ##
==========================================
- Coverage   95.86%   95.50%   -0.36%
==========================================
  Files          20       21       +1
  Lines        3044     3069      +25
==========================================
+ Hits         2918     2931      +13
- Misses        126      138      +12

Impacted Files
Coverage Δ

evaluation_benchmark_ds.py
0.00% <0.00%> (ø)

trafilatura/utils.py
97.87% <100.00%> (+0.09%)
:arrow_up:

trafilatura/xml.py
97.56% <100.00%> (+0.04%)
: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 146506a...dab59df. Read the comment docs.

Oh the evaluation file I added is for the self-evaluation use, I forgot to remove that sorry lol
The modification happens in the last three commits, I am actually not sure about why there are a number of commits here.

Hi @immortal-autumn, thanks for the feedback, I'm going to have a look at the potential improvements when I find the time.

Hi @immortal-autumn, now I looked at it and I don't understand: The characters you wish to remove are already accounted for. The ideographic space character in particular (\u3000) is already handled here:
https://github.com/adbar/trafilatura/blob/146506a2a18e5ca99ee8cd9a5779cc9f137697aa/trafilatura/utils.py#L44
Thus I don't have the impression that your PR brings anything. Unless you can name a case in which extraction improves with it, I will discard the PR.

authors: adbar codecov-commenter immortal-autumn


text:
Feral Druid getting lua errors

1x NerdPack-Trip\conditions.lua:182: attempt to call field 'UnitDot' (a nil value)
NerdPack-Trip\conditions.lua:182: in function <NerdPack-Trip\conditions.lua:181>
NerdPack\system\dsl.lua:113: in function <NerdPack\system\dsl.lua:89>
(tail call): ?
NerdPack\system\dsl.lua:141: in function <NerdPack\system\dsl.lua:137>
(tail call): ?
NerdPack\system\dsl.lua:132: in function <NerdPack\system\dsl.lua:119>
(tail call): ?
NerdPack\system\dsl.lua:47: in function <NerdPack\system\dsl.lua:45>
(tail call): ?
NerdPack\system\parser.lua:119: in function func' NerdPack\system\parser.lua:101: in function <NerdPack\system\parser.lua:93> (tail call): ? NerdPack\system\parser.lua:111: in function func'
NerdPack\system\parser.lua:101: in function <NerdPack\system\parser.lua:93>
(tail call): ?
NerdPack\system\parser.lua:111: in function `func'
NerdPack\system\parser.lua:101: in function <NerdPack\system\parser.lua:93>
(tail call): ?
NerdPack\system\parser.lua:195: in function <NerdPack\system\parser.lua:180>
SharedXML\C_TimerAugment.lua:16: in function <SharedXML\C_TimerAugment.lua:14>
Locals:
InCombatSkipped

The error is not with my AddOn.
If you read the error-message you'll notice: NerdPack-Trip
Seems to be having an issue with: conditions.lua at line 181.
Trip has to fix this problem, or his AddOn has to be disabled to avoid this error.

TY for that info I thought I had disabled it but I guess it was not disabled it. thank you for info. Im new at reading Lua errors so sorry


text:
backlog milestone

Please walk through the following steps for reporting an issue about AMP:

Please ask general questions about AMP over on stackoverflow under the AMP HTML tag: http://stackoverflow.com/questions/tagged/amp-html
Please ask/post questions/problems related to Google Search in Google's AMP forum: https://goo.gl/utQ1KZ

Short description of your issue:
Start by deleting everything above this including this sentence :)
How do we reproduce the issue?
Please post a public URL and ideally post a reduced test case. E.g. on jsbin.com that exhibits only your issue and nothing else.

Step 1 to reproduce
Step 2 to reproduce
…

What browsers are affected?
All browsers? Some specific browser? What device type?
Which AMP version is affected?
Is this a new issue? Or was it always broken? Paste your AMP version. You can find it in the browser dev tools.

This issue doesn/t have a categorywhich makes it harder for us to keep track of it. @[person] please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it.null please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it.null please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it.null please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

This issue doesn't have a category which makes it harder for us to keep track of it. Please add an appropriate category.

repo: adelinamart/amphtml


text:
fopen() Error

fopen("Fn ft" ...) - i.e. without the fm causes a freeze/loop

Fixed in F0024


text:
Window Cover

Hello
I have a problem with the cover object.
I have javascript errors when I select a cover object and a window object:
On card:
Finished with errors: check the console log
On console:
Uncaught Error:
_onLoaded3DMaterials http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2297
load http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2191
load http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2191
floor3d-card.js:2297:3876
_onLoaded3DMaterials http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2297
load http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2191
load http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2191
Uncaught Error:
_onLoaded3DMaterials http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2297
load http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2191
load http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2191
floor3d-card.js:2297:3876
_onLoaded3DMaterials http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2297
load http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2191
load http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2191
Uncaught TypeError: this._controls is undefined
rerender http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:2248
_config_changed http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:568
handleEvent http://192.168.0.10:8123/local/community/floor3d-card/floor3d-card.js:17
Maybe I'm doing something wrong, but I can't find a guide describing all the functions of the card anywhere

Hello @ozzy071988 , the most complete guide is in the welcome page of the githubn repository (here https://github.com/adizanni/floor3d-card/blob/master/README.md).
The cover entity is not always working fine, it depends on how the cover object is composed in SweetHome3d. Please copy paste your yaml configuration and, if possible, your .obj file or sh3d file

Here is my YAML and zip
MGOBJ2.zip
`type: custom:floor3d-card
path: /local/obj/
name: Plan parteru
shadow: 'yes'
globalLightPower: '0.48'
header: 'yes'
camera_position:
x: 254.83245408277153
'y': 1037.7126954855405
z: 822.2355365053763
camera_rotate:
x: -0.9864130642131598
'y': 0.1057507127130396
z: 0.15824471707595825
camera_target:
x: 118.49928676985411
'y': -33.5313738406396
z: 113.65976377583088
zoom_areas: []
overlay: 'yes'
backgroundColor: green
overlay_bgcolor: blue
overlay_width: '0'
overlay_height: '0'
mtlfile: mg.mtl
objfile: mg.obj
show_axes: 'no'
sky: 'yes'
extralightmode: 'yes'
object_groups: []
entities:

entity: input_boolean.swiatlo1
type3d: light
object_id: fluorescent_strip_fluorescent_strip_fluorescent_tube_427
light:
decay: '2'
distance: '600'
shadow: 'yes'
angle: '180'
vertical_alignment: middle
entity: input_boolean.swiatlo1
type3d: light
object_id: fluorescent_strip_fluorescent_strip_fluorescent_tube_431
light:
decay: '2'
distance: '600'
shadow: 'yes'
angle: '180'
vertical_alignment: middle
entity: input_boolean.swiatlo1
type3d: light
object_id: fluorescent_strip_fluorescent_strip_fluorescent_tube_419
light:
decay: '2'
distance: '600'
shadow: 'yes'
angle: '180'
vertical_alignment: middle
entity: input_boolean.swiatlo1
type3d: light
object_id: fluorescent_strip_fluorescent_strip_fluorescent_tube_423
light:
decay: '2'
distance: '600'
shadow: 'yes'
angle: '180'
vertical_alignment: middle
entity: input_boolean.lampasalon
type3d: light
object_id: '693'
light:
decay: '2'
distance: '600'
shadow: 'yes'
angle: '180'
vertical_alignment: middle
lumens: '1300'
entity: input_boolean.lampakuchnia
type3d: light
object_id: '697'
light:
decay: '2'
distance: '600'
shadow: 'yes'
angle: '180'
vertical_alignment: middle
entity: input_boolean.lampahall
type3d: light
object_id: '701'
light:
decay: '2'
distance: '600'
shadow: 'yes'

`

Hi.
Any ideas related to my problem?

Hello @ozzy071988, I gave you some illusion that I could work at the issue rapidly but I'm having the hardest time to dedicate to the card. I'm now going to holidays and I hope that when back (end of August) I will find time to get back at it (fix the problems and work to v2.0). Hope you will not abandon.

Hi @ozzy071988 ,
You might want to check an issue I have with covers too which was solved using one of the default models.
https://github.com/adizanni/floor3d-card/issues/97
I would recommend you try get it working first with the same model described there, and then try to use another model as most of the issues seem to be related to the 3D model itself, rather than the integration.
Just my 5 cents to try to help :).

authors: adizanni diamant-x ozzy071988


text:
一些广告被其他插件屏蔽导致的异常无视之

兼容uBlock的广告屏蔽

谢谢！

authors: adlered superzmy

repo: adlered/CSDNGreener