text:
Identical yanked errors don't simplify

dependencies = [
    "sentry >=2.0.1,<3",
]

 × No solution found when resolving dependencies:
  ╰─▶ Because only the following versions of sentry are available:
          sentry<=2.0.1
          sentry==2.0.2
          sentry==2.1.0
          sentry==2.1.1
          sentry==2.1.2
          sentry==2.1.3
          sentry==2.2.0
          sentry==2.2.1
          sentry==2.2.2
          sentry==2.2.3
          sentry==2.2.4
          sentry==2.2.5
          sentry==2.3.0
          sentry==2.3.1
          sentry==2.3.2
          sentry==2.4.0
          sentry==2.4.1
          sentry==2.4.2
          sentry==2.4.3
          sentry==2.4.4
          sentry==2.4.5
          sentry==2.4.6
          sentry==2.4.7
          sentry==2.5.0
          sentry==2.5.1
          sentry==2.5.2
          sentry==2.6.0
          sentry==2.6.1
          sentry==2.6.2
          sentry==2.7.0
          sentry==2.8.0
          sentry==2.8.1
          sentry==2.8.2
          sentry==2.9.0
          sentry>=3
      and sentry==2.0.1 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.0.2 cannot be used.
      And because sentry==2.0.2 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.1.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.1.1 cannot be used.
      And because sentry==2.1.1 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.1.2 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.1.3 cannot be used.
      And because sentry==2.1.3 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.2.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.2.1 cannot be used.
      And because sentry==2.2.1 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.2.2 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.2.3 cannot be used.
      And because sentry==2.2.3 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.2.4 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.2.5 cannot be used.
      And because sentry==2.2.5 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.3.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.3.1 cannot be used.
      And because sentry==2.3.1 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.3.2 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.4.0 cannot be used.
      And because sentry==2.4.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.4.1 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.4.2 cannot be used.
      And because sentry==2.4.2 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.4.3 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.4.4 cannot be used.
      And because sentry==2.4.4 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.4.5 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.4.6 cannot be used.
      And because sentry==2.4.6 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.4.7 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.5.0 cannot be used.
      And because sentry==2.5.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.5.1 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.5.2 cannot be used.
      And because sentry==2.5.2 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.6.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.6.1 cannot be used.
      And because sentry==2.6.1 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.6.2 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.7.0 cannot be used.
      And because sentry==2.7.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.8.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.8.1 cannot be used.
      And because sentry==2.8.1 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and sentry==2.8.2 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654), we can
      conclude that sentry>=2.0.1,<2.9.0 cannot be used.
      And because sentry==2.9.0 was yanked (reason: https://github.com/getsentry/self-hosted/issues/1654)
      and github-wikidata-bot depends on sentry>=2.0.1,<3, we can conclude that the requirements are
      unsatisfiable.

Closing as a special case of #1901


text:
No warning is output even if parsing the workspace settings fails.

The implementation has been designed to output a warning if the parsing of the workspace configuration files (pyproject.toml/uv.toml) fails.
https://github.com/astral-sh/uv/blob/main/crates/uv-workspace/src/workspace.rs#L38-L61
However, no warnings are actually output.
pyproject.toml
[project]
name = "sample"
version = "0.0.0"
dependencies = ["ruff"]

[tool.uv.pip]
# originally string type.
index-url = 1

command result
uv pip compile pyproject.toml

Resolved 1 package in 383ms
# This file was autogenerated by uv via the following command:
#    uv pip compile pyproject.toml
ruff==0.4.7
    # via sample (pyproject.toml)

Specifying a URL that does not exist in tool.uv.pip.index-url will cause an error, which suggests that the configuration value itself is being read.
pyproject.toml
[project]
name = "sample"
version = "0.0.0"
dependencies = ["ruff"]

[tool.uv.pip]
# originally string type.
index-url = "http://aaa"

command output
uv pip compile pyproject.toml

⠼ Resolving dependencies...
error: Could not connect, are you offline?
  Caused by: error sending request for url (http://aaa/ruff/)
  Caused by: client error (Connect)
  Caused by: dns error: failed to lookup address information: No address associated with hostname
  Caused by: failed to lookup address information: No address associated with hostname

Thx!

source: gharchive/issue

authors: Di-Is charliermarsh

repo: astral-sh/uv

license_type: permissive

license_source: github-api


text:
Allow Linux SQL CLI users to create projects on the /tmp directory

Describe the bug
As of Astro CLI 1.8, we are having issues mounting /tmp directories on Linux.
Version

SQL CLI 2.2
Astro CLI 1.8

To Reproduce
Use the previously mentioned versions and try to run:
$ ./astro flow init /tmp/xubiru
╭───────────────────── Traceback (most recent call last) ──────────────────────╮
│ /usr/local/lib/python3.9/site-packages/sql_cli/__main__.py:255 in init       │
│                                                                              │
│   252 │                                                                      │
│   253 │   project_dir_absolute = _resolve_project_dir(project_dir)           │
│   254 │   project = Project(project_dir_absolute, airflow_home, airflow_dags │
│ ❱ 255 │   project.initialise()                                               │
│   256 │   rprint("Initialized an Astro SQL project at", project.directory)   │
│   257                                                                        │
│   258                                                                        │
│                                                                              │
│ ╭───────────────────────────────── locals ─────────────────────────────────╮ │
│ │  airflow_dags_folder = None                                              │ │
│ │         airflow_home = None                                              │ │
│ │              Project = <class 'sql_cli.project.Project'>                 │ │
│ │              project = <sql_cli.project.Project object at                │ │
│ │                        0x7f6939cfa310>                                   │ │
│ │          project_dir = PosixPath('/tmp/xubiru')                          │ │
│ │ project_dir_absolute = PosixPath('/tmp/xubiru')                          │ │
│ ╰──────────────────────────────────────────────────────────────────────────╯ │
│                                                                              │
│ /usr/local/lib/python3.9/site-packages/sql_cli/project.py:140 in initialise  │
│                                                                              │
│   137 │   │   """                                                            │
│   138 │   │   Initialise a SQL CLI project, creating expected directories an │
│   139 │   │   """                                                            │
│ ❱ 140 │   │   shutil.copytree(                                               │
│   141 │   │   │   src=BASE_SOURCE_DIR,                                       │
│   142 │   │   │   dst=self.directory,                                        │
│   143 │   │   │   ignore=shutil.ignore_patterns(".gitkeep"),                 │
│                                                                              │
│ ╭───────────────────────── locals ──────────────────────────╮                │
│ │ self = <sql_cli.project.Project object at 0x7f6939cfa310> │                │
│ ╰───────────────────────────────────────────────────────────╯                │
│                                                                              │
│ /usr/local/lib/python3.9/shutil.py:568 in copytree                           │
│                                                                              │
│    565 │   sys.audit("shutil.copytree", src, dst)                            │
│    566 │   with os.scandir(src) as itr:                                      │
│    567 │   │   entries = list(itr)                                           │
│ ❱  568 │   return _copytree(entries=entries, src=src, dst=dst, symlinks=syml │
│    569 │   │   │   │   │    ignore=ignore, copy_function=copy_function,      │
│    570 │   │   │   │   │    ignore_dangling_symlinks=ignore_dangling_symlink │
│    571 │   │   │   │   │    dirs_exist_ok=dirs_exist_ok)                     │
│                                                                              │
│ ╭───────────────────────────────── locals ─────────────────────────────────╮ │
│ │            copy_function = <function copy2 at 0x7f693a5b3b80>            │ │
│ │            dirs_exist_ok = True                                          │ │
│ │                      dst = PosixPath('/tmp/xubiru')                      │ │
│ │                  entries = [                                             │ │
│ │                            │   <DirEntry 'data'>,                        │ │
│ │                            │   <DirEntry 'workflows'>,                   │ │
│ │                            │   <DirEntry '.airflow'>,                    │ │
│ │                            │   <DirEntry 'config'>                       │ │
│ │                            ]                                             │ │
│ │                   ignore = <function                                     │ │
│ │                            ignore_patterns.<locals>._ignore_patterns at  │ │
│ │                            0x7f6939cec4c0>                               │ │
│ │ ignore_dangling_symlinks = False                                         │ │
│ │                      itr = <posix.ScandirIterator object at              │ │
│ │                            0x7f69377dbf80>                               │ │
│ │                      src = PosixPath('/usr/local/lib/python3.9/site-pac… │ │
│ │                 symlinks = False                                         │ │
│ ╰──────────────────────────────────────────────────────────────────────────╯ │
│                                                                              │
│ /usr/local/lib/python3.9/shutil.py:522 in _copytree                          │
│                                                                              │
│    519 │   │   if getattr(why, 'winerror', None) is None:                    │
│    520 │   │   │   errors.append((src, dst, str(why)))                       │
│    521 │   if errors:                                                        │
│ ❱  522 │   │   raise Error(errors)                                           │
│    523 │   return dst                                                        │
│    524                                                                       │
│    525 def copytree(src, dst, symlinks=False, ignore=None, copy_function=cop │
│                                                                              │
│ ╭───────────────────────────────── locals ─────────────────────────────────╮ │
│ │            copy_function = <function copy2 at 0x7f693a5b3b80>            │ │
│ │            dirs_exist_ok = True                                          │ │
│ │                      dst = PosixPath('/tmp/xubiru')                      │ │
│ │                  dstname = '/tmp/xubiru/config'                          │ │
│ │                  entries = [                                             │ │
│ │                            │   <DirEntry 'data'>,                        │ │
│ │                            │   <DirEntry 'workflows'>,                   │ │
│ │                            │   <DirEntry '.airflow'>,                    │ │
│ │                            │   <DirEntry 'config'>                       │ │
│ │                            ]                                             │ │
│ │                   errors = [                                             │ │
│ │                            │   (                                         │ │
│ │                            │   │                                         │ │
│ │                            '/usr/local/lib/python3.9/site-packages/incl… │ │
│ │                            │   │   '/tmp/xubiru/data',                   │ │
│ │                            │   │   "[Errno 13] Permission denied:        │ │
│ │                            '/tmp/xubiru/data'"                           │ │
│ │                            │   ),                                        │ │
│ │                            │   (                                         │ │
│ │                            │   │                                         │ │
│ │                            '/usr/local/lib/python3.9/site-packages/incl… │ │
│ │                            │   │   '/tmp/xubiru/workflows',              │ │
│ │                            │   │   "[Errno 13] Permission denied:        │ │
│ │                            '/tmp/xubiru/workflows'"                      │ │
│ │                            │   ),                                        │ │
│ │                            │   (                                         │ │
│ │                            │   │                                         │ │
│ │                            '/usr/local/lib/python3.9/site-packages/incl… │ │
│ │                            │   │   '/tmp/xubiru/.airflow',               │ │
│ │                            │   │   "[Errno 13] Permission denied:        │ │
│ │                            '/tmp/xubiru/.airflow'"                       │ │
│ │                            │   ),                                        │ │
│ │                            │   (                                         │ │
│ │                            │   │                                         │ │
│ │                            '/usr/local/lib/python3.9/site-packages/incl… │ │
│ │                            │   │   '/tmp/xubiru/config',                 │ │
│ │                            │   │   "[Errno 13] Permission denied:        │ │
│ │                            '/tmp/xubiru/config'"                         │ │
│ │                            │   ),                                        │ │
│ │                            │   (                                         │ │
│ │                            │   │                                         │ │
│ │                            PosixPath('/usr/local/lib/python3.9/site-pac… │ │
│ │                            │   │   PosixPath('/tmp/xubiru'),             │ │
│ │                            │   │   '[Errno 1] Operation not permitted'   │ │
│ │                            │   )                                         │ │
│ │                            ]                                             │ │
│ │                   ignore = <function                                     │ │
│ │                            ignore_patterns.<locals>._ignore_patterns at  │ │
│ │                            0x7f6939cec4c0>                               │ │
│ │ ignore_dangling_symlinks = False                                         │ │
│ │            ignored_names = set()                                         │ │
│ │               is_symlink = False                                         │ │
│ │                      src = PosixPath('/usr/local/lib/python3.9/site-pac… │ │
│ │                 srcentry = <DirEntry 'config'>                           │ │
│ │                  srcname = '/usr/local/lib/python3.9/site-packages/incl… │ │
│ │                   srcobj = <DirEntry 'config'>                           │ │
│ │                 symlinks = False                                         │ │
│ │             use_srcentry = True                                          │ │
│ ╰──────────────────────────────────────────────────────────────────────────╯ │
╰──────────────────────────────────────────────────────────────────────────────╯
Error: [('/usr/local/lib/python3.9/site-packages/include/base/data',
'/tmp/xubiru/data', "[Errno 13] Permission denied: '/tmp/xubiru/data'"),
('/usr/local/lib/python3.9/site-packages/include/base/workflows',
'/tmp/xubiru/workflows', "[Errno 13] Permission denied:
'/tmp/xubiru/workflows'"),
('/usr/local/lib/python3.9/site-packages/include/base/.airflow',
'/tmp/xubiru/.airflow', "[Errno 13] Permission denied: '/tmp/xubiru/.airflow'"),
('/usr/local/lib/python3.9/site-packages/include/base/config',
'/tmp/xubiru/config', "[Errno 13] Permission denied: '/tmp/xubiru/config'"),
(PosixPath('/usr/local/lib/python3.9/site-packages/include/base'),
PosixPath('/tmp/xubiru'), '[Errno 1] Operation not permitted')]

Expected behavior
Linux users are able to create projects in the /tmp directory as if they were running the SQL CLI commands locally.

Some ideas how to debug:

check permissions and user in build process as well as when starting the container
check https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
if not on linux, use lima to spin up a virtual linux host with docker installed
test root vs non-root user
check shutil.copytree docs which is whats failing in python

Some ideas how to debug:

check permissions and user in build process as well as when starting the container
check https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
if not on linux, use lima to spin up a virtual linux host with docker installed
test root vs non-root user
check shutil.copytree docs which is whats failing in python

authors: feluelle tatiana

repo: astronomer/astro-sdk


text:
[Cosmos CI] 2.7 unit tests taking a long time to run

Examples:

It seems like it gets stuck after hatch outputs Syncing dependencies. I'm not really sure how Hatch works though, so I'm not sure what that would imply.

We merged #1013, which does speed things up, although this does not really address the core issue. CI is still taking 20+ minutes to run Airflow 2.7. The issue is related to hatchling and how it syncs dependencies. This issue should stay open.
One avenue of investigation could be-- given that Apache Airflow also uses hatchling, we could see if Apache Airflow 2.7 ran into these issues and how CI issues were addressed over there.
I don't know much about hatchling so I don't know what could be causing the problem.

repo: astronomer/astronomer-cosmos


text:
Update databricks adapter for optional items

Following on from the fix provided by this pr.
Update the databricks adapter to set default values for items that are optional e.g. catalog.
Otherwise you get this generic error if they are not provided.
[2023-03-27, 16:03:14 BST] {subprocess.py:93} INFO - 15:03:14  Encountered an error:
[2023-03-27, 16:03:14 BST] {subprocess.py:93} INFO - Runtime Error
[2023-03-27, 16:03:14 BST] {subprocess.py:93} INFO -   Database Error
[2023-03-27, 16:03:14 BST] {subprocess.py:93} INFO -     Error during request to server
[2023-03-27, 16:03:15 BST] {subprocess.py:97} INFO - Command exited with return code 2

fixed with https://github.com/astronomer/astronomer-cosmos/pull/271


text:
ci(providers/amazon): extend max_attempts for resume_redshift_cluster to 20

…

Can we add some description to the PR. What's the default value and how we are anticipating that this would resolve the issue.

sure! I forgot to mark it as a draft first 🤦♂ I've triggered the test on the cloud. WIll update more detail after testing

source: gharchive/pull-request

repo: astronomer/astronomer-providers


text:
Write guide on how to download, organize, and use multiple plugins

Requested by Ares Sportswear

@petedejoy @paolaperaza I'm going to close this for now as there isn't a need for it and it's covered by most of our CLI docs. Feel free to open another issue with a specific use case

repo: astronomerio/airflow-guides


text:
Merged in updated astropy-helpers

So astropy_helpers had gotten out of sync somehow. I'm pretty sure this was my own doing, though even in hindsight I'm not sure how to have recognized how it was happening. It is a big of a nuisance that we have an entirely separate git history located in a sub-package, because it means we need to remember to manually check the astropy_helpers git history before committing to master.
Bottom line: with these changes, all of the changes made by @duncandc seem to have paid off: from within my bare bones virtualenv, the code passes all tests and raises no errors! Woohoo!

Well, durn, Travis is more finicky than my virtualenv.

repo: astropy/halotools


text:
Added support for x==Lbox points for SubhaloPhaseSpace model

Thanks to @johannesulf for pointing this out in #900 .
It might be a good idea if the behavior of a few other Halotools functions such as enforce_periodicity_of_box were modified to automatically wrap x == Lbox points to x == 0. Any thoughts on this @johannesulf?

I think this might be a good idea. I don't immediately see a downside to this.

authors: aphearin johannesulf


text:
Bug report for failed CircleCI build (job: window-test)

Auto-generated report for window-test job build.
Link to failed build: .
Note: Information about any subsequent build failures that happen while
this issue is open, will be added as comments with more information to this issue.

Link to latest failed build:

Link to latest failed build:

Link to latest failed build:

Link to latest failed build:

Link to latest failed build:

Link to latest failed build:

Link to latest failed build:

Link to latest failed build:

Link to latest failed build:
Test Failures
TestVerifyComponentDocumentation
TestVerifyComponentDocumentation/README_does_not_exist

Link to latest failed build:
Test Failures

TestVerifyComponentDocumentation
TestVerifyComponentDocumentation/README_does_not_exist


text:
feat: get directives from SelectionField

fixes #1547

@sunli829 could you please review this?

Any update on this PR please?

thanks 🙂

authors: meskill ouertani sunli829

repo: async-graphql/async-graphql


text:
Extend support for IntelliJ builds

Reason/Context
The plugin only works with older versions of IntelliJ. There are several requests for an update at JetBrains Marketplace.
Description
The latest build number has to be changed.

@danielkocot hi
You offered good PR and I reviewed it. I left question about working capacity
But unfortunately I have all ready updated plugin to work with idea 2021.1, 2021.1.1, 2021.1.2

There are several requests for an update at JetBrains Marketplace.

Yes, you are right. As I remember I answered to requests with link to jar/zip for local installation
It was my fault to not notify about new location for plugin.
Anyway, if everything is great, I will be glad to merge your pr into this repo.
New location is: https://github.com/Pakisan/jasyncapi-idea-plugin

Hi @Pakisan,
so you moved the plugin out the asyncapi org, right. But why? Isn't this org the right spot to evolve such a plugin for an IDE?
Best,
Daniel

@danielkocot

so you moved the plugin out the asyncapi org, right. But why?
Only jasyncapi will be left in this repo in the near future. Plugins will be moved to own repositories because of different release cycle and versioning

Isn't this org the right spot to evolve such a plugin for an IDE?
You are right about this. New repositories will be transferred to asyncapi organization soon.

@danielkocot can I close this issue or you want to finish your pr?

I close the pr and also the issue.

@Pakisan lemme know when you need me to help you with the split

authors: Pakisan danielkocot derberg

repo: asyncapi/jasyncapi


text:
refactor: adapt TypeScript generator to use MetaModel

Description
This PR adapts the TypeScript generator to use the new MetaModel.
Related issue(s)
Blocked by #656

Recreating this.

repo: asyncapi/modelina


text:
Send/Receive again confusion

Hello everyone. I've read 3.0 spec changes, but it's still confusing to understand send/receive.
Is it correct that now we think from the perspective of service described in asyncapi? (look at the picture below)

It would be very helpful to update documentation with some drawings, because it's still a little bit confusing

Is it correct that now we think from the perspective of service described in asyncapi?

The intent is now that you specify this from the perspective of the application being described by the AsyncAPI document.
Therefore, if your application is sending messages, you use send. If your application receives messages, you use receive.

Perfect. Thanks

authors: dalelane skonik

repo: asyncapi/spec


text:
Arc::ptr_eq equivalent for Stealer/Worker

It's not currently possible to tell whether or not a Stealer or Worker are pointing to the same underlying queue. Could we get a public facing API for this?

Hi, thanks for filing the issue and for the PR.
I would be OK if this can achieve with a somewhat less ad-hoc approach. I have outlined a proof of concept, please let me know if that would work for you. You could then achieve what you wanted as follow:
if my_worker.stealer_ref() == &my_stealer { ... }

If this approach suits you, then feel free to modify your PR along those lines (or I can add tests similar to yours and make a PR out of the PoC, just let me know).

The only objection I have to the POC is that the transmute is shady even with the repr(transparent) and assumes that references inherently have a fixed ABI. It's not a strict lifetime transmute and really hits the edge cases of what's sound, and would generally appreciate a solution that minimized exposure to unsafe.

My understanding of repr(transparent) is that it is precisely meant to warrant ABI equivalence. It is true that the ABI is not "fixed" in the sense that it can change between rust releases (unlike say repr(C)), but I don't see how that could result in UB.
The Rust RFC book also says [...] "without actually being affected by any ABI semantics", which to me suggests that this falls squarely within the safe uses of transmute. I also found a few threads like this one that appear to confirm this view.
Now to be clear, I agree that this should not be used and will definitely reconsider if you can point me to discussions that indeed suggest this is an edge case WRT soundness.
In the worse case there is the easy way out: storing a Stealer within the Worker instead of storing directly the underlying queue. Ugly but 100% safe ;-)
The reason I prefer PartialEq/Eq + stealer_ref rather than is_same_as is that they are orthogonal and both useful in their own right, whereas is_same_as is probably a bit niche (crossbeam's deque does not seem to have anything like this despite being way older than St3).

In the worse case there is the easy way out: storing a Stealer within the Worker instead of storing directly the underlying queue. Ugly but 100% safe ;-)

I'd strongly prefer this over the transmute.

The reason I prefer PartialEq/Eq + stealer_ref rather than is_same_as is that they are orthogonal and both useful in their own right, whereas is_same_as is probably a bit niche (crossbeam's deque does not seem to have anything like this despite being way older than St3).

Fair. My only other major concern is that it returns a reference of a Send/Sync type into the internals of a !Send/!Sync type. While not inherently unsound, it has me suspicious about it's use, even if the core Arc points to the same piece of memory.

Fair. My only other major concern is that it returns a reference of a Send/Sync type into the internals of a !Send/!Sync type. While not inherently unsound, it has me suspicious about it's use, even if the core Arc points to the same piece of memory.

This is in a way why I would argue that storing a Stealer inside the Worker is a plain misuse of the wrapped stealer. The methods of the worker are sound only if Worker is !Sync, but if Worker became a wrapper for a Stealer it would be actually necessary to negate the Sync by introducing an appropriate PhantomData.
On the other hand, there is IMO absolutely nothing wrong in returning a reference to a Stealer type (abstracting over how it is internally implemented). In fact there would be nothing wrong in implementing the methods of Stealer on a Worker: the only reason this is not done is that it would be inelegant and confusing, so stealer_ref provides a zero-cost escape hatch for the cases where it may needed.
I guess my point is: using unsafe is never a light decision, but storing a Stealer would only serve to give ourselves a false sense of security and pretend that the code is safe when it actually isn't: without a PhantomData to make it !Sync it would be plain UB even though there is technically no new occurrence of the dreaded unsafe keyword. I am of the firm belief that authors should not hide a potential unsafe and that only counting occurrences of unsafe is as little relevant as LOC metrics (unless one has a fully safe codebase of course). In fact I will frequently split an unsafe section into several smaller unsafe sections so they can be justified individually and can be more easily challenged in reviews -- and our conversation shows that this latter goal is achieved ;-)
Your reluctance is noted and understood, and as said above I am ready to reconsider if some gotchas are uncovered regarding transmute on repr(transparent) types, but otherwise I would rather live with an unsafe that can be easily reviewed than with a solution that looks safe but would actually be UB without due precautions. But I totally get that you would prefer not to undersign on this so I can make tomorrow a PR based on the PoC, in which case I would be grateful if you would grant me approval to adapt your tests.

I would be grateful if you would grant me approval to adapt your tests.

@james7132 I did not get your response on that, should I go on with integrating your tests and merging the PoC? If you are not OK with the proposed course of action then no problem, I would then leave it up to you to close the issue or keep it open (maybe a more consensual way to achieve can still be found, though I ran out of ideas for now).

Oh completely missed that! Sorry, please do go ahead.


text:
Not compatible with later versions of sass...

Bundler could not find compatible versions for gem "sass":
In snapshot (Gemfile.lock):
sass (3.4.19)
In Gemfile:
breakpoint (= 2.4.2) ruby depends on
sass (~> 3.3.0) ruby
Running bundle update will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

You may install the npm package instead and use
https://github.com/strarsis/sass-include-paths (with gulp-ruby-sass).

The latest version of the gem should work with any version of Sass >= 3.3 and < 4. That looks like it's a problem with your Gemfile.lock file.

authors: Preen Snugug strarsis

repo: at-import/breakpoint

license: mit

license_source: bigquery


text:
[New Video Request]: Component Lifecycle Methods

Suggest a Topic Name
React- Component Lifecycle Methods
What do you want to Learn?

Component Lifecycle methods
With example so that it will help in interview.

How soon do you need this video tutorial?
1
Do you want to see your name, social handle as a requester in the Video Description?
No response

It's done

authors: atapas prathamesh-khadakban

repo: atapas/youtube

license: MIT


text:
🛑 Wedding HTTPS is down

In 35ad69f, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in deb2cde.

repo: atatkin/milos-uptime


text:
🛑 Wedding HTTPS is down

In b905c84, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 145fd7e.


text:
🛑 Wedding HTTPS is down

In 0dd7418, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 80d2691.


text:
🛑 Wedding HTTPS is down

In 1d053ff, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 8f15599.


text:
🛑 Wedding HTTPS is down

In dba35a8, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 8eabe2c.


text:
🛑 Wedding HTTPS is down

In 78e39f2, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 84613dc.


text:
🛑 Minted HTTP is down

In 4fe32c3, Minted HTTP ($MINTEDHTTP) was down:

HTTP code: 502
Response time: 513 ms

Resolved: Minted HTTP is back up in a17c5cc.


text:
🛑 Wedding HTTPS is down

In 31f2522, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in b69ee1f.


text:
fix the zoom issue, where when you click on the search input field, the phone zooms in

what happens is when you close the search box bar, the phone stays zoomed in and you have to manually zoom out
    /*refactor to include this whenever tapping inside input text field, it zooms in, however, when tapping on the hamburger icon to open the slide out menu while zoomed in, it stays zoomed in, making it difficult to press the hamburger button again to close the left slide out navigation
    find a fix
    resource: http://stackoverflow.com/questions/5111964/disable-auto-zoom-field-zoom-on-input-tags-on-my-mobile-site-without-disabling & http://stackoverflow.com/questions/2989263/disable-auto-zoom-in-input-text-tag-safari-on-iphone*/
    var $viewportMeta = $('meta[name="viewport"]');
    $('input, select, textarea').bind('focus blur', function(event) {
        $viewportMeta.attr('content', 'width=device-width,initial-scale=1,maximum-scale=' +        (event.type == 'blur' ? 10 : 1));
    });
    /*end find fix for zoom in issue*/

resolved by adding user-scalable=no to  meta tag in the head of the document

repo: atechapart/responsive-slide-out


text:
my minecraft crashed when i created my modpack can someone look at the log and tell me what made it crash?

here are the logs
https://mclo.gs/SHHgte0

This is the issue tracker for the mclogs website itself. Please do not report Minecraft crashes here.

authors: JulianVennen ehrenneutrum

repo: aternosorg/mclogs


text:
Prepare for new release of Jira

Workflow links: null, null.

Closing as a duplicate of #93


text:
ARC-2096 Connected Repos View

What's in this PR?
Currently, the GH4J app displays the backfilling status at the organisation level, indicating the total number of repositories that have been backfilled so far. However, it lacks the functionality to show the backfilling task status for individual repositories, including which repositories have completed the backfilling process and which ones have encountered errors resulting in failure.
Created a  view that enables users to monitor the backfilling status of each task for connected repositories. This view should include pagination to accommodate a large number of repositories, along with filtering options based on backfilling status. Additionally, the view should incorporate a search capability, allowing users to easily locate a specific repository.

Added feature flags
enable-connected-repos-view"
Affected issues
ARC-2096
How has this been tested?
Local

Will close it for now. Need PM @Ryan-Yuanqing-Jiang to review the whole story and clarify with design.

repo: atlassian/github-for-jira


text:
Dcd 678 better password regex

Updates password regex as described here - https://regexr.com/4m291

Updated password constraint in -with-vpc template as well

repo: atlassian/quickstart-atlassian-jira


text:
🛑 Dont Tread On My Site Services is down

In 76e288e, Dont Tread On My Site Services ($DONT_TREAD_ON_MY_SITE) was down:

HTTP code: 403
Response time: 420 ms

Resolved: Dont Tread On My Site Services is back up in 2b32f2a after 9 minutes.

repo: atmovantage/atmostatus


text:
Installing package on atom: ETIMEDOUT

I installed Atom on my personal Mac which works fine. I just installed Atom on my PC at work and have problem to install packages. Here is the version of Atom I'm running:
T:\>atom --version
Atom    : 1.27.0

When trying to install a packages from Atom, I get the following error:
connect ETIMEDOUT 54.172.170.160:443

I also try to install the package from the command line with this command: T:\>apm install hydrogen-launcher and got this error message:
failed
Request for package information failed: connect ETIMEDOUT 54.164.206.44:443 (5 attempts) (ETIMEDOUT)

I looked at this github page but it didn't help or I couldn't implement the workaround
Any idea about what the problem could be?

Thanks for the report - can you fill out the issue template so we have all the basic information we need?
Also, are you behind a firewall or proxy at work?
Lastly, does it matter what package you try to install e.g. does this work or do you get the same error?
apm install zen

We require the template to be filled out on all new issues and pull requests so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way :grinning:

I have the same issue.

Thank you for your message @rsese. I just wanted to make clear that you're probably not dealing with the best computer ninja around. That being said, I'm going to comply to the requirement as good as I can
Prerequisites
I cannot put X in the prerequisites because, when I run the safe mode I cannot run a script although Atom starts correctly and load the script. what is the command / keyboard shortcut to run the script without packages installed?

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
I'm not able to install packages in Atom
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

@rsese in order to be able to fill all the prerequisite, I just need to run the code in safe mode. I did read this link: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode. Unfortunatetly Although I was able to load Atom in safe mode, I could not run a script in safe mode. I guess it has to do with the fact that the packages like Hydrogen and the shortcuts that go with it are not usable in safe mode. I know it is probably a basic question but could please help me in that case? Thank you very much for your help

I could not run a script in safe mode.

Sorry were you able to install packages or are you still having trouble doing that?  But yes, if you have community packages installed, they don't run in safe mode as mentioned in the Flight Manual.

Regarding the firewall question: yes I'm behind a firewall

If you are still having trouble installing packages, since you're behind a firewall, see if this helps:
https://github.com/atom/apm/#behind-a-firewall

Thank you @rsese. So yes I still can't install packages. I'm going to try your solution. Many thanks for your feedback

I have this problem in the new version of the Atom:
Request for package information failed: connect EACCES 52.86.66.223:443

Have the same problem...
I think that it happened after changing the internet line to MAP-E type (IPv4 over IPv6, port cannot be opened).
Is apm install not just a get request?
Atom v1.45.0
Win10 Pro v1909
Fetching outdated packages and themes failed.Hide output…
Request for package information failed: connect ETIMEDOUT 34.226.171.201:443

I have same same issue, bewlo are the configuration details
Atom V1.30
Win10

authors: aminya bjce honeo lastingman prat23k rsese

repo: atom/atom


text:
Remove delay on window focus (fixes #9544)

Wire up the focus handler unconditionally
Add new core.gitRepositoryRefreshOnWindowFocus setting
Check core.gitRepositoryRefreshOnWindowFocus in focus handler
Remove refreshOnWindowFocus param since it was unused
Document the project and config params

Description of the Change
If the user has one or more projects in the tree view with Git repositories, Atom freezes for a few seconds each time the window gains focus. The editor spends this time re-indexing Git data for all of those projects in the foreground. This makes Atom feel sluggish and unresponsive, and disrupts work flow when the user is likely to be ready to blaze ahead with an active task.
See #9544 for full discussion of the issue.
After this change, the default behavior is to no longer do this re-indexing work on window focus. A new settings checkbox can be used to enable the old behavior:

Alternate Designs
The old code had an unused Boolean parameter controlling whether the focus handler would be wired up. We could have passed the new setting as the value of that parameter. I decided that wasn't desirable because the changes could not take effect immediately when the user changed the setting. To respond to user setting changes on the fly, we need to wire up the event unconditionally and check the setting's current value when it fires. Since the old parameter would conflict with the new setting, it is removed.
Why Should This Be In Core?
Fixes an issue with Core.
Benefits

Improved responsiveness when multitasking Atom with other applications
Multiple users on #9544 reported quitting Atom or almost quitting due to this issue, so possible improvement in user outreach and retention
Multiple users on #9544 resorted to risky workarounds (deleting or renaming a project's .git folder, deactivating core packages, avoiding the use of project folders), so possible improvement in general stability if those workarounds are no longer needed

Possible Drawbacks
The old code does not document why this behavior existed, so we do not know the exact rationale for it or what might be lost by removing it. I speculate that it is to account for the possibility that the user might make changes affecting one of Atom's currently open Git repositories in an external application, which would then need to be reflected in Atom. However, this behavior imposes a serious usability penalty for all Git users, and users who do not need it have no recourse to eliminate this penalty. Furthermore, it is not a robust solution to that potential problem, as it is possible to modify a Git repo without switching focus away from Atom (for example, via a scheduled task or a remote login from another computer).
To mitigate the possibility of new issues, the problematic code is not simply removed. Rather, a setting is created so that users who need the old behavior and are willing to tolerate its drawbacks can enable it with a checkbox in the Core settings.
Applicable Issues

Fixes #9544

The latest CI error says:
Error: Expected HTMLNode not to be defined.
    at new jasmine.ExpectationResult (/Users/distiller/atom/vendor/jasmine.js:120:32)
    at newMatchersClass.toBeDefined (/Users/distiller/atom/vendor/jasmine.js:1241:29)
    at jasmine.Spec.<anonymous> (/Users/distiller/atom/node_modules/fuzzy-finder/spec/fuzzy-finder-spec.coffee:1268:131)
    at jasmine.Block.execute (/Users/distiller/atom/vendor/jasmine.js:1070:17)
    at jasmine.Queue.next_ (/Users/distiller/atom/vendor/jasmine.js:2102:31)
    at /Users/distiller/atom/vendor/jasmine.js:2092:18

If that's actually related to this PR, I'll be happy to make whatever changes are needed, but it looks spurious to me.

Hi @HebaruSan, thanks for the PR!  However, we already have a different PR fixing this in the short/medium term at #15702, and a long-term fix is in-progress at atom/git-utils#80.  For those two reasons, I'm going to close this PR.  Thanks again for your initiative and interest in Atom though!

I look forward to trying out the proper solution!


text:
autoindent lines with moveLineUp/moveLineDown

Related to #7546, added the autoIndentSelection if should autoIndent. A demo of the change:

Shouldn't there be an option in settings for that?

Shouldn't there be an option in settings for that?

It looks like it already respects the existing core.autoIndent scoped config option. It makes sense to me to use the same option as auto-indenting on newline insertion. Thoughts?

Could you add a test for this @joseramonc?

@maxbrunsfeld if so, it would be nice to have this metioned in setting description

@maxbrunsfeld Added tests for editor.moveLineUp() and editor.moveLineDown(), hope they are right, they were passing locally

Sorry for letting this go quiet for a while; there were some network-related CI failures. I re-ran the build.

@maxbrunsfeld It seems that just one build failed, is there some guide or help to debug this locally? Tests are passing on my computer :disappointed:

You can safely ignore the symbols-view error; that spec is super-flaky right now.

@joseramonc Thanks for the ping. Great work!

@joseramonc Thanks for this great feature, love it :tada:

Thanks a lot for your contribution but this breaks a pretty common use case : https://discuss.atom.io/t/move-line-without-auto-indent/23754
Could we have an other option in settings to disable this specific behaviour ?
Original message :

I don't want my lines to auto indent when I move them.

How can I change this behaviour ?

Example :

Perhaps an option to disable auto-indent when moving lines in plain-text files?

Perhaps an option to disable auto-indent when moving lines in plain-text files?

Note that this is not specific to Markdown / Plain Text :

@as-cii As per the gif @dorian-marchal just posted, I'd say auto-indent shouldn't trigger when changing lines from the same "lexical" line. Or make it understand what lexical line breaks are and make it work accordingly.

OK, it looks like this feature seems to have undesirable consequences pretty often, even in contexts where auto-indent is desirable for text insertion.
@joseramonc I think we may need to remove this feature until Atom's auto-indentation system is good enough to avoid these problems.

Just like @dorian-marchal has demonstrated this feature wreaks havoc on indentation for code spanning multiple lines. It would be nice to have a separate setting to enable or disable auto-indent specifically for this feature. EG: "editor.indentOnLineMove", when set to false it won't automatically indent but editor.autoIndent will remain untouched/active.
@dorian-marchal I kludged it with this custom command.
atom.commands.add 'atom-text-editor', 'my:move-line-up', ->
  editor = atom.workspace.getActiveTextEditor()
  if atom.config.get('editor.autoIndent')
    atom.config.set('editor.autoIndent', false)
    editor.moveLineUp()
    atom.config.set('editor.autoIndent', true)
  else
    editor.moveLineUp()

atom.commands.add 'atom-text-editor', 'my:move-line-down', ->
  editor = atom.workspace.getActiveTextEditor()
  if atom.config.get('editor.autoIndent')
    atom.config.set('editor.autoIndent', false)
    editor.moveLineDown()
    atom.config.set('editor.autoIndent', true)
  else
    editor.moveLineDown()

and
'.platform-linux atom-workspace atom-text-editor:not([mini])':
  'ctrl-shift-up': 'my:move-line-up'
  'ctrl-shift-down': 'my:move-line-down'

@snowsunny It works just fine, thank you :+1:

@dorian-marchal I’m happy to help :+1:

Maybe make this an option ? It seems useful for people that mostly use language with clear indent scoping block (like html, JavaScript)
I also feel that re-arranging item in hanging indent is somewhat rare.

Making this an option sounds :cool: to me – that way we could scope it only to grammars that play nicely with this.

Adding another vote for making this a separate option from auto-indent. For someone who moves multiple lines regularly, this is a real killer.
In the meantime, thanks to @snowsunny for the workaround.

In what kind of scenario auto-indent works well but this does not ?
I was under the impression that this only make auto-indent flaws more apparent.

Yes please for separating this into its own flag.

@eddiemonge  Please try this keymap.
# for mac
'.platform-darwin atom-workspace atom-text-editor:not([mini])':
  'ctrl-cmd-up': 'my:move-line-up'
  'ctrl-cmd-down': 'my:move-line-down'

Also, auto-indent while moving doesn't work well with Python code. Here is an example:

This can be pretty dangerous when writing python. For example, moving a line from above an if statement to underneath it makes the code conditional. If you don't notice the indentation change, it can take quite a while to figure out why your code has stopped working.
Definitely needs to be an option, and probably off by default in python - and I'd imagine any other language with significant whitespace. In the meantime, thanks @snowsunny - you are my internet hero of the day.
There is now a related issue where this is being discussed further: https://github.com/atom/atom/issues/10524

authors: 50Wliu YuriSolovyov alexandernst dorian-marchal eddiemonge geoffkembel jeancroy joseramonc maxbrunsfeld mnquintana phwh radiac snowsunny stefanbuck


text:
how do you make a patch to libchromium content

I want to make some changes chromium src files in libchromiumcontent, how do I make my own patch file?

Perhaps this is what you are looking for? https://github.com/atom/libchromiumcontent

We use atom/libchromiumcontent to maintain the patch to Chromium. If you need to customize libchromiumcontent, you need to build, and package it on local machine manually. Currently electron doesn't support the custom libchromiumcontent build #3310.

Maybe I didnt explain right. I have cloned atom/libchromiumcontent. And I have made some changes to \vendor\chromium\src\third_party\ffmpeg\chromium\scripts\build_ffmpeg.py I want to know how I can make a patch file, like there is plenty of in \patches already.

Use git diff to generate the patch file. The practice likes:
cd path-to-libchromiumcontent/vendor/chromium/src
git init
git add .
git commit -m "chrome v45"
// modify the src file
// git diff the src file

Exactly what I need, thank you very much!

authors: RHNorskov hokein nishanths

repo: atom/electron


text:
Strange behavior of the controls.back

Strange behavior of the controls.back function when using $route.navigate({..., replace: true})
reproduce

moved in to atomic router repo

repo: atomic-router/react


text:
🛑 pyjamacoaches.com is down

In 6e58fdc, pyjamacoaches.com (https://pyjamacoaches.com) was down:

HTTP code: 404
Response time: 1426 ms

Resolved: pyjamacoaches.com is back up in fb4e9aa.

repo: atraeclick/status


text:
Add new example of ADC with RTIC using SysTick as monotonic

Summary
[describe your changes here]
Checklist

[x] CHANGELOG.md for the BSP or HAL updated
[x] All new or modified code is well documented, especially public items
[x] No new warnings or clippy suggestions have been introduced (see CI or check locally)

If Adding a new Board

[x] Board CI added to crates.json
[x] Board is properly following "Tier 2" conventions, unless otherwise decided to be "Tier 1"

Pinging @ceigel. Did you want to pick this back up? An RTIC example for the feather_m0 would be nice to have.

@bradleyharden sorry for the delay. I addressed the comments. I haven't tested it on hardware with the new changes. I will do that in the following days.

@bradleyharden I tested this on hardware. The PR is ready to be merged.

@ceigel, Not sure if you're still interested in working on this, but I'll be happy to merge this if you want to bring the example up to speed with the current master.

authors: bradleyharden ceigel jbeaurivage

repo: atsamd-rs/atsamd


text:
chore: apply c sdk refactors

- What I did
- How I did it
- How to verify it
- Description for the changelog

The one bad thing about the new tests in parallel is that it is hard to tell, but the C daemon is likely timing out here. Hence the 2024/07/31 18:33:49 Run Command Timeout message

@JeremyTubongbanua there is cjson used directly in the sshnpd code, can you also update the includes to use <atclient/cjson.h>
Same with any mbedtls includes in srv.

authors: JeremyTubongbanua XavierChanth

repo: atsign-foundation/noports


text:
Transactions root mismatch

From time to time we see:
"error":"transactions root mismatch"

What could be causing this?
We do mix Teku and Lighthouse in beacon-node-addresseses, would that be a problem?

This happens when a beacon node is asked for a blinded beacon block but it does not fetch the execution payload from Vouch.  Some beacon nodes have the idea of a circuit breaker, where it will build a local payload if certain conditions are met.  Each beacon node has its own configuration and parameters, so you'd have to look at that to see what is configured and either adjust the parameters or turn the circuit breaker off entirely.

Thank you very much for pointing this out.
Gonna check configs.

authors: mcdee tongson

repo: attestantio/vouch


text:
Update http4s-blaze-client, ... to 0.21.18

Updates

org.http4s:http4s-blaze-client
org.http4s:http4s-blaze-server
org.http4s:http4s-circe
org.http4s:http4s-dsl

from 0.21.3 to 0.21.18.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

dependency:v0_21@org.http4s:http4s-scalafix:0.21.5

Documentation:

https://github.com/http4s/http4s/releases/tag/v0.21.5

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch, scalafix-migrations

Superseded by #253.

repo: augustjune/canoe


text:
Update scala-library to 2.13.12

About this PR
📦 Updates org.scala-lang:scala-library from 2.13.8 to 2.13.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:2

Superseded by #519.


text:
定时停止录制任务

直播平台
1
需求描述
ctrl+c可手动停止录制并转码，可以增加一个定时在cmd窗口执行ctrl+c的功能吗，感谢大佬！
操作步骤（可选）

...
需求截图（可选）
No response

定时任务请使用系统自带功能，本程序仅做直播录制相关功能
windows系统：任务计划程序+taskkill命令
linux系统：crontab+kill命令

repo: auqhjjqdo/LiveRecorder


text:
The loader doesn't resolve paths correctly?

I don't know whether it's a bug in Aurelia, SystemJS or just a failure in the actual configuration but I know that I managed to get this to work with Angular 2.0.
I have two projects, project A is where I have the client-side application and project B is where I have all the JSPM dependencies, project B is kinda like a private CDN.
Project A is hosted at http://localhost:5000
Project B is hosted at http://localhost:5005
Here is my basic index.html setup for Aurelia that resides in project A.
<!DOCTYPE html>
<html>
	<head>
		<base href="/"/>
		<meta charset="utf-8">
		<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
		<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no"/>
		<script src="http://localhost:5005/jspm_packages/system.js"></script>
		<script src="http://localhost:5005/config.js"></script>
	</head>
	<body aurelia-app>
		<script>
			System.import("aurelia-bootstrapper");
		</script>
	</body>
</html>

Here is the config.js for systemjs that resides in project B.
System.config({
  baseURL: "http://localhost:5005",
  defaultJSExtensions: true,
  transpiler: "none",
  paths: {
    "github:*": "jspm_packages/github/*",
    "npm:*": "jspm_packages/npm/*"
  },

  map: {
    "aurelia/bootstrapper": "github:aurelia/bootstrapper@0.16.0",
    "github:aurelia/binding@0.8.6": {
      "aurelia-dependency-injection": "github:aurelia/dependency-injection@0.9.2",
      "aurelia-metadata": "github:aurelia/metadata@0.7.3",
      "aurelia-task-queue": "github:aurelia/task-queue@0.6.2",
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/bootstrapper@0.16.0": {
      "aurelia-event-aggregator": "github:aurelia/event-aggregator@0.7.0",
      "aurelia-framework": "github:aurelia/framework@0.15.0",
      "aurelia-history": "github:aurelia/history@0.6.1",
      "aurelia-history-browser": "github:aurelia/history-browser@0.7.0",
      "aurelia-loader-default": "github:aurelia/loader-default@0.9.5",
      "aurelia-logging-console": "github:aurelia/logging-console@0.6.2",
      "aurelia-router": "github:aurelia/router@0.11.0",
      "aurelia-templating": "github:aurelia/templating@0.14.4",
      "aurelia-templating-binding": "github:aurelia/templating-binding@0.14.0",
      "aurelia-templating-resources": "github:aurelia/templating-resources@0.14.0",
      "aurelia-templating-router": "github:aurelia/templating-router@0.15.0",
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/dependency-injection@0.9.2": {
      "aurelia-logging": "github:aurelia/logging@0.6.4",
      "aurelia-metadata": "github:aurelia/metadata@0.7.3",
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/event-aggregator@0.7.0": {
      "aurelia-logging": "github:aurelia/logging@0.6.4"
    },
    "github:aurelia/framework@0.15.0": {
      "aurelia-binding": "github:aurelia/binding@0.8.6",
      "aurelia-dependency-injection": "github:aurelia/dependency-injection@0.9.2",
      "aurelia-loader": "github:aurelia/loader@0.8.7",
      "aurelia-logging": "github:aurelia/logging@0.6.4",
      "aurelia-metadata": "github:aurelia/metadata@0.7.3",
      "aurelia-path": "github:aurelia/path@0.8.1",
      "aurelia-task-queue": "github:aurelia/task-queue@0.6.2",
      "aurelia-templating": "github:aurelia/templating@0.14.4",
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/history-browser@0.7.0": {
      "aurelia-history": "github:aurelia/history@0.6.1",
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/loader-default@0.9.5": {
      "aurelia-loader": "github:aurelia/loader@0.8.7",
      "aurelia-metadata": "github:aurelia/metadata@0.7.3"
    },
    "github:aurelia/loader@0.8.7": {
      "aurelia-html-template-element": "github:aurelia/html-template-element@0.2.0",
      "aurelia-metadata": "github:aurelia/metadata@0.7.3",
      "aurelia-path": "github:aurelia/path@0.8.1",
      "core-js": "npm:core-js@0.9.18",
      "webcomponentsjs": "github:webcomponents/webcomponentsjs@0.6.3"
    },
    "github:aurelia/logging-console@0.6.2": {
      "aurelia-logging": "github:aurelia/logging@0.6.4"
    },
    "github:aurelia/metadata@0.7.3": {
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/route-recognizer@0.6.2": {
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/router@0.11.0": {
      "aurelia-dependency-injection": "github:aurelia/dependency-injection@0.9.2",
      "aurelia-event-aggregator": "github:aurelia/event-aggregator@0.7.0",
      "aurelia-history": "github:aurelia/history@0.6.1",
      "aurelia-logging": "github:aurelia/logging@0.6.4",
      "aurelia-path": "github:aurelia/path@0.8.1",
      "aurelia-route-recognizer": "github:aurelia/route-recognizer@0.6.2",
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/templating-binding@0.14.0": {
      "aurelia-binding": "github:aurelia/binding@0.8.6",
      "aurelia-logging": "github:aurelia/logging@0.6.4",
      "aurelia-templating": "github:aurelia/templating@0.14.4"
    },
    "github:aurelia/templating-resources@0.14.0": {
      "aurelia-binding": "github:aurelia/binding@0.8.6",
      "aurelia-dependency-injection": "github:aurelia/dependency-injection@0.9.2",
      "aurelia-logging": "github:aurelia/logging@0.6.4",
      "aurelia-task-queue": "github:aurelia/task-queue@0.6.2",
      "aurelia-templating": "github:aurelia/templating@0.14.4",
      "core-js": "npm:core-js@0.9.18"
    },
    "github:aurelia/templating-router@0.15.0": {
      "aurelia-dependency-injection": "github:aurelia/dependency-injection@0.9.2",
      "aurelia-metadata": "github:aurelia/metadata@0.7.3",
      "aurelia-path": "github:aurelia/path@0.8.1",
      "aurelia-router": "github:aurelia/router@0.11.0",
      "aurelia-templating": "github:aurelia/templating@0.14.4"
    },
    "github:aurelia/templating@0.14.4": {
      "aurelia-binding": "github:aurelia/binding@0.8.6",
      "aurelia-dependency-injection": "github:aurelia/dependency-injection@0.9.2",
      "aurelia-html-template-element": "github:aurelia/html-template-element@0.2.0",
      "aurelia-loader": "github:aurelia/loader@0.8.7",
      "aurelia-logging": "github:aurelia/logging@0.6.4",
      "aurelia-metadata": "github:aurelia/metadata@0.7.3",
      "aurelia-path": "github:aurelia/path@0.8.1",
      "aurelia-task-queue": "github:aurelia/task-queue@0.6.2",
      "core-js": "npm:core-js@0.9.18"
    },
    "github:jspm/nodelibs-process@0.1.1": {
      "process": "npm:process@0.10.1"
    },
    "npm:core-js@0.9.18": {
      "fs": "github:jspm/nodelibs-fs@0.1.2",
      "process": "github:jspm/nodelibs-process@0.1.1",
      "systemjs-json": "github:systemjs/plugin-json@0.1.0"
    }
  }
});

Now, to the actual problem.
When I'm using System.import("aurelia-bootstrapper"); I get the following error from the browser.
GET XHR http://localhost:5005/aurelia-bootstrapper.js [HTTP/1.1 404 Not Found 1ms]
no element found [aurelia-bootstrapper.js:1:1]
Error: XHR error (404 Not Found) loading http://localhost:5005/aurelia-bootstrapper.js
	Error loading http://localhost:5005/aurelia-bootstrapper.js [system.js:4:0]

When I'm using System.import("aurelia/bootstrapper/aurelia-bootstrapper"); I get yet a different error.
mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create [localhost:5000:41:6]
GET XHR http://localhost:5005/aurelia-loader-default.js [HTTP/1.1 404 Not Found 0ms]
no element found [aurelia-loader-default.js:1:1]
Unhandled promise rejection Error: XHR error (404 Not Found) loading http://localhost:5005/aurelia-loader-default.js [es6.promise.js:139:1]
	Error loading http://localhost:5005/aurelia-loader-default.js
Stack trace:
r@http://localhost:5005/jspm_packages/system.js:4:10959
e/</M/o.onreadystatechange@http://localhost:5005/jspm_packages/system.js:4:11484

This shouldn't have anything to do with Aurelia. At that, none of Aurelia is even loaded. This would be an issue with SystemJS configuration. The best place to ask would be the jspm gitter channel or create an issue with system.js

Okay, thanks!

authors: EisenbergEffect eyalsk

repo: aurelia/loader-default


text:
Compose-ref on a model-property in repeat.for-scope does not bind the reference to the property.

Hi I'm trying to access child compose scopes hosted within a repeat.for scope from the parent using compose.ref on model property but the property will never bind to the ref.

    Repeat index: ${$index}, name: ${model.name}
    <compose compose.ref="model.composeref" view-model="./myview" model.bind="cat"></compose>

from the parent I want to access the compose contexts something like this:
someMethod(){
this.models[0].composeref.somePropertyFromTheComposeViewModel.
}

I have built a working plunker of the issue:
http://plnkr.co/edit/timkNg2zBDz6x0qj9YY0?p
any known fixes for this problem?

The compose ref isn't going to give you access to your composed view model That gives you access to the instance of Compose (the view model that backs the compose element itself). Doing what you are doing isn't stricly using our public apis, so be ware. But if you want the instance of your own view model from that, you need to reference the currentViewModel of the Compose view model.

@EisenbergEffect I have a scenario where i need to change the view after it has rendered which is   , when i try to reassign views[0] = "newview" , that is not rerendering the dom, could you help me to achieve this

repo: aurelia/templating


text:
Clear Error

I have a code that does validation using two different rules.
My question is how do I clear the errors base on a particular view?
Is there something like
this.controller.clear({rules: this.certificate_item_rules})

The controller has a reset method. You can call it with no arguments to clear all the errors. You can pass an instruction to the reset method to target a specific object/property/rules.
http://aurelia.io/hub.html#/doc/article/aurelia/validation/latest/validation-basics/12

authors: jdanyow smithaitufe

repo: aurelia/validation


text:
Kibana crashes when opening dashboards

When I open one of your dashboard templates my kibana crashes with the following messages:
Version: 6.2.2
Build: 16588
Error: Uncaught TypeError: gaugeTypes[_this.gaugeConfig.type] is not a constructor (http://172.18.48.110/bundles/vendors.bundle.js?v=16588:12)
    at window.onerror (http://172.18.48.110/bundles/commons.bundle.js?v=16588:21:468094)

What version of ELK are you running

Oh, 6.2.2 isn't supported yet.  Still on 5.6.

Oh, ok. May you know a workaround or where to look to get it running on 6.2.2?

Planning to work on upgraded version next month.  It shouldn't be too much to convert. Feel free to give it a shot and submit your changes.  Would be a big help

authors: Skaldenmet austin-taylor

repo: austin-taylor/VulnWhisperer


text:
Cleaner shutdown using Lifeline Barriers

Remove 'short-circuiting' tab shutdown messages, and wait for the final output message before terminating the PTY process, Daemon services, and the tab command client.

Refactor shutdown in the PTY.  Use Lifeline Barriers in the PTY to synchronize shutdown
Refactor tab-command & tab-daemon shutdown.  Response::TabTerminated is only fired for the currently selected tab.
Resolve a concurrency bug with the tab-cli subscription service.  The final CliSubscriptionRecv::Output message was racing CliRecv::Terminated.  Now all messages flow through CliSubscriptionRecv
Remove many shutdown-related sleep statements, and refine the remaining statements to make more sense.  The only user-facing sleep is now the 25ms sleep in the tab command client.  All other shutdown messages are immediately propagated.
Add a bunch of shutdown-related log statements.

Fix several tab/test bugs

Awaiting stdout that already arrived simply fails, printing 'read timeout' several times.
The exit behavior of /bin/bash on OSX vs Linux is different.  OSX prints 'exit'.  Remove the 'find/replace' hack, and add a function which will end the snapshot at the latest stdout match.
Add a lot of useful test rig logging.

Resolves #181.
Should improve the UX for #165, as tab will now allow 1 second for graceful shutdown.

repo: austinjones/tab-rs


text:
🛑 glitch is down

In c7fb08a, glitch (https://congruous-calico-wedge.glitch.me/) was down:

HTTP code: 502
Response time: 265 ms

Resolved: glitch is back up in 6ad8d7c.

repo: auteen/autoreplit


text:
Little mistake in README

I found a little mistake in the README, see https://hyp.is/49FjfoEDEee2WVfxwy1Brw/www.npmjs.com/package/jsonwebtoken

Callback is passed the decoded payload if the signature and optional expiration, audience, or issuer are valid.

I think there is a part missing here. I'd like to propose the following new sentence as a replacement:

Callback is passed the decoded payload if the signature is valid and optional expiration, audience, or issuer are valid.

I understand almost the same (actually what I don't like is the "Callback is passed the decoded payload").
Anyway, I see it's clearer your way, be free to open a PR and I'll merge it.

@ziluvatar : I've created the PR.

PR was merged.

authors: joovel shawninder ziluvatar


text:
Bug in $format Parsing

I noticed that if the $format parameter is present, it doesn't respect any potential following parameters:
console.log(oData.parse('$select=foo,bar&$top=10&$format=application/json&$skip=42'));

{
  '$select': [ 'foo', 'bar' ],
  '$top': 10,
  '$format': 'application/json&$skip=42'
}

Note how $skip is not parsed and is instead concatenated to $format.
However, if I move $skip to precede $format everything is parsed as expected:
console.log(oData.parse('$select=foo,bar&$top=10&$skip=42&$format=application/json'));

{
  '$select': [ 'foo', 'bar' ],
  '$top': 10,
  '$skip': 42,
  '$format': 'application/json'
}

Interesting. Definitely a bug with the grammar. It probably wouldn't be too hard to update the grammar so that "&" is recognized as not part of the $format string. Ideally, we'd limit that to a specific set of characters that are allowed in the format string. (odata.pegjs, near 221.)

authors: alixaxel mkasberg


text:
🛑 Bitfee IT-Dokumentation is down

In 7c7d007, Bitfee IT-Dokumentation (https://www.doku.ch) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bitfee IT-Dokumentation is back up in cfb3e01.

repo: authentiqdigital/upptime


text:
[TECH-DEBT] - Handle multivalue support for www urlencoded header

This is a tech-debt ticket.
Before implementing, please check if the framework(Apache Http Client) is already taking care of this situation. If not, then implement it and raise a PR.
TODO-

Add an end point or use the existing end point in the Spring Boot demo repo to reproduce this

See the relevant repo/class in the below section

Add a simple brand new test-case with couple of Key-Values to the above repo
Please take care of "body" and "queryParams" while fixing the same.

The fix is similar for both. You might reuse the same code.

Spring boot repo:
https://github.com/authorjapps/spring-boot-integration-test
Controller class:
https://github.com/authorjapps/spring-boot-integration-test/blob/master/src/main/java/com/springboot/controller/CustomerController.java
Relevant comments from the old ticket:
Comment Link: https://github.com/authorjapps/zerocode/issues/141#issuecomment-432700435
That sounds correct. 👍 This will make everyone's life a lot easy now.
Postman accepts both as key-value and combines them if both are present(shown below).
Folks, Let's go with PR review n approval please !

Then in server app-

If same key is present, they server receives as multivalue(means client also sends as multi value) - see below:

postman client

spring boot server

@arunvelusamyd , Good job mate ! Have you taken care of the above(same key situation) in your PR ? If not can you please take care now ? 👍
@macrocks , @cooljavadev @nirmalchandra - Please review n approve -or- express your view points if disagree or think any other way  🙏

@authorjapps  May I work on this?

Yes, sounds good. 👍
Greetings and Welcome, Thanks for your interest in contributing.

Mailing list - Can you please join the mailing list?

https://groups.google.com/forum/#!forum/zerocode-automation

Please visit this(2min read) CONTRIBUTION guidelines page

https://github.com/authorjapps/zerocode/blob/master/CONTRIBUTING.md

Gitter link acts as QnA forum currently, until we have all members in the mailing-list above(newly created)

https://gitter.im/zerocode-testing/help-and-usage

Cheers

@authorjapps  I apologize for the inconvenience but I am unable to work on this due to other commitments. Please feel free to reassign.

No worries. Thanks for letting us know. 👍

@authorjapps is this issue still relevant? May I work on it?

Hello mate, I have added more details(springboot repo, controller class) to the description now.
Yes please, you can kindly pick this.
And thanks for your participation in contributing!
And if you could please join these-

Mailing list - Can you please join the mailing list?

https://groups.google.com/forum/#!forum/zerocode-automation

Please visit this(2min read) CONTRIBUTION guidelines page

https://github.com/authorjapps/zerocode/blob/master/CONTRIBUTING.md

Gitter link acts as QnA forum

https://gitter.im/zerocode-testing/help-and-usage

Cheers

@authorjapps Thanks a lot for this great opportunity) I've already done all these instructions and some research with fixes.
So, I've figured out that SpringBoot recognize same key from query parameters and HttpEntity as it was described  in comments from #141
For example, ZeroCode JSON with these objects "queryParams": {"notArray": "notOne"},"body": {"notArray": "notTwo"} will be recieved by SpringBoot as {notArray=[notOne, notTwo]}
But I guess it'll be nice, if we could use arrays in "queryParams" and "body", because now, if we'll try to send something like this "queryParams": {"array": ["one","two"]},"body": {"array": ["three","four"]} SpringBoot will receive {array=[[one, two],[three,four]]}. So I've fixed it, and now ZeroCode support multivalue not only for www-urlencoded header. If it's ok, can I raise a PR? Or if it's not ok - could you please tell where I've got it wrong?
Also, I have to say that in my fix I can't see really good way to control value duplicates, but should we really do this?

Solution sounds great. Thank you. We are reviewing this and will come back here soon.
@arunvelusamyd @santhoshTpixler @macrocks @aghorpade @officiallysameer @respondsid

Mixing the parameters in the URL(AKA queryParameters) and the body parameters will introduce more confusion. It is better to have a clear separation between the URL and the body.

I agree, but in my comment using "queryParams" and "body" together, just a demonstration. Of course, they can be used separately - my idea was to give an additional opportunity to use arrays for params both in "queryParams" and in "body".

@authorjapps Hello! I am interested in working on this issue. Is anyone working on this?

@priya1712d , please go ahead and raise a PR for this when ready.
Please have a look here for CONTRIBUTING:
https://github.com/authorjapps/zerocode/blob/master/CONTRIBUTING.md

Can I work on this, @authorjapps?

authors: JoaoFelipe76 authorjapps oiakinat pgmpofu priya1712d santhoshTpixler

repo: authorjapps/zerocode


text:
Alternate packaging (helm, olm, etc)

spicedb-operator has minimal packaging right now (a directory of kustomize manifests).
Several options that are worth exploring for other delivery mechanisms:

helm charts
OLM and/or RukPak bundles
KPT
kustomizer
crossplane

Whichever packaging we choose to support should be low touch and integrated with the release pipeline.
Update 1/27/23:
Releases now include instructions for installing with kubectl, kustomize, and kustomizer. Keeping this open to track the other options above.

💯 to helm charts as a manifest strategy. I saw there was a community-driven chart at https://github.com/jonwhitty/helm-charts/tree/master/charts/spicedb but it would be nice to use one that is officially supported to ensure that we remain up to date before locking in to using the chart.

A "official" helm chart would be beneficial for our GitOps (Flux) managed K8s clusters! Willing to contribute as well..

@ecordell, I have a helm chart for the operator that creates the same resources as the bundle. I'd be happy to contribute it if it's something you want. Let me know where I should put it.

Hey @croemmich,
Could you send a link to the public repo where the helm chart is?
We will link to it from here.

I don't currently have it public, I was hoping to give it to you so I didn't have to maintain it 😄
I'll get it posted on our company account and send a link.

@corkrean https://github.com/bushelpowered/spicedb-operator-chart

Thanks!

authors: corkrean croemmich dfr-exnaton ecordell mgagliardo91

repo: authzed/spicedb-operator


text:
Add option for toleration, node selector, affinity, and topologySpreadConstraints

Right now, there is no config option in SpiceDBCluster for setting

tolerations
nodeSelector
affinity/anti-affinity
topologySpreadConstraints
Is there any plan in the future to support these configs in the operator?

Yes, these are all things we'd like to support. The current discussion is happening in #61 - feel free to chime in there, otherwise we'll keep these examples in mind when we look at addressing #61.

This is now possible in in v1.2.0

authors: djoo-ce ecordell


text:
🛑 Limesurvey § limesurvey.dopracenakole.net is down

In 6c9980d, Limesurvey § limesurvey.dopracenakole.net (https://limesurvey.dopracenakole.net) was down:

HTTP code: 502
Response time: 3593 ms

Resolved: Limesurvey § limesurvey.dopracenakole.net is back up in 9a2521e after 9 minutes.

repo: auto-mat/automat-statuspage


text:
🛑 Cyklisté sobě § www.cyklistesobe.cz is down

In 1c43910, Cyklisté sobě § www.cyklistesobe.cz (https://www.cyklistesobe.cz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cyklisté sobě § www.cyklistesobe.cz is back up in af0c9c0 after 24 minutes.


text:
Testing on localhost

An attempt to make it possible running the server with full functionality (including authentication with GitHub) locally, without port forwarding.

Coverage remained the same at 34.806% when pulling 8647c017964804c562e3a125f179fdbe5964b902 on localhost_testing into cea3e8b98206e3f4c635044f11add2aaf9637876 on master.

@0xf8f8ff This looks like it can be merged, or did you have further plans for this PR?

authors: 0xf8f8ff coveralls meling

repo: autograde/aguis


text:
Score should be reset to 0 after a build fail.

Students sometimes try some methods to see if their solution is working (for e.g, using a different method than what was asked in the assignment) and get high score. But later on when the build fails then the score is not reset to 0. Student can misuse this and keep past score ask for approval.

attaching an example, this case student has 91% score even though build fails.

attaching an example, this case student has 91% score even though build fails.

This was a conscious decision to keep approved status if already approved (see code here). The rational for this was that students could then continue to work on their code without fear that their existing approvals would be reverted. This has saved us from a fair bit of churn as students messed up their code bases, that would otherwise have caused problems. Obviously, if the assignment is autoapprove, then this can be a problem.
I'm certainly willing to reconsider this decision. Please submit a PR and corresponding test cases that we can consider for inclusion.

This was a conscious decision to keep approved status if already approved (see code here). The rational for this was that students could then continue to work on their code without fear that their existing approvals would be reverted. This has saved us from a fair bit of churn as students messed up their code bases, that would otherwise have caused problems. Obviously, if the assignment is autoapprove, then this can be a problem.
I'm certainly willing to reconsider this decision. Please submit a PR and corresponding test cases that we can consider for inclusion.

Actually the bug is not about approved status just score. In this example it was approved incidentally. But the score doesn’t reset to 0 even in cases when it is not approved.

On Jan 23, 2021, at 09:54, Hein Meling notifications@github.com wrote:
This was a conscious decision to keep approved status if already approved (see code here https://github.com/autograde/quickfeed/blob/master/ci/run_tests.go#L107). The rational for this was that students could then continue to work on their code without fear that their existing approvals would be reverted. This has saved us from a fair bit of churn as students messed up their code bases, that would otherwise have caused problems. Obviously, if the assignment is autoapprove, then this can be a problem.
I'm certainly willing to reconsider this decision. Please submit a PR and corresponding test cases that we can consider for inclusion.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/autograde/quickfeed/issues/391#issuecomment-765891411, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMIUR32G3AHWXIKYBODYVTS3KFE5ANCNFSM4WOJJRNA.

Actually the bug is not about approved status just score. In this example it was approved incidentally. But the score doesn’t reset to 0 even in cases when it is not approved.

On Jan 23, 2021, at 09:54, Hein Meling notifications@github.com wrote:
This was a conscious decision to keep approved status if already approved (see code here https://github.com/autograde/quickfeed/blob/master/ci/run_tests.go#L107). The rational for this was that students could then continue to work on their code without fear that their existing approvals would be reverted. This has saved us from a fair bit of churn as students messed up their code bases, that would otherwise have caused problems. Obviously, if the assignment is autoapprove, then this can be a problem.
I'm certainly willing to reconsider this decision. Please submit a PR and corresponding test cases that we can consider for inclusion.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/autograde/quickfeed/issues/391#issuecomment-765891411, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMIUR32G3AHWXIKYBODYVTS3KFE5ANCNFSM4WOJJRNA.

Okay, I see. Reseting the score must be done by the Python scoring framework. You would probably need to have some mechanism to catch the failure and replace the score output, since this is all just strings in the output stream.
Note that QuickFeed can handle two Score objects for the same test in the output stream, e.g:
{"Secret":"","TestName":"TestFibonacci","Score":0,"MaxScore":28,"Weight":20}
{"Secret":"","TestName":"TestFibonacci","Score":24,"MaxScore":28,"Weight":20}

In Go I use the first one to record the existence of this test, in case the test failed with a panic, and didn't output the score (the last line). However, even this isn't flawless. It still fails to record the later tests, if one of the first few fails with a panic. But maybe if you only have a single test, this would work for you as a gap-stop solution?

Okay, I see. Reseting the score must be done by the Python scoring framework. You would probably need to have some mechanism to catch the failure and replace the score output, since this is all just strings in the output stream.
Note that QuickFeed can handle two Score objects for the same test in the output stream, e.g:
{"Secret":"","TestName":"TestFibonacci","Score":0,"MaxScore":28,"Weight":20}
{"Secret":"","TestName":"TestFibonacci","Score":24,"MaxScore":28,"Weight":20}

In Go I use the first one to record the existence of this test, in case the test failed with a panic, and didn't output the score (the last line). However, even this isn't flawless. It still fails to record the later tests, if one of the first few fails with a panic. But maybe if you only have a single test, this would work for you as a gap-stop solution?

BTW: I'm working on a new gRPC-based scoring framework, with the Score object defined in Protobuf. Hence, it can become easier to implement this also in a Python framework going forward. However, it is still early days, although I made a bit of progress yesterday; finally I was able to decide on some design issues, and make the API simple. The idea is to pre-register tests, their max score and weight over gRPC with QuickFeed, before starting to run student tests. This way we always know which tests should have been executed. If you want to take a look, it is in draft PR #384.

BTW: I'm working on a new gRPC-based scoring framework, with the Score object defined in Protobuf. Hence, it can become easier to implement this also in a Python framework going forward. However, it is still early days, although I made a bit of progress yesterday; finally I was able to decide on some design issues, and make the API simple. The idea is to pre-register tests, their max score and weight over gRPC with QuickFeed, before starting to run student tests. This way we always know which tests should have been executed. If you want to take a look, it is in draft PR #384.

authors: meling vinaysetty

repo: autograde/quickfeed


text:
Update Issue - 40715002

default description
URL tested: https://www.google.com/?gws_rd=ssl
Open URL on Browserstack

Property
Value

Browser
Chrome 38.0

Operating System
Windows XP

Resolution
1024x612

Screenshot Attached
Screenshot URL

Click here to reproduce the issue on Browserstack

Updated Screenshot Attached

repo: automationbs/testbugreporting


text:
Run names in logs are not really distinguishable

When adding multiple runs e.g. minimal/run_1 and mlp/run_1 it is not clear which one is which later on, because they are both called run_1. I find it a bit confusing, I think it would be nice to make it more obvious which run is which.

Adressed in https://github.com/automl/DeepCAVE/pull/146

authors: KrissiHub sarah-segel

repo: automl/DeepCAVE


text:
Analysis of local projects with mixed Java & Kotlin source sets results in incorrect analysis. Only Kotlin classes get analyzed

Build scan link
No public build scans, but noting the IDs of a successful check on macOS (czhpyt5q5zql4) and a failing one on linux (psf4ijexa3ida)
Plugin version
1.21.0
Gradle version
8.2.1
(Optional) Android Gradle Plugin (AGP) version
8.1.1
reason output for bugs relating to incorrect advice

On CI, I see several errors, such as this one:
Advice for :common:about-screen:impl
Unused dependencies which should be removed:
  implementation project(':common:country:public')

and ./gradlew :common:about-screen:impl:reason --id :common:country:public says
* What went wrong:
Execution failed for task ':common:about-screen:impl:reason'.
> A failure occurred while executing com.autonomousapps.tasks.ReasonTask$ExplainDependencyAdviceAction
   > There is no dependency with coordinates ':common:country:public' in this project.

And :common:country:public is definitely a dependency of all variants in :common:about-screen:impl.
Describe the bug

CI (linux) is showing different results than macOS builds, and those results are all incorrect like the example above. A comparison of the two build scans shows that both have the same dependencies and build dependencies, but there are differences in task inputs. Unfortunately there's not enough detail in a build scan comparison to show what the actual difference is to know if it's important.
To Reproduce
We are trying to reproduce these issues in a sample project which can be shared publicly, but as I'm sure you know this is rather difficult.
Expected behavior

CI builds checking for unused dependencies should not have errors that can't be duplicated locally.
Additional context

This is a collection of at least two (well, three) bugs. The first, the inability to find the requested project for reporting purposes, I have already resolved locally. The second is a kind of shadow of the first and has been longstanding and maybe I'll continue to ignore it for now (it's in ComputeUsagesTask and has the result that some analyzed dependencies may not end up in the output of that task if they only have the InferredCapability with a value of false); that "shouldn't happen" but you know. This bug was actually only triggered due to a workaround I implemented here for an issue in Gradle (no issue report yet; that's next).
The other bug is a more direct result of the Gradle bug referenced above. The tl;dr is that in a local project with a mixed source set of Java and Kotlin files, Gradle only provides the Kotlin files for analysis; the Java source gets ignored. This results in incorrect dependency analysis. The fix for this is under investigation. I have reported this in a private slack (again, public issue pending); noting the link here for my own reference later.
The comment in the private thread is reposted here, again for ease of reference:

sorry for letting this languish. The problem seems to be worse than I initially realized. Given an ArtifactCollection, the result of configurations[dependencyAnalyzer.compileConfigurationName].artifactsFor(dependencyAnalyzer.attributeValueJar) (sorry for opaque code, but I hope it more or less makes sense given all this context).
Further assume that this collection contains artifacts from local projects. Some of these projects have mixed source sets of Java and Kotlin files. E.g., src/main/java/<package>/Foo.java and src/main/java/<package>/Bar.kt. Please note that this is a canonical project layout for Android projects.
Now, iterate over that collection (each element is a ResolvedArtifactResult), calling it.getFile() on each. You will end up with a result like local-project/build/classes/kotlin/main. Critically, the actual class files for this local project are in both of build/classes/kotlin/main and build/classes/java/main.
The end result is that if I try to analyze the class files, I'll miss all the Java .class files.

Well, as gross as it is, this workaround might be sufficient:
// https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/issues/948#issuecomment-1711177139
val file = if (it.file.path.endsWith("kotlin/main")) {
  it.file.parentFile!!.parentFile!!
} else {
  it.file
}

authors: autonomousapps joshfriend


text:
autoware_pointcloud_preprocessor tests do not link properly

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
The templates in autoware_pointcloud_preprocessor are not instantiated so they can't be properly linked with the tests.
Expected behavior
All binaries in the project linked without issues
Actual behavior
Linking with stricter flags produces the current error:
2024-08-26T22:06:12.8648001Z [100%] Built target test_utilities
2024-08-26T22:06:14.7299232Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o: in function `DistortionCorrectorTest_TestIsInputValid_Test::TestBody()':
2024-08-26T22:06:14.7305828Z ./obj-x86_64-linux-gnu/./test/test_distortion_corrector_node.cpp:312: undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::isInputValid(sensor_msgs::msg::PointCloud2_<std::allocator<void> >&)'
2024-08-26T22:06:14.7309918Z /usr/bin/ld: ./obj-x86_64-linux-gnu/./test/test_distortion_corrector_node.cpp:320: undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::isInputValid(sensor_msgs::msg::PointCloud2_<std::allocator<void> >&)'
2024-08-26T22:06:14.7315092Z /usr/bin/ld: ./obj-x86_64-linux-gnu/./test/test_distortion_corrector_node.cpp:325: undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::isInputValid(sensor_msgs::msg::PointCloud2_<std::allocator<void> >&)'
2024-08-26T22:06:14.7330268Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x1d8): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::pointcloud_transform_exists()'
2024-08-26T22:06:14.7333263Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x1e0): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::pointcloud_transform_needed()'
2024-08-26T22:06:14.7351779Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x1e8): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::get_twist_queue()'
2024-08-26T22:06:14.7363833Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x1f0): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::get_angular_velocity_queue()'
2024-08-26T22:06:14.7382829Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x1f8): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::processTwistMessage(std::shared_ptr<geometry_msgs::msg::TwistWithCovarianceStamped_<std::allocator<void> > const>)'
2024-08-26T22:06:14.7421488Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x200): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::processIMUMessage(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::shared_ptr<sensor_msgs::msg::Imu_<std::allocator<void> > const>)'
2024-08-26T22:06:14.7488693Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x218): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector2D>::undistortPointCloud(bool, sensor_msgs::msg::PointCloud2_<std::allocator<void> >&)'
2024-08-26T22:06:14.7492009Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x230): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector3D>::pointcloud_transform_exists()'
2024-08-26T22:06:14.7494969Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x238): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector3D>::pointcloud_transform_needed()'
2024-08-26T22:06:14.7497829Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x240): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector3D>::get_twist_queue()'
2024-08-26T22:06:14.7500735Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x248): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector3D>::get_angular_velocity_queue()'
2024-08-26T22:06:14.7504579Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x250): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector3D>::processTwistMessage(std::shared_ptr<geometry_msgs::msg::TwistWithCovarianceStamped_<std::allocator<void> > const>)'
2024-08-26T22:06:14.7508980Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x258): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector3D>::processIMUMessage(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::shared_ptr<sensor_msgs::msg::Imu_<std::allocator<void> > const>)'
2024-08-26T22:06:14.7513060Z /usr/bin/ld: /tmp/ccvFi0NQ.ltrans0.ltrans.o:(.data.rel.ro+0x270): undefined reference to `autoware::pointcloud_preprocessor::DistortionCorrector<autoware::pointcloud_preprocessor::DistortionCorrector3D>::undistortPointCloud(bool, sensor_msgs::msg::PointCloud2_<std::allocator<void> >&)'
2024-08-26T22:06:14.8537586Z collect2: error: ld returned 1 exit status

Steps to reproduce
Link with -Wl,--no-undefined to cause build to error if there are undefined symbols.
Versions
No response
Possible causes
No response
Additional context
No response

try this
https://cdn.discordapp.com/attachments/1277836331501883449/1280291965879193731/fix.zip?ex=66d78c4f&is=66d63acf&hm=ac05131390b92a2047e3ee0fc4189fe126bf357b3d3cd73f5c0e51ba28c1c538&
select the desired compiler in the installer