MSID: 96576 Version: 2 DOI: 10.1101/2<IP_ADDRESS>2317

MSID: 96576
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>2317
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=96576
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2317

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/96576v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>2317
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/96576/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Fixing issues with refs.


fix date handling on Linux

Well, #12 didn't work.  What's actually going on is that the API returns dates as integers.  On macOS, Swift was able to implicitly convert, but not on Linux.

It does work properly after all.  I thought there might be APIs which would return a Double on 64-bit but a Float on 32-bit, but I no longer think there are (except for CGFloats).
TimeInterval is just typealiased to Double, so using it instead of Double wouldn't change any behavior, but it would make the code clearer.


Improve start page after connecting

After connecting with my wallet, I always land on https://app.web3inbox.com/notifications/, which is an empty page.

2 options to improve the experience:
A) Redirect users to the Discover page https://app.web3inbox.com/notifications/new-app
B) Always show the latest notifications page (this carries the risk of users missing new notifications)
I advocate for option A.
Edit: Its possible this occurs only with wallets that have no new / latest notifications. Regardless of this, a user should always land on the Discover page first.

Closed with #254


Failing for very large numbers?

When running some random data through Hashids I found this failure:
@Test
public void test_issue11() throws Exception
{
    final Hashids hashIds = new Hashids("Fd2s3lDF1l39PDybtiZI", 5);
    final long id =<PHONE_NUMBER>169105809L;
    assertThat(id, equalTo(hashIds.decrypt(hashIds.encrypt(id))[0]));
}

java.lang.AssertionError:
Expected:<PHONE_NUMBER>169105408L
but: was<PHONE_NUMBER>169105809L

I just tried rerunning the above test using Long.MAX_VALUE as input and the test seem to pass no problem. Any other particular reason to limit the MAX_NUMBER to 9_007_199_254_740_992L?
@Test
    public void test_issue11() throws Exception
    {
        final Hashids hashIds = new Hashids("Fd2s3lDF1l39PDybtiZI", 5);
        final long id = Long.MAX_VALUE;
        System.out.println(id);
        assertEquals(id, hashIds.decode(hashIds.encode(id))[0]);
    }

The reason is interop, the javascript version is limited(At least, it was) to 9_007_199_254_740_992L.


Separate Behaviors for touch and mouse input

What feature or improvement do you think would benefit Files?
An issue that I have with Files and Windows Explorer is that you have to use the same click-to-open behavior for mouse and touch.
Touchscreen is an input that makes much more sense to allow for single-click input to open a folder or file.
Most people are already accustomed to Mouse requiring a double click to actually open something on any OS they use.
It would be great if there was an option to use single-click to open for touchscreens only while double-click for mice.
Requirements

This feature would require differentiating between touch and mouse inputs
I don't know what else it would require.

Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.3448
Comments
No response

Thanks for the feedback, Merging with #5052. You can check there or click subscribe in the right sidebar for updates.


fix: sort etcd args to make them deterministic

Fix non-deterministic order of etcd args.
fixes #248

It will be good to cover it with some test


Flutter doctor crashed, Unexpected tag 69 (ForStatement) at AndroidStudio._allLinuxOrWindows._hasStudioAt

I install flutter in my ubuntu 18.10 and it's working okey and suddenly stop working and give me this error when i was using flutter doctor
command
flutter doctor
exception
_CompileTimeError: error: Unexpected tag 69 (ForStatement) in<EMAIL_ADDRESS>expected expression
#0      AndroidStudio._allLinuxOrWindows._hasStudioAt (package:flutter_tools/src/android/android_studio.dart:222:22)
#1      AndroidStudio._allLinuxOrWindows (package:flutter_tools/src/android/android_studio.dart:238:46)
#2      AndroidStudio.allInstalled (package:flutter_tools/src/android/android_studio.dart:170:40)
#3      AndroidStudioValidator.allValidators (package:flutter_tools/src/android/android_studio_validator.dart:20:55)
#4      _DefaultDoctorValidatorsProvider.validators (package:flutter_tools/src/doctor.dart:63:35)
#5      Doctor.validators (package:flutter_tools/src/doctor.dart:132:46)
#6      Doctor.startValidatorTasks (package:flutter_tools/src/doctor.dart:139:39)
#7      Doctor.diagnose (package:flutter_tools/src/doctor.dart:211:41)
<asynchronous suspension>
#8      DoctorCommand.runCommand (package:flutter_tools/src/commands/doctor.dart:59:39)
<asynchronous suspension>
#9      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:490:18)
#10     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#11     _rootRunUnary (dart:async/zone.dart:1132:38)
#12     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#13     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#14     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#15     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#16     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#17     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
#18     _rootRun (dart:async/zone.dart:1124:13)
#19     _CustomZone.run (dart:async/zone.dart:1021:19)
#20     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#21     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#22     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#23     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#24     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#25     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

Hi @AhmedAlaa96
are you running  flutter doctor -v
from your flutter console?
Thank you

Hi @iapicca
I'm using android studio terminal then give me this error so I try  flutter doctor on ubuntu terminal
Didn't work either but, after closing the project in android studio and close android studio and try again it worked but i want why that's happens this is not the first time can you help me with that
Thank you

after closing the project in android studio and close android studio and try again it worked

If it's working now, can we get the output of flutter doctor -v?  That will tell us what version you're on so we can try to track it down.

@jmagman I run flutter doctor -v and that's what i get:
`[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Linux, locale en_US.UTF-8)
• Flutter version 1.9.1+hotfix.6 at /home/ahmed-alaa/Android Studio/flutter/flutter
• Framework revision 68587a0916 (10 weeks ago), 2019-09-13 19:46:58 -0700
• Engine revision b863200c37
• Dart version 2.5.0
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at /home/ahmed-alaa/Android Studio/Sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• Java binary at: /home/ahmed-alaa/Android Studio/android-studio-ide-191.5977832-linux/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[✓] Android Studio (version 3.5)
• Android Studio at /home/ahmed-alaa/Android Studio/android-studio-ide-191.5977832-linux/android-studio
• Flutter plugin version 41.1.2
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)`

This error happens when kernel binary (in this case flutter tool snapshot) has a structure unexpected by the VM.
The root cause varies: might have been a bug in the CFE or version skew between kernel binary and the VM.
I think given the age of the issue (and the fact that it went away) we would not be able to track it down to the root cause.


Task: add a new PATCH /api/v1/metadata/sign endpoint

What is the task about?
Add a new PATCH /api/v1/metadata/sign endpoint.
This endpoint will be used to override an existing Distributed Asynchronous Process (DAS) no matter if it's for bootstrap or metadata update.
The payload should include a new root (or possibly other) metadata that is not yet fully signed.
For example:
"metadata": {
    "root": {
      "signatures": [
        {
          "keyid": "1cebe343e35f0213f6136758e6c3a8f8e1f9eeb7e47a07d5cb336462ed31dcb7",
          "sig": "c471d9376651ed68bf5b0ce61bd21ba0bef7c38f293f8a4cfb3d56934e1c2f9106d58a9d57fafdd559d1e66e2581c21755b1ef5a6cdef59c40fcdc7bb158c80b"
        },
        {
          "keyid": "7feb22ed6a1139913ebdbfac85513890814e661d94084212972ba0c0a5c8ce27",
          "sig": "5558cdf391cc1feaeacf2a25e26b2042e50d286296c2a0c4bc3421788e8e11465b6956c3dc0e7ada29672e3740fa003b518e9d9c2a8411b5b279be94a40f750f"
        }
      ],
      "signed": {
        "_type": "root",
        "consistent_snapshot": true,
        "expires": "2024-04-17T08:51:40Z",
        "keys": {
          "1cebe343e35f0213f6136758e6c3a8f8e1f9eeb7e47a07d5cb336462ed31dcb7": {
            "keytype": "ed25519",
            "keyval": {
              "public": "ad1709b3cb419b99c5cd7427d6411522e5a93aec6767453e91af921a73d22a3c"
            },
            "scheme": "ed25519"
          },
          "7feb22ed6a1139913ebdbfac85513890814e661d94084212972ba0c0a5c8ce27": {
            "keytype": "ed25519",
            "keyval": {
              "public": "664d366b6838648405e1e18e9ef5b4e326713b0c0338935e2f715b9f02a05313"
            },
            "scheme": "ed25519"
          },
          "800dfb5a1982b82b7893e58035e19f414f553fc08cbb1130cfbae302a7b7fee5": {
            "keytype": "ed25519",
            "keyval": {
              "public": "7098f769f6ab8502b50f3b58686b8a042d5d3bb75d8b3a48a2fcbc15a0223501"
            },
            "scheme": "ed25519"
          },
          "f7a6872f297634219a80141caa2ec9ae8802098b07b67963272603e36cc19fd8": {
            "keytype": "ed25519",
            "keyval": {
              "public": "9fe7ddccb75b977a041424a1fdc142e01be4abab918dc4c611fbfe4a3360a9a8"
            },
            "scheme": "ed25519"
          }
        },
        "roles": {
          "root": {
            "keyids": [
              "1cebe343e35f0213f6136758e6c3a8f8e1f9eeb7e47a07d5cb336462ed31dcb7",
              "800dfb5a1982b82b7893e58035e19f414f553fc08cbb1130cfbae302a7b7fee5",
              "7feb22ed6a1139913ebdbfac85513890814e661d94084212972ba0c0a5c8ce27"
            ],
            "threshold": 1
          },
          "snapshot": {
            "keyids": [
              "f7a6872f297634219a80141caa2ec9ae8802098b07b67963272603e36cc19fd8"
            ],
            "threshold": 1
          },
          "targets": {
            "keyids": [
              "f7a6872f297634219a80141caa2ec9ae8802098b07b67963272603e36cc19fd8"
            ],
            "threshold": 1
          },
          "timestamp": {
            "keyids": [
              "f7a6872f297634219a80141caa2ec9ae8802098b07b67963272603e36cc19fd8"
            ],
            "threshold": 1
          }
        },
        "spec_version": "1.0.30",
        "version": 2
      }
    }
  }

I imagine this endpoint will return failure when:

there is no SIGNING_ROLE config variable set for the given metadata role

Also, I imagine that if a user calls POST /api/v1/bootstrap when there is an existing DAS process for bootstrap (BOOTSTRAP has a value of signing-<task id>) then the POST /api/v1/bootstrap endpoint will return failure.
The user must be allowed to override the existing DAS process only through this new PATCH /api/v1/metadata/sign endpoint.
Finally, I imagine that there will be a new endpoint defined called update_metadata.
References
https://github.com/repository-service-tuf/repository-service-tuf/issues/327#issuecomment-1560574181
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Also, I imagine that if a user calls POST /api/v1/bootstrap when there is an existing DAS process for bootstrap (BOOTSTRAP has a value of signing-<task id>) then the POST /api/v1/bootstrap endpoint will return failure. The user must be allowed to override the existing DAS process only through this new PATCH /api/v1/metadata/sign endpoint.

I noticed that it was missing this protection, so I filed another issue for it and updated the umbrella

[ ] https://github.com/repository-service-tuf/repository-service-tuf-api/issues/417

Finally, I imagine that there will be a new endpoint defined called update_metadata.

I didn't get the functionality of this. To update what?
If there is so, why an endpoint update_metadata if we have the /api/v1/metadata and we can have the PUT method to /api/v1/metadata`?
The POST /api/v1/metadata intends to submit a new version of the metadata resource. What would be the PUT /api/v1/metadata?

Yesterday, there was a discussion about the PATCH /api/v1/metadata and PATCH /api/v1/bootstrap, which I don't agree and I leave here my views (tl;dr) why.
From my experience, using the PATCH /api/v1/metadata and PATCH /api/v1/bootstrap we will be using methods that are specific for existing metadata and bootstrap resources. If in the future there is a use case for those methods will bring us to create parameters in the request or create a new version in the endpoint.
Another thing is about, how I cancel/delete a sign. The PATCH solves when I want to redo it. But what if I want to stop it? I think we will still need a DELETE /api/v1/metadata/sign. We could use PATCH /api/v1/metadata/sign with empty metadata but doesn't sound ideal IMO.

we will still need a DELETE /api/v1/metadata/sign.

I suggest we start with DELETE  before we implement PATCH. PATCH would then only be a shortcut for
DELETE .../SIGN + POST .../[BOOTSTRAP | METADATA], which is nice to have but not immediately necessary.
IIRC, the feature request started with DELETE and we only came up with PATCH, because we wanted to authenticate
the request with a metadata signature, to not only rely on the API auth token.
The ideas we had were all not that useful:

send along a signature over the pending metadata  (existing signatures can easily be replayed)
require the signature from a key that has not yet signed (unnecessarily limits the keys)

With PATCH we assumed that the new metadata will have changed and the included signature(s) could not be replayed. Something, we'd actually need to check. Should we fail if the new metadata has not changed?
IMO this all sounds hacky. If we want to authenticate the request using tuf keys, and can't reliably use signatures over metadata, we should maybe use some standard public key authentication method (e.g. rfc4252).
I still think the additional authentication is not necessary. As we said, at worst an attacker, who has compromised the API token, can DOS the signing event, which should be easily and quickly detectable. The important thing is that they cannot issue new trusted metadata. Which they can't without additionally compromising a quorum of tuf keys.
TLDR: I suggest to only add DELETE /api/v1/metadata/sign for now, and to do so without additional authentication besides API token.

With PATCH we assumed that the new metadata will have changed and the included signature(s) could not be replayed. Something, we'd actually need to check. Should we fail if the new metadata has not changed?

I think that's reasonable and can easily be checked. We added __eq__ method to all python-tuf API classes.
I find it logical to fail with a message that Metadata cannot be patched - new metadata same as the old one or something like that.

IMO this all sounds hacky. If we want to authenticate the request using tuf keys, and can't reliably use signatures over metadata, we should maybe use some standard public key authentication method (e.g. rfc4252).

As I understand from rfc4252 the idea is that we have a public word/bytes that should be signed and we can verify that the signature is coming from the private key we expect?
If that's the case this seems reasonable to me.

TLDR: I suggest to only add DELETE /api/v1/metadata/sign for now, and to do so without additional authentication besides API token.

I agree it sounds more important to have a delete option before having a PATCH one as you want to have a way to stop a DAS process at all even if you are not sure what will be the new metadata.
Do you think we can try the above suggestion and implement an authentication mechanism by requiring signing with a private key of a public word and then verifying this signature?

Do you think we can try the above suggestion and implement an authentication mechanism by requiring signing with a private key of a public word and then verifying this signature?

I think it adds unnecessary complexity. The attacker can't really get anything out of DOSing the signing event. It will be immediately detected by the other signers, which can then revoke the API token.

Okay, will implement first the DELETE /api/v1/metadata/sign endpoint, and then this one can be implemented as well.

DELETE /api/v1/metadata/sign endpoint is implemented and together with the community, we agreed that this feature is not needed for now.


misleading issue reference

https://github.com/Moosems/pyeditorconfig/blob/982054b20794f2fe2e4e4fa591c72e9877cb3739/pyeditorconfig/pyeditorconfig.py#L110
This is trying to reference issue number 444 in Porcupine, not in this repository.

More documentation


Issue with support-for?

Hey!
Is the support-for file missing in bower_components/normalize-scss/fork-versions/default ?
It's imported in the _normalize.scss file but isn't in the parent directory?
Thanks!

Hmm I'm having issues with this too.

Checking https://github.com/JohnAlbin/normalize-scss/issues/43 for a resolution

@martindavies Pushed a fix. Hopefully this fixes it https://github.com/leemunroe/motherplate/blob/cf302b7d92b0d68308b4c52d64b661b7962ec878/css/scss/main.scss#L2

@martindavies Did that fix things?


Update LD Crypto Suite Registry PR

https://github.com/w3c-ccg/ld-cryptosuite-registry/pull/25

New PR opened https://github.com/w3c-ccg/ld-cryptosuite-registry/pull/31. Will leave this issue open until it is accepted


Socket communication

Before I get to actually doing socket communication, there is some work that needs to be done first. First, and most importantly, we were inferring that an auction's slug would give us access to causality, which is not the case. After talking with @acjay, causality IDs are permanent, while slugs can – and do – change.
The solution I'm proposing is, instead of just fetching the required sale ID before loading the rest of the live auctions view controllers, let's move the fetching of the entire static data (the metaphysics query) up front. The nice things, because GraphQL is awesome, we can fetch anything we need upfront as well: sale info, sale artworks, and eventually the JWT we'll need to authenticate the websocket connection.
This simplifies a lot of other things that used to rely on the the static data coming eventually, but can now rely on it immediately. It removes a lot of optionality and excess properties from the sales person, too. @orta I'm keen to know what you think of these changes in particular.
Still left to do:

[x] Remove socket.io
[x] Add basic socket connection
[ ] Amend state reconciler class to handle new socket data format
[x] Simulate static data loaded from JSON file (for offline UI development)
[x] Simulate events from websockets from JSON file (for offline UI development)
[x] Update tests

Replaces #1393.

1 Error

:no_entry_sign:
No CHANGELOG changes made

2 Warnings

:warning:
PR is classed as Work in Progress

:warning:
Needs testing on a Phone if change is non-trivial

  Generated by :no_entry_sign: danger

Don't have time for an extensive review probably till next week, on a cursory glance, this looks 👍 - lots of deletions and the Sales Person being more simple is great

No problem, this PR is pretty ambitious, probably best to wait until it's more done to get a good picture.
Quick update: I've got stubbed metaphysics working, started on stubbing socket events (which I've started working on, just the initial lot state broadcast so far).

Still a long ways to go, but I'm feeling like we're making progress.

Should be 🍏 now. I've marked some of the tests relating to socket communication as pending, as that code still needs to be re/written. I'll leave this up to @orta to merge or not, and I'll pick this up again on Monday regardless.

Feels super nice 👍- great work here

Thanks! Today I'll clean it up and add some of the pending tests back in (and fix their related code).

Okay, got this wrapped up. Next steps will be updating individual bits based on different events, but that can be another PR. We need to look for any places that are using hard-coded values that we had for testing the UI, but need to be replaced with actual values now – hopefully there's nothing in the UI we're not already parsing. I could you some help on this one if you have time, Orta.
@orta your tests were very helpful making sure I had corner-cases of JSON parsing covered :100: I like how this is shaping up.

OK, let's do this 👍


Online icon not always showing correct status

After running /net/enable, and then subsequently loading  /client/index.html, the incorrect icon indicator will be shown (cloud with a line through it), as confirmed by going to /net/status without clicking on the internet access icon.

Clicking the internet icon On, and then Off again does correctly reset the status (of course)

We need the icon to be driven by a poll of the back end. That didn't work the last time we tried, I think because our multiple layers of anonymous functions defeated the React transpiler. I'll try again.

@RUN-Projects I eventually found the root of the "not updating from a useEffect" problem we hit before. Briefly, and in my words, React tries to do, at compile time, things that Javascript should do at run time, and this is a leaky abstraction, notably when you embed a state getter (which looks like a variable but isn't) in an anonymous function. See https://medium.com/geographit/accessing-react-state-in-event-listeners-with-usestate-and-useref-hooks-8cceee73c559 . The solution is useRef.

PR #25 should fix this.


[tiff] build failure when not found liblzma::liblzma

Operating system
Windows
Compiler
MSVC
Steps to reproduce the behavior
`.\vcpkg.exe install tiff`

Failure logs
Computing installation plan...
The following packages will be built and installed:
tiff[core,jpeg,lzma,zip]:x64-windows -> 4.6.0#1
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\goree\AppData\Local\vcpkg\archives in 1.75 ms. Use --debug to see more details.
Installing 1/1 tiff:x64-windows...
Building tiff[core,jpeg,lzma,zip]:x64-windows...
-- Using cached libtiff-libtiff-v4.6.0.tar.gz.
-- Cleaning sources at C:/Develop/vcpkg/buildtrees/tiff/src/v4.6.0-ba2cf5b685.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Develop/vcpkg/downloads/libtiff-libtiff-v4.6.0.tar.gz
-- Applying patch FindCMath.patch
-- Using source at C:/Develop/vcpkg/buildtrees/tiff/src/v4.6.0-ba2cf5b685.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
Working Directory: C:/Develop/vcpkg/buildtrees/tiff/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
C:\Develop\vcpkg\buildtrees\tiff\config-x64-windows-dbg-CMakeCache.txt.log
C:\Develop\vcpkg\buildtrees\tiff\config-x64-windows-rel-CMakeCache.txt.log
C:\Develop\vcpkg\buildtrees\tiff\config-x64-windows-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:252 (vcpkg_execute_required_process)
ports/tiff/portfile.cmake:28 (vcpkg_cmake_configure)
scripts/ports.cmake:170 (include)
Additional context
In the file  .\buildtrees\tiff\config-x64-windows-out.log
CMake Error at libtiff/CMakeLists.txt:157 (target_link_libraries):
  Target "tiff" links to:

    liblzma::liblzma

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

I see that Liblzma port was build successfully.
It even installed the file .\installed\x64-windows\share\liblzma\LibLZMAConfig.cmake  that declares liblzma::liblzma presence.
But tiff port does not use it. It can find liblzma without namespace. But with namespace (liblzma::liblzma) it doesn't work.

@Goreek Could you please run command ./vcpkg remove tiff:x64-windows --recurseand try again?


List DSSE maintainers

Addresses #57
The list of maintainers needs to be iterated on / confirmed by everyone. I've currently listed the folks everyone from https://github.com/secure-systems-lab/dsse/issues/57#issuecomment-1563377650.

Looks like I missed @lukpueh, who also has powers, in https://github.com/secure-systems-lab/dsse/issues/57#issuecomment-1563377650.


Decomposer doesn't create gradle task

Hello, I'm trying to use your plugin"Decomposer", but I have some troubles. I modified my settings.gradle file like your example in Readme. And my settings.gradle now is:
pluginManagement {
     repositories {
        google()
        mavenCentral()
        gradlePluginPortal()
       maven(url = "https://jitpack.io")
       }

     resolutionStrategy {
         eachPlugin {
        if(requested.id.toString() == "com.github.takahirom.decomposer"){
        useModule("com.github.takahirom:decomposer:main-SNAPSHOT")}
        }
     }
    plugins {
      id ("com.android.library")
      id ("kotlin-android")
      id ("com.github.takahirom.decomposer")
     }
}

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
      repositories {
        google()
        mavenCentral()
       }
}

rootProject.name = "My Application2"
include(":app")

But task ":uicomponent-compose:compileDebugKotlin" does not exist in my tasks list after sync. And also when i tried to run this task in command line, the was exception: "Task not found"

Thank you for trying this plugin.
You might have to use id ("com.github.takahirom.decomposer") in your app module. It is because I'm not sure what happens when you use plugins in pluginManagement.


Drop ember-popper in favor of ember-popper-modifier and popper.js v2

ember-popper wasn't really maintained much, and ember-popper-modifier seems like the more robust and modern solution. Also it uses popper.js v2, which is also the version that original Bootstrap 5 uses.
Note that due to the fact that Bootstrap 4 uses popper.js v1 (in its original JS components, that we don't use of course), some of the markup (margins of arrows) are working well with popper.js v2 (which ignores these margins), so this required some not so beautiful workarounds (CSS overrides).
Hopefully this should now also maker Ember 4 tests pass, which failed due to some outdated dependency of ember-popper...

@simonihmig Do you need us to test this PR? Or do you have anything to commit before we do so?
Our large codebase is now on<EMAIL_ADDRESS>and things seem to be working fine. We noticed that BS5 dropdown-menu-end is not working as expected, though (from BS5 docs):

Heads up! Dropdowns are positioned thanks to Popper except when they are contained in a navbar.

Do you need us to test this PR? Or do you have anything to commit before we do so?

@vst thanks for chiming in! Testing would be awesome for sure. I think I can merge this and publish a new beta version by the end of the week!

We noticed that BS5 dropdown-menu-end is not working as expected, though (from BS5 docs):

Could you please file an issue, with some more details?
@jelhan I am going to merge this now, as this makes CI green again finally. If you still want to review later - after your vacation IIRC or whenever you have time - the n please do so, I can still address feedback in a later iteration!

We noticed that BS5 dropdown-menu-end is not working as expected, though (from BS5 docs):

Could you please file an issue, with some more details?

@simonihmig Just testing 5.0.0-beta.0. It seems that this has been fixed automatically :+1:


Failing case that effects ember-test-helpers

This is an example of a failing case in the loader.  The compiled output of ember-test-helpers looks like the following. https://gist.github.com/chadhietala/14a0ee7ecdb90e697bbc.  Ember-test-helpers creates a non-named AMD build which might resolve this issue.

the output of that project is invalid, we must fix that project.

mind opening issues their, and maybe working on making it use an updated transpiler that normalizes relative correctly

Yup can do. Just wanted to show the failing example.

@chadhietala absolutely, now that i think about it. Lets ensure the loader handles this in the current way. So if we adjust the tests to pass, we should merge them in.

when the test is updated, feel free to merge. Thanks dude!

:+1:


Hypothesis tests for roundtrip to & from pandas

Part of #1846: test roundtripping between xarray DataArray & Dataset and pandas Series & DataFrame.
I haven't particularly tried to hunt down corner cases (e.g. dataframes with 0 columns), in favour of adding tests that currently pass. But these tests probably form a useful platform if you do want to ensure corner cases like that behave nicely - just modify the limits and see what fails.

This looks great! I'll let someone who knows hypothesis better do a full review. Thanks for submitting @takluyver !

As in my other PR, one suggested addition causes a test failure, and I've put that in the last commit.

Hello @takluyver! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file properties/test_pandas_roundtrip.py:

Line 39:13: E131 continuation line unaligned for hanging indent

This seems so close—could we fix the test (maybe that's just a merging of master?) and merge?

This seems so close—could we fix the test (maybe that's just a merging of master?) and merge?

Merged master, crossing fingers that fixes it.

Nope. I don't understand the error, though it looks like astropy has had something similar: https://github.com/astropy/astropy/issues/6424
Also black is now failing on a number of files not affected here.

OK, looks like the test failure now is real. Let me know if you want me to comment out the relevant line so the tests pass.

You're right @takluyver
It looks like hypothesis tests are running in the normal test suites. Anyone know offhand why that is? e.g. https://dev.azure.com/xarray/xarray/_build/results?buildId=1284
(that doesn't solve the test failure, though)

OK, looks like the test failure now is real. Let me know if you want me to comment out the relevant line so the tests pass.

If we want to merge a subset of the tests then that's fine. Ofc even better if we can use these tests to find & fix the errors

OK, looks like the test failure now is real. Let me know if you want me to comment out the relevant line so the tests pass.

If we want to merge a subset of the tests then that's fine. Ofc even better if we can use these tests to find & fix the errors

In my experience it's better to open an issue, add an xfail decorator to the test, and merge the tests PR.  Otherwise the initial PR can take a very long time and no other property-based tests get added.
It's also likely that the person who found the bug is not the best person to fix it, and requiring that they do so in order to merge a useful test just disincentives testing!

In my experience it's better to open an issue, add an xfail decorator to the test, and merge the tests PR. Otherwise the initial PR can take a very long time and no other property-based tests get added.

+1 let's do that!

OK, I've xfailed it.


feat: add search redirect at api package 2.x

What's the purpose of this pull request?
This PR adds a query to solve redirects when performing a search.
In case of VTEX platform, this is solved by the IS api.
How it works?
When performing a search if a term or facet has a redirect, the value of the redirect field should be an URL; this can later be used to redirect the user to an internal or external URL.
From VTEX admin:

It get solved as:

How to test it?

Run the @faststore/api package individually.
Browse localhost/graphql
Run the redirect query with a term that is active in /admin/search/v4/redirects/
For storeframework, you can use the term tech

We have two types of redirect available (term / facet) or a mix of both:
term

facet

term + facet

https://user-images.githubusercontent.com/67066494/236871114-125a3ba9-5b97-4f02-9a1f-e35c2f77dcae.mp4

TO DO: Add a redirect behaviour at the server side for slug pages


add failing test and fix for #91

only looks on a,link, and area for rel attributes, since these are the only elements that HTML allows to have the rel attribute.

From IRC:
@aaronpk BOT [2:39 PM]
I only have tiny internet right now so can't comment on my PR, so can someone add this as a comment? Don't merge my php-mf2 PR yet because I just realized it's wrong and I'm going to add another test case to webmention.rocks tomorrow, and I have a plan to fix the PR

It appears XPath does not have the problem @tantek and I suspected after all. We were assuming that since the query used an "or" expression at the top level, which XPath treats as a "union", that it would return the tags in the order they were in the query. However I've added tests and it looks like XPath is still returning the tags in document order. This is fine to merge now!

Had brief discussion at IWC Nürnberg with @tantek @aaronpk about whether to future proofing or HTML spec compliance is higher priority, decided that HTML spec compliance takes priority. Thanks for your work on this @aaronpk!


Cow: Blacklist authorsbreeze.com

Cow requests the blacklist of the website authorsbreeze\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

authorsbreeze\.com has been seen in 5 true positives, 0 false positives, and 0 NAAs.


Proposal to export the builded request

After finally excecuting a request and checking is good, it would be nice to export that request in different formats, like httpie, curl or raw, in order to share it with others or for documentation.

For now, you can export HTTPie command using the httpie command:
> httpie post
http POST http://localhost

cURL is on the roadmap. I also consider adding raw format.


add schema to FK constraint

Depends on https://github.com/eclipse/dirigible/pull/1152
resolve: https://github.com/SAP/xsk/issues/533

Eclipse Dirigible version 5.12.20 was released.


fix(css): page reload was not happening with .css?raw

Description
fixes #16396

/ecosystem-ci run

I reran nuxt but it failed again. It seems this PR does affect nuxt and astro. 🤔

@bluwy Would you take a look why this breaks astro?

I sent a PR to Astro to fix this. It was incorrectly crawling into the dependencies to find CSS to inline. Skipping it fixes it.

Thanks :pray:

/ecosystem-ci run


Theme: Virtualmin selecting multiple domains for backups

Hi, I think I may have a bug for you:
When using [Ctrl][Click] to select more than one virtual domain to backup, the select box behaves more as if one is using [Shift][Click] - all the rows between the two wanted, are selected as well.
I am using Chrome Version 50.0.2661.86 (64-bit) on Fedora release 22.
Just checked Firefox, that works perfectly.

I'm afraid I can't reproduce it in Chrome 51, with both old (17.84) and new 18.00b (working on it now).
Please have a look. First I used Ctrl, than Shift:
http://rostovtsev.ru/pub/src/authentic/18.00b/vm_backup_selection_455.webm
Try in incognito mode, maybe some Extensions doing it?

Hi Illa,
Sorry to not get back to you sooner. I have the same behaviour in incognito
mode.
I have attached a bad screen recording.
Best regards,
William Nettmann
Cell:<PHONE_NUMBER>
[image: Facebook] https://www.facebook.com/NettSite [image: Twitter]
https://twitter.com/NettSiteCoZa [image: Google+]
https://plus.google.com/+NettsiteCoZa [image: LinkedIn]
http://www.linkedin.com/company/1082367?trk=tyah&trkInfo=tas%3Anettsite%2Cidx%3A1-1-1
On 30 April 2016 at 20:04, Ilia Rostovtsev<EMAIL_ADDRESS>wrote:

I'm afraid I can't reproduce it in Chrome 51, with both old (17.84) and
new 18.00b (working on it now).
Please have a look. First I used Ctrl, than Shift:
http://rostovtsev.ru/pub/src/authentic/18.00b/vm_backup_selection_455.webm
Try in incognito mode, maybe some Extensions doing it?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/qooob/authentic-theme/issues/455#issuecomment-215984210

Where is screen recording? :)

I attached it to the email - it was 1.1mb, maybe it got blocked somewhere.
Best regards,
William Nettmann
Cell:<PHONE_NUMBER>
[image: Facebook] https://www.facebook.com/NettSite [image: Twitter]
https://twitter.com/NettSiteCoZa [image: Google+]
https://plus.google.com/+NettsiteCoZa [image: LinkedIn]
http://www.linkedin.com/company/1082367?trk=tyah&trkInfo=tas%3Anettsite%2Cidx%3A1-1-1
On 4 May 2016 at 19:41, Ilia Rostovtsev<EMAIL_ADDRESS>wrote:

Where is screen recording? :)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/qooob/authentic-theme/issues/455#issuecomment-216944062

Could you upload it to, let's say, Google Drive and share the public link, please?

Hi,
See
https://drive.google.com/file/d/0B8CHG1dmi4xjX21XTXdHZ1VGb3pnNmpQOFoxTjh5U0xIS29N/view?usp=sharing
Basically, I click on "Select Data", and then [Ctrl] click on "Drop
Tables".  Everything up to "Create Tables" is selected.
The theme is 17.84
Chrome is Version 50.0.2661.94 (64-bit) on Fedora 23
Best regards,
William Nettmann
Cell:<PHONE_NUMBER>
[image: Facebook] https://www.facebook.com/NettSite [image: Twitter]
https://twitter.com/NettSiteCoZa [image: Google+]
https://plus.google.com/+NettsiteCoZa [image: LinkedIn]
http://www.linkedin.com/company/1082367?trk=tyah&trkInfo=tas%3Anettsite%2Cidx%3A1-1-1
On 4 May 2016 at 19:52, Ilia Rostovtsev<EMAIL_ADDRESS>wrote:

Could you upload it to, let's say, Google Drive and share the public link,
please?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/qooob/authentic-theme/issues/455#issuecomment-216947052

I'll take a look in the morning. Thanks.

I can't reproduce it. Let's expect that version 18.00 will fix it. It has huge number of changes. A lot of things are going to work differently.
I case it's not fixed after update (when it's out), please feel free to reopen this issue.

Expect this to be fixed in 18.00


NPE Safety

Add the same level of NPE safety to the newest option as the others have.

I raise you


Tantivy requires Rust 1.62 or later.

Tantivy needs the total_cmp feature to compile, which was stabilized in Rust 1.62.

Since the days when 1.27 was supported, these things have requirements beyond that:

1.37 - adding the edition keyword in the Cargo.toml
1.56 - adding support for the 2021 edition.
1.59 - this is the MSRV of the time crate.
1.60 - this is the MSRV of the oneshot crate.
1.62 - the total_cmp feature was stabilized. This is used as of 1bd44a5f6182f80b9211018ce651ceef656b6aeb.


Add readOnly option #262

What is the difference between readOnly and enabled right now they look the same to me. And if you don't want to to enable terminal on click then you can freeze the terminal.

Sure ! I have remove this option and fix the frozen mode


Multi-harmonic josephson element

Dear all,
We work with multi-harmonic Josephson element, see https://arxiv.org/abs/2405.14695 for instance.
One way of describing them is to replace the usual
$$E_\mathrm{J} = I_\mathrm{c} \cos \left( \varphi \right)$$
By
$$E_\mathrm{J} = I_\mathrm{c1} \cos \left( \varphi\right) + I_\mathrm{c2} \cos \left( 2 \varphi\right) + I_\mathrm{c3} \cos \left( 3 \varphi\right) + ... $$
I have no idea how to add such functionality in scqubit which has a quite complicated code for me ^^' .
Could you guide to realize such improvement?
Thanks!

We did think about such a possibility, and we added this functionality a while back, though this is not documented as we weren't sure as to how many would be interested in it. In the Circuit module, you can define higher order Josephson junctions in the following way:
import scqubits as scq
circ_input = """
branches:
- [JJ2, 0, 1, 20, 2, 3]
- [L, 0, 1, 0.4]
"""
circ = scq.Circuit(circ_input, from_file=False)
circ

$$
H = 12.0 Q_{1}^{2} + \left(0.2 (2πΦ_{1})^{2} + 0.2 θ_{1}^{2} - 3.0 \cos{\left(2.0 θ_{1} \right)} - 20.0 \cos{\left(θ_{1} \right)} + 0.4 (2πΦ_{1}) θ_{1}\right)
$$
For defining the order the format is - [JJ<order>, node_1, node_2, EJ_1, EJ_2, ..., EJ_{order}, ECJ], following the syntax as usual to define a branch. The rest of the functionality should work as expected. Please let us know if you will experience any bugs.

Great! thanks a lot!

thanks @saipavanc
We might consider adding this to the docs... as it seems like there is interest.

Hello again,
I came across an error using the t1_effective method.
Indeed when using this code
zp_yaml ="""
# inductive transmon
branches:
- ["JJ", 0, 1, EJ1=7.4nA, ECJ1=40fF]
- ["L", 1, 2, El=300.4nH]
- ["JJ", 0, 2, EJ2=7.401nA, ECJ2=40.01fF]
"""
ti2 = scq.Circuit(zp_yaml, from_file=False, ext_basis="discretized", generate_noise_methods=True)
ti2.cutoff_n_1 = 10
ti2.ng1 = 0.5

ti2.t1_effective()

I got
72695.0438727016

But when using
zp_yaml ="""
# asymetric inductive transmon
branches:
- ["L", 0, 1, El1=250.4nH]
- ["JJ", 1, 2, EJ1=7.4nA, ECJ1=40fF]
- ["L", 2, 3, El2=250.4nH]
- ["JJ", 3, 4, EJ2=7.401nA, ECJ2=40.01fF]
- ["L", 4, 0, El3=250.4nH]
"""
ti3 = scq.Circuit(zp_yaml, from_file=False, ext_basis="discretized", generate_noise_methods=True)
ti3.cutoff_n_1 = 10
ti3.ng1 = 0.5
ti3.t1_effective()

I got
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[22], [line 1](vscode-notebook-cell:?execution_count=22&line=1)
----> [1](vscode-notebook-cell:?execution_count=22&line=1) ti3.t1_effective()

File c:\Users\ed261978\Anaconda3\envs\python311\Lib\site-packages\scqubits\core\noise.py:952, in NoisySystem.t1_effective(self, noise_channels, common_noise_options, esys, get_rate, **kwargs)
    [948](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:948)             max_level = max(max_level, opts.get("i", 1), opts.get("j", 1))
    [950](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:950)     esys = self.eigensys(evals_count=max_level + 1)  # type: ignore
--> [952](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:952) rate = self._effective_rate(
    [953](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:953)     noise_channels=noise_channels,
    [954](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:954)     common_noise_options=common_noise_options,
    [955](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:955)     esys=esys,
    [956](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:956)     noise_type="t1",
    [957](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:957) )
    [958](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:958) if get_rate:
    [959](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:959)     return rate

File c:\Users\ed261978\Anaconda3\envs\python311\Lib\site-packages\scqubits\core\noise.py:821, in NoisySystem._effective_rate(self, noise_channels, common_noise_options, esys, noise_type)
    [818](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:818)     options["get_rate"] = True
    [820](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:820)     # calculate the noise over the full param span in param_vals
--> [821](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:821)     rate += scale_factor * getattr(self, noise_channel_method)(
    [822](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:822)         esys=esys, **options
    [823](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:823)     )
    [825](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:825) # noise_channel is a tuple representing the noise method and default options
    [826](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/noise.py:826) elif isinstance(noise_channel, tuple):
...
   [2120](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/circuit_routines.py:2120)     )
   [2122](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/circuit_routines.py:2122) var_index = get_trailing_number(operator_name)
   [2123](file:///C:/Users/ed261978/Anaconda3/envs/python311/Lib/site-packages/scqubits/core/circuit_routines.py:2123) assert var_index

AttributeError: 'Circuit' object has no attribute 'θ4_operator'

Any idea

Continued discussion in #231. Closing this issue.


Spanish es language

Changes:

Added spanish ES language.

Considerations:
Would be great to load all files without need to implement on index.js

Thank you for this translation!
I updated the keys to make the system more consistent. Can you update your branch with the new keys?

@luanfreitasdev Done. Check it please. 😄


No error on assignment to non-nullable variable with strictNullChecks turned on.

TypeScript Version:  2.9 and 3.x
Search Terms:
strictNullChecks, no error, undefined
Code
function thing<T extends boolean | string | number>(v: T): T {
  var c: T | undefined = v;
  var d: T = c; // This should not be allowed under strictNullChecks
  return d;
}

Expected behavior:
The assignment to d should be an error since c may be undefined.
Actual behavior:
The compiler removes the | undefined from c at the point of assignment to d.
Playground Link:
https://www.typescriptlang.org/play/index.html#src=function thing<T extends boolean | string | number>(v%3A T)%3A T {
  var c%3A T | undefined %3D v%3B
  var d%3A T %3D c%3B %2F%2F This should not be allowed under strictNullChecks
  return d%3B
}

The compiler knows that v is of type T, so it can not be undefined. If you change the c assign to Math.random() < 0.5 ? v : undefined; then errors as you expect.
Full sample (playground):
function thing<T extends boolean | string | number>(v: T): T {
  var c: T | undefined = v;
  var d: T = c; // This should not be allowed under strictNullChecks

  var a: T | undefined = Math.random() < 0.5 ? v : undefined;
  var b: T = a;

  return d;
}

Error at b:
Type 'T | undefined' is not assignable to type 'T'.
  Type 'undefined' is not assignable to type 'T'.

So, this was a simplified example of a more complicated problem which exhibited the same behavior. I'll post the full situation.

Here's a more complicated example which demonstrates the same behavior, but where the compiler can't infer that undefined is not present.
interface IIterator<T> {
  next(): T | undefined;
}

function map<T, U>(it: IIterator<T>, fn: (value: T) => U): IIterator<U> {
  throw ''; // the implementation is unimportant
}

type Primitive = number | string | boolean;

interface IItem<T extends Primitive> {
  value: T | undefined;
}

function unbox<T extends Primitive>(items: IIterator<IItem<T>>): IIterator<T> {
  let it = map(items, item => item.value); // VSCode shows this type to be IIterator<T | undefined>;
  return it; // This is allowed, but IIterator<T> should not be assignable to IIterator<T | undefined>
}

The proper thing would be to add a constraint: IIterator<T extends object | Primitive> {


Crash: LCircle Component

Description
I can't use the component LCircle because there are a crash (error in browser console) all the time.
I'm using exactly the same code which is in the this repository Vue2Leaflet
Code Example
Someone know what can be the problem ? Because this code is really simple.
Thank you
My code:
...
<l-circle :lat-lng="circle.center" :radius="circle.radius"/>
...
data() {
   return {
      circle: {
        center: L.latLng(47.413220, -1.0482),
        radius: 4500
      },
   }
},
...

Error - Firefox Developer Edition:
[Vue warn]: Error in mounted hook: "TypeError: max2 is undefined"

found in

---> <LCircle>
       <LMap>
         <Map> at src/components/map/Map.vue
           <App> at src/App.vue
             <Root>
TypeError: "max2 is undefined"

    intersects leaflet-src.js:1053 _empty leaflet-src.js:7951 _updateCircle leaflet-src.js:12627 _updatePath leaflet-src.js:7947 _update leaflet-src.js:7942 _reset leaflet-src.js:7858 onAdd leaflet-src.js:7806 _layerAdd leaflet-src.js:6583 whenReady leaflet-src.js:4367 addLayer leaflet-src.js:6549 addLayer vue2-leaflet.min.js:1 mounted vue2-leaflet.min.js:1 callHook11VueJS

Error - Google Chrome:
[Vue warn]: Error in mounted hook: "TypeError: Cannot read property 'x' of undefined"

found in

---> <LCircle>
       <LMap>
         <Map> at src/components/map/Map.vue
           <App> at src/App.vue
             <Root>

vue.esm.js?efeb:1841 TypeError: Cannot read property 'x' of undefined
    at Bounds.intersects (leaflet-src.js?7737:1053)
    at NewClass._empty (leaflet-src.js?9eb7:7951)
    at NewClass._updateCircle (leaflet-src.js?7737:12627)
    at NewClass._updatePath (leaflet-src.js?9eb7:7947)
    at NewClass._update (leaflet-src.js?9eb7:7942)
    at NewClass._reset (leaflet-src.js?9eb7:7858)
    at NewClass.onAdd (leaflet-src.js?9eb7:7806)
    at NewClass._layerAdd (leaflet-src.js?9eb7:6583)
    at NewClass.whenReady (leaflet-src.js?7737:4367)
    at NewClass.addLayer (leaflet-src.js?7737:6549)

Browsers Affected

[x] Chrome
[x] Firefox
[ ] Edge
[ ] Safari 9
[ ] Safari 8
[ ] IE 11

Versions

Leaflet: v1.4.0
Vue: v2.5.22
Vue2Leaflet: v1.2.3

Yes, I have already tried that but still doesn't work.
So, for my case I have built somethings using LMarker with svg and size (depending on the meters per pixel). On zoom change, I update the size of the Radius marker.
This is the code:
<l-map ... @update:zoom="updatedZoom">
   <l-marker :lat-lng="newCenter" :icon="centerMarkFocus"/>
</l-map>
...
// https://wiki.openstreetmap.org/wiki/Slippy_map_tilenames#Resolution_and_Scale
const getMetresPerPixel = (lat, zoom) => (
  40075016.686 * Math.abs(Math.cos((lat * Math.PI) / 180))) / (2 ** (zoom + 8)
);
const radiusSizeFromMeters = (metersRadius, metersPerPixel) => (
  Math.round((metersRadius / metersPerPixel) * 2)
);
...
updatedZoom(zoom) {
   this.manageCenterMark(zoom, this.settings.meters, this.newCenter[0]);
},
manageCenterMark(zoom, metersRadius, latitude) {
   this.centerMarkFocus = new L.icon({
      iconUrl: svgCenterArea,
      iconSize: radiusSizeFromMeters(metersRadius, getMetresPerPixel(latitude, zoom)),
   });
},

@vomnes alternatively you can check the 2.0 beta that I just released on npm

@vomnes can we consider this closed does the beta version works for you ?

I didn't try the beta version, but I succeeded to reproduce the bug working on an other part of my project.
const markerRenderer = L.canvas({
   padding: .5,
});
let marker = L.circleMarker([lat, lng], {
   radius: 4,
   renderer: markerRenderer, // <----
   weight: 1,
   fillOpacity: 1,
   color: getNiceColor(),
});

Without the line renderer: markerRenderer, the TypeError: max2 is undefined occurs.
It may help someone else to fixe this error.

Closing due to inactivity, feel free to re-open


Update lifecycle page

There has been repeated confusion about Bitcoin Core's release versioning compared with SemVer 2.0.0.
While Bitcoin Core does indeed follow the spirit of SemVer regarding major and minor releases, where minor releases focus on bug fix maintenance; Bitcoin Core software releases are decoupled network versioning and consensus rule changes. As such, the exceptions need to be explained explicitly.

Looks like a good opportunity to update that 0.11 is no longer supported, and we can't really support more than the most recent.

Concept ACK fc88445

ping @harding

Opened a PR to @btcdrak's branch with a few nits and the following revised final section:

Relationship to SemVer

Bitcoin Core software versioning is similar to the SemVer optional versioning standard for regular feature releases.  However, SemVer was designed for use in normal software libraries where individuals can choose to upgrade the library at their own pace, or even stay behind if they don't like the changes.

Parts of Bitcoin, most notably the consensus rules, don't work that way.  In order for a new consensus rule to go into effect, it must be enforced by some number of miners, full nodes, or both; and once it has gone into effect, software that doesn't know about the new rule may generate or accept invalid transactions.

For this reason, Bitcoin Core deviates from SemVer for changes to consensus rules and other updates where network-wide adoption is necessary or desirable.  The deviation is slight: Bitcoin Core releases these changes as minor releases (x.y) instead of as major releases(x.0); this minimizes the size of the patch in order to make it easy for as many people as possible to inspect it, test it, and deploy it.  It also makes it possible to backport the same patch to multiple previous major releases, further increasing the number of users who can easily upgrade, although there are not always enough volunteers to manage this.

As always, please feel free to reject any changes you don't like.

ACK on @btcdrak's text and @harding's improvements

@btcdrak and I made some minor edits based on @luke-jr's feedback.  I think the version as of daa79da is probably good enough to put out there; we can revise it or expand it again in a few months if there is any further confusion that we notice on the forums or social media.

@harding OK let's publish. Thanks for your help!


It seems most control chars can't be typed.

I first noticed the problem when using Termux (a unix-ish shell environment) which has a telnet client in it.  It was impossible to type control-], which is how you get an escape from telnet.
A quick browse of the source code seems to imply that the ctrl highlight mode only works with a very few specific letters it was implemented for, and for all other keys the ctrl is ignored and it reverts to acting as if ctrl isn't on.

Same here; in my case, I couldn't use Ctrl+d to exit the Python interpreter in a Termux shell. I think this should be treated as a high-priority bug.

@Monsieur-Moony , termux lets you use volume-down (or the extra-keys button) in place of Ctrl, though I agree.

@Quasic Thanks, that's handy info 👍
Although not ideal, the extra-keys bar + codeboard is somewhat manageable for Termux.

Confirm. Key bindings for tmux don't work (with termux). Default key bindings for tmux are ctrl-b (default send-prefix) followed by command key ('c', 'd', 'n', 'p', etc.). Pressing 'Ctrl', 'b', 'c', has the effect of typing 'c'. If I use 'CTR' in termux's extra keys, ssh from a remote terminal, or use another keyboard then the key bindings work.  Enough of an issue that I no longer use CodeBoard.

If anyone can test the latest code, please let me know if the issue has re-opened.


Remove HOMEBREW_OSX_VERSION environment variable from Travis.

Changes to the core

[x] Followed hacking.md.

Since test are now run using brew cask-tests, HOMEBREW_OSX_VERSION should already be exported.

This pull request was merged in 9e49bb92f53321295d4380f87e09268a5ca263ba...b3af4340634218ac55f9c7c547e7c70ea68a5586.


Add Support For Database models.ImageField images stored in /media

In my project, I want to be able to webp images inside /media because Facebook Opengraph and Twitter cards metadata requires filetypes that are not webp. I want my website output to show the webp images while Facebook and Twitter are given the jpeg/png images when not including the webp tag.
BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(file)))
MEDIA_URL = '/media/'
MEDIA_ROOT = os.path.join(BASE_DIR, 'media')
thumbnail = models.ImageField(blank=True, null=True, max_length=255)
Do something like:

Hello @9mido, this the object.thumbnail.url is an external url (not a path to a file in the system) right ? if yes, this lib doesn't work requesting an external source, converting, and serving it. We would need to implement this behaviour

@andrefarzat  It seems Twitter cards and Facebook Opengraph allow .webp files. So I probably do not need to use this feature at all.
Ah I see what you mean. Yes the object.thumbnail.url would output to <IP_ADDRESS>:8000/media/test.webp.

@9mido exactly. It outputs the url to the file, not the path. Therefore it would be possible to try to figure out where the image is (using the settings.MEDIA_URL and settings.MEDIA_ROOT), but this method isn't error prone.
I will publish a version 2.0.0 with python 3 and django 3 support soon


[PHPStanRules] Skip $this passed exact type on NarrowPublicClassMethodParamTypeByCallerTypeRule

[x] Skip $this passed exact type on NarrowPublicClassMethodParamTypeByCallerTypeRule
[x] Handle $this passed from Interface on NarrowPublicClassMethodParamTypeByCallerTypeRule

Fixed 🎉

All checks have passed 🎉 @TomasVotruba it is ready for review.

I added fixture for both skipped and display message handling, the fix is by use ObjectType when $argType is ThisType https://github.com/symplify/symplify/pull/4223/files#diff-38ed39faf3a6e3a0c1b54af67bc268129c2f31937f9a051f2015dcdfc07a6aa2

[x] Skip $this passed exact type on NarrowPublicClassMethodParamTypeByCallerTypeRule
[x] Handle $this passed from Interface on NarrowPublicClassMethodParamTypeByCallerTypeRule

All checks have passed 🎉 @TomasVotruba I think it is ready.

Awesome, I've noticed this is magic bugs. Great job 👍


wpewebkit: Update 2.30.4 -> 2.30.5

This is a bug fix release in the stable 2.30 series.
Signed-off-by: Fabio Berton<EMAIL_ADDRESS>

For the record: Release announcement.

@fbertux thanks for the contribution.


Create transformer.h

Add transformer definition for Dlib

Thank you for the PR, however, it looks that some stuff is missing in dlib to be able to make it work. I will review it again and merge it once the transformer stuff makes it into dlib.
In particular, multm_prev3 and multm_prev4 are missing.

Yes, that's the case, but it's to anticipate a bit... I've made the latest changes to the multm_prev_ layer in line with Davis's comments, but it's still not integrated. I'm waiting for this part to be taken into account before modifying the softmax part (I'm still having unexplained sync problems with my environment).


hideous

There are a lot of existentials. Should I make all of them pure functions?

I will review this when all the errors in the CI are fixed.

In the future, please name your PRs properly and professionally and provide a description of the PR, even if it short. In the future, when we have to navigate the history of PRs, this is necessary to maintain our sanity.

Can be merged after the tests go through


Search effectiveness on multiple headings

The match-query.js script used by VuePress does not pick up the second occurrence of a filter term when it appears in both the H1 and lower headings (H2, H3, e.t.c). If the term is in multiple headings other than H1, it will find both.

PR: https://github.com/api3dao/api3-docs/pull/939


P1 is not plotted correctly?

Describe the bug
It seems that the spatial distribution plot does not show P1 correctly. (not very well tested, though)
To Reproduce

Select an input list containing priority=1
Simulate pointings
Click P1 label in the bottom plot
See whether P1 gets dim or not

maybe not correct, but let me keep it for recording purposes. will need more investigation.


Fix itest re new behaviors introduced by blockbeat

This is the branch that will be merged to master once the following PRs are merged,

#9306
#9307
#9260

This series fix all the itest flakes to make sure the blockbeat works as expected. Check #9306 for more context, and #9260 for the final results and improvements.
Depends on

#9315

linter failed due to "no space left"


Add issue template for weave scope github repo

Issue template will help both users and maintainers to exchange required info related to an issue easily.
fixes: #3223
Signed-off-by: Satyam Zode<EMAIL_ADDRESS>

@2opremio @bboreham Can you please review this?


Update authors.txt - Fix link for Veritas

Fix the link for the Veritas project

I've been working through some spelling error fixes, so I may push out a maintenance release soon despite not having a new chapter ready (yet).


Misaligned text at the front page

Describe the bug
There is misalignment in the front page and needs fixing.
To reproduce
Steps to reproduce the behavior

Use a mobile device.
Visit the website and go the main page.
Expected behavior
I think it would be better if the texts are centered.

Screenshots
From the mobile.

Yes that's true.

Describe the bug
There is misalignment in the front page and needs fixing.
To reproduce
Steps to reproduce the behavior

Use a mobile device.
Visit the website and go the main page.
Expected behavior
I think it would be better if the texts are centered.

Screenshots
From the mobile.

Yeah @xyrelljoi  if you can solve this issue please go ahead with this issue


Blazor WASM - There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

When adding the Balea to a Blazor WASM we get the following error...
There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

Thanks we were able to get this working.

I have the same problem with a new project. Eventually all nuget package references show warning icon...
Any suggestions?
What workerd for you?


add version module

Extract existing code we had to store the version from git in a file with the application.

We're currently processing your upload.  This comment will be updated when the results are available.


Creating/Maping rust types to Julia

in PyO3, one can map a rust type using PyObjectFrom to Julia, I'm wondering if there is something similar in this package to create a Julia object?

Currently, the only way is to generate wrappers with JlrsReflect.jl. The generated wrappers derive all necessary traits to access data of that type from Rust.
The other way around is not yet possible, but will be soon. My main focus for the next version of jlrs has been the ability to export Rust types and functions in a way similar to CxxWrap. In particular, you will be able to implement the OpaqueType or ForeignType trait and use macros to export that type and its methods to Julia. This file is an example of a library that uses this feature to expose RustFFT to Julia. I have a working Yggdrasil recipe for this library locally, but haven't committed that yet.
That feature is very much geared towards creating libraries that can be distributed as JLLs, though, not embedding.


zetacore : Move all TSS related messages to observer module

Seems to be duplicate of https://github.com/zeta-chain/node/issues/1512


docs(zh-cn): Reviewed 36_slice-and-dice-a-dataset-🔪.srt

docs(zh-cn): Reviewed 36_slice-and-dice-a-dataset-🔪.srt #390

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

this pr is ready for review, thx. @xianbaoqian


ci: add node v18 to test workflow

This PR contains a:

[ ] bugfix
[ ] new feature
[ ] code refactor
[ ] test update
[ ] typo fix
[ ] metadata update

Motivation / Use-Case

Add node v18 to test workflow

We need to update lock file here too


Communication tools and plans for FOSS4G 2023 Kosovo.

Such as:

[ ] What is the messaging app DWG 7 members use for internal communication?
[ ] What are the recommendation for expanding network, e.g. preparing Telegram and LinkedIn?

As discussed in #140

I revitalized my Telegram account!
I am also wondering how I should use both Telegram and Matrix depending on situation.
Maybe our main messaging stays Matrix, and I may also use Telegram if our new friends do not use Matrix.

Treated #150 for the OFF会 issue. Let's close this issue when we agreed on online communication issue.

Thanks to @smellman, we have a group in Facebook Messenger titled "FOSS4G 2023 Prizren/Kosovo".
I would recommend using Matrix to expand our online community. See also: https://github.com/UNopenGIS/7#readme.


Would you support a F-Droid store inclusion?

Thanks for your awesome app, and especially for publishing the source code.
I think it would be great to see your app in the F-Droid store and made an request for packaging, already here.
Would this be OK for you and would you support the inclusion?

@revuwa there seem to be some gradle issues. Could you please chime in here? Thanks in advance!

@IzzySoft  Is it related to gradle/wrapper/gradle.properties is missing distributionSha256Sum, unverified gradle download!?

@darshanparajuli Exactly that. But I'm not a dev, so better ask "behind the link" I gave :wink:

@IzzySoft Ahh.. I have never dealt with F-Droid, so I was asking to make sure.

No harm done. I was just pointing as I wasn't sure whether you might have missed it. So clarification is best done "over there" where the maintainers are, as they might have good pointers as well.

As F-Droid inclusion seems to take a while: if you could add an .apk to each release (starting with the current), @darshanparajuli, I could meanwhile make your app available via my repo.


Week5

The game works 95%, I couldn't make the rest button work. I'm going to try to figure it out tomorrow.

The game works 95%, I couldn't make the rest button work. I'm going to try to figure it out tomorrow.


refactor FunctionsSpec parallelize to use createDF

@lizparody - Great work.  It makes sense that the timestamp and date values tripped you up.  Take a look at the commit I added to get the code working and let me know if you have any questions!


Figure out how to extricate Sauce connect info from CI errors

We run Django with DEBUG = True when running our tests. This leaves open a door for a test error to leak sensitive and semi-sensitive information. For example, tests can leak info in debug logs and when hitting failure pages.
Two examples:

logs: https://travis-ci.org/eregs/regulations-site/jobs/149301618#L1385
debug page: https://travis-ci.org/eregs/regulations-site/jobs/149301618#L1385

It may be the case that running with DEBUG = False resolves these issues.

Just a heads up that we've deactivated the relevant API key, so sauce will fail until this is resolved.


improve consistency & visibility of colors on Reports page

Describe your changes
changed from

alternating colors of report cards had issues with button color ^
to

I tried making absolve green as well as changing the background for the card to blue to match FAQ & Tutorial, but those didn't look right.
Issue ticket number and link
NA

Looks much better, good work


Clarification required on more than three repetitions

Challenge reuse-patterns-using-capture-groups has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
I have some clarification issue.
There is some test case

Your regex should not match "42 42 42 42".

which passes when my regular expression matches this string, which is an obvious bug.
Also, behaviour for extra characters around the number that's repeated twice (like a fourth copy) is not specified in the task description, so should "12 2 23" or "42 42 42 42" match?
let repeatNum = "42 42 42 42";
let reRegex = /^(\d+)\s\1\s\1$/; // Change this line
let result = reRegex.test(repeatNum);

@Blauelf thanks for the issue. Yes, there's an error for that test.
Additionally, yes, the challenge requirements is imprecise. We could change it to something like

Use capture groups in reRegex to match numbers that are repeated only three times in a string, each separated by a space.

@erictleung I'd like to work on this.

@dakshshah96 awesome! Please first read the contributing guidelines before taking care of this issue. And feel free to visit the Contributors Help chat room if you have any questions about helping. We're there to help in case you need clarification or help on making changes. Thanks!

@erictleung Thanks! Should I fix both the test as well as the description in the same commit?

@dakshshah96 yes, that'd be great!

@erictleung Made the change here: #15515


Log window do not sync up message automatically

Environment URL: functions.azure.com
Corresbonding Ibiza URL: ms.portal.azure.com
App runtime version: ~1
Proxy runtime version: ~0.2
Private Site Extension: 1.0.10913
Repro steps:

Create a new function app and a function
Open its Develop page, click run for several times
Verify response shows 200 or 202 ...
Verify that nothing appears in Logs window

Please refer to snapshot:

I also have an issue with this and logging in general.
My function's logs are not always up to date and can sometimes jump back in time by several hours.
This is rather inconvenient when I am relying on logs for debugging.

fixed in f7a2af654c314082640dac57a121ebb8a1cb99c7


Typed function allows returning of objects with unknown properties

TypeScript Version:  2.6.2
Code
interface TestInterface {
    testValue: boolean;
}

let testFunc: () => TestInterface;

// Compiler allows returning unknown properties
testFunc = function() {
    return { testValue: true, otherValue: 7 };
}

// When the return type is explicitly specified, compiler warns about unknown properties
testFunc = function(): TestInterface {
    return { testValue: true, otherValue: 8 };
}

Playground
Expected behavior:
Since the testFunc has type annotation that specifies return value TestInterface, I expect that I will be able to return only objects with properties specified in TestInterface. However, the compiler allows me to return properties not specified in TestInterface.
To achieve my expected behavior, I need to explicitly specify the function return value. I think the compiler should be able to infer this from the type annotation.
Actual behavior:
Compiler does not complain about unknown object properties.

This works as intended. See https://github.com/Microsoft/TypeScript/wiki/FAQ#what-is-structural-typing

Duplicate of #7547


MolDraw2D, for svg inject metadata and class values from props

I think it would make sense to add injection of prop values into molecule metadata and svg selectors to allow additional per atom and bond information to be provided.
This PR allows injection of additional per atom/bond data into metadata via special props. The value of each "_metaData-" prop is added to atom/bond metadata under "key" specified by prop name.
Furthermore, this PR adds the ability to inject classes into svg atom/bond selectors via "_tagClass" property, value of which is added into classes of respective selectors.

Thanks @SPKorhonen !


Rustup

@bors r+

:pushpin: Commit d1c508fb2533d5cbdb345fe5f6df02656d62b976 has been approved by oli-obk
It is now in the queue for this repository.

:hourglass: Testing commit d1c508fb2533d5cbdb345fe5f6df02656d62b976 with merge e81f7421c72e619c828a5c5a7d39eb1c726a79ce...

:sunny: Test successful - checks-actions
Approved by: oli-obk
Pushing e81f7421c72e619c828a5c5a7d39eb1c726a79ce to master...

Nothing interesting to merge back: https://github.com/rust-lang/rust/compare/master...oli-obk:rust:test60?expand=1


Merging dev/0.7.0 into main ahead of release

This is a:

[ ] bug fix PR with no breaking changes — please ensure the base branch is master
[ ] new functionality — please ensure the base branch is the latest dev/ branch
[ ] a breaking change — please ensure the base branch is the latest dev/ branch
[x] all of the above

Description & motivation
let's release this 'ish!
(V grateful that we are squashing commits going forward — the history is much easier to read in the second half of this PR)
To do after merge:

[ ] have to go through and update all the dependent packages — since this has a required version increase, all the packages will need to go up by a minor release, right?

Closing as we are going to wait for dbt v0.20.0 compatibility to release the utils 0.7.0 package


Maestro cleanup

Not urgent
Removes un-used maestro features like mdns, templating, devicedb, and logging

See a similar PR for distro-pelion-edge:
https://github.com/PelionIoT/distro-pelion-edge/pull/179

Can you modify each commit message to mention specifically that the change is to the maestro config. For example, "Removed devicedb daemon and configuration" makes me think that devicedb daemon is removed from the snapcraft.yaml. Same with "Remove unused feature mdns". In isolation if viewed in git-history it won't be obvious that it's a maestro config change.

Yeah I can do that. To be clear though, this does remove the devicedb daemon, AND modifies the config.
So I can modify each commit to specify configuration vs daemon. But still doesn't change the fact that I remove the daemon as well.
Would it be useful for me to split the commits where i remove a daemon and adjust a config?

Can you modify each commit message to mention specifically that the change is to the maestro config. For example, "Removed devicedb daemon and configuration" makes me think that devicedb daemon is removed from the snapcraft.yaml. Same with "Remove unused feature mdns". In isolation if viewed in git-history it won't be obvious that it's a maestro config change.

Yeah I can do that. To be clear though, this does remove the devicedb daemon, AND modifies the config.
So I can modify each commit to specify configuration vs daemon. But still doesn't change the fact that I remove the daemon as well.
Would it be useful for me to split the commits where i remove a daemon and adjust a config?

hmm.  I missed the removal from the snapcraft.yaml file.  I swear I checked it twice before I commented.  weird.


Why a localhost addr appear in the Cluster info

Hi there,
I want to get all nodes ip by a simply way, then I find the Status.Addr of node info is useful. But after initing a swarm cluster, I get a localhost addr(<IP_ADDRESS>) when docker node inspect <the first manager node id>, Should it be the same as its advertised addr?
Steps to reproduce the issue:

init swarm

[root@dce-dev-1 hc]# docker swarm init
Swarm initialized: current node (ngodb1ibh7h0iai74kyimfnfy) is now a manager.

To add a worker to this swarm, run the following command:

    docker swarm join \
    --token SWMTKN-1-3tcxfr8jxtma8g1w20ps76t9ol9gdj4hxq1iub316w6eikf3ml-2jaqhe3p9sdohfg0opyhk15h6 \
    <IP_ADDRESS>:2377

To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.

inspect the node

# raw data
[root@dce-dev-1 hc]# docker node inspect ngodb1ibh7h0iai74kyimfnfy
[
    {
        "ID": "ngodb1ibh7h0iai74kyimfnfy",
        "Version": {
            "Index": 9
        },
        "CreatedAt": "2017-01-16T03:47:21.320634995Z",
        "UpdatedAt": "2017-01-16T03:47:21.423730084Z",
        "Spec": {
            "Role": "manager",
            "Availability": "active"
        },
        "Description": {
            "Hostname": "dce-dev-1",
            "Platform": {
                "Architecture": "x86_64",
                "OS": "linux"
            },
            "Resources": {
                "NanoCPUs":<PHONE_NUMBER>,
                "MemoryBytes":<PHONE_NUMBER>
            },
            "Engine": {
                "EngineVersion": "1.13.0-rc6",
                "Plugins": [
                    {
                        "Type": "Network",
                        "Name": "bridge"
                    },
                    {
                        "Type": "Network",
                        "Name": "host"
                    },
                    {
                        "Type": "Network",
                        "Name": "macvlan"
                    },
                    {
                        "Type": "Network",
                        "Name": "null"
                    },
                    {
                        "Type": "Network",
                        "Name": "overlay"
                    },
                    {
                        "Type": "Volume",
                        "Name": "local"
                    }
                ]
            }
        },
        "Status": {
            "State": "ready",
            "Addr": "<IP_ADDRESS>"  # the localhost addr appear here
        },
        "ManagerStatus": {
            "Leader": true,
            "Reachability": "reachable",
            "Addr": "<IP_ADDRESS>:2377"
        }
    }
]

# grep Status.Addr
# the first line is Status.Addr, the second line is ManagerStatus.Addr
[root@dce-dev-1 hc]# docker node inspect ngodb1ibh7h0iai74kyimfnfy | grep Addr
            "Addr": "<IP_ADDRESS>"
            "Addr": "<IP_ADDRESS>:2377"

# Status.Addr here is <IP_ADDRESS>, I think it should be <IP_ADDRESS>

join two manager nodes

[root@dce-dev-1 hc]# docker node ls
ID                           HOSTNAME   STATUS  AVAILABILITY  MANAGER STATUS
gf48s54umdrv44oszj2xwmb6f    dce-dev-3  Ready   Active        Reachable
ngodb1ibh7h0iai74kyimfnfy *  dce-dev-1  Ready   Active        Leader
rcddf3xb2pe7sew0kc47nz9fx    dce-dev-2  Ready   Active        Reachable

inspect the first manager node on another node

# raw data
[root@dce-dev-3 hc]# docker node inspect ngodb1ibh7h0iai74kyimfnfy
[
    {
        "ID": "ngodb1ibh7h0iai74kyimfnfy",
        "Version": {
            "Index": 9
        },
        "CreatedAt": "2017-01-16T03:47:21.320634995Z",
        "UpdatedAt": "2017-01-16T03:47:21.423730084Z",
        "Spec": {
            "Role": "manager",
            "Availability": "active"
        },
        "Description": {
            "Hostname": "dce-dev-1",
            "Platform": {
                "Architecture": "x86_64",
                "OS": "linux"
            },
            "Resources": {
                "NanoCPUs":<PHONE_NUMBER>,
                "MemoryBytes":<PHONE_NUMBER>
            },
            "Engine": {
                "EngineVersion": "1.13.0-rc6",
                "Plugins": [
                    {
                        "Type": "Network",
                        "Name": "bridge"
                    },
                    {
                        "Type": "Network",
                        "Name": "host"
                    },
                    {
                        "Type": "Network",
                        "Name": "macvlan"
                    },
                    {
                        "Type": "Network",
                        "Name": "null"
                    },
                    {
                        "Type": "Network",
                        "Name": "overlay"
                    },
                    {
                        "Type": "Volume",
                        "Name": "local"
                    }
                ]
            }
        },
        "Status": {
            "State": "ready",
            "Addr": "<IP_ADDRESS>"  # the localhost addr still appear here
        },
        "ManagerStatus": {
            "Leader": true,
            "Reachability": "reachable",
            "Addr": "<IP_ADDRESS>:2377"
        }
    }
]

# grep Status.Addr
[root@dce-dev-3 hc]# docker node inspect ngodb1ibh7h0iai74kyimfnfy | grep Addr
            "Addr": "<IP_ADDRESS>"
            "Addr": "<IP_ADDRESS>:2377"

# the Status.Addr is still <IP_ADDRESS>

#27910 add the field "Status.Addr" in every node, the addr should be the node's IP address as observed by the manager.
Output of docker version:
[root@dce-dev-1 hc]# docker version
Client:
 Version:      1.13.0-rc6
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   2f2d055
 Built:        Wed Jan 11 18:22:08 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.0-rc6
 API version:  1.25 (minimum version 1.12)
 Go version:   go1.7.3
 Git commit:   2f2d055
 Built:        Wed Jan 11 18:22:08 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
[root@dce-dev-1 hc]# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 5
Server Version: 1.13.0-rc6
Storage Driver: overlay
 Backing Filesystem: extfs
 Supports d_type: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: active
 NodeID: ngodb1ibh7h0iai74kyimfnfy
 Is Manager: true
 ClusterID: qya7eiumb6tnfhpyedt7m5f4t
 Managers: 3
 Nodes: 3
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
  <IP_ADDRESS>:2377
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 03e5862ec0d8d3b3f750e19fca3ee367e13c090e
runc version: 2f7393a47307a16f8cee44a37b262e8b81021e3e
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-514.2.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.793 GiB
Name: dce-dev-1
ID: X3TQ:KLCU:YGLA:OVPR:OVTO:SI7P:RHHU:2QDS:ZYPV:V63M:CHL3:QLD7
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/0
 <IP_ADDRESS>/8

related pr: #27910 https://github.com/docker/swarmkit/pull/1699

thanks for your feedback @sctlee
ping @dperny
What is the purpose to display a <IP_ADDRESS> address while not a LAN address, which also makes me feel confused.

I'm not sure. We may have changed something about the way the agent connects to the manager that's causing it to connect over localhost.

Hey, I'm curious there has been any progress on this. Anyone know? I'm currently trying to cope with this issue

I confirm the same behaviour on latest docker version, it happens when I just create a new cluster. If the managers goes down and up, it starts to display the external IP address.
I would expect to see always the external IP address, it's already reported in ManagerStatus section of the same json.

/cc @aaronlehmann

I believe this is fixed on master, and the fix will go out in the 17.04 release. The relevant swarmkit PR is https://github.com/docker/swarmkit/pull/1826

for reference, that PR was vendored through https://github.com/docker/docker/pull/30035
let me go ahead and close this issue, but feel free to comment if you're still seeing this after 17.04 was released

I encountered this problem today...
I am using latest docker-ce 19.03

docker info

Client:
 Debug Mode: false

Server:
 Containers: 5
  Running: 5
  Paused: 0
  Stopped: 0
 Images: 5
 Server Version: 19.03.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: active
  NodeID: pqgxrldap8kcymsdzkil8kxkp
  Is Manager: true
  ClusterID: gy9ktwot31qto9axpae2pwsfx
  Managers: 3
  Nodes: 4
  Default Address Pool: <IP_ADDRESS>/8
  SubnetSize: 24
  Data Path Port: 4789
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: <IP_ADDRESS>
  Manager Addresses:
   <IP_ADDRESS>:2377
   <IP_ADDRESS>:2377
   <IP_ADDRESS>:2377
 Runtimes: nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 4.15.0-52-generic
 Operating System: Ubuntu 18.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.66GiB
 Name: iZbp13txydl81paimm3up5Z
 ID: GNR5:7I3T:DXO5:IW44:NVFW:KTC2:32MG:BGEM:65SI:CZWX:FX22:JYZ5
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

docker node inspect pqgxrldap8kcymsdzkil8kxkp

    .....
        "Status": {
            "State": "ready",
            "Addr": "<IP_ADDRESS>"
        },
        "ManagerStatus": {
            "Leader": true,
            "Reachability": "reachable",
            "Addr": "<IP_ADDRESS>:2377"
        }
     .....

Any comments? Thanks.


refactor: new http wrapper in rhel provider

This uses the new HTTP GET wrapper in the RHEL provider. It also adds a new pattern, where the client can pass in a status_handler that will be called instead of response.raise_for_status to determine whether the request succeeded. This is because the RHEL provider doesn't retry 404s, so some inversion of control was necessary to preserver it's behavior. I'm looking for feedback on the approach.

Hi @willmurphyscode !  This is an interesting question but I think we can look at the abstractions expected from each function to guide us.
It feels to me like this is an acceptable case where the caller should catch the response.raise_for_status error and handle the 404 in a specific way since that is an error. Only the caller knows that an error (from the perspective of the http lib) is part of an expected path, so exception handlers seem justified there rather than adding complexity into the http layer itself. For example, the RHEL provider can wrap the http call and that keeps the RHEL path clean and also keeps the HTTP layer simple and http-focused.
Just my 2c.

@zhill I agree, but there would still be a subtle difference in the behavior: how does the caller tell the http.get wrapper not to retry 404s? (Maybe this is an unimportant feature of the current implementation, but right now it retries every status code except 404 and 200, while the http.get wrapper will retry 404s in an unconfigurable way.) I also thought about just passing in a collection of status codes that shouldn't be retried, but that might be too much less general.

Interesting 🤔 I wouldn't expect a http-level client to retry 4xx in general. I think the expectation for those errors is that they are not expected to work on a retry because the client is sending a bad request of some sort. I suspect that you're seeing API-specific logic here where, for example, the API may use 403s for rate-limit backoffs. That behavior is specific to the API that this provider is using, so I wouldn't bake it into the http utility itself, but the RHEL-data client layer.
I believe the goal of consolidation here is to unify client config and visibility (proxies, timeouts, logging etc) rather than response behaviors so I think what I'm suggesting is consistent with that goal.


Fixed issue

Description
Worked on issue #653
In tasks/htmx/easy directory I made a button that met these requirements:
The button should have an hx-get attribute that points to a URL of your choice (you can use a placeholder URL like "/your-endpoint").
The button should have an hx-trigger attribute set to "click".
When the button is clicked, it should load content from the URL specified in the hx-get attribute into an element on the page.
Create a target element with a unique ID (e.g., hx-target="#result") below the button and ensure that the button's hx-target attribute corresponds to the ID of the target element.
Once you've added the button with the correct HTMX attributes, you should be able to click it, and it should load content into the specified target element. You can test your implementation by opening the HTML file in a web browser.
Additional Context

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


LimeDrop.org doesn't work properly on Firefox ?

Hello,
Just a message to track the fact that there are JS errors on Firefox : it fails to load the

You must have some adon blocking it. I just clicked the link and it works fine.

You were right thanks. I tried with Firefox in safemode, and with disabling all my plugins one by one.
I don't know why, but it is Adblock Plus that prevents this script from loading. So for the moment a workaoround is to disable this plugin for limedrop webpage


Setup instructions for Setup systemd doesn't work

Copy in pasting the first command in Command Prompt or Powershell results in this error:
wsl.exe -d wsl-vpnkit --cd /app cat /app/wsl-vpnkit.service | sudo tee /etc/systemd/system/wsl-vpnkit.service
'sudo' is not recognized as an internal or external command,

I have the same issue too.
In addition, do we need to ensure systemd starts up on boot by updating /etc/wsl.conf?
[boot]
systemd = true

See Systemd support is now available in WSL!

With systemd enabled for a specific distro, all you have to do is this:
# activate systemd
sudo git config -f /etc/wsl.conf boot.systemd "true"

# need restart to activate
wsl.exe --shutdown

Do it in the distro you are working on like Ubuntu or something else other than "wsl-vpnkit".
I don't recommend doing this in the wsl-vpnkit distro though as that is currently working fine without systemd.
if you have a "sudo" error... how about installing "sudo" package or check system PATH ?

I try to inspect the wsl-vpnkit distribution like this,
$ wsl.exe -d wsl-vpnkit
C-PF3EKVLL:~# whoami
root
# ls /app/wsl-vpnkit.service
/app/wsl-vpnkit.service
C-PF3EKVLL:~# ls /etc/systemd/
ls: /etc/systemd/: No such file or directory
C-PF3EKVLL:~#

The default user is root and maybe sudo is not required?
Also note that here is no /etc/systemd directory.

You are missing the point... you are running commands to go inside the distro "wsl-vpnkit" (wsl.exe -d wsl-vpnkit) and you shouldn't. That's not the place you want to check if 'sudo' is available or not.
You can see the distros you have available with wsl.exe -l -v

Closing since the issue seems resolved. Thanks @josesa-xx.


musl: add unreleased upstream patch; fixes NixOS#285141

Description of changes
Building musl on Darwin results in unreadable symlinks (#285141). Patch has been committed upstream, but not yet released.
I've only included the patch when building on Darwin. It'd have no effect on linux so might as well save some unnecessary rebuilds.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Replaced by https://github.com/NixOS/nixpkgs/pull/298591


Decrease compile time

Summary
Changed files are recompiled at every build due to generated flat buffer headers. Use forward declaration to reduce the time spent while compiling those.
What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Build-related changes
[ ] Other, please describe:

If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's body (e.g. Fixes: #xxx[,#xxx], where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature
[ ] Related documents have been updated (docs/docs/en)
[ ] Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:

Thank you very much. Are you done here?

i saw this commit make crash when first opening soft after installing

@tihoangyeudau  Can you be more clear ? Opening what ? Installing what ? This PR just replaces header inclusion with forward declaration. Any development error should reveal itself in compile time, not in runtime.

@tihoangyeudau Can you be more clear ? Opening what ? Installing what ? This PR just replaces header inclusion with forward declaration. Any development error should reveal itself in compile time, not in runtime.

sorry, i cleaned and rebuilded then it works correctly


Hope to provide the files MD5 in the release

Files downloaded from the cloud disk may be damaged or modified.
Although this is a low-probability event, providing MD5 to users to verify file integrity is a good method.

Thanks for the reminder, the prompt has been added in the new version.


NETOBSERV-688 UI: Overview labels options

Added truncate label option in Overview Display options
Uses existing topology truncate option for side panel graphs
Adapt text size according to selected truncate length (XS / S are bigger)
2 items per row in legend when possible

/lgtm

/approve thanks @jotak !


Replayer Server With Auto verification

Should choose if the content has to be verified against a js function and or schema validation

show content type on recordings
add combo none/xml/json to verify the recorded response against the real one
add play results


Add support for logout

Would be great if you can add logout ability to the CLI tool.

Hi @ariannargesi,
This feature already exists, indeed. You just need to run the liara account:rm command.


Use openapi.json for HTTP APi docs.

🗣 Description

🔨 Related Issues

🤔 Concerns

The above comments should not be included here, they are automatically generated from .schema/openapi.json  in https://github.com/spiceai/spiceai.
I have created a PR there with these changes: https://github.com/spiceai/spiceai/pull/4019


Downloading the unused assets (js, css) inside the demo of the theme

The Chrome browser console warn me about downloading the assets, that aren't used on the page of the theme.
Here is these files:
https://themes.gohugo.io/dist/main.css
https://themes.gohugo.io/dist/app.bundle.js
I just would like to clarify do these files needed?
Here how it's looks:

Duplicate of https://github.com/gohugoio/gohugoioTheme/issues/99

@digitalcraftsman This issue needs to be closed because it has a duplicate in the gohugoio Theme repo. Thanks!