text:
Implement tomee.mp.jwt.allow.no-exp property over mp.jwt.tomee.allow.…

…no-exp

Should I change the property name in the JWT TCK?
https://github.com/apache/tomee/blob/main/tck/microprofile-tck/jwt/src/test/java/org/apache/tomee/microprofile/tck/jwt/validation/ExpClaimAllowMissingExpValidationTest.java#L89

Do we have an issue for this one @tichovz ?

Hi!
I have no issues for this, but David asked if could take a look at it.

On Nov 9, 2022, at 10:29 AM, Zoltán Tichov <zoltan.tichov@gmail.com> wrote:
Hi!
Is there another task that could be taken care of?

There's a change in the same code that's on my "I should really find the time to fix that" list if you want to dig in.
Basically, we added a TomEE-specific property mp.jwt.tomee.allow.no-exp.  We likely should avoid putting custom properties in >the mp.jwt.* namespace and likely we should:

rename it to something that starts with tomee like say tomee.mp.jwt.allow.no-exp
ensure both properties work for backwards compatibility
tomee.mp.jwt.allow.no-exp would win if both were defined
any use of mp.jwt.tomee.allow.no-exp should get a warning log message
create an itest or two in itests/microprofile-jwt-itests/ that uses the property
update docs/microprofile/jwt.adoc
File JIRA cause I haven't done that yet, LOL :)

The runtime change will be a piece of cake for you.  Most the work would be in the itest, which could be kind of new/fun to do.

Thoughts?

Thanks. That was the missing link, so maybe you can just rebase and we do a CI build to see, if it breaks anything?

Thanks, Would I make a rebase with the main branch or the 9.x branch?

Let's test against main and if it looks nice, we should backport to 9.1.x too

I made a rebase to main and it seems ok.

repo: apache/tomee


text:
Dependencies are underspecified in docs

I tried to build Traffic Server 9.1.2 from source. It turned out that build process depends on perl, but it is not listed in dependencies in the documentation.
Also, I recommend you specifying which of the dependencies are build-time or run-time.

We removed the check for Perl for 9.2.0. I set it to be backported to the 9.1.3 release: #8611

But you still need perl to build ATS perl module?

source: gharchive/issue

authors: bryancall petershh

repo: apache/trafficserver

license_type: permissive

license_source: github-api


text:
Prevents response body content with a 204

Issue Description
If a plugin uses TSHttpTxnSetHttpRetStatus to set the status of a transaction, when ATS generates the response it will use HttpBodyFactory and its templates to do so. There is no special handling for the 204 response code and no special template for it therefore it will get a body generated by the default body factory template. This is a violation of the W3 spec which requires a 204 response to have no body.
There are several changes that need to be made in a coordinated fashion.

A template for a 204 response should be added to body factory template system so that it is used for a 204 if available.
When generating in the body factory, if the response code is forbidden to have a body the body factory MUST NOT use a default, only the specific response template if present. If not present, a body MUST NOT be generated.
For bodyless responses, a body SHOULD BE sent if a plugin called TSHttpTxnErrorBodySet.

Pull Request
By default, when we return a 204, we do not send a response body.
If a custom response body template is configured, it is still returned.
If a plugin sets a response body explicitly, it is still returned.
Also includes minor fixes/improvements related to the above.

[approve ci]

If this needs a redo anyway, because clang format and squashing, let's split off the change to .gitignore as a separate PR and merge that quickly.

If this needs a redo anyway, because clang format and squashing, let's split off the change to .gitignore as a separate PR and merge that quickly.

This is done; moved to #2078.

[approve ci]

The method used to evaluate test conditions here is too brittle, as it relies on verbose output from the curl command line tool.
We are getting tripped up by two things:

When curl receives a 204, it interprets it so that curl's output does not include any response body, and therefore we cannot precisely validate the response is what we expect—even if, as in this case, it breaks the HTTP spec.
curl's verbose output has not expectation of stability between releases of the tool to match our expectation of stability in our repeatable testing.

Going to investigate a better way to serialize output from ATS so we can avoid the two kinds of issues above that are causing false positives here.

[approve ci autest]

[approve ci autest]

Still working on this issue. Will update the branch when I am convinced it works.

[approve ci]

[approve ci]

[approve ci autest]

[approve ci]

[approve ci autest]

@SolidWallOfCode @persiaAziz How does this look to you?

It looks good to me

[approve ci]

Cherry picking this to 7.1.0.

source: gharchive/pull-request

authors: SolidWallOfCode bryancall d2r dragon512 persiaAziz zwoop


text:
[test] rm 1MB limit in bundle_deploy test

@areusch
Hi Andrew Reusch, I write a simple benchmark to test the speed between C++ ifstream and fread when load the params data. The code snippet is below. And I use the read_all_or_die function for fread case, which was written by you. In my test case, the params data size is larger than 1MB. Maybe we can remove the 1MB limit in the apps/bundle_deploy/test.cc for workaround. If it's OK, I will send a PR to remove this.
https://github.com/apache/tvm/blob/24e89befd6c2f45fe47512de5d1445d8ea809a98/apps/bundle_deploy/test.cc#L46-L49
#include <benchmark/benchmark.h>
#include <sys/stat.h>

#include <fstream>
#include <iostream>

static void BM_read_file(benchmark::State& state) {
  for (auto _ : state) {
    std::ifstream json_in("/Users/zhyncs/Downloads/0_1.params", std::ios::in);
    std::string json_data((std::istreambuf_iterator<char>(json_in)),
                          std::istreambuf_iterator<char>());
    json_in.close();
  }
}

BENCHMARK(BM_read_file);

static char* read_all_or_die(const char* name, const char* file_path, size_t* out_size) {
  struct stat st;
  if (stat(file_path, &st)) {
    char err[1024];
    snprintf(err, sizeof(err), "%s: statting file", name);
    perror(err);
    abort();
  }

  if (out_size != nullptr) {
    *out_size = st.st_size;
  }

  char* data = (char*)malloc(st.st_size);
  FILE* fp = fopen(file_path, "rb");
  size_t bytes_to_read = st.st_size;
  size_t bytes_read = 0;
  while (bytes_read < bytes_to_read) {
    size_t this_round = fread(data, 1, st.st_size, fp);
    if (this_round == 0) {
      if (ferror(fp)) {
        char err[1024];
        snprintf(err, sizeof(err), "%s: error during read", name);
        perror(err);
      } else if (feof(fp)) {
        std::cerr << name << ": file is shorter than its stat size (" << bytes_read << " v "
                  << st.st_size << ")" << std::endl;
      } else {
        std::cerr << name << ": fread stopped returning data" << std::endl;
      }
      abort();
    }
    bytes_read += this_round;
  }

  fclose(fp);
  return data;
}

static void BM_read_file_v2(benchmark::State& state) {
  for (auto _ : state) {
    read_all_or_die("params_data", "/Users/zhyncs/Downloads/0_1.params", nullptr);
  }
}

BENCHMARK(BM_read_file_v2);

BENCHMARK_MAIN();

The result is below.
----------------------------------------------------------
Benchmark                Time             CPU   Iterations
----------------------------------------------------------
BM_read_file    3246447709 ns   3244741000 ns            1
BM_read_file_v2   24013239 ns     23994069 ns           29

Close this issue because there is no response for a long time.

repo: apache/tvm


text:
[Unity] [Hexagon] Fix deprecated call for data layout size in bits

The unity branch has errors for deprecated APIs.  Updating the codegen for Hexagon call from llvm::DataLayout::getTypeSizeInBits.getFixedSize() to llvm::DataLayout::getTypeSizeInBits.getFixedValue()
Verified this works on main as well.
cc: @farshidsp

@janetsc Can you send this to main? The change to unity should be specific to relax. We get the same change in unity after weekly rebase.

Done, created a PR for main, closing this one.

authors: janetsc masahi


text:
UNOMI-254 Add Groovy scripting support for actions

These changes include:

Make the ActionExecutorDispatcher pluggeable, so that it may delegate to multiple implementations
Provide an implementation for Groovy
Provide an sample bundle that uses a Groovy action

Signed-off-by: Serge Huber shuber@apache.org

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/unomi-pr/55/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/unomi-pr/56/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/unomi-pr/61/

authors: asf-ci sergehuber

repo: apache/unomi


text:
WICKET-6895: Corrected url to Wicket examples from 8x to 9x in documentation

Updated the examples url in asciidoc file

Wrong branch. Request should have been on the wicket-9.x branch

repo: apache/wicket

license_source: bigquery


text:
[YUNIKORN-2642] Don't set resources on the recovery queue

What is this PR for?
Don't set resources from tags on the recovery queue.
This PR is for branch-1.5.
What type of PR is it?

[x] - Bug Fix
[ ] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2642
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Tested locally w/ "make test".

repo: apache/yunikorn-core


text:
[ZEPPELIN-1883] Can't import spark submitted packages in PySpark

What is this PR for?
Fixed importing packages in pyspack requested by SPARK_SUBMIT_OPTION
What type of PR is it?
[Bug Fix]
Todos
Nothing
What is the Jira issue?
ZEPPELIN-1883
How should this be tested?

Download Apache Spark 1.6.2 (since it's the most recent for pyspark-cassandra)

Set SPARK_HOME and SPARK_SUBMIT_OPTION in conf/zeppelin-env.sh like

export SPARK_HOME="~/github/apache-spark/1.6.2-bin-hadoop2.6"
export SPARK_SUBMIT_OPTIONS="--packages com.datastax.spark:spark-cassandra-connector_2.10:1.6.2,TargetHolding:pyspark-cassandra:0.3.5 --exclude-packages org.slf4j:slf4j-api"

Check before that you can run spark-submit or not

./bin/spark-submit --packages com.datastax.spark:spark-cassandra-connector_2.10:1.6.2,TargetHolding:pyspark-cassandra:0.3.5 --exclude-packages org.slf4j:slf4j-api --class org.apache.spark.examples.SparkPi lib/spark-examples-1.6.2-hadoop2.6.0.jar

Test whether submitted packages can be import or not

%pyspark

import pyspark_cassandra

Screenshots (if appropriate)
import pyspark_cassandra

Traceback (most recent call last):
  File "/var/folders/lr/8g9y625n5j39rz6qhkg8s6640000gn/T/zeppelin_pyspark-5266742863961917074.py", line 267, in <module>
    raise Exception(traceback.format_exc())
Exception: Traceback (most recent call last):
  File "/var/folders/lr/8g9y625n5j39rz6qhkg8s6640000gn/T/zeppelin_pyspark-5266742863961917074.py", line 265, in <module>
    exec(code)
  File "<stdin>", line 1, in <module>
ImportError: No module named pyspark_cassandra

Questions:

Does the licenses files need update? - NO
Is there breaking changes for older versions? - NO
Does this needs documentation? - NO

In my test, I got a  INFO [2017-01-02 09:08:12,358] ({Exec Default Executor} RemoteInterpreterManagedProcess.java[onProcessComplete]:164) - Interpreter process exited 0 error when i try to run the paragraph.
Maybe this error occurs when couldn't download libraries of SPARK_SUBMIT_OPTIONS option.
Is this normal behavior?

@astroshim Thanks for review!
It's the expected behavior. If spark submit doens't be properly loaded, spark interpreter will die without errors.

@1ambda Spark doesn't support specifying python packages throught --packages, the correct usage is to use --py-files. Although this PR could resolve your issue, but the issue here is not due to zeppelin bug, it is because of wrong usage of --packages.

right, I'm a bit concern if this would be the right fix for the issue?

@zjffdu Thanks for review :)
Then, How can I load pyspark-cassandra for pyspark?

@1ambda Actually, pyspark-cassandra doesn't work for me in pyspark shell. I guess it works because you have installed it locally.
>>> import pyspark_cassandra
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named pyspark_cassandra

@zjffdu
I'v just created gist to show --packages option download pyspark-cassandra. https://gist.github.com/1ambda/5caf92753ea2f95ada11b1c13945d261
downloading https://repo1.maven.org/maven2/com/datastax/spark/spark-cassandra-connector_2.10/1.6.2/spark-cassandra-connector_2.10-1.6.2.jar ...
	[SUCCESSFUL ] com.datastax.spark#spark-cassandra-connector_2.10;1.6.2!spark-cassandra-connector_2.10.jar (450ms)
downloading http://dl.bintray.com/spark-packages/maven/TargetHolding/pyspark-cassandra/0.3.5/pyspark-cassandra-0.3.5.jar ...
	[SUCCESSFUL ] TargetHolding#pyspark-cassandra;0.3.5!pyspark-cassandra.jar (310ms)
downloading https://repo1.maven.org/maven2/com/datastax/spark/spark-cassandra-connector-java_2.10/1.6.0-M1/spark-cassandra-connector-java_2.10-1.6.0-M1.jar ...
	[SUCCESSFUL ] com.datastax.spark#spark-cassandra-connector-java_2.10;1.6.0-M1!spark-cassandra-connector-java_2.10.jar (23ms)
downloading https://repo1.maven.org/maven2/com/datastax/cassandra/cassandra-driver-core/3.0.0/cassandra-driver-core-3.0.0.jar ...
	[SUCCESSFUL ] com.datastax.cassandra#cassandra-driver-core;3.0.0!cassandra-driver-core.jar(bundle) (78ms)
:: resolution report :: resolve 2819ms :: artifacts dl 870ms

hmm, it works in local mode but doesn't work in yarn-client mode. Could you try yarn-client mode ?

I tested on yarn-client, mesos-client and found that

mesos-client mode copy pyspark-cassandra submitted by --packages as you can see [here] (https://gist.github.com/1ambda/e3326107d14ece9a39663cbc56f05756) (the error is due to invalid python version, not problem of spark, pyspark-cassandra)

Using Python version 2.6.6 (r266:84292, Aug 18 2016 15:13:37)
SparkContext available as sc, HiveContext available as sqlContext.
>>> import pyspark_cassandra
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/tmp/spark-df7bc8fa-233f-4124-855b-4a39fa948c1a/userFiles-ab70ffa3-212b-47ee-9611-9c240d3ce899/TargetHolding_pyspark-cassandra-0.3.5.jar/pyspark_cassandra/__init__.py", line 24, in <module>
  File "/tmp/spark-df7bc8fa-233f-4124-855b-4a39fa948c1a/userFiles-ab70ffa3-212b-47ee-9611-9c240d3ce899/TargetHolding_pyspark-cassandra-0.3.5.jar/pyspark_cassandra/context.py", line 16, in <module>
  File "/tmp/spark-df7bc8fa-233f-4124-855b-4a39fa948c1a/userFiles-ab70ffa3-212b-47ee-9611-9c240d3ce899/TargetHolding_pyspark-cassandra-0.3.5.jar/pyspark_cassandra/rdd.py", line 291
    k = Row(**{c: row.__getattr__(c) for c in columns})
                                       ^
SyntaxError: invalid syntax
>>>

yarn-client mode doens't copy pyFiles as you can see here

    // If we're running a python app, set the main class to our specific python runner
    if (args.isPython && deployMode == CLIENT) {

...

      if (clusterManager != YARN) {
        // The YARN backend handles python files differently, so don't merge the lists.
        args.files = mergeFileLists(args.files, args.pyFiles)
      }

Summary
@zjffdu @felixcheung

I am not sure why they decided not to copy py-files in yarn-client mode. But it's problem of spark, not zeppelin.
As you saw, this is expected behavior at least in local, mesos-client.

Any update on this?

I still think this is not a correct fix since it doesn't resolve the yarn-client mode which I believe most of users use this mode.

@zjffdu

since it doesn't resolve the yarn-client mode

PySpark also doens't support extending PYTHONPATH in yarn-client.
You are saying this is not right fix repeatedly without providing any other idea. So let me ask

How you can load  pyspark-cassandra using packages as described in their README.md in local, mesos-client mode.

As I said before why not using --py-files, I check the repository of pyspark-cassandra.
https://github.com/TargetHolding/pyspark-cassandra
README shows that user can use --py-files
spark-submit \
    --jars /path/to/pyspark-cassandra-assembly-<version>.jar \
    --driver-class-path /path/to/pyspark-cassandra-assembly-<version>.jar \
    --py-files /path/to/pyspark-cassandra-assembly-<version>.jar \
    --conf spark.cassandra.connection.host=your,cassandra,node,names \
    --master spark://spark-master:7077 \
    yourscript.py

I read and replied before.

Q. README shows that user can use --py-files
A. Users cannot benefit from --packages. They need to download, find location of all transitive deps and provide the paths to --py-files

And even in spark, we can use --packages in local, mesos-client. Why do you think zeppelin should't do?

I tested this PR in yarn-client and it works. How did you test this PR in yarn-client?

since it doesn't resolve the yarn-client mode

Could you tell me your env?

how did you build (command, env)
zeppelin, yarn, spark versions.

Sorry, I miss your last reply. Do you mean yarn-client mode works for you in spark ?
I use the following command to launch pyspark and get the error as following:
Launch pyspark ( I am using spark 2.1.0)
bin/pyspark --packages com.datastax.spark:spark-cassandra-connector_2.10:1.6.2,TargetHolding:pyspark-cassandra:0.3.5 --exclude-packages org.slf4j:slf4j-api --master yarn-client

Fail to import pyspark_cassandra
>>> import pyspark_cassandra
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named pyspark_cassandra

@zjffdu I'v just fixed not to extend PYTHONPATH using submitted packages only in yarn-client

Thanks, @1ambda Do you mind to create a spark ticket as well ? The behavior inconsistency between different modes seems an issue of spark, we need to clarify it with spark community.

For reviewers
Fixed to use spark.jars instead of classpath.

classpath doesn't include submitted jars at this moment (i could get 7 days ago, but not now)
it enable to simplify logic since we don't need to get classpath before setting new classpath. In other words, we can directly set PYTHONPATH in setupPySparkEnv function.
Also tested in spark 1.6.2, spark 2.0.0

@zjffdu
The spark code we talked came from https://github.com/apache/spark/pull/6360. It seems like intended so it's ok not to raise an issue.

Thanks @1ambda for the fix. Thanks @zjffdu for reviewing and verifying.
It looks good to me, while it provides more consistent behavior between PysparkInterpreter and SPARK_HOME/bin/pyspark. Merge to master and branch-0.7 if no more comments.

authors: 1ambda Leemoonsoo astroshim felixcheung zjffdu

repo: apache/zeppelin


text:
ZEPPELIN-3595. Remove interpreter binding in backend

What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html
What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
Put link here, and add [ZEPPELIN-Jira number] in PR title, eg. [ZEPPELIN-533]

How should this be tested?

First time? Setup Travis CI as described on https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

Screenshots (if appropriate)
Questions:

Does the licenses files need update?
Is there breaking changes for older versions?
Does this needs documentation?

Five hundred lines' difficult and sophisticated code will be removed. :-)

@felixcheung It's not for now if you set spark interpreter group as the first interpreter group in your zeppelin-site.xml. I think it needs more implementation even in front side as well to keep the default interpreter setting per note. We need to know whole plan to remove interpreter binding option

@jongyoul I like the idea of having a default interpreter (and not a default interpreter group ) per note.
+1

Will merge it if no more comments

authors: Tagar jongyoul zjffdu


text:
🛑 InterHop (Website) is down

In a87a37c, InterHop (Website) (https://interhop.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: InterHop (Website) is back up in e5aa823 after 11 minutes.

license: MIT


text:
Textcolor of filterlist entrys

Is there a way to change the text color of only specific entrys in the filterlist? For example i want to make the first 3 entrys green, how would i do that?
Regards Adarkas

Is there any solution on this cases?

repo: apasccon/SearchTextField

license: mit


text:
Improve installation instructions for macos

With mojave it is really difficult to just run things so will need additional instructions, plus will need to instruct user to make file executable.

Is this still important now that we have binary releases?

I think so, more than ever, because the newer versions of MacOS really lock down running unsigned executables like ours.

repo: apclary/dungeon-revealer

license: ISC


text:
Fix to permit saml custom service definition by overriding SamlRegisteredService

By using class equals method won't be possible to define a custom saml registered service by overriding the existing SamlRegisteredService class.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.fabio seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant fmartelli

repo: apereo/cas


text:
refactor plugins

This is still annoying but at least now we have real interfaces, I need this
so we can pass the zip to build hooks, letting us skip I/O and do the nodejs
env injection a lot easier.

Love it. Much clearer now.

authors: mthenw tj

repo: apex/apex


text:
Bubble Chart: Should allow for a minimum bubble size

Is your feature request related to a problem? Please describe.
I am trying to display bubbles with Z values in the range [0,1]. If the Z value is 0, then no bubble is drawn at all.
Describe the solution you'd like
Ideally, I'd be able to set a minimum size and the drawn radius would never shrink below that.
Describe alternatives you've considered
As a workaround, I am banding my data into quintile buckets and sending a value for the bucket. E.g., [0,.2] gets 1, (.2,.4] gets 2, etc.. Use the actual values to format a custom tooltip.

Duplicate of #604
Thread continued in #604

authors: BiggerNoise junedchhipa


text:
Ensure that events defined in chart options are called too.

Currently vue3-apexcharts defines the same callback for each of apexcharts events, and those callbacks just calls "emit()" so that the e.g. @mousemove='some-handler'-style definition works:
https://github.com/apexcharts/vue3-apexcharts/blob/02b0a1af917c78d791087a6fc6dbad379e04dbf9/src/vue3-apexcharts.js#L137-L138
But the docs don't mention this limitation anywhere, so most people unsuccessfully define events in the chart options like the apexcharts docs describe.
This fix calls any defined events in the chart options after the emit() is called, so the chart options' events will work.
fix https://github.com/apexcharts/vue3-apexcharts/issues/20

Has this been released yet ? I'm working with "apexcharts": "^3.49.2" and "vue3-apexcharts": "^1.5.3" and it seems to not be there yet ?

This is yet to be released.

@junedchhipa any updates on a new release for this? Just ran into this exact issue.

released vue3-apexcharts@v1.6.0

This commit introduced the issues #121, #120, #119, #118, (maybe #117) and #115.
Maybe it should be reverted or a fix is needed.

This commit has caused many regressions in v1.6.0 which is now unstable.
I agree with @ggrote this should be reverted or fixed, and v1.6.0 needs this patch to make the latest package version stable again.

released vue3-apexcharts@1.7.0

@junedchhipa  Release v1.7.0 did not address the issue introduced in this commit.  Both versions 1.6.0 and 1.7.0 now contain this regression.  I would suggest reverting the entirety of changes in v1.6.0 until these can be regression tested against all issues below, which remain unresolved.

This commit introduced the issues #121, #120, #119, #118, (maybe #117) and #115. Maybe it should be reverted or a fix is needed.

I would suggest reverting the entirety of changes in v1.6.0 until these can be regression tested against all issues below, which remain unresolved.

My changes did not introduce any issues. If you revert the config event change and keep my changes everything works fine.

authors: Zippanova ggrote junedchhipa leoatfentech rabrowne85 tiegz


text:
Expose actor id in container when running Docker build

Hey there,
Not sure this is the right place to create the issue but what I'm asking happens on your servers and is related to Docker :).
I use a monorepo with NPM workspaces, and I have issues deploying my actor because of it.
In order to selectively install my actor using npm install --workspace=my-actor, I would need the actor id to be available in the Dockerfile. Is it something you could add?
This change combined to this one https://github.com/apify/apify-cli/issues/277 would basically enable basic support for NPM workspaces monorepo.
Love the project, keep going 👍

@pocesar answered this on Discord.
Solution:

Tick the Apply environment variables also to build process option in console
Store the environment variable in apify.json
Declare ARG MY_VAR in Dockerfile

repo: apify/apify-actor-docker


text:
Can't install adapter because limitation with fusio/engine

Hello, i am trying to install this adapter but on the last version 1.9.4 from composer, not allow me to install this plugin.
Logs:
sudo -u wwwrun composer require fusio/adapter-laravel

Warning from https://repo.packagist.org: You are using an outdated version of Composer. Composer 2.0 is now available and you should upgrade. See https://getcomposer.org/2
Using version ^4.0 for fusio/adapter-laravel
./composer.json has been updated
Loading composer repositories with package information
Warning from https://repo.packagist.org: You are using an outdated version of Composer. Composer 2.0 is now available and you should upgrade. See https://getcomposer.org/2
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for fusio/adapter-laravel ^4.0 -> satisfiable by fusio/adapter-laravel[v4.0.0].
    - Conclusion: remove fusio/engine v3.3.2
    - Conclusion: don't install fusio/engine v3.3.2
    - fusio/adapter-laravel v4.0.0 requires fusio/engine ^4.0 -> satisfiable by fusio/engine[v4.0.0, v4.0.1, v4.0.2, v4.0.3, v4.0.4, v4.0.5].
    - Can only install one of: fusio/engine[v4.0.0, v3.3.2].
    - Can only install one of: fusio/engine[v4.0.1, v3.3.2].
    - Can only install one of: fusio/engine[v4.0.2, v3.3.2].
    - Can only install one of: fusio/engine[v4.0.3, v3.3.2].
    - Can only install one of: fusio/engine[v4.0.4, v3.3.2].
    - Can only install one of: fusio/engine[v4.0.5, v3.3.2].
    - Installation request for fusio/engine (locked at v3.3.2) -> satisfiable by fusio/engine[v3.3.2].

Installation failed, reverting ./composer.json to its original content.

Hi, since we are currently working on Fusio 2.0 you need to explicit install an older version of this library, please try to use explicit version v0.2.0:
composer require fusio/adapter-laravel v0.2.0

ok, thank you very much, i use the lastest RC and everything working

ok, thank you very much, i use the lastest RC and everything working

authors: DevDorrejo chriskapp

repo: apioo/fusio-adapter-laravel


text:
[Bug]: stream gets stopped when app goes to background state

Version
v2.0.0
Which operating systems have you used?

[X] Android
[ ] iOS

Environment that reproduces the issue
Oneplus 8T
android 13
Is it reproducible in the example application?
Yes
RTMP Server

Reproduction steps

start the stream
take the app to background
stream gets stopped

Expected result
on going to background state, the stream should not stop
Actual result
the stream gets stopped as soon as user takes the app to background
Additional context
No response
Relevant logs output
No response

Hi,
It is on purpose.
It is not clear if camera and microphone could be used in background in a foreground service. What is clear is that it is not possible for older Android version.
There are multiple topics on stackoverflow about this: https://stackoverflow.com/questions/67284842/camera2-cameramanager-opencamera-exception-from-time-to-time-on-some-devices

Hi, It is on purpose. It is not clear if camera and microphone could be used in background in a foreground service. What is clear is that it is not possible for older Android version.
There are multiple topics on stackoverflow about this: https://stackoverflow.com/questions/67284842/camera2-cameramanager-opencamera-exception-from-time-to-time-on-some-devices

I'm intended to make a Picture in Picture feature for android, for that i guess camera and microphone will work in background. Is there any way to do now?

There is no background support for @api.video/react-native-livestream.

There is no background support for @api.video/react-native-livestream.

are you planning to do it in future?

Maybe. Just not right now.
Are you 100% sure you need background for PiP?

Maybe. Just not right now. Are you 100% sure you need background for PiP?

yes when the app is put to background state a PiP should appear showing the stream, that's the requiremnet.

Could you provide a sample so we can test this quickly?

authors: ThibaultBee talhatsk


text:
Introduce platform-dependent assets

Currently we have just one assets folder.
There are good reasons to have platform-dependent asset folders. For example, Conga, when it's a Tatin packages, could bring just the DLLs that make sense for the current platform, rather than all of them.

It appears to be very difficult to implement this in a generalized way.
I suggest implementing a way that allows a package developer to execute her own code as part of the package installation process. That would at least allow late adjustments and the like, like deleting stuff that is not required by the package on the current platform.

This can already be done via the lx property.

repo: aplteam/Tatin


text:
Bagaimana menambahkan ssl?

Terimakasih sebelumnya buat otomatisasinya. Apakah mungkin untuk menambahkan ssl agar bisa akses https?Kalau bisa tambahin dong gan.☺☺

InsyaAllah kalau senggang yah gan, semoga bermanfaat 🙂

authors: dimzhen wadahkode

repo: apolbox/termux-webserver


text:
Support for AppSync Lambda Resolver

I would like to add support for the AppSync Lambda Resolver.
Lambda is called with the following type in AppSync.
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/aws-lambda/trigger/appsync-resolver.d.ts#L3-L6
It is possible to implement a resolver without using Appolo. However, I would appreciate it if it could be implemented using the same interface.
Thank you for considering this.

Will be supported with #67 which will allow for custom defined handlers

#67 is now ready for review if you want to take a look. Look at the README.md updates to see how this might be implemented.

Thanks for the quick reply.
I have looked at the README for #67.
It certainly looks like it could be handled by creating a custom request handler.
I will try it later.
And I close this issue.
Thank you very much in advance.

authors: BlenderDude horiuchi


text:
namespace名称不能大于32个字符的bug

如图所示：

说明：
在appId=a，创建了一个私有的dynamic_logger是可以的；
在appId=b，再次创建私有的dynamic_logger时候，页面报错！估计是js校验或者页面切换导致的问题。

case先关闭了，如还有问题，可以提供更多信息，或进群交流。

hi
部署的apollo 2.1.0 版本  也出现了这个问题 我需要怎么解决呢

hi 部署的apollo 2.1.0 版本 也出现了这个问题 我需要怎么解决呢

最后你怎么处理的呀？

authors: HadwinLing Saintchi hemkvo nobodyiam

repo: apolloconfig/apollo


text:
Propagate CacheKeyResolver changes back to the apollo-sample module

Realized that we forgot to propagate changes made in #458 back to the apollo-sample module due to which latest builds in #475 & #469 are failing (see this for the exact location of error in the build logs).
@sav007 Maybe you can help us with this one?

Maybe we should fix through #441.

Yeah makes sense. Let me see if I can open a PR.

authors: VisheshVadhera marwanad

repo: apollographql/apollo-android


text:
README not working: subgraph service doesn't start

after make demo, I get this crash log inside the subgraph services (like inventory, for example):
/usr/src/app/node_modules/@apollo/federation/dist/composition/validate/preNormalization/tagDirective.js:10

const errorsMessagesToFilter = directives_1.federationDirectives.map((directive) => `Unknown directive "@${directive.name}".`);

                                                                 ^

TypeError: Cannot read properties of undefined (reading 'map')

    at Object.<anonymous> (/usr/src/app/node_modules/@apollo/federation/dist/composition/validate/preNormalization/tagDirective.js:10:66)

    at Module._compile (node:internal/modules/cjs/loader:1101:14)

    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)

    at Module.load (node:internal/modules/cjs/loader:981:32)

    at Function.Module._load (node:internal/modules/cjs/loader:822:12)

    at Module.require (node:internal/modules/cjs/loader:1005:19)

    at require (node:internal/modules/cjs/helpers:102:18)

    at Object.<anonymous> (/usr/src/app/node_modules/@apollo/federation/dist/composition/validate/preNormalization/index.js:6:22)

    at Module._compile (node:internal/modules/cjs/loader:1101:14)

    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)

How can I fix this? Thanks!

@6peterlu this was an out-of-date dependency that was fixed on 11/22/21 in https://github.com/apollographql/supergraph-demo/commit/d5faebafc7f4c9bc7a3443374f41f33238656cf8. Sorry for the inconvenience.
Underlying fix in composition: https://github.com/apollographql/federation/blob/version-0.x/federation-js/CHANGELOG.md#v0337

repo: apollographql/supergraph-demo


text:
add custom class to hide duplicated docs notification

Summary
Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"
What are the specific steps to test this change?
For example:

Run the website and log in as an admin
Open a piece manager modal and select several pieces
Click the "Archive" button on the top left of the manager and confirm that it should proceed
Check that all pieces have been archived properly

What kind of change does this PR introduce?
(Check at least one)

[ ] Bug fix
[ ] New feature
[ ] Refactor
[ ] Documentation
[ ] Build-related changes
[ ] Other

Make sure the PR fulfills these requirements:

[ ] It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
[ ] The changelog is updated
[ ] Related documentation has been updated
[ ] Related tests have been updated

If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Other information:

tests running https://github.com/apostrophecms/testbed/pull/208

repo: apostrophecms/import-export


text:
Incompatible Plug-ins Disabled

After updating my Mail app, this is what I get every time I enable the plugin. Any workaround or solution?

Mail has disabled the following plug-ins:
MailTrackerBlocker.mailbundle
Contact the makers of these plug-ins for versions that are compatible with Mail 14.0.

What version of MailTrackerBlocker are you on? macOS version? Apple silicon or intel mac?

Thank you for the followup. I actually decided to uninstall and reinstall and it started working again. May I ask if the plugin update itself automatically or not? If not, is there away to enable that?

On Dec 27, 2020, at 5:18 AM, Aaron Lee notifications@github.com wrote:
What version of MailTrackerBlocker are you on? macOS version? Apple silicon or intel mac?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/apparition47/MailTrackerBlocker/issues/10#issuecomment-751455240, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANOVWFVSDIPR6YYCKYDJPGTSW4JYRANCNFSM4VKXAKMA.

No internal update mechanism now but you can use brew to keep it updated.


text:
Sample just a kidding!!

I dont konw how to create a connection with devices through appium，and  how to set start activity？？？how to use Api like ‘swipe’ and 'click', i am still confuse when watched whole docs,pls codeing more and let us how to use it in a more complex app,not just use in a browser to access a website.Please!!!!the amazing tool looks like so helpless in your doc.what a pity

Did you try to run sample code in https://github.com/appium/appium/tree/master/sample-code ?
This repository is outdated. (Already this is in appium-boneyard)
https://discuss.appium.io also helps you to ask questions.

repo: appium-boneyard/sample-code


text:
ERROR CUPS Unable to get PPD file

Please I need some help, I have my print server on a server with oracle Solaris 11.3 for sparc, for some reason the 12 printers stop printing and right now I just have 2 of them working, this happen eventualy and I donpt know what is the problem. these is the error_log
W [15/Jul/2019:23:30:22 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [15/Jul/2019:23:38:20 +0500] [CGI] Bad SNMP packet from 10.10.207.16: variable-bindings uses indefinite lengthDEBUG2: cgiCopyTemplateLang(tmpl="
E [15/Jul/2019:23:38:20 +0500] [cups-deviced] PID 6525 (smb) stopped with status 1!
E [15/Jul/2019:23:39:38 +0500] [cups-deviced] PID 6678 (smb) stopped with status 1!
W [16/Jul/2019:05:32:11 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:05:33:52 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:05:34:38 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:05:49:37 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:05:50:15 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:05:52:49 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:08:11 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:10:26 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:12:00 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:13:16 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:19:25 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:21:33 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:25:36 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:32:39 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:45:48 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:50:42 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:52:46 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:53:45 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:54:50 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:06:56:29 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:07:03:05 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:07:06:02 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:07:07:03 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:07:09:53 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:07:37:54 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:07:40:26 +0500] [cups-deviced] PID 9488 (smb) stopped with status 1!
W [16/Jul/2019:07:44:44 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:07:58:41 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:00:19 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:02:47 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:04:01 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:08:09:25 +0500] [CGI] Bad SNMP packet from DEBUG2: 10.10.207.16  Starting at file position 804...
E [16/Jul/2019:08:09:25 +0500] [cups-deviced] PID 12979 (smb) stopped with status 1!
W [16/Jul/2019:08:11:45 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:12:19 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:16:24 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:18:46 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:19:28 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:22:19 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:23:59 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:26:14 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:28:01 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:29:57 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:31:12 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:34:30 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:36:07 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:37:37 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:39:07 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:08:52:15 +0500] [cups-deviced] PID 22398 (smb) stopped with status 1!
W [16/Jul/2019:08:52:16 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:08:53:58 +0500] [CGI] Unable to get PPD file /printers/PRTPICKING02.ppd: 404 - Not Found
E [16/Jul/2019:08:53:59 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:08:53:59 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
E [16/Jul/2019:08:54:06 +0500] [CGI] Unable to get PPD file /printers/PRTPICKING02.ppd: 404 - Not Found
E [16/Jul/2019:08:54:07 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:08:54:07 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
W [16/Jul/2019:08:54:34 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:08:55:34 +0500] [CGI] Bad SNMP packet from 10.10.207.16: variable-bindings uses indefinite lengthDEBUG2:
E [16/Jul/2019:08:55:34 +0500] [cups-deviced] PID 22973 (smb) stopped with status 1!
W [16/Jul/2019:08:55:36 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:08:57:25 +0500] [cups-deviced] PID 23274 (smb) stopped with status 1!
W [16/Jul/2019:08:57:28 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:08:58:24 +0500] [cups-deviced] PID 23303 (smb) stopped with status 1!
W [16/Jul/2019:08:58:34 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:08:59:38 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:00:42 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:09:03:23 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:03:23 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
E [16/Jul/2019:09:03:33 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:03:33 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
W [16/Jul/2019:09:03:45 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:09:04:14 +0500] [CGI] Bad SNMP packet from DEBUG2:   10.10.207.16Returning at file position : variable-bindings uses indefinite length
E [16/Jul/2019:09:04:14 +0500] [cups-deviced] PID 23925 (smb) stopped with status 1!
E [16/Jul/2019:09:04:21 +0500] [CGI] Unable to get PPD file /printers/PRTPICKING02.ppd: 404 - Not Found
E [16/Jul/2019:09:04:21 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:04:21 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
E [16/Jul/2019:09:04:40 +0500] [CGI] Bad SNMP packet from DEBUG2: 10.10.207.16  : variable-bindings uses indefinite length
E [16/Jul/2019:09:04:40 +0500] [cups-deviced] PID 23952 (smb) stopped with status 1!
E [16/Jul/2019:09:04:53 +0500] [CGI] Unable to get PPD file /printers/PRTPICKING11.ppd: 404 - Not Found
E [16/Jul/2019:09:04:53 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:04:53 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
W [16/Jul/2019:09:06:12 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:07:33 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:09:12:48 +0500] [cups-deviced] PID 24329 (smb) stopped with status 1!
E [16/Jul/2019:09:13:56 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:13:56 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
E [16/Jul/2019:09:14:06 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:14:06 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
W [16/Jul/2019:09:14:10 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:14:45 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:16:21 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:17:41 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:18:35 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:19:11 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:21:10 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:21:54 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:22:26 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:23:01 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:09:23:39 +0500] Returning IPP client-error-not-authorized for Print-Job (ipp://10.10.205.143:631/printers/rec2) from 10.10.205.143
W [16/Jul/2019:09:24:10 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:25:11 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:26:46 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:09:28:08 +0500] Returning IPP client-error-not-authorized for Print-Job (ipp://10.10.205.143:631/printers/rec2) from 10.10.205.143
W [16/Jul/2019:09:28:40 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:31:29 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:32:20 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:32:56 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:09:35:39 +0500] Returning IPP client-error-not-authorized for Print-Job (ipp://uiortbidbp02:631/printers/rec2) from 10.10.205.143
W [16/Jul/2019:09:36:16 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:38:42 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:39:37 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:09:41:08 +0500] [cups-deviced] PID 27694 (smb) stopped with status 1!
E [16/Jul/2019:09:41:27 +0500] [CGI] Unable to get PPD file /printers/REC1.ppd: 404 - Not Found
E [16/Jul/2019:09:41:27 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:41:27 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
E [16/Jul/2019:09:41:38 +0500] [CGI] Unable to get PPD file /printers/REC1.ppd: 404 - Not Found
E [16/Jul/2019:09:41:38 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:41:38 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
W [16/Jul/2019:09:42:40 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:43:13 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:44:26 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:45:10 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:47:51 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:49:21 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:50:01 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
E [16/Jul/2019:09:52:20 +0500] [cups-deviced] PID 28777 (smb) stopped with status 1!
E [16/Jul/2019:09:52:51 +0500] [CGI] Unable to get PPD file /printers/PRTPICKING02.ppd: 404 - Not Found
E [16/Jul/2019:09:52:52 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:52:52 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
E [16/Jul/2019:09:53:01 +0500] [CGI] Unable to get PPD file /printers/PRTPICKING02.ppd: 404 - Not Found
E [16/Jul/2019:09:53:01 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/kyocera_ppd_8.2.txt"!
E [16/Jul/2019:09:53:01 +0500] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
W [16/Jul/2019:09:55:32 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:56:48 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:57:23 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:58:21 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:09:59:59 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:06:51 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:07:22 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:13:08 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:16:45 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:18:51 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:21:15 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:22:41 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:23:40 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:24:23 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:26:29 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:27:26 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:28:37 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:31:16 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:32:02 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:32:34 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:34:54 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:35:52 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:37:19 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:39:16 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:40:44 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:42:30 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:44:09 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:45:28 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:47:37 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:49:58 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:51:16 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:51:52 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!
W [16/Jul/2019:10:53:23 +0500] Notifier for subscription 42 (rss:///.rss?max_events=20) went away, retrying!

@VeronicaMinango That sounds like the PPD files were deleted from the /etc/cups/ppd directory...

No response from reporter, closing...

Hi, I have a similar problem with a samsung c430w, and /etc/cups/pppd is empty. How do I get the files back?

authors: VeronicaMinango michaelrsweet slorquet

repo: apple/cups


text:
Group and label option groups in the help screen

Option groups are currently just splatted into the rest of the declared arguments for a command. This is sometimes fine, but often it would be nice if option groups were separated and labeled, which would (a) help readability in complex commands and (b) help users understand which options carry over across multiple subcommands.
For example, for declarations like this:
struct Options: ParsableArguments {
    @Flag(help: "Display extra information while processing.")
    var verbose = false

    @Option(help: "The number of extra lines to show.")
    var extraLines = 0
}

struct Example: ParsableCommand {
    @OptionGroup(title: "Shared Options")
    var group: Options

    @Flag(help: "Parse as a binary file.")
    var parseAsBinary = false

    @Argument(help: "The input file.")
    var inputFile: String?
}

The help screen could look something like:

% example --help
USAGE: example [--verbose] [--extra-lines <extra-lines>] [--parse-as-binary] <input-file>

ARGUMENTS:
  <input-file>            The input file.

OPTIONS:
  --parse-as-binary       Parse as a binary file.

SHARED OPTIONS:
  --verbose               Display extra information while processing.
  --extra-lines <extra-lines>
                          The number of extra lines to show. (default: 0)

  -h, --help              Show help information.

It would probably also be helpful to be able to hide an entire option group from the help for a command.

repo: apple/swift-argument-parser


text:
Fix minor import syntax issue

Bug/issue #, if applicable: 48833910
Summary
Fixes a very minor syntax issue with a recently added import statement to use the docc-render alias instead of @, which could cause issues for other applications using this project as a component library.
(This import statement was recently added with #34)
Testing
Steps:

Ensure all unit tests still pass and application still builds.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] ~Added tests~
[X] Ran npm test, and it succeeded
[X] Updated documentation if necessary

@swift-ci test

repo: apple/swift-docc-render


text:
Organize and elaborate on flag/option description in convert command help text

Bug/issue #, if applicable:
Summary
This reorganizes the docc convert --help output to group command line flags and options by category and adds descriptions to many flags and options to provide additional information on how to use them.
Additionally, this makes the following smaller changes:

The preview command has clarified usage text and a discussion. Unfortunately the organization from the coverage command doesn't cary over.
Many long-time-deprecated command line flags and options now print a warning when used.
The top-level index command is hidden (but still functional). It has long been available as a process-archive subcommand.
The documentation coverage flags and options have been renamed ("--level" and "--kinds" was overly general names) and better documented in their help text.
It's no longer necessary to pass a both "--experimental-documentation-coverage" and "--coverage-summary-level" to enable the default level coverage output. (Previously, passing only "--experimental-documentation-coverage" silently did nothing).

Dependencies
None
Testing

Run swift run docc convert --help and inspect the output
Run swift run docc preview --help and inspect the output
Run swift run docc --help and inspect the output

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

~[ ] Added tests~
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

With these changes, the help output for docc convert --help looks like this
OVERVIEW: Convert documentation markup, assets, and symbol information into a documentation archive.

When building documentation for source code, the 'convert' command is commonly invoked by other tools as part of a build workflow. Such build
workflows can perform tasks to extract symbol graph information and may infer values for 'docc' flags and options from other build configuration.

When building documentation for a catalog that only contain articles or tutorial content, interacting with the 'docc convert' command directly can be
a good alternative to using DocC via a build workflow.

USAGE: docc convert [<catalog-path>] [--additional-symbol-graph-dir <symbol-graph-dir>]
       docc convert [<catalog-path>] [--additional-symbol-graph-dir <symbol-graph-dir>] [--output-dir <output-dir>]
       docc convert [<catalog-path>] [--additional-symbol-graph-dir <symbol-graph-dir>] [--output-dir <output-dir>] [<availability-options>] [<diagnostic-options>] [<source-repository-options>] [<hosting-options>] [<info-plist-fallbacks>] [<feature-flags>] [<other-options>]

INPUTS & OUTPUTS:
  <docc-catalog-path>     Path to a '.docc' documentation catalog directory.
  --additional-symbol-graph-dir <additional-symbol-graph-dir>
                          A path to a directory of additional symbol graph files.
  -o, --output-path, --output-dir <output-path>
                          The location where the documentation compiler writes the built documentation.

AVAILABILITY OPTIONS:
  --platform <platform>   Specify information about the current release of a platform.
        Each platform's information is specified via separate "--platform" values using the following format: "name={platform name},version={semantic
        version}".
        Optionally, the platform information can include a 'beta={true|false}' component. If no beta information is provided, the platform is
        considered not in beta.

DIAGNOSTIC OPTIONS:
  --warnings-as-errors    Treat warnings as errors
  --ide-console-output, --emit-fixits
                          Format output to the console intended for an IDE or other tool to parse.
  --diagnostics-file, --diagnostics-output-path <diagnostics-file>
                          The location where the documentation compiler writes the diagnostics file.
        Specifying a diagnostic file path implies '--ide-console-output'.
  --diagnostic-filter, --diagnostic-level <diagnostic-filter>
                          Filter diagnostics with a lower severity than this level.
        This option is ignored if `--analyze` is passed.

        This filter level is inclusive. If a level of 'note' is specified, diagnostics with a severity up to and including 'note' will be printed.
        The supported diagnostic filter levels are:
         - error
         - warning
         - note, info, information
         - hint, notice
  --analyze               Include 'note'/'information' level diagnostics in addition to warnings and errors.

SOURCE REPOSITORY OPTIONS:
  --checkout-path <checkout-path>
                          The root path on disk of the repository's checkout.
  --source-service <source-service>
                          The source code service used to host the project's sources.
        Required when using '--source-service-base-url'. Supported values are 'github', 'gitlab', and 'bitbucket'.
  --source-service-base-url <source-service-base-url>
                          The base URL where the source service hosts the project's sources.
        Required when using '--source-service'. For example, 'https://github.com/my-org/my-repo/blob/main'.

HOSTING OPTIONS:
  --transform-for-static-hosting/--no-transform-for-static-hosting
                          Produce a DocC archive that supports static hosting environments. (default: --transform-for-static-hosting)
  --hosting-base-path <hosting-base-path>
                          The base path your documentation website will be hosted at.
        For example, if you deploy your site to 'example.com/my_name/my_project/documentation' instead of 'example.com/documentation', pass
        '/my_name/my_project' as the base path.

INFO.PLIST FALLBACKS:
  --fallback-display-name, --display-name <fallback-display-name>
                          A fallback display name if no value is provided in the documentation catalogs's Info.plist file.
        If no display name is provided in the catalogs's Info.plist file or via the '--fallback-display-name' option, DocC will infer a display name
        from the documentation catalog base name or from the module name from the symbol graph files provided via the '--additional-symbol-graph-dir'
        option.
  --fallback-bundle-identifier, --bundle-identifier <fallback-bundle-identifier>
                          A fallback bundle identifier if no value is provided in the documentation catalogs's Info.plist file.
        If no bundle identifier is provided in the catalogs's Info.plist file or via the '--fallback-bundle-identifier' option, DocC will infer a
        bundle identifier from the display name.
  --default-code-listing-language <default-code-listing-language>
                          A fallback default language for code listings if no value is provided in the documentation catalogs's Info.plist file.
  --fallback-default-module-kind <fallback-default-module-kind>
                          A fallback default module kind if no value is provided in the documentation catalogs's Info.plist file.
        If no module kind is provided in the catalogs's Info.plist file or via the '--fallback-default-module-kind' option, DocC will display the
        module kind as a "Framework".

DOCUMENTATION COVERAGE (EXPERIMENTAL):
  --experimental-documentation-coverage
                          Generate documentation coverage output.
        Detailed documentation coverage information will be written to 'documentation-coverage.json' in the output directory.
  --coverage-summary-level <symbol-kind>
                          The level of documentation coverage information to write on standard out. (default: brief)
        The '--coverage-summary-level' level has no impact on the information in the 'documentation-coverage.json' file.
        The supported coverage summary levels are 'brief' and 'detailed'.
  --coverage-symbol-kind-filter <symbol-kind>
                          Filter documentation coverage to only analyze symbols of the specified symbol kinds.
        Specify a list of symbol kind values to filter the documentation coverage to only those types symbols.
        The supported symbol kind values are: associated-type, class, dictionary, enumeration, enumeration-case, function, global-variable,
        http-request, initializer, instance-method, instance-property, instance-subcript, instance-variable, module, operator, protocol, structure,
        type-alias, type-method, type-property, type-subscript, typedef

FEATURE FLAGS:
  --experimental-enable-custom-templates
                          Allows for custom templates, like `header.html`.
  --enable-inherited-docs Inherit documentation for inherited symbols
  --allow-arbitrary-catalog-directories
                          Experimental: allow catalog directories without the `.docc` extension.
  --emit-digest           Write additional metadata files to the output directory.
  --emit-lmdb-index       Writes an LMDB representation of the navigator index to the output directory.
        A JSON representation of the navigator index is emitted by default.

OPTIONS:
  -h, --help              Show help information.

After talking to some people about this I made some additional refinements to the order of these options:

Moved the Diagnostic options group below the Source Repository and Hosting options groups
Ordered the options in the Diagnostic Options group alphabetically
Moved the default code listing language option to the top of the Info.plist fallback options group.

With those changes the help text now looks like this:
OVERVIEW: Convert documentation markup, assets, and symbol information into a documentation archive.

When building documentation for source code, the 'convert' command is commonly invoked by other tools as part of a build workflow. Such
build workflows can perform tasks to extract symbol graph information and may infer values for 'docc' flags and options from other build
configuration.

When building documentation for a catalog that only contain articles or tutorial content, interacting with the 'docc convert' command
directly can be a good alternative to using DocC via a build workflow.

USAGE: docc convert [<catalog-path>] [--additional-symbol-graph-dir <symbol-graph-dir>]
       docc convert [<catalog-path>] [--additional-symbol-graph-dir <symbol-graph-dir>] [--output-dir <output-dir>]
       docc convert [<catalog-path>] [--additional-symbol-graph-dir <symbol-graph-dir>] [--output-dir <output-dir>] [<availability-options>] [<diagnostic-options>] [<source-repository-options>] [<hosting-options>] [<info-plist-fallbacks>] [<feature-flags>] [<other-options>]

INPUTS & OUTPUTS:
  <docc-catalog-path>     Path to a '.docc' documentation catalog directory.
  --additional-symbol-graph-dir <additional-symbol-graph-dir>
                          A path to a directory of additional symbol graph files.
  -o, --output-path, --output-dir <output-path>
                          The location where the documentation compiler writes the built documentation.

AVAILABILITY OPTIONS:
  --platform <platform>   Specify information about the current release of a platform.
        Each platform's information is specified via separate "--platform" values using the following format: "name={platform
        name},version={semantic version}".
        Optionally, the platform information can include a 'beta={true|false}' component. If no beta information is provided, the platform
        is considered not in beta.

SOURCE REPOSITORY OPTIONS:
  --checkout-path <checkout-path>
                          The root path on disk of the repository's checkout.
  --source-service <source-service>
                          The source code service used to host the project's sources.
        Required when using '--source-service-base-url'. Supported values are 'github', 'gitlab', and 'bitbucket'.
  --source-service-base-url <source-service-base-url>
                          The base URL where the source service hosts the project's sources.
        Required when using '--source-service'. For example, 'https://github.com/my-org/my-repo/blob/main'.

HOSTING OPTIONS:
  --hosting-base-path <hosting-base-path>
                          The base path your documentation website will be hosted at.
        For example, if you deploy your site to 'example.com/my_name/my_project/documentation' instead of 'example.com/documentation', pass
        '/my_name/my_project' as the base path.
  --transform-for-static-hosting/--no-transform-for-static-hosting
                          Produce a DocC archive that supports static hosting environments. (default: --transform-for-static-hosting)

DIAGNOSTIC OPTIONS:
  --analyze               Include 'note'/'information' level diagnostics in addition to warnings and errors.
  --diagnostics-file, --diagnostics-output-path <diagnostics-file>
                          The location where the documentation compiler writes the diagnostics file.
        Specifying a diagnostic file path implies '--ide-console-output'.
  --diagnostic-filter, --diagnostic-level <diagnostic-filter>
                          Filter diagnostics with a lower severity than this level.
        This option is ignored if `--analyze` is passed.

        This filter level is inclusive. If a level of 'note' is specified, diagnostics with a severity up to and including 'note' will be
        printed.
        The supported diagnostic filter levels are:
         - error
         - warning
         - note, info, information
         - hint, notice
  --ide-console-output, --emit-fixits
                          Format output to the console intended for an IDE or other tool to parse.
  --warnings-as-errors    Treat warnings as errors

INFO.PLIST FALLBACKS:
  --default-code-listing-language <default-code-listing-language>
                          A fallback default language for code listings if no value is provided in the documentation catalogs's Info.plist
                          file.
  --fallback-display-name, --display-name <fallback-display-name>
                          A fallback display name if no value is provided in the documentation catalogs's Info.plist file.
        If no display name is provided in the catalogs's Info.plist file or via the '--fallback-display-name' option, DocC will infer a
        display name from the documentation catalog base name or from the module name from the symbol graph files provided via the
        '--additional-symbol-graph-dir' option.
  --fallback-bundle-identifier, --bundle-identifier <fallback-bundle-identifier>
                          A fallback bundle identifier if no value is provided in the documentation catalogs's Info.plist file.
        If no bundle identifier is provided in the catalogs's Info.plist file or via the '--fallback-bundle-identifier' option, DocC will
        infer a bundle identifier from the display name.
  --fallback-default-module-kind <fallback-default-module-kind>
                          A fallback default module kind if no value is provided in the documentation catalogs's Info.plist file.
        If no module kind is provided in the catalogs's Info.plist file or via the '--fallback-default-module-kind' option, DocC will
        display the module kind as a "Framework".

DOCUMENTATION COVERAGE (EXPERIMENTAL):
  --experimental-documentation-coverage
                          Generate documentation coverage output.
        Detailed documentation coverage information will be written to 'documentation-coverage.json' in the output directory.
  --coverage-summary-level <symbol-kind>
                          The level of documentation coverage information to write on standard out. (default: brief)
        The '--coverage-summary-level' level has no impact on the information in the 'documentation-coverage.json' file.
        The supported coverage summary levels are 'brief' and 'detailed'.
  --coverage-symbol-kind-filter <symbol-kind>
                          Filter documentation coverage to only analyze symbols of the specified symbol kinds.
        Specify a list of symbol kind values to filter the documentation coverage to only those types symbols.
        The supported symbol kind values are: associated-type, class, dictionary, enumeration, enumeration-case, function, global-variable,
        http-request, initializer, instance-method, instance-property, instance-subcript, instance-variable, module, operator, protocol,
        structure, type-alias, type-method, type-property, type-subscript, typedef

FEATURE FLAGS:
  --experimental-enable-custom-templates
                          Allows for custom templates, like `header.html`.
  --enable-inherited-docs Inherit documentation for inherited symbols
  --allow-arbitrary-catalog-directories
                          Experimental: allow catalog directories without the `.docc` extension.
  --emit-digest           Write additional metadata files to the output directory.
  --emit-lmdb-index       Writes an LMDB representation of the navigator index to the output directory.
        A JSON representation of the navigator index is emitted by default.

OPTIONS:
  -h, --help              Show help information.

I suggest listing only --port-number and <docc-catalog-path> as arguments to the docc preview command to improve clarity, otherwise it looks pretty good.

I suggest listing only --port-number and <docc-catalog-path> as arguments to the docc preview command to improve clarity, otherwise it looks pretty good.

I haven't found a way to customize the help text for the preview command without repeating the entire convert command and all its options inline. Setting the nested convert command's visibility to hidden or private doesn't hide it from the help text and I don't see any way to customize the command help text as a whole.
The only things I seem to be able to do is to move the port argument above the other unordered arguments.

I created a small reproducer and filed https://github.com/apple/swift-argument-parser/issues/585 about the issue with the organization of the options for the preview command.

@swift-ci please test

@swift-ci please test

authors: d-ronnqvist sofiaromorales

repo: apple/swift-docc


text:
Expanded options

This adds methods to RegexComponent for the remainder of the regex options, and passes the current MatchingOptions further down into the consumers so that the correct behavior can be used.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test


text:
Ensure fireChannelActive(...) is always called before fireChannelActi…

…ve(...)
Motivation:
fireChannelActive(...) must always be called before fireChannelActive(...) which was not the cause all of the times as once ChannelOptions were applied to the accepted SocketChannel it was possible that read0() was called during this. This would then lead to an assert error as it tried to reregister on the Selector before we ever registered.
Modifications:

Ensure we only try to reregister once we have registered to the Selector
Only trigger read0() or pauseRead0() if the autoRead value actually changed
Add unit test

Result:
Correct order of events and no crashes.

Thanks @vlm for reporting

@Lukasa lol... amend the commit message. I guess it was a bit late yesterday 🤦♂

repo: apple/swift-nio


text:
Disable gpgsign in test repos

Previously, if you had this option set in your global gitconfig, it would be inherited for these repos, which would make running git commit fail, and subsequently the tests would crash. Now we explicitly disable this for the example repo.
I'm not sure if we want to keep adding one offs when other cases like this come up. I looked through man git for a way to not inherit/ignore the global config but didn't see anything (expect for ignoring the system one)

Interesting. Possibly we could commit a dummy git repo to the fixtures and use that for the tests or something.

authors: keith mxcl

repo: apple/swift-package-manager


text:
[PackageLoading] Diagnose invalid values of build settings

rdar://problem/52395869

@swift-ci smoke test


text:
Set 'createGitRepo: false' in test fixtures

Motivation:
Started seeing Git related errors in package collection tests.
Modifications:
Pass createGitRepo: false to fixture since the tests don't involve Git repos.

@swift-ci please smoke test


text:
Keychain search to return all matches

Motivation:
A registry URL (i.e., same scheme, host, and port) can have multiple entries in Keychain. Currently we only ask Keychain to return one match when doing a search, but that might not be the one we want.
Modifications:

Have Keychain search return all matches
Sort the matches by modification timestamp
Return the most recently modified match

rdar://112556752

@swift-ci please smoke test

@swift-ci please smoke test Linux

@swift-ci please smoke test Linux


text:
Fix another XCBuild compatibility issue

Similar to #6752, there was another case where we needed the new setting.
rdar://113157040

@swift-ci please smoke test

Windows CI is failing with
$ "not" "t:\\1\\bin\\swift.exe" "-module-cache-path" "T:\1\swift-test-results\x86_64-unknown-windows-msvc\clang-module-cache" "-swift-version" "4" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 9999:macOS 9999, iOS 9999, watchOS 9999, tvOS 9999" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.0:macOS 10.14.4, iOS 12.2, watchOS 5.2, tvOS 12.2" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.1:macOS 10.15, iOS 13.0, watchOS 6.0, tvOS 13.0" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.2:macOS 10.15.4, iOS 13.4, watchOS 6.2, tvOS 13.4" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.3:macOS 11.0, iOS 14.0, watchOS 7.0, tvOS 14.0" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.4:macOS 11.3, iOS 14.5, watchOS 7.4, tvOS 14.5" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.5:macOS 12.0, iOS 15.0, watchOS 8.0, tvOS 15.0" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.6:macOS 12.3, iOS 15.4, watchOS 8.5, tvOS 15.4" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.7:macOS 13.0, iOS 16.0, watchOS 9.0, tvOS 16.0" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.8:macOS 13.3, iOS 16.4, watchOS 9.4, tvOS 16.4" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.9:macOS 14.0, iOS 17.0, watchOS 10.0, tvOS 17.0" "-Xfrontend" "-define-availability" "-Xfrontend" "SwiftStdlib 5.10:macOS 9999, iOS 9999, watchOS 9999, tvOS 9999" "-libc" "MD" "-sdk" "" "-deprecated-integrated-repl" "C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swift\test\Driver\options-repl.swift"
$ "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe" "C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swift\utils\PathSanitizingFileCheck" "--allow-unused-prefixes" "--sanitize" "BUILD_DIR=T:/1/tools/swift" "--sanitize" "SOURCE_DIR=C:/Users/swift-ci/jenkins/workspace/swiftpm-PR-windows/swift" "--use-filecheck" "t:\1\bin\filecheck.exe" "--enable-windows-compatibility" "-check-prefix=REPL_NO_FILES" "C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swift\test\Driver\options-repl.swift"
$ ":" "RUN: at line 8"
$ "rm" "-rf" "T:\1\tools\swift\test-windows-x86_64\Driver\Output\options-repl.swift.tmp"
# command stderr:
Error: 'rm' command failed, [WinError 32] The process cannot access the file because it is being used by another process.
error: command failed with exit status: 1

--

********************
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.
FAIL: Swift(windows-x86_64) :: Driver/windows-link-job.swift (4601 of 9636)

that Windows failure seems sporadic, I saw it previously, but repeated Windows CI runs on other PRs made it go away sometimes. cc @compnerd

@swift-ci test windows

@swift-ci please smoke test linux

@MaxDesiatov yes - that would be sporadic - it is a file in use issue.

authors: MaxDesiatov compnerd neonichu


text:
Make CoreFoundation headers in resource dir optional for WebAssembly

Foundation is not integrated with build-script pipeline for WebAssembly yet, and it will be built as a SwiftPM package in the future. This commit makes CoreFoundation headers optional for WebAssembly for those reasons.

@swift-ci test

@swift-ci test macOS

@swift-ci test macOS

@swift-ci test macOS

repo: apple/swift-sdk-generator


text:
Build lld when no prebuilt binaries are available

Resolves https://github.com/apple/swift-sdk-generator/issues/9.
Resolves rdar://115890915.

@swift-ci test

@swift-ci test


text:
SwiftSyntax update for "Shorten #file and add #filePath (behind an experimental flag)" (apple/swift#25656)

apple/swift#25656 adds new PoundFilePathKeyword and PoundFilePathExpr nodes to the syntax tree; this PR updates the gybbed files to add them.

apple/swift#25656
@swift-ci please smoke test

apple/swift#25656
@swift-ci please test

With apple/swift#25656
@swift-ci please test

repo: apple/swift-syntax


text:
Fix inconsiderate naming

Fixes inconsiderate naming in test

I really do not think Leader / Follower conveys the actual relationship as well as Master / Slave does. Master / Slave are two widely used words in the English language that, when used together in technology, are a well understood and widely-used metaphor. I think if you're offended by that naming in some codebase then you need to have a long hard look at yourself and how much time you have on your hands.

It is not even used as a metaphor. One definition of slave in my dictionary is:

a device, or part of one, directly controlled by another: [ as modifier ] : a slave cassette deck. Compare with master1.

So it is the proper use of the word.

get a grip people

Ignore the haters, I'm a fan of this change. Nice work @pcbro

Master / Slave are perfectly acceptable words in the English language and are very well understood and widely-used term in technology. Leader / Follower as a metaphor does not describe the relationship as well. This change is objectively pointless and introduces inconsistent terminology. If you are offended by this term in some codebase then you most likely have too much time on your hands. Perhaps we can ask them to also change the name of the repo? Apple offends me and is inconsiderate because I think of Adam & Eve and the devil...

Would replica/primary be a better solution for everyone?

I can only agree with @peterkellyonline and the comment provided by @Jaxan makes it clear that this usage is targeted at the technical application of the terms..

The guys name is 'pcbro' and obviously refers to South Park. Hard to tell if this is genuine or a troll.

He's just running stuff through (Alex)[https://github.com/wooorm/alex] I think.

If this nomenclature wasn't in Swift 2, would it be added to Swift 3?
I think it's worth considering. If leader/follower isn't the right metaphor, then find a new one.

Quite beside the point who originated this patch. I don't object at all to "leader" or "follower", and I doubt you'll find anyone who does.
If you're objecting to the motivation of this patch, that is also quite beside the point. The Swift open source community will entirely benefit from a slightly more inclusive change in name that has no impact on development, and more to the point, by accepting this patch (and the untold hundreds of "typo" patches that went through last night) it can be publicly demonstrated that all contributions are welcome and considered on their merits alone.

Merging into 'master'? Outrageous.

@cannyboy - are you proposing Linus should rename the default branch to leader in the next git release? (sorry.. couldn't help myself)

I object to Leader / Follower because it does not describe the concept as well as Master / Slave, which everyone is familiar with. And it is perfectly acceptable terminology used as it is in a technology domain. But more importantly, just because you are offended by something doesn't mean it has to change.

@shirk the default branch should of course be beautiful-melting-pot which we all merge into

master on its own is fine. master and slave used the way they are is not.

Yeah, removing Master/Slave terminology is certainly worthwhile. Appealing that something was ok in the  past generally isn't a good enough argument to keep it (after all, the whole reason people are starting to question this terminology is because of it's relation to something that was deemed "ok" in the past, but which we no longer view as acceptable).
That said, while Leader/Follower is an improvement I'm not entirely sure it's ideal. Maybe Primary/Replica would be better.

Manager/worker?

Even just master/worker would be fine?

:+1:

The English word "Master" is used in technology for a few different reasons.

It is the thing that all others are created from. Like master branch, master tape, golden master.

It is the thing that gets all requests/orders/dividends and then determines where something should go. This is similar to how Master works with IDE when two drives are on the same bus. See "Marshal".

Sometimes "host" is used instead of "master" (networks, USB, et cetera) as they are synonyms.
When an antonym to "master" was required to indicate a similar item that is not defined as "master", "slave" is generally chosen. Not necessarily because of the meaning of the word but because it is an antonym for most uses of the word "master".

Its used in a different context, but theres a lot of good discussion on this django PR https://github.com/django/django/pull/2692

Looks good, thanks!

authors: Jaxan Rosyna Shirk ashfurrow cannyboy clooth czechboy0 jckarter jordanekay neilkimmett pcbro peterkellyonline pilky s3itz swizzlr tangentfairy

repo: apple/swift


text:
Make c++ defer looks like a swift one

This code uses some c++ trickery to make defer macro looks almost like defer keyword in swift.
Instad of:
defer([&]() {
  /* cleanup code */
});

coders can now drop some boilerplate and do this:
defer {
  /* cleanup code */
};

But this changes capture list to all values by reference

@przybylski , please find the author of this code (using git blame) and invite them to review this code (by using their github handle name)

@lattner could you have a look on this PR?

I prefer the function to macro trickery, honestly. Neat trick though.

Simultaneously cute and horrible :-) - looks great, thanks!

authors: jckarter lattner nadavrot przybylski


text:
[4.2] Sema: Make implicit elementwise struct init insensitive to lazy validation order.

With batch mode, other files may have forced lazy properties to get finalized before the implicit constructor is formed. Avoid the order dependency by making the behavior stable regardless of the type-checking phase of lazy declarations. Fixes rdar://problem/40903186.

@swift-ci Please test


text:
[docs] Add a link in DebuggingTheCompiler to the manual symbolication…

… lldb guide on llvm.org

@swift-ci smoke test and merge


text:
WIP: Don’t demangle an error type.

When there are errors, indexing can try to demangle an error type, which can cause an abort.
Don't do this.

@swift-ci please smoke test


text:
[RFC] Use uninitialized dealloc in swift_deallocError

Current of implementation swift_deallocError produce assertion in code like this
import Foundation

func empty(_ error: Error?) {
}

func crash(_ error: NSError?) {
  empty(error)
}

crash(nil)

Assertion is here https://github.com/apple/swift/blob/master/stdlib/public/runtime/HeapObject.cpp#L678
assert(object->refCounts.isDeiniting());

When swift_deallocError called box have unowned count = 1, strong count = 0 and deiniting = false.
I am not sure is it correct way to avoid assertion, and would it work properlly in all cases. So would be cool if somebody looks into this.

I don't think this is the correct fix, since the error is initialized. @mikeash, have we seen anything like this?

I wasn't aware of any problems with this, but this does look like the correct fix. The SWIFT_OBJC_INTEROP version of swift_deallocError is:
/// destroyed.
void
swift::swift_deallocError(SwiftError *error, const Metadata *type) {
  object_dispose((id)error);
}

This fix adjusts the non-interop version to match. Assuming the ObjC version is correct (I imagine someone would have noticed by now if it weren't) this should be good.

My mistake! Can you add a test for this, then, Anton? test/stdlib/ErrorBridged.swift seems to be a good place.

Whoops, my poor Markdown skills resulted in most of the comment being hidden. Since it describes that the function is intended to deallocate an error object which has already been destroyed, that's kind of important!

@jrose-apple As I see test/stdlib/ErrorBridged.swift REQUIRES: objc_interop but this code instead executes only if interop disabled. Do you know some another good place for test? Or just create new test?

Ah, right. Well, we can't test NSError specifically in the Swift repo because swift-corelibs-foundation isn't available in the Swift tests, but this seems like a problem that would occur with any Error, or maybe any class that conforms to Error (as opposed to the usual struct or enum). If that's the case, then adding it to test/stdlib/Error.swift is probably good.

problem that would occur with any Error
With any error marked as @objc. But @objc also require to import Foundation

I was wrong simple enum errors also produce assertions. But I am still not clear how to test it.
Just add code which leads to assertion to test/stdlib/Error.swift and if assert occurs test fail?

The test should automatically fail on crash by default, so you should be able to make a simple test case that just triggers the failure case and returns. You can try running it with and without your fix to make sure it fails when it's supposed to.

You can have perhaps a separate PR against swift-corelibs-Foundation to add a test there, which is where we plan to have bridging tests for non-ObjC bridging.

Looks like original issue already fixed in master by https://github.com/apple/swift/pull/18937
Compiler does not emit deallocError at all in this case.
Maybe still actual in some other cases but I don't them.

cc @jckarter.
@mikeash, maybe we should just test this manually, by calling swift_deallocError directly? Or should it be an error to call it on an uninitialized buffer?

It can't be called on a completely uninitialized buffer. It calls through to either object_destroy (when ObjC interop is enabled) or swift_deallocObject which requires that they be deinitialized/uninitialized but otherwise valid objects.

@mikeash Can you look into this?
Original code which leads to issue:
import Foundation

func empty(_ error: Error?) { }
func crash(_ error: NSError?) { empty(error) }

SIL generated by swift-DEVELOPMENT-SNAPSHOT-2018-08-26-a-ubuntu16.04:
sil hidden @$S4test5crashyy10Foundation7NSErrorCSgF : $@convention(thin) (@guaranteed Optional<NSError>) -> () {
// %0                                             // users: %5, %4, %1
bb0(%0 : $Optional<NSError>):
  debug_value %0 : $Optional<NSError>, let, name "error", argno 1 // id: %1
  %2 = alloc_existential_box $Error, $NSError     // users: %10, %6, %3
  %3 = project_existential_box $NSError in %2 : $Error // user: %9
  retain_value %0 : $Optional<NSError>            // id: %4
  switch_enum %0 : $Optional<NSError>, case #Optional.some!enumelt.1: bb2, case #Optional.none!enumelt: bb1 // id: %5

bb1:                                              // Preds: bb0
  dealloc_existential_box %2 : $Error, $NSError   // id: %6
  br bb4                                          // id: %7

// %8                                             // user: %9
bb2(%8 : $NSError):                               // Preds: bb0
  store %8 to %3 : $*NSError                      // id: %9
  %10 = enum $Optional<Error>, #Optional.some!enumelt.1, %2 : $Error // user: %11
  br bb3(%10 : $Optional<Error>)                  // id: %11

// %12                                            // users: %15, %14
bb3(%12 : $Optional<Error>):                      // Preds: bb4 bb2
  // function_ref empty(_:)
  %13 = function_ref @$S4test5emptyyys5Error_pSgF : $@convention(thin) (@guaranteed Optional<Error>) -> () // user: %14
  %14 = apply %13(%12) : $@convention(thin) (@guaranteed Optional<Error>) -> ()
  release_value %12 : $Optional<Error>            // id: %15
  %16 = tuple ()                                  // user: %17
  return %16 : $()                                // id: %17

bb4:                                              // Preds: bb1
  %18 = enum $Optional<Error>, #Optional.none!enumelt // user: %19
  br bb3(%18 : $Optional<Error>)                  // id: %19
} // end sil function '$S4test5crashyy10Foundation7NSErrorCSgF'

SIL generated by swift-DEVELOPMENT-SNAPSHOT-2018-09-04-a-ubuntu16.04:
// crash(_:)
sil hidden @$S4test5crashyy10Foundation7NSErrorCSgF : $@convention(thin) (@guaranteed Optional<NSError>) -> () {
// %0                                             // users: %3, %2, %1
bb0(%0 : $Optional<NSError>):
  debug_value %0 : $Optional<NSError>, let, name "error", argno 1 // id: %1
  retain_value %0 : $Optional<NSError>            // id: %2
  switch_enum %0 : $Optional<NSError>, case #Optional.some!enumelt.1: bb2, case #Optional.none!enumelt: bb1 // id: %3

bb1:                                              // Preds: bb0
  br bb4                                          // id: %4

// %5                                             // user: %8
bb2(%5 : $NSError):                               // Preds: bb0
  %6 = alloc_existential_box $Error, $NSError     // users: %9, %7
  %7 = project_existential_box $NSError in %6 : $Error // user: %8
  store %5 to %7 : $*NSError                      // id: %8
  %9 = enum $Optional<Error>, #Optional.some!enumelt.1, %6 : $Error // user: %10
  br bb3(%9 : $Optional<Error>)                   // id: %10

// %11                                            // users: %14, %13
bb3(%11 : $Optional<Error>):                      // Preds: bb4 bb2
  // function_ref empty(_:)
  %12 = function_ref @$S4test5emptyyys5Error_pSgF : $@convention(thin) (@guaranteed Optional<Error>) -> () // user: %13
  %13 = apply %12(%11) : $@convention(thin) (@guaranteed Optional<Error>) -> ()
  release_value %11 : $Optional<Error>            // id: %14
  %15 = tuple ()                                  // user: %16
  return %15 : $()                                // id: %16

bb4:                                              // Preds: bb1
  %17 = enum $Optional<Error>, #Optional.none!enumelt // user: %18
  br bb3(%17 : $Optional<Error>)                  // id: %18
} // end sil function '$S4test5crashyy10Foundation7NSErrorCSgF'

As you can see alloc_existential_box moved into .some branch and dealloc_existential_box is eliminated. So no more issue in this case.
But I dont know is any other code can produce dealloc_existential_box for empty box

@jckarter thanks for example

Test added. Can anyone trigger ci?

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - c59d755b004564e406551be9aa6d30625e837b9e

Build failed
Swift Test Linux Platform
Git Sha - c59d755b004564e406551be9aa6d30625e837b9e

All right, merging. Thanks, Anton!

authors: jrose-apple mikeash millenomi swift-ci zayass