[REQUEST of INTEGRATION] Parse Props easier

easier variance
I Wrote a function in JS so you could parse variance easier. Now looks like this:
<Button outline>this is a button</Button>
easily integratabtle
util.js:
function cfp(props, config) {   if (!config.variants) throw new Error("[ERROR] Config not complete");   const prop_keys = Object.keys(props);   const result = {};   for (let variant in config.variants) {       for (let prop in config.variants[variant]) {           if (prop_keys.includes(prop)) result[variant] = prop;       }   }   return result; }
finished component:
const Button = React.forwardRef(({ className, variant, size, asChild = false, ...props }, ref) => {   const Comp = asChild ? Slot : "button";   return (     (<Comp       className={cn(buttonVariants({ variant, size, className, ...cfp(props, config) }))}       ref={ref}       {...props}       />)   ); });

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


dispatch_apply Cannot invoke

Hi guys,
I noticed this lib wasn't working anymore. I fixed it this way

public struct Apply {

    // DSL for GCD dispatch_apply()
    //
    // Apply runs a block multiple times, before returning.
    // If you want run the block asynchounusly from the current thread,
    // wrap it in an Async block,
    // e.g. Async.main { Apply.background(3) { ... } }

    public static func userInteractive(iterations: UInt, block: UInt -> ()) {
        dispatch_apply(Int(iterations), GCD.userInteractiveQueue()) { (iteration) -> Void in
            block(UInt(iteration))
            return
        }
    }
    public static func userInitiated(iterations: UInt, block: UInt -> ()) {
        dispatch_apply(Int(iterations), GCD.userInitiatedQueue()) { (iteration) -> Void in
            block(UInt(iteration))
            return
        }
    }
    public static func utility(iterations: UInt, block: UInt -> ()) {
        dispatch_apply(Int(iterations), GCD.utilityQueue()) { (iteration) -> Void in
            block(UInt(iteration))
            return
        }
    }
    public static func background(iterations: UInt, block: UInt -> ()) {
        dispatch_apply(Int(iterations), GCD.backgroundQueue()) { (iteration) -> Void in
            block(UInt(iteration))
            return
        }
    }
    public static func customQueue(iterations: UInt, queue: dispatch_queue_t, block: UInt -> ()) {
        dispatch_apply(Int(iterations), queue) { (iteration) -> Void in
            block(UInt(iteration))
            return
        }
    }
}

Can you be more descriptive as to what doesn't work?
Also, make a pull request for changes instead posting out context code in a comment.

Hi @duemunk, I just want to notify that I might found the problem that @imton faced.
In Xcode 6.3, swift 1.2, Async.swift throw the following error

When I switched out the code with what @imton wrote, it worked.

Everything should work fine in the latest version.

@duemunk Awesome! will update my project with the latest version. Thank you


Input Number jump effect lost

If I remember correctly, the Input Number component had an effect to "move" the number when you clicked on the button. Is that lost? Why?

You could review again because for me it works, I made some changes but I do not know if they influenced that, thank you very much @fergardi


feat(Analyzer): Add a flag to skip excluded scopes in dependency graph

This flag indicates that dependencies in excluded scopes should not be added to the dependency graph. For large projects, this could reduce the size of the dependency graph and the analysis time significantly.

I'd like to just point out https://github.com/oss-review-toolkit/ort/issues/5968. It would be great if this work could fully address that issue.

@fviernau, @sschuberth: This is currently a bit experimental. What I am after is indeed not a full solution for #5968, but only a first step:
We have currently problems with an Android project that frequently crashes our ORT pipeline due to resource exhaustion. In the cases the build runs through, the Analyzer step takes more than 2 hours. The time seems to be consumed mainly when constructing the dependency graph.
I did some tests in which I filtered out test scopes when adding the dependencies to the graph builder - this made the build stable and reduced the time of the Analyzer step to 8 minutes! So, I think, this intermediate step to skip excluded scopes when building the dependency graph is already beneficial - and the implementation should not be too complex.
WDYT?

I did some tests in which I filtered out test scopes when adding the dependencies to the graph builder - this made the build stable and reduced the time of the Analyzer step to 8 minutes!

Feels a bit like cheating 😉 More seriously, I'd really like to understand what exactly is taking so long to construct the dependency graph. Also, I wouldn't expect test scopes to have much more dependencies than "regular" scopes, so why does excluding them make such a big difference?

Feels a bit like cheating wink More seriously, I'd really like to understand what exactly is taking so long to construct the dependency graph. Also, I wouldn't expect test scopes to have much more dependencies than "regular" scopes, so why does excluding them make such a big difference?

Fair points. What we have noticed is that, starting from a certain size, adding further dependencies to the graph becomes rather slow. This is probably due to the fact that the subtrees that need to be compared become larger and larger. For Android projects with their numerous synthetic scopes this seems to be a real issue; so reducing the overall size of the graph by excluding unneeded scopes can actually have a significant effect.
Regarding "cheating": I think, handling scope excludes when constructing the dependency graph needs to be done anyway when implementing full support for exclusions as requested by #5968. So, these changes are not a side-track, but already a partial solution to this goal. I have pushed some more commits, so hopefully it becomes a bit clearer now what I try to achieve.

I have extended the PR to cover the functionality requested by #5968. Still testing whether there is something missing.

It is not clear to me why the commit-lint check fails. Could anybody help me understand what is wrong?

It is not clear to me why the commit-lint check fails. Could anybody help me understand what is wrong?

For some reason it seems to believe graph format natively (see #3825). is a foother line. No idea why. Maybe try omitting the parentheses and using a comma instead, like , see #3825.

It is not clear to me why the commit-lint check fails. Could anybody help me understand what is wrong?

For some reason it seems to believe graph format natively (see #3825). is a foother line. No idea why. Maybe try omitting the parentheses and using a comma instead, like , see #3825.

The comma was not sufficient, obviously it has problems with the '#' character. I now used the reference style.


Opt-out for telemetry

Is there any possibility to disable telemetry? Would be nice to opt-out of this option.

Hey @dol, thanks for opening this issue.
The information that is collected is just to help us fix bugs -- it's pretty innocent. Here's an example log that was collected:
{
  "approxNumTorrents": 4,
  "ip": "<IP_ADDRESS>",
  "localTime": "23:49:23 GMT-0700 (PDT)",
  "playAttempts": {
    "abandoned": 0,
    "error": 0,
    "success": 0,
    "timeout": 0,
    "total": 0
  },
  "screens": [
    {
      "height": 800,
      "scaleFactor": 2,
      "width": 1280
    }
  ],
  "system": {
    "architecture": "x64",
    "numCores": 4,
    "osPlatform": "darwin",
    "osRelease": "Darwin 15.5.0",
    "totalMemoryMB": 8192
  },
  "timestamp": "2016-06-22T06:49:23.595Z",
  "uncaughtErrors": [],
  "userID": "f77a9f09565f26bbcd771dde5c0970d5408af13e59531e08a5b36a8e698c5f14"
}

It's also worth nothing, as @dcposch said in this comment:

We're not collecting personally identifying information
Lots of common software collects this kind of telemetry, with no prompts and often with no prefs setting.
Using a torrent client inherently broadcasts much more sensitive info anyway---to peers, trackers, and the DHT, which is publicly visible. Specifically, which swarms you're part of.

Despite all this, I think a PR that added an option to the preferences to disable this would be fine.

@feross  Thank you for your clarification.
How do you getter the IP? Not found any hint in the code.

Maybe only send /16 for IP address?

The IP isn't collected from the machine, it's added on the server-side. It's an artifact of how TCP connections work -- the server will always see your IP address if you send it an HTTP request ;)
However, the /16 suggestion is pretty good. Maybe there's no need to store the IP since we're already generating a unique ID. We just want to be able to count the total number of users of WebTorrent Desktop.

Since #832 has been closed, should we close this too?

@demoneaux Yep, good call


Remove building and signing XPI file

Since we updated web-ext package, now we should specify addon id in manifest instead of provide it with flag for command. More details here: https://github.com/mozilla/web-ext/issues/3124
As result, we have problem when build a release:
Run mkdir ./AMO
  mkdir ./AMO
  npx web-ext sign --api-key "$AMO_KEY" --api-secret "$AMO_SECRET" --id "{e3fc2d33-09fc-4fe8-9331-d0a464698035}" --source-dir ./firefox --artifacts-dir ./AMO
  mv AMO/*.xpi AMO/linguist.xpi
  shell: /usr/bin/bash -e {0}
  env:
    AMO_KEY: ***
    AMO_SECRET: ***

web-ext sign
Sign the extension so it can be installed in Firefox
Options:
      --version             Show version number  [boolean]
  -s, --source-dir          Web extension source directory.  [string] [required] [default: "/home/runner/work/linguist/linguist/build"]
  -a, --artifacts-dir       Directory where artifacts will be saved.  [string] [required] [default: "/home/runner/work/linguist/linguist/build/web-ext-artifacts"]
  -v, --verbose             Show verbose output  [boolean]
  -i, --ignore-files        A list of glob patterns to define which files should be ignored. (Example: --ignore-files=path/to/first.js path/to/second.js "**/*.log")  [array]
      --no-input            Disable all features that require standard input  [boolean]
  -c, --config              Path to a CommonJS config file to set option defaults  [string]
      --config-discovery    Discover config files in home directory and working directory. Disable with --no-config-discovery.  [boolean] [default: true]
      --amo-base-url        Submission API URL prefix  [string] [required] [default: "https://addons.mozilla.org/api/v5/"]
      --api-key             API key (JWT issuer) from addons.mozilla.org  [string] [required]
      --api-secret          API secret (JWT secret) from addons.mozilla.org  [string] [required]
      --api-proxy           Use a proxy to access the signing API. Example: https://yourproxy:6000  [string]
      --timeout             Number of milliseconds to wait before giving up  [number]
      --approval-timeout    Number of milliseconds to wait for approval before giving up. Set to 0 to disable waiting for approval. Fallback to `timeout` if not set.  [number]
      --channel             The channel for which to sign the addon. Either 'listed' or 'unlisted'.  [string] [required]
      --amo-metadata        Path to a JSON file containing an object with metadata to be passed to the API. See https://addons-server.readthedocs.io/en/latest/topics/api/addons.html for details.  [string]
      --upload-source-code  Path to an archive file containing human readable source code of this submission, if the code in --source-dir has been processed to make it unreadable. See https://extensionworkshop.com/documentation/publish/source-code-submission/ for details.  [string]
  -h, --help                Show help  [boolean]
Unknown argument: id
Error: Process completed with exit code 1.

As temporary solution, we may remove building XPI file for serve a standalone addon.
Later we may add a specific target firefox-standalone, that will patch manifest file and add "browser_specific_settings": {"gecko": {"id": "{e3fc2d33-09fc-4fe8-9331-d0a464698035}"}}

Or, we may introduce additional target instead

Will XPI files return to releases? I was wanting to test v6 without having to wait for the AMO release, but am not particularly thrilled about loading it unpacked.

Will XPI files return to releases? I was wanting to test v6 without having to wait for the AMO release, but am not particularly thrilled about loading it unpacked.

Actually we still build XPI, PR https://github.com/translate-tools/linguist/pull/448 just add overrides for manifest of standalone version.
File did not been present in release, because problems in CI pipeline. Now i've attached XPI file on release page


fix: update Podfile.lock

Maybe this will help resolve the error, otherwise I might want to try and add another package or remove one.

pod deintegrate && flutter clean && flutter pub get && pod install && pod repo update && pod update


Pub/Sub doesn't take namespace into account

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
Latest from the unstable branch, Fedora 35.
Minimal reproduce step
Run kvrocks with additional two namespaces, e.g.
namespace.one password4one
namespace.two password4two

Run two redisc-cli instances, and connect to kvrocks.
Switch to the first namespace via the first redis-cli: auth password4one.
Switch to the second namespace via the second redis-cli: auth password4two.
Execute subscribe channel via the second redisc-cli.
Execute publish channel not-for-second-ns via the first redis-cli.
What did you expect to see?
The message, published in namespace.one should not be received by the subscribers in namespace.two, even if the channel names are the same.
What did you see instead?
Subscribers from namespace.two received the message, published in namespace.one.
For Pub/Sub namespaces aren't isolated.
Anything Else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I'm also wondering if any users need this feature

I think this is ok, so does redis.

I think this is ok, so does redis.

Yes, this behavior is matched the Redis if we regard the namespace as the Redis DB. So I'm wondering if any users need this feature.

Yes, this behavior is matched the Redis if we regard the namespace as the Redis DB. So I'm wondering if any users need this feature.

If someone needs this feature, I think they can just use stream.

Yes, this behavior is matched the Redis if we regard the namespace as the Redis DB. So I'm wondering if any users need this feature.

If someone needs this feature, I think they can just use stream.

There's a bit different between stream and pubsub. For the stream, it likes most message queue system, all message can be saw before the retention ttl but the pubsub is fire and forget.

There's a bit different between stream and pubsub. For the stream, it likes most message queue system, all message can be saw before the retention ttl but the pubsub is fire and forget.

Yes, I mean that if someone needs this feature, they can use stream instead in the current situation. In fact, many people who directly use Redis also use stream instead of pubsub to avoid the disadvantages of pubsub. I think the Redis aligned by kvrocks is enough.


Build is failing at remotes::install_github()

The build fails because it can't download the file from Github using remotes::install_github(). I suspect this is related to r-lib/remotes#641. This is weird, because the URL opens fine in a browser etc.
Quitting from lines 15-52 (itraxBook.Rmd)
Error: Error: Failed to install 'unknown package' from GitHub:
  cannot open URL 'https://api.github.com/repos/tombishop1/itraxR/contents/DESCRIPTION?ref=HEAD'

Faced with the same problem locally, I set options(download.file.method = "libcurl"), whereas before it was set to "wininet". However, when I later tried the same in a new session using the default values, it worked fine, so I suspect this may have been a red-herring (see below for the output of the local run).
> remotes::install_github("tombishop1/itraxR")
Downloading GitHub repo tombishop1/itraxR@HEAD
√  checking for file 'C:\Users\tombi\AppData\Local\Temp\RtmpC8Uexh\remotes378c1ed41b25\tombishop1-itraxR-d0e0b78/DESCRIPTION' ...
-  preparing 'itraxR': (401ms)
√  checking DESCRIPTION meta-information ...
-  checking for LF line-endings in source and make files and shell scripts
-  checking for empty or unneeded directories
-  building 'itraxR_1.4.tar.gz'

Installing package into ‘C:/Users/tombi/Documents/R/win-library/4.1’
(as ‘lib’ is unspecified)
* installing *source* package 'itraxR' ...
** using staged installation
** R
** data
*** moving datasets to lazyload DB
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
  converting help for package 'itraxR'
    finding HTML links ... done
    CD166_19_S1                             html
    itrax_correlation                       html
    itrax_image                             html
    itrax_import                            html
    itrax_join                              html
    itrax_meta                              html
    itrax_ordination                        html
    itrax_qspecsettings                     html
    itrax_radiograph                        html
    itrax_reduce                            html
    itrax_restspectra                       html
    itrax_section                           html
    itrax_spectra                           html
    multivariate_import                     html
** building package indices
** testing if installed package can be loaded from temporary location
*** arch - i386
*** arch - x64
** testing if installed package can be loaded from final location
*** arch - i386
*** arch - x64
** testing if installed package keeps a record of temporary installation path
* DONE (itraxR)
> getOption("download.file.method")
[1] "wininet"

Thinking about this, I wonder if it has something to do with the changes in 4.1.1 - there are platform specific changes to methods for download.file. I think I can pass method =  in remotes::install_github(), so the answer might be to define a method here. Perhaps options(download.file.method = "libcurl") or method = "curl" is appropriate for macOS?

OK, it was actually a PAT thing. Seems to be sorted now.


Forward bot messages received from /tracker/events route to output channel

Proposed changes:

Events posted to /conversations/<conversation_id>/tracker/events do not trigger a new prediction, and that is fine. But a use case for this route is not currently supported: it could be used to push bot messages back to an output channel for the user to see. This is a minimal PR to add this feature. It adds the output_channel query param to the route.

Status (please check what you already did):

[ ] added some tests for the functionality
[x] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

Thanks for submitting a pull request 🚀 @Ghostvv will take a look at it as soon as possible ✨

Hi @pheel, could you give a bit more context on why you feel this change is needed? Do you need this in order to get something else working?

@federicotdn This need came up in the context of working out a handoff/handover flow: NLG is put on pause, but the user still needs to receive messages as if they were the result of actions. The most convenient way I found to do this is to append those replies to the tracker in the form of BotUttered events using the /tracker/events route.
To me the use case for where BotUttered events are forwarded to output is more obvious than the use case where they aren't, but on the face of it both seem legitimate?

Hey @pheel, thanks for the explanation. I'm trying to think, just in case, if there's already an existing way of achieving what you need. In theory, you could use the POST /conversations/<id>/execute endpoint to execute an action (which could be a bot response with the desired text defined in the domain), which will also send the events into the output channel. Would that work for you or do you need a more fine-grained control?

The problem with using /execute is that the text content of the BotUttered event is by definition not predictable in a handoff scenario. During a handoff, both BotUttered and UserUttered messages come from humans. I might have missed something researching this, but I did not find an example of a design allowing true human-to-human conversations through the tracker. Thanks.

@rasabot ???


Endless axis value is not accepted.

Hello,
When creating an endless axis, I was unable to enter the required value (-1e99).
Dokumentation:
linuxcnc.org/docs/2.7/html/config/ini-config.html
Zitat:
MIN_LIMIT = -1000 - The minimum limit for axis motion, in machine units. When this limit is reached, the controller aborts axis motion. The axis must be homed before MIN_LIMIT is in force. For a rotary axis with unlimited rotation having no MIN_LIMIT for that axis in the [AXIS_n] section then the value -1e99 is used.

Gruß Mücke

This was fixed yesterday
https://github.com/jethornton/mesact/commit/ab9589
JT

Then I was too slow.
How can I transfer the new version?

If you downloaded a deb file and installed that simply from the mesact download menu download the deb and reinstall. I don't create a new version for every small bug fix. I do update the build date.
JT


[monitor] generated_samples are in wrong folder

related python config: https://github.com/Azure/azure-rest-api-specs/pull/25074

/check-enforcer override


Struggling to send a Dictionary in Swift down EDO layer

I should move this to the EDO project but starting here in case its an implementation detail.
Seeing an issue trying to pass a dictionary from Swift of any type: [String:String] Dictionary<String, String>, NSDictionary down the EDO layer to the host app.
If I pass an Array down of [String] this seems to be work fine.
Receiving exception:
19.93s Assertion Failure: EDOObject+Invocation.m:95: failed: caught "NSInternalInconsistencyException", "Not supported

Which seems to indicate the object cannot be translated.
Test method
    func testEDODict() {
        var testProtocol: DictTestProtocol {
            return unsafeBitCast(
                GREYHostApplicationDistantObject.sharedInstance,
                to: DictTestProtocol .self)
        }
        let dict:[String:String] = ["TestKey": "TestValue", "ATestKey": "ATestValue"]
        testProtocol.testEDODict(data: dict) // Exception here
    }

Protocol
@objc
protocol DictTestProtocol {
    func testEDODict(data: [String:String]) -> Void
}

Implementation
extension GREYHostApplicationDistantObject: DictTestProtocol {
    func testEDODict(data: [String:String]) -> Void {
        for key in data {
            print(key)
        }
    }
}

Resolution:
Add this to your swift bridging header for both the test and edo bundle:
#import "Service/Sources/NSObject+EDOValueObject.h"

Convert the dict to a NSObject type (NSDictionary) and use the NSObject extention from EDOValueObject "passByValue".
data: (dict as NSDictionary).passByValue

Your test method should now look like this:
    func testEDODict() {
        var testProtocol: DictTestProtocol {
            return unsafeBitCast(
                GREYHostApplicationDistantObject.sharedInstance,
                to: DictTestProtocol .self)
        }
        let dict:[String:String] = ["TestKey": "TestValue", "ATestKey": "ATestValue"]
        testProtocol.testEDODict(data: (dict as NSDictionary).passByValue)
    }

The protocol should now use NSDictionary:
@objc
protocol DictTestProtocol {
    func testEDODict(data: [String:String]) -> Void
}

The implementation can then re-cast as needed:
extension GREYHostApplicationDistantObject: DictTestProtocol {
    func testEDODict(data: NSDictionary) -> Void {
        for (key, value) in (data as! [String:String]) {
            print(key)
        }
    }
}

Note: The same holds true passing back a dictionary up. It must be a NSDictionary and not a Swift Dictionary, and you must use passByValue.
For more details, this is documented for Objective-C here: https://github.com/google/eDistantObject/blob/master/docs/detail.md

out of curiosity: will this work?
let dict:[NSString:NSString] = [].
testProtocol.testEDODict(data: (dict as NSDictionary))


devdocs-desktop: init at 0.7.1

Also added ymarkus to maintainers list.

Motivation for this change
Add a devdocs-desktop package
Things done

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

[x] 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"
[x] 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.

Had to add a small gtk fix to fix a minor bug I just noticed

Rebase: Changed homepage from broken url to git repo.

dont have much experience with appimageTools packaging so I am hesitant to merge but it works well. I didn't know the tool and it will replace zeal for sure. By any change, do you know if it is possible to consult hackage (haskell website) with it (couldn't find the info)

Yes, looks like they do have Haskell in their collection. To be more precise, Haskell 7 & 8.


fix(FocusZone|FocusTrapZone): correctly define current document object of the components

Fixes https://github.com/stardust-ui/react/issues/1817
By replacing document to getDocument from focusUtilities we're making sure that the right document object will be used for correct FocusZone and FocusTrapZone function.
getDocument is called with node elements this._root._current and implementation looks like this:
export function getDocument(rootElement?: Element | null): Document | undefined {
  return (rootElement && rootElement.ownerDocument) || document
}

Looks good to me

Yep change makes sense. If this is a bug in the other copy, we need to merge the two asap to stop the branching 😀 or fix the bug in both places.

@davezuko totally agree on keeping consistency between copies. We encountered the bug when had a case of opening another window with components through window.open, so when document.active was used, it would use the wrong (initial) document object from the parent window. I'll create an issue on Fabric side.


add kubeflow step

Missing the section on installing the kubeflow mpi-operator to execute the NCCL tests
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Since the conflict is very straightforward, I resolve the conflicts and merge the PR.


Create Preset Themes

Create the Preset Theme component:

It dynamically changes depending on the hex colors passed as props.
It is associated with a hardcoded theme
It can be selected

Can I take this?

@macanrox Here you go! Let me know if you have any question :)

Hello, here's an update! :raised_hands:
The changes can be viewed over at my forked repo
Also let me know if there are any changes you'd like me to make. I'll be waiting on making the PR until I generate unit tests.
To Do

[x] Create Preset Theme component

[x] It dynamically changes depending on the hex colors passed as props.
[x] It is associated with a hardcoded theme
[x] It can be selected

[ ] Create unit tests

About the Preset Theme component

Created data for the hardcoded themes in data/preset-themes.js
Images preview of the themes are in public/images
The colors are stored in a state as an array in PageContainer.js and get updated whenever PresetThemes.js is selected

@macanrox Thank you for contributing !!! 🎉


validation-method is dns-generic.

https://github.com/open-mpic/open-mpic-specification/blob/b04af663e493300cad8dab61400d6bd56ac69129/openapi.yaml#L244
https://github.com/open-mpic/aws-lambda-python/blob/fd5c4d4e8fb62e24cf269697f9f7d4d1c8a9d51a/lambda_validator/lambda_function.py#L54
I found an issue, as spec describes it should be:
name_to_resolve = f'{challenge_prefix}.{identifier}' if len(challenge_prefix) > 0 else f'{identifier}.'
And controller function could not handle error response.

I pushed a fix for this in 3ecfa02
I used the line you proposed with a small change: I removed the trailing .
so
else f'{identifier}.' -> else f'{identifier}'
This was for consistency because none of the other identifier values have a trailing . added when passed to the DNS library. If there is a reason to add the trailing dot here or elsewhere, let me know.

Also, controller currently does not have proper error handling for errors originated by remote perspectives. Thus, any error generated by a remote perspective will propagate up and cause a 500 Internal Server Error. This will be fixed shortly.


[FLINK-35566] Promote TypeSerializer from PublicEvolving to Public

What is the purpose of the change
Promote TypeSerializer from PublicEvolving to Public
Brief change log
Promote TypeSerializer interfaces
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

Thanks for the PR.
If we want to also upgrade TypeSerializerSnapshot to Public, it's better to do this after removing related deprecated methods in 2.0.

So in this PR, it's better not to touch TypeSerializerSnapshot, right?

Thanks for the PR. If we want to also upgrade TypeSerializerSnapshot to Public, it's better to do this after removing related deprecated methods in 2.0.

So in this PR, it's better not to touch TypeSerializerSnapshot, right?
BTW, what about TypeSerializerSchemaCompatibility?

Thanks for the PR. If we want to also upgrade TypeSerializerSnapshot to Public, it's better to do this after removing related deprecated methods in 2.0.

So in this PR, it's better not to touch TypeSerializerSnapshot, right?
BTW, what about TypeSerializerSchemaCompatibility?

IMO,  It's better to promote these classes together since users usually use them together.
So maybe let's remove related deprecated methods firstly.
@JingGe WDYT?

IMO, It's better to promote these classes together since users usually use them together. So maybe let's remove related deprecated methods firstly. @JingGe WDYT?

@JingGe May I ask what is your opinion?

IMO, It's better to promote these classes together since users usually use them together. So maybe let's remove related deprecated methods firstly. @JingGe WDYT?

@JingGe May I ask what is your opinion?

Related deprecated methods have been removed in https://github.com/apache/flink/pull/25384
I think we could go ahead.

Related deprecated methods have been removed in #25384 I think we could go ahead.

OK.

IMO, It's better to promote these classes together since users usually use them together. So maybe let's remove related deprecated methods firstly. @JingGe WDYT?

@JingGe May I ask what is your opinion?

Related deprecated methods have been removed in #25384 I think we could go ahead.

OK.

@flinkbot run azure


fix header problem(can't find cstdint) on OSX platform

I encounter a problem when compile some node addon on its 4.1.2 version. The compiler will throw a "cstdint" header not found error. This won't show up when doing the normal compilation. And it seems only happened on Mac OS platform, for the cstdint header usually locate in /usr/include/c++/4.x.x/tr1  folder but still depends. So I just changed the macro and force it using stdint.h on OSX platform.

Does this help without patch?
CXXGLAGS="-stdlib=libc++" cmake <usual args>

Nope, the problem comes from node-gyp's compiler, I tried to add similar command but doesn't work.

:+1:


Orthogonal comparison sampling

Is your feature request related to a problem? Please describe.
In Vulkan/SPIR-V, for every type of sampling operation you can do, there exists a corresponding comparison sample operation. Shader model 6.7's "advanced texture ops" improved the situation by adding explicit-LOD comparison sampling, but D3D/DXIL is still missing:

Bias
Gradient
Mip level computation (must be passed a non-comparison sampler)

Describe the solution you'd like
I'd like to see shader model 6.8 add new intrinsics for these operations, or relax restrictions (e.g. mip level computation simply fails DXIL validation).
Describe alternatives you've considered
The only alternative I can see would be to add a non-comparison sampler to the shader for every comparison sampler, and to rewrite the shader for bias to explicitly compute derivatives, and then for bias/gradient to explicitly compute a mip level (using the non-comparison sampler), and then do an explicit-LOD sample. This is... ugly.
Additional context
This is needed for VulkanOn12 aka Dozen.

Resolved by #147


Latest version (2.1.0) does not work in IE 10

After creating a new app using aurelia-cli and then updating aurelia-binding to the latest version (2.1.0), the app fails to run on IE 10. The error is shown below:

Looks like some calls to Array.find() were added in the latest version, but aurelia-polyfills does not contain a polyfill for this function.

Thanks for reporting this!
@EisenbergEffect  this is fixed by https://github.com/aurelia/binding/pull/698

Release coming in just a few minutes.


Default fee 0.0002 TAZ

On testnet the fee defaults to 0.0002. I'm guessing there is a dev fee in this which is fine but it shouldn't be hidden like this and should be a separate input as using the standard 0.0001 fee is strongly encouraged (as fees are visible on the blockchain). I think this layout confuses the matter.

Tested on v0.1.9

Fixed. In v0.2.0 release
Commit: d6ce1f8b278066fa323be5b08ce8060a655c79b2

Awesome, that's much clearer. Just in case you haven't seen it the Zcash Foundation are looking for a cross-platform GUI wallet developer https://github.com/ZcashFoundation/ZcashFoundation/issues/73

Thanks for the tip. I reached out to the foundation on the issue.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, October 22, 2018 4:16 PM, Gareth Davies<EMAIL_ADDRESS>wrote:

Awesome, that's much clearer. Just in case you haven't seen it the Zcash Foundation are looking for a cross-platform GUI wallet developer ZcashFoundation/ZcashFoundation#73
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Add some missing cfi frame info in aesni-sha and sha-x86_64.pl

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Merged to master and 1.1.1
Thanks!


Commercial usage related

Thanks for your gorgeous work, but can RIFE with its pretrained models be deployed in commercial scenario?

Commercial behavior is allowed under the MIT license.

Thanks!


Add golang 1.16 support?

Is there a plan to support golang 1.16, or is there any way I can compile successfully now?

Support for Go 1.16 has been added in #37 and it is ready for testing.


Context has no highlighting when first opening Neovim

Description
If I open Neovim in a way that the context window is already open, then the context content has no highlighting until the context window is closed at least once.
Neovim version
v0.10.0-dev-2257+g302fa5f7d
Expected behavior
For the context window to always have the expected highlighting.
Actual behavior
This is what it looks like the first time:

Minimal config
local plugins = {
  ts = "https://github.com/nvim-treesitter/nvim-treesitter",
  ts_context = "https://github.com/nvim-treesitter/nvim-treesitter-context",
  tokyo_night = "https://github.com/folke/tokyonight.nvim",
}

for name, url in pairs(plugins) do
  local install_path = "nvim_issue/" .. name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { "git", "clone", "--depth=1", url, install_path }
  end
  vim.o.runtimepath = install_path .. "," .. vim.o.runtimepath
end

vim.cmd [[colorscheme tokyonight]]

require("tokyonight").setup()
require("nvim-treesitter.configs").setup { ensure_installed = { "lua" } }
require("treesitter-context").setup()

local foo = {
  bar = {
    ensure_installed = {
      "bash",
      "c",
      "cpp",
      "fish",
      "gitcommit",
      "javascript",
      "json",
      "json5",
      "jsonc",
      "lua",
      "markdown",
      "markdown_inline",
      "python",
      "query",
      "regex",
      "rust",
      "scss",
      "toml",
      "typescript",
      "vim",
      "vimdoc",
      "bash",
      "c",
      "cpp",
      "fish",
      "gitcommit",
      "javascript",
      "json",
      "json5",
      "jsonc",
      "lua",
      "markdown",
      "markdown_inline",
      "python",
      "query",
      "regex",
      "rust",
      "scss",
      "toml",
      "typescript",
      "vim",
      "vimdoc",
    },
  },
}

Steps to reproduce

Include the above configuration file in minimal.lua.
Open Neovim with nvim --clean -u minimal.lua minimal.lua -c "normal50Gzz".
Notice how the context window has no colorization. Then run gg50Gzz and notice how the context window is now highlighted.

I have run into a similar issue in longer python files when I scroll up into a method in a longer class. I think the cause is the upstream tree-sitter updates, which saves some work for off screen text in certain cases (based on my understanding).
Your problem is probably manageable by this plugin, but I think it will be hard to avoid some problems with the current tree-sitter code upstream. (Though I might misunderstand something here. This problem doesn't annoy me too much usually, so I haven't really looked into it.)

I have run into a similar issue in longer python files when I scroll up into a method in a longer class. I think the cause is the upstream tree-sitter updates, which saves some work for off screen text in certain cases (based on my understanding).
Your problem is probably manageable by this plugin, but I think it will be hard to avoid some problems with the current tree-sitter code upstream. (Though I might misunderstand something here. This problem doesn't annoy me too much usually, so I haven't really looked into it.)

Unlikely. These updates only apply to injections.
I think the issue is that nvim-treesitter-context is running before the TreesitterHighlighter has been setup. Not sure for certain though.
I've raised #392 which simply avoids using vim.treesitter.highlighter and instead we use our own queries. Let me know if that resolves things.

I had to revert the fix due to #410, but I was unable to reproduce the issue with the minimal config above.
@MariaSolOs Can you confirm if you're still seeing the issue with the latest commit?

@romgrk Yes, I can still reproduce it.
Here's a video:
https://github.com/nvim-treesitter/nvim-treesitter-context/assets/62502207/5b9f253b-633e-4b8e-ab40-5a3bb8dbee73


Add syntax highlighting

@HO-COOH : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Update the README.md

suggest some formats and ideas to increase the visibility of Opensourcebuddy
sample link https://gist.github.com/PurpleBooth/109311bb0361f32d87a2

Hey please assign this task to me I would like to contribute

Hello On the readme I am adding a contributors section everyone should add their respective id's through pull request okay

Done :)

HI @cleverhare , thanks for the contributions so far , you can attach the related commit id here so that we can get to track them during the conversation.

we also have a contribute.md now, can we make the README more of like link.

Okay

and you mean the readme should be like that link ?


Failed when running command with Wordpress

php version 7.1.11
squizlabs/php_codesniffer (2.9.0)
I install vai composer with squizlabs/php_codesniffer (2.9.0)
Then I run configure point to install path and path to wpcs
And I run command phpcs --standard=WordPress wp-content/themes/kymenlaaksonjate/template-service.php
Then got error below
PHP Fatal error:  Interface 'PHP_CodeSniffer_Sniff' not found in /home/sakona/dev/wpcs/WordPress/Sniff.php on line 36
PHP Stack trace:
PHP   1. {main}() /usr/local/bin/phpcs:0
PHP   2. PHP_CodeSniffer\Runner->runPHPCS() /usr/local/bin/phpcs:6
PHP   3. PHP_CodeSniffer\Runner->init() phar:///usr/local/bin/phpcs/src/Runner.php:2
PHP   4. PHP_CodeSniffer\Ruleset->__construct() phar:///usr/local/bin/phpcs/src/Runner.php:2
PHP   5. PHP_CodeSniffer\Ruleset->registerSniffs() phar:///usr/local/bin/phpcs/src/Ruleset.php:2
PHP   6. PHP_CodeSniffer\Autoload::loadFile() phar:///usr/local/bin/phpcs/src/Ruleset.php:2
PHP   7. include() phar:///usr/local/bin/phpcs/autoload.php:2
PHP   8. spl_autoload_call() /home/sakona/dev/wpcs/WordPress/Sniffs/DB/RestrictedClassesSniff.php:29
PHP   9. PHP_CodeSniffer\Autoload::load() /home/sakona/dev/wpcs/WordPress/Sniffs/DB/RestrictedClassesSniff.php:29
PHP  10. PHP_CodeSniffer\Autoload::loadFile() phar:///usr/local/bin/phpcs/autoload.php:2
PHP  11. include() phar:///usr/local/bin/phpcs/autoload.php:2
PHP  12. spl_autoload_call() /home/sakona/dev/wpcs/WordPress/AbstractClassRestrictionsSniff.php:21
PHP  13. PHP_CodeSniffer\Autoload::load() /home/sakona/dev/wpcs/WordPress/AbstractClassRestrictionsSniff.php:21
PHP  14. PHP_CodeSniffer\Autoload::loadFile() phar:///usr/local/bin/phpcs/autoload.php:2
PHP  15. include() phar:///usr/local/bin/phpcs/autoload.php:2
PHP  16. spl_autoload_call() /home/sakona/dev/wpcs/WordPress/AbstractFunctionRestrictionsSniff.php:27
PHP  17. PHP_CodeSniffer\Autoload::load() /home/sakona/dev/wpcs/WordPress/AbstractFunctionRestrictionsSniff.php:27
PHP  18. PHP_CodeSniffer\Autoload::loadFile() phar:///usr/local/bin/phpcs/autoload.php:2
PHP  19. include() phar:///usr/local/bin/phpcs/autoload.php:2

Please get help on this.
Thanks,

What version of WPCS are you using ?

I follow this command to install wpcs composer create-project wp-coding-standards/wpcs --no-dev

@sakonachhoeurng The information you provide contradicts each other, so I'm not sure how I can help.
In your original message you say you are using PHPCS 2.9.0, but the stack trace shows that you are in actual fact using PHPCS 3.x.
The screenshot from your Composer install also shows it installing PHPCS 3.1.1.
You then state that you expect you are using the latest WPCS and the Composer install screenshot confirms that, but the error stack trace is typical for WPCS < 0.13.0.
Please run the below commands and post the output here to see if we can get some clarity.

Let's confirm which version of PHPCS you are in actual fact using: phpcs -v
There may be more than one install one your system and it might be that the install being used is not the install as pulled in by Composer.
Let's see what version of WPCS you are using: phpcs -e --standard=WordPress.
Based on the sniff list this returns we should be able to get a good idea of what version of WPCS is actually being used.

@sakonachhoeurng Check if using vendor/bin/phpcs differs from phpcs.

my phpcs is /usr/local/bin/phpcs

@jrfnl, thanks for explaining.
my phpcs is 3.00.
You can check on screenshot

Therefore, I install squizelab on my project with composer.json I install it 2.9, but when I run command composer create-project wp-coding-standards/wpcs --no-dev
Then it also install version 3.0.0

Hi @jrfnl , @GaryJones
From now, I install wpcs to my project directory, then vendor/bin/phpcs version is 2.9.0,
but still got error when I run phpcs -e --standard=WordPress

There is no version of WPCS which is compatible with PHPCS 3.0.0 as that version contained quite some bugs still.
You either need 2.9.0/2.9.1 or version 3.0.2 or higher. For the best results, always use an up-to-date version of PHPCS, which would currently be version 3.1.1.

but still got error when I run phpcs -e --standard=WordPress

What error do you get when you run phpcs -e --standard=WordPress ?
And can you try to run phpcs -i to see if the WPCS standards are registered correctly in the install you are using ?
You'll probably will need to run both commands as vendor/bin/phpcs.

Hey guide,
When I try my step

Install wpcs to my project directory
Make vendor/bin/phpcs configure with vendor/bin/phpcs --config-set installed_paths wpcs
Then run vendor/bin/phpcs -e --standard=Wordpress that list all standard contain sniff
Run vendor/bin/phpcs -w --standard=Wordpress wp-content/themes/kymenlaaksonjate/template-service.php that work for me now.
That work for me,
Cheers,

Great to hear! Does that mean we can close the issue ?

I think the best way for installation, you should follow my step as installation, I try to follow your installation step, but do not understand and not so clear.
You can close the ticket.

Hi @jrfnl ,
I also have question to phpcs version 2.9 and 3.0.x what different checkstyle error.
I test that is different fro 2.9 and 3.x

I also have question to phpcs version 2.9 and 3.0.x what different checkstyle error.
I test that is different fro 2.9 and 3.x

@sakonachhoeurng What is your question ? This is a bit too vague for me to figure out what you mean ?

I mean when I run checkstyle from 2.9 that saw errors, but when I run with 3.x that error in 2.9 not exist anymore.

Without more detailed information about the errors you saw and the code this applied to, I can not tell you what is going on.
It may be a bug, but it may also be that you are seeing the effects of bugfixes which have been made to counter false positives.
As a rule of thumb, I'd say: always use the latest stable release ( 3.1.1 in this case).
All the same, I am curious to hear more about the differences you see in the results.

It may make you confuse. Not mean it error when I run with 2.9. I mean that when I run checkstyle on version 2.9
That list error from php file or directory that I want to check codestyle.
Then when I run with version 3.x the error list from php file not exist anymore for new phpcs version
sth like this

Then those error above will not happen on phpcs 3.x
I hope you understand.
My question, and I wonder how can I use between this 2 version.

@sakonachhoeurng I honestly still don't understand what you mean.
What is this checkstyle you are talking about ? If that's another tool, then you may ask for support from them.

Checkstyle is a tool for checking code style. It can be used in an ANT environment, like Jenkins.
PHPCS can output with a --report=checkstyle (XML-based), which can then be read, analysed and reported by Checkstyle or other plugins as if it was a report from Checkstyle itself.
It sounds like using PHPCS 2.9 is not producing the same errors as PHPCS 3.*.
@sakonachhoeurng We're sorry, but it's really hard to be able to narrow down what the problem might be from the limited information you've provided. Since it seems the issue is not directly related to WPCS, I suggest you raise it in the PHPCS repo.

Closing for lack of response.
If this is still an issue, please provide the additional information requested and we can reopen the issue.


Tried removing payload when it was being generically used

"Payloads" are now RequestResponsePairs. "PayloadViews" are now RequestResponsePairViews. A payload is now specifically used to describe a collection of RequestResponsePairViews that are coming out or going into transit.
Also, I changed the AllRecordsHandler because it was if err == nil and we generally if err != nil.

A couple of minor questions @benjih, but it in general it LGTM! 👍


workflow-service-sdk version changes

/lgtm
I think this readme itself should be generated just as well

alternatively use a range syntax like 1.0 and let it pick what's needed.
if the autogeneration already works, we are then missing the CI to tell us something has changed. I'm planning on adding this

@rgolangh  FYI here there is a CI step that checks if something changed. Maybe it is not working properly.


Doesn't support dasherized keys

The JSONAPI spec recommends using dasherized keys
http://jsonapi.org/recommendations/#naming
However, that breaks with jsonapi-utils.
jsonapi-resources 0.7
jsonapi-utils (~> 0.4.5)
With a request such as this:
{
  "data": {
    "id": "58",
    "type": "doctor-family-members",
    "links": {
      "self": "http://localhost:3000/doctor-family-members/58"
    },
    "attributes": {
      "doctor-id": 14,
      "family-member-id": 5,
      "min-visits": 2000,
      "avg-extra-visits": 3000,
      "doctor-name": "MATTHEW PARSONS"
    },
    "relationships": {
      "doctor": {
        "links": {
          "self": "http://localhost:3000/doctor-family-members/58/relationships/doctor",
          "related": "http://localhost:3000/doctor-family-members/58/doctor"
        }
      },
      "family-member": {
        "links": {
          "self": "http://localhost:3000/doctor-family-members/58/relationships/family-member",
          "related": "http://localhost:3000/doctor-family-members/58/family-member"
        }
      }
    }
  }
}

a param method of:
params.require(:data).require(:attributes).permit(:min_visits, :avg_extra_visits)
Shows min-visits and avg-extra-visits as not permitted.

Thanks for sharing, @averydev. I'll check what's happening and patch a minor release with the fix as soon as I'm done with my current work.
Uh... is it related to #21?

Hi there @tiagopog fantastic!  I don't believe so, though it's possible.  I wasn't able to get around the dasherized problem to find out. I removed the extraneous item from the request to get that far :)

All right, I may come back later with some news. Thanks!

Here's the GOTCHA: using dasherized keys won't actually work with the default way of permitting params in Rails' ActionController. In order to avoid you getting stuck with this issue, for now you can access your permitted params by calling @request.operations.first.data[:attributes]. Anyway, I may write a better support for this feature – with some helper methods – on this weekend. Hope it helps you :-)

Closed in #23


istioctl: move waypoints command to v1

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
5006c70cd4f42b55956980f5e3f9582c221fbf98
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[Bug] Graceful shutdown killing client connections during server stop

Code of Conduct

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

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the bug
The server shutdown sequence stops the frontend service before client sessions can complete, which forcibly closes connections and causes client applications to error. Expected behavior is that the graceful shutdown functionality allows client sessions to complete successfully before the KI stops in order to minimize disruption during e.g. rolling updates.
As far as we can tell, the scope of this involves exposing shutdown hook timeouts as user-configurable and blocking the stop sequence until all sessions have been closed. Happy to submit a PR to resolve.
Affects Version(s)
master
Kyuubi Server Log Output
2022-08-15 20:20:51.580 ERROR server.KyuubiServer: RECEIVED SIGNAL 15: TERM
2022-08-15 20:20:51.583 INFO server.KyuubiServer: Service: [KyuubiRestFrontendService] is stopping.
2022-08-15 20:20:51.586 INFO server.AbstractConnector: Stopped<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:8000}
2022-08-15 20:20:51.587 INFO server.KyuubiRestFrontendService: Rest frontend service server connector has stopped.
2022-08-15 20:20:51.591 INFO handler.ContextHandler: Stopped o.e.j.s.ServletContextHandler@74dbb1ee{/,null,STOPPED}
2022-08-15 20:20:51.591 INFO server.KyuubiRestFrontendService: Rest frontend service jetty server has stopped.
2022-08-15 20:20:51.592 INFO server.KyuubiRestFrontendService: Service[KyuubiRestFrontendService] is stopped.
2022-08-15 20:20:51.592 INFO server.KyuubiServer: Service: [KyuubiThriftBinaryFrontendService] is stopping.
2022-08-15 20:20:51.592 INFO server.KyuubiThriftBinaryFrontendService: KyuubiThriftBinaryFrontendService has stopped
2022-08-15 20:20:51.592 INFO server.KyuubiThriftBinaryFrontendService: Service: [KyuubiServiceDiscovery] is stopping.
2022-08-15 20:20:51.597 INFO imps.CuratorFrameworkImpl: backgroundOperationsLoop exiting
2022-08-15 20:20:51.597 WARN zookeeper.ServiceDiscoveryClient: This Kyuubi instance <IP_ADDRESS>:10009 is now de-registered from ZooKeeper. The server will be shut down after the last client session completes.
2022-08-15 20:20:51.597 INFO client.KyuubiServiceDiscovery: Service[KyuubiServiceDiscovery] is stopped.
2022-08-15 20:20:51.599 INFO zookeeper.ZooKeeper: Session: 0x38107b157560296 closed
2022-08-15 20:20:51.600 WARN client.KyuubiServiceDiscovery: Service[KyuubiServiceDiscovery] is not started(STOPPED) yet.
2022-08-15 20:20:51.600 INFO server.KyuubiThriftBinaryFrontendService: Service[KyuubiThriftBinaryFrontendService] is stopped.
2022-08-15 20:20:51.600 INFO server.KyuubiServer: Service: [KyuubiBackendService] is stopping.
2022-08-15 20:20:51.600 INFO server.KyuubiServer: Service: [KyuubiSessionManager] is stopping.
2022-08-15 20:20:51.600 INFO session.KyuubiSessionManager: Service: [KyuubiOperationManager] is stopping.
2022-08-15 20:20:51.600 INFO operation.KyuubiOperationManager: Service[KyuubiOperationManager] is stopped.
2022-08-15 20:20:51.600 INFO session.KyuubiSessionManager: Service: [HadoopCredentialsManager] is stopping.
2022-08-15 20:20:51.601 INFO credentials.HadoopCredentialsManager: Service[HadoopCredentialsManager] is stopped.
2022-08-15 20:20:51.601 INFO session.KyuubiSessionManager: Service[KyuubiSessionManager] is stopped.
2022-08-15 20:20:51.729 INFO operation.ExecuteStatement: Query[ba6581ad-1920-4a5f-a5b3-c7e08f519842] in RUNNING_STATE
2022-08-15 20:20:52.704 INFO server.KyuubiThriftBinaryFrontendService: Session [SessionHandle [37931c19-e528-4408-a90b-9402713f9226]] disconnected without closing properly, close it now
2022-08-15 20:20:52.705 INFO session.KyuubiSessionManager: SessionHandle [37931c19-e528-4408-a90b-9402713f9226] is closed, current opening sessions 0
2022-08-15 20:20:52.705 INFO operation.LaunchEngine: Processing user's query[7f86257c-4552-49d0-b478-368a338da813]: FINISHED_STATE -> CLOSED_STATE, statement: LAUNCH_ENGINE
2022-08-15 20:20:52.707 INFO operation.ExecuteStatement: Processing user's query[ba6581ad-1920-4a5f-a5b3-c7e08f519842]: RUNNING_STATE -> CLOSED_STATE, statement: <--- long running query --->
2022-08-15 20:20:56.731 INFO client.KyuubiSyncThriftClient: TCloseOperationReq(operationHandle:TOperationHandle(operationId:THandleIdentifier(guid:C3 EE B9 A5 16 2D 4E 52 A4 A6 94 8A 80 99 2C EB, secret:FC 76 79 64 FD C7 46 08 9B 58 25 F6 E0 AC 0A DC), operationType:EXECUTE_STATEMENT, hasResultSet:true)) succeed on engine side
2022-08-15 20:20:56.741 INFO operation.ExecuteStatement: Query[ba6581ad-1920-4a5f-a5b3-c7e08f519842] in RUNNING_STATE
2022-08-15 20:20:56.745 WARN operation.ExecuteStatement: Ignore exception in terminal state with ba6581ad-1920-4a5f-a5b3-c7e08f519842: org.apache.kyuubi.KyuubiSQLException: connection does not exist
2022-08-15 20:20:56.746 INFO server.KyuubiServer: Service[KyuubiBackendService] is stopped.
2022-08-15 20:20:56.746 INFO server.KyuubiServer: Service: [MetricsSystem] is stopping.
2022-08-15 20:20:56.746 INFO metrics.MetricsSystem: Service: [PrometheusReporterService] is stopping.
2022-08-15 20:20:56.747 INFO server.AbstractConnector: Stopped<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:10019}
2022-08-15 20:20:56.747 INFO handler.ContextHandler: Stopped o.e.j.s.ServletContextHandler@5c87bfe2{/,null,STOPPED}
2022-08-15 20:20:56.747 INFO metrics.PrometheusReporterService: Prometheus metrics HTTP server has stopped.
2022-08-15 20:20:56.747 INFO metrics.PrometheusReporterService: Service[PrometheusReporterService] is stopped.
2022-08-15 20:20:56.747 INFO metrics.MetricsSystem: Service[MetricsSystem] is stopped.
2022-08-15 20:20:56.747 INFO server.KyuubiServer: Service: [EventLogging] is stopping.
2022-08-15 20:20:56.747 INFO server.EventLoggingService: Service[EventLogging] is stopped.
2022-08-15 20:20:56.747 INFO server.KyuubiServer: Service: [KinitAuxiliaryService] is stopping.
2022-08-15 20:20:56.747 INFO server.KinitAuxiliaryService: Service[KinitAuxiliaryService] is stopped.
2022-08-15 20:20:56.747 INFO server.KyuubiServer: Service[KyuubiServer] is stopped.

Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
kyuubi.frontend.bind.host <IP_ADDRESS>
kyuubi.frontend.protocols THRIFT_BINARY,REST
kyuubi.frontend.rest.bind.port 8000
kyuubi.engine.share.level USER
kyuubi.session.engine.initialize.timeout PT7M
kyuubi.session.engine.login.timeout PT1M
kyuubi.ha.zookeeper.quorum zk-0.zk-hs.zookeeper.svc.cluster.local:2181,zk-0.zk-hs.zookeeper.svc.cluster.local:2181,zk-2.zk-hs.zookeeper.svc.cluster.local:2181/kyuubi
kyuubi.engine.connection.url.use.hostname false
kyuubi.authentication CUSTOM
kyuubi.metrics.reporters PROMETHEUS
kyuubi.session.engine.idle.timeout PT30M
kyuubi.backend.engine.exec.pool.shutdown.timeout PT20M
kyuubi.backend.server.exec.pool.shutdown.timeout PT20M

Kyuubi Engine Configurations
No response
Additional context
Running Kyuubi 1.4.1 HA mode on Kubernetes. Using external load balancer only for server discovery and ZK for engine discovery. Problem identified while testing rolling updates.
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

As far as we can tell, the scope of this involves exposing shutdown hook timeouts as user-configurable

Exposing timeout for TERM makes sense to me.

and blocking the stop sequence until all sessions have been closed.

this respects the timeout above, right?

Happy to submit a PR to resolve.

Thank you @bgrams, happy to see your PR soon.

Exposing timeout for TERM makes sense to me.

Digging more I see that we can already configure this via hadoop.service.shutdown.timeout (default 30s) and I've tested this successfully. Do you think it still makes sense to expose this via the Kyuubi config as well? If not, then I think we'd want to update docs to highlight this feature.

this respects the timeout above, right?

That's right!


feat(inlay): show virtual variable text

about this https://github.com/mistweaverco/kulala.nvim/issues/209

This assumes people using TS. I would like to have this optional. I can look into some refactoring for that.

This assumes people using TS. I would like to have this optional. I can look into some refactoring for that.

Look forward to your optimization


Popover component event handling

Describe the feature in detail (code, mocks, or screenshots encouraged)
Zag's popup elements are based on a button element which causes problems when you want to add onclick events and such, or when you want to wrap an existing button with a Tooltip.
It would be great to be able to pass event handlers to Zag's button given it cannot get rid of to allow users to decide the markup themselves.
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
#skeleton-next talk in Discord: https://discord.com/channels/1003691521280856084/1191790107867488316/1306346031528673290

they all rely on onOpenChange, so I think we'll need this change for all four (popover, tooltip, modal, combobox)

@Hugos68 I know you've got limited availability right now, no worries if you don't get back to this until later, but either way I could use your help. Currently in the Tooltip component for example we have this:
<button {...api.getTriggerProps()} class="{triggerBase} {triggerBackground} {triggerClasses}">
   {@render trigger?.()}
</button>

So Zag is spreading it's own attributes to the button as one would expect. And if I log the output of api.getTriggerProps() I get the following:

So there is already an onclick in place. But I can't seem to find any sort of reference in Zag to how we hook into this or what it's used for. I'd be leery of us implementing our own onclick handler on top of this, as I would expect that would be considered a duplicate and cause issues.
As far as the API Zag exposes, there doesn't appear to be anything related to the button click event. They have onOpenChange() which triggers when the popover is shown/hidden, but that's not quite what's being requested here.
Just thought I'd reach out to you before I reach out to Zag on this. Any ideas welcome.

Zag exposes a mergeProps function to basically merge listeners from users and zag and still have the component function, see: https://zagjs.com/overview/composition#event-composition
We can definitely support this if we want to 👍

@Hugos68 ok that actually looks fairly straight forward. I'll look to get that setup today. Thank you!

@phamduylong this would be a great candidate if you're looking for something to work on! We'll just need to implement an onclick method for all four Svelte popover components using the merge method Hugo linked above.


fix(modeling): norm weight should be fp32

Motivation
MindSpore实现的InternLM将norm的权重设置为fp32，norm本身shape不大，可以考虑转成fp32以换取更好的精度。
Modification
将 norm1, nomr2 和 outputnorm 在init_model时转成fp32的dtype
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

close for repository migration.


tutorial does not work

The tutorial is missing the line connection.connect(). We define the connect callback, but never actually call the function. As a Node noob, this took me a long time to find out until I saw the missing line in your other tutorial: https://docs.microsoft.com/en-us/sql/connect/node-js/step-3-proof-of-concept-connecting-to-sql-using-node-js?view=sql-server-ver15

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 353bf767-02de-e7ea-d4a1-e0c4b9a82b4f
Version Independent ID: 93c423a3-a489-a283-084d-a54526f524d5
Content: Use Node.js to query a database - Azure SQL Database & SQL Managed Instance
Content Source: articles/azure-sql/database/connect-query-nodejs.md
Service: sql-database
Sub-service: development
GitHub Login: @stevestein
Microsoft Alias: sstein

@nivaa7 Thank you for the feedback. We are actively investigating and will get back to you soon.

@nivaa7 Thanks for mentioning the issue with the article. We have same issue reported #70006 and a PR is already created for the same change and based on approval and merge, the article will be updated.

@nivaa7 We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Respect dock windows better

We can treat them as special status clients and keep them raised.
Or the least we can do is at least respect their boundaries for maximization etc

This was fixed when I did the rewrite in Nim way back in November, I think..

We can treat them as special status clients and keep them raised.

This was fixed when I did the rewrite in Nim way back in November, I think..

I've noticed that _NET_WM_WINDOW_TYPE_DOCK windows are not being raised. Instead they're just not being managed.
Is there any way of having them be raised?

Yes, I just keep them unmanaged.

Yes, I just keep them unmanaged. Should they be raised?

Dock windows (in my experience) are kept:

Floating
Raised above other windows

Perhaps when any window is moved / resized, at the end iterate through all the dock windows and call XRaiseWindow on all.

But this sounds kind of hacky, not sure how well it will work. but I guess I will try to implement this.

I don't know much about window managers but the simplest solution to me is to just prevent any dock windows from being unraised/lowered.
Or maybe when a normal window is being raised, you could raise them above other normal windows but below dock windows. 🤔

I don't know much about window managers but the simplest solution to me is to just prevent any dock windows from being unraised/lowered.

That would be true, but I don't think there's any X call to do that.

Or maybe when a normal window is being raised, you could raise them above other normal windows but below dock windows.

Yes, but that doesn't solve the issue if you drag a window over the panel to obscure it. I think that raising dock windows on move/resize is the only trivial way to solve this but I'll look at what other WMs do.


Read timed out

We also notice timeouts when making requests to clickhouse from servers in the same data center:
ru.yandex.clickhouse.except.ClickHouseException: ClickHouse exception, code: 159, host: ip6-localhost, port: 8123; Read timed out, query:
although the load is pretty low and there are no problems with accessing mysql on the same server
ClickHouse server version 1.1.54236

Is this issue still relevant? If so, is there any way to reproduce it?

The problem was due to lags in ClickHouse server under high load and different timeout settings in ClickHouse server and JDBC driver. When we have many select queries, performance of ClickHouse server degrades significantly and simple queries will run for more than 30 secs causing timeouts in JDBC driver

how to fix this issue ?

how to fix this issue ?
+1


Simplify lockfile tests

Use project builder to create a file and an extension function to read it.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+
Thanks!

:pushpin: Commit 191358f has been approved by alexcrichton

:hourglass: Testing commit 191358f with merge b7d5203...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing b7d52030916b4a43e1cdc80c575e1dcf2630cfe7 to master...


Use of CUDA_VERSION in installation instructions in README.md

In the pip installation instructions for GPU, a variable "CUDA_VERSION" is used. We should change the name of the variable because that is an environment variable already declared by CUDA.

We've improved the installation instructions so they don't have the cryptic variables any more!


Updating NuGet.Core version to 2.11.1

Update is needed before changing the versioning scheme.
CI should produce prerelease versions of NuGet.Core package.
//cc @deepakaravindr @emgarten @yishaigalatzer @rrelyea

LGTM :shipit:


Remove all uses of the CHANGE_ENDIAN* functions

Naturally we must use these in the lowest layer of the type marshaling code (the type marshalling library) but their direct use should be removed from the SAPI and resourcemgr.

Superseded by a milestone.


An arrow stuck in the head is not displayed correctly

A skeleton shot me in the head, but for some reason the arrow is in the air.

I don't think this had anything to do with the resource pack

I believe it is, I noticed the same thing after I applied the RP, however it could be the new mods

I don't think that there is something in the model causing this I wasn't able to replicate. I may take a look to the animation code nonetheless


faq section updated

I have implemented the third design with faqs related to the community and website
here is a full screenshot and a opened one
#195
@Its-Aman-Yadav  please review and merge my PR

@Its-Aman-Yadav

Thank you so much @kairveeehh

Thank you so much @kairveeehh

You're welcome


deepin.dde-appearance: 1.1.6 -> 1.1.8

https://github.com/linuxdeepin/dde-appearance/compare/1.1.6...1.1.8
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

https://github.com/NixOS/nixpkgs/pull/272406


Salesforce Deployment Failed: failed, reason: connect ENETUNREACH

Type: Bug
1- open lwc file
2- right click and select deploy this source to org
3- Error coming in out put panel:
request to https://altayyargroup--almbdev.sandbox.my.salesforce.com/services/Soap/m/56.0 failed, reason: connect ENETUNREACH <IP_ADDRESS>:443
VS Code version: Code 1.78.2 (Universal) (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:44:45.204Z)
OS version: Darwin x64 22.2.0
Modes:
Sandboxed: No
Extensions (35)

Extension
Author (truncated)
Version

apex-autocomplete
chu
0.2.13

apex-pmd
chu
0.5.9

vscode-eslint
dba
2.4.0

prettier-vscode
esb
9.12.0

lana
Fin
1.5.2

sfdx-autoheader
Hug
0.7.3

isort
ms-
2022.8.0

python
ms-
2023.8.0

vscode-pylance
ms-
2023.5.20

jupyter
ms-
2023.4.1011241018

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

java
red
1.18.0

vscode-commons
red
0.0.6

vscode-xml
red
0.25.0

LiveServer
rit
5.7.9

salesforce-vscode-slds
sal
1.4.8

salesforcedx-vscode
sal
57.13.1

salesforcedx-vscode-apex
sal
57.13.1

salesforcedx-vscode-core
sal
57.13.1

salesforcedx-vscode-expanded
sal
57.13.1

salesforcedx-vscode-lightning
sal
57.13.1

salesforcedx-vscode-lwc
sal
57.13.1

salesforcedx-vscode-soql
sal
57.13.1

salesforcedx-vscode-visualforce
sal
57.13.1

sfdx-package-xml-generator
Vig
2.0.9

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

vscode-java-debug
vsc
0.50.0

vscode-java-dependency
vsc
0.22.0

vscode-java-pack
vsc
0.25.11

vscode-java-test
vsc
0.38.2

vscode-maven
vsc
0.41.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
2e4cg342:30602488
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
showlangstatbar:30737416
vsccsb:30705552
azdwalk:30721579
pythonms35:30701012
pythonfmttext:30731395
pythoncmv:30739700
fixhidewlkth:30730051
hidesbindicator:30730055
pythongtdpath:30739704

It's coming on only one specific network. if I change the network it's working fine.

/causedByExtension
This is specific to the Salesforce extension.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


Add gzip support to log module

Would it be possible to add gzip archiving support to the log module? Basically, the desired functionality would be to have the logs automatically gzip'd on start or on date change. (When ZNC starts, the log module can check for non-gzip'd logs, and archive them accordingly.)
Users' logs take up a lot of space (gigabytes for some), and while cronjobs might not hurt, it wouldn't be a bad idea to have automatic gziping in place.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6964225-add-gzip-support-to-log-module?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

10/10 would love this - but IRC has been slowing down recently (same with ZNC).

I like --name --best --rsyncable combination of gzip flags:
echo "# Run daily and gzip >1 day old logs that are not yet gziped
0 1 * * * znc /usr/bin/find /var/lib/znc/moddata/log/ -mtime +1 -type f -name '*.log' -exec /bin/gzip --name --best --rsyncable {} \;

" > /etc/cron.d/znc-gzip-logs

Correct for the log dir location and znc user name.


Key: get degreefor note

Hi, let me know what do you think about this feature and what would you like to added to see it included.
Cheers

Hi Lucas, thanks for contributing. I can see how this can be useful, but for the sake of maintainability I'd rather support only the minimum and let clients implement utility functions like this one.


Updated UI Components

Thank you. The requested changes are done.

Yes i have changed it
the setting is

"php.validate.executablePath": "C:/Program Files (x86)/Ampps/php-7.1/php.exe",


testing: model-mesh: locust: new entrypoint

/cc @fcami
This PR adds an entrypoint stub for running Locust against RHODS/ODH model-mesh server.
Tested in https://github.com/openshift-psap/ci-artifacts/pull/581

Tested in https://github.com/openshift-psap/ci-artifacts/pull/581, merging.


Enable OAuth for the director website by default

It would make more sense to not enable the OAuth by default but rather make it an option like the origin or cache, since director does not rely on OAuth to work.


add -I optional argument to rsync to ignore date

It would be great if one could just mirror and overwrite the entire host folder using "rsync -m -I . /pyboard"

If you use cp -r it will recursively copy a directory and doesn't look at timestamps.

Normally, I would just use rsync without -I, but the thing is file timestamp on the Pico is showing 2 hours in future...
C:\Workspace\Micropython\pico> ls -la .
   293 May 18 19:45 blink.py
   255 May 18 19:46 main.py
   127 May 18 19:45 name_tools.py
C:\Workspace\Micropython\pico> ls -la /pyboard
   293 May 18 21:46 blink.py
   245 May 18 21:46 main.py
   127 May 18 21:46 name_tools.py

But ESP32 file timestamps seem to be the same as on my host machine.
C:\Workspace\Micropython\esp32> ls -la .
   289 May 18 20:14 blink.py
   137 May 18 20:14 boot.py
   245 May 18 20:14 main.py
   127 May 18 20:14 name_tools.py
C:\Workspace\Micropython\esp32> ls -la /pyboard
   289 May 18 20:12 blink.py
   137 May 18 20:12 boot.py
   245 May 18 20:12 main.py
   127 May 18 20:12 name_tools.py

cp -r says
C:\Workspace\Micropython\pico> cp -r ./*.py /pyboard
File 'C:\Workspace\Micropython\pico/C:\Workspace\Micropython\pico/blink.py' doesn't exist

for some reason...

On Ubuntu, the workaround with cp -r works fine.
I will be using that until the problem with rp2 timestamps is fixed, after which I will just use rsync.
Thank you for your help.

cp -r says
C:\Workspace\Micropython\pico> cp -r ./*.py /pyboard
File 'C:\Workspace\Micropython\pico/C:\Workspace\Micropython\pico/blink.py' doesn't exist

for some reason...

That's a useful clue. rshell assumes that the file seperators will always be '/' and it looks like under windows the \ didn't get converted to / in the current working directory.
I wasn't aware of issues with timestamps being in the future on the pico, so I'll look into that as well.
rshell normallys sets the time on the microcontroller to match the time on the host so that when files are created on the microcontroller then they'll match up with timestamps from the host. But it's possible that the RPi Picto is doing something funky here.


updated gopanda (latest)

Closes https://github.com/caskroom/homebrew-cask/issues/17673

Merged as 9b3271d2ca42f5e25d1d812190a873d2fdcfbc74.


See whether to use the same websocket interface as Chary/Insp

More standard stuff is good, and Charybdis and InspIRCd recently added websocket support. See if we can copy theirs.

Subsumed by https://github.com/ircv3/ircv3-specifications/pull/342


Include any neural network as a component of a staged model

It should be straightforward to allow any Equinox-based neural network to be component of an AbstractStagedModel, such as SimpleFeedback, and be called during one of the model stages.
We would need to:

if it doesn't take a state/hidden argument (e.g. not an RNN), wrap it to ignore the state argument that AbstractStagedModel.__call__ will try to pass it,
associate it with a generic NetworkState-like PyTree that has a single leaf, which stores the output of the module. Alternatively, keep a single Array in the PyTree of any model of which the network is a component (e.g. SimpleFeedback).

On the other hand, we could specify the network itself as an AbstractStagedModel where network layers correspond to distinct stages, and where the activities of different layers may be kept as part of the state. In that case, the user can add interventions to these states without needing to redesign the model.
SimpleStagedNetwork is the prototype for a neural network AbstractStagedModel.

The concern over associating third-party modules with states should probably be simpler if we replace the staged model approach with a DAG approach (#28).


[BUG] ...Emphasize Available to Assign not yellow

To reproduce just add money to assign. It's not green but I think because of the new YNAB color scheme it broke the toolkit because its not yellow anymore.

Closing this as fixed and released. If the problem still persist, just reply in this thread and I'll reopen it.


Instructions in the released dataset

Hi there!
Great paper and thanks for releasing the dataset. However, may I please ask where I can find the expert written instructions for the dataset? In the drive link I just found the json-ified IE datasets. Thank You in advance!

Hi, thank you for your attention.
The instructions we wrote for the tasks are stored here: link.
Considering that the instruction and sample are directly combined, a lot of redundancy will be caused when storing. So we adopted a runtime-generated strategy. If you only wish to generate training/validation data. You only need to remove --do_train and  --do_predict, and the log will tell you where the generated data is saved.


Branch 2.0 is using sdk 1.0

This example is not really working on Rasa 2.0, right?

Thanks for the issue, @TyDunn will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

@ArjaanBuijk I was able to run it with the pinned versions in PR #86.


trying to open drawer from header button but not working is something wrong in the code

import React from 'react';
import { StyleSheet, Text, View ,Button,TouchableOpacity,Icon} from 'react-native';
import { StackNavigator,TabNavigator ,DrawerNavigator,NavigationActions} from 'react-navigation';
import Explore from './screens/Explore';
import WishList from './screens/WishList';
const TabNav = TabNavigator(
{
Explore: {
screen: Explore,
},
WishList: {
screen: WishList,
},
},
{
animationEnabled: false,
swipeEnabled: false,

}
);
const StacksOverTabs = StackNavigator({
Root: {
screen: TabNav,
navigationOptions :({ navigation }) => ({
headerRight: <Button title="Info" onPress={() => navigation.navigate('DrawerOpen')} />,
})
},
});
const MainNavigator = DrawerNavigator({
Home: {
screen: StacksOverTabs,
},
});
export default class App extends React.Component {
state = {
fontLoaded: false
}
async componentDidMount() {
await Expo.Font.loadAsync({
'Arial': require('./screens/Fonts/Arial/Arial.ttf')
});
this.setState({ fontLoaded: true });
}
render() {
if (!this.state.fontLoaded) return null;
return (
<StacksOverTabs />

);
}
}
const styles = StyleSheet.create({
container: {
backgroundColor: '#fff',
alignItems: 'center',
justifyContent: 'center'
}
});

Hi @samakkaking! It looks like this is not a bug of the library nor a feature request, so I'll close it: I suggest next time you use Stack Overflow which is better suited for answering these types of questions. I also encourage you to join the Reactiflux community on Discord. There are React Native and React Navigation channels with helpful people who might be able to answer your question. I would also like to mention that there is a collection of helpful links and tutorials for React Navigation here which might be helpful for you.
That said, I also suggest you read the ongoing article series about how to do advanced navigation with a Drawer on Medium, I think it will help you.
If you believe that you are experiencing a bug or have a feature request, please open a new Issue following the dedicated template or submit a PR.


Add Kingly implementation to the list of existing implementations

Hi there,
I have an implementation of Conduit with the Kingly state machine library. I would like it to figure in the list of such implementations. How should I proceed?
Repository is here: https://github.com/brucou/realworld-kingly-svelte
Thank you!

You can submit your implementation here:
https://codebase.show/projects/realworld


test: fix error reporting system test race

The system tests for error reporting were still not safe to run
concurrently. The issue is that at the end we were deleting all events
(there is no API to delete events selectively, AFAICT). This meant that
concurrent executions of the system tests against the same project could
clobber anothers logged errors.
This is consistent with the observed timeouts looking for events to
show up.
Fixes #267

I still do think that these error reporting system tests have been creating too much busy work and not providing real value. I do not think we have found a single legitimate failure in the past year+. I wouldn't mind if they were to go away.


Js charts

Finished extraction of Vector2D, Wetherill, and newtonMethod from errorellipsechart.js.  Implemented tests for Vector2D and Wetherill.

Some quick last thoughts:

remove nb-gradle*
add tests for Newton method
squash commits
come up with a list of things you didn't understand and ask me/@bowring or figure them out

This work has moved to #86 for reasons noted there.


Added sass support

I'm using this package along with SASS and Gulp in my project. Since SASS can't import raw CSS files I had to copy and rename original CSS file to integrate it into the project. I guess I'm not the only one who uses SASS with front end automation tools, so it would be nice to add native SASS support. It helps to integrate styles seamlessly (using includePaths option).
I also added path to new sass file under bower main files list, so it could be parsed by npm-packages like main-bower-files.
P.s: I guess dummy Gruntfile "styles" task could be changed on something more advanced.
Thank you!

There have been many discussions like this in the past, but in general I'm opposed to adding a ruby dependency to a JS project.

More of an FYI, grunt-sass does not depend on ruby. It uses libsass which is written in C++.


VIRTUAL_ENV no longer used, giving "No Python default installation found in virtual environments" error

We use echo "VIRTUAL_ENV=${Python_ROOT_DIR}" >> $GITHUB_ENV to avoid needing a virtual env in Github Actions. As of 0.2.0 this has stopped working.
$ pip install uv
Collecting uv
  Downloading uv-0.2.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (32 kB)
Downloading uv-0.2.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.0 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 13.0/13.0 MB 185.8 MB/s eta 0:00:00
Installing collected packages: uv
Successfully installed uv-0.2.0

$ uv pip install -U pip setuptools wheel invoke
error: No Python default installation found in virtual environments
Error: Process completed with exit code 2.

python -m uv pip install -U pip setuptools wheel invoke works so it does seem there's something going on with the Python installation detection.

uv --version is 0.2.0 (latest)
Environment is Github Actions Ubuntu 20.04 runner.

I can second that. All my builds that use to work with 0.1.45 fail with this error: No Python default installation found in virtual environments.

Thanks for the report, this sounds like a regression from #3266.
I think pointing to a system installation with VIRTUAL_ENV was a hack in the first place though and never officially supported. Why not use --system now that we support that?
What's the value of ${Python_ROOT_DIR}?

@joennlae Could you share an example of the VIRTUAL_ENV or CONDA_PREFIX you are setting?

I can just share the workflow.yml file:
name: Linting

on:
  push:
    branches:
      - main
  pull_request:

jobs:
  checks:
    runs-on: ubuntu-latest
    name: ${{ matrix.quality-command }}
    defaults:
      run:
        shell: bash -el {0}
    strategy:
      matrix:
        quality-command:
          - black
          - ruff
          - mypy
    steps:
      - uses: actions/checkout@v4
      - name: Install environment
        uses: conda-incubator/setup-miniconda@v3
        with:
          environment-file: environment.yml
          activate-environment: 44ai
      - name: Install Dependencies
        run: |
          conda activate 44ai
          pip install uv==0.1.45
          uv pip install -r requirements.txt
          uv pip install -r requirements-dev.txt

the environment.yml:

name: 44ai
channels:
  - defaults
dependencies:
  - python=3.11
  - tesseract
  - ffmpeg

I it is not the full environment but this should be reproducible.

@zanieb
echo $VIRTUAL_ENV
/opt/hostedtoolcache/Python/3.11.9/x64

ls /opt/hostedtoolcache/Python/3.11.9/x64
Python-3.11.9.tgz  build_output.txt  lib     share
bin                include           python  tools_structure.txt

@thundergolfer thanks for the details! Yeah this looks like an unintentional change but I think it's probably for the best if --system achieves the intent. I could see us allowing but warning if VIRTUAL_ENV points to something that's not actually a virtual environment but I'd rather not complicate it without more justification.
@joennlae looks like you're encountering the same as #3769 which I'm fixing in #3771 — we'll have that fixed asap.

Yep thanks have made a PR internally to switch to --system. Thanks for the quick response 👌.

Neither VIRTUAL_ENV nor the --system flag seem to work on GitHub Actions anymore, switching back to pip

Please share a reproduction if you can, I'm happy to help.


Solve Large Analysis with known OD Pairs tool fails

I have been trying to use the tool within ArcGIS Pro, with a GTFS network dataset that I have developed. However, when running the tool, it fails and I get the following message in Pro:

File "C:\Users\AppData\Local\Programs\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\concurrent\futures\process.py", line 239, in _process_worker

I have double-checked the data, and they don't appear to have any issue. Note that I have also performed route analysis using the same data and network dataset successfully.
I am not sure what the above message means. Any advice?
Thanks!

Hello @gboura. I presume you are the same user from this Esri Community thread: https://community.esri.com/t5/arcgis-network-analyst-questions/large-network-analysis-toolbox-for-network/m-p/1183690.  Just wanted to link to that other thread for broader context.
I can't really determine what the problem might be from that one line of text above.  Basically the tool uses the concurrent.futures module to spin up parallel processes, and what you've pasted above is a partial error message indicating that some sort of problem with the parallelization occurred.  It could be that you set the max parallel processes too high, or it could be some other weird issue.
Can you give me more details about what's going on?
First, please paste the entire error message text.  (Try switching to the "Messages" section in the little box that shows the tool parameters and messages.  Copy and paste the entire thing in here.)
Second, what do your inputs look like?  What values have you used for the input parameters, how many origins and destinations do you have, etc.?

Hello @gboura.  In my latest update to the tool code (from earlier today), I made a small change that should improve error messages when the parallelization subprocess encounters a problem.  If you're still using this script and having problems with it, you can try the latest update, and hopefully it will at least give you a better message indicating what the problem is.

If you're still experiencing this problem, please reopen this issue with more details about your error after retrying with the updated tool.


fix: ignore remove error

:tada: This PR is included in version 0.0.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


unnecessary duplicated predication

https://github.com/alibaba/TairString/blob/65e8695c8d9c398140182b101e391adfab403179/src/tairstring.c#L901-L903

Thank you, could you please submit a PR to fix this problem?


Support state restoration for view layout

We probably don't want to try to support app restoration right now.

https://developer.apple.com/documentation/uikit/uiviewcontroller/1621499-restorationidentifier

Since we're now opening in the 'All Programs' view, it seems like we could probably get away without doing this in a v1.


[AppStore build upload] ITMS-90853 Invalid Font

Hello guys, I have issue when I want to upload new build to TestFlight.
ITMS-90853: Invalid font - There was an error validating the font at 'Runner.app/Frameworks/App.framework/flutter_assets/packages/open_iconic_flutter/assets/open-iconic.woff'. Font not supported by platform.
Can You give me some tips. I make "flutter clean", I have latest Flutter version.
I try to change this file to .ttf but this is Dart Packages framework and after build its back to woff. Cupertiono_icons and Chewie use this.
Is this possible that adding Home Widget writing in swiftUI generate this problem?

@swiftbacon
.woff fonts are not supported by the platform as also mentioned in the error. You may need to use the .tff equivalent of the font and try again.  See this issue for more details.
Closing this as non-issue from Flutter framework.


Migrate etsauer/onboarding-manager

Type of repository request
I would like to migrate the following repository into the CoP
https://github.com/etsauer/onboarding-manager
Requested name for the repository
onboarding-manager
Repository Description
Manages Creation of Namespaces in OpenShift
Admin Access
Unsure, maybe just org maintainers.
Write Access
container-cop-mergers
Read Access
container-cop
gpte
Additional details
None.

@etsauer has this been implemented via 9190cadaa857ddfb701f9458ae5b793a92a12295


Task doesn't fail on lint errors

When running the task, I would expect the task to fail when any error is found within the html. (according to the validation rules I made up).
In my case, there are errors in the markup, which are also shown in the task results, but the task itself does not fail.
Here is my task setup
{
    options : {
        htmlhintrc : 'config/.htmlhintrc'
    },
    raw : [
        '<%= config.dev.data.raw_html %>/**/*.html'
    ]
}

which runs fine and results in the following output:

Running "htmlhint:raw" (htmlhint) task
   dev/data/raw/brand/de/stada.html
      L3 |

          ^ Tag must be paired, missing: [
 ], start tag match failed [
 ] on line 2. (tag-pair)

   dev/data/raw/brand/en/stada.html
      L3 |

          ^ Tag must be paired, missing: [
 ], start tag match failed [
 ] on line 2. (tag-pair)

>> 14 files lint free.

Done, without errors.

But there are errors!  And 2 of 14 files are not lint free.
Shouldn't the task fail? Is it a bug?
I am using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

+1


Fix typo in printed message in DockstoreYamlHelper (corrected)

This PR fixes a typo in one of the error messages (calls the file docksore.yml instead of .dockstore.yml).
Closes #3429

Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install

Opening this PR to replace #3444 because that one was from a fork while this one is from a branch.


feat(@schematics/angular): update tslint and codelyzer to latest

This broke the CLI end-to-end tests because fixing errors now returns a zero status (it didn't before) when there's no more linting issue (test tests/lint/lint-with-type-check-fail).


[Revise logical def] total number of puddling passes

AgrO term (ID and Label)
total number of puddling passes
Suggested revision of logical definition
Incorrect oboInOwl:hasExactSynonym
Proposed: "total number of puddling passes"
Your nano-attribution (ORCID)

Sorry, I don't understand your note. Could you explain the issue, please?


Support for IHP PDK

Hi, I was wondering if could be possible to add IHP-Open-PDK support (130nm BiCMOS), please. Thanks.
https://github.com/IHP-GmbH/IHP-Open-PDK

We would like to add support, but it requires significant work. We would be glad to take this as a contribution.


[Migrated] from zappa.concurrent.futures import LambdaPoolExecutor?

Originally from: https://github.com/Miserlou/Zappa/issues/1024 by olirice
Feature Proposal
Implement LambdaPoolExecutor with a similar api to
ThreadPoolExecutor and ProcessPoolExecutor?
i.e.
from concurrent.futures import as_completed # pip install futures on py2.7
from zappa.concurrent.futures import LambdaPoolExecutor

# Pushes current working directory to Lambda
executor = LambdaPoolExecutor(max_workers=15)

# Function to execute in Lambda function
def do_stuff(x: int) -> int:
    return 1

futures = []
for val in range(100):
    # Submit work to Lambda function
    # Store python future (non-blocking)
    future = executor.submit(do_stuff, val)
    futures.append(future)

# As each task completes
for output in as_completed(futures):
    # Collect result from futures object
    result = output.result()

    # do more stuff with result

Thoughts:

Initialization of the executor would package up the project and ship it to Lambda (if not exists).
Submitting work to the executor pickles the variable x, copies it up to S3 and notifies a handler in Lambda
The handler downloads, unpickles, and passes the variables to the function
The client (LambdaPoolExecutor) repeatedly checks S3 for a response to see if the work is done
When the work is done, copy the pickled response from S3, unpickle, and set the result to the futures object

But why?
Zappa for cluster computing!

Drop in replacement for python concurrency primitives
Map reduce
ETL
Distributed web scraping
Generally take advantage AWS's CPU our internet connection resources with little effort

Possible hang ups

5 minute max execution time

All thoughts welcome
If the response is positive, I'll take a swing at implementing it.

I believe this can be achieved to some degree with the current asynchronous task execution.
Since this is a older migrated task I will close it.
If there is still interest in getting something like this implemented open a new issue.


"Code-style naming rules" amended

The "Code-style naming rules" MS docs page is currently hard to grasp:
There is a mistake in the heading hierarchy, making it difficult to find content.
The word "property" is used for distinct entities, making it hard to understand which entity a piece of information applies to.
The sequence of sections isn't congruent with the information to convey.
The tiny "Required" table column information is lost when put behind the huge "Allowed values" column.

So, I tried to fix the content to make it easier to understand.
I did the following:

Heading hierarchy fixed
"property" replaced with "component", or "rule", where applicable
Sections semantically sorted
Additional pieces of information added to tables
"Required" table column moved left to "Allowed values" column, so the information won't be lost
Additional example provided, to demonstrate usage of required_prefix

@zspitz in case you want to review the proposed changes.

@SetTrend

There is a mistake in the heading hierarchy, making it difficult to find content.
...
The sequence of sections isn't congruent with the information to convey.

Could you clarify this?

The word "property" is used for distinct entities, making it hard to understand which entity a piece of information applies to.

Because all the entity definitions are nothing more than a collection of property settings, associated by kind and title. I'm not sure what you are referring to. Could you clarify?

I feel ashamed for not being able to update my pull-request yet.
From what I can see, @zspitz is taking over (#28237)?

I'm going to close this PR since the improvements were made in #28237. Thank you for your efforts @SetTrend.