starRatedColor not working

the starRatedColor option is not working wheter i put in starRatedColor='rgb(109, 122, 130)' or starRatedColor='black'. Is there any known bugs? Using 2.3

Same probleme here

Be careful in fact because on the mobile version it is the props hover that is taken into account... as long as you don't click elsewhere

in mobile fixed this, using the prop: starHoverColor, setting this to the same color that I want on the rated star color
you only loss the a custom color on hover,


2.3.2 Create Sequence Diagram - Allocate Job to staff

Tasks:
Create UML Sequence Diagram for these following interactions:

[x] How the manager would allocate workload to workers.
[x] How the workers would allocate their availability and preferences.
[x] How would workers reject a job given.

Optionally

[ ] Login process for workers/managers.
[ ] How would an IT Staff create new accounts for worker/managers.

Feel free to in more as deemed necessary.

Goals: To create the sequence diagram for 'Allocate Job to staff' use case
Completion Criteria: The sequence diagram must encompass the flow based on the use case description and class diagram.
Allocated Time: 8 days
Start & End date : 27/9/23 to 6/10/23

Also, waiting on #15 to finalize diagram idea.

Sequence Diagram for how managers would allocate workload to users

Flow of sequence diagram is done, and attributes are based off of the class diagram


[Backport] [v2.7] [RFE] Add CIS-1.8 (k8s v1.26) Scan capability

CIS Workbench has released CIS-1.8 for k8s v1.26 (on oct 6th).
This issue is pending the creation of cis-1.8 in kube-bench's cfg. We will start integrating CIS-1.8 to Rancher cis-benchmark once the profile will be made available upstream.
Past issue for CIS-1.7 : https://github.com/rancher/rancher/issues/41631

Closing this issue as it's a duplicate of https://github.com/rancher/rancher/issues/43710


Strip postcodes from more document types in meta_tags component

What
The documents types listed below will now include the <meta name="govuk:static-analytics:strip-postcodes" content="true"> meta tag.

transaction
local_transaction
place
special_route

This will ensure that postcodes strings are replaced with "[postcode]" in any pages with these document types.
Why
To stop personal postcode data from being sent to Google Analytics.
Testing
I deployed the changes to integration and tested the pages below using the Google Analytics Debugger browser extension for Google Chrome, the differences in the "location" being sent to GA are shown below.

Integration
Live

/contact-electoral-registration-office?postcode=[postcode]
/contact-electoral-registration-office?postcode=SW11AA

/find-driving-test-centre?postcode=[postcode]
/find-driving-test-centre?postcode=SW11AA

/find-local-council?postcode=[postcode]
/find-local-council?postcode=SW11AA

/apply-for-secondary-school-place?postcode=[postcode]
/apply-for-secondary-school-place?postcode=SW11AA

/apply-for-primary-school-place?postcode=[postcode]
/apply-for-primary-school-place?postcode=SW11AA

/disabled-students-allowances-assessment-centre?postcode=[postcode]
/disabled-students-allowances-assessment-centre?postcode=SW11AA

/find-out-about-right-to-buy-from-your-council?postcode=[postcode]
/find-out-about-right-to-buy-from-your-council?postcode=SW11AA

/check-long-term-flood-risk?postcode=[postcode]
check-long-term-flood-risk?postcode=SW11AA

Thanks @jon-kirwan, I have squashed the commit history down in to a single commit as requested.


[5.10][Features] Update upcoming feature flags for Swift 6.

Explanation: Changes and additions to upcoming feature flags for Swift 6 as described in https://forums.swift.org/t/progress-toward-the-swift-6-language-mode/68315.

Don't enable ExistentialAny by default in Swift 6.
Gate SE-0383 behind an upcoming feature flag.

Note that the first point has no functional impact on release/5.10. I only included it to make the second commit cherry pick cleanly.

Scope: Does not impact any existing code. This change gates the deprecation warning for SE-0383 behind the upcoming feature flag, which is currently unconditional on the release/5.10 branch.
Risk: Low; the only functional impact is adding an upcoming feature flag and gating a diagnostic behind it.
Testing: Updated test cases.
Main branch PR: First two commits of https://github.com/apple/swift/pull/70123.

@swift-ci please test


NameError: name 'FunctionCallRequest' is not defined

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Steps to Reproduce (for bugs)

install cvat-sdk: pip install cvat-sdk
run code provide by the docs replacing necessary fields

Expected Behaviour
Automatic annotation should begin with model provided
Current Behaviour
When running the code provided by the docs this error appears
Traceback (most recent call last):   File "/pathtofile/annotate.py", line 18, in <module>     function_call_request = FunctionCallRequest( NameError: name 'FunctionCallRequest' is not defined
Possible Solution
cvat_sdk should have the model FunctionCallRequest
api_client.lambda_api.create_requests() should take FunctionCallRequest as input
Your Environment

cvat_sdk==2.4.7
Windows

Hi, probably, you're reading the development version docs, as the API definitions for lambda were introduced in https://github.com/opencv/cvat/pull/6276, which has not been included in any release yet. If you're actually using the development version, you can build SDK for your version manually.
Related: https://github.com/opencv/cvat/issues/6351

Yep building the sdk worked!


feat: LWW-Element-Set & Tests

LWW-Element-Set & OR-Set implemented in the builtins.

I've finished the tests and the implementations.
I also made the following changes in the existing CRDTs:

I've fixed the compare method (instead of comparing with '==' it compares the values of each set)
I've change the ID of the GCounter from string to number (I've read that the ID is a number from 0 to n-1) (https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type#G-Counter_(Grow-only_Counter))

This branch also contains some changes in the GSet and contains the GSet and 2PSet tests. I've also added the GCounter and PNCounter to pass the pipeline tests, but I'll add them to their PR with the changes that I made.


angular-1.3.8 - Infinite digest in Safari 5.1 related with difference between $browser.url() and $location.absUrl()

I explored that this code worked unexpectedly in Safari 5.1 (row 11397 in angular.js)
var oldUrl = trimEmptyHash($browser.url()); // returns "http://swift-musk-ox-6940.vagrantshare.com/catalog/c596/для_женщин/"
var newUrl = trimEmptyHash($location.absUrl()); // returns http://swift-musk-ox-6940.vagrantshare.com/catalog/c596/для_женщин/
Maybe it related with Safari's "location.href" returns undecoded url

@SerjoPepper - thanks for reporting this issue. I am afraid that Safari 5.1 is no longer supported by Apple on any platform. I could not reproduce this issue in Angular on my only version of Safari which is Version 8.0.7 (10600.7.12).
I am afraid that we will not be providing resources to fix this issue. If you are able to provide a PR with tests that fixes this without breaking the latest versions of our supported browsers, then I would be happy to consider it.

@petebacondarwin this bug reproduces not only in Safari in 5.1. I explored this bug when used prerender.io. Prerender.io uses Phantom.js 1.9 version, which uses same webkit engine as in Safari 5.1

OK, so can you reproduce this in a unit test that fails with phantomjs 1.9?

yes, I can, with any cyrillic url. I am able to provide PR

Awesome.

Closing this - please provide a PR with a unit test that fails on phantomjs 1.9. Thanks


Common subscriptions issued by different clients at the same time may be lost

Fixes #185

I see no significant change in benchmarks with this change, so I will merge it - thank you very much @ffa500!


doc: source map upload example about react native project

in docs, there is a require param minifiedUrl, how to fill this on a react native project, "main.jsbundle" or ?
can you give some example about react native project?

Hi @iwater - there are some specific docs for React Native source maps which should help - https://docs.bugsnag.com/platforms/react-native/showing-full-stacktraces/#uploading-source-maps

@duncanhewett The docs aren't helpful. It's been over 10hrs of futile efforts to upload source maps. Having react-native support should ideally have this feature built in as most of the code being executed is in Javascript and not native. Please improve the docs and the library. Thanks!

@keshavkaul Hi. Can you tell me please how did you do that? Tried many times but my URLs don't match.


[WFLY-16880]: Using SSL with a netty-acceptor is failing.

Adding the missing dependency to "io.netty.netty-transport-native-unix-common".

Jira: https://issues.redhat.com/browse/WFLY-16880
Upstream https://issues.redhat.com/browse/WFLY-16879
Signed-off-by: Emmanuel Hugonnet<EMAIL_ADDRESS>Upstream PR: https://github.com/wildfly/wildfly/pull/15984

Thanks, @ehsavoie


Better image processing support

I have issues using svg-to-png and the underlying pupperteer modules due to a proxy issue. I also did not like the size and overhead that these modules bring with them.
As a result of this, I started to investigate processing the generated SVG with regular image processing tools like imagemagick, or the npm package sharp, but found these had subtle issues with processing the SVG.
I was able to resolve these issues with the following custom command, which allowed me to use sharp in the following manner:
import sharp from 'sharp'
const svg = receiptline.transform(...)
const png = await sharp(svg).png().toBuffer()

Not only is this significantly quicker than puppeteer, it is also comes with a much smaller dependency size.
My custom command is as below:
const custom = {
  ...receiptline.commands.svg,
  ...{
    close: function() {
      return receiptline.commands.svg.close.bind(this)()
        .replace('>', '><rect width="100%" height="100%" fill="white"/>')
        .replace('<filter id="receiptlineinvert" x="0" y="0" width="100%" height="100%">', '<filter id="receiptlineinvert" x="-1%" y="-15%" width="102%" height="150%">')
    },
    text: function (text, encoding) {
      let p = this.textPosition;
      const attr = Object.keys(this.textAttributes).reduce((a, key) => a + ` ${key}="${this.textAttributes[key]}"`, '');
      this.textElement += `<text${attr}>`
      for (const character of Array.from(text)) {
        const q = this.measureText(character, encoding) * this.textScale;
        const r = (p + q / 2) * this.charWidth / this.textScale;
        p += q;
        this.textElement += `<tspan x="${r}">${character.replace(/[ &<>]/g, r => ({' ': ' ', '&': '&', '<': '<', '>': '>'}[r]))}</tspan>`;
      }
      this.textElement += `</text>`
      this.textPosition += this.measureText(text, encoding) * this.textScale;
      return '';
    },
  }
}

Most of these changes are transparent to the output, and will work fine in a browser, as well as with generic image processing tools. The only exception to this for which I have been unable to find a workaround for is the receiptlineinvert filter. Whilst what I have provided above seems to work well in an image processor or sharp, in chrome there is just a bit too much "padding" around the element.
Is there some way to incorporate these changes so that generic image processing tools can be used to process the svg?

Thank you for using receiptline!
I have tried your custom command.
The processing speed was very fast and the text positioning was improved.
But in some cases, multibyte characters were out of place.
As you know, SVG implementations have compatibility issues.
So  may not be positioned as expected.
In order for image processing tools to do the expected conversion, the  must be used.
Currently, the most compatible SVG implementations are web browsers.
So we use puppeteer, although it is larger in size and overhead.
I think your custom command is a good solution under limited conditions.
Thank you!

Your source code was a hint for us to support Thai characters.
Thank you!
And we will soon release a version that supports "sharp".
There are some limitations.
"sharp" minimizes the area of "invert" character decoration.


Operation not permitted when trying to open realm

I know some people have reported it, but I haven't found a fix to it.

Goals
Know the reason why it happens
Expected Results
apps not crashing
Actual Results
Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=io.realm Code=2 "Unable to open a realm at path '/var/mobile/Containers/Data/Application/5CB3C733-8188-440C-9AF5-A24169CD580A/Documents/default.realm.lock': open() failed: Operation not permitted Path: /var/mobile/Containers/Data/Application/5CB3C733-8188-440C-9AF5-A24169CD580A/Documents/default.realm.lock Exception backtrace: 0 Realm 0x0000000101422ad0 _ZN5realm4util4File13open_internalERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEENS1_10AccessModeENS1_10CreateModeEiPb + 712 1 Realm 0x0000000101329d70 _ZN5realm11SharedGroup7do_openERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbbNS_18SharedGroupOptionsE + 1272 2 Realm 0x00000001012498ac _ZN5realm5_impl11RealmFriend13read_group_toERNS_5RealmENS_9VersionIDE + 4712 3 Realm 0x0000000101249540 _ZN5realm5_impl11RealmFriend13re

Crashed: com.apple.main-thread
0  libswiftCore.dylib             0x1a120faa4 specialized _assertionFailure(_:_:file:line:flags:) + 440
1  libswiftCore.dylib             0x1a1069910 swift_unexpectedError + 288
2  our_app                            0x1006b0a04 specialized AppDelegate.checkRealmSchema() + 285 (AppDelegate.swift:285)
3  our_app                   0x1006aeedc AppDelegate.setupTabs() + 172 (AppDelegate.swift:172)
4  our_app                   0x1006b0f84 specialized AppDelegate.application(_:didFinishLaunchingWithOptions:) + 41 (AppDelegate.swift:41)
5  our_app                   0x1006ae470 @objc AppDelegate.application(_:didFinishLaunchingWithOptions:) +<PHONE_NUMBER> (<compiler-generated>:4305511536)
6  UIKitCore                      0x197dceee4 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 340
7  UIKitCore                      0x197dd0ca0 -[UIApplication _callInitializationDelegatesWithActions:forCanvas:payload:fromOriginatingProcess:] + 5076
8  UIKitCore                      0x197dd642c -[UIApplication _runWithMainScene:transitionContext:completion:] + 1248
9  UIKitCore                      0x1975a3208 -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 148
10 UIKitCore                      0x197a39698 _UIScenePerformActionsWithLifecycleActionMask + 100
11 UIKitCore                      0x1975a3cf0 __101-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]_block_invoke + 196
12 UIKitCore                      0x1975a37fc -[_UISceneLifecycleMultiplexer _performBlock:withApplicationOfDeactivationReasons:fromReasons:] + 476
13 UIKitCore                      0x1975a3b1c -[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:] + 736
14 UIKitCore                      0x1975a33d8 -[_UISceneLifecycleMultiplexer uiScene:transitionedFromState:withTransitionContext:] + 336
15 UIKitCore                      0x1975a78c4 __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke_2 + 188
16 UIKitCore                      0x19796af08 +[BSAnimationSettings(UIKit) tryAnimatingWithSettings:actions:completion:] + 824
17 UIKitCore                      0x197a52c84 _UISceneSettingsDiffActionPerformChangesWithTransitionContext + 244
18 UIKitCore                      0x1975a75fc __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke + 136
19 UIKitCore                      0x197a52b80 _UISceneSettingsDiffActionPerformActionsWithDelayForTransitionContext + 100
20 UIKitCore                      0x1975a7468 -[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:] + 376
21 UIKitCore                      0x1974192c0 __64-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]_block_invoke + 636
22 UIKitCore                      0x197417e28 -[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:] + 248
23 UIKitCore                      0x197418ff8 -[UIScene scene:didUpdateWithDiff:transitionContext:completion:] + 220
24 UIKitCore                      0x197dd47e4 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 548
25 UIKitCore                      0x19798b900 -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 360
26 FrontBoardServices             0x198e857a0 -[FBSSceneImpl _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 436
27 FrontBoardServices             0x198eaa838 __86-[FBSWorkspaceScenesClient sceneID:createWithParameters:transitionContext:completion:]_block_invoke.154 + 100
28 FrontBoardServices             0x198e8ff04 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 232
29 FrontBoardServices             0x198eaa4f4 __86-[FBSWorkspaceScenesClient sceneID:createWithParameters:transitionContext:completion:]_block_invoke + 312
30 libdispatch.dylib              0x193a1f184 _dispatch_client_callout + 16
31 libdispatch.dylib              0x1939f9420 _dispatch_block_invoke_direct$VARIANT$armv81 + 216
32 FrontBoardServices             0x198ecf418 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 40
33 FrontBoardServices             0x198ecf0e4 -[FBSSerialQueue _queue_performNextIfPossible] + 404
34 FrontBoardServices             0x198ecf60c -[FBSSerialQueue _performNextFromRunLoopSource] + 28
35 CoreFoundation                 0x193cd0a00 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
36 CoreFoundation                 0x193cd0958 __CFRunLoopDoSource0 + 80
37 CoreFoundation                 0x193cd0140 __CFRunLoopDoSources0 + 260
38 CoreFoundation                 0x193ccb23c __CFRunLoopRun + 1080
39 CoreFoundation                 0x193ccaadc CFRunLoopRunSpecific + 464
40 GraphicsServices               0x19dc6b328 GSEventRunModal + 104
41 UIKitCore                      0x197dd863c UIApplicationMain + 1936
42 our_app                   0x10067ca2c main + 22 (MapSelectionViewController.swift:22)
43 libdyld.dylib                  0x193b54360 start + 4

What is weird is, it is always crash when started from MapSelectionViewController which probably means it is not in background.
Steps to Reproduce
No clue how.

Code Sample

have been trying this with no luck.
 Realm.Configuration.defaultConfiguration = config

/** Realm will crash if it can't write into files in it's directory. Try to remove permission and open again**/
  do {
     _ = try Realm()
 } catch _ as NSError {
     let realmPath =       Realm.Configuration.defaultConfiguration.fileURL!.deletingLastPathComponent().path
     try! FileManager.default.setAttributes([.protectionKey: FileProtectionType.none], ofItemAtPath: realmPath)
      _ = try! Realm()
 }

Version of Realm and Tooling

Realm framework version: 5.2.0
Realm Object Server version: ?
Xcode version: 11.3.1
iOS/OSX version: 12 and 13
Dependency manager + version: ?
Thanks before.
Edit: Firebase shows 0% background, if it helps. I don't think it is memory problem too, since users still have some left.

same problem

When will version 5.0.0 release ?

I know how to fix it

Message me

Message me

hmmm, are you willing to share it here instead? So the others can be helped as well

Facing same issue. Please share solution over here.

@marsha97 Can you upgrade to the latest version of Realm and let us know if this issue still persists?
Thanks,
Lee

@marsha97 Can you upgrade to the latest version of Realm and let us know if this issue still persists?
Thanks,
Lee

Will do, in our next release

Facing same issue

It is almost a month since our latest iOS app with realm 5 released, and I haven't found the same crash happen again. So I will close this issue for now. Thank you 👍

version 5.3.5 found the same crash!

version 5.3.5 found the same crash!

oh, you are right we got it at 20 August 2020, on realm 5.2.0, will repoen this issue again 😅

Hi @marsha97 Can you give us more context with how you are using Realm? Are you using any app extensions, multithreading etc? Is this issue intermittent? Could you also share with us your Realm Configuration object?
Thanks

We are using realm for regular CRUD, sync from server, update/create. Read from it for displaying data, and delete data when user is logging out. But, we do access realm on app delegate, when user is tapping notification
 func userNotificationCenter(_ center: UNUserNotificationCenter,
                                didReceive response: UNNotificationResponse,
                                withCompletionHandler completionHandler: @escaping () -> Void) {
        guard Session.isAuthenticated() else {
            return
        }

        guard let data = response.notification.request.content.userInfo as? [String: Any] else {
            return
        }
        guard let type = data["type"] as? String else {
            return
        }
        switch type {
        case "promotion":
            let navigationController = prepareNotifactionRedirect(to: 0)
            let homeController = navigationController?.viewControllers.first as? HomeViewController
            homeController?.openPromotionDetails(id: data["promotion_id"] as? Int)  # we read promotion with the passed id, or sync and create it, if it is not present
        case "reward":
            let navigationController = prepareNotifactionRedirect(to: 2)
            let rewardController = navigationController?.viewControllers.first as? RewardIndexViewController
            rewardController?.openRewardDetails(id: data["reward_id"] as? Int)  # same as above
        default:
            break
        }
    }

our config is just for migration schema version
func checkRealmSchema() {
        let config = Realm.Configuration(
            schemaVersion: 14,

            migrationBlock: { migration, oldSchemaVersion in
                if (oldSchemaVersion < 1) {
                    migration.enumerateObjects(ofType: Voucher.className()) { oldObject, newObject in
                        newObject!["quantity"] = 0
                        newObject!["status"] = 0
                    }
                }
                ....
         }

        Realm.Configuration.defaultConfiguration = config

        /** Realm will crash if it can't write into files in it's directory. Try to remove permission and open again**/
        do {
            _ = try Realm()
        } catch _ as NSError {
            let realmPath = Realm.Configuration.defaultConfiguration.fileURL!.deletingLastPathComponent().path
            try! FileManager.default.setAttributes([.protectionKey: FileProtectionType.none], ofItemAtPath: realmPath)
            _ = try! Realm()
        }

And, we don't use any extension for this project. And we haven't found any pattern on how this happens yet.

Can you update to version 5.4.6 and see if that helps? Thanks

Can you update to version 5.4.6 and see if that helps? Thanks

I got these warnings when upgrading into 5.4.6, so I will stay with 5.2.0 for a while
https://github.com/realm/realm-cocoa/issues/6688

Has anyone continued to see this crash in >=5.4.2?
As Lee mentioned here, changes to file locking were added.

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Still facing the crash on app up for realm 5.5.0

Still facing the crash on app up for realm 5.5.0

maybe, you can open a new issue based on this version? since this one had been closed

Linking to existing issue
https://github.com/realm/realm-cocoa/issues/6096


Updates to DG

Fixes #251, Fixes #109

Codecov Report

Merging #277 (588c02a) into master (da7e978) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #277   +/-   ##
=========================================
  Coverage     56.29%   56.29%
  Complexity      625      625
=========================================
  Files           123      123
  Lines          2636     2636
  Branches        330      330
=========================================
  Hits           1484     1484
  Misses         1031     1031
  Partials        121      121

Continue to review full report at Codecov.

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


feat(doc comments on hover)

Shows documentation comments /// for models and enums on hover.
This also includes an e2e test for this functionality.

this is branched from #129, so #129 has to be merged first

https://github.blog/changelog/2020-05-19-pull-request-retargeting/ could (!) mean that you can possibly chaneg this PR to target the autoCompletionResearch branch, and then after that was merged to master this PR here should automatically be updated to point to master - might be a good opportunity to test out if I understood the change on GH correctly.

Looks good! Do you also lookup // comment?
Not sure if it's clear what the difference is

/// comment is meant to persist in the database's COMMENT section.
// comment is meant for the readers, but it's not persistent.

From VSCode's context, you're a developer who wants to understand the datamodel, so you'll probably want to allow both, if either is attached to a model or field.

Currently I only lookup /// comment. But I agree, I should check for both // and /// comments.

Interesting reading of the specs @matthewmueller - I was not aware of this. I thought // was just a comment int he schema, while /// was to "document" the entity it was besides.
We should probably clarify the specs and if this is indeed wanted behavior before we adapt the implementation to what you describe.

@carmenberndt can you possibly create a nice screenshot that highlights how this works and looks like and add it to the PR description?

So I'll remove the implementation for // comments for now then?


[FEATURE] Enable Private Relay Support NIP-42 [500k sats]

User Story
As a Amethyst user who wants to connect with a particular group of nostriches privately, I want to be able to connect to a private relay, so that I can read and share notes only with a specific group of nostriches.
Acceptance Criteria

Amethyst user can connect to a private relay
Amethyst user has a method to provide authentication details to a private relay
Amethyst user can check visually if they are successfully connected to the private relay
Amethyst user can remove a private relay
Amethyst user can de-authenticate from a private relay

implementation details
NIP-42
Origin: https://iris.to/note1c6khgk6phxzhq7hh2v32nhzrvlyn4y2ctk6h0kgtgfrgrh7y7e5qma8ykl
**Bounty (in Bitcoin sats) 500k sats by Mazin npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz
Additional context
Introduced feature request to Damus (iOS), and Iris (web) as well.
Why is this important: private relays provide differentiation and novelty compared to incumbent twtr.

We'll offer a 500k sats bounty per client for this feature.

Any takers?

Yep. I will start coding soon. Can somebody arrange a few test credentials to existing private relays?

Awesome. Yes - I've given your pubkey access to filter.nostr.wine for a year. If you connect to wss://filter.nostr.wine (no path) it will prompt you to AUTH on connect. If you need any other accounts, let us know.

Done: https://github.com/vitorpamplona/amethyst/commit/14bc1fb7d46bb086047dc906639b596a204e3230
New version soon. It will be available on v0.36.0

Incredible. Thank you Vitor! I'll zap you the bounty.

Thank you for the SATs! Let me know if you find any issue using it.

Was bout to post...I can't seem to load global when trying to test this on 0.36.0 right now.

Hum.. i can check in more detail tomorrow. The relay doesn't send any confirmation that it received the challenge, right?
The app is sending the secret. And I assume it's shared in all subscriptions. The only question is if the package is received correctly.

Yes the relay will respond to the AUTH event with ["OK", "event-id", true, ""] or ["OK", "event-id", false, "error: msg"]

Yup, I just confirmed that's whats happening. Just make the 22242 use "AUTH" in front instead of "EVENT" and everything else looked good. Keep in mind that this came after some REQs so be aware that due to that race condition we are ignoring the preceding ones.

Ohhh what an oversight! ( and super weird spec ). Will fix soon

Hmmm, that event/response looks valid to me. The path to that message is

if the created_at timestamp is > 10 minutes old (doesnt seem to be the case)
If the AUTH challenge was replaced by a new one (happens on reconnect and if you AUTH can't be validated)

Your tags and everything else look correct in the above event. I'm able to test it over and over with nostril from terminal successfully both with authorized and with unauthorized pubkeys.

Could it be my user that the server is rejecting?

An unauthorized user returns ["OK", "9bb125d444456b4dd054afc0bcb743a8573fd5aa04c2f98bc21f36b65c33cac8", false, "error: user unauthorized"] not unable to validate auth

Are you using an open source relay? I can take a look at their code to see what I am missing

Strfry doesn't support it so it is our own custom websocket but it has worked with every client who has implemented so far. You can also try wss://nostr.kollider.xyz that (I believe) uses https://github.com/scsibug/nostr-rs-relay

Kollider says User is not admitted. I am not sure how to get a credential with them

Since nostr-rs-relay seems to depend on rust-nostr/nostr crate, the above issue may be related. Now it has been fixed on upstream (on master branch), so if nostr-rs-relay incorporates it, the problem may be solved.

**should this the intention to use nostr? Seperated from the Community as an private only member club ? **


lib.systems.doubles.all: reorganize

Motivation for this change
The previous mess was partially grouped by OS, and partially grouped
by architecture, which made it very difficult to know where to add new
entries.
I've chosen to group by OS entirely, because OSes are likely to
maintain exhaustive lists of supported architectures, but it's far
less likely we'd be able to find exhaustive lists of supported OSes
for every architecture.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I'm fine with rearranging the big lists, but I think all lists below should be calculated not handwritten. This is important to ensure that the predicates and the platforms list stay in sync.

See also https://github.com/NixOS/nixpkgs/blob/master/lib/tests/systems.nix for the lists which are supposed to stay hand coded.

I'm fine with rearranging the big lists, but I think all lists below should be calculated not handwritten. This is important to ensure that the predicates and the platforms list stay in sync.

I don't understand what you mean by this.  Can you rephrase?

I mean when we do e.g.
darwin = filterDoubles predicates.isDarwin;

and then in https://github.com/NixOS/nixpkgs/blob/master/lib/tests/systems.nix do
testdarwin = mseteq darwin [ "x86_64-darwin" "i686-darwin" "aarch64-darwin" "armv7a-darwin" ];

we are testing isDarwin does what we expect, but if we write
darwin = [ "x86_64-darwin" "i686-darwin" "aarch64-darwin" "armv7a-darwin" ];

here we are no longer testing isDarwin.

I mean when we do e.g.
darwin = filterDoubles predicates.isDarwin;

and then in https://github.com/NixOS/nixpkgs/blob/master/lib/tests/systems.nix do
testdarwin = mseteq darwin [ "x86_64-darwin" "i686-darwin" "aarch64-darwin" "armv7a-darwin" ];

we are testing isDarwin does what we expect, but if we write
darwin = [ "x86_64-darwin" "i686-darwin" "aarch64-darwin" "armv7a-darwin" ];

here we are no longer testing isDarwin.

Ah, I see.  So should I just make all a big array, with comments to
seperate different OSes maybe, and go back to generating all the smaller
lists?

That sounds great to me!


packet size limit

I found  if the data size is large, sendToGroup() will split the string then send next time.
How to know and set packet size limit?

Which protocol do you use for gateway?

tcp

Your application should an application layer protocol.
See https://stackoverflow.com/questions/756765/when-will-a-tcp-network-packet-be-fragmented-at-the-application-layer


Unable to createsuperuser on current production-ready tag

What I'm trying to achieve
I'm trying to deploy (and run locally) a production-ready saleor using the 3.0 tag, as per the README.
Steps to reproduce the problem

git clone https://github.com/saleor/saleor.git
cd saleor
git checkout 3.0
# create and activate a venv, run migrations
./manage.py createsuperuser

Last command fails with a traceback.
What I expected to happen
A Django superuser is created successfully.
Screenshots and logs
Traceback from createsuperuser:
Traceback (most recent call last):
  File "redacted/saleor-platform/saleor/./manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
    utility.execute()
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/core/management/__init__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/core/management/base.py", line 354, in run_from_argv
    self.execute(*args, **cmd_options)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/contrib/auth/management/commands/createsuperuser.py", line 79, in execute
    return super().execute(*args, **options)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/core/management/base.py", line 398, in execute
    output = self.handle(*args, **options)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/contrib/auth/management/commands/createsuperuser.py", line 189, in handle
    self.UserModel._default_manager.db_manager(database).create_superuser(**user_data)
  File "redacted/saleor-platform/saleor/saleor/account/models.py", line 136, in create_superuser
    return self.create_user(
  File "redacted/saleor-platform/saleor/saleor/account/models.py", line 132, in create_user
    user.save()
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/contrib/auth/base_user.py", line 67, in save
    super().save(*args, **kwargs)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/models/base.py", line 739, in save
    self.save_base(using=using, force_insert=force_insert,
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/models/base.py", line 776, in save_base
    updated = self._save_table(
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/models/base.py", line 881, in _save_table
    results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/models/base.py", line 919, in _do_insert
    return manager._insert(
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/models/query.py", line 1270, in _insert
    return query.get_compiler(using=using).execute_sql(returning_fields)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1416, in execute_sql
    cursor.execute(sql, params)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/backends/utils.py", line 98, in execute
    return super().execute(sql, params)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "redacted/.envs/saleor/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.IntegrityError: null value in column "search_document" of relation "account_user" violates not-null constraint
DETAIL:  Failing row contains (2, t<EMAIL_ADDRESS>t, t, redacted..., 2022-05-11 13:24:14.901151+00, null, null, null, null, , , , {}, {}, 00shtkdnxnOr, en, null, null).

System information

Saleor version:

[ ] dev (current main)
[x] 3.0
[ ] 2.11
[ ] 2.10

Operating system:

[ ] Windows
[x] Linux
[ ] MacOS
[ ] Other

The current stable branch is 3.3 and createsuperuser works as expected.


Drift detected in all migrations without changing anything || --create-only is not working

Bug description
When I try to run a new migration in the database, Prisma says that all previous migrations were changed, and asks to reset the database.
When I try to create the migration with --create-only the same thing happens.
npx prisma db pull:
*** WARNING ***

These DateTime fields were enriched with `@updatedAt` information taken from the previous Prisma schema.
- Model "User", field: "updatedAt"

Related
#6505 Drift detected right after introspection (and after applying first migration)
#6579 migrate dev --create-only with empty schema but existing database schema detects drift and warns about deleting all data
#6776 Generate log file with Drift detected info for troubleshooting purpose
#5873 Feature request - Migrate: When Drift Detected -> give more Details than just the rollback script
#5987 Drift detected when nothing has changed
Environment & setup

OS: Windows 10
Database:  PostgreSQL 11.6 (Running with Dokku)
Node.js version: v14.16.0
Prisma version:

prisma               : 2.21.2
@prisma/client       : 2.21.2
Current platform     : windows
Query Engine         : query-engine e421996c87d5f3c8f7eeadd502d4ad402c89464d (at<EMAIL_ADDRESS>Migration Engine     : migration-engine-cli e421996c87d5f3c8f7eeadd502d4ad402c89464d (at<EMAIL_ADDRESS>Introspection Engine : introspection-core e421996c87d5f3c8f7eeadd502d4ad402c89464d (at<EMAIL_ADDRESS>Format Binary        : prisma-fmt e421996c87d5f3c8f7eeadd502d4ad402c89464d (at<EMAIL_ADDRESS>Default Engines Hash : e421996c87d5f3c8f7eeadd502d4ad402c89464d
Studio               : 0.371.0
Preview Features     : orderByRelation, selectRelationCount

Hi @andresribeiro — do you have a reproduction for the problem? It's probably something different from the issues you linked. It would also help if you can share your schema and migrations, or a trimmed down version that exhibits the problem.

@tomhoule What I did in the last migrations was:
(dev database)

yarn prisma migrate dev --name migration_name
-> Prisma warned about all migrations being modified, and asked to reset the database
-> I accepted, and imported the data after this process
yarn prisma migrate deploy
(To apply the last migration)
Then just change the database url to the production database and run
yarn prisma migrate deploy
And everything worked

Now the error appears that only the first migration was modified

Can you share the schema between these change so that we can try a reproduction locally?

@pantharshit00 Sorry, but I'm not allowed to do that. I will try to replicate the error in a new project. Is there any other information that might be helpful?

Unfortunately without a reproduction we can't proceed further in the debugging process :(. Let me know if you are able to provide a minimal reproduction.

@andresribeiro , i had similar issue and it could link to https://github.com/prisma/prisma/issues/7077. Hope this helps

Can you take another look @andresribeiro? In recent versions the file comparison should work much better on Windows.

I'm closing this issue since there is not enough information to reproduce and no more activity.


Review the gRPC-Web protocol proposal

Link to the protocol spec
Please post your review comments here.

@yugui

@mattklein123 have a look

@wenbozhu
@ejona86
@ctiller
For
"Response status encoded as part of the response body
Key-value pairs formatted as HTTP/1.1 headers block (without the empty newline \r\n to terminate the block)"
Why the HTTP format rather than HTTP2 literal format which would be faster to parse. We can also allow binary headers here without specific encoding.

I hope I'm not intruding with my following naive question, since it appears that this issue is only intended for a purely technical discussion:
Will full (Bidi-)streaming be supported? Because it only says this:

support any HTTP/*

and

Pending on whatwg fetch/streams to be finalized and implemented in modern browsers

which sounds like a "no" and that would be kinda disheartening. ☹
If that's correct I'd be very interested in turning this into a "yes", especially since I expect Websockets (which offer that) to be more widely supported right now than fetch/streams might be in 1-2 years.

This looks good to me. This would allow us to get rid of the Envoy bridge filter hack if the protocol was widely supported.

@lhecker There is no plan to support websockets. The biggest issue with WS is that the client library still needs to fall back to HTTP.
Server-streaming is sufficient for most use cases, e.g. when (simpler) unary calls are prohibitively expensive or slow.

@louiscryan Agreed that the http/1.1 encoding of trailers is insufficient or desired. Will fix the spec..

@wenbozhu I'm not sure if I understand this:

The biggest issue with WS is that the client library still needs to fall back to HTTP.

Did you mean that an unary RPC call should directly map to a single HTTP request or are you referring to the fact that Websockets aren't widely supported?

Server-streaming is sufficient for most use cases

So no Bidi-Streaming then? (Sorry for the repeated question.)
I hope I misunderstood but if not I'm sure that many others besides me would find it a bit frustrating if streaming doesn't work in its entirety.

@lhecker

Did you mean that an unary RPC call should directly map to a single HTTP request or are you referring to the fact that Websockets aren't widely supported?

The latter, due to proxies/firewalls etc.

So no Bidi-Streaming then?

Correct.

@wenbozhu

So no Bidi-Streaming then?
Correct.

Thanks! That's just what I wanted to know.
So what's your stance on letting the open source community decide what they want? Up till now I really get the stereotyped feeling of "Google wants this and that's how it's going to be". I hope I'm wrong again. 😞

In fact I wonder why we can't have both by transparently using regular HTTP requests (like in this proposal) wherever we can and Websockets where streaming is required.
I don't believe anyone would be surprised by gRPC requiring Websockets and similar proxy-incompatible technologies for Bidi-streaming where proxy-incompatibility is implied anyways already. But an immature solution for simplicities and compatibilities sake? That just screams that people will build their own solution sooner or later and I don't see why that should be any good or even needed. 😕

@lhecker  Thanks for the feedback!
The grpc-web spec introduces minimum changes to the existing grpc over HTTP/2 protocol. The new spec itself is bidi ready, while the actual bidi support is subject to environment/platform/network constraints (same for the grpc or WebSocket, as you noted).
How about we open a separate issue to discuss how to support bidi streams with grpc-web clients, after this spec has been reviewed and implemented? Your contribution in this work or any future work to support bidi streams is more than welcomed.  @zinuga

How about we open a separate issue to discuss how to support bidi streams with grpc-web clients, after this spec has been reviewed and implemented?

Although I believe not having such a support from the get-go would be a real shame I can kinda understand that. Having a separate issue then would be more than welcomed. Do you mind opening one? 🙂 Again I'm sorry for stirring up this issue so much. I'm definitely looking forward on helping out designing and implementing such an extension. 🙂

Thanks for all the feedback.
Plan to close the issue in a week or so. @yugui (to have a look at this spec soon ;)

LGTM

Thanks for all the feedback.
Implementation of the new spec will happen in grpc/grpc-web
Ping @zinuga if you need early access to grpc-web.

@lhecker
https://github.com/grpc/grpc-web/issues/24  (bidi support discussion)

@wenbozhu where did https://github.com/grpc/grpc-web/ gone?

@rutsky It's an early access project. Just white-listed your user id.

@zinuga could I get read permission to grpc-web?

@zinuga Could I please get early access to grpc-web?

Done. Please check.

@triptec @atishpatel

@wenbozhu I would also like early access please :)

Please provide to me too. Github username - Nishant-Pathak
On Wed, Dec 14, 2016 at 10:12 AM, Matthew Arbesfeld <
<EMAIL_ADDRESS>wrote:

@wenbozhu https://github.com/wenbozhu I would also like early access
please :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/issues/8682#issuecomment-266941195, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAsMUTZaMM-k9L1UfUM4Fa7JKPSXfDNRks5rH3PFgaJpZM4Ksxu8
.

Maybe some sort of request form would be useful. I would also like to review it.

Would love to try out grpc-web too.  Really looking forward for bidi streaming.  Real time updates are kind of expected for interactive apps now a days.

@wenbozhu I'll jump on this bandwagon. I hereby request white listing.

@wenbozhu I love a good bandwagon

@wenbozhu since it seems to be super secret may I also have a look?

@wenbozhu may I have access to grace-web, please !

Done. Feedback is welcome ..

@wenbozhu Thanks for responding but I dont see grpc-web yet.

@wenbozhu I don't see it either.

@wenbozhu I would like to try it.

@wenbozhu I would love to have a look as well, please

@wenbozhu  Add me too, please

@wenbozhu can you add me to pls:)

Could you give me access to the beta too? Thanks. @prithivraj

DONE. We plan to publish the grpc-web rep in Q1.
Thanks for your interests.

Could you please give me beta access ?

@wenbozhu Add me too please

Me too please!

Why not me! pls pls.

Can I get access to the grpc-web spec. Thank you.

DONE

@wenbozhu Please add me as well to whitelist.  Thanks.

@wenbozhu Count me in! Thanks a ton!

@wenbozhu Count me in! Thanks a ton!

Would like access as well. Did fill out some form somewhere for access but haven't heard anything.

DONE

@wenbozhu please add me to whitelist. Thank you very much.

@wenbozhu Could I please be added too? I would be happy to test it. Many thanks.

@wenbozhu please can you add me too? Thank you.

@wenbozhu  Add me pls. Thank you!

@wenbozhu can you add me too? Thank you.

I'm also interested in this. Can you add me? Thank you.

@wenbozhu Kindly add me as well please. Thank you.

@wenbozhu I'm currently evaluating gRPC and would like to take a look at the grpc-web repository. Thanks.

@wenbozhu Could I please be added to the whitelist? Thanks.

@wenbozhu Could you kindly give me access to grpc-web please? Thanks!

DONE

@wenbozhu could you please give me access as well.

@wenbozhu Could you please add me too? Thank you!

@wenbozhu Dito. ;)

@wenbozhu add me too, please. Thank you!

@wenbozhu could you please give me access as well

@zinuga, @wenbozhu I'm also interested in looking into grpc-web! Thanks!

I am interested in grpc-web.

Me too, please

I'm also interested in grpc-web. Could you please add me?

Could you please give me access grpc-web?

can you add me please?

@zinuga could I get read permission to grpc-web?

DONE

@zinuga @wenbozhu Can I have access to grpc-web please?

If possible I would like to have access, too. To test it.

DONE

@wenbozhu May I please also have read-only access to grpc-web?

@wenbozhu Could I have access to grpc-web to test as well? I just got grpc working with Electron, would love to see what's going on with grpc-web.

@wenbozhu would love access to grpc-web also!

@wenbozhu Could I have access to grpc-web ?
Thanks !

DONE
@iheanyi  I am new to Eletron .. does the client run as a chrome app?

@wenbozhu Is it possible to get read access to grpc-web?
Thanks!

@wenbozhu would it be possible to get read access to grpc-web? Thanks!

@wenbozhu Yes it does, at least it runs using V8 to my knowledge. It's pretty dope. But it uses Node.js under the hood when it comes to the gRPC client, which I find to be promising. I am not sure how it'd work with things being redistributed as an application.

@iheanyi re. redistribution; it should work properly as it does on a server. The main thing to consider is disconnect/reconnects as a server will typically be expected to be online all the time, while a desktop app might go offline for a while. This mainly affects streaming endpoints which when onError is called.

@nevi-me Solid point to consider. I'm working on a proof of concept application here  of this entire integration (Go +gRPC + Electron). Your mentioning of streaming makes me want to see if I can tweak this example to be a chatroom example because I think that it would be a good proof of concept for demonstrating "streaming" of between the client and server. But hey, I'm new to this, so I may be mistaken, haha.

@iheanyi just looked at your project, the stuff to really test is streaming, especially bi-directional. Unary calls are sort of a "given" at this point as they're the easier of the 2.
I'm using gRPC on connecting microservices together at work, Mostly between Node.js and Apache Spark (I find PySpark better that ScalaPB). On personal projects I've got client/server instances in Java, Node.js and Python. The Node.js client connects to a constant bi-directional streaming endpoint on the Java side. So I have lifecycle calls on both ends to reconnect when necessary.
On the desktop you won't have the luxury of constantly trying to reconnect as that'll impact CPU consumptions and all the perils that follow. If you wanna continue talking, we can move elsewhere so we don't keep spamming the project.

@wenbozhu I would also love to take a look at how you are going to implement grpc-web.

@wenbozhu would you please add me to grpc-web too.

@wenbozhu Could I have access to grpc-web? We've been using GRPC in production for almost a year across Go, Python, and Node, and I'd love to take a look, provide feedback, etc.

DONE

@wenbozhu could you please add me too? Thanks!

@wenbozhu We did something similar to what you're proposing in, and the proof of concept is in:
https://github.com/mwitkow/grpc-browser-compat
Basically it's a Go proxy + browser polyfill for the NodeJS gRPC transport.
Can you please add me to the grpc-web repo? :) Thanks!

@wenbozhu can i please get added to grpc-web 😄

@wenbozhu can I also get added to grpc-web?

Can I also get early access to the project?

Considering a move to gRPC in production (from a custom serialization scheme/RPC) but not having a web client is a limiting factor. How far off is a grpc-web general release? Is it a web sockets adapter or something else? Is it possible to get read access to grpc-web project?

DONE
@meekapps  It's production ready but we may change the protocol/apis etc.
Read the doc/demo and let us know your feedback.
===
@mwitkow

browser polyfill for the NodeJS gRPC transport

what's the actual transport the polyfill speaks.. . it can't be the actual grpc transport, can it?

I will patentially wait for you to make the repo public. Would love to try it before I write a separate service just for the conversion from grpc to websocket.

@wenbozhu can I also get added to grpc-web please?

Me too please

@wenbozhu me too please? :)

@wenbozhu It isalmost the gRPC transport.
It uses Fetch API (with fallback using chunked-request), the same binary framing of the gRPC transport. The only difference is that trailers (grpc status and desc) are not sent as a HEADER frame but as a DATA frame encoded in a terminator.proto. It's a proof of concept, but seems to work and we'll try it out for some of our services.

@wenbozhu Can I also get early access to the project? Thanks

@wenbozhu early access, please! thanks!

@wenbozhu Can I also have the early access to the project if possible? Thanks

DONE (accesses granted)

@wenbozhu  Can I also get early access to the project? Thanks

@wenbozhu Can I also get early access to grpc-web? Thank you!

@wenbozhu early access, please !

@wenbozhu Can I also get early access to grpc-web? Thank you!

Can I get early access to grpc-web please?

@wenbozhu I know it may be very annoying... could I please have a read access to grpc-web, too?
Thanks.

@wenbozhu , Can I get early access please.. thanks

@wenbozhu , Can I get an early access as well pls? It is very exciting news.

@wenbozhu, Can I get early access please.. thanks

@wenbozhu I would like to test and give feedback on this. Could I please get early access? Thanks!

@wenbozhu I would like to try grpc-web too, can I get early access?

@wenbozhu jumping on this train too. would love early access.

@wenbozhu Can I get early access too, plz?

@wenbozhu Would like to get early access to grpc-web and gice feedback. Thx

@wenbozhu would like to jump on the train, too.
Possible to get some early accesss goodness?

@wenbozhu, my team is evaluating using grpc in prod, but we also need a web component.  If possible, I would like access to grpc-web.  Thanks!

@wenbozhu Could I get early access to the grpc-web as well please? Thanks.

DONE

@wenbozhu Could I also be added to the early access list? Thanks in advance.

@wenbozhu Early access please? Thanks

@wenbozhu I would like to request early access. Thank you.

@wenbozhu May I have read-only access to grpc-web please? Evaluating this for my company. Thank you!

@wenbozhu Hey, would you please add me to the list? thanks.

@wenbozhu Can you add me to list? Thanks

@wenbozhu Please add me to the early-access list too.

Can I please be added as well :)

@wenbozhu I am working on an Electron gRPC app, could I get early access to grpc-web please ?

Second that ^

@wenbozhu please whitelist me too in your next batch. thanks!

Hi, I'd like access to the grpc-web repo as well. Thank you!

This sounds awesome, I'd love early access as well.  Thank you!

@wenbozhu ,
Hi, I am investigating how to handle GRPC-web related issue. Could you please add me to access list?

DONE.

Hi @wenbozhu we are using grpc extensively in our backend and would like to bring it to the browser.  Could you please add me to the early access whitelist?

Hi @wenbozhu , Could you add me to the early access list? Thanks.

@wenbozhu I'd love to get access as well — thanks!

@wenbozhu, access please? (Working a Postgres schema -> gRPC generator, want to test it for gRPC-Web as well).

@wenbozhu I would like to request grpc-web early access. Thanks in advance!

What happened to this form
https://docs.google.com/forms/d/15iRDHoP-VBenc4hWgKn7bk7IirJLgs0uh88nw1vi_Hc/viewform?edit_requested=true

Does it get hacked?
Is it still usable?

I'm a teaching assistant for a distributed systems class that's using GRPC and I'd love to check out the grpc-web repo!

@wenbozhu would like to access to grpc-web too. Thanks

@wenbozhu I'm curious about grpc-web too. Is it possible to get access?

@wenbozhu Please give me access.

@wenbozhu Hi!  Evaluating gRPC, with browser support being a huge factor.  Would appreciate early read access to grpc-web as well.  Thanks in advance!

DONE
@MidnightWonderer  The sign-up form is still alive, to collect general interests in grpc and grpc-web. The fact that this issue thread becomes the defacto sign-up sheet wasn't initially expected :)
Cheers.

@wenbozhu I would like to test grpc-web if possible, thanks in advance

May I have grpc-web early access please ?

@wenbozhu What's the point of not having the repo public and that sign-up form, really? Interest in a gitHub project is easily gaged via stars and forks, no need for forms. What are you afraid of, not doing this work in public? Such pseudo secrecy is surprising / unexpected / worrying...

@wenbozhu Please add me for early access, thanks.

@wenbozhu, whitelist for me as well. I'm with @ddevienne, I say just make it public, even if it's really rough around the edges. I've got your back if someone starts complaining. :)

I am interested in early access as well please.  Thanks.

@wenbozhu I am also interested in early access. Thank you in advance!

@wenbozhu I'm also interested in early access!

@wenbozhu Would love access as well, if possible.
I don't think the lack of openness here is surprising, unexpected, or worrying -- if you're inventing something like a new protocol, the last thing you want is for people to begin adopting it (and relying on its conventions, idiosyncrasies, etc.) before they've been finalized. This is exactly how you end up in the poor situation of having to compromise your product
You can slap hundreds of warnings on something like this saying "EXPERIMENTAL – USE AT YOUR OWN RISK" and people will still find a way to blame you when they have to upgrade and overhaul large parts of their system to make room for an actual released version of the tool.
There's a difference between openness and transparency. How the maintainers choose to conduct themselves in this context is their decision alone. They're being generous enough to do this work -- when they release this work is up to them.

yea, Im wondering too what is the status of grpc-web? I believe it was originally set for a public release as beta for Q1 of 2017, hopefully thats still on-target. At least to reveal the repo for public consumption and feedback to get things moving faster

@wenbozhu could you please give me access to https://github.com/grpc/grpc-web/ as well?

@wenbozhu I am also interested in early access. Thank you!

Would like to take a look and get early access.

DONE.
@zinuga
@ddevienne
@kenkeiter
@pkieltyka
Some background about this whole white-listing thing:
grpc-web was originally developed for internal use (excluding nginx), and we are still going through the internal process before we can make the repo open.
nginx doesn't support http/2 upstream (expected soon), which means any existing nginx users will not be able to use nginx as a reserve-proxy (for load balancing) at the same time.
Our current goal is to make the repo open in early Q2 (as alpha). At the same time, we will ship nginx with LB support.
Thanks for your interests. And your actual feedback is much appreciated too.

I'd appreciate early access.

Please could I get early access? Looking at building a chrome extension.

I'm also interested in early access! Thanks!

@wenbozhu Could I please get early access to grpc-web? Would like to experiment with it on my web application. Thanks!

@wenbozhu I'm interested in testing out early access to grpc-web, could I please be added? Cheers.

I'm interested in trying it out. Can I have pre public release access?

@wenbozhu could I trouble you for early access to grpc-web as well? Thanks!

@wenbozhu early access to grpc-web request Thanks!

@wenbozhu would love access, helping me to support web for https://github.com/lileio

@wenbozhu access, please

I'd appreciate early access.

@wenbozhu early access please

I'm teaching a class on distributed systems with gRPC. Could I get early access please?

DONE.

@wenbozhu is it possible to also have access to grpc-web. Thanks!

@wenbozhu could you please grant early access for me as well? Thank you!

@wenbozhu interested in experimenting as well, thanks!

@wenbozhu can i have the early access? thanks.

@wenbozhu Is it possible to get access to the grpc-web project?

@wenbozhu Would appreciate read access to the grpc-web project, thanks!

@wenbozhu I would like to test grpc-web if possible, thanks in advance!

@wenbozhu Our team (including @freignat91 @ neha-viswanathan) would definitely appreciate access. We are preparing for DockerCon and have a CLI for our gRPC-based backend, but would love to be able to demo a simple web UI as well. And thanks for connecting on LI!

@wenbozhu Would appreciate access to the grpc-web early access, thanks!

DONE

@wenbozhu Would appreciate access to the grpc-web early access, thanks!

@wenbozhu I'm interested as well!

@wenbozhu I'd love to take a look at the grpc-web as well!

@wenbozhu could you give me access to grpc-web as well? Thanks in advance!

Could you please give me access to the repo? I wish to test it for possible production usage in the future.

@wenbozhu very interested in having a look as well, could you give access?

Evaluating grpc for possible prod usage; web component is a must; Can I get early access please?

Thanks for working on this! It's clear that it is in high demand.  Can I get access to the repo as well? Thanks.

@wenbozhu can you please grant me read access as well?

@wenbozhu I'd like to evaluate grpc-web also please!

@wenbozhu can I please have access to the repo?

@wenbozhu  I would also like to get access to evaluate grpc-web for future use. In case the open alpha is close by feel free to ignore this request.

@wenbozhu I wish to take a look at grpc-web as well.

@wenbozhu could you add me as well?

@wenbozhu hi, I'd also like to try out grpc-web, could I get access also?  Thanks!

@wenbozhu I would also like to have access if possible. Thank you!

may I have access as well?

Add me to the access list please!

@wenbozhu could you please give me access as well. Thanks!

@wenbozhu may I have access as well please?

@wenbozhu Looking for early access as well. Please and thank you~!

@wenbozhu I would like to try it too, please.

@wenbozhu I am very interested, may I  please?

I would like to take a look at this as well, if you could please add me to the early access list.
Also a question:
IIUC, browser support for native gRPC is continuing still, although not generally available (e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=422958) and native gRPC should be preferred over the grpc-web protocol in any browsers where it has landed?
So gRPC-Web is intended as a polyfill until gRPC is more fully supported? Is the design that gRPC-Web will use the regular gRPC protocol, if the browser supports it? Or would that be up to us -- to just use the generated Node bindings directly -- if gRPC support is detected?

@wenbozhu Could you give me access? please

@wenbozhu   Have to present a talk on gRPC --> Kindly allow me to get early access to grpc-web.

@birju-s It is very alpha, not sure you would really be wise to go spreading it when the implementation isn't finished.

Sure, I will mention that people on the web working on it. Will not announce about our initiative. Does it makes sense ?  @SonarBeserk

DONE
===
@paulreimer
The eventual goal is to support the native grpc protocol, and make the deployment of grpc-web effortless. The latter includes adding production-level grpc/grpc-web support to popular proxies, frameworks.
What we don't plan to do is to add web-only features to the native grpc protocol, to keep the latter stable/efficient.  Example features include: compression, cors, xss/xsrf, custom message formats, keep-alive etc.

@wenbozhu - can you add me to the early access list for grpc-web, please? Thanks!

@wenbozhu that's great. Now that I've seen the example nginx proxy implementation adding the grpc_pass directive, I can see what you mean about adding support to existing proxies (e.g. this is an example of what an eventual upstream nginx module could look like).
The samples worked great by the way, although I haven't looked much at perf/latency yet.

Another question about the scope of gRPC-Web spec; I see there is an alternate implementation that mentions gRPC-Web here:
https://github.com/improbable-eng/grpc-web
However at a glance, the JS API is not the same (and seems to be different from the Node gRPC JS API as well...), but I assume that it implements the same transport/framing protocol described here. Does this spec (gRPC-Web) aim to provide a standard JS API (e.g. the official gRPC Node API), or is your implementation just a reference design for what a JS API might look like (and the @improbable-eng repo is another possible -- but different -- implementation of the spec).

@wenbozhu Add me too, please

@wenbozhu @zinuga we'd like early access to grpc-web. We may experiment with it in CockroachDB.

@wenbozhu could you give me early access to grpc-web? Thanks! )

@wenbozhu We would like to have early access to grpc-web too if seats are available. We already have a few ionic2 clients. Thanks.

@wenbozhu Could you please grant access to the grpc-web repository? Thanks.

i'd like to request read access too please :)

I would like to request access, too :)

@wenbozhu Please grant me access too. Thanks!

@wenbozhu any update on the progress of grpc-web?
Cheers!

Access for me too please!

@wenbozhu I would like to request access as well. Thanks!

please add me as well, thanks!

DONE
===
@paulreimer
We are committed to supporting the gRPC Node API, including a future TS version. The client library is already used in various products, so we will keep the API as stable as possible, while any future changes will be made backward compatible.
The protocol spec is subject to change, inc. new features. We are actively working on a new version of Nginx gateway with Nginx providing the HTTP/2 support (to backend servers).  In addition to the Nginx gateway, we expect to see other gateways or frameworks to support the grpc-web protocol, e.g. Envoy, go-middleware from Improbable, with full or partial features expected for a gRPC client library.

Hi, please add me as well. Thanks in advance!

@wenbozhu can you add me as well? Thanks in advance!

@wenbozhu I would love a chance to access the repo. Many thanks in advance!

@wenbozhu Please add me too, thanks!

I would like to request access as well. Thanks!

@wenbozhu please add me too, thanks!

Hi! I would like to request access to this as well. I'm trying to promote the use of gRPC in my company and one blocker is use of gRPC in the browser.

@wenbozhu I'm also interested in access. Thanks!

@wenbozhu I'm also interested in access. Thanks!

@wenbozhu May I have access too please? Thanks in advance.

@wenbozhu Me too :)

Me too ...
(It might just be easier to make the repo read only to the world?)

@wenbozhu
Can I have access please?


Add forerunner job status sign and a delay timer for running maple

Add the forerunner job status sign:

!files: the forerunner job is not finished yet. If you type something rightnow, the result is incomplete and uncertain.

*files: the forerunner job is done, now the responose of vim-clap should be fast and deterministic.

The forerunner job is normally super fast and imperceptible unless you have 1 million items, in which case it may take seconds but Vim/NeoVim is still well responsive and you won't feel any typing lag.

Add the delay for running maple.

I proposed serveral solutions for the perfornce improvement in #140. Although I have not tried all of them, the maple extension written in Rust already works very well. If you want to a performant vim-clap, please install Rust and then run :call clap#helper#build_all() in Vim/NeoVim.
Close #140.

I should say, all this flickering looks just bad. Maybe text field should be cleared by new results, not just wiped at the time user changes input? Because that doesn't look as bad as gif in this PR.
Also, this may be more perceptible and smooth if results would be shown line by line with very short delay, not just dropped on the screen all at once. Though I'm not quite sure about it.

The redraw is caused by the job inherently to my knowledge, not the rendering strategy used by vim-clap. Rendering the content linewise does not help.
:Clap blines in this gif does not use the async job, but the built-in filter which is sync, so it does not have the redraw issue.

Hmm, I just tried not clearing the previous content anyway, which seems to help indeed. Can you also check it out, see if it's really helpful? @ImmemorConsultrixContrarie
diff --git a/autoload/clap/impl.vim b/autoload/clap/impl.vim
index ec5c2cd..092a389 100644
--- a/autoload/clap/impl.vim
+++ b/autoload/clap/impl.vim
@@ -201,7 +201,7 @@ function! s:on_typed_async_impl() abort
     return
   endif

-  call g:clap.display.clear()
+  " call g:clap.display.clear()

   let cmd = g:clap.provider.source_async_or_default()

Hmm, I just tried not clearing the previous content anyway, which seems to help indeed. Can you also check it out, see if it's really helpful?

Err... No. I don't use either vim or vim-clap. I just write code blindly, heh.

I just write code blindly

I actually very admire this..., I can't live without these tools.
Anyway I have confirmed that not clearing the outdated result immedidately indeed avoids the visual flicker. Thank you! @ImmemorConsultrixContrarie


Support Custom command module

What would you like to see added to CrabFetch?
I'd love to have some custom modules
What use would this be?
For niche use-cases like rpm-ostree deployments that the wider linux world does not care about, crabfetch could support external modules.
Additional Comments
The module I'd like to convert from fastfetch
{
            "type": "command",
            "key": " 󱋩",
            "text": "/usr/libexec/bazzite-fetch-image"
},

This already links into another plan I already have which is per-module configuration, e.g you could have two displays modules but one only outputs the res, while the other grabs the DRM name (bad example but i suck at examples so deal with it)
TOML allows mixed type arrays for this to be embedded directly into the modules array, but I'm not sure how the config crate I use would let me use it.
Either way, once that's implemented I can start looking into this.

So, if I read this correctly, you want to embed all module settings in the modules array instead of the placeholder strings?

Not quite, moreso you can override the module's settings for a single entry. Example;
modules = [
    "displays",     # Uses the default displays
    {"displays", {
        title = "But this uses a different title, but is the same module"
    }}
]

This way your custom commands can simply be done like so;
modules = [
    {"custom", {
        title = "Custommm",
        exec = "/some/where/myscript.sh"
    }}
]


Top navigation menu RWD issues

There is a problem with top navigation menu on RWD views. For example desktop view (where everything works fine):

For 1240px there is no access to last top menu position System. It is hide under searchbar:

On smallest resolutions another top menu positions are not available (768px as example):

Hi, the theme is desktop only (just like the default theme). The minimum usable screen resolution is 1280px. If you have many other menu items, they are hidden under the search. I know it's a problem.
A quick fix is to edit custom.css
Find .header-right fieldset input.input-text and set:
 width: 120px; min-width: 120px;
I will provide the fix in the next version.


assignment to vector subscripted lhs produces crashes or wrong results

The attached source code was built with

gfortran 6.3 + opencoarrays 1.6.2
gfortran 7.0 (preview) + opencoarrays 1.8.2
and produces wrong results when executed with any number of images. The version build with gfortran -fcoarray=single executes fine, hence I suspect the problem to be in the run time library.

The program checks its output.
For opencoarrays 1.8.2, I get the run time error
Fatal error in MPI_Win_unlock_all: Invalid MPI_Win, error stack:
MPI_Win_unlock_all(127): MPI_Win_unlock_all(win=0x55444f4d) failed
MPI_Win_unlock_all(82).: Invalid MPI_Win
Fatal error in MPI_Win_unlock_all: Invalid MPI_Win, error stack:
MPI_Win_unlock_all(127): MPI_Win_unlock_all(win=0x55444f4d) failed
MPI_Win_unlock_all(82).: Invalid MPI_Win
PMR.zip

Can you please include a little bit more information: MPI implementation, system (OS, arch, virtualized?) and how you built and installed OpenCoarrays (with install log if possible)
Thanks!

Base MPI is Intel MPI 5.1.3
The system is a X86-based shared memory node with SLES11 SP4 as OS.
Here is the command line used to build:
CC=gcc FC="gfortran -I/lrz/sys/intel/impi/<IP_ADDRESS>/intel64/include/gfortran/7.0.0" cmake /lrz/noarch/src/gcc/opencoarrays/opencoarrays-1.8.2 -DBUILD_SHARED_LIBS:BOOL=ON -DCMAKE_INSTALL_PREFIX=${PWD}
The only log file I found was CMakeFiles/CMakeOutput.log which I have attached (adding a .txt extension, to enable the upload).
The example code was compiled with
caf vector_subscript_pos_01.f90
and executed with
cafrun -n 2 ./a.out
CMakeOutput.log.txt
Hope this helps.

Thanks so much @reinh-bader... I think I know of a machine or two that has Intel MPI 5.1.3 if the problem does not show up with MPICH/OpenMPI

Sorry I have been swamped, and have not had a chance to fully investigate yet, but this is still on my radar

No trouble, take your time.

This is still broken as of 0c2dce7bba41a8cda8ac10c53c456458797d0b11 on 12/26/2017
Here is the test case inlined:
program mod_vecsub_01
  implicit none
  integer, parameter :: ndim = 5, vdim = 2
  real :: vec(ndim), res(ndim)[*]
  integer :: idx(vdim)
  integer :: i, me
  logical :: ok[*]

  res = [ (real(i), i=1, ndim) ]
  vec = 0.0
  idx = [ ndim, 1 ]
  ok = .true.
  sync all
  me = this_image()
  vec(idx) = res(1:2)[1]
  if (vec(1) /= 2.0 .or. vec(5) /= 1.0) then
    critical
      ok[1] = .false.
      write(*, *) 'FAIL on image ',me,vec(idx)
    end critical
  end if
  if (me == 1) then
     if (ok) then
       write(*, *) 'OK'
     end if
  end if
end program

That's got nothing to do with opencoarrays. It's a compiler bug. Gfortran is not respecting the indexed addressing for the lhs after the get(). It's trying to do it before.

@vehre awesome, thanks for the response! @rouson we should look and see if this bug has been filed, and if it has not, make sure we file one and post the tracking number here. Perhaps @afanfa or Sorren might be interested in working on a fix for this?

This has been submitted as Bug 83606 on gfortran with the following slightly simplified code:
  integer, parameter :: ndim=5
  integer :: i,vec(ndim)=0, res(ndim)[*]=[ (i, i=1, ndim) ]
  vec([ndim,1]) = res(1:2)[1]
  if (vec(1) /= res(2) .or. vec(ndim) /= res(1)) &
    print *," wrong result ",vec([ndim,1])," on image ",this_image()
end

Fixed on all gcc's from 6 on.

@vehre is the fix in 6.4 and 7.3 or will it be in 6.5 and 7.4?


fix: properly deserialize srs

arkworks expects little-endian order while the ignition files were serialized in big-endian
add a test to verify deserialization

this is fantastic, will get merged as soon as #61 is in

sorry for missing this for so long!

rebased on main


Cluster Mesh Pod to ClusterIP of service in other cluster is not working (pod-to-pod works fine)

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I had anticipated that Cilium ClusterMesh would seamlessly bridge the internal network of ClusterA with that of ClusterB. However, I'm encountering an issue: I can't seem to connect to the ClusterIP of a service located in a different cluster. That said, pod-to-pod communication across clusters is functioning properly, indicating that ClusterMesh is operational to an extent.
My primary requirement is service connectivity, especially through ClusterIP, and I don't need DNS resolution for this. This is crucial because I must communicate with the DNS server in another cluster within the mesh.
I attempted to address this by enabling bpf.lbExternalClusterIP=true, but unfortunately, that didn't resolve the issue.
Could someone shed some light on this? How can I configure Cilium to expose the service CIDR range across all clusters in the mesh?
Cilium Version
v1.14.1
Kernel Version
5.15.0-79-generic
Kubernetes Version
Client Version: v1.28.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.26.7+rke2r1
Sysdump
cilium-sysdump-20230818-023811.zip
Relevant log output
[INFO] <IP_ADDRESS>:37185 - 1992 "A IN nginx.us-west.svc.cluster.local. udp 49 false 512" NOERROR qr,aa,rd 96 0.000111573s
[INFO] <IP_ADDRESS>:37185 - 41670 "AAAA IN nginx.us-west.svc.cluster.local. udp 49 false 512" NOERROR qr,aa,rd 142 0.000293594s
[INFO] <IP_ADDRESS>:37690 - 5686 "AAAA IN nginx.us-west.svc.cluster.local. udp 49 false 512" - - 0 6.001504238s
[ERROR] plugin/errors: 2 nginx.us-west.svc.cluster.local. AAAA: read udp <IP_ADDRESS>:58513-><IP_ADDRESS>:53: i/o timeout
[INFO] <IP_ADDRESS>:37690 - 54331 "A IN nginx.us-west.svc.cluster.local. udp 49 false 512" - - 0 6.001693736s
[ERROR] plugin/errors: 2 nginx.us-west.svc.cluster.local. A: read udp <IP_ADDRESS>:39970-><IP_ADDRESS>:53: i/o timeout
[INFO] <IP_ADDRESS>:37690 - 5686 "AAAA IN nginx.us-west.svc.cluster.local. udp 49 false 512" - - 0 6.002637023s
[INFO] <IP_ADDRESS>:37690 - 54331 "A IN nginx.us-west.svc.cluster.local. udp 49 false 512" - - 0 6.002863163s
[ERROR] plugin/errors: 2 nginx.us-west.svc.cluster.local. A: read udp <IP_ADDRESS>:59484-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2 nginx.us-west.svc.cluster.local. AAAA: read udp <IP_ADDRESS>:43216-><IP_ADDRESS>:53: i/o timeout

Anything else?
No response
Code of Conduct

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

Cc @giorio94

I don't know the details about the CockroachDB deployment, but generally speaking I would say that you can use global services to LB the access to the DB from clients, and the CoreDNS changes you mentioned for the headless services so that replicas can talk with each other.

I managed to at least get the DNS part of my issue working. By configuring CoreDNS itself using the kubernetes plugin:

@belmeopmenieuwesim Can you help me with my situation?
I want to create some deployments with same pods in two kubernetes clusters.
Both of them will have headless service for example "serviceA".
Can I get IPs from both cluster through coredns in cluster one?
In other words, maybe you know how to get IPs from two cluster from one CoreDNS instance?

As an alternative solution, I ended up a creating a global service per statefulset replica. Where the service name is the {hostname}-{region}. Then I used the service label selectors to select based on region={region},statefulset.kubernetes.io/pod-name={hostname}. Unfortunately this only works for statefulsets where the pod names are predictable.


use this module could not pull docker image// 基于此模块部署nginx正向代理拉取docker镜像报错

如题，nginx编译添加这个模块，然后certbot配置HTTPS代理，通过此代理可以访问google/youtube/xvideos.....等，
但配置docker拉取镜像会报错，请教下怎么解决
docker  pull nginx
Using default tag: latest
Error response from daemon: Head "https://registry-1.docker.io/v2/library/nginx/manifests/latest": Get "https://auth.docker.io/token?scope=repository%3Alibrary%2Fnginx%3Apull&service=registry.docker.io": Bad Gateway

Pls provide more details, with your description, we cannot understand what happens, especially minimal step to reproduce.
And you could use tcpdump tool to check if the proxied stream failed when connecting or the real data flow has been proxied to destination.


Build failure with hashable >= 1.3.4

src/Language/REST/Types.hs:72:10: error:
    Duplicate instance declarations:
      instance Hashable a => Hashable (OS.Set a)
        -- Defined at src/Language/REST/Types.hs:72:10
      instance Hashable v => Hashable (OS.Set v)
        -- Defined in ‘hashable-<IP_ADDRESS>:Data.Hashable.Class’
   |
72 | instance Hashable a => Hashable (OS.Set a) where
   |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

src/Language/REST/Types.hs:75:10: error:
    Duplicate instance declarations:
      instance (Hashable a, Hashable b) => Hashable (M.Map a b)
        -- Defined at src/Language/REST/Types.hs:75:10
      instance (Hashable k, Hashable v) => Hashable (M.Map k v)
        -- Defined in ‘hashable-<IP_ADDRESS>:Data.Hashable.Class’
   |
75 | instance (Hashable a, Hashable b) => Hashable (M.Map a b) where
   |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cabal: Failed to build rest-rewrite-0.1.1

https://github.com/zgrannan/rest/commit/5f71ee2131e79363be1d7257248ab2adbbddfffd already added the necessary bound on hashable. Could you publish it as a Hackage revision?

This same error occurred on Hackage, preventing it from building any documentation.

As a Hackage trustee I have created revisions for v0.1 and v0.1.1 that should prevent users from encountering these errors. See

https://hackage.haskell.org/package/rest-rewrite-0.1/revisions/
https://hackage.haskell.org/package/rest-rewrite-0.1.1/revisions/

Thanks for the report, and sorry for the delay. I've uploaded a new version of REST with some additional changes, including increasing the upper bound. New version is here: https://hackage.haskell.org/package/rest-rewrite-0.2.0.


The verifier OS image should be kept up to date

As I understand, the verifier OS image used currently is the RTM version of Server 2012 R2 with no updates applied. In particular, the major Update 1 (KB2919355) is missing. Not only this prevents an increasing number of critical software from installing correctly (such as vcruntime2015), but also it does not, in my opinion, reflect the majority of real-world systems, which do not have Windows Update disabled.
The OS image should be kept reasonably up to date, at least with critical and security updates.

Or perhaps those things should take a dependency on a KB packages.

I'm not sure this would be the right path to take:

there are a LOT of KBs; finding out which ones are actually required will be a ton of work for the maintainer (I speak from experience);
the KB packages themselves would need to be developed and maintained and that would come with its own set of challenges (need to detect if the KB is already installed; need to reliably detect the OS version and verify applicability; some KBs depend on other KBs; some KBs get updated or revoked);
most KBs require a reboot, so this would still not solve the problem of the verifier failing.

there are a LOT of KBs; finding out which ones are actually required will be a ton of work for the maintainer (I speak from experience);

It absolutely can be, but knowing all of the dependencies I think is actually better. You might disagree with this and that's fine.

the KB packages themselves would need to be developed and maintained and that would come with its own set of challenges (need to detect if the KB is already installed; need to reliably detect the OS version and verify applicability; some KBs depend on other KBs; some KBs get updated or revoked);

Yes, but that is all encapsulated in the KB package.

need to detect if the KB is already installed;

A lot of the base level packages tend to do this before going about doing any additional work. Something that would be more of core Chocolatey at some point.

need to reliably detect the OS version and verify applicability;

We have packages that do this well already.
Will become part of core Chocolatey at some point

some KBs depend on other KBs;

Sounds like a perfect use case, we have packages that depend on other packages :D

some KBs get updated or revoked

Interesting, not familiar with the revocation. I'm guessing that happens with an update to the KB or by applying a different update?

most KBs require a reboot, so this would still not solve the problem of the verifier failing.

This is a good point. Windows and its reboots.

Don't get me wrong, I like the idea of KB packages. I just wanted to point out the difficulties.
Revocation - this happens when an update is found to break some systems. MS will remove the update from Windows Update and disable download links. In the future, MS may do one of the following: fix the update and publish it again with the same KB id, publish a new update fixing the problem, abandon the update.
Superseding - some KBs (for example, KB2919355) entirely replace some earlier KBs; computers with the newer KBs installed will not get offered the superseded KBs by Windows Update.
Building KB handling into core Chocolatey is also a cool idea. Right now, however, I'm primarily interested in making the verifier compatible with more packages. Installing KBs on-demand, based on package dependencies, would require handling reboots - a major undertaking, requiring support from Chocolatey. Updating the OS image once every 3-4 months seems easier to do - and packages would be tested in an environment more representative of the real world.

Another thing we've thought about doing is installing Visual Studio 2015 so there is a version to validate vsix packages.

How about preparing and documenting a few versions of the testing environment (e.g.: plain; with Visual Studio; with IIS) and letting packages pick one via a new piece of metadata in nuspec?
In the future, virtual packages could help in selecting the proper environment, eliminating the need for that additional metadata.

This is really interesting as it seems something that AppVeyor has partially captured with their appveyor.yml and their multiple build images (VS2015/VS2013/WMF5/etc). I'm actually doing a lot of my pre-verifier verification over there and so far haven't had too many issues, though I need to test some of the trickier packages I've played with. VS2015.3 definitely comes to mind as one that failed locally when using the Chocolatey Test VM since it was missing the KB2919355 package and I wasn't using my normal Boxstarter method to kick it off.

Windows Server 2012 R2 is slowly approaching its expiration date. Are there plans to switch to a more recent Windows Server (preferably 2019)?
This would immediately improve the verification coverage, because most packages failing today due to KB2919355 (which takes a very long time to install and requires a reboot) would start working.

@jberezanski we have a backlog item to improve this process yes, no firm date on when this will be getting done, but it is very much on the radar.

@gep13 are there any more details around the requirements for updating the image or using the package-verifier without needing the specific environment it currently lives in?
I have some ideas but I'd love to know the plans that @ferventcoder has for how things get verified going forward, whether community packages would run with slightly lower priority than the chocolatey-managed ones or if it is the same across the board but only certain packages get tested on legacy releases of Windows 7 or Server 2012 R2 while most only run on Windows 2019 or Windows 10 (n-1) releases.

@dragon788 There are no details we can share at the moment with you. I am curious as to what you mean by:

using the package-verifier without needing the specific environment it currently lives in?

Can you elaborate on this?

whether community packages would run with slightly lower priority than the chocolatey-managed ones

The Chocolatey Team don't manage packages (although individual team members might be maintainers of packages). I think you're referring to the Chocolatey Core Team Packages? If so, this is not the Chocolatey Team but a team of community members   who manage those packages.
But to answer your question, there are no plans to change priorities.

only certain packages get tested on legacy releases of Windows 7 or Server 2012 R2 while most only run on Windows 2019 or Windows 10 (n-1) releases.

There are no plans just now on changing away from the Package Verifier based operating system of Windows Server 2012 R2.

@dragon788 There are no details we can share at the moment with you.

using the package-verifier without needing the specific environment it currently lives in?

My thinking was possibly running it from a Windows Docker container to test that the Powershell is correct and that the steps all function correctly without having to do a bunch of patching of the base node and installing certain KBs and rebooting to get it to the "right" state.

Can you elaborate on this?

whether community packages would run with slightly lower priority than the chocolatey-managed ones

The Chocolatey Team don't manage packages (although individual team members might be maintainers of packages). I think you're referring to the Chocolatey Core Team Packages? If so, this is not the Chocolatey Team but a team of community members who manage those packages.
But to answer your question, there are no plans to change priorities.

Ah yes, I was thinking of the Core Team packages since those often support the automated update process that can detect new versions and automatically submit and approve updates if they pass the verifier.

only certain packages get tested on legacy releases of Windows 7 or Server 2012 R2 while most only run on Windows 2019 or Windows 10 (n-1) releases.

There are no plans just now on changing away from the Package Verifier based operating system of Windows Server 2012 R2.
Understood. I'm not sure how much longer Microsoft is supporting it with security and system updates, but hopefully other Windows Server versions can get added into a build matrix as they can have fairly different Feature options and patches available as they removing things from the "core" and start making them optional.

My thinking was possibly running it from a Windows Docker container to test that the Powershell is correct and that the steps all function correctly without having to do a bunch of patching of the base node and installing certain KBs and rebooting to get it to the "right" state.

The Package Verifier installs and uninstalls the package which checks all of that. We use Windows Server 2012R2 as we need to use the lowest common denominator on what we support. Using that operating system, and requiring the patches / updates to install on it, means we know we are supporting everybody. It is a great idea to use Windows 10 / Server 2019 to verify packages, but that means they are not guaranteed to run on earlier operating systems we support.
Docker doesn't give us anything above what we currently have other than speed. The Package Verifier queue is rarely an issue so speed isn't something that we gain much from. Using Docker also has its own issues around installing packages that require a GUI or specific Windows functionality that Docker doesn't support.


DTIPrep without X11?

We have been using v1.1.6 of DTIPrep with no problems.  We wanted to try v1.2.4 to see if some outstanding issues had been addressed.  Unfortunately it seems we can't run the newer version without X, even if we are using a protocol file and don't need the GUI.  We are running this under SGE so jobs are submitted to a cluster and X is not available to us.  Any ideas?

Hello,
You should still be able to run DTIPrep without a GUI being shown even with DTIPrep1.2.4. Here is what your command line should look like:
DTIPrep --xmlProtocol ~/my_protocol.xml --DWINrrdFile myDWI.nrrd --outputFolder result/ -c

Thank you -- the -c option was not necessary before (and still says it is default in the help message).  That fixes it.

Thanks for the report. I will update the help.


Merged event-based Hubspot updates into batch update (company snapshot)

Description
Merged event-based Hubspot updates into batch update (company snapshot)
Motivation and Context
We need to get rid of event-based Hubspot updates using "fake" system contact in order to fix https://github.com/Rise-Vision/rise-vision-apps/issues/1332
See https://trello.com/c/KZmsduDo for more details.
How Has This Been Tested?
Tested using BQ console. New fields have already been added to rise-core-log:customerData.company
Release Plan:

As the Submitter, upon requesting review of this pull request, I confirm that the Release Checklist has been completed.
As the Reviewer, upon approving the changes in this PR, I confirm I have reviewed and I agree that the Release Checklist has been completed

Release Checklist Items Skipped?
N/A

@alexey-rise will you also be changing the hubspot-connector companyChanges.sql and associated job?

@tejohnso yes: https://github.com/Rise-Vision/hubspot-connector/pull/88 ,  https://github.com/Rise-Vision/core/pull/571


Added Algorithms book

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
Adds a book on Algorithms.
For resources
Description
A book to help people learn about algorithms.
Why is this valuable (or not)?
People can learn how to program.
How do we know it's really free?
A PDF with the copyright license of being able to be distributed under the authors name.
For book lists, is it a book? For course lists, is it a course? etc.
Tts a book.
Checklist:

[✓] Read our contributing guidelines.
[✓] Search for duplicates.
[✓] Include author(s) and platform where appropriate.
[✓] Put lists in alphabetical order, correct spacing.
[✓] Add needed indications (PDF, access notes, under construction).
[✓] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!


Teach hyper/rustls HTTP backends to resume partial downloads

The curl backend can already do it, but not the two hyper backends. It should just be a matter of threading the parameter through and setting the HTTP Range header.
Test by compiling with --features=rustls and RUSTUP_USE_HYPER / RUSTUP_USE_RUSTLS, and --verbose.
No way to actually write test cases for this though.

I can tackle this. I'm currently trying to figure out how to set that Range header in the Hyper client.


[#71] Added case-sensitive and distinct options to /query endpoint (master)

test suite passed at the bench.
any objections to adding the #'s?

looks good - please # it.

added #


Add changelog.md

It would be good to try to create a changelog kinda like this one: WPCS Changelog
Release notes can be used as a starting point, but a more detailed changelog would be great to have.

Sounds great, we can adopt their way quite easily.
Release naming

version - date (example: 1.0.0 - 01.01.2019)

Release content

Notes (if needed)
Types of changes: Added, Changed, Deprecated , Removed, Fixed

Added to the #133 PR


Device update endpoint

Closes #100
Implements device update endpoint.

I think we should deserialize into a model of the request instead of a dynamic object just to provide clarity on what we are expecting to be sent in the request

I attempted this with the add device endpoint but ran into issues since the Device object uses BSON types for things like Location, LastModified, and Fields. This causes problems for the json deserializer because it doesn't know how to covert these nested objects into BSON documents. Instead I am using the device constructors to populate these fields. The constructors themselves will be able to run checks to make sure the dynamic attributes being passed in are the type we expect.


Make backend datastore pluggable

I would love to find a way to see if vulcand could be used for service discovery and load balancing of tasks on an Apache Mesos cluster running tasks under Aurora.
Aurora publishes task information to (boo) zookeeper using a relatively standard thing twitter invented called Server Sets. It would be great if there was a way to get vulcand to proxy/loadbalance for aurora tasks.
Would this ever be considered, or should I just setup etcd inside mesos (meh) and rig up some machinery to sync state between the two?

Vulcand already has pluggable datastores (called engines), see engine/engine.go for the interface. There's no engine for ZooKeeper/ServerSet though, so that would need to be implemented.


Callback URL error

I'm using React as front end and auth electron. I have a problem after login. My callback URL  is localhost/login. Once I logged in I get a message that says CAN NOT GET /login

For Electron apps you should use popup mode instead of redirect. Can you have a look at the Electron sample? If there continues to be an issue, please open it there as this repo is deprecated.

@chenkie thanks! I made that but browserHistory.replace('/home') is not firing up

@golinmarq did you solved it?

Sorry @b4newz I didn't. I change the login strategy and use another service =(