Improve instructions for creating tickets in Trac, including who to contact for an account

see ticket:114 for an example of the difficulties encountered.
Both the wiki and the Sphinx docs should be improved.
Should also consider moving issue tracking to BitBucket.
Imported from Bitbucket issue 118,  created by apdavison on 12-10-2012 at 13:14, last modified: 06-01-2013 at 12:40

The main problem seemed to be with attaching a patch to a ticket.  I've now enabled TICKET_APPEND for anonymous, so this problem should no longer arise.
Improved documentation is now needed for how to obtain a Trac account.
Issue tracking will be moved to Bitbucket after the 0.6 release.
Trac comment by apdavison on 05-15-2013 at 10:07

Since we will be moving to Bitbucket issue tracking soon (see ticket:177), it doesn't seem worth taking the time to improve the documentation for Trac.
Trac comment by apdavison on 06-01-2013 at 12:40


Refactor financial_transaction_spec

There is some verbose code in the financial_transaction_spec, that could use a touch up.
Examples: valid_rental = create :rental, item_type: @item_type While correct, we have an association setup to create an item_type, along with a rental. Ends up being a bit WET.
Further, some lines are a bit long and line breaks would add a lot of readability.

Commit added to address this in #115


Add config block tree

This add config_block_tree that defines a config block including all its children. It can be used to import full config trees.
NOTE: it depends on the array support changed made by @thomasfinstad at https://github.com/thomasfinstad/vyos-client-go I could make it work without them but ideally we would merge his changes first.

Examples from my homelab:
resource "vyos_config_block_tree" "dhcp_server" {
  path = "service dhcp-server shared-network-name LAN subnet <IP_ADDRESS>/24"

  configs = {
    "default-router"= "<IP_ADDRESS>",
    "domain-name"= "vyos.net",
    "lease"= "86400",
    "name-server"= "<IP_ADDRESS>",
    "range foo start" = "<IP_ADDRESS>",
    "range foo stop"= "<IP_ADDRESS>"
  }
}

resource "vyos_config_block_tree" "interfaces" {
  path = "interfaces"
  configs = {
    "ethernet eth0 address"           = "dhcp"
    "ethernet eth0 description"       = "OUTSIDE"
    "ethernet eth0 vif 2 address"     = "dhcp"
    "ethernet eth0 vif 2 description" = "lte"
    "ethernet eth1 address"           = "<IP_ADDRESS>/24"
    "ethernet eth1 description"       = "INSIDE"
  }
}

This add config_block_tree that defines a config block including all its children. It can be used to import full config trees.
NOTE: it depends on the array support changed made by @thomasfinstad at https://github.com/thomasfinstad/vyos-client-go I could make it work without them but ideally we would merge his changes first.

I have not done any real testing of my code there, and might try to merge the map and array functions together at some point, but if @Foltik wish to pull it in that is fine with me.

Looks good to me, thanks for the contribution! Going to test this on my end and merge shortly.

Great @Foltik - please notice that I made a change to support empty values -> https://github.com/thomasfinstad/vyos-client-go/pull/1


connect wallet sections

Is your feature request related to a problem? Please describe.
In connect wallet section cards can be improved.
Describe the solution you'd like
In connect wallet section cards can be improved means. it can be improved on hovering.
pls, assign me this issue under gssoc'23.
Describe alternatives you've considered
No response
Additional context
No response

Hey @NexusNeeraj  Can you share any screenshots of how you want the hover effect to look?

on clicking these icons
[image: Screenshot 2023-05-29 182553.png]
On Mon, May 29, 2023 at 1:23 AM Joy Almeida @.***>
wrote:

Hey @NexusNeeraj https://github.com/NexusNeeraj Can you share any
screenshots of how you want the hover effect to look?
—
Reply to this email directly, view it on GitHub
https://github.com/J0SAL/Decentralized-Expense-Tracker/issues/59#issuecomment-1566244325,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZ7JCZKAWBR544QH7B7EZZ3XIOULJANCNFSM6AAAAAAYP7OIIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

https://www.oscode.co.in/
visit this site and check numbers say it all cards section and hover u
will see what happening.
On Tue, May 30, 2023 at 10:00 PM Joy Almeida @.***>
wrote:

Hey @NexusNeeraj https://github.com/NexusNeeraj, The image is not
viewable
—
Reply to this email directly, view it on GitHub
https://github.com/J0SAL/Decentralized-Expense-Tracker/issues/59#issuecomment-1568734845,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZ7JCZNI7QAJ7NADTOCKL33XIYOBTANCNFSM6AAAAAAYP7OIIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Cut 4.0 release

Depends on #93, at least. This is just a reminder for now.

@tsloughter, this is now around 4 years old 😄 I love my Elli and would like to see a 4.0 too. Anything I can do to help move it forward? Triage some more issues, fix some more stuff, close some more issues (?)

Do you know what the breaking changes are that make this 4.0?

I can look at the commits since the last release.

This is what I found:

record req now has field original_headers (was parsed_headers during dev.)

this is mentioned in the CHANGELOG

header names are downcased (though this is most likely not breaking)
the min. supported OTP bumped to 24+

This draft also seems to mention some stuff that could be included in the next major, but that shouldn't prevent 4.x from being released.

I'm pretty busy for the next two months, but usually try to do fun stuff like this during December. No need to wait for me, but I'm saying I could commit to helping out then. In the meantime I'm happy to review PRs or just be a cheerleader.

@yurrriq, given your comment, I think the following could benefit from a review and/or follow-up:

https://github.com/elli-lib/elli/pull/66

seems to not have gotten any review
probably too old, maybe close (?)

https://github.com/elli-lib/elli/pull/110

not very recent
didn't get merged at that time, even if approved
has merge conflicts

https://github.com/elli-lib/elli/pull/106

seems to have been abandoned halfway through
probably too old (?)

https://github.com/elli-lib/elli/pull/112

recent
approved
not merged

https://github.com/elli-lib/elli/pull/123

recent
not reviewed


Login doesn't work

Currently, i am getting below error in Google login,

Fatal error: Uncaught Exception: Could not log in to Google Voice with username<EMAIL_ADDRESS>Look at error log for detailed input information. in /Applications/MAMP/htdocs/Google-Voice-PHP-API-master/GoogleVoice.php:75 Stack trace: #0 /Applications/MAMP/htdocs/Google-Voice-PHP-API-master/GoogleVoice.php(160): GoogleVoice->_logIn() #1 /Applications/MAMP/htdocs/Google-Voice-PHP-API-master/example.php(17): GoogleVoice->sendSMS('+XXX XXX XXXX', 'Sending a messa...') #2 {main} thrown in /Applications/MAMP/htdocs/Google-Voice-PHP-API-master/GoogleVoice.php on line 75

I tried to debug the lib and print cURL request and found "Javascript doesn't support error"

however javascript is enabled in Browser. Also, two factor authentication is disabled.
Please help me to debug the issue.

Hi. Were you ever able to find a solution to this? I'm guessing google stores whether or not js is enabled in a cookie BEFORE the actual login submission takes place. How exactly to simulate that, I'm not sure.


Map screenshot

There is a way to create a map screenshot to stream?

for now we don't have this api but i will add it


Severe logs should be included as breadcrumbs for other events

Problem Statement
I have multiple errors happening in the app as a result of a bug. These are triggering multiple severe logs and uncaught exceptions. When looking at the events through Sentry, the severe logs are not present in the breadcrumbs for the event related to the uncaught exception.
The code looks something like this:
try {
   resource = createResource();
} except (e) {
  log.severe('bug');
  resource.cleanup();
 rethrow;
}

The rethrow is never caught, and the event for the uncaught exception does not include the bug log as a breadcrumb. This made me assume that this is not the branch that failed. I only realised what's going on after adding random throws around the code and comparing the Sentry logs between the original event and my modified version.
Solution Brainstorm
When sentry submits an event, previous events from the same sessions should be included as breadcrumbs.
Are you willing to submit a PR?
Yes

Hi,
thank you for the message, this looks like a bug.
The logger.sever creates a breadcrumb and event, the breadcrumb should be included in the event created from the rethrown exceptions. We will investigate it.

Hi, thank you for the message, this looks like a bug.
The logger.sever creates a breadcrumb and event, the breadcrumb should be included in the event created from the rethrown exceptions. At the moment I don't see why it's not included. We will investigate it.

I have hunch, that the different ways of serialization for whole events vs serialization for the native sync is the issue.
When doing serialization for whole events, it's done via https://github.com/getsentry/sentry-dart/blob/d78342459141e1798a213da74ad13e89235cbe31/dart/lib/src/utils.dart#L31
but for the native sync there's nothing like that
https://github.com/getsentry/sentry-dart/blob/d78342459141e1798a213da74ad13e89235cbe31/flutter/lib/src/sentry_native_channel.dart#L59
thus when non-serializable objects are added to a breadcrumb it just fails.

@maBarabas can you share your SDK init code snippet?
Also, a minimal reproducible example would help unless you are swallowing your exceptions, every unhandled exception should be captured automatically, and the previous errors should be part of breadcrumbs, as long as they were within the same session.
Last question, which library/package are you using for log.severe('bug');?

@marandaneto I was able to reproduce the issue with this code, adjusted the tryCatch function from our example app.
Future<void> tryCatch() async {
  try {
    throw StateError('try catch');
  } catch (error, stackTrace) {
    Logger("test").severe('bug');
    // await Sentry.captureException(error, stackTrace: stackTrace);
    rethrow;
  }
}

@marandaneto, here is my init:
Future<void> main() async {
  // Work around sentry not printing these errors for now. I've created a PR
  // that adds logging support. We can delete this after that's merged.
  // https://github.com/getsentry/sentry-dart/pull/1257
  PlatformDispatcher.instance.onError = (e, s) {
    return false;
  };

  // Make sure that severe and above logs have a stack trace for good grouping
  // in sentry. If there is no stack, then all the different log lines are
  // grouped together by default. We have worked around that by setting up a
  // grouping rule to split those groups by the messages.
  recordStackTraceAtLevel = Level.SEVERE;
  await SentryFlutter.init(
    (options) {
      options
        ..dsn = sentryDsn
        // enable debug logging for local development use cases, disable for
        // production
        ..debug = kDebugMode || kProfileMode
        ..diagnosticLevel = SentryLevel.info
        ..addIntegration(LoggingIntegration())
        // The app does all of its logging trough the logging package. We also
        // log to the console for debugging. Disable breadcrumbs for the console,
        // so that we don't see duplicate breadcrumbs in Sentry.
        //
        // Temporary fix: https://monitoraudio.atlassian.net/browse/MUF-264
        //
        // Sentry is missing error level logs in breadcrumbs for other related
        // events: https://github.com/getsentry/sentry-dart/issues/1583
        //
        // Every log is printed to the console, so this works around the issue.
        ..enablePrintBreadcrumbs = true
        // Set tracesSampleRate to 1.0 to capture 100% of transactions for performance monitoring.
        // We recommend adjusting this value in production.
        ..tracesSampleRate = 1.0
        ..attachScreenshot = true;
    },
    appRunner: appMain,
  );
}

Logging is done with package:logging so that I can make use of the LoggingIntegration.
The default log level is set to INFO.
I also use SentryUserInteractionWidget and SentryScreenshotWidget at the root of the app's widget tree.
I think the setup proposed by Kryštof should be representative.

Ok, I see, the problem is that Logger.root.onRecord.listen takes a void onData(T event)? function but it does not await the function call, so its added to the event loop since Sentry's callback is a Future.
The Logger("test").severe('bug'); call captures a new event and breadcrumb, but due to the event loop, the crumb is added a bit after the rethrow event is also captured.
In both cases, I see both events captured in the sentry.io dashboard though.

The StateError error does not contain the bug breadcrumb, but it should.
Since we don't have control over the logging API, we cannot change this behavior but rather make it as best effort, this only happens when creating the crumb and an error happens very next to each other, right?

Similar issue https://stackoverflow.com/questions/75752421/flutter-run-async-function-on-stream-listen
onRecord is a get so I cannot overwrite and combine with asyncMap or something else.
@maBarabas or @ueman do you have any ideas on how to fix this?

As we don't have control over the Logger implementation the workaround is to create a custom breadcrumb that will be awaited and therefore created before the rethrow.
Future<void> tryCatch() async {
  try {
    throw StateError('try catch');
  } catch (error, stackTrace) {
    Logger("test").severe('bug');
    await Sentry.addBreadcrumb(
      Breadcrumb(
        message: 'bug',
      ),
    );
    rethrow;
  }
}


Improve notice name consistency

Revisit notices class names for consistency.
[...] I'd suggest we put the entity name first when it makes sense for consistency, and because if we list the rules in the table alphabetically then, for example, most of the Route rules should be grouped together. So, for example, this class and code could be renamed to RouteSameNameAndDescriptionNotice and route_same_name_and_description. Then it would appear right after RouteBothShortAndLongNameMissingNotice.
Originally posted by @barbeau in https://github.com/MobilityData/gtfs-validator/pull/781#discussion_r585866237

Closing as duplicate of https://github.com/MobilityData/gtfs-validator/issues/826


Update bluestacks: url

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

@emay3700 Please STOP approving PRs! It is pointless and spammy!


integrate releases with zenodo

Whenever we release protocols, trigger zenodo to archive the repository.

[X] setup webhook for Zenodo Sandbox on repo protocolsource
[x] successfully test webhook on repo protocolsource
[x] add .zenodo.json file on repo protocolsource
[x] re-test webhook with .zenodo.json on repo protocolsource
[ ] repeat Sandbox & .zenodo.json setup at protocols repo
[x] once protocolsource repo is ready to be set for Zenodo releases, replace sandbox webhook by Zenodo webhook
[x] discard test releases for Zenodo Sandbox from protocolsource repo
[x] once protocols repo is ready to be set for Zenodo releases, replace sandbox webhook by Zenodo webhook
[x] discard test releases for Zenodo Sandbox from protocols repo

EDIT: replaced protocols-website with protocols and protocols with protocolsource. The rendered version will be in protocols repo, the source code in protocolsource repo

@hansvancalster in which stage would you like to start this behaviour? Right away, or would you still like a 'maturation' period to experiment with releases on GitHub before connecting with Zenodo? Releases that appear on Zenodo cannot be removed (unless you contact the Zenodo admins), while they can still be deleted on GitHub. On the other hand, releases that appear on GitHub before connecting Zenodo, should be re-released on GitHub if you still want them transmitted, or must be manually uploaded on Zenodo.
Another approach is to use https://sandbox.zenodo.org if you want experimentation with Zenodo (from time to (long) time, those records are deleted again). Of course the previous notes for https://zenodo.org will remain valid.

@florisvdh definitely need a maturation period first. Consider this issue just to be a reminder for the time being.

Regarding https://github.com/inbo/protocols/issues/3#issuecomment-627316739 it seems useful to set up the trigger for Zenodo-releases as well Shall I do that? I think it will be best to first have a test period with the Zenodo sandbox. We could make dummy releases to check if everything works OK (incl website), these releases are to be discarded afterwards (i.e. by deleting the tags or even rewriting some repo history).
Once releases are transmitted to 'actual' Zenodo, they will be made definitive and given a DOI (the only solution in case of mistakes is to contact Zenodo). We don't want rubbish to appear there, and on the other hand we want it to be as complete as possible.
The trigger will be needed for this repo as well as for the protocols-website repository. I can start with this one, and do the same (Zenodo Sandbox) for the other repo once it is in place and when it's clear which event must happen there to trigger Zenodo.

Yes, that would be great! Good idea to use Zenodo sandbox environment for testing. I am not familiar with triggers, is the trigger for Zenodo completely separate from the trigger for Travis CI/Github runner to the website repo? Or is some coordination necessary?
I'm not sure if we should also archive the contents of the protocols-website repo to zenodo (the source files seem more important to me)? Maybe this can be done infrequently - say once a year or  so.

They will be separate. Of course both will happen simultaneously when they occur for the same events in a repo. Actually it is called 'webhook':

Webhooks allow external services to be notified when certain events happen. When the specified events happen, we’ll send a POST request to each of the URLs you provide. Learn more in our Webhooks Guide.

I'm not sure if we should also archive the contents of the protocols-website repo to zenodo

It was my interpretation of the branching model :wink: Anyway, it is very easy to set it up, and it is easier to do it for all releases than to manually switch off and on the webhook to prevent some releases to be transmitted.
Each new release will be a version within the same Zenodo record, which itself stands for one Github repo (one record for protocols repo, and another for protocols-website if you like). So the administrative burden in GitHub and Zenodo would be minimal.
On the other hand, I now realize that it would be incremental versions for protocols-website, as all older protocols are still in it.

Another approach would be to have the latest compiled protocols in a separate repo - i.e. no older protocols, no website. I think we touched that idea as well while discussing the branching model. Perhaps that would be more logical to release in Zenodo?

I think we decided that the website should have all versions of protocols, because field-workers may need to have access to specific versions in some monitoring projects. So I would stick to the current implementation idea and indeed have webhooks that trigger Zenodo for both the protocols and protocols-website repo.

[X] setup webhook for Zenodo Sandbox
[ ] successfully test webhook
[ ] add .zenodo.json file
[ ] re-test webhook with .zenodo.json
[ ] repeat Sandbox & .zenodo.json setup at protocols-website repo
[ ] once protocols repo is ready to be set for Zenodo releases, replace webhook by Zenodo webhook
[ ] once protocols-website repo is ready to be set for Zenodo releases, replace webhook by Zenodo webhook

@hansvancalster moved my to-do list inside your first comment, so that a progress bar appears in the list of issues

@hansvancalster I suggest to also insert a version-independent Zenodo badge at the front of the Readme.


Add migration info for testnets

The migration workflow would be improved if truffle.js was set up to be able to deploy to the testnets (e.g. using Infura).

Closed by https://github.com/nventuro/crafty/commit/cd544f296e2edc39ca4bd81dd07e2ce6cb12ec1a


Add support for UUID

// Change
$table->morphs('authenticatable');

// to
$table->uuidMorphs('authenticatable');

and add in config file 'id_type' => 'uuid'
For example
if (config('auth_tracker.id_type') === 'uuid')
    $table->uuidMorphs('authenticatable');
else
    $table->morphs('authenticatable');

This package is now discontinued and replaced by a new one that supports Laravel 10 and 11: Laravel Logins


Added css.gg icons

Added css.gg icons to the icons section.
See icons at:
https://css.gg/
https://github.com/astrit/css.gg

I just merged the new version at this time to avoid conflict and corrected an typo from the line above my adding.


OIDC with Keycloak which is also in the cluster?

Hello!
Discussions were disabled, so apologies for posting this as an issue. :)
Most of my company collegues aren't as terminal-savy as me and a former worker had demployed a k3s cluster here. Now I added Headlamp as a nice Web UI to give my collegue an entrypoint into the cluster so they can see what it is doing and the likes.
However, I had wanted to use our existing Keycloak OIDC structure, bound to our AD, to enable seamless SSO. And I can, in fact, click the login button and it "logs me in" - but the browser console tells me that I am unauthenticated.
Granted, I know that it is attempting to authenticate me directly with the API server through OIDC.
Question is, how can I realize that, without having to share a singular service account token around? I shared it with another collegue for now so they can try Headlamp out besides myself, but I would like to integrate it into our existing infrastructure.
Since the container has the service account loaded and a ClusterRoleBinding is established, Headlamp can authenticate with this just fine, in theory.
Is there anything I missed or that I have to do to make it work?
Here is the current deployment, in full:

Full deployment YAML
## Copied and modified from source
## ref https://github.com/headlamp-k8s/headlamp/blob/main/kubernetes-headlamp.yaml
apiVersion: v1
kind: Namespace
metadata:
  name: headlamp
---
kind: Deployment
apiVersion: apps/v1
metadata:
  name: headlamp
  namespace: headlamp
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: headlamp
  template:
    metadata:
      labels:
        k8s-app: headlamp
    spec:
      serviceAccountName: headlamp-sva
      containers:
      - name: headlamp
        image: ghcr.io/headlamp-k8s/headlamp:latest
        args:
          - "-in-cluster"
          - "-plugins-dir=/headlamp/plugins"
        ports:
        - name: http
          containerPort: 4466
          protocol: TCP
        env:
          - name: HEADLAMP_CONFIG_OIDC_CLIENT_ID
            value: "headlamp"
          - name: HEADLAMP_CONFIG_OIDC_CLIENT_SECRET
            value: "..."
          - name: HEADLAMP_CONFIG_OIDC_IDP_ISSUER_URL
            value: "https://keycloak.our.domain/realms/master"
        livenessProbe:
          httpGet:
            scheme: HTTP
            path: /
            port: 4466
          initialDelaySeconds: 30
          timeoutSeconds: 30
      nodeSelector:
        'kubernetes.io/os': linux
---
kind: Secret
apiVersion: v1
metadata:
  name: headlamp-admin
  namespace: headlamp
  annotations:
    kubernetes.io/service-account.name: "headlamp-sva"
type: kubernetes.io/service-account-token
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: headlamp-sva
  namespace: headlamp
  labels:
    k8s-app: headlamp
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: headlamp-admin
  namespace: headlamp
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: headlamp-sva
  namespace: headlamp
---
kind: Service
apiVersion: v1
metadata:
  name: headlamp
  namespace: headlamp
spec:
  type: ClusterIP
  ports:
    - port: 80
      targetPort: 4466
  selector:
    k8s-app: headlamp
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: headlamp
  namespace: headlamp
spec:
  entryPoints:
    - websecure
  routes:
    - kind: Rule
      match: Host(`headlamp.senpro.it`)
      services:
        - name: headlamp
          port: 80

Thanks and kind regards!

@senpro-ingwersenk Did you follow this docs to setup headlamp with keycloak OIDC? Can you share redact sensitive information and share a screenshot/logs of the error that you see in browser console?

@senpro-ingwersenk Hi! Thanks for your efforts to run it. I really wonder why it is important to distinguish between keycloak outside the cluster and inside - I think in both cases you should publish Keycloak outside with Ingress (i.e. Traefik in your case?) and use domain name pointing to ingress. Also please check that the services published with the ingress are accessible from the cluster itself - it could be an issue, particularly when running in clouds like DO.


[Bug]: jest.fn cannot be overloaded with one generic

Version
29..3.1
Steps to reproduce
const mockAdd = jest.fn<typeof add>();

Expected behavior
You should be able to overload jest.fn with one generic as argument.
Actual behavior
This Typescript error is thrown:
No overload expects 1 type arguments, but overloads do exist that expect either 0 or 2 type arguments.

You can only overload jest.fn with two arguments, e.g.:
const mockAdd = jest.fn<ReturnType<typeof add>, Parameters<typeof add>>();

Additional context
According to the documentation, overloading jest.fn with one generic should be possible:
https://jestjs.io/docs/mock-function-api#jestfnimplementation
This looks to have been implemented in https://github.com/facebook/jest/pull/12489 but reverted at some point.
Environment
System:
  OS: Linux 6.0 Arch Linux
  CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
Binaries:
  Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
  Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.1/bin/yarn
  npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm

Do you use typings from @types/jest or `import {jest} from '@jest/globals'?

Ou, missed that comment! Would probably be good to add it directly under the Typscript Usage header.
I can re-test it tomorrow but I'm quite certain I tested with both typings and the problem was present in both.

I found the problem. I never had declared @jest/globals in my package.json so I was unintentionally using an old version. The old version came from react-scripts, not 100 % why it "won" my dependency chain in package.json.
Maybe defining  @jest/globals in package.json could be added to the Typescript installation instructions? I know pnpm would have warned me about not having a referenced dependency defined in my package.json, but I was using classic Yarn due to a legacy project.

Thanks for feedback. I just opened #13601 with improvements. Please take a look (;


International Price Response Functions

We need to calibrate the responsiveness of world interest rates to changes in the US net supply/demand of savings for each period in the model.  This is potentially time-varying since foreign supplydemand are likely to grow faster than US net supply/demand.
We also need calibrations of the responsiveness of world prices to changes in the US net supply/demand for tradable goods.
How do we handle consumption goods imports/exports vs production goods imports/exports?
Do we want to deal with labor migration?

The citation for the Devereaux and De Mooij paper is "Ruud Mooij & Michael Devereux, 2011. "An applied analysis of ACE and CBIT reforms in the EU," International Tax and Public Finance, Springer, vol. 18(1), pages 93-120, February."


[DRAFT] Bandersnatch VRF

PR currently open to get feedback from backend author

Open discussions:
Main points requiring a feedback and/or clarification:
~1. We need a way to sign a raw array of arbitrary bytes (similar to what has been done with sr25519). I went with this not so complicated approach here~

Pure VRF signature is wrapped here
I have the suspect that here we require to instance a ThinVrfSignature<1> instead of ThinVrfSignature<0> in order to embed the PreOut in the structure.

In sr25519 this is the code used to wrap the backend make_bytes call. I.e. the code to generate bytes from the VRF configuration (PreOut).  What is the equivalent way to do this using bandersnatch-vrfs backend?

Key derivation.

sr25519 supports both hard and soft secret key derivation (see here). While ecdsa and ed25519 support only hard secret key derivation (e.g. see here). What about bandersnatch?
Also what about soft public key derivation (currently only supported by sr25519)?

Naming... Is just bandersnatch-vrf name appropriate for the primitive we are including? To be fair this is  an ed-on-bls12-381-bandersnatch with vrf capabilities etc etc. What is an appropriate (please not verbose) name synthesizing this primitive capabilities  and that fits well with the rest of the primitives?   (e.g. "schnorr using ristretto -> sr25519)?

When a first version bandersnatch-vrfs crate on crates.io?

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate-macos
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2714614

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2714601

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2714603

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2714602

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate-macos
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2716422

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2716420

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2716409

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2716411

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate-macos
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2730084

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2730082

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2730072

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2730083

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2730078

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2730068

requires https://github.com/paritytech/substrate/pull/14036

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate-macos
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2783327

2. To be fair this is  an ed-on-bls12-381-bandersnatch with vrf capabilities etc etc. What is an appropriate (please not verbose) name synthesizing this primitive capabilities  and that fits well with the rest of the primitives?   (e.g. "schnorr using ristretto -> sr25519)?

 Fits a similar pattern as sr25519. (:

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2821255

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2821254

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2872146

Because this key type will be used by a consensus protocol, is required to implement all the traits required by session pallet. One of these is RuntimeAppPublic which in turn required RuntimePublic.
This trait offers some methods requiring access to the keystore: sign and generate_pair
Was my intention to keep the required host functions to the minimum.

generate_pair should be implemented. Apparently there is nothing we can do. As it is invoked at startup by the session pallet and also from the rpc interface to generate new keys on demand. I've added an host function for this...

sign: this may be useful if we want to sign something from an offchain worker. Currently we don't. Maybe I can just return None here?

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2873609

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate-macos
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2873610

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2873593


🐛 Bug Report: Code not copied

👟 Reproduction steps
On the Home page of the build section, there were two code blocks with the copy button but the copy button doesn't work for some reason.
👍 Expected behavior
Copy code when we click on the copy button.

👎 Actual Behavior
The code doesn't copy when we click on the copy button.

🎲 Appwrite version
Version 1.2.x
💻 Operating system
Windows
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

I can fix this issue, can someone please assign me to work on this issue?

Hi @ashrafchowdury , thank you for sharing. Please go ahead and make a PR for the same.

Closing, as this has been solved.


http2: handle client stream send error

When a client stream receiver dropped, http2 client panics with an error message SendError("...").
This PR removes the dropped stream and close the corresponding remote.

Could you please explain, how to reproduce an error? I need to write a test case before applying the patch.

I think I fixed the issue in 172915640d6a1080dff4a261e324fcd9b12d36ef.
However, in my patch, died client does not cancel the call, I've created a separate issue for that: #2.

Well done! Sorry for the super later reply, I have been busy with my graduation project lately.


error reply message

this is my code:
@app.on_updateNewMessage()
async def reply_message(c: Client, message: Update):
    print(await message.reply_text('test', quote=True, parse_mode='html'))

get this error
{
    "@type": "error",
    "code": 400,
    "message": "Failed to parse JSON object as TDLib request: Unknown class \"messageReplyToMessage\""
}

version 0.8.6

Hey, could you try to install GitHub version:
pip install git+https://github.com/pytdbot/client.git

it should be fixed and later i will release it publicly.

solved thanks

Thank you, this was fixed in Pytdbot v0.8.7 !


Zoneout

Hi, great repo and many thanks for putting your work up here for everyone.
One thing I just wanted to mention - I had a quick look at your code and it doesn't look like there is zoneout regularisation on the lstm decoders. Do you plan on adding it or indeed perhaps I missed it when I read the code?

Thank you for your kind words. Yes, this repo does not have Zoneout and we would possibly add it if there's an pull request adding this feature.


Separate Authorization and Signature headers

These two headers have different meanings and intentions, and it may not be safe to simply issue both for all requests.
PR #36 implements separate sign and authorize methods to generate these headers individually.

I'm consulting on an implementation now where the Authorization header uses a (bearer) token retrieved from an OAuth2 service, and Signature header from this protocol. Using this library as-is (generating both) would either overwrite the Authorization header (losing the token) or add a second Authorization header, which most implementations would probably not understand or some may outright reject if they're not expecting it.
This is a required change IMHO, though I realise the potential for BC impact.

Closing issue due to inactivity.


Slow wpf listview

Because i'm using several hacks, and unstable code for wpf listview, issued bad performance for wpf listview.
need to improve listview performance

I think wpf listview not bad performance in now(https://github.com/leekcake/TweetTail/commit/924a35915cb4fb330aaad3332f97559d42774747)


feat(designer_v2): Study Preview

Adds a study preview function to the Test screen.
Depends on https://github.com/hpi-studyu/studyu/pull/122

Closed in favor of: https://github.com/hpi-studyu/studyu/pull/143


Crashes in browser on process in packages/js/src/httpClient.ts if not setting url

Trying to use Axiom for a Vue project, but it crashes on on launch if i don't set the url option.
If I set it to the default value, it works.
const axiom = new Axiom({ token: 'XXX', orgId: 'XXX', url: 'https://api.axiom.co' })

process is not available in the browser. Thats why it fails on line 17 in httpClient.
const url = options.url || process.env.AXIOM_URL || AxiomURL;

Not sure how to solve this, thats why I am creating an issue instead of a PR.

Hi @bobmoff, thanks for the issue! I'm faking process.env in #26 and thinking about how to better catch these issues in the future 🙌

All depending on if there's anything to release. There'll be one today  😎

@bobmoff Can you try again with 0.1.2?

Works! 🥳


Automatically indent files

Description of the problem or steps to reproduce
Imagine that I'm editing a python file:
if somevar == "something":

The moment I press enter, it should automatically add 4 spaces (or tabs or whatever, depending on config) to the newline because python expects that.
All other editors (kate, vscode) do this by default. Maybe I'm missing something, but I don't see an option to enable it on micro.
Specifications

Commit hash: b9763856
OS: Arch Linux
Terminal: Konsole
Config:
{
    "mkparents": true,
    "tabstospaces": true
}

i think vscode don't do this by default, maybe if you have the prettier extension he does it

VScode does this default

OK, I guess I was wrong then

@zyedidia Is it too difficult to implement ?
Logic is somewhat like indent=+ tab width if previous line ends with a colon and not a comment.

You can just add this to your init.lua:
function onInsertNewline(bp)
    if bp.Buf:FileType() == "python" and string.sub(bp.Buf:Line(bp.Cursor.Y-1), -1) == ":" then
        bp:InsertTab()
    end
end

There was some discussion about the autoindent functionality in #2620.


Bug: wxCommandLinkButton doesn't display

Description:

Neither our Mockup window or the wxWidgets sample is able to display the button.
Windows 10, wxWidgets 3.1.3

This is apparently another issue with manifest not being enabled because now that we have it turned on, the button displays correctly on Windows 10.


handle parameters within chain

At the moment the parameters of the call to the emulated interface are provided to all beans. But if a bean tries to modify an parameter and puts it into the protocol, e.g. the state, the new value for the parameter should be used.

This is only an issue if the parameter is a simple type. If it is a mutable complex type it can be changed, since it is passed via reference. Simple types like string are immutable, therefore they cannot be changed. Only in this case, it would be necessary to change the existing behavior.


How to download the orbit file, I met some problems

When I tried to download the orbit file I met a warning as below, meanwhile, I checked my internet that no any problems.
Warning: No internet connection! | Cannot download orbit file

I'm having this problem “Warning: No internet connection! | Cannot download orbit file” too and I'm sure my google will open

“Warning: No internet connection! | Cannot download orbit file”
I ran into that problem too. I'm sure I have no problems with my network, google pages can be opened in the browser.

Are you on windows? If so, have you tried shutting down the windows firewall to see if the connection can be established?

Hi dear friend,  I'm on windows. I'm not attention on the firewall. I'll  shut down it and try again tomorrow. Thanks for ur help. Technical support engineerHendric Lee.  Hi-target international group. -------- 原始邮件 --------发件人： Marco<EMAIL_ADDRESS>2020年5月12日周二 上午12:50收件人： GNSSpy-Project/gnsspy<EMAIL_ADDRESS>Hendric290<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>  题： Re: [GNSSpy-Project/gnsspy] How to download the orbit file, I met some problems (#2)
Are you on windows? If so, have you tried shutting down the windows firewall to see if the connection can be established?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Same issue with you. Do u have any progress? -------- 原始邮件 --------发件人： Jason Ding<EMAIL_ADDRESS>2020年5月11日周一 下午3:25收件人： GNSSpy-Project/gnsspy<EMAIL_ADDRESS>Hendric290<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>  题： Re: [GNSSpy-Project/gnsspy] How to download the orbit file, I met some problems (#2)
I'm having this problem “Warning: No internet connection! | Cannot download orbit file” too and I'm sure my google will open
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Hi,
The library checks whether you have internet or not by connecting Google via http.client. Do you have any difficulty connecting Google via browser or not? If this is the case, you can manually change the site to anything that works for you. In the meantime, I will try to change it to a site that can work everywhere. Secondly, the timeout limit is 5 seconds in check_internet function. Though I do not think that would be the problem, but you may try to test it with longer timeout limit.
Also, are you calling the download module directly or this warning is triggered during spp function?

I have no difficulty connecting Google via browser, I tried changing the time to 15 seconds and 30 seconds, but this warning still appearst，ths warming is triggered during spp function.
Best Regards
Jason Ding 丁君生 |  M.Sc student, SHAO
Shanghai Astronomical Observatory (SHAO), Chinese Academy of Sciences

------------------ Original ------------------
From<EMAIL_ADDRESS>Date: Tue, May 12, 2020 03:42 PM
To<EMAIL_ADDRESS>Cc: "丁君生"<760837268<EMAIL_ADDRESS>Subject: Re: [GNSSpy-Project/gnsspy] How to download the orbit file, I met some problems (#2)
Hi,
The library checks whether you have internet or not by connecting Google via http.client. Do you have any difficulty connecting Google via browser or not? If this is the case, you can manually change the site to anything that works for you. In the meantime, I will try to change it to a site that can work everywhere. Secondly, the timeout limit is 5 seconds in check_internet function. Though I do not think that would be the problem, but you may try to test it with longer timeout limit.
Also, are you calling the download module directly or this warning is triggered during spp function?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I have no difficulty connecting Google via browser, I tried changing the time to 15 seconds and 30 seconds, but this warning still appearst，ths warming is triggered during spp function.
------------------ Original ------------------
From<EMAIL_ADDRESS>Date: Tue, May 12, 2020 03:42 PM
To<EMAIL_ADDRESS>Cc: "丁君生"<760837268<EMAIL_ADDRESS>Subject: Re: [GNSSpy-Project/gnsspy] How to download the orbit file, I met some problems (#2)
Hi,
The library checks whether you have internet or not by connecting Google via http.client. Do you have any difficulty connecting Google via browser or not? If this is the case, you can manually change the site to anything that works for you. In the meantime, I will try to change it to a site that can work everywhere. Secondly, the timeout limit is 5 seconds in check_internet function. Though I do not think that would be the problem, but you may try to test it with longer timeout limit.
Also, are you calling the download module directly or this warning is triggered during spp function?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I have also noticed that the sp3, clk and station obs cannot be downloaded when VPN is connected to a computer via both Google.


I will take this one and add a few test cases to the onnx project

Closing this, I think #20 is good enough for now.


[SR-14008] "Library not loaded: /usr/lib/swift/libswift_Differentiation.dylib" issue for swift test

Previous ID
SR-14008

Radar
None

Original Reporter
@dan-zheng

Type
Bug

Attachment: Download

Environment
https://swift.org/builds/development/xcode/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-osx.pkg
Apple Swift version 5.3-dev (LLVM bcee1b98f3b26c5, Swift dbcf7fe1bf76226)
Target: x86_64-apple-darwin19.6.0

Additional Detail from JIRA

Votes
2

Component/s
Package Manager

Labels
Bug, AutoDiff

Assignee
None

Priority
Medium

md5: 4ecdf44eee77ebefd73035c76ce61be5

Issue Description:
With development snapshot toolchains, swift build/swift run for executable/library targets importing _Differentiation has no problem.
However, running swift test for test targets importing _Differentiation fails with a dynamic linker issue:
$ swift test
[7/7] Linking SwiftDifferentiationPackageTests

* Build Completed!
2020-12-30 14:28:23.465 xctest[20739:26994456] The bundle “SwiftDifferentiationPackageTests.xctest” couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle.
2020-12-30 14:28:23.465 xctest[20739:26994456] (dlopen_preflight(/Users/danielzheng/Differentiation/.build/x86_64-apple-macosx/debug/SwiftDifferentiationPackageTests.xctest/Contents/MacOS/SwiftDifferentiationPackageTests): Library not loaded: /usr/lib/swift/libswift_Differentiation.dylib
  Referenced from: /Users/danielzheng/Differentiation/.build/x86_64-apple-macosx/debug/SwiftDifferentiationPackageTests.xctest/Contents/MacOS/SwiftDifferentiationPackageTests
  Reason: image not found)

Setting DYLD_LIBRARY_PATH to the toolchain library directory containing libswift_Differentiation.dylib does not help:
$ DYLD_LIBRARY_PATH=/Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a.xctoolchain/usr/lib/swift/macosx swift test
2020-12-30 14:29:55.586 xctest[20925:26997481] The bundle “SwiftDifferentiationPackageTests.xctest” couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle.
2020-12-30 14:29:55.586 xctest[20925:26997481] (dlopen_preflight(/Users/danielzheng/Differentiation/.build/x86_64-apple-macosx/debug/SwiftDifferentiationPackageTests.xctest/Contents/MacOS/SwiftDifferentiationPackageTests): Library not loaded: /usr/lib/swift/libswift_Differentiation.dylib
  Referenced from: /Users/danielzheng/Differentiation/.build/x86_64-apple-macosx/debug/SwiftDifferentiationPackageTests.xctest/Contents/MacOS/SwiftDifferentiationPackageTests
  Reason: image not found)

However, manually invoking the xctest command from swift test -v with DYLD_LIBRARY_PATH does work:
$ DYLD_LIBRARY_PATH=/Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a.xctoolchain/usr/lib/swift/macosx /Applications/Xcode-beta12_3.app/Contents/Developer/usr/bin/xctest /Users/danielzheng/Differentiation/.build/x86_64-apple-macosx/debug/SwiftDifferentiationPackageTests.xctest
Test Suite 'All tests' started at 2020-12-30 14:35:43.472
Test Suite 'SwiftDifferentiationPackageTests.xctest' started at 2020-12-30 14:35:43.473
Test Suite 'DifferentiationTests' started at 2020-12-30 14:35:43.473
Test Case '-[DifferentiationTests.DifferentiationTests testExample]' started.
Test Case '-[DifferentiationTests.DifferentiationTests testExample]' passed (0.112 seconds).
Test Suite 'DifferentiationTests' passed at 2020-12-30 14:35:43.585.
     Executed 1 test, with 0 failures (0 unexpected) in 0.112 (0.112) seconds
Test Suite 'SwiftDifferentiationPackageTests.xctest' passed at 2020-12-30 14:35:43.585.
     Executed 1 test, with 0 failures (0 unexpected) in 0.112 (0.112) seconds
Test Suite 'All tests' passed at 2020-12-30 14:35:43.585.
     Executed 1 test, with 0 failures (0 unexpected) in 0.112 (0.113) seconds

Maybe this is because swift test does not pass the DYLD_LIBRARY_PATH environment variable to the xctest invocation?

I have a reproducer for this. The Swift package tests usually run just fine, but encountering this edge case stops them from happening. To reproduce:

Make an empty Swift package.
In the Sources/PACKAGE_NAME.swift file, paste the following:

import _Differentiation

extension Array.DifferentiableView: RandomAccessCollection
where Element: Differentiable {
  public typealias Element = Array<Element>.Element
  public typealias Index = Array<Element>.Index
  public typealias SubSequence = Array<Element>.SubSequence

  public subscript(position: Array<Element>.Index) -> Element {
    get { fatalError() }
    set { fatalError() }
  }

  public subscript(bounds: Range<Array<Element>.Index>) -> SubSequence {
    get { fatalError() }
    set { fatalError() }
  }

  public var startIndex: Index { fatalError() }
  public var endIndex: Index { fatalError() }
}

You can have anything in the Tests directory, as long as there's a file. It can even be blank.
Run swift test from the command line, and you get the following output. Notice the very last line.

(base) philipturner@m1-max-mbp sr14008 % swift test
objc[92004]: Class _TtCs25CheckedContinuationCanary is implemented in both /usr/lib/swift/libswift_Concurrency.dylib (0x218cb4450) and /Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2022-05-04-a.xctoolchain/usr/lib/swift/macosx/libswift_Concurrency.dylib (0x106cfc8c8). One of the two will be used. Which one is undefined.
objc[92004]: Class _TtCs17DispatchQueueShim is implemented in both /usr/lib/swift/libswift_Concurrency.dylib (0x218cb44e0) and /Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2022-05-04-a.xctoolchain/usr/lib/swift/macosx/libswift_Concurrency.dylib (0x106cfc958). One of the two will be used. Which one is undefined.
objc[92004]: Class _TtCs9MainActor is implemented in both /usr/lib/swift/libswift_Concurrency.dylib (0x218cb4570) and /Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2022-05-04-a.xctoolchain/usr/lib/swift/macosx/libswift_Concurrency.dylib (0x106cfc9f0). One of the two will be used. Which one is undefined.
warning: Usage of /Users/philipturner/Library/org.swift.swiftpm/collections.json has been deprecated. Please delete it and use the new /Users/philipturner/Library/org.swift.swiftpm/configuration/collections.json instead.
Building for debugging...
[3/3] Linking sr14008PackageTests
Build complete! (0.36s)
2022-05-14 15:30:31.658 xctest[92072:1569176] The bundle “sr14008PackageTests.xctest” couldn’t be loaded. Try reinstalling the bundle.
2022-05-14 15:30:31.658 xctest[92072:1569176] (dlopen(/Users/philipturner/Desktop/sr14008/.build/arm64-apple-macosx/debug/sr14008PackageTests.xctest/Contents/MacOS/sr14008PackageTests, 0x0109): Symbol not found: _$sSa16_DifferentiationAA14DifferentiableRzlE0B4ViewVMn
  Referenced from: /Users/philipturner/Desktop/sr14008/.build/arm64-apple-macosx/debug/sr14008PackageTests.xctest/Contents/MacOS/sr14008PackageTests
  Expected in: /usr/lib/swift/libswift_Differentiation.dylib)

@novakov-alexey I wasn't able to reproduce your compile failure from https://github.com/apple/swift-package-manager/issues/4454#issuecomment-1116961886. From your recollection, did it involve something reminiscent of my reproducer?

Related: https://github.com/tensorflow/swift-models/pull/727
Note as a result of this, the build process for testing s4tf/s4tf (formerly swift-apis) becomes greatly more complex. But it's still possible (this is an example of a workaround).

# prepare for building S4TF
export TOOLCHAINS="org.swift.57202205041a"
tensorflow_version="2.8.0"
DESTDIR=${PWD}/Library/tensorflow-${tensorflow_version}

# build S4TF
cd s4tf
swift build -Xswiftc -DTENSORFLOW_USE_STANDARD_TOOLCHAIN \
  -Xcc -I${DESTDIR}/usr/include -Xlinker -L${DESTDIR}/usr/lib

cp ${DESTDIR}/usr/lib/libx10.dylib .build/$(uname -m)-apple-macosx/debug/libx10.dylib

swift test -Xswiftc -DTENSORFLOW_USE_STANDARD_TOOLCHAIN \
  -Xcc -I${DESTDIR}/usr/include -Xlinker -L${DESTDIR}/usr/lib

export DYLD_LIBRARY_PATH="/Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2022-05-04-a.xctoolchain/usr/lib/swift/macosx"

/Applications/Xcode.app/Contents/Developer/usr/bin/xctest \
  .build/$(uname -m)-apple-macosx/debug/TensorFlowPackageTests.xctest

Perhaps I could remove this crash from S4TF by taking the Array.DifferentiableView extension out of S4TF and into the Swift Standard Library. The code moved there may or may not conflict with the intentions of DifferentiableCollection, if that protocol ever makes it into the stdlib. After that, we may need a second reproducer because the original one won't fail anymore.

@abertelrud @neonichu @lorentey - this echoes some of our discussion, correct?

The contents of the _Differentiation module have not gone through Swift Evolution. It is not an ABI stable component of the Standard Library and therefore it isn't shipping as a public SDK component on ABI stable platforms. Moving Array.DifferentiableView to the core stdlib is not an option until it has been proposed & accepted as public API.
(Beware: while /usr/lib/swift/libswift_Differentation.dylib does ship in some versions of macOS, it is not a public library on any Apple platform. Accordingly, it may disappear or its contents may change in any OS release, including point releases. Do not link to it from any production binary -- such code will break.)
% otool -L .build/x86_64-apple-macosx/debug/swift-linear-regression
.build/x86_64-apple-macosx/debug/swift-linear-regression:
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1770.255.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.60.1)
    @rpath/libswiftCore.dylib (compatibility version 1.0.0, current version 0.0.0)
    @rpath/libswiftCoreFoundation.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
    @rpath/libswiftCoreGraphics.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
    @rpath/libswiftDarwin.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
    @rpath/libswiftDispatch.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
    @rpath/libswiftFoundation.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
    @rpath/libswiftIOKit.dylib (compatibility version 1.0.0, current version 1.0.0, weak)
    @rpath/libswiftObjectiveC.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
    @rpath/libswiftSwiftOnoneSupport.dylib (compatibility version 1.0.0, current version 0.0.0)
    @rpath/libswiftXPC.dylib (compatibility version 1.0.0, current version 1.1.0, weak)
    @rpath/libswift_Differentiation.dylib (compatibility version 1.0.0, current version 0.0.0)

The version of dyld in macOS Monterey (and later) does not support using DYLD_LIBRARY_PATH to override libraries loaded via @rpath. To avoid duplicate loading of these modules (and subsequent crashes), arrange for the binary to pick up its dependencies directly from /usr/lib/swift. One way to do this is to set the minimum deployment target to macOS 10.15 or later -- this stops the compiler from using rpath-relative install names for these libraries. (As it can safely assume that /usr/lib/libswiftCore.dylib etc do exist.)
(If this dyld limitation is causing you trouble, please do file a feedback report describing the problem -- such reports do help prioritizing the issue.)

Moving Array.DifferentiableView to the core stdlib is not an option until it has been proposed & accepted as public API.

Array.DifferentiableView is already in the core stdlib. It is just removed on release toolchains, where I have to depend on philipturner/differentiation to add it back in.

Also beware -- custom builds of the Swift Standard Library (whether they were produced by manually building the stdlib from the apple/swift repo, or by downloading one of the toolchain snapshots from swift.org) aren't drop-in replacements for the stdlib that ships in any OS version.
Such stdlib builds are not guaranteed to interoperate with OS components that load the Swift stdlib, including Foundation.

One way to do this is to set the minimum deployment target to macOS 10.15 or later

So if I set platforms to [.macOS(.v10_15)] in the Swift package manifest, you expect the error to go away?

Array.DifferentiableView is already in the core stdlib. It is just removed on release toolchains, where I have to depend on philipturner/differentiation to add it back in.

What I call the "core stdlib" lives in the stdlib/public/core directory in the source tree.
The code you've linked to is part of a separate, standalone module called _Differentiation. This module is not part of the public API of the Swift Standard Library, as (AFAIK) it has not gone through Swift Evolution.

The code you've linked to is part of a separate, standalone module called _Differentiation. This module is not part of the public API of the Swift Standard Library, as (AFAIK) it has not gone through Swift Evolution.

Yes; I was asking if it's okay to make a PR to apple/swift, where I add this extension to code in the _Differentiation module. I wanted to know whether there was a reasonable chance such a PR would be merged.

So if I set platforms to [.macOS(.v10_15)] in the Swift package manifest, you expect the error to go away?

Setting a higher minimum deployment target will cause the compiler to use absolute /usr/lib/swift install names for these dylibs, allowing DYLD_LIBRARY_PATH to work properly on macOS Monterey and Ventura.

Yes; I was asking if it's okay to make a PR to apple/swift, where I add this extension to code in the _Differentiation module inside stdlib/public/Differentiation. I wanted to know whether there was a reasonable chance such a PR would be merged, and integrated into nightly snapshots.

I don't see why not. Changes to private parts of the stdlib merely require an approval from a stdlib code owner -- the only challenge there is to find someone who has time to understand & review the addition. This is a much lower bar than going through Swift Evolution, but it's not entirely free: new entry points come with a code size & maintenance cost.

How do you set the minimum deployment target when compiling with SwiftPM? I tried changing platforms: in the package manifest and the test still failed.

Did adding the version number cause the resulting binary to use /usr/lib/swift as the install name for its libswift*.dylib dependencies?

Yes; I was asking if it's okay to make a PR to apple/swift, where I add this extension to code in the _Differentiation module inside stdlib/public/Differentiation. I wanted to know whether there was a reasonable chance such a PR would be merged, and integrated into nightly snapshots.

On closer look, isn't the extension already in the _Differentiation module? Obviously I don't quite understand what you're asking to do here.

On closer look, isn't the extension already in the _Differentiation module?

Where did you find the extension? I didn't see anything that conforms Array.DifferentiableView to RandomAccessCollection in ArrayDifferentiation.swift.

Did adding the version number cause the resulting binary to use /usr/lib/swift as the install name for its libswift*.dylib dependencies?

It's the same before

Terminal output
(base) philipturner@m1-max-mbp MyPackage % rm -rf .build
(base) philipturner@m1-max-mbp MyPackage % swift build
warning: Usage of /Users/philipturner/Library/org.swift.swiftpm/collections.json has been deprecated. Please delete it and use the new /Users/philipturner/Library/org.swift.swiftpm/configuration/collections.json instead.
Building for debugging...
[2/2] Compiling MyPackage MyPackage.swift
Build complete! (1.24s)
(base) philipturner@m1-max-mbp MyPackage % swift test
warning: Usage of /Users/philipturner/Library/org.swift.swiftpm/collections.json has been deprecated. Please delete it and use the new /Users/philipturner/Library/org.swift.swiftpm/configuration/collections.json instead.
Building for debugging...
[3/3] Linking MyPackagePackageTests
Build complete! (14.12s)
2022-06-20 17:58:58.478 xctest[75824:8397467] The bundle “MyPackagePackageTests.xctest” couldn’t be loaded. Try reinstalling the bundle.
2022-06-20 17:58:58.479 xctest[75824:8397467] (dlopen(/Users/philipturner/Desktop/MyPackage/.build/arm64-apple-macosx/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests, 0x0109): Symbol not found: _$sSa16_DifferentiationAA14DifferentiableRzlE0B4ViewVMn
  Referenced from: /Users/philipturner/Desktop/MyPackage/.build/arm64-apple-macosx/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests
  Expected in: /usr/lib/swift/libswift_Differentiation.dylib)
(base) philipturner@m1-max-mbp MyPackage % otool -L .build/arm64-apple-macosx/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests
.build/arm64-apple-macosx/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests:
	/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/swift/libswiftAppKit.dylib (compatibility version 1.0.0, current version 109.0.0, weak)
	/usr/lib/swift/libswiftCore.dylib (compatibility version 1.0.0, current version 0.0.0)
	/usr/lib/swift/libswiftCoreData.dylib (compatibility version 1.0.0, current version 19.0.0, weak)
	/usr/lib/swift/libswiftCoreFoundation.dylib (compatibility version 1.0.0, current version 14.0.0, weak)
	/usr/lib/swift/libswiftCoreGraphics.dylib (compatibility version 1.0.0, current version 2.0.0, weak)
	/usr/lib/swift/libswiftCoreImage.dylib (compatibility version 1.0.0, current version 2.0.0, weak)
	/usr/lib/swift/libswiftDarwin.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
	/usr/lib/swift/libswiftDispatch.dylib (compatibility version 1.0.0, current version 11.0.0, weak)
	/usr/lib/swift/libswiftFoundation.dylib (compatibility version 1.0.0, current version 72.105.0)
	/usr/lib/swift/libswiftIOKit.dylib (compatibility version 1.0.0, current version 1.0.0, weak)
	/usr/lib/swift/libswiftMetal.dylib (compatibility version 1.0.0, current version 261.13.0, weak)
	/usr/lib/swift/libswiftObjectiveC.dylib (compatibility version 1.0.0, current version 3.0.0, weak)
	/usr/lib/swift/libswiftQuartzCore.dylib (compatibility version 1.0.0, current version 3.0.0, weak)
	/usr/lib/swift/libswiftXPC.dylib (compatibility version 1.0.0, current version 1.1.0, weak)
	/usr/lib/swift/libswift_Differentiation.dylib (compatibility version 1.0.0, current version 0.0.0)
	@rpath/XCTest.framework/Versions/A/XCTest (compatibility version 1.0.0, current version 20501.0.0)
	@rpath/libXCTestSwiftSupport.dylib (compatibility version 1.0.0, current version 1.0.0)

And after

Terminal output
(base) philipturner@m1-max-mbp MyPackage % rm -rf .build
(base) philipturner@m1-max-mbp MyPackage % swift build
warning: Usage of /Users/philipturner/Library/org.swift.swiftpm/collections.json has been deprecated. Please delete it and use the new /Users/philipturner/Library/org.swift.swiftpm/configuration/collections.json instead.
Building for debugging...
[2/2] Compiling MyPackage MyPackage.swift
Build complete! (1.18s)
(base) philipturner@m1-max-mbp MyPackage % swift test
warning: Usage of /Users/philipturner/Library/org.swift.swiftpm/collections.json has been deprecated. Please delete it and use the new /Users/philipturner/Library/org.swift.swiftpm/configuration/collections.json instead.
Building for debugging...
[3/3] Linking MyPackagePackageTests
Build complete! (14.18s)
2022-06-20 17:59:57.955 xctest[75961:8398652] The bundle “MyPackagePackageTests.xctest” couldn’t be loaded. Try reinstalling the bundle.
2022-06-20 17:59:57.955 xctest[75961:8398652] (dlopen(/Users/philipturner/Desktop/MyPackage/.build/arm64-apple-macosx/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests, 0x0109): Symbol not found: _$sSa16_DifferentiationAA14DifferentiableRzlE0B4ViewVMn
  Referenced from: /Users/philipturner/Desktop/MyPackage/.build/arm64-apple-macosx/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests
  Expected in: /usr/lib/swift/libswift_Differentiation.dylib)
(base) philipturner@m1-max-mbp MyPackage % otool -L .build/arm64-apple-macosx/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests
.build/arm64-apple-macosx/debug/MyPackagePackageTests.xctest/Contents/MacOS/MyPackagePackageTests:
	/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/swift/libswiftAppKit.dylib (compatibility version 1.0.0, current version 109.0.0, weak)
	/usr/lib/swift/libswiftCore.dylib (compatibility version 1.0.0, current version 0.0.0)
	/usr/lib/swift/libswiftCoreData.dylib (compatibility version 1.0.0, current version 19.0.0, weak)
	/usr/lib/swift/libswiftCoreFoundation.dylib (compatibility version 1.0.0, current version 14.0.0, weak)
	/usr/lib/swift/libswiftCoreGraphics.dylib (compatibility version 1.0.0, current version 2.0.0, weak)
	/usr/lib/swift/libswiftCoreImage.dylib (compatibility version 1.0.0, current version 2.0.0, weak)
	/usr/lib/swift/libswiftDarwin.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
	/usr/lib/swift/libswiftDispatch.dylib (compatibility version 1.0.0, current version 11.0.0, weak)
	/usr/lib/swift/libswiftFoundation.dylib (compatibility version 1.0.0, current version 72.105.0)
	/usr/lib/swift/libswiftIOKit.dylib (compatibility version 1.0.0, current version 1.0.0, weak)
	/usr/lib/swift/libswiftMetal.dylib (compatibility version 1.0.0, current version 261.13.0, weak)
	/usr/lib/swift/libswiftObjectiveC.dylib (compatibility version 1.0.0, current version 3.0.0, weak)
	/usr/lib/swift/libswiftQuartzCore.dylib (compatibility version 1.0.0, current version 3.0.0, weak)
	/usr/lib/swift/libswiftXPC.dylib (compatibility version 1.0.0, current version 1.1.0, weak)
	/usr/lib/swift/libswift_Differentiation.dylib (compatibility version 1.0.0, current version 0.0.0)
	@rpath/XCTest.framework/Versions/A/XCTest (compatibility version 1.0.0, current version 20501.0.0)
	@rpath/libXCTestSwiftSupport.dylib (compatibility version 1.0.0, current version 1.0.0)

Adding platforms: [.macOS(.v12)] to Package.swift.

Also, here's my /usr/lib and /usr/lib/swift:

Ah thanks! What I missed that you want to add this conformance to this existing type. I don't have an opinion on whether that is a desirable thing -- I am not familiar with this module -- however, I doubt moving the conformance to the Swift repository will resolve the root cause of the loader error.
objc[92004]: Class _TtCs25CheckedContinuationCanary is implemented in both /usr/lib/swift/libswift_Concurrency.dylib (0x218cb4450) and /Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2022-05-04-a.xctoolchain/usr/lib/swift/macosx/libswift_Concurrency.dylib (0x106cfc8c8). One of the two will be used. Which one is undefined.
objc[92004]: Class _TtCs17DispatchQueueShim is implemented in both /usr/lib/swift/libswift_Concurrency.dylib (0x218cb44e0) and /Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2022-05-04-a.xctoolchain/usr/lib/swift/macosx/libswift_Concurrency.dylib (0x106cfc958). One of the two will be used. Which one is undefined.
objc[92004]: Class _TtCs9MainActor is implemented in both /usr/lib/swift/libswift_Concurrency.dylib (0x218cb4570) and /Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2022-05-04-a.xctoolchain/usr/lib/swift/macosx/libswift_Concurrency.dylib (0x106cfc9f0). One of the two will be used. Which one is undefined.

These messages indicate that the library libswift_Concurrency.dylib has been loaded twice. This is a significant problem that must be fixed.
The most likely cause is that the executable invoked here has an @rpath-relative load command for this library (to support back deployment of concurrency features below macOS 12), while it also loads OS frameworks that load it directly from /usr/lib/swift. (E.g., such a combination can trigger the dyld issue with DYLD_LIBRARY_PATH, but if the binary's RPATH is set incorrectly, it can also lead to two different concurrency libraries getting loaded by default, even without a library path override.)
The first order of business would be to figure out which binary is doing this and fixing it. (It may well be a binary that ships in the downloadable toolchain -- I know we have such issues there, we've seen something similar last week. 😞)
2022-05-14 15:30:31.658 xctest[92072:1569176] The bundle “sr14008PackageTests.xctest” couldn’t be loaded. Try reinstalling the bundle.
2022-05-14 15:30:31.658 xctest[92072:1569176] (dlopen(/Users/philipturner/Desktop/sr14008/.build/arm64-apple-macosx/debug/sr14008PackageTests.xctest/Contents/MacOS/sr14008PackageTests, 0x0109): Symbol not found: _$sSa16_DifferentiationAA14DifferentiableRzlE0B4ViewVMn
  Referenced from: /Users/philipturner/Desktop/sr14008/.build/arm64-apple-macosx/debug/sr14008PackageTests.xctest/Contents/MacOS/sr14008PackageTests
  Expected in: /usr/lib/swift/libswift_Differentiation.dylib)

This implies that the loader tried to load the non-public library /usr/lib/swift/libswift_Differentiation.dylib from the OS, so either DYLD_LIBRARY_PATH wasn't set correctly, or the launched process did not inherit the environment variable as expected.
As the _Differentiation module is configured as if it was a stdlib component (even though it doesn't ship as one), the right way to test its contents is to override its location via DYLD_LIBRARY_PATH. Unfortunately, since it shares the same install location as actual stdlib modules, overriding the library path also overrides the stdlib, which is generally inadvisable if you're also importing Foundation.

Did adding the version number cause the resulting binary to use /usr/lib/swift as the install name for its libswift*.dylib dependencies?
It's the same before

Oh I see, so Alexey's comment above is outdated. That's great -- so the dyld issue does not apply: you only need to figure out how to get DYLD_LIBRARY_PATH to apply to the launched process.

Also, here's my /usr/lib and /usr/lib/swift:

Most dylibs whose install names are under these directories do not actually exist there as separate files; instead, the dynamic loader picks them up from the system-wide dyld shared cache.

These messages indicate that the library libswift_Concurrency.dylib has been loaded twice. This is a significant problem that must be fixed.

That error is present on trunk snapshots, but not on 5.7 branch snapshots. For example, the 2022-05-04 and 2022-06-08 trunk snapshots produce the concurrency error. The 2022-06-04 v5.7 and 2022-06-13 v5.7 snapshots do not. I was building the package using the June 13, 2022 v5.7 Development Snapshot today.

As the _Differentiation module is configured as if it was a stdlib component (even though it doesn't ship as one), the right way to test its contents is to override its location via DYLD_LIBRARY_PATH. Unfortunately, since it shares the same install location as actual stdlib modules, overriding the library path also overrides the stdlib, which is generally inadvisable if you're also importing Foundation.

Would that mean I can't access one of Apple's API frameworks like Metal if DYLD_LIBRARY_PATH was overriden? For reference, Metal depends on Foundation and ObjectiveC.

On Apple platforms, the Swift Standard Library is an integral part of the OS, and while its public ABI is stable, its binary interface with the rest of the operating system isn't. Therefore, we can only support loading higher-level OS frameworks (incl. Foundation) with the specific version of the Standard Library that ships within the same OS release.  In particular, some system integration entry points that are shipping in the OS may not be present in the open source toolchains, or they may have different expected behavior across OS releases. Allowing the system entry points to change is crucial to improving and/or maintaining system performance across OS versions.
Replacing the stdlib with alternative builds may or may not work. In general, I would expect things to mostly work when loading fresh stdlib builds on the macOS version that we have installed on ci.swift.org -- but our test suite is limited to exercising parts of Foundation (some of the bridging implementations, to be specific). It is not testing other frameworks like Metal, and it doesn't even cover all parts of Foundation.
(We try to avoid intentionally breaking things, but since we're not actively testing interoperability (or even designing for it), things may be in various stages of brokenness at any given point. The more frameworks you import and the farther you get from the macOS version that's on CI, the more likely you'll run into subtle (or not so subtle) issues.)

I don't have an opinion on whether that is a desirable thing -- I am not familiar with this module -- however, I doubt moving the conformance to the Swift repository will resolve the root cause of the loader error.

Let's test that assumption, because if it happens to fix the error, that's good news for S4TF. And if it doesn't fix the error, we learn that we should not add that extension to the Stdlib yet (maybe hold off on DifferentiableCollection too).

I got S4TF compiling on a release tool chain (Xcode 14 beta, Swift 5.7 release). The test error still happened, even though AutoDiff is imported as a Swift package (philipturner/differentiation). This means we can narrow down the crash without building a custom toolchain. This is great news!

Things just got a lot wierder... I linked it to a compiler crash that happens exclusively on release toolchains. It might not even be a bug with SwiftPM, but instead something extremely corrupted and hidden in the compiler. So hidden that it requires rewriting the dependency chain of _Differentiation just to be exposed. I found it on the Xcode beta (5.7 release), but immediately reproduced it on the 5.6.1 release, which we can all test. This also fails on development toolchains, but with a different error message. Probably because you're not supposed to compile philipturner/differentiation on development toolchains.
I did get S4TF to compile on a development toolchain + philipturner/differentiation, after commenting out code causing the crash here (against my expectations). Attempting to override the standard library's _Differentiation with my custom package's Differentiation seems awfully similar to attempts to extend Array, which spawned SR-14008. I suspect they are related.

Reproducer (I'll narrow this down more by shrinking philipturner/differentiation):
Make an empty Swift package via swift package init. In my case, it is AutoDiffPackage2. For the Package.swift manifest, paste the following. It creates a dependency to philipturner/differentiation. Also, the Swift tools version at the top is 5.6.
// swift-tools-version: 5.6
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "AutoDiffPackage2",
    products: [
        // Products define the executables and libraries a package produces, and make them visible to other packages.
        .library(
            name: "AutoDiffPackage2",
            targets: ["AutoDiffPackage2"]),
    ],
    dependencies: [
        // Dependencies declare other packages that this package depends on.
        // .package(url: /* package url */, from: "1.0.0"),
       .package(url: "https://github.com/philipturner/differentiation", branch: "main"),
    ],
    targets: [
        // Targets are the basic building blocks of a package. A target can define a module or a test suite.
        // Targets can depend on other targets in this package, and on products in packages this package depends on.
        .target(
            name: "AutoDiffPackage2",
            dependencies: [
                .product(name: "_Differentiation", package: "differentiation"),
            ]),
        .testTarget(
            name: "AutoDiffPackage2Tests",
            dependencies: ["AutoDiffPackage2"]),
    ]
)

In the only source file within Sources/AutoDiffPackage2, replace the template code with the following. It imports a module called Differentiation (no underscore), which is part of my workaround for enabling AutoDiff on release (and now apparently development?) toolchains.
import Differentiation

extension Array.DifferentiableView: RandomAccessCollection
where Element: Differentiable {
  // All of these properties must be public.
  public typealias Element = Array<Element>.Element
  public typealias Index = Array<Element>.Index
  public typealias SubSequence = Array<Element>.SubSequence

  public subscript(position: Array<Element>.Index) -> Element {
    get { fatalError() }
    set { fatalError() }
  }

  public subscript(bounds: Range<Array<Element>.Index>) -> SubSequence {
    get { fatalError() }
    set { fatalError() }
  }

  public var startIndex: Index { fatalError() }
  public var endIndex: Index { fatalError() }
}

struct Tensor: Differentiable & AdditiveArithmetic {
  typealias TangentVector = Self

  static func == (lhs: Self, rhs: Self) {
    fatalError()
  }

  static func + (lhs: Self, rhs: Self) {
    fatalError()
  }
}

@differentiable(reverse)
func Tensor_stack(_ lhs: Tensor) -> Tensor {
  Tensor_init(stacking: [lhs])
}

@differentiable(reverse)
func Tensor_init(stacking tensors: [Tensor]) -> Tensor {
  fatalError()
}

@derivative(of: Tensor_init(stacking:))
func _vjpStacking(
  stacking tensors: [Tensor]
) -> (value: Tensor, pullback: (Tensor) -> Array<Tensor>.TangentVector) {
  fatalError()
}

Error message on release toolchains:
Error message on development toolchains:

Also, here's the branch I'm currently working on that compiles S4TF on the Xcode 14 beta toolchain: https://github.com/philipturner/s4tf/tree/compile-on-release-toolchain

https://github.com/philipturner/s4tf-crasher-1

Now I have a narrowed reproducer for real. Substitute the reproducer in https://github.com/apple/swift-package-manager/issues/4454#issuecomment-1126799942 with this.
import _Differentiation

fileprivate struct Array_DifferentiableView<Element> {}

extension Array_DifferentiableView: Differentiable {
  internal init(_ base: Array<Element>) {
    fatalError()
  }

  @derivative(of: init(_:))
  internal static func _vjpInit(_ base: Array<Element>) -> (
    value: Array_DifferentiableView<Element>,
    pullback: (TangentVector) -> Array<Element>.TangentVector
  ) where Element: Differentiable {
    fatalError()
  }
}

// Pay attention to this.
extension Array_DifferentiableView: AdditiveArithmetic {
  internal static func + (lhs: Self, rhs: Self) -> Self { fatalError() }
  internal static func - (lhs: Self, rhs: Self) -> Self { fatalError() }
}

This produces the crash as usual:
(base) philipturner@m1-max-mbp AutoDiffPackage2 % rm -rf .build && swift test
Building for debugging...
[5/5] Linking AutoDiffPackage2PackageTests
Build complete! (1.22s)
2022-07-04 11:48:59.526 xctest[74390:611491] The bundle “AutoDiffPackage2PackageTests.xctest” couldn’t be loaded. Try reinstalling the bundle.
2022-07-04 11:48:59.526 xctest[74390:611491] (dlopen(/Users/philipturner/Desktop/AutoDiffPackage2/.build/arm64-apple-macosx/debug/AutoDiffPackage2PackageTests.xctest/Contents/MacOS/AutoDiffPackage2PackageTests, 0x0109): Symbol not found: _$sSa16_DifferentiationAA14DifferentiableRzlE0B4ViewVMn
  Referenced from: /Users/philipturner/Desktop/AutoDiffPackage2/.build/arm64-apple-macosx/debug/AutoDiffPackage2PackageTests.xctest/Contents/MacOS/AutoDiffPackage2PackageTests
  Expected in: /usr/lib/swift/libswift_Differentiation.dylib)

But something interesting happens when you change the visibility of Array_DifferentiableView.+ and Array_DifferentiableView.-.

+
-
Crash

internal
internal
same as usual

fileprivate
internal
same as usual

private
internal
Crash 1

internal
fileprivate
same as usual

fileprivate
fileprivate
same as usual

private
fileprivate
Crash 1

internal
private

This bug does not actually impact S4TF on release toolchains. I encountered an error while running tests, but did not realize that the error was just the X10 error. I bypassed this by manually copying libx10 into .build/debug. This error masks the one with loading libswift_Differentiation. In the S4TF build script, I shied away from copying X10 because it was useless. Calling .../usr/bin/xctest loaded X10 without copying it because DYLD_LIBRARY_PATH actually worked. Also, hard-coding .build/debug would make release builds fail or require more complex setup.
After suppressing the X10 error on v5.7 release, swift tests ran the SwiftPM tests against my expectations. This is probably the first time in 20 months that S4TF could run tests on macOS, directly through swift test. I really wanted to fix SR-14008 so that in the future, you could do everything related to S4TF with only Xcode. The backend would be Metal/OpenCL, which is entirely Swift. You don't need to use Bash scripting or install Bazel because X10 isn't in the dependency chain. You can run SwiftPM tests directly in Xcode - if not, then through a simple swift test on the command line.
My vision for S4TF is something that even beginners to Swift can use. You can compile, import, and contribute to it, immediately. No one has to wait 20 minutes to download a massive dev toolchain on their computer. No one has to wait over an hour for Bazel to compile, or even learn how to use Bash or the command line. You can run it on any platform - even iOS - because the new dependency chain is written entirely on Swift (philipturner/differentiation, swift-reflection-mirror, swift-opencl, s4tf/metal, s4tf/opencl). These are the accessibility barriers I faced when Google sponsored S4TF, and I'm glad they will be lifted upon the release of Swift 5.7.
With that, I can safely say I won't be the one fixing SR-14008 (if it even gets fixed).

This doesn’t appear to be an active issue. Let us know if there’s a recent, consolidated reproduction!

CC: @asl
Anton has been looking into auto differentiation and may have interest in this.


neutron contract rpc

still some issue("bad-tx-improper-version-0" error in validation.cpp) , it needs to be fixed in https://github.com/qtumproject/qtum-neutron/pull/4

@Earlz fixed the merge conflicts, can u review it


Generated resource: incorrect class/namespace

Laravel Rest Api Version
1.1
Laravel Version
10.10
PHP Version
8.2
Database Driver & Version
MySQL 8.1.0 on Windows 10 Pro (x64)
Description
When generating a resource using the php artisan rest:resource {name} command it will generate a resource class but generates the actions and instructions methods with an incorrectly namespaced class. This class is not used/imported into the resource class by default, which results in an Exception and intelisense errors:

What it should look like:

To fix this I can see 2 possible solutions:

Fix the classes on the actions and instructions methods to include the full class path.
Import the class into the file (use \Lomkit\Rest\Http\Requests\RestRequest;) and remove the full path from the other methods.

I noticed you prefer to include the complete path so I may create a PR applying solution 1 if allowed.
Steps To Reproduce

Install lomkit/laravel-rest-api^1.1
Run command php artisan rest:resource TestResource
Inspect the generated file, should be located at {projectroot}/app/Rest/Resources/TestResource.php
Scroll down to the actions and instructions methods and see the incorrect result.

Hello @timyourivh,
Thanks for your feedback !
I'd prefer adding this with full class path, that's what i'm used to see in most cases.
If you find time, feel free to submit a PR, i also might be able to do this this week-end :)


Datarepository.Save with filename/fileinfo throws if full path is provided.

is not a valid filename. Contains: {':', ''}

Fixed.


Author search result without co-author being displayed when there are multiple authors in dc.contributor.author field

Describe the bug
If there are multiple authors in dc.contributor.author field, the search result only shows the author who is being searched. However, if the authors in dc.creator field, the search result shows all co-authors as well.
To Reproduce
Steps to reproduce the behavior:

Query "first" in search box - https://demo7.dspace.org/search?query=first
The result for https://demo7.dspace.org/items/1984e894-70ee-41ea-8566-83d6477139c2 only shows first as the author, the second author is not shown.

Expected behavior
Expect the co-authors in the search result as well.
Related work

Fixed by #2983


How to use the WebSocket

I am failing on figuring out how to use the WebSocket for receiving messages. Is there an example code?

The stream endpoint is not included inside the api client because it is not definable via the swagger 2.0 specification. You can use any websocket client library to connect to the /stream endpoint with a client token.

OK, thank you for this clarification.


Calendar in UTC

Hi there,
Love this directive!
I've been wondering if there is a way to show the calendar in UTC?

You might play around with the develop branch and see if using the
modelType = seconds works for you.
On Wed, Dec 16, 2015 at 9:57 AM, shahar<EMAIL_ADDRESS>wrote:

Hi there,
Love this directive!
I've been wondering if there is a way to show the calendar in UTC?
—
Reply to this email directly or view it on GitHub
https://github.com/dalelotts/angular-bootstrap-datetimepicker/issues/257
.

Hi Dale,
Will do, and again thank you for this amazing directive


BEAM-6306 Upgrade Jackson to version 2.9.8

Jackson 2.9.8 addresses several CVEs for more info
https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8

Run Spark ValidatesRunner

Run Java PreCommit


Document BPM hardcoded timeouts and standard troubleshooting procedure

Hi,
In this PR, I started documenting the hardcoded "stop" procedure in BPM.
Then I detailed the concept of "PID check" in an adjacent section, and finally added some troubleshooting default procedure, and tips for using the tools provided by default on stemcells.
Cheers

Thanks for commit!


Midsummer Milestone

@twood02 Hi professor, I cleaned up the scripts a little and added some comments, Amanda and Sarah have sent the graphing scripts, which are also included in this pull request.

@twood02 Hi professor, These new commits now include the code for the client policies, the readme, and the fixes based on the previous feedback.


regarding react-native-firebase push notification on ios

I'm having trouble with react-native-firebase push notification on ios.
Could you explain how the firebase and sendbird are linked?
Is this right that if a user gets a message while disconnected, the message is delivered through firebase with their registered FCM token automatically? or should I write a logic to send messages to FCM ?
I did added 'sbRegisterPushToken' and 'onMessageListener' logic but push notification is not working.
As far as I understand, uploading .p12 file to SendBird Dashboard is not necessary for react-native app. Is this right?

Hi, @maruzzing!

Could you explain how the firebase and sendbird are linked?

Basically, all push notifications are sent from SendBird server through FCM and then delivered to end users. Upon request of sending messages to user, SendBird server detects if the user is online or not, and if they are offline, it sends messages to FCM based on its server's API key. FCM, in turn, sends messages to end users using APNS certificate (for Apple).

Is this right that if a user gets a message while disconnected, the message is delivered through firebase with their registered FCM token automatically? or should I write a logic to send messages to FCM ?

Yes that's right. And good news are you don't have to write any logic. For react native application you have to explicitly call sb.setBackgroundState(); in order to signal server that app is in the background mode and to receive the push notifications. After the application is entered into foreground, you need to call sb.setForegroundState(); This logic is already written in App.js of the react native sample app.

As far as I understand, uploading .p12 file to SendBird Dashboard is not necessary for react-native app. Is this right?

If you use a sample app which is default in this repo and its APP_ID, then you do not need to upload the .p12 file or configure FCM. However, if you want to create a new application, then you need to configure the settings for push notifications. On the dashboard, there is application -> settings -> notifications tab, which allows you to configure the push notifications properly.
Also, these docs may be helpful:

https://docs.sendbird.com/ios/push_notifications?_ga=2.170183264.1782264590.1560403683-823716730.1555904874. (Disregard step4 and above, you just need to upload the APNS certificate on FCM)
https://docs.sendbird.com/ios/push_notifications?_ga=2.170183264.1782264590.1560403683-823716730.1555904874

I did added 'sbRegisterPushToken' and 'onMessageListener' logic but push notification is not working.

You don't need to add sbRegisterPushToken to onMessageListener, basically it is not used frequently. It fetches user's unique push token from APNS or FCM and saves them on the SendBird server to identify a user in future.
This explanation covers only Javascript SDK, other platforms might work differently.
Please if you have any questions or suggestions, let us know :-)
Thank you for using our SDK!

Hi
i am having trouble in getting push notifications in both platforms(ios/android)

i am able to send sample notification from firebase console and recieiving it correctly on both platforms
i had followed sendbird documentation of handling/setting up pushnotifications
the chat application works fine (able to send and receive messages)
when i tried to add API key for android , in the documentation it shows its having sender id also, but when i tried to add it just asked for API key
when i check sendbird dashboard , the android push tokens are registered there successfully
tried to get the notifications by offline and online , both doesent get worked

pls help me on this


peekData*E is wrong

it will only read the first byte, since peek won't move the position...
https://github.com/PMunch/binaryparse/blob/5f8f4a745ffded841975cd1166b328ee843ff81a/binaryparse.nim#L141-L153

Not sure how I've missed that, and how it hasn't broken anything yet. Good catch!

Not sure how I've missed that, and how it hasn't broken anything yet. Good catch!

Sorry this has taken so long, fixed in: https://github.com/PMunch/binaryparse/commit/7508fa718bc9bd53a87024081de6f1fdec9bb762


Issue#309 [Carousel] Add accessibility features to navigate through t…

…he slides

add support for navigating through the slides by using keyboard keys
add Hobbes UI tests

Codecov Report

Merging #311 into development will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             development     #311   +/-   ##
==============================================
  Coverage          82.22%   82.22%
  Complexity           871      871
==============================================
  Files                 82       82
  Lines               2790     2790
  Branches             517      517
==============================================
  Hits                2294     2294
  Misses               205      205
  Partials             291      291

Continue to review full report at Codecov.

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


Publish on npm

I want to remove reliance on bower completely from my project and would appreciate if you'd publish the package to npm.

Published via https://github.com/aayushkapoor206/rdash-ui


Move RequestAuthentication policy creation to iap-enabler for gitops friendliness

Problem
In my gitops setup I was facing a race condition between Fluxcd and iap-enabler where they were both updating the ingress-jwt RequestAuthentication resource:

Fluxcd creates/updates the ingress-jwt RequestAuthentication resource without the audience (TO_BE_PATCHED)
iap-enabler resolves the backend id and patches the ingress-jwt audience

Solution
Move ingress-jwt RequestAuthentication creation logic to iap-enabler.

Move policy.yaml from Kustomize resources list to envoy-config ConfigMap
Refactor setup_backend.sh to replace TO_BE_PATCHED with the correct audience and apply policy.yaml to create/update ingress-jwt

Thank you @fabito , will this change make policy.yaml out of the control from gitops Fluxcd? Also, should we use more specific placeholder than TO_BE_PATCHED since we use sed to replace the value now? Previously we specify the yaml path for the JWT_AUDIENCE replacement.

Thank you @fabito , will this change make policy.yaml out of the control from gitops Fluxcd?
Yep, solely managed by iap-enabler now

Also, should we use more specific placeholder than TO_BE_PATCHED since we use sed to replace the value now?
Sure!

/lgtm
/approve

/assign @zijianjoy

/lgtm
/approve


Fix #149 - Replace map with array for job with no args.

When decoding payload to create a job replace empty map for args with
empty array.

Coverage increased (+0.03%) to 87.838% when pulling 2191d0fc15649acc4629909069ac75ed86af6795 on krasio:issues/149-job-with-no-args into e98f7c0129cf1d86730b35a3c76a13ab02a78431 on edgurgel:master.

Coverage increased (+0.03%) to 87.838% when pulling 2191d0fc15649acc4629909069ac75ed86af6795 on krasio:issues/149-job-with-no-args into e98f7c0129cf1d86730b35a3c76a13ab02a78431 on edgurgel:master.

Thanks once again, @krasio 🎉 This seems to be the only way to "fix" the issue with the cjson lib as you pointed out. I will do some smoke tests before releasing. Thanks so much 👍


test: add oid4vci negative scenario tests

Description:
Checklist:

[ ] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

coverage: 48.47% (-0.09%) from 48.558%
when pulling 906f8fd0646b2382ed2eff42fb6da322646f6234 on test/oid4vci
into e532ba604c4e8e820345226d842d3b27813f5e66 on main.


editable correlation plot list

In correlation plot, is it possible to change the order of appealing item (phase)?

Impletemed in beb8e6c.
Closing this issue for now


grpc_bidirectional_streaming_client.out file details should be updated

grpc_bidirectional_streaming_client.out file details should be updated. Currently the out file state to run commands [1] and [2]
[1] ballerina build client
[2] ballerina run client.balx
However, for the test to run I had to give the second command as  ballerina run client without the balx. Best if we can update the documentation with the corrections

Please fix in all grpc sample out files

@shavantha once we build ballerina project, correct way is to run the balx file.
In ballerina, we do support run ballerina code giving the package like (ballerina run <package_name>). if we issue this command. bvm internally compile the code and run.
since we already build the project, we don't need to compile the code again. we can run the compiled code using the command,
ballerina run client.balx