Cannot launch multiple Java classes

Does this issue occur when all extensions are disabled?: Yes/No
I need Java based extensions for my development, therefore have not tried this.

I am still seeing the issue discussed in https://github.com/microsoft/vscode/issues/37589 which I thought was fixed

VS Code Version: 1.56.2
OS Version: macOS Mojave

Steps to Reproduce:

Run long running Java class 1
Run Java class 2
The launch command for the second class will be executed in the same terminal rather spawning off a new one.

/extJava

This only happens when the user is using "Run without Debugging" feature. Debugging multiple Java applications in terminal work well.
This is because Java debugger has special support for "Run" feature. If the user triggers a "Run" feature, the debugger generates a command line to the terminal in launch request, and then immediately terminates the debug session. Because when the user's application runs in terminal, the debugger loses control over the lifecycle of this application and keeping the debug session alive is meaningless. It seems that the VS Code client assumes that the previous session has ended and keep reusing the terminal for the subsequent session. That's not true for "noDebug" feature.
// @weinand

Thanks for letting us know. So the gist is: "VS Code should not reuse terminals when Run Without Debugging session ends"

This is a solution. But I wonder if it is possible to detect that there is some process still running in the terminal and decide whether to reuse it or not. Since "Run" is more popular than "Debug" from Java debugger extension, I would still like to reuse the terminal as much as possible.

@tyriar and @weinand would know better since they are the owners of the original code for terminal reuse from debug.

@testforstephen we are already trying to detect whether a process is running in the integrated terminal. If it is we are using a new integrated terminal.

I tried this and it seems to work fine now. Let me know if you still see issues.


Scrolling is 'tripping' when at top or bottom when no-wrap and itemCount is >= 5 issue #38

Issue #38 appears on my app
I am using OnePlus 6 android 10 with v2.4.10 of the NumberPicker

https://github.com/ShawnLin013/NumberPicker/pull/176 fixes this issue

This issue has been fixed at v2.4.11. @crackTheCode


[r] Use X_capacity=1000 to optimize reads

Larger-scale queries (in the megacell range) have revealed an opportunity to more closely align tile capacity with remote-read performance.
This PR ports #533 from Python to R on main-old.

Note: the config["sm.mem.reader.sparse_global_order.ratio_array_data"] = "0.3" bit was causing a segfault in CI which needs separate debugging. For now I'll land this PR with the capacity=1000 setting, and address the remaining issue separately.


Selecting the GPU

Hey, is it possible to select the GPU where the computations are done?
Thanks

cudarray calls during initialization.
_gpu_id = int(os.getenv('CUDARRAY_DEVICE', '0'))
so if you use os.putenv prior to importing the deeppy library on the main script, you can alter the device.
This needs to be done ~before~ you call deeppy !!

Thank you!
I now just call CUDARRAY_DEVICE=2 python neural_artistic_style.py ...


crates.io calls the license "non-standard"

FYI, using license-file without license leads to crates.io listing this crate as having a "non-standard" license, even though it's really just MIT. See also rust-lang/cargo#8537.

Hi and thanks for the info!
I'll fix it after my vacation🏖!

A new version has been released https://crates.io/crates/jql/2.6.6.
Thanks again for the heads up!


examples/front-proxy tutorial is broken

I'm using Docker for Mac and for some reason the example proxy in examples/front-proxy cannot bind to <IP_ADDRESS>:80 inside the container.
front-envoy_1  | [2020-06-08 21:04:27.772][7][critical][main] [source/server/server.cc:100] error initializing configuration '/etc/front-envoy.yaml': cannot bind '<IP_ADDRESS>:80': Permission denied

docker run --rm -p 80:80 nginx works fine.
So it makes me think something’s wrong with the docker-compose config. I unfortunately don't know enough to contribute.

Hum, I think all examples that bound to 80 need to be updated since: https://github.com/envoyproxy/envoy/pull/11323
Meanwhile:
    environment:
      - "ENVOY_UID=0"

CMD command runs with envoy user because of this configuration. I tried adding to USER root to Dockerfile and user: root to docker-compose.yaml, but it didn't work because of this entrypoint.
If you are add to ENVOY_UID=0 to environment, you can run as root. Also see, https://github.com/envoyproxy/envoy/blob/e8a2d1e24dc9a0da5273442204ec3cdfad1e7ca8/ci/docker-entrypoint.sh#L25

CMD command runs with envoy user because of this configuration.

its the entrypoint which changes the user.
@mattklein123 would you like me to PR to update the examples that expose 80 ?

Sure any fixes to improve the examples appreciated.


New section library

As discussed in #75, a more orderly way of organising built-in geometries implemented in sectionproperties.
Consists of a new library module under the pre module, with built-in geometries organised into files based on their application. Currently consists of the following:

Standard sections
Steel sections
Concrete sections (consisting of 3 new built-in sections :tada:)
Bridge sections (to be added in future by @ccaprani)
Nastran sections

This also broke a fair number of examples in the docs which I have gone through and cleaned up.
#124 will also need to be slightly reworked to catch the new library structure.

Hi @robbievanleeuwen,
I made the changes in file naming: sections.py  -> geometry.py  -and-  cross_section.py -> section.py. It seemed like it fit well within this branch/PR.
I see that the docs build so I think that means that I caught all of the updates that needed to occur in the doc string examples, too.
Shoot, I just realized that I will have to update all of the examples @normanrichardson, too. Won't take too long once he is able to merge his PR.
Should norman's PR be merged before this one?

@connorferster yeah I think it makes sense to get #143 merged first then we can edit those files as needed in this PR.

@robbievanleeuwen @Spectre5 I saw that the Lint checks were failing and so was sure to "blackify" all of the code in the directory. However, even after that, the linter is telling us that it would still modify files. I re-ran black on the whole section-properties directory and there are no modifications. What do you think might be going on here?

I'd bet that you are using a different version locally than in the CI.  This is one reason I like to use poetry to freeze the version and use poetry also in the CI files to make sure the same version is used in CI as locally, not just for black for any other future code checkers or linters too (isort, pylint, flake8, mypy, etc).  Removes a lot of these types of headaches, especially if more linting tools get added in the future.  And makes sure that all developers are using the same versions locally too.

Yep I guess you have a different version of black locally as @Spectre5 suggested. I have the same output locally as the github action.
Also there appear to be a few issues with the docs build.
Another quick one with the sphinx-gallery - the mesh is not showing on any of the plots in the examples, e.g. see here. Don't have any experience with the gallery but maybe it's something to do with the image quality being saved?

I'm guessing it is a resolution issue that @robbievanleeuwen has found.  It you look closely, you can very faintly see an outline of he circle.  Or a few edges in the second example output.  One option would be to change resolution/dpi that sphinx-gallery uses to save the images.  If that doesn't work, then another option could be to make the linewidth argument for plot_mesh being a variable and then use something thicker, like lw=1.0 in the examples.

Yet another option would be to allow passing figsize to plt.subplots and then using a larger figure.  It probably should be larger anyway, so you could make the default larger (or else just the examples).

It may also be caused by the alpha settings from the plot. Will check it out.


Different standards behind feature flags

Ideally, we should be able to select only the hashing standards we need with feature flags. This can reduce compile times. The default-features could still be all the standards, but if you specifically wanted to reduce the dependencies and compile time, you could. This should not cause any significant SemVer change and therefore could just be published as 1.0.1.

The idea of placing different hashing algorithms behind their own feature flags has already been floated in #16, but I'm still against it for the same reasons, so I'm going to close the issue as WONTFIX.

Ah okay. I didn't see that issue.


Only allow system user to perform eventual scans on root and meta

Closes #4528

Still draft because I need to add some tests for this. The test changes as of now are cleanup of existing tests.


expose instanceDiscovery flag

expose instanceDiscovery flag which is set to true by default.
Reference to python PR https://github.com/AzureAD/microsoft-authentication-library-for-python/commit/dd7b53805efb985f6a85c22f294f20d9adfcc01d

don't add the new entry to cache, because cache is static tests can be more useful if they test the end to end experience and mock the http layer
Done.

FYI - This branch has been published as a beta release for Azure SDK team to test.


chore(ci): several fixes/improvements to Firebase deployments

Several fixes and improvements related to deploying to the code-angularjs-org and docs-angularjs-org Firebase projects.
See individual commits for details.
Fixes #17111 and angular/angularjs.org#251.

I finally had a chance to look through this. It all looks good to me! Lots of long-needed updates and alignments with the recent updates to Firebase.


chore(ci): ensure that acir artifacts are published on master

Description
Problem*
Resolves
Summary*
We're currently never publishing ACIR artifacts on master as seen in this CI run: https://github.com/noir-lang/noir/actions/runs/6699174556/job/18202815460
The issue seems to be a matter of quotation marks in the if statement so this PR removes them.
Additional Context
Documentation*
Check one:

[ ] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Looks like this hasn't done the trick :thinking:


Is there a way to execute a rule?

I can't seem to find it, but is there something that will evaluate if an object passes a rule?
i.e.
my rule = age > 30 && first_name == 'John'
my_object = {first_name: 'John', age: 55}
is there something that I can call matches_rule(rule, my_object) and returns true or false?

Sounds like JsonLogic would meet your need:

Official site
RQB export documentation

Thanks Jake. That worked perfect.


[BUG] Text not appearing in the dropdown box in profile page

Description
The website is great but the text in the dropdown isn't visible as you can see in the screenshot.
Here is the link:- https://linkfree.io/account/manage/profile
and click on layout, you can see the dropdown and this only happens in dark mode, in the light mode, it's not an issue as you can see in the screenshot below
Screenshots

Additional information
No response

Able to recreate, will open this issue. Appreciate your contribution.
A note for opening issues, please add more details which helps pinpoint and triage the issues.
For example I would have adde a screenshot that showed more context, the link to the page, and that this only happens in dark mode.  Nothing to change! Just some notes for future issues to consider.

Thank you for raising, I will close this issue as it is a duplicate of https://github.com/EddieHubCommunity/LinkFree/issues/7939


Unsafe variant

Thought I would throw this out there. I think it will outperform even your instanced mode. Would love it if you could try it and let me know.
    /// <summary>
    /// Measures the difference between two strings.
    /// Uses the Levenshtein string difference algorithm.
    /// </summary>
    public static class LevenshteinUnsafe
    {
        /// <summary>
        /// Compares the two values to find the minimum Levenshtein distance.
        /// Thread safe.
        /// </summary>
        /// <returns>Difference. 0 complete match. -1 if either value1 or value2 is null, -2 if value2 is too large.</returns>
        public static unsafe int Distance(string value1, string value2)
        {
            if (value1 == null || value2 == null)
            {
                return -1;
            }
            else if (value2.Length == 0)
            {
                return value1.Length;
            }
            else if (value1.Length == 0)
            {
                return value2.Length;
            }
            else if (value2.Length > 1024)
            {
                // prevent stack overflow
                return -2;
            }

            int* costs = stackalloc int[value2.Length];
            int* costsEnd = costs + value2.Length, ptr;
            int i = 0, j, insertionCost, cost, additionCost;
            char value1Char;

            for (ptr = costs; ptr != costsEnd; ptr++)
            {
                *ptr = ++i;
            }

            for (i = 0; i < value1.Length; i++)
            {
                // cost of the first index
                cost = additionCost = i;

                // cache value for inner loop to avoid index lookup and bounds checking, profiled this is quicker
                value1Char = value1[i];

                for (ptr = costs, j = 0; ptr != costsEnd; ptr++, j++)
                {
                    insertionCost = cost;
                    cost = additionCost;

                    // assigning this here reduces the array reads we do, improvement of the old version
                    additionCost = *ptr;

                    if (value1Char != value2[j])
                    {
                        if (insertionCost < cost)
                        {
                            cost = insertionCost;
                        }

                        if (additionCost < cost)
                        {
                            cost = additionCost;
                        }

                        ++cost;
                    }

                    *ptr = cost;
                }
            }

            // the last int is the cost
            return *(--costsEnd);
        }
    }

Well I benchmarked and the instance class was faster, surprisingly. Guess the jit is not as good at unsafe code.


Fixed cut-off strings in overview page

Even the long German strings vertoe is using fit now

Awesome!

Thanks crowning :+1:


Small refactor of logs functional tests

The refactors the logs functional tests to pull out the call to ApiClient.CaptureLogsAsync into anonymous functions which simplifies the remaining validation code into one code path. No behavioral changes or fixes are made with this refactor.

/backport to release/7.x

/backport to release/6.x


AOT build leaves component templates in the final bundle

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

What is the current behavior?
AOT build inludes every component template two times making the bundle much bigger than needed as templates are included as strings which cannot be minified by UglifyJS.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

In freshly cloned repo
npm i
npm run build:aot:prod
grep -o "WebPack Angular 2 Starter by" dist/main.*.js
returns 2 lines matching:
one in ngc compiled component code (this._text_30=this.renderer.createText(this._el_29,"WebPack Angular 2 Starter by ",null),this._el_31=s.createRenderElement()
other in bundled template (\n\n    \n      WebPack Angular 2 Starter by @AngularClass\n )

What is the expected behavior?
Component templates are not included as strings. They are already handled by ngc and built into compiled components

we need something else to remove the decorators. I'll close this unless you know of a way to remove them or know of a module that will do it


fix(github)!: remove owner from OAuth connection var names

Remove the GitHub app installation's owner (org/user) from the names of OAuth connection vars.
This change spans both the AK server and the Python SDK - both need to be released and deployed together!
Core files in this PR (the rest are just small adjustments):

integrations/github

internal/vars/vars.go
jwt.go
oauth.go

runtimes/pythonrt/py-sdk/autokitteh/github.py

Tested manually with this Python code snippet:
import random

from autokitteh.github import github_client

# https://docs.github.com/en/rest/reactions/reactions#about-reactions
REACTIONS = ["+1", "-1", "laugh", "confused", "heart", "hooray", "rocket", "eyes"]

def on_github_issue_comment(event):
    github = github_client("github_conn")
    repo = github.get_repo(event.data.repo.id)
    issue = repo.get_issue(event.data.issue.number)
    comment = issue.get_comment(event.data.comment.id)
    reaction = random.choice(REACTIONS)
    comment.create_reaction(reaction)

Refs: ENG-1422, ENG-1445
BREAKING CHANGE: OAuth connection vars in existing GitHub connections need to be renamed.

What was the original intent behind having installation's owner (org/user) in the names of OAuth connection vars?
To know when user is part of org?

What was the original intent behind having installation's owner (org/user) in the names of OAuth connection vars? To know when user is part of org?

This was added in #240. I missed this aspect due to the PR's size.


Make jinachat_api_key a SecretStr

Description: This pull request removes secrets present in raw format
Issue: Jinachat api key was exposed when printing out the langchain object https://github.com/langchain-ai/langchain/issues/12165
Maintainer: @eyurtsev

lots of merge conflicts as we updated Jina Embeddings, going to close


GroupJoin after Join “flattens” results

Using Entity Framework Core 2.1 and an SQLite database, I get different behaviour from a LINQ GroupJoin if I use it after another Join. It is not clear if this is a bug or if there is something I am overlooking.
I have created a minimal VS2017 project to reproduce this, which can be found here:
https://gitlab.com/haddoncd/EntityFrameworkGroupJoinIssue
In this example, I get one object for each row in the Blog table, each containing multiple PostTitles:
db.Blogs
    .GroupJoin(
        db.Posts,
        s => s.BlogId,
        p => p.BlogId,
        (s, ps) => new
        {
            s.BlogId,
            s.BlogTitle,
            PostTitles = ps.Select(p => p.PostTitle),
        }
    )
    .OrderBy(x => x.BlogId))

But in this example, the results are "flattened" - I get one object for each Blog-Post pair like you would from a conventional SQL outer join:
db.Subscriptions
    .Join(
        db.Blogs,
        s => s.BlogId,
        b => b.BlogId,
        (s, b) => new
        {
            s.SubscriptionId,
            b.BlogId,
            b.BlogTitle,
        }
    )
    .GroupJoin(
        db.Posts,
        x => x.BlogId,
        p => p.BlogId,
        (x, ps) => new
        {
            x.SubscriptionId,
            x.BlogTitle,
            PostTitles = ps.Select(p => p.PostTitle),
        }
    )
    .OrderBy(x => x.SubscriptionId))

Note: I posted this as a question on Stack Overflow, where another user said they were able to reproduce this with SQL Server, suggesting that this is an EF Core bug, not an SQLite provider issue.

May be a dupe of https://github.com/aspnet/EntityFrameworkCore/issues/13365.

Closing as we don't plan to support this as per #17068


Infrastructure to support backward-compatibility check

Description
This PR implements the infrastructure to support backward-compatibility testing and, more generally, policies applied to multi-version registries.
The following command checks the current registry (main branch in the official repo) with a baseline registry (here, the archive v1.26.0) against a package of rules (policies) defined in the file compatibility_check.rego:
weaver registry check \
--registry https://github.com/open-telemetry/semantic-conventions.git[model] \
--baseline-registry https://github.com/open-telemetry/semantic-conventions/archive/refs/tags/v1.26.0.zip[model] \
--policy compatibility_check.rego

The following screenshot is the output of this command if we artificially remove the file registry/deprecated/container.yaml from the main branch.

Changes

[X] Extend the registry path format to support local and remote archives in addition to local folders and git repositories. The format will also support the definition of sub-folders. Motivation: with this PR, we now have two types of registries. Without a registry path format, we would need to add many parameters to support all combinations (folder, git-url, git-archive, folder, tag).

<local-path> (e.g. $HOME/otel-registry)
<git-url> (e.g. https://github.com/open-telemetry/semantic-conventions.git)
<git-url>[<sub-folder>] (e.g. https://github.com/open-telemetry/semantic-conventions.git[model])
<git-archive-url> (e.g. https://github.com/open-telemetry/semantic-conventions/archive/refs/tags/v1.26.0.zip)
<git-archive-url>[<sub-folder>] (e.g. https://github.com/open-telemetry/semantic-conventions/archive/refs/tags/v1.26.0.zip[model])
Future extension: <git-url>@<tag>
Future extension: <git-url>@<tag>[<sub-folder>]

[X] Unify RegistryPath (merge the two existing implementations defined in the weaver and weaver_semconv crates).
[x] Document CLI usage for the new registry path format.
[x] Add --baseline-registry in addition to --registry (both will support the same syntax for the registry path). The --registry-git-sub-dir will be marked as deprecated.
[x] Implement support for local and remove git archives (supported formats: .tar.gz, .zip).
[x] Replace Weaver Cache with the more general concept of RegistryRepo supporting all the variants of RegistryPath.
[X] Integrate --baseline-registry with the policy engine. In particular, we must decide how to expose the two registries in Rego.
[X] Create standard SemConv Rego rules and function to ease the creation of semconv policies.
[X] Create examples of policies to detect backward-compatibility issues.

Overall LGTM. A couple nits - Predominately I think next time the Git-Url / path reference code should be a separate PR form the policy engine changing code.
THink you can close a few open issues for this one :)

Yes, creating two PRs was part of the initial intentions, but it got lost in the heat of the moment.


join_on tag value is assigned to WHERE instead of JOIN

Issue Description
When using the join_on tag in bun ORM to specify join conditions for a relationship, the condition is unexpectedly influencing the WHERE clause, leading to a full omission of main entity results if the relationship's condition isn't met. This behavior is contrary to typical SQL JOIN operations where the main table's data would be returned with NULLs for the related table's columns if the JOIN condition fails.
Example
Given two tables books and authors, with a join_on condition like authors.nationality = 'Canadian' within the books model, the current implementation results in zero results for a book query when no authors meet the condition. The anticipated result is to receive the book data with NULLs for the author columns.
Expected Behavior
The join_on condition should be applied within the JOIN clause, permitting the retrieval of books records regardless of whether the authors condition is met.
Current Behavior
No books records are returned when the join_on condition for authors is not satisfied, suggesting that the condition is being incorrectly placed in the WHERE clause.
Steps to Reproduce

Define books and authors models with a join_on condition that references a field from the authors table.
Execute a query on books that includes a join with authors where the join_on condition (e.g., authors.nationality = 'Canadian') does not hold true.
Observe that the result set is empty, contrary to expectations.

Environment

bun ORM version: [v1.1.12]
Go version: [1.21]
Database and version: [postgres v15]

Additional Information
(Include logs, error messages, and any other context that might aid in diagnosing the issue.)
Suggested Resolution
If available, outline any potential solutions or workarounds you've considered or attempted.

Just came across this myself and the only way I found around the problem is to use Join/JoinOn and lots of error prone ColumnExpr.

Hit the same.. the solution with Bun is to use ColumnExpr(...).Join(...).JoinOn(...) which is pretty easy to break and more verbose


Yellow Box warning package needs 'requires main queue setup' when running react-native-barcode-creator

First thank you for building this package.
With latest expo when using this package the following warning is displayed:
Module BarcodeCreatorViewManager requires main queue setup since it overrides `constantsToExport` but doesn't implement `requiresMainQueueSetup`. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.

To fix this I believe you can do the following (after reading this link, https://github.com/react-native-share/react-native-share/issues/330)
After the function constantsToExport in file BarcodeCreatorViewManager.swift

    @objc
    override func constantsToExport() -> [AnyHashable : Any]! {
        return ["AZTEC": "CIAztecCodeGenerator",
                "CODE128": "CICode128BarcodeGenerator",
                "PDF417": "CIPDF417BarcodeGenerator",
                "QR": "CIQRCodeGenerator",
                "EAN13": "CIEANBarcodeGenerator",
                "UPCA": "CIEANBarcodeGenerator"
        ]
    }

add:
@objc override func requiresMainQueueSetup() -> Bool {
    return true
}

tested this works correctly, warning removed


Don't build the entire project for every package separately

Currently every crate is separated into its own package and recipe, and the entire thin-edge.io source code is downloaded and build from scratch for every package (9 at the time of writing).
This happens because of how Yocto handles tasks. Our 9 tasks have, among others, 3 main tasks: do_fetch, do_compile, and do_install. First two tasks are the same for every package (download source code from the same URL, then run cargo build which produces the same target directory). do_install is almost the same, it takes binaries from target directory and installs them to the holding area, from which they will be later packaged.
One possible way to resolve it would be to create a package tedge-source, which will fetch thin-edge.io and compile it, and then have the rest of the packages depend on do_compile task of tedge-source.
Yocto manual section for splitting application into different packages:
https://docs.yoctoproject.org/dev-manual/common-tasks.html#splitting-an-application-into-multiple-packages

Right now, the layer should pass all the tests in Connect_to_c8y.robot file, at least on my machine. Before merging, it would be good for other people to run the tests and confirm that they're working, and either propose more test cases, or give the final OK for the merge.


Propogate endpoint option to bugsnag plugin

Hi,
I see in the docs you have an option for endpoint to be set for bugsnag enterprise edition, but it doesn't seem to actually be implemented.  I've created a PR to implement it.
Thanks,

Thanks @mprobber. I appreciate it! 😛

no problem! mind doing an npm release?

Done. Thanks again.


Public federation endpoint with publicly-trusted SSL certificate

We should include in the FAQ so customers understand their SAML 2.0 Identity Provider endpoints and metadata must be publicly accessible and using a publicly trusted SSL certificate. I support customers that like to keep their federation service private and use SSL certificates from their internal PKI. Doing this results in 500 error at sign-in.

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

ID: 78e335b4-325c-7971-a8ed-24694a143ced
Version Independent ID: 78e335b4-325c-7971-a8ed-24694a143ced
Content: FAQs about using SAML 2.0 in Power Pages
Content Source: power-pages-docs/security/authentication/saml2-faqs.md
Service: power-pages
GitHub Login: @dileepsinghmicrosoft
Microsoft Alias: dileeps

Thanks for your feedback. We've added a note to the documentation: Set up a SAML 2.0 provider. Closing the issue.


failed too many times

I want to copy data from on cluster to another mongo, but when try to run the connection seem failed. I can assure connect to both cluster. Here is the error I've got.
connect=True, replicaset='rs0', tls=True), 'databasename'), 'collection_names') failed too many times in retry_until_ok Traceback (most recent call last):   File "/usr/local/lib/python3.6/site-packages/mongo_connector/util.py", line 79, in retry_until_ok     return func(*args, **kwargs)   File "/usr/local/lib64/python3.6/site-packages/pymongo/collection.py", line 3164, in __call__     "exists." % self.__name TypeError: 'Collection' object is not callable. If you meant to call the 'collection_names' method on a 'Database' object it is failing because no such method exists.
I'm using mongo-connector version 3.1.1 and pymongo version 4.1.1.
Can anyone point me in the right direction?

I'm resolving this by downgrading pymongo version to 2.9


[BEAM-7529] Add Sums.ofFloats() and Sums.ofDoubles()

Fix [BEAM-7529].

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

@dmvk Will you have a look at this please?


[DOC] write documentation

As the codebase is getting a bit larger, documentation might be needed within the files to simply describe what each of them do.

Standard comment for each function (Copilot should be fine)
Issue #19 should fix this for the play command at least, while also implementing refactoring from #16 (util functions for the play command)


TTS Support

Any chance you might be able to add TTS support?

This was added: ./chatgpt-cli text-to-speech

Thanks!


Read in parallel

h5py parallel.
There is already is read.py a way to read "chunks" of the data. For example from event 0 to 99.
Can we have an example with 4 threads (?) reading simultaneously from 0-99, 100-199, etc.?

https://docs.h5py.org/en/stable/mpi.html

I tried to do this with pythons built in multiprocessing.Pool function and it does not work because h5py File objects can not be pickled. The error can be recreated in this notebook.
I read through the h5py mpi docs link above and it seems like it needs some extra modules installed. I will look into those more and try to utilize them!


⚠ Bofrost.hr has degraded performance

In a066f1e, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 3341 ms

Resolved: Bofrost.hr performance has improved in ea6fbcc.


runtime: improve error handling path for the runtime

Rather than use fprintf for the error handling path use the platform
specific error handling systems (asl_log, __android_log_printf) if
available.  The standard file streams are not available on all platforms
(e.g. Android).

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @mikeash

@swift-ci please test

Good idea!

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows platform


Rerender

It seems the coin-or stack needs a rebuild for https://github.com/conda-forge/or-tools-feedstock/pull/24, presumably because all packages built for libprotobuf 3.21 have been built against a newer zlib.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Add DraftBox Themes

Please add DraftBox themes to JAMstack Themes

@slavakurilyak Please do a PR with your theme, the instructions are in the README


Relocatable .pc files

While trying to fix https://github.com/ruslo/hunter/issues/375 I hit the problem with non-relocatable *.pc files, i.e. path to package is hardcoded there. Does anybody know how to make all paths in *.pc relative to the current directory?
@pretyman I remember you have some similar problems before. What is your experience?
Not related directly to relocation problems but I've found some information that might be useful:

https://cmake.org/pipermail/cmake/2008-November/025050.html

We should clean PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR and prefer PKG_CONFIG_LIBDIR in autotools helper module (?)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/32660301-relocatable-pc-files?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github).

Have no idea now does it relates to the problem or not, just for the record:

http://patchwork.ozlabs.org/patch/595275/

We should clean PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR

See:

https://github.com/ruslo/hunter/pull/378

I recall having similar problems with libtool *.la files, and they needed absolute paths in them, as libtool did not allow relative paths inside of its .la files. This was described in https://github.com/ruslo/hunter/issues/218 . I don't know pkg-config, but it seems to suffer from a similar problem.
Your solution of cleaning the vars is the best.

This was described in #218

Okay, thanks for the reference I lost it :) So effectively I've implemented this approach: https://github.com/ruslo/hunter/issues/218#issuecomment-130233161 but with different variable names. Will substitute names for something more general.

Fixed by: https://github.com/ruslo/hunter/commit/e3430ac72142d4f2914e7e0b885287ab54e50091


scatter_add throws shape checking error (probably bad arguments)

While trying to use jax.lax.scatter_add, I ran across a shape-checking error that jax asked me to report. Here is a repro:
operand = np.ones((3,3,6), dtype=np.float32)
update = np.zeros((3,3,2), dtype=np.float32)
indices = np.array([0,1,2,3,3,3])
jax.lax.scatter_add(update, indices, operand, jax.lax.ScatterDimensionNumbers((0,1),(0,1),(2,)))

This is probably a bad use of scatter_add, because I don't yet understand how to use it, but it appears it should still not crash in the way that it does.

Thanks, yes, after I ran into this I figured out that index_add is actually the function that I want. The error message it throws doesn't really bother me, I just reported it because the error message asked me to.


Vite's config setting resolve.conditions isn't respected when recursing through dependencies.

Describe the bug
When vitest is recursing through the dependencies in node_modules it loses track of the resolve.conditions setting, meaning that nested imports with conditional exports resolve to the wrong file.
Reproduction
https://github.com/thislooksfun/vitest-mre
System Info
Not relevant to the bug.

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Vitest also doesn't respect Vite's default resolve.conditions — if you load the linked MRE and comment out the resolve.conditions in the vite.config.js file then both tests will fail — but that might be better reported as a separate issue.

Use test.deps.inline for node_modules, if you need to apply Vite transforms to it.

but that might be better reported as a separate issue.

This is nog a bug, Vitest processes files with SSR flag, which mean browser condition is not respected. This is intentional - a lot of dependencies will just not work with browser field in Node.

Ok, that's a decent reason to have different defaults, but it's not actually a response to this bug. If you look at the MRE I made, the "shallow" import DOES respect resolve.conditions, while the "deep" import DOES NOT. Either way this is unintended behavior, and is not surfaced to the user in understandable ways.  Either fully respect resolve.conditions or don't respect it at all.

We respect resolve.condition for all processed files. node_modules files are not processed by default, and their execution is delegated to Node for performance reasons. If you need to process them, use test.deps.inline, as I already said.
If there is a way to provide condition to Node directly, we could add it.


Use inspect.signature

inspect.getargspec is deprecated. _argnames now uses inspect.signature.
This commit also changes the behaviour to be more consistent. The
previous commit would strip self from the arguments, but only when no
default arguments were passed.
This PR fixes #23

Closing as superseeded by #38. Thanks even though!


Create model config files representing all reasonable configurations

As a first step, I'm starting a table of all input data and currently available years in electricitylci in DataYears.md. I intend to add years for all other datasets. This table, along with an understanding of possible constraints of using different datasets together, is how I propose to determine possible config files. @jump2conclusionsmatt @TJTapajyoti

@TJTapajyoti @jump2conclusionsmatt Would somebody be willing to take this task over, or at least the part to populate DataYears.md, with the EIA, fuel mining and transport LCI, etc, to complete this table?

@jump2conclusionsmatt Please take a look at the DataYears,md and help me with some of the dates. CAN imports is missing. For EIA sources, I only included the years used in model 1 and 2. But the point of these is to determine the years at least from 2010 to present that the code would work for to grab that data

Just want to put my plan out there to see if it aligns with your expectations of reasonable.

I plan on eliminating the various combinations of emissions data years (i.e., we wouldn't want 2014 eGRID, 2016 NEI, 2011 RCRA, 2015 TRI). It would be eGRID, NEI, TRI, CEMS 2016, RCRA 2015 or 2014/2013.
EIA files - I think we would want to be able to apply these inventories to different years of generation data (if replacing eGRID). So any combination above with any EIA data year. This would allow an assessment of the contributions of inventory vs. generation.
Consumption mix to match EIA data, but this appears to be the most limiting dataset. Can do the 2014 mix using Hottle et al - and thus limit to eGRID or NERC regions? And then jump back to 2016+ for the IO consumption mix, limited to BA/FERC/US.
T&D losses to align with EIA year.

@jump2conclusionsmatt . I intend the DataYears table only to be a record of all eachs for each source independently.  Then there is another step in actually deciding what feasible models are. So first, if you don't mind populating that table, then we can work on that next step.

I think I'm done making changes to DataYears.md. Started yesterday and finished today by making a test script to run through EIA data to see where things break, mostly due to column names changing.

I'm retracting my proposal to make all these model config files. I think its interesting for testing purposes but beyond the scope of what we currently have on our plate. That said I want us to continue to populate the DataYears table as data for new years become available. @jump2conclusionsmatt @TJTapajyoti


Exposing the inner ref of an element via BlazorComponent returns an emtpy(?) ref

I have a component that inherits from BlazorComponent with this code:
protected override void BuildRenderTree(RenderTreeBuilder builder)
        {
            base.BuildRenderTree(builder);
            builder.OpenElement(0, TagName);
            foreach (var param in _attributesToRender)
            {
                builder.AddAttribute(1, param.Key, param.Value);
            }
            if (_classname != null) builder.AddAttribute(1, "class", _classname);
            builder.AddElementReferenceCapture(2, capturedRef => { ElementRef = capturedRef; });
            builder.AddContent(3, _childContent);
            builder.CloseElement();
        }

It's used like so:
<form onSubmit={this.alertValue}>
    <Dynamic TagName="input" ElementRef="@inputRef" />
        <button type="button" onclick="@OnClick">
            Submit
        </button>
</form>

@functions {
    ElementRef inputRef;

    async void OnClick()
    {
        await inputRef.AlertValue();
    }
}

Which ultimately prints out to the console what the ref is. Like so:
 public static class ElementRefExtensions
    {
        public static async Task AlertValue(this ElementRef elementRef)
        {
            await JSRuntime.Current.InvokeAsync<bool>("blazorousSample.alertValue", elementRef);
        }
    }

window.blazorousSample = {
    alertValue: function (element) {
        console.log("element: %O", element);
        alert(element.value);
    }
};

One the javascript console I get:
{
  "_blazorElementRef": null
}

@AndreasTruetschel is correct. You will need bind-something for this to work, otherwise this line of code:
builder.AddElementReferenceCapture(2, capturedRef => { ElementRef = capturedRef; });

... is only writing to its own ElementRef property, not to the corresponding property on the caller.
Since you're writing your component in raw C# instead of Razor, you'll have to figure out what C# code is equivalent to the bind-something that Razor would generate.

I believe this should be added to the official Input[*] components that are meant to be used with EditForm. I recently wanted to build a word processor for a complicated form and took me a whole day to find and form a working solution


unify pipelines

Create new testing pipeline that would include build from the source step

This continues the work from #117  and #134
Pending tasks from those two:

remove neu-pre and similar stuff from names of resources
simplify names or values of certain other things
splitting integration testing into two parts: functional tests and package tests


Flush out manual process for synching FTA <> MyRange when FTA endpoint is not working

What seems to work (once table output from FTA is JSON-ified) is to run import.js locally against port-forwarded db.  Not super quick or automated but if we are stuck can be done.


Bump version to v0.18.0

This version makes this package compatible with Meilisearch v0.28.0 :tada:
Check out the changelog of Meilisearch v0.28.0 for more information on the changes.
💥  Breaking Changes

Actions that create a task in Meilisearch now return a TaskInfo and not a Task object anymore. (ex: add_documents). #299
get_tasks now returns a TasksResults where the tasks are contained inside the results field. #299
task_id in Task andTaskInfo is now a u32 instead of a u64 #299
index_uid in Task and TaskInfo is now optional. #299
Following taskTypes are renamed: #299

documentPartial -> documentAdditionOrUpdate
documentAddition -> documentAdditionOrUpdate
clearAll -> documentDeletion

Possibility to filter the tasks when using get_tasks on indexUid, status and type. #299
The returned keys when using get_keys_with get_keys or get_key now returns an additional field uid. #313
The response from get_keys_with and get_keys is now a KeysResults instead of Vec<Key>. #313
update_key only accepts updates on the description and the name #313
client.get_indexes now returns a IndexesResults instead of a Vec<Index> #315
client.get_indexes_raw now returns a Value instead of a Vec<Value>#315
Index structure:  #315

uid is now a string and not a Arc<string> and is public
client is now public
primary_key is now public
name field is removed

In SearchResults nbHits is now named estimated_total_hits #316
In SearchResults exhaustive_nb_hits is removed. #316
In SearchResults exhaustive_facets_count is removed. #316
In SearchQuery matches is now named show_mathes_position and the method with_matches is now named with_show_matches_position #316
In SearchResults matches_info is now named matches_position #316
In SearchQuery facetsDistribution is now named facets #316
In SearchResults facetsDistribution  is now named facetDistribution  #316
client.get_documents and client.get_documents_with now returns a DocumentsResults instead of a Vec<T> #315
client.get_documents has no filtering parameters anymore, use get_documents_with to filter.
// Todo get document
in client.generate_tenant_token, apiKeyPrefix is now named apiKeyUid and expects the uid of the signing API key as a value. The prototype of the function changed accordingly. #318
Method get_dump_status does not exists on Dumps anymore  #319
create_dump now returns a TaskInfo instead of a DumpInfo #319
Remove the sync feature and use Arc everywhere by default (#251) @irevoire

🐛 Enhancements

Creation of a method client.get_tasks_with and a struct TasksQuery based of this that lets you filter tasks. #299
Creation of client.get_keys_with() that lets you paginate on limit (default: 20), offset (default: 0). #313
create_key accepts a custom name.  #313
client.get_indexes_with takes as argument IndexesQuery giving you the possibility to set limit and offset. #315
client.get_indexes_raw_with takes as argument IndexesQuery giving you the possibility to set limit and offset. #315
IndexUpdater struct gives you the possibility to create an instance of all the fields you would like to change in an Index  and then execute the update: `IndexUpdater::new(&client).with_primary_key("my_id".to_string()).execute().await) #315
IndexesQuery struct allows you to define the filtering applied during the get_all_indexes_with call. #315
new method client.get_documents_with takes as argument DocumentsQuery giving the possibility to set limitm offset and the fields that you want to see in the returned documents (default: all fields). #315
new method index.get_document_with takes as argument DocumentQuery giving the possibility to chose the fields you want to see in your returned documents. #326

Thanks again to @bidoubiwa, @abhizer ! 🎉

The returned keys when using get_keys_with get_keys or get_key now returns an additional field uid. https://github.com/meilisearch/meilisearch-rust/pull/313

and name field :)

update_key only accepts updates on the description and the name https://github.com/meilisearch/meilisearch-rust/pull/313

You can apply the code styling to description and name :)

What's the pattern here?

In SearchResults matches_info is now named matches_position https://github.com/meilisearch/meilisearch-rust/pull/316
In SearchResults facetsDistribution is now named facetDistribution https://github.com/meilisearch/meilisearch-rust/pull/316

Why do we have both camelCase and snake_case for these fields?

// Todo get document

Remove this? Or fix it?

The prototype of the function changed accordingly

Can you add the prototype in the release notes?

Method get_dump_status does not exists on Dumps anymore

What about: Removed get_dump_status on Dumps struct.

create_key accepts a custom name

And a custom uuid, correct?


Can't upgrade to Babel 6

I tried to install the latest Babel 6 since I'm starting a new project. When I installed the latest Babel to my devDependencies the two simple test kept failing. So I removed them from my devDependencies and it worked. I wrote my actual tests now and well, I need Babel to run my code.
Is it normal behavior to break AVA if I install the the updated Babel to my devDependencies?

We don't support Babel 6 yet: https://github.com/sindresorhus/ava/issues/117


When using inference.py I meet this package problem.Could this be related to changing the torch version to 2.0.1 for CUDA 11.7?

It should be related to some package version issues. What it the version of your transformers and huggingface_hub?

It should be related to some package version issues. What it the version of your transformers and huggingface_hub?

The vresion of transformers is 4.37.0 and huggingface_hub is 0.23.4

Can you try this https://github.com/huggingface/transformers/issues/15062#issuecomment-1821349949 ?

Can you try this huggingface/transformers#15062 (comment) ?

Thanks，I will try it

Can you try this huggingface/transformers#15062 (comment) ?

Thank you，It works and no longer reports this error!


Reactive Modules API (proposal)

Posted here for discussion:
Reactive modules
A module related with a <JavaScript> tag supports the Reactive Modules API. This is a set of methods on module that allows the module to change the exported values and notifying the data context about the change. This allows reactive programming between modules.
Each of these APIs accept a path to the node in the exports tree. The path is a sequence of either string keys (to look up into objects) or number indices (to look up into arrays).
module.set(... path, value)
Sets the value at the path to value. Example:
exports.foo = [ {bar: "apples"}, {bar: "oranges"}]

exports.changeSomething = function() {
	// Changes the 'bar' property of the second item in the 'foo' array
	module.set("foo", 1, "bar", "bananas");
}

module.add(... path, item)
Adds item to the end of the array at the path. Example:
exports.user = { name: 'Bob', things: ["lamp", "car"] }

exports.addSomething = function()
{
	// Adds 'airplane' to the user's list of things
	module.add("user", "things", "airplane");
}

module.removeAt(... path)
Removes the item at the path. The last item in the path must be a numeric index into an array. Example:
exports.user = { name: 'Bob', things: ["lamp", "car"] }

exports.removeSomething = function()
{
	// Removes 'lamp' from users's list of things
	module.removeAt("user", "things", 0);
}

module.insertAt(... path, value)
Inserts value at the path. The last item in the path must be a numeric index into an array. Example:
exports.user = { name: 'Bob', things: ["lamp", "car"] }

exports.insertSomething = function()
{
	// Inserts 'dog' in the middle of the user's list of things
	module.insertAt("user", "things", 1, "dog");
}

I think we should go for a more natural API than this variables arguments syntax (though lacking ES6 we have to lose a few niceties).
For example:
module.get("user").get("things").add("airplane")

You can store this accessors as variables (they look like observables, but are actually just wrappers to modify the backing data)
var user = module.get("user")
user.get("things").insertAt(1, "dog")

I'm not sure get is the correct name, mabye val or var instead. But the syntax is a lot more readable. I can understand what is happening here.

@COCPORN and myself spent 3 months this spring evaluating different API designs, and concluded that the variable arguments one is the nicest, for various reasons. It is easy to build the API you are proposing (and many other APIs) on top as an abstraction layer. This is the low-level API with the minimal JS->Native API surface and overhead.

For example, with this low-level API it is easy to build a differ-based component system similar to Angular

The propsed API looks totally fine to me :)

I'd prefer to have the path argument be an array rather than leaning on arguments again. This makes a path a type, simplifies the method signature, and lets a path be referenced instead of done with literals or currying, if that is a design choice I want to make.
I also think it will teach and document better.
module.set(["foo", "bar"], true);

Other than that I think this is golden.

Again, this can be a convenience API on top. I want to keep the base API as minimal as possible

I feel like the varargs based API is actually less convenient and performs more work in terms of manipulating the arguments

I have to agree with @Sunjammer here. Doing it with an array seems a lot less magical.

Candidate implementation found here: https://github.com/fusetools/fuselibs-public/pull/208

I think this looks really weird:
module.removeAt(["foo", "bar", 1])
The array looks very redundant then

Well, that messes it up, as 1 is part of the path. That would be very inconsistent

Not if you imagine the path as terminating at an array, removeAt as a function that operates on arrays, and 1 to be the operand (ie the index at which to remove). Then your statement is the straightforward do X to the item at path Y using argument Z.
This is consistent: At path X, set Y. At path X, remove at index Y. At path X, insert Y at index Z.

Well I'm still in favor of the varargs api.
A rewrite would mean this feature not making it to 1.2 as that deadline is tonight.

There is no issue introducing an "overload" later that accepts an array for path. No difficulties creating a wrapper api on top either.

Yep, that can be easily implemented at a later point as checking if argument 0 is an array anyway

More of a question, but how would you handle a bit more complex structure?
Something like this:
exports.list = [
	{
		userId: 12,
		userName: "User 1",
		properties: {
			permissions: ["read"],
			groups: [222, 333, 444]
		}
	},
	{
		userId: 15,
		userName: "User 2",
		properties: {
			permissions: ["read", "write", "execute"],
			groups: [222, 333, 444]
		}
	}
];
exports.addGroupToUser() = function(userId, groupId) {
	// how would I add group 555 to userId 15?
}

@eksperts :
With the raw API, that would be something like
module.add("list", exports.list.indexof(...), "properties", "groups", groupId)

However, the intention is not for this API to be used much directly. It is meant as a low-level API that we build other features on top.
For example, something like:
var Component = require("FuseJS/Component")

Component(module, function() {
     this.list = [ ... ]
     this.addGroupToUser() {
        // Here, simply modify the list, and the component will update automatically through diffing
     }
})

Hence, I'm not too worried about what the low-level API looks like, as long as it is lighweight and general purpose.

Note that in the above example, Component can be implemented as a pure JS utility class

Alright, no objections. I see a point in @Sunjammer's argument, but other than that it's legit!

I just looked at the PR for this and am concered about adding these simple names directly to the module object. I know it's our object, but seeing sometihng like module.set and module.add makes it seem so "standard", yet it's not.

Does this use of exports prevent anything else from being put in the exports?  Can I still add callback functions as normal? Or can I use an OBservable as well?

The examples only go one-level deep with the JS object trees. IS an arbitrary depth intended?

makes it seem so "standard", yet it's not.

I agree, however, rooted modules in <JavaScript> tags are special, its not vanilla CommonJS, so it doesn't hurt to let it show. The modules have a life time, interact with the data context, can be instantiated multiple times etc. We already have module.disposed. It is the natural place to put things.

The examples only go one-level deep with the JS object trees.

Yes

Does this use of exports prevent anything else from being put in the exports? Can I still add callback functions as normal? Or can I use an OBservable as well?

You can use Observables anywhere, like before. No feature regression

I'm not clear on how I share state between modules.  I have a list of users that I will need to display in multiple pages. I additionally have shared user objects in that list. They also have to appear on their on other pages.  I don't see how this is done in this framework.

I'm not clear on how I share state between modules.

You have to use the dependency injection feature to acheive that:
<JavaScript dep:users="{users}">
This imports the users list from the data context

This means any structures I wish to store have to be exported at the root of the app. I'm not sure I like that since it makes modularization more difficult.
How do I export part of that structure in another module then, that is share the data?
<JavaScript dep:users="{users}" dep:param="parameter()">
    exports.user = users[param.user_id]

This means any structures I wish to store have to be exported at the root of the app.

Not true - you can mount this at any level in the tree.

This makes modularization easier as the data is tree-local. For example, a component can expose local data that is used within its subtree only.

How do I export part of that structure in another module then, that is share the data?

Didn't understand the question

   exports.user = users[param.user_id]

Alternatively:
<JavaScript dep:user="{users[parameter().user_id]}">

What I mean is that any value I wish to use in sibling components must be mounted at a higher level.
If I do <JavaScript dep:user="{users[parameter().user_id]}"> will this be a proper two-way binding to this object?
How can I do a similar binding at the JS level?
I'm missing the insight into how one actually structures the data of an app using this system.
Another example, in the apps I've written so far I have something like a user DB stored in memory. You call a JS function getUser(id) that provides an Observable for that user. I don't see how to create such a function with this new system.

What I mean is that any value I wish to use in sibling components must be mounted at a higher level.

Yes, this creates a natural component-local data sharing scheme. If you want true globals, nothing is stopping you from doing the old :Bundle and require() trick.

If I do  will this be a proper two-way binding to this object?

This is a one-way binding, but you will get the actual object and are free to modify it. However, this won't call the reactive module API, so any changes you do remotely won't be reflected. Mutation of imported state should happen through functions exported by the owning module.

How can I do a similar binding at the JS level?

You cannot. This is what the dependency injection system is for.

I'm missing the insight into how one actually structures the data of an app using this system.

We have detailed plans for this. Once this is merged we can write new best practices docs.

Another example, in the apps I've written so far I have something like a user DB stored in memory. You call a JS function getUser(id) that provides an Observable for that user. I don't see how to create such a function with this new system.

You can still provide observables if you wish, but the whole point is to reduce reliance on observables.
In this system you would for example do ` . In the future when we have a UX syntax for calling JS functions, you can even call the function with a reactive expression.

The high level recommended structure is as follows:
<App>
	<JavaScript>
		// This is the main state container module - like a redux store
		// it contains and exports all the app-global state, and exports
		// functions for all the possible transactions

		exports.things = ["one", "two", "three"]

		exports.addThing(thing) {
			module.add("things", thing)
		}
	</JavaScript>
	<Navigator>
		<Page>
			<JavaScript dep:things="{things}" dep:addThing="{addThing}" >

				// This module can compute derived state used locally on this Page
				export.thingCount = things.length

				export.buttonClicked = function() {
					addThing("lol")
				}
			</JavaScript>

How does one bridge from a require module into this system? Say I have a user module that I want several components to have access to. How do I actually structure this sharing?
Try to extend your example to include several modules. Say we have three modules, user, task and config. How would we instantiate all three of these and provide them to a component?

Something like this?
<App>
	<JavaScript>
		exports.user = require("MyApp/user")
		exports.task = require("MyApp/task")
		exports.config = require("MyApp/config")
	</JavaScript>
	<Navigator>
		<Page>
			<JavaScript dep:user="{user}">
				...

The nice thing about this is that now it is easy to mock the environment for the script in the page for testing purposes.

If you want the modules to have access to the data context, you can do:
	<JavaScript File="MyApp/user.js" />
	<JavaScript File="MyApp/task.js" />
	<JavaScript File="MyApp/config.js" />
	<Navigator>
		<Page>
			<JavaScript dep:user="{user}">
				...```

Okay, after a long discussion in chat with @mortoray we've decided to redesign this feature slightly.
I will open a new ticket to discuss the new proposed design.


How to resume training from last checkpoint

Hi,I came across your work on instance segmentation and I am currently trying to reproduce the results.I was previously able to train the model for 90,000 iterations but when I tried resuming the training from the last checkpoint,I ended up getting some errors related to not properly loading the configuration file.
as i am new to detectron2,could you provide pointers on how to resume training from existing checkpoint.Does the resume option expect a cfg file as an argument or does it expect a model weights?
thanks

CUDA_VISIBLE_DEVICES=0,1,2,3 python train_net.py --num-gpus 4 --dist-url tcp://<IP_ADDRESS>:10345
--config-file configs/coco/panoptic-segmentation/mask2former_R50_ppm-fpn_x9.yaml
--resume MODEL.WEIGHTS output/mask2former_r50_ppm-fpn_coco-pan_bs16_50ep_decx9/model_0334999.pth

CUDA_VISIBLE_DEVICES=0,1,2,3 python train_net.py --num-gpus 4
--config-file /path/to/your_config.yaml
--resume MODEL.WEIGHTS /path/to/existing_checkpoint.pth

hmmm tried that but instead of resuming from iteration 70,000K it restrarted training from iteration 0.


Datasources are not created in time

Since the data source resource is added last the resolver complains that it is not available.
aws:appsync:Resolver (api-get-campaign-query-resolver):
    error: Plan apply failed: error creating AppSync Resolver: NotFoundException: No data source found named campaigns
        status code: 404, request id: fdb308ef-c0f5-11e9-b5e1-abf56298794b

:tada: This issue has been resolved in version 1.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add function(s) to create basic Record from WarcFile

As it says, add function(s) to create basic Records from WarcFile objects. Has an option to automagically create the WARC-Record-ID and the WARC-Date header fields.

Fixed in bb8b83e18a2ed83069a059c25e148d73144300fa


Question about EntityPlayer location.

Everytime i start the game the player is located at the top-left corner of the map.
Someone knows where the problem is?
Screenshot:
Editor: http://puu.sh/kw1ol/069f3910e3.png
Ingame: http://puu.sh/kw1py/02f60a1151.png
Greetings
Navo

@nxxv0 are all those blocks behind the character colliders?

Nevermind, i found my problem.
I changed something in the impactplusplus code directly, so i broke the player spawning :)


use generated bundle.dockerfile; remove bundle from .dockerignore

- Description of the problem which is fixed/What is the use case
When building manually (using make targets and setting env vars) the output is a bundle that still points to the production image for the operator.  This is because the bundle-build uses the bundle-custom.Dockerfile which has the production values hard coded.
- What I did
Change the bundle-build target back to using the generated bundle.Dockerfile so it respects set env vars and includes the respective operator image.  Also had to remove "bundle" from .dockerignore so that the docker build can succeed.
- How to verify it
make bundle-build
install the operator using that bundle
Verify it is using the expected operator image for the controller pods
Closes: https://issues.redhat.com/browse/KATA-1828

bundle.Dockerfile is a generated file, but it is also tracked in git. Running make clean on a pristine tree removes it and you end up with a non-empty git diff which is quite confusing... what is the rationale with this file ?

I need to point the prow job to bundle-custome.Dockerfile before this gets merged.  I will create a PR for that.

PR for prow https://github.com/openshift/release/pull/33681


Support Intel Arc GPUs / Xe Cores

Description
Easier said but done, I know, but: I'd love support for Intel's Arc GPUs.
Additional Information
No response

Hi @Pandapip1, thanks for the request. Currently, CuPy's design heavily depends on CUDA's semantics, so there would be significant work unless such a layer is provided (e.g., HIP for AMD GPUs).

Intel Python have their own array library: https://intelpython.github.io/dpnp/reference/comparison.html

cc: @oleksandr-pavlyk (in case you have suggestions 🙂)

I just found VUDA, which translates CUDA calls into Vulkan calls, which are supported by Intel Arc GPUs.

Hi @Pandapip1, thanks for the request. Currently, CuPy's design heavily depends on CUDA's semantics, so there would be significant work unless such a layer is provided (e.g., HIP for AMD GPUs).

chipStar (https://github.com/CHIP-SPV/chipStar) is such a layer, it provides a compiler from HIP/CUDA to OpenCL/Level Zero. Maybe some dependencies could pose a problem, but overall it could work.

For those interested, I've posted a PoC using chipStar: https://github.com/cupy/cupy/pull/8700


3.16.0 release

release notes
3.16.0 (2018.07.12)

Add User-Agent to request headers (#118)
Fix actions.update ignoring options.exec.image parameter (#121)

process

npm version patch to bump package.json to 3.16.0
Push version commit and git tags to Github
Travis CI will auto-publish new version to NPM
Draft Github release from tags with notes above.

@jthomas it looks like 3.16.0 has not been published to NPM yet. Have you updated your tokens on the CI system?

Good catch @trieloff. I can't see anything in the travis logs to see where the issue might be.
@csantanapr would you be able to have a look at this?

@csantanapr nudge welcome back ;)

I will refresh the token to see if that’s the fix.

You might need 2fa.

2fa it’s opt in
On Fri, Jul 27, 2018 at 5:03 PM rodric rabbah<EMAIL_ADDRESS>wrote:

You might need 2fa.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-openwhisk-client-js/issues/123#issuecomment-408538218,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABC03gCrLh9DooeiKnPJXhO2USYnlxRwks5uK4ArgaJpZM4VNRqv
.

It’s looks like I can use 2fa in CI more info here https://docs.npmjs.com/getting-started/requiring-2fa-for-package-publishing-and-modification


[SPARK-32287][TESTS] Flaky Test: ExecutorAllocationManagerSuite.add executors default profile

What changes were proposed in this pull request?

I wasn't able to reproduce the failure but the best I can tell is that the allocation manager timer triggers and call doRequest. The timeout is 10s so try to increase that to 30seconds.
Why are the changes needed?

test failure
Does this PR introduce any user-facing change?

no
How was this patch tested?

unit test

@Ngone51

Test build #126506 has started for PR 29225 at commit 3af6ab9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31125/
Test PASSed.

thanks @dongjoon-hyun if you see this failing again let me know and I'll try to reproduce again. I ran it in a subset of the tests in a loop and wasn't able to reproduce locally.

Sure~ I'll monitor on GitHub Action result. Thanks.

Test build #126506 has finished for PR 29225 at commit 3af6ab9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126506/
Test PASSed.

Late LGTM. Thank you @tgravescs

Thank you @tgravescs for fixing this.

I saw this again:
[info] - add executors default profile *** FAILED *** (38 milliseconds)
[info]   4 did not equal 2 (ExecutorAllocationManagerSuite.scala:132)
[info]   org.scalatest.exceptions.TestFailedException:
[info]   at org.scalatest.Assertions.newAssertionFailedException(Assertions.scala:472)
[info]   at org.scalatest.Assertions.newAssertionFailedException$(Assertions.scala:471)
[info]   at org.scalatest.Assertions$.newAssertionFailedException(Assertions.scala:1231)
[info]   at org.scalatest.Assertions$AssertionsHelper.macroAssert(Assertions.scala:1295)
[info]   at org.apache.spark.ExecutorAllocationManagerSuite.$anonfun$new$7(ExecutorAllocationManagerSuite.scala:132)
[info]   at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
[info]   at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
[info]   at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[info]   at org.scalatest.Transformer.apply(Transformer.scala:22)
[info]   at org.scalatest.Transformer.apply(Transformer.scala:20)
[info]   at org.scalatest.funsuite.AnyFunSuiteLike$$anon$1.apply(AnyFunSuiteLike.scala:189)
[info]   at org.apache.spark.SparkFunSuite.withFixture(SparkFunSuite.scala:158)
[info]   at org.scalatest.funsuite.AnyFunSuiteLike.invokeWithFixture$1(AnyFunSuiteLike.scala:187)
[info]   at org.scalatest.funsuite.AnyFunSuiteLike.$anonfun$runTest$1(AnyFunSuiteLike.scala:199)
[info]   at org.scalatest.SuperEngine.runTestImpl(Engine.scala:306)

with:
[info] - add executors capped by num pending tasks *** FAILED *** (77 milliseconds)
[info]   6 did not equal 5 (ExecutorAllocationManagerSuite.scala:428)
[info]   org.scalatest.exceptions.TestFailedException:
[info]   at org.scalatest.Assertions.newAssertionFailedException(Assertions.scala:472)
[info]   at org.scalatest.Assertions.newAssertionFailedException$(Assertions.scala:471)
[info]   at org.scalatest.Assertions$.newAssertionFailedException(Assertions.scala:1231)
[info]   at org.scalatest.Assertions$AssertionsHelper.macroAssert(Assertions.scala:1295)
[info]   at org.apache.spark.ExecutorAllocationManagerSuite.$anonfun$new$18(ExecutorAllocationManagerSuite.scala:428)
[info]   at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
[info]   at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
[info]   at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[info]   at org.scalatest.Transformer.apply(Transformer.scala:22)
[info]   at org.scalatest.Transformer.apply(Transformer.scala:20)
[info]   at org.scalatest.funsuite.AnyFunSuiteLike$$anon$1.apply(AnyFunSuiteLike.scala:189)
[info]   at org.apache.spark.SparkFunSuite.withFixture(SparkFunSuite.scala:158)
[info]   at org.scalatest.funsuite.AnyFunSuiteLike.invokeWithFixture$1(AnyFunSuiteLike.scala:187)
[info]   at org.scalatest.funsuite.AnyFunSuiteLike.$anonfun$runTest$1(AnyFunSuiteLike.scala:199)
[info]   at org.scalatest.SuperEngine.runTestImpl(Engine.scala:306)
[info]   at org.scalatest.funsuite.AnyFunSuiteLike.runTest(AnyFunSuiteLike.scala:199)

at https://github.com/apache/spark/pull/29278/checks?check_run_id=930261611. I am retriggering.
I will monitor a bit more and update here. If the flakiness is very rare, it would be fine for now.

It would be really nice if we could get some timestamps on how long tests were taking

Oh it shows wthe timstamps when you download the log. I'll share the timestamps too later when I happene to see this again.


Collection hooks not fired when restoring document

Link to reproduction
No response
Describe the Bug
When I restore an older version of a document I would expect that the collection hooks are executed, for me this is not the case. If I have a collection with a beforeChange or beforeOperation hook none of them is called when I restore an older version of a document in that collection.
Going through the documentation about versioning and the other issues here it seems to me that this is not a bug rather than there is just no option to hook into  the process of restoring a version of a document. Is that correct?
If not what options do I have to execute code before a version is restored in order to block the user from restoring a specific version in case that this version contains data that is outdated.
To Reproduce
Create a collection, add beforeChange or beforeOperation hooks with some logging output to be able to see when they are called. Create a document for that collection in the admin ui. Update that document a couple of times so that there are multiple versions of it. Open the versions history and restore one of the older versions.
beforeChange nor beforeOperation are called.
Payload Version
2.8.2
Adapters and Plugins
No response

Any news on this one?

I think we should add beforeOperation and afterOperation. This should be done in v3 as it could be considered a breaking change. Having beforeOperation currently in your project you might not expect this code to run on restore, this could be an issue in some projects.
I'd also consider adding a beforeRestore as a new collection hook as an alternative to calling beforeChange and adding more variables to the arguments as that wouild force a lot of functions to be updated in existing projects to handle the additional calls.
For now you could work aroud this by adding your own custom endpoint to the collection so that you have the same method that then calls next. You won't be able to modify the data being updated within the restore like a normal hook would allow.
endpoints: [{
  'path': `/${collection.slug}/versions/:id`
  method: 'POST',
  handler: (req, res, next) => {
  // do whatever you want to be fore the operation
  // next()
}
}]


Setup page submit button functionality

Related to #989

Go to /#/setup
Once the space name is entered into input, Check if space exist on snapshot
If space exists - Redirect to space on click of submit button
If space doesn't exist:

Check if the name is registered
If the name belong to user - Redirect to space on click of submit button
If the name is already registered by someone else - Show not available message
If the name is available:

Change button text to "Register" and on click redirect to register page with the name input
Register page (https://app.ens.domains/name/<ENS NAME>/register) - Change this to /register?name=example.eth when register page is available

Waiting for #1029 to be merged

We should do like this https://github.com/snapshot-labs/snapshot/pull/1029#issuecomment-987837437


Error generating bindings: No such file or directory (os error 2)

I am running into the following error:
Failed due to the following error:
Could not generate UniFFI bindings for udl files due to the following error:
 No such file or directory (os error 2)

Steps to reproduce:
├── Cargo.toml
├── build.rs
└── src
    ├── lib.rs
    └── lib.udl

Cargo.toml
[package]
name = "expression_interpreter"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["staticlib", "lib"]
name = "expression_interpreter"

[dependencies]
uniffi = "0.28"

[build-dependencies]
uniffi = { version = "0.28", features = ["build"] }

build.rs
fn main() {
    uniffi::generate_scaffolding("./src/lib.udl").unwrap();
}

lib.rs
uniffi::include_scaffolding!("lib");

pub struct Executor {
}

impl Executor {
    pub fn new() -> Self {
        Executor {}
    }
}

lib.udl
namespace ExpressionInterpreter {};

interface Executor {
  constructor();
};

Full build output:
✗ cargo swift package -n ExpressionInterpreter -p macos
✔ Building target macOS
    cargo build --target x86_64-apple-darwin
    cargo build --target aarch64-apple-darwin
    mkdir -p target/universal-macos/debug
    lipo target/x86_64-apple-darwin/debug/libexpression_interpreter.a \
        target/aarch64-apple-darwin/debug/libexpression_interpreter.a -create -output \
        target/universal-macos/debug/libexpression_interpreter.a                                                                            x Generating Swift bindings...

Failed due to the following error:
Could not generate UniFFI bindings for udl files due to the following error:
 No such file or directory (os error 2)

More info
Lipo should have succeeded because the files are present:
✗ file target/x86_64-apple-darwin/debug/libexpression_interpreter.a
target/x86_64-apple-darwin/debug/libexpression_interpreter.a: current ar archive
✗ file target/aarch64-apple-darwin/debug/libexpression_interpreter.a
target/aarch64-apple-darwin/debug/libexpression_interpreter.a: current ar archive
✗ file target/universal-macos/debug/libexpression_interpreter.a
target/universal-macos/debug/libexpression_interpreter.a: Mach-O universal binary with 2 architectures: [x86_64:current ar archive] [arm64]
target/universal-macos/debug/libexpression_interpreter.a (for architecture x86_64):	current ar archive
target/universal-macos/debug/libexpression_interpreter.a (for architecture arm64):	current ar archive

After some more playing around, I found this error occurs because the Swift package name is not the same as the rust crate name defined in Cargo.toml.

After some more playing around, I found this error occurs because the Swift package name is not the same as the rust crate name defined in Cargo.toml.

thanks for coming back and pointing this out. I'll see if there is an elegant fix here or at least a warning that clarifies this


WIP: experiment to convert macaron to gin

This PR is an experiment to convert macaron to gin.
It moved all static files from macaron's middleware to gin's.
It made macaron as a middleware of gin, so that we can keep most of routes and move step by step.

Codecov Report

Merging #7177 into master will increase coverage by 0.01%.
The diff coverage is 42.3%.

@@            Coverage Diff             @@
##           master    #7177      +/-   ##
==========================================
+ Coverage   41.72%   41.73%   +0.01%
==========================================
  Files         449      450       +1
  Lines       61112    61128      +16
==========================================
+ Hits        25500    25513      +13
  Misses      32300    32300
- Partials     3312     3315       +3

Impacted Files
Coverage Δ

routers/routes/routes.go
83.79% <100%> (+0.94%)
:arrow_up:

routers/routes/gin_bridge.go
40% <40%> (ø)

modules/log/event.go
64.46% <0%> (-1.53%)
:arrow_down:

routers/repo/view.go
43.03% <0%> (+1.01%)
:arrow_up:

models/unit.go
67.56% <0%> (+5.4%)
:arrow_up:

Continue to review full report at Codecov.

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

@zeripath I think your suggest is not right. v is a local variable only available on if or else.

Oh I see. Switch em round?

So
func SignedUserName(ctx *gin.Context) string {
	if v, ok := ctx.Get("SignedUserName"); ok {
		return v.String()
	}
	return
}

Can you provide some info why gin and not chi ?

@vtolstov No reason from me. Just an experiment. I post a vote issue, see https://github.com/go-gitea/gitea/issues/7403

Thank you

related with #7403

Closed by #7420


attrs classes which inherit from slotted non-attrs classes do not inherit their bases' slots

This seems straightforwardly incorrect to me:
class NoAttrsSlotsBase:
    __slots__ = ['base']

class NoAttrsSlotsChild(NoAttrsSlotsBase):
    __slots__ = ['child']

from attrs import define

@define()
class AttrsWithNoAttrsBase:
    attrs_child: str = "default"

print(NoAttrsSlotsChild.base)
print(AttrsWithNoAttrsBase.base)

<member 'base' of 'NoAttrsSlotsBase' objects>
Traceback (most recent call last):
  File "slots2.py", line 16, in <module>
    print(AttrsWithNoAttrsBase.base)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: type object 'AttrsWithNoAttrsBase' has no attribute 'base'

Should it be fixed?

Oops I am dumb, please disregard


Feature request: add --node-labels command line option

Kubelet's --node-labels option is used by tools such as eksctl to manage groups of nodes in a K8S cluster.
Here's the help text for the option:
Labels to add when registering the node in the cluster.
Labels must be key=value pairs separated by ','.
Labels in the 'kubernetes.io' namespace must begin with an allowed prefix
(kubelet.kubernetes.io, node.kubernetes.io) or be in the specifically allowed set
(beta.kubernetes.io/arch, beta.kubernetes.io/instance-type, beta.kubernetes.io/os,
failure-domain.beta.kubernetes.io/region, failure-domain.beta.kubernetes.io/zone,
failure-domain.kubernetes.io/region, failure-domain.kubernetes.io/zone,
kubernetes.io/arch, kubernetes.io/hostname, kubernetes.io/instance-type,
kubernetes.io/os)

It would be nice if krustlet also supported this option so that external node management with such tools would also work.

Labeling this as a good first issue if anyone wanted to get started with krustlet. Shouldn't be too hard to add on to things and the hardest part will likely just be the parsing/validation for the CLI flag (the Config object can just accept a HashMap)

I've forked and branched.  Trying to figure out how to test it now.  Hopefully, I'll have something for you today or tomorrow.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98194

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/99835

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/101892

TagBot fix

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105372

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105387

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105595

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106156

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107785

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110119

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110688

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110746

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113043

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/115446

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/115825

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116038

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116530

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116964

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118722

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119502


chore: Use codecov upload token

Allow the build workflow to inherit secrets so that the CODECOV_TOKEN can be access by the codecov action. See https://github.com/cloudscape-design/.github/pull/48.
Related links, issue #, if available: AWSUI-20481
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Does it make sense to merge this before having tested the effects on the components repository and thus validate that this fixes the upload flakiness?

Does it make sense to merge this before having tested the effects on the components repository and thus validate that this fixes the upload flakiness?

Good question. I would say it generally makes sense to keep the workflow files in sync between repositories.


Youtube doesn't seem to be working?

Hey,
I get the following console logs when trying to use popcorn.js with youtube videos.
"failed to retrieve duration data, reason: No longer available"
I've noticed that the request to the Youtube api is returning error code 410 (no longer available). I think maybe it needs to be using the v3 api rather than 2.1?
Cheers,
Andre

Same for me! It stopped working! :-(

Same for me.

same here!

:+1:
Deprecated player 'youtube'. Please use Popcorn.HTMLYouTubeVideoElement directly. failed to retreive duration data, reason: No longer available
http://jsfiddle.net/popcornjs/whvkP/

Thanks for the hint. popcorn.js seems to be dead.

same here. confirmed not working with youtube.


Fix CMSEditableObject context generation

Fix #4948

@czpython @mkoistinen this fixes recent test failures (it look like a silly change but it was needed in 3.0/ Django <1.6)

:+1:

LGTM, let's merge this.


How to use the converted model for prediction?

@amir-abdi
Firstly, thank you for sharing this great work. However, I don't see any good example to demonstrate the usage for prediction using the converted TensorFlow model (.pb file). With Keras, you have predict function from the model,  while with a normally trained TF model, you specified the logits and placeholder for the input. With this converted model, I have no idea of how to perform the prediction. Could you please give me some guidance or a concrete example? Thank you very much!

Never mind. I have figured out everything.

I liked your suggestion and started to put together a sample deployment code for the readme. If you have figured it out and wanted to contribute to readme, feel free to initiate a pull request.

On Dec 2, 2017, at 3:53 PM, Bo Shao<EMAIL_ADDRESS>wrote:
Never mind. I have figured out everything.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@amir-abdi Thanks for your reply.
I have just uploaded a cleaner version on my git account. It is a working example. I added some extra comments to explain all the details. You can refer that to create samples if you want.
https://github.com/bshao001/DmsMsgRcg/blob/master/textdect/convertmodel.py


Add document date (vs added date)

I can only find "creation date", I think date added and document date are better - the latter one should be read automagically from the document...otherwise no chance for me to use this

Hi @totti4ever,
can you please describe in more detail what you mean with

the latter one should be read automagically from the document

?
What exactly you mean by "document date" ? or "date added" ?
I would love understand better your requirement.
Thank you for your feedback!

document date: date the letter (which are eventually most of my docs) has been written
good for finding documents and/or showing them in the right order
can be found by taking the first date in the ocred text
date added: date the pdf file was added to paper merge
good for finding documents added lately
from my understanding only the latter one is available right now

Hi @totti4ever,
Now I understand your point.
"document date" can be added using metadata feature.
Below are screenshots with a quick 3 step example:
Step 1 - in folder titled e.g. 2020

Step 2 - open any document in folder 2020

Step 3 - inside folder 2020, change to list view

Further more, you can process of extracting metadata can be automated.
However, I add soon documentation about "Automates" and how to write + configure plugins (feature is part of 1.4.0, it works, but not yet documented).

Hi, I see your point. But this makes the whole system for me not usable fluenty...I might check back in half a year or so to see whether it's more convenient to use then.
keep up the effort, it's great!


Make the website responsive

Hi @ANSHIKA-26 .
I would like to make the website responsive as the interface is not looking good on smaller screens


ng2-completer closes when scrollbar is clicked on IE browser

Hi @oferh, completer component closes when scrollbar is clicked on IE browser. I just wondering if you have time to fix it :)

Ho @ericoliveros, I don't think I'll get to it soon. b.t.w which version of IE?

Hi @oferh, it is Internet Explorer 11. Thanks in advance!

Hi @oferh,
I am also facing the same issue. Actually this is the issue with IE with BLUR event. When user clicks any where in IE window, blur events fire. This behavior is been controlled by other browsers like Chrome.
Could you please provide us with the solution as we are stuck with this issue ? Thanks in advance

It's not trivial to solve so may take some time for me to handle it (and I work on Mac and Linux most of the time)

closed in 1.3.0

Hi @oferh,
Thanks for your time on fixing this. :+1:

Hello. I think this bug should be opened again.
It works only in version 1.3.0, but it's broken in more recent versions.
Do you have time to fix, or could you please suggest me a workaround?
Thanks very much.

Hello, using setImmediate(fn) instead of setTimeout(fn, 0) in ctr-dropdown and ctr-input solves the problem. I hope that it doesn't introduce other regressions. May you please check and if it's ok then fix this issue? Thanks.


Add number of logs per day next to duration

Does anyone would know how to add the number of logs per day in the table generated on the website?

In the table ?
Basically it's Number of seconds by day divided by Your polling interval
Example : let's say we take a log every 3600seconds (=every hour). As you know there are 24 h / days, 60 minutes / hour and 60 seconds / hour.
so :
24 * 60 * 60 / 3600 = 24 logs /day.
Then for a log every 600s,
246060 / 600 = 144 logs / days.
Now we need to figure out a way to fetch the polling value from development.json, calculate the number of logs / days with Javascript on the website, and show it somewhere in the chart.
I'll look at this when I'll have the time.


NFS improvements

Motivation for this change
This moves us to using upstream rpcbind and nfs-utils systemd units, adding a lot of services in the process. It also enables Kerberos support in nfs-utils, so hopefully we are very close to having NFSv4 working now (I haven't yet tried to set it up though).
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Tested with my NFSv3 setup, works fine (however a reboot was needed, not sure why).

I assigned it (perhaps aspirationally) to 17.03.

Please do not merge yet -- there are still some improvements that I want
to make (notably, update nfs-utils).

Okay, this is version 2 of the patchset. I have updated more packages and moved to new configuration structure that is recommended by upstream (they also removed environment variables support from their systemd services).
NFSv3 still works on my local network.

Works fine for NFSv3 and we haven't supported much else so it should be OK. I'll merge in few days unless problems/comments surface.

I suspect this broke the NFS tests: http://hydra.nixos.org/job/nixos/unstable-small/nixos.tests.nfs3.x86_64-linux They started failing just after merge and restarting them doesn't seem to help.

sigh this is not the first time that I break tests because I don't check if there are any for this particular service. Fixed in https://github.com/NixOS/nixpkgs/commit/6812c7001ccedc142b9d93f72e2c2f2d611e6158, thanks!

If you fix stuff this fast, I don't think it matters much that you broke it in the first place ;-)  Master can sustain some short-term instabilities.


Only copy platform node_modules when created by binary

Platforms affected
osx
What does this PR do?
When platform is installed though CLI, cordova platform add osx, the copy node_modules step is no longer valid as dependencies are now at the project level.
The step is required only when the create binary from the platform repo is called.
https://github.com/apache/cordova/issues/32
What testing has been done on this change?

npm t
https://travis-ci.org/erisu/cordova-osx/builds/452152403

More Investigation Required


Clarify that all command arguments need to be present

Instead of a restrictive "All arguments needs to included in a command, otherwise it results a serious error resulting in MessageNotAck.", it could be written : "All required arguments for a command needs to be included..." It would allow the possibility to have some optional arguments in a command.

Good idea. However, right now we're assuming that all arguments are present. Otherwise we might end up with an undefined behaviour of how the TLC is expected to act. But I can certainly image there being some arguments in some command that can be considered optional, but they need to be defined in the SXL.
We've opened up a separate issue about optional arguments in commands. https://github.com/rsmp-nordic/rsmp_core/issues/148

I'm merging this and closing this issue.